qubes-gpg-split-2.0.7-1 not in template repo?

[J.M. Porup]

Installing split gpg on a new laptop, and I stumbled over this:


NOTE: A recent engimail update, version thunderbird-enigmail-1.7-1,
introduced changes in how Enigmail expects to execute GPG binary and so
requires an updated split-gpg package with version >=
qubes-gpg-split-2.0.7-1. Please make sure you have all the latest qubes
packages installed in your template.


According to my template vm, the latest version available of
qubes-gpg-split is 2.0.7. Do I need to enable a testing repo to get 2.0.7-1?

thanks
Jens

[J.M. Porup]

to answer my own question, for anyone interested, the problem is that
Split GPG is not compatible atm with TorBirdy. Here's the existing bug
report, with workaround:

https://www.mail-archive.com/tor-...@lists.torproject.org/msg67727.html

cheers
JMP

[Marek Marczykowski-Górecki]

That "-1" is package release number, not split-gpg version. In other
words qubes-gpg-split version 2.0.7 is the same as
qubes-gpg-split-2.0.7-1.

--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[Joonas Lehtonen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

J.M. Porup:

Yes,
>
I reported it some time ago, but now I think it would be
easier two change the split gpg wrapper instead of changing every
application that invokes gpg with parameters that are not supported by
the wrapper (maybe just emit a warning in such cases?).

https://bugs.torproject.org/14025
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJUxYO8AAoJENGIB/ssoMC27asP/judmkEmxS9BDEplA4TiWfb/
ECjVExEigl6HewUbDrclUDB5uqHJ3p1DBv4+zHUJr0Ma6Y4jnrrOkK0ehSggAut9
Hp6ABSgLqcq164XUfC1UDjhRjoh+W5UXrn13eE4/nUWi4yVikBMMdJzhFV4eLcIi
AtC7WGqYbNJEaF2XbG9E2+ewR+CPgj2YFw82BbZXnJO0Ry+7SZTaHN/8OymzUsx7
5GyB7VHsYg3bEJff+xv2CpdCq9qkRItbG0gjAHi4AJvViHe/D+e6A25fIRBYArT3
gZ9Q36+HZcatCzrcdVdfCG1z4cdI1gBRx8ITG+L7wIJj71dS7ECEaR8LGEGT9TYu
DoTR0GHOS71P8LtbQn3+b+YxO4N33xhjgVqFqOExoKgg1x6kHrCIqHloPlCYiU0B
h+A6KzzlsRKcc3CNcATcgNqFumGgwzZ0AJJokRd+D8V7o1NYU8KTOq6AV1F9wgE7
ahOXtHk9HwrXk43OGHKTY9mkW4a2FXS98lwVeYGOPzUJcK3ceWwQW91EK0nm8GlO
rydPGQd+KTa++9vGsiV1CjJoXPkOeAV02ptdJur3ud/IbJkuWM9FzSHmAOWXTVBM
i0H523W/TwCoINUF2Gui8O3zLi911+0oGSbap4fzxw999FaKlqoeCjF0ScplyFgO
QplLgj2561qjuM+E398A
=LI0L
-----END PGP SIGNATURE-----

[Joonas Lehtonen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Joonas Lehtonen:

> J.M. Porup:
>> to answer my own question, for anyone interested, the problem is
>> that Split GPG is not compatible atm with TorBirdy. Here's the
>> existing bug report, with workaround:
>
>> https://www.mail-archive.com/tor-...@lists.torproject.org/msg67727.html
>
>>
>
> Yes,
>
> I reported it some time ago, but now I think it would be easier two
> change the split gpg wrapper instead of changing every application
> that invokes gpg with parameters that are not supported by the
> wrapper (maybe just emit a warning in such cases?).
>
> https://bugs.torproject.org/14025

looks like an update is on its way:

https://github.com/QubesOS/qubes-issues/issues/1024#issuecomment-190443660
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJW3zl7AAoJENGIB/ssoMC2+gkQAMD1vJuT64VsOPpt93gYXQ1H
cc/zvZ8uRfFVwOslHFDD5WV/bfJIy7JhyNgGMtHwxaVC4q1YC9121KHBGdf6vpG9
MNTgphJMR34j2u1VZWoS2oWCIAHFovCi0xN0nASzqUKefIwJNQAVopEfYVjwwj1q
AoGkxQvjADAGmp7vFNYY+/1IkRl0CJJ5cvF0eRUTJLv0xfVDmRGRw5zMn5KnF0Qi
TR3Nzw2hVafTQNbGrckG1K7TKTE5/MjQix7KlKRnJPU3z284rQa1mgMDHQI83XiG
pOxju3iceSGLCqg/hK36LjWsUgKiCAF+pkGW4hg6zIGq0CCaaQcqyl1Ed3Ys6eFg
ago/AoLpo/XmpfRvdg3PtcBtAP2HecyuxWUxI7TLrzYz5q6UBJgKsUfg7lYSfUbn
L4MjvvH476Eyil/6ZjGpSXt90NEhCc7lLYx5UzRLhB6Ei7kUHCW1VaMlne0KkSRj
0KjZkXhaXV0EuVHGW4Ngmf02Iryj35fNkCxwS3O4ur8uFgzWRr0rbBcCGg4YV8on
TiegluU1DcY49HC2xSr//UBP4crxUcPt82HpPxPGmspxPAD+j/SL/EWKUG/1l+z4
qtml1InxKHX/dcVjRO4GPxA6ZPUlk1fZFEeK7SgVkosq8emG6mz6roBtZfInaIZ+
6HBR4RkM/RjhSscr+u7r
=xa3t
-----END PGP SIGNATURE-----