Bug#799205: RFS: eviacam/2.0.1-5 [ITP] -- webcam based mouse emulator
Hi everyone,
I think Cesar has fixed almost all lintian warnings except the "too
much arch independent data" warning, including the "keyword" keyword
funny issue mentioned by Gianfranco. However, I see mainly 2 problems.
First, if I try to build using debuild, I get the error
`dh_autoreconf: autoreconf -f -i returned exit code 1'. I think it is
because dh_autoreconf is running "naked" `autoreconf' instead of
`autogen.sh'. So I think the fix is to add the following entry into
debian/rule:
override dh_autoreconf:
dh_autoreconf ./autogen.sh
Besides, if I try to re-build I get `dpkg-source: error:
unrepresentable changes to source'. Now I don't really know how to fix
since I don't know how translation works. Maybe Gianfranco could help?
Cheers,
Alex
On 10/10/2015, Cesar Mauri <cesar@crea-si.com> wrote:
> Hi
>
> Thanks for your feedback.
>
>>> The point of that commit was to add the debugging flags to the
>>> compiler command line.
>>>
>>> if ! "$debug"; then
>>> - COMPFLAGS="$COMPFLAGS -DNDEBUG"
>>> + COMPFLAGS="$COMPFLAGS -DNDEBUG -O2"
>>> +else
>>> + COMPFLAGS="$COMPFLAGS -DDEBUG -g -O0"
>>> fi
>> yes, but I fail to see why you should override CPPFLAGS anyway :)
> I recently changed CPPFLAGS to CXXFLAGS which I think is more appropriate
> (preprocessor flags vs. compiler flags). But frankly, I never fully mastered
> automake and friends so, not sure if it can be still improved.
>
>
>> you can publish the tarball as always, just sign it in a tarball.gpg or
>> whatever
>> detached file.
>> how upstream builds the archive is not a Debian problem :)
>> I mean, use your favourite way, just don't change it too often to avoid
>> debian/watch file broken
> Now d/watch look like this:
>
> version=3
> opts=pgpsigurlmangle=s/$/.asc/
> http://sf.net/eviacam/eviacam_(.+)\.orig\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
> debian uupdate
>
> and
>
> uscan --debug --force-download
> dpkg-buildpackage -S -sa
>
> works for me
>
>>> I understand that a dbg package is "...useful if program crashes and you
>>> want to generate stack trace..." [1]. But not sure who might take
>>> advantage
>>> if this kind of package. I think that I need more information about
>>> this.
>> well, consider a person giving you a bug like
>>
>> "the version X.Y crashes"
>>
>> you might want them to install the dbg package and give you a stack trace
>> with
>> some useful pointers inside.
>>
>> but automatic debug packages are coming soon (TM) in Debian, so you can
>> just avoid it
>> (although it is a nice learning experience)
> I see. Perhaps we could wait for the automatic debug packages. In the
> meantime, if someone reports a crash, I could try to provide a debug
> package.
>
>
>> (sorry for the delay, let me know as soon as you have something on
>> mentors, I guess this involves
>> a new upstream minor release or a bunch of debian/patches)
> Me too. I have been busy lately.
>
> I've uploaded a new version (2.0.3) to mentors.
>
>
> Regards, Cesar
>
>
Reply to: