Your message dated Sat, 26 Sep 2020 17:04:13 +0000
with message-id <e1kmdcl-0006s0...@fasolo.debian.org>
and subject line Bug#970245: fixed in gdm3 3.38.0-2
has caused the Debian Bug report #970245,
regarding gnome-core: gnome-core/s390x has unsatisfiable dependency
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.)


-- 
970245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-core
Version: 1:3.30+3
Severity: serious

The last uploaded added the dependency on gdm3 back:

   * d/control.in: Remove special-case fallbacks for s390x
     gjs, gdm and gnome-shell are now available on s390x (although whether
     they have been successfully run there is anyone's guess), so we can pull
     in the full GNOME desktop on all release architectures again.

While the source package gdm3 built successfully on s390x, it does not
build the gdm3 binary there (even though it declares gdm to be available
on linux-any). From its debian/rules:

dh_options =
just_the_library = no
ifneq (,$(filter $(DEB_HOST_ARCH_CPU),s390x))
        dh_options += -Ngdm3
        just_the_library = yes
endif

Also verified on zelenka:

% dd-schroot-cmd -c sramacher-gnome apt-get install gnome-core
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gnome-core : Depends: gdm3 (>= 3.30) but it is not installable
E: Unable to correct problems, you have held broken packages.

Cheers
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: gdm3
Source-Version: 3.38.0-2
Done: Simon McVittie <s...@debian.org>

We believe that the bug you reported is fixed in the latest version of
gdm3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie <s...@debian.org> (supplier of updated gdm3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 26 Sep 2020 16:52:06 +0100
Source: gdm3
Architecture: source
Version: 3.38.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 
<pkg-gnome-maintain...@lists.alioth.debian.org>
Changed-By: Simon McVittie <s...@debian.org>
Closes: 970245
Changes:
 gdm3 (3.38.0-2) unstable; urgency=medium
 .
   * Team upload
   * d/rules: Set runtime configuration path.
     In Autotools, the default runtime configuration path used to be
     ${GDM_RUN_DIR}/custom.conf, but in the Meson build system the fallback
     changed to be the same as the custom.conf path in /etc (set to
     /etc/gdm3/daemon.conf in Debian for historical reasons).
     Explicitly set it to the path we used before switching to Meson, so
     that configuration changes by gdm-disable-wayland are temporary as
     intended, and do not persist to a subsequent boot.
   * Revert "debian/watch: Monitor unstable versions"
   * d/upstream/metadata: Add
   * Merge packaging from unstable
   * Release to unstable
 .
 gdm3 (3.38.0-1) experimental; urgency=medium
 .
   * Team upload
   * New upstream release
   * Remove patches that were applied upstream (in some cases differently)
   * Remove special case for s390x.
     gjs and gnome-shell now exist there, so we no longer need to avoid
     depending on them. In particular this makes the GNOME metapackages
     installable on that architecture again. (Closes: #970245)
 .
 gdm3 (3.37.90-2) experimental; urgency=medium
 .
   * Team upload
 .
   [ Simon McVittie ]
   * Add patch to remove deprecated StandardOutput=syslog from systemd unit
   * Build-Depend on systemd, for /usr/share/pkgconfig/systemd.pc
 .
   [ Iain Lane ]
   * debian/control: Bump depends on gnome-{session,settings-daemon,shell}
     We require the newly rearranged systemd units that are in these
     versions.
   * debian/control: Make gdm depend on gnome-session-common ≥ 3.37.0-2~
     This is where the systemd units live now.
 .
 gdm3 (3.37.90-1) experimental; urgency=medium
 .
   [ Marco Trevisan (Treviño) ]
   * New upstream release:
     - Updates to systemd integration
     - Support killling X on login even when wayland support is disabled
     - Fix multi-seat support (LP: #1891815)
     - Don't keep login screen running in background on Xorg
     - Fixes for when GDM isn't started on its configured initial VT
     - Don't hardcode path to plymouth
     - Enable wayland on cirrus
     - Chrome remote desktop fix
     - Always use separate session bus for greeter sessions
       This runs dbus-run-session, so the binary needs to be available
   * debian/rules:
     - Build with meson
     - Use --fail-missing if not in library-only mode
     - Expose to meson only X bin path
   * debian/control:
     - Depend on debhelper-compat = 13
     - Cleanup the Build-Depends: Remove dependencies that are not required
       explicitly by gdm
   * debian/libgdm1.symbols: Remove various (private) symbols.
     - They were wrongly exported as there's no trace of them in the
       public API.
   * debian/patches: Refresh as per meson port
   * d/p/16_xserver_path.patch:
     - Make meson read the X bin path from environment
   * d/p/meson-Fix-keyutils-pkg-config-name.patch,
     d/p/meson-Obey-at-Dcustom-conf-option-when-installing-custom..patch,
     d/p/meson-Use-correct-rules-path-when-getting-udevdir-from-pk.patch:
     - Fix some meson issues causing diffs with autotools
   * d/p/meson-Don-t-look-for-non-existent-journald-dependency.patch,
     d/p/meson_options-Enable-systemd-journal-by-default.patch:
     - Make gdm log again to the journal by default
   * debian/gdm3.install: Update install paths.
     Install everything under usr/share/gdm
   * debian/*.install: Use dh 13 ${DEB_HOST_MULTIARCH} instead of wildcards
 .
   [ Simon McVittie ]
   * d/p/local-display-factory-always-force-login-screen-to-VT-1.patch:
     - Drop, applied upstream
Checksums-Sha1:
 e47f806d9ddb2cbe50a6408fbf3a09ba7a1805e3 2888 gdm3_3.38.0-2.dsc
 d0ecc0042d6db2b37bb84288c8bef9c8d609c0b0 91120 gdm3_3.38.0-2.debian.tar.xz
 80435827b73b7fce7a260cb1c7a946458d631690 15313 gdm3_3.38.0-2_source.buildinfo
Checksums-Sha256:
 effb1da95a4c96a17530acd43574eddcb2fdad827d8aac405ae44a56ef92cc72 2888 
gdm3_3.38.0-2.dsc
 23abb187b960f4a25b712fa0b23de4d1de5b7ae7d3c466025ed0deae811cb3e1 91120 
gdm3_3.38.0-2.debian.tar.xz
 dc59bd2afe9590cff5e7f275e9f30bf8f120d491b4ce19043e1ab42f02a9ef84 15313 
gdm3_3.38.0-2_source.buildinfo
Files:
 117a28e800a85bcecc81c35e1cc78a59 2888 gnome optional gdm3_3.38.0-2.dsc
 1d1d7bae7a834b6933adf467b25be2c6 91120 gnome optional 
gdm3_3.38.0-2.debian.tar.xz
 1f263d021c24339176740ffaef0e3166 15313 gnome optional 
gdm3_3.38.0-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl9vaeQACgkQ4FrhR4+B
TE9uPQ//Sp2cSH/RG9Ic6KmJbTG+cC4+n7HtJMojlMoIe/GQYTq6d+ct6g9CCKp7
1EelTnu/0qX6xb58CvYRTE+b8tzGTVwYcU0k3gQVK8KAVyQ44Ya5M2eIyYvrmccx
iFDF70rqk4Qla0yD+5c+G8ZlR3co7gYukrSAHISnD9i6glexuXGGEivTWj0tYJv9
lbpQYPBomDSVRW0Ykqsk7D+saiPIoyIiXfDIBqeyDSNlIw7vTRJoD7SAhlwzsS5T
PnlF/VTXXfasRlQ/dq8Ga2TF49IpoRhi3UIfKnuvkzheq0Asu76gKrRt+XON1clx
CykmxfUcNlpb+XPWLcCr1krHufsoouJLpJFloMJQxaxxSZ6F5rxx24FbeT3lpfpb
+zhkWdxHRgd3qYEmuXqcuRYHdi0VFrnQPvfvYtve+43lu61SWRNx3SzgxtMRvWli
JM19ulKx7ufzKtifWOcQFf4sO5aFlKhjSun0DRkuiVFo0gJ7Lmzr9txM/oS2g5rz
4quMbKqclQE1Zl4gz+gUiDryswxuScePUwEIw69nnwJnpbkTHremtfxmBXGrjcfn
AdfQFjIVHxktl1dJyEULeq23uxIq0hun1dP2AyRqYI1qwYEDF9KiqqTICxkJeUAd
8yy8MckLalw/Pw7u2zOHBiQHZevW9DqKTD6doVvyXk1khQdssi0=
=yoOm
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to