[00:55] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.14.3 => 18.04.14.4] (core) [01:42] -queuebot:#ubuntu-release- Unapproved: rejected ubiquity [source] (bionic-proposed) [18.04.14.4] [01:44] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.14.3 => 18.04.14.4] (core) [01:55] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.14.4] [05:51] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.14.4 => 18.04.14.5] (core) [06:28] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.14.5] [07:32] infinity, you are right as usual, I'll fix that in the right way (TM) [07:32] it has been months since my last underlinking fix, but usually we spot them in package, not in testsuite, this is what tricked me [07:33] (btw a simple missing pthread link) [07:58] infinity, sorry again, but seems that even adding -pthread manually, the ldd doesn't show it [07:58] probably because there are lots of "pragma weak" stuff? [07:59] no-as-needed works, but manual link addition doesn't [07:59] infinity, https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1340250 [07:59] Ubuntu bug 1340250 in libunistring (Ubuntu) ""#pragma weak" symbol is 0 even when defined" [Undecided,New] [07:59] is this a real bug? [08:00] LocutusOfBorg: It could be a toolchain bug, or upstream may just say it's an oddity of how weak symbols work, and you need to -Wl,--no-as-needed -lpthread -Wl,--as-needed -lother -lstuff [08:00] LocutusOfBorg: Agreed that said response is a bit gross. :P [08:00] LocutusOfBorg: But that's, for instance, the only way you can intentionally link something that's not referenced at all. And weak references are a weird grey area. [08:01] LocutusOfBorg: So yeah, I wasn't saying that your fix was necessarily wrong, just that it was worth investigating. [08:02] I agree this is grey area, but I want something that I can submit upstream [08:02] did you see the bug? I updated it [08:02] and you are right, how can the linker decide if a library has to be added or not, when symbols are weak? [08:02] I haven't looked at it recently, but I'm familiar with the odd behaviour. [08:03] tltr; pthread symbols are all declared as weak in the code, linker strips pthread. [08:03] And it gets really muddy when you look at things like plugins (where weak symbols are the norm). [08:03] And you intentionally don't link plugins to the libraries that the runtime already links. [08:03] So, in that case, --no-as-needed gets it right. [08:04] my opinion is that wl,as-needed by default is a pain :) [08:04] (at least the divergence from debian is) [08:04] It's marginally goofy. The solution is to get more people using it. [08:04] We're not the only distro, thankfully. [08:04] true :) [08:04] Just, as you say, we haven't gotten Debian to do it. [08:05] do you think I should a) remove weak references b) enclose no-as-needed to every pthread linking? [08:05] I think b might be upstreamable [08:05] I'm honestly not sure how weak references make sense in the context where you then expect them to always exist. Unless you expect all your callers to link to pthread. [08:06] (Which might indeed be an expected thing via linker script or a pkg-config bit or some such) [08:06] At some point, something needs to get pthread into your address space, or you've lost. [08:06] of the program don't use them. Here we use them, because we don't want [08:06] every program that uses libintl to depend on libpthread. This assumes [08:06] that libpthread would not be loaded after libintl; i.e. if libintl is [08:06] loaded first, by an executable that does not depend on libpthread, and [08:06] then a module is dynamically loaded that depends on libpthread, libintl [08:06] will not be multithread-safe. */ [08:06] whether a function pointer's value, such as &pthread_mutex_init, is [08:06] non-NULL. However, some versions of GCC have a bug through which, in [08:06] PIC mode, &foo != NULL always evaluates to true if there is a direct [08:06] call to foo(...) in the same function. To avoid this, we test the [08:06] address of a function in libpthread that we don't use. */ [08:07] That's some serious acrobatics to avoid sanity. [08:07] seriously, I'm getting lost [08:08] I'd certainly say the Debian/Ubuntu solution should be to force it to be linked, full stop. [08:08] so, link libintl and libunistring to pthread, end of the story [08:08] The upstream solution, if they're intent on this weird "we want to only be thread-safe if you ask us as runtime to be" nonsense is pretty unclear. [08:08] this makes sense, but meh, I found even a "USE_POSIX_THREADS_WEAK" define [08:08] let me debug it [08:09] autoconf, why you so damn hard [08:21] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Bionic 18.04.1] (20101020ubuntu543.1) has been added [08:21] -queuebot:#ubuntu-release- Builds: Netboot arm64 [Bionic 18.04.1] (20101020ubuntu543.1) has been added [08:21] -queuebot:#ubuntu-release- Builds: Netboot armhf [Bionic 18.04.1] (20101020ubuntu543.1) has been added [08:21] -queuebot:#ubuntu-release- Builds: Netboot i386 [Bionic 18.04.1] (20101020ubuntu543.1) has been added [08:21] -queuebot:#ubuntu-release- Builds: Netboot ppc64el [Bionic 18.04.1] (20101020ubuntu543.1) has been added [08:21] -queuebot:#ubuntu-release- Builds: Netboot s390x [Bionic 18.04.1] (20101020ubuntu543.1) has been added [08:29] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Bionic 18.04.1] (20180724) has been added [08:29] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Bionic 18.04.1] (20180724) has been added [08:29] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Bionic 18.04.1] (20180724) has been added [08:29] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Bionic 18.04.1] (20180724) has been added [08:29] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Bionic 18.04.1] (20180724) has been added [08:29] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Bionic 18.04.1] (20180724) has been added [08:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Bionic 18.04.1] (20180724) has been added [08:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Bionic 18.04.1] (20180724) has been added [08:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Bionic 18.04.1] (20180724) has been added [08:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Bionic 18.04.1] (20180724) has been added [09:02] jibel: So, mvo has a theory that with my latest livecd-rootfs fix, your snapd bug will disappear on the next image. [09:03] jibel: I'm heading to bed soon after I trigger the last round of builds, but would be nice if you could confirm that. [09:03] jibel: (for bionic, I haven't hacked up cosmic) [09:03] infinity, yes thanks, I read his comment on #u-devel. I'll try on next build. [09:04] jibel: Shiny. Just triggered all the desktop builds, they should trickle out over the next few hours. [09:04] jibel: Would also be awesome if you could maybe put out a call for testing to QA, flavours, ubuntu-release, etc. I'm too brain dead to work a mail client. [09:04] infinity, I'll do that. enjoy your bed [09:05] jibel: Also note, Studio isn't LTS, so don't be surprised if they don't respond (and maybe remind them if they do :P) [09:05] There are no studio point release images. [09:05] jibel: And thanks. [09:06] Oh FFS. [09:06] jibel: Also, I'm an idiot and the images still have PROPOSED enabled. [09:06] Always forget one thing... [09:06] infinity: should I re-spin after these are done then? [09:07] sil2100: I'll get it when the dust settles. Staying awake and watching TV is easy, I don't have to think. ;) [09:07] Actually, on second thought, I imagine bugs will be found anyway. Naive to believe these will be perfect. [09:08] So, just let 'em be as they are. [09:08] I'll respin after I've woken up if there's nothing else to fix first. [09:08] jibel: But yeah, mention in your call for testing that the images have proposed enabled and are, thus, not final. But people should test them as if they are, so we don't have to iterate ad nauseum. [09:09] infinity: ok! [09:09] sil2100: Also, after I've slept, remind me that I only have a couple of days to help land a bunch of stuff for your xenial point release next week. :P [09:09] infinity: ;) [09:09] Most notably, systemd and d-i and almost certainly some livecd-rootfs fixes, cause builds are broken right now, AFAIK. [09:10] Broken builds? How? [09:10] sil2100: Oh, but if you're looking for something helpful to do for bionic, when the desktop images start spitting out, can you grab all the manifest files from the milestone images and diff (minus versions, obviously) with the release images, and maybe toss the results (if non-0) somewhere for me to look at? [09:11] sil2100: Broken as in a bunch of them were failing last I saw. But maybe that resolved itself. [09:11] infinity: I mean, I only checked the daily desktop one but it seems to be working [09:11] sil2100: But also willing to bet there are manifest oopses due to HWE stack shuffle. [09:11] (testing langpacks) [09:11] infinity: as for bionic, sure o/ [09:12] sil2100: I'm pretty sure I've seen xenial failures zip by my inbox. For some flavours, at least. [09:12] I have the kernel bumps for d-i ready, but I'm still waiting with that until I know if we have all the d-i bits in place already [09:12] So I'll probably push those out on Thursday or something [09:12] sil2100: We don't have all the d-i bits ready. [09:12] sil2100: (see systemd) [09:13] Yeah, which is why I didn't push it out yet, didn't want to have to re-upload for no reason [09:13] Ok! [09:16] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Bionic 18.04.1] (20180724) has been added [09:18] sil2100, jibel: Oh, other useful thing one of you can do is to fix all the URLs for bionic on the tracker. They all need bionic/ inserted in them, as we have to do for every LTS, or people who don't know how to drive a web browser complain that the images don't exist. :P [09:18] infinity: on it o/ [09:18] Ta. [09:19] (might be a bit slow with that since my laptop is suspiciously slow with a VM installing in the background) [09:29] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Bionic 18.04.1] (20180724) has been added [09:29] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Bionic 18.04.1] (20180724) has been added [09:34] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Bionic 18.04.1] (20180724) has been added [09:38] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Bionic 18.04.1] (20180724) has been added [09:38] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop i386 [Bionic 18.04.1] (20180724) has been added [09:41] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Bionic 18.04.1] (20180724) has been added [09:41] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Bionic 18.04.1] (20180724) has been added [09:41] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Bionic 18.04.1] (20180724) has been added [09:41] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Bionic 18.04.1] (20180724) has been added [09:46] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Bionic 18.04.1] (20180724) has been added [09:46] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Bionic 18.04.1] (20180724) has been added [09:46] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Bionic 18.04.1] (20180724) has been added [09:46] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Bionic 18.04.1] (20180724) has been added [09:48] jibel: if anything, I'm in progress of updating the DL links [09:54] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Bionic 18.04.1] (20180724) has been added [09:56] Lots of click-click [09:59] sil2100, I'm doing a sanity check of pending then will send the CFT [10:00] sil2100: please update the version for the libreoffice/i386 hint [10:01] oSoMoN: ^^^ [10:22] sil2100, are you done with the links? [10:23] would someone please bump the r-cran-curl/3.2-2build1/arm64 in vorlon's hints? [10:23] ginggs, helpful if you tell us what to, and hint as to why in the line above [10:24] ginggs, and that appears to be in sil2100s hints [10:25] apw: vorlon's hints has: [10:25] # crash in an unrelated module used only for testing [10:25] force-badtest r-cran-curl/3.1-2/arm64 r-cran-curl/3.2-1/arm64 [10:25] sil2100:force-badtest r-cran-curl/3.2-2build1/ppc64el r-cran-curl/3.2-2build1/s390x [10:25] but ... sil has that, which is the current version [10:25] right? so do you actually need a change ? [10:26] please make it 'force-badtest r-cran-curl/3.1-2/arm64 r-cran-curl/3.2-1/arm64 r-cran-curl/3.2-2build1/arm64' in vorlon's hints [10:26] oh god, disjoin arches in different files ... ugg [10:27] apw: i think they are different issues too - so i think keep arm64 in vorlon's file [10:28] ginggs, the discription in sil2100's sounds like the same thing [10:30] apw: ok, if you think it's better to merge, then please do [10:31] ginggs, i see the debian bug is yours, but that bug is for amd64 in actuality [10:31] jibel: still ongoing, it's not a super slow process but there's a lot of products [10:32] ginggs, yeah it is crashing in the amd64 one against the bug sil is quoting [10:32] so it seems plausible [10:34] ginggs, nayhow, i've done something vaguly sensible to make this less confusing, and kicked the can [10:34] apw: many thanks! [10:38] sil2100, need help? [10:38] can someone moderate my email to ubuntu-release ML ? [10:39] jibel: I'm almost finished I guess [10:42] jibel: ok, only the server+base ones are left, I'll finish those in a few moments - most important is that the desktop ones are all done for all flavours [10:44] jibel: if you feel like copy-pasting then I guess you could pick up the base ones, but if you have better things to do I'll get to those eventually [10:45] sil2100, k [10:55] jibel: server done, should I move on to base? [11:00] doko_, done [11:01] sil2100, i'm on it [11:01] sil2100, the issue with preinstalled snaps is not fixed [11:01] but gedit is installable now [11:03] eh [11:04] thx for fixing (server) [11:07] sil2100, done [11:08] jibel: thanks! [11:12] -queuebot:#ubuntu-release- New binary: ruby-bindex [amd64] (cosmic-proposed/none) [0.5.0-1] (no packageset) [11:13] -queuebot:#ubuntu-release- New binary: ruby-bindex [i386] (cosmic-proposed/none) [0.5.0-1] (no packageset) [11:13] -queuebot:#ubuntu-release- New binary: ruby-bindex [s390x] (cosmic-proposed/none) [0.5.0-1] (no packageset) [11:13] -queuebot:#ubuntu-release- New binary: ruby-bindex [ppc64el] (cosmic-proposed/none) [0.5.0-1] (no packageset) [11:14] -queuebot:#ubuntu-release- New binary: ruby-bindex [arm64] (cosmic-proposed/universe) [0.5.0-1] (no packageset) [11:14] -queuebot:#ubuntu-release- New binary: ruby-bindex [armhf] (cosmic-proposed/universe) [0.5.0-1] (no packageset) [11:27] -queuebot:#ubuntu-release- Unapproved: mutter (bionic-proposed/main) [3.28.2-2~ubuntu18.04.1 => 3.28.3-1~ubuntu18.04.1] (desktop-extra, ubuntu-desktop) [11:31] r-base migrated \o/ thanks apw! [11:43] ginggs, miracles [11:52] -queuebot:#ubuntu-release- Unapproved: gnome-shell (bionic-proposed/main) [3.28.2-0ubuntu0.18.04.1 => 3.28.3-0ubuntu0.18.04.1] (desktop-extra, mozilla, ubuntu-desktop) [12:02] sil2100, in only-ubiquity mode keyboard pre-selection is broken. for example if I select french as language the keyboard is set to Afghan (1st on the list) [12:06] it works with the release image [12:17] jibel: ok, let me look into that, I have some leads [12:24] sil2100, bug 1783326 [12:24] bug 1783326 in ubiquity (Ubuntu) "Wrong keyboard layout is preselected in only-ubiquity mode" [Undecided,New] https://launchpad.net/bugs/1783326 [13:02] slangasek: pinentry/1.1.0-1build2/amd64 decided it would be a fun idea to pass... can I get an updated hint please? [13:59] hi, what's the usual solution to a package that is in main, and inadvertently growed a runtime dependency on a package that that particular version of ubuntu doesn't even have? [13:59] https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1687095 case in point [13:59] Ubuntu bug 1687095 in crmsh (Ubuntu) "crm cluster health: NameError: global name 'parallax' is not defined" [High,Confirmed] [13:59] in xenial, it's in main, and has a runtime dependency on python-parallax which was only added in artful, and to universe [14:04] ahasenack, we typically avoid that happening [14:04] (which clearly we did not in this case) === plars_ is now known as plars [14:05] yeah :/ [14:05] perhaps it should be backed out [14:06] (on the assumption it is an SRU which broke it so [14:07] or was it broken in the -release pocket [14:08] it's in the release pocket, no update [14:08] *** 2.2.0-1 500 [14:08] 500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages [14:09] I also added UCA, thinking that maybe it would have an updated version, of even python-parallax available, but no [14:09] I thought openstack relied on crmsh (clustering) a lot for HA deployments [14:10] given crmsh got dropped to universe in a later series, that likely was done to fix the dependency issues [14:11] and indeed it starts depending on python-parallax somewhen [14:15] yes [14:15] one alternative could be to downgrade the xenial version back to when it wasn't requiring parallax, but that has its own problems, like possibly missing functionality [14:16] yeah, this is a true mess, and i am unsure what all options are even valid given the nominal component missmatch [15:21] tsimonq2: can I get a baseline retest of the pinentry in cosmic release with no proposed packages, please, to be sure it's genuinely a flaky test? [15:22] slangasek: tsimonq2: pinentry? [15:25] nvm [15:32] -queuebot:#ubuntu-release- Unapproved: openssl-ibmca (xenial-proposed/universe) [1.3.0-0ubuntu2.16.04.1 => 1.3.0-0ubuntu2.16.04.2] (no packageset) [15:35] I did schedule it tsimonq2 === jdstrand_ is now known as jdstrand [16:28] sil2100, any update on the kbd layout selection issue? [16:32] slangasek, https://autopkgtest.ubuntu.com/packages/pinentry/cosmic/amd64 [16:33] LocutusOfBorg: ta, hinting [16:33] thanks! [16:43] jibel: no, still investigating, I thought that maybe the latest console-setup update caused it but I'm not sure now [16:43] jibel: I mean, I tried reverting it but I'm not sure if that's enough, as the changes were in the postinst [16:44] (also reverted ubiquity and had the same result) [16:44] So now I'm actually debugging it normally from scratch [17:11] LocutusOfBorg, slangasek: thanks. [17:12] Bad tests are bad... [17:12] -queuebot:#ubuntu-release- New binary: apache-mode-el [amd64] (cosmic-proposed/universe) [2.1+4.g97bf66c-1] (no packageset) [17:12] -queuebot:#ubuntu-release- New binary: rust-csv-core [ppc64el] (cosmic-proposed/universe) [0.1.4-1] (no packageset) [17:12] -queuebot:#ubuntu-release- New binary: capstone [s390x] (cosmic-proposed/universe) [3.0.5-1] (no packageset) [17:12] -queuebot:#ubuntu-release- New binary: rust-csv-core [s390x] (cosmic-proposed/universe) [0.1.4-1] (no packageset) [17:13] -queuebot:#ubuntu-release- New binary: boxquote-el [amd64] (cosmic-proposed/universe) [2.1-2] (no packageset) [17:13] -queuebot:#ubuntu-release- New binary: capstone [i386] (cosmic-proposed/universe) [3.0.5-1] (no packageset) [17:14] -queuebot:#ubuntu-release- New binary: capstone [amd64] (cosmic-proposed/universe) [3.0.5-1] (no packageset) [17:14] -queuebot:#ubuntu-release- New binary: rust-csv-core [amd64] (cosmic-proposed/universe) [0.1.4-1] (no packageset) [17:14] -queuebot:#ubuntu-release- New binary: rust-csv-core [armhf] (cosmic-proposed/universe) [0.1.4-1] (no packageset) [17:14] -queuebot:#ubuntu-release- New binary: capstone [ppc64el] (cosmic-proposed/universe) [3.0.5-1] (no packageset) [17:14] -queuebot:#ubuntu-release- New binary: rust-csv-core [i386] (cosmic-proposed/universe) [0.1.4-1] (no packageset) [17:14] -queuebot:#ubuntu-release- New binary: rust-csv-core [arm64] (cosmic-proposed/universe) [0.1.4-1] (no packageset) [17:14] -queuebot:#ubuntu-release- New binary: capstone [arm64] (cosmic-proposed/universe) [3.0.5-1] (no packageset) [17:15] -queuebot:#ubuntu-release- New binary: capstone [armhf] (cosmic-proposed/universe) [3.0.5-1] (no packageset) [17:15] -queuebot:#ubuntu-release- New binary: gmbal-pfl [amd64] (cosmic-proposed/universe) [4.0.1-b003-1] (no packageset) [17:17] -queuebot:#ubuntu-release- New binary: nova [amd64] (cosmic-proposed/main) [2:18.0.0~b2-0ubuntu3] (openstack, ubuntu-server) [17:28] -queuebot:#ubuntu-release- New binary: hyperscan [i386] (cosmic-proposed/universe) [5.0.0-2] (no packageset) [17:49] -queuebot:#ubuntu-release- New binary: hyperscan [amd64] (cosmic-proposed/universe) [5.0.0-2] (no packageset) [20:29] jibel: Still around? [20:49] -queuebot:#ubuntu-release- Unapproved: console-setup (bionic-proposed/main) [1.178ubuntu2.2 => 1.178ubuntu2.3] (core) [21:39] infinity: Bug 1783416 is something one of my testers just found. It looks like fun. [21:39] bug 1783416 in syslinux (Ubuntu) "18.04.1 release candidate fails to boot " [Undecided,New] https://launchpad.net/bugs/1783416 [21:39] -queuebot:#ubuntu-release- Unapproved: ubiquity (xenial-proposed/main) [2.21.63.6 => 2.21.63.7] (core) [21:40] tsimonq2: using what process to copy the image to the USB stick? [21:40] slangasek, dd [21:40] ok [21:41] (not usb-creator, is the important thing, since that routinely creates unbootable things due to bugs in usb-creator rather than the image) [21:41] lynorian: You ran "sync" after dd, right? :P [21:42] Neither syslinux nor its configs have changed since release, so failing there can't possibly be a regression. [21:42] not explictly but I did leave it on for a little while after it finished [21:42] lynorian: Leaving it in for a little bit doesn't guarantee much. :) [21:43] ok will try sync [21:43] this could be a bit embarasing [21:49] oops pebkac [21:52] l [21:52] lynorian: Thanks for testing though :) [21:53] Was that it? [21:56] yes how have I not come across that before [22:24] -queuebot:#ubuntu-release- Unapproved: localechooser (bionic-proposed/main) [2.71ubuntu2 => 2.71ubuntu3] (core) [22:41] -queuebot:#ubuntu-release- Unapproved: accepted console-setup [source] (bionic-proposed) [1.178ubuntu2.3] [22:42] -queuebot:#ubuntu-release- Unapproved: accepted localechooser [source] (bionic-proposed) [2.71ubuntu3] [23:13] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.14.5 => 18.04.14.6] (core) [23:14] -queuebot:#ubuntu-release- New binary: simavr [s390x] (cosmic-proposed/universe) [1.6+dfsg-1] (no packageset) [23:14] -queuebot:#ubuntu-release- New binary: simavr [i386] (cosmic-proposed/universe) [1.6+dfsg-1] (no packageset) [23:14] just like to point out, if you prefer commandline tools to GUI tools, `dc3dd if=file.iso of=/dev/sdX` has worked tremendously well for me for nearly a decade now. Automatic sector size selection so no bs=, and it will sync before returning unless asked not to with the nosync option. [23:14] -queuebot:#ubuntu-release- New binary: simavr [ppc64el] (cosmic-proposed/universe) [1.6+dfsg-1] (no packageset) [23:15] -queuebot:#ubuntu-release- New binary: simavr [amd64] (cosmic-proposed/universe) [1.6+dfsg-1] (no packageset) [23:16] -queuebot:#ubuntu-release- New binary: simavr [arm64] (cosmic-proposed/universe) [1.6+dfsg-1] (no packageset) [23:16] -queuebot:#ubuntu-release- New binary: simavr [armhf] (cosmic-proposed/universe) [1.6+dfsg-1] (no packageset) [23:17] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.14.6] [23:17] -queuebot:#ubuntu-release- New: accepted simavr [amd64] (cosmic-proposed) [1.6+dfsg-1] [23:17] -queuebot:#ubuntu-release- New: accepted simavr [armhf] (cosmic-proposed) [1.6+dfsg-1] [23:17] -queuebot:#ubuntu-release- New: accepted simavr [ppc64el] (cosmic-proposed) [1.6+dfsg-1] [23:17] -queuebot:#ubuntu-release- New: accepted simavr [arm64] (cosmic-proposed) [1.6+dfsg-1] [23:17] -queuebot:#ubuntu-release- New: accepted simavr [s390x] (cosmic-proposed) [1.6+dfsg-1] [23:17] -queuebot:#ubuntu-release- New: accepted simavr [i386] (cosmic-proposed) [1.6+dfsg-1] [23:18] -queuebot:#ubuntu-release- New: accepted nova [amd64] (cosmic-proposed) [2:18.0.0~b2-0ubuntu3] [23:18] -queuebot:#ubuntu-release- New: accepted capstone [amd64] (cosmic-proposed) [3.0.5-1] [23:18] -queuebot:#ubuntu-release- New: accepted capstone [armhf] (cosmic-proposed) [3.0.5-1] [23:18] -queuebot:#ubuntu-release- New: accepted capstone [ppc64el] (cosmic-proposed) [3.0.5-1] [23:18] -queuebot:#ubuntu-release- New: accepted ruby-bindex [amd64] (cosmic-proposed) [0.5.0-1] [23:18] -queuebot:#ubuntu-release- New: accepted ruby-bindex [armhf] (cosmic-proposed) [0.5.0-1] [23:18] -queuebot:#ubuntu-release- New: accepted ruby-bindex [ppc64el] (cosmic-proposed) [0.5.0-1] [23:18] -queuebot:#ubuntu-release- New: accepted capstone [arm64] (cosmic-proposed) [3.0.5-1] [23:18] -queuebot:#ubuntu-release- New: accepted capstone [s390x] (cosmic-proposed) [3.0.5-1] [23:18] -queuebot:#ubuntu-release- New: accepted ruby-bindex [i386] (cosmic-proposed) [0.5.0-1] [23:18] -queuebot:#ubuntu-release- New: accepted capstone [i386] (cosmic-proposed) [3.0.5-1] [23:18] -queuebot:#ubuntu-release- New: accepted ruby-bindex [s390x] (cosmic-proposed) [0.5.0-1] [23:18] -queuebot:#ubuntu-release- New: accepted ruby-bindex [arm64] (cosmic-proposed) [0.5.0-1] [23:19] -queuebot:#ubuntu-release- New: accepted apache-mode-el [amd64] (cosmic-proposed) [2.1+4.g97bf66c-1] [23:19] -queuebot:#ubuntu-release- New: accepted gmbal-pfl [amd64] (cosmic-proposed) [4.0.1-b003-1] [23:19] -queuebot:#ubuntu-release- New: accepted boxquote-el [amd64] (cosmic-proposed) [2.1-2] [23:19] -queuebot:#ubuntu-release- New: accepted hyperscan [amd64] (cosmic-proposed) [5.0.0-2] [23:19] -queuebot:#ubuntu-release- New: accepted rust-csv-core [amd64] (cosmic-proposed) [0.1.4-1] [23:19] -queuebot:#ubuntu-release- New: accepted rust-csv-core [armhf] (cosmic-proposed) [0.1.4-1] [23:19] -queuebot:#ubuntu-release- New: accepted rust-csv-core [ppc64el] (cosmic-proposed) [0.1.4-1] [23:19] -queuebot:#ubuntu-release- New: accepted hyperscan [i386] (cosmic-proposed) [5.0.0-2] [23:19] -queuebot:#ubuntu-release- New: accepted rust-csv-core [i386] (cosmic-proposed) [0.1.4-1] [23:19] -queuebot:#ubuntu-release- New: accepted rust-csv-core [arm64] (cosmic-proposed) [0.1.4-1] [23:19] -queuebot:#ubuntu-release- New: accepted rust-csv-core [s390x] (cosmic-proposed) [0.1.4-1]