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

Format: 1.7
Date: Fri, 17 Nov 2006 15:31:05 +0000
Source: lilo
Binary: lilo-doc lilo
Architecture: source i386 all
Version: 1:22.6.1-9
Distribution: unstable
Urgency: high
Maintainer: Andrés Roldán <[EMAIL PROTECTED]>
Changed-By: Andrés Roldán <[EMAIL PROTECTED]>
Description: 
 lilo       - LInux LOader - The Classic OS loader can load Linux and others
 lilo-doc   - Documentation for LILO (LInux LOader)
Closes: 354360
Changes: 
 lilo (1:22.6.1-9) unstable; urgency=high
 .
   * Upload thanks to Julian Hernandez <[EMAIL PROTECTED]>
   * Urgency set to high because liloconfig (and hence update-lilo) failed when
     selecting the desired bitmap and the file /etc/lilo.conf was generated
     incorrectly.
   * debian/liloconfig:
     - Now the bitmap list can be selected using debconf and now liloconfig 
will work.
     - Now liloconfig saves a backup file of the configuration before writing a
       new one.
   * debian/control:
     - Change section of lilo package from base to admin
     - mbr package is now a dependency to make liloconfig run smoothly.
   * debian/watch:
     - Updated to use the new upstream URL. (Closes: #354360)
Files: 
 c1db33a9f8032bf87e95e209de833f0d 731 admin optional lilo_22.6.1-9.dsc
 0d456c8436a45f148f0d23a7678bb4fd 184772 admin optional lilo_22.6.1-9.diff.gz
 2521feda0abd9f7459c1be16b1804bd4 349196 admin optional lilo_22.6.1-9_i386.deb
 54d876563e92dd2432c2883d625fe77b 225656 doc optional lilo-doc_22.6.1-9_all.deb

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

iD8DBQFFXdqN2OByS7KTlusRApH6AJ0Ul3LBh30dbBXSVvtxCtRFWTck0ACdEXFk
Nnr1SJ5+kCUWwKQt1eyq7Zs=
=WCdV
-----END PGP SIGNATURE-----


Accepted:
lilo-doc_22.6.1-9_all.deb
  to pool/main/l/lilo/lilo-doc_22.6.1-9_all.deb
lilo_22.6.1-9.diff.gz
  to pool/main/l/lilo/lilo_22.6.1-9.diff.gz
lilo_22.6.1-9.dsc
  to pool/main/l/lilo/lilo_22.6.1-9.dsc
lilo_22.6.1-9_i386.deb
  to pool/main/l/lilo/lilo_22.6.1-9_i386.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to