Re: Listing the "Debian Installer internals" manual on http://www.debian.org/doc/devel-manuals ?
Charles Plessy, le Wed 20 Mar 2013 11:33:24 +0900, a écrit : > how about listing the "Debian Installer internals" manual on > http://www.debian.org/doc/devel-manuals ? That can probably be useful, as we now and then get people asking how to work with the installer, even if that's indeed documented. > If you like the idea I can propose a patch or commit directly. Please commit. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320095211.gc6...@type.bordeaux.inria.fr
Bug#703404: debian-installer: wheezy (PXE boot) failes to install busybox and kernel
from the various contributions, it is not clear (to me) whether or not this has any conclusion. Is there a way to avoid this problem during installation? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caf2nc0z9awaberon6ntqhlvjw4bcxvbfbsoicbhzt7k5t_s...@mail.gmail.com
Re: Torrents
Mariano wrote: > >On 03/20/2013 02:36 AM, Mariano Lazzaro wrote: >> Hi, I was wondering if there is a way to download Debian >> CDs/DVDs/Blu-rays via torrents, because I consider that way easier >> than any other alternative, since torrents nowadays are very widely used. >> >> This would also contribute greatly to the Debian Project because it >> would reduce bandwidth usage from Debian Mirrors, so users help users >> and becomes a true community effort by using torrents. >> >> Thanks for reading, thanks for your time. > >I correct myself, because I found torrents for CDs/DVDs. > >The only thing I'm missing now is torrents for Debian 6 & 7 but for the >Blu-ray discs. > >I would greatly appreciate having those torrents in that format. So far we've not had enough demand for the Blu-ray media to make it worth keeping the ISO images around and on the mirrors infrastructure, and hence we also can't support torrents. CDs and DVDs get *hugely* more downloads in comparison. If you do want the Blu-ray images, the jigdo files are available. -- Steve McIntyre, Cambridge, UK.st...@einval.com "It's actually quite entertaining to watch ag129 prop his foot up on the desk so he can get a better aim." [ seen in ucam.chat ] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1uijqr-0005q3...@mail.einval.com
Bug#703404: more infos
I'm not a debian-installer expert, but these observations might very well help to resolve the issue: - PXE boot with current installer (no additional boot args whatsoever) mine is wheezy amd64 linux md5sum: dbd20c0b342e9a25747fb6a02d58f47b initrd.gz md5sum: ef5ccd9303d785db46b33e8cc3b150ce - "Normal" interactive install (I chose ftp.de.debian.org as mirror) - Continue until busybox fails to install (the problem apparent in syslog is failure to authenticate the mirror) - Now my observations on VT2: The Release and Release.gpg downloaded from the selected mirror are in /target/var/lib/apt/lists, and /target/var/lib/apt/lists/partial, respectively. Oddly, the Release file is the text file from ftp.de.debian.org/debian/dists/wheezy/Release, *but with integrated PGP signature added*. I don't know at what stage this got added, but it is clear that the verification has to fail (because the Release.gpg signs the ungarbled Release file, not one with its own signature added). $ chroot /target apt-get -o 'Debug::Acquire::gpgv' update inside VerifyGetSigners gpgv path: /usr/bin/gpgv Keyring file: /etc/apt/trusted.gpg Keyring path: /etc/apt/trusted.gpg.d/ Preparing to exec: /usr/bin/gpgv /usr/bin/gpgv --ignore-time-conflict --status-fd 3 --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg --ignore-time-conflict /var/lib/apt/lists/partial/ftp.de.debian.org_debian_dists_wheezy_Release.gpg /var/lib/apt/lists/ftp.de.debian.org_debian_dists_wheezy_Release Read: [GNUPG:] BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze) Got BADSIG! gpgv exited W: GPG error: http://ftp.de.debian.org wheezy Release: The following signatures were invalid: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze) >From the above output, we see that the aforementioned Release and Release.gpg are used to verify the mirror. But the local Release file (which as some point was changed to be different than the one on the mirror), as mentioned, is not the one which the Release.gpg signs. By doing the following at the right point(s?), I have already managed to get a working installation: $ rm /target/var/lib/apt/lists/ftp.de.debian.org_debian_dists_wheezy_Release $ chroot /target apt-get update # Shouldn't fail anymore with BADSIG. Clearly this is nothing to add to the installer scripts, but I guess it might help towards detecting the problem. Have a nice day Jens Stimpfle -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320133030.ga3...@jstimpfle.de
Re: Listing the "Debian Installer internals" manual on http://www.debian.org/doc/devel-manuals ?
Le Wed, Mar 20, 2013 at 10:52:11AM +0100, Samuel Thibault a écrit : > Charles Plessy, le Wed 20 Mar 2013 11:33:24 +0900, a écrit : > > how about listing the "Debian Installer internals" manual on > > http://www.debian.org/doc/devel-manuals ? > > That can probably be useful, as we now and then get people asking how to > work with the installer, even if that's indeed documented. > > > If you like the idea I can propose a patch or commit directly. > > Please commit. Thanks for the feedback. Here is the patch that I am ready to commit in the absence of suggestions of problems. Index: devel-manuals.wml === RCS file: /cvs/webwml/webwml/english/doc/devel-manuals.wml,v retrieving revision 1.65 diff -u -r1.65 devel-manuals.wml --- devel-manuals.wml 29 Aug 2012 21:41:56 - 1.65 +++ devel-manuals.wml 20 Mar 2013 13:56:08 - @@ -257,3 +257,25 @@ + + + + + + + This document is intended to make Debian Installer more accessible to new + developers and as a central location to document technical information. + + + + + + ready + + + http://d-i.alioth.debian.org/doc/internals/";>HTML online. + http://anonscm.debian.org/viewvc/d-i/trunk/manual/";>DocBook source online. + + + + Index: index.wml === RCS file: /cvs/webwml/webwml/english/doc/index.wml,v retrieving revision 1.97 diff -u -r1.97 index.wml --- index.wml 26 Jan 2013 00:54:29 - 1.97 +++ index.wml 20 Mar 2013 13:56:08 - @@ -96,6 +96,7 @@ Debian Project History Debiandoc-SGML Markup Manual Debian SGML/XML HOWTO + Debian Installer internals Cheers, -- Charles > > Samuel > > > -- > To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20130320095211.gc6...@type.bordeaux.inria.fr -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320135808.ga...@falafel.plessy.net
Re: Torrents
On Wed, Mar 20, 2013 at 02:36:17AM -0300, Mariano Lazzaro wrote: > Hi, I was wondering if there is a way to download Debian > CDs/DVDs/Blu-rays via torrents, because I consider that way easier > than any other alternative, since torrents nowadays are very widely > used. > > This would also contribute greatly to the Debian Project because it > would reduce bandwidth usage from Debian Mirrors, so users help > users and becomes a true community effort by using torrents. > > Thanks for reading, thanks for your time. The debian mirrors have vastly better bandwidth than people running bittorrent. Also bittorrent is not an efficient distribution method compared to a good distribution network which Debian has. Remember Debian's mirrors are different companies and universities donating rack space and bandwidth (and often servers) to the Debian project. It isn't costing Debian anything. jigdo on the other hand is briliant since it means the mirrors don't have to waste space on the iso images, but instead just store the packages everyone uses anyhow. https://www.kernel.org/doc/ols/2008/ols2008v1-pages-173-182.pdf is a great presentation on why bittorrent isn't a good idea for large scale distribution (it is fine for small projects that don't have a good way to distribute things). But I do believe debian does have bittorrent available, but it's a waste of time to use compared to jigdo -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320135823.gf1...@csclub.uwaterloo.ca
Re: How to make USB as Installer debian 5
On Wed, Mar 20, 2013 at 09:52:34AM +0800, Jeffry Liuw wrote: > Dear Debian Developer, > > I want to make USB as Installer debian 5. Can you help me please, in > which way to make that ? > > I need to installing Debian on my SONY VIAO using USB for flexibility. > > Thank in advanced Debian 5 as in the one that hasn't been supported for quite a while? Well I know for the current Debian 6, you should be able to just dd the install image to a usb key and boot it. For older releases something like http://unetbootin.sourceforge.net/ should work. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320140928.gi1...@csclub.uwaterloo.ca
Bug#703146: apt: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze)?
Hi, to be more precise abouti my previous message (#44), here is a log of what happened while running lb config --architectures i386 ; sudo lb build http://paste.debian.net/243117/ Interesting lines are 791, 845, 863, 911, 915. By the way, may this bug be related to #614029 ? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614029 Ciao, Thierry -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320155013.ga14...@dontexist.metelu.net
PGP signature problems with firmware ISO images
Hi all, Hopefully this is the correct list to report this, if not, I'd appreciate it if you could point me in the right direction. There seem to be problems with the PGP signatures for the debian-installer ISO images including non-free firmware hosted here: http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/ Some of the images, such as wheezy_di_rc1, have no signatures (no .sign files present). Others, such as the "current" images dated 2013-02-23/2013-02-24, seem to have an invalid signature (I am verifying against keys in the debian-keyring 2012.11.15 package from wheezy): david@spongebob:~/Downloads$ gpg2 -v --keyring /usr/share/keyrings/debian-role-keys.gpg -v SHA256SUMS.sign gpg: armor: BEGIN PGP SIGNATURE Version: GnuPG v1.4.12 (GNU/Linux) :signature packet: algo 1, keyid DA87E80D6294BE9B version 4, created 1361115854, md5len 0, sigclass 0x00 digest algo 8, begin of digest 69 3e hashed subpkt 2 len 4 (sig created 2013-02-17) subpkt 16 len 8 (issuer key ID DA87E80D6294BE9B) data: [4096 bits] gpg: armor header: gpg: assuming signed data in `SHA256SUMS' gpg: Signature made sun 17.feb 2013, 15:44:14 GMT using RSA key ID 6294BE9B gpg: using PGP trust model gpg: key 372523E0: accepted as trusted key gpg: BAD signature from "Debian CD signing key " gpg: binary signature, digest algorithm SHA256 For now, I'll hold off on installing these images, but it would be great to get this fixed, as I have some hardware that requires a firmware blob for the ethernet card. PS: I'm not subscribed to the list, so in case you need more information, please contact me directly. Best regards, Davíð Steinn Geirsson da...@dsg.is signature.asc Description: PGP signature
Bug#703404: Also encountered this during a testing netinstall.
I ran into this problem too. I was doing a netinstall of Debian 'testing' (having booted from a USB stick created by "zcat boot.img.gz > /dev/sdb", then mounting, then running unetbootin on the same stick). Early in the "Install the base system" stage, using the text (ncurses? non-graphical, anyway) installer, my screen went red and the dialog box showed this error: |Unable to install busybox | | An error was returned while trying to install the busybox package | onto the target system. | | Check /var/log/syslog or see virtual console 4 for details. | | I looked on virtual console 4, and as expected, it got an error while trying to install the busybox package: WARNING: The following packages cannot be authneticated! busybox E: There are problems and -y was used without --force-yes base-installer: error: \ exiting on error base-installer/kernel/failed-package-install I don't want to just force it through by ignoring the bad signature, as I thought the whole point of the signature system is that something might be wrong (e.g., in the worst case, that some third party has tampered with the busybox package). When a sig fails, what's the standard procedure by the package maintainers? [I don't quite understand the solutions others in this thread used. For example Tycho Lürsen said "I finaly have a working system, but I had to switch mirrors twice during installation. After the reboot, I still could not use my system. I had to remove 'debian-archive-keyring' (witch is not allowed unless you force it to) and replace it with the proper one, reinstall apt, etc." Not sure what he meant by "replace it with the proper one", though.] I'm happy to provide more info if it'll help solve this, but suspect my report is just a "me too". -Karl -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8738vqf1x1@kwarm.red-bean.com
Re: PGP signature problems with firmware ISO images
da...@dsg.is wrote: > >Hopefully this is the correct list to report this, if not, I'd >appreciate it if you could point me in the right direction. Here's OK; I'm the person who signs things... :-) I've taken a look directly on the cdimage server at your problem reports. >There seem to be problems with the PGP signatures for the >debian-installer ISO images including non-free firmware hosted here: >http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/ > >Some of the images, such as wheezy_di_rc1, have no signatures (no .sign >files present). Gah, apologies for that. It looks like I forgot to put the signatures in place there. I'll fix that right now. >Others, such as the "current" images dated >2013-02-23/2013-02-24, seem to have an invalid signature (I am >verifying against keys in the debian-keyring 2012.11.15 package from >wheezy): > >david@spongebob:~/Downloads$ gpg2 -v >--keyring /usr/share/keyrings/debian-role-keys.gpg -v SHA256SUMS.sign >gpg: armor: BEGIN PGP SIGNATURE Version: GnuPG v1.4.12 (GNU/Linux) >:signature packet: algo 1, keyid DA87E80D6294BE9B >version 4, created 1361115854, md5len 0, sigclass 0x00 >digest algo 8, begin of digest 69 3e >hashed subpkt 2 len 4 (sig created 2013-02-17) >subpkt 16 len 8 (issuer key ID DA87E80D6294BE9B) >data: [4096 bits] >gpg: armor header: >gpg: assuming signed data in `SHA256SUMS' >gpg: Signature made sun 17.feb 2013, 15:44:14 GMT using RSA key ID >6294BE9B gpg: using PGP trust model >gpg: key 372523E0: accepted as trusted key >gpg: BAD signature from "Debian CD signing key >" gpg: binary signature, digest algorithm >SHA256 This I cannot reproduce at all; I've checked all the signatures just now and they verify OK. I think you've got a mix of files from two places there: all of the signature files are dated "Feb 24 00:42" but you've got a file claiming the sig was made "sun 17.feb 2013, 15:44:14 GMT". Checking the timestamps of other .sign files on the server, that's most likely one from the main wheezy d-i RC1 release as far as I can tell. -- Steve McIntyre, Cambridge, UK.st...@einval.com "It's actually quite entertaining to watch ag129 prop his foot up on the desk so he can get a better aim." [ seen in ucam.chat ] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1uinak-0002jp...@mail.einval.com
Re: PGP signature problems with firmware ISO images
Hi, On Wed, 20 Mar 2013 17:51:34 + Steve McIntyre wrote: > da...@dsg.is wrote: > > > >Hopefully this is the correct list to report this, if not, I'd > >appreciate it if you could point me in the right direction. > > Here's OK; I'm the person who signs things... :-) I've taken a look > directly on the cdimage server at your problem reports. > > >There seem to be problems with the PGP signatures for the > >debian-installer ISO images including non-free firmware hosted here: > >http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/ > > > >Some of the images, such as wheezy_di_rc1, have no signatures > >(no .sign files present). > > Gah, apologies for that. It looks like I forgot to put the signatures > in place there. I'll fix that right now. > Thanks. > >Others, such as the "current" images dated > >2013-02-23/2013-02-24, seem to have an invalid signature (I am > >verifying against keys in the debian-keyring 2012.11.15 package from > >wheezy): > > > >david@spongebob:~/Downloads$ gpg2 -v > >--keyring /usr/share/keyrings/debian-role-keys.gpg -v SHA256SUMS.sign > >gpg: armor: BEGIN PGP SIGNATURE Version: GnuPG v1.4.12 (GNU/Linux) > >:signature packet: algo 1, keyid DA87E80D6294BE9B > >version 4, created 1361115854, md5len 0, sigclass 0x00 > >digest algo 8, begin of digest 69 3e > >hashed subpkt 2 len 4 (sig created 2013-02-17) > >subpkt 16 len 8 (issuer key ID DA87E80D6294BE9B) > >data: [4096 bits] > >gpg: armor header: > >gpg: assuming signed data in `SHA256SUMS' > >gpg: Signature made sun 17.feb 2013, 15:44:14 GMT using RSA key ID > >6294BE9B gpg: using PGP trust model > >gpg: key 372523E0: accepted as trusted key > >gpg: BAD signature from "Debian CD signing key > >" gpg: binary signature, digest algorithm > >SHA256 > > This I cannot reproduce at all; I've checked all the signatures just > now and they verify OK. I think you've got a mix of files from two > places there: all of the signature files are dated "Feb 24 00:42" but > you've got a file claiming the sig was made "sun 17.feb 2013, 15:44:14 > GMT". Checking the timestamps of other .sign files on the server, > that's most likely one from the main wheezy d-i RC1 release as far as > I can tell. > Yes, I was a bit hasty there, I had an older SHA256SUMS.sign file that I was verifying; wget downloaded the new one to SHA256SUMS.sign.1. Sorry about the false alarm. Thanks again for the prompt response. Best regards, Davíð Steinn Geirsson da...@dsg.is signature.asc Description: PGP signature
Bug#703146: #703146 release critical?
I just installed a new wheezy machine as my brand new "garage" build server and got hit by #703146. No way to create cowbuilder/pbuilder chroots. The patch in #703146 does indeed fix the issue. Shouldn't this definitely go in wheezy? -- signature.asc Description: Digital signature
Bug#703146: #703146 release critical?
Quoting Christian PERRIER (bubu...@debian.org): > I just installed a new wheezy machine as my brand new "garage" build > server and got hit by #703146. No way to create cowbuilder/pbuilder > chroots. > > > The patch in #703146 does indeed fix the issue. > > Shouldn't this definitely go in wheezy? I have an upload ready that includes MIchael Vogt's patch and moves gpg from Recommends to Depends. Please object if I shouldn't upload. This upload allows pbuilder to build a build chroot, so it seems fine, but, not being a wizard with debootstrap and archive stuff, I'd appreciate someone to confirm that fixing this is OK and fixing it the way it has been proposed in #703146 is OK too. signature.asc Description: Digital signature
Re: Bug#703146: #703146 release critical?
Hi Christian, On Mittwoch, 20. März 2013, Christian PERRIER wrote: > I have an upload ready that includes MIchael Vogt's patch and moves > gpg from Recommends to Depends. does it include the -f option as needed for live-$something? (see this bugs log) > Please object if I shouldn't upload. > > This upload allows pbuilder to build a build chroot, so it seems fine, > but, not being a wizard with debootstrap and archive stuff, I'd > appreciate someone to confirm that fixing this is OK and fixing it the > way it has been proposed in #703146 is OK too. a debdiff to the version in wheezy would have been nice :) cheers, Holger -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201303201716.51453.hol...@layer-acht.org
Re: How to make USB as Installer debian 5
On Wed 20 Mar 2013 at 10:09:28 -0400, Lennart Sorensen wrote: > On Wed, Mar 20, 2013 at 09:52:34AM +0800, Jeffry Liuw wrote: > > Dear Debian Developer, > > > > I want to make USB as Installer debian 5. Can you help me please, in > > which way to make that ? > > > > I need to installing Debian on my SONY VIAO using USB for flexibility. > > > > Thank in advanced > > Debian 5 as in the one that hasn't been supported for quite a while? > > Well I know for the current Debian 6, you should be able to just dd the > install image to a usb key and boot it. > > For older releases something like http://unetbootin.sourceforge.net/ > should work. As a point of interest, it is possible to fiddle with a Lenny netinst ISO and turn it into an isohybrid which can be dd'ed or cat'ed to a USB stick. However, as you suggest, UNetbootin or something similar should be able to cope with it. Reading the Manual might not be a bad idea either. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320224129.GC32477@desktop
Bug#703581: unblock: e2fsprogs/1.42.5-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package e2fsprogs Closes #698879 This is also a request for udeb-unblock from the installer team. unblock e2fsprogs/1.42.5-1.1 - -- System Information: Debian Release: wheezy/sid APT prefers raring-updates APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 'raring'), (100, 'raring-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.0-13-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRSm0SAAoJEIh7YGGLPBauB6MP/iTl4ulKrqAnn9Xr2TPtudd/ Rt12pCLUcJ3KReyE/DHjIKAeiq41IYcr2nZ7087eRuT+EFZGtTWYxHv4U3CX89bT zNWdX2UqUMKQR6xwc/3+BXKbTJOswcjQxnF0qb/8TJbQkhREub5ts7G2dx2SDqWZ x2ke/DOO6lbslO6G/N1+RUYY7fHgpwpQCm0RZF8t17b1xTVVUhhs/awwt1wzoaKi oDAdtU4TidO3FdlYQxBAqAqqT+Jcoj2jzxTmEV4tDeRptowd42PIKmKAyXk3ippA 2o3FgVQNVZ81sMQEN1MDpxhi302YSfyym0x8rS/DTqayIuT1PoQfJ5MzvVI0nukJ x3UGbJhIQokJVMoeFH7sEzftqTJIrAPlVNv7t9OGycYYNlCp1Gn6FO7tmYknWDye 1z91djudgLYcnUHpSU9hh1T8zBTQgavq9E4/oPs4LQlTr64+wamgQLpCVd27LSm3 B4KqylEEHzKB+3KuPcbz9SxfCAGyKnHN0KQKN+R9AgMThdDrv6E7drz8Yy0qMwdB JBpHhXhzAXYwr05LZs6mgmmwjSysIJyFhG2MMs3mCqEo8zsCbwp50uviAKnx4e8F +MOPOZi4AwMN0VGTcYZ4X6svuZt60ugcxozDY7gJ1zOGdpxd3mq5OtVpx6MLE/xy IDNQ6WycVIMro+mgBMTe =DClc -END PGP SIGNATURE- diff -Nru e2fsprogs-1.42.5/debian/changelog e2fsprogs-1.42.5/debian/changelog --- e2fsprogs-1.42.5/debian/changelog 2012-07-30 01:01:45.0 +0100 +++ e2fsprogs-1.42.5/debian/changelog 2013-03-21 00:07:18.0 + @@ -1,3 +1,12 @@ +e2fsprogs (1.42.5-1.1) unstable; urgency=low + + * Non-maintainer upload. + * e2fsck-static, e2fsprogs: let preinst remove a symbolic link in +/usr/share/doc, that should have been replaced with a directory since +1.39+1.40-WIP-2006.10.02+dfsg-1. (Closes: #698879). + + -- Nicolas Boulenguez Fri, 22 Feb 2013 23:14:59 +0100 + e2fsprogs (1.42.5-1) unstable; urgency=low * New upstream version diff -Nru e2fsprogs-1.42.5/debian/e2fsck-static.preinst e2fsprogs-1.42.5/debian/e2fsck-static.preinst --- e2fsprogs-1.42.5/debian/e2fsck-static.preinst 1970-01-01 01:00:00.0 +0100 +++ e2fsprogs-1.42.5/debian/e2fsck-static.preinst 2013-03-21 00:07:18.0 + @@ -0,0 +1,19 @@ +#!/bin/sh + +# Abort on error. +set -e + +PKG=e2fsck-static +DOCLNK=/usr/share/doc/$PKG +if test "$1" = upgrade \ +-a -L $DOCLNK +then +rm $DOCLNK +fi + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0 diff -Nru e2fsprogs-1.42.5/debian/e2fsprogs.preinst e2fsprogs-1.42.5/debian/e2fsprogs.preinst --- e2fsprogs-1.42.5/debian/e2fsprogs.preinst 1970-01-01 01:00:00.0 +0100 +++ e2fsprogs-1.42.5/debian/e2fsprogs.preinst 2013-03-21 00:07:18.0 + @@ -0,0 +1,19 @@ +#!/bin/sh + +# Abort on error. +set -e + +PKG=e2fsprogs +DOCLNK=/usr/share/doc/$PKG +if test "$1" = upgrade \ +-a -L $DOCLNK +then +rm $DOCLNK +fi + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0
Bug#703146: #703146 release critical?
Quoting Holger Levsen (hol...@layer-acht.org): > Hi Christian, > > On Mittwoch, 20. März 2013, Christian PERRIER wrote: > > I have an upload ready that includes MIchael Vogt's patch and moves > > gpg from Recommends to Depends. > > does it include the -f option as needed for live-$something? (see this bugs > log) if [ "$release_file_variant" = "IN" ]; then rm -f $reldest gpg --output "$reldest" --decrypt --keyring "$KEYRING" --ignore-time-conflict "$relsigdest" fi > > Please object if I shouldn't upload. > > > > This upload allows pbuilder to build a build chroot, so it seems fine, > > but, not being a wizard with debootstrap and archive stuff, I'd > > appreciate someone to confirm that fixing this is OK and fixing it the > > way it has been proposed in #703146 is OK too. > > a debdiff to the version in wheezy would have been nice :) Will do that. signature.asc Description: Digital signature
