Re: Comments regarding relaxngcc_1.12-1_amd64.changes

2014-02-26 Thread Timo Aaltonen
On 19.02.2014 00:57, Timo Aaltonen wrote: On 18.02.2014 23:35, Florian Weimer wrote: * Timo Aaltonen: We have a bootstrapping issue with this.. upstream CVS repo ships with 'lib/bootstrap-relaxngcc.jar' which is used to generate the files for the parser. And since the source tarball can't

Re: Comments regarding relaxngcc_1.12-1_amd64.changes

2014-02-18 Thread Timo Aaltonen
On 28.01.2014 15:24, Gergely Nagy wrote: On Wed, Jan 22, 2014 at 3:17 PM, Timo Aaltonen tjaal...@ubuntu.com wrote: On 22.01.2014 15:56, Timo Aaltonen wrote: On 22.01.2014 15:21, Timo Aaltonen wrote: On 21.01.2014 14:44, Gergely Nagy wrote: - There are a couple of files in the source that

Re: Comments regarding relaxngcc_1.12-1_amd64.changes

2014-02-18 Thread Timo Aaltonen
On 18.02.2014 23:16, Timo Aaltonen wrote: On 28.01.2014 15:24, Gergely Nagy wrote: On Wed, Jan 22, 2014 at 3:17 PM, Timo Aaltonen tjaal...@ubuntu.com wrote: On 22.01.2014 15:56, Timo Aaltonen wrote: On 22.01.2014 15:21, Timo Aaltonen wrote: On 21.01.2014 14:44, Gergely Nagy wrote: - There

Re: Comments regarding relaxngcc_1.12-1_amd64.changes

2014-02-18 Thread Florian Weimer
* Timo Aaltonen: We have a bootstrapping issue with this.. upstream CVS repo ships with 'lib/bootstrap-relaxngcc.jar' which is used to generate the files for the parser. And since the source tarball can't include that relaxngcc has no way to enter Debian? Fedora doesn't seem to care, they

Re: Comments regarding relaxngcc_1.12-1_amd64.changes

2014-02-18 Thread Timo Aaltonen
On 18.02.2014 23:35, Florian Weimer wrote: * Timo Aaltonen: We have a bootstrapping issue with this.. upstream CVS repo ships with 'lib/bootstrap-relaxngcc.jar' which is used to generate the files for the parser. And since the source tarball can't include that relaxngcc has no way to enter

Re: Comments regarding relaxngcc_1.12-1_amd64.changes

2014-01-30 Thread Gergely Nagy
On Wed, Jan 22, 2014 at 3:17 PM, Timo Aaltonen tjaal...@ubuntu.com wrote: On 22.01.2014 15:56, Timo Aaltonen wrote: On 22.01.2014 15:21, Timo Aaltonen wrote: On 21.01.2014 14:44, Gergely Nagy wrote: - There are a couple of files in the source that have comments like: /* this file is

Re: Comments regarding relaxngcc_1.12-1_amd64.changes

2014-01-22 Thread Timo Aaltonen
On 21.01.2014 14:44, Gergely Nagy wrote: Dear maintainer, While processing your upload of relaxngcc 1.12-1, I noticed the following things about the packaging: - The source tarball has been repacked, but this is not documented anywhere, and the only sign of it is the get-orig-targz

Re: Comments regarding relaxngcc_1.12-1_amd64.changes

2014-01-22 Thread Timo Aaltonen
On 22.01.2014 15:21, Timo Aaltonen wrote: On 21.01.2014 14:44, Gergely Nagy wrote: - There are a couple of files in the source that have comments like: /* this file is generated by RelaxNGCC */ Are these files rebuildable? (Sadly, my Java build system knowledge is not enough to

Re: Comments regarding relaxngcc_1.12-1_amd64.changes

2014-01-22 Thread Timo Aaltonen
On 22.01.2014 15:56, Timo Aaltonen wrote: On 22.01.2014 15:21, Timo Aaltonen wrote: On 21.01.2014 14:44, Gergely Nagy wrote: - There are a couple of files in the source that have comments like: /* this file is generated by RelaxNGCC */ Are these files rebuildable? (Sadly, my Java

Comments regarding relaxngcc_1.12-1_amd64.changes

2014-01-21 Thread Gergely Nagy
Dear maintainer, While processing your upload of relaxngcc 1.12-1, I noticed the following things about the packaging: - The source tarball has been repacked, but this is not documented anywhere, and the only sign of it is the get-orig-targz target in debian/rules. Please document this in