/srv/irclogs.ubuntu.com/2016/09/07/#ubuntu-devel.txt

=== salem_ is now known as _salem
Bluefoxicypissing off everyone on ubuntu-devel-discuss in 3, 2, 1...01:59
mwhudsonheh heh i ran "EB_BUILD_OPTIONS=nocheck sbuild -d yakkety"03:22
=== King_InuYasha is now known as Son_Goku
=== Son_Goku is now known as Conan_Kudo
=== Conan_Kudo is now known as Sir_Gallantmon
=== Sir_Gallantmon is now known as Son_Goku
=== vigo is now known as vigo|afk
sakrecoerjbicha: from upstream, https://github.com/numixproject/numix-gtk-theme/issues/508 :) we just grep'ed all the colors from red to blue :)06:17
jbichasakrecoer: oh06:19
pittiGood morning06:22
sakrecoermorning! :)06:25
pittibdmurray: http://autopkgtest.ubuntu.com/packages/ubuntu-release-upgrader passed again except on armhf06:47
jamespagedoko_, great - thankyou!07:17
LocutusOfBorghi, sigh  cp: error writing 'debian/insighttoolkit4-python/usr/lib/python2.7/dist-packages/itk/itkCenteredTransformInitializerPython.py': No space left on device08:12
LocutusOfBorgppc64el08:12
LocutusOfBorgdo you think we have machines with more free space?08:13
mwhudsonpitti: autopkgtests are confusing me again, http://people.canonical.com/~ubuntu-archive/proposed-migration/yakkety/update_excuses.html#docker.io says "in progress" but it's lying08:27
mwhudsonor at least inconsistent with http://autopkgtest.ubuntu.com/running08:28
pittimwhudson: looking08:32
pittiERROR:root:http://10.24.0.175:8080/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/d/docker.io/20160907_055947@/result.tar is damaged, ignoring: "filename 'testpkg-version' not found"08:40
pittimwhudson: ah, that's it -- https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/d/docker.io/20160907_055947@/log.gz08:40
pittimwhudson: autopkgtest seems to have trouble with unpacking the source, I'll have a look08:40
mwhudsonpitti: special08:41
pittimwhudson: hmm, can't reproduce locally or on infra, and a retry worked; sun rays/temp network failure/fingers in ear/lalala etc.09:02
mwhudsonpitti: ok, so it's run on the real infrastructure now?09:11
pittimwhudson: yes, and http://autopkgtest.ubuntu.com/packages/d/docker.io/yakkety/amd64 has the actual result now09:16
mwhudsonhuh lxd does not depend on lxd-client09:17
mwhudsonTIL!09:17
pittimwhudson: Restrictions: needs-recommends, or add it explicitly09:20
pittimwhudson: indeed, you can have a box which is only a remote lxd server09:20
mwhudsonpitti: yeah, added it explicitly09:20
pittiPSA: autopkgtest infra will go down for a bit for redeployment; I'll mop up any missed britney tests afterwards09:32
=== hikiko is now known as hikiko|ln
Laneydoko_: do you know if anyone is aware of/looking at the mir ftbfs in yakkety-proposed?10:22
Laneyfound https://bugs.launchpad.net/ubuntu/+source/mir/+bug/161961610:23
ubottuLaunchpad bug 1619616 in protobuf (Ubuntu) "Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)" [High,In progress]10:23
cjwatsonLocutusOfBorg: all builders have identical disk allocation and are started from a fresh image between builds10:27
=== hikiko|ln is now known as hikiko
tseliotpitti: hi, can you help with LP: #1619306 , please? nvidia is in NEW10:37
ubottuLaunchpad bug 1619306 in ubuntu-drivers-common (Ubuntu) "SRU request: Include the 367 driver in Ubuntu 16.04" [High,In progress] https://launchpad.net/bugs/161930610:37
pittitseliot: not right now (I don't want to stop redeploying our test infra), maybe later10:40
tseliotpitti: ok, thanks10:43
LocutusOfBorgcjwatson, it makes no sense then :)10:57
LocutusOfBorgthe previous upload was successful10:58
LocutusOfBorgand changes are not worth a size change10:58
cjwatsonLocutusOfBorg: ok, can't help with that, but I thought you might find it helpful to know that any exploration of the form "clean up builder" or "use a different builder with more space" is a red herring10:59
LocutusOfBorgyes, and thanks for that :)10:59
cjwatsonyour build may have slightly nondeterministic size10:59
LocutusOfBorgthe question hidden was something like "did anybody reduce the size of the ppc64el builders in the last 10 days"?11:00
LocutusOfBorgbut the answer should be "nobody" and the size is increased from time to time, not reduced11:01
LocutusOfBorgso, exploring other possibilities11:01
cjwatsonLocutusOfBorg: basically the only way that could happen is if the inter-build reset was quite a while before the build started so that the launchpad-buildd log had grown larger - but that's really quite a negligible amount of space11:04
cjwatsonthere are things we could do like running apt-get clean after installing build-deps, but even then the amount of space involved should not be *that* large11:05
cjwatsonthere's no cruft build-up over time11:05
LocutusOfBorgBuild needed 08:42:50, 2391164k disc space11:05
LocutusOfBorgthis is from the old build11:05
LocutusOfBorgI can also remove the debian/tmp after dh_install :)11:06
LocutusOfBorgrm -rf BUILD debian/tmp11:06
LocutusOfBorgalready done :(11:06
LocutusOfBorgLaney, pretty please can you look at merging gnome-pkg-tools? your "X-AppStream-Ignore=true" can't be merged11:09
LaneyLocutusOfBorg: We dropped that whole script there, so just copy it from the Ubuntu package when merging.11:11
LocutusOfBorgok thanks11:19
LocutusOfBorgso, can I merge Laney? :)11:25
LaneySure11:25
LocutusOfBorg-         python3,11:26
LocutusOfBorg-         python3-gi,11:27
LocutusOfBorg-         gir1.2-glib-2.011:27
LocutusOfBorgthey have been removed from runtime-deps11:27
LocutusOfBorgreadding11:27
LaneyYes11:28
LocutusOfBorgaccording to svn, they are dropped with the pkg-gnome-compat-desktop-file removal11:28
LaneyBasically revert that commit11:28
LocutusOfBorgyep11:29
=== freyes__ is now known as freyes
pittiLaney: FYI: https://git.launchpad.net/~ubuntu-release/+git/autopkgtest-cloud/commit/?id=d1ac20f3c5 and https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure?action=diff&rev2=66&rev1=6513:08
pittiLaney: this should also reduce worker failure spam now13:08
pittiLaney: i. e. only the 6-hour maintenance cron job will show the logs of permanently failed workers, not the ones any more which recover quickly (nobody pays attention to them anyway)13:09
semiosisanyone know whats up with the daily builds of xenial on cloud-images?  latest one is a week old (aug 30)13:12
semiosisOdd_Bloke: ?13:12
Odd_Blokesemiosis: I'll ensure that the livecd-rootfs change has been picked up in our build PPA, then kick one off. :)13:16
semiosisOdd_Bloke: sweet!  thank you13:17
Odd_Blokesemiosis: (It triggers automatically on changes to packages _in_ the image, which doesn't apply to livecd-rootfs :)13:17
semiosisOdd_Bloke: that makes sense13:18
Laneypitti: nice; what else changed with moving to xenial?13:55
pittiLaney: mostly the upstart → systemd move and moving teh notification mails from the worker upstart job into the maintenance cron script14:07
pittiLaney: the rest is just gory small details14:07
Laneynod14:08
Laneywell, good work!14:08
pittiLaney: but this got rid of this wget | dpkg -i thing and the backport PPA, the workers are easier to stop now (cgroup units et al), and it can now be ported to py314:08
* Laney is re-jujuing for appstream-generator as well14:09
Laneytried to look at Mojo again14:09
Laney*cough*14:09
Laneyalso juju 2.0 appears to be fairly different to 1.x14:09
pittiLaney: yeah, I keep trying 2.0, but earlier it got stuck on deploying, and now this silly 2.1 versioning bug14:17
pittiLaney: 2.0 appears much nicer locally (it doesn't pull in all that crap on the host, but everything into lxd containers)14:17
Laneypitti: oh, does it? I didn't get that far due to lxd bug and I wasn't sure if I could use it on wendigo anyway14:21
Laneylike if the charms are going to be compatible14:21
pittiLaney: charm format hasn't changed much AFAICS14:21
pittiLaney: but no juju 2.0 on wendigo indeed14:21
pittiI was just hoping for a nicer "local" experience14:21
Laneyya14:21
LaneyI'd probably end up using a 2.0 feature by accident14:21
pittiold juju-local clutters the host and fails with ecryptfs (units need to be manually started after login, etc.)14:22
Laneymight try "juju-deployer" though if I can figure it out14:22
Laneyhopefully make the nagios/bootwhatsitcalled/turku setup easier14:22
Laneybasenode14:23
pittiLaney: hm, I downgraded to 2.0.4 (that took some time), and now it fails due to14:39
pittiERROR failed to bootstrap model: cannot start bootstrap instance: unable to get LXD image for ubuntu-xenial: The requested image couldn't be found.14:39
pittiLaney: that doesn't ring a bell with you by any chance?14:39
pittiah, nevermind -- installed https://launchpad.net/ubuntu/+source/juju-core/2.0~beta17-0ubuntu1.16.10.1/+build/10695313 and that works with lxd 2.1 and also downloads the image14:43
pitti(that's just stuck due to FTBFS)14:43
Laneynie14:45
Laneynice*14:45
LaneyI didn't get that far :)14:45
pittiLaney: nice, with that "juju bootstrap lxd-test localhost; juju deploy rabbitmq-server" Just Works™14:49
Laneypitti: Maybe I'll try it again tomorrow or so then14:58
Laneyiterating on canonistack isn't that fun14:58
seb128Saviq, cyphermox, was there anything else needed on bug #1613678? the hardening was enabled and the buglist seems short enough?15:05
ubottubug 1613678 in unity-notifications (Ubuntu) "[MIR] unity-notifications" [Undecided,New] https://launchpad.net/bugs/161367815:05
Saviqseb128, not that I know of, wasn't sure how to change the status to get it back in business15:08
cyphermoxseb128: I'd like to re-review to say15:41
seb128cyphermox, can you do that this week?15:42
cyphermoxI will do that today15:43
seb128thanks15:44
pittiLaney: so, nice -- that's the first time juju-2.0 ever worked for me, and now it works without a hitch15:56
pitti... except for tab completion which is broken15:56
Laneypitti: So you're going to use this to develop charms which you'll deploy on 1.25?15:57
pittiLaney: not sure yet, but I at least wanted to play around with it15:58
pittiLaney: I need to charm up the langpack-o-matic stuff, I think I'll use it for that15:58
pittiLaney: and I at least want to make the autopkgtest charms compatible with juju-2.0, as that's the default juju on 16.04 now15:59
pittiLaney: so I'm more worried about compatibility in that "upward" direction15:59
Laneypitti: Are there problems in that way?15:59
Laneytoo early to tell? :)15:59
pittiLaney: I hope not -- as I said, I've never gotten j-2 to work until now :)16:00
* pitti → dinner16:00
=== shuduo is now known as shuduo-afk
octoquadhi, can anybody tell me how I can create a branch for the software-center based off the latest revision for trusty. I don't see any obvious branches to fork from.16:19
rbasakoctoquad: bzr-based UDD is deprecated. Use "pull-lp-source software-center trusty" to grab the latest source (without VCS).16:21
octoquadrbasak, thanks, it's been a while since I contributed!16:21
octoquadls16:23
naccrbasak: re: LP: #1579480 and similar bugs, is there a best practice for dealing with 'manually' installed packages that no longer exist in the new release?16:23
ubottuLaunchpad bug 1579480 in php-defaults (Ubuntu) "PHP7-ubuntu sessionclean searches for "php5" named binary" [High,Invalid] https://launchpad.net/bugs/157948016:23
naccrbasak: e.g., LP: #1617397 might be related to the same idea (php5 packages sticking around)16:25
ubottuLaunchpad bug 1617397 in php5 (Ubuntu) "Some php5 packages not upgraded to php7 from 14.04 to 16.04" [Wishlist,Triaged] https://launchpad.net/bugs/161739716:25
rbasaknacc: if the new php-common should cause php5-common to be removed on upgrade, then maybe a Conflicts/Replaces? I'm not sure.16:26
* rbasak consults https://wiki.debian.org/PackageTransition16:26
rbasakMaybe #11?16:26
rbasakI'm interested in ondrej's opinion. We should probably do what he says here (and not diverge).16:27
naccrbasak: ack, i asked him in the second bug16:28
naccrbasak: also just took a look at debian sid and it seems to match what we currently have, afaict. Interesting, php-common breaks (versioned) php5.6-common which doesn't exist in debian, and not php5-common at all.16:37
=== alexisb is now known as alexisb-afk
=== sexy-guy changed the topic of #ubuntu-devel to: Why won't pretty girls talk to me?
sexy-guyWhy won't pretty girls talk to me?17:56
Unit193dax.17:56
sexy-guyUnit193: Why won't pretty girls talk to me?17:56
sexy-guydax: Why won't pretty girls talk to me?17:57
daxUnit193: danke17:57
Unit193dax: Thank you.17:57
=== dax changed the topic of #ubuntu-devel to: Xenial (16.04.1) Released! | Archive: feature freeze | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
daxUnit193: reminder about pondering changing this channel's ACL17:57
=== alexisb-afk is now known as alexisb
naccsmb: around?21:28
mwhudsonpitti: is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834367 going to be fixed in xenial?21:51
ubottuDebian bug 834367 in systemd "systemctl daemon-reexec (as run on systemd upgrade) causes all keystrokes to go to text console in addition to X (including passwords)" [Critical,Fixed]21:51
naccjust to confirm, an SRU to a package with version currently 7.0.5+dfsg-4build1 should result in 7.0.5+dfsg-4ubuntu0.1?22:03
sarnoldnacc: yes, that's what we've got in our version-number-table https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging22:04
naccsarnold: yep, just my first upload, so didn't want to mess up :)22:05
naccsarnold: thanks!22:06
naccsarnold: for dput to xenial-proposed, it would be `dput ubuntu:xenial-proposed <changes file>`, correct?22:17
sarnoldnacc: that's what my notes say, but I've never done uploads outside of -security22:18
jbichayou might even be able to do 7.0.5+dfsg-4ubuntu1 if that version doesn't and won't exist in any later Ubuntu release22:22
naccsarnold: ack, thanks -- many of the documents i'm finding just keep referring to 'when you do an upload', without specifying exactly what to do :)22:24
naccjbicha: true, i figured i was best off being consistent with the security team's documentation22:24
cjwatsonyou don't specifically need to dput to ubuntu:xenial-proposed22:24
cjwatsonwhat matters is what's in the Distribution field in the .changes, which is generated from the first line of debian/changelog22:25
cjwatsonand "xenial" will do fine there, that's mapped to xenial-proposed automatically22:25
cjwatsonassuming that's correct then you can just dput to ubuntu22:25
nacccjwatson: ah ok, good to konw22:25
nacc*know22:25
naccmaybe that's why it's not easy to find that detail :)22:25
cjwatsonwhat matters> well, if you specify a particular dput target then that will override22:26
cjwatsonbut most people don't22:26
naccright22:27
nacccjwatson: thanks again!22:27
sarnoldah thanks :)22:27
Unit193'devel' is even more fun. >_>22:28

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