FS#45709 - [packagekit] Updates disregard pacman.conf:IgnorePkg

Attached to Project: Community Packages
Opened by John-Michael Mulesa (jm2) - Sunday, 19 July 2015, 06:52 GMT
Last edited by Toolybird (Toolybird) - Saturday, 01 April 2023, 00:47 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description: When gnome-software is install an interface for automatic updates is installed as well, probably through packagekit. This automatic update procedure completely ignores held packages defined in IgnorePkg in pacman.conf and installs the latest version of these packages anyway.

Additional info:
* package version: 3.16.4-1


Steps to reproduce: Install gnome-software, add a package to IgnorePkg, watch gnome-software/packagekit update it anyway.
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 01 April 2023, 00:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  Seems to have been fixed a while back.
Comment by Doug Newgard (Scimmia) - Sunday, 19 July 2015, 13:17 GMT
You're not using pacman, why would it respect pacman.conf?
Comment by Jan Alexander Steffens (heftig) - Sunday, 19 July 2015, 13:36 GMT
I agree and consider this at most a feature parity problem in the packagekit stack. Not sure there's anything we can do here.
Comment by Christian Hesse (eworm) - Sunday, 19 July 2015, 19:38 GMT
Hmm, interesting...

gnome-packagekit lists packages from IgnorePkg as blocked updates. But even pkcon installes these packages...
Comment by John-Michael Mulesa (jm2) - Sunday, 19 July 2015, 19:43 GMT
@Doug: because as far as I'm aware, packagekit uses a pacman backend in order to actually install packages, and I would expect that to honor pacman.conf.
Comment by Christian Hesse (eworm) - Wednesday, 22 June 2016, 20:35 GMT
BTW, we have an upstream bug report about this...
https://github.com/hughsie/PackageKit/issues/71
Comment by Eli Schwartz (eschwartz) - Wednesday, 07 February 2018, 18:09 GMT
@jm2, it is not a "pacman" backend, it is a "libalpm" backend. The backend is responsible for making use of the configuration settings the libalpm parser gives it, and then requesting that libalpm install XXXX packages.

What is the status of this? @eworm, it looks you've authored some commits to packagekit's libalpm backend, would you be able to help them fix this? It looks like the upstream bug is going ignored...
Comment by Christian Hesse (eworm) - Wednesday, 07 February 2018, 20:31 GMT
I am aware of this bug, but did not find the spare time to look into this.
Comment by Carson Black (appadeia) - Tuesday, 31 March 2020, 01:21 GMT Comment by Carson Black (appadeia) - Sunday, 12 April 2020, 21:17 GMT
Fix landed.
Comment by bartus (bartus) - Thursday, 04 February 2021, 07:13 GMT
This broken sh.t just wasted my system configuration (`皿´#) Why this fix isn't in the community already ?

Loading...