[06:15] <lotuspsychje> archive updates success
[06:16] <lotuspsychje> just the network-manager bug not yet resolved
[06:27] <lotuspsychje> update-manager gui is gone now
[06:48] <rfm> I'm worried about this big instability only a month before an LTS release...
[06:50] <rfm> otoh its mostly the time_t stuff which wouldn't bother most ubuntu users since we abandoned 32 bit so long aga
[06:51] <mandem0110> rfm: very concerning, yes!
[06:54] <lotuspsychje> still no gnome46 yet either
[06:56] <rfm> If I were running this release I'd put i
[06:56] <rfm> t off for a month
[06:58] <lotuspsychje> well a lot of changes are upcoming
[06:58] <lotuspsychje> at the same time
[06:58] <lotuspsychje> so testers agree breakage is possible in devel stage
[07:00] <rfm> yeah, if it were February for an April release I wouldn't worry.  But it's late March!
[07:01] <lotuspsychje> there will always be bugs around, even after .1
[07:02] <lotuspsychje> and we got a mix of ubuntu devs, snap devs and gnome upstream these days
[07:02] <lotuspsychje> so its coming from all sides
[07:07] <rfm> just so scary to have this much change coming in so late for a LTS. \\
[07:07] <lotuspsychje> its much indeed
[07:08] <lotuspsychje> but then every LTS has new candy :p
[07:08] <lotuspsychje> or every release
[07:17] <rfm> I used to be paid to make these calls for Solaris. Glad I'm no longer in the loop.  Certanly  noble is working for me if I don't do full-upgrade
[07:18] <lotuspsychje> i just did a lot of archive updates
[07:18] <lotuspsychje> just ubuntu-desktop and network-manager etc packages need to be fixed
[07:19] <lotuspsychje> pretty sure today we will get more stuff
[07:22] <lotuspsychje> gnome applications button is now ubuntu logo circle
[07:25] <rfm> It  would be nice if the release team would put up a flare saying "ok now, anything busted should be reported
[07:25] <lotuspsychje> we got an #ubuntu-bugs-announce if you like
[07:26] <lotuspsychje> and #ubuntu-release for deeper dev talk about packages releases
[07:27] <lotuspsychje> and yesterday ogra_ also warned us with the devel mailing list in this channel
[07:27] <mandem0110> rfm: delay it tho and people will moan. But people will moan with a buggy release too! CAN NOT WIN.
[07:34] <rfm> mandem0110, beieve me I understand the can't win! Let's just hope the last burst of change is it. 
[07:44] <rfm> and I think I should just install the beta (instead of the system I created from the earliest daily and upgraded along)
[07:48] <lotuspsychje> it will result to the same rfm
[09:03] <Habbie> libboost-all-dev started conflicting with libssl3 (likely indirectly) somewhere in the last 30 hours
[09:03] <Habbie> does anybody happen to know where and why exactly?
[09:03] <Habbie> (i can dig in myself later, but it feels like something somebody might know)
[09:03] <Habbie> it pulls in libssl3t64 now
[09:04] <elhoir> hello folks
[09:05] <elhoir> i have still dependencies problem when updating mesa.... is migration still ongoing?
[09:06] <Habbie> elhoir, hi! what migration? t64? i suspect my trouble is related
[09:06] <elhoir> https://pastebin.com/BEA2xRyA
[09:06] <Habbie> ack
[09:06] <elhoir> Habbie, yes i think its "t64" related
[09:07] <elhoir> but the point is, packages are in place... i dont know why apt does not download and install them
[09:13] <lotuspsychje> ok seems like everything is back resolved for me on noble
[09:14] <Habbie> that was quick
[09:14]  * Habbie hits rebuild
[09:14] <lotuspsychje> had to install ubuntu-desktop
[09:14] <elhoir> not for me :-/
[09:15]  * elhoir needs some help
[09:15] <lotuspsychje> dpaste your apt errors elhoir 
[09:16] <elhoir> i did ---> https://pastebin.com/BEA2xRyA
[09:19] <lotuspsychje> elhoir: did you sudo apt update && sudo apt full-upgrade ?
[09:20] <elhoir> yes, but it complains about "missing dependencies"
[09:20] <Habbie> ah, my build works now
[09:20] <elhoir> i installed manually mesa packages, viadpkg... maybe that was my problem
[09:20] <elhoir> via dpkg
[09:22] <lotuspsychje> elhoir: did you add external ppas?
[09:22] <elhoir> https://pastebin.com/A00p7T0M
[09:23] <elhoir> lotuspsychje, yes, why?
[09:24] <lotuspsychje> revert them back to the original ubuntu sources
[09:24] <lotuspsychje> the volunteers cant help with external ppa's and often they get mixed up with ubuntus packages and result to dependency hell
[09:25] <elhoir> and how can i know the guilty ppa/package/app?
[09:26] <lotuspsychje> apt gives errors around mesa, so i assume mesa ppa?
[09:28] <elhoir> the ppa for mesa i have enabled is kisak stable for noble, which does not exist yet, so that is not the problem  for sure
[09:28] <elhoir> https://pastebin.com/GnQ8TYKg
[09:29] <lotuspsychje> lotuspsychje> revert them back to the original ubuntu sources
[09:32] <elhoir> okay, kisak ppa disabled
[09:37] <elhoir> nothing different
[09:38] <lotuspsychje> elhoir: did you sudo apt update && sudo apt full-upgrade , again?
[09:38] <elhoir> sayes
[09:39] <elhoir> yes... but i cant upgrade nor full-upgrade because of those broken dependencies
[09:40] <lotuspsychje> then the packages are not succesfully removed from the ppa
[09:40] <lotuspsychje> !ppapurge
[09:42] <elhoir> ubottu, packages are original ubuntu ones :-P
[09:54] <elhoir> i dont know where is the problem
[10:00] <RikMills> you are using a mirror for the ubuntu archive, so maybe that mirror hasn't caught up with the latest mass main archive changes yet
[10:03] <elhoir> okay, i`ll change now to the main server
[10:13] <elhoir> RikMills, didnt resolve the problem :(
[10:37] <elhoir> can anyone help me please? i need mesa drivers to boot ubuntu correctly
[10:38] <elhoir> glxinfo says they are already installed but i dont trust it... because of those dependencies...
[10:52] <elhoir> https://pastebin.com/2FaAZM2z --- i'm running in safe mode because of the fu**** mesa bug
[10:52] <elhoir> thats why i do need to full-upgrade system
[10:55] <elhoir> lotuspsychje, any other idea?
[10:55] <elhoir> RikMills, ?
[11:15] <tomreyn> have you tried a stable ubuntu release? you're more likely to get volunteer support there
[11:15] <tomreyn> also less likely to run into malfunctions
[11:25] <elhoir> tomreyn, too late, im using 24.04-dev for months xd
[11:27] <tomreyn> elhoir: it's good to help out testing future releases. i'm just saying - if you need more support, then maybe it's worth considering not to run pre-release versions.
[14:27] <lotuspsychje> i cant resize terminator window anymore, gnome terminal still works, if anyone wants to test
[14:27] <lotuspsychje> terminator version 2.1.3-1
[14:29] <elhoir> tomreyn so do you think i should fill a bug report against mesa package?
[14:29] <elhoir> perhaps filla question instead?
[14:29] <elhoir> fill a*
[14:29] <elhoir> in launchpad, i mean
[14:31] <elhoir> ah, no! its fixed at last!! :D
[14:32] <lotuspsychje> what did you do elhoir 
[14:33] <elhoir> well.. kind of... lots of packages removed...
[14:33] <elhoir> just sudo apt update && sudo apt -f install
[14:35] <elhoir> lotuspsychje, https://pastebin.com/gWzASf05
[15:02] <elhoir> lotuspsychje, this must be fixed first, before i do an upgrade ---> https://pastebin.com/9p8KfwcE
[15:41] <ChmEarl> are there still about 100 t64 libs in proposed universe/main to migrate?
[15:48] <schopin> yesterday big migration was about the core components, packages that were blocking stuff that was needed for the beta images.
[15:49] <schopin> There are still stragglers but they should migrate organically. We still have a few libraries that haven't start their transition, e.g. libevent
[15:50] <ChmEarl> schopin, ty, did a time64 build of xen-4.18.1, installed the Noble dom0, have it booted up OK
[18:05] <ChmEarl> tried to debootstrap v1.0.134 noble from bookworm, failed: libtirpc3t64:amd64 is at fault
[18:05] <ChmEarl> but mmdebstrap still works
[18:06] <arraybolt3> ravage: any clue why Matrix went down?
[18:19] <arraybolt3> Also, @room A compromized liblzma ended up in the Noble archive for about a month. We're only learning about it today. If you use Noble in production, you may want to treat your 24.04 installations as compromised.
[18:19] <Habbie> arraybolt3, in proposed, right?
[18:20] <arraybolt3> Unsure, but it could have potentially affected other built software packages according to the devs in #ubuntu-release.
[18:20] <Habbie> right
[18:20] <Habbie> fair to assume compromise
[18:20] <arraybolt3> yep, that's what I'm currently doing.
[18:21] <arraybolt3> Which is a mess, it means I get to reset my passwords, change my SSH and GPG keys, etc., etc., blah
[18:21] <Habbie> ugh
[18:21] <arraybolt3> guess today is going to be a "does Aaron's disaster recovery actually work right" day
[18:25] <elhoir> wtf
[18:25] <elhoir> such serious problems for a LTS release
[18:29] <arraybolt3> 24.04 isn't released yet.
[18:30] <arraybolt3> This is still in the development release. Trouble is that some of us use the development release for real work, mostly the Ubuntu developers themselves.
[18:30] <arraybolt3> Anyway I just nuked my SSH keys from anything important and revoked my GPG key, so I should be on the road to recovery.
[18:30] <arraybolt3> I'll probably be going through and systematically changing all my passwords next, ugh
[18:48] <elhoir> arraybolt3, :)
[18:48] <elhoir> well i dont use it for anything serious, but i dont like current situation. BUT, i can help with anything you need, but coding 
[19:58] <ChmEarl> noble: xz-utils       5.4.5-0.3
[20:08] <arraybolt3> The problem (as I understand it) is that other software has been built against the backdoored liblzma, and due to the way the backdoor worked it could have backdoored additional applications, sort of a "virus that spreads at build time".
[20:08] <arraybolt3> We don't know how bad it is or exactly how it works yet, we just know that it's happening and it's bad. It mostly looks like an SSH backdoor, but there's the possibility it does more.
[20:08] <arraybolt3> ChmEarl: ^
[20:08] <arraybolt3> (so there could be software in -release backdoored by the package that never made it out of -proposed)
[20:09] <ChmEarl> ty, going to check my netstat