/srv/irclogs.ubuntu.com/2009/05/11/#ubuntu-desktop.txt

=== ember_ is now known as ember
pittiGood morning06:48
pittididrocks: did you see the vte FTBFS due to the wrong python path? can you work on this?08:00
didrockspitti: yes, I will do it tonight08:23
didrocksHi everybody o/08:24
seb128hello didrocks08:25
seb128didrocks: do what?08:25
didrocksseb128: vte is ftbfs du to python path changes in karmic apparently (it was building successfully in jaunty)08:28
seb128ok08:28
didrocksseb128: I did gnome-python and ready for review08:28
seb128yeah I noticed thanks08:28
didrocksseb128: for gnome-python-extras, I was wondering about one thing08:29
seb128I'm catching up with weekend emails first then will do reviews08:29
didrocksseb128: ok, we will discuss that later so :)08:29
didrocksjust ping me08:29
seb128we can discuss that now08:29
didrocksok, it was about the patch 04_use_PYTHON-config_check.patch08:29
seb128I'm just no doing review now ;-)08:29
didrocksis it still usefull?08:29
didrocksit just add checking for more than one revision of Python, right?08:30
seb128not sure what is was doing08:30
seb128that was to not hard depend on a specific python version?08:30
didrocksmaybe. Without it, it's building against python 2.5 and 2.608:30
didrocksseb128: that's why I put the merge in ~didrocks/python-gnome-extras/ubuntu08:31
seb128ok, I will have a look later08:31
seb128ideally the issue should be reported to debian if the bug is still there08:31
didrocksI just left a comment in the changelog, but didn't integrate it, waiting for some thoughts :)08:31
didrocksyes, I checked and found nothing08:31
seb128what was the rational to add the patch? it should be explained in the changelog entry?08:33
seb128lut huats08:36
huatsmorning everyone08:36
huatsseb128hello !08:36
didrockshello huats08:39
huatshey didrocks08:40
didrocksseb128: no, it's not, regarding the changelog, there is just: "- debian/patches/01_use_PYTHON-config_check.dpatch08:41
didrocksit's listed on a merge against debian, and nothing more :/08:41
seb128let me look08:41
didrocksok08:41
seb128didrocks: I guess it has been added in this version https://edge.launchpad.net/ubuntu/+source/gnome-python-extras/2.14.2-1ubuntu208:43
didrocks"acinclude.m4: Fix PYTHON_INCLUDES; run autoreconf -i08:44
didrocksok08:44
didrocksso, I will ask doko08:44
seb128didrocks: I think it's needed to get the correct interpreter for the dbg build08:46
didrocksseb128: I don't really get it. We use python-config because the other one can't get the correct interpreter for debug packages?08:47
seb128PYTHON_INCLUDES="-I${py_prefix}/include/python${PYTHON_VERSION}"08:48
seb128is what upstream use08:48
seb128didrocks: see http://bugzilla.gnome.org/show_bug.cgi?id=44817308:49
ubottuGnome bug 448173 in general "use python-config to get python includes" [Normal,Resolved: fixed]08:49
didrocksseb128: ok, so. python-config is best to used than usual inclusion. Especially for dbg packages :)08:50
didrocksthanks ;)08:51
seb128didrocks: well, the hardcoded upstream variant doesn't have a case for dbg08:51
didrocksseb128: so, I will report a debian on GNOME bt08:51
didrockss/debian/bug08:51
seb128don't bother with debian08:51
seb128open an upstream one, debian will get it in the next version08:52
seb128or do it if you send the change for dbg packages there08:52
didrocksyes, that's what I meant :)08:52
seb128but you might have to send some other gnome-python dbg changes before that08:52
didrocksI might have to send other dbg changes?08:53
seb128python-gnome2-extras-dbg depends on python-gnome2-desktop-dbg and there is no python-gnome2-desktop-dbg in debian08:54
seb128so gnome-python-desktop needs to get a dbg variant first08:55
seb128and gnome-python too08:55
seb128chain of depends ...08:55
seb128to get a -dbg working you need all the depends to have a -dbg variant08:55
didrocksseb128: of course. So, I have some work to do on python-gnome2-desktop :)08:56
robert_ancellseb128: pitti: can you guys tell me what I'm supposed to do about bug 372592?  I thought it was ok to SRU these changes or should I just abort it.  The SRU request is to update to the latest stable version - is this appropriate?08:56
ubottuLaunchpad bug 372592 in totem "Update to Totem 2.26.2" [Wishlist,Fix released] https://launchpad.net/bugs/37259208:56
seb128yeah, that one will not be trivial08:56
seb128they splitted everything08:56
seb128don't bother splitted the -dbg I would say08:57
seb128debian want to use one -dbg by source08:57
seb128hello robert_ancell08:57
robert_ancellseb128: morning seb08:57
seb128robert_ancell: what pitti wrote there is "use the bugs for issues fixed in this version"08:57
seb128ie bug #36825208:57
ubottuLaunchpad bug 368252 in totem "Totem firefox plugin can't launch apple HD trailers" [Low,Fix released] https://launchpad.net/bugs/36825208:57
seb128or bug #366647 or bug #36282008:58
ubottuLaunchpad bug 366647 in totem "subtitle not re-loaded when totem restart" [Low,Fix released] https://launchpad.net/bugs/36664708:58
ubottuLaunchpad bug 362820 in totem "totem-plugin-viewer crashed with SIGSEGV in strchr()" [Medium,Fix released] https://launchpad.net/bugs/36282008:58
robert_ancellso I should SRU each of those?08:58
seb128use one of those for the sru08:58
seb128no, just use one of those to add the debdiff etc08:58
seb128I'm not sure why pitti has this policy now but that doesn't make much of a difference08:59
seb128rather than using the new version bug for the paper work use on the other bugs08:59
seb128open jaunty tasks for each issue the sru fix, add the debdiff to one of the bugs, subscribe ubuntu-sru to each bug08:59
didrocksseb128: ok. So, we wait for debian to do it in its own way, or do we go ahead and do it in the "ubuntu way"?09:00
robert_ancellok. I'm a bit confused by the process though considering you can only accept the whole update or none of it.09:00
seb128didrocks: gni?09:00
seb128robert_ancell: well, each bug concerned by the upgrade need to be confirmed as fixed and not creating new issues09:01
seb128robert_ancell: what is confusing?09:01
didrocksseb128: I'm a bit confused too by the "debian want to use one -dbg by source". But that's not what we do regarding those packages. So, I just add some -dbg for gnome-python-desktop binary packages?09:02
seb128didrocks: gnome-python-desktop has been splitted in different binaries, rather than adding a -dbg for each one just do it directly the debian way, use one -dbg for the source09:02
robert_ancellseb128: if there is no core bug for the update then it seems harder to link together.  It just feels backwards09:02
seb128didrocks: that will mean less work for you and easier to get it accepted by debian09:03
seb128robert_ancell: just make any of the fixed bugs the core one09:03
seb128robert_ancell: usually one sru fixes one bug so we use this bug as the core one09:03
robert_ancellseb128: And because it is a stable update it will include fixes that we don't have tracked09:03
seb128robert_ancell: you happened to have a case where several bugs are fixed so you still do that but in extra open jaunty task for the other bugs so they can be tracked too09:04
didrocksseb128: oh ok. understood :)09:04
seb128robert_ancell: the sru procedure tries to ensure that each bug closed is properly fixed ... if you want to reduce paper work don't list all the bug numbers in the changelog but only the one you consider worth checking to make sure they work and don't break anything09:05
seb128I'm not sure where pitti he could probably give you extra details on the current procedure and why the "new version" bug is incorrect09:06
didrocksseb128: when you will have some time: I just have an issue with gnome-python-extras: running autoreconf output some cycling dependencies that I can't get fixed :/09:07
seb128what do you mean?09:08
didrocksseb128: to take into account the previous patch, I have to run autoreconf in 70_..09:08
didrocksand there, I saw some "cycling dependencies" and it failed09:08
seb128didrocks:  can you pastebin the error?09:09
didrocksseb128: let me rebuild it on my server to get it (I just didn't copy it as I was unsure if we have to autoreconf it)09:10
seb128didrocks: why do you autoreconf? autoconf should be enough for this python path thing?09:10
pittirobert_ancell: no need to add the debdiff three times, but you need to justify each bug for SRU, describe impact, testing, and regression potential, and we will ask for verification on each bug09:11
pittirobert_ancell: since the best people to tell us whether it's fixed are teh reporters/subscribers of those bugs09:11
pittiseb128: we have always had this policy09:11
pittiseb128: for hardy you just filed new bugs for new upstream microreleases when we didn't have "real" bugs in LP already09:11
seb128pitti: I've been used "new version" bugs for srus before09:12
seb128right09:12
pittiseb128: and it makes a huge difference in terms of who will read the request for testing09:12
pittirobert_ancell: if one of the bugs is not eligible for SRU, we'll reject teh entire upload09:12
seb128they will read all the request for testing anyway09:12
pittirobert_ancell: and be warned, priority: low bugs have a very small chance of being accepted09:12
seb128and I think it makes sense to do some "new version testing" too in case of new versions09:12
pittirobert_ancell: if it's not dealbreaker and causes totem to crash for every second movie, please don't SRU it09:13
didrocksseb128: autoreconf is needed for aclocal.m4 patch (and autoconf does the same, btw)09:13
seb128pitti: I think the upload is SRU worth, it makes apple trailers work again and fix some browser crasher09:13
robert_ancellpitti: I don't think I can justify each bug by the SRU guidelines (at the time one or two seemed useful).  Now it is in Karmic it seems obvious that it should be requested as a backport.09:14
pittiseb128: regressions are valid SRUs (shoudl be regression-release then)09:14
seb128don't bother with backports09:14
pitti+1 ^09:14
robert_ancellseb128: interesting thing in this case - the regression was actually caused by Apple (they changed to a tag that totem didn't understand)09:15
robert_ancellWhat is the position on using BZR packages now?  I was updating Glade which is not in BZR, can I create one?09:18
seb128yes, feel free to add to bzr anything desktopish09:18
seb128http://wiki.ubuntu.com/DesktopTeam/Bzr09:18
robert_ancellseb128: (I remember you saying it was still a bit experimental when we were in London so not to push all the packages into it)09:19
robert_ancelllast question on my list: regarding gnome-games and clutter+libcanberra - I packaged 2.27.1 built using gstreamer and gnometris disabled.  I think we should go with that configuration for now and then decide at UDS what we do about clutter/sound.  Agree/disagree?09:21
seb128agreed09:22
seb128clutter will probably be an issue for CD space09:22
robert_ancellsure09:23
didrocksso, splitting gnome-games package?09:23
robert_ancelldidrocks: I guess we have to make a special case for gnometris for Karmic - it's going to get a whole lot more interesting Karmic+1 as there will be a lot more Clutter dependent games09:24
robert_ancellwhat else on the desktop uses clutter?09:24
didrocksrobert_ancell: yes, and with gnome-shell, at the end, it seems that we will have no choice09:25
robert_ancellthose annoying gnome-games developers. Making life difficult for integrators.  Hang on... :)09:26
didrockshehe :)09:26
robert_ancellgtg, see you guys tomorrow09:26
didrocksseb128: here it is http://paste.ubuntu.com/169387/09:35
seb128didrocks: ask to Keybuk maybe he has an idea about that09:36
didrocksseb128: ok. I'm pinging him :)09:40
=== dpm_ is now known as dpm
didrockspitti: I got it for vte. It's in the debian autoreconf patch that I haven't to generate. But I'm still wondering why it wasn't FTBFS in my jaunty pbuilder :/09:47
pittididrocks: you didn't have pkgbinarymangler installed09:47
pittiit's a check in pkgsanitychecks09:47
didrockspitti: oh, I have maybe to install it as a pbuilder hook, don't you think?09:48
didrockspitti: is it possible to simulate it, even if I don't have rosetta? (It seems to be used for stripping translation)09:49
seb128didrocks: rosetta has nothing to do with builds09:50
pittididrocks: no, it does more than that09:50
pittididrocks: just install it in the pbuilder, or your local system09:50
didrocksok, I give some test without fixing the issue to check it works at home :)09:51
pittididrocks: just dpkg -c the .debs to check for site-packages vs. dist-packages09:58
didrockspitti: I installed it with a hook in my pbuilder and yes, it wraps dh_builddeb (or a command that is called by it) and effectivelly, it FTBFS. I will keep this hook, thanks10:20
chrisccoulsonhi seb128 - you got any updates for me to work on later? ;)10:24
seb128hello chrisccoulson10:24
seb128chrisccoulson: want to resync gnome-panel or gnome-appets on debian?10:25
pittihey chrisccoulson, good morning10:25
chrisccoulsonyeah, i can do those10:25
chrisccoulsonhi pitti10:26
seb128excellent, they are for you then10:26
seb128thanks10:26
chrisccoulsonyou're welcome10:26
* seb128 still fighting bug emails from the weekend10:28
seb128IRC and bug backlog will have taken the morning10:28
seb128and I did read and reply to email twice this weekend10:28
seb128chrisccoulson: btw I don't know if you read the backlog on friday but you should run for MOTU now ;-)10:32
loolseb128: heya!10:33
loolseb128: how is it going?10:33
seb128hello lool10:33
seb128good, lot to do as usual, and a bit too many bugs open for details to my taste but other good ;-)10:34
loolEh10:34
seb128and you? did you have good holidays?10:34
loolYeah, it was nice to take some break10:34
loolI'd like to discuss https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/283447 with you10:34
ubottuUbuntu bug 283447 in netbook-remix "Undecorating maximised windows sometimes leaves a blank space below the window (Intrepid & Jaunty)" [High,Fix committed]10:34
loolI just added the Ubuntu package task and the jaunty task10:35
loolThis bug is an important issue in UNR and is fixedin metacity 2.26.010:35
loolDo you mind if we move to 2.26.0 in karmic and jaunty?10:35
loolIs anything preventing this update?10:35
seb128no, just somebody having interest for the software10:35
seb128I'm using compiz so didn't really bother and nobody else picked up on the task, talk to pitti perhaps about jaunty10:36
seb128it's probably better to backport the change there than to update to a new version10:36
loolseb128: So new version in karmic and backported fix in jaunty; will talk to pitti then, thanks!10:36
seb128new version in karmic without any doubt10:37
pittilool: you need this to be an ubuntu sru for UNR?10:37
loolpitti: Correct10:37
pittihmkay10:37
loolpitti: UNR being Ubuntu jaunty's UNR10:37
loolpitti: UNR is really in Ubuntu now10:37
pittiyeah, understood10:37
chrisccoulsonhi seb128 - i did see your conversation with dholbach on friday10:44
chrisccoulsoni'll hopefully get around to applying this week if you think i should:)10:44
seb128you should!10:46
* pitti puts on the "Chris Coulson for Pres^WMOTU!" badge10:46
seb128;-)10:47
seb128ok, time for some sponsoring now10:54
loolAh mvo is in holidays11:08
seb128is he?11:09
loolYeah, whole week it seems11:09
seb128we really need a VAC calendar we can add to e-d-s ;-)11:09
lool"update-manager -c -d" works on my desktop but doesn't on a jaunty UNR install11:09
loolah was just flaky network11:14
crevettehello, I've a small question how daniel did check there were missing files in https://bugs.edge.launchpad.net/ubuntu/+source/bluez/+bug/372428 ?12:39
ubottuUbuntu bug 372428 in bluez "[karmic] please sponsor bluez-4.38" [Undecided,New]12:39
crevetteand furthermore, what the the test I should conduct to validate I don't break things12:40
Hobbseecrevette: it's --list-missing as a switch, but i don't remember which tool it is.  it's dpkg-something12:42
* crevette tries dpkg-something :)12:42
crevettedpkg-something should be a wrapper for all dpkg* tools :)12:43
pittiHobbsee, crevette: you mean dh_install --list-missing ?13:14
Hobbseepitti: yeah, that sounds right!13:14
crevettepitti, is it possible to have it run in pbuilder in order to have a report at the end of the build ?13:15
pitticrevette: you can certainly run it in debian/rules13:15
pitticrevette: cdbs has an utils.mk for list-missing, too13:16
crevetteokay, I'll try tht, thanks13:16
chrisccoulsonis there any way of making dh_install --list-missing useful for packages that build multiple binaries? the last time I tried, it listed the missing files for each binary package in turn, and considered all files installed in one of the other binaries as missing for that particular package13:22
pittichrisccoulson: that works fine for me13:23
pittichrisccoulson: you just can't invoke it with -p, obviously13:24
chrisccoulsonpitti - thanks. i'll try again next time i need to do that and see if it works13:25
seb128it doesn't work for multi-build packages, ie when you don't  install to debian/tmp for example13:26
seb128ie that doesn't work for python packages which build for multiple version or for gtk+ which has a static, etc build13:27
chrisccoulsonthanks seb128. i think the last package i tried it on was tracker, and it didn't seem to work too well for that. i'll try it again as i'm looking at the 0.7.x packaging at the moment anyway and it would be useful for that13:33
* kenvandine_wk hopes this morning isn't a bad time to update :)13:52
pittikenvandine: not worse than any other morning :)14:01
kenvandinehehe14:01
kenvandineit worked14:01
kenvandinepitti: did you get a share request from me today?14:01
pittikenvandine: by mail? no14:01
kenvandineok14:01
kenvandineany idea why there is kde stuff in my updates?14:02
pittioh?14:02
* kenvandine doesn't think he installed anything kde related :)14:02
pittiwhat in particular?14:02
kenvandinekdebase stuff14:02
pittimight be a wrong new dependency14:02
kenvandinethat is what i am wondering14:02
pittikenvandine: if you just do apt-get upgrade, what does it hold back?14:02
kenvandinelet me try to remove it :)14:02
pittikenvandine: oh, it wanted to _upgrade_ kdebase, not newly install it?14:03
kenvandinenot sure, i was using update manager14:03
kenvandinenot apt-get14:03
kenvandinenot sure if it is easy to tell there14:03
pittidon't think so14:04
seb128pitti: do you have an opinion on code logic copy and copyright assignment?14:04
seb128pitti: ie gnotes being a tomboy copy in c++ ... should the copyright list the tomboy authors?14:04
pittiseb128: context?14:04
pittiseb128: it's a total code rewrite?14:04
kenvandineThe following packages have been kept back:14:04
kenvandine  f-spot gksu kdebase-runtime kdebase-runtime-bin-kde4 kdebase-workspace-dev kdebase-workspace-libs4+5 kdelibs-bin kdelibs5 kdelibs5-data kdelibs5-dev khelpcenter414:04
kenvandine  libkdecorations4 libkrb5-dev libkwineffects1 libltdl7 libphonon-dev libphonon4 libplasma3 libqt4-assistant libqt4-core libqt4-dbus libqt4-designer libqt4-dev libqt4-gui14:04
kenvandine  libqt4-help libqt4-network libqt4-opengl libqt4-opengl-dev libqt4-qt3support libqt4-script libqt4-scripttools libqt4-sql libqt4-sql-mysql libqt4-svg libqt4-test14:04
kenvandine  libqt4-webkit libqt4-xml libqt4-xmlpatterns libqtcore4 libqtgui4 libstartup-notification0 libstartup-notification0-dev linux-generic linux-headers-generic14:04
seb128they basically take tomboy and copy line by line translating to c++14:05
kenvandine  linux-image-generic linux-restricted-modules-generic openoffice.org-base-core openoffice.org-calc openoffice.org-common openoffice.org-core openoffice.org-draw14:05
kenvandine  openoffice.org-gnome openoffice.org-gtk openoffice.org-impress openoffice.org-math openoffice.org-style-human openoffice.org-writer phonon phonon-backend-gstreamer14:05
seb128kenvandine: grrrrr14:05
kenvandine  python-uno qt4-qmake qt4-qtconfig14:05
kenvandinewhoops14:05
seb128kenvandine: use pastebin please14:05
kenvandineit was 2 lines :)14:05
kenvandinesort of ... sorry14:05
pittiseb128: hm, no idea I'm afraid; would certainly at least be nice to credit them14:05
seb128update-manager doesn't install new packages or remove other binaries14:05
pittiseb128: "system upgrade" does, though14:06
seb128it does new installs but no removals14:06
kenvandinei must have something installed that brought it in as a dep14:06
james_wpitti: it's basically a line-by-line port for a lot of it. The tomboy authors didn't add headers to many of their files. Where they did they are preserved, but the other files only state (C) new author, which seems a bit wrong14:06
seb128kenvandine: what is the question?14:08
pittijames_w: I agree; even if it's legal, it's at least nasty14:08
kenvandineseb128: i was just wondering if there as a bad dep bringing in new packages... or if it was something i had installed14:08
james_wpitti: I don't see it as a reason to keep it out the archive though?14:08
kenvandinejust did an update today in karmic14:08
kenvandineseb128: just verifying there wasn't a bug14:08
kenvandinemorning rickspencer314:09
seb128kenvandine: your log lists kept back packages14:09
seb128hello rickspencer314:09
pittijames_w: that'd require a lawyer, I'm afraid14:09
kenvandineseb128: that was just answering pitti's question14:09
rickspencer3good morning kenvandine, seb128, pitti14:09
pittihey rickspencer314:09
seb128kenvandine: oh ok, I read the backlog, try to apt-get remove those and see what else get uninstalled, could be a recommends which triggered those14:10
kenvandineyeah14:10
seb128but it's easier to track that before clicking yes14:11
james_wpitti: ok, how should I proceed?14:11
pittijames_w: perhaps ask elmo? he's got much more license/copyright experience than me14:11
james_wpitti: ok, I'll mail him and CC ubuntu-archive?14:12
pittijames_w: sounds good14:12
james_wthanks14:12
james_wpitti: also, there is a linux-ports-meta in the queue. Would you have a few minutes sometime today to walk me through that, or to process it yourself?14:13
james_wseb128 is scared of the kernel ;-)14:13
seb128indeed!14:13
* kenvandine needs more coffee... bbiaf14:13
Ampelbeinseb128: hi. thanks for the little correction on the gnome-utils patch. however, i get failed builds on sparc, hppa and armel. on sparc and armel it's because of the "warnings treated as errors" and some sloppy program code. but on hppa it reruns autoreconf for some reason and configure fails with a syntax error. See http://launchpadlibrarian.net/26573002/buildlog_ubuntu-karmic-hppa.gnome-utils_2.27.1-0ubuntu1_FAILEDTOBUILD.txt.gz for14:14
Ampelbeinthis.14:14
seb128Ampelbein: I would not bother about the hppa case for now but working on an update not using -Werror would be useful14:22
seb128Ampelbein: the hppa case is probably a timestamp issue and autotools installed on the buildd machine, a retry on a clean install will probably work14:22
=== asac_ is now known as asac
Ampelbeinseb128: how do i disable -Werror ? should i just pass '-Wno-error=*' to CFLAGS in debian/rules? i can't find where -Werror is defined in the first place.14:33
seb128Ampelbein: configure.ac:        MAINTAINER_CFLAGS="-Werror -Wall -Wshadow -Wcast-align -Wno-uninitialized -Wformat-security -Winit-self"14:41
Ampelbeinseb128: ah, there it is. thanks. should i do a ubuntu2 for this?14:42
seb128Ampelbein: I guess editing that line in the configure and updating autoconf should work14:42
seb128Ampelbein: yes14:42
Ampelbeinok will do14:42
seb128thanks14:42
=== rickspencer3 is now known as rickspencer3-afk
jbaileypitti, What's mvo's excuse this time? ;)14:56
jbaileyHi all ;)14:56
pittijbailey: he's on holiday14:57
seb128he's on holidays for the week apparently14:57
jbaileyBah! =)14:57
seb128you can try dropping him an email though ;-)14:57
jbaileyAh well.  /me sits on his hands and waits.14:57
jbaileyNah, if he's on holidays I don't want to bug him.14:57
seb128I'm not sure how good he's at not readin email during holidays ;-)14:58
jbaileyMost Canonical people are terrible at the best of times.14:58
jbaileyHaving an email from a friend show up is almost a guarantee that it would get read.14:58
Ampelbeinseb128: bug 374889, branch linked.15:05
ubottuLaunchpad bug 374889 in gnome-utils "FTBFS due to -Werror on sparc and armel architecture." [High,Confirmed] https://launchpad.net/bugs/37488915:05
seb128_ok15:06
=== seb128_ is now known as seb128
=== awe is now known as awe-afk
=== awe-afk is now known as awe
Ampelbeinseb128: i think gnome-utils just got worse... now it even fails on i386 with the "syntax error" after rerunning autoconf on the build-daemon. See http://launchpadlibrarian.net/26586210/buildlog_ubuntu-karmic-i386.gnome-utils_2.27.1-0ubuntu2_FAILEDTOBUILD.txt.gz15:35
seb128Ampelbein: right15:36
seb128I hate autotools15:36
Ampelbeinseb128: is this my fault?15:36
seb128define "your" there ;-)15:37
seb128it's a bug in the package yes15:37
Ampelbeinit worked on pbuilder so this must be a race condition.15:37
seb128it is15:37
seb128the autotools try to be clever15:37
seb128if some timestamps are never than others they run autoconf or automake for you15:38
seb128never -> newer15:38
jbaileyseb128, autotools are cuddly.15:40
jbaileyBut AM_MAINTAINER_MODE was wired backwards, and is useless.15:40
seb128how do you ensure that autotools are not ran in such cases?15:40
jbaileyIt should always be in there, disabled by default, and be an option that you pass to configure.15:40
jbaileyIf I weren't totally apathetic, I would write a patch for that.15:41
seb128$ grep am-maintainer configure.ac15:41
seb128$15:41
Ampelbeindebian/rules passes --disable-maintainer-mode to configure already. but that option is not recognized.15:42
jbaileyHah, apparently I wrote an LJ article once ranting about this.15:42
seb128right15:42
seb128the modern autotools version don't seem to understand the option15:42
seb128in fact no15:44
jbaileyseb128, It's still in Hardy.15:44
seb128configure.ac should have a AM_MAINTAINER_MODE and autoconf should be run15:44
jbaileyAC_PREREQ(2.61)15:44
jbaileyAC_INIT(FULL-PACKAGE-NAME, VERSION, BUG-REPORT-ADDRESS)15:44
jbaileyAC_CONFIG_SRCDIR([main.cc])15:44
jbaileyAC_CONFIG_HEADER([config.h])15:44
jbaileyAM_MAINTAINER_MODE15:44
jbaileyBah, never run autoconf on it's own.15:44
seb128aclocal; autoconf15:44
jbailey"autoreconf -f -i -s" is your friend. =)15:44
seb128I hate autoreconf15:44
jbaileyWhy?15:45
seb128it makes a some hundred kbs patch where autoconf does a 25 liners15:45
seb128I don't need all the Makefile.in to be updated for a configure change15:45
jbaileyWell, those other changes are probably bug fixes and the like, though.15:45
jbaileyAnd the size of the patch isn't a big deal once you have AM_MAINTAINER_MODE in there, because then you don't have to worry about spurious rebuilds on top of that.15:46
seb128right, it just makes updates hard to review15:46
seb128AM_MAINTAINER_MODE should be the default mode in any tarball15:48
seb128I just don't see the point of that clever timestamp magic15:48
seb128usually you either want to build using ./configure && make or you want to run autogen.sh and you do that15:48
pittiit's useful for an upstream if you change Makefile.am15:49
pittithen you do make and it DTRT15:49
seb128well, make dist should switch maintainer mode on15:49
pitti+115:50
=== bluesmoke_ is now known as Amaranth
jbaileyseb128, the problem is that then a user has to remember one more thing when trying to figure out what's happening.15:51
jbaileySo they either then edit the Makefile directly and lose their changes, or they edit the Makefile.{am,in} and nothing happens.15:52
jbaileyIf the use wants to touch that *and* has autotools installed, it does the right thing.15:52
seb128it's just annoying to have to patch the configure.ac and have to run autoreconf to be able to use the configure option15:52
jbaileyYou're arguing against yourself there.15:53
jbaileyThat's what maintainer mode kills.15:53
jbaileyRight now you don't have to.  Just edit configure.ac, it will notice that it's newer, regenerate the configure script, rerun it, and go.15:53
seb128I'm not arguing against myself15:54
seb128I want to tell autotools that I know what I'm doing and that they should try to be clever because that's just buggy15:54
jbaileyWhat I think would be useful is leaving that by default, but having an option to say --disable-maintainer-mode which says don't detect the timestamps, I know what I'm doing.15:54
seb128but for that I need to patch configure.ac and run autoreconf which is annoying15:54
seb128right15:55
jbaileyJust edit configure.ac, and it will do the right thing when you're hacking on the code.15:55
jbaileyThe only time you have a problem is when you're patching configure directly.15:55
seb128I'm not hacking on the code, I'm uploading to a buildd which should not have autoconf installed15:55
jbaileySomething that the system isn't built for.15:55
jbaileyRight.  The buildds don't.15:55
=== awe is now known as awe-afk
jbaileyIt's on your dev machine that's a problem.15:55
jbaileyYou have it installed, and you're editting a file you're never supposed to touch.15:55
seb128I'm not15:56
jbaileyIt's like binary patching make on the build system.  You're not supposed to do it.15:56
jbaileyYou're not patching configure?15:56
seb128I'm having a autoreconf patch in my series15:56
jbaileyor Makefile{.in}15:56
seb128I'm not touching it manually, I run autoreconf and put the diff in a patch15:56
seb128the issue is the timestamp after patch apply15:56
jbaileyDoesn't matter.  Something other than autoconf on the current system is touching it.15:56
jbaileyIt's not designed for that.15:56
seb128you have to list the changes in the right order in the patch15:56
seb128right15:57
seb128I'm not arguing that15:57
seb128I just say it's annoying it's not decided to do what I want ;-)15:57
jbaileyEheh15:57
seb128decided -> designed15:57
seb128sometimes I wonder if we should just run autoreconf on the buildds15:58
jbaileyNo!15:58
seb128rather than having autoreconf patches15:58
jbaileyCDBS has an option for that and it's *horrible*15:58
jbaileyI tried to convince duck not to put it in.15:58
jbaileyThen you have no clue what the buildd built.15:58
seb128cdbs is buggy according to Keybul15:58
seb128Keybuk15:58
jbaileySure, it's software.  Of course it's buggy. =)15:58
seb128it tries to run autotools in a smart way rather than using autoreconf simply15:58
jbaileyKeybuk, You're wrong. =)15:58
=== awe-afk is now known as awe
jbaileyautoreconf means that you lose reproducability of builds.15:59
jbaileyUnless you keep all the build-deps around as long as the binary is still around, you can't reproduce the build reliably.15:59
jbaileyDebian/Ubuntu builds aren't hermetic, you have to draw a matrix of all the pieces in order to get a build.15:59
jbaileyThat's a hassle as it is without the actual code for something changing underneath you.16:00
seb128we need build system for human beings ;-)16:00
jbaileyI really really believe that AM_MAINTAINER_MODE([false]) should be the default, and then always done.16:00
seb128right, I would like this one16:00
jbaileyThis is for humans - we're the ones who have to debug the damned things after.16:00
seb128if would mean you just have to add the configure option to the rules16:01
seb128if -> it16:01
jbaileyNo, I would then make that *always* the default in all autoconf builds.16:01
jbaileyBEcause it has no side effects if not chosen.16:01
jbaileyBut then people who need to stop moving parts always have the option.16:01
jbaileyLagging, phone.16:01
seb128right, which is what I was saying no?16:01
Keybukjbailey: you're wrong.16:02
seb128you could just add the configure option to the rules if required16:02
jbaileyKeybuk, Bah!16:02
jbaileyseb128, Then packagers all need to patch the source.  Make it the default.16:02
seb128right16:02
Keybukjbailey: autoreconf is a tool to run autoconf, autoheader, automake, aclocal, libtoolize and autopoint in THE RIGHT ORDER16:02
Keybukand re-run them where it is sometimes necessary16:03
Keybukcdbs does not use it16:03
Keybukinstead cdbs has a hardcoded order that isn't even correct for the common case16:03
jbaileyKeybuk, Right.  And that should never be required at build time where the goal is a reproducable build.16:03
Keybukthis has nothing to do with build reproducability16:03
jbaileyKeybuk, Oh, we're arguing different things.16:03
jbaileyRight, cdbs shouldn't call those individually; it shouldn't call them at all.16:03
Keybukno, you're arguing the wrong thing16:04
Keybukcdbs does call those things today16:04
Keybukand that is the bug16:04
jbaileyBut if it's going to autoreconf is the right thing.16:04
Keybukcorrect16:04
jbaileys/to/to,/16:04
Keybukthough the differing opinions on AM_MAINTAINER_MODE shall stay different ;)16:05
Keybukpersonally I like to just let "make" invoke autoconf/automake as necessary, and have them as build-deps16:06
Keybuksince then I only need to patch Makefile.am in debian/patches16:06
seb128but you don't have predictable builds16:06
Keybukreally?16:06
seb128ie things which used to work break because new autotools version have been uploaded16:06
seb128ie libtool 1.5 to libtool 216:06
Keybukyou ship the exact versions of "make", "gcc", "ld", etc. that you tested with in the package?16:06
jbaileyKeybuk, for that it's a matter of track record. =)16:07
seb128no, but I had a lot higher of issue with autoreconf runs than with normal make16:07
KeybukI'd argue that auto-*'s track record over the past decade has been excellent16:07
pittiseb128 +116:07
Keybukthe problem has been that Debian stalled updating things like automake because of it's previously terrible track record16:07
Keybukwhich meant that packages got stuck using the broken versions16:07
seb128maintainers have not being excellent at writting correct configure.ac though16:07
Keybuknot so much16:08
seb128and old version of autotools have sometime but better at handling those16:08
Keybukthe real problem was that there had to be a flag day where all new versions would be forwardly compatible16:08
seb128but -> be16:08
Keybukbut where the version you were currently on wasn't16:08
Keybukand the trouble is people stuck at the "wasn't" version for a long time16:08
Keybukautoconf 2.50, automake 1.6 and libtool 2.0 are intended to always be forwardly compatible16:08
Keybuksure, there have been bugs, but they have fixed tghose16:08
didrocksseb128: +1 too with the number of issues :)16:09
jbaileyKeybuk, I'd give the success rate in the 4-5 year range more than the last decade.16:09
seb128the issue is that most maintainer don't understand autotools and just copy bits from other softwares16:09
jbaileySo we're getting into the realm where people are getting off of the crappy versions.16:09
Keybukjbailey: I think you'd be surprised if you actually checked when versions were actually released ;)16:09
seb128so you have broken code copied all over the place and nobody knowing how to fix it16:09
jbaileyseb128, The same could be argued for their C code.16:09
jbaileyKeybuk, I'm thinking Gnome in particular when I left Canonical still had a number of packages using Automake 1.416:09
Keybukseb128: nobody affiliated with GNOME can use *that* argument ;)16:10
seb128jbailey: the maintainer are usually keen at fixing their code bugs, not so much at fixing autotools ;-)16:10
Keybuksince GNOME programming entirely consists of copying other people's code16:10
seb128lol16:10
didrockstroll detected :)16:11
jbaileydidrocks, Yeah, but we like Séb.16:11
jbailey;)16:11
seb128I'm troll proof no worry16:11
didrockswell.. hopefully we have Keybuk for fixing all the autotool errors we don't understand (did you have any success with mine? ;)) :p16:12
Amaranthmy autofoo is copied from other places16:12
jbaileydidrocks, #autotools as well. =)16:12
Amaranthalmost 100% of it16:12
AmaranthI kind of know what it means16:13
didrocksjbailey: hum, next time, I will bother people there too ^^16:13
jbaileydidrocks, Sure.  We have a surprising number of people come in there.16:13
jbaileyFor a channel we created a month or so ago and didn't tell anyone about. =)16:13
seb128lol16:13
AmaranthI suspect they were going there before and finding it didn't exist before16:13
didrocksjbailey: :)16:16
didrocksI think I will idling there ^^16:16
Keybukthough it'd be nice to get things like intltool and gtk-doc-tool into autoreconf16:17
Keybukor at least make it locally extensible16:17
Keybukso people don't continue to ship autogen.sh16:17
seb128right16:17
seb128Ampelbein: did you follow the discussion, ie do you know what to change to avoid the build issue?16:28
Ampelbeinseb128: although i have to reread the discussion again to understand it completely, I take it that I have to add AM_MAINTAINER_MODE to configure.ac, rerun autoreconf and I'm done?16:32
jbaileyKeybuk, Do an extensibility mechanism in autoconf and have autoreconf pull that out with a trace.16:32
seb128Ampelbein: right, autoconf should be enough, just update the autotools patch you have16:32
Ampelbeinseb128: ok, will do16:34
Ampelbeinseb128: is it enough to just request a merge of the branch or should i open a new sponsoring bug?16:35
seb128Ampelbein: just update your bzr and ping me about it when it's done16:35
Ampelbeinok16:35
chrisccoulsonhey pitti, i see you've done some hal updates today. would you mind having a look at a patch i wrote to fix a hald crash? (it's in a branch proposed for merging in to ubuntu-core-dev)16:53
pittichrisccoulson: sure; I'd commit it upstream, though16:56
pittichrisccoulson: I wonder why I didn't get a merge request mail16:56
pittichrisccoulson: perhaps you can mail me the URL to the MP, and I'll get to it ASAP?16:57
chrisccoulsoni sent the patch upstream but the bug report it's attached to is fairly quiet16:57
chrisccoulsoni don't think i added you as a reviewer for the merge request. i'll mail you the URL to that shortly anyway. i have to dash now to go home16:58
pittichrisccoulson: yeah, hal patches are better on the upstream ML, nobody looks at bz, I'm afraid16:59
asacpitti: so i attached a patch for the almost dead modem fdi ;) ... bug 37497017:02
ubottuLaunchpad bug 374970 in hal-info "update/fix some modem fdi rules" [Undecided,Confirmed] https://launchpad.net/bugs/37497017:02
asachope i didnt sumit that before (had it in my inbox for a week or so)17:02
asacsubmit17:02
pittiasac: heh, thanks17:04
=== dpm is now known as dpm-afk
Ampelbeinseb128: branch https://code.edge.launchpad.net/~amoog/gnome-utils/devel updated17:05
seb128ok17:06
seb128Ampelbein: you forgot to bzr add the new change?17:27
Ampelbeinseb128: arghs. yes.17:30
Ampelbeinseb128: change pushed.17:30
seb128Ampelbein: did you check that's it's working?17:35
seb128Ampelbein: I mean the change, the bzr is updated now17:35
Ampelbeinseb128: how do i check this? i tried touching Makefile.am in clean virtualboxenvironment which should provoke invocation of the autotools, right? and it did not autoreconf on building.17:41
seb128you need to touch it after the autotools change17:41
seb128try adding a patch after that one which edit the Makefile.am or touch it in the rules17:41
Ampelbeincould it be that the latest cdbs in ubuntu broke it? i get http://paste.ubuntu.com/169803/ using 0.4.56ubuntu2, with ubuntu1 it works as expected18:01
seb128weird18:02
pittilatest cdbs just fixed a corner case in cdbs-edit-patch18:02
Ampelbeinpitti: give me a minute, i will provide terminal-logs of new version and ubuntu1.18:04
Ampelbeinpitti: 0.4.56ubuntu1: http://paste.ubuntu.com/169805/ , 0.4.56ubuntu2: http://paste.ubuntu.com/169808/18:10
Ampelbeinpitti: do you need more info? if so, just tell me and i happily provide it.18:12
pittiAmpelbein: ah, that would be my change, indeed18:14
Ampelbeinpitti: is it anything wrong with my pathnames or anything else where I did something unusual?18:16
pittiAmpelbein: no, I just screwed up; I'm at it18:17
pittiAmpelbein: uploaded; sorry!18:22
Ampelbeinpitti: i guess there is no need to be sorry. thanks for fixing it so fast.18:23
didrocksI'm screwing vte. I can't find why it is choosing site-packages and doko isn't here!18:23
didrocksI will still fight a little :)18:23
pittididrocks: you call setup.py install with --install-layout=deb ?18:28
pittithat shuold fix it18:29
didrockspitti: there is no setup.py call18:29
pittididrocks: that would be it then18:29
pittididrocks: use dh_install to install debian/tmp/.... site-packages to dist-packages18:30
didrockspitti: yes, that's what I read in doko's post18:30
pittianyway, /me waves goodbye, Taekwondo time18:30
pittisee you tomorrow!18:30
didrockspitti: see you tomorrow ;)18:30
chrisccoulsonnice spam from ubuntu-devel list today :/18:41
asaclool: http://launchpadlibrarian.net/26594087/buildlog_ubuntu-karmic-amd64.gtk%2B2.0_2.16.1-0ubuntu4~asac~k_FAILEDTOBUILD.txt.gz ...18:57
asaccp: cannot stat `./debian/install/directfb/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so': No such file or directory18:57
asacdh_install: cp returned exit code 118:57
asaclool: do you see anything in the build log that would prevent that lib from ending up there?18:58
asac(that worked on all bug amd64)18:58
asacbut18:59
rickspencer3-afkawe: hi19:05
=== rickspencer3-afk is now known as rickspencer3
rickspencer3oops, I've had the wrong nick for over two hours!19:06
awerickspencer3: hey19:11
awe;)19:11
rickspencer3awe: I saw your mail19:11
awecool, i just read your reply19:11
rickspencer3you should keep in mind that I am a complete hard ass19:11
rickspencer3;)19:11
rickspencer3ask any one here19:12
awethat's nice to hear!19:12
rickspencer3:)19:12
aweI'm having fun with merges today.19:12
rickspencer3awe: seriously, it sounds like things are going well, and you can't do better than to work with asac, he's made of awesome19:12
rickspencer3hehe19:13
awecool.  we know each other well, so I'm glad we finally get a chance to work together19:13
rickspencer3also, pitti is the tech lead for the desktop team, so you should feel free to ask him any questions as well19:13
awesounds good.  as i mentioned before, we've played guitar together at a few of our UDS/AllHands jams, so I know pitti well too...19:14
awelooking forward to working with everyone!19:14
loolasac: checking pixbuf loaders to build...19:59
loolchecking if gio can sniff png... no19:59
loolThis might be the issue19:59
=== rickspencer3 is now known as rickspencer3-afk
asaclool: hmm thanks ... but it builds the -png builder from what i saw.20:18
asaclool: odd. was temporarily. i made a new upload and now it worked ;)20:18
asacgreat20:18
loolasac: Not too reassuring   :-/20:20
=== awe is now known as awe-afk
Ampelbeinseb128: welcome back. i updated the gnome-utils branch, lp:~amoog/gnome-utils/devel21:12
seb128Ampelbein: hey, did you manage to test the issue?21:12
Ampelbeinseb128: yeah. but i had to run autoreconf after the AM_MAINTAINER_MODE change, it did not work with just running autoconf.21:13
seb128oh ok21:13
Ampelbeinand cdbs has been updated, ubuntu3 works as expected now.21:13
seb128I've noticed the update21:14
jbaileyAmaranth, AM_MAINTAINER_MODE requires the whole set to be run, yes.21:24
jbaileyIt's quite invasive.21:24
jbaileyBut after that, the right things should happen.21:24
Nafallojbailey: wow. you're alive... :-)21:27
Nafallojbailey: hi21:27
jbaileyNafallo, Still moving.  There were some iffy moments, but.. =)21:28
jbaileyMeeting in 90 seconds, back in 30 minutes.21:28
Nafalloheha21:28
Nafalloehrm21:28
Nafallohehe21:28
loolasac: BTW I uploaded a gtk+2.0 fixing the missing --build and --host; do you plan an ia32libs uplaod for A1?21:36
asaclool: yes. bug 369498 fix will land soon21:36
ubottuLaunchpad bug 369498 in gtk+2.0 "Errors when running acroread in 9.04 (fully updated)" [Medium,In progress] https://launchpad.net/bugs/36949821:37
asacdid the patches today. just want to verify gio too21:37
loolCool, thanks21:37
loolasac: You might have to revert the jaunty triplet changes21:37
seb128_Ampelbein: do you still have work on your list or are you looking for other updates?22:19
Ampelbeinseb128_: i could do other updates now. otherwise i would just look on MoM to find me some work ;-)22:20
seb128_Ampelbein: eog is to merge on debian and update to 2.27.1 if you want22:21
Ampelbeinseb128_: ok, doing that one22:22
=== rickspencer3-afk is now known as rickspencer3

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