Open tailhook opened 4 years ago
The most reliable solution here would be to slot each nightly separately so they're treated as major releases.
Moving to edgedb-pkg
@ambv Let's switch nightlies to encode nightly-{date and hour}
in the package slot, e.g. instead of edgedb-server-1-alpha5
we would have edgedb-server-1-alpha5-nightly2020061720
upgrade --nightly
after thatserver install
(and I expect nightly users to have a much larger percentage of advanced users), so garbage collecting nightlies automatically can be a problem for some users.We can make the garbage-collection into an explicit command and advise users to run it if we detect no instances using that version. This should also be useful for non-nighly releases too.
On the other hand, breakage caused by apt-get upgrade
is significantly worse, and I see no other reliable way to avoid it.
Maybe apt-mark hold
package right after installing? With yum
it looks like the plugin is needed.
But yes, given that we need garbage collection anyway it might be a good idea to have separate nightly packages.
The output of upgrade command:
Log is:
To show nicer error this we might consider running edgedb in foreground and analyze output. Or alternatively, we can implement
edgedb server logs
and parse output of that command internally.