Your message dated Sun, 29 Oct 2006 02:02:14 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#393314: fixed in mdadm 2.5.5-1 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: mdadm_2.5.4-1 These builds fail like this: gcc -Wall -Werror -Wstrict-prototypes -ggdb -fomit-frame-pointer -Os -DSendmail=\""/usr/sbin/sendmail -t"\" -DCONFFILE=\"/tmp/mdadm.conf\" -DCONFFILE2=\"/etc/mdadm.conf\" -DDEBIAN -c -o util.o util.c In file included from util.c:34: /usr/include/linux/blkpg.h:36: error: expected ':', ',', ';', '}' or '__attribute__' before '*' token util.c: In function 'remove_partitions': util.c:132: error: 'struct blkpg_ioctl_arg' has no member named 'data' util.c:135: error: 'struct blkpg_ioctl_arg' has no member named 'data' make[2]: *** [util.o] Error 1 make[2]: Leaving directory /build/buildd/mdadm-2.5.4' The code in util.c is this: struct blkpg_ioctl_arg a; struct blkpg_partition p; 131 a.op = BLKPG_DEL_PARTITION; 132 a.data = (void*)&p; 133 a.datalen = sizeof(p); 134 a.flags = 0; 135 memset(a.data, 0, a.datalen); for (p.pno=0; p.pno < 16; p.pno++) ioctl(fd, BLKPG, &a); in /usr/inlcude/linux/blkpg.h we have: struct blkpg_ioctl_arg { int op; int flags; int datalen; void __user *data; }; It looks like __user is causing a problem. If I delete it then util.c builds OK. __user is defined in linux/compiler.h #ifdef __CHECKER__ # define __user __attribute__((noderef, address_space(1))) #else # define __user If I set it to __attribute__((noderef, address_space(1))) in blkpg.h then that build OK too. So I really don't understand what gcc is whinging about. I suspect this is really a gcc bug. What do the threee arches it breaks on have in common? Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://wookware.org/
--- End Message ---
--- Begin Message ---Source: mdadm Source-Version: 2.5.5-1 We believe that the bug you reported is fixed in the latest version of mdadm, which is due to be installed in the Debian FTP archive: mdadm-udeb_2.5.5-1_amd64.udeb to pool/main/m/mdadm/mdadm-udeb_2.5.5-1_amd64.udeb mdadm_2.5.5-1.diff.gz to pool/main/m/mdadm/mdadm_2.5.5-1.diff.gz mdadm_2.5.5-1.dsc to pool/main/m/mdadm/mdadm_2.5.5-1.dsc mdadm_2.5.5-1_amd64.deb to pool/main/m/mdadm/mdadm_2.5.5-1_amd64.deb mdadm_2.5.5.orig.tar.gz to pool/main/m/mdadm/mdadm_2.5.5.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. martin f. krafft <[EMAIL PROTECTED]> (supplier of updated mdadm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 26 Oct 2006 22:35:24 +0200 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source amd64 Version: 2.5.5-1 Distribution: unstable Urgency: low Maintainer: Debian mdadm maintainers <[EMAIL PROTECTED]> Changed-By: martin f. krafft <[EMAIL PROTECTED]> Description: mdadm - tool to administer Linux MD arrays (software RAID) mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb) Closes: 393314 Changes: mdadm (2.5.5-1) unstable; urgency=low . * New upstream release: - fixes the build problems on several architectures (closes: #393314) by including the contents of linux/blkpg.h literally, not via #include. - optimises bitmap file use on 64bit systems. - does not error out anymore when trying to assemble an already assembled array without a corresponding /dev device node. - does not report an error if --assemble --scan only finds already running arrays. - fixes several bugs related to RAID10 and the new offset layout. - improves error message when a wrong '--update' option is given. * Added FAQ entries about partitionable arrays. * chroot detection now also works for 2.6.18 and beyond (c.f. kernel commit 778c1144771f0064b6f51bee865cceb0d996f2f9). * Now recommends module-init-tools. * Hides ugly errors during configuration in the absense of module-init-tools or initramfs-tools. * Send udev events for arrays assembled by the mdadm-raid init.d script. This does not close #394193 but it's a good addition anyway. I am not sending these events from the initramfs as well because it would be non-trivial to ensure that an event doesn't get sent twice for a given array. Anyway, this is all a hack until the kernel sends online/offline events to udev. See #394193. * Added more RAID10 information to the FAQ. * Added filters to logcheck for regular events, even by the md driver; also promoted messages about non-fresh components to security events. * Hide informational messages unless VERBOSE is set to a true value in /etc/default/mdadm. Files: a8a9583d2c654f71abc011cb0ce5282e 765 admin optional mdadm_2.5.5-1.dsc c3198e42a8f38f3998e5578cc3956728 179777 admin optional mdadm_2.5.5.orig.tar.gz 832eb19badcd82e84fc6bcd29836fa81 100108 admin optional mdadm_2.5.5-1.diff.gz 4bebb0b51adab63f057d6cb073598463 222492 admin optional mdadm_2.5.5-1_amd64.deb 0afe92508fdb6ce845ccbbbbc66b46a6 70892 debian-installer optional mdadm-udeb_2.5.5-1_amd64.udeb Package-Type: udeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFRHX8IgvIgzMMSnURAseWAJ4w+zxN2PPH1bBNVMYdvNYUGPKh0QCgqtsy BTMUlf+ggd6fc7vYsFFHaAw= =4CMO -----END PGP SIGNATURE-----
--- End Message ---
