* Re: Fwd: calm: cygwin package report for Ken Brown
2023-03-20 23:17 ` Jon Turney
@ 2023-03-20 23:42 ` gs-cygwin.com
2023-03-21 2:10 ` Ken Brown
` (2 subsequent siblings)
3 siblings, 0 replies; 10+ messages in thread
From: gs-cygwin.com @ 2023-03-20 23:42 UTC (permalink / raw)
To: Jon Turney; +Cc: cygwin-apps, Ken Brown
On Mon, Mar 20, 2023 at 11:17:38PM +0000, Jon Turney via Cygwin-apps wrote:
> On 20/03/2023 22:17, Ken Brown via Cygwin-apps wrote:
> > It looks like my plan for having scallywag deploy all the TeX Live
> > packages won't work (see below). calm would have to be more permissive
> > and allow deploying a package that requires something that will be
> > provided by a future package.
> >
> > In this case, I made asymptote require tl_2023, which will be provided
> > by the next texlive release. But I don't want to deploy the latter
> > until all the other packages for TeX Live 2023 have been deployed.
> >
> > Unless this is easy to fix, I'll just forget about using scallywag and
> > go back to my old method of uploading everything manually.
>
> This is trivially fixable.
>
> calm already has a list of 'provides which don't exist (yet)', so I think I
> just need to add tl_2023 and tl_basic_2023 to that list
>
> Future work: make these regexes so we don't have same problem again in a
> years time.
>
> >
> > Ken
> >
> > -------- Forwarded Message --------
> > Subject: calm: cygwin package report for Ken Brown
> > Date: Mon, 20 Mar 2023 21:57:12 -0000
> > From: cygwin-no-reply-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org
> > Reply-To: cygwin-apps-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org
> > To: kbrown-HmMyXyqgL2CVc3sceRu5cw@public.gmane.org
> >
> > ERROR: package 'asymptote' version '2.85-1' depends: 'tl_2023', but
> > nothing satisfies that
> > ERROR: error while validating merged x86_64 packages for Ken Brown
> > SUMMARY: 2 ERROR(s)
>
> Maybe calm doesn't need to do this kind of check any more?
>
> But then people might write REQUIRES="typoed-package-name" and not notice
> until it's uninstallable, so I don't know.
It seems to me like a useful warning, whether or not it remains an
error here. Also, it seems to me like this check could be added to
prevent packages from being released (other than to 'test') since an
uninstallable package is an uninstallable package, though circular
dependencies could then be an issue for releasing. (Yes, avoid those!)
Cheers, Glenn
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Fwd: calm: cygwin package report for Ken Brown
2023-03-20 23:17 ` Jon Turney
2023-03-20 23:42 ` gs-cygwin.com
@ 2023-03-21 2:10 ` Ken Brown
2023-03-21 8:55 ` Corinna Vinschen
2024-02-19 18:59 ` Ken Brown
3 siblings, 0 replies; 10+ messages in thread
From: Ken Brown @ 2023-03-21 2:10 UTC (permalink / raw)
To: Jon Turney, cygwin-apps
On 3/20/2023 7:17 PM, Jon Turney wrote:
> On 20/03/2023 22:17, Ken Brown via Cygwin-apps wrote:
>> It looks like my plan for having scallywag deploy all the TeX Live
>> packages won't work (see below). calm would have to be more
>> permissive and allow deploying a package that requires something that
>> will be provided by a future package.
[...]
> This is trivially fixable.
>
> calm already has a list of 'provides which don't exist (yet)', so I
> think I just need to add tl_2023 and tl_basic_2023 to that list
Thanks!
[...]
> Maybe calm doesn't need to do this kind of check any more?
>
> But then people might write REQUIRES="typoed-package-name" and not
> notice until it's uninstallable, so I don't know.
I don't know either, but I think I lean toward not doing the check, in
order to give maintainers maximum flexibility. In your example, the
problem is easily fixed as soon as the maintainer (or someone else)
notices that the package is uninstallable. And when they try to select
it for installation, setup will immediately tell them what the problem is.
Ken
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Fwd: calm: cygwin package report for Ken Brown
2023-03-20 23:17 ` Jon Turney
2023-03-20 23:42 ` gs-cygwin.com
2023-03-21 2:10 ` Ken Brown
@ 2023-03-21 8:55 ` Corinna Vinschen
2024-02-19 18:59 ` Ken Brown
3 siblings, 0 replies; 10+ messages in thread
From: Corinna Vinschen @ 2023-03-21 8:55 UTC (permalink / raw)
To: cygwin-apps
On Mar 20 23:17, Jon Turney via Cygwin-apps wrote:
> On 20/03/2023 22:17, Ken Brown via Cygwin-apps wrote:
> > It looks like my plan for having scallywag deploy all the TeX Live
> > packages won't work (see below). calm would have to be more permissive
> > and allow deploying a package that requires something that will be
> > provided by a future package.
> >
> > In this case, I made asymptote require tl_2023, which will be provided
> > by the next texlive release. But I don't want to deploy the latter
> > until all the other packages for TeX Live 2023 have been deployed.
> >
> > Unless this is easy to fix, I'll just forget about using scallywag and
> > go back to my old method of uploading everything manually.
>
> This is trivially fixable.
>
> calm already has a list of 'provides which don't exist (yet)', so I think I
> just need to add tl_2023 and tl_basic_2023 to that list
>
> Future work: make these regexes so we don't have same problem again in a
> years time.
Wouldn't it make sense to be able to define this in the cygport file
somehow? Or does that open a can of worms?
Corinna
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Fwd: calm: cygwin package report for Ken Brown
2023-03-20 23:17 ` Jon Turney
` (2 preceding siblings ...)
2023-03-21 8:55 ` Corinna Vinschen
@ 2024-02-19 18:59 ` Ken Brown
2024-02-19 19:22 ` Jon Turney
3 siblings, 1 reply; 10+ messages in thread
From: Ken Brown @ 2024-02-19 18:59 UTC (permalink / raw)
To: Jon Turney, cygwin-apps
On 3/20/2023 7:17 PM, Jon Turney wrote:
> On 20/03/2023 22:17, Ken Brown via Cygwin-apps wrote:
>> It looks like my plan for having scallywag deploy all the TeX Live
>> packages won't work (see below). calm would have to be more
>> permissive and allow deploying a package that requires something that
>> will be provided by a future package.
>>
>> In this case, I made asymptote require tl_2023, which will be provided
>> by the next texlive release. But I don't want to deploy the latter
>> until all the other packages for TeX Live 2023 have been deployed.
>>
>> Unless this is easy to fix, I'll just forget about using scallywag and
>> go back to my old method of uploading everything manually.
>
> This is trivially fixable.
>
> calm already has a list of 'provides which don't exist (yet)', so I
> think I just need to add tl_2023 and tl_basic_2023 to that list
>
> Future work: make these regexes so we don't have same problem again in a
> years time.
Jon,
In preparation for TeX Live 2024, please add tl_2024 and tl_basic_2024
to the list of provides which don't exist yet (unless you've already
done the regex future work).
Thanks.
Ken
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Fwd: calm: cygwin package report for Ken Brown
2024-02-19 18:59 ` Ken Brown
@ 2024-02-19 19:22 ` Jon Turney
0 siblings, 0 replies; 10+ messages in thread
From: Jon Turney @ 2024-02-19 19:22 UTC (permalink / raw)
To: Ken Brown; +Cc: cygwin-apps
On 19/02/2024 18:59, Ken Brown via Cygwin-apps wrote:
> On 3/20/2023 7:17 PM, Jon Turney wrote:
>> On 20/03/2023 22:17, Ken Brown via Cygwin-apps wrote:
>>> It looks like my plan for having scallywag deploy all the TeX Live
>>> packages won't work (see below). calm would have to be more
>>> permissive and allow deploying a package that requires something that
>>> will be provided by a future package.
>>>
>>> In this case, I made asymptote require tl_2023, which will be
>>> provided by the next texlive release. But I don't want to deploy the
>>> latter until all the other packages for TeX Live 2023 have been
>>> deployed.
>>>
>>> Unless this is easy to fix, I'll just forget about using scallywag
>>> and go back to my old method of uploading everything manually.
>>
>> This is trivially fixable.
>>
>> calm already has a list of 'provides which don't exist (yet)', so I
>> think I just need to add tl_2023 and tl_basic_2023 to that list
>>
>> Future work: make these regexes so we don't have same problem again in
>> a years time.
>
> Jon,
>
> In preparation for TeX Live 2024, please add tl_2024 and tl_basic_2024
> to the list of provides which don't exist yet (unless you've already
> done the regex future work).
These are controlled by regex now, so these should already be permitted,
and I don't need to do anything (yay!):
'tl_\d+'
'tl_basic_\d+'
^ permalink raw reply [flat|nested] 10+ messages in thread