=== antonispgs8 is now known as antonispgs [01:18] Hi room. I'm reading, but feel like I haven't found quite the right documentation thus far. Situation: I have a host on jammy/22.04, and it's time to upgrade it. In the past, I would do this via `sudo do-release-upgrade`. But this presently reports: "Please install all available updates for your release before upgrading.". OK, no big deal... I run apt update && apt upgrade. But 22.04 has phased updates (which I'm a little less [01:18] familiar with), so I have a few of packages kept back. Could someone steer me in the right direction here? It doesn't seem like I should disable phased updates to do a release-upgrade. :question [01:29] at3560k: hi. i assume that (pending) phased updates should not prevent a release upgrade. so i'm guessing something else may be causing this. [01:29] at3560k: run sudo apt full-upgrade [01:30] sudo apt upgrade package1 package2 package3 [01:30] if this doesn't solve it, yet, then check or share do-release-upgrade' /var/log/release-ugprade/main.log (path from memory, may differ slightly) [01:32] ravage: is this a way to override phasing? [01:32] I'm hearing that I should manually upgrade my packages that are kept back by the phased installs? I don't want to debate with people helping me. But I think if I do apt install, then it will mark the phased packages as manually installed, even if I dno't need them in the future? [01:33] at3560k: hearing this where? [01:33] you can always apt-mark auto afterwards. [01:34] there is https://documentation.ubuntu.com/server/explanation/software/about-apt-upgrade-and-phased-updates/#can-i-apt-upgrade-the-individual-packages-and-should-i [01:34] Thanks tomreyn, that's the sort of thing I was wondering about. [01:35] All phased updates block a release upgrade [01:35] oh, they do? didn't know this (and this page dpesn't seem to mention it) [01:36] So I *should* manually take all the phased updates prior to performing a release-upgrade. apt full-upgrade doesn't seem to do that. But I can try to take them manually [01:36] Thank you both [01:36] The upgrader is not aware that phased updates exist [01:37] the page i pointed to recommends against overriding it, but doesn't say why. i guess i would just do it. [01:37] The general advice to 'wait' for phased updates to arrive felt like a contradiction if I wanted to perform a release-upgrade, but that explanation makes sense to me [01:37] It's related with reliability. that's why phased packages are phased. [01:39] It will just upgrade the packages yes [01:39] Does not matter if you do a full release upgrade after that anyway [01:40] TRU. [01:41] i guess someone needs to report a bug against do-release-upgrades to make it learn about handling phased updates [01:45] bug 2041707 [01:45] -ubottu:#ubuntu- Bug 2041707 in ubuntu-release-upgrader (Ubuntu) "Phased updates block release upgrades" [Undecided, Triaged] https://launchpad.net/bugs/2041707 === antonispgs8 is now known as antonispgs [02:34] meustation, most people never deal with FIPS. We have a requirement due to government or regulatory requirements for some of our customers. === tonsofpc1 is now known as tonsofpcs === mrpond0 is now known as mrpond === mrpond6 is now known as mrpond [04:28] samy1028, thanks for the clarification; I'd be nevertheless curious to know more about those releases. is there a dedicated page on the ubuntu website? === mrpond7 is now known as mrpond === mrpond0 is now known as mrpond [05:18] hello [05:18] CQ CQ [05:19] CQ CQ Romeo Echo Delta === tds2 is now known as tds === JanC is now known as Guest3945 [09:15] help! I got this while `apt upgrade`: https://imgur.com/JGBW3rZ.png ; lsblk output: https://0bin.xyz/FFM4AENLSYGAVEMMZ4PW23I2KU -- where should I install grub? [09:17] (I should have asked in #ubuntu-server, probably) [09:36] Exterminador: the physical disk your bios will look for a master boot record on. [09:36] probably one of sda..d [09:37] by the way... most systems nowadays boot in uefi mode [09:38] (not yours, apparently, using old BIOS + MBR booting) [09:40] blame OVH :D I guess it's safe to install GRUB in all of the RAID disks? [10:01] Exterminador: i don't know how you partitioned those, but likely so. [10:02] I didn't. it's how OVH deployed the dedicated server. [10:03] then i can only refer to them/their documentation/their support. or you could run fdisk -l against those disks, and see which partition table type they're using. [10:04] the MBR resides on the first 512 (or something) bytes of an MBR/DOS partitioned disk. GPT partition tables usually also reserve this space for backwards compatibility. [10:06] "fdisk -l" output: https://dpaste.com/BGB3N2JH4 [10:08] from the little I understand, installing in all disks will allow the system to boot even if one disk fails? [10:19] Exterminador: those disks (sda..d) have GPT partition tables, the newer type. i assume you can still install the MBR on these, but i think i have never done this, so better don't rely on me there. [10:21] a BIOS booting system will usually allow you to confgure a boot device order, where multiple boot devices can be tried to load the boot code from in the given order. [10:22] oyu have "bios boot" partitions for grub stage 2 on all disks, so this, too, matches the requirement to be able to install grub on those disks. but i still lack experience with this setup. [10:25] tomreyn: I'll just try to install it in all of them and see if any errors arise. thanks for your input :) [10:27] you're welcome, good luck, make sure your backups are current [10:31] there's not much data to lose. the only thing that I have more important is the WeeChat config, which is being pulled to my home PC every 4h :) [10:46] looks okay, I guess? https://dpaste.com/6U78CW6V4 [11:00] Hi all [11:15] Exterminador: looks fine to me, data was written. looks like you got bitten by (bios/i386-pc) grub loosing blocklist support. [11:17] I'll let it be like it is, then. once again, thank you :) [11:19] out of the box, Ubuntu does not allow you to hide desktop icons [11:19] it just lists ~/ [11:19] so my desktop is one big mess of files [11:19] and folders [11:20] have to install: gnome-shell-extension-prefs [11:20] there, you can hide desktop icons [11:20] which is insane to me [11:20] thanks === EriC^^96 is now known as EriC^ [13:49] test [13:50] we see you ufaufi it works === JanC is now known as Guest231 [14:58] hi. i'm using 25.04 on a rpi5. The banner when logging in says "Users logged in: 0" even though im logged in on 5 different ssh sessions at once. is this expected? [15:48] that banner isn't realtime iirc [15:48] and it may be looking at local users (tty) versus remote (pty) [15:48] I'm on 24.04 and have the same behaviour f451 [15:49] system is a headless rpi so it'll be all remote [15:49] no mouse/keybd/screen [15:51] NDMakesPickingNa: ahhh maybe it needs wtmpdb [15:53] huh if i run 'w' theres no tty type (the column is blank) [15:53] f451: if you execute /usr/bin/landscape-sysinfo does it report the correct #? [15:53] tnx ill try that, 1 sec [15:54] NDMakesPickingNa: yeah, same [15:54] ie no it's still at '0' [15:58] the /etc/landscape/client.conf is empty, hmm [15:58] interesting. My old 20.04 install reports the pty correctly in w, my debian bookworm reports it correctly, my ubuntu 22 LXC on the debian install reports w correctly, but my ubuntu 24.04 install has a blank for tty colum in w, but who reports it correctly. /usr/bin/landscape-sysinfo reports the correct # of users on that last machine too [15:59] maybe a bug eh [16:00] plausible [16:00] does who report it correctly on your system? [16:00] instead of w [16:04] ill try it [16:05] NDMakesPickingNa: who reports nothing at all [16:06] maybe it has to do with sshd config [16:08] UsePAM yes is set [16:08] hmm [16:10] what about who as root [16:10] ( sudo who ) [16:10] gotta step away from keyboard, good luck [16:20] ty :D [16:21] sudo who also returns nothing [16:32] pkjlw3 === mIRC-rockcavera2 is now known as oraculo === oraculo is now known as Guest7295 === JanC is now known as Guest3876 === neocharlesalt is now known as neocharles === catties is now known as bunnies === zareem52 is now known as zareem5 [20:51] I am looking for better documentation on snmpv3 on 24.04. [20:51] (BTW I am willing to make a named account.  Just got on, and it's been a decade since I used IRC) [20:53] Most of the snmpv3 stuff I've found is out of date for 24.04, has the wrong syntax information for 24.04 (for instance net-snmp-config on Ubuntu does not presently have -a nor -A switches) [20:54] or is otherwise incomplete or for the wrong platform. [20:55] There seems to be no good catalog of vocabulary.  When I  write out snmpwalk: [20:56] root@landicho:~# snmpwalk -v3 -a MD5 -A xenopassword1 -X xenopassword2 -l authNoPriv -u xeno localhost | wc -l [20:56] 29448 [20:56] I see lots of MIB and OID stuff which apparently only a hardware professional can interpret. [20:57] Also, I want to use this for my home LAN, and I just see stuff so far to set things up on a single host. [20:58] It seems particularly odd that so much is out there for net-snmp-config with -A and -a switches, but the script on my Ubuntu does not have these. === antonispgs2 is now known as antonispgs === leprechaun is now known as _Shawn_ === _Shawn_ is now known as Shawn_Pringle === Game11454227932 is now known as Game1145422793 === Guest7295 is now known as oraculo === dstein64- is now known as dstein64 === JanC is now known as Guest1951 === test230118 is now known as test230117