Accepted devmapper 2:1.02.18-1ubuntu1 (source)

Scott James Remnant scott at ubuntu.com
Mon May 21 19:40:10 BST 2007


Accepted:
 OK: devmapper_1.02.18-1ubuntu1.dsc
     -> Component: main Section: admin
 OK: devmapper_1.02.18.orig.tar.gz
 OK: devmapper_1.02.18-1ubuntu1.diff.gz

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 21 May 2007 18:17:48 +0100
Source: devmapper
Binary: dmsetup libdevmapper1.02.1-udeb libdevmapper-dev libdevmapper1.02.1 dmsetup-udeb
Architecture: source
Version: 2:1.02.18-1ubuntu1
Distribution: gutsy
Urgency: low
Maintainer: Debian LVM Team <pkg-lvm-maintainers at lists.alioth.debian.org>
Changed-By: Scott James Remnant <scott at ubuntu.com>
Description: 
 dmsetup    - The Linux Kernel Device Mapper userspace library
 dmsetup-udeb - The Linux Kernel Device Mapper userspace library
 libdevmapper-dev - The Linux Kernel Device Mapper header files
 libdevmapper1.02.1 - The Linux Kernel Device Mapper userspace library
 libdevmapper1.02.1-udeb - The Linux Kernel Device Mapper userspace library
Changes: 
 devmapper (2:1.02.18-1ubuntu1) gutsy; urgency=low
 .
   * Merge from debian unstable, remaining changes:
     - copy po/device-mapper.po to device-mapper.pot so Rosetta has a POT
       file to import
 .
   * udev-lvm-mdadm-evms-gutsy:
     - Revert changes made during the feisty development cycle; while a
       valiant effort, we introduced just as many problems as we fixed.
     - Demote dmsetup (and dmsetup-udeb) from Depends to a Recommends, since
       we do tend to install those by default and there's no ordering problem
       anymore.
     - Apply patch from SuSE that adds an "export" option that will give udev
       the full device status of each dm device, including whether it's
       actually active or not.
     - Modify the udev rules we include; these now check the device state,
       set the /dev/mapper target as symlink to the kernel name (which HAL
       expects), and create the by-id, by-uuid and by-label devices itself.
     - Since both udev and devmapper might be creating the /dev/mapper device
       node, it's possible it can appear between our stat() and mknod() calls.
       So if mknod() returns EEXIST, do the stat again; also check lstat in
       case there's a hanging symlink there.
 .
 devmapper (2:1.02.18-1) unstable; urgency=low
 .
   * New upstream version.
   * Bump abiname.
 .
 devmapper (2:1.02.12-1) unstable; urgency=low
 .
   * New upstream version.
     - Don't suspend device which is already suspended.
Files: 
 4429056309e7876f50abdb8da4a713fe 772 admin optional devmapper_1.02.18-1ubuntu1.dsc
 26fd2df4f6dca1a6d26820498447ef45 183975 admin optional devmapper_1.02.18.orig.tar.gz
 fd4c0f3a786011703ed0670583e9786f 19116 admin optional devmapper_1.02.18-1ubuntu1.diff.gz
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGUeagSnQiFMl4yK4RAgUeAJ9bK/9JrT4dULfcPYKF8jRmVNTNhwCfUQWl
KcKKk3+5Fecm9kNe6AOdOR4=
=uYnd
-----END PGP SIGNATURE-----





More information about the gutsy-changes mailing list