On Mon, Feb 25, 2019 at 2:20 PM Adam Williamson
<adamwill(a)fedoraproject.org> wrote:
On Mon, 2019-02-25 at 08:11 -0500, Stephen Gallagher wrote:
> On Fri, Feb 22, 2019 at 4:50 PM Robert P. J. Day <rpjday(a)crashcourse.ca>
wrote:
> > On Wed, 20 Feb 2019, Lukas Ruzicka wrote:
> >
> > > I know that fish module can be installed on Fedora Rawhide, but I
> > > have seen that many modules still require Platform29 and cannot be
> > > installed. Your errors say that Platform30 is required, my shot is
> > > that maybe that it may be caused by the fact that your Fedora still
> > > is not a 30 but Rawhide. Perhaps waiting a couple of days until the
> > > branch is finished might help. But I am just guessing. CCing Contyk
> > > to this discussion.
> >
> > just tried to upgrade again, and nothing has changed. what are my
> > other options at this point?
> >
>
> I suspect you're hitting
>
https://bugzilla.redhat.com/show_bug.cgi?id=1656509 which is an
> Accepted Blocker for Fedora 30 Beta.
>
> I'm going to do some digging around that one today and I'll report my
> findings back here.
So I was wondering what happens when the openQA tests run into this,
and it turns out that if you run with '--allowerasing', it works. I'm
not sure why, though. Can you guys try that and confirm, and see if
anything actually gets erased?
I ran:
# dnf install 'dnf-command(system-upgrade)'
# dnf module install reviewboard:2.5
# dnf --releasever=30 --allowerasing system-upgrade download
and got:
Removing dependent packages:
ReviewBoard noarch
2.5.17-17.module_1631+4353a891 @fedora-modular
28 M
python2-django-haystack noarch
2.4.1-12.module_1631+4353a891 @fedora-modular
729 k
python2-djblets noarch
0.9.9-13.module_1631+4353a891 @fedora-modular
3.2 M
So yes, --allowerasing apparently removes the packages from the
modules that it's having trouble updating.
However, if I add `dnf module install nodejs:11` into the mix, I also get:
Downgrading:
nodejs x86_64
1:10.15.0-1.fc30 fedora
6.4 M
npm x86_64
1:6.4.1-1.10.15.0.1.fc30 fedora
3.6 M
Which is downgrading it to the copy that's in the standard
repositories (which is *definitely* bad, as it will break anything
relying on the 11.x experimental version).