commit:     a753e52d96f72ab54bd959982e39b26fafd21076
Author:     Sebastian Pipping <sping <AT> gentoo <DOT> org>
AuthorDate: Sat Sep  8 09:19:53 2018 +0000
Commit:     Sebastian Pipping <sping <AT> gentoo <DOT> org>
CommitDate: Sat Sep  8 09:21:45 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a753e52d

app-text/dvisvgm: Restore keywords ia64 ppc ppc64 amd64-fbsd

Bug: https://bugs.gentoo.org/663178
Bug: https://bugs.gentoo.org/663174
Bug: https://bugs.gentoo.org/661356
Package-Manager: Portage-2.3.46, Repoman-2.3.10

 app-text/dvisvgm/dvisvgm-2.5.ebuild | 2 +-
 app-text/dvisvgm/dvisvgm-2.6.ebuild | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/app-text/dvisvgm/dvisvgm-2.5.ebuild 
b/app-text/dvisvgm/dvisvgm-2.5.ebuild
index f4c0ba5ab26..aacbe77eab6 100644
--- a/app-text/dvisvgm/dvisvgm-2.5.ebuild
+++ b/app-text/dvisvgm/dvisvgm-2.5.ebuild
@@ -11,7 +11,7 @@ 
SRC_URI="https://github.com/mgieseki/dvisvgm/releases/download/${PV}/${P}.tar.gz
 
 LICENSE="GPL-3"
 SLOT="0"
-KEYWORDS="~amd64 ~hppa ~s390 ~sh ~sparc ~x86 ~x86-fbsd ~amd64-linux ~ppc-macos 
~x64-macos ~x86-macos"
+KEYWORDS="~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd 
~x86-fbsd ~amd64-linux ~ppc-macos ~x64-macos ~x86-macos"
 IUSE="test"
 # Tests don't work from $WORKDIR: kpathsea tries to search in relative
 # directories from where the binary is executed.

diff --git a/app-text/dvisvgm/dvisvgm-2.6.ebuild 
b/app-text/dvisvgm/dvisvgm-2.6.ebuild
index f4c0ba5ab26..aacbe77eab6 100644
--- a/app-text/dvisvgm/dvisvgm-2.6.ebuild
+++ b/app-text/dvisvgm/dvisvgm-2.6.ebuild
@@ -11,7 +11,7 @@ 
SRC_URI="https://github.com/mgieseki/dvisvgm/releases/download/${PV}/${P}.tar.gz
 
 LICENSE="GPL-3"
 SLOT="0"
-KEYWORDS="~amd64 ~hppa ~s390 ~sh ~sparc ~x86 ~x86-fbsd ~amd64-linux ~ppc-macos 
~x64-macos ~x86-macos"
+KEYWORDS="~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd 
~x86-fbsd ~amd64-linux ~ppc-macos ~x64-macos ~x86-macos"
 IUSE="test"
 # Tests don't work from $WORKDIR: kpathsea tries to search in relative
 # directories from where the binary is executed.

Reply via email to