Bug#428611: boo: can't compile HelloWorld
Hello, The problem is you need to have libmono1.0-cil at runtime for booc to work. Its not a Depends, so to reproduce, you simply try to build hello.boo in a clean chroot. It is a build-depends though. While I'm not sure why this is taking place, I suspect its to do with the fact that the System.dll is in the package. A fix would simply be to add it as a dependency. Hope This Helps, Pete -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428611: boo: can't compile HelloWorld
Hello again, A closer look shows that the Depends is generated by dh_clideps. In theory, this ought to pick up the missing dep from the .exe . I'm not sure why this isn't working. Sorry for not being much help, Pete -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#430831: gallery2: Recommends line recommends two database servers
Package: gallery2 Version: 2.1.2-2 Severity: normal Tags: none The recommends line for gallery2 will drag in both postgres and mysql. This isn't needed, and should be a | instead. Thanks Pete -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages gallery2 depends on: ii apache2 2.2.3-4 Next generation, scalable, extenda ii apache2-mpm-prefork 2.2.3-4 Traditional model for Apache HTTPD ii debconf [debconf-2. 1.5.11 Debian configuration management sy ii imagemagick 7:6.2.4.5.dfsg1-0.14 Image manipulation programs ii libapache2-mod-php4 6:4.4.4-8+etch3 server-side, HTML-embedded scripti ii mysql-client-5.0 [m 5.0.32-7etch1mysql database client binaries ii php46:4.4.4-8+etch3 server-side, HTML-embedded scripti ii php4-mysql 6:4.4.4-8+etch3 MySQL module for php4 ii postgresql-client-7 1:7.4.17-0etch1 front-end programs for PostgreSQL ii wwwconfig-common0.0.48 Debian web auto configuration Versions of packages gallery2 recommends: ii dcraw8.39-1 decode raw digital camera images ii ffmpeg 0.cvs20060823-8 multimedia player, server and enco ii jhead2.60-3 manipulate the non-image part of E ii libjpeg-progs6b-13 Programs for manipulating JPEG fil ii mysql-server-4.1 5.0.32-7etch1 mysql database server (transitiona ii mysql-server-5.0 [mysql- 5.0.32-7etch1 mysql database server binaries ii php4-gd 6:4.4.4-8+etch3 GD module for php4 ii postgresql-7.4 1:7.4.17-0etch1 object-relational SQL database, ve ii unzip5.52-9 De-archiver for .zip files ii zip 2.32-1 Archiver for .zip files -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417407: debian-installer: d-i destroyed existing raid device
On Tue, Apr 03, 2007 at 08:53:24AM +0200, martin f krafft wrote: also sprach Peter Nuttall [EMAIL PROTECTED] [2007.04.03.0020 +0200]: mdadm --assemble /dev/md0 works, as does your command above. The array is fine after resyncing, its just its contents that are gone. I honestly have no idea what could have gone wrong. Can you check whether the array's UUID (mdadm -D /dev/md0) was changed or whether it's still the same as before the disaster? /etc/mdadm/mdadm.conf should list it. the UUIDs match, but the backup of /etc from before the upgrade is sitting in /home... So I can't tell you if it matches the pre-etch UUID. Pete -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417407: debian-installer: d-i destroyed existing raid device
On Tue, Apr 03, 2007 at 10:59:48AM +0200, Steinar H. Gunderson wrote: On Tue, Apr 03, 2007 at 10:39:26AM +0200, martin f krafft wrote: After the mount, both of sd[ab]1 would have to be recovered and usable, but out of sync. Actually, as Sesse claims, it's entirely likely that md didn't think the partitions were out of sync. That would explain some pretty bad data screwage. But an empty filesystem? A different scenario might be a write-intent bitmap (--bitmap= to mdadm). Do you use such a thing? No, Pete /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417407: debian-installer: d-i destroyed existing raid device
On Mon, Apr 02, 2007 at 06:45:46PM +0200, martin f krafft wrote: also sprach Peter Nuttall [EMAIL PROTECTED] [2007.04.02.1833 +0200]: If you have any questions, or I can help further, please ask. I'm psn on oftc. Any suggestions as to what I did wrong or how to recover would be really nice. Please also pass the output of /usr/share/bug/mdadm/script 31 run as root. Note that RAID superblocks and fsck -b have nothing to do with each other. Sorry, the superblocks in question are the ext3 superblocks. I have attached the output. Do you have backups? Yes, but not of stuff I have been doing for the last week or so. There are also large files that I don't have backups of, simply because I don't have the space. So I can cope without recovery, but it would be very nice to recover. Did you do anything else to the partitions? I don't recall doing anything else. What does mdadm -E output for /dev/sd[ab]1 ? Attached. Thanks for getting back to me so fast, Pete -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems --- mount output /dev/mapper/lupin-root on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) procbususb on /proc/bus/usb type usbfs (rw) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/hda1 on /boot type ext3 (rw) /dev/mapper/lupin-home on /home type ext3 (rw) /dev/mapper/lupin-tmp on /tmp type ext3 (rw) /dev/mapper/lupin-usr on /usr type ext3 (rw) /dev/mapper/lupin-var on /var type ext3 (rw) --- mdadm.conf # mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST system # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md0 level=raid1 num-devices=2 UUID=a2a5496b:fc655412:8b2b4604:32399bd7 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=859d17cf:5b01cea2:9aa94566:308b5a5d # This file was auto-generated on Mon, 02 Apr 2007 13:25:58 +0100 # by mkconf $Id: mkconf 261 2006-11-09 13:32:35Z madduck $ --- /proc/mdstat: Personalities : [raid1] md0 : active raid1 sda[0] sdb[1] 293036096 blocks [2/2] [UU] unused devices: none --- /proc/partitions: major minor #blocks name 8 0 293036184 sda 816 293036184 sdb 3 0 40146624 hda 3 1 248976 hda1 3 2 1 hda2 3 5 39897396 hda5 254 0 282624 dm-0 254 15001216 dm-1 254 23002368 dm-2 254 3 770048 dm-3 254 4 401408 dm-4 254 5 30437376 dm-5 9 0 293036096 md0 --- initrd.img-2.6.18-4-k7: 24333 blocks sbin/mdadm etc/mdadm etc/mdadm/mdadm.conf lib/modules/2.6.18-4-k7/kernel/drivers/md/raid1.ko lib/modules/2.6.18-4-k7/kernel/drivers/md/raid456.ko lib/modules/2.6.18-4-k7/kernel/drivers/md/xor.ko lib/modules/2.6.18-4-k7/kernel/drivers/md/linear.ko lib/modules/2.6.18-4-k7/kernel/drivers/md/raid0.ko lib/modules/2.6.18-4-k7/kernel/drivers/md/dm-mirror.ko lib/modules/2.6.18-4-k7/kernel/drivers/md/dm-snapshot.ko lib/modules/2.6.18-4-k7/kernel/drivers/md/dm-mod.ko lib/modules/2.6.18-4-k7/kernel/drivers/md/raid10.ko lib/modules/2.6.18-4-k7/kernel/drivers/md/multipath.ko lib/modules/2.6.18-4-k7/kernel/drivers/md/md-mod.ko scripts/local-top/mdadm --- /proc/modules: raid1 21632 1 - Live 0xd0a43000 md_mod 71060 1 raid1, Live 0xd0ac9000 dm_mirror 19600 0 - Live 0xd08de000 dm_snapshot 15904 0 - Live 0xd08e4000 dm_mod 50776 15 dm_mirror,dm_snapshot, Live 0xd0916000 --- /var/log/syslog: Apr 2 13:25:56 lupin kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 Apr 2 13:25:56 lupin kernel: md: bitmap version 4.39 Apr 2 13:26:18 lupin mdadm: DeviceDisappeared event detected on md device /dev/md1 Apr 2 13:26:18 lupin mdadm: DeviceDisappeared event detected on md device /dev/md0 Apr 2 13:26:18 lupin kernel: md: md0 stopped. Apr 2 13:26:18 lupin kernel: md: bindsda Apr 2 13:26:18 lupin kernel: md: bindsdb Apr 2 13:26:18 lupin kernel: md: kicking non-fresh sda from array! Apr 2 13:26:18 lupin kernel: md: unbindsda Apr 2 13:26:18 lupin kernel: md: export_rdev(sda) Apr 2 13:26:18 lupin kernel: md: raid1 personality registered for level 1 Apr 2 13:26:18 lupin kernel: md: md1 stopped. Apr 2 13:26:29 lupin mdadm: DegradedArray event
Bug#417407: debian-installer: d-i destroyed existing raid device
On Mon, Apr 02, 2007 at 11:46:02PM +0200, martin f krafft wrote: Can you force-start the degraded array, using something like mdadm --assemble --auto=yes --force /dev/md0 /dev/sd[ab]1 mdadm --run /dev/md0 ? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems mdadm --assemble /dev/md0 works, as does your command above. The array is fine after resyncing, its just its contents that are gone. Pete -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392811: patch to support proxies in caff
Package: signing-party
Version: 0.4.8
Hello,
Since caff doesn't seem to support proxies, and gpg does, I have
patched caff to have a keyserver-options bit in .caffrc and to pass
that to gpg. The patch is against the 0.4.8 tarball. I can patch the
development version as well if you like.
Thanks
Pete
--- signing-party-0.4.8/caff/caff 2006-10-13 16:52:46.178998088 +0100
+++ caff2006-10-13 16:53:19.549924936 +0100
@@ -405,6 +405,10 @@
# Select this/these keys to sign with
#\$CONFIG{'local-user'} = [ [EMAIL PROTECTED] ];
+# If you want to pass keyserver options to gpg, for example if you wish to use
a proxy, do this:
+# \$CONFIG{'keyserver-options'} =['http-proxy=http://wwwcache:8080/;'];
+
+
# Additionally encrypt messages for these keyids
#\$CONFIG{'also-encrypt-to'} = [ [EMAIL PROTECTED] ];
@@ -459,6 +463,11 @@
@{$CONFIG{'keyid'}} = map { uc } @{$CONFIG{'keyid'}};
$CONFIG{'export-sig-age'}= 24*60*60 unless defined
$CONFIG{'export-sig-age'};
$CONFIG{'keyserver'} = 'subkeys.pgp.net' unless defined
$CONFIG{'keyserver'};
+ if (defined $CONFIG{'keyserver-options'}){
+ $CONFIG{'keyserver-options'} = ['--keyserver-options',
@{$CONFIG{'keyserver-options'}}];
+ } else {
+ $CONFIG{'keyserver-options'} = [];
+ } ;
$CONFIG{'gpg'} = 'gpg' unless defined $CONFIG{'gpg'};
$CONFIG{'gpg-sign'} = $CONFIG{'gpg'} unless defined $CONFIG{'gpg-sign'};
$CONFIG{'gpg-delsig'} = $CONFIG{'gpg'} unless defined
$CONFIG{'gpg-delsig'};
@@ -984,7 +993,7 @@
$gpg-call( $CONFIG{'gpg'} );
$gpg-options-hash_init(
'homedir' = $GNUPGHOME,
- 'extra_args' = [ qw{ --no-auto-check-trustdb
--trust-model=always }, '--keyserver='.$CONFIG{'keyserver'} ] );
+ 'extra_args' = [ qw{ --no-auto-check-trustdb
--trust-model=always }, '--keyserver='.$CONFIG{'keyserver'},
@{$CONFIG{'keyserver-options'}} ]);
$gpg-options-meta_interactive( 0 );
my ($inputfd, $stdoutfd, $stderrfd, $statusfd, $handles) =
make_gpg_fds();
my $pid = $gpg-recv_keys(handles = $handles, command_args = [
@KEYIDS ]);
