=== xispita is now known as Guest7998 === xispita_ is now known as xispita === pizzaiolo is now known as pizza [15:57] hi, I know that this may not be the best channel to ask for this but not sure where to go so maybe someone will have some ideas. So I'm checking the possibilities to use dropbear as a solution to allow me to unlock my server after reboot. There are some tutorials on the network but I can't find any information about how to properly configure networking for this. The thing is that I need to have vlan tag on it, any idea how to so [15:57] e this? [16:39] lolek: this should help: https://github.com/stcz/initramfs-tools-network-hook [16:41] man... this is great, thank you! [16:57] how do people build packages ? I don't understand how bugs like https://bugs.launchpad.net/bugs/1986775 can exist. [16:57] -ubottu:#ubuntu-server- Launchpad bug 1986775 in schroot (Ubuntu Kinetic) "schroot 1.6.12-2 incompatible with sbuild-launchpad-chroot" [High, Triaged] [16:58] I can justify myself not having built any packages since upgrading to Jammy, but i dont' understand how others didn't hit this earlier. what do peopple do for package builds ? [17:08] smoser, my pbuilder host for kinetic builds is Focal [17:08] I haven't had any issues building packages from trusty to jammy as of last week [17:11] yeah.. so you wont have issues unles you're using sbuild-launchpad-chroot to maange your chroots. but, what I don't understand is why people *don't* use that. but apparently they don't. [17:18] I rarely build binarypackages locally, normally I upload to launchpad [17:19] only for really odd things, or testing come custom patch only I expect to make use of [17:19] and I do all my builds inside a docker container so I don't see chroot being more helpful there [18:07] I don't use schroot, I either use a ppa, or a lxd container [18:16] I ran into problems with sbuild-launchpad-chroot years ago so switched away from it, and never returned. [18:16] (And now most of my package builds aren't against archive.u.c's current contents so it wouldn't work for me anyway. :p) [18:32] hi all. i have a strange network problem after i swaped the ssd with ubuntu-server from one computer to a new. ubuntu boots without any problem on the new server with the old ssd but when i try to ping a ip adress like 8.8.8.8 i get the error "Network Unreachable". I need somehow to reconfigure the whole network. How can i do this ? Searched on the internet but only found non working tips. [18:33] check /etc/netplan/*.yaml, see if the mac address of the old machine is in there [18:34] ahasenack: had only a install.yaml file and based on the tip i deleted all there [18:35] that's the network config what you just deleted [18:36] create a new one. If this is a server (not desktop), start with the first example from https://netplan.io/examples perhaps [18:36] that will use dhcp [18:36] okey yes is good [18:36] if you need static addressing, or something else, keep reading that examples page [18:36] one might suite you [18:41] ahasenack: yaaayy it works. thank you very much. [18:45] welcome :) [19:24] small question again. how can i set the cpu to performance in ubuntu-server ? google search suggest cpufrequtils but think this is outdated. [19:25] it the cpu guvernator set to performance should be preserved on reboots [19:31] linuxperia: I think the pstate stuff is the new hotness, but it's hard to keep track of all the different tools for managing cpu performance/power .. https://www.kernel.org/doc/Documentation/cpu-freq/ has a bunch of docs but lacks any sort of guidance [19:31] bryceh: rbasak: sarnold: nginx and 'We disable IPv6 on our servers so default config fubars automatic deployments' came up again. This time in Debian with an Ubuntu package version reference. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021393 [19:31] -ubottu:#ubuntu-server- Debian bug 1021393 in nginx-common "error in package nginx-common_1.18.0-6ubuntu14.2_all.deb for ubuntu 22.04 with default enabled site." [Normal, Open] [19:31] just as a for your awareness thing [19:31] linuxperia: there's probably something more useful on https://wiki.archlinux.org/title/CPU_frequency_scaling [19:32] bryceh: rbasak: debian-devel seems to agree with our original decision that 'default config' should work for 'default Debian' and not really diverge on that. [19:32] so we made the right call downstream here :p [19:33] teward: heh, what a confusing bug report all around [19:34] sarnold: yep, rejected because Ubuntu needs Ubuntu bugs, then they said "Well, it's not really an Ubuntu issue it's a Debian issue" and explained the same "We disable IPv6 completely" problem we had show up in Ubuntu bugs multiple times [19:34] stil rejected because "default should work for default installations which include v4 and v6" so [19:34] welcome to my double-pronged "no we're not changing the defaults for an end-user admin decision that can break stuff" responses xD [19:34] sarnold: tahnk you very much. will look into pstate [19:35] "if you change one setting you might have to change a second setting" [22:14] I love how ubuntu denys responsibility for debian while completely relying on it for technical depth and correctness [22:15] * feurig says all the while pushing ubuntu for the same reasons