FS#4116 - CVS link to testing packages broken
Attached to Project:
Arch Linux
Opened by Roman Kyrylych (Romashka) - Monday, 06 March 2006, 06:50 GMT
Last edited by eliott (cactus) - Wednesday, 27 February 2008, 03:21 GMT
Opened by Roman Kyrylych (Romashka) - Monday, 06 March 2006, 06:50 GMT
Last edited by eliott (cactus) - Wednesday, 27 February 2008, 03:21 GMT
|
This task depends upon
Closed by eliott (cactus)
Wednesday, 27 February 2008, 03:21 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed.
Wednesday, 27 February 2008, 03:21 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed.
This can be fixed when we redo the website, but it may be a little while. As for mkinitramfs, the problem will go away once it is introduced into Current, Extra, or Unstable.
Can I see the sources of web system? I can help to fix it while devs can work on more important tasks.
Right now I'm still developing new Arch and AUR site ("just for fun") in my free time. Maybe you'll like my work, when it's finished.
For example gtk2 in Testing has the following URL for CVS entry: http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/lib/gtk2/?cvsroot=Testing&only_with_tag=CURRENT
It is worng.
http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/system/dbus/?cvsroot=Current&only_with_tag=TESTING
Assume we have package foo. Foo is in current and testing.
For the web interface, foo has a package ID of 1334 in current, and a package ID of 1335 in testing.
Somebody clicks on http://www.archlinux.org/packages/1335/ in the web interface.
The web interface pulls the data from the database, and gets this.
package:
id = 1335
repo = Testing
maintainer = Mr.Awesome
category = Base
needupdate = False
pkgname = foo
pkgver = 1.0
pkgrel = 2
pkgdesc = Makes bar run better
url = http://house.ofbar.net
The problem is the 'repo' column in the database. This package has no meta belying its origin. If the package soley exists in testing, the problem is even worse (because there is no way we could just do a second query, get the non-testing package, and find out which repo *that one* is in).
If we only had one backend repository, then it would be a simple matter of hard coding the repo to something, and then adding the 'Testing' flag, but we don't have that luxury here.
I don't think this is fixable until we move to a different backend repository system.
If somebody has a good idea, or thinks they have a solution to the general case, let me know.
In the (hopefully) not too distant future, we will be moving to a different scm backend.
We will revisit this issue at that time if needed.
"""
If the package soley exists in testing, the problem is even worse (because there is no way we could just do a second query, get the non-testing package, and find out which repo *that one* is in).
"""
if package_name_also_in_non-testing_repo:
correct link!
else:
bad link :(
go us!