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

=== JayFo is now known as JFo
=== dous__ is now known as dous
=== Whoopie_ is now known as Whoopie
=== dendro-afk is now known as dendrobates
=== asac_ is now known as asac
dholbachgood morning07:05
mvohey dholbach07:07
dholbachhey mvo07:07
dholbachmvo: ALTER!!!!!07:07
* dholbach hugs mvo07:07
mvo:)07:07
* mvo hugs dholbach07:07
dholbachUp early?07:07
mvoyes07:07
dholbachsame here :)07:08
jmlare we the upstream of the acpi-support package?07:10
jmldholbach, hello!07:10
dholbachhiya jml07:11
dholbachjml: what about that UDW session? :-D07:11
jmldholbach, last week of January, right? I'll be in the UK that week.07:12
dholbachhttps://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep is the preliminary schedule07:12
jmldholbach, I was just about to ask :)07:12
dholbachjml: acpi-support is in debian too07:12
jmlI'm trying to find the upstream vcs for it.07:13
dholbachlet me see07:13
jmldholbach, I can do the Friday 1800 slot.07:13
dholbachwow, it's even in sync with debian in lucid07:13
dholbachjml: which topic? lplib? :)07:14
jmldholbach, I can do lplib. I could also do an "Ask Launchpad" session07:14
jmldholbach, whichever you think would be more interesting.07:14
dholbachjml: which one would you prefer?07:14
jmldholbach, I have no preference.07:15
jmlwow, it's going to be exciting being able to actually attend some of these sessions :)07:15
jmldholbach, probably lplib is best.07:16
jmldholbach, keep it concrete & code-y07:16
dholbachhum, it could be that we're "upstream" for acpi-support07:16
dholbachit's a bit of a weird divergence07:17
dholbachslangasek might know more07:17
dholbachthe debian/copyright of the debian source package says something like "It was downloaded from http://archive.ubuntu.com/....."07:17
dholbachjml: shall I pencil you in? session title? :)07:18
* jml tries to think of a clever title that doesn't violate the CoC07:19
dholbachhaha07:19
* dholbach hugs jml07:19
jmlI'm all out of clever. How about "Meet launchpadlib"?07:20
StevenK"launchpadlib and you: Making access to Launchpad easier" ?07:21
dholbachsounds good to me :)07:21
jmlI'm just going to make lp:~ubuntu-core-dev/acpi-support/trunk the dev focus for acpi-support. slangasek can correct me if I'm wrong.07:22
dholbachjml: sounds good to me07:22
dholbachjml: thanks a bunch for helping out with UDW :)07:23
jmldholbach, my pleasure.07:23
dholbachwe have a fantastic line-up this time07:23
dholbachI mean we always do :)07:23
jmldholbach, yeah. I'm looking forward to heckling at rockstar's talk :)07:24
dholbachhaha07:24
jmlNg, hello.07:25
jmlNg, could I persuade you to set the development focus branch for https://code.edge.launchpad.net/evdev ?07:25
dholbachwho can I interest in another UDW session? there's still 4 open slots!07:26
dholbachhttps://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep07:26
=== dendrobates is now known as dendro-afk
slangasekjml: that should work07:31
jmlslangasek, thanks.07:31
* jml is doing a little mindless data gardening07:32
wgrantCan I convince somebody to sync something like jack-tools? 3.0 support works now, and I'd like to see that syncing actually works.07:35
wgrant(jack-tools has all the things that are likely to trip Soyuz up, and it has no real changes, so it seems like a good test)07:36
slangasekwgrant: I synced one already07:38
slangasek(abraca, now in dep-wait)07:38
wgrantslangasek: But it at least hit the buildds? Good.07:38
slangasekyep07:39
slangasekthanks for all your help to get v3 happening :)07:40
wgrantnp07:40
wgrantSorry it took so long.07:40
=== tkamppeter_ is now known as tkamppeter
junjunhi08:08
junjuni get the source of 9.10 kernel, and found that Ubuntu patches the vanilla kernel. where can i find the information on the patch?08:09
junjuni want to know which change Ubuntu made to the vanilla kernel08:09
junjunthe patch to 2.6.31 is pretty big.08:09
junjunexcept AppArmor, and ndiswrapper, what else Ubuntu change to the kernel?08:10
dholbachjunjun: try asking in #ubuntu-kernel (and maybe wait a bit, the folks might still be asleep :-))08:13
junjundholbach: thanks!08:13
pittiGood morning08:14
pittislangasek: right, I think there should be an extra field in the workitems table eventually; but oh well, kees already fixed it for now08:16
junjunfrom Ubuntu 9.10, we patch kernel with Non-Exec stack patch. Is that exactly the patch named Exec-Shield from Redhat?08:21
junjunif not, what is the difference with Redhat's Exec-shield??08:21
junjunoh well, it seems Ubuntu uses the patch from Redhat (Fedora)08:24
keesjunjun: "execshield" is the entire unbrella project that Redhat put all their hardening features under.08:25
keesjunjun: Ubuntu's kernel carries the last remaining piece of that which is not already upstream, the partial nx-emulation for i38608:25
junjunkees: so you mean we only port the kernel patch to Ubuntu, but not the rest?08:25
keesjunjun: everything else already in the kernel, userspace, etc.08:25
keesjunjun: some details here: https://wiki.ubuntu.com/Security/Features08:26
junjunit is interesting to know, thanks08:26
keessure, np08:26
junjunso far, it seems only kernel of Fedora (and Redhat, CentOS) and Ubuntu uses this patch.08:26
keesjunjun: afaik, SUSE uses it as well, but I haven't personally verified it.08:27
junjunthe rest like OpenSuse, Debian, .... dont. is that correct?08:27
keesDebian does not use it, correct.  I'm unsure about SUSE08:27
junjunkees: ok, i will check that08:27
keesjunjun: as linked from https://wiki.ubuntu.com/Security/Features#Non-Exec%20Memory I have a simple regression test that can help validate a given kernel.08:28
keesjunjun: the patch itself is here: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-karmic.git;a=commitdiff;h=eb56f42a4bc9c671a19dcf8fd36eb3f341de7dfa08:29
keesit's based on the bits from http://www.codemonkey.org.uk/projects/execshield/08:30
junjunkees: very clear, thanks!08:32
junjunkees: why this patch doesnt work for 64bit kernel??08:33
keesjunjun: the cs-limit approach doesn't make sense for 64bit, and nearly all 64bit system already implement non-exec in hardware, so the emulation is unneeded.08:33
=== doko__ is now known as doko
junjunwhat do you mean by "cs-limit approach doesn't make sense"??08:34
keesthe partial nx-emulation patch uses the cs segment limit to split userspace into two region (one executable, the other not).  as I understand it, there's no reason to do this for 64bit, since 64bit is PAE, which implements the NX bit in the page table, so no artificial separation is needed.08:35
tseliotpitti: shall I make nvidia depend on acpid and acpi-support or would the former suffice?08:41
pittitseliot: just acpid, please08:41
pittiacpi-support is unrelated to what nvidia does, and is still on the "to die" list08:41
tseliotpitti: ok, the latter seemed too much as a dependency to me but I wanted to be sure08:42
fabbionezul: ping? is there a bacula 3.0.X backport for hardy anywhere?08:45
tkamppeterpitti, can you upload Poppler for me, debdiff on bug 293832? Thanks.09:02
ubottuLaunchpad bug 293832 in poppler "printer prints page at wrong position, page cut" [High,Fix committed] https://launchpad.net/bugs/29383209:02
pittitkamppeter: hi! sure09:24
pittitkamppeter: should the other tasks be "invalid"ated then?09:25
Ngjml: hey, is that still required?09:26
tkamppeterpitti, I think so.09:26
pittitkamppeter: uploaded09:26
Ngjml: well, I suppose I can see that there's no focus set, so I suppose a better question would be what would you like it set to? ;)09:26
tkamppeterpitti, the non-Poppler tasks are invalidated now, thanks for uploading.09:28
pittiogra: bryce_ wrote a basic test plan for touch screens to check that the udevification didn't break anything (https://wiki.ubuntu.com/X/Testing/Touchscreen); does that look reasonable to you, or is there something important that should be added there?09:28
mdzNg: re: the mkinitramfs error, 17-12-2009 11:30:21 < slangasek!n=vorlon@minbar.dodds.net: mdz: yes, Keybuk said he was going to fix that today09:50
Ngah, sorry09:51
StevenKpitti: What was the magical gvfs-mount option again?10:24
pittiStevenK: for doing what?10:24
StevenKpitti: A USB key I just inserted is not automounting10:25
pittiStevenK: so you want to mount it manually? gvfs-mount -d /dev/foo10:28
StevenKsteven@liquified:~% gvfs-mount -d /dev/sdb10:28
StevenKNo volume for device file /dev/sdb10:28
pittiso gvfs-mount -li doesn't have /dev/sdb then?10:30
pittidoes devkit-disks --mount /dev/sdb work?10:30
StevenKpitti: No, gvfs-mount -li does not have sdb10:31
StevenKdevkit-disks ... does work, though10:31
pittiStevenK: does gvfs-mount -oi say anything when you plug this in?10:34
StevenKpitti: Yes, and it actually mounted it this time.10:35
* StevenK curses heisenbugs10:35
pittifree: can you please make bug 455217 public, so that it can be SRU-processed?10:50
ubottuBug 455217 on http://launchpad.net/bugs/455217 is private10:50
freepitti: oops, sorry, just made it pubblic, thanks10:51
pittifree: and please make sure that all the fixed bugs have proper ubuntu package tasks10:51
freepitti: I think I'm not entitled to create tasks? or how do I?10:52
freepitti: I couldn't figure out how to do it last time10:52
pittifree: "Also affects distribution" -> ubuntu/landscape-client10:52
freepitti: okay, on all the bugs related to the SRU?10:52
pittiright10:52
pittiwe need to track their fixes/status in all releases10:53
pittiI started adding them10:53
freeokay10:54
pittiall added now, I think10:55
pittifree: would you mind reviewing the bugs and closing the lucid tasks which are already fixed?10:55
freepitti: sure10:56
pittithanks10:56
freepitti: I guess I can use "Fix released" for lucid tasks right?11:06
pittifree: if they are fixed in lucid, yes11:06
freepitti: okay, so that's done11:06
pitticheers11:07
freepitti: there a now bugs that have the Lucid task with fix-released, and bugs that have a new Ubuntu task (no release-specifc tasks yet)11:07
freepitti: so, I don't think I can open release-specifc tasks, can I?11:08
pittifree: you can nominate11:08
freepitti: what does that mean exactly?11:08
pittifree: the tasks won't be created yet, but they will shown as "proposed for jaunty-update", etc.11:09
pittiI'll accept them while reviewing11:09
freeokay11:09
freepitti: I can't figure out how to nominate, I can't see any "nominate" or similar button in the bug page UI..11:12
pittifree: "Target to release"11:12
pitti(with the ubuntu task selected, not the upstream task)11:12
freepitti: and how do you select the Ubuntu task? clicking on it just brings me to the landscape-client source page in the ubuntu LP project11:17
=== jelmer_ is now known as jelmer
pittifree: hm; just change the URL to /ubuntu/+source/landscape-client/... ?11:18
pittior change anything else in the ubuntu task11:19
pittilike priority, assignee, etc.11:19
freepitti: okay, manually entering the url like you suggest works, but changing something the ubuntu task doesn't, I couldn't find any way to do it except manually entering the url11:22
freepitti: okay, the bugs without specific release tasks should be all nominated now (for intrepid to lucid)11:26
pittifree: can bug 455217 be fixed in lucid, too?12:00
ubottuLaunchpad bug 455217 in landscape-client "Handle release-upgrade messages in the packagemanager plugin" [Medium,Fix committed] https://launchpad.net/bugs/45521712:00
freepitti: yes12:01
freepitti: just marked it as Fix released12:02
pittigreat12:02
=== Hellow_ is now known as Hellow
=== vila is now known as vila-lunch
=== ara_ is now known as ara
=== mac_v_ is now known as mac_v
=== vila-lunch is now known as vila
zulfabbione: no there isnt a backport13:16
fabbionezul: thanks, I have done myself13:16
zulfabbione: cool13:16
fabbionezul: you might want to take care of Lucid release notes for upgrading tho13:16
fabbionezul: you need to have a director > 3.0 to talk to fd > 3.013:17
fabbionezul: dir 3.0 can talk to fd in any version but not the other way around13:17
zulfabbione: thanks for the heads up13:17
fabbionezul: so basically, if you want LTS to LTS upgrade plan, the director machine needs to be done first13:17
zulgotcha13:18
zuljames_w: did the import failed for samba i dont see it in launchpad?13:46
james_wzul: it was stuck in the queue, I've set it to run next13:47
zuljames_w: thanks13:48
Keybukmdz, Ng: it was stuck in NEW :p14:06
=== asac_ is now known as asac
Chipzzhttp://www.advogato.org/person/robertc/diary.html?start=12914:27
Chipzzthis gets a major ++ from me14:27
ChipzzI would hope this mentality would propagate to more debian and ubuntu developers14:27
joaopinto_I really don't see the relation between upstreams doing their own packaging, and including the debian/* in the upstream source14:31
joaopinto_I agree with the first, not with the second14:32
james_wwhy?14:32
joaopinto_because debian/* use dependencies or rules some times tweeaked for specific distros/releases14:33
joaopinto_there is no advantage on having them including on the source, there is the advantage that other packagers will need to patch or rm the upstream debian/*14:33
joaopinto_ops, disadvantage14:34
joaopinto_upstreams doing the packaging is a social subject, including debian/* in the source is a technical one14:35
james_wupstream sometimes has code that doesn't work on Ubuntu, so there is a disadvantage that we sometimes need to patch it, so upstream shouldn't ship any code14:36
joaopinto_james_w, source code is generic, as far as possible, debian/rules are not, and you failed ot mention what at the advantages of having it include on the source :)14:38
joaopinto_ops, I meant debian/*14:38
james_wdebian/* are generally, otherwise we wouldn't be able to derive from Debian without making vastly more changes than we do14:38
Ngjoaopinto_: I like it when I unpack a tarball of some new software and I can just build a package out of it immediately. That's why I include a debian/ in my projects :)14:40
ScottKIs Google Talk audio supposed to be working with Empathy in Karmic?14:40
ScottKNg: The problem is most upstreams that attempt to do this, don't know a lot about Debian packaging.14:40
james_wScottK: I don't see that as a reason to tell every single upstream that does it off, as seems to be the culture currently14:41
joaopinto_james_w, you are refering to the general case of Debian versus Ubuntu, the debian/* world does not stop there, and still, your sentence is not accurate when you need to backport14:41
NgScottK: I would absolutely fit in that pot, which is why I merge back in the correctness from nxvl's packaging :)14:41
joaopinto_Ng, if you want your projects just to build, provide a .dsc file14:42
joaopinto_Ng, you will help those which "just want to build" per your rules, without interfering with others that want to build in another way14:43
Ngjoaopinto_: I don't follow, how does a .dsc help?14:43
james_wfor a .dsc file to make any sense you have to have a debian directory, no?14:43
joaopinto_Ng, dget file.dsc && debuild14:43
joaopinto_no, you just need the .dsc, diff, and orig14:44
joaopinto_and everone is happy with a single dget command, versus a wget source14:44
StevenKjoaopinto_: Which you can't build without a debian directory in the source14:44
joaopinto_StevenK, you can, because I am refering to a .dsc which points to both the orig.tar.gz and the debian diff14:45
StevenKjoaopinto_: And what do you think is in the debian diff? The debian directory.14:46
joaopinto_StevenK, right, but provided as it should as a diff, not included on the original source14:46
james_wjoaopinto_: so you refuse to let us re-use and collaborate on that debian/ directory in the most natural way, as we do the rest of the code?14:47
james_wno thanks14:47
joaopinto_james_w, no, but I don't agree that the proper place for packaging collaboration is the source, you do collaboration for a group at the cost of other group14:48
ScottKAnother issue is that improvements to Debian packaging need a new upstream release if that's the canonical source for them.14:48
james_wit's not a cost that means much14:48
james_wit doesn't have to be the canonical source, or diff.gz can make modifications14:49
Nghow much variation is there in the packaging of debian derivatives? talk of costs without numbers seems a bit pointless14:49
joaopinto_james_w, ah ok, so you assume that your need for collaboration is more important than others needs for a clean source :)14:49
james_wimprovements to the code don't need a new upstream release, we are generally happy to patch and feed the changes back for the next release14:49
joaopinto_that's something personal, nothing to argue about :)14:49
joaopinto_james_w,  upstreams should be able to collaborate if the debian/* dir is kept in any VCS14:52
Keybukhuh?14:55
Keybukupstream should never put the debian/ directory into their VCS14:55
Keybukthat's just wrong14:55
joaopinto_the only good reason I see on this change would be, "Hey you cand build .debs from the source", when there is no one able to set up a PPA or get it into the repositories14:56
Keybukanyone can have a PPA14:56
joaopinto_but again, that is not collaboration :)14:56
joaopinto_Keybuk, we are debating that http://www.advogato.org/person/robertc/diary.html?start=12914:56
Keybukthere's no loop or step to getting one, just create a Launchpad account14:57
KeybukI disagree strongly with Robert ;)14:57
Keybukone of the biggest problems I ever have, as a distribution maintainer, is upstreams who put the packaging into their tarball14:57
Keybukbecause it's always wrong14:57
Keybukand it makes it very hard for us to modify it14:57
jcastroit should just be another branch imo14:58
Keybukin certain ways, for example removing a debhelper config file, it becomes impossible to modify without repackaging the software entirely14:58
jcastrolike how we're doing for UDD14:58
joaopinto_Keybuk, that was the pointing I was making14:58
Keybuk(because our source package format doesn't permit removing files in the diff.gz)14:58
james_wKeybuk: to be fair, Rob says we should fix that.14:58
Keybukyou also end up the situation where it looks like it's got a package14:59
Keybukbut the package is wrong14:59
Keybukso people think they can grab the upstream tarball14:59
Keybukbuild it14:59
Keybukand then install it on their distribution14:59
Keybukthat could go *badly* wrong14:59
Keybuklook at the .spec file issues between SuSE and RedHat for an example ;)15:00
LaserJockhmm, so what happens if upstream has a debian/ but Debian, Ubuntu, <any old .deb-based distro> wants to package in different ways?15:02
LaserJockdoes the upstream need to pick which distro to support? or do they use something like control.in?15:03
KeybukLaserJock: it gets more fun15:04
Keybukupstream might disagree with the way distributions change their packages15:04
Keybukand deliberately make it hard for distributions15:04
Keybuk(this happens)15:04
NgKeybuk: why are you packaging things in isolation from the upstream? if their debian/ is wrong they must care enough to have one, so presumably want a correct one?15:11
KeybukNg: it means they want one they *think* is correct15:12
Keybukthat's so far removed from "a correct one" that they may as well be in different universes15:12
NgKeybuk: I think they want one that produces a working package15:13
Keybuksee, that's the problem15:13
Keybuklet me give you an example15:13
ScottKNg: Which is a small subset of what it takes to be correct.15:13
KeybukI have an upstream, who we'll call Ted15:13
Keybukhe maintains a piece of software, which we'll call e2fsprogs15:13
Keybukand he also happens to put the entire debian/ directory in his package15:13
NgTed sounds like he cares about his users!15:14
Keybuktricks that Ted has done in the past include adding code to his debian/rules to disable features on Ubuntu15:14
Keybukbecause he thought that Ubuntu was doing things wrong15:14
Keybukturned out that was a bug in his kernel code he was hiding15:14
Keybukthe only reason he was getting bug reports from Ubuntu users is because we have lots of users15:14
Ngso to avoid fixing a kernel bug we just take the packaging away from him?15:15
KeybukTed has deliberately blocked library transitions15:15
Keybuketc.15:15
Keybukno15:15
KeybukI'm saying that in the released upstream tarball is the wrong place for packaging15:15
Keybukfor a start, what's right for Debian might not be right for Ubuntu15:15
Keybukeven though the packaging files are the same)15:15
KeybukI think the right way is what we do on Upstart15:15
Keybukwe have a tarball we release without packaging15:15
Keybukthen an upstream branch which is the tarball + packaging15:16
Keybukand we collaborate on that15:16
NgI'd concede plumbing stuff, but I like being able to grab a tarball or vcs checkout of some application and have it be ready to build15:16
Keybukif distros need their own tweaks, they branch off it15:16
james_wso one person spoils it for the rest of us?15:16
KeybukNg: build for Ubuntu or build for Debian?15:16
Keybukor build for SuSE or build for RedHat?15:16
Keybukif you build something for Ubuntu, it might not work on Debian15:16
Keybukand vice-vera15:16
james_wplus, the same arguments can apply for code, though admittedly less often15:16
Keybukjames_w: one of the major portions of packaging is patches to the code15:17
Keybukthat's kinda the point15:17
Keybukhere's a better question for you15:17
Keybukwhy do we have packaging at all?15:17
Keybukif the upstream tarball is perfect as-is15:17
Keybukwhy do we *need* a debian directory in it?15:17
Keybukwhy can't we automate the process of taking an autoconfery tarball and turning it into debs?15:17
Keybukpackaging is all about hacks to the code15:17
Keybukpackaging is changing the code to fit the distribution15:18
Keybukor changing the default configuration of the code or result15:18
Keybukchanging install paths15:18
Keybukremoving files we don't want15:18
Keybukadding ones that aren't incldued15:18
Keybuketc.15:18
Keybukif the upstream tarball is correct15:18
Keybuk(which it often is in a large majority of the cases)15:18
Keybukyou don't need packaging15:18
Keybukthis is probably the primary reason I don't like packaging-in-upstream15:19
james_waside from the issue of autoconf/setup.py/Makefile.PL etc., yes15:19
Keybukyou end up with a qmail-esque bizarre situation where you have "the upstream code", and "the upstream approved patches to the code"15:19
james_wit strikes me you should write all this in a blog post and propose your preferred way instead15:19
Keybukwe discussed this in autotools a while back15:20
Keybukthe only bit you're really missing is knowing which files are libraries, which are headers, which are data, which are docs, etc.15:20
Keybuka lot of that can be guessed by path15:20
Keybukbut you kinda want a manifest-like file that hints to a packaging system15:20
Keybukyou also want a standard format file for things like source descriptions, licencing, etc.15:21
=== binitamshah is now known as binitamshah|away
=== dendro-afk is now known as dendrobates
LaserJockhmm, maybe you would want all that in a directory, maybe you could call it debian/ or something ;-)15:24
KeybukLaserJock: the idea is that it'd be useful for everyone15:25
Keybukand the debian formats are ... bizarre15:25
Keybuklike, why the hell would an upstream want to have a separate changelog?15:25
Keybuktheir version number is already in configure.ac15:25
Keybukunfortunately the discussion kinda veered towards "looks a lot like a .spec file" <g>15:25
LaserJockheh15:25
LaserJockthe problem I see mostly though is upstreams either 1) don't want to package at all or 2) don't want to package for several different distros15:26
ScottKOr don't want to deal with distros at all and just have their users get packages from them15:27
LaserJockyes15:27
ScottKOne of my upstreams (who uses Fedora) didn't see the point of getting his stuff into distros.15:29
ScottKI got one of his packages into Debian/Ubuntu and he mentioned he'd gotten a lot of new users show up right after I did that on his mailing list.15:29
ScottKSuddenly he got it and he packages his stuff for Fedora now.15:29
ionHad he been tuomov, he’d have hated you for getting new users.15:30
Ngpopcon numbers can sometimes make a good impression :)15:30
LaserJockmust upstreams I know just don't have time to learn .specs and debian/ etc.15:31
LaserJock*most15:31
ScottKThis guy was distributing rpms already, he just hadn't seen the point in going to the trouble to get it in a distro.15:32
LaserJockand then there are upstreams that fork dependencies in PPAs and call it good ;-)15:33
jambarry: ping15:34
jamyou sent a mail as "barry@canonical.com" that got blocked going to udd15:34
jamdid you want me to add that address?15:34
barryjam: dang.  yes please!15:35
jamhmm.. it says the sender is "now" a member of the list already15:36
jamso apparently it should just work now15:36
jamI know I have a few accounts that get a bit confused sometimes15:36
barryweird, maybe it got held for other reasons15:36
Keybukif upstreams did their job properly, we wouldn't _need_ distros ;-)15:36
jamI'm pretty sure it thought you weren't a member for a bit15:36
=== freeflyi1g is now known as freeflying
jambarry: ahh, I see why now15:37
jamReason:  SpamAssassin identified this message as possible spam (score 3.8)15:37
barryouch.  i should use fewer ! and $15:38
jambarry: though the message that got through was: X-Spam-Status: No, score=-2.2 required=4.5 tests=ALL_TRUSTED,AWL,BAYES_00, DATE_IN_PAST_03_06,MIME_BASE64_NO_NAME,MIME_BASE64_TEXT autolearn=ham  version=3.1.715:38
jamhad you posted to udd before?15:38
jamAs it looks like SQLGrey may have also been involved15:39
barryjam: yep, lots15:39
jam(I'm pretty sure you have)15:39
jamoh, and that sqlgrey stuff may be my local machine, not canonicals15:39
jamyeah, it probably is15:40
LaserJockwas barry trying to sell us on the "effects" bzr can have on our personal life? ;-)15:40
jamapparently my mail host likes you15:40
jambut canonical's doesn't :)15:40
jambarry: so my guess is that SA doesn't like "date in past"15:41
jamsince it seems to think that it was sent at 4am15:41
jamand then the fact that your mail client encodes everything as base6415:41
* barry restarts ntpd15:41
jameven though it is just text15:41
* persia reads backscroll and yet again wishes that `gzcat foo.diff.gz | patch` was capable of deleting files15:41
Keybukpersia: it is15:41
KeybukIan Jackson just disagreed with being able to do it, so had dpkg refuse to do so15:42
barryjam: i'm posting from a vm and when the host sleeps, my time gets out of whack.  unfortunately, that also seems to kill the ntpd service for some reason :(15:42
Keybukpersia: I think the reason dpkg refuses is quite logical15:43
Keybukpeople might think that patching a file out of the tarball is an acceptable way to solve DFSG issues15:43
Keybukwhen, of course, it isn't15:43
persiaThat's all!15:44
Keybukbecause Debian would still have been distributing the file in the tarball15:44
macoarent you sposed to do that in the orig?15:44
Keybukof course, nobody believed people would ever put debian directories in the tarball ;)15:44
persiaI agree that it's not an acceptable way to make something DFSG-free (the tarball is shipped anyway), but it would mean that suddenly it wouldn't *matter* if upstream ships packaging (debhelpers -i helps to some degree, but only to some degree)15:45
Keybukit still makes your life hard15:45
Keybukyou'd have to review every new upstream version carefully15:45
persiaCan we revisit that, or is that reviving horses that are best forgotten?15:45
Keybuk"grr, upstream added a debian/wibble.foo file that I missed, and now my package fails to install"15:45
Keybukif we were to revisit anything basic like that, we should probably just invent a new source package format15:46
persiaYeah, but one should be at least reviewing the file listing and dpkg --contents listings anyway, at an absolute minimum.15:46
Keybukput it in an ubuntu/ directory15:46
Keybukand then be done ;)15:46
persiaHrm.  tempting....   but maybe not.15:46
Keybukif Colin ever gets hit by a bus, it'll be one of my first jobs ;)15:47
KeybukMark's been wanting to do that since day one, so I know I'll be allowed <g>15:47
* pitti tosses http://cdimage.ubuntu.com/daily-live/20091218.1/ Keybukwards15:48
Keybukpitti: way ahead of you ;) already rsync'd down and updating TFTP and NFS roots15:48
Keybukwill be interesting to see how this works15:49
KeybukI got good numbers on ratchet15:49
Keybukand I'm getting increasingly convinced that ratchet is slightly slower than max15:49
pittigood luck!15:49
james_wwhat's new in this image?15:51
pittijames_w: Keybuk's speedup work from today15:51
pitti(initramfs-tools, etc.)15:51
Keybukwell, last night15:51
Keybukmostly initramfs-tools15:51
james_wthe tsort stuff?15:52
ionHow about devtmpfs?15:52
Keybukno, that was in 1815:52
KeybukI replaced all of the scripts/local loop with a tiny binary15:52
Keybukthat uses libudev to do what all that shell was trying to do *properly*15:52
james_wcool15:52
Keybukie. if the device doesn't exist, use netlink to wait for udev to finish with it15:52
Keybukif the device exists, and is in udev's queue, also use netlink15:52
Keybukif the device exists, and is not in udev's queue, done15:53
Keybukalso obviously outputs the filesystem type as udev knows it, so we don't have to separately probe fstype/blkid in the initramfs15:53
Keybukone major advantage speed-wise is that it never calls "settle"15:54
Keybukwhich means you can mount the root fs in the initramfs while loading of irrelevant modules is still happening15:54
pittiupdate-initramfs: Generating /boot/initrd.img-2.6.32-8-generic15:54
pitti.: 4: Can't open /scripts/functions15:54
pittiKeybuk: ^ known?15:54
Keybukpitti: no, can you check through scripts/*/* and see which sources /scripts/functions *before* checking for "prereqs"15:55
pitti./local-top/cryptroot15:56
pittiso, from cryptsetup15:56
Keybukpitti: fix is obvious, don't source /scripts/functions until after the prereqs case15:56
Keybukcan you do that one while you're there?15:56
* Keybuk has an allergy to cryptsetup15:57
pittihm, I moved it down, now it says15:57
pitti[: 22: Private: unexpected operator15:57
* pitti sighs15:57
Keybukpitti: pastebin the script?15:57
pittiKeybuk: I'll try to squeeze it in (release meeting now)15:58
Keybukoh, cryptsetup has a *weird* prereqs!15:58
pittiKeybuk: http://people.canonical.com/~pitti/tmp/cryptroot15:58
Keybukyeah that for just won't work ;)15:58
Keybukprobably should be $(dirname $0) rather than /scripts/local-top15:59
=== binitamshah|away is now known as binitamshah
Keybukpitti: a change I made the other day is that the prereqs bit of each script is run at mkinitramfs time16:01
Keybukrather than inside the initramfs16:01
Keybukso the generated initramfs already knows what order to run things in16:02
pittiKeybuk: updated script (same URL), it doesn't complain now16:02
pittibut I don't claim I really understood what I was doing16:02
Keybukbasically was just expecting /scripts to exist16:03
Keybukwhen that's /usr/share/initramfs-tools/scripts16:03
Keybuk(because I'm running it from mkinitramfs now)16:04
pittiKeybuk: so, I'm fine to do that upload if you want me16:04
Keybukyup, go for it16:04
KeybukI imagine we'll hit a few of those16:04
pittiuploaded16:08
pittinice, bzr bd now DTRT even without a .bzr-builddeb/ config16:09
james_winferring --merge?16:09
pittiright16:09
pittithe cryptsetup tree is full source, but it downloaded the orig.tar.gz, etc.16:09
james_wyeah, that's (yet another) thing you can thanks jelmer for16:09
pittiso far we just copied the very same config into all of our desktop trees16:10
pittijelmer: *hug*16:10
jelmerpitti: :-) Glad to hear16:10
jelmerwe have similar itchjes16:10
Keybukjames_w: I still have issues getting the first tarball into bzr ;)16:38
KeybukI do sick and evil things like make a pretend upstream-last-release tag16:38
Keybukor remove debian/changelog and import-dsc the source package I just generated16:38
KeybukI noticed that it seems to upset the auto-importer though ;-(16:39
james_whmm16:40
james_wI thought merge-upstream was supposed to work, but I can believe that I broke it16:40
Keybukit won't work if there isn't a previous upstream tarball16:40
Keybukit will only make deltas I assume16:40
Keybuknever the initial tarball16:41
Keybukyou can trick it into doing so though16:41
james_wyeah16:41
james_wwe should fix that :-)16:41
KeybukI have been heavily using the bzr stuff though16:47
Keybukmy workflow this cycle is "bzr branch lp:..." ... doesn't exist? file bug; out of date? file bug (and apt-get source)16:47
Keybukotherwise just use the bzr16:47
pittittx: what I meant is that e. g. bug 497455  -> we won't promote until it actually appears on http://people.canonical.com/~ubuntu-archive/component-mismatches.txt16:52
ubottuLaunchpad bug 497455 in libwoodstox-java "MIR for libwoodstox-java" [High,Fix committed] https://launchpad.net/bugs/49745516:52
ttxpitti: right. It's a eucalyptus runtime dep, so I guess it will show up once the package in built16:53
jelmerpitti: btw, I noticed the MIR for tdb - some of the issues there should be fixed in the version of tdb in sid16:53
jelmerpitti: Are you the right person to talk to about the MIR, or somebody else?16:53
jelmerpitti: (I'm the Debian maintainer)16:53
pittijelmer: I'm one right person, yes16:53
keespitti: for the SIGXCPU+apport thing, I saw that you merged it, but I just wanted to make sure you felt that was a valid approach.16:54
pittijelmer: which "issues" do you mean?16:54
pittikees: it looks fine to me16:55
keespitti: ok, cool.  No other signals like those two jumped out.16:55
jelmerpitti: tdb-dev has been renamed to libtdb-dev, manpages will be included in the next upstream version16:56
ScottKslangasek: It'd be nice (although lower priority than powerpc) if you could look at qt4-x11 on ia64 too.  I'm lost in a twisty turny maze of ifdefs.17:21
* slangasek gibbers17:24
ScottKslangasek: The upstream feedback was: You have a config.h, remove it.  the issue is that #include "config.h" is including the wrong file17:25
ScottKSince it works on other archs.17:25
ScottKI think it's an ifdef issue17:26
Keybukmdz: are any of the videod sessions ever going to appear on blip.tv ?17:57
=== markus_ is now known as thekorn_
machinahi, I'm trying to update this copyright from this http://pastebin.com/d5200e964 to this http://pastebin.com/d1fafa456 but I don't know if it's right for me to put a copyright under the debian maintainer's name?18:09
machinathis is about updating an Ubuntu/debian package btw..18:10
ebroderI don't suppose I could ask somebody to do a sync run so the new version of the packge I was just about to work on would hit the repos? :)18:49
ScottKslangasek: I think I found my way through the twisty/turny maze for qt4-x11 ifdefs and ia64.  Found a "-   || defined(__ia64__) \" between the last version and the current one.18:55
slangasekah, cool18:55
slangasekebroder: what package?18:55
ebroderslangasek: open-vm-tools19:00
slangasekah, needs a sync run on contrib; looking19:00
slangasekebroder: syncing19:05
ebroderYay! Thanks, slangasek19:07
=== yofel_ is now known as yofel
Lutinthose days, who do I have to ask to get a give-back on the buildds ?19:09
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
ScottKslangasek: If I give you a debdiff for qt4-x11, could you testbuild it on a ia64 porter box?  It's a huge package for me just to blind upload.19:28
slangaseksure19:28
ScottKOK.  I'll have it in a few.19:28
ScottK.dff.gz for that package takes an eternity to generate on my laptop.19:29
ScottKdff/diff19:29
=== mehdid_ is now known as darkwise
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
ScottKRight, so the good news is the emergency drop protection shutdown on my laptop works.  The bad news is the diff.gz wasn't done yet.19:48
ScottKIt was kind of cool to see the laptop blink off in mid-air when I dropped it.19:48
slangasekheh19:54
ionWhy power down the entire laptop? Why not just park the HDD heads?19:57
Lutincould someone with a lucid chroot try to install libeina-svn-05 (no matter what arch.)20:00
slangasekLutin: could; but is the problem you're trying to solve related to the fact that this package needs a binary promotion to main?20:02
* ScottK guesses yes.20:03
ScottKion: I didn't design the hardware.20:03
ionNobody blamed you for the hardware design.20:04
ScottKIt just seemed odd to ask me why it worked the way it does.20:04
ionI asked the channel.20:04
ScottKok20:04
ionsincerely willing to learn the technical reason for shutting down everything.20:05
slangasekperhaps because the hardware doesn't trust the OS to park the heads and leave them parked20:07
ionThe hardware could force the heads to be parked for a period and the OS to wait.20:08
ScottKslangasek: http://pastebin.com/f3e99eaa320:11
ScottKslangasek: On the off chance that builds, please just throw it at the archive.20:11
slangasekhow do I extract a usable patch from pastebin?20:12
arthur_slangasek: see the textarea in the bottom20:14
slangasekI see it; cut-n-pasting from it didn't please patch, that's why I was asking20:14
arthur_right after "To highlight particular lines, prefix each line with @@"20:14
arthur_ah20:14
slangasekpatch: **** Only garbage was found in the patch input.20:14
slangasekoh, haha20:15
slangasekbecause it eats @@ at the beginning of a line20:15
arthur_nice spot20:15
slangasekok, got it20:15
ScottKOops20:16
ScottKWhen I click on download it comes up correct.20:17
slangasekoh, there's a download button, ok20:17
slangasek:)20:17
Lutinslangasek: that's it, thanks20:22
slangasekLutin: ok, should be fixed in the next pulse then20:22
Lutinalright, thanks a lot20:22
Lutinslangasek: in fact JamieBennett just pointed out that it's been promoted some times ago20:39
slangasekLutin: not so; the binary was in universe until around the time I commented20:39
JamieBennettJonathan Riddell wrote on 2009-08-24:#6 Package moved to main20:39
JamieBennettfrom the bug comments20:40
* ScottK suspects a library transition20:41
slangasekthat refers to a source package20:41
Lutinah, true. the source package introduces a new binary package which wouldn't have been promoted automatically ?20:44
JamieBennettslangasek: Is there an active archive admin around which could kick the binary into main for us then?20:49
slangasekJamieBennett: already did, see above20:51
JamieBennettOK, thanks20:52
slangasekLutin: it's a routine archive admin activity to reconcile http://people.canonical.com/~ubuntu-archive/component-mismatches.txt, so it /should/ be < 48h turnaround from accepting the package to making sure it's in main if it's supposed to be20:52
Lutinslangasek: ok, thanks for the explanation20:55
wgrantlamont: Are you planning to get the lp-buildd changes merged soonish?21:16
lamontbigjools was supposed to land them, I thought21:16
wgrantAh, OK.21:16
lamontlp:~lamont/launchpad/lp-buildd/21:16
lamontis what I actually built21:17
lamontand actually has changes beyond 5421:17
wgrantAh, I wondered what those extra three revs were for.21:17
lamontyeah, it was the lalalalalalala fix these too things that fell out of reviewing changes to the machines where I installed the package21:18
lamontsome just landed after I'd cut 54, and/or were invasive enough that I want them to get more testing before I roll them.21:18
HenriqueRochahi21:45
lamontslangasek: bug 49833121:46
ubottuLaunchpad bug 498331 in libgphoto2 "FTBFS: excessive something" [Undecided,New] https://launchpad.net/bugs/49833121:46
HenriqueRochai'm trying to install lucid alpha 1 but it doesn't install21:46
slangaseklamont: how precise :-)21:46
lamontslangasek: I decided to make sure it had a descriptive subject....21:46
=== HenriqueRocha is now known as hrocha
lamontdear fellow buildd admins:  DO NOT give-back libgphoto2/armel.21:47
hrochais it possible that it is not installing because i'm using the locale in portuguese?21:47
slangasekhrocha: #ubuntu+1 is the channel for lucid support; I'm not aware of any locale-specific issues in alpha-121:48
hrochaok, thanks21:48
=== asac_ is now known as asac
=== sabdfl1 is now known as sabdfl
=== jam1 is now known as jam
=== Tm_K is now known as Tm_Tr
=== Tm_T is now known as Tm_P
=== Tm_P is now known as Tm_T
=== asac_ is now known as asac
=== elky is now known as elky`
=== elky` is now known as elky
ebroderWait, what? Why can't I target bug #191776 for Hardy? The package has always been in multiverse - I should be able to23:31
ubottuLaunchpad bug 191776 in open-vm-tools "Shutdown guest using the VI Client with VMware ESX 3.0.2 doesn't work" [Low,Fix released] https://launchpad.net/bugs/19177623:31
wgrantebroder: It doesn't exist in Hardy.23:42
wgrantIt was removed just before release.23:42
ebroderHuh! How about that23:42
wgrant(and it was in universe then)23:42
ebroderOh yeah - the bug was reported against Hardy a423:43
ebroderIt seems like it would be useful if I could deal with nominations for releases the package wasn't in at all. Oh well23:45

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