Committed in https://cgit.FreeBSD.org/ports/commit/?id=b346b480027ce76a731603e28d4ae7a847b494e1
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 15 2024
Mar 6 2024
Mar 4 2024
Mar 3 2024
Mar 1 2024
Feb 29 2024
Feb 18 2024
Feb 16 2024
- Moved noto.mk to Mk/Uses.
- Renamed "make distfile" to "make noto-fetch" and let "make makesum" call it.
- Make distfile creation reproducible (reset uid, gid, file mode, and timestamps).
Feb 11 2024
Feb 7 2024
Feb 6 2024
Jan 31 2024
Jan 25 2024
I'll look into this after dealing with bug 272216 and bug 276478.
Jan 24 2024
Jan 21 2024
In D43509#992501, @arrowd wrote:What I don't like about this change is creation of many ports. This looks like an ideal case to apply subpackages.
Each port has its own version number and release dates so subpackages don't really fit. The CJK and emoji fonts also have a different master site. I think separate ports fits better.
Jan 20 2024
Jan 19 2024
Jan 13 2024
Dec 22 2023
Nov 17 2023
Oct 17 2023
Oct 12 2023
Oct 6 2023
Sep 30 2023
Sep 21 2023
Sep 4 2023
Aug 17 2023
Aug 15 2023
Aug 10 2023
Jul 17 2023
Jul 13 2023
Jul 11 2023
Jul 5 2023
Jul 2 2023
Jul 1 2023
Jun 25 2023
Jun 23 2023
May 1 2023
Apr 16 2023
Mar 30 2023
Mar 16 2023
Mar 12 2023
Mar 9 2023
Feb 28 2023
In D38811#883669, @bapt wrote:In D38811#883667, @tijl wrote:In D38811#883565, @tcberner wrote:I would simply fix the creator to remove the hyphens before writing them to the machine-id file. Then we'll still have UUID v4.
The point of the whole thing is to have the compliant interface that modern software expects.Systemd only generates v4 as a last resort, so software cannot assume it is v4. It can't even assume it follows RFC 4122 because dbus-uuidgen and old versions of systemd just produce a random number.
I think one UUID per machine is easier to manage and generating /etc/machine-id from rc.d/hostid_save removes some redundancy. If v4 is preferred then rc.d/hostid can be patched to run "uuidgen -r" or "uuidgen ${uuidgen_flags}" with uuidgen_flags set to -r by default. I could include that in this patch but I think it is a separate issue.
This is not a last resort, this is the default if no previous machine-id do exist. some program may expect RFC 4122 at some point (some already talk about it iirc) that is why we directly went to it for new. imho this ship has sailed.
In D38811#883565, @tcberner wrote:I would simply fix the creator to remove the hyphens before writing them to the machine-id file. Then we'll still have UUID v4.
The point of the whole thing is to have the compliant interface that modern software expects.
Feb 27 2023
In D38811#883365, @bapt wrote:no hostid is not generating the same uuid, machine-id is based on uuidgen -r which generate version 4 UUID (RFC422), but you are right, about the hyphen.