=== anthonyf is now known as Guest33778
=== salem_ is now known as _salem
=== marcusto_ is now known as marcustomlinson_
=== marcustomlinson_ is now known as marcustomlinson
pittimhall119: that sounds a bit like our merge-o-matic?05:09
pittiGood morning05:09
pittiinfinity, Laney: can we please ignore the broken tests for linux 4.0.0-2.4 as well?05:10
infinitypitti: It's broken for other reasons, we're not letting it migrate right now.05:12
infinitypitti: But if you want to ignore it for something waiting on it, sure.05:13
pittiinfinity: ok; but it blocks other packages05:13
infinitypitti: Fixing.05:13
pittiinfinity: cheers!05:13
pittijdstrand: I'm merging libseccomp2 again (it's rather trivial), I need Debian's -2 to unbreak separate /usr; I hope you don't mind?05:33
sarnoldpitti: that's almost certainly fine, the last changelog entry looks like there's not many local changes remaining05:38
pittisarnold: no, just adding the autopkgtest05:39
pittiand the only change in -2 is to move the library from /usr to /lib05:39
sarnoldpitti: at least, jdstrand's usually good about keeping his changelogs precise and accurate :)05:39
pittisarnold: yes, and the patches.u.c. diff agrees with him :)05:39
sarnoldpitti: are the 'new' library paths still covered by the apparmor <abstractions/base> file?05:40
pittisarnold: oh, do we do per-library paths in apparmor? /me checks05:40
pittigrep -r seccomp /etc/apparmor*  → no hits05:40
sarnoldpitti: not usually.. I ust wanted to make sure that these weren't going someplace unexpected :)05:40
pittino, just the standard /lib/x86_64-linux-gnu/ (or whatever the architecture is)05:41
sarnoldpitti: how have I been here nearly three years and never seen patches.ubuntu.com??? this is awesome. thanks. :)05:41
pittilike libc.so.6 or libdbus and stuff05:41
pittisarnold: heh -- it's a by-product of MoM (merges.ubuntu.com)05:41
sarnoldthis is cool, I've thought before that relying upon the changelog to keep track of the ubuntu/debian delta was prone to mistakes. this is great :)05:43
pittisarnold: but you did see MoM, I hope? that also gives you both diffs05:44
sarnoldpitti: I think I've only ever seen the summary universe.html and so on there..05:44
dholbachgood morning07:11
dkesselgood morning dholbach07:13
dholbachhey dkessel07:16
dholbachmitya57, did you upload ubuntu-packaging-guide already?07:22
mitya57dholbach, oops, I forgot :/07:23
mitya57Will do now :)07:23
dholbachawesome, thanks!07:23
mitya57dholbach, uploaded (will be in NEW queue though)07:51
dholbachthanks a lot mitya57!07:52
mitya57Sorry for forgetting :)07:52
dholbachno worries :)07:52
infinitypitti: What's the state of the art on reproducing adt failures locally?08:05
pittiinfinity: hasn't changed in a long time -- easiest is to use the qemu runner08:05
pittiinfinity: http://packaging.ubuntu.com/html/auto-pkg-test.html#executing-the-test08:05
pittiinfinity: the biggest difference is the internet proxy that we (have to) use in production08:06
pittiotherwise it's pretty much exactly the same08:06
infinitypitti: Kay.  Can I run a single test there, or will it just run everything in debian/tests/control unconditionally?08:06
pittiinfinity: you can use --testname to run a single test08:06
infinitypitti: Shiny.  Thanks.08:06
pittiadt-run --testname mytest1 mysrc08:06
pittiinfinity: and usually you want -s too08:07
infinitypitti: I think I had all this going at one point, then new laptop happened.08:07
pittiinfinity: well, it's really just one "adt-buildvm-ubuntu-cloud" command away :)08:07
pittiinfinity: and yeah, getting new laptop beats destroying a throwaway VM any time :)08:08
infinityApparently, cloud-images.ubuntu.com is connected to the internet with a bendy straw.08:08
pittioh, is it slow for you?08:09
infinitypitti: Around 1MB/s, looks like.08:09
infinitypitti: So, slow for me.08:09
pittiup to vivid it was reasonably fast here, then in April/May it was ridiculously slow, and now it magically fixed itself again to be as moderately-fast as before08:09
pittiinfinity: so, best not to look at it :)08:09
infinityA watched image never downloads?08:10
Odd_Blokeinfinity: Are you connected to the VPN; I've sometimes seen image downloads routed through that.08:17
Odd_Blokes/the VPN/the Canonical VPN/08:17
Odd_BlokeWhich is obviously sloooow.08:17
infinitypitti: If I'm just experimenting with debian/tests, I assume I want something like '--unbuilt-tree foo-1.2.3-1 -B'?08:17
infinityOdd_Bloke: Yeah.  Until we fix it to allow me to be connected to both endpoints, that's probably my issue.08:18
infinityOdd_Bloke: I do occasionally forget I have that issue, though. :P08:18
pittiinfinity: put the -B before (it only applies to the next test argument), but in principle yes08:19
pittiinfinity: I usually use something like "adt-run ./ --- qemu ...", typing laziness08:19
pittiinfinity: <dir>/ is an abbreviation for --built-tree <dir>08:19
pittiand <dir>// for --unbuilt-tree <dir>08:19
pittigreetings from iwj from 9 years ago :)08:20
infinitypitti: Hahaha.08:23
infinitypitti: FWIW, --testname isn't documented in the manpage.08:28
infinitypitti: Erm, and my first derp.  Clearly this isn't performing exactly how prod does...08:31
infinitySource Package Version: 4.0.0-2.408:31
infinityRunning Kernel Version: 3.19.0-20.2008:31
infinityERROR: running version does not match source package08:31
pittiinfinity: man> thanks, fixed in http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=16eb56eac08:32
pittiinfinity: well, production gets called on a source package; I assume your test that does this comparison is newer than the binaries in wily?08:33
pittiinfinity: i. e. if your --built-tree is newer, you also need to include the newer .debs in the adt-run to run against those instead of wily's binaries08:33
infinitypitti: I'm running against a source package that matches the binaries in wily-proposed.  Which means the testbed needs to upgrade and reboot.  Which I assume it does in prod.08:33
pittiinfinity: or enable proposed08:34
infinitypitti: proposed is enabled on the commandline.08:34
pittiinfinity: yes, that's mentioned on http://packaging.ubuntu.com/html/auto-pkg-test.html#executing-the-test08:34
infinityOh, wait, maybe I missed -U08:34
infinityLet's see if that fixes it.08:34
pittiinfinity: yes, --apt-pocket only adds the apt source, doesn't run apt-get08:35
infinitypitti: Yeah, bad copy-pasta on my part.08:36
infinityAhh, lovely.08:36
infinityadt-run [02:36:44]: rebooting testbed after setup commands that affected boot08:36
infinityThat looks more promising.08:36
mardymvo: hi! Do you have some minutes to help me investigate bug 1454210?09:20
ubottubug 1454210 in webapps-sprint "accounts are lost each time the app is updated from the store or run on the device from qtc" [High,Triaged] https://launchpad.net/bugs/145421009:20
mvomardy: let me have a look09:23
mvomardy: that bug is confusing, so it only removes evernote accounts but nothing else? click does not touch userdata (yet) on upgrade. it will stop the app though09:27
mardymvo: so, we have a click hook in OA, which has a pattern to copy some files to ~/.local/share/online-accounts-hooks/09:29
mardymvo: then we have a hook processor which reads these files and generates a more elaborated version under ~/.local/share/accounts/providers/09:30
mardymvo: this hook processor also takes care of removing stale files and accounts, when the corresponding app gets removed09:30
mardymvo: the way it works, is that it scans ~/.local/share/accounts/providers/, and then it tries to find the corresponding originating file in ~/.local/share/online-accounts-hooks/09:31
mardyif it doesn't find it, then it deduces that the app has been removed, and therefore removes the file in ~/.local/share/accounts/providers/ and any created accounts09:31
mardymvo: does this sound correct to you? ^09:32
mardymvo_: did you miss some lines?09:32
mvo_mardy: sorry, network issues, the last I got was "seconds)09:32
mvo_<mardy> mvo: this hook processor also takes care of removing stale files and accounts, when the corresponding app gets removed"09:32
mardymvo_: ok, I'll repaste09:32
mardymvo_: the way it works, is that it scans ~/.local/share/accounts/providers/, and then it tries to find the corresponding originating file in ~/.local/share/online-accounts-hooks/09:32
mardymvo_: if it doesn't find it, then it deduces that the app has been removed, and therefore removes the file in ~/.local/share/accounts/providers/ and any created accounts09:33
mardymvo_: does this sound correct to you? ^09:33
mardymvo_: the files are named after the short app id (that is, without the version number)09:33
mvo_mardy: yes, makes sense09:34
mvo_mardy: so one fix would be for click to behave differently I guess - I need to look first why its doing what its doing09:34
mardymvo_: mmm... actually, wait... the hook pattern we use keeps the version number09:34
mardymvo_: ok, I guess that I have something to fix there, I should try to match the unversioned file09:35
mvo_mardy: ok, thanks. let me know how it goes and good luck :)09:35
mardymvo_: ok, if you don't here from me, then all it's good on your side :-)09:35
jamespageplease could an archive-admin merge lp:~james-page/+junk/sync-backlist-openstack into the sync backlist - some updates for openstack projects09:46
cjwatsonjamespage: I remain confused why we're blacklisting these at all.09:51
cjwatsonjamespage: Surely we have "ubuntu" substrings in our versions.09:51
jamespagecjwatson, I'm happy just to drop them all tbh - I just tripped on trying to sync a client package from debian09:52
jamespagecjwatson, you are quite correct - they would always show as a merge09:52
jamespagecjwatson, ok I've dropped all openstack packages from my branch - ok to go with that?09:54
cjwatsonjamespage: The only one there might be any justification for would be openstack-meta-packages09:54
cjwatsonjamespage: Do you want that to pop into wily?09:54
jamespagecjwatson, let me check on openstack-meta-packages09:55
infinityjamespage: openstack-meta-packages probably conflicts conceptually with the "openstack" package that I'm waiting on stokachu to reupload.10:24
infinityjamespage: It doesn't actually conflict, but I imagine confusion if we ship both.10:25
jamespageinfinity, ok - lets leave that blacklisted still - I think it relies on a load of features in the debian versions of those packages we don't support in ubuntu10:38
jamespageinfinity, cjwatson: lp:~james-page/+junk/sync-backlist-openstack updated10:40
caribouQ: When adding an upstart job to an existing package, does the sysVinit script get automatically inhibited or we need to add the 'init_is_upstart' override ?10:43
ogra_caribou, for what release ?10:44
caribouogra_: Trusty10:44
ogra_upstart is gone (for system statup)10:44
caribouogra_: yeah, I know it's for a Trusty SRU10:44
caribouok, I think I found the answer :10:45
caribouwhen the package is installed with an upstart job, the sysVinit script is installed but not enabled10:46
caribouI'll put the override, in case someone enable the script by accident10:47
cjwatsonjamespage: merged; give it 5min or so to propagate before you try syncpackage again10:47
cjwatsoncaribou: You should follow https://wiki.ubuntu.com/UpstartCompatibleInitScripts10:47
cariboucjwatson: thanks for the URL10:48
jamespagecjwatson, thankyou10:52
=== soee_ is now known as soee
=== MacSlow is now known as MacSlow|lunch
=== _salem is now known as salem_
=== MacSlow|lunch is now known as MacSlow
rbasakinfinity: around? docker.io backports incoming. Preview in https://launchpad.net/~docker-maint/+archive/ubuntu/staging/+packages - do you want me to just throw all of this at the SRU queues?12:42
rbasakinfinity: bug is https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1454719 - shall I create a task for each package being backported?12:42
ubottuUbuntu bug 1454719 in docker.io (Ubuntu Vivid) "docker.io update to 1.6.1" [Wishlist,Triaged]12:42
=== anthonyf is now known as Guest64410
infinityrbasak: Should be tasks for everything, yes.12:48
rbasakinfinity: OK bug updated and everything is in the queue now13:12
infinityrbasak: Ta.13:13
LocutusOfBorg1Hi Folks, I see libjsoncpp still in universe pocket, is it normal?13:32
LocutusOfBorg1talking about bug 1461517 and comment #313:32
ubottubug 1461517 in libjsoncpp (Ubuntu) "[MIR] libjsoncpp" [Undecided,Fix committed] https://launchpad.net/bugs/146151713:32
LocutusOfBorg1there is a serious bug against libjsoncpp and I merged in Debian the relevant delta13:33
LocutusOfBorg1so I would like to ask a plain sync ASAP13:33
LocutusOfBorg1but I don't know how this deals with the MIR request13:33
infinityLocutusOfBorg1: I'll have a look at both.13:34
LocutusOfBorg1infinity, it's almost dinstall time in debian13:34
LocutusOfBorg1so the sync is not possible (yet) I guess ;)13:34
dokowgrant, stealing your ustr merge13:34
mhall119pitti: I'm not familiar with merge-o-matic13:35
infinityLocutusOfBorg1: Where's this new cmake that the MIR talks about?13:35
LocutusOfBorg1-proposed I guess13:35
infinityOh, so it is.13:36
infinitycomponent-mismatches-proposed isn't showing the promotion.  Grr.13:36
LocutusOfBorg1(I feel guilty for the cmake merge, this is why I'm bothering so much :p )13:36
infinityLocutusOfBorg1: Guilt is a good motivator.13:37
LocutusOfBorg1and the love for cmake is a good motivator for a merge13:37
infinityLocutusOfBorg1: Tell me more about this "broken shlibs file" fixed in -4...13:38
infinityLocutusOfBorg1: Is it so broken that we don't want things building against -3?13:38
infinityLocutusOfBorg1: Should I remove it from -proposed?13:39
LocutusOfBorg1yes, exactly13:39
LocutusOfBorg1that would be awesome13:39
LocutusOfBorg1it isn't generating the shlibs:depends correctly, so packages built against libjsoncpp-dev won't depend on libjsoncpp013:39
infinityLocutusOfBorg1: Oh, that's quite unfortunate.  Do we know if anything's been built with that breakage so far? :/13:40
LocutusOfBorg1please look at the debian bug in -release13:40
LocutusOfBorg1I can do something similar for ubuntu13:40
LocutusOfBorg1anyway I guess the answer is "nothing"13:41
infinityLocutusOfBorg1: If you could check the rdeps and see if anything was built against the broken version, that would be great.13:42
infinityLocutusOfBorg1: Hopefully, the answer is no, but best to know.13:42
infinityLocutusOfBorg1: And I've removed it from -proposed for now.  -4 can be synced when LP learns about it.13:42
LocutusOfBorg1sysdig is built against the old jsoncpp13:43
=== rickspencer3_ is now known as rickspencer3
infinityLocutusOfBorg1: sysdig is broken on ARM anyway, can kill two birds with one stone by just deleting it and waiting for a new Debian sync that fixes that. :P13:46
infinityLocutusOfBorg1: Anything else?13:48
LocutusOfBorg1much stuff built against the old version13:50
LocutusOfBorg1kopete was a lucky case, uploaded the day before libjsoncpp, but I looked at all the build logs and they are fine (picked up the old one everywhere)13:50
infinityLocutusOfBorg1: Just so I'm sure I'm parsing that correctly: the only broken package was sysdig, then?13:52
infinityLocutusOfBorg1: Which I've just removed wholesale, since it was FTBFS on ARM anyway, so meh.  No need to rebuild it.13:52
LocutusOfBorg1broken is anything depending on 0.10.2-1+13:53
LocutusOfBorg1and nothing is built against it13:54
LocutusOfBorg1many packages are built against the old 0.6 who was fine13:54
infinityLocutusOfBorg1: Okay, that's what I said. :)13:54
LocutusOfBorg1I just had a trouble for kopete, uploaded on the day before, but it built quickly13:55
LocutusOfBorg1and with the old version13:55
LocutusOfBorg1so I guess syncing it, and MIRing it would be fine13:55
infinityLocutusOfBorg1: MIR already sorted.13:55
infinityLocutusOfBorg1: Can sync when LP knows what's up.13:55
LocutusOfBorg1so now cmake starts building?13:56
infinityShould do soon, yeah.13:56
infinityAssuming it can build against 0.613:56
infinity(If it can't, it should have a versioned build-dep, which it doesn't, so...)13:56
LocutusOfBorg1wow, yes, actually I built and tested against 0.613:57
LocutusOfBorg1I got the trouble because my ppa had universe enabled13:57
LocutusOfBorg1the only problem is actually than the old jsoncpp wasn't versioning correctly14:00
LocutusOfBorg1infinity, is that a problem?14:00
LocutusOfBorg1bug 121822014:01
ubottubug 1218220 in libjsoncpp (Ubuntu) "[MIR] libjsoncpp" [Undecided,Won't fix] https://launchpad.net/bugs/121822014:01
LocutusOfBorg1this is why I was trying to merge the new one14:01
pittiLaney: in case you are interested, the udisks2 regression is tracked in bug 146608114:02
ubottubug 1466081 in systemd (Ubuntu) "[udev] no uevent when block devices change" [High,Triaged] https://launchpad.net/bugs/146608114:02
infinityLocutusOfBorg1: I don't recall what I meant by that, since it was two years ago...14:02
LocutusOfBorg1it was lacking of a sane versioning ABI14:03
infinityLocutusOfBorg1: Okay, well, it's still libjsoncpp0, I don't see how that solved the problem. :P14:03
LocutusOfBorg1and this is fixed with the new one, I would like to cancel cmake builds and wait for the new jsoncpp, but you are the boss, not me :)14:03
LocutusOfBorg1this is "fixed" because upstream tracks ABI changes closely now14:04
dokotracking ABI changes closely and keeping the soversion?14:07
LocutusOfBorg1yes, I should bother them to bump the soversion14:10
dokoinfinity, can you do the dpkg merge?14:10
jdstrandpitti: re seccomp, I don't mind at all. merge away :)14:11
pittijdstrand: ack :)14:13
jdstrandpitti: fyi, I also did submittodebian on the autopkgtests and I'm discussing that with Debian14:13
pittijdstrand: yes; I asked kees yesterday and he seemed to think the nature of these tests is more like "upstream test suite", not a package integration one14:14
infinitydoko: Yeah, I think 1.18.1 has probably cooked enough by now.14:15
jdstrandyes, he does. I think he is right about some but not all :) we'll figure it out14:15
LocutusOfBorg1is cmake https://launchpad.net/ubuntu/+source/cmake/3.2.2-2ubuntu1 still building on armhf?14:17
LocutusOfBorg1I'm getting oops14:17
infinityLocutusOfBorg1: LP bug.  Under investigation. :P14:20
infinityLocutusOfBorg1: I might have hit a button too hard.14:20
LocutusOfBorg1is that your hand? http://ecx.images-amazon.com/images/I/41fXAZENBZL.jpg14:22
dokopitti, could you have a look at https://bugs.launchpad.net/ubuntu/+source/sessioninstaller/+bug/1440368 ? or find somebody from desktop (although this is foundations)14:43
ubottuUbuntu bug 1440368 in sessioninstaller (Ubuntu) "sessioninstaller should be ported to Python3" [Undecided,New]14:43
Laneypitti: thanks for looking, seems like a real real regression - yay for tests14:48
cjwatsonLocutusOfBorg1: DB row fixed, that build is (I'm told) intentionally cancelled.15:27
barryslangasek: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1324391/comments/19  (thanks bdmurray!)15:35
ubottuUbuntu bug 1324391 in python-pip (Ubuntu Trusty) "pip 1.5.4 import an invalid dependencies " [High,Fix committed]15:35
hyperairhi. could someone let banshee into vivid-updates please? the bug has been marked verified-done for a while now15:36
LocutusOfBorg1yes cjwatson it should be cancelled, thanks!15:41
bdmurrayhyperair: its been released15:43
hyperairyay thanks15:43
=== zumbi_ is now known as zumbi
hyperairbdmurray: launchpad doesn't seem to have updated yet though15:44
cjwatsonhyperair: https://launchpad.net/ubuntu/+source/banshee/+publishinghistory -> pending publication15:48
hyperairah, thanks15:48
LocutusOfBorg1infinity, syncpackage libjsoncpp ?16:13
LocutusOfBorg1still not good16:14
infinitysyncpackage: Error: Debian version 0.10.2-4 has not been picked up by LP yet. Please try again later.16:14
LocutusOfBorg1requestsync doesn't show the error16:14
LocutusOfBorg1but syncpackage does16:14
infinityLocutusOfBorg1: It does if you pass -V16:14
infinityOh, requestsync.  I never use that, for obvious reasons.16:14
infinityAnd it might be buggy with rmadison returning multiple versions in unstable.16:15
infinityI was just knee-deep in that code a couple of days ago, perhaps I should dive back in.16:15
LocutusOfBorg1infinity, some hours ago it was failing at the begin with "ubuntu has an higher version", now seems to go a little after16:16
LocutusOfBorg1syncpackage: D: Source package libjsoncpp is temporarily blacklisted (blacklisted_current). Ubuntu ignores these for now. See also LP: #84137216:16
LocutusOfBorg1syncpackage: Source libjsoncpp -> wily/Proposed: current version 0.6.0~rc2-3.1ubuntu1, new version 0.10.2-416:16
ubottuLaunchpad bug 841372 in Launchpad itself "Incorrect auto-blacklisting in DSD?" [Low,Triaged] https://launchpad.net/bugs/84137216:16
LocutusOfBorg1I see it there https://launchpad.net/debian/+source/libjsoncpp/0.10.2-416:16
LocutusOfBorg1lol I asked at the same time16:17
LocutusOfBorg1now should be fine16:17
LocutusOfBorg1the whole borg community thanks you16:19
ogra_LocutusOfBorg1, i thinnk he'd be happy with only 7of9 :)16:20
infinityogra_: But why rule out 1 through 6?16:20
LocutusOfBorg1ogra_, I would be happy too :D16:20
pittiarges: oh, you are doing SRU today?16:28
argespitti: yes... why? : )16:28
pittiarges: could we release utopic/vivid for bug 1461425 today? there's already the next round of updates in bug 146466916:29
ubottubug 1461425 in postgresql-9.4 (Ubuntu Vivid) "New upstream microreleases 9.1.17, 9.3.8, 9.4.3 - fixes regression in previous update" [Undecided,Fix committed] https://launchpad.net/bugs/146142516:29
ubottubug 1464669 in postgresql-9.4 (Ubuntu Vivid) "New upstream microreleases 9.1.18, 9.3.9, 9.4.4" [Undecided,In progress] https://launchpad.net/bugs/146466916:29
pittisorry about that, this was a bit crazy16:29
pittishold be back to one update every 3 months now16:29
argespitti: ah perfect i see you went through the jenkins 'failures'. I'll work on releasing that then reviewing the next round16:30
=== Elimin8r is now known as Elimin8er
=== tarpman_ is now known as tarpman
pittiarges: cheers!16:54
LocutusOfBorg1pitti, do you think libjsoncpp is good for a cmake rebuild?17:00
LocutusOfBorg1I mean, rebuilding cmake should pick the proposed one, right?17:00
cjwatsonI don't think the new binaries are entirely published yet; at least rmadison doesn't show them17:01
cjwatsonBut once they are, a rebuild will pick them up17:01
LocutusOfBorg1seems it is restarted17:03
seb128stgraber, hey http://iso.qa.ubuntu.com/user/register?destination=qatracker "Have you forgotten your password?" points to http://iso.qa.ubuntu.com/user/password which is invalid17:04
cjwatsonLocutusOfBorg1: I don't know what you mean by automagically.  Builds in -proposed fetch build-dependencies from -proposed.17:04
seb128stgraber, do you know what would be the right url to use?17:05
seb128also I'm trying to log through sso and it tells me that a seb128 user already exist17:05
cjwatsonHopefully whoever retried those builds checked.17:05
LocutusOfBorg1it was on "build cancelled" state, do the retry happen automatically?17:05
cjwatsonLocutusOfBorg1: No, only manually.17:05
LocutusOfBorg1ack thanks17:06
stgraberseb128: it's all Ubuntu SSO, no local accounts17:06
stgraberseb128: and yeah, we can't disable those links, the best we can do is make them fail17:07
cjwatsonLocutusOfBorg1: The master site has the new versions at the moment, so it's hopefully OK.17:07
seb128stgraber, well, sso fails telling me that "The name seb128 is already taken."17:08
stgraberseb128: ok. We had that happen ocasionally with old accounts, I can nuke your account in the DB which will solve that, just need to reown the data you have in the DB first17:08
seb128stgraber, I guess I've an account from the before sso time but I don't remember the password17:08
seb128stgraber, thanks17:08
stgrabermanually doing the SSO link is something I haven't figured out yet, so nuking the old account is easier :)17:09
stgraberwell, I could also rename the old account, that should work17:09
=== salem_ is now known as _salem
seb128you can nuke it as far as I'm concerned17:09
stgraberseb128: try now17:10
Laneystgraber: after you fix his account, can you see why the rebuild I just requested failed? :)17:10
Laney(see the email)17:10
Laneyperhaps it needs tweaking to do a cron.preinstalled build or something17:10
seb128stgraber, "17:10
seb128Error message17:10
seb128The e-mail address seb128@ubuntu.com is already registered. Have you forgotten your password?"17:10
stgraberdamn, let me change that too :)17:11
* Laney screams at the rain - washing is out17:11
* Laney runs17:11
stgraberseb128: try now17:11
seb128stgraber, works! thanks ;-)17:12
stgraberLaney: looking17:12
stgraberLaney: desktop next I assume?17:14
* Laney is damp17:14
stgraberok, so I see 3 requests (one for each product) 10min ago17:15
stgraberDB state is 3 which means, built according to nusakan but not published yet17:16
LaneyI got failure emails17:16
stgraberah, must have removed them without reading them, can you bounce them back to me?17:16
infinityLocutusOfBorg1: cmake seems to have happily built against the new libjsoncpp.  Cheers.17:17
Laneystgraber: It needs to have SUBPROJECT=system-image and run cron.daily-preinstalled17:17
infinityCuriously, it tried to build them on the old livefs builders instead of on LP.17:19
infinityDidn't even know that codepath still existed.17:19
stgraberinfinity: yeah, still happens when there's no LP project setup in the config17:30
stgraberlikely to fail horribly as we drop those old builders though :)17:30
=== _salem is now known as salem_
=== tlyu_ is now known as tlyu
dobeydoes anyone know how to do the equivalent of "python3 -m testtools.run discover" using python3-covearge?18:18
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== TheMaster is now known as Unit193
pittiLocutusOfBorg1: sorry, what about libjsoncpp? (I have no idea about C++ or cmake, what was the problem there?)20:25
infinitypitti: It's all sorted.20:59
infinitypitti: Also, I fixed the linux autopkgtests.  Merry Christmas.21:01
pittiinfinity: I saw, great job!21:01
infinitypitti: The best part was that after I fixed it all, I noticed Brad had (most of) the same changes staged in another branch he just hadn't gotten around to merging.21:02
infinitypitti: So, yay for duplicated work. ;)21:02
infinity(This is really, really, really not our week for kernel stuff)21:02
pittiutlemming: wrt. bug 1262951, I noticed that this is incompatible with what Debian's ifupdown now does: they include all files in /etc/network/interfaces.d/ which *don't* have a suffix, and that cloud specific change only includes *.cfg files21:03
ubottubug 1262951 in Ubuntu "cloud-images /etc/network/interfaces shoud source-directory interfaces.d" [Medium,Fix released] https://launchpad.net/bugs/126295121:03
pittiutlemming: what would I report this against?21:03
infinitypitti: I'd guess cloud-init and curtin, at least, probably use that facility.21:04
infinitypitti: And the only sane way forward would be to merge the two behaviours, including no-suffix and *.cfg, but nothing else.21:04
infinitypitti: IMO.21:04
pittiyeah, I guess so; I. e. additionally have the source-directory /etc/network/interfaces.d/ which Debian does21:05
infinityCause trying to mangle things on upgrade might end in tears.21:05
pittione doesn't usually dist-upgrade cloud instances, so that shouldn't be such a big deal21:06
pitti(i. e. mangling /etc/network/interfaces)21:07
infinitypitti: Lots of people dist-upgrade cloud instances.21:07
infinitypitti: If you're not a hip and cool "my whole life is ephemeral" cat, starting with a cloud image and dist-upgrading is perfectly reasonable.21:08
infinitypitti: But also, I'd be willing to bet curtin uses the same bits (maybe not, but worth a check), and maas+curtin for base installs is generally less cloudy.21:08
pittiwell, at least appending that line to /e/n/i on upgrade is not that big of a deal, but as it isn't really owned by any package it still bears the question where to put that21:09
pitti(ifupdown presumably)21:09
infinitypitti: Oh, if it's only included in the config file, not a default include in the source, it might be just as valid to just start doing this on new installs only.21:10
infinitypitti: It's not like old installs will (as a general rule, anyway) start growing new interfaces that people expect to configure that way?21:10
infinitypitti: But, YMMV, I dunno.21:11
pittiyeah, hence my original question what to report this against -- is that cloud-init? or some cloud-image-builder-thingy?21:11
pittithe bug above is against "Ubuntu"21:11
infinitypitti: Probably cloud-init has the affected code.21:11
infinitypitti: And maybe curtin, like I said.  And who knows what else.21:11
infinityd-i uses interfaces snippets now too, I thought.21:11
infinityYeah, d-i does, and also writes out 'source /etc/network/interfaces.d/*'21:13
infinityWhich seems like neither of the behaviours you described...21:13
infinitynetcfg (1.127) unstable; urgency=medium21:14
infinity  * Add support for /etc/network/interfaces.d/ by adding a "source"21:14
infinity    directive (Closes: #770078). It can be replaced with a21:14
infinity    "source-directory" one during the next release cycle.21:14
infinitynetcfg (1.127) unstable; urgency=medium21:14
infinity  * Add support for /etc/network/interfaces.d/ by adding a "source"21:14
infinity    directive (Closes: #770078). It can be replaced with a21:14
infinity    "source-directory" one during the next release cycle.21:14
infinity -- Cyril Brulebois <kibi@debian.org>  Sun, 04 Jan 2015 22:48:47 +010021:14
infinityOops, stutter paste.21:14
infinitypitti: So, netcfg in Debian hasn't caught up to the new world order.  d-i still sources *, rather than source-directory.21:16
infinitypitti: In conclusion, this is all a bit of a mess right now.21:16
pittiyay consistency21:17
infinitypitti: So, I think the right answer here is "hunt down all installers, and change what they do"... What ifupdown does is irrelevant, since 99% of the time, it's not writing interfaces(5)21:18
infinitypitti: And if it's trying to change any old config files on upgrade, that would be massively wrong.21:18
infinityAlso, yes, yay consistency.21:19
infinitynetcfg still appears to write everything to interfaces(5) too.  It could really use a rewrite to write per-interface to the .d directory.21:21
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== sergiusens_ is now known as sergiusens
=== pgraner is now known as pgraner-afk
hallyndo-release-upgrade -d -f noninteractive.  should work?23:29
sarnoldhallyn: are you hitting this? https://bugs.launchpad.net/ubuntu/+source/apt/+bug/145223823:32
ubottuUbuntu bug 1452238 in apt (Ubuntu) "Failed to upgrade system from 14.04" [Medium,Confirmed]23:32
hallynsarnold: nah, nothing so drastic.  it just isn't being noninteractive, sits and waits for me to hit y/enter/ several times.23:33

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