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

[Ricardo Wurmus]

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 can push the updates tomorrow.

That’s fine.  Then we’ll have to add the missing updates in the days
after that.

--
Ricardo

Re: Difference between Scintilla's license and ISC

[Andreas Enge]

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]

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 be working as they
were before, others may be off in subtle ways. For example, the time
display is UTC and seemingly unchangeable.

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.

If this is okay, I can push the updates tomorrow.


signature.asc
Description: PGP signature

Re: Cuirass enhancements

[Ricardo Wurmus]

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?

Since real constant pages are impossible (or can only be approximated)
I’d like to know just how far to the beginning or end I am.

It doesn’t need to be a number.  If it was just a line at the bottom
with a marker near the beginning, the middle, or the end, and adjusting
its position as I go to the next or previous page I’d already be happy.

--
Ricardo

Re: Difference between Scintilla's license and ISC

[Giovanni Biscuolo]

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 purpose and without fee is hereby granted,
>>> 
>>> and the ISC license is:
>>> Permission to use, copy, modify, and/or distribute this software for
>>> any purpose with or without fee is hereby granted,
>>
>> Notice the lack of the little word "with" in the first license.
>
> Interestingly, Debian includes Scite which includes code under the
> Scintilla license (see bottom):
>
>
> https://metadata.ftp-master.debian.org/changelogs//main/s/scite/scite_3.7.2-1_copyright

The correct license name is "Historical Permission Notice and
Disclaimer", thanks to Wikipedia [1]

This is the GNU entry:
https://www.gnu.org/licenses/license-list.en.html#HPND

the approved text is here:
https://directory.fsf.org/wiki/License:HPND
and Scintilla uses that text AFAIU

I've added HPND to our gnu/licenses.scm and sent a patch, bug number
#36295; give me a go/no go please :-) (I can push it if needed)

Happy Guix! Gio'.


[1] https://en.wikipedia.org/wiki/Scintilla_(software)

-- 
Giovanni Biscuolo

Xelera IT Infrastructures


signature.asc
Description: PGP signature

Re: Cuirass enhancements

[Danny Milosavljevic]

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 keep constant because the database changes
and so does n.
So the "/n" part on the display would keep changing--and it would be correct
in doing so.  Furthermore, the page number you are *on* would also keep
changing.

Even if there were fixed-layout "page"s, the way the database is
structured means that having pagination show a fixed number of items
per page at all is difficult to do (cuirass tries to do it).

Alternatively, the server could keep a serializable transaction
open per client session.
Then you just wouldn't see new builds until you somehow restarted your
client session (HTTP is stateless--so more fakery necessary there).
Then you can have page numbers :)

> I'm at the first tab. "Previous" is greyed out.

I don't like this graying out business.  It's perfectly possible that a new
entry appeared in the database that is now (because of the sorting) before what
you thought was the first page (because back then when you queried the page it
*was* the first page--emphasis on "was")--and now you can't get to it.

> Then I would expect
> "First" also to be greyed out: If I cannot go any further back, I am on
> the "First" tab (linear, consecutive order of tabs assumed :-))

I've made "First" and "Last" behave the way you expect in cuirass commit
d5b827097b456100039370003899ec7ad04ac934.  However, that is not
an endorsement of graying out.  I just like consistency.
 
> Even worse at the end: I can click four times on "Next", and then be at
> a page that shows only three jobs (the total number of jobs is not
> always dividable by the number of jobs per page, so the last page
> usually has a smaller remainder to show):
> https://ci.guix.gnu.org/eval/5862?border-high-time=1560816540&border-high-id=1398862
> So, I cannot go any NEXTer, that button is greyed out. As with the
> beginning, I'm expecting to be already on the LAST page. But the button
> is clickable. And when I click it, I will receive a FULL PAGE! 

Yeah, well, pages don't exist and cuirass in imperfectly faking them.

I'd go back to first principles and ask what problem the paging is supposed to
solve, then solve it in a different way.  It's already very different to what
book pages would be.

Suggestions welcome.


pgpykhqFYfzga.pgp
Description: OpenPGP digital signature

Re: Difference between Scintilla's license and ISC

[Ricardo Wurmus]

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,
>> 
>> and the ISC license is:
>> Permission to use, copy, modify, and/or distribute this software for
>> any purpose with or without fee is hereby granted,
>
> Notice the lack of the little word "with" in the first license.

Interestingly, Debian includes Scite which includes code under the
Scintilla license (see bottom):

   
https://metadata.ftp-master.debian.org/changelogs//main/s/scite/scite_3.7.2-1_copyright

-- 
Ricardo

Re: Packaging FreeCAD

[John Soo]

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

[Ricardo Wurmus]

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 logs of the failed
prerequisites are linked directly.

(We don’t keep that kind of information in the database, so we don’t
know what *build* relates to the failure.  We get that information in a
round-about way through the derivation of the build and the Guix
derivations API.)

--
Ricardo

Re: Difference between Scintilla's license and ISC

[Andreas Enge]

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:
> Permission to use, copy, modify, and/or distribute this software for
> any purpose with or without fee is hereby granted,

Notice the lack of the little word "with" in the first license.

Andreas

Re: Cuirass enhancements

[Ricardo Wurmus]

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!

[Hartmut Goebel]

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 Python executable figure out from which environment it was
> started.

This is my plan, see my yesterday's mail:
0cf6e747-48b5-1606-28a0-02fd4d370...@crazy-compilers.com

-- 
Regards
Hartmut Goebel

| Hartmut Goebel  | h.goe...@crazy-compilers.com   |
| www.crazy-compilers.com | compilers which you thought are impossible |

Difference between Scintilla's license and ISC

[Nicolas Goaziou]

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 Scintilla and SciTE

Copyright 1998-2002 by Neil Hodgson 

All Rights Reserved 

Permission to use, copy, modify, and distribute this software and
its documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and
that both that copyright notice and this permission notice appear in
supporting documentation.

NEIL HODGSON DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN
NO EVENT SHALL NEIL HODGSON BE LIABLE FOR ANY SPECIAL, INDIRECT OR
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

and the ISC license is:

License text

Copyright  

Permission to use, copy, modify, and/or distribute this software for
any purpose with or without fee is hereby granted, provided that the
above copyright notice and this permission notice appear in all
copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.

WDYT?

Regards,

-- 
Nicolas Goaziou

Re: Cuirass enhancements

[Björn Höfling]

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
> >> about failures.  
> >
> > Cuirass now has tabs, though it won’t show “newly” succeding or
> > failing jobs.  It just splits them by state, which is an
> > improvement over having just one big list.
> >
> > (The “Scheduled” tab isn’t currently working, will look into this
> > later…)  
> 
> This works now.
> 

Hi Ricardo,

that's so fast :-)

Thank you, looks good.

Björn


pgpFdzJH1Memk.pgp
Description: OpenPGP digital signature

Re: Cuirass enhancements

[Ricardo Wurmus]

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” succeding or failing
> jobs.  It just splits them by state, which is an improvement over having
> just one big list.
>
> (The “Scheduled” tab isn’t currently working, will look into this
> later…)

This works now.

-- 
Ricardo

Re: Cuirass enhancements

[Ricardo Wurmus]

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 splits them by state, which is an improvement over having
just one big list.

(The “Scheduled” tab isn’t currently working, will look into this
later…)

--
Ricardo

Re: Alternate logo (origami gnu)

[Dan Frumin]

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 artist and this only took a couple of hours.  Please tweak and
use under whatever license you prefer.  Or don't use.  It was done purely
for fun in inkscape.

https://paste.debian.net/hidden/47b14e9a/


Fun!

Now you’ll have to come up with folding instructions so we can make it
for real.  :-)



I've managed to find folding instructions for this online: 
https://issuu.com/dafeba/docs/gnu
(warning, the page seem to require arbitrary JavaScript), and it's relatively 
easy to make it! :-)

Now we just need to get instructions licensed under a free license. :-)

Best,
Dan


Thanks for sharing,
Ludo’.