On Mon, Jun 16, 2008 at 08:36:55PM +0100, Martin Meredith wrote:
Hi there.
I currently maintain rar and unrar-nonfree in debian.
When uscanning for the latest version of rar - it started to download
the x64 version, which I haven't seen before.
Anyway - It seems that upstream are now
On Tue, 2008-06-17 at 11:13 +0800, Paul Wise wrote:
On Tue, Jun 17, 2008 at 3:36 AM, Martin Meredith [EMAIL PROTECTED] wrote:
Any thoughts?
Not sure if dak/buildds can handle this, but what about multiple
source packages?
Something like unrar-nonfree-64 producing rar binary package
On Mon, Jun 16, 2008 at 08:36:55PM +0100, Martin Meredith wrote:
I'm also pretty sure that the licence doesn't let me do a
tarball-in-tarball thing (orig.tar.gz has to stay the same)
I think you mean the following:
| b. The RAR/WinRAR unregistered trial version may not be distributed
|
On Tue, Jun 17, 2008 at 08:12:29AM +0100, Martin Meredith wrote:
Buildd's wouldn't have anything to do with it anyway, as it's not
auto-built.
I found this in the copyright file of the rar package:
| This package is Auto-Buildable
Also the control file say the same. Please explain.
Bastian
On 2008-06-17 09:12:29.00 Martin Meredith [EMAIL PROTECTED] wrote:
Would an ftp-master be able to answer whether thats possible?
(having 2 different source packages provide debs for the same
source package, but different architectures)
No, this does not work.
Also, the proper fix (sort of
Hi there.
I currently maintain rar and unrar-nonfree in debian.
When uscanning for the latest version of rar - it started to download
the x64 version, which I haven't seen before.
Anyway - It seems that upstream are now packaging a i386 binary, and an
x64 binary.
I'm not too sure how I should
6 matches
Mail list logo
