FS#11414 - Duplicated dependencies on the home page (package details)

Attached to Project: Arch Linux
Opened by Nagy Gabor (combo) - Sunday, 07 September 2008, 12:29 GMT
Last edited by Dusty Phillips (Dusty) - Monday, 08 September 2008, 22:29 GMT
Task Type Bug Report
Category Web Sites
Status Closed
Assigned To Dusty Phillips (Dusty)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

If "foo" dependency of "bar" exists in more than one repos, "foo" is listed more than once among the dependencies of "bar".

Steps to reproduce:
Atm libgl is listed twice here: http://www.archlinux.org/packages/extra/i686/xawtv/ (libgl exists in both extra and testing)

See also:
http://archlinux.org/pipermail/arch-general/2008-September/018542.html
This task depends upon

Closed by  Dusty Phillips (Dusty)
Monday, 08 September 2008, 22:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  I chose to implement this in a way that only does the test and extra query when duplicates are found. I think this is marginally more optimal and more readable.
Comment by Henning Garus (garns) - Sunday, 07 September 2008, 14:26 GMT
Patch that should fix this, I'm not sure if it is the best way to do this, but I don't see a way to get around hard coding testing.
   0001-Fix-duplicated-dependenc... (1.9 KiB)
Comment by Aaron Griffin (phrakture) - Monday, 08 September 2008, 15:59 GMT
Hmm, rather than adding custom code for testing, perhaps we could do some sort of hierarchy thing... what I mean is something like:

repo_order = [ 'Core', 'Extra', 'Testing' ]

And then only use deps from the current repo or "above"/"before" it in the list. So extra can depend on core packages, but not the other way around. It makes more sense but may be harder

Either way, thanks for the patch!
Comment by Henning Garus (garns) - Monday, 08 September 2008, 16:19 GMT
I did think about something like that, it shouldn't be to difficult. However I'm not sure if it is useful to mark a dependency for a core package virtual, because it is in extra. This shouldn't happen in the first place.
The way I see it testing is a bit different, because only in testing are packages which have the same name as a package in another repo.
If I come up with a way to do this a bit more general, while keeping the number of queries low (unless I don't hava to ;) ) I will send a new patch.
Comment by Dusty Phillips (Dusty) - Monday, 08 September 2008, 16:23 GMT
Thanks for the patch! I think its probably the best method given the current infrastructure. In the long term, when I have time, I'm trying to think of a way to make packages less subservient to repos... so there wouldn't be separate packages in each repo but instead the package would be tracked along with its current version in one or more different repos and/or architectures. This would solve the problem here automatically but would also cause a lot of headaches in other places... and I"m running short on advil. :D

Loading...