Strange new release-2 errors from upset

Strange new release-2 errors from upset

[Christopher Faylor]

>upset: *** setup-2.ini: warning - package ORBit2-devel requires non-existent package minires-devel
>upset: *** setup-2.ini: warning - package atk requires non-existent package glib2-runtime
>upset: *** setup-2.ini: warning - package desktop-file-utils requires non-existent package glib2-runtime
>upset: *** setup-2.ini: warning - package gail requires non-existent package atk-runtime
>upset: *** setup-2.ini: warning - package libbonoboui2 requires non-existent package atk-runtime
>upset: *** setup-2.ini: warning - package libbonoboui2 requires non-existent package glib2-runtime
>upset: *** setup-2.ini: warning - package libclamav-devel requires non-existent package minires-devel
>upset: *** setup-2.ini: warning - package libglade2 requires non-existent package atk-runtime
>upset: *** setup-2.ini: warning - package libglade2 requires non-existent package glib2-runtime
>upset: *** setup-2.ini: warning - package libgnomeprint22 requires non-existent package glib2-runtime
>upset: *** setup-2.ini: warning - package libgnomeui2 requires non-existent package atk-runtime
>upset: *** setup-2.ini: warning - package libgtkhtml2 requires non-existent package atk-runtime
>upset: *** setup-2.ini: warning - package libserf0-devel requires non-existent package apr1
>upset: *** setup-2.ini: warning - package libserf0-devel requires non-existent package aprutil1
>upset: *** setup-2.ini: warning - package libwnck1_18 requires non-existent package atk-runtime
>upset: *** setup-2.ini: warning - package perl-ExtUtils-PkgConfig requires non-existent package pkgconfig
>upset: *** setup-2.ini: warning - package pygtk2 requires non-existent package atk-runtime
>upset: *** setup-2.ini: warning - package pygtk2 requires non-existent package glib2-runtime
>upset: *** setup-2.ini: warning - package rpm requires non-existent package mktemp
>upset: *** setup-2.ini: warning - package tetex-bin requires non-existent package clear

I've only looked at a handful of the above but they all seem to be valid
complaints.  I can't explain why they are just showing up now because all
of the changes seem to have been done months ago.  For instance, there are
no glib2-runtime or minires-devel directories in release-2 but that is not
a recent change.

Can anyone explain what's going on here?  Did we possibly lose some setup.hint
files from the release-2 directory hierarchy?

cgf

Re: Strange new release-2 errors from upset

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
>> upset: *** setup-2.ini: warning - package ORBit2-devel requires non-existent package minires-devel
>> upset: *** setup-2.ini: warning - package atk requires non-existent package glib2-runtime
>> upset: *** setup-2.ini: warning - package desktop-file-utils requires non-existent package glib2-runtime
>> upset: *** setup-2.ini: warning - package gail requires non-existent package atk-runtime
>> upset: *** setup-2.ini: warning - package libbonoboui2 requires non-existent package atk-runtime
>> upset: *** setup-2.ini: warning - package libbonoboui2 requires non-existent package glib2-runtime
>> upset: *** setup-2.ini: warning - package libclamav-devel requires non-existent package minires-devel
>> upset: *** setup-2.ini: warning - package libglade2 requires non-existent package atk-runtime
>> upset: *** setup-2.ini: warning - package libglade2 requires non-existent package glib2-runtime
>> upset: *** setup-2.ini: warning - package libgnomeprint22 requires non-existent package glib2-runtime
>> upset: *** setup-2.ini: warning - package libgnomeui2 requires non-existent package atk-runtime
>> upset: *** setup-2.ini: warning - package libgtkhtml2 requires non-existent package atk-runtime
>> upset: *** setup-2.ini: warning - package libserf0-devel requires non-existent package apr1
>> upset: *** setup-2.ini: warning - package libserf0-devel requires non-existent package aprutil1
>> upset: *** setup-2.ini: warning - package libwnck1_18 requires non-existent package atk-runtime
>> upset: *** setup-2.ini: warning - package perl-ExtUtils-PkgConfig requires non-existent package pkgconfig
>> upset: *** setup-2.ini: warning - package pygtk2 requires non-existent package atk-runtime
>> upset: *** setup-2.ini: warning - package pygtk2 requires non-existent package glib2-runtime
>> upset: *** setup-2.ini: warning - package rpm requires non-existent package mktemp
>> upset: *** setup-2.ini: warning - package tetex-bin requires non-existent package clear
> 
> I've only looked at a handful of the above but they all seem to be valid
> complaints.  I can't explain why they are just showing up now because all
> of the changes seem to have been done months ago.  For instance, there are
> no glib2-runtime or minires-devel directories in release-2 but that is not
> a recent change.

The "non-existent" packages are all currently empty, obsolete packages.

glib2-runtime -> glib2
atk-runtime -> atk
pkgconfig -> pkg-config
clear -> ncurses
minires-devel -> cygwin-1.7.x
apr1 -> libapr1-devel
aprutil1 -> libaprutil1-devel

The exception is mktemp, which AFAICS is still a real package.

I don't know why this the errors just started now, because I thought all
obsolete packages weren't be copied into release-2.


Yaakov

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkYspcACgkQpiWmPGlmQSOSjQCg5ExxcDNqLsDpgl0WHCe9hIti
1DsAoObt7P5kYE85hnBI2KbVyahfL6CZ
=mUIL
-----END PGP SIGNATURE-----

Re: Strange new release-2 errors from upset

[Christopher Faylor]

On Mon, Nov 10, 2008 at 04:15:52PM -0600, Yaakov (Cygwin Ports) wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>Christopher Faylor wrote:
>>> upset: *** setup-2.ini: warning - package ORBit2-devel requires non-existent package minires-devel
>>> upset: *** setup-2.ini: warning - package atk requires non-existent package glib2-runtime
>>> upset: *** setup-2.ini: warning - package desktop-file-utils requires non-existent package glib2-runtime
>>> upset: *** setup-2.ini: warning - package gail requires non-existent package atk-runtime
>>> upset: *** setup-2.ini: warning - package libbonoboui2 requires non-existent package atk-runtime
>>> upset: *** setup-2.ini: warning - package libbonoboui2 requires non-existent package glib2-runtime
>>> upset: *** setup-2.ini: warning - package libclamav-devel requires non-existent package minires-devel
>>> upset: *** setup-2.ini: warning - package libglade2 requires non-existent package atk-runtime
>>> upset: *** setup-2.ini: warning - package libglade2 requires non-existent package glib2-runtime
>>> upset: *** setup-2.ini: warning - package libgnomeprint22 requires non-existent package glib2-runtime
>>> upset: *** setup-2.ini: warning - package libgnomeui2 requires non-existent package atk-runtime
>>> upset: *** setup-2.ini: warning - package libgtkhtml2 requires non-existent package atk-runtime
>>> upset: *** setup-2.ini: warning - package libserf0-devel requires non-existent package apr1
>>> upset: *** setup-2.ini: warning - package libserf0-devel requires non-existent package aprutil1
>>> upset: *** setup-2.ini: warning - package libwnck1_18 requires non-existent package atk-runtime
>>> upset: *** setup-2.ini: warning - package perl-ExtUtils-PkgConfig requires non-existent package pkgconfig
>>> upset: *** setup-2.ini: warning - package pygtk2 requires non-existent package atk-runtime
>>> upset: *** setup-2.ini: warning - package pygtk2 requires non-existent package glib2-runtime
>>> upset: *** setup-2.ini: warning - package rpm requires non-existent package mktemp
>>> upset: *** setup-2.ini: warning - package tetex-bin requires non-existent package clear
>> 
>> I've only looked at a handful of the above but they all seem to be valid
>> complaints.  I can't explain why they are just showing up now because all
>> of the changes seem to have been done months ago.  For instance, there are
>> no glib2-runtime or minires-devel directories in release-2 but that is not
>> a recent change.
>
>The "non-existent" packages are all currently empty, obsolete packages.
>
>glib2-runtime -> glib2
>atk-runtime -> atk
>pkgconfig -> pkg-config
>clear -> ncurses
>minires-devel -> cygwin-1.7.x
>apr1 -> libapr1-devel
>aprutil1 -> libaprutil1-devel
>
>The exception is mktemp, which AFAICS is still a real package.

The mktemp package is obsolete.  It comes from coreutils these days.

I guess I should have made it clear that these were obsolete packages
and hence were not part of the release-2 hierarchy.  I don't understand
why non-obsolete packages in release are relying on obsolete packages
though.

>I don't know why this the errors just started now, because I thought
>all obsolete packages weren't be copied into release-2.

That one is a mystery.  I didn't see any creation dates which would
explain this.

cgf

Re: Strange new release-2 errors from upset

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Christopher Faylor wrote:
> The mktemp package is obsolete.  It comes from coreutils these days.

Then the transition wasn't correctly handled, because the latest
mktemp-1.5-4 is a real package.  An empty 1.5-5 package should have been
created at the same time as coreutils-6.10-1 so that mktemp's mktemp(1)
would be replaced by coreutils'.

It's not too late to fix that, provided we artificially bump coreutils
to 6.10-2 simultaneously.

> I guess I should have made it clear that these were obsolete packages
> and hence were not part of the release-2 hierarchy.  I don't understand
> why non-obsolete packages in release are relying on obsolete packages
> though.

In some of those cases, IIRC the dependency was current when the file
was uploaded and made obsolete later.

The GNOME stuff is all mine; once the X11 transition takes place, I can
start working on moving those GNOME libraries from Ports back into the
distro.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkY37oACgkQpiWmPGlmQSMo8wCgoQwWHc0CY/5v8PAk8N26I/gc
gLcAoKMa+YITHIdyfar+X0i5BIEpjGXZ
=u+X+
-----END PGP SIGNATURE-----

Re: Strange new release-2 errors from upset

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Yaakov (Cygwin Ports) on 11/10/2008 6:28 PM:
> Then the transition wasn't correctly handled, because the latest
> mktemp-1.5-4 is a real package.  An empty 1.5-5 package should have been
> created at the same time as coreutils-6.10-1 so that mktemp's mktemp(1)
> would be replaced by coreutils'.
> 
> It's not too late to fix that, provided we artificially bump coreutils
> to 6.10-2 simultaneously.

I'm on it.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkY5+UACgkQ84KuGfSFAYBvdgCdFObm2BcghmV64Peg7w+T4ajA
fV8AoMeOJmb+sPKb1vzCR2uSQcviNNWW
=kwLI
-----END PGP SIGNATURE-----

Re: Strange new release-2 errors from upset

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Eric Blake wrote:
> I'm on it.

Can you hold off uploading until X11 is in place (hopefully by
tomorrow)?  I'm having enough trouble keeping the staging area in sync
with release as it is.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkY8vkACgkQpiWmPGlmQSNFIACeL7Dyv0ANK8TFHDOV9sgcC8jJ
insAoIMFVfSFqcv15rQh5QYXtVwQu62Y
=4BkD
-----END PGP SIGNATURE-----

Re: Strange new release-2 errors from upset

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Yaakov (Cygwin Ports) on 11/10/2008 7:50 PM:
> Eric Blake wrote:
>> I'm on it.
> 
> Can you hold off uploading until X11 is in place (hopefully by
> tomorrow)?  I'm having enough trouble keeping the staging area in sync
> with release as it is.

Sure.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkY9McACgkQ84KuGfSFAYCYpQCgsGPq8+YHqpjvZGAX3rhTH0zP
Q5sAoMI13dX9LTB+8EmIeOzhFJng5E/C
=BDwA
-----END PGP SIGNATURE-----

Re: Strange new release-2 errors from upset

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Eric Blake wrote:
>> Can you hold off uploading until X11 is in place (hopefully by
>> tomorrow)?  I'm having enough trouble keeping the staging area in sync
>> with release as it is.
> 
> Sure.

X11 is in place now, so whenever you're ready.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkkagqMACgkQpiWmPGlmQSM81gCgsb+0VBcCNesP+ijm85FYUmnt
1wAAn3sIq5PzAi6IBLoSsSCFrurZPwy9
=sDZA
-----END PGP SIGNATURE-----

Re: Strange new release-2 errors from upset

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Yaakov (Cygwin Ports) on 11/10/2008 6:28 PM:
> Christopher Faylor wrote:
>> The mktemp package is obsolete.  It comes from coreutils these days.
> 
> Then the transition wasn't correctly handled, because the latest
> mktemp-1.5-4 is a real package.  An empty 1.5-5 package should have been
> created at the same time as coreutils-6.10-1 so that mktemp's mktemp(1)
> would be replaced by coreutils'.
> 
> It's not too late to fix that, provided we artificially bump coreutils
> to 6.10-2 simultaneously.

Chuck, according to http://cygwin.com/cygwin-pkg-maint, you still own
mktemp.  I've got the coreutils-6.10-2 build ready to go on release; are
you in a position to push an empty tarball as mktemp-1.5-5, or would you
like me to take care of that as part of pushing the updated coreutils?

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkdBQUACgkQ84KuGfSFAYD9xgCfeScpljncQpWigrHS6Yo2bY45
Ni4AoIfQAYoSmAZ95z+cV+UdoYlu0aAZ
=aqm2
-----END PGP SIGNATURE-----

Re: Strange new release-2 errors from upset

[Charles Wilson]

Eric Blake wrote:

> Chuck, according to http://cygwin.com/cygwin-pkg-maint, you still own
> mktemp.  I've got the coreutils-6.10-2 build ready to go on release; are
> you in a position to push an empty tarball as mktemp-1.5-5, or would you
> like me to take care of that as part of pushing the updated coreutils?

You can go ahead and do it when you're ready, since they both need to
happen more-or-less simultaneously.

--
Chuck

Re: Strange new release-2 errors from upset

[Christopher Faylor]

On Thu, Nov 13, 2008 at 09:56:37PM -0700, Eric Blake wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>According to Yaakov (Cygwin Ports) on 11/10/2008 6:28 PM:
>> Christopher Faylor wrote:
>>> The mktemp package is obsolete.  It comes from coreutils these days.
>> 
>> Then the transition wasn't correctly handled, because the latest
>> mktemp-1.5-4 is a real package.  An empty 1.5-5 package should have been
>> created at the same time as coreutils-6.10-1 so that mktemp's mktemp(1)
>> would be replaced by coreutils'.
>> 
>> It's not too late to fix that, provided we artificially bump coreutils
>> to 6.10-2 simultaneously.
>
>Chuck, according to http://cygwin.com/cygwin-pkg-maint, you still own
>mktemp.  I've got the coreutils-6.10-2 build ready to go on release;
>are you in a position to push an empty tarball as mktemp-1.5-5, or
>would you like me to take care of that as part of pushing the updated
>coreutils?

I just created an empty mktemp-1.999-9 package.  It occurred to me that
maybe we should be giving these packages a little more distinctive names
so that it is obvious that they are "special".

cgf

Re: Strange new release-2 errors from upset

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Christopher Faylor on 11/13/2008 10:07 PM:
>> Chuck, according to http://cygwin.com/cygwin-pkg-maint, you still own
>> mktemp.  I've got the coreutils-6.10-2 build ready to go on release;
>> are you in a position to push an empty tarball as mktemp-1.5-5, or
>> would you like me to take care of that as part of pushing the updated
>> coreutils?
> 
> I just created an empty mktemp-1.999-9 package.  It occurred to me that
> maybe we should be giving these packages a little more distinctive names
> so that it is obvious that they are "special".

And coreutils-6.10-2 is in place, so hopefully the transition is smooth.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkdCHcACgkQ84KuGfSFAYA9MgCgk4gpdqdIfOG2na6OjUd1CFuO
HlQAoKlqzLKeXWjd0QVqPIaU/vNFJlfg
=xrPi
-----END PGP SIGNATURE-----

Re: Strange new release-2 errors from upset

[Corinna Vinschen]

On Nov 13 22:11, Eric Blake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> According to Christopher Faylor on 11/13/2008 10:07 PM:
> >> Chuck, according to http://cygwin.com/cygwin-pkg-maint, you still own
> >> mktemp.  I've got the coreutils-6.10-2 build ready to go on release;
> >> are you in a position to push an empty tarball as mktemp-1.5-5, or
> >> would you like me to take care of that as part of pushing the updated
> >> coreutils?
> > 
> > I just created an empty mktemp-1.999-9 package.  It occurred to me that
> > maybe we should be giving these packages a little more distinctive names
> > so that it is obvious that they are "special".
> 
> And coreutils-6.10-2 is in place, so hopefully the transition is smooth.

I changed the mktemp maintanership to OBSOLETE.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat