#3389 PR `merged`: 2.9 release preparations¶

Labels: fixed / solved / done, ReaR Project

pcahyna opened issue at 2025-01-28 15:33:¶

jsmeix commented at 2025-02-03 12:54:¶

According to
https://github.com/rear/rear/releases/tag/rear-2.9
the 'rear-2.9' tagged commit is
https://github.com/rear/rear/commit/e89f78abc92c264647068fe540a40d349d8a5671
so by this commit ReaR 2.9 was released
on "Fri Jan 31 21:08:36 2025 +0100".

Accordingly I assume our rear/rear master branch is again
open for all further development towards ReaR 3.0, see
https://github.com/rear/rear.github.com/pull/25#issuecomment-2627067661
and subsequent comments therein.

pcahyna commented at 2025-02-03 21:37:¶

@jsmeix , correct. I also tagged 2.9 despite originally thinking that it will not be needed. The reason is that GitHub creates a download tarball wit the top level directory named {project}-{tag}, so if the tag is rear-2.9, you will get a tarball with a rear-rear-2.9 directory, which is confusing and ugly. I thought that having the tag called rear-2.9 will help to achieve tarball file name like rear-2.9.tar.gz, which is much better when downloading than 2.9.tar.gz, but it turns out this is easily achievable even without naming the tag rear-2.9: just use an URL like https://github.com/rear/rear/archive/2.9/rear-2.9.tar.gz . The part after the last slash is entirely arbitrary, so one can have the file named as one wants. See the example at https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/#_git_tags .

jsmeix commented at 2025-02-04 07:34:¶

In https://github.com/rear/rear/wiki/Release-process
I added a reference link to the above
https://github.com/rear/rear/pull/3389#issuecomment-2632131305
why there are two tags 'rear-2.X' and '2.X'

jsmeix commented at 2025-02-06 09:35:¶

FYI regarding OBS builds:

OBS has now
https://build.opensuse.org/package/show/Archiving:Backup:Rear/rear-2.9

By the way I cleaned up OBS builds:

I removed all OBS build targets where ReaR fails to build
which are RHEL_6 RHEL_7 and ScientificLinux_7 cf.
https://github.com/rear/rear/issues/3238#issuecomment-2556857719

I removed Archiving:Backup:Rear/rear-2.6
because it is old and outdated so currently we have

# osc list Archiving:Backup:Rear
ebiso
rear-2.7
rear-2.8
rear-2.9

and all build successfully where build is enabled

# osc results -v Archiving:Backup:Rear
 ebiso
 | rear-2.7
 | | rear-2.8
 | | | rear-2.9
   . . .  15.5 ppc64le (published)
   . . .  15.5 x86_64 (published)
   . . .  15.6 ppc64le (published)
   . . .  15.6 x86_64 (published)
   . . .  CentOS_7 ppc64le (published)
   . . .  CentOS_7 x86_64 (published)
   . . .  CentOS_8 ppc64le (published)
   . . .  CentOS_8 x86_64 (published)
   . . .  Debian_11 x86_64 (published)
   . . .  Debian_12 x86_64 (published)
   . . .  Fedora_40 x86_64 (published)
   . . .  Fedora_41 x86_64 (published)
   . . .  SLE_12_SP5 ppc64le (published)
 . . . .  SLE_12_SP5 x86_64 (published)
   . . .  SLE_15_SP3 ppc64le (published)
 . . . .  SLE_15_SP3 x86_64 (published)
   . . .  openSUSE_Tumbleweed i586 (published)
   . . .  openSUSE_Tumbleweed x86_64 (published)
   . . .  xUbuntu_20.04 x86_64 (published)
   . . .  xUbuntu_22.04 x86_64 (published)
   . . .  xUbuntu_24.04 x86_64 (published)
   . . .  xUbuntu_24.10 x86_64 (published)

 Legend:
  . succeeded           
    disabled

I keep 'ebiso' for SLE12, cf. my comment in
current rear-2.9.spec

# osc cat Archiving:Backup:Rear rear-2.9 rear.spec
...
%if %{?suse_version:1}0
Requires: iproute2
# Make USE_DHCLIENT="yes" working by default:
Recommends: dhcp-client
# Since SLES11 there is an extra nfs-client package:
Recommends: nfs-client
# Use xorrisofs by default to create a UEFI-bootable ReaR recovery system ISO image
# see https://github.com/rear/rear/issues/3084#issuecomment-2330996873
# In SLES11 and SLES12 there was
# /usr/bin/genisoimage provided by the genisoimage RPM and there is
# /usr/bin/mkisofs provided by the cdrkit-cdrtools-compat RPM and
# both RPMs are installed by default so we do not need RPM Recommends for them.
# In openSUSE Leap 15 and SLES15 there is no longer /usr/bin/genisoimage
# but there is /usr/bin/mkisofs provided by the mkisofs RPM.
# But we do not need a RPM Recommends for mkisofs because
# in openSUSE Leap 15 and SLES15 there is the better tool /usr/bin/xorrisofs
# which is provided by the xorriso RPM which supports UEFI booting for ISOs
# so with xorrisofs the SUSE specific tool 'ebiso' is no longer needed
# see https://github.com/rear/rear/issues/3084#issuecomment-1833496190
# and xorrisofs is used in ReaR by default as preferred method to make an ISO image.
# In the end we only recommend xorriso for creating (UEFI-bootable) ISOs:
Recommends: xorriso
%endif
...

Currently 'Recommends: xorriso'
and 'Requires: bc' is only for SUSE
because I don't know how the matching RPM packages
are named for other RPM based distributions.

[Export of Github issue for rear/rear.]

#3389 PR merged: 2.9 release preparations¶