/srv/irclogs.ubuntu.com/2016/08/11/#ubuntu-devel.txt

tgm4883Can SRUs include the removal of features?00:07
RAOFtgm4883: Under extreme circumstances, yes.00:30
tgm4883RAOF: hmm, ok. I'll take a look at fixing this00:32
mwhudsonsigh, michael wait for the accepted mail before going to lunch00:51
=== JanC is now known as Guest62829
=== JanC_ is now known as JanC
noalternativeI am trying to compile fifth browser into a deb.  I am inexperienced, and I am trying to follow the hithear instructions & I am getting errors.  I have successfully compiled hithear, but I am trying to apply lessons to fifth browser.  Here are the hithear instruction.  I am at debuild -us -uc  https://wiki.debian.org/Packaging/Intro01:27
noalternativenow the errors http://pastebin.com/Ph5QPcWX01:28
sarnoldnoalternative: your first message was cut off mid-way through the URL01:28
sarnoldnoalternative: what does 'file' report on the fifth_0.4.orig.tar.gz file?01:29
noalternativehttps://wiki.debian.org/Packaging/Intro?action=show&redirect=IntroDebianPackaging01:30
noalternativeI am not sure what you mean.01:31
noalternativemaybe I named it wrong?  I downloaded this from source forge, not github01:32
noalternativetried to rename the file according to instructions.01:32
noalternativehttps://sourceforge.net/projects/fifth-browser/files/v0.4/01:32
noalternativeadmttedly the original was not a tar.gz01:33
noalternativeso I simply renamed it01:33
noalternativeis that what your getting at?01:33
noalternativeI just wanted to complie the browser for my personal use not as a package maintainer01:36
tgm4883noalternative: you can't just rename it01:36
noalternativeok01:36
tgm4883what was it previously?01:36
noalternativefifth-0.4.txz01:37
sarnoldtry something like fifth-_0.4_orig.tar.xz01:37
tgm4883sarnold: with the dash in there?01:38
sarnoldI wanted to see what 'file' thought the file is. it might be empty. (that happens). it might be an HTML error page from some stupid download site. or, it might be an xz'd file rather than gzipped file :)01:38
sarnoldtgm4883: nah, probaly better withuo the dash01:38
sarnoldwow01:38
sarnoldhow long until tab-complete can just type my thinking for me.. not soon enough01:38
noalternativehttp://pastebin.com/KA1nVLzY01:43
noalternativeIt liked the original name I think.01:44
tgm4883noalternative: you should name it fifth_0.4.orig.tar.xz01:44
sarnoldI detest the "rename the tarball" step. so. annoying.01:44
tgm4883I agree01:44
sarnoldbecause I can never guess the name to use correctly on the first try, I always wind up having to copy-and-paste the demanded name from this error message :)01:45
sarnold(you've seen my typing, this shouldn't be a surprise :)01:46
=== juliank is now known as Guest40989
=== juliank_ is now known as juliank
noalternativeWe made some headway, but it ultimaely retruned errors.  I can't cut and paste all of it from my terminal because my terminal stops before the command was given.01:52
noalternativeIs there a log I can paste?01:53
noalternativeor maybe a specific part of the terminal like the part about errors.01:53
noalternativeHere are errors from a file called fifth_0.4-1_amd64.build02:01
noalternativehttp://pastebin.com/TeCS4BWC02:02
infinitytgm4883: You absolutely can just rename orig tarballs.03:51
tgm4883infinity: you can just rename an orig tarball from a .tar.xz to .tar.gz?03:51
infinitytgm4883: Oh.  No.  I missed the context, I guess. ;)03:52
tgm4883infinity: hah yea, I didn't think you could do that. I guess I should have said can't just change the extension03:53
tgm4883although you kinda can, if you know what you're doing03:53
infinitytgm4883: Not in a way that keeps dpkg happy and the file unchanged. :P03:53
infinityPick one.03:53
tgm4883infinity: well in this case, we had to change .txz to .tar.xz03:54
infinity'tar xf' autoguesses these days, but dpkg-source ain't having none of that modern nonsense.03:54
tgm4883although maybe we didn't need to do that and just rename it to the proper format03:54
infinitytgm4883: Oh, sure, tgz == tar.gz, etc, though.03:54
tgm4883yep03:55
=== xavigarcia_ is now known as xavigarcia
=== snkcld_ is now known as snkcld
=== czchen_ is now known as czchen
=== tgm4883_ is now known as tgm4883
=== lfaraone_ is now known as lfaraone
=== elijah_ is now known as elijah
=== tjaalton_ is now known as tjaalton
=== sinzui_ is now known as sinzui
=== popey_ is now known as popey
LaneyMirv: trying a test build of ffmpeg ...10:08
Laneycross your toes10:08
=== hikiko is now known as hikiko|ln
* sil2100 crosses his toes too10:16
* Mirv crorres toes and fingers10:30
cjwatsonMirv: so ... would you be sad if I just fixed that click test rather than approving your hack, given that I know how to do it and it's fairly easy having spotted the problem?10:34
cjwatsonMirv: https://code.launchpad.net/~cjwatson/click/new-debsig-policy-url/+merge/30265210:42
Mirvcjwatson: terrible! (thank you)10:48
Mirvreplacing the silo MP with that10:49
Laney'k, that built10:49
* Laney copies10:49
cjwatsonMirv: thanks; I tested it enough locally that I think it's good10:50
MirvLaney: \o/10:50
Laneygizza builder, launchpad11:00
seb128hum, does anyone has an idea what's wrong on bug #1611256?11:39
ubottubug 1611256 in ubuntu-release-upgrader (Ubuntu) "X to Y upgrade fails with gconf2 depends on python3:any; however: Package python3 is not configured yet." [Critical,Confirmed] https://launchpad.net/bugs/161125611:39
seb128xenial to yakkety upgrades are hitting that11:39
seb128"dpkg: dependency problems prevent processing triggers for gconf2:11:40
seb128 gconf2 depends on python3:any; however:11:40
seb128  Package python3 is not configured yet."11:40
dokoapw, when do you plan to upload the updated kernel to y?11:56
xnoxdoko, in two weeks when he is back from vac?11:58
xnox=)11:58
ogra_they allowed him vac ?!?11:58
ogra_carzy kernel team ...11:58
ogra_*crazy too11:58
=== _salem is now known as salem_
dokoLocutusOfBorg, what are you saying in 1608129? build it once without the tests, and then reenable the tests?13:19
LocutusOfBorgor build-conflict with itself13:19
LocutusOfBorgyour solution seems good too13:20
LocutusOfBorgBTW I already asked ginggs but you might want to upload this patch http://paste.ubuntu.com/23021246/13:20
loladiroHi folks, hope this is the right channel. I’ve been looking for the `dash` debug symbol package, but been unable to find it. Any pointers?13:24
xnoxloladiro, https://wiki.ubuntu.com/Debug%20Symbol%20Packages did not help?13:25
loladiroNope, tried that, but neither dash-dbg nor dash-dbgsym seemed to exist13:25
=== hikiko|ln is now known as hikiko
xnoxloladiro, yeah weird.13:29
xnoxpitti would be the person to ask, but I don't see him online atm (holidays?!)13:29
cjwatsondash has a very old-fashioned debian/rules that doesn't use debhelper, so that'll be why13:29
xnoxah13:30
xnoxtru, dh_strip is not called.13:30
loladiroSo, no debug symbols for me then :(?13:30
cjwatsonit should be pretty easy and quick to build locally13:30
cjwatsonnot a complex package13:30
loladiroYeah, absolutely13:30
loladiroI’m not really interested in dash actually, but was just using it as a test case for some automation - guess I picked the wrong thing ;)13:31
loladiroShould I file some sort of bug report so this doesn’t get forgotten for future versions, or is this known and will be fixed anyway13:32
cjwatsonI think it would be reasonable to file a bug asking for debug symbols (though a solution-neutral bug - it may be easier to just bodge the one or two necessary lines into debian/rules than to convert the whole thing to debhelper, as a downstream)13:34
cjwatsonhttps://bugs.launchpad.net/ubuntu/+source/dash/+filebug13:34
LocutusOfBorgI would open a bug in Debian13:36
cjwatsonthat's only a good idea if you can come up with a reasonable way to make it applicable to Debian13:37
loladiroAlright, bug filed. Appreciate the quick response folks.13:38
cjwatsonhttp://debug.mirrors.debian.org/debian-debug/pool/main/d/dash/ similarly doesn't exist, so that may be such an argument13:39
LocutusOfBorgyes, the strip is done in a really obscure way13:55
LocutusOfBorghttps://sources.debian.net/src/dash/0.5.8-2.3/debian/rules/13:55
LocutusOfBorgconverting into some new format will fix the issue for both OS13:55
* xnox moved IRC from a US vps to the one in docklands, so much better =)14:36
xnoxhttp://memesvault.com/wp-content/uploads/Dog-Meme-Wow-Wallpaper-03.jpg14:36
rbasakstgraber: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/161211614:47
ubottuLaunchpad bug 1612116 in juju-mongodb (Ubuntu) "please remove juju-core-1 and juju-mongodb packages from yakkety" [Undecided,New]14:47
xnoxrbasak, whilst juju-2 is still saying that it may not be used for production use?!14:48
xnoxhow does one connect and/or deploy things with juju in yakkety then?14:48
stgraberxnox: I just commented in the bug that I don't think we should do this until Juju 2.0 is released and stable14:49
* xnox hits F514:49
rbasakxnox: don't ask me!15:02
setuidIf I've pulled a package 'bar' with a BD on foo, which then uses 'import foo' in its code, but there's no RD on 'foo', removing 'foo' will break 'bar'. Does a BD incorporate foo.py into bar? Or did I just find a bug?15:38
LocutusOfBorgb-d don't incorporate runtime dependencies for python packages15:49
LocutusOfBorgusually they are listed in setup.py install_requires15:49
LocutusOfBorgand the parses and replaced with debian dependencies into python:Depends substvar that is evaluated during build by dh_python2 and replaces the dependencies with some runtime stuff15:50
LocutusOfBorgbut if install_requires is not available... the maintainer has to list them in runtime-Depends15:50
LocutusOfBorgfor libraries is easier15:51
setuidLocutusOfBorg, So sanity check this for me; python-keystone has a BD on python-ldappool, and keystone/core/core.py does an 'import ldappool', but installing python-keystone doesn't install python-ldappool15:51
setuidSo installing python-ldappool on its own will satisfy that r-d, but will break when removed (no deps depend on it)15:52
setuidsorry, keystone/common/ldap/core.py15:52
setuidimports ldappool15:52
setuidthere's a changelog entry showing the b-d being added, but they missed the r-d15:53
mterryseb128: can you reject a lightdm upload I just made to vivid accidentally?  Got my dput arguments in the wrong order and for some reason haven't disabled 'ubuntu' as the default location15:58
mterryOr any archive-admin I guess really  :)16:00
infinitymterry: Done.16:05
mterryinfinity: thanks -- I've now fixed my dput too16:09
LocutusOfBorgsetuid, you seems to be right, setup.py has no install_requires keyword, so the dependencies are not picked up (and nor explictly listed on Depends: of the runtime package)17:03
ahoneybuncyphermox: you work on the slideshow right?21:12
ahoneybunfor the installer21:12
cyphermoxahoneybun: yes21:25
ahoneybunare the sizes in the slideshow.conf strict?21:26
ahoneybunlike it HAS to be that size?21:26
ahoneybunreason I'm asking is because QtWebkit is broken in Qt4 or something and we are making our slideshow in qml21:27
ahoneybunnot html21:27
bdmurrayjbicha: for bug 1063019 you could use the Errors bucket for the crash as a test case21:39
ubottubug 1063019 in gnome-contacts (Ubuntu Xenial) "gnome-contacts-search-provider crashed with signal 5 in contacts_ensure_eds_accounts()" [Medium,In progress] https://launchpad.net/bugs/106301921:39
ahoneybunheyo our installer slideshow is broken with 1 week before freeze22:09
juliankWould be nice if the apt 1.2.14 SRU in the queue would be processed at some point :)22:09
bdmurrayjuliank: which release is that for?22:25
juliankbdmurray: xenial, the 1.2.X series is the stable APT series for xenial22:25
juliankbdmurray: In case you're wondering: The release is from Jun 22; it was supposed to be synced a month ago or so, but getting the new APT with the same bugfixes into yakkety was a bit complicated, so it was delayed some time.22:32
juliankThere will be a 1.2.15 update at some point in the future merging bugfixes from the 1.3~pre1, 1.3~pre2, 1.3~pre3, 1.3~rc1 releases; but not in the immediate future.22:33
juliank1.2.14 basically  brings us up to 1.3~exp2 in terms of important bug fixes22:33
juliankoops, ~exp322:34
juliank1.2.15 will then fix the issues with ZFS module stuff not allowing you to autoremove kernels, amongst other things22:35
juliank(That will be an awful release to do, so many changes to look at and see what should be backported/cherry-picked)22:37
juliankAlso need to wait for pitti so we can set up autopkgtests for that stuff before we upload it...22:39
juliankOh dear, I also have to update the 1.0.9.8 series for Debian stable ...22:57
jbichabdmurray: thanks, I see that there's a lot of errors on trusty for that gnome-contacts bug, so do you want to accept the sru for trusty too now (just uploaded)?22:57
Term1nalQuestion: https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-5696.html23:08
ubottunet/ipv4/tcp_input.c in the Linux kernel before 4.7 does not properly determine the rate of challenge ACK segments, which makes it easier for man-in-the-middle attackers to hijack TCP sessions via a blind in-window attack. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5696)23:08
Term1nalWhat does DNE stand for in that listing?23:08
sarnoldTerm1nal: does not exist23:09
sarnoldTerm1nal: it means that package doesn't exist in that release23:09
Term1nalAh.23:09
Term1nalSo... DNE is saying, what... patch not needed for that specific issue?23:10
sarnoldright; for example, the linx-lts-trusty package doesn't exist in trusty, 16.04, 16.10, etc..23:10
Term1nalSo is this page effectively saying that there's no fix needed for 16.04?23:12
sarnoldTerm1nal: the 'linux' package on 16.04 is marked 'needed'23:12
Term1nalah23:13
sarnoldTerm1nal: the linux ones are far more complicated than the other packages.. you've got to know which source package generated the kernels you're using in order to really read the page23:13
Term1nalCan't wait until the DDoS kiddies figure out how to exploit this and sell it as a service O.O23:13
sarnoldhey great business idea!23:14
sarnoldI mean23:14
Term1nal:P23:14
sarnoldyeah that'll be trouble...23:14
Term1nalI guess what I'm trying to figure out.. is a currently up-to-date patched 16.04 machine vulnerable to this CVE still or?23:15
Term1nalCause, sure, it's fixed in 4.7 kernel. But obviously we're not using 4.7 out of the box.23:15
sarnoldit's certainly forced to to think about TCP slightly differently; 2^32 gaurantees are ...  not impressive. with so many machines on the internet moving so many packets of data each second, 1/2^32 happens all the time..23:15
sarnoldTerm1nal: you're affected. We expect the fix to land around august 2723:16
Term1nalNeato, that's a nice specific timing.23:16
sarnoldthe kernel team works on a three-week cadence; patches in one portion, testing in another portion, publish on a date; it normally works out pretty predictably23:17
Term1nalLet's just hope PoCs aren't released before then and used to start the next poodlecorp23:17
Term1nalOdd though, isn't it typical to have these sorts of CVEs announced once a patch is ready to go?23:20
sarnoldwe do, we release USNs, e.g. http://www.ubuntu.com/usn/usn-3055-1/23:21
sarnoldthis issue came out at an inconvenient time to fit into the release that was released last week, so it's in the current cycle, which should be released in ~two weeks..23:22
sarnoldwe also mail our USNs to a moderate-traffic mail list https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce23:23
Term1nalI get those USNs through RSS23:26
juliankHmm, I messed up the apt 1.3~rc1 a bit - I did not consider the ubuntu-specific config file in the packaging. I'll fix this tomorrow.23:30
juliankAnd what's going on with all those dlsym(acl_set_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_set_file?23:31
juliankWell, the config stuff kind of happens when you switch to a new build system and rewrite the packaging rules.23:32
=== StevenK_ is now known as StevenK
TheMusoc23:43
TheMusowhoops23:43
Term1nalOh, please package latest Golang toolchain for 16.04, thanks! <323:53
Term1nalHave fun you hard workin' folks23:53

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