Please unblock dmraid/1.0.0.rc15-6 (udebs)
Hi, Could you unblock dmraid/1.0.0.rc15-6 please? Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
Re: please approve / unblock pciutils/1:3.1.2-3 (udeb)
unblocked -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Please unblock dmraid/1.0.0.rc15-6 (udebs)
Giuseppe Iuculano wrote: Hi, Could you unblock dmraid/1.0.0.rc15-6 please? unblocked Cheers Luk -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522653: win32-loader: [INTL:ru] Russian program translation update
Package: win32-loader Version: 0.6.10 Severity: wishlist Tags: l10n patch Russian program translation update is attached. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash # translation of ru.po to Russian # This file is distributed under the same license as the win32-loader package. # # Evgeny Burzak moon...@yandex.ru, 2006. # Yuri Kozlov kozlo...@gmail.com, 2007, 2008. # Yuri Kozlov yu...@komyakino.ru, 2009. msgid msgstr Project-Id-Version: win32-loader 0.6.10\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2009-01-03 22:10+\n PO-Revision-Date: 2009-03-22 09:12+0300\n Last-Translator: Yuri Kozlov yu...@komyakino.ru\n Language-Team: Russian debian-l10n-russ...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n X-Generator: KBabel 1.11.4\n Plural-Forms: nplurals=3; plural=(n%10==1 n%100!=11 ? 0 : n%10=2 n%10=4 (n%10010 || n%100=20) ? 1 : 2);\n #. translate: #. This must be a valid string recognised by Nsis. If your #. language is not yet supported by Nsis, please translate the #. missing Nsis part first. #. #: win32-loader.sh:36 win32-loader.c:39 msgid LANG_ENGLISH msgstr LANG_RUSSIAN #. translate: #. This must be the string used by GNU iconv to represent the charset used #. by Windows for your language. If you don't know, check #. [wine]/tools/wmc/lang.c, or http://www.microsoft.com/globaldev/reference/WinCP.mspx #. #. IMPORTANT: In the rest of this file, only the subset of UTF-8 that can be #. converted to this charset should be used. #: win32-loader.sh:52 msgid windows-1252 msgstr windows-1251 #. translate: #. Charset used by NTLDR in your localised version of Windows XP. If you #. don't know, maybe http://en.wikipedia.org/wiki/Code_page helps. #: win32-loader.sh:57 msgid cp437 msgstr cp866 #. translate: #. The name of your language _in English_ (must be restricted to ascii) #: win32-loader.sh:67 msgid English msgstr Russian #. translate: #. IMPORTANT: only the subset of UTF-8 that can be converted to NTLDR charset #. (e.g. cp437) should be used in this string. If you don't know which charset #. applies, limit yourself to ascii. #: win32-loader.sh:81 msgid Debian Installer msgstr Программа установки Debian #. translate: #. The nlf file for your language should be found in #. /usr/share/nsis/Contrib/Language files/ #. #: win32-loader.c:68 msgid English.nlf msgstr Russian.nlf #: win32-loader.c:71 msgid Debian-Installer Loader msgstr Загрузчик программы установки Debian #: win32-loader.c:72 msgid Cannot find win32-loader.ini. msgstr Не удалось найти win32-loader.ini. #: win32-loader.c:73 msgid win32-loader.ini is incomplete. Contact the provider of this medium. msgstr В win32-loader.ini не хватает данных. Обратитесь к поставщику этого носителя. #: win32-loader.c:74 msgid This program has detected that your keyboard type is \$0\. Is this correct? msgstr Обнаружено, что тип вашей клавиатуры \$0\. Это верно? #: win32-loader.c:75 msgid Please send a bug report with the following information:\n \n - Version of Windows.\n - Country settings.\n - Real keyboard type.\n - Detected keyboard type.\n \n Thank you. msgstr Отправьте отчёт об ошибке со следующей информацией:\n \n - версия Windows\n - региональные настройки\n - настоящий тип клавиатуры\n - определившийся тип клавиатуры\n \n Спасибо. #: win32-loader.c:76 msgid There doesn't seem to be enough free disk space in drive $c. For a complete desktop install, it is recommended to have at least 3 GB. If there is already a separate disk or partition to install Debian, or if you plan to replace Windows completely, you can safely ignore this warning. msgstr Недостаточно свободного места на диске $c. Для установки полноценного рабочего стола рекомендуется освободить на диске как минимум 3 Гб. Если в вашей системе уже есть отдельный жёсткий диск или раздел для установки Debian, или если вы планируете полностью отказаться от Windows, то просто проигнорируйте это предупреждение. #: win32-loader.c:77 msgid Error: not enough free disk space. Aborting install. msgstr Ошибка: недостаточно свободного места на жёстком диске. Отмена установки. #: win32-loader.c:78 msgid This program doesn't support Windows $windows_version yet. msgstr Эта программа пока не поддерживает Windows $windows_version. #: win32-loader.c:79 msgid The version of Debian you're trying to install is designed to run on modern, 64-bit computers. However, your computer is incapable of running 64-bit programs.\n \n Use the 32-bit (\i386\) version of Debian, or the Multi-arch version which is able to install either of them.\n \n This installer will abort now. msgstr Версия Debian, которую вы пытаетесь установить, разрабатывалась под современные 64-битные
Complete draft of the March 16th and 30th meetings minutes
FOlks, here is the complete draft of a report of our important meetings, which I intend to send as a Bits from the D-I team mail in a few days. Please comment and correct things if you feel like you have the courage to read all that logorrhea. Subject: Bits from the Debian Installer team After the release of Lenny, for which the Debian Installer team felt proud for being a part of the techn[ical successbut also guilty for being one of the release delay factors, the team felt the need to virtually sit down and discuss about our future, organization and technical challenges for the Lenny-Squeeze release cycle. For this, we organized two team meetings that were held on March 16th 2009 and March 31st 2006 [1]. This Bits from the D-I team post represents the minutes of these two meetings and will summary decisions and discussions that happened during the meetings. March 16th meeting: organisational issues - It is no mystery that the D-I team suffered from its low resources during the Etch-Lenny release cycle, particularlyvisible in difficulties felt to handle the release management work (please refer to Nomvember 2008 meetings minutes). As a consequence, the first satisfaction was having over 20 participants to the March 16th meeting and a very interactive and alive discussion. At the beginning of the meeting, a round table checkup confirmed that most participants were sharing that feeling. Nobody wanted to put any blame on our release manager (Otavio Salvador), except maybe Otavio himself. A certain lack of leadership is pointed, with indeed nobody really ready to take that leadership. To some extent, the leadership was shared between Otavio Salvador, Frans Pop and Christian Perrier, with sometimes obvious lack of real leadership. That also lead to some core components of D-I to be neglected in some way, though several team members did a great work maintaining them in releasable shape. On the other hand, the lack of developers was *also* pointed. Colin Watson noticeably insisted on the demotivation that can arise when most parts of D-I are frozen because of release preparation. That seems to have a high potential to demotivate potential participants to development. It was also pointed that former releases of D-I happened under a strong leadership by very involved, motivated people, who had a very noticeable amount of time to invest in these tasks (namely Joey Hess, then Frans Pop, who both lead the work and took the RM work in a similar way). That model reached its limits, apparently, when the release manager (who's seen as the leader) has a lower commitment reliability. As this is more likely than our previous situation, we need to learn about coping with that. The general conclusion is that we should try to have a clearer delineation between ongoing development and release-targeted work. Both need to happen and both should not conflict. In that matter, as we were able to release, what seems to be more missing is the technical leadership of the project, while the release manager remains the visible person. A general agreement is that Otavio had to spend too much time on technical work rather than focus on release priorities (building/uploading the kernel udebs is given as an example). Another agreement is that release preparation include a lot of work to coordinate, some of which could maybe be more automated (such as building more of D-I on the build daemons, running the daily builds in a more controlled environment or upload the debian-installer package more often...). Finally, after many discussions about various ways to take some load out of the RM shoulders, we settled on an organization where Otavio Salvador keeps working as D-I release manager, with some assistance during the release preparations: - Christian Perrier for all boring and tedious non technical tasks such as release announcement, web pages stuff, meeting organization (and reports, doh) - Luk Claes as dedicated link with the Debian Release Management and focusing on technical methods to take as much load as possible for the D-I RM - Jérémy Bobbio and Colin Watson as Backup experts option when tricky problems that might delay releases are identified Other widely accepted decisions were: - try having more technical leadership, not necessarily concentrated on the RM shoulders - do our best to avoid long freezes and keep the development pace active - try having development corners for our potential new contributors so that the team doesn't shrink down to the core team March 30th meeting: technical issues - release goals After the March 16th meeting that was focused on organisational and roles issues, we postponed the discussion of technical changes and Squeeze release goals to a dedicated meeting. That meeting had slightly fewer attendees, but again lasted for 2 hours and was very alive. Again, that seems to be
Re: Complete draft of the March 16th and 30th meetings minutes
On Sun, Apr 5, 2009 at 2:35 PM, Christian Perrier bubu...@debian.org wrote: FOlks, here is the complete draft of a report of our important meetings, which I intend to send as a Bits from the D-I team mail in a few days. Please comment and correct things if you feel like you have the courage to read all that logorrhea. It looks fine; I did read the first and this draft and I believe it is OK. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Complete draft of the March 16th and 30th meetings minutes
On Sunday 05 April 2009, Christian Perrier wrote: Similarly, the installation guide could be uploaded more often, of course without translation freeze. That would help better spotting issues, errors or missing parts, hopefully. Speaking as the person who has done 90% of the work on the manual and done _all_ of its releases as a separate package: this is total nonsense. Anybody who thinks this has never seriously looked at how the manual is currently written, translated, built, distributed and used. BTW, I still do consider myself to be the RM for the manual and would be very unhappy with anybody uploading it without at the very least talking to me first. signature.asc Description: This is a digitally signed message part.
Processing of debian-installer_20070308etch4_amd64.changes
debian-installer_20070308etch4_amd64.changes uploaded successfully to ftp.upload.debian.org along with the files: debian-installer_20070308etch4.dsc debian-installer_20070308etch4.tar.gz debian-installer_20070308etch4_amd64.deb debian-installer-images_20070308etch4_amd64.tar.gz Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of debian-installer_20070308etch4_amd64.changes
debian-installer_20070308etch4_amd64.changes uploaded successfully to localhost along with the files: debian-installer_20070308etch4.dsc debian-installer_20070308etch4.tar.gz debian-installer_20070308etch4_amd64.deb debian-installer-images_20070308etch4_amd64.tar.gz Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
debian-installer_20070308etch4_amd64.changes ACCEPTED
Mapping oldstable to oldstable-proposed-updates. Accepted: debian-installer-images_20070308etch4_amd64.tar.gz byhand debian-installer_20070308etch4.dsc to pool/main/d/debian-installer/debian-installer_20070308etch4.dsc debian-installer_20070308etch4.tar.gz to pool/main/d/debian-installer/debian-installer_20070308etch4.tar.gz debian-installer_20070308etch4_amd64.deb to pool/main/d/debian-installer/debian-installer_20070308etch4_amd64.deb Changes: debian-installer (20070308etch4) oldstable; urgency=low . * Rebuild to ensure that we include the updated archive key. Override entries for your package: debian-installer_20070308etch4.dsc - source devel debian-installer_20070308etch4_amd64.deb - optional devel Announcing to debian-chan...@lists.debian.org 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
Processing of cdebconf_0.140_amd64.changes
cdebconf_0.140_amd64.changes uploaded successfully to ftp.upload.debian.org along with the files: cdebconf_0.140.dsc cdebconf_0.140.tar.gz cdebconf-priority_0.140_all.udeb cdebconf_0.140_amd64.deb libdebconfclient0_0.140_amd64.deb libdebconfclient0-dev_0.140_amd64.deb cdebconf-udeb_0.140_amd64.udeb libdebconfclient0-udeb_0.140_amd64.udeb cdebconf-newt-udeb_0.140_amd64.udeb cdebconf-text-udeb_0.140_amd64.udeb cdebconf-gtk-udeb_0.140_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of cdebconf_0.140_amd64.changes
cdebconf_0.140_amd64.changes uploaded successfully to localhost along with the files: cdebconf_0.140.dsc cdebconf_0.140.tar.gz cdebconf-priority_0.140_all.udeb cdebconf_0.140_amd64.deb libdebconfclient0_0.140_amd64.deb libdebconfclient0-dev_0.140_amd64.deb cdebconf-udeb_0.140_amd64.udeb libdebconfclient0-udeb_0.140_amd64.udeb cdebconf-newt-udeb_0.140_amd64.udeb cdebconf-text-udeb_0.140_amd64.udeb cdebconf-gtk-udeb_0.140_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of netcfg_1.48_amd64.changes
netcfg_1.48_amd64.changes uploaded successfully to ftp.upload.debian.org along with the files: netcfg_1.48.dsc netcfg_1.48.tar.gz netcfg_1.48_amd64.udeb netcfg-static_1.48_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of netcfg_1.48_amd64.changes
netcfg_1.48_amd64.changes uploaded successfully to localhost along with the files: netcfg_1.48.dsc netcfg_1.48.tar.gz netcfg_1.48_amd64.udeb netcfg-static_1.48_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of rootskel_1.75_amd64.changes
rootskel_1.75_amd64.changes uploaded successfully to ftp.upload.debian.org along with the files: rootskel_1.75.dsc rootskel_1.75.tar.gz rootskel_1.75_amd64.udeb rootskel-bootfloppy_1.75_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of debian-installer-utils_1.67_amd64.changes
debian-installer-utils_1.67_amd64.changes uploaded successfully to ftp.upload.debian.org along with the files: debian-installer-utils_1.67.dsc debian-installer-utils_1.67.tar.gz di-utils-shell_1.67_all.udeb di-utils-reboot_1.67_all.udeb di-utils-exit-installer_1.67_all.udeb di-utils-terminfo_1.67_all.udeb di-utils_1.67_amd64.udeb di-utils-mapdevfs_1.67_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of debian-installer-utils_1.67_amd64.changes
debian-installer-utils_1.67_amd64.changes uploaded successfully to localhost along with the files: debian-installer-utils_1.67.dsc debian-installer-utils_1.67.tar.gz di-utils-shell_1.67_all.udeb di-utils-reboot_1.67_all.udeb di-utils-exit-installer_1.67_all.udeb di-utils-terminfo_1.67_all.udeb di-utils_1.67_amd64.udeb di-utils-mapdevfs_1.67_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of rootskel_1.75_amd64.changes
rootskel_1.75_amd64.changes uploaded successfully to localhost along with the files: rootskel_1.75.dsc rootskel_1.75.tar.gz rootskel_1.75_amd64.udeb rootskel-bootfloppy_1.75_amd64.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Продажа и монтаж сайдинга Mitten, Georgia-Pacific, СertainTeed
ПР0ДАЖА И М0НТАЖ САЙДИНГА И В0Д0СТ0К0В! - Наша кoмпания продает высококачественный винилoвый и цокoльный сaйдинг производства Канады, США и России! ЦEНЫ на материалы - значительно НИЖЕ рыночных, за счет прямых закупок у экспортеров и специальных скидок предоставленных для нашей кoмпании! Выполняем доставку и монтаж любого вида сайдинга в кратчайшие сроки! Выезжаем на замеры без выходных и задержек! Наши менеджеры принимают звонки круглосуточно! Цeны на уcлуги мoнтажа Вас приятно удивят! Работаем по схеме: Замер - Расчет - Доставка - Монтаж ! _ Для более подробной информации, позвоните нашим мeнeджерам! Телeфон менеджерa: 8 903-275-33-27 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Complete draft of the March 16th and 30th meetings minutes
Christian Perrier wrote: Please comment and correct things if you feel like you have the courage to read all that logorrhea. Ok, I'll sometimes be a bit picky, though it's to have a better announcement :-) Subject: Bits from the Debian Installer team After the release of Lenny, for which the Debian Installer team felt proud for being a part of the techn[ical successbut also guilty for technical being one of the release delay factors, the team felt the need to virtually sit down and discuss about our future, organization and technical challenges for the Lenny-Squeeze release cycle. For this, we organized two team meetings that were held on March 16th 2009 and March 31st 2006 [1]. 2009 ... This Bits from the D-I team post represents the minutes of these two meetings and will summary decisions and discussions that happened summarise during the meetings. March 16th meeting: organisational issues - It is no mystery that the D-I team suffered from its low resources during the Etch-Lenny release cycle, particularlyvisible in particulary visible difficulties felt to handle the release management work (please refer to Nomvember 2008 meetings minutes). to the November 2008 meeting minutes It would be good to have a link here. As a consequence, the first satisfaction was having over 20 participants to the March 16th meeting and a very interactive and alive discussion. At the beginning of the meeting, a round table checkup confirmed that most participants were sharing that feeling. Nobody wanted to put any s/that/the above mentioned/ blame on our release manager (Otavio Salvador), except maybe Otavio himself. A certain lack of leadership is pointed, with indeed nobody pointed out really ready to take that leadership. To some extent, the leadership was shared between Otavio Salvador, Frans Pop and Christian Perrier, with sometimes obvious lack of real leadership. That also lead to some core components of D-I to be neglected in some way, though several team members did a great work maintaining them in releasable shape. On the other hand, the lack of developers was *also* pointed. Colin pointed out Watson noticeably insisted on the demotivation that can arise when most parts of D-I are frozen because of release preparation. That seems to have a high potential to demotivate potential participants to development. It was also pointed that former releases of D-I happened under a pointed out strong leadership by very involved, motivated people, who had a very noticeable amount of time to invest in these tasks (namely Joey Hess, then Frans Pop, who both lead the work and took the RM work in a similar way). That model reached its limits, apparently, when the release manager (who's seen as the leader) has a lower commitment reliability. As this is more likely than our previous situation, we need to learn about coping with that. The general conclusion is that we should try to have a clearer delineation between ongoing development and release-targeted work. Both need to happen and both should not conflict. In that matter, as we were able to release, what seems to be more missing is the technical leadership of the project, while the release manager remains the visible person. A general agreement is that Otavio had to spend too much time on technical work rather than focus on release priorities (building/uploading the kernel udebs is given as an example). Another agreement is that release preparation include a lot of work to coordinate, some of which could maybe be more automated (such as building more of D-I on the build daemons, running the daily builds in a more controlled environment or upload the debian-installer package more often...). Finally, after many discussions about various ways to take some load out of the RM shoulders, we settled on an organization where Otavio Salvador keeps working as D-I release manager, with some assistance during the release preparations: - Christian Perrier for all boring and tedious non technical tasks such as release announcement, web pages stuff, meeting organization (and reports, doh) - Luk Claes as dedicated link with the Debian Release Management and focusing on technical methods to take as much load as possible for the D-I RM - Jérémy Bobbio and Colin Watson as Backup experts option when tricky problems that might delay releases are identified Other widely accepted decisions were: - try having more technical leadership, not necessarily concentrated on the RM shoulders - do our best to avoid long freezes and keep the development pace active - try having development corners for our potential new contributors so that the team doesn't shrink down to the core team March 30th meeting: technical issues - release goals After the March 16th meeting that
netcfg_1.48_amd64.changes ACCEPTED
Accepted: netcfg-static_1.48_amd64.udeb to pool/main/n/netcfg/netcfg-static_1.48_amd64.udeb netcfg_1.48.dsc to pool/main/n/netcfg/netcfg_1.48.dsc netcfg_1.48.tar.gz to pool/main/n/netcfg/netcfg_1.48.tar.gz netcfg_1.48_amd64.udeb to pool/main/n/netcfg/netcfg_1.48_amd64.udeb Override entries for your package: netcfg-static_1.48_amd64.udeb - optional debian-installer netcfg_1.48.dsc - source debian-installer netcfg_1.48_amd64.udeb - optional debian-installer Announcing to debian-devel-chan...@lists.debian.org 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
debian-installer-utils_1.67_amd64.changes ACCEPTED
Accepted: debian-installer-utils_1.67.dsc to pool/main/d/debian-installer-utils/debian-installer-utils_1.67.dsc debian-installer-utils_1.67.tar.gz to pool/main/d/debian-installer-utils/debian-installer-utils_1.67.tar.gz di-utils-exit-installer_1.67_all.udeb to pool/main/d/debian-installer-utils/di-utils-exit-installer_1.67_all.udeb di-utils-mapdevfs_1.67_amd64.udeb to pool/main/d/debian-installer-utils/di-utils-mapdevfs_1.67_amd64.udeb di-utils-reboot_1.67_all.udeb to pool/main/d/debian-installer-utils/di-utils-reboot_1.67_all.udeb di-utils-shell_1.67_all.udeb to pool/main/d/debian-installer-utils/di-utils-shell_1.67_all.udeb di-utils-terminfo_1.67_all.udeb to pool/main/d/debian-installer-utils/di-utils-terminfo_1.67_all.udeb di-utils_1.67_amd64.udeb to pool/main/d/debian-installer-utils/di-utils_1.67_amd64.udeb Override entries for your package: debian-installer-utils_1.67.dsc - source debian-installer di-utils-exit-installer_1.67_all.udeb - extra debian-installer di-utils-mapdevfs_1.67_amd64.udeb - standard debian-installer di-utils-reboot_1.67_all.udeb - standard debian-installer di-utils-shell_1.67_all.udeb - standard debian-installer di-utils-terminfo_1.67_all.udeb - standard debian-installer di-utils_1.67_amd64.udeb - standard debian-installer Announcing to debian-devel-chan...@lists.debian.org 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
Re: Complete draft of the March 16th and 30th meetings minutes
s/Ryan Nebur/Ryan Niebur/ -- _ Ryan Niebur ryanrya...@gmail.com signature.asc Description: Digital signature
rootskel_1.75_amd64.changes ACCEPTED
Accepted: rootskel-bootfloppy_1.75_amd64.udeb to pool/main/r/rootskel/rootskel-bootfloppy_1.75_amd64.udeb rootskel_1.75.dsc to pool/main/r/rootskel/rootskel_1.75.dsc rootskel_1.75.tar.gz to pool/main/r/rootskel/rootskel_1.75.tar.gz rootskel_1.75_amd64.udeb to pool/main/r/rootskel/rootskel_1.75_amd64.udeb Override entries for your package: rootskel-bootfloppy_1.75_amd64.udeb - extra debian-installer rootskel_1.75.dsc - source debian-installer rootskel_1.75_amd64.udeb - standard debian-installer Announcing to debian-devel-chan...@lists.debian.org 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
cdebconf_0.140_amd64.changes ACCEPTED
Accepted: cdebconf-gtk-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-gtk-udeb_0.140_amd64.udeb cdebconf-newt-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-newt-udeb_0.140_amd64.udeb cdebconf-priority_0.140_all.udeb to pool/main/c/cdebconf/cdebconf-priority_0.140_all.udeb cdebconf-text-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-text-udeb_0.140_amd64.udeb cdebconf-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-udeb_0.140_amd64.udeb cdebconf_0.140.dsc to pool/main/c/cdebconf/cdebconf_0.140.dsc cdebconf_0.140.tar.gz to pool/main/c/cdebconf/cdebconf_0.140.tar.gz cdebconf_0.140_amd64.deb to pool/main/c/cdebconf/cdebconf_0.140_amd64.deb libdebconfclient0-dev_0.140_amd64.deb to pool/main/c/cdebconf/libdebconfclient0-dev_0.140_amd64.deb libdebconfclient0-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/libdebconfclient0-udeb_0.140_amd64.udeb libdebconfclient0_0.140_amd64.deb to pool/main/c/cdebconf/libdebconfclient0_0.140_amd64.deb Override entries for your package: cdebconf-gtk-udeb_0.140_amd64.udeb - optional debian-installer cdebconf-newt-udeb_0.140_amd64.udeb - optional debian-installer cdebconf-priority_0.140_all.udeb - standard debian-installer cdebconf-text-udeb_0.140_amd64.udeb - optional debian-installer cdebconf-udeb_0.140_amd64.udeb - standard debian-installer cdebconf_0.140.dsc - source utils cdebconf_0.140_amd64.deb - extra utils libdebconfclient0-dev_0.140_amd64.deb - optional libdevel libdebconfclient0-udeb_0.140_amd64.udeb - optional debian-installer libdebconfclient0_0.140_amd64.deb - optional libs Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 343119 507372 508042 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
Bug#343119: marked as done (cdebconf: Display bug for notes templates in some situations)
Your message dated Sun, 05 Apr 2009 21:02:19 + with message-id e1lqztv-0007cc...@ries.debian.org and subject line Bug#343119: fixed in cdebconf 0.140 has caused the Debian Bug report #343119, regarding cdebconf: Display bug for notes templates in some situations 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.) -- 343119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cdebconf Severity: normal This bugs only seems to happen in rare situations. To experience it, one has to run an install in Bosnian, for instance. The bug can be seen on the cdebconf Change questions priority screen. So, to reproduce it, you first need running the initial parts of the install, up to Lad installer components step. Then Change debconf questions priority appears in the main menu: Promjeni debconf nivo prioritera. When choosing it, the select screen for priority is displayed. Lilke for many languages, this screen does not fit on one screen. However, contrary to these other languages, the screen does not display a first screen with an OK button, followed by the choices list. In contrary, the screen has no widget at all, only the text of the template. Moving the arrow keys up and down shows that the cursor virtually moves through choices, without any of these displayed. I suspect this is more a newt bug than a cdebconf bugplease reassign where appropriate. I should anyway urge translators to *reduce* the size of this screen...which is what I did for French. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-1-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Source: cdebconf Source-Version: 0.140 We believe that the bug you reported is fixed in the latest version of cdebconf, which is due to be installed in the Debian FTP archive: cdebconf-gtk-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-gtk-udeb_0.140_amd64.udeb cdebconf-newt-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-newt-udeb_0.140_amd64.udeb cdebconf-priority_0.140_all.udeb to pool/main/c/cdebconf/cdebconf-priority_0.140_all.udeb cdebconf-text-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-text-udeb_0.140_amd64.udeb cdebconf-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-udeb_0.140_amd64.udeb cdebconf_0.140.dsc to pool/main/c/cdebconf/cdebconf_0.140.dsc cdebconf_0.140.tar.gz to pool/main/c/cdebconf/cdebconf_0.140.tar.gz cdebconf_0.140_amd64.deb to pool/main/c/cdebconf/cdebconf_0.140_amd64.deb libdebconfclient0-dev_0.140_amd64.deb to pool/main/c/cdebconf/libdebconfclient0-dev_0.140_amd64.deb libdebconfclient0-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/libdebconfclient0-udeb_0.140_amd64.udeb libdebconfclient0_0.140_amd64.deb to pool/main/c/cdebconf/libdebconfclient0_0.140_amd64.deb 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 343...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Otavio Salvador ota...@debian.org (supplier of updated cdebconf 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 05 Apr 2009 17:36:15 -0300 Source: cdebconf Binary: cdebconf libdebconfclient0 libdebconfclient0-dev cdebconf-udeb cdebconf-priority libdebconfclient0-udeb cdebconf-slang-udeb cdebconf-newt-udeb cdebconf-text-udeb cdebconf-gtk-udeb Architecture: source all amd64 Version: 0.140 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Otavio Salvador ota...@debian.org Description: cdebconf - Debian Configuration Management System (C-implementation) cdebconf-gtk-udeb - Gtk+ frontend for Debian Configuration Management System (udeb) cdebconf-newt-udeb - Newt frontend for Debian Configuration Management System (udeb) cdebconf-priority - Change debconf priority (udeb) cdebconf-slang-udeb - S-Lang frontend for Debian Configuration Management System (udeb) cdebconf-text-udeb - Plain text frontend for Debian Configuration
Bug#508042: marked as done (newt frontent have inefficient use of screen real estate (multiselect))
Your message dated Sun, 05 Apr 2009 21:02:19 + with message-id e1lqztv-0007cg...@ries.debian.org and subject line Bug#508042: fixed in cdebconf 0.140 has caused the Debian Bug report #508042, regarding newt frontent have inefficient use of screen real estate (multiselect) 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.) -- 508042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cdebconf-text-udeb Version: 0.137 Severity: important User: debian-...@lists.debian.org UserTags: debian-edu x-debbugs-cc: debian-...@lists.debian.org The profile question in Debian Edu/Lenny do not look good. The multiselect question do not select all the four options, but only the first three and a scroll bar, while the display have three blank lines between the question text and the question itself. See the attached image d-i-edu-danish-profile.png for an example. This is the normal profile question in the debian-edu-install package. The expert question have more options, and look even worse. Here, the text fill the entire screen, and instead of moving the multiselect part of the question to another screen (which is done when not using preformattet text), it display the question at the lower end, on top of/below the button continue button. See the attached image d-i-edu-english-profile-expert.png. The expert profile question is not usable (not able to see properly the options to select them), while the normal profile is just confusing to users. Because of this, I set severity to important. Happy hacking, -- Petter Reinholdtsen inline: d-i-edu-danish-profile.pnginlie: d-i-edu-english-profile-expert.png pgpsuXtoROfhA.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: cdebconf Source-Version: 0.140 We believe that the bug you reported is fixed in the latest version of cdebconf, which is due to be installed in the Debian FTP archive: cdebconf-gtk-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-gtk-udeb_0.140_amd64.udeb cdebconf-newt-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-newt-udeb_0.140_amd64.udeb cdebconf-priority_0.140_all.udeb to pool/main/c/cdebconf/cdebconf-priority_0.140_all.udeb cdebconf-text-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-text-udeb_0.140_amd64.udeb cdebconf-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/cdebconf-udeb_0.140_amd64.udeb cdebconf_0.140.dsc to pool/main/c/cdebconf/cdebconf_0.140.dsc cdebconf_0.140.tar.gz to pool/main/c/cdebconf/cdebconf_0.140.tar.gz cdebconf_0.140_amd64.deb to pool/main/c/cdebconf/cdebconf_0.140_amd64.deb libdebconfclient0-dev_0.140_amd64.deb to pool/main/c/cdebconf/libdebconfclient0-dev_0.140_amd64.deb libdebconfclient0-udeb_0.140_amd64.udeb to pool/main/c/cdebconf/libdebconfclient0-udeb_0.140_amd64.udeb libdebconfclient0_0.140_amd64.deb to pool/main/c/cdebconf/libdebconfclient0_0.140_amd64.deb 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 508...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Otavio Salvador ota...@debian.org (supplier of updated cdebconf 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...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 05 Apr 2009 17:36:15 -0300 Source: cdebconf Binary: cdebconf libdebconfclient0 libdebconfclient0-dev cdebconf-udeb cdebconf-priority libdebconfclient0-udeb cdebconf-slang-udeb cdebconf-newt-udeb cdebconf-text-udeb cdebconf-gtk-udeb Architecture: source all amd64 Version: 0.140 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Otavio Salvador ota...@debian.org Description: cdebconf - Debian Configuration Management System (C-implementation) cdebconf-gtk-udeb - Gtk+ frontend for Debian Configuration Management System (udeb) cdebconf-newt-udeb - Newt frontend for Debian Configuration Management System (udeb) cdebconf-priority - Change debconf priority (udeb) cdebconf-slang-udeb - S-Lang frontend for Debian Configuration Management System (udeb) cdebconf-text-udeb - Plain text frontend for Debian Configuration Management System (udeb) cdebconf-udeb - Debian Configuration Management System
Bug#507372: marked as done (cdebconf-newt-udeb: does not show enough choices for long descriptions)
Your message dated Sun, 05 Apr 2009 21:02:19 +
with message-id e1lqztv-0007ce...@ries.debian.org
and subject line Bug#507372: fixed in cdebconf 0.140
has caused the Debian Bug report #507372,
regarding cdebconf-newt-udeb: does not show enough choices for long descriptions
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.)
--
507372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: cdebconf-newt-udeb
Severity: minor
Tags: patch
On Mon, Nov 24, 2008 at 09:12:58PM +0100, Ferenc Wagner wrote:
I've pulled the netboot Xen variant and did a paravirtual
installation. It went all right, but I noticed a mysterious empty box
on the APT setup screen: see http://apt.niif.hu/apt-config.png above
the Continue button. Is that maybe a degenerated scrollbar, where
volatile is hiding? It isn't included in sources.list after
installation. I can't test it until tomorrow, but it's unfortunate
either way...
Indeed, the minimum size requirement for select/multiselect questions
was not computed maximum number of lines that could be used for the
description.
The attached patch fix this issue. I have run an installation through
the end without any problem with the patch applied.
Cheers,
--
Jérémy Bobbio.''`.
lu...@debian.org: :Ⓐ : # apt-get install anarchism
`. `'`
`-
diff --git a/packages/cdebconf/src/modules/frontend/newt/newt.c b/packages/cdebconf/src/modules/frontend/newt/newt.c
index 71dd5c3..4137ff7 100644
--- a/packages/cdebconf/src/modules/frontend/newt/newt.c
+++ b/packages/cdebconf/src/modules/frontend/newt/newt.c
@@ -118,6 +118,7 @@ struct newtColors newtAltColorPalette = {
typedef int (newt_handler)(struct frontend *obj, struct question *q);
static void newt_progress_stop(struct frontend *obj);
+static char *get_full_description(struct frontend *obj, struct question *q);
#include cdebconf_newt.h
@@ -255,11 +256,11 @@ min_window_height(struct frontend *obj, struct question *q, int win_width)
{
int height = 3;
char *type = q-template-type;
-char *q_ext_text;
+char *full_description;
-q_ext_text = q_get_extended_description(obj, q);
-if (q_ext_text != NULL)
-height = cdebconf_newt_get_text_height(q_ext_text, win_width) + 1;
+full_description = get_full_description(obj, q);
+if (full_description != NULL)
+height = cdebconf_newt_get_text_height(full_description, win_width) + 1;
if (strcmp(type, multiselect) == 0 || strcmp(type, select) == 0)
height += 4; // at least three lines for choices + blank line
else if (strcmp(type, string) == 0 || strcmp(type, password) == 0)
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: cdebconf
Source-Version: 0.140
We believe that the bug you reported is fixed in the latest version of
cdebconf, which is due to be installed in the Debian FTP archive:
cdebconf-gtk-udeb_0.140_amd64.udeb
to pool/main/c/cdebconf/cdebconf-gtk-udeb_0.140_amd64.udeb
cdebconf-newt-udeb_0.140_amd64.udeb
to pool/main/c/cdebconf/cdebconf-newt-udeb_0.140_amd64.udeb
cdebconf-priority_0.140_all.udeb
to pool/main/c/cdebconf/cdebconf-priority_0.140_all.udeb
cdebconf-text-udeb_0.140_amd64.udeb
to pool/main/c/cdebconf/cdebconf-text-udeb_0.140_amd64.udeb
cdebconf-udeb_0.140_amd64.udeb
to pool/main/c/cdebconf/cdebconf-udeb_0.140_amd64.udeb
cdebconf_0.140.dsc
to pool/main/c/cdebconf/cdebconf_0.140.dsc
cdebconf_0.140.tar.gz
to pool/main/c/cdebconf/cdebconf_0.140.tar.gz
cdebconf_0.140_amd64.deb
to pool/main/c/cdebconf/cdebconf_0.140_amd64.deb
libdebconfclient0-dev_0.140_amd64.deb
to pool/main/c/cdebconf/libdebconfclient0-dev_0.140_amd64.deb
libdebconfclient0-udeb_0.140_amd64.udeb
to pool/main/c/cdebconf/libdebconfclient0-udeb_0.140_amd64.udeb
libdebconfclient0_0.140_amd64.deb
to pool/main/c/cdebconf/libdebconfclient0_0.140_amd64.deb
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 507...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Otavio Salvador ota...@debian.org (supplier of updated cdebconf package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
[Debian Installer] Are the daily images usable?
Dear list, I am going to install Debian tomorrow on a i686 machine and wanted to use the daily images of the Debian Installer. Two questions. 1. Are the current daily images usable. [1] does not show too much problems. 2. Is there anything I should try out (installing over UMTS device, …) to report back how it went? Thanks, Paul [1] http://wiki.debian.org/DebianInstaller/Today signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Processed: Re: Bug#520582: debian-installer: installation guide includes deprecated `tzconfig`
Processing commands for cont...@bugs.debian.org: tags 520582 pending Bug#520582: debian-installer: installation guide includes deprecated `tzconfig` Tags were: patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#519508: installation-guide: Section 5.1.3 Booting from Linux Using LILO or GRUB assumes Linux is on hd0, 0
Processing commands for cont...@bugs.debian.org: tags 519508 pending Bug#519508: installation-guide: Section 5.1.3 Booting from Linux Using LILO or GRUB assumes Linux is on hd0, 0 There were no tags set. Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519508: installation-guide: Section 5.1.3 Booting from Linux Using LILO or GRUB assumes Linux is on hd0, 0
tags 519508 pending thanks On Friday 13 March 2009, Filipus Klutiero wrote: In section 5.1.3, if using GRUB, the procedure says to add lines kernel (hd0,0)/boot/newinstall/vmlinuz initrd (hd0,0)/boot/newinstall/initrd.gz This will of course only work if the files were copied to (hd0,0)/boot/newinstall/. Which is exactly what's suggested in section 4.4 to which 5.1.3 refers. BTW, I have no idea what the value of ramdisk_size refers to in Note that the value of the ramdisk_size may need to be adjusted for the size of the initrd image. (just below). Removed. That's a remnant from the 2.4 and early 2.6 kernel era. And another BTW, it would be more generic to talk about ISO images in the third paragraph, since the iso can also be a DVD image. I've added a mention of DVD. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#518018: installation-guide: Appendix B: mkpasswd example wrong
Processing commands for cont...@bugs.debian.org: tag 518018 pending Bug#518018: installation-guide: Appendix B: mkpasswd example wrong There were no tags set. Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#518018: installation-guide: Appendix B: mkpasswd example wrong
tag 518018 pending thanks On Tuesday 03 March 2009, Rene Engelhard wrote: What is working is the following: echo -n r00tme | mkpasswd -s -m md5 because echo then omits the \n which would end up into the hash otherwise... Thanks for reporting René. I've used 'printf' instead of 'echo -n' for better portability. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511053: [patch] minor fixes to partman/preseeding notes
On Wednesday 07 January 2009, Vincent McIntyre wrote: Two patches are attached for your consideration. - partman-auto-recipe.txt.patch a few suggested grammatical changes Committed. Thanks. - preseed.xml it is now possible to preseed multiple disks try to enhance preseeding example's comments point to partman-auto-recipe.txt on websvn. mention lvm-related improvements This needs a bit of work (description of 'crypto' is not entirely accurate for example). Also, I'm planning a stable update of the manual currently and prefer to delay making these changes until after that. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509372: typo in installation-guide/po/ja/using-d-i.po
tag 509372 pending thanks On Sunday 21 December 2008, Samuel Thibault wrote: There is a typo in the japanese translation, here is a patch. Applied. Thanks. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#509372: typo in installation-guide/po/ja/using-d-i.po
Processing commands for cont...@bugs.debian.org: tag 509372 pending Bug#509372: typo in installation-guide/po/ja/using-d-i.po Tags were: patch Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509371: installation-guide: Installation guide accessibility sections
Samuel Thibault, le Sun 08 Mar 2009 03:16:56 +0100, a écrit : Ping? Ping timeout. Ping? Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509371: installation-guide: Installation guide accessibility sections
Hi Samuel,
On Sunday 21 December 2008, Samuel Thibault wrote:
Here is a patch that adds to installation-guide two accessibility
sections: in the supported hardware section, provide urls to lists
of supported braille displays and speech syntheses, and in the boot
section, document the boot parameters needed to enable accessibility
features.
Sorry for not replying to this sooner. It was on my ToDo list for the
manual, but I tend to work on that in batches.
I'm currently planning an update of the manual for stable, and it would be
nice to include this. However, there are a few problems with the proposed
patch. If you can provide an updated version of the patch fairly shortly,
I'll try to include it in the update (even though it means additional work
for translators).
The main issue is that the installation guide is built for 11
architectures, but most of your description is only valid for 2 of them:
amd64 and i386. This is of course not acceptable.
Either you'll need to specifically limit the sections to those 2 arches
(using 'arch=x86' conditions in relevant tags), or you'll need to adjust
the descriptions where appropriate. There are various options to make text
architecture specific ('arch=' conditions in section/para tags, or the
phrase tag).
Note that for arches that do not support an accessibility option at all
(s390 comes to mind), the text should be suppressed anyway.
General spelling error: s/speech syntheses/speech synthesis/
Also, please use:
s/BRLTTY/classnamebrltty/classname/
s/Speakup/classnamespeakup/classname/
Some more specific comments below.
Index: en/hardware/accessibility.xml
===
+Debian's support for braille displays is determined by the underlying
+support found in BRLTTY. Most displays work under BRLTTY, via serial, USB
+or bluetooth. Details on supported braille devices can be found at ulink
+url=url-brltty;/ulink. Debian release; ships with BRLTTY version
+brlttyver;.
[...]
+Debian's support for hardware speech syntheses is determined by the underlying
+support found in Speakup. Speakup only supports integrated boards and external
+devices connected through Serial (no USB or serial-to-USB adapters are
Serial should not be capitalized.
Is through correct? You use via for brltty. Maybe use something like
connected to a serial port.
+supported). Details on supported hardware speech syntheses can be found at
+ulink url=url-speakup;/ulink. Debian release; ships with Speakup
version
+speakupver;.
Are the versions of brltty and speakup really important for users? Please
consider that it's something that will need to be updated and that that's
easily forgotten or skipped if that is done by someone without much personal
interest in accessibility issues.
Index: en/boot-installer/accessibility.xml
===
--- en/boot-installer/accessibility.xml (r�vision 0)
+++ en/boot-installer/accessibility.xml (r�vision 0)
@@ -0,0 +1,92 @@
+Some people may need particular support due to e.g. visual impairment. USB
s/people/users/
s/due to e.g./because of e.g. some/
+braille displays are automatically detected, but most other accessibility
+features have to be enabled by hand. On machines that support it, the boot
s/by hand/manually/ or specifically enabled ?
+menu emits a beep when it is ready to receive keystrokes. Some boot parameters
+can then be appended to enable accessibility features. Note that on most
+architectures the boot loader interprets your keyboard as a QWERTY keyboard.
+
+/para
+
+sect2titleUSB Braille Displays/title
+
+para
+
+USB braille displays should be automatically detected. A textual version of
+the installer will then be automatically selected, and support for the braille
+display will be automatically installed on the target system. You can thus
just
+press enterkey; at the boot menu. Once BRLTTY is started,
+you can choose a braille table by entering the preference menu.
Is it obvious to users how this preference menu is entered?
+/para
+
+ /sect2
+ sect2titleSerial Braille Displays/title
+
+para
+
+Serial braille displays can not safely be automatically detected
+(since that may brick some of them). You thus need to append the
+userinputbrltty=driver,port,table/userinput boot parameter to tell
The parts that need to be replaced should be tagged replaceable.
+BRLTTY which driver it should use. userinputdriver/userinput
+should be replaced by the two-letter driver core for your terminal,
s/core/code/
+see ulink url=url-brltty-driver-codes;/ulink for a list.
Please change this so that the URL itself is not displayed.
+userinputdevice/userinput should be replaced by the name of the serial
+port the display is connected to, userinputttyS0/userinput is the default.
+userinputtable/userinput is the name of the braille table to be used, see
+ulink url=url-brltty-table-codes;/ulink for a list, the english table
Bug#509371: installation-guide: Installation guide accessibility sections
On Monday 06 April 2009, Samuel Thibault wrote: Samuel Thibault, le Sun 08 Mar 2009 03:16:56 +0100, a écrit : Ping? Ping timeout. No. The timeout was at least 20 minutes after you sent this. And more probably 2 days as that would have made it a full month. ;-) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509371: installation-guide: Installation guide accessibility sections
Hello, Here is an updated patch. Frans Pop, le Mon 06 Apr 2009 02:19:15 +0200, a écrit : The main issue is that the installation guide is built for 11 architectures, but most of your description is only valid for 2 of them: amd64 and i386. I know, I have already put x86 tags on the speakup sections. Note that for arches that do not support an accessibility option at all (s390 comes to mind), the text should be suppressed anyway. I'm not sure how to do this, however: brltty is enabled only on a bunch of archs, can the arch= tag take a list of archs? General spelling error: s/speech syntheses/speech synthesis/ Well, I actually wanted to use the plural form. +supported). Details on supported hardware speech syntheses can be found at +ulink url=url-speakup;/ulink. Debian release; ships with Speakup version +speakupver;. Are the versions of brltty and speakup really important for users? So as to know which drivers are available, yes. Please consider that it's something that will need to be updated and that that's easily forgotten or skipped if that is done by someone without much personal interest in accessibility issues. I know. + Once BRLTTY is started, +you can choose a braille table by entering the preference menu. Is it obvious to users how this preference menu is entered? Unfortunately, no. I have several times asked upstream for a documentation that would explain for each device how to enter the preference menu, without success. That's the best we can document here. Samuel Index: build/entities/urls.ent === --- build/entities/urls.ent (révision 58149) +++ build/entities/urls.ent (copie de travail) @@ -202,7 +202,14 @@ !ENTITY url-simtel ftp://ftp.simtel.net/pub/simtelnet/msdos/; +!ENTITY url-brltty http://www.mielke.cc/brltty/; +!ENTITY url-brltty-driver-codes http://www.mielke.cc/brltty/doc/Manual-BRLTTY/English/BRLTTY-11.html; +!ENTITY url-brltty-table-codes http://www.mielke.cc/brltty/doc/Manual-BRLTTY/English/BRLTTY-6.html; +!ENTITY url-speakup http://www.linux-speakup.org/; +!ENTITY url-speakup-driver-codes http://www.linux-speakup.org/spkguide.txt; + + !-- ** m68k links -- !-- urls that I need to absorb or point to: Index: build/entities/common.ent === --- build/entities/common.ent (révision 58149) +++ build/entities/common.ent (copie de travail) @@ -147,6 +147,12 @@ !-- version of X11 shipping with the current release -- !ENTITY x11ver 7.3 +!-- version of BRLTTY shipping with the current release -- +!ENTITY brlttyver 3.10 + +!-- version of Speakup shipping with the current release -- +!ENTITY speakupver 3.0.3 + !-- an example of adding another image to lilo.conf, cf en/post-install.sgml etc. -- !ENTITY additional-lilo-image Index: build/templates/docstruct.ent === --- build/templates/docstruct.ent (révision 58149) +++ build/templates/docstruct.ent (copie de travail) @@ -29,6 +29,7 @@ !ENTITY supported-sparc.xml SYSTEM ##SRCPATH##/hardware/supported/sparc.xml !ENTITY network-cards.xmlSYSTEM ##SRCPATH##/hardware/network-cards.xml !ENTITY supported-peripherals.xmlSYSTEM ##SRCPATH##/hardware/supported-peripherals.xml + !ENTITY accessibility-hardware.xml SYSTEM ##SRCPATH##/hardware/accessibility.xml !ENTITY buying-hardware.xml SYSTEM ##SRCPATH##/hardware/buying-hardware.xml !ENTITY installation-media.xml SYSTEM ##SRCPATH##/hardware/installation-media.xml !ENTITY memory-disk-requirements.xml SYSTEM ##SRCPATH##/hardware/memory-disk-requirements.xml @@ -94,6 +95,7 @@ !ENTITY boot-installer-s390.xml SYSTEM ##SRCPATH##/boot-installer/s390.xml !ENTITY boot-installer-sparc.xmlSYSTEM ##SRCPATH##/boot-installer/sparc.xml !ENTITY boot-installer-parameters.xml SYSTEM ##SRCPATH##/boot-installer/parameters.xml + !ENTITY boot-installer-accessibility.xml SYSTEM ##SRCPATH##/boot-installer/accessibility.xml !ENTITY boot-installer-trouble.xml SYSTEM ##SRCPATH##/boot-installer/trouble.xml !ENTITY using-d-i.xml SYSTEM ##SRCPATH##/using-d-i/using-d-i.xml Index: en/hardware/hardware-supported.xml === --- en/hardware/hardware-supported.xml (révision 58149) +++ en/hardware/hardware-supported.xml (copie de travail) @@ -399,6 +399,7 @@ /sect2 network-cards.xml; +accessibility-hardware.xml; supported-peripherals.xml; /sect1 Index: en/hardware/accessibility.xml === --- en/hardware/accessibility.xml (révision 0) +++ en/hardware/accessibility.xml (révision 0) @@ -0,0 +1,31 @@ +!-- retain these comments for translator revision
Bug#509371: installation-guide: Installation guide accessibility sections
On Monday 06 April 2009, Samuel Thibault wrote: Here is an updated patch. Thanks. Frans Pop, le Mon 06 Apr 2009 02:19:15 +0200, a écrit : Note that for arches that do not support an accessibility option at all (s390 comes to mind), the text should be suppressed anyway. I'm not sure how to do this, however: brltty is enabled only on a bunch of archs, can the arch= tag take a list of archs? Yes. E.g. 'arch=x86,alpha,hppa' General spelling error: s/speech syntheses/speech synthesis/ Well, I actually wanted to use the plural form. Why? IMO that's incorrect English in this context. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509371: installation-guide: Installation guide accessibility sections
Frans Pop, le Mon 06 Apr 2009 03:04:59 +0200, a écrit : General spelling error: s/speech syntheses/speech synthesis/ Well, I actually wanted to use the plural form. Why? IMO that's incorrect English in this context. Mmm, maybe I need to use speech synthesis devices then? Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Complete draft of the March 16th and 30th meetings minutes
Hello Frans, On Sun, Apr 5, 2009 at 4:01 PM, Frans Pop elen...@planet.nl wrote: On Sunday 05 April 2009, Christian Perrier wrote: Similarly, the installation guide could be uploaded more often, of course without translation freeze. That would help better spotting issues, errors or missing parts, hopefully. Speaking as the person who has done 90% of the work on the manual and done _all_ of its releases as a separate package: this is total nonsense. Anybody who thinks this has never seriously looked at how the manual is currently written, translated, built, distributed and used. It would be nice if you could clarify why do you believe it is nonsense. This makes easier for we all to be at same page. As you can see on the meeting minutes nobody has objected to it so would be nice if you could elaborate it a bit more to allow us (the whole team) to be aware of what you think. BTW, I still do consider myself to be the RM for the manual and would be very unhappy with anybody uploading it without at the very least talking to me first. Nobody proposed to upload it blindly; and obviously you'd be consulted before doing it. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509371: installation-guide: Installation guide accessibility sections
On Monday 06 April 2009, Samuel Thibault wrote: Frans Pop, le Mon 06 Apr 2009 03:04:59 +0200, a écrit : General spelling error: s/speech syntheses/speech synthesis/ Well, I actually wanted to use the plural form. Why? IMO that's incorrect English in this context. Mmm, maybe I need to use speech synthesis devices then? Yep. Speech synthesis is a functionality (singular) that can be provided by different (types of) devices. A speech synthesis device would be something like a speech synthesizer (which could be plural), but I doubt that's a common term. But when it comes to e.g. a section header, you can probably just use Speech synthesis (if it e.g. describes the availability of the functionality rather than its implementation in specific devices). -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509371: installation-guide: Installation guide accessibility sections
Frans Pop, le Mon 06 Apr 2009 03:28:26 +0200, a écrit : On Monday 06 April 2009, Samuel Thibault wrote: Frans Pop, le Mon 06 Apr 2009 03:04:59 +0200, a écrit : General spelling error: s/speech syntheses/speech synthesis/ Well, I actually wanted to use the plural form. Why? IMO that's incorrect English in this context. Mmm, maybe I need to use speech synthesis devices then? Yep. Speech synthesis is a functionality (singular) Ok. In french that would refer to the device as well. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509371: installation-guide: Installation guide accessibility sections
Frans Pop, le Mon 06 Apr 2009 03:04:59 +0200, a écrit : Frans Pop, le Mon 06 Apr 2009 02:19:15 +0200, a écrit : Note that for arches that do not support an accessibility option at all (s390 comes to mind), the text should be suppressed anyway. I'm not sure how to do this, however: brltty is enabled only on a bunch of archs, can the arch= tag take a list of archs? Yes. E.g. 'arch=x86,alpha,hppa' I can't make it work. the parser wants quotes, and with quotes it does not interpret the commas. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509371: installation-guide: Installation guide accessibility sections
On Monday 06 April 2009, Samuel Thibault wrote: Frans Pop, le Mon 06 Apr 2009 03:04:59 +0200, a écrit : Frans Pop, le Mon 06 Apr 2009 02:19:15 +0200, a écrit : Note that for arches that do not support an accessibility option at all (s390 comes to mind), the text should be suppressed anyway. I'm not sure how to do this, however: brltty is enabled only on a bunch of archs, can the arch= tag take a list of archs? Yes. E.g. 'arch=x86,alpha,hppa' I can't make it work. the parser wants quotes, and with quotes it does not interpret the commas. Oops, sorry. The separator is ; instead of ,. (I don't do this that often either; grep in existing docs is your friend.) Note that there are also a few not-arch tags (see archspec= in ./build/arch-options/*). Especially useful are not-x86 (if you have one text for x86 and one for all other arches) and not-s390 (any arch but s390). A list of arches in arch= is always OR. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509371: installation-guide: Installation guide accessibility sections
On Monday 06 April 2009, Frans Pop wrote: Yes. E.g. 'arch=x86,alpha,hppa' I can't make it work. the parser wants quotes, and with quotes it does not interpret the commas. And, yes, quotes are required. So: arch=x86;alpha;hppa -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509371: installation-guide: Installation guide accessibility sections
Frans Pop, le Mon 06 Apr 2009 03:49:54 +0200, a écrit : Oops, sorry. The separator is ; instead of ,. OK. (I don't do this that often either; grep in existing docs is your friend.) Yes, it doesn't work very well in the installation guide, but it does in the release notes indeed. Here is an updated patch. I had to explicitely list architectures however as I couldn't find a way to express all archs but this list. Samuel Index: build/entities/urls.ent === --- build/entities/urls.ent (révision 58149) +++ build/entities/urls.ent (copie de travail) @@ -202,7 +202,14 @@ !ENTITY url-simtel ftp://ftp.simtel.net/pub/simtelnet/msdos/; +!ENTITY url-brltty http://www.mielke.cc/brltty/; +!ENTITY url-brltty-driver-codes http://www.mielke.cc/brltty/doc/Manual-BRLTTY/English/BRLTTY-11.html; +!ENTITY url-brltty-table-codes http://www.mielke.cc/brltty/doc/Manual-BRLTTY/English/BRLTTY-6.html; +!ENTITY url-speakup http://www.linux-speakup.org/; +!ENTITY url-speakup-driver-codes http://www.linux-speakup.org/spkguide.txt; + + !-- ** m68k links -- !-- urls that I need to absorb or point to: Index: build/entities/common.ent === --- build/entities/common.ent (révision 58149) +++ build/entities/common.ent (copie de travail) @@ -147,6 +147,12 @@ !-- version of X11 shipping with the current release -- !ENTITY x11ver 7.3 +!-- version of BRLTTY shipping with the current release -- +!ENTITY brlttyver 3.10 + +!-- version of Speakup shipping with the current release -- +!ENTITY speakupver 3.0.3 + !-- an example of adding another image to lilo.conf, cf en/post-install.sgml etc. -- !ENTITY additional-lilo-image Index: build/templates/docstruct.ent === --- build/templates/docstruct.ent (révision 58149) +++ build/templates/docstruct.ent (copie de travail) @@ -29,6 +29,7 @@ !ENTITY supported-sparc.xml SYSTEM ##SRCPATH##/hardware/supported/sparc.xml !ENTITY network-cards.xmlSYSTEM ##SRCPATH##/hardware/network-cards.xml !ENTITY supported-peripherals.xmlSYSTEM ##SRCPATH##/hardware/supported-peripherals.xml + !ENTITY accessibility-hardware.xml SYSTEM ##SRCPATH##/hardware/accessibility.xml !ENTITY buying-hardware.xml SYSTEM ##SRCPATH##/hardware/buying-hardware.xml !ENTITY installation-media.xml SYSTEM ##SRCPATH##/hardware/installation-media.xml !ENTITY memory-disk-requirements.xml SYSTEM ##SRCPATH##/hardware/memory-disk-requirements.xml @@ -94,6 +95,7 @@ !ENTITY boot-installer-s390.xml SYSTEM ##SRCPATH##/boot-installer/s390.xml !ENTITY boot-installer-sparc.xmlSYSTEM ##SRCPATH##/boot-installer/sparc.xml !ENTITY boot-installer-parameters.xml SYSTEM ##SRCPATH##/boot-installer/parameters.xml + !ENTITY boot-installer-accessibility.xml SYSTEM ##SRCPATH##/boot-installer/accessibility.xml !ENTITY boot-installer-trouble.xml SYSTEM ##SRCPATH##/boot-installer/trouble.xml !ENTITY using-d-i.xml SYSTEM ##SRCPATH##/using-d-i/using-d-i.xml Index: en/hardware/hardware-supported.xml === --- en/hardware/hardware-supported.xml (révision 58149) +++ en/hardware/hardware-supported.xml (copie de travail) @@ -399,6 +399,7 @@ /sect2 network-cards.xml; +accessibility-hardware.xml; supported-peripherals.xml; /sect1 Index: en/hardware/accessibility.xml === --- en/hardware/accessibility.xml (révision 0) +++ en/hardware/accessibility.xml (révision 0) @@ -0,0 +1,32 @@ +!-- retain these comments for translator revision tracking -- +!-- $Id: accessibility-hardware.xml $ -- + + sect2 id=braille-displays arch=alpha;ia64;powerpc;x86 + titleBraille Displays/title +para + +Debian's support for braille displays is determined by the underlying +support found in classnamebrltty/classname. Most displays +work under classnamebrltty/classname, via serial, USB or +bluetooth. Details on supported braille devices can be found on the ulink +url=url-brltty;classnamebrltty/classname website/ulink. Debian +release; ships with classnamebrltty/classname version brlttyver;. + +/para + /sect2 + + sect2 id=hardware-speech-synthesis arch=x86 + titleHardware Speech Syntheses/title +para + +Debian's support for hardware speech synthesis devices is determined +by the underlying support found in classnamespeakup/classname. +classnamespeakup/classname only supports integrated boards and external +devices connected to a serial port (no USB or serial-to-USB adapters are +supported). Details on supported hardware speech synthesis devices can +be found on the ulink url=url-speakup;classnamespeakup/classname +website/ulink. Debian release; ships with
Re: Complete draft of the March 16th and 30th meetings minutes
On Monday 06 April 2009, Otavio Salvador wrote: It would be nice if you could clarify why do you believe it is nonsense. No thanks. I see no reason why _I_ should make that effort. As you seem to think that a change is needed and would improve things, it would be nice if you could explain, in some detail, what is currently lacking and how extra uploads would improve things. And it would be extra nice if you could show in that explanation that you actually understand (or at least have tried to understand) how the current setup works. As you can see on the meeting minutes nobody has objected to it... I think that's primarily because nobody had an opinion on it as so far nobody has ever shown any real and sustained interest in helping out with the manual [1]. So TBH I'm not very impressed by that argument. As soon as someone steps up and actually commits to helping out with maintenance of and RM for the manual (which is a fairly serious amount of work BTW), I'll be happy to explain how and why I do things as I currently do them [2]. Cheers, FJP [1] Yes, faw does the daily builds, but the original intention was that he'd take over RM, which never happened (which is fine). And yes, Colin is very good at providing/committing patches when he makes functional changes in D-I, but that's not the same as what we're talking about here. [2] Just as I did, in great detail, when faw took over the daily builds. See mailing list archives. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519508: installation-guide: Section 5.1.3 Booting from Linux Using LILO or GRUB assumes Linux is on hd0, 0
Le April 5, 2009 06:59:43 pm Frans Pop, vous avez écrit : tags 519508 pending thanks On Friday 13 March 2009, Filipus Klutiero wrote: In section 5.1.3, if using GRUB, the procedure says to add lines kernel (hd0,0)/boot/newinstall/vmlinuz initrd (hd0,0)/boot/newinstall/initrd.gz This will of course only work if the files were copied to (hd0,0)/boot/newinstall/. Which is exactly what's suggested in section 4.4 to which 5.1.3 refers. I see the path suggested in 4.4, but nothing about the partition. I'd suggest The procedure for GRUB is quite similar. Locate your menu.lst in the /boot/grub/ directory (sometimes in the /boot/boot/grub/), add an entry for the installer and reboot. The entry can be defined by the following lines if the installer is in /boot/newinstall/ on the first partition of the first hard drive: BTW, I have no idea what the value of ramdisk_size refers to in Note that the value of the ramdisk_size may need to be adjusted for the size of the initrd image. (just below). Removed. That's a remnant from the 2.4 and early 2.6 kernel era. And another BTW, it would be more generic to talk about ISO images in the third paragraph, since the iso can also be a DVD image. I've added a mention of DVD. Cheers, FJP Thanks much. Cheers -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
[D-I Manual] Build log for en (05 Apr 2009)
A build of the Debian Installer Manual was triggered by an update to SVN.
There were no errors during the build process.
The new version of the manual has been uploaded successfully.
A log of the build is available at:
- http://d-i.alioth.debian.org/manual/logs/en.log
===
It is possible to use RSS to track changes to the manual.
For more information, see:
http://d-i.alioth.debian.org/manual/translators.html
===
Note: PDF output is not yet supported for some languages; help
with this would be appreciated.
===
If you have any questions about the build or this message, feel
free to contact me at faw AT funlabs DOT org.
===
Updated files ('svn up')
Uen/appendix/chroot-install.xml
Uen/appendix/files.xml
Uen/appendix/preseed.xml
Uen/using-d-i/modules/pkgsel.xml
Uen/boot-installer/x86.xml
Updated to revision 58149.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Complete draft of the March 16th and 30th meetings minutes
Frans Pop wrote: On Monday 06 April 2009, Otavio Salvador wrote: It would be nice if you could clarify why do you believe it is nonsense. No thanks. I see no reason why _I_ should make that effort. Please stop that hostility. Luk -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Complete draft of the March 16th and 30th meetings minutes
On Monday 06 April 2009, Luk Claes wrote: Frans Pop wrote: On Monday 06 April 2009, Otavio Salvador wrote: It would be nice if you could clarify why do you believe it is nonsense. No thanks. I see no reason why _I_ should make that effort. Please stop that hostility. What hostility? Isn't it normal that the person proposing changes should provide argumentation for those changes before the person doing all the work defends his current methods? All I've seen so far is: 22:44 otavio - we could upload installer manual too to give more up to date docs 22:45 otavio Even if installer manual is not translated, this can bring up more attenting to what is done 22:45 otavio and what is míssing 22:45 bubulle I think it's OK to upload the d-i manual without the l10n during the development cycle This is literally *all* that was said about the installation guide. Those really are no more than very vague statements without any reasoning or backing in facts. To me it's in no way clear how _any_ of the three goals listed there would be served by more frequent uploads or skipping calls for translation updates before uploads. To me it mostly shows that neither Otavio nor Christian has any real idea of what they're talking about. I therefore think it's up to them to explain their reasoning. And really, it would help if people at least did some minimal research into how and why things are before suggesting random changes. And yes, asking _is_ allowed. But preferably in a neutral way _before_ implying that the current way things are done is incorrect or at least suboptimal. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
