Wireshark-dev: Re: [Wireshark-dev] Future of Wireshark's Debian packaging scripts in the main r

From: João Valverde <j@xxxxxx>
Date: Thu, 23 Nov 2023 13:22:31 +0000
I kindly ask you to decide whether we should keep the Debian package as-is and explain the use-case for the current state of the Debian package in Wireshark, because it is not clear to me at all. Honestly, the situation kind of baffles me since it is not used by the Debian project and they don't help maintain it. Mistakes happen but it is necessary to allow debate and course-corrections IMO. I still remember of painful it was to fix and eventually remove the ABI checker thing that severely degraded the old autotools build.

I don't think anyone should be upset if things don't go their way, as long as decisions are based on technical merit and minimally sound judgement. Anyway it's better to have a resolution for these sort of disagreements.

On 22/11/23 18:28, Gerald Combs wrote:
I think this falls well within the scope of the steering committee, and would be a good first exercise.

On 11/22/23 3:45 AM, Roland Knall wrote:
Hi

I would recommend that we bring this topic before the technical steering committee. As of right now, that committee needs to be formed in January and this topic is exactly why we are going to have the committee in the first place. The process is in the final steps and should be finished by the end of the year anyway.

I do not think that further discussing this issue is actually beneficial for the long term resolution of this situation. Both sides have valid arguments and good pointers and I would suggest as soon as the committee has taken up the topic we collectively create a single mission statement as suggested by Joao above. Until then, personally I will refrain from discussing this further, as I have said everything there is to say from my perspective.

Do you agree Gerald?

kind regards
Roland



Am Mi., 22. Nov. 2023 um 12:36 Uhr schrieb João Valverde <j@xxxxxx <mailto:j@xxxxxx>>:

    __
    Maybe you´d like to volunteer to maintain the Wireshark Debian assets? Since you've got the experience and actually use it?

    There are loads of lintian warnings waiting to be fixed, or there were until recently. Maybe you'd like to start there, and be more active staying on top of the all-important symbol lists. Just a thought.

    On 21/11/23 15:00, Anders Broman wrote:
    Hi,
    I found it useful to be able to do Debian packages easily to provide internal installation packages and even ppa for Ubuntu.
    So I have been using the Debian build system.
    Best regards
    Anders

    Den tis 21 nov. 2023 15:48Roland Knall <rknall@xxxxxxxxx <mailto:rknall@xxxxxxxxx>> skrev:

        As mentioned on the ticket - just putting it here as well - I am against dropping packaging/debian. But I am for having it underneath packaging, and not in the main directory, which is what the original change was about. I respect Joao's opinion as well as yours Balint. In this case here I think, we can provide assistance for future implementors and as a starting point, by keeping the directory underneath packaging/debian.

        just my thoughts
        Roland


        Am Di., 21. Nov. 2023 um 15:28 Uhr schrieb Bálint Réczey <balint@xxxxxxxxxxxxxxx <mailto:balint@xxxxxxxxxxxxxxx>>:

            Hi All,

            João shared his opinion about the project's commitment to maintain the
            packaging/debian/ in the project's repository:

https://gitlab.com/wireshark/wireshark/-/commit/79da670bd1b4f91eebee5c96b19eaf1f33c94777#note_1656501952 <https://gitlab.com/wireshark/wireshark/-/commit/79da670bd1b4f91eebee5c96b19eaf1f33c94777#note_1656501952>

            I believe the current practice is reasonable and beneficial enough for
            many parties to warrant the work, but I could be wrong.

            Probably the most important question is if there is anyone relying on             the packaging scripts there. If you are, please speak up otherwise the
            directory may be dropped.

            Comments are welcome.

            Cheers,
            Balint
___________________________________________________________________________
            Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>             Archives: https://www.wireshark.org/lists/wireshark-dev <https://www.wireshark.org/lists/wireshark-dev>             Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev <https://www.wireshark.org/mailman/options/wireshark-dev>  mailto:wireshark-dev-request@xxxxxxxxxxxxx <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe

___________________________________________________________________________
        Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>         Archives: https://www.wireshark.org/lists/wireshark-dev <https://www.wireshark.org/lists/wireshark-dev>         Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev <https://www.wireshark.org/mailman/options/wireshark-dev>  mailto:wireshark-dev-request@xxxxxxxxxxxxx <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe


___________________________________________________________________________
    Sent via:    Wireshark-dev mailing list<wireshark-dev@xxxxxxxxxxxxx> <mailto:wireshark-dev@xxxxxxxxxxxxx>     Archives:https://www.wireshark.org/lists/wireshark-dev <https://www.wireshark.org/lists/wireshark-dev> Unsubscribe:https://www.wireshark.org/mailman/options/wireshark-dev <https://www.wireshark.org/mailman/options/wireshark-dev> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe <mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe>

___________________________________________________________________________
    Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>     Archives: https://www.wireshark.org/lists/wireshark-dev <https://www.wireshark.org/lists/wireshark-dev>     Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev <https://www.wireshark.org/mailman/options/wireshark-dev>                   mailto:wireshark-dev-request@xxxxxxxxxxxxx <mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe