 How are you?
[07:15] <swift110-phone__> Im good lordievader. What are you up to
[07:17] <lordievader> Work, as usual
[10:29] <pragomer> hi. I am very excited about konsole's new "split feature" (like tmux), that came with 5.16. Unfortunately I am on 5.12 on kubuntu lts. Is there a way to get just this feature in kubuntu 18.04 ?
[10:34] <RikMills> pragomer: build konsole from source
[10:34] <RikMills> I have daily builds of konsole git master going on in here: https://launchpad.net/~rikmills/+archive/ubuntu/experimental
[10:35] <pragomer> what would be cool is an appimage :-)
[10:35] <RikMills> but that ppa is (a) completly unsupported and (b) no translations in those builds
[10:37] <pragomer> yes, I see.   But thank you in any case for the link/ppa. I going at least to try this in a vm
[10:38] <RikMills> no appimage that I know of. nor even a snap :/
[11:11] <BluesKaj> Hi folks
[13:25] <jubo2> I want to turn on the AES-256 hardware encryption for a SSD on a fresh install of Kubuntu on a 50GB /-partition and 200GB free and a /home-partition of 710GB. There were instructions for Arch Linux somewhere.
[13:26] <jubo2> and then setup backuping the system over LAN to home machine which is going to be on a 2TB disk. this latter I need suggestions on how to do safely, efficiently and reliably regarding if ever needing to recover from backup
[13:28] <jubo2> the best I have thought would be SSHFS authenticated by keys + Timeshift which is a rsync-based solution for all Linuxen
[15:18] <salsa4life> jubo2: thanks for the info
[15:27] <IrcsomeBot1> Brian Binh was added by: Brian Binh
[15:27] <IrcsomeBot1> <Brian Binh> (Photo, 200x200) https://irc-attachments.kde.org/Y0Y98r33/file_17408.jpg
[15:27] <IrcsomeBot1> <Brian Binh> ecsabniiuzo tp
 @Brian Binh, Spammer bitch
[17:42] <IrcsomeBot1> James Burkhardt was added by: James Burkhardt
[17:42] <IrcsomeBot1> <James Burkhardt> (Photo, 200x200) https://irc-attachments.kde.org/OvHCVR0H/file_17412.jpg
[17:42] <IrcsomeBot1> <James Burkhardt> joturijnxt
[19:03] <thomas_> Hallo, I looking for mongo find by _id, my _id is a string but Mongo need a BSON object. Did someone find a solution in nodered?
[19:06] <thomas_> When I require('mongodb') in settings.js - and use this in a function - then the function dont find global.get('mongoModule').ObjectID;
[19:06] <thomas_> In Node its no problem:
[19:07] <thomas_> var mongo = require('mongodb');
[19:07] <thomas_> > var o_id = new mongo.ObjectID("5d5ea977883f7c510f10a669");
[19:07] <thomas_> > console.log(o_id)
[19:07] <thomas_> sorry wrong chanel
[19:45] <npl> Hi all, just started using Kubuntu, problem is that it's not seeing my ultrawide monitor (2560x1080). I'm a bit of a noob when it comes to the command line and I'm having no luck with the online solutions. Any help would be really appreciated. Many thanks.
[20:04] <mavr1k> quiet
[20:05] <npl>  Hi all, just started using #Kubuntu, problem is that it's not seeing my ultrawide monitor (2560x1080). I'm a bit of a noob when it comes to the command line and I'm having no luck with the online solutions. Any help would be really appreciated. Many thanks.
[20:34] <cole> i have two laptops with ddr2 ram cards in both however, one pc is i think 4gb per ram and other laptop is only 2gb total capable. can I use just one ram card from bigger ram cards????like 1 ram card with 2gb instead of the 2 thats in it thats running a total og 1gb. can anyone care to help???????
[20:37] <cole> Im sorry if im in the wrong place to ask my question. if someone knows where i might get help with it. i would be very thankful
[21:09] <Guest77508> asad
[21:10] <Guest77508> hello
[21:12] <Guest77508> hello
[22:12] <swift110> sup
[22:45] <swift110> hey all


[05:58] <rick_h> skay:  "values in the services file"?
[09:28] <nvalerkos> hi
[09:28] <stickupkid> nvalerkos, hi
[09:28] <nvalerkos> I've deployed a controller for kubernetes charm
[09:28] <nvalerkos> i got a problem which seem a bit odd
[09:30] <nvalerkos> Stopped services: kube-proxy
[09:30] <nvalerkos> status of the kubernetes master is blocked
[09:30] <nvalerkos> I am using LXC on a single machine, localhosdt
[09:31] <nvalerkos> I am not sure why this is happening because I just deployed a charm which should work without any problems
[09:32] <stickupkid> nvalerkos, can you pastebin a juju status here
[09:33] <nvalerkos> App                    Version  Status   Scale  Charm                  Store       Rev  OS      Notescontainerd                      active       5  containerd             jujucharms   54  ubuntu  easyrsa                3.0.1    active       1  easyrsa                jujucharms  296  ubuntu  etcd                   3.3.15   active       3  etcd
[09:33] <nvalerkos> jujucharms  488  ubuntu  flannel                0.11.0   active       5  flannel                jujucharms  468  ubuntu  kubeapi-load-balancer  1.14.0   active       1  kubeapi-load-balancer  jujucharms  704  ubuntu  exposedkubernetes-master      1.17.2   blocked      2  kubernetes-master      jujucharms  792  ubuntu  kubernetes-worker      1.17.2
[09:33] <nvalerkos> active       3  kubernetes-worker      jujucharms  634  ubuntu  exposedUnit                      Workload  Agent  Machine  Public address  Ports           Messageeasyrsa/0*                active    idle   1        <IP_ADDRESS>                      Certificate Authority connected.etcd/0                    active    idle   3        <IP_ADDRESS>
[09:33] <nvalerkos> 2379/tcp        Healthy with 3 known peersetcd/1*                   active    idle   0        <IP_ADDRESS>    2379/tcp        Healthy with 3 known peersetcd/2                    active    idle   5        <IP_ADDRESS>     2379/tcp        Healthy with 3 known peerskubeapi-load-balancer/0*  active    idle   7        <IP_ADDRESS>     443/tcp
[09:33] <nvalerkos> Loadbalancer ready.kubernetes-master/0       waiting   idle   9        <IP_ADDRESS>     6443/tcp        Waiting for 6 kube-system pods to start  containerd/4            active    idle            <IP_ADDRESS>                     Container runtime available  flannel/4               active    idle            <IP_ADDRESS>                     Flannel
[09:33] <nvalerkos> subnet <IP_ADDRESS>/24kubernetes-master/1*      blocked   idle   2        <IP_ADDRESS>    6443/tcp        Stopped services: kube-proxy  containerd/3            active    idle            <IP_ADDRESS>                    Container runtime available  flannel/3               active    idle            <IP_ADDRESS>                    Flannel subnet
[09:33] <nvalerkos> <IP_ADDRESS>/24kubernetes-worker/0       active    idle   8        <IP_ADDRESS>     80/tcp,443/tcp  Kubernetes worker running.  containerd/1            active    idle            <IP_ADDRESS>                     Container runtime available  flannel/1               active    idle            <IP_ADDRESS>                     Flannel subnet
[09:33] <nvalerkos> <IP_ADDRESS>/24kubernetes-worker/1       active    idle   6        <IP_ADDRESS>    80/tcp,443/tcp  Kubernetes worker running.  containerd/2            active    idle            <IP_ADDRESS>                    Container runtime available  flannel/2               active    idle            <IP_ADDRESS>                    Flannel subnet
[09:33] <nvalerkos> <IP_ADDRESS>/24kubernetes-worker/2*      active    idle   4        <IP_ADDRESS>     80/tcp,443/tcp  Kubernetes worker running.  containerd/0*           active    idle            <IP_ADDRESS>                     Container runtime available  flannel/0*              active    idle            <IP_ADDRESS>                     Flannel subnet
[09:33] <nvalerkos> <IP_ADDRESS>/24Machine  State    DNS           Inst id        Series  AZ  Message0        started  <IP_ADDRESS>  juju-0a24b5-0  bionic      Running1        started  <IP_ADDRESS>    juju-0a24b5-1  bionic      Running2        started  <IP_ADDRESS>  juju-0a24b5-2  bionic      Running3        started  <IP_ADDRESS>  juju-0a24b5-3  bionic      Running4
[09:33] <nvalerkos> started  <IP_ADDRESS>   juju-0a24b5-4  bionic      Running5        started  <IP_ADDRESS>   juju-0a24b5-5  bionic      Running6        started  <IP_ADDRESS>  juju-0a24b5-6  bionic      Running7        started  <IP_ADDRESS>   juju-0a24b5-7  bionic      Running8        started  <IP_ADDRESS>   juju-0a24b5-8  bionic      Running9        started  <IP_ADDRESS>
[09:33] <nvalerkos> juju-0a24b5-9  bionic      Running
[09:33] <stickupkid> nvalerkos, to here https://pastebin.canonical.com/
[09:33] <stickupkid> :)
[09:33] <nvalerkos> https://pasteboard.co/IRhbIoA.png
[09:34] <nvalerkos> I dont have access to that one
[09:34] <stickupkid> nvalerkos, it seems like there is an issue with kube-proxy which is blocking the kube-master
[09:35] <stickupkid> nvalerkos, I'm not sure why that would be
[09:35] <stickupkid> nvalerkos, it might be worth asking here https://discourse.jujucharms.com/
[09:42] <manadart> stickupkid nvalerkos: pastebin.canonical.com is internal pastebin.ubuntu.com is public.
[09:42] <stickupkid> d'ho
[09:46] <nammn_de> rick_h:  morning, with provider are the clouds meant, right? (Maas, aws ..)
[09:46] <nvalerkos> localhost
[09:46] <nvalerkos> Warning  FailedCreatePodSandBox  3m48s (x125 over 31m)  kubelet, juju-0a24b5-6  (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container: failed to create containerd task: failed to mount rootfs component &{overlay overlay
[09:46] <nvalerkos> [workdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/1745/work upperdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/1745/fs lowerdir=/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/1/fs]}: invalid argument: unknown
[09:47] <nvalerkos> All pods are stuck at containercreating
[09:47] <nvalerkos> something to do with the storage volume
[09:47] <nvalerkos> I am using lxd with zfs
[10:45] <stickupkid> manadart, achilleasa CR please https://github.com/juju/juju/pull/11140
[11:25] <manadart> stickupkid: Yep.
[13:12] <rick_h> nammn_de:  right, I'm hinting there's a cloud-based specific trick to that PR
[13:12] <nammn_de> rick_h: ahh, yes I was planning to write code where specific cloud providers support renaming (aws does, maas does not)
[13:12] <nammn_de> something along the line
[13:13] <rick_h> nammn_de:  ok cool just tossing a hint your way since I didn't see anything in the PR around that
[13:13] <nammn_de> rick_h: yeah thanks!
[13:13] <nammn_de> better safe than sorry =D
[13:14] <nammn_de> my pr is still in the early phase, just out for people to give fundamental hints. Like you did.  Still constantly updated
[13:14] <rick_h> nammn_de:  understand
[13:14] <nammn_de> rick_h: i answered your concerns in my old pr (show-space).  As well here in chat, late though. Does that answer your concers?
[13:14] <nammn_de> concerns
[13:15] <rick_h> nammn_de:  I think so, I'm just trying to find time to play with it myself then
[13:42] <skay> rick_h: services file == yaml file that mojo uses. anyway, I figured out the problem. The yaml was not correct. all good. The magic thing happened where I found the error right after asking for help
[14:03] <rick_h> skay:  ah ok awesome
[14:51] <manadart> Patch for systemd file relocation: https://github.com/juju/juju/pull/11147
[14:51] <stickupkid> manadart, I'll give it look now
[14:54] <manadart> stickupkid: Thanks.
[14:54] <stickupkid> manadart, i'm assuming that this needs regression testing
[14:56] <manadart> stickupkid: I tested on Focal and Bionic. I assume that covers back to Xenial as well.
[14:56] <stickupkid> manadart, yeah, what's supported under ESM
[14:57] <stickupkid> manadart, answering my own questions - 14.04 is still in esm, but that's not systemd right, that's upstart?
[14:57] <stickupkid> manadart, so we need to test xenial onwards?
[14:57] <manadart> manadart: Series upgrades definitely now need rework. I will follow with a patch for that. At the same time I will test/fix the old upgrade steps.
[14:58] <manadart> stickupkid: Trusty is Upstart IIRC.
[14:58] <stickupkid> yeah, thought as much
[14:59] <stickupkid> manadart, so upgrading series will now need to move files right?
[15:04] <manadart> stickupkid: Actually thinking about it, upgrading from Trusty should work out of the box (I will test it). Aside from that, we handle in a Juju upgrade step.
[15:04] <manadart> I think. Testing to follow.
[15:05] <manadart> Series upgrade leaves the files alone if the upgrade is systemd -> systemd.
[15:06] <stickupkid> but that's not what we want if a restart happens though right?
[15:09] <manadart> It should be OK. If you do a series upgrade with Juju < 2.7.2, you will not be able to go up to Focal.
[15:09] <stickupkid> interesting
[15:09] <manadart> So you upgrade Juju, then do it.
[15:09] <manadart> If you are > Trusty and you upgrade Juju, it just needs to relocate the files.
[15:10] <stickupkid> > sudo: setrlimit(RLIMIT_CORE): Operation not permitted
[15:11] <manadart> stickupkid: That is a symptom of sudo on Focal (at least on LXD). it doesn't come from Juju.
[15:11] <stickupkid> yeah, really didn't like that
[15:11] <manadart> stickupkid: You can test it on the container directly - just sudo something.
[15:12] <stickupkid> anyway, it finished :D
[15:22] <stickupkid> manadart, done
[15:23] <nammn_de> achilleasa manadart: is there an easy way to bootstrap an controller on aws with --config juju-ha-space=<any space> ? I thought alpha should work. But it fails for me
[15:29] <manadart> nammn_de: I think there might be chicken/egg thing there with AWS, because you are trying to land a controller on a space that doesn't come from the provider. Juju hasn't loaded the subnets and created the space yet, so it can't satisfy.
[15:29] <nammn_de> manadart: hmmm makes sense. Just wanted to set the config setting so that i can test the rename-code
[15:29] <manadart> nammn_de: Try the other config value (juju-mgmt-space).
[15:29] <nammn_de> I could, maybe, just add a key-value to the collection :D?
[15:30] <nammn_de> manadart: same error
[15:30] <manadart> nammn_de: OK, both should work if you set it post bootstrap with `juju controller-config juju-ha-space=alpha`
[15:31] <nammn_de> manadart: oh yes, hmm tried before. now works after trying again.. weird. Thanks!
[16:32] <nammn_de> manadart: regarding your comment
[16:32] <nammn_de> didnt we discuss last time that we cannot remove them and need to add them as empty https://github.com/juju/juju/pull/11088#discussion_r370208805
[16:32] <nammn_de> because we need to fulfill the interface?
[16:44] <manadart> Wrap network backing stub in a new type for the old facade tests and put them on that.
[16:45] <manadart> The old facade tests will be strangled out in favour of the new mock suite and they will ultimately disappeared. Those methods have nothing to do with the common backing.
[16:50] <achilleasa> hml: can you take a look at https://github.com/juju/description/pull/72 ?
[16:50] <hml> achilleasa:  looking
[16:52] <nammn_de> manadart: not sure if I can follow 100% do you have an example for me?
[17:00] <nammn_de> because afaict the  spaces.NewAPIWithBacking(...) takes a backing interface.  That's why it initially used those implements. But Actually there is no networkbacking usage in that test anymore
[17:10] <hml> achilleasa:  approved
[17:10] <achilleasa> hml: tyvm


[00:04] <pleia2> sent off to summary writers
[03:21] <ahoneybun> I have crappie internet where I am atm
[03:22] <ahoneybun> So I'll see if I can get some done at a public WiFi somewhere


[15:30] <Myrtti> erUSUL: is it like the first day of school after christmas in spain today or something?
[15:30] <erUSUL> Myrtti: no; that i know of ;)
[15:32] <Myrtti> if there'd be an ip range for Spain... *ahem*
[15:32] <erUSUL> guadalinex users again
[15:32] <Myrtti> so I figured
[15:33] <erUSUL> once aoppn a time LjL Pricey has a setup to catch them in a sanbox channel
[15:34] <Myrtti> what a nice idea. I wonder why it was abandoned.
[15:34] <erUSUL> once apon a time LjL Pricey had a setup to catch them in a sanbox channel
[15:35] <Myrtti> *sigh* yet another...
[15:35] <Pici> erUSUL: upon ;)
[15:35] <erUSUL> Myrtti: well LjL and Pricey are not longer op or irc council members
[15:35] <erUSUL> Pici: bah! ;) sloppy fingers today
[15:36] <erUSUL> Myrtti: also the banforward was for telefonica ip's seems like maybe the guadalinex centers changed isp now they are ono ip's ??
[15:36] <erUSUL> Myrtti: dunno; should be investigated if the ops feel the need
[15:37] <Myrtti> I don't know about the others but I feel rather murderous
[15:37] <erUSUL> back in the day even guadalinex devs where asked (or so i heard) to change the default channel for the irc clients in the distro
[15:37] <Pici> Perhaps a realname ban on 'Usuario estandar de guadalinex' would be prudent
[15:40] <Myrtti> something would be nice
[15:41] <Myrtti> something else than me wanting to poke them with a compass
[15:43] <Myrtti> perhaps the request should be renewed too
[16:18] <erUSUL> o.0!!!! *what* *the* *fuck* some of them are 10 years old ... what are their parents/teachers thinking ?
[16:19] <erUSUL> they give them laptops whitouth the minimum info on what to do and more important what *not* to do with it
[16:27] <m4v> I'm missing something? :P
[16:31] <jpds> ...
[16:32] <Pici> erUSUL: er. may want to mind the language here too.
[16:36] <m4v> erUSUL: ooh, you were talking about estelita?
[16:38] <erUSUL> and a few others that entered the channel today, new laptops today for all of them ;)
[16:40] <m4v> why didn't my school gave me one? ;_;
[16:41] <m4v> probably I didn't pass english grammar
[16:42] <erUSUL> ^_^
[17:01] <Myrtti> erUSUL: how did you find that out?
[17:02] <erUSUL> private chat; could have lied of course. but i know laptops are being given out to primary school here in spain so it may be true
[19:53] <Pici> jpds: ping.  I have a little project that I think you may be able to help with :)
[19:59] <jpds> Pici: PM whenever you want.
[21:46] <ubot2> In #ubuntu-br, Pretto said: !synaptic is É o gerenciador de pacotes oficial do Ubuntu.
[21:47] <ubot2> In #ubuntu-br, LuizAquino said: !synaptic is É o gerenciador de pacotes oficial do Ubuntu.


[00:01] <pchosi> right. finally testing out oneiric in a real install
[00:03] <pchosi> hm, the gtk3 theme really is *very* basic (and partially really bad)
[00:04]  * pchosi slaps ochosi for not trying harder yet
[02:34] <charlie-tca> 64bit Xubuntu Desktop image refuses to start the installer
[02:34] <dtchen> fun.
[02:34] <charlie-tca> first image in a week
[02:35] <charlie-tca> I will tackle it tomorrow, too late tonight
[02:35] <dtchen> yeah, I need to head offline myself
[02:35] <charlie-tca> Glad to see you once in a while again
[02:36] <dtchen> ditto
[02:36] <Unit193> Without being rude, who was he?
[02:39] <charlie-tca> dtchen - a long time ago was the audio trouble-shooter for Ubuntu
[02:40] <charlie-tca> Probably one of the best people in open source on audio stuff
[02:41] <Unit193> Wow... Didn't know that! Any idea why he hangs around here (Not that I care, I'm just wondering!)
[02:41] <charlie-tca> also was a kernel developer for a few years, I think.
[02:41] <charlie-tca> He likes us
[02:41]  * charlie-tca shrugs
[02:41] <micahg> nice guy :)
[02:41] <charlie-tca> I don't really know, but I like having him around
[02:42] <charlie-tca> Xubuntu i386 desktop images also fail to start the installer
[02:45] <charlie-tca> micahg: you aware we are very oversize again?
[02:46] <charlie-tca> (includes all images, alternate and desktop)
[02:50] <charlie-tca> well, I got to go get some sleep/rest tonight. See all you good people tomorrow!
[02:50] <charlie-tca> save
[03:03]  * micahg saw the size...
[05:28] <astraljava> Yeah, Dan (dtchen) is one of the fellows who are helpful wherever they appear. :)
[05:48]  * Unit193 will learn to hide in the corner when important people show up
[06:21] <astraljava> Unit193: Haha! No, that's not how it goes. You get vocal, ask questions etc. That's how the wisdom is passed on. :)
[06:36] <astraljava> Hmm, did anyone else test alternate installs? I'm puzzled, because on the test spreadsheet, there's an entry that says "does not allow entry of password or selection of session"
[06:36] <astraljava> It works for me, though.
[06:39] <Unit193> My sister was doing a lot of college stuff and I couldn't really do it
[06:41] <astraljava> Sure no prob, just wanted some confirmation. But I marked my results in the sheet, I'll ask charlie when he comes in.
[14:13] <charlie-tca> Good morning
[15:13] <micahg> hi charlie-tca
[15:13] <micahg> I saw the oversizedness, will try to look at it next week
[15:20] <charlie-tca> It probably won't matter, we still have no usable destkop session
[15:20] <charlie-tca> s/destkop/desktop
[15:22] <micahg> right, until the option to override the lightdm config at install time happens
[15:24] <charlie-tca> yes, and we have about 4 more bugs on hold for that
[15:26] <charlie-tca> I am pushing that in the release team meeting, too
[22:12] <beardygnome> test
[22:15] <charlie-tca> test here too?
[22:32] <astraljava> I will test tomorrow, way too exhausted now. :D
[22:32] <astraljava> Well, actually today, as it's way past midnight already.
[22:34] <charlie-tca> Thanks for testing yesterday/early today
[22:34] <charlie-tca> I am glad you got it to work
[22:48] <astraljava> charlie-tca: Yeah, wondered what that was all about. So you couldn't log in at all using the alternate?
[22:48] <charlie-tca> nope, I got locked into a lightdm loop
[22:48] <astraljava> charlie-tca: I just hit Other..., presented my username, chose session Xubuntu, typed my password, and in I went.
[22:48] <charlie-tca> everytime I click on my user name, it looped
[22:48] <astraljava> Nasty.
[22:48] <astraljava> Ahh...
[22:48] <charlie-tca> I didn't try Other, just my user
[22:49] <astraljava> Yeah, that won't work.
[22:49] <micahg> charlie-tca: probably bug 809890
[22:49] <charlie-tca> yup
[22:49] <charlie-tca> Fortunately, it doesn't affect this system
[22:52] <charlie-tca> Let's get our applications together for sponsorship to Orlando for UDS!
[22:52] <charlie-tca> http://www.jonobacon.org/2011/07/15/ubuntu-developer-summit-sponsorship-now-open-2/
[22:53]  * micahg hopes to see you all there
[22:53] <dtchen> likely won't be there but deployed again
[22:54] <charlie-tca> Oh, man
[22:54]  * Unit193 also won't be there
[22:54] <charlie-tca> Well, work comes first
[22:54]  * micahg wishes dtchen well
[22:55]  * charlie-tca will apply, and be thinking of dtchen
[22:55] <astraljava> I'd love to be there, but I doubt I get sponsoring anywhere.
[22:56] <charlie-tca> you are an important tester, also a big part of UbuntuStudio. You have a good chance if you apply
[23:04] <astraljava> Well if you and Scott could praise me to death, then maybe. :D
[23:05] <dtchen> I'm happy to toss in my rec.
[23:06] <Unit193> astraljava: I'm sure you could make it with UbuntuStudio AND Xubuntu :)
[23:07] <dtchen> also, if you haven't been before, that's a point step
[23:07] <Unit193> I would think it would be mostly for devs anyway...
[23:08] <astraljava> Dan, seriously? Cool! Thanks a bunch!
[23:08] <astraljava> No, I never went before.
[23:09] <dtchen> Unit193: it's a development-focused (daytime, at least :-) conference, but it isn't mostly for developers. There's a healthy contingent of non-developers from the wider Ubuntu community represented.
[23:12] <Unit193> Thank you. I know someone that has gone as a non-dev, but I thought it was mostly, guess I'm wrong again :)
[23:16] <micahg> Unit193: it's for requirements gathering, the devs come to moderate some of the discussion, but non-dev input is welcome and desired
[23:20] <charlie-tca> um, I am not a developer...
[23:20] <charlie-tca> I am not a coder or packager, either
[23:20] <micahg> charlie-tca: you're a project lead :)
[23:21] <charlie-tca> Well, there is that
[23:21] <charlie-tca> But I have gone twice as qa, instead
[23:21] <micahg> k, that's important input too
[23:21] <micahg> it's all important
[23:22] <charlie-tca> I agree. You have to blow your own horn in Ubuntu to be noticed and get things done
[23:22] <Unit193> Don't you also do accessability?
[23:23] <charlie-tca> well, yeah
[23:23] <charlie-tca> I guess I do
[23:23] <charlie-tca> I forget about a lot of stuff, sometimes
[23:25] <Unit193> There is also the age factor :P
[23:27] <charlie-tca> hm, forgot that too, huh?
[23:29] <Unit193> *I wouldn't get a sponsor because of it
[23:29] <dtchen> you'd have to be younger than 17.
[23:29] <Unit193> Well, I'll be 18 by the time the images are fixed...
[23:30] <micahg> right, sense was sponsored last year to orlando
[23:32] <micahg> mr_pouit: I'll take the xfce4-indicator-plugin merge unless you want to do it
[23:33] <micahg> mr_pouit: I can also take the libdesktop-agnostic merge


[04:04] <pitti> Good morning
[07:03] <sil2100> thomi: ping
[07:17] <popey> hmm. how do you manually attach a /var/crash/..crash report to a bug?
[07:17] <RAOF> Attach it as a file?
[07:17] <pitti> you don't
[07:17] <pitti> please, don't
[07:17] <popey> I have unpacked it, so have a bunch of files which may or may not be useful to the bug report?
[07:18] <popey> oh.
[07:18] <popey> is there nothing useful in there?
[07:18] <pitti> at least not the core dump
[07:18] <popey> there's no core dump
[07:18] <popey> and my bug is private
[07:18] <pitti> there might be some logs etc. which may be useful, but attaching a raw coredump into a bug makes things really hard for a triager
[07:18] <pitti> popey: oh, python crash?
[07:18] <popey> http://paste.ubuntu.com/5666792/
[07:18] <popey> rhythmbox
[07:18] <popey> thats all that it contains
[07:19] <popey> i woke to find it crashed and a dialog on my screen saying "Sorry the program 'Rhythmbox' closed unexpectedly
[07:19] <popey> Your computer does not have enough free memory to automatically analyse the problem and send a report to the developers"
[07:19] <pitti> ah, then it's useless anyway, as the core dump is too big and thus wasn't saved
[07:19] <pitti> but I get that crash, too
[07:19] <pitti> everytime a song ends, RB crashes in saucy
[07:19] <pitti> (if it's that crash)
[07:20] <popey> no, this is if it's left not playing overnight
[07:22] <popey> should I leave rb running overnight via gdb then get a backtrace the next day? Might be more useful?
[07:22] <seb128> good morning desktopers
[07:24] <didrocks> salut seb128!
[07:24] <seb128> lut didrocks ;-)
[07:25] <pitti> bonjour seb128, ça va ?
[07:26] <seb128> pitti, salut, oui, très bien (en dehors de la pluie), et toi ?
[07:26] <pitti> seb128: ça va bien ! (et encore soleil ici :) )
[07:27] <didrocks> pitti: fais attention, seb128 va t'envoyer de la pluie
[07:27] <didrocks> c'est ce qu'il s'est passé ici :(
[07:27] <didrocks> méchant seb128 :p
[07:28] <seb128> roooh
[07:36] <jibel> good morning
[07:38] <didrocks> hey jibel!
[07:40] <didrocks> seb128: FYI, I'm uploading that change: http://bazaar.launchpad.net/~webapps/webapps-applications/trunk/revision/534, it's going to be in binNEW
[07:41] <didrocks> seb128: the goal was to add a -dev package where every webapps script will depend upon (it's using a linter script with gjs which is in universe and the scripts are in universe)
[07:41] <jibel> salut didrocks
[07:41] <didrocks> so we can keep -common binary in main
[07:41] <didrocks> and have this new -dev binary in universe
[07:41] <seb128> didrocks, ok, makes sense
[07:42] <didrocks> seb128: just a preventive ping if you can review as I want to be able to run the webapps stack quickly then to get that sorted out :)
[07:42] <didrocks> seb128: thanks!
[07:42] <seb128> didrocks, will do
[07:42] <seb128> yw
[08:08] <Laney> morning!
[08:09] <seb128> Laney, hey, how are you?
[08:09] <Laney> strangely tired, but fine thanks
[08:09] <Laney> you?
[08:09] <seb128> I'm good thanks
[08:11] <seb128> shrug, I forgot about that
[08:11] <seb128> with the new glib, unity-panel-service segfault every time you close a win...
[08:12] <seb128> cyphermox_, ^ we need that libdbusmenu fix from charles merged and uploaded
[08:12] <seb128> didrocks, ^ for info
[08:12] <seb128> going to be fun for saucy users until it is :/
[08:13] <Laney> hmm, i don't see that
[08:14] <Laney> but anyway if it's that important then we can just upload it
[08:14] <seb128> Laney, it's not the end of the world, the service respawn, you just see the menubar be relocated to the app for a second and then be masked again
[08:14] <seb128> then you get apport to nag you
[08:15] <didrocks> seb128: we can just run libdbusmenu. If the indicator guys didn't want us to disable daily release because they are going to break trunk :/
[08:15]  * Laney is in the middle of being spammed by apport
[08:15] <Laney> arghghgh
[08:15] <seb128> new glib seems to also make tb unhappy
[08:15] <seb128> chrisccoulson, ^ did you notice?
[08:15] <chrisccoulson> seb128, i haven't upgraded yet
[08:15] <chrisccoulson> unhappy in what way?
[08:17] <seb128> chrisccoulson, http://paste.ubuntu.com/5666939/
[08:17] <didrocks> seb128: https://launchpad.net/ubuntu/saucy/+queue please ;)
[08:18] <chrisccoulson> seb128, g_menu_item_set_detailed_action ?
[08:18] <chrisccoulson> what code is calling this?
[08:18] <seb128> chrisccoulson, seems to come from libmessaging-menu
[08:19] <chrisccoulson> ah
[08:19] <seb128> so maybe a messaging menu issue
[08:20] <seb128> f***
[08:21] <seb128> chrisccoulson, tb lost my config/account :-(
[08:21] <seb128> when I start it now it gives me the "welcome to tb, do you want a new email"
[08:22] <seb128> didrocks, NEWed
[08:23] <didrocks> seb128: thanks!
[08:23] <seb128> didrocks, re: libdbusmenu, let's wait for cyphermox_, he put the merge on hold because there was a debug printf left in the MR
[08:23] <didrocks> right
[08:24] <chrisccoulson> seb128, what's in ~/.thunderbird and ~/.thunderbird/profiles.ini ?
[08:24] <seb128> $ ls ~/.thunderbird/
[08:24] <seb128> appreg            Crash Reports                  profiles.ini
[08:24] <seb128> baistreq.default<EMAIL_ADDRESS>[08:25] <seb128> $ profiles.ini
[08:25] <seb128> [General]
[08:25] <seb128> StartWithLastProfile=1
[08:25] <seb128> [Profile0]
[08:25] <seb128> Name=default
[08:25] <seb128> IsRelative=1
[08:25] <seb128> Path=baistreq.default
[08:28] <Laney> I keep getting facebook "Success" pages opening in my browser
[08:28]  * Laney suspects UOA
[08:28] <seb128> that again?
[08:28] <Laney> again?
[08:28] <seb128> we had that last cycle at some point
[08:32] <Laney> seb128: can you reproduce it?
[08:32] <Laney> go to add a facebook account in UOA
[08:33] <seb128> I've on configured
[08:33] <Laney> yeah, just try to add a new one
[08:33] <Laney> happens the same for me anyway
[08:35] <seb128> Laney, can you ping mardy on #ubuntu-devel about it?
[08:35] <Laney> oui
[08:35] <seb128> 'ci
[08:35] <seb128> Laney, but yeah, it opens in firefox rather than embedded for me as well
[08:36] <seb128> Laney, I suspect fb server side changes
[08:37] <Laney> yeah, found this https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1132030
[08:37] <ubot2> Launchpad bug 1132030 in gnome-control-center-signon (Ubuntu) "Facebook account setup opens in external browser, unusable" [Undecided,Fix released]
[08:38] <seb128> Laney, that was the one from last time
[08:38] <Laney> yup
[09:19] <seb128> Laney, didrocks, chrisccoulson: just for info:
[09:19] <seb128> https://bugs.launchpad.net/indicator-messages/+bug/1180302
[09:19] <ubot2> Launchpad bug 1180302 in indicator-messages (Ubuntu) "hit SIGTRAP errors after glib 2.37 update" [High,New]
[09:20] <seb128> desrt_, larsu_: ^ hey, please have a look if you can, tb fails to start in saucy, issue with new glib/libmessaging-menu
[09:20] <seb128> well "fails to start", it hit that when I receive new messages, but it might be config dependant
[09:20] <seb128> desrt_, larsu_: it hits that error:
[09:20] <seb128> g_menu_item_set_detailed_action: Detailed action name 'mailbox:///home/user/.thunderbird/idprofile.default/Mail/pop.orange.fr/Inbox' has invalid format
[10:11] <Laney> seb128: would it be alright to promote libgee-0.8?
[10:11] <seb128> Laney, want to make it the default version?
[10:11] <Laney> not really, just updating libdmapsharing which deps on this series
[10:11] <seb128> wfm
[10:11] <seb128> we should make it default
[10:12] <seb128> but I want to check with mhr3 if that's ok with them before
[10:12] <Laney> it's got a renamed pcfile
[10:12] <Laney> so actual source changes to rdeps
[10:16] <Laney> seems like it's only for the testsuite anyway here, not at runtime
[10:33] <Laney> seb128: right, uploaded - it will depwait so promote when you're ready please
[10:35] <seb128> Laney, cool, will do in a bit
[11:08] <seb128> Sweetshark, hey, do you have a saucy libreoffice upload planned soon?
[11:11] <cyphermox_> good morning
[11:11] <cyphermox_> seb128: sorry, my intent wasn't clear
[11:11] <seb128> cyphermox_, hey
[11:11] <seb128> cyphermox_, how are you?
[11:11] <cyphermox_> I do mention there are debug stuff left in; but I don't usually block merges on that unles it was just a printf ;)
[11:11] <cyphermox_> not bad, not bad
[11:12] <cyphermox_> bright and early this morning :)
[11:12] <seb128> cyphermox_, nice
[11:12] <Sweetshark> seb128: why?
[11:12] <seb128> cyphermox_, well, new glib landed and unity-panel-service goes segfault everytime you close a win
[11:13] <seb128> cyphermox_, so we somewhat need that libdbusmenu to land in saucy sooner rather than latter if we can ;-)
[11:13] <Sweetshark> seb128: AFAIK there will need to be one as the foundation guys will break LO brutally with gcc and boost updates ...
[11:13] <cyphermox_> seb128: if the tests pass I'm happy to land it ;)
[11:13] <seb128> Sweetshark, because there is a poppler transition waiting to start and libreoffice will need a no-change-rebuild (or any other kind of upload)
[11:15] <Sweetshark> seb128: so, upstream releases are still a bit off. the gcc/boost stuff will happen first.
[11:15] <Sweetshark> seb128: xnox tweaked around with that in Oakland, I havent checked the current state there yet ...
[11:16] <seb128> Sweetshark, what about uploading 4.0.3 in saucy?
[11:16] <seb128> Sweetshark, did anyone try if that builds in saucy or did it get hit by toolchain changes already?
[11:22] <Sweetshark> seb128: not tried yet. It will shure be hit by the toolchain changes.
[11:23] <Sweetshark> seb128: there is little difference between 4.0.2/.3 wrt that.
[11:23] <seb128> shrug
[11:23] <seb128> so that poppler transition will be blocked on libreoffice to build with the new toolchain
[11:23] <seb128> is that something you are working on atm?
[11:34] <Sweetshark> seb128: no, I only came across that by accident. xnox is doing that on some private archives. We essentially agreed that xnox would upload a fixed LO with the toolchain changes and I would then merge them into the debian-SCM.
[11:34] <seb128> xnox, ĥey ;-)
[11:49] <dpm> hey seb128, regarding the https://blueprints.launchpad.net/ubuntu/+spec/client-1305-printing-stack-with-mobile-in-mind bp you were pinging me about yesterday, I don't think I'll be able to attend to the rescheduled session, as I need to be on the appdev track. But in any case, I think I was added to the blueprint by mistake
[11:50] <dpm> I know nothing about printing and I'm not sure how I could contribute to the discussion
[11:50] <seb128> dpm, hey, no worry, Till added the subscribers, I was just trying to get people to join if anyone was interested since nobody was there
[11:50] <seb128> dpm, ok, fair enough
[14:24] <xnox> Sweetshark: seb128: yeah, it started building but eventually failed. need to look more into it.
[14:25] <seb128> xnox, please let me know before uploading once you get it done
[14:26] <seb128> xnox, we have a poppler transition to do and it will need a no change rebuild from libreoffice to pick the new soname
[14:26] <seb128> xnox, so I would like to get poppler in first
[14:50] <dobey> Laney: hey, might you have a suggestion on how to actually test the software-center fix for upgrade to 13.04?
[14:54] <Laney> dobey: hmm, not so much, short of trying some dist-upgrades and hoping you can show that you could hit it before and not after
[14:54] <Laney> at least it should be possible to observe that it drops off with the new versions on errors
[14:56] <dobey> switch all the archives to raring on quantal, enable raring-proposed, and do dist-upgrade?
[14:58] <Laney> something like that
[14:59] <Laney> assuming you get the bug without the raring-proposed bit
[15:00] <dobey> did python-gi with the Breaks: for aptdaemon make it into -updates yet?
[15:01] <Laney> no, that needs to happen with s-c
[15:03] <dobey> hrmm?
[15:11] <Laney> you Break the older software-centers too
[15:12] <dobey> right
[15:12] <dobey> and that's also still in -proposed
[15:12] <dobey> so without -proposed, i expect the issue to happen more often than not (esp. given the e.u.c numbers)
[15:24] <hyperair> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1173886 <-- could someone tell me the reasoning behind hardcoding the colour of the nautilus tile?
[15:24] <ubot2> Launchpad bug 1173886 in nautilus (Ubuntu) "Wrong background colour for nautilus icon in Unity launcher" [Undecided,New]
[15:24] <hyperair> before i get to work purging said patch
[15:25] <seb128> because the automatically picked color was not working well and nobody had time to do the proper fix which is to include that color info with the icon theme
[15:25]  * hyperair facepalms
[15:26] <hyperair> you know, if you shipped some icon metadata along with the specific icon that hinted to unity what the tile should be, that's one thing, but this is rather ridiculous.
[15:27] <hyperair> now i either have to 1) live with it, 2) run a patched nautilus, 3) dpkg-divert the desktop file, or 4) fork the desktop file into ~/.local/share/applications
[15:27] <seb128> read the comments on bug #1081691?
[15:27] <ubot2> Launchpad bug 1081691 in Ayatana Design "Launcher - Update the icons used for the Software Centre, Nautilus, and Software Updater" [Medium,Fix committed] https://launchpad.net/bugs/1081691
[15:28] <seb128> see e.g my comment #23
[15:29] <seb128> but it's only a color and most users don't change their icon theme
[15:29] <seb128> so it's a pretty minor issue and optimize for the most common case
[15:30] <hyperair> i can't help but wonder how many users actually customize their desktop theme..
[15:30] <seb128> a small % for sure
[15:30] <seb128> we don't even provide an ui to do that
[15:30] <seb128> we being GNOME or Unity
[15:31] <hyperair> we don't provide a ui to do that == let's trample all over the dconf settings because we don't give a f___
[15:31] <TheMuso> I get the feeling that all OSs are generally moving away from allowing customization. Hell one can't really customize IOS beyond text size for accessibility reasons...
[15:32] <hyperair> seb128: also i can't help but note the distinct lack of response to #23.
[15:32] <seb128> right
[15:32] <seb128> I agree to patch those icons as a workaround for raring
[15:32] <seb128> but only that
[15:33] <hyperair> okay, at least we live with a temporarily broken solution.
[15:33]  * hyperair sighs
[15:33] <hyperair> how about sticking metadata into the icons themselves to tell unity what colour it should use?
[15:33]  * hyperair wonders if anyone has tried that.
[15:38] <hyperair> ah, i see that icon metadata was mentioned in bug #962120
[15:38] <ubot2> Launchpad bug 962120 in Unity "Launcher - Add API to allow apps to override the Launcher tile colourisation with a colour of their choosing" [Medium,Fix released] https://launchpad.net/bugs/962120
[15:38] <hyperair> but https://bugs.launchpad.net/ayatana-design/+bug/962120/comments/4 picked the .desktop approach instead
[15:38] <hyperair> gekker, eh..
[15:38]  * hyperair polishes the kitchen knife
[15:47] <Sweetshark> xnox: thx. can I help out there somehow, or is it a mess to get that environment set up?
[15:49] <xnox> Sweetshark: it's not a mess =) but I should push "my current state of the art somewhere"
[16:06] <desrt_> Laney: rumour has it i owe you a beer :)
[16:07] <desrt> (for tricking seb)
[16:07] <Laney> the anti-thunderbird crew
[16:08] <desrt> larsu already cooked a fix
[16:08] <desrt> it's trivial
[16:08] <Laney> some mangling of the id?
[16:09] <desrt> that's what he was going to do
[16:09] <desrt> then i reminded him that he's using the wrong API in the first place
[16:09] <Sweetshark> xnox: yes, please do ;)
[16:09] <desrt> the detailed action parsing only applies if you use an API that takes detailed action names
[16:09] <desrt> which he should not have been doing, since there is no possibility of a target
[16:11] <desrt> it would have caused problems before if someone used an action with a '::' in the name
[16:11] <desrt> but now it's fixed properly
[16:14] <Laney> great
[16:16] <larsu_> Laney, cyphermox, seb128: patch is here: https://code.launchpad.net/~larsu/indicator-messages/lp1180302
[16:16] <desrt> see https://bugzilla.gnome.org/show_bug.cgi?id=700398
[16:16] <ubot2> Gnome bug 700398 in gapplication "Warn about detailed_action parameters" [Enhancement,New]
[16:16] <seb128> larsu_, great, thanks
[16:16] <desrt> this bug is about the trap that larsu fell into
[16:17] <seb128> larsu_, I'm in a vUDS session atm but will try as soon as it's over
[16:17] <desrt> seb128: bonjour de montréal!
[16:18] <seb128> desrt, bonjour de france ;-)
[16:18] <desrt> oh.  you're visiting france today? ;)
[16:24] <larsu_> seb128: tested on cyphermox's machine. Thunderbird is still rnuning..
[16:25] <cyphermox> as opposed to crashing without touching anything, yeah, it's improved
[16:26] <larsu> :)
[16:28] <Laney> cyphermox: can you get it uploaded to saucy?
[16:30] <cyphermox> yes, will do it
[16:31] <Laney> bonus
[16:33] <cyphermox> moo?
[16:44] <desrt> seb128: so.... this g_error() in GMenu should have been a g_critical()
[16:44] <desrt> but......
[16:44] <desrt> i want fatal criticals
[16:44] <desrt> but.......
[16:44] <desrt> only for developers
[16:44]  * larsu blames this whole bug on desrt now!
[16:44] <desrt> so i have an idea i want to bounce off of you
[16:44] <desrt> which is that we turn criticals fatal only if we find glib.h is installed
[16:44] <desrt> ie: if you install -dev packages, you get fatal criticals
[16:45] <desrt> this is a good way to ensure our developers are fixing problems properly while not hurting "normal users"
[16:53] <desrt> could also base it on the -dbg/-dbgsyms package being installed
[17:00] <seb128> desrt, sorry, I was in an hangout
[17:00] <seb128> desrt, well, devs can optin easily by setting an env variable
[17:00] <desrt> seb128: but nobody does.... we need a good 'automatic' hook
[17:01] <seb128> there is no good automatic
[17:01] <desrt> another possibility that i consider: if your session crashes as the result of a fatal critical, we give you the option to login again with fatal criticals disabled
[17:01] <desrt> so that people don't get 'stuck'
[17:02] <seb128> like making your shell or im client or email client not start is going to make you not able to get work done and you are not the one who is going to fix those in most cases
[17:02] <desrt> well
[17:02] <desrt> look at what happens today
[17:02] <desrt> i use g_error() because everyone ignores criticals
[17:02] <desrt> then _everyone_ suffers
[17:02] <seb128> everyone running unstable
[17:02] <larsu> you shouldn't have used g_error...
[17:02] <seb128> which is probably close from the set of those having -dev installed
[17:03] <desrt> larsu: i shouldn't have to contend with a log file full of ignored criticals
[17:03] <desrt> seb128: not toward the end of the cycle...
[17:03] <desrt> seb128: i'd still support an opt-out
[17:03] <desrt> G_DEBUG=not-fatal-criticals or so
[17:03] <desrt> so people could easily work around
[17:03] <desrt> anyway... cyphermox wants lunch now
[17:03] <seb128> I think it's a social issue more than a technical one
[17:04] <desrt> time to go :)
[17:04] <seb128> the people who care should opt in
[17:04] <desrt> seb128: i agree.
[17:04] <seb128> desrt, enjoy!
[17:04] <desrt> but ya... bye :)
[17:06] <larsu> from desrt: the people who don't care, are the ones who cause the problems. And then the people who do care, and opt-in, are not the best people to fix the problems
[17:06] <larsu> if everybody was automatically opted in, then there wouldn't be a problem
[17:06] <seb128> larsu, a discussion to have over beer
[17:07] <seb128> larsu, I blame you and desrt for not doing opt-in, it's a bug in your code, you should have noticed it :p
[17:07]  * seb128 hides
[17:07] <seb128> larsu, and go for lunch before you all starve in front of your keyboards ;-)
[18:05] <desrt> seb128: it's an integration problem -- nobody's fault and everybody's fault, as usual
[18:19] <didrocks> robru: did you poke the archive admins about reviewing the packages in NEW?
[18:19] <didrocks> robru: https://launchpad.net/ubuntu/saucy/+queue
[18:20] <robru> didrocks, nope... in a vuds session though brb
[18:20] <didrocks> seb128: you can't talk, do you have time? they should be easy ^
[18:20] <didrocks> :)
[18:20] <seb128> didrocks, suuuure
[18:20] <seb128> ;-)
[18:20] <didrocks> thanks!
[18:28] <seb128> didrocks, hum, first on I review (unity-webapps-googleplusgames), copyright has:
[18:28] <seb128> "Files: */*.png */*.svg
[18:28] <seb128> Copyright: various
[18:28] <seb128> License: trademark-controlled"
[18:28] <seb128> which is weird
[18:28] <seb128> since the source has no such files
[18:28] <didrocks> seb128: I guess this is for robru ^
[18:28] <seb128> could be
[18:28] <didrocks> seb128: it's all robru's, I think he's going to fix all those ;)
[18:28] <seb128> I guess that's not a stopper
[18:29] <didrocks> yeah, it's weird
[18:32] <seb128> hum, -amazon lacks a COPYING (not blocker)
[18:33] <seb128> -yandexmusic
[18:33] <seb128> Files: debian/*
[18:33] <seb128> Copyright: 2012 The friendly pkgme.net robot
[18:33] <seb128> License: public-domain
[18:33] <seb128>
[18:33] <seb128> lol ;-)
[18:35] <seb128> same for -wordpress
[18:40] <didrocks> I think robru isn't done with webapps yet :p
[18:43] <seb128> right
[18:43] <seb128> didrocks, accepted indicators-client though
[18:43] <didrocks> seb128: thanks!
[18:43] <seb128> yw
[18:45] <seb128> ok, newing the webapp ones, the issues I listed before are not stoppers but would be nice to fix
[18:45] <seb128> robru, ^
[18:48] <robru> seb128, didrocks: don't look at me! this is how I inherited it from alex-abreu
[18:48] <didrocks> robru: we are *staring* at you!
[18:48] <alex-abreu> noooo
[18:48] <alex-abreu> robru, don't do finger poiting :)
[18:48] <alex-abreu> pointing
[18:49] <robru> seb128, which apps did you find had copyright files that referenced files that don't exist?
[18:49] <robru> just googleplusgames?
[18:49] <seb128> robru, no, the 5 I just newed
[18:49] <seb128> I guess the copyright is all coming from the same original source
[18:49] <alex-abreu> robru, seb128 we should review those and update the license indeed
[18:50] <alex-abreu> seb128, yeah, it was done a bit too fast there
[18:51] <alex-abreu> robru, I think that's why (at the time) I didn't include some webapps ... (e.g. g+ games)
[18:51] <robru> alex-abreu, this should be your motivation to fix them all ;-)
[18:51] <alex-abreu> *my* ? :) ... yeah send me a list and I can have a quick look
[18:52] <seb128> cyphermox, how is the indicator-messages landing going?
[18:52] <alex-abreu> feel free to share the "burden"
[18:52] <cyphermox> just about done
[18:53] <seb128> cyphermox, \o/
[18:53] <cyphermox> seb128: it's standard jenkins/autopilot delayu
[18:53] <cyphermox> as soon as it fails I'll publish
[18:54] <seb128> cyphermox, no worry, I'm just making sure it lands today so people have their email client back to be working tomorrow
[19:10] <cyphermox> yes, I want to land today but I didn't want to disable autopilot in case we could actually have successful results eventually
[19:10] <cyphermox> it looks like ATI might not fail this time
[19:10] <cyphermox> so I'm just waiting to see what the results will be
[19:10] <cyphermox> seb128: ^
[19:12] <seb128> cyphermox, ok, as long as it's built by tomorrow morning I'm happy ;-)
[20:49] <mterry> ChrisTownsend, so I'm testing your Ubuntu One patches to duplicity for inclusion in saucy/raring
[20:50] <mterry> ChrisTownsend, they don't seem to change anything.  I still get 500 errors
[20:51] <ChrisTownsend> mterry: Well, it doesn't address the real problem of why errors are occurring, it just gives it a chance for the retries to actually work by resetting the file pointer back to the beginning of the file.
[20:51] <ChrisTownsend> mterry: I'm not sure why the errors occur.
[20:52] <ChrisTownsend> mterry: Before, the retries would always fail because of the file pointer.
[20:52] <mterry> ChrisTownsend, OK.  But you made it sound like usually retrying will allow DD to continue, but I'm still reliably getting the error.  This is on GET requests
[20:53] <ChrisTownsend> mterry: I was reliably getting 404 Bad Request errors on retry.  Now it works mostly better, but I have seen the retries even fail on occasion.
[20:53] <ChrisTownsend> mterry: So my fix supposedly addresses those 404 errors by resetting the file pointer and resending out a good request.
[20:54] <ChrisTownsend> mterry: Perhaps we should still have the U1 team involved on why other errors are occurring???
[20:55] <mterry> ChrisTownsend, maybe... but I still suspect it's something we're doing client-side, since only 13.04 shows the bug
[20:56] <mterry> ChrisTownsend, maybe we're signing the oauth stuff bad or something like that
[20:56] <ChrisTownsend> mterry: Hmm, yeah.  About 95% of the time now, I can get through a backup now where before, it would always fail.
[20:57] <ChrisTownsend> mterry: So you said you see 500 errors and not 404's?
[20:57] <ChrisTownsend> mterry: Probably more than one bug on this one.
[20:58] <mterry> ChrisTownsend, mine are 500s yeah
[20:58] <mterry> ChrisTownsend, will look into it my 500s
[20:59] <ChrisTownsend> mterry: That's a generic Internal Server Error which is different than what I was chasing.
[20:59] <ChrisTownsend> mterry: Cool, let me know if I can help anymore.
[21:51] <sil2100> thomi: ping!
[21:51] <sil2100> thomi: hi!
[21:51] <sil2100> thomi: so, actually even after merging in my branch, there are still around 10 failures in autopilot
[21:51] <sil2100> thomi: https://code.launchpad.net/~autopilot/autopilot/more_ap_ap_test_fixes/+merge/164037
[21:52] <sil2100> Here's a branch in progress that we can co-work on, the description has the path to the latest AP run with my merges merged in
[21:52] <sil2100> thomi: you think you could find some time to look at those fixes, add them to this branch and maybe even get it all reviewed?


[06:49] <ricotz> hello :), please remove the leftover binaries of llvm-toolchain-snapshot in impish-proposed/universe - https://launchpad.net/ubuntu/+source/llvm-toolchain-snapshot/1:14~++20210924122635+4a57f5d1e1c5-1~exp1
[07:49] <fossfreedom> Any archive-admins around? Is there a way to prevent i386 autopackage regression test failures for budgie-desktop please? 32bit tests aren't applicable for our package. TIA https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#budgie-desktop
[07:55] <RikMills> hmmmm. I though the migration reference would make that not be seen as a regression
[08:13] -queuebot:#ubuntu-release- New: accepted carla [amd64] (jammy-proposed) [2.4.2-0ubuntu2]
[08:13] -queuebot:#ubuntu-release- New: accepted cplay-ng [amd64] (jammy-proposed) [5.0.1-2]
[08:13] -queuebot:#ubuntu-release- New: accepted draco [arm64] (jammy-proposed) [1.5.2+dfsg-2]
[08:13] -queuebot:#ubuntu-release- New: accepted draco [ppc64el] (jammy-proposed) [1.5.2+dfsg-2]
[08:13] -queuebot:#ubuntu-release- New: accepted draco [s390x] (jammy-proposed) [1.5.2+dfsg-2]
[08:13] -queuebot:#ubuntu-release- New: accepted openrefine [amd64] (jammy-proposed) [3.5.2-1]
[08:13] -queuebot:#ubuntu-release- New: accepted carla [i386] (jammy-proposed) [2.4.2-0ubuntu2]
[08:13] -queuebot:#ubuntu-release- New: accepted draco [armhf] (jammy-proposed) [1.5.2+dfsg-2]
[08:13] -queuebot:#ubuntu-release- New: accepted onevpl-intel-gpu [amd64] (jammy-proposed) [22.2.0-1]
[08:13] -queuebot:#ubuntu-release- New: accepted draco [amd64] (jammy-proposed) [1.5.2+dfsg-2]
[08:13] -queuebot:#ubuntu-release- New: accepted draco [riscv64] (jammy-proposed) [1.5.2+dfsg-2]
[08:13] -queuebot:#ubuntu-release- New: accepted mutter [amd64] (jammy-proposed) [42~beta-0ubuntu1]
[08:13] -queuebot:#ubuntu-release- New: accepted mutter [armhf] (jammy-proposed) [42~beta-0ubuntu1]
[08:13] -queuebot:#ubuntu-release- New: accepted mutter [riscv64] (jammy-proposed) [42~beta-0ubuntu1]
[08:13] -queuebot:#ubuntu-release- New: accepted mutter [arm64] (jammy-proposed) [42~beta-0ubuntu1]
[08:13] -queuebot:#ubuntu-release- New: accepted mutter [s390x] (jammy-proposed) [42~beta-0ubuntu1]
[08:13] -queuebot:#ubuntu-release- New: accepted mutter [ppc64el] (jammy-proposed) [42~beta-0ubuntu1]
[08:25] <juliank> ok so this is where rabbitmq memory goes connection_other: 1.1538 gb (56.72%)
[08:25] <juliank> "Other memory related to client connections"
[08:30] -queuebot:#ubuntu-release- New: accepted grub2 [riscv64] (jammy-proposed) [2.06-2ubuntu5]
[08:31] -queuebot:#ubuntu-release- New: accepted libzdnn [s390x] (jammy-proposed) [0.4.0-0ubuntu1]
[08:43] <juliank> now everyone go nuts on autopkgtests again! :D
[08:46] <juliank> I retried ~165 things on arm64 that probably did not need retrying
[08:46] <juliank> Unfortunately don't have integration to see which tests have already passed and don't need a retry
[08:46] <juliank> (I was retrying --state RUNNING to make sure we don't miss anyone)
[08:48] <juliank> (but they're in huge, so any manual retries and !huge uploads take precedence)
[10:14] <sil2100> RikMills: hey! I got some notification about some important KDE patch SRUs - do you know what packages does that mean? Do you have any context for that?
[10:19] <RikMills> https://mail.kde.org/pipermail/distributions/2022-February/001140.html
[10:19] <RikMills> https://mail.kde.org/pipermail/distributions/2022-February/001157.html
[10:20] <RikMills> ^ sil2100
[10:20] <RikMills> the packages in impish are knewstuff, plasma-discover, and plasma-desktop
[10:21] <RikMills> done test builds of knewstuff and plasma-discover in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4793/+packages
[10:22] <RikMills> the patch to plasma-desktop does not backport at the moment. needs other patches I think
[10:24] <sil2100> Okay, so it's in progress then. The e-mail made it sound as if it was blocked by our policies, but it seems its still 'in the works'. Is that impish only, or focal/jammy as well?
[10:26] <RikMills> sil2100: impish only. in terms of a block, as they were told about the 7 days SRU wait, they are anticipating that as a block to a quick rillout
[10:26] <RikMills> *rollout
[10:31] <sil2100> RikMills: we can work something out, but seeing that there was no new KDE-stack updates in impish since release, this seems like something that was happening since 21.10's release?
[10:32] <sil2100> Or did something break in the meantime, causing the existing packages to start going crazy?
[10:32] <RikMills> sil2100: it was, but spiked since emails went out saying 21.04 was near EOL and to upgrade. I have a link to the traffic plot somewhere
[10:33] <sil2100> I don't mean that skipping the 7-day aging is impossible, but then again I still think that we shouldn't rush anything if it's not an update-regression
[10:34] <sil2100> Though I do test the testing you and your team does, so we could certainly look into cutting the time if enough testing is done
[10:34] <sil2100> s/test/trust/
[10:41] <RikMills> sil2100: https://paste.opensuse.org/images/80029574.png
[10:42] <RikMills> so not too bad when impish was released, but climbed steadily, until the 21.04 EOL announce went out
[10:42] <RikMills> when presumably lots of people upgraded
[10:42] <sil2100> RikMills: indeed
[10:42] <sil2100> ginggs: hey, will you have some cycles today for some .4 stuff?
[10:43] <ginggs> sil2100: sure
[10:44] <sil2100> ginggs: I'd need someone to diff the manifests of the current test release candidates (for all flavors we support) against their .3 images and checking if there's nothing ominous in the diffs (possibly maybe even publishing those diffs somewhere)
[10:44] <sil2100> To make sure we're not suddenly pulling in half of the archive or something
[10:45] <ginggs> i can do that
[10:46] <sil2100> So fetching all the .3 image manifests from cdimage.ubuntu.com releases/ + releases.ubuntu.com manifests and diffing against the latest focal dailies, which should be the latest .4 RCs
[10:46] <sil2100> ginggs: thanks!
[12:22] <ricotz> hello :), please remove the leftover binaries of llvm-toolchain-snapshot in impish-proposed/universe - https://launchpad.net/ubuntu/+source/llvm-toolchain-snapshot/1:14~++20210924122635+4a57f5d1e1c5-1~exp1
[13:16] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (bionic-proposed) [1.173.21]
[13:17] -queuebot:#ubuntu-release- New binary: llvm-toolchain-snapshot [i386] (jammy-proposed/universe) [1:15~++20220202093833+1a3137dc8451-1~exp1] (i386-whitelist)
[13:41] -queuebot:#ubuntu-release- New binary: llvm-toolchain-snapshot [ppc64el] (jammy-proposed/universe) [1:15~++20220202093833+1a3137dc8451-1~exp1] (i386-whitelist)
[14:21] -queuebot:#ubuntu-release- New binary: llvm-toolchain-snapshot [amd64] (jammy-proposed/universe) [1:15~++20220202093833+1a3137dc8451-1~exp1] (i386-whitelist)
[15:23] <paride> sil2100, I think I spotted an issue with the subiquity images
[15:24] <paride> I still have to identify the secret ingredient to recreate it, as this happened on some local testing where I did a very custom install
[15:25] <paride> the issue is with /home/<user> being root:root owned
[15:26] <paride> (with /home in a separate partition in an encrypted LVM volume)
[16:06] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-snapshot [amd64] (jammy-proposed) [1:15~++20220202093833+1a3137dc8451-1~exp1]
[16:06] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-snapshot [ppc64el] (jammy-proposed) [1:15~++20220202093833+1a3137dc8451-1~exp1]
[16:06] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-snapshot [i386] (jammy-proposed) [1:15~++20220202093833+1a3137dc8451-1~exp1]
[16:06] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-snapshot [s390x] (jammy-proposed) [1:15~++20220202093833+1a3137dc8451-1~exp1]
[16:40] <athos> Hi! Would any ubuntu-archive admin be able to take a look at LP: #1118815 to remove python-oauth from the archive?
[16:42] <jbicha> also bug 1961585
[17:19] <paride> sil2100, OK I reproduced it, it's not *that* bad, and the secret ingredient is _time_
[17:20] <rbasak> jbicha: I'm not an archive admin, but I thought we generally tried to fix FTBFS before removal? In this case it looks like it might be a problem with libcereal-dev rather than slic3r-prusa, or even if not, something build related rather than a true upstream bug?
[17:55] <paride> sil2100, https://bugs.launchpad.net/cloud-init/+bug/1961620
[17:56] <paride> blackboxsw, ^^
[17:56] <paride> sil2100, not a blocker but not nice
[18:00] <xnox> paride:  to me that bug sounds critical =)
[18:00] <jbicha> rbasak: oh, I didn't investigate any further after clearing the other boost blockers
[18:01] <paride> xnox, I know it sounds critical, but I *think* is has been there for a very long time now
[18:02] <paride> xnox, and the race is slow, so you really have to wait a minute or two at the 'enter password' prompt
[18:02] <paride> xnox, I'm going to try with one of the released images to verify it's not a regression
[18:04] <paride> Maybe we need an After=home.mount, provided that systemd is happy dealing with nonexistent units (most of the time home.mount doesn't exist)
[18:04] <xnox> paride: yeah, critical, but not a regression sounds about right
[18:06]  * paride grabs 20.04.3
[18:12] <blackboxsw> eww paride good find, bad bug.
[20:10] -queuebot:#ubuntu-release- Unapproved: gramps (focal-backports/universe) [5.1.2-1 => 5.1.4-1~bpo20.04.1] (edubuntu)
[20:11] <xnox> copying apparmor built against jammy-release to make it migrate and unblock kernel testing & kernle migration; once that migrates will reupload apparmor rebuild against the new perl abi.
[22:45] <sil2100> Okay everyone, I think it's time to build the first batch of non-test official .4 RCs!
[22:54] <sil2100> o/
[22:54] <sil2100> Builds running
[22:54] <sil2100> See you tomorrow everyone o/
[23:16] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Focal 20.04.4] has been updated (20220221)
[23:17] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Focal 20.04.4] has been updated (20220221.6)
[23:22] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Focal 20.04.4] has been updated (20220221)
[23:23] -queuebot:#ubuntu-release- New binary: e-antic [amd64] (jammy-proposed/universe) [1.1.0+ds-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: node-std-mocks [amd64] (jammy-proposed/none) [1.0.1-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: highway [ppc64el] (jammy-proposed/universe) [0.16.0-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: scitokens-cpp [amd64] (jammy-proposed/universe) [0.7.0-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: rust-html-escape [amd64] (jammy-proposed/none) [0.2.9-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: highway [s390x] (jammy-proposed/universe) [0.16.0-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: pyyaml-env-tag [amd64] (jammy-proposed/none) [0.1-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: utf8-locale [amd64] (jammy-proposed/none) [0.3.0-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: python-rcon [amd64] (jammy-proposed/none) [1.3.8-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: schoolkit [amd64] (jammy-proposed/universe) [0.2-2] (no packageset)
[23:25] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Focal 20.04.4] has been updated (20220221)
[23:25] -queuebot:#ubuntu-release- New binary: e-antic [ppc64el] (jammy-proposed/universe) [1.1.0+ds-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: highway [amd64] (jammy-proposed/universe) [0.16.0-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: e-antic [s390x] (jammy-proposed/universe) [1.1.0+ds-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: node-cycle [amd64] (jammy-proposed/none) [1.0.3-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: fcitx5-anthy [amd64] (jammy-proposed/universe) [5.0.9-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: r-cran-lobstr [amd64] (jammy-proposed/universe) [1.1.1-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: kquickimageeditor [amd64] (jammy-proposed/universe) [0.2.0-2] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: rust-smallbitvec [amd64] (jammy-proposed/universe) [2.5.1-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: golang-github-intel-goresctrl [amd64] (jammy-proposed/universe) [0.2.0-2] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: scitokens-cpp [ppc64el] (jammy-proposed/universe) [0.7.0-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: python-aioapns [amd64] (jammy-proposed/universe) [2.1-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: highway [arm64] (jammy-proposed/universe) [0.16.0-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: rust-smallbitvec [ppc64el] (jammy-proposed/universe) [2.5.1-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: rust-html-escape [ppc64el] (jammy-proposed/universe) [0.2.9-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: scitokens-cpp [s390x] (jammy-proposed/universe) [0.7.0-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: fcitx5-anthy [ppc64el] (jammy-proposed/universe) [5.0.9-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: r-cran-lobstr [ppc64el] (jammy-proposed/universe) [1.1.1-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: kquickimageeditor [ppc64el] (jammy-proposed/universe) [0.2.0-2] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: tox-delay [amd64] (jammy-proposed/universe) [0.1.0-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: e-antic [armhf] (jammy-proposed/universe) [1.1.0+ds-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: utf8-locale [ppc64el] (jammy-proposed/universe) [0.3.0-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: r-cran-lobstr [s390x] (jammy-proposed/universe) [1.1.1-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: e-antic [arm64] (jammy-proposed/universe) [1.1.0+ds-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: kquickimageeditor [s390x] (jammy-proposed/universe) [0.2.0-2] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: fcitx5-anthy [s390x] (jammy-proposed/universe) [5.0.9-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: rust-html-escape [s390x] (jammy-proposed/universe) [0.2.9-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: rust-smallbitvec [s390x] (jammy-proposed/universe) [2.5.1-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: utf8-locale [s390x] (jammy-proposed/universe) [0.3.0-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Focal 20.04.4] has been updated (20220221)
[23:33] -queuebot:#ubuntu-release- New binary: scitokens-cpp [arm64] (jammy-proposed/universe) [0.7.0-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: scitokens-cpp [armhf] (jammy-proposed/universe) [0.7.0-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: fcitx5-anthy [armhf] (jammy-proposed/universe) [5.0.9-1] (no packageset)
[23:35] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Focal 20.04.4] has been updated (20220221)
[23:35] -queuebot:#ubuntu-release- New binary: fcitx5-anthy [arm64] (jammy-proposed/universe) [5.0.9-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: kquickimageeditor [arm64] (jammy-proposed/universe) [0.2.0-2] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: kquickimageeditor [armhf] (jammy-proposed/universe) [0.2.0-2] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: r-cran-lobstr [armhf] (jammy-proposed/universe) [1.1.1-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: rust-html-escape [armhf] (jammy-proposed/universe) [0.2.9-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: rust-smallbitvec [armhf] (jammy-proposed/universe) [2.5.1-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: rust-html-escape [arm64] (jammy-proposed/universe) [0.2.9-1] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: tiledb-py [s390x] (jammy-proposed/universe) [0.12.2-2] (no packageset)
[23:36] -queuebot:#ubuntu-release- New binary: rust-smallbitvec [arm64] (jammy-proposed/universe) [2.5.1-1] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: r-cran-lobstr [arm64] (jammy-proposed/universe) [1.1.1-1] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: utf8-locale [armhf] (jammy-proposed/universe) [0.3.0-1] (no packageset)
[23:38] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Focal 20.04.4] has been updated (20220221)
[23:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Focal 20.04.4] has been updated (20220221)
[23:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Focal 20.04.4] has been updated (20220221)
[23:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Focal 20.04.4] has been updated (20220221)
[23:38] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Focal 20.04.4] has been updated (20220221)
[23:39] -queuebot:#ubuntu-release- New binary: tiledb-py [amd64] (jammy-proposed/universe) [0.12.2-2] (no packageset)
[23:39] -queuebot:#ubuntu-release- New binary: utf8-locale [arm64] (jammy-proposed/universe) [0.3.0-1] (no packageset)
[23:43] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Focal 20.04.4] has been updated (20220221)
[23:47] -queuebot:#ubuntu-release- New binary: scitokens-cpp [riscv64] (jammy-proposed/universe) [0.7.0-1] (no packageset)
[23:54] -queuebot:#ubuntu-release- New binary: kquickimageeditor [riscv64] (jammy-proposed/universe) [0.2.0-2] (no packageset)
[23:56] -queuebot:#ubuntu-release- New binary: tiledb-py [arm64] (jammy-proposed/universe) [0.12.2-2] (no packageset)