Re: blue on black is unreadable

[Anthony Towns]

On Sun, Mar 26, 2000 at 12:54:39AM +0100, Wouter Hanegraaff wrote:
> Why does debian have to be different than the rest of the world in
> everything? Why do I get colors when I set TERM=xterm? there was already
> xterm-color and xterm-debian which could do colors.

Other Linux distributions tend to default to a colour xterm, I thought.

> Right now, I have to set my TERM to xterm-mono on potato to avoid
> fruitsalads in a handful of programs I use very often (Mutt, dselect,
> vim). 

So why don't you just change your local settings to make xterm be mono?
Ummm. `XTerm*ColorMode: no' seems like it'd do what you want.

> Please leave *personal* configuration to the *user*

Indeed.

Cheers,
aj

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG encrypted mail preferred.

 ``The thing is: trying to be too generic is EVIL. It's stupid, it 
results in slower code, and it results in more bugs.''
-- Linus Torvalds


pgpghATCs1TAV.pgp
Description: PGP signature

Re: Idea: Debian Developer Information Center

[Domenico Andreoli]

On Sat, Mar 25, 2000 at 10:40:27PM +0100, Josip Rodin wrote:
[snip]

> 
> > > With this system, each developer can add his own page on one of his
> > > bookmark and from time to time he can check what he's responsible for and
> > > what he should do in one look.
> [snip]
> 
> It would be my first bookmark... please do it :)
it would mine too.

-[ Domenico Andreoli, aka cavok <[EMAIL PROTECTED]>
  --[ get my public pgp key at http://www.freeweb.org/free/cavok/
 -[ ICQ: 56447243 ]--  ---[ look for DeCSS code in my homepage!


pgpdbvmgHRVFA.pgp
Description: PGP signature

Re: Signing Packages.gz

[Chris Frey]

On Sat, Mar 25, 2000 at 11:03:11PM +0100, Robert Bihlmeyer wrote:
> Chris Frey <[EMAIL PROTECTED]> writes:
> 
> > So my question is, what are your thoughts on adding a signature to the
> > current Packages.gz file, or adding a similar *dsc file for it,
> > which is then signed? 
> 
> Do you want to sign each package entry, or the whole file? Whose
> signature would be used?

I think each Packages file should be signed.  And the person responsible
for generating those Packages files should be the one to sign it, no?

> (BTW, You could add "Mail-Copies-To: poster" to the headers you use
> for this list.)

Cool, thanks.

- Chris

-- 
---
"Chase the dream, not the competition."
 - motto of the Nemesis Air Racing Team

Re: Idea: Debian Developer Information Center

[Joseph Carter]

On Sat, Mar 25, 2000 at 09:51:50PM +0100, Raphael Hertzog wrote:
> Hey people ! I posted this mail in order to have some input ... it would
> be great if some of you gave their opinion about this proposition I posted
> a while ago :
[..]

I'd have to bookmark myself.  ;>

-- 
Joseph Carter <[EMAIL PROTECTED]>   GnuPG key 1024D/DCF9DAB3
Debian GNU/Linux (http://www.debian.org/) 20F6 2261 F185 7A3E 79FC
The QuakeForge Project (http://quakeforge.net/)   44F9 8FF7 D7A3 DCF9 DAB3

 java, hon, sometimes I really want to smack you.
 Valkyrja - he'd enjoy it too much
 Valkyrja: yah, go ahead and do it... beat java into cappuccino! :-)

ITP Twig

[Jordi Mallach]

Hello,

I'm not sure about this, but I think there's no web frontend for mail in
Debian, so I am going to try to package twig.
I have not seen any entry for this app in WNPP, but if anyone really wants
this package, I have no problem giving it away.

Taken from fm's description,

TWIG is a web-based IMAP client written with PHP3. Its features include
IMAP E-mail, contact management, scheduling, Usenet
newsgroups, todo manager, and bookmark management. Any piece of
information can be shared with other users on the system using
TWIG's built-in groupware functionality. TWIG is written and implemented
completely with the PHP programming language. The
author's intention is that it becomes a simple, cross-platform, fast, and
browser-independent way to access or share almost any kind of
information, without the complexity or costs of other intranet/groupware
packages.

It's licensed under the GPL.

Thanks,

Jordi

-- 
Jordi Mallach Pérez || [EMAIL PROTECTED]   || Rediscovering Freedom,
ka Oskuro in RL-MUD || [EMAIL PROTECTED]|| Using Debian GNU/Linux

http://sindominio.net  GnuPG public information:  pub  1024D/917A225E 
telnet pusa.uv.es 23   73ED 4244 FD43 5886 20AC  2644 2584 94BA 917A 225E

Re: ITP Twig

[Alisdair McDiarmid]

On Sun, Mar 26, 2000 at 04:43:51AM +0200, Jordi Mallach wrote:
> 
> I'm not sure about this, but I think there's no web frontend for mail in
> Debian, so I am going to try to package twig.
 
Well, there's IMP... but twig looks nice, so don't let that stop your
ITP :-)
-- 
Alisdair McDiarmid[EMAIL PROTECTED]
...http://wasters.org/

RBL report..

[Jason Gunthorpe]

Okay, since everyone really desperately wants to know, I ran the numbers
on the effectiveness of RBL, RSS, DUL and ORBS against the mail intake for
lists.debian.org. All of this is theoretical and done offline against the
log file, we are blocking only via RBL (and now RSS) 

The period of analysis was 1 week.

Stat #1
  Of 3054 unique IPs 386 are in one of the RBL's, the breakdown is:
   RBL - 16
   RSS - 45
   DUL - 49 [17 rcn.com, 14, psi.net]
   ORBS - 314
  Comparing connections it is found that 3970 out of 40236 connection
  attempts would have been blocked. This can be roughly considered to be
  3970 emails blocked.

Stat #2
  Cross referencing the IP list against the bad bounce log shows 13 IPs. 
  These are highly likely to be legitimate emails.

Stat #3 
  Cross referencing the IP list against the content filtered spam log
  shows 0 hits [not surprising, this log is very small].

Stat #4
  Taking the list of all subscriber domains and substring matching this
  against the list (loosly, check for people who are blocked but
  subscribed to the list) gives 226 matches. Breakdown:
RBL - 1 
RSS - 12
DUL - 26
ORBS - 196
  The RBL and RSS hits show a very good chance of actually being
  legitimate list subscribers :< It is impossible to tell with DUL if
  the host is a subscriber on a modem or something else. ORBS is to
  prolific to check by hand.

Stat #5
  Collecting IPs from all recived and relayed (ie good) list mail and
  corellating gives 28 matches. Breakdown:
RBL - 0[Expected, we are banning RBL]
RSS - 1
DUL - 18 [17 from a single user on rcn.com]
ORBS - 10
  Note, during the 1 week period I estimate that no more than 5 unique
  spams were recieved. May of the spams were sent to all lists. Also
  note that aliases like [EMAIL PROTECTED] are not covered by these
  stats.

There seems to be a huge mismatch between messages accounted for and
messages taken in, I think these are due to sucessfully processed bounces
by the list software, which do not get logged [?]

Conclusions

I have been unable to conclusively show that any of the RBLs are actually
reducing spam, but I have positively confirmed that they *all* (save RBL
which I cannot check since we block on it) would result in legitimate
messages being blocked. 

ORBS deserves special mention because of their insane hit count, I don't
know what that is about but ORBS would block 10% of the mails we get. I
think it is without question that the majority of those blocks are
legitimate mails. ORBS is also almost completely inclusive of the RSS and
RBL.

DUL would seem to effect at most maybe 10 people, but it hasn't actually
been shown to stop any spam - so this needs more investigation. DUL has a 
policy that many people find objectional.

A perusal of the DUL ips all suggest they are *all* modems which is a
really selective filter swath. No DSL or Cable IPs appear to be listed! 

RBL has not been conclusively shown to stop spam, but it has such a low
impact (<3 uniq hits each day) that we use it anyhow.

RSS has been observed to list the occasional spam, this is expected since
they respond to spammer activity - but it is also shown that it will
effect at least 1-2 people.

* Note, once a site is listed in one of these RBLs it becomes impossible
for a user to unsubscribe from our lists - no matter what they do they
will never be able to communicate a bounce or a unsubscribe request - this
is pretty bad.

Jason

Re: RBL report..

[Hamish Moffatt]

On Sat, Mar 25, 2000 at 11:28:24PM -0700, Jason Gunthorpe wrote:
> A perusal of the DUL ips all suggest they are *all* modems which is a
> really selective filter swath. No DSL or Cable IPs appear to be listed! 

Well, I don't know about the US, but I suspect that's because you can
have a dialup account in just a few minutes on the phone or the web,
but DSL or cable requires special hardware and there are few providers.
Here in Melbourne we have two cable providers and no DSL providers at all;
you'd quickly run out of cable providers to spam through :-)


Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

ITP: pcrd

[Bdale Garbee]

I have packaged 'pcrd', which is a utility for controlling an Icom PCR-1000
radio receiver.  It is probably mostly of interest to amateur radio folk,
and so will go in the hamradio section.

The upstream site for this package is

http://www.mv.net/ipusers/cdwalker/pcrd.html

The PCR-1000 itself is sold by Icom, who have a sales-oriented web page for it
at

http://www.icomamerica.com/receivers/pc/

The package is done, and I'm playing with it now.  I'll probably upload it
sometime tomorrow.

Bdale

Re: RBL report..

[Michael Neuffer]

* Jason Gunthorpe ([EMAIL PROTECTED]) [000326 08:45]:
>[...]
>ORBS - 314
>   Comparing connections it is found that 3970 out of 40236 connection
>   attempts would have been blocked. This can be roughly considered to be
>   3970 emails blocked.
>[...] 
> ORBS deserves special mention because of their insane hit count, I don't
> know what that is about but ORBS would block 10% of the mails we get. I
> think it is without question that the majority of those blocks are
> legitimate mails. ORBS is also almost completely inclusive of the RSS and
> RBL.

ORBS has a slightly different (broader and maybe better) goal then the 
the others. It actively scans the net for open mail relays, warns 
the operators of these machines multiple times with exact descriptions 
of what they are doing, trying to accomplish (ie closing open mail relays)
which problems have been found, how to fix them (plus necessary pointers
to other sites) and how to get of the list. Only then the machine is added 
to the list.

Mike

Re: RBL report..

[Nils Jeppe]

On Sat, 25 Mar 2000, Jason Gunthorpe wrote:

> ORBS deserves special mention because of their insane hit count, I don't
> know what that is about but ORBS would block 10% of the mails we get. I
> think it is without question that the majority of those blocks are
> legitimate mails. ORBS is also almost completely inclusive of the RSS and
> RBL.

ORBS blocks all open relays. A lot of people have open relays. Since open
relays still do not have any reason for existence other than admin
ignorance, the "correct" way here would be to block all open relays and
then fix the mail servers. ORBS really cuts down on spam, the accounts I
have protected by ORBS usually only get one type of spam: that is spam
resent via mailing lists.

> * Note, once a site is listed in one of these RBLs it becomes impossible
> for a user to unsubscribe from our lists - no matter what they do they
> will never be able to communicate a bounce or a unsubscribe request - this
> is pretty bad.

Hmmm actually, I use Exim, and Exim has a way to configure
"exceptions" from RBL blocks. So you could enter an
unsubscribe-alias-email-address into these exceptions.




Nils


-- 
 "Kif, if there's one thing I don't need it's your 'I don't think that's
  wise' attitude."
--- Zap Brannigan

Re: RBL report..

[Joseph Carter]

On Sun, Mar 26, 2000 at 10:49:09AM +0200, Michael Neuffer wrote:
> > ORBS deserves special mention because of their insane hit count, I don't
> > know what that is about but ORBS would block 10% of the mails we get. I
> > think it is without question that the majority of those blocks are
> > legitimate mails. ORBS is also almost completely inclusive of the RSS and
> > RBL.
> 
> ORBS has a slightly different (broader and maybe better) goal then the 
> the others. It actively scans the net for open mail relays, warns 
> the operators of these machines multiple times with exact descriptions 
> of what they are doing, trying to accomplish (ie closing open mail relays)
> which problems have been found, how to fix them (plus necessary pointers
> to other sites) and how to get of the list. Only then the machine is added 
> to the list.

ORBS has a tendancy to not take the time to make sure their messages go to
the right places and then they are very slow to take sites off the list
after problems are fixed.

ie, to them making sure spam never happens is more important than what
damage they cause in hte process.  I rate them in with the DUL.

-- 
Joseph Carter <[EMAIL PROTECTED]>   GnuPG key 1024D/DCF9DAB3
Debian GNU/Linux (http://www.debian.org/) 20F6 2261 F185 7A3E 79FC
The QuakeForge Project (http://quakeforge.net/)   44F9 8FF7 D7A3 DCF9 DAB3

 you know, Linux needs a platform game starring Tux
 kinda Super Marioish, but with Tux and things like little cyber
   bugs and borgs and that sort of thing ...
 And you have to jump past billgatus and hit the key to drop him
   into the lava and then you see some guy that looks like a RMS
   or someone say "Thank you for rescuing me Tux, but Linus
   Torvalds is in another castle!"

Re: RBL report..

[Nils Jeppe]

On Sun, 26 Mar 2000, Joseph Carter wrote:

> ORBS has a tendancy to not take the time to make sure their messages go to
> the right places and then they are very slow to take sites off the list
> after problems are fixed.

afaik, ORBS sends to [EMAIL PROTECTED] What other right place could there
be?

And taking people off the list is automatic. Fix it, enter the IP in their
form, it gets re-cehcekd and taken off the list. Works like a charm.

> ie, to them making sure spam never happens is more important than what
> damage they cause in hte process.  I rate them in with the DUL.

If people configured their servers correctly, they'd never get on the
list. ;-) Also, ORBS allows for I think 3-5 days warning in advance, which
is sufficient to fix a server.



Nils


-- 
 "Kif, if there's one thing I don't need it's your 'I don't think that's
  wise' attitude."
--- Zap Brannigan

Bug#46388: marked as done (NO 2.1r3 M68K CDs: trn depends)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:23:16 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug fixed by now
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 1 Oct 1999 10:24:56 +
Received: (qmail 26871 invoked from network); 1 Oct 1999 10:24:55 -
Received: from panic.et.tudelft.nl ([EMAIL PROTECTED])
  by master.debian.org with SMTP; 1 Oct 1999 10:24:55 -
Received: from localhost ([EMAIL PROTECTED])
by panic.et.tudelft.nl (8.9.3/8.9.3/Debian/GNU) with SMTP id MAA31907
for <[EMAIL PROTECTED]>; Fri, 1 Oct 1999 12:24:54 +0200
Date: Fri, 1 Oct 1999 12:24:54 +0200 (CEST)
From: "J.A. Bezemer" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: NO 2.1r3 M68K CDs: trn depends
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Package: trn
Version: that from 2.1_r3
Severity: critical

Architecture: M68K

trn:
Depends: libc6, libncurses4 (>= 4.2-3.1), inews

libncurses4:
Version: 4.2-3

Due to this problem, NO 2.1_r3 CD IMAGES CAN BE MADE FOR M68K!!

This problem was already reported 4-9-99 and still not corrected. Please
correct this ASAP.

Please report to debian-cd@lists.debian.org when this problem is fixed, so
2.1_r3 CD images can be made.

BTW, this info is from the Packages.gz file.

Regards,
  Anne Bezemer

---
Received: (at 46388-done) by bugs.debian.org; 26 Mar 2000 09:23:18 +
Received: (qmail 24893 invoked from network); 26 Mar 2000 09:23:17 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:23:17 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 377804045; Sun, 26 Mar 2000 11:23:16 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:23:16 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Bug fixed by now
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

This bug refers to a package that must be included in 2.1r3, since then we
have released r4 and r5 and I'm quite sure that the good package has been
integrated ... so this bug can be closed.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Bug#50494: marked as done (general: More themes (gtk, gnome, various windowmanagers, etc) and more backgrounds)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:26:02 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Themes in debian
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 18 Nov 1999 03:16:05 +
Received: (qmail 3654 invoked from network); 18 Nov 1999 03:16:05 -
Received: from pacific-carrier-annex.mit.edu (HELO MIT.EDU) (18.69.0.28)
  by master.debian.org with SMTP; 18 Nov 1999 03:16:05 -
Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP
id AA11154; Wed, 17 Nov 99 22:16:34 EST
Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU 
[18.69.0.45])
by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id WAA02262;
Wed, 17 Nov 1999 22:16:03 -0500 (EST)
Received: from aquinas (STRATTON-FORTY-NINE.MIT.EDU [18.187.5.49])
by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id WAA14075;
Wed, 17 Nov 1999 22:16:02 -0500 (EST)
Received: from tb by aquinas with local (Exim 3.03 #1 (Debian))
id 11oI3G-0001ut-00; Wed, 17 Nov 1999 22:16:02 -0500
From: Thomas Bushnell BSG <[EMAIL PROTECTED]>
Subject: general: More themes (gtk, gnome, various windowmanagers, etc) and 
more backgrounds
To: [EMAIL PROTECTED]
X-Mailer: bug 3.2.7
Message-Id: <[EMAIL PROTECTED]>
Date: Wed, 17 Nov 1999 22:16:02 -0500

Package: general
Version: 19991118
Severity: wishlist

Debian should have more themes and backgrounds and pixmaps in suitable packages,
at least all the ones Red Hat has (the principle competition) and maybe all
the ones from themes.org that have gotten enough interest there (they
keep usage stats and votes to make some kind of judgment possible).  

I'm assuming this "wishlist bug" will get handled by adding entries to the
"ideas that need package maintainers" list.

-- System Information
Debian Release: potato
Kernel Version: Linux aquinas 2.2.13 #6 Wed Nov 17 17:02:21 EST 1999 i686 
unknown

---
Received: (at 50494-done) by bugs.debian.org; 26 Mar 2000 09:26:04 +
Received: (qmail 27233 invoked from network); 26 Mar 2000 09:26:03 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:26:03 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 465F04045; Sun, 26 Mar 2000 11:26:02 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:26:02 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Themes in debian
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

A reasonable conclusion has been reached, there's the theme-converters
package for anyone who want its favorite theme in .deb ...

This bug can be closed.
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Bug#50534: marked as done (Work-Needing and Prospective Packages for Debian GNU/Linux)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:30:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ITP with URLs
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 18 Nov 1999 12:24:05 +
Received: (qmail 11023 invoked from network); 18 Nov 1999 12:24:04 -
Received: from mx03.uni-tuebingen.de (134.2.3.13)
  by master.debian.org with SMTP; 18 Nov 1999 12:24:04 -
Received: from mirjam.informatik.uni-tuebingen.de ([EMAIL PROTECTED] 
[134.2.15.134])
by mx03.uni-tuebingen.de (8.8.8/8.8.8) with ESMTP id NAA24399
for <[EMAIL PROTECTED]>; Thu, 18 Nov 1999 13:24:02 +0100
Received: by mirjam.informatik.uni-tuebingen.de
via sendmail from stdin
id <[EMAIL PROTECTED]> (Debian Smail3.2.0.102)
for [EMAIL PROTECTED]; Thu, 18 Nov 1999 13:24:00 +0100 (CET) 
Message-Id: <[EMAIL PROTECTED]>
From: Goswin Brederlow <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Work-Needing and Prospective Packages for Debian GNU/Linux
X-Mailer: reportbug 0.24
Date: Thu, 18 Nov 1999 13:24:00 +0100

Package: general
Version: N/A; reported 1999-11-18
Severity: wishlist

The "Packages that someone is working on" list should carry url´s for
upstream sources and/or work in progress.

-- System Information
Debian Release: potato
Architecture: i386
Kernel: Linux rut 2.0.35 #4 Thu Nov 26 15:35:03 CET 1998 i686

---
Received: (at 50534-done) by bugs.debian.org; 26 Mar 2000 09:30:55 +
Received: (qmail 28685 invoked from network); 26 Mar 2000 09:30:55 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:30:55 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 70A154045; Sun, 26 Mar 2000 11:30:50 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:30:50 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: ITP with URLs
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

When someone posts an ITP to debian-devel he usually gives an URL. But
there's no need to add this information in WNPP, this will only give more
work to already busy people and everybody knows about freshmeat so it's
trivial to find the URL for a particular project/program/package. And you
already have the email of the person who is packaging it, you can
contact him for any question like that.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Bug#60988: marked as done (general: problem with ssh install due to lack of gmp2 package in frozen)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:21:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line bad non-US line in its sources.list
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 23 Mar 2000 14:41:45 +
Received: (qmail 27045 invoked from network); 23 Mar 2000 14:41:44 -
Received: from vulcan.hertford.ox.ac.uk (129.67.9.30)
  by master.debian.org with SMTP; 23 Mar 2000 14:41:44 -
Received: from hert0919 by vulcan.hertford.ox.ac.uk with local (Exim 2.05 #1 
(Debian))
id 12Y8pg-0003Og-00; Thu, 23 Mar 2000 14:43:32 +
From: David Croxford <[EMAIL PROTECTED]>
Subject: general: problem with ssh install due to lack of gmp2 package in frozen
To: [EMAIL PROTECTED]
X-Mailer: bug 3.2.10
Message-Id: <[EMAIL PROTECTED]>
Date: Thu, 23 Mar 2000 14:43:32 +

Package: general
Version: 2323
Severity: important

Partial output of 
apt-get install ssh

Sorry, but the following packages have unmet dependencies:
  ssh: Depends: gmp2 (>= 2.0.2)
E: Sorry, broken packages

There appears to be a libgmp2 package which replaces gmp2. Apt-get does not
substitute this when asked to install ssh. It does when asked to install
gmp2 though.

-- System Information
Debian Release: 2.2
Kernel Version: Linux vulcan 2.2.13 #2 Fri Feb 11 10:55:15 GMT 2000 i686 unknown

---
Received: (at 60988-done) by bugs.debian.org; 26 Mar 2000 09:21:10 +
Received: (qmail 23561 invoked from network); 26 Mar 2000 09:21:09 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:21:09 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 2039A4045; Sun, 26 Mar 2000 11:21:06 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:21:06 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: bad non-US line in its sources.list
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

It's quite evident that this guy doesn't have a good non-US line in its
sources.list ... there's no need for this bug to stay open.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Anyone's able to run 2.3.99-pre*?

[Michael Meskes]

e2fscheck always tells me it cannot read the superblock. Up to 2.3.4? it
worked well. And of course 2.2.14 runs without a problem.

Michael
-- 
Michael Meskes | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz| Go Rhein Fire!
Tel.: (+49) 2431/72651 | Use Debian GNU/Linux!
Email: Michael@Fam-Meskes.De   | Use PostgreSQL!

Bug#29453: marked as done (KDE installation on Debian 2.0)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:46:13 +0200
with message-id <[EMAIL PROTECTED]>
and subject line old kde packages and qt lib
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 14 Nov 1998 19:41:49 +
Received: (qmail 29849 invoked from network); 14 Nov 1998 19:41:45 -
Received: from dub-img-4.compuserve.com (149.174.206.134)
  by master.debian.org with SMTP; 14 Nov 1998 19:41:45 -
Received: (from [EMAIL PROTECTED])
by dub-img-4.compuserve.com (8.8.6/8.8.6/2.16) id OAA27945
for [EMAIL PROTECTED]; Sat, 14 Nov 1998 14:41:38 -0500 (EST)
Date: Sat, 14 Nov 1998 14:41:25 -0500
From: Lionel Fradin <[EMAIL PROTECTED]>
Subject: KDE installation on Debian 2.0
Sender: Lionel Fradin <[EMAIL PROTECTED]>
To: BugDebian <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline

 Hi,
 =

 I am actually trying to install the KDE package from the files I
downloaded from www.kde.org.

Following the KDE installation instructions, I got the Qt1g library from
www.troll.no/dl and compiled them in /usr/local/qt/lib.
(this is Qt1g 1.41).
 =

 The LD_LIBRARY_PATH is set to /usr/local/qt/lib in my .bash_profile
(.profile is not used) as told by Qt installation instructions.

 When unpacking kdebase(after unpacking kdesupport and kdelibs) with 'dpk=
g
-i kdebase.exe', I get a system
 message saying 'Package qt1g is not installed'.
  =

 With 'dpkg --i --debug=3D400 kdebase.exe', all depencies are found b=
ut
Qt library.
 =

 Where is dpkg looking when trying to solve dependencies?
 =

 Am I supposed to copy the Qt library files in other directory or did I
miss something?

If /etc/ld.so.conf is modified to look at /usr/local/qt/lib when running
/sbin/ldconfig, the problem remains.
I am still not able to unpack and configure kdebase.

 Hoping anybody can help me to solve that problem out, if not can you
please tell me who I can contact about my dependency problem?
 =

Thanks a lot,

By the way,is there a package to install printers (HP Laserjet) such as
'admintool' (Sun) or lpadmin or printtool (RedHat 5.2) provided with Debi=
an
2.0 or should I play along with with the printcap file?

Lionel
---
Received: (at 29453-done) by bugs.debian.org; 26 Mar 2000 09:46:15 +
Received: (qmail 1296 invoked from network); 26 Mar 2000 09:46:15 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:46:15 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id DA0414045; Sun, 26 Mar 2000 11:46:13 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:46:13 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: old kde packages and qt lib
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

Debian unlike RH doesn't use file dependeny, but only packages
dependencies. So to install KDE packages, you'll first need to install the
qt package.

This can be done automatically nowadays with apt. Check the KDE web site
for information on where to find the latest .debs.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Re: Anyone's able to run 2.3.99-pre*?

[Petr Cech]

On Sun, Mar 26, 2000 at 10:35:02AM +0200 , Michael Meskes wrote:
> e2fscheck always tells me it cannot read the superblock. Up to 2.3.4? it
> worked well. And of course 2.2.14 runs without a problem.

check that you don't mount devfs, and have IDE subsystem compiled in (it
changed location). 

Petr Cech
--
Debian GNU/Linux maintainer - www.debian.{org,cz}
   [EMAIL PROTECTED]

Bug#40117: marked as done (idea: subarchitectures for x86)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:41:37 +0200
with message-id <[EMAIL PROTECTED]>
and subject line subarch for i386
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 24 Jun 1999 17:26:59 +
Received: (qmail 16546 invoked from network); 24 Jun 1999 17:26:59 -
Received: from mail.r-u-sure.com (HELO mail.rusure.com) ([EMAIL PROTECTED])
  by master.debian.org with SMTP; 24 Jun 1999 17:26:59 -
Received: (qmail 26330 invoked by uid 1000); 24 Jun 1999 18:43:14 -
Date: Thu, 24 Jun 1999 20:43:14 +0200
From: Peter Skliarouk <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: idea
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i

Hi!

I'm sorry to send such message to here and not to any mailing
list of debian - but I don't know to which I should send such
question:

Was there considered idea about making several trees of debian -
like debian-i386, debian-i586, debian-iXeon, debian-iMerced ...?

-- 
Bye,| "Unix is simple. It just takes a
Penn.   |  genius to understand its simplicity"
|Dennis Ritchie
---
Received: (at 40117-done) by bugs.debian.org; 26 Mar 2000 09:41:39 +
Received: (qmail 32235 invoked from network); 26 Mar 2000 09:41:39 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:41:38 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 826134045; Sun, 26 Mar 2000 11:41:37 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:41:37 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: subarch for i386
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

This kind of proposition comes back from time to time, but at the
present time it's not at all doable since the mirrors are already 
excessively big. We'd need many more autobuilders for i386 ...
Finally, this is many work for not many results.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Bug#55773: marked as done (general: apt/sources.list on a per mirror basis?)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:36:11 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Good sources.list file with non-US
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 20 Jan 2000 13:07:53 +
Received: (qmail 7073 invoked from network); 20 Jan 2000 13:07:52 -
Received: from mail.orgatech.de (62.208.21.3)
  by master.debian.org with SMTP; 20 Jan 2000 13:07:52 -
Received: from surusoitto.orgatech.de ([EMAIL PROTECTED] [62.208.21.199])
by mail.orgatech.de (8.9.1a/8.9.1) with ESMTP id OAA20806
for <[EMAIL PROTECTED]>; Thu, 20 Jan 2000 14:12:22 +0100 (MET)
Received: from dieter.north.de (matti.winnegan.de) [194.94.254.153] 
by surusoitto.orgatech.de with esmtp (Exim 3.03 #1 (Debian))
id 12BHJU-0008LH-00; Thu, 20 Jan 2000 14:07:49 +0100
Received: from bsb by matti.winnegan.de with local (Exim 3.12 #1 (Debian))
id 12BHJT-00015a-00; Thu, 20 Jan 2000 14:07:47 +0100
From: <[EMAIL PROTECTED]>
Subject: general: apt/sources.list on a per mirror basis?
To: [EMAIL PROTECTED]
X-Mailer: bug 3.2.7
Message-Id: <[EMAIL PROTECTED]>
Date: Thu, 20 Jan 2000 14:07:47 +0100

Package: general
Version: 2120
Severity: wishlist

I don't think the following is a problem with apt, but it's related to
non-US being mirrored to different locations. Do we have a mirrors
pseudo-package to assign this wishlist-bug to? 

I'd like to see mirrors putting a sources.list file into their /debian
directory which a user can download and copy relevant lines into
/etc/apt/sources.list.

Since ftp.de.debian.org currently doesn't allow anonymous ftp access,
I replaced "de" with "nl" and "uk" respectively only to find out that
non-US Package files could not be retrieved :(

Regards
  Siggy

-- System Information
Debian Release: potato
Kernel Version: Linux matti 2.2.14 #1 Thu Jan 6 21:42:39 CET 2000 i586 unknown

---
Received: (at 55773-done) by bugs.debian.org; 26 Mar 2000 09:36:12 +
Received: (qmail 29282 invoked from network); 26 Mar 2000 09:36:12 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:36:12 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 198AA4045; Sun, 26 Mar 2000 11:36:11 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:36:11 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Good sources.list file with non-US
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

Hi,

all the primary ftp mirrors already use a standard location, and you can
(most of the time) use something like that :
deb ftp://ftp.fr.debian.org/debian-non-US frozen/non-US main contrib non-free
deb ftp://ftp.fr.debian.org/debian frozen main contrib non-free

And from potato on, sources.list will be modified by base-config if
network install is used, it will add the correct lines after having asked
your country (to try to detect the best mirror).

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Bug#21464: marked as done (bo -> hamm upgrade problems)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:48:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing old bug reports related to bo->hamm transition
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 21 Apr 1998 08:38:29 +
Received: (qmail 20818 invoked from network); 21 Apr 1998 08:38:29 -
Received: from tmcs.tm.tno.nl (HELO tmcs) (192.43.212.100)
  by debian.novare.net with SMTP; 21 Apr 1998 08:38:29 -
Received: from suntan.izf.tno.nl by tmcs (SMI-8.6/SMI-SVR4)
id KAA17882; Tue, 21 Apr 1998 10:38:25 +0200
Received: by suntan.izf.tno.nl (SMI-8.6/SMI-SVR4)
id KAA16615; Tue, 21 Apr 1998 10:38:24 +0200
Date: Tue, 21 Apr 1998 10:38:24 +0200
Message-Id: <[EMAIL PROTECTED]>
From: David van Leeuwen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: bo -> hamm upgrade problems

Package: dselect, general upgrading

I get several dependency loop poblems in upgrading from Debian 1.3.1
to hamm/frozen of last night.  First package was slang0.99.34, during 
install process of dselect:

Looking for part 1 of slang0.99.38 ... 
/root/debian/unstable/hamm/binary-i386/libs/slang0.99.38_0.99.38-2.18.deb
Running dpkg -iB for slang0.99.38 ...
dpkg: regarding .../slang0.99.38_0.99.38-2.18.deb containing slang0.99.38:
 slang0.99.38 conflicts with slang0.99.34 (<< 0.99.38-2.3)
  slang0.99.34 (version 0.99.38-2) is installed.
dpkg: error processing 
/root/debian/unstable/hamm/binary-i386/libs/slang0.99.38_0.99.38-2.18.deb 
(--install):
 conflicting packages - not installing slang0.99.38
Errors were encountered while processing:
 /root/debian/unstable/hamm/binary-i386/libs/slang0.99.38_0.99.38-2.18.deb

2nd try:

internal error - no filename at -e line 12,  chunk 21.

Then, i removed slang0.99.34 by hand (after removing dosemu) and
installed slang0.99.38 by hand. 

Now, dselect's install works again, but i get a next problem:

Looking for part 1 of libgdbmg1 ... 
/root/debian/unstable/hamm/binary-i386/base/libgdbmg1_1.7.3-24.deb
Running dpkg -iB for libgdbmg1 ...
dpkg: regarding .../base/libgdbmg1_1.7.3-24.deb containing libgdbmg1:
 libgdbmg1 conflicts with libgdbm1 (<< 1.7.3-20)
  libgdbm1 (version 1.7.3-19) is installed.
dpkg: error processing 
/root/debian/unstable/hamm/binary-i386/base/libgdbmg1_1.7.3-24.deb (--install):
 conflicting packages - not installing libgdbmg1
Errors were encountered while processing:
 /root/debian/unstable/hamm/binary-i386/base/libgdbmg1_1.7.3-24.deb

2nd try:

internal error - no filename at -e line 12,  chunk 19.

And i really can't solve that by hand.  

---david
---
Received: (at 21464-done) by bugs.debian.org; 26 Mar 2000 09:48:47 +
Received: (qmail 1456 invoked from network); 26 Mar 2000 09:48:47 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:48:47 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 56A604045; Sun, 26 Mar 2000 11:48:44 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:48:44 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Closing old bug reports related to bo->hamm transition
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

Evrything in the subject. Those bugs are no more of actuality.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Bug#23883: marked as done (Danger in using autoup.sh)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:48:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing old bug reports related to bo->hamm transition
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 25 Jun 1998 11:20:23 +
Received: (qmail 2291 invoked from network); 25 Jun 1998 11:20:21 -
Received: from cri.ens-lyon.fr (140.77.1.32)
  by debian.novare.net with SMTP; 25 Jun 1998 11:20:21 -
Received: from terreaux.ens-lyon.fr (terreaux [140.77.191.109]) by 
cri.ens-lyon.fr (8.8.5/8.8.1) with ESMTP id NAA21788 for <[EMAIL PROTECTED]>; 
Thu, 25 Jun 1998 13:20:09 +0200 (MET DST)
Received: from ens-lyon.fr (localhost [127.0.0.1]) by terreaux.ens-lyon.fr 
(8.8.5/8.8.0) with ESMTP id NAA25886 for <[EMAIL PROTECTED]>; Thu, 25 Jun 1998 
13:20:06 +0200 (MET DST)
Sender: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 25 Jun 1998 13:20:04 +0200
From: Sebastien Chaumat <[EMAIL PROTECTED]>
X-Mailer: Mozilla 4.03 [en] (X11; I; SunOS 5.5.1 sun4m)
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: Danger in using autoup.sh
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

 From my own experience: when upgrading to hamm using autoupsh with the
package in a local directory : the local directory should ONLY contain
packages from hamm. 

 e.g : if there's the package libreadline from bo-unstable, autoup.sh
gets confused and try a downgrade to this package. 

 It happened to me last night. I worked it out by manualy restoring the
initial state of my libreadline packages.

 Proposed fix: 
  

 1: print a warning before checking for hamm packages in the local
directory. (e.g: CAUTION: there should NOT be ANY package from other
distribution of debian (bo, bo-unstable) in the local directory (where
you store hamm packages for the update).

 2: optional : check for bo packages in the local directory and
refuse to update while they are there.


I hope this is the right place for this message.

I hope it may help.

Sebastien Chaumat
---
Received: (at 23883-done) by bugs.debian.org; 26 Mar 2000 09:48:47 +
Received: (qmail 1456 invoked from network); 26 Mar 2000 09:48:47 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:48:47 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 56A604045; Sun, 26 Mar 2000 11:48:44 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:48:44 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Closing old bug reports related to bo->hamm transition
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

Evrything in the subject. Those bugs are no more of actuality.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Bug#28170: marked as done (2.0: upgrade/cd_autoup.sh fails to find libraries)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:48:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing old bug reports related to bo->hamm transition
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 19 Oct 1998 03:09:48 +
Received: (qmail 6168 invoked from network); 19 Oct 1998 03:09:45 -
Received: from unknown (HELO karakondjul.prikazka.com) ([EMAIL PROTECTED])
  by master.debian.org with SMTP; 19 Oct 1998 03:09:45 -
Received: (from [EMAIL PROTECTED])
by karakondjul.prikazka.com (8.8.8/8.8.8/Debian/GNU) id XAA02632;
Sun, 18 Oct 1998 23:05:39 -0400
Date: Sun, 18 Oct 1998 23:05:39 -0400
Message-Id: <[EMAIL PROTECTED]>
From: Shu <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: 2.0: upgrade/cd_autoup.sh fails to find libraries


Package: n/a (upgrade script)
Version: 2.0

Tried to run upgrade/cd_autoup.sh from the binary CD to upgarde 1.3
system. Got this:

 cut here 
[shu:/cdrom/upgrade] sh ./cd_autoup.sh 
ldso_1.9.9-1.deb libc5_5.4.38-1.1.deb libc6_2.0.7t-1.deb timezones_2.0.7t-1.deb 
locales_2.0.7t-1.deb ncurses3.0_1.9.9e-2.1.deb ncurses3.4_1.9.9g-8.8.deb 
libreadline2_2.1-10.1.deb libreadlineg2_2.1-10.1.deb bash_2.01.1-3.1.deb 
libg++27_2.7.2.1-14.4.deb libg++272_2.7.2.8-0.1.deb libstdc++2.8_*.deb 
Can't find ../debian/hamm/hamm/binary-i386/libs/libstdc++2.8_*.deb!
aborting upgrade.
[shu:/cdrom/upgrade] 
 cut here 

Copied the script to writable place and made these changes to make it
work:

 cut here 
[shu:~/upgrade] diff cd_autoup.sh /cdrom/upgrade/cd_autoup.sh 
62c62
<  base/libstdc++2.8_*.deb"
---
>  libs/libstdc++2.8_*.deb"
68c68
< PKGS_MOREDPKG="interpreters/data-dumper_*.deb base/libnet-perl_*.deb \
---
> PKGS_MOREDPKG="interpreters/data-dumper_*.deb interpreters/libnet-perl_*.deb \
78c78
< DM=/cdrom/debian/hamm/hamm/$ARCH
---
> DM=../debian/hamm/hamm/$ARCH
[shu:~/upgrade] 
 cut here 
---
Received: (at 28170-done) by bugs.debian.org; 26 Mar 2000 09:48:47 +
Received: (qmail 1456 invoked from network); 26 Mar 2000 09:48:47 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:48:47 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 56A604045; Sun, 26 Mar 2000 11:48:44 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:48:44 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Closing old bug reports related to bo->hamm transition
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

Evrything in the subject. Those bugs are no more of actuality.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Re: Anyone's able to run 2.3.99-pre*?

[kimo_sabe]

On Sun, Mar 26, 2000 at 10:35:02AM +0200, Michael Meskes wrote:
> e2fscheck always tells me it cannot read the superblock. Up to 2.3.4? it
> worked well. And of course 2.2.14 runs without a problem.
  Do you have an IDE ZIP drive?  I believe I had the same problem starting
around 2.3.43.  The problem is related to having an uninitialized ATA ZIP
drive around(on the same chain, maybe) as your harddrive.  modprobing
ide-floppy was enough to work around the problem.  I added ide-floppy to my
/etc/modules and it hasn't bothered me since.  I don't know if this was ever
fixed.
  - Nick Lopez
[EMAIL PROTECTED]

ITP: xastir

[Hamish Moffatt]

As discussed on the debian-hams list, I am packaging xastir.
Xastir is an X client for APRS, the Automatic Position Reporting System.

In APRS, objects (houses, cars, people or whatever) report their position
on the air. (Usually their position is obtained using GPS for mobile
objects, or entered by hand for fixed objects.) Xastir collects the
information off the air and displays it on top of a map.

Section: hamradio. License: GPL. Uses LessTif.

More ITPs of ham stuff to follow.

Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Re: RBL report..

[Jason Henry Parker]

Nils Jeppe <[EMAIL PROTECTED]> writes:

> And taking people off the list is automatic. Fix it, enter the IP in their
> form, it gets re-cehcekd and taken off the list. Works like a charm.

My recent experience with ORBS backs this up.

> If people configured their servers correctly, they'd never get on the
> list. ;-) Also, ORBS allows for I think 3-5 days warning in advance, which
> is sufficient to fix a server.

postmaster at a host I co-admin got mail from ORBS a few days before
Christmas of 1999.  We were given four weeks to fix our open relay,
plenty of logs and a reasonable amount of help from the ORBS website
on how to fix it.  The only difficult part was finding how to upgrade
our mailserver!

Having been on the nasty end of the ORBS stick, I still give it a
thumbs-up.

jason
-- 
   
\ _/__ ``I need every braincell blazing
 \X  /   to fight my invisible enemies!''
   \/  

Re: RBL report..

[Joseph Carter]

On Sun, Mar 26, 2000 at 11:15:42AM +0200, Nils Jeppe wrote:
> > ORBS has a tendancy to not take the time to make sure their messages go to
> > the right places and then they are very slow to take sites off the list
> > after problems are fixed.
> 
> afaik, ORBS sends to [EMAIL PROTECTED] What other right place could there
> be?

The domain's technical contact.


> And taking people off the list is automatic. Fix it, enter the IP in their
> form, it gets re-cehcekd and taken off the list. Works like a charm.

Uh, I can find at least one site real quickly whose admin will tell you
that he got a message from ORBS, fixed the problem, was blacklisted
anyway, and it took him a month to get off that list even though the
problem was fixed days before they blacklisted him.


> > ie, to them making sure spam never happens is more important than what
> > damage they cause in hte process.  I rate them in with the DUL.
> 
> If people configured their servers correctly, they'd never get on the
> list. ;-) Also, ORBS allows for I think 3-5 days warning in advance, which
> is sufficient to fix a server.

Given every report I've heard to the contrary, I'm not sure I believe
that.  I've also been told that there are cases where their tests produce
false positives.

-- 
Joseph Carter <[EMAIL PROTECTED]>   GnuPG key 1024D/DCF9DAB3
Debian GNU/Linux (http://www.debian.org/) 20F6 2261 F185 7A3E 79FC
The QuakeForge Project (http://quakeforge.net/)   44F9 8FF7 D7A3 DCF9 DAB3

 it's too bad most old unices turned out y2k compliant
 because it means people will STILL BE RUNNING THEM in 30 years
   =p
 it would have been so much nicer if y2k effectively killed off
   hpux, aix, sunos, etc  ;>
 Knghtbrd: since when are PH-UX, aches, and solartus "old"?

Re: Idea: Debian Developer Information Center

[Peter Makholm]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> Hey people ! I posted this mail in order to have some input ... it would
> be great if some of you gave their opinion about this proposition I posted
> a while ago :

Just like everyone else: A great idea to which I have no futher idears
right now.

If I wasn't to afraid to sound to AOLish I would have posted a "good
idea" to the first post.

-- 
A chameleon imitating a mail daemon often delivers scrolls of fire. 

Re: RBL report..

[Hamish Moffatt]

On Sun, Mar 26, 2000 at 02:41:09AM -0800, Joseph Carter wrote:
> The domain's technical contact.

Ideally, yes. In practice, I'd say that's no more likely to work
than [EMAIL PROTECTED] I've seen NIC entries with technical contacts
called "NOC Administrator <[EMAIL PROTECTED]>"; do you think hotmail
addresses should be acceptable for domain contacts? I don't but apparently
Network Solutions don't mind.


Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Bug#32888: marked as done (base: Removing "Obsolete" package base kills a system)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 11:59:12 +0200
with message-id <[EMAIL PROTECTED]>
and subject line base mess
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 4 Feb 1999 18:58:47 +
Received: (qmail 31359 invoked from network); 4 Feb 1999 18:58:47 -
Received: from mueata-e1-wan053.citykom.de (HELO khms.westfalen.de) ([EMAIL 
PROTECTED])
  by master.debian.org with SMTP; 4 Feb 1999 18:58:47 -
Received: from kai by khms.westfalen.de with local (Exim 2.05 #1)
id 108Tz9-KY-00 (Debian); Thu, 4 Feb 1999 19:58:43 +0100
From:  <[EMAIL PROTECTED]>
Subject: base: Removing "Obsolete" package base kills a system
To: [EMAIL PROTECTED]
X-Mailer: bug 3.1.7
Message-Id: <[EMAIL PROTECTED]>
Date: Thu, 4 Feb 1999 19:58:43 +0100

Package: base
Version: N/A
Severity: critical

I've said this for a long time. Now I've actually seen it happen.

When the old "base" package was replaced by "base-files" and friends, we
left a disaster waiting to happen: the old "base" package would remain,
containing those files not migrated to the newer packages. I have no
exact list, but it definitely includes *all* the basic devices.

Dselect will now list "base" as "Obsolete or local". This encourages
people to remove it.

If they remove base, they will lose most of their devices, rendering the
system practically unusable (and only fixable for experienced *nix people
if you realize what happens as long as you still have a root shell).

If you need more details how this actually happened, mail Jutta Wrage
<[EMAIL PROTECTED]>.

Fix Proposal: have base-files or similar zero out /var/lib/dpkg/info/base.list.

-- System Information
Debian Release: 2.1
Kernel Version: Linux khms.westfalen.de 2.0.36 #2 Thu Dec 31 17:38:15 CET 1998 
i486 unknown

---
Received: (at 32888-done) by bugs.debian.org; 26 Mar 2000 09:59:14 +
Received: (qmail 6060 invoked from network); 26 Mar 2000 09:59:13 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 09:59:13 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 541994045; Sun, 26 Mar 2000 11:59:12 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 11:59:12 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: base mess
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

The base package doesn't exist any more for quite a long time, those first
time Debian user are most of them quite good and knows what to do to
correct this problem. Furthermore for those who can't, they simply have
to not remove the base package (which is guaranteed by its essential
flag)...  this bug deserves no more to be open.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Re: RBL report..

[Miquel van Smoorenburg]

In article <[EMAIL PROTECTED]>,
Joseph Carter  <[EMAIL PROTECTED]> wrote:
>Uh, I can find at least one site real quickly whose admin will tell you
>that he got a message from ORBS, fixed the problem, was blacklisted
>anyway, and it took him a month to get off that list even though the
>problem was fixed days before they blacklisted him.

I can find several sites who swear they fixed their relaying problem
properly when in fact they didn't. Especially multi-server relaying
is a concept that is hard to grasp for quite a few admins

Mike.
-- 
Windows never had any potential for soundness or beauty. If you decide to
build a motorcycle, and you start with a bathtub, no good will ever come of it. 
-- Anonymous Coward

Re: Bug#32888: marked as done (base: Removing "Obsolete" package base kills a system)

[Hamish Moffatt]

On Sun, Mar 26, 2000 at 11:03:27AM -, Debian Bug Tracking System wrote:
> The base package doesn't exist any more for quite a long time, those first
> time Debian user are most of them quite good and knows what to do to
> correct this problem. Furthermore for those who can't, they simply have
> to not remove the base package (which is guaranteed by its essential
> flag)...  this bug deserves no more to be open.

I think we are closing bugs for the sake of it here. Any reason
why the suggestion can't be implemented? (ie make base-files.postinst
truncate base.list). OK it's not a very nice solution but there isn't
a better one. I personally have nuked the base package and lost all
my devices this way.


Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Bug#42795: marked as done (Need mechanism to detect unmaintained packages)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 14:42:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Mechanism for detecting unmaintained packages
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 10 Aug 1999 15:15:09 +
Received: (qmail 26921 invoked from network); 10 Aug 1999 15:15:08 -
Received: from mailimailo.univ-rennes1.fr (129.20.128.39)
  by master.debian.org with SMTP; 10 Aug 1999 15:15:08 -
Received: from medicis2.univ-rennes1.fr (IDENT:[EMAIL PROTECTED] [129.20.24.29])
  by mailimailo.univ-rennes1.fr (8.9.3/jtpda-5.3.1) with ESMTP id 
RAA05456
  for <[EMAIL PROTECTED]>; Tue, 10 Aug 1999 17:15:07 +0200 (MET DST)
Received: (from [EMAIL PROTECTED])
by medicis2.univ-rennes1.fr (8.9.3/8.8.7) id RAA20337;
Tue, 10 Aug 1999 17:13:11 +0200
Date: Tue, 10 Aug 1999 17:13:11 +0200
Message-Id: <[EMAIL PROTECTED]>
X-Authentication-Warning: medicis2.univ-rennes1.fr: otto set sender to [EMAIL 
PROTECTED] using -f
From: "Ottavio G. Rizzo" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: manpages-it

Hello,

I suppose this is to report a bug on your bug reporting mechanism...

I'm the maintainer (the real one, not the Debian one) of the Italian
translations of the man-pages. I found out by mere chance (I'm not a
Debian user) that you have an internal bug reporting system where
users report bugs on the packages. 

The problem is, my package is unmaintained (the last deb package dates
back to four releases --- almost two years --- ago), so Debian users
who are reporting bugs related to the manpages to bugs.debian, and are
not getting any answer, may think poorly of the group of people who
are working hard on translating manpages: clearly this is
unacceptable.

Therefore I suggest that, if a package does not get updated in a
reasonable time, all bug reports get forwarded to the real
maintainer. Of course the idea that a user will report a bug in the
package (as opposed to a bug in the packaging) to the distribution
packager and not to the real responsible is completely idiotic, but
who am I to say that?

Ottavio
-- 
Ottavio Rizzo, PhD  Coordinatore del progetto di traduzione 
[EMAIL PROTECTED]   in italiano delle manpagine di Linux
http://www.pluto.linux.it/ildp/projects/man/index.html

---
Received: (at 42795-done) by bugs.debian.org; 26 Mar 2000 12:42:54 +
Received: (qmail 28948 invoked from network); 26 Mar 2000 12:42:53 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 12:42:53 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 5A3C04045; Sun, 26 Mar 2000 14:42:50 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 14:42:50 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Mechanism for detecting unmaintained packages
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

Hi,

people who wish to do this kind of work already can (and I encourage them
to do so), they can use the lintian reports (with the error/warning
called ancient-standard-version) and then post to debian-qa asking us to
take over the package after having tried to contact the maintainer. Or
they can check the changelog to see the date of the last upload ... this
is already done by a little script (written by Joey Hess) and you
can see the result here (the list is quite long :-() :
http://master.debian.org/~hertzog/non-maintained-packages.txt

I'm also setting up the qa.debian.org virtual package in the BTS which
may be used by our users to report this kind of problem (maintainer MIA,
package out of date, ...). I'll try to publicize this but I don't know yet
where and how. Anyway, this bug can be closed.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Bug#32888: marked as done (base: Removing "Obsolete" package base kills a system)

[Raphael Hertzog]

Le Sun, Mar 26, 2000 at 09:39:09PM +1000, Hamish Moffatt écrivait:
> I think we are closing bugs for the sake of it here. Any reason
> why the suggestion can't be implemented? (ie make base-files.postinst

Yes, because Santiago Vila doesn't want it and because it looks like
a crude hack. If you really think that it must be done, reopen the bug and
assign it to base-files... but it has no reason to exist against
the "general" package.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Re: RBL report..

[Mark Brown]

On Sun, Mar 26, 2000 at 11:05:40AM +0200, Nils Jeppe wrote:

> ORBS blocks all open relays. A lot of people have open relays. Since open
> relays still do not have any reason for existence other than admin
> ignorance, the "correct" way here would be to block all open relays and

ORBS also blacklist sites for other reasons, such as if their probes are
firewalled out.  This will, for example, catch sites that automatically
firewall out sites that attempt to relay through them - the site notices
the first check, blocks the rest and gets added to the list.

-- 
Mark Brown  mailto:[EMAIL PROTECTED]   (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/


pgph7wmXnQhuf.pgp
Description: PGP signature

GOB

[Robert Graham Merkel]

There has been some discussion about packaging GOB on the lists.

I have made some test packages which should be available from:

http://www.cs.mu.oz.au/~rgmerk/software

If they are OK and a developer is prepared to sponsor me I'd love
to have the packages added to the distribution.

-- 
---
Robert Merkel   [EMAIL PROTECTED]

What a strange game.  The only winning move is not to play.
-- WOP, "War Games"
---

Bug#49962: marked as done (Debian FSS-upgrade process: man pages)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 15:17:26 +0200
with message-id <[EMAIL PROTECTED]>
and subject line FHS man pages not found by the old man-db
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 12 Nov 1999 09:15:50 +
Received: (qmail 1739 invoked from network); 12 Nov 1999 09:15:49 -
Received: from cephyr.cid.net (HELO mail.cid.net) ([EMAIL PROTECTED])
  by master.debian.org with SMTP; 12 Nov 1999 09:15:49 -
Received: from cephyr.cid.net (lifenet-online.cid.net) [195.35.45.193] (mail)
by mail.cid.net (Exim 2.11) with esmtp
id 11mCoE-0001Ha-00; Fri, 12 Nov 1999 10:15:54 +0100
Received: from 62.158.230.214 for [EMAIL PROTECTED]
by lifenet-online.cid.net (Exim 2.11) with esmtp
id 11mCoD-0001HL-00; Fri, 12 Nov 1999 10:15:53 +0100
Received: (from [EMAIL PROTECTED])
by p3E9EE6D6.dip0.t-ipconnect.de 
(8.9.3+3.2W/8.9.3/Debian/GNU/angepasst) id KAA02196;
Fri, 12 Nov 1999 10:15:45 +0100
Message-ID: <[EMAIL PROTECTED]>
Date: Fri, 12 Nov 1999 10:15:30 +0100
From: =?iso-8859-1?Q?Andreas_Kr=FCger?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Debian FSS-upgrade process: man pages
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93i
X-Debian-CC: Fabrizio Polacco <[EMAIL PROTECTED]>

Package: general

In short:

A reasonably new version of "man-db" should be required on
my system automatically, through Debian package dependencies,
whenever I install any Debian package that has FSS man pages.


The full story:

I started with a slink Debian-i386 system.  I upgrade
packages one at a time to potato, as I see fit.  I never
leave package dependencies dangling.  Other than that, I
still have many slink packages around.  (My internet
connection is charged by the minute.)

It happened repeatedly to me that I upgraded to a new
package and couldn't read the manual page.  FSS strices
again.  I can always fix that by setting MANPATH to
something appropiate with "share" in it.

I'm sure there has been a version of the man-programs
(package man-db) around for some time that can read
FSS-compliant man pages all right.  Otherwise, you package
maintainers would have long ago addressed the problem.


Here is my wish of the Debian system:

A reasonably new version of "man-db" should be required on
my system automatically, through Debian package
dependencies, whenever I install any Debian package that has
FSS man pages.


I ask Fabrizio, the man-db maintainer, to kindly provide the
version number of man-db that should be used in a package
dependency for this purpose. (The current version seems to
be "2.3.10-69s", so maybe that's the answer.)  Or any other
input on this he sees fit.  Thank you.


Maybe someone should construct a Perl script or something that:
+ Parses through the various
  .../debian/dists/unstable/Contents*.gz files,
+ catches any package that has share/man - files,
+ cross check whether such a package mentions any man-db -
  version in its dependency requirements (or is man-db itself),
+ file a bug against any that doesn't, and
+ remember enough state so that the process can be repeated
  later without resending that same bug report to packages
  that have already received it.

Maybe there's an even smarter way to handle this in the
Debian scheme of things.

Maybe this has helped you.  I certainly hope so.

Keep up the good work!

Andreas

[EMAIL PROTECTED]

==

bash-2.02$ dpkg -l man-db
Desired=Unknown/Install/Remove/Purge
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ NameVersionDescription
+++-===-==-
ii  man-db  2.3.10-68  Display the on-line manual.

bash-2.02$ env | grep MAN
# No output

bash-2.02$ manpath
/usr/man:/usr/X11R6/man:/usr/local/man

bash-2.02$ apt-cache showpkg man-db
Package: man-db
Versions: 
2.3.10-69s(/var/state/apt/lists/source.rfc822.org_pub_mirror_ftp.debian.org_debian_dists_unstable_main_binary-i386_Packages),2.3.10-68(/var/lib/dpkg/status),
Reverse Depends: 
  libc6-dev,man-db
  manpages-fr,man-db
  libc6-dev,man-db
  boot-floppies,man-db
  2utf,man-db
Dependencies: 
2.3.10-69s - groff (0 (null)) libc6 (2 2.1) bsdmainutils (0 (null)) man (0 
(null)) man (0 (null)) nlsutils (0 (null)) 
2.3.10-68 - groff (0 (null)) libc6 (0 (n

Bug#51558: marked as done (debconf: arch query)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 15:22:44 +0200
with message-id <[EMAIL PROTECTED]>
and subject line bug never reassigned
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 29 Nov 1999 19:56:24 +
Received: (qmail 28190 invoked from network); 29 Nov 1999 19:56:08 -
Received: from sunu450.rz.ruhr-uni-bochum.de (134.147.64.5)
  by master.debian.org with SMTP; 29 Nov 1999 19:56:08 -
Received: (qmail 1897 invoked from network); 29 Nov 1999 19:56:09 -
Received: from magma.alg.ruhr-uni-bochum.de ([EMAIL PROTECTED])
  by mailhost.rz.ruhr-uni-bochum.de with SMTP; 29 Nov 1999 19:56:09 -
Received: from marcus by magma.alg.ruhr-uni-bochum.de with local (Exim 3.03 #1 
(Debian))
id 11sWu6-0001Rb-00; Mon, 29 Nov 1999 20:56:06 +0100
From: Marcus Brinkmann <[EMAIL PROTECTED]>
Subject: debconf: arch query
To: [EMAIL PROTECTED]
X-Mailer: bug 3.2.6
Message-Id: <[EMAIL PROTECTED]>
Date: Mon, 29 Nov 1999 20:56:06 +0100

Package: debconf
Version: 0.2.7
Severity: normal

Hi Joey,

Please don't use dpkg --print-architecture, it is not defined and will
lead to wrong results (on the Hurd for example). Use dpkg
--print-installation-architecture, which is what you really want.

(I found this in a generated /tmp/ file).

Thanks,
Marcus


-- System Information
Debian Release: potato
Kernel Version: Linux magma 2.2.12 #1 Thu Oct 14 09:29:24 EST 1999 i586 unknown

Versions of the packages debconf depends on:
ii  data-dumper 2.10-2 Store and retrieve perl data structures
perlNot installed or no info
ii  perl-5.004  5.004.05-3 Larry Wall's Practical Extracting and Report
^^^ (Provides virtual package perl5)
---
Received: (at 51558-done) by bugs.debian.org; 26 Mar 2000 13:22:51 +
Received: (qmail 14343 invoked from network); 26 Mar 2000 13:22:51 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 13:22:51 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id C37E64045; Sun, 26 Mar 2000 15:22:44 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 15:22:44 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: bug never reassigned
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

Hi,

this bug is about files in /tmp that contain some bad invocation.
Unfortunetaly the content of those files is not available in the BTS.
The bug had to be reassigned to the good package, but Marcus never did it
and we can't guess what he was talking about.

So i'm closing this bug, but marcus, if you manage to find the packages
that generated those files, feel free to reopen the bug and reassign it 
to the good package (or simply fill in a new bugreport).

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Re: RBL report..

[Nils Jeppe]

On Sun, 26 Mar 2000, Mark Brown wrote:

> ORBS also blacklist sites for other reasons, such as if their probes are
> firewalled out.  This will, for example, catch sites that automatically
> firewall out sites that attempt to relay through them - the site notices
> the first check, blocks the rest and gets added to the list.

Well I didn't know that, however, that's a pretty redundant thing to do -
afterall, you can just disable relaying alltogether and be done with
it. ;-)



-- 
 "Kif, if there's one thing I don't need it's your 'I don't think that's
  wise' attitude."
--- Zap Brannigan

Re: RBL report..

[Nils Jeppe]

On Sun, 26 Mar 2000, Joseph Carter wrote:

> > afaik, ORBS sends to [EMAIL PROTECTED] What other right place could there
> > be?
> 
> The domain's technical contact.

Might be a good idea to do this in addition to [EMAIL PROTECTED], but I
fail to see where this is "better" - Most domains have quite nonsensical
"hostmaster" tech-c's.


> Uh, I can find at least one site real quickly whose admin will tell you
> that he got a message from ORBS, fixed the problem, was blacklisted
> anyway, and it took him a month to get off that list even though the
> problem was fixed days before they blacklisted him.

Yeah well they probably did NOT fix the problem, then.


> Given every report I've heard to the contrary, I'm not sure I believe
> that.  I've also been told that there are cases where their tests produce
> false positives.

I don't see how you can create a false positive on a relay test. Either
the message gets through, and you're an open relay, or it doesn't, and
you're fine. It's quite simple, really.



-- 
 "Kif, if there's one thing I don't need it's your 'I don't think that's
  wise' attitude."
--- Zap Brannigan

Re: Signing Packages.gz

[Marcus Brinkmann]

On Sun, Mar 26, 2000 at 09:00:34AM +1000, Anthony Towns wrote:
> The whole file --- verifying each entry would take at least three minutes
> on my hardware, and god knows how long on anything moderately old or
> outdated. I certainly wouldn't want to try it on m68k on a regular basis,
> eg. (If doing something just once takes a second; doing it 4000 times
> takes a bit over an hour)

I don't think it is useful to sign the Packages file, because:
 
> Whose key should be used? Probably a special one just for dinstall,
> that's kept fairly securely by the Novare and -admin folks, and revoked
> regularly.

Any such key would have to be considered insecure, no matter how soon you
revoke it. So the paranoid people still don't trust it, and the other don't
care (probably).
 
> There doesn't really seem a huge amount of choice here, to me.

Packages should come with their *.changes file, and dpkg should have an
option to verify the signature of individual packages. There was some
discussion about this in the past. The trick is that security should be
implemented in dpkg(-dev), not somewhere else. This has the advantage that
it works also with individual packages you don't get from an archive source.
It cuold also be used to verify the origin of the package.

Thanks,
Marcus

-- 
`Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server 
Marcus Brinkmann  GNUhttp://www.gnu.orgfor public PGP Key 
[EMAIL PROTECTED], [EMAIL PROTECTED]PGP Key ID 36E7CD09
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/   [EMAIL PROTECTED]

Re: RBL report..

[Nils Jeppe]

On 26 Mar 2000, Jason Henry Parker wrote:

> postmaster at a host I co-admin got mail from ORBS a few days before
> Christmas of 1999.  We were given four weeks to fix our open relay,
> plenty of logs and a reasonable amount of help from the ORBS website
> on how to fix it.  The only difficult part was finding how to upgrade
> our mailserver!

Four weeks? Did they change this? When we got blacklisted coz a customer
(open relay) used us as a smart host, they gave us four days ;-).

> Having been on the nasty end of the ORBS stick, I still give it a
> thumbs-up.

Yeah, me too. They're competent, cool people, and their system works in
almost totally eleminating spam, unlike the other RBLs out there.

Plus, they're not a "blackhole". We had one case where an upstream
provider used one of those to block IP traffic - to Real.Com. Now
that's overkill. But blocking mail traffic from open relays is perfectly
acceptable.



-- 
 "Kif, if there's one thing I don't need it's your 'I don't think that's
  wise' attitude."
--- Zap Brannigan

Re: blue on black is unreadable

[Wouter Hanegraaff]

On Sun, Mar 26, 2000 at 10:11:57AM +1000, Anthony Towns wrote:
> On Sun, Mar 26, 2000 at 12:54:39AM +0100, Wouter Hanegraaff wrote:
> > Why does debian have to be different than the rest of the world in
> > everything? Why do I get colors when I set TERM=xterm? there was already
> > xterm-color and xterm-debian which could do colors.
> 
> Other Linux distributions tend to default to a colour xterm, I thought.

I thought slackware defaults to a non color xterm, and solaris too.
And debian slink too, which is my main problem: Why is this setting
changed between slink and potato??

> So why don't you just change your local settings to make xterm be mono?
> Ummm. `XTerm*ColorMode: no' seems like it'd do what you want.

That seems to work just fine. I wish I was aware of that resource a bit
earlier...

Wouter

Re: RBL report..

[Joseph Carter]

On Sun, Mar 26, 2000 at 04:00:54PM +0200, Nils Jeppe wrote:
> > Given every report I've heard to the contrary, I'm not sure I believe
> > that.  I've also been told that there are cases where their tests produce
> > false positives.
> 
> I don't see how you can create a false positive on a relay test. Either
> the message gets through, and you're an open relay, or it doesn't, and
> you're fine. It's quite simple, really.

Or it appears to have been accepted and goes nowhere.  I've seen a setup
or two like this specifically for the purposes of tracking who was trying
to use the relay...

ie, one rabid anti-spam group blacklisted another because their methods
happened to conflict.  It's rather amusing to say the least.
Unfortunately, it demonstrates that ORBS is a little more indiscriminant
than perhaps is good.

-- 
Joseph Carter <[EMAIL PROTECTED]>   GnuPG key 1024D/DCF9DAB3
Debian GNU/Linux (http://www.debian.org/) 20F6 2261 F185 7A3E 79FC
The QuakeForge Project (http://quakeforge.net/)   44F9 8FF7 D7A3 DCF9 DAB3

 It's a trackball for one
 so it's not a rodent
 it's a turd with a ball sticking out
 which you fondle constantly

Re: RBL report..

[Nils Jeppe]

On Sun, 26 Mar 2000, Joseph Carter wrote:

> Or it appears to have been accepted and goes nowhere.  I've seen a setup
> or two like this specifically for the purposes of tracking who was trying
> to use the relay...

Just check your reject log for ip adresses ;-)

If someone has some weird setup like that they can blame no-one but
themselves. ;)

Besides, as a deliberate setup, this is probably the exception.



> Unfortunately, it demonstrates that ORBS is a little more indiscriminant
> than perhaps is good.

Yes; because innocent people do get caught in the middle of it. But it's
the only method to fight open relays. I've said it before and I'll say it
again, there is no reason for relays to be open. Just because half the
admins out there are too incompetent to take care of their mail servers
doesn't justify why the rest of the net has to wade through floods of spam
;-)

When I have to chose between using ORBS or sorting out 20-30 spams a day,
I'll happily use ORBS. The innocent people getting caught should change to
an ISP who has competent admins, or bug their ISP to fix the problem
already.





Nils


-- 
 "Kif, if there's one thing I don't need it's your 'I don't think that's
  wise' attitude."
--- Zap Brannigan

Re: GOB

[Raphael Hertzog]

Le Mon, Mar 27, 2000 at 12:12:26AM +1000, Robert Graham Merkel écrivait:
> There has been some discussion about packaging GOB on the lists.
> 
> I have made some test packages which should be available from:
> 
> http://www.cs.mu.oz.au/~rgmerk/software
> 
> If they are OK and a developer is prepared to sponsor me I'd love
> to have the packages added to the distribution.

Sorry, but gob is already sitting in Incoming, here's what I see :

Format: 1.6
Date: Tue, 21 Mar 2000 19:56:29 +
Source: gob
Binary: gob
Architecture: source i386
Version: 0.93.0-1
Distribution: unstable
Urgency: low
Maintainer: Mark Brown <[EMAIL PROTECTED]>
Description: 
 gob- GTK+ Object Builder
Changes: 
 gob (0.93.0-1) unstable; urgency=low
 .
   * Initial Release

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Bash and Letter E

[Rodrigo Castro]

Hello

Sorry for asking again about my problem but I can't make my
letter E work in bash (neither in console nor xterm). See what
happens:

- "E" is treated like a dead key. It is not showed at first time, but
when you press another key after "E", it beeps

- "E" works in other programs and shells (ksh, csh and so on), so it
is not a hardware 

- I booted with another kernel (in case one from RedHat 6.1 CD) and it
didn't work

- I booted with init option (linux init=/bin/bash) in order to run no
init script and it didn't work either. I also tried D option (linux
D).

- I tried another keyboard and no success

- I reinstalled libc6, libncurses5 and base-files

- I installed older and newer versions of bash and libc6

- I created a new user with no /etc/input, no ~/.inputrc, no
~/.bash(rc|_profile) and even so it didn't work

I am running out of ideas. I am almost getting bash source code,
compiling with debug option and running gdb!! Anyone have an idea? 

PS: Could you send a copy to my email address? I am not a subscriber
of debian-devel nor debian-user

[]'s
-- 
Rodrigo Castro   <[EMAIL PROTECTED]>
Computer Science undergraduate student - University of Sao Paulo

I do not fear computers.  I fear the lack of them.
-- Isaac Asimov

Re: RBL report..

[Henrique M Holschuh]

On Sun, 26 Mar 2000, Joseph Carter wrote:
> On Sun, Mar 26, 2000 at 04:00:54PM +0200, Nils Jeppe wrote:
> > > Given every report I've heard to the contrary, I'm not sure I believe
> > > that.  I've also been told that there are cases where their tests produce
> > > false positives.

This used to be true. The new tests won't false-positive anymore.

> > I don't see how you can create a false positive on a relay test. Either
> > the message gets through, and you're an open relay, or it doesn't, and
> > you're fine. It's quite simple, really.
> 
> Or it appears to have been accepted and goes nowhere.  I've seen a setup
> or two like this specifically for the purposes of tracking who was trying
> to use the relay...

The failure in a test is now triggered (AFAIK) by the _receipt_ of the probe
message in the _target_ address. This allows for no false-positives by the
test suite.

ORBS is the only thing which is capable of keeping the spam low enough to be
acceptable in my home account :-( It doesn't help that spammers have
haversted the debian BTS (either the WWW pages or the ML, I don't know) for
addresses to spam, either.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh 

Re: GOB

[Mark Brown]

On Mon, Mar 27, 2000 at 12:12:26AM +1000, Robert Graham Merkel wrote:
> There has been some discussion about packaging GOB on the lists.

> If they are OK and a developer is prepared to sponsor me I'd love
> to have the packages added to the distribution.

I already uploaded a package to Incoming.  However, I'm not particularly
attached to it (I only packaged it because I need it to build another
package) so you're welcome to take it.

-- 
Mark Brown  mailto:[EMAIL PROTECTED]   (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/


pgplqg2KScvyE.pgp
Description: PGP signature

Re: RBL report..

[Joseph Carter]

On Sun, Mar 26, 2000 at 04:34:37PM +0200, Nils Jeppe wrote:
> > Unfortunately, it demonstrates that ORBS is a little more indiscriminant
> > than perhaps is good.
> 
> Yes; because innocent people do get caught in the middle of it. But it's
> the only method to fight open relays. I've said it before and I'll say it
> again, there is no reason for relays to be open. Just because half the
> admins out there are too incompetent to take care of their mail servers
> doesn't justify why the rest of the net has to wade through floods of spam
> ;-)

The point exactly..  If RBL or RSS blacklists someone, it's a known
spammer or a site which has refused to act against spammers abusing their
systems.  In these instances, the blacklisting happens as a last resort.

DUL and ORBS both seem to think they need to punish anyone whose config
or origin does not meet their standards (or as someone else noted in the
case of ORBS, if they are unable to test you..)


There are those who believe such far-reaching pre-emptive strikes against
spammers are warranted.  I'm not one of them.  I believe DUL and ORBS are
only making the problems worse by resorting to "fighting dirty" without
regard for the innocent users.

These people are typified by Craig Sanders who has said on many occasions
now in several forums that people who don't like or are hurt by such
blacklists should simply get a better ISP---as if a lot of people even had
a choice!  Can't make an omelette without breaking some eggs right?  That
sort of uncaring attitude shows exactly how unethical that view (and IMO
the people who hold it) are.

-- 
Joseph Carter <[EMAIL PROTECTED]>   GnuPG key 1024D/DCF9DAB3
Debian GNU/Linux (http://www.debian.org/) 20F6 2261 F185 7A3E 79FC
The QuakeForge Project (http://quakeforge.net/)   44F9 8FF7 D7A3 DCF9 DAB3

!netgod:*! time flies when youre using linux
!doogie:*! yeah, infinite loops in 5 seconds.
!Teknix:*! has anyone re-tested that with 2.2.x ?
!netgod:*! yeah, 4 seconds now

Bug#52748: marked as done (Potato debs using new chmod/rmdir options should depend on new fileutils)

[Debian Bug Tracking System]

Your message dated Sun, 26 Mar 2000 16:57:10 +0200
with message-id <[EMAIL PROTECTED]>
and subject line rmdir --ignore-... and chmod --reference
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 15 Dec 1999 03:32:58 +
Received: (qmail 25984 invoked from network); 15 Dec 1999 03:32:57 -
Received: from mail.vif.com (HELO jasmine.vif.com) (207.219.108.153)
  by master.debian.org with SMTP; 15 Dec 1999 03:32:57 -
Received: from Phi (ip:[216.13.61.129]) by jasmine.vif.com
 (Sendmail Unix Vr92.1.6) with ESMTP id <[EMAIL PROTECTED]>;
 Tue, 14 Dec 1999 22:33:30 -0500
Received: (from [EMAIL PROTECTED])
by Phi (8.9.3/8.9.3/Debian 8.9.3-6) id WAA02832;
Tue, 14 Dec 1999 22:31:14 GMT
Message-Id: <[EMAIL PROTECTED]>
From: Keith <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Potato debs using new chmod/rmdir options should depend on new 
fileutils
X-Reportbug-Version: 0.46
X-Mailer: reportbug 0.46
Date: Tue, 14 Dec 1999 22:31:13 +

Package: general
Version: N/A; reported 1999-12-14
Severity: normal



-- System Information
Debian Release: potato
Architecture: i386
Kernel: Linux Phi 2.2.10 #1 Mon Nov 15 06:21:18 /etc/localtime 1999 i586


Partially upgrading from Slink to unstable, I found some packages which used 
new options of rmdir and chmod in their postinst scripts, but didn't depend on 
a recent version of fileutils.deb

This can stop the scripts and thus an upgrade if the user doesn't manually 
upgrade his fileutils.deb

I don't know how many packages are concerned, but since most people playing 
with unstable probably have completly unstable installation, this problem could 
stay hidden for some time if maintainers don't check themselves their scripts.

For the record, I've had problems with the --ignore-fail-on-non-empty option of 
rmdir, and chmod --reference, which were not there in fileutils 3.16 (the Slink 
version).

Have a nice day,
Keith


---
Received: (at 52748-done) by bugs.debian.org; 26 Mar 2000 14:57:14 +
Received: (qmail 16079 invoked from network); 26 Mar 2000 14:57:13 -
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) 
(134.214.164.9)
  by master.debian.org with SMTP; 26 Mar 2000 14:57:13 -
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
id 43E9C4045; Sun, 26 Mar 2000 16:57:10 +0200 (CEST)
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Mar 2000 16:57:10 +0200
From: Raphael Hertzog <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: rmdir --ignore-... and chmod --reference
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i

Hi,

I scanned the lintian laboratory to look for things like that and I
checked each package concerned. I submitted a bug against typespeed and 
mailed Manoj Srivastava because he has many packages potentially
concerned. Other packages already had the good dependency (like debconf).

So I'm closing this bug now.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com 

Re: RBL report..

[Nils Jeppe]

On Sun, 26 Mar 2000, Joseph Carter wrote:

> The point exactly..  If RBL or RSS blacklists someone, it's a known
> spammer or a site which has refused to act against spammers abusing their
> systems.  In these instances, the blacklisting happens as a last resort.

But you can't keep up with the amount of spam out there.

> DUL and ORBS both seem to think they need to punish anyone whose config
> or origin does not meet their standards (or as someone else noted in the
> case of ORBS, if they are unable to test you..)

I don't know anything about DUL. ORBS lists people who run open relays,
which is a known and real problem.


> There are those who believe such far-reaching pre-emptive strikes against
> spammers are warranted.  I'm not one of them.  I believe DUL and ORBS are
> only making the problems worse by resorting to "fighting dirty" without
> regard for the innocent users.

So don't use ORBS on your machines. As for fighting dirty, I think it
could also be argued that blocking relay-checks is "fighting dirty". By
having an open relay, these admins cause a great deal of damage. The
bandwidth that spam eats up alone every day must be immense, world wide.


> These people are typified by Craig Sanders who has said on many occasions
> now in several forums that people who don't like or are hurt by such
> blacklists should simply get a better ISP---as if a lot of people even had
> a choice!  Can't make an omelette without breaking some eggs right?  That
> sort of uncaring attitude shows exactly how unethical that view (and IMO
> the people who hold it) are.

I care a great deal, that's why I take a look at the greater picture. And
in the long run, everybody is better off if all relays are closed. 




-- 
 "Kif, if there's one thing I don't need it's your 'I don't think that's
  wise' attitude."
--- Zap Brannigan

Re: blue on black is unreadable

[Martijn van Oosterhout]

Wouter Hanegraaff wrote:
> 
> >  Oh crap, you're right.  I wasn't thinking on that one.  Oh well, I guess
> > somebody will have to find good colour combinations for every colour
> > package.
> 
> I can do that. Black on white. Proven to work
> perfectly for centuries. Or do you only read books with white letters on
> a black background, or all sorts of colors for differently styled
> text???

No, the difference is that computer monitors are fundamentally different
media from books. Books work by reflecting surrounding light, whereas
monitors emit the light themselves.

I think having xterms with black on white to be comparable to reading
a book in direct sunlight. It's not nice at all. I always read books
in the shade.

My xterms are all white on black. The exception is netscape which it
black on light-grey, because for some reason true-type fonts look
horrid the other way round.

-- 
Martijn van Oosterhout <[EMAIL PROTECTED]>

Re: New version of xserver-svga gives poorer display on laptop

[Konstantin Kivi]

On Fri, Mar 17, 2000 at 12:14:04PM +, Joseph Heenan wrote:
> In message <[EMAIL PROTECTED]>
>   "Oliver Elphick"  wrote:
> 
> > 
> > The nature of the problem is this:
> > There is a tendency for the image to be smeared to the right.  This is
> > particularly noticeable with the mouse cursor, which trails a small comet
> [snip]
> 
> I had /exactly/ this problem. I finally solved it by using xf86config
> to generate a new configuration file. It worked fine after that (and,
> not only that, but the display which was slightly flickerly with the
> previous version is now rock solid).
> 
> My laptop is a Clevo 98 rebadged by Novatech in the UK - think the
> screen is 12.1", it does 800x600 max, /proc/pci says the controller
> is a '"S3 Inc. ViRGE/MX+MV (rec 3).". I can send you my XF86Config if
> you think it might help.
> 
I also had to add
 Set_LCDClk  40
to the Device section. Be aware that parse-xf86config
used in /etc/init.d/xdm doesn't unserstand it

> Cheers,
> 
> Joseph
> 
> 
> -- 
> Joseph Heenan, Coventry, UK  http://www.ping.demon.co.uk/
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> 
> 

-- 
Sincerely yours, Konstantin Kivi <[EMAIL PROTECTED]>

Re: Idea: Debian Developer Information Center

[Petr Cech]

On Sat, Mar 25, 2000 at 09:51:50PM +0100 , Raphael Hertzog wrote:
> Le Thu, Mar 23, 2000 at 12:31:54AM +0100, Raphael Hertzog écrivait:
> > Hi dear co-developers,
> 
> Hey people ! I posted this mail in order to have some input ... it would
> be great if some of you gave their opinion about this proposition I posted
> a while ago :

OK

> > I think that we need a page (possibly a cgi or a page automatically updated
> > once a day) that would give the maximum of information concerning one
> > maintainer. This would include :
> > - information from the LDAP db (name, email, last seen on ...)
> > - information about the NMU policy that the maintainer has adopted
> >   (timeframe before a NMU is allowed, do i need an authorization to do a
> >   nmu ?, ...)

This is cool. Could it be added to db.d.o  right now?



[snip]

Petr Cech
--
Debian GNU/Linux maintainer - www.debian.{org,cz}
   [EMAIL PROTECTED]

Re: ITP John the ripper

[Matt Zimmerman]

On Sat, Mar 25, 2000 at 03:39:24PM +0100, Christian Kurz wrote:

> as jsut discussed on debian-devel, I would like to package John the
> Ripper. If someone already has done or is working on it, please mail me,
> then I will stop packing it. Otherwise I will try to upload this package
> till friday next week to woody.

I briefly looked into packaging this a while ago, and I couldn't find a license
in the distribution.  Are you aware of a license for this program, or have you
contacted the upstream author?

-- 
 - mdz

Re: RBL report..

[Craig Brozefsky]

Nils Jeppe <[EMAIL PROTECTED]> writes:

> On Sun, 26 Mar 2000, Mark Brown wrote:
> 
> > ORBS also blacklist sites for other reasons, such as if their probes are
> > firewalled out.  This will, for example, catch sites that automatically
> > firewall out sites that attempt to relay through them - the site notices
> > the first check, blocks the rest and gets added to the list.
> 
> Well I didn't know that, however, that's a pretty redundant thing to do -
> afterall, you can just disable relaying alltogether and be done with
> it. ;-)

It's just an illustration of the problems of attempting to enforce
your preferred policies upon others.

-- 
Craig Brozefsky  <[EMAIL PROTECTED]>
Free Scheme/Lisp Software  http://www.red-bean.com/~craig
"Hiding like thieves in the night from life, illusions of 
oasis making you look twice.   -- Mos Def and Talib Kweli

Re: RBL report..

[Nils Jeppe]

On 26 Mar 2000, Craig Brozefsky wrote:

> It's just an illustration of the problems of attempting to enforce
> your preferred policies upon others.

I'd call it self-defense, really.



-- 
 "Kif, if there's one thing I don't need it's your 'I don't think that's
  wise' attitude."
--- Zap Brannigan

ITP: cmatrix

[Edward Betts]

Package: cmatrix
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 76
Maintainer: Edward Betts <[EMAIL PROTECTED]>
Version: 1.0b-1
Depends: libc6 (>= 2.1), libncurses4 (>= 4.2-3.1), xbase-clients (>= 
3.3.3.1-5), kbd-compat | kbd
Description: Console Matrix simulates the display from "The Matrix"
 It is based on the screensaver from the movie's website. It works with
 terminal settings up to 132x300 and can scroll lines all at the same rate
 or asynchronously and at a user-defined speed.

GPL.

-- 
while :;do read x;echo \?;done


pgpb4DxThH1h0.pgp
Description: PGP signature

Re: ITP: cmatrix

[David Starner]

On Sun, Mar 26, 2000 at 05:32:13PM +0100, Edward Betts wrote:

Did this message mess with GnuPG on any one else's system?
I had to kill gpg (1.0.1-2) to get mutt to continue, and then
I got 
[-- PGP output follows --]
...
Good signature from ...
...
gpg: waiting for lock (hold by 829 - probably dead) ...
gpg: waiting for lock (hold by 829 - probably dead) ...
gpg: waiting for lock (hold by 829 - probably dead) ...
gpg: waiting for lock (hold by 829 - probably dead) ...
gpg: waiting for lock (hold by 829 - probably dead) ...
gpg: waiting for lock (hold by 829 - probably dead) ...
[-- End of PGP output --]

GnuPG bug or local configuration problem?

-- 
David Starner - [EMAIL PROTECTED]
Only a nerd would worry about wrong parentheses with
square brackets. But that's what mathematicians are.
   -- Dr. Burchard, math professor at OSU

Re: ITP: cmatrix

[David Starner]

On Sun, Mar 26, 2000 at 11:08:10AM -0600, David Starner wrote:
> On Sun, Mar 26, 2000 at 05:32:13PM +0100, Edward Betts wrote:
> 
> Did this message mess with GnuPG on any one else's system?
> I had to kill gpg (1.0.1-2) to get mutt to continue, and then
> I got 
> [-- PGP output follows --]
> ...
> Good signature from ...
> ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> [-- End of PGP output --]
> 
> GnuPG bug or local configuration problem?

Okay, sorry. I looked in the bug list, but didn't get down
to the wishlist bugs. 

(FYI: it's caused by GnuPG being killed and leaving a lock file
in ~/.gnupg. Do rm ~/.gnupg/*.lock to fix it. Considering that
gpg can check that there is no process 829 as well as I can,
why doesn't it deal with it?)

-- 
David Starner - [EMAIL PROTECTED]
Only a nerd would worry about wrong parentheses with
square brackets. But that's what mathematicians are.
   -- Dr. Burchard, math professor at OSU

Re: ITP: cmatrix

[Edward Betts]

David Starner <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 26, 2000 at 05:32:13PM +0100, Edward Betts wrote:
> 
> Did this message mess with GnuPG on any one else's system?
> I had to kill gpg (1.0.1-2) to get mutt to continue, and then
> I got 
> [-- PGP output follows --]
> ...
> Good signature from ...
> ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> gpg: waiting for lock (hold by 829 - probably dead) ...
> [-- End of PGP output --]
> 
> GnuPG bug or local configuration problem?

Works fine on my machine, I have version 1.0.1-2 installed.

-- 
while :;do read x;echo \?;done

Re: ITP: cmatrix

[Edward Betts]

Edward Betts <[EMAIL PROTECTED]> wrote:
> Package: cmatrix
> Status: install ok installed
> Priority: optional
> Section: misc
> Installed-Size: 76
> Maintainer: Edward Betts <[EMAIL PROTECTED]>
> Version: 1.0b-1
> Depends: libc6 (>= 2.1), libncurses4 (>= 4.2-3.1), xbase-clients (>= 
> 3.3.3.1-5), kbd-compat | kbd

Sorry, I relise the versions are a bit out of date, I built the packages ages
ago. I would rebuild before an upload.

-- 
while :;do read x;echo \?;done

Re: [dickey@clark.net: Re: http://cgi.debian.org/cgi-bin/bugreport.cgi?bug=59191]

[Fabien Ninoles]

On Mon, Mar 20, 2000 at 07:56:07PM +0100, Raphael Hertzog wrote:
> Le Mon, Mar 20, 2000 at 03:38:34PM +0100, Santiago Vila écrivait:
> > Perhaps we should open the Bug System to upstream maintainers by adding a
> > flag to every package. If this flag is on, reports are automatically
> > forwarded to a given upstream email address. I'm sure many upstream
> > authors would ask this flag to be enabled for their packages, even if this
> > means a small percentage of received bugs happen to be packaging bugs
> > which would not have to be forwarded in normal circumstances.
> 
> I can't believe it, usually I don't agree with you but here I do ! That's a
> pretty good idea. I'm sure that for most of the packages, there aren't
> that much Debian specific bugs and since the author can choose I don't see
> a reason not to implement it. Even better anybody should be able to
> register himself in the BTS so that he'll get all the bugreports for
> a specific package (or source package, but that's something more difficult
> to implement I guess) ... this would allow several maintainer to maintain
> the same package without using an alias or a list. 

Following a specific bug request and/or a specific package is always a
feature I would like to see in the BTS. Currently, the only way to follow
a bug already mentions on the BTS is to make a new bug report and merge it
to the old. Having the possibilities to add someone to a specific bug
reply will make it possible to form a bug test team for all people who
has the same bug, and will greatly help to follow specific policy amendment
(and futurely QA tasks ;) without necessarely being subscribe to the
specific mailing lists.

> 
> Adding to this the possibility to have architecture specific bugs, and
> distribution specific bugs, and we'll have the best BTS around the world.
> Ok, who does it ? ;-)

We should at least report it has a wish list against debbugs. Hmm...
it's already done by Lars (bug# 34071) and has more than a year already
(03-03-1999). Seems the idea wasn't that original ;)

> 
> Cheers,
> -- 
> Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
>  CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
>   Formations Linux et logiciels libres : http://www.logidee.com 
> 

-- 

Fabien NinolesChevalier servant de la Dame Catherine des Rosiers
aka Corbeau aka le Veneur Gris   Debian GNU/Linux maintainer
E-mail:[EMAIL PROTECTED]
WebPage:http://www.tzone.org/~fabien
RSA PGP KEY [E3723845]: 1C C1 4F A6 EE E5 4D 99  4F 80 2D 2D 1F 85 C1 70

Re: RBL report..

[Steve Robbins]

On Sun, 26 Mar 2000, Michael Neuffer wrote:

> * Jason Gunthorpe ([EMAIL PROTECTED]) [000326 08:45]:
> >[...]
> >ORBS - 314
> >   Comparing connections it is found that 3970 out of 40236 connection
> >   attempts would have been blocked. This can be roughly considered to be
> >   3970 emails blocked.
> >[...] 
> > ORBS deserves special mention because of their insane hit count, I don't
> > know what that is about but ORBS would block 10% of the mails we get. I
> > think it is without question that the majority of those blocks are
> > legitimate mails. ORBS is also almost completely inclusive of the RSS and
> > RBL.
> 
> ORBS has a slightly different (broader and maybe better) goal then the 
> the others. It actively scans the net for open mail relays,

This is misleading.  What ORBS does is *test* mail servers to ensure that
it *is* an open relay, before adding the relay's address to the list.

They do NOT (according to the web page) "scan the net" for open relays.  
Rather, the list is generated solely from reports (via web or email) from
folks that have been spammed.

> warns 
> the operators of these machines multiple times with exact descriptions 
> of what they are doing, trying to accomplish (ie closing open mail relays)
> which problems have been found, how to fix them (plus necessary pointers
> to other sites) and how to get of the list. Only then the machine is added 
> to the list.

However, if a relay remains in their list for some time (I forget how
long, but it's on the order of a month or two), the address is moved on to
a public list of open relays.  Presumably, the spammers know about this
list, so the probability of being used as a spam relay increases immensely
as time goes on.

-Steve

Re: ITP John the ripper

[Josip Rodin]

On Sun, Mar 26, 2000 at 11:15:20AM -0500, Matt Zimmerman wrote:
> > as jsut discussed on debian-devel, I would like to package John the
> > Ripper. If someone already has done or is working on it, please mail me,
> > then I will stop packing it. Otherwise I will try to upload this package
> > till friday next week to woody.
> 
> I briefly looked into packaging this a while ago, and I couldn't find a 
> license
> in the distribution.  Are you aware of a license for this program, or have you
> contacted the upstream author?

A friend of mine asked Solar Designer, and he said it's GPL or something...

-- 
Digital Electronic Being Intended for Assassination and Nullification

Re: New version of xserver-svga gives poorer display on laptop

[Branden Robinson]

On Sun, Mar 26, 2000 at 06:05:43PM +0400, Konstantin Kivi wrote:
> I also had to add
>  Set_LCDClk  40
> to the Device section. Be aware that parse-xf86config
> used in /etc/init.d/xdm doesn't unserstand it

Be aware that because of problems like this, parse-xf86config has been
eliminated from recent XFree86 packages.  Potato will ship without it.

-- 
G. Branden Robinson|Any man who does not realize that he is
Debian GNU/Linux   |half an animal is only half a man.
[EMAIL PROTECTED] |-- Thornton Wilder
roger.ecn.purdue.edu/~branden/ |


pgpDApaBdf5cd.pgp
Description: PGP signature

stuffit expander?

[Nils Jeppe]

Hello,

Is there any debian package (or in fact Unix tool at all) that allows
uncompression of Mac .sit (stuffit) archives?


Nils

-- 
 "Kif, if there's one thing I don't need it's your 'I don't think that's
  wise' attitude."
--- Zap Brannigan

Re: blue on black is unreadable

[Branden Robinson]

On Sun, Mar 26, 2000 at 12:54:39AM +0100, Wouter Hanegraaff wrote:
> >  Oh crap, you're right.  I wasn't thinking on that one.  Oh well, I guess
> > somebody will have to find good colour combinations for every colour
> > package.  
> 
> I can do that. Black on white. Proven to work
> perfectly for centuries. Or do you only read books with white letters on
> a black background, or all sorts of colors for differently styled
> text???

You betray profound ignorance.

The pages of books (most of them, anyway) do not emit their own light.
They are reflective only.  CRT's generate light.

If black-on-white xterms work fine for you, that's great.  It's YOUR system
and your choice.  But your rationale betrays little understanding of the
phsyiological/ergonomic issues involved.

> Is there a reason why xterm defaults to color xterm? In slink it
> does, on potato it's changed all of a sudden.

The recent potato xterm packages change precious little from upstream
behavior.  You have a beef with it, take it up upstream.

> Why does debian have to be different than the rest of the world in
> everything? Why do I get colors when I set TERM=xterm? there was already
> xterm-color and xterm-debian which could do colors.

You get colors when TERM=xterm because upstream says so.  Any Linux
distribution with a brain in its head uses XFree86 xterm for its version of
xterm.  nxterm is a piece of shit.

If you want an X11R5-compatible xterm, use TERM=xterm-r5.

Read /usr/share/doc/xterm/README.Debian and
/usr/share/doc/xterm/xterm.faq.html for more information.

> Right now, I have to set my TERM to xterm-mono on potato to avoid
> fruitsalads in a handful of programs I use very often (Mutt, dselect,
> vim). That is very annoying, because it results in broken terminal
> settings when I login to *any* other system. Maybe I'm the only one who
> hates colors in xterms, but still. It should be possible to use xterms
> without colors in a normal way, and right now it isn't.

It is, you just haven't bothered to read any documentation on the subject.

> Please leave *personal* configuration to the *user*, and leave the system
> configuration to some reasonable, _very_ conservative defaults.

I agree with this statement but not the baggage you attach to it.

As far as I'm concerned, "conservative" means "upstream behavior."

If upstream changes, I'll track those changes unless there is a very good
reason not to (for instance, Debian policy).  You desire to keep
compatibility with a version of xterm that is ten years old is not a very
good reason to accomodate you in the Debian defaults.

Read that FAQ.  Features have been added to xterm by Thomas Dickey, but the
only changes that break compatibility have been bugfixes.  I'm sorry if
you've grown attached to some of X11R5's bugs.

Please keep replies out of my personal mailbox.  I read the lists.

-- 
G. Branden Robinson| Convictions are more dangerous enemies
Debian GNU/Linux   | of truth than lies.
[EMAIL PROTECTED] | -- Friedrich Nietzsche
roger.ecn.purdue.edu/~branden/ |


pgpjlhOWhE2Kx.pgp
Description: PGP signature

Re: blue on black is unreadable

[Branden Robinson]

On Sun, Mar 26, 2000 at 04:07:11PM +0200, Wouter Hanegraaff wrote:
> > So why don't you just change your local settings to make xterm be mono?
> > Ummm. `XTerm*ColorMode: no' seems like it'd do what you want.
> 
> That seems to work just fine. I wish I was aware of that resource a bit
> earlier...

Perhaps if you read the manpage before whining and bitching to this mailing
list, you'd spend less time being unhappy.

   colorMode (class ColorMode)
   Specifies whether or not recognition of ANSI  (ISO
   6429)  color  change  escape  sequences  should be
   enabled.  The default is ``true.''

-- 
G. Branden Robinson| Communism is just one step on the long
Debian GNU/Linux   | road from capitalism to capitalism.
[EMAIL PROTECTED] | -- Russian saying
roger.ecn.purdue.edu/~branden/ |


pgpqJWcVx3zVE.pgp
Description: PGP signature

Re: Bug#32888: marked as done (base: Removing "Obsolete" package base kills a system)

[Branden Robinson]

On Sun, Mar 26, 2000 at 02:53:30PM +0200, Raphael Hertzog wrote:
> Yes, because Santiago Vila doesn't want it and because it looks like
> a crude hack.

There is no correlation there.  Or if there is, it is a negative one.

-- 
G. Branden Robinson| If a man ate a pound of pasta and a
Debian GNU/Linux   | pound of antipasto, would they cancel
[EMAIL PROTECTED] | out, leaving him still hungry?
roger.ecn.purdue.edu/~branden/ | -- Scott Adams


pgpXMBuPkHWRe.pgp
Description: PGP signature

Re: ITP John the ripper

[Christian Kurz]

On 00-03-26 Josip Rodin wrote:
> On Sun, Mar 26, 2000 at 11:15:20AM -0500, Matt Zimmerman wrote:
> > > as jsut discussed on debian-devel, I would like to package John the
> > > Ripper. If someone already has done or is working on it, please mail me,
> > > then I will stop packing it. Otherwise I will try to upload this package
> > > till friday next week to woody.
> > 
> > I briefly looked into packaging this a while ago, and I couldn't find a 
> > license
> > in the distribution.  Are you aware of a license for this program, or have 
> > you
> > contacted the upstream author?

> A friend of mine asked Solar Designer, and he said it's GPL or something...

Well, I asked him to add a note to the package which describes the
license of the package. Hopefully I can convince him to do so, so that I
or somebody else are able to package it.

Ciao
 Christian
-- 
Debian Developer and Quality Assurance Committee Member
1024/26CC7853 31E6 A8CA 68FC 284F 7D16  63EC A9E6 67FF 26CC 7853


pgpTzLlSmhIAw.pgp
Description: PGP signature

Would you like to save 30% on your phone bills and...

[jeffallen]

To be removed from this mailing list immediately press reply and enter REMOVE 
on the subject line.

Would you like some information on saving 30% on your Phone bills each month 
and how to get up to 8% back each month on your Utilities including phone. This 
service works for both business and residential, domestic and international. 
Sign up is FREE

Reply with "MORE INFO" in the subject field

Re: RBL report..

[Jason Henry Parker]

Nils Jeppe <[EMAIL PROTECTED]> writes:

> Four weeks? Did they change this? When we got blacklisted coz a customer
> (open relay) used us as a smart host, they gave us four days ;-).

All I can report is my experience.  I got four weeks.

> Yeah, me too. They're competent, cool people, and their system works in
> almost totally eleminating spam, unlike the other RBLs out there.

I don't use ORBS, but I'd be happy to.  My experience with them showed
them to be quick to respond to requests, but at the same time
unyielding in their policy, no matter what (kind of like Star Trek,
really).

If I set up a mailhost again, I'll be running it past ORBS when I
think I have it ready to test for open relays; it looked to me as
though they had a very good suite of tests.

jason
-- 
   
\ _/__ ``I need every braincell blazing
 \X  /   to fight my invisible enemies!''
   \/  

Re: Bash and Letter E

[Samuel Tardieu]

| - I booted with init option (linux init=/bin/bash) in order to run no
| init script and it didn't work either. I also tried D option (linux
| D).

Assuming that your mail is serious requires a fair amount of work, but
I'll try anyway.

bash man page reports that /etc/profile is read first. What do you have
in it? I don't see how anything else could prevent your 'E' key from
working.

Re: RBL report..

[Jason Henry Parker]

Steve Robbins <[EMAIL PROTECTED]> writes:

> This is misleading.  What ORBS does is *test* mail servers to ensure that
> it *is* an open relay, before adding the relay's address to the list.
> 
> They do NOT (according to the web page) "scan the net" for open relays.  
> Rather, the list is generated solely from reports (via web or email) from
> folks that have been spammed.

While looking into the fact of the matter (which appears to be
correct), I found this idea on the orbs web-page:

} Admins may alternatively set their systems up to tag messages
} delivered from open servers as "possibly spam", or just log the
} connections. What any admin does is entirely up to that admin. If
} you've been blocked from delivering mail and given a pointer to this
} site please note: It is the decision of the administrator of the site
} which blocked you to disallow mail from open relays. Those open relays
} must comply with that admin's rules (not ours) in order to deliver
} mail to that site - we're just verifying to the admin whether a host
} is an open relay or not.

Would it be possible to insert an X-Header on email that looks
`suspiscious'?  That way no-one has to be cut out of sending mail
to the debian lists, and those who want to can score down, killfile or
whatever to their heart's content.

jason
-- 
   
\ _/__ ``I need every braincell blazing
 \X  /   to fight my invisible enemies!''
   \/  

Re: Bash and Letter E

[rodsc]

Hello,

On Sun, Mar 26, 2000 at 08:13:25AM -0800, David Benson wrote:
> I only have one debugging idea, but your problem sounds
> like no fun, so I hope this helps...
> 
> Try running ``strace bash'' to see whether the key-event
> is making it to bash.
> 
> If so, try other libreadline-based programs (eg gdb, ncftp).
> I blame readline prematurely here...

Look at the output (the error occurs with bash, ftp and gdb, these are the 
programs I tested with)

rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
read(0, "E", 1) = 1
^^^

Here I typed E.

read(0, "g", 1) = 1
^^^

It waits for another key. I typed g here

write(2, "\7", 1)   = 1
^

And it returns a beep, for every single program.

rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
read(0, "t", 1) = 1
write(2, "t", 1t)= 1
rt_sigprocmask(SIG_BLOCK, NULL, [], 8)  = 0
read(0, "T", 1) = 1
write(2, "T", 1T)= 1

And here is what happens with "normal" keys. Any other idea?

> Good Luck, and Happy Bug Hunting,
> Dave

Thank you very much, Dave, for your help.

PS: Please, send a carbon copy to me. I am not a subscriber from
debian-devel and debian-user lists.

[]'s
-- 
Rodrigo Castro   <[EMAIL PROTECTED]>
Computer Science undergraduate student - University of Sao Paulo

I do not fear computers.  I fear the lack of them.
-- Isaac Asimov

Re: Bash and Letter E

[Rodrigo Castro]

Hello,

On Sun, Mar 26, 2000 at 11:07:15PM +0200, Samuel Tardieu wrote:
> | - I booted with init option (linux init=/bin/bash) in order to run no
> | init script and it didn't work either. I also tried D option (linux
> | D).
> 
> Assuming that your mail is serious requires a fair amount of work, but
> I'll try anyway.
> 
> bash man page reports that /etc/profile is read first. What do you have
> in it? I don't see how anything else could prevent your 'E' key from
> working.

I found out that the problem is not only with bash, but it seems to be
with programs that use libreadline library like gdb or ftp. Anyway,
I'll copy it here and my /etc/inputrc goes next. I don't have any
.inputrc.

PROFILE
--
# /etc/profile: system-wide .profile file for bash(1).

PATH="$HOME/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/local/java/bin:/usr/games:."
PS1="\\$ "

export PATH PS1

umask 002

if [ "$SHELL" = "/usr/bin/tcsh" -o "$SHELL" = "/bin/csh" ]; then
  eval `dircolors -c`
else
  eval `dircolors -b`
fi
export LS_OPTIONS='-FN --color=auto -h'

export PAGER=less
export LESS="-MM -i"
export LESSCHARSET="latin1"
export LESSKEY="/etc/lesskey"
export LESSOPEN='|lesspipe "%s"'

export MOZILLA_HOME="/usr/local/netscape"

export INPUTRC="/etc/inputrc"

export CLASSPATH=.:/usr/local/jgl3.1.0/lib/jgl3.1.0.jar
--

INPUTRC
--
set meta-flag on
set convert-meta off
set output-meta on
set input-meta on

"\e[1~":beginning-of-line
"\e[3~":delete-char
"\e[4~":end-of-line
"\e[5~":beginning-of-history
"\e[6~":end-of-history
"\e[7~":beginning-of-line
"\e[8~":end-of-line
"\e[\C-@":beginning-of-line
"\e[A":previous-history
"\e[B":next-history
"\e[C":forward-char
"\e[D":backward-char
"\e[E":beginning-of-line
"\e[H":beginning-of-line
"\eOH":beginning-of-line
"\eOF":end-of-line
"\EOF":end-of-line
"\e[F":end-of-line
"\e[e":end-of-line
--


[]'s
-- 
Rodrigo Castro   <[EMAIL PROTECTED]>
Computer Science undergraduate student - University of Sao Paulo

I do not fear computers.  I fear the lack of them.
-- Isaac Asimov

Re: RBL report..

[Hamish Moffatt]

On Sun, Mar 26, 2000 at 04:00:54PM +0200, Nils Jeppe wrote:
> I don't see how you can create a false positive on a relay test. Either
> the message gets through, and you're an open relay, or it doesn't, and
> you're fine. It's quite simple, really.

Actually, I ran the relay test at abuse.net on two of my domains last
night. One of the tests results in an email being accepted but not
actually sent. It sends a message from your own domain to another address;
exim accepts those, but then they don't get sent.


Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Re: RBL report..

[Jason Henry Parker]

Hamish Moffatt <[EMAIL PROTECTED]> writes:

> On Sun, Mar 26, 2000 at 04:00:54PM +0200, Nils Jeppe wrote:
> > I don't see how you can create a false positive on a relay test. Either
> > the message gets through, and you're an open relay, or it doesn't, and
> > you're fine. It's quite simple, really.
> Actually, I ran the relay test at abuse.net on two of my domains last
> night. One of the tests results in an email being accepted but not
> actually sent. It sends a message from your own domain to another address;
> exim accepts those, but then they don't get sent.

Yes, and ORBS tests if the email gets sent or not.  Your point?

[It tries to relay some mail From some address A to another address B
and waits for the mail to arrive at B.  It's hard to see how this
could be any simpler.]

jason
-- 
   
\ _/__ ``I need every braincell blazing
 \X  /   to fight my invisible enemies!''
   \/  

Re: Signing Packages.gz

[Anthony Towns]

On Sun, Mar 26, 2000 at 04:02:20PM +0200, Marcus Brinkmann wrote:
> On Sun, Mar 26, 2000 at 09:00:34AM +1000, Anthony Towns wrote:
> > The whole file --- verifying each entry would take at least three minutes
> > on my hardware, and god knows how long on anything moderately old or
> > outdated. I certainly wouldn't want to try it on m68k on a regular basis,
> > eg. (If doing something just once takes a second; doing it 4000 times
> > takes a bit over an hour)
> I don't think it is useful to sign the Packages file, because:

A signature authenticates the source of a document. That's worthwhile,
since verifying the source of a Packages file lets you transitively
verify the source of all the packages in a distribution.

> > Whose key should be used? Probably a special one just for dinstall,
> > that's kept fairly securely by the Novare and -admin folks, and revoked
> > regularly.
> Any such key would have to be considered insecure, no matter how soon you
> revoke it. So the paranoid people still don't trust it, and the other don't
> care (probably).

Nonsense.

The only reason not to trust a key dinstall uses explicitly for signing
Packages is if you believe dinstall is compromised. If you believe that,
then you shouldn't be downloading .deb's *ever*, because you're immediately
running *untrusted* scripts as root on your systems.

If dinstall *isn't* compromised, it's still possible that your favourite
FTP site is, in which case all they need to do to compromise your machine
is replace a .deb with their own hacked version and let you download it.

Automatically signing things is less secure than manually signing things,
and you need to do some extra stuff to not have gaping security holes
when automatically signing things, but sometimes there isn't that much
of a choice. All this FUD about "no, no, we can't do that, it's not
secure!" is, well, just that. *Nothing* is absolutely `secure', some
things just have fewer or different exploits than others.

> > There doesn't really seem a huge amount of choice here, to me.
> Packages should come with their *.changes file, and dpkg should have an
> option to verify the signature of individual packages. There was some
> discussion about this in the past. The trick is that security should be
> implemented in dpkg(-dev), not somewhere else. This has the advantage that
> it works also with individual packages you don't get from an archive source.
> It cuold also be used to verify the origin of the package.

Note that this makes debian-keyring a more or less standard package. Note
that it requires you to trust everyone in that keyring with every aspect
of your system.

Note that this doesn't help with revoking signatures: if some idiot
decides that being a Debian maintainer should give him the right to 0wn
all the machines that use his package; then gets thrown out; he can still
use his key to sign packages that'll be happily installed by anyone with
an out of date debian-keyring. If he can gain control of an ftp mirror,
he can keep updating the debian-keyring.deb to include his key, and
keep "maintaining" any packages he likes. With a dinstall key, the only
way he can do this is if he's a member of the ftp team or debian-admin.

It also leads to something of a chicken-and-egg situation. It's much
easier to verify a *single* key than that every one of five-hundred of
the things is uncompromised. (It can be signed by previous versions of
itself, it can be widely published in Debian books, it can be signed by
the ftp team, etc)

Cheers,
aj

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG encrypted mail preferred.

 ``The thing is: trying to be too generic is EVIL. It's stupid, it 
results in slower code, and it results in more bugs.''
-- Linus Torvalds


pgpLmXIPb5ukR.pgp
Description: PGP signature

Re: Bash and Letter E

[Rodrigo Castro]

On Mon, Mar 27, 2000 at 01:11:17AM +0200, Antonio Fiol Bonnín wrote:
> I have no idea, but what does it do when you press your E key while in the
> middle of a command (while editing).
> 

I am afraid it has the same symptoms. :-(

PS: Please carbon copy messages to me.

[]'s
-- 
Rodrigo Castro   <[EMAIL PROTECTED]>
Computer Science undergraduate student - University of Sao Paulo

I do not fear computers.  I fear the lack of them.
-- Isaac Asimov

Re: RBL report..

[Craig Sanders]

On Sun, Mar 26, 2000 at 05:10:06PM +0200, Nils Jeppe wrote:
> On Sun, 26 Mar 2000, Joseph Carter wrote:
> > DUL and ORBS both seem to think they need to punish anyone whose config
> > or origin does not meet their standards (or as someone else noted in the
> > case of ORBS, if they are unable to test you..)
> 
> I don't know anything about DUL. 

that's OK, neither does Joseph.  As usual, he's shooting his mouth off
about stuff he couldn't even begin to comprehend.

craig

--
craig sanders

Re: Signing Packages.gz

[Robert Bihlmeyer]

Anthony Towns  writes:

> On Sat, Mar 25, 2000 at 11:03:11PM +0100, Robert Bihlmeyer wrote:
> > Do you want to sign each package entry, or the whole file?
> 
> The whole file --- verifying each entry would take at least three minutes
> on my hardware, and god knows how long on anything moderately old or
> outdated.

Verifying /one/ entry takes three minutes? On my 486 box (which I'd
call moderately outdated) verifying a 1024 bit DSS signature with GPG
takes under two seconds. (Or did you mean verifying all entries? See
below!)

> I certainly wouldn't want to try it on m68k on a regular basis,
> eg. (If doing something just once takes a second; doing it 4000 times
> takes a bit over an hour)

There is no need to check all of them - only those for packages that
are about to get installed. For reference: on said 80486 "apt-get
install gnupg" took over two minutes (without downloading). Adding two
seconds to that would be no problem, IMHO.

One thing to consider is that this would make the Package.gz file
noticeably bigger.

> Whose key should be used? Probably a special one just for dinstall,
> that's kept fairly securely by the Novare and -admin folks, and revoked
> regularly.

This key's security value would not be much above that of the debian
machines themselves. You'd get about the same security by a mirror of
master, that is administed by the same people (does this mirror
exist?).

Whose key should be used by entry-level signing? I assume that .debs
are created by an automated process with no user intervention.

-- 
Robbe

RFP: bidwatcher

[Bdale Garbee]

I've built a package of bidwatcher, which is a tool for users of eBay, that
assists in placing and monitoring bids.  I don't really want to maintain the
package, though, so I'm calling for a volunteer to package this for real and
upload it.  I'm happy to provide what I've done so far, but it's just a
dh_make in the root of the package source tree, and a few trivial edits to
the debian/* files.

The original author has abdicated, and a fork has occurred.  I'm currently
using the version from Wayne Schlitt <[EMAIL PROTECTED]>, which can be
found at http://www.midwestcs.com/bidwatcher/.  There is another version
at SourceForge, and the good news is the two folks didn't know they were
working in parallel, and have now agreed to work towards a merge using the
SourceForge site in the future.  The code is GPL'ed, and does not include
the extra wording needed for GPL'ed code linking with QT.  That needs to be
resolved before an upload.

Any takers?  

Bdale

Re: Idea: Debian Developer Information Center

[Raphael Hertzog]

Le Sun, Mar 26, 2000 at 06:10:36PM +0200, Petr Cech écrivait:
> This is cool. Could it be added to db.d.o  right now?

It could, but not right now since I've not yet started to 
work on this... I'll have some technical details to resolve.
I need access to the BTS, the LDAP database and probably the 
lintian lab (in order packages's information like standard-version
and last upload date)... 

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
 CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd
  Formations Linux et logiciels libres : http://www.logidee.com