Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #239560

Re: amdgpu broken on bookworm?

From "Andrew M.A. Cater" <amacater@einval.com>
Newsgroups linux.debian.user
Subject Re: amdgpu broken on bookworm?
Date 2021-09-01 16:40 +0200
Message-ID <CSzzb-2lz-7@gated-at.bofh.it> (permalink)
References <CQP5o-xC-5@gated-at.bofh.it> <CR66d-358-5@gated-at.bofh.it> <CRc1Y-6P4-11@gated-at.bofh.it> <CRiK6-2wm-3@gated-at.bofh.it> <CSz6a-2bn-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, Sep 01, 2021 at 09:06:47AM -0500, David Wright wrote:
> On Sat 28 Aug 2021 at 22:19:05 (-0400), songbird wrote:
> > David Wright wrote:
> > > On Sat 28 Aug 2021 at 08:36:32 (-0400), songbird wrote:
> > ...
> > >>   just to note that using "bookworm" in your subject line can
> > >> give the implication that "bookworm" is actually released which
> > >> it hasn't.  it is much better to use the keyword "testing" in
> > >> the subject line instead.
> > >
> > > I don't know where you got that from.
> > 
> >   because testing has always been just testing to me, when
> > the images are made and sent out as official releases with
> > their signed packages and keys and all the rest that is when
> > i consider them by their code names.  that is when the 
> > release team actually releases it.  just because i am following
> > along while they are putting it together in testing or sid
> > doesn't mean it is done.
> 
> That seems a reasonable viewpoint if you're a perpetual testing user,
> living entirely in the present.
> 
> > > A Release gets a *number*.
> > > (The number that might be given to trixie will depend on how
> > > superstitious the Debian release team is.) It's legitimate to talk
> > > about, say, features that might be retained in bookworm, but dropped
> > > by trixie. That's what the codenames are for.
> > 
> >   sure, but those are all conversations about possibilities
> > they're not done until they're released.
> 
> They have to be planned for in the years before release. It's
> difficult to discuss future distributions without giving them
> static codenames that don't shift under your feet. That's
> standard practice in almost any project management.
> 
> > of course this is 
> > my opinion but i think the Release team also feels something
> > about the meaning of the word "Official" and the whole process
> > including the key signing and verification steps...
> 
> I'm not sure what you're saying here; that bookworm and trixie
> aren't "official" names?
> 

It's also worth reviewing ancient history which is what made Debian
switch to codenames at all (and a bunch of projects then followed our
example eg Ubuntu and Red Hat (though Red Hat's names are barely visible).

Someone at Infomagic wanted to steal a march on everyone else and publish
Debian 1.0 on their quarterly release. I can't remember quite what they
did package - but it wasn't release quality yet and didn't actually boot.
The end result was that Debian jumped straight to 1.1 and a new thing - a
codename (Buzz) because the then DPL (Bruce Perens) worked for Pixar.

bookworm is less than a month old but will follow the release until it's 
oldoldstable - "testing" is a movable feast.

All the very best, as ever,

Andy Cater


> Cheers,
> David.
> 

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

amdgpu broken on bookworm? Jeffrey Chimene <jeff@grandadventuresranch.com> - 2021-08-27 20:50 +0200
  Re: amdgpu broken on bookworm? piorunz <piorunz@gmx.com> - 2021-08-28 13:30 +0200
    Re: amdgpu broken on bookworm? Jeffrey Chimene <jchimene@gmail.com> - 2021-08-28 15:00 +0200
      Re: amdgpu broken on bookworm? piorunz <piorunz@gmx.com> - 2021-08-28 15:10 +0200
        Re: amdgpu broken on bookworm? Jeffrey Chimene <jeff@grandadventuresranch.com> - 2021-08-28 16:00 +0200
        Re: amdgpu broken on bookworm? Jeffrey Chimene <jeff@grandadventuresranch.com> - 2021-08-28 16:20 +0200
          Re: amdgpu broken on bookworm? Jeffrey Chimene <jeff@grandadventuresranch.com> - 2021-08-28 16:30 +0200
            Re: amdgpu broken on bookworm? Jeffrey Chimene <jeff@grandadventuresranch.com> - 2021-08-28 17:40 +0200
              Re: amdgpu broken on bookworm? piorunz <piorunz@gmx.com> - 2021-08-28 18:00 +0200
                Re: amdgpu broken on bookworm? Jeffrey Chimene <jeff@grandadventuresranch.com> - 2021-08-28 19:00 +0200
                Re: amdgpu broken on bookworm? piorunz <piorunz@gmx.com> - 2021-08-28 22:50 +0200
          Re: amdgpu broken on bookworm? Jeffrey Chimene <jeff@grandadventuresranch.com> - 2021-08-28 16:30 +0200
  Re: amdgpu broken on bookworm? songbird <songbird@anthive.com> - 2021-08-28 15:00 +0200
    Re: amdgpu broken on bookworm? Jeffrey Chimene <jchimene@gmail.com> - 2021-08-28 15:10 +0200
    Re: amdgpu broken on bookworm? Jeffrey Chimene <jeff@grandadventuresranch.com> - 2021-08-28 15:30 +0200
    Re: amdgpu broken on bookworm? David Wright <deblis@lionunicorn.co.uk> - 2021-08-28 21:20 +0200
      Re: amdgpu broken on bookworm? songbird <songbird@anthive.com> - 2021-08-29 04:30 +0200
        Re: amdgpu broken on bookworm? David Wright <deblis@lionunicorn.co.uk> - 2021-09-01 16:10 +0200
          Re: amdgpu broken on bookworm? "Andrew M.A. Cater" <amacater@einval.com> - 2021-09-01 16:40 +0200
            Re: amdgpu broken on bookworm? rhkramer@gmail.com - 2021-09-01 17:40 +0200
              Re: amdgpu broken on bookworm? The Wanderer <wanderer@fastmail.fm> - 2021-09-01 17:50 +0200
              Re: amdgpu broken on bookworm? Greg Wooledge <greg@wooledge.org> - 2021-09-01 17:50 +0200
                Re: amdgpu broken on bookworm? rhkramer@gmail.com - 2021-09-01 18:20 +0200

csiph-web