public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 14909d5fe9371231437b9b85a35adf4ae5e006f1
Date: Wed, 27 Jul 2022 09:50:02 +0000	[thread overview]
Message-ID: <4Lt8CH2TL9z2y0K@people01.haj.ipfire.org> (raw)

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

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  14909d5fe9371231437b9b85a35adf4ae5e006f1 (commit)
      from  b2ab2f4cccb0792e7444e87bd5ea18590ed6272c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 14909d5fe9371231437b9b85a35adf4ae5e006f1
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Wed Jul 27 09:49:36 2022 +0000

    cups-pdf: Fix applying patch
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 lfs/cups-pdf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Difference in files:
diff --git a/lfs/cups-pdf b/lfs/cups-pdf
index efa40e87b..5e9f86562 100644
--- a/lfs/cups-pdf
+++ b/lfs/cups-pdf
@@ -81,7 +81,7 @@ $(subst %,%_BLAKE2,$(objects)) :
 $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
 	@$(PREBUILD)
 	@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE)
-	cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/cups-pdf-setpdfwrite.patch
+	cd $(DIR_APP) && patch -Np0 < $(DIR_SRC)/src/patches/cups-pdf-setpdfwrite.patch
 
 	# Compile backend
 	cd $(DIR_APP)/src && gcc $(CFLAGS) cups-pdf.c -o cups-pdf -lcups 


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2022-07-27  9:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4Lt8CH2TL9z2y0K@people01.haj.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@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