recutils has decryption features compiled out in utopic leaving rec files prepared in trusty inaccessible

[Sergio Callegari]

Recutils should include features to encrypt/decrypt specific fields. These operations are described in the recfix manual

      --encrypt
              encrypt confidential fields in the specified file.

       --decrypt
              decrypt confidential fields in the specified file.

These operations used to be supported in the recutils version in trusty. However they are compiled out of the utopic version.

As a consequence, all the rec files prepared with previous versions of ubuntu and including encrypted fields cannot be accessed in utopic.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: recutils 1.7-1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Nov 3 12:50:38 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-12 (325 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: recutils
UpgradeStatus: Upgraded to utopic on 2014-10-30 (3 days ago)

[Sergio Callegari (callegar)]

Fix available in my test ppa https://launchpad.net/~callegar/+archive/ubuntu/ppa/+packages.

Issue is wrong build dependencies.

Please SRU. As is recutils is actively preventing people from accessing their own data if they have applied some form of encryption.

[Sergio Callegari (callegar)]

Note that bug is also in debian packages, so please inform them so they can patch as well.

[Sergio Callegari (callegar)]

This bug has now been open for 2 release cycles.

As the reporter, I have identified the problem and built working packages in a PPA. After this, fixing the issue was a cut and paste away, with the cut and paste limited to two lines, but unfortunately this has not happened and now ubuntu vivid has exactly the same issue with recutils that utopic used to have.

Since there seems to be no interest in fixing the bug, I am closing it as invalid.