Bug#952175: sound-juicer: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

Lucas Nussbaum lucas at debian.org
Sun Feb 23 13:14:17 GMT 2020


Source: sound-juicer
Version: 3.24.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> /bin/mkdir -p data/appdata
> /usr/bin/msgfmt --xml --template data/appdata/org.gnome.SoundJuicer.appdata.xml.in -d ./po -o data/appdata/org.gnome.SoundJuicer.appdata.xml
> if test -f "data/appdata/org.gnome.SoundJuicer.appdata.xml"; then d=; else d="./"; fi; \
> 	if test -n "/usr/bin/appstream-util"; \
> 		then /usr/bin/appstream-util --nonet validate ${d}data/appdata/org.gnome.SoundJuicer.appdata.xml; fi \
> 	&& touch data/appdata/org.gnome.SoundJuicer.appdata.valid
> data/appdata/org.gnome.SoundJuicer.appdata.xml: 
> (appstream-util:13494): dconf-CRITICAL **: 02:47:12.421: unable to create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
> 
> (appstream-util:13494): dconf-CRITICAL **: 02:47:12.422: unable to create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
> 
> (appstream-util:13494): dconf-CRITICAL **: 02:47:12.422: unable to create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
> 
> (appstream-util:13494): dconf-CRITICAL **: 02:47:12.422: unable to create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
> 
> (appstream-util:13494): dconf-CRITICAL **: 02:47:12.422: unable to create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
> 
> (appstream-util:13494): dconf-CRITICAL **: 02:47:12.422: unable to create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
> 
> (appstream-util:13494): dconf-CRITICAL **: 02:47:12.422: unable to create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
> 
> (appstream-util:13494): dconf-CRITICAL **: 02:47:12.422: unable to create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
> 
> (appstream-util:13494): dconf-CRITICAL **: 02:47:12.422: unable to create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
> 
> (appstream-util:13494): dconf-CRITICAL **: 02:47:12.422: unable to create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will not work properly.
> FAILED:
> • tag-missing           : <content_rating> required [use https://odrs.gnome.org/oars]
> • tag-missing           : <release> required
> Validation of files failed
> make[2]: *** [Makefile:1801: data/appdata/org.gnome.SoundJuicer.appdata.valid] Error 1
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> make[1]: *** [Makefile:1289: check-recursive] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/sound-juicer_3.24.0-3_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!

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-gnome-maintainers mailing list