Re: The mirrors of hydra are down

On Wed, Nov 28, 2018 at 11:48:04PM -0600, Brett Gilio wrote: > I had a similar issue, I just substituted the hydra.gnu.org url rather > than the mirror, and it worked. If you haven't done so yet, please switch back to the mirror. cannot handle many users at a time, so we need to use the mirror

Re: 01/01: hydra: Increase image sizes for USB image and Flash image.

On Sun, Dec 09, 2018 at 05:16:58PM +0100, Ricardo Wurmus wrote: > > Ludovic Courtès writes: > > > One problem with the installation OS is that it’s pulling ALSA and all > > sorts of sound-related libraries (libsamplerate, etc.), which clearly is > > unnecessary in the installation image. That

Re: GuixSD on librem phone?

On Thu, Dec 06, 2018 at 04:24:38PM +0100, Giovanni Biscuolo wrote: > callular (baseband) merits a dedicated chapter, since it seems > practically impossible *forever* to trust that chips... and that chips > are an important attack vector (Purism will use USB bus to separate > baseband from CPU) I

Boost support for Python 3

On Wed, Dec 05, 2018 at 04:14:19PM +0100, Marius Bakke wrote: > On a side note, it would be good to enable Python 3 support in Boost > too. Do you know what is required? Just adding python-3 to Boost's inputs? Is it low-risk or should we do it in core-updates or its own branch? signature.asc

Re: Using a CDN or some other mirror?

On Wed, Dec 05, 2018 at 10:32:02AM +0800, Meiyo Peng wrote: > If at some point we need to setup traditional mirrors like other major > Gnu/Linux distros, I can contact my friends in China to setup mirrors in > several universities. I was a member of LUG@USTC, which provides the > largest FLOSS

Re: My new signing key

On Wed, Dec 05, 2018 at 03:49:42AM +0300, Oleg Pykhalov wrote: > Hello Guix, > > Recently I've changed my signing subkey, here is it: > > 7238 7123 8EAC EB63 4548 5857 167F 8EA5 001A FA9C Thanks for letting us know. Please remember to update the key on your Savannah user page:

Re: Guix receives donation from the Hanshake project!

On Mon, Dec 03, 2018 at 10:34:23PM +0100, Ludovic Courtès wrote: > Hello Guix! > > We have some good news: the Hanshake project donated to GNU and the FSF, > and part of that goes to us! > > > https://gnu.org/s/guix/blog/2018/gnu-guix-receives-donation-from-the-handshake-project/ > >

Re: push right for trivial commits

On Thu, Nov 22, 2018 at 04:07:33AM +0800, Alex Vong wrote: > I think ECC key works with commit signing precisely because commit > signing simply requires Savannah to store the key. However, for > functionalities provided by Savannah (e.g. sending email to your address > encrypted with your ECC

Re: [bug#33347] [PATCH 4/4] gnu: teeworlds: Update to 0.7.0 [fixes CVE-2018-18541].

On Wed, Nov 21, 2018 at 10:41:08PM +0800, Alex Vong wrote: > I think Leo may be busy since he hasn't reply yet. Should I just push > given the CVE fix? Yes, please push :) signature.asc Description: PGP signature

Re: Proposal: rename sshfs-fuse -> sshfs

On Wed, Nov 14, 2018 at 12:41:59PM +0100, Ricardo Wurmus wrote: > I have no objections to renaming the package, though you’ll need to keep > a definition for “sshfs-fuse” to indicate to users that the package has > been renamed. Right. See the definition of 'letsencrypt' in (gnu packages tls) for

Re: GNOME & Tracker-Sparql

On Sat, Nov 10, 2018 at 06:59:55PM -0600, Brett Gilio wrote: > I hate to be a nuissance: I remember about a month ago wondering when we > could get Tracker-Sparql upgraded, and there was some great input. There > seemed to be a delay in the GNOME channel carrying many updates to our > GNOME

Re: push right for trivial commits

On Tue, Nov 13, 2018 at 09:58:32AM +0800, Alex Vong wrote: > In the discussion, it was mentioned that the GnuPG version installed on > Savannah is 1.4.16. Therefore, savannah cannot send encrypted messages > to me using my ECC key. However, I am not sure about signing commits > with ECC key. Does

Re: Golang programs keeping references [gnu: go: Update default to 1.11.]

On Mon, Nov 12, 2018 at 06:38:53PM +0100, Pierre Neidhardt wrote: > Yes, it should be statically linked. Isn't it the same issue as we recently > had > with go-1.11 itself? > > The fix was > > --8<---cut here---start->8--- >;; Prevent

Re: Golang programs keeping references [gnu: go: Update default to 1.11.]

On Mon, Nov 12, 2018 at 06:38:53PM +0100, Pierre Neidhardt wrote: > Yes, it should be statically linked. Isn't it the same issue as we recently > had > with go-1.11 itself? > > The fix was > > --8<---cut here---start->8--- >;; Prevent

Re: Golang programs keeping references [gnu: go: Update default to 1.11.]

On Mon, Nov 12, 2018 at 12:48:20PM -0500, Leo Famulari wrote: > way, then it's time to finally move the Boyer-Moore implementation in > (guix grafts) to its own module so we can use it easily. Mistake — it's in (guix build grafts). signature.asc Description: PGP signature

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

On Mon, Nov 12, 2018 at 10:45:07AM +0100, Pierre Neidhardt wrote: > Alright, I've applied the changes and updated to go-1.11. > Should we remove go-1.9 now? If all of our Go packages are still working with Go 1.11, then it should be safe to remove Go 1.9. We should take care to handle the

Golang programs keeping references [gnu: go: Update default to 1.11.]

On Mon, Nov 12, 2018 at 04:32:46AM -0500, Pierre Neidhardt wrote: > commit 9a65a052016572b61e3c4247fcdf9e0478656f71 > Author: Pierre Neidhardt > Date: Sun Nov 11 22:02:18 2018 +0100 > > gnu: go: Update default to 1.11. > > * gnu/packages/golang.scm (go): Update default to 1.11. I

Re: more space on berlin.guixsd.org

On Sun, Nov 11, 2018 at 08:11:36PM +0100, Ricardo Wurmus wrote: > Hey Guix, > > today we finally succeeded in attaching an external storage array to the > server known as berlin.guixsd.org. I relocated the /gnu/store directory > from the local 1TB disk to the external storage. The result is

Substituting in parallel to save time?

Substitution honors the --max-jobs argument to the guix-daemon, which means that, by default, substitutes are downloaded in sequence, one at a time. I noticed that in many cases, it takes longer to set up the substitution than to actually download the substitute on my 30 Mbps downlink. The

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

On Wed, Nov 07, 2018 at 09:48:50PM +0100, Pierre Neidhardt wrote: > In my patchset, there are 2 kinds of fixes: > > - Disabling tests because Go 1.11 test policies are stricter and some lax code > from before does not pass anymore. > For this issue, upstream should fix their packages. As far

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

On Wed, Nov 07, 2018 at 09:09:24PM +0100, Pierre Neidhardt wrote: > Sure, but isn't this too much a hassle (and more pollution added to the > package > namespace) for a temporary workaround? It's a matter of taste :) > Shouldn't we focus on fixing the cache bug in the build system instead?

Re: Nano: disable hard wrapping by default

On Tue, Nov 06, 2018 at 07:43:21PM +0100, swedebugia wrote: > Could we disable it by default? > > According to the FAQ this exist: > > "With --disable-wrapping-as-root you can disable any hard-wrapping by > default when the user is root, useful to prevent accidentally changing long > lines in

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

On Wed, Nov 07, 2018 at 05:22:44PM +0100, Pierre Neidhardt wrote: > Hmm, actually it seems that go1.9 is not able to build a package against > dependencies built with go1.11. Yeah, I don't think there is any notion of backwards compatibility there. > For Demlo, that would mean that I need to add

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

On Tue, Nov 06, 2018 at 06:33:53PM +0100, Pierre Neidhardt wrote: > > If most of the Go packages are ready for Go 1.11, we could make it the > > dfeault and then use Go 1.9 for the packages that are lagging behind. Or > > vice versa. > > How do you do that? The default Go is defined in ((guix

Re: Trying to make texinfo patch

On Tue, Nov 06, 2018 at 06:53:59PM +0100, Thorsten Wilms wrote: > AWS is rather complex. Several services make things easier if all one is > looking for is off-site backup, but some would make you use > Non-Free-Software, the very thing this community can never recommend. There are packages in

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

On Tue, Nov 06, 2018 at 06:04:54PM +0100, Pierre Neidhardt wrote: > Actually bug 32919 matters, it breaks Demlo and all packages that depend on > packages that need special compilation flags (e.g. -tags "xyz"). > > Concretely, say A depends on B and B must be built with "-tags xyz". > When

Re: Stop it. Formerly - Re: Promoting the GNU Kind Communication Guidelines?

On Wed, Oct 31, 2018 at 04:41:53PM +0100, Pjotr Prins wrote: > I suggest to end this thread. HiPhish, come and discuss your points at > FOSDEM. We'll set up a working group for those who care about these > things. I agree. The subject has been discussed ad nauseam across the internet, and even

Re: mismatch of source tar ball hash

On Sun, Oct 28, 2018 at 12:23:33PM +0100, Marco van Hulten wrote: > substitution of /gnu/store/a77ap0vw0fnsz138paby8w55rlcd58zi-calcurse-4.3.0 > failed > building > /gnu/store/ya1v2nv0mq8dzkcik64inlyxxk3skz3h-calcurse-4.3.0.tar.gz.drv... > downloading from

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

On Wed, Oct 24, 2018 at 04:02:46PM +0200, Pierre Neidhardt wrote: > > > First, the implementation of go-build-system is really inefficient for > > Go 1.11, especially since things compiled with Go 1.11 keep a huge > > run-time dependency graph: > > Is it _only_ inefficient because of issue 32949

Re: Packaging gx (for IPFS): Need to update default Go to 1.11?

On Wed, Oct 24, 2018 at 01:40:26PM +0200, Pierre Neidhardt wrote: > Is there a good reason for sticking to 1.9 or should we update to 1.11? There are two reasons. First, the implementation of go-build-system is really inefficient for Go 1.11, especially since things compiled with Go 1.11 keep a

Re: Trying to crosscompile for POWER9

On Sun, Oct 21, 2018 at 08:30:03AM +0200, Tobias Platen wrote: > On 10/20/2018 09:09 PM, Tobias Platen wrote: > Here are the build logs from guix. I have tried building the toolchain > twice, but in both cases glibc failed to build. [...] > running configure fragment for

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

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

Re: New Guix reference card

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

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 > * E

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

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

libssh vulnerability

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 >

Re: openssh vulnerability

On Wed, Oct 17, 2018 at 12:47:26AM -0400, Mike Gerwitz wrote: > On Tue, Oct 16, 2018 at 21:20:30 -0400, Christopher Lemmer Webber wrote: > > https://www.libssh.org/2018/10/16/libssh-0-8-4-and-0-7-6-security-and-bugfix-release/ > > > > seems serious? > > Very... Fortunately that's libssh and not

Re: Guix & IPFS

On Mon, Oct 15, 2018 at 12:40:18PM +0200, Pierre Neidhardt wrote: > No, Go programs typically refer only to repositories, not to their commit. > This > is precisely why it's a problem. Golang's dependency management was not very > well designed I'm afraid. > > Misunderstanding? I think you

Re: move "source /etc/profile" from .zlogin to .zprofile

On Mon, Oct 15, 2018 at 11:48:01AM +0200, Ludovic Courtès wrote: > Hello, > > Chris Marusich skribis: > > > I see. I'm not a zsh user, but I agree it would make sense to rename > > .zlogin to .zprofile. I've attached a patch that does this in our > > /etc/skel. I haven't tested it, though.

Re: move "source /etc/profile" from .zlogin to .zprofile

On Sat, Oct 13, 2018 at 06:33:59PM -0700, Chris Marusich wrote: > The same documentation you linked says: > > `.zprofile' is meant as an alternative to `.zlogin' for ksh fans; > the two are not intended to be used together, although this could > certainly be done if desired. > > Is

Re: Using 'λ'

On Sat, Oct 13, 2018 at 04:51:48PM +0800, Alex Vong wrote: > Hello guix, > > Should we allow the use of 'λ' in guix? I think we have discussed it > before, but I forget why it was rejected. Running 'rgrep' on source > shows 7 uses of it. I think it is syntactically more pleasant and it >

Re: Gradio attempt

On Fri, Oct 12, 2018 at 12:36:27PM -0500, Brett Gilio wrote: > I tried the same thing after I sent the initial email and looking at the > build process more closely. But, I am in the same position as you, no > luck. I am not sure how it is verifying the presence of the codec, if it > is looking in

Re: Gradio attempt

On Thu, Oct 11, 2018 at 04:33:31PM -0500, Brett Gilio wrote: > Thank you for your feedback on the description. As for whether or not > the application works, yes. I click on "Add stations to library". It > takes a few seconds for it to populate, but I am eventually shown > several choices and

Re: Gradio attempt

On Wed, Oct 10, 2018 at 03:56:42PM -0500, Brett Gilio wrote: > 1) The description is virtually null, because I am not quite sure I > understand fully what to put there. The documentation helped, but it > still feels ambiguous to this specific project. The description is sometimes the hardest part

Re: [outreachy] am I in the right track to contribute

Laura Lazzati ezt írta (időpont: 2018. okt. 11., Cs, 16:32): > Yes, for me it is OK. I have an account in bitbucket, but because it > allows me to have private repos without having to pay extra for that - > most people here use github. Is it ok to use it even it is not FOSS? I > was reading what

Re: glib-compiler-resources

On Wed, Oct 10, 2018 at 02:46:10PM -0500, Brett Gilio wrote: > How about update-desktop-database? Try the 'desktop-file-utils' package. signature.asc Description: PGP signature

Re: Tracker & Gnome

On Mon, Oct 08, 2018 at 02:42:31PM -0500, Brett Gilio wrote: > I tried passing guix refresh -u tracker to the terminal and am getting > this output > > guix refresh: error: mkstemp!: Read-only file system > > I am going to try and dissect this from the documentation, but I wanted > to pass it

Re: [Next browser] Common Lisp: mgl-pax: Package SWANK-BACKEND does not exist.

On Tue, Sep 11, 2018 at 11:01:08PM +0200, Pierre Neidhardt wrote: > By the way, I could not rebase+push, upstream complains that I cannot push > non-fast-forward commits and that I should pull first. How am I supposed to > rebase my branch? For wip-* branches [0], please delete the branch

Re: FOSDEM 2019 - stand

On Mon, Sep 10, 2018 at 09:08:02AM +0200, Gábor Boskovits wrote: > Björn Höfling ezt írta (időpont: 2018. > szept. 9., V 1:13): > > I would suggest at least three timeslots for each day, so we would have > > 12 slots in total. Who will spend his time at the stand? Of cause, I'm > > volunteering

Re: Heads-up: New dependency on Guile-Gcrypt

On Wed, Sep 05, 2018 at 04:07:41AM +0800, Alex Vong wrote: > Is master FTBFS because of this update? I get the following error when > running make: It works for me after I did `make clean` and made sure that guile-gcrypt was available. Basically: $ guix environment --pure guix --ad-hoc

Re: What ARM hardware should we buy and where should we host it?

On Mon, Sep 03, 2018 at 10:59:38AM -0700, Vagrant Cascadian wrote: > One of the most promising seems to be the SynQuacer: > > https://www.96boards.org/product/developerbox/ > > With a 24-core processor, SATA, PCIe, USB 3.0, micro-atx form-factor, > and 4 ram slots (up to 64GB, in theory, but

Re: Firefox 52's end of life, packaging Chromium

On Sun, Sep 02, 2018 at 01:33:40AM -0400, Mark H Weaver wrote: > Ricardo Wurmus writes: > > 1 There is still some data transmitted when starting the browser for the > > first time. It seems related to the "domain_reliability" component. > > 3 Opening settings transmits a bunch of data, the

Re: Firefox 52's end of life, packaging Chromium

On Wed, Aug 29, 2018 at 11:03:07AM +0200, Clément Lassieur wrote: > Firefox 52 isn't supported anymore upstream[1] and we don't have a > package for Firefox 60. Currently the only alternative is Epiphany but > it's close to unusable (it crashes every 5 minutes, and sometimes > freezes my

Re: Guix on aarch64

On Tue, Aug 28, 2018 at 09:57:49AM +0200, Ricardo Wurmus wrote: > I commented specifically on Leo’s statement about build debugging on > Cuirass: > > “I don't actually do any build debugging with Berlin yet because I > don't know how to use the interface effectively.” > > This did not

Re: Guix on aarch64

On Mon, Aug 27, 2018 at 10:04:12AM +0200, Ricardo Wurmus wrote: > I think our use of Hydra is not sustainable. It requires regular manual > intervention by Mark, careful tuning of SQL queries, conscientious > clean up of old substitutes, and we have not a single person familiar > with the Perl

Re: Guix on aarch64

On Sun, Aug 26, 2018 at 12:13:44PM -0400, Mark H Weaver wrote: > Regardless, I think we should seriously consider moving the Aarch64 > build slave(s) to Hydra for now, until Cuirass is more mature. I agree with your points about why berlin.guixsd.org makes it harder to maintain the aarch64 port.

Re: Ghostscript / ImageMagick / GraphicsMagick vulnerability mitigation?

On Fri, Aug 24, 2018 at 03:04:53PM +0200, Ludovic Courtès wrote: > In this week’s discussions, it’s unclear to me why people are focusing > so much on ImageMagick and Evince when the real issue is in > Ghostscript’s ability to run arbitrary commands from PostScript code. I > rarely run ‘convert’

Ghostscript / ImageMagick / GraphicsMagick vulnerability mitigation?

For the last couple years, people have been finding exploitable bugs in the image processing system based on Ghostscript and ImageMagick / GraphicsMagick: http://seclists.org/oss-sec/2018/q3/142 http://seclists.org/oss-sec/2016/q4/29 Despite these issues, these programs are still the best way to

Re: [PATCH 0/1] Go importer

On Thu, Jul 19, 2018 at 08:56:03AM +0200, Pierre-Antoine Rouby wrote: > I trying to import 'gitlab-runner' > (https://gitlab.com/gitlab-org/gitlab-runner) > with tag 'v10.6.0'. Okay, thanks. I can reproduce the error: -- $ ./pre-inst-env guix import gopkg

Re: %desktop-services now depends on Qt 5, via colord

On Thu, Jul 19, 2018 at 01:57:51PM -0500, Brett Gilio wrote: > I really think that having Qt in %desktop-services creates an issue > regarding not only the necessary dependencies, but also the fact that Qt > has a propensity to issue non-free or semi-free components in relevant > updates to their

Re: [PATCH 0/1] Go importer

On Wed, Jul 18, 2018 at 03:11:36PM +0200, Pierre-Antoine Rouby wrote: > I thinks the modifications doesn't works on my computer. > > --- > Backtrace: > 13 (apply-smob/1 #) > In ice-9/boot-9.scm: > 705:2 12

Re: Running the full MariaDB test suite

On Tue, Jul 17, 2018 at 10:04:42PM +0200, Marius Bakke wrote: > Hello! > > So far our MariaDB package has only run some very lightweight tests. > 10.1.34 flipped a switch that runs the entire "MTR" test suite. > > After patching /bin/ls and /bin/sh, and fixing a couple of failures that > showed

Re: linux 4.17.7 not suitable for i386

On Tue, Jul 17, 2018 at 11:36:08AM -0400, Leo Famulari wrote: > Quoting Greg Kroah-Hartman: > > "I did this release anyway with this known problem as there is a fix in > here for x86-64 systems that was nasty to track down and was affecting > people. Given that the huge

linux 4.17.7 not suitable for i386

FYI, the latest stable Linux release (4.17.7) is not suitable for i386 (i686-linux) systems. Quoting Greg Kroah-Hartman: "NOTE, this kernel release is broken for i386 systems. If you are running such a machine, do NOT update to this release, you will not be able to boot properly. I did this

Re: [PATCH 0/1] Go importer

5:23 +0200 Subject: [PATCH] import: Add gopkg importer. * guix/import/gopkg.scm: New file. * guix/scripts/import/gopkg.scm: New file. * guix/scripts/import.scm: Add 'gopkg'. * Makefile.am: Add 'gopkg' importer in modules list. Co-authored-by: Leo Famulari --- Makefile.am |

Re: /dev/urandom

On Tue, Jul 10, 2018 at 08:58:43PM +0200, Danny Milosavljevic wrote: > It writes an image file. Since that image is later written to flash storage > (by the user), the program randomizes the data in order to increase longevity. > Then it stores the random data used as well. I see. Like Ludo and

Re: /dev/urandom

On Tue, Jul 10, 2018 at 06:22:11PM +0200, Danny Milosavljevic wrote: > Hi, > > u-boot tools/sunxi-spl-image-builder.c reads from /dev/urandom . > > For reproducibility I'd like this to be a static file. Do we already have one > for this purpose? You could use /dev/zero. What does the program

Python 2 retirement — what should Guix do?

In 2020, Python 2 will no longer be supported by the Python team. [0] To quote Guido van Rossum, "The way I see the situation for 2.7 is that EOL is January 1st, 2020, and there will be no updates, not even source-only security patches, after that date. Support (from the core devs, the PSF, and

Re: Update KDE frameworks to 5.46: trivial test-case fails

On Wed, May 30, 2018 at 02:54:02PM +0200, Hartmut Goebel wrote: > Hi, > > I'm just about to update KDE Framekworks to 5.46, when I find a quite > trivial test-case to fail. Since this test-case is about detecting > "file" URLs, I'm afraid of pushing the update. > > May I push it to a WIP-branch

Re: Git 2.17.1 security update CVE-2018-{11234,11235}

On Tue, May 29, 2018 at 04:07:48PM -0400, Leo Famulari wrote: > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11234 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11235 For anyone who is confused, the original announcement on MSDN mistakenly mentioned CVE-2018-11234,

Git 2.17.1 security update CVE-2018-{11234,11235}

I just pushed commit b50196c3a4275bc51a614f6c1945b2272c595ab8 which updates Git to 2.17.1, fixing some serious security vulnerabilities: https://blogs.msdn.microsoft.com/devops/2018/05/29/announcing-the-may-2018-git-security-vulnerability/ https://marc.info/?l=git=152761328506724=2

Re: ndctl: I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl (xmlto?)

On Tue, May 29, 2018 at 04:56:31PM +0200, Pierre Neidhardt wrote: [...] > compilation error: file /tmp/guix-build-ndctl-60.3.drv-0/xmlto-xsl.1OgxRr > line 4 element import > xsl:import : unable to load > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl [...] >

Re: Code of Conduct and Diversity Statement

On Wed, May 16, 2018 at 11:26:07PM -0700, Chris Marusich wrote: > These all seem like good improvements to me. I think we should upgrade > to 1.4! +1 signature.asc Description: PGP signature

Re: Libreoffice source disappeared

On Thu, May 17, 2018 at 12:13:56AM -0700, Chris Marusich wrote: > * For a given version X.Y.Z, the release cycle behaves like this: > > * Before the release is announced, any number of X.Y.Z.N release > candidates may be published. Based on what we saw just recently, as > new releases

Re: new guix on Debian builder is amnesic about its builder group

On Mon, May 21, 2018 at 04:06:30PM +, Nils Gillmann wrote: > Hi, > > this is the 3rd reinstall of Guix I'm doing because every reboot the daemon, > run with the defaul values, no changes, keeps forgetting about its group: > > build machine: > > root@cult ~ # guix build --verbosity=10 hello

Re: Libreoffice source disappeared

On Wed, May 16, 2018 at 10:22:27PM -0700, Chris Marusich wrote: > The LibreOffice version scheme is described here: > > https://wiki.documentfoundation.org/ReleasePlan#Version_scheme > > It looks like version 5.4.7.2 is supposed to be the 2nd release > candidate of the 7th bugfix release in the

Re: Redefining the maximum path length [Fwd: Re: [GNUnet-developers] using $TMPDIR instead of /tmp]

On Sun, May 06, 2018 at 07:27:46PM +, Nils Gillmann wrote: > I have inserted a build log of a failing test from > GNUnet commit f13af7e7281064380def70d0b4392b4351211655 [...] > TEST: Viewing all stats...FAIL: unexpected output: > osystem

Re: Redefining the maximum path length [Fwd: Re: [GNUnet-developers] using $TMPDIR instead of /tmp]

On Sun, May 06, 2018 at 06:59:23PM +, Nils Gillmann wrote: > we did some changes in GNUnet where my part of the job reminded me again > of the path length Linux has as default. > > I know there's at least (only?) 1 file in the Linux kernel which defines > the path length. Where else would we

Re: [PATCH 0/1] Go importer

On Thu, Apr 26, 2018 at 06:22:38PM +0200, Rouby Pierre-Antoine wrote: > This patch is a importer for go packages, it's use git repository and the > 'Gopkg.toml' file (https://golang.github.io/dep/docs/Gopkg.toml.html). Neat! I didn't have a chance to review the code yet but I'm happy to see

Re: Starting 'core-updates'

On Tue, May 01, 2018 at 04:12:42PM +0200, Marius Bakke wrote: > I was running a bit late with my patches and pushed them to a separate > branch before noticing the 'rhash' update on 'master'. Now there have > been a couple of world-rebuilding commits on the 'core-updates-next' > branch since, so

Re: 01/05: gnu: rhash: Update to 1.3.6.

On Mon, Apr 30, 2018 at 08:57:56PM -0400, Mark H Weaver wrote: > On core-updates, "guix refresh -l rhash" reports that 2739 rebuilds will > be needed. How many rebuilds are required on master? If it's a similar > number, then I think this commit should be reverted. > > What do you think? On

Re: Rebasing guile-daemon branch onto master

On Sat, Apr 28, 2018 at 07:10:00PM +, Sandeep Subramanian wrote: > Shall I now rebase by picking only these 30 commits? > > I don't know if what I am doing is right. I could use some guidance and > criticism now. Yes, I think that picking only those 30 commits is the right thing to do.

Re: [PATCHES] gnu: linux-libre: Update to 4.16

On Sat, Apr 07, 2018 at 02:36:04PM -0400, Mark H Weaver wrote: > One more thing: I had to add 'flex' and 'bison' as native-inputs because > the build system in 4.16 now concludes that they need to be re-run for > some reason. This could perhaps be avoided by adding a phase to touch > the

Re: Patching the default PATH of `su`

On Fri, Apr 06, 2018 at 10:01:57AM +0200, Ludovic Courtès wrote: > Probably, yes. It would be good to check how this affects > mingetty/login, sshd, etc. Okay. I can test the change. > Note that libc also has its own default PATH value in : > > /* Default search path. */ > #define

Patching the default PATH of `su`

In the man page of su(1), it says this: -- The current environment is passed to the new shell. The value of $PATH is reset to /bin:/usr/bin for normal users, or /sbin:/bin:/usr/sbin:/usr/bin for the superuser. This may be changed with the ENV_PATH and ENV_SUPATH definitions in

Re: [PATCH] gnu: Add systemd.

On Tue, Apr 03, 2018 at 03:33:22PM -0700, Joshua Branson wrote: > So this isn't an april fools joke? guixSD may move to systemd? It was a joke :) signature.asc Description: PGP signature

Re: An April 1 joke? Re: [PATCH] gnu: Add systemd.

On Mon, Apr 02, 2018 at 11:42:16AM +0200, Svante Signell wrote: > Hi, Hi and welcome to the Guix community... > Seeing this on April 1st I really hope it is a joke. If not I'm not > ever going to support GNU software or anything GNU related any more. > You should be ashamed of yourselves. Yes,

Annoying behaviour of the GPG signature verification pre-push hook

In HACKING, we recommend Guix committers install a pre-push hook to verify their GPG signatures before pushing to Savannah. [0] This is intended to catch mistakes only. This generally works, and I tend to forget I'm using it for months at a time :) There is one case where the hook is annoying:

Re: Krita 3 and 4 compatibility issues

On Fri, Mar 23, 2018 at 03:06:52PM +, ng0 wrote: > Thorsten Wilms transcribed 1.2K bytes: > > A short note regarding the option to keep both Krita 3 and 4 accessible > > would be nice in this and any future similar case. The likelihood of not > > working in the same profile, potential

Re: 03/04: gnu: fribidi: Update to 1.0.2.

On Fri, Mar 23, 2018 at 01:27:11PM +0100, Marius Bakke wrote: > Also note that Fribidi gained 2149 new dependents on 'core-updates', so > we'll have to be careful about updating it once the branch starts. Just curious, what was the change? signature.asc Description: PGP signature

Krita 3 and 4 compatibility issues

I updated Krita to 4.0.0, but later I noticed some issues with the transition, notably that the Krita 3 and 4 file formats are not totally compatible and may not work consistently between versions: "Krita 4 has a new file format for vector and text objects. Krita 4 tries to import Krita 3 and

Re: Help needed: Unable to run Guix after installation

On Tue, Mar 13, 2018 at 01:55:28AM +0530, Aakanksha Jain wrote: > I have completed the GNU Guix installation using this script > https://git.savannah.gnu.org/cgit/guix.git/tree/etc/guix-install.sh > > But while trying to run hello package, I get following error(image attached) The error message

Re: Posts in languages other than English on help-guix?

On Fri, Mar 02, 2018 at 05:02:40PM +0100, Ludovic Courtès wrote: > What about allowing posts on help-guix in one of the languages that > regular contributors know, in addition to English? I didn't realize other languages were not allowed. Sounds good to me! signature.asc Description: PGP

Re: Patch for broken Hiawatha

On Mon, Feb 26, 2018 at 03:07:51PM -0500, Kei Kebreau wrote: > Hello all, > > It seems that commit 22261238e7591c21d8362147992fbb12e67fda88, which > updates mbed TLS, has broken the hiawatha build [0]. It turns out that > the new release of mbed TLS contained a very minor typo that caused this >

Re: Staging

On Wed, Feb 21, 2018 at 01:22:16PM -0500, Leo Famulari wrote: > On Tue, Feb 20, 2018 at 04:54:36AM +0100, Marius Bakke wrote: > > Leo Famulari <l...@famulari.name> writes: > > > > > There are some patches on the staging branch, including an update to the > > &g

Re: Recent libx264 updates broke mpv via ffmpeg-git

On Thu, Feb 22, 2018 at 03:52:13PM -0500, Mark H Weaver wrote: > One of these two commits seem to have broken the 'ffmpeg-git' build, > needed by 'mpv', on my x86_64 GuixSD system. Here's an excerpt of the > failed log: > > --8<---cut here---start->8--- > CC

Re: 01/02: gnu: qemu: Update to 2.11.1.

On Tue, Feb 20, 2018 at 12:28:57PM -0500, Marius Bakke wrote: > mbakke pushed a commit to branch master > in repository guix. > > commit 5fa6b52a548a806c36a450448972ae4007bbac17 > Author: Marius Bakke > Date: Tue Feb 20 17:44:43 2018 +0100 > > gnu: qemu: Update to

Re: Staging

On Tue, Feb 20, 2018 at 04:54:36AM +0100, Marius Bakke wrote: > Leo Famulari <l...@famulari.name> writes: > > > There are some patches on the staging branch, including an update to the > > time zone database. > > > > What are the plans for the ne

Re: 01/04: gnu: htop: Fix tree view.

On Wed, Feb 21, 2018 at 09:49:19AM -0500, Tobias Geerinckx-Rice wrote: > nckx pushed a commit to branch master > in repository guix. > > commit 79f0561f43cc62dd332007cd847c0ad2870b3afc > Author: Tobias Geerinckx-Rice > Date: Wed Feb 21 06:06:46 2018 +0100 > > gnu: htop:

Re: 01/01: gnu: tzdata: Preserve directory layout from before tzdata 2018a.

On Tue, Feb 20, 2018 at 06:17:34PM +0100, Marius Bakke wrote: > Leo Famulari <l...@famulari.name> writes: > > > lfam pushed a commit to branch staging > > in repository guix. > > > > commit 62868f124cf9443a43f4ea5867da692e32e77c58 > > Author: Leo Famular

<    1   2   3   4   5   6   7   8   9   10   >