[06:05] <cpaelzer> good morning
[06:48] <utkarsh2102> cpaelzer: do you see my emojis? :)
[06:49] <cpaelzer> utkarsh2102: I see too many emojis in general :-)
[06:50]  * cpaelzer likes hand-typed :-) ascii smileys
[06:53] <utkarsh2102> aha
[06:54] <utkarsh2102> I can't make sunrise ones hand-typed
[08:01] <utkarsh2102> hey, is there anything that I can help with that'll help others? eg: reviews/bugs/etc that'll unblock others?
[08:12] <paride> o/
[08:12] <paride> TIL that ~/.pam_environment is being deprecated
[08:43] <mirespace> good morning here as well :)
[08:55] <cpaelzer> utkarsh2102: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/415170 ?
[08:56] <cpaelzer> utkarsh2102: in regard your ask for helping somewhere
[09:06] <utkarsh2102> gotcha! I'll TAL in a few minutes or after lunch.
[09:07] <utkarsh2102> like, server-todo, we have server-backlog, too, no?
[09:07] <utkarsh2102> or did I get it wrong?
[09:07] <utkarsh2102> cf: tags for bug triages
[09:08] <frickler> coreycb: are you planning to run with py3.10 for jammy? then this might be interesting for you https://bugs.launchpad.net/horizon/+bug/1960204
[09:09] <cpaelzer> utkarsh2102: I can pass you a link for the extended backlog to go through - just a sec
[09:13] <utkarsh2102> thank you!
[09:26] <cpaelzer> utkarsh2102: do you have a list of our mysql master bugs to dup to?
[09:26] <utkarsh2102> I don't think so
[09:26] <utkarsh2102> but somewhere in e-mail, I guess
[09:27] <utkarsh2102> I see Lena did a lot of duping of bugs onto some specific ones
[09:27] <utkarsh2102> I get mails of all mysql* related activities, so that way, I know
[09:30] <cpaelzer> utkarsh2102: I knew we had something https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bugs?&field.tag=triage
[09:30] <cpaelzer> from the newer completed https://wiki.ubuntu.com/ServerTeam/mysql
[09:31] <utkarsh2102> gotcha!
[09:31] <utkarsh2102> btw, we have more mysql-8.0 bugs than mysql-5.7 ones
[09:32] <cpaelzer> the mysql-8.0 bug sorted by heat are also handy to identify dup-candidates
[09:50] <paride> cpaelzer, fiy upstream s390-tools with fuse3 support has been released
[09:51] <paride> (for some permutation of fiy)
[09:52] <cpaelzer> yeah fheimes already told me this morning
[11:03] <utkarsh2102> cpaelzer: hiya, MP #415170/chrony review done. Some questions sent your way. :)
[11:04] <cpaelzer> thanks utkarsh2102 having a look
[11:10] <cpaelzer> utkarsh2102: answered
[11:10] <utkarsh2102> danke, taking a look
[11:46] <cpaelzer> utkarsh2102: if you are still looking for MRs this one just got ready https://code.launchpad.net/~paelzer/ubuntu/+source/open-vm-tools/+git/open-vm-tools/+merge/415183
[11:46] <cpaelzer> paride: ^^ that would be the next try to switch to fuse3 hoping for no conflicts at image build this time :-)
[11:51] <paride> cpaelzer, utkarsh2102 I can review that open-vm-tools one
[11:55] <cpaelzer> thank you paride
[12:03] <paride> cpaelzer, done
[12:03] <ahasenack> good morning
[12:04] <mirespace_> hi ahasenack
[12:04] <cpaelzer> hi ahasenack
[12:04] <ahasenack> hello
[12:05] <paride> o/
[12:34] <ahasenack> utkarsh2102: thanks for all the reviews!
[12:36] <utkarsh2102> ahasenack: yay, you're welcome! \o/
[13:09] <coreycb> frickler: thanks for that, yes we are at python 3.10 in jammy
[13:23] <frickler> coreycb: oh, has the default already been changed? last time I looked it was still 3.9 and using 3.10 had some weird issues with pip
[13:24] <coreycb> frickler: it doesn't look like it has changed but I think that is the plan
[13:31] <frickler> coreycb: according to https://discourse.ubuntu.com/t/jammy-jellyfish-release-schedule/23906 it was planned for mid January, but this doesn't look promising to me https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#python3-defaults
[13:32] <utkarsh2102> sergiodj: hey, can you take a look at LP: #1959581, please?
[13:32] <utkarsh2102> it's an interesting bug and I am not sure what more I/we can do about this.
[13:32] <ahasenack> frickler: 3.10 is the default in jammy-proposed, it's currently going through the migration process. Some packages are still failing tests with it
[13:33] <ahasenack> frickler: check https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#python3-defaults for the list of "reds"
[13:33] <ahasenack> ops, which you know already
[13:33] <ahasenack> sorry
[13:33] <frickler> ahasenack: yes, the python3-pip failure matches what I'm seeing locally
[13:33] <ahasenack> frickler: check my ubuntu-devel "+1 maintenance" report, where I solved many of those reds
[13:34] <ahasenack> pip3, is that the one where it didn't find the packages in /usr/local?
[13:34] <ahasenack> in the test failure
[13:34] <frickler> ahasenack: yes
[13:34] <ahasenack> yeah, I looked briefly at that yesterday, and just confirmed it, but no clue what's going on
[13:34] <frickler> ahasenack: or rather, it seems to install things into /usr/lib, but doesn't find them there are installing
[13:35] <ahasenack> my maintenance shift ended, someone will have to look at that this week
[15:20] <peto> hi, please help, i have webserver apache2 on my server, from pc in local lan, i can connect to the server/website, but from android did not work (cant connect) - it worked, but now i dont know why it isnt working, same network --- nobody can help me?
[15:21] <peto> i find out that im not listening to port 80 on tcp
[15:21] <utkarsh2102> peto: you probably need to be more specific. What's not working. What error message d'you get. 
[15:23] <peto> on adroid browser i became error, that i cant connect , site is not reachable or busy (or sometning else, dont know to exactly wording in english, sorry)
[15:23] <peto> but the site, with IP 172.16.. work on pc, so I dont understand
[15:25] <peto> apache2 service is running
[15:26] <peto> https://termbin.com/aw4g
[15:46] <ahasenack> maybe your android is on 3g/4g instead of the wifi your pc is connected to? Looks like a private address
[15:50] <peto> android is on the same wifi
[15:50] <peto> but i know it works, but now no more, and i dont know why
[15:51] <sergiodj> utkarsh2102: hey, sure.  but TBH I don't know if there's much more we can there...
[15:51] <utkarsh2102> sergiodj: oh cool, if that's what you think, then we're probably on the same page.
[15:52] <utkarsh2102> I wasn't sure about my last comment, so I'd like you to double check and see if that's not entirely stupid. :)
[15:52] <sergiodj> but thanks for the heads up, I will take another look later today and see if I can come up with something
[15:52] <utkarsh2102> great, thank you! I mentioned this in my triage report, too.
[15:53] <sergiodj> cool, thanks :)
[20:25] <ahasenack> huh, I managed to break networking in a jammy VM I was using :/
[20:25] <ahasenack> the network interface doesn't even show up anymore
[20:27] <ChmEarl> ahasenack, biosdevice naming scheme?
[20:27] <ahasenack> no, didn't mess with that
[20:28] <ahasenack> I now plugged in a normal "e1000" nic (via virt-manager), but the vm just does not react
[20:30] <ahasenack> oh, udev got removed
[20:30] <ahasenack> that's bad
[20:32] <ahasenack> I guess I didn't pay too much attention in one of the dist-upgrades I did
[20:32] <ahasenack> oh well, nothing but a test vm
[20:56] <mwhudson> eh apt really shouldn't remove a priority important package wihtout making a fuss, i thought
[21:01] <ahasenack> I'm unsure what happened, I saw dpkg logs showing these removals
[21:01] <ahasenack> but not what triggered them
[21:30] <mwhudson> apt has logs too? but i'm not quite sure what the intended behaviour is
[22:03] <JanC> the logs should show what other packages were involved in that dist-upgrade, which should at least give you an idea about what might have caused it...
[22:04] <JanC> and when you don't have udev, it should still be possible to reload the kernel module to get networking again