=== doko_ is now known as doko
shadeslayeris pm-utils still required on the ISO?03:44
=== timrc-afk is now known as timrc
=== timrc is now known as timrc-afk
=== BruceMa is now known as BruceMa-afk
pittiGood morning05:52
dokopitti, I'm annoyed about autopkg tests05:57
dokowhy is the aspcud test run when gcc-4.8 gets uploaded?05:57
pittidoko: was it? AFAICS it was run because 1:1.8.0-1 landed in trusty-proposed on Jan 11, and that introduced an autopkgtest05:59
pitti(which fails, like almost every new autopkgtest that we get *sigh*)05:59
pittiI got another slew of failures over the weekend, going through them todya06:00
dokopitti, pretty please can we ignore results for new autopkg tests until they get reviewed06:03
ubottuDebian bug 735138 in aspcud "autopkg test always failing" [Serious,Open]06:03
pittidoko: yes, jibel said he's working on that, to only hold back packages if the test ever succeeded06:04
pittidoko: until then, if something is held back by them (not gcc-4.8 though), the release team can set a "known broken" tag06:04
dokogood to know06:04
pittigcc-4.8 isn't even in -proposed06:04
dokopitti, it was, asked infinity to ignore the test. but it's annoying that I have to care about these06:05
Logan_infinity: why did most of the ppc64el FTBFSes disappear overnight07:36
Logan_I am so confused07:36
Logan_wait they were all reset to "needs building"07:38
Logan_but why07:38
Logan_doko: is this because of your mass rebuild?07:38
dokoLogan_, he did give back the packages, they should reappear soonish07:40
Logan_who did?07:40
Logan_I'm so confused :P07:40
dholbachgood morning07:40
Logan_hey Daniel07:41
dholbachhey Logan_07:41
dholbachhow's life over there?07:41
Logan_It's going. :P07:42
Logan_It is also approaching 3 AM, so I should probably get to sleep.07:42
dholbachthat sounds like a good idea :)07:42
Logan_doko: I'm still confused though. :( Who is "he," and to whom is he giving back the packages? :P07:43
dokoto the buildds07:43
Logan_So it is Adam's fault. :P07:44
Logan_I am so intuitive.07:44
Logan_I also have to forward like 20 ppc64el patches to Debian. So tedious.07:46
dokoLogan_, are you user-tagging these?07:46
Logan_infinity and I were discussing that yesterday with juliank.07:47
Logan_I don't think we came to a conclusion about what the usertag(s) should be and if my bugs even need one.07:47
Logan_Because the dh-autoreconf/autotools-dev are more futureproofing than necessarily fixing FTBFSes on a specific architecture.07:48
Logan_But they do serve an immediate purpose, though.07:48
Logan_Hi Jackson.07:48
Noskcajhey Logan_07:48
Logan_doko: Please let me know if I should use something, though.07:49
Logan_...and, if so, if I have to retroactively apply it to all ~120 other ppc64el patches I've submitted.07:50
Logan_Well, some of those are config.{sub,guess} updates with autotools-dev. I guess that whittles that number down a bit. :P07:51
dokoyou can do that with a control message07:52
Logan_Okay. Is this usertag going to be a standard?07:52
dokomaybe use debian-devel@lists.debian.org as the user, but let's ask others about that first, like cjwatson07:52
Logan_There should probably be a larger discussion about this, yeah.07:55
MacSlowGreetings folks!08:01
=== BruceMa-afk is now known as BruceMa
pittidobey: hey Rodney, how are you?08:34
pittidobey: mvo approved https://code.launchpad.net/~pitti/software-center/deprecated-ctors/+merge/201158, would you mind merging this? thanks!08:35
=== jodh` is now known as jodh
rbasakjdstrand: are you aware of bug 1262710, please?08:58
ubottubug 1262710 in nginx (Ubuntu) "[MIR] nginx" [Undecided,Confirmed] https://launchpad.net/bugs/126271008:58
Noskcajdholbach, What do i do to fix the test failure i just made? I barely know enough C to make a "hello world"09:01
NoskcajAnd do test failures make the build crash locally and i missed it or has something broke since?09:02
dholbachNoskcaj, no the test worked out fine for me locally - I did a test build09:03
dholbachNoskcaj, if you don't get very far with your own investigations, you could ask in here, or on ubuntu-devel@ for some help09:03
dholbachand if that doesn't help, you could ask upstream09:03
Noskcajok, will do.09:05
NoskcajAlthough tomorrow, since i'm not meant to be on the internet09:05
dholbachNoskcaj, see you! :)09:06
Noskcajbye, thanks for the tips09:06
dokojodh, there is no libnuma-dev on arm64 and armhf09:58
jodhdoko: yes, I saw that and was wondering how to define that in debian/control as I've already specified some arch restrictions on that package.09:59
dokojodh, or you try to build it on these archs ;p09:59
dholbachseb128, does Laney's comment on 1268097 make sense?10:01
jodhdoko: I have been waiting since November for Debian to approve my request to access their porter boxes for that exact reason10:02
dokojodh, well, you have access to armhf, and debian doesn't have access to arm64 either10:03
jodhdoko: sure. I'm trying to keep the process for myself as simple as possible as procenv builds differently on every arch and there are lots to support :) Wouldn't it be great if it was possible to test this out on mentors rather than via an upload? So, do you know how I would build-depend on libnuma-dev for (linux-all - arm64 - armhf)?10:05
jodhdoko: ... - armel - arm64 :)10:07
dokojodh, enumerate the libnuma-dev architectures explicitly10:09
shadeslayercould somene look at https://launchpadlibrarian.net/162316715/buildlog_ubuntu-trusty-ppc64el.kubuntu-meta_1.297_FAILEDTOBUILD.txt.gz10:23
shadeslayerCan't open desktop-ppc64el: No such file or directory at /usr/bin/dh_germinate_metapackage line 78.10:23
dokoshadeslayer, you need to add it in kubuntu-meta10:31
shadeslayerdoko: yep, missing arch in update.cfg10:31
TJ-Anyone familiar with apparmor internals? Specifically whether it is supposed to truncate the logged process name in syslog, e.g. comm="qemu-system-x86" instead of comm="qemu-system-x86_64" - looks like a truncate-on-underscore bug unless its deliberate10:45
cjwatsondoko: I really don't care what the usertag is; pick one :)11:02
cjwatsondoko: though using debian-devel@ seems to imply a consensus there, which isn't clear11:03
cjwatsonshadeslayer: I was deliberately not adding it until more of the rest of Kubuntu is built on ppc64el11:03
Mirvmitya57: hi! dok_o confirmed that the aarc64 Qt patches are not needed anymore with 5.211:03
shadeslayercjwatson: oh .... how do I check that ? :S11:03
dokowell, we could use one of our own email addresses11:04
cjwatsonshadeslayer: http://qa.ubuntuwire.org/ftbfs/ppc64el.html has a section for it11:04
shadeslayerI see11:04
cjwatsonhttp://qa.ubuntuwire.org/ftbfs/ppc64el.html#kubuntu in fact11:04
mitya57Mirv: great, drop them then :)11:04
Mirvwill do11:05
dokofyi, I demoted trac-bzr to -proposed. is there anybody I should explicitely tell about it?11:05
shadeslayercjwatson: ack11:05
directhexis there a way for mortals to developer for aarch64 yet?11:08
shadeslayercjwatson: ugh, eigen is FTBFS11:10
cjwatsonshadeslayer: can't help you with that one, I don't speak enough C++11:12
dokoshadeslayer, eigen?11:18
brendandwhere can i get newer versions of pulseaudio?11:19
shadeslayerdoko: https://launchpad.net/ubuntu/+source/eigen2/2.0.17-1/+build/534550311:19
shadeslayercjwatson: while you're here, any ideas if pm-utils will go away?11:23
seb128dholbach, commented on the bug btw ;-)11:26
seb128dholbach, readonly is not really an issue there, we don't want people to have to adb to sudo cp files to add a ringtone, we can do better than that ;-)11:27
=== MacSlow is now known as MacSlow|lunch
cjwatsonshadeslayer: no idea11:30
dokozul, beanstalkd ftbfs11:51
pittishadeslayer: not anytime soon, as long as there are still laptops out there which need suspend quirks12:13
=== _salem is now known as salem_
pittishadeslayer: it's optional these days (meaning that logind will work without it), and we don't install it on phones, but we still want it on desktops12:14
mptev, was the fix for bug 1033902 ever backported to 12.04? From the bug report it seems not.12:15
ubottubug 1033902 in Apport "Application thread crash shows application crash error alert" [High,Fix committed] https://launchpad.net/bugs/103390212:15
mpt…Though the bug description is filled out as if it was meant to be.12:17
pittino, it wasn't12:17
=== MacSlow|lunch is now known as MacSlow
arges@pilot in13:19
=== udevbot changed the topic of #ubuntu-devel to: Trusty Tahr Alpha 1 released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: arges
kentbxnox: sorry about the mixup with sblim-sfcc...all my fault. I'll work on getting it cleaned up today13:24
=== ara is now known as Guest58013
caribouslangasek: I have a question for you regarding http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=70665513:37
ubottuDebian bug 706655 in kdump-tools "kexec-tools: Please consider including integration for kdump auto-dumping" [Wishlist,Open]13:37
caribouslangasek: we no longer use the script in kexec-tools. It has been overriden by the kdump-tools since Raring :13:39
=== timrc-afk is now known as timrc
jdstrandTJ-: re apparmor, I believe that for "comm" that is by design. you'd likely have more luck asking on #apparmor on OFTC13:46
mlankhorstchrisccoulson: ping?13:46
TJ-jdstrand: OK... I've logged a bug report since it's useless if the reported process name can't be given to aa-complain/aa-disable13:48
jdstrandTJ-: normally you use the path to the profile name for that and the path used for binary attachment is "name" not "comm"13:51
jdstrandTJ-: reading 'man apparmor', while the text is quite old, it says there is a 15 byte limitation on the process name due to Berkeley process accounting13:52
psivaacjwatson: doko: a precise-alternate issue after 20140111: http://pastebin.ubuntu.com/6744680/ unmet deps.13:52
psivaanothing urgent here for me.. but just letting you know if in case it interests you. and apologies if it doesn't :)13:53
TJ-jdstrand: which would explain it... thanks! Caught me out trying to solve an issue with libvirt/qemu-system-x86_64 being denied access to /dev/sr013:54
dokotjaalton, ^^^ could you look at psivaa message? I think you did update precise13:54
cjwatsondoko,tjaalton,psivaa: I suspect it's a CD-building problem and that tjaalton is going to be a bit stuck13:55
cjwatsonI'll look at it, but not this afternoon, am going to be offline for a few hours13:56
tjaaltonmlankhorst: ^13:56
tjaaltonmissing packages I think?13:56
cjwatsonboth the enablement stack and the original stack are trying to be installed for some reason13:57
tjaaltonsounds familiar13:57
mlankhorstmaybe some egl drivers are tried?13:57
cjwatsonthe desktop-common seed pulls in the old stack, which is reasonable for the seed in general but the images will need to figure out how to override it13:59
cjwatsonI'll look at it but as I say not this afternoon13:59
mlankhorstcjwatson: libtxc-dxtn-s2tc0 is in universe13:59
mlankhorstat least for precise13:59
cjwatsonwhich no doubt contributes but isn't the sole problem13:59
cjwatsonat least I doubt it13:59
cjwatsonI mean it's only a Recommends, it can't be breaking things14:00
cjwatsonmlankhorst: but I can move s2tc to main in precise-updates if that's what you folks need14:00
mlankhorstyes please14:00
cjwatsonlike I say, though, won't fix this14:01
mlankhorstyeah something causes the main stack to be installed14:01
mlankhorstcjwatson: what image btw?14:02
cjwatsonprecise alternate, as psivaa said14:03
mlankhorstI think the snippet is too small to say anything sane about it14:06
mlankhorstwould need a bigger log14:06
cjwatsonI agree, need to dig into it in more detail.  we don't need a libglu1-mesa-lts-saucy, do we?14:06
cjwatsonthough that might just move the problem one level up, anyway14:07
mlankhorstlibglu split off from mesa after 8.014:07
psivaamlankhorst: http://pastebin.ubuntu.com/6744772/ is the full install log14:07
cjwatsonI don't think we're going to get the reason out of logs14:08
mlankhorstJan 13 13:36:45 in-target: invoke-rc.d: policy-rc.d denied execution of start.14:08
mlankhorstJan 13 13:37:20 in-target: Reading package lists...14:09
mlankhorstnope, missing the install command :/14:09
cjwatsonwouldn't do you any good anyway, it's just installing a task, and the definition of the task will be image-specific14:09
mlankhorsthm maybe the unrenamed packages are still part of the task?14:10
cjwatsonno doubt14:10
cjwatsonwhich is why this is an image-building problem to debug14:10
cjwatsonI doubt it's your problem14:10
cjwatsonmlankhorst: mind you - shouldn't libglamor-ltss0's depends prefer libgl1-mesa-glx-lts-saucy rather than libgl1-mesa-glx?14:12
mlankhorstoh, it should..14:13
cjwatsonmlankhorst: that's the reason germinate's giving me at the moment14:13
mlankhorstbut the package rename script should have taken care of that..14:13
cjwatsonit's the only match in grep-dctrl -FSource:Package lts-saucy --and -FDepends 'libgl1-mesa-glx '14:14
cjwatsonso fixing that will either help or will expose the next problem :)14:15
mlankhorstit shouldn't be fatal at least... no idea why it wants libgl1-mesa-glx explicitly either14:16
cjwatsonit's fatal in this case because task construction is not always entirely deterministic and essentially depends on which one of a set of alternatives it sees first14:17
cjwatsonso right now that's what causes libgl1-mesa-glx to be pulled into the ubuntu-desktop task on the alternate image14:17
mlankhorstlooks like I may need to explicitly depend on libgl1-mesa-glx-lts-saucy in build-depends then or something14:18
mlankhorstcjwatson: oh, it seems to be because of shlibs in libgl1-mesa-glx-lts-saucy14:20
mlankhorstI would rather not change that, can I override the shlibs:Depends for glamoregl?14:21
mlankhorsthm maybe adding libgl1-mesa-glx-lts-saucy in front is enough14:21
cjwatsonprobably won't be14:21
cjwatsonworst case you can sed the substvars file14:21
mlankhorstit should be enough14:22
argesxnox: do you mind if I review this merge? https://code.launchpad.net/~louis-bouchard/ubuntu/trusty/backuppc/backuppc-merge/+merge/20053614:22
cjwatsonI'd really prefer you didn't take that approach14:22
cjwatsonI'm not quite sure whether germinate will DTRT with that and it's confusing14:22
cjwatsonsed -i 's/libgl1-mesa-glx /libgl1-mesa-glx-lts-saucy /' debian/libglamor-ltss0.substvars after dh_shlibdeps should work14:23
cjwatsonanyway, have to go out14:23
jamespageOK - so I'm trying to figure out how to introduce a new libmysqlclient for mysql-5.6 into the archive without causing a transition14:49
jamespagethe mysql-5.5 client version is 18.0 and the mysql-5.6 client version is 18.1  - is it possible to have two such closely versioned libraries installed at the same time and everything still work?14:49
chrisccoulsonhi mlankhorst14:52
mlankhorstchrisccoulson: do you have some easy way to reproduce bug 126789314:52
ubottubug 1267893 in Oxide "Shutdown crash due to possible mesa race at startup" [Critical,Triaged] https://launchpad.net/bugs/126789314:52
chrisccoulsonmlankhorst, not unless you want to build oxide (which is pretty heavy) ;)14:52
zuldoko:  building now14:53
chrisccoulsonmlankhorst, and it obviously doesn't happen every time too14:53
geserjamespage: different packagename (and so-version) of the library or same?14:53
mlankhorstchrisccoulson: oh was curious if the patch Sarvatt attached fixes it14:53
chrisccoulsonmlankhorst, yeah, that patch will fix it. i can tell that without even trying it :)14:53
chrisccoulsonbut it doesn't fix the underlying cause, which is that the glx extension gets registered twice. not sure if there are other effects from that14:54
jamespagegeser, I was thinking libmysqlclient18 (for mysql-5.5) providing libmysqlclient.so.18 and libmysqlclient18.1 (for mysql-5.6) providing libmysqlclient.so.18.1 - just trying to think if there are any gotchas14:55
mlankhorstprobably not14:55
chrisccoulsonmlankhorst, so in that case, that patch should be fine14:55
mlankhorstmy guess is maybe some small extra allocation until close14:55
jamespagelike if I install the 5.6 client library, does all client use which to the 18.1 version14:56
geserjamespage: no, only those which link against it (which would be at first the mysql 5.6 client and server itself)14:57
jamespagegeser, well those statically link the client - but it sounds like it should be OK then14:57
geserjamespage: then for the client it would be even easier, but other programs which are linked against it request specifically libmysqlclient.so.18 (or libymsqlclient.so.18.1 if linked against mysql 5.6)14:59
jamespagegeser, excellent - thanks for confirming that behaviour15:00
jamespagethat's what I thought but it felt weird15:00
geserjust make sure that there is no file conflict between those two library packages15:00
jamespagegeser, ack15:00
geserjamespage: what about the -dev package? are you going to version it to not break linking/building with libmysqlclient-dev (from mysql 5.5)15:01
jamespagegeser, I think its OK for the -dev package from 5.6 to conflict with the 5.5 version - it only makes sense to ever have one installed15:02
geserjamespage: yes, but if mysql 5.6 builds libmysqlclient-dev now then you can only build other packages against 5.6 as it will replace libmysqlclient-dev from 5.5 in the archive15:03
jamespagegeser, mysql 5.6 would build libmysqlclient18.1-dev for now15:03
geserok, so no problem then15:04
jamespagehope not15:04
mlankhorstchrisccoulson: I was hoping for some official confirmation though, so I could merge the patch into mesa15:24
=== dames is now known as thedac
slangasekcaribou: Debian bug #706655> ok, can you provide a patch to the Ubuntu kexec-tools package to get rid of whatever bits are no longer required, so we can reduce the delta with Debian and I can close out that report?16:09
ubottuDebian bug 706655 in kdump-tools "kexec-tools: Please consider including integration for kdump auto-dumping" [Wishlist,Open] http://bugs.debian.org/70665516:09
caribouslangasek: ok, arges was pinging me about the kexec-tools merge earlier today16:09
caribouslangasek: I will see with him so we get rid of anything that is no longer needed16:10
=== Sweetsha1k is now known as Sweetshark
stgrabertseliot: bug 1259237 was automatically marked verification-failed, can you take a look?17:06
ubottubug 1259237 in nvidia-prime (Ubuntu Precise) "Hybrid graphics enablement in 12.04.4" [Medium,In progress] https://launchpad.net/bugs/125923717:06
stgraberwe're trying to round up the last few bits for 14.04.4 and there appears to be a dozen packages related to that bug which are targeted at 14.04.4, so the sooner we can have this sorted out the better17:07
tseliotstgraber: I worked on a fix (now in 14.04) and I attached a deb package in LP: #1268027 to see if that solves the issue. I can also upload to precise-proposed if you want17:09
ubottuLaunchpad bug 1268027 in nvidia-settings (Ubuntu) "nvidia-settings crashes on exit" [Medium,Triaged] https://launchpad.net/bugs/126802717:09
jjohansenjdstrand: since you where dealing with this earlier. I've answered bug 126854617:20
ubottubug 1268546 in apparmor (Ubuntu) "comm process name log entry truncated at underscore" [Undecided,New] https://launchpad.net/bugs/126854617:20
jdstrandjjohansen: ack, thanks17:21
jdstrandjjohansen: not saying you have to do it, but man, the ERRORS section of the man page is pretty out of date (I'm not sure I recall ever seeing a log message like the one in the man page :)17:22
jjohansenheh I bet, the man page needs some love17:22
jdstrandI can send a patch to the list17:22
sbeattieah, yeah, I bet.17:22
sbeattiejdstrand: that'd be great17:22
cjwatsonswitching libtool back to M-A: foreign as discussed last week17:33
cjwatsonI'll also work on testing the results of the debian-devel discussion so that we can have a more permanent solution17:34
cjwatson(though probably not today)17:34
infinitycjwatson: The proposed option 1 seemed san.17:44
infinitycjwatson: sane, too.17:44
cjwatsoninfinity: Yeah.  But I have only proven it correct, not tested it, as the saying goes.17:51
infinitycjwatson: Indeed.  It's obviously not harmful to native builds, but I guess some cross-testing (since that's what we're attempting to "fix") would be in order.18:04
cjwatsonYes.  Ideally I need an example of something that's actually trying to use /usr/bin/libtool ...18:06
cjwatson(That we haven't shotgunned yet)18:06
cjwatsonI'm not short of normal libtool examples18:07
infinitycjwatson: There are a large number of packages (though I can't think of one off the top of my head) that test for /usr/bin/libtool and then don't use it. :P18:10
infinitycjwatson: Those all worked fine in the M-A:foreign unsplit case, of course.18:10
infinityI don't actually know of a package that *calls* libtool, though there must be a few.18:11
dobeyinfinity: any library that is built with autotools using libtool, will probably call /usr/bin/libtool during the build18:50
infinitydobey: That's generally not true.18:50
infinitydobey: Anything properly libtoolized has its own local copy of libtool.m4, etc, and configure generates a fresh local libtool that ends up being called.18:51
infinityMost of the cases of /usr/bin/libtool usage I've seen have actually just been "-f /usr/bin/libtool" tests and then calling libtoolize. :P18:52
dobeyinfinity: the local libtool in the tree is a shell script, that can call /usr/bin/libtool, iirc18:54
jtaylormay I ask what the motivation for ppc64el is? it seems to divert a lot of manpower before the lts.18:56
jtaylorI don't recall it being explained on the mailing list18:56
infinity(For the record, we just did a test rebuild with a libtool that didn't ship /use/bin/libtool, and it proved your assertion false, I'm not just guessing)18:56
jtaylorI just found the debian report which was mostly negative to adding it18:57
infinityjtaylor: Which report is this?18:58
jtaylorprobably not negative, but I also saw no good reason to add it18:58
infinityAnyhow, the short answer is "to have Ubuntu run on POWER8 with IBM's recommended configuration".  No community members are being forced to do any work, so I'm not sure what the complaint would be.18:58
jtaylorjust discussion about ibm management :/18:59
jtaylorI'm not complaining, just curious18:59
jtaylorxnox: any news on when qemu arm64 will be fixed?19:02
infinityjtaylor: You want hallyn for that question, probably.19:03
jtayloroh sorry19:03
=== tkamppeter_ is now known as tkamppeter
hallynjtaylor: is qemu arm64 broken?19:10
hallynlater this week i will push a new qemu that shoudl have kvm support for qemu-system (but not the qemu-user-aarch64)19:11
hallynbut not today, hitting deadlines19:11
jtaylorhallyn: some of xnoxs arm64 changes in 1.5 were reverted in 1.7 merge19:13
jtaylorwe discussed it about a week ago here19:13
hallyni don't recall xnox making any changes, but if you're referring to the suse patchset then the latest estimate i know if would be a little over a month to get the new patchset upstream, and i'll pull it in as quick as i can after that19:18
hallynif there is another patch/fix you're referring to, then maybe i just messed up19:18
=== cr3_ is now known as cr3
=== cr3 is now known as Guest30001
=== fire is now known as hack
=== Guest24574 is now known as LoganCloud
=== cr3_ is now known as cr3
=== cr3 is now known as Guest76553
=== salem_ is now known as _salem
kentbI've got a package for sponsorship review if anyone would like to take a look. Thanks in advance: https://bugs.launchpad.net/ubuntu/+source/openwsman/+bug/126870720:40
ubottuUbuntu bug 1268707 in openwsman (Ubuntu) "Please upgrade openwsman in universe to latest upstream for Trusty (2.4.3)" [Undecided,New]20:40
argeskentb: well i'm piloting today so I'd be glad to look at it20:41
kentbarges: ok. thanks!20:41
argeskentb: the debdiff doesn't apply cleanly to the version already in trusty20:47
argeskentb: 2 out of 2 hunks FAILED -- saving rejects to file cmake/modules/FindRuby.cmake.rej20:47
kentbarges: ok. I know which patch that was20:48
kentbarges: I took it out when building the package...it is in patches/cmake-findruby.patch20:49
argeskentb: its not in the series file20:50
argesall that's there is the cmake-pythone-includes.patch20:51
kentbarges: sorry. I think I got mixed up here with what you were telling me.  When I originally built the package using the upstream source, there was a cmake-findruby.patch included in the 2.3.6 debian.tgz file.  That patch was no longer needed.  I removed it and also took it out of the series file so it would build.  Does that make sense?20:53
argeskentb: even with that patch removed, it still fails to apply your debdiff20:55
argeskentb: do this ' pull-lp-source openwsman trusty; cd openwsman-2.3.6; patch -p1 < patch.debdiff'20:55
argesthat fails20:55
argesfor me20:55
kentbarges: yeah. it just did for me too20:56
argeskentb: ok cool. Yea just fix that up, and re-attach that debdiff, and I'll give it another look. Thanks!20:57
kentbarges: will do. sorry about that20:59
argeskentb: its not a problem  : )20:59
jtaylorhallyn: http://launchpadlibrarian.net/157807141/qemu_1.6.0%2Bdfsg-2ubuntu3_1.6.0%2Bdfsg-2ubuntu4.diff.gz21:05
hallynjtaylor: yeah i don't think you can have that patch without having  qemu-user-aarch6421:06
jtaylorxnox: didn't you have something working at some point ^?21:07
jtaylorI think in irc he mentioned that that was dropped in the merge too21:08
infinityhallyn: The first half of that patch is specifically about arch combinations that don't need virt.21:31
infinityThe second half, sure, is about what might need virt, and that won't work until qemu-user works, but future proofing scripts never hurts.21:31
infinityBut the second part was wrong.21:32
infinitySince it needs to map arm64 to aarch64.21:32
hallyninfinity: are you saying the first half of the patch woudl still be appropriate?21:33
infinityhallyn: Yeahp.  And should also have amd64-x32 and x32-amd64 added.21:34
hallynif so, xnox could you send me a debdiff for the good part?  (or upload if you prefer, but lemme know and i'll push it to my git repo)21:34
infinity(And probably i386-x32/x32-i386 too... Starting to highlight how that little case doesn't really scale)21:35
hggdhmicahg: hi, someone from the DMB must accept the invite for ubuntu-uploaders to join bugcontrol21:42
kentbarges: okay. got it sorted this time. file is openwsman-latest.debdiff21:58
argeskentb: ok21:58
argeskentb: do you need two different changelog entries for this upload? or could they be combined?22:20
argeskentb: and i couldn't find this in debian, is it not included there yet?22:20
kentbarges: they can be combined.  debian does not have this yet, although I'm going to try and work on that on the side so we just sync in the future22:21
argeskentb: everything else looks good, and it builds fine for me22:23
argeskentb: uploaded22:24
kentbarges: awesome. thank you, sir!22:25
argeskentb: thank you for getting all this stuff updated22:25
kentbmy pleasure. it's been a good learning experience :-)22:25
argesand that ends my day22:26
arges@pilot out22:26
=== udevbot changed the topic of #ubuntu-devel to: Trusty Tahr Alpha 1 released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
cjwatsondobey: I've just gone through the local libtool in one of my projects, and there's no evidence that it would ever call /usr/bin/libtool.  It'd be extremely peculiar and pointless for it to be set up that way, so I doubt it ever happens.  I'm pretty sure any instances of this are failures to generate a package-local libtool script at configure time.22:28
Logan_When will apport start reporting to Launchpad by default in this cycle?22:30
Logan_Isn't it usually around Alpha 1 or something?22:30
jtaylordoesn't it now go to errors.ubuntu.com?22:34
Logan_jtaylor: But that's been disabled during development cycles. At some point.22:59
* Logan_ pokes pitti. ^22:59
sarnoldLogan_: it's a bit late/early for pitti, try again in six or seven hors..23:01
robert_ancellcjwatson, looking at out of date ttf-indic-fonts package (bug 958345). Don't suppose you can remember back to 2010 and know if any of the changes you made there are still relevant?23:03
ubottubug 958345 in ttf-indic-fonts (Ubuntu) "ttf-indic-fonts packages is not updated for last 2 years" [Wishlist,Triaged] https://launchpad.net/bugs/95834523:03
Logan_sarnold: Will do. :P23:04
robert_ancellI think the only change we need is the ttf-indic-fonts-core package which is just a default set to save install/download time?23:04
cjwatsonrobert_ancell: I'm pretty sure I've looked at that before and it's been quite a lot of work to merge - needs an equivalent of the -core stuff23:45
cjwatsonrobert_ancell: I can have another go at it this week23:45
ochosirobert_ancell: i managed to implement the XSetScreensaver timeout stuff we talked about yesterday in the gtk-greeter by the way (rev180). (it just won't work with nouveau for some reason :D)23:48

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