bug#30434: magit won’t work over TRAMP

Hi Alex, Alex Kost writes: > Mark H Weaver (2018-02-14 03:51 -0500) wrote: > >> Ricardo Wurmus writes: >>> I think it makes sense *not* to hardcode the path to the git executable >>> here. >> >> Agreed. Done, in commit

bug#30434: magit won’t work over TRAMP

Mark H Weaver (2018-02-14 03:51 -0500) wrote: > Ricardo Wurmus writes: >> I think it makes sense *not* to hardcode the path to the git executable >> here. > > Agreed. Done, in commit 5fe9ba59ba1cea12a70d011aacbace52e3bfda18 on > master and commit

bug#30436: bigloo@4.3b hash mismatch

Amirouche Boubekki skribis: > 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

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

Hi Leo, > The researcher's advisory recommends building UnZip with FORTIFY_SOURCE > to reduce the impact of the bug. The attached patch does that. […] > + ;; Mitigate CVE-2018-135, an exploitable buffer > overflow. > + ;; This environment variable is

bug#30434: magit won’t work over TRAMP

Ricardo Wurmus writes: > I think it makes sense *not* to hardcode the path to the git executable > here. Agreed. Done, in commit 5fe9ba59ba1cea12a70d011aacbace52e3bfda18 on master and commit 317e8e9404058af35d9843e076934560f95d895a on core-updates. I'm closing this bug now.