Hi Bengt,
> IOW, a bunch just differ by version -- I wonder how many of the
> packages that drew in old versions could run fine with respective
> latest versions of what they are dependent on?
That's a very good question!
> It would be really interesting if you could tweak your
Hi Pierre, and apologies to Efraim...
On +2019-11-26 14:01:10 +0100, Pierre Neidhardt wrote:
> Bengt Richter writes:
>
> > be a binary. Its... both? Javascript libraries leave distro
>
> Typo: "It's".
>
I noticed that too, but it's Efraim's typo,
as is the entire text: I merely
Hi Guix!
Today I have been reading https://www.divio.com/blog/documentation/
which makes some good points on how to write good documentation. They
suggest to divide documentation into four categories, depending on
their purpose:
- tutorials, written for newcomers. They should be to the point and
Hi Konrad,
On +2019-11-26 17:51:52 +0100, Konrad Hinsen wrote:
> Konrad Hinsen writes:
>
> > I'd say the very first thing we should do is look at all non-Python
> > packages that depend indirectly on Python 2.
>
> Here is an attempt at identifying them:
>
>
WebKitGTK is not rebuilt with my patch, because I removed the GnuTLS
update.
You can test with substitutes, it should work with no problem.
> P.S. I apply the patches using "patch" command, right?
With `git am`.
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP
On Tue, 26 Nov 2019 11:07:28 +0100
Pierre Neidhardt wrote:
> I was waiting for people to test the patch, since it does not run
> properly on my machine (the UI does not show up).
>
> Have you tried it yourself, Jan? Does ti work for you?
>
That's the chicken and the egg problem - I can't try
Hi,
> And what i observed is it seems that 'guix gc' doesn't clean old guix
> revision.
It is because when pulling you do not replace but you create another
profile. Therefore, garbage collect does not apply as you expect. It
appears clearly by running "guix gc --list-roots" on your guix:latest
Pierre Neidhardt writes:
> In this case, how would you intend to use guix time-machine to reproduce
> these profiles?
"guix time-machine" and inferiors are different ways to access specific
Guix versions. "guix time-machine" simply runs a different Guix version.
You can then use it to access
I'm not sure how to apply conflicting patches with Magit. Good
question, I'd like to know how to do it too! :)
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
In this case, how would you intend to use guix time-machine to reproduce
these profiles?
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
getmail is still python2.7, but on the mailinglist of it
(not archived iirc) there are efforts to move it to python3-only,
however this will take time. I've looked into porting it before
and half-succeeded (only half due to the same problem as the
maintainer has: time).
I think i saw getmail on
Hi Konrad,
Am 26.11.19 um 17:51 schrieb Konrad Hinsen:
> I find 313 packages (see list below). A few of them are still Python
> stuff (has "python" in the name but not "python2"), but most of them
> look like packages that are not themselves Python libraries.
Thanks for having brought up this
Hi Ludo,
On Tue, 26 Nov 2019 at 10:59, Ludovic Courtès wrote:
> > Obviously, it needs some love (dameon) to fit your use case.
>
> The way I’d do it is by doing:
>
> guix system docker-image config.scm
[...]
> Anyhow, thanks for sharing. I’ve used Guix on top of a “foreign distro”
> for
Konrad Hinsen writes:
> I'd say the very first thing we should do is look at all non-Python
> packages that depend indirectly on Python 2.
Here is an attempt at identifying them:
;;
(use-modules (guix packages)
(gnu packages)
Hi,
Thank you for working that.
On Mon, 25 Nov 2019 at 22:15, Jan wrote:
> Sorry for being impatient, but is it normal for patches to be merged
> that long? Is there something stopping the commits?
> I need those merged in order to continue working on Jami.
Two weeks are not that long. ;-)
Hi Pierre,
> One question arises though: channel specifications only make sense for
> profiles generated with manifests.
Not even for those, if the manifest uses inferior-packages. I'd go for
per-package channel specifications. They could be optimized (more
compact, more efficiently usable) by
To append some context to my comment, I've even tried to change
this in the build-system of gnunet, but after some discussion
it turned out to be a non-trivial task for design choices which
I amounts to bikeshed in the end. I wanted this change.
Searching for it in PLIST files, it's more common
Hi Ludo,
Am Dienstag, den 26.11.2019, 11:17 +0100 schrieb Ludovic Courtès:
> Hi Leo,
>
> Leo Prikler skribis:
>
> > From 42eedd4d9d64a8432f787e68d64476c59200c1b6 Mon Sep 17 00:00:00
> > 2001
> > From: Leo Prikler
> > Date: Sat, 23 Nov 2019 19:51:15 +0100
> > Subject: [PATCH 1/2] services: Add
Hi Guix,
In case someone likes a narrower style:
On +2019-11-26 12:27:37 +0200, Efraim Flashner wrote:
> Hopefully this is better. I added a new line between each paragraph
>
> On Tue, Nov 26, 2019 at 10:58:41AM +0100, Pierre Neidhardt wrote:
> > I think the attachment broke the formatting of
Attached are two patches. The first one searches through the listed
dependencies and removes the ones that are marked as optional. This
(potentially) decreases the size of each crate and the number of
dependencies.
Before:
(package
(name "rust-serde")
(version "1.0.103")
(source
(origin
Hi,
Ludo wrote:
> I think you could come up with a ‘qt-build-system’ (is that an
> appropriate name?) that simply adds the things above on top of
> ‘gnu-build-system’, similar to what ‘glib-or-gtk-build-system’ does.
Many thanks for this valuable hint!
I've build a prototype and found two
Hi,
Am 26.11.19 um 11:32 schrieb Ludovic Courtès:
> IMO it would be nicer to have them install things to $out/libexec.
Given ng0's comment, I'll not put time into this for now.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goe...@crazy-compilers.com |
|
Hey Ludo and Pjotr,
> Really cool! Talking in the distro or some embedded devroom may allow
> you to reach out to people not yet familiar with Guix, which is nice,
> but like Pjotr says, you can probably submit the talk to more than one
> devroom and people will coordinate.
Thank you! Yes I
Hi Leo,
Leo Prikler skribis:
> From 42eedd4d9d64a8432f787e68d64476c59200c1b6 Mon Sep 17 00:00:00 2001
> From: Leo Prikler
> Date: Sat, 23 Nov 2019 19:51:15 +0100
> Subject: [PATCH 1/2] services: Add polkit-wheel-service.
>
> * gnu/services/desktop.scm: (polkit-wheel): New variable.
>
Hi,
Hartmut Goebel skribis:
> I just discovered that some packages store programs in $out/lib/libexec
> instead of $out/libexec. In my store, only KDE packages are effected.
>
> Is it worth investigating? Or shall we just leave as it i?
IMO it would be nicer to have them install things to
I was waiting for people to test the patch, since it does not run
properly on my machine (the UI does not show up).
Have you tried it yourself, Jan? Does ti work for you?
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Hopefully this is better. I added a new line between each paragraph
On Tue, Nov 26, 2019 at 10:58:41AM +0100, Pierre Neidhardt wrote:
> I think the attachment broke the formatting of the file (there is no
> paragraph break). Could you resend it?
>
--
Efraim Flashner אפרים פלשנר
GPG key =
Hi,
Efraim Flashner skribis:
> I've been working on using 'guix system container' to deploy services on
> non-Guix systems and I've been thinking of preparing a talk and sending
> it off to the distribution room.
>
> I think it would be interesting to give a talk to the rust people about
> my
Mathieu Othacehe skribis:
>> Does anywone understands what's going on here?
>
> Found it! It's the #:return-errno passed to pointer->procedure that
> makes every call to libgit2->procedure return two values.
>
> The second one (the errno) was silently ignored. I'll propose a patch
> soon.
Oh,
Hi,
Mathieu Othacehe skribis:
> Never looked into it, but it seems that nix has proper cross compilation
> support for meson (using cross-file.conf as you mentionned), see:
> nixpkgs/pkgs/development/tools/build-managers/meson/default.nix
>
> Sadly there are other build-systems where
Hi,
Mathieu Othacehe skribis:
> I ran further tests. On Ubuntu 18.04, using qemu-user-static or
> qemu-user-binfmt makes no difference, they both fail.
>
> qemu-user-static works on Ubuntu 19.04 because of the addition of the
> 'F' flag, see:
>
Hi!
Mathieu Othacehe skribis:
> I submited a talk to minimalistic devroom titled: "GNU Guix as an
> alternative to the Yocto Project". Maybe the distributions devroom would
> have been more appropriate.
>
> The point of this talk is to compare the process of creating a small
> root filesystem
Hi Vincente & all,
zimoun skribis:
> I was suggesting that maybe you can use Guix to create this image. :-)
>
> $ guix describe
> Generation 57 Nov 25 2019 14:26:15(current)
> guix b5d4d5b
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit:
I think the attachment broke the formatting of the file (there is no
paragraph break). Could you resend it?
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Hellp zimoun,
my two cents on Docker as container images builder (not as "container
instantiation toolbox")
zimoun writes:
[...]
> The relationship between Docker and GNU Guix is container and the LXC
> [1] technology. They use both but differently:
>
> - Docker is rooted in
Hello,
zimoun skribis:
> On Thu, 21 Nov 2019 at 12:10, Pjotr Prins wrote:
>
>> I am wondering if we could directly generate Singularity containers as
>> we do with Docker today.
>
> I am not using Singularity so maybe I miss a point. But
>
> guix pack -f squashfs
>
> does not do the right
Hello,
Konrad Hinsen skribis:
>> What do we disagree on, actually? :-)
>
> This:
>
>>> 2. Power users will always write code in powerful languages that exceed
>>>what less advanced users can deal with. And since power users are not
>>>necessarily benevolent, this creates a trust issue
Hello,
zimoun skribis:
> On Sat, 16 Nov 2019 at 23:27, Ludovic Courtès wrote:
>
>> > Me too :-) It's "guix package" that is the worst offender in my
>> > opinion. It does two distinct things: querying the package database and
>> > managing profiles. And now that we have "guix search" for
Hello Clément,
Clément Lassieur writes:
> Giovanni Biscuolo writes:
>
>> please can you file a bug?
>> the bug could (should) be specific to the zpaq package
>
> No, it's common to all packages (use 'guix build -S --no-substitutes' to
> reproduce easily). And the documentation[1] doesn't say
39 matches
Mail list logo
