| 1 |
Patrick Lauer wrote: |
| 2 |
> On Thu, 2006-06-08 at 20:06 -0400, Chris Gianelloni wrote: |
| 3 |
|
| 4 |
>> Again, read what I wrote. I said that the developer would see "sunrise" |
| 5 |
>> in the PORTDIR_OVERLAY of the user's emerge --info, which you reiterated |
| 6 |
>> without considering. This is a login bug. At no point did they make |
| 7 |
>> mention of having installed pam_skey from this overlay. This means that |
| 8 |
>> I, as the developer getting this bug, am now responsible for looking at |
| 9 |
>> *every package* in the sunrise overlay to determine if *any* of them |
| 10 |
>> could *possibly* be affecting this package or causing this bug, then |
| 11 |
>> asking the user if they have any of them installed. |
| 12 |
> This differs from a manually patched ebuild in /usr/portage by virtue of showing you that an overlay is used ... |
| 13 |
> |
| 14 |
>> Wouldn't this process be *infinitely* easier if instead of "sunrise" |
| 15 |
>> there was a "pam" overlay with *only* the pam stuff? |
| 16 |
> Ooooh, cool. Now I need about 75 overlays to get things done, and of course there will be no bad interaction between them ;-) |
| 17 |
|
| 18 |
Please, leave pam_skey alone. ;) It's a thing I'm using daily and the |
| 19 |
default system-auth config file installed by this ebuild allows for both |
| 20 |
system and S/KEY passwords to be used at the same time, you can pick |
| 21 |
whichever one you want. There's no way to get yourself locked out of |
| 22 |
system unless you've already forgotten your normal password and didn't |
| 23 |
yet set up OTP, in which case, it's not pam_skey problem at all. |
| 24 |
|
| 25 |
The thing has been sitting in bugzilla for ages, I've asked Flameeyes to |
| 26 |
commit it and he said he's not going to put any mode pam stuff into the |
| 27 |
tree unless he's using the modules himself. Nothing wrong w/ that. So, I |
| 28 |
can either keep on maintaining it in my local overlay or let other |
| 29 |
people use it if they find it useful. I prefer the latter. pam_abl and |
| 30 |
pam_mount is also stuff that I'm testing/using myself. The only thing I |
| 31 |
haven't tested beyond "it compiles and installs" is pam_pgsql, that one |
| 32 |
doesn't touch system-auth at all, comes w/ commented-out .conf and so |
| 33 |
has no effect until the user has configured it. |
| 34 |
|
| 35 |
There are about 3 other bugs requesting pam stuff, but since that stuff |
| 36 |
is essentially dead upstream, it won't be in the overlay. So, are you |
| 37 |
asking to have a separate overlay project for 4 pam ebuilds? Heh, really |
| 38 |
an overkill. |
| 39 |
|
| 40 |
> Could be part of the policy to not touch existing ebuilds. |
| 41 |
|
| 42 |
IMHO the sunrice project is a good place for maintainer-wanted/needed |
| 43 |
bugs. Shouldn't be a dumpspace for whatever experimental patches for |
| 44 |
stuff that's actually being maintained in the main tree. |
| 45 |
|
| 46 |
>> This is a prime example of totally glossing over any discussion to make |
| 47 |
>> it sound promising for you. |
| 48 |
> If bugzilla wasn't so sucky people wouldn't try to use other methods of |
| 49 |
> communication ;-) |
| 50 |
|
| 51 |
Erm, look at the vmware-server bug |
| 52 |
(http://bugs.gentoo.org/show_bug.cgi?id=122500) . It's vastly useless |
| 53 |
for grabbing any ebuilds, there are ~350 comments and tons of obsolete, |
| 54 |
yet not marked as such ebuilds, that's why you switched to subversion, |
| 55 |
right? And it boosted the effectivity by a huge margin. Also comes w/ a |
| 56 |
nice side-effect of not bugspamming another 200 folks CCed on the bug |
| 57 |
when someone screws w/ attachments for a couple of times. |
| 58 |
|
| 59 |
|
| 60 |
-- |
| 61 |
Best regards, |
| 62 |
|
| 63 |
Jakub Moc |
| 64 |
mailto:jakub@g.o |
| 65 |
GPG signature: |
| 66 |
http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E |
| 67 |
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E |
| 68 |
|
| 69 |
... still no signature ;) |
Archives