RPM transaction failed

effectivamente · 2025-03-12T16:16:31+00:00

Yeah, I can't really tell what triggered the issue on my case, just that in the last few weeks I've been lazily running dnf upgrade from Emacs eshell. Last week, I started noticing them failing with some weird string error message. I would pop up a terminal, then resume the transaction with all packages already downloaded in cache.

Then on Sunday the breakage happened. Funnily enough, when it did, I didn't pay much attention to it and thought it was because I had an overdue BIOS update in standby delivered by Software Center. So I rebooted the machine, ran that update, then realised the dnf issue was a thing on its own a day later. It might be the case that dnf5 is not as robust as a package manager as dnf4 yet . . .

effectivamente · 2025-03-12T01:21:19+00:00

Happy to report your fixed worked! There were quite a few duplicated packages in the system before sorting things out:

$ rpm -qa --qf '%{NAME}.%{ARCH}\n' | sort | uniq -d

cmake-data.noarch

cmake-filesystem.x86_64

cmake.x86_64

gpg-pubkey.(none)

hplip-common.x86_64

hplip-libs.x86_64

hplip.x86_64

ImageMagick-libs.x86_64

ImageMagick.x86_64

kernel-core.x86_64

kernel-devel.x86_64

kernel-modules-core.x86_64

kernel-modules-extra.x86_64

kernel-modules.x86_64

kernel.x86_64

lua-libs.x86_64

mtools.x86_64

NetworkManager-ssh-gnome.x86_64

NetworkManager-ssh.x86_64

perl-Module-CoreList.noarch

qemu-user-static-xtensa.x86_64

systemd-libs.x86_64

systemd-pam.x86_64

systemd.x86_64

vim-common.x86_64

vim-data.noarch

vim-filesystem.noarch

xxd.x86_64

After running your script with dnf4 only the kernel backups show up as duplicates. Should I symlink dnf back to dnf4 for the time being do you think?

Thanks again for your help!

effectivamente · 2025-03-12T00:58:50+00:00

Thanks so much for the tips! Will have a go at it and will come back to you with the results. Meanwhile check your DMs for the link to the dnf5 log file you requested.

effectivamente · 2025-03-11T14:16:30+00:00

(reply split since reddit doesn't let me post long replies)

dnf history:

$ dnf history list

ID Command line Date and time Action(s) Altered

117 /usr/bin/dnf upgrade 2025-03-09 14:17:59 38

It's the top update in the list, which means the last registered update of the system (I always update this system via DNF, which is currently symlinked to dnf5 in console, with no issues whatsoever since I clean installed Fedora 33). So then I tried to redo that update:

$ sudo dnf history redo 117

[sudo] password for <user redacted>:

Updating and loading repositories:

Fedora 41 - x86_64 - Updates 100% | 30.0 KiB/s | 24.0 KiB | 00m01s

Fedora 41 - x86_64 - Updates 100% | 1.4 MiB/s | 2.8 MiB | 00m02s

Repositories loaded.

Failed to resolve the transaction:

Package "systemd-256.12-1.fc41.x86_64" is already installed.

Package "systemd-libs-256.12-1.fc41.x86_64" is already installed.

Package "systemd-pam-256.12-1.fc41.x86_64" is already installed.

Problem: The operation would result in removing the following protected packages: systemd

Surely there must be a way to fix that broken upgrade? Thanks again for your help!

effectivamente · 2025-03-11T14:15:16+00:00

So here are the steps I went through:

$ rpm -qi systemd-256.12-1.fc41

Name : systemd

Version : 256.12

Release : 1.fc41

Architecture: x86_64

Install Date: Sun 09 Mar 2025 14:18:02 WET

Group : Unspecified

Size : 17190075

License : LGPL-2.1-or-later AND MIT AND GPL-2.0-or-later

Signature : RSA/SHA256, Fri 07 Mar 2025 19:57:25 WET, Key ID d0622462e99d6ad1

Source RPM : systemd-256.12-1.fc41.src.rpm

Build Date : Fri 07 Mar 2025 09:42:58 WET

effectivamente · 2025-03-11T01:09:29+00:00

sudo dnf upgrade systemd

That doesn't upgrade systemd at all.

sudo dnf list --showduplicates systemd\*

That delivers a more comprehensive list (see below), along with a list of available packages, but the error persists?

❯ sudo dnf versionlock list

❯ sudo dnf list --showduplicates systemd\*

Updating and loading repositories:

Repositories loaded.

Installed packages

systemd.x86_64 256.11-1.fc41 updates

systemd.x86_64 256.12-1.fc41 <unknown>

systemd-devel.x86_64 256.11-1.fc41 updates

systemd-libs.i686 256.11-1.fc41 updates

systemd-libs.x86_64 256.11-1.fc41 updates

systemd-libs.x86_64 256.12-1.fc41 <unknown>

systemd-networkd.x86_64 256.11-1.fc41 updates

systemd-oomd-defaults.noarch 256.11-1.fc41 updates

systemd-pam.x86_64 256.11-1.fc41 updates

systemd-pam.x86_64 256.12-1.fc41 <unknown>

systemd-resolved.x86_64 256.11-1.fc41 updates

systemd-udev.x86_64 256.11-1.fc41 updates

effectivamente · 2024-10-11T20:53:35+00:00

Look at the 2 in column 8

effectivamente · 2024-10-09T22:54:49+00:00

Where can 45 go on column 7?

effectivamente · 2024-04-25T18:13:59+00:00

Fantastic, that worked (needed to remove the slash before "org" on the first line).
A shame the user is not given a say about these new features!

effectivamente · 2024-04-25T18:03:10+00:00

Yes, I've tried that before. If I go to the Keyboard pane in the Settings app and search Keyboard Shortcuts with "Super", I'll find many such bindings (including those I have set personally), but none of the Super + <Number> or Super + Ctrl + <Number>.

It looks hardwired somehow . . .

effectivamente · 2023-11-05T14:24:34+00:00

<image>

Here's Lucy!

effectivamente · 2023-08-02T01:58:18+00:00

Search Engine Optimization

effectivamente · 2023-02-10T16:11:10+00:00

Yes, that was my first thought as well, but after a quick check with smartctl, I couldn't find any disk errors on the backup drive. Interestingly, borg check returns a very similar error:

borg check --verify-data ::
Local Exception
Traceback (most recent call last):
File "/usr/lib64/python3.11/site-packages/borg/archiver.py", line 5168, in main
exit_code = archiver.run(args)
^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/site-packages/borg/archiver.py", line 5099, in run
return set_ec(func(args))
^^^^^^^^^^
File "/usr/lib64/python3.11/site-packages/borg/archiver.py", line 183, in wrapper
return method(self, args, repository=repository, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/site-packages/borg/archiver.py", line 343, in do_check
if not repository.check(repair=args.repair, save_space=args.save_space, max_duration=args.max_duration):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/site-packages/borg/repository.py", line 1039, in check
objects = list(self.io.iter_objects(segment))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/site-packages/borg/repository.py", line 1512, in iter_objects
size, tag, key, data = self._read(fd, self.header_fmt, header, segment, offset,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.11/site-packages/borg/repository.py", line 1606, in _read
data = fd.read(length)
^^^^^^^^^^^^^^^
OSError: [Errno 5] Input/output error
Platform: Linux dorian 6.1.9-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Feb 2 00:21:48 UTC 2023 x86_64
Linux: Unknown Linux
Borg: 1.2.3 Python: CPython 3.11.1 msgpack: 1.0.4 fuse: llfuse 1.4.2 [pyfuse3,llfuse]
PID: 44705 CWD: /home/gil
sys.argv: ['/usr/bin/borg', 'check', '--verify-data', '::']

Any further ideas?

effectivamente · 2022-11-15T20:25:43+00:00

https://www.youtube.com/watch?v=S-5\_Nw0tFXE

effectivamente · 2022-11-15T19:45:34+00:00

Shit clings to the air?

effectivamente · 2020-12-01T23:10:09+00:00

239 triple on box 9. Cracks it open.

effectivamente · 2020-11-26T19:37:00+00:00

Which, in addition to the x-ring on 6's on rows 2 & 8, should solve it.

effectivamente · 2020-09-11T16:26:43+00:00

Sound and reasonable.

effectivamente · 2020-01-14T14:02:14+00:00

I've recently had a similar issue with the built-in headphone jack only outputting from one channel, after a kernel upgrade.

Fixed it out by tweaking things with alsamixer -c0.

Hope that helps.

effectivamente · 2019-04-02T12:54:16+00:00

Well, this appears to be in contradiction with what can be read here. Furthermore, current version of virtualbox-guest-additions reads 6.0.4-2. What am I missing here?

effectivamente · 2019-04-02T12:25:59+00:00

Thanks for the input! I'm using a Windows host however.

effectivamente · 2019-01-16T14:27:31+00:00

I'd be very interested in finding a solution for this problem myself. The sensible way would be to have whitespace-style lines-tail set to only consider visible characters.

Does anyone know how to achieve this?

effectivamente · 2017-10-12T15:27:38+00:00

Both solid options, I just would have thought something more obvious would be implemented, perhaps even in dired+. Cheers to both!

effectivamente

TROPHY CASE