[00:42] How do you start/stop networking on 18.10 server using CLI? [00:43] I'm using Netplan and the default networking services. [00:51] Secutor: why would you want to *stop* the networking [00:51] you can just reapply the net config with `sudo netplan apply` if you change it [00:51] i'm not aware of any real "shut it off" functionality out of the box with netplan [00:53] yeah you have to stop networkd and then down the interfaces manually i think [00:54] I have a script and want to ensure that there is no incoming network traffic for a few moments to do some work then re-enable networking. [00:56] I know I can install ifdown and some older tools but want to try to do things the more modern Ubuntu way if possible. === TJ_Remix is now known as TJ- [01:11] ip link set eth0 down [01:12] That'll just down the interface at the link layer. ip link set eth0 up to re-up it. [03:02] Thank you hyperlumic, that works. [06:15] good morning [09:40] I am trying to pin a package but man is the documentation confusing. Setting a high number in pin priority what does that do? "Pin: version 5.10*" will this match version 5.100? [09:51] a_ok: a single package? Are you sure you don't just want to put a hold on the package? What are you actually trying to achieve? [09:53] rbasak: I want to able to make sure a few packages are never upgraded to another major version. We use ansible to configure our servers so placing a file for each package is ideal [09:55] a_ok: how do you define "major version"? [09:57] a_ok: are you aware of Ubuntu's stable release update policy? See https://wiki.ubuntu.com/StableReleaseUpdates [09:57] In general Ubuntu doesn't do major version updates in stable releases. [09:57] rbasak: Sorry I meant semvers minor version. But patch version is ok [09:57] Packages in the archive don't necessarily follow "semver" for the package version strings themselves. [09:58] (though the general concept has been used in our ecosystem long before the semver people rediscovered it) [09:58] rbasak: Not relevant in this case. I need it. Semvers is used. Where other scheme is used I will create an appropriate pref file [09:59] a_ok: the problem is that I don't think there's any way to configure apt to break down the version string for differentiation for pinning purposes [09:59] a_ok: it's relevant because you need apt to do that but package version strings that apt use aren't defined to be "semver". [10:01] rbasak: So you mean that the package can just ommit the version or something? [10:01] I don't understand your question. What does "omit the version" mean? [10:02] When I say "Pin: version 2.1.*" Should it not be impossible for version that does not match that scheme to be installed? [10:02] If you're trying to configure apt to work around a broken third party apt repository upgrade policy, you're going to face a world of pain. [10:03] apt isn't designed around being able to do that. [10:03] Is there an wasy way to get to a package's bugs page on launchpad? I'm trying to get to git-ubuntu, but everything uses google search, which returns garbage [10:03] kstenerud: https://bugs.launchpad.net/usd-importer [10:03] It's not a package as such; it's an upstream package hosted at launchpad.net/usd-importer (name bad for historical reasons) [10:06] It's not a package as such; it's an upstream *project* hosted at launchpad.net/usd-importer (name bad for historical reasons) [10:06] Sorry [11:01] hello, in my bionic KVM VM, the hostname is reset to some old value on reboot [11:01] any idea where it is kept? (it's not in /etc) [11:24] oskie: in which environment do you run your VM? iirc cloud-init runs by default, so it may set the hostname and other parameters on boot [11:32] frickler: i had to update it with hostnamectl and mess with cloud init (preserve_hostname) [11:33] i guess hostnamectl stores it in some kind of binary format or other [15:22] rbasak: kstenerud: pad.lv/fb/usd-importer [15:23] works as well for srcpkgs [15:30] Does anyone know if spectre-meltdown-checker thats available for Ubuntu 18.04 can be obtained for 16.04? [15:30] I just tried it on 18.04 and its great [15:43] !info spectre-meltdown-checker xenial [15:43] Package spectre-meltdown-checker does not exist in xenial [15:43] !info spectre-meltdown-checker bionic [15:43] spectre-meltdown-checker (source: spectre-meltdown-checker): Spectre & Meltdown vulnerability/mitigation checker. In component universe, is optional. Version 0.37-1 (bionic), package size 29 kB, installed size 120 kB [15:43] shubjero: looks to not be available [15:58] nacc: yeah too bad, its pretty useful.. and all my hypervisors are running 16.04.. haha [15:58] i have one system on 18.04 and its not part of our compute fleet :) [15:59] actually here it is in a non-packaged version (fine) https://github.com/speed47/spectre-meltdown-checker === jdstrand_ is now known as jdstrand [17:17] ahasenack, cpaelzer, kstenerud: are we expecting any other transitions from the server team end? [17:17] I was going to email ubuntu-devel@ with an "upcoming transitions from the server team; let me know if you want us to hold" notice. [17:17] cpaelzer: should I include Ruby in that? [17:26] rbasak: maybe bind, but it's a small one [17:26] haven't checked if there is a soname bump yet, but there might be one in time for disco [17:27] OK [17:27] bind9 1:9.11.4+dfsg-3ubuntu5 -> 1:9.11.5+dfsg-1 [17:27] probably safe [17:36] ahasenack: would you want to mark that bug for samba as blocks-proposed or whatever the correct tag is to prevent it from migrating? [17:37] nacc: how does that work? [17:38] nacc: if I add the tag, and fix freeipa's test which would let samba pass, it won't pass? [17:38] s/pass/migrate/ [17:38] ahasenack: i am trying to remember, but i recall there is a tag that will prevent a package from migrating out of proposed [17:38] block-proposed does sound similar [17:38] er [17:38] familiar [17:39] * ahasenack reads https://wiki.ubuntu.com/ProposedMigration [17:39] ahasenack: https://bugs.launchpad.net/ubuntu/+source/ruby-autoparse/+bug/1754464 had it [17:39] Launchpad bug 1754464 in ruby-autoparse (Debian) "remove broken ruby srcpkgs due to ruby-defaults stuck in bionic-proposed" [Unknown,New] [17:39] "No bugs with the block-proposed tag are open against the package (this can be used to temporarily block a package on manual testing);" [17:40] nice [17:40] I added it [17:40] thanks [17:42] ahasenack: np, it's handy for cases like this [17:42] indeed [18:02] rbasak: ruby is coming once FTBFS are resolved [18:02] rbasak: but it is a minor version, so no rebuild wave planned [20:13] what is going on here? http://paste.debian.net/hidden/19a7c323/ [20:15] kinghat: normally ubuntu systems don't have root passwords [20:16] i have to actually be root to restart apache there? [20:17] or have sudo privs [20:17] i mean i gave it root password [20:17] im logged in as admin account [20:17] admin account ? [20:17] i only have one account [20:18] you should be your normal user and use sudo to launch root based commands [20:18] eg: "sudo systemctl restart apache" [20:18] i see what you mean [20:18] that also looks like your running a desktop [20:19] are you sure this is an ubuntu server install [20:19] ya [20:30] That auth thing is annoying. I'd much prefer if it just said "you need to use sudo" instead of reinventing the wheel [20:31] yes [20:43] heh i can predict what that pastebin says without opening it [20:44] :) [22:04] why would netplan not apply at boot ? [22:04] (server 18.10) [22:04] it doesn't need to [22:04] the inplace migration I made from fedora worked [22:05] except that I forgot to install lvm2 so lvm was missing in the initrd [22:05] there's a generator that runs at boot, same as the other systemd generators, so the config is written before networkd starts [22:05] and the second part was that netplan was never applying [22:05] I made my own config [22:05] (basic dhcp on one interface) [22:06] http://paste.alacon.org/45631 [22:06] I reverted to ifupdown for now [22:07] /etc/network/interfaces was empty [22:07] bjonnh: maybe the device doesn't have that name at the time networkd is starting, so you might need to match the device by MAC address for networkd to know exactly which one enp7s0f1 is [22:08] oh [22:08] so, like this: http://paste.alacon.org/45632 [22:08] just my guess, since that's pretty simple config [22:11] I called them id0 and id1 [22:11] lets see [22:26] would anyone know of an alternative much simpler version of freenas that can run on ubuntu with a gui to configure SFTP accounts quickly? [22:27] cyphermox: that was it [22:27] cyphermox: thanks