[Pkg-privacy-maintainers] Bug#976579: libgsecuredelete: FTBFS: gsecuredelete.vapi:8.3-8.25: error: `Gsd.Intl' already contains a definition for `init'

Lucas Nussbaum lucas at debian.org
Sat Dec 5 12:21:37 GMT 2020


Source: libgsecuredelete
Version: 0.3-2
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[4]: Entering directory '/<<PKGBUILDDIR>>/gsecuredelete'
> rm -f test_vala.stamp && echo stamp > test_vala.stamp-t
> /usr/bin/valac --pkg=glib-2.0 --pkg=posix --vapidir=. --pkg=gsecuredelete  -C main.vala gsecuredelete.vapi
> gsecuredelete.vapi:23.3-23.23: warning: Creation method of abstract class cannot be public.
> 		public AsyncOperation ();
> 		^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:79.3-79.30: warning: Creation method of abstract class cannot be public.
> 		public SecureDeleteOperation ();
> 		^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:100.3-100.26: warning: Creation method of abstract class cannot be public.
> 		public ZeroableOperation ();
> 		^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:23.3-23.23: warning: Creation method of abstract class cannot be public.
> 		public AsyncOperation ();
> 		^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:79.3-79.30: warning: Creation method of abstract class cannot be public.
> 		public SecureDeleteOperation ();
> 		^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:100.3-100.26: warning: Creation method of abstract class cannot be public.
> 		public ZeroableOperation ();
> 		^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:8.3-8.25: error: `Gsd.Intl' already contains a definition for `init'
> 		public static void init ();
> 		^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:8.3-8.25: note: previous definition of `init' was here
> 		public static void init ();
> 		^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:11.2-11.51: error: `Gsd' already contains a definition for `AsyncOperation'
> 	public abstract class AsyncOperation : GLib.Object {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:11.2-11.51: note: previous definition of `AsyncOperation' was here
> 	public abstract class AsyncOperation : GLib.Object {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:42.2-42.53: error: `Gsd' already contains a definition for `DeleteOperation'
> 	public class DeleteOperation : Gsd.ZeroableOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:42.2-42.53: note: previous definition of `DeleteOperation' was here
> 	public class DeleteOperation : Gsd.ZeroableOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:53.2-53.51: error: `Gsd' already contains a definition for `FillOperation'
> 	public class FillOperation : Gsd.ZeroableOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:53.2-53.51: note: previous definition of `FillOperation' was here
> 	public class FillOperation : Gsd.ZeroableOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:69.2-69.54: error: `Gsd' already contains a definition for `MemOperation'
> 	public class MemOperation : Gsd.SecureDeleteOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:69.2-69.54: note: previous definition of `MemOperation' was here
> 	public class MemOperation : Gsd.SecureDeleteOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:73.2-73.65: error: `Gsd' already contains a definition for `SecureDeleteOperation'
> 	public abstract class SecureDeleteOperation : Gsd.AsyncOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:73.2-73.65: note: previous definition of `SecureDeleteOperation' was here
> 	public abstract class SecureDeleteOperation : Gsd.AsyncOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:89.2-89.51: error: `Gsd' already contains a definition for `SwapOperation'
> 	public class SwapOperation : Gsd.ZeroableOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:89.2-89.51: note: previous definition of `SwapOperation' was here
> 	public class SwapOperation : Gsd.ZeroableOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:99.2-99.68: error: `Gsd' already contains a definition for `ZeroableOperation'
> 	public abstract class ZeroableOperation : Gsd.SecureDeleteOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:99.2-99.68: note: previous definition of `ZeroableOperation' was here
> 	public abstract class ZeroableOperation : Gsd.SecureDeleteOperation {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:105.2-105.39: error: `Gsd' already contains a definition for `AsyncOperationError'
> 	public errordomain AsyncOperationError {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> gsecuredelete.vapi:105.2-105.39: note: previous definition of `AsyncOperationError' was here
> 	public errordomain AsyncOperationError {
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Compilation failed: 9 error(s), 6 warning(s)
> make[4]: *** [Makefile:574: test_vala.stamp] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/libgsecuredelete_0.3-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



More information about the Pkg-privacy-maintainers mailing list