Of course, this would mean that the system
> would no longer be crytographically safe in general, but it might
> still be safe for some class of files with a fixed structure, such
> as xz. And not every one would render a vulnerability public...
> So, it is safer not to accept garbage
that has been introduced recently in
> > utils-linux
>
> Or `really' from chiark-really (from chiark-utils).
Considering that util-linux is Priority: required while
chiark-really is Priority: extra I'd suggest that runuser would be
a more sensible recommendation. Still, I love t
> > [0]
> > http://www.freedesktop.org/wiki/Software/systemd/InterfaceStabilityPromise/
C/libc: Nothing will ever be deprecated/removed.
What's that you say? gets(3)?
Linux kernel: never removes/changes interfaces.
That's why it still has devfs. Oh
d the builders even accept packages that has an invalid
distribution specified (in the most recent changelog entry, that is)?
Filtering out "UNRELEASED" and packages with an empty changelog would
prevent at least some premature uploads.
Kind regards, David Weinehall
--
/) David Weineh
#x27;s
> dependency.
Most Debian systems aren't using sysvinit by active choice, but because
it was the default when they installed their machines, so this argument
doesn't really make sense.
Kind regards, David Weinehall
--
/) David Weinehall /) Rime on my window (\
//
refer the "new" GNOME, but
with all 3 buttons enabled + the workspace grid extension. The only
thing I don't like is that a feature I used a lot was removed from
Nautilus, but the flexibility of GNOME Shell doesn't really help
there...
Regar
On Mon, Aug 11, 2014 at 01:47:53PM -0400, Lennart Sorensen wrote:
> On Mon, Aug 11, 2014 at 07:42:41PM +0200, David Weinehall wrote:
> > Available in GNOME 3.
> >
> > Available in GNOME 3.
> >
> > Not enabled by default (if I remember correctly), but possible to
dow manager.
Kind regards, David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.d
half-full.
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.
ibuting half-empty CD-images?).
So, as long as GNOME fits on the first installation CD I see no reason
not to prefer it over XFCE.
Kind regards, David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.
o your system?
Kind regards, David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debia
-die" package?
Kind regards, David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists
On Sat, Jan 04, 2014 at 03:13:01AM +, Clint Adams wrote:
> On Wed, Jan 01, 2014 at 10:58:32AM +0100, David Weinehall wrote:
> > That's also why I *don't* use BSD-style licenses for software that
> > I write, but rather GPLv2 or LGPLv2.1.
>
> So if someone takes
On Tue, Dec 31, 2013 at 02:54:50PM +, Clint Adams wrote:
> On Sun, Dec 29, 2013 at 03:50:06AM +0100, David Weinehall wrote:
> > Apart from the termination clause, the GPLv2 is far more concise,
> > I don't see tivoization as a problem (it's the software I want to
On Sat, Dec 28, 2013 at 08:53:56PM +, Clint Adams wrote:
> On Sat, Dec 28, 2013 at 09:45:09AM +0100, David Weinehall wrote:
> > As one of the "GPL v2 only" proponents, I take affront. I choose to
> > license what little software I release as GPL v2 only because I do
ter) to (L)GPL v3 (or later) is, if anything, very antisocial,
since it locks out users of GPL v2 (only) software and forces the GPL v3
interpretation onto GPL v2 (or later) software.
But by all means, go on and punch me in the face...
Regards: David Weinehall
--
/) David Weinehall /) Rime o
as they were given themselves. Forking a project and
altering the license from GPLv2 to GPLv3 does *not* pass that test.
Kind regards, David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~ta
On Fri, Jul 05, 2013 at 01:08:27AM +0200, John Paul Adrian Glaubitz wrote:
> On 07/05/2013 12:58 AM, Jakub Wilk wrote:
> >* David Weinehall , 2013-07-04, 16:36:
> >>http://lkml.org/lkml/2006/1/25/273
> >
> >http://lkml.org/lkml/2006/1/30/100
>
> Could you be
cense the first
> time, it was v2 by then. Of crucial interest is when Linus changed from
> v2 or later to v2 only. And looking at the source code, e.g. 3.9.8, a
> very lot of files are still v2+, not v2 only. That's a very big
> difference.
http://lkml.org/lkml/2006
ktop system (by this I take it to mean that you're not
using a GUI), why would you worry about GNOME's dependencies anyhow?
If you're using a desktop system it doesn't feel like a stretch to use
functionality that fits in with the desktop system. And vice versa,
obviously.
Re
On Sat, Jun 01, 2013 at 03:39:44PM +0200, Salvo Tomaselli wrote:
> They release twice a week or so. That is another sign of a software you
> shouldn't rely on too much
You mean like, say, the Linux kernel?
Regards: David
--
/) David Weinehall /) Rime o
in special
cases, and leave /tmp primarily as a dumping ground for the user
(If it wasn't for NFS *shudder* I'd advocate /home//tmp for this
purpose instead).
Regards: DAvid
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white ros
is the unit file that gets updated, the file in /etc only
contains overrides for the values you want to override.
Thus, when /lib changes, those updates will be included, no breakage.
The only issue I can think of is that there's currently (TTBOMK) no way
of unsetting a value completely, wh
neither are you TTBOMK :)
> > And debian-policy isn't set in stone.
> > Otherwise it wouldn't have last been revised in February 2012 :)
> >
>
> The debian-policy maybe, but the FHS, and config files in /etc *is* a very
> strong policy that you will not chang
something isn't supported currently in our tools doesn't
make it impossible to support it. And debian-policy isn't set in stone.
Otherwise it wouldn't have last been revised in February 2012 :)
Regards, David Weinehall
--
/) David Weinehall /) Rime on my window (\
On Wed, May 09, 2012 at 03:47:21PM +0200, Gergely Nagy wrote:
> Tollef Fog Heen writes:
>
> > ]] Philipp Kern
> >
> >> You will not, however, get a conffile update prompt when the system
> >> file changes (e.g. to update your own local copy to incorporate the
> >> fix).
> >
> > This is something
matter who wins, the users lose :S And I don't blame the Debian
maintainers of either package. I think that the upstream for Node.js
should've done their homework a bit better though, and that the ax25
upstream should've had a bit more imagination. But shit happened
already.
Regard
region
> of emergency communications capability until the problem is resolved.
>
>
> Ironically one of the reasons many hams looked to Debian was the stability
> of the system and the ability to upgrade in place. Changing a core ham
> radio component throws those reasons o
w people seem to be violently agreeing so hard.
So, what you're saying is that we should fork udev to do things that
neither its upstream developer nor its Debian maintainer doesn't intend
for it to do, all to make it possible to use an init-system that doesn't
support eve
On Tue, Apr 03, 2012 at 09:55:19AM +1000, Peter Miller wrote:
> On Mon, 2012-04-02 at 19:39 +0200, David Weinehall wrote:
> > So, I'm curious here: why would you need a non-copyleft license for a
> > *test suite*?
>
> Consider the case where a legal department
is copyleft
doesn't mean that your C library has to be. The only thing it means is
that you'd have to release modifications to that compliance test suite
*if* you distribute the compliance test suite it to others.
Regards: David
--
/) David Weinehall /) Rime on my window (\
lways run it, since the user might choose to
uninstall systemd, or temporarily disable it, or... Well, you get the
idea.
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se
o solve all use cases that sysvinit can solve plus a lot
of things that it doesn't (or can't, by design).
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Be
nome settings as
> a "support issue" or "general usage".
No, you're right. Rants don't really belong on any of our lists...
Also, we're not upstream. Any issues that aren't Debian specific
should be filed in the upstream
tever what would be), the length of the init
scripts ranges from 8 to 653 lines, with the average being 115 lines.
I'd hardly call that short enough to be easy to debug.
Kind regards, David Weinehall
--
/) David Weinehall /) Rime on my window (\
// ~~
x27;t even been an option with sysvinit (socket activation being one
thing).
Regards, David Weinehall
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (
st. I don’t think there’s real use for a
> blacklist, it is too dangerous.
Wouldn't both be best? Let's say the whitelist contains all packages of
a certain category. The blacklist could then be used to make an
exception for a specific package within that category.
Rega
> options open.
I'd be very curious to hear what these serious and ongoing structural
problems are.
Kind regards: David Weinehall
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/
On Wed, Oct 05, 2011 at 07:01:11AM +0200, Guillem Jover wrote:
> On Tue, 2011-10-04 at 22:28:00 +0200, David Weinehall wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: David Weinehall
> >
> > * Package name: susv4
> > Version :
Package: wnpp
Severity: wishlist
Owner: David Weinehall
* Package name: susv4
Version : 7
Upstream Author : N/A
* URL : N/A
* License : Public Domain
Programming Lang: POSIX sh
Description : Fetch and install SUSv4 (POSIX.1:2008) documentation
The
x27;re
> in the SUS.
SuSv3 -- POSIX:2001
SuSv4 -- POSIX:2008
So if they're in SuS, they're specified by POSIX :)
While I've read the SuSv3 quite thoroughly, I have yet to study the
SuSv4, so I dunno how big the differences are, and if any of them are
important.
Regards: David
-
's just that libc touches a lot more components than
any other library does.
[snip]
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-fro
it on embedded devices makes a lot of sense.
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
--
To UNSUBSCRIBE, email to d
mitted by IT department policies,
etc.).
With all these flaws I still use NM. It works fairly well, but I curse
every time I do an upgrade and NM happens to be in the list of packages
that is upgraded.
[snip]
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~
sonably
enough, been told that gnome-panel 2.32 is probably what they really
want. Are there any plans to provide this package?
[snip]
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://ww
st breaking these very same builds.
If someone would ask me to choose between these two options, I'd start
looking around for the candid camera...
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\)
n experimental will be the correct one, the one in unstable
will be the crippled one. The reason things fails isn't because of
dash, but because of sloppy programming on behalf of people that still
believe that bash is the say all and end all when it comes to s
/
> restore test, I'll be good to go. Stay tuned ...
Perhaps you, with the experienced gained from your adventures with
extlinux, could help write some documentation?
Kind regards: David Weinehall
--
/) David Weinehall /) Rime on my window (\
// ~~~
ger being swapped out preemptively all the time. The
> > difference in perceived responsiveness is spectacular.
>
> You might also be interested in:
>
> # sync; cat 3 > /proc/sys/vm/drop_caches
That'd be
sync; echo 3 > /proc/sys/vm/drop_caches
Kind regards: David Weine
n a fully-working
> Debian system.
Last time I checked, /usr/bin is also part of default $PATH...
[snip]
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautif
NCY=makefile, to make it easier to switch with some confidence
> > that it would work for most users. :)
>
> Now you're talking! :)
Or we could do like with the net.ipv6.bindv6only setting, and just
change it and then ignore all complaints.
Regards: David
--
/)
d characters too,
at least the more uncommon ones (for instance, according to the above
statistics there's only one file with a double qute, so it'd make sense
to have it renamed, similarly for the 3 backslashes).
Regards: David
--
/) David Weinehall /) Rime on my window (\
/
On Sun, May 10, 2009 at 08:51:33AM -0300, Henrique de Moraes Holschuh wrote:
> On Fri, 08 May 2009, David Weinehall wrote:
> > > No. But we do leave /usr read-only the rest of the time, which
> > > is often 99.999% of the time. A separate /usr is required for t
ead-only while installing or
> > upgrading packages”. Thanks for providing another case in point.
>
> No. But we do leave /usr read-only the rest of the time, which
> is often 99.999% of the time. A separate /usr is required for this.
Uhm
> shortened. I'll send out a new CFV.
OK, does this mean that everyone who already cast their vote will need
to do so again, or will the voting period simply be extended another
week?
Regards: David
--
/) David Weinehall /) Rime on my window (\
// ~~
cannot access the WiFi, because their wireless cards
are not supported. Or rather, the drivers are available, but they all
report the same error message "Firmware not found". Happy, happy, joy,
joy. I'm sure those potential Debian users will feel really happy about
Debian's
s a part of the man-db package instead
might be an idea. lintian already depends on man-db, so the
dependencies wouldn't change, and it would also mean that linda can use
the same check without code duplication.
Regards: David
--
/) David Weinehall <[
the things which are written in this book.
Damn, I was just about to submit a bunch of bugfixes for the some of the
more blatantly obviously fuckups, such as the homophobia and misogynism.
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
//
list to download and run
binaries, I sugges you at least sign your email; providing sources would
be even better. Running unknown binaries isn't exactly recommended
practise =)
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~
>
> sorting-hat sorts Debian developers into the appropriate house
> (Griffindor, Ravenclaw, Hufflepuff or Slytherin).
That'd be Gryffindor...
[snip]
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ /
o do this here) the
> community might be the thing that keeps them here rather then some other
> project or FOSS in general.
They don't have to take it away from the Debian lists... They can always
discuss on debian-curiosa if they so desire. Just don't let the
off-topic discussi
ly
> > doubt that DSA will require uglyness to accept it.
>
> It was a joke. Adjust your view of reality, some people actually try to
> have fun from time to time.
Didn't your AM tell you? All Debian developers are required to be
impervious to humour, irony, puns, simile, or
ong thread on -legal.
Why? All these licenses are compatible. Depending on what the GPL-only
code is used for, the resulting library will either be GPL or LGPL.
Finding out which should be quite simple.
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window
ldd (and the
> buildd operator) very unhappy.
Well, wouldn't the best way be to require binaries to be uploaded,
and then discard them and rebuild the package anyway? This way the
maintainer has to build the package for his own machine at least,
and at the same time the package gets rebuild on
> I'm afraid the GNOME bugzilla can't handle that amount of bugs.
Yeah, I bet you have several hundred thousand pet features that was
removed (rather than replaced) in the transition from GNOME 1.4 to 2.0.
Yup. That's probably it.
Regards: David
--
/) David Weinehall <
On Sat, Jan 20, 2007 at 09:32:07PM -0500, Greg Folkert wrote:
> On Sat, 2007-01-20 at 21:16 +0100, David Weinehall wrote:
> > On Sat, Jan 20, 2007 at 06:34:18AM -0500, Greg Folkert wrote:
> > > On Sat, 2007-01-20 at 11:51 +0100, Josselin Mouette wrote:
> > > > Le
\
> --corruptmysettingsplease
You *do* know that there is a graphical gconf-editor, right?
[snip]
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http:/
hat uses the spec."
Presumably people that want to edit their menus can launch this
application using the launcher. It's not really the average
everyday tool...
[snip]
PS: My vote for default GNOME browser definitely goes to Epiphany;
Firefox^WIceweasel comes nowhere close to feel
2350k 828642
2350k (+ 828642, I guess) != 8MB...
The 8MB you cite is for compressing, not decompressing.
[snip]
regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) htt
il very recently (sometimes between Nov 19th
> and Nov 27h).
>
>
> Regards,
> Frederic
>
> [1] http://www.0d.be/debian/debian-gnome-2.16-status.html
Some entries seem to list newer Debian-versions than upstream
versions... Some watch-fil
comes down to bad software design on the automake side rather than bad
makefiles).
[snip]
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~
ing-things.
>
> It's easier to eyeball packages that explicitly announce "bash".
> Those could be put to a stress test through:
>
> /bin/dash
> /bin/posh
> ...
>
> If someone feels up to.
I don't really see the point. If the ma
from bashisms.
You can use whatever bashisms you like when you're working
interactively, that won't hinder dash from executing shells on boot and
elsewhere. Using bashisms in scripts does however cause a problem.
Oh, and there *are* other suitable interactive shells than bash. tcsh,
ksh,
On Thu, Nov 23, 2006 at 09:48:31PM +0100, Florian Weimer wrote:
> * David Weinehall:
>
> > On Sun, Nov 19, 2006 at 07:13:22PM +0100, Andreas Metzler wrote:
> >> Michelle Konzack <[EMAIL PROTECTED]> wrote:
> >> [...]
> >> > ...and where is SuSv3 in
On Thu, Nov 23, 2006 at 11:56:48AM -0800, Thomas Bushnell BSG wrote:
> On Thu, 2006-11-23 at 20:46 +0100, David Weinehall wrote:
> > Well, let's hope people don't use any of the non-SuSv3 features of cat
> > in their shell scripts...
>
> Why? Who cares?
Well,
for most users. That doesn't mean we should limit
ourselves to using bash for non-interactive use though.
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.
ntial to use only SuSv3 compliant features. I think
rewriting *all* scripts to use only SuSv3 features would be too big of
an ordeal, but just fixing the initscripts, plus all scripts in
essential should be doable.
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my windo
e *much*
> easier. Isn't that enough?
If you just want to avoid things breaking, it's enough. If you want to
be able to use the scripts on an embedded platform, or to take advantage
of the performance boost of using dash instead of bash, it isn't.
Regards: David
--
/) David We
On Thu, Nov 23, 2006 at 07:54:46PM +0100, Bill Allombert wrote:
> On Thu, Nov 23, 2006 at 07:41:08PM +0100, David Weinehall wrote:
> >
> > And compared to dash, the difference is vast:
> >
> > -rwxr-xr-x 1 root root 80200 2006-11-21 16:36 /bin/dash
> >
> >
On Thu, Nov 23, 2006 at 07:09:49PM +0100, Steinar H. Gunderson wrote:
> On Thu, Nov 23, 2006 at 06:37:52PM +0100, David Weinehall wrote:
> > Somehow I doubt that you used today's version of bash (which I bet
> > is a lot bigger and more memory-consuming due to new features).
>
> Guess what? I used bash on that old hardware when it was shiny and new
> also. Didn't seem to have any problems.
Somehow I doubt that you used today's version of bash (which I bet
is a lot bigger and more memory-consuming due to new features).
Regards: David
--
/) David
1-21 Steve Langasek <[EMAIL PROTECTED]>
> ([EMAIL PROTECTED])~$
>
> Looks that it's signed by itself.
Yes, aren't all keys self-signed?
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Di
ly use job-control in your shell-scripts? Interesting...
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost
ate: 6.1
Version table:
6.1 0
500 http://ftp.se.debian.org unstable/contrib Packages
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao
ure
it's provided by anything in Debian), the FR-extensions (Fortran
Runtime), most (all?) of the utilities marked as DEVELOPMENT (things
such as compilers, sccs-related commands, cflow, and ctags).
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
//
ds: on."
This proposal has some merit, as long as we do s/POSIX/SuSv3/.
Also, we probably want to make exceptions for find/xargs (to get -0).
[snip]
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
//
ing "debconf" is *also* not allowed, because it is *also* not a
> "POSIX feature". The point is that "POSIX feature" is *not* a
> specification of anything, given the way that POSIX deals with builtins.
Sorry, but that's a strawman, for two reasons. First, POSI
a sort of
> blessing to using an absolute path in this situation, since coreutils test
> is not quite "any other program that one would expect to be on the PATH"
> simply because in this case the shell isn't going to *look* at the PA
d help to be reminded that I can't really
> depend on very much of the semantics of local from any specific
> implementation.
>
> fname () {
> local a # keep it simple
> a='' # initialize the variable
> use a ...
> }
> is the only s
guess, as long as we get rid of crap like [[ ]], <, >, -nt,
-ot, -ef, $RANDOM, $"...", read -e, declare, typeset, function (augh, I
cannot understand why bash even introduced that one), let, source
(again, completely pointless), pushd, popd, &>, {}...
I can probably come up wit
p of people that caused it to fail...
> Before this there was a widely agree definition of what
> /bin/sh needs to support and almost no bugs related to this.
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~~
On Tue, Nov 14, 2006 at 05:11:27PM +0100, Marco d'Itri wrote:
> On Nov 14, David Weinehall <[EMAIL PROTECTED]> wrote:
>
> > > busybox?
> > Such a requirement would at least be wonderful for us embedded developers...
> But hardly practical, IIRC there ar
ably a 3rd
> > alternative]".
>
> busybox?
Such a requirement would at least be wonderful for us embedded developers...
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-whit
the GFDL debacle a manual I could easily refer to, ...
The SuSv3 is to be considered as POSIX these days, so it's available for
free (and even packaged in Debian...)
PS: The equality operator is =.
RegardS: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window
the next firmware version is out;
that way we'll avoid the binary only regulatory daemon.
See the following post:
http://marc.theaimsgroup.com/?l=linux-netdev&m=116226285115407&w=1
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
//
ilable in Debian...
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/
--
To UNSUBSCRIBE, email to [EMAIL
gram.
Isn't there a risk of causing double work?
Person A reports spam, Blars removes it
Person B reports the same spam, Blars checks again - no spam found
Regards: David
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~~~
at least add a postinst
script that does the migration), then I'm all for a switch to the
new version.
Regards: David Weinehall
--
/) David Weinehall <[EMAIL PROTECTED]> /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.
On Tue, Jul 25, 2006 at 01:34:47PM +0200, Wouter Verhelst wrote:
> On Tue, Jul 25, 2006 at 04:39:24AM +0200, David Weinehall wrote:
> > On Mon, Jul 24, 2006 at 06:32:54PM -0400, Joey Hess wrote:
> > > Steve Greenland wrote:
> > > > This really seems like somet
On Tue, Jul 25, 2006 at 11:42:39AM +0900, Miles Bader wrote:
> David Weinehall <[EMAIL PROTECTED]> writes:
> > Well, if foo depends on foo-data, and foo-data depends on foo, I find
> > it really hard to see the point of splitting the two into distinctive
> > packages...
1 - 100 of 182 matches
Mail list logo
