PR#457: Update f39 to upstream release 1.76.1 - rpms/linux-system-roles

rpms / linux-system-roles

#457 Update f39 to upstream release 1.76.1

Closed a month ago by rmeggins. Opened a month ago by packit.

rpms/ packit/linux-system-roles 1.76.1-f39-update-propose_downstream into f39

Packit • a month ago

af889a3

.gitignore

file modified

		`@@ -756,3 +756,4 @@`
		`/fapolicyd-1.1.2.tar.gz`
		`/bootloader-1.0.4.tar.gz`
		`/snapshot-1.3.2.tar.gz`
		`+ /ansible-sshd-v0.23.4.tar.gz`

CHANGELOG.md

file modified

+18

		`@@ -1,6 +1,13 @@`
		`Changelog`
		`=========`

		`+ [1.76.1] - 2024-04-07`
		`+ ---------------------`
		`+`
		`+ ### Bug Fixes`
		`+`
		`+ - sshd - fix: Document and streamline the sshd_main_config_file (#281)`
		`+`
		`[1.76.0] - 2024-04-05`
		`---------------------`

		`@@ -16,7 +23,18 @@`

		`- bootloader - fix: Add /etc/default/grub if missing (#93)`
		`- network - fix: Allow network to restart when wireless or team connection is specified (#675)`
		`+`
		`+ [1.75.4] - 2024-04-04`
		`+ ---------------------`
		`+`
		`+ ### Bug Fixes`
		`+`
		- rhc - a line `ansible_host=` to be put in the config file.
		`+`
		+ The former is a job of `{state: absent}`. An empty string should not cause such a desctructive operation. The latter is ignored by the Client and is equivatent to that line missing.
		`+`
		`+ Result:`
		`+ Consistently with a similar condition of the display_name parameter, an empty string ansible_host is treated as undefined. It's the same behavior as with a null value.`
		- rhc - the Ansible host name to be reset in the Inventory by `insights-client --ansible_host=`;
		`- rhc - fix: Ignore ansible_host: "" (#169)`

linux-system-roles.spec

file modified

+5 -2

		`@@ -23,7 +23,7 @@`
		`%endif`
		`Url: https://github.com/linux-system-roles`
		`Summary: Set of interfaces for unified system management`
		`- Version: 1.76.0`
		`+ Version: 1.76.1`
		`Release: 1%{?dist}`

		`License: GPLv3+ and MIT and BSD and Python`
		`@@ -135,7 +135,7 @@`
		`%global forgeorg15 https://github.com/willshersystems`
		`%global repo15 ansible-sshd`
		`%global rolename15 sshd`
		`- %deftag 15 v0.23.3`
		`+ %deftag 15 v0.23.4`

		`%global rolename16 ssh`
		`%deftag 16 1.3.3`
		`@@ -689,6 +689,9 @@`
		`%endif`

		`%changelog`
		`+ * Sun Apr 7 2024 Packit <hello@packit.dev> - 1.76.1-1`
		`+ - Update to upstream version 1.76.1`
		`+`
		`* Fri Apr 5 2024 Packit <hello@packit.dev> - 1.76.0-1`
		`- Update to upstream version 1.76.0`

sources

file modified

+1 -1

		`@@ -13,7 +13,7 @@`
		`SHA512 (nbde_client-1.2.18.tar.gz) = 8ef9654079c2c8f361a16af9e8378565318f9f3930f71d688b2213c214f858e9dd331faf645809ddf3f2ef1f48770873c8fe6bcb2938e2e73acc7eaec5881aec`
		`SHA512 (certificate-1.3.4.tar.gz) = 7fff3afd55836228cbd116e805e64855e390f2926eaa8dc5ca9c878f10a8171fd633257c32e27d391bd0e723a2138ff24e3fc6e5b10dead4e5fc39f3e84c3fe3`
		`SHA512 (crypto_policies-1.3.3.tar.gz) = 0bd3bc2d129dcad06d26bee6a5ea9296968f2885ca907d80b7cf4e12141eb3e2e47a7418aaa72e84df7d1642bb0c3d60c9bea2c8bed4a6d5be560467ecb59ba8`
		`- SHA512 (ansible-sshd-v0.23.3.tar.gz) = a491e1fde36233b9fc02701212568f4849edc232d9ccab76e5fdb7fc9603594ea68be221ec0a60b40df937b84d3699c16a5644388ed01fba2cbd12b5df636443`
		`+ SHA512 (ansible-sshd-v0.23.4.tar.gz) = dba48ef0949aadc2ba7374eff46c134687aface36bd82b99ba1e1ac52b43cf8b2315cd2cd6b6c62b10e1617e18fa96ce22ecee5e783550b5d3dc663f41b34a00`
		`SHA512 (ssh-1.3.3.tar.gz) = 5da0d102a0344eff983d00683aa4ccb5e5ef454e8360076954bffa015bc76a4ed4a31aa61200a310cf14e3f530d1b4d3b2c7fb3e491f49ca4e7d58c1ca3b85e0`
		`SHA512 (ha_cluster-1.16.0.tar.gz) = ae49a7c0de1f6afc965707931d3e24f4b4817800df17adb55650d8215943d0dfe7e231e17283db11f9d2c7176f7bddc2e191ca2d69a4ba0d8cf256a5b57b1026`
		`SHA512 (vpn-1.6.4.tar.gz) = 43f8c8195c32ba1573fb1213dc7b630121ee4d8ec1f9fff53df96afc1ce7deabdb0833cb68faaccaf67451a81eda23e1850a951c10918401381a27e98d379e8d`

packit commented a month ago

Upstream tag: 1.76.1
Upstream commit: 56d4074d

If you need to do any change in this pull request, you can clone Packit's fork and push directly to the source branch of this PR (provided you have commit access to this repository):

git clone ssh://$YOUR_USER@pkgs.fedoraproject.org/forks/packit/rpms/linux-system-roles.git
cd linux-system-roles
git checkout 1.76.1-f39-update-propose_downstream
git push origin 1.76.1-f39-update-propose_downstream

Alternatively, if you already have the package repository cloned, you can just fetch the Packit's fork:

cd linux-system-roles
git remote add packit ssh://$YOUR_USER@pkgs.fedoraproject.org/forks/packit/rpms/linux-system-roles.git
git fetch packit refs/heads/1.76.1-f39-update-propose_downstream
git checkout 1.76.1-f39-update-propose_downstream
git push packit 1.76.1-f39-update-propose_downstream

If you have the koji_build job configured as well, make sure to configure the allowed_pr_authors and/or allowed_committers (see the docs) since by default, Packit reacts only to its own PRs.

Before pushing builds/updates, please remember to check the new version against the packaging guidelines.

For example, please:

check that the new sources only contain permissible content
check that the license of the new version has not changed
check for any API/ABI and other changes that may break dependent packages
check the autogenerated changelog

:exclamation: Changed default for the changelog entry generated by Packit

We would like to bring to your attention a recent update regarding the default changelog entry generated by Packit during release syncing. Going forward, the default changelog entry will be generated as follows:

- Update to version {version}

followed by a Bugzilla reference if thereis an open bug about a new upstream release.
This aligns with the Fedora Packaging Guidelines and has been agreed upon in this discussion. If you prefer a different behaviour, you can override this default in your configuration, e.g. by using custom command(s) in changelog-entry action (see example).