Re: [arch-general] [arch-dev-public] [signoff] patch-2.6
On Thu, 26 Nov 2009 00:42:33 -0500 Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Wed, Nov 25, 2009 at 11:12 PM, Allan McRae <allan@archlinux.org> wrote:
Allan McRae wrote:
Ionut Biru wrote:
On 11/20/2009 07:24 AM, Allan McRae wrote:
Upstream update. Signoff both.
signoff x86_64
Anyone for i686?
Anyone?
signoff i686
Does this [1] affect arch? I guess it does for users building from aur or abs, but I'm not really familiar with most build-environments. [1] http://blog.flameeyes.eu/2009/12/01/gentoo-service-announcement-keep-clear-o... --
On Tue, Dec 1, 2009 at 3:44 PM, Alexander Duscheleit <jinks@huntemann.uni-oldenburg.de> wrote:
Does this [1] affect arch? I guess it does for users building from aur or abs, but I'm not really familiar with most build-environments.
[1] http://blog.flameeyes.eu/2009/12/01/gentoo-service-announcement-keep-clear-o...
I don't see what differences it makes, whether you use aur or abs or not. It has nothing to do with the build environment. makepkg will use whatever patch command you specified in the PKGBUILD. That said, the above problem seems to be related to using -F3. I had never seen that option anywhere before, I had no idea what it was. Actually I am still a bit confused now even after reading the man page :) Some quick scanning over abs tree did not reveal anything : find /var/abs/ -name PKGBUILD | xargs grep "fuzzy" find /var/abs/ -name PKGBUILD | xargs grep " -F" find /var/abs/ -name PKGBUILD | xargs grep "patch.* -[^ ]*F" So I would guess we do not care, but I might be missing something. Or maybe the problem does not even only exist with -F3. The description of the problem in the above link is awfully poor.
On Wed, Dec 2, 2009 at 1:40 AM, Xavier <shiningxc@gmail.com> wrote:
On Tue, Dec 1, 2009 at 3:44 PM, Alexander Duscheleit <jinks@huntemann.uni-oldenburg.de> wrote:
Does this [1] affect arch? I guess it does for users building from aur or abs, but I'm not really familiar with most build-environments.
[1]
http://blog.flameeyes.eu/2009/12/01/gentoo-service-announcement-keep-clear-o...
I don't see what differences it makes, whether you use aur or abs or not. It has nothing to do with the build environment. makepkg will use whatever patch command you specified in the PKGBUILD.
That said, the above problem seems to be related to using -F3. I had never seen that option anywhere before, I had no idea what it was. Actually I am still a bit confused now even after reading the man page :)
Some quick scanning over abs tree did not reveal anything : find /var/abs/ -name PKGBUILD | xargs grep "fuzzy" find /var/abs/ -name PKGBUILD | xargs grep " -F" find /var/abs/ -name PKGBUILD | xargs grep "patch.* -[^ ]*F"
So I would guess we do not care, but I might be missing something. Or maybe the problem does not even only exist with -F3. The description of the problem in the above link is awfully poor.
The gentoo bugtracker describe issues using patch with fuzz factor. Refer to the link below. http://bugs.gentoo.org/show_bug.cgi?id=293570
participants (3)
-
Abdul Halim
-
Alexander Duscheleit
-
Xavier