[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#883628: ITP: ioport -- direct access to I/O ports from the command line

On Fri, 5 Jan 2018 12:16:10 +0100 Tobias Frost <tobi@debian.org> wrote:
> On Fri, Jan 05, 2018 at 11:44:55AM +0100, Lubomir Rintel wrote:
> > On Fri, 05 Jan 2018 11:20:02 +0100 Lubomir Rintel <lkundrak@v3.sk>
> > wrote:
> > It's not clear to me what distribution to include in the changelog
> > ("sid", "unstable", "testing" or something else?)
> Use unstable.


> > Should I be bumping the package version number for each udpate? Should
> > I be adding a new changelog entry for each? Even if not
> > uploaded/released?
> You keep the Debian revision the same until it is sponsored.

That's what I initially meant to do, but mentors.debian.org won't let
me upload a changed package with the same version number.

I suppose I perhaps should've used 1~x version numbers until the
package passes a review, but it doesn't seem to be something I could do
anything about anymore.

> For the 1st upload, you do not add entries to the changelog as well, it
> is just "Initial Packaging (Closes: #ITP-Bug-Number).
> Subsequent uploads will go more into details then, listing every change
> made to the packaging.

> I recommend to browse through the documents linked in "3. Make the package"
> in https://mentors.debian.net/intro-maintainers. They will probably help you
> a lot to get into the (difficult) topic of packaging.
> I know its a lot to read, but it helps to know "where to look"; it is not
> necessary that you memorize everything to the letter, but a rough idea where
> something is explained will help. (and the knowledge will also come with
> using it anyway)

Yeah, I'm familiar with it (the link, not necessarily the content).

Still, while probably a great reference, the documentation doesn't seem
to be too good at providing best practices guidance (should the package
be versioned in a VCS? Should I pick any hosting or is it typical to
keep it on alioth/salsa? Should I always be relying on latest
debhelper? Etc.). I suppose that builds up with experience.

The updated package:



Reply to: