rpms/NetworkManager
7
0
Fork 0
Code Issues Pull Requests Releases Activity

Update patch numbering

Browse Source 
As done in the c9s branch, use 0 as base for patches that change
behavior from upstream, and 1000 for backports. In this way, upon a
rebase we can drop all (1000+x) patches and keep others.

Related: RHEL-35580
This commit is contained in:
Beniamino Galvani 2024-06-20 10:14:29 +02:00
parent b49844bea1
commit b42cc4e3f2
2 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
0001-checkpoint-fix-port-reactivation-when-controller-is-.patch → 1001-checkpoint-fix-port-reactivation-when-controller-is-.patch
View File

10
NetworkManager.spec
View File

@ -219,8 +219,14 @@ Source7: 70-nm-connectivity.conf
Source8: readme-ifcfg-rh.txt Source8: readme-ifcfg-rh.txt
Source9: readme-ifcfg-rh-migrated.txt Source9: readme-ifcfg-rh-migrated.txt
#Patch1: 0001-some.patch # RHEL downstream patches that change behavior from upstream.
Patch1: 0001-checkpoint-fix-port-reactivation-when-controller-is-.patch # These are not bugfixes, hence they are also relevant after
# the next rebase of the source tarball.
# Patch0001: 0001-some.patch
# Bugfixes that are only relevant until next rebase of the package.
# Patch1001: 1001-some.patch
Patch1001: 1001-checkpoint-fix-port-reactivation-when-controller-is-.patch
Requires(post): systemd Requires(post): systemd
%if 0%{?fedora} || 0%{?rhel} >= 8 %if 0%{?fedora} || 0%{?rhel} >= 8