[00:10] pitti: Y'know, having a /usr/bin/\ that is, indeed, just something that returns the first argument might solve all sorts of issues. :) [00:10] that's an evil idea [01:35] infinity: Is this a seed thing or a bug on your end? bug 1641783 [01:35] bug 1641783 in lubuntu-meta (Ubuntu) "man or command not found commands not installed by alternate installer." [Undecided,New] https://launchpad.net/bugs/1641783 [01:35] ("your" meaning archive admins) [01:45] tsimonq2: man-db is in standard, if your alternate setup isn't enabling standard by default that's a bug somewhere. Whose bug, I'm not sure without looking. [01:46] infinity: I think maybe I'll poke around and take a look at the recent commits to d-i. [01:46] infinity: But thanks. [01:47] tsimonq2: d-i has almost nothing to do with it. [01:47] Oh? [01:47] tsimonq2: The default task selection should come from a preseed on the media. [01:47] infinity: livecd-rootfs? [01:48] tsimonq2: Err, depending on what "the alternate installer" means here. The Lubuntu alternate ISO, or a minimal d-i netboot? [01:48] infinity: Lubuntu Alternate. [01:48] Kay. debian-cd, then, is what's likely to contain the magic. [01:49] Ah ok. [01:50] data/zesty/preseed/lubuntu/lubuntu.seed should probably explicitly select minimal and standard along with lubuntu-desktop, just as the live images do. [01:50] Though this has been "broken" literally forever, curious that no one cared until today. [01:50] O__O [01:51] Where are you seeing this? This thing? http://bazaar.launchpad.net/~vcs-imports/debian-cd/trunk/files [01:51] Ah nevermind, apologies. [01:51] https://code.launchpad.net/~ubuntu-cdimage/debian-cd/ubuntu [01:51] Yes, that. :) [01:52] If this is actually a regression, something subtle changed elsewhere, and I'd like to know about it. [01:52] infinity: Either nobody noticed until today (which, Lubuntu QA needs some *serious* redesign if that's the case) or it wasn't an issue until today. [01:53] (or a few days ago, to be accurate) [01:53] But I suspect your alternate has installed this way since the flavour existed. [01:53] O__O [01:54] The only other obvious candidate for blame would be tasksel, which hasn't changed since shortly before xenial release. [01:54] infinity: So this line should read: "taskseltasksel/firstmultiselect lubuntu-desktop ubuntu-minimal ubuntu-standard" http://bazaar.launchpad.net/~ubuntu-cdimage/debian-cd/ubuntu/view/head:/data/zesty/preseed/lubuntu/lubuntu.seed#L6 ? [01:55] minimal and standard don't have the ubuntu- prefix. [01:55] Oh, ok. [01:55] But otherwise that's where they're put? [01:55] I'd have to remind myself how tasksel preseeds work, but in theory that would do it. [01:56] Ok, PR incoming. [01:56] (for consistency with how we write it in livecd-rootfs, it'd probably be "minimal standard $foo-desktop" to go from small to large. [01:56] But that's nitpicking. [01:57] Well that's fair enough. Nitpicking exists for a reason. ;) [01:59] Hrm. Could you test with xenial (and if that's broken, also trusty) first, though? [01:59] Cause I feel like tasksel *should* be doing standard by default. [01:59] How would I go about testing? [02:00] Just do a quick install of each, then "apt-get install standard^" and see if anything new is pulled in. [02:01] tsimonq2: I have a date with "not being at work" for the evening, but keep me informed. [02:01] Using the default alternate installer, or will The Best Method Ever work? :P https://help.ubuntu.com/lts/installation-guide/amd64/apds04.html [02:01] Ok, infinity . [02:02] tsimonq2: How would you test the installed by not using the installer? :P [02:02] infinity: I guess I'm asking if it matters how I run tasksel. [02:02] Good point. lol [02:02] s/installed/installer/ [02:02] Ok will do. [02:03] For people who install with debootstrap, they can run "apt-get install minimal^ standard^ foo-desktop^" all by themselves, but that's a thing ISOs are supposed to do for them. ;) [02:04] Yup. :D [02:05] infinity: I really like that method. It lets me see what I'm installing *exactly* and lets me customize it before rebooting. Reminds me of installing Arch. :P [02:06] tsimonq2: It fails entirely to be even remotely user-friendly, but yes, I have a few machines in the wild that are debootstrap-installed. Some that are remote machines that pivoted from preinstalled CentOS, two that we didn't have bootable installers for when they were installed, etc. [02:06] It's not something I'd recommend to friends and family. [02:07] Not if I wanted to remain friends and continue being in the will. [02:07] Me neither. No way. [02:08] But for all the machines that are mine I *always* debootstrap. [02:09] I even have a Chromebook and Crouton uses debootstrap. :D [02:09] tsimonq2: It started as a practical dogfooding thing (I work for Canonical, I should see what users soo, so I can fix it when it sucks), but the more we've tried to improve things, the more I've found my nerdy compulsion to be an anal-retentive sysadmin of my own machines has gone way down. [02:10] tsimonq2: If you ignore my /home (obviously), my laptop is so amazingly stock Ubuntu that me of a decade ago would probably have some choice insults for current me. [02:11] infinity: Well I don't work for Canonical (I hope one day though :P) and this machine is a Frankenstein monster. I'm running LXQt and I have a half installed KDE Plasma somewhere with a half installed Lubuntu somewhere else. Maybe even some Unity 8 left? I don't know. [02:12] I'd like to think that past me would be proud of how far we've come with out-of-the-box usability, but really, that guy built his own kernels on the regular, he clearly had unresolved issues. [02:13] * infinity -> non-IRC life. [02:13] Yeah, I like Ubuntu because I can just install it THEN make it a Frankenstein. I could never install Arch successfully, and Gentoo takes too long. :P [02:14] Every time I build my own kernel, sbuild breaks. Maybe I should do it again and file a bug. :P [02:14] o/ infinity [02:14] But yeah, sbuild breaking does NOT make me a happy camper... :/ [02:15] tsimonq2: sbuild breaking is probably a sign that your custom kernel is missing the filesystem driver for your overlay of choice (overlay, which is upstream or aufs, which isn't). [02:15] And really gone. [02:15] Yeah I think that's the issue. I don't know, when I go through the "I want to do kernel hacking" phase again, I'll file a bug. :P [02:16] It sounds awfully familiar. [02:17] (or fix my freaking setup, whatever one fixes it first :P) [03:30] UH, ADAM. [03:32] Wait... [03:32] * tsimonq2 does a dist-upgrade first [03:32] I was gonna say... [03:32] I tried installing those tasks and it proposed like 200 packages. [04:03] infinity: Reproducable with Xenial: http://pix.toile-libre.org/upload/original/1479182570.png [04:05] Grabbing Lubuntu Trusty 14.04.1 Alternate now. [05:24] -queuebot:#ubuntu-release- New binary: slixmpp [ppc64el] (zesty-proposed/universe) [1.2.1-1] (no packageset) [05:25] -queuebot:#ubuntu-release- New binary: postfix [ppc64el] (zesty-proposed/main) [3.1.3-3] (core) [05:25] -queuebot:#ubuntu-release- New binary: postfix [amd64] (zesty-proposed/main) [3.1.3-3] (core) [05:25] -queuebot:#ubuntu-release- New binary: slixmpp [i386] (zesty-proposed/universe) [1.2.1-1] (no packageset) [05:25] -queuebot:#ubuntu-release- New binary: postfix [i386] (zesty-proposed/main) [3.1.3-3] (core) [05:25] -queuebot:#ubuntu-release- New binary: slixmpp [s390x] (zesty-proposed/universe) [1.2.1-1] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: should.js [amd64] (zesty-proposed/universe) [8.4.0~dfsg-3] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: slixmpp [amd64] (zesty-proposed/universe) [1.2.1-1] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: postfix [s390x] (zesty-proposed/main) [3.1.3-3] (core) [05:27] -queuebot:#ubuntu-release- New binary: postfix [powerpc] (zesty-proposed/main) [3.1.3-3] (core) [05:27] -queuebot:#ubuntu-release- New binary: postfix [arm64] (zesty-proposed/main) [3.1.3-3] (core) [05:27] -queuebot:#ubuntu-release- New binary: slixmpp [powerpc] (zesty-proposed/universe) [1.2.1-1] (no packageset) [05:27] -queuebot:#ubuntu-release- New binary: postfix [armhf] (zesty-proposed/main) [3.1.3-3] (core) [05:32] -queuebot:#ubuntu-release- New binary: slixmpp [arm64] (zesty-proposed/universe) [1.2.1-1] (no packageset) [05:33] -queuebot:#ubuntu-release- New binary: slixmpp [armhf] (zesty-proposed/universe) [1.2.1-1] (no packageset) [08:29] thanks pitti for fixing the testsuite [10:01] -queuebot:#ubuntu-release- Unapproved: bash (trusty-proposed/main) [4.3-7ubuntu1.5 => 4.3-7ubuntu1.6] (core) [10:06] -queuebot:#ubuntu-release- Unapproved: rejected bash [source] (trusty-proposed) [4.3-7ubuntu1.6] [10:08] -queuebot:#ubuntu-release- Unapproved: bash (trusty-proposed/main) [4.3-7ubuntu1.5 => 4.3-7ubuntu1.6] (core) [10:25] -queuebot:#ubuntu-release- Unapproved: util-linux (trusty-proposed/main) [2.20.1-5.1ubuntu20.7 => 2.20.1-5.1ubuntu20.8] (core) [10:29] -queuebot:#ubuntu-release- Unapproved: accepted cinder [source] (trusty-proposed) [1:2014.1.5-0ubuntu2.1] [10:30] -queuebot:#ubuntu-release- Unapproved: accepted python-glanceclient [source] (trusty-proposed) [1:0.12.0-0ubuntu1.1] [10:31] -queuebot:#ubuntu-release- Unapproved: accepted util-linux [source] (trusty-proposed) [2.20.1-5.1ubuntu20.8] [10:35] -queuebot:#ubuntu-release- Unapproved: apt (xenial-proposed/main) [1.2.15 => 1.2.16] (core) [11:24] -queuebot:#ubuntu-release- New binary: libgtkdatabox [ppc64el] (zesty-proposed/universe) [1:0.9.3.0+dfsg-2] (no packageset) [11:25] -queuebot:#ubuntu-release- New binary: libgtkdatabox [amd64] (zesty-proposed/universe) [1:0.9.3.0+dfsg-2] (no packageset) [11:25] -queuebot:#ubuntu-release- New binary: libgtkdatabox [i386] (zesty-proposed/universe) [1:0.9.3.0+dfsg-2] (no packageset) [11:26] -queuebot:#ubuntu-release- New binary: libgtkdatabox [s390x] (zesty-proposed/universe) [1:0.9.3.0+dfsg-2] (no packageset) [11:30] -queuebot:#ubuntu-release- New binary: libgtkdatabox [powerpc] (zesty-proposed/universe) [1:0.9.3.0+dfsg-2] (no packageset) [11:39] -queuebot:#ubuntu-release- New binary: libgtkdatabox [armhf] (zesty-proposed/universe) [1:0.9.3.0+dfsg-2] (no packageset) [11:40] -queuebot:#ubuntu-release- New binary: libgtkdatabox [arm64] (zesty-proposed/universe) [1:0.9.3.0+dfsg-2] (no packageset) [11:45] infinity: So it seems Trusty is not affected. [12:31] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-hard-disk-led [amd64] (zesty-proposed) [13~git20160916.6fe27b2-1] [12:31] -queuebot:#ubuntu-release- New: accepted ido-ubiquitous [amd64] (zesty-proposed) [3.14-1] [12:31] -queuebot:#ubuntu-release- New: accepted libconfig-methodproxy-perl [amd64] (zesty-proposed) [0.02-1] [12:31] -queuebot:#ubuntu-release- New: accepted libgtkdatabox [arm64] (zesty-proposed) [1:0.9.3.0+dfsg-2] [12:31] -queuebot:#ubuntu-release- New: accepted libgtkdatabox [i386] (zesty-proposed) [1:0.9.3.0+dfsg-2] [12:31] -queuebot:#ubuntu-release- New: accepted libgtkdatabox [ppc64el] (zesty-proposed) [1:0.9.3.0+dfsg-2] [12:31] -queuebot:#ubuntu-release- New: accepted libpod-elemental-transformer-list-perl [amd64] (zesty-proposed) [0.102000-1] [12:31] -queuebot:#ubuntu-release- New: accepted libwww-shorten-github-perl [amd64] (zesty-proposed) [0.1.7-1] [12:32] -queuebot:#ubuntu-release- New: accepted golang-github-pivotal-golang-clock [amd64] (zesty-proposed) [0.0~git20151018.0.3fd3c19-1] [12:32] -queuebot:#ubuntu-release- New: accepted libgtkdatabox [amd64] (zesty-proposed) [1:0.9.3.0+dfsg-2] [12:32] -queuebot:#ubuntu-release- New: accepted libgtkdatabox [powerpc] (zesty-proposed) [1:0.9.3.0+dfsg-2] [12:32] -queuebot:#ubuntu-release- New: accepted libpod-weaver-section-support-perl [amd64] (zesty-proposed) [1.007-1] [12:32] -queuebot:#ubuntu-release- New: accepted iedit [amd64] (zesty-proposed) [0.9.9.9-1] [12:32] -queuebot:#ubuntu-release- New: accepted libgtkdatabox [s390x] (zesty-proposed) [1:0.9.3.0+dfsg-2] [12:32] -queuebot:#ubuntu-release- New: accepted libgtkdatabox [armhf] (zesty-proposed) [1:0.9.3.0+dfsg-2] [12:32] -queuebot:#ubuntu-release- New: accepted node-grunt-contrib-clean [amd64] (zesty-proposed) [1.0.0-1] [12:32] -queuebot:#ubuntu-release- New: accepted postfix [amd64] (zesty-proposed) [3.1.3-3] [12:32] -queuebot:#ubuntu-release- New: accepted postfix [armhf] (zesty-proposed) [3.1.3-3] [12:32] -queuebot:#ubuntu-release- New: accepted postfix [powerpc] (zesty-proposed) [3.1.3-3] [12:32] -queuebot:#ubuntu-release- New: accepted postfix [s390x] (zesty-proposed) [3.1.3-3] [12:32] -queuebot:#ubuntu-release- New: accepted recursive-narrow [amd64] (zesty-proposed) [20140811.1546-1] [12:32] -queuebot:#ubuntu-release- New: accepted slixmpp [amd64] (zesty-proposed) [1.2.1-1] [12:32] -queuebot:#ubuntu-release- New: accepted slixmpp [armhf] (zesty-proposed) [1.2.1-1] [12:32] -queuebot:#ubuntu-release- New: accepted node-regenerator-runtime [amd64] (zesty-proposed) [0.9.5-1] [12:32] -queuebot:#ubuntu-release- New: accepted postfix [i386] (zesty-proposed) [3.1.3-3] [12:32] -queuebot:#ubuntu-release- New: accepted r-cran-rentrez [amd64] (zesty-proposed) [1.0.4-1] [12:32] -queuebot:#ubuntu-release- New: accepted slixmpp [arm64] (zesty-proposed) [1.2.1-1] [12:32] -queuebot:#ubuntu-release- New: accepted postfix [arm64] (zesty-proposed) [3.1.3-3] [12:32] -queuebot:#ubuntu-release- New: accepted should.js [amd64] (zesty-proposed) [8.4.0~dfsg-3] [12:32] -queuebot:#ubuntu-release- New: accepted postfix [ppc64el] (zesty-proposed) [3.1.3-3] [12:32] -queuebot:#ubuntu-release- New: accepted slixmpp [powerpc] (zesty-proposed) [1.2.1-1] [12:32] -queuebot:#ubuntu-release- New: accepted slixmpp [i386] (zesty-proposed) [1.2.1-1] [12:32] -queuebot:#ubuntu-release- New: accepted slixmpp [s390x] (zesty-proposed) [1.2.1-1] [12:32] -queuebot:#ubuntu-release- New: accepted slixmpp [ppc64el] (zesty-proposed) [1.2.1-1] [13:11] if an archive-admin is around, and wants to help me for a few demote/remove I think we are mostly ready for ghc transition [13:14] infinity: so, what to call X backport stack from yak? lts-y to follow the old style, or something else? I know there's going to be just one kernel, but is that handled on the metapackage level so that there's still going to be lts-y/z/å/ä kernels? [13:15] and the rolling bit provided by a metapackage [13:15] please take care of virtualbox too in case ^^ [13:15] as done with trusty [13:16] or at least wait for my upload :p [13:16] nothing has been done so far [13:33] LocutusOfBorg: Debian removed some haskell packages too; I didn't remove those yet as I didn't have an overview of what could go [13:34] LocutusOfBorg: do you have a list? === chrisccoulson_ is now known as chrisccoulson === santa is now known as Guest64868 [13:47] LocutusOfBorg: I removed haskell-applicative-quoters, but three others removed by debian have rdepends: http://paste.ubuntu.com/23480403/ === Guest64868 is now known as santa_ [13:53] pitti, can demoting them work? e.g. haskell-fail (rc buggy in debian) [13:54] LocutusOfBorg: yes, if you find a closed set of sources, we can demote [14:07] pitti, your workflow seems to have an issue [14:08] e.g. haskell-snap-core depends on haskell-blaze-builder-enumerator, but only in zesty [14:08] not in zesty-proposed [14:08] so, I don't think this as example is a blocker [14:09] that's just process-removal's output; but still, we would at least temporarily need to break zesty with these removals [14:09] or remove -snap along (the -proposed version can then promote back to zesty once fixed) [14:09] yes, but they aren't a blocker, right? [14:09] I mean, the situation will auto heal [14:09] no, fine for me, but we need to chase down the complete set [14:09] and then demote it as a whole [14:09] ok, I already have it, just a few sec that I compare it with your :) [14:10] mine is nowhere near complete, it's just Debian removals since Nov 1st [14:10] but that also just covers removals from unstable, not from testing [14:10] pitti: it's probably just temporarily breaking build-deps in zesty, which should be OK as long as there's a thing in zesty-proposed due to migrate [14:11] cjwatson: not sure if we have existing best practices, but it would feel better to completely demote the set into -proposed rather than keeping half of it broken in release? [14:11] aaaaaaaaaaaa [14:12] I think you're tilting at windmills there :) [14:12] and it will probably end up being very complicated [14:13] for Haskell transitions I've always just checked that the build-deps go away in -proposed and then been happy to break devel for that, since builds all happen in -proposed anyway [14:13] ok [14:13] I see http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#haskell-heist as a blocker (FTBFS on two arches) [14:14] haskell-snap* seems okay [14:14] http://paste.ubuntu.com/23480533/ [14:14] $ reverse-depends src:haskell-heist [14:14] Reverse-Recommends [14:14] ================== [14:14] * libghc-snap-doc (for libghc-heist-doc) [14:15] I'm fine with demoting that as well, not much breakage there [14:15] ok, then let's do this -- /me grabs the axe [14:16] pitti, wait [14:16] there still is a blocker: haskell-xmlhtml haskell-heist, haskell-snap [14:16] they are failing due to xmlhtml and gcc bug in arm64 and s390x [14:16] not sure how I can debug it, what is the suggestion here? [14:17] LocutusOfBorg: right, that's what I meant with the above -- these three have no rdepends, so I'm fine with leaving them in -proposed [14:17] oh ok [14:17] so that the ghc8 transition can land without this blocking it [14:17] so I can fix them later, fine [14:17] indeed [14:17] and I can have a better picture [14:17] probably I can debug arm64 with qemu [14:29] LocutusOfBorg: ok, your list is done [14:34] fingers crossed, thanks :) [14:46] -queuebot:#ubuntu-release- New: accepted purpose [amd64] (zesty-proposed) [1.1-2ubuntu1] [14:46] -queuebot:#ubuntu-release- New: accepted purpose [armhf] (zesty-proposed) [1.1-2ubuntu1] [14:46] -queuebot:#ubuntu-release- New: accepted purpose [powerpc] (zesty-proposed) [1.1-2ubuntu1] [14:46] -queuebot:#ubuntu-release- New: accepted purpose [s390x] (zesty-proposed) [1.1-2ubuntu1] [14:46] -queuebot:#ubuntu-release- New: accepted purpose [arm64] (zesty-proposed) [1.1-2ubuntu1] [14:46] -queuebot:#ubuntu-release- New: accepted purpose [ppc64el] (zesty-proposed) [1.1-2ubuntu1] [14:46] -queuebot:#ubuntu-release- New: accepted purpose [i386] (zesty-proposed) [1.1-2ubuntu1] [14:51] pitti, did you forget to demote agda-stdlib? [14:52] or is it useless? (wrt agda ppc64el) [14:52] LocutusOfBorg: ah, that wasn't on your list [14:52] LocutusOfBorg: there's no rebuild of that in -proposed either [14:53] I don't know, based on the transition tracker, it is uninstallable on ppc64el, due to agda [14:53] is it a blocker? [14:53] it is an arch:all package [14:54] LocutusOfBorg: possibly, yes [14:54] so demoting can be done? [14:54] * LocutusOfBorg wonders about the word "demoting" :/ [14:56] LocutusOfBorg: moved to -proposed ("demoted") and blocked in britney [14:56] thanks, and sorry for not mentioning it, I was not sure about that situation [14:56] * LocutusOfBorg waits for next britney run [14:56] no problem [14:56] we all play this by ear :) [14:57] haskell can be challenging [14:57] -queuebot:#ubuntu-release- Unapproved: gcin (xenial-proposed/universe) [2.8.4+dfsg1-1ubuntu1 => 2.8.4+dfsg1-1ubuntu1.1] (input-methods) [14:58] -queuebot:#ubuntu-release- Unapproved: gcin (yakkety-proposed/universe) [2.8.4+dfsg1-9build1~1 => 2.8.4+dfsg1-9build1~1ubuntu1] (input-methods) [14:59] -queuebot:#ubuntu-release- Unapproved: qemu (trusty-proposed/main) [2.0.0+dfsg-2ubuntu1.30 => 2.0.0+dfsg-2ubuntu1.31] (ubuntu-server, virt) [15:01] is there anyone around who can look at my linux-firmware SRU for xenial? [15:03] Q: When a package is SRUed to many releases and awaiting verification, shouldn't there be a "verification-needed-{release}' present in the bug ? [15:03] caribou: no, we only do that for -done; as long as it's still unverified in any release, we keep v-needed [15:04] that was the follow up question: if it has been verified for only one release, we should only add 'verification-done-{release}' then [15:04] pitti: ^^ [15:05] correct [15:05] pitti: thanks! [15:26] pitti, the mail flooding has started, cheers! [15:26] excellent! /me unblocks adga-stdlib then [15:27] thanks! [15:27] BTW, if anybody wants to see xapian-core migrate... [15:28] just grab src:notmuch from here https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+delete-packages [15:28] with the new emacs25 in main, I added it as dependency [15:29] maybe ginggs ^^ :) https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/7131474/+listing-archive-extra [15:31] LocutusOfBorg: ok [15:31] thanks! [15:38] LocutusOfBorg: notmuch still has a dependency on emacs25 ... [15:40] doko: do you mean emacs24? [15:41] ginggs: of course, don't trust what I write, always trust what I mean ;) [15:43] doko: ah you mean in the depends of notmuch-emacs? [15:44] doko: because LocutusOfBorg did add emacs25-nox | emacs25 | to the build-deps [15:46] yes [15:48] -queuebot:#ubuntu-release- Unapproved: muse (xenial-proposed/universe) [2.1.2-1build1 => 2.1.2-1ubuntu0.16.04.1] (no packageset) [15:48] -queuebot:#ubuntu-release- Unapproved: muse (yakkety-proposed/universe) [2.1.2-2 => 2.1.2-2ubuntu0.16.10.1] (no packageset) [15:48] doko, LocutusOfBorg: ok, i'll fix [16:08] interesting, the ghc transition page looks scary http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=daisy [16:08] oops [16:09] http://people.canonical.com/~ubuntu-archive/transitions/ghc.html [16:09] maybe I should wait some more time? [16:11] That occasionally happens mid-transition-to-release; just wait for the next run [16:11] It's a big batch of packages and the copy isn't atomic [16:11] So it can easily get split into multiple publisher runs [16:20] oh, I didn't knew that [16:33] -queuebot:#ubuntu-release- Unapproved: bind9 (xenial-proposed/main) [1:9.10.3.dfsg.P4-8ubuntu1.2 => 1:9.10.3.dfsg.P4-8ubuntu1.3] (core) [16:41] somebody please hint libaws to make gnutls28 migrate? [16:42] also asis should migrate with that ^^ [16:45] No, they are in the process of being rebuilt [16:48] ok [16:50] LocutusOfBorg: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#agda-stdlib → I think that does need a rebuild, and you rebuilt it in yakkety too [16:51] LocutusOfBorg: I already hinted gnutls28 earlier, it's in [16:51] gnat breakage happened a while ago already, it was unrelated [16:51] nevertheless, I am fixing it [16:53] pitti, with emacs and dh-elpa almost fixed, I'll rebuild agda and then agda-stdlib [16:54] or just rebuild it now [16:54] * pitti hugs LocutusOfBorg, nice work! [16:54] :) [16:56] btw that haskell-xmlfoo broken in arm64 and s390x eat something like 30GB of ram in my laptop [16:56] I killed it [16:56] seems a similar issue to the haskell-lambdabot-haskell-plugins all your ram belongs to me [17:01] oh last thing: cjwatson this might be a nice timing to unblock haskell auto-import :) [17:02] LocutusOfBorg: done [17:02] ta [17:05] -queuebot:#ubuntu-release- Unapproved: criu (xenial-proposed/universe) [2.6-1ubuntu1~ubuntu16.04.1 => 2.6-1ubuntu1~ubuntu16.04.2] (no packageset) [17:09] ^ will fix the current build failure of criu in xenial-proposed (said it needed dh10, but really doesn't...) [17:12] feature request: in a ppa, map unstable with distro-info --devel [17:12] is it possible? [17:13] I don't think we want to do that, but you can use "devel" in the changelog when uploading to a PPA. [17:13] wow, hidden feature :) thanks! [17:15] tjaalton: No, there won't be multiple kernels with rolling metas, just one hwe stack, period. [17:15] tjaalton: One of the big driving forces here was not having junk in main that we later tell people "just kidding, not supporting that". [17:16] tjaalton: So, linux-hwe will just roll forward, and I'd expect xorg-hwe to do the same. [17:19] -queuebot:#ubuntu-release- New binary: golang-golang-x-oauth2 [amd64] (zesty-proposed/universe) [0.0~git20161103.0.36bc617-3] (no packageset) [17:20] -queuebot:#ubuntu-release- New binary: django-simple-redis-admin [amd64] (zesty-proposed/universe) [1.4.0-1] (no packageset) [17:20] -queuebot:#ubuntu-release- New binary: peco [ppc64el] (zesty-proposed/universe) [0.0~git20161005.0.d4f7705-1] (no packageset) [17:21] -queuebot:#ubuntu-release- New binary: libelfin [ppc64el] (zesty-proposed/universe) [0.2-4] (no packageset) [17:21] -queuebot:#ubuntu-release- New binary: peco [i386] (zesty-proposed/universe) [0.0~git20161005.0.d4f7705-1] (no packageset) [17:21] -queuebot:#ubuntu-release- New binary: peco [arm64] (zesty-proposed/universe) [0.0~git20161005.0.d4f7705-1] (no packageset) [17:23] -queuebot:#ubuntu-release- New binary: libelfin [amd64] (zesty-proposed/universe) [0.2-4] (no packageset) [17:23] -queuebot:#ubuntu-release- New binary: peco [amd64] (zesty-proposed/universe) [0.0~git20161005.0.d4f7705-1] (no packageset) [17:23] -queuebot:#ubuntu-release- New binary: peco [s390x] (zesty-proposed/universe) [0.0~git20161005.0.d4f7705-1] (no packageset) [17:23] -queuebot:#ubuntu-release- New binary: libelfin [arm64] (zesty-proposed/universe) [0.2-4] (no packageset) [17:23] -queuebot:#ubuntu-release- New binary: unirest-java [amd64] (zesty-proposed/universe) [1.4.8-1] (no packageset) [17:23] -queuebot:#ubuntu-release- New binary: peco [armhf] (zesty-proposed/universe) [0.0~git20161005.0.d4f7705-1] (no packageset) [17:26] -queuebot:#ubuntu-release- New binary: peco [powerpc] (zesty-proposed/universe) [0.0~git20161005.0.d4f7705-1] (no packageset) [17:29] and mono transitioned ... [17:32] -queuebot:#ubuntu-release- New binary: gnuplot [amd64] (zesty-proposed/universe) [5.0.5+dfsg1-4] (no packageset) [17:33] doko, can you please help xapian-core migrate? [17:34] LocutusOfBorg: not today. afk now [17:34] Laney, ^^ you did a lot of rebuilds for xapian [17:34] but something is missing [17:35] rying easy from autohinter: akonadi-search/4:16.04.3-0ubuntu2 aptitude/0.8.3-1ubuntu4 baloo/4:4.14.3-0ubuntu6 khelpcenter/4:16.04.3-0ubuntu2 libqapt/3.0.2-0ubuntu4 libsearch-xapian-perl/1.2.24.0-1 maildir-utils/0.9.16-1build1 pinot/1.05-1.2 recoll/1.22.3-1build1 ubuntu-kylin-software-center/1.3.11 unity-lens-applications/7.1.0+16.10.20160927-0ubuntu2 xapian-bindings/1.4.0-7 xapian-core/1.4.1-1 xapian-omega/1.4.1-1 zeitgeist/0.9.16-0ubuntu6 [17:35] start: 8925+0: a-1739:a-1191:a-1194:i-1200:p-1196:p-1196:s-1209 [17:35] orig: 8925+0: a-1739:a-1191:a-1194:i-1200:p-1196:p-1196:s-1209 [17:35] easy: 9007+0: a-1758:a-1201:a-1205:i-1211:p-1207:p-1206:s-1219 [17:35] * amd64: alot, aptoncd, goplay, libnotmuch-dev, libnotmuch4, lubuntu-desktop, mutt, muttprofile, notmuch, notmuch-addrlookup, notmuch-dbg, notmuch-emacs, notmuch-mutt, notmuch-vim, packagesearch, python-notmuch, python3-notmuch, ruby-notmuch, synaptic [17:35] * arm64: goplay, libnotmuch-dev, libnotmuch4, mutt, notmuch, notmuch-addrlookup, notmuch-dbg, packagesearch, ruby-notmuch, synaptic [17:35] * armhf: goplay, libnotmuch-dev, libnotmuch4, lubuntu-desktop, mutt, notmuch, notmuch-addrlookup, notmuch-dbg, packagesearch, ruby-notmuch, synaptic [17:35] * i386: goplay, libnotmuch-dev, libnotmuch4, lubuntu-desktop, mutt, notmuch, notmuch-addrlookup, notmuch-dbg, packagesearch, ruby-notmuch, synaptic [17:35] * powerpc: goplay, libnotmuch-dev, libnotmuch4, lubuntu-desktop, mutt, notmuch, notmuch-addrlookup, notmuch-dbg, packagesearch, ruby-notmuch, synaptic [17:36] * ppc64el: goplay, libnotmuch-dev, libnotmuch4, mutt, notmuch, notmuch-addrlookup, notmuch-dbg, packagesearch, ruby-notmuch, synaptic [17:36] * s390x: goplay, libnotmuch-dev, libnotmuch4, mutt, notmuch, notmuch-addrlookup, notmuch-dbg, packagesearch, ruby-notmuch, synaptic [17:36] FAILED [17:36] nope [17:37] * amd64: aptoncd, goplay, lubuntu-desktop, packagesearch, synaptic [17:37] * arm64: goplay, packagesearch, synaptic [17:37] * armhf: goplay, lubuntu-desktop, packagesearch, synaptic [17:37] * i386: goplay, lubuntu-desktop, packagesearch, synaptic [17:37] * powerpc: goplay, lubuntu-desktop, packagesearch, synaptic [17:37] * ppc64el: goplay, packagesearch, synaptic [17:37] * s390x: goplay, packagesearch, synaptic [17:37] the new run removed notmuch [17:38] what do you need help with? [17:39] I'm doing goplay [17:41] Laney, probably everything is in universe [17:42] not sure why lubuntu-desktop and aptoncd are there [17:42] They probably depend on other things that are in the list [17:43] ok I did goplay aptoncd packagesearch, synaptic [17:43] lets see [18:05] infinity: alright, thanks! I'll get on with it then :) [18:34] could someone please approve the grub2 2.02~beta3-3ubuntu1 binaries for amd64 and arm64? [18:36] checking [18:39] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (zesty-proposed) [2.02~beta3-3ubuntu1] [18:39] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (zesty-proposed) [2.02~beta3-3ubuntu1] [19:10] cyphermox, can you accept linux 4.9.0-1.2 in the Zesty unapproved queue ? [19:11] rtg: sorry, EPERM. [19:11] slangasek: ^? [19:15] cyphermox, rtg: accepted [19:15] slangasek, thanks [19:15] ta [20:31] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [0.7.8-1-g3705bb5-0ubuntu1~16.04.3 => 0.7.8-45-g584b843-0ubuntu1~16.04.1] (edubuntu, ubuntu-cloud, ubuntu-server) [20:41] slangasek, ^ [20:41] please let me know what i need to do to make that acceptable [20:49] smoser: reviewing [21:35] -queuebot:#ubuntu-release- New: accepted django-simple-redis-admin [amd64] (zesty-proposed) [1.4.0-1] [21:35] -queuebot:#ubuntu-release- New: accepted golang-golang-x-oauth2 [amd64] (zesty-proposed) [0.0~git20161103.0.36bc617-3] [21:35] -queuebot:#ubuntu-release- New: accepted gnuplot [amd64] (zesty-proposed) [5.0.5+dfsg1-4] [21:35] -queuebot:#ubuntu-release- New: accepted unirest-java [amd64] (zesty-proposed) [1.4.8-1] [21:36] -queuebot:#ubuntu-release- New: accepted peco [amd64] (zesty-proposed) [0.0~git20161005.0.d4f7705-1] [21:36] -queuebot:#ubuntu-release- New: accepted peco [armhf] (zesty-proposed) [0.0~git20161005.0.d4f7705-1] [21:36] -queuebot:#ubuntu-release- New: accepted peco [powerpc] (zesty-proposed) [0.0~git20161005.0.d4f7705-1] [21:36] -queuebot:#ubuntu-release- New: accepted peco [s390x] (zesty-proposed) [0.0~git20161005.0.d4f7705-1] [21:36] -queuebot:#ubuntu-release- New: accepted peco [arm64] (zesty-proposed) [0.0~git20161005.0.d4f7705-1] [21:36] -queuebot:#ubuntu-release- New: accepted peco [ppc64el] (zesty-proposed) [0.0~git20161005.0.d4f7705-1] [21:36] -queuebot:#ubuntu-release- New: accepted peco [i386] (zesty-proposed) [0.0~git20161005.0.d4f7705-1] [22:32] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [0.7.8-1-g3705bb5-0ubuntu1~16.04.3 => 0.7.8-47-gb6561a1-0ubuntu1~16.04.1] (edubuntu, ubuntu-cloud, ubuntu-server) [23:21] -queuebot:#ubuntu-release- New binary: libelfin [amd64] (zesty-proposed/universe) [0.2-5] (no packageset) [23:21] -queuebot:#ubuntu-release- New binary: libelfin [ppc64el] (zesty-proposed/universe) [0.2-5] (no packageset) [23:21] slangasek: can you 'remove-package -y -m "moved to -updates" -s xenial-proposed -e 1.2.15 apt' so I can review the next one? [23:23] -queuebot:#ubuntu-release- New binary: libelfin [arm64] (zesty-proposed/universe) [0.2-5] (no packageset) [23:23] -queuebot:#ubuntu-release- New binary: libelfin [i386] (zesty-proposed/universe) [0.2-5] (no packageset) [23:25] bdmurray: done [23:26] cjwatson: sorry you weren't able to attend the UOS session -- a great discussion and fyi, I think we have a way forward to become dgit compatible and for dgit to eventually be aware of our imports (which have a more complete history than what dgit asserts currently) [23:26] cjwatson: mostly just an fyi for you for now :) [23:27] nacc: useful, thanks! the other thing I was thinking of while cycling through town tonight was that maybe we should acknowledge that there may not be a single source of truth for imports for a while, and that it might be worth having a way for a package-namespace repository to say "allow anyone who can upload this package to push to this repository" separate from making it the ... [23:27] ... /ubuntu/+source/foo default [23:28] cjwatson: thanks [23:28] cjwatson: yeah, that's something i was thinking about as well, as right now, the usd-import-team becomes a bottleneck to write to the repositor(ies) [23:28] nacc: originally I was thinking that we'd do that by letting usd-import-team set the default, but that only works if we can really say it's definitely the preferred thing for everyone to use [23:28] cjwatson: right [23:28] and I feel like that could both be some way off, and maybe a distraction [23:29] anyway, I should sleep, but glad to hear it was useful [23:29] and having that flexibility would be great anyways, I think [23:29] cjwatson: have a good night! [23:29] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (xenial-proposed) [0.7.8-45-g584b843-0ubuntu1~16.04.1] [23:29] bdmurray: technically shouldn't be required before reviewing the new one though, should it? [23:30] slangasek: reviewing or accepting? [23:31] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [0.7.8-47-gb6561a1-0ubuntu1~16.04.1] [23:32] bdmurray: either? if it's just replacing the existing one that's already copied to -updates, should be fine I think? [23:33] Hmm, I thought I'd heard it wasn't. [23:51] slangasek, pitti: thanks for the help on cloud-init [23:58] jgrimm: no problem!