Bug#923605: ITP: dhcpoptinj -- DHCP option injector (updated: 0.5.2-1)
The package now contains latest upstream (0.5.2) as well as fixes to debian/copyright (typo in GPL version, include "+", rename "MIT" to "Expat" and remove copyright lines from Expat licence text). Best regards -- Andreas Misje
Bug#925505: closed by Adam Borowski (Re: Bug#925505: RFS: dhcpoptinj/0.4.4-1 [ITP])
> I have not tested the functionality, but the packaging seems sound. > > In NEW. Thanks a lot for having a look! Out of curiosity, why did you upload one of the older revisions uploaded to https://mentors.debian.net/package/dhcpoptinj and not the newest, in which I have fixed a few issues, like outdated standards version and debian-compat, and updated the VCS URIs? If you are considering uploading another version, would you mind if I package 0.5.0 first? Thanks again for taking the time to help me. Best regards, -- Andreas Misje
Bug#923605: ITP: dhcpoptinj -- DHCP option injector
Jonathan, If you did take a look or still intend to take a look, here are the chances I've made since the initial upload: - Move the project to https://salsa.debian.org/misje-guest/dhcpoptinj (I'm loving the simple pipeline setup!). - Add a autopktest that ensures that "dhcpoptinj --version" outputs upstream version matching package version. - Change Standards-Version to 4.3.0 and debhelper-compat to 12. - Remove the incorrect multi arch lines from control. - Make the Vcs-Git URI canonical. Best regards -- Andreas Misje
Bug#923605: ITP: dhcpoptinj -- DHCP option injector
> Yes, you'll have to convert it to a non-native package. I gave that a try. I've tried following all guidelines, so if I've done something the wrong way I'll get around to fix whatever issues as soon as possible. I'd like to do packaging as correct as possible so that I can contribute to other projects. I've ignored the Lintian info output. I can bump the standards and debhelper versions if need be, but my impression is that this is not necessary. Whether I should bother with a testsuite I honestly don't know. > And yes, you can host your upstream project on salsa, if you don't have > a guest account yet, you can register one at: > https://signup.salsa.debian.org/ Cheers! I thought guest accounts did not have permission to add projects. If you'd like me to move dhcpoptinj-deb to salsa (and subsequently update the package with new vcs-git URIs) I'll do that. By the way, if I do this, or any other change to the package, do I create another package revision or just force-upload 0.4.4-1, since this is a new, unuploaded package anyway?
Bug#925505: RFS: dhcpoptinj/0.4.4-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "dhcpoptinj" Package name: dhcpoptinj Version : 0.4.4-1 Upstream Author : Andreas Misje URL : https://github.com/misje/dhcpoptinj License : GPL-3 Section : net It builds those binary packages: dhcpoptinj - DHCP option injector To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dhcpoptinj Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dhcpoptinj/dhcpoptinj_0.4.4-1.dsc More information about dhcpoptinj can be obtained from https://github.com/misje/dhcpoptinj Changes since the last upload: Initial release. Closes: #923605 Best regards -- Andreas Misje
Bug#923605: ITP: dhcpoptinj -- DHCP option injector
Package: dhcpoptinj Severity: wishlist Owner: Andreas Misje * Package name: dhcpoptinj Version : 0.4.2 Upstream author : Andreas Misje * URL : https://github.com/misje/dhcpoptinj * Licence : GPL-3.0 * Description : a simple utility for injecting DHCP options into DHCP packets I would like to package a project I have developed. It can be found at https://github.com/misje/dhcpoptinj. The licence is GPL-3.0, but I am open to change the licence to another permissive licence if need be. The source already contains all files needed to produce a package with bash completion and a man page, with no resulting Lintian errors. However, I am sure it needs to be converted to non-native format. I'll do that once I get a little bit of guidance on how to. My initial question is where to put the Debian files. In a repo of its own? If so, where should such a repository live? On salsa.debian.org? Best regards, -- Andreas Misje
