=== Spads_ is now known as Spads
=== alai888 is now known as alai
=== jamesh_ is now known as jamesh
=== robru is now known as robru__
=== robru_ is now known as robru
pittiGood morning05:45
dholbachgood morning07:29
seb128hey dholbach07:59
dholbachhi seb12807:59
=== gaspa_ is now known as gaspa
dholbach@pilot in08:47
=== udevbot_ changed the topic of #ubuntu-devel to: Wily (15.10) Released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-wily | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: dholbach
seb128dholbach, ;-)08:51
highvoltagen/win 2108:58
pittiapw, infinity, Laney: hah! queue lengths: http://autopkgtest.ubuntu.com/running.shtml09:04
=== davmor2_ is now known as davmor2
Laneypitti: nice!09:09
Laneyand shtml> nice too (was away on Friday when you announced it)09:10
Laneywe'll make a web designer of you yet09:10
pittiLaney: I just added <html style="layout: nice"> ☺09:12
pittiLaney: as for reading the queue contents: the administrator UI also just reads and requeues all requests, which garbles their order :(09:14
LocutusOfBorg1good morning folks09:16
pittiLaney: I reviewed your britney MP yesterday, looks good now! thanks for that09:17
pittiLaney: please push09:17
Laneyjust grinding through email, will look soon09:17
LocutusOfBorg1can anybody please retry arrayfire for xenial on amd64 and i386?09:30
LocutusOfBorg1it should build now09:30
LocutusOfBorg1and remove powerpc build, it doesn't build anymore in Debian too09:30
pittiLocutusOfBorg1: done09:30
pittiwell, the retries09:30
LocutusOfBorg1well, I uploaded a new version on Debian a few seconds ago09:31
LocutusOfBorg1we will see how the build goes09:31
LocutusOfBorg1but I need to know if the current version was failing because of underlying toolchain failures09:31
LocutusOfBorg1so thanks09:31
apwpitti, nice09:45
Laneypitti: manual merge proposal request: https://git.launchpad.net/~laney/+git/autopkgtest-cloud/commit/?id=6f74b2a4a718012fa645ca4f78a4557c4f26ad1809:46
Laney(LP doesn't support MPs for these personal git branches)09:46
* Laney cowboyed it already to check it works09:47
LocutusOfBorg1interesting, the build failed09:48
LocutusOfBorg1so I'll wait for the debian dinstall and ubuntu sync09:48
pittiLaney: ok, let's keep that for a while; pushed with a "debci-web-swift charm:" log prefix09:49
LaneyI think this makes browsers re-learn their URL bar entries at least09:50
morphisseb128, cyphermox, pitti: time to look at https://requests.ci-train.ubuntu.com/#/ticket/522 and publish if ok for you?10:09
pittimorphis: I'm afraid I have zero knowledge about libhybris and whether to update it10:09
seb128morphis, I don't think you need a coredev for that, #ubuntu-ci-eng trainguards should be enough10:10
morphisseb128: robru just told me I need one :)10:10
robruseb128: nope it's a main package, needs core dev10:10
robruseb128: trainguards have no publishing power any longer10:10
seb128oh, I didn't know libhybris was in main10:11
morphispitti, seb128: so who can do the publishing job then?10:11
morphiswas rsalveti who did that directly before10:11
Mirvmorphis: for example p + s10:11
sil2100seb128: yeah, it is, I already tried publishing this silo and failed ;)10:12
Mirvmorphis: sil_2100 possibly soon and I'll probably apply within a few months as well10:12
seb128Mirv, morphis, I just did it10:12
morphisseb128: thanks!10:12
sil2100seb128: thanks!10:12
seb128trusting you guys that the update is good10:12
morphisMirv: sounds good10:13
=== marcustomlinson is now known as marcustomlinson|
=== marcustomlinson| is now known as marcustomlinson
pittidholbach: btw, I'm handling bug 151082410:25
ubottubug 1510824 in policykit-1 (Ubuntu Wily) "PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)" [Medium,Triaged] https://launchpad.net/bugs/151082410:25
pittidholbach: (to avoid stepping on our toes for sponsoring)10:25
dholbachpitti, I uploaded it earlier - was that wrong? :-/10:26
pittidholbach: ah, didn't see that in the bug10:26
pittidholbach: no, it's ok, but I'm committing to Debian and would like to keep them in sync10:26
pittibut I can still sync after that10:26
pittidholbach: the stable SRUs are fine; thanks for sponsoring!10:27
* pitti updates the bug status10:27
dholbachthanks pitti!10:27
pittidholbach: I unsub'ed sponsors to clean up the list (the SRU will keep the tasks open for a while)10:28
Laneybdmurray: glib2.0/wily> I rebuilt the source pkg and uploaded it again, thanks for noticing10:32
=== vrruiz_ is now known as rvr
cjwatsoninfinity: Reminder about xenial chroot refreshing11:28
cjwatsonUnit193: Nothing special beyond the reposurgeon docs.  Once you're using reposurgeon rather than just fast-export/import, you're going to need to read its docs anyway :-)11:29
=== _salem is now known as salem_
morphiscyphermox: ping12:37
cyphermoxgood morning!12:41
cyphermoxmorphis: hey12:41
morphiscyphermox: good morning!12:42
morphiscyphermox: regarding our discussion on friday12:43
morphishave a look at https://code.launchpad.net/~morphis/bluez/vivid-5.36-upgrade/+merge/27830212:43
morphisand the result on https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-054/+packages12:43
morphiswhich produces now sane version numbers12:43
morphisfrom a MP12:43
morphiscyphermox: it currently only adds one extra changelog item "No-change rebuild."12:45
=== zsombi_ is now known as zsombi
pittiLaney: aah! "never passed" stuff on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#systemd :)13:09
Laneypitti: yay!13:11
Laneyand sad that we have this for unity813:12
didrockswhat is the difference with "always failed"?13:12
Laneydoesn't wait for the test to finish13:12
didrocksshouldn't it be "Test in progress (always failed)" rather then ?13:13
didrocksnot important, but it seems, this just introduce a difference where there should be none?13:13
tkamppetersladen, hi13:13
pittididrocks: yeah, that's a point13:13
* didrocks happy to propose a patch (just need to find the branch :p)13:14
pittididrocks: https://code.launchpad.net/~ubuntu-release/britney/britney2-ubuntu13:14
didrockspitti: thanks!13:14
* pitti hugs our new britney maintainer13:14
dholbach@pilot out13:15
=== udevbot_ changed the topic of #ubuntu-devel to: Wily (15.10) Released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-wily | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
didrockspitti: you should have told that after I did a MP :p13:15
didrocksstrategic mistake here ;)13:15
didrocks(but trailing coma at the end of the dict in the code, /me hugs $whoever)13:17
* didrocks looks for how to run tests13:20
didrocksyeah, I was just missing kombu13:22
didrocksand modified tests pass13:22
pittithat reminds me, we should probably change that to use python3-amqplib; as that's available in trusty, python3-kombu isn't13:22
pittirobru: ^ right?13:22
didrocks(same for python3-mock, it's part of unittest now)13:23
pittididrocks: oh? if you feel like it, please feel free to convert that too, that'd be appreciated13:24
pittididrocks: ah, that's just in ./tests/test_boottest.py, right?13:25
didrockspitti: https://code.launchpad.net/~didrocks/britney/more_coherent_message/+merge/278312 first13:25
didrocksand yeah13:25
didrocksI can change it13:25
pittididrocks: wrong merge target :/13:25
didrocksargh, I used bzr lp-propose13:26
didrocksso that set upstream branch isn't the right one13:26
pittididrocks: but nevermind, I can merge it like that13:26
didrockspitti: ok, thanks :)13:26
didrockspitti: feel free to change to unittest maybe meanwhile? I have the test_boottest failing here, even with trunk)13:26
pittididrocks: oh? works here13:26
pittiwhat's failing?13:26
didrocksTypeError: do_test() missing 2 required positional arguments: 'unstable_add' and 'expect_status'13:27
didrocksI'm on wily though13:27
didrockswith 3.413:27
didrocks(and running using nose)13:27
pittiwily/3.4 should be fine13:27
pittididrocks: I just call tests/test_autopkgtest.py and tests/test_boottest.py13:27
pittihow do you run using nose?13:27
didrocksyeah, calling works13:28
didrocksnosetests3 tests/*13:28
pittimerged, thanks!13:28
diwicmaybe having a runny nose helps13:28
* diwic sees puns everywhere, hard to hold back13:28
didrocksdiwic: ask Laney! :-)13:28
Laneyah, the bikeshed looks nicer now!13:28
didrockspitti: sweet! ;)13:29
didrockspitti: want me to push the unittest thingy?13:29
caribouAny reason why dh_input high would not prompt for a question during a normal apt-get install of a new package (never installed)13:29
pittididrocks: so, no idea aobut those; if you care, feel free to look into the nose thingy13:29
diwic"look into the nose thingy"?!13:29
caribouIf I follow-up with dpkg-reconfigure it does ask the question13:29
pittididrocks: but converting the external mock into whatever the internal replacement is sounds great (I figure it's trivial)13:29
pittidiwic: yes, so that it's running again :)13:30
* diwic goes gossiping about Britney's nose running and earns some extra $$$13:30
pittididrocks: apparently it's mis-interpreting the do_test() helper function as a test ?13:31
didrockspitti: sounds like so, let's not bother about the nose one, I'm looking at mock internal, one sec13:31
didrocksyep, quite easy :)13:32
didrockspitti: just last commit of lp:~didrocks/britney/unittest-mock13:33
pittididrocks: oh, that was really easy :)13:34
pittididrocks: merged, merci !13:35
didrockspitti: isn't it? There has been some small interface changes that I needed in my projects, but britney tests don't use any of them13:35
didrockspitti: avec plasir :)13:35
* mdeslaur hugs mardy for fixing unity-scope-gdrive13:49
seb128mardy, thanks for that!13:51
mardymdeslaur, seb128: yw! :-)13:51
mardythe funny thing is that I don't use it much, and I wasn't even aware that it was broken :-)13:53
cyphermox@pilot in13:55
=== udevbot_ changed the topic of #ubuntu-devel to: Wily (15.10) Released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-wily | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: cyphermox
sil2100cyphermox, kenvandine: hey guys! I have a core-dev-related packaging question14:04
mterrykenvandine, good morning!  Over the weekend, I tried building deja-dup trunk in a PPA, and it built fine, including tests: https://launchpadlibrarian.net/227251469/buildlog_ubuntu-xenial-amd64.deja-dup_34.1bzr1556~ubuntu16.04.1_BUILDING.txt.gz14:05
mterrykenvandine, so I'm claiming you've got something weird going on.  Although I don't know how it could affect your second laptop/new user14:05
sil2100cyphermox, kenvandine: first, the situation: as you know, since gcc5 some of our CI Train project stopped being able to dual land due to ABI changes (symbols etc.)14:05
sil2100cyphermox, kenvandine: so some of those projects decided on providing a debian/rules rule that auto-generates the control file and picks the right symbols file for the selected distro, changing the sonames etc. if needed14:06
sil2100cyphermox, kenvandine: anyway, those are in the archive... but now we have a new project that wants to start doing the same, but14:07
sil2100I found an issue with it, and just want to know if you guys find this bad as much as I do14:07
cyphermoxsounds bad to me already14:08
sil2100cyphermox, kenvandine: the new project that wants to do that basically also does the same magic as the others, but besides changing the symbols and control file, it also changes the content's library version (4.3.0 for vivid, 5.0.0 for xenial+) - the problem is, that due to how we do dual landings, both vivid and xenial *packages* would have one version number: 5.0.014:08
sil2100Meaning, the package for vivid versioned 5.0.0 would provide the 4.3.0 library in it14:09
sil2100While the same version (just with the CI Train version part changed to 16.04 as for all dual-landings) would have 5.0.0 in it14:09
sil2100For xenial14:10
cyphermoxwhy say it's 4.3 if it's not?14:10
sil2100cyphermox: well, yeah, it's evil, I didn't like the idea but Steve and some other people agreed on that hack to allow dual-landing for people14:10
sil2100cyphermox: I guess the reason is, since there's ABI breakage between releases, the upstream doesn't want the sonames to be the same for both14:11
sil2100So they originally bumped the wily/xenial version to 5.0.014:12
cyphermoxsil2100: if they break ABI, the so version should change14:12
cyphermoxthat applies to vivid too14:12
kenvandineyeah, i'm not sure i understand how it helps anything14:12
cyphermoxcould they not just SRU things ?14:12
sil2100cyphermox: the ABI breakage is from the toolchain side14:13
sil2100So it's not something they caused14:13
cyphermoxhow so?14:13
sil2100They still build from one source tree14:13
cyphermoxI think it would be best to see the code14:13
sil2100It's C++11, due to gcc5 the symbol files changed between vivid and wily/xenial14:13
cyphermoxthat doesn't make it a different so version though, if it's just that the symbols are named differently14:14
cyphermoxie. you still might have new API in the library, it's just that the symbols file will look one way for vivid because gcc < 5, and another way for wily/xenial because gcc >= 514:15
sil2100cyphermox: yes, they're named differently, so there's no compatibility between libraries then, right? Since a lib build against one will expect different symbols coming from the library14:15
cyphermoxI mean, there won't be a difference between the symbol names as they are in vivid right now and the new version of that package.14:16
cyphermox(or what they might have been if the package existed already and what it will now be)14:16
sil2100You mean, no difference in symbols between compiling against gcc4.9 and gcc5?14:18
=== barry` is now known as barry_
=== barry_ is now known as barry
=== mhall119|fossetc is now known as mhall119
jamespagehow big is the filesystem that supports PPA based builds?  I'm hitting what I think is a freespace issue in this PPA - https://launchpad.net/~openstack-ubuntu-testing/+archive/ubuntu/ceph-sru/+packages14:28
jamespagebut can't tell for sure...14:28
cjwatsonjamespage: 60GiB14:29
cyphermoxsil2100: what I mean is there is obviously a difference between compiling with 4.9 and 5, but vivid should always compile with 4.9, so you shouldn't have to jump through hoops messing with soname or sover, things should just "work"14:29
cyphermoxor did I get the gcc version used in vivid wrong? ;)14:30
cjwatsonjamespage: it's the same for PPAs and Ubuntu builds14:30
jamespagecjwatson, okay14:30
* jamespage scratches his head14:30
cjwatsonjamespage: doesn't look like a disk issue to me14:30
cjwatsonjamespage: cc1 is being SIGKILLed, which implies OOM14:31
cjwatson(more or less)14:31
cjwatsonjamespage: is this an extremely large translation unit?14:31
dobeymwhudson: you around?14:32
sil2100cyphermox: well, things don't really work, as the fact is: you have different symbols exported in one distro and different in the other, which means that the soname should be bumped14:33
sil2100(bumped = changed)14:33
sil2100cyphermox: at least that's what I have always been taught14:34
sil2100cyphermox: so now, building the same package on two different distros, with the package providing a symbols file - people now look for a way to build those two at once from one source tree14:34
sil2100cyphermox: since you at least need to provide 2 different symbols files for vivid and wily/xenial+14:35
sil2100Although everyone doing this anyway changes the soname as they're no longer binary compatible14:35
sil2100I mean, ABI-compatible14:35
cyphermoxsil2100: it's only relevant if the code in the library changes. if what you're seeing is one distro giving out symbols named in a particular way (mangled some way), and another distro mangled a different way, you still have the same API/ABI, it's just toolchain specifics?14:37
zzarrhello! how do I avoid this message when building an application for generic Ubuntu ARM? error: Unknown module(s) in QT: bluetooth14:37
cyphermoxin other words, building on vivid or on xenial should work without any changes as long as they're not using magic that is only available in gcc5, provided they just use the default compiler for the release14:38
cyphermoxwhat you'll hit after that is just how dh will parse and compare the symbols generated14:38
zzarrcyphermox, did you respond to my question?14:39
sil2100cyphermox: yes, and that was the main point of doing the hack with debian/rules, but they also change the soname as this was recommended by someone from the ubuntu-archive team14:39
dobeydoko: you around?14:39
sil2100But that's irrelevant to the original question ;)14:39
cyphermoxzzarr: no, that was for sil210014:39
zzarrokey, I was confused ;)14:40
dobeyzzarr: install the bluetooth qt module?14:40
zzarryes, but how do I do that?14:40
cyphermoxsil2100: I don't have the context for the soname change, I guess, unless it's to support upgrades correct, in which case what is meant is the name of the library.14:40
dobeylibqt5bluetooth5 - Qt Connectivity Bluetooth module14:41
killallHello, i need some help, i have 2 usb devices purchased in diferent times and one works and the other does not work. Booth work in windows.   SONiX USB Device in lsusb detects as   0c45:8419 Microdia14:41
zzarrdobey, I know, but where do I install it?14:41
killallthis is making me crazy i dont know if i have to mod the driver or not14:42
zzarrin the emulator?14:42
dobeykillall: #ubuntu is the support channel14:42
dobeyzzarr: i don't know how you are building things, but yes, wherever you are getting that error is obviously where it needs to be installed14:42
zzarrI get the error here (compiler output) The process "/home/zzarr/.config/QtProject/qtcreator/ubuntu-sdk/ubuntu-sdk-15.04-armhf/qt5-qmake-arm-linux-gnueabihf" exited with code 3.14:44
zzarrdobey, I installed the package, but it did not help14:46
sil2100cyphermox: well, I guess it had to be done that way in wily, since let's say you have a library foo with an soversion of 2 in wily compiled against gcc4.9, then gcc5 got uploaded and foo had to be rebuilt - without the soversion changing, apps linked against soversion 2 would stop working14:47
dobeyzzarr: you are trying to write an app that uses that module, for the phone?14:51
sil2100cyphermox: since it all happened in one series14:52
dobeyzzarr: you can't, you'll have to ship the library in your own package, and even when doing so i don't think you'll be able to use it anyway14:53
zzarrdobey, no it's for a generic device with a bluetooth dongle14:53
dobeyzzarr: but you're building it using the phone sdk14:53
zzarrhow do I do that (it might just work)14:54
dobeyare you trying to build a .deb package?14:54
zzarrsimply downloading the code and building it, thanks14:54
zzarrno, it's installed in opt14:54
zzarrthanks for the heads up dobey :D14:55
dobeydeb packages can install in opt. cf the "for purchase" apps in software-center14:55
zzarrtrue, but so far I've just installed the project in opt directly from the SDK14:56
kenvandinemterry, no idea what's going on... it fails consistently for me in sbuild :/14:57
dobeyubuntu-sdk isn't building in an emulator, it's cross-compiling; and the ubuntu-sdk chroots have further restraints since they're for the phone14:57
kenvandinemterry, i can't look at it today though, sorry14:57
mterrykenvandine, ok.  Maybe I can bug another desktop person and that would be a good 3rd (4th if we could LP) opinion14:58
kenvandinemterry, yeah... sorry :)14:58
zzarrdobey, okey, so that's why it's not working for me14:58
mterryseb128, know anyone that wants to review a deja-dup branch (to drop python2 from image)?14:58
dobeyzzarr: i'd suggest just making your own chroot for cross-compiling it in, or building on armhf hardware directly14:59
mterrykenvandine, no worries  :)  sorry it was such a hassle14:59
seb128mterry, python ... maybe try didrocks?14:59
mterrydidrocks, hello  :)14:59
* didrocks whistles14:59
didrocksmterry: ok ok, I'm using deja-dup (and still swearing against bad volumediff sometimes) :p but I thing I owne you that ;)15:00
mterrydidrocks, heh15:00
mterrydidrocks, https://code.launchpad.net/~mterry/deja-dup/no-python2/+merge/27687515:01
didrocksmterry: for tomorrow is fine?15:01
mterrydidrocks, kenvandine looked at it, but saw some weird test failures that I and LP couldn't reproduce.  So I'm hoping for another sanity check.  Yeah, tomorrow is fine15:01
didrocksah, interesting, yeah, will do15:02
didrocksseb128: there is some vala in this python, want to remind me some Unity0 time? :)15:02
mterrydidrocks, this is vala changes to allow us to drop a python2 package from the image15:03
mterrydidrocks, seb128 tricked you15:03
mterrynot intentionally  :)15:03
seb128didrocks, yeah, like in good old times!15:03
didrocksI don't see any clutter dependency though, not fully good old times! :)15:04
didrocksmterry: yeah, seems so :p15:04
zzarrokey, I'll make my own chroot in that case :)15:04
zzarrthanks dobey, I have to go15:05
pittiLaney: ah, did you restart the dbus tests?15:12
pittiLaney: I think I overzealously killed a batch before, I thought they were still hanging; thanks for fixing those!15:12
pitti(if you didn't restart them, I will)15:13
pittibut I need to sort out the "apt-get source needs to download the -release version" issue15:13
cpaelzerpitti, hi I'm working with autopkgtest for the first time and wonder if there is a way to let adt-run invoke the adt-virt-qemu with -smp >1?. Google neither made me happy about "why not" nor "how to"15:14
cpaelzerpitti, test can't run in schroot which would be the more obvious solution :-/15:14
pitticpaelzer: see man adt-virt-qemu15:14
pitticpaelzer: -c N15:14
cpaelzerpitti, to bad I search for smp in the doc - thanks!15:14
cpaelzergoogle needs to learn what I need and not what I ask - so do manpages (or read them from beginning to end)15:15
didrocksximion: hey, not sure if you saw my new PR so that we can ensure a more consistent experience for people deploying appstream: https://github.com/ximion/appstream-dep11/pull/2. Hope that helps!15:16
pitticpaelzer: you can also pass through arbitrary qemu options (--qemu-options) for the stuff that isn't exposed directly15:16
ximiondidrocks: saw it, will apply it soon :-) Looks pretty good :)15:16
* ximion will work on getting rid of X-Source-Checksum in DEP-11 files soon15:17
didrocksgood :)15:17
cpaelzerpitti, yeah just saw it as I started to fully digest man adt-virt-qemu - thanks15:17
jamespagecjwatson, quite possibly (re is this an extremely large translation unit?)15:19
jamespagecjwatson, how much memory do we give builders these days?15:20
cjwatsonjamespage: 4GiB15:23
cjwatsonjamespage: can you split the translation unit?15:24
jamespagecjwatson, erm feeling stupid - how would I go about doing that?15:24
cjwatsonjamespage: we've talked about bumping to 8GiB, but it will take a while, and it still makes sense to look for approaches to make the build less unreasonable15:24
cjwatsonjamespage: erm, depends?  look at the .c file in question, see if there's some way to split it up if it's enormous15:25
cjwatsonjamespage: may be lots of complex macro expansion or something15:26
jamespagecjwatson, 11k lines15:26
cjwatsonthat's pretty big15:26
cjwatsonjamespage: another approach you can try is to use less parallelisation in your build15:26
jamespagecjwatson, yeah I was thinking that15:27
jamespagegonna take a loooonnggg time to build now...15:27
cjwatsonjamespage: well, you could try initially just dropping it to 215:27
=== salem_ is now known as _salem
=== manjo` is now known as manjo
=== Daviey_ is now known as Daviey
maprerican somebody explain me why this is not building?  the b-d it's complaining about looks available to me.. https://launchpad.net/ubuntu/+source/squashfs-tools/1:4.3-316:16
pittiSection: universe/libdevel16:20
seb128mapreri, that package is in main16:20
seb128it can't use a build-depends in universe16:20
pittimapreri: liblz4-dev is in universe16:20
mapreriok, i got fooled by the "main" label on https://launchpad.net/ubuntu/+source/lz4/0.0~r131-1 ..16:21
pittican't this use lzma?16:21
maprerino idea, i've no releshionship with it other than being involved on a reverse of a reverse of a reverse dep :)16:22
mapreribut the why there is a "component: main" in https://launchpad.net/ubuntu/+source/lz4/0.0~r131-1 ... :S16:23
infinitymapreri: LP display misfeature.  It came from main in Debian.  If you look at the publishing info on the right, is says universe.16:26
infinitys/is says/it says/16:26
mapreriyeah, i figured.. that's confusing, but anyway..  yes guess squashfs-tools can be built without lz4, removing support for it; it got added some releases ago, but it's an optional flag in d/rules16:28
cjwatsonmisfeature> oh, I missed a bit when I tried to remove that from the UI.16:30
pitticjwatson: hm, https://launchpad.net/ubuntu/xenial/+queue?queue_state=0 lost its components/section displays16:39
pittiworth a bug report, or known already?16:39
cjwatsonpitti: expand the items16:40
pitticjwatson: oh, silly me -- thanks16:40
cjwatsonpitti: you'll see the component/section directly on source uploads, but for binary uploads they're per-binary16:41
pitticjwatson: yeah, of course -- I was just confused for a sec16:41
=== Spads_ is now known as Spads
=== Spads_ is now known as Spads
=== _salem is now known as salem_
robrupitti: correct that python3-kombu is not in trusty18:12
sladentkamppeter: yo20:02
mwhudsondobey: hi20:21
=== salem_ is now known as _salem
dobeymwhudson: hey. i was wondering if you had any idea what was going on in this build failure on ppc64el? https://launchpadlibrarian.net/227153468/buildlog_ubuntu-xenial-ppc64el.pay-service_15.10%2B16.04.20151120.2-0ubuntu1_BUILDING.txt.gz20:26
dobeymwhudson: it's happening only on ppc64el on xenial; everything else built fine20:26
dobey(and exact same code built fine on vivid)20:27
dobeyhoping it's something we can fix easily/quickly, but my gccgo skills are limited, especially regarding hardware i don't have any direct access to20:27
mwhudsondobey: oh hm20:58
mwhudsondobey: looks like https://github.com/golang/go/issues/1337520:59
mwhudsonyeah very much like that21:01
mwhudsondobey: what's the actual care level on this? :-)21:03
mwhudsonwe'll be uploading go 1.5.2 within a week or two and i'll try to make sure this is fixed there21:03
mwhudsondobey: don't you have access to the ppc64el porter box?21:04
mwhudsonoh heh no xenial chroot anyway21:04
dobeyi don't21:07
dobeywell, if i do, i don't know anything about porter boxes :)21:07
dobeymwhudson: it's not super urgent, but would like a fix asap. any idea on when exactly that fix would land?21:10
tkamppetersladen, you are working with fonts?21:10
sladentkamppeter: some times21:11
sladentkamppeter: when the mood takes me21:11
tkamppetersladen, there seems to be used some fonts with unclear copyright in Linux, see https://bugzilla.redhat.com/show_bug.cgi?id=1284215.21:12
ubottubugzilla.redhat.com bug 1284215 in myanmar3-unicode-fonts "Possible copyright violation with the Myanmar3 unicode font" [Unspecified,New]21:12
tkamppeterSo Hin-Tak Leung, the reporter of this bug asked me to forward this to the font maintainers of Ubuntu/Canonical to check whether Ubuntu contains any fonts with the same copyright problem.21:14
tkamppetersladen, so I want to ask you to check this.21:14
* sladen looking ... tkamppeter 21:18
sladentkamppeter: thank you for the heads up21:21
mwhudsondobey: week or two?21:37
mwhudsonoh i see "exactly"21:37
dobeymwhudson: any idea if it would be trivial to throw the patch in the existing package and do a quick upload?21:37
mwhudsondobey: probably21:38
dobeymwhudson: can i bribe you to do that? :)21:38
mwhudsondepends on how quickly ~ubuntu-sponsors react21:38
mwhudsondobey: i'm still waiting for my last "quick fix" to get sponsored...21:38
dobeyoh, you don't have upload privs?21:38
dobeywhat source package is that in?21:39
mwhudsonit would also be good to test that the fix actually helps, which means some fooling around with ppas i guess21:39
mwhudsondobey: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/150165121:40
ubottuLaunchpad bug 1501651 in golang (Ubuntu) "ARM chroot issues: fatal error: rt_sigaction failure" [High,In progress]21:40
dobeymwhudson: oh, that upload faild to build on amd64 and i38621:41
dobeymwhudson: with the unexpected relocation error! :)21:42
mwhudsonno, that was the previous one21:42
mwhudsoni'm fairly sure21:42
mwhudsonand yes, can we get the binutils people to stop changing things please21:42
mwhudsonyes, that's ubuntu3, i'm waiting for someone to upload ubuntu421:43
dobeyoh ok21:43
dobeyinfinity, slangasek: ^^ can one of you sponsor the latest patch on bug #1501651 please?21:44
ubottubug 1501651 in golang (Ubuntu) "ARM chroot issues: fatal error: rt_sigaction failure" [High,In progress] https://launchpad.net/bugs/150165121:44
slangasekdobey, mwhudson, infinity: done22:35
mwhudsonslangasek: thanks!22:35
Unit193slangasek: Is it the weekend yet? :)22:35
sarnoldUnit193: .. it's like you can read minds :)22:37
Unit193sarnold: I can't even read my own mind...22:37
=== _salem is now known as salem_
=== salem_ is now known as _salem
mwhudsonslangasek: whaat https://launchpadlibrarian.net/227405312/buildlog_ubuntu-xenial-amd64.golang_2%3A1.5.1-0ubuntu4_BUILDING.txt.gz22:44
mwhudsonspecifically "E: Failed to fetch http://ftpmaster.internal/ubuntu/pool/main/g/gettext/libasprintf0v5_0.19.4-1ubuntu3_amd64.deb  Temporary failure resolving 'ftpmaster.internal'22:45
mwhudsoni guess that means retry?22:45
cjwatsonmwhudson: yes, must have been temporary network trouble particularly given that subsequent fetches succeeded22:46
mwhudsoncan someone hit retry on https://launchpad.net/ubuntu/+source/golang/2:1.5.1-0ubuntu4/+build/8335506 ?22:46
cjwatsonmwhudson: retried22:46
cjwatsonwas already going there :)22:46
slangaseknot the first such resolution failure I've seen in the past week, hmm22:46
mwhudsoncjwatson: service!22:47

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