Summary: | rp-pppoe-3.5-r9 fails to store username | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | genbug |
Component: | [OLD] Unspecified | Assignee: | Gentoo Dialup Developers <net-dialup> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
genbug
2005-04-24 04:22:24 UTC
indeed, there is a problem regarding password saving, but it has nothing to do with what you described. the problem is that adsl-setup edit chap-secrets with typed username and password. workaround: re-enter username every time you run adsl-setup Indeed you are right, I've just checked. So rp-pppoe is going to break everyone's connect after the first use. So if it is as fundementally broken as that why is r9 not hard masked? This cost me a lot of time and about 3days without a working connection. Less experienced users will be completely lost. This is supposed to be the current "stable " version isn't it? because main functionality isn't broken and most users don't use adsl-setup anyway. what would you do if I'd mask the rp-pppoe? I will fix it in r10, but I am waiting input in other 2 bugs related to rp-pppoe. please don't change status of this bug Well a util to help set up an adsl connection that causes a working connection to no longer connect . You dont get much more broken than that.
There's no indication this is a once only tool . So major functionality not only fails to work but actually does dammage to a working system.
>>most users don't use adsl-setup
Those that do probably can't connect anymore , so that conclusion may be ill-founded.
I would have thought the severity of this bug would warrent and immediate fix -it would not seem to be a big issue technically.
This is the ONLY version still in portage. It is broken and not fully tested.
I had a working setup with r7 (apparently r2 worked as well). The r7 ebuild was pulled without a working replacement.
If r10 is not available earlier versions should be put back in the tree a.s.a.p to prevent more systems going off line due this careless bug.
This is exactly the type of situation that makes Gentoo unreliable and a headache to maintain.
The lack of will to rectify only adds to the level and extent of user frustrations.
Sorry to sound off, but I have wasted far too much time with kind of problem on Gentoo. It is completely unnecessary.
fixed in r10. Thanks for the fix in r10. I see you've marked it as fixed. Does that mean you have released r10? Is that scheduled for immediate release or is it necessary to open a bug against portage that currently only has one , broken copy of this package? synchronize your portage tree by issuing "emerge --sync" I'll take that as " affirmative captain" ;) I did that just proir to posting but it obviously had not propagated to the mirror I got. I'll re-sync if it's not too early. Thanks for the speedy response on this , hopefully it will avoid others falling into the same trap I did. Cheers. |