bug#31210: Perl graft breakage

My suggested approach of making compatibility symlinks didn't work. See for details and further discussion. Mark

bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error

I've now pushed another commit b5178b325409b1eaf953f8f3007a180cbd27b167 to master, which changes the replacement perl to think it is version 5.26.1, although it's actually version 5.26.2. With this fix, I'm now able to build guix without 'po4a' reporting errors. Please try it out and let me know

bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error

Unfortunately, the compatibility symlinks are not sufficient. The problem is that other perl packages such a po4a are installing their modules into $out/lib/perl5/site_perl/5.26.1, which conflicts with the compatibility symlink that we're installing in perl. When perl and po4a are put together

bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error

I just pushed commit 5618193694b08855488b29fae1db42f05ca6deaf to 'master', which I hope will fix the remaining problems with our grafted perl. Can you verify and let us know? Mark

bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error

Hi, Julien Lepiller writes: > Le Thu, 19 Apr 2018 10:39:10 -0400, > Leo Famulari a écrit : > >> I believe this is fixed by commit >> 44b98b00026e62766620dbc4330a305282d61069. >> >> Can you try again and let me know? > > Hi, I don't think this is fully

bug#31113: mcron ERROR: In procedure mktime:

Hi Ludovic, l...@gnu.org (Ludovic Courtès) writes: > Hello, > > Rutger Helling skribis: > >> I had this problem too. >> >> Reverting commit cfbf6de18cc70d2e385feb5f61f9363f18e78ddf (gnu: mcron: >> Update to 1.1 and deprecate "mcron2".) fixed it for me. > > This was a bug

bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error

On Fri, Apr 20, 2018 at 07:46:45PM -0400, Leo Famulari wrote: > On Fri, Apr 20, 2018 at 02:41:52PM +0200, Julien Lepiller wrote: > > Hi, I don't think this is fully fixed. On current master, trying to run > > po4a (a perl application that guix now depends on to generate the > > translation of the

bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error

On Fri, Apr 20, 2018 at 02:41:52PM +0200, Julien Lepiller wrote: > Hi, I don't think this is fully fixed. On current master, trying to run > po4a (a perl application that guix now depends on to generate the > translation of the manual), I get the following: > > [env]$ po4a-updatepo > Can't locate

bug#31085: Unexpected behaviour when running `guix build lilypond'

Hello l...@gnu.org (Ludovic Courtès) writes: > Hello, > > Diego Nicola Barbato skribis: > >> I have experienced some unexpected behaviour when running `guix build >> lilypond': >> After verifying that there was a substitute available with `guix weather >> -m m.scm' (Where

bug#31227: emacs-lispy is broken

Hi, emacs-lispy is broken (void-variable hydra-lispy-x on load) since commit b5904fcc34596e0aabb85020808b746e4c8b39a0. Clément

bug#31216: commit 217b8c2e0 produces 'Can't locate Date/Parse.pm in @INC Error' perl error

Le Thu, 19 Apr 2018 10:39:10 -0400, Leo Famulari a écrit : > On Wed, Apr 18, 2018 at 11:14:40PM -0400, George myglc2 Clemmer wrote: > > Commit ... > > > > 217b8c2e0 * gnu: perl: Replace with 5.26.2 [fixes > > CVE-2018-{6797,6798,6913}]. > > > > ... caused the attached perl