| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: https://bugs.gentoo.org/645714
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652254
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
| |
commit to stable
Package-Manager: Portage-2.3.28, Repoman-2.3.9
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
| |
* desnappify
* fix ARM performance issue. Thanks to David Flogeras and Alexander Tsoy.
Closes: https://bugs.gentoo.org/647952
Closes: https://bugs.gentoo.org/651602
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652188
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652188
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652410
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
| |
Still has rough edges and needs (lots of?) improvement.
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651854
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652358
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652360
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652362
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652364
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652366
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652368
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652370
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/652372
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/614396
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Closes: https://bugs.gentoo.org/652234
|
|
|
|
| |
Closes: https://bugs.gentoo.org/645040
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
|
| |
Include upstream patch for all 7.0 versions
Limit version in 5.6.35-r1 as the patch is not the same there
Closes: https://bugs.gentoo.org/652352
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/652070
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
|
|
|
|
| |
Also bump EAPI and enable USE=expert_mode by default.
Bug: https://sourceforge.net/p/ext4magic/tickets/10/
Closes: https://bugs.gentoo.org/650074
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
As a pretty simple eclass, which only inherited multilib in order to
get $(get_libdir) and eutils for who knows why, and all its consumers
bumped to EAPI=6, it makes sense to require EAPI 6 for this eclass.
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.28, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Starting with 4.6.0, we statically link sleuthkit to a locally
complied libewf since it is getting tree-cleaned (#547418). Mask the
USE flag in prior versions. See the commit message for the sleuthkit
4.6.0 bump for more details.
This partially reverts commit
37d9e41ab5c6fb2031aefdeb7af72a7354472031. The mask was put in place
without it being communicated to the maintainer.
Bug: https://bugs.gentoo.org/547418
Bug: https://bugs.gentoo.org/607968
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This bump starts to bundle libewf since app-forensics/libewf is about
to get treecleaned (see #547418). The upstream only supports libewf
version 20130128[0], which is not available in the tree. Because they
haven't clarified the supported libewf versions until recently, we
have been depending on any version and it's been causing build
failures (see #607968). Although there are compatibility patches to
support later versions of libewf in tsk, they are not supported by
upstream. There's little to no expactation of tsk updating its code to
use the latest libewf since they've forked the version 20130128[1].
In terms of stability, 20130128 was marked stable in Gentoo at some
point[2]. There are no known security vulnerabilities. If in the
future the upstream fork diverges, we can add it to the tree as a new
package and establish a proper dependency relationship.
Note though that the ewf USE flag is masked by treecleanears[3], so
this change currently has no visible impact on users.
[0] https://github.com/sleuthkit/sleuthkit/blob/sleuthkit-4.6.0/INSTALL.txt#L44
[1] https://github.com/sleuthkit/libewf_64bit
[2] https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-forensics/libewf/libewf-20130128.ebuild?revision=1.6&view=markup
[3] https://gitweb.gentoo.org/repo/gentoo.git/tree/profiles/base/package.use.mask?id=f103062521b15cddc67a822a7a25640d3fbab76a#n65
Bug: https://bugs.gentoo.org/547418
Bug: https://bugs.gentoo.org/607968
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|