Summary: | mesa/drm account request | ||
---|---|---|---|
Product: | freedesktop.org | Reporter: | vehemens |
Component: | New Accounts | Assignee: | fd.o Admin Massive <sitewranglers> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | airlied, brian.paul |
Version: | unspecified | Keywords: | NEEDINFO |
Hardware: | Other | ||
OS: | FreeBSD | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
ssh public key
gpg public key as an attachment |
Description
vehemens
2008-08-10 14:13:06 UTC
Created attachment 18294 [details]
gpg public key as an attachment
Howdy, I'll need to know what project your working on. Also you'll need to get approval from a project lead before you can get an account. On Monday 18 August 2008 06:46:58 pm bugzilla-daemon@freedesktop.org wrote: > http://bugs.freedesktop.org/show_bug.cgi?id=17062 > > > Benjamin Close <Benjamin.Close@clearchain.com> changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- Keywords| |NEEDINFO > > > > > --- Comment #2 from Benjamin Close <Benjamin.Close@clearchain.com> > 2008-08-18 18:46:58 PST --- Howdy, I'll need to know what project your > working on. Also you'll need to get approval from a project lead before you > can get an account. I after access to the mesa/drm project. Most of my initial work will be with bsd-core. I'm assuming that the project lead would be Brian Paul which I added to this email. I would like to change this request to a new project request. Please call it drm-shared and repro the drm project master branch. (In reply to comment #4) > I would like to change this request to a new project request. Please call it > drm-shared and repro the drm project master branch. Not without Dave's approval, and you'd still need Brian's approval to commit to Mesa. vehemens, I vaguely remember seeing your email address before but I don't recall ever seeing any Mesa patches/etc from you (I could be forgetting). Can you say more about what you want to do in Mesa? It sounds like you're moreso interested in drm. On Friday 29 August 2008 04:12:11 am bugzilla-daemon@freedesktop.org wrote: > http://bugs.freedesktop.org/show_bug.cgi?id=17062 > > > Daniel Stone <daniel@fooishbar.org> changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- CC| |airlied@freedesktop.org, > > | |brian.paul@tungstengraphic > | |s. com > > --- Comment #5 from Daniel Stone <daniel@fooishbar.org> 2008-08-29 > 04:12:09 PST --- (In reply to comment #4) > > > I would like to change this request to a new project request. Please > > call it drm-shared and repro the drm project master branch. > > Not without Dave's approval, and you'd still need Brian's approval to > commit to Mesa. If you mean Dave Airie, he already suggested a bsd-master branch on dri-devel in the "DRM development process wiki page.." thread. This is intended to be one step better. I won't request mesa commit access at this time if it's going to be difficult to get. That's Brain's call. On Friday 29 August 2008 08:07:51 am bugzilla-daemon@freedesktop.org wrote: > http://bugs.freedesktop.org/show_bug.cgi?id=17062 ... > --- Comment #6 from Brian Paul <brian.paul@tungstengraphics.com> > 2008-08-29 08:07:50 PST --- vehemens, I vaguely remember seeing your email > address before but I don't recall ever seeing any Mesa patches/etc from you > (I could be forgetting). Can you say more about what you want to do in > Mesa? It sounds like you're moreso interested in drm. Any near term Mesa work would be limited to BSD build options which I can do as local patches, so I really don't need access at this time. Probably should of said that earlier :/ How goes my project request? So near but so far. You need a signing+encrypting GPG key to get a fd.o account or userdir-ldap gets very upset, so you should add an encryption subkey to this key. (other than that, Dave Airlie approved the account creation, but I'm leaving NEEDINFO due to the key) I thought I has created the ssh and gpg keys per the account request page instructions. Did I miss a step, or is this something in addition to what's documented? I would very much like to get this account issue resolved, but cannot do it without some assistance. If I need a "signing+encrypting GPG key", please provide detailed instructions on how to create one. This is a request for help in generating the keys in the form required as the instructions are not clear in this area. I would appreciate help in closing this issue. I don't know anything about key generation either. I'm adding Robert McQueen to the cc list. Robert? Hmm, looks like this has got lost in the either - sorry about that. The problem is your gpg key doesn't support encryption, only signing: benjsc@wolf:~/work/gnome.o/gtk+| gpg --edit-key Keighley gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information pub 4096R/A16EABBD created: 2008-08-10 expires: never usage: SC trust: unknown validity: unknown [ unknown] (1). John Keighley (freedesktop.org account) <vehemens@verizon.net> Command> Notice there is no 'E' option for 'usage' on the key. A key that supports encryption does have this ie: pub 1024D/4842B5B4 created: 2002-04-10 expires: never usage: SC trust: ultimate validity: ultimate sub 2048g/3FA8A57E created: 2002-04-10 expires: never usage: E [ultimate] (1). Benjamin Simon Close <Benjamin.Close@clearchain.com> [ultimate] (2) Benjamin Simon Close <benjsc@FreeBSD.org> Without an encryption key we can't create your account as we encrypt using the key to send you your details. If you could generate a key with encryption and attach it to this bug (please remove the 'NEEDINFO' keyword as well) and I'll create your account. To create a key you can use: gpg --gen-key Just make sure when presented with the menu you DONT chose a 'sign only' key. Ping ping 2 No response from submitter, rejecting this request. Please reopen if you still want this done and have an updated gpg key or need help. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.