[01:45] <jbicha> Bluefoxicy: you could file a bug and use the tag upgrade-software-version
[01:46] <jbicha> since monodevelop is currently synced with Debian, you can also file a bug against the Debian package, severity wishlist
[07:43] <pitti> Good morning
[08:18] <ginggs> morning pitti!  are you up for looking at pandas LP: #1643151 ?  fewer removals needed now
[08:28] <pitti> ginggs: I really don't like removing pandas, they are endangered and cute!!
[08:28] <pitti> ginggs: (looking ☺ )
[08:29] <didrocks> turning them into happy pandas is a way to remove sad pandas :)
[08:29] <ginggs> pitti: true, but they have reproducibility problems
[08:29] <pitti> ginggs: so maybe you should add a Depends: to sextractor?
[08:43] <pitti> ginggs: hmm, do you have a list of all binaries that need to be removed?
[08:43]  * pitti is piecing them together with reverse-depends, but you may already have it
[08:44] <ginggs> pitti: sorry i don't have a single list with all of them handy
[08:45] <pitti> ok, nevermind
[09:04] <pitti> ginggs: http://paste.ubuntu.com/23622919/ ← looks plausible?
[09:05] <pitti> (took a bit, some binaries are weird)
[09:05] <ginggs> pitti: looks way more than i expected, let me check
[09:07] <ginggs> pitti: libsopt* shouldn't be on that list, it no longer depends on pandas
[09:07] <pitti> ginggs: that's reverse-depends and binaries of reverse-build-depends, minus packages that are only in -proposed
[09:09] <pitti> ginggs: ok, dropped
[09:12] <ginggs> pitti: thanks very much
[09:12] <pitti> ginggs: rest looks good?
[09:12] <ginggs> oh wait
[09:13] <ginggs> i misunderstood what you meant by dropped
[09:13] <ginggs> pitti: glueviz (and others) only build arch:all packages
[09:14] <pitti> ginggs: but these still need to be removed on these arches
[09:14] <pitti> .. I think
[09:14] <pitti> well, they would come back next time it gets built, but they would be uninstallable
[09:15] <ginggs> but there is no such thing as glueviz 0.9.0+dfsg-1 arm64 binary, is there?
[09:16] <pitti> it's published there
[09:16] <pitti> I don't think it makes much of a difference -- it's either present and uninstallable, or not publshed there, but will come back with the next build
[09:18] <ginggs> pitti: i don't understand.  where do you see glueviz is published for arm64?
[09:18] <pitti>  glueviz      | 0.9.0+dfsg-1 | zesty/universe          | source, all
[09:18] <pitti> ginggs: well, if you prefer I can remove them, if you have a list of arch:all packages from that list
[09:18] <ginggs> i was just going to paste that
[09:19] <pitti> but I'd rather remove it from these arches too
[09:19] <ginggs> pitti: so rmadison says source,all - i don't see arm64, but i'm just not understanding, so please go ahead
[09:19] <pitti> ack
[09:27] <sil2100> fossfreedom: hey! Let me take a look at your cdimage merge in a bit :)
[09:31] <fossfreedom> sil2100 - thanks!
[09:45] <ginggs> pitti: thanks for dealing with those pandas, it was the humane thing to do
[09:45] <pitti> heh
[09:47] <jbicha> pitti: if you're doing removals, could you look at bug 1649163 ?
[10:01] <pitti> jbicha: done
[10:01] <tjaalton> looks like plasma-framework is blocking mesa, test on s390x has failed since quite a time
[10:01] <jbicha> thanks
[10:05] <xnox> tjaalton, right. but i'm pretty sure plasma-framework does not care about s390x.
[10:06] <xnox> infinity, could you please do the hints magic for plasma-framework s390x test? ^
[10:06] <tjaalton> that too
[10:23] <doko> xnox, cjwatson: does haskell defaults to -O0 on s390x?
[10:25] <doko> hmm, haskell-xmlhtml builds in unstable
[10:26] <xnox> doko, i didn't think so. i thought the "advanced" haskell was missing with some fancy features.
[10:26] <xnox> whatever that thing was.
[10:29] <xnox> maybe that's not true any more. ghc provides look the same and have ghc-dynamic and ghc-ghci
[10:30] <xnox> doko, you are looking at rebuild results?
[10:30] <doko> yes, but gcc-7 only for now
[10:31] <xnox> https://launchpad.net/ubuntu/+source/haskell-xmlhtml/0.2.3.5-3
[10:31] <xnox> did not build on s390x in release....
[10:31] <doko> right, but the file succeeds to build when -O1 is used
[10:31] <xnox> =(
[10:32] <doko> I assume this is our limitation on memory/swap
[10:32] <doko> $ wc -l ghc_12.i
[10:32] <doko> 5146360 ghc_12.i
[10:32] <doko> -rw-rw-r-- 1 ubuntu ubuntu 207693501 Dec 13 10:15 ghc_12.i
[10:33] <doko> try 207693502 ;p
[10:33] <doko> try ubuntu 207693502 ;p
[10:33] <doko> heh
[10:38] <cpaelzer> Hi, I'd have an MRE question
[10:38] <cpaelzer> I know that for a totally new version one has to upload the new orig tarball, but I wondere how that works with an MRE
[10:38] <cpaelzer> zesty already has the newer orig tarball - so one could say LP has it
[10:38] <cpaelzer> but (so far) yakkety does not
[10:39] <cpaelzer> now I want to properly upload this for MRE and wonder if I have to set -sa or not on buildpackage to include the orig tarball on the upload
[10:42] <xnox> cpaelzer, largely irrelevant. either your upload will be rejected straight away, or will hit the unapproved queue.
[10:42] <xnox> cpaelzer, you can use -sa alway... and launchpad will discard duplicate tarballs for you.
[10:49] <cpaelzer> xnox: thank, the latter is interesting as I thought to read a warning that it might be rejected if it has one already
[10:49] <cpaelzer> xnox: I cant find it but maybe that triggers only if it is different which might be a perfect case to reject it
[10:53] <cpaelzer> xnox: ah here dput is what is telling me "Package includes an .orig.tar.gz file although the debian revision suggests that it might not be required. Multiple uploads of the .orig.tar.gz may be rejected by the upload queue management software."
[11:02] <pitti> xnox: nice, apt full-upgrade on my VM marks libcgmanager0 and upstart for auto-removal
[11:02] <pitti> xnox: thanks for landing unity-greeter!
[11:03] <xnox> cpaelzer, be a rebel, ignore warnings.
[11:04] <xnox> cpaelzer, launchpad enforces that checksum of the .orig.* in the .dsc remains the same. whether you upload one (again) or not is irrelevant, as long as there is at least one.
[11:04] <xnox> at least one copy.
[11:04] <pitti> xnox: I still have indicator-network running (from gnome-session), that's still outstanding or unexpected?
[11:05] <xnox> pitti, still outstanding
[11:05]  * cpaelzer is not so rebel-ish most of the time, but thanks for the quote xnox - I feel safer now!
[11:05] <xnox> pitti, i have a branch somewhere for it, but not landed yet.
[11:22] <fossfreedom> sil2100: thanks for the review.  Much appreciated.
[11:24] <fossfreedom> sil2100: I presume the DMB needs to officially approve ~ubuntubudgie-dev ?
[11:25] <sil2100> fossfreedom: I think so! I need to bring this up with them as enabling a new flavor is something new to me!
[11:25] <fossfreedom> ah - makes sense.
[11:25] <sil2100> fossfreedom: it looks good to me so far but I think the DMB would need to take ownership if it, but that might be the TB's responsibility
[11:25] <fossfreedom> Quick question if I may?
[11:25] <sil2100> Sure
[11:26] <fossfreedom> The seed "owner" is me - I'm fuzzy how to upload a bzr branch as a team (ubuntubudgie-dev) rather than myself.  Any thoughts?
[11:27] <sil2100> fossfreedom: if you go to the seed branch details, you can then go to 'Change branch details'
[11:28] <sil2100> fossfreedom: there you should be able to change the owner
[11:28] <fossfreedom> looking...
[11:28] <sil2100> fossfreedom: once you do that you should still be able to bzr push to it as normal since you're a member of the team
[11:30] <fossfreedom> sil2100: thanks - I think that worked. the branch is now called "lp:~ubuntubudgie-dev/ubuntu-cdimage/ubuntu-cdimage"
[11:31] <sil2100> \o/
[11:31] <sil2100> Same for the seeds?
[11:34] <fossfreedom> sil2100: think that's done as well - lp:~ubuntubudgie-dev/ubuntu-seeds/ubuntu-budgie.zesty
[11:35] <sil2100> fossfreedom: excellent, I'm poking around to see if we can get the team officially blessed
[11:35] <sil2100> Need to find out who has the power to do that - is it the TB after creating the packageset or can it be us for now
[11:36] <fossfreedom> sil2100: you sir are an officer and a gentleman.  Thanks!
[11:38] <sil2100> yw! Sorry it looks a bit chaotic so far
[11:59] <mitya57> pitti, hi, it is reported that docutils breaks sphinx autopkgtest, but is it possible to retry that with the proposed version of sphinx rather than the release one?
[11:59] <mitya57> Also, I get 500 internal server errors when trying to retry the tests :(
[12:03] <Laney> mitya57: add extra &trigger= to the URL
[12:03]  * Laney just tried a retry and it worked, maybe transient
[12:04] <mitya57> Laney, You submitted an invalid request: Malformed trigger, must be srcpackage/version
[12:05] <Laney> URL?
[12:05] <mitya57> I.e. it was https://autopkgtest.ubuntu.com/request.cgi?release=zesty&arch=amd64&package=sphinx&trigger=python-docutils%2F0.13.1%2Bdfsg-1
[12:05] <mitya57> And I changed it to https://autopkgtest.ubuntu.com/request.cgi?release=zesty&arch=amd64&package=sphinx&trigger=
[12:05] <Laney> oh
[12:05] <Laney> &trigger=package/version
[12:06] <mitya57> Laney, what should I replace python-docutils/0.13.1+dfsg-1 with?
[12:08] <Laney> you should add &trigger=sphinx/theversioninproposed if you want it to get that too
[12:11] <Laney> to the URL that you get from excuses.html, that is
[12:11] <Laney> Just append it on the end
[12:12]  * Laney . o O ( where else would you append it? )
[12:13]  * mitya57 finally got it
[12:13] <mitya57> Laney, thanks!
[12:14] <Laney> mitya57: yw
[12:14] <Laney> looks like sphinx itself has a few red tests, would be good to look at those
[12:15] <mitya57> I've looked at most logs, they don't even mention sphinx — so something unrelated
[12:16] <mitya57> But some packages definitely need fixing, like hovercraft which I'm looking at right now
[12:18] <Laney> nod
[13:02] <Bluefoxicy> ugh, this is the worst interface
[13:02]  * Bluefoxicy just finds a way to file bugs, then modifies the URL in launchpad to not be stupid.
[13:33] <Bluefoxicy> Okay, not sure if I did that right, but now Launchpad #1649580 also references Debian Bug #848038
[13:34] <Bluefoxicy> I'm not sure if Ubuntu even has a Mono team anymore
[13:59] <ginggs> pitti, re: pandas we missed removing python3-feather-format arm64, will you do it please?
[14:00] <pitti> ginggs: *flush*
[14:00] <ginggs> pitti: thanks
[14:05] <cpaelzer> robru: is there a way to splot the bileto associated autopkgtests in the queue to get an ETA feeling ?
[14:05] <pitti> cpaelzer: PPA queues are zarro (http://autopkgtest.ubuntu.com/running)
[14:06] <cpaelzer> pitti: ok, so I learned the source is the ppa queue
[14:06] <cpaelzer> pitti: but I'm missing my automated sign-off, how would I get to logs or so
[14:06] <cpaelzer> sorry, just too new to bileto in that regard
[14:06] <pitti> url?
[14:07] <cpaelzer> pitti: https://bileto.ubuntu.com/#/ticket/2290
[14:07] <pitti> cpaelzer: actually, there's one unity8 run for ticket #2233 queued
[14:07] <pitti> ... so not that
[14:07] <cpaelzer> should be libvirt
[14:08] <pitti> cpaelzer: hm, it didn't even start testing yet -- there is no link to an excuses page
[14:08] <pitti> " No packages are being considered! If you are preparing sources manually, please upload them to the PPA now."
[14:08] <pitti> I suppose you did that as the PPA has a libvirt
[14:08] <cpaelzer> pitti: they are in the ppa
[14:08] <cpaelzer> yes
[14:09] <pitti> cpaelzer: sorry, can't say, deferring to roaksoax
[14:09] <pitti> err, robru
[14:09] <cpaelzer> pitti: and I checked the "Lander Signoff" which according to Bileto docu is the next to kick of britney
[14:09] <cpaelzer> pitti: thanks for thinking through the basics with me, waiting for robru then
[14:09] <cpaelzer> robru: ^^
[14:10] <caribou> rbasak: Hi,got a minute to discuss the isc-dhcp / isc-dhcp-ddns issue ?
[14:10] <pitti> cpaelzer: try to click the "diffs" button perhaps? that's the one it keeps complaining about, not sure
[14:12] <robru> pitti: where are you seeing "no packages..."? That's quite an old status, not relevant
[14:12] <pitti> robru: I just checked the audit log for anything that might stand out
[14:12] <robru> cpaelzer: indeed, the"missing diff" status is why autopkgtests aren't running
[14:12] <pitti> robru: I didn't expect you to be awake at this hour, jetlag FTW? :-(
[14:12] <robru> pitti: yes quite jetlagged
[14:13] <cpaelzer> ok, hitting regenerate diffs now - didn't know that was a blocking step
[14:14] <robru> cpaelzer: yes, for tickets built from merges, it generates the diff at the same time it generates the source packages. When you upload manual sources though it doesn't get a chance to do that so you have to do it manually
[14:14] <rbasak> caribou: yes. Would a hangout be easiest, maybe with slashd? I don't see him online though.
[14:14] <robru> This is one of the pain points that makes MPs first class and source packages second class
[14:15] <pitti> robru: ah, that actually makes sense -- there's no way of telling when the dev is done uploading bits to the PPA
[14:15] <caribou> rbasak: yes he is, spoke to him earlier. Let me set it up
[14:15] <cpaelzer> I'm fine to note it and press it into my muscle memory over time, just didn't know
[14:15] <rbasak> caribou: ack
[14:15] <pitti> robru: although the "build" button would be slightly less confusing than the diffs one, I suppose
[14:16] <robru> pitti: for a while there was some code to auto diff but it was error prone, often triggering at inopportune times
[14:16] <cpaelzer> robru: but now generating diff failed I think, is ended with Diff missing - is there something I could do about that?
[14:16] <robru> pitti: build and diff buttons are indistinguishable if you don't have MPs
[14:18] <robru> cpaelzer: sigh, that's a race condition. Can you file a bug against lp: bileto please? Just say "status at end of diff job fails to notice new diffs"
[14:18] <cpaelzer> robru: sure I can file one
[14:19] <cpaelzer> robru: what can I do now to trigger britney for me in the meanwhile?
[14:20] <robru> cpaelzer: nothing. You need to wait  up to ~20 min for the status to correct itself, then you should see "successfully built" along with "automated signoff: queued"
[14:20] <cpaelzer> robru: ok, thanks that is fine for me
[14:20] <robru> You're welcome
[14:20] <cpaelzer> as long as I know it will continue to stumble forward I'm fine - just don't want to know it blocked
[14:21] <robru> cpaelzer: ping me again if it doesn't say "successfully built" within 20min but it should be good
[14:21] <cpaelzer> robru: ok, will do so - until then you now have bug 1649595 to track
[14:22] <robru> Thanks
[14:25] <doko> Laney: did you find out a system how to rebuild the gnat packages?
[14:26] <Laney> doko: no, just finding ones which fail autopkgtests
[14:45] <pete-woods> pitti: hi. sorry to hear you're leaving
[14:45] <pete-woods> been good working with you
[14:45] <pete-woods> had a question before you go, though
[14:45] <pete-woods> how should I go about getting stuff into python-dbusmock from now on?
[14:45] <dobey> pete-woods: what would you put into python-dbusmock?
[14:46] <pete-woods> dobey: nothing this very second
[14:46] <pitti> pete-woods: no change really; I keep maintaining this project on Github and debian
[14:46] <pitti> pete-woods: I'll probably just stop worrying about the overlays, but I figure you can do that yourself
[14:46] <pete-woods> pitti: hmm, probably not, but I can learn :)
[14:47] <dobey> pete-woods: sure. just seems like if it's a new module to mock something it should go into the project it's mocking, not python-dbusmock :)
[14:47] <pete-woods> pitti: thanks for the info :)
[14:47] <pete-woods> dobey: this would be things like the NM template, and general fixes, though
[14:48] <dobey> ah ok, though i'd say someone really needs to get the NM template upstreamed
[14:49] <dobey> aww there isn't a cups template in dbusmock. doh
[14:50] <pete-woods> but then I need to push updates to network-manager
[14:50] <pete-woods> which would likely be super slow
[14:50] <pitti> my gut feeling is that keeping the templates in dbusmock is easier all around
[14:51]  * pete-woods still doesn't know where he'd be in Canonical without pitti's dbusmock
[14:52] <pete-woods> probably having had a breakdown somewhere around the 1 year mark and quitting
[14:52] <cpaelzer> robru: it kind of worked, I got a ping in ubuntu-ci-eng that it built, and automated signed off switched to queued - but I still can't find it anywhere on http://autopkgtest.ubuntu.com
[14:52] <pitti> you might have written it yourself? :-)
[14:52] <pete-woods> pitti: I'd have tried. but my python-fu isn't that strong
[14:52] <cpaelzer> robru: neither queued, not failed/succeeded - if you spot it let me know where to look for it
[14:52] <pete-woods> it'd probably have been a C++ project, and been very tough
[14:53] <dobey> pete-woods: not that hard. i implemented something similar before dbusmock existed :)
[14:53] <robru> cpaelzer: no you're confused. "Queued" in bileto doesn't mean "i triggered your autopkgtests", it means "this is in the queue of things to have autopkgtests triggered for"
[14:53] <pete-woods> to make it as flexible as python-dbusmock I think it might have been
[14:54] <dobey> mostly it's just busy work
[14:54] <pete-woods> you can just stuff code in strings with python
[14:54] <pitti> pete-woods: most of it isn't rocket science, but writing the generic method mocks and poking in dbus-python's innards was an interesting research exercise
[14:54] <robru> Eg, eventually britney will see it and trigger autopkgtests
[14:54] <dobey> yeah, writing it in C++ would have been limiting for sure
[14:54] <cpaelzer> robru: very meta that is - thanks for un-con-fusing
[14:55] <dobey> but i can't say that i enjoy writing python inside strings in c++ as a means of writing tests, either :P
[14:55] <pitti> dobey: OOI, why would you?
[14:56] <pitti> dobey: dbusmock's primary interface is, well, d-bus, not python
[14:56] <pitti> well, the function bodies need to be python, sure (but usually they are trivial half-liners)
[14:56] <robru> cpaelzer: it's unfortunately a limitation of britney. It doesn't just trigger autopkgtests, it also does silly things like "load entire Ubuntu archive into memory", so this means it can only inspect one ticket at a time (is impossible to run two in parallel, you get OOM), so it takes a while to churn through all the tickets
[14:58] <robru> cpaelzer: eventually your ticket should say "running" and then at that point you can expect them to show up in autopkgtest infra
[14:58] <pitti> robru: well, it does super-polynomial computations over the archive graph (although in almost all practical cases i's O(n²), but you really don't want to do that on-disk :)
[14:59] <robru> pitti: yes, but it is quite the bottleneck when all you want is to trigger autopkgtests
[14:59] <pitti> robru: well, you still want installability tests too, no?
[14:59] <dobey> robru: but how do you know what to trigger, without inspecting the archive graph?
[14:59] <pitti> robru: you already disable second-stage installability, but at least the package itself should be installable in its own right
[15:00] <pitti> and rdepends calculation needs the entire archive map too
[15:00] <pitti> for britney's original intent (running once for every distro) that's quite fine
[15:00] <robru> pitti: i suppose
[15:00] <pitti> the thing to optimize for britney would be to only do that initial loading/map building once, instead of once per silo
[15:00] <pitti> or maybe pickle it out
[15:00] <robru> Ooooooooooh pickle
[15:01] <pitti> or whatever the fastest serialization is these days :)
[15:02] <robru> Poor cpaelzer just wants autopkgtests run and here he has to wait for britney to poke every other ticket before his. Autopkgtests can run in parallel but britney has to run each ticket in series before it even notices to trigger them
[15:03] <pitti> robru: she's your's now, have fun teaching that rascal :)
[15:04] <robru> pitti: if CI train is and indication, i suppose i will spend the next 4 years rewriting it from scratch, twice
[15:04] <pitti> haha
[15:04] <pitti> robru: once in Go, and the final version in Haskell :)
[15:06] <robru> pitti: did you know m4 is Turing-complete? I once wrote a prime-number calculator using nothing but m4 macros
[15:07] <pitti> nice
[15:07] <pitti> robru: I do know that C++ templates are -- I've seen a crazy project which actually uses that in uni time
[15:08] <robru> Heh.
[15:44] <dims> cjwatson : wgrant : can you please help with lp bug 1609128? (i tried to find you a few days ago, here's some context https://irclogs.ubuntu.com/2016/12/07/%23ubuntu-devel.html#t16:24)
[15:46] <cjwatson> yeah, rolling an updated release is on my to-do list, but I'm behind on a bunch of code I need to write first
[15:48] <dims> cjwatson : i see thanks. waiting eagerly
[15:48] <cjwatson> ~/wg 119
[15:48] <cjwatson> oops
[15:51] <chrisccoulson> pitti, I guess now's a bad time to ask you if you feel like maintaining a web browser? ;)
[15:52] <pitti> chrisccoulson: slight grammar -- I'll be maintaining something that runs *in* a web browser :)
[15:52] <chrisccoulson> heh
[15:53] <chrisccoulson> pitti, it looks like it's going to be a lot of fun anyway :)
[15:55] <seb128> chrisccoulson, hey, aren't you supposed to be on holidays? ;-)
[15:55] <chrisccoulson> seb128, yep. I'm back temporarily, thanks to adobe and mozilla
[15:55] <seb128> oh right
[15:56] <seb128> the fun never stops for you, I almost forgot
[15:56] <seb128> ;-)
[15:56] <chrisccoulson> "fun" ;)
[15:56] <seb128> didn't you have a release to get out on newyear or something last year?
[15:56]  * seb128 doesn't remember the details
[15:57] <chrisccoulson> seb128, last year it was flashplayer, 28th december
[15:57] <seb128> well, dec 13th is better!
[15:57] <chrisccoulson> I don't really understand how I ended up with flash tbh
[15:58] <pitti> can we just leave it broken, and may it never come back?
[15:58] <chrisccoulson> heh
[15:58] <pitti> honest question: does anyone actually encounter flash on any non-pr0n web sites these days?
[15:58] <seb128> chrisccoulson, hope your enjoy your holidays once that round of updates is done!
[15:58] <pitti> I haven't had it installed for several years, but of course everyone uses different websites
[15:59] <chrisccoulson> pitti, I don't know. I struggle to find sites to test it with now. BBC News still seems to require it too
[15:59] <pitti> we can thank Android and phones, I think
[15:59] <chrisccoulson> s/too/though/
[15:59] <seb128> pitti, I think the website they use for the townhall calls does
[15:59] <seb128> I couldn't use it on my firefox last time
[15:59] <pitti> anything that doesn't work on a mobile browser basically ceased to exist, no?
[15:59] <pitti> seb128: bluejeans?
[15:59] <seb128> yes
[16:00] <chrisccoulson> getting rid of flash and convincing seb128 to maintain firefox should be my new years resolution
[16:00] <pitti> seb128: right, I had to use chromium for that one, not sure if it was a codec or flash issue
[16:00] <seb128> chrisccoulson, let's see how convincing you can be ;-)
[16:00] <chrisccoulson> seb128, beer?
[16:01] <seb128> lol
[16:01] <Laney> seb128 only responds to absinthe
[16:01] <seb128> beer is a start
[16:01] <pitti> ice cream has been observed to have a measurable effect too
[16:01] <seb128> not sure it's going to enough to make me agree to maintain firefox though
[16:01] <pitti> and stollen
[16:01] <seb128> Laney, shusssh
[16:02]  * seb128 is hungry now
[16:02] <chrisccoulson> me too
[16:02] <chrisccoulson> I've already over-eaten though and it's only dec 13
[16:07] <cjwatson> pitti: flash is still commonplace on websites aimed at kids, I find
[16:08] <dobey> flash is sadly still commonplace in way too many places :(
[16:08] <pitti> ah -- I wasn't trying to troll (much), but genuinely interested
[16:08] <dobey> pitti: i had to use flash yesterday to listen to a company video conf call :)
[16:08] <pitti> I surely wouldn't look at kid's websites, so that's a good data point
[16:09] <dobey> pitti: some banks use flash for certain features still
[16:18] <pitti> TTFN -- time to start the EOY holidays, IRC-less; I wish you all some nice resting and time with your family, see you back in January!
[16:18] <cjwatson> have fun!
[16:19] <dholbach> pitti, all the best!
[16:19] <roadmr> enjoy pitti !
[16:20] <cking> all the best pitti
[16:22] <popey> pitti: bluejeans - our company site for commuication from our great leaders...
[16:29] <nacc> slangasek: so I got the zend* stuff mostly sorted in zesty. But I think it's currently stuck because there is one binary package that disappears in the transition from src:zend-framework to src:zendframework (libzend-framework-zendx-php). I documented this drop in the changelog, but perhaps I should have indicated in the control that zendframework Breaks libzend-framework-zendx-php? It doesn't provide
[16:29] <nacc> or replace it, though. Just looking for some guidance on how to resolve the transition
[16:44] <xnox> juliank, mvo: today i learned what "rc" status stands for. Finally apt search told me that it's for [residual-config]
[16:45] <xnox> i always thought that it was strange to call leftover configs as "removed-configs"
[16:46] <mvo> xnox: heh
[16:47] <Laney> what does rc mean in /etc?
[16:47] <juliank> xnox: It actually stands for remove config-files
[16:47] <juliank> That is, the package is selected for removal in dpkg; but still has config-files on the system
[16:47] <Laney> "run commands" apparently
[16:47]  * Laney gets a history lesson
[16:48]  * xnox thought rc stands for stable software
[16:49] <rbasak> bdmurray: I hadn't looked at bug 1640823 again, no. Shall I review and release if appropriate during my SRU day tomorrow?
[16:49] <juliank> xnox: remote control
[16:50] <bdmurray> rbasak: Since you had an opinion I think that's appropriate
[16:51] <rbasak> bdmurray: OK will do, thanks.
[16:57] <slangasek> nacc: libzend-framework-zendx-php, is this something that would have been a top-level package users would install?
[16:59] <nacc> slangasek: yeah, it's a leaf package with no rdeps
[17:01] <nacc> barry: fyi, i've refreshed my snap, i just need to verify it still works :)
[17:04] <barry> nacc: nice
[17:09] <nacc> slangasek: or is this a consequence of needing to also delete src:zend-framework from zesty (see: LP: #1593024 c#14)
[17:09] <slangasek> nacc: so, that means someone who has that package installed will have a somewhat rocky upgrade (basically, what trips update-output can also trip a user upgrade).  Should there be a libzend-framework-zendx-php dummy package that depends on something else in the new set?
[17:10] <nacc> slangasek: right, i could do that, but there's nothing that is libzend-framework-zendx-php that is provied by zendframework, unfortunately
[17:11] <nacc> slangasek: so the zend-framework orig tarball differs from zendframework. z-f used the 'full' tarball which included unsupported/experimental extensions, zf only ships the core
[17:12] <nacc> slangasek: and so zf doesn't provide those extensions at all, or anything that replaces that functionality
[17:13] <slangasek> nacc: ok. In that case, the current packages are probably fine as-is and we just need to mangle the archive a bit to let this in
[17:15] <nacc> slangasek: ack, I wasn't finding anything in the debian manual that covered this case -- and the upgrade of the packages that are upgradeable does work (i tested that already earlier) -- it's just this one leaf package.
[17:18] <juliank> So, now that the word is out about the apt security update: I also uploaded 1.2.18 to xenial-proposed to replace the 1.2.17 in the queue there, so the queue contaisn a fixed version too
[17:19] <juliank> To prevent an accidental upload of 1.2.17, it would be wise to remove it from the unapproved queue, and only keep 1.2.18 in there
[17:19] <juliank> s/upload/approval/
[17:25] <juliank> That said, I might want to rebuild the changes file for 1.2.18 with all changes since 1.2.15
[17:41] <infinity> juliank: Yeah, can you reupload 1.2.18 with the right -v?
[17:43] <juliank> infinity: done
[17:43] <infinity> juliank: Ta.
[17:46] <juliank> Now I need to figure out when the next normal stable release updates will happen. My queues got a bit strange with the whole security business
[17:46] <juliank> s/queues/patch queues/
[17:47] <Laney> doko: For some reason libaws has built now, so maybe this ada stuff can move forward a bit
[17:47] <juliank> That is, 1.3.3 and 1.2.19 will happen at some point. Not sure when, though.
[17:47]  * Laney is off from today but might poke at it a bit if there's time
[17:47] <Laney> otherwise please do
[17:49]  * juliank is a constant bugfix cherry-picking machine
[17:56] <infinity> juliank: Why did aclocal.m4 and configure disappear?
[17:56] <juliank> infinity: What, that sounds weird.
[17:56] <infinity> juliank: (I realise they probably come back on debian/rules clean, but that still seems like poor form for an upstream tarball to not ship them)
[17:57] <juliank> Ah
[17:57] <juliank> Right
[17:57] <juliank> infinity: I accidentally passed -nc to gbp buildpackage.
[17:57] <juliank> I'll reupload one without -nc
[17:58] <juliank> Too many non-git uploads prepared the past week
[17:58] <infinity> juliank: Ta.  I assume 1.2.18 doesn't actually "exist" in the wild outside of the xenial queue?
[17:58] <juliank> Not in the tarball form :)
[17:58] <infinity> Check.
[17:58] <infinity> Then a fresh upload would be lovely.
[17:59] <infinity> debian/copyright went byebye too.  Symptom of the same oops?
[17:59] <juliank> infinity: Should be in now.
[18:03] <infinity> juliank: That looks better.  Will give it a bit of a once-over for obvious breakage and accept today.
[18:03] <juliank> neat
[18:04] <juliank> This will make sarnold very happy :)
[18:04] <infinity> He's never happy.
[18:13] <sarnold> :)
[18:14] <juliank> he smiled!
[18:14] <infinity> It's a ruse.
[18:18] <attente> hi, would anyone be able to sponsor a xenial sru for bubblewrap? https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1649330
[18:21] <infinity> juliank: Unrelated to the quality of the SRU (which I'm about to accept), but I suspect your travis.yml referencing wily all over the place might explode when we remove wily from the mirrors.
[18:22] <juliank> attente: In any case, the version number is wrong. Not sure about policy regarding adding new packages in an SRU.
[18:22] <juliank> infinity: Yeah. I'm building a PPA picking the components I need, but I'm not done yet
[18:23] <attente> juliank: what should the version number be?
[18:23] <nacc> attente: https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
[18:23] <nacc> is a good reference
[18:24] <attente> nacc: thanks
[18:24] <attente> i'll update that
[18:24] <juliank> nacc: That does not mention anything about those ~ uploads though
[18:25] <nacc> juliank: you mean, e.g. ~ppa1 etc?
[18:25] <juliank> nacc: I meant, you basically would want 0.1.4-2~ubuntu0.1
[18:25] <juliank> otherwise your version is higher than zesty
[18:26] <juliank> zesty having 0.1.4-2
[18:26] <infinity> attente: Two things.  Version should be "0.1.4-2~16.04.1" to indicate a no-change backport.
[18:26] <infinity> attente: Second thing: can you see if 0.1.2-1 from yakkety works just as well for your purposes?
[18:27] <infinity> attente: Cause xenial should *not* be higher than yakkety, so if you *need* the zesty verion, then it needs to be backported to both releases, with a really good reason why.
[18:27] <nacc> juliank: ah yes, i hadn't looked at the details of this specific case
[18:27] <attente> infinity: d'oh, of course
[18:27] <infinity> attente: (note: I'll probably reject that reason unless it's stellar)
[18:27] <infinity> attente: So, preferably, backport yakkety's version, so if it does the job, then let's do that.
[18:27] <infinity> s/so if/see if/
[18:28] <attente> infinity: thanks, i'll do that
[18:28] <infinity> attente: Basic reasoning here from my side: There's pretty much 0 chance of regression in introducing a NEW package into an old release, but updating a package in a stable release is much more potentially dangerous.
[18:28] <infinity> So, happy to handwave review and accept the yakkety version backported to xenial, once you verify it fits your needs.
[18:29] <attente> infinity: thank you
[18:31] <nacc> slangasek: infinity: do i also need AA help for the imagemagick migration? (two binaries being removed in the version change)
[18:31] <infinity> nacc: Usually not.
[18:32] <infinity> nacc: Binary removal is simulated by proposed-migration to do the installability checks, but they're not actually removed until after migration, when we get around to tidying up after you.
[18:32] <infinity> nacc: Oh.  Except for those two NBS binaries that are *in proposed*.  I'll whack those.
[18:33] <nacc> infinity: ah thanks!
[18:34] <infinity> nacc: Cleaned up for you.
[18:40] <nacc> infinity: thanks again!
[18:51] <attente> infinity: hi, i've tried the yakkety version and it works fine too. the version is also fixed: https://launchpad.net/~attente/+archive/ubuntu/test?field.series_filter=xenial
[18:55] <slangasek> nacc: yeah, when you see those kinds of messages in update_excuses, pointing the AAs at it is the right thing to do
[19:47] <nacc> slangasek: thanks!
[22:40] <locust__> Any ipmitool maintainers around?
[23:19] <doko> Laney: you shouldn't use -feliminate-dwarf2-dups, I'm told that it is broken. Passing -gz to compile and linker flags should work now
[23:28] <nacc> locust__: well, we're currently in sync with debian right now, afaict (post 16.04). What specifically do you need?