What really confuses me is that 2.5.33-1ubuntu2 (the version we're
trying to upgrade *from*) has the exact same underlying issue:
```
$ diff -urNw
libgphoto2-6t64_2.5.33-1ubuntu2_*.deb.unpacked/usr/lib/udev/rules.d/60-libgphoto2-6t64.rules
---
libgphoto2-6t64_2.5.33-1ubuntu2_amd64.deb.unpacked/usr/lib/udev/rules.d/60-libgphoto2-6t64.rules
2026-07-15 09:34:49.000000000 -0700
+++
libgphoto2-6t64_2.5.33-1ubuntu2_i386.deb.unpacked/usr/lib/udev/rules.d/60-libgphoto2-6t64.rules
2026-07-15 09:34:49.000000000 -0700
@@ -1,7 +1,7 @@
# udev rules file for libgphoto2 devices (for udev 201 version)
# Created from this library:
-# libgphoto2 2.5.33 standard camlibs, x86_64-linux-gnu-gcc, no
ltdl, EXIF
-# libgphoto2_port 0.12.2 iolibs: disk ptpip serial usb1
usbdiskdirect usbscsi, x86_64-linux-gnu-gcc, no ltdl, EXIF, USB, serial without
locking
+# libgphoto2 2.5.33 standard camlibs, i686-linux-gnu-gcc, no
ltdl, EXIF
+# libgphoto2_port 0.12.2 iolibs: disk ptpip serial usb1
usbdiskdirect usbscsi, i686-linux-gnu-gcc, no ltdl, EXIF, USB, serial without
locking
#
# this file is autogenerated, local changes will be LOST on upgrades
ACTION!="add|bind", GOTO="libgphoto2_rules_end"
```
...yet, dpkg didn't make a fuss about it when they were getting
installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2173989
Title:
libgphoto2-6t64: multi-arch conflict on
/usr/lib/udev/rules.d/60-libgphoto2-6t64.rules breaks upgrades on
systems with :i386 installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/2173989/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs