public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] squid 3.5.20: latest patches from upstream
Date: Thu, 18 Aug 2016 18:07:04 +0200	[thread overview]
Message-ID: <35525ab4-cf59-0f60-38f0-fc54451ac459@ipfire.org> (raw)
In-Reply-To: <1470221229.2710.433.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

Hi,

On 03.08.2016 12:47, Michael Tremer wrote:
> Hi,
> 
> I didn't check the source, yet because it fails to apply before that:
> 
> [root(a)rice-oxley ipfire-2.x]# pwclient git-am -s 692
> Applying patch #692 using 'git am -s'
> Description: squid 3.5.20: latest patches from upstream
> Applying: squid 3.5.20: latest patches from upstream
> .git/rebase-apply/patch:50: trailing whitespace.
> # 
> .git/rebase-apply/patch:57: trailing whitespace.
>  
> .git/rebase-apply/patch:73: trailing whitespace.
>  
> .git/rebase-apply/patch:81: trailing whitespace.
>  
> .git/rebase-apply/patch:107: trailing whitespace.
>  
> error: patch failed: lfs/squid:70
> error: lfs/squid: patch does not apply
> Patch failed at 0001 squid 3.5.20: latest patches from upstream
> The copy of the patch that failed is found in: .git/rebase-apply/patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
> 'git am' failed with exit status 128
> ...

Being curious:
Anything new about this problem?

I doublechecked my sources - here its building without any problems.

Best,
Matthias


  parent reply	other threads:[~2016-08-18 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24 11:44 Matthias Fischer
2016-08-02 15:14 ` Michael Tremer
2016-08-02 18:49   ` Matthias Fischer
2016-08-03 10:47     ` Michael Tremer
2016-08-03 18:49       ` Matthias Fischer
2016-08-18 16:07       ` Matthias Fischer [this message]
2016-08-18 17:26         ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35525ab4-cf59-0f60-38f0-fc54451ac459@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox