This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH cygport] Add a command to make a test release


> On 10/5/2017 10:23 AM, Andrew Schulman wrote:
> > Sometimes more complicated situations come up. We have one with lftp right now:
> > 
> > prev: 4.7.7-1
> > curr: 4.8.0-1
> > test: 4.7.8-1
> > 
> > This happened because 4.8.0-1 turns out to be broken, and later versions won't
> > build in Cygwin yet. So I had to promote 4.7.8-1 to test.
> 
> I didn't pay close attention to the lftp bug reports, so what I'm saying 
> may be nonsense.  But wouldn't it make more sense to just remove 4.8.0-1 
> if it's broken? 

Maybe. It was partly broken.

> You could still make 4.7.8-1 a test version, leaving a 
> working 4.7.7-1 as current.
> 
> Doing it this way, you wouldn't need anything but the ability to mark a 
> release as "test".

No, it also requires the ability to remove 4.8.0-1. To do that I have to
either ask for help here, or upload an override.hint file with

curr: 4.7.7-1
test: 4.7.8-1

or

prev: 4.7.7-1
curr: 4.7.8-1

So it'd be nice if cygport could do that for me.

Obviously this is an unusual case, but every now and then for one reason or
another I need to upload an override.hint file. Any time I do that, it'd be
nice if cygport handled the details for me.

Ooh, how about this:

  cygport lftp.cygport all
  cygport lftp.cygport override curr=4.7.7-1 test=4.7.8-1
  cygport lftp.cygport up

That would create override.hint and upload it with the package, leaving the
cygport file and source package alone.

Andrew


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]