F41 Change Proposal: Multiple Versioned CRI-O and CRI-Tools Packages (self-contained)

2024-05-08 Thread Aoife Moloney
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

Wiki - https://fedoraproject.org/wiki/Changes/VersionedCRI-OandCRI-ToolsPackages
Discussion Thread -
https://discussion.fedoraproject.org/t/f41-change-proposal-multiple-versioned-cri-o-and-cri-tools-packages-self-contained/116526

== Summary ==
The installed versions of CRI-O and CRI-Tools are supposed to match
the version of Kubernetes that they are deployed with. FESCo recently
approved multiple, versioned packages for Kubernetes
(https://fedoraproject.org/wiki/Changes/VersionedKubernetesPackages).
This Change Request, if approved, will allow Fedora to also provide
matching versions of CRI-O and CRI-Tools for Kubernetes administrators
that use Fedora as the base machine OS.

== Owner ==
* Name: [[User:Buckaroogeek| Brad Smith]]
* Email: bradley.g.sm...@gmail.com

* Name: [[User:haircommander| Peter Hunt]]
* Email: peh...@redhat.com


== Detailed Description ==
Both CRI-O (https://src.fedoraproject.org/rpms/cri-o, upstream:
https://github.com/cri-o/cri-o) and CRI-Tools
(https://src.fedoraproject.org/rpms/cri-tools, upstream:
https://github.com/kubernetes-sigs/cri-tools) are designed to version
match the version of Kubernetes they are deployed with. Version
matching is a guarantee to Kubernetes administrators that these
components use the same API version of the target Kubernetes
installation.

Starting in Fedora 41, users will be able to install any supported
version of Kubernetes (typically 3 concurrent, supported versions)
using, for example, "dnf install kubernetes1.30". This Change, if
approved would allow the user to also install CRI-O and/or CRI-Tools
with the same version, i.e. "dnf install cri-o1.30 kubernetes1.30" or
"dnf install cri-tools1.30" to work with any version 1.30 CRI
(Container Runtime Interface) implementation.

CRI-O is a well-regarded CRI implementation. Each Kubernetes cluster
requires a CRI implementation such as cri-o to function. Alternatives
include containerd or Docker Engine among others.

CRI-Tools contains the crictl command line interface tool that
provides a CLI for CRI-compatible container runtimes. This allows the
CRI runtime developers to debug their runtime without needing to set
up Kubernetes components.

== Feedback ==
TBD

== Benefit to Fedora ==

Enthusiasts and kubernetes administrators and developers will have
access to the full stack of properly versioned components to install
and manage a Kubernetes cluster directly from Fedora repositories. All
supported versions of Kubernetes and related components such as CRI-O
and CRI-Tools will be available in each of the supported releases of
Fedora, starting with Fedora 41.

The past practice of tying a specific version of Kubernetes to a
release of Fedora created an unnecessary tight coupling between Fedora
and Kubernetes for cluster administrators and developers. In order to
change the version of either Kubernetes or Fedora, the version of the
other component also needed to change. This proposal provides changes
that finalize the uncoupling of Fedora releases and Kubernetes cluster
versions.

== Scope ==
* Proposal owners: Request appropriate src.fedoraproject.org
repositories from Fedora engineering and maintain those repositories.

* Policies and guidelines: N/A (not needed for this Change)

* Trademark approval: N/A (not needed for this Change)

* Alignment with the Fedora Strategy: This proposal enhances Fedora's
strengths in Technology and Innovation as it enhances the use of
Fedora to function as the machine OS for any supported version of
Kubernetes and as the administrator's workstation for all supported
Kubernetes clusters regardless of where the cluster is deployed.

== Upgrade/compatibility impact ==
The shift from the existing model to the versioned model could create
friction for current users of CRI-O or CRI-Tools on Fedora. Proper use
of Provides and Obsoletes in the spec files as well as a supporting
communication plan will help to reduce those complications.


== Early Testing (Optional) ==

Do you require 'QA Blueprint' support? N

== How To Test ==
# 1. Install a versioned CRI-O or CRI-Tools package on a fresh
instance of Fedora. Install should be error free.
# 2. On an existing Fedora machine, replace a non-versioned CRI-O or
CRI-Tools package with a versioned package. There should not be any
errors.



== User Experience ==
The user experience should remain unchanged except for the need to
select a specific version of CRI-O or CRI-Tools.




== Dependencies ==
No direct dependencies. If Kubernetes is installed and used then CRI-O
and Kubernetes should have the same major:minor version. As a command
line tool,  the version of CRI-Tools will be selected by the user
based on their specific requirements and needs.


Orphaned packages looking for new maintainers

2024-05-08 Thread Maxwell G
Report started at 2024-05-06 17:14:29 UTC

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

Request package ownership via the *Take* button in the left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://a.gtmx.me/orphans/orphans.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

Package  (co)maintainers   Status Change

bti   orphan   2 weeks ago  
container-workflow-tool   orphan   5 weeks ago  
emacs-htmlize orphan   6 weeks ago  
golang-github-elves-elvish@go-sig, orphan  2 weeks ago  
golang-github-xiaq-persistent @go-sig, orphan  2 weeks ago  
jolokia-jvm-agent orphan   4 weeks ago  
mingw-cppunit orphan   0 weeks ago  
mingw-freeimage   orphan   4 weeks ago  
mozilla-fira-fontsmaxamillion, orphan  0 weeks ago  
neofetch  orphan   0 weeks ago  
php-bantu-ini-get-wrapper adamwill, orphan 6 weeks ago  
php-christophwurst-id3parser  orphan   6 weeks ago  
php-deepdiver-zipstreamer orphan   6 weeks ago  
php-doctrine-dbal orphan, remi 6 weeks ago  
php-fgrosse-phpasn1   orphan   6 weeks ago  
php-giggsey-localeorphan   6 weeks ago  
php-league-uri-interfaces orphan   6 weeks ago  
php-opencloud-openstack   orphan   6 weeks ago  
php-opis-closure  orphan, remi 6 weeks ago  
php-pimpleorphan   6 weeks ago  
php-punic orphan   6 weeks ago  
php-scssphp   orphan   6 weeks ago  
php-stecman-symfony-console-  orphan   6 weeks ago  
completion  
prometheus-jmx-exporter   orphan   4 weeks ago  
prometheus-simpleclient-java  orphan   4 weeks ago  
python-jose   orphan   5 weeks ago  
rust-clap_lex @rust-sig, orphan0 weeks ago  
rust-digest_auth  @rust-sig, orphan0 weeks ago  
rust-lev_distance @rust-sig, orphan0 weeks ago  
rust-stratisd_proc_macros @rust-sig, bgurney, mulhern, 1 weeks ago  
  orphan
snakeyaml mizdebsk, orphan, sbluhm 4 weeks ago  
vim-editorconfig  orphan   4 weeks ago  
wdune orphan   1 weeks ago  

The following packages require above mentioned packages:
Depending on: golang-github-xiaq-persistent (1), status change: 2024-04-19 (2 
weeks ago)
golang-github-elves-elvish (maintained by: @go-sig, orphan)
golang-github-elves-elvish-0.15.0-11.fc40.src requires 
golang(github.com/xiaq/persistent/hash) = 0-0.12.20210113git3175cfb.fc40, 
golang(github.com/xiaq/persistent/hashmap) = 0-0.12.20210113git3175cfb.fc40, 
golang(github.com/xiaq/persistent/vector) = 0-0.12.20210113git3175cfb.fc40
golang-github-elves-elvish-devel-0.15.0-11.fc40.noarch requires 
golang(github.com/xiaq/persistent/hash) = 0-0.12.20210113git3175cfb.fc40, 
golang(github.com/xiaq/persistent/hashmap) = 0-0.12.20210113git3175cfb.fc40, 
golang(github.com/xiaq/persistent/vector) = 0-0.12.20210113git3175cfb.fc40

Depending on: mozilla-fira-fonts (1), status change: 2024-05-03 (0 weeks ago)
apostrophe (maintained by: atim)

Orphaned packages looking for new maintainers

2024-05-08 Thread Maxwell G
Report started at 2024-04-27 20:06:57 UTC

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

Request package ownership via the *Take* button in the left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://a.gtmx.me/orphans/orphans.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

Package  (co)maintainers   Status Change

bamf  orphan   0 weeks ago  
bti   orphan   0 weeks ago  
container-workflow-tool   orphan   4 weeks ago  
emacs-htmlize orphan   5 weeks ago  
golang-github-elves-elvish@go-sig, orphan  1 weeks ago  
golang-github-xiaq-persistent @go-sig, orphan  1 weeks ago  
jolokia-jvm-agent orphan   2 weeks ago  
mingw-freeimage   orphan   2 weeks ago  
php-aws-sdk3  orphan   4 weeks ago  
php-bantu-ini-get-wrapper adamwill, orphan 4 weeks ago  
php-christophwurst-id3parser  orphan   4 weeks ago  
php-deepdiver-zipstreamer orphan   4 weeks ago  
php-doctrine-dbal orphan, remi 4 weeks ago  
php-fgrosse-phpasn1   orphan   4 weeks ago  
php-giggsey-localeorphan   4 weeks ago  
php-guzzlehttp-guzzle6orphan   4 weeks ago  
php-league-uri-interfaces orphan   4 weeks ago  
php-opencloud-openstack   orphan   4 weeks ago  
php-opis-closure  orphan, remi 4 weeks ago  
php-pimpleorphan   4 weeks ago  
php-punic orphan   4 weeks ago  
php-ralouphie-getallheaders   orphan   4 weeks ago  
php-scssphp   orphan   4 weeks ago  
php-stecman-symfony-console-  orphan   4 weeks ago  
completion  
prometheus-jmx-exporter   orphan   2 weeks ago  
prometheus-simpleclient-java  orphan   2 weeks ago  
python-jose   orphan   3 weeks ago  
rust-stratisd_proc_macros @rust-sig, bgurney, mulhern, 0 weeks ago  
  orphan
snakeyaml mizdebsk, orphan, sbluhm 2 weeks ago  
vim-editorconfig  orphan   3 weeks ago  
wdune orphan   0 weeks ago  

The following packages require above mentioned packages:
Depending on: bamf (16), status change: 2024-04-22 (0 weeks ago)
deepin-daemon (maintained by: @deepinde-sig, @go-sig, cheeselee, zsun)
deepin-daemon-5.14.44-8.fc40.x86_64 requires bamf-daemon = 
0.5.6-1.fc41, deepin-session-ui = 5.6.2-3.fc40

plank (maintained by: filiperosset)
plank-0.11.89-15.20210202.git013d051.fc40.src requires 
pkgconfig(libbamf3) = 0.5.6
plank-0.11.89-15.20210202.git013d051.fc40.x86_64 requires 
bamf-daemon = 0.5.6-1.fc41
plank-devel-0.11.89-15.20210202.git013d051.fc40.i686 requires 
pkgconfig(libbamf3) = 0.5.6
plank-devel-0.11.89-15.20210202.git013d051.fc40.x86_64 requires 
pkgconfig(libbamf3) = 0.5.6
plank-libs-0.11.89-15.20210202.git013d051.fc40.i686 requires 
libbamf3.so.2
plank-libs-0.11.89-15.20210202.git013d051.fc40.x86_64 requires 
libbamf3.so.2()(64bit)

deepin-calendar (maintained by: @deepinde-sig, cheeselee, felixonmars, 
zsun)
deepin-calendar-5.10.0-3.fc40.x86_64