[06:44] <oSoMoN> good morning desktoppers
[09:02] <seb128> goood morning desktopers!
[09:14] <oSoMoN> salut seb128 
[09:14] <seb128> oSoMoN, salut! en forme ?
[09:15] <oSoMoN> ça va, et toi?
[09:20] <seb128> nickel!
[09:20] <Wimpy> Bonjour o/
[09:48] <seb128> Wimpy, salut, ça va ?
[09:50] <Wimpy> Aller bien. Mais il fait un froid glacial ici !
[09:51] <seb128> brrrrrrrr :)
[10:17] <oSoMoN> hi Wimpy !
[12:56] <kenvandine> mitya57:  hey, i got a ping for the folks at telegram asking if i can help them transition the telegram-desktop deb to a snap.  Looks like you have had a number of uploads on that, is that a package you typically look after?
[12:57] <kenvandine> the older versions do not work well and they need to be able to make sure users stay pretty current
[12:57] <kenvandine> s/for/from/
[12:57] <ogra> sounds like you want something like firefox or chromium do ? (deb2snap transition)
[13:01] <kenvandine> yup
[13:02] <kenvandine> that's exactly what they are asking for
[13:04] <jbicha> good morning
[13:06] <ogra> looks like it is an import from debian though ... there was only a singl no-change rebuild to have it pick up new Qt versions from the archive
[13:32] <mitya57> kenvandine: Hi! All my telegram-desktop uploads were just rebuilds for Qt ABI breaks :)
[13:33] <mitya57> If you need someone who needs the package well, you may try asking the maintainer of it in Debian.
[13:33] <mitya57> *who knows the package
[13:33] <kenvandine> that's fine, we wouldn't want deb2snap in debian
[13:34] <kenvandine> just making sure i wasn't going to step on anyone's toes :)
[13:35] <kenvandine> quite a few features in the version in bionic and focal aren't supported, and users just quietly miss messages, for example
[13:35] <kenvandine> and that kind of thing will continue to happen
[14:24] <ricotz> hello desktopers, could someone take a look at https://code.launchpad.net/~ricotz/ubuntu-seeds/+git/ubuntu/+merge/434778
[18:34] <bandali> good day
[18:35] <bandali> hey ricotz, so there was a new firefox point release (108.0.1) today. i'll push to both PPAs (~mozillateam's and ~ubuntu-mozilla-security's), though the sponsoring/uploading of it by security team will most likely be done after the holidays
[18:50] <ricotz> bandali, hi, great, please *only* push to ubuntu-mozilla-security ppa
[18:51] <ricotz> :\
[18:52] <ricotz> there is no need for two identicial source builds resulting in different binaries
[19:20] <ricotz> bandali, still around?
[19:59] <bandali> ricotz, hey, am around now
[19:59] <bandali> sorry i'd already pushed to the mozillateam ppa for bionic and focal :/
[20:00] <bandali> i see the builds were cancelled
[20:01] <ricotz> bandali, hey, to not conflict with the official builds in the security ppa I am adding ~mtX suffixes, but if there are foreseeable uploads to the security ppa then a binary copy of the successful builds are the best
[20:02] <ricotz> same for the thunderbird builds
[20:02] <ricotz> yeah, I cancelled them in favor the security ppa builds
[20:03] <bandali> ah ok cool cool. yeah i'll push to the security ppa for bionic and focal in a bit
[20:03] <ricotz> note that the build-deps are not an exact match between the two PPAs, so the security PPA builds are preferred
[20:04] <bandali> noted
[20:04] <ricotz> thanks! I am going to binary copy them from there when they finished :)
[20:06] <bandali> sounds good!
[20:06] <ricotz> bandali, I am wondering if there were any issues with the missing s390x builds?
[20:07] <bandali> ricotz, the desktop and security team seem to agree that the broken builds on s390x for firefox are not critical
[20:08] <bandali> but if i do manage to get my hands on a s390x vm i can try generating patch like you'd done for the other arches and see if it helps
[20:08] <ricotz> bandali, I see, noted :)
[20:09] <ricotz> I still have hope for an upstream fix to have those files properly generated on build-time :)
[20:10] <bandali> right, yeah that would be great
[21:01] <seb128> ahasenack_, hey, unsure what happened to update-notifier/bionic, didn't I fix it yesterday?
[21:02] <ahasenack_> seb128: I don't know, but the last upload again didn't have the autoconf generated files, and the build failed
[21:02] <ahasenack_> seb128: I filed a bug for it, #1999897
[21:03] <seb128> ahasenack_, where did it fail? I don't see it accepted
[21:03] <ahasenack_> seb128: I tried a build before accepting
[21:04] <ahasenack_> seb128: the one at the top (most recent), https://launchpad.net/ubuntu/bionic/+queue?queue_state=4&queue_text=update-notifier
[21:04] <ahasenack_> you can see in the diff it's removing the autoconf generated files
[21:04] <ahasenack_> I was considering uploading with that restored and accepting, but didn't get to it today
[21:05] <seb128> ahasenack_, I don't understand, I've a .upload from the right version
[21:05] <ahasenack_> seb128: do a dget https://launchpad.net/ubuntu/bionic/+upload/29992183/+files/update-notifier_3.192.1.15.dsc
[21:05] <ahasenack_> open it up
[21:06] <ahasenack_> and you will see there is only autogen.sh in the source directory
[21:06] <seb128> ahasenack_, I'm just saying I don't understand what happened
[21:06] <ahasenack_> ah
[21:06] <seb128> the content on my disk is right
[21:06] <seb128> I reuploaded...
[21:06] <seb128> it's in the queue
[21:06] <ahasenack_> seb128: the upstream bionic branch has the problem, it doesn't build in bionic
[21:06] <ahasenack_> but the bionic package, in the archive, builds
[21:06] <ahasenack_> it has the autoconf generated files
[21:07] <seb128> ahasenack_, right, I fixed manually the source yesterday to get that moving, I don't want to investigate buggy vcses at this point before holidays
[21:07] <ahasenack_> likewise :)
[21:07] <seb128> ahasenack_, the queue has a working one now
[21:07] <seb128> I just opened the source from the queue in my browser
[21:07] <ahasenack_> maybe you fixed it for one upload, then there was the wrong changes file, and that upload lost the fix?
[21:07] <seb128> it has the configure
[21:08] <seb128> yeah, dunno at this point, but if you want to wrap that before holidays the queue should be right
[21:08] <seb128> let me check xenial as well
[21:08] <ahasenack_> xenial was fine, but yeah
[21:08]  * ahasenack_ dgets
[21:08] <ahasenack_> yes!
[21:10] <seb128> ahasenack_, ah, I misread what you wrote on the bug about xenial, k, so we should be sorted out now
[21:10] <seb128> ahasenack_, thanks again for catching up the different problems and sorry for the buggy uploads
[21:10] <ahasenack_> seb128: the changes file again... ;)
[21:11] <seb128> SHRUG
[21:11] <ahasenack_> hahaha
[21:12] <seb128> ahasenack_, reupload, let's see if I managed to yet again screw something :-p
[21:12] <seb128> reuploaded I mean
[21:13] <ahasenack_> changes ok
[21:13] <ahasenack_> getting the thing
[21:13] <ahasenack_> contents ok
[21:13] <ahasenack_> phew
[21:14] <seb128> ahasenack_, THANKS :-)
[21:14] <seb128> \o/
[21:14] <ahasenack_> \o/