* how to obsolete now-removed subpackage?
[not found] <164267844372.1313732.6963001602045507938@server2.sourceware.org>
@ 2022-01-20 12:14 ` Glenn Strauss
2022-01-20 13:12 ` Ken Brown
0 siblings, 1 reply; 6+ messages in thread
From: Glenn Strauss @ 2022-01-20 12:14 UTC (permalink / raw)
To: cygwin-apps
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
On Thu, Jan 20, 2022 at 11:34:03AM -0000, cygwin-apps@cygwin.com wrote:
> ERROR: install packages from source package 'lighttpd' have non-unique current versions 1.4.63-1 (lighttpd-mod_trigger_b4_dl), 1.4.64-2 (15 others)
> ERROR: error while validating merged x86_64 packages for Glenn Strauss
> SUMMARY: 2 ERROR(s)
Am I using PKG_OBSOLETES incorrectly?
Is there something else I need to do to remove this subpackage?
Thanks. Glenn
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: how to obsolete now-removed subpackage?
2022-01-20 12:14 ` how to obsolete now-removed subpackage? Glenn Strauss
@ 2022-01-20 13:12 ` Ken Brown
2022-01-20 13:42 ` Jon Turney
0 siblings, 1 reply; 6+ messages in thread
From: Ken Brown @ 2022-01-20 13:12 UTC (permalink / raw)
To: cygwin-apps
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."
> Is there something else I need to do to remove this subpackage?
I think what you want is simply for lighttpd-mod_trigger_b4_dl to be empty,
which you can achieve with
lighttpd_mod_trigger_b4_dl_CONTENTS=
Ken
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: how to obsolete now-removed subpackage?
2022-01-20 13:12 ` Ken Brown
@ 2022-01-20 13:42 ` Jon Turney
2022-01-20 14:00 ` Jon Turney
0 siblings, 1 reply; 6+ messages in thread
From: Jon Turney @ 2022-01-20 13:42 UTC (permalink / raw)
To: cygwin-apps
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: how to obsolete now-removed subpackage?
2022-01-20 13:42 ` Jon Turney
@ 2022-01-20 14:00 ` Jon Turney
2022-01-20 14:04 ` Glenn Strauss
2022-01-20 15:57 ` Jon Turney
0 siblings, 2 replies; 6+ messages in thread
From: Jon Turney @ 2022-01-20 14:00 UTC (permalink / raw)
To: cygwin-apps
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: how to obsolete now-removed subpackage?
2022-01-20 14:00 ` Jon Turney
@ 2022-01-20 14:04 ` Glenn Strauss
2022-01-20 15:57 ` Jon Turney
1 sibling, 0 replies; 6+ messages in thread
From: Glenn Strauss @ 2022-01-20 14:04 UTC (permalink / raw)
To: Jon Turney; +Cc: cygwin-apps
On Thu, Jan 20, 2022 at 02:00:02PM +0000, Jon Turney wrote:
> 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"
It makes sense now that you and Ken have explained it, but I
misunderstood that when comparing PKG_OBSOLETES to PKG_NAMES.
Maybe the documentation could use <PKG>_OBSOLETES in places
where <PKG> is expected to be replaced with a package name?
Cheers, Glenn
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: how to obsolete now-removed subpackage?
2022-01-20 14:00 ` Jon Turney
2022-01-20 14:04 ` Glenn Strauss
@ 2022-01-20 15:57 ` Jon Turney
1 sibling, 0 replies; 6+ messages in thread
From: Jon Turney @ 2022-01-20 15:57 UTC (permalink / raw)
To: cygwin-apps
On 20/01/2022 14:00, Jon Turney wrote:
> 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.
Yeah.
The upload you tried with my suggested change to the cygport failed for
the reasons I suspected.
I've deployed a fix.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-01-20 15:58 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <164267844372.1313732.6963001602045507938@server2.sourceware.org>
2022-01-20 12:14 ` how to obsolete now-removed subpackage? Glenn Strauss
2022-01-20 13:12 ` Ken Brown
2022-01-20 13:42 ` Jon Turney
2022-01-20 14:00 ` Jon Turney
2022-01-20 14:04 ` Glenn Strauss
2022-01-20 15:57 ` Jon Turney
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).