On 6 August 2014 06:56, Paul Wise wrote:
>
> > https://phab.enlightenment.org/T1489
>
> Why is that bug locked/private?
>
I do believe you might actually need a phab account to see it.
http://i.imgur.com/7NcKL7r.jpg here's a screenshot instead
>
>
> The best thing you can do for now is just ap
>If you could get upstream to delete src/bin/lz4 from their VCS and
>tarballs that would be good too.
https://phab.enlightenment.org/T1489
The two main comments were "Could you work on the patch to use the lib if
the lib is found. This would require debian to provide a lz4.pc (and give
it to upst
Hi Pabs,
On 5 August 2014 06:02, Paul Wise wrote:
>
> The attached files (completely untested) should do something like that
> and fix other issues.
Yup, the use-lz4.patch was great, i merged your rules/control with mine
(that i'd created from your previous mail) and everything appears to be
f
Hi pabs,
On 1 August 2014 05:36, Paul Wise wrote:
>
> Add liblz4-dev to the Build-Depends. In addition you will need to patch
> src/bin/Makefile.am and src/bin/termptysave.c so that the system version
> is used. Since you are patching the autotools build system you will need
> to replace autotoo
>
> >(you must put a 'c' before 'git' in '/git/')
> done
>
> >So, the better place is /usr/bin.
>
done
>
> >Please, register all changes in d/changelog. I didn't see about prerm.
>
postrm and postinst, i think i've done it ok..
> >Please, explain the cause of each action. Put it first:
> >
> >
Thanks for notifying me Eriberto, i'd removed it as i was about to upload
last night and then noticed another issue.
I'm going to look into it again later on today or tommorow, please feel
free to check i've done everything else correctly.
The current issue now revolves around the postrm and post
Hi pabs,
>
> >Also, src/bin/lz4 looks like an embedded code copy. Please ensure that
> >the package uses the system version of the lz4 library and that
> >src/bin/lz4 is removed in debian/rules build before ./configure is
> >run, so that the code copy is never used. For bonus points, convince
> >u
hey eriberto,
> >Ok. It's right. The package installs a empty directory. So, dpkg will
> >remove a empty directory only. It is valid for all packages. So,
> >remove postrm because their acts are wrong. If you want check, install
> >a package, add an extra file in a directory and try to purge thi
I've deleted the others and reuploaded as 0.6.1-1 . I think i've fixed
everything you listed. Upstream have been pointed at this bug to address
the ganeet issue. They should be emailing some info soon.
-- Forwarded message --
From: mentors.debian.net
Date: 31 July 2014 16:38
Subje
Hi Eriberto,
Thank you for taking the time to look over the package.
1 to 5 done. Do you want me to upload a 2.8.2+dfsg-2 with my changes for
review?
EDIT: dpkg: warning: while removing sandboxgamemaker, directory
'/usr/share/sandboxgamemaker' not empty so not removed
After removing postrm i got
Hi Nicolas
The eet file source issues, i ran a 'find' and couldn't see the files your
talking about, could you name one or two explicitly for me?
When i mentioned them, the terminology devs seemed to think they were
config files. (enlightenment has a thing about putting text into 'machine
code' f
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "sandboxgamemaker"
* Package name: sandboxgamemaker
Version : 2.8.2+dfsg-1
Upstream Author : Platinum Arts, LLC
* URL : www.sandboxgamemaker.com
* License
from
https://www.enlightenment.org/p.php?p=about/terminology
Changes since the last upload:
* Initial release (Closes: #718031)
Regards,
Anthony F McInerney
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
F
13 matches
Mail list logo
