Pacman

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.
Tasklist

FS#7613 - Pacman and local repositories

Attached to Project: Pacman
Opened by Johannes Schriewer (dunkelstern) - Saturday, 14 July 2007, 00:10 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 16 July 2007, 07:32 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity High
Priority Normal
Reported Version 3.0.5
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
If you have local repositories in pacman.conf (those with a file:// prefix instead of http or ftp) pacman doesn't do package updates of these repositories.
Found this bug while testing an update for kpacupdate.

Steps to Reproduce:
1. Add a local repo to your pacman.conf
2. Take any PKGBUILD of a package you have installed already
3. Increase the pkgrel, build and place the package in your repository
4. Run gensync on your repository
5. Do a pacman -Sy
6. pacman "downloads" the new description file (some weird transfer rates are displayed btw.)
7. Do a pacman -Su
8. The updated package is not displayed for update
9. Do a pacman -S <your_package>
10. The package from one of the official repos (the online ones) is seen as the newest package and pacman tells you that your package is up to date and if you really want to upgrade.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Monday, 16 July 2007, 07:32 GMT
Reason for closing:  Not a bug
Comment by Johannes Schriewer (dunkelstern) - Saturday, 14 July 2007, 03:08 GMT
Well i've seen this effect on online repos too.

See this:
root@crystal64# pacman -Ss xmms
current/xmms 1.2.10-8
The X MultiMedia System
community/xmms 1.2.10-9
The X MultiMedia System

And no update is presented on -Su:
root@crystal64# pacman -Syu
:: Synchronizing package databases...
testing is up to date
current is up to date
extra is up to date
unstable is up to date
community is up to date
kdemod is up to date
:: Starting full system upgrade...
resolving dependencies... done.
looking for inter-conflicts... done.

Targets: bluez-libs-3.12-1 bluez-utils-3.12-1

Total Package Size: 0.38 MB

Proceed with installation? [Y/n]

Comment by Roman Kyrylych (Romashka) - Sunday, 15 July 2007, 12:09 GMT
About the original report: are you sure you have your repo _above_ the official repos in your pacman.conf? ;-)
Comment by Dan McGee (toofishes) - Sunday, 15 July 2007, 13:33 GMT
Roman probably hit the nail on the head here...I have zero problem with this for my local repo. He definitely did in the case posted above in the comments, as you can see current is above community in the repo updating. Once a package has been found in one repo, it is ignored in the rest even if the version number is higher.

On a side note, try using repo-add to generate your repo. And "weird download rates" are just local transfer rates- does it really matter what they say?
Comment by Roman Kyrylych (Romashka) - Sunday, 15 July 2007, 14:41 GMT
I'm not a native English speaker, so I'm not 100% sure what "hit the nail on the head" means exactly :P
Sure I have zero problems with this as well. :) Just wanted to hear Johannes' reply.
Comment by Dan McGee (toofishes) - Sunday, 15 July 2007, 14:47 GMT
I'm sorry about that- using idioms a bit early in the morning. It means "got something exactly right".
Comment by Johannes Schriewer (dunkelstern) - Monday, 16 July 2007, 00:29 GMT
Well if the order matters, it should be stated anywhere, for sure it is stated that pacman searches the repos in specified order, but that doesn't imply that updates are only done if they are in right order or don't i get it right?

If you update explicitly to the newer version of another repo and do an update later on pacman outputs this:
[dark64@crystal64 ~]$ sudo pacman -Su
:: Starting full system upgrade...
warning: xmms: local (1.2.10-9) is newer than current (1.2.10-8)
[dark64@crystal64 ~]$ pacman -Si community/xmms
Repository : community
Name : xmms
Version : 1.2.10-9
...

For sure the statement is right, but it is the current version of community. It's completely unneccessary to explicitly state that.
I think pacman should check the correct repository before stating that.

About the weird download rates: I know that but the display is weird (therefore I didn't open a bugreport for it :) )

Perhaps someone could add a switch to do a cross repository update? I mean don't stop searching as it may cause problems on the one side, for sure it can cause problems the other way round too (i.e. If i want MY package and not that from community...)

Perhaps it just was a bit late that evening and I didn't get it. Sorry about that.
Comment by Dan McGee (toofishes) - Monday, 16 July 2007, 00:44 GMT
from 'man pacman.conf':

The order of repositories in the file matters; repositories listed
first will take precedence over those listed later in the file when
packages in two repositories have identical names, regardless of ver-
sion number.
Comment by Roman Kyrylych (Romashka) - Monday, 16 July 2007, 07:31 GMT
The current pacman behaviour is fine IMO.
If you want your packages to always take precedence - just put your local repo on top.
BTW, that's why [testing] is above [current]

P.S.: xmms was removed from current looong time ago. ;-)

Loading...