On Wednesday, December 24, 2025 10:32:17 AM Mountain Standard Time Md. Asif Hossain wrote: > You can set a default key in ~/.devscripts.conf. My file contains the > > > following entry: > > > > DEBSIGN_KEYID="2D48F45A7EBE8C12" > > I > > In my case, it is ~/.devscripts. Good catch. Mine is also ~/.devscripts; ~/.devscripts.conf was a typo. > I uploaded both .changes files, and I would like to confirm whether this is > necessary. > > When I ran: > > dput mentors ibus-avro_1.2+git20230914-3_amd64.changes > > it uploaded the following files successfully: > > - > > ibus-avro_1.2+git20230914-3.dsc > - > > ibus-avro_1.2+git20230914-3.debian.tar.xz > - > > ibus-avro_1.2+git20230914-3_all.deb > - > > ibus-avro_1.2+git20230914-3_amd64.buildinfo > - > > ibus-avro_1.2+git20230914-3_amd64.changes > > After that, when I tried to run: > > dput mentors ibus-avro_1.2+git20230914-3_source.changes > > it initially returned a 403 Forbidden error, even though the GPG signatures > were valid. > > Error: > Checking signature on .changes > gpg: /home/theboss/Documents/Maintain > ibus-avro/ibus-avro_1.2+git20230914-3_source.changes: Valid signature from > 9DA7036E0282625F > Checking signature on .dsc > gpg: /home/theboss/Documents/Maintain > ibus-avro/ibus-avro_1.2+git20230914-3.dsc: Valid signature from > 9DA7036E0282625F > Uploading to mentors (via https to mentors.debian.net): > Uploading ibus-avro_1.2+git20230914-3.dsc: Upload failed: 403 Forbidden > > > However, I did receive a confirmation email. After some time, I retried the > same command and it uploaded successfully. > It uploaded the following files successfully: > > - ibus-avro_1.2+git20230914-3.dsc > - ibus-avro_1.2+git20230914-3.debian.tar.xz > - ibus-avro_1.2+git20230914-3_amd64.buildinf > - ibus-avro_1.2+git20230914-3_source.changes > > > Confirmation email: > Subject: ibus-avro_1.2+git20230914-3: ACCEPTED on mentors (unstable) > Body: > Hi. What happened is that you uploaded it twice, and the second upload replaced the first upload. The system was programmed to not let you do that while the first upload was processing, which is why it failed the first time and succeeded after you had waited a while. You can see this as upload #1 and upload #2 at: https://mentors.debian.net/package/ibus-avro/ As one of the other responses on Debian Mentors pointed out, you want to upload only the amd64.changes, as it will be able to produce more lintian output than the source.changes. > Your upload of the package 'ibus-avro' to mentors.debian.net was > successful. Others can now see it. The URL of your package is: > > https://mentors.debian.net/package/ibus-avro/ > > The respective dsc file can be found at: > > > https://mentors.debian.net/debian/pool/main/i/ibus-avro/ibus-avro_1.2+git20230 > 914-3.dsc > > If you do not yet have a sponsor for your package you may want to go to: > > https://mentors.debian.net/sponsors/rfs-howto/ibus-avro/ > > and set the "Seeking a sponsor" option to highlight your package on the > welcome page. > > You can also send an RFS (request for sponsorship) to the debian-mentors > mailing list. Your package page will give you suggestions on how to > send that mail. Use the example RFS template at the URL above to file an RFS bug to the Debian Mentors mailing list. This is the official way you request a sponsor. Even though I am already working on sponsoring your package, it is good for you to know how to do this so you can find sponsors in the future. Once the RFS is files, we will work on the few things that need to be fixed, some of which are highlighted by lintian, and then we can release it. -- Soren Stoutner soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.