Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 651134

Summary: =mail-filter/rspamd-1.7.1-r1 fix USE flags gd and jit/torch conflict
Product: Gentoo Linux Reporter: Christian Roessner <c>
Component: Current packagesAssignee: Christian Roessner <c>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bruce, bug, djc, proxy-maint
Priority: Normal Keywords: EBUILD, PATCH
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: mail-filter/rspamd-1.7.1-r1.ebuild
rspamd-1.7.1-r1.ebuild
metadata.xml
rspamd.logrotate

Description Christian Roessner 2018-03-22 07:37:51 UTC
Created attachment 524768 [details]
mail-filter/rspamd-1.7.1-r1.ebuild

This version fixes bug #611890

Tested and works for me
Comment 1 Christian Roessner 2018-03-22 09:36:27 UTC
Created attachment 524774 [details]
rspamd-1.7.1-r1.ebuild

This file fixes also torch/jit Cmake problems
Comment 2 Christian Roessner 2018-03-22 09:37:02 UTC
Created attachment 524776 [details]
metadata.xml

Adding USE flag torch
Comment 3 Christian Roessner 2018-03-22 09:45:55 UTC
Created attachment 524778 [details]
rspamd.logrotate

Fixed version of the logrotate file
Comment 4 Dirkjan Ochtman (RETIRED) gentoo-dev 2018-03-22 10:20:03 UTC
It looks like you now allow enabling torch while having jit disabled. Does that configuration actually make sense? If not, may need some REQUIRED_USE stuff in there restricting that usage.
Comment 5 Christian Roessner 2018-03-22 10:47:00 UTC
(In reply to Dirkjan Ochtman from comment #4)
> It looks like you now allow enabling torch while having jit disabled. Does
> that configuration actually make sense? If not, may need some REQUIRED_USE
> stuff in there restricting that usage.

Hm, there is already REQUIRED_USE="torch? ( jit )" in the ebuild I uploaded ;-) Is it wrong?
Comment 6 Dirkjan Ochtman (RETIRED) gentoo-dev 2018-03-29 13:35:31 UTC
Resolving as duplicate, will include these fixes in 1.7.2 from bug 651366.

*** This bug has been marked as a duplicate of bug 651366 ***