[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: Fedora 31: dnf upgrade suddenly enables modular streams for protobuf
From:       Stephen Gallagher <sgallagh () redhat ! com>
Date:       2019-12-06 17:12:32
Message-ID: CAFoKQtyHUMMduRwrwSh+mkAO-8gB-uzdq04kKK0bcUwX9=doCw () mail ! gmail ! com
[Download RAW message or body]

On Fri, Dec 6, 2019 at 12:11 PM Charalampos Stratakis
<cstratak@redhat.com> wrote:
> 
> 
> 
> ----- Original Message -----
> > From: "Stephen Gallagher" <sgallagh@redhat.com>
> > To: "Development discussions related to Fedora" <devel@lists.fedoraproject.org>
> > Cc: "Mat Booth" <mbooth@fedoraproject.org>, \
> >                 protobuf-mainatiners@fedoraproject.org
> > Sent: Friday, December 6, 2019 5:59:50 PM
> > Subject: Re: Fedora 31: dnf upgrade suddenly enables modular streams for protobuf
> > 
> > On Fri, Dec 6, 2019 at 11:51 AM Igor Gnatenko
> > <ignatenkobrain@fedoraproject.org> wrote:
> > > 
> > > Thanks for CCing me (maintainer of protobuf here), I am particularly
> > > not happy that some module (which is not even called protobuf, but
> > > some random Java #$%! with ripped out python support overrides my
> > > builds).
> > > 
> > > I have put a proposal into a FESCo ticket.
> > > 
> > > On Fri, Dec 6, 2019 at 5:44 PM Miro Hrončok <mhroncok@redhat.com> wrote:
> > > > 
> > > > Today I've attempted to run "dnf upgrade".
> > > > 
> > > > It has the following in it:
> > > > 
> > > > Upgrading:
> > > > protobuf  x86_64  3.6.1-6.module_f31+6793+1c93c38e  updates-modular
> > > > 
> > > > Enabling module streams:
> > > > ant
> > > > eclipse
> > > > maven
> > > > 
> > > > 
> > > > I don't consider this behavior adequate for a released Fedora version.
> > > > 
> > > > As a maintainer of dependent packages (Cura stack) I have tested and
> > > > built it
> > > > against the nonmodular protobuf. What just happened here and how do I
> > > > track it down?
> > > > 
> > > > dnf doesn't even tell me what module is this in. I suppose eclipse.
> > > > 
> > > > However, protobuf was not mentioned in https://pagure.io/fesco/issue/2285
> > > > 
> > 
> > 
> > For the record, I've just pushed a temporary removal of the eclipse
> > default stream, so the next compose will not have it. For those of you
> > who are affected, your best bet would be to use `yum history rollback`
> > and wait to update again until tomorrow.
> 
> I got affected as well and I guess a big number of people also.
> 
> Is it safe to assume that with the next compose the extra modules will be \
> disabled/removed when doing a dnf update? Or do we need to rollback the update? 

No, the extra modules won't be disabled/removed automatically. The
change I made is to ensure no one else gets hit. You will need to roll
back the update if you were affected.
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org



[prev in list] [next in list] [prev in thread] [next in thread]