Miguel A. Vallejo wrote:
...
> I activelly follow the development of some programs in diverse areas
> (ham radio, astronomy, emulators, etc), and new versions usually
> appears in unstable months after release. The more prominent example
> is the kernel itself. Current version is 5.5.7, but unstabl
I have a friend who works as a system administrator that always says:
Debian Stable --> Debian Server
Debian Testing --> Debian Desktop Moderate
Debian Unstable --> Debian Desktop Fast
Being Moderate and Fast the speed at you will eat new bugs.
As time goes by, I'm more and more agree with him.
On Tue, Feb 25, 2020 at 06:48:21PM +0100, Sam wrote:
> Thanks for your points of view! I agree that Stable comes at a cost, and of
> course if I ever were to set up a server Debian would probably be my choice.
>
> Regarding derivatives, I know about Ubuntu, Mint, etc., but I don't exactly
> like
On Thu, 27 Feb 2020 09:30:36 -0500
Stefan Monnier wrote:
> > Right. You can also use a CD based Linux such as finnix to shrink an
> > existing LVM logical volume (LV), create a new LV for swap, and run
> > mkswap to lay down a swap partition on it.
>
> BTW, you don't need a separate CD or anyt
On Thu, 27 Feb 2020 08:54:02 +1100
Keith Bainbridge wrote:
>
>
> I'm having trouble understanding how LVM snapshots works on / if it
> is outside the LVM.
>
I don't think anyone has picked this up. Yes, you do need additional
space.
I've only done it a few times. It basically involves leavi
> Right. You can also use a CD based Linux such as finnix to shrink an
> existing LVM logical volume (LV), create a new LV for swap, and run
> mkswap to lay down a swap partition on it.
BTW, you don't need a separate CD or anything like that: you can use
your initrd for that same purpose. I.e. at
On Thu, 27 Feb 2020 11:43:42 +1100
Keith Bainbridge wrote:
> OK I am in the process of install debian in vbox. It set up LVM
> using the whole partition, and allowed several logical volumes.
>
> Am I safe to believe that this is what will happen with a SSD when I
> start?
Yes.
>
> I got a pr
On Thu, 27 Feb 2020 08:59:55 +
Brad Rogers wrote:
> On Wed, 26 Feb 2020 19:47:35 -0600
> John Hasler wrote:
>
> Hello John,
>
> >blindly upgrading nightly causes far more problems than it solves.
>
> Because that's what gets asked about. Nobody posts saying;
>
> "I updated lasted nigh
On Wed, 26 Feb 2020 19:47:35 -0600
John Hasler wrote:
> Andrei writes:
> > An entire month without security updates is not the best idea in my
> > opinion.
>
> It appears to me from watching this list that the practice of
> blindly upgrading nightly causes far more problems than it solves.
On Wed, 26 Feb 2020 19:47:35 -0600
John Hasler wrote:
Hello John,
>blindly upgrading nightly causes far more problems than it solves.
Because that's what gets asked about. Nobody posts saying;
"I updated lasted night, and everything worked!"
There's no point.
However, I do recognise that yo
Brad writes:
> I update daily, but 'cherry pick' in the event of transitions that
> _might_ have repercussions.
So you *don't* "track" testing by doing automatic full upgrades every
day. That is the practice that I'm arguing against.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
Andrei writes:
> An entire month without security updates is not the best idea in my
> opinion.
I follow the security list and do security updates as required, of
course. Those rarely (if ever) require full upgrades. There is no
need to do daily full upgrades just to stay up with security.
> A
On 27/2/20 8:54 am, Keith Bainbridge wrote:
Thanks for the positive responses. I am interested now because I am
about to buy a new drive. I guess the answer to these will be obvious
when I choose LVM at the disk selection stage, but do I need to keep
system partitions separate? as I install t
On 27/2/20 3:46 am, Charles Curley wrote:
On Thu, 27 Feb 2020 00:15:44 +1100
Keith Bainbridge wrote:
Is LVM viable? I can see the benefit of re-sizing on the fly. I use
multi-boot. I can see the possibility of /dev/sda1 and LVM using the
rest. But is it viable, please?
Yes, it is viable. I
On Tue, 25 Feb 2020 19:18:10 -0600
John Hasler wrote:
Hello John,
>*Don't* "track" Testing or Unstable by upgrading nightly.
I'm with songbird (and others). It can be done, with care;
I subscribe to the 'Testing Changes' mailing list.
I subscribe to the 'Debian Developers' mailing list.
I sub
On Thu, 27 Feb 2020 00:15:44 +1100
Keith Bainbridge wrote:
> Is LVM viable? I can see the benefit of re-sizing on the fly. I use
> multi-boot. I can see the possibility of /dev/sda1 and LVM using the
> rest. But is it viable, please?
Yes, it is viable. I use an encrypted partition with LVM on
John Hasler wrote:
...
> *Don't* "track" Testing or Unstable by upgrading nightly. I don't
> understand why people want to do this. A full upgrade (after a test
> upgrade) about once a month is plenty.
different people have different purposes. :)
my reasons for my morning routine is to det
Hi.
On Thu, Feb 27, 2020 at 12:15:44AM +1100, Keith Bainbridge wrote:
> Is LVM viable? I can see the benefit of re-sizing on the fly. I use
> multi-boot. I can see the possibility of /dev/sda1 and LVM using the rest.
> But is it viable, please?
Yes. LVM does not care if your drive was d
Further to lvm snapshots, I have read about 10 articles explaining the
concept of LVM and how to set them up. All of them talk about using
/dev/sdb, c, d or more for LVM. None uses /dev/sda
I am running a laptop and raspberry pi's, all with only 1 prime 'disk' and
USB attached disks/sticks.
Is LV
On 2020-02-26, Andrei POPESCU wrote:
>
> Debian testing already has checks and delays in place to filter out
> (most of the) problems. Updates fixing security issues are prioritised.
I used testing once; I found 'apt-listbugs' to be quite helpful in
obviating potential disaster (it was invariably
On Ma, 25 feb 20, 19:18:10, John Hasler wrote:
> Sam writes:
> > I will give Testing a spin and will definitely take another look at
> > the Debian derivatives. You also made me admire the Debian community,
> > so that's a big plus on the
> > reasons-why-I-definitely-need-to-switch-to-Debian list :
On 26/2/20 10:59 am, Stefan Monnier wrote:
LVM snapshots
I use timeshift for the same purpose; and have needed it a couple of
times over 14 months since switching from mint.
I look at what packages are to be upgraged, and if more than a few
libraries, I create a new timeshift first. Usually
Sam writes:
> I will give Testing a spin and will definitely take another look at
> the Debian derivatives. You also made me admire the Debian community,
> so that's a big plus on the
> reasons-why-I-definitely-need-to-switch-to-Debian list :)
A couple of suggestions if you decide to use Testing o
> I would happily consider using Debian Testing for example, but wherever I see
> someone asking about it I always find someone discouraging from using it due
> to the possibility of having broken or unsecure packages for a long time due
> to it being automated.
Other tools you can use: LVM snapsh
Thank you very much for the tips!
I will give Testing a spin and will definitely take another look at the Debian
derivatives. You also made me admire the Debian community, so that's a big
plus on the reasons-why-I-definitely-need-to-switch-to-Debian list :)
Thank you,
Sam
Peter Ehlert wrote:
> I think Debian Testing would fit you very well
> It is like a rock, honestly.
that hasn't been my experience, but i know what i'm doing
well enough to fix things or to ask for help here if i find
something i don't understand well enough.
i got bit by some kind of lightdm
Roberto writes:
> On strategy would be to run testing and not update too frequently.
I do that with Unstable. Works fine (but I use neither Gnome nor KDE) I
follow the security list and upgrade the relevant package when I see
something there that matters to me. Security fixes reach Unstable as
f
20 7:55 AM, Sam wrote:
Hello,
I would like to hear opinions about the release cycle of the Stable Debian
releases for a Desktop user.
I love the Debian ideals and perks (its social contract, independence from big
companies...) and understand to a certain extent the fundamentals on why
keeping &qu
Sam wrote:
> Hello,
>
> I would like to hear opinions about the release cycle of the Stable Debian
> releases for a Desktop user.
>
> I love the Debian ideals and perks (its social contract, independence from
> big
> companies...) and understand to a certain extent
I install testing on all my machines*. It is very usable. Sid has given me
problems in the past, so I stay clear.
*While it is true I install testing, I should clarify that I continue to
use it as it moves into stable and then old-stable. Eventually, I hit some
kind of "you can't get there from he
On Tue, Feb 25, 2020 at 06:48:21PM +0100, Sam wrote:
> Thanks for your points of view! I agree that Stable comes at a cost, and of
> course if I ever were to set up a server Debian would probably be my choice.
>
> Regarding derivatives, I know about Ubuntu, Mint, etc., but I don't exactly
> like
Thanks for your points of view! I agree that Stable comes at a cost, and of
course if I ever were to set up a server Debian would probably be my choice.
Regarding derivatives, I know about Ubuntu, Mint, etc., but I don't exactly
like distributions tied to or ultimately dependant on commercial en
On Tue, 25 Feb 2020 16:55:46 +0100
Sam wrote:
> Hello,
>
> I would like to hear opinions about the release cycle of the Stable
> Debian releases for a Desktop user.
>
> I love the Debian ideals and perks (its social contract, independence
> from big companies...) and un
On Tue, Feb 25, 2020 at 04:55:46PM +0100, Sam wrote:
> Hello,
>
> I would like to hear opinions about the release cycle of the Stable Debian
> releases for a Desktop user.
>
> I love the Debian ideals and perks (its social contract, independence from
> big
> companies
Hello,
I would like to hear opinions about the release cycle of the Stable Debian
releases for a Desktop user.
I love the Debian ideals and perks (its social contract, independence from big
companies...) and understand to a certain extent the fundamentals on why
keeping "old-ish" v
On Tuesday 03 February 2009 12:51:15 Barclay, Daniel wrote:
> [C]ould freezes in testing be started sooner
> after the previous release?
I think so. There's really no reason that testing has to unfreeze at all,
but it's how things are done right now.
I think it would be nice if some automated s
o freeze for N+1
> that can be justified given the overhead of releasing, and I think the
> answer to that will always be at least somewhat subjective.
>
> Nye
>
> (PS: FWIW, it's my *personal* belief that the freeze for Lenny should
> have been somewhat earlier, but on t
Ken Teague wrote:
> Barclay, Daniel wrote:
>> Ken Teague wrote:
...
>
>> If Debian set a shorter target release interval, each individual package
>> maintainer would implement (and test and debug) a smaller set of features
>> and changes (for that package) for each (more frequent) release. I don'
that the freeze for Lenny should
have been somewhat earlier, but on the other hand we already seem to
have reached the point where the time from freeze to release is a
large fraction of the total release cycle, and do we really want that
proportion to be bigger?)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
David Jardine wrote:
> On Tue, Jan 06, 2009 at 12:28:44PM -0800, Ken Teague wrote:
>> Barclay, Daniel wrote:
...
>
> Well, maybe I'll prove to be understanding neither of you, but the
> point seems to be that you can't 'force' the maturity of a package.
I wasn't talking about trying to force the
Boyd Stephen Smith Jr. wrote, on 07/01/09 09:09:
On Tuesday 2008 December 30 12:30:40 Barclay, Daniel wrote:
However, when you're releasing N thousand changes every 18 months or so,
it's arguable that maybe you should be releasing N/2 thousand changes every
9 or 10 months.
Bah. I think that 1
On Tuesday 2008 December 30 12:30:40 Barclay, Daniel wrote:
> However, when you're releasing N thousand changes every 18 months or so,
> it's arguable that maybe you should be releasing N/2 thousand changes every
> 9 or 10 months.
Bah. I think that 18 months is a fine amount of time between stabl
David Jardine wrote:
> If that's not a complete load of rubbish, quality will be improved
> by longer release cycles.
Makes sense to me. I also found this in a very old post to this list
which points out a lot of pros and cons::
On Sat, 22 Sep 2007 00:36:15 +0530, Masatran, R. Deepak wrote:
>
Barclay, Daniel wrote:
> As I wrote in my other message, I'm talking about changing the "chunk size"
> of releases, not the quality.
Debian releases work more or less like this:
- new software versions are published upstream (source code).
- this software is packaged into debian and enters 'unst
On Tue, Jan 06, 2009 at 12:28:44PM -0800, Ken Teague wrote:
> Barclay, Daniel wrote:
> > [...]
> > Doing it the second way does _not_ have to compromise any quality
> > standards.
> > (Why do you (seemingly) think it does?)
>
> Perhaps I wasn't understanding you correctly the first time around.
>
Carl Fink wrote:
> Just jumping in on one small point.
>
> Doesn't actually make much sense, if you think about it. If the packages
> are updated by Debian developers, surely that would help Debian to its next
> release, too? Anyway, IIRC someone posted to this list last year that a
> great numb
Just jumping in on one small point.
On Tue, Jan 06, 2009 at 12:28:44PM -0800, Ken Teague wrote:
> I can't put an exact number on it, but I think there are more than a
> thousand Debian developers from various parts of the world, each of whom
> have a life outside of Debian development. Without p
w does it sound like that?) People rarely address how the length
> of Debian's release cycle is affected by how much change Debian tries to
> incorporate into each release.
The changes are mostly incorporated into the various packages and the
Linux kernel. I don't think most Debi
Raquel wrote:
> On Tue, 30 Dec 2008 15:38:41 -0800
> Ken Teague wrote:
>
>>> Is Debian's stable release cycle relative long because Debian
>>> releases typically involve big changes that set the minimum time
>>> between releases, or is it because Debian
Ken Teague wrote:
> Barclay, Daniel wrote:
>> Why do so many defenses of Debian's release cycle length seem to ignore or
>> skirt the issue of _how_ _much_ is planned to be in each release? (Saying
>> "when it's right" still depends on what "it"
Raquel wrote:
>
> I, for one, am very thankful for Debian and the way that it
> releases. I run a couple of servers that I would just as soon "just
> ran", instead of having to tinker or fix things all the time. I have
> more to do.
>
> Thank you, Debian!!
>
Yes, me too. I'm also using debia
Koh Choon Lin wrote:
> Dear all
>
> Anyone has an idea what is the release cycle for Debian? I understand
> six months is the standard for Ubuntu.
>
Look in http://bugs.debian.org/release-critical/ . The current number of
bugs affecting the next release is 92 (the green line)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Funny. I always thought that latest "testing" was anointed "stable" by
the release panjandrum when - and only when -- the latter determined
that the relative positions of the planets were such to guarantee
complete freedom of the new release from bugs
On Tue, 30 Dec 2008 15:38:41 -0800
Ken Teague wrote:
> > Is Debian's stable release cycle relative long because Debian
> > releases typically involve big changes that set the minimum time
> > between releases, or is it because Debian not really attempt to
> >
Barclay, Daniel wrote:
> Why do so many defenses of Debian's release cycle length seem to ignore or
> skirt the issue of _how_ _much_ is planned to be in each release? (Saying
> "when it's right" still depends on what "it" is--which set of features/
> cha
s. keeling wrote:
> Koh Choon Lin :
>> Anyone has an idea what is the release cycle for Debian? I
>> understand six months is the standard for Ubuntu.
>
> Why? What's wrong with Etch and Lenny? They're both well usable now,
> yes? Are you looking for Le
On Thu, 25 Dec 2008, Mark Allums engaged keyboard and shared this with us all:
>--} Andrei Popescu wrote:
>--} > On Tue,23.Dec.08, 07:37:18, Mark Allums wrote:
>--} >
>--} >> Release schedule for Debian seems to be, whenever they feel like it.
>--} >
>--} > Maybe it's because I'm not a native speak
Koh Choon Lin :
>
> Anyone has an idea what is the release cycle for Debian? I
> understand six months is the standard for Ubuntu.
Why? What's wrong with Etch and Lenny? They're both well usable now,
yes? Are you looking for Lenny features in a "stable" releas
Andrei Popescu wrote:
On Tue,23.Dec.08, 07:37:18, Mark Allums wrote:
Release schedule for Debian seems to be, whenever they feel like it.
Maybe it's because I'm not a native speaker, but this sounds to me as if
Debian Developers would release according to their mood :)
It means that lite
Andrei Popescu wrote:
On Tue,23.Dec.08, 07:37:18, Mark Allums wrote:
Release schedule for Debian seems to be, whenever they feel like it.
Maybe it's because I'm not a native speaker, but this sounds to me as if
Debian Developers would release according to their mood :)
Regards,
Andrei
W
On Wed,24.Dec.08, 16:21:41, Daryl Styrk wrote:
> Andrei Popescu wrote:
> > On Tue,23.Dec.08, 07:37:18, Mark Allums wrote:
> >
> >> Release schedule for Debian seems to be, whenever they feel like it.
> >
> > Maybe it's because I'm not a native speaker, but this sounds to me as if
> > Debian Dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrei Popescu wrote:
> On Tue,23.Dec.08, 07:37:18, Mark Allums wrote:
>
>> Release schedule for Debian seems to be, whenever they feel like it.
>
> Maybe it's because I'm not a native speaker, but this sounds to me as if
> Debian Developers would
On Tue,23.Dec.08, 07:37:18, Mark Allums wrote:
> Release schedule for Debian seems to be, whenever they feel like it.
Maybe it's because I'm not a native speaker, but this sounds to me as if
Debian Developers would release according to their mood :)
Regards,
Andrei
--
If you can't explain it
On Tue, Dec 23, 2008 at 08:28:43PM +0800, Koh Choon Lin wrote:
> Dear all
>
> Anyone has an idea what is the release cycle for Debian? I understand
> six months is the standard for Ubuntu.
>
The operative rule for all recent releases is that each release
happens when the release
Douglas A. Tutty wrote:
On Tue, Dec 23, 2008 at 08:28:43PM +0800, Koh Choon Lin wrote:
Dear all
Anyone has an idea what is the release cycle for Debian? I understand
six months is the standard for Ubuntu.
When its ready. Generally every couple of years or so.
Mark Allums wrote
Koh Choon Lin wrote:
Dear all
Anyone has an idea what is the release cycle for Debian? I understand
six months is the standard for Ubuntu.
Also, when can binary for 4.0r6 be expected to be released?
Binary for 4.0r6 should be out any day now. Might already be out.
Release schedule for
On Tue, Dec 23, 2008 at 08:28:43PM +0800, Koh Choon Lin wrote:
> Dear all
>
> Anyone has an idea what is the release cycle for Debian? I understand
> six months is the standard for Ubuntu.
>
When its ready. Generally every couple of years or so.
--
To UNSUBSCRIBE, email to d
Dear all
Anyone has an idea what is the release cycle for Debian? I understand
six months is the standard for Ubuntu.
Also, when can binary for 4.0r6 be expected to be released?
--
Regards
Koh Choon Lin
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
Am 2006-03-10 22:23:48, schrieb David Berg:
> Has anyone heard/read anything that MIGHT indicate that etch MIGHT go
> stable faster than the 2-3 years that it took for Sarge, and Woody to
> go stable?
Woody went faster then 2-3 years, but there was a changement
in the Woody-Installer which took a
On Sat, 11 Mar 2006 22:07:44 -0500
Mark Fletcher <[EMAIL PROTECTED]> wrote:
> Many of the people who come to this list looking for help know
> exactly what it's like to be in Debian Hell... :-!
Attempting to keep an up-to-date Sid system before I knew much about
Linux, I have been to Debian Hell.
Olafur Jens Sigurdsson writes:
> Actually Hell freezes over every year, or allmost.
> http://en.wikipedia.org/wiki/Hell%2C_Norway
There is also a Hell in Michigan in the US (in the lower peninsula:
Paradise is in the upper peninsula).
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
Þann 2006-03-11, 22:07:44 (-0500) skrifaði Mark Fletcher:
> gawab wrote:
>
> > Steve Lamb wrote:
> >
> >> Marc Shapiro said:
> >>
> >>
> >>> Personally, my theory on the REAL reason that the release cycles have
> >>> been getting so long is that we are running out of "Toy Story"
> >>> character
gawab wrote:
Steve Lamb wrote:
Marc Shapiro said:
Personally, my theory on the REAL reason that the release cycles have
been getting so long is that we are running out of "Toy Story"
character
names. What do we do when there are no more characters left?
Start working through
On Friday, 10.03.2006 at 22:09 -0800, Steve Lamb wrote:
> Marc Shapiro said:
> > Personally, my theory on the REAL reason that the release cycles have
> > been getting so long is that we are running out of "Toy Story" character
> > names. What do we do when there are no more characters left?
>
>
Marc Shapiro wrote:
David Berg wrote:
I'm curious to know when etch might freeze. Now, before you all jump
on me and tell me "its ready when its ready", let me clarify. I'm not
looking for a date, or a month, or even a year necessarily as I
realize they would all be guesses. Perhaps I could
David Berg wrote:
I don't know if there's a good way to ask this question, and am very
tempted to just hit cancel now...
I'm curious to know when etch might freeze. Now, before you all jump
on me and tell me "its ready when its ready", let me clarify. I'm not
[snip]
I think that your reques
Steve Lamb wrote:
Marc Shapiro said:
Personally, my theory on the REAL reason that the release cycles have
been getting so long is that we are running out of "Toy Story" character
names. What do we do when there are no more characters left?
Start working through Monsters, Inc.? I
On Fri, 2006-03-10 at 22:23 -0600, David Berg wrote:
> I don't know if there's a good way to ask this question, and am very
> tempted to just hit cancel now...
>
> I'm curious to know when etch might freeze. Now, before you all jump
> on me and tell me "its ready when its ready", let me clarify.
Marc Shapiro said:
> Personally, my theory on the REAL reason that the release cycles have
> been getting so long is that we are running out of "Toy Story" character
> names. What do we do when there are no more characters left?
Start working through Monsters, Inc.? I mean what's cooler than
David Berg wrote:
I'm curious to know when etch might freeze. Now, before you all jump
on me and tell me "its ready when its ready", let me clarify. I'm not
looking for a date, or a month, or even a year necessarily as I
realize they would all be guesses. Perhaps I could get the best
answer b
David Berg wrote:
> I don't know if there's a good way to ask this question, and am very
> tempted to just hit cancel now...
>
> I'm curious to know when etch might freeze. Now, before you all jump
> on me and tell me "its ready when its ready", let me clarify. I'm not
> looking for a date, or
e/xorg), translation goals, deciding what
packages get a last
minute repreive (like webmin), including new arch(64bit) and not
including others(68k) and of course the rate at which RC bugs are fixed.
It seems each release cycle is an advanture. This one include ubuntu as
a factor. They are working w
On Friday 10 March 2006 21:23, David Berg wrote:
> I don't know if there's a good way to ask this question, and am very
> tempted to just hit cancel now...
>
> I'm curious to know when etch might freeze. Now, before you all jump
> on me and tell me "its ready when its ready", let me clarify. I'm
I don't know if there's a good way to ask this question, and am very
tempted to just hit cancel now...
I'm curious to know when etch might freeze. Now, before you all jump
on me and tell me "its ready when its ready", let me clarify. I'm not
looking for a date, or a month, or even a year necessa
get what you pay for ... in terms of quality of coding,
> productive work, qa, bug tracking, doc que ment a tion,
> testing, etc
>
> "release cycle" can be daily or weekly or monthly ...
> - you can release a CD anytime you like
> and that daily build already exists
>
&g
silly con valley ... a good developer can pull down $150K/yr or more
and gazillion in stock options
- you get what you pay for ... in terms of quality of coding,
productive work, qa, bug tracking, doc que ment a tion,
testing, etc
"release cycle" can be
Hi,
Would it be feasible to hire one or more full time developer to spend
all their time ironing out the release critical bugs?
How much would this developer need to get paid?
Any ideas as to whether people would be willing to commit a certain
amount of annual donations to this etc. would also b
On Thu, Mar 13, 2003 at 09:24:00PM -0500, Abdul Latip wrote:
> * The Multiple Architecture Support Issue
>
> Each additional architecture support will significantly increase
> the Debian release cycle, including security update, as well as
> moving from "unstable" to &q
00 or 1) has very little
> relation to the Debian release cycle.
yes, i would call this correct. it is actually about RC bugs,
so-called release-critical bugs. If there is one of those, then the
frozen testing release is not ready for rollout.
> Each additional architecture support will s
Hi,
First of all, apology for my poor English. This following
is *NOT* a complaint, but I would like to know if I have
got the picture correctly in regard of the Debian release cycle
(e.g. from Woody to Sarge). Please let my know the URL if
this issue has been discussed before.
* The Essential
90 matches
Mail list logo
