Bug#379063: DDPO: include data about versions in Ubuntu
Package: qa.debian.org
Severity: wishlist
Hi,
A Debian Developer gave the following suggestion on
https://wiki.ubuntu.com/DCT (the homepage for Ubuntu's Debian
Collaboration Team) :
Something like the Debian QA Packages (developer.php) overview would be
immensely useful. What versions of "my packages" are where in Ubuntu,
who can see that the important bugfixes I just uploaded to Debian end
up in Ubuntu.
While I fully understand that some people will think that such a thing
has nothing to do on a debian.org service, I think that this information
should be integrated into the DDPO, because it's where it will be the
most useful for Debian maintainers interested in the status of their
packages in Ubuntu.
Of course, it doesn't have to be enabled by default, thus limiting the
flamewar potential of such a feature.
After discussing this a bit with Christoph Berg, here is how, ideally,
it would work :
- It would list the version of packages in both Ubuntu Dapper (stable
version) and Ubuntu Edgy (development version) (this will have to be
updated every 6 month)
- It would provide some links to the useful resources regarding the
packages in the ubuntu world (DD might have problems understanding
where to look to find some additional info).
Sources.gz files can be rsynced from archive.ubuntu.com::ubuntu/dists/
You'd need to fetch them for both dapper and edgy, and for all four
sections (main, restricted, universe, multiverse). The Ubuntu mirror
push happens every hour.
Relevant sources of information:
Launchpad page for each source package:
https://launchpad.net/distros/ubuntu/+source/feed2imap
Changelogs:
http://changelogs.ubuntu.com/changelogs/pool/universe/f/feed2imap/feed2imap_0.8-1/changelog
Patches:
There's an index on http://patches.ubuntu.com/PATCHES
example patch url:
http://patches.ubuntu.com/f/fam/fam_2.7.0-8ubuntu1.patch
Thank you,
--
| Lucas Nussbaum
| lucas@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr GPG: 1024D/023B3F4F |
Reply to: