FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 11-20-2009, 04:24 AM
"Allan McRae"
 
Default patch-2.6

Upstream update. Signoff both.


Changes in version 2.6:

* A regression test suite has been added ("make check").
* A --merge option has been added which will merge a patch file into
the original files similar to merge(1). See the patch(1) manual page for
documentation.
* Unless a filename has been specified on the command line, look only
for filenames in the patch until one has been found. This prevents
patch from tripping over garbage that isn't a patch. When conforming
to POSIX, this behavior is turned off and patch will ask for a
filename if none is found.
* All reject files have file name headers, which allows them to be used as
regular patches.
* When a patch file modifies the same file more than once, patch makes
sure it backs up the original version of the file rather than any
intermediary versions.
* In the above situation, if there are rejects in more than one of those
patches, they all go into the same reject file.
* When the file to be patched is specified on the command line, all patches
are applied to that file. (Previously, the first patch was applied to the
file specified on the command line, and the names of additional files to
patch were taken from header lines in the patch file.)
* The -r option now works correctly even if there are rejects in more than
one file. Use the - argument to discard rejects.
* Rejected hunks come out in unified diff format if the input patch was of
that format, otherwise in ordinary context diff form. Use the
--reject-format option to enforce either "context" or "unified" format.
Timestamps and the "diff -p" (--show-c-function) output are preserved.
Changed lines in context format reject files are correctly indicated
with '!' markers as the format defines. Added and removed lines are
still marked with '+' and '-', respectively.
* The file permissions of reject files are no longer set to match the files
they modify. Instead, they retain the default permissions. This is
consistent with reject files produced with the -r option.
* The --binary option disables the heuristic for stripping CRs from
line endings in patches. This allows to preserve CRs even in mangled
patches, or in patches generated on non-POSIX systems and without the
--binary option.
* Backup files for nonexisting files are now created with default
permissions rather than with mode 0: backup files with mode 0 were
causing problems with applications which do not expect unreadable
files.
* The -B, -Y, and -z options (--prefix, --basename-prefix, --suffix) now
imply the simple version control mode, and can be combined.
* Patch rejects more malformed normal format commands and checks for
trailing

garbage. It now recognizes ed commands without addresses.
* Change the default value of PATCH_GET to 0. (Previously, the default
was 0

under POSIXLY_CORRECT and negative otherwise; this is causing problems
particularly with Perforce.)
* Handle missing timestamps better.
* Various bug fixes.
 
Old 11-22-2009, 04:43 PM
Ionut Biru
 
Default patch-2.6

On 11/20/2009 07:24 AM, Allan McRae wrote:

Upstream update. Signoff both.


Changes in version 2.6:

* A regression test suite has been added ("make check").
* A --merge option has been added which will merge a patch file into
the original files similar to merge(1). See the patch(1) manual page for
documentation.
* Unless a filename has been specified on the command line, look only
for filenames in the patch until one has been found. This prevents
patch from tripping over garbage that isn't a patch. When conforming
to POSIX, this behavior is turned off and patch will ask for a
filename if none is found.
* All reject files have file name headers, which allows them to be used as
regular patches.
* When a patch file modifies the same file more than once, patch makes
sure it backs up the original version of the file rather than any
intermediary versions.
* In the above situation, if there are rejects in more than one of those
patches, they all go into the same reject file.
* When the file to be patched is specified on the command line, all patches
are applied to that file. (Previously, the first patch was applied to the
file specified on the command line, and the names of additional files to
patch were taken from header lines in the patch file.)
* The -r option now works correctly even if there are rejects in more than
one file. Use the - argument to discard rejects.
* Rejected hunks come out in unified diff format if the input patch was of
that format, otherwise in ordinary context diff form. Use the
--reject-format option to enforce either "context" or "unified" format.
Timestamps and the "diff -p" (--show-c-function) output are preserved.
Changed lines in context format reject files are correctly indicated
with '!' markers as the format defines. Added and removed lines are
still marked with '+' and '-', respectively.
* The file permissions of reject files are no longer set to match the files
they modify. Instead, they retain the default permissions. This is
consistent with reject files produced with the -r option.
* The --binary option disables the heuristic for stripping CRs from
line endings in patches. This allows to preserve CRs even in mangled
patches, or in patches generated on non-POSIX systems and without the
--binary option.
* Backup files for nonexisting files are now created with default
permissions rather than with mode 0: backup files with mode 0 were
causing problems with applications which do not expect unreadable
files.
* The -B, -Y, and -z options (--prefix, --basename-prefix, --suffix) now
imply the simple version control mode, and can be combined.
* Patch rejects more malformed normal format commands and checks for
trailing
garbage. It now recognizes ed commands without addresses.
* Change the default value of PATCH_GET to 0. (Previously, the default
was 0
under POSIXLY_CORRECT and negative otherwise; this is causing problems
particularly with Perforce.)
* Handle missing timestamps better.
* Various bug fixes.



signoff x86_64

--
Ionut
 
Old 11-24-2009, 03:08 AM
"Allan McRae"
 
Default patch-2.6

Ionut Biru wrote:

On 11/20/2009 07:24 AM, Allan McRae wrote:

Upstream update. Signoff both.



signoff x86_64



Anyone for i686?
 
Old 11-26-2009, 03:12 AM
"Allan McRae"
 
Default patch-2.6

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?
 
Old 11-26-2009, 04:42 AM
Eric Bélanger
 
Default patch-2.6

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
 
Old 12-01-2009, 01:44 PM
Alexander Duscheleit
 
Default 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-of-gnu-patch-2-6

--
 
Old 12-01-2009, 04:40 PM
Xavier
 
Default patch-2.6

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-of-gnu-patch-2-6
>

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.
 
Old 12-02-2009, 12:02 AM
Abdul Halim
 
Default patch-2.6

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-of-gnu-patch-2-6
> >
>
> 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
 

Thread Tools




All times are GMT. The time now is 07:09 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org