#1 Enable all arches in EPEL
Merged 2 years ago by tdawson. Opened 2 years ago by sharkcz.
rpms/ sharkcz/lightdm multiarch  into  rawhide

file modified
+4 -9
@@ -11,15 +11,7 @@ 

  Name:		lightdm

  Summary:	A cross-desktop Display Manager

  Version:	1.30.0

- Release:	17%{?dist}

- 

- %if 0%{?rhel} >= 8

- # Exclude failing arch

- #DEBUG util.py:593:  No matching package to install: 'gnome-common'

- #DEBUG util.py:593:  No matching package to install: 'itstool'

- #DEBUG util.py:593:  Not all dependencies satisfied

- ExclusiveArch: x86_64 ppc64le

- %endif

+ Release:	18%{?dist}

  

  # library/bindings are LGPLv2 or LGPLv3, the rest GPLv3+

  License:	(LGPLv2 or LGPLv3) and GPLv3+
@@ -327,6 +319,9 @@ 

  

  

  %changelog

+ * Fri Jun 10 2022 Dan Horák <dan[at]danny.cz> - 1.30.0-18

+ - Enable all arches in EPEL

+ 

  * Sun Jun 05 2022 Leigh Scott <leigh123linux@gmail.com> - 1.30.0-17

  - Fix xauthority corruption (rhbz#2093668)

  - Add missing requires for post scriptlet (rhbz#2093698)

I believe RHEL got the missing desktop bits for aarch64 and s390x in one of the last minor releases. Tested successfully with scratch builds.

epel8 - https://koji.fedoraproject.org/koji/taskinfo?taskID=88076201
epel9 - https://koji.fedoraproject.org/koji/taskinfo?taskID=88076131

Once merged lightdm-gtk should build as well.

It makes sense to build for arm arch, but why you want to use a graphical login manager on a IBM server system?
https://en.wikipedia.org/wiki/IBM_System/390
Are you using a graphical desktop on such a system?

There is no graphical console, but mainframes are not used from the console, but rather via VMs instead and it makes sense to provide a desktop environment there. RHEL added it, because there was a demand for it and with virt-manager you can't distinguish if the remote machine is a x86 box or ppc or s390x. It just works the same.

Ok, gdm is also built for s390 architecture.
But i do not use rhel or his derivatives for myself any more.
So, sorry i can't merge this for myself.
Ihmo, one existing maintainer should use use it to work on bugreports.
Or are you in packager group?

I have zero interest in rhel/epel.

I'm maintaining / co-maintaining lightdm in epel9.
I'd like this merely for consistency sake. I have enough packages to maintain, and when some do not do s390x, it's a bit of a pain.

Pull-Request has been merged by tdawson

2 years ago
Metadata