gs-3.33 + gsfonts
Please blame me for all of this, and not the archive maintainer, but if you try to install gs-3.33 from the unstable tree, (the GNU version of gs), you'll notice it depends on gsfonts-4.01. Next you'll notice, gsfonts is in non-free and you cannot install it (as you're a pure-gnu). Fortunately, the location of gsfonts is incorrect, and you can safely download, sell, modify, whatever, gsfonts-4.01-2 from non-free, as it's GPL! I've already sent an email to Guy asking him to move gsfonts-4.01-2 from non-free to unstable/text. Thanks for your attention (and for the bug-reports those of you who didn't read this are going to send), -- joost witteveen [EMAIL PROTECTED] [EMAIL PROTECTED] -- Use Debian/GNU Linux!
Re: Bug#4339: no free pine package available
On Thu, 29 Aug 1996, Marek Michalkiewicz wrote: Package: ftp.debian.org The current version of pine is in non-free because the copyright is not clear. We really should talk to the maintainers - perhaps we can get permission to distribute the package as part of the distribution? (FYI, it's in Red Hat, and those guys are quite careful about copyrights, too...) The copyright is quite clear. You can not distribute this package for a fee without first getting permission from the pine developers. According to our policy this requires it go into non-free. We have talked with the developers about changing this. In the next version they changed the wording but the intent remained the same. I will be working on the new release (when I can find some time) and I will check the copyright again to see if things have improved. Even if we don't get permission (say, Red Hat paid them lots of $$$ to get a license), I think we should still distribute an older version (before the copyright change - I think it was 3.92) in the regular distribution (just like we do with ghostscript). Are there any problems with this? The older version has some substantial bugs that have been fixed in later releases. It is my understanding that we do not distribute buggy software when the fix is available. The ghostscript example is, I think, a temporary solution while a new release is awaited. Unless someone with more authority than myself agrees with you, I am disinclined to re-release the old version. Barring further instructions from that direction, I will close this bug report. Luck, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Bug#4190: Bug4190: serious security hole in libc (resolver)
This is why I really wish H.J. Lu would make pure, bug-fix only releases for the current, stable libcs. Yes, I know Debian isn't using the latest, stable libc, but this paritcular bug isn't fixed in the current beta version either. Marek Michalkiewicz writes: I think there are two possible ways to fix it: (1) ignore the dangerous environment variables completely (is anyone actually using them? I heard about them for the first time from the security alert...). If anyone needs these features - create a separate full-featured resolver library people can use (for non-setuid programs only) by setting LD_PRELOAD. Supposedly, the NSS support in libc 6 has a much better way of handling things like this. (2) ignore them if (geteuid() != getuid() || getegid() != getgid()). Problem: you can pass them to login via telnetd, so telnetd needs to be fixed too. Anyway, I think telnetd should do what the one in NetKit-0.08 does: allow only a few (known to be safe) environment variables, and don't allow the rest. Right now, we check for a few variables known to be dangerous - and we can't be sure that there are no more. The bash man page mentions BASH_ENV in one place, and it's not checked by telnetd. About the best I can do, without further guidance, is make libc not echo the problem lines to stderr. Is that acceptable? David -- David EngelOptical Data Systems, Inc. [EMAIL PROTECTED] 1101 E. Arapaho Road (214) 234-6400 Richardson, TX 75081
Bug#4339: no free pine package available
Dale Scheetz wrote: The copyright is quite clear. You can not distribute this package for a fee without first getting permission from the pine developers. According to our policy this requires it go into non-free. Now I noticed that the copyright has changed, the new one (same in version 3.94 and 3.95; the new Red Hat beta contains 3.95) looks better to me. It says: | Redistribution of this release is permitted as follows, or by mutual | agreement: [...] | (c) Inclusion in a CD-ROM collection of free-of-charge, shareware, or | non-proprietary software for which a fee may be charged for the | packaged distribution. Isn't this good enough? It sounds clear to me, but then I'm not a lawyer... If not - have you tried to ask them for individual permission similar to that in the procmail package? Here is it: | The copyright statement below is addended for the Debian system: |This program may be sold as a component of the Debian Linux |distribution or a Linux distribution derived from the Debian |Linux distribution. If it is distributed in binary form, the |source code must be included in the distribution as well. | End of addendum. (procmail would be non-free without this - the original copyright says that it may not be sold). The older version has some substantial bugs that have been fixed in later releases. It is my understanding that we do not distribute buggy software I see. The fix is available - but is non-free. I can see that you may not like to do the extra work of maintaining two versions of the same package, but perhaps we can just say that the older version is completely unsupported? I hope someone still has a copy of the old package, which could be put in contrib. Buggy software might sometimes be better than no software at all... I rarely use pine myself (usually only when I have to read some MIME-encrypted mail :-), but I know it's quite popular. It would be a pity if we can't ship a MIME-aware mailer with the standard distribution. Marek
Bug#4343: ssh binaries are not stripped
Package: ssh Version: 1.2.14-1 The binaries in this package are not stripped, and they should according to the packaging guidelines. Marek
new maintainer for wu-ftpd wanted
Hi, I'm searching for a new maintainer for the wu-ftpd package. You should be able to program in perl (addftpuser is written in perl). Thanks, Peter -- Peter TobiasEMail: Fachhochschule Ostfriesland [EMAIL PROTECTED] Fachbereich Elektrotechnik und Informatik [EMAIL PROTECTED] Constantiaplatz 4, 26723 Emden, Germany [EMAIL PROTECTED]
Bug#4334: squid should not run as root by default
You (Marek Michalkiewicz) wrote: Package: squid Version: 1.0.beta16-1 In the default configuration, squid runs as root. While it can be changed in the config file, someone might forget to configure it after installation, so I think the default should be secure. The permissions/ownerships in /var/squid and /var/log/squid should be changed accordingly. I think squid should ideally run under its own allocated UID/GID. Was fixed in 1.0.9 (uploaded to master a couple of days ago). 1.0.10 is underway. It runs as proxy/proxy. Mike. -- Miquel van | Cistron Internet Services --Alphen aan den Rijn. Smoorenburg,| mailto:[EMAIL PROTECTED] http://www.cistron.nl/ [EMAIL PROTECTED] | Tel: +31-172-419445 (Voice) 430979 (Fax) 442580 (Data)
Bug#4190: serious security hole in libc (resolver)
David Engel wrote:
About the best I can do, without further guidance, is make libc not
echo the problem lines to stderr. Is that acceptable?
I'm not sure. Someone could still read special files as root
(they would not see the contents, but merely reading them might
sometimes cause troubles too, if reading changes the state of
the device - as is the case with tapes, for example).
My suggestion (not tested, but it is rather simple) - replace
all occurrences of getenv() in the resolver with safe_getenv(),
implemented like this:
char *
safe_getenv(const char *name)
{
if (geteuid() != getuid() || getegid() != getgid())
return NULL;
return getenv(name);
}
This assumes that telnetd will only pass known safe environment
variables to login, as suggested in another bug report against
netstd (I just got a response that the next netstd will be OK).
In the more paranoid version, safe_getenv() could simply always
return NULL. Not all of the environment variables used by the
resolver might be dangerous - but I think it is better to err on
the safe side here...
Marek
Bug#4339: no free pine package available
On Thu, 29 Aug 1996, Marek Michalkiewicz wrote: The current version of pine is in non-free because the copyright is not clear. The onus rests on the pine maintainer, not me, so I'm reassigning this to pine. Guy
Bug#4344: trn should provide news-reader
Package: trn Version: 3.6-5 trn should provide the virutal package `news-reader'. -- Shields, CrossLink.
Bug#4331: linux-security] [linux-alert] SECURITY FIX/UPDATE: anonftp (fwd)
AFAIK it is along the line wit site exec tar cvzf -rsh-command blafasel host:tar.tgz Probably something else - I don't believe Red Hat would have that nice old _PATH_EXECPATH bug for so long :-). It might be related to the feature that wu-ftpd can send you a tar of a directory if you do get directory.tar. Still I'm not sure how it could be exploited though. Elliot? Marek
Re: Do we ever retire packages?
On 29 Aug 1996, Kai Henningsen wrote: So, I'd propose a new directory, parallel to contrib and non-free. We could call it dropped or orphaned and include a README saying that these are packages that are no longer supported by the Debian project in any way, and are not recommended, but if you want them, here they are. contrib is an appropriate location for orphaned software. Guy
Bug#4339: no free pine package available
I rarely use pine myself (usually only when I have to read some MIME-encrypted mail :-), but I know it's quite popular. It would be a pity if we can't ship a MIME-aware mailer with the standard distribution. How odd... I seem to have a /usr/bin/exmh, and exmh isn't in my /usr/local/bin. I consider exmh to be the most MIME-aware mailer I've had the pleasure to use. If it isn't in my /usr/local/bin, ., ~/bin, or /usr/local/openwin.bin, but I'm using it on my system, then it must be part of the Debian distribution, or my system is really messed up... Exmh is an optional package in the mail section. According to dselect, it depends on tk41, tcl75, mh, and metamail. Metamail is a general package to handle MIME types unknown to your mailer. Most of the mailers out there (including pine) use metamail transparantly. However, exmh is very MIME-aware on its own. It will automatically display enriched-text correctly, handle multipart MIME messages well (both multipart/mixed and multipart/alternative), and integrates well with PGP. Marek -- Buddha Buck [EMAIL PROTECTED] Just as the strength of the Internet is chaos, so the strength of our liberty depends upon the chaos and cacaphony of the unfettered speech the First Amendment protects. -- A.L.A. v. U.S. Dept. of Justice
metamail_2.7-8
-BEGIN PGP SIGNED MESSAGE- Format: 1.5 Date: Thu, 29 Aug 1996 17:11:43 +0200 Source: metamail Binary: metamail Architecture: source i386 Version: 2.7-8 Distribution: unstable Urgency: low Maintainer: Michael Meskes [EMAIL PROTECTED] Description: metamail - An implementation of MIME. Changes: metamail (2.7-8) unstable; urgency=LOW . * Corrected postinst Files: f465edef358649b0933bd1ab7ed84434 604 mail optional metamail_2.7-8.dsc 822607a7d160d93aee614ee5edd0678b 16963 mail optional metamail_2.7-8.diff.gz 31ded5f3dcfde8571ee69a61b434ff72 147244 mail optional metamail_2.7-8_i386.deb 3401751ef93bd141f0179d3ad5b2f0a6 156075 mail optional metamail_2.7.orig.tar.gz -BEGIN PGP SIGNATURE- Version: 2.6.2i iQCVAwUBMiW31SpaNcQEtuj1AQGztwQAtpiMmPvpgKQBGb4+gPbFfiKdI4kIgUJ7 JoVaazQUwywcODKKpgyKRxerDtCSGTMTvV46/xC7NtyT14uqElwIMKc1g2Q6gs+Q mID684v3NnoipH+HQZChVfmkUeT7u0Jp1wXZzdF7bnquN5O1l5ggUAE0xlNy3NeB +QvcgaN/Kh8= =py+a -END PGP SIGNATURE- -- Michael Meskes |_ __ [EMAIL PROTECTED] | / ___// / // / / __ \___ __ [EMAIL PROTECTED] | \__ \/ /_ / // /_/ /_/ / _ \/ ___/ ___/ [EMAIL PROTECTED]| ___/ / __/ /__ __/\__, / __/ / (__ ) Use Debian Linux!| //_/ /_/ //\___/_/ //
sudo_1.5-1
Now that I finished this version, Bdale take over sudo. -BEGIN PGP SIGNED MESSAGE- Format: 1.5 Date: Thu, 29 Aug 1996 11:44:22 +0200 Source: sudo Binary: sudo Architecture: source i386 Version: 1.5-1 Distribution: unstable Urgency: low Maintainer: Bdale Garbee [EMAIL PROTECTED] Description: sudo - Provides limited super user privileges to specific users. Changes: sudo (1.5-1) unstable; urgency=LOW . * New upstream version * New maintainer * New packaging format Files: 965a9072f8d28519b650b59eae9a84da 582 admin optional sudo_1.5-1.dsc 809460190aea106c42eea3902a430849 171962 admin optional sudo_1.5.orig.tar.gz 6ebdde4a6d2b1f8fe0ceb5c47f4fb73a 10717 admin optional sudo_1.5-1.diff.gz 6a3ac478cd69e71796ae4e4649509b2a 56588 admin optional sudo_1.5-1_i386.deb -BEGIN PGP SIGNATURE- Version: 2.6.2i iQCVAwUBMial4ipaNcQEtuj1AQHD1AQA3w/0BcJf+xVbPy5TAQjeLEhScFRxKC4K VeeZlqnrBnfIz6h68Y22RtdKonNR5el7LaXcXatqZe+ygLeXRtIPo2RgcQ+IXsL5 4C7iuqsG/YvE8p0pvFTeA6qut547z4MY6FqrWy2Nc+0nPTBtkmSVa2wxLABATiv9 C11cDiP6QUY= =VKND -END PGP SIGNATURE- -- Michael Meskes |_ __ [EMAIL PROTECTED] | / ___// / // / / __ \___ __ [EMAIL PROTECTED] | \__ \/ /_ / // /_/ /_/ / _ \/ ___/ ___/ [EMAIL PROTECTED]| ___/ / __/ /__ __/\__, / __/ / (__ ) Use Debian Linux!| //_/ /_/ //\___/_/ //
metamail_2.7-8 corrected
Just in case someone checks the md5sums in this announcement here's the correct one: -BEGIN PGP SIGNED MESSAGE- Format: 1.5 Date: Thu, 29 Aug 1996 17:11:43 +0200 Source: metamail Binary: metamail Architecture: source i386 Version: 2.7-8 Distribution: unstable Urgency: low Maintainer: Michael Meskes [EMAIL PROTECTED] Description: metamail - An implementation of MIME. Changes: metamail (2.7-8) unstable; urgency=LOW . * Corrected font name in postinst * Corrected rules file to not install /usr/doc/copyright/README Files: 37fdef4f6625e4b0156b16055cec185b 604 mail optional metamail_2.7-8.dsc cd831615e058b1a0cc3bf0e787a46e46 17029 mail optional metamail_2.7-8.diff.gz 89cc67e3e83a628635b2995ec3b2fa72 147294 mail optional metamail_2.7-8_i386.deb 9ea5de89000246aba400092b6fe4c67f 156075 mail optional metamail_2.7.orig.tar.gz -BEGIN PGP SIGNATURE- Version: 2.6.2i iQCVAwUBMiam3ypaNcQEtuj1AQEtDgP+IYfrw1WbL51PE2GIFtWNliRm8g4UYNtE O9SPTkRbNYN1zvzIh/RYHbrpW+CQgSuueYYTHeIfw6Z8YjeAZRPfw730yxdktxBB 31MRxEF760qT+xqCXVTetRIDZ+hOhHbVAq/Utgc7T3f2nAMX0fJmMdqwexP/lwRS DSPOI1xm2mA= =S7zT -END PGP SIGNATURE- -- Michael Meskes |_ __ [EMAIL PROTECTED] | / ___// / // / / __ \___ __ [EMAIL PROTECTED] | \__ \/ /_ / // /_/ /_/ / _ \/ ___/ ___/ [EMAIL PROTECTED]| ___/ / __/ /__ __/\__, / __/ / (__ ) Use Debian Linux!| //_/ /_/ //\___/_/ //
Re: dpkg-buildpackage and -source questions
If you get this message: dpkg-source: error: tarfile `./exmh_1.6.9.orig.tar.gz' contains object with newline in its name (exmh-1.6.9.orig/?exmh-1.6.9.orig/exmh.README?exmh-1.6.9.orig/COPYRIGHT?exmh-1.6.9.orig/e...(rest of output deleted) You should upgrade your cpio. Unfortunately the (Debian-specific) change that I'm relying on wasn't documented in any changelog file, so I don't know which versions are OK, but I do know that 2.4.2-2 works. If someone has a version of cpio between 2.3-2 (which I know doesn't work) and 2.4.2-2 I'd be grateful if they'd do one of the following two tests: * Try to unpack a source package with it using dpkg-source or * Type `cpio -Hustar -0t anything.tar | cat -vet' and see whether the output from cpio is null-terminated or newline-terminated. I'll be making some changes to dpkg-source and the dpkg control file. Thanks, Ian.
Bug#4346: Essential LaTeX style files missing
Package: ltxmisc Version: 1.0-1 In 1.1.7, Debian's TeX is unusable for somebody who wants to do serious work with it, at least for me (I work in German). Hardly any of the often - used packages is there (this starts with a4.sty, which is required by the documentation of german.sty, missing). The best way would probably be to go through the LaTeX Companion and install everything that's mentioned in there. -- Thomas Koenig, [EMAIL PROTECTED], [EMAIL PROTECTED] The joy of engineering is to find a straight line on a double logarithmic diagram.
Re: New virtual package names.
On 30 Aug 1996, Mark Eichin wrote: Emacs also has conditions where it calls an outside editor... Interesting. I'm aware of cases where it will call outside *viewers* (mostly mime/web stuff) but I can't think of what outside editors it would call. Could you perhaps expand on this point? I am a novice when it comes to emacs. My impression came from a bug report on pine about pico leaving backup copies of email that are world readable. It turned out that the emacs mail handler was calling pico with the auto-backup enabled. This is what left me with that impression. (I was sure that someone less ignorant than myself would surely correct me if I was wrong) Luck, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Bug#4347: emacs html-mode + font-lock highlights too greedily
Package: emacs Version: 19.31-2 I have the following line in an HTML document: bdeny_sender/b in the brestrict.options/b file and the email However when font-lock mode is turned on, everything from deny_sender to restrict.options is highlighted, whereas the right to do is to only highlight the contents of the b.../b pairs. -- Richard Kettlewell [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.elmail.co.uk/staff/richard/
Bug#4346: Essential LaTeX style files missing
Thomas Package: ltxmisc Thomas Version: 1.0-1 Thomas Thomas In 1.1.7, Debian's TeX is unusable for somebody who wants to do Thomas serious work with it, at least for me (I work in German). Hardly Thomas any of the often - used packages is there (this starts with a4.sty, Thomas which is required by the documentation of german.sty, missing). Thomas Thomas The best way would probably be to go through the LaTeX Companion Thomas and install everything that's mentioned in there. That option was once discussed informally between Nils, Erick and myself. We never did this because - it would be overkill, there are too many style files mentioned in the Companion, and some of them change or get replaced by the bi-annual LaTeX release - if you were to start from Karl Berry's sources, you wouldn't get it either, what Debian delivers is a standard base TeX. And Debian is after all an open system. Everybody could package, say, latex-goodies. I just put these things into /usr/local/lib/texmf/tex/latex// As for a4, I much prefer vmargin (which the LaTeX Companion has as vpage, described on page 89). -- Dirk Eddelbuttel http://qed.econ.queensu.ca/~edd
Bug#4348: smartlist.postinst fails
Package: smartlist
Status: install ok half-configured
Priority: optional
Section: mail
Maintainer: Christoph Lameter [EMAIL PROTECTED]
Version: 3.10-1
Depends: smail | sendmail | mail-transport-agent, procmail, libc5 (= 5.2.18-1)
Description: Versatile and Fast List Processor
-- Clip here for transcript --
Setting up smartlist (3.10-1) ...
hostname: illegal option -- q
Usage: hostname [-v] {hostname|-F file} set host name (from file)
domainname [-v] {nisdomain|-F file} set NIS domain name (from file)
hostname [-v] [-d|-f|-s|-a|-i|-y] display formated name
hostname [-v] display host name
hostname -V|--version|-h|--help print info and exit
dnsdomainname=hostname -d, {yp,nis,}domainname=hostname -y
-s, --short short host name
-a, --alias alias names
-i, --ip-address addresses for the host name
-f, --fqdn, --longlong host name (FQDN)
-d, --domain DNS domain name
-y, --yp, --nis NIS/YP domain name
-F, --fileread host name or NIS domain name from given File
This comand can get or set the host name or the NIS domain name. You can
also get the DNS domain or the FQDN (fully qualified domain name).
Unless you are using bind or NIS for host lookups you can change the
FQDN (Fully Qualified Domain Name) and the DNS domain name (which is
part of the FQDN) in the /etc/hosts file.
/var/lib/dpkg/info/smartlist.postinst: newaliases: command not found
dpkg: error processing smartlist (--configure):
subprocess post-installation script returned error exit status 127
Errors were encountered while processing:
smartlist
dpkg --configure returned error exit status 1.
Bug#4348: smartlist.postinst fails
Dont know what kind of hostname tool you got installed on your machine.
It works on my Debian 1.1 system.
On Fri, 30 Aug 1996, Douglas Bates wrote:
batesPackage: smartlist
batesStatus: install ok half-configured
batesPriority: optional
batesSection: mail
batesMaintainer: Christoph Lameter [EMAIL PROTECTED]
batesVersion: 3.10-1
batesDepends: smail | sendmail | mail-transport-agent, procmail, libc5 (=
5.2.18-1)
batesDescription: Versatile and Fast List Processor
bates
bates-- Clip here for transcript --
batesSetting up smartlist (3.10-1) ...
bateshostname: illegal option -- q
batesUsage: hostname [-v] {hostname|-F file} set host name (from file)
bates domainname [-v] {nisdomain|-F file} set NIS domain name (from file)
bates hostname [-v] [-d|-f|-s|-a|-i|-y] display formated name
bates hostname [-v] display host name
bates hostname -V|--version|-h|--help print info and exit
batesdnsdomainname=hostname -d, {yp,nis,}domainname=hostname -y
bates-s, --short short host name
bates-a, --alias alias names
bates-i, --ip-address addresses for the host name
bates-f, --fqdn, --longlong host name (FQDN)
bates-d, --domain DNS domain name
bates-y, --yp, --nis NIS/YP domain name
bates-F, --fileread host name or NIS domain name from given
File
bates This comand can get or set the host name or the NIS domain name. You
can
bates also get the DNS domain or the FQDN (fully qualified domain name).
bates Unless you are using bind or NIS for host lookups you can change the
bates FQDN (Fully Qualified Domain Name) and the DNS domain name (which is
bates part of the FQDN) in the /etc/hosts file.
bates/var/lib/dpkg/info/smartlist.postinst: newaliases: command not found
batesdpkg: error processing smartlist (--configure):
bates subprocess post-installation script returned error exit status 127
batesErrors were encountered while processing:
bates smartlist
batesdpkg --configure returned error exit status 1.
bates
{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}
{}Snail Mail: FTS Box 466, 135 N.Oakland Ave, Pasadena, CA 91182{}
{}FISH Internet System Administrator at Fuller Theological Seminary {}
{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}
PGP Public Key = FB 9B 31 21 04 1E 3A 33 C7 62 2F C0 CD 81 CA B5
Re: dpkg-buildpackage and -source questions
On Fri, 30 Aug 1996, Ian Jackson wrote: If you get this message: dpkg-source: error: tarfile `./exmh_1.6.9.orig.tar.gz' contains object with newline in its name (exmh-1.6.9.orig/?exmh-1.6.9.orig/exmh.README?exmh-1.6.9.orig/COPYRIGHT?exmh-1.6.9.orig/e...(rest of output deleted) You should upgrade your cpio. Unfortunately the (Debian-specific) change that I'm relying on wasn't documented in any changelog file, so I don't know which versions are OK, but I do know that 2.4.2-2 works. This resolved the problem for me. At least at this point I can unpack hello ok. Shouldn't dpkg have a depends added for this? I have not understood your reluctance to add depends for patch and diff as well. If they really aren't dependencies, souldn't they be recommended or suggested? If not there should, at least be some mention of their usefulness in the description somewhere. Thanks for the help, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Bug#4349: dpkg-source has misleading warning message
Package: dpkg Version: 1.3.9 sfere:~$ dpkg-source -b procmeter-2.0 procmeter-2.0.orig.tar.gz dpkg-source: warning: .orig.tar.gz name procmeter-2.0.orig.tar.gz is not package-upstreamversion.orig.tar.gz (wanted procmeter_2.0.orig.tar.gz) This should read `... is not package_upstreamversion.orig.tar.gz ...' (S)
Re: CC's on this mailing list
'Lars Wirzenius wrote:' Spam does make furious, extra Cc's from mailing lists don't. They just annoy me (see signature), and in theory they do cost me a bit. Not enough to make me worry about it, but enough to write kilobyte after kilobyte about it. I do wish that people wouldn't Cc me when I read the mailing list. I feel that it is good netiquette not to do that. I like the CCs because lately I haven't been able to keep up with the list and knowing that someone responded to something (which shows up in my mailbox and not the procmail filter) is useful. This may be a mark that we or I don't think there is enough real problems with Debian. Hm, perhaps the three month release schedule is one: we have one month left for the next release, and we're just about to make a big change in source packaging? Perhaps it would be better to wait an extra month for this occasion only? I don't think we have a good mechanism for code cleanups before a major release. Instead, I think that sticking with stable releases from upstream is the way to keep Debian stable. I like the three month schedule, but feel it is mostly independent of maintainer issues. Though perhaps we should save the source package changes for the release after next month's? -- Christopher J. Fearnley|Linux/Internet Consulting [EMAIL PROTECTED], [EMAIL PROTECTED] |UNIX SIG Leader at PACS http://www.netaxs.com/~cjf |(Philadelphia Area Computer Society) ftp://ftp.netaxs.com/people/cjf|Design Science Revolutionary Dare to be Naive -- Bucky Fuller |Explorer in Universe
uploading gs-4.01-4
-BEGIN PGP SIGNED MESSAGE- Date: 29 Aug 96 21:19 UT Format: 1.6 Distribution: unstable Urgency: Low Maintainer: joost witteveen [EMAIL PROTECTED] Source: gs Version: 4.01-4 Binary: gs Architecture: i386 source Description: gs: Postscript interpreter with X11 and svgalib preview support. Changes: * bjd paches from Yves Arrouye. (sorry Yves, I forgot to include them in gs_4.01-3). Files: 314a54bfe56ef2ba7461c51fc829f5e5 2186266 non-free - gs_4.01-4.tar.gz 37b4db5b1b3e1d85fc351a82d51a3572 30402 non-free - gs_4.01-4.diff.gz 33827c08f5e09c73f608e25e51c1a4ed 1079338 non-free Optional gs_4.01-4_i386.deb -BEGIN PGP SIGNATURE- Version: 2.6.2i iQCVAwUBMiYJ2JNVaG8BiEBRAQHt6gP+Ng3OsgFNvx5TyIrbMgiwXr2VVLPGvp9s KzRwNXgYuPCuqiaKPZXlX5FdsRjz5pweyaujYttp4+zqp/FYr96qSDPIgP3XMX8D bbM2fsJyyypxswKOwWjeui2siRJZdqurtqcmv1b2gWGJn5P+0Z2yAGbowodNZGA+ yMak6au6uK0= =pnv2 -END PGP SIGNATURE-
Bug#4342: pgp command : add '+clearsig=on'
Package: dpkg Version: 1.3.10 you should add +clearsig to the pgp paramterers (pgp is callen when i start dpkg-buildpkg). on my system, pgp doesn't create clear sigs, and changing /etc/pgp-i.conf doesn't help. but that's a diffrent problem. dpkg should use +clearsig in any case, because it doesn't work without. Regards, Andreas
Bug#4341: no man page
Package: hello Version: 1.3-11 there is no man page. ok, i don't need a man page for hello, and there is a big info file, but as far as i understand debian, a missing man page is considered a bug. :-) Regards, Andreas
