From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: upset messages
Date: Sun, 23 Feb 2014 20:43:00 -0000 [thread overview]
Message-ID: <20140223204348.GA5247@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20140223100724.14828.qmail@sourceware.org>
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
next parent reply other threads:[~2014-02-23 20:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140223100724.14828.qmail@sourceware.org>
2014-02-23 20:43 ` Christopher Faylor [this message]
2014-02-23 20:45 ` Christopher Faylor
[not found] <20150206071012.17498.qmail@sourceware.org>
2015-02-06 10:55 ` Fwd: " Marco Atzeri
2015-02-06 11:47 ` Corinna Vinschen
2015-02-06 17:11 ` Yaakov Selkowitz
[not found] <20140811221133.3852.qmail@sourceware.org>
2014-08-11 22:37 ` David Stacey
2014-08-11 22:48 ` Yaakov Selkowitz
[not found] <20140613200237.24877.qmail@sourceware.org>
2014-06-13 21:25 ` Ken Brown
2014-06-13 23:07 ` Yaakov Selkowitz
[not found] <20140613060445.15838.qmail@sourceware.org>
2014-06-13 6:10 ` Yaakov Selkowitz
2014-06-13 6:23 ` Jari Aalto
2014-06-13 10:59 ` Marco Atzeri
2013-11-29 1:46 Christopher Faylor
2013-11-29 10:10 ` marco atzeri
2013-11-29 13:58 ` Christopher Faylor
2013-11-29 14:32 ` marco atzeri
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=20140223204348.GA5247@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--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).