On Saturday, December 6, 2025 11:43:49 PM Mountain Standard Time Md. Asif Hossain wrote: > I found my mistakes. Here is my new workflow: > > *1.* nano ~/.gbp.conf > *2. *[DEFAULT] > > # Manage a "pristine-tar" branch: > pristine-tar = True > pristine-tar-commit = True > > # Use Debian-style branch names: > upstream-branch=upstream/latest > debian-branch=debian/latest > > # Build packages with pbuilder: > # pbuilder = True > # Or use sbuild: > builder = sbuild > > # Sign tags (optional): > #sign-tags = True > #keyid = <fingerprint> > > *3. *gbp clone https://salsa.debian.org/Asif/ibus-avro.git > cd ibus-avro/ > git checkout debian/latest > git checkout -b debian/latest > git checkout debian/latest > > *4. *update debian/control with, Maintainer: Md. Asif Hossain < > md.asifhossainayon@gmail.com> > > *5. *update debian/changelog with, > ibus-avro (1.2+git20230914-1) unstable; urgency=low > > * First upload to mentors by Md. Asif Hossain > > -- Md. Asif Hossain <md.asifhossainayon@gmail.com> Sat, 06 Dec 2025 > 23:00:00 +0600 > > *6.* git status > git add . > git commit -m "Set self as maintainer and update version/changelog for > first upload" > > *7. Output:* > W: ibus-avro source: latest-debian-changelog-entry-reuses-existing-version > 1.2+git20230914-1 ~ 1.2+git20230914-1 (last used: Thu, 04 Apr 2024 17:29:47 > -0400) [debian/changelog:1] > > I: Lintian run was successful. Very good. You figured out that lintian is an automated system that checks for problems. It detected a few and you fixed them. Sometimes lintian is wrong in a particular case and we need to override it. But, in the majority of cases, lintian points you in the direction of something you need to fix. > *Questions:* > 1. "W: ibus-avro source: > latest-debian-changelog-entry-reuses-existing-version 1.2+git20230914-1 ~ > 1.2+git20230914-1 (last used: Thu, 04 Apr 2024 17:29:47 -0400) > [debian/changelog:1]" - Does this mean I have nothing to maintain? > 2. If I want to be a maintainer of this one, is there any probability to > take this one by others? If yes, how to prevent that? > 3. Am I doing the right thing? > 4. What to do next? There are a number of small things we need to do before we are ready to upload. Fixing these lintian tags are on the list. But, before we do them, there is something else I would recommend we do first: enable Salsa CI (this runs a bunch of Continuous Integration tests every time you commit to Salsa that help us to make sure we are not missing anything). To do so, follow the instructions at: https://salsa.debian.org/salsa-ci-team/pipeline Here is an example of a repository where this is enabled (changes need to be made in both these places): https://salsa.debian.org/soren/privacybrowser/-/blob/master/debian/salsa-ci.yml?ref_type=heads https://salsa.debian.org/soren/privacybrowser/-/settings/ci_cd#js-general-pipeline-settings When you have done that, the next time you commit to the repository (or you can trigger them manually) these test will run: https://salsa.debian.org/python-team/packages/python-electrum-ecc/-/pipelines/ 986655 By the way, don’t forget to copy your emails to debian- mentors@lists.debian.org. > *Internship update:* > Dear Student, > You can continue there as a volunteering/extra curricular activities. > For the 3 credit BSCS Internship course, it's a requirement for each > student to do industry oriented internship/job and necessary > certifications/documents like appointment letter, recommendation letter etc > are also required. > > So, I need to find another *suitable* one. I am sorry to hear that working on Debian will not satisfy the requirement of for your internship. I hope that you are able to find something that can. -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.