Re: Guidence over testing

[Carsten Schoenert <c.schoenert@t-online.de>]

Hello Jai Kadam,

Am 05.12.25 um 09:59 schrieb Jai kadam:
..
> I should probably read all manuals now :)

yes, that is something we do expect from you.
So did you ever read the manual of git-buildpackage (aka gbp)? gbp is 
the chosen helper tool by the DPT, it's essential you know it!

https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/

You need to to get familiar with that, otherwise it's for you but also 
for others quite cumbersome to help.

You need to understand what steps you need to make and why, also what 
configure options you will need to give the various gbp commands sometimes.

The usual dance you will need to do with every new upstream version is:

1. Import the newer version into the packaging git tree.
2. Look into the changes Upstream has done like increased required
   versions for build depending packages or new added dependencies.
3. Adjust/Add/Remove additional needed patches if needed, the so called
   patch-queue.
4. Look into open bug reports and fix them if possible.
5. Adjust the packaging like updating copyright information, adjust
   sequencer files, fix build and test suite issues, check .
6. Look into merge requests if existing.
7. Adjust/Update the CI/autopkgtest setup if needed.
8. Check if you need to update the debian/ folder in case a bump of the
   Debian Policy was released. The current value for Standards-Version
   is 4.7.2.
9. Run Lintian after your test build and fix Warnings, Errors and if
   possible other flags too.
10. Reach out for help if you feeling lost, don't end in try & error
    in case you do not really understand what's going wrong and why.

And as for you as a newcomer I would suggest to also get familiar with 
(git-)pbuilder first. It's to me easier to learn for starters and for 
building packages it doesn't matter if you use pbuilder or sbuild. Once 
you are more experienced you can dive into sbuild at any time then.

--
Regards
Carsten