[07:16] Good morning [08:58] Can I install ubuntu server from. The network install cd? [10:04] xrandr_mac: so long that you have network access during the installation, yes - I've used that a lot [10:38] any idea what to do when I try to make a package and I get this error? http://paste.debian.net/1074553/ [11:22] RoyK: is there a debian directory and it contains a changelog file? [11:28] supaman: there's a debian dir, but no changelog file, so I forged one and with a little trouble, it worked [11:28] great :-) [13:48] jamespage: sahid: i'm going to sweep up the remaining rc's for stein. i don't think there are many. [13:53] Hi. Installing ubuntu-server (bionic), I am only asked to configure the DNS server by the installer and not the rest of the network configuration (DHCP/static). [13:53] coreycb: ack, do you need some help? I can do some [13:53] I then have to edit the netplan configuration manually in the live system. [13:54] sahid: i think we're good, thanks. we can split up the final release when that comes around. [13:54] coreycb: ok sure we will do that :) [13:55] sahid: james has smoke tests passing on the current proposed packages so we'll re-run that and we'll need to manually test dashboards [14:01] coreycb: ta - just a few I think === _KaszpiR__ is now known as _KaszpiR_ === Wryhder is now known as Lucas_Gray === lotuspsychje__ is now known as lotuspsychje === kallesbar_ is now known as kallesbar [23:24] Trying to install latest ubuntu 18.04 LTS server on a VM and the installer crashes when I'm trying to set manual ipv4 address, starting the installer all over again :( [23:25] that sounds vaguely familiar [23:32] sveinse: probably bug 1816954 [23:32] bug 1816954 in subiquity (Ubuntu) "Unable to show Info nor Set static IP during install" [Undecided,Fix committed] https://launchpad.net/bugs/1816954 [23:46] hi, I ran into a problem I thought I solved but apparently did not. My boot partition is only 500mb and it has 0 bytes free. I was trying to do an upgrade and now I'm stuck [23:46] I see some guides saying I can boot from a different disc of linux and try to repartition the disk, but wanted to see if anyone thinks that's a terrible idea on here before I accidentally break something [23:47] Maxel: are you booted? [23:47] Maxel: It happened to me all the time on my old server. You probably have older kenels taking up all the space. uninstall them first, and then you can install the upgrade [23:47] I wouldn't go down that route, no.. [23:47] yeah, it's a vm I have [23:47] you should be able to remove some kernels [23:47] running on esxi [23:47] I'd just truncate some kernels with "> /boot/vmlinuz-...." -- pick old ones [23:47] then dpkg --purge that old version [23:47] I would like to solve the tiny boot partition eventually, but I need to free up some space first [23:48] what does dpkg -l linux-image-*-generic | grep ^ii show? [23:48] remind me what the util to pipe output to pastebin is? [23:48] pastebinit [23:49] http://paste.ubuntu.com/p/VWc835NQ4F/ [23:49] yes ok you probably don't need all of those :) [23:50] try to keep the newest one or two, and whatever kernel you're running now [23:50] I think I messed this up once though, what's the safe way to remove these? I just deleted the files and got myself in trouble [23:50] apt remove linux-image-4.4.0-134-generic [23:50] (for example) [23:51] like sarnold says probably best not to remove the kernel you are actually running [23:51] truncate one file with > /boot/vmlinuz-whatever ... to free up storage; then you can dpkg --purge the package that owned the file [23:51] just fill the file with 0 bytes you mean? [23:51] then upgrade to bionic where this kind of stuff doesn't pile up in the same way :) [23:52] (not necessarily helpful advice i realize) [23:52] Maxel: yes [23:52] well not fill the file [23:52] is that 18.04? cause that's what I was trying to actually do here [23:52] replace the file with a 0 byte file [23:52] Maxel: yes [23:52] ls -l [23:52] whoopsies [23:53] just cause I'm extra worried, so can I just do: echo "" > vmlinuz-4.4.0-128-generic [23:55] maybe; I've always used > filename to truncate files [23:55] using echo in that fashion may try to make a new directory entry and thus fail to allocate memory [23:55] no need to echo anything, just lead with the > [23:55] right [23:58] trying to purge the package now: dpkg: warning: ignoring request to remove vmlinuz-4.4.0-128-generic which isn't installed