Re: RFC: removing Mirrors.masterlist from .gitignore in choose-mirror
Quoting Cyril Brulebois (k...@debian.org): > Hi, > > some background: choose-mirror is a bit special in that it fetches > during the source build (when online) an updated version of the mirror > list[1] and embeds it into the source package. The Said file is > .gitignore'd, meaning it doesn't show up in choose-mirror's git repo / > history. This also means it's difficult to track the differences between > releases, notice possible issues in the list, etc. > > 1. > http://anonscm.debian.org/viewvc/webwml/webwml/english/mirror/Mirrors.masterlist?revision=HEAD > > I'm thinking about removing it from .gitignore, and about tracking it in > git, committing an update right before a choose-mirror release/upload. > > Any objection or comment? That seems fairexcept that, being a frequent uploader of choose-mirror, I'm very likely to forget about that when building it then committing back after the build (as I'm building in pbuilder, the Mirrors.masterlist file in my local git checkout is not updated...only the one in the chroot is). So, please forgive me in advance..:-) signature.asc Description: Digital signature
Re: RFC: removing Mirrors.masterlist from .gitignore in choose-mirror
Christian PERRIER (2013-10-12): > That seems fairexcept that, being a frequent uploader of > choose-mirror, I'm very likely to forget about that when building it > then committing back after the build (as I'm building in pbuilder, the > Mirrors.masterlist file in my local git checkout is not updated...only > the one in the chroot is). After sending the mail I was still wondering how to trigger the sync and how to make sure the file is committed. Maybe we could just use something similar to d-i's l10n status file: - stop the sync during clean (easily overridable by downstreams if they want to keep it); - warn if the file is say older than 2 weeks; - give appropriate instructions to run the sync (*and commit* ;)) when an outdated file is detected. That should ensure we see the need for an update while we're preparing the source package, and that we take appropriate measures when that happens. What do you think? Mraw, KiBi. signature.asc Description: Digital signature
Re: RFC: removing Mirrors.masterlist from .gitignore in choose-mirror
Quoting Cyril Brulebois (k...@debian.org): > That should ensure we see the need for an update while we're preparing > the source package, and that we take appropriate measures when that > happens. What do you think? Ack. I'm sure I can still find a way to still fail from time to time but, eh...you know that, right? :-) signature.asc Description: Digital signature
Bug#726137: debian-installer: CD eject button not working
Package: debian-installer Severity: important Dear Maintainer, I installed Debian using debian-7.1.0-amd64-CD-1.iso and debian-7.2.0-amd64-CD-2.iso burned to CD. However, the eject button of the drive does not work during installation (afterwards, it works fine), so I have to switch to another TTY and type 'eject' to open the drive and change the CDs, when apt-setup is asking for other CDs. Since this does work neither on my laptop nor on my desktop PC, it is probably not related to specific hardware, but instead some software bug. This bug is (at least) important, because it makes it impossible for inexperienced users (ignorant of TTYs) to use multiple CDs during installation. Best regards, Andreas -- 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/52598d16.7040...@gmail.com
Processed: Bug#724931: Please include the patch in git
Processing control commands: > affects -1 + hw-detect mountmedia Bug #724931 [debian-installer] ISO loopback support for Debian installer Added indication that 724931 affects hw-detect and mountmedia -- 724931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b724931.13816010429174.transcr...@bugs.debian.org
Bug#724931: Please include the patch in git
Control: affects -1 + hw-detect mountmedia
Hi,
the patch for this bug affects the following packages:
* apt-setup
* cdrom-detect
* hw-detect (check-missing-firmware)
* mountmedia
Since among the maintainers of all these packages is Christian Perrier,
I'm sending this to you.
A short summary:
The patch created by Ian Bruce and myself adds ISO loopback support for
the Debian installer using a new boot parameter, to be used as follows:
loopmount=[DEVICE:]ISO
Here ISO specifies the path to the ISO, i.e.
/ISO/debian-7.1.0-amd64-CD-1.iso.
DEVICE is for the name or UUID of the device, on which the ISO is
located. Giving this is optional and if it is not given, all devices are
searched for the ISO.
If the boot parameter is not given (or no ISO could be found),
everything works essentially as before.
For the patch to work, the loop-module is needed in the initrd, so I
suggest to make it a dependency of cdrom-detect.
I furthermore highly recommend to make the ext2/ext3/ext4, ntfs and udf
modules dependencies of cdrom-detect, since these are the most common
filesystems and thus being able to loopmount from them would be good.
(Fat is somewhat outdated.)
The patch makes it possible to boot using USB-HDD from any filesystems
with drivers in the initrd.
The patch also cleans up the somewhat messy workaround for bug #608201.
For ease of use, I propose to add a loopback.cfg similar to the the
attached one to the ISO in the folder /boot/grub/. This would allow to
easily mount the ISO using grub2.
I tested loopmounting with the following ISOs. (They were modified with
the attached Apply_Patches.sh.)
* debian-7.1.0-amd64-netinst.iso
* debian-7.1.0-i386-netinst.iso
* debian-7.1.0-amd64-CD-1.iso
* debian-7.1.0-amd64-CD-2.iso (+)
* debian-7.1.0-amd64-CD-3.iso (+)
* debian-7.1.0-amd64-DVD-1.iso
* debian-7.1.0-amd64-DVD-2.iso (+)
(+): Not modified, just copied to the folder of the first ISO in the set.
This worked without problems. To make sure all other boot mechanisms
still work, I tested them for the patched debian-7.1.0-amd64-CD-1.iso:
* Isohybrid: OK
* USB-HDD: OK
* CD: I can't open the CD drive with the button the on the drive. I
have to change to another TTY and use 'eject'. (This problem exists also
with the original ISO image, see #726137.)
Since the patch works well and does no harm, I ask you to include it in git.
Changes since the last patch:
* finish.d/10apt-cdrom-setup: Remove the whole 'deb file:' line. With
the last patch, an empty line remained.
* The script mountmedia uses 'mount -tauto', but this only tries to
mount as fat and nothing else, so I changed this to detect the
filesystem with blkid. Now firmware can be loaded from a harddrive/USB
with any of the filesystems, for which drivers are in the initrd.
* Removed $FATFS from cdrom-detect and instead let the filesystem be
automatically detected using blkid. With this it is possible to use
USB-HDD for all filesystems, for which drivers are in the initrd.
* Removed iso-hybrid and usb-hdd templates, since it works well without.
Best regards,
Andreas
Apply-Patches.sh
Description: application/shellscript
diff -rupN apt-cdrom-setup.orig/usr/bin/load-install-cd apt-cdrom-setup/usr/bin/load-install-cd
--- apt-cdrom-setup.orig/usr/bin/load-install-cd 2011-03-23 03:00:10.0 +0100
+++ apt-cdrom-setup/usr/bin/load-install-cd 2013-10-11 21:36:49.735038936 +0200
@@ -10,6 +10,13 @@ ROOT="$1"
logoutput="log-output -t load-install-cd"
+# Why isn't this function, or something like it,
+# in /usr/share/debconf/confmodule ?
+db_getval()
+{
+ db_get "$1" && echo "$RET" || true
+}
+
check_id() {
cd_ids=$(LC_ALL=C $logoutput --pass-stdout chroot $ROOT \
apt-cdrom ident | grep "^Identifying" | cut -d" " -f2)
@@ -29,18 +36,9 @@ while ! check_id; do
db_go || exit 10
done
-fs=iso9660
-if db_get cdrom-detect/cdrom_fs && [ "$RET" ]; then
- fs="$RET"
-fi
-OS=$(udpkg --print-os)
-case "$OS" in
- hurd)
- OPTIONS=ro
- ;;
- *)
- OPTIONS=ro,exec
- ;;
-esac
+fs=$(db_getval cdrom-detect/cdrom_fs)
+[ "$fs" ] || fs=iso9660
+OPTIONS=$(db_getval cdrom-detect/cdrom_options)
+[ "$OPTIONS" ] || OPTIONS=ro,exec
db_get cdrom-detect/cdrom_device
$logoutput mount -t "$fs" -o $OPTIONS $RET /cdrom
diff -rupN apt-cdrom-setup.orig/usr/lib/apt-setup/generators/40cdrom apt-cdrom-setup/usr/lib/apt-setup/generators/40cdrom
--- apt-cdrom-setup.orig/usr/lib/apt-setup/generators/40cdrom 2013-05-12 12:49:10.0 +0200
+++ apt-cdrom-setup/usr/lib/apt-setup/generators/40cdrom 2013-10-11 00:19:52.494473022 +0200
@@ -10,7 +10,9 @@ if ! type chroot_cleanup_localmounts >/d
# Variant of chroot_cleanup that only cleans up chroot_setup's mounts.
chroot_cleanup_localmounts () {
rm -f /target/usr/sbin/policy-rc.d
- mv /target/sbin/start-stop-daemon.REAL /target/sbin/start-stop-daemon
+ if [ -f /target/sbin/start-stop-daemon.REAL ]; then
+ mv /target/sbin/start-stop-daemon.REAL /target/sbin/start-stop-daemon
+ fi
if
Re: RFC: removing Mirrors.masterlist from .gitignore in choose-mirror
Christian PERRIER (2013-10-12): > Quoting Cyril Brulebois (k...@debian.org): > > > That should ensure we see the need for an update while we're preparing > > the source package, and that we take appropriate measures when that > > happens. What do you think? > > Ack. I'm sure I can still find a way to still fail from time to time > but, eh...you know that, right? :-) Here's what happens during clean now: | if [ -d .git ] && which git >/dev/null 2>&1; then \ | last=`git log --format=format:%at -- Mirrors.masterlist|head -1`; \ | now=`date +%s`; \ | if [ $((now-date)) -gt $((60*60*24*14)) ]; then \ | printf "\n\n*** WARNING: Mirrors.masterlist was last committed more\n"; \ | printf "*** than 2 weeks ago, maybe it needs an update?"; \ | echo; echo; echo "You can try the following command to run a sync, and use git diff/git commit:"; \ | echo " make Mirrors.masterlist";\ | sleep 5; \ | fi; \ | fi | | | *** WARNING: Mirrors.masterlist was last committed more | *** than 2 weeks ago, maybe it needs an update? | | You can try the following command to run a sync, and use git diff/git commit: |make Mirrors.masterlist [ + sleep for a few seconds ] Of course that only happens during clean from a git repository, when git is installed, so won't happen on buildds. Speaking of which, refreshing the masterlist was attempted at build time too, so I've patched rules to also export ONLINE=n during build, to avoid that entirely. [ Side notes: 1. It's a serious bug to depend on the network; 2. It's also not deterministic to allow failure in doing so. ] Mraw, KiBi. PS: About failures… everyone can fail. Especially those who do a lot. Not going to blame you. :-) signature.asc Description: Digital signature
Bug#715408: Error in Testing installier
Control: tags -1 + moreinfo unreproducible Hi, I do not have this problem with the recent Debian installer. Have you tried it with the debian-testing-amd64-netinst.iso from the following site? http://cdimage.debian.org/cdimage/daily-builds/daily/20131012-1/amd64/iso-cd/ Please send a mail, whether or not it works now. Best regards, Andreas -- 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/5259a3d6.9020...@gmail.com
Processed: Bug#715408: Error in Testing installier
Processing control commands: > tags -1 + moreinfo unreproducible Bug #715408 [debian-installer] Error in Testing installier Added tag(s) unreproducible and moreinfo. -- 715408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b715408.13816063666050.transcr...@bugs.debian.org
Processing of choose-mirror_2.50_amd64.changes
choose-mirror_2.50_amd64.changes uploaded successfully to localhost along with the files: choose-mirror_2.50.dsc choose-mirror_2.50.tar.gz choose-mirror_2.50_all.udeb choose-mirror-bin_2.50_amd64.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1vv4rx-0003hw...@franck.debian.org
choose-mirror_2.50_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 12 Oct 2013 21:06:29 +0200 Source: choose-mirror Binary: choose-mirror choose-mirror-bin Architecture: source all amd64 Version: 2.50 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Cyril Brulebois Description: choose-mirror - Choose mirror to install from (menu item) (udeb) choose-mirror-bin - Choose mirror to install from (program) (udeb) Changes: choose-mirror (2.50) unstable; urgency=low . * Start tracking Mirrors.masterlist instead of only including it when building the source package: - Sync it as of 2013-10-12. - Remove it from .gitignore accordingly. * Update debian/rules to run clean then check-masterlist instead of clean then Mirrors.masterlist; this new target checks (when the .git directory is present and git available) the date of the last update to the said file, and warns if it's older than 2 weeks, providing instructions to sync the said file, and waiting a few seconds to draw attention. * Export ONLINE=n when building. Fetching stuff from internet during build isn't too nice, especially when failure is allowed. Checksums-Sha1: c9e4c3161f5154f28674c9622df54377657e0942 1806 choose-mirror_2.50.dsc a8f7f97b04ca962603e6b0cc381fd6640f58725c 234453 choose-mirror_2.50.tar.gz 40498ce37e1a0e5854b3f8880718b3f682453b2b 1006 choose-mirror_2.50_all.udeb e6fd2552781b675f5cdd421fdfbaf343909d70f3 198356 choose-mirror-bin_2.50_amd64.udeb Checksums-Sha256: 9caf30fcd1bdcd5a45faf6599266aec54a83c45656c8da7e266781fd6700f30e 1806 choose-mirror_2.50.dsc 2a32c6e11a0204b60bb86df9c5745fe35a5783ff2fca9cf5612a9d84f0ff15da 234453 choose-mirror_2.50.tar.gz b936f501ade08e482001a2391f5ce3ce4f55aa8236ae75cfedb4f454e79a37d0 1006 choose-mirror_2.50_all.udeb 3dad3680dcf03c67f0642130c3cbadf4df2e53090d1ef12277e46818cf1908ec 198356 choose-mirror-bin_2.50_amd64.udeb Files: 449f8dcb13bf6fa9791753b961cccbc1 1806 debian-installer extra choose-mirror_2.50.dsc e3b2ad2a68c96ebc44b799a37dfa02ed 234453 debian-installer extra choose-mirror_2.50.tar.gz d176cec13a3080fdf278dafcfc6b8904 1006 debian-installer extra choose-mirror_2.50_all.udeb 4a22c168ba0fafdf3e30e9618276a041 198356 debian-installer extra choose-mirror-bin_2.50_amd64.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBAgAGBQJSWaGyAAoJEP+RSvDCs1Ugx6wP/3dXtXHswvrGqO/VGIiOMDqY 7eN7KbY/fKyRGA22FFcgLnMsdTIQWUVacarH0pNhoRP/i1sWsb9enbi9HOZz1dSs kqCX3xtrViYHtuNc7jZ+HgCTqeA4/yxH6qLfSANoOp9vf+FdEzoUlUSuiwRoivI3 aX2W8Shvt86P3+hC8LX+j4W27Z8ae03ytmgh2/bpa9CJ2d/C7F/kzrBm3ZMZ2Wp/ EOGIIEfRC8PrBP4IH8R5sM+Kx0ulO0nSgqrs0GSSRzTTXeRyl8cLRhYwfltrjque r/fmt4cz2nPhMFMZgJQZfe+ACNHySXsc49ZoxpsH4VvEhEYM+J40UqLcEdfXm8HH 82NOYVFQ3tzRVnq99F0pCRF12cm8bJ9EmqolQydvo0FIYXc+WLT3tjN8qDoFgZxF LRm2jvcLUkMJQAcVbX2+KAoOKNeiATyiYehZTWrZkPg9x7BNaqgJFQYm0vXxtqyH 8ezDZkYq+g7cFLv7wXWlInQYKI7lHEarZqts4ddHE64vjJV71mWVjGIQ/RhT1dW4 sSPSiNe1P2BfJZUGsv5wcKlJDyQKS03L0aRiYbcbV4hWUhpA9o4TkWgn8UQVl8Sa /9WMlyKGNqNs22+IzjxfhK0IHXL/wj+DqtKtsegKjC3QH1BVW3HSMctSP+KKk8fG dTMaqEMFQ4hiamu4EMzX =i3Ol -END PGP SIGNATURE- Thank you for your contribution to Debian. -- 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/e1vv4wa-0004mq...@franck.debian.org
Re: Installer bugs 708126 and 709319
Bernard McNeill (2013-10-12): > Have these two bugs been addressed in 7.2? (-boot@ would have been a better place to ask.) AFAICT those bugs weren't reassigned to the relevant packages, and not fixed in unstable. That's usually the prerequisite to having bugs fixed in stable. Mraw, KiBi. signature.asc Description: Digital signature
Re: RFC: removing Mirrors.masterlist from .gitignore in choose-mirror
Cyril Brulebois wrote: > [ Side notes: >1. It's a serious bug to depend on the network; >2. It's also not deterministic to allow failure in doing so. ] Have you ever looked at the debian-installer source package's network use? I'm just saying. If I were throwing arbitrary rules out there, I'd add: 3. Committing redundant data to version control is wrong. But I have another rule that superscedes all 3: 0. Ignore arbitrary rules when you have the time to think for yourself. Personally, I think that the way choose-mirror handled Mirrors.masterlist was fine. Note that it didn't fail if there was a network problem. -- see shy jo signature.asc Description: Digital signature
Re: RFC: removing Mirrors.masterlist from .gitignore in choose-mirror
Joey Hess (2013-10-12): > Have you ever looked at the debian-installer source package's network > use? I'm just saying. Fetching packages from the same mirror isn't exactly the same as wgetting a file from an http location without any kind of verification. I'm just saying. src:debian-installer's being "strange" doesn't look like a reason for others to do strange things on their own, at least to me. > If I were throwing arbitrary rules out there, I'd add: > > 3. Committing redundant data to version control is wrong. Having to debdiff source packages to see what the changes were makes me think that it's actually useful. At least to me. I'm sorry if that looks wrong, but I can take the blame for doing things that let me work. > Personally, I think that the way choose-mirror handled > Mirrors.masterlist was fine. Noted. > Note that it didn't fail if there was a network problem. This was already noted in an earlier mail. KiBi. signature.asc Description: Digital signature
Correctness of current translation-status?
Hi Christian, please find attached the output of calc-release-status as of today. I've committed a few fixes to the said script earlier so that it reaches the end (mostly making sure the git checkout worked for all packages), but I'm not sure the results are OK. Can you please have a quick look and tell me whether they seem realistic? Thanks already! Mraw, KiBi. # Installer translation status generated by the script: # scripts/l10n/calc-release-status # This file should be updated before every official release. # Generated on: Sat, 12 Oct 2013 23:21:44 + # am: 2 M ar: 2 M ast: 2 M be: 2 M bg: 2 M bn: 2 M bo: 2 P bs: 2 M ca: 2 M cs: 2 M cy: 2 M da: 2 M de: 2 M dz: 2 P el: 2 M eo: 2 M es: 2 M et: 2 M eu: 2 M fa: 2 M fi: 2 M fr: 2 M ga: 2 M gl: 2 M gu: 2 M he: 2 M hi: 2 M hr: 2 M hu: 2 M hy: 2 L id: 2 M is: 2 M it: 2 M ja: 2 M ka: 2 P kk: 2 M km: 2 M kn: 2 M ko: 2 M ku: 2 P lo: 2 M lt: 2 M lv: 2 M mk: 2 M ml: 2 M mr: 2 M nb: 2 M ne: 2 P nl: 2 M nn: 2 P pa: 2 M pl: 2 M pt: 2 M pt_BR: 2 M ro: 2 M ru: 2 M se: 2 L si: 2 M sk: 2 M sl: 2 M sq: 2 P sr: 2 M sr@latin: 2 L sv: 2 M ta: 2 M te: 2 M tg: 2 M th: 2 M tl: 2 P tr: 2 M ug: 2 M uk: 2 M vi: 2 M zh_CN: 2 M zh_TW: 2 M signature.asc Description: Digital signature
Removing linux-modules-di-*-2.6 checkouts on ravel?
Hi, I initially didn't pay much attention to the actual packages listed on: http://d-i.debian.org/git-summary.html linux-modules-di-*-2.6 have been gone for a while, see .mrconfig commit: | r67037 | joeyh | 2011-11-21 19:21:58 +0100 (Mon, 21 Nov 2011) | 10 lines | | removed entries for linux-kernel-di-* | | These git repositories are unused now that the linux kernel package builds | udebs. They have been moved to attic/ | | Note that I could have left the entries but set deleted=true in each, | and mr 1.05 would then nag us to delete the directories. However, | older versions of mr, when operating in untrusted mode, would choke on that | line, so I have not done that. ravel still has those checkouts (d-i/trunk/packages/linux-modules-di-*-2.6) around and I'm wondering whether something or someone would still be depending on their being there. If nobody speaks up, I'll probably move them out of the way, see if some crontab explodes, and either rm after a while, or put back into place/fix things up if anything breaks. Mraw, KiBi. signature.asc Description: Digital signature
