Retiring setup.hint

Retiring setup.hint

[Jon Turney]

I propose that calm will stop accepting uploads containing setup.hint 
some time shortly after 2017-11-18.

This is approximately one year after the cygport release [1] which, 
stopped generating these files, so if you're using cygport >= 0.23.0, no 
action is needed.

Warnings that you need to upgrade cygport have been generated for more 
than 6 months [2].

After setup.hint uploads are disabled, any remaining setup.hint in the 
cygwin release on sourceware.org will be migrated to pvr.hint(s), as per 
[3].

[1] https://cygwin.com/ml/cygwin-announce/2016-11/msg00078.html
[2] https://cygwin.com/ml/cygwin-apps/2017-04/msg00024.html
[3] https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html

Re: Retiring setup.hint

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

On Oct 25 20:42, Jon Turney wrote:
> 
> I propose that calm will stop accepting uploads containing setup.hint some
> time shortly after 2017-11-18.
> 
> This is approximately one year after the cygport release [1] which, stopped
> generating these files, so if you're using cygport >= 0.23.0, no action is
> needed.
> 
> Warnings that you need to upgrade cygport have been generated for more than
> 6 months [2].
> 
> After setup.hint uploads are disabled, any remaining setup.hint in the
> cygwin release on sourceware.org will be migrated to pvr.hint(s), as per
> [3].
> 
> [1] https://cygwin.com/ml/cygwin-announce/2016-11/msg00078.html
> [2] https://cygwin.com/ml/cygwin-apps/2017-04/msg00024.html
> [3] https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html

I'm still generating setup.hint files for the Cygwin package itself.

Please have a look into cygwin's cygport file.  Do we have an *easy*
replacement for creating test releases from cygport in the meantime?

Ideally I can simply call cygport with a --test parameter or some such
to create a test release.

As long as we don't have that, I'm inclined to veto the idea to drop
setup.hint.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Retiring setup.hint

[Jon Turney]

On 25/10/2017 21:23, Corinna Vinschen wrote:
> On Oct 25 20:42, Jon Turney wrote:
>>
>> I propose that calm will stop accepting uploads containing setup.hint some
>> time shortly after 2017-11-18.
>>
>> This is approximately one year after the cygport release [1] which, stopped
>> generating these files, so if you're using cygport >= 0.23.0, no action is
>> needed.
>>
>> Warnings that you need to upgrade cygport have been generated for more than
>> 6 months [2].
>>
>> After setup.hint uploads are disabled, any remaining setup.hint in the
>> cygwin release on sourceware.org will be migrated to pvr.hint(s), as per
>> [3].
>>
>> [1] https://cygwin.com/ml/cygwin-announce/2016-11/msg00078.html
>> [2] https://cygwin.com/ml/cygwin-apps/2017-04/msg00024.html
>> [3] https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html
> 
> I'm still generating setup.hint files for the Cygwin package itself.
> 
> Please have a look into cygwin's cygport file.  Do we have an *easy*
> replacement for creating test releases from cygport in the meantime?
> 
> Ideally I can simply call cygport with a --test parameter or some such
> to create a test release.

See https://cygwin.com/ml/cygwin-apps/2017-10/msg00017.html which 
contains my patch to do this, and an offer to implement this in whatever 
way is acceptable to Yaakov.

> As long as we don't have that, I'm inclined to veto the idea to drop
> setup.hint.

Re: Retiring setup.hint

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]

On Oct 25 21:46, Jon Turney wrote:
> On 25/10/2017 21:23, Corinna Vinschen wrote:
> > On Oct 25 20:42, Jon Turney wrote:
> > > 
> > > I propose that calm will stop accepting uploads containing setup.hint some
> > > time shortly after 2017-11-18.
> > > 
> > > This is approximately one year after the cygport release [1] which, stopped
> > > generating these files, so if you're using cygport >= 0.23.0, no action is
> > > needed.
> > > 
> > > Warnings that you need to upgrade cygport have been generated for more than
> > > 6 months [2].
> > > 
> > > After setup.hint uploads are disabled, any remaining setup.hint in the
> > > cygwin release on sourceware.org will be migrated to pvr.hint(s), as per
> > > [3].
> > > 
> > > [1] https://cygwin.com/ml/cygwin-announce/2016-11/msg00078.html
> > > [2] https://cygwin.com/ml/cygwin-apps/2017-04/msg00024.html
> > > [3] https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html
> > 
> > I'm still generating setup.hint files for the Cygwin package itself.
> > 
> > Please have a look into cygwin's cygport file.  Do we have an *easy*
> > replacement for creating test releases from cygport in the meantime?
> > 
> > Ideally I can simply call cygport with a --test parameter or some such
> > to create a test release.
> 
> See https://cygwin.com/ml/cygwin-apps/2017-10/msg00017.html which contains
> my patch to do this, and an offer to implement this in whatever way is
> acceptable to Yaakov.

Looks good to me.

> > As long as we don't have that, I'm inclined to veto the idea to drop
> > setup.hint.

Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Retiring setup.hint

[Achim Gratz]

Corinna Vinschen writes:
> Please have a look into cygwin's cygport file.  Do we have an *easy*
> replacement for creating test releases from cygport in the meantime?

The current version of my patch:
http://repo.or.cz/cygport/rpm-style.git/patch/246a46e3e23f44ac6abc58d36d9b78bbd502dd3e

> Ideally I can simply call cygport with a --test parameter or some such
> to create a test release.

I've opted for a proper command rather than an option due to the way the
options are processed, so:

$ cygport $p pkg-test

The packaging step will have output to remind you if you're packaging
"current" or "test".


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: Retiring setup.hint

[Jon Turney]

On 25/10/2017 22:18, Corinna Vinschen wrote:
> On Oct 25 21:46, Jon Turney wrote:
>> On 25/10/2017 21:23, Corinna Vinschen wrote:
>>> On Oct 25 20:42, Jon Turney wrote:
>>>>
>>>> I propose that calm will stop accepting uploads containing setup.hint some
>>>> time shortly after 2017-11-18.

Better plan: when uploaded, calm will rename a setup.hint file to pvr.hint.

(If the appropriate pvr cannot be determined (from the name of tar files 
in the same directory), or the setup.hint contains lines which aren't 
valid in a pvr.hint, the upload will fail)

I deployed an update to calm today which does this.

(It also has some preliminary support for depends:, obsoletes:, 
build-depends: hints, along with some cosmetic fixes)

>>>> This is approximately one year after the cygport release [1] which, stopped
>>>> generating these files, so if you're using cygport >= 0.23.0, no action is
>>>> needed.
>>>>
>>>> Warnings that you need to upgrade cygport have been generated for more than
>>>> 6 months [2].
>>>>
>>>> After setup.hint uploads are disabled, any remaining setup.hint in the
>>>> cygwin release on sourceware.org will be migrated to pvr.hint(s), as per
>>>> [3].
>>>>
>>>> [1] https://cygwin.com/ml/cygwin-announce/2016-11/msg00078.html
>>>> [2] https://cygwin.com/ml/cygwin-apps/2017-04/msg00024.html
>>>> [3] https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html
>>>
>>> I'm still generating setup.hint files for the Cygwin package itself.
>>>
>>> Please have a look into cygwin's cygport file.  Do we have an *easy*
>>> replacement for creating test releases from cygport in the meantime?
>>>
>>> Ideally I can simply call cygport with a --test parameter or some such
>>> to create a test release.
>>
>> See https://cygwin.com/ml/cygwin-apps/2017-10/msg00017.html which contains
>> my patch to do this, and an offer to implement this in whatever way is
>> acceptable to Yaakov.
> 
> Looks good to me.

I'll hold off on doing anything further until we've had some successes 
with the cygwin package to show this is working to your satisfaction.

(I haven't yet started on writing a tool to do the migration, in any case)

Re: Retiring setup.hint

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2504 bytes --]

On Nov 13 11:39, Jon Turney wrote:
> On 25/10/2017 22:18, Corinna Vinschen wrote:
> > On Oct 25 21:46, Jon Turney wrote:
> > > On 25/10/2017 21:23, Corinna Vinschen wrote:
> > > > On Oct 25 20:42, Jon Turney wrote:
> > > > > 
> > > > > I propose that calm will stop accepting uploads containing setup.hint some
> > > > > time shortly after 2017-11-18.
> 
> Better plan: when uploaded, calm will rename a setup.hint file to pvr.hint.
> 
> (If the appropriate pvr cannot be determined (from the name of tar files in
> the same directory), or the setup.hint contains lines which aren't valid in
> a pvr.hint, the upload will fail)
> 
> I deployed an update to calm today which does this.
> 
> (It also has some preliminary support for depends:, obsoletes:,
> build-depends: hints, along with some cosmetic fixes)
> 
> > > > > This is approximately one year after the cygport release [1] which, stopped
> > > > > generating these files, so if you're using cygport >= 0.23.0, no action is
> > > > > needed.
> > > > > 
> > > > > Warnings that you need to upgrade cygport have been generated for more than
> > > > > 6 months [2].
> > > > > 
> > > > > After setup.hint uploads are disabled, any remaining setup.hint in the
> > > > > cygwin release on sourceware.org will be migrated to pvr.hint(s), as per
> > > > > [3].
> > > > > 
> > > > > [1] https://cygwin.com/ml/cygwin-announce/2016-11/msg00078.html
> > > > > [2] https://cygwin.com/ml/cygwin-apps/2017-04/msg00024.html
> > > > > [3] https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html
> > > > 
> > > > I'm still generating setup.hint files for the Cygwin package itself.
> > > > 
> > > > Please have a look into cygwin's cygport file.  Do we have an *easy*
> > > > replacement for creating test releases from cygport in the meantime?
> > > > 
> > > > Ideally I can simply call cygport with a --test parameter or some such
> > > > to create a test release.
> > > 
> > > See https://cygwin.com/ml/cygwin-apps/2017-10/msg00017.html which contains
> > > my patch to do this, and an offer to implement this in whatever way is
> > > acceptable to Yaakov.
> > 
> > Looks good to me.
> 
> I'll hold off on doing anything further until we've had some successes with
> the cygwin package to show this is working to your satisfaction.

Thanks!


Corinna


-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Retiring setup.hint

[Thomas Wolff]

Am 25.10.2017 um 21:42 schrieb Jon Turney:
>
> I propose that calm will stop accepting uploads containing setup.hint 
> some time shortly after 2017-11-18.
>
> This is approximately one year after the cygport release [1] which, 
> stopped generating these files, so if you're using cygport >= 0.23.0, 
> no action is needed.
>
> Warnings that you need to upgrade cygport have been generated for more 
> than 6 months [2].
>
> After setup.hint uploads are disabled, any remaining setup.hint in the 
> cygwin release on sourceware.org will be migrated to pvr.hint(s), as 
> per [3].
>
> [1] https://cygwin.com/ml/cygwin-announce/2016-11/msg00078.html
> [2] https://cygwin.com/ml/cygwin-apps/2017-04/msg00024.html
> [3] https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html
I would appreciate to see some explanation about this. Why the change 
and what are package maintainers expected to do?
If calm can simply "rename setup.hint to pvr.hint", what's the purpose 
of all this?
Thomas

Re: Retiring setup.hint

[Achim Gratz]

Thomas Wolff writes:
> If calm can simply "rename setup.hint to pvr.hint", what's the purpose
> of all this?

One of the purposes is that dependencies can and do change over time and
eventually we will want to have separate dependencies for each released
package like everybody else does.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: Retiring setup.hint

[Jon Turney]

On 13/11/2017 19:59, Thomas Wolff wrote:
> Am 25.10.2017 um 21:42 schrieb Jon Turney:
>> I propose that calm will stop accepting uploads containing setup.hint 
>> some time shortly after 2017-11-18.

So, firstly this plan has been superseded...

>> This is approximately one year after the cygport release [1] which, 
>> stopped generating these files, so if you're using cygport >= 0.23.0, 
>> no action is needed.
>>
>> Warnings that you need to upgrade cygport have been generated for more 
>> than 6 months [2].
>>
>> After setup.hint uploads are disabled, any remaining setup.hint in the 
>> cygwin release on sourceware.org will be migrated to pvr.hint(s), as 
>> per [3].
>>
>> [1] https://cygwin.com/ml/cygwin-announce/2016-11/msg00078.html
>> [2] https://cygwin.com/ml/cygwin-apps/2017-04/msg00024.html
>> [3] https://cygwin.com/ml/cygwin-apps/2016-09/msg00025.html
> I would appreciate to see some explanation about this. Why the change 
> and what are package maintainers expected to do?

... so, you don't have to do anything.

I hope that the:"WARNING: '/sourceware/cygwin-staging/home/Thomas 
Wolff/x86_64/release/mintty/setup.hint' seen, please update to cygport 
 >= 0.23.0" in the mails you received from calm appropriately indicates 
the expectation that I'd like you to update the version of cygport you 
are using, when convenient for you.

> If calm can simply "rename setup.hint to pvr.hint", what's the purpose 
> of all this?

I like to think what I wrote was a bit more nuanced than that.

>> "If the appropriate pvr cannot be determined [...], the upload will fail"

In the (common) case where a setup.hint and package archives for a 
single version are uploaded, renaming is possible.

But there are less common, but permitted scenarios where this is not 
possible, e.g.:

- If you decide to upload e.g. 2.9.0-1 and test version 3.0.0-1 at the 
same time.  Not recording the dependencies for these versions separately 
fundamentally does not work (see [1])

- Uploading just a replacement setup.hint for an existing version is no 
longer permitted under these rules (but you can still upload a 
replacement pvr.hint for a specific version)

It would have been nice if it had occurred to me that I could do this 
renaming trick a bit earlier, though...

[1] https://cygwin.com/ml/cygwin-apps/2016-06/msg00069.html