Bug 2118061 - Please branch and build mingw-libxslt for EPEL 9
Summary: Please branch and build mingw-libxslt for EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mingw-libxslt
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: EPEL Packagers SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2118060 2118062
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-13 21:07 UTC by Orion Poplawski
Modified: 2023-02-24 04:12 UTC (History)
4 users (show)

Fixed In Version: mingw-libxslt-1.1.37-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-24 04:12:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2022-08-13 21:07:09 UTC
Please branch and build mingw-libxslt in epel9.

If you do not wish to maintain mingw-libxslt in epel9,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/mingw-libxslt/addgroup
and grant it commit access, or collaborator access on epel* branches.

I would also be happy to be a co-maintainer (FAS: orion).

We will require an ExclusiveArch until RHEL 9.1 when they should be shipping the mingw-gcc packages on all arches.

Scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=90769612

DEBUG util.py:443:  No matching package to install: 'mingw32-libgcrypt'
DEBUG util.py:443:  No matching package to install: 'mingw32-libxml2 >= 2.7.2-3'
DEBUG util.py:443:  No matching package to install: 'mingw64-libgcrypt'
DEBUG util.py:443:  No matching package to install: 'mingw64-libxml2 >= 2.7.2-3'

Comment 1 Kalev Lember 2022-08-14 13:39:27 UTC
I've added both you and epel-packagers-sig. Feel free to go ahead and build it :) Thanks!

Comment 2 Ben Cotton 2023-02-07 14:53:23 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 3 Orion Poplawski 2023-02-12 20:50:57 UTC
I'm getting:

+ ../configure --host=i686-w64-mingw32 --build=x86_64-redhat-linux-gnu --target=i686-w64-mingw32 --prefix=/usr/i686-w64-mingw32/sys-root/mingw --exec-prefix=/usr/i686-w64-mingw32/sys-root/mingw --bindir=/usr/i686-w64-mingw32/sys-root/mingw/bin --sbindir=/usr/i686-w64-mingw32/sys-root/mingw/sbin --sysconfdir=/usr/i686-w64-mingw32/sys-root/mingw/etc --datadir=/usr/i686-w64-mingw32/sys-root/mingw/share --includedir=/usr/i686-w64-mingw32/sys-root/mingw/include --libdir=/usr/i686-w64-mingw32/sys-root/mingw/lib --libexecdir=/usr/i686-w64-mingw32/sys-root/mingw/libexec --localstatedir=/usr/i686-w64-mingw32/sys-root/mingw/var --sharedstatedir=/usr/i686-w64-mingw32/sys-root/mingw/com --mandir=/usr/i686-w64-mingw32/sys-root/mingw/share/man --infodir=/usr/i686-w64-mingw32/sys-root/mingw/share/info --without-python --enable-shared --enable-static --without-python --enable-shared --enable-static
configure: error: cannot find install-sh, install.sh, or shtool in ".." "../.." "../../.."
error: Bad exit status from /var/tmp/rpm-tmp.9tDojE (%build)

any idea what might be causing that?

Comment 4 Fedora Update System 2023-02-16 06:55:28 UTC
FEDORA-EPEL-2023-65253d97b8 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-65253d97b8

Comment 5 Fedora Update System 2023-02-17 02:22:39 UTC
FEDORA-EPEL-2023-65253d97b8 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-65253d97b8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2023-02-24 04:12:15 UTC
FEDORA-EPEL-2023-65253d97b8 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.