Okay... Would you use a PPA with a never version of PK which does not
contain this issue? Cause I guess it will never be fixed in Lucid.
** Changed in: packagekit (Ubuntu)
Status: Fix Released => Confirmed
** Summary changed:
- Blocked updates still suggested for update
+ [lucid] Blocked
Hi Matthias, I am still running lucid 10.04 LTS with KDE 4.5.1, and kpackagekit
is still 0.5.4.
I don't know yet when I will upgrade to maverick.
--
Blocked updates still suggested for update
https://bugs.launchpad.net/bugs/501028
You received this bug notification because you are a member of Ub
Should be fixed in Maverick.
@Etienne: Does it work for you now?
** Changed in: packagekit (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
Blocked updates still suggested for update
https://bugs.launchpad.net/bugs/501028
You receive
** Tags removed: blocked packagekit upgrade
--
Blocked updates still suggested for update
https://bugs.launchpad.net/bugs/501028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
The upcoming packagekit 0.5.6 will use the same pinning file as
synaptic. But you can already setup pinning manually in the apt
configuration, see the man page of apt_preferences
--
Blocked updates still suggested for update
https://bugs.launchpad.net/bugs/501028
You received this bug notificatio
I do not know what follow up will be given to this, but I feel uncomfortable
that the GUI does not behave the same way as the "reference" apt-get does.
I do not know about packagekit-backend-apt, nor how it is related to apt-get.
All I know is that I could not find an option in kpackagekit to bloc
In the end we could parse the held packages from the status file and
skip them in the calculation of updates. But I am not sure how much
sense it makes to behave differently to apt itself.
--
Blocked updates still suggested for update
https://bugs.launchpad.net/bugs/501028
You received this bug n
Apt does use a different mechanism to hold packages. You have to use
pinning. The PackageKit backend of the 0.5 series uses the same pinning
information like Synaptic.
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: packagekit (Ubuntu)
Status: New =
