Michele Calgaro via trinity-devel wrote: Thank you, I now remember - it belongs to tdeutils. I have some questions Michele - why 14.2 ? I was hoping 14.1 is the candidate. - and as it is upstream in gnupg, how should I proceed. I recall there was something in git to track the original source. I do not think I fully qualify for creating PR for this particular case. Can you advise? thanks --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

Dne st 11. března 2020 Michele Calgaro via trinity-devel napsal(a): Hi both, in any case, we will need to make a decision about pinentry-tqt. As I understand, the code is now part of the upstream pinentry. Here are some ways to deal with this: 1. Add a separate git repository that will follow upstream pinentry but only pinentry-tqt will be built during build in TDE. There would have to be an occasional merge with upstream, but we should have our own branches, our own tags, out own issues tracking... just as we do with libtdevnc and libvnc upstream. 2. Add the pinentry-tqt code to tdeutils, as you mentioned. But this would mean manual synchronization between pinentry upstream and tdeutils. 3. Add only a mirror of pinentry git repository but not as part of the TDE umbrella. And the packages will be built completely outside the other TDE packages. What is your opinion? Cheers -- Slávek

Hi I dropped a mail to Damien Goutte-Gattat. Seems to be responsible for pinentry. Here is the essence of what he says [...] As mentioned in the bug 2830 I found out that actually I need to have pinentry-tqt and pinentry-tty, so that it does not conflict with dependencies from debian. the pinentry-tty is required for console only applications. The code can be obtained via git clone git://git.gnupg.org/pinentry.git because it was merged already. All the rest in the bug 2830 is correct. In the last note from 20.10.2018 I mean, when building TDE I do on each package sed -i "s/pinentry-qt/pinentry-tqt/" $(TGTDIR)"/debian/control" because of mentioned dependencies. So in my opinion what needs to be done is to take the decision how we deal with upstream pinentry and pimp all the packages that depend on pinentry-qt (so to speak do a switch to pinentry-tqt). Of course it needs to be done for each distribution. I have added only the debian part, but it does not seem to be that much of work - mostly decision and setup. When the decision is taken, I would love to do my part, especially now with most of the other topics I had closed and COVID19 knocking on the door, we may at once have much more time for development if the internet remains intact of course :) regards --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

Michele Calgaro via trinity-devel wrote: Is it expected that I do something here? regards --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting