Re: Shall we merge wip-gnome3.30 to core-updates?

Hi Kei, > This could be partly caused by the fact that only some of the GNOME > packages were updated to their 3.30 versions, but I don't know how GNOME > works well enough to diagnose the issue right away. What GNOME packages that should be updated haven’t been updated ? > If this is okay, I

Re: Difference between Scintilla's license and ISC

Hello! I do not get why the license can be free with the non-commercial clause. What am I misunderstanding? Andreas

Re: Shall we merge wip-gnome3.30 to core-updates?

Kei Kebreau writes: > Marius Bakke writes: > >> @Kei: If you have tested this branch elsewhere, I think it's okay to >> merge even if it does not yet build on 'core-updates'. > > Great! I'll give the branch a test on top of "master" first. Update on the GNOME updates: while most things seem to

Re: Cuirass enhancements

Danny Milosavljevic writes: > On Tue, 18 Jun 2019 19:50:25 +0200 > Björn Höfling wrote: > >> * I would like to know that I'm on page k/n. > > That web interface is a frontend to a dynamically changing database > (and a quickly changing database at that). > > What would "page" even mean there?

Re: Difference between Scintilla's license and ISC

Hello Guix! Ricardo Wurmus writes: > Andreas Enge writes: > >> I think that the Scintilla license is non-free... >> >> On Wed, Jun 19, 2019 at 01:24:15PM +0200, Nicolas Goaziou wrote: >>> Permission to use, copy, modify, and distribute this software and >>> its documentation for any pur

Re: Cuirass enhancements

Hi Björn, On Tue, 18 Jun 2019 19:50:25 +0200 Björn Höfling wrote: > * I would like to know that I'm on page k/n. That web interface is a frontend to a dynamically changing database (and a quickly changing database at that). What would "page" even mean there? And the "/n" part is impossible to

Re: Difference between Scintilla's license and ISC

Andreas Enge writes: > I think that the Scintilla license is non-free... > > On Wed, Jun 19, 2019 at 01:24:15PM +0200, Nicolas Goaziou wrote: >> Permission to use, copy, modify, and distribute this software and >> its documentation for any purpose and without fee is hereby granted, >>

Re: Packaging FreeCAD

Hi Paul, > How about engineering.scm for FreeCAD? This module already contains > other CAD-related packages such as LibreCAD and KiCad. Thanks. I did this and am preparing a patch now. - John

Re: Cuirass enhancements

Björn Höfling writes: > * If a job failed because of its dependency, I would like to see which > one caused the problem. I don't know how to find that out. > In Hydra, the name and build log of the failing dependency was directly > available. This is now implemented on the “details” page. The

Re: Difference between Scintilla's license and ISC

Hello, I think that the Scintilla license is non-free... On Wed, Jun 19, 2019 at 01:24:15PM +0200, Nicolas Goaziou wrote: > Permission to use, copy, modify, and distribute this software and > its documentation for any purpose and without fee is hereby granted, > > and the ISC license is:

Re: Cuirass enhancements

Björn Höfling writes: > It's nice that there is a search now, but it's not enough for me :-) > > The search string disappears from the search box. It would be very nice > if it would be kept, then I can remember and refine it if necessary. This is now implemented. -- Ricardo

Re: Down with PYTHONPATH!

Am 18.06.19 um 17:46 schrieb Konrad Hinsen: > Conda uses the same approach as Python's virtualenv: create a seperate > Python installation made up mainly of linke to files shared with other > such installations. > > We could probably do something similar in Guix as well, assuming we can > make the

Difference between Scintilla's license and ISC

Hello, In bug#36043 (), we discuss an issue about the license used in Scintilla. More specifically, the question is: Does Scintilla desserve its own license in license.scm, or should it use ISC? For the record, the Scintilla license is: License for S

Re: Cuirass enhancements

On Wed, 19 Jun 2019 10:23:57 +0200 Ricardo Wurmus wrote: > Ricardo Wurmus writes: > > > Hi Björn, > > > >> * I'm really missing the tabs/filters like in Hydra: "succeding", > >> "newly succeding", "newly failing", ... > >> In having all jobs in one big list is annoying. I care usually only >

Re: Cuirass enhancements

Ricardo Wurmus writes: > Hi Björn, > >> * I'm really missing the tabs/filters like in Hydra: "succeding", >> "newly succeding", "newly failing", ... >> In having all jobs in one big list is annoying. I care usually only >> about failures. > > Cuirass now has tabs, though it won’t show “newly” s

Re: Cuirass enhancements

Hi Björn, > * I'm really missing the tabs/filters like in Hydra: "succeding", > "newly succeding", "newly failing", ... > In having all jobs in one big list is annoying. I care usually only > about failures. Cuirass now has tabs, though it won’t show “newly” succeding or failing jobs. It just

Re: Alternate logo (origami gnu)

On 17-06-19 11:36, Ludovic Courtès wrote: Hi, Daniel Fitzpatrick skribis: I made an origami gnu based off some origami instructions I found online. Possibly suitable as an alternate logo. Looks vaguely similar to the Clear Linux penguin, but not as polished or polygonal. I'm not an artis