Il 01/01/2022 03:31, Leandro Cunha ha scritto:
> Hi,
>
> On Tue, Dec 21, 2021 at 4:06 PM Maxime Lombard <berillions@gmail.com> 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 ?
>>
>> Thanks for your answer,
>> Maxime
> Yes, there are some packages that haven't been updated for a while.
> One of them is the retroarch that next year completes its second without
> updates and the chromium.
> And I believe it is open to anyone who wants to contribute.
> There are some processes such as ITS, NMU, QA (orphan packages) and team
> upload (for packages kept in teams where it is necessary to work with
> someone on the team or be part of the team).
>
> I usually help with QA work and team uploads. But I did deal with ITS once.
>
> Full reference on this.
> https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#managing-packages
> https://www.debian.org/devel/wnpp
> https://wiki.debian.org/WNPP
> https://wnpp.debian.net
>
> I remember thinking that it was necessary to be a DM or DD to
> contribute to Debian
> and over time I realized I was wrong.
I also contributing for 7 years only via git (alioth and salsa) without
being DM but in some cases as I have seen recently with debian-cinnamon
packages where when this year in the team there was some months with no
DD/DM (with upload permission) active it was difficult to find someone
who sponsored the uploads (with the major versions there are up to 15-16
components to be uploaded at the same time) the work prepared took up to
a month to be uploaded (now the problem has just been solved)
@Maxime: So probably if you start contributing regularly I think it is
better that you start creating an account on https://nm.debian.org/ and
create a gpg key with which to sign the work done to speed up a possible
transition to DM in the future if situations such as mine will happen
(moreover in a period with particular other unforeseen events, including
above all the coronavirus that complicate things)
about disabling tests try to add an override to debian/rules:
> override_dh_auto_test:
> : # disable it
In any case big thanks for your help improving/updating packages, wine I
had already seen that it would need help and it would be useful to also
have the latest stable versions in the backports (only if there is
really enough time after updating / improving the packages) but
unfortunately I don't have enough time to contribute to those too
>
> Happy 2022! ;)
>