[02:04] <imgbot> [03:04] <imgbot> [05:34] <imgbot> [05:34] <imgbot> [05:34] <imgbot> [05:34] <imgbot> [11:54] <imgbot> [13:19] <slangasek> ogra_, sil2100: around?  bug #1385656 - I think we want a revert, but that needs figuring out what went in the image and since the commit logs aren't generated as part of the image build...
[13:20] <ogra_> slangasek, there isnt really anything in there that could affect packagekit http://people.canonical.com/~ogra/touch-image-stats/rtm/126.changes
[13:21] <ogra_> slangasek, http://people.canonical.com/~ogra/touch-image-stats/rtm/125.changes has apt changes, i wonder if that is somehow related
[13:22] <slangasek> john-mcaleely: was bug #1385656 definitely not reproducible on 125?
[13:24] <rsalveti> ogra_: quite a few packages got removed though, not sure if that could be causing any bad side effect
[13:24] <rsalveti> bug guess that's easy to know, just install them by hand
[13:25] <ogra_> rsalveti, thats all only hud, i doubt it can affect packagekit
[13:25] <rsalveti> hm, libdbusmenu-qt5 got removed
[13:25] <rsalveti> not sure if that would cause anything though
[13:25] <ogra_> but with the builder situation atm re-rolling an image will also be hard without some admin driving them ...
[13:25] <rsalveti> ogra_: what is the issue?
[13:26] <slangasek> what's the builder situation?
[13:26] <ogra_> they put image builds on awfully low score and are busy
[13:26] <ogra_> (see #ubuntu-release, i pinged about that a while ago)
[13:26] <slangasek> ok
[13:28] <ogra_> (Lese Datenbank ... 38661 Dateien und Verzeichnisse sind derzeit installiert.)
[13:28] <ogra_> Vorbereitung zum Entpacken von .../libdbusmenu-qt5_0.9.3+14.10.20140619-0ubuntu1_armhf.deb ...
[13:28] <ogra_> Entpacken von libdbusmenu-qt5:armhf (0.9.3+14.10.20140619-0ubuntu1) ...
[13:28] <ogra_> Error: Timeout was reached
[13:28] <ogra_> phablet@ubuntu-phablet:~$
[13:28] <ogra_> (sorry for the german)
[13:28] <ogra_> smells like we have some bigger problem here
[13:28] <ogra_> (not sure where thaat message comes from though)
[13:30] <ogra_> seems it installed the package fine though
[13:32] <ogra_> so i see that packagekit message in syslog when unity8 tries to refresh the view after installing ...
[13:32] <ogra_> then it goes to 100% CPU
[13:35] <ogra_> hmm
[13:36] <ogra_> in fact it is constantly at 100% cpu even after reboot
[13:36] <ogra_> crap
[13:38]  * ogra_ installs unity-voice-service ... (and starts packing)
[13:40] <ogra_> bah
[13:41] <ogra_> now apport hardlocked my phone ... doesnt take input anymore
[13:41] <ogra_> with a load of 13 in top
[13:42] <rsalveti> Oct 25 09:41:27 ubuntu-phablet PackageKit: daemon start
[13:42] <rsalveti> Oct 25 09:41:27 ubuntu-phablet PackageKit: daemon quit
[13:42] <rsalveti> Oct 25 09:41:52 ubuntu-phablet dbus[750]: [system] Failed to activate service 'org.freedesktop.PackageKit': timed out
[13:42] <rsalveti> yeah
[13:42] <rsalveti> that's what I'm getting
[13:42] <ogra_> right, like i logged in the bug
[13:43] <ogra_> i have all dropped packages re-installed apart from the hub
[13:43] <ogra_> i see a fresh ubuntu-app-launch file in /var/crash
[13:44] <ogra_> hmm, now it behaves better after a reboot
[13:46] <slangasek> reproducible on previous build? reproducible on mako?
[13:47]  * ogra_ installs hud too ... then i will have all dropped packages back
[13:47] <rsalveti> weird, even after reinstalling hud and every dropped package, it is still failing for me
[13:47] <ogra_> yeah
[13:47] <rsalveti> was 125 fine?
[13:47] <ogra_> i doubt it is actually the dropping of packages
[13:47] <ogra_> no idea and i dont have the time to test that
[13:48] <ogra_> rsalveti, 125 has the libc change though
[13:48] <rsalveti> will take ages for me to download it
[13:48] <ogra_> well, same network here :)
[13:49] <rsalveti> yeah, quite a few changes on 125 as well, apt, bash, gstreamer, libc
[13:49] <ogra_> right
[13:49] <slangasek> the libc change was a targeted change to raise the limit on TLS usage; there's no reason to think that's the cause
[13:49] <slangasek> that is, there's no reason to single it out as a possible cause
[13:50] <ogra_> http://fanf42.blogspot.com/2014/08/upgrading-to-ubuntu-1404-error-timeout.html
[13:50] <ogra_> there
[13:51] <ogra_> i get the timeout error here all the time ... seems that refers to the apt change
[13:51] <rsalveti> I did get ' Error: Timeout was reached' as well
[13:51] <ogra_> right
[13:51] <ogra_> i dont get apt segfaults like he describes though
[13:52] <ogra_> (and indeed it is a totally different problem, but a good pointer i think)
[13:52] <ogra_> rsalveti, try downgarding apt
[13:52] <rsalveti> what were the apt changes that we got on 125?
[13:52] <ogra_> security fixes
[13:53] <ogra_> security team synced bash and apt from utopic
[13:53] <slangasek> apt shouldn't be involved in the installation of a click package, however
[13:53] <rsalveti> right
[13:53] <ogra_> indeed
[13:53] <rsalveti> this timeout we got was when installing deb packages with apt
[13:54] <ogra_> well
[13:54] <ogra_> does  packagekit use libapt anywhere ?
[13:55] <ogra_> i assume it is perhaps linked against it
[14:03] <rsalveti> ogra_: slangasek: downgrading apt fixes it
[14:03] <rsalveti> Oct 25 10:02:43 ubuntu-phablet dbus[751]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
[14:03] <rsalveti> Oct 25 10:02:43 ubuntu-phablet PackageKit: daemon start
[14:03] <rsalveti> Oct 25 10:02:43 ubuntu-phablet dbus[751]: [system] Successfully activated service 'org.freedesktop.PackageKit'
[14:04] <ogra_> https://lists.ubuntu.com/archives/rtm-14.09-changes/2014-October/000763.html
[14:05] <rsalveti> wow, diff is huge, major version bump
[14:05] <ogra_> does not really sound like related in any way ... i suspect we were multiple versions behind
[14:05] <rsalveti> yes
[14:05] <rsalveti> https://launchpadlibrarian.net/187988966/apt_1.0.4ubuntu6_<IP_ADDRESS>ubuntu2.diff.gz
[14:05] <ogra_> and PPAs dont take -v into account for dpkg-genchanges
[14:06] <ogra_> (which annoys me since we use them)
[14:07] <rsalveti> flashing 126 again and will only downgrade apt to see if that is indeed what caused the issue
[14:07] <rsalveti> then we should probably revert if for now, and retry the landing with the extra needed fix next week
[14:07] <ogra_> ++
[14:08] <ogra_> i need to check out soon though, someone else will have to drive the builds
[14:08] <rsalveti> will try to get the revert on a ppa
[14:09]  * ogra_ goes downstairs for a smoke before finishing the packing here
[14:24] <imgbot> [14:24] <imgbot> [14:25] <popey> \o/
[14:44] <popey> clean installed 127 and it's device offline ...
[14:46] <ogra_> you mean in adb ?
[14:47] <popey> yes
[14:47] <popey> sat at the logo now
[14:47] <popey> JW011705	offline
[14:47] <popey> i had OTA updated to the broken image earlier, then used udf to flash it when i just saw the bot announce 127 was done
[14:48] <popey> hah, now it's booted
[14:50] <ogra_> sounds like apparmor re-generating
[14:51] <popey> yeah, i guess so
[14:51] <popey> 127 is still busted
[14:51] <popey> can't run pkcon
[14:52] <rsalveti> ogra_: popey: mind testing https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-012 ?
[14:52] <popey> phablet@ubuntu-phablet:~$ pkcon
[14:52] <popey> Failed to contact PackageKit: Error calling StartServiceByName for org.freedesktop.PackageKit: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PackageKit timed out
[14:52] <popey> ok
[14:52] <rsalveti> for https://launchpad.net/bugs/1385656
[14:52] <popey> is there some magic for testing? I mean, some special way to add the ppa (I haven't used ppas for a while on rtm)
[14:52] <rsalveti> same as before, with apt-add-repository
[14:53] <popey> or is add-apt-repository ppa:ci-train-ppa-service/landing-012  sufficient?
[14:53] <rsalveti> just add a team/distro/ppa
[14:53] <ogra_> popey, citrain
[14:53] <rsalveti> in this case it would be ppa:ci-train-ppa-service/ubuntu-rtm/landing-012
[14:53] <popey> ok
[14:53] <rsalveti> ogra_: what is new in 127?
[14:53] <rsalveti> device tarball updates?
[14:54] <ogra_> rsalveti, nothing apparently, i thought the network-manager change was not landed
[14:54] <rsalveti> oh, alright
[14:54] <ogra_> which is why i triggered this build
[14:59] <ogra_> rebooting ...
[15:01] <ogra_> installing lastpass
[15:01] <ogra_> done
[15:01] <ogra_> rsalveti, works fine for me
[15:01]  * ogra_ removes lastpass again
[15:01]  * popey reboots
[15:02] <ogra_> rsalveti, seems to be fine
[15:03] <ogra_> unrelatedly i thik unity8 is eating wayy to much resources though ... but thats for next week
[15:03] <popey> pkcon is still broken
[15:04] <ogra_> i didnt check from cmdline ... the store worked for me
[15:06] <popey> hmm, should I have upgraded more than just apt from that ppa?
[15:06] <ogra_> yes
[15:06] <popey> ok
[15:06] <rsalveti> ogra_: what should we do, publish and image rebuild?
[15:06] <ogra_> rsalveti, yeah
[15:07] <ogra_> popey, all packages you have iinstalled indeed ...
[15:07] <popey> ok, yes, that fixed it, and pkcon
[15:07] <rsalveti> pkcon working fine here
[15:07] <popey> rsalveti: ^
[15:07] <rsalveti> great, will publish
[15:07] <ogra_> phablet@ubuntu-phablet:~$ ls apt/
[15:07] <ogra_> apt_<IP_ADDRESS>ubuntu2.is.1.0.4ubuntu7_armhf.deb                  libapt-inst1.5_<IP_ADDRESS>ubuntu2.is.1.0.4ubuntu7_armhf.deb
[15:07] <ogra_> apt-transport-https_<IP_ADDRESS>ubuntu2.is.1.0.4ubuntu7_armhf.deb  libapt-pkg4.12_<IP_ADDRESS>ubuntu2.is.1.0.4ubuntu7_armhf.deb
[15:07] <ogra_> apt-utils_<IP_ADDRESS>ubuntu2.is.1.0.4ubuntu7_armhf.deb
[15:08] <ogra_> (i usually wget them and "dpkg -i *" for silo testing ... thats slightly cleaner
[15:08] <ogra_> )
[15:08] <ogra_> rsalveti, write a mail about that ... since we worked past QA here
[15:08] <rsalveti> ogra_: sure
[15:08] <ogra_> so people are aware what we did
[15:08] <popey> nice one, thanks chaps!
[15:09] <ogra_> popey, well ... we dont have an image yet ...
[15:09]  * popey restarts doing the original thing he was doing, installing a click to test it
[15:09] <popey> well, I'm alright ㋛
[15:09] <ogra_> heh
[15:15] <rsalveti> ogra_: are you going to be able to trigger a new image once it migrates to rtm release?
[15:15] <rsalveti> need to pack my stuff here
[15:17] <ogra_> if it does that before 12
[15:18]  * popey flew back on an A380 which was very nice and new
[15:18] <popey> sat in the highest seat number I have ever sat in... 83A
[15:21] <ogra_> wow
[15:23]  * ogra_ twiddles thimbs til rmadison agrees with the bot
[15:23] <ogra_> *thumbs too
[15:28] <ogra_> sigh ... slow publisher ..
[15:30] <rsalveti> ogra_: should be in release in a few more
[15:31] <rsalveti> lp thinks it's already in release
[15:34] <ogra_> well, i have to leave the room before 12 ...
[15:35] <ogra_> (and rmadison still disagrees)
[15:35] <ogra_> also with the builders being busy i'm not sure we will get an image soon unless we have someone bumping its build score
[15:50] <rsalveti> still not in rmadison...
[15:51] <ogra_> i'm moving to the lobby ... hoping the wlan code will stay valind long enough
[15:52] <popey> ogra_: the bar has free wifi with no code needed
[16:01] <ogra_> ok, build triggered
[16:04] <imgbot> [16:05] <cjwatson> ogra_: the correct fix FWIW was a new packagekit
[16:05] <cjwatson> ogra_: https://launchpad.net/ubuntu/+source/packagekit/0.8.17-4ubuntu3
[16:05] <cjwatson> yet another thing we're wasting time on by having an out-of-date ubuntu-rtm/14.09 missing many bug fixes
[16:06] <cjwatson> (sorry I wasn't around earlier to let you know, since that would have been a much quicker fix)
[16:09] <john-mcaleely> slangasek, unknown when bug #1385656 appeared from my point of view - victor reported it over telegram this morning
[16:11] <john-mcaleely> rsalveti, ogra_ so following on from email, is 128 going to have the wifi power fix as well as the back out to adress bug #1385656
[16:11] <cjwatson> it's a thing I fixed last month in Ubuntu, but because Ubuntu RTM didn't have the new apt, the effort involved in persuading people that it should preemptively have the fixed packagekit was too much
[16:11] <ogra_> john-mcaleely, yes
[16:11] <john-mcaleely> ogra_, excellent
[16:11] <ogra_> cjwatson, right, we can do that next week
[16:11] <cjwatson> I would strongly recommend taking the new packagekit and un-reverting apt once you have a moment, to restore the security fix
[16:11] <ogra_> we just didnt want to leave the images broken til then
[16:11] <cjwatson> it shouldn't be necessary to reupload - we can just copy the security-fixed apt back in
[16:11] <cjwatson> (with some archive admin help)
[16:12] <john-mcaleely> sounds good
[16:14] <ogra_> cjwatson, well we kind of broke all processes with that revert ... if you feel like doing that while we're all in the air, please do
[16:14]  * ogra_ will be offline very soon
[16:14] <ogra_> (and ricardo already left)
[16:16] <cjwatson> Hm, I could fiddle with the ubuntu-rtm archive then get on a plane, that sounds good
[16:17] <cjwatson> I might do a bit later :)
[16:17] <ogra_> heh
[16:17]  * ogra_ crosses fingers
[16:17] <cjwatson> Though I can't really test anything
[16:18] <ogra_> i guess popey could help you out
[16:20] <cjwatson> And yeah, it's kind of entertaining that apt is tangentially involved in installing click packages; the work to give click its own dbus service will fix that
[16:20] <ogra_> well, packagekit is still linked against apt on the lib level, no ?
[16:21] <cjwatson> The aptcc backend is, yes
[16:21] <ogra_> eve with a click dbus service
[16:21] <ogra_> *even
[16:21] <cjwatson> But we wouldn't be using packagekit any more
[16:21] <ogra_> ah
[16:22] <cjwatson> It was always just an expedient thing to use to shorten the path to first implementation
[16:22] <cjwatson> And now that packagekit upstream is dropping plugin support in 1.0, we have to find an alternative anyway
[16:22] <ogra_> ah, i didnt know they would do that
[16:23] <ogra_> ok ... off to the airport
[16:23]  * ogra_ waves
[16:24] <cjwatson> have a safe trip
[16:24] <ogra_> you too
[16:33] <popey> cjwatson: happy to help... wassup?
[16:41] <cjwatson> popey: later maybe
[16:41] <cjwatson> no rush right now
[16:42] <popey> cjwatson: ok
[17:19] <imgbot> [17:19] <imgbot> [17:25] <ahayzen> clicks are installing again thanks folks :)


[06:13] <bob2> sounds like a terrible idea
[19:46] <sudarshans> is there any place where I can get a few tech specs of bazaar's repo format?
[19:47] <sudarshans> as in some idea of what system is used to store files (packs like git, or deltas or ...?)
[19:47] <sudarshans> looked around a bit, couldn't find any relevant info
[19:51] <sudarshans> basically do renames consume significant space?
[19:51] <sudarshans> and do similar files get automatically grouped together
[19:51] <sudarshans> so as to use deltas between them?
[19:55] <sudarshans> well?
[19:55] <sudarshans> lifeless: ^
[20:04] <sudarshans> https://answers.launchpad.net/bzr/+question/192935
[20:04] <sudarshans> hope that is the right place
[20:04] <sudarshans> good bye!


[14:02] <lamalex> kenvandine, is it possible to draw in an indicator, or are icons the only display method
[14:03] <lamalex> I guess I'm asking if my program has an open svg and wants to use librsvg or something to change color/etc can that changed svg be placed in the indicator applet?
[14:13] <lamalex> api looks like icons only
[14:34] <qense> lamalex: Do you mean Indicator Application?
[14:40] <vish> lamalex: i'm guessing you are referring to symbolic icons?
[14:40] <vish> if so , that is the plan for maverick , use a symbolic icon and allow the color to be changed on the fly
[14:40] <vish> depending on state of the indicator
[14:42] <lamalex> vish, do applications get to specify the color?
[14:42] <lamalex> is it possible to do more interesting things like fade from one color to another?
[14:43] <vish> lamalex: they would probably specific , warning/ok , like what has been done upstream , but the plan is for more states like pressed/active , and the colors will be specified in the icon themselves
[14:43] <lamalex> ah
[14:43] <vish> s/specific/specify
[14:44] <vish> lamalex: the "fade" is already being faked for the mute animation , i believe one icon is overlayed over the other
[14:45] <lamalex> ah, cool
[14:47] <vish> lamalex: what are ya planning? ;)
[14:48] <lamalex> vish, I wanted to mock up (in code) what I think the download indicator should behave like
[14:49] <vish>  cool!
[14:52] <lamalex> yeah! but im not sure if what I was planning is possible or not. it's all very easy with librsvg, but I don't think I have that benefit. I'll look at the sound indicator though and see how the fade is accomplished there
[14:52] <lamalex> basically I want to do fade + animation
[14:57] <vish> lamalex: animation also you can fake by using several icons , like the nm connection animation. [unless you are planning something toooo fancy ;) ]
[14:58] <lamalex> vish, basically just a pie that fills in radially, but moves in two directions and changes colors on events
[14:59] <vish> lamalex: yup , you can do that with icons
[15:00] <lamalex> cool beans, I'll play with it some and see what I can come up with
[19:25] <AnAnt> Hello, where can I find info about messaging indicator (menu) API ?
[19:26] <AnAnt> I don't find anything in the wiki


[06:03] <didrocks> good morning
[06:04] <happyaron> didrocks: morning, can you check the MIA request again? ;-)
[06:05] <happyaron> MIR... typo
[06:05] <didrocks> happyaron: hey! I guess you mean MIR? :)
[06:05] <didrocks> happyaron: will do, but probably tomorrow. I need to backlog on emails first
[06:05] <didrocks> (just back from vacations)
[06:05] <happyaron> great
[06:25] <ypwong> happyaron, you're early today :)
[06:28] <happyaron> ypwong: actually late today, 23:28 already.
[06:42] <seb128> good morning desktopers
[06:42] <seb128> happyaron, you are at debconf?
[06:45] <happyaron> seb128: yes
[06:46] <seb128> happyaron you are doing all conferences this summer ... :-)
[06:47] <happyaron> seb128: I agree, it's quite tiring to travel around...
[06:47] <seb128> happyaron, with all this drinking and partying as well, right? ;-)
[06:48] <happyaron> no, that only happens at that very place..
[06:48] <seb128> lol
[06:49] <happyaron> but yes, they've asked me to join them when I'm back to Beijing
[07:07] <pitti> bonjour didrocks ! oooh, tu es retour !
[07:07] <pitti> didrocks: as-tu eu des bonnes vacances ?
[07:07] <didrocks> Guten Morgen pitti! Long time no see :)
[07:08] <pitti> bonjour seb128
[07:08] <pitti> happyaron: hey, how are you?
[07:08] <didrocks> pitti: oui, les vacances étaient très bien (mais j'ai eu les épaules bloquées depuis une semaine :( )
[07:08] <didrocks> pitti: et toi ?
[07:08] <seb128> pitti, salut, ça va bien ?
[07:09] <pitti> didrocks: urgh, Julie's post looked like you were hanging out on beaches, not ruining your shoulder?
[07:09] <pitti> seb128: oui, merci ! et toi ?
[07:09] <happyaron> pitti: good, and you?
[07:09] <happyaron> :)
[07:09] <pitti> happyaron: quite fine, thanks
[07:10] <didrocks> pitti: we were, didn't prevent to probably endure some cold wind which hardened my muscles I guess :)
[07:12] <didrocks> pitti: how were your holidays btw?
[07:12] <pitti> didrocks: very quiet and relaxing; we mostly stayed at home as the weather was really bad
[07:12] <pitti> didrocks: so no paragliding :/
[07:13] <pitti> didrocks: but I enjoyed a week off anyway, I felt a looot better
[07:13] <didrocks> pitti: argh :/ yeah, it seems it was something general all over europe anyway this summer…
[07:13] <pitti> didrocks: and that friend of mine was still here, so we could hang out a bit
[07:13] <pitti> yeah, April and August just got swapped
[07:13] <didrocks> ah nice, that what worthes holidays: a change in habits/people around :)
[07:13] <didrocks> yep
[07:14] <didrocks> pitti: even in the south of France, which isn't Lyon, at the beach, the water temperature was between 18 and 20
[07:16] <pitti> didrocks: heh, yeah, with zero stress about planning, hotels, travel, etc. :)
[07:16] <didrocks> heh, indeed :)
[07:17] <didrocks> speaking of hotels, we finalized the booking for Japan! \o/
[07:17] <pitti> didrocks: instead, we tinkered around a bit to install a solid pole foot in the garden for hanging up a hammock
[07:17] <pitti> didrocks: ooh! quand avez-vous aller ?
[07:17] <pitti> "allez vous"
[07:18] <didrocks> pitti: ah, that's a nice plan (the hammock ;)), that's our only disappointment of "only" having a balcony
[07:18] <didrocks> pitti: du 27 septembre au 17 octobre
[07:19] <didrocks> we booked our flights a while back, but we didn't for the hotels until recently
[07:19] <didrocks> (as we needed to ensure the dates for every places we go to)
[07:19] <seb128> didrocks, all set then? ;-)
[07:20] <seb128> didrocks, seems like you should be able to come to the client week as well
[07:20] <didrocks> seb128: still the trains: we know which one to take and so on, but I would prefer that we look at their time schedule
[07:20] <seb128> k
[07:20] <didrocks> seb128: didn't see any official announcement, but yeah, from what I heard, that should be ok :)
[07:20] <didrocks> seb128: we already know what we are going to visit, per half a day
[07:20] <seb128> oh, pitti gets setting's mps now, nice ;-)
[07:21] <seb128> didrocks, great
[07:21] <pitti> seb128: yeah, and bugs; need to teach my .procmailrc about it :)
[07:22] <seb128> pitti, welcome on board, we can always use extra hands on settings ;-)
[07:23]  * pitti runs desperately :)
[07:23] <didrocks> oh, I don't see my ubuntu-developer-tools-center autopkgtests…
[07:23] <didrocks> probably I made something wrong
[07:24] <pitti> didrocks: no XS-Testsuite:
[07:24] <didrocks> ahah :)
[07:24] <pitti> didrocks: these days, dpkg-source adds it automatically
[07:24] <didrocks> yeah, so adt manual run works :p
[07:24] <pitti> but we only merged this like a week or two ago
[07:24] <didrocks> pitti: ok, will add, however, I need to check with you on running my medium tests (and why not large tests as well)
[07:24] <pitti> https://launchpad.net/ubuntu/+source/dpkg/1.17.13ubuntu1
[07:24] <didrocks> for medium, I need to be able to download a docker image
[07:25] <pitti> didrocks: nah, please just try a rebuild; the .dsc should then get it automatically
[07:25] <maxb> c
[07:25] <maxb> oops
[07:26] <didrocks> pitti: ok, will do that! do you think you will have time later this week for the medium tests?
[07:26] <pitti> didrocks: actually, it got into this version: https://launchpad.net/ubuntu/+source/dpkg/1.17.12ubuntu1
[07:26] <didrocks> nice that it's automated now :)
[07:26] <didrocks>   * Automatically add the Testsuite field in dpkg-source to the .dsc file.
[07:26] <pitti> didrocks: yeah, last weeks were a bit crazy, I didn't get to looking into the proxy issues; but with you being back to poke me, we can do that
[07:26] <didrocks> got it :)
[07:26] <didrocks> great!
[07:27] <didrocks> I'll need to find victims as well to run udtc on their machine :p
[07:27] <didrocks> machines*
[07:28]  * seb128 feels like didrocks he looking at him through IRC
[07:28] <pitti> and it worked!
[07:28] <didrocks> \o/
[07:29] <didrocks> I don't know any other i386 victim :p
[07:29] <pitti> /plugin load stare-down
[07:29] <pitti> ERROR: no such plugin
[07:29] <didrocks> ahah
[07:29] <pitti> didrocks: i3what? oh, those old 16 bit IBM PC thingies? :-)
[07:31]  * pitti has a flashback about DOS programming with page and offset addressing craziness
[07:31] <didrocks> hehe :)
[07:32] <seb128> youngers...
[07:32] <seb128> i386 ftw!
[07:36] <pitti> 6510 FTW!
[07:36] <didrocks> so feature freeze was last week, the MIR wasn't updated and the update submitted to mterry I guess (seeing what happyaron told me this morning)
[07:37]  * didrocks isn't assigned to the bug, so I would appreciate a link btw to when I'll look at it again
[07:37] <seb128> didrocks, yeah, mterry is just too busy with rtm
[07:38] <didrocks> so, we'll need a FFe I guess to seed it
[07:38] <darkxst> didrocks, hey, can you promote tracker?
[07:38] <seb128> didrocks, we decided to postpone the fcitx by default, even for Chinese, but we would still like to be able to build-depends indicator-keyboard and u-s-d with it to add support for fcitx users
[07:38] <seb128> even if we don't use it by default
[07:38] <seb128> so it allows opting in
[07:38] <seb128> but yeah
[07:38] <seb128> going to need a ffe
[07:38] <didrocks> darkxst: I need to recheck after doko's discussion on the bug after latest uploaded, so not today for sure (just back from holidays)
[07:38] <willcooke> morning dudes
[07:39] <seb128> hey willcooke
[07:39] <didrocks> darkxst: but can add that by EOW
[07:39] <didrocks> hey willcooke!
[07:39] <didrocks> seb128: ah, great then!
[07:39] <seb128> didrocks, that might also reduce the number of sources we need to MIR this cycle
[07:39] <seb128> like no need of engines and such
[07:40] <didrocks> seb128: so, the MIR doesn't cover them anymore?
[07:40] <didrocks> like, the bug was updated to state that clearly?
[07:40] <seb128> didrocks, I don't think so, we still want to MIR those next cyclm
[07:40] <seb128> the MIR is still valid
[07:40] <seb128> it's just an order of priorities
[07:40] <seb128> happyaron ^
[07:40] <darkxst> didrocks, ok thanks, I have temporarily disabled the few deps that were not in main
[07:41] <didrocks> happyaron: and please, reassign me one of the component, that's the way we ping/pong
[07:41] <didrocks> darkxst: yeah, I read that in between 2 huge pile of emails :) anyway, before EOW, I'll have a quick look
[07:42] <happyaron> didrocks: I have sent an reply for that MIR
[07:42] <happyaron> didrocks: isn't that sufficient?
[07:42] <didrocks> happyaron: didn't get it you didn't assigned me to one of the task once ready for me to rereview :)
[07:43] <darkxst> didrocks, ok thanks ;)
[07:45] <happyaron> didrocks: ok, assigned https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1356222
[07:45] <ubot2`> Ubuntu bug 1356222 in librime "[MIR] fcitx and related packages" [Undecided,Incomplete]
[07:45] <didrocks> happyaron: perfect, will get back to you! thanks :)
[07:45] <happyaron> thanks!
[08:25] <willcooke> ZOMG!  Glances is awesome!
[08:26]  * seb128 glances at willcooke
[08:26] <seb128> not an easy name to google for :p
[08:26] <willcooke> :D
[08:26] <willcooke> apt-get install glances
[08:26] <seb128> CLI, curses
[08:26] <seb128> nah
[08:26] <willcooke> :D
[08:26] <seb128> not that kind of geek ;-)
[08:27] <willcooke> pfft.  Amateur
[08:27] <seb128> hehe
[08:28] <seb128> installed it anyway to have a look, seems like a decent utility ;-)
[08:29] <willcooke> :D
[08:36] <willcooke> hey FJKong, 1:1 meeting today?
[08:36] <FJKong> willcooke: I am in meeting with NUDT, I will ping you some minutes later ok?
[08:36] <willcooke> sure thing
[08:36] <willcooke> thanks FJKong
[09:36] <FJKong> willcooke: ping
[09:37] <willcooke> hey FJKong
[09:37] <FJKong> meeting done
[09:37] <FJKong> willcooke: 1 1?
[09:37] <willcooke> yeah, let's do it FJKong
[09:37] <willcooke> I'll send you a hangout
[09:37] <FJKong> willcooke: ok
[10:09]  * didrocks goes for a run
[11:03] <larsu> pitti: hi! How do I set something like XDG_DATA_DIRS in a package test?
[11:04]  * larsu was wondering why his tests failed while building the package but not while doing make check
[11:05] <pitti> larsu: not sure I understand the question -- export XDG_DATA_DIRS= ... ?
[11:08] <larsu> pitti: I guess I'm asking for the best practice (I don't ususally deal with packaging)
[11:08] <pitti> larsu: you can set it in debian/rules, in override_dh_auto_test (or wherever you call the tests)
[11:09] <larsu> pitti: okay, that's what I would have done but it feels a bit hacky. Thanks!
[11:09] <pitti> larsu: yeah, it's a workaround for an upstream bug
[11:09] <pitti> the upstream tests should set the data dir itself if it's using some local data
[11:09] <larsu> ah, maybe I should do that then
[11:26] <seb128> larsu, was that the issue with the uitk error?
[11:27] <larsu> seb128: ya :(
[11:27] <seb128> hum, k, at least you figured it out!
[11:27] <larsu> I'm setting it manually now - even though it feels a bit odd to hard code it to /usr/share
[11:27] <larsu> qt is doing that even in production code when XDG_DATA_DIRS is empty or not set
[11:31] <larsu> seb128: got some early review comments in the process though
[11:31] <larsu> looks like this can get in very soon
[11:32] <seb128> great!
[11:32] <Sweetsha1k> moin all!
[11:32] <seb128> good morning Sweetsha1k
[11:32] <seb128> how are you?
[11:33] <Sweetsha1k> seb128: Im misnamed.
[11:33] <Sweetshark> this is better.
[11:33]  * ogra_ actually liked Sweet Schalk :)
[11:34] <Sweetshark> ... and I bring presents: http://people.canonical.com/~bjoern/utopic/4.3.1/libreoffice-l10n_4.3.1~rc2-0ubuntu1_source.changes and http://people.canonical.com/~bjoern/utopic/4.3.1/libreoffice_4.3.1~rc2-0ubuntu1_source.changes
[11:34] <Sweetshark> seb128: ^^ can you sponsor those to utopic?
[11:36] <Sweetshark> ogra_: Eating one clown for breakfast each day keeps the worries away.
[11:36] <seb128> Sweetshark, sure
[11:36] <ogra_> *omnomnomnom*
[13:10] <seb128> mterry, hey
[13:11] <mterry> seb128, hello!
[13:11] <seb128> mterry, sentence case is what johnlea/unity designers have been asked us to use consistently for some years
[13:11] <seb128> mterry, GNOME HIG was using "One Case By Word" style
[13:11] <mterry> seb128, I've been asking about freezes in #ubuntu-unity, you can see scrollback a bit
[13:11] <seb128> looking
[13:20] <seb128> kenvandine, hey
[13:20] <seb128> kenvandine, I sent some easy uss bugfixes, if you feel like doing trivial reviews ;-)
[14:58] <sabdfl> willcooke, seb128, wow
[14:58] <sabdfl> just updated my utopic desktop-next machine (XPS 27 touch screen All-in-One)
[14:58] <willcooke> sabdfl, you got the session bug fix via updates?
[14:58] <sabdfl> YEAH!
[14:58] <willcooke> ha, I was just about to ping you about that
[14:58] <sabdfl> what a blast
[14:58] <sabdfl> video worked in the browser!
[14:58] <willcooke> Its pretty sexy right!
[14:58] <sabdfl> yes it most certainly is
[14:59] <willcooke> My 6 year used U8 to open YouTube and watch videos full screen, no help needed
[14:59]  * sabdfl wants screencasts
[14:59] <sabdfl> isn't it interesting, i have Win8 on a similar machine right next door
[14:59] <willcooke> sabdfl, me and jorge are on it.  Blog post with pics & vids on its way
[14:59] <sabdfl> complete bafflement every time i go in there
[14:59] <sabdfl> nice
[14:59] <sabdfl> anyway, kudos to the guys i know it's a side side thread BUT it's very cool to see
[14:59] <sabdfl> and FAST
[15:00] <willcooke> Thanks sabdfl - I will be sure to pass on your comments to the whole team
[15:33] <seb128> sabdfl, nice! ;-)
[15:34] <sabdfl> seb128, yes, really exciting to see
[15:36] <seb128> indeed
[15:36] <BigWhale> Hello all.
[15:39] <BigWhale> Who's the go-to-guy for compiz/opengl/unity type of a question? I've implemented webcam support for Kazam and when webcam is enabled a window with webcam feed will open.  No matter what properties I set to it. :/
[15:40] <seb128> BigWhale, you can try to ask Trevinho or ChrisTownsend I think
[15:41] <BigWhale> seb128, thanks! Altho, I'm already pessimistic about it... :> It seems like it is a opengl thing.
[15:41] <seb128> yw!
[15:43] <didrocks> pitti: hum, so the autopkgtests are failing on adt, even if all tests pass for me (the coverage is the one expected at the small tests alone don't exercise the whole code, only small + large exercise 99% of it): https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-ubuntu-developer-tools-center/lastBuild/ARCH=i386,label=adt/console
[15:45] <mterry> seb128, you were right.  I asked Design and they said sentence capitalization is fine.  That's what I get for assuming they talk to each other  :)
[15:46] <didrocks> (actually, the % in nose-cov is wrong, if I run just a subpart of my tests, it's way higher)
[15:51] <seb128> mterry, ;-)
[15:51] <seb128> mterry, it's not "fine", it's "needed" :p
[15:51] <seb128> i.e that's what we use consistently
[15:52] <mterry> seb128, I just wish visuals from Design could be taken at face value.  Ah well
[15:52] <seb128> mterry, yeah, that would be nice
[15:52] <mterry> seb128, updated branch and commented as such
[15:52] <ChrisTownsend> BigWhale: So what I *think* is going on is that most fullscreen windows are unredirected meaning they have total control of the video buffer and hence have more performance.  When a window is unredirected, then it will be the only window displayed even if Always on Top is set for other windows.
[15:52] <seb128> too much turnoever in design team though
[15:52] <seb128> mterry, thanks
[15:53] <seb128> mterry, sorry for bouncy my "design should be frozen" complain in your direction btw, you are just the messenger there
[15:53] <mterry> seb128, it's a legitimate complaint for sure
[15:53] <ChrisTownsend> BigWhale: However, there is a whitelist in ccsm in which you can set fullscreen windows to not do this and it might allow Always on Top windows to show, but I'm not sure.
[15:53] <seb128> yeah, just not directory to the right person
[15:54] <ChrisTownsend> BigWhale: In ccsm->Composite->Unredirect Match, you can add another !(Class=x) for your fullscreen game and see if it helps.
[15:56]  * didrocks found what hackery was mocking coverage report wrong (even if that doesn't explain why adt says the tests failed when they didn't)
[15:56] <didrocks> well, it says the RET code is 0, testing locally is 0 though
[15:56] <didrocks> and no KO
[16:03] <didrocks> hum, got a fix, but that's weird…
[16:04] <didrocks> (for the coverage report)
[16:12] <seb128> attente_, hey, so I updated my system/restarted my session, fcitx forces qwerty when it starts (in a way that makes i-k not update, but I guess that's the missing signal issue we discussed)
[16:12] <seb128> same in session, if I quit fcitx, change to azerty, run fcitx I get put back to qwerty
[16:12] <didrocks> found a proper fix (still for the wrong coverage report, will wait for pitti for the adt failing)
[16:12] <attente_> seb128, are you by any chance using the setting "allow different sources for each window"?
[16:14] <seb128> attente_, no
[16:14] <seb128> attente_, using the first option "same for all windows"
[16:15] <attente_> seb128, but this problem is only happening initially when the session starts? or is it also happening when you open a new window?
[16:16] <seb128> attente_, it's happening constantly as long as fcitx is running
[16:17] <seb128> attente_, like I run fcitx, it goes to qwerty
[16:17] <seb128> I use i-k to pick fr back
[16:17] <seb128> I alt-tab to gedit
[16:17] <seb128> it's back to swerty
[16:17] <seb128> qwerty
[16:17] <seb128> so seems every time a win gets focus
[16:18] <seb128> attente_, fcitx doesn't have fr/azerty in its config
[16:18] <seb128> only qwerty and pinyin
[16:18] <attente_> i see
[16:18] <seb128> that could be the issue?
[16:18] <attente_> i guess you're using fr+oss?
[16:18] <seb128> yes
[16:20] <attente_> seb128, when you type is it azerty though?
[16:20] <attente_> or is it just a problem with what fcitx-qimpanel is showing?
[16:20] <seb128> ?
[16:21] <seb128> no, when I say "it changes to qwerty" I mean "when I hit z on my keyboard it gives me a w"
[16:21] <seb128> I'm not even sure I've qimpanel
[16:21] <seb128> I've the indicator that shows a keyboard icon but doesn't give indication of what is selected
[16:23] <attente_> seb128, can i get your 'gsettings get org.gnome.desktop.input-sources sources' please?
[16:24] <seb128> [('xkb', 'fr+oss'), ('xkb', 'gb'), ('ibus', 'pinyin'), ('fcitx', 'sunpinyin')]
[16:24] <seb128> attente_, ^
[16:26] <attente_> seb128, thanks, i see it
[16:27] <seb128> attente_, w
[16:27] <seb128> attente_, how/what did you change?
[16:27] <seb128> yw!
[16:27] <attente_> seb128, just that i see the problem now
[16:28] <seb128> k
[16:28] <seb128> let me know if you need more info or if you have a fix to test
[16:30] <tkamppeter> willcooke, hi
[16:31] <willcooke> hey tkamppeter
[16:34] <attente_> seb128, can you check your fcitx configuration under 'Global Config' -> 'Share State Among Window'?
[16:38] <attente_> i guess this problem is just because fcitx doesn't have that particular variant of fr+oss...
[16:44] <seb128> attente_, that combo is set to "No"
[16:48] <seb128> changing that combo doesn't make a difference there, even after restarting fcitx&co
[16:49] <attente_> yeah, i tried it with "All", but it still happens
[16:50] <attente_> which is counter-intuitive to me because i would think fcitx should stop changing the IM when the focused window changes
[16:52] <attente_> probably we should disable the fcitx-xkb module, but then i'm not sure how we would show the current keyboard layout in fcitx-qimpanel
[17:06] <attente_> bah, ok, i know what's wrong
[17:18] <happyaron> seb128: hey, can you help me check why ibus stuck in -proposed? is it only because freeze or there's anything else to deal with?
[17:18] <seb128> happyaron, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[17:18] <happyaron> ok, bookmarking the url
[17:19] <seb128> "Not touching package due to block request by freeze (contact #ubuntu-release if update is needed) "
[17:19] <happyaron> yup
[17:19] <seb128> it was probably blocked before that though
[17:19] <seb128> the freeze is not that old
[17:20] <seb128> but we don't have records of old reasons afaik, so we need for the freeze to lift to know what other issues there are
[17:22] <happyaron> ok
[17:37] <didrocks> ok, that's more than enough for today and fixed the coverage issue (77% for small tests alone, which makes more sense), see you tomorrow guys!
[18:09] <Sweetshark> seb128: still no utopic upload it seems. any blockers?
[18:09] <seb128> Sweetshark, I forgot sorry, doing it now
[18:11] <Sweetshark> seb128: np, thx ;)
[18:17] <BigWhale> ChrisTownsend, thanks for the info, I'll look into it.
[18:21] <seb128> Sweetshark, done


[00:01] <CarlFK> English
[00:03] <CarlFK> im trying to remove some of the manual steps from http://www.voxforge.org/home/dev/autoaudioseg "Step 2 - Add Missing Words ... [WINWARD] w ih n w er d
[00:07] <persia> CarlFK: Apparently not.  I thought maybe one of the speech synthesizer lexicons would have such a thing, but they are entirely phonemic, rather than having phonetic spellings.
[00:08] <persia> (Also, most aren't GPL: generally closer to ISC)
[00:09] <wgrant> Uh. Can I reject bug #240934, or do we support compilation on architectures that don't exist?
[00:09] <CarlFK> persia: yeah. but that may be ok.  apparently festival can do what is needed, but someone (me) needs to ... um.  make the output usable :)
[00:14] <persia> CarlFK: Right.  I've just dug a bit more: You can get (non-GPL) lists in festival-oald (oald-0.4.out) or festival-cmu (cmudict-04.out), depending on the pronunciation you prefer.
[00:16] <CarlFK> persia: thanks
[00:19] <emgent> heya people
[00:20] <YokoZar> jdong: can I poke you for a backport?
[00:21] <YokoZar> I've tested it :)  https://bugs.edge.launchpad.net/hardy-backports/+bug/240755
[00:26] <persia> motu-release: The DIF notice has been posted to u-d-a@ : could someone please send the related information re: the DIF exception process, etc.?
[00:27] <persia> (or tell me to do it, but I don't want to ursurp release planning activities)
[00:32] <cyberix> Where can I find a guide for splitting one source package into multiple binary packages?
[00:33] <persia> cyberix: http://wiki.debian.org/PkgSplit, but I found this confusingly Java-specific.
[00:34] <persia> cyberix: The general rules are 1) put the right names in debian/control, 2) use -p, -a, and -i in debhelper calls in debian/rules.
[00:35] <cyberix> What disturbs me most is that the two pieces of software probably share some files
[00:35] <cyberix> e.g. AUTHORS
[00:35] <cyberix> and maybe some documentation
[00:35] <persia> cyberix: AUTHORS doesn't typically belong in the binary package.  If you have shared docs, consider having a foo-doc package.
[00:36] <cyberix> Also, there are probably related things that I don't see currently
[00:37] <cyberix> It would be useful to get a list of typical problems
[00:38] <LinuxMonkey> anyone here know when the next packaging 101 is, cause trying to follow the guide I got lost.lol
[00:48] <persia> LinuxMonkey: What are you packaging, and where did you get lost?
[00:50] <LinuxMonkey> persia: well im trying to learn packaging, therefore following the guide at https://wiki.ubuntu.com/PackagingGuide/Complete and doing that hello thing. however someone first told me i needed to create a chroot and do everything from there, however someone else told me thats not the case so I guess im lost
[00:50] <LinuxMonkey> and the guide is not quite clear on that
[00:51] <persia> LinuxMonkey: There's no right answers in packaging.  Personally, I strongly recommend seeking a different goal than "to learn packaging".  Good goals might be "to package some application", "to fix some class of packaging bugs", or the like.
[00:51] <persia> Or rather, there are several, equally right answers (and there are some wrong answers).
[00:52] <persia> To address the need for a chroot specifically: if you are building something that can generate a source package using the tools in your current release, you may proceed without a chroot.  If you rely on tools in a different release to build the source package, you must do that in a chroot.
[00:54] <baron1984> is there anyone from the kernel team in here?
[00:55] <persia> baron1984: While there often is, #ubuntu-kernel is almost always a better place to ask about the kernel, as it then becomes on-topic.
[01:01] <LinuxMonkey> well persia i love the way you change the goals but  in fact they are the same goals I have however in order to "Package some application" "fix a bug and repackage" you infact need to learn packaging in a way. and thats what I want to do. im just following the advise of the WIKI to start with
[01:02] <persia> LinuxMonkey: I can see that argument, although the level of knowledge required to package one application or fix some class of bugs is not as high as is typically expected by those who claim to understand packaging :)
[01:02] <persia> So, what are you seeking to accomplish as a result of your study of the wiki?
[01:06] <LinuxMonkey> well I guess its whatever you guys want me to do really, untill i learn more, I was trying to follow the guides on the wiki but im starting to understand thats probably NOT the best way to aproach this, probably the best way is to get someone to show me how to do something and continously work on that type of stuff untill at ease with it and learn something else as I go along
[01:07] <baron1984> well, #ubunt-kernel is dead, can you guys at least tell me how to go about filing a suspend/resume bug?
[01:07] <baron1984> what kind of information is needed, etc
[01:09] <nxvl> if i have a source package inside another, do i need to the copyrights of them to the copyritght file or just mention there is this other package
[01:09] <persia> LinuxMonkey: I'd recommend working on bugfixes for a bit.  If you want packaging-specific bugfixes, trying to fix the packages that cannot install (apt-cache unmet -i) can be an interesting way to become familiar with debian/control
[01:10] <persia> nxvl: You need both copyrights.  Ideally you'll also complain to upstream about the extra security work involved in bundling embedded sources, and you won't have that problem anymore.
[01:12] <nxvl> persia: the embed source is gnulib
[01:12] <persia> nxvl: Ah.  Right.  You want to mention that in debian/copyright, and find a saner package then.
[01:12] <nxvl> persia: i have already talk with cjwatson and he told me it's better to keep it there than linking
[01:13] <nxvl> persia: but my question is: should i list the copyright under "Copyright:" or just mention it with it's license under "License:"
[01:13] <LinuxMonkey> persia: ok I wouldnt mind working on bug fixes, just dont know were to start. what to do. think of me as fresh meat, willing to do anything and learn what i need to do as long as u point me in right direction
[01:14] <persia> LinuxMonkey: Right.  Are there any bugs that you experience that irritate you?
[01:16] <LinuxMonkey> no not really persia the bugs ive encountered have been fixed really fast
[01:16] <persia> LinuxMonkey: OK.  Are there any packages that you use a lot and find especially useful?
[01:18] <LinuxMonkey> I dont use much mostly wine. lol as in windows wine
[01:19] <persia> LinuxMonkey: Hmm.  It's hard from that to tell what might interest you.  You might look through the bugs tagged "packaging" on launchpad, and see if you can find a good fix for one.
[01:26] <crimsun_> baron1984: https://wiki.ubuntu.com/DebuggingKernelSuspend
[01:50] <m-c> superm1: ping
[01:52] <emgent> argh.. I cant sleep
[01:53] <m-c> Micheal larabel from phoronix.com has been working on an interesting project.  Have you heard about it?
[01:55] <m-c> With the development of the open source drivers, from Intel, AMD, and Novell, there are reasons why people will want independent comparisons of open source graphic drivers.
[01:56] <m-c> Michael has created a GPL-based benchmark suite for testing these drivers against GPL-based benchmark programs.  I have tried this software out, and I can attest that it is worth incorporating into the next Ubuntu release.
[01:56] <m-c> Michael says he has discussed this with superm1 already, but so far I have not been able to contact him or see a write up in Launchpad.
[01:56] <persia> m-c: Does it have a needs-packaging bug?
[01:57] <baron1984> m-c: I'd kill for any kind of open source drivers, binary blobs are why you can't improve a distro without hosing people's video cards, etc.
[01:57] <persia> baron1984: Select different hardware :)
[01:57] <baron1984> Nvidia's drivers aren't entirely compatible with even Hardy, they just hacked their way around a lot of things
[01:57] <baron1984> and XRandr doesn't work well
[01:58] <baron1984> I'd take compatibility over a few more frames a second
[01:58] <m-c> I invited Michael to the channel.  Persia, is the next step to enter a need-packaging bug report?  If so, then I will get on it.
[01:59] <m-c> michaellarabel: hi
[01:59] <michaellarabel> Hi
[01:59] <persia> m-c: The best first step for any new package request is a needs-packaging request.  That is the list of software that is available to be packaged for those packaging things.
[02:00] <m-c> Right.  I understand.  Is there any information that might be needed from Michael while he is present, regarding license or other information?
[02:00] <persia> The next step would be for someone to claim the request, and build a candidate package for REVU.  It's also worth reviewing the Debian bugs against wnpp, and linking to any relevant RFP or ITP: if a package is going into Debian, it makes sense not to duplicate the work.
[02:01] <persia> I think a good needs-packaging bug contains the software name, the license, the homepage, and a brief description.
[02:01] <m-c> Would it be more applicable for this package to be entered upstream, into Debian?
[02:03] <m-c> Right, I can enter this into Debian first, then, with the information you specified.
[02:03] <persia> michaellarabel: If you are upstream for software that ought be included, there are some things that can be done in your release planning to make packaging easier: including the license in the root directory of the release tarball, providing versioned gzip-compressed tarballs for download (and maintaining the old version archive), and the like.  More suggestions are available from https://wiki.ubuntu.com/UpstreamGuide (althoug
[02:03] <persia> h this is incomplete).
[02:03] <m-c> Thank you for your advice.
[02:04] <michaellarabel> persia: License is already in root directory, the tarballs are versioned, and there is still an old version archive, etc. :)
[02:04] <persia> m-c: I can't say whether it belongs in Debian: depends on interest and utility.  If getting it in faster is a goal, it may be easier to put in Ubuntu now, as Ubuntu is unfrozen, and Debian is entering a release freeze.  Of course, this is a soft freeze, so it may not matter.
[02:05] <persia> michaellarabel: Excellent :)
[02:06] <m-c> My perception is that getting it into Ibex would be superb, with the AMD open source drivers coming to maturity at that time
[02:08] <nxvl> finally got it packaged!
[02:08] <michaellarabel> persia: Any other tips?
[02:09] <nxvl> persia: what was the process for revu, just upload and wait, or send an e-mail somewhere?
[02:10] <persia> michaellarabel: As upstream?  No.  As a potential packager?  I can point you at various guides, but need more information about what you need.
[02:10] <persia> nxvl: Upload, wait, and ask here on REVU days.
[02:10] <persia> You can also ask here once a day when it's not REVU day.
[02:10] <persia> nxvl: Also, if you've time, feel free to review others packages :)
[02:11] <nxvl> :D
[02:11] <nxvl> i will try
[02:12] <michaellarabel> persia: No other real questions... I just have never went through the Ubuntu/Debian package submission process before.
[02:12] <persia> michaellarabel: I'm not deeply familar with the Debian process, but the Ubuntu process is to use REVU.  Let's see if the bot has the link...
[02:13] <persia> !revu
[02:13] <nxvl> i am familiar with the debian one
[02:13] <nxvl> :D
[02:13]  * nxvl is NM
[02:14] <nxvl> for debian you need to be psicological prepared or have a friend
[02:14] <nxvl> :D
[02:14] <nxvl> they are evil
[02:14] <nxvl> :P
[02:14] <nxvl> you need to upload your package to mentors.debian.net
[02:17] <nxvl> and somewhere in mentor you have the info about the ITP Bug, mailling list and stuff
[02:35] <nixternal> oi oi
[02:48] <superm1> persia, yeah i offered to help provide some advice when a package is ready
[02:48] <superm1> and to look it over and such
[02:49] <superm1> if no one else was going to step up to package it in the next month or two i was going to take a look near the middle to end of summer at doing it
[02:49] <michaellarabel> superm1: Hi, yeah, m-c will probably submit that package to you then as he's offered to do it and has more time than me.
[02:49] <superm1> wonderful
[02:49] <superm1> time is a great thing to have :)
[02:49] <nixternal> time sucks!
[02:50] <superm1> hopefully i'll get around to giving it more of a thorough look and get you some more input on its functionality
[02:50] <michaellarabel> superm1: Great. What was the test/suite that had taken you all day to do? Did you get my email about that?
[02:51] <superm1> yeah i got the email about it, but  got swamped on other things so it's added to the "Todo"
[02:51] <michaellarabel> ok
[02:51] <superm1> when i get a chance to look again i'll just do universe
[02:51] <superm1> or universe-x
[02:51] <superm1> and go from there
[02:52] <michaellarabel> k
[03:26] <SpookyET> I keep getting this email http://pastie.org/217736
[03:27] <SpookyET> http://pastie.org/private/byvfyjge9ysotzfryinivq
[04:49] <nxvl> where can i find an explanation about what the sections means?
[04:50] <persia> nxvl: http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
[04:54] <nxvl> persia: yes, i'm reading that, but it only lists the sections
[04:54] <nxvl> well, they are pretty obvious
[04:55] <bimberi> nxvl: http://packages.debian.org/unstable/
[04:55] <persia> nxvl: Oh, you want an explanantion of each section?  Hmmm...
[04:56] <persia> nxvl: I don't know where the official source lives.  http://packages.debian.org/unstable/ has a nice overview of each of them.
[04:57]  * nxvl HUGS persia and bimberi
[04:57] <nxvl> :D
[04:57] <bimberi> :)
[05:51] <Zombie> Hello.
[05:51] <Zombie> I'd like some upgrade help. I have a Kubuntu Hardy CD and a Ubuntu DVD.  Irssi: Join to #ubuntu-motu was synced in 869472 secs
[06:00] <joejaxx> hahahahahahahaha
[06:00] <joejaxx> 10 days
[06:00] <joejaxx> that HAS to be a record
[06:00] <wgrant> Nice!
[06:01] <ajmitch> joejaxx: it's not unusual to have that
[06:01] <joejaxx> really?
[06:03] <ajmitch> nah, irssi has often done that for me in the past until I closed or /cycle'd windows that where out of sync after a disconnect
[06:03] <joejaxx> oh
[06:03] <joejaxx> that is unfortunate
[06:04] <ajmitch> usually if I was over the 20-channel limit & hadn't identified before irssi tried to rejoin them all
[06:06] <joejaxx> oh
[06:06] <joejaxx> sounds like me :D
[06:06] <lifeless> has anyone filed that irssi bug?
[06:06] <joejaxx> no
[06:06] <joejaxx> :P
[06:06] <joejaxx> i did not think of it
[06:07] <joejaxx> as i am in over 500 channels lol
[06:07] <ajmitch> yeah, that's just madness
[06:07] <joejaxx> so i thought it might just be my user case
[06:07] <joejaxx> :)
[06:15] <Zombie> I have a systemic question about where Ubuntu stores downloaded debs.
[06:15] <Zombie> Where does it store them.?
[06:17] <joejaxx> Zombie: /var/cache/apt/archives
[06:21] <wgrant> nixternal: Why does smb4k keep destroying /etc/sudoers?
[06:21] <wgrant> It has at least 4 separate instances of it in its bug history.
[06:21] <wgrant> This is probably a very bad thing.
[06:22] <ScottK> Adri2000 or Lutin: You might want to look at the current spamassassin on DaD.  debian/changelog is mssing all the Ubuntu entries.
[06:22] <ajmitch> wgrant: because it's an evil package that should be removed, given its potential for serious breakage?
[06:23] <wgrant> ajmitch: That's what I was thinking.
[06:23] <wgrant> Destroying once, maybe.
[06:23] <wgrant> But 4 separate bugs.
[06:23] <wgrant> Seriously.
[06:24] <ajmitch> looking at the bug for it, it must do some stupid things with that file
[06:25] <persia> Isn't there some policy statement about not touching conffiles from other packages?
[06:25] <wgrant> sudoers is a special case.
[06:25] <ajmitch> yes, don't do it in maintainer scripts
[06:25] <wgrant> Which is even more reason to *keep the $#*($#@ away from it*
[06:25] <ScottK> Ambitious maintainer is all it is ....
[06:26] <ajmitch> bug 238011 for those who want to cry
[06:26] <wgrant> Nothing else manages to eat config files - why something that touches sudoers?
[06:26] <wgrant> ajmitch: Ah, I apparently failed to paste that here earlier. Oops.
[06:29] <wgrant> I see that the first incarnation managed to stick some X error crap at the start.
[06:29] <wgrant> This is truly impressive.
[06:29] <wgrant> I'd like to know how it does it.
[06:30] <ajmitch> crossing the streams
[06:30] <wgrant> Hm?
[06:30] <ajmitch> never mind
[06:30] <persia> ajmitch: Yes :)
[06:30] <joejaxx> wgrant: possible movie reference :P
[06:30] <joejaxx> haha
[06:30] <joejaxx> :)
[06:30] <ajmitch> you're probably too young for that one :)
[06:31] <wgrant> Blah/
[06:31] <joejaxx> :P
[06:31]  * bimberi offers ajmitch a marshmallow ;p
[06:31] <ajmitch> heh
[06:31]  * StevenK chuckles
[06:39] <wgrant> I like the summary of bug #226722
[06:39] <wgrant> Fits a lot in.
[06:45] <LinuxMonkey> now thats funny
[06:46] <Ekushey> rofl
[06:52] <Zombie> Folks.
[06:52] <Zombie> You people need to add an option for CD and DVD based upgrades.
[06:52] <Zombie> I can't get my system to do that
[06:52] <persia> Zombie: It should be present (and this still isn't a support channel).
[06:53]  * persia thinks the "upgrade from CD" function was added in edgy
[06:53] <joejaxx> yeah
[06:53] <joejaxx> that should be on the optical media
[06:54] <wgrant> Zombie: You should be in #ubuntu. Make sure that you're not trying to use a desktop CD.
[07:04] <Ekushey> what do i need to do to be able to upload to REVU? i already joined the LP revu-uploaders team
[07:05] <wgrant> Ekushey: You need to request that the REVU keyring be synced.
[07:05] <wgrant> I really must improve that process one day.
[07:06] <Ekushey> wgrant, are you in charge?
[07:06] <wgrant> Ekushey: I have the power.
[07:06] <wgrant> It is now running, but will take several minutes.
[07:07] <persia> wgrant: Back to a cron job?
[07:07] <Ekushey> wgrant, my LP ID is russell.john
[07:07]  * persia tries to remember why the cron job was cancelled
[07:07] <wgrant> persia: I was thinking that a minimal version of the sync - that is, picking up only new keys - could run immediately before the upload processor each time.
[07:07] <wgrant> And refresh all keys once a day
[07:08] <\sh> moins
[07:08] <wgrant> Hey \sh.
[07:08] <wgrant> Ekushey: So you'll be quite close to the end.
[07:08] <persia> wgrant: That sounds complete, but I remember something going wrong and the keyring being corrupt back on the original sparky.  Maybe my memory is faulty.  Maybe the new infrastructure is sufficiently better.
[07:12] <Ekushey> wgrant, so i can try uploading tomorrow?
[07:13] <wgrant> Ekushey: Give it another couple of minutes...
[07:13] <Ekushey> so fast? wow :)
[07:13] <wgrant> It is done.
[07:14] <wgrant> Upload now - your upload should be on REVU in about 6 minutes.
[07:14] <Ekushey> great, thanks wgrant!
[07:16] <Ekushey> i'll do it at night from home
[07:17] <Ekushey> i've question one question, why isn't flock available on the repo? what's wrong with it?
[07:17] <jussi01> its closed source?
[07:18] <Ekushey> is it? isn't it based on firefox?
[07:21]  * jussi01 cant find source anywhere...
[07:21] <LinuxMonkey> i found the source
[07:22] <LinuxMonkey> http://downloads.flock.com/index.php?product=flock-source-current&os=linux
[07:22] <Ekushey> it's licensed under MPL / LGPL dual license
[07:22]  * jussi01 must be going blind...
[07:23] <LinuxMonkey> jussi01: just tired
[07:23] <Ekushey> so there must be some other reason why it's not available on ubuntu
[07:23] <jussi01> LinuxMonkey: havent woken up yet...
[07:23] <jussi01> Ekushey: hasnt been done yet?
[07:23] <LinuxMonkey> its 2:32am and i havent gone to bed yet
[07:25] <Ekushey> no clue... is there a way to find out if someone is packaging it or not?
[07:25] <persia> Ekushey: Look for a needs-packaging bug on launchpad, or an RFP/ITP bug in the BTS.  These are the means by which people request/announce packaging
[07:26] <Ekushey> ok persia
[07:27] <jussi01> LinuxMonkey: its 9.27 am, im not awake yet
[07:32] <dholbach> good morning
[07:34] <LinuxMonkey> morning dholbach were either so tired were not responding (my case) or not awake yet (everyone else)
[07:35] <dholbach> LinuxMonkey: bed time then? :)
[07:35] <LinuxMonkey> yeah another 25 minutes or so. its only 3:35am anyways
[07:36] <dholbach> that's OK then ;-)
[08:55] <emgent> morning
[09:18] <huats> morning dear motu world
[09:29] <RAOF> Howdie.
[09:35] <RAOF> bigon: I'm looking at telepathy-butterfly (because miro's blocked).  It seems that the Ubuntu divergence (don't pull in python-ctypes, which introduces an unnecessary 2.4 dependency) should go back to Debian.  Would you like me to file a bug in the BTS?
[09:35]  * persia is amused at the complaint that courier-imap is too new.  Usually it's about things being outdated.
[09:35] <RAOF> Someone's merged it from the future :)
[09:36] <persia> Perhaps the idea is to get the average version to some ideal...
[09:36] <RAOF> Hm.  Awkward.  subversion FTBFS, and libsvn-perl is uninstallable.
[09:37] <persia> RAOF: It's part of the master plan to get everyone to go back to RCS
[09:37] <RAOF> svn-buildpackage ain't gonna be working for me in the immediate future.
[09:37] <wgrant> persia: Shingle version control!
[09:38] <RAOF> Ah.  Subversion needs a merge, apparently.
[09:38] <persia> wgrant: I'm not sure I trust those newfangled things.
[10:18] <bigon> RAOF, fixed in the tp-butterfly bzr branch
[10:21] <Adri2000> ScottK: yes, base version (3.2.4-2
[10:21] <Adri2000> err
[10:22] <Adri2000> ScottK: ) not available on snapshot.d.n, so empty patches and broken merge
[10:51] <RicardoPerez> can any MOTU member apply the patch in bug #222038?
[10:52] <james_w> hi askand
[10:52] <askand>  james_w:  hi
[10:53] <james_w> would you like to look at http://merges.ubuntu.com/universe.html and see if there are any packages on there you are familiar with/use/like the sound of?
[10:56] <askand> james_w: quite a lot..but i like the sound of freetennis for example :P
[10:56] <james_w> cool, so look at what name is next to the package, as we need to make sure that they are not currently working on it.
[10:57] <james_w> unfortunately I don't know who that person is, I was hoping they would be on IRC so that we could get a quick answer.
[10:59] <askand> Oh
[10:59] <james_w> would you like to pick another so that we can go ahead and do one, and once we've done that you can proceed with freetennis?
[10:59] <james_w> I don't think there would be any problem in merging this one as the person doesn't seem to be very active.
[10:59] <james_w> Does anyone know William Lima?
[11:00] <askand> he doesnt seem to be very active according to launchpad
[11:02] <james_w> ok, let's go ahead and do it
[11:03] <james_w> if you click the name of the package then you will be taken to a page named REPORT that tells you a bit about what's going on.
[11:04] <james_w> let me know once you've read the page, and if there is something that you don't understand.
[11:04] <TheMuso> Who wants to join me cleaning the sponsors queue somewhat?
[11:05] <james_w> hi TheMuso
[11:05] <TheMuso> Hey james_w.
[11:06] <dholbach> TheMuso: I already did a few and plan to do some more
[11:07]  * directhex is finally working on an actual universe package, rather than main or debian
[11:09] <askand> james_w: looks pretty clear to me
[11:09] <TheMuso> dholbach: Right, I'm going to clear some as well, since DIF is so close.
[11:10] <james_w> askand: cool, so in this case as it failed to merge cleanly there is a tarball with the results
[11:10] <james_w> askand: if you remove the "REPORT" from the end of the URL you will find the files. Please download and extract the tarball
[11:10] <james_w> (not the .orig.tar.gz one)
[11:10] <dholbach> TheMuso: right - let's chat in here and say which ones we're looking at - so we don't look both at the same :)
[11:11]  * dholbach looks at xmms2
[11:11]  * TheMuso has a lock on spread
[11:11]  * sebner waves
[11:12] <dholbach> hi sebner
[11:12] <sebner> can anybody tell me when a nvidia-glx update is planned (support for 2.6.26 kernel)
[11:12] <askand> james_w: ok downloaded and extracted the ubuntu.src.tar.gz one
[11:12] <dholbach> sebner: best to ask in #ubuntu-kernel or #ubuntu-x
[11:13] <james_w> askand: cool, so if you go back to the REPORT file you will see a list of conflicted files, we need to sort those out.
[11:13] <sebner> dholbach: cool, thanks =) though 800*600 isn't that bad since this forces me to learn :P
[11:13] <james_w> askand: the first is debian/control, so please open that in a text editor.
[11:15] <directhex> sebner, in intrepid, or generally?
[11:15] <james_w> askand: you will see that on the Ubuntu side we just changed the Maintainer as normal. On the Debian side they changed maintainer as well, but also updated the Build-Depends, and added some more information.
[11:15] <sebner> directhex: intrepid since there we have a new kernel =)
[11:15] <james_w> askand: we want all of Debian's changes, but we want to modify the maintainer field as well.
[11:16] <james_w> askand: but ensure that the "Original-Maintainer:" refers to the new Debian Maintainer.
[11:16] <james_w> askand: got it?
[11:16]  * TheMuso takes a lock on zsnes.
[11:18] <askand> james_w: hm..how do I ensure that the original-maintainer (bart martens) refers to the new debian maintainer?
[11:19] <gnomefreak> What is the name of the hardy-backports team that you use when a bug needs to be backported?
[11:19] <james_w> askand: the line you leave as "XSBC-Original-Maintainer:" should be "XSBC-Original-Maintainer: Debian OCaml Maintainers<EMAIL_ADDRESS>rather than "XSBC-Original-Maintainer: Bart Martens<EMAIL_ADDRESS>[11:20] <james_w> askand: as this line refers to the Debian maintainer, which has changed, so we need to make sure we get the right one.
[11:20] <askand> ah ok got it
[11:21]  * dholbach looks at gtkglarea
[11:21] <askand> james_w:  and I should also change the build-deps ?
[11:22] <james_w> askand: you should probably go with what Debian has.
[11:23] <askand>  james_w: yes
[11:23] <james_w> askand: if you look at the last two Ubuntu entries in debian/changelog you can see if Ubuntu changed them, in which case you should look in to it a bit more.
[11:23] <james_w> http://merges.ubuntu.com/f/freetennis/freetennis_0.4.8-3ubuntu2.patch
[11:23] <james_w> that's the Ubuntu changes, and you can see that the Build-Depends weren't modified, so you can just take what Debian has.
[11:25] <askand>  james_w: ok done
[11:25] <james_w> askand: great, so save that file and we can move on to the next one.
[11:25] <rzr> hi
[11:25] <james_w> askand: feel free to stick anything in a pastebin if you would like me to glance over it.
[11:26] <james_w> askand: the next file is debian/freetennis.8, which is the manpage.
[11:26] <askand> james_w:  should I also add homepagefield ?
[11:26] <james_w> askand: looking at the changelogs both sides improved the file, so this may be easy or difficult.
[11:26] <rzr> As a debian maintainer I am about to release a package which closes some ubuntu bugs, should I also add (LP:#xyz) in debian/control ?
[11:26] <rzr> then the debian package will just need to be imported
[11:27] <james_w> askand: yup, that's useful to have.
[11:27] <james_w> askand: when merging you want to follow Debian as closely as possible, just sticking with Ubuntu changes where there is good reason to.
[11:28]  * dholbach takes a look at tkdiff
[11:29] <askand> james_w: how does this look? http://pastebin.com/m38d07c00
[11:30] <james_w> askand: good, we also want the Uploaders line
[11:30] <james_w> askand: and you need to delete the conflict markers and the Debian section.
[11:31] <askand> james_w: http://pastebin.com/m7b881a22 not sure what the <<<<<<<<< is?
[11:32]  * dholbach takes a look at libofx
[11:32] <james_w> askand: that's one of the conflict markers. They are just there to denote the areas which need some attention. When you are done you need to delete them.
[11:33] <Laney> askand, james_w: If you're trying to merge freetennis, you should be aware of bug #241249
[11:33] <james_w> Laney: thanks
[11:34] <james_w> askand: sorry, that should of course be the first step, check to see if the work has already been done. In this case it has, sorry.
[11:34]  * rzr waves _o/
[11:34] <askand> james_w:  oh
[11:35] <TheMuso> dholbach: I'm still here, I'm just being careful with a somewhat hackish change in zsnes. :)
[11:35] <james_w> though in this case it apparently happened concurrently, so there was little we could have done.
[11:35] <dholbach> TheMuso: I didn't think you had vanished :)
[11:35] <directhex> dholbach, can never have too many mono merges
[11:35] <dholbach> Mr TheMuso-vich :)
[11:36] <dholbach> directhex: hm?
[11:36] <TheMuso> dholbach: har har har. That still makes me laugh.
[11:36] <james_w> askand: in this case Debian adopted our changes, so we can take their package directly, which is what it means by "sync".
[11:36] <james_w> askand: sorry about that. If you like we can look at another package.
[11:36] <directhex> dholbach, LP:240671
[11:36] <dholbach> bug 240671
[11:36] <dholbach> directhex: what about it?
[11:37] <directhex> dholbach, just commenting. it's the second merge in a couple of weeks, and i wouldn't be surprised if there were more, when more bugs appear
[11:37] <dholbach> right
[11:38] <dholbach> I don't know any mono at all, that's why I asked slomo to take a look at it
[11:38] <rzr> vorian: around ?
[11:38]  * dholbach takes a look at xgrep
[11:39] <RAOF> bigon: Cool; that'll be syncable then.
[11:43]  * TheMuso takes a look at ming
[11:44] <nixternal> wgrant: dunno why it is still doing that...file a bug upstream on that please
[11:44] <nixternal> for smb4k that is
[11:48] <askand> james_w: no worries :) i think I come back later a bit
[11:48] <james_w> askand: great.
[11:49]  * TheMuso looks at paprefs.
[11:50]  * dholbach lunches
[11:52] <rzr> I guess I have to RTFM again :)
[11:52] <rzr> As a debian maintainer I am about to release a package which closes some ubuntu bugs, should I also add (LP:#xyz) in debian/control when possible?
[11:54] <directhex> ooh, that'd be nice
[11:56] <rzr> i cant find this info on the wiki
[11:57] <rzr> let's ommit them then
[12:00]  * TheMuso looks at extace
[12:06] <RAOF> rzr: You're very welcome to add LP:#xyz tags.  To debian/changelog (that's what you meant, right?).  The syntax is exactly the same as for the BTS, but with "LP: #" rather than "closes: #".
[12:06] <rzr> no my question  was
[12:06] <rzr> can I mix Closes:# and LP:# on the same release ?
[12:07] <RAOF> Yes, absolutely.
[12:07] <rzr> are you sure ?
[12:07] <RAOF> The BTS understands closes: and ignores LP:, launchpad understands LP: and ignores closes:
[12:07] <directhex> which is why LP uses LP: and not closes:
[12:07] <rzr> but debian doesnt care about derived distro bug trackers
[12:08] <rzr> so this info is useless to debian
[12:08] <RAOF> That's right.
[12:08] <rzr> well I wanted to make sure
[12:08] <RAOF> It would be nice if you added them, but you're certainly not expected or obligated to do so :)
[12:08] <rzr> I see benefits and drawbacks :)
[12:09] <rzr> polution vs factorisation
[12:10] <rzr> let's add both then
[12:11] <RAOF> Very good of you, thanks :).
[12:14] <rzr> thank you RAOF , now Let's open a debian specific help desk for copperation
[12:19]  * TheMuso looks at guidedog
[12:27]  * TheMuso looks at rpld
[12:29] <RAOF> rzr: You mean, the Ubuntu version of the Debian utnubu team? :)
[12:30] <rzr> we'll call it the naibed team
[12:32]  * TheMuso looks at apcalc
[12:32] <RAOF> That's got a bit of a ring to it.
[12:32] <Hobbsee> 238 outstanding.  ouch
[12:34] <TheMuso> Hobbsee: Yeah, clearing the sponsors queue will help get that down somewhat.
[12:53] <afflux> siretart: hi... I have some questions about the cryptsetup initramfs script
[12:53] <afflux> siretart: first thing is, I wonder why we don't use udev_settle anymore, and do a "normal" 3-minute sleep
[12:56] <afflux> siretart: second thing is, the break condition in this sleep waits for ${ROOT}, which is the "resulting" device, instead of the cryptsource. I think this is why the sleep does not work for me (on my system, it just hangs. looking at the source, it should be working after 3 minutes though, because the panic condition some lines later checks for $cryptsource again).
[12:57] <wgrant> Has anybody upgraded to Intrepid recently? Am I likely to be condemning my system to a fiery death if I try it now?
[12:57] <jpds> wgrant: Hobbsee has.
[12:58] <afflux> siretart: third thing is, after manually changing the initramfs script  I found out that neither /sbin/cryptsetup nor /lib/cryptsetup/askpass exist. both are referred to from the script.
[12:58] <afflux> wgrant: it works quite well on my desktop machine, currently, except the cryptroot I mentioned above ;)
[12:59] <Hobbsee> wgrant: no, it should be reasonable.  i'd be interested to see if your mime types bugger up though
[12:59] <wgrant> Hobbsee: We shall see, though I don't use anything that uses mimetypes.
[12:59]  * wgrant stopped using cryptroot a while ago.
[12:59] <Hobbsee> wgrant: right, so you don't use nautilus.
[12:59] <siretart> afflux: yeah, I noticed that my merge isn't correct yet. I'm still at setting up a kvm instance for testing
[13:00] <afflux> siretart: it looks like I have a quick solution for the third thing
[13:00] <Hobbsee> wgrant: no matter what you double click on, it'll load in whatever the last program you set was.
[13:00] <siretart> afflux: AFAIC, even in hardy plain crypted partitions seem to be somehwat broken. I see that when I'm trying to manually set them up (read: without d-i)
[13:00] <Hobbsee> at least, that's what i'm finding
[13:01] <siretart> afflux: are you famillar with bzr? - if yes please fix that in a branch. that makes it easier for me to review, okay?
[13:01] <afflux> yup okay
[13:01] <afflux> siretart: udev_settle or (fixed) manual waiting?
[13:02] <afflux> where manual waiting is "check for partition every 100ms"
[13:03] <siretart> sorry?
[13:06] <afflux> siretart: we have two ways to wait for the cryptsource, if it didn't appear yet. We used to use "udevadm settle --timeout=30" in hardy, but changed to do a 180*100ms sleep
[13:07] <siretart> afflux: I think the loop is the only reliable way to go.
[13:07] <afflux> okay
[13:07] <siretart> afflux: because udevsettle only helps if the kernel is currently processing an event which might cause the device to pop up
[13:08] <afflux> I see
[13:08] <siretart> afflux: if you have a very slow device, like an pendrive or slow scsi device that needs intensive initialisiation, udev_settle wont help you
[13:08] <afflux> siretart: which branch should I use for branching? ~siretart/cryptsetup/ubuntu or ~ubuntu-core-dev/cryptsetup/ubuntu
[13:08] <siretart> the one with the latest commit. I think it is the latter one
[13:08] <afflux> okay thanks
[13:11] <vorian> rzr, I am now
[13:18] <siretart> afflux: btw, if you think you think you fixed a bug in a bzr commit, do a 'bzr commit --fixes lp:12345' with the correct bugnumber. lp will automatically associate your branch with the bug
[13:18] <afflux> oh okay, nice to know, thanks
[13:24] <ffm> Hey, I'm a bit bored. How can I search through needs-packaging requests?
[13:26] <wgrant> ffm: Just do an advanced search for the needs-packaging tag at https://bugs.launchpad.net/ubuntu/+bugs?advanced=1
[13:27] <ffm> wgrant: thanks.
[13:31] <dholbach> TheMuso is doing AWESOME work in the sponsoring queue
[13:31] <dholbach> let's join him!
[13:31] <emgent> rheya dholbach :)
[13:32]  * Laney highfives TheMuso
[13:32] <Laney> Thanks for the uploads :D
[13:32] <TheMuso> dholbach: No longer unfrotunately, I'm starting to find it hard to concentrate, as its getting late  here, so I'll have to call it a night, but will attempt to find time tomorrw to do some more.
[13:32] <TheMuso> gah as evident by my typing. :p
[13:32] <dholbach> TheMuso: I'll do some myself - who else is interested?
[13:33]  * Laney is going to carry on giving you stuff to sponsor ;)
[13:40]  * dholbach checks out sdlmame
[13:42]  * DktrKranz did 5/6 earlier, will do more this evening
[13:42] <dholbach> woohoo
[13:42] <dholbach> thanks DktrKranz
[13:42]  * dholbach high-fives DktrKranz and TheMuso
[13:43]  * DktrKranz high-five-a-day dholbach
[13:43] <dholbach> hehe
[13:51] <ScottK> DktrKranz: Are you an avscan user or were you just triaging in general when you marked up an avscan bug earlier today.
[13:52] <DktrKranz> ScottK: just triaging.
[13:53] <ScottK> OK.
[13:53]  * ScottK was hoping for someone to package a new upstream.
[13:53] <DktrKranz> IIRC, I subscribed (or assigned) to a bug, feel free to take it if you want to.
[13:54]  * dholbach takes a look at keurocalc-kde4
[13:54] <afflux> siretart: my branch is https://code.launchpad.net/~afflux/cryptsetup/ubuntu.initramfs-fixes . The latest changes are not tested yet, I'll do that now.
[13:54] <DktrKranz> ScottK: myon put it into adoption (or orphaned it), it could be interesting to take maintainership.
[13:55] <ScottK> Yes.  I'm hoping someone will do that.
[13:55]  * ScottK doesn't use it either, but it's a clamav rdepend and currently FTBFS in Intrepid needing the new version.
[13:59] <siretart> afflux: yes, your commits look pretty relevant. will merge them!
[14:02] <afflux> siretart: okay, worked. Only thing is: when not using usplash I get two warnings about not being able to run /sbin/udevsettle because it does not exist. They don't seem to be critical (for me?) though. I also get the message described in bug 151532. But, as the initial reporter states too, the system boots up without any further problems.
[14:02] <DktrKranz> ScottK: if you need it, I can have a look at it, maintaining packages is fine, especially if they are needed by others
[14:03] <ScottK> DktrKranz: I've played with it in testing a bit and it looks like a reasonably decent anti-virus frontend.  I think it's worth keeping.
[14:04] <ScottK> If you want to adopt it in Debian, I know who I could get to sponsor you.
[14:04] <DktrKranz> myon directly?
[14:04] <ScottK> Actually I was thinking sgran (the clamav maintainer).
[14:04] <DktrKranz> I haven't a fixex sponsor
[14:05] <ScottK> He's been decent about sponsoring clamav related NMUs for me.
[14:06] <DktrKranz> I can give it a try, I need to understand package logic before, since I'm not a user, it could be harder
[14:07] <ScottK> It seems reasonably well designed.
[14:08] <ScottK> When I was trying to get clamav 0.92 back to Dapper avscan was a tough one.
[14:09] <DktrKranz> any particular issues?
[14:09] <siretart> afflux: cool. thanks for your commits, I'll merge them into the next upload!
[14:09] <ScottK> I ended up taking the Feisty package, using the Dapper debian/rules, grabbing one file that had the libclamav interfaces out of the avscan internals of the hardy package, slamming them all together and it worked.
[14:10] <ScottK> I couldn't backport the entire Hardy package due to other dependency issues.
[14:10] <DktrKranz> mh... sounds complex
[14:10] <ScottK> In any case that fact that that worked suggest to me a reasonably well designed program with good stable internals.
[14:10] <ScottK> That was complex., but it was a one time problem.
[14:11] <ScottK> The biggest issue with it is it'll need watching as clamav evolves as they have a habit of doing interface changes with no warning.
[14:11] <ScottK> avscan upstream seems responsive to it though.
[14:12] <DktrKranz> are they linked or follow a separate development plan?
[14:13] <ScottK> Separate.  avscan is a user of libclamav.
[14:15] <ScottK> DktrKranz: Why don't you look at what it'd take to get the new avscan packaged and see how comfortable you are with it.
[14:16] <ScottK> DktrKranz: If you need to build against the new clamav on Hardy, it's in the ubuntu-clamav PPA: https://launchpad.net/~ubuntu-clamav/+archive
[14:16] <DktrKranz> I was thinking about it, since we want clamav and no-one jump in to take responsibility in Debian so fare
[14:17] <ScottK> Currently we have 3 A/V gui packages: Klamav, Clamtk, and Avscan.
[14:18] <ScottK> Klamav is very KDE focused.  Clamtk is somewhat limited.  I think having Avscan is useful.
[14:18] <ScottK> It's still under development, so it may well end up being the best of them.
[14:19] <DktrKranz> Avscan is for GNOME, I suppose
[14:19] <DktrKranz> gtk+1.2, wasn't it being removed from Debian?
[14:22] <ScottK> Ah.  That was the other problem.
[14:22] <ScottK> I knew there was something.
[14:22] <ScottK> Who knows, maybe the new version is updated ...
[14:23] <DktrKranz> let's see
[14:23] <ScottK> If not, it'd still be useful to get it updated in Ubuntu so eventually I can backport clamav 0.93 and later.
[14:24] <DktrKranz> looking at myon's comments, new version requires new endeavour, and SONAME handling seems problematic
[14:25] <wgrant> ScottK: Have you not yet managed to convince upstream to be less distro-hostile?
[14:25] <ScottK> So it's a 'learning experience'.
[14:25] <ScottK> wgrant: No.
[14:26] <ScottK> I've asked them to add some Ubuntu specific info to their web site just yesterday.  We'll see how that goes.
[14:26] <DktrKranz> mh... avscan homepage is unreachable
[14:26] <ScottK> That's not a good sign.
[14:28] <ScottK> I can get to it.  It's just pretty empty.
[14:29] <ScottK> Sorry.  Wrong page.
[14:29] <DktrKranz> I get 404
[14:30]  * ScottK too.
[14:32] <cyberix> I have a package in Hardy. The upstream has released a new release. Should I create a huge debdiff and try to get that applied for intrepid or what?
[14:32] <cyberix> i.e. are debdiffs the right tool for all package upgrades?
[14:33] <LucidFox> cyberix> Only within the same upstream version
[14:33] <LucidFox> for a new upstream version, attach the diff.gz
[14:34] <cyberix> LucidFox: Should that contain both packaging and upstream changes or only upstream changes?
[14:34] <LucidFox> Erm... it should contain only packaging changes
[14:34] <LucidFox> diff.gzs by definition contain only packaging changes
[14:39] <cyberix> LucidFox: So how do I get the upstream tar ball updated?
[14:39] <LucidFox> cyberix> The sponsor will download it
[14:39] <LucidFox> and your diff.gz
[14:39] <directhex> (try using uupdate, it's made for this kind of thing)
[14:43] <cyberix> The new upstream release goes throught revu?
[14:44] <LucidFox> cyberix> No.
[14:44] <LucidFox> REVU is only for new packages.
[14:44] <LucidFox> cyberix> You file a bug report on LP, attach the diff.gz and subscribe ubuntu-universe-sponsors.
[14:49] <cyberix> LucidFox: And how do the sponsor know he should get the new upstream tar ball?
[14:49] <persia> cyberix: debian/watch or debian/rules get-orig-source :)
[14:51] <cyberix> And if I'm not aware of the new upstream release, then things will break.
[16:04] <ivoks> motu wannabes?
[16:04] <ivoks> there's one very simple task if someone is interested
[16:05] <persia> ivoks: We try not to use that term :)  What's the task?
[16:05]  * santiago-ve rises hand but is at work ATM
[16:05] <ivoks> there's wifi-radar package in ubuntu
[16:05] <ivoks> it is very old and i'm an official maintainer
[16:05] <ivoks> it's time to drop it and merge debian's package
[16:06] <ivoks> there are only two patches that should be applied to new debian package
[16:06] <ivoks> it's dpatch system, IIRC
[16:06] <ivoks> so, low hanging fruit
[16:06] <ivoks> if no one is interested, i'll do it, but it looks like good exercise...
[16:06] <vorian> ivoks: I requested a sync with bug #240809 for wifi radar
[16:07] <ivoks> vorian: right, wifi-radar was packaged for ubuntu first, and then for debian, so weare out of sync for a very long time; it's time to move on and drop our package
[16:07] <vorian> ah, good good
[16:08] <ivoks> santiago-ve: interested?
[16:08] <santiago-ve> ivoks: aye, but werrr not for now... at work atm :p
[16:08] <dholbach> ivoks: vorian requested a sync - is a merge necessary?
[16:09] <ivoks> dholbach: there is one GUI related patch
[16:09] <ivoks> and one for atheros cards... i don't have atheros, so i can't tell if it's needed any more
[16:09] <dholbach> right
[16:09] <vorian> hmm
[16:10] <ivoks> blaa.... just sync it and move on... just one note
[16:10] <ivoks> last time i checked debian's package, it asked questions during install
[16:10] <ivoks> and it didn't have daemon
[16:10] <ivoks> while ubuntu package didn't ask questions and had daemon for auto-connecting
[16:13] <ivoks> you are free to decide, i don't mind any of those two options
[16:54] <siretart> afflux: I just uploaded your changes to intrepid. thanks for your commits, and keep up your good work! :)
[16:54] <afflux> siretart: thanks and you're welcome ;)
[17:11] <rzr> go a message for me ? i lost it
[20:01] <nand> Hi! I've one package, ike, that is now present on intrepid, and which was not a debian merge (packaged only for Ubuntu). It's now also present in Debian. Upstream plans to do a release this week end: I'll update the debian package on Debian. The deadline in this situation is the debian import freeze, or the feature freeze?
[20:02] <nand> (forgot one sentence in the middle :) => I want to push this new version to ubuntu)
[20:07] <mario_limonciell> nand, you can pull the update from debian afterward after DIF, you will just manually need to request a sync
[20:07] <mario_limonciell> the DIF turns off all automatic syncing
[20:07] <nand> ah ok! So the deadline in this case is feature freeze
[20:07] <nand> cool, thanks!
[20:17] <mario_limonciell> nand, but if you can do it sooner than feature freeze, that's more ideal as you don't have to go and prod as many people :)
[20:18] <nand> I guess so :)
[20:20] <HoellP> hello, can anyone help me with debian packaging?
[20:20] <HoellP> i set up everything and it seems to work
[20:21] <HoellP> but when i try to build, i get the following error:
[20:21] <HoellP> checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool
[20:21] <HoellP> make: *** [config.status] Error 1
[20:21] <ScottK> Then you're missing a build-dep.
[20:24] <Kopfgeldjaeger> HoellP: try libxml-parser-perl
[20:25] <HoellP> but i can't control the packages controlled by pbuilder, can i?
[20:26] <HoellP> ah
[20:26] <HoellP> *working*
[20:42] <highvoltage> g'night motus
[20:51] <cody-somerville> night highvoltage
[21:50] <norsetto> heya heya
[21:53] <RainCT> hey norsetto
[21:54] <norsetto> Hola RainCT
[21:54] <RainCT> :)
[22:02] <geser> Hi norsetto
[22:10] <norsetto> heya geser, any new event on the horizon?
[22:11] <lukehasnoname> http://www.imdb.com/title/tt0119081/
[22:11] <norsetto> huats!!!
[22:11] <laga> i love that movie. it's a bit scary sometimes tho
[22:11] <huats> norsetto: !!!
[22:17]  * norsetto must be the only living being on this planet that not only has not seen that movie but before yesterday didn't even know it existed
[22:17]  * ajmitch waits for the laptop to load to be able to see what it is
[22:17] <ajmitch> ubuntu needs to boot faster :)
[22:17] <persia> ajmitch: You need a solid-state drive...
[22:18] <laga> no. ubuntu needs to boot faster. :)
[22:18] <ajmitch> wouldn't make it much faster
[22:18] <persia> Well, maybe.  I recently saw a 27 second bootchart for Ubuntu.
[22:18]  * ajmitch needs to not run certain things like apache, mysql/postgresql, zope, etc on the laptop
[22:18] <persia> Yes.  That would do it :)
[22:19] <laga> heh
[22:19] <ajmitch> oh, and an openldap server, of course
[22:20] <ajmitch> all the useful things I need to test on a box somewhere :)
[22:20] <persia> ajmitch: Hmm.  You need a laptop with two distinct computers (one headless with internal serial console bridge).  That way you can boot quick for client stuff, and still play with your server.
[22:21] <ajmitch> heh
[22:21] <ajmitch> sadly it's because it's faster than the desktop box I have at work
[22:45] <james_w> persia: mind if I take cecilia out for a dance?
[22:47] <persia> james_w: Please do.  If you find a way to get her to play with the updated csound, I'd be especially happy.
[22:47] <james_w> you mean debian bug 438611??
[22:48] <james_w> or debian bug 476300?
[22:48] <Zombie> I have an advisory for Ubuntu Hardy/.
[22:48] <Zombie> The version of Open Arena included is Deprecated.
[22:49] <Zombie> And will not play on line with other Open Arena servers.
[22:49] <ScottK> What does deprecated mean in Open Arean terms?
[22:49] <ScottK> Ah.
[22:49] <ajmitch> various games tend to do this, unfortunately
[22:50] <norsetto> james_w: I think bug 438611 is obsolete now
[22:50] <Zombie> Another game that is broken, but because of technical issues is Warzone 2100
[22:50] <Zombie> Warzone 2100 used to operate fine under Gutsy.
[22:50] <Zombie> Now it skips like it uses software rendering
[22:50] <ajmitch> are there bugs failed about these issues in launchpad?
[22:51] <james_w> norsetto: yep, I just followed the paper trail all the way to the end.
[22:51] <norsetto> filed failed or failed filed?
[22:51] <ajmitch> norsetto: forgive me, I was looking at another screen while typing :P
[22:51] <Zombie> One more bug.
[22:52] <Zombie> OpenVPN deletes its own user account when upgrading from Gutsy causing it not to launch.
[22:53] <norsetto> ajmitch: ever seen my typing? Thats something to ask to be excused about
[22:53] <ajmitch> Zombie: again, launchpad is the first place to go to put in bugs
[22:54] <ajmitch> it may still get lost, but at least there'll be a record of it beyond 5 minutes of IRC :)
[22:58] <EagleScreen> hello
[22:58] <EagleScreen> i am learning to use pbuilder
[22:59] <EagleScreen> what happens if i am running Debian and i want to build a Ubuntu hardy package?
[22:59] <EagleScreen> i think i should use: sudo pbuilder update --distribution DIST-NAME --override-config
[22:59] <EagleScreen> in addiction, should I change repositories to hardy?
[23:00] <persia> EagleScreen: You might want to get debootstrap and pbuilder from Ubuntu to ease creating the chroot, but once you have a chroot, you can just build normally.
[23:01] <persia> Note that there are some extra checks in the developer tools (e.g. dpkg-buildpackage) in Ubuntu to verify complinace with additional Ubuntu policies that you'll miss working from Debian: it may also be worth having a working chroot with Ubuntu for building the packages.
[23:01] <EagleScreen> but i want to build for Debian and also for Ubuntu
[23:01] <james_w> persia: hmm, do you know if the patch in debian bug 476300 is sufficient for the updated csound?
[23:02] <ScottK> persia: The Debian debchroot knows about Ubuntu releases.
[23:02] <persia> ScottK: It does?  Cool.
[23:02]  * persia hasn't used Debian dev tools in a bit.
[23:03] <james_w> if an upload fixes a CVE then do I need to do anything more than mention the CVE number for it to be correctly tracked?
[23:03] <persia> james_w: My memory from the csound mailing list was that there was a more complex issue involved, and that the regex described served more to protect cecilia than as the main cause of incompatibility.  You might test it, and see what you find.
[23:04] <ScottK> james_w: There is a separate CVE tracker.
[23:05] <james_w> ScottK: is it based on changelog notification, or is it more manual than that?
[23:05] <ScottK> It's more manual than that.
[23:05] <persia> Anyone from MOTU SWAT around?
[23:05] <ScottK> emgent would know the details.
[23:05] <persia> james_w: If nobody steps up with details, ask in #ubuntu-hardened
[23:05] <EagleScreen> then, i dont need to change nothing to build for Ubuntu??
[23:05] <ScottK> james_w: You should also go back and look at which supported releases are also vulnerable.
[23:05] <james_w> there's no bug in lp, so I want to make sure that it gets picked up as we get the fix for free.
[23:06] <james_w> ah -hardened, thanks.
[23:06] <emgent> uhm ?
[23:06] <persia> james_w: Please do create a bug in LP, and link the bug to a CVE.
[23:06] <ScottK> james_w: Yeah.  You'll want to make bug and then nominate it for all affected releases.
[23:06] <ScottK> james_w: Now that emgent is here, I'm sure he can guide you through the process.
[23:06] <EagleScreen> i will investigate
[23:06] <persia> And subscribe ubuntu-security or motu-swat, as appropriate
[23:07] <ScottK> EagleScreen: You need to make a pbuilder chroot for the appropriate ubuntu release, but you can do it using the Debian packages.
[23:07] <james_w> hi emgent, I'm merging a package that includes a CVE fix from Debian, and I just want to make sure that I do the right things.
[23:08] <emgent> hi james_w uhm, ok
[23:08]  * ScottK needs to run off.  See you all later.
[23:08] <emgent> please join -hardened we can talk in this room
[23:08] <emgent> bye ScottK
[23:09] <EagleScreen> thanks Scottk, i supuse it must be done using command i said, but is needed anything more? may be temporaly use ubuntu repository in menu.lst???
[23:09] <EagleScreen> godbye scottk


[23:18] <TheSashmo> ok im going crazy.... no matter what I do, my laptop running ubuntu 18, keeps locking the screen and turning off the display, i've tried all the suggest online, and even used gnome tweaks, but its keeps turning off, does ANYONE know wtf?
[23:22] <gQuigs> TheSashmo: how long does it take until it happens.. ?
[23:22] <TheSashmo> its about 5mins
[23:26] <TheSashmo> ok I think I solved it
[23:26] <TheSashmo> effing power section has a screen option too!
[23:26] <TheSashmo> FML