#2819 PR merged: Preparations for ReaR 2.7

Labels: enhancement, fixed / solved / done

jsmeix opened issue at 2022-06-09 08:58:

jsmeix commented at 2022-06-09 11:23:

Tomorrow I will try to somehow generate a
from what I have in


Convert the release notes from the ReaR web pages into a simple text file:

w3m -dump -cols 78 http://relax-and-recover.org/documentation/release-notes-2-xx | iconv -f UTF-8 -t ASCII//TRANSLIT | sed -e 's/^      ? /      - /' > doc/rear-release-notes.txt

but this requires to have the ReaR 2.7 release notes
published on http://relax-and-recover.org/documentation/
before ReaR 2.7 was actually released which I like to avoid.

jsmeix commented at 2022-06-09 13:09:

I will revert my here added changes of
when that pull request is merged.

I added them mainly because I was confused
about the failing automated build test
so I thought I just try to add the changes of
to see how things behave then here.

jsmeix commented at 2022-06-14 14:28:

In https://github.com/rear/rear/pull/2819/commits/c09ee23e5dc715257374853c31631b7c587d0b8c
I created doc/rear-release-notes.txt from

cat release-notes-2-7.md | pandoc -t plain --columns=78 | iconv -f UTF-8 -t ASCII//TRANSLIT >rear-release-notes.txt

plus then manual correction of some very long lines
(i.e. I had to manually wrap some too long lines via vi).

I checked for '?' characters that iconv ... -t ASCII//TRANSLIT
may result when characters cannot be transliterated

# grep '?' doc/rear-release-notes.txt

    shouldn't it [ReaR] restore the [RAID] arrays with the same UUIDs ...?" in
    unix exists but no module file?". Furthermore ensure that kernel modules
    -   https://bugzilla.redhat.com/show_bug.cgi?id=1239009 (f22)
    -   https://bugzilla.redhat.com/show_bug.cgi?id=1238843 (rhel 7.2)
best choice? We have done some tests and published the results. See

In all those lines the '?' characters are correct
(same text appears in the release-notes-2-7.md input)
so no characters were not transliterated by
iconv ... -t ASCII//TRANSLIT

I checked that the output is pure ASCII:

# file doc/rear-release-notes.txt

doc/rear-release-notes.txt: ASCII text

(for UTF-8 file reports "UTF-8 Unicode text").

jsmeix commented at 2022-06-14 14:56:

I added missing http... link URLs
in doc/rear-release-notes.txt

The above pandoc -t plain converts markdown

[Link text](http...)

to plain text

Link text

but ignores the link URL http...
so I added the missing link URLs manually
for what I found in the markdown via

# grep '](' release-notes-2-7.md

By the way:
Those link URLs are also missing in our current
ReaR 2.6 release notes
which contain (excerpt):

Relax-and-Recover website

GitHub project


[Relax-and-Recover website](http://relax-and-recover.org/)

[GitHub project](https://github.com/rear/)

jsmeix commented at 2022-06-15 13:47:

I added Renaud Metrich and pcahyna to the AUTHORS section in doc/rear.8.adoc
and replaced some 'please' therein with better wording and made it plain ASCII
and then regenerated doc/rear.8 via 'asciidoctor -b manpage rear.8.adoc'
so now also rear.8 is plain ASCII.


* Convert the release notes from the ReaR web pages
  into a simple text file

* Add the list of contributors which did something
  for this new release via
  (in this example the previous release was 2.6):

  git log --format="%aN" $(git merge-base master 2.6)..master | sort -u | sed -e 's/,/, /g'

* review doc/rear-release-notes.txt for broken lines
  (visual check)

so I guess "Add the list of contributors" means
to add them to the release notes
but our current ReaR 2.6 release notes
do not contain a list of contributors
and I don't like to add such a list now there.

So I only updated the AUTHORS section in doc/rear.8.adoc
and regenerated doc/rear.8

jsmeix commented at 2022-06-15 13:51:

I think this pull request is now complete
so it could be merged into current master code
provided at least both of you
@gdha and @pcahyna
agree (i.e. when you approve this pull request)
and unless one of

jsmeix commented at 2022-06-15 13:55:

Next week I would like to

Announce freeze period and ask for community testing
on rear-users@lists.relax-and-recover.org

according to

such a "freeze period" does not mean
cannot be fixed. Of course we can still do
all what is required to release ReaR 2.7.

jsmeix commented at 2022-06-20 11:37:

Mainly for my own information regarding

Announce freeze period and ask for community testing
on rear-users@lists.relax-and-recover.org

For ReaR 2.6 and 2.5 I don't find such mails on

For ReaR 2.4 I only found the "New release ReaR v2.4 announcement"

For ReaR 2.3 I found both the "Pre-ReaR version 2.3 freeze period"
and the "Announcement: New release of Rear v2.3"

jsmeix commented at 2022-06-22 10:34:


Announce freeze period and ask for community testing
on rear-users@lists.relax-and-recover.org

Yesterday I sent the mail below
but nothing appeared in my mail folder
and also nothing appeared on

My sent mail is basically inexplicably lost in nowhere.
I got no failure notice from a mail server or something like that.

Because we did not send such a mail for ReaR 2.6 and 2.5
I won't worry if we omit that also for ReaR 2.7.

Announcement: ReaR version 2.7 release approaching

To [rear-users@lists.relax-and-recover.org](mailto:rear-users@lists.relax-and-recover.org) on 2022-06-21 10:58

Dear ReaR users and contributors,

the next ReaR version 2.7 release is approaching.

The last ReaR 2.6 release was two years ago
so there are many changes for the new ReaR 2.7.

See our current ReaR 2.7 release notes at


in particular for new features, bigger enhancements,
and possibly backward incompatible changes.

The planned ReaR 2.7 release date is end June 2022.

Until then we will not do bigger code changes
(except needed fixes for serious issues)
to keep our ReaR upstream master code stable
so we can do some basic general testing
before we release it.

Because we can only test generic things
we would appreciate it if you could test
our current ReaR upstream master code
in particular if it still works as well
as the ReaR version that you currently use
in your specific enviroment.

Testing ReaR upstream GitHub master code:

It is possible to have several ReaR versions in parallel
each one in its own separated directory without conflicts
between each other and without conflicts with a normally
installed ReaR version (e.g. via an RPM package).

Accordingly you can test our ReaR upstream master code
from within a separated directory to find out if things
work better or worse with ReaR upstream master code
compared to the ReaR version that you currently use.

Basically "git clone" the ReaR upstream master code
into a separated directory and then configure
and run ReaR from within that directory like:
# git clone https://github.com/rear/rear.git

# mv rear rear.github.master

# cd rear.github.master

# vi etc/rear/local.conf

# usr/sbin/rear -D mkbackup
Note the relative paths "etc/rear/" and "usr/sbin/".

Please report issues via the [New issue] button on

Please also provide feedback (e.g. as reply to this mail)
when you tested our ReaR upstream master code
and it works without issues for you.

Many thanks in advance for your testing and
best regards from the ReaR upstream team!

Johannes Meixner

jsmeix commented at 2022-06-27 05:41:


Meanwhile I got an
"Undelivered Mail Returned to Sender"
notice for my above mail:

From  MAILER-DAEMON@service.3ti.be
To    jsmeix@suse.de
Date  Sun 11:17

This is the mail system at host service.3ti.be.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<[rear-users@mailservice.3ti.be](mailto:rear-users@mailservice.3ti.be)> (expanded from
    <[rear-users@lists.relax-and-recover.org](mailto:rear-users@lists.relax-and-recover.org)>): delivery temporarily suspended:
    connect to[]:10024: Connection refused

Reporting-MTA: dns; service.3ti.be
X-Postfix-Queue-ID: 889A41602CE
X-Postfix-Sender: rfc822; [jsmeix@suse.de](mailto:jsmeix@suse.de)
Arrival-Date: Tue, 21 Jun 2022 10:58:57 +0200 (CEST)

Final-Recipient: rfc822; [rear-users@mailservice.3ti.be](mailto:rear-users@mailservice.3ti.be)
Original-Recipient: rfc822;[rear-users@lists.relax-and-recover.org](mailto:rear-users@lists.relax-and-recover.org)
Action: failed
Status: 4.4.1
Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to[]:10024: Connection refused

pcahyna commented at 2022-06-29 21:52:

I checked my e-mail and I have not received it. My last message from rear-users was on Tue, 25 Jan 2022 "Re: [rear-users] canĀ“t format USB Sticke"

pcahyna commented at 2022-06-29 21:54:

If you rebase on top of master, Packit will build rear-2.7 RPMs for you.

jsmeix commented at 2022-06-30 07:08:

I changed doc/rear.8 manually with vi
and after that git diff shows:

diff --git a/doc/rear.8 b/doc/rear.8
index 0ad3ad8d..9fa07c27 100644
--- a/doc/rear.8
+++ b/doc/rear.8
@@ -888,7 +888,7 @@ Sebastien Chabrolles (\c
 Renaud Metrich (\c
 .URL "https://github.com/rmetrich" "" ")"
-"pcahyna" (\c
+Pavel Cahyna (\c
 .URL "https://github.com/pcahyna" "" ")."
 We hope that ReaR continues to prove useful and to attract more developers who agree to be maintainers.
 Refer to the MAINTAINERS (\c
@@ -915,4 +915,4 @@ The copyright is held by the original authors of the respective code pieces as c
 Relax\-and\-Recover comes with ABSOLUTELY NO WARRANTY; for details
 see the GNU General Public License at \c
-.URL "http://www.gnu.org/licenses/gpl.html" "" ""
\ No newline at end of file
+.URL "http://www.gnu.org/licenses/gpl.html" "" ""

which means the before generated doc/rear.8 via

asciidoctor -b manpage rear.8.adoc

cf. https://github.com/rear/rear/pull/2819#issuecomment-1156497530
did not have a newline at end of file
so I will have to check why this happens
(all regular text files should have a newline at end of file).

jsmeix commented at 2022-06-30 07:18:

Regarding rear-users@lists.relax-and-recover.org
yes, the last mails I got are those that are shown on

do you know if the ReaR mailing lists shown at
should still work or if they are perhaps dead meanwhile?

jsmeix commented at 2022-06-30 10:49:

@gdha @schlomo
seems to be related and indicates some general issue
with the ReaR mailing lists that are shown at

gdha commented at 2022-07-08 09:28:

@jsmeix I have tested rear-2.7 candidate on RHEL 9, but that is not yet mentioned in the release notes I noticed. For the rest - wow excellent and well done.

jsmeix commented at 2022-07-12 11:17:

thank you for having a look at my changes.

I assume you mean the following section
in the current release notes text:

ReaR 2.7 is supported on the following Linux based operating systems:

-   Fedora 29, 30, 31, and 32
-   RHEL 6, 7, and 8
-   CentOS 6, 7, and 8
-   Scientific Linux 6 and 7

I can add RHEL 9 to the line about RHEL
but I don't know about the other Fedora based distributions.

According to
RHEL 9 is based on Fedora 34
so ReaR 2.7 should support Fedora 34
but what about later Fedora versions?

According to
there is no CentOS 9
so there is nothing to change for the CentOS line.

According to
there is no Scientific Linux 8 or 9
so there is nothing to change for the Scientific Linux line.

jsmeix commented at 2022-07-12 12:08:

With my last
I have now this text (excerpt):

ReaR 2.7 is supported on the following Linux based operating systems:

-   Fedora 29, 30, 31, 32, 33, and 34
-   RHEL 6, 7, 8, and 9
-   CentOS 6, 7, and 8
-   Scientific Linux 6 and 7

@gdha @pcahyna
is this OK for you?

jsmeix commented at 2022-07-12 13:19:

@gdha @pcahyna @rear/contributors
I would like to merge this pull request
tomorrow afternoon unless there are objections.

[Export of Github issue for rear/rear.]