Fwd: upset messages

Fwd: upset messages

[Marco Atzeri]

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 -0000
From: cygwin-no-reply@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-plpython

Re: upset messages

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 326 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: upset messages

[Yaakov Selkowitz]

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

[Yaakov Selkowitz]

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

[David Stacey]

On 11/08/14 23:11, cygwin-no-reply@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

[Yaakov Selkowitz]

On 2014-06-13 16:25, Ken Brown wrote:
> On 6/13/2014 4:02 PM,
> cygwin-no-reply-rDBXBDvO6BXQT0dZR+AlfA@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: upset messages

[Ken Brown]

On 6/13/2014 4:02 PM, cygwin-no-reply@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

[Marco Atzeri]

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

[Jari Aalto]

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

[Yaakov Selkowitz]

On 2014-06-13 01:04, cygwin-no-reply@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

[Christopher Faylor]

On Sun, Feb 23, 2014 at 03:43:48PM -0500, Christopher Faylor wrote:
>On Sun, Feb 23, 2014 at 10:07:24AM -0000, 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

[Christopher Faylor]

On Sun, Feb 23, 2014 at 10:07:24AM -0000, 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

[marco atzeri]

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
>

Re: upset messages

[Christopher Faylor]

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

[marco atzeri]

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

upset messages

[Christopher Faylor]

/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