[00:01] tomreyn: now I got 10 gbit link switch and fileserver :) [00:01] i am happy for you. === gry is now known as Sveta [03:16] i have been running a debian server for the last month. 1st time [03:17] think i will switch to ubuntu. everything from debian should also work in ubuntu right? [03:18] debian stuff seems really old and i read they don't update apps for years [03:18] !latest [03:18] Packages in Ubuntu may not be the latest. Ubuntu aims for stability, so "latest" may not be a good idea. Post-release updates are only considered if they are fixes for security vulnerabilities, high impact bug fixes, or unintrusive bug fixes with substantial benefit. See also !backports, !sru, and !ppa. [03:19] so ubuntu does the same thing? [03:21] yes, for the very most part, stability is preferred over adding new features within a release, too. [03:21] of course, you can do release upgrades, thus get newer versions. [03:22] on a server, stability is usually very relevant. [03:23] you don't want this business critical web application to fail because a minor backwards incompatible change to the webserver was introduced in its newer version. [03:27] i see. I am just using it for media. better to just leave it the way it is then === lotuspsychje__ is now known as lotuspsychje [07:10] Good morning [08:42] beisner, coreycb: hi. Im wondering why sometimes I have a failures on my dev zone with e.g. multiattach and I see that package for Queens cloud archive and Bionic as well are old. Last available packages there is 9.1.1 but as I see https://releases.openstack.org/queens/ it should be 10.1.0. Could you build new package or it will be a problem :> ? [12:49] dpawlik: it's very unusual for upstream (and ubuntu as well) to jump to a new major release for a stable branch. i found some history on the upstream change: https://github.com/openstack/requirements/commit/66a2b0617c3eacd21726c35a556c2a2620a4b91b [12:51] coreycb: he probably didn't see your reply [12:51] coreycb: (also isn't the cloud archive pulling in new openstacks periodically as part of what it is?) [12:51] sarnold: ah thanks :) [12:53] sarnold: yes, but similar to stable ubuntu releases, we generally just try to just do bug fixes to maintain stability [12:54] sarnold: but yes to your point we have new releases coming out every 6 months [12:57] heh, this suggests we shold already have stein in cloud archive.. https://wiki.ubuntu.com/OpenStack/CloudArchive [13:14] Can anyone help me with flatpak and ubuntu server ? I did: apt install -y --no-install-recommends lightdm flatpak xorg If I run export DISPLAY=:0 ; flatpak run tv.kodi.Kodi ... its says Invalid MIT-MAGIC-COOKIE-1 keyxcb_connection_has_error() returned true. Its related to x11 auth,right? [13:15] muhaha: Yes, I believe you need to do something with xauth, but it's been a long time since I did something like this so I can't remember any other details. [13:24] did you use ssh -X to ocnnect? [13:37] What I did https://pastebin.com/GcPp2drE [13:38] I am getting now No protocol specified xcb_connection_has_error() returned true [13:38] did you connect to your server using ssh -X? or just ssh? [13:38] ssh [13:39] I dont need to forward X11 [13:39] Doesn't Kodi need X? [13:40] It does [13:40] muhaha: What are you trying to achieve, I think there's some confusion. :) [13:41] On server A which has GPU and HDMI output install xorg and run kodi in flatpak [13:41] And have it output on the screen attached to the GPU? [13:41] exactly [13:42] Ah, is xorg running on that display? [13:42] yes. ps -ef | grep [x]org root 1595 614 0 02:05 tty7 00:00:00 /usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [13:43] Essentially you need to direct Kodie to the right display via `DISPLAY=: flatpak run tv.kodi.Kodi`. [13:44] 14:37 What I did https://pastebin.com/GcPp2drE [13:44] I think you may be able to get the rest of the way with XAUTHORITY=/path/to/.Xauthority [13:47] but its running under root [13:47] *present [13:48] So I will have to generate Xauthority for kodi user, right ? [13:49] but xhost + kodi should help, right? [13:50] or set the root file to be readable by kodi [13:54] xhost +si:localuser:kodi should do the trick I guess === cpaelzer_ is now known as cpaelzer [18:41] Well I created question... https://superuser.com/questions/1407474/run-kodi-on-ubuntu-bionic-server-with-flatpak [18:41] Lulz === gry is now known as Sveta [21:00] I'm trying to install a particular version of a package, but it seems to be tied to other dependencies that want to install the latest version of the packages [21:00] is there a way to tell Ubuntu to install all these packages for this 1 version so that it doesn't complain? [21:02] DammitJim, not sure what you mean. Perhaps doing an 'apt update' will fix the problem? [21:02] I already did apt update [21:03] so, if I was to run apt dist-upgrade, all my erlang packages would upgrade to version 21.2 [21:03] I am trying to only go to version 21.1 [21:04] erlang? Normally when people use a programming language, and need a very specific version, there is language-specific tooling for that. [21:04] eg python virtualenvs, haskell stack, etc [21:05] looks like you have third party sources which ship upgrades instead of security / bufg fixes [21:06] if you insist on using them and are happy with software getting outdated and *not patched*, you can do apt pinning [21:07] DammitJim: ^ [21:07] I tried using apt-mark hold erlang but that messed me up [21:07] it caused other packages to get uninstalled [21:09] that can happen [21:17] can I pin erlang* to a specific version? [21:21] this and it's dependencies which come from this 3rd party repo, yes [21:28] got it [21:28] thanks [21:32] the better approach would be to find a trustable and reliable apt source which gives you maintained (regularly patched) static upstream versions, maybe making multiple versions installable next to one another. [21:33] but idk whether such exists for erlang. you could mabe provide it as a service to the community. [21:37] yeah, they don't have that [21:37] this is temporary [21:37] I just need to get to a certain version to be "supported" [21:41] this sounds like a chroot or VM use case [21:41] * or container