Your message dated Sat, 24 Aug 2024 11:12:46 +0100
with message-id <zsmyhlj7rdokx...@remnant.pseudorandom.co.uk>
and subject line Re: Bug#836107: libaccounts-glib: please use dbus-run-session
to run tests
has caused the Debian Bug report #836107,
regarding libaccounts-glib: please use dbus-run-session to run tests
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
836107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcp
Version: 1.21-1
Severity: normal
User: d...@packages.debian.org
Usertags: dbus-launch dbus-launch-for-tests
As described in <https://lists.debian.org/debian-devel/2016/08/msg00554.html>
I'm trying to reduce how much dbus-launch is used in Debian.
This package currently uses dbus-x11 for tests, explicitly launching
dbus-launch.
It should be possible to replace dbus-x11 as follows:
* replace the build-dependency on dbus-x11 with dbus (>= 1.8)
* replace "xvfb-run -a dbus-launch ..." with
"xvfb-run -a dbus-run-session ..."
If D-Bus is the only reason you are using xvfb, you can remove that too,
and just use "dbus-run-session -- dh_auto_test".
Thanks,
S
--- End Message ---
--- Begin Message ---
Version: 1.23-1
On Tue, 30 Aug 2016 at 17:21:13 +0100, Simon McVittie wrote:
> It should be possible to replace dbus-x11 as follows:
>
> * replace the build-dependency on dbus-x11 with dbus (>= 1.8)
> * replace "xvfb-run -a dbus-launch ..." with
> "xvfb-run -a dbus-run-session ..."
Looks like this was done in:
libaccounts-glib (1.23-1) unstable; urgency=medium
* Update watch file
* New upstream release (1.23).
* Bump Standards-Version to 4.0.0, no changes needed.
* Use dbus-run-session instead of dbus-launch
* Update symbols file
* Release to unstable
--- End Message ---
