bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

I think Google uses JGit for their public facing Git servers, but I'm not sure. On February 12, 2018 5:59:50 PM EST, Danny Milosavljevic wrote: >Hi Leo, > >On Mon, 12 Feb 2018 10:09:39 -0500 >Leo Famulari wrote: > >> I think it's worth adding, but as

bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’

Ricardo Wurmus writes: > Mathieu Lirzin writes: > >> Danny Milosavljevic writes: >> >>> On Mon, 12 Feb 2018 17:52:41 +0100 >>> Mathieu Lirzin wrote: >>> I think it would work better if when installing python@3, a

bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’

Mathieu Lirzin writes: > Hi, > > Danny Milosavljevic writes: > >> On Mon, 12 Feb 2018 17:52:41 +0100 >> Mathieu Lirzin wrote: >> >>> I think it would work better if when installing python@3, a ‘python’ >>> executable would be available in

bug#30428: guix git-fetch doesn't specify "--depth 1" - git clone clones a lot without any use

Hi Leo, On Mon, 12 Feb 2018 10:09:39 -0500 Leo Famulari wrote: > I think it's worth adding, but as an option, because there are Git > server implementations, like JGit, that don't support shallow cloning. Thanks for that! I didn't consider that before... Possible patch

bug#30437: closed (Re: bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’)

help-debb...@gnu.org (GNU bug Tracking System) writes: > From: Ricardo Wurmus > Subject: Re: bug#30437: No “.guix-profile/bin/python” after ‘guix package -i > python’ > To: 30437-d...@debbugs.gnu.org > Date: Mon, 12 Feb 2018 20:00:57 +0100 (38 minutes, 1 second ago) >

bug#30434: magit won’t work over TRAMP

Alex Kost writes: > Ricardo Wurmus (2018-02-12 13:53 +0100) wrote: > >> The default value for “magit-git-executable” (when magit is installed >> via Guix) appears to be a store path, such as >> “/gnu/store/l7g5r1c2i0bf3cd71g53ajy8khdcyidz-git-2.16.1/bin/git”. This >> means

bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’

Hi, Danny Milosavljevic writes: > On Mon, 12 Feb 2018 17:52:41 +0100 > Mathieu Lirzin wrote: > >> I think it would work better if when installing python@3, a ‘python’ >> executable would be available in the PATH. Maybe there is a technical >> reason for

bug#30415: Unzip CVE-2018-1000031 and others

On Sun, Feb 11, 2018 at 10:35:48AM -0500, Leo Famulari wrote: > And CVE-2018-135 may be mitigated by the compiler. I'll investigate > more. The researcher's advisory recommends building UnZip with FORTIFY_SOURCE to reduce the impact of the bug. The attached patch does that. AFAICT, the

bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’

On Mon, Feb 12, 2018 at 06:23:07PM +0100, Danny Milosavljevic wrote: > Hi Mathieu, > > On Mon, 12 Feb 2018 17:52:41 +0100 > Mathieu Lirzin wrote: > > > I think it would work better if when installing python@3, a ‘python’ > > executable would be available in the PATH. Maybe there

bug#30434: magit won’t work over TRAMP

Ricardo Wurmus (2018-02-12 13:53 +0100) wrote: > The default value for “magit-git-executable” (when magit is installed > via Guix) appears to be a store path, such as > “/gnu/store/l7g5r1c2i0bf3cd71g53ajy8khdcyidz-git-2.16.1/bin/git”. This > means that when magit is used over TRAMP it will try

bug#30436: bigloo@4.3b hash mismatch

On 2018-02-12 17:59, Leo Famulari wrote: On Mon, Feb 12, 2018 at 05:43:35PM +0100, Amirouche Boubekki wrote: Trying to install bigloo@4.3b leads to a hash mismatch. This was reproduced by several people. Can you copy and paste the error message here? $ guix package -i bigloo@4.3b

bug#30437: No “.guix-profile/bin/python” after ‘guix package -i python’

Hi Mathieu, On Mon, 12 Feb 2018 17:52:41 +0100 Mathieu Lirzin wrote: > I think it would work better if when installing python@3, a ‘python’ > executable would be available in the PATH. Maybe there is a technical > reason for not doing so, but I find its absence rather confusing.

bug#30436: bigloo@4.3b hash mismatch

Trying to install bigloo@4.3b leads to a hash mismatch. This was reproduced by several people.

bug#30435: libreoffice: Fonts don't show up after install

Package: guix After installing and running libreoffice with $ guix package -i libreoffice@5.3.7.2 $ soffice no fonts show up (see attached screenshot). Following the instructions provided by https://www.gnu.org/software/guix/manual/html_node/Application-Setup.html#Application-Setup I did $ guix

bug#30434: magit won’t work over TRAMP

The default value for “magit-git-executable” (when magit is installed via Guix) appears to be a store path, such as “/gnu/store/l7g5r1c2i0bf3cd71g53ajy8khdcyidz-git-2.16.1/bin/git”. This means that when magit is used over TRAMP it will try to find the exact same git executable on the remote.