Bug#1110410: RFS: editorconfig-geany/0.2.1-1 [ITP] -- EditorConfig support for Geany
Control: tags -1 moreinfo
Hi Robert,
On Mon, Aug 04, 2025 at 05:32:53PM -0400, Robert Di Pardo wrote:
> Package: sponsorship-requests
> Severity: wishlist
> X-Debbugs-CC: pkg-geany-team@lists.alioth.debian.org
>
> Dear mentors,
>
> I am looking for a sponsor for my package "editorconfig-geany":
>
> * Package name : editorconfig-geany
> Version : 0.2.1-1
> Upstream contact : Andreas Wirooks <andreas.wirooks@1und1.de>
> * URL : https://github.com/editorconfig/editorconfig-geany
> * License : GPL-2.0+
> * Vcs : https://github.com/editorconfig/editorconfig-geany
> Section : devel
>
short review, based on the mentors version uploaded 2025-08-08 19:27
d/README.source should contain information as described in
Debian Policy 4.14 - it does not, so best is to delete this file.
d/changelog:
The initial upload of a package only one entry:
- Initial release (Closes: #890252) <nnnn is the bug number of your ITP>
remove the other/older entries.
(That will also fix a lintian warning)
d/control:
Please remove versions constraints of your B-Ds that are already fulfilled
since oldstable. (that is for geany in your case.)
You don't need to Depend on geany-common, it is pulled in by geany
already.
VCS-Fields point to where the packaging is happening, not the upstream
repo. (Upstream has a debian directory, so this will be extra
confusing.)
Please create a repository e.g on salsa.debian.org.
If you want me to create a repo in the Debian namespace, give me a
poke and I'll add you to the ACL as well.
I think the Homepage-Field should point to https://editorconfig.org/
Lintian:
W: editorconfig-geany source: odd-historical-debian-changelog-version 1 (for non-native) [debian/changelog:8]
I: editorconfig-geany source: debian-watch-contains-dh_make-template Example watch control file for uscan [debian/watch]
I: editorconfig-geany: hardening-no-bindnow [usr/lib/x86_64-linux-gnu/geany/editorconfig-geany.so]
Please update the package and then remove the moreinfo tag.
(Note: I did not do the copyright review yet)
--
tobi
Reply to: