Re: update to F32 conflicts

2020-04-27 Thread Patrick O'Callaghan
On Mon, 2020-04-27 at 11:02 +, Neal Becker wrote: > > On Sun, 2020-04-26 at 20:59 +, Neal Becker wrote: > > > > That would have been clearer had you quoted the context. Since you're > > using the lame HyperKitty interface, this is something you have to do > > manually. > > > > poc > >

Re: update to F32 conflicts

2020-04-27 Thread Neal Becker
> On Sun, 2020-04-26 at 20:59 +, Neal Becker wrote: > > That would have been clearer had you quoted the context. Since you're > using the lame HyperKitty interface, this is something you have to do > manually. > > poc For years I've been using gmane to read/write this (and other) lists.

Re: update to F32 conflicts

2020-04-27 Thread Patrick O'Callaghan
On Sun, 2020-04-26 at 20:59 +, Neal Becker wrote: > No, I was replying to an earlier message. I didn't try --allowerasing, I had > already just removed mutter328 before I saw your message. Perhaps that would > have worked. That would have been clearer had you quoted the context. Since

Re: update to F32 conflicts

2020-04-26 Thread Ed Greshko
On 2020-04-27 04:59, Neal Becker wrote: > No, I was replying to an earlier message. I didn't try --allowerasing, I had > already just removed mutter328 before I saw your message. Perhaps that would > have worked. > Probably would have.  By erasing.  And, earlier you said you didn't want to

Re: update to F32 conflicts

2020-04-26 Thread Neal Becker
No, I was replying to an earlier message. I didn't try --allowerasing, I had already just removed mutter328 before I saw your message. Perhaps that would have worked. Thanks, Neal ___ users mailing list -- users@lists.fedoraproject.org To

Re: update to F32 conflicts

2020-04-26 Thread Samuel Sieb
On 4/26/20 1:50 PM, Neal Becker wrote: I got the same error with --skip-broken. If you're replying to me, I said "--allowerasing", not "--skip-broken". ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to

Re: update to F32 conflicts

2020-04-26 Thread Neal Becker
I got the same error with --skip-broken. Finally I just removed mutter328. This removed the dependent packages (e.g., wingpanel-blah-blah), but I don't even know what they are and probably won't miss them. ___ users mailing list --

Re: update to F32 conflicts

2020-04-26 Thread Samuel Sieb
On 4/26/20 5:16 AM, Neal Becker wrote: I've removed a few packages (python2 related) and gotten it down to this: Error: Problem: package mutter328-libs-3.28.4-4.fc31.x86_64 requires libgnome-desktop-3.so.18()(64bit), but none of the providers can be installed -

Re: update to F32 conflicts

2020-04-26 Thread Ed Greshko
On 2020-04-26 20:16, Neal Becker wrote: > I've removed a few packages (python2 related) and gotten it down to this: > Error: > Problem: package mutter328-libs-3.28.4-4.fc31.x86_64 requires > libgnome-desktop-3.so.18()(64bit), but none of the providers can be installed > -

Re: update to F32 conflicts

2020-04-26 Thread Neal Becker
I've removed a few packages (python2 related) and gotten it down to this: Error: Problem: package mutter328-libs-3.28.4-4.fc31.x86_64 requires libgnome-desktop-3.so.18()(64bit), but none of the providers can be installed - gnome-desktop3-3.34.5-1.fc31.x86_64 does not belong to a distupgrade

Re: update to F32 conflicts

2020-04-24 Thread Ed Greshko
On 2020-04-25 00:05, home user wrote: > It looks like you are having module problems. I don't know if this > will help, but while testing upgrade from F31 to F32 to look for > issues, we were advised to run > dnf module reset '*' > to make modules behave before running the upgrade. You could try

Re: update to F32 conflicts

2020-04-24 Thread home user
> Any suggestions about any of these conflicts? > > sudo dnf system-upgrade download --refresh --releasever=32 > sudo dnf system-upgrade download --refresh --releasever=32 > Before you continue ensure that your system is fully upgraded by running "dnf > --refresh upgrade". Do you want to

Re: update to F32 conflicts

2020-04-24 Thread Ed Greshko
On 2020-04-24 20:09, Neal Becker wrote: > Any suggestions about any of these conflicts? You probably can get by with adding --skip-broken to the upgrade command.  Alternatively, disable the repo from where they came since you see "does not belong to a distupgrade repository".  Probably those

update to F32 conflicts

2020-04-24 Thread Neal Becker
Any suggestions about any of these conflicts? sudo dnf system-upgrade download --refresh --releasever=32 sudo dnf system-upgrade download --refresh --releasever=32 Before you continue ensure that your system is fully upgraded by running "dnf --refresh upgrade". Do you want to continue [y/N]: y