Re: RFS: setop/0.1-1 [ITP]
Hello,
Am 20.04.2016 um 23:16 schrieb Gianfranco Costamagna:
Is it this one?
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813485>
I exactly followed all instructions from
<http://mentors.debian.net/sponsor/rfs-howto> and/or
<https://wiki.debian.org/Mentors/BTS> and still don’t know, where my
mistake was.
not sure, I don't know why a new bug hasn't been opened.
BTW there should be two bugs, not a single one, and there are automatic
scripts that correlates them by blocking the ITP by the RFS one.
can you please try again?
I resent the RFS mail to submit@bugs.debian.org. This time the subject
was simply "RFS: setop/0.1-1 [ITP]" instead of "Bug#813485: RFS:
setop/0.1-1 [ITP]". Perhaps that was the problem.
Omitting -O3 yields in making a debug version (equal to -O0) on my
system. By default, the make file shall produce a release build, and by
testing I found out that O2 and O3 are best compared to the alternatives
(e. g. Os).
Ok?
no.
man dh_strip
(snip)
you have to produce debug builds with -g and so on.
As you said in another mail, no action is needed here.
I deleted the dependence libboost-dev as suggested, ALTHOUGH I am not
sure if that is correct.
The documentation just says “This package provides headers.” Besides
regex and program-options I indeed need some other headers and now I
don’t know if these are installed for sure.
I don’t understand what you mean by that.
BIN=foo means nobody can change that
BIN?=foo means "assign foo if nothing else is already defined"
[…]
Same for HELP
and LIBS
HELP, BIN, and LIBS changed as suggested.
public domain
it was fine
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
just be sure to mention it correctly on the copyright file
https://codesearch.debian.net/results/License%3A%20unlicense/page_0
Changed the text according to the examples.
You should check it. It’s taken from <https://wiki.debian.org/debian
/watch#GitHub>, but mentors.debian.net says it doesn’t work.
uscan --debug doesn't work too.
Probably you have to git tag v0.1 and git push --tags?
it is failing to parse the html, not having releases there might be the reason.
You were right: not having any releases yields in an error. I created
one for testing, and everything is ok now.
Best,
Frank
Reply to: