Re: upset messages
Il 11/29/2013 2:45 AM, Christopher Faylor ha scritto: /sourceware1/cygwin-staging/setup/upset: Error. Parsing failed. - duplicate packages lapack detected - x86_64/release/lapack/lapack vs. /var/ftp/pub/cygwin/x86_64/release/lapack Marco you created an additional lapack directory with duplicate files. I'd appreciate it if you would use the new upload mechanism since it will guard against this kind of thing. cgf just noticed. I tried to solve a problem and I created a different one. So to solve both I just uploaded new packages bumping to -2 I tried in the past the new method, but I had the impression was not active for me. Could you check ? Regards Marco
Re: upset messages
On Fri, Nov 29, 2013 at 11:10:16AM +0100, marco atzeri wrote: Il 11/29/2013 2:45 AM, Christopher Faylor ha scritto: /sourceware1/cygwin-staging/setup/upset: Error. Parsing failed. - duplicate packages lapack detected - x86_64/release/lapack/lapack vs. /var/ftp/pub/cygwin/x86_64/release/lapack Marco you created an additional lapack directory with duplicate files. I'd appreciate it if you would use the new upload mechanism since it will guard against this kind of thing. just noticed. I tried to solve a problem and I created a different one. So to solve both I just uploaded new packages bumping to -2 I actually fixed the problem by removing the directory. It sure looked like you had duplicated content there. I tried in the past the new method, but I had the impression was not active for me. Could you check ? AFAIK, you never sent the SSH key for upload details. I don't see anything in the archives. cgf
Re: upset messages
Il 11/29/2013 2:58 PM, Christopher Faylor ha scritto: On Fri, Nov 29, 2013 at 11:10:16AM +0100, marco atzeri wrote: I actually fixed the problem by removing the directory. It sure looked like you had duplicated content there. it was not exactly the same. there was a small difference between the two uploads, but I did it wrong I tried in the past the new method, but I had the impression was not active for me. Could you check ? AFAIK, you never sent the SSH key for upload details. I don't see anything in the archives. My fault, I assumed you already had my SSH Key cgf
two questions about new upload method
(1) Is there something I should sould be doing to tell upset which package versions are old and should be purged? I uploaded lftp, and the new version was added to the archive, but the old one (4.4.7-1) is still there. Do I need to add curr: and prev: lines to setup.hint? Or will upset figure that out and remove the old versions at some point? (2) I uploaded the unison packages for x86_64 in subdirectories of x86_64/release/unison: x86_64/release/unison/unison2.27 x86_64/release/unison/unison2.32 x86_64/release/unison/unison2.40 x86_64/release/unison/unison2.45 because that's how they're organized in x86/release. Will upset pick them up when they're organized that way? I only ask because it's been about 18 hours and they haven't appeared in any of the mirrors yet, although upset seems to be running every hour. Thanks, Andrew.
Re: two questions about new upload method
On Fri, Nov 29, 2013 at 12:27:17PM -0500, Andrew Schulman wrote: (1) Is there something I should sould be doing to tell upset which package versions are old and should be purged? There was a long thread about how to delete packages in cygwin-apps. http://cygwin.com/ml/cygwin-apps/2013-10/threads.html#00184 It also went into November. I uploaded lftp, and the new version was added to the archive, but the old one (4.4.7-1) is still there. Do I need to add curr: and prev: lines to setup.hint? Or will upset figure that out and remove the old versions at some point? (2) I uploaded the unison packages for x86_64 in subdirectories of x86_64/release/unison: x86_64/release/unison/unison2.27 x86_64/release/unison/unison2.32 x86_64/release/unison/unison2.40 x86_64/release/unison/unison2.45 because that's how they're organized in x86/release. Will upset pick them up when they're organized that way? I only ask because it's been about 18 hours and they haven't appeared in any of the mirrors yet, although upset seems to be running every hour. Guess I need to add a FAQ. Q) Why aren't my files being transferred to the release area? I've waited several days and don't see any movement. A) The package updater runs every 10 minutes so, if you don't see any movement in, e.g., 20 minutes, then your package is not going to be updated. The main reason that this could happen is if you uploaded a package that you are not actually responsible for. The updater only knows what you are responsible for based on http://cygwin.com/cygwin-pkg-maint so if you aren't listed as an owner there your packages won't be updated. I added you as the owner for unison and unison2.45. cgf
cygwin-pkg-maint update
I just noticed that gl2ps , libgl2ps1 and libgl2ps-devel are not reported as they were only recently added. But I see the same for the result of split /addition in the past like netcdf-cxx4, libnetcdf-cxx4, libnetcdf-cxx4-devel or the suitesparse expansion. So before touching anything : what is the right procedure to update cygwin-pkg-maint ? Regards Marco
SSH key for upload access
Name: Marco Atzeri Package: lapack BEGIN SSH2 PUBLIC KEY B3NzaC1yc2EDAQABAAABAQDBdNLOzObcACE50UDaWncOKGYK8Ph2j7NGdMlgRH IjzLj6ibCAJK8rSJ+9u1UY59cjUL3LbdWnJzohRMnQ+cEe2mrG1uwjQXVC5C9V0A9EFKwV 6q/Q6z3+UO4K14jH+s8tYCei/M/92c2c9zmta2w4sf6S+D1BS6MWOA5wg5GGHXAtVaiU4Z PhjOgrTDxsGY8tQBWEtUVRKaXLRHO014ObE8HddC4dgyiSk89eW8Bj0I9mfW/jtOd2pcNF G0Z/CSWjRyLftQvYHAznppse8Q9rKQYkp7jLHcNYn8oQU5vGwRZzU3axdIUCZx26YJu6AT 5h3CjsRvMjvKtvNJ2QV5Zz END SSH2 PUBLIC KEY
Re: SSH key for upload access
On Fri, Nov 29, 2013 at 10:25:39PM +0100, marco atzeri wrote: Name: Marco Atzeri Package: lapack BEGIN SSH2 PUBLIC KEY B3NzaC1yc2EDAQABAAABAQDBdNLOzObcACE50UDaWncOKGYK8Ph2j7NGdMlgRH IjzLj6ibCAJK8rSJ+9u1UY59cjUL3LbdWnJzohRMnQ+cEe2mrG1uwjQXVC5C9V0A9EFKwV 6q/Q6z3+UO4K14jH+s8tYCei/M/92c2c9zmta2w4sf6S+D1BS6MWOA5wg5GGHXAtVaiU4Z PhjOgrTDxsGY8tQBWEtUVRKaXLRHO014ObE8HddC4dgyiSk89eW8Bj0I9mfW/jtOd2pcNF G0Z/CSWjRyLftQvYHAznppse8Q9rKQYkp7jLHcNYn8oQU5vGwRZzU3axdIUCZx26YJu6AT 5h3CjsRvMjvKtvNJ2QV5Zz END SSH2 PUBLIC KEY Activated. cgf
Re: cygwin-pkg-maint update
On Fri, Nov 29, 2013 at 09:43:11PM +0100, marco atzeri wrote: I just noticed that gl2ps , libgl2ps1 and libgl2ps-devel are not reported as they were only recently added. But I see the same for the result of split /addition in the past like netcdf-cxx4, libnetcdf-cxx4, libnetcdf-cxx4-devel or the suitesparse expansion. So before touching anything : what is the right procedure to update cygwin-pkg-maint ? You can add your new packages to cygwin-pkg-maint since you have a login account on sourceware.orgi with cygwin group access. You'll need to use CVS: cvs -d :ext:sourceware.org:/cvs/cygwin co htdocs You don't add -devel or other subpackages packages like libgl2ps-devel. Just add the main package name. In case anyone noticed: unison is a special case since new version numbers are part of the package name. To answer the general question: Anyone without a cygwin group account on sourceware will have to send mail here to have one of us update cygwin-pkg-maint. Personally, I'd appreciate a patch but if you can't do that, at least use the same format as cygwin-pkg-maint in your request. cgf
Re: two questions about new upload method
On Fri, Nov 29, 2013 at 01:13:30PM -0500, Christopher Faylor wrote: I added you as the owner for unison and unison2.45. Which didn't do anything. I'm investigating why now. cgf
Re: two questions about new upload method
On Fri, Nov 29, 2013 at 10:06:50PM -0500, Christopher Faylor wrote: On Fri, Nov 29, 2013 at 01:13:30PM -0500, Christopher Faylor wrote: I added you as the owner for unison and unison2.45. Which didn't do anything. I'm investigating why now. It was because the !ready files disappeared after the previous run. I put one in unison/unison2.45 and the files were moved. cgf
