Bug#4627: gawk" clean target prevents build

'llucius wrote:' > >Package: gawk >Version: 3.0.0-4 > >1) "debian/rules" clean target does not ignore errors when doing the >"make distclean" which causes the build to fail since there's nothing >to clean (not even a Makefile). Would you believe I ran into this problem when making my la

PGP?

Didn't we use to have a PGP package? I didn't find it any of the usual ftp sites and mirrors. I lost my installed version due to my incompatibility with dselect and now I'm having big trouble doing many of the things I need to do, including sending mail (since I've set up my mail so that mail is P

Bug#4629: "alias" is arch dependent

Package: alias Version: 2.1-2 1) "debian/rules" should build package in "binary-arch" target rather than "binary-indep" since this is a arch dependent package. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED

Bug#4630: "lclint-doc" should be arch independent

Package: lclint Version: 2.1b-1 1) "lclint-doc" is built as architecture dependent when it's not. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]

Bug#4631: "mailpgp" doesn't extract and should be arch independent

Package: mailpgp Version: 1.0-1 1) Source doesn't extract due to an invalid ".dsc" file and the ".diff.gz" patches reference a directory called "mailpgp-1.0-1" rather than the expected "mailpgp-1.0". 2) Since the package doesn't contain any architecture dependent files, it should

Bug#4632: "saytime" won't extract with dpkg-source

Package: saytime Version: 1.0-1 1) "saytime" will not extract with dpkg-source due to a directory of "saytime-1.0-0" in the ".orig.tar.gz" archive and because the ".diff.gz" attempts to patch a directory called "saytime-1.0-1" when it should "saytime-1.0". Also, the ".dsc" file is

Re: PGP?

> Didn't we use to have a PGP package? > I noticed that it disappeared a few days ago too. What's up? Did I miss an announcement or something? - Jim -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]

Bug#4633: "io" package should be built under "binary-arch" target

Package: io Version: 1.12-1 1) Since the package is architecture dependent, it should be built under the "binary-arch" target rathar than the "binary-indep" one. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECT

Bug#4634: "mpage" doesn't build when using "dpkg-buildpackage -B"

Package: mpage Versoin: 2.4-1 1) The work being done in the "binary-indep" target should be moved to the "binary-arch" target since the is an architecture dependent package. (Unless, the intent was to build an "mpage_2.4-1_i386.deb" and an "mpage-doc_2.4-1_all.deb" package?) -- T

Starting messages should have unique style

Hi folks! I just discovered that the start up messages of Debian don't have a unique style. Some say starting daemon xxx ... (lower case `s' and dots `...') while others say Starting network daemons: xxx (upper case `S', colon, no dots) etc. It would be nice if we had a "style gu

new package: nfsroot boot any client into Linux on network

30min after you installed this package on your server, you can: . Insert a nfsrootbootfloppy (create one with "mknfsrootboot") in any computer on your local network that has it's networkcard configured (running whatever OS), press "RESET", and hey presto, it's running LINUX! (and is confi

Re: Starting messages should have unique style

On Sun, 29 Sep 1996, Christian Schwarz wrote: > > Hi folks! > > I just discovered that the start up messages of Debian don't have a unique > style. Some say > starting daemon xxx ... > (lower case `s' and dots `...') while others say > Starting network daemons: xxx > (upper case `S',

Bug#4639: "mhonarc" has invalid ".orig.tar.gz" file

Package: mhonarc Version: 1.2.3-2 1) When extracting "mhonarc", dpkg-source produced the following message: dpkg-source: error: tarfile `/sys/downloads/mhonarc_1.2.3.orig.tar.gz' contains object (mhonarc.orig/) not in expected directory (mhonarc-1.2.3.orig) -- TO UNSUBS

Bug#4641: dpkg-source cannot create existing .tmp-nest dir

Package: dpkg-dev Version: 1.4.0 dpkg-source -b povray-3.0.10 dpkg-source: building povray using existing povray_3.0.10.orig.tar.gz dpkg-source: failure: unable to create `.tmp-nest': File exists I think dpkg-source should delete any existing dir before trying to create one and complain... Yves

m4_1.4-6 uploaded to master

-BEGIN PGP SIGNED MESSAGE- Format: 1.5 Date: Sun, 29 Sep 1996 16:29:38 -0400 Source: m4 Binary: m4 Architecture: source i386 Version: 1.4-6 Distribution: unstable Urgency: low Maintainer: Dale Scheetz <[EMAIL PROTECTED]> Description: m4 - a macro processing language Changes: m4

Re: Starting messages should have unique style

> It would be nice if we had a "style guide" so that the different > packages could all use the same style. What do you think? > Cool, I'm not the only one this bothered. Let's change it. Can we? Please, please! B-) Yes, yes! Let's start sentences with uppercase, and don't use

Bug#4642: Shar archives use incorrect shell code!

Package: sharutils Version: 4.2.1-1 Shar uses a lock dir for multifile archives, and the last shar file has the following code at the end: $echo $shar_n 'x -' 'lock directory' '_sh25318:' $shar_c if rm -fr _sh25318; then $echo 'removed' else $echo 'failed to remove'

Bug#4643: online help badly configured for vim-4.4

Package: vim Version: 4.4-1 Vim doesn't find its help files because all are gzipped :-( I have had to ungzip all these files before I could display online help (command :help). -rw-r--r-- 1 root root95556 Sep 24 14:53 vim_40.txt.gz -rw-r--r-- 1 root root 2960 Sep 24 1