From: "Yaakov (Cygwin Ports)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: Strange new release-2 errors from upset
Date: Mon, 10 Nov 2008 22:16:00 -0000 [thread overview]
Message-ID: <4918B298.9070200@users.sourceforge.net> (raw)
In-Reply-To: <20081107142844.GA9369@ednor.casa.cgf.cx>
-----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-----
next prev parent reply other threads:[~2008-11-10 22:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 14:29 Christopher Faylor
2008-11-10 22:16 ` Yaakov (Cygwin Ports) [this message]
2008-11-10 23:18 ` Christopher Faylor
2008-11-11 1:29 ` Yaakov (Cygwin Ports)
2008-11-11 2:03 ` Eric Blake
2008-11-11 2:51 ` Yaakov (Cygwin Ports)
2008-11-11 2:58 ` Eric Blake
2008-11-12 7:16 ` Yaakov (Cygwin Ports)
2008-11-14 4:56 ` Eric Blake
2008-11-14 5:06 ` Charles Wilson
2008-11-14 5:08 ` Christopher Faylor
2008-11-14 5:11 ` Eric Blake
2008-11-14 8:33 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4918B298.9070200@users.sourceforge.net \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).