Andy Wingo skribis:
> On Mon 04 Apr 2016 12:20, iyzs...@member.fsf.org (宋文武) writes:
>
>> How to fix this?
>>
>> The procedure is ‘update-package-source’ in (guix upstream).
>> it find the file, then use ‘substitute’ to replace the version and
>> hash. ‘substitute’ works line-by-line, it can’t m
On Mon 04 Apr 2016 12:20, iyzs...@member.fsf.org (宋文武) writes:
> How to fix this?
>
> The procedure is ‘update-package-source’ in (guix upstream).
> it find the file, then use ‘substitute’ to replace the version and
> hash. ‘substitute’ works line-by-line, it can’t match mutiple lines.
>
> I try:
Leo Famulari writes:
> I've noticed that `guix refresh -u` will update extraneous packages if
> they happen to have the same version and be in the same module.
>
> For example, from commit d694230ab, you can reproduce the bug:
>
> $ ./pre-inst-env guix environment guix -- ./pre-inst-env guix refr
On Mon, Feb 22, 2016 at 10:33:12PM +0100, Andreas Enge wrote:
> On Tue, Feb 16, 2016 at 04:27:24AM -0500, Leo Famulari wrote:
> > I've noticed that `guix refresh -u` will update extraneous packages if
> > they happen to have the same version and be in the same module.
> >
> > For example, from com
On Tue, Feb 16, 2016 at 04:27:24AM -0500, Leo Famulari wrote:
> I've noticed that `guix refresh -u` will update extraneous packages if
> they happen to have the same version and be in the same module.
>
> For example, from commit d694230ab, you can reproduce the bug:
>
> $ ./pre-inst-env guix env
I've noticed that `guix refresh -u` will update extraneous packages if
they happen to have the same version and be in the same module.
For example, from commit d694230ab, you can reproduce the bug:
$ ./pre-inst-env guix environment guix -- ./pre-inst-env guix refresh -u
python-pytest
$ git diff
