/srv/irclogs.ubuntu.com/2016/06/10/#ubuntu-devel.txt

naccelbrus: yeah the 500s seems to be something (i'm guessing it's a php error?) -- but i'm not sure i can find the apache logs to see00:14
naccslangasek: would you have any advice for debugging the armhf regression in cacti? it's causing php7.0 to not update currently and I really don't know how to reproduce it (the tests need root)?00:27
slangaseknacc: pointer?00:27
naccslangasek: http://autopkgtest.ubuntu.com/packages/c/cacti/yakkety/armhf/00:28
naccslangasek: started failing about a week ago, it seems00:28
naccsymptomatically, timeouts are occurring (I think), but the logs indicate the webserver is getting 500s ... but I don't think autopkgtest stores the apache logs (cmiiw) so I'm not sure how to verify if it's something obvious00:29
slangaseknacc: this regressed without any relevant changes to the dependencies; so it's currently a badtest and we should mark it as such to remove the migration blocker00:32
naccslangasek: ack, that makes sense to me :)00:33
naccslangasek: is that something you can do for me?00:34
slangasekyes (already done)00:34
naccslangasek: great, thanks! this should allow dh-php to demote to universe (once php7.0 propogates to release), which will remove a component mismatch and let dh-php update as well00:34
slangasekpretty unhelpful that none of the output goes into the test log :P00:34
naccslangasek: yeah :)00:35
naccslangasek: i was at quite a loss on how to figure out what was going on00:35
slangaseknacc: I'm assuming you care about cacti not blocking php7.0's migration, and that you don't particularly care about the cacti in -proposed right now00:36
naccslangasek: ack00:36
slangasekok. then I'm leaving the cacti in -proposed blocked by its own test failure, and someone who does care about that package can figure it out00:36
naccyep, that'd be elbrus --^ presumably :)00:36
naccslangasek: feel free to ignore my question until it's convenient for you, but phpunit in yakkety-proposed currently fails to build (https://launchpadlibrarian.net/263777009/buildlog_ubuntu-yakkety-amd64.phpunit_5.4.2+dfsg-1_BUILDING.txt.gz) because the Debian package is not properly versioning the deps on php-codecoverage (so what could be a build-dep failure is instead expressed as a build failure).00:51
naccBut the dep in question (php-codecoverage) will fail to build if resubmitted currently because it depends on a newer phpunit than is in yakkety (in fact, I think the version that is currently not building). I am really not sure how these two packages got into this state, and if Debian did manually overriding knowing it would be overcome once they were both built00:51
naccslangasek: but my question is: are you ok if i submit a patch like was done in 16.04 to add a build profile that disables the tests (and we possibly use that to bootstrap this tight loop)?00:53
naccalternatively, if it's possible, we could pass DEB_BUILD_OPTIONS=nocheck to the builder for php-codecoverage and it builds fine00:58
naccusing that .deb file (--extra-package), phpunit also now builds01:01
slangaseknacc: if DEB_BUILD_OPTIONS=nocheck is sufficient to let us bootstrap, we can reasonably do that and shove it into the bootstrap archive01:01
slangasekeasier than having to change packages01:01
naccslangasek: ack, i'm just verifying both build successfully afterwards01:02
naccslangasek: ok, this process worked for me locally: http://paste.ubuntu.com/17162006/01:24
=== juliank is now known as Guest53138
=== juliank_ is now known as juliank
naccnote that the php-mock-object build is a needed merge (reviewed by rbasak already)01:25
=== mnepton is now known as mneptok
sergiusensslangasek still around? is this a known issue https://launchpadlibrarian.net/264431731/buildlog_ubuntu-yakkety-amd64.snapcraft_2.11+16.10_BUILDING.txt.gz ?02:03
slangaseksergiusens: nothing that's known to me, but I see there's been a new version of python3.5 synced to yakkety-proposed today02:05
sergiusensah that can explain it02:06
sergiusensslangasek I guess this would block my SRUing02:07
slangaseksergiusens: no reason that it should02:07
sergiusensah, I thought we always had to push to the devel series first :-)02:08
slangaseksergiusens: you did push it to the devel series; it's not required that it migrate out of -proposed when it's been blocked by an unrelated bug...02:08
sergiusensfair enough02:09
slangasekfwiw I can't see any reason something is looking for a Makefile at that path... it might be a python3.5 regression, but that file doesn't exist in the previous version of the python3.5 package either02:10
sergiusensslangasek it does on xenial $ dpkg -S /usr/lib/python3.5/config-3.5m-x86_64-linux-gnu/Makefilelibpython3.5-dev:amd64: /usr/lib/python3.5/config-3.5m-x86_64-linux-gnu/Makefile02:15
slangasekah02:15
slangasekonly in libpython3.5-dev, which I didn't have installed :-)02:16
slangaseksergiusens: ... and which is not a build-dep of snapcraft either02:17
sergiusensslangasek yeah, I wonder how it ever worked...02:17
slangasekprobably by the previous version not unnecessarily requiring that Makefile :)02:18
slangasekdoko: ^^ python3.5 3.5.1-15 in -proposed is definitely broken wrt pybuild; I'm going to drop it out of -proposed to unblock package builds until a fix is available02:21
sergiusensat least I know the same package built fine on xenial https://launchpad.net/~snappy-dev/+archive/ubuntu/snapcraft-daily/+build/989620202:23
slangaseksergiusens: ^^ and having removed that, snapcraft can be retried in about an hour02:23
sergiusensthanks, I'll be in bed by then, but I'll make sure to retry in the morning, in the meantime I'll leave the upload on xenial ;-)02:27
naccslangasek: can you demote dh-php to universe?02:32
naccslangasek: php7.0-dev should now only suggest it, and that's the only revdep in main02:32
slangaseknacc: http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed claims it's still used in main; until it shows up on that report I won't fiddle with it, that just encourages archive admins to get into accidental revert wars02:33
naccslangasek: ack, sorry02:39
=== Spads_ is now known as Spads
naccslangasek: hrm, when i look at that page it says it wants to move xml2 to main (since dh-php depends on it and dh-php is in main). I'm suggesting we demote dh-php to universe -- did I misunderstand? Also, i'm really confused, the debdiff rbasak uploaded for me and diff at https://launchpadlibrarian.net/264339273/php7.0_7.0.7-4_7.0.7-4ubuntu1.diff.gz indicate dh-php is now in Suggests (or should be).02:53
naccBut my chdist apt-cache does not?02:53
naccargh, i know why, nm02:55
nacccontrol.in vs. control02:55
=== Spads_ is now known as Spads
slangaseknacc: right, so if all the changes were done and dh-php would be ready to drop, you would see dh-php under "move sources from main to universe" instead of a dependency of dh-php under "move sources from universe to main"03:31
mwhudsonwhen SRUing something directly from yakkety to xenial, do i just stick a xenial changelog on the top of whatever's in yakkety?03:33
mwhudsonslangasek: ^03:33
slangasekmwhudson: that's usually ok03:33
=== Spads_ is now known as Spads
pittibdmurray: tgt> I'll look05:35
pittislangasek: plasma-workspace> rather looks like the uninstallability of -proposed is locked up with the other KDE packages; http://autopkgtest.ubuntu.com/packages/p/plasma-workspace/yakkety/armhf/ just succeeded in current y-release05:37
pittislangasek: so I don't think the "force-badtest plasma-workspace/armhf/4:5.5.5.2-0ubuntu1" is justified actually05:37
pittislangasek: and consequently, I don't think we should ignore the failure for 4:5.6.4-0ubuntu1 either05:38
pittislangasek: it didn't promote as it's still blocked by dependencies05:38
pittibut I tried with --all-proposed often enough, that's not it -- something in y-proposed is really missing05:39
pittinacc: so php7.0 landed, nice work! so I take it your php-imagick merge can land now?05:40
ginggsmorning pitti! sorry, i didn't see your question on LP: #1556685 Is my answer reasonable, or do i need to dig deeper?05:53
ubottuLaunchpad bug 1556685 in oce (Ubuntu Xenial) "Wrong installation path (0.16 instead of 0.17)" [Undecided,Incomplete] https://launchpad.net/bugs/155668505:53
pittiginggs: ok, you now said it's cosmetic and has no actual impact on its rdepends; but a test case is still necessary, i. e. how can someone verify that the update still works05:56
pittiinfinity: the glibc FTBFS on amd64, is that known? (hidden symbol `__stack_chk_fail_local' isn't defined)05:56
pittihttp://autopkgtest.ubuntu.com/packages/g/glibc/yakkety/amd64/05:57
ginggspitti: well, i did check that freecad and gmsh still open and after upgrading, but not being familiar with the applications did not do extensive testing05:57
pittiginggs: but these wouldn't use cmake files at runtime, right?05:58
ginggscorrect05:58
pittiginggs: i. e. "test that freecad and gmsh still start" is a good part of the test and should be mentioned05:58
pittibut e. g. "test that they still build" might be another?05:59
pitti(sorry, I have absolutely no idea what oce is)05:59
ginggsok, i'll expand on that.  they *only* build after the upgrade05:59
ginggspitti: so when i'm done with that, do i need to upload the same version again?06:01
pittiginggs: I didn't reject it, just held it in the queue06:01
pittioh, but vorlon did06:02
pittiginggs: yeah, easiest to just reupload the same thing06:02
ginggspitti: danke!06:02
pittiginggs: thanks06:02
pittiginggs: so, put yourself into the position of someone not knowing oce who is supposed to decide "is that an update which does not cause regressions and actually fixes the bug?"06:02
pittiginggs: and formulate the test case and regression potential accordingly06:03
pittixnox: FYI, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libseccomp is blocked as it regresses on i386 and s390x06:04
ginggsginggs: i tried doing that in the SRU bug LP: #1556680, but i see i should have been more explicit in LP: #155668506:06
ubottuLaunchpad bug 1556680 in oce (Ubuntu Xenial) "[SRU] Wrong library path in CMake file for 64bit system" [Undecided,Fix committed] https://launchpad.net/bugs/155668006:06
ubottuLaunchpad bug 1556685 in oce (Ubuntu Xenial) "Wrong installation path (0.16 instead of 0.17)" [Undecided,Incomplete] https://launchpad.net/bugs/155668506:06
pittiginggs: ah, the joy of SRU bugs; never do that, please06:17
ginggspitti: never do what, exactly?06:25
pittiginggs: open a separate bug #2 that says "SRU for bug #1"06:26
ubottuError: Launchpad bug 2 could not be found06:26
ubottubug 1 in Ubuntu Malaysia LoCo Team "Microsoft has a majority market share" [Critical,In progress] https://launchpad.net/bugs/106:26
* pitti smirks at ubottu06:26
pittijust adding a trusty/xenial/etc. task to the actual bug is much preferred06:26
pittiit avoids smearing out the info between the two, and the originally affected people can help testing, etc.06:27
pittiand the tasks don't need to be kept in sync manually06:27
ginggspitti: understood, https://wiki.ubuntu.com/StableReleaseUpdates#Fixing_several_bugs_in_one_upload says to avoid creating meta-bugs, but that's not what happened here06:27
pittiginggs: ah, maybe they are different issues, sorry then; (they sound similar)06:28
ginggsLP: #1556680 is the real bug06:28
ubottuLaunchpad bug 1556680 in oce (Ubuntu Xenial) "[SRU] Wrong library path in CMake file for 64bit system" [Undecided,Fix committed] https://launchpad.net/bugs/155668006:28
ginggspitti: but i agree that the way it was done is confusing for someone trying to review, and i will fix that by being more explicit in LP: #155668506:31
ubottuLaunchpad bug 1556685 in oce (Ubuntu Xenial) "Wrong installation path (0.16 instead of 0.17)" [Undecided,Incomplete] https://launchpad.net/bugs/155668506:31
pittiginggs: thanks muchly for cleaning up!06:31
brendandif i run some tests via adt-run with nose, and i have logging.info statements (using logging module) in them, and the logging level set to INFO, should i see that output in the adt log? right now i just see the test names, no more detail than that06:31
mgedminnose suppresses logging output by default and only shows it if a test fails06:32
mgedminyou can ask nose not to do that with a command-line switch06:32
mgedmin-s, IIRC06:32
brendand--nocapture, great - thanks06:34
dokoslangasek, hmm, I don't see the issue yet06:51
pittidoko: many thanks for uploading py3.5, much appreciated!06:58
* pitti feeds the Launchpad hamsters to import it06:58
dokopitti, hmm, see above, slangasek claims that -15 is broken. still investigating why07:00
pitti linux | 4.4.0-24.43   | xenial-updates   | source07:45
pitti linux | 4.4.0-23.41   | yakkety          | source07:45
pittiapw: ^ apparently there's some forward copying missing?07:45
pittiapw: or is that on purpose somehow?07:45
infinitypitti: Yeah, I just didn't have any overwhelming urge to fix it until I had a better reason (like new upstream version) for an upload.07:55
infinitypitti: And I did all the kernel forward copies just now.07:55
pittiinfinity: ok, thanks; I ignored the  failure as it didn't seem triggered by the new cdebconf07:56
infinityhttps://launchpad.net/ubuntu/+source/linux/4.4.0-24.43/+publishinghistory07:56
pittiinfinity: so I'll add a force-badtest for amd64 for that version, to avoid asking you again next time :)07:57
pittibdmurray: tgt/wily was a spurious failure apparently, succeeded now08:01
apwpitti, no not on purpose, it was on my list to confirm done this morning, and it seems infinity has beat me to it08:03
pittiapw: ack, thanks08:04
infinityapw: Heh, yeah, it was on my "when I wake up" list too, and we seem to have woken up at the same time.08:05
apwinfinity, which is wrong on so many levels :)08:06
xnoxpitti, huh, that looks weird... I'll check if I dropped or reordered patches... unless upstream renumbered things which is abi break....08:40
xnoxalso no clue why these syscalls are negative =/08:41
ogra_just turn the around ;)08:44
ogra_*them08:44
pittixnox, slangasek: so poppler/gdal/gp2ls/tinyxml2 transition all hinge on suitesparse, which built because we now build against universe deps, but is not installable because its new libmetis5 dep is in universe09:53
pittixnox, slangasek: that's one of the hairy scenarios that I was afraid of.. :-(09:53
pitti"someone will fix it eventually"09:54
ginggspitti: i thought slangasek promoted libmetis5 already10:01
ginggspitti: LP: #158840710:02
ubottuLaunchpad bug 1588407 in metis (Ubuntu) "[MIR] metis" [Undecided,Fix released] https://launchpad.net/bugs/158840710:02
pitti libmetis5     | 5.1.0.dfsg-4 | yakkety/universe | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x10:03
pitti metis         | 5.1.0.dfsg-4 | yakkety/universe | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x10:03
pittiginggs: thanks, I missed the MIR as it was already closed10:03
bdrung_workpitti, whom can i poke to get the cpu+ram hotplug into the kernel?10:03
pittibdrung_work: my favourite go-to kernel person is apw, he should know whom to give this to10:04
pittiapw: sorry Andy10:04
apwheh, i ahve many fine victim^Wpeople to pass this on to10:04
pittiginggs: hm, so if this was promoted and demoted later on, I wonder why it still didn't land then10:05
pittiwell, let's find out at the next publisher/britney run10:05
pittiginggs: thanks10:05
apwbdrung_work, you might want to ask on #ubuntu-kernel so we can discuss10:05
* pitti joins too10:05
bdrung_workpitti, btw, do you know whom to talk to about the cloud images? i like to have consoleblank disabled there.10:09
rbasakbdrung_work: bug 86901710:10
ubottubug 869017 in kbd (Ubuntu) "Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)" [Medium,Triaged] https://launchpad.net/bugs/86901710:10
bdrung_workthanks rbasak10:12
rbasakbdrung_work: Wesley (an intern on the Canonical Server team) was looking into it, mainly to scratch his own itch I think. I still have him down as driving the bug. Looks like it needs an updated patch.10:13
rbasakbdrung_work: might be worth coordinating with him. He's not in here but is magicalChicken in #ubuntu-server.10:13
rbasakbdrung_work: but feel free to take the bug and patch it :)10:13
=== hikiko is now known as hikiko|ln
=== hikiko|ln is now known as hikiko
elbrusnacc: do you know of any changes in the armhf autopkgtest setup, because the same version of cacti that passed in the past, now fails...11:59
elbrusnacc: so it is either a real regression due to php (and very weird also cdebconf) or the testing framework is borking for whatever reason12:00
* elbrus will copy more logs to the artifacts; nacc do you have suggestions next to the cacti.log and apache2/access.log & error.log?12:01
=== zyga_ is now known as zyga
ginggspitti: regarding suitesparse, if i understand update_output.txt correctly, it is the missing arm64 build of gammaray that blocking things.  Can we kill that?12:14
bdrung_workpitti, rbasak: is there any package or project that I should assign #1591166 to?12:18
jamespageapologies if I'm duping existing question but is there something wonky with the proposed migration for dependencies on python-cffi (and its versioned backends)12:21
jamespagepython-oslo.privsep is wedged with12:21
jamespagepython-oslo.privsep/amd64 unsatisfiable Depends: python-cffi-backend-api-min (<= 9729)12:21
jamespagepython-oslo.privsep/amd64 unsatisfiable Depends: python-cffi-backend-api-max (>= 9729)12:21
jamespagebut its quite installable afaict12:22
pittiginggs: wow, you were able to decipher that?12:26
pittiginggs: hm, it failed on i386 too12:26
pittiginggs: gammaray has zero rdepends, so I'm just going to remove it from yakkety, keeping the y-proposed version12:27
ginggspitti: i could be completely wrong12:27
pittiwe might just retry the builds12:27
pittiginggs: not sure if it's the only cause, but it's certainly *a* cause12:27
pitti... done12:29
pittibdrung_work: assigned to cloud-images12:29
bdrung_workthanks12:30
pittiapw: want a bug for the missing python-yaml test dep? (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/ppc64el/l/linux/20160610_110617@/log.gz)12:32
pittiapw: such things are a bit hard to spot as the kernel tests have failed for quite some time (but differently)12:32
cjwatsonjamespage: It's conceivable that the britney instance here doesn't understand versioned Provides; that was only added upstream in April12:41
cjwatsonjamespage: somebody in ~ubuntu-release will have the exciting job of sorting out a merge12:42
jamespagecjwatson, the comment in the newer python-cffi would indicate that might be required as well12:42
apwpitti, yeah lets have a bug, as i will need to SRU that i assume13:05
pittiapw: filed bug 1591189, with hopefully quiescing the bot13:08
ubottubug 1591189 in linux (Ubuntu) "missing python-yaml autopkgtest dependency" [Undecided,Confirmed] https://launchpad.net/bugs/159118913:08
apwpitti, thanks, i'll get that sorted out13:09
pitticheers!13:09
Odd_BlokeI have a machine running a DNS server, and /etc/resolv.conf points at localhost.  When cloud-init runs on reboot, it does a getaddrinfo('my.metadata.service.', None) _before_ the DNS server is up (note the trailing dot).  'my.metadata.service' is defined in /etc/hosts, but that isn't found (because the trailing dot isn't stripped off before looking in to /etc/hosts), so cloud-init errors out.13:35
Odd_BlokeIs the fact that the un-dotted form is not found in /etc/hosts a bug?13:35
rbasakThat's a good question.13:40
rbasakI have "127.0.0.1localhost.localdomainlocalhost13:40
rbasakin /etc/hosts13:40
rbasakgetent hosts localhost.localdomain.13:40
rbasakfails to find anything.13:40
rbasakI'm not sure DNS semantics applies at nsswitch/hosts file level.13:41
rbasakI'm struggling to answer the question though, in part because "my.metadata.service." is a hack.13:42
Odd_Blokerbasak: A hack how?13:45
rbasakOdd_Bloke: I don't believe you have service. registered :)13:48
rbasakOdd_Bloke: the more I think about it, the more I think that it isn't defined that you're speaking DNS, so you can't expect DNS semantics. I'm not sure though.13:49
Odd_Blokerbasak: Yeah, it's a slightly weird interface.13:50
rbasakOdd_Bloke: you could be using NIS :)13:51
rbasak(what's this "DNS" think you speak of?)  :-)13:51
rbasakthing13:51
* rbasak can't type today13:51
ginggspitti i think you did it - suitesparse is through \o/13:51
pittiginggs: ooh! not yet on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt, I was watching it13:52
pittibut indeed https://launchpad.net/ubuntu/+source/suitesparse/1:4.5.3-1 is landing13:52
ginggsi'm getting mails of all the packages being accepted13:52
pitti\o/14:04
infinitypitti: Yo, what's the deal when britney claims a test is running, but it hasn't shown as running for hours?  Do things sometimes just get lost?14:13
pittiinfinity: which test?14:13
infinitypitti: (linux-raspi2)14:13
pittiinfinity: there's a few blacklisted ones which can't run, and a corner-case bug which sometimes causes lost  requests14:13
infinitypitti: It ran and broke 4h ago, but there's no indication that it was restarted.  Doesn't show as failed, though, shows as running.14:14
pittiah, this one: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/armhf/l/linux-raspi2/20160610_095800@/log.gz14:14
pittiit didn't get as far as deciphering a version number, so britney can't match it14:14
infinitypitti: Ahh, hence "version: n/a" on the result list.14:15
infinitySeems to have happened fairly regularly.  Weird.14:15
pittiso, that's an interesting question14:15
pittishoudl we somehow get this across to britney as a (failed) test result; but then, how *do* you define an approriate version number14:16
infinitypitti: Well, if it never even grabbed the source to get a version, shouldn't that be an auto-give-back?  Looks like it's the infra's fault, not the package.14:17
infinityOr, put another way, if you can blame the package, you surely have a version number.14:17
ginggsupdate_excuses.html shows supercollider - old binaries left on armhf: supercollider-supernova (from 1:3.7.0~repack-1)  - what needs to happen there?14:17
pittiinfinity: yeah; I need to run this with --debug to understand what's going on14:18
pittiinfinity: I actually did have that as "tmpfail" for a fair while, but that then caused eternal tmpfail loops/worker killing sprees on packages that were actually not existing or broken14:19
pittiapt really only gives you one exit code 100 for both transient and permanent issues14:19
pittiso that needs some more error message parsing fine-tuning14:19
infinitypitti: Fair enough.  In this case, I can requeue it.  Unless you already have?14:20
pittiinfinity: no, let me first do a manual run to see what's going on14:20
infinitypitti: Or that.  Go for it.  I'll leave it.14:20
infinitypitti: The other security kernels got through, I'm less fussed about raspi2 on yakkety.14:20
pittiinfinity: ... and of course this totally works when run manually14:24
infinitypitti: Of course it does.14:25
infinitypitti: I mean, historically, it works some of the time. :P14:25
infinitypitti: But it also seems to fail a lot.14:25
infinitySo, whee.14:25
pittiinfinity: I guess I'll add some logging verbosity then14:25
pittioh, it's not exit code 10014:29
pittiand stderr is already shown14:29
pittiso, apt fails with !100 with an error on stdout or nonexisting14:30
ginggsi think singular, supercollider and openms need to be decrufted, please14:35
pittiginggs: what does that mean? not on http://people.canonical.com/~ubuntu-archive/nbs.html14:36
ginggssorry, maybe wrong term14:36
* pitti wasn't aware that we need to remove NBS from -proposed14:36
pittithey should just become NBS in -release14:36
pittiassuming of course that  all remaining reverse dependencies get dropped14:37
pittibut ICBW14:37
pittiginggs: for e. g. singular that just means that it's not built on armhf, and indeed https://launchpad.net/ubuntu/+source/singular/4.0.3-p1+ds-2build2/+build/9804780 is depwwait14:38
pittiI can't explain the supercollider-supernova thing, I'm afraid14:39
ginggsok so for singular then, can we remove the armhf binaries so it can migrate, and it will build when python-polybori becomes available again?14:41
cjwatsonwe need to remove NBS from -proposed in the corner case where a source package drops binaries that were previously part of another publication to yakkety-proposed since the last version in yakkety14:43
cjwatsonmay not be relevant here, haven't checked14:44
pittiinfinity: ah, found a way to reproduce14:44
pittifixing this needs to wait until Monday I'm afraid, I need to run soon; but I take that's  enough14:45
naccelbrus: that's what i would start with for sure (re: cacti logs). But note the first regression point happened w/o any change to php proper (afaict) ... so it's hard for me to debug why :)14:46
infinityginggs: Erk, who removed polybori on armhf in the first place? :/14:49
* infinity looks.14:49
infinityOh, Colin. :P14:49
cjwatsonI imagine I had a reason14:50
infinityFTBFS on armhf; also removed in Debian14:50
cjwatsonah yeah, I reckoned that if Debian had given up on it then there was no sense trying *too* hard14:51
infinityThe part where no code changed and it started failing, though, leads one to wonder if polybori is really the problem or if we just papered over something worse.14:51
infinity(ie: I'd assume it's libpng's fault somehow)14:51
infinityOr boost.14:52
naccrbasak: i made a thinko in my php7.0 upload so it didn't actually change anything (d/control.in vs. d/control). Would you be willing to re-sponsor the debdiff in LP: #159062314:53
ubottuLaunchpad bug 1590623 in php7.0 (Ubuntu) "Drop dh-php from Recommends to Suggests" [Undecided,In progress] https://launchpad.net/bugs/159062314:53
naccpitti: yes, once that is done --^ and goes through, php-imagick can go in (i can actually test it once dh-php updates) and that will unblock php-defaults14:53
rbasaknacc: yep, looking.14:54
naccrbasak: thanks!14:54
* pitti waves good bye and happy weekend14:54
infinitypitti: See you soon14:54
infinitypitti: Oh, what's the deal with that raspi2?  Is it handled, or do I need to do things to it?14:55
ginggsbye pitti14:55
rbasaknacc: I have to run (early EOD to catch a train) but I think there's a bug in usd-merge.15:19
rbasakIt's quite confusing. I tried to "undo" a "usd-merge commit" while experimenting.15:19
rbasakI've ended up with a .git/ubuntu/yakkety "ref", which seems to override .git/refs/heads/ubuntu/yakkety.15:20
rbasakSo when I reset the ubuntu/yakkety branch back to its original hash, "git-rev-parse ubuntu/yakkety" and thus "usd-merge commit" both don't see it, which causes a bunch of extra merge commits as I redo each time, IYSWIM.15:21
rbasakI think the problem is that the call to "git update-ref" needs to be "refs/heads/ubuntu/yakkety" rather than just "ubuntu/yakkety".15:21
naccrbasak: hrm, i'll re-read the man-page15:22
naccand test locally15:22
rbasakThanks!15:22
naccrbasak: i know there's also a bug with `usd-merge reconstruct` and upload/ tags15:22
naccas those can't be cherry-picked the same15:23
naccrbasak: ack, you're right, fixing it and pushing15:29
naccbarry: fyi, we've combined that gh repository with the lp one. And i've updated the wiki references as well15:31
barrynacc: cool.  did rbasak land pr#2 yet?15:32
naccbarry: i just pulled it in to our combined repository. I think rbasak will close the gh one eventually. So since i have write access to the lp one, i was able to commit the changes directly :)15:32
barrynacc: cool :)15:32
bdmurraypitti: How did you restart it tgt/wily?  I forget how to do that.15:33
anaranhi, will firefox be available on ubuntu phones soon, without external display connected (similar to firefox for android)?15:34
nacci think rbasak wasn't able to get to it before he left, but could someone help sponsor the latest debdiff in LP: #1590623 ? Needed to help unblock one set of php* in excuses15:39
ubottuLaunchpad bug 1590623 in php7.0 (Ubuntu) "Drop dh-php from Recommends to Suggests" [Undecided,In progress] https://launchpad.net/bugs/159062315:39
rbasaknacc: I did upload it, sorry I didn't say. I guess you don't get the email? Anyway, it's in proposed :)16:10
naccrbasak: interesting, yeah, i wasn't notified and i hadn't seen it yet in excuses16:11
naccrbasak: ah probably because it's still building, got it16:12
naccrbasak: tahnks! i can see the proposed builds have the right deps now16:35
rbasakNo problem :)16:36
dobeyanaran: an external display isn't required, but it's not particularly useful to run firefox on a phone. if you want to know if mozilla is going to ship a version of firefox suited for use on phones/tablets, in the ubuntu store, you'd have to ask mozilla.17:38
ogra_dobey, you just need a mouse,keyboard and a good looking-glass :P17:45
dobeyogra_: well, when the keyboard integration is fixed, you won't need an external keyboard17:53
slangasekpitti: as ginggs said, metis was already promoted, so somebody else re-demoted it without looking at component-mismatches-proposed18:07
elbrusdoes anybody here no a good example of autopkgtest tests that add log files to the artifacts?18:55
elbruss/no/know/18:55
* elbrus has "set -e" so can't just do it at the end of the test18:56
=== Spads_ is now known as Spads
=== Spads_ is now known as Spads
keesdoko: any chance you can take a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826786 ? I'm really not sure how it's best solved, but it's blocking upstream kernel testing of the new gcc plugin infrastructure21:20
ubottuDebian bug 826786 in src:gcc-6-cross "gcc-6-cross: No gcc plugin headers for cross compilers" [Wishlist,Open]21:20
=== tinoco is now known as tinoco-vacation
=== tinoco-vacation is now known as tinoco
=== tinoco is now known as tinoco-vacation
naccslangasek: would you be able to assist me with the bootstrap for phpunit? I've verified the steps needed, and I think this will unblock the majority of the stuck php packages (as phpunit will be updated and installabe)21:36
slangaseknacc: I'm not going to get to it today; maybe infinity could help22:04
naccslangasek: ok, np22:04
naccinfinity: if you're around, i need to bootstrap build 3 packages with DEB_BUILD_OPTIONS as they all interdepend (but the end-result, which we'd want to copy to the archive doesn't require any DEB_BUILD_OPTIONS and builds successfully in my testing)22:05

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