Hi All,
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
-T (T/Mr.T/Todd/Dude/His Resplendence)
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
How did you end up with dnf5? That might explain some of your issues.
On 10/22/24 02:22, Samuel Sieb wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
How did you end up with dnf5? That might explain some of your issues.
I presume it was part of the upgrade to 40
# rpm -qa dnf dnf-4.21.1-1.fc39.noarch
# which dnf /usr/bin/dnf
# ls -al /usr/bin/dnf lrwxrwxrwx. 1 root root 4 Sep 19 17:00 /usr/bin/dnf -> dnf5
On 10/22/24 2:25 AM, ToddAndMargo via users wrote:
On 10/22/24 02:22, Samuel Sieb wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
How did you end up with dnf5? That might explain some of your issues.
I presume it was part of the upgrade to 40
# rpm -qa dnf dnf-4.21.1-1.fc39.noarch
# which dnf /usr/bin/dnf
# ls -al /usr/bin/dnf lrwxrwxrwx. 1 root root 4 Sep 19 17:00 /usr/bin/dnf -> dnf5
Maybe it was the failed upgrade to 41. I'm on 40 and have this: # rpm -q dnf dnf-4.21.1-1.fc40.noarch # ls -l /usr/bin/dnf lrwxrwxrwx. 1 root root 5 Aug 14 17:00 /usr/bin/dnf -> dnf-3
What does "rpm -qf /usr/bin/dnf5" give you?
I do have dnf5 also installed, but it's not supposed to be the default and I'm pretty sure that I installed it myself to test something.
On 10/22/24 02:38, Samuel Sieb wrote:
On 10/22/24 2:25 AM, ToddAndMargo via users wrote:
On 10/22/24 02:22, Samuel Sieb wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
How did you end up with dnf5? That might explain some of your issues.
I presume it was part of the upgrade to 40
# rpm -qa dnf dnf-4.21.1-1.fc39.noarch
# which dnf /usr/bin/dnf
# ls -al /usr/bin/dnf lrwxrwxrwx. 1 root root 4 Sep 19 17:00 /usr/bin/dnf -> dnf5
Maybe it was the failed upgrade to 41.
Most probably!
I'm on 40 and have this: # rpm -q dnf dnf-4.21.1-1.fc40.noarch # ls -l /usr/bin/dnf lrwxrwxrwx. 1 root root 5 Aug 14 17:00 /usr/bin/dnf -> dnf-3
What does "rpm -qf /usr/bin/dnf5" give you?
# rpm -qf /usr/bin/dnf5 file /usr/bin/dnf5 is not owned by any package
I do have dnf5 also installed, but it's not supposed to be the default and I'm pretty sure that I installed it myself to test something.
Since I am going to be on 41 pretty quick, do you know what dnf5 did with skip-broken?
Oh and get this, I am still on 38's kernel!
# uname -r 6.5.10-200.fc38.x86_64
On Tue, Oct 22, 2024 at 5:46 AM ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
On 10/22/24 02:38, Samuel Sieb wrote:
On 10/22/24 2:25 AM, ToddAndMargo via users wrote:
On 10/22/24 02:22, Samuel Sieb wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
How did you end up with dnf5? That might explain some of your issues.
I presume it was part of the upgrade to 40
# rpm -qa dnf dnf-4.21.1-1.fc39.noarch
# which dnf /usr/bin/dnf
# ls -al /usr/bin/dnf lrwxrwxrwx. 1 root root 4 Sep 19 17:00 /usr/bin/dnf -> dnf5
Maybe it was the failed upgrade to 41.
Most probably!
I'm on 40 and have this: # rpm -q dnf dnf-4.21.1-1.fc40.noarch # ls -l /usr/bin/dnf lrwxrwxrwx. 1 root root 5 Aug 14 17:00 /usr/bin/dnf -> dnf-3
What does "rpm -qf /usr/bin/dnf5" give you?
# rpm -qf /usr/bin/dnf5 file /usr/bin/dnf5 is not owned by any package
I do have dnf5 also installed, but it's not supposed to be the default and I'm pretty sure that I installed it myself to test something.
Since I am going to be on 41 pretty quick, do you know what dnf5 did with skip-broken?
Oh and get this, I am still on 38's kernel!
Doesn't 41 still offer dnf? I have both installed on 40.
On 22 Oct 2024, at 15:54, Neal Becker ndbecker2@gmail.com wrote:
Doesn't 41 still offer dnf? I have both installed on 40.
on f40 dnf4 is default and recommended. You can experiment with dnf5, but beware of bugs. on f41 dnf5 is default and recommanded. You can fall back to dnf4 if something important breaks in dnf5.
Barry
On 10/22/24 2:46 AM, ToddAndMargo via users wrote:
On 10/22/24 02:38, Samuel Sieb wrote:
On 10/22/24 2:25 AM, ToddAndMargo via users wrote:
On 10/22/24 02:22, Samuel Sieb wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
How did you end up with dnf5? That might explain some of your issues.
I presume it was part of the upgrade to 40
# rpm -qa dnf dnf-4.21.1-1.fc39.noarch
# which dnf /usr/bin/dnf
# ls -al /usr/bin/dnf lrwxrwxrwx. 1 root root 4 Sep 19 17:00 /usr/bin/dnf -> dnf5
Maybe it was the failed upgrade to 41.
Most probably!
I'm on 40 and have this: # rpm -q dnf dnf-4.21.1-1.fc40.noarch # ls -l /usr/bin/dnf lrwxrwxrwx. 1 root root 5 Aug 14 17:00 /usr/bin/dnf -> dnf-3
What does "rpm -qf /usr/bin/dnf5" give you?
# rpm -qf /usr/bin/dnf5 file /usr/bin/dnf5 is not owned by any package
Something is really broken now. I highly recommend a re-install at this point or when you decide to go to F41. I wouldn't trust any of the system files to be what they should be.
On 10/22/24 20:04, ToddAndMargo via users wrote:
On 10/22/24 13:57, Samuel Sieb wrote:
I highly recommend a re-install at this point or when you decide to go to F41.
Do yo mean wipe and reinstall? Or is there an in place reinstall?
My backups have most of the offending thing on them that caused this. So a good clean up is best at this point
On 10/22/24 8:04 PM, ToddAndMargo via users wrote:
On 10/22/24 13:57, Samuel Sieb wrote:
I highly recommend a re-install at this point or when you decide to go to F41.
Do yo mean wipe and reinstall? Or is there an in place reinstall?
You could keep your /home directory (assuming you aren't the person that said they don't separate that), but yes, a wipe and re-install of the root partition. Personally, I would probably have done that a while ago if it was my computer. It's a bit of a pain to find all the missing packages as you go, but it's better than wondering what else is messed up. Make a copy of /etc and re-install. But to be fair, I've gone both ways with situations like this. It depends on things like how quickly I need it running again, how much time I have to mess around with it, how badly it's messed up, etc.
On Tue, 2024-10-22 at 22:59 -0700, Samuel Sieb wrote:
You could keep your /home directory (assuming you aren't the person that said they don't separate that), but yes, a wipe and re-install of the root partition.
Long ago, probably back before Fedora existed, I did installs in place by booting off something else. Deleting all files I wanted gone (everything but my data). Starting the installer, selecting existing partitions, and unselecting "format" options for each partitions. It was dicing with death, but it worked. I haven't looked to see if you can still do the same trick.
I like to keep data on a separate drive. It can be unplugged during an install, and replugged later.
Or, unplug existing drive. Install to a spare drive. Import the data from the old drive after installation. Unplug and keep the old drive as a temporary back-up, and to use as the next spare drive.
Installing to a spare drive takes so much stress out of the situation, and you're free to experiment all over the place before committing yourself to it.
I'd always found upgrades over the top to be risky. Apart from your own data loss, things can get left over with system/app/config files from prior releases. It took me far longer (many hours or days) than doing a fresh install, then customise it using my old configuration files as templates.
On 10/22/24 11:52 PM, Tim via users wrote:
On Tue, 2024-10-22 at 22:59 -0700, Samuel Sieb wrote:
You could keep your /home directory (assuming you aren't the person that said they don't separate that), but yes, a wipe and re-install of the root partition.
Long ago, probably back before Fedora existed, I did installs in place by booting off something else. Deleting all files I wanted gone (everything but my data). Starting the installer, selecting existing partitions, and unselecting "format" options for each partitions. It was dicing with death, but it worked. I haven't looked to see if you can still do the same trick.
The Fedora installer will not let you do that for very good reasons.
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
Hi All,
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
-T (T/Mr.T/Todd/Dude/His Resplendence)
Followup:
It is a bug:
dnf5 upgrade does not recognize --skip-broken option https://github.com/rpm-software-management/dnf5/issues/1033
Many thanks, -T (T/Mr.T/Todd/Dude/His Resplendence)
On Tue, 2024-10-22 at 16:19 -0700, ToddAndMargo via users wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
Hi All,
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
-T (T/Mr.T/Todd/Dude/His Resplendence)
Followup:
It is a bug:
dnf5 upgrade does not recognize --skip-broken option https://github.com/rpm-software-management/dnf5/issues/1033
Yet another reason to be discussing this on the Test list.
poc
On Wed, 2024-10-23 at 04:39 -0700, ToddAndMargo via users wrote:
On 10/23/24 02:54, Patrick O'Callaghan wrote:
Yet another reason to be discussing this on the Test list.
They are not very responsive over there.
They'll still want to hear about bugs. And either way, if you want to test unreleased software that's the place for it.
poc
Patrick O'Callaghan wrote:
On Wed, 2024-10-23 at 04:39 -0700, ToddAndMargo via users wrote:
On 10/23/24 02:54, Patrick O'Callaghan wrote:
Yet another reason to be discussing this on the Test list.
They are not very responsive over there.
They'll still want to hear about bugs. And either way, if you want to test unreleased software that's the place for it.
And lacking a suitably quick reply is not an excuse to post on the wrong list.
I suspect that the folks on the test list are less inclined to help when someone is flailing about and not reading the documentation before asking for help. :)
T, please take a breath and read up before you rush to install the beta release of Fedora so you know what the changes are and are prepared to adjust for them.
(and for the love of all that is good, please do a clean install or restore from a solid backup so every issue you have isn't likely to be due to a horribly failed system upgrade.)
ToddAndMargo via users wrote:
On 10/22/24 2:04 AM, ToddAndMargo via users wrote:
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
[...]
It is a bug:
dnf5 upgrade does not recognize --skip-broken option https://github.com/rpm-software-management/dnf5/issues/1033
You need to actually read through the issues to see how they are resolved. That issue is closed and the skip-broken option was removed. It is documented on the changes page:
https://dnf5.readthedocs.io/en/stable/changes.html#changes-to-individual-com...
upgrade
* Dropped --skip-broken option, as it was already available in DNF4 only for compatibility reasons with YUM, but has no effect. * Instead, decisions about package selection and handling dependency issues are based on the best or no-best options.
On 10/22/24 02:04, ToddAndMargo via users wrote:
Hi All,
What replaces --skip-broken in dnf5?
# dnf --releasever=40 --skip-broken upgrade Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more information about the arguments.
-T (T/Mr.T/Todd/Dude/His Resplendence)
I am on dnf3 now
-
Barry Scott -
Neal Becker -
Patrick O'Callaghan -
Samuel Sieb -
Tim -
Todd Zullinger -
ToddAndMargo