Re: [DNG] Advice sought re: ejabberd
On Sun, Jul 18, 2021 at 12:42:15PM -0500, o1bigtenor via Dng wrote: > # less /var/log/ejabberd/error.log > 2021-07-18 09:43:36.985 [error] > <0.82.0>@ejabberd_config:validate_opts:1095 Unknown option 'echo > /lib > /etc/ld.so.conf.d/opensrf.confwhat' > 2021-07-18 09:43:36.985 [error] <0.82.0>@ejabberd_config:start:88 > Failed to load configuration file /etc/ejabberd/ejabberd.yml Looks like you have some junk (“echo /lib > /etc/ld.so.conf.d/opensrf.conf”) in /etc/ejabberd/ejabberd.yml config file. This is a part of install instructions: https://evergreen-ils.org/~bshum/OpenSRF-README.html#_adjust_the_system_dynamic_library_path but it should be executed, not put in ejabberd config. You need to clean this up. -- Tomasz Torcz “If you try to upissue this patchset I shall be seeking to...@pipebreaker.pl an IP-routable hand grenade.” — Andrew Morton (LKML) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Fwd: Installing postgresql13 on beowulf
> On 19 Jul 2021, at 09:59, Gregory Nowak wrote: > > On Sun, Jul 18, 2021 at 03:46:56PM +1000, wirelessduck--- via Dng wrote: >> Bionic is an Ubuntu release. You should be using buster-pgdg repository for >> postgresql apt as Devuan Beowulf is directly based on Debian Buster. Devuan >> has no direct relationship with Ubuntu. > > I don't recall seeing buster in the provided release output, which is > why I suggested using bionic. If buster is indeed present, and I > missed it, then buster should indeed be used. Apologies for the confusion. > > Greg Yes, they list all the supported releases on the page at https://apt.postgresql.org which redirects to the wiki at https://wiki.postgresql.org/wiki/Apt. For those who don’t know, they also distribute postgres extensions and related apps (eg. barman, pspg) and updated libpq/libpq-dev through pgdg apt repository. The one major exception being PgAdmin4, which switched to using its own apt repository. -- Tom___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Fwd: Installing postgresql13 on beowulf
On Sun, Jul 18, 2021 at 03:46:56PM +1000, wirelessduck--- via Dng wrote: > Bionic is an Ubuntu release. You should be using buster-pgdg repository for > postgresql apt as Devuan Beowulf is directly based on Debian Buster. Devuan > has no direct relationship with Ubuntu. I don't recall seeing buster in the provided release output, which is why I suggested using bionic. If buster is indeed present, and I missed it, then buster should indeed be used. Apologies for the confusion. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Advice sought re: ejabberd
On Sun, 2021-07-18 at 19:08 +0100, Marjorie Roome via Dng wrote: > On Sun, 2021-07-18 at 12:42 -0500, o1bigtenor via Dng wrote: > > On Sun, Jul 18, 2021 at 10:01 AM Antony Stone > > wrote: > > > On Sunday 18 July 2021 at 16:54:25, o1bigtenor via Dng wrote: > > > > > > > # service ejabberd start > > > > [] Starting ejabberd...:root@memyself:/home/opensrf-3.2.1# > > > > service > > > > ejabberd status > > > > [] Getting ejabberd status...:Failed RPC connection to the > > > > node > > > > ejabberd@localhost: nodedown > > > > > > > > Commands to start an ejabberd node: > > > > foreground Start an ejabberd node in server mode (attached) > > > > > > Did you try that one to see whether it gives you any extra > > > information as it's > > > trying to start? > > > > > > > Optional parameters when starting an ejabberd node: > > > > --logs dir Directory for logs: /var/log/ejabberd > > > > > > Have you looked in there for any additional details? > > > > > > > Hadn't even thought of looking there - - - - :-( !! > > # less /var/log/ejabberd/error.log > > 2021-07-18 09:43:36.985 [error] > > <0.82.0>@ejabberd_config:validate_opts:1095 Unknown option 'echo > > /lib > /etc/ld.so.conf.d/opensrf.confwhat' > > 2021-07-18 09:43:36.985 [error] <0.82.0>@ejabberd_config:start:88 > > Failed to load configuration file /etc/ejabberd/ejabberd.yml > > 2021-07-18 09:43:36.985 [critical] <0.82.0>@ejabberd_app:start:70 > > Failed to start ejabberd application: unknown_option > > > > # less /var/log/ejabberd/ejabberd.log > > 2021-07-18 09:43:36.455 [info] <0.82.0>@ejabberd_config:start:69 > > Loading configuration from /etc/ejabberd/ejabberd.yml > > 2021-07-18 09:43:36.985 [error] > > <0.82.0>@ejabberd_config:validate_opts:1095 Unknown option 'echo > > /lib > /etc/ld.so.conf.d/opensrf.confwhat' > > 2021-07-18 09:43:36.985 [error] <0.82.0>@ejabberd_config:start:88 > > Failed to load configuration file /etc/ejabberd/ejabberd.yml > > 2021-07-18 09:43:36.985 [critical] <0.82.0>@ejabberd_app:start:70 > > Failed to start ejabberd application: unknown_option > > > > So these log files are indicating that something is missing from > > the > > configuration file. > > That config file is a '. . . conf.d' file - - - I understand that > > Beowulf really doesn't use 'systemd' files. > > > > So how do I satisfy this lacuna? > > > Looks like the problem is in the (missing?) ejadderd configuration > files. > > There are lots of options. I'd expect the suitable defaults for > Evergreen would be provided by Evergreen. Obviously they aren't. > > For ejabberd you /could/ try looking here: > > https://docs.ejabberd.im/get-started/ > > But unless the Evergreen defaults are really basic you probably need > to search the Evergreen documentation. > > NB. I doubt if the problem is anything to do with systemd. > Had a look at the Evergreen docs - seems to be rather opaque about what is involved in using ejabberd. However the following discussion is about what seems to be the same RPC problem: https://www.ejabberd.im/node/938/index.html At least gives some ideas to try. -- Marjorie ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Advice sought re: ejabberd
o1bigtenor via Dng said on Sun, 18 Jul 2021 06:17:02 -0500 >Greetings > >I have, at least temporarily, abandoned installing 'Evergreen' - - >library software. > >Far too many books around here never mind a huge collection of papers >most often pdfs. > >The Evergreen 'system' uses ejabberd as a communication tool and it >would seem to me (new at digging under the hood as it were) that >ejabberd is quite intertwined into this system. > >Ejabberd was installed as part of the install but then in the setup >it is necessary to shut it off. >The install workflow used 'systemctl' etc etc as a control >I used 'service ejabberd stop' which worked but when I wanted to >restart the service the complaints started. > >Is there a simple way to change this reliance on systemd or is this >something better left to someone who does know what they're doing (not >me - - - grin!)? I don't understand the problem, and additionally, in certain respects I'm a "hammer is my one tool" type of guy, so to me everything looks like a nail. With those provisos, I have a suggestion: Use runit to control ejabberd. sv up ejabberd or sv down ejabberd or sv status ejabberd, etc. If you don't want to switch init systems just now, which would be completely understandable, you can put a respawn command for runsvdir (the runit supervisor program) in /etc/inittab, and then just add the ejabberd daemon to runit and disable the ejabberd daemon in sysvinit. Anyway... Now this could be slick. Create a shellscript called systemctl on your path. Your systemctl shellscript would parse its systemd-specific arguments and output them as sv commands for runit. I have a feeling all your ejabberd "systemctl" problems would instantly vanish. And as you're writing the shellscript, visualize what you're doing as kicking Poettering, FreeDesktop.org and Redhat right in the petunias. SteveT Steve Litt Spring 2021 featured book: Troubleshooting Techniques of the Successful Technologist http://www.troubleshooters.com/techniques ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Advice sought re: ejabberd
On Sun, 2021-07-18 at 12:42 -0500, o1bigtenor via Dng wrote: > On Sun, Jul 18, 2021 at 10:01 AM Antony Stone > wrote: > > On Sunday 18 July 2021 at 16:54:25, o1bigtenor via Dng wrote: > > > > > # service ejabberd start > > > [] Starting ejabberd...:root@memyself:/home/opensrf-3.2.1# > > > service > > > ejabberd status > > > [] Getting ejabberd status...:Failed RPC connection to the > > > node > > > ejabberd@localhost: nodedown > > > > > > Commands to start an ejabberd node: > > > foreground Start an ejabberd node in server mode (attached) > > > > Did you try that one to see whether it gives you any extra > > information as it's > > trying to start? > > > > > Optional parameters when starting an ejabberd node: > > > --logs dir Directory for logs: /var/log/ejabberd > > > > Have you looked in there for any additional details? > > > > Hadn't even thought of looking there - - - - :-( !! > # less /var/log/ejabberd/error.log > 2021-07-18 09:43:36.985 [error] > <0.82.0>@ejabberd_config:validate_opts:1095 Unknown option 'echo > /lib > /etc/ld.so.conf.d/opensrf.confwhat' > 2021-07-18 09:43:36.985 [error] <0.82.0>@ejabberd_config:start:88 > Failed to load configuration file /etc/ejabberd/ejabberd.yml > 2021-07-18 09:43:36.985 [critical] <0.82.0>@ejabberd_app:start:70 > Failed to start ejabberd application: unknown_option > > # less /var/log/ejabberd/ejabberd.log > 2021-07-18 09:43:36.455 [info] <0.82.0>@ejabberd_config:start:69 > Loading configuration from /etc/ejabberd/ejabberd.yml > 2021-07-18 09:43:36.985 [error] > <0.82.0>@ejabberd_config:validate_opts:1095 Unknown option 'echo > /lib > /etc/ld.so.conf.d/opensrf.confwhat' > 2021-07-18 09:43:36.985 [error] <0.82.0>@ejabberd_config:start:88 > Failed to load configuration file /etc/ejabberd/ejabberd.yml > 2021-07-18 09:43:36.985 [critical] <0.82.0>@ejabberd_app:start:70 > Failed to start ejabberd application: unknown_option > > So these log files are indicating that something is missing from the > configuration file. > That config file is a '. . . conf.d' file - - - I understand that > Beowulf really doesn't use 'systemd' files. > > So how do I satisfy this lacuna? > Looks like the problem is in the (missing?) ejadderd configuration files. There are lots of options. I'd expect the suitable defaults for Evergreen would be provided by Evergreen. Obviously they aren't. For ejabberd you /could/ try looking here: https://docs.ejabberd.im/get-started/ But unless the Evergreen defaults are really basic you probably need to search the Evergreen documentation. NB. I doubt if the problem is anything to do with systemd. -- Marjorie ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Advice sought re: ejabberd
On Sun, Jul 18, 2021 at 10:01 AM Antony Stone wrote: > > On Sunday 18 July 2021 at 16:54:25, o1bigtenor via Dng wrote: > > > # service ejabberd start > > [] Starting ejabberd...:root@memyself:/home/opensrf-3.2.1# service > > ejabberd status > > [] Getting ejabberd status...:Failed RPC connection to the node > > ejabberd@localhost: nodedown > > > > Commands to start an ejabberd node: > > > foreground Start an ejabberd node in server mode (attached) > > Did you try that one to see whether it gives you any extra information as it's > trying to start? > > > Optional parameters when starting an ejabberd node: > > --logs dir Directory for logs: /var/log/ejabberd > > Have you looked in there for any additional details? > Hadn't even thought of looking there - - - - :-( !! # less /var/log/ejabberd/error.log 2021-07-18 09:43:36.985 [error] <0.82.0>@ejabberd_config:validate_opts:1095 Unknown option 'echo /lib > /etc/ld.so.conf.d/opensrf.confwhat' 2021-07-18 09:43:36.985 [error] <0.82.0>@ejabberd_config:start:88 Failed to load configuration file /etc/ejabberd/ejabberd.yml 2021-07-18 09:43:36.985 [critical] <0.82.0>@ejabberd_app:start:70 Failed to start ejabberd application: unknown_option # less /var/log/ejabberd/ejabberd.log 2021-07-18 09:43:36.455 [info] <0.82.0>@ejabberd_config:start:69 Loading configuration from /etc/ejabberd/ejabberd.yml 2021-07-18 09:43:36.985 [error] <0.82.0>@ejabberd_config:validate_opts:1095 Unknown option 'echo /lib > /etc/ld.so.conf.d/opensrf.confwhat' 2021-07-18 09:43:36.985 [error] <0.82.0>@ejabberd_config:start:88 Failed to load configuration file /etc/ejabberd/ejabberd.yml 2021-07-18 09:43:36.985 [critical] <0.82.0>@ejabberd_app:start:70 Failed to start ejabberd application: unknown_option So these log files are indicating that something is missing from the configuration file. That config file is a '. . . conf.d' file - - - I understand that Beowulf really doesn't use 'systemd' files. So how do I satisfy this lacuna? TIA ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] deprecated options (Was: Refracta have a static IP)
Bernard Rosset via Dng wrote: >> Perhaps it's time for the relevant package to spit out some notice level >> logging when it hits deprecated options ? > > I can't imagine the volume of information that would produce on system > upgrades, even updates packs. > Unreadable, if you ask me: Too much information = No information, as it will > be discarded. No, I'm not talking about changelogs - which as you say tend to get very lengthy on a system upgrade and either ignored or are a pita to wade through, and for many users, much of what's in there isn't relevant to their use case. I'm talking about, as a service/daemon starts, then it spits out a warning notice **IFF** a deprecated option is encountered in the config. I've seen the latter many times, and it works - doesn't stop the service working, doesn't disappear in a gazzillion pages of changelogs that no-one reads (because a lot of the changelog isn't relevant to the user's use case) - but does provide a warning that the config needs re-visiting. Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Fwd: Installing postgresql13 on beowulf
> On 18 Jul 2021, at 21:08, o1bigtenor wrote: > > On Sun, Jul 18, 2021 at 5:58 AM wirelessduck--- via Dng > wrote: >> >> > snip I use the buster-pgdg repositories for all of my postgresql installations, following the instructions on apt.postgresql.org but substituting the lsb_release part for “buster” >>> >>> Thank you very much. >>> I did not understand that I was to use 'Buster' in place of 'lsb_release' . >>> >>> Using 'lsb_release' is what caused the foobar. >>> >>> Regards >> >> Yes that snippet is designed to make it easy to copy and paste so you they >> can provide one script to setup for all supported distros. As Devuan isn’t >> directly supported by pgdg repository we just have to make a small change to >> use the equivalent Debian release name. >> > > Dunno if I'm understanding correctly but when I use the actual 'name' > of the distribution then I would have to change such when that > distribution changes - - - yes? > > The generic statement would not need upgrading as I understand it. > > Deeply appreciating the sharing in this group!! Check the man page for lsb_release. https://manpages.debian.org/buster/lsb-release/lsb_release.1.en.html You will see that `lsb_release -cs` as used in the postgresql wiki page snippet just prints the running system distribution codename. In Debian, Ubuntu, and others directly supported by pgdg that will “autofill” in the codename into the shell script. As “beowulf” is not supported directly by pgdg, we just have to substitute in the equivalent Debian release codename instead of using the output of `lsb_release -cs`. -- Tom___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Advice sought re: ejabberd
On Sunday 18 July 2021 at 16:54:25, o1bigtenor via Dng wrote: > # service ejabberd start > [] Starting ejabberd...:root@memyself:/home/opensrf-3.2.1# service > ejabberd status > [] Getting ejabberd status...:Failed RPC connection to the node > ejabberd@localhost: nodedown > > Commands to start an ejabberd node: > foreground Start an ejabberd node in server mode (attached) Did you try that one to see whether it gives you any extra information as it's trying to start? > Optional parameters when starting an ejabberd node: > --logs dir Directory for logs: /var/log/ejabberd Have you looked in there for any additional details? Antony. -- My life is going completely according to plan. I do sometimes wish it had been *my* plan, though. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Advice sought re: ejabberd
On Sun, Jul 18, 2021 at 7:48 AM d...@d404.nl wrote: > > On 18-07-2021 13:17, o1bigtenor via Dng wrote: > > Greetings > > > > I have, at least temporarily, abandoned installing 'Evergreen' - - > > library software. > > > > Far too many books around here never mind a huge collection of papers > > most often pdfs. > > > > The Evergreen 'system' uses ejabberd as a communication tool and it > > would seem to me (new at digging under the hood as it were) that > > ejabberd is quite intertwined into this system. > > > > Ejabberd was installed as part of the install but then in the setup > > it is necessary to shut it off. > > The install workflow used 'systemctl' etc etc as a control > > I used 'service ejabberd stop' which worked but when I wanted to > > restart the service the complaints started. > > > > Is there a simple way to change this reliance on systemd or is this > > something better left to someone who does know what they're doing (not > > me - - - grin!)? > > > > TIA > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > Most likely you cannot do service ejabberd restart after a stop. You > have to use service ejabberd start > Otherwise you get a error/warning that no running service has been found > before starting the service. > # service ejabberd start [] Starting ejabberd...:root@memyself:/home/opensrf-3.2.1# service ejabberd status [] Getting ejabberd status...:Failed RPC connection to the node ejabberd@localhost: nodedown Commands to start an ejabberd node: start Start an ejabberd node in server mode debug Attach an interactive Erlang shell to a running ejabberd node iexdebug Attach an interactive Elixir shell to a running ejabberd node live Start an ejabberd node in live (interactive) mode iexliveStart an ejabberd node in live (interactive) mode, within an Elixir shell foreground Start an ejabberd node in server mode (attached) Optional parameters when starting an ejabberd node: --config-dir dir Config ejabberd:/etc/ejabberd --config file Config ejabberd:/etc/ejabberd/ejabberd.yml --ctl-config file Config ejabberdctl: /etc/ejabberd/ejabberdctl.cfg --logs dir Directory for logs: /var/log/ejabberd --spool dirDatabase spool dir: /var/lib/ejabberd --node nodenameejabberd node name: ejabberd@localhost To me this is a dead end - - - - perhaps someone can show me the path through? TIA ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Advice sought re: ejabberd
On 18-07-2021 13:17, o1bigtenor via Dng wrote: Greetings I have, at least temporarily, abandoned installing 'Evergreen' - - library software. Far too many books around here never mind a huge collection of papers most often pdfs. The Evergreen 'system' uses ejabberd as a communication tool and it would seem to me (new at digging under the hood as it were) that ejabberd is quite intertwined into this system. Ejabberd was installed as part of the install but then in the setup it is necessary to shut it off. The install workflow used 'systemctl' etc etc as a control I used 'service ejabberd stop' which worked but when I wanted to restart the service the complaints started. Is there a simple way to change this reliance on systemd or is this something better left to someone who does know what they're doing (not me - - - grin!)? TIA ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng Most likely you cannot do service ejabberd restart after a stop. You have to use service ejabberd start Otherwise you get a error/warning that no running service has been found before starting the service. Grtz Nick OpenPGP_signature Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Advice sought re: ejabberd
Hi o1bigtenor, On Sun, 2021-07-18 at 06:17 -0500, o1bigtenor via Dng wrote: > [snip] > The Evergreen 'system' uses ejabberd as a communication tool and it > would seem to me (new at digging under the hood as it were) that > ejabberd is quite intertwined into this system. > > Ejabberd was installed as part of the install but then in the setup > it is necessary to shut it off. > The install workflow used 'systemctl' etc etc as a control > I used 'service ejabberd stop' which worked but when I wanted to > restart the service the complaints started. > > Is there a simple way to change this reliance on systemd or is this > something better left to someone who does know what they're doing > (not me - - - grin!)? > Firstly what are the complaints? They may be diagnostic of what the problem is. ejabberd /is/ in the Devuan Beowulf repository and looking at the package depends it doesn't require systemd. If 'service ejabberd stop' works then I assume it has an /etc/init.d/ejabberd init file installed and that the stop command is working. Can you check that the init is set up correctly to enable/start it? It could be the LSB header is wrong (it's not unknown with systemd oriented packages even when they install an init). Also check the commands for 'service' in the init file. -- Marjorie ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Advice sought re: ejabberd
Greetings I have, at least temporarily, abandoned installing 'Evergreen' - - library software. Far too many books around here never mind a huge collection of papers most often pdfs. The Evergreen 'system' uses ejabberd as a communication tool and it would seem to me (new at digging under the hood as it were) that ejabberd is quite intertwined into this system. Ejabberd was installed as part of the install but then in the setup it is necessary to shut it off. The install workflow used 'systemctl' etc etc as a control I used 'service ejabberd stop' which worked but when I wanted to restart the service the complaints started. Is there a simple way to change this reliance on systemd or is this something better left to someone who does know what they're doing (not me - - - grin!)? TIA ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Fwd: Installing postgresql13 on beowulf
On Sun, Jul 18, 2021 at 5:58 AM wirelessduck--- via Dng wrote: > > snip > >> > >> I use the buster-pgdg repositories for all of my postgresql installations, > >> following the instructions on apt.postgresql.org but substituting the > >> lsb_release part for “buster” > >> > > > > Thank you very much. > > I did not understand that I was to use 'Buster' in place of 'lsb_release' . > > > > Using 'lsb_release' is what caused the foobar. > > > > Regards > > Yes that snippet is designed to make it easy to copy and paste so you they > can provide one script to setup for all supported distros. As Devuan isn’t > directly supported by pgdg repository we just have to make a small change to > use the equivalent Debian release name. > Dunno if I'm understanding correctly but when I use the actual 'name' of the distribution then I would have to change such when that distribution changes - - - yes? The generic statement would not need upgrading as I understand it. Deeply appreciating the sharing in this group!! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Fwd: Installing postgresql13 on beowulf
> On 18 Jul 2021, at 20:39, o1bigtenor wrote: > > On Sun, Jul 18, 2021 at 12:47 AM wirelessduck--- via Dng > wrote: >> >> >> On 18 Jul 2021, at 12:58, Gregory Nowak via Dng wrote: >>> >>> On Sat, Jul 17, 2021 at 09:38:13PM -0500, o1bigtenor via Dng wrote: - - - - no mention of Beowulf and that means a - - - no go - - - - at least as far as I can tell. Any ideas? >>> >>> Bionic is based on buster, and therefore similar to Beowulf. If the >>> repository has bionic, use bionic if installing on Beowulf. >>> >>> Greg >> >> Bionic is an Ubuntu release. You should be using buster-pgdg repository for >> postgresql apt as Devuan Beowulf is directly based on Debian Buster. Devuan >> has no direct relationship with Ubuntu. >> >> I use the buster-pgdg repositories for all of my postgresql installations, >> following the instructions on apt.postgresql.org but substituting the >> lsb_release part for “buster” >> > > Thank you very much. > I did not understand that I was to use 'Buster' in place of 'lsb_release' . > > Using 'lsb_release' is what caused the foobar. > > Regards Yes that snippet is designed to make it easy to copy and paste so you they can provide one script to setup for all supported distros. As Devuan isn’t directly supported by pgdg repository we just have to make a small change to use the equivalent Debian release name. -- Tom ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Fwd: Installing postgresql13 on beowulf
On Sun, Jul 18, 2021 at 12:47 AM wirelessduck--- via Dng wrote: > > > > > On 18 Jul 2021, at 12:58, Gregory Nowak via Dng wrote: > > > > On Sat, Jul 17, 2021 at 09:38:13PM -0500, o1bigtenor via Dng wrote: > >> - - - - no mention of Beowulf and that means a - - - no go - - - - at least > >> as far as I can tell. > >> > >> Any ideas? > > > > Bionic is based on buster, and therefore similar to Beowulf. If the > > repository has bionic, use bionic if installing on Beowulf. > > > > Greg > > Bionic is an Ubuntu release. You should be using buster-pgdg repository for > postgresql apt as Devuan Beowulf is directly based on Debian Buster. Devuan > has no direct relationship with Ubuntu. > > I use the buster-pgdg repositories for all of my postgresql installations, > following the instructions on apt.postgresql.org but substituting the > lsb_release part for “buster” > Thank you very much. I did not understand that I was to use 'Buster' in place of 'lsb_release' . Using 'lsb_release' is what caused the foobar. Regards ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
