Note: currently there is no reiser4progs 1.1.0-1.1 for Debian Jessie AMD64 -- not even in backports repositories.

I built a Reiser4, new Software Format Release Number (SFRN) 4.0.1,--patched Linux kernel 4.4.6 on a local VirtualBox 5.0.16 Debian Jessie AMD64 instance. Subsequently I uploaded the resulting DEB package to one of my Google Compute Engine (GCE) cloud Reiser4 test instances, which was running the previous Reiser4 SFRN 4.0.0 -patched kernel. My newly built kernel installed smoothly; notwithstanding, I realized that I had to build the corresponding SFRN 4.0.1 reiser4progs 1.1.0-1.x to match the newly installed kernel, since:

NOTE: after mount in the new kernel you won' t be able to
check your partition by reiser4progs-1.0.9 and older versions, so
please upgrade your reiser4progs BEFORE. Everyone who relies on
liveCDs with reiser4progs-1.0.9, or older versions: be careful!¹

Although I had the necessary utilities with which I had built a 'debianized' kernel, I needed to²:

Shell

Note: make sure you have permission to write to your parent directory -- as the resulting U/DEBs will be created there.

Executing dch directive below is optional. I executed dch to edit debian/changelog and note that I am generating reiser4progs 1.1.0-1.x SFRN 4.0.1 for Debian Jessie.

Shell

Procedure will take a while and lots of data will pass across your terminal screen. After the procedure ends, check your parent directory with

Shell

libreiser4-dev_1.1.0-1.x_amd64.deb
mkreiser4-udeb_1.1.0-1.x_amd64.udeb
reiser4progs_1.1.0-1.x_amd64.deb
reiser4progs-udeb_1.1.0-1.x_amd64.udeb

where value of x depends on whether you used dch or not.

For userland we only need the generated *.deb files; the bonus UDEBs, i.e., generated *.udeb, are only needed for Debian-Installer (d-i) media.

¹ Reiser4: Format 4.0.1: Meta(data) checksums.
² From my modified reiser4progs 1.1.0.1 repository - which creates UDEBs as well as DEB packages.

DISCLAIMER:P although due diligence has been applied, this resource is made available for testing/evaluation purposes on an AS IS basis. The procedure only reflects my own modifications, my limited testing, and the potential user who executes the procedures assumes all risks.

Please do not hold me or Metztli Information Technology (and/or its associates) responsible if the information provided here does not achieve the desired result. The information is provided AS IS and with the hope that it may be useful to the Internet community --especially those interested in Reiser4 support on Debian.

Notwithstanding, There is no implicit or explicit guarantee that the information presented here is accurate --even though due diligence was exercised during the procedure. Accordingly, if an user(s) decide to implement the procedure or shell commands described here she, he, or them, do so at her, his, or their own risk. You have been forewarned.