[02:48] <lotuspsychje> good morning to all
[03:37] <guiverc> does anyone know the program whcih expands the ISO on install?  (it'll be same if calamares/lubuntu or ubiquity/rest so I'm betting not the the installer package)
[03:39] <sarnold> "expands"?
[03:40] <guiverc> writes the squashfs to the actual disk... bug 1898302
[03:42] <guiverc> sorry, wasn't well explained; bug complains ubuntu are putting details in wrong locations on disk, non-Linux standards..  https://bugs.launchpad.net/ubuntu/+bug/1898302
[03:44] <sarnold> guiverc: that's called usrmerge, it's all the ragethese days, https://wiki.debian.org/UsrMerge
[03:45] <guiverc> thank you most kindly sarnold :)   I'll read it.. and hopefully get clues !  thanks
[03:46] <guiverc> That's most apt !!  (not the package name, no pun).  thanks!
[03:46] <sarnold> hah, and coming back to re-read what I wrote, 'rage' is quite the perfect choice :)
[03:46] <sarnold> a great many people seem to think usrmerge is the best thing ever
[03:47] <sarnold> and a great many people are driven to apoplexy over something so inane
[03:47] <sarnold> anywaym, have fun :)
[03:47] <guiverc> :)   always try!
[09:29] <tomreyn> guiverc: in #ubuntu , nickanme lapion brought up something which sounded similar:
 Why do the ubuntu install dvd's rely on a symbolic and or a hard-link ?
 has everybody forgotton that the only truly useful file system for smaller usb-sticks is vfat ?
[09:31] <tomreyn> starting at 02:12 am CEST (should be 00:12 UTC), if you ant to look at the logs.
[09:32] <tomreyn> i'm not sure it's the same thing, though.
[09:37] <guiverc> thanks tomreyn
[09:40]  * guiverc was dealing with food so waited till I'd finished & washed hands  .. I expected to find a duplicate of it so I could mark it as such, I gave up looking; but settled with EOL'ing numerous bugs that cluttered my searches...
[09:41] <lotuspsychje> guiverc: if my eyes see correctly, the bugs about ltsupgrade seems like to be 4.15 kernel bionics to 20.04.1
[09:44] <guiverc> I was commenting about the /bin link /usr/bin.. ; but most bugs I've seen on upgrade seemed to be python, qt4/5 but I'm opening less than half of upgrade bugs I see on -announce
[09:45] <lotuspsychje> ah kk
[14:22] <tomreyn> oh i missed that 18.04 -> 20.04 is now supported
[14:25] <tomreyn> since 2020-09-28
[14:56] <daftykins> that was a heck of a delay
[14:59] <tomreyn> longer than usual for sure, but probably not longer than needed.
[17:05] <tomreyn> are zfs services running or even installed on a default 20.04.1 desktop, if anyone knows?
[17:06] <tomreyn> that's if the zfs option hasn't been chosen on the installer
[17:07] <tomreyn> dmesg | grep zfs    on a default install should tell (i don't have one here currently)
[17:08] <lotuspsychje> tomreyn: grep returns nothing here
[17:09] <tomreyn> thanks
[17:09] <lotuspsychje> and i installed 20.04.1 in such early stage, i cant recall i saw the option in ubiquity
[17:10] <tomreyn> so before .1 release?
[17:11] <lotuspsychje> tomreyn: yeah i always help testing lts very early stage
[17:11] <lotuspsychje> so i dont have .1 clean installed systems here
[17:12] <tomreyn> okay, so it could have been added late rone
[17:12] <tomreyn> * later on
[17:12] <tomreyn> thanks
[20:03] <Maik> welcome Squarism & Seven_Six_Two
[20:05] <Maik> my brain isn't 100% awake yet, my apologies for not inviting you earlier
[20:07] <Squarism> thanks
[20:08] <Seven_Six_Two> np. didn't know about this chan. I do sit in -offtopic now and again
[20:10] <Maik> offtopic is just too busy and most of the time only about nonsense imho. In this channel users can chat more relaxed about non support related Ubuntu stuff.
[21:42] <jeremy31> Anyone familiar with dkms?  I am wondering why it seemed to fail on https://github.com/jeremyb31/bluetooth-5.4.git details at https://askubuntu.com/questions/1277459/bluetooth-rtl8723be-does-not-find-devices-on-lenovo-ideapad-100-14iby
[21:46] <TJ-> how is it failing?
[21:47] <TJ-> source install path should match the package name and version, e.g. /usr/src/$PACKAGE-$VERSION
[21:47] <jeremy31> Hi TJ- It seemed to fail for the user on the askubuntu site, but it worked when I tested it,  his modinfo showed intree module loading after a reboot
[21:48] <TJ-> ` I must have missed that part in the ask
[21:51] <jeremy31> TJ-: bottom of the question, might have been some glich where a new kernel was installed before the dkms was added
[21:53] <TJ-> there's a link to "show 14 more comments" but it never does!
[21:54] <TJ-> is it a 'depmod -a' issue? or is the module never built or installed ?
[21:55] <jeremy31> TJ-: worked fine after I told them to go into the directory and do a make clean, make, and had them copy the new module to where the original btusb.ko was and reboot
[21:55] <TJ-> jeremy31: so did they do a "sudo dkms install module/version" ?
[21:56] <TJ-> if it fails, it will/should report why
[21:56] <jeremy31> TJ-: dkms add and dkms install
[21:57] <TJ-> and they've put the source in the correct /usr/src/$MODULE-$VERSION directory?
[21:58] <TJ-> you'd need to capture/grab the dkms log of the build from /var/lib/dkms/
[22:01] <jeremy31> TJ-: I think I will try again on this machine after installing a new kernel but before rebooting to see what I find out
[22:03] <jeremy31> Thanks for your time
[22:41] <Ziopeppus2> Hello
[22:43] <jeremy31> TJ-: It must have been a kernel update before a reboot when the dkms was installed.  Got similar results on this machine
[22:44] <TJ-> jeremy31: that sounds likely, especially if you're not passing the -k option to specify which kernel version to build/install for
[22:46] <jeremy31> TJ-: A rare case from what I see.  Any way to do it automatically in Makefile or dkms.conf?
[22:49] <TJ-> jeremy31: in theory the /etc/kernel/postinst.d/dkms script should ensure a new build / install... but if that fails (silently) then the symptoms would match
[22:52] <jeremy31> TJ-: I think that depends on the newer kernel being installed before the dkms
[22:53] <jeremy31> after not before


[01:57] <chilts> ojwb: I meant for Vic Uni :)
[01:57] <ojwb> ah
[01:57] <ojwb> sounds like the brandname was what made it possible
[01:58] <chilts> true
[01:58] <ojwb> also, it almost seems a shame to actually work for someone in NZ at this point...
[01:58] <chilts> ??
[01:59] <ojwb> i've yet to work for an NZ client
[01:59] <chilts> ah I see
[01:59] <ojwb> after 4 years here
[01:59] <chilts> heh
[01:59] <chilts> I thought you'd been here longer
[01:59] <chilts> oooh, are you in your new house yet?
[01:59] <ojwb> yes, 2 weeks today
[01:59] <chilts> nice ... going well?
[01:59] <ojwb> mostly
[02:00] <chilts> there are always bits and pieces you find once you've moved in, aye
[02:00] <ojwb> the inifinity didn't work - otherwise it's mostly good
[02:51] <snail> ojwb: infinity as in pool? flash!
[02:51] <ojwb> snail: no, on demand gas water heater thing
[02:52] <snail> oh, less flash, but probably more important
[02:54] <ojwb> yeah
[02:54] <ojwb> they've swapped it out for a loan one, and taken it away to poke at


[05:13] <walrider> ping
[05:15] <walrider> Kilos, helo uncl how u doing :)
[05:35] <pavlushka> Morning Kilos :)
[12:53] <pavlushka> Welcome RemonShai :)
[12:53] <RemonShai> ty pavlushka
[15:37] <pavlushka> hey zaki :)
[15:37] <pavlushka> u-la-la: weather in Chittagong
[15:37] <u-la-la> pavlushka: In Chittagong, Bangladesh at 9:00 PM BDT on November 14, 2016: 26°C; Humidity: 65%; Wind: North at 0 km/h; Conditions: Haze; Sunrise/set: 6:04 AM BDT/5:09 PM BDT; Moonrise/set: 5:13 PM BDT/5:25 AM BDT
[15:46] <zaki> hi pavlushka
[15:48] <pavlushka> zaki: winter is setting here :(
[15:48] <pavlushka> on the north most side
[16:06] <zaki> pavlushka: hmm but it's warm here in city
[16:06] <zaki> bbl
[22:17] <pavlushka> Morning Kilos :)
[22:17] <Kilos> hi pavlushka
[22:18] <pavlushka> How are you Kilos ?
[22:18] <Kilos> ok ty and you lad?
[22:19] <pavlushka> I am better :)
[22:19] <Kilos> yay
[22:55] <pavlushka> night Kilos :) see ya


[00:12] <zkriesse> Hallo all
[03:34] <DarthBear> does anyone know of a good tutorial if you new to xchat and irc
[03:34] <DarthBear> including commands and stuff
[03:36] <Unit193> https://toxin.jottit.com/xchat
[03:36] <DarthBear> thnx buddy
[06:28] <jjseeker> Hi I'm back again with another question if that's okay
[06:30] <jjseeker> I would like to know if it's worth the time to learn how to install packages from .tar.gz files vs just getting the .deb package
[06:30] <jjseeker> if that makes any sense
[06:33] <wilee-nilee> jjseeker, Rarely do you need a tar install, you want to see if what your looking for is in the repos first.
[06:34] <geirha> Yes and no. You'll learn abit on how software gets built, but it generally gets messy, and the software will be hard to uninstall.
[06:34] <geirha> Oh, he left
[06:34] <wilee-nilee> tarred and feathered
[09:14] <regor> I'm having multiple issues popping up so, I'm not sure where to start. Now that things have settled down a bit and I can get online, my first issue is with my hp printer! It prints fine but scanning software say's no scanners present?
[09:15] <regor> BTW...this all started when I upgraded to unbuntu 13!
[09:47] <regor> morning pip__
[09:48] <pip__> hello
[09:48] <pip__> quiet in here...
[09:49] <regor> yeah...it is. you come in here a lot?
[09:49] <pip__> only when I need something
[09:49] <regor> :)
[09:49] <regor> is it usually this quiet this time of the day?
[09:49] <pip__> I usually try the forums - a bust t the moment clearly - first
[09:50] <pip__> I'm not on this early mostly, but it's a little busier most times I'd say
[09:50] <regor> yeah, spent a lot of time there myself
[09:51] <regor> is this place for beginners to learn about linux OS or beginners to get help with issues?
[09:52] <pip__> I'd say both, possibly more on the issues side
[09:52] <regor> :) well then I got the tight place!
[09:53] <pip__> the ubuntu channel gets pretty hectic as i recall
[09:53] <pip__> so I try here as it's a bit quieter
[09:53] <pip__> :)
[09:53] <regor> i'm logged in there too!
[09:53] <pip__> :D
[09:53] <regor> they are way over my head!
[09:53] <pip__> me too
[09:54] <regor> last time I played with linux was when mandrake just came out!
[09:54] <regor> am I showing my age? :)
[09:54] <pip__> wow, is that quite a while ago?
[09:54] <regor> several years.
[09:55] <pip__> yeah, I think. It became Mandriva & then something else I think
[09:55] <pip__> from what I hear the whole GNU/Linux thing is more people friendly these days
[09:55] <pip__> most of the time :)
[09:56] <regor> yep...your right...mandriva. When I was looking for a new distro, I found out how long ago mandrake really was!
[09:56] <pip__> lol
[09:56] <regor> linux has come a long way sine those days
[09:56] <regor> since
[09:57] <regor> has gotten more user friendly
[09:57] <regor> more...GUI
[09:57] <pip__> It's improved greatly since I started using it
[09:57] <pip__> exactly
[09:57] <regor> how long you been playing with it?
[09:58] <pip__> how long have you been using again - sounds like the wrong place to ask that actually lol
[09:58] <pip__> using linux
[09:58] <regor> :)
[09:58] <regor> yes
[09:59] <regor> I guess I should have said "using" it!
[09:59] <pip__> it was my bad, I made it sound like a 12 step channel
[09:59] <regor> I just like to play around with linux and see what it can do
[10:00] <regor> it's seems like real "computing" to me!
[10:00] <regor> not just clicking on icons
[10:00] <pip__> can you explain?
[10:00] <regor> i'm an old DOS user....guess I like the command line!
[10:02] <pip__> I'm scared of it, but getting there & I agree, it feels more "hands on"
[10:03] <regor> When I played around with DOS, I used to set up the boot process so it would load one line at a time. I could see how things were loading and I could hit "enter" each time for another command! Maybe I'm just a control freak! :)
[10:04] <pip__> lol, maybe, but it's an excellent way to learn how a computwer system really works
[10:04] <regor> :) exactly!
[10:05] <pip__> :D
[10:05] <pip__> regor; I gotta go - real world stuff
[10:05] <pip__> catch you soon bud, welcome to the community
[10:05] <regor> got ya...take care and stay out of trouble!
[10:05] <pip__> :D
[10:05] <pip__> u know it
[10:05] <pip__> !!!
[10:05] <regor> :) later
[18:20] <[1]tom> hello
[18:22] <[1]tom> an older version of ubuntu (10.04) is advised for my colleges robotics club
[18:22] <[1]tom> but when setting up the dual boot on my laptop i've run into some issues installing the build-essential packages
[18:22] <[1]tom> is there anyone who might be able to help?
[18:24] <Unit193> 10.04 has gone EOL for the desktop, though.
[18:25] <[1]tom> would you recommend trying to use a later version? last year i tried using 12.x with out success
[18:25] <[1]tom> got lost in dependency hell with the packages they wanted us to use
[18:26] <[1]tom> but at least i got the compiler and the internet working.
[18:30] <[1]tom> i think i have decided to go for a more recent version. any reason i shouldnt go with 13? i just might have better luck with back compatibility with a slightly older version, i'm thinking
[18:38] <krytarik> [1]tom: You should go with Ubuntu 12.04 then, as it's also a Long-Term Support version.
[19:14] <jjseeker> What happens to a file if I moved it to a directory that did not exist at the time?
[19:15] <jjseeker> Is it gone forever?
[19:15] <jjseeker> lol
[19:18] <jjseeker> Well I just started searching for it using find /
[19:18] <jjseeker> hopefully I'll find it
[19:39] <jjseeker> Hello
[21:48] <regor> good morning all! I logged in last night with a question about ubuntu 13. I've been getting several error messages popping up. Once things get quieted down, it seems to run fairly well but I am having issues with scanning on my hp printer. Ubuntu seems to print just fine, most of the time, but no scanner is recognized! any suggestions?
[21:59] <wilee-nilee> regor, You might try simple scan
[22:00] <regor> thanks wilee-nilee, but that's what I was trying! Then I tried Xsane, both of which detected no scanner!
[22:02] <wilee-nilee> regor, Is the scanner part of the HP?
[22:02] <regor> Yes, it's an all-in-one!
[22:02] <wilee-nilee> regor, Give ne the model and let me look around.
[22:02] <wilee-nilee> me*
[22:03] <regor> HP Photosmart 3210 All-In-One
[22:05] <wilee-nilee> regor, Here is some info take a look and see if any scanner references are there, it is listed as working in general in ubuntu. https://wiki.ubuntu.com/PhotoSmart3210
[22:06] <regor> OK, thanks...brb
[22:06] <wilee-nilee> Doh I forgot the ubuntu forums are down.
[22:08] <wilee-nilee> regor, Which ubuntu release do you have installed 13.04?
[22:14] <regor> Mmm, I can see the printer setup process is what I did and even had it print a test page. But, when I followed the information about the scanner, I received, "libnetsnmp.so.15: cannot open shared object file: No such file or directory" which is the same error that pops up when I try to scan! Also, after I typed in the command and saw the response, I got a crash report pop up telling me that...
[22:14] <regor> ...the application makeuri.py has stopped!
[22:15] <regor> yes...13.04
[22:21] <regor> after doing a lot of reading on this issue, I've come to the conclusion that 13.04 has many issues and the version I had, 12.04 has long term support, sooooo, maybe I should just start all over and reload 12.04! I mean, I'm not going to loose anything, this system is pretty new!
[22:22] <regor> and...12.04 worked great!


[00:14] <camako> Robru, I added the MP for Saviq to the spread sheet  ---> https://code.launchpad.net/~mir-team/platform-api/rtm-14.09-compat-mir-0.8.1/+merge/246370
[00:14] <camako> robru ^^
[00:15] <Saviq> camako, ah, I see you unconfused this, glad
[00:15] <camako> Saviq, yeah it builds
[00:15] <Saviq> camako, you need to include this diff before your changelog change https://launchpadlibrarian.net/194801806/platform-api_2.5.0%2B14.10.20141015-0ubuntu1_2.5.0%2B14.10.20141015-0ubuntu2.diff.gz
[00:15] <Saviq> camako, the train will complain otherwise
[00:16] <camako> Saviq, you added platform-api to column G, now we are adding papi MP.. I dunno if it makes a difference
[00:16] <camako> Saviq, ok I'll take that in too
[00:16] <Saviq> camako, yeah, remove it from the sources column
[00:17] <camako> Saviq, ok
[00:19] <Saviq> robru, camako, because of the nature of the change I would not "revoke" the QA sign-off, just build it and publish straight away to unblock the migration
[00:20] <robru> Saviq, I think I'm ok with that
[00:20] <robru> one sec
[00:20] <camako> Saviq, changelog updated
[00:21] <Saviq> camako, thanks, ACK
[00:35] <robru> Saviq, camako: sorry guys I gotta run to the doctor's, will be back in about 2 hours. Hopefully rsalveti is around to hit publish on that when it finishes building, otherwise I can do it later.
[00:36] <Saviq> robru, nw, it's almost build, I'll just do a quick validation and set the spreadsheet accordingly
[00:54] <Saviq> ok, robru, rsalveti, if you're around ↑, everything seems finally in order
[00:54] <Saviq> please publish rtm/018 (only papi needs publishing, not sure how the job looks)
[02:10] <imgbot> [02:38] <robru> Saviq: ok, sorry for the delay, republished
[02:40] <kenvandine> ToyKeeper, i saw your comment about the autopilot failures
[02:40] <kenvandine> you need python3-evdev installed
[02:40] <kenvandine> which i can't figure out why it isn't getting installed
[02:40] <kenvandine> python3-autopilot depends on it
[02:40] <kenvandine> for some reason when CI runs the AP tests, that package gets installed
[02:41] <kenvandine> but installing ubuntu-system-settings-autopilot doesn't...
[02:41] <kenvandine> i don't want to add a depends for it myself, since ubuntu-system-settings-autopilot depends on python3-autopilot, which depends on python3-evdev
[02:56] <kenvandine> ToyKeeper, i went ahead and added the depends and kicked off a rebuild
[02:56] <kenvandine> this way i know it doesn't bite us again
[02:57] <kenvandine> but if you like, you can just install that package then start the tests
[02:57] <kenvandine> the rebuild just adds the depends on the package
[03:00] <kenvandine> ToyKeeper, and silo 3 can land separately, just without it any settings test that mocks upower will fail
[03:00] <kenvandine> but they are failing now anyway
[03:11] <imgbot> [03:18] <robru> ಠ_ಠ
[03:21] <robru> Saviq: you still around? some kind of merge conflict cleaning your silo.
[03:21] <robru> just looking into it now...
[03:31] <robru> Saviq: nm, fixed it. all landed and merged now!
[04:15] <imgbot> [04:15] <imgbot> [08:06] <tvoss> sil2100, good morning
[08:07] <tvoss> sil2100, could you take a look at line 52, I adjusted needs qa to no, elaborated in the test plans column
[08:07] <sil2100> Morning!
[08:09] <sil2100> tvoss: I'll check that in a moment, but I might have to consult QA as well
[08:21] <sil2100> pstolowski: hey! I would need you to get https://code.launchpad.net/~unity-team/unity-scope-click/fix-1390191-rtm/+merge/242214 approved by someone
[08:22] <sil2100> tvoss: ok, so I'll have to talk about your silo with QA - normally I would let it in with this rationale, but since it's location-service QA might think there's additional risk assigned etc.
[08:22] <pstolowski> sil2100, hi! uhm, sure
[08:25] <sil2100> dobey: ^
[08:25] <sil2100> (actually I see dobey was the lander)
[08:28] <pstolowski> sil2100, done
[08:28] <pstolowski> sil2100, dobey will be available in a few hours
[08:32] <bzoltan> sil2100:  I am done with the rtm silo10, feel free to empty it and put back to the pool. Also the line 58 can be deleted from the sheet. Thank you a lot for the resources. It was a super valuable exercise. The Vivid edition of the UITK passes all tests on RTM.
[08:34] <sil2100> bzoltan: that's good to know - does it also run without any user-visible problems? You dogfooded it?
[08:34] <sil2100> pstolowski: thanks!
[08:35] <sil2100> ogra_, davmor2, popey: I have a doctor's appointment in 10 minutes so I'll have to jump out, in theory I should make it in time for the meeting but this depends on the waiting queue
[08:38] <tvoss> sil2100, sure, let me know if I can help
[08:47] <Saviq> sil2100, hey, rtm silo 012 passed QA but Omer must've forgot to push the button, what do we do in that case https://trello.com/c/E7oTClp2/571-ubuntu-rtm-landing-012-unity8-saviq ?
[09:00] <Saviq> ah actually no, it's the broken silo
[09:10] <john-mcaleely> sil2100, ogra_ - is now a good time to push a *vivid* device tarball?
[09:10] <ogra_> john-mcaleely, sure, go ahead
[09:10] <sil2100> o/
[09:11] <john-mcaleely> thanks
[09:11] <sil2100> john-mcaleely: yeah, no plans for vivid this week, so +1
[09:11] <sil2100> Saviq: broken silo..?
[09:11] <Saviq> sil2100, yeah, see Timo's comment
[09:11] <john-mcaleely> I hope davmor2 will be along at some point today with news of the rtm device tarball :-)
[09:11] <sil2100> Ah, this one
[09:11] <sil2100> Yeah
[09:12] <sil2100> Saviq: it will land soon then
[09:12] <Saviq> sil2100, well, it's my fault as I accidentally built it and we tried to recover by bincopying to a different silo, but it never go to a coherent state
[09:12] <Saviq> sil2100, thanks
[09:12] <john-mcaleely> ok, so vivid tarball pushed
[09:12] <davmor2> john-mcaleely: no I decided I was bribed enough as a child
[09:13] <john-mcaleely> heh
[09:13] <john-mcaleely> I'm not sure I get that
[09:13] <Saviq> sil2100, it seems like it won't do anything automagically, might even require manual copy to proposed
[09:13] <Saviq> unless you find a way to get it to work...
[09:16] <ogra_> geez .... test results for 192 and 193 look really bad
[09:16] <ogra_> ~20 new crashers
[09:17] <sil2100> Wow, 193 had mir, but this would mean it's unrelated?
[09:17] <ogra_> seems unity-scopes_scoperunner crashes in every test
[09:17] <ogra_> sil2100, yeah, started one image before
[09:18] <sil2100> Looks like a scoperunner issue
[09:18] <davmor2> sil2100: I blame ogra_
[09:19] <sil2100> ogra_: yeah...
[09:19] <ogra_> sil2100, might be an apparmor one though, i cant open any log file so i cant tell
[09:19] <davmor2> john-mcaleely: wasn't even now it might make more sense :)
[09:19]  * sil2100 logs in into the VPN
[09:22] <jibel> ogra_, health-check didn't run on 192 and 5 tests are failing.
[09:24] <ogra_> jibel, yeah, thats not the issue, we have a new constant crasher (unity-scopes_scoperunner)
[09:25] <ogra_> that worries me more than a few new crashes
[09:25] <jibel> right, could be bug 1357143 ?
[09:25] <ogra_> err
[09:25] <ogra_> failures
[09:25] <sil2100> ogra_: looking at the console logs and comparing with earlier images, so far I don't see any additional apparmor denials
[09:26] <ogra_> sil2100, yeah, smells like it could be the bug above
[09:27] <ogra_> funnily on my own device ... while i have a unity-scopes_scoperunner.crash file, it is from the 9th ... so 5 days old
[09:28] <sil2100> Maybe autopilot triggers it in a funny way
[09:28] <ogra_> seems https://code.launchpad.net/~alecu/unity-scope-click/fix-empty-variant/+merge/246365 has the fix
[09:28] <sil2100> alecu: ping
[09:32] <Saviq> trainguards, I can has reconfigure on rtm silo 006 please, added qtmir there
[09:37] <vila> hi there, any pending issues with ci  ?
[09:45] <sil2100> pstolowski: hey!
[09:45] <pstolowski> sil2100, hey
[10:03] <sil2100> tvoss: hey, so we had a talk about your silo, and it will have to wait for next milestone - sadly one of the reasons is also that it's not yet approved by the product team
[10:03] <tvoss> john-mcaleely, ^, could you take care of that issue, please?
[10:16] <davmor2> john-mcaleely: can you throw me the link for the tarball again please
[10:19] <Saviq> sil2100, any word on publishing rtm silo 12?
[10:19] <sil2100> Saviq: trying this now :)
[10:19] <Saviq> sil2100, ah, thanks :)
[10:19] <davmor2> john-mcaleely: nevermind found it
[10:21] <sil2100> Saviq: if you could make sure to document adding dependencies in commit-messages/changelog-entries I would be really happy ;) Anyway, it seems it's publishing!
[10:22] <Saviq> sil2100, I'll try to remember, sorries
[10:22] <Saviq> sil2100, can I have a reconf on silo 6 in the mean time
[10:22] <sil2100> No worries, it's cosmetics really
[10:22] <sil2100> Saviq: sure
[10:23] <Saviq> sil2100, btw, https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-012-2-publish/26/console seems to have a wrong path to the branch it pushed to
[10:23] <Saviq> missing "ci-train-bot"
[10:24] <sil2100> Saviq: this is really strange, actually the ci-train-bot LP account seems to be missing
[10:24] <sil2100> Where did it push it to then..?
[10:25] <Saviq> sil2100, it pushed fine
[10:25] <Saviq> sil2100, just the log is wrong
[10:25] <Saviq> sil2100, well, actually, maybe it pushed to ~/, which is the user's path then
[10:25] <sil2100> Saviq: might be the case here then
[10:26] <sil2100> Since CI Train prints exactly the string it did bzr push to
[10:26] <sil2100> Didn't know you could do ~/something/something
[10:29] <Saviq> sil2100, see the last commit in https://code.launchpad.net/~indicator-applet-developers/qmenumodel/trunk - something's funky there as well
[10:30] <sil2100> Saviq: yeah, noticed that in another trunk as well, the user config is somehow busted
[10:30] <sil2100> The problem is that I don't have much power over the CI Train machine now after it got pushed to IS
[10:30] <sil2100> But I'll re-try today to get someone looking at this
[10:30] <Saviq> sil2100, nw, thanks
[10:39] <Saviq> sil2100, sorries, one last resync of rtm silo 6, added a sync of qtubuntu from vivid :)
[10:40] <sil2100> Saviq: sure ;)
[10:40] <Saviq> s/qtubuntu/qmenumodel/
[10:41] <sil2100> Done!
[10:54] <john-mcaleely> sil2100, how do I get tvoss gps testing silo approved?
[10:54] <john-mcaleely> sil2100, it's an urgent request from a customer
[10:55] <tvoss> john-mcaleely, probably best to check with pmcgowan once he comes up
[10:55] <sil2100> john-mcaleely: is this required for this milestone?
[10:55] <john-mcaleely> sil2100, yes. testing GPS needs to be done well before other dates coming soon :-)
[10:56] <sil2100> It's a little bit latish you know ;)
[10:56] <sil2100> *lateish
[10:56] <sil2100> jibel: ^
[10:57] <john-mcaleely> sil2100, my fault. I forgot to get the bug raised to the product team. Mostly because it was a feature request...
[11:01] <mandel> sil2100, is the silo creation closed? I'd need to create one for rtm quite urgent :-/
[11:02] <mandel> sil2100, I though it could be done yesterday night
[11:02] <sil2100> mandel: for testing you mean?
[11:03] <sil2100> mandel: since for a silo to get it for this week's promotion it's already too late
[11:03] <mandel> sil2100, I guess it was promotion.. but well, if it is too late is too late, nothing we can really do I suppose
[11:03] <mandel> sil2100, I'll add it to the spreadsheet then
[11:08] <jibel> john-mcaleely, it's too late and not reviewed by the product team. You can escalate it to Pat.
[11:20] <john-mcaleely> jibel, do you know when the product team triage canonical-devices-system-image? It seems I filed it there four days ago
[11:20] <john-mcaleely> https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1408984/+activity
[11:20] <john-mcaleely> pmcgowan, when you're online ^ please get this in this milestone
[11:22] <john-mcaleely> (the alternative is for our customer to wait at least a week, possibly two, to start this testing.)
[11:24] <jibel> john-mcaleely, idk when the review is.
[11:29] <dbarth> hi trainguards, i have silo 007 vivid finally tested and good to land on vivid
[11:29] <dbarth> I have also tested backports to 14.04 if I can get a sync to Trusty, to initiate the SRU process
[11:30] <sil2100> dbarth: hey! Ok, let me do that
[11:30] <sil2100> But let's first release to vivid
[11:30] <dbarth> sure, that's the goal
[11:30] <dbarth> upstream, then SRUs
[11:31] <sil2100> dbarth: btw. you know why the build job was waiting for infinity? Do you remove some arches in this silo?
[11:32] <dbarth> sil2100: it was a build wait because the chrome build fails on powerpc, etc.
[11:32] <dbarth> same as oxide
[11:33] <cjwatson> That shouldn't have caused the build job to wait unless the package was previously built on those architectures
[11:33] <cjwatson> Which would then imply that you'll have trouble getting out of -proposed without archive admin intervention, and it would be best to have it analysed up-front
[11:34] <sil2100> Yeah, looking at LP it seems that previously it had powerpc binaries
[11:34] <cjwatson> but:
[11:34] <cjwatson>  unity-chromium-extension | 3.0.0+14.04.20140318-0ubuntu1  | vivid/universe | source, amd64, armhf, i386
[11:34] <dbarth> cjwatson: i think i stopped the job cause it was being stuck on those arches
[11:34] <sil2100> No, wait
[11:34] <cjwatson> so IMO the build job is wrong
[11:34] <dbarth> that one is a new piece of code
[11:34] <cjwatson> dbarth: You did, but it shouldn't have broken this way
[11:34] <dbarth> using the newest chrome API
[11:34] <sil2100> cjwatson: https://launchpad.net/ubuntu/+source/unity-chromium-extension
[11:34] <sil2100> cjwatson: this page confuses me
[11:34] <dbarth> ie, a replacement for the old NPAPI which has been deprecated
[11:35] <sil2100> cjwatson: the version in -proposed seems to have powerpc binaries
[11:35] <sil2100> cjwatson: while the one in the archive, LP says it's build-dep-waiting on something
[11:35] <cjwatson> sil2100: Yeah, clearly managed to build somehow, but that was in a utopic PPA so who knows
[11:35] <sil2100> cjwatson: ah, scratch the last sentence of mine
[11:35] <sil2100> cjwatson: it's actually dep-waiting on the 3 arches
[11:36] <dbarth> do you have links to the individual builds that were on dep waits ?
[11:36] <cjwatson> And it was stuck in -proposed because those three arches had unsatisfiable binaries
[11:36] <cjwatson> dbarth: that's not necessary
[11:36] <dbarth> ah right, so it couldn't have worked anyway
[11:36] <cjwatson> sil2100: so how about I just remove the binaries for those three arches from -proposed
[11:36] <cjwatson> they aren't going to work, and they're evidently now no longer built
[11:36] <dbarth> +1
[11:36] <sil2100> cjwatson: sounds like a plan, thanks :)
[11:37] <cjwatson> it's disappointing that nobody followed this up for the 201 days that unity-chromium-extension has been stuck in -proposed
[11:37] <cjwatson> somebody dropped the ball in epic style there
[11:37] <dbarth> 201 days?
[11:37] <dbarth> oh, that was the initial landing attempts
[11:37] <dbarth> and then we went into fixing the package-kit problem
[11:37] <cjwatson> given how easy this was to address, it should have been addressed ~200 days ago
[11:38] <cjwatson> and not ignored
[11:39] <sil2100> 201 days?! Oh damn
[11:39] <cjwatson> I've removed those binaries now; I strongly suggest letting the 200-day-old upload migrate before dealing with the next one
[11:39] <dbarth> sorry, i was not aware this package was still blocked there
[11:39] <cjwatson> I suspect somebody cleared a silo when they shouldn't have
[11:40] <dbarth> i asked the initial silo to be unloaded, knowing it would take a bit to fix the other bug
[11:40] <cjwatson> yeah, but this is how things get lost
[11:40] <dbarth> and then we went into 'phone focus' mode... ;)
[11:58] <john-mcaleely> davmor2, any news on the device tarball? (I'm on hols today, and will be out this afternoon, if it needs pushing)
[11:59] <davmor2> john-mcaleely: running still should be done in about 25-30 minutes
[12:00] <john-mcaleely> davmor2, cool, no problem
[12:03]  * sil2100 goes off to prepare dinner
[12:03] <sil2100> john-mcaleely: once you get a +1 from davmor2, feel free to push it
[12:04] <john-mcaleely> sil2100, thanks!
[12:05] <ogra_> must be quite some dinner if you start preparing it around noon :)
[12:05] <john-mcaleely> lol
[12:10] <john-mcaleely> jibel, looks like victorp got to it before pmcgowan . I believe #1408984 is now approved for this milestone
[12:10] <john-mcaleely> sil2100, ^
[12:34] <sil2100> ogra_: it has to cook in the oven for over an hour ;)
[12:34] <ogra_> :)
[12:34] <sil2100> ogra_: oh, and I meant the 'dinner' dinner
[12:34] <sil2100> You know, dinner can mean 'supper', but can also mean 'lunch'
[12:34] <sil2100> Confusing
[12:35] <ogra_> heh
[12:52] <davmor2> sil2100, john-mcaleely: tarball complete
[12:53] <john-mcaleely> davmor2, yay. +1 ?
[12:53] <cwayne> pete-woods: did you ever figure out the "(missing upload)" thing for the store?
[12:53] <davmor2> john-mcaleely: yeap
[12:53] <john-mcaleely> davmor2, double yay
[12:55] <john-mcaleely> sil2100, ogra_ pushed, per your comment above. Coming to an rtm build near you soon :-)
[12:55] <john-mcaleely> thank you!
[12:55] <ogra_> john-mcaleely, enjoy your holiday now !
[12:55] <ogra_> :)
[12:55] <sil2100> o/
[12:55] <john-mcaleely> :-)
[12:59] <sil2100> So now we just need to wait for rvr to finish testing telephony-service
[12:59] <rvr> sil2100: I did, but I need boiko to confirm an issue
[12:59] <sil2100> Oh
[12:59] <rvr> Either him or bfiller
[13:00] <davmor2> john-mcaleely: now get outta here ;)
[13:00] <sil2100> jibel, brendand, davmor2, rvr: did you notice any scoperunner crashes during todays usage
[13:00] <sil2100> ?
[13:00] <davmor2> _usr_bin_webapp-container.32011.crash
[13:00] <davmor2> _usr_bin_webapp-container.32011.upload
[13:00] <davmor2> _usr_bin_webapp-container.32011.uploaded
[13:00] <davmor2> sil2100: ^ that's it
[13:02] <rvr> _usr_share_click_preinstalled_com.ubuntu.camera_<IP_ADDRESS>2_camera-app.32011.crash
[13:03] <rvr> No scope crashes, though
[13:08] <sil2100> davmor2, rvr: great news
[13:08] <sil2100> We'll anyway inform cwayne once he's up
[13:08] <cwayne> sil2100: whatsup?
[13:09] <ogra_> you broke it !!
[13:09] <ogra_> :)
[13:09] <sil2100> cwayne: hey! So, after the custom tarball upload yesterday we noticed scoperunner crashes for every autopilot test in the smoketesting suite
[13:09] <sil2100> cwayne: it's always reproducible on the testing environment, but it seems to happen only during running autopilot tests
[13:10] <cwayne> hmm, there were only changes to like 2 scopes.. shouldnt have affected any of the other ones
[13:10] <victorp> sil2100, that is wierd, nothing else landed on the actual scope running?
[13:10] <sil2100> cwayne: it seems some scope is crashing, and since no scope-related thing got updated besides the custom tarball
[13:11] <sil2100> victorp: no... nothing besides that
[13:11] <victorp> do you have some logs?
[13:11] <sil2100> victorp: there were a lot of landings, but nothing to do with scopes
[13:11] <ogra_> as i said before, apparmor changes landed too, but we dont seem to have any apparmor denials in the logs
[13:12] <ogra_> iirc the apparmor changes were custome related
[13:12] <ogra_> -e
[13:12] <cwayne> it's happening for every single autopilot test?
[13:12] <sil2100> victorp: http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/192:20150113:20150107-5ffb790/223/reminders/ <- here's for instance one of the tests that had the crash, you can access the crashfile there
[13:12] <ogra_> cwayne, yup
[13:12] <sil2100> cwayne: almost every, but in overall there's like 20 scoperunner crashes in the smoketesting runs
[13:12] <sil2100> http://rtm-dashboard.ci.ubuntu.com/smokeng/utopic/touch_stable/krillin/192:20150113:20150107-5ffb790/223/
[13:13] <victorp> sil2100, it looks like I cant see that :(
[13:13] <victorp> I guess I dont have vpn setup
[13:20] <jibel> sil2100, not today, but I've a scope runner crash from 2 day sago
[13:30] <sil2100> bzoltan: aargh, unapproved branches! :) Check merges from silo 10
[13:31] <bzoltan> sil2100:  ohh, I am sorry. So amateurish mistake ...fixed
[13:37] <seb128> sil2100, so you know why the status of rtm 004 is "ready to build" on the dashboard when the package is built in the ppa since yesterday?
[13:38] <ogra_> seb128, an MP branch or is it a source package upload ?
[13:38] <seb128> ogra_, copy from a vivid source
[13:38] <ogra_> (the latter need a watch only build)
[13:39] <ogra_> then try a watch only build
[13:39] <seb128> well, it's built
[13:39] <seb128> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-004
[13:39] <ogra_> the train doesnt watch the actual build for source packages
[13:39] <ogra_> you need to tell it to ...
[13:39] <ogra_> it only works fully automatic for MPs
[13:44] <seb128> ogra_, danke, that worked
[13:44] <ogra_> :)
[13:44] <jibel> john-mcaleely, om26er is on silo19
[13:45] <om26er> john-mcaleely, I am actually waiting for tvoss|lunch to give me steps to verify the fix.
[13:45] <pete-woods> cwayne: no. it's still happening today
[13:46] <tvoss> om26er, please see the bug report linked on the spreadsheet. Also: the patch does not alter the service's behavior
[13:46] <om26er> jibel, ^ :)
[13:47] <rsalveti> ogra_: do you know what happened with vivid?
[13:48] <ogra_> rsalveti, was something supposed to happen with it ?
[13:48] <rsalveti> ogra_: well, it failed to build
[13:48] <rsalveti> E: Unable to locate package libmirclient8driver-android
[13:48] <rsalveti> E: Unable to locate package libmirplatform4driver-android
[13:48] <rsalveti> still that hack?
[13:49] <ogra_> sigh
[13:49] <ogra_> yeah, needs build system changes
[13:50] <rsalveti> ogra_: right, let me bump that
[13:52] <rsalveti> actually, there was no mir upload for days, maybe it just got promoted
[13:52] <cjwatson> maybe component-mismatches?
[13:53] <cjwatson> oh, no, those are the old names
[13:53] <ogra_> there was a mir upload to rtm yesterday ... it should have gone into vivid too
[13:53] <cjwatson> yeah, you need to fix livecd-rootfs
[13:53] <cjwatson> <cjwatson@amber ~/src/ubuntu/livecd-rootfs/livecd-rootfs>$ bzr grep libmir live-build
[13:53] <cjwatson> live-build/auto/config:         add_package install ubuntu-minimal libmirclient8driver-android libmirplatform4driver-android ubuntu-touch
[13:53] <cjwatson> live-build/ubuntu-touch/hooks/80-enable-libhybris.chroot:if dpkg -l libmirclient8driver-android 2>/dev/null|grep -q ^ii; then
[13:53] <ogra_> yup
[13:53] <cjwatson> live-build/ubuntu-touch/hooks/80-enable-libhybris.chroot:if dpkg -l libmirplatform4driver-android 2>/dev/null|grep -q ^ii; then
[13:54] <rsalveti> right, but the upload for vivid happend at 8th
[13:54] <cjwatson> is there a mir ABI bump checklist that this could go on?  there are several things that seem to be forgotten nearly every time
[13:54] <ogra_> rsalveti, if you touch it anyway, drop that ugly check in the .chroot script
[13:54] <rsalveti> ogra_: sure
[13:55] <rsalveti> yeah, we need a checklist
[13:55] <rsalveti> camako: ^
[13:55] <cjwatson> rsalveti: I processed NBS binaries yesterday: https://launchpad.net/ubuntu/vivid/armhf/libmirclient8driver-android
[13:55] <cjwatson> the old not-built-from-source binary would have been hanging around in the archive until then
[13:55] <rsalveti> right, that explains then
[13:57] <rsalveti> yeah, package got renamed
[13:57] <rsalveti> that was a big change
[13:57] <rsalveti> -Package: libmirclient8driver-android
[13:57] <rsalveti> +Package: mir-client-platform-android
[13:57] <rsalveti> wonder why nobody from touch was involved in that landing
[13:58] <ogra_> most likely because it was prepared last year ... lying around til after holidays and then picked up again and touch people were forgotten
[14:00] <rsalveti> ogra_: why dropping that from .chroot?
[14:01] <ogra_> only the check
[14:01] <ogra_> not the command it wraps, just that dpkg -l code ... it is pointless
[14:02] <rsalveti> needed for libmirplatform5driver-android at least
[14:02] <rsalveti> right
[14:03] <rsalveti> argh, will need to brb, family around, need to have lunch at the right time
[14:03] <rsalveti> will fix this once back
[14:04] <dobey> pstolowski, sil2100: eh?
[14:06] <pstolowski> dobey, ?
[14:06] <jdstrand_> the apparmor changes were to apparmor-easyprof-ubuntu and were only to allow more access to the sdcard for the camera and gallery in reserved policy groups. there is nothing in there that would've caused scopes to fail
[14:07] <jdstrand> there was a custom tarball landing that incorporated those changes to fast boot. I can't comment on what else was in there
[14:07] <dobey> pstolowski: you and sil2100 mentioned me earlier. about your branch i guess?
[14:07] <jdstrand> s/to fast/for fast/
[14:09] <sil2100> dobey: all is cool
[14:09] <pstolowski> dobey, yes, we needed top-approval
[14:09] <sil2100> seb128: it looks ok to me now
[14:09] <ogra_> jdstrand, right, perhaps a scope falls over *because* it can access the SD card now :)
[14:09] <pstolowski> dobey, the silo was tested alreadt by om26er
[14:10] <jdstrand> well, they had access before, the only change was being able to readdir /media/<user>/
[14:10] <ogra_> sil2100, seems the store scope is broken :/
[14:10] <dobey> yeah. oh. i was pretty sure it was top approved already. anyway, ok. :)
[14:10] <sil2100> ogra_: for users as well?
[14:10]  * sil2100 tries
[14:10] <ogra_> sil2100, try it
[14:10] <jdstrand> but that would only affect scopes that were confined and used these policy groups-- and I know of none
[14:11] <ogra_> i only get a wqallpaper and bouncin bottom bar
[14:12] <sil2100> ogra_: hmm, I'm running 193 here and the store scope works fine
[14:12] <sil2100> Let me experiment a bit
[14:13] <ogra_> sil2100, i think victorp sees it too
[14:15] <ogra_> sil2100, after reboot it works
[14:15] <sil2100> ogra_: really strange, looks fine here
[14:15] <ogra_> i upgraded to 192 this morning and to 193 just now ... so it probably only happens after a while
[14:17] <ogra_> sil2100, or perhaps a server issue ...
[14:17] <rvr> sil2100:  Approved silo 16
[14:18] <sil2100> rvr: \o/
[14:18] <sil2100> ogra_: so, you anyway think it might be the store scope at fault?
[14:19] <ogra_> sil2100, see the other channel ... seems there is a server issue
[14:27] <seb128> sil2100, yeah, I needed to do a watch only rebuild
[14:27] <seb128> thanks
[14:29] <sil2100> ogra_, jibel: so I think we can label the scoperunner crash as low impact for now, right?
[14:29] <ogra_> yeah
[14:46] <sil2100> Ok, I see telephony-service has migrated completely, nothing in the proposed migration is left
[14:46] <sil2100> ogra_, jibel: what do you say for building the candidate image now?
[14:53] <om26er> tvoss, it timedout for me: "Problem executing the CLI: Wait for fix timed out."
[14:53] <tvoss> om26er, sure, that's fine
[14:53] <om26er> FWIW I am sitting near a window
[14:54] <tvoss> om26er, it's gps only, might well happen
[14:54] <tvoss> om26er, could you pastebin the complete output?
[15:01] <camako> rsalveti, something wrong with Mir?
[15:01] <om26er> tvoss, it took a long time to scroll in the terminal to copy that text. ~15000 lines. http://paste.ubuntu.com/9748370/
[15:01] <rsalveti> camako: we need some sort of checklist when landing mir, because we're currently hardcoding the package name at the script that builds the touch image
[15:02] <rsalveti> camako: latest update included a package rename and abi bumpa
[15:02] <rsalveti> *bump
[15:02] <rsalveti> which broke vivid, which I'm currently fixing
[15:02] <tvoss> om26er, thanks
[15:03] <camako> rsalveti, I see.. bummer... who owns the script?
[15:04] <rsalveti> camako: it's part of livecd-rootfs, so any core dev should be able to update that if needed
[15:04] <rsalveti> camako: but just ping either me or ogra_ and should be fine
[15:04] <rsalveti> until we fix this properly
[15:06] <camako> rsalveti, I was under the impression that it was fixed. I'll talk to Chris (RAOF).
[15:06] <rsalveti> the issue is the update alternatives for the android/desktop backend
[15:06] <rsalveti> to fix this properly we basically need to remove mesa from touch
[15:07] <camako> rsalveti, gotcha
[15:07] <sil2100> ogra_: once you're around, maybe let's kick a new image if jibel has nothing against it
[15:07] <rsalveti> because we're installing both mir-client-platform-mesa and mir-client-platform-android
[15:07] <rsalveti> when we should only be installing mir-client-platform-android
[15:07] <rsalveti> but the dep chain ends up bringing both
[15:08] <camako> rsalveti, ok I'll chase it
[15:15] <rsalveti> camako: so, with latest mir we don't need update-alternatives for the client library, right?
[15:16] <rsalveti> just for the server
[15:16] <rsalveti> platform actually
[15:16] <camako> rsalveti yes only platform
[15:16] <rsalveti> camako: great
[15:28] <jibel> sil2100, waiting for silo 19
[15:28] <sil2100> jibel: oh, wait, so this got approved by Pat?
[15:28] <victorp> sil2100, it was a server issue, according to beuno
[15:29] <jibel> sil2100, no by victorp
[15:29] <sil2100> Ah, ok
[15:31] <sil2100> om26er: how's testing going?
[15:33] <om26er> sil2100, so far so good
[15:33] <sil2100> jibel: in this case it seems we'll indeed end up with an image for the evening meeting
[15:33] <om26er> sil2100, a longer test is running which should take ~30 minutes I believe.
[15:34] <jibel> sil2100, yeah, the estimation this morning was without an additional silo to land today
[15:34] <om26er> tvoss, does the logs look good ?
[15:34] <om26er> tvoss, what causes this messsage: http://paste.ubuntu.com/9748909/ ?
[15:35] <tvoss> om26er, it's on purpose, the mode is standalone gps, non assisted
[15:42] <om26er> davmor2, can you try to run one of the tests in bug 1408984 -- see comment#8
[15:42] <om26er> standalone gps just does not get a fix for me (which is not related to this change).
[15:48] <davmor2> om26er: yeap flash has just finished need to get the silo installed
[16:01] <ogra_> sil2100, sorry, only returned now ... do you have an image building already ? else i'll kick one now
[16:01] <sil2100> ogra_: no no, scratch that
[16:02] <sil2100> ogra_: we're still waiting for that location-service silo that product team enforced
[16:02] <sil2100> It's in testing right now :)
[16:02] <ogra_> oh, the one that wasnt approved this morning ?
[16:05] <sil2100> No, we were waiting for Pat, but then victorp approved it :)
[16:06] <ogra_> ah, k
[16:08]  * mterry really wants another image but sees the above
[16:11] <davmor2> tvoss, jibel, om26er: so both the command in the description and the command in comment 8 but exit with a first fix time
[16:11] <davmor2> _status_update(uint16_t, void*): status=4, context=0x1432d8
[16:11] <davmor2> Mean time to first fix in [ms]: 58745
[16:11] <davmor2> Variance in time to first fix in [ms]:<PHONE_NUMBER>7
[16:11] <davmor2> ubuntu-location-service start/running, process 9126
[16:12] <om26er> davmor2, that basically means its doing what its supposed to, I believe.
[16:12] <davmor2> om26er: I'd say it works then :)
[16:12] <om26er> and that.
[16:13] <davmor2> om26er: is that all you need from me?
[16:13] <om26er> davmor2, yep
[16:13] <om26er> davmor2, thanks :)
[16:13] <davmor2> om26er: no worries
[16:14] <om26er> sil2100, ^
[16:14] <sil2100> o/
[16:14] <sil2100> Thanks!
[16:15] <sil2100> Publishing, once this migrates we kick a new image
[16:15] <sil2100> I suppose the US QA team will only be able to start testing
[16:16] <om26er> sil2100, so new image in ~2h ?
[16:22] <alex-abreu> trainguards can you reconfigure silo 21 for ubuntu-rtm ?
[16:22] <alex-abreu> ^^ L55
[16:22] <sil2100> om26er: yeah...
[16:22] <sil2100> alex-abreu: sure
[16:22] <alex-abreu> sil2100, thank you
[16:24] <sil2100> alex-abreu: done, remember that unity-webapps-qml is also in your rtm silo 13
[16:25] <alex-abreu> sil2100, thank you, yes
[16:40] <sil2100> ogra_: ok, rmadison seems happy (britney as well)
[16:40] <sil2100> ogra_: let's kick teh new image!
[16:41] <ogra_> kicking
[16:41] <sil2100> Thanks :)
[16:41]  * ogra_ looks for his shoes
[16:41] <sil2100> Use your best kicking shoes
[16:42] <ogra_> kicked
[16:50] <sil2100> Today's meeting will be real quick
[16:50] <imgbot> [16:52]  * davmor2 passes ogra_ so hob nail boots to give it a proper kick
[16:54] <kgunn> trainguards just need an rtm silo for line 83, so rickspencer can test a potential solution seems he is special and is able to repro
[16:58] <sil2100> kgunn: k
[16:59] <sil2100> kgunn: so it's ready for assignment?
[17:00] <ogra_> sil2100, as usual, snappy meeting running over, i'll be late
[17:00] <kgunn> sil2100: yep
[17:01] <sil2100> ogra_: ok
[17:13]  * ogra_ pokes google with a pointy stick
[17:35] <mterry> What is the usual build time for a new image?
[17:36] <robru> mterry: 1 to 2 hours as far as I know.
[17:38]  * mterry hugs robru
[17:38] <mterry> and goes to the gym while he waits
[17:38] <sil2100> We should have a new image in ~1h
[17:38] <sil2100> ;)
[17:38]  * robru blushes
[17:39] <Saviq> trainguards ↑ please :)
[17:39] <Saviq> robru, thanks for yesterday, and sorry about all the fuss
[17:39] <robru> Saviq: no worries, that's my job ;-)
[17:40] <robru> Saviq: just need you to approve https://code.launchpad.net/~mir-team/qtmir/gles-sync/+merge/246339
[17:40] <Saviq> robru, done
[17:41] <sil2100> robru: btw. since I didn't have time to look into that today - but did you notice that when ci-train-bot commits to branches, the user seems to be b0rken? Consider for instance this branch: https://code.launchpad.net/~indicator-applet-developers/qmenumodel/trunk
[17:41] <sil2100> robru: looks like some variable is not set properly
[17:42] <robru> sil2100: yeah I fixed that a couple times already but somehow my fix doesn't seem to be sticking. not sure what keeps resetting that :-/
[17:42] <robru> sil2100: do you have an example from within the last week?
[17:43] <sil2100> hmmm, I remember seeing that once yesterday as well, but can't remember the project it was in
[17:43] <sil2100> Let me dig a little bit
[17:43] <robru> sil2100: https://ci-train.ubuntu.com/job/cyphermox-test/527/console actually it seems fine currently
[17:43] <sil2100> robru: maybe those are all just leftovers for now
[17:44] <robru> sil2100: one thing about the staging instance is that it comes with a whole new charm, and I'm reasonably confident that the charm sets this correctly, so once we get a new production deployment it should be fixed permanently. just not sure how the existing charm in the existing deployment keeps breaking this.
[18:43] <tvoss> davmor2, so you happy to sign off the silo?
[19:01] <davmor2> tvoss: 19 went ages ago
[19:02] <davmor2> tvoss: was om26er to sign off
[19:02] <tvoss> davmor2, cool,thx :)
[19:03] <davmor2> ogra_: is everything alright with the build I'd of thought it would of appeared by now
[19:10] <ogra_> davmor2, just checking
[19:11] <ogra_> the rootfs seems to have built https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch
[19:12] <davmor2> ogra_: great so just taking its time then right?
[19:12] <ogra_> the importer seems to run  ... hmm
[19:22] <ogra_> davmor2, there were issues with the importer that stephane fixed only 20min ago ... should pop out the image soon
[19:23] <davmor2> ogra_: nice thanks for the update
[19:23]  * ogra_ vanishes again
[19:23] <ogra_> *fnop*
[19:25] <imgbot> [19:25] <imgbot> [19:25] <imgbot> [19:25] <imgbot> [19:26] <davmor2> \o/
[19:32] <alecu> ping cihelp: Hi! I'd like to have lp:pay-ui autopilot tests being run by jenkins, or some other bot
[19:39] <fginther> alecu, let me look into that
[19:40] <alecu> great
[20:27] <davmor2> kenvandine: bit of an issue for me on mako and krillin on the latest update http://paste.ubuntu.com/9751834/  the updates page is blank when I rewind the revision 10
[20:28] <robru> Saviq: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity8 seems to be a problem with your unity8 migration from silo 18.
[20:28] <davmor2> kenvandine: I'll write up a bug ToyKeeper has just confirmed it
[20:32] <om26er> Hi! mardy
[20:33] <kenvandine> davmor2, blank? or just spinning checking?
[20:34] <davmor2> kenvandine: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1410968 see screenshot in bug
[20:35] <davmor2> kenvandine: 3 qa see it on 4 devices
[20:39] <kenvandine> nt.qml:31 module "Ubuntu.Connectivity" is not installed^M
[20:39] <kenvandine> doh!
[20:39] <kenvandine> davmor2, looks like something was removed in that image
[20:39] <kenvandine> yes, it was dropped from the image
[20:39] <kenvandine> i guess settings really needs to depend on it
[20:39] <kenvandine> anyone know why it was dropped?
[20:40] <davmor2> jfunk: ^
[20:41] <davmor2> kenvandine: system settings wasn't imported from vivid was it?  if so it might be version incompatibility maybe?
[20:41] <jfunk> davmor2: ack
[20:41] <kenvandine> davmor2, nope
[20:41] <kenvandine> http://people.canonical.com/~ogra/touch-image-stats/rtm/195.changes
[20:41] <kenvandine> the package was dropped
[20:42] <kenvandine> i'm adding the depends now
[20:48] <davmor2> ogra_, slangasek: image is bad a user will not be able to update from it till kenvandine fix is back into the system is there a way we can knock the ota on the head for this image so users don't get it?
[20:48] <kenvandine> i wonder why it was removed, but we should have had a depends for it anyway
[20:49] <davmor2> kenvandine: it hates you?  Hate it back it works for me ;)
[20:49] <kenvandine> davmor2, oh... it also broke telegram
[20:49] <kenvandine> that package is part of the platform
[20:49] <kenvandine> click apps depend on it existing
[20:50] <kenvandine> click packages can't depend on it
[20:50] <kenvandine> me adding the depends is a good idea, but we have apps using it as well which can't do the same
[20:50] <davmor2> kenvandine: man that sucks I wonder if it was a seed change, I know there was an issue with the build it took longer than normal :(
[20:51] <kenvandine> maybew
[20:52] <kenvandine> i'm not seeing a seed change
[20:52] <kenvandine> ogra_, ^^ thoughts?
[20:56] <om26er> kenvandine, it was removed in unity8 silo
[20:57] <om26er> i.e. the dependency was removed from unity8 which I guess was pulling it into the image.
[20:58] <om26er> Saviq, ^
[20:59] <slangasek> davmor2: I'm not in the loop, what image are you talking about?
[21:01] <kenvandine> image 195 dropped a package that is part of the platform
[21:01] <kenvandine> the connectivity api
[21:01] <davmor2> slangasek: last rtm proposed image krillin 195 mako 163 krillin.es 144 emulator 157 (but I guess that one doesn't matter so much.)
[21:01] <kenvandine> broke settings and telegram
[21:01] <kenvandine> and probably other click apps too
[21:01] <kenvandine> davmor2, i have the dep change building in rtm silo 3
[21:01] <slangasek> davmor2: ok.  So we should roll back to the previous image, for all devices?
[21:02] <davmor2> slangasek: I think there is an ota tag that cna stop people upgrading to it.
[21:02] <slangasek> I don't know anything about that
[21:03] <slangasek> my understanding is that rollbacks on the channel are handled by re-publishing the previous image
[21:03] <davmor2> slangasek: rollbacks work too
[21:03] <davmor2> kenvandine: looks like unity8 is to blame ← Saviq it's your fault :)
[21:04] <kenvandine> i added the dep to settings
[21:04] <kenvandine> but it should probably be seeded as part of the framework
[21:04] <davmor2> kenvandine: indeed
[21:05] <pmcgowan> kenvandine, lets fix the seed
[21:05] <kenvandine> ogra_, can you seed it?
[21:05] <slangasek> davmor2: I don't see an ubuntu-touch/ubuntu-rtm/14.09-proposed/krillin.es channel
[21:05] <kenvandine> i'd like to have the package depends in there too, since settings is a debian package
[21:05] <slangasek> oh, it's 14.09.es-proposed, hum
[21:05] <kenvandine> i'm anal that way :)
[21:06] <davmor2> slangasek: indeed thanks sorry I couldn't think of the exact channel off the top of my head :)
[21:07] <kenvandine> pmcgowan, i added an ubuntu-touch task too
[21:09] <davmor2> kenvandine: only issue then is if there is a newer version and yours is updated and the seed isn't and it all fails because of it ;)
[21:15] <slangasek> davmor2: rolled back to previous versions for all the devices you mentioned; should be publishing shortly
[21:15] <davmor2> slangasek: thanks
[21:15] <davmor2> jfunk: ^
[21:16] <Saviq> oh jeez, everything's my fault again?
[21:17] <Saviq> who forgot to depend on the connectivity module?
[21:17] <kenvandine> Saviq, aren't you used to it? :-D
[21:17] <kenvandine> Saviq, me... and of course some click apps :)
[21:17] <kenvandine> Saviq, it's know to have broken settings and telegram
[21:17] <davmor2> Saviq: not everything only critical breakages of the system that lie squarely at your upload :P
[21:18] <Saviq> kenvandine, sounds like it should be part of the framework then, if apps use it?
[21:18] <kenvandine> Saviq, yeah... it should be seeded
[21:18] <davmor2> Saviq: this is the conversation we were just having :)
[21:18] <kenvandine> Saviq, most importantly it broke updating :)
[21:18] <Saviq> yeah I can see that
[21:19] <kenvandine> so very hard to fet a fix
[21:19] <Saviq> kenvandine, yay :|
[21:19] <kenvandine> s/fet/get
[21:19] <davmor2> Saviq: remind me to buy you a beer at the next sprint ;)
[21:20] <Saviq> davmor2, I'll remember to grep through / whenever I drop a dependency next time :P
[21:20] <Saviq> robru, "unexpected error: test dependencies are unsatisfiable"
[21:21] <davmor2> night all thanks for the quick responses kenvandine and slangasek
[21:22] <robru> Saviq: yeah i dunno, i was hoping you knew ;-)
[21:22] <Saviq> alecu, we got an adt failure on -scope-click after a unity8 upload https://jenkins.qa.ubuntu.com/job/vivid-adt-unity-scope-click/lastBuild/ARCH=amd64,label=adt/
[21:22] <Saviq> alecu, apparently test deps are uninstallable, any idea?
[21:23]  * alecu looks
[21:23] <Saviq> if only it said more
[21:23] <Saviq> I wonder if proposed got broken, /me adds to chroot
[21:24] <alecu> no idea about this...
[21:24] <alecu> dobey: can you take a look at that log too? ^
[21:24] <dobey> sure
[21:25] <Saviq> IIUC this would mean that B-D for unity-scope-click would be uninstallable in proposed
[21:25] <alecu> there are a bunch of broken deps in that log:
[21:26] <alecu> eg: Broken unity-scope-click:amd64 Depends on account-plugin-ubuntuone [ amd64 ] < none -> 14.04+14.10.20140910 > ( universe/libs )
[21:26] <dobey> Saviq: no, it's the binary packagses that aren't installing
[21:26] <dobey> Saviq: build-depends installed as it actually built
[21:26] <Saviq> dobey, right
[21:27] <dobey> so seems like maybe archive is broken?
[21:27] <dobey> ie, bad timing?
[21:27] <brendand> robru, i'm thinking we need to add a line or two of code to citrain to remove dropped dependencies. we keep on missing these things in silo testing because citrain doesn't do that
[21:27] <Saviq> dobey, could be
[21:28] <dobey> Saviq: it looks like ubuntu-system-settings-online-accounts might have borked something
[21:28] <Saviq> it failed twice already https://jenkins.qa.ubuntu.com/job/vivid-adt-unity-scope-click/
[21:28] <kenvandine> can anyone test silo 3 for me when it finishes building?  just verify it pulls in connectivity module back in as a dep?
[21:28] <kenvandine> i'm going to need to leave in 20m or so
[21:28] <kenvandine> and it won't be done building by then
[21:29] <dobey> huh
[21:29] <dobey> Saviq: well, the scope hasn't changed in vivid in a month...
[21:29] <kenvandine> if not i can test it when get back, but didn't want to hold up the fix
[21:31] <Saviq> dobey, yeah, not saying it's the scope's fault, rather that it seems to be an actual issue, not intermittent
[21:31] <dobey> but why does adt-run install all those packages and then give up with "oh btw, that was a huge waste of time because we can't actually resolve deps"
[21:32] <dobey> hmm, i can't really tell what is going on there
[21:32] <Saviq> yeah me neither, really
[21:34] <Saviq> trying to build u-s-click with proposed here, let's see if I find any issues
[21:39] <dobey> well, it builds fine according to the log. the problem is installing the packages (i'm not entirely sure how adt does that exactly)
[21:40] <Saviq> yeah, I want to try and install the built packages
[21:41] <Saviq> but... http://pastebin.ubuntu.com/9752191/ ← dobey
[21:41] <Saviq> no build :/
[21:41] <dobey> huh
[21:41] <dobey> but why did it build in the adt run then?
[21:42] <Saviq> yeah, good question
[21:43] <dobey> [----------] 6 tests from BootstrapTest (19 ms total)
[21:43] <dobey> in the adt log
[21:43] <dobey> so that code built and passed the tests :)
[21:45] <alecu> it's passing here too
[21:45] <alecu> (on my desktop, still utopic)
[21:46] <Saviq> ah, smart, you have a dummy adt test there to just verify the package builds :P
[21:46] <Saviq> alecu, yeah, no question there, really, just it failed to build for me for some reason
[21:46] <dobey> yes
[21:47] <Saviq> interesting, I think DEB_BUILD_OPTIONS="parallel=5" caused this? it seems to be building fine now... ¿?
[21:47] <dobey> hmm
[21:47] <dobey> weird
[21:47] <robru> brendand: sorry i didn't understand. What is the problem? You mean if a package drops a dep for something it still really needs?
[21:49]  * dobey tries adt-run locally on vivid
[21:52] <Saviq> dobey, yeah, looks like unity-scope-click and -autopilot are uninstallable on proposed
[21:52] <Saviq> trying to find out why
[21:55] <Saviq> oh yay, circular dep
[21:56] <dobey> oh because we depend on unity8 and unity8 declares it depends on us?
[21:57] <dobey> i think unity8 depending on specific scopes is wrong
[21:57] <Saviq> dobey, actually no, we only Recommend
[21:57] <dobey> oh
[21:58] <Saviq> dobey, but yeah, can't install unity-scope-click from proposed
[21:58] <dobey> that wasn't added to unity8 today was it?
[21:58] <Saviq> qtdeclarative5-ofono0.2 : Breaks: ubuntu-system-settings (< 0.3+15.04.20150114) but 0.3+15.04.20150112-0ubuntu1 is to be installed
[21:58] <dobey> oh, that's the problem
[21:58] <dobey> lovely
[21:59] <dobey> so the unity8/scope dep isn't the issue
[21:59] <Saviq> no
[21:59] <Saviq> that didn't change
[21:59] <Saviq> oh hmm, but there is a new settings in proposed
[21:59] <Saviq> so it might indeed still be just a timing problem
[22:01] <Saviq> yeah, it just resolved itself
[22:01] <Saviq> dobey, ↑
[22:01] <Saviq> now who can restart adt tests (that's still alive at this hour)
[22:02] <dobey> hmm
[22:02] <dobey> not sure if i can
[22:03] <Saviq> I'm sure I can't
[22:03] <Saviq> jibel, you around by any chance? could you restart http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/AutoPkgTest/job/vivid-adt-unity-scope-click/85/ for us? the issue should be resolved now
[22:04] <dobey> thomi maybe?
[22:04] <dobey> he should be starting his thursday by now i think
[22:04] <Saviq> soon, yeah
[22:05] <dobey> or robru perhaps?
[22:05] <Saviq> robru, I don't think you can deal with adt can you?
[22:06] <dobey> if trainguards can't poke jenkins to re-run adt jobs, i think we should fix that
[22:07] <Saviq> trueth
[22:07] <robru> Saviq: dobey: I can't remember, let me check
[22:07] <Saviq> robru, http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/AutoPkgTest/job/vivid-adt-unity-scope-click/85/
[22:07] <Saviq> if you can (re)build this, then you can :)
[22:07] <robru> Saviq: ah poop, I don't have the right VPN configured, gimme a few minutes to sort that
[22:08] <Saviq> robru, there's only one VPN!
[22:08] <dobey> one vpn to rule them all, i thought
[22:08] <robru> Saviq: yeah I don't have that one set up yet ;-) still hobbling along with the old one
[22:19] <robru> Saviq: bah I'm on the VPN but the DNS isn't working. can you give me the IP for d-jenkins?
[22:19] <Saviq> robru, <IP_ADDRESS>
[22:24] <robru> bah! I can access jenkins by the IP but then SSO redirects to the domain so I can't complete the login without DNS working. I'll poke IS about this
[22:28] <ToyKeeper> Anyone have an idea where we are for the missing dep fix?
[22:28] <cjwatson> Saviq,dobey,robru: retrying now
[22:28] <robru> Saviq: yeah sorry, I can probably normally retry that job for you but right now everything's busted. no #is vanguard, not sure how long it will take to resolve.
[22:28] <robru> cjwatson: thanks
[22:29] <dobey> thanks cjwatson
[22:29] <cjwatson> the new VPN is much better, I suggest configuring it :)
[22:29] <Saviq> ToyKeeper, it's building in silo 3 IIRC
[22:31] <robru> cjwatson: yeah I was putting off because I'm busy. trying it now
[22:31] <ToyKeeper> Looks like 3 is built.
[22:31] <Saviq> ToyKeeper, yeah, that's it, kenvandine had to go
[22:32] <Saviq> ToyKeeper, so it needs someone to jump on it and confirm the fix
[22:33] <ToyKeeper> Saviq: I just installed silo 3 on the same 195 install where I first saw the issue...  and it's not working.
[22:34] <ToyKeeper> I'll try a reflash to be sure, but so far it doesn't look good.
[22:34] <Saviq> ToyKeeper, did it pull in qml-module-...?
[22:36] <ToyKeeper> Saviq: It's hard to tell.  I already started reflashing, and our silo tools aren't verbose enough to show apt's output.  :(
[22:36] <robru> Saviq: I don't suppose you know the IP of the dns server that resolves *.ubuntu-ci do you?
[22:36] <Saviq> robru, it should get in with the vpn config
[22:36] <robru> Saviq: yeah I would've thought, but not working here
[22:37] <Saviq> robru, like I don't have anything special set up, let me dig in syslog
[22:37] <Saviq> robru, <IP_ADDRESS>
[22:37] <robru> Saviq: dunno, this happened to me before, last time I set up the old VPN, had to do something special to make *.ubuntu-ci resolve. can't find the wiki page for that though
[22:38] <Saviq> NetworkManager[1148]: <info>   Internal DNS: <IP_ADDRESS>
[22:38] <Saviq> robru, do you have something similar in your syslog?
[22:38] <Saviq> when connecting to the new VPN
[22:39] <robru> Saviq: yeah I do, now that I configured it by hand ;-)
[22:40] <Saviq> robru, there's a bunch of domains it resolves for, you might be missing stuff if you do by hand, are you using the NM GUI to configure the VPN?
[22:41] <robru> Saviq: yes
[22:44] <Saviq> robru, dunno, WFM :P
[22:45] <ToyKeeper> Saviq: With 197 + silo 3, I see lots of qml-module-* packages...  but the settings/updates page is still completely blank.
[22:46] <ToyKeeper> I also see the welcome wizard checkbox for HERE has returned, so I think things have improved...  but not all the way yet.
[22:49] <ToyKeeper> kenvandine: When you return, it doesn't appear that silo 3 is a complete fix.  :(
[22:50] <Saviq> ToyKeeper, I'm not in on the details
[22:51] <ToyKeeper> Saviq: In 195, the Updates page stopped working in System Settings...  totally blank, and made OTA updates impossible.  The theory is that it was caused by missing deps.
[22:52] <ToyKeeper> I think the deps are pulled in now, but Updates still doesn't work.  I don't know why.
[23:04] <Saviq> ToyKeeper, trying here, got the problem reproduced
[23:04] <Saviq> installing silo
[23:05] <Saviq> ToyKeeper, were you using `citrain` to install the silo?
[23:05] <dobey> ToyKeeper: do you know if mako 161 was broken in that respect too?
[23:05] <Saviq> dobey, 163 was the first according to davmor2's email
[23:06] <dobey> Saviq: i just saw that e-mail, but my phone is also not showing an image update available, though i see 165 in the server tree. :-/
[23:06] <Saviq> dobey, I think that's because it was removed from the index
[23:06] <Saviq> dobey, to not update people to the broken image
[23:07] <dobey> Saviq: right, but i don't want to update to 163. 162 and 165 are both in the archive though (this is actually on a hammerhead, but the image builds for it mirror the mako images)
[23:08] <Saviq> dobey, there's no fixed image yet
[23:08] <Saviq> dobey, so IIUC your only upgrade would be to a broken image
[23:08] <Saviq> dobey, so that's prevented
[23:08] <dobey> oh
[23:09] <Saviq> ToyKeeper, everything's fine, just citrain can't install the packages from silo 3 because they require a package that isn't in the silo, an "apt update" and "apt dist-upgrade" after citrain helps, though
[23:09] <robru> Saviq: ok, I fixed DNS, I can totally rerun that job now ;-)
[23:09] <Saviq> :)
[23:09] <Saviq> robru, do you get the dns from vpn now or manual?
[23:10] <Saviq> yay, it published
[23:10] <dobey> dave's mail said "it can be resolved from a pc to updated" which implied to me that a newer version fixed it, but if you have the broken image, you have to flash over usb to upgrade
[23:10] <robru> Saviq: well I left my manual config in place, I should double-check that it works automaticaly now. the problem was that I had both 'dnsmasq' and 'dnsmasq-base' installed (because I have no idea what I'm doing), uninstalling dnsmasq made everything magicallystart working
[23:10] <Saviq> dobey, yeah, just there's nothing non-broken to flash to, yet
[23:11] <Saviq> :)
[23:12] <robru> Saviq: yep, seems to be working even without manual dns config. great ;-)
[23:22] <dobey> oh well, past time to go anyway
[23:26] <Saviq> ToyKeeper, as far as I can tell, silo 3 is good to go
[23:47] <ToyKeeper> Saviq: Sorry, had to relocate.  Yes, I used citrain.  Looks like you found the answer about mako already.
[23:48] <Saviq> ToyKeeper, so yeah, citrain can't deal with silos like that because installing the silo requires access to the archive, which citrain disables temporarily (blame robru)
[23:48] <ToyKeeper> Saviq: Thanks for the info on out-of-silo packages.
[23:48] <ToyKeeper> Disabling the archive temporarily usually fixes a lot more issues than it causes, but...  it's still error-prone.
[23:49] <robru> Saviq: what? it does that on purpose because the whole point of it is that you're testing the silo, not random updates from distro.
[23:49] <Saviq> robru, I know ;)
[23:49] <robru> Saviq: it sounds like whatever dep you needed should have been in the silo
[23:49] <Saviq> robru, wha? do you mean we should be uploading all deps (even if they're in archive already) to the silos?
[23:50] <ToyKeeper> Not if it didn't need a rebuild...
[23:50] <robru> Saviq: not all deps, just ones where the archive version isn't new enough
[23:50] <ToyKeeper> I think the issue here is more general.  Our whole silo infrastructure is bad at handling dep changes...  and it's a really difficult issue to fix.
[23:50] <robru> Saviq: or rather the image version
[23:51] <Saviq> robru, the archive version *is* new enough, but this is a case of completely new deps
[23:51] <Saviq> robru, that were not in the image before the silo
[23:51] <robru> Saviq: oh, ok. yeah that wouldn't work ;-)
[23:51] <Saviq> robru, no, I totally understand why it does that, we just need to think about improving that case, at the very least fail with a clear error message
[23:52] <robru> Saviq: well in theory one day the ci airline will provide images built for every silo, and then you just install the image. that'd certainly resolve this particular issue, but who knows how far away that is.
[23:52] <Saviq> robru, fginther does!
[23:52]  * Saviq hides
[23:53] <ToyKeeper> Saviq: BTW, which exact package(s) need to be grabbed from the archive?
[23:53] <robru> Saviq: lemme put it this way... spreadsheet replacement just got deprioritized. so now we're waiting even longer just for the spreadsheet to get replaced. who knows how much longer after that to replace the whole train.
[23:54] <Saviq> robru, oh, wasn't it almost ready back in DC?
[23:55] <Saviq> ToyKeeper, libconnectivity-qt1 qml-module-ubuntu-connectivity
[23:55] <robru> Saviq: yeah, the spreadsheet replacement is about 99% ready as far as I can see, but management decided dep8 was more important, so now spreadsheet replacement is on hold
[23:55] <ToyKeeper> Saviq: Hmm, "apt-get update ; apt-get upgrade" didn't mention either of those after installing silo 3.
[23:56] <Saviq> ToyKeeper, `apt-cache policy qml-module-ubuntu-connectivity`?
[23:57] <ToyKeeper> qml-module-ubuntu-connectivity:
[23:57] <ToyKeeper>   Installed: (none)
[23:57] <ToyKeeper>   Candidate: (none)
[23:57] <ToyKeeper>   Version table:
[23:57] <ToyKeeper> So...  maybe citrain left my sources broken.


[03:59] <lszyba1> hello, I did:  bzr tag -r 77 datahub-release-0.7  now how do I push this to launchpad?
[03:59] <lszyba1> Do I have to recommit and push? "No new revisions to push."
[04:02] <spiv> lszyba1: no, the push worked
[04:03] <spiv> lszyba1: the message is confusing (there's a bug open about that), but the tag will have been pushed.
[04:04] <spiv> lszyba1: $ bzr tags -d lp:datahub
[04:04] <spiv> datahub-release-0.7  77
[04:05] <spiv> lszyba1: so you can see the tag is there :)
[04:06] <spiv> (bug 164450 appears the bug number)
[04:16] <lszyba1> thanks, is there a command to list tags  bzr lstags  ??
[04:16] <bob2> just 'bzr tags'
[04:16] <lszyba1> bzr tags ..found it
[04:17] <lszyba1> thanks,,updated my manual..http://lucasmanual.com/mywiki/Bazaar
[04:20] <lszyba1> anybody knows if launchpad shows tags anywhere?
[04:24] <spiv> Not that I know of.
[04:32] <jfroy|work> jelmer: ping
[04:33] <jelmer> jfroy|work, pong
[04:33] <jfroy|work> jelmer: OK, so I thought I understood, but bzr-svn (or me) just did something I'm not sure I understand.
[04:34] <jfroy|work> Basically, what are you supposed to do again when bzr pull from the subversion branch tells you the branches have diverged? I did a merge, commit, push operation.
[04:35] <jfroy|work> And although that mostly worked, bzr-svn committed, as far as I can tell, the same set of changes that someone else had committed via svn (which caused the branches to diverge in the first place).
[04:35] <jfroy|work> Is that expected, or did I do something wrong?
[04:35] <jelmer> jfroy|work, yes - see the bzr-svn FAQ
[04:36] <jelmer> you may want to use bzr rebase rather than merge
[04:36] <jfroy|work> Ah right, I remember that...
[04:37] <jfroy|work> Hum, I see, I forgot I wasn't working with a Subversion checkout, but rather a branch
[04:37] <jfroy|work> (since committing on a checkout is broken in 1.9)
[04:37] <jfroy|work> A checkout would not have normally allowed by commit which caused the branch to diverge.
[04:37]  * jfroy|work is unconfused
[04:37] <jfroy|work> *allowed my
[04:38] <jfroy|work> The amazing thing is, no conflicts were generated.
[04:38] <jfroy|work> It's as if the same set of changes were applied twice without a problem.
[04:39] <jelmer> yes, that's correct - the revision that was moved to the right hand side is no longer on mainline
[04:40] <jfroy|work> indeed, it got moved to the right-side of the merge commit.
[05:47] <tetha> uhoh. "Device not ready" while trying yo read the kernel is no nice greeting in the morning
[06:00] <poolie> spiv, still around?
[06:01] <spiv> poolie: yeah
[06:03] <poolie> i'm going to finish up in a bit, about 5:30 or 6, and go out
[06:03] <spiv> jelmer: if I have the latest stable branch of bzr-svn installed I can't branch from http://bzr.arbash-meinel.com/branches/bzr/1.10-dev/revision_stream
[06:04] <poolie> mwh reported a new bug with those checks i put in for stacked branches
[06:05] <poolie> i'm just thinking about whether to get on to that now or keep going with john's merges
[06:05] <poolie> probably the second is better, as it's already work in progress
[06:06] <poolie> and then i can take an uinterrupted go at 302968
[06:06] <poolie> how did you go?
[06:06] <spiv> 302968?
[06:06] <poolie> correction bug 302698
[06:07] <spiv> I saw mwh's bug, it seems to still be noticing the problem a bit too late.
[06:07] <poolie> yeah
[06:07] <spiv> Sooner than the next push, at least :)
[06:07] <poolie> right
[06:07] <poolie> i'm happy with the check there
[06:07] <poolie> and it should be fairly possible to just work backwards and see what should be done
[06:08] <spiv> It's weird that the autopack's _check_references trips over, but the push itself didn't.
[06:08] <spiv> Oh, unless an earlier pack that's part of the autopack has the dud record(s).
[06:09] <spiv> If that's the case then it might just be a matter of waiting until a report of that error comes in that isn't from an autopack.
[06:10] <spiv> I agree that at the moment doing work that will make the rc1 tomorrow better is probably the best bet.
[06:10] <poolie> indeed, but what would that be? :)
[06:12] <spiv> Heh.
[06:12] <poolie> i'll look at your tweak for 'avoid extracting revision texts' and merge it
[06:12] <spiv> Landing already reviewed/proposed patches.
[06:12] <poolie> the patch makes sense to me
[06:12] <spiv> I'm doing that one atm, actually :)
[06:12] <poolie> oh ok
[06:12] <spiv> Just waiting for my push to finish then I'll hit pqm-submit (so only a few seconds)
[06:13] <poolie> then i'll look at 'retry 2/3', as no one has reviewed that yet
[06:14] <spiv> That'd be good.  I took a glance at it but the diff seemed a bit odd, and merging bzr.dev gave some irritating criss-cross conflicts.
[06:15] <spiv> ("odd" as in "looks like it shows unrelated changes that are already in bzr.dev")
[06:22] <poolie> i might try that merge then
[06:24] <spiv> poolie: oh, and Mary would be happy if http://bundlebuggy.aaronbentley.com/project/bzr/request/%3C418c22640811181423hc9a2628y4b0bae4dd1f6e7fd%40mail.gmail.com%3E makes it into 1.10
[06:26] <spiv> poolie: there's a newer patch that makes _get_nick into a public get_nick as suggested by the review, but that newer patch is stalled while waiting for tests to be written for that new public API.
[06:26] <spiv> poolie: so probably we should just merge the initial patch (with _get_nick) for 1.10
[06:27] <poolie> +1 from me
[06:27] <spiv> poolie: I can do that if that sounds -- great :)
[07:02] <vila> hi all
[07:04] <poolie> hey vila
[07:34] <poolie> ok, i've fixed up jam's retry patch and sent it to pqm, and now i'm signing off
[07:34] <vila> pfeww, finally the fix for bug #277537 is ready to be used or should I run yet another mammoth 34h bzr check ? :-/ :-) :-\
[07:36] <spiv> poolie: cool.  I've got jam's pack re-order patch with PQM too, so I think we've merged all the important stuff he wanted to have merged.
[07:37]  * spiv goes for a swim
[08:44] <loxs> folks, bzr+ssh doesnt work with the setup installer for windows. So I decided to install python and paramiko and then bzr. Paramiko now works on its own. I try to install with the "simple" installer, but now bzr is not in the system path. And I can't find the exe. Where is it installed?
[09:32] <speakman> how is nested trees developing going?
[09:47] <_mathrick> hey
[09:48] <_mathrick> what is the best repo structure to have a dev branch, and another branch which is dev + local conf (DB/host settings in this case)?
[09:49] <_mathrick> ideally, all changes would be pushed into dev unless I specifically say not to
[09:49] <_mathrick> ie. I'd like to avoid manual sync as much as possible
[10:07] <SteveA> poolie, spiv: hi.  do you need any help getting the branches that are still causing a problem for online services?
[10:07] <spiv> SteveA: more details certainly wouldn't hurt
[10:08] <spiv> SteveA: is it easy to make a tarball of the offending branch(es) + plus instructions to reproduce the problem with the tarball?
[10:13] <_mathrick> um, how can I export a shelf?
[10:14] <SteveA> spiv: I think we only see it when talking to Launchpad
[10:14] <SteveA> spiv: best thing is if I give you access to the private branches, I think
[10:16] <SteveA> spiv: I just added you as a member of a team.  You should be able to get the branches now.
[11:05] <james_w> jelmer: hey just discussing how to make --export-upstream work better for someone, and I think we may be able to solve your problem at the same time
[11:29] <Lo-lan-do> Hey there
[11:30] <Lo-lan-do> Can I get bzr branch (or bzr checkout) to not create a working directory but only to fetch the revisions?
[11:31] <Lo-lan-do> I'm trying to setup a "mirror" repository on my laptop with branches bound to those on my server's repository.
[11:31] <james_w> hey Lo-lan-do
[11:31] <james_w> you can do it if you create a --no-trees repository
[11:31] <Lo-lan-do> But even though the local repository is --no-trees, bzr branch creates working copies :-/
[11:32] <james_w> oh
[11:32] <james_w> that's odd
[11:35] <Lo-lan-do> (This is bzr 1.5-1.1 on Debian unstable, by the way)
[11:35] <Lo-lan-do> But anyway, I'll do some shell magic with bzr reconfigure.
[11:36] <james_w> I'm pretty sure --no-trees should work
[11:36] <james_w> you might have found a bug
[11:37] <james_w> Lo-lan-do: thanks for working on loggerhead for alioth
[11:37] <Lo-lan-do> You're welcome.  You'll probably notice it doesn't Just Work quite yet :-)
[11:39] <Lo-lan-do> (I reported the bugs last night)
[11:40] <Lo-lan-do> I'm off to lunch, but I'll be back to discuss them afterwards :-)
[12:12] <jelmer> james_w, ah, cool - how?
[12:12] <james_w> jelmer: do you use export-upstream in merge mode, or not?
[12:13] <jelmer> james_w, no, I don't use merge mode anymore these days
[12:13] <james_w> jelmer: to add a new mode, so one can just re-use the tarball if already present
[12:15] <james_w> we could also make it a but easier as well, as when you are not in merge mode the upstream branch is not necessary to retrieve the revision in question, as you will have merged it
[12:15] <james_w> though noting the upstream branch will still be useful
[12:15] <james_w> I haven't thought it all through yet though
[12:17] <phoenix3051> anyone know why on ubuntu hardy, bzr depends on  python-central (>= 0.6.7) but only 0.6.5ubuntu1 is available
[12:19] <jelmer> james_w, Is there a good use case for "export-upstream" without "export-upstream-revision" ?
[12:20] <james_w> jelmer: it was intended for nightly build
[13:26] <CardinalFang> Three lines:  $ bzr upgrade \nFormat <RepositoryFormatKnit1> for file:///blah/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance \nbzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format.\n
[13:26] <CardinalFang> "please change!  sorry, nothing to do!"  Why?
[13:27] <beuno> CardinalFang, maybe the repo is old format?
[13:27] <beuno> are you using shared repos?
[13:27] <CardinalFang> Yes, I am.
[13:28] <beuno> CardinalFang, then you have to upgrade bith the branch and the repo
[13:28] <CardinalFang> Hrm.  Ugly.  Okay.
[14:32] <goshawk> hi
[14:32] <goshawk> is there a command to remvoe unknow files?
[14:32] <goshawk> from the repo?
[14:32] <goshawk> *remove
[14:33] <Odd_Bloke> goshawk: `bzr clean-tree`, though that may be in bzrtools.
[14:33] <goshawk> tahnks
[14:33] <goshawk> thanks
[14:33] <goshawk> works great!
[14:33] <goshawk> :)
[14:34] <goshawk> wait... it deleted the whole repo...
[14:38] <Odd_Bloke> goshawk: That's surprising.  Are you sure that you had added the files you were expecting to keep?
[14:38] <_mathrick> goshawk: repo or tree?
[14:38] <goshawk> wait
[14:39] <_mathrick> also, bzr serve just tried to murder my RAM, why does it hate my RAM?
[14:40] <_mathrick> it used up above 500M or so, unsure how much exactly, because I was too busy killing it before it took all the mem
[14:41] <_mathrick> the repo has only 2 revisions, although it has quite a few files
[14:41] <_mathrick> 10K files, ~150MB working tree
[14:42] <_mathrick> how do I find out what's up?
[14:51] <goshawk> Odd_Bloke: it was my fault
[14:58] <goshawk> how can i revert before deleting?
[15:00] <goshawk> done :)
[17:08] <CaMason_> hi guys. About to try about bzr for the first time
[17:10] <CaMason_> does bzr support keywords at all? I namely want to use the $id $ feature of svn if possible
[17:13] <james_w> CaMason_: not currently, it is in development though
[17:13] <CaMason_> james_w: ok. It's not that important for me at the moment :)
[17:14] <CaMason_> I love the fact this is portable. I can now continue my dev and commits whilst on the train :D
[17:14] <CaMason_> I did like tortoiseSVN though. I'm on vista x64, so I can't use the gui
[17:14] <CaMason_> although the eclipse plugin seems good
[17:14] <Lo-lan-do> I thought there was a TortoiseBZR too?
[17:15] <CaMason_> yes but it doesn't support x64, I believe
[17:16] <Lo-lan-do> Ah.  Pardon me for being ignorant of these things, I haven't touched Windows for years.
[17:17] <CaMason_> there's only a couple of things holding me back in windows, and thats the Adobe suite, and better multi-monitor support
[17:18] <CaMason_> I need access to the Adobe stuff, and there's no elegant working solutions for the suite. Also, I use 3 or 4 monitors, and the support with distro's like ubuntu isn't as good as the windows implementation, yet
[17:19] <Lo-lan-do> I wasn't tryng to elicit a discussion on that subject, just apologising, really ;-)
[17:19] <CaMason_> Lo-lan-do: I was just voicing my dissapointment with Adobe's lack of linux builds, as usual :)
[17:21] <CaMason_> hrm.. I've got a couple of symbollic links in my project. I just did a bzr add, and commit. Now 'bzr status' shows those 2 links as 'unknown' with @ appended
[17:21] <CaMason_> Any ideas on the best approach now?
[17:26] <james_w> CaMason_: what happens if you "bzr add <symlink>"?
[17:27] <CaMason_> it seems it added the folder, but not contents (desired)
[17:27] <CaMason_> and commit succeeded :)
[17:37] <CaMason_> What's the preferred mechanism for seperating lines/sentences with a commit message?
[17:41] <james_w> CaMason_: I like to do a one line summary, a blank line, then paragraphs explaining it
[17:41] <CaMason_> sorry for my lack of understanding. How would I insert a newline when I'm typing at command line? (linux)
[17:41] <james_w> that works well with things like bzr log --line, loggerhead etc.
[17:42] <james_w> oh
[17:42] <james_w> don't pass -m
[17:42] <james_w> and don't type a message
[17:42] <james_w> it is possible at the command line, but if you do that you will be given an editor in which to type
[17:43] <CaMason_> oh I see! and thanks to uncommit, I can go back and try it on a real commit :D
[17:43] <CaMason_> liking bzr already
[18:20] <LaserJock> james_w: congrats on the Ubuntu package branches
[18:57] <sohail> hi, anyone know the status of bzrp4? Is the bzr -> perforce functionality available to test/hack?
[19:22] <james_w> thanks LaserJock
[19:36] <LaserJock> james_w: I was looking at a failure and see:   UnicodeDecodeError: 'utf8' codec can't decode bytes in position 286-291: unsupported Unicode code range
[19:36] <LaserJock> james_w: isn't that a common problem?
[19:37] <james_w> yeah
[19:37] <james_w> it assumes debian/changelog is valid utf-8
[19:37] <james_w> I'm going to try and remove that assumption or relax it somehow
[19:38] <Dvyjones> Is there anything like SNV's $Id$ (I think that's how it is in SVN at least) in bazaar?
[19:39] <james_w> Dvyjones: not currently, but it's in development
[19:50] <Dvyjones> And there's nothing like CIA(.vc) in Bazaar?
[19:50] <beuno> Dvyjones, sure, check out the CIA plugin: http://bazaar-vcs.org
[19:50] <beuno> er
[19:50] <beuno> http://bazaar-vcs.org/BzrPlugins
[19:59] <LaserJock> james_w: this one seems a bit weird: bzrlib.errors.NoSuchTag: No such tag: upstream-ubuntu-0.12
[20:00] <Dvyjones> Do oyu know any good PHP software management softares / CMSes that support showing last bazaar pushes?
[20:23] <james_w> LaserJock: yeah, that's the most common one, it's a logic error I haven't had chance to look in to yet
[20:24] <LaserJock> james_w: something about the way it figures out what the upstream release is I suppose
[21:46] <poolie> hello
[21:46] <pygi> hello poolie
[21:55] <thumper> poolie: hi
[21:55] <thumper> poolie: I was trying to remind myself of the --fixes syntax, and went `bzr help bugs`
[21:56] <thumper> poolie: I was somewhat surprised not to see a launchpad example in there
[21:56] <thumper> poolie: it had three or four other examples, but no lp :(
[21:56] <poolie> that sounds like a bug
[21:56] <poolie> i wonder why
[21:57] <poolie> ah so it does talk about lp, but doesn't give a good example
[22:15] <grettke> Hi guys. I've got a shared-repo with a project in it that I no don't need. I want to delete it. Should I just rm -rf it, or use bzr commands to do so? It has never been branched, just created is all.
[22:15] <poolie> if it has nothing else in it that you want, you can just rm it
[22:16] <grettke> Ok.
[22:17] <grettke> If I were to delete and recreate that project, as far as the shared repo is concened, it is not the same as the old one?
[22:19] <poolie> right
[22:20] <grettke> thanks poolie. bye.
[22:25] <spiv> poolie: huh!
[22:25] <poolie> mm?
[22:25] <spiv> poolie: that change used to pass tests, but now it trips on your new consistency chekc
[22:26] <poolie> ah
[22:26] <spiv> (the change to remove "len(self.target._fallback_repositories) > 0")
[22:27] <poolie> yes, that's what i understood you to mean
[22:27] <poolie> good thing that check was there i guess
[22:27] <spiv> I guess that makes sense, it can't be a straight pack-to-pack copy, some delta records have to be fulltexts.
[22:40] <poolie> thumper, spiv: just <http://pastebin.ubuntu.com/77542/> or anything more?
[22:40] <thumper> poolie: fixes rather than addresses perhaps?
[22:40] <thumper> but yes, that is all I was looking for
[22:41] <poolie> i'd kind of like to say what effect this will
[22:41] <poolie> have
[22:42] <poolie> but, that's mostly defined server side and may go out of date
[22:43] <poolie> and i'm not sure off hand what will happen
[22:45] <spiv> poolie: that looks reasonable to me
[22:46] <poolie> thumper: i just got subscribed to a very active project using code reviews etc
[22:46] <poolie> so, congratulations on your feature's popularity
[22:46] <spiv> Off hand I believe --fixes lp:NNNN causes that branch to be associated with the bug, and that association's status is set to "Fix Available".  I think "addresses" is an ok way to summarise that ;)
[22:46] <poolie> but it's also an eyewatering amount of email
[22:46] <poolie> and i don't really really care about it
[22:46] <poolie> possibly i should fix this in my mail client
[22:47] <poolie> but i wonder, if i unsubscribed (if i can) whether I'd get a good replacement through the web
[22:47] <poolie> basically a timeline view of all merge proposals, comments, and landings
[22:55] <spiv> poolie: so I've updated my original InterPackRepo.fetch hack for bug 294479 to add a comment and a NEWS entry.
[22:55] <spiv> poolie: I'm just running a full test suite now, in case there's something unexpected, but I don't expect there to be.
[23:03] <poolie> so this is setting it through a callback?
[23:03] <poolie> i think a comment about why we're doing it, and maybe also something on the constructor parameter to say we don't really want it would make sense
[23:03] <poolie> i sent that doc patch to pqm
[23:04] <spiv> poolie: right.
[23:04] <spiv> poolie: I'll add a comment to the constructor too.
[23:29] <jml> you know what would be great?
[23:29] <jml> being able to re-order threads in a loom
[23:30] <jml> (I guess doing it properly depends on proper cherrypicking, but I'd be happy with a half-arsed solution that was a joy to use)
[23:46] <Glenjamin> hey guys, i've just installed bzr1.9 on windows, and i'm getting the error "Unable to load bzr-svn extensions - did you build it?" "cannot import name client"
[23:46] <Glenjamin> anyone know what this actually means?
[23:47] <lifeless> jml: its in todo I think, file a bug, yada yada yada
[23:51] <awilkins> Glenjamin: It's a packaging bug
[23:51] <awilkins> Glenjamin: You installed the python2.5 version?
[23:51] <Glenjamin> yes
[23:51] <awilkins> Glenjamin: Delete c:\python25\lib\site-packages\bzrlib\plugins\svn
[23:51] <awilkins> Unless you actually want to use bzr-svn, of course
[23:52] <Glenjamin> and if i want svn i should just install it?
[23:52] <awilkins> "just install it" is relative on windows
[23:52] <awilkins> It's rather tricky to get it built
[23:52] <Glenjamin> ah
[23:52] <Glenjamin> i probably dont need it for now
[23:52] <awilkins> For windows I think you are going to be looking at prepackaged binaries
[23:52] <Glenjamin> yeah, i'm fine with that
[23:53] <Glenjamin> while i'm here, i dont suppose anyone knows how to get tortoisebzr working on 64bit windows?
[23:58] <spiv> poolie: http://bundlebuggy.aaronbentley.com/project/bzr/request/%3C20081127231800.GH23611%40steerpike.home.puzzling.org%3E is the updated patch, btw


[07:03] <AndyFitz> can kubuntu use the new ok ? :-)
[07:03] <AndyFitz> oops. the new K  ( gaim autoreplaces text for me )
[11:16] <verwilst> Riddell-1wa: you here?
[11:48] <pef> hello
[12:13] <froud> Arrrgh!!! anyone here know how to create the debian/ in a project so that people can do dpkg-buildpackage?


[12:15] <belkinsa>  Okay, my Ubuntu address is working again.  Thank you for the help
[16:08] <ybon> hi :)
[16:09] <ybon> Anyone using dh_virtualenv to build packages on launchpad? I've an error when dh_virtualenv try to fetch the python package, like if there is not Internet connection, so I may be missing a point
[16:09] <ybon> https://launchpadlibrarian.net/203371551/buildlog_ubuntu-trusty-amd64.addok_0.1.0-7_BUILDING.txt.gz for more details
[16:09] <wgrant> ybon: Launchpad builders can't connect to the Internet.
[16:10] <ybon> makes sense
[16:10] <ybon> but then any way to use dh_virtualenv?
[16:10] <ybon> like uploading the python package by hand
[16:10] <wgrant> I don't know what that is, but from the name I would suspect not.
[16:10] <wgrant> You need to either include your dependencies in your package, or specify them as packages in your Build-Depends field.
[16:11] <ybon> (http://dh-virtualenv.readthedocs.org/)
[16:11] <ybon> ok
[16:11] <dobey> you should probably package them properly in your ppa, if they are not already in ubuntu
[16:11] <ybon> I'm totally dumb in packaging, so I may be missing a point, but for what I understand dh_virtualenv try to dl the packages at build time
[16:12] <ybon> dobey: the idea of dh_virtualenv is not to need to repackage python packages :)
[16:12] <dobey> it's not virtualenv, but setuptools will do that as well
[16:12] <dobey> ybon: dh_virtualenv is an oxymoron then :)
[16:12] <ybon> hehe
[16:12] <wgrant> Sensible Debian packages build only using other packages.
[16:13] <dobey> exactly
[16:13] <ybon> yeah, I understand that
[16:13] <ybon> but mine is not sensible ;)
[16:13] <ybon> I just want to make it easier for people on Ubuntu to install the app I'm working on
[16:13] <dobey> having a tool for building python packages that is designed expressly not to use packages, is not sensible
[16:13] <ybon> but I'd prefer not to need to repackages every python dep
[16:14] <ybon> designed to use python packages ;)
[16:14] <dobey> how many python deps do you have which aren't packaged in ubuntu already?
[16:14] <ybon> I mean, building the .deb works perfectly, on local
[16:14] <ybon> good question :)
[16:14] <ybon> Let me check
[16:14] <dobey> "perfectly"
[16:14] <ybon> I confirm :)
[16:14] <ybon> I can build it and install it on my server ;)
[16:17] <dobey> sure, it appears to work for you. i wasn't questioning that. just that "perfectly" is a rather strong statement, particularly when you're doing something completely antithetical to debian packaging :)
[16:17] <ybon> ok, I remove "perfectly" from my statment, you won :)
[16:20] <ybon> so 1 package is missing, 5 are not up to date
[16:20] <dobey> besides, making debian packages of python libraries is generally pretty trivial
[16:21] <ybon> but I may consider using those versions anyway
[16:21] <dobey> on what version of ubuntu? and what packages?
[16:21] <ybon> only targetting LTS, so Precise and Trusty
[16:21] <ybon> the app I'm trying to package is https://github.com/etalab/addok
[16:22] <ybon> again, I'm totally new on Debian/Ubuntu packaging, so making my own pooding at the moment to try to eat something every day ;)
[16:28] <dobey> well, i don't know which one is missing. they all seem to be available
[16:28] <ybon> I don't see ngram
[16:28] <dobey> docopt and werkzeug can be backported easily from a newer release it seems; the others are all still older versions than you list in requirements.txt
[16:29] <dobey> oh right, ngram was missing, indeed
[16:30] <dobey> i think the "==" dependencies you have is a bit odd too
[16:30] <dobey> generally, you'd want >=
[16:32] <ybon> depends on the habit, I prefer to control them and to have requirements to warn me when I need to upgrade
[16:32] <ybon> anyway, seems I need to review my plans ;)
[16:33] <ybon> thanks for the assistance in seeying the reality :)
[16:33] <dobey> if you want to have more control over dependency versions like that and use your app inside virtualenv, then your best option is probably to just ship your tarball on pypi, and tell people to install it with virtualenv that way, rather than using debian packaging
[16:34] <dobey> so that people can set up a virtualenv container specific to your app
[16:35] <ybon> yep
[16:35] <ybon> I loved the idea of a Ubuntu package too, but it's a bit more work than just adding dh_virtualenv and having it automagically
[16:36] <ybon> dealing with virtualenv is still a bit messy for people not used to python ecosystem
[16:37] <ybon> so having an easier Ubuntu LTS copy-paste to deploy is a nice to have :)
[16:40] <dobey> well, if you need specific versions of python packages, it's going to be a problem, because those will change
[16:42] <ybon> well, this one is not really a strong need
[16:43] <dobey> it very rarely is :)
[16:44] <dobey> i can maybe help get some packages updated in a ppa if you need help with that, but i'm generally pretty short on time, and am doing actual work right now :)
[16:45] <ybon> thanks :)
[16:46] <ybon> I'm considering my options right now ;)
[16:46] <ybon> python-ngram
[16:47] <ybon> python-ngram seems not active, so it means that if I make a package, I will need to maintain it
[16:47] <ybon> which step I'm not sure I should do
[16:47] <ybon> being also pretty short in time, like all of us ;)
[16:55] <dobey> if upstream ngram is no longer active, then maybe you shouldn't use it :)
[16:57] <ybon> héhé ;)
[21:11] <KaZeR> hey there. Everytime i upload a .pot file, it ends up in "Need review". When reviewing it, I do not see why it isn't automatically processed. can someone help?
[21:56] <ki7mt> Hello all, I have project that is on SF right now, and want bring most of it over to LP for a new Ubuntu package. Must I create a new LP account and everything that goes with it or can I run it from my personal account on LP?
[21:57] <beuno> ki7mt, hi
[21:57] <beuno> you would create a team
[21:57] <beuno> and own that team yourself
[21:57] <dobey> you can do it personally, via a team, or as a new account
[21:57] <beuno> but that would disconnect it from you personally, and allow others to jump in
[21:57] <dobey> a team is generally the best way to do things
[21:58] <ki7mt> Ok, that sounds good, I'll read up on the team route. Thanks.
[22:01] <wgrant> ki7mt: You'd usually create a team at https://launchpad.net/people/+newteam, then a project owned by that team at https://launchpad.net/projects/+new
[22:04] <ki7mt> wgrant, ok, that seems logical. So then, users added to the team would also be part of the project yes?
[22:05] <beuno> yes
[22:05] <ki7mt> Ok, thanks. will read up a bit more before I dive it :-)
[22:05] <ki7mt> .. dive in ..
[22:12] <cjwatson> And in general it's pretty rare to need a new account.
[22:21] <dobey> yeah, usually the reason to create a new account would be to create a bot, which you add to a team, that uses the API to perform various things (like using tarmac to manage branch landings)
[22:21] <dobey> anyway, i am gone. later :)
[22:26] <mapreri> ki7mt: you might want to experiment thinks in staging.launchpad.net
[22:44] <ki7mt> mapreri, yes, thanks, I was thinking the same thing after reading about both teams and projects.