 I will also keep my eyes open @kc2bez @guiverc while QA-testing - (re @lubuntu_bot: (irc) <kc2bez> Of course. Please let me know if anything strange pops up in testing guiverc)
 Thank you! (re @Leokolb: I will also keep my eyes open @kc2bez @guiverc while QA-testing -)
 NP - what about Thunderbird? (re @kc2bez: Thank you!)
 I think the last place we landed was to not include a mail client.
 Ah..yes - memory here slipping a wee bit ..
 any decision on fcitx?
 I dropped it from the seed along with k3b and trojita. (re @lynorian: any decision on fcitx?)
[04:40] <guiverc> after install; it wants to remove k3b  (expected from ^)
[04:41] <kc2bez> Hmm, I would have thought it would have left it unless you did a auto remove
[04:42] <guiverc> my full-upgrade is followed by autoremove + autoclean..
[04:42] <kc2bez> Oh, OK.
[04:43] <guiverc> k3b likely included other related packages (i don't know them but they look related)... trojita was NOT removed as I think teward said/expected
[04:44] <kc2bez> I think we are OK there.
[04:49] <guiverc> other packages were k3b related OR other software I have installed  (`kde-cli-tools` I assume was me)... no fcitx, no trojita was tocuhed.
[04:50]  * guiverc clarifies; 'me' as in my bloated package install related
 some not so good news..upgraded Lubuntu Impish to Jammy and all 3 pkgs (k3b,fcitx,and trojita) all gone
 I think we can write a release note about that. (re @Leokolb: some not so good @kc2bez @guiverc news..upgraded Lubuntu Impish to Jammy and all 3 pkgs (k3b,fcitx,and trojita) all gone)
 Yes agree - it should suffice - one must always read the release notes before an upgrade.. (re @kc2bez: I think we can write a release note about that.)
 And @kc2bez we of course include some good comments about backing up the data as usual
 Exactly.
 1st initial QA tests after deletions(trojita,ke3b,fcitx)look good @kc2bez so far..
 Good news.
 Ray of light at tunnels end!
 @Leokolb Thank you for testing that...  (release-upgrade)❤


[01:08] <EzraR-m> persia: are you around?
[02:12] <evilshadeslayer> tumbleweed: poke
[02:12] <evilshadeslayer> tumbleweed: bug 603831
[09:34] <joaopinto> is REVU actively used lately ?
[11:04] <AnAnt> Hello, I need help with an apport script, I want to get the value of a config variable, so I did this:
[11:04] <AnAnt>     SLModemdDevice = command_output(['sh', '-c', '[ ! -r /etc/default/sl-modem-daemon ] || (. /etc/default/sl-modem-daemon ; echo $SLMODEMD_DEVICE)'])
[11:04] <AnAnt> is that correct ?
[11:06] <AnAnt> also, is there a way to test some apport functions directly in a python shell ? I tried , import apport ; command_output('ls') ; but that gave the following error:
[11:06] <AnAnt> NameError: name 'command_output' is not defined
[11:06] <geser> when you use "import apport" then you need "apport.command_output('ls')"
[11:07] <geser> or use "from apport import *" then "command_output('ls')" works
[11:11] <tumbleweed> (although command_output is in apport.hookutils not apport)
[11:37] <AnAnt> ah, ok
[11:42] <AnAnt> thanks
[13:40] <ari-tczew> tumbleweed: ping
[13:41] <tumbleweed> ari-tczew: hi, is LP: #414247 good to go?
[13:42] <ari-tczew> tumbleweed: do you mean bug 414247 ?
[13:42] <tumbleweed> ari-tczew: yes
[13:42] <ari-tczew> tumbleweed: I'm not sure to coolbhavi package. Some things are not included.
[13:51] <ari-tczew> tumbleweed: could you look at bug 602450 ?
[13:52] <tumbleweed> ari-tczew: my question on that is should I look at it or unsubscribe sponsors?
[13:53] <ari-tczew> tumbleweed: hmm, not yet. I'd like to see a feedback from sponsor, who is expierenced with python packages.
[13:54] <tumbleweed> in that case I'll look. If there's anything I know about, it's python
[13:55] <tumbleweed> xattr sync looks good
[14:07] <joaopinto> anyone with experience with ruby apps packaging ?
[14:08] <joaopinto> this app Makefile is using /usr/local/lib/site_ruby for a ruby module (or whatever it's called), I have no idea on the expected place for ruby
[14:21] <ari-tczew> joaopinto: look for motu ruby on launchpad
[14:21] <joaopinto> ok, tks
[14:22] <evilshadeslayer> ari-tczew: btw you took on kadu right
[14:22] <evilshadeslayer> ari-tczew: it doesnt need a merge :P
[14:26] <ari-tczew> evilshadeslayer: I didn't look at kadu yet.
[14:26] <evilshadeslayer> ari-tczew: doesnt need merging.. not from what i interpreted
[14:28] <ari-tczew> evilshadeslayer: why?
[14:28] <evilshadeslayer> ari-tczew: well,we the ubuntu package has a added dep,and debian doesnt ship with that dep
[14:29] <ari-tczew> evilshadeslayer: so ubuntu should ship that dep.
[14:29] <ari-tczew> so it;s needs merging
[14:29] <ari-tczew> it;s due to new kde IIRC - that said debfx
[14:30] <Laney> you should rather understand why and whether we need to keep it
[14:30] <evilshadeslayer> ari-tczew: uh wait,youve got it the wrong way :P
[14:30] <evilshadeslayer> ari-tczew: we *do* ship that dep
[14:30] <evilshadeslayer> ari-tczew: debian *doesnt*
[14:30] <evilshadeslayer> build dep
[14:31] <ari-tczew> evilshadeslayer: so why you want to drop it?
[14:31] <evilshadeslayer> i dont want to drop it...
[14:31] <evilshadeslayer> thats why it doesnt need a merge
[14:35] <ari-tczew> evilshadeslayer: I don't understand you.
[14:35] <evilshadeslayer> i dont understand my self sometimes:P
[14:35] <ari-tczew> QtWebKit is no longer part of libqt4-dev so all packages using it need to build-depend on libqt4-webkit-dev.
[14:36] <evilshadeslayer> ari-tczew: do you mind if i took a look at kadu?
[14:37] <ari-tczew> evilshadeslayer: I think that we should ship that B-D.
[14:37] <evilshadeslayer> ari-tczew: ok lemme look a it,and ill get back :)
[14:46] <Laney> would be nice if that changelog had more detail
[14:55] <ScottK> What ari-tczew said about QtWebKit is exactly correct.  We're using a newer version of Qt than Debian, so we need to add this, whereas they don't.
[17:36] <ari-tczew> kadu ftbfs: error: 'fchmod' was not declared in this scope :(
[17:43] <coolbhavi> ari-tczew, include #include <sys/stat.h> in the ftb file
[17:44] <ari-tczew> coolbhavi: already exist
[17:44] <coolbhavi> or check if the header if already included is properly linking on to the compiler
[17:45] <ari-tczew> coolbhavi: how can I check it?
[17:53] <coolbhavi> ari-tczew, maybe something like this: gcc -include /path/to/directory/containing/header_name/header_name.h -o myoutputfile myoutputfile.c and you can compile and check again
[17:54] <ari-tczew> coolbhavi: you are doing a lot work for Ubuntu. I encourage you to present here more frequently. In team we can do more and more.
[17:54] <coolbhavi> ari-tczew, sure!
[17:55] <evilshadeslayer> :P
[17:55] <evilshadeslayer> ari-tczew: yeah i got involved with rbot.. seems debian released a new package
[17:56] <ari-tczew> evilshadeslayer: what is rbot?
[17:56] <evilshadeslayer> ari-tczew: one sec
[17:56] <evilshadeslayer> !info rbot
[17:56] <ari-tczew> aha
[17:56] <evilshadeslayer> ^^ for eg
[17:56] <evilshadeslayer> evilbot: hi
[17:56] <evilbot> howdy, evilshadeslayer!
[17:57] <ari-tczew> o_O
[17:57] <evilshadeslayer> ari-tczew: hmm?
[17:58] <ari-tczew> evilshadeslayer: nothing ;p don't care
[17:58] <evilshadeslayer> :P
[17:59] <evilshadeslayer> the current version doesnt work in ubuntu
[17:59] <evilshadeslayer> was fixed in latest release
[17:59] <coolbhavi> evilshadeslayer, rbot ftb'd on my PPA due to missing rake and some modules
[17:59] <evilshadeslayer> coolbhavi: yeah im fixing those :P
[18:00] <coolbhavi> :P
[18:00] <evilshadeslayer> idk how but it doesnt ftbfs in debian
[18:00] <coolbhavi> evilshadeslayer, build environments are different
[18:00] <evilshadeslayer> yeah
[18:01] <evilshadeslayer> probably build deps get pulled in properly there
[18:01] <coolbhavi> hmm
[18:16] <evilshadeslayer> coolbhavi: rbot fixed :)
[18:16] <evilshadeslayer> just going through patches
[18:17] <coolbhavi> evilshadeslayer, It required module tweaking and b-d on rake I guess :)
[18:17] <evilshadeslayer> coolbhavi: had to add a few more build deps
[18:17] <evilshadeslayer> coolbhavi: rake, rubygems, libgettext-ruby1.8
[18:18] <coolbhavi> evilshadeslayer, thats what i meant i think :)
[18:18] <evilshadeslayer> yeah .. was just telling you which ones i added ;)
[18:19] <coolbhavi> rock on :)
[18:21] <evilshadeslayer> yeah.. will have to drop patches
[18:21] <coolbhavi> :)
[18:28] <ari-tczew> coolbhavi: am I correct with following command? gcc -include /usr/include/sys/stat.h -o main main.cpp
[18:28] <coolbhavi> ari-tczew, try out on trial and error mate you ll stick!
[18:30] <ari-tczew> coolbhavi: only errors in output ...
[18:30] <coolbhavi> ari-tczew, try linking with ftb file
[18:30] <coolbhavi> and see
[18:31] <coolbhavi> if the header is included on recompilation
[18:36] <ari-tczew> I don't understand. No idea how to fix it.
[19:04] <ari-tczew> if package doesn't have a patchsystem and I'm preparing a merge, can I patch files directly?
[19:04] <tumbleweed> yes
[19:06] <evilshadeslayer> the patch will appear in diff.gz..
[19:29] <ari-tczew> tumbleweed: I thought that if you'll join MOTU, then you'll doing less, but I see that you're active. I'm glad. thanks!
[19:29] <Roran> hmm
[19:29] <Roran> anyone up for a merge?
[19:29] <Roran> https://edge.launchpad.net/~rohangarg/+archive/experimental/+packages << merge from there.. after it builds
[19:31] <tumbleweed> ari-tczew: yeah I thought I'd do less too. Dunno what happened :P
[19:32]  * evilshadeslayer looks at tumbleweed
[19:33] <ari-tczew> tumbleweed: what do you think about upgrade libsmbios?
[19:34] <tumbleweed> ari-tczew: yes, it's borken and needs to be fixed. I saw the merge bug, looks like it needs work
[19:34] <tumbleweed> I have an SRU patch for when we have maverick sorted out
[19:35] <evilshadeslayer> ok rbot built and needs love
[19:38] <tumbleweed> evilshadeslayer: you don't like the review queue? :)
[19:38] <evilshadeslayer> tumbleweed: i can upload to revu for merges too? :)
[19:38] <evilshadeslayer> sweet :D
[19:38] <tumbleweed> evilshadeslayer:
[19:38] <tumbleweed> no, I meant ubuntu-sponsors
[19:38] <evilshadeslayer> oh
[19:38] <ari-tczew> evilshadeslayer: revu is for new packages
[19:38] <evilshadeslayer> ari-tczew: yeah
[19:39] <ari-tczew> tag: needs-packaging
[19:39] <evilshadeslayer> ari-tczew: thats why i was surprised :P
[19:39] <evilshadeslayer> tumbleweed: uh.. well.. sure.. ill file a bug
[19:39] <ari-tczew> evilshadeslayer: can't you use a 1 nickname?
[19:40] <evilshadeslayer> ari-tczew: ah.. i was registering a nick for the bot :P
[19:40] <kees> ScottK: around?  I'd like to try to figure out why we're seeing different results with drkonqi.  :P
[19:40] <evilshadeslayer> but all of them were taken :P
[19:40] <BlackZ> evilshadeslayer: if you have not the upload rights you have *always* to file a merge bug
[19:40] <evilshadeslayer> BlackZ: yes.. im filing it
[19:41] <kees> ScottK: ah, nm, I installed rekonq and see what you're seeing now.  seems like it's different from kate somehow.
[19:42] <tumbleweed> hi BlackZ: haven't seen much from you on the review queue recently
[19:42] <BlackZ> tumbleweed: I'm busy with exams, however I'm working on some merges now
[19:43] <evilshadeslayer> BlackZ: can i point to the PPA instead of attaching a debdiff?
[19:43] <tumbleweed> BlackZ: good :)
[19:44] <tumbleweed> evilshadeslayer: no, please post the diffs, it makes life easier for the reviewer
[19:44] <evilshadeslayer> tumbleweed: ok..
[19:44] <ari-tczew> or use bazaar
[19:44] <tumbleweed> yeah, that too (although I still find the diff workflow faster)
[19:45] <BlackZ> evilshadeslayer: it would be better to attach a debdiff in the bug as a patch: 1. this will indicate the sponsors there's a patch; 2. the work of the sponsors will be facilitated
[19:45] <evilshadeslayer> ok
[19:47] <BlackZ> evilshadeslayer: also, according to our policy for the merges, you have to attach two debdiffs to the bug report (if you just attach the debdiff of versiondebian -> versiomerged that's not a big deal)
[19:48] <tumbleweed> yes, the ubuntu -> ubuntu diff can be massive. If it's more than a few screenfulls, nobody will read it anyway
[19:48] <evilshadeslayer> BlackZ: im attaching diff of our current ubuntu packaging and new ubuntu packaging,since this is a new upstream release
[19:50] <ari-tczew> I miss for archive admins :(
[19:50] <BlackZ> evilshadeslayer: if you're doing a version-upgrade the debdiff aren't suitable
[19:50] <evilshadeslayer> i know ;)
[19:50] <BlackZ> since they can be too big (of size)
[19:50] <ari-tczew> MoM would looks cleaner after ACKed syncs
[19:50] <evilshadeslayer> yeah i pasted a 5 MB debdiff once
[19:51] <BlackZ> you could use your PPA (if you have one) for that
[19:51] <tumbleweed> or a branch
[19:51] <tumbleweed> evilshadeslayer: is this something debian doesn't have? or something debian is lagging behind in?
[19:52] <evilshadeslayer> tumbleweed: whut?
[19:52] <tumbleweed> evilshadeslayer: why are we getting a new version, not syncing from debian?
[19:52] <evilshadeslayer> tumbleweed: were merging from debian since a sync would not work,we need extra deps to make the package not FTBFS
[19:53] <tumbleweed> evilshadeslayer: in that case, you post a diff between the current debian version and your fixes
[19:53] <tumbleweed> that diff should be small
[19:53] <BlackZ> evilshadeslayer: so it's not a version upgrade
[19:53] <BlackZ> evilshadeslayer: if that fixes a bug, it's a bug fix ;)
[19:54] <evilshadeslayer> tumbleweed: ok.. that would mean just the changelog,control and rules files
[19:54] <evilshadeslayer> BlackZ: well
[19:54] <evilshadeslayer> BlackZ: idk if it fixes any bugs :P
[19:54] <evilshadeslayer> but it will make rbot work :P
[19:55] <tumbleweed> let my pot on my bot developer hat and say "use ibid" :)
[19:55] <evilshadeslayer> ibid ?? :P
[19:55] <tumbleweed> launchpad.net/ibid (it's in the repos)
[19:56] <evilshadeslayer> tumbleweed: i like my ruby bot :P
[19:56] <BlackZ> evilshadeslayer: if it's a bug, report a bug and attach your debdiff
[19:57] <BlackZ> then subscribe ubuntu-sponsors and wait
[19:57] <evilshadeslayer> kewl
[19:57]  * evilshadeslayer has to upload kdegames after this
[20:00] <evilshadeslayer> BlackZ: tumbleweed so i just post the changes i did to debian packaging right?
[20:01] <evilshadeslayer> in the bug report
[20:01] <tumbleweed> evilshadeslayer: as a debdiff
[20:01] <evilshadeslayer> ok
[20:04] <BlackZ> evilshadeslayer: if that's the first modify in ubuntu for the package, yes
[20:04] <BlackZ> otherwise you have to modify the *currently* ubuntu package for include your modify
[20:05] <evilshadeslayer> BlackZ: that will make the debdiff huge
[20:05] <BlackZ> evilshadeslayer: why? if that will happen, just do a clean to the debdiff
[20:06] <evilshadeslayer> BlackZ: because debian has a new version and packaging has changed alot
[20:06] <BlackZ> evilshadeslayer: I don't understand: are you doing a merge?
[20:07] <evilshadeslayer> yes
[20:07] <BlackZ> evilshadeslayer: ah, then yes: just do as you said (remember to flag it as a patch)
[20:07] <evilshadeslayer> ok
[20:08] <BlackZ> evilshadeslayer: obviously it must be a debdiff
[20:09] <evilshadeslayer> yeah ok :)
[20:18] <evilshadeslayer> BlackZ: http://pastebin.com/jLWK7aRN << i get that in the debdiff,but i didnt modify that
[20:18] <evilshadeslayer> i think  its the doing of debuild -S -sa
[20:19] <evilshadeslayer> due to that it makes a file debian-changes-0.9.15+post20100705+gitb3aa806-1ubuntu1 in debian/patches  http://pastebin.com/VwyDt1zU
[20:19] <BlackZ> evilshadeslayer: does the package use quilt 3.0 ?
[20:19] <evilshadeslayer> yes
[20:20] <BlackZ> evilshadeslayer: so is there a patch in debian/patches auto-generated during the build?
[20:20] <evilshadeslayer> yes
[20:21] <evilshadeslayer> http://pastebin.com/VwyDt1zU << thats the one
[20:23] <BlackZ> evilshadeslayer: you should check what's happened there; maybe the problem is a patch
[20:23] <tumbleweed> most likely it's an issue with clean not cleaning up enough
[20:24] <BlackZ> evilshadeslayer: ever if you didn't modified nothing outside the debian directory
[20:24] <BlackZ> tumbleweed: yeah
[20:24] <evilshadeslayer> hmm
[20:24] <evilshadeslayer> BlackZ: since i was not sure,i pulled clean debian sources again and modified the stuff again
[20:25] <evilshadeslayer> but it still created the patch
[20:29] <evilshadeslayer> uh wait
[20:29] <evilshadeslayer> doh... debian ships that patch
[20:30] <tumbleweed> evilshadeslayer: it's still a bug
[20:30] <evilshadeslayer> so how do we fix it?
[20:30]  * tumbleweed has a look
[20:30] <evilshadeslayer> maybe debian did want to modify that file?
[20:32] <ari-tczew> can I run 2 builds both on pbuilder?
[20:32] <evilshadeslayer> ari-tczew: afaik no
[20:33] <evilshadeslayer> ari-tczew: if you have two different base tarballs then yes
[20:33] <tumbleweed> evilshadeslayer: they used to have a line in their clean rule to remove that file, but it's gone
[20:33] <ari-tczew> I want to build two differents packages, so differents tarballs and .dsc
[20:33] <evilshadeslayer> tumbleweed: 		mv debian/rbot/usr/share/rbot/plugins/$${PL}.rb debian/rbot/usr/share/rbot/plugins/$${PL}.rb.disabled; \
[20:34] <evilshadeslayer> ari-tczew: base tarball of pbuilder :P
[20:34] <evilshadeslayer> uh wait
[20:34] <tumbleweed> evilshadeslayer: no, rm -f lib/rbot/pkgconfig.rb
[20:34] <evilshadeslayer> tumbleweed: where does it clean that file in debian/rules?
[20:35] <evilshadeslayer> uh.. no such stuff here
[20:35] <tumbleweed> evilshadeslayer: "used to"
[20:35] <evilshadeslayer> ohh
[20:35] <evilshadeslayer> right
[20:35] <evilshadeslayer> tumbleweed: so they delibrately removed it?
[20:35] <tumbleweed> looks like it was an accident
[20:36] <tumbleweed> they forgot to B-D on rake, too (and possibly other things)
[20:42] <evilshadeslayer> yeah
[20:43] <evilshadeslayer> so i add that to clean right
[20:43] <tumbleweed> yip
[20:43] <evilshadeslayer> uh waut
[20:43] <evilshadeslayer> tumbleweed: see debian/clean
[20:44] <evilshadeslayer> whats that file?
[20:44] <tumbleweed> evilshadeslayer: oh I missed that. man dh_clean
[20:44] <evilshadeslayer> :P
[20:44] <evilshadeslayer> right
[20:44] <tumbleweed> only problem is that dh_clean gets called before this file is created
[20:44] <evilshadeslayer> then were missing dh_clean
[20:45] <tumbleweed> no, cdbs calls dh_clean for you
[20:45] <evilshadeslayer> hmm
[20:45] <evilshadeslayer> oh ok
[20:47] <evilshadeslayer> tumbleweed: so we still have to add that command manuall in clean: ?
[20:47] <evilshadeslayer> *manually
[20:50] <tumbleweed> yes, so we might as well delete debian/clean
[20:50] <evilshadeslayer> ok
[20:53] <evilshadeslayer> tumbleweed: i can remove the patch as well then right?
[20:54] <evilshadeslayer> the debian series patch that is auto generated
[20:54] <tumbleweed> evilshadeslayer: yes
[20:54] <evilshadeslayer> ok
[20:55] <evilshadeslayer> tumbleweed: http://pastebin.com/kEpkj0fp
[20:55] <evilshadeslayer> im attaching that
[20:55] <tumbleweed> I thought you were going to delete that debian-xxx patch?
[20:55] <evilshadeslayer> i did
[20:56] <tumbleweed> did you?
[20:56] <evilshadeslayer> tumbleweed: debdiff of debian package with new ubuntu package
[20:56] <evilshadeslayer> not old ubuntu package and new ubuntu package :)
[20:56] <tumbleweed> oh i see it was in the debian source too. nm
[20:57] <evilshadeslayer> :)
[20:58] <tumbleweed> evilshadeslayer: to make your reviewer's life easier, you can remove the debian-changes-0.9.15+post20100705+gitb3aa806-1 section of the debdiff
[20:58] <tumbleweed> it'll get deleted when the reviewer bulids the ubuntu source package
[20:58] <evilshadeslayer> tumbleweed: ah ok :)
[20:58] <tumbleweed> please forward that patch to debian
[20:58] <tumbleweed> (but don't send them our changelog or maintainer-changes
[20:58] <evilshadeslayer> hehe :P
[20:59] <evilshadeslayer> of course not
[20:59] <tumbleweed> err, what was I saying, it won' tget deleted
[20:59] <evilshadeslayer> first lemme upload with the correct stuff to ubuntu and will forward later
[21:00] <tumbleweed> (with source format 1, it would get deleted, but with 3, because it's a quilt patch it has to be manually deleted)
[21:10] <evilshadeslayer> tumbleweed: ok,i cant remove the debian-changes stuff from debdiff,since ill be posting this debdiff as is and ask the reviewer to apply it to current debian packaging
[21:11] <tumbleweed> evilshadeslayer: I can't understand that
[21:11] <evilshadeslayer> tumbleweed: ill ask the reviewer to download the debian package and apply this debdiff on top of it
[21:11] <evilshadeslayer> so,i cant remove the debian-changes stuff
[21:11] <tumbleweed> evilshadeslayer: that's the normal way merges are handled, yes
[21:12] <tumbleweed> no, don't remove that, I was wrong (as I said)
[21:12] <evilshadeslayer> ok :P
[21:13] <evilshadeslayer> bug 604102
[21:14] <evilshadeslayer> tumbleweed: ^^
[21:14] <tumbleweed> evilshadeslayer: did you forward th epatch to debian?
[21:14] <evilshadeslayer> tumbleweed: im going to
[21:14] <evilshadeslayer> but just in a few secs
[21:14] <tumbleweed> please link to the bug when you do
[21:14] <evilshadeslayer> tumbleweed: ok,should i mail it to them or upload it somewhere?
[21:15] <tumbleweed> evilshadeslayer: https://wiki.ubuntu.com/Debian
[21:16] <tumbleweed> evilshadeslayer: btw merge bugs are normally titled with this format: https://wiki.ubuntu.com/UbuntuDevelopment/Merging#File a merge bug
[21:17] <evilshadeslayer> oh
[21:17] <tumbleweed> and you need to subscribe ubuntu-sponsors if you want it to show up in the sponsorship queue
[21:21] <evilshadeslayer> done
[21:21] <evilshadeslayer> tumbleweed: https://bugs.edge.launchpad.net/~ubuntu-universe-sponsors ??
[21:21] <tumbleweed> evilshadeslayer: no, just ubuntu-sponsors
[21:22] <evilshadeslayer> ah ok
[21:22] <tumbleweed> universe and main sponsors were merged into one
[21:22] <evilshadeslayer> done
[21:23] <tumbleweed> great. Now we'll give debian a few days to pick up your fix, otherwise we go with your merge
[21:23] <evilshadeslayer> tumbleweed: :P
[21:30] <evilshadeslayer> tumbleweed: btw i cant find a build log on that page
[21:30] <tumbleweed> evilshadeslayer: which page?
[21:31] <evilshadeslayer> tumbleweed: http://packages.qa.debian.org/r/rbot.html
[21:31] <tumbleweed> evilshadeslayer: that's because it's an arch all package. It was built on the maintainer's PC
[21:31] <evilshadeslayer> -.-
[21:32] <evilshadeslayer> tumbleweed: he just uploaded the .deb?
[21:32] <tumbleweed> debian does binary uploads for one arch, and the buildd farm builds the rest (if necessary)
[21:32] <tumbleweed> yes
[21:32] <evilshadeslayer> ....
[21:32] <tumbleweed> yes, he really should have tested in pbuilder :)
[21:33] <evilshadeslayer> tumbleweed: i could not imagine debian could be this lazy/callous :P
[21:33] <evilshadeslayer> oh also, should i add my self to debian changelog as well?
[21:33] <evilshadeslayer> documenting the changes
[21:34] <tumbleweed> evilshadeslayer: no, don't touch the changelog
[21:34] <evilshadeslayer> uh alright
[21:39] <joaopinto> uh, Debian accepts direct .deb uploads ?
[21:49] <evilshadeslayer> tumbleweed: uh.. i used reportbug .. but .. it sent the mail and all... but i didnt get a chance to attach a patch :P
[21:50] <evilshadeslayer> i didnt even get a bug number
[21:50] <tumbleweed> evilshadeslayer: you'll be e-mailed th ebug number
[21:50] <tumbleweed> then you can attach the patch
[21:50] <evilshadeslayer> oh ok
[21:50] <tumbleweed> evilshadeslayer: btw submittodebian makes it all easier
[21:50] <evilshadeslayer> hmm
[21:50] <evilshadeslayer> well the page said to use reportbug :P
[21:51] <tumbleweed> evilshadeslayer: submittodebian is a wrapper around reportbug
[21:51] <evilshadeslayer> hmm didnt see that
[21:59] <evilshadeslayer> tumbleweed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588657
[21:59] <evilshadeslayer> tumbleweed: i just send a mail to the specified bug address with the patch?
[22:01] <tumbleweed> evilshadeslayer: yes, but while you are there, let's do a few more things
[22:01] <evilshadeslayer> uh ok
[22:02] <evilshadeslayer> tumbleweed: what needs to be done?
[22:02] <tumbleweed> ok, so, you filed the bug as important, but you can actually raise it to serious
[22:03] <evilshadeslayer> ok,how?
[22:03] <tumbleweed> you should also add the tag "patch"
[22:03] <evilshadeslayer> tumbleweed: i have no idea how to do this :P
[22:04] <tumbleweed> http://www.debian.org/Bugs/server-control
[22:05] <tumbleweed> cc your email to<EMAIL_ADDRESS>and start it with this http://paste.ubuntu.com/461747/
[22:07] <evilshadeslayer> tumbleweed: just that part of pastebin in the body?
[22:09] <tumbleweed> evilshadeslayer: yes, the bug control server follows instructions in the mail body. It'll stop when it gets to thanks.
[22:09] <evilshadeslayer> ok
[22:09] <tumbleweed> oh, if you want to mark the bug as coming from debian, you can add this in too:
[22:09] <tumbleweed> user<EMAIL_ADDRESS>[22:09] <tumbleweed> usertag 588657 + origin-ubuntu maverick
[22:09] <evilshadeslayer> anything in subject? apart from " Patch for rbot "
[22:09] <tumbleweed> ...coming from ubuntu, I mean
[22:09] <tumbleweed> fine
[22:09] <evilshadeslayer> :)
[22:10] <evilshadeslayer> sent :D
[22:14] <evilshadeslayer> tumbleweed: hmm.. somethings wrong.. where do i add the upstream url again?
[22:14] <evilshadeslayer> to LP bugs
[22:14] <tumbleweed> "also affects distribution"
[22:15] <evilshadeslayer> tumbleweed: and i put the bug link right?
[22:15] <tumbleweed> yes
[22:15] <evilshadeslayer> doesnt work :(
[22:16] <evilshadeslayer> tumbleweed: you try
[22:16] <tumbleweed> you chose Debian as the distribution?
[22:18] <evilshadeslayer> wait
[22:18] <evilshadeslayer> tumbleweed: done :D
[22:18] <evilshadeslayer> now i wait :P


[19:15] <Tm_T> AlanBell: choo choo says night train
[19:21] <AlanBell> :)
[19:24] <AlanBell> so Tm_T shall we go through the agenda?
[19:24] <IdleOne> o/
[19:25] <IdleOne> let's get to it, we are burning daylight.
[19:25] <AlanBell> #startmeeting IRC team
[19:25] <meetingology> Meeting started Sun May 26 19:25:57 2013 UTC.  The chair is AlanBell. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[19:25] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[19:26] <AlanBell> https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda
[19:26] <AlanBell> we have missed a couple of meetings, and this one isn't really getting off to a great start :(
[19:27] <Tm_T> hmmm
[19:27]  * knome blows to a vuvuzela to lift up the mood
[19:27] <Tm_T> if there's something that require broader participation from IRCC I suppose we can continue via mail with those subject
[19:28] <IdleOne> +1
[19:28] <IdleOne> m4v still hasn't been made a member :/
[19:29] <AlanBell> yes, we can and m4v membership application is something I would really like to do by mail, that has been hanging for far too long
[19:29] <Tm_T> agreed
[19:29] <AlanBell> #topic Review last meetings action items
[19:30]  * AlanBell hunts back for the last meeting that wasn't just postponing stuff to the next meeting
[19:33] <AlanBell> gosh, it really has been some time
[19:34] <AlanBell> I will have a further hunt later for undone action items
[19:35] <AlanBell> #topic Open items in the IRCC tracker
[19:35] <AlanBell> there has been no activity in the tracker
[19:35] <AlanBell> #topic Review Bugs related to the Ubuntu IRC Council
[19:35] <AlanBell> we have no bugs
[19:35] <AlanBell> #topic Membership applications
[19:36] <AlanBell> we do have a membership application from m4v
[19:36] <AlanBell> https://wiki.ubuntu.com/m4v
[19:36] <AlanBell> https://launchpad.net/~m4v
[19:37] <AlanBell> m4v has been a consistent long term contributor to Ubuntu in particular in the IRC area, and especially on the bot infrastructure
[19:37] <bazhang> that should be an insta-pass
[19:37] <Unit193> Is he here?
[19:38] <AlanBell> I am entirely comfortable that the IRCC is an appropriate membership body for this application
[19:38] <bazhang> m4v, not in this channel
[19:38] <AlanBell> the wiki page looks good and there are strong testimonials
[19:39] <IdleOne> m4v gets my +1
[19:39] <IdleOne> please to pass that along on the mailing list :)
[19:39] <AlanBell> we will vote on it by email, anyone else got any thoughts to add?
[19:40] <Tm_T> +1 for mailinglist
[19:40] <lderan> Hello
[19:40] <knome> lderan, o/
[19:42] <Tm_T> let's move to next topic
[19:43] <AlanBell> yup
[19:43] <AlanBell> #topic Replace floodbot kick+ban behaviour for webchat users who flood - tsimpson
[19:44] <AlanBell> https://wiki.ubuntu.com/IRC/IrcCouncil/IRCteamproposal has further details
[19:44] <AlanBell> Currently when a webchat user floods the bots will set a ban and kick the user, then forget about them. I think this behaviour is overly defensive and discriminates against webchat users unfairly. It would make more sense if the bots simply set -e for that user (as to apply the existing quiet on webchat users) instead of the +q they normally set.
[19:44] <AlanBell> This would require some modification to the floodbot script but, as already treats webchat users who flood differently, it shouldn't be too major.
[19:44] <Tm_T> +1 from mew
[19:44] <knome> AlanBell, what's -e ?
[19:44] <AlanBell> removing the exempt
[19:45] <AlanBell> so as I understand it, webchat is +q by default
[19:45] <Tm_T> knome: webchat is banned entirely, individuals have +e exempt that allows them to talk at all
[19:45] <knome> okay
[19:45] <Tm_T> banned, quieted, same effect in this case
[19:45] <IdleOne> knome: currently we +q all webchat, then floodbots set +e so they can speak in the channel.
[19:45] <knome> sounds fair
[19:46] <IdleOne> setting -e would allow them to remain in the channel, but the floodbots would need to let the user know somehow how to get the +e reset.
[19:47] <IdleOne> which would mean that when there are no ops around, the ops channel could end up with users waiting a long time and getting frustrated
[19:47] <knome> wouldn't the webchat users get +e if they just rejoined?
[19:47] <AlanBell> but at the moment they just get banned altogether
[19:47] <knome> or would that have to be done manually
[19:48] <IdleOne> knome: floodbots track which users have been banned so we would need some sort of mechanism to let floobots know that $user is ok to let back in the channel and be able to speak
[19:48] <knome> mhm
[19:50] <IdleOne> I don't think it will be a major issue. +1 to setting -e instead of kick/banning
[19:50] <AlanBell> yeah, I think the policy suggestion is fine, it just needs someone to tangle with the floodbot code and implement it
[19:51] <AlanBell> LJL knows that code, dunno if tsimpson was proposing to do it or not
[19:51] <IdleOne> How is the open sourcing of that code coming, if at all?
[19:51] <AlanBell> it would be good to get other people familiar with the floodbot code
[19:52] <Unit193> Could be just like a quiet, -e and if it continues +b kick, and if not, +e.
[19:52] <AlanBell> the code is on launchpad, not much progress since then, LjL wasn't around for some time and it became less of a priority once it was on launchpad (albeit in a private project)
[19:54] <AlanBell> https://launchpad.net/floodbot is the project
[19:54] <IdleOne> Would it be easier to use supybot with the functionality of the floodbots added?
[19:55] <AlanBell> floodbot is written in PHP rather than python, it is 1807 lines of code
[19:56] <AlanBell> and does some funky stuff with multiple instances of the bot talking to each other through control channels and sharing updates via a pastebin and other surprising and interesting features
[19:57] <IdleOne> short answer: no.
[19:57] <LjL> if the floodbots aren't going to set +b on kicked webchat users any longer, are we confident the ops will know how to actually ban them?
[19:59] <IdleOne> most of us use scripts to do that
[20:01] <LjL> IdleOne: which are webchat-aware?
[20:01] <IdleOne> chanserv.py currently defaults to *591c6114@* for webchat
[20:02] <LjL> uh?
[20:02] <LjL> you mean it bans the ident?
[20:02] <IdleOne> correct
[20:02] <LjL> well that won't let the floodbots know the user is banned
[20:03] <IdleOne> I know
[20:03] <IdleOne> which is why those of us who use chanserv.py try not to ban webchat and instead we remove/kick and let floodbot set the ban
[20:03] <LjL> then again these days the IP is in the webchat mask, so it's less bad than it used to be. but banning the ident or other funny things one might do don't play nice with the system
[20:04] <bazhang> yep
[20:04] <bazhang> just a remove
[20:04] <LjL> IdleOne: and what do the others do, just ban *!*@gateway/whatever?
[20:04] <IdleOne> not sure what auto_bleh does
[20:04] <IdleOne> I haven't used it in a long time
[20:07] <LjL> anyway to answer your question IdleOne, i don't think anyone has worked on the floodbots to bring them to what could be a releasable state. i know i haven't, and at this point, i really don't think i'm ever going to
[20:07] <Tm_T> I have to go, but I support any changes toward equal treatment
[20:07] <AlanBell> ok Tm_T
[20:07] <IdleOne> LjL: understandable.
[20:10] <AlanBell> so, do we think this is still a good idea, a bad idea, or an idea that requires further thought, and a plan for someone to implement it?
[20:10] <IdleOne> currently the only one who could implement it is LjL right?
[20:12] <IdleOne> I think maybe a better idea would be leave things the way they are but have floodbot send a notice to the channel asking for a live op to set a comment/duration on the ban
[20:12] <Unit193> (Autobleh doesn't ban nick or ident, just host.  At least, that's how I set it up.)
[20:12] <IdleOne> s/to the channel/to the control channel/
[20:12] <LjL> i can comment out the line the says "ban it", but not sure whether it'll have other side effects i'm currently not thinking about. i guess i can just do it and we'll see. i'm not really in the mood to look at it in detail
[20:13] <LjL> IdleOne: well it already sends a "-WARNING" that people are supposed to highlight on
[20:13] <IdleOne> I would prefer if a live op decides whether to remove the ban or set a time limit on it.
[20:13] <IdleOne> LjL: it doesn't tell us the banID though
[20:14] <LjL> it doesn't have a clue about the "banID"
[20:14] <IdleOne> doesn't ubottu ask floodbot to comment on the ban?
[20:14] <LjL> i don't think so
[20:14] <IdleOne> ubottu: sens me a PM every time I set a ban
[20:14] <IdleOne> sends*
[20:15] <LjL> IdleOne, pretty sure the floodbots are exempted from them
[20:15] <LjL> that*
[20:16] <IdleOne> Well, fair treatment is all well and good. IF it means possibly breaking the floodbots other behaviors we might want to hold off.
[20:21] <AlanBell> yeah, I am not sure about this
[20:21] <AlanBell> maybe it could be a banforward rather than a ban
[20:21] <AlanBell> but I am not sure how much of a problem this actually is
[20:21] <LjL> honestly IdleOne, if you want to talk about this, you might as well talk about removing the webchat +b entirely and just handling webchat users manually. the floodbots introduced automatic handling for this because it was hard to match people's real hostnames with the webchat hostname they obtained
[20:21] <LjL> but these days, the hostname for webchat users contains their real IP
[20:21] <LjL> so you can just go ban that as needed
[20:23] <AlanBell> ok, well it was a proposal from tsimpson, who was around earlier
[20:23] <IdleOne> LjL: I didn't see the +b as an issue honestly. I would like it if the floodbots could ask us to set comments on the banID (not a big thing if they don't)
[20:23] <IdleOne> just thought it would be a nice feature
[20:24] <AlanBell> I think we need to discuss further, perhaps on the mailing list, I am not sure that there are any changes that really need to be made, and if there are, it might not be the one proposed
[20:24] <IdleOne> IMO leave things as is. I think we are searching for a tech solution where one isn't needed.
[20:25] <LjL> IdleOne: maybe ubottu can do that, the floodbots sure can't as they don't know about banIDs (and if they somehow got ubottu to tell you, it would be annoyingly complicated to deal with it, and there's no reason why ubottu couldn't do it in the first place)
[20:25] <AlanBell> OK, I will send a mail to the list later with minutes of this meeting and highlight the discussion around this topic
[20:25] <IdleOne> sounds good.
[20:26] <LjL> AlanBell: maybe the only problem that should be a real problem that i see is what happens when people got automatically muted for flooding. if the involved person is a webchat user, then they get an automatic ban, and if there's no one around to remove that, they stay banned.
[20:26] <AlanBell> yeah, I just don't know if that actually happens much to real people who are not intentionally flooding
[20:26] <LjL> AlanBell: as to when ops actually kick someone manually, though... i think they should have a look at the modes being set and the floodbot "-WARNING" and realize
[20:28] <LjL> anyway tsimpson may also be able to implement whatever is needed, i'm sure he's among the people most familiar with both the floodbots and ubottu. get his opinion, or just let him work out what seems best
[20:28] <AlanBell> yeah :)
[20:28] <AlanBell> #topic Any Other Business
[20:28] <tsimpson> ubottu does
[20:28] <tsimpson> "[ubottu] Please somebody comment on the ban of<EMAIL_ADDRESS>in #ubuntu done by FloodBot3, use: @comment 55195 <comment>" eg
[20:28] <AlanBell> oh, hi tsimpson
[20:28] <tsimpson> \o
[20:28] <LjL> tsimpson: ah that's nice, IdleOne's concern is settled then i think
[20:29] <IdleOne> so the real problem is humans not listening to the bot when it asks for something
[20:29] <LjL> yeah :)
[20:29] <AlanBell> yeah, I think maybe a refresher on what messages the bots do that humans should respond to might be good
[20:29] <Unit193> AlanBell: Review of the ubuntu-bots bugs?  I'd think [Eir] ones could be closed?
[20:31] <AlanBell> #action AlanBell to compile page on bot messages for humans
[20:31] <meetingology> ACTION: AlanBell to compile page on bot messages for humans
[20:31] <tsimpson> there is only bug #899630 left
[20:31] <tsimpson> that should probably be closed
[20:31] <AlanBell> interesting point Unit193
[20:31] <AlanBell> https://bugs.launchpad.net/ubuntu-bots
[20:32] <AlanBell> bug #899630 is now closed
[20:33] <knome> meetingology is tweaked by lderan! \o/
[20:34] <meetingology> knome: Error: "is" is not a valid command.
[20:34] <knome> boo.
[20:34] <lderan> :P
[20:34] <AlanBell> yes, lderan has done some great stuff :) private votes are on the way \o/
[20:34] <knome> and the moin output is so much better, it's pretty much ready-to-copy-paste now
[20:35] <AlanBell> yup
[20:35] <AlanBell> ok, any other stuff before I close this meeting?
[20:35] <lderan> :D
[20:35] <AlanBell> #endmeeting
[20:35] <meetingology> Meeting ended Sun May 26 20:35:51 2013 UTC.
[20:35] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-05-26-19.25.moin.txt
[20:35] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-05-26-19.25.html
[20:35] <AlanBell> thanks everyone
[20:36] <IdleOne> thank you
[20:36] <knome> you should all look in the wonderful wiki output
[20:38] <lderan> yes do :P
[20:42] <IdleOne> looks beautiful
[20:52] <AlanBell> https://wiki.ubuntu.com/MeetingLogs/IRCC/20130526


[05:46] <Noskcaj> bug 1164343
[06:35] <dholbach> good morning
[06:38] <jibel> good morning
[06:47] <smartboyhw> hello dholbach
[06:47] <dholbach> hi smartboyhw
[07:06] <pitti> Good morning
[07:11] <jibel> bonjour pitti
[07:12] <pitti> bonjour jibel, ça va ?
[07:13] <jibel> pitti, très bien et toi? apart from your adventure with your landline phone ;)
[07:15] <pitti> jibel: un petite fatigue, mais je vais bien
[07:15] <pitti> I'm glad that the psql stuff went well, so back to writing network test cases :)
[07:21] <smartboyhw> Hmm 7:15 GMT now. Hopefully we will get Beta 2 in 3 hours:)
[11:33] <smartboyhw> balloons, pong back me whenever you are available.
[12:28] <pitti> jibel: uh, lots of armhf autopkgtest failures
[12:29] <pitti> jibel: but it's great to have them running now, merci beaucoup!
[12:31] <jibel> pitti, de rien :) I quickly walked through the failures and was wondering if some (most?) of them are due to container limitations, like restrictions on /dev
[12:31] <pitti> yeah, I figure things like gvfs or udisks won't have much chance there
[12:49] <balloons> smartboyhw, allo
[12:49] <smartboyhw> balloons, hello.
[12:50] <smartboyhw> We are discussing for the possibility of maintaining Testdrive ourselves
[12:50] <balloons> who is "we"?
[12:50] <smartboyhw> balloons, me + Noskcaj
[12:50] <smartboyhw> ourselves = QA Team
[12:51] <balloons> ahh
[12:51] <balloons> :-)
[12:51] <smartboyhw> balloons, :)
[12:52] <balloons> ok, well.. you should start by trying to fix some bugs :-)
[12:52] <balloons> things that are important to you
[12:52] <smartboyhw> balloons, well you should try first:P
[12:53] <smartboyhw> balloons, after you try I try
[12:57] <balloons> lol
[12:58] <smartboyhw> balloons, yep. You try first
[12:58] <smartboyhw> See how difficult it is for you:P
[12:58] <smartboyhw> balloons, fix the 2-row bug
[13:08] <pitti> balloons: oh, we have a meeting now, don't we?
[13:08] <balloons> pitti, :-)
[13:08] <balloons> join us
[13:09] <balloons> if you wish
[13:20] <smartboyhw> phillw, run your script! It is released!
[13:20] <smartboyhw> balloons, if you may remove that "Raring final Beta Testing" please:P
[13:20] <balloons> :-)
[13:20] <smartboyhw> balloons, and don't forget to DEPO
[13:21] <smartboyhw> s/DEPO/DEOP/
[13:40] <phillw> smartboyhw: it's not 'my' script, such matters are looked after by someone far more intelligent than myself :P
[13:40] <smartboyhw> phillw, .....
[13:40] <smartboyhw> LOL
[13:40] <smartboyhw> Anyways phillw it is released and we are all happy:)
[13:40] <smartboyhw> Tell your testers:)
[13:45] <balloons> xnox, I hear you have some ubiquity automated tests I didn' t know about.. I'm curious to learn :-)
[13:57] <pitti> jibel: did you happen to use run-adt-test/prepare-testbed with a proxy somewhere?
[13:58] <pitti> jibel: I wonder how much effort it would be to make prepare-testbed create an /etc/apt/apt.conf.d/01proxy file, so that it can be used with apt-cacher-ng
[13:58] <jibel> pitti, yes, in the lab.
[13:59] <jibel> pitti, not too much effort, could you file a bug against auto-package-testing and assign it to me so I don't forget?
[14:00] <pitti> jibel: will do; not a biggie
[14:00] <jibel> thanks
[14:04] <pitti> jibel: it already exists, I made an additional comment: https://bugs.launchpad.net/auto-package-testing/+bug/1042217
[14:05] <jibel> pitti, and I reported it :)
[14:40] <cprofitt> hello... I have a strange 'bug' that I am not sure how to report
[14:40] <cprofitt> I need to do more testing after work today, but advice would be appreciated
[14:41] <cprofitt> it is a Lenovo T500... and the Ethernet does not work on battery
[14:42] <cprofitt> this is under 13.04... under 12.10 it does not have this issue
[14:42] <balloons> cprofitt, ohh.. under battery only?
[14:42] <cprofitt> yep
[14:42] <balloons> powersaving of some sort?
[14:42] <cprofitt> could be, but it is nothing I have setup
[14:43] <cprofitt> and does not appear to be bios related from what I can tell
[14:43] <cprofitt> 12.10 works on battery, but 13.04 does not
[14:43] <cprofitt> I am on power 99% of the time so had not noticed it until last night when I worked on a customers issue
[14:45] <balloons> you might need to mess about with different kernels to see if that's where the regression lies
[14:45]  * cprofitt nods
[14:46] <cprofitt> any specific commands to run to gather the necessary information
[14:46] <cprofitt> ifconfig still shows the ethernet as being there, but it does not work
[14:46] <balloons> cprofitt, well yea, some debugging as to what's going on might help
[14:47] <balloons> for instance, plugged in, connect to ethernet
[14:47] <balloons> then unplug.. do you lose connection?
[14:47] <cprofitt> No, I do not lose connection if it was plugged in and I remove power
[14:47] <balloons> what appears in the syslog
[14:47] <cprofitt> only if I start the laptop up w/o power
[14:48] <balloons> ahh ok.. so if you boot without power, and then add in power can you connect?
[14:48] <balloons> I would be interested in your logs no matter what.. they should reveal somethng about what's going on
[14:48] <balloons> fingers crossed, haha
[14:48] <cprofitt> yes
[14:48] <cprofitt> yes, if I add power the Ehternet starts to work
[14:49] <cprofitt> which logs should I collect?
[14:49] <balloons> https://wiki.ubuntu.com/DebuggingACPI
[14:49] <cprofitt> ah... syslog
[14:49] <cprofitt> ok...
[14:49] <balloons> see the filing a bug report part
[14:49] <balloons> also, try the boot options :-)
[14:54] <cprofitt> thanks
[14:59] <balloons> yw
[16:23] <jibel> pitti, apt proxy support in r165. set APTPROXY in ~/.adtrc to your local proxy address.
[16:25] <pitti> jibel: wow, thanks!
[16:25] <pitti> ah, or in ~/.adtrc, perfect
[16:25] <pitti> jibel: that's the IP as seen from the client, I guess
[16:25] <pitti> jibel: i. e. not <IP_ADDRESS>, but <IP_ADDRESS>
[16:27] <jibel> pitti, right, IP from the client (<IP_ADDRESS>, <IP_ADDRESS>:3128 on my home net) or hostname if it's resolvable on your network
[16:27] <jibel> + port of course
[16:27] <pitti> oh wow, that actually works
[16:27] <pitti> $ host donald
[16:27] <pitti> donald has address <IP_ADDRESS>
[16:27] <pitti> donald has IPv6 address fe80::224:d7ff:fe20:b470
[16:28] <pitti> ah, I guess it asks the hosts' dnsmasq
[16:28] <pitti> yay for a local DNS server
[16:28] <pitti> but I guess <IP_ADDRESS> should always work
[18:00] <jtaylor> can one get the install log from this: https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-python-scipy-armhf/ARCH=armhf,label=adt&&arm/5/artifact/results/summary.log
[18:00] <jtaylor> the log only shows package failed to install, but no further messages
[18:01] <jtaylor> oh wait, I know why it failed
[18:02] <jtaylor> I guess we'll have to live with that failure, as autopkgtest does not support versions it certainly won't support arch qualifications
[18:02] <balloons> hmm
[18:15] <jtaylor> I guess it would make sense for autopkgtest to skip tests a dependency excludes an arch
[18:15] <jtaylor> alterntive would be add a arch field to dep8 test syntax
[18:15] <jtaylor> which is probably overkill
[18:16] <jtaylor> I'll file a bug
[18:21] <jtaylor> bug 1165128
[19:18] <SergioMeneses> hi guys! maybe this will be interesting http://lococouncil.ubuntu.com/2013/04/05/about-ubuntu-13-04-cdsdvds/
[19:19] <balloons> SergioMeneses, LTS's are really becoming focused more and more
[19:20] <SergioMeneses> balloons, sure!
[19:20] <SergioMeneses> balloons, and I am agree about it
[19:20] <SergioMeneses> do you?
[19:20] <balloons> yes, very much
[19:20]  * SergioMeneses hugs balloons
[19:20] <balloons> my post about rolling release is my viewpoints on it
[19:21] <balloons> in short, I'd like to base everything about "stable" being LTS's with timely updates delivered
[19:22] <balloons> then just a rolling development release.. I'll always be on dev, so in some ways I'm already rolling.. but it would be easier to just avoid the need for the interim releases as much
[19:22] <balloons> at any rate.. interesting to see more and more focus
[19:22] <balloons> and man.. I can't wait for 14.04!
[19:25] <SergioMeneses> balloons, 14.04? really? jejeje I think you have time enough to play with soemthing more
[19:25] <balloons> lol.. yes, but it's the next lts
[19:25] <balloons> and like every lts, it will be a culmination of change
[19:26] <SergioMeneses> balloons, sure!
[19:27] <SergioMeneses> but let me say something, ubuntu 13.04 is beautiful , the design, icons, everything is perfect
[19:27] <SergioMeneses> I'm using 13.04 beta
[19:27] <SergioMeneses> but it looks awesome
[19:27] <balloons> yes :-)
[19:27] <balloons> upgrade go ok then I guess?
[19:28] <SergioMeneses> yes, an upgrade
[19:28] <SergioMeneses> I can make a total install, not now
[19:28] <SergioMeneses> can't
[19:33] <Letozaf_> balloons, Hi
[19:34] <Letozaf_> SergioMeneses, o/
[19:34] <balloons> Letozaf_, hello
[19:35] <Letozaf_> balloons, I'm carrying out some laptop tests, I have a doubt on a test can I ask you ?
[19:35] <balloons> sure, go for it
[19:35] <SergioMeneses> Letozaf_, Ursinha hi
[19:35] <SergioMeneses> Letozaf_, what?
[19:36] <Letozaf_> balloons, well I am testing the USB ports and when you attach a music player, for instance
[19:36] <Letozaf_> balloons, the testcase says that a suggestion box should ask you to open Rhythmbox
[19:36] <balloons> ahh yes
[19:36] <Letozaf_> balloons, but instead
[19:37] <balloons> if you have autolaunche preferences
[19:37] <Letozaf_> balloons, the suggestion box ask me what to do
[19:37] <Letozaf_> balloons, so shouldn't the testcase be modified ?
[19:37] <Letozaf_> balloons, I mean someone could think that its a bug
[19:38] <SergioMeneses> Letozaf_, maybe is an old testcase
[19:38] <Letozaf_> SergioMeneses, could be
[19:38] <SergioMeneses> Letozaf_, do you have the link?
[19:39] <Letozaf_> SergioMeneses,http://laptop.qa.ubuntu.com/qatracker/testcases/1476/info
[19:39] <Letozaf_> SergioMeneses, Case ID: hiu-002
[19:40] <Letozaf_> SergioMeneses, balloons I have Raring just installed and so I think that the default behavior is to ask what to do and not ask to open Rhythmbox
[19:43] <balloons> want to propose a commit to modify the cases?
[19:44] <balloons> in general, the test is really just for a prompt
[19:44] <balloons> but only if you have autolaunch on
[19:45] <Letozaf_> balloons, that's why I was asking to know witch it the right one, I think that a newbie testing could think he found a bug if the testcase is not clear
[19:45] <balloons> Letozaf_, absolutely
[19:45] <balloons> the test has to be clear
[19:46] <balloons> so under system details, removable media
[19:46] <SergioMeneses> mmmm
[19:46] <balloons> that controls things
[19:46] <SergioMeneses> I write that testcase =/
[19:46] <balloons> depending on the settings, your pc will react differently
[19:47] <Letozaf_> balloons, yes, that's the point
[19:47] <SergioMeneses> *wrote
[19:47] <balloons> so.. the idea behind the test is connectivity right..
[19:47] <Letozaf_> balloons, maybe we should just write that depending on your settings, you can get 2 different behaviours
[19:47] <balloons> so you should be able to see usb disks when you mount them
[19:47] <balloons> so perhaps we change the test altogether
[19:48] <balloons> to verify the fact that the usb disk automatically mounts
[19:48] <balloons> make sense?
[19:49] <balloons> in other words, we don't care if rythmnbox works in this case.. we actually have a test for that :-)  So just want to make sure the testcase stays clear
[19:50] <Letozaf_> balloons, SergioMeneses I think the testcase is ok, we just need to point out that you can have different behavior depending on your settings
[19:50] <Letozaf_> balloons, SergioMeneses what do you think ?
[19:51] <balloons> I didn't want to make it a testcase for the removable media settings :-)
[19:51] <SergioMeneses> balloons, ++
[19:51] <SergioMeneses> but we can add a note or commentary about it
[19:51] <Letozaf_> balloons, SergioMeneses ok fine
[19:51] <balloons> it's really just testing usb stuff.. I'm thinking have people plug in usb items
[19:51] <balloons> keyboards, mouse, pendrive, camera, etc
[19:52] <balloons> headphones:-)
[19:52] <balloons> have people try there usb devices and make sure they work properlu
[19:52] <Letozaf_> balloons, yes I think you are right
[19:52] <balloons> then you can list out some of those things.. aka, can you see the files on your pendrive, can you play music on your mp3 player.. does the mouse work, keyboard?
[19:52] <balloons> network usb adapter, etc, etc
[19:53] <Letozaf_> balloons, sounds good!
[19:53] <balloons> don't forget you can use the smoke testing format for this
[19:54] <balloons> https://wiki.ubuntu.com/Testing/TestCaseFormat
[19:54] <balloons> kk.. back in a few
[19:55] <Letozaf_> balloons, SergioMeneses so who's gonna do this, I mean if SergioMeneses wants to for me it-s fine, if not I will, it's the same for me, you decide
[19:57] <SergioMeneses> Letozaf_, if you want to, I have a lot of things to do :S lococouncil things
[19:57] <Letozaf_> SergioMeneses, balloons ok so I will :D
[19:58] <SergioMeneses> Letozaf_, if you need an opinion, advice or soemthing feel free to pm me
[19:58] <Letozaf_> SergioMeneses, thank you :)
[20:01] <SergioMeneses> btw balloons cprofitt what happen with ubuntu-friendly?  news or something
[20:35] <balloons> SergioMeneses, cprofitt et la are working on getting UF working without needing lp
[20:35] <balloons> so the profiles show up properly.. and if they don't they can know why ;-)
[21:15] <Noskcaj> because most of you didn't see howards suggestion, Why don't we make testdrive maintained by the QA team?
[21:16] <Noskcaj> balloons, haven't we finished testing beta 2? can you change it's status to "release"
[21:17] <balloons> Noskcaj, I don't change those statuses :-)
[21:17] <balloons> the release team decides that, but yes I agree..
[21:18] <balloons> it's weird to see the status not be set to released
[21:18] <Noskcaj> yeah
[21:18] <Noskcaj> and aren't a new set of dailies meant to be out?
[21:23] <balloons> Noskcaj, they are doing a lot of archive cleanup today
[22:05] <phillw> balloons: give stgraber a very gentle poke in the ribs, setting it to 'released' will have been an oversight as we were a bit later than planned in getting the beta 2's out :)
[22:41] <balloons> phillw, not everything is marked
[22:43] <phillw> balloons: look at http://iso.qa.ubuntu.com/qatracker/milestones/261/builds everything wasn't marked there, either. It's just a flag :)
[23:46] <SergioMeneses> ok guys! see you tomorrow, take care


 manual.lubuntu.me is offline for a bit, and will throw HTTPS errors until I get to update the certs (Certbot is not fun) tomorrow.  It requires Canonical to update the DNS first before I can do the certbot stuff on the new infra.  And unlike the previous everything's on one certificate approach, we're doing individual certs for individual domains.  Makes life a little easier heh.
[02:58] <guiverc> do you want me to paste somethign to reddit or elsewhere?  or do you think notices we've already made are enough?
[03:08] <guiverc> I've posted https://www.reddit.com/r/Lubuntu/comments/t96zpq/lubuntu_infrastructure_migration_still_occuring/  & entry on discourse
[03:08] <guiverc> & thanks @teward001
 yep yep
 i'm not doing a total migraiton just yet, doing it piecemeal heh
 but i'm only as fast as Canonical IS is :P
[03:15] <guiverc> Not a problem - do what's easiest/best for you !
 well saying "SCREW IT WE'LL BE DOWN FOR DAYS" Is an option but :P
 nah in this case manual might be down for like 12-18 hours or whatever when Canonical is slow
[03:40]  * guiverc suddenly remembers I was told iso.qa.ubuntu was being migrated by Canonical IS to newer hardware, that was >30 days ago now; so :(  at "or whatever when .. is slow"
 yes well in THIS case
 all Canonical has to do here for us is just update the DNS
 that's fast
 then i just need to do migrations heh
[19:39] <jbicha> hi, please update the 2 Lubuntu packages to depend on fonts-ubuntu instead of ttf-ubuntu-font-family https://people.canonical.com/~ubuntu-archive/nbs.html
[19:53] <kc2bez[m]> jbicha: Is there a bug to associate with that?
[19:54] <jbicha> kc2bez[m]: no
[19:55] <kc2bez[m]> Ok, no problem. I was just wondering for the changelog.
 fyi Manual is still down I believe - Canonical hasn't updated the DNS.  And internet-wide there's been some large outages in places so.
 manual is now migrated
 migrating notes.lubuntu.me now
 notes and phab are both going to migrate once DNS updates this time round.


[21:23] <ibeardslee> morning
[21:30] <ajmitch> morning
[21:31]  * ajmitch really doesn't like it when the 7:45 AM bus doesn't show & having to wait at the bus stop for another 20 minutes
[22:06] <chilts> morning
[22:55] <ojwb> morning
[22:57] <hads> Morning
[22:59] <Atamira> mornin
[22:59] <Atamira> hate having to get to the bus stop 20 mins early, and the bus comes even earlier than that
[22:59] <Atamira> and then the next one is late
[23:01]  * ojwb has concluded it's simpler just not to leave the house ever
[23:02] <thumper> morning
[23:02] <thumper> TGIF!
[23:05] <ibeardslee> ojwb: http://theoatmeal.com/comics/working_home
[23:06] <mwhudson> morning
[23:09] <Atamira> oh that is just sad ibeardslee
[23:10] <ojwb> sadly accurate