Missing SLE_12 soft link with sles12_sp3 update

Our installation scripts have references to http://download.opensuse.org/repositories/server:/database:/postgresql/SLE_12/, but that URL is gone today. A sles12_sp3 directory does exist, with an update date of August 11th. Was a soft-link update omitted as part of an sp3 update?

SLES 12 SP3 is not officially out yet, so if you are involved in a beta
you should probably report it through the beta program. Otherwise, note
that you are pointed to an openSUSE repository, while dealing with SUSE
Linux Enterprise Server (SLES) and that means you are out of support
anyway. Is there a reason you pointed there rather than to an official
SLE repository? Are you indeed using SLES 12 SP3-beta-something?


Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

Thanks ab for explaining that we’re mixing opensuse content into an enterprise environment. We’re specifically looking for a psycopg package. We also are getting haproxy from another openSuse URL.

Is there a proper repo URL for psycopg for the enterprise edition (SLES)? Haproxy would be the next concern - we’d like to do that the right way as well.

Apologies for naive questions, this is one of several OSes I interact with.

On 08/14/2017 12:44 PM, shardy wrote:[color=blue]

Thanks ab for explaining that we’re mixing opensuse content into an
enterprise environment. We’re specifically looking for a psycopg
package. We also are getting haproxy from another openSuse URL.

Is there a proper repo URL for psycopg for the enterprise edition
(SLES)? Haproxy would be the next concern - we’d like to do that the
right way as well.[/color]

Ideally you would get software via the official channels which should be
part of SLES whenever you register your box using suse_register or
SUSEConnect or something. If you have not done that, then that’s part of
the purchasing process; if you have done that then maybe the packages you
need are not part of SLES at all, which is always possible with packages
that have not yet been formally adopted by the distro. Some package may
never be adopted in because they are out of scope (e.g. LibreOffice is not
part of SLES without its “Desktop” extension as I recall). Other packages
may only be available via some of the extensions to SLES, such as the Web
Scripting extension which provides things like PHP, etc. Talking to your
account/sales representative may be the best way to figure out where
packages are and ensure your user (in the SUSE Customer Center (SCC)) has
rights to register for them.
[color=blue]

Apologies for naive questions, this is one of several OSes I interact
with.[/color]

No problem; nobody knows anything until they learn them.


Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

I sent before I meant to… bah.

It may be worthwhile to point out that while you have found repositories
on the Open Build Service (OBS) for SLES, this is one of the highlights of
the SUSE ecosystem. Packagers of one thing or another (such as haproxy)
can package it for openSUSE, SLES, or even other distributions, all at
once. As a result, you can get a lo of software that is not part of
anything SUSE-ish but still maintained by people who know what they are
doing and care about doing it well. In that/this case, you can submit a
bug directly to the maintainer from the OBS web interface to let them know
something is amiss. I would probably hold off on that for SLES 12 SP3
until SP3 is actually released, but that is just me.


Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.