Bug#661465: Remove gnome dependencies for Debian

2012-03-17 Thread S. Sakar
The openjdk-* packages might work for Ubuntu, but that's not the Debian way. Consider a distribution X using Debian as a base and having to install gnome packages gconf, libgnome, gvfs etc. because of java.

Bug#575652: cryptsetup: init script "cryptdisks-early" fails during system halt

2010-03-31 Thread S. Sakar
Your proposed solution doesn't work with encrypted root systems which seems tricky since root is only remounted read-only. How safe would it be to ignore failed luksClose attempts ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble?

Bug#500723: Conflict with latest ATI debian packages

2008-09-30 Thread S. Sakar
Package: fglrx-driver Version: 1:8-7-2 Severity: normal hi, I've installed the latest debian packages generated from the ATI installer but they seems to conflict with the versioning of the debian ones which are older. Apt wants to upgrade to 1:8-7-2 although it's older. Please adopt a prober versi

Bug#499666: Allow encrypted loop device as root partition

2008-09-21 Thread S. Sakar
Package: initramfs-tools Version: 0.92j Severity: wishlist Tags: patch hi, i've set up an encrypted loop-AES device as the root partition (boot paramter dev=/dev/loopX) and update-initramfs fails with : mkinitramfs: missing loop root /dev/loop2 /sys entry mkinitramfs: workaround is MODULES=most m

Bug#378488: some additional ideas about a loop-aes-hook for initramfs

2007-04-10 Thread S. Sakar
hello, I've written a hook with a different approach. It is quite simple (and works only on my machine :-) ). To shortly summarize it: * don't put gpgkeys or gpghome-directories for local partitions into the initrd * provide a crypttab like file, since losetup and mount of loop-aes-utils can u

Bug#359802: hotplug scripts don't work

2006-10-21 Thread S. Sakar
Since i've changed these udev-rules (OWNER="0660", GROUP="nut") the nut daemon doesn't fail at boot anymore! The scripts don't seem to work, because the owner and permission of the usb-device (powerware 5110) are the default values, so the nut-daemon fails at boot. This could solve this one, too.