[Bug 217759] pkg-fallout choking on svn diff
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Mar 13 15:18:02 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217759
Bug ID: 217759
Summary: pkg-fallout choking on svn diff
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: portmaster at bsdforge.com
After the commit of pr 217342
I'm receiving messages from pkg-fallout. Where it's
puking on one of the svn diff (patch) entries -- deletions,
actually :
=> SHA256 Checksum OK for foswiki/Foswiki-2.1.3.tgz.
===========================================================================
=======================<phase: patch-depends >============================
===========================================================================
=======================<phase: patch >============================
===> Patching for foswiki-2.1.3
===> Applying FreeBSD patches for foswiki-2.1.3
No file to patch. Skipping...
1 out of 1 hunks ignored--saving rejects to tools/minifycss.rej
=> FreeBSD patch patch-minifycss failed to apply cleanly.
*** Error code 1
Stop.
make: stopped in /usr/ports/www/foswiki
this is the portion of the diff:
Index: foswiki/files/patch-minifycss
===================================================================
--- foswiki/files/patch-minifycss (revision 434989)
+++ foswiki/files/patch-minifycss (nonexistent)
@@ -1,11 +0,0 @@
---- tools/minifycss
-+++ tools/minifycss
-@@ -2,7 +2,7 @@
- BEGIN {
- unshift @INC, $ENV{FOSWIKICPAN} if defined $ENV{FOSWIKICPAN};
- }
--use CSS::Minifier qw(minify);
-+use CSS::Minifier::XS qw(minify);
-
- foreach my $file (@ARGV) {
- open(INFILE, $file) or die "failed opening $file";
The patch looks as one would expect, and as I use traditional
jails, not poudriere. I'm at a loss as to what needs to be done
to fix pkg-fallout.
Thoughts?
--Chris
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list