GMP GCC C++ Hurd cross-build failure on core-updates

2022-12-14 Thread Nathan Dehnel
You could try seeing what they're doing here to cross-build
https://github.com/flavioc/cross-hurd
It worked last time I ran it (which was admittedly a while ago)



Re: Status of hibernation (suspend to disk) in Guix

2022-12-14 Thread Nathan Dehnel
> 2. Does hibernation work in case of a swap-file inside a
 root-partition inside a luks-encrypted device?

Just posting to confirm that this does work (with BTRFS as well;
single drive only, not RAID).



Re: shepherd: prefix output with service names?

2022-12-14 Thread Maxim Cournoyer
Hi Ricardo,

Ricardo Wurmus  writes:

[...]

> What do you think of prefixing every line with the name of the service
> that is responsible for it?  This way we could probably also
> prettify/post-process the output somewhat.

I think that's a great idea; I'm not sure if you've noticed, but mcron
is now doing that for the job it runs, so it'd be consistent if Shepherd
also did that.

-- 
Thanks,
Maxim



Re: GNU Guix 1.4.0rc2 available for testing!

2022-12-14 Thread Vagrant Cascadian
On 2022-12-11, Ludovic Courtès wrote:
> The second release candidate of the upcoming 1.4.0 release is now
> available for testing, fixing issues that were reported for rc1:

Also available in .deb format on your favorite Debian mirrors:

  https://tracker.debian.org/pkg/guix

Currently only in Debian sid/unstable, but probably installable on a
Debian bookworm/testing system, too.


live well,
  vagrant


signature.asc
Description: PGP signature


Re: GNU Guix 1.4.0rc2 available for testing!

2022-12-14 Thread Maxim Cournoyer
Hello,

Roman Scherer  writes:

> Hi Ludo,
>
> I tested the foreign distro installation of 
> guix-binary-1.4.0rc2.aarch64-linux.tar.xz
> on Asahi Linux. I went through the installation without any problems.

And I tested the installation of
'guix-binary-1.4.0rc2.armhf-linux.tar.xz' on top of a very bare-bone
embedded OS, which went mostly fine apart from gotchas that are
attributed to that strange busybox environment (I needed guix pack to
help bootstrap the needed dependencies), and some changes to the install
script to accommodate that use case (see #60068).

It seem to run fine there.

Thanks for the RCs!

-- 
Thanks,
Maxim



Re: shepherd: prefix output with service names?

2022-12-14 Thread Thompson, David
Hi Ricardo,

On Wed, Dec 14, 2022 at 5:44 AM Ricardo Wurmus  wrote:
>
> What do you think of prefixing every line with the name of the service
> that is responsible for it?  This way we could probably also
> prettify/post-process the output somewhat.

I think that's a great idea!

- Dave



shepherd: prefix output with service names?

2022-12-14 Thread Ricardo Wurmus
Hi Guix,

here is some output from “guix system reconfigure”:

--8<---cut here---start->8---
…
activating system...
The following derivation will be built:
  /gnu/store/7361cd8aasxwwb93ygdfwjp3ghn06ahb-switch-to-system.scm.drv

building /gnu/store/7361cd8aasxwwb93ygdfwjp3ghn06ahb-switch-to-system.scm.drv...
making '/gnu/store/rp04hkqlzx5j2lhxainsz77vpqqigsjz-system' the current 
system...
setting up setuid programs in '/run/setuid-programs'...
populating /etc from /gnu/store/gq2dvz09wf3sdmvynr2vdzy5wwj7k9fd-etc...
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

initdb: error: directory "/var/lib/postgresql/data" exists but is not empty
If you want to create a new database system, either remove or empty
the directory "/var/lib/postgresql/data" or run initdb
with an argument other than "/var/lib/postgresql/data".
Starting installation ...
Validate installation settings ...
Create file system structures ...
Create self-signed certificate database ...
Error: Instance creation failed!  Failed to start DS
The following derivation will be built:
  /gnu/store/5jx2cj780cqs2pp575rckvrx45j9kysy-install-bootloader.scm.drv

building 
/gnu/store/5jx2cj780cqs2pp575rckvrx45j9kysy-install-bootloader.scm.drv...
guix system: bootloader successfully installed on '(/dev/sda)'
shepherd: Evaluating user expression (and (defined? (quote transient?)) (map (# 
?) ?)).
The following derivation will be built:
  /gnu/store/q933nvsqjx2f9zra91jbpjvb9x2yf2sn-upgrade-shepherd-services.scm.drv

building 
/gnu/store/q933nvsqjx2f9zra91jbpjvb9x2yf2sn-upgrade-shepherd-services.scm.drv...
shepherd: Service host-name has been started.
shepherd: Service user-homes has been started.
shepherd: Service sysctl has been started.
shepherd: Service host-name has been started.
shepherd: Service term-console could not be started.
shepherd: Service postgres-roles has been started.
shepherd: Service directory-server-localhost could not be started.
To complete the upgrade, run 'herd restart SERVICE' to stop,
upgrade, and restart each service that was not automatically restarted.
Run 'herd status' to view the list of services on your system.
--8<---cut here---end--->8---

You see that there is output of tools that run as part of service
activation snippets.  It is not clear which service is responsible for
any particular line of output.

What service produced the line “Error: Instance creation failed!  Failed
to start DS”, for example?  I know it’s the directory-server-localhost
service, because that’s what I’m working on right now, but it’s not
clear from the output.

What do you think of prefixing every line with the name of the service
that is responsible for it?  This way we could probably also
prettify/post-process the output somewhat.

-- 
Ricardo



Re: Status of hibernation (suspend to disk) in Guix

2022-12-14 Thread Ivan Vilata i Balaguer
Ivan Vilata i Balaguer (2022-12-12 21:11:53 +0100) wrote:

> Mekeor Melire (2022-12-10 01:00:24 +) wrote:
> 
> > > What about the "filefrag" executable from the "e2fsprogs" package.
> > > According to this article, it can be used in place of the deprecated
> > > uswsusp suite:
> > >
> > > https://www.linuxuprising.com/2021/08/how-to-enable-hibernation-on-ubuntu.html
> 
> Good find!  Besides the issue of `filefrag` being ExtFS-specific, another
> thing that worries me is [this check][1] that `swap-offset` does about the
> swap header being physically contiguous on disk, which would need to be made
> manually with `filefrag`.
> 
> [1]: 
> https://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-utils.git/tree/swap-offset.c#n114

I had a quick look to the [source code of mkswap][1] and it does take care of
checking whether the swap file has holes in it (look for the word "hole").  If
it has, it prints a warning (but it continues).  For instance:

```
$ dd if=/dev/zero of=swap bs=512 count=1 seek=1000
1+0 records in
1+0 records out
512 bytes copied, 0.000234313 s, 2.2 MB/s
$ mkswap swap

mkswap: swap contains holes or other unsupported extents.
This swap file can be rejected by kernel on swap activation!
Use --verbose for more details.

Setting up swapspace version 1, size = 496 KiB (507904 bytes)
no label, UUID=3c5920cb-04ee-4713-8008-c2c1bebc2f6f
```

[1]: https://github.com/util-linux/util-linux/blob/master/disk-utils/mkswap.c

Since it's unlikely that the file will change its block arrangement on disk,
and enlarging it requires another invocation of `mkswap`, it's probably enough
to tell the user to check for such warnings on `mkswap` invocation (in section
"(guix)Keyboard Layout, Networking, and Partitioning"), and then instructing
them to use `filefrag` in "(guix)Swap Space" should be ok.

I can work on an additional patch for that, but I can't ensure that it'll be
ready before 1.4.0 (I'm not in the dev team, so I don't know what the planning
for the release is ).

Cheers!

-- 
Ivan Vilata i Balaguer -- https://elvil.net/


signature.asc
Description: PGP signature