<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-support/ca-certificates, branch master</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2025-11-07T13:31:53+00:00</updated>
<entry>
<title>The poky repository master branch is no longer being updated.</title>
<updated>2025-11-07T13:31:53+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-11-07T13:31:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8c22ff0d8b70d9b12f0487ef696a7e915b9e3173'/>
<id>urn:sha1:8c22ff0d8b70d9b12f0487ef696a7e915b9e3173</id>
<content type='text'>
You can either:

a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs

b) use the new bitbake-setup

You can find information about either approach in our documentation:
https://docs.yoctoproject.org/

Note that "poky" the distro setting is still available in meta-yocto as
before and we continue to use and maintain that.

Long live Poky!

Some further information on the background of this change can be found
in: https://lists.openembedded.org/g/openembedded-architecture/message/2179

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta: set S to be in UNPACKDIR in recipes that explicitly set S</title>
<updated>2025-06-20T11:07:26+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex@linutronix.de</email>
</author>
<published>2025-06-16T09:49:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=e1f059f34e7f1e6a252aff1ec5b1eb3376bd4d65'/>
<id>urn:sha1:e1f059f34e7f1e6a252aff1ec5b1eb3376bd4d65</id>
<content type='text'>
(From OE-Core rev: 7321cc17ae5483f17fe9cdffea7b62acd9d9c3a2)

Signed-off-by: Alexander Kanavin &lt;alex@linutronix.de&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ca-certificates: fix on-target postinstall script</title>
<updated>2025-05-27T08:01:16+00:00</updated>
<author>
<name>Gyorgy Sarvari</name>
<email>skandigraun@gmail.com</email>
</author>
<published>2025-05-23T18:18:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=77b7006d7700e413ca363631fbd652fb88e46c20'/>
<id>urn:sha1:77b7006d7700e413ca363631fbd652fb88e46c20</id>
<content type='text'>
When the package is installed directly on the machine (instead of
installing it in the rootfs directly), the postinstall script fails with
the following error:

/usr/sbin/update-ca-certificates: line 75: shift: shift count out of range

The reason is that the "update-ca-certificates" script is executed with
the "--sysroot" argument, and as the sysroot $D is passed. However on the
target system this variable doesn't exist, so the argument is passed without
this mandatory value, and the execution fails.

To avoid this error, check if the $D variable exists, and pass the --sysroot
argument only when it does.

Reported-by: WXbet &lt;Wxbet@proton.me&gt;
(From OE-Core rev: cf39461e97098a1b28693299677888ba7e8bfccf)

Signed-off-by: Gyorgy Sarvari &lt;skandigraun@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ca-certificates: upgrade 20241223 -&gt; 20250419</title>
<updated>2025-05-13T09:29:20+00:00</updated>
<author>
<name>Wang Mingyu</name>
<email>wangmy@fujitsu.com</email>
</author>
<published>2025-05-12T09:02:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=890c360c55230ab8ee711e7498e66019643becaa'/>
<id>urn:sha1:890c360c55230ab8ee711e7498e66019643becaa</id>
<content type='text'>
0001-Revert-mozilla-certdata2pem.py-print-a-warning-for-e.patch
0001-update-ca-certificates-don-t-use-Debianisms-in-run-p.patch
refreshed for 20250419

0002-sbin-update-ca-certificates-add-a-sysroot-option.patch
removed since it's included in 20250419

(From OE-Core rev: e39cc1fb7234bf2b37856296d3c0d10ddf8cae64)

Signed-off-by: Wang Mingyu &lt;wangmy@fujitsu.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ca-certificates: submit sysroot patch upstream, drop default-sysroot.patch</title>
<updated>2025-04-10T10:05:34+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex@linutronix.de</email>
</author>
<published>2025-04-07T09:40:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=183e7414d1925dd08f3ae0594b63dc92bd4abf41'/>
<id>urn:sha1:183e7414d1925dd08f3ae0594b63dc92bd4abf41</id>
<content type='text'>
ca-certificates/0002-update-ca-certificates-use-SYSROOT.patch
was using a non-standard environment variable, and was replaced
with a patch that adds a command line option (and then this
was submitted upstream). ca-certificates recipe was tweaked accordingly,
and nothing else in core or meta-oe is using update-ca-certificates.

Drop default-sysroot.patch as the use case is unclear: sysroot
is explicitly specified in all known invocations of update-ca-certificate,
and if there's a place where it isn't, then update-ca-certificates
will error out trying to write to /etc, and should be fixed to
explicitly specify the sysroot.

(From OE-Core rev: 90d9f0ba674d4fe8e9291f0513c13dff3775c545)

Signed-off-by: Alexander Kanavin &lt;alex@linutronix.de&gt;
Signed-off-by: Mathieu Dubois-Briand &lt;mathieu.dubois-briand@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ca-certificates: upgrade 20240203 -&gt; 20241223</title>
<updated>2025-01-03T10:51:27+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-01-01T10:34:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0ebc2cb04eeeb2a41de5930a8ab8b357ee5b124c'/>
<id>urn:sha1:0ebc2cb04eeeb2a41de5930a8ab8b357ee5b124c</id>
<content type='text'>
(From OE-Core rev: 48a236c2f78fee5e6db19c6be23b4a18df025607)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ca-certificates: get sources from debian tarballs</title>
<updated>2024-08-03T06:56:10+00:00</updated>
<author>
<name>Alexander Kanavin</name>
<email>alex@linutronix.de</email>
</author>
<published>2024-08-02T16:09:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=eaffa0a69615814bb58a41a6a21884a8ca6d1f8d'/>
<id>urn:sha1:eaffa0a69615814bb58a41a6a21884a8ca6d1f8d</id>
<content type='text'>
git repo no longer has tags for recent versions which means
we had missed several of them, and wouldn't be able to get
notifications about any future releases.

(From OE-Core rev: 81f013fd1312551628701bf36ac62746a2606dbd)

Signed-off-by: Alexander Kanavin &lt;alex@linutronix.de&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ca-certificates: Add comment for provenance of SRCREV</title>
<updated>2024-07-30T11:32:53+00:00</updated>
<author>
<name>Theodore A. Roth</name>
<email>troth@openavr.org</email>
</author>
<published>2024-07-29T15:07:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c451345ff40979f6b082978c5c644132280c2196'/>
<id>urn:sha1:c451345ff40979f6b082978c5c644132280c2196</id>
<content type='text'>
Provide references for how the SRCREV was arrived at for the 20240203
release.

(From OE-Core rev: 6916cdb0f05f6644edb1e432a9421595abb9f0ca)

Signed-off-by: Theodore A. Roth &lt;troth@openavr.org&gt;
Signed-off-by: Theodore A. Roth &lt;theodore_roth@trimble.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>ca-certificates: update 20211016 -&gt; 20240203</title>
<updated>2024-07-26T11:28:42+00:00</updated>
<author>
<name>Theodore A. Roth</name>
<email>troth@openavr.org</email>
</author>
<published>2024-07-24T14:53:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=beabc787cacb9b399f19eac39903948154dcce18'/>
<id>urn:sha1:beabc787cacb9b399f19eac39903948154dcce18</id>
<content type='text'>
The 20240203 version is the same as used in Ubuntu &gt;= 24.04 and Debian
Trixie (testing).

(From OE-Core rev: ce19168885a04b0d77e81c1fd1c4262b195a47d4)

Signed-off-by: Theodore A. Roth &lt;troth@openavr.org&gt;
Signed-off-by: Theodore A. Roth &lt;theodore_roth@trimble.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta/meta-selftest/meta-skeleton: Update LICENSE variable to use SPDX license identifiers</title>
<updated>2022-02-20T16:45:25+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-02-18T17:15:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b0130fcf91daee0d905af755302fabe608da141c'/>
<id>urn:sha1:b0130fcf91daee0d905af755302fabe608da141c</id>
<content type='text'>
An automated conversion using scripts/contrib/convert-spdx-licenses.py to
convert to use the standard SPDX license identifiers. Two recipes in meta-selftest
were not converted as they're that way specifically for testing. A change in
linux-firmware was also skipped and may need a more manual tweak.

(From OE-Core rev: ceda3238cdbf1beb216ae9ddb242470d5dfc25e0)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
