Bug 387744 - Plasma Discover doesn't honour pinned packages
Summary: Plasma Discover doesn't honour pinned packages
Status: RESOLVED NOT A BUG
Alias: None
Product: Discover
Classification: Applications
Component: PackageKit (show other bugs)
Version: 5.10.5
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-09 15:12 UTC by tomhutter
Modified: 2018-02-14 15:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tomhutter 2017-12-09 15:12:37 UTC
To use firefox 57.1 from Debian/sid, I have set up apt pinning to restrict all packages except firefox to Debian/buster:

Package: *
Pin: release o=Debian,a=buster
Pin-Priority: 900

Package: firefox
Pin: release o=Debian,a=sid
Pin-Priority: 1000

While aptitude shows me no packages to update, Plasma Discover shows all newer packages from sid as upgradable.
Comment 1 Nate Graham 2017-12-09 17:24:34 UTC
Discover interacts with PackageKit, and doesn't touch apt directly. So it's likely that this is an upstream PackageKit feature request, but I'll let Aleix make that determination.
Comment 2 Aleix Pol 2017-12-11 13:18:29 UTC
Can you please confirm that "pkcon get-updates" does the right thing?
Comment 3 Nate Graham 2017-12-11 14:07:48 UTC
tomhutter, please provide the requested info so we can continue to triage the bug. Thanks!
Comment 4 tomhutter 2017-12-11 23:02:29 UTC
I have apt pinning still intact:

$ cat /etc/apt/preferences.d/firefox.pref
Package: *
Pin: release o=Debian,a=buster
Pin-Priority: 900

Package: firefox
Pin: release o=Debian,a=sid
Pin-Priority: 1000


Now I disabled the sid repo:

$ cat /etc/apt/sources.list.d/sid.list
#deb http://debian.mirror.iphh.net/debian/ sid contrib non-free main

$ apt-get update
$ apt-get -s dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ pkcon get-updates
Getting updates               [=========================]
Loading cache                 [=========================]
Finished                      [=========================]
There are no updates available at this time.

Then I reenabled the sid repo:

$ cat /etc/apt/sources.list.d/sid.list
deb http://debian.mirror.iphh.net/debian/ sid contrib non-free main

$ apt-get update
$ apt-get -s dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ pkcon get-updates                      
Getting updates               [=========================]         
Loading cache                 [=========================]         
Finished                      [=========================]         
Normal          apparmor-2.11.1-4.amd64 (debian-unstable-main)                  user-space parser utility for AppArmor
Normal          apparmor-notify-2.11.1-4.all (debian-unstable-main)             AppArmor notification system
Normal          apparmor-profiles-2.11.1-4.all (debian-unstable-main)           profiles for AppArmor Security policies
Normal          at-spi2-core-2.26.2-2.amd64 (debian-unstable-main)              Assistive Technology Service Provider Interface (dbus core)
....

$pkcon get-updates | grep "^Normal" | wc -l
134
Comment 5 Aleix Pol 2017-12-28 19:33:44 UTC
Will have to test.
https://help.ubuntu.com/community/PinningHowto
Comment 6 Aleix Pol 2018-01-08 16:21:09 UTC
I've been testing with "apt-mark hold" and "apt-mark unhold". It's worked properly so far.

I've seen you mentioned aptitude, does "apt dist-upgrade" have the same behaviour there as well?
Comment 7 Aleix Pol 2018-01-16 16:56:07 UTC
We need more information to continue investigating this issue.
Comment 8 Christoph Feck 2018-01-30 00:49:36 UTC
If you can provide the information requested in comment #6, please add it.
Comment 9 Christoph Feck 2018-02-14 15:22:02 UTC
No response; changing status. If you have new information, please add a comment.