Bug#699669: RFS: agar/1.4.1+repack1-1 [ITP] -- toolkit for graphical applications
On Wed, Feb 6, 2013 at 2:48 PM, Mathieu Malaterre <malat@debian.org> wrote:
> On Tue, Feb 5, 2013 at 4:22 AM, Stephen M. Webb
> <stephen.webb@bregmasoft.ca> wrote:
>> This was because a pre-built Windows binary was included in the upstream source tarball. The complete source for the
>> binary is included. After some discussion, the executable is now being left in and the pristine tarball is being
>> included. I change the package version accordingly and re-uploaded to m.d.n.
>
> Looks good now:
>
> $ dget -u http://mentors.debian.net/debian/pool/main/a/agar/agar_1.4.1-1.dsc
>
>> The package builds as-is in a current sid pbuilder environment. Those symbols are only built when the package
>> configuration can successfully detect the presence of working GLX headers. It would be useful to check the config.log
>> to identify the reason why this was unsuccessful for you.
>
> I cannot reproduce this from another computer. We'll leave this as-is.
>
>
> New comments:
>
> 1.
> Please do not use version for png-dev and jpeg-dev package. This helps
> in preventing source upload everytime package -dev gets updated.
>
> 2.
> There is an issue with the d/copyright, some file are not listed:
>
> $ head ./vg/vg_line.h
> /* Public domain */
>
> but d/copyright indicate only BSD...
>
>
> 3. Currently Std-Vers is 3.9.4
4. I believe there is an issue:
$ dpkg -c libag-vg4_1.4.1-1_amd64.deb
[...]
lrwxrwxrwx root/root 0 2013-02-06 14:42
./usr/lib/libag_vg.so.4 -> libag_vg.so.4.0.0
Looks like there is an issue with multiarch path installation. shared
lib should not be in usr/lib, but usr/lib/x86_64-linux-gnu (at least
on my machine).
Thanks,
Reply to: