On Fri, Jul 05, 2019 at 10:35:05AM -0300, Francisco M Neto wrote:
> On Tue, 2019-07-02 at 12:23 -0400, Default User wrote:
> > On Tue, Jul 2, 2019, 05:38 Dave Sherohman wrote:
> > > I think the core misunderstanding here is that you seem to be assuming
> > > that, when a new stable comes out, a
On Tue, 2019-07-02 at 12:23 -0400, Default User wrote:
>
>
> On Tue, Jul 2, 2019, 05:38 Dave Sherohman wrote:
> > I think the core misunderstanding here is that you seem to be assuming
> > that, when a new stable comes out, a new unstable is created to go with
> > it.
Well... maybe? I
On 2019-07-02, Curt wrote:
> On 2019-07-01, Joe wrote:
>>
>> Debian's main selling point is that a Stable can *always* be upgraded
>> in place to the next version, so that kind of incompatibility does not
>
> Then it will fail to live up to the marketing for the brave 600 or so
On Tue, Jul 2, 2019, 05:38 Dave Sherohman wrote:
> On Mon, Jul 01, 2019 at 03:34:55PM -0400, Default User wrote:
> > What if a new Stable release introduces a major change to the existing
> > distribution technology or methodology?
> >
> > For example, a new default filesystem is introduced. Or
On Mon, Jul 01, 2019 at 03:34:55PM -0400, Default User wrote:
> What if a new Stable release introduces a major change to the existing
> distribution technology or methodology?
>
> For example, a new default filesystem is introduced. Or something like
> systemd infects the distribution or its
On 2019-07-01, Joe wrote:
>
> Debian's main selling point is that a Stable can *always* be upgraded
> in place to the next version, so that kind of incompatibility does not
Then it will fail to live up to the marketing for the brave 600 or so
Debian users (according to Popularity Contest)
On Tue, 2 Jul 2019 09:21:59 +0200
wrote:
> On Mon, Jul 01, 2019 at 11:51:10PM +0200, Matthew Crews wrote:
> > On 7/1/19 10:24 AM, Default User wrote:
> > > Hi.
> > >
> > > Easy question, maybe hard to answer . . .
> > >
> > > Is someone has an existing conventional Unstable setup (nothing
>
On Mon, Jul 01, 2019 at 11:51:10PM +0200, Matthew Crews wrote:
> On 7/1/19 10:24 AM, Default User wrote:
> > Hi.
> >
> > Easy question, maybe hard to answer . . .
> >
> > Is someone has an existing conventional Unstable setup (nothing exotic
> > in hardware or software), what if any special
On Mon, Jul 01, 2019 at 11:27:40PM +0200, Ansgar wrote:
> Default User writes:
> > Or something like
> > systemd infects the distribution or its rate of metastasis accelerates,
This was definitely toxic...
> I think we should make systemd mandatory; it would help make Debian a
> more welcoming
On 7/1/19 10:24 AM, Default User wrote:
> Hi.
>
> Easy question, maybe hard to answer . . .
>
> Is someone has an existing conventional Unstable setup (nothing exotic
> in hardware or software), what if any special actions should be taken
> before, during, or after the impending release of the
Default User writes:
> Or something like
> systemd infects the distribution or its rate of metastasis accelerates,
I think we should make systemd mandatory; it would help make Debian a
more welcoming distribution by making toxic people hopefully finally go
away.
Ansgar
On Mon, Jul 01, 2019 at 11:18:18PM +0200, deloptes wrote:
> Joe wrote:
>
> > Presumably, apt-get will be dropped one day, but apt is already the
> > preferred system, with more functionality than apt-get.
>
> AFAIK apt is frontend to apt-get, or I am wrong?
They're both front-ends to the APT
Joe wrote:
> Presumably, apt-get will be dropped one day, but apt is already the
> preferred system, with more functionality than apt-get.
AFAIK apt is frontend to apt-get, or I am wrong?
On Mon, Jul 01, 2019 at 09:25:17PM +0100, Joe wrote:
> Presumably, apt-get will be dropped one day, but apt is already the
> preferred system, with more functionality than apt-get.
For GNU's sake, _dselect_ is still packaged!
I can't imagine apt-get going anywhere, so long as Debian lives. Not
On Mon, 1 Jul 2019 15:34:55 -0400
Default User wrote:
>
> Well, a recent thread about encrypted file systems got me to thinking.
>
> What if a new Stable release introduces a major change to the existing
> distribution technology or methodology?
>
> For example, a new default filesystem is
Default User wrote:
> On Mon, Jul 1, 2019, 13:51 Brian wrote:
>
> What if a new Stable release introduces a major change to the existing
> distribution technology or methodology?
>
> For example, a new default filesystem is introduced. Or something like
> systemd infects the distribution or
On Mon, Jul 1, 2019, 13:51 Brian wrote:
> On Mon 01 Jul 2019 at 13:24:48 -0400, Default User wrote:
>
> > Hi.
> >
> > Easy question, maybe hard to answer . . .
> >
> > Is someone has an existing conventional Unstable setup (nothing exotic in
> > hardware or software), what if any special actions
On Mon 01 Jul 2019 at 13:24:48 -0400, Default User wrote:
> Hi.
>
> Easy question, maybe hard to answer . . .
>
> Is someone has an existing conventional Unstable setup (nothing exotic in
> hardware or software), what if any special actions should be taken before,
> during, or after the
Hi.
Easy question, maybe hard to answer . . .
Is someone has an existing conventional Unstable setup (nothing exotic in
hardware or software), what if any special actions should be taken before,
during, or after the impending release of the new Stable?
(inb4:
1 - RTFM
2 - RTF release notes)
19 matches
Mail list logo
