Stuart Henderson <s...@spacehopper.org> wrote:
> On 2020-09-28, Greg Thomas <get.misc.open...@gmail.com> wrote:
> > "Have sysupgrade just do the right thing. For example, there could be
> > a _sysupgrade user in the systems /etc/passwd, whose $HOME would
> > indicate the preferred location for sets"
> >
> > Holy fucking overkill.
>
> meh. It *is* a problem on some systems, especially if the disk layout
> was done pre-sysupgrade.
sysupgrade.sh was added 2019/04/25. it has the following tags:
OPENBSD_6_8: 1.40.0.4
OPENBSD_6_8_BASE: 1.40
OPENBSD_6_7: 1.37.0.4
OPENBSD_6_7_BASE: 1.37
OPENBSD_6_6: 1.25.0.4
OPENBSD_6_6_BASE: 1.25
OPENBSD_6_5: 1.25.0.2
we only "support" the current release (6.7), the previous release (6.6).
So, people have disk layouts which predate our "support" cycle. sysupgrade
was not intended to deal with strange layouts. Many of us feel that sysupgrade
should not bend over to deal with strange layouts.
So we are at an impasse. The recommended solution is for people to stop
making sysupgrade-incompatible layouts in the future, and to consider
repairing their incompatible layouts from the past.
if sysupgrade doesn't work, people have the old ways of doing things.
doctor doctor it hurts when i layout my disk strangely...
