rpms/ostree

Fork 0

Upstream update available: ostree 2025.7 → 2026.1 #1

New issue

Open

opened 2026-04-28 01:38:18 +03:00 by sbelikov · 0 comments

sbelikov commented

2026-04-28 01:38:18 +03:00

Owner

Upstream update available: `ostree` `2025.7` → `2026.1`

Package

Package: ostree
RPM name: ostree
Branch: niceos-5.2
Current EVR: 2025.7-1
Update class: major
Compare method: python_rpm
Update policy: leaf
Risk tags: github-upstream, patch-debt

Upstream

Upstream type: github
Upstream project: ostreedev/ostree
Upstream URL: github.com — ostree
Detected version: 2026.1
Tag/release: v2026.1
Source: github_release_latest
Published: 2026-04-10T23:37:28Z
Release URL: github.com — v2026.1
Source URL: api.github.com — v2026.1
Pre-release: False

Signals

Security-relevant keywords detected: False
Policy blocked: False
Policy reason: -
Labels: ai-summary, bot, needs-build, needs-triage, priority/high, update/major, upstream-update, upstream/github

NiceSOFT AI preliminary stability analysis

Analysis of Upstream Update for `ostree` in NAI.S.OS

1. Key Details

Version: 2026.1 (major update from 2025.7)
Update Type: Major (significant changes)
Policy: leaf (not a minor update)
Risk Tags: github-upstream, patch-debt (indicating potential upstream changes)
Changes Mentioned:
- Bug fixes (e.g., soft-reboot handling, UTF-8 filename support)
- CI/CD overhaul (Packit CI, TMT tests)
- Improvements to ostree package (e.g., BLS key preservation)

2. Risk Assessment

A. ABI (Application Binary Interface) Risks

Status: No explicit ABI changes mentioned.
Potential: Major updates often involve ABI changes, but the data does not confirm this.
Recommendation: Monitor for any implicit ABI changes (e.g., new APIs, deprecated functions). If applicable, update BuildRequires and %check to ensure compatibility.

B. Security Risks

Status: No specific CVEs or security vulnerabilities mentioned.
Potential: Fixes like BLS key preservation are critical for security, but no explicit threats are noted.
Recommendation: Ensure the package is tested for security compliance, especially if it’s used in production.

C. CI/CD Impact

Status: Major CI overhaul (Packit CI, TMT tests).
Potential: New tools may require updated dependencies or configurations.
Recommendation: Verify compatibility of BuildRequires and %check with the new CI tools. Test the package in the new environment.

D. Upgrade Risks

Status: Major update with improvements but no backward compatibility.
Potential: Potential for breaking changes (e.g., API differences, new features).
Recommendation: Test the package in a staging environment before deployment. Document any changes in NEWS or ChangeLog.

3. Recommendations

Update the Package:
- Apply the update to ensure all fixes and improvements are applied.
- Verify compatibility with existing systems (e.g., CI/CD pipelines).
Review BuildRequires and %check:
- Update BuildRequires to include new dependencies (e.g., TMT tools).
- Adjust %check to include new tests (e.g., CI/CD tests).
Test in Staging Environment:
- Deploy the package to a staging environment to validate functionality and compatibility.
Monitor for Implicit ABI Changes:
- If the update introduces new APIs or deprecated functions, update the package accordingly.
Document Changes:
- Update the NEWS or ChangeLog file to reflect the major update and its implications.

4. Conclusion

This major

Источники, найденные web_search

Upstream release notes / description

This release includes several important bug fixes, most notably fixing
soft-reboot handling for var, sysroot, and boot mounts, and
preserving extension BLS keys across staged deployments. The libarchive
integration now correctly handles UTF-8 filenames without locale
dependency, and the dracut module was fixed to use the correct systemd
unit directory. On the features side, ostree admin status --json now
includes the deployment origin refspec.
The CI infrastructure saw a significant overhaul: Packit CI was added
with RPM builds and TMT integration tests, the test-tmt shell script
was replaced with a Rust xtask, and Justfile targets were introduced
for local development workflows.

Bug Fixes

libarchive: Handle UTF-8 filenames without locale dependency
state-overlay: Fix ENODATA handling for GLib < 2.74
bootconfig: Preserve extension BLS keys across staged deployments
generator: Fix soft-reboot for var, sysroot, and boot
boot/dracut: Use systemdsystemunitdir instead of systemdsystemconfdir

Improvements

status: Include deployment origin refspec as refspec in JSON output

CI & Testing

Revamp bootc integration test suite with bcvk VM support
Drop running COSA as UID 0
Drop cosa fetch
Respect TEST_TMPDIR for temporary directories
Sync bootc-ubuntu-setup action from bootc-dev/infra
Add Packit CI with RPM builds and TMT integration tests
Remove bcvk VM dispatch from Rust integration tests
Replace test-tmt shell script with Rust xtask
Fix cargo build failure on Fedora 43/44 in Containerfile.packit
Extend cargo fmt check to cover all Rust crates
Sync Rust linting checks from bootc-dev/bootc
Fix cargo fmt formatting in tests/xtask
Remove unused Kill9Stats and RebootStats structs from tests/inst
Add Rust validate targets to Justfile for local development
Use Justfile targets in GitHub workflow and add missing v2024_7 feature
Install ca-certificates in Debian Testing pre-checkout setup
Make fuse and libfuse-dev conditional for Debian Testing

New Contributors

@lxnay made their first contribution in github.com — 3569
@pvalena made their first contribution in github.com — 3572
@henrywang made their first contribution in github.com — 3576

Full Changelog: github.com — v2025.7...v2026.1

NiceOS maintainer checklist

Confirm that the detected version is a stable upstream release.
Check upstream changelog for security fixes, ABI/API changes and build-system changes.
Check ABI/API compatibility and reverse dependencies.
Download source into NiceOS lookaside storage.
Update Version and related fields in SPECS/*.spec only if policy allows it.
Regenerate SOURCES/sources.lock.json, manifests, metadata and SBOM.
Build SRPM/RPM in a clean NiceOS buildroot.
Run package smoke tests.
Link PR/build logs and close this issue after update or triage.

Bot metadata

Tool: niceos_upstream_monitor.py 2.1.3-local-websearch-github-release-pages
Generated at: 2026-06-15T00:19:50Z

# Upstream update available: `ostree` `2025.7` → `2026.1` ## Package - Package: `ostree` - RPM name: `ostree` - Branch: `niceos-5.2` - Current EVR: `2025.7-1` - Update class: `major` - Compare method: `python_rpm` - Update policy: `leaf` - Risk tags: `github-upstream, patch-debt` ## Upstream - Upstream type: `github` - Upstream project: `ostreedev/ostree` - Upstream URL: <a href="https://github.com/ostreedev/ostree" target="_blank" rel="noopener noreferrer">github.com — ostree</a> - Detected version: `2026.1` - Tag/release: `v2026.1` - Source: `github_release_latest` - Published: `2026-04-10T23:37:28Z` - Release URL: <a href="https://github.com/ostreedev/ostree/releases/tag/v2026.1" target="_blank" rel="noopener noreferrer">github.com — v2026.1</a> - Source URL: <a href="https://api.github.com/repos/ostreedev/ostree/tarball/v2026.1" target="_blank" rel="noopener noreferrer">api.github.com — v2026.1</a> - Pre-release: `False` ## Signals - Security-relevant keywords detected: `False` - Policy blocked: `False` - Policy reason: `-` - Labels: `ai-summary, bot, needs-build, needs-triage, priority/high, update/major, upstream-update, upstream/github` ## NiceSOFT AI preliminary stability analysis ### **Analysis of Upstream Update for `ostree` in NAI.S.OS** --- #### **1. Key Details** - **Version**: `2026.1` (major update from `2025.7`) - **Update Type**: Major (significant changes) - **Policy**: `leaf` (not a minor update) - **Risk Tags**: `github-upstream`, `patch-debt` (indicating potential upstream changes) - **Changes Mentioned**: - Bug fixes (e.g., soft-reboot handling, UTF-8 filename support) - CI/CD overhaul (Packit CI, TMT tests) - Improvements to `ostree` package (e.g., BLS key preservation) --- #### **2. Risk Assessment** ##### **A. ABI (Application Binary Interface) Risks** - **Status**: No explicit ABI changes mentioned. - **Potential**: Major updates often involve ABI changes, but the data does not confirm this. - **Recommendation**: Monitor for any implicit ABI changes (e.g., new APIs, deprecated functions). If applicable, update `BuildRequires` and `%check` to ensure compatibility. ##### **B. Security Risks** - **Status**: No specific CVEs or security vulnerabilities mentioned. - **Potential**: Fixes like BLS key preservation are critical for security, but no explicit threats are noted. - **Recommendation**: Ensure the package is tested for security compliance, especially if it’s used in production. ##### **C. CI/CD Impact** - **Status**: Major CI overhaul (Packit CI, TMT tests). - **Potential**: New tools may require updated dependencies or configurations. - **Recommendation**: Verify compatibility of `BuildRequires` and `%check` with the new CI tools. Test the package in the new environment. ##### **D. Upgrade Risks** - **Status**: Major update with improvements but no backward compatibility. - **Potential**: Potential for breaking changes (e.g., API differences, new features). - **Recommendation**: Test the package in a staging environment before deployment. Document any changes in `NEWS` or `ChangeLog`. --- #### **3. Recommendations** 1. **Update the Package**: - Apply the update to ensure all fixes and improvements are applied. - Verify compatibility with existing systems (e.g., CI/CD pipelines). 2. **Review `BuildRequires` and `%check`**: - Update `BuildRequires` to include new dependencies (e.g., TMT tools). - Adjust `%check` to include new tests (e.g., CI/CD tests). 3. **Test in Staging Environment**: - Deploy the package to a staging environment to validate functionality and compatibility. 4. **Monitor for Implicit ABI Changes**: - If the update introduces new APIs or deprecated functions, update the package accordingly. 5. **Document Changes**: - Update the `NEWS` or `ChangeLog` file to reflect the major update and its implications. --- #### **4. Conclusion** This major ### Источники, найденные web_search 1. <a href="https://github.com/ostreedev/ostree/releases/tag/v2026.1" target="_blank" rel="noopener noreferrer">GitHub release API: ostreedev/ostree v2026.1</a> 2. <a href="https://github.com/ostreedev/ostree/tree/v2026.1" target="_blank" rel="noopener noreferrer">GitHub tag page: ostreedev/ostree v2026.1</a> 3. <a href="https://github.com/ostreedev/ostree/releases" target="_blank" rel="noopener noreferrer">GitHub releases page: ostreedev/ostree</a> 4. <a href="https://github.com/ostreedev/ostree/compare/v2025.7...v2026.1" target="_blank" rel="noopener noreferrer">GitHub compare page: ostreedev/ostree v2025.7...v2026.1</a> 5. <a href="https://www.chegg.com/?msockid=00aeff7645c16d271e85e80f44b16c2f" target="_blank" rel="noopener noreferrer">Chegg - Get 24/7 Homework Help | Study Support Across 50+ Subjects</a> 6. <a href="https://github.com/ostreedev/ostree" target="_blank" rel="noopener noreferrer">GitHub - ostreedev/ostree: Operating system and container binary ...</a> 7. <a href="https://www.codeproject.com/articles/816861/calculator-sample-in-wcf-vb" target="_blank" rel="noopener noreferrer">Coding Education Platforms for Beginners | .Software</a> 8. <a href="https://glfs-book.github.io/slfs/general/ostree.html" target="_blank" rel="noopener noreferrer">OSTree-2026.1 - glfs-book.github.io</a> 9. <a href="https://en-gb.facebook.com/" target="_blank" rel="noopener noreferrer">Facebook – log in or sign up</a> 10. <a href="https://www.facebook.com/" target="_blank" rel="noopener noreferrer">Facebook</a> ## Upstream release notes / description This release includes several important bug fixes, most notably fixing soft-reboot handling for `var`, `sysroot`, and `boot` mounts, and preserving extension BLS keys across staged deployments. The libarchive integration now correctly handles UTF-8 filenames without locale dependency, and the dracut module was fixed to use the correct systemd unit directory. On the features side, `ostree admin status --json` now includes the deployment origin refspec. The CI infrastructure saw a significant overhaul: Packit CI was added with RPM builds and TMT integration tests, the test-tmt shell script was replaced with a Rust xtask, and Justfile targets were introduced for local development workflows. ## Bug Fixes - **libarchive**: Handle UTF-8 filenames without locale dependency - **state-overlay**: Fix `ENODATA` handling for GLib < 2.74 - **bootconfig**: Preserve extension BLS keys across staged deployments - **generator**: Fix soft-reboot for `var`, `sysroot`, and `boot` - **boot/dracut**: Use `systemdsystemunitdir` instead of `systemdsystemconfdir` ## Improvements - **status**: Include deployment origin refspec as refspec in JSON output ## CI & Testing - Revamp bootc integration test suite with bcvk VM support - Drop running COSA as UID 0 - Drop cosa fetch - Respect `TEST_TMPDIR` for temporary directories - Sync bootc-ubuntu-setup action from bootc-dev/infra - Add Packit CI with RPM builds and TMT integration tests - Remove bcvk VM dispatch from Rust integration tests - Replace test-tmt shell script with Rust xtask - Fix cargo build failure on Fedora 43/44 in `Containerfile.packit` - Extend `cargo fmt` check to cover all Rust crates - Sync Rust linting checks from bootc-dev/bootc - Fix `cargo fmt` formatting in tests/xtask - Remove unused `Kill9Stats` and `RebootStats` structs from tests/inst - Add Rust validate targets to Justfile for local development - Use Justfile targets in GitHub workflow and add missing `v2024_7` feature - Install `ca-certificates` in Debian Testing pre-checkout setup - Make `fuse` and `libfuse-dev` conditional for Debian Testing ## New Contributors * @lxnay made their first contribution in <a href="https://github.com/ostreedev/ostree/pull/3569" target="_blank" rel="noopener noreferrer">github.com — 3569</a> * @pvalena made their first contribution in <a href="https://github.com/ostreedev/ostree/pull/3572" target="_blank" rel="noopener noreferrer">github.com — 3572</a> * @henrywang made their first contribution in <a href="https://github.com/ostreedev/ostree/pull/3576" target="_blank" rel="noopener noreferrer">github.com — 3576</a> **Full Changelog**: <a href="https://github.com/ostreedev/ostree/compare/v2025.7...v2026.1" target="_blank" rel="noopener noreferrer">github.com — v2025.7...v2026.1</a> ## NiceOS maintainer checklist - [ ] Confirm that the detected version is a stable upstream release. - [ ] Check upstream changelog for security fixes, ABI/API changes and build-system changes. - [ ] Check ABI/API compatibility and reverse dependencies. - [ ] Download source into NiceOS lookaside storage. - [ ] Update `Version` and related fields in `SPECS/*.spec` only if policy allows it. - [ ] Regenerate `SOURCES/sources.lock.json`, manifests, metadata and SBOM. - [ ] Build SRPM/RPM in a clean NiceOS buildroot. - [ ] Run package smoke tests. - [ ] Link PR/build logs and close this issue after update or triage. ## Bot metadata - Tool: `niceos_upstream_monitor.py 2.1.3-local-websearch-github-release-pages` - Generated at: `2026-06-15T00:19:50Z`

sbelikov added the

labels

2026-04-28 01:38:18 +03:00