Aim to base helloSystem on supported FreeBSD 12.2-RELEASE-p4 or 13.0-RELEASE #135
Comments
|
Keep in mind that we cannot use And we can only switch to 12.2 once we have a compatible Intel DRM package. Which means (if I am not mistaken) that we can only switch to 12.2 once the Intel DRM package in last quarter's packages is compatible with 12.2. So, at least another quarter to wait? |
Disappearances should be infrequent (and annoyances should be avoidable). Maybe raise a separate issue for this, for a focused investigation that's not scattered across multiple issues.
Above, |
I think it is - but does it work? #1 |
File systems supportFrom helloSystem/docs@5414719:
– and:
https://github.com/vermaden/automount describes Instead: Available, logged: |
|
f73b9d6
|
|
@probonopd I suspect,
Thanks |
|
For me the question is which FreeBSD version the next helloSystem version, 0.5.0 (~March 2021) should be based on. The experimental builds right now are building towards the upcoming 0.5.0. (The mid-term question will be whether 1.0.0 will be 13-based...). I must have overlooked the difference between And the question is, can any 12 later than 12.2 currently work properly (including Intel GPU drivers) with last quarter's packages (because |
|
|
helloSystem documentation refers to https://cirrus-ci.com/ but it's somewhat mysterious. How can I tell what does exist?
Patch levels and security advisoriesThanks to debdrup in freenode (@debdrup in GitHub?) I recently learnt of this unnoficial page: Under https://bokut.in/freebsd-patch-level-table/#releng/12.2
Posted to Reddit, unfortunately neither post was allowed: |
grahamperrin
changed the title
It's simple to test this for yourself with |
Unfortunately not. This is a show-stopper to reasonable testing:
For my everyday system with 2,019 packages from For helloSystem with some packages from Worst amongst those might be
|
|
This means that we really need to find a way to make quarterly work for us, rather than having to use last quarter's packages... If only this could be solved FreeBSD-wide. I would really rather not want to have to maintain a private mirror of the packages. |
|
grahamperrin
changed the title
|
With reference to
ImportantFreeBSD-EN-21:08.freebsd-update fixes the bug that caused #115 #136 and #137 1744e6d prevents upgrades to packages with helloSystem and so, increases the risk of problems. Again: please revert this commit; it's excessive. |
|
When deciding on whether to base the next version on 12.x or on 13, we need to factor in that GPU acceleration may be severly limited in 13: Also, this currently blocks us from using 13: (Unless we can get rid of gvfs which would be the best solution) |
|
0.5.0 will be based on 12.2 thanks to the help of @crees with the Intel GPU driver. I don't know about |
|
Thanks,
#135 (comment) above described patch levels and security advisories and:
– so #135 (comment) above listed, and linked to, the four security vulnerabilities that were fixed at patch level 4. I don't have a readily available list of security vulnerabilities that were fixed by levels 1, 2 or 3.
If you'll prevent updates to the non-patched system, then you'll force users to be without fixes for security vulnerabilities. This is somewhat inconsistent with the welcome to the system, which mentions security:
A truly secure system involves much more than end-to-end encryption. The prevention of package upgrades by 1744e6d is more than a security concern. It is, moreover, deeply inconsistent with the promised freedom to load software without restrictions. Prevention is working against me, not for me. |
|
Indeed. Will look into it. Opening a separate issue. |
|
Thanks. Briefly:
I should assume that all post https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.2/
|
|
Patching the contents of the ISO is probably futile, because at the time when the user installs the ISO of the helloSystem release there are already new patches available. So allowing the user to patch the installed system could possibly make sense, see my thoughts in helloSystem/Utilities#33 (comment) though. |
Found, a few weeks later: |
|
https://cirrus-ci.com/github/helloSystem/ shows all the builds that are going on, and their logs. Not something "mere mortals" should need to understand, but definitely interesting for helloSystem developers, testers, and power users ;-) |
DRM
#1
From https://old.reddit.com/r/freebsd/comments/lgjuab/-/gn3t3qi/?context=1 for three relevant packages from
latest:OpenZFS
From #125 (comment):
FreeBSD
12.2-RELEASE-p3with the kernel module built from a12.2jail forquarterly:2021-02-12.22.03.FreeBSD.12.2-RELEASE-p3.with.openzfs-kmod.from.quarterly.mp4
ksnip
#17 (2020-11-21)
ISO/settings/packages.hello
Line 68 in 9c09b32
A fixed version in
quarterly:https://www.freshports.org/graphics/ksnip#history
1.7.3_1committed 2020-12-30.The text was updated successfully, but these errors were encountered: