[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #20643 [Internal Services/Service - deb.tpo]: make and maintain a registry of what debs are on deb.tp.o and why
#20643: make and maintain a registry of what debs are on deb.tp.o and why
-------------------------------------------------+-------------------------
Reporter: arma | Owner: hiro
Type: task | Status:
| assigned
Priority: Medium | Milestone:
Component: Internal Services/Service - deb.tpo | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by irl):
I started having a go at this before I knew there was a ticket. Some ideas
that I've had regarding this:
* I like the view provided by DDPO (e.g.
https://qa.debian.org/developer.php?login=irl)
* I'd like to be able to compare to the versions in the corresponding
Debian/Ubuntu suites
* I'd like to see the results of uscan to see when the package needs
updating to a new upstream (can be the results of the Debian package's
uscan provided by Debian)
* The packages on deb.tpo are listed nicely in the Sources.gz file for
each suite, you can read these files with deb822 (in python-debian on
Debian systems)
* A single HTML table is really all that's required here
* We could have a policy of having an extra Maintainer line in the
control files that ends up in the Sources.gz to keep track of who is the
maintainer for each package, depending on what the archive software
supports (I think Ubuntu does this to differentiate the Ubuntu maintainer
from the Debian maintainer)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20643#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs