[03:10] <Snoovar> http://www.ebay.de/itm/272245749800
[08:12] <OsakaFoo> hey, seems to be stuck on the loading dots on my nexus 4 - I could adb shell in and most things seem to have started okay - ideas?
[08:40] <mcphail> OsakaFoo: what channel are you using?
[08:48] <OsakaFoo> stable, just tried dev now
[08:48] <OsakaFoo> with dev I can't get adb shell :/
[08:50] <mcphail> I think dev is generally "known broken". I was wondering if you were running that in the first place
[08:51] <OsakaFoo> before I flashed it with stable, I got a similar issue booking to android stock - stuck on the orbs
[08:51] <OsakaFoo> But once I was able to boot into stable play around, then I reboted the device andit getss stuck
[08:52] <mcphail> That sounds very odd
[08:53] <OsakaFoo> I also left it overnight on the loading screen hah
[08:54] <OsakaFoo> shall give stable another shot
[09:09] <OsakaFoo> which is the best log file
[09:09] <OsakaFoo> re my isssue :P
[09:11] <OsakaFoo> is it possible to see what it is waiting on?
[09:41] <lesamourai>  buntu sdk and emulator were running in previous ubuntu 15.10(upgraded from 15.04) . Did clean install of 16.04 and touch emulator gets stuck at 'Choose passcode' screen on first time boot.  Next did clean install ubuntu 15.10 , still same issue. anyone has clues on how to get it working?
[10:08] <nganu> hello people
[10:09] <nganu> how is actually QML licensing used by Ubuntu Touch?
[10:09] <nganu> I mean, does Canonical pay for the license to Digia?
[10:33] <OsakaFoo> mcphail: its working now
[10:33] <OsakaFoo> after I tried to install stable twice and it fained
[10:33] <OsakaFoo> failed*
[10:34] <OsakaFoo> I went to give CM a go, installed twm, failed to boot CM, but used twm to clear lots of things - installed stable again woo
[11:04] <brunch875> What's utouch perspective on IM? Are we going to get something running atop telepathy?
[11:04] <lotuspsychje> brunch875: telegram is nice
[11:04] <brunch875> I get the impression messaging protocols are slowly decaying in favor of closed, proprietary stuff such as whatsapp or facebook chat
[11:04] <brunch875> :s
[11:06] <brunch875> Yeah, it's very nice indeed. But I'm curious if we'll have a central hub using the system "accounts"
[11:06] <brunch875> Same program to send SMS, telegrams and gtalks
[11:06] <lotuspsychje> ota 12 will be nice, but not sure of the plans for this
[11:07] <brunch875> yeah... priorities :D
[11:07] <brunch875> what's coming with ota12?
[11:08] <lotuspsychje> brunch875: think there was an article about it on omgubuntu.com
[11:09] <lotuspsychje> oh ota11 sorry
[11:09] <brunch875> I'm only finding up to ota10
[11:11] <brunch875> if I recall correctly it was about snappy things, but my information is very limited
[11:11] <lotuspsychje> brunch875: http://www.omgubuntu.co.uk/2016/05/ubuntu-touch-scopes-even-better-dash-browser
[11:13] <brunch875> aaaah yes I've read this one!
[11:14] <brunch875> Really looking forward to it
[11:15] <lotuspsychje> : )
[11:15] <lotuspsychje> same here
[11:15] <lotuspsychje> i would love ubuntu-touch to be more customizable aswell
[11:15] <lotuspsychje> leave the user the choice more
[11:16] <brunch875> I've never been a big fan of widgets/scopes
[11:17] <lotuspsychje> well some scopes are handy
[11:17] <brunch875> but if the team pulls it out well, we might see the desktop get replaced
[11:17] <brunch875> so instead of the desktop pointing to a folder, you'll have your scopes there
[11:27] <lotuspsychje> brunch875: i hope things get customizable :p
[11:29] <brunch875> Watching the video I've come to realize just how polished utouch is
[11:29] <brunch875> it looks very very good
[11:29] <lotuspsychje> i love my bq 4.5 :p
[11:29] <brunch875> I love mine too!
[11:30] <lotuspsychje> brunch875: what kind of scopes do you use?
[11:31] <brunch875> Mostly the news and nearby ones
[11:31] <lotuspsychje> i got softpedia linux,500p wallpapers,lxer,alternate appstore,weather app
[11:32] <brunch875> For I prefer launching the weather app itself
[11:32] <brunch875> or the music program to listen to music
[11:32] <brunch875> but I've got to admit it's amazing to get results from soundcould
[11:33] <lotuspsychje> nice
[11:33] <brunch875> but to be honest I prefer the unity dash in the desktop
[11:33] <brunch875> hit super+M and it shows music results
[11:34] <brunch875> if soundcloud results showed up, it'd be just perfect
[11:35] <lotuspsychje> :p
[11:45] <brunch875> For me, the ideal behaviour of scopes/unity dash would be to have a very accesible shortcut in which to search for content from different configurable sources (ala small plugins) which then launches the default program on that content
[11:46] <brunch875> Like separating two different layers: "searcher" and "runner"
[11:49] <brunch875> From this perspective, I believe the gallery application should become a scope instead. And on the other hand have a program which limits itself to opening pictures
[11:50] <brunch875> but I guess it's very complicated to draw a line between where one thing begins and the other ends
[11:50] <lotuspsychje> isnt there a photo's scope?
[11:51] <brunch875> yes, but what I mean is the photo scope overlaps a bit with what the app does
[11:51] <lotuspsychje> right
[11:51] <brunch875> it's like some superset (kind of)
[13:05] <Acou_Bass> those new scope designs look great... i really dont like the solid white for desktop thoug, much preferred the transparency of unity 7 dash :P
[13:06] <Acou_Bass> i really cant see how the desktop version of the unity 8 dash will, y'know, make for a good desktop thing so far, im hoping thatll improve
[13:51] <JanC> brunch875: AFAIK they are working on an API for adding IM protocols, but I'm not sure when it will be ready  :)
[13:52] <brunch875> :D
[13:52] <brunch875> is it based on telepathy or something new?
[13:55] <JanC> they said the API would be simpler than telepathy, but it can't be plain telepathy because they need to protect IM protocols from each other IIRC
[13:57] <brunch875> that's fantastic news
[13:57] <brunch875> hopefully it's something somewhat compatible with existing plugins
[13:57] <JanC> I assume that is so that e.g. Skype can't read your Jabber messages, etc.
[14:04] <allizom> I'd like to buy a phone to use with Ubuntu Phone but every model I checked out is currently out of stock. Which ones are currently available?
[14:05] <brunch875> apparently this "outlet" thing has them available
[14:06] <brunch875> but I don't know if it means second-hand or what
[14:07] <JanC> they are very new 2nd hand I guess
[14:07] <allizom> brunch875: link?
[14:08] <brunch875> https://store.bq.com/es/ubuntu-edition-e-4-5-outlet
[14:08] <brunch875> apparently it 'could come' with some minor issues
[14:08] <JanC> e.g. returned by customers because they don't like it or such
[14:09] <brunch875> on the bright side it's much cheaper
[14:09] <allizom> it seems like that's only for the spanish shop... checking out
[14:10] <brunch875> but if it helps you know, I took little care of my device (dropped to ground, put in pocket with coins...) and it is good as new
[14:10] <allizom> as soon as I enter my country it becomes unavailable
[14:10] <brunch875> so I'd say it's very unlikely to receive a scratched one
[14:11] <JanC> allizom: did you try ordering on the outlet store without changing the language?
[14:11] <allizom> JanC: no, because it says about shipping in spain
[14:12] <allizom> I don't know whether they ship outside of it
[14:14] <JanC> ah yes, they now only allow Spain for shipping from the outlet store
[14:14] <JanC> I'm pretty sure they gave other choices in the past
[14:15] <allizom> JanC: is there any other model available?
[14:17] <allizom> or I could buy the android version of, for instance, the meizu pro 5 and flash it with ubuntu phone
[14:17] <brunch875> you can even buy the android version of the aquaris
[14:18] <brunch875> but as I've heard, you have to repartition the device to do that
[14:18] <brunch875> and I haven't seen any guides laying around nor how to get the repartitioning software from bq
[14:19] <allizom> I'm currently reading the guide for flashing ubuntu, I'd like to make sure I can follow it before committing to the purchase
[14:20] <JanC> allizom: the bq Ubuntu phones will probably be back in stock at some time
[14:21] <JanC> you could try to contact bq and/or subscribe for notification in the store
[14:22] <allizom> JanC: I'd rather not wait for an indefinite time as this would be a gift
[14:22] <JanC> right, so then maybe try to contact them
[14:23] <allizom> are there differences between the android and ubuntu editions of the meizu pro 5? such as locked bootloader or else?
[14:23] <brunch875> the meizu has more locks, doesn't it?
[14:23] <brunch875> the bq phone is pretty open
[14:23] <brunch875> hasn't given me any trouble
[14:24] <allizom> brunch875: which kind of locks?
[14:24] <brunch875> the bootloader, I think
[14:24] <brunch875> but don't trust my word fully
[14:24] <allizom> hm
[14:24] <brunch875> I'm only repeating rumours :P
[14:26] <JanC> allizom: if this is a present, you are aware that Ubuntu Touch is still in development, right?  :)
[14:26] <allizom> JanC: of course, thanks for the reminder :)
[14:26] <brunch875> as in: no whatsapp :D
[14:27] <allizom> But I think I'm going to tinker more with it than the giftee
[14:27] <JanC> and a lot of other stuff missing or a bit rough on the edges really
[14:27] <allizom> yes I know
[14:30] <allizom> so I could 1) contact bq for informations about restocking and/or buy an android edition device and flash it. Is 2) feasible? Have any of you tried it?
[14:30] <allizom> I mean with a device with a corresponding ubuntu edition
[14:31] <allizom> which is as of now unavailable
[14:31] <hasan> hi
[14:31] <mcphail> allizom: I know some people flashed the bq 4.5 from stock android to Ubuntu. Don't know if the device is still on sale
[14:32] <hasan> I reset my phone, in the new set up wizard, what is preferred name!?
[14:35] <hasan> I reset my phone, in the new set up wizard, what is preferred name!?
[14:36] <brunch875> hasan: I don't understand the question
[14:39] <hasan> Sorry, in the new set up wizard on my Aquaris E4.5, I see new field, Preferred Name for personalized device
[14:39] <hasan> it is host-name!?
[14:39] <brunch875> I think so
[14:43] <Gprince> Help
[14:43] <Gprince> Sup peps....anyone here?
[14:44] <brunch875> !ask | Gprince
[14:44] <brunch875> Hello!
[14:45] <Gprince> I want to install ubuntu on my samsumg tablet, how can i do that.
[14:45] <Gprince> It currently runs andriod 5.1.1
[14:46] <brunch875> That's going to be a bit complicated, since ubuntu isn't ready for all devices out of the box
[14:47] <Gprince> Complicated but not impossible right.?
[14:47] <brunch875> !devices | Gprince
[14:48] <Gprince> Am all about complications....an will to give it a try, i just need the right steps to follow.
[14:48] <brunch875> You'll have more info over there; I'm not really experienced in that
[14:48] <Gprince> Ok...thanks.
[14:49] <Gprince> But actually..thats where i was before i got here.
[14:49] <Gprince> And the steps there didnt work out for me.
[14:49] <Gprince> But thanks for your help.
[14:50] <brunch875> Which device is your tablet?
[14:50] <Gprince> Its samsung galaxy note 10.1 exynos 3g 2014
[14:51] <Gprince> Lattest flagship.😄
[14:51] <brunch875> oh! It seems that there's a working port for that
[14:51] <brunch875> lucky!
[14:52] <Gprince> Ohh....really...
[14:52] <Gprince> Please how?
[14:54] <brunch875> well, apparently you have to use the command phablet-flash community --device <vendor>
[14:55] <Gprince> Ok <brunch>. So how do i do that.
[14:56] <Gprince> You have and guide or steps?
[14:56] <brunch875> do you have ubuntu on your desktop/laptop?
[14:56] <brunch875> sounds like it's going to be easier if you do that
[14:57] <brunch875> link after link I found this video
[14:57] <brunch875> https://www.youtube.com/watch?v=Riw3ybLYKSs
[14:57] <brunch875> But it's as old as 2013...
[14:57] <Gprince> Yes i do on my laptop, but its on a virtual box.
[14:58] <brunch875> three years have passed... I'm not sure I'd recommend it
[14:58] <Gprince> You think it will work.?
[14:59] <brunch875> it probably will... but it's very old and there's probably broken stuff
[14:59] <brunch875> it's a bit of a gamble
[15:01] <brunch875> And from what I've heard, ubuntu touch uses android 4 drivers so I'm not really sure how good it'll get along with android 5+
[15:02] <Gprince> Yhh...i read that also, but since its been updated, so i thought the drivers too must have been also updated.
[15:03] <brunch875> it's not really supported by ubuntu
[15:03] <brunch875> some random guy spent his free time to make it work, but it isn't something official
[15:04] <Gprince> Ohh great.
[15:04] <Gprince> And this random guy did he share his ideas on how he did it.
[15:05] <brunch875> well, it's like making cyanogenmod work on devices
[15:05] <brunch875> you ever been around xda-developers?
[15:06] <Gprince> And hope installing it wont alter my bootloader, so incase things to south i can easily restore my previous backup.
[15:06] <Gprince> Yhh...am a senior member on xda.
[15:06] <brunch875> Probably, but here are no warranties!
[15:06] <brunch875> the thread for this device is here
[15:07] <brunch875> http://forum.xda-developers.com/showthread.php?t=2168999
[15:08] <brunch875> of course you can always start porting yourself :D
[15:08] <brunch875> https://developer.ubuntu.com/en/phone/devices/porting-new-device/
[15:09] <Gprince> Hmmm...here comes my homework.
[15:09] <Gprince> This will definately delay the release of my new rom port...😅
[15:10] <brunch875> :D
[15:12] <Gprince> Lol....
[15:13] <Gprince> Thanks brunch...
[15:14] <brunch875> heh, I wish I knew more to be more helpful :P
[15:14] <Gprince> BRUNCH.......sounds like u love pizza.😜
[15:14] <brunch875> My real name is Bruno!
[15:14] <brunch875> It is saturday so the ubuntu crew is hibernating
[15:14] <Gprince> Nice name.
[15:15] <Gprince> Bruno am Gabriel....nice to meet you.
[15:15] <brunch875> Likewise!
[15:16] <Gprince> Are u on xda.?
[15:16] <brunch875> No, I'm not really a dev...
[15:16] <brunch875> the hardest I ever did was change bootloader and flash cyanogen on my old galaxy S
[15:16] <brunch875> (and I soft bricked it on the process)
[15:17] <Gprince> Lol....that was cool.
[15:18] <Gprince> But u should try it sometime...its fun though a bit frustrating.
[15:18] <brunch875> I wish I had more time
[15:19] <brunch875> I'd create a decent game for utouch
[15:19] <Gprince> Ohh....
[15:19] <Gprince> What about programming languages?
[15:19] <Gprince> U know any?
[15:19] <Gprince> Seems u are also a lover a linux also.
[15:20] <brunch875> born in C and grown in java
[15:20] <brunch875> but only recently finished my studies
[15:20] <brunch875> once you know these, higher level languages like python are easy
[15:20] <Gprince> Ohh....i think today is my day.
[15:23] <Gprince> Are u on telegram or whats app. I can learn more from u..am actuall a java playboy but c...am just new in that.
[15:25] <brunch875> I'd rather talk on irc. Feel free to message me around here and I'll lend you a hand if I'm available!
[15:26] <Gprince> Ohh....no p.
[15:27] <Gprince> Do u have a device currently running U.T
[15:27] <brunch875> Yeah, I bought the utouch aquaris e4.5
[15:29] <Gprince> Ok...
[15:29] <Gprince> Once again thanks...hope to meet u again.
[15:29] <brunch875> See you around! I always use this nick :Þ
[15:30] <Gprince> Ok. As i too.
[15:50] <Gprince> Brunch
[15:53] <Gprince> Brunch...u there?
[16:49] <kristofer> hello!
[16:49] <kristofer> I've gone through the installation process for the nexus 7, now I'm at a screen that says "this phone needs restoring from a pc or service center"
[16:50] <kristofer> should I just wait?
[18:11] <s`> how do you save file in nano using terminal app? i mean, how do you trigger ^X
[18:14] <Acou_Bass> if you click the thing on the far left on the options button in the termnal app above your keyboard
[18:14] <Acou_Bass> hold your thumb on it
[18:14] <Acou_Bass> a popup should come up - move thumb to 'nano'
[18:14] <Acou_Bass> then nano keybindings come up
[18:14] <Acou_Bass> one of them is ctrl-x
[18:14] <Acou_Bass> i think theres also a ctrl-x on the default one though i could be wrong
[18:16] <s`> sorry i can't find this "thing" lol
[18:16] <s`> there is ctrl-x in the default
[18:16] <s`> i mean, there isnt*
[18:17] <s`> far left on the options button above ur keyboard....
[18:18] <Acou_Bass> yeah, its like an orange square with a black numpad logo in it
[18:18] <Acou_Bass> press and hold it, a little popup comes up
[18:18] <s`> oh ok i have SCR, FNS, CTRL and CMD
[18:19] <s`> no nano options
[18:19] <Acou_Bass> the very top theres no nano? :(
[18:19] <s`> no
[18:19] <s`> lol
[18:19] <Acou_Bass> weird... what OTA you on?
[18:19] <s`> how can i see that? sorry i just got my phone
[18:19] <s`> meizu pro5
[18:19] <Acou_Bass> hmm i dunno about neizu
[18:19] <Acou_Bass> meizu even
[18:19] <s`> lemme google
[18:20] <Acou_Bass> in those SCR, FNS, CTRL, CMD options, mine also has 'nano'
[18:21] <s`> Acou_Bass: OTA 10-2
[18:21] <s`> ubuntu 15.04
[18:22] <s`> im just trying to ssh into the phone, but i need to edit sshd_config lol
[18:22] <s`> or maybe it's easier to wget my public key from somewhere
[18:22] <Acou_Bass> theres probably a way to add custom keysets to it
[18:22] <Acou_Bass> + yeah i just did that, no need to edit sshd
[18:29] <Acou_Bass> i ws sure ther was a way to edit the keysets on the terminal.... cant remember how and cant find it
[18:29] <Acou_Bass> XD
[18:43] <s`> Acou_Bass: u think it's safe to install packages from xenial? cause i can't find many packages in vivid :\
[18:43] <Acou_Bass> you mean packages with apt-get? id so no to begin with there before even doing cross-release installing :P
[18:43] <ahayzen> Hi, anyone know where the logs for pulseaudio should be? or how i can find out why it hasn't started ?
[18:44] <s`> syslog i'd say
[18:44] <s`> mine is started with --log-target=syslog option
[18:45] <ahayzen> all i have in there is "ubuntu-phablet pulseaudio[2347]: [pulseaudio] main.c: Daemon startup failed."
[18:46] <s`> tried to start it in foreground and see if it crashes?
[18:46] <s`> my cmdline is:  pulseaudio --start --log-target=syslog
[18:47] <ahayzen> it'll be fine if i reboot my phone, i'm just trying to figure out why randomly pulse+media-hub+indicator-sound don't start on my device
[18:48] <s`> it'll be fine even if you start manually after failing?
[18:49] <s`> Acou_Bass: what OTA are you?
[18:50] <ahayzen> yeah starting it manually it seems to have worked i get "[pulseaudio] pid.c: Stale PID file, overwriting." and then something about bluez but the process has stayed running
[18:51] <s`> peraphs you had a stale pid file and it didnt overwrote it at boot
[18:51] <s`> but i really dont know sorry
[18:51] <ahayzen> yeah idk, i'll have a talk with the media guys in the week, thanks for the pointers :-)
[19:58] <brunch875> I see the utouch system settings on the desktop is getting progress
[19:58] <brunch875> gjjjj!!
[20:01] <MacBook> Hi
[20:03] <MacBook> I reset my Aquaris E4.5 Ubuntu Edition, in the all new set up wizard I have a field that I don't know how to fill it? Preferred name (at last step: Personalized your device)
[20:03] <MacBook> I check it, it is not related to host-name
[20:03] <MacBook> host name is default as ubuntu-phablet
[20:07] <MacBook> I reset my Aquaris E4.5 Ubuntu Edition, in the all new set up wizard I have a field that I don't know how to fill it? Preferred name (at last step: Personalized your device)
[20:15] <dobey> i presume it's the device name used in bluetooth perhaps
[20:17] <MacBook> but bluetooth not changed yet!
[22:24] <Acou_Bass> s`: im using stable OTA on nexus 4
[23:28] <MVP> Please how can i use prxt on the ubuntu touch.
[23:30] <Acou_Bass> prxt? whatsthat
[23:48] <kristofer> hello!
[23:49] <kristofer> I'm still stuck with this message "This phone needs restoring from a PC or a service center"
[23:50] <kristofer> I'm installing it on a nexus 7 that has stock android 6.0.1; do I need to go back to 4.4 in order to make this work?
[23:55] <podbay> I'm going through the CurrencyConverter tutorial, but the uris for the xml feed and namespace seem to have changed.  Is this updated anywhere?


[05:31] -queuebot:#ubuntu-release- New: accepted linux-signed-oem-osp1 [amd64] (bionic-proposed) [5.0.0-1019.21]
[05:34] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-59.66~16.04.1] (kernel)
[05:37] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-59.66~16.04.1] (kernel)
[05:53] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-59.66~16.04.1]
[05:53] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-59.66~16.04.1]
[06:07] <mwhudson> uh how did the version of golang-github-disintegration-imaging in eoan RELEASE migrate
[06:07] <mwhudson> it never passed on arm64
[06:09] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1051.60] (kernel)
[06:09] <mwhudson> oh no, it did
[06:10] <mwhudson> go 1.10 vs go 1.11 maybe
[06:32] <mwhudson> yes
[07:43] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1051.60]
[09:43] <cpaelzer> There are currently 13 UFW tests on http://autopkgtest.ubuntu.com/running#pkg-ufw; all are stuck on "Test get_netfilter_capabilities() ..." in the "build-needed" stage. This will not recover due to bug 1840633. It would be great if someone could cancel them. FYI: Since I don't exactly know who can do this I posted this on multiple channels.
[10:18] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (xenial-proposed/main) [4.15.0-1022.25~16.04.1] (kernel)
[10:18] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (bionic-proposed/main) [4.15.0-1022.25] (kernel)
[10:21] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (eoan-proposed/main) [5.2.0-13.14] (core, kernel)
[10:21] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (eoan-proposed/main) [5.2.0-13.14] (core, kernel)
[10:21] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (eoan-proposed/main) [5.2.0-13.14] (core, kernel)
[10:23] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (bionic-proposed) [4.15.0-1022.25]
[10:23] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (eoan-proposed) [5.2.0-13.14]
[10:23] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (eoan-proposed) [5.2.0-13.14]
[10:23] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (eoan-proposed) [5.2.0-13.14]
[10:24] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (xenial-proposed) [4.15.0-1022.25~16.04.1]
[11:23] -queuebot:#ubuntu-release- New binary: x265 [i386] (eoan-proposed/universe) [3.1.1-2] (kubuntu)
[11:29] <Laney> cpaelzer: the PPA ones?
[11:31] -queuebot:#ubuntu-release- New binary: x265 [amd64] (eoan-proposed/universe) [3.1.1-2] (kubuntu)
[11:32] <cpaelzer> Laney: there are a bunch from PPAs yes
[11:32] <cpaelzer> Laney: and there is one on I think armhf which is on for 75h
[11:32] <Laney> ok
[11:32] <cpaelzer> that as well
[11:33] <cpaelzer> Until I have found the root cause there might be more to come :-/
[11:33] <Laney> I'm sshed into an instance which has hung right now
[11:33] <cpaelzer> Laney: are you ok if I might ming you late ron for more of these aborts?
[11:33] <Laney> do you want something from it?
[11:33] <cpaelzer> or is there any self-empowering that I could do it on my own
[11:33] <cpaelzer> we ones that hang right now are useless IMHO
[11:33] <Laney> like some debugging information
[11:33] <cpaelzer> I have some prepared which will report debug info
[11:34] <Laney> https://paste.ubuntu.com/p/9PxrWRMkJc/
[11:34] <Laney> ok
[11:34] <cpaelzer> Laney: well, how much could we get from the current systems?
[11:34] <Laney> well I can run things ...
[11:34] <cpaelzer> oh nice
[11:34] <cpaelzer> so you can actually log in
[11:34] <Laney> you could probably do the same via canonistack
[11:34] <cpaelzer> nice to iptables actually is busy there
[11:34] <cpaelzer> vry useful
[11:35] <Laney> if it's something that breaks the SSH runner somehow
[11:35] -queuebot:#ubuntu-release- New binary: x265 [s390x] (eoan-proposed/universe) [3.1.1-2] (kubuntu)
[11:35] <cpaelzer> the problem is that it is at build time (build-needed from autopkgtest)
[11:36] <cpaelzer> which is odd, the actual same build on LP infra works fine
[11:36] <cpaelzer> only in this autopkgcontext it fails
[11:36] <cpaelzer> but seeing the hanging iptables command is interesting
[11:36] <cpaelzer> Laney: how could I submit commands against it?
[11:36] <Laney> via my fingers
[11:36] <cpaelzer> sure, then the first two thing I'd want to see are
[11:36] <Laney> or try canonistack (autopkgtest w/ssh runner), like I say - bet it happens there too
[11:37] <cpaelzer> let me hand you two commands and then I can give ssh runner via canonistack a chance later
[11:37] <Laney> ok
[11:37] <cpaelzer> never doen that if there is any docu/script/hint on that I'd appreciate a link
[11:37] <cpaelzer> 1. cat /proc/25819/wchan
[11:38] <Laney> no link, it only recently became feasible
[11:38] <cpaelzer> 2. strace of 25819 (if you can submit semi interactive commands)
[11:38] -queuebot:#ubuntu-release- New binary: x265 [armhf] (eoan-proposed/universe) [3.1.1-2] (kubuntu)
[11:38] <cpaelzer> I already thank you for the suggestion, that sounds like the most similar environment that I could get
[11:39] -queuebot:#ubuntu-release- New binary: x265 [arm64] (eoan-proposed/universe) [3.1.1-2] (kubuntu)
[11:39] <Laney> wchan is 0
[11:39] <Laney> strace: https://paste.ubuntu.com/p/5Z745G963k/ <- that repeating endlessly
[11:39] <cpaelzer> ok so it is really busy
[11:40] <cpaelzer> Thank you so much
[11:40] <cpaelzer> back trying ssh runner after lunch ...
[11:41] <cpaelzer> Laney: you can kill all of those currently up then, they won't complete
[11:41] -queuebot:#ubuntu-release- New binary: x265 [ppc64el] (eoan-proposed/universe) [3.1.1-2] (kubuntu)
[11:41] <Laney> juliank might be able to help you with that, think he did it
[11:43] <juliank> manually running autopkgtest on canonistack?
[11:44] <Laney> ssh runner
[11:44] <juliank> I only played with the entire cloud thing
[11:48] <Laney> ah well
[11:49] <Laney> Should be doable by copying the first line of an autopkgtest log from autopkgtest.u.c, and removing all the production specific bits about ftpmaster.internal and proxies
[11:52] <Laney> (ufws are killed)
[12:05] <juliank> Laney: doesn't it also need an image built though?
[12:06] <Laney> you can probably use an upstream one
[12:10] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1056.61] (kernel)
[12:12] <cpaelzer> Thanks Laney
[12:58] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1056.61]
[13:03] <cpaelzer> Laney: juliank: I was wondering if the network rules in this might be important --security-groups<EMAIL_ADDRESS>[13:03] <cpaelzer> do you have a way to query their definition?
[13:03] <cpaelzer> they don't seem to exist in any place of *stack that I can touch
[13:06] <Laney> cpaelzer: I doubt it, that's just a firewall at the cloud level - nothing the instances themselves see
[13:06] <cpaelzer> hmm, ok thanks
[13:07] <cpaelzer> I didn't get --flavor autopkgtest running nor the special image type, but I fell back to a normal eoan image with m1.mediuam
[13:07] <cpaelzer> should be pretty similar
[13:07] <cpaelzer> test is still running
[13:07] <cpaelzer> lets hope the issue triggers there
[13:07] <Laney> fingers crossed
[13:17] <juliank> cpaelzer: It's just copies of the default security group
[13:17] <juliank> for scaling reasons
[13:17] <juliank> IIRC
[13:18] <Laney> something something mumble openstack
[13:54] -queuebot:#ubuntu-release- Unapproved: amd64-microcode (disco-proposed/main) [3.20181128.1ubuntu1 => 3.20181128.1ubuntu1.1] (core)
[13:59] -queuebot:#ubuntu-release- Unapproved: amd64-microcode (bionic-proposed/main) [3.20180524.1~ubuntu<IP_ADDRESS> => 3.20181128.1~ubuntu<IP_ADDRESS>] (ubuntu-desktop, ubuntu-server)
[14:02] -queuebot:#ubuntu-release- Unapproved: amd64-microcode (xenial-proposed/main) [3.20180524.1~ubuntu<IP_ADDRESS> => 3.20181128.1~ubuntu<IP_ADDRESS>] (no packageset)
[14:40] <gpiccoli> Hi SRU vanguard, could you please skip/force-badtest the autopkgtesting for makedumpfile/1:1.6.6-2ubuntu1 (eon-proposed) on ppc64el?
[14:40] <gpiccoli> Justification can be found here: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/comments/37
[14:40] <gpiccoli> Tnx in advance =)
[14:40] <gpiccoli> slashd, cascardo  ^
[14:40] <Odd_Bloke> gpiccoli: Why would the SRU vanguard touch the autopkgtests for the development release?
[14:41] <gpiccoli> Odd_Bloke, I don't know hehe I thought in pinging them
[14:41] <Odd_Bloke> (I am neither an SRU vanguard, nor anyone else you might want to talk to, but I suspect you're asking the wrong people. :)
[14:41] <gpiccoli> Odd_Bloke, is there anybody that can look that?
[14:41] <gpiccoli> Perhaps Odd_Bloke hehehe
[14:41] <Odd_Bloke> up enter ;)
[14:41] <gpiccoli> What I want is an exemptioon for this test, since we may have some form of test infrastructure issue
[14:42] <gpiccoli> what is "up enter" Odd_Bloke ?
[14:42] <gpiccoli> probably this is a silly question hehe, sorry if it's the case
[14:43] <Odd_Bloke> gpiccoli: I just meant "read my last message", apologies for not being clear! :)
[14:44] <gpiccoli> OK Odd_Bloke, no problem
[14:58] <slashd> Odd_Bloke, I think what gpiccoli needs is an archive admin for them to let the package through.
[15:00] <slashd> rbasak, ? Am I right here ^
[15:01] <rbasak> I think it's ~ubuntu-release
[15:01] <rbasak> You can file a bug against https://code.launchpad.net/~ubuntu-release/britney/hints-ubuntu
[15:01] <rbasak> an MP sorry
[15:02] <slashd> gpiccoli, that should answer your question about how to proceed ^
[15:02] <slashd> thanks rbasak, much appreciated !
[15:02] <rbasak> np!
[15:02] <gpiccoli> tnx slashd, rbasak
[15:08] <gpiccoli> just confirming with ubuntu-release team: to be able to get the package released before the freeze, I need an exemption in the test failure for ppc64el - the way to this is to fill MP forcing the badtest?
[15:08] <gpiccoli> vorlon ^
[15:12] <gpiccoli> Laney ^ too (sorry, forgot to loop you!)
[15:48] <vorlon> gpiccoli: yes, MP welcome
[15:50] <gpiccoli> ok vorlon, thanks
[15:56] -queuebot:#ubuntu-release- Unapproved: opencryptoki (bionic-proposed/universe) [3.9.0+dfsg-0ubuntu1.1 => 3.9.0+dfsg-0ubuntu1.2] (no packageset)
[16:48] <mdeslaur> can the SRU in bug 1835968 please be released now?
[16:55] -queuebot:#ubuntu-release- New binary: mysql-8.0 [s390x] (eoan-proposed/main) [8.0.16-0ubuntu3] (no packageset)
[16:57] <vorlon> mdeslaur: looking
[16:58] <vorlon> mdeslaur: released
[16:59] <mdeslaur> thanks vorlon
[17:06] -queuebot:#ubuntu-release- New binary: mysql-8.0 [amd64] (eoan-proposed/main) [8.0.16-0ubuntu3] (no packageset)
[17:09] -queuebot:#ubuntu-release- New binary: mysql-8.0 [ppc64el] (eoan-proposed/main) [8.0.16-0ubuntu3] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: python-py2bit [amd64] (eoan-proposed/universe) [0.3.0-2] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: python-py2bit [s390x] (eoan-proposed/universe) [0.3.0-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: python-py2bit [i386] (eoan-proposed/universe) [0.3.0-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: python-py2bit [arm64] (eoan-proposed/universe) [0.3.0-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: python-py2bit [armhf] (eoan-proposed/universe) [0.3.0-2] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: python-py2bit [ppc64el] (eoan-proposed/universe) [0.3.0-2] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: mysql-8.0 [i386] (eoan-proposed/main) [8.0.16-0ubuntu3] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: wireshark [s390x] (eoan-proposed/universe) [3.0.3-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: wireshark [i386] (eoan-proposed/universe) [3.0.3-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: wireshark [ppc64el] (eoan-proposed/universe) [3.0.3-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New: accepted wireshark [i386] (eoan-proposed) [3.0.3-1]
[17:38] -queuebot:#ubuntu-release- New: accepted wireshark [ppc64el] (eoan-proposed) [3.0.3-1]
[17:38] -queuebot:#ubuntu-release- New: accepted python-py2bit [amd64] (eoan-proposed) [0.3.0-2]
[17:38] -queuebot:#ubuntu-release- New: accepted python-py2bit [armhf] (eoan-proposed) [0.3.0-2]
[17:38] -queuebot:#ubuntu-release- New: accepted python-py2bit [ppc64el] (eoan-proposed) [0.3.0-2]
[17:38] -queuebot:#ubuntu-release- New: accepted wireshark [s390x] (eoan-proposed) [3.0.3-1]
[17:38] -queuebot:#ubuntu-release- New: accepted python-py2bit [arm64] (eoan-proposed) [0.3.0-2]
[17:38] -queuebot:#ubuntu-release- New: accepted python-py2bit [s390x] (eoan-proposed) [0.3.0-2]
[17:38] -queuebot:#ubuntu-release- New: accepted python-py2bit [i386] (eoan-proposed) [0.3.0-2]
[17:39] -queuebot:#ubuntu-release- New: accepted python-alignlib [ppc64el] (eoan-proposed) [0.1.1-1]
[17:39] -queuebot:#ubuntu-release- New: accepted x265 [arm64] (eoan-proposed) [3.1.1-2]
[17:39] -queuebot:#ubuntu-release- New: accepted x265 [i386] (eoan-proposed) [3.1.1-2]
[17:39] -queuebot:#ubuntu-release- New: accepted x265 [s390x] (eoan-proposed) [3.1.1-2]
[17:39] -queuebot:#ubuntu-release- New: accepted x265 [amd64] (eoan-proposed) [3.1.1-2]
[17:39] -queuebot:#ubuntu-release- New: accepted x265 [ppc64el] (eoan-proposed) [3.1.1-2]
[17:39] -queuebot:#ubuntu-release- New: accepted x265 [armhf] (eoan-proposed) [3.1.1-2]
[17:39] -queuebot:#ubuntu-release- New: accepted python-alignlib [s390x] (eoan-proposed) [0.1.1-1]
[17:56] -queuebot:#ubuntu-release- New binary: mysql-8.0 [armhf] (eoan-proposed/main) [8.0.16-0ubuntu3] (no packageset)
[17:56] <lordcirth> Did the root-on-ZFS installer option make it into 19.10? I don't see it in the daily ISO
[18:36] <Eickmeyer> vorlon: If you can, could you look at raysession? teward uploaded another one, it's binNEW.
[18:36] -queuebot:#ubuntu-release- New binary: mysql-8.0 [arm64] (eoan-proposed/main) [8.0.16-0ubuntu3] (no packageset)
[18:46] <teward> *is pinged*
[19:16] <cyphermox> could anyone please help with pyyaml 5.1.2-1 in eoan-proposed? grr and python-asdf appear to me to be badtest (grr is an unrelated failure, and python-asdf is due to enddianness in tests); salt seems to reliably timeout, I'm not sure how to deal with that
[19:18] -queuebot:#ubuntu-release- Unapproved: s390-tools (eoan-proposed/main) [2.10.0-0ubuntu2 => 2.10.0-0ubuntu2] (core)
[19:35] <rbasak> vorlon: ^ that's the last of the binaries for mysql-router from src:mysql-8.0. This adds a binary built from the same source (it was being build anyway). It isn't on the critical path for the MySQL transition but I uploaded it since we want it for Eoan, it's a feature and feature freeze is coming up.
[19:35] <rbasak> Note that we know about shipping libmysqlrouter*.so*. We're looking into statically linking it instead since it isn't intended that the package supplies a library used externally - it's an internal thing and doesn't really need to be a shared object.
[19:36] <rbasak> In the meantime we put it in /usr/lib/mysql-router/ to keep it out of the way.
[19:36] <rbasak> I hope that's OK.
[19:37] <rbasak> (and /usr/lib/mysql-router/mysqlrouter/ contains plugins for the binary but that's normal)
[20:43] -queuebot:#ubuntu-release- New: accepted rustc [amd64] (eoan-proposed) [1.36.0+dfsg1+llvm-2ubuntu1]
[20:43] -queuebot:#ubuntu-release- New: accepted rustc [armhf] (eoan-proposed) [1.36.0+dfsg1+llvm-2ubuntu1]
[20:43] -queuebot:#ubuntu-release- New: accepted rustc [ppc64el] (eoan-proposed) [1.36.0+dfsg1+llvm-2ubuntu1]
[20:43] -queuebot:#ubuntu-release- New: accepted rustc [arm64] (eoan-proposed) [1.36.0+dfsg1+llvm-2ubuntu1]
[20:43] -queuebot:#ubuntu-release- New: accepted rustc [s390x] (eoan-proposed) [1.36.0+dfsg1+llvm-2ubuntu1]
[20:43] -queuebot:#ubuntu-release- New: accepted rustc [i386] (eoan-proposed) [1.36.0+dfsg1+llvm-2ubuntu1]
[22:43] -queuebot:#ubuntu-release- New: accepted mysql-8.0 [amd64] (eoan-proposed) [8.0.16-0ubuntu3]
[22:43] -queuebot:#ubuntu-release- New: accepted mysql-8.0 [armhf] (eoan-proposed) [8.0.16-0ubuntu3]
[22:43] -queuebot:#ubuntu-release- New: accepted mysql-8.0 [ppc64el] (eoan-proposed) [8.0.16-0ubuntu3]
[22:43] -queuebot:#ubuntu-release- New: accepted mysql-8.0 [arm64] (eoan-proposed) [8.0.16-0ubuntu3]
[22:43] -queuebot:#ubuntu-release- New: accepted mysql-8.0 [s390x] (eoan-proposed) [8.0.16-0ubuntu3]
[22:43] -queuebot:#ubuntu-release- New: accepted mysql-8.0 [i386] (eoan-proposed) [8.0.16-0ubuntu3]
[22:44] <vorlon> rbasak: ^^ various lintian messages on mysql-router (with lintian -I), but nothing blocking
[22:44] -queuebot:#ubuntu-release- New: accepted raysession [amd64] (eoan-proposed) [0.7.2-0ubuntu2]
[22:44] <vorlon> Eickmeyer: ^^
[22:44] <Eickmeyer> vorlon: Thanks!!!
[22:51] <rbasak> Thanks!
[23:18] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (bionic-proposed/main) [5.0.0-1017.18~18.04.1] (kernel)
[23:18] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (disco-proposed/main) [5.0.0-1017.18] (core, kernel)


[10:26] <Riddell> who can tell me what's wrong with kwrited-data in proposed
[10:30] <Riddell> I removed it from the kwrited source package and I ran remove-package but it still complains in update_excuses
[10:33] <Laney> Riddell: I still see it in vivid-proposed. Did you wait for the publisher?
[10:35] <cjwatson> https://launchpad.net/ubuntu/vivid/amd64/kwrited-data still shows it as published.  What was your remove-package command line?
[10:36] <cjwatson> Riddell: ^-
[10:36] <cjwatson> That's not just a "wait for publication" issue; the removal didn't happen.
[10:36]  * Laney nods
[10:36] <Riddell> seems to have disappeared from my bash history
[10:37] <cjwatson> Should be: remove-package -m 'some reason' -s vivid-proposed -b kwrited-data
[10:38] <Riddell> ok run that now, let's see if that helps, thanks cjwatson
[10:38] <Riddell> whatever will we do when you're no longer around!
[10:39] <cjwatson> Oddly your removal seems to have worked for some arches but not others.
[10:39] <cjwatson> See https://launchpad.net/ubuntu/vivid/powerpc/kwrited-data
[10:39] <cjwatson> I'll still be around to diagnose Launchpad-related weirdness :-)
[10:40] <cjwatson> Oh, from the publication history above, looks like you removed it from vivid rather than from vivid-proposed, I think
[11:46] <infinity> Riddell: When you can't bug Colin, I'm sure you'll find someone else who knows most of the same answers.
[13:56] <teward> if I want specific built binaries removed from current Ubuntu releases (not the dev release), do I have to bug the tech board about it, or is there a specific list I should email to for discussing it?
[13:57] <infinity> teward: As a general rule, the answer to that is "no".
[13:58] <infinity> teward: A first starting point would to mail the ubuntu-archive list about it, though.
[13:58] <teward> infinity: okay... that kind of explains that, and was assumed, the issue being E:NotFixableAndNeverMaintainedAnymore for specific binaries in a source package, but meh
[14:01] <infinity> teward: We've done SRUs in the past to disable specific bits of software and point users in a more supportable direction, but that should also be considered a last (or second-last, I guess) resort.
[14:03] <teward> infinity: right, the issue here goes back to https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1392319, a case of the naxsi that's included in that being ancient beyond reason, and it being dropped in Debian because nobody on the Debian maintaners for the nginx package use naxsi and can support or diagnose it.  with users still using it and it being filled with holes and those specific binaries not being supportable, I'm not sure
[14:03] <teward> whether it can even be sanely kept...
[14:03] <ubot2> Launchpad bug 1392319 in nginx (Ubuntu) "naxsi-ui-extract does not work" [Undecided,New]
[14:03] <teward> but again, as you said, last or second-last resort...
[14:04] <teward> i think it's more of a case that "This is never going to be fixed and we don't maintain it anywhere anymore", for the bug and package, but that kind of breaks triage guidelines...
[14:04] <teward> (specifically for the nginx-naxsi-* binaries)
[14:07] <teward> infinity: i'll probably end up emailing the list anyways.  but i have a few other things on my radar first
[14:45] <infinity> teward: Does one of the other flavours support everything naxsi does except for the naxsi bit itself?
[14:46] <infinity> teward: An unfriendly-but-workable solution would be to turn nginx-naxsi into an empty package that depends on another flavour, and pops up a preinst note telling the user that they're about to be shafter and sidegraded, and why that is.
[14:46] <teward> infinity: AFAIK naxsi is unique - there's nothing that does what naxsi does.  I"m already beyond the argument of making the package empty
[14:47] <infinity> teward: But it might also pay to discuss with Debian what they plan to do for their stable releases.
[14:47] <teward> infinity: i know it's already dropped in testing - the unstable changes as such migrated
[14:48] <teward> infinity: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746199#18 is the most relevant
[14:48] <ubot2> Debian bug 746199 in src:nginx "Outdated naxsi version, incorrect learning tools included in packages" [Important,Fixed]
[14:48] <teward> even states as such that the "naxsi packages are going to be removed before jessie is frozen"
[14:48] <infinity> teward: Right, I can see what they've done for jessie, I meant what they plan to do for wheezy.
[14:48] <teward> infinity: i don't think they can make the changes in wheezy
[14:49] <teward> infinity: i'm not on their maintainers team, but I can poke people and see what they're thinking
[14:50] <infinity> teward: Well, my gut feeling would be "fix the broken tool" (or replace it with the right one, if it's literally the wrong tool).
[14:51] <teward> infinity: and therein lies the crucial issue, and rbasak echoed that
[14:51] <infinity> teward: As for "it's old and upstream has moved on", the answer is generally "too bad".  That's true of all software in a stable distribution.
[14:51] <rbasak> I suggested to just leave a Trusty task open.
[14:51] <teward> infinity: right, again, i'm already well past my initial question
[14:51] <teward> exactly
[14:51] <teward> rbasak: i pinged you after my first comment here :)
[14:51] <rbasak> If someone does come along with something SRU-able that fixes everything, then we wouldn't refuse that.
[14:52] <infinity> Thankfully, those packages are in universe, so no one has actually committed to supporting them.
[14:52] <infinity> Aren't we glad we split that up. :P
[14:52] <rbasak> :)
[14:53] <teward> rbasak: in the mean time per your recommendation i'm writing a comment on the bug that there's nobody to maintain the naxsi section, so it'll just remain open until someone in the community tries and supports it
[14:53] <rbasak> Though in part, I presume nobody reviewed naxsi for supportability because it wasn't a candidate for main
[14:53] <teward> infinity: yeah, definitely glad about that, nginx core plugins behave themselves :P
[14:53] <teward> rbasak: yeah, probably that, bigger issue is that it still has third-party modules in it, so sarnold's initial argument about the third-party plugins in the MIR for nginx remains.
[17:19] <elfy> Laney: hey - apparently you're the owner of the vid for the 15:00 release session - the video at summit isn't viewable
[17:21] <Laney> I know, it's processing
[17:21] <Laney> youtube needs more hamsters
[17:22] <elfy> okey doke - thanks Laney :)
[18:14] <Laney> elfy: there
[18:55] <bdmurray> tracker doesn't fall under the gnome MRE does it?
[18:58] <elfy> Laney: cheers


[05:15] <nigelb> AlanBell: Your kind of game http://type.method.ac
[08:25] <czajkowski> aloha
[19:49] <mhall119> jcastro: give me a ping when you're around
[19:49] <jcastro> yo
[19:50] <cjohnston> that was too long
[19:51] <cjohnston> to respond
[19:54] <jussi> ahh, back to KDE <3
[19:55] <mhall119> jcastro: sorry, my irc is slow
[20:02] <jcastro> mhall119: what did you need?
[20:06] <mhall119> jcastro: was wondering if you saw my post about Summit development
[20:06] <jcastro> no, where at?
[20:09] <mhall119> jcastro: give me one second, I'm having to ressurect apache
[20:09] <mhall119> yahoo's bot kills my t1.micro
[20:10] <jcastro> heh
[20:10] <jcastro> micros are so worthless
[20:12] <mhall119> yeah, but they're cheap
[20:12] <mhall119> and a convenient place to run irssi
[20:12] <mhall119> jcastro: http://mhall119.com/2011/10/uds-p-summit-development-cycle/
[20:13] <jcastro> oh nice!
[20:13] <jcastro> so hey, do you think we'll have the double page thing done?
[20:14] <jcastro> the &page=1 and all that?
[20:16] <mhall119> jcastro: i think AlanBell was starting on that, if not i can knock it out tomorrow
[20:16] <jcastro> okey
[20:17] <AlanBell> linaro has a hacked together "just rooms with linaro sessions in" view
[20:17] <jcastro> ah
[20:17] <jcastro> do you think we could get the inverse?
[20:17] <jcastro> I think even without the linaro rooms we don't fit on one panel anyway right?
[20:17] <AlanBell> well, I think it is an ugly hack
[20:18] <AlanBell> should be based on tracks
[20:18] <AlanBell> or possibly arbitary sets of rooms
[20:26] <cjohnston> the problem is that linaro keeps hacking in linaro stuff... which sucks.
[20:36] <AlanBell> hacking in multiple conference support is a good thing
[20:37] <AlanBell> hacking in stuff that depends on a conference with 'linaro' in the track and session slugs isn't so great
[20:39] <mhall119> AlanBell: next cycle perhaps
[20:39] <mhall119> too late now
[20:39] <AlanBell> sure
[20:39] <mhall119> AlanBell: will you be at UDS?
[20:39] <AlanBell> not this one
[20:39] <mhall119> too bad
[20:40] <cjohnston> AlanBell: i agree
[20:41] <cjohnston> we need to seperate UDS and LDS in summit.. but make sure that summit is aware that both events are taking place at the same time, and not allow one person to be scheduled for something at each event at the same time
[20:42] <jcastro> cjohnston: hey I need that travel info for when you plan on stopping by
[20:43] <AlanBell> oh, my local summit is broken after upgrading to oneiric
[20:43] <AlanBell> (could be unrelated to that)
[20:45] <AlanBell> argh, it could be the django update
[20:46] <cjohnston> jcastro: we are just gonna park at the dock...
[20:46] <jcastro> ok
[20:46] <cjohnston> we are driving down there monday the 17th, and get back tuesday the 25th
[20:47] <cjohnston> are you home those two days
[20:48] <AlanBell> fixored. Summit doesn't run by default on oneiric.
[20:48] <cjohnston> AlanBell: no it doesnt.. outdated versions suck
[20:49] <AlanBell> its fine, a one line fix
[21:03] <AlanBell> thinking of having a URL like this-> http://summit.ubuntu.com/uds-p/roomset?rooms=antigua-1,antigua-2,grand-sierra-f
[21:05] <jcastro> oooh
[21:05] <cjohnston> I think pg 1 pg 2 would be better
[21:06] <cjohnston> or easier
[21:06] <AlanBell> how do you work out what goes on which page?
[21:06] <mhall119> alphabetical order
[21:06] <AlanBell> this way you could have a screen showing "stuff on this floor"
[21:06] <mhall119> or we can just give a list of room ids, it'd be shorter than names
[21:06] <mhall119> AlanBell: only one floor
[21:07] <AlanBell> brussels wasn't
[21:07] <mhall119> fancy belgians
[21:08] <AlanBell> but anyhow, that was an example of why you might want the flexibility to do a schedule of an arbitary set of rooms
[21:09] <mhall119> true
[21:09] <mhall119> I think that would be better, if not easier
[21:09] <AlanBell> I think it would be easier :)
[21:10] <mhall119> though I'm not sure how useful "stuff on this floor" would be
[21:10] <mhall119> I don't want to miss out on interesting sessions just because they're on a different floor from my last session
[21:11] <cjohnston> well... that would be have a monitor "this floorr" and a monitor "first floor"
[21:11] <AlanBell> three monitors stacked vertically
[21:12] <mhall119> I'm beginning to think the monitors approach just doesn't scale well
[21:12] <AlanBell> however, the point is to have a way of doing ubuntu rooms, and linaro rooms, allowing for overlap, and allowing dual monitor setups
[21:12] <mhall119> properly segregating concurrent summits would give us that
[21:13] <AlanBell> if you just pass a room list on the query string then you can do anything
[21:13] <mhall119> AlanBell: have you started on that yet?
[21:13] <cjohnston> mhall119: I am all for doing that... we just need jcastro to give us permission
[21:14] <mhall119> since when do we need his permission? :)
[21:14] <cjohnston> I think that would be the best easiest cleanest way
[21:14] <cjohnston> ok then.. lets do it!
[21:14] <jcastro> permission for what?
[21:14] <mhall119> I thought AlanBell already was!
[21:14] <cjohnston> (we need him to do it tho so that when it breaks we blame him)
[21:14] <AlanBell> not yet mhall119, just looked at the linaro stuff, and in some django documentation on parsing lists in urls or query strings
[21:14] <jcastro> oh, so the way it will be, is the areas around the linaro rooms will have the linaro shcedules
[21:14] <cjohnston> mhall119: im talking the segregating summits
[21:14] <jcastro> and then we can put the uds ones where the UDS TVs will be
[21:14] <jcastro> and certain spots in the middle will have 2 displays, one for linaro, one for UDS
[21:15] <cjohnston> jcastro: can we just do it right, and make them two different summits?
[21:15] <mhall119> cjohnston: oh that, yeah, I wish we could have done that this cycle, but there was just so much work in getting things cleaner and stabilized
[21:15] <jcastro> cjohnston: yeah, sure, just not for this UDS.
[21:15] <cjohnston> its dont
[21:15] <cjohnston> done
[21:15] <AlanBell> if they are different summits you will struggle with room sharing, and people sharing
[21:15] <mhall119> no it's not
[21:16] <cjohnston> mhall119: http://bazaar.launchpad.net/~summit-hackers/summit/trunk/revision/168 ?
[21:17] <cjohnston> i think the scheduler would need a little love.. but its there
[21:17] <mhall119> cjohnston: that just lets one summit use multiple LP Sprint records
[21:17] <cjohnston> o.. i thought it allowed multiple sprints
[21:18] <cjohnston> ahh.. misreading
[21:18] <cjohnston> jcastro: are the rooms that linaro has there stuff in linaro only rooms?
[21:18] <jcastro> some of them
[21:18] <jcastro> and only some of the time
[21:18] <cjohnston> 17.14.33 < jcastro> oh, so the way it will be, is the areas around the linaro rooms will have the linaro shcedules
[21:19] <cjohnston> so we need uds monitors everywhere
[21:19] <jcastro> yeah, the dedicated hackrooms
[21:19] <jcastro> well, it was explained to me that most of our stuff will be in the southern end of the place
[21:19] <jcastro> they will basically be at the end of each hallway
[21:20] <jcastro> cjohnston: I figure just make it flexible enough to be able to show the rooms we want like alan says
[21:20] <jcastro> IS is handling the # of TVs and where to put them, etc.
[21:20] <cjohnston> ok
[21:23]  * AlanBell has a functional schedule for UDS Quintisential Quoll


[07:18] <dholbach> good morning
[15:21] <locodir-useroleo> since i installed ubuntu 13.04 my pc is very slow any help please
[18:50] <trinikrono> happy emancipation from ubuntu-tt todays a holiday :D


[03:53] <quidnunc> Is prevu no longer maintained?
[05:08] <micahg> tumbleweed: hrm, will sks be unusable in precise once the pool changes or can individuals still have uses for it?
[06:52] <tumbleweed> micahg: perfectly usable, but you wan't get any traffic from sks-keyservers.net
[06:53] <micahg> tumbleweed: ok, backport it is then
[06:53] <tumbleweed> the big feature 1.1.1 is missing (IIRC) is subkey -> key resolution
[06:59] <dholbach> good morning
[07:02] <geser> good morning
[07:03] <dholbach> hi geser
[08:23] <iulian> Morning dholbach, geser.
[08:23] <dholbach> hi iulian
[08:24] <iulian> How's it going dholbach? All good?
[08:24] <dholbach> good good - how about you?
[08:25] <iulian> Not too bad. :)
[08:28] <geser> Hi iulian
[08:29] <nigelb> Morning geser, dholbach, iulian :)
[08:29]  * nigelb likes how this is all very circular
[08:29] <dholbach> hi nigelb
[08:29] <nigelb> 8
[08:30] <nigelb> grr
[08:30] <nigelb> clearly, I meant to go to window 8 there.
[13:03] <vibhav> coolbhavi: ping
[13:04] <coolbhavi> vibhav, hey
[13:04] <vibhav> coolbhavi: PM?
[13:04] <coolbhavi> yes
[14:41] <PaoloRotolo> Hi all
[15:07] <gigix> hi
[15:53] <trijntje> Hi all, I'm trying to learn about building packages using recipes by following https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted
[15:53] <trijntje> however, the example fails to build and the "list of daily builds in launchpad" returns an error. Any pointers on what to do next would be appreciated
[16:02] <tumbleweed> keep reloading the daily builds list. When pages time out, that usually works
[16:03] <tumbleweed> I filed a bug 905792 for that
[16:04] <tumbleweed> trijntje: anyway, more to the point "returns an error" isn't very useful for anyone who may help you
[16:05] <tumbleweed> if you can pastebin the command you ran and its output, that's far more helpful
[16:06] <trijntje> the output form running pbuilder: http://paste.ubuntu.com/1074998/
[16:07] <tumbleweed> looks like you're mostly there
[16:07] <tumbleweed> python -m testtools.run wikkid.tests.test_suite
[16:08] <tumbleweed> is failing
[16:08] <tumbleweed> you need to figure out why
[16:15] <trijntje> tumbleweed: thanks. But I know nothing about wikkid, so I have to clue what to look for. I'll just see if there's something else I can get to build
[16:49] <trijntje> got the it to work for the project I was aiming for, so all is well
[16:58] <tumbleweed> good :)
[20:35] <cousteau> apparently there's a branch of Qucs called "qucs-qt4"
[20:36] <cousteau> for some reason it seems to have been abandoned...
[20:36] <cousteau> ...not really called qucs-qt4, but it's been there for quite a while
[20:57] <cousteau> ...actually it doesn't seem to be Qt4 at all...


[01:21] <Peng_> mwhudson: Hi.
[01:21] <mwhudson> Peng_: hi
[01:21] <Peng_> (Actually, I'm totally not here right now.)
[01:21] <mwhudson> i was going to ask something about loggerhead, but i forget wat
[01:21] <Peng_> mwhudson: Anyway, w -- ah.
[01:22] <mwhudson> i was probably just going to tell you to merge your branches, but i see they have merge proposals so i'll comment there i guess :)
[01:22] <igc> morning all
[01:22] <mwhudson> when i emerge from my pile of email
[01:22] <mwhudson> hello igc
[01:22] <Peng_> igc: Good morning. :)
[01:25] <Peng_> Well, if you remember what it was, I should be back in maybe 30 minutes. Or maybe 1-2 years; I'm a bit tired. :D
[01:25] <Peng_> If I do sleep for 2 years, please don't deprecate pack-0.92 while I'm gone. :D
[01:29] <igc> so today's focus for me: nested-tree review; benchmark, tweak & announce https://launchpad.net/bzr-historycache
[03:24] <levo> hey, anyone around to help a newbie? I'm having problems with getting rename to work.
[03:26] <levo> I modified and moved some files, but bzr mv complains the destination dir. isn't versioned
[03:26] <levo> or if I add the destination dir, it complains the source isn't versioned, but it's marked as removed in bzr status
[03:26] <Peng_> levo: Did you rename the dir as well? Have you bzr added it?
[03:27] <Peng_> levo: Hmm, not sure. But you may want "bzr mv --after".
[03:27] <levo> that's what I'm using, I can't find any way to get it to work though :/
[03:27] <Peng_> Oh.
[03:28] <Peng_> My only other suggestion is that a newer version of bzr might be better, but I really don't know. Sorry.
[03:28]  * Peng_ hopes someone else is here.
[03:28] <Peng_> Pastebinning the list of commands you ran may help.
[03:29] <levo> OK, thanks Peng, I'm not running the RC yet but I'll try that
[03:30] <bob2> did you ad the destination dir?
[03:30] <bob2> bzr add -N thatdir
[03:30] <bob2> then mv --after
[03:31] <levo> It says the target file is already versioned:
[03:31] <levo> bzr: ERROR: Could not move string.h => string.h: reusable/string.h is already versioned
[03:31] <Peng_> bob2: -N?
[03:32] <bob2> then un-add it
[03:32] <levo> to bzr add? it says no such option
[03:32] <bob2> what?
[03:32] <bob2> pastebin the output of 'bzr status'
[03:33] <levo> bzr add -N says no such option, not sure if that's what you mean though
[03:34] <bob2> pastebin the output of 'bzr status'
[03:34] <levo> http://pastebin.com/d6c2d994b
[03:37] <levo> I basically moved the directories 'test' and 'reusable' out of source up to the top level, sorry its kind of spammy
[03:37] <bob2> yowch
[03:37] <bob2> in future, use bzr mv
[03:37] <bob2> that is easy to recover, you also added a bunch of other files
[03:37] <levo> lol I'm hosed aren't I?
[03:38] <bob2> no
[03:38] <spiv> 1.14rc1 adds "bzr mv --auto" which would probably do a good job here.
[03:38] <spiv> (After unadding the moved files, of course)
[03:39] <bob2> mv reusable/threading/ ,,f ; for thing in resuable/* ; do bzr rm --keep $thing ; bzr mv --after rc/$thing $thing ; done ; mv ,,f reusable/threading
[03:39] <bob2> or so
[03:40] <lifeless> spiv: whatcya up to today?
[03:40]  * bob2 wonders if he will ever shake ,,
[03:41] <levo> trying to parse all that, I'm on windows :p
[03:41] <bob2> yowch
[03:41] <lifeless> bob2: {{}}
[03:44] <spiv> lifeless: have finally upgraded to Jaunty, happily minimal fallout so far :)
[03:44] <spiv> lifeless: am about to embark on lunch, but would love a review of http://bundlebuggy.aaronbentley.com/project/bzr/request/%3C20090417141519.GA9721%40steerpike.home.puzzling.org%3E
[03:44] <Peng_> Stupid question because I'm lazy: Can "merge --uncommitted" work over a remote branch?
[03:45] <spiv> Peng_: off the top of my head, no, because we don't (yet?) support reading non-local working trees.
[03:45] <Peng_> Yeah, I just tried it, and you're right.
[03:51] <lifeless> PathNotChild: Path "/extra" is not a child of path "/extra/"
[03:53] <lifeless> spiv: it smells a little off
[04:01] <levo> thanks for the help everyone, I managed to get it all sorted out
[04:02] <levo> kind of understand why it wasn't working automatically now
[04:08] <levo> kind of a confusing diagnostic to say that the source isn't versioned, although I don't know what it should say instead since I don't understand exactly why it couldn't be moved in terms of the internal mechanics
[04:09] <lifeless> I think there is a ui bug
[04:09] <lifeless> but I'm glad you're up and running
[04:10] <levo> thanks! and thanks for bzr, it's awesome
[04:26] <lifeless> spiv: ping
[04:26] <lifeless> spiv: How would you feel if we stopped PathNotChild occuring with foo, foo/
[04:48] <spiv> lifeless: so long as there's no risk of foobar being accidentally allowed, I suppose it's ok.  I'm a little surprised it's not already accepted come to think of it.
[04:48] <spiv> lifeless: I thought it did a bit of path normalisation before checking for PathNotChild?
[05:28] <BasicPRO> blah, bad time for LP to sit down
[05:32] <spm> BasicPRO: which part is sitting down?
[05:32] <BasicPRO> code
[05:34] <spm> wfm. can you give a url or similar?
[05:35] <BasicPRO> http://bazaar.launchpad.net/~tanner/bzr/1.14rc2/files
[05:36] <BasicPRO> click "NEWS"
[05:38] <spm> interesting. readme gives an internal error as well. mwhudson ^^ <==
[05:38]  * mwhudson looks
[05:39] <mwhudson> spm: it's timing out for me, is that what you mean?
[05:39] <BasicPRO> means I broke it? :-(
[05:39] <spm> mwhudson: partially. the NEWS file times out. README gives an informative "Internal Server Error" - nothing else :-(
[05:40] <mwhudson> i wonder if pygments is being insane, or annotate being slow
[05:40] <spm> bouncy time? see if that helps?
[05:41] <mwhudson> won't make a difference for the ISE
[05:44] <spm> mwhudson: I live in hope that it would :-)
[05:44] <mwhudson> um
[05:44] <mwhudson> BasicOSX: i presume "bzr annotate README" works for you?
[05:45] <BasicOSX> yes
[05:46] <mwhudson> hm
[05:50] <mwhudson> BasicOSX: bzr annotate http://bazaar.launchpad.net/~tanner/bzr/1.14rc2/README fails for me
[05:50] <mwhudson> BasicOSX: i don't know what's going wrong, but i plead NMF :)
[05:51] <BasicOSX> does that mean I did something wrong when I setup the branch?
[05:58] <spiv> BasicOSX: it appears you've been hit by bug 354036
[05:58] <BasicOSX> heh
[05:58] <spiv> BasicOSX: did you use your 1.14rc2 branch to push it up? :)
[05:58] <BasicOSX> bzr.dev
[05:58] <spiv> Huh!
[05:59] <spiv> That's a worry :(
[05:59] <BasicOSX> Bazaar (bzr) 1.15dev  r4299
[05:59] <BasicOSX> It would be initial push tho right?
[05:59] <BasicOSX> Not the last one I just did?
[05:59] <spiv> Right.
[05:59] <BasicOSX> that was bzr.dev before patch
[06:00] <spiv> As in, if any pushes had been done with unfixed bzr.dev...
[06:00] <spiv> Ah, phew :)
[06:01] <spiv> Ok that explains it then.  Deleting the branch (or at least deleting the remote .bzr dir) and repushing will fix the problem.
[06:02] <spiv> (I'm not sure that this is the cause of viewing README triggering Internal Server Error, although it could be)
[06:04] <lifeless> I don't think it is
[06:09] <BasicOSX> PQM playing 1.14rc2
[06:10] <lifeless> cool
[06:10] <lifeless> I'm beat; had a fluvax shot yesterday and my arm has been killing me
[06:10] <lifeless> if anyone needs me call my mobile
[06:22] <BasicOSX> grrr, comcast I hate you
[06:23] <mwhudson> spiv, lifeless: it is why viewing README triggers a 50x
[06:23] <mwhudson> at least, the error i got on the command line was the same one i found in the logs
[06:39] <spiv> mwhudson: which error?  I get a "No such file" on the command line.
[06:40] <mwhudson> spiv: maybe BasicOSX has done stuff to the branch already
[06:40] <mwhudson> it ended with
[06:40] <mwhudson>     parent_lines = [parent_cache[parent] for parent in parent_map[key]]
[06:40] <mwhudson> KeyError: ('README-20050309040720-8f368abf9f346b9d'<EMAIL_ADDRESS>[06:42] <spiv> mwhudson: ah ok.  Yes, that does look possibly related.
[08:56] <jelmer> moin
[09:13] <jelmer> looks like all working tree stuff on git indexes is working
[09:13] <jelmer> except for commits
[09:20] <robin_dewd> cool. :-) I got your dulwich and bzr-git stuff from trunks I think and even updated bazaar to trunk as well (1.15dev) and was not able to make much with it at this point
[09:20] <igc> me dinner
[09:24] <jelmer> robin_dewd: what didn't work exactly?
[09:24] <jelmer> there have been a lot of changes in the last few days
[09:25] <robin_dewd> i tried a couple of things with it
[09:25] <robin_dewd> one was to clone a git repository from github (I was excited alright ;-)
[09:25] <robin_dewd> other was to branch from a local repo on a near directory
[09:31] <jelmer> rockstar: if you can get it to blow up with the current version, please file bugs :-)
[09:31] <jelmer> I can get it to work on most things right now, I fixed a couple of nasty issues
[09:42] <bignose> how can I remove an un-wanted loom from a branch?
[09:50] <Kinnison> Not sure, the help for "combine-thread" suggests that will, in the future, unloomify a branch
[09:53] <lifeless> bignose: once it has only one thread its ~= to a branch; just export the thread and remove the loom
[09:53] <lifeless> bignose: obviously this could be improved
[09:54] <bignose> no hackery in the branch that can be done?
[09:55] <lifeless> not trivially no
[09:55] <lifeless> this would work:
[09:55] <lifeless> bzr export-thread ../foo
[09:55] <lifeless> rm -rf .bzr/branch
[09:56] <lifeless> mv ../foo/.bzr/branch .bzr
[09:56] <bignose> can I branch from a loomified branch, and specify that the new branch should *not* have a loom?
[09:56] <lifeless> not currently, its a good idea; you can export the top thread though
[09:56] <bignose> okay, that's the chosen workaround then.
[09:56] <bignose> thanks.
[09:57] <bignose> hmm wait, how do I export from one branch to another branch? exporting to a directory just exports a working tree.
[10:03] <bignose> oh, export-thread
[10:03] <bignose> an undocumented command :-(
[10:04] <bignose> actually, a non-existent command (bzr-loom 1.4.0~bzr93-2)
[10:05] <bignose> so, with no "branch without getting a loom" command, and with no "export-thread" command
[10:06] <bignose> how can I get a branch from branch 'foo/' without a loom?
[10:08] <lifeless> bignose: sorry, its just export-loom
[10:08] <lifeless> export-thread has been discussed not done
[10:13] <bignose> hmm. and if I have no threads, export-loom does nothing?
[10:15] <bignose> attempting to create a thread in a loom that has no threads gives an AssertionError
[10:15] <bignose> assert after_thread is None or after_thread in state.get_threads_dict()
[10:25] <lifeless> uhm, having no threads == having no branch - you have no tips at all
[10:25] <lifeless> I'm not sure how you'd even get to that state
[10:34] <bignose> well, 'bzr show-loom' shows no threads, but 'bzr info', 'bzr check' and 'bzr status' all seem happy
[10:34] <bignose> 'bzr log' shows revisions as expected
[10:36] <jelmer> lifeless: so, it would be nice if it would be possible to support just record_iter_changes() or record_entry_contents() in CommitBuilder implementations
[10:36] <jelmer> lifeless: does it sound sensible to e.g. add a "supports_record_iter_changes" and a "supports_record_entry" contents variable to CommitBuilder
[10:36] <bignose> same when I branch; the new branch is also showing fine, but has no threads when I 'show-loom'
[10:36] <jelmer> lifless: that influences the decision of Commit() as to what to use?
[10:40] <bignose> so, I'm stuck on this branch; if the loom is broken, I don't know what else might break and I don't want to continue relying on this branch
[10:40] <bignose> but apparently I can't remove the loom.
[10:42] <lifeless> jelmer: I want to migrate to just ric
[10:43] <lifeless> jelmer: multiple codepaths indefinitely is not attractive
[10:49] <jelmer> lifeless: Ok
[10:49] <jelmer> lifeless: I'd like a way to say I'd always like ric then :-)
[10:49] <jelmer> lifeless: I already have that for bzr-git
[10:49] <jelmer> and I don't feel like implementing record_entry_contents, too
[10:51] <lifeless> jelmer: there is a comment in commit.py about this
[10:51] <lifeless> jelmer: until its safe in all those cases we can't force it to ric always
[10:51] <lifeless> it will be faster once we can, so its important to aim for that
[10:54] <jelmer> lifeless: hmmok
[10:55] <lifeless> jelmer: in particular you can't have a iter_changes on your trees that is actually both correct-for-status and correct-for-commit when new directories are added and specific files is selected
[10:57] <lifeless> and iter_changes doesn't do excludes at all yet
[10:57] <lifeless> so the fastest way to get ric used only, is to fix these issues in bzr core
[11:01] <bignose> lifeless: okay, a workaround that worked:
[11:01] <bignose> bzr init bzr/ && cd bzr/ && bzr pull ../foo/
[11:01] <bignose> erm, s/init bzr/init bar/
[11:02] <bignose> causes the new branch 'bzr/' to have no loom but have all the revisions from 'foo/' as desired
[11:02] <bignose> argh
[11:02] <bignose> new branch 'bar/' that is.
[11:02] <bignose> damned muscle memory :-)
[11:08] <jelmer> lifeless: hmm
[11:29]  * bignose hopes all his wild assertions about Bazaar looms on the mailing list are actually true
[12:30] <finiteset> how do I checkout an old revision from my project?
[12:33] <lifeless> if you have a tree you're in, bzr revert -r X, or if you want a new tree, bzr branch -r X sourcebranch / bzr checkout -r X sourcebranch
[12:35] <finiteset> I have a project using in bzr and I want to check  out an older revision of it  to a different location.
[13:02] <mars> why does the shelve command offer the options "yes", "no", "finish", and "quit"?  Shouldn't that be "yes", "no", "all", "quit"?
[13:03] <mars> ah, nevermind - finish means "done", doesn't it?  And quit actually means "abort"?
[13:52] <ddaa> Hello,
[13:53] <beuno> hi,
[13:53] <ddaa> When trying to use bzr-hg, "bzr pull ../hg-branch" fail with a "AssertionError: KnitPackRepository('file:///home/david/Documents/Akamao/akamao.bzr/.bzr/repository/') not in write group"
[13:53] <ddaa> raised from File "/usr/lib/python2.6/dist-packages/bzrlib/repository.py", line 660, in add_inventory
[13:54] <ddaa> Any idea what that means, and how I can work around or fix this?
[13:54] <ddaa> I have no idea what this "write group" concept is. Is this something new?
[13:56] <ddaa> Mh... I guess I could try adding some repo.start_write_group() and repo.commit_write_group()...
[13:57] <ddaa> Maybe add in a couple of chicken bones.
[14:07] <ddaa> mh... it will probably be quicker to learn hg than to turn bzr-hg into something usable
[14:09] <lifeless> ddaa: jelmer has a bzr-hg branch that is more advanced, I believe
[14:10] <lifeless> ddaa: write groups are broadly transactions, they are the basis of packs
[14:10] <ddaa> lifeless: hello mate
[14:10] <lifeless> :) hi
[14:10] <ddaa> yup, actually, just after asking I started remembering, and used grep powers to find out the relevant methods.
[14:11] <ddaa> I patched the write-group thing, but now I have an error where the branch head revision cannot be found in the repo.
[14:12]  * ddaa is using launchpad's trunk, is going to check whether jelmer has an active personal branch.
[14:12] <lifeless> catch you later
[14:12] <lifeless> <afk
[16:05] <LeoNerd> How do I stop this fscking annoying popup window that says there's a new revision, every time I commit to a branch? It seems to have started recently, since a debian update...
[16:07] <Kinnison> presumably you now have the bzr-gtk notification doobry running
[16:07] <Kinnison> look for "bzr-notify" in your process list
[16:10] <LeoNerd> Ahyes. There it is. Just kill it? Or will something start it up again?
[16:10]  * ddaa is kinda puzzled at how mercurial requires one to edit the ~/.hgrc in a trivial way to enable bundled extensions.
[16:10] <Kinnison> I imagine it'll start on desktop start
[16:10] <Kinnison> see /etc/xdg/autostart
[16:11] <Kinnison> there'll be bzr-notify.desktop in there
[16:11] <Kinnison> not sure how you disable it short of rm -f the file
[16:11] <LeoNerd> Ahyes
[16:11]  * Kinnison just got used to it
[16:11] <Kinnison> :-)
[16:11] <LeoNerd> $ sudo mv bzr-notify.desktop bzr-notify.desktop.NOYOUFSCKINGDONT
[16:12] <LeoNerd> Hrm.. shame I can't even  chmod -x  it
[16:12] <awilkins> I saw an article that put forward the idea that .desktop files were the equivalent of Outlook worms for GNOME
[16:13] <LeoNerd> It is annoying that there doesn't seem to be a local policy override thing
[16:14] <Kinnison> No idea if removing it from the session applet would do the trick
[16:14] <Kinnison> sorry
[16:16] <Kamping_Kaiser> why dont you just remove the package?
[16:16] <Kinnison> bzrk is too useful I imagine
[16:16] <Kinnison> Unfortunately bzr-notify is part of bzr-gtk
[16:17] <ddaa> awilkins: it's not nearly as bad it sounds. The problem basically is that the rest of the system assumes that not setting the execute permission on a file will prevent it from being executed accidentally, but .desktop files can be executed by nautilus regardless of the execute permission.
[16:17] <Kamping_Kaiser> ah
[16:17] <james_w> LeoNerd: cp /etc/xdg/autostart/bzr-notify.desktop ~/.local/share/applications/
[16:18] <james_w> then edit ~/.local/share/applications/bzr-notify.desktop to have "NoDisplay=True"
[16:18] <LeoNerd> Ya.. None of my files have +x on
[16:18] <james_w> "NoDisplay=true" perhaps
[16:18] <LeoNerd> james_w: Ahh.. Hrm.. Can I just set that value in /etc ?
[16:18] <LeoNerd> (go go magic negative-options)
[16:19] <james_w> yep
[16:21] <moquist> Is it possible for me to edit my bzr log messages after commit?
[16:21] <Kinnison> No[*]
[16:21] <moquist> james_w: hey! I was just dusting my bzr bd skillz off the other day and thought of you.
[16:21] <Kinnison> [*: Yes, but not really, erm, urp]
[16:22] <moquist> Kinnison: possible but highly discouraged?
[16:22] <ddaa> moquist: [*] you can get a similar effect using uncommit, and rebase if you want to change a commit message that is before other commits you do not want to change.
[16:22] <igc> night all - see you next week after I return from leave
[16:23] <ddaa> Of course, that will confuse merge/pull, etc for every branch out there that contains revisions that were changed/rebased.
[16:23] <moquist> ddaa: Hmm. I have lots of messages that say (e.g.) "yeep" b/c I was just making tiny changes in my own repo...but now I want to publish this, and I figure the rest of the world won't find "yeep" very helpful.
[16:23] <ddaa> moquist: was that understandable, our do you need spelled it out more?
[16:23] <moquist> ddaa: maybe. I'll look into it first.
[16:24] <moquist> I might just inflict yeeps on the world.
[16:24] <ddaa> Here's how I would go about it:
[16:24] <ddaa> 1. inflict "yeep" on the world
[16:25] <moquist> ddaa: heh. Sounds good to me. :-D
[16:25] <ddaa> 2. failing that, for every revision do something like "merge -r2..3 ../orig; commit -m 'nice message'"
[16:25] <james_w> hey moquist
[16:25] <ddaa> when specifying a range to merge, you actually do (essentially) a diff+patch, without referring to the merged revisions in the parents.
[16:26] <ddaa> But it's going to be quite tedious if you have more than a half-dozen revisions.
[16:26] <moquist> ddaa: yeah. not too many more, but maybe 10-15 messages to change.
[16:28]  * Kinnison recommends option 1
[16:28] <Kinnison> with addendum: "Learn not to yeep in future"
[16:28]  * ddaa ruffles Kinnison.
[16:28] <moquist> yeah...that's the real moral of the story.
[16:28] <moquist> thx!
[16:31] <Kinnison> There's some *really* crap commit messages in the world from me
[16:31] <moquist> Kinnison: I pledge never to hold them against you.
[16:31] <Kinnison> So kind :-)
[16:38] <Keybuk> jelmer: so I installed bzr-git
[16:38] <Keybuk> and it doesn't show up in bzr plugins
[16:38] <Keybuk> and thumper said to ask you ;)
[16:39] <jelmer> Keybuk: Did you install the package or from the bzr branch?
[16:39] <jelmer> Keybuk: No warnings from bzr about it not being able to load the plugin ?
[16:40] <Keybuk> jelmer: the bzr branch
[16:40] <Keybuk> there is no package
[16:40] <Keybuk> wing-commander scott% apt-cache search bzr-git
[16:40] <Keybuk> wing-commander scott%
[16:41] <jelmer> Keybuk: It's not in Ubuntu (yet), just experimental for now
[16:41] <jelmer> The bzr branch is probably the best source for it for now anyway, given the rate of changes
[16:42] <jelmer> Keybuk: So you have it in ~/.bazaar/plugins/git, are there any warnings about it not being able to load in ~/.bzr.log?
[16:42] <Keybuk> it went into /usr/local/lib somewhere
[16:42] <Keybuk> it doesn't work anyway - managed to get bzr to see it and it complained it needed 1.15
[16:44] <jelmer> ah, yes, it unfortunately does at the moment; remote git servers are a bit limited in what they support
[16:45] <jelmer> so I had to patch bzr, and that change won't land until 1.15
[16:47] <Keybuk> ok
[16:47] <Keybuk> oh well
[16:47]  * Kinnison wows
[16:47] <Kinnison> bzr managed to use my link fully just now
[16:47]  * Kinnison gives it the 1MB/s prize
[16:48] <jelmer> Kinnison: :-)
[16:49] <Kinnison> hah, now it's lying, claiming 1.4MB/s which is faster than my link goes, while actually doing bugger all network traffic
[16:50]  * Kinnison takes the prize back and gives bzr a wooden spoon
[16:57]  * Kinnison pouts -- python-dulwich is too old in intrepid
[17:06] <jelmer> Kinnison: Yeah, development has been going pretty quickly (un)fortunately
[17:07] <jelmer> Kinnison: I suspect it'll have slowed down enough for Koala
[17:08] <awilkins> Kinnison: Is is possible your 2MBit/s connection has just been upgraded to 10Mbit/s - your ISP is doing that. I only noticed when things went _pchow_.
[17:08] <awilkins> 1.4 MB/s would fit 10Mbit/s
[17:09]  * awilkins could also be mad
[17:11] <Kinnison> awilkins: Erm, the only thing I'm waiting for is my 10Mbit/s service to be upgraded to 20Mbit/s
[17:11]  * Kinnison is on business-grade cable
[17:28]  * SamB_irssi attempts to push to SVN using bzr-svn ...
[17:37] <SamB_irssi> jelmer: how do I specify what user to use for a specific SVN server ?
[18:39] <joaopinto> hello, I am getting the "http does not support mkdir" that is usually related to the missing launchpad-login
[18:41] <joaopinto> I need to commit some changes, and it's always trying to use the http method, how to I change it to bzr+ssh ?
[18:45] <cody-somerville> joaopinto, does it say that when you commit?
[18:45] <cody-somerville> joaopinto, ie. do you have a binded branch/checkout?
[18:45] <joaopinto> cody-somerville, yes, it shows the http branch
[18:46] <cody-somerville> joaopinto, just do bzr bind <bzr+ssh url>
[18:46] <joaopinto> ah
[18:48] <joaopinto> the bind operation does not report an error, but does not help either
[18:48] <joaopinto> Cannot lock LockDir(http://bazaar.launchpad.net/%7Egetdeb-web-developers/getdeb-web/main/.bzr/branch/lock)
[18:49] <SamB_irssi> jelmer: having to use "svn propdel" to get a username into the SVN auth cache isn't ideal!
[18:49] <SamB_irssi> hmm.
[18:49] <SamB_irssi> didn't even work?
[18:50] <joaopinto> cody-somerville, ops, bind did help, tks
[18:51] <cody-somerville> joaopinto, :)
[19:17] <LarstiQ> SamB_irssi: *blink*
[19:32] <stephank> I have a project I started working on in a bazaar tree. Now I'd like to reuse large parts of this application for another customer. I stripped down the application to remove functionality specific to my first customer, and now have a bazaar branch with a minimal functional version of the application. Now I'm about to branch that again so I can start work for the new customer.
[19:32] <stephank> My question is, how do I do merges across these three branches?
[19:32] <stephank> If I merge changes from the shared branch back into my original branch for customer 'A', I'd lose all the functionality because it take in the commits where I stripped everything down.
[19:33] <stephank> Basically, I want to move to a /\ shape, but at the moment only have the bottom left node of that graph.
[19:33]  * LarstiQ nods
[19:34] <LarstiQ> stephank: I haven't tested it out to that level, but what you should be able to do is merge your stripped branch into A, and then reject all the changes.
[19:35] <LarstiQ> stephank: basically by doing `bzr merge stripped; bzr revert; bzr ci -m 'Reject strippage'`
[19:35] <LarstiQ> stephank: afaics that should from then on allow you to merge changes without having to deal with the huge diff of removed functionality each time.
[19:36] <LarstiQ> stephank: I do something similar like this (but only two branches) for merging the Debian unstable packaging of bzr-svn into the Ubuntu bzr-svn ppa packages
[19:36] <stephank> LarstiQ: Aha! I'll try that out immediatly. :)
[19:37] <LarstiQ> (for which I don't want the Debian changelog entries that mess up the chronological order in the Ubuntu changelog)
[19:37] <LarstiQ> besides some real packaging differences
[19:39] <stephank> LarstiQ: hmm.. when I revert, it really reverts the merge as well, and the commit is not picking up any changes.
[19:40] <ddaa> stephank: you MUST do "revert ."
[19:40] <ddaa> the final dot is important
[19:40] <ddaa> or "revert $PATH" if you prefer
[19:40] <stephank> ddaa: Aha, ofcourse
[19:41] <LarstiQ> stephank: sorry, what ddaa said
[19:41] <LarstiQ> ddaa: I actually left the . off in my advice, mea culpa.
[19:42] <stephank> LarstiQ: no problem, thanks for the excellent help, and ddaa, this did the trick. :)
[20:26] <fbond> What's the word on merging ancestry with cherry-picks?
[20:33] <jelmer> SamB_irssi: hi
[20:34] <jelmer> SamB_irssi: still there?
[21:33] <SamB_irssi> jelmer: again
[21:33] <SamB_irssi> I am here again
[21:33] <SamB_irssi> jelmer: it's an https URL on sf.net, if that makes any difference
[21:35] <jelmer> SamB_irssi: hi
[21:35] <jelmer> SamB_irssi: Did you see the thread on the bazaar mailing list?
[21:36] <jelmer> SamB_irssi: basically, you need to use svn+https://
[21:37] <SamB_irssi> jelmer: on a completely different subject, are you going to vote for http://bundlebuggy.aaronbentley.com/project/bzr/request/%3CE1LupWj-0005Cp-WD%40hydrogen%3E ?
[21:37] <SamB_irssi> jelmer: I tried svn+https://
[21:37] <SamB_irssi> it didn't seem to help me get a "username" prompt
[21:37] <SamB_irssi> hmm.
[21:37] <SamB_irssi> maybe my bzr.dev is too old?
[21:38] <jelmer> SamB_irssi: which version of bzr are you running?
[21:38] <jelmer> SamB_irssi: you'd need a fairly recent one
[21:38] <jelmer> SamB_irssi: or bzr.foreign
[21:39] <SamB_irssi> fwiw, svn+https:// failed in the same exact way, not in a different way -- it asked me for the password for "naesten"
[21:39]  * SamB_irssi wonders if there is a way to make irssi warn you that you are scrolled up
[21:40] <LarstiQ> SamB_irssi: if there is more text after you scrolled up it says - more -
[21:41] <SamB_irssi> LarstiQ: where does that show up?
[21:41]  * SamB_irssi waits for someone to say something so he can see where it shows up
[21:41] <SamB_irssi> oh, there it is
[21:42] <SamB_irssi> LarstiQ: is there some way to change that to a different color?
[21:43] <LarstiQ> SamB_irssi: euh, I suppose
[21:43] <SamB_irssi> jelmer: ah, with latest bzr.dev it works better
[21:43] <LarstiQ> SamB_irssi: may I recommend the trackbar script to you?
[21:43] <SamB_irssi> now it just looks horrible ;-)
[21:43] <LarstiQ> SamB_irssi: it's white for me
[21:43] <SamB_irssi> LarstiQ: yeah, it was white here too
[21:44] <LarstiQ> SamB_irssi: I think I'm using whatever is default in Debian qua style
[21:44] <SamB_irssi> (the "ugly" refers to bzr-svn's username prompt, btw)
[21:45] <LarstiQ> ah :)
[21:46] <SamB_irssi> jelmer: uh-oh ... it's asking me first for a username, then for a password ... but now it's asking me for a password for naesten again!
[21:47] <LarstiQ> what a naesty behaviour!
[21:47] <LarstiQ> ok, time for bed if my jokes are that bad
[21:47] <LarstiQ> ciao
[21:47] <SamB_irssi> that is, first it asks for a username and I say "sbronson" ... then it asks for a password for sbronson ... then it asks for a password for naesten!
[21:48]  * SamB_irssi puts back the svn+
[21:50] <SamB_irssi> arg, apparantly it found "naesten" cached???
[21:51] <jelmer> SamB_irssi: can you reproduce this with the latest bzr.foreign and the latest bzr-svn?
[21:52] <SamB_irssi> what's bzr.foreign ???
[21:53] <jelmer> SamB_irssi: http://people.samba.org/bzr/jelmer/bzr/foreign
[21:53] <SamB_irssi> that looks kind of like a dash to me ...
[21:53] <SamB_irssi> oh, wait
[21:53] <jelmer> contains a few pending patches for bzr.dev and a workaround for the fact that bzr.dev asks for passwords more often than necessary
[21:53] <SamB_irssi> different url
[21:53]  * SamB_irssi was looking at something from google with a desciptively similar sounding url
[21:54] <SamB_irssi> s/descip/descep
[21:56] <yacoob> is there any way to stop bzr from merging a file that has been deleted in destination branch?
[21:59] <james_w> yacoob: no, but if you revert that path after merging then it will be remembered
[22:00] <SamB_irssi> jelmer: okay, yes, I still have the problem
[22:01] <SamB_irssi> but it might now just be a configuration/cache issue of some kind
[22:01] <jelmer> SamB_irssi: so this is happening while you are pulling?
[22:01] <SamB_irssi> jelmer: I don't believe so
[22:01] <jelmer> SamB_irssi: so it's only while pushing?
[22:01] <jelmer> SamB_irssi: and Bazaar is asking you for a username+password more than once?
[22:02] <SamB_irssi> no credentials show up in ~/.bzr.log for pull
[22:02] <SamB_irssi> oh, actually I don't get any prompts now ...
[22:02] <SamB_irssi> sorry :-)
[22:02] <SamB_irssi> or ... one password prompt
[22:03] <SamB_irssi> for the wrong username, though
[22:04] <SamB_irssi> and I can't figure out where it's getting the username/password from :-(
[22:05] <jelmer> SamB_irssi: It should be getting it from ~/.subversion/auth if you tried to use svn itself on that URL before
[22:10] <SamB_irssi> This is my bzr.log output:
[22:10] <SamB_irssi> http://paste.lisp.org/display/78916
[22:11] <SamB_irssi> but I don't see anything in ~/.subversion/auth ...
[22:15] <jelmer> ah, bzr-svn wasn't prompting yet
[22:15] <jelmer> SamB_irssi: I'm pushing a fix for bzr-svn
[22:16] <SamB_irssi> jelmer: but I'm still puzzled as to where it came up with the "password"
[22:17] <SamB_irssi> jelmer: but I'm still puzzled as to where it came up with the "password"
[22:17] <SamB_irssi> EWIN
[22:17]  * SamB_irssi meant to re-do a bzr pull ...
[22:18]  * SamB_irssi wonders when/where jelmer is pushing it
[22:23] <asabil> hi all
[22:23] <asabil> is there a way to stop the Commit().commit() from using the progress bar ?
[22:24] <james_w> asabil: programatically?
[22:24] <asabil> james_w: yes
[22:24] <james_w> I think you pass in a progress bar
[22:24] <james_w> Dummy or Null or something
[22:26] <asabil> james_w: not for commit ()
[22:26] <james_w> ah
[22:27] <james_w> that sounds like an omission
[22:27] <jelmer> SamB_irssi: Just pushed it, to the 0.6 branch
[22:31] <SamB_irssi> jelmer: I still seem to have the same problem :-(
[22:31] <jelmer> SamB_irssi: It's not prompting you for a username?
[22:31] <SamB_irssi> indeed
[22:32] <SamB_irssi> but I also seem to need to pass --username to svn every time ...
[22:32] <jelmer> SamB_irssi: so it looks like the username is cached in ~/.subversion/auth then
[22:33] <SamB_irssi> I can't see it !
[22:34] <jelmer> SamB_irssi: have you grepped for it?
[22:34] <jelmer> it should be in one of the files in ~/.subversion/auth/svn.username/
[22:34] <asabil> jelmer: can you take a look at this branch: https://code.launchpad.net/~asabil/bzr-rebase/filter-branch ?
[22:35] <SamB_irssi> jelmer: I don't seem to *have* any files there
[22:36] <jelmer> SamB_irssi: I'm not sure where it gets it from then, but if svn is assuming it knows the username then bzr-svn probably would too
[22:36] <jelmer> asabil: sure, what about it?
[22:37] <asabil> jelmer: what do you think about merging it into the rebase plugin ?
[22:37] <asabil> and maybe rename bzr-rebase to bzr-rewrite ?
[22:37] <asabil> with all the history manipulation related commands
[22:38] <yacoob> james_w, doesn't quite work, still get conflicts on next merge.
[22:38] <james_w> yacoob: you did a "revert; commit; merge"?
[22:38] <james_w> and you get the same deleted conflict?
[22:40] <SamB_irssi> jelmer: hmm.
[22:40] <SamB_irssi> jelmer: would be nice if bzr-svn had a way to override that :-(
[22:40] <yacoob> merge from branch a to branch b, revert addition of a file x, commit. Then made a change in file x in branch a. Merge from a to be gives a conflict.
[22:44]  * SamB_irssi tries updating to a more recent subversion package
[22:45] <jelmer> asabil: can you send me a merge request?
[22:45] <asabil> jelmer: to your personal mail box ?
[22:45] <jelmer> asabil: I'm at a conference at the moment, don't have a lot of time to look into it atm
[22:45] <jelmer> asabil: yeah
[22:46] <asabil> jelmer: I can also ask for a merge from launchpad
[22:46] <jelmer> SamB_irssi: You can override it by specifying the username in the url
[22:46] <SamB_irssi> hmm ... it looks like if I hit "enter" at the password prompt for "naesten", vanilla svn asks me for another username
[22:46] <jelmer> asabil: Launchpad's merges don't include merge directives though unfortunately
[22:46] <SamB_irssi> jelmer: that didn't seem to work
[22:46] <asabil> jelmer:  okidoki, I will do then, thanks
[22:46] <SamB_irssi> I think ..
[22:47] <SamB_irssi> subversion doesn't seem to care if I put something before @ in the http url ?
[22:47] <SamB_irssi> er. https ...
[22:49] <yacoob> bug or feature?
[22:52] <jelmer> SamB_irssi: bzr-svn does
[22:52] <jelmer> yacoob: that's intentional
[22:52] <jelmer> yacoob: as bzr doesn't know what to do with changes to a file that's removed
[22:53] <jelmer> yacoob: it doesn't want to throw away those changes that have been made silently
[22:53] <yacoob> so I'd have to deal with this on every subsequent merge...
[22:55] <Peng_> Only if the file was modified.
[22:55] <yacoob> well, yes.
[22:55] <yacoob> no way to work around it, I presume?
[23:05]  * SamB_irssi heads home ... hasn't failed yet with the username@ in the URL, but he's still not happy about having to use that :-(
[23:06]  * SamB_irssi ... and it still might
[23:07] <lifeless> yacoob: you only have to deal with it once for each change; if upstream stop changing it it will stop conflicting
[23:08] <lifeless> yacoob: its arguably a bug to have subsequent changes generate conflicts again; could go either way - may be worth some discussion on the list
[23:09] <yacoob> lifeless, I'm the upstream :) and I keep config files in bzr. Branch a is 'desktop', b - 'laptop'. Some of the stuff is not needed on the laptop, so it would be nice to say once 'no, I don't need this on the laptop'.
[23:16] <lifeless> yacoob: righto; still the analogy holds
[23:16] <lifeless> you'd like the delete to stay deleted
[23:17] <lifeless> even on later changes to the file
[23:17] <yacoob>  very much so. I'll open a bug about that. --flag for this would be okay I think.
[23:24] <yacoob> https://bugs.launchpad.net/bzr/+bug/364336
[23:25] <yacoob> ah :>