| === micahg_ is now known as micahg | ||
| -queuebot:#ubuntu-release- Unapproved: libvirt (trusty-proposed/main) [1.2.2-0ubuntu13.1.21 => 1.2.2-0ubuntu13.1.22] (kubuntu, ubuntu-desktop, ubuntu-server, virt) | 07:48 | |
| cpaelzer | hi, currently qemu 2.10 migration in artful is blocked by bug 1715128 | 08:51 |
|---|---|---|
| ubot5` | bug 1715128 in cloud-init (Ubuntu) "Crashes in convert_ec2_metadata_network_config on ScalingStack bos01 (ppc64el)" [Critical,Confirmed] https://launchpad.net/bugs/1715128 | 08:51 |
| cpaelzer | I wanted to ask if one could force the migration (all else is good) since no one knows how long resolution will take | 08:52 |
| apw | cpaelzer, is it safe to let it migrate if it is going to make scalingstack sad, given that is where we build things ? | 09:04 |
| wgrant | apw: It's cloud-init that's broken | 09:04 |
| wgrant | qemu is only affected because the cloud-init in the images doesn't work any more | 09:05 |
| cpaelzer | as wgrant says | 09:05 |
| apw | oh i see, not reading very well ... perhaps i should not be typing :) | 09:05 |
| cpaelzer | I'd expect any ppc64el test needin network through proxies to fail over the next days | 09:06 |
| cpaelzer | until that is resolved | 09:06 |
| apw | that does not seem unreasonable ... hinted | 09:11 |
| apw | cpaelzer, if this is going to take days to fix, can we not revert the whole of the cloud-init update somehow | 09:11 |
| apw | cpaelzer, given it is cratering testing | 09:11 |
| cpaelzer | apw: absolutely | 09:11 |
| cpaelzer | apw: I planned to jump into the cloud-init standup today to dsicuss options | 09:12 |
| cpaelzer | apw: a CURVER+reallyOLDVER might be a temporary fix in this case | 09:12 |
| cpaelzer | but since this is around data source identification in scaling stack we have to understand what really is going on) | 09:12 |
| wgrant | Well we know now | 09:13 |
| cpaelzer | my current theory is that scaling stack tries to mimic ec2, but doesn't do perfectly (a common case btw) | 09:13 |
| wgrant | https://bugs.launchpad.net/cloud-init/+bug/1715241 | 09:13 |
| ubot5` | Ubuntu bug 1715241 in cloud-init "ds-identify openstack returns not found on non-intel" [Medium,Confirmed] | 09:13 |
| wgrant | ds-identify simply doesn't work outside x86. | 09:13 |
| wgrant | Since it relies on DMI | 09:13 |
| cpaelzer | IM-veryH-o I'm not 100% convinced that is the issue affecting the current case | 09:14 |
| apw | they use dmi ... openstack "for the win" | 09:14 |
| cpaelzer | hmm, yeah you might be right ont hat bug actually | 09:14 |
| cpaelzer | yet I wonder why this should now be different than before | 09:15 |
| cpaelzer | anyway smoser and rharper will ahve all the current context later today | 09:15 |
| wgrant | Becaise cloud-init used to poll all datasources | 09:16 |
| cpaelzer | Maybe it comes together with fail-detect EC2 + new ipv6 code that can fault if no EC2 data is actually provided | 09:16 |
| wgrant | there was work this cycle to speed up cloud-init by using ds-identify to skip irrelevant sourcea | 09:16 |
| cpaelzer | The polling -> detect change happened a while ago, that is why I wonder the recent update breaking it in this case | 09:17 |
| cpaelzer | I'm rather up to date on the ds-identify move | 09:17 |
| cpaelzer | just thought that would have been in artful for a while now, which is why I expect it to be partially bad for a while but e.g. the ipv6 code added now making this a hard fail | 09:17 |
| wgrant | it is either that it has just swktched to EC2, or EC2 used to work but doesn't any more | 09:18 |
| wgrant | but it *should* be using OpenStack on that cloud, so fixing ds-identify would probably work | 09:19 |
| cpaelzer | ack | 09:19 |
| cpaelzer | I think copying that discussion context to the current bug is worth to | 09:19 |
| * cpaelzer is copying | 09:19 | |
| * Laney is looking into why /running is timing out | 09:25 | |
| Laney | don't all go hit it to confirm that that's the case please :/ | 09:25 |
| apw | Laney, :) | 09:25 |
| Laney | https://paste.ubuntu.com/25483043/ | 09:30 |
| Laney | some extremely duplicated requests | 09:30 |
| apw | queue gone mad ... hrm | 09:30 |
| Laney | https://paste.ubuntu.com/25483059/ | 09:34 |
| Laney | BRITNEYYYYYYYYYYYY | 09:34 |
| cpaelzer | oops she did it again (lamest pun ever I guess) | 09:35 |
| -queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.27.5~14.04 => 2.27.6~14.04] (no packageset) | 09:35 | |
| -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.27.5 => 2.27.6] (desktop-core, ubuntu-server) | 09:35 | |
| -queuebot:#ubuntu-release- Unapproved: snapd (zesty-proposed/main) [2.27.5+17.04 => 2.27.6+17.04] (desktop-core, ubuntu-server) | 09:36 | |
| apw | Laney, crashing out before she writes her state back perhaps ? | 09:37 |
| apw | Laney, is there ever a case where a duplicated run is valid in the pending queue (with the same actual parameters) | 09:37 |
| * apw will review those snapds ^ | 09:38 | |
| Laney | it was crashing | 09:39 |
| * Laney dies | 09:42 | |
| Laney | guess I get to write a script to filter these out, and then fix britney | 09:42 |
| apw | Laney, sounds like a fun day for you ... i wonder if we should be writing what we have submitted to disk at the time we submit it ... and then it is always recorded | 09:43 |
| Laney | yeh | 09:45 |
| Laney | going to make runs a bit slower but that's probably less bad than this | 09:45 |
| -queuebot:#ubuntu-release- Unapproved: ntp (xenial-proposed/main) [1:4.2.8p4+dfsg-3ubuntu5.6 => 1:4.2.8p4+dfsg-3ubuntu5.7] (ubuntu-server) | 09:51 | |
| Laney | https://paste.ubuntu.com/25483111/ | 09:52 |
| Laney | https://www.youtube.com/watch?v=ZKFDK-Z1QUE | 09:55 |
| Laney | back in business | 10:00 |
| -queuebot:#ubuntu-release- Unapproved: xorg-server (xenial-proposed/main) [2:1.18.4-0ubuntu0.4 => 2:1.18.4-0ubuntu0.5] (desktop-core, xorg) | 10:09 | |
| apw | Laney, i don't see "moving triggered by apw to the top of the list" in there anywhere :) | 10:15 |
| Laney | heh oh god | 10:16 |
| Laney | reordering would be a lot more weird | 10:16 |
| Laney | you'd have to ack everything out and then put it back in a different order | 10:16 |
| Laney | /o\ | 10:16 |
| -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (zesty-proposed) [2.27.6+17.04] | 10:16 | |
| Laney | poor apw is going to have to queue up with the plebs :) | 10:17 |
| apw | i assume you are picking all the requests and acking the bad ones and then exiting to do this ? | 10:17 |
| Laney | yeh | 10:18 |
| Laney | like filter-amqp | 10:18 |
| -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.27.6] | 10:23 | |
| acheronuk | bug #1703368 breaks build and tests of some k* packages, as libxslt requires headers which were removed | 10:25 |
| ubot5` | bug 1703368 in glibc (Ubuntu) "[FFe] [17.10 FEAT] upgrade to newest version of glibc >=2.26" [Undecided,Triaged] https://launchpad.net/bugs/1703368 | 10:25 |
| acheronuk | bug #1715599 | 10:25 |
| ubot5` | bug 1715599 in glibc (Ubuntu) "2.26-0ubuntu1 breaks compliation of several KDE sources" [Undecided,New] https://launchpad.net/bugs/1715599 | 10:25 |
| acheronuk | libxslt is not an optional build dep, so no easily working around that | 10:26 |
| -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.27.6~14.04] | 10:26 | |
| xnox | acheronuk, that header is dropped and no longer required, one should include locale.h alone. | 10:27 |
| xnox | acheronuk, hence this is a bug in libxslt, let me look into that. | 10:27 |
| acheronuk | xnox: I was coming to that conclusion after filing the bug | 10:27 |
| xnox | acheronuk, e.g. in src:perl it does "proper" configure time checks and generates defines to conditionally include locale.h, xlocale.h, or both. | 10:28 |
| xnox | acheronuk, in this case I will just drop the xlocale.h include. | 10:28 |
| xnox | and upload. | 10:28 |
| acheronuk | xnox: thanks :) | 10:29 |
| xnox | apw, awwww... /o\ what cloud-init regression? | 11:38 |
| xnox | is there a bug number? do you add bug number when pushing hints? | 11:38 |
| xnox | cpaelzer, we are currently undergoing investigations in scaling stack failing to talk to the metadata sources. and cloud-init was mistakenly identifying and (using/abusing) ec2 data-source on scalingstack on non-intel architectures since introduction of ds-identify it seems, and we are inflight fixing that. | 11:39 |
| xnox | and separately, I'm currently seeing regression of not being able to talk to the openstack native datasource, on intel, in scalingstack =/ | 11:40 |
| wgrant | xnox: Hm, really? Do you have an example instance? | 11:42 |
| wgrant | Which network is it on? | 11:42 |
| wgrant | And which cloud? | 11:42 |
| xnox | wgrant, yes i have all that. One sec. | 11:42 |
| xnox | &> some other channel | 11:43 |
| === alan_g is now known as alan_g|lunch | ||
| apw | xnox I should and did not | 12:08 |
| * Laney wonders what this secret discussion revealed | 12:29 | |
| cpaelzer | Laney: you checked which other channel they meant as well :-) | 12:31 |
| Laney | I just know it's no channel that I'm in :( | 12:32 |
| slashd | Good day sil2100 ;), Do you have some cycle to approve the upload of "python-neutronclient" for Xenial and Zesty ? (LP: #1692334) | 13:04 |
| ubot5` | Launchpad bug 1692334 in python-neutronclient (Ubuntu Zesty) "neutron bash completion helper is not installed" [Medium,In progress] https://launchpad.net/bugs/1692334 | 13:04 |
| === alan_g|lunch is now known as alan_g | ||
| tjaalton | pymol tests on ppc64el are breaking since a glibc update a week ago, and is blocking mesa.. | 13:17 |
| doko | tjaalton: are you sure it's glibc? I think I've seen these earlier, not just triggered by mesa | 13:46 |
| tjaalton | doko: just trying to parse http://autopkgtest.ubuntu.com/packages/p/pymol/artful/ppc64el | 13:47 |
| acheronuk | can a member of SRU team please release the missing packages for bug #1687444 ? | 13:49 |
| ubot5` | bug 1687444 in polkit-kde-agent-1 (Ubuntu Zesty) "Zesty SRU tracking bug for KDE's Plasma 5.9.5" [Undecided,Fix committed] https://launchpad.net/bugs/1687444 | 13:49 |
| acheronuk | ksshaskpass & polkit-kde-agent-1 | 13:50 |
| sil2100 | slashd: hey! On it in some minutes ;) | 13:52 |
| slashd | sil2100, thanks | 13:52 |
| acheronuk | oh, those are some 0-diff packages. so doesn't really matter. they can stay at 5.9.4 if releasing is deemed more a regression risk than not | 13:53 |
| sil2100 | acheronuk: I asked Brian about why he kept some of them unreleased | 14:07 |
| sil2100 | acheronuk: I could understand the polkit one since it had some autopkgtest regressions that first need someone to confirm if unrelated | 14:07 |
| sil2100 | But besides that, no idea why he didn't release those | 14:07 |
| acheronuk | sil2100: well, as I said, the only upstream changes were internal version bumps, so even a nominal and likely unrelated regression would be a good reason to not release | 14:09 |
| sil2100 | acheronuk: yeah, it still requires someone to look and confirm ;) I guess I can pick it up | 14:10 |
| acheronuk | I thought those were some with some fixes, but I was mistaken. | 14:11 |
| acheronuk | The final paragraph of the SRU says to leave those unreleased if there is even a small risk | 14:12 |
| acheronuk | all the crucial packages seem to have gone through | 14:13 |
| acheronuk | I should have remembered all that, as I wrote the bug! | 14:15 |
| xnox | tjaalton, triggering pymol test with pymol as the only trigger, to test it alone in artful-release pocket, without anything from proposed. | 14:43 |
| -queuebot:#ubuntu-release- Unapproved: accepted python-neutronclient [source] (zesty-proposed) [1:6.1.0-0ubuntu3] | 14:44 | |
| -queuebot:#ubuntu-release- Unapproved: accepted python-neutronclient [source] (xenial-proposed) [1:4.1.1-2ubuntu1] | 14:45 | |
| slashd | freyes, ^^^ | 14:55 |
| slashd | thanks sil2100 | 14:56 |
| -queuebot:#ubuntu-release- Unapproved: accepted virt-manager [source] (zesty-proposed) [1:1.3.2-3ubuntu4.1] | 15:30 | |
| -queuebot:#ubuntu-release- Unapproved: accepted virt-manager [source] (xenial-proposed) [1:1.3.2-3ubuntu1.16.04.4] | 15:31 | |
| sil2100 | bdmurray: ^ there are 3 KDE packages left in -proposed that weren't pushed to -updates, any reason for that? IIRC you were the one publishing that batch | 15:33 |
| freyes | slashd, thanks for the heads up | 15:33 |
| sil2100 | For zesty | 15:33 |
| bdmurray | sil2100: No, copying all the package names was hard. | 15:33 |
| sil2100 | heh, yeah, crazy amount | 15:34 |
| sil2100 | bdmurray: ok, so I'll just check them quick and publish - or maybe you want to do that? | 15:34 |
| bdmurray | sil2100: I can do it | 15:35 |
| doko | what is the current way to re-run tests against all-proposed? | 16:12 |
| nacc | doko: i have had to right-click the url, c&p, and append "&all-proposed=1" | 16:13 |
| doko | ahh, maybe we should generate that button by default ... | 16:14 |
| Laney | no | 16:15 |
| nacc | doko: i thin it would get abused :/ | 16:15 |
| nacc | Laney: would it be difficult for the retry button to not just be a POST but instead be a web form where you can append more arguments? (in the case where, say, two packages need to be tested together). I find the biggest hassle is just c&p the same URL 5 times for each arch | 16:16 |
| nacc | Laney: not asking you to do it, just curious | 16:16 |
| Laney | Probably in most cases that is an insufficiently tight dependency | 16:17 |
| Laney | but I'd probably implement that in retry-autopkgtest-regressions | 16:17 |
| nacc | Laney: you might be right on the reason | 16:18 |
| Laney | like [1] let you select the failing package instead of always dumping everything, [2] allow you to supply an extra trigger | 16:18 |
| nacc | Laney: yeah, that would satisfy my need | 16:19 |
| Laney | :3 | 16:21 |
| Laney | nacc: don't think you can file bugs on lp:ubuntu-archive-tools sadly | 16:22 |
| nacc | ooh https://bugs.launchpad.net/ubuntu-archive-tools | 16:24 |
| nacc | Laney: there? | 16:24 |
| Laney | well blow me down | 16:25 |
| Laney | now it'll turn out I've filed one there before | 16:26 |
| -queuebot:#ubuntu-release- Unapproved: python3.5 (xenial-proposed/main) [3.5.2-2ubuntu0~16.04.1 => 3.5.2-2ubuntu0~16.04.2] (core) | 16:27 | |
| -queuebot:#ubuntu-release- Unapproved: python3.5 (zesty-proposed/main) [3.5.3-1 => 3.5.3-1ubuntu0~17.04.0] (core) | 16:27 | |
| nacc | Laney: heh | 16:28 |
| nacc | Laney: I did a quick saerch and didn't see it, but filed LP: #1715698 | 16:30 |
| ubot5` | Launchpad bug 1715698 in ubuntu-archive-tools "retry-autopkgtest-regressions could take a srcpkg and extra triggers" [Undecided,New] https://launchpad.net/bugs/1715698 | 16:30 |
| Laney | nacc: merci | 16:30 |
| Laney | if you (or anyone) work on it, feel free to subscribe me to the MP for a review | 16:30 |
| -queuebot:#ubuntu-release- Unapproved: tor (xenial-proposed/universe) [0.2.7.6-1ubuntu1 => 0.2.9.11-1ubuntu1~16.04.1] (no packageset) | 16:31 | |
| nacc | Laney: ack, will do! | 16:31 |
| SpamapS | RAOF: FYI, I uploaded bug 1711724 to both xenial and zesty (as you can see above). Would very much appreciate a queue-jump as that has been waiting a long time since doko sniped it out of the queue for the other bug originally. | 16:32 |
| ubot5` | bug 1711724 in python3.5 (Ubuntu Zesty) "Segfaults with dict" [High,In progress] https://launchpad.net/bugs/1711724 | 16:32 |
| SpamapS | aw man.. just noticed zesty has python 3.6.1 .. durn it | 16:33 |
| SpamapS | one more upload | 16:33 |
| stgraber | any chance someone on the release team can review https://bugs.launchpad.net/bugs/1715278 | 16:33 |
| ubot5` | Ubuntu bug 1715278 in lxc (Ubuntu) "[FFe] LXC 2.1" [Undecided,New] | 16:33 |
| stgraber | ? | 16:33 |
| stgraber | I'll be offline most of next week, so would be neat if we could get this uploaded and any issues sorted out before travel | 16:34 |
| -queuebot:#ubuntu-release- Unapproved: python3.6 (zesty-proposed/universe) [3.6.1-1 => 3.6.1-1ubuntu0~17.04.0] (no packageset) | 17:03 | |
| -queuebot:#ubuntu-release- Unapproved: rejected maas [source] (zesty-proposed) [2.2.3-6106-g314b2b2-0ubuntu1~17.04.1] | 17:05 | |
| SpamapS | RAOF: ^^ also python3.6 in zesty | 17:07 |
| -queuebot:#ubuntu-release- Unapproved: accepted docker.io [source] (zesty-proposed) [1.13.1-0ubuntu1~17.04.1] | 17:09 | |
| -queuebot:#ubuntu-release- Unapproved: accepted runc [source] (zesty-proposed) [1.0.0~rc2+docker1.13.1-0ubuntu1~17.04.1] | 17:15 | |
| xnox | Laney, so i take it autopkgtest will be running all weekend. given glibc and perl. sigh | 17:17 |
| -queuebot:#ubuntu-release- Unapproved: accepted docker.io [source] (xenial-proposed) [1.13.1-0ubuntu1~16.04.1] | 17:22 | |
| -queuebot:#ubuntu-release- Unapproved: accepted runc [source] (xenial-proposed) [1.0.0~rc2+docker1.13.1-0ubuntu1~16.04.1] | 17:29 | |
| -queuebot:#ubuntu-release- Unapproved: accepted tor [source] (xenial-proposed) [0.2.9.11-1ubuntu1~16.04.1] | 17:35 | |
| bdmurray | xnox: is bug 1713536 fixed in artful? | 17:37 |
| ubot5` | bug 1713536 in systemd (Ubuntu Zesty) "udev: boot script does not trigger subsystem coldplug" [Undecided,In progress] https://launchpad.net/bugs/1713536 | 17:37 |
| bdmurray | oh, nope systemd is in -proposed | 17:38 |
| Laney | xnox: seems like it :-) | 17:38 |
| Laney | at least non- huge stuff should get processed quickly | 17:38 |
| bdmurray | SpamapS: I'll have a look today | 17:39 |
| SpamapS | bdmurray: ty! | 17:46 |
| xnox | bdmurray, in proposed, yes. | 17:46 |
| xnox | bdmurray, but it will take a while to migrate due to backlogs =/ | 17:46 |
| bdmurray | xnox: is the SRU important enough to not wait for the fix in -proposed? | 17:47 |
| xnox | bdmurray, accepting into -proposed yes; releasing to -updates can wait until it migrates in artful too. | 17:48 |
| bdmurray | xnox: okay | 17:49 |
| -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (zesty-proposed) [232-21ubuntu6] | 18:04 | |
| -queuebot:#ubuntu-release- Unapproved: accepted fuse-umfuse-ext2 [source] (zesty-proposed) [0.4-1.1ubuntu0.17.04.1] | 18:15 | |
| -queuebot:#ubuntu-release- Unapproved: accepted fuse-umfuse-ext2 [source] (xenial-proposed) [0.4-1.1ubuntu0.16.04.1] | 18:17 | |
| -queuebot:#ubuntu-release- Unapproved: accepted fuse-umfuse-ext2 [source] (trusty-proposed) [0.4-1.1ubuntu0.14.04.1] | 18:19 | |
| -queuebot:#ubuntu-release- New source: uvp-monitor (artful-proposed/primary) [2.2.0.315-0ubuntu1] | 18:27 | |
| -queuebot:#ubuntu-release- Unapproved: accepted kdeplasma-addons [source] (zesty-proposed) [4:5.9.5-0ubuntu0.2] | 18:28 | |
| slangasek | FFe request: LP: #1715720 | 18:31 |
| ubot5` | Launchpad bug 1715720 in tortoisehg (Ubuntu) "FFe: sync tortoisehg 4.3.1-1 from unstable, unblocks new mercurial" [Undecided,New] https://launchpad.net/bugs/1715720 | 18:31 |
| -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-131.180] (core, kernel) | 18:48 | |
| -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-131.180] | 19:25 | |
| bdmurray | SpamapS: What happened here? 27 - libreadline-dev, libncursesw5-dev (>= 5.3), gcc (>= 4:6.3), | 19:37 |
| bdmurray | 28 + libreadline-dev, libncursesw5-dev (>= 5.3), | 19:37 |
| -queuebot:#ubuntu-release- Unapproved: accepted python3.6 [source] (zesty-proposed) [3.6.1-1ubuntu0~17.04.0] | 19:41 | |
| -queuebot:#ubuntu-release- Unapproved: accepted python3.5 [source] (xenial-proposed) [3.5.2-2ubuntu0~16.04.2] | 19:42 | |
| slangasek | thanks to whoever triggered the re-test to confirm pymol/ppc64el is broken in release | 19:51 |
| -queuebot:#ubuntu-release- Unapproved: accepted postgresql-9.6 [source] (zesty-proposed) [9.6.5-0ubuntu0.17.04] | 19:56 | |
| -queuebot:#ubuntu-release- Unapproved: accepted postgresql-9.5 [source] (xenial-proposed) [9.5.9-0ubuntu0.16.04] | 19:58 | |
| -queuebot:#ubuntu-release- Unapproved: accepted postgresql-9.3 [source] (trusty-proposed) [9.3.19-0ubuntu0.14.04] | 19:59 | |
| -queuebot:#ubuntu-release- Unapproved: accepted stunnel4 [source] (xenial-proposed) [3:5.30-1ubuntu0.1] | 20:24 | |
| -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (xenial-proposed) [2:8.4.0-0ubuntu5] | 20:26 | |
| -queuebot:#ubuntu-release- Unapproved: accepted ntp [source] (xenial-proposed) [1:4.2.8p4+dfsg-3ubuntu5.7] | 20:38 | |
| SpamapS | bdmurray: huh? | 20:41 |
| -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (xenial-proposed) [2:13.1.4-0ubuntu4] | 20:42 | |
| bdmurray | SpamapS: https://launchpadlibrarian.net/336180848/python3.5_3.5.3-1_3.5.3-1ubuntu0~17.04.0.diff.gz see the changed Build-Depends | 20:42 |
| SpamapS | bdmurray: I wonder if that happened because I did debuild -S on xenial? | 20:43 |
| SpamapS | I definitely didn't _try_ to add that line. | 20:44 |
| -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (trusty-proposed) [1.2.2-0ubuntu13.1.22] | 21:00 | |
| bdmurray | SpamapS: will you reupload? | 21:01 |
| SpamapS | bdmurray: happy to, it will be a little while though. | 21:02 |
| bdmurray | SpamapS: sure, I'll reject this one and feel free to ping me | 21:03 |
| -queuebot:#ubuntu-release- Unapproved: rejected python3.5 [source] (zesty-proposed) [3.5.3-1ubuntu0~17.04.0] | 21:04 | |
| -queuebot:#ubuntu-release- New sync: node-md5.js (artful-proposed/primary) [1.3.4-1] | 21:46 | |
| -queuebot:#ubuntu-release- New source: ibm-java71 (xenial-proposed/partner) [7.1.4.10-0ubuntu1] | 23:08 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!