<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/release, branch main</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=main</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2026-06-12T18:21:48Z</updated>
<entry>
<title>vmimage.subr: Add ability to install src in VM image</title>
<updated>2026-06-12T18:21:48Z</updated>
<author>
<name>Krzysztof Galazka</name>
<email>kgalazka@FreeBSD.org</email>
</author>
<published>2026-06-12T18:21:14Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4ea4116f8d2069194563c8692c1f28d88c319ca8'/>
<id>urn:sha1:4ea4116f8d2069194563c8692c1f28d88c319ca8</id>
<content type='text'>
In some cases having a src tree in a VM image is convenient
for development or debugging. Add a WITH_SRC variable,
which, when set, will cause the vm-release target to include
FreeBSD-set-src in the list of packages installed in an image.

Signed-off-by: Krzysztof Galazka &lt;krzysztof.galazka@intel.com&gt;

Sponsored by:   Intel Corporation

Reviewed by:	cperciva
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D57143
</content>
</entry>
<entry>
<title>GCE: Apply public-image label on GCE images</title>
<updated>2026-06-10T02:33:12Z</updated>
<author>
<name>Xin LI</name>
<email>delphij@FreeBSD.org</email>
</author>
<published>2026-06-10T02:33:03Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=c85542b92acd286d9e4b034b2ab4d6b6cd46c740'/>
<id>urn:sha1:c85542b92acd286d9e4b034b2ab4d6b6cd46c740</id>
<content type='text'>
Update the GCE image creation process to automatically apply the
'public-image=true' label when publishing new images. This aligns
with standard labeling expectations for images hosted in public
projects.

MFC after:	3 days
</content>
</entry>
<entry>
<title>EC2: Don't enable firstboot_pkgs in small flavour</title>
<updated>2026-05-16T19:18:52Z</updated>
<author>
<name>Colin Percival</name>
<email>cperciva@FreeBSD.org</email>
</author>
<published>2026-05-16T18:58:13Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=61df4be487cfbfd27b0959e1eb66ef0d8f84562f'/>
<id>urn:sha1:61df4be487cfbfd27b0959e1eb66ef0d8f84562f</id>
<content type='text'>
The EC2 "base" flavour installs the devel/py-awscli package at boot
time by default; we don't do this in the "small" flavour, so the
default behaviour was to update the FreeBSD-ports repository and
then do nothing with it.

Turn off firstboot_pkgs by default; if someone is using the "small"
flavour of AMIs and wants to install packages at instance launch
time, they simply need to add 'firstboot_pkgs_enable="YES"' to
/etc/rc.conf (which they must already be editing via user-data, in
order to provide the list of packages they want installed).

Sponsored by:	Amazon
MFC after:	3 days
MFC to:		stable/15
Relnotes:	EC2 "small" images now have firstboot_pkgs_enable="NO".
</content>
</entry>
<entry>
<title>Cloud releases: More firstboot_pkg_upgrade</title>
<updated>2026-05-14T21:59:11Z</updated>
<author>
<name>Colin Percival</name>
<email>cperciva@FreeBSD.org</email>
</author>
<published>2026-05-14T21:14:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4080419d9a2d88d44d20baaf3ea01934561819c1'/>
<id>urn:sha1:4080419d9a2d88d44d20baaf3ea01934561819c1</id>
<content type='text'>
Update a couple more cloudware images which I forgot about earlier.

Reviewed by:	ziaee
Fixes: 464a351267dc ("Cloud releases: Switch to firstboot_pkg_upgrade")
Differential Revision:	https://reviews.freebsd.org/D57006
</content>
</entry>
<entry>
<title>Cloud releases: Switch to firstboot_pkg_upgrade</title>
<updated>2026-05-14T21:05:12Z</updated>
<author>
<name>Alexander Ziaee</name>
<email>ziaee@FreeBSD.org</email>
</author>
<published>2026-05-14T21:05:07Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=464a351267dc0d1843b919dd72ad1c70c24815ce'/>
<id>urn:sha1:464a351267dc0d1843b919dd72ad1c70c24815ce</id>
<content type='text'>
Cloud images are deployed with base system packages. Introduce a
firstboot package auto updater to patch the base system on first boot.

MFC after:		1 hour
MFC to:			stable/15
Reviewed by:		cperciva
Sponsored by:		Google Cloud
Differential Revision:	https://reviews.freebsd.org/D56890
</content>
</entry>
<entry>
<title>Makefile.vm: Split error condition</title>
<updated>2026-05-06T17:50:07Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2026-05-05T21:12:25Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=76d756eaa6823aad282cc53ec4e41a9777d89adc'/>
<id>urn:sha1:76d756eaa6823aad282cc53ec4e41a9777d89adc</id>
<content type='text'>
Make it clear which of two possible cases applies.

Reviewed by: cperciva
Differential Revision: https://reviews.freebsd.org/D56837
</content>
</entry>
<entry>
<title>packages: Make create-sets.sh more robust during release</title>
<updated>2026-05-05T00:32:34Z</updated>
<author>
<name>Lexi Winter</name>
<email>ivy@FreeBSD.org</email>
</author>
<published>2026-05-05T00:31:20Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=8e8d87856241f69c277dc5fab48c5c66312475d6'/>
<id>urn:sha1:8e8d87856241f69c277dc5fab48c5c66312475d6</id>
<content type='text'>
Commit d1c176fedfc9 made create-sets.sh exit when it encounters an
error, instead of creating an empty repository.  However, this turns
out to cause some issues:

1. A package not having any sets is considered an error, but during
   the release build, we stuff a 'pkg' package into the repository
   which doesn't have any sets, which causes a failure.  Avoid this
   by simply ignoring the pkg package.

2. No error was printed in this case, which made the problem hard
   to diagnose.  Add an explicit error message.

3. A similar problem occurred running on a repository which already
   contained sets, which is not usually done during the build, but
   is not necessarly an inappropriate thing to do.  Fix this one by
   ignoring set packages when looking for sets.

While here, fix another issue that might cause packages to be wrongly
skipped if the path to the repository contains a '-' character, since
we didn't strip the path before testing the package name.

PR:	294966
Fixes:	d1c176fedfc9 ("packages: Make create-sets.sh more robust")
MFC after:	2 weeks
Reported by:	Alastair Hogge &lt;agh@riseup.net&gt;
Reviewed by:	emaste
Sponsored by:	https://www.patreon.com/bsdivy
Differential Revision:	https://reviews.freebsd.org/D56792
</content>
</entry>
<entry>
<title>packages: Make create-sets.sh more robust</title>
<updated>2026-04-28T19:50:42Z</updated>
<author>
<name>Lexi Winter</name>
<email>ivy@FreeBSD.org</email>
</author>
<published>2026-04-28T19:39:14Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=d1c176fedfc99d61c1dc8037ab549bec48c17bea'/>
<id>urn:sha1:d1c176fedfc99d61c1dc8037ab549bec48c17bea</id>
<content type='text'>
Use ${PKG_CMD} rather than bare 'pkg' to fix the build when pkg is
not in the tools path.  Provide a default in case it's not set for
some reason (e.g., running the script by hand).

Since set -- $(...) does not trigger an exit from set -e if the
command fails, this failure was silent and resulted in sets not
being built correctly if we failed to run pkg.  Use a temporary
variable, which does trigger set -e, to fail correctly.

MFC after:	2 weeks
Reviewed by:	sjg
Sponsored by:	https://www.patreon.com/bsdivy
Differential Revision:	https://reviews.freebsd.org/D56676
</content>
</entry>
<entry>
<title>make-pkg-package: Add set -e; abort if a cmd fails</title>
<updated>2026-04-27T21:16:18Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2025-10-04T20:14:43Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0068c706f8ce872c735ddcc383c5cd5ab85acc88'/>
<id>urn:sha1:0068c706f8ce872c735ddcc383c5cd5ab85acc88</id>
<content type='text'>
This makes it less likely we will silently generate broken artifacts.

Reviewed by:	ivy
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D56671
</content>
</entry>
<entry>
<title>pkg-stage: Improve symlink creation</title>
<updated>2026-04-27T19:47:24Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2025-05-05T18:01:21Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4846afc9104a1b4aeec31dc7c324f69ad5ffab1b'/>
<id>urn:sha1:4846afc9104a1b4aeec31dc7c324f69ad5ffab1b</id>
<content type='text'>
Invoke ln with -n and -f.  In normal use it doesn't matter, but during
development this might be run in a partially populated leftover tree.

Reviewed by:	ivy
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D52883
</content>
</entry>
</feed>
