Wie, waar, wanneer
Videobewaking: wie, waar, wanneer Vind de beste leverancier • Fiscaal aftrekbaar • Bescherming van uw goederen, lokaal maar ook medewerkers • Analoge of digitale camerabewaking • Opname van de beelden http://www.debesteleverancier.be/videobewaking/gratis-offerte.htm?lng=nltg=camerautm_campaign=camerautm_source=admrutm_medium=emailyou=debian-boot@lists.debian.org --- Online versie: http://mailing.fb.bb1.mailbb.be/c8567/e51913396/hd775f/l256636/index.html Deze e-mail werd verstuurd naar debian-boot@lists.debian.org. Profiel aanpassen: http://mailing.fb.bb1.mailbb.be/c8567/e51913396/hd775f/l256638/index.html Uitschrijven: http://mailing.fb.bb1.mailbb.be/c8567/e51913396/hd775f/l256637/index.html Privacy policy: http://mailing.fb.bb1.mailbb.be/c8567/e51913396/hd775f/l256639/index.html
Re: util-linux: dropping cfdisk-udeb, switching to ncurses
Hello all. Now that D-I Stretch Alpha 1 seems to have been released I think it's time to poke some life into this thread again... I'd like to upload the util-linux version currently sitting in experimental to unstable as soon as you find approve. As a reminder, the original reason for me contacting you is the dropping of the cfdisk-udeb (since ncursesw5 does not have an udeb and the ncurses maintainer would like to avoid adding it unless there is a real need for one). On Thu, Jun 04, 2015 at 10:25:49AM +0200, Cyril Brulebois wrote: Steve McIntyre st...@einval.com (2015-06-04): [...] I don't think we use it at all *anyway*... Having had a quick look, it seems we only depend on fdisk-udeb in some components (lilo-installer, rescue-mode). Even if it's been unused in the past I'd also like to point out that you should please also look at future possibilities. The updated version of util-linux now brings significantly improved *fdisk utilities which should each and all hopefully serve all your modern partitioning needs. (If not, please speak up about what you're missing. Preferrably directly on the upstream mailing list.) (As I understand it you're currently mainly using parted. I'm not in any position to list pros/cons of parted vs util-linux *fdisk. I'm just pointing out that past knowledge about *fdisk needs to be re-evaluated because of the introduction of libfdisk and the rewrite of *fdisk to all use libfdisk.) But I'd feel safer if that udeb drop could be happening after D-I Stretch Alpha 1 has been released. If you at any point in the future see the need for re-adding the cfdisk-udeb please don't hesitate to raise that request in the future. The removal is in no way a permanent strategical move. Just the most convenient and suitable one at the moment to avoid stalling progress. Regards, Andreas Henriksson PS. I'm currently on vacation. Any real action from my side is not very likely to actually happen until sometime closer to debconf. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150728094626.ga29...@fatal.se
Re: proofreading the installation-guide
On Tue, Jul 28, 2015 at 09:06:03PM +0100, Justin B Rye wrote: Holger Wansing wrote: Justin B Rye justin.byam@gmail.com wrote: An interesting idea, but one that seems unlikely to work, especially given the way it's used in the text. For instance, there's a page welcome/what-is-debian-linux.xml, which is full of sentences like debian; was the first Linux distribution to include a package management system. It was mostly me changing Debian into debian; that days in 2010. If I remember correctly, it was initiated by a post of Frans Pop, who proposed that change. And the rationale was in fact, to get a manual, that can easily be turned from a Debian installer manual into a Ubuntu installer manual, for example. Whoever it is that's reworking the manual for the derivative is still going to need to go through the whole text changing the content. The debian; entity seems liable to cost us more effort than it saves them (a single extra search-and-replace operation). If that was the case, it would be a single search-and-replace operation for you, too. Just catch the ones you see while proofreading, leave the rest. The Debian derivative's people will catch the ones you miss, and you can someday, *when there's time to do it*, diff your source with theirs to find the rest. Of course, this is only for derivatives that use the same installer. And I can't see any particular pattern in when it's Debian installer, when it's debian; installer, and when it's d-i;. With the above been said, it should be as follows: In sentences which apply to Debian and also to its derivates, it should use debian; , while in sentences which only apply to Debian and not to the derivates, it should be Debian. It was also my intention to make it that way indeed, but: 1. I found out that the job was bigger than I first thought when taking it over, leading to mistakes. 2. due to the lack of manpower in the d-i team, especially the loss of Frans, the d-i manual guru (amongst other roles), there was probably not enough reviewing of that changes, and things may got overlooked. Oh, well, for now I'll plan on trying to get debian; into shape as part of my proofreading sweep - it would be easy enough to switch back from sometimes saying debian; to always saying Debian if we decide to give up on it. The debian-gnu; entity is effectively just shorthand for Debian GNU/arch-kernel; - confusing but handy. Wait, does it expand to Debian or debian;? The architecture;, arch-title; and arch-kernel; entities are slightly oddly named Since I keep losing track and having to check again, I'll leave a note for myself here: architecture; = 32-bit PC, 32-bit soft-float ARM, etc. arch-title; = i386, armel, etc. arch-kernel; = Linux, KFreeBSD, etc. but make sense as parametrisations, as do release; and releasename; as long as they're used for things that stay true for every release. (Oh, and I've just noticed there's a releasename-cap;, used instead of plain releasename; for no obvious reason in hardware/supported/arm.xml and nowhere else.) But there are also special entities for enterkey;, escapekey;, tabkey;, f10key;, and even ekey;! Most of these are only used once each - the rest of the time (and always for keys like F2 or space) it just uses keycap.../keycap. That entities like releasename-cap; enterkey; escapekey; tabkey; were created, to give translators a chance to follow the rules for their language there (for example, in German we write Jessie, Stretch or Unstable uppercase, while in English that's mostly lowercase: jessie, stretch, unstable) or to have tab key translated into Tabulator-Taste for German, for example. Sorry, I don't follow. Surely German needs *all* instances of releasename; to be capitalised? How does it help to have some of them replaced in the text with releasename-cap;? And why is it any easier to provide translations for tabkey; than for keycodeTab/keycode? Why would you need ones for f10key; and ekey;, but not keycodeF2/keycode or keycodeSpace/keycode? Hmm, I can imagine cases where the *English* version might benefit from having an entity indefinitearticle; that automatically selects either a or an depending on whether the following substituted-in word starts with a vowel sound! But let's not. Globally said, there may be several occurrences of above things not being perfectly consistent, because there are many editors for the manual these days, but there is no Frans Pop anymore, watching the changings and correcting things where needed. [PS included for convenience:] So I suppose it would be reasonable to put a comment in the document source explaining this, perhaps where these macros are defined, and making further changes as we discover the need and have time, possibly prompted by bug reports from Debian derivatives or forks, or
Processing of debootstrap_1.0.72_amd64.changes
debootstrap_1.0.72_amd64.changes uploaded successfully to localhost along with the files: debootstrap_1.0.72.dsc debootstrap_1.0.72.tar.gz debootstrap-udeb_1.0.72_all.udeb debootstrap_1.0.72_all.deb 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: https://lists.debian.org/e1zk51n-0003ef...@franck.debian.org
Bug#787117: marked as done (debootstrap: missing wily)
Your message dated Tue, 28 Jul 2015 13:48:51 + with message-id e1zk5ft-0006eh...@franck.debian.org and subject line Bug#787117: fixed in debootstrap 1.0.72 has caused the Debian Bug report #787117, regarding debootstrap: missing wily to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 787117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debootstrap Version: 1.0.70 Severity: wishlist I'd attach a patch, but for a symlink it's going to be longer than just mentioning that the fix is ln -s gutsy scripts/wily. :) (I've tested via the script parameter that this actually works, too FWIW.) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 ---End Message--- ---BeginMessage--- Source: debootstrap Source-Version: 1.0.72 We believe that the bug you reported is fixed in the latest version of debootstrap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 787...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson cjwat...@debian.org (supplier of updated debootstrap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 28 Jul 2015 14:32:19 +0100 Source: debootstrap Binary: debootstrap debootstrap-udeb Architecture: source all Version: 1.0.72 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Colin Watson cjwat...@debian.org Description: debootstrap - Bootstrap a basic Debian system debootstrap-udeb - Bootstrap the Debian system (udeb) Closes: 757819 787117 Changes: debootstrap (1.0.72) unstable; urgency=medium . [ Iain Lane ] * Add (Ubuntu) wily as a symlink to gutsy (closes: #787117). . [ Colin Watson ] * Fix resolve_deps and setup_available to work in the --foreign case (closes: #757819, LP: #1450980). Checksums-Sha1: 6d260dfed5240c6f28f4f3a9069a67fc08e63bc9 1831 debootstrap_1.0.72.dsc dabf81337a51ae6dc84c1dc3bd231dd3d25b7e36 62089 debootstrap_1.0.72.tar.gz fa8b3d1b6f7c352c2a02fce0f196d66980312368 18484 debootstrap-udeb_1.0.72_all.udeb 52c6a120f24534e18dac02ee995d8066a5946fe7 65002 debootstrap_1.0.72_all.deb Checksums-Sha256: cfae25c4e1feba837ed9cdfe1db7614ef10845f6b8235266a811b212c241ad72 1831 debootstrap_1.0.72.dsc 90f4cf1390326f020b9192b6a45ba1d323fffab9c22c6f62451780e6f5482f8d 62089 debootstrap_1.0.72.tar.gz 79987576c978108e28952e495fc070800ef8c2cb9049b267bad72d9b4b72c387 18484 debootstrap-udeb_1.0.72_all.udeb 501fb1b22c5b18a831c1fd983c108a1de9330baca6c08a55edef25c2e4f99e12 65002 debootstrap_1.0.72_all.deb Files: e6a1e593a85018c14f004d1d39ed9eb0 1831 admin extra debootstrap_1.0.72.dsc 0cacf6e3bd8b566e921d2a326d6fd2bd 62089 admin extra debootstrap_1.0.72.tar.gz 49f24e3299352aa5453f725ec0d55566 18484 debian-installer extra debootstrap-udeb_1.0.72_all.udeb bb770d60961ce50a906fe570a36f907d 65002 admin extra debootstrap_1.0.72_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Colin Watson cjwat...@debian.org -- Debian developer iQIVAwUBVbeEpjk1h9l9hlALAQhQ/w//TbjlH2TTGXWO55sgtxoXFLysb3KfO91v fRN0hFlyvWC/jPXfA07sbFDME+mC/qlFEU8Kj5lsEbiYV+HftS5EyyglcotFTDOt 7JZfIIwhRCfqfyvgx6C9UY/apuPUIJXglygZ7eWztMCIHhKAYca4/KylJrkLlNsv slEZlsjRB3jBnQp5gnky6+B2GGwq+WAS1FvSjUZ6ohcjZiNgZ+w9fhd3OFQXiXJ2 HEe2uZ43H0/iFS/L6LJclMszqTPld/eDizbDk5Tvd14vBwZfucI5U6lII0zV+iOy 5ORNTh37BVhY7UnDBXujZ1/H477e4kfrRzniEfQaLsK9NDwPhQc6Vb0U2HQxh+iC R3O0kgvOvI8W4U0Ld5Z281bZXJX3zDPIZVxS16LHf2tSYJ53K74RzD+r7I2Gcc2E RtFk74ClMC7cyMhcuHojdZphC7zRSvnQHDAmN53eonCtDIttniPOhwBHbO0BrHI0 2+YjEwonMa/UGBwiM91pXwpt6G1/67jzwAcATcACt2yL/vFQqbo7DqBbO/LcPRXa 3uN3wJWj+gWXegJSx7uXwSkaf0BYrtcCrcUbb1nh1pyNi9VaYG7VCmJX02Wy+Q8v 7JjEIDOGT6O7oCMixfv8pZMTzMYIvbIJySXyzoYig7k0P8OoWWe34KYNftzb0ivj GqSZwaPSXVY= =9qz9 -END PGP SIGNATUREEnd Message---
debootstrap_1.0.72_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 28 Jul 2015 14:32:19 +0100 Source: debootstrap Binary: debootstrap debootstrap-udeb Architecture: source all Version: 1.0.72 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Colin Watson cjwat...@debian.org Description: debootstrap - Bootstrap a basic Debian system debootstrap-udeb - Bootstrap the Debian system (udeb) Closes: 757819 787117 Changes: debootstrap (1.0.72) unstable; urgency=medium . [ Iain Lane ] * Add (Ubuntu) wily as a symlink to gutsy (closes: #787117). . [ Colin Watson ] * Fix resolve_deps and setup_available to work in the --foreign case (closes: #757819, LP: #1450980). Checksums-Sha1: 6d260dfed5240c6f28f4f3a9069a67fc08e63bc9 1831 debootstrap_1.0.72.dsc dabf81337a51ae6dc84c1dc3bd231dd3d25b7e36 62089 debootstrap_1.0.72.tar.gz fa8b3d1b6f7c352c2a02fce0f196d66980312368 18484 debootstrap-udeb_1.0.72_all.udeb 52c6a120f24534e18dac02ee995d8066a5946fe7 65002 debootstrap_1.0.72_all.deb Checksums-Sha256: cfae25c4e1feba837ed9cdfe1db7614ef10845f6b8235266a811b212c241ad72 1831 debootstrap_1.0.72.dsc 90f4cf1390326f020b9192b6a45ba1d323fffab9c22c6f62451780e6f5482f8d 62089 debootstrap_1.0.72.tar.gz 79987576c978108e28952e495fc070800ef8c2cb9049b267bad72d9b4b72c387 18484 debootstrap-udeb_1.0.72_all.udeb 501fb1b22c5b18a831c1fd983c108a1de9330baca6c08a55edef25c2e4f99e12 65002 debootstrap_1.0.72_all.deb Files: e6a1e593a85018c14f004d1d39ed9eb0 1831 admin extra debootstrap_1.0.72.dsc 0cacf6e3bd8b566e921d2a326d6fd2bd 62089 admin extra debootstrap_1.0.72.tar.gz 49f24e3299352aa5453f725ec0d55566 18484 debian-installer extra debootstrap-udeb_1.0.72_all.udeb bb770d60961ce50a906fe570a36f907d 65002 admin extra debootstrap_1.0.72_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Colin Watson cjwat...@debian.org -- Debian developer iQIVAwUBVbeEpjk1h9l9hlALAQhQ/w//TbjlH2TTGXWO55sgtxoXFLysb3KfO91v fRN0hFlyvWC/jPXfA07sbFDME+mC/qlFEU8Kj5lsEbiYV+HftS5EyyglcotFTDOt 7JZfIIwhRCfqfyvgx6C9UY/apuPUIJXglygZ7eWztMCIHhKAYca4/KylJrkLlNsv slEZlsjRB3jBnQp5gnky6+B2GGwq+WAS1FvSjUZ6ohcjZiNgZ+w9fhd3OFQXiXJ2 HEe2uZ43H0/iFS/L6LJclMszqTPld/eDizbDk5Tvd14vBwZfucI5U6lII0zV+iOy 5ORNTh37BVhY7UnDBXujZ1/H477e4kfrRzniEfQaLsK9NDwPhQc6Vb0U2HQxh+iC R3O0kgvOvI8W4U0Ld5Z281bZXJX3zDPIZVxS16LHf2tSYJ53K74RzD+r7I2Gcc2E RtFk74ClMC7cyMhcuHojdZphC7zRSvnQHDAmN53eonCtDIttniPOhwBHbO0BrHI0 2+YjEwonMa/UGBwiM91pXwpt6G1/67jzwAcATcACt2yL/vFQqbo7DqBbO/LcPRXa 3uN3wJWj+gWXegJSx7uXwSkaf0BYrtcCrcUbb1nh1pyNi9VaYG7VCmJX02Wy+Q8v 7JjEIDOGT6O7oCMixfv8pZMTzMYIvbIJySXyzoYig7k0P8OoWWe34KYNftzb0ivj GqSZwaPSXVY= =9qz9 -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: https://lists.debian.org/e1zk5ft-0006eo...@franck.debian.org
Bug#757819: marked as done (qemu-debootstrap can't handle Pre-Depends)
Your message dated Tue, 28 Jul 2015 13:48:51 + with message-id e1zk5ft-0006ey...@franck.debian.org and subject line Bug#757819: fixed in debootstrap 1.0.72 has caused the Debian Bug report #757819, regarding qemu-debootstrap can't handle Pre-Depends to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 757819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debootstrap Version: 1.0.60 Severity: normal After a foreign deboostrap, the second stage failed: dpkg: regarding .../systemd-sysv_208-7_armhf.deb containing systemd-sysv, pre-dependency problem: systemd-sysv pre-depends on systemd systemd is unpacked, but has never been configured. dpkg: error processing archive /var/cache/apt/archives/systemd-sysv_208-7_armhf.deb (--unpack): pre-dependency problem - not installing systemd-sysv dpkg --configure --pending succeeds, so I think debootstrap may just need to be adjusted now that systemd is default. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debootstrap depends on: ii wget 1.15-1+b1 Versions of packages debootstrap recommends: ii debian-archive-keyring 2012.4 ii gnupg 1.4.18-2 debootstrap suggests no packages. -- no debconf information -- see shy jo signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: debootstrap Source-Version: 1.0.72 We believe that the bug you reported is fixed in the latest version of debootstrap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 757...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Watson cjwat...@debian.org (supplier of updated debootstrap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 28 Jul 2015 14:32:19 +0100 Source: debootstrap Binary: debootstrap debootstrap-udeb Architecture: source all Version: 1.0.72 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Colin Watson cjwat...@debian.org Description: debootstrap - Bootstrap a basic Debian system debootstrap-udeb - Bootstrap the Debian system (udeb) Closes: 757819 787117 Changes: debootstrap (1.0.72) unstable; urgency=medium . [ Iain Lane ] * Add (Ubuntu) wily as a symlink to gutsy (closes: #787117). . [ Colin Watson ] * Fix resolve_deps and setup_available to work in the --foreign case (closes: #757819, LP: #1450980). Checksums-Sha1: 6d260dfed5240c6f28f4f3a9069a67fc08e63bc9 1831 debootstrap_1.0.72.dsc dabf81337a51ae6dc84c1dc3bd231dd3d25b7e36 62089 debootstrap_1.0.72.tar.gz fa8b3d1b6f7c352c2a02fce0f196d66980312368 18484 debootstrap-udeb_1.0.72_all.udeb 52c6a120f24534e18dac02ee995d8066a5946fe7 65002 debootstrap_1.0.72_all.deb Checksums-Sha256: cfae25c4e1feba837ed9cdfe1db7614ef10845f6b8235266a811b212c241ad72 1831 debootstrap_1.0.72.dsc 90f4cf1390326f020b9192b6a45ba1d323fffab9c22c6f62451780e6f5482f8d 62089 debootstrap_1.0.72.tar.gz 79987576c978108e28952e495fc070800ef8c2cb9049b267bad72d9b4b72c387 18484 debootstrap-udeb_1.0.72_all.udeb 501fb1b22c5b18a831c1fd983c108a1de9330baca6c08a55edef25c2e4f99e12 65002 debootstrap_1.0.72_all.deb Files: e6a1e593a85018c14f004d1d39ed9eb0 1831 admin extra debootstrap_1.0.72.dsc 0cacf6e3bd8b566e921d2a326d6fd2bd 62089 admin extra debootstrap_1.0.72.tar.gz 49f24e3299352aa5453f725ec0d55566 18484 debian-installer extra debootstrap-udeb_1.0.72_all.udeb bb770d60961ce50a906fe570a36f907d 65002 admin extra debootstrap_1.0.72_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Colin Watson cjwat...@debian.org -- Debian developer iQIVAwUBVbeEpjk1h9l9hlALAQhQ/w//TbjlH2TTGXWO55sgtxoXFLysb3KfO91v fRN0hFlyvWC/jPXfA07sbFDME+mC/qlFEU8Kj5lsEbiYV+HftS5EyyglcotFTDOt 7JZfIIwhRCfqfyvgx6C9UY/apuPUIJXglygZ7eWztMCIHhKAYca4/KylJrkLlNsv
Re: proofreading the installation-guide
Hi, Justin B Rye justin.byam@gmail.com wrote: Hendrik Boom wrote: Justin B Rye wrote: * entity questions - when am I meant to say Debian and when is it debian;? This like many of these entities seems to have no obvious function other than to make the source harder to interpret... * The d-i; entity expands to debian-installer in bold verbatim lowercase. If that is in effect the brandname of the software project then presumably we shouldn't be talking about the d-i; - that ought to be the Debian installer. Presumably both of these parametrisations are for the convenience of Debian derivatives and forks. By making these macros, it's easier for the, and it'll be easier for us to merge downstream patches. An interesting idea, but one that seems unlikely to work, especially given the way it's used in the text. For instance, there's a page welcome/what-is-debian-linux.xml, which is full of sentences like debian; was the first Linux distribution to include a package management system. It was mostly me changing Debian into debian; that days in 2010. If I remember correctly, it was initiated by a post of Frans Pop, who proposed that change. And the rationale was in fact, to get a manual, that can easily be turned from a Debian installer manual into a Ubuntu installer manual, for example. And I can't see any particular pattern in when it's Debian installer, when it's debian; installer, and when it's d-i;. With the above been said, it should be as follows: In sentences which apply to Debian and also to its derivates, it should use debian; , while in sentences which only apply to Debian and not to the derivates, it should be Debian. It was also my intention to make it that way indeed, but: 1. I found out that the job was bigger than I first thought when taking it over, leading to mistakes. 2. due to the lack of manpower in the d-i team, especially the loss of Frans, the d-i manual guru (amongst other roles), there was probably not enough reviewing of that changes, and things may got overlooked. The debian-gnu; entity is effectively just shorthand for Debian GNU/arch-kernel; - confusing but handy. The architecture;, arch-title; and arch-kernel; entities are slightly oddly named but make sense as parametrisations, as do release; and releasename; as long as they're used for things that stay true for every release. (Oh, and I've just noticed there's a releasename-cap;, used instead of plain releasename; for no obvious reason in hardware/supported/arm.xml and nowhere else.) But there are also special entities for enterkey;, escapekey;, tabkey;, f10key;, and even ekey;! Most of these are only used once each - the rest of the time (and always for keys like F2 or space) it just uses keycap.../keycap. That entities like releasename-cap; enterkey; escapekey; tabkey; were created, to give translators a chance to follow the rules for their language there (for example, in German we write Jessie, Stretch or Unstable uppercase, while in English that's mostly lowercase: jessie, stretch, unstable) or to have tab key translated into Tabulator-Taste for German, for example. Globally said, there may be several occurrences of above things not being perfectly consistent, because there are many editors for the manual these days, but there is no Frans Pop anymore, watching the changings and correcting things where needed. Regards Holger -- Created with Sylpheed 3.5.0 under D E B I A N L I N U X 8 . 0J E S S I E . Registered Linux User #311290 - https://linuxcounter.net/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150728190027.b25aa6026e9dfb93eaeed...@wansing-online.de
Re: util-linux: dropping cfdisk-udeb, switching to ncurses
Hi, Andreas Henriksson andr...@fatal.se (2015-07-28): Now that D-I Stretch Alpha 1 seems to have been released I think it's time to poke some life into this thread again... I'd like to upload the util-linux version currently sitting in experimental to unstable as soon as you find approve. As a reminder, the original reason for me contacting you is the dropping of the cfdisk-udeb (since ncursesw5 does not have an udeb and the ncurses maintainer would like to avoid adding it unless there is a real need for one). ACK. On Thu, Jun 04, 2015 at 10:25:49AM +0200, Cyril Brulebois wrote: Steve McIntyre st...@einval.com (2015-06-04): [...] I don't think we use it at all *anyway*... Having had a quick look, it seems we only depend on fdisk-udeb in some components (lilo-installer, rescue-mode). Looking again, I don't see any hits on cfdisk-udeb, only fdisk-udeb. Let's go over our source packages. lilo-installer: === Calls sfdisk in postinst, hence the dependency. partitioner: Generates its dependency fields this way: | ifeq ($(ARCH),mips) | dh_gencontrol -- -Vfdisk:Depends=fdisk-udeb | else ifeq ($(ARCH),m68k) | dh_gencontrol -- -Vfdisk:Depends=atari-fdisk-udeb, mac-fdisk-udeb | endif It seems to heavily call *disk command, see: main.c scripts/common.sh scripts/mips.sh rescue: === Assuming almost nobody is going to cry over lilo-installer, let's look at rescue-mode. The dependency was introduced by: http://anonscm.debian.org/cgit/d-i/rescue.git/commit/?id=d7405ee44aae324a24d562898780b834ae8e94fd (even if it seems the changelog entry has a typo and refers to fdisk-utils instead of fdisk-udeb in the control file.) The idea is to have most tools around just in case, no direct usage AFAICT. Even if it's been unused in the past I'd also like to point out that you should please also look at future possibilities. The updated version of util-linux now brings significantly improved *fdisk utilities which should each and all hopefully serve all your modern partitioning needs. (If not, please speak up about what you're missing. Preferrably directly on the upstream mailing list.) (As I understand it you're currently mainly using parted. I'm not in any position to list pros/cons of parted vs util-linux *fdisk. I'm just pointing out that past knowledge about *fdisk needs to be re-evaluated because of the introduction of libfdisk and the rewrite of *fdisk to all use libfdisk.) I've added Colin in copy (Steve is there already) since both have toyed around with parted and “modern” stuff over the past few months. But I'd feel safer if that udeb drop could be happening after D-I Stretch Alpha 1 has been released. If you at any point in the future see the need for re-adding the cfdisk-udeb please don't hesitate to raise that request in the future. The removal is in no way a permanent strategical move. Just the most convenient and suitable one at the moment to avoid stalling progress. Right now, I don't think removing it would hurt us; that was also Steve's first impression. So feel free to go ahead. Mraw, KiBi. signature.asc Description: Digital signature
Re: proofreading the installation-guide
Holger Wansing wrote: Justin B Rye justin.byam@gmail.com wrote: An interesting idea, but one that seems unlikely to work, especially given the way it's used in the text. For instance, there's a page welcome/what-is-debian-linux.xml, which is full of sentences like debian; was the first Linux distribution to include a package management system. It was mostly me changing Debian into debian; that days in 2010. If I remember correctly, it was initiated by a post of Frans Pop, who proposed that change. And the rationale was in fact, to get a manual, that can easily be turned from a Debian installer manual into a Ubuntu installer manual, for example. Whoever it is that's reworking the manual for the derivative is still going to need to go through the whole text changing the content. The debian; entity seems liable to cost us more effort than it saves them (a single extra search-and-replace operation). And I can't see any particular pattern in when it's Debian installer, when it's debian; installer, and when it's d-i;. With the above been said, it should be as follows: In sentences which apply to Debian and also to its derivates, it should use debian; , while in sentences which only apply to Debian and not to the derivates, it should be Debian. It was also my intention to make it that way indeed, but: 1. I found out that the job was bigger than I first thought when taking it over, leading to mistakes. 2. due to the lack of manpower in the d-i team, especially the loss of Frans, the d-i manual guru (amongst other roles), there was probably not enough reviewing of that changes, and things may got overlooked. Oh, well, for now I'll plan on trying to get debian; into shape as part of my proofreading sweep - it would be easy enough to switch back from sometimes saying debian; to always saying Debian if we decide to give up on it. The debian-gnu; entity is effectively just shorthand for Debian GNU/arch-kernel; - confusing but handy. Wait, does it expand to Debian or debian;? The architecture;, arch-title; and arch-kernel; entities are slightly oddly named Since I keep losing track and having to check again, I'll leave a note for myself here: architecture; = 32-bit PC, 32-bit soft-float ARM, etc. arch-title; = i386, armel, etc. arch-kernel; = Linux, KFreeBSD, etc. but make sense as parametrisations, as do release; and releasename; as long as they're used for things that stay true for every release. (Oh, and I've just noticed there's a releasename-cap;, used instead of plain releasename; for no obvious reason in hardware/supported/arm.xml and nowhere else.) But there are also special entities for enterkey;, escapekey;, tabkey;, f10key;, and even ekey;! Most of these are only used once each - the rest of the time (and always for keys like F2 or space) it just uses keycap.../keycap. That entities like releasename-cap; enterkey; escapekey; tabkey; were created, to give translators a chance to follow the rules for their language there (for example, in German we write Jessie, Stretch or Unstable uppercase, while in English that's mostly lowercase: jessie, stretch, unstable) or to have tab key translated into Tabulator-Taste for German, for example. Sorry, I don't follow. Surely German needs *all* instances of releasename; to be capitalised? How does it help to have some of them replaced in the text with releasename-cap;? And why is it any easier to provide translations for tabkey; than for keycodeTab/keycode? Why would you need ones for f10key; and ekey;, but not keycodeF2/keycode or keycodeSpace/keycode? Hmm, I can imagine cases where the *English* version might benefit from having an entity indefinitearticle; that automatically selects either a or an depending on whether the following substituted-in word starts with a vowel sound! But let's not. Globally said, there may be several occurrences of above things not being perfectly consistent, because there are many editors for the manual these days, but there is no Frans Pop anymore, watching the changings and correcting things where needed. [PS included for convenience:] So I suppose it would be reasonable to put a comment in the document source explaining this, perhaps where these macros are defined, and making further changes as we discover the need and have time, possibly prompted by bug reports from Debian derivatives or forks, or even just doing a diff between our d-i manual and some of the derivatives' Okay. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150728200603.ga13...@xibalba.demon.co.uk
Re: proofreading the installation-guide
On Tue, Jul 28, 2015 at 07:00:27PM +0200, Holger Wansing wrote: Hi, Justin B Rye justin.byam@gmail.com wrote: Hendrik Boom wrote: Justin B Rye wrote: * entity questions - when am I meant to say Debian and when is it debian;? This like many of these entities seems to have no obvious function other than to make the source harder to interpret... * The d-i; entity expands to debian-installer in bold verbatim lowercase. If that is in effect the brandname of the software project then presumably we shouldn't be talking about the d-i; - that ought to be the Debian installer. Presumably both of these parametrisations are for the convenience of Debian derivatives and forks. By making these macros, it's easier for the, and it'll be easier for us to merge downstream patches. An interesting idea, but one that seems unlikely to work, especially given the way it's used in the text. For instance, there's a page welcome/what-is-debian-linux.xml, which is full of sentences like debian; was the first Linux distribution to include a package management system. It was mostly me changing Debian into debian; that days in 2010. If I remember correctly, it was initiated by a post of Frans Pop, who proposed that change. And the rationale was in fact, to get a manual, that can easily be turned from a Debian installer manual into a Ubuntu installer manual, for example. And I can't see any particular pattern in when it's Debian installer, when it's debian; installer, and when it's d-i;. With the above been said, it should be as follows: In sentences which apply to Debian and also to its derivates, it should use debian; , while in sentences which only apply to Debian and not to the derivates, it should be Debian. It was also my intention to make it that way indeed, but: 1. I found out that the job was bigger than I first thought when taking it over, leading to mistakes. 2. due to the lack of manpower in the d-i team, especially the loss of Frans, the d-i manual guru (amongst other roles), there was probably not enough reviewing of that changes, and things may got overlooked. The debian-gnu; entity is effectively just shorthand for Debian GNU/arch-kernel; - confusing but handy. The architecture;, arch-title; and arch-kernel; entities are slightly oddly named but make sense as parametrisations, as do release; and releasename; as long as they're used for things that stay true for every release. (Oh, and I've just noticed there's a releasename-cap;, used instead of plain releasename; for no obvious reason in hardware/supported/arm.xml and nowhere else.) But there are also special entities for enterkey;, escapekey;, tabkey;, f10key;, and even ekey;! Most of these are only used once each - the rest of the time (and always for keys like F2 or space) it just uses keycap.../keycap. That entities like releasename-cap; enterkey; escapekey; tabkey; were created, to give translators a chance to follow the rules for their language there (for example, in German we write Jessie, Stretch or Unstable uppercase, while in English that's mostly lowercase: jessie, stretch, unstable) or to have tab key translated into Tabulator-Taste for German, for example. Globally said, there may be several occurrences of above things not being perfectly consistent, because there are many editors for the manual these days, but there is no Frans Pop anymore, watching the changings and correcting things where needed. So I suppose it would be reasonable to put a comment in the document source explaining this, perhaps where these macros are defined, and making further changes as we discover the need and have time, possibly prompted by bug reports from Debian derivatives or forks, or even just doing a diff between our d-i manual and some of the derivatives' -- hendrik -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150728192418.gb4...@topoi.pooq.com
Re: proofreading the installation-guide
Hi, Justin B Rye justin.byam@gmail.com wrote: Holger Wansing wrote: Justin B Rye justin.byam@gmail.com wrote: The debian-gnu; entity is effectively just shorthand for Debian GNU/arch-kernel; - confusing but handy. Wait, does it expand to Debian or debian;? debian-gnu; - debian; GNU/arch-kernel; - Debian GNU/Linux | Debian GNU/kFreeBSD [...] But there are also special entities for enterkey;, escapekey;, tabkey;, f10key;, and even ekey;! Most of these are only used once each - the rest of the time (and always for keys like F2 or space) it just uses keycap.../keycap. That entities like releasename-cap; enterkey; escapekey; tabkey; were created, to give translators a chance to follow the rules for their language there (for example, in German we write Jessie, Stretch or Unstable uppercase, while in English that's mostly lowercase: jessie, stretch, unstable) or to have tab key translated into Tabulator-Taste for German, for example. Sorry, I don't follow. Surely German needs *all* instances of releasename; to be capitalised? How does it help to have some of them replaced in the text with releasename-cap;? No, not _all_ instances of releasename; have to be capitalised in German, for example in URLs they will have to stay lowercase. But I can use releasename; or releasename-cap; in my translation, where releasename; is used in English. And why is it any easier to provide translations for tabkey; than for keycodeTab/keycode? Why would you need ones for f10key; and ekey;, but not keycodeF2/keycode or keycodeSpace/keycode? This is probably not perfect, maybe it was in the beginning, and then Frans left us? I don't know the exact details, so simply my best guess, maybe. I don't see any benefit on the f10key; or ekey;, too. Holger -- Created with Sylpheed 3.5.0 under D E B I A N L I N U X 8 . 0J E S S I E . Registered Linux User #311290 - https://linuxcounter.net/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150728222342.7870e3bed76d5395701be...@wansing-online.de
