Re: D-i beta1
2012/7/2 Christian PERRIER bubu...@debian.org: Quoting Samuel Thibault (sthiba...@debian.org): Hello, It'd be good to migrate to testing for b1 also espeakup (just translations) and brltty (description fixup, and d-i udev hardware list update). The same stands for eject. It does not only have translation updates, though, but also: [ Frank Lichtenheld ] * Declare Multi-Arch: foreign. Requested by Helmut Grohne. Closes: #676780 * Use dpkg-buildflags for hand-built dmcrypt-get-device, too. * Use hardening=+all * Added build dependency on dpkg-dev (= 1.16.1~) for the changes above * Bump Standards-Version to 3.9.3 (no changes) CC'ing Frank but I doubt he'd object. No objections from me, I think it would be good to migrate that to testing. Gruesse, -- Frank Lichtenheld dj...@debian.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOSaayUr0O1r-k2=prldshsde0cncluqpytr_abpdquzvw+...@mail.gmail.com
Please unblock eject
Hi. Please let migrate eject/2.1.5+deb1+cvs20081104-6 to testing. Changelog: * Only try to open the device read/write if not root. (Partly addresses #522859) * Bump Standards-Version to 3.8.1 (no changes) * Program translations: - Swedish updated. Closes: #517512 Gruesse, -- Frank Lichtenheld dj...@debian.org www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Please unblock eject
Hi. Please allow eject into testing. It is blocked because of its udeb. Gruesse, -- Frank Lichtenheld dj...@debian.org www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Please unblock eject/2.1.5+deb1-1
Hi.
Please allow eject into testing. It only contains a translation update
and some very minor fixes, but due to me moving some files around in
the .orig.tar.gz the debdiff is very huge.
I realize that me finally fixing the upstream tarball to make live of
translators easier coinsided badly with the freeze, so if wanted I can
upload only the debconf translation update to lenny-proposed-updates
instead if wanted.
Anyway, here is a debdiff *without* the effects of the repacking:
diff -Nru eject-2.1.5/debian/changelog eject-2.1.5+deb1/debian/changelog
--- eject-2.1.5/debian/changelog2008-07-31 18:39:25.0 +0200
+++ eject-2.1.5+deb1/debian/changelog 2008-07-31 18:39:26.0 +0200
@@ -1,3 +1,14 @@
+eject (2.1.5+deb1-1) unstable; urgency=low
+
+ * Create new upstream tar ball so that we can get rid of
+these strange named .po files. Closes: #336792, #336810
+ * New git repository online, add Vcs-* fields.
+ * Add Homepage field.
+ * Debconf translations:
+- Lithuanian added. Closes: #490779
+
+ -- Frank Lichtenheld [EMAIL PROTECTED] Sun, 20 Jul 2008 23:42:07 +0200
+
eject (2.1.5-10) unstable; urgency=medium
* Debconf translations:
diff -Nru eject-2.1.5/debian/control eject-2.1.5+deb1/debian/control
--- eject-2.1.5/debian/control 2008-07-31 18:39:25.0 +0200
+++ eject-2.1.5+deb1/debian/control 2008-07-31 18:39:26.0 +0200
@@ -4,6 +4,9 @@
Build-Depends: gettext, debhelper (= 6.0.7), dpkg-dev (= 1.13.2),
libdevmapper-dev [!kfreebsd-i386 !kfreebsd-amd64]
Maintainer: Frank Lichtenheld [EMAIL PROTECTED]
Standards-Version: 3.8.0
+Vcs-Git: git://git.debian.org/git/collab-maint/eject.git
+Vcs-Browser: http://git.debian.org/?p=collab-maint/eject.git
+Homepage: http://www.pobox.com/~tranter/eject.html
Package: eject
Architecture: any
diff -Nru eject-2.1.5/debian/po/lt.po eject-2.1.5+deb1/debian/po/lt.po
--- eject-2.1.5/debian/po/lt.po 1970-01-01 01:00:00.0 +0100
+++ eject-2.1.5+deb1/debian/po/lt.po2008-07-31 18:39:26.0 +0200
@@ -0,0 +1,23 @@
+# Lithuanian messages for eject package.
+# Copyright (C) 2003 Software in the Public Interest, Inc.
+# This file is distributed under the same license as package eject.
+# Kęstutis Biliūnas [EMAIL PROTECTED] 2008.
+
+msgid
+msgstr
+Project-Id-Version: eject\n
+Report-Msgid-Bugs-To: \n
+POT-Creation-Date: 2004-04-11 23:40+0200\n
+PO-Revision-Date: 2008-07-14 12:20+0300\n
+Last-Translator: Kęstutis Biliūnas [EMAIL PROTECTED]\n
+Language-Team: Lithuanian [EMAIL PROTECTED]\n
+MIME-Version: 1.0\n
+Content-Type: text/plain; charset=UTF-8\n
+Content-Transfer-Encoding: 8bit
+
+#. Type: text
+#. description
+#: ../eject-udeb.templates:3
+msgid Eject a CD from the drive
+msgstr Išimti diską iš CD įrenginio
+
diff -Nru eject-2.1.5/eject.c eject-2.1.5+deb1/eject.c
--- eject-2.1.5/eject.c 2008-07-31 18:39:25.0 +0200
+++ eject-2.1.5+deb1/eject.c2008-07-31 18:39:26.0 +0200
@@ -665,7 +665,7 @@
printf(\n);
#else
- fprintf(stderr, _(%s: CD-ROM select speed command not supported by
thiskernel\n), programName);
+ fprintf(stderr, _(%s: CD-ROM select speed command not supported by
this kernel\n), programName);
#endif
}
@@ -1058,7 +1058,7 @@
const char* dev = GetDevmapperDevice (s1);
if (dev) {
if (v_option)
-printf(_(%s: %s is encrypted on real device
%s\n),
+printf(_(%s: %s is encrypted on real device
%s\n),
programName, s1, dev);
} else
dev = s1;
@@ -1131,10 +1131,10 @@
const char* dev = GetDevmapperDevice (name);
if (dev) {
if (v_option)
-printf(_(%s: %s is encrypted on real device %s\n),
+printf(_(%s: %s is encrypted on real device %s\n),
programName, name, dev);
name = dev;
-}
+}
for (i = 0; partitionDevice[i] != 0; i++) {
/* look for ^/dev/foo[a-z]([0-9]?[0-9])?$, e.g. /dev/hda1 */
And a diffstat for the full debdiff:
debian/changelog | 11 +
debian/control|3
debian/po/lt.po | 23 ++
eject.c |8
po/Makefile | 22 --
po/cs.po | 436
po/cs_CZ.po | 431
po/de.po | 445 +
po/de_DE.po | 516
po/eject.pot | 91 -
po/es.po | 515
po/es_ES.po | 510
po/fr.po | 520 +
po/fr_FR.po | 515
Please unblock eject
eject 2.1.5-10 is now old enough, it only waits on the upload of the alpha binaries. Please allow it to go to testing. Changelog: eject (2.1.5-10) unstable; urgency=medium * Debconf translations: - Belarusian added. Closes: #488624 - Slovak added. Closes: #488892 * Bump Standards-Version to 3.8.0. -- Frank Lichtenheld [EMAIL PROTECTED] Mon, 07 Jul 2008 00:24:13 +0200 eject (2.1.5-9) unstable; urgency=low * Program translations: - Turkish updated. Closes: #482406 * Debconf translations: - Turkish added. Closes: #482715 - Esperanto added. Closes: #478957 (this was added in -8 as a program translation, but is really a debconf translation) -- Frank Lichtenheld [EMAIL PROTECTED] Wed, 28 May 2008 22:09:22 +0200 Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Unblock atari-fdisk
atari-fdisk 0.7.1-5.4 should probably be unblocked.
The NMU was very trivial and the udeb that is the reason for the block
is only present on the non-release arch m68k.
Debdiff for reference:
diff -Nru atari-fdisk-0.7.1/debian/changelog atari-fdisk-0.7.1/debian/changelog
--- atari-fdisk-0.7.1/debian/changelog 2006-12-30 10:52:56.0 +0100
+++ atari-fdisk-0.7.1/debian/changelog 2008-04-16 20:08:21.0 +0200
@@ -1,3 +1,10 @@
+atari-fdisk (0.7.1-5.4) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add new archs, closes: #396326
+
+ -- Riku Voipio [EMAIL PROTECTED] Wed, 16 Apr 2008 20:55:15 +0300
+
atari-fdisk (0.7.1-5.3) unstable; urgency=high
* Non-maintainer upload.
diff -Nru atari-fdisk-0.7.1/debian/control atari-fdisk-0.7.1/debian/control
--- atari-fdisk-0.7.1/debian/control2006-10-23 20:31:45.0 +0200
+++ atari-fdisk-0.7.1/debian/control2008-04-16 20:07:58.0 +0200
@@ -24,7 +24,7 @@
atari-fdisk udeb package
Package: atari-fdisk-cross
-Architecture: alpha amd64 arm hppa hurd-i386 i386 ia64 mips mipsel powerpc
s390 sh sparc
+Architecture: alpha amd64 arm armeb armel hppa hurd-i386 i386 ia64
kfreebsd-i386 kfreebsd-amd64 mips mipsel powerpc ppc64 s390 sh sh4 sparc
Section: otherosfs
Priority: extra
Depends: ${shlibs:Depends}
Gruesse,
--
Frank Lichtenheld [EMAIL PROTECTED]
www: http://www.djpig.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Transition to parted 1.8
On Mon, Jun 30, 2008 at 04:13:31PM +0200, Adeodato Simó wrote: * Otavio Salvador [Thu, 19 Jun 2008 15:40:49 -0300]: qtparted (Debian QA Group [EMAIL PROTECTED]) Done. (But since it is not in testing it is not really important anyway) Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#275565: Patch
. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488907: installation-reports: netboot installation on Powerbook G4 12, mostly successfull
: 643304 kB /proc/meminfo: LowFree: 35552 kB /proc/meminfo: SwapTotal: 1638392 kB /proc/meminfo: SwapFree: 1638392 kB /proc/meminfo: Dirty: 704 kB /proc/meminfo: Writeback: 0 kB /proc/meminfo: AnonPages:7312 kB /proc/meminfo: Mapped: 2288 kB /proc/meminfo: Slab:34116 kB /proc/meminfo: SReclaimable:26088 kB /proc/meminfo: SUnreclaim: 8028 kB /proc/meminfo: PageTables:376 kB /proc/meminfo: NFS_Unstable:0 kB /proc/meminfo: Bounce: 0 kB /proc/meminfo: CommitLimit: 1960044 kB /proc/meminfo: Committed_AS:10608 kB /proc/meminfo: VmallocTotal: 317852 kB /proc/meminfo: VmallocUsed: 58200 kB /proc/meminfo: VmallocChunk: 258372 kB /proc/bus/input/devices: I: Bus=0017 Vendor=0001 Product=0001 Version=0100 /proc/bus/input/devices: N: Name=Macintosh mouse button emulation /proc/bus/input/devices: P: Phys= /proc/bus/input/devices: S: Sysfs=/class/input/input0 /proc/bus/input/devices: U: Uniq= /proc/bus/input/devices: H: Handlers=mouse0 /proc/bus/input/devices: B: EV=7 /proc/bus/input/devices: B: KEY=7 0 0 0 0 0 0 0 0 /proc/bus/input/devices: B: REL=3 /proc/bus/input/devices: /proc/bus/input/devices: I: Bus=0017 Vendor=0001 Product=22c4 Version=0200 /proc/bus/input/devices: N: Name=ADB keyboard /proc/bus/input/devices: P: Phys=adb2:2.c4/input /proc/bus/input/devices: S: Sysfs=/class/input/input1 /proc/bus/input/devices: U: Uniq= /proc/bus/input/devices: H: Handlers=kbd /proc/bus/input/devices: B: EV=120003 /proc/bus/input/devices: B: KEY=1 0 0 0 0 0 0 0 0 0 0 feb0ffdf 3cf fffe /proc/bus/input/devices: B: LED=7 /proc/bus/input/devices: /proc/bus/input/devices: I: Bus=0017 Vendor=0001 Product=771f Version=0100 /proc/bus/input/devices: N: Name=ADB Powerbook buttons /proc/bus/input/devices: P: Phys=adb7:7.1f/input /proc/bus/input/devices: S: Sysfs=/class/input/input2 /proc/bus/input/devices: U: Uniq= /proc/bus/input/devices: H: Handlers=kbd /proc/bus/input/devices: B: EV=13 /proc/bus/input/devices: B: KEY=7b 0 2 0 e 0 0 0 /proc/bus/input/devices: /proc/bus/input/devices: I: Bus=0017 Vendor=0001 Product=3301 Version=0100 /proc/bus/input/devices: N: Name=ADB mouse /proc/bus/input/devices: P: Phys=adb3:3.01/input /proc/bus/input/devices: S: Sysfs=/class/input/input3 /proc/bus/input/devices: U: Uniq= /proc/bus/input/devices: H: Handlers=mouse1 /proc/bus/input/devices: B: EV=7 /proc/bus/input/devices: B: KEY=7 0 0 0 0 0 0 0 0 /proc/bus/input/devices: B: REL=3 /proc/bus/input/devices: /proc/bus/input/devices: I: Bus=0019 Vendor=0001 Product=0001 Version=0100 /proc/bus/input/devices: N: Name=PMU /proc/bus/input/devices: P: Phys= /proc/bus/input/devices: S: Sysfs=/class/input/input4 /proc/bus/input/devices: U: Uniq= /proc/bus/input/devices: H: Handlers=kbd /proc/bus/input/devices: B: EV=23 /proc/bus/input/devices: B: KEY=10 0 0 0 /proc/bus/input/devices: B: SW=1 /proc/bus/input/devices: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.24-1-powerpc Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Accepted eject 2.1.4-4 (source powerpc)
On Wed, Apr 11, 2007 at 08:13:02AM +0200, Christian Perrier wrote: * Multiply installer-menu-item number by 100 as requested by Joey Hess (960 - 96000). (Closes: #418607) Hmmm, really? Was the menu item number 960? If so, that's an error, it should have been 96 and the new number should be 9600. Otherwise, that's just an error in the changelog which is harmless. No, it was 960 (since it should appear at the very end of the list) I assumed someone checked the previous values before filing the bugs... Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404261: rescue-mode: should support encrypted disks
Package: rescue-mode Version: 1.7 Severity: wishlist It would be really cool if rescue-mode would support encrypted disks. A first step would be to go through the list of partitions found and determine wether they are actually encrypted. Ideally it would then offer the user to open them. If I can be of any more assistance don't hesitate to ask :) Gruesse, Frank Lichtenheld -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-powerpc Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Updating the install manual info at the ddp web pages
Hi. The information at http://www.debian.org/doc/user-manuals#install seems rather outdated. Perhaps someone could prepare an updated entry? (This hasn't to be a direct patch for the WML, the text and links would suffice) Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I Manual on official Debian website [long]
On Tue, Dec 28, 2004 at 03:07:09PM +0100, Frans Pop wrote:
The scripts that support creating pdf and text files have now been
implemented in the Sarge branch as well as in trunk.
How are things going on your end WRT a decision on where to build the
manual and what directory structure to use?
The where is still an unsolved question...
On the directory structure I have researched how difficult it would
be to adjust the filenames and links. Turns out it is not difficult at
all. Proof-of-concept patch against the sarge branch:
Index: install.en.xml
===
--- install.en.xml (revision 24570)
+++ install.en.xml (working copy)
@@ -23,7 +23,7 @@
!-- retain these comments for translator revision tracking --
!-- $Id$ --
-book
+book lang=en
bookinfo.xml;
preface.xml;
Index: build.sh
===
--- build.sh(revision 24570)
+++ build.sh(working copy)
@@ -29,11 +29,13 @@
echo Architecture: $arch
if [ -n $noarchdir ]; then
destsuffix=$lang
+ elif [ -n $webbuild ]; then
+ destsuffix=$arch
else
destsuffix=${lang}.${arch}
fi
./buildone.sh $arch $lang
- mkdir $destination/$destsuffix
+ mkdir -p $destination/$destsuffix
mv *.html $destination/$destsuffix
./clear.sh
done
Index: style-html.xsl
===
--- style-html.xsl (revision 24570)
+++ style-html.xsl (working copy)
@@ -12,6 +12,7 @@
!-- Any html-specific parameters follow --
!-- You may find some in /etc/sgml/docbook-xsl/html/param.xsl --
+xsl:param name=html.ext select=concat('.',/book/@lang,'.html')/
!-- Where to put resulting html. Don't forget trailing slash! --
xsl:param name=base.dir select='./'/
@@ -34,4 +35,4 @@
!-- Do we want fancy icons instead of Next, Prev, Up, Home? --
xsl:param name=navig.graphics0/xsl:param
-/xsl:stylesheet
\ No newline at end of file
+/xsl:stylesheet
I would still prefer we go for this approach.
Gruesse,
--
Frank Lichtenheld [EMAIL PROTECTED]
www: http://www.djpig.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I Manual on official Debian website [long]
On Sun, Dec 19, 2004 at 04:13:41PM +0100, Frans Pop wrote: On Thursday 16 December 2004 16:06, Frank Lichtenheld wrote: I was thinking of changes that are relevant for Sarge as well. Everybody agrees that the manual for Sarge is far from optimal. But then these changes should happen in the sarge branch, too. Or you have to create a sarge-webpages branch if you want to protect the version used in the images from too many changes. Of course. The question was just: do we want to republish on the web when changes in the Sarge branch are made (doesn't have to be for every little dotted i or crossed t of course). Definetly yes. If someone would make a list which packages/versions of packages the installmanual needs that aren't available in woody, this would be appreciated. [...] In the end I was able to build all formats by using some intermediate files build using Sarge. Thanks for the work. I have to say, the backport solution doesn't look very feasible to me... Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I Manual on official Debian website [long]
On Thu, Dec 16, 2004 at 09:27:54AM +0100, Frans Pop wrote: On Thursday 16 December 2004 01:43, Frank Lichtenheld wrote: No, this isn't correct. The current structure is 1.) releases/stable/releasenotes.lang.html 2.) releases/stable/installmanual.lang.html 3.) releases/stable/arch/*.lang.* 4.) releases/stable/arch/release-notes.lang.* 5.) releases/stable/arch/release-notes/*.lang.html Hmm. I miss http://www.debian.org/releases/stable/i386/install (same for other arches) in your list; these are linked from the list at the top of http://www.debian.org/releases/stable/installmanual and seems to be the URL where content negotiation takes place. I guess these URLs contain index.lang.html links to the releases/stable/arch/install.lang.html files. please note that /releases/stable/i386/install as an URL is mapped by apache to a file releases/stable/i386/install.lang.html. So there are no explicit links for that, apache chooses the file. install.lang.html is covered by point 3). I t is just the first page of the installation manual. index.lang.html seems to be a page for the CD version. AFAICS it is not build from the installmanual's sources (It seems to be HTML written by hand ;) and is not linked from anywhere in the webpage. Note however that currently the build system in that branch does not allow building pdf or txt files. How can we work around this? merge the change to the branch? I see no way around this. This will have to be OK'ed by Joey Hess. We should definetly try this IMO and I'm willing to help if there is anything I can do there. Is this a risk for the image building? Otherwise I couldn't see a reason not to do it. - - There will probably be major changes to the manual (restructuring) after Sarge is released that are relevant. Do we want to rebuild the manual after release for the website? We could think about doing that and placing the result in the etch/ directory. I was thinking of changes that are relevant for Sarge as well. Everybody agrees that the manual for Sarge is far from optimal. But then these changes should happen in the sarge branch, too. Or you have to create a sarge-webpages branch if you want to protect the version used in the images from too many changes. Your suggestion would work for any changes in the manual that relate to post-Sarge changes in the functionality of d-i. Indeed. - - Should rebuilds (if we want them) be triggered automatically or started manually? What are the implications of this for translations of the website? My preference would be manually because that would make it possible to check the status of translations first and allow to keep the build scripts simpler. How many people will be able to trigger the build? Hopefully enough... Depends on where the building process would be hosted and how complex we make the script. I would suggest keeping the script as simple as possible and add a README with instructions for publishing the results. If we decide to build manually I could do the builds at home and make a tarbal available to d-www people. That should work to start with. Ok, this will be left for the webmasters (and d-admins) to decide :/ We should really try to find a Debian controlled machine to build the thing on (which would also allow to rsync it instead of getting a tarball). Hmm, perhaps build it in a chroot? If someone would make a list which packages/versions of packages the installmanual needs that aren't available in woody, this would be appreciated. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I Manual on official Debian website [long]
On Wed, Dec 15, 2004 at 08:21:52PM +0100, Frans Pop wrote: On Monday 13 December 2004 13:10, Frank Lichtenheld wrote: 2) The current installmanual for woody uses the layout arch/filename.lang.ext, the sarge installmanual uses lang.arch/filename.ext. I think we would prefer the old layout (which would require some changes in build.sh, AFAICS). As we also link to the final location on the website from the manual, it would be nice to know what the URL structure will be. AFAICT, the structure for Woody seems to be: 1. www.d.o/releases/stable/ 2. www.d.o/releases/stable/releasenotes/ 3. www.d.o/releases/stable/installmanual/ 4. www.d.o/releases/stable/arch/ 5. www.d.o/releases/stable/arch/install/ No, this isn't correct. The current structure is 1.) releases/stable/releasenotes.lang.html 2.) releases/stable/installmanual.lang.html 3.) releases/stable/arch/*.lang.* 4.) releases/stable/arch/release-notes.lang.* 5.) releases/stable/arch/release-notes/*.lang.html This is: 1.) Index page for release notes, build from debian-www CVS 2.) Index page for installmanual, build from debian-www CVS 3.) installmanual files 4.) releasenotes, formats txt and pdf 5.) releasenotes, format html I would suggest to create a new wrapper buildscript webbuild.sh for the website that builds the wanted languages and formats and makes sure it all ends up in the proper directory structure and creates symlinks for content negotiation (and possibly the index pages). I would also suggest the following directory structure under www.d.o/releases/sarge|testing|stable/. 1. ./ 2. ./releasenotes/ (or whatever has already been decided) 3. ./installmanual/ 4. ./installmanual/arch.lang/ 5. ./installmanual/arch/ I will respond to that another time. Will need some time to think this through. Other issues to be decided: - - Which languages to include on the website? For the CD's (and the d-i-manual packages) we've limited the languages to be included to those that were completely translated: en, es, pt_br, fr, cs and ja. At the moment de and ru are also very advanced and some other languages are partially translated. Which should be included at release time? Depends. Should be discussed with the translators, too. Should extra languages that complete later be added at that time? definetly yes - - Probably the manual for the website should be built from the sarge branch of the SVN repository. yes Note however that currently the build system in that branch does not allow building pdf or txt files. How can we work around this? merge the change to the branch? I see no way around this. - - There will probably be major changes to the manual (restructuring) after Sarge is released that are relevant. Do we want to rebuild the manual after release for the website? We could think about doing that and placing the result in the etch/ directory. - - Should rebuilds (if we want them) be triggered automatically or started manually? What are the implications of this for translations of the website? My preference would be manually because that would make it possible to check the status of translations first and allow to keep the build scripts simpler. How many people will be able to trigger the build? Hopefully enough... - - Should the index page at 3 be generated automatically or maintained manually. I would leave that one in the debian-www CVS. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I Manual on official Debian website
On Sun, Dec 12, 2004 at 08:02:24PM +0100, Frans Pop wrote: There seems to be a very old version of the Debian Installer Manual at, for example, http://www.debian.org/releases/testing/i386/. Do you happen to know anything about that? IMHO these should either be removed or updated. I will investigate this. I guess the final location, version and updates of the manual (and release notes) on the Debian website should be discussed. For the release notes, all preparations are finished, so there is nothing left to do by the webmasters. For the installation manual, there are still the same questions remaining I brought up some months ago on d-boot (I can search the mail in the archives, if you want, but it's probably unecessary): 1) AFAIK the install-manual can't be build with the tools available in woody, only on sarge (and sid, of course). So the most important question is: Can we arrange for the manual to be build on klecker or do we need to build it somewhere else and then rsync it to klecker? (klecker = www-master). Some time after the release the problem will vanish of course. 2) The current installmanual for woody uses the layout arch/filename.lang.ext, the sarge installmanual uses lang.arch/filename.ext. I think we would prefer the old layout (which would require some changes in build.sh, AFAICS). Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I Manual on official Debian website
On Mon, Dec 13, 2004 at 05:15:20AM -0800, Steve Langasek wrote: My $.02: Having filename.lang.ext is great for content negotiation, but really stinks when you're trying to have a look at a version of the manual for a language other than your browser's preferred language, because all the links get pointed back to URLs that go through content negotiation. :-) Actually the woody installmanual uses a mix. The links in the manual itself don't use content negotiation. I guess this was done to provide a initial link for all languages (e.g. http://www.debian.org/releases/woody/alpha/install) but prevent the problems you mentioned. The link issue means that a change in build.sh would not be enough to change the scheme, though. Good that you mentioned it :) Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#283949: allow generation of plain text
Package: debian-installer-manual
Severity: normal
Tags: patch
While investigating how to incorporate the install manual into
the websites I saw there is no plain text output yet. I've prepared
a little patch to allow this (xml-single html-text).
The method of using w3m -dump still has some drawbacks. The most
important one is that most of the URLs are invisible. None of the
textmode browers I tested seems to have an option to change this
behaviour, though (sadly enough, the text export of Firefox does this
one good, but has its errors, too. Beside the fact we can't use it
in batch mode ;) Still working on this.
Gruesse,
Frank Lichtenheld
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7-smp
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8
Index: buildone.sh
===
--- buildone.sh (revision 24138)
+++ buildone.sh (working copy)
@@ -20,6 +20,7 @@
stylesheet_dir=$build_path/stylesheets
stylesheet_profile=$stylesheet_dir/style-profile.xsl
stylesheet_html=$stylesheet_dir/style-html.xsl
+stylesheet_html_single=$stylesheet_dir/style-html-single.xsl
stylesheet_fo=$stylesheet_dir/style-fo.xsl
stylesheet_dsssl=$stylesheet_dir/style-print.dsl
@@ -101,6 +102,24 @@
checkresult $?
}
+create_text () {
+
+create_profiled
+
+echo Creating temporary .html file...
+
+/usr/bin/xsltproc \
+--xinclude \
+ --output $tempdir/install.${language}.html \
+$stylesheet_html_single \
+$tempdir/install.${language}.profiled.xml
+checkresult $?
+
+echo Creating .txt file...
+w3m -dump $tempdir/install.${language}.html \
+ $destination/install.${language}.txt
+}
+
create_dvi () {
# Skip this step if the .dvi file already exists
@@ -179,6 +198,7 @@
html) create_html;;
ps)create_ps;;
pdf) create_pdf;;
+txt) create_text;;
*) echo Format $format unknown or not yet supported!;;
esac
Index: build.sh
===
--- build.sh(revision 24138)
+++ build.sh(working copy)
@@ -16,6 +16,10 @@
destination=/tmp/manual
fi
+if [ -z $format ]; then
+formats=html pdf ps txt
+fi
+
[ -e $destination ] || mkdir -p $destination
if [ $official_build ]; then
@@ -32,9 +36,15 @@
else
destsuffix=${lang}.${arch}
fi
- ./buildone.sh $arch $lang html
- mkdir $destination/$destsuffix
- mv build.out/html/*.html $destination/$destsuffix
+ ./buildone.sh $arch $lang $formats
+ mkdir -p $destination/$destsuffix
+ for format in $formats; do
+ if [ $format = html ]; then
+ mv build.out/html/*.html $destination/$destsuffix
+ else
+ mv build.out/install.$lang.$format $destination/$destsuffix
+ fi
+ done
./clear.sh
done
done
Bug#283949: Acknowledgement (allow generation of plain text)
Forgot the new .xsl file. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ style-html-single.xsl Description: application/xml
Bug#283972: update information about i386 bootloader configuration
Package: debian-installer-manual Severity: normal Tags: patch I would propose to move the reference to section 8.3 from lilo-installer to os-prober, because this seems more appropriate. You might consider ignoring the other more cosmetic parts of the patch, although I think we really should stop talking about Windows 9x as probably most of the people reading this will have 2000 or XP installed by now. Index: en/using-d-i/modules/os-prober.xml === --- en/using-d-i/modules/os-prober.xml (revision 24138) +++ en/using-d-i/modules/os-prober.xml (working copy) @@ -34,4 +34,15 @@ /para/note +para arch=i386 + +If you can no longer boot into Windows (or DOS) after this step, +you'll need to use a Windows (MS-DOS) boot disk and use the +userinputfdisk /mbr/userinput command to reinstall the MS-DOS +master boot record mdash;; however, this means that you'll need to use +some other way to get back into Debian! For more information on this +please read xref linkend=reactivating-win/. + +/para + /sect3 Index: en/using-d-i/modules/i386/lilo-installer.xml === --- en/using-d-i/modules/i386/lilo-installer.xml(revision 24138) +++ en/using-d-i/modules/i386/lilo-installer.xml(working copy) @@ -19,7 +19,8 @@ Currently the LILO installation will only create menu entries for other operating systems if these can be firsttermchainloaded/firstterm. This means you may have to manually add a menu entry for operating -systems like GNU/Linux and GNU/Hurd after the installation. +systems like GNU/Linux (beside the one you just installed of course) +and GNU/Hurd after the installation. /para/note para @@ -59,8 +60,8 @@ /parapara -If you can no longer boot into Windows 9x (or DOS) after this step, -you'll need to use a Windows 9x (MS-DOS) boot disk and use the +If you can no longer boot into Windows (or DOS) after this step, +you'll need to use a Windows (MS-DOS) boot disk and use the userinputfdisk /mbr/userinput command to reinstall the MS-DOS master boot record mdash; however, this means that you'll need to use some other way to get back into Debian! For more information on this This change of course will require a rewrite of the linked reactivating-win document which is overdue anyway. I'm on it and will add it to this bug report once I'm finished. Gruesse, Frank Lichtenheld -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-k7-smp Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#283972: Acknowledgement (update information about i386 bootloader configuration)
Attached a first draft for a new reactivating-win document. Comments welcome. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ Index: build/entities/common.ent === --- build/entities/common.ent (revision 24138) +++ build/entities/common.ent (working copy) @@ -47,14 +47,6 @@ !-- As measured on a completed woody install, work space included. -- !ENTITY minimum-fs-size 110notation-megabytes; -!-- minimum total memory (RAM + swap is ok) needed, i.e., for kernel -- -!-- module config -- -!ENTITY minimum-memory-with-swap 9notation-megabytes; - -!-- minimum memory for diskless workstations (NFS root) -- -!ENTITY minimum-memory-with-nfsroot 16notation-megabytes; - - !-- number of packages, approx, in the main distribution -- !-- do: grep '^Package:' Packages | wc -l -- !-- might be fun to generate this dynamically -- @@ -77,9 +69,6 @@ !-- Number of current Debian maillists -- !ENTITY num-of-debian-maillists 160 -!-- threshold, below which, we are a low memory system -- -!ENTITY low-mem-threshold 5notation-megabytes; - !-- version of X11 shipping with the current release -- !ENTITY x11ver 4.3.0 @@ -89,21 +78,28 @@ 'image=/boot/vmlinuz.new label=new append=mcd=0x320,11 + initrd=/initrd.img read-only' -!ENTITY boot-loader-installer - phrase arch='alpha'boot loader installer/phrase - phrase arch='arm'boot loader installer/phrase - phrase arch='hppa'boot loader installer/phrase - phrase arch='i386'lilo/phrase - phrase arch='ia64'boot loader installer/phrase - phrase arch='m68k'boot loader installer/phrase - phrase arch='mips'boot loader installer/phrase - phrase arch='mipsel'boot loader installer/phrase - phrase arch='powerpc'yaboot or quik/phrase - phrase arch='sparc'boot loader installer/phrase - phrase arch='s390'boot loader installer/phrase +!ENTITY additional-lilo-other +'other=/dev/hdb1 +label=Windows' +!ENTITY additional-grub-other +'title Windows 95/98/Me +root(hd0,0) +makeactive +chainloader +1 +' + +!ENTITY additional-grub-image +'title Debian GNU/Linux, other kernel +root(hd0,1) +kernel /boot/vmlinuz.new root=/dev/hda2 ro +initrd /boot/initrd.img.new +' + + !-- prefix for files that can be downloaded -- !-- ![ %official-web-build; [ !ENTITY downloadable-file url-boot-floppies; ]] -- !ENTITY downloadable-file url-debian-installer; Index: en/post-install/reactivating-win.xml === --- en/post-install/reactivating-win.xml(revision 24138) +++ en/post-install/reactivating-win.xml(working copy) @@ -7,16 +7,96 @@ para After installing the base system and writing to the emphasisMaster Boot -Record/emphasis, you will be able to boot Linux, but probably nothing else. -This depends what you have chosen during the installation. This chapter -will describe how you can reactivate your old systems so that you can also -boot your DOS or Windows again. +Record/emphasis, you will be able to boot Linux, but perhaps nothing else, +despite the fact that the installer normally tries to detect other operating +systems. It also depends on what you have chosen during the installation. +This chapter will describe how you can reactivate your old systems so that +you can also boot your DOS or Windows again. We assume you have chosen +one of the two bootloaders available from within d-i;. If you want to +use another bootloader please refer to the related documentation. +/para + +sect2 id=reactivating-win-grub + titleBooting DOS and Windows from commandGrub/command/title + +para + +Grub is a flexible and powerful bootloader for PC systems that +is also able to boot other operating systems than Linux. +commandGrub/command is configured via the +filename/boot/grub/menu.lst/filename file. Grub reads this file +directly during boot, so there is no need to execute an update program +after every edit of it like for many other bootloaders. + /parapara -commandLILO/command is a boot manager with which you can also boot -other operating systems than Linux, which complies to PC -conventions. The boot manager is configured via +The Grub configuration file includes a list of the available systems +to boot. Each section at least contains a userinputtitle/userinput +and a userinputroot/userinput option. Grub doesn't use the name +of the Linux device file for determine the root partition of a system +but a different notation which is described in the section +filenameNaming Convention/filename in filenamegrub/filename +Texinfo manual. E.g. the first partition of your first hard drive +(independent of it is IDE or SCSI) is written as +userinput(hd0,0)/userinput, the second partition +userinput(hd0,1)/userinput, and so on. + +/para + +!-- FIXME: Naming convention example is wrong if the partitions +are logical ones
Re: Dropping 386 support
On Fri, Oct 22, 2004 at 11:34:50AM -0400, Andres Salomon wrote: On Fri, 2004-10-22 at 00:31 +0200, Frank Lichtenheld wrote: Has the current image compiled the patch in? (I haven't checked that yet) Yes, it does. If yes, there should be no problem at all to implement this solution (as long as the patch works). If no, the d-i team will have to speak Heh, that's the rumor. Can't say that I've actually tested it. :) ok, time to find out. up and say if a new kernel image could still be added before release with reasonable effort. As most 386 machines will already fail to satisfy other requirements of d-i (as RAM), it may even be acceptable only support 386 via upgrades or manual installation... I will begin next week with some upgrade tests from woody on a 386 machine and could then handle the further steps like creation of a upgrade-i386 directory with backported modutils, initrd-tools and a current kernel-image. If someone from the kernel or glibc team had access to a real 386, we might be able to make (userspace) support work. Would it be possible to get access to this machine? hmm, I can make that possible (I can probably get it connected to the internet somewhere in the university and then offer ssh access to it). What kind of access would you need? Do you need to test woody-sid upgrades or do you need a plain woody or a plain sarge? Chroots? Is ssh enough or do you need serial console, too? I will need some days to set it up. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dropping 386 support
On Sat, Oct 02, 2004 at 06:01:31PM -0400, Andres Salomon wrote: The kernel team is considering dropping 386 support (the 80386 processor, not the i386 arch) from Debian. Currently, in order to support 386, we include a 486 emulation patch (the patch can be viewed [...] Comments? Thoughts? I think the following should pretty much outline the current opinion of the release team (at least vorlon and me agreed explicetly on it): We're in favor of keeping a -386 kernel image that is compiled with the patch activated and therefor runs on real i386 machines. It should be mentioned in the release notes and in the description of the option in the kernel config that it has known security risks and that there may no fix for this available in the near or even far future. That leaves i386 users the choice whether they want to accept the risk or if they want to stay on older software (which probably has its own risks). As the patch doesn't has any affects on all other machines we think this is an acceptable solution. Has the current image compiled the patch in? (I haven't checked that yet) If yes, there should be no problem at all to implement this solution (as long as the patch works). If no, the d-i team will have to speak up and say if a new kernel image could still be added before release with reasonable effort. As most 386 machines will already fail to satisfy other requirements of d-i (as RAM), it may even be acceptable only support 386 via upgrades or manual installation... I will begin next week with some upgrade tests from woody on a 386 machine and could then handle the further steps like creation of a upgrade-i386 directory with backported modutils, initrd-tools and a current kernel-image. Any objections against this? Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#274795: file conflicts in debconf-doc cdebconf
Package: debconf-doc,cdebconf Subject: debconf-doc,cdebconf: conflicting files Severity: serious At least the following files are included in at least two packages (there may be others, only the first one found is reported): usr/share/man/man7/debconf.7.gz You may want to add conflicts to one or more of the packages or take other actions to allow the parallel installation of the packages. Please clone and reassign this report as needed to properly track the issue Gruesse, Frank Lichtenheld -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#273065: Installation report
Package: installation-reports INSTALL REPORT Debian-installer-version: daily build 20040923 (businesscard) uname -a: Linux feynman 2.6.8-1-386 #1 Sat Aug 28 13:18:58 EDT 2004 i686 GNU/Linux Date: 20040923 Method: Boot from CD, network configuration from DHCP Packages retrieved from internet Machine: Processor: AMD Athlon 64 3500+ Memory: 1 GB Root Device: SATA, Samsung SP1614C Root Size/partition table: /dev/sda1 / ext3 7GB /dev/sda2 ext3 7GB (reserved for amd64 /) /dev/sda7 /home ext3 130GB /dev/sda6 /varext3 15GB /dev/sda5 noneswap1GB /dev/hda/media/cdrom0 iso9660 ro,user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 Output of lspci and lspci -n: :00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0282 :00:00.1 Host bridge: VIA Technologies, Inc.: Unknown device 1282 :00:00.2 Host bridge: VIA Technologies, Inc.: Unknown device 2282 :00:00.3 Host bridge: VIA Technologies, Inc.: Unknown device 3282 :00:00.4 Host bridge: VIA Technologies, Inc.: Unknown device 4282 :00:00.7 Host bridge: VIA Technologies, Inc.: Unknown device 7282 :00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800 South] :00:05.0 VGA compatible controller: STMicroelectronics STG4000 [3D Prophet Kyro Series] (rev 01) :00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) :00:0e.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) :00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) :00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South] :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) :00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge lspci -n :00:00.0 0600: 1106:0282 :00:00.1 0600: 1106:1282 :00:00.2 0600: 1106:2282 :00:00.3 0600: 1106:3282 :00:00.4 0600: 1106:4282 :00:00.7 0600: 1106:7282 :00:01.0 0604: 1106:b188 :00:05.0 0300: 104a:0010 (rev 01) :00:0b.0 0200: 10ec:8169 (rev 10) :00:0e.0 0c00: 1106:3044 (rev 46) :00:0f.0 0104: 1106:3149 (rev 80) :00:0f.1 0101: 1106:0571 (rev 06) :00:10.0 0c03: 1106:3038 (rev 81) :00:10.1 0c03: 1106:3038 (rev 81) :00:10.2 0c03: 1106:3038 (rev 81) :00:10.3 0c03: 1106:3038 (rev 81) :00:10.4 0c03: 1106:3104 (rev 86) :00:11.0 0601: 1106:3227 :00:11.5 0401: 1106:3059 (rev 60) :00:18.0 0600: 1022:1100 :00:18.1 0600: 1022:1101 :00:18.2 0600: 1022:1102 :00:18.3 0600: 1022:1103 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[E/O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: I first tried to start the installation in default mode (2.4 kernel) On first hardware detection the system hang whilke trying to install sd_mod. While it is certainly acceptable that on a SATA machine install only works with 2.6, the installer shouldn't hang, but give a meaningful error message. After booting with linux2.6 the install run flawlessly. Great work! Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[Manual] installer-manual on the website (was: release plans for website?)
On Mon, Aug 02, 2004 at 10:55:38PM -0400, Joey Hess wrote: Is there any plan for how the web site update will be handled for sarge's release? Besides just switching the names and links to sarge, I've been looking at what parts of the web site will need updating for the new installer and other missing bits. These include: [...] - sarge/installmanual: doesn't exist. One possibility is to link to the sarge install manual in the debian archive on a mirror, which is updated whenever the images are updated. I don't know how the woody install manual is imported into the web site so maybe however it is manage is better. This is how the installation manual was handled for boot-floppies (i.e. potato and woody): The sources where checked out from the boot-floppies CVS and were build locally. I investigated a bit how to handle the sarge installation manual: The installation manual doesn't build on woody AFAICT, so manual build is probably no option until www-master is updated to sarge, and I think nobody want rely on that. So linking to an external resource like the archive or copying it from there would be better. Some questions to consider: - The boot-floppies manual was built as PDF, plain text and HTML. I think at least plain text and HTML should be available for sarge, too. Yet I don't see any generation of plain text currently. Is this intentional? - For usage on the website the files should be able to be handled by content negotiation. This requires that there is only one directory per arch with all translations in it and files named foo.langcode.html. Would it be possible to generate the pages this way or should we write a little script that solves this by renaming the current output files? Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Manual] installer-manual on the website (was: release plans for website?)
On Thu, Aug 05, 2004 at 08:53:49PM +0200, Osamu Aoki wrote: On Thu, Aug 05, 2004 at 04:11:50PM +0200, Frank Lichtenheld wrote: This is how the installation manual was handled for boot-floppies (i.e. potato and woody): The sources where checked out from the boot-floppies CVS and were build locally. ... Whatever final web page should look like, I really looking for the web page with URL reactivated: http://www.debian.org/releases/testing/installmanual http://www.debian.org/releases/testing/releasenotes This can be even a short sentence stating it is not available on web but only as package. We seem to have simply removed them after woody release. This is what were beginning right now and which was the cause for me to investigate the current install manual. I can do that easily, just a few things to decide: installmanual: What pointers? (Alioth pages?, package?, ...) releasenotes: Only a sentence not available or a pointer to the CVS? Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modconf maintainance - status and future?
On Wed, Jul 28, 2004 at 09:56:13PM -0400, Joey Hess wrote: Frank Lichtenheld wrote: 2) If there are actually some people interested in this (I am, so that if is superfluous) should the program still located in the debian-boot CVS and have debian-boot as maintainer address? I don't see any reason for modconf to remain associated with this list unless someone is doing boot-floppies development here again for some reason. Ok, since this was the only answer to my mail I assume that I can safely adopt modconf. I'm thinking about moving it from the debian-boot CVS to a SVN rep on Alioth, too. If there aren't any objections to this I would ask for the creation of a Alioth project for this this week and then ask for the removal of the code in the CVS rep once I have transfered it there. Any people interested in helping with this are welcome as well as objections and comments to the whole issue. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#256401: modconf: location of modprobe config files changed with module-init-tools
On Sat, Jun 26, 2004 at 09:42:47PM +0200, Yann Bloch wrote: module-init-tools puts its config files in /etc/modprobe.d, not in /etc/modprobe.conf, as modconf expects. The problem had an easy workaround for me: In /usr/share/modconf/params 56c56 CFGFILE=$Target/etc/modprobe.conf --- CFGFILE=$Target/etc/modprobe.d I guess this will need some additional checking to make it integrate smoothly in the various possible configurations. It may even be better not to specify a config file at all, and let modprobe find it itself. Well the maintainer will decide. The only case where this could perhaps brake would be on old versions of module-init-tools ( 3.1, exact version can be determined from the module-init-tools changelog) since these used /etc/modprobe.conf. But this could be solved with a versioned dependency. The thing about this whole code is that it was definetly needed when modconf was used by boot-floppies (the $Target prefix was not equal in this case). Don't know if anyone is still using the --target option today... Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
modconf maintainance - status and future?
Hi. In recent months there were some problems with the modconf program, especially with the linux 2.6 support. Since modconf isn't a part of the Debian installation process anymore (probably since the bf-d-i step) there seems no great interest in maintaining it. Eduard Bloch has done some work, but even that was about seven months ago. I still use modconf and still like it for some purposes. So I would like to improve the situation. Two questions: 1) Would it be ok to officially search for people interested in maintaining it (by mail to WNPP and/or debian-devel)? 2) If there are actually some people interested in this (I am, so that if is superfluous) should the program still located in the debian-boot CVS and have debian-boot as maintainer address? Opinions, comments? Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#234564: minor problems
On Mon, May 03, 2004 at 01:59:10AM +0100, Martin Michlmayr wrote: * Frank Lichtenheld [EMAIL PROTECTED] [2004-02-24 16:45]: I use a pcmcia network card, but the PCMCIA bus was not correctly configured (insmod of ds.o failed, because there was no socket driver loaded), so the network didn't work. After the install I used modconf to load the correct module and it worked. Don't know what the problem exactly was. I can give you a lspci output later if wanted. I think this might be fixed in beta4. Can you try it? If not, can you send the output of lcpci and lcpci -n. Hmm, there are many weird problems with the hardware detection with this notebook: 1) It seems to load all the necessary modules, but 2) It prompts me with the list of all modules. If I choose - the right module (pcnet_cs), it just prompts me again - a false module (like ne2), it starts the network-hw-detection again, but now all dialogs are in English (I use de_DE normally) - none of the above it brings me to the main menu. When I go to Netzwerk einrichten it starts the network-hw-detection again and then prompts me with a list of modules, if I want to remove them, these are all IDE and SCSI modules like ide-scsi, ide-mod (or was it scsi-mod?), etc. I attach lspci outputs made with knoppix (wich detects the hardware just fine, so it seems not to be a problem with the hardware itself). Will try later to also test the other problems. Gruesse and hth, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ 00:00.0 Host bridge: VIA Technologies, Inc. VT8501 [Apollo MVP4] (rev 03) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8501 [Apollo MVP4 AGP] 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 19) 00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 0a) 00:07.4 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 20) 00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 21) 00:0a.0 CardBus bridge: O2 Micro, Inc. OZ6832/6833 Cardbus Controller (rev 34) 00:0a.1 CardBus bridge: O2 Micro, Inc. OZ6832/6833 Cardbus Controller (rev 34) 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i7d (rev 5c) 00:00.0 Class 0600: 1106:0501 (rev 03) 00:01.0 Class 0604: 1106:8501 00:07.0 Class 0601: 1106:0686 (rev 19) 00:07.1 Class 0101: 1106:0571 (rev 06) 00:07.2 Class 0c03: 1106:3038 (rev 0a) 00:07.4 Class 0601: 1106:3057 (rev 20) 00:07.5 Class 0401: 1106:3058 (rev 21) 00:0a.0 Class 0607: 1217:6832 (rev 34) 00:0a.1 Class 0607: 1217:6832 (rev 34) 01:00.0 Class 0300: 1023:8420 (rev 5c)
Bug#234564: minor problems
On Mon, May 03, 2004 at 01:59:10AM +0100, Martin Michlmayr wrote: * Frank Lichtenheld [EMAIL PROTECTED] [2004-02-24 16:45]: I encountered some minor problems during the install process: While creating the filesystems, I selected /dev/hda1 and ext2 and /boot. Then I selected /dev/hda2 (which was already a swap partition) and keep filesystem. After that /dev/hda1 and /dev/hda2 were both marked as to be mounted on /boot Can you reproduce this? No. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
d-i on packages.d.o
Hi. I recently added the udeb packages to packages.debian.org. They are handled like normal packages, placed in section debian-installer and I also added a note to each packages' page and the package list that these packages are not intended for use as normal debs. See http://packages.debian.org/unstable/debian-installer/ for the result. The search functions should also find udeb packages now. I would appreciate any comments (like suggestions for better warnings, requests for more debian-installer specific information [installer-menu-item and the like], comments on the usefulness of these pages in general, etc.). (BTS pseudo-package is www.debian.org) Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#234564: minor problems
Package: installation-reports Debian-installer-version: Beta 2 uname -a: not available, see below Date: 2004-02-24 15:00 Method: CD-Boot, installed from CD, additional packages installed from http mirror Machine: Gericom Notebook Processor: AMD K6-2 Memory: 64 MB Root Device: IDE Root Size/partition table: /dev/hda1 /boot /dev/hda2 swap /dev/hda3 / Output of lspci: not available, see below Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [E] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: After I installed the system sucessfully and worked a little bit on it, the harddrive has started giving strange error messages and the filesystem is totally f***ed up now. I believe this is a hardware problem though. I only took the machine to try the installer. Haven't used it for a year or two. Here the problems during the install: I use a pcmcia network card, but the PCMCIA bus was not correctly configured (insmod of ds.o failed, because there was no socket driver loaded), so the network didn't work. After the install I used modconf to load the correct module and it worked. Don't know what the problem exactly was. I can give you a lspci output later if wanted. I encountered some minor problems during the install process: While creating the filesystems, I selected /dev/hda1 and ext2 and /boot. Then I selected /dev/hda2 (which was already a swap partition) and keep filesystem. After that /dev/hda1 and /dev/hda2 were both marked as to be mounted on /boot After the note about the reboot showed up a note about debconf priorities, but I couldn't read it since the reboot was already started. Somewhat confusing ;) Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
