Bug#953127: RFS: fonts-jetbrains-mono/1.0.3-2 [ITP] -- free and open-source typeface for developers
Hello Adam, 2020-03-17 23:28 CET, Adam Borowski: > On Tue, Mar 17, 2020 at 11:41:25AM +0100, Romain Porte wrote: > > So, here is finally the proposed package for contrib/fonts inclusion: > > > https://mentors.debian.net/debian/pool/contrib/f/fonts-jetbrains-mono/fonts-jetbrains-mono_1.0.4-1.dsc > > In NEW, thanks for your work. Great news, thanks for your support! > > There is a link to the Debian Font Teams VCS (salsa) for the font > > hosting as I will only be uploader but I have set maintainer as fonts > > team. > > > > > Vcs-Git: https://salsa.debian.org/fonts-team/fonts-jetbrains-mono.git > > > Vcs-Browser: https://salsa.debian.org/fonts-team/fonts-jetbrains-mono > > > > Shall the repository be created by the fonts team, or is this reserved > > only for "main" fonts? > > There's no such restriction. And, in this font, every single bit is free -- > it's just a build-time problem. > > Repo created. Could you tell me what's your Salsa username? As I am not a DD (yet? ;)) I have created a guest account: https://salsa.debian.org/microjoe-guest Not sure what I can do with that. Am I expected to push the source package into the newly-created repo, like the other fonts repositories? Ciao, Romain. signature.asc Description: PGP signature
Bug#953127: RFS: fonts-jetbrains-mono/1.0.3-2 [ITP] -- free and open-source typeface for developers
On Tue, Mar 17, 2020 at 11:41:25AM +0100, Romain Porte wrote: > So, here is finally the proposed package for contrib/fonts inclusion: > https://mentors.debian.net/debian/pool/contrib/f/fonts-jetbrains-mono/fonts-jetbrains-mono_1.0.4-1.dsc In NEW, thanks for your work. > There is a link to the Debian Font Teams VCS (salsa) for the font > hosting as I will only be uploader but I have set maintainer as fonts > team. > > > Vcs-Git: https://salsa.debian.org/fonts-team/fonts-jetbrains-mono.git > > Vcs-Browser: https://salsa.debian.org/fonts-team/fonts-jetbrains-mono > > Shall the repository be created by the fonts team, or is this reserved > only for "main" fonts? There's no such restriction. And, in this font, every single bit is free -- it's just a build-time problem. Repo created. Could you tell me what's your Salsa username? Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi ⠈⠳⣄
Bug#953127: RFS: fonts-jetbrains-mono/1.0.3-2 [ITP] -- free and open-source typeface for developers
Hi Andrey, 2020-03-17 14:26 CET, Andrey Rahmatullin: > On Mon, Mar 16, 2020 at 11:56:07PM +0100, Adam Borowski wrote: > > > > $ 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. > > > > IIRC the message already includes a hint: you need to delete the > > fonts-jetbrains-mono_1.0.3-1_amd64.upload file. > Only in dput-ng. Nice catch! > $ dput mentors fonts-jetbrains-mono_1.0.4-1_amd64.changes > Package fonts-jetbrains-mono was already uploaded to mentors > If you want to upload nonetheless, use --force or remove > fonts-jetbrains-mono_1.0.4-1_amd64.mentors.upload So I have installed dput-ng over dput to avoid this problem (and others yet-to-be-found) issues to occur in the future. I started using dput after reading the "Chapter 9. Uploading the package" [1] of the Debian Maintainer guide [2]. It tells that the "dput" tool is now priviledged over "dupload" command. Maybe we should be more specific and recommend "dput-ng" as a more newcomer-friendly alternative to dput on this page? [1] https://www.debian.org/doc/manuals/maint-guide/upload.html [2] https://www.debian.org/doc/manuals/maint-guide/ Ciao, Romain. signature.asc Description: PGP signature
Bug#953127: RFS: fonts-jetbrains-mono/1.0.3-2 [ITP] -- free and open-source typeface for developers
On Mon, Mar 16, 2020 at 11:56:07PM +0100, Adam Borowski wrote: > > > $ 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. > > IIRC the message already includes a hint: you need to delete the > fonts-jetbrains-mono_1.0.3-1_amd64.upload file. Only in dput-ng. -- WBR, wRAR signature.asc Description: PGP signature
Bug#953127: RFS: fonts-jetbrains-mono/1.0.3-2 [ITP] -- free and open-source typeface for developers
Hi, 2020-03-16 23:56 CET, Adam Borowski: > > 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. > > IIRC the message already includes a hint: you need to delete the > fonts-jetbrains-mono_1.0.3-1_amd64.upload file. Well, this is not very explicit, but it indeed did the trick. After that I was notified by the watch system that the package was updated to version 1.0.4 6 days ago. So, here is finally the proposed package for contrib/fonts inclusion: https://mentors.debian.net/package/fonts-jetbrains-mono That can be locally examinated using the .dsc file: https://mentors.debian.net/debian/pool/contrib/f/fonts-jetbrains-mono/fonts-jetbrains-mono_1.0.4-1.dsc There is a link to the Debian Font Teams VCS (salsa) for the font hosting as I will only be uploader but I have set maintainer as fonts team. > Vcs-Git: https://salsa.debian.org/fonts-team/fonts-jetbrains-mono.git > Vcs-Browser: https://salsa.debian.org/fonts-team/fonts-jetbrains-mono Shall the repository be created by the fonts team, or is this reserved only for "main" fonts? Ciao, Romain. signature.asc Description: PGP signature
Bug#953127: RFS: fonts-jetbrains-mono/1.0.3-2 [ITP] -- free and open-source typeface for developers
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. signature.asc Description: PGP signature
Bug#953127: RFS: fonts-jetbrains-mono/1.0.3-2 [ITP] -- free and open-source typeface for developers
On Mon, Mar 16, 2020 at 09:20:49PM +0100, Romain Porte wrote: > 2020-03-16 20:52 CET, Adam Borowski: > > On Mon, Mar 16, 2020 at 01:02:38PM +0100, Romain Porte wrote: > > > 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. While I, and many others, don't like that, it's an acceptable solution. > 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). Right, good so far. > 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. IIRC the message already includes a hint: you need to delete the fonts-jetbrains-mono_1.0.3-1_amd64.upload file. > Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi ⠈⠳⣄
Bug#953127: RFS: fonts-jetbrains-mono/1.0.3-2 [ITP] -- free and open-source typeface for developers
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... > 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". > 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. But it's the buildable-from-source -or- contrib issue that's the blocker. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi ⠈⠳⣄
