Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#13887 - Pacman downgrading with -Syu
Attached to Project:
Pacman
Opened by Andre Ramaciotti (andreramaciotti) - Friday, 20 March 2009, 15:12 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 20 March 2009, 18:24 GMT
Opened by Andre Ramaciotti (andreramaciotti) - Friday, 20 March 2009, 15:12 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 20 March 2009, 18:24 GMT
|
DetailsI turned on the testing repository so I could use the new xorg-server and the new intel driver, but I don't want to use testing for all my packages, so I left it in the end of my /etc/pacman.conf. The problem is that when I run pacman -Syu, I get:
:: Synchronizing package databases... core is up to date extra is up to date community is up to date testing is up to date :: Starting full system upgrade... warning: intel-dri: local (7.3-1) is newer than extra (7.2-2) warning: libgl: local (7.3-1) is newer than extra (7.2-1) warning: libsoup: local (2.25.4-1) is newer than extra (2.24.3-1) warning: liferea: local (1.5.14-1) is newer than extra (1.4.27-1) warning: mesa: local (7.3-2) is newer than extra (7.2-1) warning: xf86-input-evdev: local (2.1.3-1) is newer than extra (2.1.2-1) warning: xf86-input-keyboard: local (1.3.2-2) is newer than extra (1.3.2-1) warning: xf86-input-synaptics: local (1.0.99.2-1) is newer than extra (1.0.0-1) warning: xorg-server: local (1.6.0-1) is newer than extra (1.5.3-4) resolving dependencies... looking for inter-conflicts... error: failed to prepare transaction (could not satisfy dependencies) :: intel-dri: requires libdrm>=2.4.4 :: libgl: requires libdrm>=2.4.5 :: mesa: requires libdrm>=2.4.5 And if I try to -Syud, it says what packages would be upgraded: Targets (2): libdrm-2.3.1-3 xf86-video-intel-2.4.3-1 But this are the verions installed: libdrm 2.4.5-2 xf86-video-intel 2.6.99.902-1 Most packages of my local installation won't be 'upgraded' because pacman knows it's a newer version, but that's not what's happening with libdrm and xf86-video-intel. Pacman is version 3.2.2 and libalbpm is 3.1.1 |
This task depends upon
I don't know if this is exactly a pacman issue as it is a versioned dependency issue
I spected the warnings to appear because I am using packages which are newer than extra (and I want to keep them like this), but xf86-video-intel and libdrm don't appear in these warnings, even though they're newer than the version in extra (i.e. intel is 2.6.99.902-1 here but 2.4.3-1 in extra and libdrm is 2.4.5-2 here but 2.3.1-3 in extra). It seems to me pacman thinks 2.4.3-1 as newer version than 2.6.99.902-1 (maybe because the number of periods is different?)
What you're doing is unsupported. You're not supposed to pick-and-choose packages from testing like this
It's not a big problem to me, though. You can close this bug report if you like.
:: intel-dri: requires libdrm>=2.4.4
:: libgl: requires libdrm>=2.4.5
:: mesa: requires libdrm>=2.4.5
Wants to install: libdrm-2.3.1-3 xf86-video-intel-2.4.3-1
Currently installed: libdrm 2.4.5-2 xf86-video-intel 2.6.99.902-1
It looks like, for some reason or another pacman is saying "lets install these versions". I have a suspicion that these packages have options=(force) enabled....
And yes, they do. So what you're experiencing is expected, as option=(force) tells pacman to screw the version check. It's like saying "I don't care, this is an upgrade no matter what you say"
Seems like an unexpected side-effect in this case, but everything is, technically, working as intended