Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 5612 - rp-pppoe ebuilds
Summary: rp-pppoe ebuilds
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-26 12:03 UTC by Pierre-Henri Jondot
Modified: 2003-02-04 19:42 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
The rp-pppoe-3.3.ebuild (rp-pppoe-3.3.ebuild,773 bytes, text/plain)
2002-07-26 12:06 UTC, Pierre-Henri Jondot
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Henri Jondot 2002-07-26 12:03:24 UTC
rp-pppoe-3.4 ebuild is masked for sandbox violation reasons.

As long as rp-pppoe-3.3.ebuild was present, it was not a big issue, as
rp-pppoe-3.3 worked ok for the majority of people...

But now, rp-pppoe-3.4.ebuild is the only remaining rp-pppoe ebuild in the
portage tree...

Why did rp-pppoe-3.3 get removed ?
Comment 1 Pierre-Henri Jondot 2002-07-26 12:06:45 UTC
Created attachment 2607 [details]
The rp-pppoe-3.3.ebuild 

If it helps, here is the rp-pppoe-3.3.ebuild that is still present on one of my
gentoo boxes. (I did not emerge --clean rsync so recently on this one... Btw, I
do not quite agree on the change of policy concerning the fonctionning of
emerge rsync, as for cleaning I mean... but that is another story...)
Comment 2 SpanKY gentoo-dev 2002-07-26 18:16:22 UTC
i noted this in http://bugs.gentoo.org/show_bug.cgi?id=4615

gentoo has a habit of punting ebuilds for older versions, in this case i think 
3.3 got punted before 3.4 was masked
Comment 3 Seemant Kulleen (RETIRED) gentoo-dev 2002-07-27 02:42:43 UTC
sorry, I went a little nuts when cleaning out the portage tree. 3.3 is now back
in the directory.  And I hear 3.4 actually works.  If there are any more sandbox
issues with 3.4 please do reopen this bug report.