bug#27563: [PATCH v3 2/2] gnu: ghostscript: Write document ID only when encrypting.

On Fri, Jul 07, 2017 at 03:21:49PM +0200, Danny Milosavljevic wrote: > Yeah, at the upstream bug link > we discussed > that (somewhat). While they don't want to carry the patches (because > they don't want to lose functionality) they explained

bug#27563: [PATCH v3 0/2] Make ghostscript reproducible.

On Fri, 07 Jul 2017 17:18:15 +0200 l...@gnu.org (Ludovic Courtès) wrote: > OK, makes sense. Maybe we can still have it disabled (or enabled) by > environment variable Sure. Any suggestions for the name of the environment variable? Also, where would we set it so the build processes of all the

bug#27563: [PATCH v3 2/2] gnu: ghostscript: Write document ID only when encrypting.

Danny Milosavljevic skribis: > I'd vote for an environment variable to disable UUID printing and also > Time header printing. That way it would do everything normally in > regular usage - but when used in packages, it would just not *print* > the problematic stuff. No

bug#27563: [PATCH v3 0/2] Make ghostscript reproducible.

Danny Milosavljevic skribis: > On Fri, 07 Jul 2017 17:18:15 +0200 > l...@gnu.org (Ludovic Courtès) wrote: > >> OK, makes sense. Maybe we can still have it disabled (or enabled) by >> environment variable > > Sure. Any suggestions for the name of the environment

bug#27605: Lightweight desktop example fails to build with kernel panic

Leo Famulari skribis: > On Fri, Jul 07, 2017 at 05:16:54PM +0200, Ludovic Courtès wrote: >> > Actually, false alarm! After increasing the image size to 20 GiB, I >> > missed the messages about being out of space. Sorry for the noise! >> >> So the problem is that the estimate

bug#27563: [PATCH v3 0/2] Make ghostscript reproducible.

> . Hmm... can you access the patch linked there (under "Solution") ?

bug#27563: [PATCH v3 2/2] gnu: ghostscript: Write document ID only when encrypting.

On Fri, Jul 07, 2017 at 06:42:25PM +0200, Danny Milosavljevic wrote: > Leo Famulari wrote: > > > That leaves the document UUID - and upstream, in some of the other > > I think the lowest risk is to do nothing to Ghostscript and move the PDF > > documentation to a separate

bug#27563: [PATCH v3 2/2] gnu: ghostscript: Write document ID only when encrypting.

Hi Leo, On Fri, 7 Jul 2017 12:21:51 -0400 Leo Famulari wrote: > > That leaves the document UUID - and upstream, in some of the other > I think the lowest risk is to do nothing to Ghostscript and move the PDF > documentation to a separate 'doc' output. Then, we could have >

bug#27611: Virtual machine documentation

The documentation about using GuixSD in a virtual machine has grown organically in response to user questions and complaints, and I think it's become sort of confusing for beginners. All the relevant information is in the manual, and it's easy for experienced Guix users to find what they need.

bug#27605: Lightweight desktop example fails to build with kernel panic

On Fri, Jul 07, 2017 at 05:16:54PM +0200, Ludovic Courtès wrote: > > Actually, false alarm! After increasing the image size to 20 GiB, I > > missed the messages about being out of space. Sorry for the noise! > > So the problem is that the estimate was too small, right? No, the problem was that I

bug#27563: [PATCH v3 0/2] Make ghostscript reproducible.

On Fri, 07 Jul 2017 19:51:10 +0200 l...@gnu.org (Ludovic Courtès) wrote: > For CreationDate/ModDate, I think it should honor SOURCE_DATE_EPOCH as > in >

bug#27563: [PATCH v3 0/2] Make ghostscript reproducible.

Danny Milosavljevic skribis: >> . > > Hmm... can you access the patch linked there (under "Solution") ? It’s 404, but Leo sent a link to the patch on debian.org. Ludo’.

bug#27386: offloading documentation and env

Oleg Pykhalov skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Hmm could it be that ‘machine-load’ in (guix scripts offload) always >> returns +inf.0, for instance because it fails to run “cat /proc/loadavg” >> on the remote machine? (If it succeeded we would see the

bug#27563: [PATCH v3 2/2] gnu: ghostscript: Write document ID only when encrypting.

Hi Ludo, On Fri, 07 Jul 2017 14:02:04 +0200 l...@gnu.org (Ludovic Courtès) wrote: > Also, do you know whether the PDF specs are OK with that? Yeah, at the upstream bug link we discussed that (somewhat). While they don't want to carry

bug#27605: Lightweight desktop example fails to build with kernel panic

On Fri, Jul 07, 2017 at 08:53:37AM -0400, Leo Famulari wrote: > On Fri, Jul 07, 2017 at 02:23:05PM +0200, Ludovic Courtès wrote: > > Did you pass --image-size? If not, it could be that the image size > > estimate is slightly too small (see commit > > a8ac4f081a9a679498ea42ccfe001f218bba3043). > >

bug#27605: Lightweight desktop example fails to build with kernel panic

Hi Leo, Leo Famulari skribis: > [...] > registering closures... > populating... > creating FAT partition... > mkfs.fat 4.1 (2017-01-24) > mounting root partition... > [ 688.377705] EXT4-fs (vda1): mounted filesystem with ordered data mode. > Opts: (null) > installing

bug#27605: Lightweight desktop example fails to build with kernel panic

On Fri, Jul 07, 2017 at 02:23:05PM +0200, Ludovic Courtès wrote: > Did you pass --image-size? If not, it could be that the image size > estimate is slightly too small (see commit > a8ac4f081a9a679498ea42ccfe001f218bba3043). > > The build log should contain something like: > > creating ~a

bug#27563: [PATCH v3 0/2] Make ghostscript reproducible.

Hi Ludo, On Fri, 07 Jul 2017 14:00:09 +0200 l...@gnu.org (Ludovic Courtès) wrote: > Danny Milosavljevic skribis: > > > Also, newer PDF files have an RDF header specifying some extra information > > in an XML-like format. For example there's an instance UUID (PDF/A > >

bug#27563: [PATCH] gnu: ghostscript: Don't write document UUID; use "" as instance UUID.

> What’s the impact of simply removing all of this from generated PDF > files? Should we instead make it optional? I don't know. It's just one metadata element - and it's recent. I mean that there are lots of (old) PDF files that don't have it in the first place. > For instance, we could >

bug#27563: [PATCH] gnu: ghostscript: Don't write document UUID; use "" as instance UUID.

Danny Milosavljevic skribis: > * gnu/packages/patches/ghostscript-no-header-uuid.patch: New file. > * gnu/local.mk (dist_patch_DATA): Add it. > * gnu/packages/ghostscript.scm (ghostscript)[source]: Use it. [...] > --- /dev/null > +++

bug#27563: [PATCH v3 2/2] gnu: ghostscript: Write document ID only when encrypting.

Danny Milosavljevic skribis: > * gnu/packages/patches/ghostscript-no-header-id.patch: New file. > * gnu/local.mk (dist_patch_DATA): Add it. > * gnu/packages/ghostscript.scm (ghostscript)[source]: Use it. [...] > new file mode 100644 > index 0..3526a300e > ---

bug#27563: [PATCH v3 0/2] Make ghostscript reproducible.

Danny Milosavljevic skribis: > Also, newer PDF files have an RDF header specifying some extra information > in an XML-like format. For example there's an instance UUID (PDF/A specifies > that it's recommended to set this to an empty string), and a document UUID. > The

bug#27605: Lightweight desktop example fails to build with kernel panic

Leo Famulari skribis: > On Fri, Jul 07, 2017 at 08:53:37AM -0400, Leo Famulari wrote: >> On Fri, Jul 07, 2017 at 02:23:05PM +0200, Ludovic Courtès wrote: >> > Did you pass --image-size? If not, it could be that the image size >> > estimate is slightly too small (see commit

bug#27563: [PATCH v3 0/2] Make ghostscript reproducible.

Danny Milosavljevic skribis: > Hi Ludo, > > On Fri, 07 Jul 2017 14:00:09 +0200 > l...@gnu.org (Ludovic Courtès) wrote: > >> Danny Milosavljevic skribis: >> >> > Also, newer PDF files have an RDF header specifying some extra information >> > in an