Source: xdg-utils Version: 1.1.3-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201119 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<<PKGBUILDDIR>>/autotests' > rm -f failed-tests > * Testing that xdg-email > - uses kmailservice to launch the default e-mail client in KDE3 > - uses kde-open to launch the default e-mail client in KDE4 > - uses kde-open5 to launch the default e-mail client in KDE5 > - uses run_thunderbird if default e-mail client is Thunderbird in KDE5 > * Testing that xdg-icon-resource > - installs a png icon system-wide > * Testing that xdg-mime query default > - reads $XDG_CONFIG_HOME/mimeapps.list > * Testing that xdg-open > - opens a URL with gio open in recent GNOME 3, and Cinnamon > ASSERTION FAILED: expected command to be run: gio open > http://www.freedesktop.org/ > ASSERTION FAILED: expected command to be run: gio open > http://www.freedesktop.org/ > - opens a URL with gvfs-open if gio open is missing in GNOME 3, GNOME 2, > and Cinnamon > - opens a URL with gnome-open if gio open and gvfs-open are missing in > GNOME 2 > - opens a URL with the generic method if gio open and gvfs-open are missing > in GNOME 3, and Cinnamon > - opens a URL with the generic method if gio open, gvfs-open and gnome-open > are missing in GNOME 2 > - opens a URL with kfmclient in KDE 3 > - opens a URL with kde-open in KDE 4 > - opens a URL with kde-open5 in KDE 5 > - opens a URL with gvfs-open in MATE > - opens a URL with mate-open if gio open and gvfs-open are missing in MATE > - opens a URL with exo-open in XFCE > - opens a URL with enlightenment_open in Enlightenment > - opens a file path with pcmanfm in LXDE > - percent-decodes a file:// URL and opens it with pcmanfm in LXDE > - opens files with spaces in their name in LXDE > - looks up x-scheme-handler/* in LXDE > - looks up x-scheme-handler/* in generic mode > - works with multi-word $BROWSER commands > - is not vulnerable to command injection in URLs when using $BROWSER in > generic mode > - is not vulnerable to argument injection in URLs when using $BROWSER in > generic mode > - opens files in generic mode > - opens files with # characters in their name in generic mode > - opens files with spaces in their name in generic mode > * Testing that xdg-screensaver > - calls xset -dpms, xset +dpms and xset dpms force when performing reset > * Testing that xdg-settings > - determines default browser using GConf in GNOME 2 > - determines default browser from $XDG_CONFIG_HOME/mimeapps.list in gnome3 > - determines default URL handler from $XDG_CONFIG_HOME/mimeapps.list in > gnome3 > - determines default browser from $XDG_CONFIG_HOME/mimeapps.list in cinnamon > - determines default URL handler from $XDG_CONFIG_HOME/mimeapps.list in > cinnamon > - determines default browser from $XDG_CONFIG_HOME/mimeapps.list in lxde > - determines default URL handler from $XDG_CONFIG_HOME/mimeapps.list in lxde > - determines default browser from $XDG_CONFIG_HOME/mimeapps.list in mate > - determines default URL handler from $XDG_CONFIG_HOME/mimeapps.list in mate > - determines default browser from $XDG_CONFIG_HOME/mimeapps.list in generic > - determines default URL handler from $XDG_CONFIG_HOME/mimeapps.list in > generic > - uses $BROWSER in generic mode > > TEST FAILURES: > > t-xdg-open.sh: Assertion failed when testing that xdg-open opens a URL with > gio open in recent GNOME 3, and Cinnamon: expected command to be run: gio > open http://www.freedesktop.org/ > t-xdg-open.sh: Assertion failed when testing that xdg-open opens a URL with > gio open in recent GNOME 3, and Cinnamon: expected command to be run: gio > open http://www.freedesktop.org/ > > make[3]: *** [Makefile:6: test] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/11/19/xdg-utils_1.1.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! 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.
