Bug#582884: ITP: usb-creator -- Live USB creator
Dmitrijs Ledkovs wrote: Mehdi Dogguy me...@dogguy.org wrote: * Package name : usb-creator usb-creator is a bit misleading (or at least… not clear). Could you rename it into something like live-usb-creator? This package has been shipped in Ubuntu for a few releases now. Honestly, I don't know how you (as a team) ended up with such a name. it was before me. But there is liveusb-creator package already developed and packaged in Fedora [1] [1] https://fedorahosted.org/liveusb-creator/ Speaking as a random bystander who just happened to notice this Debian ITP and went WTF?, I would like to point out that usb-creator and liveusb-creator are two different strings, and that even liveusb-creator may be less than self-explanatory for people who don't happen to have been reading the boot-CD development mailinglists for the past few years. For us outsiders, LiveUSB is an unfamiliar piece of jargon. I gather it's formed by analogy with liveCD, but the difference is that live CDs are literally a kind of CD (like music CDs and data CDs), while live USBs aren't any kind of USB - they're a kind of flash drive. Taking that already confusing term and leaving off the live eliminates the only clue that it has something to do with booting an operating system, and leaves us wondering how you've managed to package a Creator that can be plugged into a USB port. So if you're going to insist on giving these packages newbie-hostile names, please at least say you'll give them intelligible short descriptions, not just ones that expand the name slightly. I would suggest instead of having synopses like this: Package: usb-creator-common ... Description: Live USB creator (common files) they should be more along the lines of: Package: usb-creator-common ... Description: tool for putting OS images on flash drives - common files -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582527: poppler-utils: typo in package synopsis (utilitites)
Package: poppler-utils Severity: wishlist Version: 0.12.4-1 Tags: patch A fix for the surplus t in the package's short description. -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru poppler-0.12.4.pristine/debian/control poppler-0.12.4/debian/control --- poppler-0.12.4.pristine/debian/control 2010-05-21 16:27:30.0 +0100 +++ poppler-0.12.4/debian/control 2010-05-21 16:28:39.0 +0100 @@ -138,7 +138,7 @@ xpdf-reader Provides: xpdf-utils, pdftohtml -Description: PDF utilitites (based on libpoppler) +Description: PDF utilities (based on libpoppler) This package contains pdftops (PDF to PostScript converter), pdfinfo (PDF document information extractor), pdfimages (PDF image extractor), pdftohtml (PDF to HTML converter), pdftotext (PDF to text converter),
Bug#552002: Time to remove pcregrep?
Package: pcregrep
Version: 7.8-3
Followup-For: Bug #552002
Tags: patch
Assuming pcregrep has indeed succeeded in outliving its original
reason for existing (so that the subject-line bug here is in fact
Severity: not-a-bug), it seems to me that this automatically
implies that the original package description is out of date.
Debian Policy 3.4 says: The description should describe the package
(the program) 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.
Currently, its long description says:
# Perl-style regexps have many useful features that the standard POSIX ones
# don't; this is basically the same as grep but with the different
# regexp syntax.
# .
# The other reason for the existence of pcregrep is that its source code is an
# example of programming with libpcre.
Mark Baker wrote:
There is one useful feature that I don't think GNU grep has, which is
multiline mode.
If the --multiline and (let's not forget) --newline options are now
the only remaining reasons for installing pcregrep instead of
sticking with grep -P then they deserve to be advertised in the
package description.
Even without that, I don't see that there is a good reason to drop it;
some people will be used to using it, and it's name is sufficiently
specific that it's not clogging up the namespace. It really isn't any
extra effort to maintain it.
I'm happy to get rid of it if the general consensus is that that would be
the right thing to do, but personally I'm not convinced.
(The main reason for its existence in the upstream source is as sample
code, but as more and more features have been added it's not as useful for
that as it was in early versions)
This never was a reason for a reader to want to install the pcregrep
binary package anyway; it sounds as if the purpose would be served
more effectively by a Vcs-* header so that anyone who's interested
can check out an early upstream version.
It seems to me its description these days should be something along
the general lines of:
Description: grep utility using Perl Compatible Regular Expressions
Perl 5 regexps have many useful features that the standard POSIX ones
lack; but GNU grep's support for them is still incomplete. This package
provides a version specializing in PCRE support, including --multiline
and --newline options not available with grep -P.
(In the process of rewriting it I've tried to reduce the potential
for confusion between the terms regex, regexp, and pcre.)
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru pcre3-7.8.pristine/debian/control pcre3-7.8/debian/control
--- pcre3-7.8.pristine/debian/control 2010-05-08 12:28:59.0 +0100
+++ pcre3-7.8/debian/control 2010-05-08 12:41:03.0 +0100
@@ -70,10 +70,8 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Replaces: pgrep (4.5)
-Description: grep utility that uses perl 5 compatible regexes.
- Perl-style regexps have many useful features that the standard POSIX ones
- don't; this is basically the same as grep but with the different
- regexp syntax.
- .
- The other reason for the existence of pcregrep is that its source code is an
- example of programming with libpcre.
+Description: grep utility using Perl Compatible Regular Expressions
+ Perl 5 regexps have many useful features that the standard POSIX ones
+ lack; but GNU grep's support for them is still incomplete. This package
+ provides a version specializing in PCRE support, including --multiline
+ and --newline options not available with grep -P.
Bug#579421: bind9-host: obsolete package description
Package: bind9-host Version: 1:9.7.0.dfsg.P1-1 Severity: minor Tags: patch The current package description for bind9-host says: Package: bind9-host Description: Version of 'host' bundled with BIND 9.X This package provides the 'host' program in the form that is bundled with the BIND 9.X sources. This version differs from the one provided in the package called host, which is from NIKHEF, and has a similar but different set of features/options. While this is admirably clear about exactly which interocitor the package provides, it says nothing about what an interocitor is or why I might want to install one (infringing a Policy 3.4 should). Furthermore, the information it gives about which kind of host this isn't has gone stale - in Squeeze, the NIKHEF version has finally been RMed (http://bugs.debian.org/537736;), leaving host as a virtual package provided only by bind9-host. And now that bind9 has a monopoly on interocitor supply, every last word in the package description is essentially a pointless duplication of the Homepage: line (oh yeah, and there should be a Homepage: line). Stealing some informative text from the interocitor(1) man page: Homepage: http://www.isc.org/software/bind [...] Description: DNS lookup utility This package provides host, a simple utility for performing DNS lookups. It is normally used to convert names to IP addresses and vice versa. . This is the version bundled with the BIND 9.X sources. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.33.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bind9-host depends on: ii libbind9-601:9.7.0.dfsg.P1-1 BIND9 Shared Library used by BIND ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcap21:2.17-2 support for getting/setting POSIX. ii libdns64 1:9.7.0.dfsg.P1-1 DNS Shared Library used by BIND ii libgssapi-krb5-2 1.8.1+dfsg-2 MIT Kerberos runtime libraries - k ii libisc60 1:9.7.0.dfsg.P1-1 ISC Shared Library used by BIND ii libisccfg601:9.7.0.dfsg.P1-1 Config File Handling Library used ii liblwres60 1:9.7.0.dfsg.P1-1 Lightweight Resolver Library used ii libssl0.9.80.9.8n-1 SSL shared libraries ii libxml22.7.7.dfsg-2 GNOME XML library bind9-host recommends no packages. bind9-host suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579421: bind9-host: obsolete package description
Oops. Patch attached this time. (I didn't just forget to attach it, I deleted the directory it was in, and then the rootfs on that computer died. And edlug.org.uk mailserver's flakey again. I hope you're having a better day!) -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru bind9-9.7.0.dfsg.P1.pristine/debian/control bind9-9.7.0.dfsg.P1/debian/control --- bind9-9.7.0.dfsg.P1.pristine/debian/control 2010-04-27 19:45:57.0 +0100 +++ bind9-9.7.0.dfsg.P1/debian/control 2010-04-27 19:44:18.0 +0100 @@ -5,6 +5,7 @@ Uploaders: Bdale Garbee bd...@gag.com Build-Depends: libkrb5-dev, debhelper (= 5), libssl-dev, libtool, bison, libdb-dev (4.6), libldap2-dev, libxml2-dev, libcap2-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], hardening-wrapper, libgeoip-dev (= 1.4.6.dfsg-5) Build-Conflicts: libdb4.2-dev +Homepage: http://www.isc.org/software/bind Standards-Version: 3.7.3.0 XS-Vcs-Browser: http://git.debian.org/?p=users/lamont/bind9.git XS-Vcs-Git: git://git.debian.org/~lamont/bind9.git @@ -43,11 +44,12 @@ Conflicts: host, dnsutils ( 1:9.0.0) Replaces: dnsutils ( 1:9.0.0) Provides: host -Description: Version of 'host' bundled with BIND 9.X - This package provides the 'host' program in the form that is bundled with - the BIND 9.X sources. This version differs from the one provided in the - package called host, which is from NIKHEF, and has a similar but different - set of features/options. +Description: DNS lookup utility + This package provides host, a simple utility for performing DNS + lookups. It is normally used to convert names to IP addresses and vice + versa. + . + This is the version bundled with the BIND 9.X sources. Package: libbind-dev Section: libdevel
Bug#577850: mini-buildd: [debconf_rewrite] Debconf templates and debian/control review
Stephan Sürken quoted: + There will need to be a dedicated LVM volume group for the chroots + to be maintained on (with schroot). --- There will need to be sound strange for my (non-native) ears ;), maybe just a typo? Don't worry, not a typo; all the following are grammatical. There is a dedicated LVM volume group There needs to be a dedicated LVM volume group There will be a dedicated LVM volume group There will need to be a dedicated LVM volume group Now you point it out, it's interesting that idiomatic English lets me do this, with the will applied on top of the need. I'm treating it as if it was describing a requirement which will come into existence in future; logically, the two layers of modality should be the other way round, expressing a requirement (affecting me now) that a dedicated LVM volume group is going to be available (in future). The there (is) on the very top is the final twist: in an impersonal construction, who is it that feels the need? So it would seem more reasonable if it was: It is necessary that there will be a dedicated LVM volume group But no, that's thoroughly unidiomatic! -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547251: closed by Agustin Martin Domingo agmar...@debian.org (Bug#547251: fixed in wdm 1.28-3.5)
Debian Bug Tracking System wrote: * Fixed to work with composite extension, so we avoid corruptions when composite is enabled, and at a depth other than 24 (Closes: #488715, #547251). I can verify that wdm_1.28-3.5_i386.deb no longer crashes on my Squeeze-testbed machine. Thanks! -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#576749: aspell: man page misspells its
Package: aspell Version: 0.60.6-4 Severity: wishlist Tags: patch Paragraph two of the DESCRIPTION has: # The Aspell library contains an interface allowing other programs # direct access to it's functions and therefore reducing the complex ^ That's the contraction meaning it is or it has. What you wanted was the possessive pronoun its (compare his, whose). Misapostrophisation is almost completely incapable of causing real ambiguity, so I'm only calling it wishlist. You might even argue that it's a valuable hint to alert readers of the limitations of spellchecking software... -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.33.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aspell depends on: ii dictionaries-common 1.5.1 Common utilities for spelling dict ii libaspell15 0.60.6-4 GNU Aspell spell-checker runtime l ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.2-9 GCC support library ii libncursesw5 5.7+20100313-1 shared libraries for terminal hand ii libstdc++64.4.2-9The GNU Standard C++ Library v3 Versions of packages aspell recommends: ii aspell-en [aspell-dictionary] 6.0-0-6English dictionary for GNU Aspell Versions of packages aspell suggests: pn aspell-docnone (no description available) pn spellutilsnone (no description available) -- debconf-show failed -- JBR Ankh kak! (Ancient Egyptian blessing) --- aspell-0.60.6.pristine/manual/aspell.1 2006-12-19 10:55:08.0 + +++ aspell-0.60.6/manual/aspell.1 2010-04-06 22:07:40.0 +0100 @@ -15,7 +15,7 @@ used by the library. .PP The Aspell library contains an interface allowing other programs direct -access to it's functions and therefore reducing the complex task of +access to its functions and therefore reducing the complex task of spell checking to simple library calls. The default library does not contain dictionary word lists. To add language dictionaries, please check your distro first for modified dictionaries, otherwise look here
Bug#506786: [RFR] templates://linux-2.6/{linux-base.templates,templates/temp.image.pla in/templates}
Ben Hutchings wrote: [Cc'ing the bug, not the lists.] If the two labels (boot sector and root directory) are inconsistent then different tools might reasonably disagree. (I'm going to guess the blkid labels are boot and the problem ones are root.) My odd results were coming from file systems that had been given both kinds of label last year; dosfslabel was showing the root label that it had set, not the boot label I needed. Booting Lenny and using old dosfslabel to generate new clashing labels I can repeat this; even on Squeeze, dosfslabel always prefers to report root labels, ignoring one of the two kinds of label that it now sets. That's a defensible behaviour (after all, what else have I got that can read root labels?) but users who are unaware of the distinction would benefit from some sort of man page tweak: If boot sector and root directory labels differ, dosfstools will report the root directory label. The boot sector labels needed for mount LABEL= can be read with other tools such as blkid. If you can come up with a test case where dosfslabel is still doing the wrong thing (starting from a blank disk, like my test case in #559985) then I will try to fix it. I can't make it *create* label discrepancies, so it's safe for use in the linux-base upgrade, and #506786 counts as fixed. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554170: passwd: handle /var/backups/passwd.bak
Nicolas François wrote: Justin B Rye wrote: [...] Or preferably something more like this: -- #!/bin/sh cd /var/backups || exit 0 for FILE in passwd group shadow gshadow; do test -f /etc/$FILE || continue cmp -s $FILE.bak /etc/$FILE continue install --preserve-context -pm 0600 /etc/$FILE $FILE.bak done -- Is there a reason you changed cp + chmod to install --preserve-context ? The --preserve-context causes warnings (which would be sent daily) on non-SELinux machines. Oh, sorry! I'm even using a non-SELinux kernel right now - so that tells me which machine I must have been on when I did my testing. Okay, scratch that --preserve-context. Usually I'd go for the install -pm 0600 approach because it has the advantage of not leaving the permissions wrong for a moment; but in this case, that only means there's a window of opportunity for members of the shadow group to read data they could already see in the original file... In fact it's not quite clear to me why the permissions would _need_ to be tightened up. Using the same install command on all these files also loses the opportunity to preserve the shadow group-ownership on /etc/*shadow. But then again if you're stripping the group-readable bit why would you _want_ to preserve the group-ownership? Anyway, as I say, the whole point of this bugreport was that the Shadow Cabal would know best what's appropriate here... -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573516: gfsd: package description needs work
Package: gfsd
Version: 2.3.0-1
Severity: minor
Tags: patch l10n
Description: Gfarm filesystem daemon
A filesystem daemon for the Gfarm filesystem,
which has been running on every filesystem node.
Something has been lost in translation there. Did you mean has to
be running, perhaps?
Out of all the binary packages in the gfarm source package, at
present only gfarm-doc gives anything like enough information in its
package description to comply with Debian Policy 3.4:
# The description should describe the package (the program) 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.
At present a sysadmin who encounters gfsd isn't given enough clues
to deduce that an associated documentation package exists, and any
admins who guess are likely to get its name wrong. My patch adds
dependencies to make the connection apparent.
(Meanwhile in gfarm-clients, the man pages for gfchgrp, gfchmod,
gfchown, gffindxmlattr, gfgroup, gfln, gfmv, gfstat, gfuser,
gfxattr, and gfchgrp are in Japanese - I assume; there's also some
sort of charmap problem. It would be nice if they were available in
English; if not, they should at least live in the appropriate
/usr/share/man/XX directory.)
Okay, the main thing your package descriptions need is a boilerplate
paragraph explaining what Gfarm FS is. Let's see how much of it I
can get from the gfarm-doc description:
The Gfarm filesystem is a distributed filesystem consisting of the
local storage of commodity PCs. PCs in a local area network,
compute nodes in a single cluster, multiple clusters in wide area,
comprise a large-scale, high-performance shared network
filesystem. The Gfarm filesystem solves performance and
reliability problems in NFS and AFS by means of multiple file
replicas. It not only prevents performance degradation due to
access concentration, but also supports fault tolerance and
disaster recovery.
Some of that's very informative; some of it's a bit garbled. What
else is there? The upstream front page:
Gfarm file system is a next-generation network shared file system,
which will be an alternative solution of NFS, and will meet a
demand for much larger, much reliable, and much faster file system.
I'm not keen on this - Next Generation is a buzzword left over
from the 1980s, and the rest is only telling me what it isn't yet.
The upstream docs directory has:
Gfarm is a reference implementation of the Grid Datafarm
architecture designed for global petascale data-intensive
computing. It provides Gfarm Grid file system that is a shared
file system in cluster or Grid that can scale up to petascale
storage, and realize scalable I/O bandwidth and scalable parallel
processing.
This is slightly wobbly English, but it has some elements worth
keeping. So I would suggest the following boilerplate:
The Gfarm file system is designed to turn commodity PCs into nodes of
a distributed storage network, implementing the Grid Datafarm
architecture for global petascale data-intensive computing. It solves
performance and reliability problems in NFS and AFS by means of
multiple file replicas, and not only prevents performance degradation
due to access concentration, but also supports fault tolerance and
disaster recovery.
(This needs fact-checking to be sure I haven't mangled it!)
Then each package (especially the ones that turn PCs into nodes)
needs an explanation of its role. Suggested patch attached.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.33.custom
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gfsd depends on:
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libgfarm0 2.3.0-1Runtime libraries for the Gfarm fi
ii libssl0.9.8 0.9.8m-2 SSL shared libraries
gfsd recommends no packages.
gfsd suggests no packages.
-- no debconf information
--
JBR
Ankh kak! (Ancient Egyptian blessing)
Source: gfarm
Section: net
Priority: extra
Maintainer: NIIBE Yutaka gni...@fsij.org
Build-Depends: quilt (= 0.46-7~), debhelper (= 7), autotools-dev, libssl-dev,
libldap2-dev, libpq-dev, postgresql
Standards-Version: 3.8.4
Uploaders: Osamu Tatebe tat...@cs.tsukuba.ac.jp, Noriyuki SODA
s...@sra.co.jp
DM-Upload-Allowed: yes
Homepage: http://datafarm.apgrid.org/
Package: gfarm-doc
Section: doc
Depends: ${misc:Depends}
Architecture: all
Description: Gfarm file system documentation
The Gfarm file system is designed to turn commodity PCs into nodes of
a distributed storage network, implementing the Grid Datafarm
architecture for global petascale data-intensive computing. It solves
performance and reliability problems in NFS and AFS by means of
multiple file replicas, and not only
Bug#509974: Auto-lowercase package names?
Package: aptitude Version: 0.4.11.11-1+b2 Followup-For: Bug #509974 Trent W. Buck wrote: As package names are always lowercase, perhaps aptitude should lowercase requested package names? AOL. Aptitude's behaviour with strings that it doesn't immediately recognise as package names is a bit bizarre. Let's imagine I want to install the amanda backup server. If I ask to aptitude install amanda, this runs into the problem that there's no such binary package name. As a fallback aptitude tries to find packages I might have meant by searching for the string amanda in package descriptions, but as it happens this also fails: root:~# aptitude install amanda Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done No candidate version found for amanda No candidate version found for amanda No packages will be installed, upgraded, or removed. [...] I have no idea why it seems to happen twice, there. I might have guessed that one of these attempts might have been a search on just package names... except that it didn't find amanda-server. Or maybe I would guess that the second search included source packages... except that it misses the one named amanda (as in aptitude build-dep amanda, which works). I don't see anything about this behaviour in aptitude-doc. If I ask to install Amanda, on the other hand, the search successfully matches some packages that happen to have that exact capitalised string in their descriptions: root:~# aptitude install Amanda Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Couldn't find any package matching Amanda. However, the following packages contain Amanda in their description: amanda-server chiark-backup mtx amanda-client Couldn't find any package matching Amanda. However, the following packages contain Amanda in their description: amanda-server chiark-backup mtx amanda-client No packages will be installed, upgraded, or removed. [...] In the case of amanda, searching case-sensitively for the capitalised name finds the packages I was looking for, but it isn't much help with, for instance, apache2: root:~# aptitude install Apache2 Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Couldn't find any package matching Apache2. However, the following packages contain Apache2 in their description: libapache2-mod-auth-sys-group libapache2-mod-rpaf libapache2-mod-proxy-html libapache2-mod-ruby libapache2-authcassimple-perl libapache2-mod-ocamlnet libapache2-reload-perl libapache2-mod-perl2-dev libapache2-mod-auth-pgsql libapache2-mod-perl2-doc libapache2-authenntlm-perl libapache2-mod-auth-openid libapache-ruby1.8 libapache2-mod-auth-plain libembperl-perl libapache2-mod-suphp libapache2-mod-encoding libapache2-mod-defensible libapache2-mod-speedycgi libapache2-mod-perl2 libapache2-mod-auth-pam libapache2-mod-gnutls libapache2-mod-lisp libapache2-mod-mime-xattr libfile-mmagic-xs-perl Couldn't find any package matching Apache2. However, the following packages contain Apache2 in their description: libapache2-mod-auth-sys-group libapache2-mod-rpaf [...etc, as above...] libapache2-mod-mime-xattr libfile-mmagic-xs-perl No packages will be installed, upgraded, or removed. [...] (Notice that apache2 itself isn't on that list.) Wouldn't it make more sense to replace one of those package description searches with a normalised name lookup and/or case-insensitive search? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.33.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.9 0.7.25.3 Advanced front-end for dpkg ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcwidget3 0.5.16-3 high-level terminal interface libr ii libept0 0.5.30 High-level library for managing De ii libgcc1 1:4.4.2-9GCC support library ii libncursesw55.7+20090803-2 shared libraries for terminal hand ii libsigc++-2.0-0c2a 2.2.4.2-1type-safe Signal Framework for C++ ii libstdc++6 4.4.2-9 The GNU Standard C++ Library v3 ii libxapian15 1.0.18-1 Search engine library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-do 0.4.11.11-1 English manual for aptitude, a ter
Bug#570429: sensord: useless on Debian GNU/kFreeBSD
Package: sensord Version: 1:3.1.2-2 Severity: minor root:~$ apt-get install sensord; uname -s [...] Setting up librrd4 (1.3.8-1) ... Setting up fancontrol (1:3.1.2-2) ... Setting up lm-sensors (1:3.1.2-2) ... Setting up sensord (1:3.1.2-2) ... Starting sensor daemon: sensordError loading default configuration file: Kernel interface error failed! GNU/kFreeBSD This is obviously a candidate for don't do that then, given the clue buried in the name Linux Monitoring sensors... but then again note the presence of lsb-base in the dependencies below. The Architecture: fields of one or more of the packages in the family need to be adjusted to mark sensord as Linux-only; you'll have a better idea than I do of what the approved method is when they're a mix of any and all. But by the way, while you're adjusting that control file, would you mind changing the short description for fancontrol? At present it claims to have exactly the same functionality as lm-sensors, and in this case I can easily see how you'd fix it - something like this: -Description: utilities to read temperature/voltage/fan sensors +Description: fan speed control daemon -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: kfreebsd-i386 (i686) Kernel: kFreeBSD 8.0-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sensord depends on: ii libc0.1 2.10.2-2 GNU C Library: Shared libraries ii librrd4 1.3.8-1Time-series data storage and displ ii libsensors4 1:3.1.2-2 library to read temperature/voltag ii lm-sensors1:3.1.2-2 utilities to read temperature/volt ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip sensord recommends no packages. sensord suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523372: consolekit: Couldn't read /proc/'pid_number'/environ
On Sat, Apr 25, 2009, Justin B Rye wrote: Me too. I get both sorts of WARNINGs Somewhere between versions 0.3.0-4 and 0.4.1-3 this stopped happening; I've taken the workaround out of /usr/share/dbus-1/system-services/org.freedesktop.ConsoleKit.service now, and I see console-kit-daemon in my process lists, but neither the Couldn't read /proc//environ message nor #531279's Unable to activate console message are turning up in my logs any longer. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2010021518.ga21...@xibalba.demon.co.uk
Bug#570015: consolekit: ck-collect-session-info coredumps on kFreeBSD
Package: consolekit Version: 0.4.1-3 Severity: normal Every time I boot into kFreeBSD, the logs include: Feb 15 16:02:28 xan kernel: pid 1591 (ck-collect-session-), uid 0: exited on signal 11 (core dumped) ...and there's a fresh 3.8MB corefile in the root directory. I gather it's /usr/lib/ConsoleKit/ck-collect-session-info that's crashing, though what it's trying to do and what functionality I'm therefore liable to be missing out on is unclear, so I'll just call it Severity: normal. Following the wiki's instructions for HowToGetABacktrace I get a debug version; taking a wild stab in the dark at the right arguments I run it under gdb, and while it doesn't crash, it does say something that might explain the problem: Starting program: /usr/lib/ConsoleKit/ck-collect-session-info --uid 0 --pid $$ ** (ck-collect-session-info:13682): WARNING **: ** (process:13683): WARNING **: Socket credentials not supported on this OS unix-user = 0 x11-display = :0.0 display-device = ttyp0 is-local = false Program exited normally. (But I'm still getting the core dumps; clearly there's some trick to invoking it that I haven't guessed.) -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: kfreebsd-i386 (i686) Kernel: kFreeBSD 8.0-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages consolekit depends on: ii dbus1.2.20-2 simple interprocess messaging syst ii libc0.1 2.10.2-2 GNU C Library: Shared libraries ii libck-connector00.4.1-3 ConsoleKit libraries ii libdbus-1-3 1.2.20-2 simple interprocess messaging syst ii libdbus-glib-1-20.84-1 simple interprocess messaging syst ii libglib2.0-02.22.4-1 The GLib library of C routines ii libkvm0 8.0-4FreeBSD kvm (kernel memory interfa ii libpolkit-gobject-1-0 0.96-1 PolicyKit Authorization API ii libx11-62:1.3.3-1X11 client-side library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages consolekit recommends: ii libpam-ck-connector 0.4.1-3ConsoleKit PAM module consolekit suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100215212105.ga25...@xibalba.demon.co.uk
Bug#547251: wdm: segfaults
Package: wdm Version: 1.28-3.3 Now that a new version is available I'll send a followup - thanks for maintaining wdm! On Fri, Sep 18, Justin B Rye wrote: Package: wdm Version: 1.28-3.1 Severity: important To be specific, /usr/bin/wdmLogin segfaults. That was on a machine which has since been decommissioned, trying with either a Matrox Marvel graphics card or an antique S3ViRGE. There, the segfaults happened frequently but not invariably (but didn't start until the upgrade to Squeeze, and always stopped when I switched to another display manager); elsewhere things have gone differently. On a second i386 machine, I've seen the same versions of wdm working flawlessly with the same Matrox card. On a third, I've seen wdm failing in a slightly different fashion. This one is in fact a triple-boot Debian testbed PC with a Lenny partition, a Squeeze/Sid partition, and a Squeeze kFreeBSD partition; the graphics card is an onboard i8xx. In each case, regardless of the kernel and X version involved, wdm fails. It doesn't segfault, though - it just crashes over and over again when it gets to the point of setting up the login screen. No such problems occur with xdm, slim, nodm, or startx. Any suggestions for debugging? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wdm depends on: ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libfontconfig12.8.0-2generic font configuration library ii libice6 2:1.0.6-1 X11 Inter-Client Exchange library ii libpam-modules1.1.1-1Pluggable Authentication Modules f ii libpam-runtime1.1.1-1Runtime support for the PAM librar ii libpam0g 1.1.1-1Pluggable Authentication Modules l ii libsm62:1.1.1-1 X11 Session Management library ii libwraster3 0.92.0-8.1 Shared libraries of Window Maker r ii libx11-6 2:1.3.3-1 X11 client-side library ii libxau6 1:1.0.5-1 X11 authorisation library ii libxdmcp6 1:1.0.3-1 X11 Display Manager Control Protoc ii libxext6 2:1.1.1-2 X11 miscellaneous extension librar ii libxft2 2.1.14-1 FreeType-based font drawing librar ii libxinerama1 2:1.1-2X11 Xinerama extension library ii libxmu6 2:1.0.5-1 X11 miscellaneous utility library ii psmisc22.10-1utilities that use the proc file s ii x11-apps 7.5+1 X applications ii x11-common1:7.5+3X Window System (X.Org) infrastruc ii x11-xserver-utils 7.5+1+b1 X server utilities ii xutils1:7.5+3X Window System utility programs m wdm recommends no packages. Versions of packages wdm suggests: ii xfonts-base 1:1.0.1standard fonts for X -- debconf information: * shared/default-x-display-manager: wdm wdm/daemon_name: /usr/bin/wdm -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100214144746.gb2...@xibalba.demon.co.uk
Bug#566122: apt-listbugs freezes during Parsing Found/Fixed information
Francesco Poli wrote:
Unfortunately, I seem to be unable to reproduce the bug.
I'm getting what looks like the same bug on kfreebsd-i386, but _not_
on the same (multibooting) machine's plain i386 partition, even when
running installs of identical lists of packages.
In today's batch, all the following packages installed happily the
first time I asked for them (reporting no significant bugs):
base-files dbus dbus-x11 dh-make file ipopd iso-codes
kfreebsd-kernel-headers libc-client2007e libdbus-1-3
libdbus-glib-1-2 libdrm-intel1 libdrm2 libjs-jquery libmagic1
libpam-modules libpam-runtime libpam0g lintian mlock smartmontools
xul-ext-flashblock
Leaving me with:
debhelper gdb iceweasel libenchant1c2a libgcrypt11 tzdata
Each of the above (individually or in combination) consistently
failed to get past Parsing Found/Fixed information... 0% until I
disabled apt-listbugs. They have nothing very obvious in common -
iceweasel has Grave bugs, but tzdata doesn't have anything worse
than Normal.
Running
(echo 'VERSION 2'; echo '' ;
ls -1 /var/cache/apt/archives/tzdata_*.deb |
sed 's/^/x x x x /') |
/usr/sbin/apt-listbugs apt -d
shows it hanging at
[...]
#SOAP::Mapping::Object:0x144ee3f0 {}source=tzdata
{}found_versions=[tzdata/2009g-0lenny1] {}done= {}blocks=
{}date=1252150206 {}fixed=#SOAP::Mapping::Object:0x144ed356
{}fixed_versions=[] {}mergedwith=
{}found={tzdata/2009g-0lenny1=nil} {}unarchived=
{}blockedby= {}keywords= {}summary=
{}msgid=4aa24746.1000...@googlemail.com {}id=545146
{}forwarded= {}severity=critical {}owner=
{}log_modified=1258465323 {}location=db-h {}subject=upgrade
Debian 4-5 fails with tzdata: error 10 in post-install
{}originator=Euer Max euer@gmail.com
{}last_modified=1258465323 {}pending=pending {}affects=
{}archived=0 {}tags= {}fixed_date=[] {}package=tzdata
{}found_date=[] {}bug_num=545146
Retrieving bug reports... Done
Parsing Found/Fixed information... 0%Start checking: 545146
.. checking ver 2010a-1 against fixed: found:tzdata/2009g-0lenny1
Which means nothing to me.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: kfreebsd-i386 (i686)
Kernel: kFreeBSD 7.2-1-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apt-listbugs depends on:
ii apt 0.7.25.3Advanced front-end for dpkg
ii libdpkg-ruby1.8 0.3.2 modules/classes for dpkg on ruby 1
ii libgettext-ruby1.8 1.93.0-1.1 Gettext for ruby1.8
ii libhttp-access2-ruby1.8 2.1.5.2-1 HTTP accessing library for ruby (t
ii libruby1.8 [libzlib-ruby1.8] 1.8.7.249-1 Libraries necessary to run Ruby 1.
ii libxml-parser-ruby1.80.6.8-4 Interface of expat for the scripti
ii ruby 4.2 An interpreter of object-oriented
apt-listbugs recommends no packages.
Versions of packages apt-listbugs suggests:
ii conkeror [www-browser] 0.9.1-1 keyboard focused web browser with
ii debianutils 3.2.2Miscellaneous utilities specific t
ii iceweasel [www-browser] 3.5.6-2 Web browser based on Firefox
ii lynx-cur [www-browser] 2.8.8dev.2-1 Text-mode WWW Browser with NLS sup
ii reportbug 4.10.2 reports bugs in the Debian distrib
ii w3m [www-browser] 0.5.2-2.1WWW browsable pager with excellent
-- no debconf information
--
JBR
Ankh kak! (Ancient Egyptian blessing)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100214172534.ga5...@xibalba.demon.co.uk
Bug#566122: apt-listbugs freezes during Parsing Found/Fixed information
Francesco Poli wrote: Did you try with apt-listbugs/0.1.3 from unstable (with libdpkg-ruby1.8/0.3.6 which should be automatically pulled in by dependencies)? That fixes it. Purging apt-listbugs, libdpkg-ruby1.8.0, and iceweasel and then reinstalling the Testing versions brings it back; it hangs on 0% again. Re-upgrading; working again. Mikołaj's turn! -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100214185617.ga8...@xibalba.demon.co.uk
Bug#569578: aptitude: Mark package as having been manually removed
Christophe Lohr wrote: Severity: wishlist Pardon me butting in on your wishlist; I'm just a random bystander, but you reminded me of an unsubmitted wishlist item of my own that might in fact be a better match for what you're after. Hi, aptitude can mark a package as manual installed or automatically installed. Symmetrically, I suggest to introduce a way to mark a package as being manually removed or automatically removed. Similarly, aptitude should avoid to automatically reconsider a manual decision. For example, if a packet is marked as having been manually removed, aptitude should not try to install it again on the pretext that another package recommends or suggests it. This could easily lead to trouble in day-to-day use. Imagine: * I install package foo. It depends on either bar or baz, so I let it pull in the default, bar. * When I decide to try foo with baz, I manually remove bar (since that's the easiest way to get foo to switch to using baz); aptitude silently blacklists it. * Later I discover the package quux, and ask aptitude to install it. It would also like to pull in bar, but doesn't. * Unfortunately, quux needs bar - it's just that in principle it can be configured to use a remote bar-server, so it only has a Recommends instead of a Depends. * Thus I end up with an inoperable quux install. Most of the time when I uninstall a package, I'm not ruling out the possibility I might someday want it back. A package I genuinely want to tell to get out and stay out is an exceptional case; and it seems to me that what I'm after there is something more like purging it and then putting it on hold. At present, hold means keep version X.Y-Z installed, and can only be applied when the package is in fact installed; maybe it could be generalised to let me hold off unwanted packages (keep version NULL installed). Thus for instance if I wanted to install individual GNOME-compatible apps without them automatically inviting all their friends along with them I would be able to put gconf2 on hold-off to break the dependency chain. Notice that doing it this way means I never need to have had it installed in the first place. It would also make sense to let it apply to virtual packages. Another way of getting there would be to extend forbid-version so it interprets aptitude forbid-version gconf2=* as forbid all versions. Oh, except that forbid-version doesn't seem to stop packages being pulled in by dependencies. Yet another approach that's already possible (with some effort) is to use equivs to create a dummy dependency package that declares a Conflicts: gconf2. -- JBR PS: and a pony! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568753: locales: belongs in Section: localization
Package: locales
Version: 2.10.2-5
Severity: wishlist
Tags: patch
All the packages that provide internationalisation data are moving
out of Section: libs and into their own private part of the
archive; but locales and locales-all haven't followed them.
There's no obvious reason for libc's l10n data package to be an
exception; it contains no .so files, but does provide executables
that are important for the system's locale-handling infrastructure.
Compare the package iptables, which is full of actual shared
libraries and lives in Section: net.
One practical benefit of moving it out of Section: libs is that it
would make life easier for tools like deborphan. At present if I do
a Debian install using the Standard+Desktop tasks, but then remove
mutt, locales ends up flagged as a redundantly installed library.
You may have some good counterargument, but I'm submitting this
suggestion in case it's just that nobody has considered it.
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru eglibc-2.10.2.old/debian/control eglibc-2.10.2.new/debian/control
--- eglibc-2.10.2.old/debian/control 2010-02-07 14:25:44.0 +
+++ eglibc-2.10.2.new/debian/control 2010-02-07 14:24:37.0 +
@@ -67,7 +67,7 @@
Package: locales
Architecture: all
-Section: libs
+Section: localization
Priority: standard
Depends: ${locale:Depends}, debconf | debconf-2.0
Conflicts: base-config, belocs-locales-bin, belocs-locales-data
@@ -85,7 +85,7 @@
Package: locales-all
Architecture: any
-Section: libs
+Section: localization
Priority: extra
Depends: ${locale:Depends}, lzma
Provides: locales
Bug#568763: ftp-master: Re: Bug#568753: locales: belongs in Section: localization
Package: ftp.debian.org Severity: wishlist Please move locales and locales-all to Section: localization. On Sun, Feb 07, 2010 at 04:19:17PM +0100, Aurelien Jarno wrote: On Sun, Feb 07, 2010 at 02:44:59PM +, Justin B Rye wrote: Package: locales Version: 2.10.2-5 Severity: wishlist Tags: patch All the packages that provide internationalisation data are moving out of Section: libs and into their own private part of the archive; but locales and locales-all haven't followed them. There's no obvious reason for libc's l10n data package to be an exception; it contains no .so files, but does provide executables that are important for the system's locale-handling infrastructure. Compare the package iptables, which is full of actual shared libraries and lives in Section: net. One practical benefit of moving it out of Section: libs is that it would make life easier for tools like deborphan. At present if I do a Debian install using the Standard+Desktop tasks, but then remove mutt, locales ends up flagged as a redundantly installed library. You may have some good counterargument, but I'm submitting this suggestion in case it's just that nobody has considered it. Done at the package level. Feel free to ask the ftpmaster team to do the same change at the archive level. (I'm not necessarily expecting quite such a blistering turnaround with this...) -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567897: psad: cobwebby package description
Package: psad
Version: 2.1.5
Severity: wishlist
Tags: patch
PSAD's package description could do with some attention.
First, it thinks the latest version of Linux is 2.4.x, and claims to
support 2.2.x - in fact 2.4 is officially unsupported on oldstable.
Second, it has a rather hard to follow list of (lists of) features.
I've tried to tidy it into a clear bulleted list; if I've chopped it
up wrongly, my apologies, but that's more evidence it needs fixing.
And third, it claims to incorporate Snort signatures. The NEWS file
says those were thrown out a while ago.
Here's a more nitpicky package description review - don't bother
reading it if I've already convinced you to accept the patch!
HomePage: http://www.cipherdyne.org/psad/
(That camelcase is unconventional, but should be harmless. So I
don't know why psad's PTS page doesn't show a link...)
Package: psad
Architecture: any
(Does the dependency on iptables save it from needing to specify
except the kfreebsd-* release arches?)
[...]
Description: The Port Scan Attack Detector
This is close to the style recommended by the Developers Reference,
but it would be closer without the capitalised definite article.
PSAD is a collection of four lightweight system daemons written in
Perl and in C that is designed to work with Linux firewalling code
(iptables in the 2.4.x kernels, and ipchains in the 2.2.x kernels)
So just say with iptables, and drop all the references to 2.2/2.4
and ipchains/iptables throughout.
to detect port scans. It features a set of highly configurable danger
(1)
thresholds (with sensible defaults provided), verbose alert messages
(2)
that include the source, destination, scanned port range, begin and
(2a)(2b) (2c)(2d)
end times, tcp flags and corresponding nmap options (Linux 2.4.x
(2d') (2e) (2e'? No, 2f?)
kernels only), reverse DNS info, email alerting, and automatic
(2g? No, 3!) (4) (5)
blocking of offending ip addresses via dynamic configuration of
ipchains/iptables firewall rulesets.
Plus some miscellaneous tweaks, such as using the shift key more for
Nmap, TCP, and IP (but fwsnort seems to be canonically lowercase).
.
In addition, for the 2.4.x kernels psad incorporates many
of the tcp signatures included in Snort to detect highly suspect scans
for:
[...]
Discard all this; instead I've taken some text from the upstream
website. My patch has this instead:
Description: Port Scan Attack Detector
PSAD is a collection of four lightweight system daemons (in Perl and
C) designed to work with iptables to detect port scans. It features:
* a set of highly configurable danger thresholds (with sensible
defaults provided);
* verbose alert messages that include the source, destination,
scanned port range, beginning and end times, TCP flags, and
corresponding Nmap options;
* reverse DNS information;
* alerts via email;
* automatic blocking of offending IP addresses via dynamic firewall
configuration.
.
When combined with fwsnort and the Netfilter string match extension,
PSAD is capable of detecting many attacks described in the Snort rule
set that involve application layer data.
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru psad-2.1.5.pristine/debian/control psad-2.1.5/debian/control
--- psad-2.1.5.pristine/debian/control 2010-01-31 23:33:53.0 +
+++ psad-2.1.5/debian/control 2010-02-01 00:40:00.0 +
@@ -6,7 +6,7 @@
Build-Depends: debhelper (= 7), quilt
Standards-Version: 3.8.3
-HomePage: http://www.cipherdyne.org/psad/
+Homepage: http://www.cipherdyne.org/psad/
Package: psad
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}, ${perl:Depends},
@@ -17,23 +17,19 @@
Recommends: bastille
Suggests: fwsnort
Conflicts: bastille ( 1:1.3.0-4)
-Description: The Port Scan Attack Detector
- PSAD is a collection of four lightweight system daemons written in
- Perl and in C that is designed to work with Linux firewalling code
- (iptables in the 2.4.x kernels, and ipchains in the 2.2.x kernels)
- to detect port scans. It features a set of highly configurable danger
- thresholds (with sensible defaults provided), verbose alert messages
- that include the source, destination, scanned port range, begin and
- end times, tcp flags and corresponding nmap options (Linux 2.4.x
- kernels only), reverse DNS info, email alerting, and automatic
- blocking of offending ip addresses via dynamic configuration of
- ipchains/iptables firewall rulesets.
+Description: Port Scan Attack Detector
+ PSAD is a collection of four lightweight system daemons (in Perl and
+ C) designed to work with iptables to detect port scans. It features:
+ * a set of highly configurable danger thresholds (with sensible
+defaults provided);
+ * verbose
Bug#566282: notmuch: description should mention maildir/mh format requirement
Package: notmuch Version: 0.0+201001211401 Severity: wishlist Tags: patch Prospective users of notmuch get to read the package description, think it sounds useful, visit the homepage and find out the reasons for the name, install it, peruse the README files and the man page's Description section, scan down for the command they need to do a test-run, and execute notmuch setup... before finally being told: # [...] # # If you already have your email being delivered to directories in either # maildir or mh format, then that's perfect. Mail storage that uses mbox # format, (where one mbox file contains many messages), will not work with # notmuch. If that's how your mail is currently stored, we recommend you # first convert it to maildir format with a utility such as mb2md. You can # continue configuring notmuch now, but be sure to complete the conversion # before you run notmuch new for the first time. Given that mbox is the normal default format, this makes notmuch fairly useless for a significant proportion of users. It would be nice if the package description could give a hint at this - maybe Notmuch is a system for indexing, searching, reading, and tagging large collections of email messages. in maildir or mh format. While I'm nitpicking this description, I suppose I should point out the trivial grammar slip in the next sentence: It uses the Xapian library to provide fast, full-text search of very large collection of email with a very convenient search syntax. That's collections. But don't bother fixing it - the phrase is repetitive. Just say: Description: thread-based email index, search and tagging Notmuch is a system for indexing, searching, reading, and tagging large collections of email messages in maildir or mh format. It uses the Xapian library to provide fast full-text searches with a very convenient search syntax. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages notmuch depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libgcc1 1:4.4.2-9GCC support library ii libglib2.0-02.22.4-1 The GLib library of C routines ii libgmime-2.4-2 2.4.11-1 MIME message parser and creator li ii libstdc++6 4.4.2-9 The GNU Standard C++ Library v3 ii libtalloc2 2.0.1-1 hierarchical pool based memory all ii libxapian15 1.0.17-1 Search engine library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime notmuch recommends no packages. Versions of packages notmuch suggests: pn emacs none (no description available) pn vim none (no description available) -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru notmuch-0.0+201001211401.pristine/debian/control notmuch-0.0+201001211401/debian/control --- notmuch-0.0+201001211401.pristine/debian/control 2010-01-21 02:15:16.0 + +++ notmuch-0.0+201001211401/debian/control 2010-01-22 16:38:03.0 + @@ -17,6 +17,6 @@ Suggests: emacs, vim Description: thread-based email index, search and tagging Notmuch is a system for indexing, searching, reading, and tagging - large collections of email messages. It uses the Xapian library to - provide fast, full-text search of very large collection of email with - a very convenient search syntax. + large collections of email messages in maildir or mh format. It uses + the Xapian library to provide fast full-text searches with a very + convenient search syntax.
Bug#561307: RFP: dos2unix -- convert text file line endings between CRLF and LF
Jari Aalto wrote: Subject: RFP: dos2unix -- convert text file line endings between CRLF and LF See: http://packages.debian.org/tofrodos -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558387: How about shared Mercurial repository service?
Paul Crowley wrote: To: 558...@bugs.debian.org This went to the BTS, but you'd need to CC me (directly or as 558387-submit...@bugs.debian.org) to be sure it reaches my inbox - fortunately I also scan the BTS via other means. mercurial-server doesn't provide a server binary, as you say. Instead it adds a service to what the SSH daemon provides. I don't think I can go with the wording you propose, because the service is available as soon as mercurial-server is installed, which isn't what toolkit would suggest - to me, a toolkit is inert until you use the tools to do something. How about something like this? mercurial-server - shared Mercurial repository service I did consider suggesting the option of calling it a framework, but if the above makes the most sense it'll do perfectly. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558384: uzbl: requires existence of files in /usr/share/doc/uzbl
Package: uzbl Version: 0.0.0~git.20091107-1 Justification: Policy 12.3 Severity: serious When starting up for the first time, uzbl attempts to copy files from /usr/share/doc/uzbl to $XDG_CONFIG_HOME, and fails if it can't: $ sudo mv /usr/share/doc/uzbl /usr/share/doc/unuzbl $ uzbl || echo $? cp: cannot stat `/usr/share/doc/uzbl/examples/config/uzbl/config': No such file or directory Could not copy default config to /home/jbr/etc/uzbl/config 3 This violates a must in Debian Policy 12.3 (paragraph 4): # Packages must not require the existence of any files in # '/usr/share/doc/' in order to function*. Any files that are # referenced by programs but are also useful as stand alone # documentation should be installed under '/usr/share/package/' # with symbolic links from '/usr/share/doc/package'. # [...] # * The system administrator should be able to delete files in # '/usr/share/doc/' without causing any programs to break. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.31.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages uzbl depends on: ii libatk1.0-0 1.28.0-1 The ATK accessibility toolkit ii libc6 2.10.1-7 GNU C Library: Shared libraries ii libcairo2 1.8.8-2The Cairo 2D vector graphics libra ii libfontconfig12.6.0-4generic font configuration library ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib ii libglib2.0-0 2.22.2-2 The GLib library of C routines ii libgtk2.0-0 2.18.3-1 The GTK+ graphical user interface ii libpango1.0-0 1.26.0-1 Layout and rendering of internatio ii libsoup2.4-1 2.28.1-3 an HTTP library implementation in ii libwebkit-1.0-2 1.1.16-3 Web content engine library for Gtk ii libx11-6 2:1.2.2-1 X11 client-side library uzbl recommends no packages. Versions of packages uzbl suggests: pn dwm-tools none (no description available) pn socat none (no description available) ii zenity2.28.0-1 Display graphical dialog boxes fro -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558387: mercurial-server: NP problem
Package: mercurial-server
Version: 0.9-1
Severity: wishlist
Tags: patch
Hi! You may or may not be aware that I've been haunting the
debian-l10n-english mailinglist, trying among other things to
encourage developers to follow the DevRef6.2 guidelines on package
descriptions. One of those guidelines is that the short description
should be a Noun Phrase (minus articles) referring to the package
contents - or to put that in more useful terms, it should fit the
template $PACKAGE provides a/the/some $SYNOPSIS. Yours on the
other hand fits the template $PACKAGE lets you $SYNOPSIS (or
perhaps $PACKAGE is designed to $SYNOPSIS), which means it's
(closer to) a Verb Phrase.
Now, phrases like that are common as apropos output, and package
descriptions are often copied directly from either a man page or an
upstream website, but both sources have drawbacks. Web pages tend
to be full of irrelevant enthusiasm about how open-source and easy
to compile the software is; man pages tend to assume the reader is
already familiar with the purpose of the software.
Before you ask, the logic of standardising on Noun Phrases goes like
this:
* Browsing through lists of descriptions is easier when they're
parallel, and the quickest way of improving browsability is to
encourage the use of the format that's already ahead.
* Individual executables may have a single function easily
summarised by a Verb Phrase, but packages aren't executables;
using a Noun Phrase makes packages like x11-common, coreutils,
or ttf-unifont easier to describe.
* Verb Phrase descriptions make it hard to tell at a glance what
general kind of thing a package provides - a daemon, a graphical
app, a set of commandline utilities?
The inherent vagueness is particularly unwelcome in the case of a
package named mercurial-server which doesn't in fact contain a
server binary! Instead I gather that the package is basically a set
of tools (and associated infrastructure) to let admins configure
Mercurial and SSH to work together. So it would be nice if the
synopsis said something like:
mercurial-server - toolkit for managing a shared Mercurial repository
My patch also capitalises SSH and Mercurial throughout on the
grounds that ssh is the command and mercurial is the package.
By the way, did you consider the option of naming it Amalgam?
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.31.custom
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru mercurial-server-0.9.pristine/debian/control mercurial-server-0.9/debian/control
--- mercurial-server-0.9.pristine/debian/control 2009-11-26 13:12:16.0 +
+++ mercurial-server-0.9/debian/control 2009-11-26 13:38:44.0 +
@@ -11,8 +11,8 @@
Package: mercurial-server
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, adduser, python, mercurial, openssh-server | ssh-server
-Description: provide and manage a shared Mercurial repository
+Description: toolkit for managing a shared Mercurial repository
mercurial-server makes a group of repositories available to the developers
- you choose, identified by ssh keys, with easy key and access management
- based on mercurial.
+ you choose, identified by SSH keys, with easy key and access management
+ based on Mercurial.
Bug#557650: bsdmainutils: incomplete list in package description
Package: bsdmainutils Version: 8.0.1 Severity: wishlist Tags: patch In the changelog: bsdmainutils (8.0.1) unstable; urgency=low [...] * Renamed banner to printerbanner. (Closes: #315664) But the package description still says: Included are: banner, ncal, cal, calendar, col, colcrt, colrm, column, from, hexdump, look, lorder, ul, write. An updated and realphabeticised version of that would be: Included are: bsd-write, calendar, col, colcrt, colrm, column, from, hexdump, look, lorder, ncal, printerbanner, ul. That's omitting symlinks; including them would add cal, hd, and write. Apart from that it's a perfectly okay package description, and it seems a pity to have to bother you about it. Wouldn't it be nice if there was a dh_package_description_executables_catalog (or something) to handle this automatically? Compare bsdutils bug #482098, coreutils bug #535458, procps bug #535954, and psmisc bug #485693... -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.31.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bsdmainutils depends on: ii bsdutils 1:2.16.1-4 Basic utilities from 4.4BSD-Lite ii debianutils 3.2.1 Miscellaneous utilities specific t ii libc6 2.10.1-7 GNU C Library: Shared libraries ii libncurses5 5.7+20090803-2 shared libraries for terminal hand bsdmainutils recommends no packages. Versions of packages bsdmainutils suggests: ii cpp 4:4.3.3-9+nmu1 The GNU C preprocessor (cpp) ii miscfiles [wordlist] 1.4.2.dfsg.1-9 Dictionaries and other interesting pn vacation none (no description available) ii wbritish [wordlist] 6-3British English dictionary words f ii whois 4.7.36 an intelligent whois client -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru bsdmainutils-8.0.1.pristine/debian/control bsdmainutils-8.0.1/debian/control --- bsdmainutils-8.0.1.pristine/debian/control 2009-11-03 14:34:42.0 + +++ bsdmainutils-8.0.1/debian/control 2009-11-23 14:36:04.0 + @@ -15,8 +15,8 @@ This package contains lots of small programs many people expect to find when they use a BSD-style Unix system. . - Included are: banner, ncal, cal, calendar, col, colcrt, colrm, column, from, - hexdump, look, lorder, ul, write. + Included are: bsd-write, calendar, col, colcrt, colrm, column, from, hexdump, + look, lorder, ncal, printerbanner, ul. . This package used to contain whois and vacation, which are now distributed in their own packages. Also here was tsort, which is now in the coreutils
Bug#557650: bsdmainutils: incomplete list in package description
Michael Meskes wrote: On Mon, Nov 23, 2009 at 02:40:45PM +, Justin B Rye wrote: But the package description still says: Included are: banner, ncal, cal, calendar, col, colcrt, colrm, column, from, hexdump, look, lorder, ul, write. An updated and realphabeticised version of that would be: Included are: bsd-write, calendar, col, colcrt, colrm, column, from, hexdump, look, lorder, ncal, printerbanner, ul. I'm not sure I really agree. The name list lists the BSD tools under there original names. We had to rename two in Debian because of conflicts, but the new names do not mean as much to a new user as the original ones. Do you mean you're prioritising the interests of users coming from BSD who are going to want to know which package to install to get a banner on their path? That's pointless: installing this package _won't_ put a banner on their path, and besides, it's almost certain to have already been pulled in by the dependencies from man-db and so on. Look at the equivalent lists for other packages such as coreutils (or even bsdutils), where the items being catalogued are the names of the executables that the package literally includes. It's reasonable enough if you choose to _also_ mention the symlinks, but face facts: this .deb really does include /usr/bin/bsd-write and /usr/bin/printerbanner. Maybe something like this would work for everyone: It provides banner (as printerbanner), calendar, col, colcrt, colrm, column, from, hexdump (or hd), look, lorder, ncal (or cal), ul, and write (as bsd-write). -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555394: os-prober: fails both sides of a Linux/kFreeBSD dual-boot
Package: os-prober
Version: 1.35
Severity: normal
My Squeeze testbed system dual-boots Debian GNU/Linux and Debian
GNU/kFreeBSD (installed from an October debian-installer netinst
daily image). On both OSes, os-prober is pulled in by grub2, but
fails to live up to its documentation (by which of course I mean the
package description).
The partition layout is just:
/dev/hda1 AKA ad0s1 (ext3) = i386 system
/dev/hda2 AKA ad0s2 (ufs2) = kfreebsd-i386 system
/dev/hda3 AKA ad0s3 (vfat) = unused data partition
/dev/hda4 AKA ad0s4 (swap) = swap partition
On the Linux side (running either 2.6.30-2-486 or a kernel-packaged
2.6.31.custom), sudo os-prober outputs nothing - unless I first
mount the partition that has the GNU/kFreeBSD system on it, in which
case it misidentifies it:
/dev/hda2:Debian GNU/Linux (squeeze/sid):Debian:linux
As a result, /etc/grub.d/30_os-prober either silently fails to
detect anything, or outputs:
Found Debian GNU/Linux (squeeze/sid) on /dev/hda2
Either way it does nothing to the generated grub.cfg. I might guess
that this is because linux-boot-prober /dev/hda2 finds nothing,
but then again nor does linux-boot-prober /dev/hda1.
No, wait, my mistake: update-grub also outputs copious debug
output to syslog. That looks like a recently-added grub2 bug, but
here's a copy of the output anyway:
Nov 9 12:00:07 xan 10freedos: debug: /dev/hda3 is a FAT32 partition
Nov 9 12:00:07 xan 10qnx: debug: /dev/hda3 is not a QNX4 partition: exiting
Nov 9 12:00:07 xan 20microsoft: debug: /dev/hda3 is a FAT32 partition
Nov 9 12:00:07 xan kernel:
Nov 9 12:00:07 xan kernel: WARNING Wrong ufstype may corrupt your
filesystem, default is ufstype=old
Nov 9 12:00:07 xan kernel: You didn't specify the type of your ufs filesystem
Nov 9 12:00:07 xan kernel: mount -t ufs -o
ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
Nov 9 12:00:07 xan kernel: ufs_read_super: bad magic number
Nov 9 12:00:07 xan macosx-prober: debug: /dev/hda3 is not an HFS+ partition:
exiting
Nov 9 12:00:07 xan os-prober: debug: running
/usr/lib/os-probes/50mounted-tests on /dev/hda1
Nov 9 12:00:07 xan os-prober: debug: running
/usr/lib/os-probes/50mounted-tests on /dev/hda2
Nov 9 12:00:07 xan os-prober: debug: running
/usr/lib/os-probes/mounted/10freedos on mounted /dev/hda3
Nov 9 12:00:07 xan os-prober: debug: running /usr/lib/os-probes/mounted/10qnx
on mounted /dev/hda3
Nov 9 12:00:07 xan os-prober: debug: running
/usr/lib/os-probes/mounted/20macosx on mounted /dev/hda3
Nov 9 12:00:07 xan os-prober: debug: running
/usr/lib/os-probes/mounted/20microsoft on mounted /dev/hda3
Nov 9 12:00:07 xan os-prober: debug: running
/usr/lib/os-probes/mounted/30utility on mounted /dev/hda3
Nov 9 12:00:08 xan 30utility: debug: /dev/hda3 is a FAT32 partition
Nov 9 12:00:08 xan 50mounted-tests: debug: /dev/hda4 is a swap partition;
skipping
Nov 9 12:00:08 xan os-prober: debug: os detected by
/usr/lib/os-probes/50mounted-tests
Nov 9 12:00:08 xan os-prober: debug: running
/usr/lib/os-probes/50mounted-tests on /dev/hda4
Nov 9 12:00:08 xan os-prober: debug: running /usr/lib/os-probes/mounted/40lsb
on mounted /dev/hda3
Nov 9 12:00:08 xan os-prober: debug: running
/usr/lib/os-probes/mounted/70hurd on mounted /dev/hda3
Nov 9 12:00:08 xan os-prober: debug: running
/usr/lib/os-probes/mounted/80minix on mounted /dev/hda3
Nov 9 12:00:08 xan os-prober: debug: running
/usr/lib/os-probes/mounted/90linux-distro on mounted /dev/hda3
Nov 9 12:00:08 xan os-prober: debug: running
/usr/lib/os-probes/mounted/90solaris on mounted /dev/hda3
It obviously isn't guessing the UFS-type that d-i gave me.
On the kFreeBSD side, sudo os-prober outputs only:
Cannot find list of partitions!
...with no debug output to syslog.
The same problem with identifying kFreeBSD partitions affects
grub-install, which isn't a disaster because I don't really want it
to lay claim to the boot sector. update-grub does at least generate
a grub.cfg with a kFreeBSD boot stanza, and I can use a script on
the Linux side to copy that from /mnt/boot/grub/grub.cfg into
/boot/grub/grub.cfg... so everything boots happily.
Nonetheless, it seems to me that os-prober should be able to identify
Debian installs, and it isn't managing to do that here.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: {i386,kfreebsd-i386} (i686)
Kernel: {Linux 2.6.31.custom,kFreeBSD 7.2-1-686}
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages os-prober depends on:
ii libc{6,0.1} 2.10.1-5 GNU C Library: Shared libraries
os-prober recommends no packages.
os-prober suggests no packages.
-- no debconf information
--
JBR
Ankh kak! (Ancient Egyptian blessing)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Bug#554170: passwd: handle /var/backups/passwd.bak
Package: passwd Version: 1:4.1.4.2-1 Severity: wishlist At present /etc/cron.daily/standard maintains backups of /etc/passwd (and so on) in /var/backups. If this is something that it's generally agreed is worth doing, it would seem to make more sense for the cronjob handling it to belong to the package passwd, not cron itself. I'd like to propose that passwd should copy the approach adopted by dpkg, which now (since version 1.15.4.1) does the work of maintaining backups in /var/backups for itself, checking first to see if there's already a backup in place. This is part of an attempt to retire /etc/cron.daily/standard and eliminate a redundant dependency - see bug #537073. The section in /etc/cron.daily/standard currently looks like this: -- #!/bin/sh [...] bak=/var/backups [...] # # Backup key system files # if cd $bak ; then cmp -s passwd.bak /etc/passwd || (cp -p /etc/passwd passwd.bak chmod 600 passwd.bak) cmp -s group.bak /etc/group || (cp -p /etc/group group.bak chmod 600 group.bak) if [ -f /etc/shadow ] ; then cmp -s shadow.bak /etc/shadow || (cp -p /etc/shadow shadow.bak chmod 600 shadow.bak) fi if [ -f /etc/gshadow ] ; then cmp -s gshadow.bak /etc/gshadow || (cp -p /etc/gshadow gshadow.bak chmod 600 gshadow.bak) fi fi if cd $bak ; then if ! cmp -s dpkg.status.0 /var/lib/dpkg/status ; then cp -p /var/lib/dpkg/status dpkg.status savelog -c 7 dpkg.status /dev/null fi fi [...] -- The new /etc/cron.daily/dpkg cronjob looks like this: -- #!/bin/sh # Backup the 7 last versions of dpkg's status file if cd /var/backups ; then if ! cmp -s dpkg.status.0 /var/lib/dpkg/status ; then cp -p /var/lib/dpkg/status dpkg.status savelog -c 7 dpkg.status /dev/null fi fi -- So you could create a /etc/cron.daily/passwd like this: -- #!/bin/sh # Back up the 7 last versions of passwd and related files if cd /var/backups ; then cmp -s passwd.bak /etc/passwd || (cp -p /etc/passwd passwd.bak chmod 600 passwd.bak) cmp -s group.bak /etc/group || (cp -p /etc/group group.bak chmod 600 group.bak) if [ -f /etc/shadow ] ; then cmp -s shadow.bak /etc/shadow || (cp -p /etc/shadow shadow.bak chmod 600 shadow.bak) fi if [ -f /etc/gshadow ] ; then cmp -s gshadow.bak /etc/gshadow || (cp -p /etc/gshadow gshadow.bak chmod 600 gshadow.bak) fi fi -- Or preferably something more like this: -- #!/bin/sh cd /var/backups || exit 0 for FILE in passwd group shadow gshadow; do test -f /etc/$FILE || continue cmp -s $FILE.bak /etc/$FILE continue install --preserve-context -pm 0600 /etc/$FILE $FILE.bak done -- But the point here is to get it under the control of the developers most likely to know better. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#553676: geeqie: Please provide a simple version that replaces gqview
Excuse me butting in; I'm just another longtime GQView user. In fact on Lenny I'm using Geeqie, but on Squeeze I had to switch back to avoid the extra dependencies. Michal Čihař wrote: GSR gsr.b...@infernal-iceberg.com napsal(a): With the migration from gqview to geeqie, lots of dependencies are pulled: map libs, gconf, clutter... Please provide some version that replaces gqview (a simple viewer that uses gtk, and not more) and make the rest be optional. What you think should stay in simple viewer? EXIF support? Color management? Lirc support? GPS support? All these are compile time optional external dependencies, which do bring additional libraries. It seems to me that none of these libraries are additional in the relevant sense: if I'm already using GQView/Geeqie on Lenny, all the dependencies needed for its functionality have already been satisfied. Even if I wasn't using GQView previously, installing it onto a Stable system that already has apps like Audacious or MPlayer or Iceweasel is unlikely to involve any _new_ library dependencies at all. It's only installing the Squeeze version of Geeqie that pulls in the long list of new, additional dependencies - gconf2, gnome-keyring, liborbit2, libsoup-gnome2.4-1... anybody willing to follow dependency chains like that one might as well use the standard GNOME-specific image viewer: sudo aptitude install eog is a smaller download! GQView's selling point was always that it was a desktop-neutral simple image viewer. If GQView is being retired, and Geeqie's not aiming for the same role, it would almost make more sense for the transition package to depend on one of the few remaining GTK+ graphics-directory browsers... maybe GPicView? -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537073: cron: unnecessary dependency on lockfile-progs
On Jul 14, 2009, Justin B Rye wrote: Further comments on the standard cronjobs: -- The dpkg in Squeeze now handles dpkg status file backups itself: http://packages.debian.org/changelogs/pool/main/d/dpkg/dpkg_1.15.4.1/changelog#versionversion1.15.4; If you can persuade the package passwd to take over the handling of its own backups then all that'll be left is the checks for fscked filesystems, which never had a good excuse for being in a cron.daily script in the first place. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551197: mgm: fails to launch on non-Linux ports
Package: mgm
Version: 1.1.svn.20080520-1
Severity: important
Unlike other graphical system-monitoring apps such as GKrellM, MGM
is available for kfreebsd-i386; but when I try to run it I just get:
Unable to open plugin directory /usr/share/mgm/modules/gnukfreebsd: No such
file or directory
The problem here is that $moddir is set from $Config{osname}, which
is no longer guaranteed to be linux.
There is a simple workaround: creating a gnukfreebsd - linux
symlink gets it mostly up and running. As it happens, using the
/usr/share/mgm/modules/netbsd in the source package would be _less_
useful, since it's just a cut-down copy of the linux moddir, and
some of the omitted modules do work thanks to the linprocfs support
on Debian's gnukfreebsd.
The alternative approach is just to stop calling it Architecture:
all. Or of course you could upgrade this bug to grave and get
the package RMed - after all it has a negligible popcon score and a
404ing homepage.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: kfreebsd-i386 (i686)
Kernel: kFreeBSD 7.2-1-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mgm depends on:
ii perl 5.10.1-5Larry Wall's Practical Extraction
ii perl-tk 1:804.028-6 Perl module providing the Tk graph
mgm recommends no packages.
mgm suggests no packages.
-- no debconf information
--
JBR
Ankh kak! (Ancient Egyptian blessing)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550086: doc-base: cobwebby description and dependencies
Package: doc-base
Version: 0.9.4
Severity: minor
Tags: patch
The control file for doc-base has:
# Suggests: dhelp | dwww | doc-central | yelp | khelpcenter, scrollkeeper
But scrollkeeper is a transition package to rarian-compat, and
khelpcenter has vanished entirely in favour of khelpcenter4.
Then in the package's long description:
# This package contains utilities to manage documentation installed on
# a Debian system. It contains a database of document metadata.
# Various third-party systems such as 'dwww', 'dhelp', 'doc-central'
# or 'scrollkeeper' use this data to provide a catalog of available
# documentation.
# .
# If you want to get additional information about 'doc-base' please
# consult the `Debian doc-base Manual' included in this package.
s/scrollkeeper/rarian-compat/ - it doesn't actually work, but that's
bug #546208.
While I'm making this tweak, there's other work to do. It isn't
literally true that the doc-base .deb file contains the
/var/lib/doc-base database - it just contains the software needed
to populate it. And what's third-party about the native Debian
packages dwww, dhelp and doc-central? Does it just mean not part
of this package? I'm going to rephrase a few things and filter out
the unnecessary spaces and quote-marks, like this:
This package contains utilities to manage documentation installed on
a Debian system. It generates a database of document metadata, which
other packages such as dwww, dhelp, doc-central, and rarian-compat
can use to provide a catalog of available documentation.
.
For additional information see the Debian doc-base Manual included in
this package.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.31.custom
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages doc-base depends on:
ii dpkg 1.15.3.1 Debian package management system
ii libmldbm-perl 2.01-3 Store multidimensional hash struct
ii libuuid-perl 0.02-3+b1 Perl extension for using UUID inte
ii perl 5.10.0-25 Larry Wall's Practical Extraction
doc-base recommends no packages.
Versions of packages doc-base suggests:
ii doc-central 1.8.2+nmu2 web-based documentation browser
ii dwww 1.11.1 Read all on-line documentation wit
ii rarian-compat [scrollkeeper] 0.8.1-4Documentation meta-data library (c
-- no debconf information
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ur doc-base-0.9.4.pristine/debian/control doc-base-0.9.4/debian/control
--- doc-base-0.9.4.pristine/debian/control 2009-09-10 18:08:45.0 +0100
+++ doc-base-0.9.4/debian/control 2009-10-07 14:19:58.0 +0100
@@ -8,15 +8,14 @@
Package: doc-base
Depends: ${perl:Depends}, libuuid-perl, dpkg (= 1.14.17), libmldbm-perl
-Suggests: dhelp | dwww | doc-central | yelp | khelpcenter, scrollkeeper
+Suggests: dhelp | dwww | doc-central | yelp | khelpcenter4, rarian-compat
Conflicts: dhelp ( 0.6.7), dwww ( 1.10.13~)
Architecture: all
Description: utilities to manage online documentation
This package contains utilities to manage documentation installed on
- a Debian system. It contains a database of document metadata.
- Various third-party systems such as 'dwww', 'dhelp', 'doc-central'
- or 'scrollkeeper' use this data to provide a catalog of available
- documentation.
+ a Debian system. It generates a database of document metadata, which
+ other packages such as dwww, dhelp, doc-central, and rarian-compat
+ can use to provide a catalog of available documentation.
.
- If you want to get additional information about 'doc-base' please
- consult the `Debian doc-base Manual' included in this package.
+ For additional information see the Debian doc-base Manual included in
+ this package.
Bug#549948: acpid: outdated package description
Package: acpid Version: 1.0.10-2 Severity: minor Tags: patch Lenny's acpid no longer requires /proc/acpi/event; but the package description is lagging behind. # Package: acpid # Description: Utilities for using ACPI power management Also, that's a strangely inaccurate synopsis: /usr/sbin/acpid is only one thing, and it isn't a utility. Use the same short description as the man page: Description: Advanced Configuration and Power Interface event daemon # Modern computers support the Advanced Configuration and Power Interface (ACPI) # to allow intelligent power management on your system and to query battery and # configuration status. # . # ACPID is a completely flexible, totally extensible daemon for delivering # ACPI events. It listens on a file (/proc/acpi/event) and when an event # occurs, executes programs to handle the event. The programs it executes # are configured through a set of configuration files, which can be # dropped into place by packages or by the admin. Update the reference to listening on /proc/acpi/event: [...] It listens on a netlink interface (or on the deprecated file /proc/acpi/event), and when an event occurs[...] If current Squeeze kernels don't have CONFIG_ACPI_PROC_EVENT then this version may be getting stale already, but it's slightly ahead of the man page. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages acpid depends on: ii libc6 2.9-25 GNU C Library: Shared libraries ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii module-init-tools 3.10-3 tools for managing Linux kernel mo Versions of packages acpid recommends: ii acpi-support-base 0.123-1scripts for handling base ACPI eve acpid suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru acpid-1.0.10.pristine/debian/control acpid-1.0.10/debian/control --- acpid-1.0.10.pristine/debian/control 2009-10-06 15:05:46.0 +0100 +++ acpid-1.0.10/debian/control 2009-10-06 15:09:50.0 +0100 @@ -18,13 +18,13 @@ lsb-base (= 3.2-14), module-init-tools (= 3.1-rel-2ubuntu2) Recommends: acpi-support-base -Description: Utilities for using ACPI power management +Description: Advanced Configuration and Power Interface event daemon Modern computers support the Advanced Configuration and Power Interface (ACPI) to allow intelligent power management on your system and to query battery and configuration status. . ACPID is a completely flexible, totally extensible daemon for delivering - ACPI events. It listens on a file (/proc/acpi/event) and when an event - occurs, executes programs to handle the event. The programs it executes - are configured through a set of configuration files, which can be - dropped into place by packages or by the admin. + ACPI events. It listens on a netlink interface (or on the deprecated file + /proc/acpi/event), and when an event occurs, executes programs to handle the + event. The programs it executes are configured through a set of configuration + files, which can be dropped into place by packages or by the admin.
Bug#549948: acpid: outdated package description
Justin B Rye wrote: Lenny's acpid no longer requires /proc/acpi/event; but the package s/Lenny/Testing/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549977: gsfonts: out-of-date package description
Package: gsfonts Version: 1:8.11+urwcyr1.0.7~pre44-4 Severity: minor Tags: patch I've been going through the archives looking for package descriptions in need of routine maintenance. Package: gsfonts Description: Fonts for the Ghostscript interpreter(s) These are free look-alike fonts of the Adobe PostScript fonts. Recommended for all flavors of Ghostscript (gs-gpl, gs-afpl and gs-esp). Those flavours no longer exist (even in Oldstable). Fixing that along with some trivial DevRef6.2.2-compliance tweaks, I'd suggest: Description: fonts for the Ghostscript interpreter This package provides free look-alikes for Adobe's PostScript fonts, recommended for use with Ghostscript. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gsfonts depends on: ii defoma0.11.10-1 Debian Font Manager -- automatic f gsfonts recommends no packages. gsfonts suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru gsfonts-8.11+urwcyr1.0.7~pre44.pristine/debian/control gsfonts-8.11+urwcyr1.0.7~pre44/debian/control --- gsfonts-8.11+urwcyr1.0.7~pre44.pristine/debian/control 2009-10-06 19:51:47.0 +0100 +++ gsfonts-8.11+urwcyr1.0.7~pre44/debian/control 2009-10-06 19:53:21.0 +0100 @@ -14,6 +14,6 @@ Architecture: all Depends: defoma (= 0.11.10) Conflicts: gs ( 5.50-5), gs-aladdin ( 6.50-4), gsfonts-x11 ( 0.13) -Description: Fonts for the Ghostscript interpreter(s) - These are free look-alike fonts of the Adobe PostScript fonts. - Recommended for all flavors of Ghostscript (gs-gpl, gs-afpl and gs-esp). +Description: fonts for the Ghostscript interpreter + This package provides free look-alikes for Adobe's PostScript fonts, + recommended for use with Ghostscript.
Bug#549872: ace-of-penguins: incomplete list in package description
Package: ace-of-penguins
Version: 1.2-9
Severity: minor
Tags: patch
The package description fails to mention canfield and thornq:
Package: ace-of-penguins
Description: Solitaire-games with penguin-look
The Ace of Penguins is a set of Unix/X solitaire games based on the
ones available for Windows(tm) but with a number of enhancements.
.
The package consists of the games Pegged, Minesweeper, Solitaire,
Taipei (together with a level editor), Golf, Mastermind, Merlin and
Freecell.
This description has some other slightly odd features - what's a
penguin-look? Why bother mentioning that it works on Unix/X? Why
say (tm) for a brand name that's actually an (R)? And what sort
of order is that list in? So while I'm rewriting it I'd suggest:
Description: penguin-themed solitaire games
The Ace of Penguins is a set of solitaire games inspired by the ones
available for MS Windows, but with a number of enhancements.
.
The package consists of the games Canfield, Freecell, Golf, Mastermind,
Merlin, Minesweeper, Pegged, Solitaire, Taipei (with a level editor),
and Thornq.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30.custom
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ace-of-penguins depends on:
ii libc6 2.9-25GNU C Library: Shared libraries
ii libpng12-0 1.2.39-1 PNG library - runtime
ii libx11-6 2:1.2.2-1 X11 client-side library
ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime
ace-of-penguins recommends no packages.
ace-of-penguins suggests no packages.
-- no debconf information
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru ace-of-penguins-1.2.pristine/debian/control ace-of-penguins-1.2/debian/control
--- ace-of-penguins-1.2.pristine/debian/control 2009-10-05 23:21:45.0 +0100
+++ ace-of-penguins-1.2/debian/control 2009-10-05 23:23:40.0 +0100
@@ -11,10 +11,10 @@
Package: ace-of-penguins
Architecture: any
Depends: ${shlibs:Depends}
-Description: graphical solitaire-games with penguin-look
- The Ace of Penguins is a set of graphical solitaire games based on the
- ones available for Windows(tm) but with a number of enhancements.
+Description: penguin-themed solitaire games
+ The Ace of Penguins is a set of solitaire games inspired by the ones
+ available for MS Windows, but with a number of enhancements.
.
- The package consists of the games Pegged, Minesweeper, Solitaire,
- Taipei (together with a level editor), Golf, Mastermind, Merlin and
- Freecell.
+ The package consists of the games Canfield, Freecell, Golf, Mastermind,
+ Merlin, Minesweeper, Pegged, Solitaire, Taipei (with a level editor),
+ and Thornq.
Bug#549450: moreutils: package description futureproofing for 1980
Package: moreutils Version: 0.37+b1 Severity: wishlist Tags: patch I'm aware that the package description is getting regular attention to update its list of goodies, but just in case you haven't noticed: This is a growing collection of the unix tools that nobody thought to write thirty years ago. When written that was pointing at the mid-seventies; soon it'll have drifted to point at the eighties. I recommend naming the decade. By the way, is there a reason behind the ordering of the list or would it make sense to sort it alphabetically? I attach a second, even more optional patch that does that too. Thanks for maintaining moreutils! -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages moreutils depends on: ii libc6 2.9-25 GNU C Library: Shared libraries ii perl 5.10.0-25 Larry Wall's Practical Extraction moreutils recommends no packages. Versions of packages moreutils suggests: ii libtime-duration-perl 1.06-1 Time::Duration -- rounded or exact ii libtimedate-perl 1.1600-9 Time and date functions for Perl -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru moreutils-0.37.pristine/debian/control moreutils-0.37/debian/control --- moreutils-0.37.pristine/debian/control 2009-07-25 09:18:38.0 +0100 +++ moreutils-0.37/debian/control 2009-10-03 13:40:54.0 +0100 @@ -15,7 +15,7 @@ Replaces: lckdo Description: additional unix utilities This is a growing collection of the unix tools that nobody thought - to write thirty years ago. + to write back in the seventies. . So far, it includes the following utilities: - sponge: soak up standard input and write to a file diff -ru moreutils-0.37.pristine/debian/control moreutils-0.37/debian/control --- moreutils-0.37.pristine/debian/control 2009-07-25 09:18:38.0 +0100 +++ moreutils-0.37/debian/control 2009-10-03 13:58:45.0 +0100 @@ -15,19 +15,19 @@ Replaces: lckdo Description: additional unix utilities This is a growing collection of the unix tools that nobody thought - to write thirty years ago. + to write back in the seventies. . So far, it includes the following utilities: - - sponge: soak up standard input and write to a file + - combine: combine the lines in two files using boolean operations - ifdata: get network interface info without parsing ifconfig output - ifne: run a program if the standard input is not empty - - vidir: edit a directory in your text editor - - vipe: insert a text editor into a pipe - - ts: timestamp standard input - - combine: combine the lines in two files using boolean operations - - pee: tee standard input to pipes - - zrun: automatically uncompress arguments to command - - mispipe: pipe two commands, returning the exit status of the first - isutf8: check if a file or standard input is utf-8 - lckdo: execute a program with a lock held + - mispipe: pipe two commands, returning the exit status of the first - parallel: run multiple jobs at once + - pee: tee standard input to pipes + - sponge: soak up standard input and write to a file + - ts: timestamp standard input + - vidir: edit a directory in your text editor + - vipe: insert a text editor into a pipe + - zrun: automatically uncompress arguments to command
Bug#549457: x11-apps: flawed package description
Package: x11-apps Version: 7.4+2 Severity: wishlist Tags: patch The current package description has two problems. Its first paragraph is a relic of the days when these apps were in xbase-clients: An X client is a program that interfaces with an X server (almost always via the X libraries), and thus with some input and output hardware like a graphics card, monitor, keyboard, and pointing device (such as a mouse). This explanation of what an X client is became pointless when the word client disappeared from the package name, so I recommend just throwing out the whole paragraph. Second, three of the listed apps (bitmap, xcursorgen, and xmore) have no descriptions. In the case of bitmap, this looks like the result of an editing error, since the line ends with a comma and trailing whitespace rather than a semicolon, and since its associates atobm and bmtoa have fallen off the list entirely. My patch gives them the following suggested descriptions: - atobm, bitmap, and bmtoa, tools for manipulating bitmap images; - xcursorgen, a tool for creating X cursor files from PNGs; - xmore, a text pager; -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages x11-apps depends on: ii cpp 4:4.3.3-9 The GNU C preprocessor (cpp) ii libc6 2.9-25 GNU C Library: Shared libraries ii libpng12-01.2.39-1 PNG library - runtime ii libsm62:1.1.1-1 X11 Session Management library ii libx11-6 2:1.2.2-1 X11 client-side library ii libxaw7 2:1.0.6-1 X11 Athena Widget library ii libxcursor1 1:1.1.9-1 X cursor management library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxft2 2.1.13-3 FreeType-based font drawing librar ii libxkbfile1 1:1.0.5-1 X11 keyboard file manipulation lib ii libxmu6 2:1.0.4-2 X11 miscellaneous utility library ii libxmuu1 2:1.0.4-2 X11 miscellaneous micro-utility li ii libxrender1 1:0.9.4-2 X Rendering Extension client libra ii libxt61:1.0.6-1 X11 toolkit intrinsics library ii x11-common1:7.4+4X Window System (X.Org) infrastruc x11-apps recommends no packages. Versions of packages x11-apps suggests: ii mesa-utils7.5.1-1Miscellaneous Mesa GL utilities -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru x11-apps-7.4+2.pristine/debian/control x11-apps-7.4+2/debian/control --- x11-apps-7.4+2.pristine/debian/control 2009-07-27 18:20:42.0 +0100 +++ x11-apps-7.4+2/debian/control 2009-10-03 14:58:50.0 +0100 @@ -48,19 +48,15 @@ xcalc, xclipboard, xclock, xconsole, xcursorgen, xditview, xeyes, xgc, xload, xlogo, xmag, xman, xmore, xwd, xwud Description: X applications - An X client is a program that interfaces with an X server (almost always via - the X libraries), and thus with some input and output hardware like a - graphics card, monitor, keyboard, and pointing device (such as a mouse). - . This package provides a miscellaneous assortment of X applications that ship with the X Window System, including: - - bitmap, + - atobm, bitmap, and bmtoa, tools for manipulating bitmap images; - oclock and xclock, graphical clocks; - xbiff, a tool which tells you when you have new email; - xcalc, a scientific calculator desktop accessory; - xclipboard, a tool to manage cut-and-pasted text selections; - xconsole, which monitors system console messages; - - xcursorgen; + - xcursorgen, a tool for creating X cursor files from PNGs; - xditview, a viewer for ditroff output; - xedit, a simple text editor for X; - xeyes, a demo program in which a pair of eyes track the pointer; @@ -69,7 +65,7 @@ - xlogo, a demo program that displays the X logo; - xmag, which magnifies parts of the X screen; - xman, a manual page browser; - - xmore; + - xmore, a text pager; - xwd, a utility for taking window dumps (screenshots) of the X session; - xwud, a viewer for window dumps created by xwd; - Xmark, x11perf, and x11perfcomp, tools for benchmarking graphical
Bug#549327: insserv: new package description, new grammar errors
Package: insserv
Version: 1.12.0-11
Severity: minor
Tags: patch
(Also found in -12, -13, -14)
Thanks for keeping the insserv package description up-to-date!
Unfortunately, the new version needs some reanglification.
Description: Tool to organize boot sequence using LSB init.d script
dependencies
The capital T is a regression - what was wrong with Lenny's
DevRef6.2.2-compliant boot sequence organizer using [...]?
The insserv program is used to update the order of symlinks in
/etc/rc?.d/ with sysv-rc based on dependencies specified in the
scripts themselves using LSB init.d script headers.
I can't tell what with sysv-rc is intended to mean here -
• update the order of symlinks by using the package sysv-rc?
• update the order of symlinks with regard to the package sysv-rc?
• update the order of symlinks on a system with the package sysv-rc?
The best I can do in my revised version is rip it out and hope I'm
not losing anything important.
(Incidentally, sysv-rc isn't the world's most self-explanatory
package name. The sysv part means a legacy of UNIX System V,
which isn't very illuminating, and RC doesn't stand for any of
the things a novice might guess. In fact there's no consensus on
what the C does stand for - Change? Control? Configuration?)
.
This allow each package maintainer to specify their init.d script
relation to other scripts and make it possible to detect and reject
script dependency loops as well as making sure all scripts start in
their intended order.
You've got your favourite minor grammar glitch in the second word:
you want third-person-present-singular agreement, allowS (likewise
later and makeS it possible). Then there's a missing possessive
(or similar), and I think you mean their relationS with others.
The whole allows X and makes Y possible as well as making sure that
Z is a bit ungainly anyway.
My patch changes it so that it's telling end users why insserv
should be installed on their system, not giving packaging advice to
Debian developers.
.
The program insserv in this package should be used with care and
together with the sysv-rc package, as using it incorrectly can lead
to an unbootable system.
The together with the sysv-rc package seems to be trying to do the
job of a Breaks: file-rc dependency... though I suppose it's
possible to have file-rc and insserv installed together as long as
you don't run /sbin/insserv. But the people who need to be warned
about that are people who already have file-rc plus sysv-rc and who
now get insserv pulled in during an apt-get upgrade. Those people
won't see the warning in insserv's package description; they'll have
to depend on there being code in insserv that checks for a
compatible system and squawks if anything is wrong.
My suggested version:
Description: boot sequence organizer using init.d script dependencies
The insserv program is used by the standard SysV-based init system. It
updates the order of symlinks in /etc/rc?.d/ based on dependencies
specified by LSB headers in the init.d scripts themselves.
.
These declared relations between scripts make it possible to optimize
the boot sequence for the currently installed set of packages, while
detecting and rejecting dependency loops.
.
Using insserv incorrectly can result in an unbootable system.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30.custom
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages insserv depends on:
ii libc6 2.9-25 GNU C Library: Shared libraries
insserv recommends no packages.
Versions of packages insserv suggests:
ii bootchart0.10~svn407-3.1 Boot process performance analyser
-- debconf information:
* insserv/enable: true
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru insserv-1.12.0.pristine/debian/control insserv-1.12.0/debian/control
--- insserv-1.12.0.pristine/debian/control 2009-10-01 16:50:56.0 +0100
+++ insserv-1.12.0/debian/control 2009-10-02 14:33:32.0 +0100
@@ -15,16 +15,13 @@
Depends: ${shlibs:Depends}, ${misc:Depends}
Suggests: bootchart
Breaks: sysv-rc ( 2.87dsf-3)
-Description: Tool to organize boot sequence using LSB init.d script dependencies
- The insserv program is used to update the order of symlinks in
- /etc/rc?.d/ with sysv-rc based on dependencies specified in the
- scripts themselves using LSB init.d script headers.
+Description: boot sequence organizer using LSB init.d script dependencies
+ The insserv program is used by the standard SysV-based init system. It
+ updates the order of symlinks in /etc/rc?.d/ based on dependencies
+ specified by LSB headers in the init.d scripts themselves.
.
- This allow each package maintainer to specify their init.d script
- relation to other scripts and make it possible to detect and reject
-
Bug#492536: No new package
Nacho Barrientos Arias wrote: The package is maintained but I don't intend to prepare a new upload fixing _only_ this minor spelling mistake. Pardon me for sticking my oar in here; I'd like to point out that the spelling mistake in question is arguable anyway, and is sitting right next to another, similar mistake which is less arguable. My patch barely registers as minor; in my view the maintainer is quite entitled to regard it as wishlist. Current version: # This GUI only needs an URL to a RDF file storing SIOC forums # information to start browsing and searching into it. This implies the pronunciation an url (homophonous with earl) rather than a U.R.L. (you ar el). U.R.L. is more widely used, but url is not a mistake; I know people who really say that. However, a RDF file is a mistake; there's universal agreement that it's pronounced as ar dee eff, so it requires an. The package description also has a couple of slightly awkward features that make it obvious that it was written by a non-native English-speaker, but I'm not sure I'd bother fixing them even if the package passed through debian-l10n-english for a review. -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru buxon-0.0.4.pristine/debian/control buxon-0.0.4/debian/control --- buxon-0.0.4.pristine/debian/control 2009-09-24 11:24:36.0 +0100 +++ buxon-0.0.4/debian/control 2009-09-24 11:49:55.0 +0100 @@ -14,5 +14,5 @@ Archive of Mailing Lists) project, provides a graphical user interface which helps you to browse SIOC forums. . - This GUI only needs an URL to a RDF file storing SIOC forums + This GUI only needs a URL to an RDF file storing SIOC forums information to start browsing and searching into it.
Bug#548214: abby: should use sane defaults
Package: abby Version: 0.4.3-1 Severity: minor When launched, abby presents the user with an interactive dialog asking for the locations of the cclive/clive binaries. This is unnecessary; the package depends on cclive | clive, so it should simply try cclive (wherever that is on my $PATH), and fall back on clive (ditto) if cclive isn't available. Likewise, if I cd to down/here/where/my/videos/go and invoke abby, it's annoying to need to tell it I want to store the downloads in /home/jbr/down/here/where/my/videos/go when my $PWD already provides a perfectly good default (falling back on $HOME if not available). If you don't want to do that, there's the alternative of following 'http://standards.freedesktop.org/basedir-spec-latest.html'. By all means allow these defaults to be overridden by environmental variables or config-file settings or Preferences menu-items, but please do not turn downloading videos into a quiz on the FHS. Incidentally, does anybody know why abby is called abby? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages abby depends on: ii cclive0.5.0-2lightweight command line video ext ii clive 2.2.5-1video extraction utility for YouTu ii libc6 2.9-25 GNU C Library: Shared libraries ii libgcc1 1:4.4.1-1 GCC support library ii libqt4-network4:4.5.2-2 Qt 4 network module ii libqt4-xml4:4.5.2-2 Qt 4 XML module ii libqtcore44:4.5.2-2 Qt 4 core module ii libqtgui4 4:4.5.2-2 Qt 4 GUI module ii libstdc++64.4.1-1The GNU Standard C++ Library v3 abby recommends no packages. abby suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547439: piuparts: typo in NEWS.Debian
Package: piuparts Version: 0.36 Severity: wishlist Tags: patch piuparts (0.36) unstable; urgency=low * piuparts 0.36 introduces many changes to master-slave mode, please read debian/changelog carefully. * Backwards compatibility of the configuration files for master-slave-mode has been broken, as the three config files got merged into one: /etc/piuparts/piuparts/piuparts.conf ^^ I'm very much hoping you mean /etc/piuparts/piuparts.conf! -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages piuparts depends on: ii apt0.7.23.1 Advanced front-end for dpkg ii debootstrap1.0.15Bootstrap a basic Debian system ii lsb-release3.2-23Linux Standard Base version report ii lsof 4.81.dfsg.1-1 List open files ii python 2.5.4-2 An interactive high-level object-o ii python-debian 0.1.14Python modules to work with Debian piuparts recommends no packages. Versions of packages piuparts suggests: ii ghostscript 8.70~dfsg-2 The GPL Ghostscript PostScript/PDF pn python-rpy none (no description available) -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru piuparts-0.36.pristine/debian/NEWS piuparts-0.36/debian/NEWS --- piuparts-0.36.pristine/debian/NEWS 2009-03-20 12:33:51.0 + +++ piuparts-0.36/debian/NEWS 2009-09-19 19:17:08.0 +0100 @@ -4,7 +4,7 @@ debian/changelog carefully. * Backwards compatibility of the configuration files for master-slave-mode has been broken, as the three config files got merged into one: -/etc/piuparts/piuparts/piuparts.conf +/etc/piuparts/piuparts.conf * piuparts-reports has been re-added and improved. * The documentation files have been merged and converted to asciidoc.
Bug#523372: consolekit: Couldn't read /proc/'pid_number'/environ
notforwarded 523372 tags 523372 tag - upstream wontfix stop On Sat, Sep 05, Justin B Rye wrote: This message still occurs every time ConsoleKit starts. Why has the bug report been tagged upstream wontfix? Ah! I'd missed the fact that it claimed to have been forwarded to https://bugzilla.redhat.com/show_bug.cgi?id=444139;. Or maybe I'd read it and forgotten it because it's so obviously a mistake: that report had seen no new activity since May 2008. That's also why it's wontfix - the bug was last seen in ConsoleKit-0.2.10-3.fc9. Nobody mentioned having seen it in anything more recent, so the report just rotted away when Fedora 9 reached end-of-life. And bts-link automatically passed that wontfix on to the Debian bug. But Debian bug #523372 was originally seen in ConsoleKit 0.3.0-2, and is still present in 0.3.0-4; that's the same upstream version number as the ConsoleKit in Fedora 10 and 11. Somebody with a RedHat Bugzilla login needs to submit a new report, as was requested here: https://bugzilla.redhat.com/show_bug.cgi?id=444139#c6;. Until that happens, this issue has not been forwarded, and upstream has been given no opportunity to declare it wontfix. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547143: xserver-xorg: xorg/evdev/HAL versus serial mouse
Package: xserver-xorg Version: 1:7.4+4 Severity: wishlist I'm calling this wishlist because I've eventually managed to get X working again; it's essentially a documentation issue. As NEWS.Debian says, devices configured in xorg.conf to use the mouse or kbd driver are ignored by the X server by default. I'm meant to switch over to HAL and evdev. That's all very well for you kids with your shiny twentyfirst-century laptops, but unfortunately, this old machine has no PS/2 ports. It uses an AT-port keyboard (which evdev is happy to recognise as an input device) and a serial mouse (which is apparently ignored). I don't see any mention of this issue in the docs, so I thought I'd better report it and the workaround I'm using. The xorg.conf below gets X to work as normal again with a minimum of complaining - though it also requires HAL to be disabled via an exit 0 at the top of the init.d script. In principle there's probably some alternative involving writing appropriate custom .fdi files, but if I could work out how to do that sort of thing I'd be busy using my mutant psychic powers to fight superpowered criminals like the rest of you X-developers! HAL has no discernible reason for being present on this box, so I'm just nobbling it. Note that just disabling HAL and AutoAddDevices wasn't enough - I've had to put lots more lines back in my xorg.conf that I'd previously been leaving to the defaults. Many thanks for providing /usr/share/doc/xserver-xorg/examples/xorg.conf! If it has been decided that xorg no longer supports serial mice, that's fine; just make sure the announcement gets into the Squeeze release notes. Otherwise, please document somewhere the approved method for keeping them working - the obvious place would be a NEWS.Debian file for xserver-xorg-input-mouse. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2009-08-10 17:18 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1689976 2009-08-06 17:55 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400/G450 (rev 05) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1072 2009-09-16 14:55 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: #jbr comments like -*- sh -*- # cf: /usr/share/doc/xserver-xorg/examples/xorg.conf Section ServerFlags Option AutoAddDevicesFalse Option AutoEnableDevices False EndSection Section InputDevice Identifier Keyboard Driver kbd Option CoreKeyboard Option XkbLayout gb EndSection Section InputDevice Identifier Mouse Driver mouse Option CorePointer Option Device/dev/ttyS0 Option Protocol MouseMan EndSection Section Device Identifier Video Card Option UseFBDev False EndSection Section Monitor Identifier Monitor HorizSync 30-82 VertRefresh 30-100 EndSection Section Screen Identifier Screen Device Video Card Monitor Monitor SubSection Display Modes 1280x1024 EndSubSection EndSection Section ServerLayout Identifier Layout Screen Screen InputDevice Keyboard InputDevice Mouse EndSection #/jbr Xorg X server log files on system: -rw-r- 1 root adm 30175 2009-09-16 14:54 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.6.3 Release Date: 2009-7-31 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.30.4-dsa-ia32 i686 Debian Current Operating System: Linux xan 2.6.30.custom #1 Sun Aug 16 16:07:03 BST 2009 i586 Build Date: 06 August 2009 04:49:57PM xorg-server 2:1.6.3-1+b1 (bui...@murphy.debian.org) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Sep 16 14:47:02 2009 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Layout (**) |--Screen Screen (0) (**) | |--Monitor Monitor (**) | |--Device Video Card (**) |--Input Device Keyboard (**) |--Input Device Mouse (**) Option AutoAddDevices False (**) Option AutoEnableDevices False (**) Not automatically adding devices (**) Not automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font
Bug#546986: glhack: No write permission to lock /var/games/glhack/perm!
Stefan Ritter wrote: To: 546...@bugs.debian.org By the way, at present mail to the bug doesn't automatically go to the submitter. Fortunately this is likely to be changed soon: http://lists.debian.org/debian-devel/2009/09/msg00422.html you're right. You could put yourself in group 'games' until I fix it in the next version ;). Ah, but then I can copy/overwrite save files. Obviously, if I can install it I've got root privileges anyway, but somehow I can resist the temptation to cheat when it involves typing in a password... -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547143: xserver-xorg: xorg/evdev/HAL versus serial mouse
Julien Cristau wrote: On Thu, Sep 17, 2009 at 09:48:53 +0100, Justin B Rye wrote: [...] Note that just disabling HAL and AutoAddDevices wasn't enough - I've had to put lots more lines back in my xorg.conf that I'd previously been leaving to the defaults. Many thanks for providing /usr/share/doc/xserver-xorg/examples/xorg.conf! That's weird. I'd have expected that disabling AutoAddDevices would make things work with the old xorg.conf InputDevice section (once that is done, keeping hal running or stopping it shouldn't make a difference). This machine's due to be decommissioned soon anyway, so I'm hurrying through some more tests while it's still available. I've switched to a standard Debian kernel in case there are any driver issues. Summarised findings: * I was getting interference from a buggy display manager * other display managers (or startx) allow hal+serialmouse * hal, the kbd driver, and Ctrl-Alt-Backspace interact badly Details: The first thing I tried was disabling my display manager, de-lobotomising HAL and running startx. This works! Well, except that DontZap appears to be in effect, contrary to my instructions. Yes, I edited the xorg.conf and reconfigured console-setup and restarted hal and rebooted for luck. Still nothing. But that's only a mild annoyance for now. It's only when I use wdm that everything goes haywire. My first ten tries go like this: * wdmLogin seems happy then segfaults halfway through launching a session, spewing some really strange syslog messages. * Works perfectly. * Works perfectly. * An amusing failure mode where my attempt to enter a username results in it doing that shaking the box to indicate a wrong password thing that gets more and more frenzied until it crashes. * Works except that it doesn't recognise the Enter key. Useless. Where's my goddamn Ctrl-Alt-Backspace?! * Works perfectly. * Works perfectly. * Segfaults on the middle letter of my username. * Logs me in rather slowly, but otherwise works. * Works perfectly. Plain xdm works fine too. So it looks as if switching from wdm to xdm would let me keep hal running on this hardware... if I had some reason to want hal. Now, if I temporarily move my xorg.conf out of the way and rely on the defaults (and hal), then startx, xdm, and wdm all work equally well. The resolution's hopeless, the serial mouse is missing, but nothing segfaults, I've got a GB keymap, and Ctrl-Alt-Backspace works. Hmmm. Whoops! On my last try of ten, wdmLogin segfaults with a rush of nasty kernel errors about secondary DMA buffers. So wdm seems to be just plain flaky, and I should go and submit a proper bugreport for it. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547251: wdm: segfaults
Package: wdm Version: 1.28-3.1 Severity: important To be specific, /usr/bin/wdmLogin segfaults. See symptoms described in this bugreport against xserver-xorg: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547143#15 ...and especially this bit: It's only when I use wdm that everything goes haywire. My first ten tries go like this: * wdmLogin seems happy then segfaults halfway through launching a session, spewing some really strange syslog messages. * Works perfectly. * Works perfectly. * An amusing failure mode where my attempt to enter a username results in it doing that shaking the box to indicate a wrong password thing that gets more and more frenzied until it crashes. * Works except that it doesn't recognise the Enter key. Useless. Where's my goddamn Ctrl-Alt-Backspace?! * Works perfectly. * Works perfectly. * Segfaults on the middle letter of my username. * Logs me in rather slowly, but otherwise works. * Works perfectly. Syslog is full of this sort of stuff: Sep 17 19:16:12 xan wdm: (EE) MGA(0): [drm] Could not boot-strap DMA (-16) Sep 17 19:16:12 xan wdm: SELinux: Disabled on system, not enabling in X server Sep 17 19:16:14 xan wdm: (EE) XKB: No components provided for device Virtual core keyboard Sep 17 19:16:14 xan wdm: /etc/X11/wdm/Xresources_0: 1: /etc/X11/wdm/Xresources_0: Permission denied Sep 17 19:16:14 xan wdm: /etc/X11/wdm/Xresources_0: 2: Syntax error: newline unexpected Sep 17 19:16:14 xan wdm: Cannot open config file. Using builtin defaults Sep 17 19:16:14 xan wdm: wdmLogin warning: WINGs: could not load widget images file: could not open file Sep 17 19:16:17 xan kernel: wdmLogin[4810]: segfault at 33 ip b7f9ac43 sp bfb4c53c error 4 in libX11.so.6.2.0[b7f0e000+118000] Sep 17 19:16:17 xan xan : Greet: guarenteed_read error, UNMANAGE DISPLAY Sep 17 19:16:17 xan xan : Greet: pipe read error with /usr/bin/wdmLogin (xan is the hostname - I've no idea what's going on with the xan xan messages talking about wdmLogin.) This is a clean install of wdm with no config changes. The failures occur less often (but still occasionally) when no special options have been set in xorg.conf; and they don't occur at all with xdm or startx. Just to be sure it wasn't my graphics drivers that were the problem I switched out the Matrox Marvel in favour of an antique S3ViRGE graphic decelerator card (and booted a standard Debian kernel), but still: Sep 17 20:18:11 xan xan : Greet: guarenteed_read error, UNMANAGE DISPLAY Sep 17 20:18:11 xan kernel: [ 912.292884] wdmLogin[3826]: segfault at 33 ip b7ee8c43 sp bfa5455c error 4 in libX11.so.6.2.0[b7e5c000+118000] Sep 17 20:18:11 xan xan : Greet: pipe read error with /usr/bin/wdmLogin (Further information is unlikely to be available for a while since I'm retiring this machine.) -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wdm depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii libc6 2.9-25 GNU C Library: Shared libraries ii libfontconfig12.6.0-4generic font configuration library ii libice6 2:1.0.5-1 X11 Inter-Client Exchange library ii libpam-modules1.0.1-10 Pluggable Authentication Modules f ii libpam-runtime1.0.1-10 Runtime support for the PAM librar ii libpam0g 1.0.1-10 Pluggable Authentication Modules l ii libsm62:1.1.1-1 X11 Session Management library ii libwraster3 0.92.0-8.1 Shared libraries of Window Maker r ii libx11-6 2:1.2.2-1 X11 client-side library ii libxau6 1:1.0.4-2 X11 authorisation library ii libxdmcp6 1:1.0.2-3 X11 Display Manager Control Protoc ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxft2 2.1.13-3 FreeType-based font drawing librar ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library ii libxmu6 2:1.0.4-2 X11 miscellaneous utility library ii psmisc22.8-1 utilities that use the proc file s ii x11-apps 7.4+2 X applications ii x11-common1:7.4+4X Window System (X.Org) infrastruc ii x11-xserver-utils 7.4+2 X server utilities ii xutils1:7.4+4X Window System utility programs m wdm recommends no packages. Versions of packages wdm suggests: ii xfonts-base 1:1.0.0-6 standard fonts for X -- debconf information: * shared/default-x-display-manager: wdm wdm/daemon_name:
Bug#486370: samba4: outdated package description
On Sun, September 5,402 1993, Justin B Rye wrote: The references to LanManager in the short descriptions of so many samba packages are unhelpful. The Samba (3) suite has had a facelift, but Samba4 has now entered Sid with its old package descriptions intact, full of early-nineties topical references like LanManager and OS/2 and the next generation... Samba 3: SMB/CIFS file, print, and login server for Unix Samba 4: LanManager-like file server for Unix (version 4) They also still label the suite as _experimental_ and not ready for real use. Is this still true? Will it be true when Samba4 is a candidate for release in Squeeze? If not, you're going to have to change the package descriptions anyway, so please bring them in line with Samba's. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546986: glhack: No write permission to lock /var/games/glhack/perm!
Package: glhack Version: 1.2-1 Severity: normal $ sudo apt-get install glhack Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed glhack 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/1,651kB of archives. After this operation, 3,072kB of additional disk space will be used. Reading package fields... Done Reading package status... Done Retrieving bug reports... Done Parsing Found/Fixed information... Done Selecting previously deselected package glhack. (Reading database ... 121622 files and directories currently installed.) Unpacking glhack (from .../archives/glhack_1.2-1_i386.deb) ... Processing triggers for menu ... Processing triggers for man-db ... Setting up glhack (1.2-1) ... Processing triggers for menu ... $ $ glhack Warning: cannot write scoreboard file /var/games/glhack/record -- glHack: Autodetected video depth: 32 bits per pixel. -- glHack: Autodetected 21 different video modes. -- glHack: Selected 800x600... No write permission to lock /var/games/glhack/perm! $ $ ls -dl /var/games/glhack/* /usr/games/glhack -rwxr-xr-x 1 root root45 2009-09-10 14:30 /usr/games/glhack -rw-rwSr-- 1 root games0 2009-09-10 14:30 /var/games/glhack/logfile -rw-rwSr-- 1 root games0 2009-09-10 14:30 /var/games/glhack/perm -rw-rwSr-- 1 root games0 2009-09-10 14:30 /var/games/glhack/record drwxrwsr-x 2 root games 4096 2009-09-10 14:30 /var/games/glhack/save Does the glhack binary maybe need to be setgid games, like nethack-console etcetera? I see there are dpkg-statoverride calls in /var/lib/dpkg/info/glhack.postinst, but none of them touch the binary. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages glhack depends on: ii libc6 2.9-25GNU C Library: Shared libraries ii libgl1-mesa-glx [libgl 7.5.1-1 A free implementation of the OpenG ii libpng12-0 1.2.39-1 PNG library - runtime ii libsdl1.2debian1.2.13-4+b1 Simple DirectMedia Layer ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime glhack recommends no packages. glhack suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546458: dash: outdated package description
Package: dash
Version: 0.5.5.1-2.3
Severity: wishlist
Tags: patch
Dash has the following description:
Description: POSIX-compliant shell
The Debian Almquist Shell (dash) is a lightweight POSIX-compliant shell
derived from ash.
.
It can be usefully installed as /bin/sh (because it executes scripts
faster than bash), or as the default shell for the superuser. It
depends on fewer libraries than bash, and is therefore less likely to
be affected by an upgrade problem or a disk failure. It is also
useful for checking the POSIX compliance of scripts.
That was a good summary of its status in Lenny (itself an update
from the version in Etch), but it doesn't really fit its current
status as an Essential package. My suggestion would be:
Description: lightweight standard shell
The Debian Almquist Shell (dash) is a POSIX-compliant shell derived
from ash.
.
Since it executes scripts faster than bash, and has fewer library
dependencies (making it more robust against software or hardware
failures), it is used as the default system shell on Debian systems.
(But obviously, feel free to throw out my version if you've got
better ideas.)
By the way, while I'm looking at the control file: ash was already a
transition package in Sarge, and Woody-to-Squeeze upgrades aren't
supported, so isn't it about time it was retired?
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ur dash-0.5.5.1.pristine/debian/control dash-0.5.5.1/debian/control
--- dash-0.5.5.1.pristine/debian/control 2009-09-12 22:19:11.0 +0100
+++ dash-0.5.5.1/debian/control 2009-09-12 22:30:40.0 +0100
@@ -13,15 +13,13 @@
Priority: required
Pre-Depends: ${shlibs:Depends}
Depends: debianutils (= 2.15), dpkg (= 1.15.0)
-Description: POSIX-compliant shell
- The Debian Almquist Shell (dash) is a lightweight POSIX-compliant shell
- derived from ash.
+Description: lightweight standard shell
+ The Debian Almquist Shell (dash) is a POSIX-compliant shell derived
+ from ash.
.
- It can be usefully installed as /bin/sh (because it executes scripts
- faster than bash), or as the default shell for the superuser. It
- depends on fewer libraries than bash, and is therefore less likely to
- be affected by an upgrade problem or a disk failure. It is also
- useful for checking the POSIX compliance of scripts.
+ Since it executes scripts faster than bash, and has fewer library
+ dependencies (making it more robust against software or hardware
+ failures), it is used as the default system shell on Debian systems.
Package: ash
Architecture: all
Bug#477092: [PATCH] add support for setting a username + password in grub-installer for GRUB 2
Christian Perrier wrote: Quoting Felix Zielcke (fziel...@z-51.de): [...] +Template: grub-installer/superuser +Type: string +# :sl2: +_Description: GRUB superuser: + The GRUB boot loader offers many powerful interactive features, which could + be used to compromise your system if unauthorized users have access to the + machine when it is starting up. To defend against this, you may choose a + username and password which will be required before editing menu entries or + entering the GRUB command-line interface. By default, any user will still be + able to start any menu entry without entering a username and password. + . + If you do not wish to set a GRUB username, leave this field blank. + s/your system/the system maybe s/starting up/booting up I'm not sure about To defend against this No strong opinion on any of these (even the you might not be the owner quibble is weak here). username or user name? One word. Christian Perrier and Justin B Rye are user names, but not their usernames. +Template: grub-installer/grub2-password [...] Another option is somethign similar to the root password prompt: _Description: GRUB password: You need to set a password for GRUB. A malicious or unqualified user with GRUB access can have disastrous results, so you should take care to choose a GRUB password that is not easy to guess. It should not be a word found in dictionaries, or a word that could be easily associated with you. Looks good to me. +Template: grub-installer/empty-password +Type: error +# :sl2: +_Description: Empty password + You have given a username but no password. If you don't want authorization + please don't specify an username, else you have to give a password. Looks bad to me: s/an username/a username/; s/, else/; otherwise/; and you don't want (to get) authorization, you want there to be authentication. You may want to use the same wording than the similar template in user-setup: _Description: Empty password You entered an empty password, which is not allowed. Please choose a non-empty password. This loses the advice on what to do if you're not trying to set up a password. On the other hand, how would I apply that advice if I didn't already know about dpkg-reconfigure? Is there a back button? -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545247: go2: ImportError: No module named glade
Package: go2 Version: 0.090827 Severity: minor This can't be right: $ apt-get install go2 $ pager /usr/share/doc/go2/README.Debian $ source /usr/lib/go2/go2.sh $ go2 -h | pager $ go2 --gui Traceback (most recent call last): File /usr/lib/go2/go2.py, line 1204, in module import gtk, gtk.glade ImportError: No module named glade I'm calling this minor because the man page doesn't mention the --gui option (though it does point at the homepage, which refers to a modo gráfico). Nonetheless, if it has functionality that requires extra libraries, it shoould Depend/Recommend/Suggest them. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages go2 depends on: ii python2.5.4-2An interactive high-level object-o ii python-central0.6.11 register and build utility for Pyt go2 recommends no packages. Versions of packages go2 suggests: pn locatenone (no description available) pn python-psyco none (no description available) -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545249: go2: documentation needed
Package: go2 Version: 0.090827 Severity: minor (This might deserve l10n and/or patch tags) go2 has a super-short package description, and its man page says: # This manual page was written for the Debian distribution because the # original program does not have a manual page. [...] # This program follows the usual GNU command line syntax, with long # options starting with two dashes (`-´). A summary of options is # included below. For a complete description, see the Info files. [...] # This program is fully documented in # http://arco.inf-cr.uclm.es/~david.villa/go2.html But there's no info file in the package (unless you mean /usr/share/pyshared/go2-0.090827.egg-info, which doesn't contain any such description) and the website is in Spanish. If I have /usr/lib/go2/go2.sh loaded in my shell (a requirement mentioned in the README but nowhere else) I can see that the output of go2 --help includes several options not listed in the manpage (and some not listed on the website): -l, --gui, --cmd, --dir. As I mentioned in bug #545247, --gui doesn't work. So please: * expand the package description with information from the webpage * update the man page with at least the information that's in the README and the --help output If you need assistance with translations, there's always the debian-l10n-english mailing list, and I include below my own rough version of the package description. -- Package: go2 Description: fast directory finder This package provides a mechanism for quickly changing directory on the commandline, in the style of the old Norton Change Directory for DOS, but designed specifically for bash. . Features: * cache of recent searches; * history list of visited directories; * blacklist of directories not to search; * configuration file for default options; * multithreaded execution. . To activate go2, users need to source the appropriate function in their ~/.bashrc - see README.Debian for details. -- Leftover sub-wishlist not-quite-bug-reports: Are you sure go2 is bash-specific? It seems to work in pretty much any normal user shell - ksh, zsh... in fact, every shell I tried it in except dash and csh. Since shell functions take priority over executables, have you considered the possibility of creating a /usr/bin/go2 that exists just to tell users that they need to set up the shell function? Just an idea. Why Suggests: locate and not Suggests: locate | mlocate? -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages go2 depends on: ii python2.5.4-2An interactive high-level object-o ii python-central0.6.11 register and build utility for Pyt go2 recommends no packages. Versions of packages go2 suggests: pn locatenone (no description available) pn python-psyco none (no description available) -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523372: consolekit: Couldn't read /proc/'pid_number'/environ
On Thu, Apr 09, giggz wrote: At boot I have this warning message in my log : console-kit-daemon[2287]: WARNING: Couldn't read /proc/2285/environ: Failed to open file '/proc/2285/environ': No such file or directory This message still occurs every time ConsoleKit starts. Why has the bug report been tagged upstream wontfix? The workaround of adding --no-daemon to the invocation in /usr/share/dbus-1/system-services/org.freedesktop.ConsoleKit.service makes the WARNING go away, but only until the file is overwritten on the next upgrade. It may also have side-effects, but since there's no man page, who can say? I suspect this bug has been confused with the pstree -a repeats threads non-bug that jiddanni tacked onto it in followups. I can see that one in the bugs.freedesktop.org BTS; but nothing about WARNING messages sent to syslog. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540831: [Pkg-alsa-devel] Bug#540831: blacklisting pcspkr ruins beep(1), and icewm' mail beep
Elimar Riesebieter wrote: As mentioned by others in this thread you should check your sound card for the ability to simulate a terminal beep, what most drivers do. Mailnotification and system sounds can also be handled by your soundcard, though. [...] A working soundcard isn't enough to guarantee that the speakers are usable for mail-notification beeps. I might have fancy externally powered speakers that I turn off when not in use. I might listen to all my music via tinny little headphones. I might use the soundcard only for recording. Or I might have a soundcard that isn't appropriately configured yet. Where is the documentation on how I'd go about reconfiguring it? Thanks for reverting this change. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533704: [imagemagick][bug] Could you post an exemple of misindentified file
Bastien ROUCARIES wrote: About debian bug #533704: Identify crashes on non-image XML files Could you please post a misindentified xml file please. Upstream need it. It's true, some .xml files just give a sensible no decode delegate for this image format warning. But try this one, which I'm fairly confident is valid XML 1.0: http://www.w3.org/TR/2008/REC-xml-20081126/REC-xml-20081126.xml Despite a couple of security updates to the version of imagemagick in Stable (currently 7:6.3.7.9.dfsg2-1~lenny3) I still get: (process:16648): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject' (process:16648): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed identify: Memory allocation failed `REC-xml-20081126.xml'. On Testing it's now imagemagick 7:6.5.1.0-1.1, which changes the results to be similar to what I see with imagemagick-dbg on Stable: identify: Memory allocation failed `REC-xml-20081126.xml' @ svg.c/ReadSVGImage/2827. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541076: pod2pdf: package description problems
Package: pod2pdf
Version: 0.42-1
Severity: minor
Tags: patch
The short description line claims that pod2pdf provides a
converts Perl Old Documentation to PDF format
This synopsis has a couple of problems.
* There's no such thing as Perl Old Documentation. Obviously you
mean (Perl's) Plain Old Documentation format.
* It's a verb phrase. The DevRef6.2.2-compliant format is a noun
phrase (something that fits the above provides a... template).
* (Severity level pedantic) PDF format is a PIN-numberism -
Portable Document Format format. Why not just expand it?
My patch changes it to
Plain Old Documentation to Portable Document Format converter
Your long description is fine (never mind my urge to fiddle with the
commas), but has a single minor typo: lingua fraca.
Thanks for packaging pod2pdf!
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i586)
Kernel: Linux 2.6.30.custom
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pod2pdf depends on:
ii libgetopt-argvfile-perl 1.11-1 Perl module for reading script opt
ii libpdf-api2-perl 0.73-1 module for creating or modifying P
ii perl 5.10.0-24 Larry Wall's Practical Extraction
ii perl-modules 5.10.0-24 Core Perl modules
Versions of packages pod2pdf recommends:
ii libfile-type-perl 0.22-1.1 determine file type using magic st
ii libimage-size-perl3.2-1 determine the size of images in se
pod2pdf suggests no packages.
-- no debconf information
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ur pod2pdf-0.42.pristine/debian/control pod2pdf-0.42/debian/control
--- pod2pdf-0.42.pristine/debian/control 2009-08-11 14:41:50.0 +0100
+++ pod2pdf-0.42/debian/control 2009-08-11 14:44:03.0 +0100
@@ -14,7 +14,7 @@
Depends: ${perl:Depends}, ${misc:Depends}, perl-modules,
libpdf-api2-perl (= 0.6), libgetopt-argvfile-perl
Recommends: libimage-size-perl, libfile-type-perl
-Description: converts Perl Old Documentation to PDF format
+Description: Plain Old Documentation to Portable Document Format converter
POD allows for the documentation of Perl code, but with
a few tricks, e.g. when disguised as comments, it is
applicable to many other languages, too. It resembles
@@ -27,8 +27,7 @@
to PostScript and from there via ps2pdf to PDF.
Its major advantage lies in the inclusion of images
for the documentation. This renders POD suitable for
- many smallish projects as a lingua fraca for their
+ many smallish projects as a lingua franca for their
documentation - associated with the source and separate
documents - so texts (and graphics) can be shared more
easily between documenters and programmers.
-
Bug#540156: lintian: New feature - Check debian/control::Description for upcase starting word
Jari Aalto wrote: Description: Simple and easy to use addressbook ... SUGGESTION Add a --pedantic check for capitalized first word in Description field. Pedantic and very uncertain, since it's only sentential punctuation that's deprecated, not lexically capitalised or all-uppercase words (as in Debian addressbook or GNOME addressbook). Spotting a final period (full stop) would be easier, though you'd have to filter the cases that end with etc. or T.L.A.! Equally deprecated in DevRef6.2.2, and much easier to check: anything beginning with an article (a/an/the). The only false positive I can see for that one is abcde, A Better CD Encoder. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532715: bsdutils: does not have programs listed in description
Osamu Aoki wrote: Here is facts: Curremtly Description: Basic utilities from 4.4BSD-Lite This package contains the bare minimum number of BSD utilities needed to boot a Debian system. You should probably also install bsdmainutils to get the remaining standard BSD utilities. Included are: cal, col, colcrt, colrm, column, logger, renice, script, scriptreplay, ul, wall But I do not see cal etc. in package. And I don't see that text in the post-Lenny package description. See my previous bugreport #482098, which provided a patch for both the inaccurate binaries-list and the misleadingly phrased introduction. Wouldn't it be nice if the maintainers of -utils backages could rely on some sort of standard debhelper tool for keeping this sort of contents-list up to date? See also coreutils (#535458), procps (#535954), psmisc (#485693), and so on. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#452388: Back on 'standard system' is confusing bug report
Christian Perrier wrote: Description: Standard system This task installs a reasonably small character-mode system. What about something like: Description: Standard (non-graphical) system This task installs a reasonably small character-mode system, that provides the most commonly used tools in non-graphical environments. No comma before a that clause; and the last part isn't quite right either (provides [...] tools in [...] environments?). I assume the intended sense is the tools that in non-graphical environments are used most commonly, but there's no good way of phrasing that. How about just: This task installs a reasonably small character-mode system, providing tools often used in non-graphical environments. However, I worry that this will encourage CLI-phobic users to uncheck the Standard task. It's not for console-only systems; after all, I'm using mutt right now in my window manager. It's a basic neutral user environment, including apt, exim4, perl, python, and so on, just not X - the only time I would leave it out is on a bare-bones server with no users. Perhaps it should say something more like: This task sets up a basic user environment, providing a reasonably small selection of services and tools usable on the command line. Or if the idea is that GNOME users _don't_ need it, it needs a name change to, say, Traditional or Command Line User Environment. A name change might be appropriate anyway, given that tasksel's Standard task includes the whole of Priority: required and Priority: important, not just Priority: standard. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534415: [Pkg-freevo-maint] Bug#534415: [BTS#534415] templates://freevo/{freevo.templates}
A Mennucc wrote: Justin B Rye ha scritto: A Mennucc wrote: Description: home theater framework - binaries Freevo is a complete home theater framework. It comprises a Personal Video Recorder system for saving television input to disk and playing it back. It can browse and play [...] I have to get rid of that comprise, why? the usage of comprise is the whole comprises the parts. http://en.wiktionary.org/wiki/comprise So that comprise is exact. The definition you're quoting there says that comprise is followed by either a collective term for a set of constituent elements, or more usually by a list (in which case it is unhelpfully ambiguous about whether that's an exhaustive list). That isn't how you've used it - you've got one thing (Freevo) comprising another single item (the PVR). The more important reason for avoiding comprise is that there are plenty of people out there who use it the other way round (see wiktionary on the members comprise the team), so using the word is always more or less guaranteed to confuse at least some readers. Freevo is a complete home theater framework. It can operate as a Personal Video Recorder system for saving television input to disk, but can also browse and play pictures, music, games, and movies either from the hard disk or from CDs and DVDs. Freevo can be used on a regular desktop computer using the monitor, mouse, and keyboard, or can turn it into a dedicated home theater with a TV (plus remote). The last phrase does not parse easily. At first read, there is ambiguity regarding the subject of the last can turn and the it. I guess that the intended meaning is Freevo can turn your desktop computer, but at a first read it also sounds as Freevo can turn your keyboard Good point: at best it's saying that it can turn a regular desktop computer into a dedicated home theatre. No, you can start with thoroughly irregular hardware! (One issue I haven't brought up is whether theater is appropriate. In en_GB a home theatre would involve staging plays in your house. I'm not sure if it's at all ambiguous in en_US - I notice the wikipedia entry for home theater redirects to home cinema, but probably I should leave the issue to any native en_US-speakers on the list.) Freevo is a complete home theater framework. It can operate as a Personal Video Recorder system for saving television input to disk, but it can also browse and play pictures, music, games, and movies either from the hard disk or from CDs and DVDs. Freevo can be used on a regular desktop computer using the monitor, the mouse and keyboard. mouse, and keyboard. Freevo can also be the central software in a dedicated home theater to be enjoyed with a TV (and a remote). That does fix it, but to be enjoyed with sounds like a serving suggestion (which I suppose is more or less what it is, but still.) The change I'd have suggested to my own last attempt is: Freevo is a complete home theater framework. It can operate as a Personal Video Recorder system for saving television input to disk, but can also browse and play pictures, music, games, and movies either from the hard disk or from CDs and DVDs. Freevo can be used on a regular desktop computer using the monitor, mouse, and keyboard; or it can serve as the basis of a dedicated home theater system with a TV (plus remote). I'm having trouble avoiding overuse of use as usual. Hang on, let's see if it's any easier the other way around: Freevo is a complete home theater framework. It can operate as a Personal Video Recorder system for saving television input to disk, but can also browse and play pictures, music, games, and movies either from the hard disk or from CDs and DVDs. Freevo can be used to build a dedicated home theater system with a TV (plus remote), or can simply be run on a regular desktop computer with a monitor, mouse, and keyboard. How's that? -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536889: [developers-reference]: Please add an example for the short description starting with a verb
# for the control server:
retitle 536889 [developers-reference]: explicitly deprecate verb phrase synopses
thanks
The next step is to get your comments together as something I can
conveniently point at in a post to debian-l10n-english. This may
take me some time, but I promise it'll be less than the year and a
half it took me to get my vague ideas into shape for bug #516436!
Currently, DevRef6.2.2 says:
# The synopsis functions as a phrase describing the package, not a
# complete sentence, so sentential punctuation is inappropriate: it
# does not need extra capital letters or a final period (full stop).
# It should also omit any initial indefinite or definite article -
# a, an, or the. Thus for instance:
#
# Package: libeg0
# Description: exemplification support library
#
# Technically this is a noun phrase minus articles, as opposed to a
# verb phrase. A good heuristic is that it should be possible to
# substitute the package name and synopsis into this formula:
#
# The package name provides {a,an,the,some} synopsis.
Criticisms:
1) basically, it's not clear that verb phrases are the main thing
we're deprecating;
2) in particular, the noun phrase/verb phrase part can be read as
an incidental description of the given example;
3) more examples (both should and should not) would be good;
4) a good heuristic also makes it sound as if fitting the template
is optional. (Yes, the underlying definition is a matter of
syntax, but since developers don't usually think in terms of
noun phrases or verb phrases, the heuristic is the only
practical validation mechanism.)
You also mention the issue of translations. I don't know if we'd
want to even try to apply the same rule in languages that use
suffixed articles, or no articles at all! And Verb-Subject-Object
languages like Welsh would make things even trickier...
--
JBR
Ankh kak! (Ancient Egyptian blessing)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536889: [developers-reference]: Please add an example for the short description starting with a verb
Justin B Rye wrote: It was already obvious that technical terms alone wouldn't work (because they're meaningless to non-linguists); but it seems the substitution formula doesn't work very well either. Or does it just need to give more examples? Maybe examples of what _isn't_ right? I'd also be inclined to retitle this bug to something like [developers-reference]: explicitly deprecate verb phrase synopses, but I'd prefer to hear from you before I do that. By the way, just talking about starting with a verb isn't a safe diagnostic, since it's possible to construct a valid noun phrase synopsis that begins with a verb: dndtool - do not disturb sign generator just as it's possible for the deprecated verb phrase format to begin with a noun: fwutil - hand compile your firewall rules The only reliable way for non-specialists to tell whether a phrase obeys the guidelines is to slot it into the heuristic template and see if it fits. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537073: cron: unnecessary dependency on lockfile-progs
Justin B Rye wrote: * standard.daily - a minimal modification of the cronjob; Come to think of it: #!/bin/sh # /etc/cron.daily/standard: standard daily maintenance script # Written by Ian A. Murdock imurd...@gnu.ai.mit.edu # Modified by Ian Jackson ijack...@nyx.cs.du.edu # Modified by Steve Greenland stev...@debian.org # Start in the root filesystem, make SElinux happy cd / bak=/var/backups LOCKFILE=/var/lock/cron.daily # # Avoid running more than one at a time # umask 066 : $LOCKFILE That would be microscopically better as : $LOCKFILE -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536889: [developers-reference]: Please add an example for the short description starting with a verb
Jens Seidel wrote:
as described in #400970 the formulation of the short description starting
with a verb is not clear. Chapter 6.2.2 suggests:
A good heuristic is that it should be possible to substitute the package
name and synopsis into this formula:
The package name provides {a,an,the,some} synopsis.
Applying this to a package description as
display large colourful characters in text mode
one could guess that a 3rd person form is more suitable:
displays ...
No; both are wrong and fail the heuristic. Display things is a
verb phrase; displays things is a verb phrase; and verb phrases
don't fit the formula. As the previous line of DevRef6.2.2 says,
what developers are meant to be using is a noun phrase (minus
articles), _not_ a verb phrase. Of course, DevRef guidelines aren't
legally binding, so a lot of package descriptions are malformed.
Since I'm the guy who came up with the current phrasing (of a
pre-existing recommendation; see bug #516436), I'd be interested to
hear what you'd suggest as a way of communicating this more clearly.
It was already obvious that technical terms alone wouldn't work
(because they're meaningless to non-linguists); but it seems the
substitution formula doesn't work very well either. Or does it just
need to give more examples? Maybe examples of what _isn't_ right?
In this specific case:
Package: toilet
Description: display large colourful characters in text mode
The problem with a synopsis like toilet's is that it doesn't say
what sort of thing this package is. What's needed is a description
that makes it clear to people browsing the package repositories
whether toilet is a:
- daemon that puts a scrolling marquee on the console
- font-setup utility for the partially sighted
- text banner generator using ASCII art
See? Those are all expressed so that they do fit the formula - The
package toilet provides a... text banner generator using ASCII art.
Oh, and if that package description came to debian-l10n-english for
review I'd also en_USify the spellings and ask why TOIlet?
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537073: cron: unnecessary dependency on lockfile-progs
Package: cron
Version: 3.0pl1-106
Severity: minor
Tags: patch
As has been mentioned in other bugreports (#485452, #535227), the
use of lockfile-progs by /etc/cron.daily/standard introduces an
unnecessary dependency on a low-Priority package, pulling it in by
default on every Debian install, even though you could get the same
functionality more easily via coreutils these days.
I attach three different sh scripts:
* flockdemo - which just shows how it works;
* standard.daily - a minimal modification of the cronjob;
* rewrite - a thoroughgoing reimplementation.
That third one is just there because I couldn't help myself - it has
extra features such as recognising ext4, but it deliberately changes
more or less every line and probably isn't suitable for use.
I also attach a patch that covers the minimal-change version plus
corresponding edits to the control file, removing the unnecessary
Recommends: lockfile-progs and the corresponding paragraph of the
package description. It should also fix bugs #179629 and #478967,
though not bug #333837.
Further comments on the standard cronjobs:
--
First, /etc/cron.monthly/standard has been empty for most of a
decade. Now would be a good time to get rid of it.
Second, the names of these cronjobs contravene a should in Debian
Policy 9.5, where it defines the namespace for these files:
# If a package wants to install a job that has to be executed via
# cron, it should place a file with the name of the package in one
# or more of the following directories:
Even anacron, which can't use plain anacron, gets as close as it
can with 0anacron. So the one remaining standard cronjob should
be named /etc/cron.daily/cron, leaving the namespace clear in case
a package ever turns up named standard.
Third, I agree with bug #473711: it's pointless to have every single
Debian machine spinning up every single hard disk to check the
status of lost+found directories every single day. Corrupted file
systems don't surreptitiously fsck themselves - doing the check more
often than once per boot is only going to be useful if the sysadmin
performs crucial system rescue procedures without paying attention,
and if you're going to assume that, you need to do a lot more kinds
of check! IMHO this task should belong to initscripts; if that's
too much trouble it could at least be factored out into a script
(something like /sbin/chklost+found) so that it can be called both
@reboot and @daily.
--
JBR
Ankh kak! (Ancient Egyptian blessing)
#!/bin/sh
FLOCK=~/lock# or whatever; not somewhere world-writable
umask 066 # don't let anyone else get a read-lock
: $FLOCK # always recreate it in case it's on a tmpfs
exec $FLOCK # use STDIN, don't interfere with output
if ! flock -n 0; then
echo 'Failed to acquire lock'
exit 1
fi
echo 'Running - now launch another to demonstrate collisions'
sleep 5
echo 'Finished' # $FLOCK automatically released
#!/bin/sh
# /etc/cron.daily/standard: standard daily maintenance script
# Written by Ian A. Murdock imurd...@gnu.ai.mit.edu
# Modified by Ian Jackson ijack...@nyx.cs.du.edu
# Modified by Steve Greenland stev...@debian.org
# Start in the root filesystem, make SElinux happy
cd /
bak=/var/backups
LOCKFILE=/var/lock/cron.daily
#
# Avoid running more than one at a time
#
umask 066
: $LOCKFILE
exec $LOCKFILE
if ! flock -n 0; then
cat EOF
Unable to run /etc/cron.daily/standard because lockfile $LOCKFILE
acquisition failed. This probably means that the previous day's
instance is still running. Please check and correct if necessary.
EOF
exit 1
fi
umask 022
#
# Backup key system files
#
if cd $bak ; then
cmp -s passwd.bak /etc/passwd || (cp -p /etc/passwd passwd.bak
chmod 600 passwd.bak)
cmp -s group.bak /etc/group || (cp -p /etc/group group.bak
chmod 600 group.bak)
if [ -f /etc/shadow ] ; then
cmp -s shadow.bak /etc/shadow || (cp -p /etc/shadow shadow.bak
chmod 600 shadow.bak)
fi
if [ -f /etc/gshadow ] ; then
cmp -s gshadow.bak /etc/gshadow || (cp -p /etc/gshadow gshadow.bak
chmod 600 gshadow.bak)
fi
fi
if cd $bak ; then
if ! cmp -s dpkg.status.0 /var/lib/dpkg/status ; then
cp -p /var/lib/dpkg/status dpkg.status
savelog -c 7 dpkg.status /dev/null
fi
fi
#
# Check to see if any files are in lost+found directories and warn admin
#
# Get a list of the (potential) ext2, ext3 and xfs l+f directories
# Discard errors, for systems not using any of these.
df -P --type=ext2 --type=ext3 --type=xfs 2/dev/null |
awk '/\/dev\// { print }' | sed -e 's/ [[:space:]]*/ /g' |
while read mount block used avail perc mp; do
[ $mp = / ] mp=
echo $mp/lost+found
done |
while read lfdir; do
# In each directory, look
Bug#181170: dpkg: -l cannot get status to match desire if purged
Guillem Jover wrote: Dan Jacobson wrote: Desired=Unknown/Install/Remove/Purge/Hold |Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:uppercase=bad) ||/ Name VersionDescription +++-==-==- pn dpkg-www none (no description available) I take it that the cause of the misunderstanding here is that it says Purge is still merely Desired (and so by implication not yet accomplished). well, true, it is a cosmetic problem, but as you see, there is no way to make the desired state letter match the status letter, as all there is is Not/Installed and no matching category. therefore we never reach our desires, one could say. so maybe rename something. I'm not going to change the ‘desired’ or ‘status’ letters, as that would break external packages and scripts realying on them bein what they currently are. You have to consider though, that they are not meant to match, as one is an action to perform and the other a state. But I could certainly change the first to something like “Desired Action”. I don't see how that helps. Quite the opposite: the problem is that they are desired _states_ (which is why the desire persists when the action is finished). When jidanni asks about a purged package and it answers that Desired=p, it isn't wrongly saying that it hopes to someday perform the action of purging, it's correctly reporting that its intended state is the purged state. Why not expand u/i/r/p/h as Unknown/Installed/Removed/Purged/Held? (Alternatively, yes, you could change the name of the category; even a close synonym like Intended would make jidanni's problem go away. But I gather that would be more effort, and almost any effort would be too much.) -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534415: [Pkg-freevo-maint] Bug#534415: [BTS#534415] templates://freevo/{freevo.templates}
A Mennucc wrote: Description: home theater framework - binaries Freevo is a complete home theater framework. It comprises a Personal Video Recorder system for saving television input to disk and playing it back. It can browse and play pictures, music, games, and movies, both from the internal hard disk or from CDs and DVDs. It can be used either to build a dedicated home theater with a TV (plus remote) or on a regular desktop computer using the monitor, the mouse and keyboard. What do you think? I have to get rid of that comprise, and the phrasing of that last sentence seems to imply that you can use it without involving any hardware running Debian. How about phrasing the boilerplate as: Freevo is a complete home theater framework. It can operate as a Personal Video Recorder system for saving television input to disk, but can also browse and play pictures, music, games, and movies either from the hard disk or from CDs and DVDs. Freevo can be used on a regular desktop computer using the monitor, mouse, and keyboard, or can turn it into a dedicated home theater with a TV (plus remote). -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535954: procps: incomplete list in package description
Package: procps Version: 1:3.2.8-1 Severity: minor Tags: patch Every summer I run through the descriptions for high-priority and/or high-popcon packages, looking for the ones that need any work. Last year I had this one down as not worth the effort of a bug report, but this time round it's made it onto my list. # Description: /proc file system utilities # These are utilities to browse the /proc filesystem, which is not a real file # system but a way for the kernel to provide information about the status of # entries in its process table. (e.g. running, stopped or zombie) # Both command line and full screen utilities are provided. Ncurses is needed # for the full screen utilities. More information can be found at procps # website http://procps.sf.net/ # . # This package includes the following utilities: top, uptime, tload, # free, vmstat, watch, skill, pmap, pgrep, slabtop and pwdx. Wishlist-level gripes: * procfs really is a file system (just not a writing-to-disk FS); * odd punctuation: period, open bracket, lowercase e; * the Depends: line takes care of ncurses, no need to explain it; * add a Harvard comma in that list (just a matter of taste); * point at the homepage with a Homepage: line; The one that makes this worth submitting as Severity: minor: * that's a strangely selective contents catalogue - it omits kill, pkill, ps, snice, sysctl, and w! My suggested replacement is: Homepage: http://procps.sf.net/ [...] Description: /proc file system utilities This package provides command line and full screen utilities for browsing procfs, a pseudo file system dynamically generated by the kernel to provide information about the status of entries in its process table (such as whether the process is running, stopped, or a zombie). . It contains free, kill, pkill, pgrep, pmap, ps, pwdx, skill, slabtop, snice, sysctl, tload, top, uptime, vmstat, w, and watch. Mind you, as with bsdutils (bug #482098), coreutils (#535458), etcetera, I can't help feeling that the only sensible long-term solution for contents-catalogues like this would be to maintain them automatically via some sort of standard debhelper tool... -- JBR Ankh kak! (Ancient Egyptian blessing) --- ../procps-3.2.8.pristine/debian/control 2009-07-05 03:11:48.0 +0100 +++ debian/control 2009-07-06 11:29:33.0 +0100 @@ -4,6 +4,7 @@ Maintainer: Craig Small csm...@debian.org Build-Depends: debhelper (= 7), libncurses5-dev, make (= 3.78.1-8), dpatch Standards-Version: 3.8.1 +Homepage: http://procps.sf.net/ Package: procps Architecture: any @@ -13,15 +14,13 @@ Replaces: watch, bsdutils ( 2.9x-1) Recommends: psmisc Description: /proc file system utilities - These are utilities to browse the /proc filesystem, which is not a real file - system but a way for the kernel to provide information about the status of - entries in its process table. (e.g. running, stopped or zombie) - Both command line and full screen utilities are provided. Ncurses is needed - for the full screen utilities. More information can be found at procps - website http://procps.sf.net/ + This package provides command line and full screen utilities for browsing + procfs, a pseudo file system dynamically generated by the kernel to + provide information about the status of entries in its process table + (such as whether the process is running, stopped, or a zombie). . - This package includes the following utilities: top, uptime, tload, - free, vmstat, watch, skill, pmap, pgrep, slabtop and pwdx. + It contains free, kill, pkill, pgrep, pmap, ps, pwdx, skill, slabtop, + snice, sysctl, tload, top, uptime, vmstat, w, and watch. Package: libproc-dev Architecture: any
Bug#535776: lzma: package description review
Package: lzma Version: 4.43-14 Severity: minor Tags: patch As lzma's Priority goes up, its package description becomes more of an embarrassment. Here's some suggested changes; and once I'm editing the control file I might as well review all the others in the same source package, for consistency. Patch attached; justifications below. -Homepage: http://www.7-zip.org/sdk.htm +Homepage: http://www.7-zip.org/sdk.html Typo-fix. Package: lzma [...] -Description: Compression method of 7z format in 7-Zip program +Description: LZMA compression - command line utility The original is wobbly English, but more importantly it's useless as a description of this package (unless users happen to be familiar with 7-Zip). Replace it with something informative and DevRef6.2.2-compliant. - LZMA is a compression algorithm, based on the famous Lempel Ziv - compression method. - . - The main characteristics of the algorithm are very good compression, - fast decompression, use of lot of RAM for compression and low usage of - RAM for decompression. - . - LZMA provides high compression ratio and very fast decompression, so it - is very suitable for embedded applications. For example, it can be used - for ROM (firmware) compression. Repetitive and poorly phrased (for a start, use of lot of RAM is ungrammatical). Try: + The Lempel-Ziv Markov-chain Algorithm is a compression method based on + the famous LZ77 algorithm, and was first introduced by 7-Zip for use in + .7z archives. + . + Its main characteristics are a very high compression ratio, with high RAM + usage, and fast decompression, with low RAM usage. These properties make + it well suited to embedded uses, such as for ROM (firmware) compression. (And use this text as boilerplate in other package descriptions.) - This package provides a gzip-like interface for the lzma program. + This package provides the lzma command line utility, which has a + familiar gzip-like interface. The package does _not_ provide an interface for the lzma program - it provides the lzma binary itself! Package: lzma-dev [...] -Description: Compression method of 7z format in 7-Zip program - development files +Description: LZMA compression - development files Changing all of the short descriptions to form a consistent set. Then the same boilerplate changes, ending with: - This package contains the headers and libraries of lzma. It is - experimental and will be replaced by the library as soon as it is - available. + This package provides headers and development libraries for lzma. It's far from obvious what the library was supposed to mean, but whatever it was, this description is misleading - if this package was experimental it shouldn't have been in Sid, never mind Lenny. Replace it with something accurate. Package: lzma-source [...] -Description: Source for the lzma kernel module +Description: LZMA compression - Linux kernel module source Mention that we're talking Linux, not FreeBSD. [...boilerplate ditto...] This package provides the source code for the lzma kernel modules. - Kernel source and headers are required to compile these modules. + Linux kernel source and headers are required to compile these modules. This individual package description already has a bugreport (#466582), but I'm treating mine as independent: even with my patch, the description for lzma-source could still easily be improved by input from somebody who understands what purpose it's supposed to serve (assuming this package still has a reason to exist). Package: lzma-alone [...] -Description: Compression method of 7z format in 7-Zip program +Description: LZMA compression - legacy utility The original has a synopsis identical to that of lzma, which is deeply unhelpful. My suggested replacement is a bit of a stab in the dark; if you don't like it, please produce something better. [...boilerplate ditto...] - This package provides the SDK based lzma_alone program. + This package provides only the old lzma_alone compression utility, which + has an interface more like that of zip. The current description is no help to a user wondering what lzma_alone is good for - they probably won't even know what SDK it's referring to. Besides (reading http://tukaani.org/lzma/history), both versions are SDK based: lzma_alone was in LZMA-utils, and then lzma was based on lzma_alone. -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru lzma-4.43.pristine/debian/control lzma-4.43/debian/control --- lzma-4.43.pristine/debian/control 2009-07-03 20:14:56.0 +0100 +++ lzma-4.43/debian/control 2009-07-04 09:45:25.0 +0100 @@ -4,7 +4,7 @@ Maintainer: Mohammed Adnène Trojette adn+...@diwi.org Uploaders: Arnaud Fontaine ar...@debian.org Build-Depends: debhelper (= 5.0.0), quilt, zlib1g-dev -Homepage: http://www.7-zip.org/sdk.htm +Homepage: http://www.7-zip.org/sdk.html Vcs-Git: git://git.debian.org/git/collab-maint/lzma.git Vcs-Browser:
Bug#535557: initscripts: minor problems in package description
Package: initscripts
Version: 2.86.ds1-63
Severity: minor
Tags: patch
In the package description,
-Description: Scripts for initializing and shutting down the system
+Description: scripts for initializing and shutting down the system
DevRev6.2.2-compliance, in passing. The other synopses in the same
control file are entitled to their capital letters.
The scripts in this package initialize a standard Debian
- GNU/Linux system at boot time and finalize it at halt or
- reboot time.
+ system at boot time and shut it down at halt or reboot time.
Two issues:
1) initscripts_2.86.ds1-63_kfreebsd-{amd64,i386}.deb
2) finalise is some sort of malapropism (it means something
closer to put into its canonical form ready for use);
terminate might be closer, but shut down, as in the
synopsis, is the normal idiom.
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru sysvinit-2.86.ds1.pristine/debian/control sysvinit-2.86.ds1/debian/control
--- sysvinit-2.86.ds1.pristine/debian/control 2009-07-03 10:04:00.0 +0100
+++ sysvinit-2.86.ds1/debian/control 2009-07-03 10:06:19.0 +0100
@@ -54,8 +54,7 @@
Recommends: psmisc
Conflicts: sysv-rc ( 2.86.ds1-1.2), sysvinit ( 2.86.ds1-12), udev ( 0.080-1), usplash ( 0.5.8-2), libdevmapper1.02.1 ( 2:1.02.24-1), insserv ( 1.09.0-12)
Replaces: sysvinit ( 2.85-12), libc6, libc6.1, libc0.1, libc0.3
-Description: Scripts for initializing and shutting down the system
+Description: scripts for initializing and shutting down the system
The scripts in this package initialize a standard Debian
- GNU/Linux system at boot time and finalize it at halt or
- reboot time.
+ system at boot time and shut it down at halt or reboot time.
Bug#535458: coreutils: out-of-date package description
Package: coreutils
Version: 7.4-2
Severity: minor
Tags: patch
The package description's list of included binaries is out of date.
It fails to mention arch, base64, chcon/runcon, flock, sha224sum
(etc), shuf, and truncate (but it does include mktemp).
My patch also fixes a couple of other trivial issues in passing:
* the capitalised definite article in the short description is
deprecated in DevRef 6.2.2;
* the first paragraph of long description isn't particularly
descriptive (it just uses a couple of near-synonyms of
core), so replace it with some explanatory text from the
upstream website;
* also, add a Homepage: line.
However, I can't help feeling that the only sensible long-term
solution would be for packages like bsdutils, coreutils,
debianutils, and sysvinit-utils to maintain contents-lists like this
via some sort of standard debhelper tool...
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru coreutils-7.4.pristine/debian/control coreutils-7.4/debian/control
--- coreutils-7.4.pristine/debian/control 2009-07-01 18:58:03.0 +0100
+++ coreutils-7.4/debian/control 2009-07-01 23:56:38.0 +0100
@@ -10,17 +10,20 @@
Pre-Depends: ${shlibs:Depends}
Essential: yes
Replaces: mktemp
-Description: The GNU core utilities
- This package contains the essential basic system utilities.
+Description: GNU core utilities
+ This package contains the basic file, shell and text manipulation
+ utilities which are expected to exist on every operating system.
.
Specifically, this package includes:
- basename cat chgrp chmod chown chroot cksum comm cp csplit cut date dd df dir
- dircolors dirname du echo env expand expr factor false fmt fold groups head
- hostid id install join link ln logname ls md5sum mkdir mkfifo mknod mktemp
- mv nice nl nohup od paste pathchk pinky pr printenv printf ptx pwd readlink
- rm rmdir sha1sum seq shred sleep sort split stat stty sum sync tac tail tee
- test touch tr true tsort tty uname unexpand uniq unlink users vdir wc who
- whoami yes
+ arch base64 basename cat chcon chgrp chmod chown chroot cksum comm cp
+ csplit cut date dd df dir dircolors dirname du echo env expand expr
+ factor false flock fmt fold groups head hostid id install join link ln
+ logname ls md5sum mkdir mkfifo mknod mktemp mv nice nl nohup od paste
+ pathchk pinky pr printenv printf ptx pwd readlink rm rmdir runcon
+ sha*sum seq shred sleep sort split stat stty sum sync tac tail tee test
+ touch tr true truncate tsort tty uname unexpand uniq unlink users vdir wc
+ who whoami yes
+Homepage: http://gnu.org/software/coreutils
Package: mktemp
Pre-Depends: coreutils (= 7.4-1)
Bug#535530: e2fslibs: outdated package description
Package: e2fslibs Version: 1.41.7-1 Severity: minor Tags: patch Lat year I nagged you into updating the package description for e2fsprogs to acknowledge the existence of ext3+ (#483023); but this left the other descriptions in the same control file lagging behind. Suggested patch attached; justifications follow. -Description: ext2 filesystem libraries - The ext2fs and e2p libraries are used by programs that directly access - EXT2 filesystems from usermode programs. The EXT2 filesystem is very often - used as the default filesystem on Linux systems. Various system programs - that use libext2fs include e2fsck, mke2fs, tune2fs, etc. Programs that use - libe2p include dumpe2fs, chattr, and lsattr. Problems: * the s/ext2/ext2-to-ext4/ issue; * the phrase programs that access filesystems from programs; * the weasel-rich some programs include foo, bar, baz, etc; * repetition of the words use and program. Solution: recycle some boilerplate from e2fsprogs. +Description: ext2/ext3/ext4 file system libraries + The ext2, ext3 and ext4 file systems are successors of the original ext + (extended) file system. They are the main file system types used for + hard disks on Debian and other Linux systems. + . + This package provides the ext2fs and e2p libraries, for userspace software + that directly accesses extended file systems. Programs that use libext2fs + include e2fsck, mke2fs, and tune2fs. Programs that use libe2p include + dumpe2fs, chattr, and lsattr. Incidentally, I'm using a single space between sentences there, but I haven't edited the whole control file for consistency; single-spacing is the standard recommended on debian-l10n-english, but it isn't mandated anywhere official. (And it's not what I habitually use myself!) -Description: ext2 filesystem libraries - headers and static libraries - The ext2fs and e2p libraries are used by programs that directly access - EXT2 filesystems from usermode programs. The EXT2 filesystem is very often - used as the default filesystem on Linux systems. Various system programs - that use libext2fs include e2fsck, mke2fs, tune2fs, etc. Programs that use - libe2p include dumpe2fs, chattr, and lsattr. +Description: ext2/ext3/ext4 file system libraries - headers and static libraries + The ext2, ext3 and ext4 file systems are successors of the original ext + (extended) file system. They are the main file system types used for + hard disks on Debian and other Linux systems. I've taken out the part that explains what these particular libraries do and replaced it with the same old boilerplate that explains what ext*fs is. That's less informative, but you wouldn't install the devel package if you didn't already know all this. -Description: Debugging information for e2fsprogs +Description: debugging information for e2fsprogs [...] -Description: Debugging information for uuid-runtime +Description: debugging information for uuid-runtime [...etc...] For consistency and DevRef6.2.2 compliance. -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ur e2fsprogs-1.41.7.pristine/debian/control e2fsprogs-1.41.7/debian/control --- e2fsprogs-1.41.7.pristine/debian/control 2009-06-01 12:48:42.0 +0100 +++ e2fsprogs-1.41.7/debian/control 2009-07-02 13:20:32.0 +0100 @@ -194,12 +194,15 @@ Replaces: e2fsprogs ( 1.34-1) Provides: libext2fs2, libe2p2 Architecture: any -Description: ext2 filesystem libraries - The ext2fs and e2p libraries are used by programs that directly access - EXT2 filesystems from usermode programs. The EXT2 filesystem is very often - used as the default filesystem on Linux systems. Various system programs - that use libext2fs include e2fsck, mke2fs, tune2fs, etc. Programs that use - libe2p include dumpe2fs, chattr, and lsattr. +Description: ext2/ext3/ext4 file system libraries + The ext2, ext3 and ext4 file systems are successors of the original ext + (extended) file system. They are the main file system types used for + hard disks on Debian and other Linux systems. + . + This package provides the ext2fs and e2p libraries, for userspace software + that directly accesses extended file systems. Programs that use libext2fs + include e2fsck, mke2fs, and tune2fs. Programs that use libe2p include + dumpe2fs, chattr, and lsattr. Package: e2fslibs-dev Section: libdevel @@ -209,12 +212,10 @@ Provides: ext2fs-dev, e2p-dev Replaces: libkrb5-dev ( 1.3) Architecture: any -Description: ext2 filesystem libraries - headers and static libraries - The ext2fs and e2p libraries are used by programs that directly access - EXT2 filesystems from usermode programs. The EXT2 filesystem is very often - used as the default filesystem on Linux systems. Various system programs - that use libext2fs include e2fsck, mke2fs, tune2fs, etc. Programs that use - libe2p include dumpe2fs, chattr, and lsattr. +Description: ext2/ext3/ext4 file system libraries - headers and static libraries + The ext2, ext3 and ext4 file systems
Bug#535227: cron: still bad package description
Package: cron Version: 3.0pl1-106 Severity: minor Tags: patch Last June I submitted bug #485452, which pointed out an error and some stylistic problems in cron's package description. The fix did not apply my suggested patch directly; it dealt with the factual error, but turned some portions of the text into word salad. # Package: cron # Description: process scheduling daemon # The cron daemon is a background process that runs particular programs at # particular times (for example, every minute, day, week or month), as # specific in the in a crontab. By default, users may also create # crontabs of their own so that processes are run on their behalf. The line as specific in the in a crontab needs corrective surgery. # Users may also install crontabs so that processes are run on # their behalf, though this feature can be disabled or restricted to # particular users. This paragraph is redundant. If you insist on keeping it, throw out the last sentence of the previous paragraph. # Output from the commands is usually mailed to the system administrator # (or to the user in question); you should probably install a mail system # as well so that you can receive these messages. # . # This cron package is configured by default to do some basic daily system # maintenance tasks, such as ensuring creating copying key system files. # Additional maintenance tasks are available on external packages, such as # 'checksecurity' The line such as ensuring creating copying key system files is severely garbled. The last sentence needs work too: tasks aren't on packages, and what are external packages, anyway? # The lockfile-progs package is recommended as it will prevent # /etc/cron.daily/standard from running multiple # times if something gets jammed. (This is looking rather ridiculous now that there's a perfectly good file-locking tool in Stable's Essential coreutils, but that's a separate issue.) I suggest... no, come to think of it this time I even _recommend_ that you adopt the attached patch. -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru cron-3.0pl1.pristine/debian/control cron-3.0pl1/debian/control --- cron-3.0pl1.pristine/debian/control 2009-06-30 18:58:02.0 +0100 +++ cron-3.0pl1/debian/control 2009-06-30 20:40:58.0 +0100 @@ -15,22 +15,17 @@ Provides: Description: process scheduling daemon The cron daemon is a background process that runs particular programs at - particular times (for example, every minute, day, week or month), as - specific in the in a crontab. By default, users may also create - crontabs of their own so that processes are run on their behalf. - . - Users may also install crontabs so that processes are run on - their behalf, though this feature can be disabled or restricted to - particular users. + particular times (for example, every minute, day, week, or month), as + specified in a crontab. By default, users may also create crontabs of + their own so that processes are run on their behalf. . Output from the commands is usually mailed to the system administrator (or to the user in question); you should probably install a mail system as well so that you can receive these messages. . This cron package is configured by default to do some basic daily system - maintenance tasks, such as ensuring creating copying key system files. - Additional maintenance tasks are available on external packages, such as - 'checksecurity' + maintenance tasks, such as creating backups of key system files. Other + packages, such as checksecurity, can provide further maintenance tasks. . The lockfile-progs package is recommended as it will prevent /etc/cron.daily/standard from running multiple
Bug#488237: lsb-base: useless package dependencies
severity 488237 minor # Policy 3.5 should not, so more than wishlist thanks Followup-For: Bug #488237 As I reported one year ago: # Depends: sed, ncurses-bin I left it at wishlist then since Lenny was just beginning to go into freeze, but depending on Essential packages is prohibited by Policy. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530754: malformed log messages
fixed 530754 4.2.0-1 thanks Package: rsyslog Followup-For: Bug #530754 It looks like this issue goes away with the version in Sid: Jun 26 20:03:42 zipacna kernel: Kernel logging (proc) stopped. rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=1394 x-info=http://www.rsyslog.com;] exiting on signal 15. Jun 26 20:03:42 zipacna kernel: imklog 4.2.0, log source = /proc/kmsg started. Jun 26 20:03:42 zipacna rsyslogd: [origin software=rsyslogd swVersion=4.2.0 x-pid=11537 x-info=http://www.rsyslog.com;] (re)start [next day] Yup, works on my original testbed machine too. I'll tag it fixed. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30.custom (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rsyslog depends on: ii libc6 2.9-12GNU C Library: Shared libraries ii lsb-base 3.2-22Linux Standard Base 3.2 init scrip ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime Versions of packages rsyslog recommends: ii logrotate 3.7.7-3Log rotation utility Versions of packages rsyslog suggests: ii rsyslog-doc 3.22.0-1 documentation for rsyslog pn rsyslog-gnutlsnone (no description available) pn rsyslog-gssapinone (no description available) pn rsyslog-mysql | rsyslog-pgsql none (no description available) pn rsyslog-relp none (no description available) -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522128: grub-common: grub: No video mode activated
fixed 522128 1.96+20090611-1 thanks Package: grub-common Followup-For: Bug #522128 On April 1, Justin B Rye wrote: grub2's boot-time invocation of background_image /path/to/image (as defined in /etc/grub.d/05_debian_theme) no longer succeeds; Fixed in Sid - both the machines that originally showed this bug are now back to showing pretty pictures on boot. Hurrah! And thanks. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534688: developers-reference: package description garbles ToC
Package: developers-reference Version: 3.4.1 Severity: minor Tags: patch (Found in all post-Woody versions of d-r) The package description has a Table of Contents section, generated by a trivial piece of Perl, that says: # . #1. Scope of This Document #2. Applying to Become a Maintainer #3. Debian Developer's Duties #4. Resources for Debian Developers #5. Managing Packages #6. Best Packaging Practices #7. Beyond Packaging #8. Internationalizing, translating, being internationalized and being # . ... trailing off in midphrase. It's a strange sort of a phrase, too, since DDs (the entities doing the applying in 2, the managing in 5, and indeed the internationalizing and translating here) don't do any being internationalized. My patch fixes it by pruning back the title of l18n.dbk to just: 8. Internationalization and Translations Incidentally, there's a misplaced apostrophe in 3, and the triple indent is unnecessary, but I wouldn't rate those above wishlist. -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru developers-reference-3.4.1.pristine/l10n.dbk developers-reference-3.4.1/l10n.dbk --- developers-reference-3.4.1.pristine/l10n.dbk 2008-06-09 21:17:46.0 +0100 +++ developers-reference-3.4.1/l10n.dbk 2009-06-25 23:53:45.0 +0100 @@ -4,7 +4,7 @@ !ENTITY % commondata SYSTEM common.ent %commondata; ] chapter id=l10n -titleInternationalizing, translating, being internationalized and being translated/title +titleInternationalization and Translations/title para Debian supports an ever-increasing number of natural languages. Even if you are a native English speaker and do not speak any other language, it is part of
Bug#534228: pdbv: hard-coded month-names, including Mai
Package: pdbv
Version: 2.0.11-0.4
Severity: minor
Tags: patch l10n
The names of the months (as used in pdbv's sort-by-date view) are
hard-coded in pdbv.pot, and the fifth one is misspelled there:
#: ../pdbv:1178
msgid Mai
msgstr
Looking in .po files I see that quite a few translations fail to
provide msgstrs for these msgids; and then there are the fuzzy
strings for March, which include the renderings Arch: and
Arquitectura! There's even a comment in it.po:
# FIXME UPSTREAM: May
I could send you a patched pdbv.pot, but it shouldn't be hard-coded
there in the first place when LC_TIME can do all the work for us.
See attached patch; it's a bit of a kludge (I ought to work out
where that function gets called and fix things there), and it leaves
some spring cleaning to be done in the po directory, but It Works
For Me, and should also improve things for users of other locales.
-- System Information:
Debian Release: 5.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.28.custom
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pdbv depends on:
ii coreutils [fileutils] 6.10-6 The GNU core utilities
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii liblocale-gettext-perl1.05-4 Using libc functions for internati
ii libtie-ixhash-perl1.21-2 ordered associative arrays for Per
ii perl-base 5.10.0-19 minimal Perl system
ii perl-modules 5.10.0-19 Core Perl modules
Versions of packages pdbv recommends:
ii popularity-contest1.46 Vote for your favourite packages a
ii procps1:3.2.7-11 /proc file system utilities
pdbv suggests no packages.
-- debconf information:
pdbv/cron: hourly
* pdbv/clean_output_dir: true
pdbv/force: false
pdbv/listing: all
* pdbv/cron_lang:
pdbv/light: false
* pdbv/output_dir: /var/www/pdbv
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru pdbv-2.0.11.pristine/modules/xhtml.pl pdbv-2.0.11/modules/xhtml.pl
--- pdbv-2.0.11.pristine/modules/xhtml.pl 2005-02-23 10:42:20.0 +
+++ pdbv-2.0.11/modules/xhtml.pl 2009-06-22 16:27:49.0 +0100
@@ -436,32 +436,8 @@
sub PdbvXhtmlMakeDate {
my ($year, $month) = split( , $_[0]);
-if ($month eq '01') {
- $month = gettext(January);
-} elsif ($month eq '02') {
- $month = gettext(February);
-} elsif ($month eq '03') {
- $month = gettext(March);
-} elsif ($month eq '04') {
- $month = gettext(April);
-} elsif ($month eq '05') {
- $month = gettext(Mai);
-} elsif ($month eq '06') {
- $month = gettext(June);
-} elsif ($month eq '07') {
- $month = gettext(July);
-} elsif ($month eq '08') {
- $month = gettext(August);
-} elsif ($month eq '09') {
- $month = gettext(September);
-} elsif ($month eq '10') {
- $month = gettext(October);
-} elsif ($month eq '11') {
- $month = gettext(November);
-} elsif ($month eq '12') {
- $month = gettext(December);
-}
-return $year., .$month;
+$month =~ s/^0//; # not octal!
+return strftime $year, %B, 0, 0, 0, 0, $month, 0;
}
sub PdbvXhtmlMakeSize {
Bug#533704: imagemagick: identify crashes on non-image XML files
Package: imagemagick Version: 7:6.3.7.9.dfsg2-1 Severity: minor (Also found in Lenny's 7:6.3.7.9.dfsg2-1~lenny1.) Running identify * on a directory that contains non-imagefiles can't be expected to work well, but I was expecting no decode delegate for this image format, not this: (process:3100): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject' (process:3100): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed identify: Memory allocation failed `eg.rdf'. The above happens with any RDF file, while XHTML gives me: (process:3111): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Error parsing XML data (process:3111): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Error parsing XML data (process:3111): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Error parsing XML data (process:3111): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Error parsing XML data (process:3111): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Error parsing XML data (process:3111): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject' (process:3111): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed identify: Memory allocation failed `eg.html'. There's an obvious workaround (don't do that then), so I'm only calling it minor; but it claims it's buggy, and who am I to argue? With imagemagick-dbg I don't get the WARNING messages, just: identify: Memory allocation failed `eg.rdf' @ svg.c/ReadSVGImage/2827. identify: Memory allocation failed `eg.html' @ svg.c/ReadSVGImage/2827. Looks like for a start it's seeing all XML as SVG... -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.30.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages imagemagick depends on: ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co ii libc6 2.9-12GNU C Library: Shared libraries ii libfontconfig1 2.6.0-3 generic font configuration library ii libfreetype6 2.3.9-4.1 FreeType 2 font engine, shared lib ii libice62:1.0.5-1 X11 Inter-Client Exchange library ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii liblcms1 1.18.dfsg-1 Color management library ii libmagick107:6.3.7.9.dfsg2-1 image manipulation library ii libsm6 2:1.1.0-2 X11 Session Management library ii libtiff4 3.8.2-11 Tag Image File Format (TIFF) libra ii libx11-6 2:1.2.1-1 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime imagemagick recommends no packages. imagemagick suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#139115: bind9-doc: ARM not registered with doc-base
severity 139115 minor # Debian Policy 9.10; recommended optional thanks On Sun, Jun 05, 2005, Justin B Rye wrote: Okay, if not for Woody or Sarge, how about in Etch? If not Woody or Sarge or Etch or Lenny, how about Squeeze? -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530754: malformed log messages
Package: rsyslog Version: 3.22.0-1 Severity: minor The version of rsyslogd that hit Testing yesterday has started sending messages on restarts that lack a datestamp/hostname prefix. Instead of the usual messages like this: May 26 12:50:08 oempc kernel: imklog 3.20.5, log source = /proc/kmsg started. May 26 12:50:08 oempc rsyslogd: [origin software=rsyslogd swVersion=3.20.5 x-pid=1578 x-info=http://www.rsyslog.com;] restart a restart now looks like this: rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=1897 x-info=http://www.rsyslog.com;] exiting on signal 15. May 27 14:24:20 oempc kernel: imklog 3.22.0, log source = /proc/kmsg started. rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=2861 x-info=http://www.rsyslog.com;] restart May 27 14:24:20 oempc rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=2861 x-info=http://www.rsyslog.com;] restart I'm assuming this isn't an intentional change; it chokes my homebrew log-monitor, and the /etc/logcheck/ignore.d.server/rsyslog regexp won't be happy about it either. (I have an unmodified rsyslog.conf.) -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.29.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rsyslog depends on: ii libc6 2.9-12GNU C Library: Shared libraries ii lsb-base 3.2-22Linux Standard Base 3.2 init scrip ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime Versions of packages rsyslog recommends: ii logrotate 3.7.7-3Log rotation utility Versions of packages rsyslog suggests: pn rsyslog-doc none (no description available) pn rsyslog-gnutlsnone (no description available) pn rsyslog-gssapinone (no description available) pn rsyslog-mysql | rsyslog-pgsql none (no description available) pn rsyslog-relp none (no description available) -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530754: malformed log messages
Michael Biebl wrote: tags 530754 unreproducible [...] I quickly tested it with 3.22.0-1 and can't reproduce your problem. The message, that shows up in /var/log/syslog looks like May 27 16:50:47 pluto rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=32634 x-info=http://www.rsyslog.com;] restart From what I see, you get duplicated log messages, which seems a bit weird. Are you passing debug flags to rsyslog? It's an unmodified vanilla install on a machine that essentially exists only to let me see what's hitting Testing (a bit of an antique, but that shouldn't make a difference in this case). Hang on, I'll try upgrading a machine that's been dormant for the past month... yup: grep 'syslog\|klog' /var/log/syslog May 27 16:13:33 zipacna kernel: imklog 3.20.5, log source = /proc/kmsg started. May 27 16:13:33 zipacna rsyslogd: [origin software=rsyslogd swVersion=3.20.5 x-pid=1393 x-info=http://www.rsyslog.com;] restart May 27 16:13:34 zipacna kernel: imklog 3.20.5, log source = /proc/kmsg started. May 27 16:13:34 zipacna rsyslogd: [origin software=rsyslogd swVersion=3.20.5 x-pid=1393 x-info=http://www.rsyslog.com;] restart May 27 16:21:45 zipacna kernel: imklog 3.22.0, log source = /proc/kmsg started. rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=14801 x-info=http://www.rsyslog.com;] restart May 27 16:21:45 zipacna rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=14801 x-info=http://www.rsyslog.com;] restart May 27 16:23:31 zipacna kernel: imklog 3.22.0, log source = /proc/kmsg started. rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=14801 x-info=http://www.rsyslog.com;] restart May 27 16:23:31 zipacna rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=14801 x-info=http://www.rsyslog.com;] restart (That's booting, doing an anacron daily-restart, then going through an aptitude upgrade; as soon as it's 3.22.0, it's in stereo.) -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530754: malformed log messages
Michael Biebl wrote: tags 530754 unreproducible And using yet a third junk PC I've just done a bare-bones 5.0r1 i386 netinst followed by an immediate upgrade to Squeeze, without once changing a default. Reproducible again: May 27 21:56:34 debian kernel: imklog 3.18.6, log source = /proc/kmsg started. May 27 21:56:34 debian rsyslogd: [origin software=rsyslogd swVersion=3.18.6 x-pid=1809 x-info=http://www.rsyslog.com;] restart May 27 22:03:20 debian kernel: imklog 3.22.0, log source = /proc/kmsg started. rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=9000 x-info=http://www.rsyslog.com;] restart May 27 22:03:20 debian rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=9000 x-info=http://www.rsyslog.com;] restart May 27 22:03:20 debian rsyslogd-2040: error accessing config file or directory '/etc/rsyslog.d/*.conf': Success [try http://www.rsyslog.com/e/2040 ] May 27 22:03:20 debian rsyslogd: the last error occured in /etc/rsyslog.conf, line 46 May 27 22:03:57 debian kernel: imklog 3.22.0, log source = /proc/kmsg started. rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=9000 x-info=http://www.rsyslog.com;] restart May 27 22:03:57 debian rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=9000 x-info=http://www.rsyslog.com;] restart I then upgraded it to Sid and hupped rsyslog, just in case it was some sort of obscure versioned library dependency; but it was still there: May 27 22:10:45 debian kernel: Kernel logging (proc) stopped. rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=9000 x-info=http://www.rsyslog.com;] exiting on signal 15. May 27 22:10:45 debian rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=9000 x-info=http://www.rsyslog.com;] exiting on signal 15. May 27 22:10:48 debian kernel: imklog 3.22.0, log source = /proc/kmsg started. rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=15674 x-info=http://www.rsyslog.com;] restart May 27 22:10:48 debian rsyslogd: [origin software=rsyslogd swVersion=3.22.0 x-pid=15674 x-info=http://www.rsyslog.com;] restart May 27 22:10:48 debian rsyslogd-2040: error accessing config file or directory '/etc/rsyslog.d/*.conf': Success [try http://www.rsyslog.com/e/2040 ] May 27 22:10:48 debian rsyslogd: the last error occured in /etc/rsyslog.conf, line 46 ↑ (I think nobody's reported that misspelling of occurred yet.) -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529208: fvwm: typo in Replaces: line (fvwmtabss)
Package: fvwm Version: 1:2.5.27.ds-3 Severity: minor Tags: patch Conflicts: fvwm-beta, fvwm-common, fvwmtabs, fvwm-gnome Replaces: fvwm-beta, fvwm-common, fvwmtabss, fvwm-gnome ^ This bug has probably already bitten anybody it was ever going to bite, but here's a typo-fix patch anyway. Thankyou for maintaining FVWM! -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru fvwm-2.5.27.ds.pristine/debian/control fvwm-2.5.27.ds/debian/control --- fvwm-2.5.27.ds.pristine/debian/control 2009-05-18 00:31:27.0 +0100 +++ fvwm-2.5.27.ds/debian/control 2009-05-18 00:37:28.0 +0100 @@ -26,7 +26,7 @@ Suggests: fvwm-themes, m4, cpp, menu (=1.5), wm-icons Provides: x-window-manager, fvwm-gnome Conflicts: fvwm-beta, fvwm-common, fvwmtabs, fvwm-gnome -Replaces: fvwm-beta, fvwm-common, fvwmtabss, fvwm-gnome +Replaces: fvwm-beta, fvwm-common, fvwmtabs, fvwm-gnome Description: F(?) Virtual Window Manager FVWM is a powerful ICCCM2 compliant multiple virtual desktop window manager for the X Window System. FVWM requires relatively little memory.
Bug#526587: /etc/cron.weekly/apt-xapian-index gives DeprecationWarning
Package: apt-xapian-index Version: 0.18 Severity: minor Tags: patch When there's work to do, the cron.weekly (ana)cron job sends me an error message, as follows. /etc/cron.weekly/apt-xapian-index: /usr/share/apt-xapian-index/plugins/debtags.py:92: DeprecationWarning: Use tags_of_package instead for tag in self.db.tagsOfPackage(pkg.name): Even a Python ignoramus like me can fix that one: it's s/tagsOfPackage/tags_of_package/ (on lines 92 _and_ 105). Trivial patch attached which Works For Me. (This is presumably the kid brother of the much nastier python-apt issues already reported, but unlike them it still seems to be present in the version 0.19 in Sid, as far as I can tell.) -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.29.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-xapian-index depends on: ii python2.5.4-2An interactive high-level object-o ii python-apt0.7.8 Python interface to libapt-pkg ii python-debian 0.1.13 Python modules to work with Debian ii python-xapian 1.0.10-1 Xapian search engine interface for apt-xapian-index recommends no packages. apt-xapian-index suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) --- debtags.py.old 2009-05-01 23:24:51.0 +0100 +++ debtags.py.new 2009-05-01 23:00:19.0 +0100 @@ -89,7 +89,7 @@ document is the document to update pkg is the python-apt Package object for this package -for tag in self.db.tagsOfPackage(pkg.name): +for tag in self.db.tags_of_package(pkg.name): document.add_term(XT+tag) def indexDeb822(self, document, pkg): @@ -102,7 +102,7 @@ document is the document to update pkg is the Deb822 object for this package -for tag in self.db.tagsOfPackage(pkg[Package]): +for tag in self.db.tags_of_package(pkg[Package]): document.add_term(XT+tag) def init():
Bug#525275: dict-freedict-deu-eng: description of notruf contains non-printable chars
From: Justin B Rye j...@xibalba.demon.co.uk To: Kęstutis Biliūnas ke...@kaunas.init.lt Cc: Timo Juhani Lindfors timo.lindf...@iki.fi Bcc: Subject: Re: Bug#525275: dict-freedict-deu-eng: description of notruf contains non-printable chars Reply-To: In-Reply-To: 49f234dd.2030...@kaunas.init.lt Kęstutis Biliūnas wrote: Notruf [noËtruËf] (n) , s.(m ) emergency call It seems that the reason that in the translation transcriptions are used character MODIFIER LETTER TRIANGULAR COLON 'ː' (UTF-8: 0xCB 0x90), instead of a simple symbol COLONY ':' (0x3A). [ː] is the correct length-mark character for use in a phonetic transcription, and it's only one of many IPA symbols that require those wordlists to be in UTF-8 - compare the entry for Geschenkkorb [gəʃɛŋkɔrp] (n) , s.(m ). The problem is that the bugreporter is using a legacy ISO-8859-1 charmap. Dict might fail more gracefully, but it's got to fail. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523372: consolekit: Couldn't read /proc/'pid_number'/environ
Me too. I get both sorts of WARNINGs and the sixty-odd TIDs, which isn't exactly a bug: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/148454 Michael Biebl wrote: Does it help if you change in /usr/share/dbus-1/system-services/org.freedesktop.ConsoleKit.service the following line Exec=/usr/sbin/console-kit-daemon to Exec=/usr/sbin/console-kit-daemon --no-daemon Yes; for me this fixes everything. The daemon is still running, but apparently in no-daemon mode. What does that mean? Does it have any disadvantages for single-user machines? Does it have any advantages over using Exec=/bin/true? And above all, is there a way of configuring this in /etc, so that I can be confident it will survive the next apt-get run? (reboot afterwards) /etc/init.d/dbus restart was enough. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.29.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages consolekit depends on: ii dbus 1.2.12-1 simple interprocess messaging syst ii libc6 2.9-4 GNU C Library: Shared libraries ii libck-connector0 0.3.0-2 ConsoleKit libraries ii libdbus-1-31.2.12-1 simple interprocess messaging syst ii libdbus-glib-1-2 0.80-3simple interprocess messaging syst ii libglib2.0-0 2.20.0-2 The GLib library of C routines ii libx11-6 2:1.2.1-1 X11 client-side library ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime Versions of packages consolekit recommends: ii libpam-ck-connector 0.3.0-2ConsoleKit PAM module consolekit suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525074: /var/log/apt/term.log is mode 0600
Package: apt
Version: 0.7.21
Severity: minor
Tags: patch
/var/log/apt is a new feature of APT in Lenny; I'm glad to see it,
and I'm sure lots of other people would be grateful too if there was
any mention of it in the documentation or changelog!
Unlike /var/log/dpkg.log (which is readable for the adm group) or
/var/log/aptitude (which is simply world-readable), and even unlike
the /var/log/apt directory itself (mode 0755), the term.log files
created within it are accessible only to the superuser.
Now, I'm no programmer, but a grep through the sources shows me a
line in apt-pkg/deb/dpkgpm.cc that goes:
chmod(logfile_name.c_str(), 0600);
Now, I have no idea why this line is present, but changing it to
0644, rebuilding, crossing my fingers, and installing fixes my bug.
Of course, even if you agree that 0600 is wrong you might prefer to
make it come out as root:adm 0640, but that would be beyond my
trivial patching abilities.
--
JBR
Ankh kak! (Ancient Egyptian blessing)
--- ../apt-0.7.21/apt-pkg/deb/dpkgpm.cc 2009-04-14 13:20:29.0 +0100
+++ apt-pkg/deb/dpkgpm.cc 2009-04-21 21:31:35.0 +0100
@@ -524,7 +524,7 @@
if (!logfile_name.empty())
{
term_out = fopen(logfile_name.c_str(),a);
- chmod(logfile_name.c_str(), 0600);
+ chmod(logfile_name.c_str(), 0644);
// output current time
char outstr[200];
time_t t = time(NULL);
Bug#523501: dlocate -S gives usage summary from locate
Package: dlocate Version: 0.96.1 Severity: minor Tags: patch If I say: dlocate -S $(locate /bogusfilename) the fruitless invocation of locate returns the zero-length argument ; dlocate balks and returns a usage summary. Fair enough. However, if I say: dlocate -S $(locate /bogusfilename) in this case dlocate is tricked into passing on the nonexistent argument to GNU locate, which confusingly returns an error message of its own. To top it off, if I try: dlocate -S $(locate) this gives two locate usage messages, not necessarily for the same brand of locate! Surely dlocate should always start by checking whether it has any arguments, and if not, give its usage summary error? At present, it not only allows runs with no $PKGS, it even corrects an empty $PKGS_REGEXP to '^$' - I don't see how that could ever be useful. This may imply I'm missing something, but never mind, here's a one-liner patch that fixes the subject-line bug. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i586) Kernel: Linux 2.6.28.custom Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dlocate depends on: ii dctrl-tools [grep-dctrl 2.13.1 Command-line tools to process Debi ii dpkg1.14.25 Debian package management system ii findutils 4.4.0-2 utilities for finding files--find, ii gawk [awk] 1:3.1.5.dfsg-4.1 GNU awk, a pattern scanning and pr ii locate 4.4.0-2 maintain and query an index of a d ii mawk [awk] 1.3.3-11.1 a pattern scanning and text proces ii perl5.10.0-19Larry Wall's Practical Extraction dlocate recommends no packages. dlocate suggests no packages. -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ur dlocate-0.96.1.pristine/dlocate dlocate-0.96.1/dlocate --- dlocate-0.96.1.pristine/dlocate 2008-06-27 11:10:05.0 +0100 +++ dlocate-0.96.1/dlocate 2009-04-10 02:20:11.0 +0100 @@ -145,6 +145,9 @@ done PKGS=$(echo $PKGS | sed -e s/^$SEPARATOR//) + +[ $PKGS ] || dlocate_help + #echo $PKGS PKGS_REGEXP=$(echo $PKGS | sed -e s/$SEPARATOR/|/g)
Bug#523004: nodm: initscript ignores NODM_ENABLED=false
Package: nodm Version: 0.2 Severity: important Tags: patch When I install nodm on a machine where sh == dash: Unpacking nodm (from .../apt/archives/nodm_0.2_i386.deb) ... Processing triggers for man-db ... Setting up nodm (0.2) ... [: 74: false: unexpected operator [: 74: false: unexpected operator Press return to continue. And even though I've left it configured with the default NODM_ENABLED value of false, it starts. This is caused by a bashism in the initscript; checkbashisms says possible bashism in /etc/init.d/nodm line 52 (should be 'b = a'): if [ $NODM_ENABLED == no ] || [ $NODM_ENABLED == false ] That is, it should be if [ $NODM_ENABLED = no ] || [ $NODM_ENABLED = false ] This fails the Lenny release goal of dash-compatibility, so it should probably count as release-critical, but I'll call it important. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.29.custom (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nodm depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii libc6 2.9-4 GNU C Library: Shared libraries ii libpam0g 1.0.1-9Pluggable Authentication Modules l ii x11-common1:7.3+18 X Window System (X.Org) infrastruc ii xinit 1.1.1-1X server initialisation tool ii xterm [x-terminal-emulator] 242-1 X terminal emulator nodm recommends no packages. nodm suggests no packages. -- debconf information: nodm/xinit: /usr/bin/xinit nodm/xsession: /etc/X11/Xsession nodm/x_options: vt7 -nolisten tcp nodm/min_session_time: 60 * nodm/enabled: false nodm/user: root -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523004: Acknowledgement (nodm: initscript ignores NODM_ENABLED=false)
If you wish to submit further information on this problem, please send it to 523...@bugs.debian.org, as before. Oops, like that trivial patch I said I was going to attach: --- ../nodm-0.2/debian/nodm.init2009-02-23 18:02:07.0 + +++ debian/nodm.init2009-04-07 19:44:50.0 +0100 @@ -49,7 +49,7 @@ case $1 in start) [ $VERBOSE != no ] log_daemon_msg Starting $DESC $NAME - if [ $NODM_ENABLED == no ] || [ $NODM_ENABLED == false ] + if [ $NODM_ENABLED = no ] || [ $NODM_ENABLED = false ] then log_warning_msg Not starting $NAME because NODM_ENABLED is '$NODM_ENABLED' in /etc/default/$NAME else -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522128: grub-common: grub: No video mode activated
Just after midnight (localtime), 2009/03/31, Justin B Rye wrote: grub2's boot-time invocation of background_image /path/to/image (as defined in /etc/grub.d/05_debian_theme) no longer succeeds; [...] In case people think this was an April Fools' Day prank, let me confirm that it's a real bug that goes away if I manually downgrade to 1.96+20080724-16. It has to be both grub-common and grub-pc or the update-grub call won't work. (A side benefit of keeping grub on hold is that I no longer have to read warning messages about how you're reorganising the internals of the update-grub command every time I upgrade my kernel. What are sysadmins expected to do about that, anyway?) -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522128: grub-common: grub: No video mode activated
Package: grub-common Version: 1.96+20090317-1 Severity: normal grub2's boot-time invocation of background_image /path/to/image (as defined in /etc/grub.d/05_debian_theme) no longer succeeds; trying it on the grub commandline returns grub: No video mode activated. This is presumably related to the fact that running vbetest eventually returns cannot set VBE mode 3, but until somebody manages to WTFM I'm rather shooting in the dark here. This failure to set a background image is a regression from the version previously in Testing, which was 1.96+20080724-16 (it's a regression from grub-legacy, come to that). I took an otherwise similar computer and checked: before grub-common was upgraded to 1.96+20090317-1, vbetest and background_image worked; afterwards, they didn't. No other other changes - in particular, grub-pc did not need to be upgraded to 1.96+20090317-1 to produce this effect. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.28.xan Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grub-common depends on: ii base-files 5.0 Debian base system miscellaneous f ii libc6 2.9-4 GNU C Library: Shared libraries ii libfreetype6 2.3.7-2 FreeType 2 font engine, shared lib ii libncurses55.7+20090314-1shared libraries for terminal hand ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime grub-common recommends no packages. Versions of packages grub-common suggests: ii multiboot-doc 0.97-47lenny2 The Multiboot specification -- no debconf information -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#452492: qalculate-kde: Celsius misspelled as celcius
Package: qalculate-kde Followup-For: Bug #452492 Tags: patch Since no units are capitalized in this line, I don't think that is a bug. I will close this bug if you have no objections. Excuse me jumping in here, but I don't see any indication that the original 2007 bugreporter (Davide Mancusi are...@gmail.com) has received a copy of your call for objections... Please, re-read the subject line (or the content of the bugreport). CELCIUS is not, even disregarding case, the same ASCII string as CELSIUS. ^ The typo seems to originate in doc/en/qalculate_kde/units.docbook; patch attached. Hope this helps... -- JBR Ankh kak! (Ancient Egyptian blessing) diff -ru qalculate-kde-0.9.6.pristine/doc/en/qalculate_kde/units.docbook qalculate-kde-0.9.6/doc/en/qalculate_kde/units.docbook --- qalculate-kde-0.9.6.pristine/doc/en/qalculate_kde/units.docbook 2007-06-17 12:42:34.0 +0100 +++ qalculate-kde-0.9.6/doc/en/qalculate_kde/units.docbook 2009-03-03 21:26:13.0 + @@ -1037,7 +1037,7 @@ entrypara1055.056/para/entry /row row valign=top -entryparaCalorie (15 degrees Celcius)/para/entry +entryparaCalorie (15 degrees Celsius)/para/entry entryparacal_fifteen/para/entry entryparaJ/para/entry entrypara4.185880 (approximate)/para/entry @@ -3021,8 +3021,8 @@ /thead tbody row valign=top -entryparaDegree Celcius/para/entry -entryparaoC / °C / celcius/para/entry +entryparaDegree Celsius/para/entry +entryparaoC / °C / celsius/para/entry entryparaK/para/entry entrypara\x + 273.15/para/entry /row
Bug#516436: 6.2.2: talks nonsense about appositive clauses
Package: developers-reference
Version: 3.4.1
Severity: normal
Tags: patch
This report has been brewing on debian-l10n-english for years - see
http://lists.debian.org/debian-l10n-english/2008/08/msg4.html;
The advice in DevRef 6.2.2 about package short descriptions is good,
but it's undermined by the fact that the rationale given is hogwash.
For a start:
# An appositive clause is defined in WordNet as a grammatical
# relation between a word and a noun phrase
Alas, valid package synopses are _not_ appositive clauses (indeed,
they're neither appositive nor clauses); clauses are not grammatical
relations; and what's more, WordNet has no such entry.
Now, the use of this kind of pseudoscientific gobbledygook in
justification for a rule may offend me as a linguistics graduate,
but that doesn't mean I want to see it replaced with an accurate
version. Even if every word of it was true, it would still be a bad
idea to base policy guidelines on a set of formal syntactic
principles, since most Debian package maintainers have had no
particular training in English syntactic analysis.
Besides, the grammatical rules clearly aren't the real reason for
the rule. If we're going to justify our advice, we should explain
it in terms of the real benefits it brings, such as that
standardising makes it easier for users to browse through a list of
short descriptions.
My patch concentrates on providing templates that developers can fit
their proposed synopses into. If you're interested in thrashing out
details of the wording, now would be a good time to bring it back to
debian-l10n-engl...@lists.debian.org, since there are more posters
around than usual.
--
JBR Uqarituukasippungaasiit (one word in West Greenlandic)
Silly me, I went and spoke out of turn as usual!
diff -ru ../developers-reference-3.4.0.pristine/best-pkging-practices.dbk ./best-pkging-practices.dbk
--- ../developers-reference-3.4.0.pristine/best-pkging-practices.dbk 2008-06-02 11:29:07.0 +0100
+++ ./best-pkging-practices.dbk 2009-02-20 20:53:11.0 +
@@ -210,41 +210,50 @@
section id=bpp-pkg-synopsis
titleThe package synopsis, or short description/title
para
-The synopsis line (the short description) should be concise. It must not
-repeat the package's name (this is policy).
+Policy says the synopsis line (the short description) must be concise, not
+repeating the package name, but also informative.
/para
para
-It's a good idea to think of the synopsis as an appositive clause, not a full
-sentence. An appositive clause is defined in WordNet as a grammatical relation
-between a word and a noun phrase that follows, e.g., Rudolph the red-nosed
-reindeer. The appositive clause here is red-nosed reindeer. Since the
-synopsis is a clause, rather than a full sentence, we recommend that it neither
-start with a capital nor end with a full stop (period). It should also not
-begin with an article, either definite (the) or indefinite (a or an).
-/para
-para
-It might help to imagine that the synopsis is combined with the package name in
-the following way:
+The synopsis functions as a phrase describing the package, not a complete
+sentence, so sentential punctuation is inappropriate: it does not need extra
+capital letters or a final period (full stop). It should also omit any initial
+indefinite or definite article - a, an, or the. Thus for instance:
/para
screen
-replaceablepackage-name/replaceable is a replaceablesynopsis/replaceable.
+Package: libeg0
+Description: exemplification support library
/screen
para
-Alternatively, it might make sense to think of it as
+Technically this is a noun phrase minus articles, as opposed to a verb phrase.
+A good heuristic is that it should be possible to substitute the package name
+and synopsis into this formula:
/para
-screen
-replaceablepackage-name/replaceable is replaceablesynopsis/replaceable.
-/screen
para
-or, if the package name itself is a plural (such as developers-tools)
+The package replaceablename/replaceable provides {a,an,the,some}
+replaceablesynopsis/replaceable.
+/para
+para
+Sets of related packages may use an alternative scheme that divides the
+synopsis into two parts, the first a description of the whole suite and the
+second a summary of the package's role within it:
/para
screen
-replaceablepackage-name/replaceable are replaceablesynopsis/replaceable.
+Package: eg-tools
+Description: simple exemplification system (utilities)
+
+Package: eg-doc
+Description: simple exemplification system - documentation
/screen
para
-This way of forming a sentence from the package name and synopsis should be
-considered as a heuristic and not a strict rule. There are some cases where it
-doesn't make sense to try to form a sentence.
+These synopses follow a modified formula. Where a package
+replaceablename/replaceable has a synopsis
+replaceablesuite/replaceable (replaceablerole/replaceable) or
+replaceablesuite/replaceable -
Bug#515656: closed by Andreas Metzler ametz...@downhill.at.eu.org (Re: Bug#515656: out-of-date /usr/share/doc-base/findutils)
Andreas Metzler wrote: I think the doc-base entry is still fine, since the documentation still covers GNU locate. Closing. Except that the doc-base entry doesn't say anything about GNU; it just claims to be documenting locate. On a given Debian system, GNU locate may or may not even be installed, and locate may mean slocate or mlocate; if that's the case, telling users all about a different implementation of the command is unhelpful. The only way users are going to have a chance of second-guessing it is if they happen to be familiar with the way the upstream tarballs are organised. So okay, you're right, it's not a bug, it's a can of worms. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
