Your message dated Tue, 11 Mar 2025 10:50:26 +0000
with message-id <[email protected]>
and subject line Bug#1092279: fixed in rpi.gpio 0.7.1~a4-1.2
has caused the Debian Bug report #1092279,
regarding rpi.gpio-common: /usr/lib/udev/rules.d/60-rpi.gpio-common.rules may
get lost in upgrade due to /usr-move (DEP17)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1092279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092279
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rpi.gpio-common
Version: 0.7.1~a4-1.1
Severity: serious
Justification: file loss in upgrade
Tags: trixie sid
User: [email protected]
Usertags: dep17p7
User: [email protected]
Usertags: armel armhf arm64
X-Debbugs-Cc: [email protected]
In an an upgrade from bookworm to trixie, rpi.gpio-common may loose
/usr/lib/udev/rules.d/60-rpi.gpio-common.rules, because it is a file
shared in a Multi-Arch: same package and being moved from /lib to
/usr/lib during the upgrade. For more information refer to
https://subdivi.de/~helmut/dep17.html section P7.
As I was wondering about a good way to fix this, I failed to find a
reason for rpi.gpio-common to exist as a separate package from
python3-rpi.gpio. I was made aware that there formerly was a Python 2
package that would benefit from a -common package sharing the udev rules
file, but now no such package exists anymore. This leaves the question
of whether you would prefer keeping (and fixing) the rpi.gpio-common
package or merging its content into python3-rpi.gpio (thus reducing the
number of packages in the archive for good).
In case you want to keep rpi.gpio-common, allow me to suggest dropping
Multi-Arch: same for one release. You cannot actually coinstall
python3-rpi.gpio, so coinstalling rpi.gpio-common is of very limited
use. I guess that the Multi-Arch hinter opportunistically suggested
adding Multi-Arch: same, but here it is one precondition to actually
loosing the file. A very simple way of working around the problem at
hand could be:
-Multi-Arch: same
+# begin-remove-after: released:trixie
+# Avoid being Multi-Arch: same for the trixie upgrade to avoid a DEP17
+# P7 file loss of the udev fules file being moved from /lib to /usr/lib.
+Multi-Arch: no
+# end-remove-after
I offer writing a patch (including the workarounds for the /usr-move)
for the other ways. Please let me know if you want to accept my offer
and indicate which path you prefer.
Helmut
--- End Message ---
--- Begin Message ---
Source: rpi.gpio
Source-Version: 0.7.1~a4-1.2
Done: Chris Hofstaedtler <[email protected]>
We believe that the bug you reported is fixed in the latest version of
rpi.gpio, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Hofstaedtler <[email protected]> (supplier of updated rpi.gpio package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 06 Mar 2025 10:55:03 +0100
Source: rpi.gpio
Architecture: source
Version: 0.7.1~a4-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Raspberry Pi Maintainers
<[email protected]>
Changed-By: Chris Hofstaedtler <[email protected]>
Closes: 1092279
Changes:
rpi.gpio (0.7.1~a4-1.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Disable Multi-Arch: same for trixie to avoid DEP17 file loss.
Minimal workaround as suggested by Helmut Grohne <[email protected]>.
(Closes: #1092279)
Checksums-Sha1:
c990023426766a7f793ef9e290b8e7271dec524a 2273 rpi.gpio_0.7.1~a4-1.2.dsc
8982ac54cc4df4c4e59164e68d9b0cf77578a907 3292
rpi.gpio_0.7.1~a4-1.2.debian.tar.xz
Checksums-Sha256:
92ec946bf80ba2b624e40d7d881bf9a50fa75f552765c2cc6203c277a7983299 2273
rpi.gpio_0.7.1~a4-1.2.dsc
6eb5585548c86e2b11d115bc46adee1c194cc9fa4ed9fae1f16431c250e043d8 3292
rpi.gpio_0.7.1~a4-1.2.debian.tar.xz
Files:
488bc07a298e4b7ed4102bc02b2093f6 2273 python optional rpi.gpio_0.7.1~a4-1.2.dsc
5093a18d8ec91eccdb93d99f166eab8f 3292 python optional
rpi.gpio_0.7.1~a4-1.2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmfJcWoACgkQXBPW25MF
LgNM4w/+INNl2cUE7ol8KX26tRFxowwWn1aMpUJ+l46vhaSIjWcmS2y08f4p+Zwl
vJynp5eA2C2/CvBsJ32QjTC7WDo4QSY/5bWhLLD3Z/3bU8jwTEtI2orxm0bwrhXA
aIIBmkhiPFi4bFZh42mXnpGdegPXXkmaGqusaLuDaaUzcFRnn7wL4i0oxaKGiUB7
b52HBAbcBXSbQRUEwJFtyvThCXGlXSTQ91XJmcfQievXgDicK5NOhegkN8iukwPV
bfg6mGiQo/Sqdh9Cs4sZ6MtilQ7ebF2PxFFo6AtZB951WvmPk8ed+LvGlUkkYC9t
JTGQWZoD09+QqQDG6nqwq0LkUdmDVW0sdYoRSDer8Auppun82wl38x+zMLfxpH1y
UXR+rZtg4J/bZP+C9R/7o57mC6a520kjkjcyV2Eh7DkbUEz8WHAI3duaPR2PEyC2
W7NSdTCueXsDZN5Bf8acBZQwdnnVIgeWHhIKl4uK32PFJ8znRIi4j9WMIopoA7H5
6ft3090hoH2iv7SiuZJfWQq5ivoDE030yTqGqV/p5nmCSNifvlZ1qyCplDs8ffwQ
ehGPSbYAlp9EHGh+ncbXRZ8PUM5O9jMCwWVshTeEEZCRtTGpYgQTKhNRUTjFNYdC
2cANObfVhX3YNr5rmVQD9TWcWdrFjdbFGpOlXA5+tV9cMHgqyyc=
=J7Ul
-----END PGP SIGNATURE-----
pgpjcjj7wTdP4.pgp
Description: PGP signature
--- End Message ---
