Your message dated Sun, 27 Jan 2019 11:07:41 -0500
with message-id 
<caaajcmyottbmxpmf9qqddvtebbfvagnomen5q6rup2fk+ed...@mail.gmail.com>
and subject line Re: Bug#920617: gnome-settings-daemon: Please upgrade 
gnome-settings-daemon-common too.
has caused the Debian Bug report #920617,
regarding gnome-settings-daemon: Please upgrade gnome-settings-daemon-common 
too.
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.)


-- 
920617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-settings-daemon
Version: 3.30.2-1
Severity: normal

Dear Maintainer,

gnome-settings-daemon won’t upgrade because it needs the same version of gnome-
settings-daemon-common.

 gnome-settings-daemon : Depends: gnome-settings-daemon-common (= 3.30.2-2) but
3.30.2-1 is installed



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.17.0-3-686-pae (SMP w/3 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-settings-daemon depends on:
ii  gnome-settings-daemon-common  3.30.2-1
ii  gsettings-desktop-schemas     3.28.1-1
ii  libasound2                    1.1.7-2
ii  libc6                         2.28-5
ii  libcairo2                     1.16.0-2
ii  libcanberra-gtk3-0            0.30-7
ii  libcanberra0                  0.30-7
ii  libcolord2                    1.4.3-4
ii  libcups2                      2.2.10-3
ii  libfontconfig1                2.13.1-2
ii  libgdk-pixbuf2.0-0            2.38.0+dfsg-7
ii  libgeoclue-2-0                2.5.2-1
ii  libgeocode-glib0              3.26.0-2
ii  libglib2.0-0                  2.58.2-4
ii  libgnome-desktop-3-17         3.30.2-4
ii  libgtk-3-0                    3.24.4-1
ii  libgudev-1.0-0                232-2
ii  libgweather-3-15              3.28.2-2
ii  liblcms2-2                    2.9-3
ii  libnm0                        1.14.4-4
ii  libnotify4                    0.7.7-4
ii  libnspr4                      2:4.20-1
ii  libnss3                       2:3.41-1
ii  libpam-systemd                240-4
ii  libpango-1.0-0                1.42.4-6
ii  libpangocairo-1.0-0           1.42.4-6
ii  libpolkit-gobject-1-0         0.105-25
ii  libpulse-mainloop-glib0       12.2-3
ii  libpulse0                     12.2-3
ii  libupower-glib3               0.99.9-3
ii  libwacom2                     0.31-1
ii  libwayland-client0            1.16.0-1
ii  libx11-6                      2:1.6.7-1
ii  libxext6                      2:1.3.3-1+b2
ii  libxi6                        2:1.7.9-1

Versions of packages gnome-settings-daemon recommends:
ii  iio-sensor-proxy  2.4-2
ii  pulseaudio        12.2-3

gnome-settings-daemon suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
We believe this bootstrapping problem is caused by dak being too quick
to remove arch:all packages. gnome-settings-daemon often doesn't build
on the arch:all autobuilder as soon as it builds on other
architectures.

The workaround is for a developer to build the arch:all package
locally and upload it. Here's what I use for my sbuild:

sbuild -d unstable -A --no-arch-any --extra-repository='deb
http://deb.debian.org/debian testing main'

and then I upload the resulting _all.changes file.

Since I've done that for this build of gnome-settings-daemon (it may
take some time to be published) and the underlying bug does not appear
to be in gnome-settings-daemon itself, I am closing this bug. Thank
you for letting us know.


Jeremy Bicha

--- End Message ---

Reply via email to