/srv/irclogs.ubuntu.com/2011/11/27/#ubuntu-motu.txt

broderl3on: actually, it looks like there have been a handful of uploads to the debian clang package. would you mind looking at this and seeing if they're worth merging?00:03
broderugh, including a soname bump00:03
l3onbroder, what you mean? :) I'm new in merging :P00:04
broderme too :-P00:05
=== yofel_ is now known as yofel
broderok, it looks like the new version of clang is being held in debian unstable because of unmet dependencies, so let's hold off on that and just fix the package for now00:06
l3ongreat :)00:07
l3onbroder, should I send my patch somewhere?00:10
broderl3on: probably. i would start by trying to figure out if upstream clang has any multiarch-awareness. if it does, that'd be the place to send the patch00:15
broderif not, grab the latest package from debian unstable, update its ubuntu support, and file a debian bug asking very nicely if they'd take the patch00:15
anderskl3on: Have you tested that patch?  The equivalent patch didn’t work in oneiric, and I don’t see any reason for it to work in precise either.00:17
broderandersk: really? i can link simple executables with oneiric's clang package out of box00:17
l3onandersk, me too...00:17
l3onI mean... I built a package in oneiric, that fail in precise00:18
l3onbug 89666800:19
ubottuLaunchpad bug 896668 in forked-daapd (Ubuntu) "Please merge forked-daapd 0.19gcd-2 (universe) from Debian unstable " [Undecided,In progress] https://launchpad.net/bugs/89666800:19
anderskInteresting.  It was still failing for me in oneiric as of 2011-10-14.  But I’ve since upgraded to precise, and I can’t reproduce on oneiric anymore.00:20
broderi'm planning to test-build and test the packages before i upload, so i'll be sure it works00:21
anderskAnyway, can we write this patch in such a way that it doesn’t automatically break every six months?00:21
broderandersk: i'm open to suggestions00:22
broderl3on: by the way, the debdiff you uploaded is missing a trailing newline, and it confuses patch. i'll work around it, just fyi00:22
l3onis it the last line, right ?00:23
broderyeah, there's no newline at the end00:23
broderandersk: but i think a long-term fix should be discussed with upstream or at least debian, and i don't think fixing the package as it exists now should block on that00:23
anderskLike, if the distributor is Ubuntu but the codename is not one of warty, hoary, …, oneiric, precise, then it must be a future Ubuntu release, so we should assume it behaves the same as precise until we learn otherwise.00:24
l3onit's strange.. when I use gmail to send patch, if the last line is empty on LP line is replaced with a blank space... strange.00:24
broderl3on: ^ you want to try and do that?00:24
anderskSee http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-June/015545.html for my last attempt to argue with upstream about this stupidity.00:24
l3onbroder, I'll try ... :)00:26
broderl3on: ok. i'll wait to upload then00:26
l3onlet me collect idea :D00:26
l3onmmm... upstream o debian?00:26
anderskBoth.00:28
l3onandersk, broder → http://paste.ubuntu.com/750929/00:45
l3onwhat do you think about ?00:45
l3onthat's the text I'll file as bug in upstream00:45
anderskInclude a reference to my cfe-dev thread?  http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-June/015545.html00:47
anderskI’m pretty convinced that the right upstream solution is to switch back to calling gcc as a linker wrapper, like clang 2.8 did.00:49
l3onwell andersk it seems you know more then me :D00:51
l3onAnd I'm a bit confused about what write :P00:51
l3onbroder, could you merge the clang bugs ?01:00
broderl3on: merge? we don't have bug merges, we have duplicate bugs01:00
l3onjust to make a note about patch ...01:00
l3onah ok... :)01:00
l3onanyway... bug filed in upstream and linked in LP discussion01:01
l3onwe'll see01:01
l3on:)01:01
=== EvilJackyAlcine is now known as JackyAlcine
anderskNo matter what happens upstream, we should probably try to get Debian to do something about this.02:51
anderskThe LLVM 3.0 release is scheduled in 4 days and probably won’t have this fixed.  Debian probably won’t have 3.0 for a while after that, and 3.1 for an even longer while after that.02:53
=== mfisch` is now known as mfisch
=== mfisch is now known as Guest24696
broderScottK: can i get you to add backportbot to ubuntu-backporters?05:50
micahgbroder: umm, I wouldn't be so happy about that once ubuntu-backporters has archive perms05:53
brodermicahg: it's entirely under my control05:54
broderit's equivalent to giving me access, and i'm not planning to login anywhere i wouldn't login myself05:54
micahgbroder: I didn't realize we had so many old open backport requests06:02
broderneither did i until today :)06:03
broderat some point i'm also going to go through and do something with requests matching /from (dapper|edgy|feisty|gutsy|intrepid|etc)/06:03
broder(i'd mark them as incomplete if we expired bugs. as it is, i'm not sure what i'm going to do; i'm inclined to mark won't fix and encourage people to re-open)06:04
micahgbroder: the thing with the bot is that it's always on (usually on a server), so if that server is somewhere that's open to the world, there's a higher level of risk involved than a personal system which is probably either not always connected or behind some type of firewall/router06:05
micahgbroder: won't fix seems appropriate for the task since it's a backport per project instead of series06:06
micahgalso, if we can get people to use the new requestbackport tool, that would be a win as well06:07
broderis it possible for the bot to get bug triaging powers without adding it to ubuntu-backporters?06:08
micahgwell, that would require making a new bug supervisor team for the backport projects with ubuntu-backporters + whoever as members (might not be a bad idea anyways)06:10
micahgbut best to discuss with ScottK when he's available06:11
=== yofel_ is now known as yofel
l3onDebian bug 64635011:37
ubottuDebian bug 646350 in src:mupdf "mupdf: FTBFS with -Werror=format-security" [Normal,Open] http://bugs.debian.org/64635011:37
=== Quintasan_ is now known as Quintasan
jtaylorwhat happened with this backport: https://launchpad.net/ubuntu/+source/pyzmq/2.1.7-1~natty113:34
jtaylori386 is "building" since weeks and others never started13:35
AmpelbeinQuick question about sponsor-patch. I want to use it to acknowledge sync request in bug 896849 but all I get is http://paste.ubuntu.com/751396/. What am I doing wrong?13:39
ubottuLaunchpad bug 896849 in transgui (Ubuntu) "Sync transgui 3.2-1 (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/89684913:39
tumbleweedjtaylor: hrm, I get an OOPS when I try and look at the build record13:39
tumbleweedjtaylor: but IIRC, it was blocked on backports building against backports13:39
jtaylorme too13:39
tumbleweedAmpelbein: -s13:39
tumbleweedI guess we should improve that error...13:40
jtaylorthe armel log looks weird too13:40
Ampelbeintumbleweed: Thanks. I guess there is no way to skip test building (I've done that manually before).13:41
tumbleweedwere the builds killed maybe?13:41
tumbleweedAmpelbein: -u ubuntu13:42
tumbleweed(instead of -s(13:42
tumbleweedbroder: Any reason backport-helper doesn't link to the tracking bug in the changelog?13:44
Ampelbeintumbleweed: Thanks. Apparently I was mistaken about what sponsor-patch does for syncs.13:44
tumbleweedack-sync used to syncpackage13:45
Ampelbeintumbleweed: I thought it would either set bug to confirmed and add a comment like "Sync acked" OR use the lp function to sync the package from debian.13:45
tumbleweed(well, at some point we made it not do that any more)13:45
tumbleweedyeah, we aren't doing native syncs in it, because natvie syncs can't indicate sponsorship yet13:46
AmpelbeinI see.13:46
tumbleweedso, yes it just adds a comment13:47
tumbleweedbut leaves poking archive admins to you :)13:47
AmpelbeinHmm, ok. ;-)13:47
l3onhi all.. someone could tell me which tags I should add at debian bug 650180 ?13:48
ubottuDebian bug 650180 in metis-edf "metis-edf: FTBFS - missing link at math" [Normal,Open] http://bugs.debian.org/65018013:48
AmpelbeinBtw, this could be improved, too: http://paste.ubuntu.com/751409/13:49
jtaylorsome add-needed tags13:50
jtaylorone moment13:50
l3ontnx :)13:50
jtaylorhttp://wiki.debian.org/ToolChain/DSOLinking#Not_resolving_symbols_in_indirect_dependent_shared_libraries13:50
jtaylordoes it fail in debian?13:51
l3onjtaylor, what do you mean?... if in debian build fails ?13:52
jtaylorah no its not add-needed13:53
l3onI'm started work with build fail in Ubuntu, as reported here: https://launchpadlibrarian.net/83736713/buildlog_ubuntu-precise-i386.metis-edf_4.1-2-1_FAILEDTOBUILD.txt.gz13:53
jtaylorits actually underlinking which causes problem with as-needed, http://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries13:54
l3onsubmitted the fist debian bug 65017813:54
ubottuDebian bug 650178 in metis-edf "metis-edf: FTBFS with -Werror=format-security" [Normal,Open] http://bugs.debian.org/65017813:54
l3onand then the second one :)13:54
tumbleweedAmpelbein: that simply looks like a bug (the non-test-building code paths not getting enough testing)13:56
jtaylorwho do I have to talk to to get that backport issue resolved? #launchpad?13:57
tumbleweedjtaylor: I don't know what happned there, but there's no point worrying about it until bug 888665 is solved14:00
ubottuLaunchpad bug 888665 in Launchpad itself "Backports can't build-depend on other backports" [Critical,Triaged] https://launchpad.net/bugs/88866514:00
jtaylorah ok14:00
l3ontumbleweed, one week has gone... debian bug 64932214:24
ubottuDebian bug 649322 in clearsilver "clearsilver: FTBFS with -Werror=format-security" [Normal,Open] http://bugs.debian.org/64932214:24
l3onshould we adopt changes in ubuntu ?14:25
jtaylorno too early14:26
jtaylorwe should first wait for the toolchain to be fixed14:27
l3onok :)14:28
tumbleweedl3on: an hour after you left the channel, after filing that:14:35
tumbleweed02:16 < cjwatson> clearsilver, in scrollback: please don't touch that14:35
tumbleweed02:17 < cjwatson> I've contacted the security team about that one14:36
tumbleweed02:18 < cjwatson> sigh, public bug report, I suppose it's too late14:36
l3onmmm... so I did something wrong?14:37
l3onsecurity-issue ?!14:37
tumbleweedthere's a reason we made those fail builds, yes14:37
tumbleweedmany of them aren't dangerous, that one probably is14:37
jtaylorI don't see an issue with a public bug though, its a thing gcc can detect since years, anyone who wants to use that knows about it anyway already14:38
tumbleweedjtaylor: yeah, it was there for anyone who was looking for it14:38
tumbleweedl3on: you did nothing wrong. You could have contacted the security team in private, if you'd realised the security risks with it, but maybe someone else would have come along and filed a bug...14:39
cjwatsonl3on: clearsilver> that was an exploitable security hole, yes15:05
cjwatsonl3on: I sent mail to security teams with (IIRC) the same patch, before you looked at it; haven't heard anything back though15:06
cjwatsonbecause I thought it might benefit from a coordinated release15:06
cjwatsonit's true that anyone looking for it could have found it15:06
jtaylormight be worse increasing the severty of the bug then?15:07
cjwatsonjtaylor: "we should first wait for the toolchain to be fixed" - what fix would that be then?15:07
jtaylorcjwatson: fixed in the sense that it does not change anymore15:07
jtaylorI heard error=format-security may be disabled depending on the next rebuild15:07
cjwatsonI think you're out of date - I already disabled it in dpkg-buildpackage, but dpkg-buildflags still exports it15:09
cjwatsonin any case, that's no reason to delay a package upload15:09
cjwatsonI'll bump that Debian bug to grave now15:09
=== stalcup is now known as what
cjwatsonoh, huh, I didn't send a patch, silly me15:10
=== what is now known as v
cjwatsonl3on: anyway, sorry, I didn't mean to snark really, you had no way of knowing I'd already looked at that15:12
Laneyhow far back can we use .orig.tar.bz2?15:32
l3oncjwatson, sorry, that was my fault ... I'm not so good understanding severity of bugs ... I need more practice :D15:32
tumbleweedl3on: erm, nothing here is your fault at all :)15:33
l3on:)15:34
cjwatsonLaney: anything that supports 3.0 (quilt), so dpkg (>= 1.14.17), i.e. >= intrepid15:38
Laneycheers15:38
brodertumbleweed: that's not a backport-helper thing; it's happening at a lower level (i think mass-sync? but i'm not sure). i don't know why it's done that way17:30
tumbleweedah, right17:30
broderprobably because there's a fair amount of shared code with syncs17:30
tumbleweedof course, this is something else that LP will have to implement natively before our archive admins can lose shell access17:32
broderactually, at the TB meeting, we talked about just using backportpackage and uploading directly17:33
broderbut that would block on backporters being able to process the queue17:33
tumbleweedyeah17:33
Ampelbeintumbleweed: Can you test something for me: 'lp-shell staging' and then do 'lp.bugs[851798].subscriptions[1].canBeUnsubscribedByUser()' Does that result true or false?18:41
tumbleweedTrue18:42
Ampelbeinok, thanks.18:42
tumbleweederr that's ubuntu-release18:42
tumbleweedah, I was'nt on staging18:42
Ampelbeintumbleweed: Huh?18:42
Ampelbeinah18:42
tumbleweedright, still True18:43
tumbleweedI think the problem here was that PersonTeam is a wrapper around the launchpadlib object18:43
tumbleweedso == was never true18:43
AmpelbeinAye. The problem should be gone with the variable.18:44
AmpelbeinThere was another problem, if the sponsors team wasn't sub[0], a "Couldn't unsubscribe" would have been issued anyways.18:45
Ampelbeintumbleweed: ok, pushed a fix. It works for me now.18:52
=== micahg_ is now known as micahg
=== EvilJackyAlcine is now known as JackyAlcine
=== Guest89395 is now known as Zic

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