/srv/irclogs.ubuntu.com/2007/12/13/#ubuntu-devel.txt

FujitsuOh, so it does actually redirect to the right place.00:00
LaserJockyeah00:00
LaserJockKeybuk: would your plan help upstreams who want to just be able to maintain their packages in Ubuntu?00:37
LaserJockfor instance could they be given their own seed for there little set of packages? or does that become waaay to many seeds00:38
KeybukI suspect my plan would actually involve some kind of Soyuz feature where it had a link between people and source packages in distributions00:40
Keybukso you could set a maintainer team for any package00:40
Keybukand we'd keep them up to date through the seeds00:40
Keybukso in theory, a non-seeded package could be owned by a team consisting of the upstream and ubuntu-dev, yeah00:40
Keybuk*shrug*00:40
Keybukor you could just make a small seed :)00:40
Keybukbut yes00:41
LaserJockI know Mark was keen on allowing upstreams to have a sane path for uploading their packages00:41
Keybukthe idea is to make it easier for people to start contributing to Ubuntu on a more limited set of packages than "here's 10,000"00:41
LaserJockand Debian seems to be doing similar stuff with Debian Maintainers00:41
Amaranth"here's 10,000" scares the shit out of me :P00:42
LaserJockoh come on, it's fun :-)00:42
Keybukbut also, we wouldn't want "maintainers" in the debian sense - which is why ubuntu-dev should be in all of the teams00:42
Amaranthyeah, that's why i'm motu but haven't uploaded a single package yet :P00:42
LaserJockKeybuk: exactly00:44
FujitsuHm, why would a package FTBFS here without libxext-dev, but not in Debian? I thought our X stuff was fairly similar.00:44
slangasekFujitsu: for some reason, the Debian libx11-dev depends on libxext-dev and the Ubuntu one does not01:31
somerville32slangasek, I was doing some goggling today and you can be mean :P01:32
slangaseksomerville32: why yes, I can :)01:32
Fujitsuslangasek: Aha. Would that be a bug on our side?01:32
slangasekFujitsu: I don't know; I haven't looked closely to see if there's bugginess anywhere, or just a difference in how the packages are built01:33
KmosFujitsu: it's not the first one.. i've a similar one this week, let's find it01:37
FujitsuKmos: Not the first one of what?01:38
Kmos[00:44] <Fujitsu> Hm, why would a package FTBFS here without libxext-dev, but not in Debian? I thought our X stuff was fairly similar.01:39
Kmosit's xdemineur package01:39
FujitsuI know there are quite a number, and we carry diffs for several.01:40
FujitsuThat being the only delta.01:40
FujitsuAnd Debian rejecting said delta when you (Kmos) forward it to them.01:40
Kmosfor example.. libx11 in debian experimental doesn't depends on libxext-dev, but the version at unstable depends on it01:42
Kmosso, debian maintainer of xdemineur, updated the package and added libxext-dev to b-d01:42
Kmos:))01:42
Kmosso we have synced it01:42
slangasekFujitsu: well, in general if a package references xext directly, and doesn't build-depend on it, this is a bug in that package regardless of whether libx11-dev should have a dep on libxext-dev.01:43
=== DrPepperKid is now known as MacSlow
slangasekFujitsu: so if Debian is rejecting these fixes, please point me at them :)01:43
* Fujitsu digs up that bug.01:43
FujitsuDebian bug #455224 is an example of a rejection (one of Kmos', in fact)01:44
ubotuDebian bug 455224 in bbkeys "Please add libxext-dev to build depends" [Normal,Open] http://bugs.debian.org/45522401:44
slangasekah, well01:45
KmosFujitsu: that one is very aggressive from Bruno :( it's one of the debian developers that doesn't care about ubuntu01:45
slangasekKmos: but it's a strategic error on your part to submit a bug to Debian saying "we did this in Ubuntu, please do it too" instead of explaining why it's also a bug in the Debian package :)01:46
Kmosslangasek: you're right01:47
Kmosi need to go.. 2 am here01:48
Kmoscya01:48
slangasekok, Debian bug #455224 reopened with commentary01:54
ubotuDebian bug 455224 in bbkeys "Please add libxext-dev to build depends" [Normal,Open] http://bugs.debian.org/45522401:54
Fujitsuslangasek: Danke.01:54
* StevenK waits for the BTS to catch up01:55
* persia admires slangasek's skill with a laser pointer02:01
TheMusoHrm. Is the autosync likely to be run before DIF?02:02
* persia hopes so, as otherwise DIF would already be in place. perhaps at DIF?02:02
* StevenK waits for Bruno to reply to slangasek, "My packages don't have bugs. This is Debian."02:03
slangasekStevenK: that would be unfortunate, because then I would have to give somerville32 another example of my meanness02:07
StevenKHaha02:08
sorenIf a conffile gets renamed, that should be handled in preinst, right?02:08
* soren is allowed to ask stupid questions at this hour02:08
slangaseksoren: in order to allow the dpkg conffile handling to trigger during the unpack phase, ye02:08
zulhey soren02:08
slangaseks02:08
sorenzul: Ahoy.02:08
StevenKslangasek: Maybe you could take a leaf out of my book and reply back, "Bruno, I am going to eat your liver." ? :-P02:08
sorenslangasek: Thanks.02:08
=== mjg59` is now known as mjg59
slangaseknow, which was the package I NMUed where I handled conffile migration on downgrades.. :)02:10
StevenKHah02:11
soren\o/ multipath-tools uploaded.02:16
* soren needs sleep... badly.02:16
slangaseklamont: looks like gettext hasn't been uploaded yet?02:22
somerville32Does the linux packages not use a patch system?02:33
Fujitsusomerville32: It's in git.02:33
somerville32I mean, our linux packages02:33
somerville32or do we have it in bazaar or something?02:33
mjg59It's also in git02:33
somerville32Why are we using git?02:34
FujitsuBecause upstream does.02:34
slangasekfor easier interop with upstream02:34
somerville32Where is it hosted?02:34
infinitykernel.ubuntu.com02:35
slangasekhttps://wiki.ubuntu.com/KernelGitGuide02:35
* Fujitsu points at https://wiki.ubuntu.com/KernelGitGuide02:35
FujitsuBlergh.02:35
slangasek:)02:35
* somerville32 goes to patch the kernel! :)02:35
lamontslangasek: it was a bad day. doing gettext now.03:42
=== panchoat is now known as iE17
lamontslangasek: did someone do libtool already, I wonder?04:14
lamontgettext testbuild running04:15
=== asac_ is now known as asac
=== calc_ is now known as calc
=== Shely is now known as Schneeflocke
slangaseklamont: libtool is still on the menu06:17
slangasekbut it's a -1 increment, so I'm not too worried06:17
choudeshwhat is up with the gnome-orca package in hardy?06:35
choudeshsuckers been broke for weeks06:35
encompassHowdy everyone!06:51
doko_TheMuso: do you merge espeak as well?07:03
=== doko_ is now known as doko
warp10Hi all!07:06
TheMusodoko: I don't see the point, as we've essentially got the same changes as Debian. I'm going to work with Debian for the next upstream release so we can just sync.07:14
dokoTheMuso: ok, thanks07:15
=== antdedyet is now known as jtraylor
=== jtraylor is now known as antdedyet
=== antdedyet is now known as jtraylor
=== jtraylor is now known as jonathant
=== jonathant is now known as jtraylor
=== jtraylor is now known as antdedyet
kagouGood morning07:39
dholbachgood morning07:41
TheMusoHey dholbach.07:42
ion_Hi07:42
dholbachheya TheMuso, hey ion_07:42
kagouhey dholbach07:42
dholbachhi kagou07:42
=== Shely is now known as iSchnee
=== pbn_ is now known as pbn
pittiGood morning08:14
Burgundaviahey pitti, mvo08:14
mvohey Burgundavia!08:15
StevenKMorning pitti08:16
warp10hey pitti08:17
=== \sh_away is now known as \sh
=== \sh is now known as \sh_away
=== DrPepperKid is now known as MacSlow
MacSlowGreetings everybody!08:53
pittihi MacSlow09:04
MacSlowTag pitti09:04
mvodholbach: do you mind if I do your gnome-mag merge?09:06
dholbachmvo: not at all09:07
* dholbach hugs super-mvo09:07
mvothanks dholbach!09:07
* mvo hugs dholbach09:07
dholbach:-)09:07
LaserJockis there any one person that takes care of abiword?09:11
TheMusomvo: I'm already half way hrough it, if you've got more important things to do, I can finish what I've started.09:12
TheMusothrough it09:12
mvoTheMuso: sure, I leave it then09:12
KeybukI am delighted by the BT engineer's disbelief at how my house is wired09:13
BurgundaviaKeybuk: the sheer number of devices or the amount of network cable?09:13
Keybukthe fact that apparently one of the last endless procession of BT engineers wired it so that the phone line comes into the master socket, goes upstairs to another socket there, and then comes back to the master socket again09:14
TheMusoThat is crazy.09:14
Burgundaviawow09:14
seb128lamont: did you look at bug #175775 or did you re-do the gettext update?09:17
ubotuLaunchpad bug 175775 in gettext "Please merge gettext 0.17-2 (main) from Debian unstable (main)" [Wishlist,Confirmed] https://launchpad.net/bugs/17577509:17
mvoanyone working on the hotkey-setup merge?09:17
MacSlowhi mvo09:18
MacSlowdholbach, Aaaalter... Schwede! :)09:19
loolTheMuso: Hi there; just sent a proposal for promotion to main of colorblind; I heard you were interested with this subject09:19
TheMusolool: Ah right. Funny you should mention that, as if colorblind was in main, gnome-mag could be synced. :)09:20
TheMusoAs the only ubuntu change is to not build against it.09:20
loolTheMuso: It's because I wanted to work on the gnome-mag merge that I noticed actually ;)09:20
mvohey MacSlow09:20
TheMusoSo, depending on how quick a turn around an MIR for something like that is, I may wait on the merge, and just sync when colorblind is in main.09:21
TheMusolool: Right.09:21
TheMusolool: Ubuntu already has the same upstream as Debian, so I think waiting for colorblind to come in and syncing makes more sense actually.09:21
TheMuso.c09:31
TheMusough typo09:31
mvocjwatson: do we use the dash udeb? it got removed from debian09:59
StevenKI thought we used busybox?09:59
mvoI think so too, but I'm not sure enough10:00
StevenKmvo: Me either.10:00
KmosNot available because:10:03
KmosBuilder returned BUILDERFAIL when asked for its status10:03
Kmoskohnen builld machine10:04
Kmos*buildd10:04
Kmosinfinity: you already know about this error :)10:04
StevenKKmos: Yeah, but it's 3am where infinity is.10:04
Kmosoh god :( sorry10:05
StevenKI doubt an IRC message will get him out of bed.10:05
Kmosme too10:05
mvoStevenK: aren't you in the same TZ as him?10:05
=== \sh_away is now known as \sh
seb128dholbach: the vinagre sponsorship request is on hold because it requires a new gtk-vnc and this one is buggy, should I do something to get vinagre out of the "waiting on sponsor" stats?10:51
dholbachseb128: no that's fine, I'll just ignore it on the list as I know you're handling it - that's fine10:54
dholbachif you want, you can unsub the sponsors team10:54
seb128ok10:54
dholbachbut it's not necessary, I'm sure it'll be done soon10:54
seb128yeah, I'll not unsubscribe10:55
seb128the things is that the gtk-vnc upstream tarball is buggy10:55
=== pedro is now known as pedro_
seb128I'm wondering how the guy who did the update managed to build it10:55
dholbachoh nice10:55
seb128my guess is that he didn't even try10:55
seb128because ./configure doesn't work, the tarball lacks an install-sh10:55
dholbachARG10:56
seb128and he did a bunch of other updates, I'm wondering if he's testing anything10:56
dholbachbest to add that comment to the bug10:56
seb128or just running dch and opening bugs10:56
seb128I did, waiting for a reply now10:56
pittidholbach: will you care about your three outstanding merges, or shall I help you?11:01
seb128pitti: the platform team splitted the remaining merges during the meeting yesterday11:01
pittiok, thanks11:01
dholbachthanks :)11:01
pittiwe might actually be able to sync libgnomemm2.6, but I didn't check the small patch details11:04
seb128pitti: lool said he would do this one, you might want to ask him if he had a look yet11:07
pittiok11:08
pittiKeybuk: python-distutils-extra is a nice corner case; 1.91ubuntu3 is in Debian unstable, so the package is actually synced; could MoM be taught to not display those?11:11
Keybuknot easily11:12
pittiok; easy enough to ignore11:15
=== pedro is now known as pedro_
* pitti holds up a transparent "geser for core-dev!"11:27
=== cjwatson_ is now known as cjwatson
=== \sh is now known as \sh_away
=== cprov is now known as cprov-out
=== kiko is now known as kiko-fud
=== Kmos_ is now known as Kmos
encompassSo MeMaker is getting REALLY busy and we need a list... how can this happen?  Does ubuntu provide any, or is there some place we can use to make a list?13:25
=== cprov-out is now known as cprov
_MMA_encompass: A list of?13:31
encompass_MMA_: mail list, sorry for not being clear enough13:32
persiaencompass: Ubuntu has mailing lists, but only for Ubuntu.  Do you mean for https://launchpad.net/memaker?13:32
encompasspersia: yeah... things are getting very busy and we need to get things organized before we get burned out13:33
_MMA_encompass: PM.13:33
persiaencompass: I think it might be tricky to get a mailing list on lists.ubuntu.com (but I'm not an expert).  You might ask in #launchpad if there is any support there.13:34
encompasspersia: thanks I will13:34
persiaencompass: Good luck.13:35
se2re13:35
=== se2 is now known as seb129
seb129re13:35
seb129I've issue with dapper being very slow to boot on a recent enough computer (PIV 2.4GHz), each boot line is taking some seconds13:36
seb129did anybody already had a similar case or any idea on what could create that and fix it?13:36
seb129windows works correctly on the box13:36
seb129debian has the same slow boot issue13:36
seb129the issue is not only at boot, it's a slow when using13:37
Mithrandirseb129: it's very disconcerning when you have a off-by-one bug in your nick.13:37
StevenKBwahaa13:38
seb129Mithrandir: write to the correct nickname I'll read it anyway :p13:39
lamontseb128: I applied our patch to gettext 0.17-213:41
seb129ok, nobody has an idea about that?13:43
* lamont notes that someone bumped kde up to 5000 in the queues... I guess that means they're done uploading kde 16 times. :-)13:45
Hobbseelamont: no, just parts of it sorry13:45
Hobbseelamont: but i've put in the hope of that, yes.13:45
Hobbseelamont: whether the uploaders do it is another story, perhaps.13:45
lamontand the fact that hppa hasn't launched a build in about 12 hours means that it's academic until we figure that out13:45
lamontHobbsee: given that pretty much any package whose name starts 'kde' takes 1-5 hours to build, and the burstiness of the uploads, I have been known to smack them down to a build pri of 300 so that hppa can get through the queue13:46
Hobbseelamont: by all means, but make sure the base packages get built before the rest do.13:46
lamontOTOH, it's only fair to let them in sometime, and besides, LP keeps reprioritizing them.13:46
Hobbseewhich is why some of them got bumped in that order.13:46
lamontah, makes sense... so they don't do versioned build-deps either, eh?13:47
Hobbseewell, sure they do13:47
Hobbseebut LP of course goes and tries the others, before the base ones.13:47
Hobbseewhich still takes time and such13:47
bigonhi, is it normal that there is no more usbfs mounted on hardy?13:51
persiabigon: Mostly.  There's a /dev/usb/ tree that contains much of that information.13:52
pittibigon: not just since hardy; we got rid of that in feisty or so13:52
* persia thought it was early gutsy13:53
bigonbigon@imladris:/dev/usb$ ls -la13:53
bigontotal 013:53
bigondrwxr-xr-x  2 root root      60 2007-12-13 07:42 .13:53
bigondrwxr-xr-x 13 root root   14420 2007-12-13 14:52 ..13:53
bigoncrw-rw----  1 root root 180, 96 2007-12-13 07:42 hiddev013:53
bigonthere is nothin usefull in /dev/usb13:54
persiabigon: My mistake: /dev/bus/usb13:54
bigonpersia: /dev/bus/usb doesn't exist13:54
persiabigon: Does for me, but my system is known to be odd.13:55
bigonlsusb says nothing13:55
bigonmm13:55
* bigon reboot13:55
persiabigon: Do you have the right modules loaded?13:55
=== dholbach_ is now known as dholbach
Keybukpitti, mvo: ping14:00
mvohello Keybuk14:00
=== kiko-fud is now known as kiko
bigonok it's a kernel issue with 2.6.2414:05
bigonwith 2.6.22 I get /dev/bus/usb, with 2.6.24 i don't14:05
=== Kmos_ is now known as Kmos
persiabigon: Likely a udev / kernel coordination thing.  Do you get /sys/bus/usb?14:16
Keybukthat's correct14:18
=== \sh_away is now known as \sh
persiaKeybuk: Is there another transition planned for that information, or is this just expected hardy breakage while development is underway?14:19
Keybuk?14:20
Keybukit's expected breakage for running non-default kernels ;)14:20
persiaKeybuk: Ah.  Right :)14:21
Keybukthe userspace bits haven't caught up yet14:21
bigonpersia: yes I have a /sys/bus/usb directory14:37
persiabigon: Then the kernel is doing it's job.  udev should catch up soon (likely around the same time as linux-meta)14:37
bigonok14:38
bigonthx14:38
dholbach * Riddell bigs up Kubuntu Tutorials Day in half an hour in #kubuntu-devel https://wiki.kubuntu.org/KubuntuTutorialsDay14:43
* dholbach passes on the message :)14:43
=== kiko is now known as kiko-phone
=== cprov is now known as cprov-lunch
=== Hobbsee_ is now known as Hobbsee
seb128soren: so, does the consolekit upgrade fix your issue?15:17
seb128pitti: can you give a build retry to gdm on the archs where it didn't build?15:18
pittiseb128: done15:19
seb128pitti: thanks15:19
sorenseb128: I haven't tried it yet. I'm a few days behind on updates on this box..15:25
seb128soren: ok15:25
wiphi, is there people involve in the rt kernel?15:49
_MMA_wip: #ubuntu-kernel is the place.15:51
wip_MMA_: thanks15:52
=== cprov-lunch is now known as cprov
=== \sh is now known as \sh_away
pittimvo: hm, your python-apt merge looks like it shuold have been a sync?16:30
mvopitti: it needs to build against the right version of apt16:30
mvopitti: but yeah, its *very* close16:30
pittimvo: ah, just b-dep version change?16:31
pittiwell, that's just a timing issue :) but nevermind16:31
mvopitti: heh :)16:35
=== cpro1 is now known as cprov
geserlamont: can you give-back librpcsecgss and biloba? (FTBFS due to chroot problems on hppa)17:20
lamontgeser: are they chroot-problems, or are they build failure?17:21
geserlamont: both are CHROOTWAIT: http://launchpadlibrarian.net/10192942/buildlog_ubuntu-hardy-hppa.biloba_0.4-2_CHROOTWAIT.txt.gz and http://launchpadlibrarian.net/10374771/buildlog_ubuntu-hardy-hppa.librpcsecgss_0.17-1ubuntu1_CHROOTWAIT.txt.gz17:23
lamontthere are 3 that are chroot-failure, I'll give all 3 back once we make sure it's working again17:24
geserok and thanks17:24
Mithrandirmvo: any idea what might cause -rw------- 1 root root 4,0G 2007-12-13 06:39 /var/log/apt/term.log17:28
Mithrandir?17:28
geseris DIF already in effect?17:31
DktrKranzlamont, mind give-back yorick-curses yorick-hdf5 yorick-imutil yorick-soy yorick-yeti ?17:34
lamontDktrKranz: architecture?17:35
lamontMithrandir: I'm gonna bet "something looping asking a question."  How'd I do?17:35
Mithrandirlamont: not too bad, I believe.17:35
lamont^517:35
DktrKranzlamont, each for yorick-yeti, lpia and hppa for yorick-curses yorick-hdf5 yorick-imutil yorick-soy17:36
Mithrandirlamont: it's filled with ^G, though, which is special17:37
lamontoh... loop of beeping.  cool.17:37
lamontfor (;;) { printf("\a\n");}17:37
Mithrandirindeed17:38
lamontif <wtmp says userid==tfheen> { for (;;) { printf("\a\n");} }17:38
lamontDktrKranz: it'll take me a bit - I need to go heads down on something for about an hour and a half or so, it'll be top-of-list after that (any and all yorick-* packages on any architecture that are failed and current)17:40
* lamont iconifies xchat17:40
DktrKranzlamont, no hurry. thanks.17:40
lamontmy daughter has reviewed "Ubuntu for non-geeks, second edition": "The back of the book is completely unhelpful.  It tells us nothing of why the walruses are in the cover art."17:50
Asulaohello. need to use gtk glib functions, but can't seem to find a package named glib or import library. What's the package name in Ubuntu please?17:59
pochuAsulao: libglib2.0-dev18:01
Asulaopochu: sorry I didn't explain... I want to use glib from python18:01
Asulaohave gtk installed, but can't seem to find glib functions (if they do exist)18:02
Asulaopygtk18:02
geserAsulao: then probably python-gtk218:03
Chipzzgeser: python-gtk2 does not contain any files with glib in their name18:04
Asulaogeser: I do have that installed, but can't seem to find a glib.pyc or the sort.18:04
Asulaonor documentation for the glib module18:04
ChipzzAsulao: what functions do you need exactly?18:05
Asulaog_timeout_add and so18:05
ChipzzI think you should use gtk.timeout_add18:07
Chipzzthat's what ggogling suggests anyway18:08
Chipzz*googling18:08
ChipzzAsulao: anyway, I think #pygtk on irc.gnome.org would be a more appropriate place to ask18:08
Asulaook. great. I'll go there. many thankses. :-)18:09
=== pedro is now known as pedro_
mvoMithrandir: woah, that is impressive. what does it look like inside?18:45
mvoMithrandir: and where do you see it?18:46
Mithrandirmvo: on a gutsy amd64 server.  It mostly contained ^G-s18:53
geserlooks like the last dash upgrade broke the sparc buildd :(18:54
=== Kmos_ is now known as Kmos
Kmosgeser: yep..18:56
Kmoshttp://launchpadlibrarian.net/10890584/buildlog_ubuntu-hardy-sparc.nginx_0.5.33-1_CHROOTWAIT.txt.gz18:56
mvogeser: ohhhh19:03
Kmosgeser: Mithrandir is fixing it19:04
mvoMithrandir: could I get access to a compressed version? I assume it compresses quite well ...19:05
=== pedro is now known as pedro_
Mithrandirmvo: sorry, I needed the disk space so I nuked it. :-(19:09
Mithrandirmvo: I'll make sure to tell you if I see it again19:09
mvoMithrandir: ok, sorry for the trouble :/19:09
CarlFKcjwatson: where do I submit a patch for bug #38442 ?20:16
ubotuLaunchpad bug 38442 in ubiquity "Ubiquity dialogues too large for 800x600 display" [High,Confirmed] https://launchpad.net/bugs/3844220:16
torkelCarlFK: attach it to the bug20:21
CarlFKthanks20:22
BurgundaviaCarlFK: I love you20:23
CarlFKwell, lets see if it is acceptable before we rush into things :)20:23
Chipzzcan't this just be fixed in the glade file or something20:30
Chipzzoh and btw20:30
ChipzzCarlFK: on a seperate note20:31
ChipzzCarlFK: gtk+ devel had patches for natural size for widgets20:31
Chipzz*has20:31
Chipzzmaybe these could be an improvement too?20:31
ChipzzCarlFK: please take a look at: http://mail.gnome.org/archives/gtk-devel-list/2007-November/msg00145.html20:33
Chipzz(and following messages)20:33
CarlFKlooking20:33
Burgundaviaslangasek: I can write the release notes for alpha220:33
Chipzzcjwatson: ping20:34
bryceI'm trying to rebuild my hardy pbuilder tree, however when I run `sudo pbuilder --create hardy`, I get this error:20:36
bryceThe following packages have unmet dependencies:20:36
bryce  aptitude: Depends: libapt-pkg-libc6.6-6-4.5 but it is not installable20:36
bryceE: Unmet dependencies. Try using -f.20:36
bryceany ideas what's wrong?20:36
slangasekBurgundavia: yes please :)20:37
slangasekBurgundavia: but where is the camera that lets you see I was just writing mail to ubuntu-marketing?20:37
Burgundaviaslangasek: don't need a camera. I have a direct brain feed of every Canonical employee20:38
slangasekis that what that tickle is20:38
bryceheya tor20:38
bryceheya tormod20:38
tormodhi bryce20:38
Burgundaviaslangasek: send the email anyway, it will help me remember to do it20:38
slangasekBurgundavia: right-o20:39
nixternalany archive admins hiding around here? we are having problems with hardy and main...can't pbuild with hardy, not can we update hardy pbuilder...404 on main20:46
geserbryce: a new apt in hardy, all reverse depends needs to be rebuild20:47
brycegeser: ah, is this something I can work aroudn on my end, or just wait for it to finish?  is there an eta known for when it'll be working?20:49
geserbryce: looks like you need to wait for the next publisher run, see https://edge.launchpad.net/ubuntu/hardy/+source/aptitude/+builds20:50
brycethanks20:50
=== warp10_it is now known as warp10
blueyedCan somebody please decide if Gimp final (2.4.2) should go through -updates/SRU or -backports, please? See bug 157642 and bug 164795. 2.4 is a bugfix only branch and users are quite embarrassed to have a buggy rc in gutsy.23:19
ubotuLaunchpad bug 157642 in gimp "gimp 2.4 *final*  in gutsy" [Undecided,New] https://launchpad.net/bugs/15764223:19
ubotuLaunchpad bug 164795 in gutsy-backports "Please backport gimp 2.4.2 from hardy to gutsy" [Undecided,New] https://launchpad.net/bugs/16479523:19
jdongblueyed: what is the nature of its bugginess?23:19
StevenKI still note that "buggy RC" is yet to followed up with other bug reports.23:19
blueyedzless /usr/share/doc/gimp/NEWS.gz for a start23:20
blueyedIt might be OK to decline it for SRU, but somebody should do so.23:24
StevenKblueyed: You still haven't answered my question.23:25
blueyedStevenK: I don't see any question from you. And I've provided a list of bugfixes, as you've requested.23:25
StevenKblueyed: Ah, I wasn't talking about bug fixes, I was talking about bug reports on Launchpad.23:26
StevenKIn fact, I said "bug reports"23:26
blueyedStevenK: An unreported bug which got fixed is no bug? Anyway, I've not triaged gimp yet much (but enough to have seen the cry for an update). I'm just asking for a decision.23:29
=== cheguevara_ is now known as CheGuevara
StevenKI'm yet to be completly convinced aside from users saying "How unprofessional is shipping an RC of gimp?"23:30
jdongblueyed: well if there's a huge shotgun list of bugs/defects that users are experiencing, then I think the argument can be made, but I don't see that so far....23:32
StevenKExactly my point.23:32
jdongblueyed: it'd also depend on how much testing the new version has gotten, and how much the interface/plugin-API changed23:32
blueyedI understand.23:33
blueyedjdong: it's bugfix-only.23:33
jdonghow large is the debdiff between the RC and final?23:33
blueyedthe one from hardy?23:33
jdongwell... I guess?23:34
StevenKYes, but saying it's bugfix only and pointing at real, Confirmed high-impact bugs on Launchpad are two *very* different things23:34
StevenK 881 files changed, 81411 insertions(+), 105144 deletions(-)23:35
StevenKRight, "bug fixes"23:35
blueyedjdong: the debdiff is 50M, but most is moved changelogs and .po stuff.23:35
LaserJockholy crap23:36
jdongblueyed: ok, do you know what number of bugs people are actively experiencing in our RC of gimp?23:36
LaserJockoops, sorry there23:36
jdongblueyed: if it's a small SRU-able number I think they should be individually targeted.... this big of a change is hard to argue for -updates unless the package is totally dysfunctional to begin with23:36
jdong(well all releases of gimp are dysfunctional in my hands but that's a different matter :D)23:36
blueyedjdong: yes, I understand. I'll then just add a comment to the -updates-bug and ask people to name/triage real bugs. I'm not a gimp user really either.23:37
LaserJockwe should take care of the SRU bug though23:38
jdongblueyed: right, I think that's a good start. Let's estimate the impact then decide what needs to be fixed.23:38
LaserJockwe tend to leave things linger23:38
LaserJock+ing23:38
blueyedStevenK: I have "1009 files changed, 606889 insertions(+), 371127 deletions(-)" btw (more)23:38
StevenKI will deal with it when seb128 has turned up and I've spoken to him about it.23:38
jdonghaha23:38
jdong"Attached is the debdiff for review....." :D23:38
StevenKOh god, we aren't using that23:39
jdongI think this beats my Xgl debdiff record :)23:39

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