gmane.linux.gentoo.devel

Ciaran McCreesh | 9 Oct 20:52

EAPI 2 is brokened :(

Unfortunately Portage and Pkgcore have broken EAPI 2 implementations.
So far as I can see:

Portage:

* doesn't implement the 'default' function correctly for src_prepare.

Pkgcore:

* doesn't implement src_prepare
* doesn't have a working default
* default_src_configure and default_src_prepare are the only
default_s that work

Unfortunately, neither appears to have comprehensive unit tests
covering all new EAPI 2 functionality, so these got through into
package managers that made it into the tree.

This is a bit of a mess. Possible solutions are:

* Ignore it, and tell anyone using broken package managers to upgrade,
and deal with the resulting mess.

* Create a new EAPI 3 which is identical to EAPI 2. Make really really
sure Portage and Pkgcore implement it correctly before they go into the
tree. Deprecate EAPI 2, and convert everything using it to EAPI 3.

* Avoid using any broken feature, and retroactively remove the
definitions from EAPI 2. Unfortunately, this probably isn't viable
because of the src_prepare thing in Pkgcore (were it merely an

(Continue reading)

Doug Goldstein | 9 Oct 23:47

Re: EAPI 2 is brokened :(

Ciaran McCreesh wrote:
> Unfortunately Portage and Pkgcore have broken EAPI 2 implementations.
>   
<snip>

Ciaran, I would think at this point you know this since you've seen this
brought up hundreds of times on this list. The mailing list is not an
appropriate place to file bug reports. The proper place would be in
http://bugs.gentoo.org for Portage and http://www.pkgcore.org for pkgcore.

Ciaran McCreesh | 9 Oct 23:53

Re: EAPI 2 is brokened :(

On Thu, 09 Oct 2008 17:47:36 -0400
Doug Goldstein <cardoe <at> gentoo.org> wrote:
> Ciaran McCreesh wrote:
> > Unfortunately Portage and Pkgcore have broken EAPI 2
> > implementations. 
> <snip>
> 
> Ciaran, I would think at this point you know this since you've seen
> this brought up hundreds of times on this list. The mailing list is
> not an appropriate place to file bug reports. The proper place would
> be in http://bugs.gentoo.org for Portage and http://www.pkgcore.org
> for pkgcore.

Uh... The bugs have already been reported. This is supposed to be a
discussion about how to handle the fallout -- what do you feel you
gain by leaping to erroneous conclusions and making accusations?

--

-- 
Ciaran McCreesh

Brian Harring | 10 Oct 00:22

Re: EAPI 2 is brokened :(

On Thu, Oct 09, 2008 at 10:53:13PM +0100, Ciaran McCreesh wrote:
> On Thu, 09 Oct 2008 17:47:36 -0400
> Doug Goldstein <cardoe <at> gentoo.org> wrote:
> > Ciaran McCreesh wrote:
> > > Unfortunately Portage and Pkgcore have broken EAPI 2
> > > implementations. 
> > <snip>
> > 
> > Ciaran, I would think at this point you know this since you've seen
> > this brought up hundreds of times on this list. The mailing list is
> > not an appropriate place to file bug reports. The proper place would
> > be in http://bugs.gentoo.org for Portage and http://www.pkgcore.org
> > for pkgcore.
> 
> Uh... The bugs have already been reported. This is supposed to be a
> discussion about how to handle the fallout -- what do you feel you

Interestingly enough, I don't see a bug filed in either of those 
ticket systems.  I see an irc msg that's vague on details from you 
proceeding this email by an hour or so though.

Pkgcore EAPI2 support was released ~2 days ago; portage EAPI2 support 
was released 09/26, ~12 days ago.  So... not exactly a huge window.  
In addition, all *3* versions supporting EAPI2 are all unstable; 
meaning fairly rapid upgrade cycle by consumers of unstable, and 
not exactly likely to have versions lingering long term in peoples 
vdb.

So where exactly is this "sky is falling" issue you're worried about?  
Bugs happen.  I'd expect zac will fix whatever issue there is and

(Continue reading)

Ciaran McCreesh | 10 Oct 00:34

Re: EAPI 2 is brokened :(

On Thu, 9 Oct 2008 15:22:19 -0700
Brian Harring <ferringb <at> gmail.com> wrote:
> So where exactly is this "sky is falling" issue you're worried
> about? Bugs happen.

It means anyone using EAPI 2 now is going to encounter severe
breakages with Pkgcore. Simply put, all your Pkgcore users are going to
get screwed over very messily as soon as they try to use any EAPI 2
things. Is this not something we should be caring about?

> Frankly you're overreacting on this- and that is assuming you *are* 
> overreacting instead of just going for a bit of a public smear 
> via bugs.

Bah. If you want me to lecture you on how you're being blatantly
irresponsible and incompetent then I will do, although by the way you
rush on the defensive and start trying to cover your ass by throwing
accusations at me it looks like you already know it. But what I care
about is getting the mess fixed in the most painless way possible.

This is a real issue and developers need to know the implications.

> Either way, my vote is fix the bugs, leave EAPI2 as is, and in the 
> future kindly file bugs properly (preferably w/out the noise, but 
> I'll take usable bug reports in almost any form).

If you want bug reports via trac instead of IRC, get your trac to
respond faster.

--

--

(Continue reading)

Brian Harring | 10 Oct 01:38

Re: EAPI 2 is brokened :(

On Thu, Oct 09, 2008 at 11:34:59PM +0100, Ciaran McCreesh wrote:
> On Thu, 9 Oct 2008 15:22:19 -0700
> Brian Harring <ferringb <at> gmail.com> wrote:
> > So where exactly is this "sky is falling" issue you're worried
> > about? Bugs happen.
> 
> It means anyone using EAPI 2 now is going to encounter severe
> breakages with Pkgcore. Simply put, all your Pkgcore users are going to
> get screwed over very messily as soon as they try to use any EAPI 2
> things. Is this not something we should be caring about?

You're massively overreacting, either due to ignorance or due to 
trying to stir things up.

Tree currently has 308 ebuilds out of 25500 that are EAPI=2.  ~1.1% 
of the tree.

Of that 308, number of ebuilds that either inherit java-utils (which 
adds src_prepare), define their own src_prepare, or even *match* 
default via grepping in the ebuild is 20.

I reiterate.  20 out of 308 EAPI2 consumers, meaning that pkgcore 
misbehaved on .078% of the tree (all unstable ebuilds in addition, 
and haven't even counted how many are masked), and it did this for a 
window of a few days.

There is a difference between not caring about breakage, and gauging 
the affect of the breakage and dealing with it appropriately 
(triaging).

(Continue reading)

Ciaran McCreesh | 10 Oct 01:55

Re: EAPI 2 is brokened :(

On Thu, 9 Oct 2008 16:38:56 -0700
Brian Harring <ferringb <at> gmail.com> wrote:
> Of that 308, number of ebuilds that either inherit java-utils (which 
> adds src_prepare), define their own src_prepare, or even *match* 
> default via grepping in the ebuild is 20.

Of those, and those in overlays, and those that are going to be
committed over the next few weeks, how many use src_prepare to apply
security related patches?

> Also, if you want to bitch at me and call me incompetent do it via 
> your blog.  No one this ml cares to watch us trade blows, let 
> alone deal with personal BS that bleeds into your posts.

I'm not the one going around levelling personal attacks at everyone.

--

-- 
Ciaran McCreesh

Mart Raudsepp | 10 Oct 08:32

Re: EAPI 2 is brokened :(

On Fri, 2008-10-10 at 00:55 +0100, Ciaran McCreesh wrote:
> On Thu, 9 Oct 2008 16:38:56 -0700
> Brian Harring <ferringb <at> gmail.com> wrote:
> > Of that 308, number of ebuilds that either inherit java-utils (which 
> > adds src_prepare), define their own src_prepare, or even *match* 
> > default via grepping in the ebuild is 20.
> 
> Of those, and those in overlays, and those that are going to be
> committed over the next few weeks, how many use src_prepare to apply
> security related patches?

A round zero. Security patches are going stable soon after entering
portage tree, and EAPI=2 ebuilds can not go stable yet, as there is no
package manager supporting EAPI=2 that is going to be stable in the next
week or two (so maintainers make sure they don't use EAPI=2 for security
fix revisions).
And if the bug is there and properly filed to the appropriate bugzilla,
they wouldn't go stable before that bug is fixed (which I read are
already fixed).
I can not understand why this is dragged on. It was a bug, it is fixed.
The sky is not falling and EAPI-2 is not broken - there was a bug in the
implementation that is fixed.

--

-- 
Mart Raudsepp
Gentoo Developer
Mail: leio <at> gentoo.org
Weblog: http://planet.gentoo.org/developers/leio

Ciaran McCreesh | 10 Oct 15:56

Re: EAPI 2 is brokened :(

On Fri, 10 Oct 2008 09:32:44 +0300
Mart Raudsepp <leio <at> gentoo.org> wrote:
> > Of those, and those in overlays, and those that are going to be
> > committed over the next few weeks, how many use src_prepare to apply
> > security related patches?
> 
> A round zero. Security patches are going stable soon after entering
> portage tree, and EAPI=2 ebuilds can not go stable yet, as there is no
> package manager supporting EAPI=2 that is going to be stable in the
> next week or two (so maintainers make sure they don't use EAPI=2 for
> security fix revisions).

Oh really? So you're absolutely certain there aren't and won't soon be
any EAPI 2 bumps of non-EAPI 2 versions that include security patches?
And you're absolutely certain that there aren't, say, any packages that
sed a broken chmod in a makefile in src_prepare?

> I can not understand why this is dragged on. It was a bug, it is
> fixed. The sky is not falling and EAPI-2 is not broken - there was a
> bug in the implementation that is fixed.

The point of EAPI is to avoid these kinds of problems. The process is
failing and the fallout needs to be handled.

--

-- 
Ciaran McCreesh

Robert Buchholz | 10 Oct 19:03

Re: EAPI 2 is brokened :(

On Friday 10 October 2008, Ciaran McCreesh wrote:
> On Fri, 10 Oct 2008 09:32:44 +0300
>
> Mart Raudsepp <leio <at> gentoo.org> wrote:
> > > Of those, and those in overlays, and those that are going to be
> > > committed over the next few weeks, how many use src_prepare to
> > > apply security related patches?
> >
> > A round zero. Security patches are going stable soon after entering
> > portage tree, and EAPI=2 ebuilds can not go stable yet, as there is
> > no package manager supporting EAPI=2 that is going to be stable in
> > the next week or two (so maintainers make sure they don't use
> > EAPI=2 for security fix revisions).
>
> Oh really? So you're absolutely certain there aren't and won't soon
> be any EAPI 2 bumps of non-EAPI 2 versions that include security
> patches?

This would not affect stable users, as Mart pointed out. ~arch users 
should keep their systems up-to-date anyway (including their PM), and 
should be aware their security support is limited to providing updates.

Robert

Alec Warner | 10 Oct 09:05

Re: EAPI 2 is brokened :(

On Thu, Oct 9, 2008 at 3:34 PM, Ciaran McCreesh
<ciaran.mccreesh <at> googlemail.com> wrote:
> On Thu, 9 Oct 2008 15:22:19 -0700
> Brian Harring <ferringb <at> gmail.com> wrote:
>> So where exactly is this "sky is falling" issue you're worried
>> about? Bugs happen.
>
> It means anyone using EAPI 2 now is going to encounter severe
> breakages with Pkgcore. Simply put, all your Pkgcore users are going to
> get screwed over very messily as soon as they try to use any EAPI 2
> things. Is this not something we should be caring about?

I think everyone appreciates the forewarning (even if not everyone
appreciates the manner in which it was delivered).  I think we do care
and we are fixing it.  I believe the developers of said packages have
a different idea of the risks involved than you and I don't expect
everyone to agree on specific software development or release
processes.

>
>> Frankly you're overreacting on this- and that is assuming you *are*
>> overreacting instead of just going for a bit of a public smear
>> via bugs.
>
> Bah. If you want me to lecture you on how you're being blatantly
> irresponsible and incompetent then I will do, although by the way you
> rush on the defensive and start trying to cover your ass by throwing
> accusations at me it looks like you already know it. But what I care
> about is getting the mess fixed in the most painless way possible.
>

(Continue reading)

Zac Medico | 10 Oct 00:19

Re: EAPI 2 is brokened :(


Ciaran McCreesh wrote:
> Unfortunately Portage and Pkgcore have broken EAPI 2 implementations.
> So far as I can see:
> 
> Portage:
> 
> * doesn't implement the 'default' function correctly for src_prepare.

This is fixed and released in sys-apps/portage-2.2_rc12.

> None of these are very nice. Better options would be encouraged... We
> have to do *something*, though, because this is hitting users already
> (see bug 240684 for one).

Like I said in the council thread, I think you may be overreacting.
No version of sys-apps/portage that supports EAPI 2 has been marked
stable yet so the fact that some unstable versions were a little
buggy is not a big problem since unstable users tend to upgrade
relatively frequently and sys-apps/portage is promoted to the from
of the merge list anyway.
--
Thanks,
Zac

Return

Return to gmane.linux.gentoo.devel.

Advertisement

Search Archive

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane