/srv/irclogs.ubuntu.com/2017/07/26/#ubuntu-devel.txt

tsimonq2Logan: Hey, so what did you find out with kanatest?02:10
=== giraffe is now known as Guest17892
=== AdmWiggin is now known as tianon
Unit193Hey, so after seeing some tests that should not be failing, I ran  autopkgtest -U --apt-pocket=proposed -- lxc autopkgtest-artful  on ruby-net-scp and that passed for me.07:01
Unit193http://autopkgtest.ubuntu.com/packages/r/ruby-net-sftp/artful/amd64 also shouldn't have failed.07:01
Unit19334 tests, 66 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications07:03
Unit193100% passed07:03
mwhudsonnice07:04
Unit193I know because I prepped several uploads in Debian for ruby-net-ssh. :P07:05
Unit193mwhudson: Should I ask where you are?  You seem to always be alive in the 'dead zone'.07:08
Unit193Is there a way to get them testing against -proposed?07:11
ginggsUnit193: the tests can be triggered against additional packages07:15
Unit193ginggs: ruby-net-scp/ruby-net-sftp need --apt-pocket=proposed=src:ruby-net-ssh07:16
ginggsUnit193: retrying07:20
Unit193Thanks!07:20
Unit193I understand I don't have permissions for it, but how?07:20
ginggsUnit193: do you see the links for retrying (they look like recycle icons) on  http://autopkgtest.ubuntu.com/packages/r/ruby-net-sftp/artful/amd64 ?07:22
Unit193ginggs: I did, but since it needed a package from -proposed I thought the fine tuning would be different.07:24
ginggsUnit193: ok, so look at the URL of one of the retry links, then add '&trigger=ruby-net-ssh%2F1%3A4.1.0-1'07:24
Unit193That's officially 'fun'.  Thanks.07:25
mwhudsonUnit193: nz07:49
mwhudsonyes, retry url hacking is fun07:50
mwhudsonyou can also add &all-proposed=107:50
Unit193Ah.  I'm not core nor motu (just packageset), so not (yet) really able to useit.07:52
LocutusOfBorgmwhudson, what is the last thing blocking python3.6?07:52
LocutusOfBorgUnit193, I stole your wine-development merge07:52
Unit193I had one?07:53
Unit193Thanks, LocutusOfBorg!07:53
LocutusOfBorgyou asked me to sponsor that for you07:53
Unit193Good enough. :)07:53
LocutusOfBorggo cmake, go07:57
mwhudsonLocutusOfBorg: yara ftbfs on armhf08:21
LocutusOfBorgack08:21
mwhudsonLocutusOfBorg: which i am hacking almightily now08:21
LocutusOfBorgI'm fixing the last gtk-d failures08:21
LocutusOfBorgoh wonderful08:21
mwhudsonoh boy this code really expects aligned access to work08:27
mwhudsonlike, a lot08:44
mwhudsonxnox: what do you think about removing the existing yara binaries on armhf? (and rdeps i guess)08:57
mwhudsonxnox, slangasek, doko: sent an update to ubuntu-devel about yara09:13
=== nikow1 is now known as nikow
LocutusOfBorgcan I ask for a little perl advice?10:34
LocutusOfBorgLaney, the debhelper merge is ready, but I fail to parse the Ubuntu version10:34
Laneyyou what?10:34
LocutusOfBorgperl -e ' undef $/; foreach (@ARGV) { open (IN, $_) or die "$_: $!"; $file=<IN>; close IN; if ($file=~m/=head1 .*?\n\n(.*?) - (.*?)\n\n/s) { my $item="=item $1(1)\n\n$2\n\n"; if (" dh_installmanpages " !~ / $1 /) { $list.=$item; } else { $list_deprecated.=$item; } } } END { my $recommended_compat = 10.6.4ubuntu1; $recommended_compat =~ s{\..*}{}; while (<STDIN>) { s/#LIST#/$list/; s/#LIST_DEPRECATED#/$list_deprecated/;10:35
LocutusOfBorgs/#RECOMMEDED_COMPAT#/$recommeded_compat/; print; }; }' dh_auto_build dh_auto_clean dh_auto_configure dh_auto_install dh_auto_test dh_bugfiles dh_builddeb dh_clean dh_compress dh_fixperms dh_gconf dh_gencontrol dh_icons dh_install dh_installcatalogs dh_installchangelogs dh_installcron dh_installdeb dh_installdebconf dh_installdirs dh_installdocs dh_installemacsen dh_installexamples dh_installgsettings dh_installifupdown10:35
LocutusOfBorgdh_installinfo dh_installinit dh_installlogcheck dh_installlogrotate dh_installman dh_installmanpages dh_installmenu dh_installmime dh_installmodules dh_installpam dh_installppp dh_installudev dh_installwm dh_installxfonts dh_link dh_lintian dh_listpackages dh_makeshlibs dh_md5sums dh_missing dh_movefiles dh_perl dh_prep dh_shlibdeps dh_strip dh_systemd_enable dh_systemd_start dh_testdir dh_testroot dh_ucf dh_update_autotools_c10:35
LocutusOfBorgonfig dh_usrlocal | \10:35
LocutusOfBorgpod2man --utf8 -c Debhelper -r "10.6.4ubuntu1" --name="debhelper" --section=7  > debhelper.710:35
LocutusOfBorghttps://launchpadlibrarian.net/330668177/buildlog_ubuntu-artful-amd64.debhelper_10.6.4ubuntu1_BUILDING.txt.gz10:35
LocutusOfBorgbad copy-paste10:35
LocutusOfBorgforcing VERSION=10 "fixes" it, but it is hacky and bad10:35
LocutusOfBorgsolution is to drop that ubuntu in recommended compat, right?10:35
LocutusOfBorgthe question is: should I revert somewhere this? https://anonscm.debian.org/git/debhelper/debhelper.git/commit/?id=d2ca3a7f964eb915035c4526baa92325d3f6dbd710:37
LocutusOfBorg$$recommended_compat =~ s{\..*}{};10:37
LocutusOfBorgthis is what fails10:37
Laneyis it calculating that variable wrong?10:38
LocutusOfBorgthe problem is that rege10:40
LocutusOfBorgwith the debian version 10.6.4 is returning "10"10:40
LocutusOfBorgwith the ubuntu version, 10.6.4ubuntu1 it returns "can't parse foobar"10:40
LocutusOfBorgBareword found where operator expected at -e line 1, near "10.6.4ubuntu1"10:40
LocutusOfBorgso, this code "$recommended_compat =~ s{\..*}{};" is having issues10:41
LocutusOfBorgFWIW doing this VERSION=$(shell dpkg-parsechangelog -SVersion |cut -f 1 -d "u") also works, because it strips the "ubuntu" part from version10:43
LaneyLocutusOfBorg: Looks like it should be quoted?10:43
Laneymy $recommended_compat = 10.6.4ubuntu1;10:43
cjwatsonYeah that probably just wants to be my $$recommended_compat = q($(VERSION));10:44
cjwatsonor similar10:44
cjwatsonhmm, do I have upstream commit access10:46
cjwatsondoesn't look like it10:49
LocutusOfBorgsorry, bad connection sigh10:54
LocutusOfBorgseems not good, man ./debhelper.7 shows: "#RECOMMEDED_COMPAT#" instead of 1010:55
cjwatsonI'm preparing a patch10:56
LocutusOfBorgack, do you want to directly upload debhelper? I can give you the merge, or you can just grab from the ppa above10:56
cjwatsonnot especially10:57
cjwatsonI'll send a patch to Debian10:57
LocutusOfBorgok thanks10:58
LaneyThere's some "recommeded" / "recommended" confusion too.11:02
cjwatsonyes, I'm fixing that11:04
LaneyNod11:05
LocutusOfBorgso also debian manpages should be bad11:05
LocutusOfBorgyes lol11:06
cjwatsonindeed11:10
cjwatson... and a lack of s///g ...11:14
cjwatsonLocutusOfBorg,Laney: https://bugs.debian.org/86978011:24
ubottuDebian bug 869780 in debhelper "debhelper: recommended compat version substitution is totally broken" [Normal,Open]11:24
cjwatsonfeel free to cherry-pick or whatever11:25
Laneycjwatson: Ta11:36
LaneyLocutusOfBorg: You going to take that?11:36
rbalintjuliank: are you ok with the smaller patch against apt in LP: #1690980 ?12:11
ubottuLaunchpad bug 1690980 in OEM Priority Project "unattended-upgrades does not block shutdown of system, as it is designed to" [Critical,Triaged] https://launchpad.net/bugs/169098012:11
LocutusOfBorgLaney, will upload in ppa12:12
LocutusOfBorgsorry I was @lunch12:12
* Laney nod12:12
juliankrbalint: Tech side is OK, but I'm thinking about the commit message summary. It's a bit long, does not mention the timeout, and mentions shutdown, whereas it's any service stop that is affected?12:14
juliankGracefully terminate processes apt-daily-upgrade.service on stop?12:15
LocutusOfBorgLaney, do you want to do some testing before I upload to Ubuntu? I admit, I'm worried about it :)12:15
rbalintjuliank: thanks that's clear and short12:16
juliankoh, it's missing a word12:16
rbalintjuliank: so sure, feel free to change it12:16
juliankGracefully terminate processes *in* apt-daily-upgrade.service on stop12:16
rbalintdo you plan landing 1.2.25 in xenial in the near future?12:17
juliankLet's go with "Gracefully terminate process when stopping apt-daily-upgrade"12:18
juliankrbalint: Hey, I'm waiting for 1.2.24 since 5 weeks or so to enter proposed. 1.2.25 is basically scheduled now-ish, after the next 1.5 beta (and 1.4.8)12:19
juliankI did not yet push even 1.4.7 to zesty, as I'm waiting for 1.4.6 to be approved first12:20
juliankAnd AFAIUI, updates are supposed to be in newer suites before older ones.12:20
juliankSo, the plan would be to have the service fix in 1.5~beta2, cherry pick to a 1.4.8 release, and cherry-pick that and the stuff from 1.4.7 into 1.2.2512:22
julianksee bug 1702326 for the changes in 1.4.712:23
ubottubug 1702326 in apt (Ubuntu Zesty) "New microrelease 1.4.7 for zesty" [Medium,Triaged] https://launchpad.net/bugs/170232612:23
juliank(basically minor (in size) fixes to the http method to correctly handle some server responses)12:24
rbalintjuliank: ok, thanks!12:24
juliankThere are no other fixes scheduled for 1.4.8 at the moment, so that would be just the service change :)12:24
juliankOh, I see DonKult has some fixes in his repo he did not push yet12:27
rbalintmvo: i'm fairly confident in the u-u PR, maybe could you please take a look again?12:29
mvorbalint: sure, let me do that now12:29
LocutusOfBorgmapreri, diffoscope: error: unrecognized arguments: --thisflagdoesntexistandwontexist12:34
LocutusOfBorgdiffoscope on s390x seems sad12:34
LocutusOfBorghttps://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/d/diffoscope/20170726_103422_64cc6@/log.gz12:34
mapreriLocutusOfBorg: that's not an error12:35
mapreriindeed that autpkgtest test passes12:35
mapreriand yeah, that thing is another failure that is fixed by another commit I forgot about…12:35
mapreri(btw, that test is there to test that if you pass an invalid argument diffoscope exists with code 2)12:35
LocutusOfBorgack12:37
LocutusOfBorgmwhudson, why python3-defaults is not pointing at the right python? I'm lost12:37
LocutusOfBorghttps://launchpad.net/ubuntu/+source/python3-defaults/3.6.1-0ubuntu212:37
LocutusOfBorgit should be 3.6.212:37
LocutusOfBorgsagemath is picking up Get:10 http://ftpmaster.internal/ubuntu artful-proposed/main amd64 libpython3-stdlib amd64 3.6.1-0ubuntu2 [7012 B]12:37
LocutusOfBorgand not sure if this is the reason for its failure12:38
mapreriLocutusOfBorg: https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=7e16cecb98ec2e874da4f3ea291e276602852dcd12:38
mapreriand probably will need https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=fe57c99828060ae77af2784961d47beb44eb74f5 as well..12:38
LocutusOfBorgI uploaded with the first patch, since I can't test s390x12:39
mapreriit's weird that only s390x failed12:40
maprerithat thing failed in debian as well, on amd6412:40
LocutusOfBorgLaney, https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+packages12:49
LocutusOfBorgdo you want to test it out? :p12:49
LocutusOfBorgI uploaded wxwidgets3.0 on that ppa, lets see if it works or not12:51
juliankrbalint: I forgot to tell you, I committed it in https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=78bc10d4702b30b46d802294ac43cffc34d9c43112:55
juliankrbalint: Feel free to do a 1.5~beta1ubuntu1 now if you want it now, 1.5~beta2 comes in a few days12:56
juliankWell, it might come today, but I'm not sure what DonKult is up to exactly12:56
ogra_arges, hmm, how did my name end up in that livecd-rootfs changelog ? i cant remember ever touching any of this13:00
argesogra_: I didn't put it there...13:00
ogra_arges, well, you upploaded it13:02
ogra_(but i see, seems rcj assembled it)13:02
ogra_well, not that important anyway ... i was just wondering how my name got on there13:03
argeshttps://launchpad.net/ubuntu/+source/livecd-rootfs/2.408.13 looks correct, I think my 'sru-release' script seems to have printed incorrect info on the bug13:04
ogra_yeah, that was the trusty sru13:04
ogra_not the xenial one :)13:04
ogra_https://launchpad.net/ubuntu/+source/livecd-rootfs/2.208.1413:05
argesah, yea I think rcj included other patches in his upload13:06
ogra_(thats fine, but i still cant remember ever touching any vmdk, ova or vargrat stuff in my life ;) )13:13
ogra_(at least not in livecd-rootfs ... but perhaps my memory fades :P i'm getting old ... :)  )13:13
argespkkk~.13:25
arges~13:25
arges.~.13:25
argeswhoops13:26
LocutusOfBorgarges, this seems the command used to kill a stuck ssh connection, correct?13:29
rcjogra_: I pulled in contributions to livecd-rootfs in the utopic->xenial timeframe for that trusty upload to support build of cloud-images.  I kept all the contributors names.  I can't recall which you contributed to but it must have been in there ;)13:29
=== dja_ is now known as dja
rbalintjuliank: thanks, in a few days is ok i would not create a delta for a few days in in this case13:42
xnoxmwhudson, it is landing =)13:59
xnoxi'm sure it will spill over two publications and screw people up for an hour or so.13:59
dokoyeah, got 56 migration mails ...14:09
zhongjunnacc: hi15:11
nacczhongjun: hello15:12
zhongjunnacc: I got this error in ubuntu 16.04 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84755715:13
ubottuDebian bug 847557 in nfs-kernel-server "/usr/sbin/exportfs: exportfs cannot handle IPv6 addresses" [Important,Open]15:13
zhongjunnacc:  This bug has been fixed in nfs-kernel-server version 1:1.3.4-115:13
zhongjunnacc: Could we backport the "fix" in  nfs-kernel-server version 1:1.2.815:14
zhongjunnacc: Could we backport the "fix" in  ubuntu 16.0415:16
nacczhongjun: do you know the specific fix?15:16
zhongjunnacc: Actually, I am not sure about the specifix fix15:17
nacczhongjun: if you want it in xenial-backports, you can request it (https://wiki.ubuntu.com/UbuntuBackports). But for a bugfix to go into xenial-updates, you have to know what the bugfix is (https://wiki.ubuntu.com/StableReleaseUpdates).15:18
zhongjunnacc: Is there a fast way or some links that I could make me find the specific fix quickly?15:22
zhongjunnacc: Is there a fast way or some links that it could make me find the specific fix quickly?15:22
rbasakzhongjun: https://en.wikipedia.org/wiki/Bisection_(software_engineering) maybe?15:26
nacczhongjun: you would need to look at what was fixed in teh debian upload. More than likely it's an upstream fix (not a debian-specific one). Generally, no, there's not a 'quick way'15:26
rbasakOr yeah, look through the commit messages and changelogs.15:26
zhongjunrbasak, nacc: Thanks,  if anyone familiar with exportfs  IPv6, please tell me15:29
roaksoax_4/win 315:35
dokoxnox: do you know if LocutusOfBorg will do the perl merge and start the perl transition?15:52
xnoxno idea.15:52
dokook, then I'll do the merge15:54
Laneywhy not wait and ask?15:55
ginggsdoko, Laney: lemme ask him15:58
maprerilast I heard from him he said "I won't until python is good"16:06
LocutusOfBorgdoko, why do you think this is a merge?16:08
LocutusOfBorgI'm uploading a no-change rebuild in a ppa16:08
dokowas zlib updated in Debian?16:08
LocutusOfBorgsome of the patches I'm carrying are fixed in new perl, so probably a plain sync will work16:09
LocutusOfBorgno doko it wasnt16:09
LocutusOfBorgbtw I just uploaded debhelper, for sure I would wait a little bit before syncing perl16:09
LocutusOfBorguploaded in my ppa16:09
dokoLocutusOfBorg: so you are handling this?16:09
LocutusOfBorgif you want to help, please help :)16:09
LocutusOfBorgI can do the sync/merge, but for sure I can't handle perl alone16:10
LocutusOfBorg(I was waiting for python3-defaults to land)16:10
LocutusOfBorgdoes this sound ok for you?16:11
LocutusOfBorgsync/merge in one hour or two16:11
LocutusOfBorgand then do the rebuilds tonight/later16:11
dokoI only want to make sure that it's done mid next week, before I start with gcc-716:11
LocutusOfBorgthis sounds like a good plan16:12
LocutusOfBorgI'm just worried about the testsuite16:12
LocutusOfBorgbut  yeah, lets sync and start rebuilds in one hour16:12
LocutusOfBorgbuilders are bad now, amd64 is sloooow16:12
LocutusOfBorgnot sure what they are building, hopefully they will be green soon16:13
LocutusOfBorgwe still have that perl "hey don't build arch:all before arch:any or rmadison will be sad" stuff16:13
LocutusOfBorgso, I want amd64 ready before syncing16:14
dokowhich ppa?16:14
LocutusOfBorg~costamagnagianfranco/locutusofborg-ppa16:14
LocutusOfBorgppc64el started, so I guess we can just wait for it16:15
LocutusOfBorgtest failures were common16:15
LocutusOfBorgdoko, can you please bump debhelper priority? https://launchpad.net/ubuntu/+source/debhelper/10.6.4ubuntu116:19
LocutusOfBorgI don't want the egg and cichken issue16:19
* LocutusOfBorg chicken 16:19
jbichatumbleweed: reverse-depends doesn't seem to handle '-r testing' or '-r buster'16:21
LocutusOfBorgjbicha, would be nice to see also -r artful-proposed, to understand which stuff has already been rebuilt on top of the new library :)16:22
LocutusOfBorgthanks to whoever did it16:25
cjwatsonLocutusOfBorg: security updates, but it'll get there in a bit16:38
ginggswhy would objcopy fail to extract debug info on the buildds when FPC calls it, but works fine if I call it with the same arguments from a build script?16:47
LocutusOfBorgcjwatson, I mean, thanks to whoever bumped the priority of perl and debhelper :)16:48
LocutusOfBorgno problem cjwatson, breaking the whole world can wait some hours I hope :p16:48
cjwatsonnot I16:48
LocutusOfBorgdoko, the plain sync seems to have worked on ppc64el16:55
LocutusOfBorgso, lets wait for builders to settle down and I'll force-sync16:55
* LocutusOfBorg leaves16:57
LocutusOfBorgcheers!16:57
bluefoxxxxwhich channel for help with community documentation issues?  Just #ubuntu?17:03
tsimonq2bluefoxxxx: I assume #ubuntu-doc?17:04
bluefoxxxxthanks17:04
tumbleweedjbicha: ah, I think the distro-info-data was out of date, re-running it now17:06
LocutusOfBorgdoko, sync?17:27
LocutusOfBorgI'm doing it, done17:30
tumbleweedjbicha: fixed18:18
jbichathanks!18:19
=== sergiusens_ is now known as sergiusens
tsimonq2slangasek, infinity, jbicha: Hey there! I'll be helping with the Qt transition while mitya57 is off on vacation, what's the status of getting the Ubuntu Touch packages removed from the archive? If a new Qt version is uploaded, it probably won't migrate from -proposed unless those are removed...18:51
slangasektsimonq2: from my perspective, xnox was driving these removals; I'd check with him on status18:57
tsimonq2slangasek: Thanks.18:58
dokoLocutusOfBorg: I'm uploading the first batch of perl rebuilds19:47
naccmdeslaur: fyi, apache2 2.4.27-3 is now in unstable. I'll merge up to that, which should be past the version that declares http2 stable.20:14
mdeslaurnacc: great, thanks20:17
mwhudsonxnox: \o/21:50
LocutusOfBorgdoko, ack thanks22:37
LocutusOfBorgI'll rekick some stuff22:43
Unit193infinity: I don't suppose you're online?22:56
infinityUnit193: I might be.22:57
Unit193I was wondering why specifically in https://launchpad.net/ubuntu/+source/ruby-specinfra/2.66.0-1ubuntu1 you added that, I don't see it in the requirements and autopkgtests pass without it.22:57
Unit193Based on grep, I do see how one might use it, but I'm wondering 1. How you saw that.  2. If the build-dep is still needed.22:57
infinityUnit193: If I recall, it actually showed us as failures in rdeps.22:58
Unit193I wondered if that was the case, if it were I wouldn't think build-depend...22:59
infinityBuild-dep was probably to cover a build-time testsuite or something, but might possibly have been a paranoid error.23:00
infinityI don't see how it hurts either, mind you. :P23:00
Unit193I see "spec/command/debian/port_spec.rb:  it { should eq 'netstat -tunl | grep -- :80\ ' }" in that version, and "lib/specinfra/command/base/port.rb:      "netstat -tunl | grep -- #{escape(pattern)}"" in the new.23:00
infinityLots of calls to netstat in the source.23:00
Unit193infinity: Right, but if I push to Debian, specifically in a package I'm not an uploader, I want to make dang sure it's needed. :)23:00
Unit193Yeah, though a lot under 'freebsd'23:01
Unit193infinity: Thanks for explaining, and for remembering that long ago!23:01
infinityUnit193: Well, I would test it without the build-dep, but apparently the testsuite breaks earlier. :P23:06
infinity/usr/lib/ruby/2.3.0/rubygems/specification.rb:1436:in `block in activate_dependencies': can't satisfy 'net-ssh (< 4.0, >= 2.7)', already activated 'net-ssh-4.1.0' (Gem::LoadError)23:06
Unit193sudo autopkgtest -U --apt-pocket proposed=ruby-net-ssh -- lxc autopkgtest-artful23:06
infinityUnit193: But I'd posit that if it passes for you, your chroot is dirty (ie: has net-tools in it)23:06
Unit193I have no idea about the autopkgtests, it shouldn't have been installed (it's a new container, nothing abnormal), and the base chroot I used to build didn't have it either.23:08
infinityAnd the testsuite ran?23:08
infinityI mean, I literally just tried to build it and the testsuite doesn't run at all.23:09
infinitySo, I kinda want to know how you managed.23:09
Unit193The old one I think I targetted for Zesty, I'm working on a new version that of course handles net-ssh 4.x23:10
infinityAnyhow, it's possible the build-dep was in error if the ruby-specinfra testsuite doesn't exercise that bit of code (though, that would be a bug in lack of coverage of the testsuite, then), but the dependency is obviously correct.23:11
infinityAnd was needed for testsuites of OTHER rdeps to pass.23:11
infinity(And just needed because duh)23:11
Unit193infinity: Re-running the autopkgtest, something else is pulling net-tools in, that could be the answer. :P23:18
Unit193Err..23:18
Unit193infinity: SO yes, for sure no net-tools in the autopkgtest..container, and it still passed. No idea how to give you the log for autopkgtest run though.23:27
infinityUnit193: autopkgtest isn't relevant here, though.23:46
infinityUnit193: The direct dependency is correct *even if* the testsuite doesn't exercise that code.23:47
infinityUnit193: We don't add deps just to satsify testsuites.23:47
infinityUnit193: Now for *building*, the build-dep might not be relevant if the testsuite doesn't run that code, but also meh?23:47
Unit193infinity: In this case, autopkgtest also builds it.  And I figured good to specifically run with autopkgtests as they're a bit of a blackbox to me still.  Of course building runs the tests, and the build passes. :)23:48
Unit193To be clear, no I agree with your first point, net-tools should be a *depend*, but *build-depend* was what I was trying to figure out.23:49
Unit193(https://deb.li/3PbhA)23:50
infinityUnit193: Sure.  Build-dep might have just been a belt-and-bracers thing because I knew the build ran a testsuite and I didn't care to check if it had decent coverage.23:51
Unit193Good enough.23:52
infinityUnit193: And path of least resistance, since it had literally always built with net-tools in the past.23:52
Unit193Sure, understandable.23:52
infinityUnit193: I do know some OTHER testsuite exercises that code, cause that's how I noticed the bug, but damned if I can figure out what it was now. :P23:52
Unit193ruby-serverspec or chef, likely.23:52
infinityDidn't seem to be either of them at a glance.23:53
infinityBut there's also serverspec-runner, which might be a test-depend somewhere or something.23:53
infinityI dunno.  I gave up looking, I have a dinner to run off to. :P23:53
Unit193Food is always a good reason.23:54
infinityFree food.23:54
infinityPaid for by parents.23:54
Unit193Ooooooh.23:54
infinitySo, +1/-123:54
infinityBut steak, so maybe another +1?23:54
Unit193Yes very much so.23:54
Unit193But, anywho if all goes well that package is syncable now. \o/23:55

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