Blueking | tomreyn: now I got 10 gbit link switch and fileserver :) | 00:01 |
---|---|---|
tomreyn | i am happy for you. | 00:01 |
=== gry is now known as Sveta | ||
Marz | i have been running a debian server for the last month. 1st time | 03:16 |
Marz | think i will switch to ubuntu. everything from debian should also work in ubuntu right? | 03:17 |
Marz | debian stuff seems really old and i read they don't update apps for years | 03:18 |
tomreyn | !latest | 03:18 |
ubottu | 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:18 |
Marz | so ubuntu does the same thing? | 03:19 |
tomreyn | yes, for the very most part, stability is preferred over adding new features within a release, too. | 03:21 |
tomreyn | of course, you can do release upgrades, thus get newer versions. | 03:21 |
tomreyn | on a server, stability is usually very relevant. | 03:22 |
tomreyn | 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:23 |
Marz | i see. I am just using it for media. better to just leave it the way it is then | 03:27 |
=== lotuspsychje__ is now known as lotuspsychje | ||
lordievader | Good morning | 07:10 |
dpawlik | 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 :> ? | 08:42 |
coreycb | 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:49 |
sarnold | coreycb: he probably didn't see your reply | 12:51 |
sarnold | coreycb: (also isn't the cloud archive pulling in new openstacks periodically as part of what it is?) | 12:51 |
coreycb | sarnold: ah thanks :) | 12:51 |
coreycb | sarnold: yes, but similar to stable ubuntu releases, we generally just try to just do bug fixes to maintain stability | 12:53 |
coreycb | sarnold: but yes to your point we have new releases coming out every 6 months | 12:54 |
sarnold | heh, this suggests we shold already have stein in cloud archive.. https://wiki.ubuntu.com/OpenStack/CloudArchive | 12:57 |
muhaha | 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:14 |
Odd_Bloke | 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:15 |
sarnold | did you use ssh -X to ocnnect? | 13:24 |
muhaha | What I did https://pastebin.com/GcPp2drE | 13:37 |
muhaha | I am getting now No protocol specified xcb_connection_has_error() returned true | 13:38 |
sarnold | did you connect to your server using ssh -X? or just ssh? | 13:38 |
muhaha | ssh | 13:38 |
muhaha | I dont need to forward X11 | 13:39 |
lordievader | Doesn't Kodi need X? | 13:39 |
muhaha | It does | 13:40 |
Odd_Bloke | muhaha: What are you trying to achieve, I think there's some confusion. :) | 13:40 |
muhaha | On server A which has GPU and HDMI output install xorg and run kodi in flatpak | 13:41 |
Odd_Bloke | And have it output on the screen attached to the GPU? | 13:41 |
muhaha | exactly | 13:41 |
lordievader | Ah, is xorg running on that display? | 13:42 |
muhaha | 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:42 |
lordievader | Essentially you need to direct Kodie to the right display via `DISPLAY=:<some-display> flatpak run tv.kodi.Kodi`. | 13:43 |
muhaha | 14:37 <muhaha> What I did https://pastebin.com/GcPp2drE | 13:44 |
sarnold | I think you may be able to get the rest of the way with XAUTHORITY=/path/to/.Xauthority | 13:44 |
muhaha | but its running under root | 13:47 |
muhaha | *present | 13:47 |
muhaha | So I will have to generate Xauthority for kodi user, right ? | 13:48 |
muhaha | but xhost + kodi should help, right? | 13:49 |
sarnold | or set the root file to be readable by kodi | 13:50 |
muhaha | xhost +si:localuser:kodi should do the trick I guess | 13:54 |
=== cpaelzer_ is now known as cpaelzer | ||
muhaha | Well I created question... https://superuser.com/questions/1407474/run-kodi-on-ubuntu-bionic-server-with-flatpak | 18:41 |
muhaha | Lulz | 18:41 |
=== gry is now known as Sveta | ||
DammitJim | 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 |
DammitJim | is there a way to tell Ubuntu to install all these packages for this 1 version so that it doesn't complain? | 21:00 |
lordcirth__ | DammitJim, not sure what you mean. Perhaps doing an 'apt update' will fix the problem? | 21:02 |
DammitJim | I already did apt update | 21:02 |
DammitJim | so, if I was to run apt dist-upgrade, all my erlang packages would upgrade to version 21.2 | 21:03 |
DammitJim | I am trying to only go to version 21.1 | 21:03 |
lordcirth__ | erlang? Normally when people use a programming language, and need a very specific version, there is language-specific tooling for that. | 21:04 |
lordcirth__ | eg python virtualenvs, haskell stack, etc | 21:04 |
tomreyn | looks like you have third party sources which ship upgrades instead of security / bufg fixes | 21:05 |
tomreyn | if you insist on using them and are happy with software getting outdated and *not patched*, you can do apt pinning | 21:06 |
tomreyn | DammitJim: ^ | 21:07 |
DammitJim | I tried using apt-mark hold erlang but that messed me up | 21:07 |
DammitJim | it caused other packages to get uninstalled | 21:07 |
tomreyn | that can happen | 21:09 |
DammitJim | can I pin erlang* to a specific version? | 21:17 |
tomreyn | this and it's dependencies which come from this 3rd party repo, yes | 21:21 |
DammitJim | got it | 21:28 |
DammitJim | thanks | 21:28 |
tomreyn | 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:32 |
tomreyn | but idk whether such exists for erlang. you could mabe provide it as a service to the community. | 21:33 |
DammitJim | yeah, they don't have that | 21:37 |
DammitJim | this is temporary | 21:37 |
DammitJim | I just need to get to a certain version to be "supported" | 21:37 |
tomreyn | this sounds like a chroot or VM use case | 21:41 |
tomreyn | * or container | 21:41 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!