On Wed, Feb 9, 2022 at 6:05 PM Paul Wise <p...@debian.org> wrote: > On Wed, 2022-02-09 at 12:26 -0600, Judah Richardson wrote: > > > Fair. The package in Raspberry Pi OS lists you and someone else (I > > forgot the name, my apologies) as the maintainers. So either the > > Raspberry Pi OS' repo records are wrong, or the Foundation is simply > > using the upstream package as is. > > I'm not a maintainer of the unattended-upgrades package in Debian,
Yeah I think I may have gotten that wrong too. Sorry, too much going on this week. Michael Vogt is the maintainer. > so > that is surprising. I am just someone who uses unattended-upgrades and > didn't want your bug report to cause its removal from Debian bookworm, > since release-critical (Severity: serious and higher) bugs do that. > > I am assuming the RPi OS is using the unmodified Debian package. > Any issues could still be caused by the RPi OS apt repositories > though, since they could have other packages different to Debian and > apt/unattended-upgrades are very sensitive to dependency problems or > mismatches. Generally the recommendation when using a Debian based > distribution is to try and reproduce issues on plain Debian before > reporting a bug in Debian. The same applies to reporting directly to > the upstream projects that get packaged in Debian. > Fair. Getting support for distro repo packages that have upstream sources continues to be problematic. For one, it's not entirely clear where the problem lies or who is actually responsible. I had this problem a lot when I ran FreeBSD, whose repos include a lot of packages originally developed for Linux and ported over. While your suggestion to replicate the issue in Debian (the package works just fine on my Debian machine) makes sense, it's not practical to expect most users of a given distroB to also maintain an instance of upstream distroA purely for troubleshooting purposes. Again, none of this is anyone's fault *per se*, it's just an artifact of how open source computing works in general. Based on the output of the commands you pasted: > > The RPi OS is not using the Debian package of chromium, they have their > own package that is a fair bit older than the Debian package. > Thanks for the information! > > You don't have any pending package updates and therefore no possibility > of unattended-upgrade failures. So I think we can close the bug report. > Yeah I haven't had any error messages for a couple weeks now so apparently whatever the issue is has been cleared up. Thanks for your input! > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise >
