Re: Workaround for Re: Broken system upgrade due to rich dependencies

On Fri, Mar 09, 2018 at 11:05:55AM +0100, Igor Gnatenko wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I have built RPM with backported with/without/unless rich deps for F26. > > https://copr.fedorainfracloud.org/coprs/ignatenkobrain/rpm-4.13.x-richd > eps/ > > Just update from

Re: Workaround for Re: Broken system upgrade due to rich dependencies

On Fri, Mar 9, 2018 at 5:05 AM, Igor Gnatenko wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I have built RPM with backported with/without/unless rich deps for F26. > > https://copr.fedorainfracloud.org/coprs/ignatenkobrain/rpm-4.13.x-richd > eps/

Re: Re: Broken system upgrade due to rich dependencies

On 8 March 2018 at 14:37, Tony Nelson wrote: > On 18-03-07 14:14:38, Nicolas Mailhot wrote: >> >> Le mercredi 07 mars 2018 à 12:18 -0500, Josh Boyer a écrit : >> > On Wed, Mar 7, 2018 at 12:11 PM, Nicolas Mailhot >> > wrote: >> > > Le

Workaround for Re: Broken system upgrade due to rich dependencies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have built RPM with backported with/without/unless rich deps for F26. https://copr.fedorainfracloud.org/coprs/ignatenkobrain/rpm-4.13.x-richd eps/ Just update from this repo before doing distro-sync/system-upgrade and you should be good. - -- -

Re: Broken system upgrade due to rich dependencies

> "PM" == Panu Matilainen writes: PM> It's not a solution because doing so usually drags half the distro PM> along due to library dependencies etc. That's true if you're updating to the rpm/dnf/whatever from the distro you want to upgrade to. That's not true if you're

Re: Broken system upgrade due to rich dependencies

Le jeudi 08 mars 2018 à 15:47 -0500, Stephen John Smoogen a écrit : > On 8 March 2018 at 15:32, Stephen John Smoogen > wrote: > > On 8 March 2018 at 13:38, Nicolas Mailhot > et> wrote: > > I have spent this afternoon going through many of your emails

Re: Broken system upgrade due to rich dependencies

El jue, 08-03-2018 a las 12:55 +0200, Panu Matilainen escribió: > On 03/08/2018 12:42 PM, Panu Matilainen wrote: > > On 03/08/2018 12:21 PM, Reindl Harald wrote: > > > > > > > > > Am 08.03.2018 um 08:53 schrieb Panu Matilainen: > > > > P.P.S. So why didn't yum have anything like that? Because

Re: Broken system upgrade due to rich dependencies

On 8 March 2018 at 15:32, Stephen John Smoogen wrote: > On 8 March 2018 at 13:38, Nicolas Mailhot wrote: > I have spent this afternoon going through many of your emails and our > logs so I could find try to figure out what to help you. Coming back

Re: Broken system upgrade due to rich dependencies

On 8 March 2018 at 13:38, Nicolas Mailhot wrote: > Le jeudi 08 mars 2018 à 17:57 +, Tom Hughes a écrit : >> >> No, it almost certainly means that laposte.net have announced via >> their DNS records that emails with laposte.net addresses should not >> be trusted

Re: Re: Broken system upgrade due to rich dependencies

On 18-03-07 14:14:38, Nicolas Mailhot wrote: Le mercredi 07 mars 2018 à 12:18 -0500, Josh Boyer a écrit : > On Wed, Mar 7, 2018 at 12:11 PM, Nicolas Mailhot > wrote: > > Le mercredi 07 mars 2018 à 11:31 -0500, Stephen John Smoogen a écrit > > : > > > > > > I

Re: Broken system upgrade due to rich dependencies

Le jeudi 08 mars 2018 à 17:57 +, Tom Hughes a écrit : > > No, it almost certainly means that laposte.net have announced via > their DNS records that emails with laposte.net addresses should not > be trusted unless they come direct from a laposte.net server. Actually, it probably means the

Re: Broken system upgrade due to rich dependencies

On 08/03/18 17:46, Nicolas Mailhot wrote: Le jeudi 08 mars 2018 à 18:11 +0100, Fabio Valentini a écrit : Additionally, I frequently get Spam warnings for your e-mails because they don't pass the validation tests for being sent from a laposte.net address. That tells a lot more about USA

unproductive finger pointing; was: Re: Broken system upgrade due to rich dependencies

On Thu, 8 Mar 2018, Nicolas Mailhot wrote: > That tells a lot more about USA operators being not willing to work with > non USA operators than anything else. ehh? from the headers in that post, as received by me: X-Authentication-Results: bastion01.phx2.fedoraproject.org; dkim=fail

Re: Broken system upgrade due to rich dependencies

Le jeudi 08 mars 2018 à 18:11 +0100, Fabio Valentini a écrit : > > Additionally, I frequently get Spam warnings for your e-mails because > they don't pass the validation tests for being sent from a laposte.net > address. That tells a lot more about USA operators being not willing to work with

Re: Re: Broken system upgrade due to rich dependencies

On Thu, 2018-03-08 at 17:47 +0100, Nicolas Mailhot wrote: > Le jeudi 08 mars 2018 à 18:15 +0200, Yanko Kaneti a écrit : > > > > Nobody would care if a MTA on the way Fedora-ml->your-mailbox adds > > because nobody but you would see it. > > And what, exactly, do you think answers to those mails

Re: Re: Broken system upgrade due to rich dependencies

On Thu, Mar 8, 2018 at 5:47 PM, Nicolas Mailhot wrote: > Le jeudi 08 mars 2018 à 18:15 +0200, Yanko Kaneti a écrit : >> >> Nobody would care if a MTA on the way Fedora-ml->your-mailbox adds >> because nobody but you would see it. > > And what, exactly, do you think

Re: Re: Broken system upgrade due to rich dependencies

Le jeudi 08 mars 2018 à 18:15 +0200, Yanko Kaneti a écrit : > > Nobody would care if a MTA on the way Fedora-ml->your-mailbox adds > because nobody but you would see it. And what, exactly, do you think answers to those mails look like once they had this added on the incoming route? You're not

Re: Re: Broken system upgrade due to rich dependencies

On Wed, 2018-03-07 at 20:14 +0100, Nicolas Mailhot wrote: > Le mercredi 07 mars 2018 à 12:18 -0500, Josh Boyer a écrit : > > On Wed, Mar 7, 2018 at 12:11 PM, Nicolas Mailhot > > wrote: > > > Le mercredi 07 mars 2018 à 11:31 -0500, Stephen John Smoogen a > > > écrit >

Re: Broken system upgrade due to rich dependencies

On 03/08/2018 02:23 PM, Neal Gompa wrote: On Thu, Mar 8, 2018 at 6:48 AM, Panu Matilainen wrote: On 03/08/2018 01:39 PM, Neal Gompa wrote: On Thu, Mar 8, 2018 at 2:53 AM, Panu Matilainen wrote: On 03/07/2018 03:10 PM, Neal Gompa wrote: On Wed,

Re: Broken system upgrade due to rich dependencies

On Thu, Mar 8, 2018 at 6:48 AM, Panu Matilainen wrote: > On 03/08/2018 01:39 PM, Neal Gompa wrote: >> >> On Thu, Mar 8, 2018 at 2:53 AM, Panu Matilainen >> wrote: >>> >>> On 03/07/2018 03:10 PM, Neal Gompa wrote: On Wed, Mar 7, 2018 at

Re: Broken system upgrade due to rich dependencies

On 03/08/2018 01:39 PM, Neal Gompa wrote: On Thu, Mar 8, 2018 at 2:53 AM, Panu Matilainen wrote: On 03/07/2018 03:10 PM, Neal Gompa wrote: On Wed, Mar 7, 2018 at 5:52 AM, Igor Gnatenko wrote: And you forgot: 5. Teach DNF to use

Re: Broken system upgrade due to rich dependencies

On Thu, Mar 8, 2018 at 2:53 AM, Panu Matilainen wrote: > On 03/07/2018 03:10 PM, Neal Gompa wrote: >> >> On Wed, Mar 7, 2018 at 5:52 AM, Igor Gnatenko >> wrote: >>> >>> And you forgot: >>> 5. Teach DNF to use "target" DNF/RPM stack to

Re: Broken system upgrade due to rich dependencies

On 03/08/2018 12:42 PM, Panu Matilainen wrote: On 03/08/2018 12:21 PM, Reindl Harald wrote: Am 08.03.2018 um 08:53 schrieb Panu Matilainen: P.P.S. So why didn't yum have anything like that? Because back then, there were other upgrade methods that did run on the "target stack": anaconda,

Re: Broken system upgrade due to rich dependencies

On 03/08/2018 12:21 PM, Reindl Harald wrote: Am 08.03.2018 um 08:53 schrieb Panu Matilainen: P.P.S. So why didn't yum have anything like that? Because back then, there were other upgrade methods that did run on the "target stack": anaconda, preupgrade, fedup to name a few and i never used

Re: Broken system upgrade due to rich dependencies

On 03/08/2018 09:53 AM, Panu Matilainen wrote: On 03/07/2018 03:10 PM, Neal Gompa wrote: On Wed, Mar 7, 2018 at 5:52 AM, Igor Gnatenko wrote: And you forgot: 5. Teach DNF to use "target" DNF/RPM stack to perform upgrade (best and proper way). This has been

Re: Broken system upgrade due to rich dependencies

On 03/07/2018 03:10 PM, Neal Gompa wrote: On Wed, Mar 7, 2018 at 5:52 AM, Igor Gnatenko wrote: And you forgot: 5. Teach DNF to use "target" DNF/RPM stack to perform upgrade (best and proper way). This has been requested for a long time:

Re: Re: Broken system upgrade due to rich dependencies

Le mercredi 07 mars 2018 à 12:18 -0500, Josh Boyer a écrit : > On Wed, Mar 7, 2018 at 12:11 PM, Nicolas Mailhot > wrote: > > Le mercredi 07 mars 2018 à 11:31 -0500, Stephen John Smoogen a écrit > > : > > > > > > I don't know if this is useful but in the RHL and early

Re: Re: Broken system upgrade due to rich dependencies

Le 2018-03-07 18:15, Reindl Harald a écrit : if there wouldn't be dependencies in the real world making it risky and difficult just update rpm itself would you pull all dependencies down to glibc with that transaction? If needed, yes, it is unsafe to install from a repo that has a newer rpm

Re: Broken system upgrade due to rich dependencies

On Wed, 2018-03-07 at 09:13 -0500, Colin Walters wrote: > > On Wed, Mar 7, 2018, at 5:52 AM, Igor Gnatenko wrote: > > > > And you forgot: > > 5. Teach DNF to use "target" DNF/RPM stack to perform upgrade (best and > > proper way). > > If you're using yum/dnf inside a container, the natural way

Re: Re: Broken system upgrade due to rich dependencies

On Wed, 7 Mar 2018, Nicolas Mailhot wrote: > It is quite insane, that, to this day, users are expected to know the > rpm stack better than dnf, and tell it to update it first. > > KNOWING THE PACKAGE INFRA STACK STACK IS THE INSTALLER JOB > > whenever dnf hits a repo with an updated rpm stack,

Re: Re: Broken system upgrade due to rich dependencies

On Wed, Mar 7, 2018 at 12:11 PM, Nicolas Mailhot wrote: > Le mercredi 07 mars 2018 à 11:31 -0500, Stephen John Smoogen a écrit : >> >> I don't know if this is useful but in the RHL and early Fedora days, >> the way to do inplace upgrades was to first update just the

Re: Re: Broken system upgrade due to rich dependencies

Le mercredi 07 mars 2018 à 11:31 -0500, Stephen John Smoogen a écrit : > > I don't know if this is useful but in the RHL and early Fedora days, > the way to do inplace upgrades was to first update just the 'core' > tools needed by rpm. It is quite insane, that, to this day, users are expected to

Re: Broken system upgrade due to rich dependencies

On 7 March 2018 at 05:40, Jaroslav Mracek wrote: > Recently, several users report problems with system upgrade due to rich > dependencies that are not supported by RPM in Fedora 25, and not fully > supported by RPM in Fedora 26 (statement 'with'). Rich dependencies are >

Re: Broken system upgrade due to rich dependencies

On Wed, Mar 7, 2018, at 5:52 AM, Igor Gnatenko wrote: > > And you forgot: > 5. Teach DNF to use "target" DNF/RPM stack to perform upgrade (best and > proper way). If you're using yum/dnf inside a container, the natural way to major upgrades is to just pull the new base image and rebuild, rather

Re: Broken system upgrade due to rich dependencies

On Wed, Mar 7, 2018 at 5:52 AM, Igor Gnatenko wrote: > And you forgot: > 5. Teach DNF to use "target" DNF/RPM stack to perform upgrade (best and > proper way). > This has been requested for a long time: https://bugzilla.redhat.com/show_bug.cgi?id=1032541 It'd

Re: Broken system upgrade due to rich dependencies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2018-03-07 at 10:40 +, Jaroslav Mracek wrote: > Recently, several users report problems with system upgrade due to > rich dependencies that are not supported by RPM in Fedora 25, and not > fully supported by RPM in Fedora 26 (statement