[00:00] <Eickmeyer> Hi ubuntu-release. Might have a late sync coming from Debian for entangle if that's OK. bug 1716656
[00:41] <vorlon> ginggs: gyoto sorted
[01:16] -queuebot:#ubuntu-release- Packageset: Removed crystalhd from i386-whitelist in jammy
[01:16] -queuebot:#ubuntu-release- Packageset: Removed gcc-8 from i386-whitelist in jammy
[01:16] -queuebot:#ubuntu-release- Packageset: Removed nvidia-graphics-drivers-460-server from i386-whitelist in jammy
[01:16] -queuebot:#ubuntu-release- Packageset: Removed nvidia-graphics-drivers-495 from i386-whitelist in jammy
[01:16] -queuebot:#ubuntu-release- Packageset: Removed nvidia-graphics-drivers-tesla-470 from i386-whitelist in jammy
[01:16] -queuebot:#ubuntu-release- Packageset: Added pth to i386-whitelist in jammy
[01:28] <tumbleweed> Eickmeyer: do it
[01:28] <Eickmeyer> tumbleweed: Ok, as soon as 3.0-3 lands in debian, I'll do the sync.
[01:34] -queuebot:#ubuntu-release- Unapproved: weechat-matrix (jammy-proposed/universe) [0.3.0-3 => 0.3.0-3.1] (no packageset) (sync)
[01:34] -queuebot:#ubuntu-release- Unapproved: workrave (jammy-proposed/universe) [1.10.49-3 => 1.10.50-1] (no packageset) (sync)
[01:35] -queuebot:#ubuntu-release- Unapproved: accepted weechat-matrix [sync] (jammy-proposed) [0.3.0-3.1]
[01:35] -queuebot:#ubuntu-release- Unapproved: accepted workrave [sync] (jammy-proposed) [1.10.50-1]
[01:35] -queuebot:#ubuntu-release- Unapproved: brag (jammy-proposed/universe) [1.4.1-2.1 => 1.4.1-2.2] (no packageset) (sync)
[01:36] -queuebot:#ubuntu-release- Unapproved: accepted brag [sync] (jammy-proposed) [1.4.1-2.2]
[06:28] <vorlon> doko: hey, so I've gone back and looked at the message history about why strace was being included in the i386 seed, and see you said it was "needed by binfmt-support".  I can find no evidence anywhere that this is true, so I'm dropping it from the whitelist as part of the pre-release cleanup.
[06:28] <vorlon> doko: if you can provide a concrete reference, we can figure out how to get it into the seed properly and resurrect the binary
[06:34] -queuebot:#ubuntu-release- Unapproved: sqlmap (jammy-proposed/universe) [1.6.3-1 => 1.6.4-2] (no packageset) (sync)
[06:35] -queuebot:#ubuntu-release- Unapproved: accepted sqlmap [sync] (jammy-proposed) [1.6.4-2]
[06:37] <vorlon> doko: actually, after saying that, it seems something now has pulled in strace correctly as update-i386-whitelist doesn't want to drop it from the seed
[06:46] <vorlon> doko: I reverse myself again.  Yes, strace i386 binaries removed now
[06:46] -queuebot:#ubuntu-release- Packageset: Removed strace from i386-whitelist in jammy
[06:52] <seb128> hey release team, could we get a review for https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1968215 ?
[06:52] <seb128> it's late but important for the firefox transition from the deb to the snap
[06:53] <seb128> also it's new code so low regression risk
[06:53] <Wimpy> Morning o/
[06:53] <Wimpy> Please accept ubuntu-mate-artwork 22.04.15
[06:57] <seb128> @vorlon, ^ can you help with the portal ffe request?
[06:59] <vorlon> seb128: done
[06:59] <seb128> vorlon, thanks!
[07:15] -queuebot:#ubuntu-release- Unapproved: dkms (jammy-proposed/main) [2.8.7-2ubuntu1 => 2.8.7-2ubuntu2] (i386-whitelist, ubuntu-desktop)
[07:25] -queuebot:#ubuntu-release- New: rejected rpiboot [source] (jammy-proposed) [0~20220131+git693d5be-0ubuntu1]
[07:25] -queuebot:#ubuntu-release- New: accepted rust-xkbcommon-sys [arm64] (jammy-proposed) [0.7.5-1]
[07:31] -queuebot:#ubuntu-release- New sync: gcc-11-cross-mipsen (jammy-proposed/primary) [5+c1]
[07:34] -queuebot:#ubuntu-release- New: accepted rpiboot [source] (jammy-proposed) [0~20220315+git6fa2ec0+nowin-0ubuntu1]
[07:37] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [sync] (jammy-proposed) [0.20.0-3]
[07:38] -queuebot:#ubuntu-release- New: accepted blueprint-compiler [sync] (jammy-proposed) [0~20220302-2]
[07:38] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-manager [sync] (jammy-proposed) [0.2.3-2]
[07:39] -queuebot:#ubuntu-release- New: accepted hyperspy [sync] (jammy-proposed) [1.6.1-1]
[07:39] -queuebot:#ubuntu-release- New: accepted astunparse [sync] (jammy-proposed) [1.6.3-1]
[07:39] -queuebot:#ubuntu-release- New: accepted gcc-11-cross-mipsen [sync] (jammy-proposed) [5+c1]
[07:39] -queuebot:#ubuntu-release- New: accepted opencu [sync] (jammy-proposed) [3-2]
[07:39] -queuebot:#ubuntu-release- New binary: rpiboot [ppc64el] (jammy-proposed/none) [0~20220315+git6fa2ec0+nowin-0ubuntu1] (no packageset)
[07:39] -queuebot:#ubuntu-release- New: accepted bettercap [sync] (jammy-proposed) [2.32.0-1]
[07:39] -queuebot:#ubuntu-release- New binary: rpiboot [amd64] (jammy-proposed/none) [0~20220315+git6fa2ec0+nowin-0ubuntu1] (no packageset)
[07:39] -queuebot:#ubuntu-release- New: accepted mptcpd [sync] (jammy-proposed) [0.9-1]
[07:39] -queuebot:#ubuntu-release- New binary: rpiboot [s390x] (jammy-proposed/none) [0~20220315+git6fa2ec0+nowin-0ubuntu1] (no packageset)
[07:40] -queuebot:#ubuntu-release- New binary: rpiboot [arm64] (jammy-proposed/none) [0~20220315+git6fa2ec0+nowin-0ubuntu1] (no packageset)
[07:41] -queuebot:#ubuntu-release- New binary: blueprint-compiler [amd64] (jammy-proposed/none) [0~20220302-2] (no packageset)
[07:41] -queuebot:#ubuntu-release- New binary: rpiboot [armhf] (jammy-proposed/none) [0~20220315+git6fa2ec0+nowin-0ubuntu1] (no packageset)
[07:42] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [amd64] (jammy-proposed/none) [0.20.0-3] (no packageset)
[07:42] -queuebot:#ubuntu-release- New binary: opencu [amd64] (jammy-proposed/none) [3-2] (no packageset)
[07:42] <cpaelzer> ubuntu-release: Hi, we finally got the last MIR completed that was targetted at jammy (https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1950321) but while we prep the uploads given the time this also needs an FFE ack I think
[07:42] <cpaelzer> anyone around that could have a look?
[07:42] -queuebot:#ubuntu-release- New: accepted blueprint-compiler [amd64] (jammy-proposed) [0~20220302-2]
[07:42] -queuebot:#ubuntu-release- New: accepted opencu [amd64] (jammy-proposed) [3-2]
[07:42] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [amd64] (jammy-proposed) [0.20.0-3]
[07:43] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [arm64] (jammy-proposed/none) [0.20.0-3] (no packageset)
[07:43] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [s390x] (jammy-proposed/none) [0.20.0-3] (no packageset)
[07:43] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [ppc64el] (jammy-proposed/none) [0.20.0-3] (no packageset)
[07:43] -queuebot:#ubuntu-release- New binary: mptcpd [ppc64el] (jammy-proposed/none) [0.9-1] (no packageset)
[07:43] <vorlon> waveform: please check the output of 'lintian -I rpiboot*deb'
[07:44] -queuebot:#ubuntu-release- New binary: gnome-shell-pomodoro [armhf] (jammy-proposed/none) [0.20.0-3] (no packageset)
[07:44] -queuebot:#ubuntu-release- New binary: opencu [arm64] (jammy-proposed/none) [3-2] (no packageset)
[07:45] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [arm64] (jammy-proposed) [0.20.0-3]
[07:45] -queuebot:#ubuntu-release- New: accepted mptcpd [ppc64el] (jammy-proposed) [0.9-1]
[07:45] -queuebot:#ubuntu-release- New: accepted rpiboot [amd64] (jammy-proposed) [0~20220315+git6fa2ec0+nowin-0ubuntu1]
[07:45] -queuebot:#ubuntu-release- New: accepted rpiboot [armhf] (jammy-proposed) [0~20220315+git6fa2ec0+nowin-0ubuntu1]
[07:45] -queuebot:#ubuntu-release- New: accepted rpiboot [s390x] (jammy-proposed) [0~20220315+git6fa2ec0+nowin-0ubuntu1]
[07:45] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [armhf] (jammy-proposed) [0.20.0-3]
[07:45] -queuebot:#ubuntu-release- New: accepted rpiboot [arm64] (jammy-proposed) [0~20220315+git6fa2ec0+nowin-0ubuntu1]
[07:45] -queuebot:#ubuntu-release- New: accepted opencu [arm64] (jammy-proposed) [3-2]
[07:45] -queuebot:#ubuntu-release- New: accepted rpiboot [ppc64el] (jammy-proposed) [0~20220315+git6fa2ec0+nowin-0ubuntu1]
[07:45] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [ppc64el] (jammy-proposed) [0.20.0-3]
[07:45] -queuebot:#ubuntu-release- New: accepted gnome-shell-pomodoro [s390x] (jammy-proposed) [0.20.0-3]
[07:46] -queuebot:#ubuntu-release- Packageset: Removed binfmt-support from i386-whitelist in jammy
[07:46] -queuebot:#ubuntu-release- Packageset: Removed libeatmydata from i386-whitelist in jammy
[07:47] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (jammy-proposed) [22.04.13]
[07:48] -queuebot:#ubuntu-release- New binary: mptcpd [armhf] (jammy-proposed/none) [0.9-1] (no packageset)
[07:49] -queuebot:#ubuntu-release- New binary: mptcpd [arm64] (jammy-proposed/none) [0.9-1] (no packageset)
[07:50] -queuebot:#ubuntu-release- New: accepted mptcpd [arm64] (jammy-proposed) [0.9-1]
[07:50] -queuebot:#ubuntu-release- New: accepted mptcpd [armhf] (jammy-proposed) [0.9-1]
[07:57] -queuebot:#ubuntu-release- Unapproved: accepted evince [sync] (jammy-proposed) [42.1-2]
[07:58] -queuebot:#ubuntu-release- Unapproved: accepted gnome-session [source] (jammy-proposed) [42.0-1ubuntu2]
[07:58] -queuebot:#ubuntu-release- Unapproved: accepted v4l2loopback [source] (jammy-proposed) [0.12.5-1ubuntu4]
[07:58] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (jammy-proposed) [2:20.0.0-0ubuntu3]
[08:05] -queuebot:#ubuntu-release- New binary: rpiboot [riscv64] (jammy-proposed/none) [0~20220315+git6fa2ec0+nowin-0ubuntu1] (no packageset)
[08:06] -queuebot:#ubuntu-release- New binary: opencu [riscv64] (jammy-proposed/none) [3-2] (no packageset)
[08:11] <sil2100> tjaalton: hey! Can you get the desktop team's perspective on LP: #1968167 (seb I guess?)? Put a comment on  the bug for this
[08:25] <tjaalton> seb128: ^ how about it? :)
[08:26] <seb128> tjaalton, sorry I just connected and don't have the backlog
[08:27] <tjaalton> ah
[08:27] <tjaalton> https://launchpad.net/bugs/1968167
[08:27] -queuebot:#ubuntu-release- New: accepted opencu [riscv64] (jammy-proposed) [3-2]
[08:27] -queuebot:#ubuntu-release- New: accepted rpiboot [riscv64] (jammy-proposed) [0~20220315+git6fa2ec0+nowin-0ubuntu1]
[08:29] <seb128> sil2100, wacom is a special class of hardware and not essential to a working system so I feel confident that even if there was to be a regression it wouldn't be a release issue and would be fine to deal with a SRU
[08:30] <tjaalton> thanks
[08:34] <sil2100> seb128: thank you!
[08:35] <sil2100> tjaalton: ok, let me accept this - but promise me that IF my wacom tablet suddenly stops working, you'll be sure to SRU the new version to fix this ;p
[08:36] <tjaalton> sil2100: ack ;)
[08:36] <tjaalton> my intuos5m is fine :)
[08:36] -queuebot:#ubuntu-release- Unapproved: accepted xf86-input-wacom [source] (jammy-proposed) [1:1.0.0-3ubuntu1]
[08:37] -queuebot:#ubuntu-release- Unapproved: accepted crmsh [source] (jammy-proposed) [4.3.1-1ubuntu2]
[08:37] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-artwork [source] (jammy-proposed) [22.04.15]
[08:38] -queuebot:#ubuntu-release- Unapproved: accepted dkms [source] (jammy-proposed) [2.8.7-2ubuntu2]
[08:38] -queuebot:#ubuntu-release- Unapproved: accepted udisks2 [source] (jammy-proposed) [2.9.4-1ubuntu2]
[08:59] -queuebot:#ubuntu-release- Unapproved: entangle (jammy-proposed/universe) [3.0-1build1 => 3.0-3] (ubuntustudio) (sync)
[09:13] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-manager [amd64] (jammy-proposed/universe) [0.2.3-2] (no packageset)
[09:14] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-manager [ppc64el] (jammy-proposed/universe) [0.2.3-2] (no packageset)
[09:14] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-manager [s390x] (jammy-proposed/universe) [0.2.3-2] (no packageset)
[09:15] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-manager [armhf] (jammy-proposed/universe) [0.2.3-2] (no packageset)
[09:17] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-manager [arm64] (jammy-proposed/universe) [0.2.3-2] (no packageset)
[09:18] -queuebot:#ubuntu-release- Unapproved: python-eventlet (jammy-proposed/main) [0.30.2-5 => 0.30.2-5ubuntu1] (openstack)
[09:20] -queuebot:#ubuntu-release- Unapproved: xdg-desktop-portal (jammy-proposed/main) [1.14.2-1 => 1.14.2-1ubuntu1] (desktop-core)
[09:21] -queuebot:#ubuntu-release- Unapproved: ltrace (jammy-proposed/main) [0.7.3-6.1ubuntu5 => 0.7.3-6.1ubuntu6] (core)
[09:22] -queuebot:#ubuntu-release- Unapproved: rtl8821ce (jammy-proposed/universe) [<IP_ADDRESS>-0ubuntu8 => <IP_ADDRESS>-0ubuntu9] (kernel-dkms)
[09:34] -queuebot:#ubuntu-release- Unapproved: libmbim (focal-proposed/main) [1.24.8-1~20.04 => 1.26.2-1~ubuntu20.04.1] (desktop-core, i386-whitelist)
[09:34] -queuebot:#ubuntu-release- Unapproved: libqmi (focal-proposed/main) [1.28.6-1~20.04.1 => 1.30.4-1~ubuntu20.04.1] (desktop-core, i386-whitelist)
[09:37] -queuebot:#ubuntu-release- Unapproved: modemmanager (focal-proposed/main) [1.16.6-2~20.04.1 => 1.18.6-1~ubuntu20.04.1] (desktop-core, i386-whitelist)
[09:51] -queuebot:#ubuntu-release- New binary: gnome-shell-extension-manager [riscv64] (jammy-proposed/universe) [0.2.3-2] (no packageset)
[10:55] -queuebot:#ubuntu-release- Unapproved: csound (jammy-proposed/universe) [1:6.17.0~dfsg-3 => 1:6.17.0~dfsg-3ubuntu1] (ubuntustudio)
[10:57] -queuebot:#ubuntu-release- Unapproved: qtbase-opensource-src (jammy-proposed/universe) [5.15.3+dfsg-1 => 5.15.3+dfsg-2] (i386-whitelist, kubuntu, qt5) (sync)
[11:15] <paride> vorlon, https://code.launchpad.net/~paride/ubuntu-cdimage/ubuntu-cdimage/+merge/418941
[11:16] <paride> vorlon, the Focal images look sane and the oversize is minimal
[11:28] -queuebot:#ubuntu-release- Unapproved: mate-terminal (jammy-proposed/universe) [1.26.0-1ubuntu1 => 1.26.0-1ubuntu2] (ubuntu-mate, ubuntukylin)
[11:31] -queuebot:#ubuntu-release- Unapproved: mate-desktop-environment (jammy-proposed/universe) [1.26.0+1ubuntu5 => 1.26.0+1ubuntu6] (ubuntu-mate)
[11:46] -queuebot:#ubuntu-release- Unapproved: accepted entangle [sync] (jammy-proposed) [3.0-3]
[11:46] -queuebot:#ubuntu-release- Unapproved: accepted xdg-desktop-portal [source] (jammy-proposed) [1.14.2-1ubuntu1]
[11:46] -queuebot:#ubuntu-release- Unapproved: accepted python-eventlet [source] (jammy-proposed) [0.30.2-5ubuntu1]
[11:47] -queuebot:#ubuntu-release- Unapproved: accepted csound [source] (jammy-proposed) [1:6.17.0~dfsg-3ubuntu1]
[11:47] -queuebot:#ubuntu-release- Unapproved: accepted rtl8821ce [source] (jammy-proposed) [<IP_ADDRESS>-0ubuntu9]
[11:47] -queuebot:#ubuntu-release- Unapproved: accepted ltrace [source] (jammy-proposed) [0.7.3-6.1ubuntu6]
[11:47] -queuebot:#ubuntu-release- Unapproved: gnome-control-center (jammy-proposed/main) [1:41.4-1ubuntu9 => 1:41.4-1ubuntu10] (ubuntu-desktop)
[11:49] -queuebot:#ubuntu-release- Unapproved: accepted qtbase-opensource-src [sync] (jammy-proposed) [5.15.3+dfsg-2]
[11:50] -queuebot:#ubuntu-release- Unapproved: accepted gnome-control-center [source] (jammy-proposed) [1:41.4-1ubuntu10]
[11:50] -queuebot:#ubuntu-release- Unapproved: accepted mate-terminal [source] (jammy-proposed) [1.26.0-1ubuntu2]
[11:50] -queuebot:#ubuntu-release- Unapproved: accepted mate-desktop-environment [source] (jammy-proposed) [1.26.0+1ubuntu6]
[12:00] <cpaelzer> hi, another ping for ubuntu-release to please FFE ack https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1950321/comments/22 which is important but late due the wait for the security review on the MIR bug.
[12:05] <sil2100> cpaelzer: lookin
[12:25] -queuebot:#ubuntu-release- Unapproved: mate-settings-daemon (jammy-proposed/universe) [1.26.0-1 => 1.26.0-1ubuntu1] (ubuntu-mate)
[12:36] <jbicha> please ignore gnome-shell-pomodoro i386 autopkgtest failures since it's not built for i386
[12:38] -queuebot:#ubuntu-release- Unapproved: bitlbee (jammy-proposed/universe) [3.6-1.2 => 3.6-1.3] (no packageset) (sync)
[12:38] -queuebot:#ubuntu-release- Unapproved: accepted bitlbee [sync] (jammy-proposed) [3.6-1.3]
[12:53] -queuebot:#ubuntu-release- Unapproved: whois (jammy-proposed/main) [5.5.11 => 5.5.13] (core) (sync)
[13:02] <cpaelzer> sil2100: thanks for the first look - I answered your questions in https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1950321/comments/24
[13:44] -queuebot:#ubuntu-release- Unapproved: xz-utils (jammy-proposed/main) [5.2.5-2build2 => 5.2.5-2ubuntu1] (core, i386-whitelist)
[13:47] -queuebot:#ubuntu-release- Unapproved: gzip (jammy-proposed/main) [1.10-4ubuntu3 => 1.10-4ubuntu4] (core, i386-whitelist)
[13:47] -queuebot:#ubuntu-release- Unapproved: mate-control-center (jammy-proposed/universe) [1.26.0-2ubuntu2 => 1.26.0-2ubuntu3] (ubuntu-mate)
[13:53] -queuebot:#ubuntu-release- Unapproved: accepted mate-settings-daemon [source] (jammy-proposed) [1.26.0-1ubuntu1]
[13:53] -queuebot:#ubuntu-release- Unapproved: accepted xz-utils [source] (jammy-proposed) [5.2.5-2ubuntu1]
[14:19] <athos> hello :) pinging ubuntu-release to ack this FFe: https://bugs.launchpad.net/ubuntu/+source/cl-plus-ssl/+bug/1960615
[14:26] <tumbleweed> approved
[14:55] -queuebot:#ubuntu-release- Unapproved: gnome-bluetooth3 (jammy-proposed/universe) [42.0-3 => 42.0-4ubuntu1] (no packageset)
[14:57] -queuebot:#ubuntu-release- Unapproved: accepted gnome-bluetooth3 [source] (jammy-proposed) [42.0-4ubuntu1]
[15:34] <Wimpy> Please accept mate-control-center 1.26.0-2ubuntu3
[15:42] <vorlon> xnox: https://people.canonical.com/~ubuntu-archive/component-mismatches.html wants to demote linux-ibm, something needs seeding
[15:47] <vorlon> xnox: likewise, nvidia-graphics-drivers-{470-server,510} have binary component-mismatches; these are compat packages but something seems to need fixing to hold them in restricted
[15:55] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-manager [riscv64] (jammy-proposed) [0.2.3-2]
[15:55] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-manager [amd64] (jammy-proposed) [0.2.3-2]
[15:55] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-manager [armhf] (jammy-proposed) [0.2.3-2]
[15:55] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-manager [s390x] (jammy-proposed) [0.2.3-2]
[15:55] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-manager [arm64] (jammy-proposed) [0.2.3-2]
[15:56] -queuebot:#ubuntu-release- New: accepted gnome-shell-extension-manager [ppc64el] (jammy-proposed) [0.2.3-2]
[16:27] -queuebot:#ubuntu-release- Unapproved: cl-plus-ssl (jammy-proposed/universe) [20200609.gitff4634a-1build1 => 20220328.git8b91648-3] (no packageset) (sync)
[16:28] -queuebot:#ubuntu-release- Unapproved: accepted cl-plus-ssl [sync] (jammy-proposed) [20220328.git8b91648-3]
[16:44] -queuebot:#ubuntu-release- New sync: golang-github-mdlayher-dhcp6 (jammy-proposed/primary) [0.0~git20190311.2a67805-2]
[16:46] -queuebot:#ubuntu-release- New sync: golang-github-iglou-eu-go-wildcard (jammy-proposed/primary) [1.0.3-2]
[17:10] <cpaelzer> ubuntu-release: hi, the questions you had are answered on https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1950321 for hopefully an FFE ack to seed it via deps from qemu+samba.
[17:46] <sergiodj> ubuntu-archive: hello, could someone take a quick look at https://code.launchpad.net/~sergiodj/britney/+git/hints-ubuntu/+merge/419138 please?
[17:58] <vorlon> sergiodj: please do a baseline retest (retry-autopkgtest-regressions --no-proposed) instead
[17:59] <sergiodj> vorlon: ACK
[17:59] <vorlon> sergiodj: ah except that there was a baseline retest 2 days ago so this seems unlikely to succeed
[17:59] <sergiodj> yes
[17:59] <vorlon> basically, britney knows that these tests have regressed in -proposed
[17:59] <vorlon> so nack on regressing these tests as part of a docker.io SRU
[18:06] <sergiodj> fair enough.  back to the drawing board, then
[18:06] <sergiodj> the problem here is that I cannot reproduce this bug locally, which makes it really hard to determine what's happening
[18:42] -queuebot:#ubuntu-release- Unapproved: accepted whois [sync] (jammy-proposed) [5.5.13]
[18:58] -queuebot:#ubuntu-release- Unapproved: accepted mate-control-center [source] (jammy-proposed) [1.26.0-2ubuntu3]
[18:59] -queuebot:#ubuntu-release- Unapproved: pysurfer (jammy-proposed/universe) [0.11.0-2 => 0.11.0-3] (no packageset) (sync)
[19:00] -queuebot:#ubuntu-release- Unapproved: accepted pysurfer [sync] (jammy-proposed) [0.11.0-3]
[19:19] -queuebot:#ubuntu-release- Unapproved: accepted gzip [source] (jammy-proposed) [1.10-4ubuntu4]
[19:19] <vorlon> juliank: uploading libjpeg8-empty
[19:20] <juliank> vorlon: sorry for missing
[19:21] <vorlon> cpaelzer: hi, not sure if you missed my ping about the fact that https://bugs.launchpad.net/ubuntu/+source/python-xmlschema/+bug/195336 is still open/in progress despite the fact that python-xmlschema has been promoted to main?
[19:22] -queuebot:#ubuntu-release- Unapproved: libjpeg8-empty (jammy-proposed/main) [8c-2ubuntu9 => 8c-2ubuntu10] (core, i386-whitelist)
[19:23] -queuebot:#ubuntu-release- Unapproved: accepted libjpeg8-empty [source] (jammy-proposed) [8c-2ubuntu10]
[19:23] -queuebot:#ubuntu-release- Unapproved: sbd (jammy-proposed/universe) [1.5.1-1build1 => 1.5.1-1ubuntu1] (no packageset)
[19:24] -queuebot:#ubuntu-release- Unapproved: accepted sbd [source] (jammy-proposed) [1.5.1-1ubuntu1]
[19:26] -queuebot:#ubuntu-release- Unapproved: snapd (jammy-proposed/main) [2.55.2+22.04.1 => 2.55.3+22.04] (desktop-core, ubuntu-server)
[19:35] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (jammy-proposed) [2.55.3+22.04]
[19:36] -queuebot:#ubuntu-release- Unapproved: horizon (jammy-proposed/main) [4:22.1.0-0ubuntu1 => 4:22.1.0-0ubuntu2] (openstack)
[20:20] <cpaelzer> vorlon: I did indeed not see that ping or bug - thanks
[20:21] <cpaelzer> coreycb: jamespage: https://bugs.launchpad.net/ubuntu/+source/python-xmlschema/+bug/195336
[20:21] <cpaelzer> umm, I linked it as -is - but this isn't python-xmlschema ...
[20:22] <vorlon> https://bugs.launchpad.net/ubuntu/+source/python-xmlschema/+bug/1953363
[20:22] <vorlon> sorry, not sure where that last digit went
[20:22] <cpaelzer> Oh I got it, - it is the bug task that you meant
[20:22] <cpaelzer> thanks
[20:22] <cpaelzer> fixed the state already
[20:22] <vorlon> ta
[20:23] <cpaelzer> np vorlon
[20:23] <cpaelzer> do you - by any chance - have 5 minutes to consider FFE-acking https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1950321 ?
[20:23] <cpaelzer> sil2100: was having a look before, but I'm sure by now he has entered his deserved EOW
[20:26] <vorlon> sure
[20:26] <cpaelzer> thanks in advance, and no hurry - it is very much EOD for me for today anyway
[20:26] <vorlon> not clear from the bug what the FFe is requesting
[20:27] <vorlon> is this about enabling glusterfs support in samba?
[20:28] <cpaelzer> vorlon: the IR is glusterfs and now that it is approved we'D want to enable it in samba + qemu
[20:29] <cpaelzer> vorlon: to pull it into main and (among other reasons) to provide the features people asked for that made us want to promote it
[20:29] <cpaelzer> we linked the samba/qemu bugs in the updates at the bottom, but didn't convert them to individual FFE bugs as the MIR bug has all the content and context already
[20:30] <vorlon> too much content and context ;)
[20:30] <vorlon> acked for samba
[20:30] <cpaelzer> what would you need for qemu to make a decision?
[20:31] <cpaelzer> vorlon: there is already an MR  and a PPA that shows the intended change - I think can provide what you need so just let me know
[20:32] <vorlon> cpaelzer: what is the runtime impact of building with glusterfs support?  Will it change any behavior of qemu with existing invocations, or does it require enabling an additional option?
[20:32] <vorlon> (at runtime)
[20:33] <cpaelzer> vorlon: sil asked that and I explained in comment 24
[20:33] <cpaelzer> TL;DR - you need to add an option otherwise it isn't even loading the .so file
[20:33] <vorlon> got it
[20:37] <cpaelzer> thank you!
[20:39] -queuebot:#ubuntu-release- New: accepted golang-github-iglou-eu-go-wildcard [sync] (jammy-proposed) [1.0.3-2]
[20:39] -queuebot:#ubuntu-release- New: accepted golang-github-mdlayher-dhcp6 [sync] (jammy-proposed) [0.0~git20190311.2a67805-2]
[20:41] -queuebot:#ubuntu-release- New binary: golang-github-iglou-eu-go-wildcard [amd64] (jammy-proposed/none) [1.0.3-2] (no packageset)
[20:41] -queuebot:#ubuntu-release- New binary: golang-github-mdlayher-dhcp6 [amd64] (jammy-proposed/none) [0.0~git20190311.2a67805-2] (no packageset)
[21:14] -queuebot:#ubuntu-release- Packageset: Removed nvidia-graphics-drivers-tesla-510 from i386-whitelist in jammy
[21:14] -queuebot:#ubuntu-release- Packageset: Removed python3.9 from i386-whitelist in jammy
[22:42] -queuebot:#ubuntu-release- New: accepted golang-github-iglou-eu-go-wildcard [amd64] (jammy-proposed) [1.0.3-2]
[22:42] -queuebot:#ubuntu-release- New: accepted golang-github-mdlayher-dhcp6 [amd64] (jammy-proposed) [0.0~git20190311.2a67805-2]
[22:46] -queuebot:#ubuntu-release- Unapproved: gnome-connections (jammy-proposed/universe) [42.1-1 => 42.1.1-1] (no packageset) (sync)
[22:47] -queuebot:#ubuntu-release- Unapproved: accepted gnome-connections [sync] (jammy-proposed) [42.1.1-1]
[23:28] -queuebot:#ubuntu-release- New binary: bettercap [amd64] (jammy-proposed/universe) [2.32.0-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: bettercap [s390x] (jammy-proposed/universe) [2.32.0-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: bettercap [ppc64el] (jammy-proposed/universe) [2.32.0-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New: accepted bettercap [amd64] (jammy-proposed) [2.32.0-1]
[23:29] -queuebot:#ubuntu-release- New: accepted bettercap [s390x] (jammy-proposed) [2.32.0-1]
[23:29] -queuebot:#ubuntu-release- New: accepted bettercap [ppc64el] (jammy-proposed) [2.32.0-1]
[23:32] -queuebot:#ubuntu-release- New binary: bettercap [arm64] (jammy-proposed/universe) [2.32.0-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: bettercap [armhf] (jammy-proposed/universe) [2.32.0-1] (no packageset)
[23:35] -queuebot:#ubuntu-release- Unapproved: libcanberra (jammy-proposed/main) [0.30-8ubuntu2 => 0.30-10ubuntu1] (i386-whitelist, ubuntu-desktop)


[07:57] <dholbach> good morning
[09:20] <geser> good morning
[09:25]  * sebner waves at geser :)
[09:28] <geser> Hi sebner, how are you? long time not seen you around
[09:30] <sebner> geser: I'm always around, just not writing. Hahaha, well I'm fine besides that I have my math exam in 1 hour ...
[09:32] <geser> sebner: good luck with your exam
[09:32] <sebner> geser: thanks :); I'll leave then. We can talk later :)
[09:59] <iulian> Morning geser.
[09:59] <iulian> Hey dholbach.
[09:59] <dholbach> hi iulian
[10:00] <geser> Hi iulian
[14:57] <ari-tczew> dholbach: do you maintain profil "Ubuntu developers/development" on facebook?
[14:57] <dholbach> yes
[16:48] <geser> hyperair: what's your opinion on syncing pdfmod from Debian experimental?
[16:51] <hyperair> geser: you mean it's not synced yet?
[16:51] <hyperair> geser: apologies, i must have overlooked it
[16:52] <geser> hyperair: natty has 0.8.3-1build2 and as a rebuild is needed for a transition, perhaps sync 0.9.0-1 at that chance
[16:54] <hyperair> geser: may i sync it now?
[16:54] <hyperair> geser: as in, syncpackage?
[16:54] <hyperair> geser: out of curiosity, what build-deps have changed?
[16:55] <geser> hyperair: sure, libpoppler-glib5 is NBS and pdfmod depends on it
[16:55] <hyperair> i see.
[16:55] <geser> just a library transition
[16:56] <hyperair> i see.
[16:56] <hyperair> geser: and a rebuild fixes it all?
[16:56] <hyperair> no sourceful changes?
[16:57] <geser> hyperair: depends, sometimes a rebuild is enough and sometimes not, but pdfmod 0.9.0 built in my natty pbuilder without problems
[16:57] <hyperair> ah, in that case it's fine, i guess
[16:58]  * hyperair test builds just in case
[16:58] <hyperair> just to see what new clilibs/shlibs have changed
[16:59] <geser> I'm just surprised that pdfmod 0.9.0 doesn't depend on libpoppler-glib6 at all which might be due to "ld --as-needed"
[16:59] <Laney> why syncpackage and not normal sync?
[17:00] <hyperair> no, that's unlikely
[17:00] <hyperair> Laney: because i'm a lazy and impatient bastard
[17:00] <Laney> they get done daily now
[17:00] <hyperair> Laney: then i'm just a lazy bastard.
[17:01] <hyperair> geser: yeah, see, that's what i was worried about, because pdfmod is a CLI app which doesn't use ld for linking
[17:01] <Laney> as you wish
[17:03] <hyperair> dh_clideps: Warning: Missing shlibs entry: libpoppler-glib.so.5 or poppler-glib for: poppler-sharp.dll! Resolved moduleref via DLL map: poppler-glib to: libpoppler-glib.so.5
[17:03] <hyperair> geser: ^^
[17:03] <hyperair> that's what happened.
[17:04] <geser> how to fix it?
[17:05] <hyperair> patch the .config file, i guess.
[17:05] <hyperair> poppler-sharp.dll.config
[17:05] <hyperair> no wait
[17:05] <hyperair> we need to fix poppler-sharp first
[17:05] <hyperair> and then rebuild pdfmod
[17:05] <hyperair> pdfmod should be syncable after
[17:09] <geser> ah, looks like the recent poppler-sharp rebuild (for that transition) broke it, as no dependency at all anymore
[17:10] <hyperair> heh
[17:10] <hyperair> lemme investigate
[17:10] <geser> looks like fabricesp forgot to update debian/poppler-sharp.dll.config in his rebuild attempt
[17:13] <geser> like it was it, uploading a fixed poppler-sharp
[17:13] <hyperair> geser: ...did you upload yet?
[17:13] <hyperair> geser: if you haven't, please stop.
[17:13] <geser> ok
[17:13] <hyperair> i'm in the middle of preparing an upload that autogenerates the SONAME
[17:13] <hyperair> so we can just do no-change reuploads in the future
[17:14] <geser> ok, I let you handle poppler-sharp and pdfmod
[17:14] <hyperair> thanks.
[17:16] <hyperair> now how do we get the soname...
[17:19] <geser> objdump -p /usr/lib/libpoppler-glib.so | grep SONAME
[17:23] <hyperair> !
[17:23] <hyperair> thanks
[20:08] <ari-tczew> cjwatson: would be nice to have your look on bug 711454
[20:13] <cjwatson> ari-tczew: yeah, I'm aware of the problem but am not sure how to solve it; probably needs consultation with the UDD folks since they have similar problems
[20:13] <cjwatson> I certainly can't do you a quick fix, sorry
[20:14] <ari-tczew> cjwatson: I understand.
[20:14] <cjwatson> it's also tied in with http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572204
[20:15] <cjwatson> my personal preference is to omit .pc files from all these kinds of things, but then you have the problem that if you want to actually operate on the quilt patches then you have to run a strange command to set up the .pc directory for yourself
[20:15] <cjwatson> it gets even more confusing if you have a wrong (unmerged) .pc directory
[20:16] <cjwatson> I know how to handle it for myself, but I don't yet have a firm grasp of what it might be sane to recommend that everyone use
[20:19] <ari-tczew> main merges are less than 100! and all less than 150
[20:22] <Rhonda> huhpmf
[20:23] <Rhonda> requestsync hasn
[20:23] <Rhonda> requestsync hasn't noticed yet that there is fillets-ng-data newer version in unstable yet  *pouts*
[20:23] <Rhonda> I uploaded it the same time as fillets-ng
[20:33] <geser> does rmadison know about it?
[20:40] <Rhonda> yep
[20:40] <Rhonda> uhm, no. what the
[20:41] <Rhonda> *slapsherself* … of course, it's stuck in NEW  %-/
[20:42]  * Rhonda . o O ( new dutch speech files )
[21:08] <Rhonda> Shall I set the fillets-ng sync request to new instead of confirmed for the time being?
[21:10] <Rhonda> bdrung or cjwatson, can you unsubscribe ubuntu-archive from bug #711473? I don't want it to be on your agenda as long as the -data package isn't through Debian NEW, otherwise an accidental sync would render the package unusable.
[21:12] <seidos> hi all.  i was just wondering, is it possible to install a package from maverick on a lucid system?  if so, how?
[21:15] <bdrung> Rhonda: you need to ask a ubuntu-archive member (https://launchpad.net/~ubuntu-archive/+members#active)
[21:16] <Rhonda> Oh, thought you are one, sorry.
[23:21] <cjwatson> Rhonda: I see somebody's done it


[12:49] <cjwatson> stgraber: Right.  It *looks* like it's auto-imported, but it would be good if you could check it over if you get a moment.
[16:45] <almostevery> hello, is this the ubuntu dev channel?
[16:55] <almostevery> hello, can anyone help please? I have a problem with 14.04. keyring program
[16:56] <kklimonda> almostevery: it's not really the best channel for asking support questions (especially on weekends), it's for discussing development of ubuntu itself.
[16:57] <kklimonda> almostevery: you'll have more luck on #ubuntu probably
[16:58] <almostevery> kklimonda, it is where I'm coming from, as it is beyond a support matter. and my question is precisely about a problem related to design-development of the keyring program on 14.04.
[17:00] <almostevery> I just started using 14.04., and saw that the new design of the keyring program doesn't 'forget' the keyring passwords. that is, across restarts of computer or re-insertions of hardware, it doesn't ask the password again, but instead it suffices to right-click on unlock to access the keyring.
[17:00] <almostevery> that is, it suffices to access desktop to access a keyring, if it is once decrypted via its respective password
[17:01] <almostevery> which wasnt the case in 12.04. I dont know 13.04. or 13.10. as I didnt use them
[17:02] <kklimonda> you may have more luck asking during the working week, right now most people aren't around
[17:02] <almostevery> well, maybe I have. let's see..
[17:02] <mdeslaur> almostevery: the keyring is automatically unlocked with your login password when you log in
[17:02] <mdeslaur> almostevery: that's how it always worked
[17:03] <almostevery> mdeslaur, yes, for the 'login' keyring it is true. but login keyring is not my only keyring, and until now it wasn't the case that all other keyrings were 'kept open' forever in the way I described above. this is the novel problem.
[17:04] <mdeslaur> almostevery: if you don't want it to use your login password to unlock automatically, you can change it in the Passwords and Keys tool by right-clicking the "Login" section and selecting "Change password"
[17:04] <mdeslaur> almostevery: are you using the same password for the other keyrings?
[17:06] <almostevery> mdeslaur, even there, it is not the same thing as before. it never was the case that accessing desktop released access to all keyrings that have been unlocked before.
[17:06] <mdeslaur> almostevery: I'm guessing people thought that was a bug that needed fixing :)
[17:07] <mdeslaur> almostevery: perhaps open a bug with the upstream gnome-keyring project?
[17:07] <almostevery> mdeslaur, yes. this was what I heard in the support channel
[17:08] <almostevery> mdeslaur, I have installed 14.04. only now, and promptly noticed this. hasn't this been reported as a problem until now?
[17:08] <mdeslaur> almostevery: nope
[17:08] <almostevery> since April?
[17:08] <mdeslaur> almostevery: most people are happy that the bug is finally fixed and it automatically unlocks all keyrings I guess
[17:11] <almostevery> mdeslaur, 'bug is finally fixed'? which bug was there?
[17:11] <mdeslaur> almostevery: please file a bug with "ubuntu-bug gnome-keyring", then file an upstream bug here: https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-keyring
[17:12] <mdeslaur> almostevery: people used to complain that the other keyrings wouldn't unlock automatically at login
[17:13] <almostevery> mdeslaur, and you call this a 'bug'?
[17:13] <almostevery> it is a feature.
[17:13] <mdeslaur> almostevery: that's why you should file a bug upstream, and explain your point of vue and see if they agree and will change t
[17:14] <mdeslaur> it
[17:14] <mdeslaur> s/vue/view/
[17:15] <mdeslaur> almostevery: oh, are the passwords for your other keyrings actually stored in the login keyring?
[17:16] <almostevery> the bug is what we have now. devices and keyrings auto-decrypting across restarts and reconnects..I should think ubuntu users -and by all means devs- know way better than offering a facebookization of the OS.
[17:17] <almostevery> mdeslaur, in the present 'transparent' state of the keyrings, I fear I cant answer such a question publicly, sorry.
[17:17] <mdeslaur> almostevery: well, if they are, then that's your problem, you didn't uncheck the "automatically unlock this keyring when I log in" option when you unlocked them
[17:17] <mdeslaur> so they got atored
[17:17] <mdeslaur> stored
[17:18] <mdeslaur> almostevery: if you click on the "Login" keyring and you have an entry called "Unlock password for:keyringname" then that's why
[17:19] <mdeslaur> right click on that and delete it
[17:20] <almostevery> mdeslaur, you mean I delete the login keyring?
[17:20] <almostevery> mdeslaur, sorry, I got it
[17:20] <almostevery> yes, I see such entries
[17:21] <mdeslaur> ok, so delete those entries, and then lock and unlock your other keyrings
[17:21] <mdeslaur> when it asks for your password, UNCHECK the box marked "Automatically unlock this keyring whenever I'm logged in"
[17:25] <almostevery> mdeslaur, I deleted them. now I will uncheck the box, and hope the keyrings wont be kept open afterwards. in the login keyring, I see also password used in a client application. if I deleted it, would I have to reenter the password each time I open the client?
[17:29] <mdeslaur> almostevery: depends how the application stores the password. Either it stores it unconditionally, or it has a checkbox that asks you whether or not it should be stored
[17:33] <almostevery> mdeslaur, I will just try it, then. thank you for your help, it seems to have solved the auto-access problem. thanks for the links to bug reporting, too. I would anyway consider contacting them to know more.
[17:36] <almostevery> and to get clear about it
[17:38] <almostevery> mdeslaur, have a good weekend!
[18:33] <hjd> The package haskell-data-lens-template is in the FTBFS list for Utopic (due to unmet dependencies). However, I was able to build it on an up to date utopic system without any problems, atleast on i386. Could someone please trigger a rebuild of this package? :)
[19:30] <rbasak> hjd: apt-get can't install libghc-data-lens-dev for me on utopic-proposed on amd64. Are you sure you have utopic-proposed enabled in your build environment?
[19:44]  * hjd checks
[19:49] <hjd> rbasak: No, I don't have -proposed enabled.
[20:01] <hjd> ...and I get the same unmet dependencies error after enabling -proposed. Nevermind then :)
[21:35] <cjwatson> rbasak: I recommend leaving it alone.  I'm on top of the Haskell transition, but there are a number of layers.
[21:35] <cjwatson> (hjd has left.)
[21:35] <cjwatson> It's always "fun" when people think they can parachute into the middle of that :-/
[21:35] <cjwatson> Well-meaning, but ...
[21:36]  * xnox irc disconnected again.....
[21:38]  * cjwatson uploads rebuilds of another layer of the above
[22:49] <rbasak> cjwatson: yeah, I assumed it wasn't as simple as that :)
[23:43] <Guest67794> Hello, I need help compiling a non-pae Kernel
[23:44] <Guest67794> I found out what to change in the .config flies, but the rules script keeps overwriting what I put in there
[23:59] <directhex> Guest12249, why do you need a non-pae kernel?


[17:46] <Scary_Guy> https://is2.4chan.org/g/1601020554826.png unfortunate
[17:51] <cmaloney> Oh God, that's naty
[17:51] <cmaloney> nasty
[18:04] <Scary_Guy> Actaully it might be the former too with all that standing water, though I suppose that would be "gnaty"
[22:52] <greg-g> lesson: always mount servers high on the rack
[22:53] <greg-g> management's takeaway ^. Nevermind fixing the rotten plumbing.


[00:20] <kwwii> so between the emails, the wiki and this nonsense everyone should check out the new information
[16:25] <sportman1280> hello.  i have a bug with an icon set and am trying to fix it.  The firefox 3 bookmark icon (the folder) is using the gnome default icon.  Not the icon set icon.  I dont believe it is being set right, but how do i go about setting the firefox bookmark icons?
[16:28] <andreasn> sportman1280: the organize-bookmarks icon?
[16:28] <andreasn> screenshot?
[16:28] <sportman1280> no the actual bookmark fold icons
[16:28] <sportman1280> sure one sec
[16:30] <sportman1280> http://savage.lcsee.wvu.edu/~jderemer/Screenshot.png
[16:30] <andreasn> did you try to restart the browser?
[16:30] <sportman1280> andreasn: notice how they are grey folders?
[16:31] <sportman1280> andreasn: yes.  If you notice the navigation icons are correct.
[16:31] <andreasn> well, yellow-brown rather I would say, but yet :)
[16:31] <andreasn> "but yes" I mean
[16:31] <sportman1280> they are supposed to be a blue folder...
[16:32] <sportman1280> im not sure which icon firefox 3 uses for that icon
[16:32] <andreasn> it's the stock gtk icon
[16:32] <sportman1280> ok. thanks
[16:33] <sportman1280> there is no gtk icon for the kamel icon set
[16:33] <sportman1280> so ill fix that :)
[16:35] <andreasn> the name it calls is gtk-directory
[16:35] <sportman1280> yep. i had found it
[16:35] <sportman1280> its already fix
[16:35] <sportman1280> ed
[16:35] <andreasn> should work with just a symlink to folder
[16:35] <sportman1280> thanks a lot :-D
[16:35] <andreasn> does it work now?
[16:35] <sportman1280> yes
[16:36] <andreasn> sweet
[16:36] <andreasn> np
[16:36] <sportman1280> just created a icon called gtk-directory
[16:36] <sportman1280> theres a lot of directory and folder icons, so i wasnt sure which one.... hah
[20:30] <G-H-Robson> hi


[11:02] <mjjm> Hello
[11:03] <mjjm> i need some help.
[11:03] <cfhowlett> !ask
[11:03] <mjjm> i m french.
[11:03] <cfhowlett> !fr
[11:05] <mjjm> yes.  I can write some words.
[11:08] <mjjm> I would like to submit my ubuntu studio correctly.
[11:08] <cfhowlett> "submit" ?? makes no sense.  ask #ubuntu-fr
[11:11] <mjjm> no  submit but i would like return my ubuntu studio without
[11:11] <cfhowlett> still makes no sense.  google translate is not your friend.  ask the french language channel.
[11:15] <mjjm> I wrote one question but i did not answer.
[11:15] <cfhowlett> wordscramble english.  see #ubuntu-fr
[11:16] <mjjm> Not today but I don't when...
[11:17] <mjjm> I 'm go...
[11:17] <mjjm> I'm going...
[11:18] <mjjm> goodbye.