On Wed, Oct 01, 2014 at 02:20:17PM -0300, Eriberto wrote:
Do you removed V=1 from d/rules? Why?
Please, review my last mail saying about blhc and test the command to
you understand the issue. Try to learn, not execute a command only.
Sorry about that, I just used to use DH_VERBOSE=1 to
2014-10-03 9:28 GMT-03:00 ChangZhuo Chen (陳昌倬) czc...@gmail.com:
Why you did a lintian override to amd64 only?
The path contains multiarch tuple, so it only works on amd64. I tried to
build i386 package via pbuilder, and there is no tEH in library. So I
think it only happens in amd64.
My
New situation: we already have a new Lintian (since yesterday).
Please, update the Standards-Version to 3.9.6.
Cheers,
Eriberto
2014-10-03 9:36 GMT-03:00 Eriberto eribe...@eriberto.pro.br:
2014-10-03 9:28 GMT-03:00 ChangZhuo Chen (陳昌倬) czc...@gmail.com:
Why you did a lintian override to
On Fri, Oct 03, 2014 at 09:38:15AM -0300, Eriberto wrote:
New situation: we already have a new Lintian (since yesterday).
Please, update the Standards-Version to 3.9.6.
Just update the Standards-Version to 3.9.6. Looks like nothing need to
change for 3.9.5 ~ 3.9.6. The package is in mentor [0],
Uploaded.
Thanks for your work.
Cheers,
Eriberto
2014-10-03 11:31 GMT-03:00 ChangZhuo Chen (陳昌倬) czc...@gmail.com:
On Fri, Oct 03, 2014 at 09:38:15AM -0300, Eriberto wrote:
New situation: we already have a new Lintian (since yesterday).
Please, update the Standards-Version to 3.9.6.
Just
2014-10-01 1:38 GMT-03:00 ChangZhuo Chen (陳昌倬) czc...@gmail.com:
Hi!
Do you use the tarball from github? The tarball from github does not
contain data file used by libzhuyin, so upstream suggested using tarball
from sourceforge [1].
Yes, I used the GitHub because your d/copyright, in Source
Hi,
Just upload a new version in mentor [0] with the following update:
- Fix debhelper version to = 9
- Add lintian-overrides for force positive spelling-error-in-binary
- Use hardening=+all
- Update Source field in d/copyright to sourceforge
- Add github release to d/watch
Please help to
Do you removed V=1 from d/rules? Why?
Please, review my last mail saying about blhc and test the command to
you understand the issue. Try to learn, not execute a command only.
Why you did a lintian override to amd64 only?
2014-10-01 12:53 GMT-03:00 ChangZhuo Chen czc...@gmail.com:
Hi,
Just
On Thu, Aug 28, 2014 at 08:35:35AM -0300, Eriberto wrote:
Hi ChangZhuo,
Good news. I will wait for you. You're welcome.
Upstream released a new version 0.9.99.20140929, and it does not install
binary tools and its manpage. So we don't need to decide whether
including binary tools or not
Hi ChangZhuo,
1. I found several differences between your orig.tar.gz and the
tarball in upstream site. I used the diff command to compare. Can you
check this?
2. d/control: please, change the DH level from 9.0.0 to 9.
3. d/copyright: there are new authors and dates in new upstream code.
You
On Tue, Sep 30, 2014 at 02:51:05PM -0300, Eriberto wrote:
Hi ChangZhuo,
1. I found several differences between your orig.tar.gz and the
tarball in upstream site. I used the diff command to compare. Can you
check this?
The tarball is from sourceforge [0] with the following SHA256.
-
On Tue, Aug 26, 2014 at 10:01:39AM -0300, Eriberto wrote:
Ok. My suggestion:
1. Put all files in /usr/share/libzhuyin-utils. I think that
zhuyin-utils is better for package name. But it is my opinion. Not
relevant.
2. Make symlinks in /usr/bin and /usr/share/man. Example:
Hi ChangZhuo,
Good news. I will wait for you. You're welcome.
Cheers,
Eriberto
2014-08-28 8:02 GMT-03:00 ChangZhuo Chen (陳昌倬) czc...@gmail.com:
Hi Eriberto,
Currently upstream is working on this issue [0] now, so I just want to
wait a week or so to let upstream fix the name collision
Yesterday I made a mistake.
2014-08-26 10:01 GMT-03:00 Eriberto eribe...@eriberto.pro.br:
2. Make symlinks in /usr/bin and /usr/share/man. Example:
zhuyin_gen_binary_files.
No... In this case, you will need change the command name inside the
manpage. Sorry for my mistake.
Cheers,
Eriberto
Ok. My suggestion:
1. Put all files in /usr/share/libzhuyin-utils. I think that
zhuyin-utils is better for package name. But it is my opinion. Not
relevant.
2. Make symlinks in /usr/bin and /usr/share/man. Example:
zhuyin_gen_binary_files.
Or don't distribute the binaries. I prefer the first
On Sun, Aug 24, 2014 at 10:39:04AM -0300, Eriberto Mota wrote:
1. You didn't install the binaries and manpages. Why?
The binary and manpages are for tools to build binary data from
dictionary data. It is only useful for developer of libzhuyin. For the
developers who want to use libzhuyin to
2014-08-25 10:20 GMT-03:00 ChangZhuo Chen (陳昌倬) czc...@gmail.com:
On Sun, Aug 24, 2014 at 10:39:04AM -0300, Eriberto Mota wrote:
1. You didn't install the binaries and manpages. Why?
The binary and manpages are for tools to build binary data from
dictionary data. It is only useful for
On Mon, Aug 25, 2014 at 11:14:03AM -0300, Eriberto wrote:
I understood your POV. However, note that is an available resource
that you are hiding. When adapting the code to particular needs, a
final user will want these binaries. So, why don't distribute it? You
can write your POV in long
On Sat, Aug 23, 2014 at 09:09:17PM -0300, Eriberto Mota wrote:
Hi ChangZhuo,
The new upstream version has new dates. So, you must update the
d/copyright file. Your sintax is wrong, because you put the upstreams
names before the years. Another point is that the packaging copyright,
usually,
Hi ChangZhuo.
Sorry, but in my last check I found two issues:
1. You didn't install the binaries and manpages. Why?
2. The installer is creating the directory
usr/include/libzhuyin-0.9.99.[CURRENT DATE]. Example:
usr/include/libzhuyin-0.9.99.20140824. Please, solve this issue. Feel
free to ask
Hi ChangZhuo,
The new upstream version has new dates. So, you must update the
d/copyright file. Your sintax is wrong, because you put the upstreams
names before the years. Another point is that the packaging copyright,
usually, is an maintainer name. I suggest this sintax:
Files: *
Copyright:
tags 745721 moreinfo
thanks
Hi ChangZhuo.
Please:
1. d/control:
- What is '...' in long descriptions?
- I didn't understand what is the '-data' package. What is this?
Can you improve the long description?
2. d/copyright:
- I didn't find Peng Huang and BYVoid in upstream code.
Hi,
Since upstream has new version 0.9.99.20140718, I will pack this new
version, with the following fix.
1. d/control:
- What is '...' in long descriptions?
It means etc, and so on. I will change to use etc if ... causes
confused.
- I didn't understand what is the '-data'
On Thu, Apr 24, 2014 at 11:10:56PM +0800, Kan-Ru Chen wrote:
Thanks for packaging this library! I'm reviewing this package.
Upstream has new version 0.9.99.20140425, so I just repack it with
latest version.
ChangZhuo Chen (陳昌倬) czc...@gmail.com writes:
Package: sponsorship-requests
Severity: wishlist
Hi All,
I am looking for a sponsor for libzhuyin:
* Package name: libzhuyin
Version : 0.9.93
Upstream Author : Peng Wu alexep...@gmail.com
* URL :
25 matches
Mail list logo
