Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

2023-07-05 Thread Dirk Eddelbuettel


Control: severity -1 normal

I am changing this back because

 a)  there is no general bug in R 4.3.1, and there newer was

 there were a few packages requiring an update to the new graphics engine
 version (as the packages choose to call R_GE_checkVersionOrDie, it is
 coming from their side, not the R package imposing/causing a break)

 filing bug reports against the affected package resolved the issue as
 expected, if you look at 
   https://qa.debian.org/excuses.php?package=r-base
 there is not a single graphics related issue

 but I can argue this issue til I am blue in the face and not get
 anywhere so the R package now provides r-graphics-engine-*

 b)  note that the remaining autopkgtest breaks have nothing to do with the
 graphics engine version, and the change I was asked to make (and which I
 accomodated) will not help

 however, the error is not with R just like the one you posted in your
 bug report was not:

Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires
the use of native symbols

 this is almost surely intra-package and needs to be resolved by those
 package

For both reasons the bug report should be closed but I am now only dialing it
down to 'normal'.  r-base is a bystander here, and the messenger that is
being shot at.

We of course do use R 4.3.* just fine with 21,000 r-cran-* binary packages in
r2u. If one keeps the package current with CRAN all is well.  It is not my
fault if some other maintainers claim they (and I paraphrase, but it is all
in the BTS) "have too many packages to keep them current".  That is an issue
for which filing bugs again r-base does not, and cannot, help.

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org



Processed: Re: Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

2023-07-05 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #1039721 [src:r-base] r-base: 4.3 causes many autopkgtests to fail
Severity set to 'normal' from 'serious'

-- 
1039721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

2023-06-29 Thread Dirk Eddelbuettel


On 28 June 2023 at 17:39, Jeremy Bícha wrote:
| Control: severity -1 serious
| 
| On Wed, Jun 28, 2023 at 5:29 PM Dirk Eddelbuettel  wrote:
| > Feel free to change the severity back if you truly think it is that serious.
| 
| Done.
| 
| Feel free to close the bug once r-base is ready to migrate to Testing.
| This is mostly just a tracking bug that people may find easier than
| browsing the mailing list.
| 
| > I maintain that r-base is fine.  I have no control over how other people use
| > my package, and if all other maintainers put breaking autopkgtests in well
| > yes then they do hold r-base hostage and it will take "forever" to migrate 
to
| > testing.  We have been there before.
| 
| Some just set this field in debian/control:
| Testsuite: autopkgtest-pkg-r

Of course. That is just the mechanical 'how does one'.

The actual problem is combining this with letting the packages get out of
sync, or in the case of the API change, not yet having rebuilt.

I just filed bug reports against (somewhat popular) packages r-cran-ragg (a
graphics device) and r-cran-svglite (ditto).  Once those are remade this
self-inflicted autopkgtest "issue" will improve.

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org



Processed: Re: Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

2023-06-28 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #1039721 [src:r-base] r-base: 4.3 causes many autopkgtests to fail
Severity set to 'serious' from 'normal'

-- 
1039721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

2023-06-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1039721 normal
Bug #1039721 [src:r-base] r-base: 4.3 causes many autopkgtests to fail
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1039721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

2023-06-28 Thread Dirk Eddelbuettel


severity 1039721 normal
thanks

Hi Jeremy,

That is a false positive (more below) and a duplicate of #1039510; the
discussion of the latter now continues on the debian-r list.

On 28 June 2023 at 12:31, Jeremy Bícha wrote:
| Source: r-base
| Version: 4.3.1-1
| Severity: serious
| 
| I'm copying this from https://launchpad.net/bugs/2020799
| 
| ==
| A bunch of R packages fail autopkgtests with 4.3.0-1, with errors
| looking like this:
| 
| Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires
| the use of native symbols
| 
| Looking into the upstream code and changelog, this appears to be
| related to this change:
| 
| Attempting to use a character string naming a foreign function entry
| point in a foreign function call in a package will now signal an error
| if the packages has called R_forceSymbols to specify that symbols must
| be used.
| ==

This shoots the messenger. That is a bug in the vectors package, not in R
4.3.0 (or now R 4.3.1).

I would be happy to schedule a quick chat (I am on Central time) but I
already wrote a number of email messages on this, now mostly under the above
bug number or on the debian-r list (off the usual Debian mailing list server).

FWIW I also look after https://eddelbuettel.github.io/r2u/ which *all* of
CRAN (and a few hundred BioConductor packages) as complete .deb binaries with
full dependencies for Ubuntu 20.04 (focal) and 22.04 (jammy). There are no
bugs, and there is no API issue.  r2u is mesmerizing; just play with the
rocker/r2u:22.04 container.

The combination of a number of maintainer a) adding autopkgtest and at the
same time b) letting some packages go stale creates this.  It happens at each
release, and it manifestly unfair to package r-base which I have been
maintaining for 20+ years.

Cheers, Dirk
(Debian dev since 1995 or so
 R maintainer since 1998-2002 dependeing on how you count
 R Foundation Board member for a decade+
 Author of 60+ CRAN packages)

| 
| Thank you,
| Jeremy Bícha

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org



Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

2023-06-28 Thread Jeremy Bícha
Source: r-base
Version: 4.3.1-1
Severity: serious

I'm copying this from https://launchpad.net/bugs/2020799

==
A bunch of R packages fail autopkgtests with 4.3.0-1, with errors
looking like this:

Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires
the use of native symbols

Looking into the upstream code and changelog, this appears to be
related to this change:

Attempting to use a character string naming a foreign function entry
point in a foreign function call in a package will now signal an error
if the packages has called R_forceSymbols to specify that symbols must
be used.
==

Thank you,
Jeremy Bícha