Fwd: upset messages
It seems something went wrong on my upload on the 32bit area. upset: *** /var/ftp/pub/cygwin/x86/setup.ini: warning - package singular-help-3.1.6-2 refers to nonexistent external-source: singular however https://cygwin.com/packages/x86/singular/ says I have the new versions: singular-4.0.2-1 singular-4.0.2-1-src while /sourceware/ftp/anonftp/pub/cygwin/x86/release/singular says I don't have them ls -1 *.bz2 singular-3.1.3-1-src.tar.bz2 singular-3.1.6-2-src.tar.bz2 Do we have a double stage are ? I always thought /sourceware/ftp/anonftp/pub/cygwin/x86/release/singular was the base for https://cygwin.com/packages/x86/singular/ info. Regards Marco
Re: Fwd: upset messages
On Sun, 2015-05-17 at 10:52 +0200, Marco Atzeri wrote: It seems something went wrong on my upload on the 32bit area. upset: *** /var/ftp/pub/cygwin/x86/setup.ini: warning - package singular-help-3.1.6-2 refers to nonexistent external-source: singular Right after I sent my last email, I noticed this error as well and realized that the singular-base -src packages had to be renamed. I took care of that as well and requeued your singular packages for upload. while /sourceware/ftp/anonftp/pub/cygwin/x86/release/singular says I don't have them ls -1 *.bz2 singular-3.1.3-1-src.tar.bz2 singular-3.1.6-2-src.tar.bz2 Remember that packages are *.tar.xz nowadays, but in any case everything looks right now. I always thought /sourceware/ftp/anonftp/pub/cygwin/x86/release/singular was the base for https://cygwin.com/packages/x86/singular/ info. The /sourceware/ftp/anonftp/pub/cygwin/ directory (aka /var/ftp/pub/cygwin due to symlinks) are the basis of our package FTP/rsync area. The package list pages are generated by upset into the HTTP space. -- Yaakov
Re: upset messages
On Feb 6 11:55, Marco Atzeri wrote: any reason for such message ? I see no error or complain, just notification Hmm, no idea. Yaakov, do you have any? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp1_oEqwG5G8.pgp Description: PGP signature
Fwd: upset messages
any reason for such message ? I see no error or complain, just notification Forwarded Message Subject: upset messages Date: 6 Feb 2015 07:10:12 - From: cygwin-no-re...@cygwin.com upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-9.4.1-1-src.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libecpg-compat3/libecpg-compat3-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/libecpg-compat3 upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libecpg-compat3/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/libecpg-compat3 upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libecpg-devel/libecpg-devel-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/libecpg-devel upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libecpg-devel/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/libecpg-devel upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libecpg6/libecpg6-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/libecpg6 upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libecpg6/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/libecpg6 upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libpgtypes3/libpgtypes3-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/libpgtypes3 upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libpgtypes3/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/libpgtypes3 upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libpq-devel/libpq-devel-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/libpq-devel upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libpq-devel/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/libpq-devel upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libpq5/libpq5-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/libpq5 upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/libpq5/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/libpq5 upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-client/postgresql-client-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-client upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-client/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-client upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-contrib/postgresql-contrib-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-contrib upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-contrib/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-contrib upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-devel/postgresql-devel-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-devel upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-devel/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-devel upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-doc/postgresql-doc-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-doc upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-doc/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-doc upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-plperl/postgresql-plperl-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-plperl upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-plperl/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-plperl upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-plpython/postgresql-plpython-9.4.1-1.tar.xz into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql-plpython upset: moved /sourceware/cygwin-staging/home/Marco Atzeri/x86/release/postgresql/postgresql-plpython/setup.hint into /var/ftp/pub/cygwin/x86/release/postgresql/postgresql
Re: upset messages
On Fri, 2015-02-06 at 12:47 +0100, Corinna Vinschen wrote: On Feb 6 11:55, Marco Atzeri wrote: any reason for such message ? I see no error or complain, just notification Hmm, no idea. Yaakov, do you have any? Per a previous discussion, I had attempted to add acknowledgement messages when an upload was successful, so uploaders weren't left wondering. For whatever reason, nothing happened until now; I'm not sure what triggered that yet. -- Yaakov
Re: upset messages
On 11/08/14 23:11, cygwin-no-re...@cygwin.com wrote: upset: couldn't unlink /sourceware/cygwin-staging/home/David Stacey/x86/!ready - No such file or directory I'm not sure what happened here - apologies if it was my fault. I was attempting to upload new versions of xmlstarlet and yasm, both of which appear to have been taken. I've also checked both my 'x86' and 'x86_64' directories, and the '!ready' files appear to have disappeared - so hopefully these upset errors won't get generated ad infinitum. Does anyone have any idea as to what could have caused this? Dave.
Re: upset messages
On 2014-08-11 17:37, David Stacey wrote: On 11/08/14 23:11, cygwin-no-reply wrote: upset: couldn't unlink /sourceware/cygwin-staging/home/David Stacey/x86/!ready - No such file or directory I'm not sure what happened here - apologies if it was my fault. I was attempting to upload new versions of xmlstarlet and yasm, both of which appear to have been taken. I've also checked both my 'x86' and 'x86_64' directories, and the '!ready' files appear to have disappeared - so hopefully these upset errors won't get generated ad infinitum. Does anyone have any idea as to what could have caused this? I'm looking into it, but I doubt it's anything you did. Yaakov
Re: upset messages
On 2014-06-13 01:04, cygwin-no-re...@cygwin.com wrote: upset: *** /var/ftp/pub/cygwin/x86_64/setup.ini: error - package qiv requires nonexistent package libpng14 upset: *** /var/ftp/pub/cygwin/x86_64/setup.ini: error - package qiv requires package libpng14 which has no curr binary Jari, please fix your setup.hint files. Yaakov
Re: upset messages
2014-06-13 09:10 Yaakov Selkowitz yselkowitz-rDBXBDvO6BXQT0dZR+AlfA(at)public.gmane.org: | On 2014-06-13 01:04, | cygwin-no-reply-rDBXBDvO6BXQT0dZR+AlfA(at)public.gmane.org wrote: | | upset: *** /var/ftp/pub/cygwin/x86_64/setup.ini: error - package qiv | requires nonexistent package libpng14 | upset: *** /var/ftp/pub/cygwin/x86_64/setup.ini: error - package qiv | requires package libpng14 which has no curr binary | | Jari, please fix your setup.hint files. Fixed this, re-uploaded. Where can I see all upset messages? Jari
Re: upset messages
On 13/06/2014 08:23, Jari Aalto wrote: 2014-06-13 09:10 Yaakov Selkowitz yselkowitz-rDBXBDvO6BXQT0dZR+AlfA(at)public.gmane.org: | On 2014-06-13 01:04, | cygwin-no-reply-rDBXBDvO6BXQT0dZR+AlfA(at)public.gmane.org wrote: | | upset: *** /var/ftp/pub/cygwin/x86_64/setup.ini: error - package qiv | requires nonexistent package libpng14 | upset: *** /var/ftp/pub/cygwin/x86_64/setup.ini: error - package qiv | requires package libpng14 which has no curr binary | | Jari, please fix your setup.hint files. Fixed this, re-uploaded. Where can I see all upset messages? Jari https://sourceware.org/cygwin-apps/package-upload.html Although not shown above, you can also create a !mail (or !email) file which contains a list of email address (one per line) where any upset errors should be sent. If that isn't specified then you won't get email when upset finds issues with what was uploaded. Currently, this is not a per-directory thing since upset parsing doesn't work that way so, if you add a !email file you will get all errors from upset - not just ones associated to your uploaded packages. It doesn't matter where you create this file but it makes sense to put it at the root of your upload directory.
Re: upset messages
On 6/13/2014 4:02 PM, cygwin-no-re...@cygwin.com wrote: upset: Error. Parsing failed. - duplicate packages tig detected - x86/release/tig vs. /var/ftp/pub/cygwin/x86/release/git/tig Jari, here's another one that needs your attention. Ken
Re: upset messages
On 2014-06-13 16:25, Ken Brown wrote: On 6/13/2014 4:02 PM, cygwin-no-reply-rdbxbdvo6bxqt0dzr+a...@public.gmane.org wrote: upset: Error. Parsing failed. - duplicate packages tig detected - x86/release/tig vs. /var/ftp/pub/cygwin/x86/release/git/tig Jari, here's another one that needs your attention. I fixed this already by moving tig -- and the other git addons that weren't from git.src -- to $arch/release/. Yaakov
Re: inetutils upset messages
On Thu, Apr 10, 2014 at 07:38:08AM +0200, Achim Gratz wrote: Christopher Faylor writes: On Wed, Apr 09, 2014 at 11:28:25PM +0200, Achim Gratz wrote: It appears that the new setup.ini is generated before any file removals have happened, but after the copies have been done. No, that is not right. The setup.ini is created last. Then I have no idea how a setup.ini could have been created that refered to files that were already (correctly) removed from the ftp area. I've checked the timestamps on both and they were showing the same modification times. After sleeping on this, I see what happened now. I'll fix this in upset ASAP. cgf
Re: inetutils upset messages
On Thu, Apr 10, 2014 at 01:17:20PM -0400, Christopher Faylor wrote: On Thu, Apr 10, 2014 at 07:38:08AM +0200, Achim Gratz wrote: Christopher Faylor writes: On Wed, Apr 09, 2014 at 11:28:25PM +0200, Achim Gratz wrote: It appears that the new setup.ini is generated before any file removals have happened, but after the copies have been done. No, that is not right. The setup.ini is created last. Then I have no idea how a setup.ini could have been created that refered to files that were already (correctly) removed from the ftp area. I've checked the timestamps on both and they were showing the same modification times. After sleeping on this, I see what happened now. I'll fix this in upset ASAP. Should be fixed. cgf
Re: inetutils upset messages
Christopher Faylor writes: After sleeping on this, I see what happened now. I'll fix this in upset ASAP. Should be fixed. Thank you very much for your patience. I'll keep my paws from this for a while, though. :-) Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ DIY Stuff: http://Synth.Stromeko.net/DIY.html
Re: inetutils upset messages
On Thu, Apr 10, 2014 at 08:23:04PM +0200, Achim Gratz wrote: Christopher Faylor writes: After sleeping on this, I see what happened now. I'll fix this in upset ASAP. Should be fixed. Thank you very much for your patience. I'll keep my paws from this for a while, though. :-) There was nothing to be patient about since the real problems were all mine. Just about everything that you did should have been caught but upset wasn't up to the task. The current upload system is better than what we had but it is still too delicate for normal humans. Give me another ten years and I'll probably improve it. cgf
Re: inetutils upset messages
Christopher Faylor writes: Nevermind. Stupid coding error. It appears that the new setup.ini is generated before any file removals have happened, but after the copies have been done. I don't know if that will produce yet another error from upset (so far there are none), but since I was trying to get rid of the 1.9.1-1 packages the setup.ini refers to nonexistent prev files until the next run. Sorry for that. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: inetutils upset messages
Achim Gratz writes: Christopher Faylor writes: Nevermind. Stupid coding error. It appears that the new setup.ini is generated before any file removals have happened, but after the copies have been done. I don't know if that will produce yet another error from upset (so far there are none), but since I was trying to get rid of the 1.9.1-1 packages the setup.ini refers to nonexistent prev files until the next run. Sorry for that. Rats, upset is now upset… in any case, the intention was that inetutils-server-1.9.1-1.tar.xz should have been removed. The deletion cookies have been deleted from my upload area, but it doesn't appear to have had any effect on the ftp, probably since it triggered the error earlier than the removal. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: inetutils upset messages
On Wed, Apr 09, 2014 at 11:28:25PM +0200, Achim Gratz wrote: Christopher Faylor writes: Nevermind. Stupid coding error. It appears that the new setup.ini is generated before any file removals have happened, but after the copies have been done. No, that is not right. The setup.ini is created last. cgf
Re: inetutils upset messages
On Thu, Apr 10, 2014 at 12:32:59AM +0200, Achim Gratz wrote: Achim Gratz writes: Christopher Faylor writes: Nevermind. Stupid coding error. It appears that the new setup.ini is generated before any file removals have happened, but after the copies have been done. I don't know if that will produce yet another error from upset (so far there are none), but since I was trying to get rid of the 1.9.1-1 packages the setup.ini refers to nonexistent prev files until the next run. Sorry for that. Rats, upset is now upset… in any case, the intention was that inetutils-server-1.9.1-1.tar.xz should have been removed. The deletion cookies have been deleted from my upload area, but it doesn't appear to have had any effect on the ftp, probably since it triggered the error earlier than the removal. Did you try to delete inetutils-server after the first error showed up? That wouldn't have had any effect. The file deletion cookies are always deleted regardless of error state but that shouldn't matter too much because it shouldn't have been possible to get into a state where files were moved and the distro was compromised. So there is still a *#($ bug there. I guess I'll have to set up my test bed again and try to figure out how this happened. Would you happen to have a timeline for what you did, like: 22:41 UTC created -inetutils-1.9.1-1-src.tar.xz 23:06 UTC oops. 23:09 UTC created a -inetutils-debuginfo/-inetutils-debuginfo-1.9.1-1.tar.xz ? Maybe I can figure out from that what happened. cgf
Re: inetutils upset messages
Christopher Faylor writes: On Wed, Apr 09, 2014 at 11:28:25PM +0200, Achim Gratz wrote: It appears that the new setup.ini is generated before any file removals have happened, but after the copies have been done. No, that is not right. The setup.ini is created last. Then I have no idea how a setup.ini could have been created that refered to files that were already (correctly) removed from the ftp area. I've checked the timestamps on both and they were showing the same modification times. Did you try to delete inetutils-server after the first error showed up? That wouldn't have had any effect. I did initially forget that I also had to remove inetutils-server-1.9.1-1.tar.xz, so first I only deleted inetutils-1.9.1-1.tar.xz, inetutils-debuginfo-1.9.1-1.tar.xz and inetutils-1.9.1-1-src.tar.xz. Then the updater ran and produced a setup.ini that still referred to the now deleted files on the ftp area, but not sent an error mail at that time. So I went ahead and asked to delete those two files, which never happened. Just like the day before, the first error mail from upset was actually from the second run after the actual update. The file deletion cookies are always deleted regardless of error state but that shouldn't matter too much because it shouldn't have been possible to get into a state where files were moved and the distro was compromised. So there is still a *#($ bug there. I guess I'll have to set up my test bed again and try to figure out how this happened. Would you happen to have a timeline for what you did, like: 22:41 UTC created -inetutils-1.9.1-1-src.tar.xz 23:06 UTC oops. 23:09 UTC created a -inetutils-debuginfo/-inetutils-debuginfo-1.9.1-1.tar.xz Not to this detail; I compress my history, so I only ever have the last of each command, not any earlier invocations. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
inetutils upset messages
upset: *** /var/ftp/pub/cygwin/x86_64/setup.ini: warning - package inetutils-server refers to nonexistent external-source: inetutils This is a valid error since there was no inetutils-1.9.1-2-src.tar.xz I fixed that but I don't understand is how this ended up in the release area in that state. ... Nevermind. Stupid coding error. In the *future* this should not leave the release area in an inconsistent state. Btw, I should mention that the setup.ini generation happens once an hour at (currently) 2 minutes past the hour. I do tend to change that when I'm working on a problem but once an hour should be a constant unless there is a serious problem requiring complete shutdown of setup.ini generation. cgf
Re: inetutils upset messages
Christopher Faylor writes: upset: *** /var/ftp/pub/cygwin/x86_64/setup.ini: warning - package inetutils-server refers to nonexistent external-source: inetutils This is a valid error since there was no inetutils-1.9.1-2-src.tar.xz I fixed that but I don't understand is how this ended up in the release area in that state. Sorry, this is my fault – apologies to everyone who got these messages. I patched the inetutils server archive, but since I didn't touch the source I didn't copy it with the new name. I was actually suspecting an error from upset, but when the new setup.ini was up and correct and no messages from upset arrived I thought it was OK with it. The first two upset messages came in two hours after the upload, so I didn't see them. I'll fix up inetutils packaging for good this evening. At the moment the setup.ini is OK, but the previous version isn't going to show correctly. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: upset messages
On Sun, Feb 23, 2014 at 03:43:48PM -0500, Christopher Faylor wrote: On Sun, Feb 23, 2014 at 10:07:24AM -, cygwin-no-reply wrote: upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag I don't understand why this is happening. One of the reason upset is complaining is because obsolete x86 curl-devel doesn't have an empty tarball associated with it but it doesn't look like it ever did. FWIW, upset assumed that there would always be a tarball in the same directory as a setup.hint. Can anyone explain what changed between 9:36 - 10:06 this morning to cause this to start happening? Actually, I guess it could have happened earlier than that since we apparently had a disk full condition on sourceware. cgf
Re: upset messages
On Sun, Feb 23, 2014 at 10:07:24AM -, cygwin-no-reply wrote: upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag upset: *** package missing category tag I don't understand why this is happening. One of the reason upset is complaining is because obsolete x86 curl-devel doesn't have an empty tarball associated with it but it doesn't look like it ever did. FWIW, upset assumed that there would always be a tarball in the same directory as a setup.hint. Can anyone explain what changed between 9:36 - 10:06 this morning to cause this to start happening? cgf
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
upset messages
/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
SuiteSparse: upset messages
On 2013-07-15 16:43, upset lived up to its name and complained: upset: *** /sourceware/ftp/pub/cygwin/x86/setup.ini: warning - package libSuiteSparse-devel refers to nonexistent external-source: SuiteSparse Marco, The problem was that libSuiteSparse-devel-3.7.1-1 was left without a source package of the same version. I moved that out of the way for now; let me know if you need it restored. Yaakov
Re: SuiteSparse: upset messages
Il 7/15/2013 11:49 PM, Yaakov (Cygwin/X) ha scritto: On 2013-07-15 16:43, upset lived up to its name and complained: upset: *** /sourceware/ftp/pub/cygwin/x86/setup.ini: warning - package libSuiteSparse-devel refers to nonexistent external-source: SuiteSparse Marco, The problem was that libSuiteSparse-devel-3.7.1-1 was left without a source package of the same version. I moved that out of the way for now; let me know if you need it restored. Yaakov I forgot to remove it, thanks Marco
Re: zlib: upset messages
On 5/14/2012 1:32 AM, Yaakov (Cygwin/X) wrote: On 2012-05-14 00:31, upset lived up to its name and complained: upset: *** setup.ini: warning - package minizip requires non-existent package libgcc_1 I made the obvious fix on sourceware; please fix your local copy, etc. Thanks (and sorry for the trouble). -- Chuck
zlib: upset messages
On 2012-05-14 00:31, upset lived up to its name and complained: upset: *** setup.ini: warning - package minizip requires non-existent package libgcc_1 Chuck, I made the obvious fix on sourceware; please fix your local copy, etc. Yaakov
