Bug#514799: release-notes: check grub's hooks in /etc/kernel-img.conf before upgrade
Package: release-notes Severity: normal After upgrading from sarge to etch, users were invited to manually update some entries in /etc/kernel-img.conf (specifically, the postinst_hook and postrm_hook) as described in etch's /usr/share/doc/grub-doc/NEWS.Debian. However, this was not totally obvious, and because the compatibility wrapper ensured that everything worked, I imagine there are quite a few systems where this was not done. It seems possible that such systems would break after the upgrade to lenny (although I haven't tested this). If it is known that they will not break, then please close this bug! (and accept my apologies). Otherwise, it might be helpful to add something like the following to the release notes, possibly at 4.1.1.2 (straight after 4.1.1.1 makes sure that you are on a suitable kernel) or 4.1.6 (straight after LILO issues). 4.1.1.2 Check grub's kernel installation hooks If you use GRUB as bootloader and previously upgraded to etch from an older release of debian, please verify that the hooks in /etc/kernel-img.conf have been updated from /sbin/update-grub to /usr/sbin/update-grub. The older path will cease to work after the upgrade to lenny. For more details, see /usr/share/doc/grub-doc/NEWS.Debian from the grub-doc package. I hope this helps! Best wishes and thanks for all your work on debian... -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#512578: wget(1) follow-ftp example is wrong or confusing
Package: wget Version: 1.10.2-2 Severity: minor Tags: patch I believe that there is a bug in the manpage wget(1). /usr/share/man/man1/wget.1.gz The example involving follow/no-follow says the opposite of what I expect. If I understand the example, then: normal factory default: off (no-follow) local default set in wgetrc: on (follow) user option needed to restore default: (no-follow) I therefore propose the attached patch (relative to the etch version of wget, but the same goes for the current lenny version). I hope this helps. Best wishes and thanks... Jeremy -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages wget depends on: ii libc6 2.3.6.ds1-13etch8 GNU C Library: Shared libraries ii libssl0.9.80.9.8c-4etch4 SSL shared libraries wget recommends no packages. -- no debconf information --- wget.1 2006-06-28 17:41:30.0 +0100 +++ wget.1.new 2009-01-21 12:44:58.0 + @@ -228,8 +228,8 @@ \\fB\-\-no\-\fR prefix. This might seem superfluous\-\-\-if the default for an affirmative option is to not do something, then why provide a way to explicitly turn it off? But the startup file may in fact change -the default. For instance, using \f(CW\*(C`follow_ftp = off\*(C'\fR in -\\fI.wgetrc\fR makes Wget \fInot\fR follow \s-1FTP\s0 links by default, and +the default. For instance, using \f(CW\*(C`follow_ftp = on\*(C'\fR in +\\fI.wgetrc\fR makes Wget \fIfollow\fR \s-1FTP\s0 links by default, and using \fB\-\-no\-follow\-ftp\fR is the only way to restore the factory default from the command line. .Sh Basic Startup Options
Bug#425878: kicker: clockapplet doesn't step through timezones properly when clock type is fuzzy
Package: kicker Version: 4:3.5.5a.dfsg.1-6 Severity: normal Many thanks for the clock applet, it's very nice. When clock type is 'fuzzy', there's a bug with the timezones feature. The bug doesn't happen with the other clock types. If you step to the next timezone (by clicking the middle mouse button), the display changes to Twelve o'clock. It stays like that until the end of the current minute, when the fuzzy string is updated correctly. If you click at just the right moment (or the wrong moment!) you can even produce an unreadable string with part or Twelve o'clock over-writing part of a different string. I suggest that it would be better to generate a new fuzzy string as soon as the timezone is changed, rather than waiting until the minute is over. (This shouldn't be hard to do. For example, when you change clock type from digital to fuzzy, the correct fuzzy string is generated immediately.) For the record, I attach ~/.kde/share/config/clockappletrc -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kicker depends on: ii kdebase-data 4:3.5.5a.dfsg.1-6 shared data files for the KDE base ii kdelibs4c2a4:3.5.5a.dfsg.1-8 core libraries and binaries for al ii libacl12.2.41-1 Access control list shared library ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libattr1 2.4.32-1 Extended attribute shared library ii libaudio2 1.8-4 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libfam02.7.0-12 Client library to control the FAM ii libfontconfig1 2.4.2-1.2 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-21GCC support library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libkonq4 4:3.5.5a.dfsg.1-6 core libraries for Konqueror ii libpng12-0 1.2.15~beta5-1PNG library - runtime ii libqt3-mt 3:3.3.7-4 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-7 X11 client-side library ii libxau61:1.0.1-2 X11 authorisation library ii libxcomposite1 1:0.3-3 X11 Composite extension library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes3 1:4.0.1-5 X11 miscellaneous 'fixes' extensio ii libxft22.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii libxtst6 1:1.0.1-5 X11 Testing -- Resource extension ii zlib1g 1:1.2.3-13compression library - runtime kicker recommends no packages. -- no debconf information [Analog] LCD_Style=true Show_Date=false Show_Seconds=true [Calendar] Size=239,175 [Date] Font=helvetica,11,-1,5,50,0,0,0,0,0 [Digital] Blink=false LCD_Style=true Show_Date=true Show_Seconds=false [Fuzzy] Font=helvetica,11,-1,5,0,0,0,0,0,0 Fuzzyness=1 Show_Date=true [General] Initial_TZ=1 RemoteZones=Asia/Tokyo,Australia/Darwin,Australia/Eucla,Australia/Sydney,Europe/Berlin,Europe/London,Europe/Zurich,Pacific/Auckland Type=Fuzzy
Bug#417837: knetwalk: at startup, settings - game type does not show which game type is active
Package: knetwalk Version: 4:3.5.5-1 Severity: normal Many thanks for a nice puzzle! There is a small bug, though. 1. Start knetwalk 2. Click menu option settings - choose game type. Observe: There is no indication which game type is active. 3. Click on a game type, for example, normal. 4. Click the menu option again. Observe: there is now a tick beside normal. This is good. I think program startup should initialise the tick, so that it is visible at step 2 already. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages knetwalk depends on: ii kdelibs4c2a4:3.5.5a.dfsg.1-6 core libraries and binaries for al ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libgcc11:4.1.1-21GCC support library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libkdegames1 4:3.5.5-1 KDE games library and common files ii libpng12-0 1.2.15~beta5-1PNG library - runtime ii libqt3-mt 3:3.3.7-3 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-5 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii zlib1g 1:1.2.3-13compression library - runtime knetwalk recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417073: parted: trouble growing an old ext2 partition
Package: parted Version: 1.7.1-3 Severity: normal Parted says You found a bug in GNU Parted!. But even before it said that, a resize command seems to have failed silently. I'm attaching a log file with details. I'm going to leave the offending partitions alone for a while, in case you get back to me for further details. At the start of the logfile, we have 5 7230MB 9377MB 2147MB logical ext2/usr 6 9377MB 10.2GB 806MB logical ext2(old /var) to be deleted 7 10.2GB 11.8GB 1612MB logical ext2/home 8 11.8GB 12.0GB 197MB logical ext2(old /tmp) to be deleted My plan was to delete the partitions currently numbered 6 and 8, and grow /usr and /home to fill the new space. As the logfile shows: - my first attempt to resize 5 failed silently (this seems bad!) - my second attempt gives a lot of warnings of the type: Warning: Block 786702 shouldn't have been marked (0, 1)! and then: Error: Attempt to read sectors -2--1 outside of partition on /dev/hda. Ignore/Cancel? c - when I cancelled, parted said that I'd found a bug, and then: Error: SEGV_MAPERR (Address not mapped to object)Aborted Later by contrast, removing (the old) 8 and growing /home worked perfectly. It seems to me that: - it's bad that the first resize failed *silently* - some documentation on what the warnings mean and whether they are safe to ignore would we welcome Trying the same resize again gives the same errors. For the time being, I'm not going to try anything else with that partition and that free space, in case you want some more information, a backtrace or something. I can give more details of the partition's history: (January 2000) - win98SE installer used to make /dev/hda1; win98SE installed there - slink installer used to make other partitions - only further change in seven years was updating the swap-partition type (March 2007) - booted testing etch from /dev/hdb - dumped the disk layout with sfdisk -d (for clarity, I've added another column to show the normal mount points) # partition table of /dev/hda unit: sectors /dev/hda1 : start= 63, size= 13349952, Id= b /dev/hda2 : start= 13350015, size= 257040, Id=83, bootable/ /dev/hda3 : start= 13607055, size= 13092975, Id= 5 /dev/hda4 : start=0, size=0, Id= 0 /dev/hda5 : start= 13607118, size= 256977, Id=82 swap /dev/hda6 : start= 13864158, size= 256977, Id=82 swap /dev/hda7 : start= 14121198, size= 4192902, Id=83 /usr /dev/hda8 : start= 18314163, size= 1574307, Id=83 /var /dev/hda9 : start= 19888533, size= 3148677, Id=83 /home /dev/hda10: start= 23037273, size= 3662757, Id=83 /tmp - used parted 1.7.1-3 from testing to make successful changes to /dev/hda as follows: - rm 6 (old-style 128MB swap partition for kernel 2.1.xxx) - rm 5 (old-style 128MB swap partition for kernel 2.1.xxx) - resize 3 7230 13670 (shrink extended partition now that swap is gone) - resize 2 6834 7033 (grow root partition by 50%) - mkpartfs primary linux-swap 7033 7230 (single bigger swap, ~192MB) - new output from sfdisk -d # partition table of /dev/hda unit: sectors /dev/hda1 : start= 63, size= 13349952, Id= b /dev/hda2 : start= 13350015, size= 385560, Id=83, bootable / /dev/hda3 : start= 14121135, size= 12578895, Id= 5 /dev/hda4 : start= 13735575, size= 385560, Id=82 swap /dev/hda5 : start= 14121198, size= 4192902, Id=83 /usr /dev/hda6 : start= 18314163, size= 1574307, Id=83 /var /dev/hda7 : start= 19888533, size= 3148677, Id=83 /home /dev/hda8 : start= 23037273, size= 3662757, Id=83 /tmp - used parted 1.7.1-3 to make more changes as follows: - resize 8 23037273s 23422769s (down to size by which /home will grow) - mkpart logical ext2 23422833s 25125659s (this will be the new /var) - cp 6 9 (paranoid: use cp (not move) so I can mount both for 'diff -R') - mkpart logical ext2 25125723s 26700029s (this will be the new /tmp) - cp 8 10 (paranoid again) - rebooted; did my paranoid checks; ready to erase the old partitions - rm 6 (the old /var), see logfile - failure to grow /usr (the reason for this bugreport) - rm 7 (the new minor number for the old /tmp) - success with growing /home -- System Information: Debian Release: 4.0 Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-486 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages parted depends on: ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libncurses5 5.5-5 Shared libraries for terminal hand ii libparted1.7-1
Bug#416573: mpage(1) - multiple manpage fixes
Package: mpage Version: 2.5.4-2 Severity: normal Tags: patch I propose the attached patch for the mpage(1) manpage; the diff is relative to etch's version, 2.5.4-2. I've tried to improve the description of the -bpapersize option. I've also corrected a large number of typos, grammar errors, groff markup errors, trailing whitespace errors, and strange pieces of English. I hope this helps. Best wishes, J Bygott --- mpage.1 2005-09-13 20:38:25.0 +0100 +++ mpage.1.new 2007-03-29 01:43:56.122338048 +0100 @@ -53,7 +53,7 @@ .SH DESCRIPTION -.I mpage +.B mpage reads plain text files or PostScript documents and prints them on a PostScript printer with the text reduced in size so that several pages appear on one sheet of paper. @@ -62,14 +62,18 @@ .PP The following options are recognized (note that arguments to options may be -separated from the option by spaces, except for +separated from the option by spaces, except for .BR -B , .BR -m , .BR -M , .B -p and .BR -P ): -Also when mpage encounters -- as option it will stop parsing arguments +Also when +.B mpage +encounters +.B -- +as option it will stop parsing arguments and the remaining arguments are interpreted as filenames. .TP @@ -83,7 +87,7 @@ .TP .B -4 Print 4 normal pages per sheet -.IR (default) . +.RI ( default ). .TP .B -8 @@ -94,25 +98,29 @@ Toggle layout of the pages on the sheet so that successively numbered pages run down the sheet, as opposed to left to right. .RI ( default -updown) . +updown). .TP .B -A -This option is deprecated, see \fB-b\fP. -Prepare output for A4 sized paper. -For default see 'mpage -x'. +This option is deprecated, use +.B -bA4 +instead. .TP -.BI -b papertype -Prepare output for selected paper type. +.BI -b papersize +Prepare output for the selected paper type. .I Papersize -can be \fIA3\fP for European A3, -\fIA4\fP for European A4, -\fILetter\fP for US Letter or \fILegal\fP for Legal -sized paper. -For default see 'mpage -x'. -To see the list of currently available types, just give the 'mpage -bl' -or 'mpage -b?' command (Note: mpage exits after finding such option use.) +can be \fBA3\fP for European A3, +\fBA4\fP for European A4, +\fBLetter\fP for US Letter, or \fBLegal\fP for Legal +sized paper. For available types, see option \fB-bl\fP. +For the default, see 'mpage -x'. This default is taken from the +system; see \fBpapersize\fP(5). If it isn't found, mpage exits +with an error. + +.TP +.BR -bl ,\ -b? +List the currently available paper types, then exit. .TP .BR -B [\fInum\fR[\fBlrtb\fR]*] @@ -120,19 +128,19 @@ Specify text box margins and line thickness. The default is 0 columns (lines) for both left and right (top and bottom) margins and 0 line thickness. -Specifying -.B -B -solely toggles printing of the box. +Specifying +.B -B +solely toggles printing of the box. .IR l , .IR r , .I t or .I b -set the left, right, top or bottom margin respectively to +set the left, right, top or bottom margin respectively to .I num columns (lines). -Not specifying any of the sides, will set the line thickness when -.I num +Not specifying any of the sides, will set the line thickness when +.I num is given. For example .BI -B 1 @@ -141,7 +149,7 @@ .TP .B -c -Toggle concatenation off pages from different files on single sheets +Toggle concatenation of pages from different files on single sheets .RI ( default off). @@ -165,27 +173,26 @@ .TP .BI -D dateformat -Set the date format as in +Set the date format as in .IR strftime (3) to be used in date/time representations (e.g. in headers). -(Note: to be useful you probably need the \fB-H\fP option.) +(Note: to make this useful you probably need the \fB-H\fP option.) .TP .B -e -Print 2 normal pages per sheet in duplex mode. Every first -and fourth page or on one side and every second and third +Print 2 normal pages per sheet in duplex mode: every first +and fourth page on one side and every second and third on the other side. This is more or less a combination of -the \fR-O\fP and \fR-E\fP option but then in one pass. +the \fR-O\fP and \fR-E\fP options but in one pass. .TP .B -E -Print 2 normal pages per sheet. However, this option will print -every second and third page of every set of four pages. -This option will ignore +Print 2 normal pages per sheet, namely: print only the second and +third page of every set of four pages. See also \fB-O\fP. These +options override .B -a and .BR -l . -See also the \fR-O\fP option. Using these options double sided prints can be created without a duplex printer. @@ -193,11 +200,11 @@ .B -f Toggles folding lines longer than page width .RI ( default -off) . +off). .TP .BI -F fontname -Specify font. +Specify font. .RI ( default Courier). Check your printer for supported fonts. Note: this has almost nothing to do with the fonts used for your X-windows/KDE/Gnome @@ -205,13 +212,13 @@ .TP .BI -h header -This is used only when the +This
Bug#416389: upgrade from 0.1.19 leaves crufty /var/lib/harden-clients
Package: harden-clients Version: 0.1.30 Severity: normal From the sarge version (0.1.17) of harden-clients.config: mkdir -p /var/lib/harden-clients touch /var/lib/harden-clients/fetchmail ... touch /var/lib/harden-clients/fetchmail-ssl But there is no clean-up! When I purge the package, those files remain. This is a bug in the sarge version of harden-clients. Now, I see that the changelog for 0.1.19 says: * Fetchmail package now support ssl so removing those questions. So new versions don't touch those files anymore. But it would still be nice clean this up for users upgrading from sarge. Maybe the postinst could do something like this? case $1 in configure) # clean up behind versions 0.1.19 (remove in etch+2) rm -f /var/lib/harden-clients/fetchmail rm -f /var/lib/harden-clients/fetchmail-ssl rmdir /var/lib/harden-clients 2 /dev/null ... Thank you. It's a pity this won't make it into etch, otherwise you could remove it in etch+1 already! Best wishes, Jeremy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415589: wbritish: please add 'fenugreek'
Package: wbritish Version: 6-2 Severity: normal Please consider adding 'fenugreek' to the next edition of wbritish. It's a medicinal herb and flavouring, popular since antiquity, known to the Egyptians, widely used today in middle eastern and Indian cookery. It's available in all good UK supermarkets and any Asian grocer's. It's a common enough word, suitable for 'wbritish' at least. Thank you. -- System Information: Debian Release: 4.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414270: kdeprint: kprinter(1) typos / typesetting errors
Package: kdeprint Version: 4:3.5.5a.dfsg.1-6 Severity: minor Tags: patch The attached patch cleans up a couple of things on the kprinter(1) manpage. In particular, the option -n (number of copies) should be described on a new line. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kdeprint depends on: ii enscript 1.6.4-11 Converts ASCII text to Postscript, ii kdelibs4c2a4:3.5.5a.dfsg.1-6 core libraries and binaries for al ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libgcc11:4.1.1-21GCC support library ii libqt3-mt 3:3.3.7-3 Qt GUI Library (Threaded runtime v ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii poster 1:19990428-8 Create large posters out of PostSc ii psutils1.17-24 A collection of PostScript documen -- no debconf information --- kprinter.1 2007-02-06 19:56:20.0 + +++ kprinter.1.new 2007-03-10 13:39:30.0 + @@ -6,7 +6,7 @@ .SH SYNOPSIS \fBkprinter\fP [Qt\-options] [KDE\-options] [options] file(s) .SH DESCRIPTION -\fBKPrinter\fP opens automatically when you click on the Print icon of any KDE application. Choose your print job settings by going through the dialog and the click on the Print button. +\fBKPrinter\fP opens automatically when you click on the Print icon of any KDE application. Choose your print job settings by going through the dialog and then click on the Print button. .sp 1 \fBkprinter\fP is a very versatile tool. Depending on the actual features and power of the print subsystem of your computer, \fBkprinter\fP translates the former's abilities into a nice and easy\-to\-understand GUI. If your print subsystem does not support duplexing, \fBkprinter\fP will not show the option. If your print subsystem is CUPS, kprinter is at its peak shape. .sp 1 @@ -48,7 +48,9 @@ .TP .B \-J, \-t title Title/Name for the print job -\-#, \-n number Number of copies +.TP +.B \-#, \-n number +Number of copies .TP .B \-o option=value Printer option @@ -114,7 +116,7 @@ .TP .B \-\-dograb running under a debugger can cause an implicit -\-nograb, use \-dograb to override +\fB\-\-nograb\fP, use \fB\-\-dograb\fP to override .TP .B \-\-sync switches to synchronous mode for debugging
Bug#413248: installation-reports: (etch) strangeness with non-ASCII-character filenames on vfat partition
Package: installation-reports Version: weekly build 20070115 Severity: normal I've met some problems with an existing vfat filesystem, specifically with filenames that have non-ASCII characters. These problems might affect very many users, hence severity important. [Unrelated issue, for completeness, see APPENDIX below: I've copied an excerpt from /var/log/installer/syslog, showing a failure of 'dpkg --compare-versions'] Summary: Problems with non-ASCII characters in windows filenames (eg SendTo/3½ Floppy). The problem here is the one-half character. Possible cause: Old installer (official weekly build CD1 20070115), but I'm reporting this anyway in case the problem still exists. The problem arises when *installing* etch from this CD. It does not arise when *upgrading* sarge to etch with the same CD. If the problem no longer exists, great. But if it does, severity seems important since this filename is standard in win9x (at least) so very many users will be affected. (If it's a feature not a bug, then at the very least something in the release notes is needed. Perhaps something to do with uni_xlate or utf8 mount options to vfat??? But it would be best if the installer just did things right.) My current mount options in /etc/fstab are as created by the installer: /dev/hda1 /windowsvfatdefaults0 0 Symptoms: debian:/windows$ find * | wc wc: standard input:19465: Invalid or incomplete multibyte or wide character wc: standard input:19614: Invalid or incomplete multibyte or wide character wc: standard input:19652: Invalid or incomplete multibyte or wide character 19961 52873 989337 The problem filenames are things like 'windows/SendTo/3½ Floppy (A).lnk'(*very* common on win 98 systems) 'windows/Favorites/Münster.url' debian:~$ mkisofs -r -J -o cdtest.iso /windows/windows/Favorites [...] Incorrectly encoded string (Hifisound der Lautsprecher Selbstbau Spezialist aus [EMAIL PROTECTED]) encountered. Possibly creating an invalid Joliet extension. Aborting. == A few system details: CPU: AMD Athlon(TM) XP2000+ stepping 02 install medium: etch testing weekly build 15/1/2007 [Debian GNU/Linux testing _Etch_ - Official Snapshot i386 CD Binary-1 20070115-09:39] installation method: default install (i.e. I just pressed ENTER) patitioning: -- use exisiting /dev/hda1 as vfat on mountpoint /windows -- install linux on /dev/hdb -- dual boot via grub -- install grub boot sector on /dev/hda debian:~$ locale LANG=en_GB.UTF-8 LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 LC_COLLATE=en_GB.UTF-8 LC_MONETARY=en_GB.UTF-8 LC_MESSAGES=en_GB.UTF-8 LC_PAPER=en_GB.UTF-8 LC_NAME=en_GB.UTF-8 LC_ADDRESS=en_GB.UTF-8 LC_TELEPHONE=en_GB.UTF-8 LC_MEASUREMENT=en_GB.UTF-8 LC_IDENTIFICATION=en_GB.UTF-8 LC_ALL= == APPENDIX (excerpt from /var/log/installer/syslog) This may be normal but it looks strange. Feb 28 19:58:48 debootstrap: dpkg: libc6: dependency problems, but configuring anyway as you request: Feb 28 19:58:48 debootstrap: libc6 depends on tzdata; however: Feb 28 19:58:48 debootstrap: Package tzdata is not installed. Feb 28 19:58:48 debootstrap: Setting up libc6 (2.3.6.ds1-8) ... Feb 28 19:58:48 debootstrap: dpkg: --compare-versions takes three arguments: version relation version Feb 28 19:58:48 debootstrap: Feb 28 19:58:48 debootstrap: Type dpkg --help for help about installing and deinstalling packages [*]; Feb 28 19:58:48 debootstrap: Use `dselect' or `aptitude' for user-friendly package management; Feb 28 19:58:48 debootstrap: Type dpkg -Dhelp for a list of dpkg debug flag values; Feb 28 19:58:48 debootstrap: Type dpkg --force-help for a list of forcing options; Feb 28 19:58:48 debootstrap: Type dpkg-deb --help for help about manipulating *.deb files; Feb 28 19:58:48 debootstrap: Type dpkg --license for copyright license and lack of warranty (GNU GPL) [*]. Feb 28 19:58:48 debootstrap: Feb 28 19:58:48 debootstrap: Options marked [*] produce a lot of output - pipe it through `less' or `more' ! Feb 28 19:58:48 debootstrap: Feb 28 19:58:48 debootstrap: Selecting previously deselected package perl-base.
Bug#412071: kmail: ispell language switching is bugged
Package: kmail Version: 4:3.5.5.dfsg.1-6 Severity: normal Several editors in kde integrate with spelling checking (e.g ispell). No problem if you only use one dictionary. The problems come if you often need to switch language. (This is an area where debian should excel. Think: language teacher preparing worksheets, or student writing literature essays, or people with customers abroad, or ...) kwritedoes the switching beautifully kedit tries to do the same but is bugged kmail composer tries to do the same but is bugged differently (it pops up both a checker in the changed language and a box saying you need to close and restart!) kword does it brokenly (it's not clear if it's trying to integrate in the same way or trying to do it differently; but what it does is badly broken: offering a languages unrelated to what is installed, e.g. hebrew, and crashing if those are then chosen) Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409015, where I described the correct behaviour of kwrite, and why kedit/kmail/kword do this incorrectly. (I realise that I should have filed separate bugs to help track the issues. Sorry about that. That's what I am doing now.) Many thanks for looking at this. I'm sure switching languages is useful for many people. (Dr) Jeremy Bygott Oxford I'm told that there is a joke in Finland. If you speak three languages, you are trilingual. If you speak only two languages, you are bilingual. And if you speak only one language? Then you are English. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kmail depends on: ii kdebase-kio-plugins4:3.5.5a.dfsg.1-6 core I/O slaves for KDE ii kdelibs4c2a4:3.5.5a.dfsg.1-6 core libraries and binaries for al ii kdepim-kio-plugins 4:3.5.5.dfsg.1-6 KDE pim I/O Slaves ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libaudio2 1.8-3 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-21GCC support library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libkcal2b 4:3.5.5.dfsg.1-6 KDE calendaring library ii libkdepim1a4:3.5.5.dfsg.1-6 KDE PIM library ii libkleopatra1 4:3.5.5.dfsg.1-6 KDE GnuPG interface libraries ii libkmime2 4:3.5.5.dfsg.1-6 KDE MIME interface library ii libkpimidentities1 4:3.5.5.dfsg.1-6 KDE PIM user identity information ii libksieve0 4:3.5.5.dfsg.1-6 KDE mail/news message filtering li ii libmimelib1c2a 4:3.5.5.dfsg.1-6 KDE mime library ii libpng12-0 1.2.15~beta5-1PNG library - runtime ii libqt3-mt 3:3.3.7-3 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-5 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft22.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii perl 5.8.8-7 Larry Wall's Practical Extraction ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages kmail recommends: ii procmail 3.22-16Versatile e-mail processor -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412072: kedit: ispell language switching is bugged
Package: kedit Version: 4:3.5.5-3 Severity: normal Several editors in kde integrate with spelling checking (e.g ispell). No problem if you only use one dictionary. The problems come if you often need to switch language. (This is an area where debian should excel. Think: language teacher preparing worksheets, or student writing literature essays, or people with customers abroad, or ...) kwritedoes the switching beautifully kedit tries to do the same but is bugged kmail composer tries to do the same but is bugged differently (it pops up both a checker in the changed language and a box saying you need to close and restart!) kword does it brokenly (it's not clear if it's trying to integrate in the same way or trying to do it differently; but what it does is badly broken: offering a languages unrelated to what is installed, e.g. hebrew, and crashing if those are then chosen) Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409015, where I described the correct behaviour of kwrite, and why kedit/kmail/kword do this incorrectly. (I realise that I should have filed separate bugs to help track the issues. Sorry about that. That's what I am doing now.) Many thanks for looking at this. I'm sure switching languages is useful for many people. (Dr) Jeremy Bygott Oxford I'm told that there is a joke in Finland. If you speak three languages, you are trilingual. If you speak only two languages, you are bilingual. And if you speak only one language? Then you are English. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kedit depends on: ii kdelibs4c2a4:3.5.5a.dfsg.1-6 core libraries and binaries for al ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libgcc11:4.1.1-21GCC support library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 kedit recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411664: openbsd-inetd: depends on package of lower priority
Package: openbsd-inetd Version: 0.20050402-4 Severity: serious Justification: Policy 2.5 policy: Packages must not depend on packages with lower priority values Currently openbsd-inetd shows up as important but it [1]depends on update-inetd which is only standard. I think the [2]overrides are wrong, not the package itself, but I don't know where to report rc bugs in overrides. [1] http://packages.debian.org/testing/net/openbsd-inetd [2] http://packages.qa.debian.org/o/openbsd-inetd.html Sorry if there are automatic checks that would have caught this anyway. (There should be, if there aren't!) -- System Information: Debian Release: 4.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411602: cruft: more filter updates
Package: cruft Version: 0.9.6-0.15 Severity: normal As before, comments come in the following categories: NEW, REMOVE, RENAME, EDIT, RENAME AND EDIT, ASK Some edits are described in pseudo-patch notation: -delete this line +add this line == NEW == New filter to take over three lines from filters/cron; this change happened in sarge already, see /usr/share/doc/cron/NEWS.Debian.gz filters/checksecurity # checksecurity 2.0.7-10.1 /var/log/setuid.changes* /var/log/setuid.today /var/log/setuid.yesterday filters/emacs21-common # emacs21-common 21.4a+1-3 /usr/share/emacs21/site-lisp/**/*.elc /usr/local/share/emacs/21.4 /usr/local/share/emacs/21.4/site-lisp (One line comes from the existing filters/emacsen-common, but with s/20/21/ .) == REMOVE == == RENAME == [Mentioned at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334091 as an afterthought; understandably overlooked.] tcl8.0 - tcl8.3(tcl8.0 not in etch, 'practically obsolete' in sarge according to the package's own synopsis) And then copy it to - tcl8.4(same filter but people might have only one version of tcl installed, and we don't know which) == EDIT == filters/bsdgames (files have moved - FHS compliance) +# bsdgames 2.17-8 -/var/lib/games/bsdgames/** +/var/games/bsdgames/** filters/cron +# cron 3.0pl1-100 (etch) +/var/backups +/var/backups/dpkg.status* +/var/backups/group.bak +/var/backups/gshadow.bak +/var/backups/passwd.bak +/var/backups/shadow.bak +/var/lock/cron.daily -/var/log/btmp* #Rationale: sarge's cron.monthly/standard says +/var/log/btmp # rotation of btmp taken over by logrotate # so only btmp itself can be listed here (even btmp might better belong to pkg login??) # The rotated btmp* belongs in filter/logrotate # since it's cruft if logrotate isn't installed # (We can't assign btmp itself to logrotate # because logrotate isn't *required* only *important* -/var/log/setuid.changes* #belongs in checksecurity now (sarge's -/var/log/setuid.today # cron already doesn't touch these files) -/var/log/setuid.yesterday # see /usr/share/doc/cron/NEWS.Debian.gz +/var/spool/cron/crontabs/* +/var/run/crond.reboot # (not sure about this line) filters/emacsen-common +# emacsen-common 1.4.17 -/usr/share/emacs20/site-lisp/**/*.elc # not in etch/sarge (last seen woody) +/usr/local/share/emacs +/usr/local/share/emacs/site-lisp filters/nvi (patch) --- nvi 2005-10-28 18:01:53.0 +0100 +++ nvi.new 2005-11-03 21:54:28.0 + @@ -1,9 +1,10 @@ +# nvi 1.79-22 /usr/bin/editor /usr/bin/ex /usr/bin/vi /usr/bin/view /usr/share/man/man1/editor.1.gz -/usr/share/man/man1/ex.1 -/usr/share/man/man1/view.1 +/usr/share/man/man1/ex.1.gz +/usr/share/man/man1/vi.1.gz /usr/share/man/man1/view.1.gz /var/tmp/vi.recover filters/pdmenu #pdmenu 1.2.89 (etch) -/var/lib/pdmenu/pdmenurc_auto #obsolete since 1.2.81; removed in sarge postinst +/var/lib/pdmenu/pdmenurc +/var/lib/pdmenu/pdmenurc.vc +/var/lib/pdmenu/pdmenurc.x11 filters/ppp #ppp 2.4.4rel-4.1 (etch) #files deleted in ppp.postrm seem like the right things to list here: /etc/ppp/pap-secrets /etc/ppp/chap-secrets /etc/ppp/resolv.conf /etc/ppp/peers/provider /etc/chatscripts/provider /etc/ppp/peers/ /etc/ppp/ip-up.d/ /etc/ppp/ip-down.d/ /etc/ppp/ /etc/chatscripts/ /var/log/ppp.log /var/log/ppp-connect-errors /var/log/ppp-ipupdown.log filters/vim (add version number and alphabetize for clarity) # vim 7.0-122+1 /usr/bin/editor /usr/bin/ex /usr/bin/vi /usr/bin/view /usr/share/man/man1/editor.1.gz /usr/share/man/man1/ex.1.gz /usr/share/man/man1/vi.1.gz /usr/share/man/man1/view.1.gz filters/vim-gnome (same as filters/vim except for name in comment) # vim-gnome 1:6.3-071+1 == RENAME AND EDIT == (emacs20 is not in etch, so: mv filters/emacs20 filters/emacs21 and then s/emacs20/emacs21/ ) == ASK == filters/dpkg I wonder if the following line in the filter isn't too general? /var/lib/dpkg/* My ex-slink-potato-woody-sarge system has this file; looks pretty crufty to me: -rw-rw-r-- 1 root root 0 2000-11-10 21:03 predep-package So maybe we should edit? -/var/lib/dpkg/* +/var/lib/dpkg/available +/var/lib/dpkg/available-old +/var/lib/dpkg/cmethopt +/var/lib/dpkg/diversions +/var/lib/dpkg/diversions-old +/var/lib/dpkg/lock +/var/lib/dpkg/methlock +/var/lib/dpkg/statoverride +/var/lib/dpkg/statoverride-old +/var/lib/dpkg/status +/var/lib/dpkg/status-old
Bug#411261: sharutils: uudecode(1) suggestions
Package: sharutils Version: 1:4.6.3-0 Severity: minor Tags: patch Thank you for recently fixing some very old issues with this manpage. May I make a further suggestion? I think the main paragraph for uuencode is currently quite unclear and also inaccurate. Unclear because of the future tense combined with jumping between the description of encoding and decoding. Inaccurate, because _name_ is only a *suggestion* (uudecode -o can override the name). How about the following text instead? Uuencode reads _file_ (or by default the standard input) and writes an encoded version to the standard output, using only printing ASCII characters. The encoded output begins with a header, for use by uudecode, which records the mode of the input file and suggests _name_ for the decoded file that will be created. (If _name_ is /dev/stdout then uudecode will decode to standard output.) The encoding has the format documented at uuencode(5), unless the option -m is given, when base64 encoding is used instead. I attach a fairly small patch for this. Actually, would you consider a patch for bigger changes? For a start, the manpage should use fonts in a more standard way. More importantly, I think BUGS should list something like this: o uudecode silently overwrites _name_ if it exists already o uudecode accepts names like ../foo Thus, users would at least be warned that they should always inspect the header lines or use the -o option. (If you judge that this belongs upstream, I'd be grateful if you could forward it, thank you.) Yours, (Dr) Jeremy Bygott Oxford -- System Information: Debian Release: 4.0 --- uuencode.1.exp 2007-02-17 12:15:16.035662000 + +++ uuencode.1.new 2007-02-17 16:31:20.535903808 + @@ -45,8 +45,8 @@ .I Uuencode and .I uudecode -are used to transmit binary files over transmission mediums -that do not support other than simple +are used to transmit binary files over channels +that support only simple ASCII data. .PP @@ -54,22 +54,23 @@ reads .I file (or by default the standard input) and writes an encoded version -to the standard output. -The encoding uses only printing +to the standard output, using only printing ASCII -characters and includes the -mode of the file and the operand +characters. The encoded output begins with a header, for use by +.IR uudecode , +which records the mode of the input file and suggests .I name -for use by -.I uudecode. -If +for the decoded file that will be created. (If .I name is .I /dev/stdout -the result will be written to standard output. By default the standard -UU encoding format will be used. If the option +then +.I uudecode +will decode to standard output.) The encoding has the format +documented at uuencode(5), unless +the option .I \-m -is given on the command line +is given, when .B base64 encoding is used instead. .PP @@ -96,8 +97,8 @@ .I name is /dev/stdout the result will be written to standard output. .I Uudecode -ignores any leading and trailing lines. The program can automatically decide -which of the both supported encoding schemes are used. +ignores any leading and trailing lines. The program tells from the +header which of the two supported encoding schemes was used. .SH EXAMPLES The following example packages up a source tree, compresses it, uuencodes it and mails it to a user on another system.
Bug#410800: /etc/cruft/filters/foo might override /usr/lib/cruft/filters/foo ?
Package: cruft Version: 0.9.6-0.15 Severity: wishlist Hi, Maybe cruft should ignore /usr/lib/cruft/filters/foo if the admin has created a filter /etc/cruft/filters/foo. This would provide a neat way of overriding a filter shipped with cruft if it is out of date, or if admin has installed foo from unstable. At the moment, it seems admin has to tamper with the contents of /usr/lib/cruft/filters, which is a pity: that dir ought to remain under control of dpkg entirely. What do you think? It would be a one-line patch to /usr/lib/cruft/extrafiles Regards, Jeremy -- System Information: Debian Release: 4.0 APT prefers testing -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410719: emacs21-common: minor typos in NEWS file
Package: emacs21-common Version: 21.4a+1-3 Severity: minor Tags: patch Hi, I propose the attached minor patch for the file /usr/share/emacs/21.4/etc/NEWS which fixes a typo and removes some spurious trailing whitespace. Best wishes, etc -- System Information: Debian Release: 4.0 --- NEWS2007-01-04 07:53:32.0 + +++ NEWS.new2007-02-12 20:59:28.0 + @@ -849,7 +849,7 @@ *** If Emacs was invoked with the `-q' or `--no-init-file' options, it does not allow you to save customizations in your `~/.emacs' init file. This is because saving customizations from such a session would -wipe out all the other customizationss you might have on your init +wipe out all the other customizations you might have on your init file. ** If Emacs was invoked with the `-q' or `--no-init-file' options, it @@ -2350,7 +2350,7 @@ ** Function assq-delete-all replaces function assoc-delete-all. -** The new function animate-string, from lisp/play/animate.el +** The new function animate-string, from lisp/play/animate.el allows the animated display of strings. ** The new function `interactive-form' can be used to obtain the @@ -2588,7 +2588,7 @@ matches any character in SET. SET may be a character or string. Ranges of characters can be specified as `A-Z' in strings. -'(in SET)' +'(in SET)' like `any'. `(not (any SET))' @@ -2790,7 +2790,7 @@ `(one-or-more SEXP)' matches one or more occurrences of A. - + `(1+ SEXP)' like `one-or-more'. @@ -2802,7 +2802,7 @@ `(zero-or-one SEXP)' matches zero or one occurrences of A. - + `(optional SEXP)' like `zero-or-one'.
Bug#410738: cruft: adjust filter for transition to xorg?
Package: cruft Version: 0.9.6-0.15 Severity: normal Hi Marcin, I see that cruft has a filter /usr/lib/cruft/filters/xfree86-common but there is no such package in etch. http://packages.debian.org/xfree86-common http://packages.debian.org/x11-common I believe the filter should be renamed x11-common, and changed so it says #x11-common 1:7.1.0-11 /etc/X11/xorg.conf /var/log/Xorg.0.log /var/log/Xorg.0.log.old On an etch system, the file /etc/X11/XF86Config-4, if present, really *is* cruft. I'm not sure /etc/X11/config is meaningful anymore (on this etch system, there is no such file). And if /var/log/xdm-errors should be listed anywhere, then in a separate filter for package xdm, since it is quite normal to have only gdm or kdm installed, not xdm. Best wishes, Jeremy -- System Information: Debian Release: 4.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410309: lapack-doc: multiple instances of applie
Package: lapack-doc Version: 3.0.2531a-28 Severity: minor The same typo occurs prominently on nearly forty manpages. Either 'apply' or 'applies' would be acceptable. With lapack-doc installed, the command 'apropos applie | grep -v applies' outputs a list of nearly forty afflicted manpages. It would be nice if this were fixed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410310: xview-clients: /usr/X11R6/bin/owplaces tries to exec 'xtoolplaces' which is not in debian
Package: xview-clients Version: 3.2p1.4-19 Severity: normal This package ships a short script (sarge) /usr/X11R6/bin/owplaces (etch) /usr/bin/owplaces The sarge version, at least, merely tries to exec 'xtoolplaces'. However, packages.debian.org lists no such file in either stable or testing. Package Contents Search Results You have searched for xtoolplaces in testing, architecture i386. Can't find that file, at least not in that distribution and on that architecture. Perhaps owplaces (which has no manpage) should just be removed? Assuming the package itself lives on, that is... :-) -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-3-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages xview-clients depends on: ii libc6 2.3.2.ds1-22sarge4GNU C Library: Shared libraries an ii libx11-6 4.3.0.dfsg.1-14sarge3 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14sarge3 X Window System miscellaneous exte ii xlibs 4.3.0.dfsg.1-14sarge3 X Keyboard Extension (XKB) configu ii xviewg 3.2p1.4-19XView shared libraries [libc6] -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410332: po-debconf: typo (seperate) in debconf-gettextize.1
Package: po-debconf Version: 1.0.8 Severity: minor Tags: patch s/seperate/separate/ I'm not sure if the manpage is the preferred form of modification, so I'm not sure the patch will help, but here it is... -- System Information: Debian Release: 4.0 147c147 are managed in seperate files to help translators. In the initial --- are managed in separate files to help translators. In the initial
Bug#410343: xserver-xorg-core: manpage Xorg(1) refers to non-existent files
Package: xserver-xorg-core Version: 2:1.1.1-15 Severity: minor Under SEE ALSO, the manpage /usr/share/man/man1/Xorg.1.gz refers to xorgconfig(1), xorgcfg(1) but those files don't seem to be in debian (stable or testing). (I searched on packages.debian.org, x86 architecture only.) Should those references be deleted? -- System Information: Debian Release: 4.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410361: videogen: package description and manual pages need updating for etch
Package: videogen Version: 0.32-3 Severity: important Tags: patch Since etch will release with Xorg (config file /etc/X11/xorg.conf) it seems quite important to update the package description and manual pages. I'm attaching patches for .control, videogen.1 and some_modes.1. I've taken most trouble with videogen.1, in order to - mention xorg.conf - remove useless SEE ALSO entries (not in sarge or etch) - add useful SEE ALSO entries - fix some bad grammar - make the formatting (bold vs italic) more standard, as specified in man(1). I hope all this will be helpful! (Dr) J S Bygott Oxford -- System Information: Debian Release: 4.0 --- control 2007-02-09 23:34:53.0 + +++ control.new 2007-02-09 23:37:08.0 + @@ -8,7 +8,7 @@ Maintainer: Bas Zoetekouw [EMAIL PROTECTED] Description: Create arbitrary-res modelines using hardware parameters Videogen is a small but nice utility to create modelines you can - insert into your XF86Config(-4) and fb.modes files. + insert into your xorg.conf, XF86Config(-4) and fb.modes files. . Modeline is created by telling the program the resolution you want and your video hardware parameters (maximum video adapter --- some_modes.12006-08-23 14:19:33.0 +0100 +++ some_modes.1.new2007-02-10 00:36:19.0 + @@ -1,22 +1,19 @@ .TH SOME_MODES 1 some_modes Szabolcs Rumi \ -*- nroff -*- .SH NAME -some_modes \- generate common Modelines for XFree86 and fbset +some_modes \- generate common Modelines for Xorg and fbset .SH SYNOPSIS .B some_modes .SH DESCRIPTION .B some_modes -is a wrapper for videogen(1). +is a wrapper for \fBvideogen\fP(1). It interactively asks the +user for monitor parameters. Then it prints commonly-used mode +lines for use with Xorg (or its predecessor, XFree86) and fbset. .P -It interactively asks the user about their monitor parameters. -Then it prints commonly-used mode lines for XFree86 and fbset. -.P -.SS CONFIGURATION FILE -The file ~/.videogen is used to store the user's input between +.SH FILES +The file \fI~/.videogen\fP is used to store the user's input between invocations. -.SS OPTIONS -None. .SH SEE ALSO -videogen(1),X(1), XF86Setup(1), xvidtune(1), kvideogen(1), xf86cfg(1) +videogen(1), Xorg(1), xorg.conf(5), xvidtune(1) .SH AUTHOR Szabolcs Rumi szrumi_at_axelero_dot_hu .SH COPYING --- videogen.1 2006-08-23 14:19:34.0 +0100 +++ videogen.1.new 2007-02-10 01:56:42.0 + @@ -1,15 +1,20 @@ .TH VIDEOGEN 1 videogen Szabolcs Rumi \ -*- nroff -*- .SH NAME -videogen \- generate Modelines for XFree86 servers +videogen \- generate Modelines for Xorg servers .SH SYNOPSIS +.HP 2 .B videogen -[\-v|\-q] [\-fb|\-nfb] [\-nv|\-nnv] [\-f=file|\-] [\-m=mode] -[\-mdc=n] [\-mhf=n] [\-mvf=n] [\-dvf=n] [\-hv=n] [\-vv=n] -[\-hfp=n] [\-hbp=n] [\-hsp=n] [\-vfp=n] [\-vbp=n] [\-vsp=n] +.RB [ \-v | \-q ] +.RB [ \-fb | \-nfb ] +.RB [ \-nv | \-nnv ] +[\fB\-f=\fP\fIfile\fP|\fB\-\fP] [\fB\-m=\fImode\fR] +[\fB\-mdc=\fIn\fR] [\fB\-mhf=\fIn\fR] [\fB\-mvf=\fIn\fR] [\fB\-dvf=\fIn\fR] +[\fB\-hv=\fIn\fR] [\fB\-vv=\fIn\fR] [\fB\-hfp=\fIn\fR] [\fB\-hbp=\fIn\fR] +[\fB\-hsp=\fIn\fR] [\fB\-vfp=\fIn\fR] [\fB\-vbp=\fIn\fR] [\fB\-vsp=\fIn\fR] .SH DESCRIPTION .B videogen -can be used to generate Modelines for XFree86 servers to reach the -highest possible vertical refresh (screen update) rate at all +generates Modelines for Xorg servers (or XFree86 servers) +to reach the highest possible vertical refresh rate at all resolutions, or to match the refresh rate you desire. As a new feature, it can obey the non-free NVidia driver's timing constraints. It can print the calculated results in the Linux framebuffer device @@ -30,10 +35,10 @@ the default (~/.videogen) or read from stdin which might be helpful if you want to call videogen from another program or from a script. .P -The general syntax rules are the following: the parameters can be specified +The general syntax rules are the following: parameters are specified using name=value pairs. The parameter names are matched in a case insensitive -manner. Blanks are optional. More name=value pairs can be specified on a single -line separated by ; characters. Any string after a # character is +manner. Blanks are optional. Multiple name=value pairs can be specified on a +single line separated by ; characters. Any string after a # character is treated as a comment up to the end of the line. .SS COMMAND LINE The command line options always override the parameters set in the @@ -45,40 +50,40 @@ configuration file variable counterparts (if present). .PD .TP -.I \-v +.B \-v .PD 0 .TP -.I \-q +.B \-q .TP -.I verbose=on|off -Turn on/off verbose output. FYI -q stands for quiet ;) +\fBverbose=on\fP|\fBoff\fP +Turn on/off verbose output. FYI \fB-q\fP stands for quiet ;) (default=on) .PD .TP -.I \-fb +.B \-fb .PD 0 .TP -.I \-nfb +.B \-nfb .TP -.I fbset=on|off +\fBfbset=on\fP|\fBoff\fP Turn on/off fbset (Linux framebuffer timings) mode
Bug#410169: debconf-doc: two typos in devconf-devel.7
Package: debconf-doc Version: 1.5.11 Severity: minor Tags: patch two typos, here's the patch: --- debconf-devel.7 2006-09-14 19:49:03.0 +0100 +++ debconf-devel.7.new 2007-02-08 08:57:04.0 + @@ -268,7 +268,7 @@ .TP .B TITLE string This sets the title debconf displays to the user. You rarely need to use -this commands since debconf can automatically generate a title based on +this command since debconf can automatically generate a title based on your package's name. .TP .B SETTITLE question @@ -323,7 +323,7 @@ .B BEGINBLOCK .TP .B ENDBLOCK -Some debconf frontends can display a number of question to the user at once. +Some debconf frontends can display a number of questions to the user at once. Maybe in the future a frontend will even be able to group these questions into blocks on screen. BEGINBLOCK and ENDBLOCK can be placed around a set of INPUT commands to indicate blocks of questions (and blocks can even be -- System Information: Debian Release: 4.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410168: debconf-doc: typo in debconf.7 (te)
Package: debconf-doc Version: 1.5.11 Severity: minor Tags: patch typo, patch attached -- System Information: Debian Release: 4.0 --- debconf.7 2006-04-29 02:10:58.0 +0100 +++ debconf.7.new 2007-02-08 10:11:42.0 + @@ -202,7 +202,7 @@ something. .P Once you have the database, you need to figure out how to make -te remote systems use it. This depends of course on the configuration of +the remote systems use it. This depends of course on the configuration of those systems and what database types they are set up to use. .P If you are using the LDAP debconf database, an entire network of debian
Bug#410202: klipper: improve package description?
Package: klipper Version: 4:3.5.5a.dfsg.1-5 Severity: minor The first part of the long package description is clumsy English, and a little bit wrong: klipper provides several additional features of the traditional clipboard functionality [...] (wrong because, if they are features *of*, they can't be *additional*. It currently sounds as if klipper is implementing an improved subset of the 'traditional' clipboard standard, whatever that is.) A minimum correction might be: klipper provides features beyond traditional clipboard functionality, like [...] klipper provides traditional clipboard functionality plus additional features, like [...] Mm, still a bit bureaucratic. I would recommend something more like this: klipper provides standard clipboard functions (cut and paste, history saving) plus additional features, like [...] I think one of the coolest features is smooth integration with X (the option to synchronise with X clipboard and X selection); if you agree, then you might even add that to the list of features, right after 'like'. If someone (without KDE) is looking around for a better clipboard than they've got, and reading the package descriptions, then it might be a factor. Thanks anyway for a nice package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410249: two typos in gnumeric.1
Package: gnumeric Version: 1.6.3-4 Severity: minor Tags: patch two typos/grammar glitches, patch attached (the patch changes six lines because of slightly changed word wrapping) best regards -- System Information: Debian Release: 4.0 --- gnumeric.1 2006-02-20 14:56:38.0 + +++ gnumeric.1.new 2007-02-08 20:59:35.0 + @@ -24,9 +24,9 @@ at the source code level by any competent programmer. The program can be started from the command line as \fBgnumeric\fR or -from one of the menus provided by underlying platform. When started on -the command line, \fBgnumeric\fR may be followed by the options listed -below and possibly the names files in various spreadsheet formats +from one of the menus provided by the underlying platform. When started +on the command line, \fBgnumeric\fR may be followed by the options listed +below and possibly the names of files in various spreadsheet formats which will then be opened immediately. For instance, the command: gnumeric myfile.gnumeric @@ -75,9 +75,9 @@ .TP .B \fB\-\-display=\fR\fIDISPLAY\fR X display to use, where DISPLAY has the form -machinename:Xdisplay.Screen. Note the machine displaying gnumeric must -have granted the machine running gnumeric the right to display (see -xhost). +machinename:Xdisplay.Screen. Note that the machine displaying gnumeric +must have granted the machine running gnumeric the right to display +(see xhost). .TP .B \fB\-\-screen=\fR\fISCREEN\fR
Bug#410123: klipper: clearing the clipboard does not clear the clipboard history
Package: klipper Version: 4:3.5.5a.dfsg.1-5 Severity: wishlist I think 'clear clipboard' should clear the clipboard history file. (Currently, the file is only cleared if one empties the clipboard and then saves the empty clipboard on program exit.) Suppose that, after using klipper for some days, user does two things: -- clears the clipboard -- changes from save clipboard contents to don't save Then user's old, already-saved clipboard remains on file at ~/.kde/share/apps/klipper/history2.lst and will happily remain there for months. This is unlikely to be what the user wanted to achieve. It's so unexpected that it should probably be considered a 'normal' bug. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages klipper depends on: ii kdelibs4c2a4:3.5.5a.dfsg.1-5 core libraries and binaries for al ii libacl12.2.41-1 Access control list shared library ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libattr1 2.4.32-1 Extended attribute shared library ii libaudio2 1.8-2 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libfam02.7.0-12 Client library to control the FAM ii libfontconfig1 2.4.2-1 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-21GCC support library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libpng12-0 1.2.15~beta5-1PNG library - runtime ii libqt3-mt 3:3.3.7-3 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-4 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes3 1:4.0.1-5 X11 miscellaneous 'fixes' extensio ii libxft22.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii zlib1g 1:1.2.3-13compression library - runtime klipper recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409942: please document alternate bind syntax in mount(8)
Package: mount
Version: 2.12r-16
Severity: normal
At the moment, neither mount(8) nor fstab(5) tells us how to do bind
mounts with fstab, or even that it's possible. We have to *guess* that
doing this in fstab works:
/some/old/dir /some/new/mountpoint ??? bind ??? ???
and it's not clear what is or isn't permitted for ???.
Please consider amending mount(8) so the options listed under -o include
something like this:
bind same as --bind (other mount options are silently ignored)
[...]
rbindsame as --rbind (other mount options are silently ignored)
Isn't it also time to update the SYNOPSIS in mount(8), now that linux
versions =2.4.0 will be standard ? I suggest adding two lines
like this:
mount { --bind | -o bind } olddir newdir
mount { --rbind | -o rbind } olddir newdir
or, possibly, just one line
mount { --bind | --rbind | -o bind | -o rbind } olddir newdir
Thanks for your work.
-- System Information:
Debian Release: 4.0
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409684: xsane: please avoid redisplaying eula with every failed startup
Package: xsane Version: 0.99+0.991-1 Severity: normal Under certain conditions, the click-through appears again and again, at each startup. I believe this to be a bug, because at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=132679 the author wrote The license dialog comes up once when the user runs a new version of xsane, it does not come up every time. Here's the situation: - USB scanner is plugged in and available, - user is not in group scanner, - user runs xsane for the first time. (Won't this happen to many users? It's a pretty reasonable scenario.) - User encounters the click-through, a little upsetting (#132679), but not too important. She clicks accept. Up pops Failed to open device `niash:libusb:004:006': Device busy. (Not a helpful message; see bug #409550. By contrast, if no scanner is plugged in, xsane produces a nice help button.) User clicks to exit the program, and fiddles around trying to get xsane to work. Unplugs and replugs the scanner. Tries different ports. Struggles with the documentation, tries some wrong things. She does the right thing, and adds herself to the group scanner - but without logging in and out, so it still doesn't work. Each time she tries xsane, she has to click through the licence again before getting the same error. The error is annoying enough. By now, the repeated licence click-through is upsetting and insulting. Result: this user's first exposure to xsane is exasperating, and her opinion of debian as a desktop goes down. I believe many users will share this experience. Please consider adjusting xsane, so the click-through is shown only once. Best wishes, (Dr) Jeremy Bygott Oxford -- System Information: Debian Release: 4.0 Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages xsane depends on: ii libatk1.0-0 1.12.4-1 The ATK accessibility toolkit ii libc6 2.3.6.ds1-8GNU C Library: Shared libraries ii libcairo2 1.2.4-4The Cairo 2D vector graphics libra ii libfontconfig12.4.2-1generic font configuration library ii libgimp2.02.2.13-1 Libraries necessary to Run the GIM ii libglib2.0-0 2.12.4-2 The GLib library of C routines ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface ii libieee1284-3 0.2.10-4 cross-platform library for paralle ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libpango1.0-0 1.14.8-4 Layout and rendering of internatio ii libpng12-01.2.15~beta5-1 PNG library - runtime ii libsane 1.0.18-5 API library for scanners ii libtiff4 3.8.2-7Tag Image File Format (TIFF) libra ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library ii libx11-6 2:1.0.3-4 X11 client-side library ii libxcursor1 1.1.7-4X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxi61:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1X11 Xinerama extension library ii libxrandr22:1.1.0.2-5X11 RandR extension library ii libxrender1 1:0.9.1-3 X Rendering Extension client libra ii xsane-common 0.99+0.991-1 GTK+-based X11 frontend for SANE ( ii zlib1g1:1.2.3-13 compression library - runtime -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409742: setting win95 in winecfg does not seem to set correct path
Package: wine Version: 0.9.25-1 Severity: normal 1. Overview I'm trying to use wine to run programs from an existing win95 install. (Win 95 version 4.00.950B, OEM SR2.1 with USB supplement, to be precise.) The documentation suggests it will work, see e.g. http://www.winehq.org/site/docs/wine-faq/index#IF-I-USE-WINDOWS-WHICH-VERSIONS-OK But selecting win95 in winecfg seems not to do the right thing. I get Warning: the specified System directory Lc:\\windows\\system32 is not accessible. Could not load 'VBRUN300.DLL' required by 'OB', error=2 and indeed, system32 isn't part of a win95 system. Wine should probably be looking in c:\\windows\\system, though this needs checking. jsb:~/.wine/dosdevices/c:/windows$ find * | grep -i vbrun system/vbrun300.dll I guess I should set WINEDLLPATH ? But my point is, shouldn't selecting win95 set the necessaries up correctly to allow an existing win95 to work? That's why I think this is a bug. Best wishes, etc Jeremy 2. Details: - debian on /dev/hda - old win95 hard disk on /dev/hdd, mounted at /media/b - grub to dual boot I've had to move the win95 disk to newer hardware, and while it just about made it through the motherboard upgrade, with some hand-holding (there's the delightful amd-k6 issue... see footnote) some drivers aren't available etc, leaving me stuck with clunky vga. Debian/wine would be the best solution. jsb:~$ rm -rf .wine/ jsb:~$ winecfg Invoking /usr/lib/wine/wine.bin winecfg.exe ... wine: creating configuration directory '/home/jsb/.wine'... Failed to open the service control manager. wine: '/home/jsb/.wine' created successfully. [Okay, that bit about service control manager is a bit worrying. I saw somewhere that upstream was worried that debian users often break wine by not installing enough pieces. But anyway, let's continue...] winecfg has opened on the applications tab, so we set windows version to windows 95 and click apply. On the audio tab, click ALSA driver, apply. Now the drives tab. We remove Z: (pointing to /). We click on C: and change the path from ../drive_c to /media/b. We click apply. ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory err:winecfg:on_remove_click unixpath: / Wine exited with a successful status [Mm, sound needs fixing; again, have I got enough of wine? Let's carry on, trying a simple game, maybe no dll needed:] cd .wine/dosdevices/c:/games/same jsb:~/.wine/dosdevices/c:/games/same$ wine Same.exe Invoking /usr/lib/wine/wine.bin Same.exe ... Warning: the specified System directory Lc:\\windows\\system32 is not accessible. Warning: the specified System directory Lc:\\windows\\system32 is not accessible. ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory Warning: the specified System directory Lc:\\windows\\system32 is not accessible. [Okay, the messages are tedious, but the same game looks right, plays nicely, and writes to the high score table. Fine. Very impressive. But:] jsb:~/.wine/dosdevices/c:/games/ob$ wine ob.exe Invoking /usr/lib/wine/wine.bin ob.exe ... Warning: the specified System directory Lc:\\windows\\system32 is not accessible. Warning: the specified System directory Lc:\\windows\\system32 is not accessible. ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory Could not load 'VBRUN300.DLL' required by 'OB', error=2 Wine exited with a successful status jsb:~/.wine/dosdevices/c:/windows$ find * | grep -i vbrun system/vbrun300.dll It looks as if win95 looks in the wrong places, at least by default. If I run regedit and change system32 to system in the path, the program starts. [It doesn't get far, but that's another story:] fixme:int31:DPMI_CallRMProc DPMI real-mode call using DOS VM task system, not fully tested! Warning: unprotecting memory to allow real-mode calls. NULL pointer accesses will no longer be caught. [Bah, software validation. A paid-for program is now unusable because of a motherboard failure. I can't wait for win to fix this fixme!] 3. Footnote The amd-k6 issue? Win95 won't boot, not even safe mode, on CPUs that are too fast (!) and the ms tool that fixes it requires windows (!!) Solution: use cabextract under debian and put the files in the right place yourself, then boot win, then run the tool to complete the update to the registry. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages wine depends on: ii debconf [debconf-2.0]1.5.11 Debian configuration management sy ii libwine 0.9.25-1Windows API Implementation (Librar ii
Bug#409550: xsane: please try to improve device busy error message
Package: xsane Version: 0.99+0.991-1 Severity: important You install debian gnu/linux for a friend, but forget to make her part of the scanner group. She plugs in her USB scanner and runs xsane. Error: Failed to open device `niash:libusb:004:006': Device busy. This may, perhaps, be good enough for a command line tool like scanimage. But for a gui, it's downright misleading. Is it possible to improve it? Maybe something like [...] Device busy. Do you have sufficient access rights? [...] Either the device is busy or you do not have access permissions. Or, if you prefer, something more explicit, like Are you a member of the 'scanner' group? But only if that is likely to be general enough for users with different setups. It would be great if you get some minimum string change like that into etch, still. It would significantly help many inexperienced users, and lower the support burden on others. Hence my view that this is important. If you don't like those suggestions, you could try pointing to a likely place in the documentation. The answer is obvious if you know it, but otherwise it's buried quite deep. At the moment, you'd have to say something like Try man sane(7) and read the PROBLEMS section. It's no good trying man xsane, for instance, or looking in /usr/share/doc/xsane/html/. (Is there a good reason why the index file isn't called index.html but rather sane-xsane-doc.html ? If you open the directory in a gui like konqueror, with reasonably large icons, it's not obvious where to start, and the first two pages don't link back to the index page, so it isn't even obious that there is an index.) Actually, it might be good to add a short paragraph about device busy and permissions to /usr/share/doc/xsane/html/sane-problems-doc.html and then you could point to that file. In that paragraph, mention the need to log in again after being added to the group; it isn't enough just to replug the scanner. For lenny (wishlist) it would be nice to have something more intelligent. For example (if saned is not involved) the normal mechanism is the group scanner, isn't it? So you could *check* if the user is in that group, and then output something like: [...] Device busy. Do you have access rights? You do not seem to be a member of the scanner group. Many thanks for the package, by the way. I've found the colour correction correction options very useful with newspaper articles. And that was the sarge version! So I'm looking forward to using the etch version... -- System Information: Debian Release: 4.0 Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages xsane depends on: ii libatk1.0-0 1.12.4-1 The ATK accessibility toolkit ii libc6 2.3.6.ds1-8GNU C Library: Shared libraries ii libcairo2 1.2.4-4The Cairo 2D vector graphics libra ii libfontconfig12.4.2-1generic font configuration library ii libgimp2.02.2.13-1 Libraries necessary to Run the GIM ii libglib2.0-0 2.12.4-2 The GLib library of C routines ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface ii libieee1284-3 0.2.10-4 cross-platform library for paralle ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libpango1.0-0 1.14.8-4 Layout and rendering of internatio ii libpng12-01.2.15~beta5-1 PNG library - runtime ii libsane 1.0.18-5 API library for scanners ii libtiff4 3.8.2-7Tag Image File Format (TIFF) libra ii libusb-0.1-4 2:0.1.12-2 userspace USB programming library ii libx11-6 2:1.0.3-4 X11 client-side library ii libxcursor1 1.1.7-4X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxi61:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1X11 Xinerama extension library ii libxrandr22:1.1.0.2-5X11 RandR extension library ii libxrender1 1:0.9.1-3 X Rendering Extension client libra ii xsane-common 0.99+0.991-1 GTK+-based X11 frontend for SANE ( ii zlib1g1:1.2.3-13 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409125: guarddog: please add 'git' protocol
Package: guarddog Version: 2.5.0-1 Severity: wishlist Please consider adding the git protocol http://www.linux-mips.org/wiki/Git so one can just enable it without learning the details. Thanks for the good work. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages guarddog depends on: ii gawk 1:3.1.5.dfsg-4GNU awk, a pattern scanning and pr ii kdelibs4c2a4:3.5.5a.dfsg.1-5 core libraries and binaries for al ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libaudio2 1.8-2 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libfam02.7.0-12 Client library to control the FAM ii libfontconfig1 2.4.2-1 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-21GCC support library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libpng12-0 1.2.15~beta5-1PNG library - runtime ii libqt3-mt 3:3.3.7-3 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-4 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft22.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii zlib1g 1:1.2.3-13compression library - runtime guarddog recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408931: gstreamer0.10-tools: typo in package description (versionned)
Package: gstreamer0.10-tools Version: 0.10.10-2 Severity: minor s/versionned/versioned/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409015: kword crashes, language choosing broken
Package: kword Version: 1:1.6.1-2 Severity: important The choosing of language for spelling checking seems quite broken. Especially in kword, which doesn't choose from the installed languages and can easily be made to crash. Details below. Severity seems Important at least. It would be sad if etch were released with kedit/word in this state. I think it would be bad for debian. One of the strengths of debian and kde is support for multiple languages. For many users, it is *important* to be able to switch rapidly between languages, even within the same document. (Suppose you are developing materials for foreign language teaching. Or writing essays with long quotations in other languages. Or writing business emails to foreign customers. Or...) For this reason, I don't agree at all with bug #404683. It isn't possible to have a per-document language setting in the cases above. kwrite does the right thing, kudos! (step 4 below) Moreover, it looks as if the intention is to integrate this feature across kde: to kmail, kedit, ... and maybe kword (I can't tell, it's so broken). That would be wonderful. Alas, the feature is bugged in kedit (step 5 below). And badly broken in kword (step 6 below). Details: 0. Start with desktop system recently upgraded from sarge to etch. Install several dictionaries, including in my case ibritish, ingerman. This test example will use those two languages. 1. Create a new user account with no settings at all (to try and eliminate the possibility of bad settings left behind from before upgrade to etch). From kdm, start a KDE session for this new user. Click through the new desktop wizard, accepting (in my case) default country United Kingdom, default language British English. 2. control centre - KDE components - spell checker The drop-down tab says ispell default. Change this to Unknown [ngerman], encoding 8859-1. Apply. Quit. (BUG: the name should be better than this. End-users will not be impressed that they have to pick unknown dictionaries.) 3. k - utilities - editors - kwrite Save a file test containing some text in the two languages: An English sentence. Und ein deutscher, möglichst mit Umlaut. 4. On the kwrite menu bar, click tools - spelling. The tab correctly shows Unknown [ngerman], respecting the setting made at step 2. The program correctly offers to change English into Englisch. Click on the language tab and change to English [british]. Click okay (You have to restart the dialogue for changes to take effect) On the kwrite menu bar, again click tools - spelling. The tab respects the change of language; the program offers to change Und (to Fund). This is correct behaviour, very good. It makes it highly practical to check spelling for documents in more than one language. (Moreover, control centre will respect the change of default language - this is good integration.) Quit kwrite. 5. k - utilities - editors - kedit Open file test saved at step 3. On the kedit menu bar, click tools - spelling. The tab shows british, the program objects to Und. Correct so far. Click on the language tab and change to Unknown [ngerman]. Click okay (You have to restart the dialogue for changes to take effect) On the kedit menu bar, again click tools - spelling. BUG: The tab shows the changed language (ngerman), but the program is still using the previous value (british). TWO WORKAROUNDS: -- quit and restart kedit -- click settings - configure kedit - spelling - okay Both are too clumsy for serious work in production environments. (As for quit-and-restart in kmail-composer... a hopeless approach). It gets worse. 6. k - office - kword import file test (filter locale [8859-1]) click on spellcheck button (or click tools - spellcheck - spelling...) BUG: The languages shown in the language tab are not related to the installed languages. ingerman does not show up at all. I have a list of about 29 entries matching regexp en.* (en_GB and so on) and at the end an entry he (for Hebrew, which I've never installed). It isn't at all clear whether kword is trying to integrate with the rest of kde or not. Personally, I think it should behave like kwrite. click he, then ignore to advance the checking to the next word... BUG: kword crashes with signal 6 (SIGABRT) I attach a backtrace, in case it helps, but the bug seems perfectly reproducible. I also notice a snippet (similar to the attached) at the end of ~./xsession-errors [Perhaps this should be split into several bugs? Or assigned to some kde metapackage? But kword is the worst affected.] -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of
Bug#408837: xcursor-themes: please clarify package description
Package: xcursor-themes Version: 1.0.1-5 Severity: wishlist Please consider clarifying the package description. (Policy 3.4: describe it to a user (system administrator) who has never met it before so that they have enough information to decide whether they want to install it). I've just done a sarge - etch upgrade and I'm now removing dummy packages. One such is xlibs-data. The description says it's safe to remove it, but if I do, then xcursor-themes will disappear as well (auto-dependency). Is that okay? The description doesn't help me decide. No (non-dummy) package in etch seems to depend on, or even suggest, xcursor-themes, but I would expect X to need _some_ cursors. Are the themes merely additional, optional themed cursors, not needed for a working X? (In other words, does X contain some even more basic cursors built in?) Currently, in the short description base X cursor themes, the word base (and the fact that they came from a pretty core X package before the transition) suggests that they are needed, the word themes suggests not. The long description doesn't help. [Maybe, to an X developer, base X means part of X11 since the year dot. But to the rest of us, it could mean fundamental, important.] If they are in fact optional, perhaps the package description could be something more like this? Traditional X cursor themes (handhelds, redglass, whiteglass) for use with the Xcursor library. They used to be part of the xlibs-data package. They are now packaged separately because most users only need the standard cursors built into X. Please see libxcursor1 for more information. OR, if they do matter, something like this? Base X cursor themes (handhelds, redglass, and whiteglass) for use with the Xcursor library. Most X installations require this package to ensure that at least some cursors are available. These cursors used to be part of the xlibs-data package. Please see libxcursor1 for more information. Regards, (Dr) J S Bygott -- System Information: Debian Release: 4.0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408857: dfontmgr: does not quit cleanly
Package: dfontmgr Version: 0.11.10 Severity: normal Experienced within kde from etch(testing). I can reproduce this every time. 1. $ dfontmgr 2. click tab application a list of applications is shown, eg fontconfig, gs, psfontmgr, libwmf0.2-7, pango, x-ttcidfont-conf 3. click on any application name *except the first*, eg pango 4. click file - quit wolfgang:~$ dfontmgr Attempt to free unreferenced scalar: SV 0x88cbed4, Perl interpreter: 0x814e008 during global destruction. Attempt to free unreferenced scalar: SV 0x88d1114, Perl interpreter: 0x814e008 during global destruction. Attempt to free unreferenced scalar: SV 0x88cc1ec, Perl interpreter: 0x814e008 during global destruction. Attempt to free unreferenced scalar: SV 0x88cc168, Perl interpreter: 0x814e008 during global destruction. Attempt to free unreferenced scalar: SV 0x88cc0e4, Perl interpreter: 0x814e008 during global destruction. Attempt to free unreferenced scalar: SV 0x88cc060, Perl interpreter: 0x814e008 during global destruction. Attempt to free unreferenced scalar: SV 0x88cbf04, Perl interpreter: 0x814e008 during global destruction. wolfgang:~$ -- System Information: Debian Release: 4.0 Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages dfontmgr depends on: ii defoma0.11.10Debian Font Manager -- automatic f ii libft-perl1.2-16 Perl module for the FreeType libra ii libglade-perl 0.61-1 Glade-perl runtime modules ii libgtk-perl 0.7009-12 Perl module for the gtk+ library ii perl 5.8.8-7Larry Wall's Practical Extraction dfontmgr recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408418: suggestions for documenting startup behaviour (kdmrc)
Package: kdm Version: 4:3.5.5a.dfsg.1-5 Severity: normal Tags: patch This is about the behaviour new in etch (the overrides to kdmrc). Please consider the suggestions below. Judging by the number of related bugs (eg #403776, #403797, #406438, #406939) it would help many people. These suggestions would have saved me a whole morning. (1) I propose adding a prominent comment to /etc/kde3/kdm/kdmrc (see patch1). The reason for putting the comment in this file and right at the top is twofold. Firstly, users who are upgrading will be used to editing the so-called master configuration file. They will not expect overrides. This helps to clarify the prominent word master. I realize that kdm *if started directly* won't ignore values in kdmrc. But most people start it the default way, via the scripts /etc/init.d/kdm. And so kdmrc will be where people will look. They will not look in /usr/share/doc/kdm until *after* they have wasted a lot of time investigating this issue. See the various bugs in the BTS. This way, upgraders will have half a chance of seeing it with dpkg's conffile handling, and otherwise, they'll see it when editing kdmrc. [It is a pity that the gui-frontend deletes comments, so I endorse bug http://bugs.kde.org/show_bug.cgi?id=86650 whole-heartedly.] (2) I propose clarifying the README.Debian (see patch2) Reason: the existing text can be misunderstood when reading carelessly. It looks a bit like we provide a way of customizing kdm [...] in kdmrc in other words, the way to override kdm builtin defaults is in kdmrc. Also, I have fixed a typo. (The past participle of ride is ridden.) (3) I propose fixing the same typo in /etc/init.d/kdm (see patch3) Many thanks for all your debian work. I hope this helps. Best wishes, (Dr) Jeremy Bygott -- System Information: [deleted: I'm writing from sarge; reportbug seems broken on my etch system] --- /etc/kde3/kdm/kdmrc.supplied2006-12-29 20:25:12.0 + +++ kdmrc.improved 2007-01-25 16:57:08.0 + @@ -1,5 +1,11 @@ # KDM master configuration file # +# Please note: settings in this file are sometimes ignored (overridden). +# The default KDM startup script /etc/init.d/kdm looks in /etc/defaults/kdm.d +# for theme-related settings which, if found, take precedence. The possibly +# overridden settings are: UseBackground, BackgroundCfg, UseTheme, Theme. +# See /usr/share/doc/kdm/README.Debian for details. +# # Definition: the greeter is the login dialog, i.e., the part of KDM # which the user sees. # --- /usr/share/doc/kdm/README.Debian2006-12-29 19:50:41.0 + +++ README.Debian.improved 2007-01-25 17:05:02.0 + @@ -16,7 +16,7 @@ KDM Customization = -We provide a way to customize KDM by overriding theme related values in +We provide a way to override theme-related values normally set in the master configuration file (kdmrc): * USEBACKGROUND * BACKGROUNDCFG @@ -26,8 +26,8 @@ and background configuration file (backgroundrc): * WALLPAPER -You just need to create a file with overrided value(s) and put it in -kdm override directory (default is /etc/default/kdm.d). +You just need to create a file with override value(s) and put it in +the kdm override directory (default is /etc/default/kdm.d). Below this is direct from the xdm package README --- /etc/init.d/kdm 2006-12-29 19:50:41.0 + +++ kdm.improved2007-01-25 17:09:03.0 + @@ -57,7 +57,7 @@ # we generate kdm configuration files genkdmconf --in $KDMCFGDIR 1 /dev/null -# we update kdm configuration files (only overrided values) +# we update kdm configuration files (only overridden values) [ -n $USEBACKGROUND ] sed -i s|^#\?UseBackground=.*|UseBackground=$USEBACKGROUND| $KDMCFG [ -n $BACKGROUNDCFG ] sed -i s|^#\?BackgroundCfg=.*|BackgroundCfg=$BACKGROUNDCFG| $KDMCFG [ -n $USETHEME ] sed -i s|^#\?UseTheme=.*|UseTheme=$USETHEME| $KDMCFG
Bug#408469: ca-certificates: broken postrm
Package: ca-certificates Version: 20061027 Severity: serious Justification: Policy 6.2 (sometimes interacts non-idempotently), 3.9 (error (missing dir) not checked for), 6.8 (removes files at wrong time) The postrm, called with remove, changes into a directory that does not always exist. The results are unpleasant. 1. if you try to remove the package when /etc/ssl/certs is empty, remove fails, because dpkg removes the dir before postrm is called 2. if you removed but did not purge (typical within aptitude, because such packages as openoffice.org-core pull you in automatically) and later try to remove or purge again, remove/purge fails. I believe you MUST be able to remove a package more than once, idempotently (policy 6.2), but currently, you cannot. Hence I think the bug is serious. (Apologies if I'm wrong about that.) For example, dpkg can't always remove the package if brokenly installed. Encountered during sarge - etch upgrade error recovery: wolfgang:~# dpkg -r ca-certificates (Reading database ... 114332 files and directories currently installed.) Removing ca-certificates ... /var/lib/dpkg/info/ca-certificates.postrm: line 21: cd: /etc/ssl/certs: No such file or directory dpkg: error processing ca-certificates (--remove): subprocess post-removal script returned error exit status 1 Errors were encountered while processing: ca-certificates Possible solutions: 1. in postrm, check if dir exists before cd; or 2. create a prerm and remove the hash symlinks there The second seems more in keeping with policy 6.8: the prerm should do the cleanup, then dpkg can remove the dir /etc/ssl/certs listed in *.list (and we won't get warnings about dir not empty) Perhaps the dir is only empty if you answer the template question the same way I did? It might explain why this hasn't been noticed before. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403220: aptitude-doc-en: bugs in manual and changelog
Package: aptitude-doc-en Version: 0.4.3-1 Severity: minor Thanks for a useful manual. A few small bugs from the sarge version (0.2.15.9) are still present in 0.4.3-1 ch01s01s04.html quote in the screen shot below, the kaffeine package was selected and + was pushed /quote correction: s/kaffeine/kaffeine-mozilla/ ch02s02s03.html In the box describing Reinstall: press L, we have quote when you quit aptitude or perform an install run for technical reasons. (essentially, /quote Corrections: - insert a comma after install run (you don't perform the install run for technical reasons; the comma is needed for correct grouping) - delete full stop after reasons fulfil or fulfill? Here in the UK, fulfil is the correct spelling. That will be true for readers in many parts of the world. I believe US English accepts both fulfil and fulfill. If that is so, you could make the change s/fulfill/fulfil/ in a couple of places, at least: ch02s02s02.html: fulfill the dependency. These versions can be manipulated ch02s04s05.html: spanb class=commandaptitude/b/span will automatically attempt to fulfill There is a changelog bug for (unstable) version 0.4.4-1 - Translation updates: * Basque (Closes: #38973) Surely 38973 should be 389730 ;-) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=38973 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389730 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403054: typos in /etc/dictd/dictdconfig.alias
Package: dictd Version: 1.10.2-3 Severity: minor Tags: patch Two typos: in a command name, and in a path (Also present in sarge version 1.19.15-1) --- dictdconfig.alias.1.10.2-3 2006-12-14 11:51:35.822879000 + +++ dictdconfig.alias.corrected 2006-12-14 11:53:15.010800336 + @@ -1,9 +1,9 @@ #!/usr/bin/perl -lp -# By default, dictdcnfig uses the basename of the file in +# By default, dictdconfig uses the basename of the file in # /usr/share/dictd as the name of the database. This file is an # executable filter that substitutes a preferred name for a dictionary -# in /var/lb/dictd/db.list. This name is displayed by the dict -D +# in /var/lib/dictd/db.list. This name is displayed by the dict -D # command and is used with the -d option of dict to request # definitions from a specific dictionary instead of the default of all # installed dictionaries.
Bug#403067: scowl: british wordlists require practice and practise
Package: scowl Version: 6-2 Severity: normal wbritish-* is wrong about practice american-words.10: practice, practice's american-words.20: practiced, practices, practicing british-words.10: practise, practise's british-words.20: practised, practises, practising The British entry is wrong. I'm not familiar with how scowl generates the lists, but surely final/british-words.10 needs to include practice, practice's (noun) and practise (verb). It must be wrong to include practise's, certainly at level 10, probably at any level. Is it possible except in highly artificial sentences? It is practise's misfortune to be a verb spelt differently from the related noun. [I suspect Canadian follows British English here, but I'm not sure.] From scowl-6/README: Great care has been taken so that that only one spelling for any particular word is included in the main list. Fine, but the principle needs to be applied correctly, a bit like: american-words.10 : check, checks british-words.10: check, checks, cheque, cheques -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403097: kmix: show/hide menubar does not toggle state correctly
Package: kmix Version: 4:3.3.2-1 Severity: normal How to reproduce the bug: 0. Start kmix with default settings. 1. Using the mouse, click menubar - settings - hide menubar 2. The menubar is gone. Now we try to show it again. 3. Right-click in mixer area, the context menu still says hide when it should say show (strange!) but click on hide anyway. 4. The menubar returns, but menubar - settings now says show menubar even though the menubar *is* shown. To restore the correct status, repeat the process. Anaylsis: When the menubar is showing, there are three ways to hide it: H1) right-click in mixer area - settings - hide H2) click menubar - settings - hide H3) ctrl+m When the menubar is hidden, there are two ways to show it: S1) right-click in mixer area - settings - show S2) ctrl+m It seems that only H1 and S1 actually toggle the name of the option between show and hide. So it is easy to get into the wrong state by mixing, for example, H2 and S1 I think the bugfix must be for all methods to toggle the name of the option. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-3-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kmix depends on: ii kdelibs4 4:3.3.2-6.4 KDE core libraries ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libasound2 1.0.8-3 ALSA library ii libc6 2.3.2.ds1-22sarge4GNU C Library: Shared libraries an ii libfam0c1022.7.0-6sarge1 client library to control the FAM ii libgcc11:3.4.3-13sarge1 GCC support library ii libice64.3.0.dfsg.1-14sarge2 Inter-Client Exchange library ii libidn11 0.5.13-1.0GNU libidn library, implementation ii libpng12-0 1.2.8rel-1PNG library - runtime ii libqt3c102-mt 3:3.3.4-3sarge1 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-14sarge2 X Window System Session Management ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14sarge2 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14sarge2 X Window System miscellaneous exte ii libxrender10.8.3-7 X Rendering Extension client libra ii xlibs 4.3.0.dfsg.1-14sarge2 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401782: dict-gcide: typo in package description (sever)
Package: dict-gcide Version: 0.48-4 Severity: minor There's a typo in the package description displayed by aptitude. Not good for a dictionary! ;-) s/sever/server/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399060: imagemagick: convert -draw fails when filenames start with a digit
Package: imagemagick Version: 6:6.0.6.2-2.7 Severity: normal The parsing of convert -draw commands is a bit broken. One example is bug #344801. But the bug affects convert -draw much more generally. For example, let's make a nice circle: $ touch 1.gif $ convert -size 200x200 -fill blue -draw 'circle 50,50 0,50' 1.gif 1.gif Now, we want two circles: $ convert -draw 'image Over 100,100 200,200 1.gif' 1.gif 2.gif convert: Non-conforming drawing primitive definition `image'. This is a bug! There is a workaround: try a different filename. $ cp 1.gif a.gif $ convert -draw 'image Over 100,100 200,200 a.gif' a.gif 2.gif -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-3-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages imagemagick depends on: ii libmagick6 6:6.0.6.2-2.7 Image manipulation library -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362623: adduser: deluser(8) manpage typos and suggestions
Package: adduser Version: 3.85 Severity: minor Tags: patch This applies to both stable (version 3.63) and testing (version 3.85). There are some typos (an user -- a user etc). Also, I suggest adding DIR to the synopsis (--backup-to DIR). I suggest changing setup (copied from adduser) to cleanup. Finally, I suggest a simpler version of the warning. Patch follows diff -u deluser.8 deluser.8.new patch --- deluser.8 2006-04-14 16:06:53.0 +0100 +++ deluser.8.new 2006-04-14 16:25:42.0 +0100 @@ -10,7 +10,7 @@ .SH NAME deluser, delgroup \- remove a user or group from the system .SH SYNOPSIS -.BR deluser [options] [\-\-remove-home] [\-\-home DIR] [\-\-remove-all-files] [\-\-backup] [\-\-backup-to] user +.BR deluser [options] [\-\-remove-home] [\-\-home DIR] [\-\-remove-all-files] [\-\-backup] [\-\-backup-to DIR] user .PP .BR deluser \-\-group [options] group .br @@ -76,7 +76,7 @@ If the file .B /usr/local/sbin/deluser.local exists, it will be executed after the user account has been removed -in order to do any local setup. The arguments passed to +in order to do any local cleanup. The arguments passed to .B deluser.local are: .br @@ -87,17 +87,16 @@ .BR deluser is called with the \-\-group option, or delgroup is called, a group will be removed. -Warning: If any users have the group to be removed as primary group -the group cannot be removed. +Warning: The primary group of an existing user cannot be removed. If the option .B \-\-only-if-empty is given, the group won't be removed if it has any members left. -.SS Remove an user from a specific group +.SS Remove a user from a specific group If called with two non-option arguments, .B deluser -will remove an user from a specific group. +will remove a user from a specific group. .SH OPTIONS .TP .B \-\-conf FILE @@ -117,7 +116,7 @@ .TP .B \-\-system Only delete if user/group is a system user/group. This avoids -accidentally deleting non-system user/groups. Additionally, if the +accidentally deleting non-system users/groups. Additionally, if the user does not exist, no error value is returned. This option is mainly for use in Debian package maintainer scripts. .TP
Bug#362670: hdparm(8) refers to 2.0 kernels as current
Package: hdparm Version: 6.1-2 Severity: wishlist Quite early in the manpage we read some options may work correctly with only the latest kernels and then in the current kernel (2.0.10) [...] This makes it difficult for a learner to get involved: it isn't clear how much of the manpage to trust, or even whether the package is relevant nowadays or legacyware. It would be helpful if a knowledgeable person could update those bits of the manpage. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-3-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362017: kxkb: layout tab reset button has strange effect
Package: kdebase-bin Version: 4:3.3.2-1sarge1 Severity: normal This bug may be related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361733 I shall describe how to reproduce the bug on a new user account (for which kxkb has never been run). (1) start Control Centre -- Regional Accessibility -- Keyboard Layout (2) The keyboard layout module opens with the layout tab active. Note that keyboard layouts are not enabled, so most of the tab is greyed out. You can see that the greyed-out defaults are: keyboard model: Generic 104-key PC active layouts: U.S. English (us) (3) click to enable keyboard layouts; the main box becomes active (not greyed-out) (4) click reset in the bottom right; the main box becomes greyed-out, but you can see the U.S. English keyboard listed *twice* on the right Each time you repeat (3)-(4), the list gets longer by one entry. This behaviour is a bug. Variation: say you already have layouts enabled and there are two layouts on the list. (3a) click to disable layouts (4a) click reset : now your list is two layouts longer! -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-3-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kdebase-bin depends on: ii kdelibs4 4:3.3.2-6.4 KDE core libraries ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libfam0c1022.7.0-6sarge1 client library to control the FAM ii libgcc11:3.4.3-13GCC support library ii libice64.3.0.dfsg.1-14sarge1 Inter-Client Exchange library ii libidn11 0.5.13-1.0GNU libidn library, implementation ii libpam-runtime 0.76-22 Runtime support for the PAM librar ii libpam0g 0.76-22 Pluggable Authentication Modules l ii libpng12-0 1.2.8rel-1PNG library - runtime ii libqt3c102-mt 3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-14sarge1 X Window System Session Management ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14sarge1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14sarge1 X Window System miscellaneous exte ii libxrender10.8.3-7 X Rendering Extension client libra ii libxtst6 4.3.0.dfsg.1-14sarge1 X Window System event recording an ii xlibs 4.3.0.dfsg.1-14sarge1 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362030: kdebase-bin: kxkb: improve keyboard layouts explanation (and functionality?)
Package: kdebase-bin Version: 4:3.3.2-1sarge1 Severity: wishlist I think you can improve the GUI to make it more intuitive and the handbook to explain things better. Any maybe you can add functionality. Let me first say that there are many things I like about kxkb: -- country flags to show the current layout (or err if there is an error) -- kxkb shows the setxkbmap command line (useful for learning/debugging!) -- you can set up more than four layouts (does anyone use this feature?) -- you can switch keyboard layouts per-application or per-window. Now come my criticisms. The xkb options don't work. Actually, they work very well, but they don't do what users may reasonably expect. If I understand things correctly, there are two ways to change keyboard layouts, the native X way and the KDE way. Co-operation between the two is restricted in ways the user may not expect. In particular, it is easy to get the impression that the xkb group switching options (shift keys, LED indicators) can be set up to switch the layouts selected in the kxkb layout tab. So it looks as if the group switching doesn't work. I know that I got this impression. From the discussion at refs [1] and [2] it looks as if Vassilii got this impression. I conclude that many less skilful people will give up in disappointment, and even those who succeed will suffer frustration along the way. It took me several hours to figure out the details, and I had to learn more about keyboards than I ever wanted. [1]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=257984 [2]http://bugs.kde.org/show_bug.cgi?id=84606 I think we can do better than X and KDE are different products[2]. I have three proposals. I will try to keep them short, because I am stuck with Debian Sarge (kdebase-bin 3.3.2-1sarge1) so I don't know if things have improved already. (1) Make the GUI clearer In the tab xkb options the heading Group Shift/Lock behaviour is cryptic for non-experts. Change it to something like Group switching (for switching xkb groups within the current layout, eg latin cyrillic) (2) Make kxkb handbook clearer Include an early section on when *NOT* to use keyboard layouts. Users of Win9x may think there is no other way. Encourage the user to learn keystrokes on their default layout. Explain the powerful concept of deadkeys. Maybe point to a suitable webpage or include a lengthy appendix. Definitely give examples. Eg if you live in the UK, you probably have a Generic 105-key (intl) PC keyboard with layout gb. Then you can do: (acute accent) AltGr + ; followed by a,e,i,o,u,A,E,I,O,U (circumflex)AltGr + ' followed by a,e,i,o,u,A,E,I,O,U (grave accent) AltGr + # followed by a,e,i,o,u,A,E,I,O,U (German Umlaut) AltGr + [ followed by a,e,i,o,u,A,E,I,O,U (German Esszett)AltGr + s (tilde) AltGr + ] followed by vowel or n And please tell me how to do c-cedilla! [Tranlators of the kxkb handbook should be encouraged to include a suitable example for their locale.] Only *then* explain *how* to use keyboard layouts. Include something like my paragraph above (there are two ways to change keyboard layouts, the native X way and the KDE way. Co-operation between the two is restricted in ways the user may not expect). Maybe give a bit of detail of the two mechanisms: native X -- the X server knows up to four layouts -- can toggle between them using group switching commands, which can be bound to various shift keys etc -- can use keyboard LEDs as indicators KDE -- each user can set up one or more layouts -- can switch using mouse click or keystroke (default: ctrl+alt+k) -- keyboard indicator in panel -- can maintain separate keyboard settings per application or per window Explain (assuming this is true!!) that in order to provide this fine-grained control, KDE sends a new setxkbmap command every time the user changes to a new application or window. This is the commandline shown in the layout tab. Explain that you can select many layouts in KDE, but at any given time, X knows about only one layout (or two if you clicked include latin layout). So if you pick two separate kxkb layouts, group switching will have no effect. If you pick one layout (eg a cyrillic one) and click on include latin layout, then as far as KDE is concerned you have one layout (one country flag) but you can toggle using the xkb options. (3) Add functionality? I live in Britain and have a British keyboard. So for me, include latin layout doesn't work very well, because it should include gb not us. A real-world example: Anna's physical keyboard is British, but she wants to type lots of German. She learnt to touch-type in Germany. It is far quicker for her to use a German layout and type ; for ö rather than using the British layout with Umlaut-deadkey combinations. But sometimes (for rarer punctuation and stuff) she wants to look at the keyboard and toggle back to the British layout. She needs a win-key toggle or similar, rather than mouse
Bug#361686: xscreensaver: pong(6x) manpage typos
Package: xscreensaver Version: 4.21-3 Severity: minor Tags: patch There are two short chunks of repeated text (The pong the pong) on the manpage. Also a missing full stop and a missing space. I've also changed artifact to artefact because all my dictionaries (Collins 2003, Chambers, Shorter OED) give artefact as the main spelling. Here is the patch: --- pong.6x 2005-04-09 08:49:55.0 +0100 +++ pong.6x.new 2006-04-09 17:36:47.0 +0100 @@ -9,8 +9,8 @@ .SH DESCRIPTION The .I pong -The pong program simulates an ancient Pong home video game, as well as -various artifacts from displaying it on a color TV set. +program simulates an ancient Pong home video game, as well as various +artefacts from displaying it on a color TV set. .SH OPTIONS .I pong accepts the following options: @@ -46,10 +46,10 @@ .BR analogTVColor , .BR analogTVBrightness , and -.BR analogTVContrast +.BR analogTVContrast . +They range from 0 to 100, except for tint which is an angle between +-180 and +180. -which correspond to standard TV controls. They range from 0 to -100,except for tint which is an angle between -180 and +180. .SH TRADEMARKS Pong may be a trademark. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages xscreensaver depends on: ii libatk1.0-01.8.0-4 The ATK accessibility toolkit ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libglade2-01:2.4.2-2 library to load .glade files at ru ii libglib2.0-0 2.6.4-1 The GLib library of C routines ii libgtk2.0-02.6.4-3.1 The GTK+ graphical user interface ii libice64.3.0.dfsg.1-14sarge1 Inter-Client Exchange library ii libjpeg62 6b-10 The Independent JPEG Group's JPEG ii libpam0g 0.76-22 Pluggable Authentication Modules l ii libpango1.0-0 1.8.1-1 Layout and rendering of internatio ii libsm6 4.3.0.dfsg.1-14sarge1 X Window System Session Management ii libx11-6 4.3.0.dfsg.1-14sarge1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14sarge1 X Window System miscellaneous exte ii libxml22.6.16-7 GNOME XML library ii libxmu64.3.0.dfsg.1-14sarge1 X Window System miscellaneous util ii libxpm44.3.0.dfsg.1-14sarge1 X pixmap library ii libxrandr2 4.3.0.dfsg.1-14sarge1 X Window System Resize, Rotate and ii libxrender10.8.3-7 X Rendering Extension client libra ii libxt6 4.3.0.dfsg.1-14sarge1 X Toolkit Intrinsics ii xlibs 4.3.0.dfsg.1-14sarge1 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361687: xscreensaver: pong - fast ball bounces from *behind* paddle
Package: xscreensaver Version: 4.21-3 Severity: normal I don't know if this is a bug or a feature. When the ball speeds up, it often passes most of the way through a paddle before bouncing back. This looks bad. Unless it's a deliberate bug (to emulate classic pong?) it would be better not to draw any part of the ball that has crossed the line of the paddle. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages xscreensaver depends on: ii libatk1.0-01.8.0-4 The ATK accessibility toolkit ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libglade2-01:2.4.2-2 library to load .glade files at ru ii libglib2.0-0 2.6.4-1 The GLib library of C routines ii libgtk2.0-02.6.4-3.1 The GTK+ graphical user interface ii libice64.3.0.dfsg.1-14sarge1 Inter-Client Exchange library ii libjpeg62 6b-10 The Independent JPEG Group's JPEG ii libpam0g 0.76-22 Pluggable Authentication Modules l ii libpango1.0-0 1.8.1-1 Layout and rendering of internatio ii libsm6 4.3.0.dfsg.1-14sarge1 X Window System Session Management ii libx11-6 4.3.0.dfsg.1-14sarge1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14sarge1 X Window System miscellaneous exte ii libxml22.6.16-7 GNOME XML library ii libxmu64.3.0.dfsg.1-14sarge1 X Window System miscellaneous util ii libxpm44.3.0.dfsg.1-14sarge1 X pixmap library ii libxrandr2 4.3.0.dfsg.1-14sarge1 X Window System Resize, Rotate and ii libxrender10.8.3-7 X Rendering Extension client libra ii libxt6 4.3.0.dfsg.1-14sarge1 X Toolkit Intrinsics ii xlibs 4.3.0.dfsg.1-14sarge1 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361733: kxkb: layout tab defaults button corrupts keyboard model list
Package: kdebase-bin Version: 4:3.3.2-1sarge1 Severity: normal I shall describe how to reproduce the bug on a new user account (for which kxkb has never been run). If the user has already made kxkb settings, the screen will look different at step (2). But the bug is always there. (1) start Control Centre -- Regional Accessibility -- Keyboard Layout (2) The keyboard layout module opens with the layout tab active. Note that keyboard layouts are not enabled, so most of the tab is greyed out. You can see that the greyed-out defaults are: keyboard model: Generic 104-key PC active layouts: U.S. English (us) [It is debatable whether those are good defaults. It might make more sense to try and get system-wide defaults from /etc/X11/XF86Config-4, and only fall back to 104-key (us) if nothing there looks sensible. For example, I have the normal settings for a British keyboard: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout gb EndSection so on my system a better default would be Generic 105-key (intl) PC and United Kingdom (gb). Wishlist bug? But let's carry on for now.] (3) click to enable keyboard layouts; the main box becomes active (not greyed-out) (4) click on the drop-down arrow for choosing the keyboard model; on the drop-down menu, click on Generic 105-key (Intl) PC (5) click on defaults in the bottom left; the main box is greyed-out again, but the keyboard model now says pc104. This is already different from the text we saw in step (2). This is a bug. (6) repeat step (3) (7) try to repeat step (4) You will see that the list contains pc104 at the point where it should say Generic 105-key (Intl) PC. This is a bug! There is a workaround for this bug. If keyboard model XX is missing, select instead model YY. Repeat steps (5)-(7). This time model YY is missing, so you can reselect XX. But most users will be confused before they discover the workaround. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kdebase-bin depends on: ii kdelibs4 4:3.3.2-6.4 KDE core libraries ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libfam0c1022.7.0-6sarge1 client library to control the FAM ii libgcc11:3.4.3-13GCC support library ii libice64.3.0.dfsg.1-14sarge1 Inter-Client Exchange library ii libidn11 0.5.13-1.0GNU libidn library, implementation ii libpam-runtime 0.76-22 Runtime support for the PAM librar ii libpam0g 0.76-22 Pluggable Authentication Modules l ii libpng12-0 1.2.8rel-1PNG library - runtime ii libqt3c102-mt 3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-14sarge1 X Window System Session Management ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-14sarge1 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-14sarge1 X Window System miscellaneous exte ii libxrender10.8.3-7 X Rendering Extension client libra ii libxtst6 4.3.0.dfsg.1-14sarge1 X Window System event recording an ii xlibs 4.3.0.dfsg.1-14sarge1 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#361436: gdm: typos in default conf file
Package: gdm Version: 2.13.0.10-2 Severity: minor There are some typos in the default conf file. This applies to both the stable and the testing versions of gdm. (version 2.6.0.8-1) /etc/gdm/gdm.conf /etc/gdm/factory-gdm.conf (version 2.13.0.10-2) /usr/share/gdm/defaults.conf /usr/share/gdm/factory-defaults.conf Suggested corrections: applicaitons -- applications ony -- only vts. turn -- vts. Turn usage that) -- usage) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360896: util-linux: cfdisk(8) manpage typos
Package: util-linux Version: 2.12p-4sarge1 Severity: minor Tags: patch [Also applies to unstable version 2.12r-8] The cfdisk(8) manpage contains some typos. I attach a patch. debian:~/bugs/cfdisk8$ diff -u cfdisk.8.orig cfdisk.8.new diffs -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages util-linux depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libncurses55.4-4 Shared libraries for terminal hand ii libuuid1 1.37-2sarge1 universally unique id library ii slang1a-utf8 1.4.9dbs-8The S-Lang programming library wit ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information --- cfdisk.8.orig 2006-04-05 10:34:14.0 +0100 +++ cfdisk.8.new2006-04-05 10:59:43.0 +0100 @@ -113,7 +113,7 @@ .IR Unusable . The size field displays the size of the partition in megabytes (by default). It can also display the size in sectors and cylinders (see -the change units command below). If an asterisks +the change units command below). If an asterisk .RB ( * ) appears after the size, this means that the partition is not aligned on cylinder boundaries. @@ -184,9 +184,9 @@ desired value and press .IR Enter . The altered disk parameter values do not take effect until you return -the main menu (by pressing +to the main menu (by pressing .IR Enter or ESC -at the change disk geometry command line. If you change the geometry +at the change disk geometry command line). If you change the geometry such that the disk appears larger, the extra sectors are added at the end of the disk as free space. If the disk appears smaller, the partitions that are beyond the new last sector are deleted and the @@ -198,7 +198,7 @@ .TP .B m Maximize disk usage of the current partition. This command will -recover the the unused space between the partition table and the +recover the unused space between the partition table and the beginning of the partition, but at the cost of making the partition incompatible with DOS, OS/2 and possibly other operating systems. This option will toggle between maximal disk usage and DOS, OS/2, @@ -218,7 +218,7 @@ .B cfdisk next prompts you for the size of the partition you want to create. The default size, equal to the entire free space of the current -partition, is display in megabytes. You can either press the +partition, is displayed in megabytes. You can either press the .I Enter key to accept the default size or enter a different size at the prompt. @@ -241,7 +241,7 @@ will ask you to choose where to place the partition. After the partition is created, .B cfdisk -automatically adjusts the other partition's partition types if all of +automatically adjusts the other partitions' partition types if all of the primary partitions are used. .TP .B p @@ -282,7 +282,7 @@ the extended partition is printed before the first logical partition. If a partition does not start or end on a cylinder boundary or if the -partition length is not divisible by the cylinder size, an asterisks +partition length is not divisible by the cylinder size, an asterisk .RB ( * ) is printed after the non-aligned sector number/count. This usually indicates that a partition was created by an operating system that @@ -351,9 +351,9 @@ .B cfdisk will write the partition table to disk and the tell the kernel to re-read the partition table from the disk. The re-reading of the -partition table works is most cases, but I have seen it fail. Don't +partition table works in most cases, but I have seen it fail. Don't panic. It will be correct after you reboot the system. In all cases, -I still recommend rebooting the system--just to be safe. +I still recommend rebooting the system -- just to be safe. .TP .I Up Arrow .TP
Bug#360660: gnome-games: aisleriot - agnes - documentation error
Package: gnome-games Version: 1:2.8.3-2 Severity: minor There seems to be an error in section 3.1 (Agnes) of the AisleRiot manual (version 2.8). The description for foundations says Eight piles top right. Shouldn't that say Four piles top right ? -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358585: floatbg(1X) manpage typos
Package: floatbg Version: 1.0-21 Severity: minor [Applies also to floatbg 1.0-23 in unstable.] you won't to see -- you won't see deterministicly -- deterministically [OPTIONAL] a hsv-model -- an hsv-model addapted -- adapted -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#358586: typo in xserver-xfree86.templates
Package: xserver-xfree86 Version: 4.3.0.dfsg.1-14sarge1 Severity: minor There is a typo in the English text of this template: Template: xserver-xfree86/config/modules s/capabilties/capabilities/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357951: e2fsprogs: badblocks(8) manpage typos
Package: e2fsprogs Version: 1.37-2sarge1 Severity: minor overriden -- overridden with an one pattern -- with one pattern on an device -- on a device I believe the first has been fixed in unstable (e2fsprogs_1.38+1.39-WIP-2005.12.31-1_i386.deb) but the other two remain. Best wishes, J -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages e2fsprogs depends on: ii e2fslibs1.37-2sarge1 ext2 filesystem libraries ii libblkid1 1.37-2sarge1 block device id library ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libcomerr2 1.37-2sarge1 common error description library ii libss2 1.37-2sarge1 command-line interface parsing lib ii libuuid11.37-2sarge1 universally unique id library -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337332: vim.list unpacks two wrong links (which update-alternatives then corrects)
Package: vim Version: 1:6.3-071+1 Severity: normal Two symlinks in vim.list should be deleted: srwxrwxrwxroot/root 0 ./usr/share/man/man1/ex.1.gz -- vim.1.gz srwxrwxrwxroot/root 0 ./usr/share/man/man1/view.1.gz -- vim.1.gz As soon as dpkg has unpacked these links, dpkg calls vim.postinst, where these links are changed with update-alternatives. It looks like a bug to include them in vim.list. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages vim depends on: ii dpkg 1.10.28 Package maintenance system for Deb ii libc62.3.2.ds1-22GNU C Library: Shared libraries an ii libgpmg1 1.19.6-19sarge1 General Purpose Mouse - shared lib ii libncurses5 5.4-4 Shared libraries for terminal hand ii vim-common 1:6.3-071+1 Vi IMproved - Common files -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335507: cruft: filters should be applied selectively
Package: cruft Version: 0.9.6-0.4 Severity: important 1.Outline There seems to be a design flaw in cruft's filter mechanism. In some ways this is a 'wishlist' bug, but I've tagged it 'important' because - cruft's filters cause it to overlook cruft that it could and should find; - with the current design, as cruft's filters improve so the problem worsens. The good news is that the flaw is not hard to fix. I'm providing what I think is an almost complete solution. 2.The problem Consider this common situation: package 'foo' (1) contains an extra file '/foo/bar' that dpkg wouldn't normally know about, and (2) forgets to delete /foo/bar when foo is purged. Alice installs package 'foo'. She wants cruft to ship with a filter /usr/lib/cruft/filters/foo so that /foo/bar is not reported as 'unexplained'. But Bob also installs 'foo', and later he purges it. He doesn't want cruft to use the filter /usr/lib/cruft/filters/foo. [A real-life example: purging package 'inewsinn' leaves crufty files like '/etc/news/whoami'. Cruft is unable to report them because of the filter named 'inn' - even if package 'inn' was never installed.] Moreover, as cruft's filters improve with each new release (giving fewer false positives) so cruft's ability to detect when these files become crufty diminishes (giving more false negatives, so to speak). The more you please Alice, the less you please Bob. It's a zero-sum game! 3.A solution I believe there is a good solution: cruft should use *all* of the locally provided filters /etc/cruft/filters, but only *some* of the filters shipped with cruft. It should use filter /usr/lib/cruft/filters/foo if and only if package foo seems to be installed on the system. This can be done by modifying the script /usr/lib/cruft/extrafiles, see attachment. For this to be a complete solution, something needs to be done about the filters not named after a package. I believe they should be abolished. For example: file current filter name proposed filter name /etc/localtime timezones libc6 /var/log/lastlog lastlog login This is better, eg it is libc6.postinst which creates /etc/localtime. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages cruft depends on: ii file4.12-1 Determines file type using magic ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an -- debconf-show failed extrafiles Description: application/shellscript
Bug#335270: nn: broken templates/config/postinst files
Package: nn
Version: 6.6.5-2
Severity: important
[I have checked 6.7.2-1 from testing and all the following applies.]
[I have also looked back at 6.6.4-0.woody.1, where it also applied.]
The control files nn.{templates,config,postinst} seem a bit broken, in
several ways. Perhaps the bug severity should be serious?
Summary:
(1) Template name mismatch
(2) Obsolete (and deprecated) creation of /etc/news in nn.config
(3) Owner/group mismatch for /etc/news
(4) Postinst writes to /etc/servers when /etc/server seems intended
Details:
(1) Template name mismatch
File nn.templates defines Template: nn/ask-server.
But the scripts nn.config and nn.postinst try to interact with the
differently-named template nn/ask-newsserver.
The result of this mismatch is a bit unpredictable, because it depends
on the pre-existing data in /var/cache/debconf/{config,templates}.dat
If there is no pre-existing nn/ask-newsserver in its cache, debconf
may return $RET = nn/ask-newsserver doesn't exist and this is
written out by the postinst to /etc/news/servers (this actually
occurred during my upgrade to woody).
If there is a pre-existing (old) nn/ask-newsserver in the cache, debconf
uses it, completely ignoring the (new) nn/ask-server in the package.
(This occurs on my system now, under sarge, though I have not been able
to determine when nn/ask-newsserver entered the cache.)
For a quick fix, I suggest changing nn.templates so that the template
is called 'nn/ask-newsserver' consistently.
[In the longer term, it would be good to agree a shared template with
other news packages in debian. This is touched on in various policy
documents. Until this is done, I would expect preconfiguration on a
fresh install (with no existing /etc/news/server) to ask the news
server question for several packages but then use the answer only from
one; not good.]
(2) Obsolete (and deprecated) creation of /etc/news in nn.config
Since version June 2002 (6.6.4-0.woody.1) the directory /etc/news has
been part of the nn-dirs. See the changelog and bug #134002. Sure
enough, in nn_6.7.2-1_i386.deb-DATA, we see:
drwxr-xr-xroot/root 0 ./etc/news/
So I think the creation of /etc/news by script nn.config is obsolete.
Doing it in the maintainer scripts seems to go back essentially to
bug #49639 from November 1999, before it was one of the nn-dirs.
Surely you don't need to do that any more? By the time the dir is
needed - in the postinst - it will exist.
Creating the dir in the config script is not just redundant, it is
deprecated: the config script should not need to modify the
filesystem at all [debconf-devel(7), from package debconf-doc].
(3) Owner/group mismatch for /etc/news
The package is unclear about the desired owner/group of /etc/news.
In nn.config it says
install -d -m 755 -o news -g news /etc/news
but the nn-dir unpacked by the package (see above) was root/root.
If there is a good reason for departing from general policy (debian
policy, section 10.9) and having owner/group news/news , then the
.deb-DATA should change, so it unpacks the dir correctly. If you
are happy with root/root, the code in nn.config should say so -
except, as suggested at (2) above, this code should probably be deleted
anyway.
(4) Postinst writes to /etc/servers when /etc/server seems intended
File nn.config asks its template question
if [ ! -f /etc/news/server ]
But the postinst uses the answer to that template question like this:
# setting /etc/news/servers
db_get nn/ask-newsserver || true
echo $RET /etc/news/servers
Notice the difference: 'server' and 'servers'.
I don't know the package well enough. Perhaps this is not a bug. But
it does look strange. Surely if /etc/news/server does not exist, that
is the file you want to create? [If this *is* a bug, it helps explain
why the other bugs didn't get noticed sooner.]
- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages nn depends on:
ii debconf 1.4.30.13Debian configuration management sy
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libncurses5 5.4-4Shared libraries for terminal hand
-- debconf information:
nn/ask-server: news
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335035: debconf-doc: debconf-devel(7) manpage typos
Package: debconf-doc
Version: 1.4.30.13
Severity: minor
Tags: patch
I'm attaching a patch for about a dozen typos in the manpage
debconf-devel(7) (file /usr/share/man/man7/debconf-devel.7.gz)
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Script started on Fri 21 Oct 2005 16:09:59 BST
debian:~/bugs/debconf-doc$ diff -u debconf-devel.7.dist debconf-devel.7
--- debconf-devel.7.dist2004-11-28 01:56:01.0 +
+++ debconf-devel.7 2005-10-21 16:09:35.0 +0100
@@ -135,7 +135,7 @@
.TP
.B multiselect
Like the select data type, except the user can choose any number of items
-from the choices list (or chose none of them).
+from the choices list (or choose none of them).
.TP
.B note
Rather than being a question per se, this datatype indicates a note that
@@ -176,9 +176,9 @@
.RS
The 'Description' field, like the description of a Debian package, has
two parts: A short description and an extended description. Note that some
-debconf frontends don't displays the long description, or might only
-display it if the user asks for help. So the short description should be
-able to stand on its own.
+debconf frontends don't display the long description, or might only display
+it if the user asks for help. So the short description should be able to
+stand on its own.
.P
If you can't think up a long description, then first, think some more. Post
to debian-devel. Ask for help. Take a writing class! That extended
@@ -224,7 +224,7 @@
see the table in Debian policy's debconf specification document.
.P
The extended return code is genrally free form and unspecified, so you
-should generally ignore it, and should certianly not try to parse it in a
+should generally ignore it, and should certainly not try to parse it in a
program to work out what debconf is doing. The exception is commands like
GET, that cause a value to be returned in the extended return code.
.P
@@ -332,15 +332,15 @@
.TP
.B SUBST question key value
Questions can have substitutions embedded in their 'Description' and 'Choices'
-fields (use of substitutions in 'Choices' fields is a bit of a hack though,
-and better mechanism will eventually be developed). These substitutions
-look like ${key}. When the question is displayed, the substitutions are
-replaced with their values. This command can be used to set the value of a
+fields (use of substitutions in 'Choices' fields is a bit of a hack though;
+a better mechanism will eventually be developed). These substitutions look
+like ${key}. When the question is displayed, the substitutions are replaced
+with their values. This command can be used to set the value of a
substitution. This is useful if you need to display some message to the
user that you can't hard-code in the templates file.
.IP
Do not try to use SUBST to change the default value of a question; it won't
-work since there is a SET command explicitely for that purpose.
+work since there is a SET command explicitly for that purpose.
.TP
.B FGET question flag
Questions can have flags associated with them. The flags can have a value
@@ -351,11 +351,11 @@
This sets the value of a question's flag. The value must be either true
or false.
.P
-One common flag is the seen flag. It is normally only set if a user already
-seen a question. Debconf usually only displays questions to users if they
-have the seen flag set to false (or if it is reconfiguring a package).
+One common flag is the seen flag. It is normally only set if a user has
+already seen a question. Debconf usually only displays questions to users if
+they have the seen flag set to false (or if it is reconfiguring a package).
Sometimes you want the user to see a question again -- in these cases you can
-set the seen flag to false to force the debconf to redisplay it.
+set the seen flag to false to force debconf to redisplay it.
.RE
.TP
.B METAGET question field
@@ -483,11 +483,11 @@
scripts.
.P
Note that if your package's sole use of debconf is in the postrm, you should
-make your package's postinst sources /usr/share/debconf/confmodule, to give
+make your package's postinst source /usr/share/debconf/confmodule, to give
debconf a chance to load up your templates file into its database. Then the
templates will be available when your package is being purged.
.P
-You can also use debconf in other, stand alone programs. The issue to watch
+You can also use debconf in other, standalone programs. The issue to watch
out for here is that debconf is not intended to be, and must not be used as
a registry. This is unix after all, and programs are configured by files in
/etc, not by some nebulous debconf database (that is only a cache anyway
@@ -509,7 +509,7 @@
Besides the 'Description' field, you should translate the 'Choices' field
of a select or multiselect template. Be sure to list the translated choices
in the same order as they
Bug#335060: logrotate: more manpage typos
Package: logrotate Version: 3.7-5 Severity: minor Tags: patch There are a few more typos besides the then/than error from bug #333996. (1) 100 k is size - 100k in size (2) the (2) belongs inside the parenthesis, right after chmod (3) they resides - they reside (4) sharedscript - sharedscripts (5) My patch also moves the paragraph for sharedscripts ahead of size, because it belongs earlier alphabetically. Sorry I overlooked the then/than bug when reporting #101272. Must be a blind spot! On the other hand, I note that (1)-(3) and (5) were already reported in #101272. :-) -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Script started on Fri 21 Oct 2005 18:39:45 BST debian:~/bugs/logrotate$ diff -u logrotate.8.dist logrotate.8 --- logrotate.8.dist2005-05-25 10:49:16.0 +0100 +++ logrotate.8 2005-10-21 18:30:42.0 +0100 @@ -123,7 +123,7 @@ The next section defines the parameters for both \fI/var/log/httpd/access.log\fR and \fI/var/log/httpd/error.log\fR. -Each is rotated whenever it grows over 100k is size, and the old log +Each is rotated whenever it grows over 100k in size, and the old log files are mailed (uncompressed) to [EMAIL PROTECTED] after going through 5 rotations, rather then being removed. The \fBsharedscripts\fR means that the \fBpostrotate\fR script will only be run once, not once for each @@ -198,7 +198,7 @@ Immediately after rotation (before the \fBpostrotate\fR script is run) the log file is created (with the same name as the log file just rotated). \fImode\fR specifies the mode for the log file in octal (the same -as \fBchmod\fR)(2), \fIowner\fR specifies the user name who will own the +as \fBchmod\fR(2)), \fIowner\fR specifies the user name who will own the log file, and \fIgroup\fR specifies the group the log file will belong to. Any of the log file attributes may be omitted, in which case those attributes for the new file will use the same values as the original log @@ -298,8 +298,8 @@ .TP \fBnoolddir\fR -Logs are rotated in the directory they normally resides in (this -overrides the \fBolddir\fR option). +Logs are rotated in the directory they normally reside in (this overrides +the \fBolddir\fR option). .TP \fBnosharedscripts\fR @@ -357,6 +357,17 @@ are removed rather then rotated. .TP +\fBsharedscripts\fR +Normally, \fBprerotate\fR and \fBpostrotate\fR scripts are run for each +log which is rotated, meaning that a single script may be run multiple +times for log file entries which match multiple files (such as the +\fI/var/log/news/*\fR example). If \fBsharedscripts\fR is specified, the +scripts are only run once, no matter how many logs match the wildcarded +pattern. However, if none of the logs in the pattern require rotating, the +scripts will not be run at all. This option overrides the +\fBnosharedscripts\fR option. + +.TP \fBsize \fIsize\fR[\fBG\fR|\fBM\fR|\fBk\fR] Log files are rotated when they grow bigger then \fIsize\fR bytes. If \fIsize\fR is followed by \fIM\fR, the size if assumed to be in megabytes. @@ -365,17 +376,6 @@ \fIsize 100k\fR, \fIsize 100M\fR and \fIsize 1G\fR are all valid. .TP -\fBsharedscripts\fR -Normally, \fBprerotate\fR and \fBpostrotate\fR scripts are run for each -log which is rotated, meaning that a single script may be run multiple -times for log file entries which match multiple files (such as the -\fI/var/log/news/*\fR example). If \fBsharedscript\fR is specified, the scripts -are only run once, no matter how many logs match the wildcarded pattern. -However, if none of the logs in the pattern require rotating, the scripts -will not be run at all. This option overrides the \fBnosharedscripts\fR -option. - -.TP \fBstart \fIcount\fR This is the number to use as the base for rotation. For example, if you specify 0, the logs will be created with a .0 extension as they are debian:~/bugs/logrotate$ exit Script done on Fri 21 Oct 2005 18:41:22 BST
Bug#334268: procmail-lib: dead code in postinst; no prerm/postrm to remove symlink
Package: procmail-lib Version: 1:2002.01.02-1 Severity: normal Two, possibly related, bugs (1) This code from the postinst looks dead to me. if [ -d /usr/lib/procmail-lib -a ! -d /usr/lib/procmail-lib ]; then rm -rf /usr/lib/procmail-lib fi So it can't have done what it was supposed to do, surely! Or am I missing something? :-) (2) When upgrading from pre-woody, the postinst makes a symlink. Even purging the package doesn't remove the symlink. I had procmail-lib from potato installed (vn 1995.08.28-4.1) and upgraded to woody (vn 1997.07.22-2). The (woody) postinst created this symbolic link: debian:/usr/lib$ ls -o procmail-lib lrwxrwxrwx 1 root 23 2002-08-26 03:57 procmail-lib - /usr/share/procmail-lib This link is unchanged by the woody - sarge upgrade, and is not removed when procmail-lib is purged. I would suggest removing the link in the prerm, or if you really want the link to survive further upgrades, then in a postrm. Something like if [ -L /usr/lib/procmail-lib ]; then rm -f /usr/lib/procmail-lib fi -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages procmail-lib depends on: ii perl 5.8.4-8Larry Wall's Practical Extraction ii procmail 3.22-11Versatile e-mail processor -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334301: modutils: typo on manpage update-modules(8)
Package: modutils Version: 2.4.26-1.2 Severity: minor The manpage for update-modules says SEE ALSO depmod(1). I believe that should be depmod(8). -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages modutils depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii sysvinit2.86.ds1-1 System-V like init -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334091: filter for cruft should filter filters not filter
Package: cruft Version: 0.9.6-0.4 Severity: normal Tags: patch Cruft's filter file for itself, /usr/lib/cruft/filters/cruft , contains a small mistake. Here is the patch: --- cruft.dist 1998-04-13 17:40:45.0 +0100 +++ cruft 2005-10-15 13:53:26.0 +0100 @@ -1,5 +1,5 @@ /etc/cruft/explain/* -/etc/cruft/filter/* +/etc/cruft/filters/* /var/spool/cruft/expl_* /var/spool/cruft/file_* /var/spool/cruft/miss_* This bug also occurs in experimental 0.9.6-0.8 Can we make a case for some of the bugfixes to cruft filters making it into the revision of stable? I'm thinking of, at least, the fixes to /usr/lib/cruft/explain/init_d /usr/lib/cruft/filters/dpkg(both fixed in experimental) The case would be: (1) a substantial gain in usefulness (less spurious cruft reported); (2) many users would benefit (see popcon); (3) no danger of breaking anything. What does Anthony Towns think? I realize it's borderline with regard to what 'stable' is for, but wouldn't every user of the package be grateful? Can we not argue that cruft shipped with bad filters is sufficiently broken to warrant a revision to stable? (PS: wonderful package, even with broken filters) -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages cruft depends on: ii file4.12-1 Determines file type using magic ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#332650: /etc/ppp/ip-up over-writes its log (should append)
Package: ppp
Version: 2.4.3-20050321+2
Severity: normal
Tags: patch
I suggest that /etc/ppp/ip-up should *append* to the logfile, not
overwrite. The other scripts (ip-down, ipv6-up and ipv6-down) append.
Here is my patch:
debian:/etc/ppp$ diff -u ip-up.dist ip-up
--- ip-up.dist 2005-05-05 18:32:20.0 +0100
+++ ip-up 2005-10-07 16:00:13.0 +0100
@@ -37,7 +37,7 @@
# If /var/log/ppp-ipupdown.log exists use it for logging.
if [ -e /var/log/ppp-ipupdown.log ]; then
- exec /var/log/ppp-ipupdown.log 21
+ exec /var/log/ppp-ipupdown.log 21
echo $0 $*
echo
fi
If you accept this patch then the logfile may start to grow. So you
might want to rotate the logfile by modifying /etc/logrotate/ppp
It makes sense to use the same options as for /var/log/ppp-ipupdown.log
so I suggest the following patch:
debian:/etc/logrotate.d$ diff -u ppp.dist ppp
--- ppp.dist2005-05-05 18:32:21.0 +0100
+++ ppp 2005-10-07 16:18:24.0 +0100
@@ -1,4 +1,4 @@
-/var/log/ppp-connect-errors {
+/var/log/ppp-connect-errors /var/log/ppp-ipupdown.log {
weekly
rotate 4
missingok
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages ppp depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libpam-modules 0.76-22 Pluggable Authentication Modules f
ii libpam-runtime 0.76-22 Runtime support for the PAM librar
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libpcap0.7 0.7.2-7 System interface for user-level pa
ii makedev2.3.1-77 creates device files in /dev
ii netbase4.21 Basic TCP/IP networking system
ii procps 1:3.2.1-2 The /proc file system utilities
ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime
-- debconf information:
ppp/maxfail:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#332659: spelling errors in /usr/share/ppp/pap-secrets
Package: ppp Version: 2.4.3-20050321+2 Severity: minor Tags: patch There are two spelling errors in this file. These changes are needed: s/therfore/therefore/ s/its/it's/(or s/its/it is/) Because the line breaking changes a bit, the patch affects four lines. Here it is: debian:/etc/ppp$ diff -u pap-secrets.dist pap-secrets --- pap-secrets.dist2005-05-05 18:32:20.0 +0100 +++ pap-secrets 2005-10-07 17:24:42.0 +0100 @@ -4,12 +4,12 @@ # This is a pap-secrets file to be used with the AUTO_PPP function of # mgetty. mgetty-0.99 is preconfigured to startup pppd with the login option # which will cause pppd to consult /etc/passwd (and /etc/shadow in turn) -# after a user has passed this file. Don't be disturbed therfore by the fact -# that this file defines logins with any password for users. /etc/passwd -# (again, /etc/shadow, too) will catch passwd mismatches. +# after a user has passed this file. Don't be disturbed therefore by the +# fact that this file defines logins with any password for users. +# /etc/passwd (again, /etc/shadow, too) will catch passwd mismatches. # # This file should block ALL users that should not be able to do AUTO_PPP. -# AUTO_PPP bypasses the usual login program so its necessary to list all +# AUTO_PPP bypasses the usual login program so it's necessary to list all # system userids with regular passwords here. # # ATTENTION: The definitions here can allow users to login without a -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330483: lifelines-doc: doc-base file contains false description and is broken
Package: lifelines-doc Version: 3.0.37.2-3 Severity: important The package's file /usr/share/doc-base/lifelines-doc contains errors. (1) The abstract is wrong, so the documentation is installed with a badly misleading description. (2) The control fields are wrong for non-html; each format should only have one Files section. (3) The control fields for html only enter one of the two manuals into the doc-base index. It would be better if both manuals were entered. Details: (1) The abstract is wrong. It currently says: Abstract: This manual describes what lifelines is and how it can be used to manage online manuals on Debian systems. Surely lifelines is for managing genealogy data, not for managing online manuals. :-) So shouldn't the abstract say something like this? Abstract: User guide and full programmer's manual for the lifelines genealogy software (2) Installation of lifelines-doc generates these warnings: Setting up lifelines-doc (3.0.37.2-3) ... warning: files: overwriting previous setting of control field at /usr/sbin/install-docs line 592, IN line 11. warning: files: overwriting previous setting of control field at /usr/sbin/install-docs line 592, IN line 15. warning: files: overwriting previous setting of control field at /usr/sbin/install-docs line 592, IN line 19. This is because having two Files sections for one Format is not supported. Here is the relevant part of the doc-base manual, at file:/usr/share/doc/doc-base/doc-base.html/ch2.html#s2.3 Files A filename or shell glob representing the files which constitute the in this format of the document. Required field. So /usr/share/doc-base/lifelines-doc should have lines something like this Files: /usr/share/doc/lifelines-doc/ll-*.xml.gz (3) The html section is unhelpful, because it only adds one of the two manuals to the doc-base index. Here is what it currently says: Format: HTML Files: /usr/share/doc/lifelines-doc/ll-userguide.html Index: /usr/share/doc/lifelines-doc/ll-userguide.html Since the manual is in two parts (user guide, programmer's guide) it would be better to ship a small ll-index.html something like this html headtitleLifelines manuals/title/head body a href=ll-userguide.htmlLifelines user guide/a a href=ll-reportmanual.htmlReport programming subsystem/a /body /html and try something like Format: HTML Index: /usr/share/doc/lifelines-doc/ll-index.html Files: /usr/share/doc/lifelines-doc/ll-*.html -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330382: swisswatch: upgrade from 0.6-7.1.1 leaves broken /usr/doc symlink
Package: swisswatch Version: 0.6-8 Severity: normal Severity is probably minor. (But it is serious if policy says that purging a package must remove stuff like this). Upgrading swisswatch from 0.6-7.1.1 to 0.6-8 does not deal properly with the /usr/doc symlink. Consequently, when 0.6-8 is purged, there is a broken symlink /usr/doc/swisswatch - ../share/doc/swisswatch Arguably this was a bug in the old-prerm, which should have said if [ $1 = upgrade -o $1 = remove ]; then instead of simply if [ $1 = remove ]; then So upgrading doesn't remove the link, but the upgraded package doesn't know about the link any more. When swisswatch is now removed, the broken link remains. Suggested fix: add a suitable line to the preinst, something like # clean up cruft from versions 0.6-8 if [ -L /usr/doc/swisswatch ]; then rm /usr/doc/swisswatch fi -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages swisswatch depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii xlibs 4.3.0.dfsg.1-14sarge1 X Keyboard Extension (XKB) configu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
