This affects me too (Ubuntu 26.04, Thunderbird & Firefox). Same underlying issue, different package: I had mozillateamppa pinned with Pin-Priority: 1001 for Thunderbird, correctly overriding the Ubuntu-provided snap wrapper for normal apt operations. Despite this, unattended-upgrades silently reinstalled the snap wrapper overnight, because its own version carries a higher epoch (2:1snap1-... vs 1:140.x...~mt1), which unattended-upgrades apparently evaluates independently of my pin-priority configuration.
The combination of (1) the artificially inflated epoch on the transitional snap package and (2) unattended-upgrades not respecting explicit pin-priority creates a scenario where a user's clearly stated package preference is silently overridden without any prompt or notification. This is functionally indistinguishable from an application reinstalling itself against explicit user configuration — behavior I associate with proprietary platforms, not with a Linux distribution. For users who specifically switched to Linux for the ability to control their own system, this is a significant trust issue, independent of any technical justification around origin-pinning implementation difficulty. I'd ask that this be reconsidered, or at minimum that unattended- upgrades warn/log clearly when a pinned-down package is about to be overridden by a higher-epoch package from an unpinned origin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079810 Title: unattended-upgrades doesn't respect repo pin-priority To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2079810/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
