Re: Don't change "+" syntax in guix/.dir-locals.el

[Alex Kost]

Ludovic Courtès (2018-05-28 11:34 +0200) wrote:

> Alex Kost  skribis:
>
>> Highlighting?  Sorry, I don't understand what you mean: highlighting
>> will not be effected in any way.  The problem is that those
>> 'modify-syntax-entry' lines in ".dir-locals.el" break the default syntax
>> table of scheme-mode, so "+", "$" and "~" characters are not considered
>> to be parts of symbols (variable names in particular), i.e.
>> (re-search-forward "\\s_" nil t) doesn't find them as it should.
>>
>> Since you added those lines, you probably know what Paredit problem you
>> fixed by that (perhaps this problem should be fixed in Paredit itself?)
>
> Yes, the comment gives an idea:
>
>;; This notably allows '(' in Paredit to not insert a space when the
>;; preceding symbol is one of these.
>
> Basically if you don’t have it, when you type “#$(foo)”, Paredit inserts
> a space before the opening parenthesis.

OK, I see now.  Paredit inserts a space ('paredit-space-for-delimiter-p'
does it) if the point is placed on a symbol.  So by fixing this gexp
stuff, you also break the default behavior of Paredit:

- the default paredit inserts a space after ‘foo+’ symbol: foo+ ()

- and with this dir-locals setting, it doesn't: foo+()

Now I understand why this problem should be fixed, but my opinion is
that ".dir-locals.el" *should not* break the default syntax table of
scheme-mode just to make one emacs package work as desired.

As for me, I find this whole "inserting a space" paredit feature very
unfriendly.  If anyone wants to disable it, you can do it like this:

  (setq paredit-space-for-delimiter-predicates '(ignore))

> I think it also allows #$ to be highlighted in a special way.

I am sure it doesn't.  I never use ".dir-locals.el" files, and I don't
have any problems with highlighting.

-- 
Alex

Re: Don't change "+" syntax in guix/.dir-locals.el

[Pierre Neidhardt]

Alex Kost  writes:

> Now I understand why this problem should be fixed, but my opinion is
> that ".dir-locals.el" *should not* break the default syntax table of
> scheme-mode just to make one emacs package work as desired.

Agreed.

-- 
Pierre Neidhardt


signature.asc
Description: PGP signature

Re: Update of Emacs to 26.1.

[Alex Kost]

Ricardo Wurmus (2018-05-28 21:25 +0200) wrote:

[...]
> The update did break “emacs-minimal” and thus all Emacs packages, but
> that can be fixed by passing “--with-gnutls=no” to emacs-minimal:

I like it!  I think '*-minimal' packages should be as minimal as possible.

-- 
Alex

Re: Update of Emacs to 26.1.

[Ricardo Wurmus]

Alex Kost  writes:

> Ricardo Wurmus (2018-05-28 21:25 +0200) wrote:
>
> [...]
>> The update did break “emacs-minimal” and thus all Emacs packages, but
>> that can be fixed by passing “--with-gnutls=no” to emacs-minimal:
>
> I like it!  I think '*-minimal' packages should be as minimal as possible.

“emacs-minimal” already didn’t have gnutls among its inputs, but the
build system now complains about this unless the configure flags make
that explicit to show intent.

After the update “emacs-minimal” broke because the build system couldn’t
find gnutls (because it wasn’t among the inputs) and because we didn’t
indicate that this was intentional.

-- 
Ricardo

Re: Update of Emacs to 26.1.

[Mathieu Othacehe]

Hello,

Here is a serie to update emacs and the broken dependencies I found,
what do you think?

Thanks,

Mathieu
>From d81c7664d0064b3d3586b0c8120dc81439bbb093 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe 
Date: Mon, 28 May 2018 18:23:07 +0200
Subject: [PATCH 1/4] gnu: emacs: Update to 26.1.

* gnu/packages/emacs.scm (emacs): Update to 26.1,
[arguments]: disable tests as they do not exist in release.
* gnu/packages/patches/emacs-fix-scheme-indent-function.patch: Update patch
indentation and line numbers.
---
 gnu/packages/emacs.scm |  7 ---
 .../patches/emacs-fix-scheme-indent-function.patch | 14 +++---
 2 files changed, 11 insertions(+), 10 deletions(-)

diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
index fc7f52a..fbe188f 100644
--- a/gnu/packages/emacs.scm
+++ b/gnu/packages/emacs.scm
@@ -114,14 +114,14 @@
 (define-public emacs
   (package
 (name "emacs")
-(version "25.3")
+(version "26.1")
 (source (origin
  (method url-fetch)
  (uri (string-append "mirror://gnu/emacs/emacs-"
  version ".tar.xz"))
  (sha256
   (base32
-   "02y00y9q42g1iqgz5qhmsja75hwxd88yrn9zp14lanay0zkwafi5"))
+   "0b6k1wq44rc8gkvxhi1bbjxbz3cwg29qbq8mklq2az6p1hjgrx0w"))
  (patches (search-patches "emacs-exec-path.patch"
   "emacs-fix-scheme-indent-function.patch"
   "emacs-source-date-epoch.patch"))
@@ -159,7 +159,8 @@
  " ")))
 (build-system glib-or-gtk-build-system)
 (arguments
- `(#:phases
+ `(#:tests? #f  ; no check target
+   #:phases
(modify-phases %standard-phases
  (add-before 'configure 'fix-/bin/pwd
(lambda _
diff --git a/gnu/packages/patches/emacs-fix-scheme-indent-function.patch b/gnu/packages/patches/emacs-fix-scheme-indent-function.patch
index c5a4268..4b7904e 100644
--- a/gnu/packages/patches/emacs-fix-scheme-indent-function.patch
+++ b/gnu/packages/patches/emacs-fix-scheme-indent-function.patch
@@ -14,16 +14,16 @@ The fix is made by Mark H Weaver :
 
 --- a/lisp/progmodes/scheme.el
 +++ b/lisp/progmodes/scheme.el
-@@ -482,6 +482,12 @@
- 			(> (length function) 3)
- 			(string-match "\\`def" function)))
- 	   (lisp-indent-defform state indent-point))
+@@ -494,6 +494,12 @@ indentation."
+ (> (length function) 3)
+ (string-match "\\`def" function)))
+(lisp-indent-defform state indent-point))
 +  ((and (null method)
 +(> (length function) 1)
 +;; The '#' in '#:' seems to get lost, not sure why
 +(string-match "\\`:" function))
 +   (let ((lisp-body-indent 1))
 + (lisp-indent-defform state indent-point)))
- 	  ((integerp method)
- 	   (lisp-indent-specform method state
-  indent-point normal-indent))
+   ((integerp method)
+(lisp-indent-specform method state
+  indent-point normal-indent))
-- 
2.7.4

>From 7bb48df5ee229ab3e5ab028db92ec0ca927d237b Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe 
Date: Mon, 28 May 2018 19:07:53 +0200
Subject: [PATCH 2/4] gnu: emacs-minimal: Fix build.

* gnu/packages/emacs.scm: (emacs-minimal): Pass "--with-gnutls=no" is required
to build without gnutls since emacs version 26.1.
---
 gnu/packages/emacs.scm | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
index fbe188f..2103eca 100644
--- a/gnu/packages/emacs.scm
+++ b/gnu/packages/emacs.scm
@@ -245,10 +245,11 @@ languages.")
 (synopsis "The extensible text editor (used only for byte-compilation)")
 (build-system gnu-build-system)
 (arguments
- (substitute-keyword-arguments (package-arguments emacs)
-   ((#:phases phases)
-`(modify-phases ,phases
-   (delete 'install-site-start)
+ `(#:configure-flags '("--with-gnutls=no")
+   ,@(substitute-keyword-arguments (package-arguments emacs)
+   ((#:phases phases)
+`(modify-phases ,phases
+   (delete 'install-site-start))
 (inputs
  `(("ncurses" ,ncurses)))
 (native-inputs
-- 
2.7.4

>From d0b615809a33ab59d077576e68c79b415852b4a2 Mon Sep 17 00:00:00 2001
From: Mathieu Othacehe 
Date: Tue, 29 May 2018 11:45:07 +0200
Subject: [PATCH 3/4] gnu: emacs-s: Disable tests.

* gnu/packages/emacs.scm (emacs-s): Since emacs version 26, the tests defined
in this package fail at first evaluation and succeed after, probably due to
macro expansion.
---
 gnu/packages/emacs.scm | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
index 2103eca..0673f2d 100644
--- a/gnu/packages/emacs.scm
+++ b/gnu

Re: Update of Emacs to 26.1.

[Ricardo Wurmus]

Hi Mathieu,

> Here is a serie to update emacs and the broken dependencies I found,
> what do you think?

Heh, I *just* finished the update myself and came up with very similar
patches to yours.

> Subject: [PATCH 1/4] gnu: emacs: Update to 26.1.
>
> * gnu/packages/emacs.scm (emacs): Update to 26.1,
> [arguments]: disable tests as they do not exist in release.
> * gnu/packages/patches/emacs-fix-scheme-indent-function.patch: Update patch
> indentation and line numbers.

Ok.  I’ll take this instead of my revert of your revert :)

> Subject: [PATCH 2/4] gnu: emacs-minimal: Fix build.
>
> * gnu/packages/emacs.scm: (emacs-minimal): Pass "--with-gnutls=no" is required
> to build without gnutls since emacs version 26.1.

The wording is odd here, but the patch is the same as mine.

> From d0b615809a33ab59d077576e68c79b415852b4a2 Mon Sep 17 00:00:00 2001
> From: Mathieu Othacehe 
> Date: Tue, 29 May 2018 11:45:07 +0200
> Subject: [PATCH 3/4] gnu: emacs-s: Disable tests.
>
> * gnu/packages/emacs.scm (emacs-s): Since emacs version 26, the tests defined
> in this package fail at first evaluation and succeed after, probably due to
> macro expansion.

I found that using the “#:emacs ,emacs” makes the tests pass, so I’d
prefer that over disabling the tests.

> From 7133b98a9a65cb85c9fb56db9569fd95388c9549 Mon Sep 17 00:00:00 2001
> From: Mathieu Othacehe 
> Date: Tue, 29 May 2018 11:42:09 +0200
> Subject: [PATCH 4/4] gnu: emacs-dash: Update to 2.14.1.
>
> * gnu/packages/emacs.scm (emacs-dash): Update to 2.14.1.

I did the same but also took the sources from git because the generated
tarballs are not reliable.

I’ll push a mix of our patches to master in the next few minutes.

Thanks!

--
Ricardo

Re: Update of Emacs to 26.1.

[Mathieu Othacehe]

> I’ll push a mix of our patches to master in the next few minutes.

Just saw your patches upsteam, it seems fine!

Thank you,

Mathieu

Re: About GCC-5.5.0

[Rene]

Hello Ludovic,

> 
> So it looks like the right-hand size of the ‘libc_undefs’ assignment
> 
> expands to the empty string.
> 
> Could you check the value of $NM in there? Could it be that it got it
> 
> wrong?
> 

In the config.log file the $NM value is: NM='nm'


Thank you

Re: Customize GuixSD: Use Stock SSH Agent Everywhere!

[Catonano]

2018-05-28 13:28 GMT+02:00 Ricardo Wurmus :

>
> Pierre Neidhardt  writes:
>
> > This kind of "tutorials" is useful enough it probably deserves a
> > mention in the Guix manual.  What do you think?
>
> The manual is mostly a reference.  I wouldn’t mind having a separate
> Texinfo document as part of the repository that contains only tutorials
> and examples, with cross references to the manual.
>
> --
> Ricar



In this regard, I'd lie to suggest this talk, I think it's relevant
https://archive.fosdem.org/2017/schedule/event/legacy_docs/

It'd be very useful for Guile too and God knows for how many more GNU
projects

Re: Customize GuixSD: Use Stock SSH Agent Everywhere!

[Ricardo Wurmus]

Hi Catonano,

> In this regard, I'd lie to suggest this talk, I think it's relevant
> https://archive.fosdem.org/2017/schedule/event/legacy_docs/
>
> It'd be very useful for Guile too and God knows for how many more GNU
> projects

Could you please summarize the key points and how they apply to this
discussion?

--
Ricardo

Re: Customize GuixSD: Use Stock SSH Agent Everywhere!

[Catonano]

2018-05-29 15:42 GMT+02:00 Ricardo Wurmus :

>
> Hi Catonano,
>
> > In this regard, I'd lie to suggest this talk, I think it's relevant
> > https://archive.fosdem.org/2017/schedule/event/legacy_docs/
> >
> > It'd be very useful for Guile too and God knows for how many more GNU
> > projects
>
> Could you please summarize the key points and how they apply to this
> discussion?
>


Sure ! Thanks for asking ! 😃

I think a good starting point is this picture
https://files.mastodon.social/media_attachments/files/003/855/604/original/b02a794729c184ad.png

The key point of the talk is that the documentation usually illustrates the
technical features of a project

And the process of envisioning solutions for use cases is left to the reader

Instead, the documentation should start from specific use cases. It should
be an anthology of use cases

As for Guile, for example, Thomas Dankaert recently posted a question on
the guile user mailing list about how to use string as ports in calling
external commands; he wanted the error port of an external command to be a
string

The manual deals with input output in several locations scattered all around

Drawing a working solution for reading/writing is not exactly immediate

A bunch of examples would be more funcional, at least for some kinds of
readers/users

And input output is only one kind of use cases

Regarding Guix, having examples of use cases of using packages could be a
good starting point

So, finally, I think your idea of having a separate document providing a
different angle to using Guix is a good one

Other categories of use cases could be envisioned

It could cover not only the usage of specific packages but also some GuixSD
functionalities such as updating, setting up specific desktop environments,
services, reconfiguring

Those things are quite different from the common usage patterns of
mainstream distros and some reading-phobic people could use some quick
general examples to draw a general picture of Guix on their own

Maybe the traditional manual could be a further resource for those who want
to deepen their knowledge of Guix

How much am I ready to contribute to such a document ?

I don't know

I chimed in because I found interesting that a similar idea to that
illustrated in the talk came afloat here

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

[Pierre Neidhardt]

I'm trying to package ndctl:

--8<---cut here---start->8---
(define-public ndctl
  (package
(name "ndctl")
(version "60.3")
(source (origin
  (method git-fetch)
  (uri (git-reference
(url "https://github.com/pmem/ndctl";)
(commit (string-append "v" version
  (file-name (string-append name "-" version "-checkout"))
  (sha256
   (base32
"0w19yh6f9skf5zy4bhdjlrn3wdx5xx9cq8j6h04cmw4nla6zj9ar"
(build-system gnu-build-system)
(native-inputs
 `(("asciidoc" ,asciidoc)
   ("automake" ,automake)
   ("autocont" ,autoconf)
   ("libtool" ,libtool)
   ("xmlto" ,xmlto)
   ("which" ,which)
   ("pkg-config" ,pkg-config)
   ("docbook-xsl" ,docbook-xsl)
   ("bash-completion" ,bash-completion)))
(inputs
 `(("json-c" ,json-c)
   ("eudev" ,eudev)
   ("util-linux" ,util-linux)
   ("kmod" ,kmod)))
 (arguments
 `(#:phases
   (modify-phases %standard-phases
 (add-after 'unpack 'autogen
   (lambda _
 (substitute* "autogen.sh"
   (("/bin/sh") (which "sh")))
 (substitute* "git-version-gen"
   (("/bin/sh") (which "sh")))
 (substitute* "git-version"
   (("/bin/bash") (which "bash")))
 (zero? (system* "sh" "autogen.sh")))
(home-page "https://github.com/pmem/ndctl";)
(synopsis "Manage the non-volatile memory device sub-system in the Linux 
kernel")
(description
 ;; TODO: Update desc.
 "Utility library for managing the libnvdimm (non-volatile memory device)
sub-system in the Linux kernel.")
(license license:gpl2+)))
--8<---cut here---end--->8---

It fails to build to documentation:

--8<---cut here---start->8---
starting phase `build'
  GEN  version.m4
make --no-print-directory all-recursive
  GEN  version.m4
Making all in .
  GEN  version.m4
  GEN  rhel/ndctl.spec
  GEN  sles/ndctl.spec
  CC   ccan/str/str.o
  CC   ccan/str/debug.o
  CC   ccan/list/list.o
  CC   util/parse-options.o
  CC   util/usage.o
  CC   util/size.o
  CC   util/main.o
  CC   util/help.o
  CC   util/strbuf.o
  CC   util/wrapper.o
  CC   util/filter.o
  CC   util/bitmap.o
  AR   libccan.a
ar: `u' modifier ignored since `D' is the default (see `U')
  AR   libutil.a
ar: `u' modifier ignored since `D' is the default (see `U')
Making all in daxctl/lib
  CC   ../../util/sysfs.lo
  CC   ../../util/log.lo
  CC   libdaxctl.lo
  GEN  libdaxctl.pc
  CCLD libdaxctl.la
Making all in ndctl/lib
  CC   nfit.lo
  CC   dimm.lo
  CC   smart.lo
  CC   inject.lo
  CC   intel.lo
  CC   hpe1.lo
  CC   msft.lo
  CC   ars.lo
  CC   firmware.lo
  CC   libndctl.lo
  GEN  libndctl.pc
  CCLD libndctl.la
Making all in ndctl
  CC   ndctl.o
  CC   create-nfit.o
  CC   namespace.o
  CC   bus.o
  CC   check.o
  CC   region.o
  CC   dimm.o
  CC   ../util/log.o
  CC   list.o
  CC   test.o
  CC   ../util/json.o
  CC   inject-error.o
  CC   inject-smart.o
  CC   util/json-smart.o
  CC   util/json-firmware.o
  CCLD ndctl
Making all in daxctl
  CC   daxctl.o
  CC   list.o
  CC   ../util/json.o
  CCLD daxctl
Making all in Documentation/ndctl
  GEN  asciidoc.conf
  GEN  ndctl.xml
  GEN  ndctl-wait-scrub.xml
  GEN  ndctl-start-scrub.xml
  GEN  ndctl-zero-labels.xml
  GEN  ndctl-read-labels.xml
  GEN  ndctl-write-labels.xml
  GEN  ndctl-init-labels.xml
  GEN  ndctl-check-labels.xml
  GEN  ndctl-enable-region.xml
  GEN  ndctl-disable-region.xml
  GEN  ndctl-enable-dimm.xml
  GEN  ndctl-disable-dimm.xml
  GEN  ndctl-enable-namespace.xml
  GEN  ndctl-disable-namespace.xml
  GEN  ndctl-create-namespace.xml
  GEN  ndctl-destroy-namespace.xml
  GEN  ndctl-check-namespace.xml
  GEN  ndctl-inject-error.xml
  GEN  ndctl-inject-smart.xml
  GEN  ndctl-update-firmware.xml
  GEN  ndctl-list.xml
  GEN  ndctl.1
  GEN  ndctl-wait-scrub.1
I/O error : Attempt to load network entity 
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
warning: failed to load external entity 
"http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl";
compilation error: file /tmp/guix-build-ndctl-60.3.drv-0/xmlto-xsl.BtfqIT line 
4 element import
xsl:import : unable to load 
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
make[2]: *** [Makefile:591: ndctl.1] Error 5
make[2]: *** Waiting for unfinished jobs
  GEN  ndctl-start-scrub.1
I/O error : Attempt to load network entity 
http://docbook.sourceforge.net/release/xsl/current/m

Reference manual + tutorials (was: Customize GuixSD: Use Stock SSH Agent Everywhere!)

[Ricardo Wurmus]

Hi Catonano,

>> > In this regard, I'd lie to suggest this talk, I think it's relevant
>> > https://archive.fosdem.org/2017/schedule/event/legacy_docs/
>> >
>> > It'd be very useful for Guile too and God knows for how many more GNU
>> > projects
>>
>> Could you please summarize the key points and how they apply to this
>> discussion?
>>
>
>
> Sure ! Thanks for asking ! 😃
>
> I think a good starting point is this picture
> https://files.mastodon.social/media_attachments/files/003/855/604/original/b02a794729c184ad.png

[…]

Thank you for the summary!

I think that both styles are important.  A reference manual is great
when looking up information and to figure out uncommon workflows.  It’s
also good to have a single section that describes all features of a
tool, which otherwise would have to be extracted from user stories.

Having a document that is centered around user stories is also very
useful, as they make it easier for readers to see their own needs in
them and find the appropriate recipe that leads them to a solution more
quickly.

It would be great to have both!  I’d like the existing reference manual
to remain as the canonical description of all features of Guix, so that
an additional story-centered document (whether that be a dedicated
section or a separate file) can guide readers to more information if
they might need it.

How to begin, though…? :)

--
Ricardo

Re: Reference manual + tutorials (was: Customize GuixSD: Use Stock SSH Agent Everywhere!)

[Catonano]

2018-05-29 16:57 GMT+02:00 Ricardo Wurmus :

>
> Hi Catonano,
>
> >> > In this regard, I'd lie to suggest this talk, I think it's relevant
> >> > https://archive.fosdem.org/2017/schedule/event/legacy_docs/
> >> >
> >> > It'd be very useful for Guile too and God knows for how many more GNU
> >> > projects
> >>
> >> Could you please summarize the key points and how they apply to this
> >> discussion?
> >>
> >
> >
> > Sure ! Thanks for asking ! 😃
> >
> > I think a good starting point is this picture
> > https://files.mastodon.social/media_attachments/files/003/
> 855/604/original/b02a794729c184ad.png
>



> How to begin, though…? :)
>
>

The step 0 could be to copy and paste this post by Chris in a Texinfo
document

The step 1 could be to add a "post" about how to configure a desktop
environment based on openbox along the lines of what this post proposes
https://fedoramagazine.org/openbox-fedora/

And then who knows ☺

Re: Reference manual + tutorials

[Julien Lepiller]

How to begin, though…? :)


The step 0 could be to copy and paste this post by Chris in a Texinfo
document

The step 1 could be to add a "post" about how to configure a desktop
environment based on openbox along the lines of what this post
proposes
https://fedoramagazine.org/openbox-fedora/

And then who knows ☺




Isn't the contributing section of the manual already a user story?

Re: Reference manual + tutorials

[Ricardo Wurmus]

Julien Lepiller  writes:

> Isn't the contributing section of the manual already a user story?

It’s a meta story.  We have no stories about the use of Guix itself.

--
Ricardo

Videos

[Ricardo Wurmus]

Hi Guix,

I’d like us to produce a series of short videos (< 4 mins each) that
introduce functional package management with Guix.

This is supposed to be aimed at people who are intimidated by the manual
and wouldn’t know where to begin reading.  Each of the videos should
focus on a single feature and be on the point.  The final seconds should
point the viewer to the manual to learn more.

Who would like to be involved in the planning and production of the
videos?  There are many tasks such as:

* collecting topics that should be covered
* writing canonical narration scripts for each episode
* translating the scripts into different languages
* recording the narrations in different languages
* drafting the storyboard for each video (i.e. what exactly is to be
  shown and for how long)
* recording the video portions
* mixing different audio tracks and the video track
* designing intro and outro frames
* recording or finding freely licensed music for the intro / outro
* coordinating with all volunteers

What do you think?

--
Ricardo

master seem to build fail

[Feng Shu]

make[2]: 进入目录“/home/feng/project/guix”
Compiling Scheme modules...
  LOAD guix/http-client.scm
  LOAD guix/scripts/pack.scm
  LOAD guix/scripts/system.scm
  LOAD gnu/bootloader/grub.scm
  LOAD gnu/bootloader/u-boot.scm
  LOAD gnu/packages/algebra.scm
  LOAD gnu/packages/audio.scm
  LOAD gnu/packages/bootloaders.scm
  LOAD gnu/packages/check.scm
  LOAD gnu/packages/code.scm
  LOAD gnu/packages/compression.scm
  LOAD gnu/packages/cpp.scm
  LOAD gnu/packages/emacs.scm
  LOAD gnu/packages/firmware.scm
  LOAD gnu/packages/games.scm
  LOAD gnu/packages/gnome.scm
  LOAD gnu/packages/gnuzilla.scm
  LOAD gnu/packages/image.scm
  LOAD gnu/packages/image-viewers.scm
  LOAD gnu/packages/java.scm
  LOAD gnu/packages/calendar.scm
  LOAD gnu/packages/linux.scm
  LOAD gnu/packages/messaging.scm
  LOAD gnu/packages/music.scm
  LOAD gnu/packages/networking.scm
  LOAD gnu/packages/python.scm
  LOAD gnu/packages/qt.scm
  LOAD gnu/packages/rust.scm
  LOAD gnu/packages/samba.scm
  LOAD gnu/packages/search.scm
  LOAD gnu/packages/tls.scm
  LOAD gnu/packages/video.scm
  LOAD gnu/packages/wine.scm
  LOAD gnu/services/base.scm
  LOAD gnu/system.scm
  LOAD gnu/system/file-systems.scm
  LOAD gnu/system/install.scm
  LOAD gnu/system/vm.scm
  LOAD gnu/build/file-systems.scm
  LOAD gnu/build/linux-boot.scm
  LOAD gnu/tests.scm
  LOAD gnu/tests/install.scm
Backtrace:
In ice-9/boot-9.scm:
   222:29 19 (map1 (((gnu bootloader extlinux)) ((gnu tests)) ((…)) …))
   222:29 18 (map1 (((gnu tests)) ((gnu tests base)) ((gnu #)) (#) …))
   222:17 17 (map1 (((gnu tests base)) ((gnu system)) ((gnu # #)) # …))
  2788:17 16 (resolve-interface (gnu tests base) #:select _ #:hide _ …)
  2714:10 15 (_ (gnu tests base) _ _ #:ensure _)
  2982:16 14 (try-module-autoload _ _)
   2312:4 13 (save-module-excursion #)
  3002:22 12 (_)
In unknown file:
  11 (primitive-load-path "gnu/tests/base" #)
In gnu/tests/base.scm:
390:6 10 (_)
63:20  9 (run-basic-test #< kernel: # …)
In ice-9/eval.scm:
155:9  8 (_ #(#(#) #< …))
159:9  7 (_ #(#(#) #< …))
   293:34  6 (_ #(#(#(#(#(#(#(#(#(#) …) …) …) …) …) …) …) …))
   196:35  5 (_ #(#(#(#(#) # #) #) #))
   196:35  4 (_ #(#(#(#) #<) …))
In gnu/system/linux-initrd.scm:
335:4  3 (base-initrd (#< device: "TAGjoptajej2…> …) …)
   233:10  2 (file-system-packages (#< device: "TAG…> …) …)
In unknown file:
   1 (find # …)
   0 (string-prefix? "ext" (read-only) # # …)

ERROR: In procedure string-prefix?:
In procedure string-prefix?: Wrong type argument in position 2 (expecting 
string): (read-only)

Some deprecated features have been used.  Set the environment
variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
program to get more information.  Set it to "no" to suppress
this message.
make[2]: *** [Makefile:5408：make-go] 错误 1
make[2]: 离开目录“/home/feng/project/guix”
make[1]: *** [Makefile:4536：all-recursive] 错误 1
make[1]: 离开目录“/home/feng/project/guix”
make: *** [Makefile:3122：all] 错误 2
feng@tumashu:~/project/guix $ 

-- 

Re: master seem to build fail

[Clément Lassieur]

Hi Feng,

I had a similar issue, I did "make clean" and then it worked again.

Clément

Feng Shu  writes:

> make[2]: 进入目录“/home/feng/project/guix”
> Compiling Scheme modules...
>   LOAD guix/http-client.scm
>   LOAD guix/scripts/pack.scm
>   LOAD guix/scripts/system.scm
>   LOAD gnu/bootloader/grub.scm
>   LOAD gnu/bootloader/u-boot.scm
>   LOAD gnu/packages/algebra.scm
>   LOAD gnu/packages/audio.scm
>   LOAD gnu/packages/bootloaders.scm
>   LOAD gnu/packages/check.scm
>   LOAD gnu/packages/code.scm
>   LOAD gnu/packages/compression.scm
>   LOAD gnu/packages/cpp.scm
>   LOAD gnu/packages/emacs.scm
>   LOAD gnu/packages/firmware.scm
>   LOAD gnu/packages/games.scm
>   LOAD gnu/packages/gnome.scm
>   LOAD gnu/packages/gnuzilla.scm
>   LOAD gnu/packages/image.scm
>   LOAD gnu/packages/image-viewers.scm
>   LOAD gnu/packages/java.scm
>   LOAD gnu/packages/calendar.scm
>   LOAD gnu/packages/linux.scm
>   LOAD gnu/packages/messaging.scm
>   LOAD gnu/packages/music.scm
>   LOAD gnu/packages/networking.scm
>   LOAD gnu/packages/python.scm
>   LOAD gnu/packages/qt.scm
>   LOAD gnu/packages/rust.scm
>   LOAD gnu/packages/samba.scm
>   LOAD gnu/packages/search.scm
>   LOAD gnu/packages/tls.scm
>   LOAD gnu/packages/video.scm
>   LOAD gnu/packages/wine.scm
>   LOAD gnu/services/base.scm
>   LOAD gnu/system.scm
>   LOAD gnu/system/file-systems.scm
>   LOAD gnu/system/install.scm
>   LOAD gnu/system/vm.scm
>   LOAD gnu/build/file-systems.scm
>   LOAD gnu/build/linux-boot.scm
>   LOAD gnu/tests.scm
>   LOAD gnu/tests/install.scm
> Backtrace:
> In ice-9/boot-9.scm:
>222:29 19 (map1 (((gnu bootloader extlinux)) ((gnu tests)) ((…)) …))
>222:29 18 (map1 (((gnu tests)) ((gnu tests base)) ((gnu #)) (#) …))
>222:17 17 (map1 (((gnu tests base)) ((gnu system)) ((gnu # #)) # …))
>   2788:17 16 (resolve-interface (gnu tests base) #:select _ #:hide _ …)
>   2714:10 15 (_ (gnu tests base) _ _ #:ensure _)
>   2982:16 14 (try-module-autoload _ _)
>2312:4 13 (save-module-excursion #)
>   3002:22 12 (_)
> In unknown file:
>   11 (primitive-load-path "gnu/tests/base" #)
> In gnu/tests/base.scm:
> 390:6 10 (_)
> 63:20  9 (run-basic-test #< kernel: # …)
> In ice-9/eval.scm:
> 155:9  8 (_ #(#(#) #< …))
> 159:9  7 (_ #(#(#) #< …))
>293:34  6 (_ #(#(#(#(#(#(#(#(#(#) …) …) …) …) …) …) …) …))
>196:35  5 (_ #(#(#(#(#) # #) #) #))
>196:35  4 (_ #(#(#(#) #<) …))
> In gnu/system/linux-initrd.scm:
> 335:4  3 (base-initrd (#< device: "TAGjoptajej2…> …) …)
>233:10  2 (file-system-packages (#< device: "TAG…> …) …)
> In unknown file:
>1 (find # …)
>0 (string-prefix? "ext" (read-only) # # …)
>
> ERROR: In procedure string-prefix?:
> In procedure string-prefix?: Wrong type argument in position 2 (expecting 
> string): (read-only)
>
> Some deprecated features have been used.  Set the environment
> variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
> program to get more information.  Set it to "no" to suppress
> this message.
> make[2]: *** [Makefile:5408：make-go] 错误 1
> make[2]: 离开目录“/home/feng/project/guix”
> make[1]: *** [Makefile:4536：all-recursive] 错误 1
> make[1]: 离开目录“/home/feng/project/guix”
> make: *** [Makefile:3122：all] 错误 2
> feng@tumashu:~/project/guix $ 

Re: Videos

[Julien Lepiller]

Le 2018-05-29 16:48, Ricardo Wurmus a écrit :

Hi Guix,

I’d like us to produce a series of short videos (< 4 mins each) that
introduce functional package management with Guix.

This is supposed to be aimed at people who are intimidated by the 
manual

and wouldn’t know where to begin reading.  Each of the videos should
focus on a single feature and be on the point.  The final seconds 
should

point the viewer to the manual to learn more.

Who would like to be involved in the planning and production of the
videos?  There are many tasks such as:

* collecting topics that should be covered
* writing canonical narration scripts for each episode
* translating the scripts into different languages
* recording the narrations in different languages
* drafting the storyboard for each video (i.e. what exactly is to be
  shown and for how long)
* recording the video portions
* mixing different audio tracks and the video track
* designing intro and outro frames
* recording or finding freely licensed music for the intro / outro
* coordinating with all volunteers

What do you think?

--
Ricardo


That sounds like a great plan! Of course I'd like to be involved in 
translating
the script into French and I could probably record a French version of 
the videos
too. I don't have any experience in the other fields, but I guess I 
could learn.

Re: Videos

[Catonano]

2018-05-29 17:45 GMT+02:00 Julien Lepiller :

> Le 2018-05-29 16:48, Ricardo Wurmus a écrit :
>
>> Hi Guix,
>>
>> I’d like us to produce a series of short videos (< 4 mins each) that
>> introduce functional package management with Guix.
>>
>> This is supposed to be aimed at people who are intimidated by the manual
>> and wouldn’t know where to begin reading.  Each of the videos should
>> focus on a single feature and be on the point.  The final seconds should
>> point the viewer to the manual to learn more.
>>
>> Who would like to be involved in the planning and production of the
>> videos?  There are many tasks such as:
>>
>> * collecting topics that should be covered
>> * writing canonical narration scripts for each episode
>> * translating the scripts into different languages
>> * recording the narrations in different languages
>> * drafting the storyboard for each video (i.e. what exactly is to be
>>   shown and for how long)
>> * recording the video portions
>> * mixing different audio tracks and the video track
>> * designing intro and outro frames
>> * recording or finding freely licensed music for the intro / outro
>> * coordinating with all volunteers
>>
>> What do you think?
>>
>> --
>> Ricardo
>>
>
> That sounds like a great plan! Of course I'd like to be involved in
> translating
> the script into French and I could probably record a French version of the
> videos
> too. I don't have any experience in the other fields, but I guess I could
> learn.
>
>

I think I have demonstrated my aptitude in recording video fragments on the
field 😄

As for storyboarding and scripting, instead, I'd love to receive
suggestions.

Also, I wouldn't know how to mix audio/video. What software could we use ?
I don't know.

Re: GSoC: Adding a web interface similar to the Hydra web interface

[Ludovic Courtès]

Hello Tatiana & all,

Ricardo Wurmus  skribis:

>> I am a bit confused about the database structure. As far as I understand,
>> there are project_name (project) and branch_name (jobset) properties, but
>> project_name is a primary key, so a project can't have several branches?
>
> I share your confusion.  Maybe Ludovic or Mathieu can shed some more
> light on this.

It’s confusing indeed, I think it’s a mistake that has yet to be fixed.
Basically what we do now is that we use a different ‘repo_name’ when we
just want to add a branch…

We should fix it at some point.  Suggestions welcome!

I would encourage you to write commits in a way to minimize friction
when we are to merge them—that is, following the conventions that
Ricardo outlined.  That way Mathieu, Ricardo, or myself can take a look
and quickly cherry-pick to master.

Anyway, kudos on what you’ve already achieved!  Getting started on an
existing code base is never easy, so I think you’ve done a good job.

Thank you,
Ludo’.

Re: Videos

[Amirouche Boubekki]

On 2018-05-29 16:48, Ricardo Wurmus wrote:

Hi Guix,

I’d like us to produce a series of short videos (< 4 mins each) that
introduce functional package management with Guix.

This is supposed to be aimed at people who are intimidated by the 
manual

and wouldn’t know where to begin reading.  Each of the videos should
focus on a single feature and be on the point.  The final seconds 
should

point the viewer to the manual to learn more.

Who would like to be involved in the planning and production of the
videos?  There are many tasks such as:

* collecting topics that should be covered
* writing canonical narration scripts for each episode
* translating the scripts into different languages
* recording the narrations in different languages
* drafting the storyboard for each video (i.e. what exactly is to be
  shown and for how long)
* recording the video portions
* mixing different audio tracks and the video track
* designing intro and outro frames
* recording or finding freely licensed music for the intro / outro
* coordinating with all volunteers

What do you think?



Guix videos! Great idea! FWIW, I think it's a lot of
efforts, but if the community manage to pull it off,
very great!

FWIW, I record screencast using the following script:

  ~/src/scheme/video$ cat record.sh
  #!/bin/sh
  ffmpeg -video_size 1920x1080 -framerate 25 -f x11grab -i :0.0+0,0 -f 
pulse -ac 2 -i default $1


Then run the script with something like:

  $ ./record.sh guix-functional-package-manager.mp4

I've been recording some guile hacking session, that you
can find on youtube with the name "GNU Guile Hacking".
Or using the following command:

  youtube-dl 
https://www.youtube.com/playlist?list=PL_jCPpfzyfeqtG9Jm4-WkiyX3kP4GiZp5


It's far away from anything like a MOOC but some people
enjoy them.  I am not looking to spam the mailing with
my poor attempts at marketing GNU Guile but rather suggest
that anyone can create such video focusing on guix. And
without much prepartion, can do much better than me.

Anyway, good luck!

Re: GSoC: Adding a web interface similar to the Hydra web interface

[Gábor Boskovits]

2018-05-29 18:07 GMT+02:00 Ludovic Courtès :

> Hello Tatiana & all,
>
> Ricardo Wurmus  skribis:
>
> >> I am a bit confused about the database structure. As far as I
> understand,
> >> there are project_name (project) and branch_name (jobset) properties,
> but
> >> project_name is a primary key, so a project can't have several branches?
> >
> > I share your confusion.  Maybe Ludovic or Mathieu can shed some more
> > light on this.
>
> It’s confusing indeed, I think it’s a mistake that has yet to be fixed.
> Basically what we do now is that we use a different ‘repo_name’ when we
> just want to add a branch…
>
> We should fix it at some point.  Suggestions welcome!
>
>
I believe the confusion arises from the fact, that there is a naming
inconsistency.
If we could come up with good names to the things involved, then that might
suggest a clean solution. It seems that the problem is caused by a project
and
a repository is somehow intermixed. That might suggest a solution to keep
project-name as is, as primary key, and add a separate repository field...
or not.
Does that make sense?


> I would encourage you to write commits in a way to minimize friction
> when we are to merge them—that is, following the conventions that
> Ricardo outlined.  That way Mathieu, Ricardo, or myself can take a look
> and quickly cherry-pick to master.
>
> Anyway, kudos on what you’ve already achieved!  Getting started on an
> existing code base is never easy, so I think you’ve done a good job.
>
> Thank you,
> Ludo’.
>
>

Re: Code of Conduct and Diversity Statement

[Ludovic Courtès]

Hello Guix!

Tobias Geerinckx-Rice  skribis:

> Leo Famulari wrote:
>> 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
>
> Oh, is this still under review? +1!

I was waiting for Ricardo’s “+1” and he just wrote on IRC that we could
go ahead, so commit a076f19908d06b6df49f1c25c40de8838213cd71 finally
switches to version 1.4.  \o/

Thanks to everyone who participated!

Ludo’.

Re: Update of Emacs to 26.1.

[Alex Kost]

Ricardo Wurmus (2018-05-29 13:32 +0200) wrote:

> Alex Kost  writes:
>
>> Ricardo Wurmus (2018-05-28 21:25 +0200) wrote:
>>
>> [...]
>>> The update did break “emacs-minimal” and thus all Emacs packages, but
>>> that can be fixed by passing “--with-gnutls=no” to emacs-minimal:
>>
>> I like it!  I think '*-minimal' packages should be as minimal as possible.
>
> “emacs-minimal” already didn’t have gnutls among its inputs, but the
> build system now complains about this unless the configure flags make
> that explicit to show intent.

Oops, sorry, I didn't pay the required attention to the problem you
solved when I wrote that :-)  I just thought that 'emacs-minimal' had
unneeded 'gnutls' input and you removed it.  But now I see, thanks!

-- 
Alex

Re: Updating udisks: New dependencies (libblockdev, volume-key, dmraid, libbytesize, ndctl...)

[Ludovic Courtès]

Howdy!

Nils Gillmann  skribis:

> Pierre Neidhardt transcribed 1.3K bytes:
>> 
>> I'm working on updating udisks from the "old legacy" version (which is
>> currently packaged in Guix) to version 2.7.6.
>> 
>>  https://github.com/storaged-project/udisks
>> 
>> It turns out to be much harder than expected!  Recent versions of udisks
>> depend on libblockdev, which in turn depends on the 
>> volume_key, dmraid, libbytesize, ndctl and possibly more, all of which
>> are not packaged in Guix yet.
>> 
>> What do you think?  Is it worth it?  Any alternative to udisks?
>
> Possibly there are alternatives, but it is required by some parts in
> Guix. So,
>
>> Otherwise I'll go ahead and send a big fat patch set.
>
> as Invader Zim would say: "More patches means more Guix!" (go for it :)).

Agreed.  :-)

I guess we can’t really avoid udisks and it does the job well anyway, so
let’s go for the big patch set!  Maybe in 2020 we’ll have a bunch of
Scheme modules doing that job?  :-)

BTW, regarding patch sets, please make sure to send the first message to
guix-patc...@gnu.org (the cover letter), and then to send the other
patches of that series to n...@debbugs.gnu.org, where NNN is the number
assigned as a result of sending your first message.

TIA!
Ludo’.

Re: Don't change "+" syntax in guix/.dir-locals.el

[Ludovic Courtès]

Hi Alex,

Alex Kost  skribis:

> Ludovic Courtès (2018-05-28 11:34 +0200) wrote:
>
>> Alex Kost  skribis:
>>
>>> Highlighting?  Sorry, I don't understand what you mean: highlighting
>>> will not be effected in any way.  The problem is that those
>>> 'modify-syntax-entry' lines in ".dir-locals.el" break the default syntax
>>> table of scheme-mode, so "+", "$" and "~" characters are not considered
>>> to be parts of symbols (variable names in particular), i.e.
>>> (re-search-forward "\\s_" nil t) doesn't find them as it should.
>>>
>>> Since you added those lines, you probably know what Paredit problem you
>>> fixed by that (perhaps this problem should be fixed in Paredit itself?)
>>
>> Yes, the comment gives an idea:
>>
>>;; This notably allows '(' in Paredit to not insert a space when the
>>;; preceding symbol is one of these.
>>
>> Basically if you don’t have it, when you type “#$(foo)”, Paredit inserts
>> a space before the opening parenthesis.
>
> OK, I see now.  Paredit inserts a space ('paredit-space-for-delimiter-p'
> does it) if the point is placed on a symbol.  So by fixing this gexp
> stuff, you also break the default behavior of Paredit:
>
> - the default paredit inserts a space after ‘foo+’ symbol: foo+ ()
>
> - and with this dir-locals setting, it doesn't: foo+()

To me that’s a feature, because in Scheme ‘+’ is acceptable within
identifiers, so there’s no reason to automatically insert a space after
‘+’.

> Now I understand why this problem should be fixed, but my opinion is
> that ".dir-locals.el" *should not* break the default syntax table of
> scheme-mode just to make one emacs package work as desired.

Do you think .dir-locals.el could perform this change in a buffer-local
fashion?

Thanks for explaining!

Ludo’.

Re: Reference manual + tutorials

[Ludovic Courtès]

Hello!

Ricardo Wurmus  skribis:

> It would be great to have both!  I’d like the existing reference manual
> to remain as the canonical description of all features of Guix, so that
> an additional story-centered document (whether that be a dedicated
> section or a separate file) can guide readers to more information if
> they might need it.

I think it’s not all-or-nothing though.  Our manual could be better
structured and it could include more examples.

I like the “traditional” GNU manuals (libc, Emacs, Gnus, etc.), which
work very well for me, even though they’re only “locally
user-story-based”, so to speak.

Ludo’.

Re: GSoC-2018 - Build daemon rewrite in Scheme Updates

[Ludovic Courtès]

Hello uniq10,

Thanks for the update!

Sandeep Subramanian  skribis:

> `build-derivation` is now using `call-with-container`
> and it seems to work well. `build-derivation` assumes
> that all the inputs needed for the derivation is already
> built and ready. As a next step I wanted to try and build
> the `inputDrvs` if the inputs are missing.

Nice, it sounds like a good start.

Where is the code you’ve been working on?  Is it
?

In general, I would encourage you to follow the project’s conventions as
closely as possible to ease future merges.  See
.
Please also consider showing up on #guix on IRC to share what you’re up
to and ask for advice whenever you feel like it.  Communication is key
is a distributed project like this.

As discussed off-list, I just started merging into ‘master’ proper work
from last year: .  This is an area where
we’ll obviously have to coordinate.  For example it’d be great if you
could rebase onto master once 31618 has been merged, and let me know if
anything is amiss.

> I looked through the C++ code to find out how exactly
> this is done and I have a good understanding of it now.
> I plan to emulate the behaviour of the C++ code for
> the entire derivation building pipeline.
>
> I spent a lot of time browsing the C++ code base and had
> to keep going back to it often, since I had trouble keeping
> the C++ code flow in memory. So, I thought it would be
> worthwhile to write some detailed notes on the C++ daemon
> code base that I can refer to while coding. The notes I made
> can be found here:
> https://github.com/uniq10/gsoc-guix-notes/blob/master/daemon-notes.md

Woow, very nice!  From a quick look it does seem to correctly reflect
what’s happening in that code.  It would have helped me a lot to have
such a document back then.  ;-)

BTW, note that you shouldn’t take the structure of the C++ code as a
reference to follow.  In Scheme we would more naturally use different
idioms than those of this code (object-oriented C++).  You’re welcome to
discuss on this list or on IRC how to structure things.

Thanks for the update and for the nice work!

Ludo’.

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

[Ludovic Courtès]

Hello,

Pierre Neidhardt  skribis:

>   GEN  ndctl-wait-scrub.1
> I/O error : Attempt to load network entity 
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
> warning: failed to load external entity 
> "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl";
> compilation error: file /tmp/guix-build-ndctl-60.3.drv-0/xmlto-xsl.BtfqIT 
> line 4 element import
> xsl:import : unable to load 
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl

There are many packages using Docbook.  Often fixing the above issue is
just a matter of adding libxml2, libxslt, and docbook-xsl as inputs;
this has the effect of defining XML_CATALOG_FILES and related variables
such that things work.

There are also packages that directly modify the catalog URI, though I
can’t find a good example right now.

HTH!

Ludo’.

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

[Leo Famulari]

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

[...]

> --8<---cut here---start->8---
> case "$1" in
> stylesheet)
>   if [ "$VERBOSE" -ge 1 ]
>   then
> echo >&2 "Convert to troff"
>   fi
>   echo 
> "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl";
>   ;;
> post-process)
>   [ -e "$XSLT_PROCESSED" ] && rm "$XSLT_PROCESSED"
>   ${GCP_PATH:-cp} -R -P -p -- * "$OUTPUT_DIR" 2>/dev/null
>   ;;
> esac
> --8<---cut here---end--->8---
> 
> I think that "echo" line should be patched just like docbook.  What do
> you think?

Yes, we should do something like what we do for docbook.


signature.asc
Description: PGP signature

Re: Videos

[Ludovic Courtès]

Hello,

Ricardo Wurmus  skribis:

> I’d like us to produce a series of short videos (< 4 mins each) that
> introduce functional package management with Guix.

That’s a good idea!

> Who would like to be involved in the planning and production of the
> videos?  There are many tasks such as:
>
> * collecting topics that should be covered
> * writing canonical narration scripts for each episode
> * translating the scripts into different languages
> * recording the narrations in different languages
> * drafting the storyboard for each video (i.e. what exactly is to be
>   shown and for how long)
> * recording the video portions
> * mixing different audio tracks and the video track
> * designing intro and outro frames
> * recording or finding freely licensed music for the intro / outro
> * coordinating with all volunteers

For a start, volunteers could look at material from talks we gave (see
).
For example graphics from the slides or the narrative to introduce a
topic might help get started.

Ludo’.

Re: master seem to build fail

[Ludovic Courtès]

Hello,

"Feng Shu"  skribis:

> In gnu/system/linux-initrd.scm:
> 335:4  3 (base-initrd (#< device: "TAGjoptajej2…> …) …)
>233:10  2 (file-system-packages (#< device: "TAG…> …) …)
> In unknown file:
>1 (find # …)
>0 (string-prefix? "ext" (read-only) # # …)
>
> ERROR: In procedure string-prefix?:
> In procedure string-prefix?: Wrong type argument in position 2 (expecting 
> string): (read-only)

This particular issue is a symptom of a change in the ABI introduced by
a5acc17a3c10a3779b5b8b1a2565ef130be77e51.  That’s why “make clean-go && make”
solves the problem.

Ludo’.

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

[Leo Famulari]

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&m=152761328506724&w=2
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11235

The summary is that a malicious Git remote can execute arbitrary code on
your machine when you clone from the remote, so please update ASAP.


signature.asc
Description: PGP signature

Re: Updating udisks: New dependencies (libblockdev, volume-key, dmraid, libbytesize, ndctl...)

[Pierre Neidhardt]

Ludovic Courtès  writes:

> BTW, regarding patch sets, please make sure to send the first message to
> guix-patc...@gnu.org (the cover letter), and then to send the other
> patches of that series to n...@debbugs.gnu.org, where NNN is the number
> assigned as a result of sending your first message.

Ack.

Big fat patch set coming soon.

-- 
Pierre Neidhardt

The person who makes no mistakes does not usually make anything.


signature.asc
Description: PGP signature

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

[Tobias Geerinckx-Rice]

Leo,

Leo Famulari wrote:
The summary is that a malicious Git remote can execute arbitrary 
code on
your machine when you clone from the remote, so please update 
ASAP.


Thanks for this explicit heads-up!

Kind regards,

T G-R

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

[Leo Famulari]

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, which is apparently incorrect. The correct CVE
IDs are CVE-2018-11233 and CVE-2018-11235.


signature.asc
Description: PGP signature

Re: Reference manual + tutorials

[Ricardo Wurmus]

Ludovic Courtès  writes:

> Hello!
>
> Ricardo Wurmus  skribis:
>
>> It would be great to have both!  I’d like the existing reference manual
>> to remain as the canonical description of all features of Guix, so that
>> an additional story-centered document (whether that be a dedicated
>> section or a separate file) can guide readers to more information if
>> they might need it.
>
> I think it’s not all-or-nothing though.  Our manual could be better
> structured and it could include more examples.
>
> I like the “traditional” GNU manuals (libc, Emacs, Gnus, etc.), which
> work very well for me, even though they’re only “locally
> user-story-based”, so to speak.

Yes, this can work.  It’s hard for me to imagine where one would put
prose that resembles a tutorial in our current manual.  It currently
leans very heavily towards a reference manual, which discourages me from
adding elaborate examples.

There’s also the danger of interrupting the flow with too many big
inline examples.  Currently, it is easy to understand the big picture
because the prose isn’t separated by step for step instructions.

It would be sad to miss out on good tutorials just because they don’t
fit into the current manual; and it would be just as sad to clutter the
manual by filling it with tutorials that would seem out of place.

It’s difficult to strike the right balance.

--
Ricardo

Re: Videos

[Ricardo Wurmus]

Catonano  writes:

> Also, I wouldn't know how to mix audio/video. What software could we
> use ?  I don't know.

In the past I have used the sequence editor in Blender for processing
videos.

I would use that if the video needs to be cut and the audio needs to be
carefully aligned.  For simpler videos where the exact duration of each
segment is known and the narrator is forced to fit the narration into
the known duration we can do without Blender and automate the mixing
(with ffmpeg or similar).

--
Ricardo

Help needed to update VLC to 3.0.3 on the master branch

[Mark H Weaver]

Hello Guix,

I just pushed a major VLC update to the 'core-updates' branch, commit
76277052939524d1ea3394f83739f06efd0dd8ae.  I pushed it to 'core-updates'
because I've been living on that branch for months, and so it's the only
branch that I can easily test for.

However, I strongly suspect that the old VLC on master, and the old
ffmpeg-2.8 that it depends on, are most likely a security risk.

So, I would be grateful if someone could cherry-pick this commit to
'master', do some basic testing on it, and then push it on my behalf if
it works.

Many thanks to Roel Janssen  for his invaluable help on
this commit!

   Mark

Re: 04/05: gnu: swig: Patch for Octave 4.4.

[Mark H Weaver]

kkebr...@posteo.net (Kei Kebreau) writes:

> kkebreau pushed a commit to branch master
> in repository guix.
>
> commit 3771000f893d4b53e302f5bca07afeba69e76cd4
> Author: Kei Kebreau 
> Date:   Fri May 25 22:25:21 2018 -0400
>
> gnu: swig: Patch for Octave 4.4.

On the core-updates branch, "guix refresh -l swig" reports that updating
swig requires 1453 rebuilds.  That's too many, so I reverted it.

Instead, I suggest creating a different 'swig' package for octave that
inherits from the primary one and adds this patch.

What do you think?

  Mark