Le mardi 23 août 2016 à 12:55 -0500, Isaac David a écrit :
> Le mar. 23 août 2016 à 4:51, Paul Kocialkowski a
> écrit :
> > Also, I don't see what problem can arise from this, as it was
> > suggested at:
> > https://labs.parabola.nu/issues/1039
> >
> > ALARM also hardcodes "armv7h" in the distr
Le mar. 23 août 2016 à 4:51, Paul Kocialkowski a
écrit :
Also, I don't see what problem can arise from this, as it was
suggested at:
https://labs.parabola.nu/issues/1039
ALARM also hardcodes "armv7h" in the distributed pacman.conf, so
there's no
specific reason it would cause a problem when
Le vendredi 19 août 2016 à 20:20 -0500, Isaac David a écrit :
> The hack makes sense for them, because they chose to use a
> single pacman.conf template for all the architectures they
> maintain; but we have multiple files, like Arch does, in
> abslibre and therefore can afford just hard-coding "ar
Hi,
Le vendredi 19 août 2016 à 20:20 -0500, Isaac David a écrit :
> This was bug https://labs.parabola.nu/issues/1039, thanks
> for reminding me of it.
Thanks for pushing a fix in the meantime.
> Were you able to test this configuration? Behind the scenes
> ALARM (should I say AGLARM?) is also d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Paul,
This was bug https://labs.parabola.nu/issues/1039, thanks
for reminding me of it.
Were you able to test this configuration? Behind the scenes
ALARM (should I say AGLARM?) is also doing some extra sed
magic to substitute @CARCH@ with a
