Re: Adopting a package
Thank you very much, both of you. I've been reading up on a lot of the documentation, but still have a ways to go. Links are always helpful. :) Best regards, Brian On June 14, 2021, Andrey Rahmatullin wrote: > On Tue, Jun 15, 2021 at 03:30:41AM -0500, Brian Thompson wrote: > > What is the typical way one would go about adopting a package? > If you mean an orphaned one, just upload it with you as the > maintainer, in > addition to the O bug management described at > https://www.debian.org/devel/wnpp/#l3 > > > I've heard that writing a patch and proposing it might be a good > >starting point. > Proposing it where? Orphaned packages don't have a maintainer so maybe > you > confused that with something else. > > -- > WBR, wRAR
Re: Adopting a package
On Tue, Jun 15, 2021 at 03:30:41AM -0500, Brian Thompson wrote: > What is the typical way one would go about adopting a package? If you mean an orphaned one, just upload it with you as the maintainer, in addition to the O bug management described at https://www.debian.org/devel/wnpp/#l3 > I've heard that writing a patch and proposing it might be a good >starting point. Proposing it where? Orphaned packages don't have a maintainer so maybe you confused that with something else. -- WBR, wRAR signature.asc Description: PGP signature
Re: Adopting a package
Hi Brian, thanks for offering to take over an important package. On Tue, Jun 15, 2021 at 03:30:41AM -0500, Brian Thompson wrote: > What is the typical way one would go about adopting a package? I've > heard that writing a patch and proposing it might be a good starting > point. Specifically, I am looking at apt-listchanges. The Developer's reference Chapter 5.9.5 (https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#adopting-a-package; points to the WNPP Web Pages (https://www.debian.org/devel/wnpp/) which describe the processes. If you have any more questions, please by all means come back and ask. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Adopting a package
What is the typical way one would go about adopting a package? I've heard that writing a patch and proposing it might be a good starting point. Specifically, I am looking at apt-listchanges. Best regards, Brian
Adopting orphan package: arpwatch -- Ethernet/FDDI station activity monitor
Hello, This is my first e-mail to the debian-mentor list. I have been a Debian user for 15 years and sysop for the past 10 years, and would like to help out with package maintenance for this great community. I have found that the arpwatch package has been orphaned for more than a 905 days now, and would like to adopt it. This would be my first package and the first endeavour into helping out in any way, so I'm looking for pointers in the right direction. Orphan bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686996 As you can see there has been some interest in adopting it, but none of those people has accepted it. I've been doing local packages for my own systems for the past years, and I've been reading the maintenance guides for that. So if I understand the developer's manual correctly, I would need a sponsor for proxying the maintenance of this package. If and when I get a sponsor, I would send my updates to that person for QA and final upload to the repository. Am I correct? If not, please help me figure this out :-) Best of wishes, -- kchr |_|O|_| |_|_|O| Kim Christensen |O|O|O| http://technopragmatics.org - () ascii ribbon campain - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: Digital signature
Re: Adopting orphan package: arpwatch -- Ethernet/FDDI station activity monitor
Hi Kim, On 03/04/2015 05:17 PM, Kim Christensen wrote: I have found that the arpwatch package has been orphaned for more than a 905 days now, and would like to adopt it. This would be my first package and the first endeavour into helping out in any way, so I'm looking for pointers in the right direction. Orphan bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686996 As you can see there has been some interest in adopting it, but none of those people has accepted it. I've been doing local packages for my own systems for the past years, and I've been reading the maintenance guides for that. Sounds like your first step should be to state your intention to adopt on that bug report. Lucas gives good instructions how to do that in the lest entry on the bug. So if I understand the developer's manual correctly, I would need a sponsor for proxying the maintenance of this package. If and when I get a sponsor, I would send my updates to that person for QA and final upload to the repository. Am I correct? If not, please help me figure this out :-) That's pretty much how it goes. The best thing is to pull together the package, and when you think it is ready, upload it to mentors.debian.net. Ask for some reviews for your package on this list, and you should receive comments to help improve it. Once you have a positive review, create a RFS bug (Request For Sponsor), and hopefully a sponsor will offer to work with you and do an upload. See here for more help on the process: https://mentors.debian.net/intro-maintainers Regards, Ross signature.asc Description: OpenPGP digital signature
Adopting a package
Can someone help me on the steps to follow for adopting a package at debian? Thanks and best regards, Mario Trangoni
Re: Adopting a package
On Fri, Aug 16, 2013 at 08:46:49PM +0200, Mario Trangoni wrote: Can someone help me on the steps to follow for adopting a package at debian? http://www.debian.org/devel/wnpp/ http://www.debian.org/doc/manuals/developers-reference/pkgs.html#adopting -- WBR, wRAR signature.asc Description: Digital signature
adopting a package
I am adopting an orphaned package (ircii), I have changed the title to ITA, and I have also changed the owner using cont...@bugs.debian.org. As the last package built was from 2008, I have started work on building the 2011 version, patching the build system etc. I also have an account on mentors.debian.org. Do I have to find a sponsor for this package? How do I proceed? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110907103714.GA26683@darkness
Re: adopting a package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Shaun, thanks for your interest to help Debian. On 07.09.2011 12:37, Shaun Silk wrote: Do I have to find a sponsor for this package? How do I proceed? Yes, you need a sponsor. Please read [1][2] to get the idea. You may also find the New Maintainer's Guide helpful [3]. [1] http://mentors.debian.net/intro-maintainers [2] http://wiki.debian.org/SponsoredMaintainer [3] http://www.debian.org/doc/manuals/maint-guide/ - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOZ36LAAoJEMcrUe6dgPNtwTgQALRIm4nE1wMHBpYC7TyAbOUl qAA9Qqhn+PIJL18VZ0vUm9TiVcsSxJBLZPVWTi1uW6N81kr5tlt9WO2MjaBPay9g V7lwO67yhbjfY5bLPCkreTfxVYCsTvkbWXldOsg8XjnY4BAbv0wsEI8FQFsYGM8b JXJHiJfurJ4VqC0E4QeLVMZSs5FuZj41meUkl1+jzP1m2dbOj5sZa2fAs2EERzRo b7QhGbr34+k3nydh9oaAuU346nRyI3lMKp/hif4ADuXBpdt4scQLLILnB2p+/er9 rn/yRbcgheMyZUkukLPdj7ZMg+A5cMGPPkfgxs4HQRJUllHqFFL3CB0qhjQK4uU9 PcWI5DohJinWO/0TOTor+qPQD5XjUBql4xAU9sWhFul8LipljluOyQlqSXBDHBiR hyNhh6HGHCfXyzW/tEmvb6QjlPmcl2apL+7dYsWnRg0Cj+Ss+CpH60XYWPWSusoP 54V6JkjWjpZpdHLJ1P7ccfqnjl2NNaNE1WWXz2LgQEaHthuMtGRyLGe3tyDka1al imR9N16ZUc3UNiLc36ZZXKmVp4jFJquHHPb6UdWdK2s47OLIw5UCp8wcIlQrJcoP zj6uQTmHXuKhR98a6yXU/1Z2mj06HbcR2M/HllCLtOVWMrogmP3NV0KsKY8BO1vz FPaPn4php+y2iFQU3PE/ =aqky -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e677e8c.6090...@toell.net
Re: RFS: gdmap (adopting, updated package)
Dear mentors, On Sun, 13 Mar 2011 21:43:39 +0100, Stephen Kitt st...@sk2.org wrote: I am looking for a sponsor for the new version 0.8.1-2 of my package gdmap. It builds these binary packages: gdmap - Tool to visualize diskspace The package appears to be lintian clean. The upload would fix these bugs: 579043, 594406 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gdmap - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gdmap/gdmap_0.8.1-2.dsc I would be glad if someone uploaded this package for me. Kind regards Stephen Kitt I'm still looking for a sponsor, I would grately appreciate it if someone could take a look at this package. Best regards, Stephen signature.asc Description: PGP signature
RFS: gdmap (adopting, updated package)
Dear mentors, I am looking for a sponsor for the new version 0.8.1-2 of my package gdmap. It builds these binary packages: gdmap - Tool to visualize diskspace The package appears to be lintian clean. The upload would fix these bugs: 579043, 594406 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gdmap - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gdmap/gdmap_0.8.1-2.dsc I would be glad if someone uploaded this package for me. Kind regards Stephen Kitt signature.asc Description: Digital signature
Re: RFS: pgn-extract (adopting orphaned package)
At Mon, 4 Jan 2010 21:54:20 +0100, Vincent Legout wrote: On Mon, Jan 04, 2010 at 05:25:38PM -0200, Nelson A. de Oliveira wrote : Hi! On Mon, Jan 4, 2010 at 5:11 PM, Christoph Egger christ...@debian.org wrote: Looking at it currently. However your watchfile seems to be dysfunctional, otherwise the package looks fine to me. (...) % uscan --report-status Useless content call in void context at /usr/share/perl5/LWP/Protocol/ftp.pm line 378 uscan warning: In watchfile debian/watch, reading FTP directory ftp://ftp.cs.kent.ac.uk/pub/djb/Extract/ failed: 400 FTP return code 000 Actually it works: $ uscan --report-status Processing watchfile line for package pgn-extract... Newest version on remote site is 16-7, local version is 16.7 pgn-extract: remote site does not even have current version Maybe this problem is caused by using/missing the PASV mode of FTP. See the uscan manpage for PASV. An improvement could be made on the watch file however (replace the dash by a dot): version=3 opts=uversionmangle=s/-/./ \ ftp://ftp.cs.kent.ac.uk/pub/djb/Extract/pgn-extract-(.*)\.tgz $ uscan --report-status Processing watchfile line for package pgn-extract... Newest version on remote site is 16.7, local version is 16.7 = Package is up to date Thanks Christoph and Nelson. I think Nelson is right, I've updated the watch file. http://mentors.debian.net/debian/pool/main/p/pgn-extract/pgn-extract_16.7-1.dsc Best Regards, Vincent Hm strange. uscan still fails for me on my local computer as well as on my sheeva plug but works fine on ravel.d.o I'll need a closer look here on my side I guess. Anyway as the package was already fine for me and the watchfile is improved now I've uploaded it. Regards Christoph pgpN5aMLBMRR4.pgp Description: PGP signature
Re: RFS: pgn-extract (adopting orphaned package)
Hi! At Sun, 3 Jan 2010 11:40:03 +0100, Vincent Legout wrote: Dear mentors, I am looking for a sponsor for the new version 16.7-1 of my package pgn-extract. It builds these binary packages: pgn-extract - Portable Game Notation (PGN) extractor The package appears to be lintian clean. The upload would fix these bugs: 561252 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/pgn-extract - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/pgn-extract/pgn-extract_16.7-1.dsc I would be glad if someone uploaded this package for me. Kind regards Vincent Legout Looking at it currently. However your watchfile seems to be dysfunctional, otherwise the package looks fine to me. Regards Christoph % uscan --report-status Useless content call in void context at /usr/share/perl5/LWP/Protocol/ftp.pm line 378 uscan warning: In watchfile debian/watch, reading FTP directory ftp://ftp.cs.kent.ac.uk/pub/djb/Extract/ failed: 400 FTP return code 000 pgpXKwqy9a95H.pgp Description: PGP signature
Re: RFS: pgn-extract (adopting orphaned package)
Hi! On Mon, Jan 4, 2010 at 5:11 PM, Christoph Egger christ...@debian.org wrote: Looking at it currently. However your watchfile seems to be dysfunctional, otherwise the package looks fine to me. (...) % uscan --report-status Useless content call in void context at /usr/share/perl5/LWP/Protocol/ftp.pm line 378 uscan warning: In watchfile debian/watch, reading FTP directory ftp://ftp.cs.kent.ac.uk/pub/djb/Extract/ failed: 400 FTP return code 000 Actually it works: $ uscan --report-status Processing watchfile line for package pgn-extract... Newest version on remote site is 16-7, local version is 16.7 pgn-extract: remote site does not even have current version Maybe this problem is caused by using/missing the PASV mode of FTP. See the uscan manpage for PASV. An improvement could be made on the watch file however (replace the dash by a dot): version=3 opts=uversionmangle=s/-/./ \ ftp://ftp.cs.kent.ac.uk/pub/djb/Extract/pgn-extract-(.*)\.tgz $ uscan --report-status Processing watchfile line for package pgn-extract... Newest version on remote site is 16.7, local version is 16.7 = Package is up to date Best regards, Nelson -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: pgn-extract (adopting orphaned package)
On Mon, Jan 04, 2010 at 05:25:38PM -0200, Nelson A. de Oliveira wrote : Hi! On Mon, Jan 4, 2010 at 5:11 PM, Christoph Egger christ...@debian.org wrote: Looking at it currently. However your watchfile seems to be dysfunctional, otherwise the package looks fine to me. (...) % uscan --report-status Useless content call in void context at /usr/share/perl5/LWP/Protocol/ftp.pm line 378 uscan warning: In watchfile debian/watch, reading FTP directory ftp://ftp.cs.kent.ac.uk/pub/djb/Extract/ failed: 400 FTP return code 000 Actually it works: $ uscan --report-status Processing watchfile line for package pgn-extract... Newest version on remote site is 16-7, local version is 16.7 pgn-extract: remote site does not even have current version Maybe this problem is caused by using/missing the PASV mode of FTP. See the uscan manpage for PASV. An improvement could be made on the watch file however (replace the dash by a dot): version=3 opts=uversionmangle=s/-/./ \ ftp://ftp.cs.kent.ac.uk/pub/djb/Extract/pgn-extract-(.*)\.tgz $ uscan --report-status Processing watchfile line for package pgn-extract... Newest version on remote site is 16.7, local version is 16.7 = Package is up to date Thanks Christoph and Nelson. I think Nelson is right, I've updated the watch file. http://mentors.debian.net/debian/pool/main/p/pgn-extract/pgn-extract_16.7-1.dsc Best Regards, Vincent -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: pgn-extract (adopting orphaned package)
Dear mentors, I am looking for a sponsor for the new version 16.7-1 of my package pgn-extract. It builds these binary packages: pgn-extract - Portable Game Notation (PGN) extractor The package appears to be lintian clean. The upload would fix these bugs: 561252 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/pgn-extract - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/pgn-extract/pgn-extract_16.7-1.dsc I would be glad if someone uploaded this package for me. Kind regards Vincent Legout -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: imagination (adopting orphaned package)
Dear mentors,
I am looking for a sponsor for the new version 1.5-3 of the package
imagination. I am adopting an orphaned package.
It builds these binary packages:
imagination - DVD slide show maker
The package appears to be lintian clean and builds in a clean sid pbuilder.
The upload would fix these bugs: 543846
The changes are mostly trivial:
imagination (1.5-3) unstable; urgency=low
* New maintainer. (Closes: #543846)
* debian/control:
- Add Vcs-* fields.
- Extend description.
- Rename Suggests on *-unstripped-* packages to the new
*-extra-* packages.
* Add debian/watch file.
* debian/copyright: Replace deprecated symbol (C) with ©.
* Move imagination.{xpm,1} to debian/ and install them from
debian/rules. Delete debian/manpages/, debian/pixmaps/, and
imagination.{manpages,install}.
Please note that the new watch file doesn't currently work, but that
is because of a bug in the sourceforge redirector. See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543711
The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/i/imagination
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget
http://mentors.debian.net/debian/pool/main/i/imagination/imagination_1.5-3.dsc
I would be glad if someone uploaded this package for me.
Kind regards
Andrew Starr-Bochicchio
P.S. I am not subscribed to pkg-multimedia-maintainers, please CC me
in replies. This package is not currently in pkg-multimedia, but I
might be interested in maintaining it there if the team is interested
in the package.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: imagination (adopting orphaned package)
On Mon, Aug 31, 2009 at 1:36 PM, Andrew SBa.star...@gmail.com wrote:
Dear mentors,
I am looking for a sponsor for the new version 1.5-3 of the package
imagination. I am adopting an orphaned package.
In my shortest wait ever on debian-mentors, this package was sponsored
off list. Thanks!
It builds these binary packages:
imagination - DVD slide show maker
The package appears to be lintian clean and builds in a clean sid pbuilder.
The upload would fix these bugs: 543846
The changes are mostly trivial:
imagination (1.5-3) unstable; urgency=low
* New maintainer. (Closes: #543846)
* debian/control:
- Add Vcs-* fields.
- Extend description.
- Rename Suggests on *-unstripped-* packages to the new
*-extra-* packages.
* Add debian/watch file.
* debian/copyright: Replace deprecated symbol (C) with ©.
* Move imagination.{xpm,1} to debian/ and install them from
debian/rules. Delete debian/manpages/, debian/pixmaps/, and
imagination.{manpages,install}.
Please note that the new watch file doesn't currently work, but that
is because of a bug in the sourceforge redirector. See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543711
The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/i/imagination
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget
http://mentors.debian.net/debian/pool/main/i/imagination/imagination_1.5-3.dsc
I would be glad if someone uploaded this package for me.
Kind regards
Andrew Starr-Bochicchio
P.S. I am not subscribed to pkg-multimedia-maintainers, please CC me
in replies. This package is not currently in pkg-multimedia, but I
might be interested in maintaining it there if the team is interested
in the package.
I feel comfortable maintaining this myself, but if anyone in
pkg-multimedia has a interest in this I'd still be open to maintaining
it there. Please drop debian-mentors in your reply...
Thanks all,
Andrew Starr-Bochicchio
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: A question about adopting a package
On Fri, Apr 25, 2008 at 11:42:41AM +0200, Vincent Bernat wrote: It seems that you have awaken the previous maintainer who have stolen your ITA. I hope that this won't bug you. Yes, I have already noticed. That is perfectly ok with me. To Alan Bain: - If you are reding this list, check your libf2c2 and ratfor packages. They are also listed as orphaned for 70 days. I have sent you an e-mail (to afrb2 at debian dot org). Have you received it? -- Stanislav -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A question about adopting a package
On Fri, 25 Apr 2008 00:05:26 +0400, Stanislav Maslovski [EMAIL PROTECTED] wrote: === 8 package wnpp retitle 465910 ITA: nec -- NEC2 Antenna Modelling System owner 465910 ! quit === 8 Yes, it would. You don't actually need the 'quit', but it hurts noone. Thanks, done. It seems that you have awaken the previous maintainer who have stolen your ITA. I hope that this won't bug you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
A question about adopting a package
Hello mentors, Reading the list of orphaned packages I have noticed that package nec has been orphaned [1]. Because I use NEC2 in antenna related research I think that I can adopt this package. At the moment I am not a maintainer of any package in Debian nor a DD, however I have been packaging software for my own needs for quite some time. One my package is awaiting a sponsor on mentors.debian.net [2]. As I have never worked with the BTS control bot, I am asking for directions. Shall this mail sent from my own address to [EMAIL PROTECTED] suffice for setting an ITA? === 8 package wnpp retitle 465910 ITA: nec -- NEC2 Antenna Modelling System owner 465910 ! quit === 8 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465910 [2] http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=fuse-convmvfs -- Stanislav -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A question about adopting a package
On Thu, Apr 24, 2008 at 11:25:11PM +0400, Stanislav Maslovski wrote: As I have never worked with the BTS control bot, I am asking for directions. Shall this mail sent from my own address to [EMAIL PROTECTED] suffice for setting an ITA? === 8 package wnpp retitle 465910 ITA: nec -- NEC2 Antenna Modelling System owner 465910 ! quit === 8 Yes, it would. You don't actually need the 'quit', but it hurts noone. -- Rodrigo Gallardo GPG-Fingerprint: 7C81 E60C 442E 8FBC D975 2F49 0199 8318 ADC9 BC28 signature.asc Description: Digital signature
Re: A question about adopting a package
On Thu, Apr 24, 2008 at 02:36:37PM -0500, Luis Rodrigo Gallardo Cruz wrote: On Thu, Apr 24, 2008 at 11:25:11PM +0400, Stanislav Maslovski wrote: Shall this mail sent from my own address to [EMAIL PROTECTED] suffice for setting an ITA? === 8 package wnpp retitle 465910 ITA: nec -- NEC2 Antenna Modelling System owner 465910 ! quit === 8 Yes, it would. You don't actually need the 'quit', but it hurts noone. Thanks, done. -- Stanislav -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A question about adopting a package
Luis Rodrigo Gallardo Cruz wrote: You don't actually need the 'quit', but it hurts noone. There actuatually seems to be a trend to use 'kthxbye' nowadays, which is not documented, but seems to work, and a lot cooler and lolcatter From http://www.debian.org/Bugs/server-control quit stop thank thanks thankyou thank you On a line by itself, in any case, possibly followed by whitespace, tells the control server to stop processing the message; the remainder of the message can include explanations, signatures or anything else, none of it will be detected by the control server. So 'quit' would be perfectly fine, and actually very useful, ie: I mail control and cc: a bug [EMAIL PROTECTED] tags XX moreinfo sevrity XX serious [more commands] quit Blah, I need you to provide all this extra info, blah... [more info on the bug] So that control doesn't try to parse evrery line of your mail and get confused, signatures included :) -- ·''`. Come, let me sing into your ear, those dancing days are gone : :' : I carry the sun in a golden cup, the moon in a silver bag `. `' `- Proudly running Debian GNU/Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A question about adopting a package
On Thu, 24 Apr 2008, Amaya wrote: Luis Rodrigo Gallardo Cruz wrote: You don't actually need the 'quit', but it hurts noone. There actuatually seems to be a trend to use 'kthxbye' nowadays, which is not documented, but seems to work, and a lot cooler and lolcatter It is documnted on server-control... see if you can find it. Don Armstrong -- This can't be happening to me. I've got tenure. -- James Hynes _Publish and Perish_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A question about adopting a package
Amaya [EMAIL PROTECTED] writes: Luis Rodrigo Gallardo Cruz wrote: You don't actually need the 'quit', but it hurts noone. There actuatually seems to be a trend to use 'kthxbye' nowadays, which is not documented, but seems to work, and a lot cooler and lolcatter I find these last two to be mutually exclusive. -- \Laurie got offended that I used the word 'puke.' But to me, | `\ that's what her dinner tasted like. -- Jack Handey | _o__) | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Adopting a package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Mentors, when adopting a package, sould I first contact the original maintainer and the the retitle the 'O:' bug to 'ITA:' or retitle it first and contact the maintainer afterwards? As I remember, a non-dd is allowed to adopt a package, am I right? Thanks, - -- Szabolcs -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFTNNjGJRwVVqzMkMRAm0hAJ9FZll0OsYzlG4GOf3Ak6OGTg+oggCgm1n8 ABiUtqaRlV+Go8uJTCROsr4= =2j9Q -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Adopting a package
Székelyi Szabolcs wrote: when adopting a package, sould I first contact the original maintainer and the the retitle the 'O:' bug to 'ITA:' or retitle it first and contact the maintainer afterwards? depends. when there is a O:, retitle it to ITA:, get a package ready and uploaded. when there is a RFA:, contact the maintainer first, retitle with his permission to ITA:, get a package ready and uploaded. As I remember, a non-dd is allowed to adopt a package, am I right? yes, of course. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Procedure for adopting a package?
On Sun, 2006-07-02 at 22:53 +0200, Bartosz Fenski aka fEnIo wrote: Please don't feel offended. I tried to contact you several times and I hijacked this packaged because I couldn't do that. In the future, an NMU might be a better start for improving a package that lacks care, rather than hijacking it right away. Thijs signature.asc Description: This is a digitally signed message part
Procedure for adopting a package?
Hello Mr. Fenski As the maintainer of the package calcurse (at least until yesterday) I was surprised, both good and bad, this morning to check my email and find that a new version of calcurse has been uploaded to Debian. I was surprised in a good way because the upload of version 1.4 was overdue and is now complete. That's great for the users of calcurse. The delay in packaging the update was entirely my fault and had to do with personal circumstances. My personal problems aside, it's great that a upload of calcurse occured to get the unstable package up-to-date. I was surprised in a bad way because with the new upload of version 1.4, I see that I have been replaced as the maintainer of the package. I thought that there was a process, at least informal and out of courtesy if not actually formal, where someone desiring to take over a package would contact the present maintainer and ask if he/she would be willing to part with the package. Either the present maintainer would agree and give up the package or not agree and hopefully invite the person to either co-maintain or assist with the package in some other way. Please let me know if I've misunderstood the adoption process. I absolutely love the Debian project and look forward to contributing my time and effort to it in the future. However I must admit that I'll think twice about packaging software in the future if there is indeed a policy where a DD can simply take over maintainence of a package without even sending me a courtesy email. From the bug reports you've filed against calcurse it's clear to me that you probably are the perfect person to maintain it, so in the final analysis I have no issue with you becoming the maintainer. But like I said, I thought there was a process regarding adoption. Ryan Coyner -- Ryan Coyner http://bakakaba.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Procedure for adopting a package?
* Ryan Coyner [Sun, 02 Jul 2006 12:11:36 -0400]: However I must admit that I'll think twice about packaging software in the future if there is indeed a policy where a DD can simply take over maintainence of a package without even sending me a courtesy email. No, there isn't such policy. To all effects, the calcurse 1.4-1 upload was an unannounced hijack, which are not allowed in Debian at all (dev-ref 5.9.5). I can certainly understand the feelings of a DD who cares for a package if they think that the maintainer (particularly if not DD) is not doing a good job at it. However, I've always dealt with this situation by offering help to the original maintainer, in whichever way was appropriate (eg. co-maintainership if the maintainer just lacks time sometimes, or mentoring and sponsoring if the package is not in well form). I would expect the rest of DDs to do the same. But like I said, I thought there was a process regarding adoption. Confirmed. And thanks for bringing this to our attention in such a polite manner. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org And don't get me wrong - I don't mind getting proven wrong. I change my opinions the way some people change underwear. And I think that's ok. -- Linus Torvalds -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Procedure for adopting a package?
On Sun, Jul 02, 2006 at 12:11:36PM -0400, Ryan Coyner wrote: Hello Mr. Fenski Hi. As the maintainer of the package calcurse (at least until yesterday) I was surprised, both good and bad, this morning to check my email and find that a new version of calcurse has been uploaded to Debian. I was surprised in a good way because the upload of version 1.4 was overdue and is now complete. That's great for the users of calcurse. The delay in packaging the update was entirely my fault and had to do with personal circumstances. My personal problems aside, it's great that a upload of calcurse occured to get the unstable package up-to-date. I was surprised in a bad way because with the new upload of version 1.4, I see that I have been replaced as the maintainer of the package. I thought that there was a process, at least informal and out of courtesy if not actually formal, where someone desiring to take over a package would contact the present maintainer and ask if he/she would be willing to part with the package. Either the present maintainer would agree and give up the package or not agree and hopefully invite the person to either co-maintain or assist with the package in some other way. I tried to contact you several times. Mails sent to your address were bouncing all the time. I contacted your sponsor and talked about it with him. As a conclusion we decided that I can hijack this package. Please let me know if I've misunderstood the adoption process. I absolutely love the Debian project and look forward to contributing my time and effort to it in the future. However I must admit that I'll think twice about packaging software in the future if there is indeed a policy where a DD can simply take over maintainence of a package without even sending me a courtesy email. From the bug reports you've filed against calcurse it's clear to me that you probably are the perfect person to maintain it, so in the final analysis I have no issue with you becoming the maintainer. But like I said, I thought there was a process regarding adoption. Please don't feel offended. I tried to contact you several times and I hijacked this packaged because I couldn't do that. Feel free to reupload calcurse with you in the maintainer line again. I'm willing to sponsor your upload if you want. regards fEnIo -- ,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo : :' : 32-050 Skawina - Glowackiego 3/15 - malopolskie v. - Poland `. `' phone:+48602383548 | proud Debian maintainer and user `- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001 signature.asc Description: Digital signature
Re: Procedure for adopting a package?
On Sunday 02 July 2006 23:53, Bartosz Fenski aka fEnIo wrote: --cut-- From the bug reports you've filed against calcurse it's clear to me that you probably are the perfect person to maintain it, so in the final analysis I have no issue with you becoming the maintainer. But like I said, I thought there was a process regarding adoption. Please don't feel offended. I tried to contact you several times and I hijacked this packaged because I couldn't do that. In such cases you better document your intentions in BTS, since that: - will leave public records of your trials to reach the maintainer. - will prevent (or coordinate) duplicate hijack efforts if the package had been really in bad shape and this was the last resort in the light of better maintenance. Hijacking is not necessary a bad thing[tm] imho if done with respectcare. -- pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Advice on adopting a package: relay-ctrl
On Sat, Mar 27, 2004 at 01:24:48PM +1100, Anibal Monsalve Salazar may have written: On Fri, Mar 26, 2004 at 06:27:04AM -0500, Brian T Glenn wrote: deb http://cvs.delink.net/debian/ delink contrib deb-src http://cvs.delink.net/debian/ delink contrib I couldn't get relay-ctrl_3.1.1.orig.tar.gz. $ apt-get source relay-ctrl Reading Package Lists... Done Building Dependency Tree... Done Need to get 37.8kB of source archives. Get:1 http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (dsc) [571B] Err http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (tar) 404 Not Found Get:2 http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (diff) [2184B] Fetched 2755B in 1s (1795B/s) Failed to fetch http://cvs.delink.net/debian/pool/contrib/r/relay-ctrl/relay-ctrl_3.1.1.orig.tar.gz 404 Not Found E: Failed to fetch some archives. My apologies. This has been corrected. -- Brian T Glenn delink.net Internet Services pgpuuussJ1lkC.pgp Description: PGP signature
Re: Advice on adopting a package: relay-ctrl
On Fri, Mar 26, 2004 at 06:27:04AM -0500, Brian T Glenn wrote: deb http://cvs.delink.net/debian/ delink contrib deb-src http://cvs.delink.net/debian/ delink contrib I couldn't get relay-ctrl_3.1.1.orig.tar.gz. $ apt-get source relay-ctrl Reading Package Lists... Done Building Dependency Tree... Done Need to get 37.8kB of source archives. Get:1 http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (dsc) [571B] Err http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (tar) 404 Not Found Get:2 http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (diff) [2184B] Fetched 2755B in 1s (1795B/s) Failed to fetch http://cvs.delink.net/debian/pool/contrib/r/relay-ctrl/relay-ctrl_3.1.1.orig.tar.gz 404 Not Found E: Failed to fetch some archives. Anibal Monsalve Salazar -- .''`. Debian GNU/Linux | Building 28C : :' : Free Operating System | Monash University VIC 3800, Australia `. `' http://debian.org/| http://www-personal.monash.edu/~anibal/ `- | pgp0.pgp Description: PGP signature
Re: Advice on adopting a package: relay-ctrl
On Sat, Mar 27, 2004 at 01:24:48PM +1100, Anibal Monsalve Salazar may have written: On Fri, Mar 26, 2004 at 06:27:04AM -0500, Brian T Glenn wrote: deb http://cvs.delink.net/debian/ delink contrib deb-src http://cvs.delink.net/debian/ delink contrib I couldn't get relay-ctrl_3.1.1.orig.tar.gz. $ apt-get source relay-ctrl Reading Package Lists... Done Building Dependency Tree... Done Need to get 37.8kB of source archives. Get:1 http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (dsc) [571B] Err http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (tar) 404 Not Found Get:2 http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (diff) [2184B] Fetched 2755B in 1s (1795B/s) Failed to fetch http://cvs.delink.net/debian/pool/contrib/r/relay-ctrl/relay-ctrl_3.1.1.orig.tar.gz 404 Not Found E: Failed to fetch some archives. My apologies. This has been corrected. -- Brian T Glenn delink.net Internet Services pgp0.pgp Description: PGP signature
Re: Advice on adopting a package: relay-ctrl
On Fri, Mar 26, 2004 at 01:39:24PM +1100, Anibal Monsalve Salazar may have written: Yes. You put in one directory the files with the following suffixes: .diff.gz, .dsc, .changes, .deb and .orig.tar.gz. For example, look at [2] or any other debian package for that matter. Note that you have to provide one .deb file, not one for each architecture supported by debian. You can also see my web page, referenced in my signature. [2] http://ftp.debian.org/debian/pool/main/z/zcip/ Thank you. The changes file has been updated. The new apt lines are: deb http://cvs.delink.net/debian/ delink contrib deb-src http://cvs.delink.net/debian/ delink contrib relay-ctrl is released under the GPL, but it depends on qmail, which has a non-free license. Cheers, -- Brian T Glenn delink.net Internet Services pgpcnZ5wtpyPw.pgp Description: PGP signature
Re: Advice on adopting a package: relay-ctrl
On Fri, Mar 26, 2004 at 06:27:04AM -0500, Brian T Glenn wrote: deb http://cvs.delink.net/debian/ delink contrib deb-src http://cvs.delink.net/debian/ delink contrib I couldn't get relay-ctrl_3.1.1.orig.tar.gz. $ apt-get source relay-ctrl Reading Package Lists... Done Building Dependency Tree... Done Need to get 37.8kB of source archives. Get:1 http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (dsc) [571B] Err http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (tar) 404 Not Found Get:2 http://cvs.delink.net delink/contrib relay-ctrl 3.1.1-1 (diff) [2184B] Fetched 2755B in 1s (1795B/s) Failed to fetch http://cvs.delink.net/debian/pool/contrib/r/relay-ctrl/relay-ctrl_3.1.1.orig.tar.gz 404 Not Found E: Failed to fetch some archives. Anibal Monsalve Salazar -- .''`. Debian GNU/Linux | Building 28C : :' : Free Operating System | Monash University VIC 3800, Australia `. `' http://debian.org/| http://www-personal.monash.edu/~anibal/ `- | pgp7N6lzqPoGJ.pgp Description: PGP signature
Re: Advice on adopting a package: relay-ctrl
On Mon, Mar 22, 2004 at 07:36:23PM -0500, Brian T Glenn wrote: I have submitted an ITA (Bug#238972), but the original RFA is Bug#238972. The original RFA is 237446. There was no need for a new bug report (238972). You have already retitled bug report 237446. Now, you need to merge 237446 and 238972. See [0]. [0] http://www.debian.org/Bugs/server-control I have new packages created for relay-ctrl at the current version per the RFA. I attempted to contact the current maintainer, but i have received no response after a few days. What else should I be doing in order to execute the ITA? You will need a sponsor to upload the package for you. See [1]. [1] http://people.debian.org/~mpalmer/debian-mentors_FAQ.html#sponsored_packages The packages are available from the following apt source: deb http://cvs.delink.net/debian/ delink main contrib deb-src http://cvs.delink.net/debian/ delink main contrib I visited http://cvs.delink.net/debian/ to see the .changes file and the response was file does not exist. I just wanted to see the .changes file without downloading everything. -- Brian T Glenn delink.net Internet Services Anibal Monsalve Salazar -- .''`. Debian GNU/Linux | Building 28C : :' : Free Operating System | Monash University VIC 3800, Australia `. `' http://debian.org/| http://www-personal.monash.edu/~anibal/ `- | pgpncMMoQpfKO.pgp Description: PGP signature
Re: Advice on adopting a package: relay-ctrl
On Fri, Mar 26, 2004 at 09:16:21AM +1100, Anibal Monsalve Salazar may have written: On Mon, Mar 22, 2004 at 07:36:23PM -0500, Brian T Glenn wrote: I have submitted an ITA (Bug#238972), but the original RFA is Bug#238972. The original RFA is 237446. There was no need for a new bug report (238972). You have already retitled bug report 237446. Now, you need to merge 237446 and 238972. See [0]. [0] http://www.debian.org/Bugs/server-control Thank you, I will do that now. I only recently found where I was to retitle instead of expecting the submit address to handle it. I will merge these bugs. I have new packages created for relay-ctrl at the current version per the RFA. I attempted to contact the current maintainer, but i have received no response after a few days. What else should I be doing in order to execute the ITA? You will need a sponsor to upload the package for you. See [1]. [1] http://people.debian.org/~mpalmer/debian-mentors_FAQ.html#sponsored_packages Thanks. The packages are available from the following apt source: deb http://cvs.delink.net/debian/ delink main contrib deb-src http://cvs.delink.net/debian/ delink main contrib I visited http://cvs.delink.net/debian/ to see the .changes file and the response was file does not exist. I just wanted to see the .changes file without downloading everything. I had not yet uploaded the .changes file. I was attempting to follow one of the Debian mirror's hierarchies to set up my apt source, and I was not sure where the changes file belonged in the hierarchy. Does it go in the same dir as the binary .deb or does it go with the source files? Cheers, -- Brian T Glenn delink.net Internet Services pgp3x0Tn8UkRQ.pgp Description: PGP signature
Re: Advice on adopting a package: relay-ctrl
On Thu, Mar 25, 2004 at 08:24:54PM -0500, Brian T Glenn wrote: On Fri, Mar 26, 2004 at 09:16:21AM +1100, Anibal Monsalve Salazar may have written: On Mon, Mar 22, 2004 at 07:36:23PM -0500, Brian T Glenn wrote: I have submitted an ITA (Bug#238972), but the original RFA is Bug#238972. The original RFA is 237446. There was no need for a new bug report (238972). You have already retitled bug report 237446. Now, you need to merge 237446 and 238972. See [0]. [0] http://www.debian.org/Bugs/server-control Thank you, I will do that now. I only recently found where I was to retitle instead of expecting the submit address to handle it. I will merge these bugs. I have new packages created for relay-ctrl at the current version per the RFA. I attempted to contact the current maintainer, but i have received no response after a few days. What else should I be doing in order to execute the ITA? You will need a sponsor to upload the package for you. See [1]. [1] http://people.debian.org/~mpalmer/debian-mentors_FAQ.html#sponsored_packages Thanks. The packages are available from the following apt source: deb http://cvs.delink.net/debian/ delink main contrib deb-src http://cvs.delink.net/debian/ delink main contrib I visited http://cvs.delink.net/debian/ to see the .changes file and the response was file does not exist. I just wanted to see the .changes file without downloading everything. I had not yet uploaded the .changes file. I was attempting to follow one of the Debian mirror's hierarchies to set up my apt source, and I was not sure where the changes file belonged in the hierarchy. Does it go in the same dir as the binary .deb or does it go with the source files? Yes. You put in one directory the files with the following suffixes: .diff.gz, .dsc, .changes, .deb and .orig.tar.gz. For example, look at [2] or any other debian package for that matter. Note that you have to provide one .deb file, not one for each architecture supported by debian. You can also see my web page, referenced in my signature. [2] http://ftp.debian.org/debian/pool/main/z/zcip/ Cheers, -- Brian T Glenn delink.net Internet Services Anibal Monsalve Salazar -- .''`. Debian GNU/Linux | Building 28C : :' : Free Operating System | Monash University VIC 3800, Australia `. `' http://debian.org/| http://www-personal.monash.edu/~anibal/ `- | pgphE5XwXk9aR.pgp Description: PGP signature
Advice on adopting a package: relay-ctrl
I have submitted an ITA (Bug#238972), but the original RFA is Bug#238972. I have new packages created for relay-ctrl at the current version per the RFA. I attempted to contact the current maintainer, but i have received no response after a few days. What else should I be doing in order to execute the ITA? The packages are available from the following apt source: deb http://cvs.delink.net/debian/ delink main contrib deb-src http://cvs.delink.net/debian/ delink main contrib -- Brian T Glenn delink.net Internet Services pgp0.pgp Description: PGP signature
Advice on adopting a package: relay-ctrl
I have submitted an ITA (Bug#238972), but the original RFA is Bug#238972. I have new packages created for relay-ctrl at the current version per the RFA. I attempted to contact the current maintainer, but i have received no response after a few days. What else should I be doing in order to execute the ITA? The packages are available from the following apt source: deb http://cvs.delink.net/debian/ delink main contrib deb-src http://cvs.delink.net/debian/ delink main contrib -- Brian T Glenn delink.net Internet Services pgpuC0UIy0taI.pgp Description: PGP signature
Adopting a package without being DD?
Hello, I'd like to adopt qiv (bug #176329), but I am not a DD yet. I am using this package and don't want to see it removed. Should I file ITA? Or maybe - how long should I wait for some real DD to take care of this package before filing ITA myself? -- Dariush Pietrzak, Who are we helping? - the girl. - Typical. Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Adopting a package without being DD?
hello dariush... Received at 2003-01-14 / 22:24 by Dariush Pietrzak: I'd like to adopt qiv (bug #176329), but I am not a DD yet. I am using this package and don't want to see it removed. Should I file ITA? Or maybe - how long should I wait for some real DD to take care of this package before filing ITA myself? perhaps you should look for a sponsor (someone who would upload the package for you), first. otherwise you should not wait an arbitrary time to ITA, just do it. :) cheers, sebastian -- ::: sebastian henschel ::: kodeaffe ::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import msg08295/pgp0.pgp Description: PGP signature
Adopting a package without being DD?
Hello, I'd like to adopt qiv (bug #176329), but I am not a DD yet. I am using this package and don't want to see it removed. Should I file ITA? Or maybe - how long should I wait for some real DD to take care of this package before filing ITA myself? -- Dariush Pietrzak, Who are we helping? - the girl. - Typical. Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9
Re: Adopting a package without being DD?
hello dariush... Received at 2003-01-14 / 22:24 by Dariush Pietrzak: I'd like to adopt qiv (bug #176329), but I am not a DD yet. I am using this package and don't want to see it removed. Should I file ITA? Or maybe - how long should I wait for some real DD to take care of this package before filing ITA myself? perhaps you should look for a sponsor (someone who would upload the package for you), first. otherwise you should not wait an arbitrary time to ITA, just do it. :) cheers, sebastian -- ::: sebastian henschel ::: kodeaffe ::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import pgpyGS9SdevRQ.pgp Description: PGP signature
adopting a package
Thanks for your hints. But I have still two questions: 1. Where can I find the old-version of the package. (Since I want to adopt an existing package I think I can skip the steps descriped in the sections 3-6 in the Debian New Maintainers' Guide and start with section 9.) 2. I can not use the programs dupload or dput for uploading the package. (My my debian-PC has no internet connection.) So I need a guide to: How to upload a package manually. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: adopting a package
Andreas Klein [EMAIL PROTECTED] writes: 1. Where can I find the old-version of the package. (Since I want to adopt an existing package I think I can skip the steps descriped in the sections 3-6 in the Debian New Maintainers' Guide and start with section 9.) apt-get source PACKAGE Or look into the pool. 2. I can not use the programs dupload or dput for uploading the package. (My my debian-PC has no internet connection.) So I need a guide to: How to upload a package manually. Looking at db.debian.org you are no DD. So you cant upload. You have to ask for a sponsor that looks at your package and then uploads it. If you are and my search failed: Use scp to auric and move them into the incoming and be sure to give katie the rights to read the files. :) -- begin OjE-ist-scheisse.txt bye, Joerg Encrypted Mail preferred! Registered Linux User #97793 @ http://counter.li.org end msg07546/pgp0.pgp Description: PGP signature
adopting a package
Thanks for your hints. But I have still two questions: 1. Where can I find the old-version of the package. (Since I want to adopt an existing package I think I can skip the steps descriped in the sections 3-6 in the Debian New Maintainers' Guide and start with section 9.) 2. I can not use the programs dupload or dput for uploading the package. (My my debian-PC has no internet connection.) So I need a guide to: How to upload a package manually.
Re: adopting a package
Andreas Klein [EMAIL PROTECTED] writes: 1. Where can I find the old-version of the package. (Since I want to adopt an existing package I think I can skip the steps descriped in the sections 3-6 in the Debian New Maintainers' Guide and start with section 9.) apt-get source PACKAGE Or look into the pool. 2. I can not use the programs dupload or dput for uploading the package. (My my debian-PC has no internet connection.) So I need a guide to: How to upload a package manually. Looking at db.debian.org you are no DD. So you cant upload. You have to ask for a sponsor that looks at your package and then uploads it. If you are and my search failed: Use scp to auric and move them into the incoming and be sure to give katie the rights to read the files. :) -- begin OjE-ist-scheisse.txt bye, Joerg Encrypted Mail preferred! Registered Linux User #97793 @ http://counter.li.org end pgpyVGuay4hqw.pgp Description: PGP signature
adopting a package
I want do adopt the package **larswm**. I have several years Linux experience but I'm a newbi to debian. So I need a quick introdution in Howto maintain a debian package. Thanks for your help. Andreas Klein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: adopting a package
Andreas Klein [EMAIL PROTECTED] writes: I want do adopt the package **larswm**. I have several years Linux experience but I'm a newbi to debian. So I need a quick introdution in Howto maintain a debian package. http://www.debian.org/doc/maint-guide/ -- People said I was dumb, but I proved them! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: adopting a package
On Tue, Oct 22, 2002 at 09:03:58AM +0200, Andreas Klein wrote: I want do adopt the package **larswm**. I have several years Linux experience but I'm a newbi to debian. So I need a quick introdution in Howto maintain a debian package. Read practically all the links in http://www.debian.org/devel/ if you are to make package for Debian. Josip's Debian New Maintainers' Guide is available as: http://www.debian.org/doc/maint-guide/ (Released version) http://www.debian.org/doc/manuals/maint-guide/ (CVS version) Package: maint-guide (or translation maint-guide-fr) I think developer reference is must-read if you think about packaging for other people. Cheers. -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki [EMAIL PROTECTED] Cupertino CA USA, GPG-key: A8061F32 .''`. Debian Reference: post-installation user's guide for non-developers : :' : http://www.debian.org/doc/manuals/reference/ also http://qref.sf.net `. `' Our Priorities are Our Users and Free Software --- Social Contract -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
adopting a package
I want do adopt the package **larswm**. I have several years Linux experience but I'm a newbi to debian. So I need a quick introdution in Howto maintain a debian package. Thanks for your help. Andreas Klein
Re: adopting a package
Andreas Klein [EMAIL PROTECTED] writes: I want do adopt the package **larswm**. I have several years Linux experience but I'm a newbi to debian. So I need a quick introdution in Howto maintain a debian package. http://www.debian.org/doc/maint-guide/ -- People said I was dumb, but I proved them!
Re: adopting a package
On Tue, Oct 22, 2002 at 09:03:58AM +0200, Andreas Klein wrote: I want do adopt the package **larswm**. I have several years Linux experience but I'm a newbi to debian. So I need a quick introdution in Howto maintain a debian package. Read practically all the links in http://www.debian.org/devel/ if you are to make package for Debian. Josip's Debian New Maintainers' Guide is available as: http://www.debian.org/doc/maint-guide/ (Released version) http://www.debian.org/doc/manuals/maint-guide/ (CVS version) Package: maint-guide (or translation maint-guide-fr) I think developer reference is must-read if you think about packaging for other people. Cheers. -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki [EMAIL PROTECTED] Cupertino CA USA, GPG-key: A8061F32 .''`. Debian Reference: post-installation user's guide for non-developers : :' : http://www.debian.org/doc/manuals/reference/ also http://qref.sf.net `. `' Our Priorities are Our Users and Free Software --- Social Contract
Re: Adopting a package ¿¿??
On Fri, 2 Mar 2001 00:48:57 +0100, Javier Viñuales Gutiérrez [EMAIL PROTECTED] wrote: I know to make a _new_ debian package from its sources but now, I need to package a _orphaned_ package from its diff, dsc, orig and changes files. What do I have to do?. You probably only have to dpkg-source -x on your .dsc file which gives you the package directory. Then go ahead with your changes, do the appropriate changelog entries and proceed to build your new source/binary package. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Karlsruhe, Germany | Beginning of Wisdom | Fon: *49 721 966 32 15 Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fax: *49 721 966 31 29
Adopting a package ¿¿??
Hello, I know to make a _new_ debian package from its sources but now, I need to package a _orphaned_ package from its diff, dsc, orig and changes files. What do I have to do?. Thank you. -- Javier Viuales Gutirrez [EMAIL PROTECTED] GnuPG public information: pub 1024D/4EB82468 1C2A 0241 D350 B43D E027 4FCD F8E8 3454 4EB8 2468 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Adopting a package ¿¿??
Hello, I know to make a _new_ debian package from its sources but now, I need to package a _orphaned_ package from its diff, dsc, orig and changes files. What do I have to do?. Thank you. -- Javier Viñuales Gutiérrez [EMAIL PROTECTED] GnuPG public information: pub 1024D/4EB82468 1C2A 0241 D350 B43D E027 4FCD F8E8 3454 4EB8 2468
Re: Adopting a package
On Fri, Mar 02, 2001 at 12:48:57AM +0100, Javier Vi?uales Guti?rrez wrote: I know to make a _new_ debian package from its sources but now, I need to package a _orphaned_ package from its diff, dsc, orig and changes files. What do I have to do?. First, apt-get source packagename. This will download the diff, dsc, orig, and unpack them. If you already have the .diff, dsc, and orig.tar.gz, use dpkg-source -x filename.dsc to do the same as apt-get source. Now, update the package. If you need to upgrade to a new upstream version uupdate automates this process nicely. (Note that if you get .rej files for the diff, you'll have to merge the changes manually; sometimes, if it's just editing the Makefile.in, you can re-run automake if the Makefile.am was properly patched. Deal with it on a case-by-case basis.) Don't forget to change the Maintainer to your name in the control file, and create a new revision with your name in the changelog (dch -i in the source tree will create a new revision.) Hope this helps, Joe
Adopting a package
Hi I am a little new at this and confused by the documentation on the bug track page. How do I go about adopting a package that is up for adoption? I believe I have to send a message to [EMAIL PROTECTED] but what do I use in the subject? Just a little confused by these options. OIf you are going to adopt a package, retitle its bug to replace `O' with `ITA', in order for other people to know the package is being adopted and to prevent its automatic removal from the archive. To actually adopt the package, upload it with your name in its Maintainer: field, and close this bug once the package has been installed. RFAIf you are going to adopt a package, retitle its bug to replace `RFA' with `ITA', in order for other people to know the package is being adopted and to prevent its automatic removal from the archive. To actually adopt the package, upload it with your name in its Maintainer: field, and close this bug once the package has been installed. Thanks Sean # # Sean Preston [EMAIL PROTECTED] # GNU/Linux, the OS of choice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Adopting a package
On 26-Feb-2001 Sean Preston wrote: Hi I am a little new at this and confused by the documentation on the bug track page. How do I go about adopting a package that is up for adoption? I believe I have to send a message to [EMAIL PROTECTED] but what do I use in the subject? Just a little confused by these options. go to http://bugs.debian.org, read the developer reference. When you are doing the work, but not ready to upload, mail to [EMAIL PROTECTED] a retitle command. When you actually have the package ready, in your changelog, add a line like: * adopted package, Closes: #1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Adopting a package
Hi I am a little new at this and confused by the documentation on the bug track page. How do I go about adopting a package that is up for adoption? I believe I have to send a message to [EMAIL PROTECTED] but what do I use in the subject? Just a little confused by these options. OIf you are going to adopt a package, retitle its bug to replace `O' with `ITA', in order for other people to know the package is being adopted and to prevent its automatic removal from the archive. To actually adopt the package, upload it with your name in its Maintainer: field, and close this bug once the package has been installed. RFAIf you are going to adopt a package, retitle its bug to replace `RFA' with `ITA', in order for other people to know the package is being adopted and to prevent its automatic removal from the archive. To actually adopt the package, upload it with your name in its Maintainer: field, and close this bug once the package has been installed. Thanks Sean # # Sean Preston [EMAIL PROTECTED] # GNU/Linux, the OS of choice
RE: Adopting a package
On 26-Feb-2001 Sean Preston wrote: Hi I am a little new at this and confused by the documentation on the bug track page. How do I go about adopting a package that is up for adoption? I believe I have to send a message to [EMAIL PROTECTED] but what do I use in the subject? Just a little confused by these options. go to http://bugs.debian.org, read the developer reference. When you are doing the work, but not ready to upload, mail to [EMAIL PROTECTED] a retitle command. When you actually have the package ready, in your changelog, add a line like: * adopted package, Closes: #1
Re: Adopting a Package
On Tue, Aug 15, 2000 at 01:00:46AM -0400, Steven R . Baker wrote: I changed the control files, did a dch -i, and stuff, and did dpkg-buildpackage and it didn't generate a new .changes file, just a .diff and a .dsc??? Do you have a gpg key with the exact ID in your Maintainer: field? Send the logs of dpkg-buildpackage to see what happened. Jordi PS: Thank you for updating AS, it's a shame potato shipped with 1.6 :| -- Jordi Mallach Pérez || [EMAIL PROTECTED] || Rediscovering Freedom, aka Oskuro in|| [EMAIL PROTECTED] || Using Debian GNU/Linux Reinos de Leyenda || [EMAIL PROTECTED] || http://debian.org http://sindominio.net GnuPG public information: pub 1024D/917A225E telnet pusa.uv.es 23 73ED 4244 FD43 5886 20AC 2644 2584 94BA 917A 225E pgpUXgAr6Hrpj.pgp Description: PGP signature
Re: Adopting a Package
So, I just created a new package. Should I have merged the changelogs into one, and made the packages look similar? Yes. If the package name is the same, you should have. The package should as cleanly as possible replace the old one. History is important, even if it's just new version upstream, new maintainer, newly re-packaged., and the rest of the changelog is useless. It's still history of the package, and someone might CHOOSE to revert and stay with the older version given a major change like that. apt-get upgrade will install your package, and the user has a right to be able to read the changelog and the readmes and understand what happened. Seth
Re: Adopting a Package
On Mon, Aug 14, 2000 at 11:58:38PM -0400, Steven R . Baker wrote: Hi everyone, I just adopted AfterStep, but ran into some problems with the adoption process. The previous AfterStep package packaged version 1.6.10, and the current (stable) version is 1.8.3. So, after speaking with the previous maintainer (a while ago) I packaged 1.8.3. When packaging 1.8.3, I ran into a few problems. Namely, the fact that the AfterStep source tree has changed so much since 1.6.10 that most of the debian control files were useless. So, I just created a new package. Should I have merged the changelogs into one, and made the packages look similar? I just received a message from someone commenting (although, I don't know if it was sarcastic or not) on the lack of a changelog for my AfterStep package. Some thoughts on this would be greatly appreciated. In short, yes. A history of what has happened with respects to the debian package is important. a changelog entry of * Completely reimplemented debian/* due to major upstream changes or similar would be sufficient to explain things. (My wording sucks.. dont use the above.) -- Michael Beattie ([EMAIL PROTECTED]) - If NT is the answer, you didn't understand the question. (NB: Stolen sig) - Debian GNU/Linux Ooohh You are missing out! pgpoNlFHX22Cl.pgp Description: PGP signature
Re: Adopting a Package
Thanks. That's basically what I was thinking, only it never occurred to me at all until after the package was installed. I'll fix it. Which leads me to my next question. What's the proper way to do another release of my package? I changed the control files, did a dch -i, and stuff, and did dpkg-buildpackage and it didn't generate a new .changes file, just a .diff and a .dsc??? What's the proper procedure for creating a new release? Thanks, -Steven On Mon, Aug 14, 2000 at 09:04:49PM -0700, Seth Cohn wrote: So, I just created a new package. Should I have merged the changelogs into one, and made the packages look similar? Yes. If the package name is the same, you should have. The package should as cleanly as possible replace the old one. History is important, even if it's just new version upstream, new maintainer, newly re-packaged., and the rest of the changelog is useless. It's still history of the package, and someone might CHOOSE to revert and stay with the older version given a major change like that. apt-get upgrade will install your package, and the user has a right to be able to read the changelog and the readmes and understand what happened. Seth pgpOGcybvEKBE.pgp Description: PGP signature
Adopting a Package
Hi everyone, I just adopted AfterStep, but ran into some problems with the adoption process. The previous AfterStep package packaged version 1.6.10, and the current (stable) version is 1.8.3. So, after speaking with the previous maintainer (a while ago) I packaged 1.8.3. When packaging 1.8.3, I ran into a few problems. Namely, the fact that the AfterStep source tree has changed so much since 1.6.10 that most of the debian control files were useless. So, I just created a new package. Should I have merged the changelogs into one, and made the packages look similar? I just received a message from someone commenting (although, I don't know if it was sarcastic or not) on the lack of a changelog for my AfterStep package. Some thoughts on this would be greatly appreciated. Thanks, -Steven PGP signature
Re: Adopting a Package
So, I just created a new package. Should I have merged the changelogs into one, and made the packages look similar? Yes. If the package name is the same, you should have. The package should as cleanly as possible replace the old one. History is important, even if it's just "new version upstream, new maintainer, newly re-packaged.", and the rest of the changelog is useless. It's still history of the package, and someone might CHOOSE to revert and stay with the older version given a major change like that. apt-get upgrade will install your package, and the user has a right to be able to read the changelog and the readmes and understand what happened. Seth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Adopting a Package
On Mon, Aug 14, 2000 at 11:58:38PM -0400, Steven R . Baker wrote: Hi everyone, I just adopted AfterStep, but ran into some problems with the adoption process. The previous AfterStep package packaged version 1.6.10, and the current (stable) version is 1.8.3. So, after speaking with the previous maintainer (a while ago) I packaged 1.8.3. When packaging 1.8.3, I ran into a few problems. Namely, the fact that the AfterStep source tree has changed so much since 1.6.10 that most of the debian control files were useless. So, I just created a new package. Should I have merged the changelogs into one, and made the packages look similar? I just received a message from someone commenting (although, I don't know if it was sarcastic or not) on the lack of a changelog for my AfterStep package. Some thoughts on this would be greatly appreciated. In short, yes. A history of what has happened with respects to the debian package is important. a changelog entry of * Completely reimplemented debian/* due to major upstream changes or similar would be sufficient to explain things. (My wording sucks.. dont use the above.) -- Michael Beattie ([EMAIL PROTECTED]) - If NT is the answer, you didn't understand the question. (NB: Stolen sig) - Debian GNU/Linux Ooohh You are missing out! PGP signature
Re: Adopting a Package
Thanks. That's basically what I was thinking, only it never occurred to me at all until after the package was installed. I'll fix it. Which leads me to my next question. What's the proper way to do another release of my package? I changed the control files, did a dch -i, and stuff, and did dpkg-buildpackage and it didn't generate a new .changes file, just a .diff and a .dsc??? What's the proper procedure for creating a new release? Thanks, -Steven On Mon, Aug 14, 2000 at 09:04:49PM -0700, Seth Cohn wrote: So, I just created a new package. Should I have merged the changelogs into one, and made the packages look similar? Yes. If the package name is the same, you should have. The package should as cleanly as possible replace the old one. History is important, even if it's just "new version upstream, new maintainer, newly re-packaged.", and the rest of the changelog is useless. It's still history of the package, and someone might CHOOSE to revert and stay with the older version given a major change like that. apt-get upgrade will install your package, and the user has a right to be able to read the changelog and the readmes and understand what happened. Seth PGP signature
Adopting a Package
Hi everyone, I just adopted AfterStep, but ran into some problems with the adoption process. The previous AfterStep package packaged version 1.6.10, and the current (stable) version is 1.8.3. So, after speaking with the previous maintainer (a while ago) I packaged 1.8.3. When packaging 1.8.3, I ran into a few problems. Namely, the fact that the AfterStep source tree has changed so much since 1.6.10 that most of the debian control files were useless. So, I just created a new package. Should I have merged the changelogs into one, and made the packages look similar? I just received a message from someone commenting (although, I don't know if it was sarcastic or not) on the lack of a changelog for my AfterStep package. Some thoughts on this would be greatly appreciated. Thanks, -Steven pgpwSdIjOK6EP.pgp Description: PGP signature
Guidance while adopting freeamp package
I have spoken with the old maintainer, and am adopting the freeamp package. I have downloaded the old source from ftp.debian.org and have created a newer package based on more recent upstream sources. However, I have a number of questions about how I have done things that I am unsure of. Is it appropriate to ask all of them on this list, or would someone be willing to help me via private email? Thanks in advance. -- Ian Peters | GnuPG Key ID 5C23D20C| He that breaks a thing to find out [EMAIL PROTECTED] | E584 2558 FAC3 BEAB EFAC | what it is has left the path of [EMAIL PROTECTED] | FC74 CFED 7E24 5C23 D20C | wisdom. -- J.R.R. Tolkien pgpPoYw2TtSsA.pgp Description: PGP signature
Re: Guidance while adopting freeamp package
This is the list... On Tue, Jul 20, 1999 at 10:59:41AM -0400, Ian Peters wrote: I have spoken with the old maintainer, and am adopting the freeamp package. I have downloaded the old source from ftp.debian.org and have created a newer package based on more recent upstream sources. However, I have a number of questions about how I have done things that I am unsure of. Is it appropriate to ask all of them on this list, or would someone be willing to help me via private email? Thanks in advance. -- Ian Peters | GnuPG Key ID 5C23D20C| He that breaks a thing to find out [EMAIL PROTECTED] | E584 2558 FAC3 BEAB EFAC | what it is has left the path of [EMAIL PROTECTED] | FC74 CFED 7E24 5C23 D20C | wisdom. -- J.R.R. Tolkien -- Please cc all mailing list replies to me, also. = * http://benham.net/index.html[EMAIL PROTECTED] * * * ---* * Debian Developer, Debian Project Secretary, Debian Webmaster * * [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] * * [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] * = pgpBPDeAcu9zA.pgp Description: PGP signature
Re: Guidance while adopting freeamp package
On Tue, Jul 20, 1999 at 08:33:57AM -0700, Darren O. Benham wrote: This is the list... Well, my first questions are: I have been working with the old package, updating it to the latest release of freeamp. I have changed the Standards-Version to 3.0.0 from 2.4.0. The documentation, which I expected to be installed in /usr/share/doc/freeamp, is installed into /usr/doc/freeamp. Is this normal? When I run lintian on the resulting package, I get lots of errors such as: E: freeamp: unstripped-binary-or-object usr/lib/freeamp/plugins/freeamp-linux.ui ... E: freeamp: shlib-with-non-pic-code usr/lib/freeamp/plugins/freeamp-linux.ui ... E: freeamp: shlib-with-executable-bit usr/lib/freeamp/plugins/freeamp-linux.ui 0755 ... E: freeamp: no-shlibs-control-file usr/lib/freeamp/plugins/freeamp-linux.ui ... (The ...'s are just the same error repeated for another one of the plugins.) What should I do about this? This was also present in the original version of the package I am adopting. Is this really an error, and if so, what do I change to fix this? Thanks for any help. Please cc all mailing list replies to me, also. You are using mutt and have the Mail-Followup-To: header set to debian-mentors@lists.debian.org, which mutt does automatically for you unless you add unset followup_to to your .muttrc. If mutt (which I also use) sees this header, it will not cc you, even if I select group reply to your message. If you really wish cc's of your reply's, you should unset this variable. -- Ian Peters | GnuPG Key ID 5C23D20C| He that breaks a thing to find out [EMAIL PROTECTED] | E584 2558 FAC3 BEAB EFAC | what it is has left the path of [EMAIL PROTECTED] | FC74 CFED 7E24 5C23 D20C | wisdom. -- J.R.R. Tolkien pgpuanWkfeSzA.pgp Description: PGP signature
Re: Guidance while adopting freeamp package
On Tue, Jul 20, 1999 at 02:28:49PM -0400, Ian Peters wrote: Well, my first questions are: I have been working with the old package, updating it to the latest release of freeamp. I have changed the Standards-Version to 3.0.0 from 2.4.0. The documentation, which I expected to be installed in /usr/share/doc/freeamp, is installed into /usr/doc/freeamp. Is this normal? It is if you are using debhelper. It also means the Standards-Version is *NOT* 3.0.0. You'll have to install docs and manpages manually to achieve that or stay at 2.5.x until debhelper is upgraded (no idea when). When I run lintian on the resulting package, I get lots of errors such as: E: freeamp: unstripped-binary-or-object usr/lib/freeamp/plugins/freeamp-linux.ui ... E: freeamp: shlib-with-non-pic-code usr/lib/freeamp/plugins/freeamp-linux.ui ... E: freeamp: shlib-with-executable-bit usr/lib/freeamp/plugins/freeamp-linux.ui 0755 ... E: freeamp: no-shlibs-control-file usr/lib/freeamp/plugins/freeamp-linux.ui ... (The ...'s are just the same error repeated for another one of the plugins.) What should I do about this? This was also present in the original version of the package I am adopting. Is this really an error, and if so, what do I change to fix this? I don't know enough about freeamp to comment on this... -- Please cc all mailing list replies to me, also. = * http://benham.net/index.html[EMAIL PROTECTED] * * * ---* * Debian Developer, Debian Project Secretary, Debian Webmaster * * [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] * * [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] * = pgpouDsnxSnLH.pgp Description: PGP signature
Re: Guidance while adopting freeamp package
On Tue, Jul 20, 1999 at 02:28:49PM -0400, Ian Peters wrote: I have been working with the old package, updating it to the latest release of freeamp. I have changed the Standards-Version to 3.0.0 from 2.4.0. The documentation, which I expected to be installed in /usr/share/doc/freeamp, is installed into /usr/doc/freeamp. Is this normal? Debhelper hasn't yet converted to full FHS compliance. Let's wait and see. When I run lintian on the resulting package, I get lots of errors such as: E: freeamp: unstripped-binary-or-object usr/lib/freeamp/plugins/freeamp-linux.ui E: freeamp: shlib-with-non-pic-code usr/lib/freeamp/plugins/freeamp-linux.ui E: freeamp: shlib-with-executable-bit usr/lib/freeamp/plugins/freeamp-linux.ui 0755 E: freeamp: no-shlibs-control-file usr/lib/freeamp/plugins/freeamp-linux.ui You do know that you can get explanations of all these errors by using the '-i' option of lintian? What should I do about this? This was also present in the original version of the package I am adopting. Is this really an error, and if so, what do I change to fix this? If possible (if they will function properly after it), strip them, according to the Policy guidelines. Compile them with the -fPIC option for the linker to get rid of the second error. chmod -x them to get rid of the third, and ignore the fourth error if no other library/executable will link to these files outside your package. It would be good to provide us with some more information - what kind of plug-ins are they actually? Please cc all mailing list replies to me, also. You are using mutt and have the Mail-Followup-To: header set to debian-mentors@lists.debian.org, which mutt does automatically for you unless you add unset followup_to to your .muttrc. If mutt (which I also use) sees this header, it will not cc you, even if I select group reply to your message. If you really wish cc's of your reply's, you should unset this variable. Hm, cool. I noticed this header, but I don't know how to edit it 'in-place', i.e. on the screen where I'm editing other headers, just before sending the message. Is there such option? Or can I just use 'E' and add it myself (that is a bit painful)? -- enJoy -*/\*- spelled 'iosip', or simply 'joseph'
Adopting a package
I've got a feeling I'm missing something really obvious here. I'd like to adopt the orphaned mpich package, so I mailed the wnpp. I first mailed them a bit over a week ago, but I was a bit confused (I hadn't properly read the documentation at the top of the page) so I sent another message earlier this week. The list appears to have been updated in the interim, so it seems that someone is looking at the mailbox. I haven't heard anything at all back, so I'm wondering if I've been going about this in completely the wrong way or if I just ought to be more patient? -- Mark Brown mailto:[EMAIL PROTECTED] (Trying to avoid grumpiness) http://www.tardis.ed.ac.uk/~broonie/ EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/
Re: Adopting a package
On Fri, 4 Dec 1998, Mark Brown wrote: I've got a feeling I'm missing something really obvious here. I'd like to adopt the orphaned mpich package, so I mailed the wnpp. I first mailed them a bit over a week ago, but I was a bit confused (I hadn't properly read the documentation at the top of the page) so I sent another message earlier this week. The list appears to have been updated in the interim, so it seems that someone is looking at the mailbox. I haven't heard anything at all back, so I'm wondering if I've been going about this in completely the wrong way or if I just ought to be more patient? Hello, I am new here so hello to all first! I had a similar experience: Last week I sent a message to wnpp that I want to become a debian-developer and maintain a new package of the harddisk-recording program slab! But no answer so far... Should I resent the post or wait another week? btw: I am going to be a developer soon, and any help is welcome. :-) At the moment I am on the path to an debian-official that means I will meet somebody to confirm my existance and the validity of my pgp-key which I generated a few hours ago Olaf -- -- Olaf Stetzer -- EC/JRC/Institute for Transuranium Elements -- - email to: [EMAIL PROTECTED] or [EMAIL PROTECTED] - -- Jazz is not dead, it just smells funny. Frank Zappa -- --
Re: Adopting a package
*-Mark Brown [EMAIL PROTECTED] | | I've got a feeling I'm missing something really obvious here. I'd like | to adopt the orphaned mpich package, so I mailed the wnpp. I first | mailed them a bit over a week ago, but I was a bit confused (I hadn't | properly read the documentation at the top of the page) so I sent | another message earlier this week. The list appears to have been | updated in the interim, so it seems that someone is looking at the | mailbox. | | I haven't heard anything at all back, so I'm wondering if I've been | going about this in completely the wrong way or if I just ought to be | more patient? A better way may be to post your intent on -devel. wnpp doesn't really hand out packages, he just tries to keep track of what's needed. If noone objects you can mail wnpp and say that you have taken over the package. -- The only way tcsh rocks is when the rocks are attached to its feet in the deepest part of a very deep lake. (Linus Torvalds) [EMAIL PROTECTED] [-: .elOle. :-] [EMAIL PROTECTED]
