On Tue, Oct 25, 2016 at 07:59:07PM +0200, Hartmut Goebel wrote:
> Am 25.10.2016 um 14:49 schrieb Leo Famulari:
> > Changing the subject: Is that branch stable? Can I start testing core
> > Python package upgrades on top of it?
>
> I worked on this branch, just fixed some last (hopefully) errors an
Am 25.10.2016 um 14:49 schrieb Leo Famulari:
> Changing the subject: Is that branch stable? Can I start testing core
> Python package upgrades on top of it?
I worked on this branch, just fixed some last (hopefully) errors and
IMHO the branch is stable.
--
Regards
Hartmut Goebel
| Hartmut Goebel
On Tue, Oct 25, 2016 at 11:48:42AM +0200, Hartmut Goebel wrote:
> Am 23.10.2016 um 21:52 schrieb ng0:
> > I think this is wrong. My assumption is I work with the old system as
> > long as the new system is not in place. I see no changes which fix this,
> > so why should I do work in advance when th
Am 23.10.2016 um 21:52 schrieb ng0:
> I think this is wrong. My assumption is I work with the old system as
> long as the new system is not in place. I see no changes which fix this,
> so why should I do work in advance when this must be fixed afterwards?
>
> Will the current system report packages
Hartmut Goebel writes:
> Hi,
>
> I just found some Python packages recent checked in to master, which
> have "inputs" defined.
>
> All Python packages, please keep in mind:
>
> *The default for including other Python packages is "propagated-inputs".*
>
> guix import is wrong here, as it defaults
Hi,
I just found some Python packages recent checked in to master, which
have "inputs" defined.
All Python packages, please keep in mind:
*The default for including other Python packages is "propagated-inputs".*
guix import is wrong here, as it defaults to "inputs". Please refer to
the section
