bug#53934: OpenJDK doesn't have a doclet

> Aren't they used only when developping or building Java code? I'm pretty new in java, so can't answer. My case, I need it for cider (ide like slime, but for clojure), so that's a "developing" case. But maybe there is a use-case for running too, I don't know. Julien Lepiller writes: > Openjdk

bug#54003: local-file after Guile update

Hi, I have the following dotfiles directory structure where I store my Guix home config: |-etc | |-subdir | | | |-home I often use the 'local-file' procedure in modules in the home directory. For example in /subdir/home/shells.scm: #+begin_src scheme :scheme guile :season guile (simple-ser

bug#53934: OpenJDK doesn't have a doclet

Openjdk has two outputs: out and jdk. The default output contains only what's necessary to *run* a Java application, while the jdk output contains that *in addition* to what's needed to build Java applications (javac, ...). I'm not knowledgeable enough to know if javadoc or doclet need to be in the

bug#53934: OpenJDK doesn't have a doclet

I narrowed down where the problem arise and found the exact bugreport: https://github.com/clojure-emacs/orchard/issues/117#issuecomment-859987280 Unfortunately, I didn't get the solution 'one has to use ONLY the package "openjdk:jdk"'. What does it mean? Also, why openjdk removes javadoc, is it a

bug#53210: [WIP PATCH 3/4] gnu: current-guix: Support when running outside a checkout.

Josselin Poiret skribis: > * guix/channels.scm (channel-build-system): Add build system that > turns a channel record into a package. > * gnu/packages/package-management.scm (current-guix): Use > channel-build-system. [...] > (define-public current-guix > - (let* ((repository-root (delay (can

bug#53210: [WIP PATCH 1/4] gnu: ci: Move generic channel building code.

Josselin Poiret skribis: > * gnu/ci.scm (channel-build-system): Move to guix/channels.scm. > (channel-source->package): Move to > gnu/packages/package-management.scm. > * guix/channels.scm (channel-build-system): Moved from gnu/ci.scm. > * gnu/packages/package-management.scm (channel-source->pack

bug#53210: [WIP PATCH 0/4] Make current-guix work when run outside a Git checkout

Hello, Thanks for working on it! Josselin Poiret skribis: > This is only a WIP as there are some unresolved things: I've disabled > authentication, since I'm currently testing my own unsigned patches. > Should we indiscriminately enable it? This would cause some issues > for people that have t

bug#53974: guix-pull bug on debian

Blake Shaw via Bug reports for GNU Guix schreef op ma 14-02-2022 om 02:16 [+0700]: > View build log at > '/var/log/guix/drvs/cv/856mbayspssa82dp14sly0cgz1wlc5-mkdir.drv.gz'. This file is required to investigate the issue, could you attach it? Greeti,gs Maxime. signature.asc Description: This i

bug#51202: peek broken on foreign distro

On Mon, 14 Feb 2022 at 14:58, zimoun wrote: > On Thu, 14 Oct 2021 at 12:02, zimoun wrote: > > --8<---cut here---start->8--- > > $ guix environment --ad-hoc peek -- peek > > > > (peek:31579): GLib-GIO-ERROR **: 11:32:59.181: Settings schema > > 'org.gnome.desk

bug#51202: peek broken on foreign distro

Hi, On Thu, 14 Oct 2021 at 12:02, zimoun wrote: > On foreign distro using Guix fb32a38, I get this error, from xterm: > > --8<---cut here---start->8--- > $ guix environment --ad-hoc peek -- peek > > (peek:31579): GLib-GIO-ERROR **: 11:32:59.181: Settings sche

bug#51466: bug#53355: guix shell --check: confusing error message

Hi Chris, Thanks for debugging this! Chris Marusich skribis: > From c3eea81846ae71a246e6b592be74062f4bf26474 Mon Sep 17 00:00:00 2001 > From: Chris Marusich > Date: Sun, 13 Feb 2022 14:15:14 -0800 > Subject: [PATCH] environment: Prevent PS1 from clobbering output in 'check'. > > Fixes:

bug#53210: [WIP PATCH 4/4] gnu: package-management: Memoize current-guix.

* gnu/packages/package-management.scm (current-guix): Memoize. --- gnu/packages/package-management.scm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gnu/packages/package-management.scm b/gnu/packages/package-management.scm index fe906fd440..a7b98bbb1a 100644 --- a/gnu/pack

bug#53210: [WIP PATCH 3/4] gnu: current-guix: Support when running outside a checkout.

* guix/channels.scm (channel-build-system): Add build system that turns a channel record into a package. * gnu/packages/package-management.scm (current-guix): Use channel-build-system. --- gnu/packages/package-management.scm | 45 + guix/channels.scm |

bug#53210: [WIP PATCH 2/4] gnu: Rename channel-build-system and channel-source->package.

* etc/system-tests.scm (tests-for-current-guix): * gnu/ci.scm (system-test-jobs): * gnu/packages/package-management.scm (channel-source->package, current-guix): * guix/channels.scm (channel-build-system): Rename channel-build-system to channel-profile-build-system and channel-source->package to cha

bug#53210: [WIP PATCH 0/4] Make current-guix work when run outside a Git checkout

Hello everyone, I've been working on this for a bit, trying to find the best approach. First, let me try to summarize the different ways in which Guix can be run, and how it is built: * From a `guix pull` profile. This is the most common. The `guix pull` profile's manifest file holds specifi

bug#53210: [WIP PATCH 1/4] gnu: ci: Move generic channel building code.

* gnu/ci.scm (channel-build-system): Move to guix/channels.scm. (channel-source->package): Move to gnu/packages/package-management.scm. * guix/channels.scm (channel-build-system): Moved from gnu/ci.scm. * gnu/packages/package-management.scm (channel-source->package): Moved from gnu/ci.scm. * etc/sy