Packit: Use packit for bumping official fedora package #231
Comments
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
Apr 28, 2023
Fixes: containers#231 Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
Apr 28, 2023
Fixes: containers#231 Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
Apr 28, 2023
Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
Apr 28, 2023
Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
|
SGTM |
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 1, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `container-selinux.spec` which gets synced with fedora dist-git on every upstream release. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 2, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `rpm/container-selinux.spec` which gets synced with fedora dist-git on every upstream release. The version in the new spec file is set to `0` by default and gets updated by packit automatically on every packit task. For local manual rpm builds using the spec, the helper script in the `rpm/` subdir will update the Version field with the latest version found in the upstream repo. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 2, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `rpm/container-selinux.spec` which gets synced with fedora dist-git on every upstream release. The version in the new spec file is set to `0` by default and gets updated by packit automatically on every packit task. For local manual rpm builds using the spec, the helper script in the `rpm/` subdir will update the Version field with the latest version found in the upstream repo. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 2, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `rpm/container-selinux.spec` which gets synced with fedora dist-git on every upstream release. The version in the new spec file is set to `0` by default and gets updated by packit automatically on every packit task. For local manual rpm builds using the spec, the helper script in the `rpm/` subdir will update the Version field with the latest version found in the upstream repo. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 2, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `rpm/container-selinux.spec` which gets synced with fedora dist-git on every upstream release. The version in the new spec file is set to `0` by default and gets updated by packit automatically on every packit task. For local manual rpm builds using the spec, the helper script in the `rpm/` subdir will update the Version field with the latest version found in the upstream repo. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
lsm5
added a commit
to lsm5/container-selinux
that referenced
this issue
May 2, 2023
Get rid of `container-selinux.spec.rpkg` in favour of `rpm/container-selinux.spec` which gets synced with fedora dist-git on every upstream release. The version in the new spec file is set to `0` by default and gets updated by packit automatically on every packit task. For local manual rpm builds using the spec, the helper script in the `rpm/` subdir will update the Version field with the latest version found in the upstream repo. Packit will automatically create a PR on fedora dist-git on every new upstream release. A sample PR will look like: https://src.fedoraproject.org/rpms/container-selinux/pull-request/10# A dry run for this can be triggered using: `$ packit propose-downstream --local-content` To run this command locally, you would need to have your packit user-configuration-file set. Ref: https://packit.dev/docs/configuration/#user-configuration-file along with a fedora api key created at: https://src.fedoraproject.org/settings#nav-api-tab with sufficient ACLs. Fixes: containers#231 Co-authored-by: František Lachman <[email protected]> Signed-off-by: Lokesh Mandvekar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Next time we cut a release, I'd like to try a complete packit workflow for bumping the official Fedora package and see how it goes.
The text was updated successfully, but these errors were encountered: