[00:40] slangasek: what do you want with bugs that are a "please test if this is fixed in the next alpha"? [00:41] * Hobbsee milestones, assigns to her, etc [01:16] c === freeflyi1g is now known as freeflying === Pici` is now known as Pici === miguillo2 is now known as miguillo [03:00] if any archive admins are about, can you see why https://edge.launchpad.net/ubuntu/+source/mythtv/0.21.0~fixes16338-0ubuntu3/+build/530056 hasn't hit the archive yet? It built like 8 hours ago. [03:01] and its not in NEW [03:19] jcastro: ping. [03:52] Hobbsee: hmm, not sure what you mean; is the bug a serious one that needs milestoned in the first place, is the bug marked as 'fix released'...? [04:06] slangasek: it's a "i could reproduce this originally, and it's not good for the final release if it's reproducable - it needs testing during our testing for t6 [04:06] * Hobbsee can't seem to reproduce it now [04:07] ok; probably nominating/targetting it for hardy would be best I think [04:08] mhmm. with the rest of them, that people say "affects hardy. we hope it gets fixed sometime, but we have no fix in sight" ones [04:08] (that's why i don't use affecting hardy [04:08] ) [04:09] slangasek, would you mind checking why a build from about 8 hours didn't publish yet? [04:09] superm1: is probably soyuz bug :) [04:09] Hobbsee: well, I mean for the bugs that are targetted for hardy to actually be fixed for hardy in accordance with their severities :) [04:09] superm1: sure, what do you have? [04:10] https://edge.launchpad.net/ubuntu/+source/mythtv/0.21.0~fixes16338-0ubuntu3/+build/530056 [04:10] slangasek: that's not what the others tend to use it for, but yeah [04:10] Hobbsee, now lets not be pessimistic or anything... [04:10] oh damn, i didn't bring my laptop [04:10] * Hobbsee could have rsynced. [04:10] superm1: of course not. just aware of the way soyuz likes to work. [04:11] superm1: it's either in the new queue, or its' a bug, and soyuz has gotten hungry again. [04:11] its not in the new queue [04:11] nothing has changed with it that would have put it there, and i looked there a little bit ago to make sure [04:11] see and i dont even talk bad about soyuz, why would it want to eat my builds? [04:11] if anything it should eat yours :) [04:12] hah [04:13] * Hobbsee looks, blinks [04:14] superm1: erm. what makes you think it's not published? [04:14] superm1: https://edge.launchpad.net/ubuntu/hardy/+source/mythtv/0.21.0~fixes16338-0ubuntu3/ shows it as 'done', yeah [04:14] Hobbsee, it hasn't shown up on archive.ubuntu.com or packages.ubuntu.com [04:15] and drescher agrees that it's there... [04:15] http://archive.ubuntu.com/ubuntu/pool/multiverse/m/mythtv/ [04:15] * Hobbsee points at mythtv-backends [04:15] look at mythtv-common [04:15] http://archive.ubuntu.com/ubuntu/pool/multiverse/m/mythtv/mythtv-backend_0.21.0~fixes16338-0ubuntu3_amd64.deb [04:15] in archive.ubuntu.com [04:15] its missing [04:15] oh, hmm [04:16] so, some of the binaries are there [04:16] along with the rest of i386 [04:16] superm1: mythtv-common is arch: all? [04:16] yeah [04:16] i thought it might be [04:17] superm1: it' ssitting on launchpad i fyou awnt to grab it from there [04:17] but, uh, i suspect that's a soyuz bug :) [04:18] Hobbsee, its not a big deal for myself, but when the alternate disks go to build in 3 or 4 hours, they aren't going to like it [04:19] the CD builds pull directly from drescher, though [04:20] so if there's an issue preventing it from being visible for archive.ubuntu.com, that won't affect the CD builds anyway [04:20] superm1: i think you'll need to poke cprov over that, and he doesnt' appear to be around. [04:20] mythtv-common | 0.21.0~fixes16338-0ubuntu3 | hardy/multiverse | all [04:20] that's the one you're looking for? [04:20] yes [04:23] well if the cd builds right from drescher not a big deal [04:23] that's the only thing that really matters to get it in "tonight" [04:23] i'll wait for cprov tomorrow then for fixing it on a.u.c and p.u.c [04:24] yup [04:25] hmm. i need noise cancelling earphones, or to kick these giggling girls out of the lab. [04:26] Heh [04:26] and then people complain about not that many females in IT. Well, if they act like that, then no... [04:26] There's a shopping centre ~10 mins away. go there! [04:39] Aw [04:40] Aw? [04:40] StevenK: supposed to be /aw [05:27] _MIf you have the ubuntustudio splah installed, you may also have to remove that. [05:27] gah wrong channel [05:35] wasabi: glad you like the gui - were my bug fix updates from today enough to get things sorted? [05:39] superm1: yah, it doesn't build "right" from drescher, but the CD build servers all mirror directly from drescher [05:44] wasabi: thanks, I've noted the feature requests. Perhaps a hardy+1/+2 type thing [05:44] wasabi: if you're ever interested in doing some cairo/gtk hacking, I'd be happy to point you at the code (it's not terribly complex) and explain it === Fujitsu_ is now known as Fujitsu === Lutin_ is now known as Lutin [06:52] * Hobbsee smashes wget against a brick wall [07:12] Good morning [07:13] * slangasek waves [07:13] Heya pitti [07:26] ogra_: artwork> which package does this refer to, precisely? [07:27] ogra@ceron:~/devel/packages/gfxboot-theme-ubuntu-0.5.3$ dpkg -S /usr/share/backgrounds/simple-ubuntu.png [07:27] ubuntu-wallpapers: /usr/share/backgrounds/simple-ubuntu.png [07:27] wallpapers ... [07:28] but i suspect other artwork packages might have grown as well ... [07:28] slangasek: I would need to check, but all the sounds for the sound scheme are at 44100Hz, 16 bit Stereo. At the least, I could resample them to 22050, and for a sound scheme, that wouldn't impact on their quality much for general use anyway. [07:28] slangasek: So, ubuntu-sounds being 2.3 currently, could be taken down to about 1.5/1.6 probably... [07:29] ogra_: yes, could be. ubuntu-wallpapers hasn't changed since alpha-5, so it doesn't account for the size increase - but of course if we can slim it back down again, that would be welcome all the same [07:29] TheMuso, do we still use .wav files ? [07:29] ogra_: We do indeed, and thats all we can use, due to the audiofile library being used. [07:29] afaik [07:30] slangasek, well, 3.5M is quite heavy for a wallpaper imho [07:30] TheMuso, hrm ... we should really look into switching to ogg [07:30] ogra_: files of many common formats (currently AIFF, AIFF-C, WAVE, NeXT/Sun, BICS, and raw data). [07:30] to gain some compression [07:30] ogra_: Willing to massively edit either the audiofile library, or GNOME code proper? [07:31] TheMuso, lest talk about that after hardy is out :) i cant oredict my workload for interpid yet since so much changed in edubuntu land [07:31] ogra_: Something like that needs doing upstrea. [07:31] TheMuso: how do i test the scim thing? [07:31] ogra_: I'm just saying its a lot of work. [07:32] right, i'm aware :) [07:32] asac: I can't remember without looking it up./ [07:32] rather unfortunate that GNOME has this lovely gstreamer framework, but system sounds can only be .wav files :-P [07:32] asac, open the scim gui, select de nodeadkeys, re-login is what i did [07:32] slangasek: Indeed. [07:32] slangasek: But it is an option, and I can do it if 1.3 or so MB is that critical. [07:33] slangasek, there was a patch floating around that made the systeem sounds use gstreamer as well i think it was abandoned :( [07:34] TheMuso: let me see what happens after the latest round of liveCD builds, and after I try to fix python2.5+db4.6 so we can kick db4.2 back off, and I'll see where we are; making changes to the fundamentals of GNOME sound handling is not a useful fix for alpha-6, and I'd rather not have to short us on sound quality either [07:35] * cjwatson trims 50KB off the CD boot menu; every little helps [07:35] slangasek: Ok fair enough. [07:35] * TheMuso should really do a new scheme one day... [07:36] one place where I know we ought to be trimming for sure is the fact that we now have two distinct gtk2 engines being pulled in by human-theme on the Ubuntu CD [07:36] but I'm not sure which one needs to be gotten rid of yet [07:37] slangasek: Ken didn't reply last night, I take it? [07:37] slangasek: Wasn't clearlooks already on the CD? [07:37] it should be dropped if that is the case [07:38] we default to murrine now [07:38] cjwatson: nope, hoping he's a fairly early riser :) [07:38] Amaranth: this is gtk2-engines-murrine vs. gtk2-engines-ubuntulooks [07:38] slangasek: oh, in that case i thought ubuntulooks was being dropped [07:38] ogra__: so -ubuntulooks isn't used and can be dropped without ill effect? [07:38] that was the point of redoing the themes using clearlooks and murrine [07:39] Amaranth: makes sense, I just have no clue whether we're at the point where -ubuntulooks is ready to be dropped, do you? [07:39] -ubuntulooks is only 40KB though? [07:39] slangasek, well, my installs all use murrine by default here, not sure kwwii wants to ship a fallback with Human, that would require clearlooks indeed [07:39] pulls in a bunch of libraries, but I assume most of those are used by something else [07:39] slangasek: Well, I'd say no, the other two themes...need some work [07:39] cjwatson: ah, argh [07:40] cjwatson: alright, moving that to the "every little bit counts" pile [07:40] heh [07:40] cjwatson: yes, all the libs it pulls in are already there [07:41] Amaranth: umm... are they "not happening for hardy" need some work, or "needs to get done by hardy" need some work? [07:41] I suspect the latter [07:41] Probably just need someone to spend a day with them polishing [07:41] whichever side they fall on, we should cut the other end off as long as it still leaves us with a functional desktop :-) === doko_ is now known as doko [07:42] they work fine, they just need some tweaking (tooltips aren't themed properly, etc) [07:42] hmm, using pngcrush on the wallpaper actually gains zero ... thats really strange [07:43] ogra__: someone crushed it already? [07:43] Amaranth, but its stil 3.5M [07:44] well, pngcrush just removes metadata [07:44] it makes my classmate desktop unresponsive while it loads [07:44] it doesn't compress the image more or anything [07:44] oh, i thought it does [07:45] oh, i guess it does [07:45] 703M daily-live/20080305/hardy-desktop-amd64.iso [07:45] 705M daily-live/20080305/hardy-desktop-i386.iso [07:45] hnngh [07:45] i was thinking of another tool [07:45] slangasek: drop gthumb ;) [07:46] Amaranth: in favor of? [07:46] slangasek, amd64 alternate is fine ... lets just resort to that one :P [07:46] slangasek: well, we have fspot already [07:46] slangasek, we have f-spot in the default install [07:46] but this debate has gone on for like 3 releases now [07:47] slangasek, unfortunately it still used the wrong packages for this build. guess we'll have to wait until tomorrow for more luck :( [07:47] but people will complain if you drom gthumb [07:47] *drop [07:47] didn't we already drop gthumb? [07:47] can we not have the applications debate *again* [07:47] yes, we did; it even wants to go to universe, needs seeding [07:47] pitti: yes [07:47] oh, yay [07:47] but oh, still need rom [07:47] room* [07:48] * Amaranth uninstalls gthumb [07:48] superm1: mmm, odd [07:48] * pitti wonders what used up some 80 MB since alpha-4 [07:49] yeah, i thought alpha 4 was way under the limit [07:49] i can't think of anything that got added though [07:49] some 650 MB including some langpacks, yes [07:49] the manifest diff between alpha-5 and alpha-6 is short enough, but looking through for which packages have grown would take some doing [07:50] are those langpacks still on the disc? [07:50] slangasek: for the alternates we could flip some large packages to lzma [07:50] and none of the alpha-4 metadata is still around, sigh [07:50] maybe just drop them again for now? [07:50] Amaranth: we did [07:50] oh, i missed that bit [07:50] Amaranth: that's where the other ~ 30 MB from my estimation (80 MB) come from [07:50] stupid splits :P [07:51] pitti: alternates don't concern me nearly as much; as soon as OOo-l10n lands, I understand we'll already have more space there [07:51] ah, right, lzma FTW [07:51] is there a howto anywhere for switching packages to lzma ? [07:52] * ogra__ would like to see how gcompris would behave with that [07:52] it ought to be possible to take the manifest diff and feed it to something that downloads all the old packages from the librarian and compares sizes [07:52] might want to do that inside the DC, of course [07:52] ogra__: dh_builddeb -- -Zlzma; but calc already did the archive analysis on which packages benefit most, I think [07:53] slangasek, ah, thanks [07:53] ogra__: dh_builddeb -- -Zlzma, pre-depends: dpkg (>= 1.14.12ubuntu3) [07:53] well, gcompris is 60M source :) [07:53] it should gain *something* [07:54] ogra__: there's a space/performance trade-off with lzma; the focus is (and IMHO should be) on deploying it first in the packages with the largest footprint [07:54] hrm [07:54] gcompris is my largest package in edu land ... [07:55] bloody hell, I was looking at the ship seed before, not the live CD; live still has a number of langpacks that can be unseeded if necessary :/ [07:55] the binaries take about 80M or so ... i dont have space constraints on the addon CD atm though [07:55] slangasek: it may be that calc only looked at the Ubuntu CDs [07:56] cjwatson: oh, possible, yes [07:58] Spads, Ng: ping? [07:58] oh wrong channel === ogra__ is now known as ogra [08:22] where's openoffice.org-common for 2.4.0rc2? [08:24] slangasek: mind if I upload oo.org-voikko for a rebuild? [08:25] tjaalton: go ahead, please [08:25] slangasek: thanks [08:25] openoffice.org-common> what do you mean? I see it in the archive where it should be? [08:25] slangasek: ok, maybe archive problems again? it's not on a.u.c [08:26] yes, superm1 was mentioning mythtv wasn't making it to a.u.c either [08:26] OO.o not installable on amd64 for me either [08:27] morning [08:32] slangasek: hmm, there's also voikko 2.2-1 in unstable, which seems to add some additional support for OO.o 2.4. maybe sync that? [08:32] not too many changes [08:32] are you asking me to sync it, or are you asking my opinion on whether a sync is appropriate?: ) [08:32] well, both :) [08:34] slangasek: I'll try a pbuilder run first === seb128_ is now known as seb128 [08:36] "Sorry, Gestor de actualizaciones closed unexpectedly" [08:36] * slangasek twitch [08:36] slangasek: BTW, while live filesystems do build straight from drescher, the archive mirror on antimony comes from syncproxy [08:36] slangasek: and it looks like that's out of date [08:37] "Cannot install 'openoffice.org-dev'E: pbuilder-satisfydepends failed." [08:37] so much for trying pbuilder [08:37] I was expecting partman-ext3 49ubuntu2 to be there, which is timestamped 22:05 last night on drescher, but it isn't [08:38] slangasek: have you poked IS about it yet? [08:38] cjwatson: ah, I hadn't poked, no [08:38] pitti, slangasek: any opinion if we should switch evolution-data-server to use gnome-keyring in hardy? Currently passwords are stored in the user directory, keyring would be better but there is no migration which means users would have to re-enter their password on upgrade === harrison1 is now known as harrisony === hunger_t is now known as hunger [08:52] Riddell: around ? [08:53] seb128: I'm all for consolidating to gnome-keyring [08:54] seb128: it's much easier to do backups, put keys on USB stick, etc. [08:54] pitti: do you think having to re-enter the passwords is an issue we need to fix though? [08:54] seb128: hm, wrt. bug 196962, do you remember the decision about rb vs. sj for audio CDs? [08:54] Launchpad bug 196962 in gnome-volume-manager "Audio CD launches both Rhythmbox and Sound Juicer" [Undecided,New] https://launchpad.net/bugs/196962 [08:54] pitti: launch rhythmbox [08:54] seb128: if we could fix that, the evo keyring would be badly protected :) [08:55] seb128: but it's just entering your password once for the hardy upgrade, right? that seems bearable to me [08:55] seb128: rb> ok, fixing in gvm then [08:55] pitti: well, evolution passwords are not protected right now, evolution could read those and store them in the keyring if they are not there [08:55] pitti: yes [08:55] oh, one more reason to do that switch [08:56] seb128: so, IMHO it's worth an upstream bug report to do that transition, but if it won't happen, I don't think that it bites too much [08:56] pitti: I though we stopped using gvm for mounting? [08:56] seb128: I'd like to see the evo keyring cleaned on upgrade, though [08:56] pitti: I talked to upstream about it, they will likely do something but maybe not before hardy [08:56] pitti: right [08:56] seb128: gvm> it still handles scanners, printers, and the like [08:57] and cameras [08:57] pitti: right, but audio CD should be nautilus [08:57] I agree [08:57] just wanted to confirm with you [08:57] * pitti hugs seb128 [08:57] * seb128 hugs pitti === asac_ is now known as asac [08:57] seb128: btw, we already have the first complaints about that :) [08:57] seb128: I'm never happy when users (particularly those named Steve) have to reenter information after upgrades. Is gnome-keyring already supported by e-d-s upstream as an option, and is there any prospect of migration support in the future? [08:57] pitti: I'm not sure what you are fixing in gvm for rb then? [08:58] pitti: about what? [08:58] seb128: complaint> bug 198505 [08:58] Launchpad bug 198505 in gnome-volume-manager "gnome-volume-manager does not mount devices any more in hardy" [Undecided,Won't fix] https://launchpad.net/bugs/198505 [08:58] seb128: apparently gvm still launches sj [08:58] so I'll make it not do that [08:59] alright [08:59] thanks === soren_ is now known as soren [08:59] slangasek: what I wrote to pitti before, keyring is supported and other distros use it now, there is no migration code but upstream agree that would be nice to do, somebody needs to write this code though [09:00] mm right [09:02] well, I take the view that if it wasn't hurting users before now to have the passwords outside of gnome-keyring, leaving them there until a migration path is available is not a big deal and I'd rather have the user experience right [09:03] I tend to agree with that [09:03] what's the likelihood the upstream bits would be ready in time for the hardy point release? [09:03] I would like to use the keyring though, I'll try to get somebody upstream helping getting that migration code before hardy beta [09:17] are daily cd images mirrored? cdimage.ubuntu.com is slow today [09:17] there are no mirrors of dailies, no [09:17] ok, thanks [09:17] slangasek: and for milestones? [09:18] alphas, also no [09:18] ok [09:21] I have a really impressive metacity bug here; the window switcher (i.e. the pop-up when you use C-A- to move between workspaces) has got stuck on, and won't (a) go away or (b) let me move out of the first row of workspaces [09:21] I'm going to have to kill my X session once various stuff has finished running, but is there anything I can do in the meantime to diagnose this? [09:22] it started while some pretty heavy disk I/O was going on [09:22] are other window manager things, moving, switching between tasks, etc still working? [09:23] cjwatson: why do you need to restart the session? restarting the wm should be enough no? [09:23] I can move between workspaces, but not Alt-Tab, and the window switcher has keyboard focus so I can't do anything useful [09:24] restarting the window manager would probably be enough, true [09:24] no idea on what debug information would be useful [09:24] it doesn't seem to be stucked so a backtrace would likely be of no use [09:25] the most useful information would be a way to trigger the bug [09:25] I would say you can just restart it [09:26] yeah, I've never seen it before - if I see it again I'll try to find common features [09:26] cjwatson, i had some similar things with my alt key the last days ... not actually metacity i guess but similar [09:26] moring seb128 [09:26] like if i click on a window i can only move it (like with a stuck altkey) [09:27] hi huats [09:27] ogra_cmpc: there is a linux or xorg bug about key events being continuously generated sometimes [09:27] ogra_cmpc: I don't think it's that; setxkbmap normally clears that kind of thing for me and doesn't help in this case [09:28] it didnt for me [09:28] and given that it happened on the classmate it verz likely happened under heavy disk IO [09:28] *very [09:28] stracing metacity from a console says it's very busy, constantly reading/writing [09:28] it could well be a stuck key event [09:29] thats what i mean [09:29] cjwatson: xev? [09:29] i had that happening before always related to the alt key [09:29] seb128: how do I get metacity's windowid from a console? [09:30] ah, xwininfo [09:30] I was going to suggest xprop but that should do it too [09:30] hm, xev isn't saying anything [09:31] cjwatson: there are some bugs reported against xorg about keys getting stuck [09:31] mostly page down and such but i suppose alt could get stuck too [09:32] bug 194214 [09:32] Launchpad bug 194214 in xorg-server "Keys get "stuck" down" [Medium,Confirmed] https://launchpad.net/bugs/194214 [09:32] I often get Tab, and something that doesn't seem to be real, stuck. [09:32] i've had that in feisty and gutsy happening as well at least once every release cycle [09:32] Amaranth: There's another very similar to that. [09:32] and it always seemed related to IO [09:33] ogra_cmpc: i believe the original reporter was scrolling in firefox when it happened, dunno if that'd hit the disk or not [09:33] certainly spikes your CPU [09:33] indeed [09:33] That fits with my tab key getting stuck, it was during 100% load. [09:33] i only have it happening on special key combos (alt+tab etc) and if there is actually lots of disk IO [09:34] (CPU load) [09:34] havent seen it in normal browser operation or so [09:35] ogra_cmpc: I'm not sure that it's related to CPU load; it also seems to correlate with mouse activity. [09:35] might be [09:35] it usually went away with the next kernel upgrade for me ... [09:35] RAOF: Not for me. [09:35] disk I/O> I was doing 'dd if=/dev/zero of=alt.img bs=1024 count=$((3*1024*1024))' and simultaneously rsyncing a CD image [09:35] probably not massive CPU load involved [09:36] the prob its that it occurs so randomly that you cant even reliably reproduce it [09:37] ogra_cmpc: *I* can. It's nice and easy to reproduce. [09:37] ah [09:37] Hold down a key, scroll madly in firefox. [09:37] Tada! Key is stuck down. [09:37] ive been having problems where enter gets stuck for a moment [09:37] pwnguin: yes, also that [09:37] esp if i run something like apt-get upgrade [09:37] Also works in WoW, but you don't need to scroll madly. [09:38] iwj conjectured that it might have something to do with the fact that my CPU is hyperthreaded [09:38] or at least might be easier to reproduce given that [09:38] mine's dual core [09:38] all mine are [09:38] well, mine isnt, neither here on the classmate nor on the laptop where i saw the issue in other releases [09:39] *Definitely* not firefox related. Hold down 'a', scroll madly in gedit. 'a' is no stuck down. [09:39] s/no/now/ [09:39] Also probably not CPU load related, my laptop's not doing _too_ much. One core is ~50%, the other is idle. [09:40] whats the load average at ? [09:41] hi is there a social contract for ubuntu like debians ? [09:41] bug 124406 has a massive pile of key repeat reports [09:41] dbmoodb, search for "code of conduct" [09:41] Launchpad bug 124406 in ubuntu "Keyboard keys get stuck and repeat (Feisty, Gutsy) (dup-of: 194214)" [Undecided,Confirmed] https://launchpad.net/bugs/124406 [09:41] Launchpad bug 194214 in xorg-server "Keys get "stuck" down" [Medium,Confirmed] https://launchpad.net/bugs/194214 [09:41] but that is not a contract is it ? [09:41] dbmoodb: there's a code of conduct, and a set of core beliefs, but not i dont think theres anything quite like debian's dfsg [09:41] 1.63. Hm, tracker must be indexing. [09:41] ubuntu members have to sign it [09:41] ogra_cmpc: it's not the same thing [09:42] right, but similar [09:42] --- not dfsg -- social contract - 'debian will remain free' kind of thing [09:42] there's the Ubuntu Promise [09:42] is there a contract [09:42] a legally binding document [09:42] dfsg is part of the social contract of debian [09:42] it defines what Free means [09:42] the Debian Social Contract is NOT legally binding [09:42] heh [09:42] it is [09:42] there is no consideration involved and therefore it cannot be [09:43] its more like a constitution [09:43] in order for a contract to be binding it must involve consideration in both directions [09:43] dbmoodb: no, it is not [09:43] dbmoodb: there isn't a single document that's like the Debian Social Contract, but there are a number of things that address different bits of it; the licensing policy, the code of conduct, the Ubuntu Promise [09:43] it does [09:44] dbmoodb: slangasek and I are both Debian developers [09:44] ok so is ubuntu promised to remain "free" [09:44] dbmoodb: yes, it's right there on www.ubuntu.com [09:44] -where [09:44] front page [09:44] if you're looking for guiding philosophies [09:44] http://www.ubuntu.com/community/ubuntustory/philosophy === \sh_away is now known as \sh [09:44] the promise ? [09:44] "Ubuntu will always remain free of charge" and "Ubuntu CDs contain only free software applications" [09:45] and, as pwnguin says, the philosophy link for more detail [09:45] heh, googling ubuntu promise brings up an intresting pile of scsi howtos :) [09:45] ok ... so how is it different to the dfsg ? [09:45] we are not going to compromise Ubuntu's freedom as stated on the philosophy and licensing pages [09:46] sure [09:46] the differences between Ubuntu's licensing policy and the DFSG are quite small; in essence they amount to more liberal treatment of non-code works [09:47] well number one, developers can't vote to change the policy as far as i can tell [09:47] see "Documentation, Firmware, and Drivers" on the licensing page [09:47] ok... [09:47] other than that, the Ubuntu licensing policy is largely just a rephrasing of the DFSG [09:48] and that should be pretty obvious from reading them side-by-side [09:49] - yes i got that that is why i was wondering [09:49] if there was a social contract ") [09:50] its probably better off without one [09:51] lest an argument break out whether "a comma is a typo widely held belief" [09:59] <\sh> guys I'm really lost...and at the end of my knowledge somehow [10:02] <\sh> Building wine in pbuilder and on a clean chroot (which is used for sbuild, too) wine works like a charm... [10:02] carlos, pitti: any language pack update planned then? [10:03] carlos, pitti: would be nice to have a reflect of the GNOME current translations on current dailies [10:03] can do, but it'll block the buildds quite a bit [10:03] slangasek: ^ ok? [10:03] <\sh> building wine as package, the binaries in the package are borked...and I don't see anything in my buildlogs what triggers it...(this is the cause why wine is not running in the moment...building it on our buildds or in any plain sbuild chroot bring us broken binaries) [10:03] pitti: are the packages going to get bigger? :/ [10:03] slangasek: smaller, since it's a -base refreshment [10:03] carlos: btw did you get the list of packages not building a template? [10:04] ok, go ahead please [10:05] seb128: still working on that.. [10:05] oh, argh [10:05] no, nevermind; unargh [10:06] carlos: any estimation on how long it'll take? I would like to start fixing those issues, just to know if I should wait or try building a list by some other way [10:06] * seb128 hugs pitti [10:07] carlos: btw, we got new KDE l10n packages yesterday, so I guess next week we should do another -base refreshment? [10:09] holy crap, I didn't expect to get that partman-auto change right first time [10:12] cjwatson: Which one is that? [10:13] the first part of fixing bug 134950 [10:13] Launchpad bug 134950 in partman-auto "auto-resize primary partition constraints are too strong" [High,Triaged] https://launchpad.net/bugs/134950 [10:18] pitti: those are kde 4, they're not in rosetta === warp10 is now known as warp69 [10:22] Riddell: ok, not necessary then [10:22] doko: Around? [10:23] lool: yes [10:23] doko: Someone uploaded a new python-twill a while ago which depends on python-mechanize (>= 0.1.7b-2) [10:23] and that one doesn't exist, correct? [10:23] doko: Do you think it would be possible to solve this by updating python-mechanize? [10:23] doko: It does, but is too old [10:23] I mailed the uploader some 10 days ago to no luck [10:24] Michele Angrisano [10:24] I would have to look, maybe email jinti (Brian Sutherland) if that version is ok for other packages (schooltool, zope)? [10:24] slangasek: (Is it ok to push this to solve an uninstallability issue?) [10:25]