Re: [ITP] astrometry.net-0.38-1
Well, well. I'm grateful for esp. the hours Chuck put into this, and for having at least seen the process and all, but I suppose it's time to end this -- I just can't bear to watch losing all the votes so bravely fought for ;-) AstroTortilla is fine with a custom repo. All we ever wanted was to be able to install astrometry.net with Cygwin's setup.exe. There were two reasons for doing the ITP: 1) Astrometry.net is immensely useful, albeit for a relatively minor userbase (*), and it *will* be part of both Cygwin and all the other major/applicable distros, eventually 2) the thought never occured to me that custom repos are possible ... (*) So-called computerized GOTO telescopes have been sold by the unknown tens if not hundreds of thousands over the past 10-20yrs. ALL of them are essentially fixed by AstroTortilla, which critically relies on Astrometry.net. So it may well be that once the word gets out that there's a GOTO correction program just like the one Hubble Space Telescope uses, available for amateur astronomers and compatible with their trusty old mounts, we'll see some downloads. How many would we need for it to be considered significant enough? Is this document still valid? http://sourceware.org/cygwin-apps/package-server.html Anything else I need to know? Thanks once again for your time and effort! I'm sorry the lessons you gave me will go down the drain if I won't become a package manager ... ;-) -- jussi P.S. If this message doesn't turn out to be the end of story just yet, let it be known that I will have a look at building the package with dynamic linking, if package size is deemed a bigger issue than the superficially miniscule userbase. It's just there's work (as in paycheck) to do, and my family has very recently grown by one, so I'm in no greater hurry with this than before ...
Re: [ITP] astrometry.net-0.38-1
On 11/9/2011 5:00 AM, Jussi Kantola wrote: AstroTortilla is fine with a custom repo. All we ever wanted was to be able to install astrometry.net with Cygwin's setup.exe OK. How many would we need for it to be considered significant enough? No idea. Is this document still valid? http://sourceware.org/cygwin-apps/package-server.html Seems accurate -- but it's missing information about gpg security. I think you want Creating a custom Cygwin package server -- you probably don't want to create or host a full mirror. Anything else I need to know? Here's what I do, locally: top/setup.exe top/genini top/release/foo/foo-1.2.3-1.tar.bz2 top/release/foo/foo-1.2.3-1-src.tar.bz2 top/release/foo/setup.hint $ cd cygwin $ ./genini --recursive release setup.ini $ bzip2 -c setup.ini setup.bz2 Then, upload setup.ini, setup.bz2, the new tarballs and setup.hint to your website, replicating the directory structure (from top/ on down). Now, your users will have to invoke setup.exe with the -X, because otherwise setup.exe will expect the setup.ini/bz2 files to be signed. However, turning the security measures off is a problem, because then your users have no protection against corrupted files on the *main* mirrors, either. So, ideally, you would ALSO sign *your* setup.ini/setup.bz2 files. See http://www.cygwin.com/ml/cygwin-announce/2008-08/msg1.html Now, this still requires your end users to take an explicit action (see item (3i),(3ii),(3iii) in the referenced announcement.) You could enable them to do (3i) or (3iii) via a batch file that you distribute...or... See the cygwin-ports instructions for their users, here: http://sourceware.org/cygwinports/ In that case, the use of 'cygstart' implies that cygwinports would be *added* to an existing cygwin installation; hence a bare-windows installation would require two separate setup.exe runs (*). This is actually a /good/ thing, because it means there's no confusion between the standard cygwin installation on my box and the cygwinports cygwin installation on my box -- your end users would just have one, to which they've added the extra stuff. (*) future update runs of setup would handle both the 'standard' packages and the addons simultaneously. Thanks once again for your time and effort! I'm sorry the lessons you gave me will go down the drain if I won't become a package manager ... ;-) You're still managing a package...it just wouldn't be hosted as an intrinsic part of the cygwin distribution itself. -- Chuck
RFU: rtorrent-0.8.9-3
Due to a packaging error on my part, the '-2' release didn't actually contain rtorrent.exe. As a result please upload: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/rtorrent/rtorrent-0.8.9-3.tar.bz2 \ http://emergedesktop.org/cygwin/rtorrent/rtorrent-0.8.9-3-src.tar.bz2 Please remove the '-2' release as it is incomplete. Thank you, Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d
Re: ATTENTION: Tcl/Tk transition
On Tue, 2011-11-08 at 02:18 +0100, Dr. Volker Zell wrote: I obsoleted the following packages: db-2.7.7 db-3.1.17 db-3.3.11.2 db-4.0.14 db-4.1.25.3 db-4.2.52.5 db-4.3.29.1 db-4.4.20.4 IMO there is no reason to keep these old versions, as nothing in the distro depends on them. So if there are no objections, we can just outright remove them, and use _obsolete packages only for tcl-db*.*. did a rebuild of db-4.5.20.2 and added db-4.8.30 Something is wrong with these packages; the libdb* and tcl-db* packages aren't versioned. (BTW, I think the tcl-db4.5 should also be an _obsolete package, pointing to tcl-db4.8.) 5.x will follow later when the dust settles. That will be helpful. * ming [tcl-ming] (Dr. Volker Zell) new requires: tcl notes: needs a pkgIndex.tcl file to be of any use Done. It has now a pkgIndex.tcl file. * WordNet (Dr. Volker Zell) new requires: tcl tcl-tk notes: needs patches for security vulnerabilities, patches available from all major distros, e.g.: http://pkgs.fedoraproject.org/gitweb/?p=wordnet.git;a=tree Done, with all the paches and security fixes. These look good. You will find the packages under /home/vzell on sourceware. Just copy (scp -r) them over when everybody is ready. Thank you for your prompt attention to this. Since space on /home is tight, I have copied the ming and WordNet into a staging area until we're ready for the move. Thanks, Yaakov Cygwin/X
Re: RFU: rtorrent-0.8.9-3
On Wed, Nov 09, 2011 at 06:36:43PM -0500, Chris Sutcliffe wrote: Due to a packaging error on my part, the '-2' release didn't actually contain rtorrent.exe. As a result please upload: wget -x -nH --cut-dirs=1 \ http://emergedesktop.org/cygwin/rtorrent/rtorrent-0.8.9-3.tar.bz2 \ http://emergedesktop.org/cygwin/rtorrent/rtorrent-0.8.9-3-src.tar.bz2 Please remove the '-2' release as it is incomplete. Done. cgf
Re: ATTENTION: Tcl/Tk transition
On 10.11.2011 00:51, Yaakov (Cygwin/X) wrote: On Tue, 2011-11-08 at 02:18 +0100, Dr. Volker Zell wrote: I obsoleted the following packages: db-2.7.7 db-3.1.17 db-3.3.11.2 db-4.0.14 db-4.1.25.3 db-4.2.52.5 db-4.3.29.1 db-4.4.20.4 IMO there is no reason to keep these old versions, as nothing in the distro depends on them. So if there are no objections, we can just outright remove them, and use _obsolete packages only for tcl-db*.*. did a rebuild of db-4.5.20.2 and added db-4.8.30 Something is wrong with these packages; the libdb* and tcl-db* packages aren't versioned. (BTW, I think the tcl-db4.5 should also be an _obsolete package, pointing to tcl-db4.8.) What do you mean with arent't versioned ? tar -tvjf db-4.5.20.2-3/dist/db/tcl-db/tcl-db-4.5.20.2-3.tar.bz2 usr/lib/tcl8.5/ usr/lib/tcl8.5/db4.5/ usr/lib/tcl8.5/db4.5/cygdb_tcl-4.5.dll usr/lib/tcl8.5/db4.5/pkgIndex.tcl tar -tvjf db-4.5.20.2-3/dist/db/libdb/libdb-4.5.20.2-3.tar.bz2 usr/bin/cygdb-4.5.dll usr/bin/cygdb_cxx-4.5.dll tar -tvjf db-4.8.30-1/dist/db/tcl-db/tcl-db-4.8.30-1.tar.bz2 usr/lib/tcl8.5/ usr/lib/tcl8.5/db4.8/ usr/lib/tcl8.5/db4.8/cygdb_tcl-4.8.dll usr/lib/tcl8.5/db4.8/pkgIndex.tcl tar -tvjf db-4.8.30-1/dist/db/libdb/libdb-4.8.30-1.tar.bz2 usr/bin/cygdb-4.8.dll usr/bin/cygdb_cxx-4.8.dll Ciao Volker
Re: ATTENTION: Tcl/Tk transition
On Thu, 2011-11-10 at 03:00 +0100, Dr. Volker Zell wrote: What do you mean with arent't versioned ? The package names themselves: tar -tvjf db-4.5.20.2-3/dist/db/libdb/libdb-4.5.20.2-3.tar.bz2 tar -tvjf db-4.8.30-1/dist/db/libdb/libdb-4.8.30-1.tar.bz2 The libdb packages must be libdb4.5 and libdb4.8. As for the -devel packages, perhaps we only need the latest one? tar -tvjf db-4.5.20.2-3/dist/db/tcl-db/tcl-db-4.5.20.2-3.tar.bz2 tar -tvjf db-4.8.30-1/dist/db/tcl-db/tcl-db-4.8.30-1.tar.bz2 If we need only one version of the Tcl bindings, fine (and it should come from 4.8), otherwise these need to be tcl-db4.5 and tcl-db4.8. Yaakov
