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:
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
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
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
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
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,
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
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,
| 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
| 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
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
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
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.
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
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
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
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
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),
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
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
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
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.
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
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
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
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
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.
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
/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
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
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
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
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
33 matches
Mail list logo
