From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: how to obsolete now-removed subpackage?
Date: Thu, 20 Jan 2022 13:42:38 +0000 [thread overview]
Message-ID: <c4de2caa-da79-5d4c-4ada-731f4b59eba1@dronecode.org.uk> (raw)
In-Reply-To: <84551e01-2f6d-21d5-27e0-4237badd8ec0@cornell.edu>
On 20/01/2022 13:12, Ken Brown wrote:
> On 1/20/2022 7:14 AM, Glenn Strauss wrote:
>> lighttpd 1.4.64 removes long-deprecated packages,
>> including mod_trigger_b4_dl (replaceable with a lua script, if needed)
>>
>> I am trying to build using lighttpd.cygport and after uploading package
>> 1.4.64-1, I got errors, so I tried adding
>> PKG_OBSOLETES="lighttpd-mod_trigger_b4_dl"
>> to lighttpd.cygport and building lighttpd.cyport package 1.4.64-2
>
>> Am I using PKG_OBSOLETES incorrectly?
>
> Yes. The cygport manual says that PKG_OBSOLETES is "A single-line
> string containing a list of package(s) which this package replaces....
> Note that the PKG_OBSOLETES name is descriptive rather than literal,
> where "PKG" should be substituted with the name of the binary package
> whose contents it describes."
I think this might be a bug in calm (which processes the package uploads).
How OBSOLETES is put into effect has changed slightly in the latest
version of cygport, and calm hasn't caught up with it yet.
Thanks for reporting this.
next prev parent reply other threads:[~2022-01-20 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164267844372.1313732.6963001602045507938@server2.sourceware.org>
2022-01-20 12:14 ` Glenn Strauss
2022-01-20 13:12 ` Ken Brown
2022-01-20 13:42 ` Jon Turney [this message]
2022-01-20 14:00 ` Jon Turney
2022-01-20 14:04 ` Glenn Strauss
2022-01-20 15:57 ` Jon Turney
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=c4de2caa-da79-5d4c-4ada-731f4b59eba1@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).