Hi,
When doing automatted committing during stabilization, I recently
started seeing manifest signing fail like this:
gpg: pkglue.c:41: mpi_from_sexp: Assertion `data' failed.
!!! !!! gpg exited with '6' status
!!! Disabled FEATURES='sign'
The curious thing: It works most of the time, but fails
W dniu 14.07.2011 12:31, Thomas Kahle pisze:
Hi,
When doing automatted committing during stabilization, I recently
started seeing manifest signing fail like this:
gpg: pkglue.c:41: mpi_from_sexp: Assertion `data' failed.
!!! !!! gpg exited with '6' status
!!! Disabled FEATURES='sign'
# Pacho Ramos pa...@gentoo.org (14 Jul 2011)
# Upstream doesn't maintain it for a long time, nothing uses it
# anymore and bundles a copy of sqlite3, bug #252540
# Removal in 30 days
=gnome-extra/libgda-3*
signature.asc
Description: This is a digitally signed message part
Hi everyone,
During the last meeting of the hardened team [1], we discussed the issue
of the proper use of the global hardened flag. Because hardened has
various meanings the flag is being (ab)used in various way. Primarily
there are two distinct meanings that need to be distinguished in the
Am Donnerstag 14 Juli 2011, 14:54:41 schrieb Kacper Kowalik:
W dniu 14.07.2011 12:31, Thomas Kahle pisze:
Hi,
When doing automatted committing during stabilization, I recently
started seeing manifest signing fail like this:
gpg: pkglue.c:41: mpi_from_sexp: Assertion `data' failed.
On Thursday, July 14, 2011 18:52:04 Anthony G. Basile wrote:
2) The choice of a hardened kernel is made by emergeing
hardened-sources, configuring, compiling, booting. There is no use flag
for this choice per se. That means that virtual/linux-sources would
remove the condition RDEPEND:
