New installation CDs and qemu image

2014-02-11 Thread Samuel Thibault
Hello, I've rebuilt the installation CDs and the preinstalled qemu image. Samuel -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Re: New installation CDs and qemu image

2014-02-11 Thread Gabriele Giacone
On Tue, Feb 11, 2014 at 1:17 PM, Samuel Thibault samuel.thiba...@gnu.org wrote: I've rebuilt the installation CDs and the preinstalled qemu image. CD says start ext2fs: panic: pmap_remove: null pv_list! -- G..e -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject

heimdal: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Svante Signell
Source: heimdal Version: 1.6~git20131207+dfsg-1 Severity: important Tags: patch User: debian-hurd@lists.debian.org Usertags: hurd Hi, Currently heimdal fails to build on GNU/Hurd due to a missing definition of _IOT_sundevdata. The attached patch solves this problem by defining it with the _IOT

Re: New installation CDs and qemu image

2014-02-11 Thread Samuel Thibault
Gabriele Giacone, le Tue 11 Feb 2014 17:18:41 +0100, a écrit : On Tue, Feb 11, 2014 at 1:17 PM, Samuel Thibault samuel.thiba...@gnu.org wrote: I've rebuilt the installation CDs and the preinstalled qemu image. CD says start ext2fs: panic: pmap_remove: null pv_list! Which CD? Which virtual

Re: heimdal: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Samuel Thibault
Svante Signell, le Tue 11 Feb 2014 17:48:50 +0100, a écrit : uint64_t param1; uint64_t syscall; }; +#ifdef __GNU__ +/* FIXME: Enter the correct values here */ +#define _IOT_sundevdata _IOT(_IOTS(long), 7, 0, 0, 0, 0) Why long? The structure contains uint64_t, not longs. Did you

pristine-tar: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Svante Signell
Source: pristine-tar Version: 1.30 Severity: important Tags: patch User: debian-hurd@lists.debian.org Usertags: hurd Hi, Currently pristine-tar fails to build on GNU/Hurd due to PATH_MAX not being defined. The attached patch solves this problem by calculating the needed string lengths and malloc

Re: New installation CDs and qemu image

2014-02-11 Thread Gabriele Giacone
On Tue, Feb 11, 2014 at 6:04 PM, Samuel Thibault samuel.thiba...@gnu.org wrote: Gabriele Giacone, le Tue 11 Feb 2014 17:18:41 +0100, a écrit : CD says start ext2fs: panic: pmap_remove: null pv_list! Which CD? Which virtual machine startup command line? How much memory did you give it? Did you

Re: pristine-tar: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Samuel Thibault
Svante Signell, le Tue 11 Feb 2014 18:17:45 +0100, a écrit : @@ -531,6 +533,7 @@ argv[i++] = level_buf; argv[i++] = NULL; + /* FIXME: since exevp don't return exec_buf is defined static */ There is no need to make it static: execvp does not return simply because it puts

Re: heimdal: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Svante Signell
On Tue, 2014-02-11 at 18:09 +0100, Samuel Thibault wrote: Svante Signell, le Tue 11 Feb 2014 17:48:50 +0100, a écrit : uint64_t param1; uint64_t syscall; }; +#ifdef __GNU__ +/* FIXME: Enter the correct values here */ +#define _IOT_sundevdata _IOT(_IOTS(long), 7, 0, 0, 0, 0)

Re: pristine-tar: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Svante Signell
On Tue, 2014-02-11 at 18:26 +0100, Samuel Thibault wrote: Svante Signell, le Tue 11 Feb 2014 18:17:45 +0100, a écrit : @@ -531,6 +533,7 @@ argv[i++] = level_buf; argv[i++] = NULL; + /* FIXME: since exevp don't return exec_buf is defined static */ There is no need to make

Re: heimdal: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Samuel Thibault
Svante Signell, le Tue 11 Feb 2014 18:39:15 +0100, a écrit : Regarding the use of _IOT etc, I'm trying to follow the same construct as you and Pino did in bug#483281 Why not simply reading the documentation in the porting guidelines too? --- a/lib/kafs/afssys.c 2013-12-07

Re: pristine-tar: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Samuel Thibault
Svante Signell, le Tue 11 Feb 2014 18:52:28 +0100, a écrit : Maybe I got it wrong then, perhaps const would be better. Const would mean you're preventing yourself from writing to it. But you *want* to write to it with snprintf. Why do you believe you need to add something else than char*?

Re: heimdal: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Svante Signell
On Tue, 2014-02-11 at 19:21 +0100, Samuel Thibault wrote: Svante Signell, le Tue 11 Feb 2014 18:39:15 +0100, a écrit : Regarding the use of _IOT etc, I'm trying to follow the same construct as you and Pino did in bug#483281 Why not simply reading the documentation in the porting guidelines

heimdal: FTBFS on hurd-i386

2014-02-11 Thread Svante Signell
Source: heimdal Version: 1.6~git20131207+dfsg-1 Severity: important Tags: patch User: debian-hurd@lists.debian.org Usertags: hurd Hi, Currently heimdal fails to build on GNU/Hurd due to a missing definition of _IOT_sundevdata. The attached patch solves this problem by defining it with the _IOT

Re: pristine-tar: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Svante Signell
On Tue, 2014-02-11 at 19:24 +0100, Samuel Thibault wrote: Svante Signell, le Tue 11 Feb 2014 18:52:28 +0100, a écrit : Maybe I got it wrong then, perhaps const would be better. Const would mean you're preventing yourself from writing to it. But you *want* to write to it with snprintf. Why

pristine-tar: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Svante Signell
Source: pristine-tar Version: 1.30 Severity: important Tags: patch User: debian-hurd@lists.debian.org Usertags: hurd Hi, Currently pristine-tar fails to build on GNU/Hurd due to PATH_MAX not being defined. The attached patch solves this problem by calculating the needed string lengths and malloc

Re: pristine-tar: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Samuel Thibault
Svante Signell, le Tue 11 Feb 2014 19:49:46 +0100, a écrit : On Tue, 2014-02-11 at 19:24 +0100, Samuel Thibault wrote: Svante Signell, le Tue 11 Feb 2014 18:52:28 +0100, a écrit : Maybe I got it wrong then, perhaps const would be better. Const would mean you're preventing yourself from

Re: pristine-tar: FTBFS on hurd-i386 (for review)

2014-02-11 Thread Samuel Thibault
Svante Signell, le Tue 11 Feb 2014 19:55:30 +0100, a écrit : --- a/zgz/zgz.c 2013-09-04 04:15:45.0 +0200 +++ b/zgz/zgz.c 2014-02-11 19:40:43.0 +0100 That looks right. Samuel -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of

Re: New installation CDs and qemu image

2014-02-11 Thread Samuel Thibault
Gabriele Giacone, le Tue 11 Feb 2014 18:22:43 +0100, a écrit : 4 GB RAM. It seems there is an issue with more than 1856M indeed, and it would appear only while using an initrd... Perhaps grub simply puts the initrd out of reach from the kernel... Samuel -- To UNSUBSCRIBE, email to

Re: New installation CDs and qemu image

2014-02-11 Thread Samuel Thibault
Samuel Thibault, le Tue 11 Feb 2014 23:37:05 +0100, a écrit : Gabriele Giacone, le Tue 11 Feb 2014 18:22:43 +0100, a écrit : 4 GB RAM. It seems there is an issue with more than 1856M indeed, and it would appear only while using an initrd... Perhaps grub simply puts the initrd out of reach

Re: New installation CDs and qemu image

2014-02-11 Thread Santi cluke
Where i can get the new rebuilded CDs and QEMU image? 2014-02-11 9:17 GMT-03:00 Samuel Thibault samuel.thiba...@gnu.org: Hello, I've rebuilt the installation CDs and the preinstalled qemu image. Samuel -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of

Re: New installation CDs and qemu image

2014-02-11 Thread Samuel Thibault
Santi cluke, le Tue 11 Feb 2014 21:39:58 -0200, a écrit : Where i can get the new rebuilded CDs and QEMU image? The same place as usual. Samuel -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processing of gnumach_1.4-5_hurd-i386.changes

2014-02-11 Thread Debian FTP Masters
gnumach_1.4-5_hurd-i386.changes uploaded successfully to localhost along with the files: gnumach_1.4-5.dsc gnumach_1.4-5.debian.tar.bz2 gnumach-common_1.4-5_all.deb gnumach_1.4-5_hurd-i386.deb gnumach-dbg_1.4-5_hurd-i386.deb gnumach-image-1-486_1.4-5_hurd-i386.deb

gnumach_1.4-5_hurd-i386.changes ACCEPTED into unstable

2014-02-11 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 11 Feb 2014 23:10:46 + Source: gnumach Binary: gnumach gnumach-dbg gnumach-image-1-486 gnumach-image-1-xen-486 gnumach-image-1.4-486 gnumach-image-1.4-xen-486 kernel-image-1.4-486-di

Re: New installation CDs and qemu image

2014-02-11 Thread Santi cluke
Thanks Samuel, but I've searched here ( http://ftp.debian-ports.org/debian-cd/hurd-i386/current/) and the arent new versions. Thanks in advance. Diego 2014-02-11 20:42 GMT-03:00 Samuel Thibault samuel.thiba...@gnu.org: Santi cluke, le Tue 11 Feb 2014 21:39:58 -0200, a écrit : Where i can

Re: New installation CDs and qemu image

2014-02-11 Thread Samuel Thibault
Santi cluke, le Tue 11 Feb 2014 22:08:18 -0200, a écrit : Thanks Samuel, but I've searched here (http://ftp.debian-ports.org/debian-cd/ hurd-i386/current/) and the arent new versions. Snapshots have never been there. It seems I didn't keep the link to people.d.o on that page, I should have, my

Processing of gnumach_1.4-6_hurd-i386.changes

2014-02-11 Thread Debian FTP Masters
gnumach_1.4-6_hurd-i386.changes uploaded successfully to localhost along with the files: gnumach_1.4-6.dsc gnumach_1.4-6.debian.tar.bz2 gnumach-common_1.4-6_all.deb gnumach_1.4-6_hurd-i386.deb gnumach-dbg_1.4-6_hurd-i386.deb gnumach-image-1-486_1.4-6_hurd-i386.deb

gnumach_1.4-6_hurd-i386.changes ACCEPTED into unstable

2014-02-11 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 11 Feb 2014 23:47:14 + Source: gnumach Binary: gnumach gnumach-dbg gnumach-image-1-486 gnumach-image-1-xen-486 gnumach-image-1.4-486 gnumach-image-1.4-xen-486 kernel-image-1.4-486-di

Re: New installation CDs and qemu image

2014-02-11 Thread Samuel Thibault
Samuel Thibault, le Wed 12 Feb 2014 00:13:18 +0100, a écrit : Samuel Thibault, le Tue 11 Feb 2014 23:37:05 +0100, a écrit : Gabriele Giacone, le Tue 11 Feb 2014 18:22:43 +0100, a écrit : 4 GB RAM. It seems there is an issue with more than 1856M indeed, and it would appear only while