[01:09] <joto> good evening everyone
[01:09] <joto> I was wondering what Postgresql version would be included with 24.04 LTS?
[01:11] <oerheks> !info Postgresql noble
[01:11] <joto> thank you!
[01:11] <joto> good to know that'll be on 16
[01:11] <joto> I'm on 15 now :)
[01:13] <oerheks> great, read the releasenotes for changes
[01:13] <oerheks> https://blueprints.launchpad.net/ubuntu/noble/+source/postgresql-common/+changelog
[01:15] <joto> indeed, valuable info thank!
[09:22] <elhoir> THIS is where i wanted to post :P
[09:22] <lotuspsychje> !details
[09:23] <elhoir> sorry lotuspsychje 
[09:24] <lotuspsychje> ask your question with your !paste and wait for volunteers to help you
[09:28] <elhoir> "simple".... how to fix this ---> https://pastebin.com/DzgFDqmn
[09:29] <lotuspsychje> elhoir: thats the very same paste you shared yesterday, then told us you bypassed that
[09:30] <elhoir> yeah, and its filing now today again
[09:30] <elhoir> failing*
[09:30] <lotuspsychje> right..
[09:31] <elhoir> may be some software (i.e. skypeforlinux) that conflicts with some new "t64" packages?
[09:31] <elhoir> i dont know how to explain
[09:59] <RikMills> fyi, many packages in noble may be uninstallable for a while, as amd64 binaries that were built after the compromised xz-utils published are being deleted
[10:00] <lotuspsychje> allrighty, tnx RikMills 
[10:01] <RikMills> that will result in the candidate amd64 version in apt version mismatching with for example its arch:all dependency
[10:01] <RikMills> The following packages have unmet dependencies:
[10:01] <RikMills>  nmap : Depends: nmap-common (= 7.94+git20230807.3be01efb1+dfsg-3) but 7.94+git20230807.3be01efb1+dfsg-3build1 is to be installed
[10:03] <lotuspsychje> yep thats what im getting
[10:04] <RikMills> i.e. the 3build1 amd64 binary was deleted, so apt sees the -3 as candidate to install. but as the arch:all nmap common is still at 3build1, apt bails
[10:05] <RikMills> once that affects packages are rebuilt again this should go away
[10:05] <RikMills> not sure of an ETA for that
[10:06] <RikMills> also no idea if this will impact the beta as yet
[10:10] <lotuspsychje> ok RikMills tnx for the info
[10:23] <elhoir> will it affect finl release date?
[10:23] <elhoir> final*
[11:05] <RikMills> elhoir: can't say for now, but would hope not
[11:07] <elhoir> :-)
[11:07] <elhoir> ok thanks
[11:07] <elhoir> rik i have still facein troubles with the "t64"packages, is it still expected?
[11:07] <elhoir> facing*
[11:11] <elhoir> RikMills, 
[13:50] <BtbN> Is there some issue with the 24.04 repos at the moment? A bunch of packages like cmake or vim fail to install with dependency issues.
[13:50] <lotuspsychje> BtbN: https://dpaste.org/SFgtc
[13:50] <BtbN> hm, fun
[13:51] <BtbN> This grinds an entire CI infra to a halt right now
[13:51] <ravage> yoiu should not have any production CI tha depends on a pre-beta release 🙂
[13:51] <BtbN> Well, it comes out next month, and people want stuff to work on it on day one
[13:52] <lotuspsychje> one box for testing is good
[13:52] <ravage> not day one yet
[13:52] <ravage> so just stop the CI and wait
[13:52] <lotuspsychje> production, follow the LTS route and wait .1
[13:52] <BtbN> Yeah, that's not how users operate
[13:52] <ravage> you want packages for the release for sure
[13:52] <BtbN> You don't have working packages on day one, and users get angry
[13:53] <BtbN> I assume this is just a matter of waiting for a bunch of build-bots to do their thing, and then it'll work again?
[13:53] <ravage> right
[13:54] <RikMills> BtbN: more or less. archive admins etc are working on what needs to be done
[13:54] <ravage> https://launchpad.net/builders you can watch it build stuff live if you have nothing better to do
[13:55] <BtbN> Does not look all that busy on first glance :D
[13:56] <ravage> i dont think it is a good idea to block all workers for it
[13:56] <ravage> there is regular business going on there too
[13:56] <ravage> maybe they also have some own workers reserverd. i dont know 🙂
[13:57] <ravage> i usually just watch my snap builds there
[13:57] <RikMills> BtbN: rebuilds haven't started yet. admins are working on the list of what to rebuild
[13:58] <RikMills> plus one of the main guys driving that is on west coast US
[13:58] <RikMills> so is only just waking up probably
[13:58] <ravage> lets hope he is an early bird 😄
[13:59] <lotuspsychje> IT peepz all 24/7 birds :p
[13:59] <ravage> i love to sleep. but usually after staying up until 4 am
[14:00] <lotuspsychje> unless your server is borked, wont sleep too good :p
[14:00] <ravage> or my bot is misbehaving again 😄
[14:00] <lotuspsychje> lol
[14:00] <RikMills> best bet is probably to enjoy your Easter weekend and look at noble again after
[14:00] <lotuspsychje> yeah good idea
[14:01] <lotuspsychje> and watch out for a second exploit in april 1st
[14:01] <ravage> updates my 2 systems yesterday. they are in a good state. will wait a few days now
[14:01] <ravage> *updated
[14:02] <BtbN> work refused to pay me weekend + holiday emergency pay, so stuff is gonna sit there until tuesday
[14:02] <ravage> perfect 🙂
[14:02] <BtbN> Though I'm pretty sure we have nothing remotely bleeding edge enough to be majorly affected
[14:38] <tomreyn> vlm: try with plain http
[14:40] <vlm> tomreyn, thanks
[14:40] <vlm> thats is it worked when using http
[14:43] <tomreyn> vlm: apparently there is https://github.com/probonopd/zsync-curl for HTTPS support
[14:45] <tomreyn> but there are also gpg signed sha256sums at https://cdimage.ubuntu.com/daily-live/current/ so you don't strictly need those
[14:46] <vlm> tomreyn, im good i got it working with http, nifty program this i think,no active server requirement needed
[14:47] <tomreyn> you're welcome - i assumed you were using https in an attempt to ensure authenticity.
[14:48] <vlm> tomreyn, actually just copy pasted the link from documentation =)
[14:49] <tomreyn> right, i'm not sure why it says httpS there
[14:51] <vlm> just so happy i got it working, its easier to test those builds that are not released and update somewhat frequently then with this for of sync