Discussion:
Bug#738850: ITP: iniparser -- a stand-alone INI file reading/writing library
(too old to reply)
Daniel Lintott
2014-05-16 21:00:03 UTC
Permalink
Could I ask what the current situation with iniparser is?

A package I shall be preparing currently depends on iniparser.

Regards
--
Daniel Lintott
GPG Key: 4096R/5D73EC6E
Klee Dienes
2014-05-16 23:10:03 UTC
Permalink
Post by Daniel Lintott
Could I ask what the current situation with iniparser is?
You can find my packaged sources at https://github.com/kdienes/iniparser .

I think they’re ready to upload. I’m currently working my way through the N-M process, after which I will likely upload the package myself. Or if you know someone willing to sponsor the package, I’m happy to work with them sooner.

(Also, if you are interested, I’m happy to have you take over or co-maintain the package. I packaged it because it was used by psmoveapi).
Daniel Lintott
2014-05-17 19:30:02 UTC
Permalink
Thanks for the prompt reply!
Post by Klee Dienes
You can find my packaged sources at https://github.com/kdienes/iniparser .
I've taken a look at your packaging at agree it looks good. I noted a
couple of things that I've picked up since I started packaging...

debian/rules
- no need to define a .PHONY target
- build flags import and set isn't required as dh9 sets all the
required build_flags

debian/control
- section can be removed from libiniparser0 binary package

debian/watch (Attached)
- Look at GitHub tags directly (not via deprecated github redir)
- Add dversionmangle to remove date/git suffix

debian/changelog
- Most new packages use a single entry in the changelog, for the
initial packaging and closing of ITP bug
Post by Klee Dienes
I think they’re ready to upload. I’m currently working my way through
the N-M process, after which I will likely upload the package myself.
Or if you know someone willing to sponsor the package, I’m happy to
work with them sooner.
I do have a sponsor who I work with, for several packages but I can't
comment on his current workload etc. It may be worth preparing the
source and uploading to mentors.debian.org, filing an RFS bug and see if
anyone is interested.
Post by Klee Dienes
(Also, if you are interested, I’m happy to have you take over or
co-maintain the package. I packaged it because it was used by psmoveapi).
I would be reluctant to take over the package entirely as I'm not really
familiar with library packaging (other than perl modules).

Regards,
--
Daniel Lintott
GPG Key: 4096R/5D73EC6E
Klee Dienes
2014-05-17 23:50:01 UTC
Permalink
Post by Daniel Lintott
I've taken a look at your packaging at agree it looks good. I noted a
couple of things that I've picked up since I started packaging…
debian/rules
- no need to define a .PHONY target
- build flags import and set isn't required as dh9 sets all the
required build_flags
Removed the build flags stuff; thanks.

Do you have a reference regarding the .PHONY target? Are you saying that there’s a mechanism by which PHONY targets are no longer necessary? Or just that since those files aren’t present in the source directory, they’re not needed. Now that you have me thinking about this, I realize that debhelper probably has a bunch of invisitargets that are never getting captured by .PHONY. So I took the easy way and agreed with you and removed them all. There is a *lot* of documentation out there that implies that they should be present, though … I wonder if there’s a canonical source of guidance anywhere.
Post by Daniel Lintott
debian/control
- section can be removed from libiniparser0 binary package
I know it’s redundant, but it pains me to have all the other binary packages specify a Section: and not libiniparser0.
Post by Daniel Lintott
debian/watch (Attached)
- Look at GitHub tags directly (not via deprecated github redir)
- Add dversionmangle to remove date/git suffix
Thanks! I wonder if it would be possible to add a note to githubredir.debian.net explaining that it’s deprecated and giving the new syntax. I also wonder if there’s any lintian checks that already look for deprecated watch file formats.
Post by Daniel Lintott
debian/changelog
- Most new packages use a single entry in the changelog, for the
initial packaging and closing of ITP bug
That makes sense, but OTOH, I’m using these packages internally in my personal work. So as I find bugs I am bumping the version internally … it makes sense to me to keep meaningful changelog entries. Is there a reason they’re considered harmful, or is it just a matter of personal preference? I suspect you are right that I should push the “Closes: #738850” entry to the release that actually closes the ITP … I’ll do that when I go to submit.
Post by Daniel Lintott
I would be reluctant to take over the package entirely as I'm not really
familiar with library packaging (other than perl modules).
This one, thankfully, is a pretty easy one. No pressure was intended … I’m happy to maintain it. Just wanted to extend the offer.
--
To UNSUBSCRIBE, email to debian-bugs-dist-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Daniel Lintott
2014-05-18 13:50:02 UTC
Permalink
Post by Daniel Lintott
I've taken a look at your packaging at agree it looks good. I noted a
couple of things that I've picked up since I started packaging…
Thanks for the feedback! I took most of your suggestions (comments to follow)
Post by Daniel Lintott
debian/rules
- no need to define a .PHONY target
- build flags import and set isn't required as dh9 sets all the
required build_flags
Removed the build flags stuff; thanks.
Do you have a reference regarding the .PHONY target? Are you saying that there’s a mechanism by which PHONY targets are no longer necessary? Or just that since those files aren’t present in the source directory, they’re not needed. Now that you have me thinking about this, I realize that debhelper probably has a bunch of invisitargets that are never getting captured by .PHONY. So I took the easy way and agreed with you and removed them all. There is a *lot* of documentation out there that implies that they should be present, though … I wonder if there’s a canonical source of guidance anywhere.
I don't have any reference per se.. other than I've not seen it used
personally... (Doesn't mean I'm right btw) :P

Just having a look the only reference I could find was at the beginning
Post by Daniel Lintott
debian/control
- section can be removed from libiniparser0 binary package
I know it’s redundant, but it pains me to have all the other binary packages specify a Section: and not libiniparser0.
Ack... I noticed that it was flagged up by Lintian, so thought I'd
suggest it. I'm not sure what the official view is.
Post by Daniel Lintott
debian/watch (Attached)
- Look at GitHub tags directly (not via deprecated github redir)
- Add dversionmangle to remove date/git suffix
Thanks! I wonder if it would be possible to add a note to githubredir.debian.net explaining that it’s deprecated and giving the new syntax.
That may well be possible... Just looking at changelog for the
devscripts package which contains uscan it contains the following:

+ Update the GitHub example. Based on a patch by YABUKI Yukiharu.
(Closes: #728182)

in version 2.14.0 (which is present in testing)
I also wonder if there’s any lintian checks that already look for deprecated watch file formats.
It may be worth suggesting that to the Lintian developers
Post by Daniel Lintott
debian/changelog
- Most new packages use a single entry in the changelog, for the
initial packaging and closing of ITP bug
That makes sense, but OTOH, I’m using these packages internally in my personal work. So as I find bugs I am bumping the version internally … it makes sense to me to keep meaningful changelog entries. Is there a reason they’re considered harmful, or is it just a matter of personal preference? I suspect you are right that I should push the “Closes: #738850” entry to the release that actually closes the ITP … I’ll do that when I go to submit.
I don't think it's necessarily considered bad, but something I've
noticed a lot of Debian Developers require when they sponsor packages on
mentors.debian.org
Post by Daniel Lintott
I would be reluctant to take over the package entirely as I'm not really
familiar with library packaging (other than perl modules).
This one, thankfully, is a pretty easy one. No pressure was intended … I’m happy to maintain it. Just wanted to extend the offer.
No problem ;)

Regards
--
Daniel Lintott
GPG Key: 4096R/5D73EC6E
Salvatore Bonaccorso
2017-10-12 22:40:08 UTC
Permalink
Hi Klee

Is it still planned to package iniparser for Debian?

I know another small Projekt which I likely will use which depends on
iniparser, so I wonder if uploading for Debian is still planned.

Regards,
Salvatore
Salvatore Bonaccorso
2017-10-18 04:50:02 UTC
Permalink
Control: tags -1 + pending

Hi
Post by Salvatore Bonaccorso
Hi Klee
Is it still planned to package iniparser for Debian?
I know another small Projekt which I likely will use which depends on
iniparser, so I wonder if uploading for Debian is still planned.
I took over Klee's initial packaging and uploaded the package (now
sitting in NEW).

https://ftp-master.debian.org/new/iniparser_4.0-1.html

If someone of you both would prefer to maintain it please let me know!

Regards,
Salvatore

Loading...