http://bugs.winehq.org/show_bug.cgi?id=58823
Bug ID: 58823 Summary: Wine Debian build dependencies are missing libxkbregistry-dev Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs@winehq.org Reporter: shtetldik@gmail.com CC: dimesio@earthlink.net Distribution: ---
I noticed that when I'm installing build dependencies using your Debian repo
sudo apt build-dep wine-devel
It's not pulling in libxkbregistry-dev, which results in the build missing winewayland support. Though I see that winewayland is provided by your own built packages somehow.
Can you please make libxkbregistry-dev be pulled by build dependencies.
http://bugs.winehq.org/show_bug.cgi?id=58823
--- Comment #1 from Shmerl shtetldik@gmail.com --- Another important missing package I noticed when doing apt build-dep is libvulkan-dev.
Can you please also include it, so I won't need to open another bug.
Thank you!
http://bugs.winehq.org/show_bug.cgi?id=58823
--- Comment #2 from Rosanne DiMesio dimesio@earthlink.net --- Both libxkbregistry-dev and libvulkan-dev are already listed as build dependencies in our Debian Testing .dsc file, https://build.opensuse.org/projects/Emulators:Wine:Debian/packages/wine-deve....
As you note, it is working as expected on the OBS. I don't know why it doesn't work on your system, but keep in mind that our scripts are designed for the OBS, which is not a standard Debian system. The recommended way to use our build scripts is on the OBS; anyone can create an account and branch our packages.
http://bugs.winehq.org/show_bug.cgi?id=58823
--- Comment #3 from Shmerl shtetldik@gmail.com --- Interesting, I'm not sure why it's not working using build-dep. May be it's falling back to Debian's own wine package for this and that is missing something? It can be some confusion of repositories priority potentially, since your source package is called "wine" and Debian's own repo source package is also called "wine".
Not a big deal though, I just install it manually in my local build script.
http://bugs.winehq.org/show_bug.cgi?id=58823
--- Comment #4 from Shmerl shtetldik@gmail.com --- Potentially, you can rename your source package from wine, to actual wine-devel to avoid this. Just an idea.
http://bugs.winehq.org/show_bug.cgi?id=58823
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #5 from Rosanne DiMesio dimesio@earthlink.net --- Marking invalid.
http://bugs.winehq.org/show_bug.cgi?id=58823
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Rosanne DiMesio dimesio@earthlink.net --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=58823
--- Comment #7 from Shmerl shtetldik@gmail.com --- I dug a bit more into it, while your dsc file has it, actual apt sources shown for your source package have stuff missing. I don't really get it:
Trying such command on Debian testing with your repo enabled:
apt showsrc wine
I get this among other things:
Package: wine Binary: wine-devel-i386, wine-devel-amd64, wine-devel, wine-devel-dev, wine-devel-dbg, winehq-devel Version: 10.17~forky-1 Maintainer: Rosanne DiMesio dimesio@earthlink.net, Marcus Meissner meissner@suse.com Original-Maintainer: WineHQ Builds webmaster@fds-team.de Build-Depends: autotools-dev, autoconf, bison, docbook-to-man, docbook-utils, docbook-xsl, flex, fontforge, gawk, gcc, gettext, libacl1-dev, libasound2-dev, libcups2-dev, libdbus-1-dev, libfontconfig1-dev | libfontconfig-dev, libfreetype6-dev, libgl1-mesa-dev, libglu1-mesa-dev, libgnutls30-dev | libgnutls28-dev | libgnutls-dev, libgphoto2-dev | libgphoto2-6-dev | libgphoto2-2-dev (>= 2.4.6), libgtk-3-dev, libice-dev, libkrb5-dev, libncurses6-dev | libncurses5-dev | libncurses-dev, libpcap-dev, libpulse-dev, libsane-dev, libsdl2-dev, libssl-dev, libstdc++6-4.5-dev | libstdc++-dev, libudev-dev, libv4l-dev, libx11-dev, libxcomposite-dev, libxcursor-dev, libxext-dev, libxi-dev, libxinerama-dev, libxrandr-dev, libxrender-dev, libxt-dev, libxxf86vm-dev, linux-libc-dev, ocl-icd-opencl-dev, patch, perl, sharutils, unixodbc-dev, x11proto-xinerama-dev
Note that this list is missing all ffmpeg deps (libav*), libxkbregistry-dev and libvulkan-dev. I don't get it really.
http://bugs.winehq.org/show_bug.cgi?id=58823
--- Comment #8 from Rosanne DiMesio dimesio@earthlink.net --- I see what's happening. Each Debian and Ubuntu version we package for has its own dsc file, but they all share the same control file in debian.tar.xz. Per https://en.opensuse.org/openSUSE:Build_Service_Debian_builds#Handling_build_..., the control file only contains build dependencies that are available in all the distros, while the dsc files contain the common dependencies as well as dependencies specific to each distro version.
The OBS uses the dsc file when setting up the build environment, but that file is not available to dpkg within the container--dpkg generates a dsc file based on the control file, which only contains dependencies common to all Debian/Ubuntu versions. libxkbregistry and libvulkan are not in the the control file because at the time they were added, there were still older versions we built packages for that did not provide them.
We are no longer building for those old versions, so I could add libxkbregistry and libvulkan to the control file, but keep in mind this is something that can occur any time a new dependency is added. This brings me back to what I said earlier: our build scripts are written for the OBS, they work on the OBS, but anyone trying to use them on any other system must be prepared to modify them as needed for the different environment.
http://bugs.winehq.org/show_bug.cgi?id=58823
--- Comment #9 from Shmerl shtetldik@gmail.com --- Interesting, thanks for clarifying!
http://bugs.winehq.org/show_bug.cgi?id=58823
--- Comment #10 from Shmerl shtetldik@gmail.com --- Side question, but where I can see the build logs in OBS for the WineHQ packages? I can use that to get some ideas how exactly you are configuring things for the official packages.
Thanks!
http://bugs.winehq.org/show_bug.cgi?id=58823
--- Comment #11 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Shmerl from comment #10)
Side question, but where I can see the build logs in OBS for the WineHQ packages? I can use that to get some ideas how exactly you are configuring things for the official packages.
Go to https://build.opensuse.org/project/show/Emulators:Wine:Debian. Click on whichever package you want to look at (devel, staging, stable). At the next screen, click on "Show excluded/disabled results", then click on "disabled" for whatever build log you want. That will take you to a screen where you can download the log file.
http://bugs.winehq.org/show_bug.cgi?id=58823
--- Comment #12 from Shmerl shtetldik@gmail.com --- Nice, thanks!
I was basically looking for this part:
./configure --prefix=/opt/wine-devel \ --libdir=${prefix}/lib \ --mandir=${prefix}/share/man \ --infodir=${prefix}/share/info \ --disable-tests \ --enable-archs=i386,x86_64 \
-
WineHQ Bugzilla