kirkland | okay, so a team that I'm a member of is subscribed to all bugs against a certain project | 00:21 |
---|---|---|
kirkland | can i exclude myself from that bug mail, without leaving the team? | 00:21 |
kirkland | sans procmail/filters | 00:21 |
wgrant | No. | 00:21 |
mwhudson | is this one of the things that's going to be fixed sooner or later? | 00:22 |
wgrant | There's no way to do that at the moment, unless the team has a contact address set, in which case bugmail will go there instead. | 00:22 |
micahg | kirkland: I think this is bug 204980 | 00:22 |
ubot5 | Error: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/204980) | 00:22 |
wgrant | Not really. | 00:23 |
mwhudson | by 'sooner or later' i mean, in the current work that's being done on bug subscriptions | 00:23 |
wgrant | mwhudson: I think so. | 00:23 |
mwhudson | awesome | 00:23 |
kirkland | dang | 00:23 |
* mwhudson doesn't really want to get all bzr bug mail & merge proposal mail | 00:23 | |
kirkland | okay, yeah, that's it | 00:23 |
micahg | kirkland: I think the workaround is to make a ML for the team and the people interested can subscribe to the list | 00:24 |
micahg | and set the ML as the contact address | 00:24 |
micahg | kirkland: bug 75620 is also related | 00:26 |
ubot5 | Launchpad bug 75620 in Launchpad Bugs "bug contacts should be able to unsubscribe from implicit subscriptions (affected: 5, heat: 45)" [High,Triaged] https://launchpad.net/bugs/75620 | 00:26 |
* micahg kicks ubot5 for providing incorrect information | 00:26 | |
KombuchaKip | Hey room. I've just added some blueprints to my launchpad project. I'd like the public to be able to discuss and provide feedback on them. I don't see a "wall" or some such though. | 02:16 |
spiv | KombuchaKip: there's the "whiteboard" | 02:19 |
KombuchaKip | spiv: I see it, but I don't quite know how it works. I'll see if I can dig up some documentation. | 02:19 |
KombuchaKip | spiv: I'm looking here https://help.launchpad.net/BlueprintDocumentation but I don't see anything for feedback and discussion. | 02:21 |
spiv | Yeah. The whiteboard isn't a particularly good spot for discussion, but I think it's the best that's builtin. | 02:23 |
KombuchaKip | spiv: Hmm, I suppose IRC will do. | 02:24 |
spiv | You could also create a mailing list for the project. | 02:25 |
spiv | (but there's no per-blueprint discussion forum in launchpad that I know of) | 02:25 |
KombuchaKip | spiv: Right. I think I'll create a mailing list then. I don't think you can create one for a project though, only for a team. And even then, I think you can only create one, no? | 02:27 |
spiv | KombuchaKip: yeah, they are a team thing. But that doesn't especially matter: if you put "the mailing list is here: <URL>" in the launchpad project description and your project's README etc people will find it. | 02:31 |
KombuchaKip | spiv: True enough | 02:31 |
* KombuchaKip can't help but wonder why deleting a launchpad project mailing list takes so long. | 03:08 | |
CarlFK | I have the source and debian dir on my box. I want to package it for maverick on my ppa. I know I need to add a maveirck changelog entry. then run something that uploads it. did all this a year ago... made notes somewhere | 04:03 |
CarlFK | anyone know a URL that describes what I need, that isn't 1000 lines long (I seem to remember lots of details for stuff I didn't need | 04:03 |
CarlFK | actually I think it is 2 commands - one to build -src and diff, one to upload | 04:04 |
wgrant | dch -i | 04:05 |
wgrant | <edit changelog> | 04:05 |
wgrant | debuild -S | 04:05 |
wgrant | dput ../foo_bar_source.changes | 04:05 |
wgrant | Er. | 04:06 |
wgrant | dput ppa:USERNAME/PPA ../foo_bar_source.changes | 04:06 |
CarlFK | thanks | 04:07 |
lifeless | wgrant: debrelease --dput ppa:USERNAME/PPA | 04:07 |
lifeless | or is it debupload. I forget. | 04:08 |
wgrant | Oh, handy. | 04:08 |
CarlFK | hmm, I found: debuild -k 80E61AF4 -S -sa | 04:08 |
CarlFK | in a script that I guess does what I need. yay. I think. be good if I knew what it was doing... | 04:09 |
wgrant | -S => source only; no binaries | 04:09 |
wgrant | -sa => upload orig.tar.gz | 04:09 |
wgrant | -k => sign with this key ID | 04:09 |
CarlFK | lifeless: it is both ;) man debrelease - a wrapper around dupload or dput | 04:14 |
CarlFK | er, dup.., not debup - meh. | 04:15 |
CarlFK | " Step 1 Open Passwords and Encryption Keys. Step 2 Select the My Personal Keys tab, select your key. Step 3 Select Remote > Sync and Publish Keys from the menu. Choose the Sync button." | 04:28 |
CarlFK | did that. um.. how did it know who I am ? | 04:28 |
wgrant | CarlFK: How do you mean? | 04:32 |
CarlFK | wgrant: good Q. i guess it is just someones public key, and whoever has the private part (me) can make use of it. um... yeah. | 04:33 |
CarlFK | I was expecting to have to authenticate with the key server when I sent it my public key | 04:34 |
wgrant | You did, with your private key's signature on your public key. | 04:34 |
CarlFK | why doesn't this return anything? carl@dc10:~$ gpg --fingerprint | 04:36 |
CarlFK | ah, cuz it's the wrong flavor of key... | 04:38 |
wgrant | Nothing at all? | 04:38 |
CarlFK | right. I dont have a pgp - just ssh/rsa? | 04:38 |
wgrant | That could be a problem, if you only have an SSH key. | 04:39 |
CarlFK | should it take more than 60 seconds to gen a key? | 04:43 |
CarlFK | looks like we are over 3 min | 04:43 |
lifeless | are you doing it on your local machine | 04:44 |
lifeless | or remotely? | 04:44 |
CarlFK | local | 04:44 |
lifeless | tap some keys :) | 04:44 |
lifeless | CarlFK: if you did this a year ago, you must have a gpg key already | 04:45 |
CarlFK | yeah, but I accedently mkfs-ed my home partition. doh. | 04:45 |
lifeless | ahhhh | 04:46 |
CarlFK | had most of my stuff backed up... but not my key. | 04:46 |
lifeless | no backups ? | 04:46 |
lifeless | meep, ouch. | 04:46 |
wgrant | Well, keys arguably shouldn't be in with your normal backups anyway. | 04:46 |
CarlFK | all my code is in remote repos. config files I give a crap about I stuff on another box. so I thought i was covered. doh. | 04:47 |
poolie | thumper: hi, can you answer https://bugs.launchpad.net/bugs/674581 | 04:53 |
ubot5 | Launchpad bug 674581 in Launchpad Bazaar Integration "Sourceforge Mercurial Import Fails (affected: 1, heat: 6)" [Undecided,New] | 04:53 |
poolie | iow "can we import from hg on sourceforge"? | 04:54 |
CarlFK | https://help.launchpad.net/ReadingOpenPgpMail#Google%20mail%20%28Gmail%29 "FireGPG Firefox plugin is perfect for this task." click... " I removed Gmail support... and put it officially in ‘discontinued’ state." | 05:04 |
poolie | CarlFK: you were the maintainer of the plugin? | 05:17 |
CarlFK | nope | 05:17 |
CarlFK | those are quotes from the 2 pages | 05:18 |
CarlFK | not sure how appropiate, but here is my solution: select text in gmail, $ xclip -o | gpg2 -d | 05:19 |
CarlFK | i dont think xclip is installed by default | 05:19 |
poolie | probably not | 05:20 |
* wgrant is boring and uses a real email client. | 05:20 | |
poolie | feel free to edit that page | 05:20 |
CarlFK | https://help.launchpad.net/UserPreferences/ Logged in as carlfk "This email already belongs to somebody else." um.. what ?! | 05:30 |
wgrant | CarlFK: Do you have two Launchpad or Ubuntu SSO accounts? | 05:31 |
CarlFK | I hope not. I try to avoid multiple accounts | 05:31 |
CarlFK | https://help.launchpad.net/ReadingOpenPgpMail shows "Logged in as carlfk" but I don't see an edit link | 05:34 |
CarlFK | I seem to remember a tool bar floating around. don't see anything like that | 05:36 |
CarlFK | and back on ppa: dput ppa:carlfk/PPA ../dvswitch_0.9~alpha-0.3_source.changes; .... Uploading to ppa (via ftp to ppa.launchpad.net): Uploading dvswitch_0.9~alpha-0.3.dsc: done. Uploading dvswitch_0.9~alpha-0.3.tar.gz: done. Uploading dvswitch_0.9~alpha-0.3_source.changes: done. Successfully uploaded packages. | 05:39 |
CarlFK | but https://launchpad.net/~carlfk/+archive/ppa "0 updates added during the past month." | 05:39 |
CarlFK | dput was done at least 10 min ago | 05:40 |
CarlFK | " Could not find a PPA named 'PPA' for 'carlfk'." | 05:58 |
CarlFK | trying dput ppa:carlfk/ppa | 06:01 |
spiv | CarlFK: yes, lowercase matches the URL https://launchpad.net/~carlfk/+archive/ppa | 06:01 |
CarlFK | spiv: thanks. | 06:02 |
CarlFK | Currently 1 package building - yay | 06:07 |
CarlFK | gpgv: Signature made Tue Nov 16 06:00:09 2010 UTC using RSA key ID 17901261 gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./dvswitch_0.9~alpha-0.5.dsc | 06:15 |
CarlFK | http://launchpadlibrarian.net/59188187/buildlog_ubuntu-maverick-i386.dvswitch_0.9~alpha-0.5_BUILDING.txt.gz | 06:15 |
CarlFK | should I be concerned about that? | 06:15 |
wgrant | No. | 06:21 |
wgrant | It built successfully. | 06:21 |
wgrant | CarlFK: ^^ | 06:21 |
CarlFK | k - thanks. | 06:24 |
CarlFK | "Builds: i386 - Pending publication" Is that why there is no http://ppa.launchpad.net/carlfk/ppa/ubuntu/dists/maverick/main/binary-i386/Packages.gz ? | 06:34 |
wgrant | CarlFK: Yes. | 06:35 |
wgrant | However, it should have been published about 20 minutes ago. | 06:36 |
wgrant | So something might be broken. | 06:36 |
CarlFK | this works: wget https://launchpad.net/~carlfk/+archive/ppa/+build/2048738/+files/dvswitch_0.9%7Ealpha-0.5_i386.deb; dpkg -i ... | 06:46 |
wgrant | Yeah, that will work. | 06:47 |
wgrant | But the publisher is broken, so it won't appear on ppa.launchpad.net yet. | 06:47 |
CarlFK | which makes me very happy. I was expecting a depandancy problem or something | 06:47 |
CarlFK | wgrant: publisher is broken - do I need to file a bug report or anything? | 07:02 |
wgrant | CarlFK: No, it's a general operational issue which needs a sysadmin. | 07:03 |
wgrant | I have poked. | 07:03 |
CarlFK | thanks | 07:03 |
CarlFK | figured. jus making sure. | 07:03 |
=== LinuxJedi|away is now known as LinuxJedi | ||
ixokai | I haven't been able to log into lp for weeks now (and despite lp sending me email, the 'reset password' bit doesn't send anything-- yes i checked spam); and two separate submissions to the "login" support form for this time have been as of yet totally silent. Anyone have an idea of somewhere/someone I can contact more directly? | 08:01 |
wgrant | ixokai: Could you open a support case at https://forms.canonical.com/lp-login-support/? | 08:02 |
ixokai | Done that, twice | 08:03 |
ixokai | Once nearly three weeks ago, again a week+ish ago | 08:03 |
ixokai | Okay, slight exaggeration on number of weeks; gmail claims the first report was Oct 31, second Nov 4 | 08:11 |
ixokai | But no response. So trying to find if there's a more direct/alternate method of contact. | 08:11 |
poolie | ixokai: asking here is probably the most direct way | 08:18 |
ixokai | poolie: Okay, thanks. I'll ping off during business hours and see if anyone's around to help then. :) | 08:20 |
poolie | mthaddon is going to look at it now, i think | 08:21 |
glen | hi, i was wondering, whether 0day ftp hackers have used launchpad to share ftp site passwords or not? i noticed weird ticket created with odd attachment | 08:43 |
spiv | glen: it's often best to spam and other misuse at https://answers.launchpad.net/launchpad/ | 08:58 |
glen | oka, thanks. filed https://answers.launchpad.net/launchpad/+question/134251 | 09:05 |
=== Guest86531 is now known as jelmer | ||
zyga | hi | 10:49 |
zyga | I have a build recipe that works fine for lucid and maverick but fails to build packages for natty | 10:49 |
zyga | https://code.launchpad.net/~linaro-infrastructure/+recipe/linaro-python-json-daily-build/+build/7088 | 10:49 |
zyga | is this expected? | 10:49 |
wgrant | zyga: Recipe builds aren't support on natty yet. | 11:01 |
zyga | wgrant, I see, thanks | 11:02 |
zyga | wgrant, so I should use regular dput source package to get it to build on natty? | 11:02 |
wgrant | zyga: That's right. | 11:02 |
=== almaisan-away is now known as al-maisan | ||
=== al-maisan is now known as almaisan-away | ||
gnomefreak | for some reason i keep getting an OOPS when trying to add a source package to a bug report. here is the OOPS i just got Error ID: OOPS-1781EA207 | 11:52 |
ubot5 | https://lp-oops.canonical.com/oops.py/?oopsid=1781EA207 | 11:52 |
=== mrevell is now known as mrevell-lunch | ||
=== Ursinha-afk is now known as Ursinha | ||
=== mrevell-lunch is now known as mrevell | ||
geser | does somebody know if fetching attachments from private bugs over the LP API is expected to work? | 14:22 |
lifeless | geser: not currently, we're still fixing it | 14:24 |
lifeless | geser: as it happens I was talking to sysadmins just today about progress on that. | 14:24 |
geser | lifeless: any guess when it's expected to get fixed? So I can add a comment to a bug about it | 14:26 |
lifeless | geser: out of my control, sorry. | 14:26 |
geser | ok, thanks anyway. At least I know that not the script it buggy. | 14:28 |
geser | lifeless: do you know if there is a bug about it to which I could subscribe to watch the progress? | 14:30 |
=== Ursinha is now known as Ursinha-lunch | ||
lifeless | geser: https://bugs.launchpad.net/launchpad-foundations/+bug/395960 | 14:35 |
ubot5 | Launchpad bug 395960 in Launchpad Foundations "proxying user supplied libarian files via the launchpad appserver domain has security and performance issues (affected: 3, heat: 23)" [High,Fix committed] | 14:36 |
=== LinuxJedi is now known as LinuxJedi|away | ||
=== matsubara is now known as matsubara-lunch | ||
=== chrisccoulson_ is now known as chrisccoulson | ||
=== Ursinha-lunch is now known as Ursinha | ||
=== TheUni__ is now known as TheUni | ||
=== TheUni is now known as Guest17020 | ||
=== zyga is now known as zyga-afk | ||
=== Lcawte|Away is now known as Lcawte | ||
=== LinuxJedi|away is now known as LinuxJedi | ||
=== You're now known as ubuntulog | ||
=== LinuxJedi is now known as LinuxJedi|away | ||
=== You're now known as ubuntulog_ | ||
=== You're now known as ubuntulog | ||
=== matsubara-lunch is now known as matsubara | ||
=== yofel_ is now known as yofel | ||
=== zyga-afk is now known as zyga | ||
shadeslayer | whats the difference between a virtual builder and a virtual-64 builder? | 17:31 |
shadeslayer | for eg: meitnerium (virtual-64) and papaya (virtual) | 17:31 |
maxb | shadeslayer: At a guess, I would say that you can virtualize a 32 bit CPU on a 64 bit host CPU, but you can't virtualize a 64 bit CPU on a 32 bit host. | 17:49 |
shadeslayer | ohk... | 17:50 |
maxb | Hence only some virtual builders can take on amd64 build roles | 17:50 |
shadeslayer | seems logical | 17:50 |
=== LinuxJedi|away is now known as LinuxJedi | ||
zyga | hmm, is package building very fragile (build recipes) | 18:46 |
zyga | I had a PPA with three packages that built fine | 18:46 |
zyga | I changed the recipies to build in a different PPA and requested a rebuild | 18:47 |
zyga | and one of the packages failed to build for lucid (while building successfuly for maverick) | 18:47 |
zyga | it broke because of missing dependency of something that is in the very same ppa | 18:47 |
zyga | the maverick build picked up the same package but raised loud warnings about untrusted packages | 18:48 |
zyga | is each virtual builder on some separate archive that needs to be synchronized somehow? | 18:49 |
maxb | No, it is not fragile. You should give links to the specific build logs you have questions about so people can answer more usefully | 18:54 |
zyga | maxb, sure | 18:54 |
zyga | https://code.edge.launchpad.net/~linaro-infrastructure/+recipe/linaro-python-dashboard-bundle-daily-build | 18:55 |
zyga | so this package has just failed to build twice for lucid | 18:55 |
zyga | and worked for maverick | 18:55 |
zyga | I could not figure out why the dependency did not work for one vs the other by reading build logs | 18:56 |
maxb | The dependency itself failed to build on lucid | 18:57 |
maxb | Therefore it is not available | 18:57 |
zyga | hmm, that's odd AFAIR it exists on lucid | 18:57 |
zyga | maxb, how did you determine that it failed to build on luicid | 18:58 |
maxb | https://code.edge.launchpad.net/~linaro-infrastructure/+archive/launch-control-snapshots/+packages | 18:58 |
zyga | you are correct, somehow the view I'm looking at on my other computer did not show that failure | 18:59 |
zyga | hmm | 19:00 |
zyga | even stranger | 19:00 |
zyga | https://code.edge.launchpad.net/~linaro-infrastructure/+recipe/linaro-python-json-daily-build | 19:00 |
zyga | apparently it built fine 3 hours ago | 19:00 |
zyga | so? | 19:00 |
zyga | in particular here: https://code.edge.launchpad.net/~linaro-infrastructure/+recipe/linaro-python-json-daily-build/+build/7776 | 19:01 |
maxb | zyga: The build of branch->source package succeeded. The build of source package->binary package did not. | 19:02 |
zyga | I don't understand | 19:02 |
zyga | what is branch->source vs source -> binary? | 19:03 |
maxb | First there is a process which takes one of more bazaar branches and produces a Debian source package. | 19:03 |
zyga | okay I understand | 19:03 |
maxb | Second, and entirely separately, there are one or more builds of that Debian source package. | 19:04 |
zyga | so the status page is highly confusing | 19:04 |
maxb | Which status page? | 19:04 |
zyga | https://code.edge.launchpad.net/~linaro-infrastructure/+recipe/linaro-python-json-daily-build | 19:04 |
zyga | this one | 19:04 |
zyga | it says "Successful build" ... "Lucid" ... "Launch Control Snapshots" | 19:04 |
maxb | Ah, yes. The term "build" is excessively overloaded | 19:05 |
zyga | and (which is far worse) it does not make any note of the error | 19:05 |
maxb | zyga: Can you click to retry the failed build? | 19:05 |
zyga | maxb, yes | 19:05 |
zyga | maxb, why the binary build failed then? | 19:05 |
maxb | if so, try it. I am guessing that something went wrong with the builder, or it was withdrawn from service, during the build | 19:06 |
zyga | maxb, I'm reading the log but it seems a failure to resolve dependency on one of the non-ppa packages | 19:06 |
maxb | Which log? I see no log available | 19:06 |
maxb | https://code.edge.launchpad.net/~linaro-infrastructure/+archive/launch-control-snapshots/+build/2049318 <-- no log | 19:06 |
zyga | hmm | 19:07 |
zyga | you are right, perhaps I was confused but I could sworn that I just read that log file | 19:07 |
zyga | too many computers/tabs | 19:07 |
zyga | I'm retrying the build | 19:08 |
zyga | is it sensible to ask for a better status page that has separate status for the first and second "build" phase? | 19:08 |
maxb | Yes, I think it is very sensible. It is a critical flaw in the recipe page | 19:09 |
zyga | okay, it worked | 19:12 |
zyga | darn, I exceeded my daily quota :-) | 19:14 |
zyga | oh well | 19:14 |
maxb | daily quota? | 19:14 |
zyga | time to call it a day | 19:14 |
zyga | that's what the page said when I requested a rebuild of the python-linaro-dashboard-bundle that failed due to missing dependency before | 19:15 |
maxb | ah, I didn't even know there was a recipe daily quota | 19:15 |
maxb | however, rather than requesting a new build, are you able to retry the previous one? | 19:15 |
zyga | maxb, I did that - it worked (as I said) | 19:16 |
zyga | maxb, I requrested a new build of the package I originally discussed | 19:16 |
zyga | the one that failed because of missing python-linaro-json | 19:16 |
maxb | Yes but there is a subtle difference between requesting a new build and retrying a previous request | 19:16 |
zyga | hmm, let's see | 19:17 |
maxb | In any case, wait until the binary of python-linaro-json has been published | 19:17 |
zyga | https://code.edge.launchpad.net/~linaro-infrastructure/+recipe/linaro-python-dashboard-bundle-daily-build/+build/7795 | 19:17 |
zyga | I see | 19:17 |
zyga | there is a separate publishing state? | 19:17 |
zyga | there is no option to retry the build on that page | 19:17 |
maxb | Oh | 19:17 |
maxb | Maybe you can't retry recipe builds, then | 19:18 |
zyga | maxb, thanks for your help :-) | 19:20 |
maxb | np | 19:20 |
matsubara | maxb, hi there, I changed the bzr-pqm recipe to be owned by ~launchpad-committers, added a link to the dev.l.n/LaunchpadPpa and requested a new build for maverick. let me know if you need anything else related to that. | 19:21 |
maxb | matsubara: that sounds good, thanks. | 19:21 |
matsubara | np | 19:22 |
maxb | You might want to think about reassigning lp:~matsubara/bzr-pqm/debian too | 19:23 |
maxb | Eventually it'll need an update of some kind, I'm sure | 19:23 |
matsubara | maxb, done. | 19:25 |
dejuren | gents, I'm trying to recover lost PW in launchpad, and confirmation code is not comming.... pse help? | 19:26 |
maxb | Hmm. It's probably time for us to officially call the launchpad PPA deprecated on hardy | 19:26 |
vish | hi, when i create a team with a mailing list, is there a way to add mail filters to the list? | 19:27 |
vish | there seems an option to moderate the list but that looks like a spam filter moderation.. cant seem to find an option to add filters.. | 19:28 |
matsubara | maxb, maverick build failed. do you have an idea why by looking at the log: https://launchpadlibrarian.net/59205977/buildlog.txt.gz? | 19:35 |
maxb | dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found | 19:36 |
maxb | AIUI, recipe builds require that the packaging be munged into 3.0 (native) format | 19:36 |
matsubara | maxb, I mean, do you know how to solve that? | 19:36 |
matsubara | maxb, hmm looks like this one: https://bugs.launchpad.net/launchpad-code/+bug/614768 | 19:38 |
ubot5 | Launchpad bug 614768 in bzr-builder "Unable to build dpkg v3 (quilt) packages (affected: 14, heat: 80)" [High,Triaged] | 19:39 |
maxb | Indeed. Fairly trivial to work around, though | 19:39 |
maxb | I've pushed & re-requested | 19:44 |
matsubara | thanks maco | 19:47 |
matsubara | ops | 19:47 |
matsubara | maxb, ^ | 19:47 |
=== jamalta_ is now known as jamalta | ||
mounir | Question: can we access Launchpad data (read only) to issue sql queries directly from the database? | 20:00 |
=== matsubara is now known as matsubara-afk | ||
thumper | mounir: no | 20:22 |
thumper | mounir: not even launchpad devs can do that | 20:22 |
mounir | is there alternatives? Like having a snapshot database or backup database that we can access so we don't affect the live one? | 20:23 |
mounir | thumper, can the staging stabase be accessed? | 20:25 |
thumper | mounir: due to privacy reasons, straight sql access to the db is likely to never be offered | 20:25 |
mounir | thumper, how do we generate reports, easily? | 20:27 |
thumper | mounir: what type of reports are you thinking of? | 20:27 |
thumper | mounir: although this is one of the reasons we have launchpadlib | 20:27 |
thumper | mounir: have you looked at the API? | 20:27 |
mounir | like whihc blue prints are done, how many still left, etc.... | 20:27 |
mounir | thumper, no I have not looked at the API. | 20:28 |
thumper | mounir: launchpadlib is the way to access Launchpad data from scripts | 20:28 |
mounir | Thumper if we have a read only access we can direct BIRT to access the data and generate report/charts that sort of stuff | 20:28 |
thumper | mounir: you won't get read only access | 20:29 |
thumper | not directly to the db | 20:29 |
mounir | thumper, how given access to project owner for their project data, is that possible? | 20:29 |
thumper | mounir: launchpadlib is the way | 20:29 |
mounir | thumper, do you have a link to launchpadlib? | 20:30 |
mounir | ls | 20:30 |
thumper | https://help.launchpad.net/API | 20:31 |
mounir | thumper, thank you | 20:32 |
thumper | np | 20:33 |
maxb | Hmm, I think something might be broken | 20:45 |
maxb | https://code.launchpad.net/~launchpad-committers/+recipe/bzr-pqm-launchpad-ppa/+build/7797 is in status Uploading, and has been for an hour | 20:45 |
maxb | oh, what? I have a rejected email, but LP still thinks the upload is in progress | 20:53 |
mwhudson | thumper: being able to push to lp:$project and having all the bits get hooked up right is very nice btw | 20:59 |
thumper | mwhudson: cool | 20:59 |
wgrant | lamont: Hi. | 21:52 |
lamont | morning wgrant | 21:53 |
wgrant | lamont: Had ross been aborted, do you know? | 21:54 |
lamont | dunno. | 21:54 |
lamont | I did a killall make expect and a couple more selective kills, launchpad-buildd fired off it's cleanup purge, and went on about its business | 21:55 |
lamont | does this mean that the 'abort this build' actually tries to do something now? | 21:55 |
wgrant | lamont: The UI button? No. | 21:56 |
lamont | the last log entry for it was a Dispatching entry | 21:56 |
wgrant | :( | 21:56 |
lamont | from something like 13 hours earlier | 21:56 |
lamont | which is actually sensible for gcc-snapshot | 21:57 |
=== Ursinha is now known as Ursinha-dinner | ||
lifeless | geser: ping | 22:22 |
geser | lifeless: pong | 22:22 |
lifeless | please try your script accessing private bug attachments now | 22:23 |
geser | lifeless: trying; it's "grab-attachment" from ubuntu-dev-tools | 22:24 |
lifeless | geser: if you get an Unauthorized then its not logged into launchpad properly. | 22:25 |
geser | lifeless: "grab-attachments 676076" crashes with "httplib2.ServerNotFoundError: Unable to find the server at lplibrarian.internal" (can pastebin the whole traceback if needed) | 22:26 |
lifeless | geser: please do | 22:27 |
lifeless | ah, I think I know whats up. | 22:27 |
lifeless | we have a code path that will need to be tweaked to actually enable this. | 22:28 |
geser | lifeless: http://paste.ubuntu.com/533251/ | 22:28 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!