[Dachs-support] Fwd: Questions about DaCHS
Markus Demleitner
gavo at ari.uni-heidelberg.de
Mon Jul 31 14:23:12 CEST 2023
Hi Loïc,
On Mon, Jul 31, 2023 at 01:42:02PM +0200, Loïc Trompet wrote:
> > So... do you happen to know what might have been special about these
> > jobs? How did you create them, what happened to them, and how were
> > they deleted?
> I did not create them. I did not access our server where DaCHS is installed
> since several weeks. I think that the only possibility are queries to the
> data service made by external people.
I see. Um... just so I can have a look: Is your server accessible
from the outside world? If so, what is its URL? I just want to make
sure the jobs really aren't still managed by DaCHS.
If they are not not any more: can you have a look at what's in
the results? Perhaps that will give us a clue at how to reproduce
the problem.
> > deb https://ftp.belnet.be/debian/ buster main contrib
Ah, ok, so it's a buster machine. That would explain its desire to
remove gavodachs2-server: that *does* have some extra dependencies
that are missing from buster.
So, in:
> > > The following packages will be REMOVED:
> > > gavodachs2-server python3-gavo
> > > The following packages will be upgraded:
> > > python3-gavo-stc python3-gavo-utils python3-gavo-votable
> > Can you tell us if this upgrade is safe ?
the machine realises it can upgrade the "simpler" basic packages, but
it realises that to do so, it needs to remove the packages with more
complicated dependencies, because they say the need the simpler
package of exactly the same version.
Such an upgrade should never be proposed on an apt update, I think.
Did you ask it to do a dist-upgrade?
Be that as it may, since buster is now oldoldstable, I'd rather not
try and see how to satisfy DaCHS' current dependencies in it.
So, unless there's some pressing issue, I'd suggest that *if* you
want a newer DaCHS, you do the dist-upgrade at least to bullseye; the
somewhat complicated part with that is postgres (cf.
<http://docs.g-vo.org/DaCHS/tutorial.html#upgrading-postgres>), but
even that is manageable.
On the other hand *if* a simple ``apt upgrade`` really did suggest to
remove gavodachs2-server, I'd like to look into it to see if I can
avoid such a (relatively) dangerous proposition.
Thanks,
Markus
More information about the Dachs-support
mailing list