/srv/irclogs.ubuntu.com/2011/02/09/#ubuntu-devel.txt

ohsixcjwatson: thanks00:57
ohsixcjwatson: does zsync work well with those images? (<10% transferred between versions)01:09
charlie-tcaohsix: yes, it does. I use it everyday to keep my copies updated01:11
cjwatsonI don't have measurements myself, but I don't see why it wouldn't, certainly01:11
ohsixneat01:12
cjwatsonone of the reasons we use squashfs is that it's rsync-friendly, which should hold for zsync too01:12
ohsixdo the aufs update options in update-manager actually work?01:12
macoaufs still exists?01:13
ohsixwell i never tried it, but i've seen it there; and it'd be cool if it did01:13
cjwatsonaufs still exists01:13
macoi remember that it did....i remember talk of it on the mailing list01:13
macobut i thought the upstream kernel rejected it?01:13
macocjwatson: is it sauce? or did upstream change minds?01:14
cjwatsonthere's no other option for our live CDs right now01:14
cjwatsonI don't know what the state of the update-manager work is; mvo had it working at one point but I don't know if that's current or what the provisos were01:14
cjwatsonwe're looking at a similar facility using btrfs01:14
ohsixman an fs that can do snapshots and jump back to them would be great :D01:15
ohsixafaik you can do it with lvm but it's convoluted and expensive01:16
cjwatsonunfortunately the alpha-2 installer wasn't quite up to the required installation bits, but alpha-3 should be; I don't know how far mvo's got with the u-m side01:16
macoohsix: https://lists.ubuntu.com/archives/ubuntu-devel/2009-March/027747.html01:16
ohsixmaco: thanks01:18
macocjwatson: this is what i was thinking of https://lists.ubuntu.com/archives/ubuntu-devel/2010-June/030952.html01:20
cjwatsonyes, there have been problems with aufs maintenance01:23
cjwatsonbut union-mounts are perpetually almost-there-but-not-quite01:23
cjwatsonwe would love to use them eventually ...01:23
macoand given valerie having left red hat, i don't expect them to reach "quite" any quicker01:23
JordiGHSo my package shows a bug in Ubuntu that it doesn't show in Debian. It hasn't been modified; looks like it's just a problem with how some libraries get pulled in as dependencies during build time in Ubuntu and Debian. How should I fix it/01:38
JordiGH?01:38
JordiGHThis bug, to be precise: https://bugs.launchpad.net/ubuntu/+source/octave3.2/+bug/54667101:38
ubottuUbuntu bug 546671 in octave3.2 (Ubuntu) "fltk backend does not load" [Undecided,New]01:38
JordiGHIf there is no Ubuntu maintainer for a Debian package, is there a way to automatically request bugs for an Ubuntu package be forwarded to Debian?01:40
micahgJordiGH: there's a link in the PTS to Ubuntu bugs01:41
JordiGHYeah, can I just get them forwarded to my email?01:41
micahgJordiGH: you can subscribe to the package in launchpad if you like01:41
JordiGHWhat's the point of reporting bugs to an Ubuntu package that has no Ubuntu maintainer? :-/01:42
micahgJordiGH: Ubuntu doesn't have maintainers01:42
JordiGHWhat are they called, Software Artists?01:42
cjwatsonit just means that packages do not necessarily have dedicated maintainers in the same way that they do in Debian01:43
micahgJordiGH: unfortunately, we don't have enough people to get to all the bugs01:44
cjwatsonit doesn't mean that nobody will ever look at it01:44
JordiGHOkay, I guess I'll subscribe to all of "my" Ubuntu packages... and figure out how to fix this bug that doesn't exist in Debian.01:44
macocan start out just requesting a no-change rebuild in case it just needs to be rebuilt to go with current libraries i guess01:45
cjwatsonmaco: best not to spend buildd resources on that until after confirming that it would fix the problem01:46
JordiGHI don't that's the problem, I gotta figure out why it's not pulling in the right library at build time.01:46
* cjwatson peers at the build-dependencies01:46
JordiGHI don't know that's01:46
micahgmaco: it's been rebuilt since it was reported with no succes01:46
macomicahg: oh01:46
cjwatsoncomparing the Debian and Ubuntu build logs would be a good plan01:47
micahgJordiGH: I would suggest finding which package has that symbol and make sure that it was pulled in with the build-deps in Ubuntu, it could be something that the toolchain changes for natty/wheezy are trying to avoid01:47
cjwatsonthe bug was reported long before those toolchain changes.01:47
JordiGHSo, how do I tell Launchpad to send me bug reports regarding these packakges?01:48
cjwatsonsubscribe to the package, as micahg told you01:48
micahgcjwatson: right, I'm saying the toolchain change might be meant to fix similar issues01:48
JordiGHI know, where's the damn link?01:48
micahgs/fix/expose/01:48
cjwatsonstop swearing and I'll tell you?01:48
JordiGHWhere's the beautiful link?01:48
cjwatsonheh01:48
cjwatsonhttps://launchpad.net/ubuntu/+source/octave3.201:48
micahghttps://bugs.launchpad.net/ubuntu/+source/octave3.2/+subscribe01:48
cjwatsontop right, "Subscribe to bug mail"01:48
JordiGHAlright, thanks.01:49
JordiGHAnd now, I gotta do the same for the 30+ other packages, joy.01:49
cjwatsonthe usual culprit for this kind of bug is alternatives in the build-dependency chain01:49
JordiGHI gotta login?01:49
* JordiGH taps foot impatiently.01:49
cjwatsonyou could use launchpadlib for that01:49
* cjwatson looks up the API01:49
macowell you still have to login to use the api01:50
cjwatsonsure01:50
macoin order to authorise your script to run01:50
cjwatsonbut it saves clicking through 30+ links01:50
JordiGHLook, guys, I don't want to get involved with Ubuntu; I just don't want my package making us look bad because nobody is looking at it in Ubuntu. I want to subscribe pkg-devel-octave@lists.alioth.debian.org to all of these packages, not my personal email.01:51
JordiGHI guess I can use pkg-octave-devel@lists.alioth.debian.org as the subscription email address?01:51
micahgJordiGH: well, you still have to log in, but then, create a team, set that e-mail as the team contact, subscribe the team01:51
cjwatsonyou'll need an account whose preferred e-mail address is pkg-octave-devel01:52
broderJordiGH: isn't this what the derivatives feature in Debian BTS is for?01:52
cjwatsons/BTS/PTS/01:52
broderor maybe it's PTS. i can't remember01:52
JordiGHbroder: What feature is that?01:52
broder:)01:52
* micahg already suggested the link in the PTS to Ubuntu bugs (shows a count as well)01:52
cjwatsonit's in the developer's reference01:52
broderhttp://www.debian.org/doc/manuals/developers-reference/resources.html#pkg-tracking-system01:53
broderyou want to subscribe to the derivatives-bugs keyword01:53
JordiGHbroder: I see... thanks.01:54
brodernp01:55
cjwatsonhmm, no differences in the octave3.2 dependencies between Debian and Ubuntu that I can see01:55
cjwatson(not meaningful ones anyway)01:55
cjwatsonI wonder if this is really a problem in octave itself, or a transitive problem somewhere else01:56
JordiGHWhere's the Ubuntu build log?01:56
cjwatsonhttps://launchpad.net/ubuntu/+source/octave3.2 links to all the versions01:57
cjwatson(I have a browser keyword for https://launchpad.net/ubuntu/+source/%s, since that's nearly always my starting point)01:57
cjwatsonhttp://launchpadlibrarian.net/58223997/buildlog_ubuntu-natty-i386.octave3.2_3.2.4-8_BUILDING.txt.gz is the latest one on i38601:57
* cjwatson tries to install it here to look but it depends on the world so will take a while01:58
JordiGHWell, I see it is pulling libfltk1.1-dev01:59
cjwatsonthat seems to match Debian01:59
JordiGHWait, duh, fltk is not the problem, it's the opengl stuff.02:02
cjwatsonindeed.  it's pulling in the same libgl* packages too, though02:02
cjwatsonthis is sort of why I wondered if it was a problem further down the stack02:02
* JordiGH wonders if it's a problem with C++ symbol mangliing.02:02
JordiGHThat could happen if there are several versions of g++ involved...02:03
JordiGHLet's see, where is that Ubuntu libgl package...02:03
cjwatsonit's a while since that ABI changed02:03
cjwatsonoctave3.2:1> backend("fltk")02:03
cjwatsonoctave3.2:2>02:03
cjwatsonseems fine here02:03
JordiGHHuh.02:04
JordiGHCan you plot something?02:04
JordiGHType "sombrero".02:04
JordiGHWithout quotes.02:04
cjwatsonlooks like a sombrero to me02:05
cjwatsonblue brim, red tip02:05
JordiGHWhat version?02:05
cjwatson3.2.4-8, in natty02:05
cjwatsonso perhaps something between maverick and natty has fixed thig02:05
cjwatson*this02:05
JordiGHOh, good.02:05
cjwatsonor perhaps it is architecture-specific02:06
macooh the if-statements02:06
cjwatsonI'm on i386; the only mention of an architecture anywhere in the bug report (most of the users don't say) is amd6402:06
cjwatsonI can't easily confirm that02:06
JordiGHI dooooubt this is architecture specific.02:07
cjwatsonwell, it's your package, but if it were mine I wouldn't like to rule it out until it's been confirmed, especially as we still don't know the cause :)02:08
JordiGHWell, libftgl2 doesn't have that symbol for some reason.02:09
cjwatsonshould it?02:10
JordiGHGood question, ld seems to think so, at least when it created Octave.02:11
cjwatsonGoogle suggests opengl_renderer is part of the Octave API?02:11
cjwatsone.g. http://octave.sourceforge.net/doxygen/html/classopengl__renderer.html02:11
JordiGHYes.02:11
JordiGHThat's our bare-bones Doxygen.02:11
cjwatsonso why should the vtable for opengl_renderer be supplied by some other library?02:12
JordiGHWait, I see, that is an Octave symbol...02:13
JordiGHHmmmm....02:16
cjwatsonit should be in liboctinterp; in the lucid amd64 package, at least, it isn't02:19
JordiGHOkay, I'm feeling like a n00b... why does objdump tell me that liboctave has no symbols? Does that just mean it's been stripped? But don't you need symbols in order to link to it?02:19
* cjwatson unpacks a few more for comparison02:19
cjwatsonprobably wrong options, I'm using 'nm -D' here02:19
cjwatsonthere are different types of symbols and you may be asking for the wrong type02:19
JordiGHHuh, I don't want to disassemble it.02:20
cjwatsonnm -D isn't a disassembler.02:20
cjwatsonso maverick amd64 is broken, natty amd64 works02:20
cjwatsonor at least has the right symbols02:20
cjwatsonsame with i386 - lucid/maverick broken, natty fixed02:22
JordiGHHuh.02:22
JordiGHHow very odd.02:22
cjwatsonso you're right that it's not arch-specific02:22
* cjwatson diffs the maverick and natty build logs02:23
JordiGHOh, cute, nm can demangle C++ symbols.02:23
JordiGHThat's pretty damn interesting.02:23
cjwatson-checking for glEnable in -lGL... no02:24
cjwatson+checking for glEnable in -lGL... yes02:24
cjwatsonlooks like the first difference of note02:24
JordiGHYou diffed the build logs...02:25
cjwatsonyes02:25
cjwatsonGL/gl.h was present in both though02:25
cjwatsonand in fact GL/gl.h is identical in maverick and natty's mesa-common-dev02:29
cjwatsoncuriouser and curiouser02:29
JordiGHand it's the same Octave version, down to the Debian revision, isn't it?02:30
cjwatsonno02:30
cjwatson octave3.2 |    3.2.4-6 | maverick/universe | source, amd64, armel, i386, powerpc02:30
cjwatson octave3.2 |    3.2.4-8 | natty/universe | source, amd64, armel, i386, powerpc02:31
JordiGHWell, well, well...02:31
cjwatsonI wonder if the removal of libgl1-mesa-swx11-dev and libglu1-mesa-dev from the build-deps was significant02:31
cjwatsonnot a whole lot else changed02:32
JordiGHhttp://bugs.debian.org/59133302:32
RAOFWait - libgl1-mesa-swx11-dev was in the build-deps?02:32
JordiGHRAOF: Yes.02:32
JordiGHSo that could make the configure script fail.02:33
cjwatsonaha, I misread the maverick build log too - libgl1-mesa-dev *wasn't* installed then, of course02:35
cjwatson(due to the Conflicts from libgl1-mesa-swx11-dev02:35
cjwatson)02:35
JordiGHOkay, mystery solved.02:36
JordiGHcjwatson: Aren't you a DD?02:36
JordiGHI've seen your name in Debianthings.02:37
cjwatsonI still don't entirely get it though; GL/gl.h is provided by mesa-common-dev, which is depended upon by libgl1-mesa-dev and libgl1-mesa-swx11-dev both02:37
cjwatsonso what's making the configure test fail?02:37
cjwatsonJordiGH: yes02:37
RAOFIt's quite possible that libgl1-mesa-swx11 is broken; I can't imagine many people use it, so we wouldn't notice.02:37
cjwatsondamn, I missed taking note of my ten-year anniversary in Debian :-)02:37
* maco sets cake in front of cjwatson02:38
cjwatsonSubject: New Debian maintainer Colin Watson02:38
cjwatsonDate: Mon, 05 Feb 2001 20:36:19 +000002:38
cjwatsonanyway02:38
JordiGHHappy decennial.02:39
cjwatsonthanks :)02:39
cjwatsonah, octave3.2 is doing AC_TRY_LINK02:39
charlie-tcacjwatson: Congratulations on 10 years in Debian! that is quite an accomplishment02:39
cjwatsonsorry, AC_CHECK_LIB02:39
JordiGHcjwatson: Sorry, I've managed to get this far in life without understanding autotools. What's significant about those two macros?02:41
cjwatsonjust that the output of configure would depend on the shared libraries providing those symbols as well as on the headers02:42
cjwatsonI suspect that if we really wanted to nail this down it would require seeing config.log, which hasn't been preserved here02:43
cjwatsonbut it does seem as though those two build-deps are the culprit02:43
cjwatsonis it safe to remove those in both 3.2.3-1 and 3.2.4-6?02:44
JordiGHHuh, can you backport fixes to older Ubuntu releases?02:44
JordiGHI thought they only did security fixes.02:45
cjwatsonwe can02:45
cjwatsonhttps://wiki.ubuntu.com/StableReleaseUpdates02:45
cjwatsonthis is broken functionality, I think it's reasonable to fix02:45
JordiGHWell, we only use opengl for that particular function, so you can try backporting Thomas's fix to those two Ubuntu releases, and if you get the sombrero, then it works.02:46
cjwatsonI can take care of that02:48
cjwatsonthanks for the debugging02:48
JordiGHAnd thanks to you too.02:48
=== emma is now known as em
=== sanchaz-away is now known as sanchaz
=== oubiwann_ is now known as oubiwann
didrocksgood morning07:35
=== Guest20469 is now known as Lutin
Davieyoops07:54
Daviey@pilot out07:54
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots:
nigelbDaviey: patch piloting over night? ;)07:56
pittiGood morning07:57
cdbsGood morning Martin sir!07:57
hdonthe cgdb in ubu10.04 does not properly ioctl() with TIOCSWINSZ07:57
hdonthe latest release from their website works, though07:57
hdonerr07:58
hdonactually know, i just built from their bleeding edge07:58
hdonbut anyhow07:58
hdonit's a simple fix. you guys should put it in07:58
hdond'oh07:58
hdonnevermind, it still doesn't. i forgot i put in a work-around.07:58
* hdon fixes07:59
hdon$ cgdb cgdb # YES!07:59
broderhdon: best thing to do is file a bug, prepare a debdiff or a merge proposal (https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff), and ask for sponsorship (https://wiki.ubuntu.com/SponsorshipProcess)08:00
hdonbroder, sorry for the wrong information. the bug hasn't been fixed in any version of cgdb. i am fixing it now08:00
broderwell, once you do...08:00
dholbachgood morning08:01
hdoni will have to send the fix to the cgdb maintainer08:01
hdonsomeone else can get it into ubu08:01
=== jono_ is now known as jono
dholbachif you have a new project you want to introduce at UDW (5 minutes) and attract new people to help out, please consider signing up at the bottom of https://wiki.ubuntu.com/UbuntuDeveloperWeek/Sessions08:17
=== smb` is now known as smb
nigelbdholbach: does this look good? http://justanothertriager.wordpress.com/2011/02/09/have-an-interesting-project-you-want-to-talk-about/08:28
nigelbarg, sorrywrong channel08:28
=== JamieBen1ett is now known as JamieBennett
dholbach@pilot in08:40
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots: dholbach
cdbsdholbach: yay!08:41
* pitti hugs dholbach08:43
=== hunger_ is now known as hunger
hdonbroder, the bug is not in cgdb, it is in gdb. a warning occurs, though. you can see the bug in action here: http://codebad.com/~donny/gdb-tty-bug.png09:48
dholbachhey seb128 - who maintains gnome-session upstream? can we ping them about https://bugzilla.gnome.org/show_bug.cgi?id=637449 ? :)09:48
seb128dholbach, vuntz09:48
seb128dholbach, he's on #ubuntu-desktop, you can ping him there if you want09:48
dholbachI'm pinging him - thanks :)09:49
seb128yw09:49
=== zyga_ is now known as zyga
pittijames_w: hm, do you still remember why I reverted the WI tracker blueprints branch back then?10:40
pittijames_w: was it just because lillypilly was still running hardy?10:41
sabdflpitti: i know the feeling. the past recedes rapidly, doesn't it :-)10:41
sabdfllike my hairline10:42
pittior "maverick"10:42
cdbs:o sa-bdfl :)10:43
broderha! i think the sponsorship form is counting html entities as multiple characters10:43
broderat least, that's my best explanation for why it thought my write-up was 11 characters longer than i did10:43
maxb*blink*10:44
maxblillypilly?10:44
pittimaxb: aka "people.canonical.com"10:44
maxbJust when I thought canonical machine names couldn't get weirder....10:44
pittiYK, http://lillypilly.canonical.com/ confirms that it works :)10:45
pittimaxb: you think lillypilly is weird? have you looked at https://launchpad.net/builders recently, especially the armel ones?10:45
cody-somervilleWow. I just realized I've been reading 'lillypilly' as 'lillypad' this entire time.10:45
* pitti hasn't attempted trying to pronounce actinidiaceae or #canonical anacardiaceae yet10:46
pitti(eh, where did this "#canonical" come from)10:46
cdbsWow!10:46
cdbsinternal canonical discussions on #ubuntu-devel10:46
pittiI guess IS ran out of Penguin names, fruits and Antarctica stations at some point10:47
pittiand apparently the periodic table of elements as well :)10:47
cody-somervilleand berries10:47
broderthat's a lot of things to run out of10:47
Nafallopitti: you missed elements, but apparently we're still using the fruits scheme.10:49
pittiNafallo: "I missed elements"?10:49
pittiNafallo: oh, if you mean that buildds don't exhaust element names, we have more servers than just buildds :)10:50
Nafallopitti: we went through the periodic table between antarctica stations and fruits ;-)10:50
cdbsI kinda like the names of the buildds10:50
cdbsmakes me feel hungary10:50
pittiNafallo: I mentioned that above :)10:50
cdbs*hungry10:50
Nafalloah.10:50
jpdscdbs: Some people feel anger.10:51
pittiNafallo: will you guys ever move to Comic characters?10:51
Nafallopitti: not my decision10:51
cdbsOr Toy Story characters, like Debian does10:51
pittinah, NIH10:52
pittiand too confusing :)10:52
directhexdebian already ran out of toy story characters10:52
directhexhence using a toy story 2 character for 7.010:52
broderwheezy was the singing squeaky-toy penguin, right?10:53
directhexyep. from TS2, which has absolutely no historical ties to debian, other than being the sequel to TS110:53
Laneywhat is the historical tie with TS1?10:55
directhexLaney, bruce perens, bruce@pixar.com10:56
Laneyah yes10:56
directhexand related, e.g debian-bugs@pixar.com10:57
* amitk thinks IS should dedicating machine names to the top ubuntu contributors10:58
pitti. o { Hey Nafallo, can you please poke sabdfl? it crashed again }11:02
pittiamitk: I don't think that'll come across very well..11:02
amitkpitti: you mean there will be friction against the Ubuntu Hall of Fame?11:03
amitkpitti: or you think people don't want machines named after them :)11:04
pittirather, talking about people names when you speak about machines :)11:04
pittithat, too11:04
* Laney fscks amitk 11:04
* amitk goes back to hacking on the kernel and leaves community sensitivity to others... :-p11:05
pittiI have named my machines after Duck Tales characters11:05
=== MacSlow is now known as MacSlow|lunch
Nafallopitti: lolnovetoed11:06
cjwatsondirecthex: Debian hadn't quite run through everything in TS1 - scanning down wikipedia, there's at least RC, Mr. Spell, Rocky, Snake, Robot, Shark, Mike11:06
cjwatsonI assume the RMs just preferred Wheezy11:06
cjwatson("RC" would be more than a little confusing ...)11:07
directhexcjwatson, i was under the impression RC was on the excluded list11:07
* cody-somerville names his machines after the dictionary.com word of the day.11:07
cjwatsonstill leaves at least six though11:07
directhexthe machines at home are named delerium, death, desire & dream. cake to the person who guesses the scheme11:07
cody-somervilledirecthex, The Endless?11:08
directhexcake!11:10
* cody-somerville suspects the cake is a lie.11:10
tjaaltonwhat is the correct way to configure the console keymap? 'cached.kmap.gz' is a 20 byte file here11:13
tjaaltontried reconfiguring console-setup11:13
mr_pouitcjwatson: hi, what's the "correct" way of getting rid of the aubergine bg in grub-pc (the xubuntu plymouth theme is black, so it's a bit weird currently)? I tried to drop a 06_xubuntu_theme in /etc/grub.d to override the bg: http://paste.ubuntu.com/564912/. It works, but I guess it's not that nice, as it makes grub set the aubergine bg, and right after set a black one...11:18
pittijames_w: ah, nevermind, https://code.launchpad.net/~james-w/launchpad-work-items-tracker/blueprints-api/+merge/43240 has the reason (overly long file names)11:40
dholbachdoes anybody have a moderately educated opinion about bug 714838 (syncing newest gnutls26) - the sync generally looks good and we're still before FF - but it looks loads and loads changed (2.8→2.10)12:06
ubottuLaunchpad bug 714838 in gnutls26 (Ubuntu) "Sync gnutls26 2.10.4-2 (main) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/71483812:06
cjwatsontjaalton: reconfigure console-setup or edit /etc/default/keyboard - it may be that it currently requires a manual 'sudo setupcon' due to some bug12:07
cjwatsonmr_pouit: there's no correct way to do it in add-on packages right now - it'll need changes in grub212:07
cjwatsondholbach: I think it should be the reporter's responsibility to analyse reverse dependencies and prepare a transition if one is needed12:08
* dholbach nods12:08
cjwatsonand that he should be asked to do that12:08
cjwatsonmind you is it actually a transition?12:09
tjaaltoncjwatson: it looks fine though, just that the console keymap on my desktop is wrong, laptop has the same settings and it's fine there (though no umlauts with the vga font it seems)12:09
cjwatsonapparently not, it's still gnutls2612:09
Laneyno12:09
dholbachcjwatson, yes, no transition - just a huge version jump12:09
cjwatsonthen I have no educated opinion :)12:09
cjwatsontjaalton: does 'sudo setupcon' fix it?12:09
tjaaltoncjwatson: no, it creates the 20byte cache file, if I've removed it before12:10
cjwatsonforget about the cache file, I mean does it fix the currently-in-use keymap?12:11
tjaaltonno12:11
cjwatsonthen I need more details - what's the current behaviour compared to desired behaviour?12:12
tjaaltoncjwatson: it's the us layout12:12
tjaaltonon X it has been fine12:12
tjaaltonmaybe it was broken before upgrading lucid->maverick->natty yesterday, can't remember..12:13
cjwatsontjaalton: "it's the us layout" is that current state or desired state?12:15
cjwatsonshow me /etc/default/keyboard and /etc/default/console-setup12:16
tjaaltoncjwatson: current, I want fi :)12:16
tjaaltoncjwatson: http://paste.ubuntu.com/564947/ http://paste.ubuntu.com/564948/12:17
cjwatsontjaalton: now the output of 'sh -x /bin/setupcon' (run at the console)12:19
=== MacSlow|lunch is now known as MacSlow
tjaaltoncjwatson: sigh, how do I get the output somewhere? script, screen, redirecting stderr all fail12:24
tjaaltonit just says "not on the linux console..."12:24
cjwatsonhmm12:25
cjwatsontjaalton: use --force12:27
tjaaltonnaturally :)12:31
tjaaltoncjwatson: http://paste.ubuntu.com/564951/12:32
cjwatsontjaalton: could you remove /etc/console-setup/cached.kmap.gz and do the same again?12:34
cjwatson(20-byte file sounds like the result of gzipping nothing)12:35
tjaaltonok, got it. the error from ckbcomp is "Unknown name $sun_t6_custom"12:36
cjwatsonwhat version of keyboard-configuration and console-setup?12:37
=== evilvish is now known as vish
tjaaltonuh, 1.57ubuntu512:38
tjaaltonboth12:38
tjaaltonI see there are newer ones available12:38
cjwatsonconsole-setup (1.57ubuntu6) natty; urgency=low12:38
cjwatson  * Allow underscores in rules variables ($sun_t6_custom).12:38
cjwatson -- Evan Dandrea <ev@ubuntu.com>  Mon, 07 Feb 2011 15:14:44 +000012:38
tjaalton:)12:39
tjaaltonwonder why it wasn't installed yesterday during the upgrade12:40
tjaaltonmain archive and all.. but12:42
cjwatsontjaalton: ubuntu6 failed to build; ubuntu7 succeeded (yesterday)12:45
tjaaltoncjwatson: ok, that explains it. and the layout is good now12:46
cjwatsongood good12:46
tjaalton:)12:46
barrydholbach: ping, re: bug 686257 merge proposal (python-keyring)12:59
ubottuLaunchpad bug 686257 in python-keyring (Ubuntu) "upgrade to python-keyring 0.5.1 (and MIR)" [High,Triaged] https://launchpad.net/bugs/68625712:59
ogradholbach, hmm, you already acked all sync requests ari-tczew asked me for13:03
* ogra didnt know he had asked you too13:04
seb128ogra, he probably didn't13:05
seb128ogra, dholbach just do clean the sponsoring queue daily13:05
seb128ogra, without need pings to do it13:05
seb128needing13:05
ograah13:06
seb128ogra, seems he's patch pilot as well today ;-)13:06
ograoh, i missed that bit13:06
ograwho reads topics anyway :P13:06
ari-tczewDktrKranz: ping13:46
=== oubiwann is now known as oubiwann_
* hallyn just finally read the loom howto, figures he'll have to give those a shot13:49
hallynfor his udd sanity13:49
ari-tczewis there anyone with concerns about upgrade gnutls26 to 2.10*? bug 71483813:50
ubottuLaunchpad bug 714838 in gnutls26 (Ubuntu) "Sync gnutls26 2.10.4-2 (main) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/71483813:50
hallynjdstrand: I"ve uploaded the debdiff and source package for libvirt 0.8.7 to people.canonical.com/~serge/libvirt_0.8.7-0ubuntu1.src.tgz, if you wanted to take a look.13:51
DktrKranzari-tczew: pong13:55
=== yofel_ is now known as yofel
jdstrandhallyn: ack, but I won't be able to look at it for a bit13:55
jdstrandhallyn: thanks for doing it :)13:55
ari-tczewDktrKranz: IIRC at the natty start we have discussed about something related to gnutls... could you give a feedback for my question asked 5 minutes ago here?13:56
dholbachbarry, pong13:57
barrydholbach: hi.  comment updated on https://code.launchpad.net/~barry/ubuntu/natty/python-keyring/bug-686257/+merge/4896713:58
hallynjdstrand: thanks - no hurry, i'm gonna need sometime before i can get to testing it the way i want13:58
DktrKranzari-tczew: I think it was about gnustep13:58
dholbachbarry, will check in a bit13:58
barrydholbach: thanks13:58
hallyn(unfortunately I can't try loom right now bc I can't install packages - this is not good :)14:00
ari-tczewDktrKranz: yea probably, have you got any concerns about upgrade gnutls to 2.10.4?14:00
DktrKranzari-tczew: non that I know of14:01
ari-tczewdholbach: ^^14:01
dholbachbarry, I never saw tests packaged, but I haven't looked closely for a while - so I don't know - it just looked weird to me14:01
dholbachari-tczew, then get somebody else to ACK it - I just wasn't sure myself14:02
barrydholbach: looking in my build log keyring/tests subpackage is included in the .deb afaict14:02
dholbachbarry, yes, that's what I noticed too and why I wrote the comment14:03
dholbachI personally don't see the need (if people want code examples, they can grab the source - also users should be able to trust the package maintainers that the test suite was run) - but I'm very happy to be overruled - as I said: I don't know what "the standard" is there :)14:04
barrydholbach: i get it now (the tests weren't included before but now they are)14:04
barrydholbach: i'm not sure there *is* a standard ;)14:04
barrydholbach: it was debated to no consensus in upstream mlists.  you know now which side i came down on :)14:05
dholbachyep14:05
barrydholbach: do you feel strongly that they should not be included?14:05
dholbachno, as I said: I'm happy to be overruled14:06
pittiFWIW, I think it's by and large a waste to include them in binary pacakges14:06
barrypitti: please see my comment in the above mentioned merge proposal14:07
pittibarry: I do agree to the argument that these make it easy to check the correctness of the installed package14:11
barrypitti: i also like the simpler packaging when the tests are a subpackage (nothing to rm)14:12
barrydholbach, pitti: in the absence of consensus, can we keep the tests in this case?14:16
dholbachbarry, I'm happy whatever14:18
pittiyeah, I don't think it's a policy matter14:18
pittishoudl be the discretion of the maintainer14:18
pittiI don't have a strong opinion against it14:18
barrycool. thanks.14:19
dholbachbarry, I removed the "ppa0"14:26
dholbach@pilot out14:26
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots:
barrydholbach: thanks.  that was an artifact of a test build.14:26
dholbachari-tczew, what do you want to know about Harvest?14:33
hallynhm, a freshly created package using 'dh_make' is calling '/usr/bin/make -C .', but a 'CFLAGS += XYZ" in the top-level Makefile is being ignored.  Is that expected?14:33
ari-tczewdholbach: what kind of bugs are reported on harvest?14:33
dholbachari-tczew, you can see the list of "kinds of opportunities" on the left hand side and hover over them with the mouse14:34
dholbach(outstanding merges, rc bugs in Debian, etc.)14:34
ari-tczewdholbach: I'm clicking on kinds and nothing happened14:34
dholbachhover14:35
dholbachdon't blick14:35
dholbachclick14:35
ari-tczew?14:35
hallyndo i have maybe cdbs was overkill for this package14:35
dholbachmove the mouse of "bitesize" for example and don't move for a second14:35
dholbachit will give you some information what "bitesize" is about14:36
=== sconklin-gone is now known as sconklin
=== Quintasan_ is now known as Quintasan
ari-tczewdholbach: ok I guess how it works14:38
dholbachyou can select package sets and opportunity types you're interested in14:38
ari-tczewdholbach: I've received some informations that natty has got a lot of uninstallable packages. does harvest support this kind of bugs?14:39
dholbachno, I don't think there's a list for it14:40
ari-tczewdholbach: what do you think about expand harvest with department for uninstallable packages?14:43
dholbachari-tczew, the only thing you need to do is write a script that spits out data according to: http://daniel.holba.ch/blog/?p=83814:43
dholbachI can then add it to Harvest easily14:43
dholbachHarvest is decentral: you write a script that writes a simple enough list, I add it to Harvest14:44
dholbachcheck out http://harvest.ubuntu.com for more information14:44
ari-tczewdholbach: I'm not a code developer.14:44
dholbachand I won't have the time in the next few weeks, but I agree that it's a good idea14:45
gesersmoser: Hi, are you perhaps working on the ec2-api-tools FTBFS? I've gave it a try but only run into a new issue once I fixed one (I've already run into 2)14:45
smosergeser, i did not know it was ftbfs. i will make sure it does not. bug ?14:46
gesersmoser: no bug yet but http://launchpadlibrarian.net/58997063/buildlog_ubuntu-natty-i386.ec2-api-tools_1.3.57419-0ubuntu2_FAILEDTOBUILD.txt.gz14:46
ari-tczewdholbach: No matching opportunities in 238 selected packages14:47
smoserfirst issue is java depends ?14:47
ari-tczewdholbach: why only 238 packages are supported?14:47
gesersmoser: I can file a bug and attach those fixes that I already have if it helps you14:47
dholbachari-tczew, which package set is currently selected?14:47
ari-tczewdholbach: nothing14:47
dholbachari-tczew, there are much much more packages supported - it just shows you what you selected and what it has data available for14:47
dholbachari-tczew, please send me a screenshot14:48
smosergeser, sure. it can't hurt.14:48
smoserthank you.14:48
ari-tczewdholbach: http://img204.imageshack.us/i/harvestx.png/14:53
gesersmoser: bug 71581814:55
ubottuLaunchpad bug 715818 in ec2-api-tools (Ubuntu) "ec2-api-tools FTBFS in natty" [Undecided,New] https://launchpad.net/bugs/71581814:55
dholbachari-tczew, ok - can you file a bug about it? http://launchpad.net/harvest/+filebug14:59
dholbachI don't know what's going on right now - maybe Dylan will know14:59
=== herton is now known as herton_lunch
pittibarry: btw, the computer-janitor pygi branch should work well now with current natty's pygobject15:13
cdbssmoser: euca2ools is no longer shipping the EUCALYPTUS_CERT for EC2. why?15:14
smosercdbs, that not be intended15:16
cdbssmoser: really? in your blog post it appears its very much needed for AWS15:17
smoser*not shipping it* would be not intended :)15:17
smoserit is packaged in /usr/share/euca2ools/cert-ec2.pem15:17
cdbs:o15:18
* cdbs missed that in dpkg -L15:18
=== makl is now known as ximion
=== ximion is now known as makl
smosercdbs, if this is broken, let me know, but it does not appear to me that it should be.15:21
barrypitti: cool, i'll take a look, thanks15:23
=== makl is now known as ximion
=== herton_lunch is now known as herton
=== jono_ is now known as jono
=== jono is now known as Guest69233
=== beuno is now known as beuno-lunch
jambarry: just seeing if you're actually online right now, had some questions for you16:39
barryjam: i'm here, though just finishing up a meeting16:39
jambarry: k, just ping me when you're done, nothing urgent, but some udd questions16:39
barryjam: all freed up16:42
jambarry: I was thinking about the package-import stuff. And I thought it might be nice to prototype some stuff, and work with someone who is actually doing udd, and see what feedback we get16:42
jamI can write code, but I really don't know a ton about packaging.16:42
jamSo I was thinking it might be nice to do some prototype conversions of packages you actually maintain, so that you can give feedback about what you like/don't like16:43
barryjam: i'd be happy to be your guinea pig :)16:43
jamrather than hypothetical "wouldn't it be good if the importer did X"16:43
barryjam: unfortunately, i will not be at today's udd meeting16:44
loolcjwatson: Oy!  We're lacking some modules in initramfs for btrfs and probably others on some architecture/kernels; if btrfs-tools is installed, the initramfs has the right modules though; I see partman-btrfs arranges for this to be installed, but I was wondering whether we wanted to seed this somewhere so that Ubuntu initramfses have support for btrfs?16:45
cjwatsonlool: perhaps standard along with the other filesystems there, but I'm not entirely convinced - most of the filesystems there are ones you might have on USB sticks or whatever, and btrfs isn't really in that category16:46
cjwatsonlool: the initramfs only needs it if / is btrfs, and surely the installer should take care of that16:47
loolcjwatson: correct, d-i and ubiquity take care of that16:47
loolvia partman-btrfs16:47
cjwatsonindeed16:47
loolcjwatson: btrfs is "special" in that its deps are broken in the kernel modules16:47
looljust like ubifs16:47
cjwatson"its deps are broken"?16:47
loolcjwatson: The module dependencies are insufficient to pull the right stuff16:48
loollong story, but basically multiple providers of the feature prevents the module from having a sensible dep16:48
cjwatsonoh, you mean the way btrfs-tools/debian/local/btrfs.modules lists libcrc32c crc32c zlib_deflate btrfs16:48
loolYes16:49
cjwatsonis btrfs.ko itself in the initramfses you care about, just not its dependencies?16:49
loolcorrect16:49
cjwatsonbtrfs is probably there because 'auto_add_modules base' in initramfs-tools adds it16:49
cjwatsonso in that case I'd recommend adding those extra modules in 'auto_add_modules base' too16:49
cjwatsonthat seems better than seeding btrfs-tools16:50
cjwatsonand it should be upstreamable to Debian if their kernel is the same way16:50
loolcjwatson: Thanks a lot; I wanted to do this too, pinged maks on #debian-devel, but I dind't specifically know where to fix this in initramfs-tools16:50
loolcjwatson: wheredo you usually upstream hte initramfs-tools bugfixes?16:51
cjwatsonjust grep for btrfs in the source, there's only one non-changelog match16:51
cjwatsonbugs.debian.org16:51
loolcjwatson: thanks a lot16:52
jambarry: so can you give a couple of packages that you would like me to play around with?16:52
loolcjwatson: There is one btrfs utility which gets copied into the initramfs too; I don't know whether that'd be relevant enough to warrant seeding16:53
barryjam: sure.  do you want ones with or without quilt3 patches?16:53
loolI don't use btrfs at this point16:53
jambarry: I want ones that you use :), but both is probably good16:53
cjwatsonlool: it's useful for control and I think for subvolume bits and pieces but I don't think it's vital16:54
barryjam: okay :)  i'm going to grab some lunch and look at my set of branches.  will let you know16:54
jambarry: grabbing lunch myself, thanks. You can just email me if you want16:54
loolcjwatson: Ok; I will defer the seed part then, thanks16:54
barryjam +116:54
loolcjwatson: while we're at it, I've noticed ubifs has a similar issue and an uglier workaround (if / is ubifs and MODULES=dep, add these modules); do you think it should be listed in base too, or is it just a weird filesystem?16:56
loolcjwatson: Actually I'm just realizing that the base fix will only work for MODULES=most, probably not =dep16:57
cjwatsonlool: ubifs seems a bit too special-purpose for base16:59
loolcjwatson: Ok; I think I will use the same approach for btrfs + MODULES=dep than for ubifs17:00
ari-tczewcjwatson: you're admin with knowledge, maybe you have an opinion for bug 71483817:00
ubottuLaunchpad bug 714838 in gnutls26 (Ubuntu) "Sync gnutls26 2.10.4-2 (main) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/71483817:01
cjwatsonlool: this does seem like it ought to be a set of manual hints to the dependency resolver, yes17:01
cjwatsonari-tczew: I disclaimed having an opinion earlier when dholbach asked.  I think the basic questions should be: what's the reason for the sync, and are you prepared to take responsibility for any problems it causes?17:02
cjwatsonit seems like there should be more of a reason than just it being available17:03
=== cmagina is now known as cmagina-lunch
ari-tczewFound a total of 93 reverse build-depend(s) for libgnutls-dev.17:07
ari-tczewnot good17:07
cjwatsonI think that's why it made dholbach nervous; it's fairly core, and it's hard to roll back libraries17:07
cjwatsonso there'd have to be a substantial benefit to justify the risk17:08
ari-tczewcjwatson: I think he was easy as usually.17:13
ari-tczewcjwatson: I'll ask kees during his today piloting. If he won't be convinced, I'll delay sync to next devel cycle.17:15
loolcjwatson: Turns out there's a nicer fix in tip initramfs-tools as maks pointed out; I guess it means I need to mergeit  :-)17:16
cjwatsonlool: I've got most of that merge in bzr, I'll do it if you like17:19
cjwatsonI just forgot to commit17:19
loolcjwatson: Awesome17:27
loolcjwatson: Well I'd love if you were to upload that, thanks a lot!17:27
cjwatsonI'm sure I can manage that :)17:27
cjwatsonI'd been meaning to anyway17:27
=== beuno-lunch is now known as beuno
keesactivate super pursuit mode!17:30
keeswait, that's not it.17:30
kees@pilot in17:30
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots: kees
=== deryck is now known as deryck[lunch]
keesari-tczew: reading back-scroll doesn't help. what's the question?17:37
cjwatsonlool: done17:41
ari-tczewkees: we are considering useful of sync bug 71483817:42
ubottuLaunchpad bug 714838 in gnutls26 (Ubuntu) "Sync gnutls26 2.10.4-2 (main) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/71483817:42
=== cmagina-lunch is now known as cmagina
* lool hugs cjwatson 17:46
keesari-tczew: the only reason gnutls26 appeared in unstable is because debian opened for development again. I don't think we should sync it this cycle without a more pressing reason.17:48
ari-tczewkees: I'll delay it for next devel cycle then.17:49
keesokay, thanks17:50
ari-tczewkees: I'm counting on exim4. ;-)17:50
keesari-tczew: which bug# is that one?17:50
ari-tczewkees: bug 71385517:50
ubottuLaunchpad bug 713855 in exim4 (Ubuntu) "Merge exim4 4.74-1 (main) from Debian experimental (main)" [Medium,Confirmed] https://launchpad.net/bugs/71385517:50
keesari-tczew: for exim4, can you change 71_exiq_grep_error_on_messages_without_size.patch to use the upstream fix (from that report), drop the "From" (this should have been Author: with Daniel van Eeden) and add an Origin: line, and finally mention the debian bug # in the changelog?18:01
ari-tczewkees: FYI, I know about new way created by upstream, but I submitted debdiff before upstream patch.18:02
keesari-tczew: no worries. best we get the "real" fix in, though.18:02
=== sforshee is now known as sforshee-lunch
hvI read about a serious java bug on slashdot.  I cannot find a corresponding bug number on bugs.debian.org, or bugs.launchpad.org.  The bug is this: Double.parseDouble("2.2250738585072012e-308") produces an infinite loop.18:08
hvIs this well known?18:08
ari-tczewkees: I wanted get it by merging next upstream release, but that's right, we can get it right now and drop with merging next upstream release.18:08
ari-tczewhv: #launchpad18:08
micahgari-tczew: no, he's asking about java18:09
ari-tczewah18:09
mtaylorpitti: hi! is there a way to silence WARNING: the following files are not recognized by DistUtilsExtra.auto:18:10
keesari-tczew: right18:10
ari-tczewkees: what's the deadline of your piloting today?18:11
ari-tczewsince I have to do some other stuff right now, I'll finish exim4 later18:11
keesari-tczew: I'm done in about 3.5 hours18:11
ari-tczewok18:11
keesari-tczew: no worries; it's an easy fix now that I've read through the rest of it.18:11
micahgkees: can you sponsor my pidgin merge?18:11
keesmicahg: bug #?18:12
micahgkees: I just a merge proposal, no bug: https://code.launchpad.net/~micahg/ubuntu/natty/pidgin/2.7.9-2/+merge/4872118:12
* micahg figured it would be picked up the next morning :)18:12
cjwatsonhv: best to file a bug if you find it in our Java implementation.  We don't normally trawl Slashdot looking for bug reports there. :-)18:13
hvcjwatson: I don't expect bug reports in slashdot, either.  Last one I remember was the debian openssh fiasco ;)18:14
cjwatsons/openssh/openssl/18:15
hvapparently openjdk does not use launchpad for bug reports (or that is what launchpad says)18:15
keesmicahg: looking at it now18:15
cjwatsonyou should file bug reports on Ubuntu packages in the package namespace, not the upstream project namespace18:15
micahgkees: thanks18:15
cjwatsonhttps://bugs.launchpad.net/ubuntu/+source/openjdk-618:15
cjwatson(or, better, 'ubuntu-bug openjdk-6')18:15
keeshv: sbeattie may already be looking into that issue.18:16
=== arand__ is now known as arand
keesmicahg: I find this merge confusing. :) /me isn't used to bzr merges for packaging yet.18:18
hvcjwatson: thanks. /me is embarrassed.  kees: thanks.18:19
micahgkees: ok, I guess leave it for someone else, or I can walk you through it18:20
keesmicahg: no, no, I got it; it's just I need to pull a lot of packages to actually review it. it's much easier to review debian-to-ubuntu deltas rather than ubuntu-to-ubuntu deltas across a debian change18:21
micahgkees: ah, ok18:21
micahgkees: yeah, I actually found a change I made was actually made by Debian, so I dropped it from the changelog18:22
* kees nods18:22
micahgkees: BTW, the debian branches are on LP, so you can diff against them as well18:23
keesmicahg: true, but I only trust source packages. :)18:23
micahgkees: no, I meant the Debian source package import18:24
keeswow, there are _extensive_ changes between debian and ubuntu. seb128: shouldn't you enumerate the changes when doing a merge of pidgin? besides just control and rules, there are _8_ added patches.18:25
seb128kees, they were enumerated like 2 changelog entries bellow18:26
micahgkees: I'm wondering how I missed those18:26
* micahg only saw one change18:26
keesseb128: yeah, I see that now.18:26
seb128kees, I did just fetch the new debian revision, apply that and added a "sync on debian" entry18:26
keesmicahg: this is why I don't trust bzr. :)18:26
seb128either that rebasing18:26
seb128easier18:26
micahgkees: maybe I should redo that then18:26
keeswell, my opinion is to always enumerate the delta, but if that's not how seb128 does it, then I guess it's less of an issue here.18:27
keeslet me still look at what actually changed, one sec...18:27
* micahg guesses he shouldn't trust bzr either18:27
seb128kees, that's how I do it usually but I feeled lazy and just wanted to backport one revision from debian without redoing the merge18:28
keesseb128: see, there are changes between the last full resync list and current.18:28
* kees nods18:28
keeslast full changelog list was 1:2.7.3-1ubuntu118:28
* micahg can do a full list :)18:28
keesmicahg: yeah, I'd prefer that. I'll keep review the actual delta here, but I'd like to see a full delta report in the changelog.18:29
kees*reviewing18:29
seb128kees, well I could have copied the summary in the current entry18:30
seb128it's basically a merge with a new revision grabbed after and a changelog entry added for upload18:30
keesseb128: right. but between 1:2.7.3-1ubuntu1 and current there were 7 real changes, and 3 resyncs without enumeration. it can be confusing to someone new to the package. *shrug*18:32
seb128indeed, sorrya bout théat18:33
seb128doh, "sorry about that" rather18:34
micahgI just found some stuff never made it into our package :(, minor things like Vcs-Svn changed to Vcs-Git18:35
RoAkSoAxis there anyone expert in distutils extra that might be ableto help me with an issue of updating a .desktop file?18:36
* micahg needs to file a bug against bzr for not showing this stuff18:37
bcurtiswxi downgraded a package from the gnome3 PPA to natty (nautilus), but it still links to libgtk-3.0.so.0 => /usr/lib/libgtk-3.0.so.0 (0x00007fd03e47b000)18:45
bcurtiswxhow can I change that to be -2.0 ?18:45
=== deryck[lunch] is now known as deryck
keesmicahg: the actual contents of the merge look fine. once you're ready with a new changelog, I'm happy to upload.18:48
bcurtiswxas far as packaging is concerned, a merge you would bzr merge-upstream, what do you do for a sync ?18:49
lifelessmdz: ping18:52
micahgkees: it seems we missed a lot of changes in our version, i'm going to try to pull in some of the changes that Debian made to the packaging, I'll check the changelog to make sure it's not something specific that we changed18:52
keesmicahg: cool, thanks18:55
=== sforshee-lunch is now known as sforshee
mdzlifeless, hi18:57
lifelessmdz: I'm wondering what my next step should be with the discussion about package name substring matching in bug search18:57
lifelessmdz: I'm presuming you saw my thread on u-d, and blog post on blog.l.n18:58
mdzlifeless, I had seen your blog post but not the u-d thread18:58
mdzand I didn't see the comments on your blog post18:58
mdzso I know what you proposed but not what the response was18:59
lifelessthere was little response18:59
lifelessone strongly in favour of the current behaviour18:59
lifelesssome technical 'how can we help make what you do now fast'18:59
lifelessand a few 'make it faster -please'18:59
lifelessthe u-d thread - https://lists.ubuntu.com/archives/ubuntu-devel/2011-February/032381.html19:00
lifelessmdz: based on the feedback I've had, I don't think there would be an outcry at us changing this, but I want to make sure that I haven't missed a community depending on it19:02
mdzlifeless, in that case, I think all you can do if you want to be more cautious is to wait a while longer and publicize the question more widely19:02
lifelessmdz: can you suggest a good forum for wider publication ?19:03
mdzlifeless, you've already hit ubuntu-devel and planet, so I'd say identi.ca and twitter if you haven't already19:03
mdzlifeless, but frankly, I think it would be reasonable to throw the switch and see what happens, so long as it's easy to back out19:03
lifelessI'll send something out on those channels today19:03
mdzAIUI you're doing more runtime feature switches these days to facilitate that sort of thing19:04
lifelessyes, we can phase it in conservatively with the ability to toggle it off in a second19:04
lifelessif we're not sure about a change19:04
keesslangasek: hi, do you have a moment to look at https://code.launchpad.net/~mathieu-tl/ubuntu/natty/plymouth/lsb-release-version/+merge/45095 ? I think it's ready, but since you had reviewed it before, it might make sense for you to double-check it now?19:24
slangasekkees: <cough> reload the page ;)19:24
keesslangasek: /me sees no difference....19:26
slangasekkees: Status: Merged19:26
slangasekkees: I merged it not 5 minutes ago :)19:26
keesoh! hah.19:26
keesokay, I was looking for comments or your review status to change. ;)19:27
keesexcellent timing!19:27
jambarry: are you still around?19:53
jamsome Q's about pychecker19:53
barryjam: yep19:59
jambarry: so, it looks like it was fairly recently converted to v3 format, and before that there *weren't* any debian/patches files20:00
jam(as of Lucid at least, since 'apt-get source' gave me something without any debian/patches)20:00
barryinteresting20:00
barryjam: does that make it harder or worse to use as an example?20:01
jambarry: I'm trying to figure out how things are supposed to be done20:01
jamI thought I sort of understood debian/patches, but getting something that doesn't have it is both good and bad20:02
jamgood to know that things like this exist20:02
jambad because we have to plan for how to handle them20:02
barryjam: right.  it's considered bad form to add a patch system when there isn't one already, unless you're the debian maintainer20:03
barryjam: in those cases, we edit the source directly, and the change gets included in a diff.gz file against the original tarball20:04
jambarry: I always thought it was bad form to edit the source directly :)20:04
barryjam: as did i, until i chastised for doing it the other way :)20:05
jambarry: so why don't I see your name in the pychecker history?20:06
jam):20:06
jam:)20:06
=== tkamppeter_ is now known as tkamppeter
jamsilly async hands20:06
jambarry: so my goal with this is to put together a (possibly fully manual) import of a package, that you could poke around in, and see what you think of20:08
jamI'd like something that you actively use, if possible20:08
barryjam: okay, let me find a better example20:09
barryjam: i guess part of the problem is that the packages i maintain i usually am also the upstream, so i don't tend to use quilt much in them.  where i've interacted b/w quilt and bzr is in projects i've fixed bugs in, i.e. adding patches20:13
jambarry: I personally don't care about quilt as much as how should the import look20:23
jamhowever, I assume you also tend to just fix upstream?20:23
jamor do you actually do fixes in patches?20:23
jamcjwatson: are you around ? i realize the timezone is probably pretty bad for you right now20:23
ari-tczewkees: I tried to encourage Debian maintainer to enable hardening in exim4 but he seems to be not interested :(20:24
SpamapSkees: thanks for uploading that upstart fix. :)20:25
barryjam: when i submit branches that fix bugs in ubuntu, i adapt to the package's existing patch system.  if it uses quilt, that's what i use, but it could be one of several different patch systems - or none at all.  i know that probably doesn't help much ;).  the biggest impedance mismatch is where i'm developing a fix in a branch that has a patchsys and i need to submit a new debian/patches file for review.20:27
barryjam: quilt is a good enough example of that, and this page shows the pain:20:27
barryhttps://wiki.ubuntu.com/DistributedDevelopment/Documentation/PatchSystem20:27
keesSpamapS: you bet; glad to have that all sorted out.20:28
barryjam: so i think any package that has a set of quilt packages would be decent to start with because it would give a sense of how we *want* to deal with it20:28
keesari-tczew: that's too bad :(20:28
jambarry: I'll read through that.20:30
jamThere are, in fact, several co-mingled issues20:30
jamone is how to handle 'I want the current tip in a fashion I can easily hack on it'20:31
jamanother is "how do we want to represent the history"20:31
barryindeed. ;)20:31
barryjam: if there's a conflict between those two goals, the first is (i think) more important.  a source package's history is largely determined by debian/changelog rather than 'bzr log' if that makes sense20:32
barryjam: i'm leaving early today, so let's talk again tomorrow20:32
lifelessbarry: the history has an impact on 'merge two branches20:32
jambarry: what is the "quilt import...; quilt push; quilt pop" ? (Just trying to understand why the multiple steps)20:33
jamthat seem to conflict20:33
barrylifeless: ah, not something the user cares much about, but the machinery cares a lot about20:34
lifelessbarry: they user cares a lot when merging from debian, or linaro from ubuntu. or linaro from debian20:34
keesSpamapS: https://code.launchpad.net/~clint-fewbar/ubuntu/natty/mountall/fix-mounted-tmp/+merge/4868120:34
keesSpamapS: doesn't "env MOUNTPOINT=/tmp" mean the /usr logic will never fire?20:34
barryjam: 'man quilt' will answer a lot of questions there, but basically think of quilt as a version control system.  it manages a stack of patches.  that's important because sometimes a patch is applied upstream and you can get rid of it in debian/patches20:35
jambarry: right, but you just imported a patch, and then push and pop it, which seems pretty strange, I guess you talk about it20:35
barrylifeless: i guess ime, a diff is useful, but debian/changelog tells me more about the history than bzr log does20:35
barryjam: right.  it *is* strange. :)20:35
jambarry: also, isn't that to remove the change from the working tree, which isn't what you are supposed to still do?20:36
barryjam: and i don't know if it's the best way to do it, but it's the only way i found that didn't result in huge gobs of unresolveable conflicts20:36
barryjam: someone (james_w perhaps?) did recommend that the changes could live in both the source tree and in debian/patches, but i found that confusing20:37
jambarry: I thought that was the point of v3 quilt20:37
lifelessbarry: by representing history, I think you and jam may mean different things20:38
jamthat it would be in a patch system, but also in the WT, so that you actually build/test against the final code20:38
SpamapSkees: no that only sets a default value20:38
lifelessbarry: things like 'should patches be a patch file or a changed revision20:38
lifelessbarry: and those changes radically alter the sorts of merge conflicts you get20:38
lifelessbarry: I'm not talking about /bzr log/ output *t all*20:38
barryjam: right, but most packagers *only* use quilt.  iow, it's there vcs for changing the package.  we essentially have two competing vcses on the same source tree20:38
jamlifeless: right. and everyone I've talked about seems to have internalized things differently :)20:38
SpamapSkees: that is so that if somebody runs 'start mounted-tmp' the don't torch all files in / .. might be worth nothing how important it is.20:38
SpamapSs/nothing/noting/20:39
=== mok01 is now known as mok0
* SpamapS really should get a new keyboard the typos are getting worse.. :p20:39
keesSpamapS: heh, okay, cool20:39
barryjam, lifeless i *really* have to go now, so we'll pick this up again tomorrow.  one thing that may be helpful is to think about not what we have to do today, but what we eventually want it to look like.  in that regard, i don't ever want to deal with the quilt until i have to generate something for external consumption, and then for folks who aren't using udd (read: the debian maintainer)20:40
jambarry: in my head, it is a "bzr export-loom-to-debian-patches" or something along those lines20:41
keesSpamapS: should the "cd "${MOUNTPOINT}" gain a "|| exit 0" ?20:41
SpamapSkees: I don't think so. The logic of the if's will exit 0 on the chance that /usr is mounted before /tmp (there won't be a /tmp/.delayed_mounted_tmp_clean) and this way we flag problems where /tmp isn't accessible.20:43
keesSpamapS: what about the totally insane case of: system comes up with no /tmp directory, /usr gets mount, entire filesystem is wiped.20:45
SpamapSkees: upstart scripts are guaranteed to run with set -e .. but I agree.. hggdh brought up that it is a bit scary that set -e is our only guard.. so maybe even || exit 1 is better.20:46
keescool20:46
SpamapSwant me to a) add a comment to the env statement, and b) add the || exit 1 and re-push ? Or do you just want to do that and upload?20:47
keesSpamapS: I'll just add it and push/upload. easy fixes.20:47
SpamapSkees: once again, thanks for the reviews and uploads.20:48
* SpamapS thinks there must be a UTF-8 character for "gratitude"20:48
keesSpamapS: you bet! :) thanks for the fixes :)20:48
ari-tczewkees: exim4 updated20:50
ari-tczewguess your browse remember bug number ;-)20:50
ari-tczews/browse/web browser20:50
keesari-tczew: yup, thanks, I'll go re-check.20:52
ari-tczewkees: when you have done exim4, would be nice to get this one https://code.launchpad.net/~bkbox/ubuntu/maverick/munin/fix-for-699967/+merge/4898420:54
amitkbryceh: hey bryce, around?21:40
amitkbryceh: I'm running latest natty with an nvidia GeForce 8400. Nouveau was giving several problems, so I decided to try the binary driver (nvidia-current). Now X doesn't start any more and uninstall the binary driver doesn't help either. Any suggestions?21:42
RAOFamitk: Uuurgh.21:43
amitkRAOF: i know, bad idea :-/21:44
RAOFamitk: Installing the binary driver has probably uninstalled X.  nvidia-current doesn't support the X server we have in natty at the moment (and the dependencies are a little messed up), so the xserver declares a Breaks: on nvidia-current.21:44
amitkRAOF: really?!!! /me checks21:45
RAOF(Or, technically, on xserver-xorg-video-8, which nvidia-current Provides:)21:45
amitkRAOF: you're right, apt-get install xorg is installing a lot of stuff21:46
amitkRAOF: thanks, X is back :)21:49
RAOF:)21:49
keescoming out of hyperdrive now...21:50
kees@pilot out21:51
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots:
amitkRAOF: how well are the discrete ATI cards supported? I need something other than nouveau21:51
RAOFamitk: If you've got something less new than a Radeon X6800 it should be fully supported.21:51
RAOF(By the open drivers.  Again, no proprietary fglrx for Xserver 1.10 yet)21:52
ari-tczewkees: FYI, it could be ubuntu3 for SRU21:52
ari-tczewbecause natty is 3ubuntu221:52
keesari-tczew: it _can_ be, but it should not be.21:52
ari-tczewkees: strange21:53
keesbest to just stick to the common convention to avoid needing to consider collisions.21:53
ari-tczewbut no problem for me21:53
keesfor example, I can give you a case where this caused a problem:21:53
keesmaverick release, natty opened for development21:54
keessome SRUs went through into maverick and were distro-copied to natty21:54
keesso maverick and natty had the same versions21:54
keesthey were, say ubuntu2 then ubuntu3. then natty gets a "real" bump to ubuntu4.21:54
keeson the next SRU to maverick, following the package convention, it also tried to do ubuntu4, but that collides with natty21:55
ari-tczewkees: nope. maverick - 1ubuntu2, natty -3ubuntu221:55
keesari-tczew: right, in this case it's not a problem. I'm saying that when reviewing patches and doing sponsorship, it's best to set a good example and follow the expected conventions on package versioning.21:55
ari-tczewkees: ok understand.21:56
ari-tczew;]21:56
kees:)21:56
achiangkees: i've a question re: chromium-browser... v8 is in maverick-security (i think), but i don't see a .orig.tar.gz here --- http://ports.ubuntu.com/pool/universe/c/chromium-browser/22:01
keesachiang: hm, looking22:03
keesachiang: I think the orig would just be in the regular archive.22:04
achiangkees: ah, interesting. thanks22:04
keesachiang: should be findable on LP though: https://launchpad.net/ubuntu/+source/chromium-browser22:04
achiangkees: actually, i don't see it here either -- http://archive.ubuntu.com/ubuntu/pool/universe/c/chromium-browser/22:05
achiangkees: i guess we don't actually want v8 anywhere22:05
achiangbecause it doesn't appear in LP either22:06
keesachiang: yeah, looks to just be v922:06
achiangkees: thanks!22:06
keesachiang: you should still be able to dig it out of https://launchpad.net/ubuntu/+source/chromium-browser/+publishinghistory22:07
achiangkees: nope, the latest is what i want, so v9 is perfect22:07
keesachiang: e.g. https://launchpad.net/ubuntu/maverick/+source/chromium-browser/8.0.552.237~r70801-0ubuntu0.10.10.122:07
keesachiang: okay, cool22:07
achiangthanks again22:08
szymon_ghi22:20
szymon_gcould anyone tell me what are default cflags for ubuntu 32bit 10.10/11.04 :?22:20
szymon_gis it, despite its name (-386) still runable on that architecture /apart from performance issues etc/- thats theorotical question22:21
micahgszymon_g: minimum arch for x86 is 686 in Ubuntu now22:22
szymon_gmicahg, is it the same for the current one and the next one, or was it changed somehow? have you got a link to documentation etc about that /i discuss that on one of forums, i need a 'hard proof'/ :?22:23
szymon_gah, thanx for answer btw (my manner :/)22:23
* micahg looks for the pertinent mail on ubuntu-devel22:24
micahgszymon_g: https://lists.ubuntu.com/archives/ubuntu-devel/2010-July/031020.html22:25
szymon_goh, great thanx micahg!22:26
micahgszymon_g: you're welcome22:26
szymon_gbtw, if may i ask: why the name is still 386? if can be (well.. it is) a bit confusing...22:26
micahgszymon_g: legacy, Debian's default is 486, but we just call the platform i38622:27
* szymon_g still doesn't understand why not to call it simply i686 ;)22:27
broderszymon_g: it's mostly because the string "i386" is baked into a lot of places, and changing it would be a huge ordeal22:29
hallynis there a 'dh_installxyz' command to install /etc/default files?  I know debian/package.default will get handled, but the package ships with a /etc/default/xyz file in its base directory, I'm wondering how to best get that installed22:33
broderhallyn: i think dh_installinit handles default files22:33
broderbut what's wrong with just using dh_install for that?22:34
hallynbroder: just that the file ships in the package's base dir.  should i just copy it into debian/ in a pre-build step?22:34
broderdh_install can pull from the root of the package22:34
hallyni don't want to copy it myself and riskit getting otu of sync22:34
hallynbroder: that's what i was hoping.  so you say dh_installinit?  lemme go re-read that one22:35
broderno, dh_install22:35
broderthere's no reason to treat the file specially. it's in one place, you want it in another place, that's what dh_install does22:35
hallynbroder: ok.  i was afraid there might in fact be a reason to treat is specially22:36
hallyn(namely, perms/ownership)22:36
hallynbroder: i'll do that then, thanks!22:36
broderperms and ownership are all handled by dh_fixperms anyway22:37
broderdh_installinit doesn't do anything special to the default file it copies over22:37
highvoltage /win 2622:37
hallynand so the first place dh_install looks for the file is the package topdir?22:38
=== bjf is now known as bjf[afk]
=== mbarnett changed the topic of #ubuntu-devel to: Launchpad down/read-only from 23:00 - 00:30 UTC for a code update || Archive: open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Frien
=== sconklin is now known as sconklin-gone

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!