how to obsolete now-removed subpackage?
Jon Turney
jon.turney@dronecode.org.uk
Thu Jan 20 14:00:02 GMT 2022
On 20/01/2022 13:42, Jon Turney wrote:
> 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."
Reading this again...
To be clear, PKG needs to be replaced by the name of a package. So, you
probably want something like:
lighttpd_OBSOLETES="lighttpd-mod_trigger_b4_dl"
> 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.
... but there might still be an issue I need to think about here.
More information about the Cygwin-apps
mailing list