On 2015-07-27 21:45, Achim Gratz wrote:
|
| The update to Perl 5.22 is planned for the end of this week. Please
| notify immediately if you cannot provide the updated packages indicated
| below by then to your package upload area on cygwin.com.
|
| Your following packages place Perl modules into
With the latest round of changes I'm now down to two local change-sets
for setup:
1. Implement an option that installs exactly the requested packages, no
matter what packages are already installed. This leaves an installation
in the same state as a new install from scratch would have, modulo any
Andrew Schulman writes:
>> The idea was that you install the pre-release Perl that was published
>> specifically to facilitate this rebuild.
>
> Sorry, where is that? I looked in setup, and the newest test version there
> is 5.14.4-3.
>From the thread on the Perl update:
--8<---cut h
> > But okay, I'll rebuild it. So are you asking me to first wait until Perl
> > 5.22
> > comes out, then rebuild the package and release it afterwards? Or to
> > manually
> > change where the files go, and release the update at the same time as Perl
> > 5.22?
>
> The idea was that you instal
On 7/28/2015 12:40 PM, Corinna Vinschen wrote:
On Jul 28 12:36, Ken Brown wrote:
On 7/28/2015 12:23 PM, Eric Blake wrote:
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware access
David Rothenberger writes:
> I've already built and uploaded new subversion packages. I will rebuild
> net-snmp by Sunday at the latest. I can easily put a !perl file in the
> top-level release directories if that's the decision. I will ensure that
> there are no other packages in the release areas
Achim Gratz wrote:
> That would give two more days for maintainers to upload, which would be
> OK. The only difference would be that every maintainer needs to ensure
> that posting the cookies in the top-level release directories is OK. At
> the moment we're stuck anyway as long as David and Yaak
On Jul 28 12:36, Ken Brown wrote:
> On 7/28/2015 12:23 PM, Eric Blake wrote:
> >On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
> One more thing that we'll have to solve one way or the other. I still
> hope that one maintainer with full sourceware access will be able to
> post the !rea
On Jul 28 10:23, Eric Blake wrote:
> On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
> >>> One more thing that we'll have to solve one way or the other. I still
> >>> hope that one maintainer with full sourceware access will be able to
> >>> post the !ready cookies all at the same time.
> >>
> >>
On Jul 28 18:17, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Or Eric. I'm not sure how this !perl thingy is supposed to work since
> > the tags are handled by upset...
>
> The idea was that when every maintainer has said he's ready, someone
> goes into the server just after the updater has
On 7/28/2015 12:23 PM, Eric Blake wrote:
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware access will be able to
post the !ready cookies all at the same time.
Corinna or Yaakov,
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
>>> One more thing that we'll have to solve one way or the other. I still
>>> hope that one maintainer with full sourceware access will be able to
>>> post the !ready cookies all at the same time.
>>
>> Corinna or Yaakov, that I am aware.
>
> Or Eri
Corinna Vinschen writes:
> Or Eric. I'm not sure how this !perl thingy is supposed to work since
> the tags are handled by upset...
The idea was that when every maintainer has said he's ready, someone
goes into the server just after the updater has run and moves all !perl
to !ready, so that an ho
> > I mean, seriously, this seems like a lot of dumb work to me.
>
> Sorry.
OK. Again, not your fault and thanks for maintaining. Andrew
On Jul 28 08:40, Marco Atzeri wrote:
> On 7/28/2015 7:43 AM, Achim Gratz wrote:
> >Adam Dinwoodie writes:
> >>Is there a consensus on the way to upload files ready for Perl 5.22 to
> >>be made available? The Git packages are ready to go, but I'm not sure
> >>if I should be uploading them without a
On 7/27/2015 9:46 PM, Achim Gratz wrote:
The update to Perl 5.22 is planned for the end of this week. Please
notify immediately if you cannot provide the updated packages indicated
below by then to your package upload area on cygwin.com.
Your following packages place Perl modules into vendor_p
16 matches
Mail list logo
