bug#22276: .sig

2016-01-04 Thread Alex Kost
Ludovic Courtès (2016-01-03 14:10 +0300) wrote: > Alex Kost skribis: > >> Ludovic Courtès (2016-01-01 21:04 +0300) wrote: >> >>> I’ve amended that section of the manual based on text from the >>> announcement (see >>> ). >>> Step

bug#22276: .sig

2016-01-04 Thread Alex Kost
Ludovic Courtès (2016-01-03 14:22 +0300) wrote: > Seems that the GPH repository given at > is now unreachable: > > $ cvs -z3 -d :pserver:anon...@cvs.gnupg.org:/cvs/gph co gph > cvs [checkout aborted]: connect to cvs.gnupg.org(217.69.76.56):2401 fail

bug#22276: .sig

2016-01-04 Thread Ludovic Courtès
Alex Kost skribis: > Ludovic Courtès (2016-01-03 14:10 +0300) wrote: > >> Alex Kost skribis: >> >>> Ludovic Courtès (2016-01-01 21:04 +0300) wrote: >>> I’ve amended that section of the manual based on text from the announcement (see

bug#22274: GuixSD resets hardware clock (on Lenovo x200 with libreboot)

2016-01-04 Thread Christopher Allan Webber
Ludovic Courtès writes: > Christopher Allan Webber skribis: > >> If I reboot into GuixSD, at some point in the boot process it resets my >> hardware clock to 1970! If I reboot into Debian again after that, it's >> 1970 there also. > > Ouch! Your config includes the ntp daemon. Could it be that

bug#22274: GuixSD resets hardware clock (on Lenovo x200 with libreboot)

2016-01-04 Thread Christopher Allan Webber
Mark H Weaver writes: > Very strange. FWIW, I've used Libreboot X60 and X200 laptops running > GuixSD quite extensively -- they are my primary development machines -- > and I've never seen anything like this. > > One possibility that comes to mind is that perhaps your hardware clock > battery is

bug#22274: GuixSD resets hardware clock (on Lenovo x200 with libreboot)

2016-01-04 Thread Ludovic Courtès
Christopher Allan Webber skribis: > Ludovic Courtès writes: > >> Christopher Allan Webber skribis: >> >>> If I reboot into GuixSD, at some point in the boot process it resets my >>> hardware clock to 1970! If I reboot into Debian again after that, it's >>> 1970 there also. >> >> Ouch! Your con

bug#22304: Build for Julia is not reproducible

2016-01-04 Thread Ricardo Wurmus
When building “julia” twice we get different binaries for $out/lib/julia/sys.so and $out/lib/julia/sys-debug.so I could not determine the exact differences, because instead of a diff I just see something like this: --- /gnu/store/6njfyp46b22b0wb0r0ccg2wdzjx7066g-julia-0.4.2/lib/julia/sys.s

bug#16791: w3m fails to do any SSL certificate checking

2016-01-04 Thread Leo Famulari
On Mon, Jan 04, 2016 at 01:19:32AM -0500, Leo Famulari wrote: > On Sat, Jan 02, 2016 at 09:20:30PM -0500, Leo Famulari wrote: > > I looked into how Debian does it. They bundle a configuration file that > > sets the correct options. > > > > If you download the "debian" file [0], which includes all

bug#16791: w3m fails to do any SSL certificate checking

2016-01-04 Thread Ludovic Courtès
Leo Famulari skribis: > On Sat, Jan 02, 2016 at 09:20:30PM -0500, Leo Famulari wrote: >> I looked into how Debian does it. They bundle a configuration file that >> sets the correct options. >> >> If you download the "debian" file [0], which includes all of their >> packaging for w3m, you can vie