[06:36] jbicha: could you ping Debian #862425? [06:36] Debian bug 862425 in pcre2 "pcre2: Please switch to 3.0 (quilt) or use dgit-maint-merge(7)" [Wishlist,Open] http://bugs.debian.org/862425 [07:21] kirkland: byobu: Depends: debconf (>= 0.5) | debconf-2.0, gettext-base, net-tools, python3 | python, python3-newt | python-newt [07:21] don't do that, breaking the dependency system === Elimin8r is now known as Elimin8er [10:19] cjwatson: what's the future of system-config-kickstart? it's seeded in supported-sysadmin-desktop, uses Python2 [10:19] and no bug subscriber [10:29] doko: I've subscribed to its bugs. I'll have a look at some point - it probably has a new upstream [11:44] cpaelzer, coreycb, jamespage: I have assigned a lot of the bugs filed with the py2-demotion tag to ubuntu-server, whereever I found the server team as a bug subscriber. excluded are the openstack packages [12:04] doko: OOI, has Ubuntu committed to maintaining a delta for all of these? Or is the expectation to just send patches to Debian and wait? Do we have a specific target? [12:05] A specific target release I mean. [12:46] can I reverse search on package removal from archive in Debian? [12:46] like (why) was package X removed? [12:47] cpaelzer, you can go on the bts page of the package [12:48] cpaelzer, e.g https://packages.qa.debian.org/g/gdm.html the top entry is the removal which includes the details if you click on it [12:50] thanks seb128 [14:07] doko: ping sent [14:08] rbasak: sorry, where does the requirement to get a commitment come from? sure, we can demote these as well [14:08] jbicha: ta [14:08] pcre2 gave me a really bad first impression of dgit 😢 [14:09] good, then I'm not alone ;p [14:10] doko: have you seen https://browse.dgit.debian.org/pcre2.git/ ? [14:10] doko: I wasn't aware that removal of Python 2 from main was intended for this cycle, and to my knowledge the server team hasn't planned time for this. [14:11] too bad the pcre2 packaging doesn't use Vcs fields in debian/control and too bad it doesn't preserve all that commit metadata in debian/patches/ [14:11] doko: was it communicated somewhere that I'm missing? This is the first I've heard of this (specific work to introduce a delta that is, rather than the general desire to remove Python 2 which of course I know about) [14:13] rbasak: I would like to, but this depends on openstack migrating to Python3. Yes, I think we communicated that before the last two or three LTSes. Feel free to search the mailing lists, and maybe even some blueprints [14:14] but maybe you missed it [14:22] doko: if you can't point to a definitive communication (eg. with an URL) where you made it clear that you wanted this for Bionic and that you'd expect the server team to move the server-maintained packages with a delta, then I don't think it's reasonable for you to spring this on us now. But I'll check with my manager. [14:23] rbasak: well, I hope you have planned some time to work on the server seeds then, doesn't look like these have been worked on for ages [14:23] doko: please can you be specific about what needs doing with the server seeds? [14:23] rbasak: explicit seeding of python2 modules [14:24] For the python2 removal? See above. [14:39] rbasak, doko: I think the server seeds need some general housekeeping; there are multiple ways to get things seeded, and I think its over-populated atm with things that should just be depends [14:56] Hi all. I'd like to know whether https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1595695 is going to be addressed or whether you actually *want* to leave the indicator's behaviour as is? [14:56] Launchpad bug 1595695 in indicator-bluetooth (Ubuntu) "Bluetooth indicator disappears every time bluetooth is being turned off" [Undecided,Confirmed] [18:23] icey: my email looks fine here: https://lists.ubuntu.com/archives/ubuntu-devel/2017-November/040054.html === mitya57_ is now known as mitya57 [20:16] cpaelzer: are you looking for a particular package? you can look at e.g. https://launchpad.net/debian/+source/moodle/+publishinghistory [20:17] that question was many hours old, wasn't it [20:26] bdmurray: can i get a new version of neutron into artful-proposed at this point or do i need to wait for the current proposed version to complete verification? there's a high-impact bug fix that just became ready to cherry-pick. [20:26] yes, yes it was :) but still, interesting.. [20:38] coreycb: its up to you, upload another if you want [20:38] bdmurray: ok i'll upload another with the both bug's referenced in the latest changelog and bump the version [21:26] does anybody know if this dep8 test failure is an infrastructure random issue? It looks like a timeout in the cloud that is used for the tests: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/q/quagga/20171130_164223_ee46e@/log.gz [21:26] scroll to the very end [21:35] here is another failure type: " [16:09:45]: ERROR: erroneous package: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U." [21:36] anything I, the uploader, can do? Or is this an infrastructure problem, i.e., the image is out of date and/or inconsistent [22:17] ahasenack: yes, that looks like an infra issue [22:18] ahasenack: so it should be manually retried [22:18] slangasek: can you hit the button for me? I don't have perms (my upload was sponsored) [22:18] it's iproute2 in http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html [22:19] ahasenack: done [22:19] thanks a lot [22:19] hey i accidentially dput git when i meant it to go to a ppa so smack that down from me if you ssee it [22:20] wxl: dput without a target? I use this trick: http://pastebin.ubuntu.com/26084332/ :) [22:20] good idea ahasenack [22:20] shame, shame, shame [23:36] bdmurray: i've uploaded a new version of neutron to the artful queue. that can replace version 2:11.0.2-0ubuntu1 that is currently in proposed. [23:37] coreycb: ack [23:39] coreycb: what is its status in bionic? [23:41] bdmurray: eh. looks like the builder is moving slow. it's waiting to build in proposed.