Re: How to re-upload a removed package?
On Wed, Dec 16, 2009 at 12:52 AM, Alejandro Rios wrote: > 1. Should I upload it to unstable or to proposed-updates? That depends on your intention. At the minimum, the security issue should be fixed in oldstable even though security support for it expires in February. For that you need to follow this procedure: http://www.debian.org/doc/developers-reference/pkgs.html#bug-security By uploading to unstable and more importantly maintaining the package in the future you ensure that destar will remain available in Debian and be available in future releases. > 2. If uploading to unstable, should I make other changes different from > those that are related to the security bugs (i.e. for lintian warnings, > standars version), or not? If you intend for the package to be available in future Debian releases, you should do some or all of the following: Clean up the package for lintian, policy, dh7, dpkg-source v3 etc. Get in contact with upstream (which seems to have become active again since destar was removed) to get the security issue fixed there and a new release made. If you have time you could also get involved in developing the software to ensure it does not get removed from Debian again. Contact the former maintainers of the Debian destar package - Debian VoIP Team - and ask them if they would be interested in maintaining it now that upstream is active again. If so you could join the team and help them maintain it in their SVN repository. If not, then you could maintain it yourself through sponsorship: http://people.debian.org/~mpalmer/debian-mentors_FAQ.html http://wiki.debian.org/SponsorChecklist When a package is removed from Debian, all the bugs are closed (by Marco Rodrigues). So you should look at the bug list (archived and non-archived) for destar and reopen the ones that are closed in version 0.2.2-5.2+rm, then try to get them fixed: http://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;src=destar Fix all the issues listed on the PTS page: http://packages.qa.debian.org/d/destar.html Ensure that the package will pass the NEW queue: http://ftp-master.debian.org/REJECT-FAQ.html Import the changes from the Ubuntu package: https://launchpad.net/ubuntu/+source/destar Look at the Ubuntu bugs too (inc closed ones): https://bugs.launchpad.net/ubuntu/+source/destar The next Debian/Ubuntu releases are quite soon so you'll need to do the above fairly quickly. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: How to re-upload a removed package?
Hello Holger OK, that's the same Anibal Monsalve told me, but when I was about to do it, two questions came up: 1. Should I upload it to unstable or to proposed-updates? 2. If uploading to unstable, should I make other changes different from those that are related to the security bugs (i.e. for lintian warnings, standars version), or not? Thanks again. Alejandro. 2009/12/15 Holger Levsen > Hi Alejandro, > > On Montag, 14. Dezember 2009, Alejandro Rios wrote: > > But I'm not sure of what to do with this package anymore, specially after > > it was already removed from unstable and testing, but not from > (old)stable, > > so some advice on this would be appreciated. > > Just bring the package back in shape, fix the reasons why it was removed > and > reupload it and have fun! > > > cheers, > Holger >
Re: How long does debtag information need to propagate to UDD
On Tue, Dec 15, 2009 at 11:38 PM, Andreas Tille wrote: > So my question is: How to track the path the information on the public > DebTags interface to UDD? I might try and read the code of the debtags > importer but my hope is somebody is able to give a quick answer and has > an idea who is really responsible (DebTags maintainers or UDD importer > or even somebody else) and how this can be fixed. IIRC the debtags admins (enrico) approve the changes and then they are automatically added to the Packages files in the archive. Presumably UDD then imports them from there. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
How long does debtag information need to propagate to UDD
Hi, as you might know I use UDD to display package information for Debian Pure Blends. I tried to get a reasonable tool to set DebTags for a set of packages which are used in a certain workfield (so called task). This is implemented by providing a yellow button for not yet tagged on pages like this http://debian-med.alioth.debian.org/tasks/epi Somewhen in October I tagged all these packages and the information is available in the DebTags database in the input interface. I do not have any information how the DebTags information is propagated to UDD but if it would be there the page above would show green buttons and a tooltip with the tags set. So my question is: How to track the path the information on the public DebTags interface to UDD? I might try and read the code of the debtags importer but my hope is somebody is able to give a quick answer and has an idea who is really responsible (DebTags maintainers or UDD importer or even somebody else) and how this can be fixed. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561228: VCS-CVS are converted to bogus hyperlinks
Package: qa.debian.org Severity: wishlist Lines of the form │Vcs-CVS: :ext:_anon...@anoncvs.mirbsd.org:/cvs contrib/hosted/tg/deb/makefs are converted to bogus hyperlinks of the form │http://packages.qa.debian.org/libb/:ext:_anoncvs%40anoncvs.mirbsd.org:/cvs%20contrib/hosted/tg/deb/libbsd-arc4random-perl which is wrong for a number of reasons. CVS specifications are not URIs, they consist of two parts, and the separator is important (i.e. the parts cannot possibly be easily concatenated), as it specifies the location of the root. So I suggest to not make hyperlinks out of VCS-CVS fields, but maybe display them as hover information. VCS-Browser, if existent, are fine though. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-6-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/mksh -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: How to re-upload a removed package?
Hi Alejandro, On Montag, 14. Dezember 2009, Alejandro Rios wrote: > But I'm not sure of what to do with this package anymore, specially after > it was already removed from unstable and testing, but not from (old)stable, > so some advice on this would be appreciated. Just bring the package back in shape, fix the reasons why it was removed and reupload it and have fun! cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#496490: Please investigate removal of adolc
Barak A. Pearlmutter (15/12/2009): > > even though Neil Williams tried to give him a hand. > > He did? I'd be happy to have a co-maintainer. He did: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496490#8 Mraw, KiBi. signature.asc Description: Digital signature
