Re: Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-11-20 Thread Dirk Eddelbuettel 

On 12 October 2017 at 16:31, Dirk Eddelbuettel wrote:
| 
| On 12 October 2017 at 22:32, Johannes Ranke wrote:
| | Am Donnerstag, 12. Oktober 2017, 12:01:14 CEST schrieb Dirk Eddelbuettel:
| | 
| | > So we did this 71 times, but stopped 4+ years ago.  Not sure what got the
| | > toolchain coughing, but I guess we could try again.
| | 
| | texi2dvi used to trip over ~ in path names, so for locally building 
backports 
| | we used to rename the directory that the source was extracted to, 
substituting 
| | "~" by "-" before building. But I don't know if that was the reason for 
Dirk 
| | to change the scheme.
| | 
| | It seems that this was fixed in texi2dvi upstream
| | 
| |   http://svn.savannah.gnu.org/viewvc/texinfo/trunk/util/texi2dvi?
| | r1=7199=7200
| 
| It definitely was involved as "guilty party" once, then got fixed upstream --
| and it may have regressed.
| 
| Worth trying again though.

I just did, and got two failures with the 'making pdf files' part. Likely bug
in texlive or texinfo -- and possible regression.  It really seems to hate a
build directory with a ~ in it.  So 3.4.2.20171120 for the upcoming 3.4.3.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Johannes Ranke 
Am Donnerstag, 12. Oktober 2017, 12:01:14 CEST schrieb Dirk Eddelbuettel:

> So we did this 71 times, but stopped 4+ years ago.  Not sure what got the
> toolchain coughing, but I guess we could try again.

texi2dvi used to trip over ~ in path names, so for locally building backports 
we used to rename the directory that the source was extracted to, substituting 
"~" by "-" before building. But I don't know if that was the reason for Dirk 
to change the scheme.

It seems that this was fixed in texi2dvi upstream

  http://svn.savannah.gnu.org/viewvc/texinfo/trunk/util/texi2dvi?
r1=7199=7200

Johannes

Re: Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Graham Inggs 
On 12 October 2017 at 19:01, Dirk Eddelbuettel  wrote:
> So we did this 71 times, but stopped 4+ years ago.  Not sure what got the
> toolchain coughing, but I guess we could try again.

That would be great, thanks!

Re: Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Dirk Eddelbuettel 

On 12 October 2017 at 17:45, Graham Inggs wrote:
| Hi Dirk
| 
| On 12/10/2017 16:37, Dirk Eddelbuettel wrote:
| > And yes, the hint re 3.5 being shaky leads itself to uploading to 
experimental.
| 
| Would you please consider versioning such uploads as 3.5~something 
| instead of 3.4.something?
| 
| e.g. your second-to-last upload of r-base was 3.4.1.20170921-1
| I think it would have been clearer if it were versioned 3.4.2~20170921-1 
| or even 3.4.2~rc1-1
| 
| This also allows for things like Depends: r-base-core (>= 3.4.2~) should 
| they ever be needed.

Could do, I think, and once did. Grep'ing debian/changelog:

edd@bud:~$ grep "^r-base.*\~" src/debian/R/R-3.4.2/debian/changelog | wc -l
71
edd@bud:~$ grep "^r-base.*\~" src/debian/R/R-3.4.2/debian/changelog | head
r-base (3.0.1~20130512-1) unstable; urgency=low
r-base (3.0.0~20130330-1) unstable; urgency=low
r-base (3.0.0~20130327-1) unstable; urgency=low
r-base (3.0.0~20130324-1) unstable; urgency=low
r-base (2.15.3~20130327-1) unstable; urgency=low
r-base (2.15.3~20130326-1) unstable; urgency=low
r-base (2.15.3~20130324-1) unstable; urgency=low
r-base (2.15.1~20120617-1) unstable; urgency=low
r-base (2.15.0~20120323-1) unstable; urgency=low
r-base (2.15.0~20120317-1) unstable; urgency=low
edd@bud:~$

So we did this 71 times, but stopped 4+ years ago.  Not sure what got the
toolchain coughing, but I guess we could try again.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Graham Inggs 

Hi Dirk

On 12/10/2017 16:37, Dirk Eddelbuettel wrote:

And yes, the hint re 3.5 being shaky leads itself to uploading to experimental.


Would you please consider versioning such uploads as 3.5~something 
instead of 3.4.something?


e.g. your second-to-last upload of r-base was 3.4.1.20170921-1
I think it would have been clearer if it were versioned 3.4.2~20170921-1 
or even 3.4.2~rc1-1


This also allows for things like Depends: r-base-core (>= 3.4.2~) should 
they ever be needed.


Regards
Graham

Re: Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Dirk Eddelbuettel 

On 12 October 2017 at 16:18, Sébastien Villemot wrote:
| On Thu, Oct 12, 2017 at 09:13:54AM -0500, Dirk Eddelbuettel wrote:
| > 
| > On 12 October 2017 at 15:58, Sébastien Villemot wrote:
| > | Thanks Charles for explaining this.
| > | 
| > | Actually the migration has already happened, thanks to the Release Team 
that
| > | took appropriate action to mitigate the impact of the most recent uploads.
| > | 
| > | This will soon be reflected in the tracker and various web pages.
| > | 
| > | R-related uploads can therefore be resumed.
| > 
| > Nice.
| > 
| > Was there a way to read that off the (otherwise very impressive and helpful)
| > tracker status page?  Or was is somewhere else?
| 
| For the moment you can only see it on the main archive database:
| 
| $ rmadison r-base
| r-base | 2.15.1-4   | oldoldstable   | source, all
| r-base | 3.1.1-1| oldstable-kfreebsd | source, all
| r-base | 3.1.1-1+deb8u1 | oldstable  | source, all
| r-base | 3.3.3-1~bpo8+1 | jessie-backports   | source, all
| r-base | 3.3.3-1| stable | source, all
| r-base | 3.4.2-1| testing| source, all
| r-base | 3.4.2-1| unstable   | source, all
| 
| > This was a good dry run.  Come R 3.5.0 next April we actually MUST rebuild
| > all packages rather than just doing it because we can.  I'll circle back
| > closer to the date, the r-devel branch upstream is still a little shaky.
| 
| Ok, looking forward to it.
| 
| When it is ready, please follow the transition guidelines which are summarized
| there:
| 
|   https://wiki.debian.org/Teams/ReleaseTeam/Transitions
| 
| The short version of it is: please open a transition bug and wait for an ack
| from the Release Team *before* uploading R 3.5 to unstable (but of course you
| are free to upload to experimental sooner).

Rest assurred I will definitely circle back with you and Charles :-)   Debian
work can still be a pleasure when you get some work done with clueful people.

And yes, the hint re 3.5 being shaky leads itself to uploading to experimental.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Sébastien Villemot 
On Thu, Oct 12, 2017 at 09:13:54AM -0500, Dirk Eddelbuettel wrote:
> 
> On 12 October 2017 at 15:58, Sébastien Villemot wrote:
> | Thanks Charles for explaining this.
> | 
> | Actually the migration has already happened, thanks to the Release Team that
> | took appropriate action to mitigate the impact of the most recent uploads.
> | 
> | This will soon be reflected in the tracker and various web pages.
> | 
> | R-related uploads can therefore be resumed.
> 
> Nice.
> 
> Was there a way to read that off the (otherwise very impressive and helpful)
> tracker status page?  Or was is somewhere else?

For the moment you can only see it on the main archive database:

$ rmadison r-base
r-base | 2.15.1-4   | oldoldstable   | source, all
r-base | 3.1.1-1| oldstable-kfreebsd | source, all
r-base | 3.1.1-1+deb8u1 | oldstable  | source, all
r-base | 3.3.3-1~bpo8+1 | jessie-backports   | source, all
r-base | 3.3.3-1| stable | source, all
r-base | 3.4.2-1| testing| source, all
r-base | 3.4.2-1| unstable   | source, all

> This was a good dry run.  Come R 3.5.0 next April we actually MUST rebuild
> all packages rather than just doing it because we can.  I'll circle back
> closer to the date, the r-devel branch upstream is still a little shaky.

Ok, looking forward to it.

When it is ready, please follow the transition guidelines which are summarized
there:

  https://wiki.debian.org/Teams/ReleaseTeam/Transitions

The short version of it is: please open a transition bug and wait for an ack
from the Release Team *before* uploading R 3.5 to unstable (but of course you
are free to upload to experimental sooner).

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Re: Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Dirk Eddelbuettel 

On 12 October 2017 at 15:58, Sébastien Villemot wrote:
| Thanks Charles for explaining this.
| 
| Actually the migration has already happened, thanks to the Release Team that
| took appropriate action to mitigate the impact of the most recent uploads.
| 
| This will soon be reflected in the tracker and various web pages.
| 
| R-related uploads can therefore be resumed.

Nice.

Was there a way to read that off the (otherwise very impressive and helpful)
tracker status page?  Or was is somewhere else?

This was a good dry run.  Come R 3.5.0 next April we actually MUST rebuild
all packages rather than just doing it because we can.  I'll circle back
closer to the date, the r-devel branch upstream is still a little shaky.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Re: Bug#868558: Would you please not upload new r-* packages until transition is finalised (Re: r-api-3.4)

2017-10-12 Thread Sébastien Villemot 
On Thu, Oct 12, 2017 at 10:40:00PM +0900, Charles Plessy wrote:

> the point is that r-base and all the other packages will only migrate to
> testing when all of them will be ready at the same time.  Packages need
> 5 days to migrate to Testing and each upload resets the counter, thus
> blocking the migration of all.  Therefore, a break of 5 days without
> uploads is needed if we want to see the r-* packages in Testing.

Thanks Charles for explaining this.

Actually the migration has already happened, thanks to the Release Team that
took appropriate action to mitigate the impact of the most recent uploads.

This will soon be reflected in the tracker and various web pages.

R-related uploads can therefore be resumed.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature