[05:40] <NCommander> wgrant: ping?
[05:42] <wgrant> NCommander: Hi
[05:42] <NCommander> wgrant: so I was trying to use the raw-installer custom upload to publish squashfs into installer-arch into the dist folder
[05:42] <NCommander> Obviously it didn't work, and since you've noticed it, I suspect I broke something else in LP
[05:43] <wgrant> Yaeh
[05:43] <wgrant> If you're going to commit such evil, perhaps give us a headsup first :)
[05:43] <wgrant> raw-installer is barely tested to work in PPAs at all, let alone at that scale.
[05:44]  * NCommander gulps
[05:44] <NCommander> What did I hose >.>;
[05:45] <NCommander> (raw-installer generally works with d-i, guess I broke the world somewhat more)
[05:47] <wgrant> NCommander: https://oops.canonical.com/oops.py/?oopsid=OOPS-8a6501691b7c6ada250ac4ab32b1ee69
[05:47] <ubot5`> https://lp-oops.canonical.com/oops.py/?oopsid=8a6501691b7c6ada250ac4ab32b1ee69
[05:48] <wgrant> NCommander: I'm not quite sure why it's crashing like that, but it's probably something evil in your tarball
[05:48] <NCommander> wgrant: oh, that was the first one
[05:49] <NCommander> The code is hardcoded to attempt to try and extract installer-$ARCH
[05:49] <NCommander> FIrst attempt had livecd-$ARCH, and I thought it merely published nothing
[05:49] <NCommander> THe second attempt had the folder right, and then nothing showed up so I ran away quickly :-)
[05:51]  * NCommander decides it *might* be easier to setup a local LP instance to test and abuse this less I bring the wrath of the Soyuz devs upon me
[05:51] <StevenK> NCommander: All three Soyuz devs share a timezone now, too ....
[05:51] <NCommander> but fortunately, there an ocean away from me; gives me plenty of time to hide :-)
[05:51] <bigjools>  =:o
[05:51] <NCommander> *their
[05:53] <NCommander> Might be easier to simply implement a new custom upload type but I think it might cause someone to maul me
[05:58] <StevenK> NCommander: Still in AKL?
[05:58] <NCommander> Migrated back to OR after a check engine light and other concerns forced me to call it quits
[05:58]  * NCommander did accomplish everything on the TODO list except the Dempster Highway
[05:59] <NCommander> more annoyingly, the error codes cleared themselves once I was about halfway back to Oregon, but I have that nasty feeling I'm looking at transmission failure sooner rather than later
[06:01]  * StevenK rejects NCommander's uploads with prejudice.
[06:02] <StevenK> NCommander: What do you drive?
[06:02]  * NCommander hasn't uploaded anything to the archive in awhile
[06:02] <NCommander> StevenK: 2007 Hyundai Tucson
[06:02] <NCommander> 2WD, but it gets excellent mileage and is decent on washboard roads (and arctic tundra)
[06:03] <StevenK> NCommander: http://en.wikipedia.org/wiki/Subaru_Legacy_%28fifth_generation%29 is what Sarah and I drive.
[06:03] <NCommander> http://en.wikipedia.org/wiki/Hyundai_Tucson - me
[06:03] <StevenK> Yeah, I found that already
[06:03] <NCommander> Hilariously, in NYC, when I park the damn thing, I get the compact discount, and the SUV surcharge
[06:03] <StevenK> NCommander: Your PPA uploads are what I rejected.
[06:04] <NCommander> Wait, what?
[06:04] <NCommander> What queue did they end up in?
[06:04] <StevenK> ACCEPTED
[06:04] <NCommander> ...
[06:04] <NCommander> I *really* broke LP
[06:04] <StevenK> PPA uploads are automatically accepted
[06:04] <wgrant> And crashing doesn't autoreject
[06:05] <wgrant> Since it usually indicates an LP bug.
[06:05] <StevenK> Right
[06:05] <NCommander> So LP got stuck in an infinite loop?
[06:05] <StevenK> It will try and process the queue, hit your upload, crash and die.
[06:05] <wgrant> It tried to reprocess them a couple of hundred times yesterday
[06:05] <wgrant> Just makes things a bit slower.
[06:06] <StevenK> Oh, that's right, it will just skip your PPA
[06:06] <StevenK> NCommander: Auto or manual?
[06:06] <NCommander> auto unfortunately
[06:06] <StevenK> Hah
[06:06] <NCommander> Parents wouldn't co-sign the loan unless it was something they could drive
[06:06] <StevenK> NCommander: Said Legacy (which is sold in .au as 'Liberty') is 6 speed manual 4WD
[06:07] <NCommander> Bah
[06:07] <NCommander> Damn you and your stickshift
[06:07] <ScottK> Wait.
[06:07] <StevenK> NCommander: If you tried to drive it, you'd end up banging your hand into the door handle from muscle memory
[06:07] <ScottK> You took and automatic to Alaska?
[06:08] <NCommander> ScottK: semi-automatic
[06:08] <StevenK> ScottK: He's brave and/or stupid.
[06:08] <NCommander> P-R-N-D-1-2-3-4
[06:08] <NCommander> (with 1-4 being sequential)
[06:08] <NCommander> so I can gear down/up like a stick but no clutch :-/
[06:08] <ScottK> That's an automatic.
[06:09] <NCommander> http://goo.gl/maps/m2YDl - (route I drove going up)
[06:10] <StevenK> "This route crosses through Canada."
[06:10] <StevenK> Hahaa
[06:10] <StevenK> You pretty much have no choice, though?
[06:10] <ScottK> It's that or a boat.
[06:10] <StevenK> Right
[06:11] <StevenK> No so much fun driving on a boat
[06:11] <bigjools> that's a long way
[06:11] <ScottK> Depends on how big it is and how many people are walking around on the vehicle deck.
[06:12] <NCommander> THere is the Alaska Martime System from Bellingham, WA to southern Alaska
[06:12] <NCommander> But the prices make an international business class fair look cheap
[06:17] <NCommander> wgrant: honest opinion, if I wanted to build livefs's on the buildds would you say the 'raw-installer' custom upload is approiate, or I should create a new one (or some pre-existing one somewhere)? (I think raw-installer does some managing of the "current" directory in installer-*)
[06:18] <wgrant> NCommander: I'd create a new one. Do they even need to be published to the archive?
[06:18] <NCommander> wgrant: I was thinking a PPA would do the trick
[06:19] <wgrant> NCommander: I'd go with something like translations-static, where you pull the files down through the API
[06:20] <NCommander> wgrant: infinity was working on modifying LP that buildd-* could accept a job from ubuntu-cdimage, but my mental thought was it isn't hard to generate it via PPA. I did need a little bit of voodoo though to get livecd.sh to run in a PPA
[06:20]  * NCommander was trying to figure out a proof of concept before I broke the world
[06:21] <ScottK> Interesting concept of time you have.
[06:21] <ScottK> "Before"
[06:21] <NCommander> then when we need to respin a squashfs, nusaken can generate the stub source package, fire it into a PPA, and poke liblaunchpad to see "has it built yet?" then download
[06:21] <StevenK> ScottK: NCommander saying he broke the world was a common occurance on the Ubuntu Mobile weekly calls.
[06:22] <ScottK> You'd think he'd have learned by now.
[06:22]  * NCommander upgraded from breaking the world to merely breaking davidm
[06:22] <StevenK> NCommander: ITYM nusakan
[06:22] <NCommander> but, just for the record, you guys suck :-P
[06:23] <ScottK> NCommander: We aren't the one that drove to Alaska with an automatic transmission.
[06:24] <NCommander> eh, that's not the crazist thing I ever did
[06:24] <ScottK> Color me not surprised.
[06:24]  * NCommander only notes now that he's digging himself deeper
[06:24] <StevenK> NCommander: Dig up, stupid.
[06:24] <ScottK> Or at the very least stop.
[06:27] <NCommander> WIth friends like you, who the heck needs enemies :-P
[06:28]  * ScottK misread that last word at first and thougth things had taken a seriously weird turn.
[06:30]  * NCommander doesn't want to know what ScottK read
[06:30] <ScottK> For once, you're right.
[06:31] <bigjools> haha
[06:31] <StevenK> I can guess, and I don't like it.
[06:33] <bigjools> ok, how do I get vi in busybox
[06:33] <NCommander> bigjools: its a compile time option
[06:33] <bigjools> arse
[06:33] <NCommander> bigjools: its possible its there but no symlink
[06:33] <bigjools> doesn't help with my current busybox shell then!
[06:34] <NCommander> try busybox vi
[06:34] <bigjools> applet not found
[06:34] <NCommander> I believe ed is standard in busybox though
[06:34] <bigjools> not in this one!
[06:34] <NCommander> bigjools: what are you trying to fix?
[06:34]  * NCommander *might* have a statically linked busybox handy
[06:35] <bigjools> I am booting off a usb stick so I can edit the password file a box
[06:35] <bigjools> on a*
[06:35] <NCommander> Oh
[06:35] <NCommander> That's easier
[06:35] <NCommander> chroot *mnt directory* /bin/bash
[06:35] <NCommander> export TERM=vt100
[06:35] <NCommander> nano /etc/passwd
[06:35] <bigjools> I wonder if in-target will work
[06:35] <wgrant> bigjools: Why not just use GRUB to do that?
[06:36] <wgrant> This isn't Windows :)
[06:36]  * NCommander rather do it from an EFI shell :-P
[06:36] <bigjools> that assumes that I can get into grub
[06:36] <bigjools> got away with no editor
[06:37] <NCommander> is the file malformed or just forgotten password?
[06:37] <bigjools> chroot did it, why did I not do that earlier when I thought of it ...
[06:37] <bigjools> it's a maas-installed juju node where something went wrong in cloud-init
[06:38] <bigjools> thx for tip NCommander
[06:39]  * NCommander would hope that a juju wouldn't bring pain and destruction to innocent installation
[06:39] <NCommander> ^s
[06:39] <ScottK> Interesting theory.
[06:39] <bigjools> well it's supposed to add an ssh key... but failed
[06:40] <NCommander> .... How do you go from add an ssh key to OMG BROKEN /etc/passwd O_O;
[06:40] <bigjools> it's not broken
[06:40] <cody-somerville> Why do you want to upload the squashfs to an archive instead of to the librarian?
[06:40] <bigjools> I am addingt a password
[06:40] <bigjools> so I can ssh in
[06:40]  * cody-somerville is still baffled that you guys want to use launchpad buildds instead of using openstack cloud + juju or whatever.
[06:41] <NCommander> cody-somerville: mostly because I didn't consider uploading to librarian.
[06:41] <NCommander> cody-somerville: generally speaking, I rather used tried and tested tools for critical infrastructure until they've had some time to bake :-)
[06:42] <NCommander> Also, openstack is very x86 only ATM
[06:43] <cody-somerville> I'm not sure how the new code you're writing to add support for this in Launchpad is tried and tested vs. OpenStack
[06:44] <cody-somerville> and IIUC, Linaro 'cross-builds' their ARM images on x86 (but I might be mistaken on that)
[06:44] <cody-somerville> Plus, there is also MAAS.
[06:44] <NCommander> cody-somerville: only new code I'm writing is a publishing method into Launchpad. In addition, I don't want to spawn multiple sets of infrastructure we have to maintain
[06:45] <cody-somerville> lol. Tell me about it. If you guys do implement this, I'm going to have to add support to Offspring to be able to use the launchpad buildd farm
[06:45] <cody-somerville> not looking forward to that
[06:45] <NCommander> As it stands we have to maintain a seperate set of buildds for live images, and another (much larger) set for package builds. OpenStack doesn't really solve the problem I want to solve
[06:47] <cody-somerville> That's a fair point.
[06:47] <NCommander> In addition, then the machiens used for liveFS builds can migrate into the builder pool, and add more ARM and PowerPC hardware
[06:49] <bigjools> of course it helps if I didn't try and ssh into the BMC
[06:54] <NCommander> cody-somerville: actually, I don't want to publish to librarian. Being able to simply wget squashfs's makes life easier when I'm tinkering with a local CD image build vs. having to deal with launchpadlib
[06:55] <cody-somerville> Files in the librarian are wgetable
[06:55]  * NCommander has found that while its generally trivial to put something in librarian, it was my experience that getting things out are more difficult
[06:55] <NCommander> cody-somerville: yes, on some impossible-to-remember URL which changes each time a new file is uploaded
[06:56] <cody-somerville> you don't want a unique filename for each squashfs build you do?
[06:56] <NCommander> We don't currently do it. SUppose if I'm already burning the existing livecd code to the ground, might as well implement it in a slightly smarter manner
[06:57] <NCommander> other thing I need to figure out if is there is a saner way to actually get the correct privelleges to call livecd.sh (it doesn't like fakeroot :-))
[06:59] <StevenK> NCommander: If you have the LFA, it's pretty easy. :-)
[07:01] <NCommander> LFA?
[07:01] <StevenK> LibraryFileAlias
[07:01] <NCommander> er
[07:02] <NCommander> I meant on the buildds themselves
[07:02]  * NCommander was not happy with his workaround to make livecd.sh go
[07:02] <NCommander> s/was/is/g
[09:19] <dholbach> hiya
[09:19] <dholbach> I was wondering if anyone was looking into https://bugs.launchpad.net/launchpad/+bug/1031764 right now
[09:19] <ubot5`> Ubuntu bug 1031764 in Launchpad itself "timeout on code.launchpad.net/~ubuntu-branches" [Critical,Triaged]
[09:25] <wgrant> dholbach: Bug #1029642 is probably the one you actually care about
[09:25] <ubot5`> Launchpad bug 1029642 in Launchpad itself "ScopedCollection:CollectionResource:#branch_merge_proposal-page-resource (landing candidates) dying from late evaluation of security rules" [Critical,Triaged] https://launchpad.net/bugs/1029642
[09:25] <dholbach> aha!
[09:26] <dholbach> wgrant, so is this a problem somewhere else as well? or just in the ~ubuntu-branches MP list?
[09:26] <wgrant> dholbach: It's slow globally, but has only significant affected ~ubuntu-branches and a U1 thing, from what I've seen.
[09:27] <dholbach> ok, that's good to know - thanks a bunch
[09:27] <wgrant> It will hopefully be fixed soon.
[09:29] <dholbach> awesome
[09:29] <dholbach> thanks wgrant
[12:49] <vila> weird issue with packages copied from one ppa to another: the target ppa was empty to start with and after the copy there is no Release.gpg in the target ppa
[12:49] <vila> known issue ? Should I file a bug ?
[16:45] <jonrafkind> I am trying to add a .desktop file to an existing package (that I didn't originally make). It uses cdbs in the rules file. I tried just putting blah.desktop in the debian/ directory but that wasn't enough. How can I make sure the .desktop file gets installed with the package?
[17:52] <george_e> I know this is an odd question but... when creating a recipe, can I omit the base branch and _just_ have two nested branches?
[17:52] <george_e> Is that even possible?
[17:52] <dobey> george_e: you can't nest a branch if you don't have something to nest it into
[17:53] <dobey> why would you want to do that anyway?
[17:54] <george_e> Well... I have one nested branch for the Debian packaging.
[17:54] <george_e> ...and I was wondering if the code could be nested in a directory as well.
[17:55] <george_e> So the uploaded .tar.gz would look something like this: ./debian ./the_code
[17:55] <george_e> The Debian packaging would be aware that the code is in a separate directory.
[17:56] <george_e> I guess it does sound a little strange. I'll explain a little further:
[17:56] <george_e> So I've got some Debian packaging that generates two binary packages - and each needs a separate source tree.
[18:03] <dobey> no, that's really not how you should handle the packaging. the debian/ dir should be nested under the top level dir of the source tree
[18:03] <dobey> why are you building two different sources in the same packaging?
[18:27] <haseeb> hi i am getting the following http://pastebin.com/p9AXugEq
[18:28] <haseeb> config file http://pastebin.com/rrsEEmMC
[18:48] <dobey> haseeb: has nothing to do with launchpad or bzr really, but it is a general ssh issue. you need to fix the file permissions on ~/.ssh and ~/.ssh/config
[18:50] <dobey> and your config is wrong; you'd need "Host bazaar.launchpad.net" and you can omit the "HostName" under that. also you don't need configure ssh to configure your lp hostname for bzr; you should do "bzr lp-login" instead
[18:51] <haseeb> ok
[18:55] <haseeb> dobey,  same error
[18:57] <dobey> you still need to fix the file permissions on them then
[18:58] <dobey> or just delete it if that's the only thing in the .ssh/config file
[19:03] <george_e> dobey: Sorry, I was away for a few minutes there. I'm not really building two source packages - since the source tree is identical in both cases (I'm nesting the same branch in two places). The reason I'm doing this is because I'm building the library for two architectures.
[19:04] <george_e> Note that this is NOT the same as specifying Architecture: Any in the debian/control file.
[19:04] <george_e> ...because I am not building Linux / Unix binaries.
[19:04] <dobey> what are you trying to do exactly?
[19:04] <george_e> I am using Mingw-w64 to build Windows binaries.
[19:05] <george_e> (Sorry if this really is confusing.)
[19:05] <dobey> you probably don't want to use launchpad recipes to do that
[19:05] <george_e> So my plan was to have the Debian directory and two identical source trees.
[19:05] <dobey> or debian packaging
[19:05] <george_e> One for 32-bit Windows and one for 64-bit.
[19:05] <george_e> dobey: I do - because the files are used for cross-compiling.
[19:06] <george_e> I'm not building _executables_.
[19:06] <george_e> I'm building the .lib / .a files that the executables use.
[19:06] <dobey> launchpad recipes are for building debian packages for use on Ubuntu via a PPA
[19:06] <george_e> Exactly.
[19:06] <george_e> That's what I'm doing.
[19:06] <dobey> Windows is not Ubuntu and doesn't use PPAs
[19:07] <george_e> The packages contain files that go in /usr/i686... and /usr/x86_64.
[19:07] <george_e> dobey: Other distros do this. Example: http://rpm.pbone.net/index.php3?stat=26&dist=84&size=46569&name=mingw64-zlib-static-1.2.5-10.fc17.noarch.rpm
[19:07] <george_e> Those packages just contain the files that Mingw-w64 produces.
[19:08] <george_e> I'm not trying to stuff Windows applications into a Debian package.
[19:08] <george_e> These packages are just the development files that are used to produce them.
[19:09] <dobey> and mingw-w64 builds win64 binaries on i386 ubuntu?
[19:09] <george_e> Yes.
[19:09] <george_e> That's why the packages produced are architecture-independent.
[19:10] <george_e> The Mingw-w64 compiler can produce 32 and 64-bit Windows executables from both a 32 and 64-bit Ubuntu installation.
[19:10] <dobey> well, you don't need multiple source trees and everything nested separately
[19:11] <dobey> you need a more complex deiban/rules file
[19:11] <george_e> What else can I do?
[19:11] <george_e> dobey: Ah, okay.
[19:11] <george_e> How would that work?
[19:11] <dobey> in much the same way that some C extensions to Python are built for multiple python versions, for example
[19:11] <george_e> Would you like to see what I have so far?
[19:11] <george_e> I have a branch on LP.
[19:12] <dobey> or make your packaging branch the main tree, and nest everything else
[19:12] <dobey> depending on how the thing you're building actually configures/builds itself
[19:12] <george_e> Currently, the debian/rules here only builds for 32-bit Windows - http://bazaar.launchpad.net/~george-edison55/win-cross/zlib-debian/files
[19:13] <george_e> dobey: That was something I had considered (making the Debian branch the main one).
[19:17] <dobey> i'm not sure exactly how to do what you want, but something like http://bazaar.launchpad.net/~ubuntuone-control-tower/dirspec/packaging-dailies/view/head:/rules (how python3 and python2.7 packages are built from same source), might work for you
[19:18] <george_e> dobey: Okay, thanks. I have done some packaging before for Python modules that generate both Py2k and Py3k packages.
[19:18] <george_e> ...so hopefully something like that will work.
[19:19] <george_e> Maybe the Makefile will let me specify a directory for object / binary files.
[19:24] <dobey> george_e: it doesn't matter really, since install for one should get called before building the other anyway
[19:24] <dobey> george_e: unless you want to fix it to allow building both at the same time
[19:24] <george_e> Ah, so then I just need to run 'make clean' between the two then?
[19:25] <george_e> I guess I need to read up more on how dh_build works.
[19:25] <dobey> well, dh_auto_clean should be getting run between each build, yes
[19:25] <dobey> so you can use override_dh_auto_clean to remove any extra files you need to remove, as is done in that py3k example i showed
[19:26] <george_e> Right.
[19:26] <george_e> One last question... I assume override_dh_auto_build will be called once for each package.
[19:26] <george_e> How do I know which one is getting built?
[19:27] <dobey> i'm not sure. i don't think dh provides any magic for it automatically, so you'll probably have to do some extra stuff to tell it which one to build
[19:27] <george_e> Thanks for helping me out.
[20:59] <svuorela> so. I can't create a account (I don't receive any emails, my mailserver isn't contacted), when using the 'forgot password' functionality I end up with a OOPS ID and something wrong. When trying to use the SSO support they are amazingly unhelpful. What does one do?
[21:17] <lifeless> svuorela: SSO support is where you need to go; have you used their email support system or web form or IRC ?
[21:21] <svuorela> lifeless: the web form
[21:23] <lifeless> svuorela: I suggest you try #canonical-isd on this IRC server
[21:23] <lifeless> svuorela: but first
[21:23] <lifeless> what URL are you using that has the 'forgot password' functionality on it.
[21:24] <svuorela> https://login.launchpad.net/+login
[21:27] <svuorela> lifeless: when is a appropriate timezone for heading into #canonical-isd ?
[21:27] <lifeless> now
[21:27] <lifeless> svuorela: thats definitely an ISD managed url, sorry!