Package: tar
Version: 1.11.8
When attemping to do remote tar operations using the archive name systax
specified in the info file, which is [EMAIL PROTECTED]:file, if user is not
specified, tar core dumps, when it should use the current username as the
default.
This is probably part of the same
Forwarded message:
From [EMAIL PROTECTED] Mon Oct 23 17:47:44 1995
Date: Mon, 23 Oct 1995 12:47:22 -0400 (EDT)
From: Fernando [EMAIL PROTECTED]
To: J.H.M.Dassen [EMAIL PROTECTED]
Subject: Re: Bug#1732: Bad arithmetic in new perl packages
In-Reply-To: [EMAIL PROTECTED]
Message-ID: [EMAIL
J.H.M.Dassen writes:
#!/usr/bin/perl
@array=(
item1 4 units,
item2 1.5 units,
item3 8 units + see item2
);
foreach (@array) {
if( ($item_name,$amount,$unit,$delimiter,$moreinfo)=
: Perl seems to be confused making some arithmetic operations (additions).
: Sometimes the result of $a+=$b, when $a is 0 and $b is 2 happens to be
: 2.04192 or something similar.
:
: Fernando, I unfortunately have no idea what is causing this. Please
: provide a short script which
Package: trn
Version: 3.6-2
It's not clear to me why trn uses 'recommends' for a mail transport
and a news article injector, while tin uses 'depends'. I think that depends
makes more sense, so I'm filing this against trn.
Bdale
Hyperlatex doesn't recommend ghostscript but gs from 1.3-5 (and higher)
I'm closing this bug.
--
Erick [EMAIL PROTECTED] +31-10-4635142
Department of General Surgery (Intensive Care) University Hospital Rotterdam NL
Marek Michalkiewicz wrote:
Package: at
Version: 2.8a-2
The at command sometimes has problems with date parsing which result
in a SEGV. For example:
$ at tomorrow
Segmentation fault
I think I've fixed this in the most recent version of at, 2.9a,
which has been out since August or so.
Thomas
--
Since noone is maintaining these, and they *desperately* need
updating, I shall do it.
Who has the latest version and which format are they in ?
Ian.
Package: bash
Version: 1.14.4-5
Bash doesn't quote correctly in some cases. Here is a test case which
exhibits the problem:
---start of showbug---
#!/bin/sh
./printargc $0 ${1+$@}
---end of showbug---
---start of printargc---
#!/bin/sh
echo 'argc =' $#
---end of printargc---
Running showbug
Bdale Garbee writes (Bug#1753: trn recommends, instead of depends):
Package: trn
Version: 3.6-2
It's not clear to me why trn uses 'recommends' for a mail transport
and a news article injector, while tin uses 'depends'. I think that depends
makes more sense, so I'm filing this against trn.
Package: netbase
Version: 1.91-1
See the transcript below. The `-f' (flood ping) option is disabled
for non-root users, but IMO the -l option should be restricted or
disabled too.
Ian.
chiark:~ id
uid=1001(ijackson) gid=1001(ijackson)
groups=1001(ijackson),202(doom),203(killer)
chiark:~ ping
Here's an strace of dpkg failing. [Remember, this is on an empty
directory.]
Notice especially the line that reads:
readdir(4, 0x48000) = -1 ENOENT (No such file or directory)
I don't have a clue where that 0x48000 argument is coming from, but it
looks like it's corrupt
Package: source
Version: 1.2.13
To reproduce: do lots of things that need lots of swap, when you
haven't got enough.
Effect: system locks up totally, with only an insignificant amount
of disk activity.
Thrashing badly I could understand (but wouldn't like). Randomly
killing processes I could
Ian Jackson writes (Bug#1758: recommended):
reassign 1753 tin
Damn, that's the second time I've done that.
I'll go and check my mail aliases.
Ian.
On Tue, 24 Oct 1995, Bruce Perens wrote:
[EMAIL PROTECTED] said:
Are you saying it looks anywhere near as nice as mine ?
Well, I think it looks awful, but I will accept your format simply
to end this argument if you or someone else
will write and maintain the parser for it and
an
Michael Alan Dorman writes (Conflicting with a range of revisions...):
Well, I've decided to return to Matt Porters' previous split between
minicom and lrzsz.
One side-effect of this is that I need to make the updated lrzsz package
conflict just with minicom-1.71-[1..2] (the ones that
[EMAIL PROTECTED] said:
Please add and document to this. If tools are introduced into the
distribution, the author and maintainer of those tools should provide
and maintain man pages for them.
Yes, that makes sense. The parse wasn't immediately obvious to me. For
example, is the semicolon
I completely fail to understand why anyone is promoting this format.
It is ugly, and my format is machine readable too.
But Ian, almost _any_ format can be made machine readable -- but
Bill's format is _easily_ machine readable -- you could slap together
a whole bunch of ways to read it.
Martin Schulze writes (sysklogd-1.2-13 released):
I'm just trying to upload this package. The changes are only minor
ones. Here are the relevant ChangeLog entries
...
* changed the name in control file (Bug#1695)
Aaargh, no !
Please, change it back.
Ian Murdock wrote:
Ian == Ian Jackson [EMAIL PROTECTED] writes:
Ian `|' is not allowed in conflicts; `,' is used to mean OR.
It would be nice if CONFLICTS and the other fields used the same
notation for OR/AND, instead of being in direct apposition.
Could the current behavior be gradually phased out at some
Ian Jackson writes:
Bill Mitchell writes (changes file format):
Just out of curiosity, does the following represent a horribly
formatted and human-unreadable package announcement? Except for
the lack of a Priority field, it passes the dchanges(1) syntax check.
I completely fail to understand
21 matches
Mail list logo
