/srv/irclogs.ubuntu.com/2010/11/09/#ubuntu-devel.txt

=== bjf is now known as bjf[afk]
=== sanchaz-away is now known as sanchaz
twbSo this "weyland" thing that Mark was waffling on about... does it mean ssh -X won't Just Work in upcoming releases of Ubuntu?01:26
twb(Or: is there a more appropriate channel to ask that?)01:26
kklimondatwb: it's simply way to early to ask that01:37
twbokey dokey01:37
kklimondaalso, X are not the only way of running applications remotely.01:38
twbI realize that, but I'd prefer not to replace ssh -X with some raster-based nightmare like RFB or RDP01:39
kklimondabut it's still too early to ponder about it.01:39
twbNod.01:39
Chipacais there an easy and magic way to split a library package into libfoo and libfoodev?01:42
lifeless.install files01:42
Chipacalifeless: thanks01:45
* Chipaca reads01:45
electrofreakI've realized a problem with the powernowd and Phenom II's dynamic clocking. For example... if I download mprime and run 4 stresses from the program, my CPU usage will go to 100%, but the clocks of all the cores is 800MHz except for 1, which is at 3.2GHz. This was also a problem when doing multithreaded converting with ffmpeg. But if I use 'stress' with 4+ cpu stresses, it will clock up all the cores properly. So, there seems to01:55
electrofreakbe a problem with the threading and powernowd clocking each of the cores independently. Any ideas on a proper fix? (killing powernowd is a workaround)01:55
psusielectrofreak, uninstall the powernowd package... it's obsolete and I have requested that it be removed from the archive... the functionality it provides is now provided by the kernel itself01:58
twbDoesn't it just set the CPU scaling governor to performance on AC and conservative on battery?01:59
psusiI think that's laptop mode tools...01:59
psusithough it is interesting that your cores report different clocks... usually all the cores in a multi core cpu must be using the same clock02:00
twbLast time I looked, all those throttling apps basically just modprobed the driver and then set the governor on ACPI events02:01
twbi.e. they were all pretty much useless02:01
electrofreakpsusi, well... I don't think that the kernel's version works right either02:04
electrofreakpsusi, I could be wrong maybe02:05
electrofreakpsusi, well, in older CPUs... they clocks were different per core...02:05
electrofreakbut this is a brand new Phenom II... each core clocks differently02:06
psusielectrofreak, given that it works correctly with one program and not the other, I'd guess that the one is either not actually running multiple threads and keeping all cores busy, or they are running at low priority so are ignored by the governor.. but first thing I suggest is that you remove the powernowd package...02:06
electrofreakpsusi, err... I messed up that sentence... in older CPUs, they clocks on each core were the same. But on new CPUs... each core can clock independently02:06
electrofreakpsusi, well... that program is definitely doing multiple threads... because in top it reports nearly 400% CPU (4 cores) and when I stop powernowd... the temperature jumps up very quick.02:08
electrofreakpsusi, 'stress' actually spawns separate processes.02:08
electrofreakpsusi, I'll try removing powernowd02:08
electrofreakpsusi, although, I might need to reboot now... because it just stopped it and the kernel itself isn't handling it on its own right now (probably because powernowd took over before02:09
electrofreakpsusi, or is there something that I can set in /sys to make the kernel take over again?02:10
=== sanchaz is now known as sanchaz-away
electrofreakpsusi, ok. I echo'd "ondemand" into /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor, that seems to work02:17
electrofreakbut now, mprime for some reason doesn't cause any of the cores to clock higher now.02:17
psusielectrofreak, it's probably nicing itself and iirc, ondemand by default ignores processes using the maximum niceness02:19
electrofreaknice value is 1002:20
electrofreakshould I try 0 nice?02:20
=== dendro-afk is now known as dendrobates
=== manusheel_afk is now known as manusheel
electrofreakpsusi, ok. I figured this out. have to set ignore_nice_load=0... then everything works fine.02:34
electrofreakpsusi, adding it to sysfs.conf to persist through reboots, too.02:34
=== dendrobates is now known as dendro-afk
=== robert_ancell is now known as robert_ancell-af
pittiGood morning06:50
pittislangasek: nice, thanks06:51
=== almaisan-away is now known as al-maisan
dholbachgood morning!07:35
=== lan3y is now known as Laney
=== robert_ancell-af is now known as robert_ancell
neerajHi, while uploading my package in ppa, I am getting this error msg again and again or two/six packages which I am packaging. Rejected:09:24
neerajUnable to find sugar-presence-service-0.90_0.90.1.orig.tar.bz2 in upload or distribution.09:24
neerajFiles specified in DSC are broken or missing, skipping package unpack verification.09:24
neerajanyhelp? I tried google but not able to find a soln09:26
akheronneeraj: try building with the -sa option09:36
neerajakheron: thanks. I forgot to use "-sa" and kept trying with -s flag :(09:38
=== hunger_ is now known as hunger
=== dendro-afk is now known as dendrobates
=== Claudinux_ is now known as Claudinux
=== freeflying_ is now known as freeflying
=== MacSlow is now known as MacSlow|lunch
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
pittisconklin: I assigned bug 672964 to you, it's a regression in the lucid proposed kernel12:48
ubottuLaunchpad bug 672964 in linux (Ubuntu Lucid) "2.6.32-26 unbootable: does not find root file system" [Critical,New] https://launchpad.net/bugs/67296412:48
pittisconklin: diwic reported it, I guess he can supply additional debug info if needed12:48
=== jorge is now known as jcastro
=== tmzt is now known as tmzt_dg2root
=== sebner_ is now known as sebner
=== oubiwann is now known as oubiwann-away
=== MacSlow|lunch is now known as MacSlow
=== dendrobates is now known as dendro-afk
Riddelldoko: what should we do about -mimplicit-it=thumb ?13:53
Riddelldoko: so far we added it to qt and kde4libs to work around failing to build13:54
Riddelldoko: should we add it to other packages as needed or should it go back in the gcc defaults?13:54
Riddellcurrently the kde stack is stuck on http://launchpadlibrarian.net/58639702/buildlog_ubuntu-natty-armel.kdepimlibs_4:4.5.3-0ubuntu1_FAILEDTOBUILD.txt.gz13:54
mdeslaurcjwatson, ev: bug 67302814:10
ubottuLaunchpad bug 673028 in ubiquity (Ubuntu) "Ubiquity encrypted home doesn't setup encrypted swap" [Undecided,New] https://launchpad.net/bugs/67302814:10
=== jdstrand_ is now known as jdstrand
Riddell\sh: could you verify bug 533369 ?14:35
ubottuLaunchpad bug 533369 in debootstrap (Ubuntu Lucid) "Fails to debootstrap squeeze chroot due to missing apt-get" [Undecided,Fix committed] https://launchpad.net/bugs/53336914:35
=== oubiwann-away is now known as oubiwann
Riddelloubiwann: hi, what was the outcome of the touch sessions with the Qt people?14:45
\shRiddell: I trashedbin my squeeze stuff, but can redo do it tomorrow...not right now...14:52
oubiwannRiddell: they liked the architecture, have used v1 of the GEIS API (complete with a Qt demo), and are even more excited about GEIS v214:54
oubiwannthey provided a great deal of feedback on all aspects of utouch, and really improved the quality of the UDS sessions as a result14:55
Ng914:55
Ngdoh14:55
ogra_ac1014:55
ScottK1114:55
=== bjf[afk] is now known as bjf
Riddelloubiwann: so presumably we can look forward to touch on linux being in Qt 4.8?14:59
oubiwannRiddell: well, it's more complicated than that... full MT support on Linux with Qt depends on XInput 2.1 landing14:59
oubiwannwe're hoping that 2.1 makes it into the X 1.11 release15:00
oubiwann1.10 is probably going to come out around Apr 2011, and that will still be too soon for XI2.1 to be fully tested15:01
oubiwann1.11 is likely to come out around August of 2011, so that's the target for XI2.1 getting released15:01
oubiwanntoolkits aren't interested in supporting touch officially for linux until 2.1 lands15:02
oubiwannbut the Qt guys are really staying closely involved with the 2.1 dev process and plans, and I would expect that they'll be ready to go as soon as X is15:03
oubiwann(in other words, I wouldn't expect a 6 month lag from them after August 2011)15:03
Riddelloubiwann: right, thanks for the update15:07
oubiwannRiddell: no prob15:07
bilalakhtarWhere can I find a listing of people with upload rights to 'which packageset' and other details15:11
geserbilalakhtar: the data is in LP and to some part also distributed in the heads of some people15:12
bilalakhtargeser: I mean, what is the URI to the LP page?15:13
bilalakhtarsince I know there is one15:13
geserI don't know a single page15:13
bilalakhtargeser: okay15:13
bilalakhtarfine then15:13
geserespecially that I don't know of any page in LP that shows upload permissions at all15:13
geseryou have to use the LP API to get the data15:14
bilalakhtarok15:14
geserPPU and similiar (e.g. package sets) are only managed through the LP API15:14
geserare you looking for something special? perhaps I can tell you the right spots to look at15:17
cjwatsonbilalakhtar: might be easiest to use edit_acl.py from lp:ubuntu-archive-tools - it has a query feature15:28
bilalakhtarcjwatson: thanks15:29
SpamapSSo.. I'm wondering why there was no discussion of btrfs at uds-n .. don't we want it as a default FS for 12.04? is that being relaxed now?15:30
* SpamapS has started using btrfs for all cache/temporary data.15:30
cjwatsonmostly forgetfulness, but I thought there were still serious issues with reliability and things like being able to use a halfway reasonable percentage of the block device15:31
SpamapSsince UDS-M I've been using it for my local mirror and now I'm working on getting schroot's setup on it15:33
SpamapShave had no issues, but have never gotten near capacity on a drive. does it just fragment badly?15:34
pittiI have used it as / (not /home yet) for about half a year without data loss15:34
=== dholbach_ is now known as dholbach
pittihowever, resuming from RAM often hangs, and I heard that this was particular to using btrfs15:34
jdongI've used it as / and /home and /srv for a year...15:36
jdongno data loss but two reformats due to metadata occupying tens of gigabytes of space15:36
cjwatsonSpamapS: I don't know the details.  comments I've heard are that you're lucky if you get it to use even half the disk space.  I think that's unacceptable for Ubuntu15:36
jdongand performance, I've found, rapidly degrades with time15:36
jdongcjwatson: it's lately more like 80%, but still not great.15:36
cjwatson(I haven't looked in a while though, and I recognise that we're not contributing much to the kernel side)15:37
jdongit's much more irritating when it mysteriously goes slow though...15:37
jdongparticularly with qemu/kvm type workloads (random IO on gigantic files), btrfs can generate a lot of disk traffic15:38
jdongit's still missing important features like a consistency check / repair mechanism too15:39
* cjwatson grumbles at having to do http://paste.ubuntu.com/528747/ to busybox15:41
SpamapSjdong: wow.. ok .. so not in 12.04 ;)15:42
jdongSpamapS: well I don't know. I'm not great at predicting the future, and Ubuntu doesn't have a stake in doing this kernel development right now15:43
jdongso it's just speculation on our end15:43
jdongthis looks like a case of proverbial "it's ready when it's ready"15:43
\shcjwatson: why?15:44
SpamapSjdong: IMO, if its not ready by 11.04, its not ready for 12.04 given the long term ramifications of a default filesystem choice on an LTS15:44
cjwatson\sh: see build logs.  irritating header incompatibilities15:44
jdongSpamapS: well the filesystem is certainly not something to risk mass-exposure to. But who knows, maybe by 12.04 ext4 will be deprecated in favor of btrfs :)15:45
jdongSpamapS: never know what'll happen in a year+ of Linux dev15:45
jdongSpamapS: but I think the bottom line is, we'll decide around UDS time for 12.04 with the information then. Right now it's hard to speculate one way or the other15:48
jdongbut users are already welcome to do btrfs installs and play with the technology15:48
SpamapSjdong: if there is one thing to be conservative about.. default filesystem on an LTS is probably it. ;)15:48
jdongyep :)15:48
\shcjwatson: hmm...wasn't there some discussion about not using <linux/*> includes when avoidable?15:48
SpamapSjdong: if its not already default for 11.10 .. it would be hard to convince *me* that its ready enough for 12.04. :-P15:49
jdongSpamapS: your opinion might be different if all the other popular OS'es by 12.04 have features afforded by btrfs-type filesystems.15:50
SpamapSSeems to me like there's another thing going on, which is changing the way people think about files in general. There's the traditional static folder/tree view, and then there's something else.. I like the idea of a file manager that is entirely time-oriented.15:50
SpamapSjdong: If they have something btrfs-type that is tested and agreed upon, then lets use that. ;)15:51
jdongSpamapS: indeed if OS X, Windows, RedHat, and friends ALL had time machine type snapshotting features, live checksumming / recovery, etc... we might get impatient15:51
ebroderi'm kind of skeptical that's a compelling enough use case to be worth getting impatient over15:51
SpamapSebroder: people don't think twice about saving a file if they know it is version controlled. "forever undo" is quite freeing. :)15:52
=== apw` is now known as apw
jdongebroder: deep integration with the rest of the desktop of COW snapshotting would make me very impatient ;-)15:53
cjwatson\sh: yes.  hence "grumbles"15:53
dokoRiddell: are thre bug reports open about this?15:58
Riddelldoko: no, just build logs16:06
dokoRiddell: I'll have a look tomorrow with the linaro people16:17
dokoRiddell: so this is kdepimlibs, qt and kde4libs ?  a bug report would be nice16:19
TeTeTtkamppeter: hi, I'm encountering a black/white vs color printing problem in eog, I filed a bug against eog, but not sure if it's not actually cups: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/67308216:24
ubottuLaunchpad bug 673082 in eog (Ubuntu) "10.04: Print in black/white instead of color" [Undecided,New]16:24
=== beuno is now known as beuno-lunch
m4they, i've got a .config that fails to boot when compiled with 10.10 32bit toolchain16:39
m4ti verified this on another maverick install also16:39
m4tCONFIG_MPENTIUMM and CONFIG_M686 both have the issue16:40
=== al-maisan is now known as almaisan-away
m4tshould i file this under linaro-gcc?16:41
=== yofel_ is now known as yofel
=== beuno-lunch is now known as beuno
pitticjwatson: any idea how this could have happened? https://launchpad.net/ubuntu/jaunty/+source/xserver-xorg-video-geode/2.11.10-1~jaunty117:35
pitticjwatson: Q-FUNK just accidentally uploaded it (was meant for PPA)17:35
pitticjwatson: shall I reject the binary?17:36
psusijdong: I've been playing with lvm snapshots to test ugprading to natty and then reversing it... very nifty17:36
pittiit should just have been rejected (upload to stable), and on top of that jaunty is EOL17:36
RoAkSoAxkirkland: ping?17:36
pittiwgrant: ^ any idea about this jaunty upload?17:36
cjwatsonpitti: madison-lite on cocoplum doesn't list it17:37
pitticjwatson: it was just uploaded a few mins ago17:37
cjwatsonabsolutely should have been uploaded, do what you can to reject it17:38
cjwatsoner, shouldn't17:38
pitticjwatson: I rejected the binary, but of course the source is there now17:39
RoAkSoAxpitti: howdy! I have a question for you! I'm gonna ship the scripts (to reduce power consumption) with powernap. So I was wondering if it would be better to install the scripts in usr/lib/powernap/actions and then symlink to  etc/pm/power.d, or should I install them directly to etc/pm/power.d ?17:40
pittiRoAkSoAx: install directly, please; that's much less confusing17:40
jdongpsusi: yeah and btrfs's potential to extend that to the per-file/per-directory level, once integrated with applications, will be incredible too17:41
RoAkSoAxpitti: indeed. though I'm also writing a tool to enable/disable scripts easily and also list scripts with their description. So i gues that the tool will just remove the executable bit17:41
pittiRoAkSoAx: or rename them to .disabled or so17:42
pittiRoAkSoAx: but chmod -x sounds okay, too17:42
SpamapShttps://launchpad.net/~clint-fewbar/+archive/fixes/+build/2037553/+files/buildlog_ubuntu-lucid-amd64.mongodb_1%3A1.2.2-1ubuntu1.1~ppa1_FAILEDTOBUILD.txt.gz17:42
SpamapScan anybody explain why this symlink produces this error:17:42
TerminXanyone know why rsyslog hasn't been synced from debian in quite a long time?17:42
SpamapSdpkg-deb: building package `mongodb' in `../mongodb_1.2.2-1ubuntu1.1~ppa1_amd64.deb'.17:43
SpamapStar: ./usr/bin/mongo: file changed as we read it17:43
SpamapS/usr/bin/mongo is a symlink17:43
RoAkSoAxpitti: alright, will evaluate which one is more convenient. Thanks for the Input :)17:43
SpamapSto ../lib/mongodb/xulwrapper17:43
cjwatsonTerminX: needs merge, somebody needs to look at it by hand17:45
cjwatson(like all merges)17:45
RoAkSoAxSpamapS: you doing the symlink manually?17:45
SpamapSno, with dh_link17:45
SpamapSit works fine when building locally w/ sbuild17:46
TerminXcjwatson: ah, I guess there's no specific maintainer for the package then?  I was under the impression that ubuntu had switched to rsyslog by default17:46
TerminXI don't think anybody looked at it during the maverick dev cycle either17:47
SpamapSsome things just get lost in the scuffle. ;)17:48
cjwatsonTerminX: merges are assigned to the person who touched the package last by default; but not everyone gets around to all their merges17:48
cjwatsonthe standard rubric is that if you want to do it, you contact the person who touched it last to avoid duplicating work17:48
RoAkSoAxSpamapS: idk then... maybe the symlinks gets overriden by something else during the creation of the package (i'm just guessing :) )17:49
SpamapSRoAkSoAx: at this point all I can do is guess. :-/17:49
ebroderlooking at the diff from debian, there's probably a bunch of stuff you could drop if you merged rsyslog now - stuff like sysklogd transitional code17:49
SpamapSRoAkSoAx: I suppose I can ls -lR debian/mongodb in the rules file so we see what it looks like before that point17:49
RoAkSoAxSpamapS: or see if soemthing is installing in /usr/bin/mongo instead of just symlinking17:51
SpamapSRoAkSoAx: ls -lR will show that I hope17:52
SpamapSRoAkSoAx: doesn't relaly make sense that it would "change while reading" though17:52
SpamapSand why it does it only on the buildd's I'm a little confused17:52
juk_bug-buddy just caught stardict with: ** GLib **: /build/buildd/glib2.0-2.26.0/glib/gmem.c:239: failed to allocate 512 bytes17:52
SpamapShmm17:55
RoAkSoAxSpamapS: try building with a pbuilder instead ..17:55
ebroderpitti: by the way, i'd very much like to help with the perl-sectomy, or the footprint work more generally. please feel free to throw tasks at me if you'd like17:55
SpamapSI just updated my lucid schroot and one of the things it pulled down was this:17:55
SpamapSGet:14 http://archive.ubuntu.com/ubuntu/ lucid-updates/main tar 1.22-2ubuntu1 [390kB]17:55
pittiebroder: ooh, much appreciated17:55
RoAkSoAxSpamapS: ah!1 that might be it then17:55
SpamapSIf it breaks now, there may be a regression17:55
RoAkSoAxSpamapS: indeed17:55
RoAkSoAxSpamapS: btw.. is there a meeting today?17:56
SpamapSRoAkSoAx: yes, 18:00UTC, though I think that will be moved to 16:00UTC going forward17:56
RoAkSoAxSpamapS: ok cool... will be back later ... my battery is almost drained :)17:56
SpamapSlooks like zul forgot to update the header17:57
=== Claudinux_ is now known as Claudinux
pittiebroder: do you want to start with some small ones, like cups-driver-gutenprint and libfile-copy-recursive-perl?18:09
pittiebroder: not sure whether you followed the changes I already uploaded today?18:09
pittiebroder: in the ideal case, packages already don't need anything from perl-modules, so a simple dh_perl -d is enough18:10
pittiebroder: for some packages I needed to replace functionality from perl-modules with external programs (like rm -r) or other small replacements18:10
pittiebroder: I sent them to Debian, too, one patch is already accepted :)18:10
ogra_acpitti, we need to talk abotu the WI tracker some time this week ... (mobile got renamed to arm etc)18:10
pittiebroder: the biggest thing left is apparmor-utils18:11
ogra_ac(not today anymore though, just a heads up that i will ping you some time)18:11
pittiogra_ac: sure; please feel free to adapt natty.cfg yourself (~platform on lillypilly)18:13
ogra_acok18:13
ebroderpitti: sure, the small ones sound fine. i can look at apparmor-utils too if i get a chance, but what is our solution if a package does need something from perl-modules?18:14
pittiebroder: for easy cases I rewrote the code to just use perl-base18:14
jdstrandpitti, ebroder: you might check with kees on the apparmor one-- he may already be working on it18:14
pittiebroder: like "dirname"18:14
pittiebroder: for doc-base the only place that needed it was --dump-db, which is a debug option; I changed the code to say "Please install perl for this blabla" if you use it18:15
ebroderpitti: ok, sounds good. i'll try to be sufficiently creative18:15
pittiebroder: I haven't yet worked on a package where perl-modules is necessary for core functionality18:15
pittiebroder: in that case we still have the option to split out that module from perl-modules, so that we can install it separately18:16
pittiebroder: we should make a list of those in the blueprint, so that we can do that in a larger step18:16
pittiebroder: so if you stumble over one of those, please make a note there18:16
* ebroder nods18:16
cjwatsonI wouldn't do that casually though, the Replaces forest can get pretty insane18:16
pittiebroder: thanks! please let me know about the progress, so that we can coordinate18:16
pitticjwatson: no, we should try to avoid that18:16
cjwatsonyou'll probably run into File::Path at some point18:17
=== bjf is now known as bjf[afk]
pittifortunately so far it wasn't needed18:17
pittiyou can do surprisingly much with perl-base18:17
keespitti, ebroder: so apparmor-utils uses libterm-readkey-perl, librpc-xml-perl in the Depends18:18
=== sconklin is now known as sconklin-lunch
cjwatsonlibfile-copy-recursive-perl uses File::Copy which is in perl-modules18:18
ebroderpitti: in the cases where we can just do dh_perl -d, why don't i just make a note on the blueprint? it'll probably be faster for you to just do those than you dealing with a branch from me18:18
keesactually, ${perl:Depends}18:18
pittikees: right, those are fine (as soon as we fix those to not pull in perl); we need to fix apparmor-utils' "perl" dependency itself, though18:18
cjwatsonsometimes you can use the module optionally and implement some other fallback18:18
keespitti: it's coming from ${perl:Depends} I assume18:19
keespitti: shouldn't we fix dpkg's idea of that instead?18:19
pittikees: right, dh_perl adds a perl dependency by default18:19
cjwatsonkees: that's what dh_perl -d does18:19
keespitti: so what's the right solution?18:19
pittikees: I usually go through "grep -wr use" and check where all imported modules come from18:19
keesah, s/dh_perl/dh_perl -d/ in rules18:20
pittikees: and once nothing is left, change dh_perl to -d18:20
cjwatsonbe sure to check require as well as use18:20
pittiright18:20
* pitti will still do some maverick SRU catchup and then call it a day; enough breakage for one day :)18:21
pittiso, good night everyone!18:21
keesokay, I remain confused. what is the process to make sure I can switch to perl-base?18:27
keesbecause it seems like a lot of stuff lives in perl-modules, which requires perl currently18:27
pittikees: grep the source for "use" and "require" and check whether all of those are in perl-base, or standalone perl packages (which are seprate dependencies)18:28
keespitti: right, I have the list now. I guess doing the perl-name to package is the trick18:28
pittikees: for "use foo" I usually do "dpkg -S foo.pm"18:29
pittinot sure whether there's something better18:29
keesyeah, that's where I am too. Okay, cool.18:29
pittikees: thanks for looking into it!18:29
keesyou bet.18:29
keespitti: btw, with the loss of changelog.Debian.gz, people will not be able to examine their local filesystem to determine why a security update to a package was performed...18:30
keeswhat happens if I encounter something that requires perl-modules ?18:30
pittikees: they just came back :) (in reduced form), see u-d-a@ and planet18:30
pittikees: but apt-changelog should pick those up as well18:31
pittikees: for simple cases it's often possible to rewrite18:31
keesrequire Term::ReadLine;18:31
keespitti: ah, top 10 changes, nice.18:32
pittie. g. rmtree($dir) -> system('rm', '-r', $dir)18:32
keesuse Data::Dumper18:32
pittikees: that's more tricky; perhaps we could use libterm-readline-gnu-perl for that, and un-"perl"-ize (and MIR) that18:32
pittikees: Dumper was used in doc-base, but it was only a debugging tool; I did http://launchpadlibrarian.net/58890660/doc-base_0.9.5_0.9.5ubuntu1.diff.gz for that18:33
keesFile::Basename, the list goes on and on18:33
pittikees: as I said, this one will be hard :)18:33
pittiBasename is trivial to express with core Perl, though18:33
keeshrmpf.18:33
keesyeah18:33
pittikees: I don't (much) expect to actually be able to drop Perl completely in Natty; but working towards it18:34
kees-    mkpath ($d, 0, 0755);18:34
kees-    rmtree ($d.$suffix, 0, 0);18:34
kees+    system ('mkdir', '-m', '-p', $d);18:34
pittiat least it will be much easier to drop it for custom projects, etc18:34
keesthat's wrong. -m requires an argument18:34
pittikees: oops, thanks; didn't come up in testing18:34
keesI think we'd be better have a perl module that lives in -base that implements all these common uses18:35
pittikees: as I said above, for the more complex ones we might actually just split them out from perl-modules18:36
pittiso that we can install them separately18:36
keesokay.18:36
pittikees: fortunately most packages just look like http://launchpadlibrarian.net/58895007/foomatic-filters_4.0.5-0ubuntu3_4.0.5-0ubuntu4.diff.gz18:37
keespitti: heh, good. apparmor-utils seems to make up for it. :) 6 things from -modules or perl itself. :)18:39
pittiI'll keep that for later then :)18:40
keesheh18:40
pittikees: I'll start with the simple libraries, they should be easy, and can collect necessary stuff along the way18:41
keeshave you replaced File::Temp anywhere yet?18:41
pittino18:41
pittiI touched some 6 packages so far, 4 were trivial (just add -d), one required a simple code change, and doc-base was the one nontrivial one so far18:41
pittikees: (doc-base fixed, FTR, thanks for spotting)18:42
keespitti: cool18:42
SpamapSRoAkSoAx: darn, no failure with the updated tar18:43
keespitti: oh, actually, sorry, it's still wrong. File::Path::mkpath's $mode is filtered by umask where as mkdir -m is not.18:44
pittikees: but it's just a cache from public doc data..18:44
apwpitti, whome owns the launchpad-janitor scripting ?18:45
pittiI think having that directory 700 would be wrong18:45
pittiapw: launchpad?18:45
pittiapw: you mean the thing that autocloses bugs and so on?18:45
apwpitti, yeah indeed ... my real question is, is there a way to say 'really don't close this bug' so that we can have a proposed kernel with two uploads, the first one closes a bug and the second reopens it ...18:51
apwand if there isn't do we think that they would accept a new syntax to allow that18:51
pittiapw: accepting into proposed doesn't close bugs18:51
pittijust when they get moved to -updates18:51
=== Mamarok_ is now known as Mamarok
apwpitti, right ... exactly but when it does go into -updates everying in the changelog which is all proposed versions in one block via -v<old updates version> get processed and closed18:57
pittiapw: correct18:57
pittiapw: so the followup upload has to change the changelog accordingly to not mention the dropped patches any more18:58
apwpitti, and i want to be able to close a bug in the first -proposed upload, but undo it in the second -propoesed upload ... so that the bug is not closed when moving to -updates18:58
pittiwe can't close bugs in the first upload18:58
pittithey aren't fixed if they are only in -proposed18:58
apwpitti, so it is acceptable to hand edit the changelogs to drop the LP: bits from the first upload to proposed to ensure they don't close on move to updates ?18:58
pittiapw: there is no actual need to start a new changelog record, though; you could just bump the existing one and drop stuff18:58
apwpitti, yep ... get you on the proposed not doing anything bit18:58
apwpitti, that is acceptable ?18:59
pittiapw: that works for me as well18:59
pittiwhatever is more convenient18:59
pittii. e. update the first changelog record, or add a new one for the new version and just retro-fix the previous one18:59
pittithe former would look less confusing to users, though18:59
apwpitti, doesn't that mean that our changelog sort of lies ?19:00
pittiapw: not really IMHO; the bits that get released to -updates never had the dropped changes after all19:00
pittiapw: but as I said, I'm also fine with your method19:00
apwpitti, ok thanks19:00
* pitti waves good night for real now19:02
RoAkSoAxSpamapS: weird then19:04
cjwatsonkees: BTW, best not to do any of this (perl-base -> perl) unless you have to, IMO - I don't think we should be aggressively doing it for stuff not on the CDs19:06
cjwatsonapw: why list them in the -proposed upload in the first place, then?  Why not just say "see LP #nnnnnn" (or some similar syntax which carefully doesn't match the close regex) if you just want to refer to it?19:08
bilalakhtarpitti: So this means that there won't be a debian/changelog in ubuntu packages from now on?19:09
apwcjwatson, well we are uploading a -proposed with them in where they should close, then if they fail testing we revert them and want them not to close any more... seems the appropriate thing is to as you say change that first reference from LP: xxx to SEE: xxx and we'll be golden19:10
bilalakhtarBTW, why is -proposed frozen?19:11
cjwatsonapw: so you're not unconditionally leaving them open in -updates, only if -proposed fails?19:11
cjwatsonbilalakhtar: be careful about the distinction between debian/changelog (source packages) and changelog.Debian.gz (binary packages).  pitti's work only affects the latter (and there's open TB discussion about it)19:11
cjwatsonbilalakhtar: -proposed is frozen to assist the Linaro 10.11 release19:11
bilalakhtarcjwatson: okay, thanks19:12
cjwatsonor was frozen, I think I saw slangasek saying he was OK with it being unfrozen nowish19:12
apwcjwatson, we are marking them for closure yes in the first upload to -proposed, then we re-upload to -proposed undoing the commits which didn't work (or could not be verified) so we have a changelog block which has them closing and one which reverts that change.  when that moved to -updates it would erroneously close (via the janitor) so we were checking how to best avoid the bad close.  it seems effecticly removing the bug numbers from the first ch19:13
apwangelog section is the right approach19:13
cjwatsonor you could just reopen after the janitor closes them19:13
cjwatsonconsider how much technical work is worth it :)19:13
cjwatsontechnically, a reupload ought to require some degree of reverification, which is expensive19:14
apwcjwatson, heh indeed, i think updaing the references in the old is easier than touching all the bugs as we can script the former19:14
apwcjwatson, yes, and the regression testing is meant to occur on the second upload to give us more confidence19:14
loolHmm any idea why postgresql-9.0 isn't in natty?  I see it has been in unstable for ~20 days, perhaps we only sync packages which made it to testing?19:17
cjwatsonyou can script the latter too ... :-)19:17
cjwatsonlool: no, it's because it delivers at least one binary package (libpq-dev I think) which is also in natty built by another source package.  I asked pitti about it and he said he wasn't sure if he wanted to switch to 9.0 yet19:18
cjwatsonlool: testing isn't related19:18
cjwatsonapw: sounds like a lot more work to me, but as you like ...19:19
loolcjwatson: Ok; thanks for the explanation, I remember you also mentioned that in your email, just didn't think of this explanation19:19
=== bjf[afk] is now known as bjf
robbiewcjwatson: so http://cdimage.ubuntu.com/ubuntu-server/daily/current/ has server images for Mac/PPC32/PS3...was this done on purpose?19:36
robbiewconsolidation?19:37
cjwatsonrobbiew: yes, https://blueprints.launchpad.net/ubuntu/+spec/ubuntutheproject-foundations-n-cdimage-ports-consolidation19:37
cjwatsonkilling off the ports directories in general19:37
robbiewah ha!  I knew there was a blueprint19:37
robbiewcouldn't find it19:37
robbiewthanks!19:37
robbiewcjwatson: so from a QA perspective, did we agree to test these as well?19:38
cjwatson(though the exact set of images being built may well change ...)19:38
cjwatsoncertainly not, no19:38
robbiewcool19:38
robbiewhggdh: ^^^19:38
cjwatsonthere's a separate blueprint somewhere for what we should be testing19:38
cjwatsonthis was just reorganisation of what we were already building19:38
cjwatsonmind you, *somebody* should be on the hook to test anything we build19:38
cjwatsonbut it shouldn't necessarily be Canonical QA19:38
hggdhcjwatson, robbiew: thanks19:38
robbiewcjwatson: ack19:39
robbiewagreed19:39
robbiewcjwatson: so much for me requesting PS3s for the Server team19:39
robbiewlol19:39
=== dendro-afk is now known as dendrobates
ajmitchrobbiew: surely you could get a few PS3s donated to willing community members to test? :)19:44
robbiewheh...they don't even support Linux as another OS anymore ;)19:45
=== sconklin-lunch is now known as sconklin
cjwatsonrobbiew: :-)19:48
cjwatsonyeah, I think ps3 was slated to be EOLed, I'm just waiting for somebody who purports to be authoritative for that port to tell me - don't like doing it by fiat19:48
robbiewcjwatson: so who's authoritative for PS3?19:49
cjwatsonrobbiew: good question.  I passed it on to somebody called IIRC Tiago Faria a while back, but I don't know who took it from there19:59
=== almaisan-away is now known as al-maisan
=== dendrobates is now known as dendro-afk
wgrantpitti: Hm, that's unfortunate.20:36
=== ximion1 is now known as ximion
=== ximion is now known as ximion1
=== ximion1 is now known as ximion
jdstrandsbeattie: fyi, apparmor hit maverick-proposed20:50
sbeattiejdstrand: cool, thanks20:51
=== tkamppeter_ is now known as tkamppeter
=== dendro-afk is now known as dendrobates
lifelesssladen: hi21:40
sladenlifeless: hello21:43
highvoltagehi lifeless and sladen!21:48
=== dendrobates is now known as dendro-afk
mathiazcr3: http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html22:04
mathiazcr3: ^^ this is the SRU tracker I mentioned22:04
cr3mathiaz: thanks, zul actually answered me. email sent to victorp for his information22:06
=== dendro-afk is now known as dendrobates
=== al-maisan is now known as almaisan-away
=== bjf is now known as bjf[afk]
=== dendrobates is now known as dendro-afk
=== Lutin is now known as Guest92219
bdrungkirkland: thanks for the merge. can you move the errno tool from u-d-t to bikeshed?23:51

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