Hi Adam, 2020-03-16 20:52 CET, Adam Borowski: > On Mon, Mar 16, 2020 at 01:02:38PM +0100, Romain Porte wrote: > > I am requiring your mentorsip help to publish this package. > > I have received some feedback from Adam, but not much since then. > > Sorry for not responding sooner, my TODO list is bursting at seams. > It seems to one else responded as well... No problem, I understand that everyone can be busy, myself uncluded. ;) I shouted out to debian-devel also because I have been observing the ongoing threads and one newcomer has been greatly helped in proposing her/his first contribution to the project. But if you can continue the sponsoring then thanks! > > Our discussion about the package can be followed on the ITP bug: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952954 > > The main obstacle being the FontLab format problem, and I'm not very > knowledgeable about it. Unless there's some free tool that can read that > format and convert it (possibly in multiple hops) to TrueType, the font > can't enter the main archive. > > It would be greatly preferred to find a solution, but if one can't be > found, the "contrib" archive can be used. For that, you'd change > "Section: fonts" to "Section: contrib/fonts". So that was it! It was really unclear for me what the options we had, as I am very new to the ecosystem I did not think about changing the Section to contrib/fonts in order to "fix" this issue. As we do not find a compromise for main inclusion, I am fine for this package to go to contrib. I can explain the why in the debian/copyright file as suggested by Lintian when I have changed the section. > > The package has been released to -2 Debian release with some > > improvements. > > > > Changes since the last upload: > > But... there was no previous upload. Unless you know of any actual users > who rely on your -1 packaging, the Debian scheme is to avoid bumping the > version for any of WIP versions that did not enter the distribution. > > Thus, unless there's a good reason, it would be nice if you could mark > the changelog entry as -1. So my problem was that after first publication on mentors, the "dput" call to the same -1 revision was refused because the file was already existing on the server. I have just retried now after updating the section and copyright file and dput went fine: > Successfully uploaded fonts-jetbrains-mono_1.0.3-1.dsc to mentors.debian.net for mentors. > Successfully uploaded fonts-jetbrains-mono_1.0.3.orig.tar.xz to mentors.debian.net for mentors. > Successfully uploaded fonts-jetbrains-mono_1.0.3-1.debian.tar.xz to mentors.debian.net for mentors. > Successfully uploaded fonts-jetbrains-mono_1.0.3-1_all.deb to mentors.debian.net for mentors. > Successfully uploaded fonts-jetbrains-mono_1.0.3-1_amd64.buildinfo to mentors.debian.net for mentors. > Successfully uploaded fonts-jetbrains-mono_1.0.3-1_amd64.changes to mentors.debian.net for mentors. But just after that I received an email saying that the package could not be updated: > Hello, > > Unfortunately your package "fonts-jetbrains-mono" was rejected because > of the following reason: > > An upload with the same version but different distribution exists on > mentors. If you wish to upload this version for an other > distribution, delete the old one. > > Please try to fix it and re-upload. Thanks, So I deleted the whole package (all revisions) in the mentors web interface (cannot be done directly on command line? I think --force on dput would not help here as it is mentors-specific). But now when I am retrying to republish the package in mentors I get the following: > $ dput mentors fonts-jetbrains-mono_1.0.3-1_amd64.changes > Package has already been uploaded to mentors on mentors.debian.net > Nothing more to do for fonts-jetbrains-mono_1.0.3-1_amd64.changes And… basically reproduced it! This is why I have bumped the debian revision between -1 and -2 in the first place in my first uploads. I am quite lost in the steps to overcome this situation properly right now. > But it's the buildable-from-source -or- contrib issue that's the blocker. I think we should go the contrib-way. I have fixed the package locally and need some place to upload this fixed -1 release. Thanks again for your support. Ciao, Romain.
Attachment:
signature.asc
Description: PGP signature