/srv/irclogs.ubuntu.com/2012/10/16/#ubuntu-devel.txt

=== jono is now known as Guest36495
=== dendro-afk is now known as dendrobates
pittistgraber: no worries04:39
pittigood morning04:39
=== tkamppeter_ is now known as tkamppeter
dholbachgood morning06:53
=== smb` is now known as smb
=== henrix_ is now known as henrix
=== henrix is now known as henrix_
=== henrix_ is now known as henrix
Laneyhm, the e.u.c graph hasn't updated in 5 days08:55
cjwatsonLaney: it has ... *drumroll* ... an error08:58
cjwatsonquis custodiet ipsos custodes?08:58
LaneyHost errors.errors.ubuntu.com not found: 3(NXDOMAIN) :(08:59
xnoxLaney: I heard that ev was calculating / updating the graph in a "semi" automatic way, e.g. by computing it somewhere and pushing the result.09:02
xnoxev: are cron jobs fixed?! =)09:02
brendanddoes anyone know difference between 'NO_PROXY' and 'no_proxy'?09:08
cjwatsonThe latter is an environment variable I've heard of; the former isn't09:10
margaIs this an appropriate channel to ask upstart questions?  I need to know the difference of having an "exec" line alone in the file and having it inside a "script" block (no pre-start or post-stop, just script)09:11
brendanddid i really need to specify 'and no smart answers' :)09:11
cjwatsonbrendand: Um, I thought that was a perfectly straightforward answer.09:11
cjwatsonmarga: The latter will involve an unnecessary /bin/sh process that then execve-s (or similar) the thing you actually wanted to run, rather than having upstart exec it directly09:12
cjwatsonbrendand: IOW, without further context, I would have assumed that NO_PROXY was an error, perhaps influenced by the way the *_proxy environment variables are curious anomalies in being lower-case.09:13
margacjwatson, ok, but I need to pass some env variables to it.09:13
cjwatson(I don't know the history behind that.)09:13
margaI'm going to go paste something.09:13
cjwatsonmarga: Why not use 'env'?09:13
cjwatsonThe Upstart stanza, I mean, not the command09:14
margacjwatson, just let me paste this and you tell me how to make it better.09:14
cjwatsonSure09:14
margahttp://paste.ubuntu.com/1282738/09:15
margaThe thing is, if I add my stanza like that, upstart gets very angry and refuses to start or stop anything.09:15
cjwatsonAh, you need to compute the environment variables; that's trickier09:15
cjwatsonOK, I'll work something out for you, few minutes09:15
cjwatsonYour basic problem is that you've confused fork tracking09:15
margaOk...09:16
cjwatsonmarga: I don't think that's the whole file; can you show me the whole file, please?09:16
brendandcjwatson, it seems that all proxy env variables have both an upper and lower-case form (https://bugs.kde.org/show_bug.cgi?id=54898) ?? how confusing09:16
ubottuKDE bug 54898 in kcmproxy "implement NO_PROXY in preset environment variables proxy configuration" [Normal,Resolved: fixed]09:16
cjwatsonbrendand: I have never heard of that.09:16
margaI was reading the cookbook, which I found very interesting, but I still can't figure out why upstart stops working09:16
cjwatsonPerhaps it's something KDE made up.09:16
cjwatsonNote that the w3.org reference quoted there has no mention of upper-case forms.09:17
brendandcjwatson, i'm not on kubuntu, fyi09:17
cjwatsonBut of course environment variables are all just conventions of varying strengths.09:17
cjwatsonbrendand: Use the lower-case forms and ignore these alleged upper-case forms.09:17
brendandcjwatson, i wonder where the upper-case form is getting set though?09:17
cjwatsonbrendand: Nowhere, quite possibly :-)09:18
margacjwatson, ok, 1 min.  I think the rest is just the original /etc/init/gssd.conf, although I'm not totally sure09:18
brendandcjwatson, something has set it, without my knowledge09:18
margahttp://paste.ubuntu.com/1282741/09:19
cjwatsonbrendand: Could be anywhere09:19
brendandcjwatson, exactly09:19
cjwatsonBut I doubt it's terribly interesting09:19
cjwatsonAnything can set whatever environment variables it likes, with or without any meaning09:20
cjwatsonmarga: Yeah, so 'expect fork' means that Upstart tracks the first process in the main script09:20
cjwatsonRunning dpkg-query and dpkg --compare-versions throws that off09:20
margaok.09:20
margaIs there a way to fix it?09:21
cjwatsonCan you not do this with a dependency instead, and lose the dpkg* calls?09:21
margaNo, this file is distributed to the clients via puppet.09:22
cjwatsonOtherwise, the only way I can think of to do this is to move the dpkg* calls to the pre-start script and have it write out a temporary file which is then sourced by the main script09:22
cjwatsonAlthough the temporary file would have to be in a fixed location09:22
margaBut wouldn't sourcing have the same effect?09:22
cjwatsonNo09:23
cjwatsonSourcing doesn't fork a subprocess09:23
margaugh, this is ugly09:26
cjwatsonmarga: Regard it as the cost for getting rid of the ugliness of pid files :-)09:29
margaUhm, it's saying that the pre-start process terminated with status 1.  I already have initctl logpriority in 1.  Is there anyway I could find out WHY it's finishing with status 1?09:36
margalogpriority in debug, I meant09:37
=== hrww is now known as hrw
cjwatsonmarga: set -x at the start, and look at the logs?09:49
cjwatson(the start of the pre-start script)09:49
margaok, that would have been better.  I used logger on each line.09:50
margaSo, now it works when the flags are empty, but it hangs when there are flags.09:57
margaThis makes me miserable...09:57
margaI'll paste how it looks now.09:57
margahttp://paste.ubuntu.com/1282778/09:59
margaWhat did I do wrong this time?09:59
dholbach@pilot in09:59
=== udevbot_ changed the topic of #ubuntu-devel to: Quantal Quetzal development | Beta 2 released! | Archive: Frozen | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> precise | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: dholbach
cjwatsonmarga: Use '.' not 'source'09:59
cjwatson'source' is a bashism09:59
cjwatsonmarga: 'export EXTRA_FLAGS' is useless10:00
cjwatsonOh, actually you initialise that, never mind.  You could drop the export and make it just env though10:00
margaok.  That was in the cookbook.10:00
cjwatsonI think just 'env EXTRA_FLAGS='10:01
margaWhat's the difference between env and export?10:01
cjwatson'man 5 init' documents it10:01
margaok, thanks.10:01
cjwatsonSo, I don't totally understand why it hangs, so I'm not sure that'll fix it10:02
cjwatsonMaybe jodh can take over if that isn't enough; I have two bugs I need to be fixing urgently10:03
margaOk, thanks a lot for the help!10:03
margaGood luck with your bugs10:03
jodhmarga: do you see anything in /var/log/upstart/<job>.log? when you say it hangs, is a rpc.gssd process actually running and if so with which flags?10:04
margajodh, I just rebooted (once it hangs, nothing I do will make it right again, except a reboot).  Just a moment10:05
jodhmarga: does it hang on boot or when you attempt to start the job manually?10:05
margaIt hangs when I do something that upstart doesn't like...10:07
margaI mean, if I modify the file in some ways, it hangs on start/stop10:07
margaBut not on boot.10:07
jodhmarga: when you attempt to start it manually, are you sure there isn't already a rpc.gssd process already running?10:08
margaYes10:08
margaI found the bug10:08
margaIt was a shell escaping bug10:08
jodhmarga: that should have been logged in /var/log/upstart/<job>.log10:09
margaIt was in the upstart log that you mentioned.  I didn't know about it till now10:09
margaI was looking at the syslog which wasn't helpful at all.10:09
margaNow I know better.10:09
margaThanks.10:09
jodhmarga: also, if you'd run 'init-checkconf job.conf', that would have given you an error.10:09
margaNo, it was a more convoluted syntax error10:10
cjwatsonOh?  I didn't spot that ...10:11
margaI am echoing into a file and then sourcing it, and I'm missing some escaping quotes10:11
margacjwatson, no, because it was not in the original paste. My bad.  I don't have a -e capable rpc.gssd, so to test it, I was using -t 60010:11
cjwatsonI didn't see anything that clearly required quotation10:11
cjwatsonAh10:11
margaAnd I didn't escape the space10:11
cjwatsonYeah, so echo "EXTRA_FLAGS=\"${EXTRA_FLAGS}\"" then10:12
margaRight.10:12
cjwatson(or echo "EXTRA_FLAGS='${EXTRA_FLAGS}'")10:12
margaThanks a lot cjwatson and jodh !10:13
dholbachRiddell, are you planning to do another kubuntu-docs upload before release?10:28
dholbachI saw there's https://code.launchpad.net/~bkerensa/ubuntu/quantal/kubuntu-docs/fix-for-1049278/+merge/125965 and https://code.launchpad.net/~m-alaa8/ubuntu/quantal/kubuntu-docs/fix-for-1066132/+merge/129598 in the queue10:28
dholbachRiddell, ^ I'll ping Darkwing about it too10:30
dholbachdpm, pitti: any opinions about https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/997248?10:33
ubottuLaunchpad bug 997248 in langpack-locales (Ubuntu) "Inconsistency in decimal point for es_MX and es_NI locale" [Undecided,In progress]10:33
pittidholbach: I always demand forwarding them upstream (http://sourceware.org/bugzilla/enter_bug.cgi?product=glibc, "localedata" component), with a reference to an official documents which proves that the proposed change is correct10:35
pittiI've seen too many wars about other people then chiming in and saying "but that's all wrong!!!"10:35
dholbachok10:35
dholbachwill do10:35
dholbachthanks pitti10:35
pittithanks!10:35
Laney-devel discussion> seems like a tag defer-next-release which hides from the overview, together with a script that untags all such bugs would work?10:37
Laneyfor bugs, not sure about MPs10:37
dholbachyes, sounds good10:38
dholbachit'd be nice if we could do the same for MPs easily10:38
Laneya hack would be to make an account whose purpose is to cause a MP to be hidden, then request a review from it10:39
dholbachwhat would the hack do? mark the MP as 'WIP' (or something) and then repropose it?10:41
Laneydoes WIP hide?10:41
dholbachyes10:41
dholbachnot sure though if you need special permissions for that10:42
dholbachseb128, does https://code.launchpad.net/~carifio/seahorse/seahorse-remove-broken-help-buttons/+merge/129303 look OK to you? or is it something that should be forwarded upstream?10:42
Laneyat least I can do it10:42
dholbachcool10:42
Laneyso the unhide script has credentials for this account, sees which 'reviews' it has to do, flips the status back to Needs review and abstains10:42
Laneyassuming this is possible via API10:43
dholbachI guess it should10:43
* Laney can probably implement this10:44
xnoxLaney: dholbach: I don't like "work in progress" because many "work in progress" are actually sponsor asking sponsoree to do something, which has not been done yet. Maybe we should reject those, but I have been setting to "work in progress".10:45
Laneyit's WIP+review from role account10:45
dholbachxnox, WIP is something everyone can do, but not 'reject' :-/10:45
xnoxLaney: that would be nice =)10:45
Laneycall it ~defer-sponsorship10:46
xnox"needs reivew" -> "WIP+review" with a comment on the merge proposal would be nice indeed =))))10:46
Laneyhaha10:47
Laneydholbach: was "HOLY PATATAS BRAVAS" you?10:47
dholbachyes :)10:47
seb128dholbach, I will have a look to the seahorse merge request, I looked a bit at it before10:48
dholbachseb128, merci beaucoup mon ami10:49
seb128dholbach, de rien ;-)10:49
=== MacSlow is now known as MacSlow|lunch
amb__I am trying to port a debian experimental package (xen 4.2.0) to Precise. When I debuild I get /usr/bin/ld.bfd.real: unrecognized option '-Wl,-Bsymbolic-functions'. AIUI if -B is passed to ld, it should be without the -Wl. The text 'symbolic-functions' does not appears anywhere within the source. But config.log & config.status (built) have 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' - it's coming from inside the ship (um, inside Pr11:22
amb__ecise). That surely must be wrong. Any ideas?11:22
=== amb__ is now known as alexbligh1
alexbligh1$ dpkg-buildflags | fgrep LDFLAGS11:30
alexbligh1LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro11:30
alexbligh1manpage suggests the -Wl etc. should not be there.11:30
cjwatsonMan page doesn't document the Ubuntu vendor defaults11:31
alexbligh1"Options passed to the compiler when linking executables or shared objects (if the linker is called directly, then -Wl and , have to be stripped from these options). Default value: empty."11:31
cjwatsonSure, man page bug11:31
cjwatsonThe actual program behaviour is correct for Ubuntu11:31
cjwatsonAlthough note that further down there's a bit about relro which says it's enabled by default11:32
alexbligh1Ah, does it mean '-Wl' has to be stripped by the setter? or by the consumer?11:32
cjwatsonYou should be linking with gcc, not with ld11:32
alexbligh1AFAICT it's running a bog standard autoconf11:33
cjwatsonAs the man page says, if you want to link with ld, you need to strip off -Wl,11:33
alexbligh1Ah, I read that as 'the setter needs to strip it'.11:33
cjwatsonNo, that's wrong11:33
cjwatsonautoconf doesn't control how programs are linked11:33
cjwatsonautomake does, but bog-standard automake will link with gcc11:33
alexbligh1oh sorry, auto*11:34
cjwatsonCan't be bog-standard11:34
cjwatsonI expect there are some custom rules somewhere11:34
alexbligh1seems to be using $(LD) ...11:35
cjwatsonThe Ubuntu package in precise had a patch to adjust LDFLAGS for use by ld11:35
alexbligh1The Xen package? How do you remember all this stuff? :-)11:35
cjwatsonI looked up the changelog11:36
cjwatsonIt was dropped in quantal because the quantal packaging toolchain no longer exports LDFLAGS to the environment by default; you have to ask for it using dpkg-buildflags11:36
alexbligh1ha ha11:36
cjwatsonHowever this means that the quantal package has the (far from uncommon) bug of not using the default build flags11:36
cjwatsonIf upstream can be persuaded to use $(CC) rather than $(LD) to link, that would be best, but they may have reasons not to11:36
cjwatsonFailing that, restore the patch to hack LDFLAGS11:37
alexbligh1I'm trying to build on Precise anyway, and there is no Xen4.2.0 anywhere in Ubuntuland as far as I can tell (even in PPA)11:37
alexbligh1Hence stealing the Debian one.11:37
cjwatsonSure, but there's no reason you couldn't borrow most of the packaging, or at least that patch from it11:37
alexbligh1No indeed, that is exactly what I shall do.11:37
cjwatsonxen ought to be modified to use dpkg-buildflags, at which point it'll start noticing this problem again, even in Debian11:38
alexbligh1I may not steal the ubuntu packaging, as the xen 4.1 ubuntu packaging was 'interesting' (like the dev libraries were incomplete)11:38
cjwatson(Debian's packaging toolchain never exported LDFLAGS to the environment by default; that was an Ubuntuism which we dropped in quantal in the cause of getting closer to Debian)11:38
alexbligh1 dpkg-buildpackage -rfakeroot -D -us -uc -b11:39
alexbligh1dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security11:39
alexbligh1dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): -D_FORTIFY_SOURCE=211:39
alexbligh1dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security11:39
alexbligh1dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O211:39
alexbligh1dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): -Wl,-Bsymbolic-functions -Wl,-z,relro11:39
alexbligh1doesn't that suggest it is?11:39
cjwatsonThat's precise's behaviour, yes11:39
cjwatsonNotice that I said quantal11:39
alexbligh1ah it's an implict call to buildflags.11:40
=== Quintasan_ is now known as Quintasan
alexbligh1cjwatson, thx11:40
cjwatsonno problem11:41
dholbachcan the people from lubuntu,mythbuntu,xubuntu,ubuntustudio please have a look at https://code.launchpad.net/~gunnarhj/ubuntu/quantal/lightdm-gtk-greeter/lang-chooser-on-by-default/+merge/129758 and see if that's what they want?12:00
smbcjwatson, I am somewhat torn between trying to ask you one evening in Copenhagen what should be done exactly with the buildflags and the Xen package or after it when there is a bit time (and not release week). Though both has somewhat illusional chances. I try to keep it in mind/on a list for the next time I touch it...12:10
mr_pouitdholbach: not an issue for xubuntu/lubuntu because we use our own config file.12:11
=== _salem is now known as salem_
* smartboyhw thinks so too with Ubuntu Studio12:11
dholbachmr_pouit, do you by chance know how other flavours deal with this?12:11
dholbachaha12:11
dholbachmaybe you could reply on the merge proposal?12:12
dholbachjust so it's easier to track down for us12:12
dholbachand maybe we should ask some of the other flavours to review this too12:12
mr_pouitin the bug report, Gunnar already stated this (https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/803858/comments/27) too12:13
ubottuLaunchpad bug 803858 in lightdm-gtk-greeter (Ubuntu) "No language chooser on login screen in LightDM" [Undecided,In progress]12:13
dholbachok cool12:14
ochosidholbach: ping12:14
dholbachochosi, pong12:15
ochosidholbach: astraljava passed a question about this merge-request along: https://code.launchpad.net/~gunnarhj/ubuntu/quantal/lightdm-gtk-greeter/lang-chooser-on-by-default/+merge/12975812:15
dholbachmr_pouit, smartboyhw and I were just talking about it12:16
smartboyhwdholbach, some comments in our dev channel says it is ok12:16
ochosisorry, i was informed about that just now :p12:16
dholbachochosi, so it seems like xubuntu/lubuntu because use their own config file12:16
dholbachso it might well be that the change is not necessary12:16
dholbach(and it might be similar for Ubuntu Studio)12:17
smartboyhwdholbach, I wonder: Actually what will the lightdm-gtk-greeter look like after the merge?12:17
ochosidholbach: just out of interest, is this the language-selector here: http://www.zimagez.com/zimage/screenshot-10162012-020905pm.php12:17
smartboyhwdholbach, should I go and ask the Kubuntu guys?12:17
mr_pouitdholbach: it's useful for people who use lightdm-gtk-greeter with ubuntu12:17
dholbachsmartboyhw, they use lightdm-kde-greeter12:18
smartboyhwdholbach, er....Wait12:18
dholbachmr_pouit, right, yes12:18
dholbachok, I guess I will just ping mterry about it once he turns up later on12:19
smartboyhwdholbach, hmm....Since I do saw the select language menus in 12.10 Ubuntu Studio builds.....maybe that wasn't needed for Ubuntu Studio..It is just derived from Ubuntu Studio12:19
cjwatsonsmb: In general, if not using sufficiently smart helper tools (dh(1) from debhelper compat level >= 9), packages should fetch at least the default values of CPPFLAGS, CFLAGS, and LDFLAGS from dpkg-buildflags in debian/rules and pass those to the upstream build system in whatever way is appropriate12:20
cjwatsonThere are various options and exactly which to use depends on the build system12:20
=== MacSlow|lunch is now known as MacSlow
smbcjwatson, Yes, I guess I would have the do the latter as the Debian Xen package was (iirc) not using the shorter dh variant but a more complex rules file. I was wondering when it did not need the hack anymore but I think back then when I asked around it was not persistent/widely enough.12:25
cjwatsonThe LDFLAGS hack ceased to be required when we changed dpkg-buildpackage in early quantal to no longer export flags by default, but the flip side is that you've probably lost hardening flags.12:25
cjwatsonSo it's moderately important to fix that for R.12:26
=== cpg is now known as cpg|away
smbcjwatson, Sure I saw that in the scrollback. It is now on my my list at least (and hopefully I do not forget to look at it when I touch it next). Probably also to go backwards into Q if opportunity permits.12:27
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== doko__ is now known as doko
dokocjwatson, which hardening flags do we loose exactly? these are still defaults in gcc13:03
cjwatsonOh, maybe13:04
cjwatsonI looked into this a while back but I forget the results13:04
cjwatsonNot hardening then, but -Wl,-Bsymbolic-functions13:05
dokoright, that would be the one13:05
dokojamespage, are you ok with building gwt, mondrian using openjdk-6 to work-around the build failures?13:22
jamespagedoko, +113:22
cjwatsondoko: Would that help with eigenbase-resgen too?13:23
dokoI'll check13:23
cjwatsonBut yeah, we can't remove that stack, too many build-deps13:24
=== yofel_ is now known as yofel
gogo_Hello, in Ubuntu 12.10, I cannot change window animation duration from CCSM. Any altered value have no effect on duration and default values are still used. Is this a bug or intended behavior?13:59
stokachuWould someone be able take a look at https://launchpad.net/ubuntu/precise/+queue?queue_state=1&queue_text=open-iscsi? its been in the unapproved queue since 10/314:16
stokachudholbach: so once the package is in the upload queue ubuntu-sponsors is not needed and it relies on ubuntu-sru at that point?14:29
dholbachstokachu, yes14:29
stokachudholbach: ok cool just checking so I dont incorrectly subscribe sponsors again14:29
dholbachit's all good :)14:29
dholbachthanks for your work on this14:29
stokachusure thing :D14:30
xnoxstokachu: most of SRU folks are busy doing the release =)14:31
stokachuxnox: ah14:32
stokachuxnox: http://people.canonical.com/~ubuntu-archive/pending-sru.html, does the package show up once the upload has been approved?14:33
xnoxstokachu: yes. these are packages that were accepted into $release-proposed and now are tracked how long they are in the -proposed and if they are "aged", "verified" and did not regress.14:35
dokoLaney, your handbrake upload ftbfs on amd6414:36
Laneyyes I know14:36
doko=)14:36
LaneyI pinged jbicha, it's his backport really14:36
Laneythe way we upload those makes it appear to be the backporter on the hook14:36
Laneydoko: is there a way to do that scanning locally with sbuild?14:38
dokoLaney, don't know. maybe ask lamont, I think he did add the code to the buildds in ia64 times ...14:39
jbichaimplicit pointer conversion build failures are so annoying14:40
cjwatsonIt's in lp:launchpad-buildd14:42
xnoxdoko: yeah I totally want to know how to run that check locally, as it's not integrated into something useful which get's installed by mk-sbuild (same as pkgstripper, binary manglers & dbgsym generators).14:43
=== dendrobates is now known as dendro-afk
cjwatsonlpbuildd/check_implicit_pointer_functions.py <foo.build14:43
cjwatsonor sbuild | lpbuildd/check_implicit_pointer_functions.py --inline14:43
* xnox takes a note to add a further wrapper to my sbuild....14:44
stokachuxnox: is there anyone in particular i could bug about this package being in the unapproved queue?14:47
stokachuwithout losing some fingers14:47
cjwatsonstokachu: I'll take a look.14:48
xnoxstokachu: looking at https://launchpad.net/~ubuntu-sru/+members the usual suspects are steve, colin, adam, clint... =) for that sort of package.14:49
cjwatsonstokachu: accepted14:50
stokachucjwatson: awesome thanks man14:51
hallynsafe to assume we have no sparcs in build farm?15:01
cjwatsonWe have two sparc builders.15:01
cjwatsonartigas and sejong.  https://launchpad.net/builders15:01
hallyncjwatson: so openbios-sparc, which must be built on sparc, *could* be pulled into ubuntu?15:02
cjwatsonNo, that's a different problem15:02
hallyni'm looking into how closely we can mirror debian's qemu packaging layout for r15:02
cjwatsonWe have no way to do architecture: all builds on anything other than i38615:02
hallynok so i should drop sparc15:03
hallyncjwatson: thanks15:04
cjwatsonbug 18349515:05
ubottuLaunchpad bug 183495 in openbios-sparc (Ubuntu Hardy) "[FTBFS] openbios-sparc (1.0~alpha2+20070816-1) fails to build in hardy" [High,Confirmed] https://launchpad.net/bugs/18349515:05
cjwatsonAlthough I'm sure there's a bug on Launchpad somewhere, where it more properly belongs15:05
hallyncjwatson: but as it's been around since 2008, low prio i assume15:06
cjwatsonhallyn: Bug 21742715:08
ubottuLaunchpad bug 217427 in Launchpad itself "Please support arbitrary arch/buildd affinity for arch:all builds" [High,Triaged] https://launchpad.net/bugs/21742715:08
xnoxcjwatson: but there is no way to currently express that in .dsc e.g. build-arch field15:09
hallyncjwatson: i'm a little surprised a powerpc - on - x86 crosscompiler isn't packaged...15:10
xnoxcjwatson: hallyn: (ugly-hack) arch: ppc, Multi-Arch:15:10
xnoxcjwatson: hallyn: (ugly-hack) Arch: ppc, Multi-Arch: allowed15:10
cjwatsonxnox: See that bug report.15:10
cjwatsonxnox: I'd rather you didn't work around it that way.15:10
cjwatsonIf nothing else, that's no use for cases that involve build-deps.15:10
cjwatsonhallyn: *shrug*15:11
hallyncjwatson: i'm wondering whether, if it did, that sufficed15:11
cjwatsonhallyn: Don't know.  Possibly15:12
xnoxhallyn: well all rdeps would need to be changed to: package [sparc]15:12
xnoxhallyn: well all rdeps would need to be changed to: package [ppc]15:12
cjwatsonxnox: No, they wouldn't.15:12
cjwatsonCross-compile binary, put it in an architecture: all binary just as it is now.15:13
cjwatsonAlso, you can't specify a particular architecture in Depends.15:13
hallyncjwatson: any sense having a uds session on this?15:18
cjwatsonhallyn: No, we'd just all sit around and agree that either the Launchpad bug needs to be fixed or we need a cross-compiler15:19
hallynok :)15:20
hallynthere used to be a simple howto for locally creating cross-compiler, but might be a bear to package15:20
cjwatsonhrw might know15:21
hrwhi15:21
hallynhrw: wondering about feasability of creating a set of cross-compiler packages15:22
hallyn(specifically gcc for powerpc and sparc)15:22
hrwhallyn: doable with arm cross compiler packages as base15:23
hrwhallyn: but openbios-sparc on debian is arch:all - can't be same in ubuntu?15:24
hrwI see - 'This package must be built on a SPARC machine'15:25
hallynhrw: right (same with openbios-ppc, and presumably openhackware)15:26
hallynso gcc-arm-linux-gnueabi as an example?15:27
hrwhallyn: going for cross compilation with them means maintaining 3 packages per arch (6 for biarchs).15:27
hrwhallyn: binutils-armel-cross, armel-cross-toolchain-base, gcc-4.7-armel-cross15:27
hrwhallyn: first gives binutils, second glibc and libgcc, last one gives compiler15:28
cjwatsonMight be less effort to fix the LP bug ...15:28
hrwcjwatson: and then we will pray that no one wants openbios-hppa :D15:29
cjwatsonOK, that's true, fixing the LP bug wouldn't help with openbios-sparc since it's no longer an architecture in modern series15:29
cjwatsonSo a cross-compiler would be needed for that either way15:29
hrwor package removal but that will hurt all users of qemu-sparc15:30
cjwatsonThe package was actually removed ages ago15:33
cjwatsonBut it'd be nice to be able to reintroduce it15:33
hrwquestion is: who wants to maintain those cross compilers?15:34
cjwatsonhallyn's the one pushing for this currently :)15:35
hrwhallyn: grab binutils-armel-cross source, sed -i s/armel/sparc/ debian/changelog then debian/rules control and build. then same with armel-cross-toolchain-base and gcc-4.7-armel-cross. when all done, grab gcc-defaults-armel-cross and do changelog and rules trick then rebuild.15:37
dholbach@pilot out15:37
=== udevbot_ changed the topic of #ubuntu-devel to: Quantal Quetzal development | Beta 2 released! | Archive: Frozen | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> precise | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
hrwhallyn: if you are lucky then small amount of work needed.15:37
hallynhrw: thanks, will give it a shot15:40
hrwhallyn: wookey did aarch64 cross compiler recently from those packages so it is doable ;)15:42
hrwhallyn: in case of problems - ask me15:42
hallynwill do thx15:43
lamontjbicha: like cjwatson said - it's just a logfile scan that looks for implicits that were conversion truncation, or so15:46
=== adam_g_ is now known as adam_g
=== Ursinha-afk is now known as Ursinha
=== deryck is now known as deryck[lunch]
=== glebihan_ is now known as glebihan
=== deryck[lunch] is now known as deryck
=== rsalveti_ is now known as rsalveti
=== Ursinha_ is now known as Ursinha
=== cpg|away is now known as cpg
cjwatsonjtaylor: abiword/armel failed to build19:53
jtaylorOo19:53
jtaylorcan't be the abiword change19:53
=== henrix is now known as henrix_
cjwatsonjtaylor: No, but now we're in a bit of a bind for release19:54
cjwatsonWe *were* at the point where there were zero out-of-date binaries in the archive19:54
cjwatsonabiword has broken that19:54
cjwatsonThe last build was only 2012-10-08 ...19:55
=== cpg is now known as cpg|away
jtayloryes not long ago19:55
cjwatsonLooks like somebody has retried it already?19:55
jtaylorI didn't expect toolchain breaking19:55
cjwatsonHe says as the build log goes away19:55
cjwatsonjtaylor: I should have noticed it was in images and required your sync to go through -proposed19:55
jtaylorbut isn't this a larger issue jut discovered by abiword19:58
cjwatsonMaybe, but such fine principles are for earlier in the cycle19:59
cjwatsonNow we need to not break stuff or expose breakage19:59
micahgcjwatson: if it's just armel, it shouldn't impact any images at least20:00
cjwatsonNo, but if fixing it requires a source upload, that'll hit Xubuntu and Lubuntu20:00
cjwatsonI am *not* going to leave out-of-dates just after we spent weeks getting them clean20:00
cjwatsonI mean *literally* just after, as in the next publisher cycle20:01
micahgtrue20:04
=== Ursinha is now known as Ursinha-afk
=== cpg|away is now known as cpg
mwhudsonprobably not the place to ask this question, but:20:36
mwhudsonwhy would apt-get remove $package (unattended-upgrades in this case) want to install over 100 new packages?20:37
slangasekpossiblybecause something else on the system depends on $package and apt looks for a way to satisfy your request that results in the smallest number of additional packages having to be removed20:38
mwhudsonah right20:39
mwhudsoni think i don't want to remove it in fact20:39
mwhudsonjust disable it20:39
ScottKcjwatson: Is you comment on Bug #674627 at all indicative that it's still an issue or you just doing cleanup?21:23
ubottuLaunchpad bug 674627 in sip4-qt3 (Ubuntu) "python: /build/buildd/sip4-qt3-4.11.2/siplib/siplib.c:10613: sipEnumType_alloc: Assert-makro "(((currentType)->td_flags & 0x0007) == 0x0003)" ei pidä paikkaansa." [Undecided,Confirmed] https://launchpad.net/bugs/67462721:23
cjwatsonScottK: Just cleanup.21:25
ScottKOK.  Thanks.21:25
cjwatsonScottK: I was hunting for bugs filed on the upstream ubiquity project, which we don't use.21:25
ScottKThe sip4 upstream has been very responsive about fixing stuff, but since he actually spends time on stuff I send him, I'm reluctant to forward old bugs that I can't confirm are an issue.21:26
=== salem_ is now known as _salem
cyphermox@pilot in21:55
=== udevbot_ changed the topic of #ubuntu-devel to: Quantal Quetzal development | Beta 2 released! | Archive: Frozen | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and dicussion of hardy -> precise | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: cyphermox
slangasekbarry: so did you also hit bug #1054712?22:01
ubottuLaunchpad bug 1054712 in usb-creator (Ubuntu) "usb-creator-gtk crashed with SIGSEGV" [Medium,Triaged] https://launchpad.net/bugs/105471222:01
stgraberslangasek: I had that happen to me a couple of times lately while testing persistence. Seemed to happen pretty often when dealing with fast storage (external USB3 SSD).22:07
barryslangasek: yep.  i was investigating bug #915626 but realized it was different.  my reported bug #1064072 was duped to bug #1054712 but i didn't investigate further22:08
ubottuLaunchpad bug 915626 in usb-creator (Ubuntu Quantal) "usb-creator-gtk crashed with SIGSEGV" [High,Confirmed] https://launchpad.net/bugs/91562622:08
ubottuLaunchpad bug 1054712 in usb-creator (Ubuntu) "duplicate for #1064072 usb-creator-gtk crashed with SIGSEGV" [Medium,Triaged] https://launchpad.net/bugs/105471222:08
ubottuLaunchpad bug 1054712 in usb-creator (Ubuntu) "usb-creator-gtk crashed with SIGSEGV" [Medium,Triaged] https://launchpad.net/bugs/105471222:08
=== charlieS` is now known as charlieS
stgrabersegfault would typically happen after the file copy and before the boot sector would get written. Apparently killing the leftovers udisk and usb-creator processes was helping but it was still mostly random in my case (using the same source image and destination drive)22:09
barrystgraber: it sure smells like a reference counting bug22:10
stgraberat the time I was in the middle of sorting a bunch of casper bugs so didn't have much time to investigate. I just ended up manually setting up the MBR and the disk then worked fine.22:11
cjwatsonjtaylor: Yeah, you're off the hook - a retry succeeded22:17
cjwatson(phew)22:17
jtayloruff22:17
jtaylorstrange22:17
barrystgraber, slangasek: i can take a closer look tomorrow.  the crash sure seems like dbus-string.c is trying to delete something it doesn't own but thinks it does22:18
* jtaylor sticks big red marker onto scren "hands off seeded packages"22:18
jtaylorsorry for the screwup22:18
cjwatsonAh well, no real harm done in the end22:19
jtaylorat least i saw another potential issue scroll by in the log22:20
jtaylorWsequence-point22:20
jtaylorand reported to debian22:20
slangasekbarry, stgraber: so for me the problem is consistently reproducible when trying to write to a USB stick without persistence22:50
slangasekhaven't tried with yet22:51
barryslangasek: yep, when i was looking at it, it crashed every time for me.  debugging it will be fun though22:51
slangasekyeah, segfaulting python is my favoite22:52
barryslangasek: especially memory ownership bugs :)22:56
bdmurrayslangasek: is that the usb-creator bug?22:56
barrybdmurray: yep22:57
slangasekwell, apparently a different one than the one we currently have targeted22:57
slangasekbarry: python is very noisy under valgrind23:19
barryoh yes23:19
barryslangasek: Misc/vgrindefs from python's source helps (though it's been ages since i valground python ;)23:20
barryslangasek: oops23:20
barryslangasek: wrong file23:20
barryMisc/README.valgrind23:21
slangasekta :)23:21
barrynp!23:21
slangasekthough it's possible I can just ignore everything up to the point right before it crashes, anyway; it's fairly quiet while it's running the disk copy23:22
slangasek==12322==  Address 0x0 is not stack'd, malloc'd or (recently) free'd23:24
slangasekwell that's helpful23:24
slangasekhah, and when I run it under pdb it completes successfully :P23:35
slangasekbarry: bah, what does pdb permute that causes this command to succeed? :/23:45

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