Re: Remove a package?
On Wed, May 06, 2009 at 03:34:12AM +0700, Alexey Salmin wrote: Hello! Hi! At first I want to say that I'm not sure that this mailing list is a right place for my letter. Secondly, this letter isn't actually about some specific package, I'm just interested in understanding Debain policies. Is there any way to remove some package from debian distribution? For example: package bcrypt is completely dead. It doesn't work at amd64 at all because of obvious bug, which I've reported here (path included) half a year ago, but got no response. Last update of official site (http://bcrypt.sourceforge.net/) was in September 2002. This program doesn't work and has no support. Is there any reason to keep such packages? Packages can be removed if they aren't in good shape, upstream is dead, etc. Have you tried pinging bcr...@packages.debian.org? If you got no response after a reasonable time, the QA team will see if the maintainer is missing in action (adding them to CC, dropping -devel through BCC). If you'd like to see bcrypt stay in the archive, you could adopt the package upstream and also adopt the packaging, or another developer might be interested. If the current maintainer is MIA, the QA team might adopt the package themselves. (QA: I'll happily prepare an upload, but will need sponsorship.) Alexey -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Best, -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
Re: Remove a package?
On Wed, 6 May 2009 03:34:12 +0700 Alexey Salmin alexey.sal...@gmail.com wrote: CC'ing the maintainer. Hello! At first I want to say that I'm not sure that this mailing list is a right place for my letter. Secondly, this letter isn't actually about some specific package, I'm just interested in understanding Debain policies. http://www.uk.debian.org/Bugs/Reporting The pseudo-package you need is: ftp.debian.org — Problems with the FTP site (Although the pseudo-package description doesn't explicitly point at bugs that cause the removal of a package, checking the actual bug report page lists lots of RM bugs.) http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=ftp.debian.org;dist=unstable There is a particular syntax for such bug reports. Is there any way to remove some package from debian distribution? For example: package bcrypt is completely dead. It doesn't work at amd64 at all because of obvious bug, which I've reported here (path included) half a year ago, but got no response. Last update of official site (http://bcrypt.sourceforge.net/) was in September 2002. This program doesn't work and has no support. Is there any reason to keep such packages? Why remove it when it could be possible to prepare a fixed package, make it available via mentors.debian.net and get a sponsor to upload it as an Non-Maintainer Upload? If the package was fixed on amd64, would you still use it? The package seems quite popular: http://qa.debian.org/popcon.php?package=bcrypt Just because a package is old or dead upstream doesn't mean it is necessarily removable from Debian - there has to be a problem with the package on a release architecture (as there is on amd64 currently) or building from source or using an old lib like gtk1.2 etc. -- Neil Williams = http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/ pgpTNsy3xEEAG.pgp Description: PGP signature
Remove a package?
Hello! At first I want to say that I'm not sure that this mailing list is a right place for my letter. Secondly, this letter isn't actually about some specific package, I'm just interested in understanding Debain policies. Is there any way to remove some package from debian distribution? For example: package bcrypt is completely dead. It doesn't work at amd64 at all because of obvious bug, which I've reported here (path included) half a year ago, but got no response. Last update of official site (http://bcrypt.sourceforge.net/) was in September 2002. This program doesn't work and has no support. Is there any reason to keep such packages? Alexey -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Remove a package?
On Tue, May 5, 2009 at 4:51 PM, Neil Williams codeh...@debian.org wrote: Is there any way to remove some package from debian distribution? For example: package bcrypt is completely dead. It doesn't work at amd64 at all because of obvious bug, which I've reported here (path included) half a year ago, but got no response. Last update of official site (http://bcrypt.sourceforge.net/) was in September 2002. This program doesn't work and has no support. Is there any reason to keep such packages? I'll be attending to the bug no later than this weekend. Regards, Kevin -- Kevin Coyner GnuPG key: 1024D/8CE11941
[Ping] Packages-arch-specific: please remove iroffer package
Hi Ludovic, On Fri, Jul 21, 2006 at 10:03:56PM +0200, Ludovic Brenta wrote: It has been a week since I sent the request below, and I received no answer. I am resending to the three maintainers of Packages-arch-specific, and CCing debian-devel. I have the same issue with Packages-arch-specific for iroffer which builds on any architectures right now. Since you did not get any anwser and so do I, I post my desperate request with you. :) Pretty please, James or anyone having access to that file and wanna-build, could you remove the following line from it? iroffer: i386 sparc powerpc alpha # lacks config for other archs I think wanna-build use it to distribute the tasks to the buildds, because the package I adopted is never built on other architectures. Cheers, -- .''`. Aurélien GÉRÔME : :' : `. `'` Free Software Developer `- Unix Sys Net Admin signature.asc Description: Digital signature
Re: Proper way to remove a package from both sarge and sid
* Frederik Dannemare | Package in question is mozilla-firefox-locale-da which is to be replaced | by mozilla-firefox-locale-da-dk (not maintained by me) from source | package mozilla-firefox-locale-all. AFAIK, Danish is not spoken anywhere but in Denmark. Why do you want a m-f-l-da-dk rather than just a m-f-l-da ? (To ask a different question and not answering the one you had. :) -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Proper way to remove a package from both sarge and sid
Scripsit Tollef Fog Heen [EMAIL PROTECTED] * Frederik Dannemare | Package in question is mozilla-firefox-locale-da which is to be replaced | by mozilla-firefox-locale-da-dk (not maintained by me) from source | package mozilla-firefox-locale-all. AFAIK, Danish is not spoken anywhere but in Denmark. Why do you want a m-f-l-da-dk rather than just a m-f-l-da ? Hey, I speak Danish and I'm in Scotland. But seriously, I can see benefits of sticking to a common convention for naming localization packages; for example that might make it easier later to add some front end that would automatically add all localization packages for the current locale where I have the underlying software installed. -- Henning MakholmLigger Öresund stadig i Middelfart?
Re: Proper way to remove a package from both sarge and sid
On Friday 14 January 2005 17:08, Tollef Fog Heen wrote: * Frederik Dannemare | Package in question is mozilla-firefox-locale-da which is to be | replaced by mozilla-firefox-locale-da-dk (not maintained by me) | from source package mozilla-firefox-locale-all. AFAIK, Danish is not spoken anywhere but in Denmark. Why do you want a m-f-l-da-dk rather than just a m-f-l-da ? [ ... ] Well, I don't know. You'd have to ask the maintainer of ..-da-dk. I only did the ..-dk package before mozilla-firefox-locale-all arrived. -- Frederik Dannemare | mailto:[EMAIL PROTECTED] http://qa.debian.org/developer.php?login=Frederik+Dannemare http://frederik.dannemare.net | http://www.linuxworlddomination.dk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Proper way to remove a package from both sarge and sid
On Thu, 13 Jan 2005, Vincent Danjean wrote: Santiago Vila wrote: Instead of that, I would upload a new version of mozilla-firefox-locale-da which is empty and has a Depends: mozilla-firefox-locale-da-dk, i.e. a dummy package. Put in section oldlibs and then deborphan will tell you that you can remove it safely. Then no conflict would be needed (well, a versioned one perhaps), and there would not be so much hurry in removing the package, as you will be helping users of the old package to install the new one. No, it would not be enough. Some people can try to install the new -da-dk package with your old -da package already present. Even if people upgrade your package at the same time, there is no evidence that dpkg will upgrade the -da package before installing the -da-dk package. A conflict/replace on -da in the new -da-dk package is the (only ?) good thing to do I agree that the new -da-dk package needs a versioned Replaces on all the non-dummy versions of -da (that's why I said a versioned one perhaps) but there is not an absolute need to conflict with it. Your dummy package is only useful to force users to switch to the new -da-dk package on upgrade. In this case, the conflict/replace in -da-dk should be versionned. No, if a dummy package exists then there should not be a Conflicts, only a Replaces. The upgrade will be smoother if deborphan and section: oldlibs takes care of removing the old -da package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Proper way to remove a package from both sarge and sid
Hi Martin On Tuesday 11 January 2005 21:40, Martin Zobel-Helas wrote: Hi Frederik, On Tuesday, 11 Jan 2005, you wrote: BTW, what does RoM and RoQA mean? RoM: Request of Maintainer RoQA: Request of QA Group Thanks, bug report sent away with subject of RM: mozilla-firefox-locale-da -- RoM; replacement available, replacement collides with this one P.S.: Please include the list on replies. Best regards, -- Frederik Dannemare | mailto:[EMAIL PROTECTED] http://qa.debian.org/developer.php?login=Frederik+Dannemare http://frederik.dannemare.net | http://www.linuxworlddomination.dk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How to remove a package from ftp.debian.org?
Subject says it all. Do I have to file a bug against ftp.debian.org? Michael -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
Re: How to remove a package from ftp.debian.org?
Previously Michael Meskes wrote: Subject says it all. Do I have to file a bug against ftp.debian.org? Yes, magic wands have not been perfected yet :) Wichert. -- / Generally uninteresting signature - ignore at your convenience \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Re: How to remove a package from ftp.debian.org?
Michael Meskes [EMAIL PROTECTED] writes: Subject says it all. Do I have to file a bug against ftp.debian.org? Yes. Ciao Racke -- Tech beats design - hold your breath for Bhttp://fuckdotcom.de/B For projects and other business stuff please refer to COBOLT NetServices (URL: http://www.cobolt.net; Email: [EMAIL PROTECTED]; Phone: 0041-1-3884400)
Re: How to remove a package from ftp.debian.org?
Michael Meskes wrote: Subject says it all. Do I have to file a bug against ftp.debian.org? Yes.
Re: How to remove a package from ftp.debian.org?
Fri, Apr 27, 2001 at 04:52:58PM +0200 wrote: Subject says it all. Do I have to file a bug against ftp.debian.org? yes http://www.debian.org/doc/developers-reference/ch-archive-manip.en.html#s-removing-pkgs David P.S. this sort of question can probably be best asked on -mentors. Michael -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
