/srv/irclogs.ubuntu.com/2009/12/11/#ubuntu-devel.txt

=== yoasif_ is now known as yoasif
cjwatson-                if 'DONE' in f or 'POSTPONED' in f or 'TODO' in f or 'INPROGRESS' in f:00:05
cjwatson+                if 'DONE' in f or 'POSTPONED' in f or 'TODO' in f or 'INPROGRESS' in f or 'WIP' in f:00:05
cjwatsonnixternal: ^- committed, should fix that00:05
nixternalcjwatson: rock on! thanks!00:08
cjwatsonit'll probably take an hour or two before pitti's cron job picks that up00:08
nixternalthat's cool...really appreciate that...I was just going to change them all on the wiki page, but you made that easier :)00:09
maxbI don't suppose there is any way to convince update-manager that a *specific* third-party repo should not be disabled on distro upgrade, is there?00:20
james_wmaxb: the feature was just added I think00:26
james_wthere's some config somewhere00:26
maxbI shall go grepping then00:27
=== dendrobates is now known as dendro-afk
maxbOf course, if it has just been added, it'll be several years before all my colleagues are using a suitable version of Ubuntu :-)00:28
cjwatsonmaxb: add it to /usr/share/update-manager/mirrors.cfg?00:29
cjwatsonI think that works00:29
james_wmaxb: there's bug 147080 for coarse-grained00:34
ubottuLaunchpad bug 147080 in update-manager-core "do-release-upgrade should make disabling third party repositories optional" [Wishlist,Fix released] https://launchpad.net/bugs/14708000:34
yoasifi have a possible bug, but i don't know where to file it00:45
yoasifbasically, all of the alpha-1 cds have the same name (ubuntu, xubuntu, kubuntu), which makes it a chore to seed all of them on bittorrent (or even to store them).... any ideas where to file this?00:45
cjwatsonyoasif: already filed as bug 19966000:46
ubottuLaunchpad bug 199660 in ubuntu-meta "CD-image naming scheme" [Undecided,Invalid] https://launchpad.net/bugs/19966000:46
cjwatson(Invalid because it was moved to ubuntu-cdimage; but I do suggest you find a workaround anyway, it's painful to change because it would break everyone's scripts)00:47
yoasifcjwatson, thanks, still kinda lame00:47
cjwatsonhow polite00:47
yoasifhmm?00:47
maxbIs notify-osd broken in lucid, or is the funky grid of orange lines some sort of debug aid?00:55
maxbcjwatson: Thanks for the mirrors.cfg pointer. I think you are right about the filename, but I think the copy that is actually used is shipped in the release-upgrader tarball. Hmm. But now I have ideas about overriding it using /etc/update-manager/release-upgrades.d/00:59
Rocket2DMndoko, what?01:07
ebroderlies01:07
ebroderSorry - wrong window01:07
keesjames_w: is the documentation out of date or am I doing something wrong with these merges?02:04
kees$ bzr mark-uploaded02:05
keesbzr: ERROR: Unknown target distribution: lucid02:05
james_wis a bug02:05
james_wyou can ignore it for now02:05
james_wso I guess the documentation is out of date :-)02:05
keesheh02:05
keesjames_w: it would be nice to have changelog merging working better and something that does the dpkg-genchanges -S -v... stuff.  Is that on the list?02:06
keesjames_w: it's currently harder to do merges with bzr, since MoM does this stuff for you automatically.02:06
james_wthe changelog merging is on the list02:06
keesI'm worried we're going to start losing merged changelog history if people aren't helped to do the dpkg-genchanges call.02:07
keesanyway, must run away to dinner...02:07
james_wwe could add a --merge flag to "bzr bd"02:07
james_wthat can look at the changelog and do the right thing02:07
james_wit's not possible to do it automatically02:07
Keybukall mark-uploaded does is tag, right?02:08
james_wyeah02:09
Keybukso debcommit -r DTRT for now :p02:09
james_windeed :-)02:09
* maxb wonders if anyone is interested in sponsoring a merge of Subversion?02:10
=== dendro-afk is now known as dendrobates
sam_Hi,After I finish a dpkg-buildpackage I modify some .conf files but no .c source files, I want to update the modified .conf files into the .deb file, how can I use dpkg-buildpackage command to avoid re-compile all the .c source files:02:37
AmaranthIf you're just building it for yourself you can use debuild binary02:38
=== dous_ is now known as dous
=== pbn_ is now known as pbn
=== robbiew is now known as robbiew_
DNS777hey guys, do you have a simple guide for me how to make a proper ubuntu/debian package? :-)04:14
fabrice_sp!packagingguide04:15
ubottuThe packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports04:15
fabrice_spDNS777, ^04:15
DNS777ty :)04:16
fabrice_spyw ;-)04:17
YokoZarjcastro: I want to make a wiki page link to "upstreaming bugs" to describe the process, which page should I point it at?04:20
* YokoZar is modifying the Testing Team pages to mention how important upstreaming bugs is when they're found in the development release04:21
jcastroYokoZar: https://wiki.ubuntu.com/Bugs/Upstream04:22
jcastroYokoZar: feel free to grab an existing subpage and make a wine-specific one if you want04:23
YokoZarnot wine related ;)04:23
YokoZarjcastro: that was my thought, but that page doesn't seem too friendly in its current form.04:23
YokoZarhttps://wiki.ubuntu.com/Bugs/HowToTriage at "Forwarding upstream" links to that page too, but it doesn't seem to have the promised content04:23
YokoZarnamely "details on how ot report bugs in various upstream bug trackers"04:23
jcastroyeah04:24
jcastrothe idea is that each of those sections is specific to that project04:24
jcastroas you can see we only have the major ones04:24
YokoZarI guess I was expecting a brief paragraph or two on why we upstream in general and what it is on that page04:24
jcastrobut anyone is welcome to add anything, like the Listen folks did04:24
jcastroI suppose I could add something like that.04:24
jcastrocan you send me a mail and I'll todo it?04:24
* jcastro is only half-way working right now. :p04:25
YokoZarWill do.  Thanks :)04:25
=== dous_ is now known as dous
ebroderIf you hit 'c' at the aptitude [Y/n/?] prompt, you might get something useful05:01
ebroderOof - wrong window05:02
keesjames_w: it's possible to do it automatically -- just lookup the version in LP for that suite06:11
pittiGood morning06:48
gesergood morning pitti07:14
dholbachgood morning07:53
tbielawamorning08:00
* ruffus910 waves hello08:01
slangasekKeybuk: dropping the "starting-dm" event - wasn't ubiquity integration also dependent on this?  and will gdm declare a Breaks: on usplash, to help users avoid getting wedged if there's a reboot mid-upgrade?08:12
ttxcjwatson: testing the eucalyptus update, it appears that the SC cannot announce itself on a CC+SC setup (local name conflict because SC_NAME = CC_NAME)08:30
looljames_w: Cool, thanks a lot!08:31
ttxcjwatson: maybe we should place the information about "target cluster" in a TXT record as well08:34
ttx-s doesn't seem to scale :)08:34
zhengHi, I'm new to use dpkg-buildpackage for .deb, how can I add a user after I install a ????.deb?09:30
zhengIs there a scipt to add user in the .deb? how can I call it?\09:31
jiboumanszheng: lots of existing packages do it already (mysql and apache come to mind), you could take a look at those and follow their lead09:41
zhengjiboumans, hi, thx in advance,09:42
zhengI test it with postgresql, when I install postgres from internet with "apt-get isntall postgresql", it will add a user: postgres;09:43
zhengbut when I download the postgresql's source with "apt-get source", then I dpkg-buildpackage it, but I dont add user for me this time.09:44
zhengbut when I download the postgresql's source with "apt-get source", then I dpkg-buildpackage it into the .deb, then I install these .deb file, but It dont add user for me this time.09:45
zhenghi, jiboumans, I get it, I add some script in debian/postinst.ex10:03
DNS777did any1 tried to compile the mumble-1.2.0 ?10:10
DNS777i have a lot of errors with that :-(10:11
Keybukslangasek: I put a breaks on usplash11:05
Keybukif ubiquity was depending on it, then that was definitely a bug ;)11:05
Keybukcjwatson: if you were using starting-dm, use starting gdm instead11:05
james_wkees: true, but I would like to work offline where possible11:30
Lurepitti: have time to discuss one karmic sru?11:37
pittiLure: just ask :)11:39
Lurekarmic shipped with beta5 version of digikam (as upstream release schedule slipped twice)11:42
Lurewe have one highly visible crasher - bug 45411311:42
ubottuLaunchpad bug 454113 in digikam "digikam crashes when click on download selected" [High,Triaged] https://launchpad.net/bugs/45411311:42
Lureso I suspect the only way for sru is to backport individual fixes (one-by-one)?11:42
Lureno way to bend rule to go with final in such case?11:43
* Lure has done backports, but seems many do not have them enabled and not get fixes11:43
Lurepitti: ^^^11:44
pittiLure: depends if _all_ changes between beta5 and final conform to SRU requirements11:49
pittiif they do, shipping the entire upstream release is okay11:49
pittibut the default mode is "backport that one patch"11:49
=== MacSlow is now known as MacSlow|lunch
dholbachif anybody could moderate ubuntu-devel-announce I'd appreciate it :)11:58
Lurepitti: they don't - problem I see that there are also string changes (due to string freeze on rc)12:00
chrisccoulsonhello dholbach12:00
dholbachhey chrisccoulson12:00
chrisccoulsonhow are you?12:00
Lurepitti: ok, can I at least prepare multiple bugfixes in one sru upload?12:00
pittiLure: seems like backporting would be safer then12:00
dholbachchrisccoulson: good good - how about you?12:00
pittiLure: sure, just make sure to attribute the individual patches to their bug reports12:01
chrisccoulsondholbach - i'm quite tired, but i finish work for the week in an hour :)12:01
dholbachyeeehaw :)12:01
* dholbach hugs chrisccoulson12:01
* chrisccoulson hugs dholbach12:02
directhexno hugs for me? :(12:02
* dholbach hugs directhex too12:02
directhexyays12:03
pittidoko_, robbiew_: for bug 417757, would it be ok to just upload the reapplied patch and thus unfix the two other bugs again? I have to agree to the folks there that it's indeed urgent12:06
ubottuError: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/417757)12:06
* chrisccoulson hugs directhex too12:15
directhex\o/12:15
sebnerpoor directhex :P12:15
* sebner hugs directhex too12:15
=== MacSlow|lunch is now known as MacSlow
doko_pitti: please let's check this in lucid first (will upload after the gcc-4.4 builds are in the archive)14:00
=== BenC1 is now known as BenC
=== ev1 is now known as ev
emgentcjwatson: around?14:09
=== robbiew_ is now known as robbiew
superm1pitti, would it be feasible to specify flags and commands that upstream wants gdb ran with in apport  hooks?14:46
pittisuperm1: not currently, but of course you could change the code to append a field GdbFlags: to the gdb options14:50
superm1pitti, okay. well i'll need to see exactly what's missing and look into doing that then14:51
pittisuperm1: what would be an example option you'd be interested in?14:52
superm1pitti, so here's exactly what upstream asks for: http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.214:52
superm1i haven't compared exactly what is different with the commands applied to gdb on all traces, but upstream was saying that with our (newly functional!) traces that we're submitting upstream, they weren't exactly that14:53
pittisuperm1: hm, most of the gdb options there just seem to affect the gdb CLI, not the trace output?14:56
superm1pitti, ah yeah i think your right14:57
superm1pitti, so when working with a coredump they're N/A.  I'll punt this question back at upstream then to get a specific for what they're not liking about the new traces, they should be useful, although just not the exact same format they're used to seeing14:58
loolkirkland: Hey15:19
loolkirkland: I see you made the transitional qemu depend on qemu-kvm15:20
loolkirkland: Why not -extras?15:20
loolkirkland: e.g. qemubuilder depends on qemu | kvm, we could transition it to the new packages and/or have the transitional packages point at the corresponding new places for the binaries15:21
=== dendrobates is now known as dendro-afk
=== beuno is now known as beuno-lunch
=== dendro-afk is now known as dendrobates
keesjames_w: well, you can't "bzr branch" or "bzr push" or "dput" when offline, so it doesn't seem to bad that you can't do your final upload prep (dpkg-genchanges) until you're online too.15:46
james_wbut if I have the branch prepared and I want to test build then I do a dpkg-genchanges15:46
james_wperhaps we could do something with a marker set by merge-package15:49
james_wI'm a bit nervous about that though15:49
james_wplus, when sponsoring it's not the person that does the merge that usually does the dpkg-genchanges15:50
james_wand MoM doesn't currently help with that anyway15:50
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
=== vorian is now known as Obama
=== Obama is now known as LordObama
geserjdstrand: do you know why there are so many unprocessed sync requests? (like e.g. 489631)16:16
jdstrandgeser: two thoughts: a) resources and b) source format 3.0 (quilt)16:17
jdstrandgeser: I'm on today, but haven't started processing them16:17
geserdoes b) also stop syncs from format 1.0 packages?16:18
slangasekit means that archive admins' time is taken up playing whack-a-mole with the 3.0 stuff for the autosyncs16:19
geserah16:19
=== thekorn_ is now known as thekorn
=== beuno-lunch is now known as beuno
hyperairhas anyone here heard of an issue regarding pulseaudio and usb headsets?16:58
hyperairlag in audio, or something like that16:58
hyperairdtchen: ^^ ?16:59
micahgpitti: can I chat with you about ubuntu-bug?17:32
=== deryck is now known as deryck[lunch]
=== yoasif_ is now known as yoasif
slangasekpitti: where does the code for this new pm-utils-powersave-policy package live?  And is this package being installed by default?17:41
slangasekpitti: (the SATA link power management stuff still concerns me, due to the impact for anyone who's hitting swap)17:42
jdongslangasek: out of curiousity, how bad is the latency when SATA goes into ALPM?17:43
slangasekjdong: I never measured it except holistically17:43
slangasekand by that measurement, it was "pretty bad"17:43
jdongslangasek: ouch. Heh I've only done the same also, and surprisingly I didn't feel the hit. Maybe I'm spoiled with RAM and don't hit swap17:44
slangasekI knew I was memory-constrained already, at the time; I've since solved that underlying bug17:44
jdong*nods*17:47
jdongwell honestly Linux interactivity (ahem) sucks whenever hitting swap in any form...17:47
jdongbut yeah, I can totally see how a couple ms of a sleeping SATA link could exacerbate things17:47
* jdong wonders what happened to Con Koliva's work with swap prefetching17:49
Trewasjdong: it wasn't accepted to the mainline kernel because no-one could provide hard numbers how/when it helps, and then con pretty much gave up17:52
jdong*nods*17:52
jdongit's annoyingly challenging to find ways to quantify desktop interactivity, unfortunately17:53
Trewasagreed17:53
jdongPhoronix does it by... umm... measuring 10000 SQLite inserts with a BFS kernel17:53
jdong(WTF?)17:53
ftadoko_, pitti: are you still working on the ipv6 resolver bug?17:55
fbondHi.  When the update-notifier window is popped up and then sent to the background it briefly steals my keyboard focus.  Does anyone know if this has been reported as a bug?18:07
=== yofel_ is now known as yofel
slangasekScottK: thanks for getting boost1.40 on its feet - fwiw, boost-graph-parallel fails to build because it depends on mpi, so I'm culling it entirely from the package now (there was still one reference in debian/control)18:20
ScottKslangasek: OK.  Thanks.  I thought I saw some reference upstream to graph and graph-parallels being merged.18:21
ScottKslangasek: Also ajmitch has a patch for the boost-python problem he's been on the verge of uploading for some time.  You probably ought to get that from him.18:21
slangasekajmitch: ping?18:21
slangasekwhat's currently broken wrt boost-python?18:23
ScottKI don't remember, but it affects Karmic too.18:23
ScottKIt doens't hit many packages, but the ones it does it hits hard is all I remember18:23
=== MacSlow is now known as MacSlow|break
=== deryck[lunch] is now known as deryck
=== yofel_ is now known as yofel
=== markus_ is now known as thekorn
keespitti: still around?19:36
ajmitchslangasek: pong20:00
slangasekajmitch: hey - ScottK says there's a boost-python fix I should be talking to you about20:00
ajmitchslangasek: yes I talked to ScottK yesterday, thanked him for getting the merge in, I have free time today to upload again20:00
=== Pici` is now known as Pici
slangasekajmitch: ok - not knowing when you'd be around, I went ahead and uploaded my boost fix separately; I guess those builds are now far enough along that it doesn't matter whether the next upload happens now vs. later20:01
ajmitchor if you prefer to upload, patch is in boost1.40 in https://edge.launchpad.net/~ajmitch/+archive/ppa20:01
ajmitchok20:02
ScottKEither way, I no longer TIL Boost, so it's a win.20:02
ajmitchheh20:02
slangasek:-)20:02
smoserkirkland, around ?21:16
maxbI have a merge of Subversion pending sponsorship. Should I just continue to wait and hope? Or should I contact anyone in particular?21:22
ScottKmaxb: Wait and hope.  You didn't happen to fix the lack of kwallet integration did you?21:23
maxbI didn't test it, being firmly in gnome land, but the Debian changes being merged included turning that on21:26
maxbAlthough I'm now having a sudden wondering whether it'll still build in a main-only environment21:26
ScottKmaxb: If it builds, that's better than it did before.21:27
ScottKThere's a bug on that you can take credit for fixing in debian/changelog then.21:28
maxbAh, kdelibs5-dev is in main, I'm safe21:30
ScottKAll of Kubuntu is in Main, so kdelibs is a safe bet.21:31
ScottKmaxb: Since you fixed kwallet, I'll have a look at it.  What bug?21:31
maxbbug 48395321:32
ubottuLaunchpad bug 483953 in subversion "Merge subversion 1.6.6dfsg-2 (main) from Debian unstable (main)." [Undecided,In progress] https://launchpad.net/bugs/48395321:32
ScottKLooking21:32
ScottKmaxb: Explicitly listing the supported versions is preferred over 'all' in the new Debian Python policy that's in draft.  If that's the only change i have, I'll adjust that and upload.21:35
maxbHm21:35
maxbThat is a shame, because it's a cause of debian/ubuntu delta21:36
* maxb hunts the text of the draft21:36
ScottKmaxb: http://lists.debian.org/debian-python/2009/12/msg00009.html21:37
ScottKmaxb: We were originally going to explicitly deprecate all, but since it's unfortunately quite common in the archive we thought it would be too soon for that.21:38
maxbInstall of "all", we could make it say ">= 2.something" instead, and that would be OK ?21:39
=== elky is now known as Guest85008
ScottKYes.21:40
ScottKmaxb: What does it say in Debian right now?21:40
maxbIt says individual versions21:40
maxbI changed it so the Ubuntu delta didn't itself have to be adjusted when Ubuntu changed its own default Python version, with a view to feeding that back to Debian21:41
maxbuh, s/default version/set of supported versions/21:42
ScottKLet me look21:44
ScottKmaxb: What Debian has is OK.21:44
ScottKThat it covers more Python versions than we have is not a problem.21:45
ScottKThat's meant to be a list of versions it could support, not just the ones used in the current release.21:45
ScottKIf that's the only diff, this should be a sync.21:45
maxbOh, no, that's far from the only diff21:46
=== Simira_ is now known as Simira
ScottKmaxb: Would you please do up a debdiff for me then?22:00
maxbScottK: Sorry, did I miss anything in the netsplit?22:00
ScottKmaxb: I asked you to make a debdiff for me.22:01
ScottKThis new fangled bzr stuff I'm still working on learning.22:01
maxbHeh22:01
maxbWe didn't reach a conclusion (that I saw) on what the XS-Python-Version: should look like22:01
maxbAlso, owing to how part of the work I did with this merge was stitching up some weirdness that the bzr importer created, it really needs to actually be bzr pushed, rather than letting the importer re-derive it from an upload22:02
ScottKmaxb: Oh, here's what I said on that:22:04
ScottKThat it covers more Python versions than we have is not a problem.22:04
ScottKThat's meant to be a list of versions it could support, not just the ones used in the current release.22:04
ScottKSo it's fine as is from Debian.22:05
maxbIn that case, I guess I'll just uncommit the last revision from the bzr branch22:06
maxbOr should I re-add 2.4, which we previously dropped, as an Ubuntu delta?22:08
maxbThe latter, I guess22:09
=== lamont` is now known as lamont
ScottKIt does no harm, so don't diverge over it.22:11
maxbIs there any convention on where in the changelog I should write LP bugnumbers closed by merge of Debian changes?22:14
ebroderProbably on the "Merge from Debian" line?22:15
slangasekI find all the available options unsatisfactory, personally :)22:15
ScottKslangasek: For which point?22:16
slangasekScottK: for LP bugnumber convention on fixes merged from Debian22:16
ScottKAh.  Right.22:17
maxb  * Merge from debian unstable (LP: #483953).22:18
maxb    Includes enabling kwallet support (LP: #481792, #466078).22:18
maxb    Remaining changes:22:18
maxb^ Acceptable ?22:18
ScottKI'd go for that.22:19
cody-somervillelmao22:22
cody-somervilleDue to a bug in Debian's infrastructure a ton of stuff migrated to testing from unstable when it shouldn't have.22:22
ebroder"Whoops"22:23
cody-somervilleSo much for the little experiment of syncing from testing instead of unstable, lol.22:23
ScottKmaxb: I have to run out for a while, so just shove your debdiff in the bug and i'll look at it later.22:23
ScottKcody-somerville: It'll be more important later anyway.22:23
ebroderHmm...I'm waiting for a package to hit testing. I wonder if it was affected22:23
maxbScottK: Thanks - did you see my comment about needing the branch pushed too, even if you upload by the debdiff?22:23
ScottKmaxb: I did, but I didn't understand it.22:24
ScottKWe can chat later as I really need to run.22:24
maxbI shall elaborate upon it in the bug22:24
ScottKOK.  Good22:24
CzesiuHello22:25
CzesiuCould you tell me what's wrong with call: requestsync -d unstable rrdcollect 10.04?22:25
CzesiuReplacing 10.04 with lucid also doesn't work as expected22:26
maxbNothing obviously wrong, what breaks?22:26
CzesiuI'm using ubuntu-dev-too 0.83debian1 from22:26
CzesiuE: The versions in Debian and Ubuntu are the same already (0.2.4-2). Aborting.22:26
=== dendrobates is now known as dendro-afk
maxblucid is correct here, 10.04 is not, I would say22:26
CzesiuBut there is new release in unstable at the moment22:27
maxbHow recently uploaded?22:27
Czesiu4 days ago22:27
maxbHmm22:27
Czesiuhm, I checked 6 days ago22:28
maxbOk, it breaks for me too, this seems like a bug22:28
CzesiuThanks, I'll report it.22:29
maxbCzesiu: Wait 5 minutes please, I'm just investigating22:30
Czesiuok22:30
maxbHmm, LP itself knows about the new version22:31
CzesiuMay I check it too?22:32
maxbWhat do you mean?22:32
Czesiumaxb: what LP knows about the latest release from Debian22:34
maxbYou may see it here: https://launchpad.net/debian/sid/+source/rrdcollect22:34
Czesiumaxb: oops, I've never look carefully on that page :)22:35
maxbCzesiu: I'm completely confused as to why requestsync is getting it wrong, but I can't find anything wrong with what I get if I manually drive the Launchpad API, so I think a bug on requestsync is the right way to go22:41
Czesiumaxb: I see there is new version on Debian. I'll upgrade it and if the bug persists I'll report it22:42
maxbCzesiu: Oh. bah. It's apparently hitting some php script instead of launchpad :-/22:46
maxbI didn't know about that22:46
maxbCzesiu: It's apparently getting confused because the new version has not build on all architectures in Debian22:49
maxbYou can check it yourself with rmadison -u debian -a source -s unstable rrdcollect22:49
Czesiumaxb: hm, it's not build only on hurd-i386, which is not release critical IIRC22:50
maxbIndeed. But it's enough to accidentally confuse requestsync22:50
Czesiumaxb: thanks, I will add this suggestion to bugreport too22:51
michalski-bjis Cody Somerville in by chance? (online, avail.)22:51
michalski-bjneed to ask him a few questions22:52
maxbCzesiu: Please add the actual current output of "rmadison -u debian -a source -s unstable rrdcollect" to the bug report as well22:52
maxbHmm. What is ScottK likely to have wanted a debdiff *against*, given this is a new upstream version?23:03
ScottKmaxb: The current Debian version.23:03
maxbAha23:04
ScottKI've already pulled that from Debian.23:04
mun24how to get the error code for connect socket error -123:07
Czesiumaxb: thanks for support. #560758 has been submitted to Debian BTS.23:08
maxberrr, the *debian* bts?23:08
maxbrequestsync is an ubuntu program23:09
Czesiumaxb: right. I'm developing on Debian, but I also try to take care of ubuntu bugs reported for my packages. And I am using ubuntu-dev-tools available in Debian23:09
=== dendro-afk is now known as dendrobates
maxbAh. It would probably be best to have filed the bug "upstream" in Launchpad23:10
ccheneydoes linux just work out of the box with 4k sectors?23:10
ccheneyhttp://www.engadget.com/2009/12/11/western-digital-advanced-format-promises-slight-boost-in-usabl/ <- saw this a few min ago23:10
Czesiumaxb: hm, let me check that, I'm still not accustomed to launchpad :)23:11
directhe`ccheney, man mkfs.ext223:12
ccheneyah found this thread too http://www.gossamer-threads.com/lists/linux/kernel/103914123:12
directhe`oh, hardware drivers need support too? hadn't thought of that23:13
ccheneyoh ugh this is another one of those we need uefi immediately things23:14
ccheney"Most likely, the universe will explode at this time..." ;-)23:16
maxbScottK: I'm afraid your advice about it being OK to include versions of Python we don't have in XS-Python-Version is apparently not correct.23:16
maxbThe build is FTBFS in my PPA23:16
directhe`ccheney, what's wrong with regular EFI? all the cool kids have EFI23:18
Czesiumaxb: I see that developer of Debian package for ubuntu-dev-tools is also a member of the same team on LP, so I left it as it.23:21
ccheneydirecthe`: hmm i thought it was all uefi now, i haven't actually ever seen a system with it other than macs (and on those never seen what theirs looks like)23:23
ccheneywe should be seeing a lot of *efi soon though as 2TiB is limit for bios aiui23:23
ccheneydirecthe`: as best as i can tell current efi is called uefi23:24
directhe`ccheney, i have itanium kit with EFI, and a mac with EFI23:27
directhe`ccheney, iirc the only "normal" systems with EFI are a limited number of motherboards from MSI23:28
directhe`plus you need Vista x64 SP1, or Windows 7, to boot EFI in "native" mode, so that's hindered adoption somewhat23:28
ccheneydirecthe`: yep, but the limit of 2TiB drives should force more deployment of EFI soon23:37
directhe`ccheney, you'd think so23:37
directhe`ccheney, 32-bit windows is still popular amongst people with 4 gig of ram...23:37
ccheneydirecthe`: heh yea23:38
ScottKmaxb: Weird.  OK.23:45
ScottKmaxb: Where's the build log?23:45
maxbhttps://launchpad.net/~maxb/+archive/ppa/+build/1391193/+files/buildlog_ubuntu-lucid-amd64.subversion_1.6.6dfsg-2ubuntu1~~testbuild1_FAILEDTOBUILD.txt.gz23:45
maxbI've just done a local cowbuilder build with XS-Python-Version: >= 2.4, and that works. I'd like to go with that, if it's acceptable to you23:46
ScottKmaxb: That's good.23:46
maxbpeterS will likely take that into Debian, I would imagine23:47
ScottKmaxb: That's, IIRC, explicitly preferred in the new draft Python policy, so I would hope so.23:50
ScottKmaxb: I think that's a Python support bug, btw (your build failure).23:50
maxbI can believe that23:51
ScottKWould you please file an Ubuntu python-support bug on that?23:53
maxbIt'll take more research than I have time for tonight, but I'll scribble myself a note23:53
ScottKThanks.23:54
maxbScottK: Do you mean python-support? pyversions is contained in the 'python' source23:59
ScottKmaxb: I do because I think it's python-support that is interpreting the field.  Subscribe me to the bug and I'll move it if need be.23:59
* ScottK has to run again.23:59

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