[Bug 43436] New: Would it be possible to add Mageia 6 back to the Install page?
https://bugs.winehq.org/show_bug.cgi?id=43436 Bug ID: 43436 Summary: Would it be possible to add Mageia 6 back to the Install page? Product: Wine-staging Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arichter(a)lobo.net CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- I would sure like to see Mageia added back to the wine-staging Install page, Mageia has been very good about keeping up with the stable releases but staging is where all the fun is. I have been successfully building RPMS for both i586 and x86_64 under Mageia 6 and would be glad to submit RPMS or SRPMS for both architectures. Mageia 6 also now supports mock, which is what I have been using to build the i586 RPMs under x86_64. I apologize for submitting this as a bug since it's not a bug but I would either like to see Mageia back under the Install page or contribute built RPMS and SRPMS to help make it happen. I'm a bit new to this RPM building thing but the stuff I've made has worked out for me, and I've tried to be more active in the winedb. Thank you for your time and efforts, I only want to help on the Mageia side of things. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 Michael Müller <michael(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Product|Wine-staging |Packaging Version|2.13 |unspecified Component|-unknown |wine-packages --- Comment #1 from Michael Müller <michael(a)fds-team.de> --- The packaging files are not the reason why we stopped supporting Mageia. Their repository tools are causing the problems, otherwise everything would be ready to go. On our build server, the packages are builtin inside of a Mageia VM and then copied to the host system, which signs the files and adds them to a repository. The problem is that the host system is running Debian and that the tool to create such repositories (genhdlist2) doesn't seem to play well with anything else than Mageia. I was unable to find a working combination of genhdlist2, URPM and librpm that works on Debian without any warnings or errors. The script also looks up files in the system to determine the Mageia version which then leads to differences in the created repository format. This will obviously not work on Debian and we therefore came to the conclusion that we can not ensure that the created repository is valid and stopped providing packages. Not to mention that Mageia also applied quite some patches on librpm and we would most probably need a second librpm version (one for Fedora and one for Mageia). Mageia is the first distribution that caused such problems and it seems like nobody thought about the possibility that such tools might also be used on other systems. We do not really want to maintain our own forks of these libraries and it would be great if Mageia could make their packaging tools more compatible. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 Neal Gompa <ngompa13(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ngompa13(a)gmail.com --- Comment #2 from Neal Gompa <ngompa13(a)gmail.com> --- Starting with Mageia 6, the exact same tooling that's used for Fedora is supported for Mageia. The DNF package manager is available and fully supported[1], and Mock in Debian supports Mageia 6 as a build target[2], as of Debian 9. RPM in Mageia 6 is basically in sync with Fedora 25 (rpm 4.13.0.1 with some backports from rpm git master). The main issue you might encounter is that Mageia uses RPM's file triggers more aggressively than Fedora does (and rpm < 4.13 doesn't support them), but it should still work... I believe Debian has rpm 4.13.0.1 in experimental, and that will work. However, since you're building packages in a Mageia VM, this part isn't an issue. You can use createrepo / createrepo_c to generate metadata just like you can for Fedora to target Mageia with the DNF package manager. I don't expect any issues from Debian tooling for generating metadata for Mageia in this regard... [1]: https://blog.mageia.org/en/2017/07/21/dandifying-mageia-part-2/ [2]: https://packages.debian.org/stretch/all/mock/filelist -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #3 from Michael Müller <michael(a)fds-team.de> --- I finally had time to update the build system to use the same packaging scripts for fedora as well as for mageia and to setup the mageia 6 VMs. I did some test builds and published them into a temporary testing repo. Can some confirm that the following commands work, so that we can put them (plus the stable builds) into the official winehq repo? dnf config-manager --add-repo https://repos.wine-staging.com/test/mageia/6/wine.repo To install Wine Staging: dnf install winehq-staging To Install Wine Devel: dnf install winehq-devel -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #4 from Neal Gompa <ngompa13(a)gmail.com> --- It works for me when I do the following commands: # dnf config-manager --set-enabled mageia-i586 updates-i586 # dnf config-manager --add-repo https://repos.wine-staging.com/test/mageia/6/wine.repo # dnf install winehq-staging (or winehq-devel) I needed the first command as 32-bit repositories are not enabled by default[1]. After that, it was successfully installed and I was able to run an application through Wine. It was a little concerning seeing the GPG key say "Test Repository", but I imagine you'll fix that before publishing. [1]: https://wiki.mageia.org/en/Using_DNF#Install_and_Setup -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #5 from Michael Müller <michael(a)fds-team.de> --- The mageia 6 installer had 32 bit multiarch enabled by default, but I am not sure if it also applies to dnf. Anyway, it makes sense to mention it in the installation instructions as someone might have disabled it. Regarding the testing key: The packages are signed by the host system when publishing them into a repository. As soon as they get published into the official repository, they also get the correct signature. You can remove the repository and key again. Mageia 6 is now enabled by default and is picked up for the daily builds (e.g. [1]) and release builds. The correct url will be [2], but you will need to wait till Wine (Staging) 2.18 is released before it will work. [1]: https://dev.wine-staging.com/builder/group/269/ [2]: https://dl.winehq.org/wine-builds/mageia/6/winehq.repo -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #6 from Neal Gompa <ngompa13(a)gmail.com> --- (In reply to Michael Müller from comment #5)
The mageia 6 installer had 32 bit multiarch enabled by default, but I am not sure if it also applies to dnf. Anyway, it makes sense to mention it in the installation instructions as someone might have disabled it.
It doesn't yet apply to DNF, unfortunately. Known issue and planned to be worked on for Mageia 7. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #7 from Neal Gompa <ngompa13(a)gmail.com> --- Michael, Could we please have the Mageia page[1] updated with the new supported state? I see that the repository[2] now exists and has content. [1]: https://wiki.winehq.org/Mageia [2]: https://dl.winehq.org/wine-builds/mageia/6/winehq.repo -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #8 from Michael Müller <michael(a)fds-team.de> --- We should wait till the next Staging release and also include a stable build, before officially announcing support for Mageia 6. Otherwise users would be confused why they can not install certain packages. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #9 from Neal Gompa <ngompa13(a)gmail.com> --- So since Wine 2.18 went out on Sept 29, then that means we'd be looking at October 13 for Mageia support to be restored? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #10 from Michael Müller <michael(a)fds-team.de> --- No, Wine Staging 2.18 will most probably be released Tuesday or Wednesday. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #11 from Neal Gompa <ngompa13(a)gmail.com> --- Michael, I see that Wine 2.19 has gone out, are we now at a point where the Mageia page can be redone and linked back from the download page? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #12 from Rosanne DiMesio <dimesio(a)earthlink.net> --- I've updated the Mageia wiki page with instructions based on comments 4 & 5; please check that they are correct, as I don't use Mageia. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 --- Comment #13 from Neal Gompa <ngompa13(a)gmail.com> --- (In reply to Rosanne DiMesio from comment #12)
I've updated the Mageia wiki page with instructions based on comments 4 & 5; please check that they are correct, as I don't use Mageia.
The instructions are specifically for Mageia 6, so you should probably put a Mageia 6 header like is done for Fedora {24,25,26} on the Fedora page. Otherwise, looks fine for the installation steps. As for the build-dependency stuff (for equivalent "build wine from source" instructions), this is the command I used to install the build dependencies (no guarantee of its completeness, but it worked for me): dnf install lib64cups2-devel.x86_64 libcups2-devel.i586 lib64dbus-devel.x86_64 libdbus-devel.i586 docbook-dtd-sgml docbook-utils lib64fontconfig-devel.x86_64 libfontconfig-devel.i586 fontforge lib64freetype6-devel.x86_64 libfreetype6-devel.i586 gettext-devel glibc-devel.x86_64 glibc-devel.i586 lib64gnutls-devel.x86_64 libgnutls-devel.i586 lib64gphoto-devel.x86_64 libgphoto-devel.i586 lib64gpm-devel.x86_64 libgpm-devel.i586 lib64gsm-devel.x86_64 libgsm-devel.i586 lib64gstreamer1.0-devel.x86_64 libgstreamer1.0-devel.i586 lib64gtk+3.0-devel.x86_64 libgtk+3.0-devel.i586 icoutils imagemagick lib64isdn4k-utils-devel.x86_64 libisdn4k-utils-devel.i586 lib64lcms2-devel.x86_64 liblcms2-devel.i586 lib64alsa2-devel.x86_64 libalsa2-devel.i586 lib64gstreamer-plugins-base1.0-devel.x86_64 libgstreamer-plugins-base1.0-devel.i586 lib64mpg123-devel.x86_64 libmpg123-devel.i586 lib64pcap-devel.x86_64 libpcap-devel.i586 lib64rsvg2-devel.x86_64 librsvg2-devel.i586 lib64sm-devel.x86_64 libsm-devel.i586 lib64v4l-devel.x86_64 libv4l-devel.i586 lib64va-devel.x86_64 libva-devel.i586 lib64x11-devel.x86_64 libx11-devel.i586 lib64xcomposite-devel.x86_64 libxcomposite-devel.i586 lib64xcursor-devel.x86_64 libxcursor-devel.i586 lib64xext-devel.x86_64 libxext-devel.i586 lib64xi-devel.x86_64 libxi-devel.i586 lib64xinerama-devel.x86_64 libxinerama-devel.i586 lib64xrandr-devel.x86_64 libxrandr-devel.i586 lib64xrender-devel.x86_64 libxrender-devel.i586 lib64xslt-devel.x86_64 libxslt-devel.i586 lib64mesaglu1-devel.x86_64 libmesaglu1-devel.i586 lib64ncurses-devel.x86_64 libncurses-devel.i586 lib64openal-devel.x86_64 libopenal-devel.i586 lib64osmesa-devel.x86_64 libosmesa-devel.i586 perl-devel lib64png-devel.x86_64 libpng-devel.i586 prelink lib64pulseaudio-devel.x86_64 libpulseaudio-devel.i586 lib64sane1-devel.x86_64 libsane1-devel.i586 sgml-tools lib64tiff-devel.x86_64 libtiff-devel.i586 lib64gif-devel.x86_64 libgif-devel.i586 lib64unixODBC-devel.x86_64 libunixODBC-devel.i586 valgrind-devel lib64xpm-devel.x86_64 libxpm-devel.i586 The equivalent for the groups installed by Fedora is: dnf install task-c-devel That should let you fill in the information similar to the Fedora page. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 Rosanne DiMesio <dimesio(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #14 from Rosanne DiMesio <dimesio(a)earthlink.net> --- This was fixed months ago. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43436 Rosanne DiMesio <dimesio(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #15 from Rosanne DiMesio <dimesio(a)earthlink.net> --- Closing fixed packaging bug. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org