Re: Command 'more': missing dll cygpcre.dll [Attn more maintainer]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Joshua Daniel Franklin on 9/14/2005 7:10 PM: I did that 'more' release as part of getting together some packages for a minimal but still somewhat useful Cygwin installation. I like 'less' and have never actually used 'more'. I'd actually prefer if we could symlink it to 'less' for the people who are used to it and drop the separate package. Anyway, thanks for the upload but I guess I'm still MIA. :) Sorry if my upload without waiting for your reply was too hasty, but it appears no harm was done. On closer inspection of /usr/src/more*/more.c, you did list yourself as the person porting to cygwin, and I should have realized that you are still actively on the cygwin lists. Meanwhile, cygwin less is at 381, but upstream less 382 is out (although http://www.greenwoodsoftware.com/less/ says there is no need to upgrade); and looking at /usr/src/less-381-1, I can't see a maintainer there either. Who maintains less, and are they willing to make a new release of less that includes /bin/more as a link to less, so that we can obsolete the more package in favor of less? This time, I won't be so hasty (with more, I figured that 3 years of inactivity warranted an instant upgrade). To summarize, should cygwin follow the maxim 'less is more'? :) - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDKXOl84KuGfSFAYARApZ9AKDDxJJ+e8TjezZ8KRaSu1TAJcNGSwCgqq7Q nS96fNQdj7pofomys2O+SZw= =jkgb -END PGP SIGNATURE-
Re: Command 'more': missing dll cygpcre.dll [Attn more maintainer]
On Thu, Sep 15, 2005 at 07:14:13AM -0600, Eric Blake wrote: According to Joshua Daniel Franklin on 9/14/2005 7:10 PM: I did that 'more' release as part of getting together some packages for a minimal but still somewhat useful Cygwin installation. I like 'less' and have never actually used 'more'. I'd actually prefer if we could symlink it to 'less' for the people who are used to it and drop the separate package. Anyway, thanks for the upload but I guess I'm still MIA. :) Sorry if my upload without waiting for your reply was too hasty, but it appears no harm was done. On closer inspection of /usr/src/more*/more.c, you did list yourself as the person porting to cygwin, and I should have realized that you are still actively on the cygwin lists. I missed the fact that you uploaded this without the approval of the maintainer. Please don't do that. Meanwhile, cygwin less is at 381, but upstream less 382 is out (although http://www.greenwoodsoftware.com/less/ says there is no need to upgrade); and looking at /usr/src/less-381-1, I can't see a maintainer there either. I maintain less. Who maintains less, and are they willing to make a new release of less that includes /bin/more as a link to less, so that we can obsolete the more package in favor of less? This time, I won't be so hasty (with more, I figured that 3 years of inactivity warranted an instant upgrade). To summarize, should cygwin follow the maxim 'less is more'? :) Checking various linux systems: % rpm -q -f /bin/more util-linux-2.12p-9.3 % dpkg -S /bin/more util-linux: /bin/more % epm -q -f /bin/more util-linux-2.12q-r1 So, no, I will not be including a 'more' symlink in the 'less' package. I'll take on 'more' maintenance responsibilities. cgf
[HEADSUP] ALL Maintainers, please reply.
Mails in the last couple of weeks indicate that we have lost one or the other maintainer without getting any notice from them. Since we have a couple of packages which haven't been updated for a good amount of time, there's apparently a need to find out, which packages are still maintained and which have lost their maintainer on the way. So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. This survey will run until 2005-10-31. I will ping every week, so you have a bit of time. However, if you don't reply until 2005-10-31, your packages will be up for grabs. Which means, they will disappear from the Cygwin net distribution if nobody wants to take over maintainership. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc.
Re: [HEADSUP] ALL Maintainers, please reply.
On Sep 15 18:45, Corinna Vinschen wrote: Mails in the last couple of weeks indicate that we have lost one or the other maintainer without getting any notice from them. Since we have a couple of packages which haven't been updated for a good amount of time, there's apparently a need to find out, which packages are still maintained and which have lost their maintainer on the way. So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. This survey will run until 2005-10-31. I will ping every week, so you have a bit of time. However, if you don't reply until 2005-10-31, your packages will be up for grabs. Which means, they will disappear from the Cygwin net distribution if nobody wants to take over maintainership. To reply to my own mail for equity. The below list are the packages I maintain. SWI-Prolog ash cpio cron crypt cygrunsrv file flac gawk inetutils irc libao libogg libvorbis login lynx mt netcat openssh openssl patch psmisc robots ruby sed setsid sharutils shutdown speex tcsh tin vim vorbis-tools which Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc.
Re: [HEADSUP] ALL Maintainers, please reply.
On Thu, Sep 15, 2005 at 06:45:37PM +0200, Corinna Vinschen wrote: Mails in the last couple of weeks indicate that we have lost one or the other maintainer without getting any notice from them. Since we have a couple of packages which haven't been updated for a good amount of time, there's apparently a need to find out, which packages are still maintained and which have lost their maintainer on the way. So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. This survey will run until 2005-10-31. I will ping every week, so you have a bit of time. However, if you don't reply until 2005-10-31, your packages will be up for grabs. Which means, they will disappear from the Cygwin net distribution if nobody wants to take over maintainership. bc binutils bison byacc ccache cygwin dejagnu (but a new maintainer may be pending) diffutils ed expect (but a new may be pending) fileutils flex gdb grep groff gzip less make more termcap texinfo tcltk time Btw, this doesn't go without saying, but please don't use the responses from this email as an excuse to contact people directly about the packages they maintain. cgf
Re: [HEADSUP] ALL Maintainers, please reply.
Hey, On 15/09/05, Corinna Vinschen [EMAIL PROTECTED] wrote: Mails in the last couple of weeks indicate that we have lost one or the other maintainer without getting any notice from them. Since we have a couple of packages which haven't been updated for a good amount of time, there's apparently a need to find out, which packages are still maintained and which have lost their maintainer on the way. So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. This survey will run until 2005-10-31. I will ping every week, so you have a bit of time. However, if you don't reply until 2005-10-31, your packages will be up for grabs. Which means, they will disappear from the Cygwin net distribution if nobody wants to take over maintainership. w32api mingw-runtime Chris -- Chris Sutcliffe http://emergedesktop.org http://ironhead.modblog.com
Re: [HEADSUP] ALL Maintainers, please reply.
I maintain the OpenGL package. André Bleau Please address any question about the OpenGL package to the cygwin mailing list, not to me directly. _ Gardez le contrôle grâce à la protection contre les fenêtres pop-up articulée sur la technologie brevetée Microsoft SmartScreen http://join.msn.com/?pgmarket=fr-capage=features/popup Commencez dès maintenant à profiter de tous les avantages de MSN Premium et obtenez les deux premiers mois GRATUITS*.
Re: [HEADSUP] ALL Maintainers, please reply.
I maintain clisp [I am willing to surrender the maintainership to anyone willing qualified.] -- Sam Steingold (http://www.podval.org/~sds) running w2k http://www.palestinefacts.org/ http://pmw.org.il/ http://truepeace.org http://www.savegushkatif.org http://www.openvotingconsortium.org/ It's not just a language, it's an adventure. Common Lisp.
Re: [HEADSUP] ALL Maintainers, please reply.
On Thu, September 15, 2005 5:45 pm, Corinna Vinschen wrote: Mails in the last couple of weeks indicate that we have lost one or the other maintainer without getting any notice from them. Since we have a couple of packages which haven't been updated for a good amount of time, there's apparently a need to find out, which packages are still maintained and which have lost their maintainer on the way. So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. This survey will run until 2005-10-31. I will ping every week, so you have a bit of time. However, if you don't reply until 2005-10-31, your packages will be up for grabs. Which means, they will disappear from the Cygwin net distribution if nobody wants to take over maintainership. base-files base-passwd lcms (kinda - said I would but not re-released yet!) units J.
Re: [HEADSUP] ALL Maintainers, please reply.
On Sep 15 18:45, Corinna Vinschen wrote: To reply to my own mail for equity. The below list are the packages I maintain. sharutils You just recently gave that one to me. Corinna -- Eric Blake
Re: [HEADSUP] ALL Maintainers, please reply.
On Thu, 2005-09-15 at 18:45 +0200, Corinna Vinschen wrote: other maintainer without getting any notice from them. Since we have a couple of packages which haven't been updated for a good amount of time, there's apparently a need to find out, which packages are still maintained and which have lost their maintainer on the way. I'm still here, but not actively maintaining packages, offhand that means dpkg, squid probably need excising or new maintainers. Rob -- GPG key available at: http://www.robertcollins.net/keys.txt. signature.asc Description: This is a digitally signed message part
Re: [HEADSUP] ALL Maintainers, please reply.
On Sep 15 10:24, Harold L Hunt II wrote: cppunit ddd (won't do new versions) distcc fontconfig, libfontconfig1, libfontconfig-devel (won't do new versions) fvwm (won't do new versions) GraphicsMagick, libGraphicsMagick0, libGraphicsMagick-devel ImageMagick, libImageMagick6, libImageMagick-devel lesstif (won't do new versions) libXft, libXft2, libXft-devel, libXft1 (won't do new versions) links nedit (won't do new versions) openbox (won't do new versions) transfig WindowMaker (won't do new versions) Xaw3d xfig xgraph xmon xterm Can you elaborate on won't do new versions? wget --- I've posted a package of a newer version; I'm not trying to take the package like a jerk, but I will accept it if the current maintainer does not checkin or if he explicitly says that he doesn't want it anymore No worries. We just carefully assume that Hack is on vacation or something, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc.
Re: [HEADSUP] ALL Maintainers, please reply.
On Sep 15 17:35, Eric Blake wrote: On Sep 15 18:45, Corinna Vinschen wrote: To reply to my own mail for equity. The below list are the packages I maintain. sharutils You just recently gave that one to me. Oh yes, that slipped through. Thanks for the reminder. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc.
Re: [HEADSUP] ALL Maintainers, please reply.
On Sep 16 03:36, Robert Collins wrote: On Thu, 2005-09-15 at 18:45 +0200, Corinna Vinschen wrote: other maintainer without getting any notice from them. Since we have a couple of packages which haven't been updated for a good amount of time, there's apparently a need to find out, which packages are still maintained and which have lost their maintainer on the way. I'm still here, but not actively maintaining packages, offhand that means dpkg, squid probably need excising or new maintainers. Er... what does that mean, dpkg and squid have a maintainer or dpkg and squid have no maintainer? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc.
Re: [HEADSUP] ALL Maintainers, please reply.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here are my packages, including approved packages waiting for upload (I hope I didn't forget anything): audiofile (libaudiofile0, libaudiofile-devel) d esound (libesound0, libesound-devel) desktop-file-utils glib (glib-devel) gnome-keyring gtk+ (gtk+-devel) gtk-engines gtypist help2man hicolor-icon-theme imlib libglade2 libgnomecanvas2 libgnomeprint22 libgnomeprintui22 libIDL2 libwnck libxml netpbm (libnetpbm10, libnetpbm-devel) ORBit (libIDL) ORBit2 pcre shared-mime-info startup-notification Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDKbz8piWmPGlmQSMRAj2yAJ9Lq/3X0/msOjD4pIGPBi+6oFi2fgCgmH0J HuGLqKW+jB+qcdjEd4qFbCI= =4mf2 -END PGP SIGNATURE-
Re: lesstif
Brian, Brian Ford wrote: On Thu, 15 Sep 2005, Harold L Hunt II wrote: Brian Ford wrote: On Thu, 15 Sep 2005, Harold L Hunt II wrote: [snip] That's pretty much why the lesstif package is stuck where it is: it didn't work with nedit. We must have a mis-communication here. I told you (as quoted below) that my build of your unmodified lesstif-0.94.4 package worked for all our in-house applications as well as nedit. I suspected that you were using an outdated compiler or binutils package, and that was what caused your nedit issue. Hmm... no, I confirmed back, I believe, that I had the latest compiler and binutils and I think we left it at that. Since there is confusion about what is on both of our machines, the best thing for you to do would be to take a clean Windows image under VMWare, install Cygwin on it, compile the two packages and see what happens. Make sure that you do more with nedit than just opening it up... you actually need to open some files and play around in order to get it to crash (sometimes). Do you want to look into this, or do you just want to give lesstif to me? If you agree to some sort of verification that nedit works, its yours. No need to reply back, just take it if you agree. Harold No need to CC me in replies Hunt
Re: [HEADSUP] ALL Maintainers, please reply.
Corinna Vinschen wrote: So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. apache2 apache2-devel apache2-manual apr libapr0 apr-util libaprutil0 doxygen neon (soon to be renamed to neon24) libneon24 neon25 (not yet - new package coming soon) libneon25 (not yet - new package coming soon) patchutils subversion subversion-apache2 subversion-book subversion-devel subversion-perl subversion-python swig Max.
Re: [HEADSUP] ALL Maintainers, please reply.
On Thu, 15 Sep 2005, Corinna Vinschen wrote: Mails in the last couple of weeks indicate that we have lost one or the other maintainer without getting any notice from them. Since we have a couple of packages which haven't been updated for a good amount of time, there's apparently a need to find out, which packages are still maintained and which have lost their maintainer on the way. So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. This survey will run until 2005-10-31. I will ping every week, so you have a bit of time. However, if you don't reply until 2005-10-31, your packages will be up for grabs. Which means, they will disappear from the Cygwin net distribution if nobody wants to take over maintainership. At the moment: zsh (maybe adding a few packages in the near future). -- Peter A. Castro [EMAIL PROTECTED] or [EMAIL PROTECTED] Cats are just autistic Dogs -- Dr. Tony Attwood
Re: [HEADSUP] ALL Maintainers, please reply.
On Thu, Sep 15, 2005 at 06:45:37PM +0200, Corinna Vinschen wrote: So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. I maintain the following packages: fetchmail postgresql (but Reini was suppose to take over with 8.x) procmail proftpd python rebase Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
Re: Adding a Maintainer: field to setup.hint
I'm thinking about adding a maintainer field to setup.hint which would have meaning only in setup.hint but would allow us to more easily track who maintains what. It would look like this: Maintainer: Chris Faylor i.e., no email address, just a person's name (for obvious reasons). I could then add this information to the cygwin packages web page. I'm all for it. Orphaned packages would be changed to either Orphaned or Up for Grabs or MIA. I'd go for Orphaned. Does anyone have a problem with this? If not, I'll use the info that Corinna is gathering to modify the setup.hints on sourceware.org. cgf Also, the package maintainence instructions should be updated to state that once you are a maintainer, you are considered to be the maintainer until you provide a new setup.hint changing the Maintainer: field, or when a request to reach you on the cygwin-apps list goes unanswered for a period of time (6 weeks, like the current maintainer poll?). Should we also have some sort of timeout policy on obsolete packages, where once a package has been in the _obsolete category for at least 2 years (or some other time length) it is automatically a candidate for removal from the distro? -- Eric Blake
Re: Adding a Maintainer: field to setup.hint
Christopher Faylor wrote: I'm thinking about adding a maintainer field to setup.hint which would have meaning only in setup.hint but would allow us to more easily track who maintains what. It would look like this: Maintainer: Chris Faylor Perhaps keep maintainer all lower-case, for consistency with existing setup.hint fieldnames? Does anyone have a problem with this? If not, I'll use the info that Corinna is gathering to modify the setup.hints on sourceware.org. Sounds good. To avoid duplicating information, maybe add a maintainer field only to non-external-source packages? Max.
Re: [HEADSUP] ALL Maintainers, please reply.
w3m * On Thu, Sep 15, 2005 at 06:45:37PM +0200, Corinna Vinschen wrote: Mails in the last couple of weeks indicate that we have lost one or the other maintainer without getting any notice from them. Since we have a couple of packages which haven't been updated for a good amount of time, there's apparently a need to find out, which packages are still maintained and which have lost their maintainer on the way. So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. This survey will run until 2005-10-31. I will ping every week, so you have a bit of time. However, if you don't reply until 2005-10-31, your packages will be up for grabs. Which means, they will disappear from the Cygwin net distribution if nobody wants to take over maintainership. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc.
Re: [HEADSUP] ALL Maintainers, please reply.
* On Thu, Sep 15, 2005 at 05:21:55PM -0400, Bob Heckel wrote: w3m Sorry, forgot to include: libgc
Re: [HEADSUP] ALL Maintainers, please reply.
Corinna Vinschen wrote: So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. Package LastUpstr. - rsync 2.6.6-1 = typespeed 0.4.4-2 = gmp 4.1.4-2 = par 1.52= tidy041206-1050912 ucl 1.011.03 upx 1.241.25 libungifAFAIR is should be Harold's since 4.1.0-3 Lapo -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (ICQ UIN: 529796)
Re: [HEADSUP] ALL Maintainers, please reply.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lapo Luchini wrote: libungif AFAIR is should be Harold's since 4.1.0-3 But (only now) I see that he didn't include it in his list. Maybe I remember wrong. Or maybe he just forgot. Anyway, as I said 0.962 years ago¹, I no longer use it or am interested in it, so I will eventually package a new version of it (if needed) but will be my least priority. 1: http://sourceware.org/ml/cygwin-apps/2004-09/msg00327.html - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (ICQ UIN: 529796) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQIcBAEBAgAGBQJDKeyOAAoJELBiMTth2oCDu9UP+gNkIssFT2SHYkYIH3Uw54uX W2xRIYJiyqF14EHdj+7PqWp5kp81tGXyD9BjiDmyXePQZJEtG+/Xb9lT0zok6Q97 iOLCD0axK5IWM1nsb4bWtHBtZB/K7e0KX0sbBJo9qXzRAOgBrvXpHZ6pCf3ANS+A ChrIc+g+PWB8myXxX0krwg0+vkURo0nDkCvFYMVqvpYs2I8PXYpC6aezRC218WN7 n+0ilVBKGTS0Hyn8m2k8xab5szqzegRGu2jUxPMhW56jhqwmfCfUOSf1YfpAfBBK r7xG44lN4s1lFIUu1SaA5uKQyK1/+5COnT9Pvah6Hh/gwZ+U8fz+JlUX5obsuSQn g34/XWE3to9WzE3o/qGsHi8ZvVMKqapRYpnMzT49k6pOz98IQ5Tn7JAqsz/8k+qb mRH2DU2/+mmEeupf0DYod2b+UXYXYBvt9yb2IkX4y0KoXzbhB5vwr/0PfWqf9d7c RyY+flW+m0hvUdAOpfYqmtnE/A0e3OKbDZsZNa7/5DJn9ZLm3FSv3v12DEbhwAhz VY4SUy2V1QH6OPa6i5AjsrPBXeHIavyQyGhXG+UHsMhGiu+imlwqK1IimP0U9e9a aIwrNT7z4+E1aCc6R4J37hqf++F25iCE8Q2JD93xiXwlCm5Y8S+oJFjrVtsgCitB kEWGF3uicdNAIe+MpwdK =Gyea -END PGP SIGNATURE-
libungif [Was: Re: [HEADSUP] ALL Maintainers, please reply.]
Lapo, Lapo Luchini wrote: Corinna Vinschen wrote: [snip] libungifAFAIR is should be Harold's since 4.1.0-3 Lapo Hmm... Here is me announcing a 4.1.2-1 for your eval: http://www.cygwin.com/ml/cygwin-apps/2004-03/msg00044.html Here is a response from you about how you think that I might be better suited to determine when it is ready for prime time: http://www.cygwin.com/ml/cygwin-apps/2004-03/msg00163.html Here is what we did with 4.1.2-1 and designation of a maintainer: [silence, crickets, leaves blowing around...] :) Looks like 4.1.2-1 got dropped on the floor since it is still marked as test almost 18 months later. The README for both versions still lists you as the maintainer. At this time I'd have to say that it doesn't make a lot of sense for me to become the maintainer, but I'd pick it up if the alternative was that it would be removed from the distro. Harold
RE: [HEADSUP] ALL Maintainers, please reply.
Nano (Several unstable versions I could consider moving too but wont unless interest is expressed, also some new stable versions, I guess I should update.) Aspell binaries and docs and dev and libaspell but not dictionaries. (There is a new version of this which I will upgrade too if any interest is expressed, but I think it needs new versions of the dictionaries.) Cyrus-sasl (includes libsasl2) (Also has a new version which I'll do if anyone is interested; however I am no longer working for the company which needed this library in cygwin so if anyone wants to take over maintainership that's fine with me.) Regards, Gareth PS, how did I become unsubscribed from cygwin-apps and yet still receive email from it?
Re: [HEADSUP] ALL Maintainers, please reply.
Gerrit P. Haase wrote: Have I missed one? gtk-doc? If anyone is interested to take over one or more packages feel free to do so, just drop me a note in my inbox. There are also packages in my private repository which could be taken, i.e. Gnome desktop related packages are done by Yaakov and me and there are at least 100 packages needed to run Gnome, not counted the bindings (Perl/C++/Python/Java/...) and applications. Does that mean you don't intend to update your GNOME packages? In any case, I would like first claims to anything GNOME related, as I've already put so much work into it. Yaakov
Re: [HEADSUP] ALL Maintainers, please reply.
Sorry, I sent this earlier today, but from the wrong account so it ended up bouncing. Yaakov S wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gerrit P. Haase wrote: Harold L Hunt II wrote: [...package list...] freetype? Indeed, freetype2 is somewhat out of date. I've already built 2.1.9 in order to run the current GIMP, so if you're not interested in updating this one, please let us know. It's yours.
Re: [HEADSUP] ALL Maintainers, please reply.
Corinna Vinschen wrote: Mails in the last couple of weeks indicate that we have lost one or the other maintainer without getting any notice from them. Since we have a couple of packages which haven't been updated for a good amount of time, there's apparently a need to find out, which packages are still maintained and which have lost their maintainer on the way. So, ALL maintainers of Cygwin packages, please reply to this mail within the next six weeks, including a list of ALL packages you maintain. This survey will run until 2005-10-31. I will ping every week, so you have a bit of time. However, if you don't reply until 2005-10-31, your packages will be up for grabs. Which means, they will disappear from the Cygwin net distribution if nobody wants to take over maintainership. CURRENT PACKAGES --- alternatives autoconf (wrapper) autoconf2.1 autoconf2.5 automake1.4 automake1.6 automake1.7 automake1.8 automake1.9 bzip2 libbz2_1 cvs cygutils gdbm libgdbm-devel libgdbm4 gettext gettext-devel libgettextpo0 libintl3 jbigkit jpeg libjpeg62 libgeotiff libgeotiff-devel libgeotiff1 libiconv libiconv2 libcharset1 libpng libpng10 libpng10-devel libpng12 libpng12-devel libtool1.5 libltdl3 mingw-bzip2 mingw-libbz2_1 mingw-zlib mktemp ncurses ncurses-demo libncurses-devel libncurses8 pkgconfig proj libproj-devel libproj0 terminfo tiff libtiff-devel libtiff5 unzip xpm-nox zip zlib OLDER, COMPATIBILITY PACKAGES --- libbz2_0 libgdbm libgdbm3 libintl libintl1 libintl2 libjpeg6b libpng2 libncurses5 libncurses6 libncurses7 libtiff3 libtiff4 OBSOLETE PACKAGES --- autoconf-devel autoconf-stable automake (obsolete wrapper) automake-devel automake-stable cygipc libtool (obsolete wrapper) libtool-devel libtool-stable -- Chuck
Re: [HEADSUP] ALL Maintainers, please reply.
At the moment, I maintain: I suppose I also inherited some obsolete packages by taking over coreutils: bash bashdb bash-completion coreutils cvsutils diffstat fileutils (obsolete) findutils libreadline4 (unlikely to need upgrade) libreadline5 (unlikely to need upgrade) libreadline6 m4 readline sh-utils (obsolete) sharutils tar textutils (obsolete) -- Eric Blake
