On Sat, Dec 20, 2025 at 12:12:00PM +0600, Md. Asif Hossain wrote:
>Hello,
>
>I have a few questions and would appreciate your guidance.
>
>1. Do I need to create the _source.changes file manually?
Of course no, you need to create it by building the package.
>If not, can I safely avoid creating the following files: ~/.dput.cf,
>config.pl, and nstable-amd64.tar.zst?
No, you need to use both sbuild and dput so you need files used by them.
>From my understanding, these files are only used for generating the
>_source.changes file.
This is not true, especially about .dput.cf.
>2. What should I do with the generated .deb file? Is it required for the
>upload process, or should it be ignored?
If you upload the binary .changes it will be uploaded, otherwise it will
be ignored.
But you are not building the package just to upload it to mentors, you are
building it to make sure that it builds and that installing and using it
works and to run QA tools on it, starting with lintian.
>3. I noticed one remaining issue regarding versioning.
>The generated file is:
>
>ibus-avro_1.2+git20230914-1_source.changes
>
>but I expected:
>
>ibus-avro_1.2+git20230914-2_source.changes
>
>Please note that I am building from origin/debian/latest. I would like to
>understand why the version number is not incrementing as expected which is
>the same for other files also.
Did you add a new changelog entry for -2?
>4. Do I need to sign both .changes files, or is signing only one?
You sign whatever you upload.
--
WBR, wRAR