[00:52] <blut> where do i get ubuntu support?
[00:52] <blut> cant join the #ubuntu channel
[00:59] <micahg> blut: try again, wfm
[00:59] <blut> 16:59 -!- Cannot join to channel #ubuntu (You are banned)
[01:00] <micahg> blut: well, if you were banned you're not likely to get support...
[01:00] <micahg> idk what the policy is
[01:00] <blut> ...
[01:00] <blut> micahg: i have never been in there before!
[01:00] <micahg> blut: you can file a request here: https://answers.launchpad.net/ubuntu
[01:01] <micahg> blut: ah, that's a problem
[01:01] <micahg> blut: hold on
[01:06] <persia> mvo: ubuntu-dev-tools is the least owned package in the archive :)  If you have a useful script to share, please add it (and it's manpage) with alacrity :)
[06:03] <nigelb> I'm looking for a main sponser to review a patch I have submitted :), bug 398873
[06:26] <Mirv> cjwatson: btw I didn't know there is also modem-modeswitch shipped in udev already... anyway, eg. Josh seems to indicate kernel developers would not want switching in the kernel code: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?p=1906#1906
[06:28] <Mirv> and that modem-modeswitch should be removed and is obsoleted by its developer
[07:01] <pitti> Good morning
[07:02] <pitti> crimsun: symptoms> apport.hookutils has helpers for the common cases: getting a package's modified conffiles (attach_conffiles) and non-default gconf values (attach_gconf)
[07:02] <pitti> crimsun: see python -c 'import apport.hookutils; help(apport.hookutils)'
[07:03] <pitti> crimsun: we don't have functions other than that, since for general conffiles there's not much abstraction that you could do (if you have some ideas, I'm all ears)
[07:20] <poet> where does the LiveCD store files?  I'm out of disk space on the LiveCD because I copied over a large file.  Deleted the file, trash is empty, disk is still full
[07:23] <pitti> poet: it's all in a RAM disk
[07:24] <pitti> so you can't do file operations which change more than your RAM size minus half a GB (which is necessary for ubuntu itself)
[07:26] <nigelb> Can a main sponsor review a patch I have submitted :), bug 398873
[07:35] <dholbach> good morning
[09:14] <dupondje> On 2010-02-15 19:03z (1 hours 48 minutes ago), you uploaded a translation template for aptitude in Ubuntu Lucid package "aptitude" in Launchpad. => Translation template ?!
[09:14] <pitti> just ignore that, it's spam from Launchpad translation imports
[09:14] <dupondje> owkej :)
[09:15] <dupondje> btw, is there a bugreport about the login screen is something broken @ boot ?
[09:16] <dupondje> tought it was a bug in xorg-server-core and got fixed, but still having it sometimes
[09:16] <ogra> dont upload openoffice :) the langpack spam can go on for days :)
[09:16] <apw> pitti, should i be expecting an archive tool to be installed by default on a lucid install?
[09:17] <tkamppeter> pitti, hi
[09:17] <apw> (specifically ubuntu-build)
[09:17] <pitti> apw: archive as in .zip, etc.?
[09:17] <dupondje> ogra: lol :) spamfiler++ :)
[09:17] <apw> pitti, as in ubuntu-build ...
[09:17] <pitti> apw: hm, that's not expected; that's from ubuntu-dev-tools
[09:17] <pitti> hey tkamppeter
[09:17] <apw> pitti, how can i tell if its my fault its installed?
[09:18] <pitti> apw: ubuntu-dev-tools isn't in http://cdimage.ubuntu.com/daily-live/current/lucid-desktop-i386.manifest
[09:18] <tkamppeter> pitti, I have SRUed bug 513690, can you approve the foomatic-filters package in -proposed? Thanks.
[09:18] <apw> pitti, then i guess somehow i've asked for it ... hrm
[09:18] <pitti> tkamppeter: I'll process it when I do my round of SRUs this week; thanks!
[09:19] <ogra> apw, there is a flag somewhere that sets it to manually installed ... (beyond the meta checks you can do in the manifest file)
[09:19] <pitti> apw: it's a very useful package to have, though :)
[09:19]  * ogra doesnt know where that lives exactly though
[09:19] <apw> heh but its suddenly started using names of scripts i already had which is inconvienient
[09:20] <persia> apw: The trick is that when you write a script to help with development, commit it to ubuntu-dev-tools before someone else steals the namespace :)
[09:20] <ogra> heh
[09:20] <persia> Well, that's the point of u-d-t, isn't it?  So that we all share and improve the same set of scripts?
[09:21]  * apw adds  'if (ircnick == persia) { panic(); } to the kernel
[09:24]  * persia limits apw's uploads to not include the kernel
[09:24]  * apw takes the week off
[09:26] <persia> And this is why we have the values of cooperation and mutual support :)
[09:45] <mvo> ubuntu-dev-tools> can I haz edit-patch in there?
[09:45] <seb128> mvo, what is edit-patch?
[09:46] <mvo> seb128: a wrapper that auto-detects the patch system and DTRT
[09:47] <mvo> seb128: works with cdbs-edit-patch, dpatch-edit-patch, quilt
[09:47] <seb128> mvo, does it handle quilt nicely?
[09:47] <seb128> ie export QUILT_PATCHES
[09:47] <seb128> quilt push
[09:47] <seb128> etc?
[09:47] <mvo> yes
[09:47] <seb128> \o/
[09:47] <seb128> go go go
[09:47] <mvo> even bzr add debian/patches/new_patch
[09:47] <seb128> just upload!
[09:47] <seb128> ;-)
[09:47] <mvo> :) credits for dholbach for the idea
[09:48] <jpds> mvo: Is it related to watch-patch in there?
[09:48] <mvo> needs a bit of testing, but hey - this is lucid
[09:48] <jpds> what*
[09:49] <mvo> jpds: no, but they overlap in the auto-detection, I guess that is where they can/should share code
[09:49]  * mvo was not aware of what-patch
[09:54] <persia> mvo: Please do add any tools you want (sorry if my previous response was lost)
[09:54] <persia> mvo: And please don't ask next time: u-d-t is for us all to share our best scripts to help make development easier.
[09:55] <mvo> cool, thanks
[10:48] <apw> pitti, any idea what is causeing the partial updates in our burn-down charts?  i am guessing we have only our wiki entries.  may make more sense to drop those days completely
[10:48] <pitti> apw: partial updates?
[10:49] <apw> pitti, http://people.canonical.com/~pitti/workitems/canonical-kernel-team.html <-- four days back and like 16
[10:49] <pitti> oh
[10:49] <pitti> those happen if the WI tracker crashed either all day, or in the very last run of the day
[10:49] <pitti> sometimes happens if LP is down
[10:49] <ogra> apw, that points out where the team was really slackish :)
[10:50] <apw> heh
[10:50] <pitti> or just falls over with those silly "cannot decode JSON object" stuff, etc.
[10:50] <pitti> apw: the 12th was a bug in the WI tracker, not being able to cope with blueprints being milestoned to "later"
[10:50] <apw> if we are usiing a single transaction i'd expect the DB to not get updated in that case
[10:50] <pitti> this is fixed now
[10:50] <pitti> but since it was on the weekend, I didn't fix it fast enough
[10:50] <pitti> apw: right
[10:51] <pitti> apw: but you'd still not get any WI data for that day if it fails all day
[10:51] <apw> pitti, perhaps we should purge the wiki data for that day too, so its clear there is no data for the day
[10:51] <pitti> and then there's sqlite which is apparenlty not  ... entirely compliant .. to transactions
[11:16] <q0k> hi
[11:48] <apw> pitti, gnote is dumping core when i run it, (core dumped) and everything, but i don't see a (!) to report it ... whats the best way to diagnose that
[11:48] <apw> (the apport failure)
[11:48] <dupondje> you should be able to run apport manually :)
[11:48] <apw> yeah but i want it 'retraced', i don't just want to file the bug, i want the core included
[11:48] <pitti> apw: do you have a /var/crash/_usr_bin_gnote.1000.crash ?
[11:49] <apw> yeah i do
[11:51] <apw> pitti, ok moving that aside got it to pop up and ask again.  i think i hit restart and notthing happened, so i hit cancel and it went away.  for ever
[11:53] <pitti> ah, right, then it's "touched"
[12:09] <Greenwill> Who has a Fujitsu s7220... please contact me... i'm out of Japan and out of USA... i can't buy a fujitsu s7220 laptop here... if i order it from japan and ubuntu doesn't run on it i'll have big troubles...i didn't find it at https://wiki.ubuntu.com/LaptopTestingTeam/Fujitsu  ... could you test it ? (take installation video)please let me know bobgreenwill@openoffice.org thanks in advance
[12:10] <persia> IRC doesn't really work that way
[12:12] <Tm_T> awww
[12:20] <Chipzz> actually
[12:20] <Chipzz> I feel like mailing this greenwill idiot and telling him the laptop works
[12:20] <Chipzz> (and hope it doesn't)
[12:20] <Tm_T> Chipzz: no need to call him an idiot, though
[12:20] <persia> That's not best.
[12:20] <persia> It probably doesn't work, and probably needs some bugs filed.
[12:21] <persia> Same question was asked (with same idle time) also in other channels :(
[12:21] <persia> Needs someone to send a nice mail explaining how to get support.
[12:21] <Chipzz> Tm_T: failure to read channel topic and blatant violation of it -> idiot
[12:21] <Tm_T> Chipzz: still no need to call him that
[12:22] <Chipzz> so what do you call ppl like that then?
[12:22] <Tm_T> I just don't call them loud, I keep it in myself (:
[12:22] <Tm_T> keeps the atmosphere more friendly, I'd sat
[12:22] <Tm_T> say
[12:23] <Chipzz> persia: personnally I prefer the saying it does and having him blow money on it approach :P
[12:23] <Chipzz> apparently ppl only learn the hard way
[12:24] <persia> Chipzz: I don't think that approach is the one that leads to the best result in terms of Ubuntu's hardware support, and I prefer to concentrate on that (because I actually care a little), rather than on user behaviour (because there are lots of other users)
[12:24] <Chipzz> persia: ubuntu hardware support is an orthogonal issue
[12:24] <persia> Chipzz: Also, consider the possibility that the user is incredibly intelligent and well informed in several areas, but has never used IRC before, and is completely unaware of how it works.
[12:25] <Chipzz> if he's unaware of how it works
[12:25] <Chipzz> he shouldn't be using it
[12:25] <Chipzz> are you driving a car if you don't have a drivers licence?
[12:25] <Tm_T> Chipzz: should we say same to all users in #ubuntu too? (:
[12:25] <persia> Well, except that lots of documentation indicates that one *should* use IRC to request support.
[12:26] <Tm_T> persia: exactly
[12:26] <persia> That users may not know how the first time is an opportunity for education (which we can take or not as we prefer, individually)
[12:26] <Chipzz> then said documentation should do a better job of educating users on how to use irc
[12:26] <persia> I'll agree with that :)
[12:26] <Chipzz> like telling the users to read the frigging topic BEFORE asking questions
[12:27] <Chipzz> and after reading it, also comprehending and obeying it
[12:34] <Chipzz> persia: anyway, given that a) he uses an @openoffice.org address, which indicates he is a developer and thus fully aware of how things work in the opensource world, and b) he was doing it on multiple channels it's a pretty good guess that he was fully aware of what he was doing and wether or not it was acceptable behaviour
[12:36] <Chipzz> http://answers.yahoo.com/question/index?qid=20100216041614AA3ScID
[13:13] <pitti> zul: just noticed that the dhcp3-client apport package hook only attaches audit logs, related package info, etc. if you agreed to attach dhclient3.conf; that doesn't look intended?
[13:14] <pitti> zul: perhaps most/all of that stuff should be done outside the "if response == True"?
[13:14] <zul> pitti: agreed
[13:15]  * pitti is just reviewing the existing hooks and is impressed how many we have these days
[13:15] <tseliot> Keybuk: do we do something like "press this key to stop the fsck in Plymouth" already? If so, how do you call plymouth from mountall to write the "press this key..." line? Do you use "--update=" and then watch-keystroke or do you use "message" instead of "--update="?
[13:15] <pitti> people use interactivity, and all that
[13:17] <Keybuk> tseliot: err
[13:18] <tseliot> too many questions? :-P
[13:18] <Keybuk> tseliot: ply_boot_client_tell_daemon_to_display_message()
[13:18] <Keybuk> then ply_boot_client_ask_daemon_to_watch_for_keystroke()
[13:19] <Keybuk> with ply_boot_client_update_daemon() before both of those
[13:19] <Keybuk> so all three ;)
[13:20] <tseliot> Keybuk: ok, so you're using "message" to request action and "update" to update the status of fsck
[13:20] <Keybuk> tseliot: right
[13:20] <Keybuk> so update to update the fsck progress
[13:20] <Keybuk> then message to put a message on the screen about being able to cancel
[13:20] <Keybuk> then watch for keystroke to actually get told if they press that key
[13:21] <tseliot> Keybuk: ok, I was asking as I'm reimplementing a few functions in the theme and I wanted to implement bug #497311
[13:22] <Keybuk> right
[13:22] <tseliot> Keybuk: so, with that feature you would have to call ply_boot_client_tell_daemon_to_display_message() twice
[13:22] <Keybuk> I would?
[13:22] <tseliot> if you wanted to have 2 lines
[13:23] <Keybuk> that's ok ;)
[13:23] <tseliot> ok
[13:23] <Keybuk> it was more wanting to have a line along the bottom to put keypress information
[13:23] <Keybuk> "Press C to cancel" etc.
[13:23] <Keybuk> since the middle is already taken up by the theme's fsck stuff
[13:24] <tseliot> ok, so the theme would have 1st line = message, 2nd line = fsck status, 3rd line = action text
[13:25] <Keybuk> sure
[13:25] <tseliot> Keybuk: at this point I think that implementing bug #509373 would not be trivial
[13:26] <tseliot> well, doing it right, that is
[13:27] <tseliot> Keybuk: do you think I can postpone that? Or do you need that feature too?
[13:28] <Keybuk> tseliot: wrapping of long lines seems more of a DX issue to me ;)
[13:28] <Keybuk> it's definitely "experience" related
[13:29] <tseliot> Keybuk: ah, so the question would be more whether we want to have long lines or not
[13:29] <tseliot> it makes sense
[13:33]  * mvo is impressed by the amount of "OK" in http://people.ubuntu.com/~mvo/automatic-upgrade-testing/2010-02-16-12:16:25/
[13:33]  * pitti hugs mvo, splendid!
[13:33] <tseliot> :-)
[13:34] <pitti> mvo: is that "default install" or "all of main"?
[13:36] <pitti> mvo: does that include checks for bad "changed conffile" prompts?
[13:37] <mvo> pitti: that is the default install, main-all is running still
[13:38] <mvo> pitti: confile prompts do currently not cause failures, but they appear in the logs, I should make them fatal :)
[13:38] <pitti> ah, I already hoped.. :)
[13:38] <mvo> 2010-02-16 14:19:15,645 WARNING got a conffile-prompt from dpkg for file: '/etc/X11/app-defaults/Xedit'
[13:38] <mvo> 2010-02-16 14:24:06,125 WARNING got a conffile-prompt from dpkg for file: '/etc/default/apport'
[13:38] <mvo> the apport one is a false positive
[13:38] <mvo> I think its caused by the upgrader itself
[13:39] <pitti> right, I recently handled a bug report for that and assigned it to update-manager
[13:39] <mvo>  '/etc/X11/app-defaults/Xedit' <- that one has a open (and targeted) bugreport
[13:39] <pitti> perhaps we could copy the new version's file instead of just changing the value
[13:40] <tkamppeter> pitti, hi
[13:43] <tkamppeter> pitti, I have got a package for the "ptouch" label printer driver (http://www.openprinting.org/show_driver.cgi?driver=ptouch) and I have reviewed it and added the standard Ubuntu extensions (PPD update, Apport hook).
[13:43] <tkamppeter> pitti, now I want to upload the package. Is it possible to get it in before FF?
[13:44] <pitti> tkamppeter: sure, it's not Thursday yet
[13:45] <frafu> Hi, onboard is the default onscreen keyboard that ships with Ubuntu. As the ubuntu developers always patch the packages that I prepare to hide the menu items of onboard, I would like to ask whether somebody can tell me, who I can contact to discuss a way to let them visible. (Maybe by moving them from the Universal Access menu to the Accessories menu.)
[13:45] <pitti> everythign which is in NEW by Thursday won't need extra red tape
[13:47] <tkamppeter> pitti, so I simply upload it. Is it possible to MIR it to Lucid main after FF?
[13:48] <sebner> pitti: do you know by any chance when cjwatson will return?
[13:48] <unimatrix> any rhythmbox developers here by chance?
[13:48] <pitti> sebner: next week, he's on holiday this week
[13:49] <sebner> pitti: ohh, then I need to find someone else willing to backport dpkg on the build machines :\
[13:49] <pitti> tkamppeter: does it need to be in main? but yes, no big problem
[13:50] <ion> Le sigh, an apparmor profile change on upgrade caused the computer to grind to a halt again, thanks to the kernel module misbehaving.
[13:52] <tkamppeter> pitti, it is a printer driver, which means hardware support. Having it in main gives more Plug'n'Print already from the live CD.
[13:53] <pitti> tkamppeter: adding it to the CDs is a bigger step, we have to justify CD size versus popularity
[14:06] <cvincenzo> hello there
[14:12] <Jeeves_> Am I allowed to ask this channel about packagebuilding issues? Or is there a more appropriate channel?
[14:13] <nigelb> Jeeves_: #ubuntu-motu would be a good place
[14:14] <hyperair> #ubuntu-motu for universe packages
[14:14] <hyperair> for main packages, this is the right place
[14:18] <Jeeves_> Yeah, well. It's a private package :)
[14:18] <Jeeves_> I'm having issues with dh_shlibdeps
[14:25] <cvincenzo> can someone tell me whether packages of ubuntu for NAT and firewall there, so does the server (ubuntu) as a firewall and router?
[14:27] <Jeeves_> cvincenzo: This question is better for #ubuntu-server
[14:27] <cvincenzo> thank you Jeeves
[14:28] <Jeeves_> yw
[14:33] <Riddell> what's up with libmysqlclient16 on amd64?  I get a 403 forbidden
[14:35]  * Riddell eyes up zul as a potential guilty party
[14:35] <persia> Riddell: There was some version issues such that it caused everything to FTBFS only on amd64.  Didn't affect other arches because the source package that provided the messy version FTBFS there.
[14:35] <persia> Riddell: There's a bug about it/
[14:35] <persia> bug #521815
[14:35] <zul> Riddell: yes its in middle of being fixed
[14:36] <Riddell> good luck
[14:44] <pitti> Riddell: you can just purge the lib from your system to be able to dist-upgrade again
[14:44] <pitti> I guess it was pulled in at some point, but nothing uses it
[14:45] <Riddell> I'm just impatient for my packages to build :)
[14:45] <pitti> I and someone else were able to get rid of it without problems
[14:45] <pitti> oh, ok
[14:45] <pitti> shouldn't that already work?
[14:45] <Riddell> not if libmysqlclient16 can't be installed
[14:46] <Riddell> it's still the 7 version according to my apt
[15:09] <ari-tczew> ttx: ping
[15:09] <ttx> ari-tczew: opng
[15:09] <ttx> pong
[15:10] <ari-tczew> ttx: could you take a look again @ bug 515259 please?
[15:10] <ttx> ari-tczew: sure
[15:12] <ttx> ari-tczew: would you happen to also have the Ubuntu-1/Ubuntu debdiff ?
[15:13] <ttx> ari-tczew: (debdiff libcommons-attributes-java_2.2-6ubuntu1.dsc libcommons-attributes-java_2.2-7ubuntu1.dsc)
[15:14] <ari-tczew> ttx: I'm not Vikram, I can make debdiff, it's should be correct ;-)
[15:14] <ari-tczew> txx: debdiff libcommons-attributes-java_2.2-7.dsc libcommons-attributes-java_2.2-7ubuntu1.dsc > libcommons-attributes-java_2.2-7ubuntu1.debdiff
[15:14] <ari-tczew> s/txx/ttx
[15:14] <ttx> ari-tczew: that's debian/Ubuntu debdiff
[15:15] <ttx> ari-tczew: both are useful for review
[15:15] <ttx> ari-tczew: I need 2.2-6ubuntu1 -> 2.2-7ubuntu1
[15:15] <ari-tczew> ttx: what's the different method?
[15:16] <sebner> ari-tczew: about belpic: See this bug and especially the last comment. not really a reason to merge: https://bugs.edge.launchpad.net/ubuntu/+source/belpic/+bug/514174
[15:16] <ttx> ari-tczew: debdiff libcommons-attributes-java_2.2-6ubuntu1.dsc libcommons-attributes-java_2.2-7ubuntu1.dsc > ubuntu-to-ubuntu.debdiff
[15:17] <ari-tczew> ttx: why ubuntu-to-ubuntu? I 1st one heard about this
[15:17] <ari-tczew> sebner: so this is job for coolbhavi
[15:17] <sebner> ara:
[15:17] <sebner> argh
[15:18] <ttx> ari-tczew: see https://wiki.ubuntu.com/UbuntuDevelopment/Merging (search for "If you need sponsorship, you should generate two debdiffs")
[15:18] <sebner> ari-tczew: He hasn't reported it yet (wondering if he'll do it) but until it's fixed in Debian and no new upstream version there is no reason to merge currently
[15:18] <ari-tczew> ttx: so are you think. that my last attachment is not useful?
[15:19] <ttx> ari-tczew: it is useful. I just prefer to have both of them.
[15:20] <ari-tczew> ttx: so please just upload it. btw: please see https://merges.ubuntu.com/libc/libcommons-attributes-java/libcommons-attributes-java_2.2-6ubuntu1.patch if it will be useful for you ttx
[15:20] <ari-tczew> sebner: You have searched for packages that names contain belpic in all suites, all sections, and all architectures. @ packages.debian.org :-/
[15:22] <Chipzz> errr
[15:22] <sebner> ari-tczew: I don't understand?!
[15:22] <Chipzz> you might consider coordinating with Yoe?
[15:22] <Chipzz> doesn't he maintain that package?
[15:23] <ari-tczew> sebner: packages.debian.org can't found package belpic
[15:23] <Chipzz> ari-tczew: then you fail at searching
[15:23] <Chipzz> ari-tczew: pretty certain Yoe maintains a package for it in debian
[15:23] <sebner> ari-tczew: I know, the search is b0rken somehow. You can find it on some other way
[15:23] <sebner> ari-tczew: http://packages.qa.debian.org/b/belpic.html  <-- here you go ;)
[15:24] <ari-tczew> Chipzz: so please @ Yoe for fix section issue
[15:27] <Chipzz> ari-tczew: he's on irc, on the #debian-devel channel
[15:28] <ari-tczew> [16:27] [473] ari-tczew #debian-devel Cannot join channel (+i) - you must be invited ; regards ;-)
[15:29] <Chipzz> you may want to consider trying irc.debian.org? :P
[15:30] <ari-tczew> sebner: if Section field will be added into debian/control, is it possible to sync package?
[15:31] <ari-tczew> btw. I'm going to request bug @ debian, because coolbhavi now is on MOTU meeting
[15:31] <sebner> ari-tczew: Yeah, it's syncable then.
[15:37] <pitti> cr3: bonjour
[15:37] <ttx> ari-tczew: uploaded
[15:38] <ari-tczew> ttx: could you take a look too @ bug 521390
[15:38] <pitti> cr3: you have an alpha-3 work item "provide list of types of problems that we should make symptoms for:" (https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-bug-management); is that still relevant? should we postpone/drop it? will be done this week?
[15:38] <ttx> ari-tczew: not just now
[15:38] <pitti> cr3: (just cleaning up teh remaining WIs and was curious about that one)
[15:38] <ari-tczew> maybe pitti ?
[15:38] <czajkowski> I really need to unhighligh cz :(
[15:53] <cr3> pitti: I've been thinking about it and I've even been asking the support folks for suggestions, so it's on my radar
[15:54] <mathiaz_> james_w: hi - could you schedule an import of the puppet package in sid in the package branch?
[15:55] <mathiaz_> james_w: LP has imported the new version from sid and I'd like to merge the package via bzr
[15:56] <ari-tczew> sebner: how are you think, should do I make debdiff for NMU or make debdiff which will include only debian/control changes?
[15:57] <sebner> ari-tczew: I'm wondering that you are doing something for this little change
[15:59] <james_w> mathiaz: it's running now
[15:59] <mathiaz> james_w: o^42
[15:59] <james_w> 5 minutes or so
[15:59] <james_w> mathiaz: how was FOSDEM?
[15:59] <mathiaz> james_w: great!
[15:59] <mathiaz> james_w: it was my first time there
[15:59] <mathiaz> james_w: so had to get used to the whole navigation
[16:00] <mathiaz> james_w: lots of talks to choose from
[16:01] <james_w> mathiaz: excellent
[16:01] <mathiaz> james_w: http://fosdem.org/2010/schedule/events/dist_topgit
[16:01] <mathiaz> james_w: ^^ that one was interesting wrt to package branches
[16:02] <james_w> yeah
[16:03] <mathiaz> james_w: nothing ground breaking though - it's similar to what we discussed with bzr looms
[16:03] <mathiaz> james_w: the list of tools/helpers is interesting though
[16:03] <james_w> mathiaz: yeah, it would be their implementation of it
[16:03] <mathiaz> james_w: I'll publish a blog post about fosdem soon
[16:03] <james_w> ace
[16:05] <jibel> mvo, ping
[16:05] <mvo> hello jibel
[16:07] <Laney> could someone possibly rescore https://launchpad.net/ubuntu/+source/ghc6/6.12.1-9/+build/1512010 for me? I would like to know whether it builds yet...
[16:08] <LaserJock> does apt-get source always tell you if a package is maintained in bzr or not?
[16:08] <mathiaz> james_w: http://paste.ubuntu.com/377693/
[16:08] <mathiaz> james_w: ^^ have you already seen this error?
[16:09] <geser> mathiaz: know bug
[16:09] <jibel> mvo, hello, I'm working on synaptic "sorting" issues of the package list.
[16:10] <mathiaz> geser: is there a workaround?
[16:11] <jibel> mvo, we currently can't sort by package name and I noticed there is no sort mode to change the sort order of this column. Is it intended or do you need a fix ?
[16:11] <jibel> mvo, see bug 518509
[16:14] <geser> mathiaz: bug 515597 and the "workaround" is to modify /usr/lib/python2.6/dist-packages/bzrlib/merge.py line 153 to "return self.merge_text(params)" (remove the second self)
[16:15] <geser> or wait for the bzr 2.1.0 release
[16:15] <mathiaz> geser: awesome! thanks
[16:17] <mvo> jibel: hi, let me check the bug
[16:17] <mvo> jibel: you mean that reverse sorting is not working? it would be nice to fix that
[16:19] <jibel> mvo, you can only sort packages in ascending order, descending does nothing.
[16:21] <jibel> mvo, in rpackagelister.cc only LIST_SORT_NAME is defined.
[16:27] <mvo> jibel: right, I remember now, it should be realtively straightforward to fix I hope, the other sorting columns should give you the needed info. do you think you could work on this code? I'm happy to help with specific questions
[16:28] <jibel> mvo, working on it then. I'll try to fix bug 165181 in the mean time.
[16:32] <mvo> nice! thanks jibel
[16:34] <mvo> jibel: I will send you tee or beer (whatever you prefer) as a thank-you :)
[16:44] <dupondje> how come that packages in NEW take sometimes really long before it gets into archives ? :)
[16:50] <pitti> mvo: any idea why http://people.ubuntu.com/~mvo/automatic-upgrade-testing/current/ points to Feb 08?
[16:52] <Keybuk> ev: you guys should totally aim for a 10s install in lucid+1
[16:52] <ev> hrm, where did I put that ice pick
[16:54] <mvo> pitti: yes, a bug in the script that updates the current symlink, I fix now
[16:54] <pitti> mvo: you rock, thanks
[16:55] <mvo> np
[18:25] <dupondje> http://archive.ubuntu.com/ubuntu/pool/main/m/mysql-cluster-7.0/libmysqlclient16_7.0.9-1_amd64.deb
[18:25] <dupondje> this seems broken ...
[18:25] <dupondje> dunno who can fix this :)
[18:28] <lucasr> jcastro, ping
[18:29] <jcastro> pong!
[18:30] <jcastro> lucasr, what can I do for you?
[18:31] <mathiaz> zul: ^^ - argh - libmysqlclient16 got bumped
[18:32] <zul> mathiaz: yeah i know im working on it
[18:32] <mathiaz> zul: mysql-dfsg-5.1 will have to be fixed as well
[18:33] <zul> mathiaz: it either needs to be fixed in soyuz (prefered) or i have a work around
[18:33] <zul> mathiaz: http://people.canonical.com/~chucks/libmysqlclient-fix2.patch
[18:39] <mathiaz> zul: why not use DEB_UPSTREAM_VERSION_MAJOR_MINOR?
[18:39] <mathiaz> zul: instead of UPSTREAM_VERSION?
[18:40] <mathiaz> zul: that would give: 7.0.9really5.1.41
[18:41] <mathiaz> zul: well that wouldn't actually work
[18:42] <mathiaz> zul: hm well - I'm not sure what's the correct answer here
[18:43] <zul> mathiaz: i been discussing it with slangasek as well
[18:43] <mathiaz> zul: upgrading to futur libmysqlclient16 packages should work as well
[18:44] <mathiaz> zul: DEB_NOEPOCH_VERSION should give you 5.1.41-3ubuntu5
[18:45] <mathiaz> zul: well - for a long time there was a  libmysqclient15off
[18:45] <mathiaz> zul: I don't remember where the libmysqlclient15off was coming from
[18:45] <dupondje> mathiaz: is that the reason http://archive.ubuntu.com/ubuntu/pool/main/m/mysql-cluster-7.0/libmysqlclient16_7.0.9-1_amd64.deb has permission error ?
[18:45] <mathiaz> dupondje: may be
[18:46] <mathiaz> mysql-cluster-7.0 ended up in main as well - which shouldn't have been the case
[18:55] <YokoZar> I have a very special problem with Lucid - Gnome works, I can run calculator and everything, but entering any terminal command or creating a folder in nautilus causes an instant deadlock.  I'm not even sure how to report such a problem
[18:56] <hyperair> what deadlocks?
[18:57] <YokoZar> hyperair: cpu goes to 100%, I hear fans spinning, no mouse movement.
[18:57] <YokoZar> I suspect maybe dbus
[18:57] <hyperair> use teh conky.
[18:59] <hyperair> i dont see how running some random terminal command can fry dbus
[19:00] <YokoZar> It's the only thing I can think of that create folder and terminal might have in common, though I'm not too familiar on the internals
[19:00] <kees> pitti: say, should I be expecting apt to remove devicekit-disks?
[19:01] <james_w> kees: devicekit-disks -> udisks
[19:01] <james_w> so it should be installing the latter at the same time?
[19:01] <YokoZar> pitti: do I need to file a separate bug to ask for branding-ubuntu to be added to the seed or is getting in main enough?
[19:03] <sebner> YokoZar: ohh, what a fortune :) Did you get my mail?
[19:03] <YokoZar> Yeah one sec
[19:07] <kees> james_w: okay, cool.  yeah, it installed udisks.
[19:07] <kees> james_w: why are we not using Debian's devicekit-disks?
[19:07] <james_w> kees: it's an upstream rename
[19:08] <kees> ah-ha! ok
[19:08] <james_w> http://ftp-master.debian.org/new.html
[19:08] <superm1> its really annoying for downstreams too... having to update to use all the new names and keys and what not
[20:04] <ccheney> ScottK: we aren't planning to transition to boost 1.41 this cycle are we?
[20:04] <ScottK> ccheney: Not AFAIK, no.
[20:04] <ccheney> ScottK: ok, i saw it was in the archive but still in universe atm
[20:05] <ScottK> boost-defaults |   1.40.0.1 |         lucid | source
[20:05] <ccheney> ah ok :)
[20:05] <ScottK> I expect it to stay there.
[20:06] <slangasek> phew :)
[20:07] <smoser> i've a packaging question. what is the general rule for the name of 'Source'. should it be the same as upstream package name (to the extent possible) or should it be the same as the binary.
[20:07] <smoser> as an example: http://sourceforge.net/projects/snoopy/
[20:07] <sebner> smoser: what's the binary name?
[20:07] <slangasek> smoser: I believe the general rule is to name the source package to match the upstream package name as closely as possible, unless you're packaging perl
[20:07] <smoser> project is 'snoopy', but package (and in this case Source) is 'libphp-snoopy'
[20:07] <slangasek> (though arguably, the perl source package naming also matches upstream "as closely as possible")
[20:08] <sebner> smoser: I'd go with snoopy then
[20:08] <smoser> i'm looking to package 'cloudfusion' which would have a binary named 'libcloudfusion-php'
[20:08] <smoser> thanks.
[20:09]  * slangasek sees multiple mentions of php and looks around for his wooden stake
[20:13] <slangasek> DktrKranz: how frequently do you poll for new upstream versions of launchpadlib?
[20:14] <slangasek> DktrKranz: I'm told to expect a new upstream release before FF, would you prefer that I let you package it in Debian first or shall I prep it in Ubuntu and forward you my changes?
[20:18] <DktrKranz> slangasek: usually when I'm aware of them (I usually look at DEHS, but once per week I scan homepages for updates). I can prepare it quickly when it will be released, if you can give me a IRC ping if I'm late on it, I can arrange things.
[20:18] <slangasek> DktrKranz: ok, cheers :)
[20:18] <DktrKranz> :)
[20:20] <lifeless> mvo: ping
[20:20] <lifeless> mvo: just had an interesting question in -motu; do-release-upgrade won't attempt hardy->lucid yet, it goes to intrepid instead.
[20:21] <lifeless> mvo: shouldn't we permit that (when -d is given) so that the ugprade path can be tested?
[20:21] <kees> lvm2 merge uploaded... hold on to your hats
[20:21] <lifeless> kees: nooooooo

[20:22] <kees> pitti: in talking to Debian upstream, it seems that the symlinks are correct
[20:22] <kees> lifeless: ??
[20:22] <lifeless> kees: I'm teasing.
[20:22] <kees> pitti: (for lvm uuid and name)
[20:22] <kees> lifeless: oh, whew.  okay :)
[20:22] <slangasek> lifeless: and for you: <ō>
[20:22] <kees> slangasek: wow, you had that art at the ready.  nice.  :)
[20:23] <slangasek> kees: only in the sense that I am well versed in the extended Latin alphabet ;)
[20:23] <kees> hehe
[20:23] <mvo> lifeless: yes, that should actually work "do-release-upgrade -d"
[20:23] <lifeless> mvo: apparently its not
[20:23] <mvo> hmm
[20:23] <lifeless> its selecting intrepid
[20:23]  * mvo looks
[20:23] <mvo> *ick*
[20:24] <mvo> lifeless: I joined #motu now
[20:24] <kees> lifeless: how do I upgrade a remote bzr tree?
[20:24] <lifeless> bzr upgrade url
[20:24] <lifeless> or ssh host bzr upgrade path
[20:25] <lifeless> or rsync locally; bzr upgrade; rsync back
[20:25] <kees> lifeless: bzr: ERROR: File exists: '/srv/bazaar.launchpad.net/push-branches/00/00/3c/c9/backup.bzr'
[20:25] <lifeless> kees: two things; click on the button in the web ui:)
[20:25]  * kees goes looking for a button
[20:25] <lifeless> kees: and you can delete that file using sftp (lftp is nice - lftp sftp://bazaar.launchpad.net/~user/product/branch)
[20:26]  * kees ♥ lftp
[20:28] <leonardr> DktrKranz: i'm talking with slangasek on #ubuntu-release about a pre-freeze launchpadlib release. he says you're doing the packaging
[20:28] <leonardr> i'm going to try to have everything released by tomorrow morning, but i wonder how much lead time you'll need to do the packaging?
[20:28] <leonardr> ie. when do i lose my opportunity?
[20:29] <DktrKranz> leonardr: I'll be able to package it not before tomorrow, ~20 UTC
[20:30] <DktrKranz> after that, I'll be back home and can manage it
[20:30] <leonardr> ok, so i can be pretty late tomorrow as long as it's done tomorrow
[20:32] <DktrKranz> leonardr: I could reserve some moments during work, if that would help
[20:33] <leonardr> DktrKranz: i'm just trying to find out now so i don't get into a situation where i'm causing you stress
[20:33] <leonardr> unless something goes catastrophically wrong in the next hour it should be available tomorrow for you to package whenever you like
[20:33] <DktrKranz> that's great then :)
[20:38] <kees> lifeless: hrm, how long should the LP-button-upgrade of a branch take?
[20:39] <smoser> mathiaz, your patch looks good.
[20:39] <smoser> i'm happy you generally figured out how you were "supposed" to do it.
[20:40] <smoser> the only suggestion i have is
[20:40] <smoser> if not self.cfg.has_key('puppet'): return
[20:40] <smoser> to save yourself an indentation level
[20:40] <mathiaz> smoser: :) - well I know how to read python code ;)
[20:40] <smoser> but thats pretty nit-picky
[20:41] <smoser> so, i'm good with it as it is if you like.
[20:41] <lifeless> kees: 'a while'
[20:43] <mathiaz> smoser: suggestion applied. Branch updated.
[20:44] <kees> lifeless: heh
[20:44] <smoser> merged.
[20:44] <qense> What do <placeholder>s do in glade files?
[20:44] <qense> What is their function?
[20:52] <lifeless> kees: it has a async queue that it churns through. no idea if there is a status page
[21:31] <PlainFlavored> hey, i'm learning C, is it alright if I paste a short piece of code that's not working out very well and have someone tell me what's wrong with it?
[21:33] <ccheney> is mysql going to be fixed soon? its blocking OOo
[21:34] <lamont> that's very sad... I looked at the armel builders to find one I could steal, and they're all doing long builds
[21:35] <ccheney> lamont: trying to put OOo on one them too ;-)
[21:35] <lamont> ccheney: gcc-snapshot bootstrap for um... something
[21:35] <d1b> ccheney: please no !
[21:35] <ccheney> zul: ping
[21:35] <mathiaz> ccheney: zul is working on it with slangasek as well
[21:36] <ccheney> ah ok :)
[21:36] <ccheney> zul: thanks guys (saw above from mathiaz)
[21:36] <d1b> PlainFlavored: wrong channel. try #c
[21:37] <PlainFlavored> d1b: okay, thanks
[22:36] <slangasek> ccheney: one way or another, should be resolved by Thursday
[22:40] <ccheney> slangasek: ok
[22:40] <ccheney> slangasek: i guess its complicated to fix? (i don't know what is wrong other than it ftbfs)
[22:41] <slangasek> ccheney: libmysqlclient16 was inadvertently taken over by the wrong source package, and bumped the binary package's version number by a decade or so; looking at whether it's possible to roll this back in soyuz, with the fallback plan being to mock up a new binary version number for all eternity
[22:42] <slangasek> (and option #1 requires containing the spread of the broken package version, which means not uploading option #2 until we've ruled it out)
[22:44] <ccheney> oh wow, thats painful
[23:23] <\sh> time to go home
[23:24] <sebner> \sh: hf!
[23:25] <\sh> sebner: I had already :) now it's family time...happy to see my little son again after a 20h day at work
[23:26] <sebner> \sh: 1) Don't work that much 2) your son is awake at 00:26?
[23:27] <\sh> sebner: yes :) his teeth are giving him some problems :) 10 teeth at a time is much pain :)
[23:27] <sebner> urgh
[23:27] <sebner> \sh: wrong smilies though :P
[23:27] <\sh> anyways...good night :)
[23:28] <sebner> \sh: gn8
[23:32] <jp--> hi guys. can somebody check my forum post? I've got problems trying to get sound work on Jaunty, I think the kernel module for my sound card gets confused with the hdmi and rca output... http://ubuntuforums.org/showthread.php?p=8836492#post8836492  thank you =)