public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Devon Miller" <devon.c.miller@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Re: Re: Re: how thorough is #emerge --sync?
Date: Thu, 19 Oct 2006 10:38:20 -0400	[thread overview]
Message-ID: <c52221f0610190738n2fedcf7bl6db11aba61c8cd3b@mail.gmail.com> (raw)
In-Reply-To: <1556722.K8zGttGTqY@work.message-center.info>

[-- Attachment #1: Type: text/plain, Size: 3474 bytes --]

You both seem to be arguing about what constitutes stable. And there are 2
different definitions: stable as defined by the upstream source and stable
as defined in portage.

In this case, the "upstream stable" is 0.9.3 and the "portage stable" os 0.8
.

Not appreciating the distinction, Maxim was asking why he's not getting the
latest stable (expecting the "upstream stable").

Alexander's comments reflect the "portage stable", but don't take in to
account that portage does not always keep up. In fact, in this case it's
languished rather badly.

0.9.1 was added to bugzilla (http://bugs.gentoo.org/show_bug.cgi?id=87626)
in Apr-05
It looks like it was added to portage in Nov-05
It's been in portage for 11 months, with no bugs filed against it, and it's
still ~x86.

0.9.2 was added to bugzilla (http://bugs.gentoo.org/show_bug.cgi?id=) in
Dec-05
It l was added to portage in Feb-06
It's been in portage for 8 months, with no bugs filed against it, and it's
still ~x86.

Now, Darren has added a bug for 0.9.3 and a month later, it's still waiting
to get added to portage.
His issue is 0.9.1 and 0.9.2 should have been stable by now.

So, while Alexander is technically correct, (emerge is doing exactly what it
should) this not a good thing, because portage is still delivering older,
buggy code. Unfortunately, getting ebuilds marked stable requires the
intervention of a Gentoo developer and while the documentation says what
*should* happen, it does not say what to do when something falls through the
cracks.

I would suggest Darren look through the develoiper list (
http://www.gentoo.org/proj/en/devrel/roll-call/userinfo.xml) for developers
handling media-sound. Add them to the cc list on the 0.9.2 ebuild and add a
comment asking that it be marked stable. And ask for the 0.9.3 to be added
as ~x86

dcm

On 10/19/06, Alexander Skwar <listen@alexander.skwar.name> wrote:
>
> Darren Kirby <bulliver@badcomputer.org>:
>
> > Quoth the Alexander Skwar
> >
> >> Darren, on the other hand, seems to have
> >> some misunderstanding about how portage works.
> >
> > Stop being so bloody obtuse and read my response to Willie. I know
> perfectly
> > well how portage works. I am taking issues with your vague responses
> which
> > are open to several interpretations.
>
> No, they are not. I said, that it is unreasonable to expect, that
> emerge should offer a version other than 0.8 of dir2ogg, as that's
> the latest stable. Or rather, I asked maxim why he thinks, that
> a version, other than the latest stable (ie. 0.8), should be
> offered.
>
> > You would be well served by writing a clear and concise response
>
> I did. If you try to interprete it somehow and you get it wrong,
> than I'm terribly sorry for that, but that's just not my problem.
>
> > rather than
> > another open-ended question if you want to get your point accross.
>
> My point is, that emerge offers, by default, to install the latest
> stable version. I wanted to make maxim think about why he expects
> a different version.
>
> >> Just because there's
> >> a newer version of some program out there in the wild, doesn't mean,
> >> that it'll be available to emerge/portage through some sort of magic.
> >
> > That's certainly not what I think,
>
> I didn't say so, did I?
>
>
> Alexander Skwar
> --
> <rcw> those apparently-bacteria-like multicolor worms coming out of
>       microsoft's backorifice
> <rcw> that's the backoffice logo
>
>
> --
> gentoo-user@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 4359 bytes --]

  reply	other threads:[~2006-10-19 14:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18  3:37 [gentoo-user] how thorough is #emerge --sync? maxim wexler
2006-10-18  3:43 ` maxim wexler
2006-10-18  5:30   ` [gentoo-user] " Alexander Skwar
2006-10-18  5:53     ` Darren Kirby
2006-10-18  6:11       ` Iain Buchanan
2006-10-18  6:31       ` [gentoo-user] " Alexander Skwar
2006-10-18 18:30         ` Darren Kirby
2006-10-18 18:57           ` Willie Wong
2006-10-18 19:20             ` Darren Kirby
2006-10-18 21:37               ` [gentoo-user] " Alexander Skwar
2006-10-18 21:31             ` Alexander Skwar
     [not found]               ` <200610181449.12060.bulliver@badcomputer.org>
2006-10-19 10:04                 ` [gentoo-user] " Alexander Skwar
2006-10-19 14:38                   ` Devon Miller [this message]
2006-10-19 14:53                     ` [gentoo-user] " Alexander Skwar
2006-10-19 17:21                     ` [gentoo-user] Re: Re: " Willie Wong
2006-10-19 19:37                     ` [gentoo-user] " Darren Kirby
     [not found]                   ` <200610191217.17509.bulliver@badcomputer.org>
2006-10-19 21:16                     ` [gentoo-user] [OT] " Justin Findlay
2006-10-18 21:27           ` [gentoo-user] Re: Re: " Alexander Skwar
2006-10-18  7:56       ` [gentoo-user] " Neil Bothwick
2006-10-18 18:23         ` Darren Kirby
2006-10-18 21:38           ` [gentoo-user] " Alexander Skwar
2006-10-18  3:44 ` [gentoo-user] " Brett I. Holcomb
2006-10-18  3:46 ` Brett I. Holcomb
2006-10-18  3:56 ` Drew
2006-10-18  4:00 ` Darren Kirby
2006-10-18 21:02   ` maxim wexler
2006-10-18 21:35     ` Darren Kirby
2006-10-19  0:06       ` maxim wexler
2006-10-19 10:09       ` Bo Ørsted Andresen
2006-10-19 18:23         ` Darren Kirby
2006-10-19 20:49           ` Daniel Barkalow
2006-10-18 21:49     ` Daniel Barkalow
2006-10-18 21:50     ` Neil Bothwick
2006-10-19  0:21     ` b.n.
2006-10-18  5:29 ` [gentoo-user] " Alexander Skwar
2006-10-18  8:01 ` [gentoo-user] " Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c52221f0610190738n2fedcf7bl6db11aba61c8cd3b@mail.gmail.com \
    --to=devon.c.miller@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox