Bug#551600: [mdadm] package error?

[richard lucassen]

I compiled mdadm from source (unstable) and there's no problem to
install the package (mdadm_3.0-3.1)

OTOH, talking about udev, yesterday an upgrade simply renamed the file:

/etc/udev/rules.d/91-permissions.rules 

to

/etc/udev/rules.d/91-permissions.rules.dpkg-old

which changed the permission/ownership of some devices and made them
unaccessible for normal users.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#551600: [mdadm] package error?

[richard lucassen]

Package: mdadm
Version: 3.0-2


This morning, using the usual apt-get update; apt-get dist-upgrade the
package mdadm was removed from testing. When trying to reinstall
mdadm, this happens:

# apt-get install mdadm
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer
required:  dnsmasq-base libass3 xorg-docs-core libnm-glib-vpn0 ppp
libparted1.8-12 Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  alsa-base alsa-utils gnome-mount gnome-power-manager
gnome-volume-manager  gparted hal hal-cups-utils initramfs-tools
linux-image-2.6-amd64  linux-image-2.6.26-2-amd64
linux-image-2.6.30-2-amd64 network-manager  network-manager-gnome
sound-juicer udev xorg xserver-xorg xserver-xorg-core 
xserver-xorg-input-all xserver-xorg-input-evdev xserver-xorg-input-kbd 
xserver-xorg-input-mouse xserver-xorg-input-synaptics 
xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-apm 
xserver-xorg-video-ark xserver-xorg-video-ati xserver-xorg-video-chips 
xserver-xorg-video-cirrus xserver-xorg-video-dummy
xserver-xorg-video-fbdev  xserver-xorg-video-glint
xserver-xorg-video-i128 xserver-xorg-video-intel 
xserver-xorg-video-mach64 xserver-xorg-video-mga
xserver-xorg-video-neomagic  xserver-xorg-video-nv
xserver-xorg-video-openchrome xserver-xorg-video-r128 
xserver-xorg-video-radeon xserver-xorg-video-radeonhd 
xserver-xorg-video-rendition xserver-xorg-video-s3 
xserver-xorg-video-s3virge xserver-xorg-video-savage 
xserver-xorg-video-siliconmotion xserver-xorg-video-sis 
xserver-xorg-video-sisusb xserver-xorg-video-tdfx xserver-xorg-video-tga
 xserver-xorg-video-trident xserver-xorg-video-tseng
xserver-xorg-video-v4l  xserver-xorg-video-vesa
xserver-xorg-video-vmware xserver-xorg-video-voodoo The following NEW
packages will be installed:  mdadm
0 upgraded, 1 newly installed, 59 to remove and 0 not upgraded.
Need to get 433kB of archives.
After this operation, 220MB disk space will be freed.
Do you want to continue [Y/n]? n
Abort.

I like the CLI, but I suppose this is not what installing mdadm should
cause.

R.

-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
| Public key and email address:|
| http://www.lucassen.org/mail-pubkey.html |
+--+



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#551600: [mdadm] package error?

[Adrian Zaugg]

This is because of #541884. It should have been fixed in mdadm
(3.0-3.1), which didn't get into testing because of new bugs. That means
someone who dist-upgrades testing right now, breaks its system. There is
a warning displayed by udev during installation, but at this time it may
already be too late.

Could this be prevented somehow? Could mdmad (3.0-2) be altered to
conflict/break/whatever with udev (146-1) and higher?

Regards, Adrian.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org