Hi,
Thanks for your answer. I'll take a look after my new year vacation.
Just a question about a package which block the new version of Wine integration.
vkd3d 1.2-6 in Experimental is not usable in Sid because it needs mesa-vulkan-driver << 21.
Michael did that because vkd3d tests fails during building. I don't know
why because it fails with mesa 20 too.
I opened a bug report upstream and wine/vkd3d developer told me that there
is this issue because of nobody has the same GPU (someone can have the
error and someone else not)
The question is :
It is possible to don't make the test to package the app ?
it's possible to pass "--disable-tests" as argument for configure.
Thanks,
Le jeu. 30 déc. 2021 à 10:27, Wouter Verhelst <
[email protected]> a écrit :
Hi Maxime,
On Tue, Dec 21, 2021 at 07:47:47PM +0100, Maxime Lombard wrote:
Hello,
I'm an user of Debian since 10 years ago and it's only now that i
decide
to help to packaging.
I send this email about wine and wine-development package which are
not
updated since a very long time.
The last wine stable version on Sid is the 5.0 and development
version is
6.0+repack. Currently, the wine source code is frozen and the new
stable
version 7.0 will release next month.
--> I sent email to Michael Gilbert (without answer from him) and
open a
bug report recently to update package.
Same thing with vkd3d package 1.2 which is still in "experimental"
since a
long time too.
I think it's not in Unstable because the test fail with
mesa-vulkan-driver
>= 21 (see changelog)
--> I open a bug report upstream about this failure (see
https://bugs.winehq.org/show_bug.cgi?id=52248). Is it possible to
build
the package without to do test (set --disable-tests to configure) ?
Nowadays, the last package of wine-development was uploaded ~6 months
ago.
More bugs report opened the last months have no answer from Maintainer
(999753, 995580), same thing with vkd3d bug (994186, 993570)
I packaged myself vkd3d 1.2-7 and wine-development 7.0~rc2 and all
works
correctly.
I updated debian folder for wine to prepare the next Stable version.
My question is, how to contribute and hope to have updated version of
this
package in Debian since I am a novice ?
https://www.debian.org/devel/join/ should help as a general introduction
on how to contribute.
Assuming you built your updated wine package by getting the existing
wine packages and updating them for the new upstream version (your mail suggests that, but I'm not sure), you have a few options.
First, you can send a patch to the Debian BTS. The easiest way to
accomplish this is by way of the "debdiff" program in the "devscripts" package; see its man page for details. Alternatively, you can publish
your build directory in a git repository somewhere, possibly on salsa.debian.org, and let the wine developers (who gather on the [email protected] mailinglist) know.
If you don't get any feedback from the wine maintainers, you should
probably contact the debian mentors mailinglist (link on the join page
above) to request more help.
Hope this helps,
--
w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}
<div dir="auto">Hi,<div dir="auto"><br></div><div dir="auto">Thanks for your answer. I'll take a look after my new year vacation. </div><div dir="auto"><br></div><div dir="auto">Just a question about a package which block the new version of Wine
integration.</div><div dir="auto"><br></div><div dir="auto">vkd3d 1.2-6 in Experimental is not usable in Sid because it needs mesa-vulkan-driver << 21.</div><div dir="auto"><br></div><div dir="auto">Michael did that because vkd3d tests fails during
building. I don't know why because it fails with mesa 20 too.</div><div dir="auto"><br></div><div dir="auto">I opened a bug report upstream and wine/vkd3d developer told me that there is this issue because of nobody has the same GPU (someone can have
the error and someone else not)</div><div dir="auto"><br></div><div dir="auto">The question is :</div><div dir="auto">It is possible to don't make the test to package the app ?</div><div dir="auto">--> it's possible to pass "--disable-
tests" as argument for configure.</div><div dir="auto"><br></div><div dir="auto">Thanks,</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le jeu. 30 déc. 2021 à 10:27, Wouter Verhelst <<a href="mailto:
[email protected]">
[email protected]</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Maxime,<br>
On Tue, Dec 21, 2021 at 07:47:47PM +0100, Maxime Lombard wrote:<br>
> Hello,<br>
> <br>
> I'm an user of Debian since 10 years ago and it's only now that i decide<br>
> to help to packaging.<br>
> I send this email about wine and wine-development package which are not<br>
> updated since a very long time.<br>
> The last wine stable version on Sid is the 5.0 and development version is<br>
> 6.0+repack. Currently, the wine source code is frozen and the new stable<br>
> version 7.0 will release next month.<br>
> --> I sent email to Michael Gilbert (without answer from him) and open a<br>
> bug report recently to update package.<br>
> Same thing with vkd3d package 1.2 which is still in "experimental" since a<br>
> long time too.<br>
> I think it's not in Unstable because the test fail with mesa-vulkan-driver<br>
> >= 21 (see changelog)<br>
> --> I open a bug report upstream about this failure (see<br> > <a href="
https://bugs.winehq.org/show_bug.cgi?id=52248" rel="noreferrer noreferrer" target="_blank">
https://bugs.winehq.org/show_bug.cgi?id=52248</a>). Is it possible to build<br>
> the package without to do test (set --disable-tests to configure) ?<br>
> Nowadays, the last package of wine-development was uploaded ~6 months ago.<br>
> More bugs report opened the last months have no answer from Maintainer<br>
> (999753, 995580), same thing with vkd3d bug (994186, 993570)<br> > I packaged myself vkd3d 1.2-7 and wine-development 7.0~rc2 and all works<br>
> correctly.<br>
> I updated debian folder for wine to prepare the next Stable version.<br>
> My question is, how to contribute and hope to have updated version of this<br>
> package in Debian since I am a novice ?<br>
<a href="
https://www.debian.org/devel/join/" rel="noreferrer noreferrer" target="_blank">
https://www.debian.org/devel/join/</a> should help as a general introduction<br>
on how to contribute.<br>
Assuming you built your updated wine package by getting the existing<br>
wine packages and updating them for the new upstream version (your mail<br> suggests that, but I'm not sure), you have a few options.<br>
First, you can send a patch to the Debian BTS. The easiest way to<br> accomplish this is by way of the "debdiff" program in the "devscripts"<br>
package; see its man page for details. Alternatively, you can publish<br>
your build directory in a git repository somewhere, possibly on<br>
<a href="
http://salsa.debian.org" rel="noreferrer noreferrer" target="_blank">salsa.debian.org</a>, and let the wine developers (who gather on the<br>
<a href="mailto:
[email protected]" target="_blank" rel="noreferrer">
[email protected]</a> mailinglist) know.<br>
If you don't get any feedback from the wine maintainers, you should<br> probably contact the debian mentors mailinglist (link on the join page<br> above) to request more help.<br>
Hope this helps,<br>
-- <br>
w@uter.{be,<a href="
http://co.za" rel="noreferrer noreferrer" target="_blank">co.za</a>}<br>
wouter@{<a href="
http://grep.be" rel="noreferrer noreferrer" target="_blank">grep.be</a>,<a href="
http://fosdem.org" rel="noreferrer noreferrer" target="_blank">fosdem.org</a>,<a href="
http://debian.org" rel="noreferrer noreferrer" target="_blank">debian.
org</a>}<br>
</blockquote></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)