Re: packages for adoption: icu, tiff, xerces-c, psutils
On Wed, Feb 11, 2015 at 12:02 PM, Richard Winters r...@mmogp.com wrote: I'm not a 'debian' maintainer or developer...total newbie to alioth - but I'm a c++ developer with over 10 years experience. I'm experienced with linux and more specifically debian development (just not officially). That said I'd love to get involved with Debian development - I love debian and live by it. Anyone willing to lemme help out would be great. I check on alioth often...projects never seem to be posted for help...as a newbie I'm confused how to get started - I've read documentation yet most of these emails looking for helping or specifying a package to be orphaned require a dev or maintainersome of the packages I've looked into helping out with either dont have a buglist or are severely old and have dozens of helpers already. I offer my help here because I tend to need the ICU packages for building various things...if its gonna be orphaned I'd rather help out... Take a look at the how-can-i-help package to identify potential areas where you can contribute. For example, % how-can-i-help --show newcomer,RFH % how-can-i-help --old | less More details can be found in man how-can-i-help. You can install this by apt-get install how-can-i-help. raju -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CABpbYaeBavGAkiY1HzO_a3majhfZgQU2m3Z=0wbth3w56ya...@mail.gmail.com
Re: packages for adoption: icu, tiff, xerces-c, psutils
Hello Kamaraju, Thank you for that information I am checking it out at this time! Best, *Richard B. Winters* On Sat, Feb 14, 2015 at 10:51 AM, kamaraju kusumanchi raju.mailingli...@gmail.com wrote: On Wed, Feb 11, 2015 at 12:02 PM, Richard Winters r...@mmogp.com wrote: I'm not a 'debian' maintainer or developer...total newbie to alioth - but I'm a c++ developer with over 10 years experience. I'm experienced with linux and more specifically debian development (just not officially). That said I'd love to get involved with Debian development - I love debian and live by it. Anyone willing to lemme help out would be great. I check on alioth often...projects never seem to be posted for help...as a newbie I'm confused how to get started - I've read documentation yet most of these emails looking for helping or specifying a package to be orphaned require a dev or maintainersome of the packages I've looked into helping out with either dont have a buglist or are severely old and have dozens of helpers already. I offer my help here because I tend to need the ICU packages for building various things...if its gonna be orphaned I'd rather help out... Take a look at the how-can-i-help package to identify potential areas where you can contribute. For example, % how-can-i-help --show newcomer,RFH % how-can-i-help --old | less More details can be found in man how-can-i-help. You can install this by apt-get install how-can-i-help. raju -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CABpbYaeBavGAkiY1HzO_a3majhfZgQU2m3Z=0wbth3w56ya...@mail.gmail.com
Re: packages for adoption: icu, tiff, xerces-c, psutils
Jay Berkenbilt writes (packages for adoption: icu, tiff, xerces-c, psutils): The other two packages are relatively low-effort packages to maintain. The psutils package is dead upstream though there is someone out there who might be interested in taking over upstream. I would introduce him to any new maintainer. The xerces-c package is a library package but a pretty easy one as they go. It has few downstream packages within debian and gets very infrequent upstream releases. I regularly use psutils and would be happy to take it on. I guess we should wait until after jessie before formalising this with an upload. Ian. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/21724.39472.998719.247...@chiark.greenend.org.uk
Re: packages for adoption: icu, tiff, xerces-c, psutils
Ian Jackson ijack...@chiark.greenend.org.uk wrote: Jay Berkenbilt writes (packages for adoption: icu, tiff, xerces-c, psutils): The other two packages are relatively low-effort packages to maintain. The psutils package is dead upstream though there is someone out there who might be interested in taking over upstream. I would introduce him to any new maintainer. The xerces-c package is a library package but a pretty easy one as they go. It has few downstream packages within debian and gets very infrequent upstream releases. I regularly use psutils and would be happy to take it on. That's great! Go ahead and retitle the RFA to ITA. I guess we should wait until after jessie before formalising this with an upload. Yeah, unlike tiff and icu which have pending rc bugs that can hopefully be fixed before jessie by my successor, psutils is not likely to have any issues like that. Feel free to switch RFA to ITA and upload right after jessie is released. Thanks! -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150212163857.3019399151.qww314...@jberkenbilt-linux.appiancorp.com
Re: packages for adoption: icu, tiff, xerces-c, psutils
JFTR I sent email to tiff RFA and I am willing to take over it. Thank you, Jay, for all your hardwork on libtiff4-libtiff5 transition (and also for the rest of your packages). If you don't get any volunteers for the rest, please ping here and me again after jessie release (instead of orphaning them). Cheers, Ondrej On Wed, Feb 11, 2015, at 17:01, Jay Berkenbilt wrote: I have four packages that I'd like to give away. If I don't find a new maintainer for them, I may orphan them after jessie is released since I no longer have time to maintain them. I have been maintaining these packages for a long time (over 10 years in some cases), and all four packages are in good shape. I have filed RFA bugs for each package. Two of the packages, tiff and icu, are important library packages with lots of reverse dependencies and frequent security issues. They are fairly low effort to maintain but require occasional surges of effort. In particular, ICU gets two non-binary-compatible (soname bump) upstream releases each year and requires regular coordination with the release team and often some of its downstream packages. The tiff packages are mostly inactive upstream but do get occasional upstream releases. The other two packages are relatively low-effort packages to maintain. The psutils package is dead upstream though there is someone out there who might be interested in taking over upstream. I would introduce him to any new maintainer. The xerces-c package is a library package but a pretty easy one as they go. It has few downstream packages within debian and gets very infrequent upstream releases. All four packages are maintained with git-buildpackage, but right now their repositories are in github because I switched all my packages over to git-buildpackage during a time when alioth had extended downtime. Pushing the repos over to a better/additional place is trivial, of course. I have provided additional information in the RFA bug reports: icu: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777694 tiff: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777695 xerces-c: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777698 psutils: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777699 -- Jay Berkenbilt q...@debian.org Email had 1 attachment: + signature.asc 1k (application/pgp-signature) -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1423672075.1544800.226222857.2c551...@webmail.messagingengine.com
Re: packages for adoption: icu, tiff, xerces-c, psutils
Ondřej Surý ond...@sury.org wrote: JFTR I sent email to tiff RFA and I am willing to take over it. Thank you, Jay, for all your hardwork on libtiff4-libtiff5 transition (and also for the rest of your packages). If you don't get any volunteers for the rest, please ping here and me again after jessie release (instead of orphaning them). Cheers, Ondrej This is great. Thanks for the response. Feel free to take over tiff at any time. There are open security issues that I haven't had time to take care of yet. If you take care of the security issues, you can grab the packages at that time. If you use git-buildpackage and want to take over the repos, you can get https://github.com/jberkenbilt/debian-tiff and push it to wherever. Obviously don't fork it on github since then I won't be able to delete my copy. I could be open to giving up vips and nip2 as well. They are very low effort, and upstream is super-responsive, so I can probably still handle them even with almost no time, but if you wanted them, I'd be open to it. -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2015025047.0225557611.qww314...@jberkenbilt-linux.appiancorp.com
Re: packages for adoption: icu, tiff, xerces-c, psutils
Hey there: Posting again because I didn't hit reply-all (sorry, but would rather advertise Im available for help to the whole mailing list.) I'm not a 'debian' maintainer or developer...total newbie to alioth - but I'm a c++ developer with over 10 years experience. I'm experienced with linux and more specifically debian development (just not officially). That said I'd love to get involved with Debian development - I love debian and live by it. Anyone willing to lemme help out would be great. I check on alioth often...projects never seem to be posted for help...as a newbie I'm confused how to get started - I've read documentation yet most of these emails looking for helping or specifying a package to be orphaned require a dev or maintainersome of the packages I've looked into helping out with either dont have a buglist or are severely old and have dozens of helpers already. I offer my help here because I tend to need the ICU packages for building various things...if its gonna be orphaned I'd rather help out... Samples of work can be provided if needed. *Richard B. Winters* Chairman CEO *Massively Modified, Inc.* MMod | Kwaeri *Phone*: (607) 431-8726 *Fax: *(877) 267-0412 *WebGL Engine (In Progress):* kwaeri Engine http://kwaeri.mmogp.com/ On Wed, Feb 11, 2015 at 11:01 AM, Jay Berkenbilt q...@debian.org wrote: I have four packages that I'd like to give away. If I don't find a new maintainer for them, I may orphan them after jessie is released since I no longer have time to maintain them. I have been maintaining these packages for a long time (over 10 years in some cases), and all four packages are in good shape. I have filed RFA bugs for each package. Two of the packages, tiff and icu, are important library packages with lots of reverse dependencies and frequent security issues. They are fairly low effort to maintain but require occasional surges of effort. In particular, ICU gets two non-binary-compatible (soname bump) upstream releases each year and requires regular coordination with the release team and often some of its downstream packages. The tiff packages are mostly inactive upstream but do get occasional upstream releases. The other two packages are relatively low-effort packages to maintain. The psutils package is dead upstream though there is someone out there who might be interested in taking over upstream. I would introduce him to any new maintainer. The xerces-c package is a library package but a pretty easy one as they go. It has few downstream packages within debian and gets very infrequent upstream releases. All four packages are maintained with git-buildpackage, but right now their repositories are in github because I switched all my packages over to git-buildpackage during a time when alioth had extended downtime. Pushing the repos over to a better/additional place is trivial, of course. I have provided additional information in the RFA bug reports: icu: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777694 tiff: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777695 xerces-c: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777698 psutils: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777699 -- Jay Berkenbilt q...@debian.org
Re: packages for adoption: icu, tiff, xerces-c, psutils
Jay, Thank you for that good sir, I will do just that (I'm sure by the time I wrap my head around orchestrating a transition of ICU to version 54.1; someone would have taken over - and perhaps I'd be able to contribute through them at that time and work my way up to a co/maintainer over time). Really appreciate your response - your first paragraph actually motivated me even more. Cheers - *Richard B. Winters* On Wed, Feb 11, 2015 at 1:26 PM, Jay Berkenbilt q...@debian.org wrote: My suggestion would be to read through the material at https://wiki.debian.org/DebianMaintainer and take it from there. Sounds like you're about where I was when I started with Debian in 2003: I was experienced Linux/C/C++ developer using tiff, xerces, and icu at work. I took over the packages with the help of sponsors and initially as a co-maintainer and used my experience there toward becoming a full debian developer about 18 months later. I'm afraid I don't have time or energy to help with the sponsorship, but maybe you can find someone who can take over maintaining icu with the intention of sponsoring you or who can sponsor you to take over maintenance. I got my start with the tiff packages by managing a transition that corrected an inadvertent binary compatibility problem without an soname bump, and through that, earned enough of a reputation to be able to move through the new maintainer process pretty easily. ICU presents an opportunity to do something similar. Take a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757025. When I created that, ICU 53 was out, but I was not able to get the transition done for jessie. Now ICU 54 is out, and one of the first jobs of icu's next maintainer will be, post jessie, to orchestrate a transition of icu to version 54.1 or whatever is current at the time. This would be a good way to cut your teeth on slightly more advanced package maintenance activities required with library packages. -- Jay Berkenbilt q...@debian.org
Re: packages for adoption: icu, tiff, xerces-c, psutils
Richard Winters r...@mmogp.com wrote: Hey there: Posting again because I didn't hit reply-all (sorry, but would rather advertise Im available for help to the whole mailing list.) I'm not a 'debian' maintainer or developer...total newbie to alioth - but I'm a c++ developer with over 10 years experience. I'm experienced with linux and more specifically debian development (just not officially). That said I'd love to get involved with Debian development - I love debian and live by it. Anyone willing to lemme help out would be great. I check on alioth often...projects never seem to be posted for help...as a newbie I'm confused how to get started - I've read documentation yet most of these emails looking for helping or specifying a package to be orphaned require a dev or maintainersome of the packages I've looked into helping out with either dont have a buglist or are severely old and have dozens of helpers already. I offer my help here because I tend to need the ICU packages for building various things...if its gonna be orphaned I'd rather help out... Samples of work can be provided if needed. My suggestion would be to read through the material at https://wiki.debian.org/DebianMaintainer and take it from there. Sounds like you're about where I was when I started with Debian in 2003: I was experienced Linux/C/C++ developer using tiff, xerces, and icu at work. I took over the packages with the help of sponsors and initially as a co-maintainer and used my experience there toward becoming a full debian developer about 18 months later. I'm afraid I don't have time or energy to help with the sponsorship, but maybe you can find someone who can take over maintaining icu with the intention of sponsoring you or who can sponsor you to take over maintenance. I got my start with the tiff packages by managing a transition that corrected an inadvertent binary compatibility problem without an soname bump, and through that, earned enough of a reputation to be able to move through the new maintainer process pretty easily. ICU presents an opportunity to do something similar. Take a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757025. When I created that, ICU 53 was out, but I was not able to get the transition done for jessie. Now ICU 54 is out, and one of the first jobs of icu's next maintainer will be, post jessie, to orchestrate a transition of icu to version 54.1 or whatever is current at the time. This would be a good way to cut your teeth on slightly more advanced package maintenance activities required with library packages. -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150211132653.0261594103.qww314...@jberkenbilt-linux.appiancorp.com
packages for adoption: icu, tiff, xerces-c, psutils
I have four packages that I'd like to give away. If I don't find a new maintainer for them, I may orphan them after jessie is released since I no longer have time to maintain them. I have been maintaining these packages for a long time (over 10 years in some cases), and all four packages are in good shape. I have filed RFA bugs for each package. Two of the packages, tiff and icu, are important library packages with lots of reverse dependencies and frequent security issues. They are fairly low effort to maintain but require occasional surges of effort. In particular, ICU gets two non-binary-compatible (soname bump) upstream releases each year and requires regular coordination with the release team and often some of its downstream packages. The tiff packages are mostly inactive upstream but do get occasional upstream releases. The other two packages are relatively low-effort packages to maintain. The psutils package is dead upstream though there is someone out there who might be interested in taking over upstream. I would introduce him to any new maintainer. The xerces-c package is a library package but a pretty easy one as they go. It has few downstream packages within debian and gets very infrequent upstream releases. All four packages are maintained with git-buildpackage, but right now their repositories are in github because I switched all my packages over to git-buildpackage during a time when alioth had extended downtime. Pushing the repos over to a better/additional place is trivial, of course. I have provided additional information in the RFA bug reports: icu: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777694 tiff: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777695 xerces-c: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777698 psutils: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777699 -- Jay Berkenbilt q...@debian.org signature.asc Description: PGP signature
Re: a few packages for adoption
On Mon, May 9, 2011 at 7:44 PM, Jay Berkenbilt q...@debian.org wrote: ** Please reply to me directly (or CC me on replies) as I am not currently subscribed to debian-devel. ** I recently became a father of twins and, as such, have less time to work on packages than I used to. While I do plan on keeping some of my packages, there are others I'm interested in finding new maintainers for, if anyone is interested: * ICU: This is ICU4C. I sent another (lengthy) message about it. * xerces-c, xerces-c2: These are two versions of Xerces-C (http://xerces.apache.org). These are generally pretty low effort to maintain, and upstream is helpful and responsive. xerces-c2 is an older version that is no longer really being maintained, and backporting security fixes to it can be very hard, but so far, there hasn't been anything major. xerces-c is the 3.x series and is actively maintained upstream. Note that xerces-c2 has an orphaned reverse dependency (xalan), which you may occasionally need to NMU, though I think I only had to do that one time. * libxml-xerces-perl: This is a Xerces-p, a perl interface to Xerces-c. As far as I can tell, it is dead upstream, and there are better alternatives. At one time, it was the only perl module capable of doing XML validation with both DTD and schema support and with the capability of providing values for default attributes when doing validation, but I haven't actually tried to determine whether that's true for about six or seven years. If no one wants this, I may orphan it or request removal. * psutils: This is a collection of tools including psnup and ps2ps. They are pretty popular, but the project has been dead upstream for a while. psutils is part of all the major distributions, and we all have various patches. I put some effort into trying to synchronize with other distributions a while ago. Our psutils package includes a few other tools that are not strictly part of the upstream distribution, and every now and then, someone posts a bug report asking for some additional utility to be added. Some of the time, there's a licensing reason or some other reason why it won't work out (so you have to be careful when analyzing these requests), but every now and then it works out. I could take care if you sponsor me. Bastien I'll wait a few days to give people a chance to reply. For the xerces packages, I'd probably give preference to the debian SGML/XML group or to other groups maintaining stuff from apache. -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110509134418.322691.qww314159@motoko.argon.local -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTimobUr3yY09=ALU=uqa3wwkr+t...@mail.gmail.com
a few packages for adoption
** Please reply to me directly (or CC me on replies) as I am not currently subscribed to debian-devel. ** I recently became a father of twins and, as such, have less time to work on packages than I used to. While I do plan on keeping some of my packages, there are others I'm interested in finding new maintainers for, if anyone is interested: * ICU: This is ICU4C. I sent another (lengthy) message about it. * xerces-c, xerces-c2: These are two versions of Xerces-C (http://xerces.apache.org). These are generally pretty low effort to maintain, and upstream is helpful and responsive. xerces-c2 is an older version that is no longer really being maintained, and backporting security fixes to it can be very hard, but so far, there hasn't been anything major. xerces-c is the 3.x series and is actively maintained upstream. Note that xerces-c2 has an orphaned reverse dependency (xalan), which you may occasionally need to NMU, though I think I only had to do that one time. * libxml-xerces-perl: This is a Xerces-p, a perl interface to Xerces-c. As far as I can tell, it is dead upstream, and there are better alternatives. At one time, it was the only perl module capable of doing XML validation with both DTD and schema support and with the capability of providing values for default attributes when doing validation, but I haven't actually tried to determine whether that's true for about six or seven years. If no one wants this, I may orphan it or request removal. * psutils: This is a collection of tools including psnup and ps2ps. They are pretty popular, but the project has been dead upstream for a while. psutils is part of all the major distributions, and we all have various patches. I put some effort into trying to synchronize with other distributions a while ago. Our psutils package includes a few other tools that are not strictly part of the upstream distribution, and every now and then, someone posts a bug report asking for some additional utility to be added. Some of the time, there's a licensing reason or some other reason why it won't work out (so you have to be careful when analyzing these requests), but every now and then it works out. I'll wait a few days to give people a chance to reply. For the xerces packages, I'd probably give preference to the debian SGML/XML group or to other groups maintaining stuff from apache. -- Jay Berkenbilt q...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110509134418.322691.qww314159@motoko.argon.local
Re: Real Life hits: need to give up packages for adoption
* Matthias Urlichs [EMAIL PROTECTED] [2006-05-31 07:55]: Still open: * kforth (new Upstream) Can you please file an O: bug? Taken: * festival, speech-tools Franz Pletz Franz, when will you upload? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Life hits: need to give up packages for adoption
On Wed, Jun 07, 2006 at 12:25:27AM -0400, Anthony DeRobertis wrote: Christoph Haas wrote: Yes, of course. Besides some minor things I don't quite like about Subversion ([...] getting out old revisions of a file means typing the full URL for no reason) svn cat -rrev file_name Oh, thanks. I should have tried that. :) Christoph -- ~ ~ .signature [Modified] 1 line --100%--1,48 All signature.asc Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
Christoph Haas wrote: Yes, of course. Besides some minor things I don't quite like about Subversion ([...] getting out old revisions of a file means typing the full URL for no reason) svn cat -rrev file_name works for me... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Life hits: need to give up packages for adoption
Hi,
thanks for the numerous offers and replies.
I forgot to mention that most (if not all) of these are managed with
git. I don't use dpatch or similar tools - managing patches is the SCM's
job.
The archives mostly are on netz.smurf.noris.de; if your package is
not, and you're interested in working with git (or importing into your
own SCM), drop me a line and I'll push it.
The package build script I use is called b.debuild, it's in the
sourcemgr.git archive.
Still open:
* kforth
(new Upstream)
Taken:
* festival, speech-tools
Franz Pletz
* gnutls, gcrypt, libtasn1, libksba
(security-critical, some work required, having a team for these
packages would be ideal)
Andreas Metzler, Eric Doland, James Westby
* NTP server
Christoph Haas, Simon Richter
* libdigest-hmac-perl, libdigest-sha1-perl, libdigest-md2-perl,
libdigest-perl, libio-interface-perl, libio-socket-multicast-perl,
libnet-xwhois-perl, libvideo-capture-v4l-perl
Zak B. Elep
* python-docutils
martin f krafft
* python-imaging
Matthias Klose
* gnulib
Daniel Baumann
* gnupg2[1]
Eric Dorland, Franz Pletz
* hashalot
Adam Borowski
* tcng
Adam Borowski
* ufraw
Hubert Chan
* videogen
Bas Zoetekouw
[1] I agreed with James Troup that the package will revert to him when
gnupg2 is actually ready to supersede gnupg -- whenever *that* is.
(I assume that this will be open to negotiation when the time comes.)
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
I wake up every morning and I wish I were dead, and so does Jim.
[Tammy Fae Bakker]
signature.asc
Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
Hi! You wrote: * videogen (easy pickings) If no one else is interested, I'd like to take this one. It could take me a few weeks to find time to upload though, as Real Life is getting in the way atm. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Life hits: need to give up packages for adoption
Hi, * NTP server (some work required; currently, not-really-maintained by the Debian NTP Team, which consists of zero active members) I'll take it. Simon signature.asc Description: OpenPGP digital signature
Re: Real Life hits: need to give up packages for adoption
On 5/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I am sorry (and not happy with myself) that I've been procrastinating about this for too long. This decision has not been easy. However, I need to focus more on (a) work that actually feeds my kids, and (b) time that is *not* spent hacking. Awww... :( * libdigest-hmac-perl, libdigest-sha1-perl, libdigest-md2-perl, libdigest-perl, libio-interface-perl, libio-socket-multicast-perl, libnet-xwhois-perl, libvideo-capture-v4l-perl I'd like to take these up. Cheers, Zakame -- Zak B. Elep || http://zakame.spunge.org [EMAIL PROTECTED] || [EMAIL PROTECTED] 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Life hits: need to give up packages for adoption
Morning... Matthias, your From: line appears to be missing. Or my MUA is b0rked. On Mon, May 29, 2006 at 09:29:34PM +0200, wrote: * NTP server (some work required; currently, not-really-maintained by the Debian NTP Team, which consists of zero active members) I'd take my chance on this one. There is a large number of bugs open and I believe that this package is very important. Still I'd like to have a co-maintainer for the package. Anyone else interested? I'd create an SVN repository on my server or alioth. Kindly Christoph -- ~ ~ .signature [Modified] 1 line --100%--1,48 All signature.asc Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
Hi, Christoph Haas schrieb: * NTP server (some work required; currently, not-really-maintained by the Debian NTP Team, which consists of zero active members) I'd take my chance on this one. There is a large number of bugs open and I believe that this package is very important. Still I'd like to have a co-maintainer for the package. Anyone else interested? I'd create an SVN repository on my server or alioth. I have no problem with co-maintenance, but I'd have a problem with svn. Simon signature.asc Description: OpenPGP digital signature
Re: Real Life hits: need to give up packages for adoption
On Tue, May 30, 2006 at 11:25:58AM +0200, Simon Richter wrote: Christoph Haas schrieb: * NTP server (some work required; currently, not-really-maintained by the Debian NTP Team, which consists of zero active members) I'd take my chance on this one. There is a large number of bugs open and I believe that this package is very important. Still I'd like to have a co-maintainer for the package. Anyone else interested? I'd create an SVN repository on my server or alioth. I have no problem with co-maintenance, but I'd have a problem with svn. Suggestions? (Unless there are further volunteers we can as well take this to PM.) Kindly Christoph -- ~ ~ .signature [Modified] 1 line --100%--1,48 All signature.asc Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
Simon Richter [EMAIL PROTECTED] writes: Hi, Christoph Haas schrieb: * NTP server (some work required; currently, not-really-maintained by the Debian NTP Team, which consists of zero active members) I'd take my chance on this one. There is a large number of bugs open and I believe that this package is very important. Still I'd like to have a co-maintainer for the package. Anyone else interested? I'd create an SVN repository on my server or alioth. I have no problem with co-maintenance, but I'd have a problem with svn. Maybe bzr or git? -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - Microsoft gives you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Life hits: need to give up packages for adoption
On Tue, May 30, 2006 at 10:09:07AM -0300, Otavio Salvador wrote: Simon Richter [EMAIL PROTECTED] writes: Hi, Christoph Haas schrieb: * NTP server (some work required; currently, not-really-maintained by the Debian NTP Team, which consists of zero active members) I'd take my chance on this one. There is a large number of bugs open and I believe that this package is very important. Still I'd like to have a co-maintainer for the package. Anyone else interested? I'd create an SVN repository on my server or alioth. I have no problem with co-maintenance, but I'd have a problem with svn. Maybe bzr or git? I'm currently looking into several systems. Usually I use Subversion and svn-buildpackage but due to a lot of trouble with svn-buildpackage I have moved away from repositories for my Debian packages lately. Darcs looks like a nice competitor but has some issues regarding checking in changes automatically (might as well be my ignorance but it sounds like I need weird scripts and a .procmailrc to merge changes automatically). For git and bzr there don't seem to be sophisticated tools to build packages (*-buildpackage). svn-buildpackage for example keeps the upstream tarballs in one directory but still builds from the trunk/ which is pretty nice. Well, well, all the RCS philosophy again. Too much choice. Kindly Christoph -- ~ ~ .signature [Modified] 1 line --100%--1,48 All signature.asc Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
Christoph Haas wrote: Darcs looks like a nice competitor but has some issues regarding checking in changes automatically (might as well be my ignorance but it sounds like I need weird scripts and a .procmailrc to merge changes automatically). You don't *need* them; you can choose to do that, but you can also choose otherwise. There are two ways to give contributors commit access in darcs. (I'm using quotes because in Darcs, commit is an ambiguous term and is usually avoided; I'm using it here to mean incorporating a change in a special project-wide shared repository.) *** Way One --- Set up an email address which feeds messages to darcs. Darcs is capable of checking GnuPG signatures in these mails and only allowing known keys to commit. The contributor commits by using the darcs send command. The upside is that the contributors do not need shell access to the server. The downside is that setting this up is not very easy. Way Two --- Give contributors shell access to the server; make the shared repository writable by all these accounts. The contributor commits by using the darcs push command. The upside is that this is very easy to set up. The downside is that you need to give contributors shell access. (I suppose a restricted shell is possible. I haven't investigated this.) *** I personally prefer Way Two. I have tried Way One, but it isn't worth the trouble most of the time. What makes darcs special in my opinion is its support for second-class contributors: anybody can darcs send stuff to the project mailing list (if you've set stuff up for this; it's not very hard), the email is both human- and computer-readable: it can be eyeballed and it can be fed directly to darcs to incorporate the change to the local repository (from which it can be committed to the shared repository, if this is desired and one has the necessary commit privs). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Life hits: need to give up packages for adoption
On Mon, May 29, 2006 at 09:29:34PM +0200, wrote: * libdigest-hmac-perl, libdigest-sha1-perl, libdigest-md2-perl, libdigest-perl, libio-interface-perl, libio-socket-multicast-perl, libnet-xwhois-perl, libvideo-capture-v4l-perl (easy pickings; check for new Upstream) I guess these packages would fit in the Debian Perl Group's collection. If there are no objections I would start to move them over. gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `-NP: Dire Straits: Walk Of Life signature.asc Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
On Mon, 29 May 2006 21:29:34 +0200, [EMAIL PROTECTED] (Unknown) said: * ufraw (need to package new Upstream; easy) I can take this if nobody else wants it. -- Hubert Chan - email Jabber: [EMAIL PROTECTED] - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA (Key available at wwwkeys.pgp.net) Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Life hits: need to give up packages for adoption
On Tue, May 30, 2006 at 01:46:30AM -0700, Zak B. Elep wrote: * libdigest-hmac-perl, libdigest-sha1-perl, libdigest-md2-perl, libdigest-perl, libio-interface-perl, libio-socket-multicast-perl, libnet-xwhois-perl, libvideo-capture-v4l-perl I'd like to take these up. Oops, I just saw your mail now after writing my own offer. Please just go ahead; unless you want to maintain the packages within the Debian Perl Group, of course ;-) gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `-NP: Bob Dylan: I want you signature.asc Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
Christoph Haas wrote: I'm currently looking into several systems. Usually I use Subversion and svn-buildpackage but due to a lot of trouble with svn-buildpackage I have moved away from repositories for my Debian packages lately. Out of curiousity, what problems have you encountered with svn-buildpackage? Personally, I have transitioned all the packages that I maintain solo into it, as well as some of the package maintenance teams I am on use it. I have not encountered any problems. The only problem I have encountered so far is that the Horde team uses Arch, which I simply cannot understand. I have spent quite a while reading through the documentation and messing with it, but Arch seems to me to not make any rational sense. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto signature.asc Description: OpenPGP digital signature
Re: Real Life hits: need to give up packages for adoption
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In article [EMAIL PROTECTED] (gmane.linux.debian.devel.general) you wrote: On (29/05/06 21:29), [EMAIL PROTECTED] wrote: [...] * gnutls, gcrypt, libtasn1, libksba (security-critical, some work required, having a team for these packages would be ideal) I would like to be part of the team for these packages. I had already invested a little bit of time in these, http://downhill.aus.cc/debian/misc/ and would be happy to at least give the packages a kick to get them into shape. cu and- My elan might fail after some time, so a team really looks good. -reas - -- The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal vision of the emperor's, and its inclusion in this work does not constitute tacit approval by the author or the publisher for any such projects, howsoever undertaken.(c) Jasper Ffforde -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEfIoXHTOcZYuNdmMRAouEAJ9cVXJeNXc6PBXlgd0MIkdsvRNTkQCcCrR+ dgqv9lYYtiGcGOD9JZxr7+s= =FAh9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Life hits: need to give up packages for adoption
On Tue, May 30, 2006 at 01:45:10PM -0400, Roberto C. Sanchez wrote: Christoph Haas wrote: I'm currently looking into several systems. Usually I use Subversion and svn-buildpackage but due to a lot of trouble with svn-buildpackage I have moved away from repositories for my Debian packages lately. Out of curiousity, what problems have you encountered with svn-buildpackage? Personally, I have transitioned all the packages that I maintain solo into it, as well as some of the package maintenance teams I am on use it. I have not encountered any problems. Yes, of course. Besides some minor things I don't quite like about Subversion (merging looks like black magic for me and getting out old revisions of a file means typing the full URL for no reason) these are the actual problems I encountered with svn-buildpackage: * svn-upgrade Upgrading from a new upstream tarball has never worked here. Matthijs Mohlmann and I are maintaining the pdns (PowerDNS) package in a Subversion repository. That software isn't trivial but it's also no rocket science. Still svn-upgrade choked and left us alone like something didn't work half way - what do you want to do? and we ended up with a borked repository. Up to now we made a backup of the repository beforehand and took our chances. I believe we merged in the upstream changes manually. I didn't want to understand what svn-upgrade is doing under the hood so I felt left alone there. * svn-inject Injecting new packages through svn-inject fails here. I get errors about the MKCOL method not being allowed on the remote WebDAV server. Perhaps it's a problem that the Apache runs on Sarge while I'm developing on Sid. * svn-buildpackage The main script for building a package works well here. Just that the build-area doesn't seem to be tidied up automatically. A few failed attempts of building a package and that directory grows here. But building a package from the repository through pbuilder is very nice. Kudos to Eduard Bloch though. The scripts are pretty sophisticated. And I already spent some time getting it working with pbuilder (see [1]). In the end I still favor Subversion over any other RCS. Although Simon Richter made me try Git today. And I like to try out new things so I can find better arguments against it. :) The only problem I have encountered so far is that the Horde team uses Arch, which I simply cannot understand. I have spent quite a while reading through the documentation and messing with it, but Arch seems to me to not make any rational sense. Neither to me. Bazaar (as made and used by the Ubuntu staff) seems to be a better arch. Still I couldn't be convinced to use it. Disclaimer: I'm not a Subversion guru. So I might as well just be ignorant. Kindly Christoph [1] http://workaround.org/moin/SvnBuildpackage -- ~ ~ .signature [Modified] 1 line --100%--1,48 All signature.asc Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
On Tue, May 30, 2006 at 08:48:14PM +0200, I (Christoph Haas) wrote: * svn-inject Injecting new packages through svn-inject fails here. I get errors about the MKCOL method not being allowed on the remote WebDAV server. Perhaps it's a problem that the Apache runs on Sarge while I'm developing on Sid. It appears like MKCOL returns a 405 when a collection (apparently a directory on the DAV server - I'm not a DAV expert) is already existing. So removing the whole repository, re-creating it and then running svn-inject works. I was sure that I injected into a blank repository - apparently it wasn't totally blank. Another strange issue is that the tarballs/ directory for upstream tarballs it not automatically created and needs to be adjusted by hand by editing the trunk/.svn/deb-layout file. Or it's just me not understanding the mergeWithUpstream setting correctly. Kindly Christoph -- ~ ~ .signature [Modified] 1 line --100%--1,48 All signature.asc Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
wrote: * gnulib (easy pickings; need to package new Upstream from CVS, every month or so) I'll take that. -- 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: Real Life hits: need to give up packages for adoption
Christoph Haas wrote: Yes, of course. Besides some minor things I don't quite like about Subversion (merging looks like black magic for me and getting out old revisions of a file means typing the full URL for no reason) these are the actual problems I encountered with svn-buildpackage: * svn-upgrade Upgrading from a new upstream tarball has never worked here. Matthijs Mohlmann and I are maintaining the pdns (PowerDNS) package in a Subversion repository. That software isn't trivial but it's also no rocket science. Still svn-upgrade choked and left us alone like something didn't work half way - what do you want to do? and we ended up with a borked repository. Up to now we made a backup of the repository beforehand and took our chances. I believe we merged in the upstream changes manually. I didn't want to understand what svn-upgrade is doing under the hood so I felt left alone there. I guess I will need to watch out for that. I have only had one upstream upgrade so far since using svn-buildpackage, and I have not had this happen. Though, many of my packages are trivial to maintain. * svn-inject Injecting new packages through svn-inject fails here. I get errors about the MKCOL method not being allowed on the remote WebDAV server. Perhaps it's a problem that the Apache runs on Sarge while I'm developing on Sid. Not sure. I have shell access and use the svn+ssh method for my Subversion access. * svn-buildpackage The main script for building a package works well here. Just that the build-area doesn't seem to be tidied up automatically. A few failed attempts of building a package and that directory grows here. But building a package from the repository through pbuilder is very nice. I have noticed this as well. Kudos to Eduard Bloch though. The scripts are pretty sophisticated. And I already spent some time getting it working with pbuilder (see [1]). Yes, it is just too bad that they did not use a respectable language, like Python. As it is, there are many features I would like to see added, but all I can do is file wishlist bugs, as I don't anything about Perl besides how to spell it. Your link on getting svn-buildpackage and pbuilder working was excellent. I used as a guide as well when I needed to integrate the two. In the end I still favor Subversion over any other RCS. Although Simon Richter made me try Git today. And I like to try out new things so I can find better arguments against it. :) I agree that (and pardon my paraphrasing), subversion is the worst form of revision control, except for all the others that have been tried. Personally, none of the others make sense. The only problem I have encountered so far is that the Horde team uses Arch, which I simply cannot understand. I have spent quite a while reading through the documentation and messing with it, but Arch seems to me to not make any rational sense. Neither to me. Bazaar (as made and used by the Ubuntu staff) seems to be a better arch. Still I couldn't be convinced to use it. Disclaimer: I'm not a Subversion guru. So I might as well just be ignorant. Ditto. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto signature.asc Description: OpenPGP digital signature
Re: Real Life hits: need to give up packages for adoption
On Mon, May 29, 2006 at 09:29:34PM +0200, Matthias Urlichs wrote: * gnulib (easy pickings; need to package new Upstream from CVS, every month or so) I ported quite a lot of C software between IRIX/SunOS/AIX/Linux, so I'll take it. * tcng (some clean-up required) I have some idea about bare tc -- two local ISPs run my scripts that manage traffic shaping according to the customers' databases; however, I haven't used tcng itself -- it looks interesting, though. Unless someone else steps up, I can do it. * hashalot (easy pickings) Trivial; I can grab it if no one else does -- but if someone actually uses it, that person of course has a priority. Whee? -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Life hits: need to give up packages for adoption
On Tue, 2006-05-30 at 20:48 +0200, Christoph Haas wrote: * svn-upgrade Upgrading from a new upstream tarball has never worked here. Matthijs Mohlmann and I are maintaining the pdns (PowerDNS) package in a Subversion repository. That software isn't trivial but it's also no rocket science. Still svn-upgrade choked and left us alone like something didn't work half way - what do you want to do? and we ended up with a borked repository. Up to now we made a backup of the repository beforehand and took our chances. I believe we merged in the upstream changes manually. I didn't want to understand what svn-upgrade is doing under the hood so I felt left alone there. Does the upstream tar ball contain symbolic links? svn-upgrade calls svn_load_dirs, a contrib script from the subversion package, to get the new upstream version into the repository. Before version 1.3.0-1, svn_load_dirs didn't know how to handle symbolic links. Cheers, Til signature.asc Description: This is a digitally signed message part
Real Life hits: need to give up packages for adoption
Hi,
My inability to find enough time to focus on package maintainance
has been *way* too persistent. I therefore need to give up my packages
for adoption, for the time being.
I am sorry (and not happy with myself) that I've been procrastinating
about this for too long. This decision has not been easy. However,
I need to focus more on (a) work that actually feeds my kids, and
(b) time that is *not* spent hacking.
Before filing Orphan bugs, I'd like to ask whether anybody wants to
tackle these packages. The Easy Pickings stuff would be ideal start-up
work for new maintainers / mentorship; some of the others do need some
work.
* gnutls, gcrypt, libtasn1, libksba
(security-critical, some work required, having a team for these
packages would be ideal)
* festival, speech-tools
(some clean-up work, new major upstream release pending)
* NTP server
(some work required; currently, not-really-maintained by the Debian
NTP Team, which consists of zero active members)
* libdigest-hmac-perl, libdigest-sha1-perl, libdigest-md2-perl,
libdigest-perl, libio-interface-perl, libio-socket-multicast-perl,
libnet-xwhois-perl, libvideo-capture-v4l-perl
(easy pickings; check for new Upstream)
* python-docutils
(easy pickings)
* python-imaging
(easy pickings)
* gnulib
(easy pickings; need to package new Upstream from CVS, every month or so)
* gnupg2
(some clean-up work)
* hashalot
(easy pickings)
* kforth
(new Upstream)
* tcng
(some clean-up required)
* ufraw
(need to package new Upstream; easy)
* videogen
(easy pickings)
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
Incorrigible punster -- Do not incorrige.
signature.asc
Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
also sprach [2006.05.29.2129 +0200]: * python-docutils (easy pickings) I'd like to take that on. I am already co-maintainer. Other co-maintainers welcome. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system windoze nt crashed. i am the blue screen of death. no one hears your screams. signature.asc Description: Digital signature (GPG/PGP)
Re: Real Life hits: need to give up packages for adoption
On Mon, May 29, 2006 at 09:29:34PM +0200, wrote: * festival, speech-tools (some clean-up work, new major upstream release pending) [..] * gnupg2 (some clean-up work) I'd be interested in taking these three, especially gnupg2 as I'm using it on a daily basis. Thanks, Franz -- Franz Pletz \ Lots of the basis of the open source movement www: http://franz-pletz.org/ \ come from procrastinating students. email: [EMAIL PROTECTED] \ -- Andrew Tridgell signature.asc Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
* () wrote: Hi, My inability to find enough time to focus on package maintainance has been *way* too persistent. I therefore need to give up my packages for adoption, for the time being. I am sorry (and not happy with myself) that I've been procrastinating about this for too long. This decision has not been easy. However, I need to focus more on (a) work that actually feeds my kids, and (b) time that is *not* spent hacking. Before filing Orphan bugs, I'd like to ask whether anybody wants to tackle these packages. The Easy Pickings stuff would be ideal start-up work for new maintainers / mentorship; some of the others do need some work. * gnupg2 (some clean-up work) I'd like to take this, as it ties into some of my work packaging OpenSC quite nicely. -- Eric Dorland [EMAIL PROTECTED] ICQ: #61138586, Jabber: [EMAIL PROTECTED] 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6 -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ G e h! r- y+ --END GEEK CODE BLOCK-- signature.asc Description: Digital signature
Re: Real Life hits: need to give up packages for adoption
On (29/05/06 21:29), [EMAIL PROTECTED] wrote: Hi, My inability to find enough time to focus on package maintainance has been *way* too persistent. I therefore need to give up my packages for adoption, for the time being. That's a shame. * gnutls, gcrypt, libtasn1, libksba (security-critical, some work required, having a team for these packages would be ideal) I would like to be part of the team for these packages. James -- James Westby [EMAIL PROTECTED] http://jameswestby.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Real Life hits: need to give up packages for adoption
* python-imaging (easy pickings) as former maintainer of this package and having used that as an example package, I'd like to maintain this one again. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: {Arch,OCaml,Python,Mono} Packages for Adoption
John Goerzen [EMAIL PROTECTED] writes: tla-tools I can take this one, if noone else wants it. Regards, Rotty -- Andreas Rottmann | [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62 v2sw7MYChw5pr5OFma7u7Lw2m5g/l7Di6e6t5BSb7en6g3/5HZa2Xs6MSr1/2p7 hackerkey.com Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald E. Knuth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: {Arch,OCaml,Python,Mono} Packages for Adoption
Andreas Rottmann [EMAIL PROTECTED] writes: tla-tools I can take this one, if noone else wants it. If you do, could you update the debian package to the latest upstream version? Thanks, -Miles -- Next to fried food, the South has suffered most from oratory. -- Walter Hines Page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: {Arch,OCaml,Python,Mono} Packages for Adoption
On Wed, Apr 27, 2005 at 11:46:37AM +0200, Andreas Rottmann wrote: John Goerzen [EMAIL PROTECTED] writes: tla-tools I can take this one, if noone else wants it. Manoj has also expressed interest; could you coordinate with him? -- John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: {Arch,OCaml,Python,Mono} Packages for Adoption
On Wed, 27 Apr 2005 19:10:17 +0900, Miles Bader [EMAIL PROTECTED] said: Andreas Rottmann [EMAIL PROTECTED] writes: tla-tools I can take this one, if noone else wants it. Sorry for the delay. The new version is in incoming at the moment, and the public archives are visible under http://arch.debian.org/arch/private/srivasta/#easy ,[ Processing of tla-tools_2005.0.patch.23-1_i386.changes ] | tla-tools_2005.0.patch.23-1_i386.changes uploaded successfully to localhost | along with the files: | tla-tools_2005.0.patch.23-1.dsc | tla-tools_2005.0.patch.23.orig.tar.gz | tla-tools_2005.0.patch.23-1.diff.gz | tla-tools_2005.0.patch.23-1_all.deb ` If you do, could you update the debian package to the latest upstream version? The packaged version is the current (patch 23) from your 2005 repo. I have cleaned up the packaging, pared down the dependency lists , and added the dependency for uuidgen. The utilities all tested fine on my machine. All my debian packages can be seen at http://arch.debian.org/cgi-bin/archzoom.cgi/[EMAIL PROTECTED] for any potential collaborators. manoj -- Life is too short to stuff a mushroom. Storm Jameson Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: {Arch,OCaml,Python,Mono} Packages for Adoption
On Tue, 19 Apr 2005, John Goerzen wrote: Hello, I'm going through the list of packages I'm maintainer for, and found several that I no longer use. Some I've tried to give away long ago, but for whatever reason, never were picked up. I've submitted orphaned versions of all of these and filed appropriate wnpp bugs. [Mono] nant ikvm I'll take these thanks. Maybe the Mono packaging group will want them but that's for later. Cheers Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
{Arch,OCaml,Python,Mono} Packages for Adoption
Hello, I'm going through the list of packages I'm maintainer for, and found several that I no longer use. Some I've tried to give away long ago, but for whatever reason, never were picked up. I've submitted orphaned versions of all of these and filed appropriate wnpp bugs. [Arch] cscvs tla-tools [Ocaml] regexp-pp pycaml perl4caml [Mono] nant ikvm [Python] gnupginterface [Misc] inform-mode haskelldb -- John Goerzen Author, Foundations of Python Network Programming http://www.amazon.com/exec/obidos/tg/detail/-/1590593715 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3 packages for adoption
Le Mardi 4 Novembre 2003 19:31, Oliver Kurth a écrit : Hi there, I would like to give three of my packages for adoption: [..] memtester i am interested in this one, i will take it have a nice day -- OpenSides sprl Free Software Specialist Benoit Mortier - Linux Engineer pgp1xM00BLDEf.pgp Description: signature
3 packages for adoption
Hi there, I would like to give three of my packages for adoption: dumpasn1 This is a useful program if you work with files using the ASN.1 syntax, eg. X.509 cerificates. I needed this in my previous job, but not any more. Upstream is responsive, no bugs. tcpreen This is a sort of proxy. It listen on some configrable port, and forwards net traffic to another arbitrary server and, and prints all the information goinf back and forth. I thought it was useful, when I packaged it, but in reality I use ethereal. I will orphan this in two week, if noone else wants it. One wishlist bug, for a new version. Upstream is very responsive. memtester This is (very) useful if you want to test your RAM, but want the box to keep running, eg. if it's an important server and you are not sure if it does strange things because of RAM failures or other reasons. I will keep this if noone wants it, because I sometimes use it. Two bugs, one of them specific to large memory systems, the other contains a patch. Shame on me... For more nformation start at my QA page: http://qa.debian.org/developer.php?gpg_key=451EAB1B Greetings, Oliver -- .''`. : :' :Oliver Kurth [EMAIL PROTECTED] `. `' Debian GNU/Linux maintainer - www.debian.org `- When sending passwords, please use my gpg key. That's what it's good for. signature.asc Description: Digital signature
Packages for adoption
Hola amigos, Due to my constraints in life, I could not maintain a number of packages properly. So here are packages up for adoption : coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html, libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs, muttprint, type1inst, freefont, and sharefont. I will now maintain a couple of Thai related packages. cheers, Chanop -- ,. | May Debian be with you ~~ [EMAIL PROTECTED]| | http://thai.anu.edu.au| `' pgpjehhpmpf5R.pgp Description: PGP signature
Re: Packages for adoption
Il mar, 2002-08-27 alle 14:50, Chanop Silpa-Anan ha scritto: Hola amigos, Due to my constraints in life, I could not maintain a number of packages properly. So here are packages up for adoption : coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html, libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs, muttprint, type1inst, freefont, and sharefont. i'll take the following one ifno one objects: hyperlatex freefont sharefont -- Federico Di Gregorio Debian GNU/Linux Developer Italian Press Contact[EMAIL PROTECTED] INIT.D Developer [EMAIL PROTECTED] 99.% still isn't 100% but sometimes suffice. -- Me signature.asc Description: PGP signature
Re: Packages for adoption
Hi all, Chanop Silpa-Anan wrote: Due to my constraints in life, I could not maintain a number of packages properly. So here are packages up for adoption : coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html, libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs, muttprint, type1inst, freefont, and sharefont. I took muttprint and will upload a new package soon... Regards, Rene -- .''`.Rene Engelhard : :' :** Debian GNU/Linux Developer ** `. `' http://www.debian.org | http://people.debian.org/~rene/ `- [EMAIL PROTECTED] pgpBLfOHCRuuK.pgp Description: PGP signature
RE: Packages for adoption
Due to my constraints in life, I could not maintain a number of packages properly. So here are packages up for adoption : coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html, libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs, muttprint, type1inst, freefont, and sharefont. Hi, Can someone tell me what these packages are about : coriander, cpuburn, gscanbus, gsumi ? Sorry but I don't have internet here :( Best regards, -- .''`. Debian GNU/Linux 3.0 released ! : :' : Use it ! ;) `. `~' http://www.debianworld.org `- * Ce message et toutes les pieces jointes (ci-apres le message) sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. *
Re: Packages for adoption
Le mardi 27 août 2002 à 22:50, Chanop Silpa-Anan écrivait: coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html, libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs, muttprint, type1inst, freefont, and sharefont. As Rene took muttprint, i took latex2html and i will also upload a new package soon. Auré -- BOFH excuse #18: excess surge protection
Re: Packages for adoption
On Tue, 27 Aug 2002, Chanop Silpa-Anan wrote:
# Hola amigos,
#
#
# Due to my constraints in life, I could not maintain a number of packages
# properly. So here are packages up for adoption :
#
# coriander, cpuburn, gscanbus, gsumi, hyperlatex, latex2html,
# libdc1394-8, libdc1394-dev, libjpeg-mmx-dev, libjpeg-mmx-progs,
# muttprint, type1inst, freefont, and sharefont.
im interesting on cpuburn pkg
Cheers,
Indra Kusuma
--
,''`. Indra{@,.}Kusuma.OR.ID - [personal - Debian/GNU Linux - IPv6]
: :' : 0x4D829E49 - 187D 8C98 FB76 E1A8 5558 853A 4795 4FC1 4D82 9E49
`. `'
`-
Packages for adoption: dip, sliplogin
HI, due to absolute missing of dial up abilities (I don't even have a fixed line any more :-) I have to orphane two of my packages: dip - I'm crying in orphaning this, as I was putting a lot of care. It's the tool to handle SLIP/PPP connection (both sides), and it was the only one available for a long time. Now its fortune is slipping down, partly for the absolute dominance of PPP (I corrected PPP stuff on it) and the hostility of one HOWTO author. It has 4 bugs, two of them were due to the transition to glibc2, but I'm unable to see if they're gone. I also have a patch that I'm unable to test (it's not in the bts). sliplogin - Tool to attach a serial line network interface This tool is used to turn the terminal line on standard input into a Serial Line IP (SLIP) link to a remote host. Sliplogin can be used to setup SLIP dialin connections. Need a maintainer with good knowledge of modems and one to do test :-) Cheers, fab -- | [EMAIL PROTECTED] [EMAIL PROTECTED][EMAIL PROTECTED] | 6F7267F5 fingerprint 57 16 C4 ED C9 86 40 7B 1A 69 A1 66 EC FB D2 5E | [EMAIL PROTECTED] gsm: +358 (0)40 707 2468
Re: Packages for adoption
Hi. I am now using and prefer the asclassic, and since knghtbrd (the maintainer) and joel (he is another applicant for asclassic) agreed to my succession, I take it over. Thanks. In article [EMAIL PROTECTED] [EMAIL PROTECTED] (Joseph Carter) writes: [1 text/plain; us-ascii (quoted-printable)] I have a few packages which are mine that I no longer actually use and it would be best to give these to other developers who WOULD use them: asclassic - version 1.1 of AfterStep, up until recently the only wm I could stomach. The others all sucked, including new versions of AS which were painful to configure, poorly documented, and too damned slow. Window Maker has become at least as useful to me and in fact I think I have fewer complaints about wmaker than asclassic at this point. -- Taketoshi Sano: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
packages for adoption
I would like to offer the following two packages for adoption or removal: upsd- I don't use it, but others apparently do, and there are no open bugs that I am aware of jaztool - I don't use it, I'm not sure anyone does. Rumor has it that a newer version of the Zip tools for Linux fully supports Jaz drives as well... dunno. There are two bugs that were forwarded upstream, but the upstream author is unresponsive. Bdale
