Bug#404034: looks correct
Back in 2006, Reuben Thomas wrote:
>> "A priori, that is, form these necessities of the": form --> from
Ritesh Raj Sarraf wrote:
> I don't think this is a typo.
> "form these necessities of the mind"
> prepare the thought and wild ideas that are already running in your mind.
It's definitely a typo. The Coleridge quote is from "Aids to
Reflection" (1825), page 397, and if you search Google Books you'll
see he wrote "from" (which makes sense), not "form" (which doesn't).
# Metaphysics are the science which determines what can, and what
# can not, be known of Being and the Laws of Being, _a_priori_,
# (that is, from those necessities of the mind or forms of thinking,
# which, though first revealed to us by experience, must yet have
# pre-existed in order to make experience itself possible.
("A priori" might be literally translated "from previous".)
--
JBR
Ankh kak! (Ancient Egyptian blessing)
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101004073520.ga25...@xibalba.demon.co.uk
Bug#627880: Typo in long description (Lainux/Linux)
David Paleino wrote:
> Package: flashybrid
> Severity: minor
> Version: 0.16
>
> Hello Kirill,
> please read http://www.debian.org/Bugs/Reporting to learn how to correctly
> report a bug in a package in Debian.
Well, if it's going to be reported, let's get all the rest of the
problems in this description patched too. Meanwhile, does anybody
know if the package still works with the new /run layout in Sid?
> On Wed, 25 May 2011 12:50:26 +0600, Kirill Aleksandrovich wrote:
>> [..]
He didn't mention the short description:
Description: automates use of a flash disk as the root filesystem
That's a non-DevRef-compliant verb phrase, and not really accurate.
Just installing this package doesn't automatically convert my system
to run out of /ram - that takes some manual work and a reboot!
Description: setup tools for using a flash disk as the root file system
>> Flashybrid is a system to help in setting up and managing hybrid
>> flash/disk/ram based Debian systems which can run most of the time using
"Ram based" must be like using a dead badger. s/ram /RAM-/
It's not clear what the "most of the time" here is intended to mean,
but the most obvious interpretation is that it modifies "can" - that
is, sometimes they randomly fail to run. I'd suggest just removing
the phrase. Oh, and I'll shuffle some commas.
>> only a small flash disk for their root filesystem and do a useful, but
>> limited task (such as being a router, or a PDA, or a rescue system on a
s/do a useful, but limited task (/perform limited but useful tasks /
>> USB keydrive). The flash can be as small as 32 mb, though 64 to 256 mb
>> is more comfortable.
Millibits? s/mb/MB/
>> To use this package, you will need a 2.4 or greater version of the
>> Lainux kernel, with tmpfs support built in.
>>
>> Lainux /= Linux.
Furthermore, "2.4 or greater" = "any version of Linux supported by
Debian for a very long time", so this whole paragraph is pointless...
except that these days the package should probably be tagged as
"Architecture: linux-any" rather than "all", but since I'm not certain
about that I'll leave it out of this patch.
The 404ing "Homepage" is clear enough, though - I'll remove that line.
--
JBR
Not a developer or even a flashybrid user
diff -ru flashybrid-0.16.pristine/debian/control flashybrid-0.16/debian/control
--- flashybrid-0.16.pristine/debian/control 2010-10-10 22:10:14.0 +0100
+++ flashybrid-0.16/debian/control 2011-05-25 13:13:09.769623054 +0100
@@ -4,18 +4,14 @@
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 5.0.0), po-debconf
Standards-Version: 3.7.2
-Homepage: http://www.xorcom.com/rapid/
Package: flashybrid
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, rsync
-Description: automates use of a flash disk as the root filesystem
+Description: setup tools for using a flash disk as the root file system
Flashybrid is a system to help in setting up and managing hybrid
- flash/disk/ram based Debian systems which can run most of the time
- using only a small flash disk for their root filesystem and do a useful,
- but limited task (such as being a router, or a PDA, or a rescue system
- on a USB keydrive). The flash can be as small as 32 mb, though 64 to 256
- mb is more comfortable.
- .
- To use this package, you will need a 2.4 or greater version of the Lainux
- kernel, with tmpfs support built in.
+ flash/disk/RAM-based Debian systems, which can run using only a small
+ flash disk for their root file system and perform limited but useful
+ tasks such as being a router, or a PDA, or a rescue system on a USB
+ keydrive. The flash can be as small as 32 MB, though 64 to 256 MB is
+ more comfortable.
Bug#681190: xfonts-intl-phonetic: package description review
Package: xfonts-intl-phonetic Version: 1.2.1-8 Severity: wishlist Tags: patch I noticed a couple of minor spelling/language issues in the package descriptions for xfonts-intl-phonetic and emacs-intl-fonts, and naturally ended up reviewing the whole control file. (This isn't connected to the review for fonts-gfs-neohellenic that just came up as bug #680936 - I was already looking at this before then.) [...] > Package: xfonts-intl-arabic [...] > Description: International fonts for X -- Arabic ^ ^^ The debian-l10n-english house style (and DevRef) would recommend lowercase "I" and single dash. > This package includes some Arabic fonts (digits and single and double > column). You will need the fonts if you plan to view, print or author > documents written in any of the Arabic languages. "Single and double column" should probably have "characters" on the end, and "you will need the fonts" should probably say "these fonts". The d-l-e house style would add a "Harvard" comma after "print" (and that style is already used in most lists in these descriptions). "The Arabic languages" looks like an error - you could write Urdu (an Indo-European language) with these fonts but not Maltese (a form of Arabic). Say "documents written in an Arabic script". > . > The fonts are for use with the X Window System. > > Package: xfonts-intl-asian [...] > Description: International fonts for X -- Asian > This package includes some Vietnamese, Indian, Lao, and Thai fonts. > You will need the fonts if you plan to view, print or author documents > written in any of the languages mentioned above. A nomenclature problem: Hebrew, Korean, and Uzbek are also "Asian", but out of scope for this collection; so wouldn't it make sense to use some slightly more specific geographical label for these? After all, it's clearly a grouping by region rather than anything more fundamental or it wouldn't include VISCII. Saying "(south-east) Asian" is a bit unwieldy, but there's room for it in the synopsis. Then, what sort of order is "Vietnamese, Indian, Lao, and Thai"? I'm tempted to suggest "Indian and Indochinese"; that would misleadingly suggest it includes Khmer, but then again I already suspect that "Indian" overstates its coverage. And finally, the things listed above aren't all languages, or even individual scripts; "Indian" is a whole family of scripts. Perhaps "languages/scripts" would be vague enough. > . > The fonts are for use with the X Window System. > > Package: xfonts-intl-chinese [...] > Description: International fonts for X -- Chinese > This package includes some GB2312, GB8565-88, BIG5 (ETen), and SiSheng > Chinese fonts. You will need the fonts if you plan to view, print or author > documents written in Chinese and using any of the encodings mentioned above. "BIG5" should be "Big5" (it's not B.I.G.; it was developed by Taiwan's top five IT firms). But I have no idea what "SiSheng fonts" would be; isn't SiSheng a way of entering tone diacritics? Oh well, the rest of it more or less makes sense. (Why does this one, unlike for instance -arabic, go into so much detail about encodings when the level of coverage makes encodings more or less irrelevant? Couldn't it just say "documents written in Chinese", and stop there?) > . > The fonts are for use with the X Window System. > > Package: xfonts-intl-chinese-big [...] > Description: International fonts for X -- Chinese big > This package includes some GB2312 big Chinese fonts. > You will need the fonts if you plan to view, print or author > documents written in Chinese and using any of the encodings mentioned above. Since "big" here means simply "large point-size", it should probably use the word "large" and not one that makes readers wonder whether it has something to do with Big5 or big-endianness or extensive character sets. "Any of the encodings" isn't appropriate here. > . > The fonts are for use with the X Window System. > > Package: xfonts-intl-european [...] > Description: International fonts for X -- European > This package includes some ISO 8859-1 (Latin-1), ISO 8859-2 (Latin-2), > ISO 8859-3 (Latin-3), ISO 8859-4 (Latin-4), ISO 8859-5 (Cyrillic), > ISO 8859-7 (Greek), ISO 8859-8 (Hebrew), ISO 8859-9 (Latin-5), and KOI > (Cyrillic) fonts. Also one ISO 8859-1 big font is included. > You will need the fonts if you plan to view, print or author documents > using any of the languages/encodings specified above. As I mentioned, Hebrew is Asian (and a member of the "Afroasiatic" language family), but I suppose if Israel gets into the Eurovision Song Contest then Hebrew might as well be in the European font package too (and we'll forget about the other continents that use Latin-based scripts). I'll just rephrase the line about the "big font", change "languages" to "scripts", and call that done. The encodings are even listed in a sensible order! (But why do the different packages disagree abo
Re: Please review package description of (open)motif
Paul Gevers wrote: > [Please keep cc in the loop.] > > Currently, Graham and I are working on getting (open)motif [1] in shape > for inclusion in main. While I was going through the package I was > unhappy with the current description of the binary packages. I have > already extended the description of motif-clients, but I would like a > review of all descriptions. Okay - I'll start with that and go back to the others, then: > Package: motif-clients What does this package name mean, anyway? Is the idea that it's a set of executables that have a client relationship towards Motif, whatever that means, or are they just Motif-based tools that happen (obviously) to be graphical, and therefore (obviously) count as X11 clients? Either way, it seems an odd way of looking at things. Why would a user search for and then install this package? If the point of the exercise is to get a Motif-flavoured X environment, wouldn't it make more sense to call the package simply "mwm - Motif Window Manager"? But I'll assume not for now. [...] > Description: Motif window manager and virtual key bindings configure client That is, mwm and xmbind, right? I'm dubious about this expression "configure client"; I'd be a lot happier with something more like "configuring utility" or "configuration widget" - or less longwindedly "setup tool". Then again, what good is the word "virtual" doing us here? Okay, virtual key bindings are in software, and this tool doesn't claim to be capable of changing the physical arrangement of keys, but is that really a misunderstanding that readers would otherwise be prone to? Oh... and looking up the man pages I see that the bindings in question also cover mouse events, so "virtual key bindings" isn't even pedantically accurate. It's a more general MWM configurator. And since we've already mentioned MWM we could just say: Description: Motif window manager and setup tool But why do we even need to care about xmbind? Most packages that contain window managers also contain one or two other trivial helper binaries; but they put the focus in the packagename and synopsis on the thing that users might actually want to install. So again I'm back to wondering why this isn't "Description: Motif Window Manager" (but again that's not in my patch). > Motif is the industry standard toolkit for *NIX systems. This package Surely the standard toolkit for *NIX systems is something more like coreutils? Or if we're talking "graphical" it would be X... should we perhaps call it "the standard GUI component toolkit for *NIX"? We could also insert a linebreak to get a paragraph that could fit neatly at the start of each package description in the set as a boilerplate intro. > contains the Motif window manager, which has clear but classical appearance, "(It) has clear appearance" sounds like it's missing an article. (Classical? Now I'm imagining a Roman mosaic tiled window manager.) > and xmbind, which is used to configure virtual key bindings for motif. Since we're not pressed for space here I'll suggest expanding this to "virtual key/mouse-bindings". At last one that I'm sure isn't just me: s/motif/Motif/. > [1] http://packages.qa.debian.org/o/openmotif.html (So "OpenMotif" is the old non-free version and now it's gone LGPL it's called plain "Motif"? Okay, confusing.) > Source: motif > Section: devel (Wait, why is the source package's Section set to something not used by any of the binary packages?) [...] > Package: libmotif4 [...] > Description: Motif - shared libraries > This package includes all files you need to run Motif > applications which are linked against Motif, which > are the shared libraries for the most part. This is a clumsy effort to explain stuff that's mostly implicit in the Debian packaging dependency system. Just say: Description: Motif - shared libraries Motif is the industry standard GUI component toolkit for *NIX. . This package contains the shared libraries and associated files. And so on cut'n'pastily: > Package: libmotif4-dbg [...] > Description: Motif - shared libraries debugging symbols English doesn't normally pluralise the nouns in a stack like that. Come to that, synopses don't usually take the time to explain that the debugging symbols are for the shared libraries. Just say: Description: Motif - debugging symbols > This package includes all files you need to run Motif > applications which are linked against Motif, which > are the shared libraries for the most part. No it doesn't. Or at least, not the normal ones. > . > This package contains the debugging symbols. Turn the first paragraph into our boilerplate and it's done. > Package: libmotif-dev [...] > Description: Motif - development files > Everything you need to build Motif applications with > Motif. This includes header files, static libraries, > the manual pages for the Motif API and uil (user interface > language compiler) This has a bit more content to it,
Re: Please review package description of (open)motif
Paul Gevers wrote: > Agreeing with your argument, I would go for > > Description: Motif Window Manager Oh! Hurrah. [...] >>> contains the Motif window manager, which has clear but classical >>> appearance, >> >> "(It) has clear appearance" sounds like it's missing an article. >> >> (Classical? Now I'm imagining a Roman mosaic tiled window manager.) > > Sorry, I am not a native speaker. I try to say that it looks a dated > (already a decade). Would that be a better word than? It's possible that it should really be "classic", but you'll notice I kept "classical" in my patch; it makes rather a good euphemism for "so antique it's stylish". It even makes me think of all those chiselled edges as a sort of monumental-architecture feature. >>> and xmbind, which is used to configure virtual key bindings for motif. >> >> Since we're not pressed for space here I'll suggest expanding this to >> "virtual key/mouse-bindings". > > Sure. Maybe we should even focus less on xmbind. Make the first part > about MWM end with a full stop and mention it more as an auxiliary tool: > > This package contains the Motif window manager, which has a clear but > classical appearance. It is accompanied by xmbind, which is used to > configure virtual key/mouse-bindings for Motif. Yes, that works. >> (So "OpenMotif" is the old non-free version and now it's gone LGPL >> it's called plain "Motif"? Okay, confusing.) > > Yes. Indeed. Motif has been used in the past for the group of software > implementations of motif: the paid variant, the free (but not dsfg-free) > version openmotif and lesstif, which was the only really free > implementation of motif. By sheer coincidence your initial mail reached me just as I finished finally uninstalling (nedit and therefore) lesstif2 on my desktop. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130119160337.ga26...@xibalba.demon.co.uk
Re: [RFR] templates://isdnutils/{ipppd.templates,isdnlog.templates,isdnutils-b ase.templates,isdnvboxserver.templates}
Christian Perrier wrote:
> Preamble: I *did not* review debian/control for this package. [...]
Okay, I'll keep my hands off the package descriptions too. They
aren't great, but they're intelligible.
> Template: ipppd/ispphone
[...]
> At least one phone number has to be dialed in order to connect
> - to your Internet service provider (ISP).
> + to the Internet service provider (ISP).
That makes it sound as if there's only one ISP in the world. It's
hard to avoid "your" here... but I suppose in this particular case
we could make it "to _an_ ISP".
> Template: ipppd/isplogin
[...]
> +_Description: ISP user name:
> + Most ISPs require a user name and password to be provided when
> + connecting.
The terminology I'm used to here is "account name" (it's definitely
not the name of the user).
> Template: ipppd/isppasswd
[...]
> +_Description: ISP password:
> + Please enter the password to use when connecting to the ISP. This password
> + will be kept in /etc/ppp/pap-secrets and
> + /etc/ppp/chap-secrets together along with the username.
together with the account name.
"Together with" or "along with", not "together along with".
> --- isdnutils.old/debian/isdnlog.templates2009-09-18 18:26:24.672339165
> +0200
> +++ isdnutils/debian/isdnlog.templates2009-09-18 19:02:09.349343195
> +0200
> @@ -1,52 +1,54 @@
> Template: isdnlog/country
[...]
> + Please choose the local country. This will be used to set the rate table to
> + use for calculating the calls costs
This makes me think "but didn't I tell my computer this about ten
seconds after I inserted the debian-installer CD?", but never mind.
> Template: isdnlog/isdnrate-daemon
[...]
> + This setting is only useful for people with special requirements, such as
> those using the
> + isdn2h323 package.
There is no isdn2h323 package - debian-legal decided it was
undistributable (GPL with extra restrictions). We could say:
This setting is only useful for special setups, such as for an
ISDN-to-H.323 gateway.
> _Description: Firmware to load:
> + Some ISDN cards can't function properly until some firmware has been
> + loaded. A notable example is the Sedlbauer SpeedFax+ PCI or Siemens
> I-Surf, which need ISAR.BIN to be loaded. Choose "ISAR.BIN" if this is
> + necessary.
That's two: "Notable examples are the Sedlbauer SpeedFax+ PCI and
Siemens I-Surf, which need [...]"
> Template: isdnutils/firmwarecards
[...]
> + If you use more than one card, enter the number of the card(s) that need
> + the firmware to be loaded.
There are verb agreement issues lurking in this sentence ("the card
or cards that needs or need the firmware"); I'd like to avoid the
issue by saying "the card(s) in need of firmware".
> Template: isdnvboxserver/user
[...]
> +_Description: Login for the answering machine:
> + When clients (using the vbox program provided by the isdnvboxclient
> + package) connect to the answering machine, they will be prompted with a
> + user name and password.
> + .
> + The user name you define here does not have to be a user on the
> + system itself.
Make that:
Connections to the answering machine (using the vbox program provided
by the isdnvboxclient package) will be prompted for a username and
password.
.
The username you define here does not have to correspond to a login
account on this system.
> Template: isdnvboxserver/vboxnodir
> Type: error
> _Description: No home directory
> - The home directory `${DIR}' for user `${USER}' doesn't exist. This means
> + The home directory `${DIR}' for user `${USER}' does not exist. This means
> that the file `${DIR}/.vbox.conf' cannot be created.
Does it really mean ${USER} here and below and not ${User}? Is it
always going to be "root" or does it redefine it?
I'll stick to standardising quotes: "", not `'.
> Template: isdnvboxserver/doinit
> Type: error
> _Description: Device in inittab doesn't agree with devfs mode
> The entry for vboxgetty in /etc/inittab uses a device name that does not
> correspond to the current devfs usage; either a devfs (/dev/isdn/ttyIxx)
> name is used in inittab while devfs is not mounted, or the non-devfs name
> is used while devfs is mounted.
"Current devfs usage"?
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru isdnutils-3.9.20060704.pristine/debian/ipppd.templates
isdnutils-3.9.20060704/debian/ipppd.templates
--- isdnutils-3.9.20060704.pristine/debian/ipppd.templates 2009-09-19
12:52:20.0 +0100
+++ isdnutils-3.9.20060704/debian/ipppd.templates 2009-09-22
09:52:28.0 +0100
@@ -1,47 +1,44 @@
Template: ipppd/ispwontdoit
Type: error
-_Description: ISP dialup config already exists
- The files device.${IPPP0} and ipppd.${IPPP0} already exist. Therefore the
+_Description: ISP dialup configuration already exists
+ The device.${IPPP0} and
Re: [RFR] templates://isdnutils/{ipppd.templates,isdnlog.templates,isdnutils-b ase.templates,isdnvboxserver.templates}
Justin B Rye wrote: > Okay, I'll keep my hands off the package descriptions too. Sorry, I got bored and reviewed it anyway. Here's a separate diff for the control file, as an alternative to just sending it in as a wishlist bug report. > --- isdnutils-3.9.20060704.pristine/debian/control2009-09-19 > 12:52:20.0 +0100 > +++ isdnutils-3.9.20060704/debian/control 2009-09-20 23:39:20.0 > +0100 > Package: isdnutils [...] > Conflicts: ipppd (<<1:3.1pre1b-23) (That's a conflicts against Potato, so rather stale, but never mind) > -Description: Most important ISDN-related packages and utilities > +Description: ISDN utilities - dependency package Standardising on "$SUITE - $COMPONENT". > - Note that for an external ISDN adapter, you do NOT need this package or any > of > - the related ones. This is only for use with an internal ISDN adapter. > - Choosing this package will select the most frequently used components. > + This package depends on the most frequently used components for an > + ISDN system using an internal adapter; they are not required for an > + external adapter. "Note that" is redundant, especially as a start. Instead start by saying what the package _is_ good for. > . > - The current version of isdnutils is split up into component packages, to > make > - it easier to fine-tune what is installed; hardly anyone needs everything. > - However, it's not possible to automatically select what is needed > - This is a dependency package to ease installation, and choosing this selects > - the most important new packages. After installation, this package can be > - safely removed. > + The isdnutils suite is split up into component packages, to make it > + easier to fine-tune what is installed; hardly anyone needs everything. > + However, it's not possible to select what is needed automatically. This > + dependency package just ensures the most important components are > + installed, and can be safely removed again once that is done. Don't expect users to think in terms of source-package names, and don't talk as if this was rapidly-evolving software. d-l-e regulars may be interested to see I've moved "automatically" to after its verb... > . > - The component packages selected by this are: > - isdnutils-base basic set of ISDN utilities. > - ipppdfor networking over ISDN with syncPPP. > - isdnlog for logging ISDN calls (and much more). > - isdnutils-xtools for X ISDN apps (currently only xisdnload and xmonisdn) > - isdnvboxserver ISDN answering machine, things needed on the server > system. > - isdnvboxclient ISDN answering machine, client side (vbox). > + The component packages involved are: > + * isdnutils-base: the basic set of ISDN utilities; > + * ipppd:for networking over ISDN with syncPPP; > + * isdnlog: for logging ISDN calls (and much more); > + * isdnutils-xtools: graphical utilities (xisdnload and xmonisdn); > + * isdnvboxclient: ISDN answering machine client; > + * isdnvboxserver: ISDN answering machine server. Just standardised and homogenised. I'm not really convinced there's any point listing the hard dependencies, but never mind. > . > - Not selected (although dselect will suggest some) are: > - isdnutils-docfor extensive documentation (basic docs are of course > - included with each package). > - isdneurofile file transfer over ISDN with the special eurofile > protocol. > - capiutilsCAPI utilies. > - pppdcapiplugin a plugin for the normal ppp daemon that uses CAPI to > - communicate over ISDN. > - libcapi20-3 shared library package needed by CAPI applications (will > be > - selected automatically when needed). > - libcapi20-devlibcapi20 development files. > - isdnactivecards firmware for mostly active ISDN cards, and other related > - tools. > + It also suggests the following optional extras: > + * capiutils: CAPI utilies; > + * isdneurofile: for file transfer over the EUROFILE protocol; > + * isdnutils-doc: additional documentation; > + * pppdcapiplugin: a CAPI plugin for the normal PPP daemon. That's homgenised, sorted, and updated; most importantly I've taken out the claims that isdnutils suggests isdnactivecards and so on. > Package: isdnutils-base [...] > -Description: ISDN utilities, the basic (minimal) set > +Description: ISDN utilities - minimal set Standardising on "$SUITE - $COMPONENT". > - These utilities are the basic set of ISDN utilities that you need when you > - have an ISDN card installed. For complete functionality compara
Re: [LCFC] templates://isdnutils/{ipppd.templates,isdnlog.templates,isdnutils-b ase.templates,isdnvboxserver.templates}
Christian Perrier wrote: > This is the last call for comments for the review of debconf > templates for isdnutils. One problem I missed last time and one I created. > Template: isdnlog/country [...] > _Description: Country: > Please choose the local country. This will be used to set the rate table to > use for calculating the calls costs That's some sort of broken possessive. Make it: use for calculating the costs of calls. > Package: isdnactivecards [...] > Description: ISDN utilities - active ISDN card support > This package provides firmware and firmware-loading utilities for active > ISDN cards (the Eicon, Eicon Diva, ICN, IBM Active 2000, or PCBIT-D cards). ^^ ^^ Oops, failed alphabetical ordering. ISDN cards (the Eicon, Eicon Diva, IBM Active 2000, ICN, or PCBIT-D cards). -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#547251: closed by Agustin Martin Domingo (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-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100411172015.ga12...@xibalba.demon.co.uk
Bug#318024: dict-freedict-afr-deu: "Africaan"?
Package: dict-freedict-afr-deu Severity: minor Tags: patch This is a dict package for translating between the languages with ISO 639-2 Alpha-3 codes "afr" and "deu", right? +---+---+---+ | 639-2 | 639-2 | Name | +---+---+---| | afr | af| Afrikaans | | deu | de| German| +---+---+---+ "Africaan" isn't right in English, German, Afrikaans, French or any other language I know of. Indeed, "Africaan-German" looks like a typo for "African-German", which would make it a monolingual dictionary for the variety of German spoken in its old colonies (parallel to "Swiss-German"). So please correct the references to "Africaan" in the packaging to "Afrikaans". (Severity: wishlist from here on. Yes, I know, it's a QA-group package with a minimal userbase, and one of many with similarly phrased descriptions, but if you're going to be changing it anyway...) Meanwhile, "This is a package of the [blah] dictionary for the dictd server software" is a redundant and slightly unnatural phrasing. We can see it's a package, any server there's a "Suggests:" for is obviously going to be software, and we can make a good guess that packages named foobar-d are going to be servers... So here's an all-in-one patch: --- wrong +++ right @@ -1,4 +1,2 @@ -Description: Dict package for Africaan-German Freedict dictionary - This is a package of the - Africaan-German Freedict dictionary - for the dictd server software. +Description: Dict package for Afrikaans/German Freedict dictionary + Afrikaans/German Freedict dictionary for dictd. -- System Information: Debian Release: 3.1 Architecture: i386 (i586) Kernel: Linux 2.6.11.hurakan Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318025: dict-freedict-sco-deu: "Scottish"?
Package: dict-freedict-sco-deu Severity: normal This is a dict package for translating between German and the variety of Gaelic spoken in Scotland, right? Well, the word "Scottish" is rarely used to refer to a language, but when it is, it isn't that one. * Gaelic (or Scots Gaelic, or Gaidhlig) is a Celtic language related to Irish (aka Irish Gaelic, or Gaeilge), with only fifty or sixty thousand speakers in total. * Scottish, or more usually Scots, is an entirely separate language (or, depending on your point of view, dialect of English) with something like one and a half million speakers. Just to confuse things, some of the speakers live in Ireland. Most of the freedict packages have been named in line with the standard ISO 639-2 Alpha-3 codes, but "sco" is Just Plain Wrong: +---+---+-+ | 639-2 | 639-2 | Name| +---+---+-| | gal | gd| Scottish Gaelic; Gaelic | | sco | | Scots | +---+---+-+ Renaming the package to dict-freedict-gal-deu may be more work than it deserves, given its QA-Group status and popcon figures, but please at least amend the Description to give a warning of this gross misnomer. -- System Information: Debian Release: 3.1 Architecture: i386 (i586) Kernel: Linux 2.6.11.hurakan Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318025: dict-freedict-sco-deu: "Scottish"?
Michael Bunk wrote: > I'm freedict upstream. Thanks for your report. Even though your introductory > question looks like a rhetoric question, since I don't know the languages > Gaelic or Scottish, I have to ask you to please answer your question :) > > Since it has only 300 headwords, I will put a note into the dictionary file. > The .deb descriptions are generated automatically. That proces would have to > be adapted to include the important notes from the dictionary file. The headwords being things like "Sasunnach" and "uisge", that's Gaelic, not Scots. See "http://www.ethnologue.com/show_language.asp?code=gla"; "http://www.ethnologue.com/show_language.asp?code=sco";. (Oh... now I notice that I garbled the ISO 639 table last time; inevitable, I suppose. Well, here's a definitive edition: "http://www.loc.gov/standards/iso639-2/englangn_ascii.html";. The appropriate three-letter code is -gla-.) It seems unlikely anybody would bother packaging a wordlist (even one this size) for "-sco-", since for a start it doesn't have a generally-agreed spelling system. And the fewer things labelled "SCO" I have on my system the better. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [RFR] templates://tpconfig/{templates}
Christian Perrier wrote:
> Your review should be sent as an answer to this mail.
Templates file:
> _Description: Options to pass to tpconfig when booting:
[...]
> + Please specify any command-line options you want passed to tpconfig at
> + boot or resume time.
> + .
> + These options will be passed after the touchpad reset if you choosed
> + that option.
"Chose", or "have chosen", or "selected"...
> + .
> + A common option is '--tapmode=0' which is meant to disable 'tapping'
> + in order to prevent spurious mouse events being caused by accidentally
> + brushing over the touchpad.
Simplify (mainly by de-passivising):
A common option is '--tapmode=0', which is meant to disable 'tapping'
so that accidentally brushing the touchpad doesn't cause spurious mouse
events.
Control file:
> -Description: configure touchpad devices
> +Description: touchpad devices configuration utility
Description: touchpad device configuration utility
Tricky one. It seems to me that if each machine had two touchpads,
then it might be "devices", but merely working on many different
models isn't enough to preserve number-agreement in a noun-pile.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- ../tpconfig.old/debian/templates 2008-12-09 19:10:11.0 +
+++ debian/templates 2008-12-09 19:13:42.0 +
@@ -1,25 +1,30 @@
Template: tpconfig/overwrite-config-file
Type: boolean
Default: true
-_Description: Manage tpconfig configuration file with debconf?
- The tpconfig configuration file, "/etc/default/tpconfig", can be handled
- automatically by debconf, or manually by you.
+_Description: Manage tpconfig configuration file automatically?
+ Please choose whether the tpconfig configuration file
+ (/etc/default/tpconfig) should be handled automatically or manually.
Template: tpconfig/reset_p
Type: boolean
Default: false
_Description: Reset the touchpad when booting?
Some machines do not reset the touchpad hardware when they are booted
- and/or resumed. On these machines, it is necessary to manually reset the
- touchpad. Accept here to do a manual reset when the system is started or
- resumed. Refuse if you don't want this.
+ and/or resumed. On these machines, it is necessary to manually reset the
+ touchpad.
+ .
+ If you choose this option, a manual reset will be performed when the
+ system is started or resumed.
Template: tpconfig/options
Type: string
_Description: Options to pass to tpconfig when booting:
- Specify any command-line options you want passed to tpconfig at boot or
- resume time. (Note that if you specified above that the touchpad is to be
- reset, then it will be reset first, and then any options specified here
- done after.) For example, one common option is "--tapmode=0", which tells
- the touchpad to disable "tapping", to prevent spurious mouse events being
- caused by accidentally brushing against the touchpad.
+ Please specify any command-line options you want passed to tpconfig at
+ boot or resume time.
+ .
+ These options will be passed after the touchpad reset if you chose
+ that option.
+ .
+ A common option is '--tapmode=0' which is meant to disable 'tapping'
+ so that accidentally brushing the touchpad doesn't cause spurious mouse
+ events.
--- ../tpconfig.old/debian/control 2008-12-09 19:10:12.0 +
+++ debian/control 2008-12-09 19:13:56.0 +
@@ -10,7 +10,7 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Replaces: synaptics
-Description: configure touchpad devices
- This program can show or modify the configuration of several
- different kinds of touchpad devices, including the Synaptics
+Description: touchpad device configuration utility
+ This package provides a program that can show or modify the configuration of
+ various touchpad devices, including the Synaptics
TouchPad and the ALPS Glidepad/Stickpointer.
Template: tpconfig/overwrite-config-file
Type: boolean
Default: true
_Description: Manage tpconfig configuration file automatically?
Please choose whether the tpconfig configuration file
(/etc/default/tpconfig) should be handled automatically or manually.
Template: tpconfig/reset_p
Type: boolean
Default: false
_Description: Reset the touchpad when booting?
Some machines do not reset the touchpad hardware when they are booted
and/or resumed. On these machines, it is necessary to manually reset the
touchpad.
.
If you choose this option, a manual reset will be performed when the
system is started or resumed.
Template: tpconfig/options
Type: string
_Description: Options to pass to tpconfig when booting:
Please specify any command-line options you want passed to tpconfig at
boot or resume time.
.
These options will be passed after the touchpad reset if you chose
that option.
.
A common option is '--tapmode=0' which is meant to disable 'tapping'
so that accidentally brushing the touchpad doesn't caus
Re: [RFR] templates://mserv/{mserv.templates}
Christian Perrier wrote: > Your review should be sent as an answer to this mail. This isn't quite a complete review. > Template: mserv/mp3_location [...] > +_Description: Path to the root of the MP3 archive: > + Mserv needs to know where MP3 files are located so that it can index > + them. The files don't need to be arranged in any special way. Bare "MP3 files" here feels odd. We don't want to say "your" MP3 files, but how about "its" MP3 files? Hang on, though - what if (as in fact is the case) my music files aren't in MP3 format? The package description claims it supports Ogg Vorbis format too... and yes, my trial install (on Etch) shows up a variety of other annoyances, but since it supports music123 I'm not having any problem getting it to play WAV, Flac, Musepack, MP4 or Speex files either... _Description: Path to the root of mserv's music archive: Mserv needs to know where its music files are located so that it can index them. The files don't need to be arranged in any special way. > + If no MP3 files are available right now, just enter any directory. > + In that case, > + mserv will not be able to play music. To index new MP3 files in the > + future, you can > + run "dpkg-reconfigure mserv" to instruct the program about their location. Avoid the alternative interpretation of "enter [the] directory". And "instruct about" seems didactic, so say "inform of". If no music files are available right now, just enter any directory name. In that case, mserv will not be able to play music. To index new music files in the future, you can run "dpkg-reconfigure mserv" to inform the program of their location. > Template: mserv/path_invalid > Type: boolean > Default: false > -_Description: This path does not exist. Would you like to use it anyway? > +_Description: Use nonexisting directory anyway? "Nonexistent" or (rarer, but maybe justified here) "non-existing". Except that I got this error when it _did_ exist. Mserv does its scan as an unprivileged user - it should say something like: _Description: Really use unreadable location? Mserv cannot access the directory path you specified. Please choose whether you want to use that path anyway. > Template: mserv/confirm_update > +_Description: Really change the MP3 files archive location? s/MP3 files/music/g, simplifying the noun-pile. > Package: mserv [...] > Recommends: mpg321 | mpg123 | vorbis-tools | music123 | sox I'd suggest changing that to "mp3-decoder | music123 | sox", but I'll leave it as it is. > -Description: local centralised multiuser music server > - Mserv is a music server designed to do a number of things better than most > - systems designed to play mp3s or oggs: > +Description: centralised multiuser music server - server z > Standard form for multi-binary packages : one fix part and one > package-specific If we're doing "suite description - package role" we can avoid "server - server": Description: centralized multiuser music environment - server > + Mserv is a network music server with the following features: > > Less "advertisment-style". You don't know if it's better than others > and anyway, package descriptions are not meant for this..:-) Agreed, but you've dropped the qualifier "local" from the short description - I wouldn't suggest running it over the Internet. I'd also suggest that people might want it to turn up in searches on the word "jukebox". So bulking it back out a bit: Mserv is a local network jukebox server. It features: > + - Support for any type of client using a standard TCP protocol; What does this even mean? (Does it support SSH clients?) I can only imagine it's hinting at the fact (advertised in README.Debian) that you could connect to it from a MUD... > + - storage of information on MP3 (bitrate, duration, name, author, genre, > date > +produced, last play date) in an on-disk database; This has a better candidate lead noun, the "database". Not that it's quite what people normally mean when they refer to an "on-disk database" - it doesn't mean "stored in a .db file instead of in memory", it means "made of lots and lots of little text files, which you'll probably have to edit by hand". > + - rating information supplied by the user (awful, bad, neutral, > +good, superb); These go in the same "database" system, so merge the items: - text databases for track information (author, name, year, genre, last play date, duration) and user ratings (awful, bad, neutral, good, superb); (Ordering them as they appear in the file; no sign of "bitrate".) > + - queuing system (track, album, random album, etc); ^. > + - random play mode that uses users' ratings; Is there an easy way of avoiding "uses user"? How about: - random play mode taking users' ratings into account; > + - search facilities, status information, statisti
Re: [RFR] templates://mserv/{mserv.templates}
Justin B Rye wrote:
> This isn't quite a complete review.
Some other bits I missed:
> Package: mserv-cgi
> Architecture: all
> Depends: mserv-client, apache | httpd, ${perl:Depends}
Needs s/apache/apache2/ and presumably s/httpd/httpd-cgi/, or maybe
just removal from the archive.
> Package: mserv-dev
> Section: devel
> Architecture: any
> Depends: mserv-client (= ${binary:Version})
> Description: centralized multiuser music environment - development files
> Mserv is a network music server.
I forgot to update this one to "local network jukebox server".
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [RFR] templates://myphpmoney/{templates}
Christian Perrier wrote: > Your review should be sent as an answer to this mail. All the template changes look good (once amended), but: > +_Description: Web server to use with MyPhpMoney: > + MyPhpMoney currently only supports Apache-like web servers. There's only one Apache left in unstable now! Then again, this is an orphaned RC-buggy package with zero popcon votes... is there any likelihood that this will be sorted out? > +Description: finance manager > > Users don't care that it's written in PHP, indeed..:-) If they can't work it out, let them use debtags! > + MyPhpMoney includes 6 modules: > + - Count book (to enter operations and balance accounts); A vocabulary Frenglishism. I'd say "accounts book", but I think that's a Brenglishism! So... is it "cash book"? "Accounting book"? > + - Operation and recipient (to see a summary of operations, with the > +origin and the destination of the money) ; ^ You de-Frenglification missed one extra space: ^ -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [LCFC] templates://myphpmoney/{templates}
Christian Perrier wrote:
> This is the last call for comments for the review of debconf
> templates for myphpmoney.
On looking at this again I've noticed a couple of things in the
templates that I should have spotted the first time round.
> Template: myphpmoney/mysql_user
...
> _Description: MySQL database login name:
> Please enter the MySQL login name to use for accessing MyPhpMoney's
> database.
The "for accessing" is subtly awkward. How about:
Please enter the name of the MySQL account to be used for the MyPhpMoney
database.
> Template: myphpmoney/database_pass
...
> _Description: MySQL database password:
> Please enter the password for the MySQL login name that will be used to
> access MyPhpMoney's database. Leave this blank for not using a password.
Changing this mostly to keep it in line with the above:
Please enter the password of the MySQL account to be used for the
MyPhpMoney database. Leave this blank to use no password.
(A "null password" rather than a "locked account", right?)
> Template: myphpmoney/dbcreateerror
...
> _Description: MyPhpMoney database creation failure
> The MyPhpMoney installation program failed to properly set up a database.
> Please make sure all of parameters you supplied are correct and that
(missing article)
> the your database server software is running.
(excess article)
> Template: myphpmoney/postrm_remove_database
...
> _Description: Remove database after purging the myphpmoney package?
> Please choose whether MyPhPMoney's database should be removed when
Php
--
JBR
Ankh kak! (Ancient Egyptian blessing)
--- ../myphpmoney.old/debian/templates 2007-06-15 11:50:47.0 +0100
+++ debian/templates2007-07-02 02:26:01.0 +0100
@@ -2,83 +2,73 @@
Type: boolean
Default: false
_Description: Do you want to configure MyPhpMoney now?
- MyPhpMoney needs to be configured before its use, i.e. the MySQL database
- should be created and the Apache Web Server should be configured.
+ MyPhpMoney needs to be configured before its use: the MySQL database
+ should be created and the Apache web server should be configured.
.
- For that you will need the username and the password of your MySQL
- database administrator.
+ To achieve this, you will need to provide the login name and the
+ password of the MySQL database server administrator.
.
If you want to configure it later, you should run 'dpkg-reconfigure
myphpmoney'.
-Template: myphpmoney/webservers
-Type: multiselect
-Choices: ${webservers}
-Default: apache, apache-ssl, apache-perl, apache2
-_Description: Please select which Web Server you want to use for MyPhpMoney
- MyPhpMoney currently only supports Apache type Web Servers.
-
Template: myphpmoney/databasemgr_server
Type: string
Default: localhost
-_Description: What is the hostname where your database is running?
- If your database is on another machine besides the one that MyPhpMoney is
- running on then you need to change this value to the fully qualified
- domain name for that system. If you wish to access it locally, simply
- use "localhost" here.
+_Description: Database server host name:
+ The database for MyPhpMoney may be hosted on a remote server.
+ .
+ Please enter the fully qualified domain name for that system.
+ .
+ If the database is hosted locally, please enter 'localhost'.
Template: myphpmoney/database_name
Type: string
Default: myphpmoney
-_Description: What name do you want for your MyPhpMoney database?
- This is where all the MyPhpMoney data will be stored.
+_Description: MyPhpMoney database name:
+ Please enter the name of the database where MyPhpMoney data will be stored.
Template: myphpmoney/mysql_user
Type: string
Default: myphpmoney
-_Description: What is your MySQL database username?
- What username will access the MySQL database for MyPhpMoney? This user
- will be created if it doesn't already exist. Note that your database
- manager must be configured to allow password authentication or MyPhpMoney
- will not work.
+_Description: MySQL database login name:
+ Please enter the name of the MySQL account to be used for the MyPhpMoney
+ database.
+ .
+ It will be created if it doesn't already exist.
+ .
+ Please note that the database server software must be configured to allow
+ password authentication.
Template: myphpmoney/database_pass
Type: password
-_Description: What is the password you wish to use for the database user?
- Enter a password for the database user (leave blank for no password). This
- is the password that will be used along with the database user name you
- have already supplied to connect to the database.
+_Description: MySQL database password:
+ Please enter the password of the MySQL account to be used for the
+ MyPhpMoney database. Leave this blank to use no password.
Template: myphpmoney/mysql_dbadmin
Type: string
Default: root
-_Description: Enter the username of your MySQL database administrator.
- This is the d
Re: [ITR] templates://htdig/{templates}
Christian Perrier wrote: > The first step of the process is to review the debconf source > template file(s) of htdig. This review will start on Friday, December 21, > 2007, or > as soon as you acknowledge this mail with an agreement for us to > carry out this process. I'll be away from keyboard for the next week, so I'll share my rough notes in advance. The package description needs quite a lot of rephrasing. For a start, its short description: -Description: WWW search system for an intranet or small internet ht://Dig is precisely not a World Wide Web search engine - it's a local website search engine. And what's a "small internet"? +Description: web search engine for intranets - The ht://Dig system is a complete World Wide Web indexing and searching + The ht://Dig system is a complete web indexing and searching system for a small domain or intranet. This system is not meant to replace the need for powerful internet-wide search systems like Lycos, (Dated - these days Lycos is a portal rather than a search engine) Google, or Yahoo!. Instead it is meant to cover the search needs of a single company, campus, or even a particular subsection of a website. . As opposed to some WAIS-based or web-server based search engines, ht://Dig isn't opposed to WAIS, and "-based" is just fog as usual. I'd boil it down to "Unlike some WAIS or web search engines" - but then I wonder about the claim it's leading into: ht://Dig can span several web servers at a site. The type of these different web servers doesn't matter as long as they understand the HTTP 1.0 protocol. Does ht://Dig really have rivals that can only index one server? Are there web servers that still don't support HTTP 1.0? Perhaps these "features" should be retired into the bulleted feature-list. The list's bullet syle should be standardised, but I'll take that part for granted. -* Intranet searching -* It is free -* Full source code included -* Full support for the ISO-Latin-1 character set Cut these non-features (what's htdig doing with ja.po and ru.po files etcetera if it can't even handle š or €?). Perhaps replace them with: + - indexing of any number of unrelated web servers; Standardising on noun phrases: -* Robot exclusion is supported + - robot exclusion support; -* Keywords can be added to HTML documents + - keyword tagging of HTML documents; -* A Protected server can be indexed + - indexing of protected servers; -* The depth of the search can be limited + - configurable-depth searches; Then the trailing caveat: - Please note that ht://Dig is a resource-hog, with respect to processor usage, - when indexing. - . - Disk space requirements: - . - 13.000 documents indexed: 150MB disk space with a 'wordlist database' -93MB disk space without a 'wordlist' The first half is subtly bad en_US; the second half has a blatantly wrong $LC_NUMERIC! + Please note that ht://Dig indexing is processor-intensive; and its disk + space requirements are approximately 12kB per document indexed (so e.g. + 13,000 documents indexed = 150MB with a wordlist database, 93MB without). -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Re: [RFR] templates://htdig/{templates}
Christian Perrier wrote:
> Your review should be sent as an answer to this mail.
> -Description: WWW search system for an intranet or small internet
> +Description: web search and indexation system - binaries
Annoyingly, "indexation" exists only as a technical term in
accounting. And the indexing has to happen first. So:
Description: web indexing and searching system - binaries
> The ht://Dig system is a complete World Wide Web indexing and searching
^^
Take out the misleading WW part. But that means it's repeating "web
search and indexing system" in both synopsis and long description
("system" in particular occurs far too often); one or the other
should perhaps say "web search engine".
> system for a small domain or intranet. This system is not meant to
> + replace the need for powerful internet-wide search systems.
Come to think of it, we wouldn't want to "replace the need" for
Google (we would satisfy the need by replacing Google). Say:
The ht://Dig system is a complete web search engine for a small domain
or intranet. It is not meant to replace the major Internet-wide search
engines; instead it is meant [...]
(It's strangely hard to phrase this without giving an example!)
> + The ht://Dig search engine can span several web servers at a site.
>
> We're in the 21st century, now..:-)
Even further, today. But I'd merge this into the first Feature:
- intranet searching, spanning multiple local web servers;
> -* Keywords can be added to HTML documents
> + - HTML documents keywords support;
That doesn't quite work, and it's a bit obscure anyway. It's
talking about and other
specially added tags. I was thinking:
- keyword tagging of HTML documents;
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- ../htdig.old/debian/templates 2007-12-18 08:53:28.0 +
+++ debian/templates2008-01-01 16:05:32.0 +
@@ -1,22 +1,22 @@
Template: htdig/generate-databases
Type: boolean
Default: true
-_Description: Generate endings database now?
+_Description: Generate ht://Dig endings database now?
The ht://Dig search engine requires an endings database which has to be
generated before the first start. Generating the database will take a
short while. It can be done either now or later by calling the
- '/usr/sbin/htdigconfig' script. Should the database be generated now
- rather than later on?
+ '/usr/sbin/htdigconfig' script.
Template: htdig/run-rundig
Type: boolean
Default: false
-_Description: Execute the rundig script daily?
- rundig is a program that obtains on-line content and creates a searchable
- database for the ht://Dig search engine. It downloads and indexes HTML
- from the web, as defined in /etc/htdig/htdig.conf. Say Yes if you wish to
- run this program daily. Say No if you don't plan to use htdig in this
- way (perhaps htdig is being used by a third party, for instance KDE, to
- perform local indexing). If in doubt, say No. It is the safest choice
- unless you know what you're doing.
+_Description: Schedule a daily execution of the 'rundig' script?
+ On-line content must be indexed by the 'rundig' script before
+ ht://Dig can be used to search data. That script indexes the
+ web content defined in /etc/htdig/htdig.conf.
+ .
+ If you choose this option, a daily run of the script will be scheduled.
+ You may choose to not use this option if ht://Dig is used another
+ way (for instance by KDE, to
+ perform local indexing). If in doubt, do not choose this option.
--- ../htdig.old/debian/control 2007-12-18 08:53:28.0 +
+++ debian/control 2008-01-01 16:14:58.0 +
@@ -10,55 +10,35 @@
Depends: ${shlibs:Depends}, perl, lockfile-progs, debconf (>= 1.2.9) |
debconf-2.0
Suggests: htdig-doc, wwwoffle | httpd
Conflicts: libmifluz0
-Description: WWW search system for an intranet or small internet
- The ht://Dig system is a complete World Wide Web indexing and searching
- system for a small domain or intranet. This system is not meant to
- replace the need for powerful internet-wide search systems like Lycos,
- Google, or Yahoo!. Instead it is meant to cover the search needs of a
- single company, campus, or even a particular subsection of a website.
- .
- As opposed to some WAIS-based or web-server based search engines,
- ht://Dig can span several web servers at a site. The type of these
- different web servers doesn't matter as long as they understand the
- HTTP 1.0 protocol.
+Description: web indexing and searching system - binaries
+ The ht://Dig system is a complete web search engine for a small domain
+ or intranet. It is not meant to replace the major Internet-wide search
+ engines; instead it is meant to cover the search needs of a single
+ company, campus, or even a particular subsection of a website.
.
Features:
-* Intranet searching
-* It
Re: [LCFC] templates://htdig/{templates}
Christian Perrier wrote: > This is the last call for comments for the review of debconf > templates for htdig. One search-and-replace: > Package: htdig [...] > Features: > - intranet searching, spanning multiple local web servers; > - robot exclusion; > - boolean expression searches; > - configurable search results; > - fuzzy searching (various algorithms supported); > - indexation of HTML and text files; ^ > - keyword tagging of HTML documents; > - email notification of expired documents; > - indexation of protected servers; ^ Indexation is when salaries are pegged against cost-of-living figures; s/indexation/indexing/. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#701604: gkermit: cobwebby package description
Package: gkermit
Version: 1.0-10
Followup-For: Bug #701604
This bug should probably be merged with 732938.
> The package description for gkermit needs some routine maintenance.
This is gradually rising from the level of "routine", but not enough
to change the severity quite yet.
>> [...] The non-free package ckermit adds connection
>> establishment, character-set translation and scripting features.
ckermit no longer even exists in stable/testing/unstable, so there's
no point comparing the two in this package description; my patch needs
a rewrite.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- control.pristine 2019-07-12 14:40:37.618636024 +0100
+++ control 2019-07-12 14:44:24.596388439 +0100
@@ -8,7 +8,6 @@
Package: gkermit
Architecture: any
Depends: ${shlibs:Depends}
-Description: A serial and network communications package
- G-Kermit is a GPL'd kermit package. It offers medium-independent terminal
- session and file transfer. The non-free package ckermit adds connection
- establishment, character-set translation and scripting features.
+Description: GNU Kermit file transfer program
+ G-Kermit can serve as an endpoint for the Kermit protocol, supporting
+ text and binary file transfers on 7- and 8-bit serial connections.
Bug#232848: arpd: contains mystery file
Package: arpd
Version: 1.0.2-9.2
Severity: minor
I'm not actually using this package, but I noticed
("http://packages.debian.org/cgi-bin/search_contents.pl?searchmode=filelist&word=arpd&version=testing";)
that the testing/unstable edition contains a lost-looking file:
".so." - a hidden symlink to itelf in the root directory.
I don't think that's meant to be there.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux xan 2.6.2 #1 Wed Feb 11 22:30:29 GMT 2004 i586
Locale: LANG=en_GB, LC_CTYPE=en_GB
Versions of packages arpd depends on:
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
-- no debconf information
--
JBR
Ankh kak! (Ancient Egyptian blessing)
