Bug 257144 - textproc/libxml2: Fails to patch: FAILED Applying FreeBSD patch-CVE-2019-20388
Summary: textproc/libxml2: Fails to patch: FAILED Applying FreeBSD patch-CVE-2019-20388
Status: Closed Not A Bug
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-desktop (Team)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-12 20:29 UTC by Michael Osipov
Modified: 2021-08-23 08:56 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Osipov 2021-07-12 20:29:32 UTC 
# make
===>  License MIT TRIO accepted by the user
===>   libxml2-2.9.12 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by libxml2-2.9.12 for building
===>  Extracting for libxml2-2.9.12
=> SHA256 Checksum OK for gnome2/libxml2-2.9.12.tar.gz.
===>  Patching for libxml2-2.9.12
===>  Applying FreeBSD patches for libxml2-2.9.12 from /usr/ports/textproc/libxml2/files
Ignoring previously applied (or reversed) patch.
1 out of 1 hunks ignored--saving rejects to xmlschemas.c.rej
===>  FAILED Applying FreeBSD patch-CVE-2019-20388
===> FAILED to apply cleanly FreeBSD patch(es)  patch-CVE-2019-20388
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/textproc/libxml2
*** Error code 1

Stop.
make: stopped in /usr/ports/textproc/libxml2

The file in question is xmlschemas.c and looks completely different at this hunk.
Comment 1 Michael Osipov 2021-07-12 20:35:13 UTC 
Purely my fault....
Comment 2 theis 2021-08-22 19:04:10 UTC 
I ran into the same problem but have no solution. Why do you think it was your fault? Or what to do to solve it?
Comment 3 Michael Osipov 2021-08-22 21:15:52 UTC 
I will need to try to remember and let you know.
Comment 4 theis 2021-08-23 08:56:01 UTC 
It looks as if my last gitup update a couple of days before didn't work, esp. the CVE patch files were not removed. I did a gitup again this morning and the error is gone. So I'm happy now :)

And thanks for offering me to help me out.