Hello,
I have a few questions and would appreciate your guidance.
1. Do I need to create the _source.changes file manually?
If not, can I safely avoid creating the following files: ~/.
dput.cf,
config.pl, and nstable-amd64.tar.zst?
From my understanding, these files are only used for generating the _source.changes file.
2. What should I do with the generated .deb file? Is it required for the upload process, or should it be ignored?
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.
4. Do I need to sign both .changes files, or is signing only one?
Additionally, I would like to apologize for a mistake in my previous email—I replied instead of using “Reply All,” which is why the message did not reach
debian-mentors@lists.debian.org. I am including the content here again for completeness.
---------------------------------------------------------------------------------------------
I realized that I previously made a mistake by creating the
config.pl
file under ~/.cache/sbuild instead of the correct location,
~/.config/sbuild. After solving that, when I ran gbp buildpackage, I
encountered the following error:
Error reading configuration: PIUPARTS binary 'piuparts' does not exist or is not executable
gbp:error: 'sbuild' failed: it exited with 2
According to chatgpt's suggestion my current ~/.config/sbuild/
config.pl contains the following:
$chroot_mode = 'unshare';
$build_arch_all = 1;
$build_source = 1;
$source_only_changes = 1;
$run_lintian = 1;
$run_autopkgtest = 0;
$run_piuparts = 0;
With
this configuration, the _source.changes file is now generated
correctly. However, I noticed one remaining issue: the generated file is
ibus-avro_1.2+git20230914-1_source.changes (-1_source.changes)
instead of the expected:
ibus-avro_1.2+git20230914-2_source.changes (-2_source.changes)
I
am building from origin/debian/latest, so I wanted to ask whether this
version mismatch indicates that I may be building from an older
changelog entry, or if there is another step I should verify to ensure
the correct version is used.
Could you please let me know if my
current configuration and workflow look correct, and advise me on how
best to address the version numbering issue? If everything is ok then I
am willing to run "debsign ibus-avro_1.2+git20230914-1_source.changes" to sign the changes file with my GPG key and so on. Do I need to sign both .changes files or this one only?
Thank you very much for your time and guidance.
Best regards,
Md. Asif Hossain