Package for LXQt. Help wanted.

[Meiyo Peng]

Hello everyone,

I made a series of packages for LXQt. The code is at:
https://github.com/meiyopeng/guix/tree/lxqt

I did this beacuse I want to run i3 window manager within lxqt
session. Currently most things work great except lxqt-panel. I have two
problems.

1. The $QT_PLUGIN_PATH environment variable points to
/run/current-system/profile/lib/qt5/plugins. I don't know where it's
set. So qtsvg has to be installed into syetem profile, or all the lxqt
applications can not properly display icons. Should I add qtsvg to
lxqt applications' propagated-inputs? If so, should I add qtbase too,
since qtbase also provides lib/qt5/plugins, although lxqt works without
qtbase in system profile but I can never be sure.

2. lxqt-panel complains about "Warning: Could not find any platform
plugin". (lxqt-runner also prints this message but it works.) I found
out this message was printed by kwindowsystem.

The related code in kwindowsystem:
https://github.com/KDE/kwindowsystem/blob/9f88c9a5d25ff7909c25ce399572ca348b5706b1/src/pluginwrapper.cpp#L79

Qt's document (https://doc.qt.io/qt-5/qcoreapplication.html#libraryPaths)
says "entries of the QT_PLUGIN_PATH environment variable are always
added to libraryPaths". So I install kwindowsystem into system profile,
and add /run/current-system/profile/lib/plugins to QT_PLUGIN_PATH. Then
this error message disappear. But lxqt-panel still does not work.

I still have no idea how to fix lxqt-panel. This does not affect me
because I use i3, so lxqt-panel is useless to me. But there may be other
people interested in LXQt and I want to help them get this fixed. Can
anybody help me?

Will anybody help me review the code? I'd appreciate it.

--
Meiyo Peng

Re: FOSDEM 2019 (ACTION: please register or mail)

[Leo Famulari]

On Mon, Oct 22, 2018 at 05:34:49AM +0200, Björn Höfling wrote:
> as 2018 is already over, I suppose it was in your interest I added you
> to the 2019 list:
> 
> https://libreplanet.org/wiki/Group:Guix/FOSDEM2019#Attendees

Haha, yes, I would like to be on the list for 2019. And for 2018, too,
but that may be out of your control ;)


signature.asc
Description: PGP signature

Re: FOSDEM 2019 (ACTION: please register or mail)

[Björn Höfling]

On Sun, 21 Oct 2018 18:42:48 -0400
Leo Famulari  wrote:

> On Fri, Aug 24, 2018 at 11:23:43AM +0200, Pjotr Prins wrote:
> > If you intend to come and/or want to speak please add your name and
> > proposed title to the new page at
> > 
> >   https://libreplanet.org/wiki/Group:Guix/FOSDEM2018
> > 
> > Alternatively, reply here or mail me privately so we can keep a
> > tally.  
> 
> I will be there!
> 
> Please add my name to the list :) I don't have an account on
> LibrePlanet.

Hi Leo,

nice to hear.

as 2018 is already over, I suppose it was in your interest I added you
to the 2019 list:

https://libreplanet.org/wiki/Group:Guix/FOSDEM2019#Attendees

:-)

Björn


pgph5fFgGMqJB.pgp
Description: OpenPGP digital signature

Re: New Guix reference card

[Leo Famulari]

On Sat, Oct 20, 2018 at 01:05:18PM -0700, Chris Marusich wrote:
> I see that the second page is mostly blank.  Is that intended?

I think it's meant to be the back of a printed card. It would be great
to have a stack of these for FOSDEM :)


signature.asc
Description: PGP signature

Re: FOSDEM 2019 - stand

[Leo Famulari]

On Mon, Oct 15, 2018 at 11:29:53AM +0300, Efraim Flashner wrote:
> * Alex Sassmannshausen
> * Tonton
> * Andreas Enge
> * Ludovic
> * Gabor Boskovits
> * Leo Famulari
> * Tobias G-R
> * Björn Höfling
> * Christopher Baines
> * Julien Lepiller
> * Efraim Flashner

I will definitely be there, and I'd love to take a shift at the table.
It sounds fun!


signature.asc
Description: PGP signature

Re: FOSDEM 2019 (ACTION: please register or mail)

[Leo Famulari]

On Fri, Aug 24, 2018 at 11:23:43AM +0200, Pjotr Prins wrote:
> If you intend to come and/or want to speak please add your name and
> proposed title to the new page at
> 
>   https://libreplanet.org/wiki/Group:Guix/FOSDEM2018
> 
> Alternatively, reply here or mail me privately so we can keep a tally.

I will be there!

Please add my name to the list :) I don't have an account on
LibrePlanet.


signature.asc
Description: PGP signature

Re: libssh vulnerability

[Chris Marusich]

Leo Famulari  writes:

> It's true that libssh2 has too many dependents to update without a
> graft. However, libssh, which is what was changed, only has a handful of
> dependents, which is convenient for us :)

Oh, I see - I was confused and incorrectly thought you had updated
libssh2.  Sorry for the confusion!

-- 
Chris


signature.asc
Description: PGP signature

libssh vulnerability

[Leo Famulari]

On Sat, Oct 20, 2018 at 01:17:48PM -0700, Chris Marusich wrote:
> Will this change trigger many rebuilds?  It has many dependents:
> 
> --8<---cut here---start->8---
> $ guix refresh -l libssh2
> Building the following 1321 packages would ensure 3307 dependent
> packages are rebuilt: [...]
> --8<---cut here---end--->8---

It's true that libssh2 has too many dependents to update without a
graft. However, libssh, which is what was changed, only has a handful of
dependents, which is convenient for us :)

--
$ guix refresh -l libssh
Building the following 9 packages would ensure 12 dependent packages are 
rebuilt: kodi@18.0_alpha-8.ec16dbc wireshark@2.6.4 
guile2.0-guix@0.15.0-5.1d0be47 cuirass@0.0.1-20.fe2b73c emacs-guix@0.5 
gwl@0.1.1 hpcguix-web@0.0.1-3.53e09ea guile2.2-ssh@0.11.3 tmate@2.2.1
--

It's confusing, but libssh and libssh2 are totally separate projects.
And for the record, they are also not related to OpenSSH, which is the
one we all know and use directly.


signature.asc
Description: PGP signature

Re: Packaging Inferno

[Diego Nicola Barbato]

Hello Ludo,

I have sent a patch incorporating most of your feedback to
guix-patc...@gnu.org (bug#33080).

l...@gnu.org (Ludovic Courtès) writes:

> Hi Diego,
>
> Sorry for the delay!

No problem (my replies are not quite instantaneous either).

> Diego Nicola Barbato  skribis:
>
>> Nils Gillmann  writes:
>>
>>> Ludovic Courtès transcribed 1.9K bytes:
 Hello Diego,
 
 Diego Nicola Barbato  skribis:

[...snip...]

 thing to do.  As for trademarks, please see
 
 to determine whether there’s a problem at all.
>>
>> @Ludo:  Judging from the link there seems to be no problem with the
>> trademarks after all.  The bundled fonts (the ones I did not remove),
>> however, are provided in a format native to Inferno (and Plan 9) and can
>> not be rebuilt from source, which might be a problem according to this
>> [2] thread.
>
> Sometimes TTF files are considered source, so it really depends.  Unless
> there’s evidence that there exists another source for these fonts, I’d
> say we can assume it’s fine, possibly with a comment.

I have found no evidence that there exists another source.

> Do you know whether other FSDG distros and Debian provide these fonts?

They do not provide these exact fonts but those from which some of these
are derived (misc and jis are "based" on X fonts, vera is probably based
on Bitstream Vera).
It is harder to find the origin of the other fonts as there is little
information about them (big5 was "provided by students at the University
of Hong Kong" according to its README; courier, gb, and minitel do not
contain any information).  The remaining fonts just reuse "subfonts"
from the other directories.

 Could you also check whether all the code is GPLv2+ like the ‘license’
 field suggests?
>>
>> @Ludo:  According to the NOTICE files scattered through the source tree
>> and the Inferno home page [3] different parts of Inferno are licensed
>> under GPLv2+, LGPLv2+, Expat (MIT-template), Lucent Public License 1.02
>> and Freetype.
>> Am I right to assume that I have to mention all of them in the ‘license’
>> field even though the NOTICE in the root of the source tree [4] says
>> that the "collection" is governed by the GPLv2+?  
>
> Yes, but you can leave a comment explaining that the combined work is
> effectively GPLv2+.
>
>> I could not find the Lucent Public License [5] in the (guix licenses)
>> module.  Should I add it or should I use ‘non-copyleft’?
>
> You can use ‘non-copyleft’ in that case, with a reference to
> .
>
> Note that the page above says that the Lucent PL is incompatible with
> the GPL.  Are we combining GPL code with Lucent code here?

AFAICT LPL code (libmp libsec) is combined with GPL code when building
emu.  There is some more LPL code in the os directory, which is only
needed for building native inferno, and in the appl and module
directories, which contain Limbo code which is run on inferno but not
used to build it.
The NOTICE says that all licenses are compatible with the GPLv2 but that
is apparently incorrect.
As I am not very familiar with software licenses I do not know what to
do about this.  According to the GPL FAQ [*] it is possible to add an
exception when using incompatible libraries, but I am hesitant to
suggest this in a bug report to upstream because I do not know if that
applies here.

Is this a blocker?

 Do I get it right that the build result is a script that launches
 Inferno as a GNU/Linux process?  It seems like it could be useful.
>>
>> @Ludo: That is right.  I got the script from here [6].  It starts the
>> window manager and logs in as the current user; it is supposed to
>> provide a convenient entry point to start exploring the system.
>> Alongside this script in %out/bin/ there is also a symlink to the emu
>> binary which is installed by ‘mk install’ under
>> %out/usr/inferno/Linux/386/bin/ (Linux/arm/bin on arm machines).  This
>> directory contains several other executables.  I am considering making
>> some of them (like the Limbo compiler) available under %out/bin in the
>> same way as emu. 
>
> Sounds good.  Note that, if possible, we should stick to the usual file
> system layout (that is OUT/share, OUT/lib, OUT/bin, etc. and not
> OUT/usr.)  Though if keeping the /usr/inferno layout style is really
> important, we can make an exception.

The layout style is not important; I only used OUT/usr/inferno because
/usr/inferno is the default in mkconfig.  I have changed this to
OUT/share/inferno, which matches what the Nix package [†] does.

[...snip...]

> Thanks for your reply!
>
> Ludo’.

Thanks for the feedback!

Diego

[*]: https://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs
[†]: 
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/inferno/default.nix

Re: Blog: Guix packaging tutorial

[Pierre Neidhardt]

Divan  writes:
> Off topic, but how did you convert this? Guessing pandoc, but it seems
> converted better then the standard, =pandoc index.org -t gfm -o
> /tmp/index.md= would do.

This is a very good question.  Indeed, Org support in Pandoc is sub-par, so I
did not use that.  Instead, I've used Emacs directly and its
~(org-md-export-to-markdown)~ function.  But even then, the export result lacked
a few elements, such as fenced code language tag or the header.
So I wrote a wrapper script to fix that automatically for me.
It's not very generic but it's a starting point.

Here is the implementation:


https://gitlab.com/ambrevar/ambrevar.gitlab.io/tree/master/source/guix-packaging

-- 
Pierre Neidhardt
https://ambrevar.xyz/


signature.asc
Description: PGP signature

Re: Come back and graphical installer

[Pierre Neidhardt]

> * To write this kind of installer in Guile, we need bindings for a nice
>   high level graphical library and we have to be careful not to increase
>   too much the installer footprint.

This could be a great opportunity to revamp Guile-gnome ;)

> So this seems that something we want in the future but that is a bit out
> of reach for the 1.0 release.

I'd be very interested to work on this at some point.

-- 
Pierre Neidhardt
https://ambrevar.xyz/


signature.asc
Description: PGP signature