bug.ig...@aleeas.com wrote:
> > Incomplete or vague bug reports don't usually result in improvements.
>
> I'd be happy to provide anything else. Let me know if I can.
A complete and non-vague bug report.
Until then, this conversation is dead.
On 5 March 2022 18:02:05 CET, Theo de Raadt wrote:
>bug.ig...@aleeas.com wrote:
>
>> > OK so this matches "complex disk layout" and I'm not so surprised thatyou
>> > are having problems with sysupgrade.
>>
>> Haha. I guess you are right.
>>
>> But how did it upgrade it to snapshot then?
>> A
bug.ig...@aleeas.com wrote:
> > OK so this matches "complex disk layout" and I'm not so surprised thatyou
> > are having problems with sysupgrade.
>
> Haha. I guess you are right.
>
> But how did it upgrade it to snapshot then?
> And if it can't upgrade (some systems), then it's a bug, right?
>
On 2022/03/05 16:40, bug.ig...@aleeas.com wrote:
> > When you upgrade from the usb image, do you need to use non-default
> answers to any of the questions?
>
> As far as I remember only for the file sets source drive (and its related
> options).
>
> > There's no general problem with sysupgrade b
On 2022/03/05 06:05, bug.ig...@aleeas.com wrote:
> > Something went wrong with the sets update then. Can't say any more
> > from this. Try sysupgrade again and see if there's any clue in the
> > log from sysupgrade that should be emailed to root (which in a normal
> > default setup will be forwarde
On Sat, Mar 05, 2022 at 09:00:21AM +0100, bug.ig...@aleeas.com wrote:
>
> Upgrading this way worked but sysupgrade didn't.
> I have a feeling this is a bug in sysupgrade.
So you upgraded to:
> OpenBSD 7.1-beta (GENERIC.MP) #402: Fri Mar 4 11:15:14 MST 2022
> dera...@amd64.openbsd.org:/usr/s
