Re: how to get a new version of 'unrar' into the official repository?
Max wrote: On 2/13/06, Mark Nipper [EMAIL PROTECTED] wrote: Well as Hamish stated, the license may not permit the AMD64 people to distribute the package. What's wrong with the license? What makes AMD64 people different from i386 people? The current solution is to include deb-src lines for Debian non-free from official Debian mirrors and build the package yourself. Why not simply to include the source package in the debian-amd64 repository? Is it againt the or what? From my experience, package maintainers are willing to work with bug reports for AMD64 when talking about actual bugs in the packages. This will at least allow you to continue to grab packages via 'apt-get source' and build them locally. But missing package is a bug, isn't it? If not, then where to complain about such problems? Max Some packages in non-free are licensed only to the Debian project - which currently doesn't include AMD64. Hence the limited subset of non-free - all licenses were checked by hand, and only those available for distribution by non-Debian people (the AMD64 team) went in. There's no non-free autobuilder to prevent accidental inclusion of unlicensed software. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
how to get a new version of 'unrar' into the official repository?
There is a new version of 'unrar' available for all platforms but AMD64. The source package can be obtained from http://debian.dev.sourceguru.net/unrar-nonfree It compile and run smootly on debian-amd64. But how to get it into the official repository? My bugreport #335824 was closed because AMD64 is not an official port and the bug is fixed for all other support platforms. Max
Re: how to get a new version of 'unrar' into the official repository?
On Mon, Feb 13, 2006 at 04:06:53PM -0800, Max wrote: There is a new version of 'unrar' available for all platforms but AMD64. The source package can be obtained from http://debian.dev.sourceguru.net/unrar-nonfree It compile and run smootly on debian-amd64. But how to get it into the official repository? My bugreport #335824 was closed because AMD64 is not an official port and the bug is fixed for all other support platforms. The maintainer can't really do anything about this; it's up to the AMD64 porters. There's no automatic building for non-free, because licenses may not permit it etc. There is no bug in the package (it DOES build on amd64, as you found out), so there's no use in reporting bugs against that package. I think the maintainer closed it for the wrong reason, but they are still correct to close it. Cheers, Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to get a new version of 'unrar' into the official repository?
On 2/13/06, Hamish Moffatt [EMAIL PROTECTED] wrote: The maintainer can't really do anything about this; it's up to the AMD64 porters. There's no automatic building for non-free, because licenses may not permit it etc. OK, then how to draw attention of AMD64 porters to this problem? I thought the bugreport would do that, but it did not. Max
Re: how to get a new version of 'unrar' into the official repository?
On 13 Feb 2006, Max wrote: On 2/13/06, Hamish Moffatt [EMAIL PROTECTED] wrote: The maintainer can't really do anything about this; it's up to the AMD64 porters. There's no automatic building for non-free, because licenses may not permit it etc. OK, then how to draw attention of AMD64 porters to this problem? I thought the bugreport would do that, but it did not. Well as Hamish stated, the license may not permit the AMD64 people to distribute the package. The current solution is to include deb-src lines for Debian non-free from official Debian mirrors and build the package yourself. From my experience, package maintainers are willing to work with bug reports for AMD64 when talking about actual bugs in the packages. This will at least allow you to continue to grab packages via 'apt-get source' and build them locally. The long term solution of course is for some folks to help out with the unrar-free package and get it working on 64-bit platforms (and support RAR version 3 ultimately). Please note that I am in no way affiliated with the AMD64 project or Debian itself (although I do provide mirrors for both). If at some point AMD64 officially is included under the Debian umbrella, it might become possible to distribute non-free also. But I'm sure some Debian purists would like to purge the entire non-free branch in general, and I can't say I disagree too much with them. However, being entirely practical for a moment, I too have built the AMD64 version of unrar-nonfree for myself via 'apt-get source ...; fakeroot dpkg-buildpackage' because people are still distributing RAR's and I still need to unpack them. :) It's not a perfect world unfortunately. -- Mark Nippere-contacts: 832 Tanglewood Drive[EMAIL PROTECTED] Bryan, Texas 77802-4013 http://nipsy.bitgnome.net/ (979)575-3193 AIM/Yahoo: texasnipsy ICQ: 66971617 -BEGIN GEEK CODE BLOCK- Version: 3.1 GG/IT d- s++:+ a- C++$ UBL$ P---+++ L+++$ !E--- W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--) Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**) --END GEEK CODE BLOCK-- ---begin random quote of the moment--- The ships hung in the sky in much the same way that bricks don't. -- Douglas Adams end random quote of the moment -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to get a new version of 'unrar' into the official repository?
On Mon, Feb 13, 2006 at 10:25:13PM -0800, Max wrote: OK, then how to draw attention of AMD64 porters to this problem? I thought the bugreport would do that, but it did not. No, the porters won't be searching all the bug reports in case of amd64-specific issues. I'd say posting to this list was the best way. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
