Re: Excessive wait for DAM - something needs to be done

2003-07-23 Thread Sam Couter
Martin Michlmayr - Debian Project Leader <[EMAIL PROTECTED]> wrote:
> At the same time I observe that this thread has generated much hot
> air, but I didn't see any proposal of who could act as DPL.

Please post the selection criteria for acceptance to the position of DAM.

The response "If you don't know already, you don't qualify" is
unacceptable.
-- 
Sam "Eddie" Couter  |  mailto:[EMAIL PROTECTED]
Debian Developer|  mailto:[EMAIL PROTECTED]
|  jabber:[EMAIL PROTECTED]
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpKwZLHsBKiy.pgp
Description: PGP signature


Re: Python module for debconf

2002-04-10 Thread Sam Couter
Adam Heath <[EMAIL PROTECTED]> wrote:
> The byte compilation should be done when the package is built, not at runtime,
> not at install time.

That doesn't work for languages that change their bytecode spec with
each version of their interpreter, and don't maintain backwards
compatibility.
-- 
Sam "Eddie" Couter  |  mailto:[EMAIL PROTECTED]
Debian Developer|  mailto:[EMAIL PROTECTED]
|  jabber:[EMAIL PROTECTED]
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgp4eYS8k6h8u.pgp
Description: PGP signature


Re: Package metadata server

2002-04-07 Thread Sam Couter
Glenn McGrath <[EMAIL PROTECTED]> wrote:
> It could probably be done with HTTP, using cgi scripts (i dont know much
> about this), that way standard clients can be used to retrieve pieces of
> the Packages's file by putting the querry in the url.

And then you get the solution which has been mentioned before but not
commented on much:

Packages contains package names, versions and pointers (filenames) to
the rest of the package metadata.

I you want information about a particular package, download the file
containing the metadata for that package. Then you don't have to
download stuff you're not interested in, and you don't have to
re-download all the metadata for packages which haven't changed.
-- 
Sam "Eddie" Couter  |  mailto:[EMAIL PROTECTED]
Debian Developer|  mailto:[EMAIL PROTECTED]
|  jabber:[EMAIL PROTECTED]
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpkxPCqEPT3R.pgp
Description: PGP signature


Re: Appropriate? mutt/mailx requires mail-transport-agent

2002-01-07 Thread Sam Couter
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I'm working on a diskless workstation configuration where I don't want
> mailers running on each machine, though users may have access to the
> mail spool through nfs.  Is it appropriate for apt-get to coerce exim
> to be installed when I only need a reader?  Is this a problem about
> finding the smtp agent?

If you only want to send email from those workstations, and not receive
any, try the package named 'ssmtp'. It provides a /usr/sbin/sendmail
program to send mail, but doesn't run as a daemon and doesn't listen for
inbound mail. Very nice.
-- 
Sam "Eddie" Couter  |  mailto:[EMAIL PROTECTED] |  I need a short and
Internet Engineer   |  jabber:[EMAIL PROTECTED]  |  clever comment for
tSA Consulting  |  http://www.topic.com.au/|  my .signature file
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpoXvWdnrgbH.pgp
Description: PGP signature


Re: Bug#127252: -unstable compiled against the wrong libpng

2002-01-03 Thread Sam Couter
Ivan E. Moore II <[EMAIL PROTECTED]> wrote:
> 
> please tell me where I stated I would do the work for our users?

When you signed up as a Debian Developer.
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key ID:   DE89C75C,  available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpXD1o5yaum6.pgp
Description: PGP signature


Re: A language by any other name

2001-09-26 Thread Sam Couter
Bill Wohler <[EMAIL PROTECTED]> wrote:
>   Having the English think that British English is the lingua franca of
>   the computing world is the same as the French thinking that French
>   is the lingua franca of the world. It's only wishful thinking.

And how is that different to Americans thinking that American English is the
only language of the computing world? Pull your head out of your arse (not
your ass, that's a donkey) and take a good look around. The world is much
more than 50 states.

Get an atlas, have a look at how small the US is compared with the rest of
the world. Familiarise yourself with some geography if you're one of the 14
percent or so who can't point at the US on a world map.[1]

>   Therefore, without emotion and with a pragmatic hand to guide me, I
>   feel that English should be an alias for en_US.

s/without emotion/with typical American patriotism/
s/pragmatic/dogmatic/

So was your message supposed to be serious, or are you just trolling?

[1]: http://www.sciencedaily.com/print/1999/03/990301072238.htm
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key ID:   DE89C75C,  available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpjyKCzUaH3p.pgp
Description: PGP signature


Re: bind9-chroot (was: questions on ITP)

2001-09-25 Thread Sam Couter
On Tue, 25 Sep 2001, Christian Kurz wrote:
> But having a link from either the config-files in /etc/bind to $CHROOT
> or in the other direction, could be in my opinion a security risk.

Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
> Oh, how so?

Because the files accessed from within the chroot once it's broken are the
SAME FILES as on the real system.
Doesn't that kinda defeat the purpose of having a chroot?

> Get some sleep. Links from inside the chroot to outside do not work, unless
> the kernel is fucked up.

Hard links work fine.

> 
> NEVER. This is not some low-grade distribution where you can go around
> scattering configuration files all over the filesystem.  I will fight tooth
> and nail against such an atrocity.
> 

I agree wholeheartedly here.

I don't see what's so hard about rsync'ing the files from /etc to the
chroot in the init script each time the daemon is started.
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key ID:   DE89C75C,  available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpkbczBGVPDX.pgp
Description: PGP signature


Re: rfc1149

2001-05-03 Thread Sam Couter
Evan Prodromou <[EMAIL PROTECTED]> wrote:
> 
> Obviously, if doves were used, both pigeons and doves would have to
> provide the pseudo-package "avian-packet-carrier" and the installer
> package would need to update-alternatives as appropriate.


Pigeons *are* doves. What you think of as pigeons are probably rock doves.


Taxonomically, pigeons and doves are the same.
Both are members of the order Columbiformes, family Columbidae. The term dove
is generally used for smaller species with pointed tails. "Pigeon" refers to the
larger species with square or rounded tails.
http://www.comptons.com/encyclopedia/ARTICLES/0125/01443584_A.html

-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key ID:   DE89C75C,  available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpb87RO4CHS5.pgp
Description: PGP signature


Re: rfc1149

2001-05-03 Thread Sam Couter
Marcin Owsiany <[EMAIL PROTECTED]> wrote:
> 
> No need to create a section for them. Birds can sit on the tree
> directly.

But what about now that we have pools? Will they drown?
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key ID:   DE89C75C,  available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpMFsmgpwdhk.pgp
Description: PGP signature


Re: Proposing task-debian

2001-05-01 Thread Sam Couter
Matt Zimmerman <[EMAIL PROTECTED]> wrote:
> 
> debfoster does not do what I described, as you can see by its description.

I use it on my system for precisely that, only I don't limit it to just task
packages.

> How does this allow you to remove a task package in an intuitive way?  That
> is what this discussion was about.

debfoster task-foo
[ wait while task-foo and its dependencies are installed ]

debfoster task-foo-
[ wait while task-foo is removed ]

Debfoster then asks:
Do you want to keep libfoo1? [Y/n]
Do you want to keep foo? [Y/n]

Alternatively, you can remove task-foo however you like and then run debfoster
with no arguments to get the same result.

Isn't that the kind of thing you're after?
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key ID:   DE89C75C,  available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpRv2x47EHi5.pgp
Description: PGP signature


Re: Proposing task-debian

2001-05-01 Thread Sam Couter
Matt Zimmerman <[EMAIL PROTECTED]> wrote:
> 
> A cleaner implementation would be to create a simple program or script that
> would attempt to remove a given package and (recursively) all of its
> dependencies, skipping any that are depended upon by packages outside of the
> set of packages being manipulated.  So if you had installed
> task-x-window-system-core, then later installed xterm (which depends on 
> xlibs),
> you could run this hypothetical program on task-x-window-system-core, and
> remove all of the pieces of task-x-window-system-core that were not needed by
> other packages.
> 
> This would make a good python-apt script.

Yeah, and you could call it... Let's see... debfoster is a good name!

[EMAIL PROTECTED]:~$ apt-cache show debfoster
Package: debfoster
Priority: optional
Section: admin
Installed-Size: 80
Maintainer: Ivo Timmermans <[EMAIL PROTECTED]>
Architecture: i386
Version: 1.99+2.0pre8-2
Depends: libc6 (>= 2.2.2-2)
Recommends: apt
Filename: pool/main/d/debfoster/debfoster_1.99+2.0pre8-2_i386.deb
Size: 18488
MD5sum: 9889daf0211f8ebae701f71d45fc5790
Description: Install only wanted Debian packages
 debfoster is a wrapper program for apt and dpkg.  When first run, it
 will ask you which of the installed packages you want to keep
 installed.
 .
 After that, it maintains a list of packages that you want to have
 installed on your system.  It uses this list to detect packages that
 have been installed only because other packages depended on them.  If
 one of these dependencies changes, debfoster will take notice, and
 ask if you want to remove the old package.
 .
 This helps you to maintain a clean Debian install, without old
 (mainly library) packages lying around that aren't used any more.

-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key ID:   DE89C75C,  available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpNMW1p9LYBM.pgp
Description: PGP signature


Creeping featuritis (was: Re: tar -I incompatibility)

2001-01-09 Thread Sam Couter
Hamish Moffatt <[EMAIL PROTECTED]> wrote:
> 
> So, what's your point exactly?
> 
> I hope you never use apt-get, as that would certainly be
> something beyond bare bones.

No it's not. It does one thing (Advanced Package Management), and does it
fairly well. Just because the thing it does is a complex task doesn't mean
it's got creeping featuritis. If it tried to do more than just package
management, that would be a different story.
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgp7pr7N9pfVe.pgp
Description: PGP signature


Re: tar -I incompatibility

2001-01-08 Thread Sam Couter
Hamish Moffatt <[EMAIL PROTECTED]> wrote:
> 
> If we're expected to avoid any advanced features, why do the authors bother
> to implement them?

http://www.tuxedo.org/~esr/jargon/html/entry/creeping-featuritis.html
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgprsCIGsT2lB.pgp
Description: PGP signature


Re: tar -I incompatibility

2001-01-07 Thread Sam Couter
Martin Bialasinski <[EMAIL PROTECTED]> wrote:
> 
> So, as you can not assume any particular flag for bzip2 compression
> anyway, why should GNU tar change its bzip2 option to the one used by
> the solaris tar?

I'm not saying it *should* change the behaviour of the -I option.

I'm saying that if it does, it does. I just don't want to hear complaints
about a non-standard option suddenly behaving differently.
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpKlL7DukBG1.pgp
Description: PGP signature


Re: tar -I incompatibility

2001-01-07 Thread Sam Couter
Michael Stone <[EMAIL PROTECTED]> wrote:
> 
> Changing gnu tar to be compatible with one of many diverse proprietary
> implementations, for only one of several incompatible flags, is a
> rationalization rather than a justification.

I agree, but it's at least as good (maybe better) a reason as the reason for
adding -I in the first place. Yet people complain about it. Loudly and
annoyingly.

> Bzzt. The stable version of tar is basically unusable because it
> contains several known bugs and is unmaintained. Upstream maintainer
> recommended following the so-called unstable tree to address those known
> bugs.

I've been corrected several times on this comment. GNU tar is unstable
because that's what the author says to use, and stable is broken and
unmaintained. Similarly, the "unstable" version of GNU tar is in Debian
stable, and will break systems when people upgrade to the next stable.

I take the comment back, as I was in error.

> Most of the options in gtar are non-standard. Are you saying that users
> should rely on none of them?

Pretty much. It's always useful to know exactly which options you're using
are not going to work on many other systems, and to not form habits that
involve the use of those options.

The same argument is usually applied to programming: Don't use
platform-specific features unless you need to.

> See above, and lose the condescension. People who use multiple platforms
> should know better than to assume behavior of tar flags across
> implementations.

Sorry about the condescending tone. What I meant to get across is that
people who regularly use other systems won't be in the habit of using -I or
-z for that matter, and aren't likely to miss it.

You can probably assume that -c, -x, -f and -v behave the same across
implementations (modern implementations, anyway). That's about all, and
isn't that enough for everything you'd every want to do with tar?
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpYJgRGzXEuO.pgp
Description: PGP signature


Re: tar -I incompatibility

2001-01-07 Thread Sam Couter
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> 
>   Could you please name the other unices that behave identically
>  to solaris tar wrt the -I option? And which other unices even have
>  the -I option in tar?

My point is that the -I option *doesn't* mean "uncompress this file using
bzip2" for anything other than GNU tar. Now that it doesn't mean that for
GNU tar either, people are complaining. I think they probably shouldn't have
been using -I to start with, at least not as a matter of habit or in scripts
that might live for any decent length of time or have an application on any
non-GNU system.
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpSPYMGYDdy5.pgp
Description: PGP signature


Re: Solving the compression dilema when rsync-ing Debian versions

2001-01-07 Thread Sam Couter
Otto Wyss <[EMAIL PROTECTED]> wrote:
> 
> So why not solve the compression problem at the root? Why not try to
> change the compression in a way so it does produce a compressed result
> with the same (or similar) difference rate as the source? 

Are you going to hack at *every* different kind of file format that you
might ever want to rsync, to make it rsync friendly?

Surely it makes more sense to make rsync able to more efficiently deal with
different formats easily.
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpy7IsSTN3dq.pgp
Description: PGP signature


Re: tar -I incompatibility

2001-01-07 Thread Sam Couter
Goswin Brederlow <[EMAIL PROTECTED]> wrote:
> Just as linux-centric as the other way is solaris-centric.

Not true. There's the way GNU tar works, then there's the way every other
tar on the planet works (at least with respect to the -I option). GNU tar is
(used to be) the odd one out. Now you're saying that not behaving like the
odd man out is being Solaris-centric? I don't think so.

> 
> I like systems that don't change on a day to day basis. I don't want
> "ls *" to do "rm *" tomorrow just because some other unix does it and
> the author feels like it.
> 

I'm sure this has been said before, but:

Don't run unstable if you don't like stuff changing or breaking.

Unstable breaks stuff from time to time. It changes stuff more often than
that.

If options or behaviour changes from one update to the next, stiff bikkies.
Deal with it in your own quiet little way.

If that behaviour or option was non-standard to begin with, then think
yourself lucky that you had it working as long as you did.

> "tar -xIvvf file.tar.bz2" has been in use under linux for over a year
> by pretty much everybody. Even if the author never released it as
> stable, all linux distributions did it. I think that should count
> something. Enough to at least ease the transition.

Pretty much everybody? I'd say you could modify that statement to "pretty
much everybody who doesn't deal with non-Linux systems often". The
qualifier to that statement is very important.

Ask someone who's actually used a non-Linux UNIX or UNIX-like system to
explain it to you sometime.
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgp9IMxwRKa2j.pgp
Description: PGP signature


Re: package pool and big Packages.gz file

2001-01-06 Thread Sam Couter
Andrew Stribblehill <[EMAIL PROTECTED]> wrote:
> 
> Doesn't gzip have a --rsync option, or somesuch? Apparently Andrew
> Tridgell (Samba, Rsync) has a patch to do this, but I don't know
> whether he passed it onto the gzip maintainers.

I like the idea of having plugins for rsync to handle different kinds of
data. So the gzip plugin will decompress the data, and the rsync algorithm
can work on the decompressed data. Much better.

> (Apparently he's working on a --fuzzy flag for matching rsyncs
> between, say foo-1.0.deb and foo-1.1.deb. He says it should be
> called the --debian flag.)

A deb plugin would be better. :)
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpSUf10GUoEI.pgp
Description: PGP signature


Re: big Packages.gz file

2001-01-06 Thread Sam Couter
> On 2001-01-05, Brian May <[EMAIL PROTECTED]> wrote:
> > What do large packages have to do with the size of the index file,
> > Packages?

Andreas Fuchs <[EMAIL PROTECTED]> wrote:
> They waste one byte per multiple of 10 bytes of package size. (-;

You mean one byte per order of magnitude of package size. ;)

> Bad joke? So sue me.

Yes, very bad. I couldn't resist correcting, which makes me at least as bad.
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgpSGNJSoIRqT.pgp
Description: PGP signature


Re: tar -I incompatibility

2001-01-06 Thread Sam Couter
Goswin Brederlow <[EMAIL PROTECTED]> wrote:
> PS: Why not change the Solaris version to be compatible with the widely used 
> linux version? I'm sure there are more people and tools out there for linux 
> using -I then there are for solaris.

This is an incredibly Linux-centric point of view. You sound worse than the
BSD bigots.

There are many, many, many different unices that are *not* Linux. You can't
hope to change them all to be Just Like Linux (tm). You'll be lucky if any of
them follow Linux behaviour, rather than the other way around.

Hint: Adopt some cross-platform habits like:
"bzip2 -dc foo.tar.bz2 | tar xf -"

Not only will you then become more immune to changes in behaviour that was
non-standard to begin with, you'll also find adjustment to other systems a
lot easier.
-- 
Sam Couter  |   Internet Engineer   |   http://www.topic.com.au/
[EMAIL PROTECTED]|   tSA Consulting  |
OpenPGP key available on key servers
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C


pgppqfa3DzFYe.pgp
Description: PGP signature