Hi,
This is not due to NFS, but due to the fact that the NFS mount is
mounted nosuid (and nodev, probably). I can reproduce it on a local
filesystem mounted nosuid.
It seems that, when remounting a bind mount which is originally nosuid
inside a mount ns, you need to specify explicitely the nosuid
Users should be aware of anti-feature of packages.
It is best to have anti-feature tag in anti-feature packages so that user know
which program has anti-features; Like F-Droid. Also, user should be aware of
anti-feature during installation. And wherever this awareness is needed...
An example is
Hi,
Mathieu Othacehe skribis:
>> here is an example: https://ci.guix.gnu.org/build/287478/details and
>> https://ci.guix.gnu.org/build/287476/details are being built at the
>> same time, and the logs currently show they are both running the test
>> phase of the php package.
>
> Thanks for the re
Hey Ludo,
Thanks for sharing your thoughts, it's always useful :).
> Seems to me that ‘BuildSteps’ is an orthogonal concern that has little
> to do with Cuirass’ job and with its data model. In Hydra I saw that as
> a (necessary) kludge.
I'm not sure to follow you here. Cuirass and Hydra have
I have a USB-connected HP DeskJet Ink Advantage 1515 printer/scanner.
On my own system (this is a full Guix System, not Guix on a foreign distro) I
modified the configuration.scm:
```scheme
(use-package-modules #;... scanner)
(operating-system
#;...
(services
(append
#;...
(
Hi,
On Mon, 2021-02-08 at 13:28 +, soheil--- via Bug reports for GNU Guix wrote:
> Users should be aware of anti-feature of packages.
> It is best to have anti-feature tag in anti-feature packages so that user know
> which program has anti-features; Like F-Droid. Also, user should be aware of
On Mon, Feb 08, 2021 at 01:28:40PM +, soheil--- via Bug reports for GNU
Guix wrote:
> Users should be aware of anti-feature of packages.
> It is best to have anti-feature tag in anti-feature packages so that user
> know which program has anti-features; Like F-Droid. Also, user should be
> aw
On Mon, Feb 08, 2021 at 11:04:48PM -0500, Leo Famulari wrote:
> On Sun, Feb 07, 2021 at 02:47:30PM -0500, guix-comm...@gnu.org wrote:
> > commit 589b6be99634d0c42cf25e1599b2f62b0d8e89f7
> > Author: Efraim Flashner
> > AuthorDate: Sun Feb 7 21:47:01 2021 +0200
> >
> > gnu: xorriso: Update to 1
"bdju" writes:
> Apparently there were issues back in August. Version number is still
> 1.0.0. Current build has been failing a couple weeks maybe.
> Build log here: http://ix.io/2OPc
> guix version: guix (GNU Guix) b421b2f66ec5b39bd1331e276bff5f9698cd65dc
> I am using Guix System.
Hello, thanks
Hi guix users,
It strikes me that a better course of action here would be, rather than
providing a warning that might not be noticed by the user, to remove the
default and force people to explicitly put `password-authentication? #t` or
`password-authentication? #f`.
That way if I have set up a
10 matches
Mail list logo
