On Tue, 2024-12-10 at 00:35 -0800, Xiyue Deng wrote: > Hi Phil, > > Phil Wyett <philip.wy...@kathenas.org> writes: > > > > [..snip..] > > > > Morning Xiyue and all, > > > > Xiyue mentions tooling after Sam raised an issue. > > > > Xiyue, Many thanks for entering this conversation as I feel you are an ideal > > person (through our many interactions) to detail/discuss what you feel > > mentors > > is, is not, what is expected of the submitter and the reviewer; and what > > mentors should be. > > > > As a none DD I do basic build testing and validation of packages and their > > files in-order to bring them up to a minimum standard for a DD to then look > > at. > > This is to encourage Debian Developers to review and sponsor packages in > > mentors. A mentors package submission at the stage tagged 'confirmed' on the > > RFS bug means it is decent shape and be less of a strain on a DD's time. > > > > I use the sbuild using unshare[1] setup which can also run lintian, piuparts > > and autopkgtest test when configured. > > > > pbuilder I have historically used in the same minimal build VM sbuild for > > build > > after successful build tests. > > > > We use 'licenserecon' command 'lrc' to do validation checking of > > 'd/copyright'. > > This tool is new and improving. Manual checking are also used. > > > > I do not use scripts or have it automated. I do these tests manually across > > two > > laptops for each package I review. Automation and documentation is on the > > to-do > > list. > > > > My work on mentors is with primarily already available Debian tools and > > Visual > > Studio Code. The key thing is the time I am fortunate to be able to give to > > Debian due to my circumstances. > > > > An expectation that once a DD does an upload for you, they are obligated to > > do > > them for you from that point on I have seen in and around mentors. Unless a > > DD > > specifically makes a commitment to a package, I believe that all package > > uploads by a a DD are a one shot and there should be no expectation a DD > > will > > be available to do it in the future. All submitters I feel should file an > > RFS > > and an available DD can be canvassed for or waited for. > > > > [1] https://wiki.debian.org/sbuild#Setup > > > > Thanks for explaining your workflow in detail! I didn't realize this > also involves manual work, and my kudos for working on so many RFS bugs > nonetheless! > > I think Phil's checking work provides many good feedback on many obvious > packaging issues, and once an RFS bug is confirmed, the package will be > in a sufficiently good shape for sponsoring. Any further issue may > require more domain knowledge and may be beyond the scope of automated > tools. > > I'm really looking forward to see Phil continuing on automating and > documenting these tools. Once that happens, I wonder whether there > would be interest in making Phil's work a service on mentors.d.n or BTS > (like bartm@d.o)? I think it would be a great addition to complement > local Lintian runs and Salsa CI. >
Hi Xiyue, I will try to get some further work done soon. The checks I do are of course always subject to review and change if conversation on the mentors list mandated it. I believe the initial current tests for contributors are consistent for all and I would hope for many to become muscle memory. One of the goals is Reproducible builds testing, a hope to make it part of everyone's work flow, highlight its importance. The tests and format of the report is there and I am ever hopeful others interested in Debian Mentors may use it. I would be very happy if other reviewers came forward to help and learn more about Debian. Mentors is a great place to learn. Regards Phil -- Donations... Buy Me A Coffee: https://buymeacoffee.com/kathenasorg Liberapay: https://liberapay.com/kathenas -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Matrix: #kathenas:matrix.org Website: https://kathenas.org Wiki: https://wiki.kathenas.org Instagram: https://instagram.com/kathenasorg Threads: https://www.threads.net/@kathenasorg --
signature.asc
Description: This is a digitally signed message part
