Quoting Olly Betts (2018-06-14 22:46:54)
> I've already made an upload, but it looks like there are some changes
> there since the last upload (at least to debian/copyright). I'll sort
> out merging them and doing another upload, though I might let the
> first upload migrate to testing first,
On Thu, Jun 14, 2018 at 11:13:04AM +0200, Jonas Smedegaard wrote:
> Quoting Olly Betts (2018-06-14 04:29:27)
> > On Thu, Jun 14, 2018 at 12:45:38AM +0200, Jonas Smedegaard wrote:
> >> I still like pinot and believe there is a use for it in Debian as
> >> alternative to extract and tracker. But
Quoting Olly Betts (2018-06-14 04:29:27)
> On Thu, Jun 14, 2018 at 12:45:38AM +0200, Jonas Smedegaard wrote:
>> I still like pinot and believe there is a use for it in Debian as
>> alternative to extract and tracker. But evidently it keeps falling
>> too low on my priority list :-(
>>
>>
On Thu, Jun 14, 2018 at 12:45:38AM +0200, Jonas Smedegaard wrote:
> I still like pinot and believe there is a use for it in Debian as
> alternative to extract and tracker. But evidently it keeps falling too
> low on my priority list :-(
>
> Please do adopt it. Or co-maintain it with me, if
Quoting Olly Betts (2018-05-31 23:47:10)
> On Thu, May 31, 2018 at 12:22:58AM +0200, Sebastian Andrzej Siewior wrote:
>> pinot has currently two RC bugs and failed to build during the curl4
>> transition / binNMU.
>> Does it make sense to add the two patches (Olly pointed to) and
>> upload it or
On Thu, May 31, 2018 at 12:22:58AM +0200, Sebastian Andrzej Siewior wrote:
> pinot has currently two RC bugs and failed to build during the curl4
> transition / binNMU.
> Does it make sense to add the two patches (Olly pointed to) and upload
> it or would a RM make sense?
Popcon suggests pinot
On 2017-03-01 12:53:23 [+1300], Olly Betts wrote:
> Upstream addressed this by avoiding linking libxapianbackend.so to
> openssl (apparently it doesn't use it anyway):
>
> https://github.com/FabriceColin/pinot/commit/3a40d5abe159a106f3aabaedf1a199020946b3b5
pinot has currently two RC bugs and
Control: tags -1 + fixed-upstream patch
Upstream addressed this by avoiding linking libxapianbackend.so to
openssl (apparently it doesn't use it anyway):
https://github.com/FabriceColin/pinot/commit/3a40d5abe159a106f3aabaedf1a199020946b3b5
Cheers,
Olly
Package: pinot
Version: 1.05-1.1+b1
Severity: serious
Justification: Policy 2.2.1
Bad news everyone - pinot links libxapian (which is GPLv2+) and openssl
(which has a GPLv2+-incompatible advertising clause in its licence) into
the same binary:
$ ldd
9 matches
Mail list logo
