=== Ursinha is now known as Ursinha-afk [03:12] skaet: fyi, something is not quite right with http://status.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html. bug 344878 has assignments in the bug, but the report is not picking it up [03:12] Launchpad bug 344878 in linux (Ubuntu Precise) (and 8 other projects) "file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) (affects: 75) (dups: 7) (heat: 448)" [High,In progress] https://launchpad.net/bugs/344878 [09:39] morning all [09:40] how would I go about getting jruby moved from multiverse to universe? [09:40] the latest Debian version has moved into main (it no longer bundles its deps) [09:41] file bug, subscribe ubuntu-archive [09:41] Laney: thanks [09:42] :-) [09:42] someone might Just Do It for you if they read the request on IRC, but bugs work. [09:43] well you neven know - I'll belt and braces it [09:48] if any archive admins do pick this up its a little complicated due to deps currently FTBFS - see bug 576980 for more information [09:48] Launchpad bug 576980 in jruby (Debian) (and 1 other project) "jruby ships prebuilt jar files in the orig tarball (affects: 1) (heat: 8)" [Unknown,Fix released] https://launchpad.net/bugs/576980 [09:52] stgraber: hm, well, it's unfortunate since we often do things like posting AMI sets from off antimony [09:52] stgraber: but I suppose it's tolerable in the shortish term === Ursinha-afk is now known as Ursinha [12:50] cjwatson: off antimony but still from a limited set of machines that we could whitelist or from random IPs (home internet for example)? [12:52] an alternative I thought about yesterday evening is to require an API key (send as a standard HTTP password), that should be just as easy to implement as the IP whitelisting (no need to have that hooked up with SSO + team membership, it'd just be linked to a QA tracker instance) [13:01] cjwatson: thinking about it for an extra 10 minutes, I'll store a list of valid qatracker userids + api key in a per-instance configuration key. So for any account where we want to give API access, we'll just need to generate a password (different from SSO) and add it to the list in the admin UI. [13:02] this should be easy for me to implement as the usernames are stored by Drupal, the password for the API will be store by the tracker and I don't need to go through the whole list of ACLs to figure out if the user is an admin or not as he'll be explicitly added by an admin [13:03] the only potential problem I see here is that for example an account used for Jenkins to post results will have just as much right as the account used to post new builds, so we'll need to be careful about who gets added to that list [13:03] stgraber: in my case it's home internet, although admittedly my IP doesn't change often [13:03] (if we had IPv6 then you could whitelist my tunnel range ;-) ) [13:04] API key> I suppose that's not too bad ... [13:06] I'll poke at the Drupal ACL api during my 5 hours ride through Maine, see if there's some easy way to check the ACLs from an xmlrpc module, if there's, then I'll just add the API key as a regular profile field for everyone and apply the same ACLs on xmlrpc as we have from the web interface [19:51] heads up: recipe builds et al is causing a rolling blackout while I upgrade the buildds for them. that is all. [21:11] jdstrand, weirdness with the report and bug 344878 was sorted out. All should be ok now. [21:11] Launchpad bug 344878 in linux (Ubuntu Precise) (and 8 other projects) "file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) (affects: 76) (dups: 7) (heat: 454)" [High,In progress] https://launchpad.net/bugs/344878 [21:11] cool