search

helloSystem / docs

This repository builds the documentation for hello
https://hellosystem.github.io/docs/
BSD 2-Clause "Simplified" License
20 stars 22 forks source link

Troubleshooting: lock the hello package; and a one-line fix for cases where FreeBSD bug 232921 bites #17

Closed grahamperrin closed 3 years ago

grahamperrin commented 3 years ago
  1. Mandatory lock of hello before pkg upgrade
  2. a simple command-line fix for FreeBSD bug 232921, which can sometimes bite following a routine system upgrade.
probonopd commented 3 years ago

I think we should find a way to lock the hello package out of the box... And wrap the pkg command in something that prints an information and exits when invoked with upgrade. Wdyt?

grahamperrin commented 3 years ago

If you can lock hello that'll be smart, but the more immediate priority should be to document avoidance of the trouble.

An unusable system i.e. broke login screen is significantly troublesome ;-) and we can't expect users who are familiar with pkg to always make good use of bectl or beadm before (naturally) wishing to upgrade.

probonopd commented 3 years ago

Closing in favor of https://github.com/helloSystem/ISO/commit/1744e6d141b91c61897f423ef815965908a85e15

probonopd commented 3 years ago

Do not attempt use of freebsd-update commands with experimental helloSystem

Do you mean pkg freebsd-update, pkg update, pkg upgrade?

Also, please try to be much more concise. How about:

WARNING: Please do not attempt to use the FreeBSD pkg command line tool to upgrade or update heloSystem. This is currently not supported and may result in a broken system.

grahamperrin commented 3 years ago

More concise. FreeBSD bug 232921 puts things in perspective.

With users advised to simply lock the hello package:

Please revert https://github.com/helloSystem/ISO/commit/1744e6d141b91c61897f423ef815965908a85e15 – it's excessive. Thank you.

grahamperrin commented 3 years ago

No point in leaving this open when it's a source of confusion.