Source: dfu-programmer Version: 0.6.1-1 Severity: important X-Debbugs-Cc: Rodolphe PELLOUX-PRAYER <[email protected]>, [email protected], [email protected], [email protected], Package Salvaging Team <[email protected]>
Hi Rodolphe, It seems the package dfu-programmer has seen quite a series of unfortunate attempts to update it. To say it clearly: My prefered result to upgrade this package would be if I would sponsor this package while keeping you as Uploader. Your last message I've seen in BTS[1] about five years ago seemed you are interested to work on it but you did not found any sponsor. Unfortunately subsequent offers for sponsering were not answered by you - no idea why ... you might have missed these. I would be quite interested what you think about the sponsoring process and how it could be enhanced for you. Anyway, to break this circle and finally get the latest version of dfu-programmer into the archive I cloned your reporitory to the Debian/ team[2]. Since I had to update all three branches using MRs sounded to complex for me. I've sent you an invitation to this repository so you should have full access for future commits. I hope this location might simplify the cooperation on this repository. In case you disagree with this that's perfectly fine. Just merge the changes into your private repository if you want to upload from there (please also revert the change of Vcs fields in d/control in this case). As I said keeping the package in your hands by the help of sponsors would be my prefered solution. Since we observed in other cases that maintainers are somehow vanishing for whatever reason the alternative is to orphan the package. There is an attempt to introduce a new procedure, which I propose to call Intend To Orphan. While we have an established process for making minimal, fine-grained changes to a package, it does not cover broader improvements such as migrating to Salsa, updating the Standards-Version, or adjusting the debhelper compatibility level. However, some packages could benefit from more extensive changes, and this procedure aims to provide a structured way to implement them. Unlike the well-established Package Salvage procedure[3] which requires an active Uploader, the goal here is to allow collaborative work on a package on Salsa, even if no active uploader expresses interest in maintaining it. --> Maintainer set to Debian QA Group <[email protected]> If you do not agree to those large-scale changes to this package I did in Git, feel free to close this bug or tag it as 'wontfix' to inform others. There is no obligation to continue reading if your stance is clear, and that decision will, of course, be respected. Otherwise, I will follow the well-established timing of the ITS procedure, waiting 21 days before performing a QA Upload to delayed=10. This procedure has not yet reached consensus--I am simply exploring whether it could be accepted. It was disussed at DebConf25 but some consensus is pending. Please keep in mind that the goal of this process is to help ensure that packages remain up to date and well maintained. If you have suggestions for improving it, your feedback is most welcome. As said above I'd prefer if you keep on maintaining dfu-programmer but for completeness I mention the criteria for the orphaning process: - Bugs filed against the package do not have answers from the maintainer. - Upstream has released several versions, but despite there being a bug entry asking for it, it has not been packaged. - Not published with Vcs fields set to Salsa - No maintainer upload in the last 12 years (and no response to bugs since 5 years) - Standards-Version < 4 This package was highlighted in the Bug of the Day[4] initiative, which aims to introduce newcomers to manageable tasks and guide them through the workflow to solve them. The focus of this initiative is on migrating packages to Salsa, as it's a great way to help newcomers become familiar with a consistent Git-based workflow. Kind regards Andreas. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881075#15 [2] https://salsa.debian.org/debian/dfu-programmer [3] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [4] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
