Bug 2210972 - perl-Text-Kakasi-2.04-51.fc39 FTBFS: error: Patch number not specified: %patch -p1 -b .perl580
Summary: perl-Text-Kakasi-2.04-51.fc39 FTBFS: error: Patch number not specified: %patc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Text-Kakasi
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F39FTBFS
TreeView+ depends on / blocked
 
Reported: 2023-05-30 07:34 UTC by Petr Pisar
Modified: 2023-05-30 10:52 UTC (History)
3 users (show)

Fixed In Version: perl-Text-Kakasi-2.04-52.fc39
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-30 10:52:30 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-847 0 None None None 2023-05-30 10:24:58 UTC

Description Petr Pisar 2023-05-30 07:34:25 UTC 
perl-Text-Kakasi-2.04-51.fc39 fails to build in Fedora 39:

$ fedpkg local
Downloading Text-Kakasi-2.04.tar.gz
######################################################################## 100.0%
error: Patch number not specified: %patch -p1 -b .perl580



error: Patch number not specified: %patch -p1 -b .perl580

test@fedora-39:~/fedora/perl-Text-Kakasi $ echo $?
1

This is triggered by rpm-4.18.90 which turned %patch without -P option into an error <http://rpm.org/wiki/Releases/4.19.0.html#spec>.

Reproducible: Always
Comment 1 Parag Nemade 2023-05-30 08:08:12 UTC 
this can be fixed by either using
%autosetup
or
%patch -P 0 -p1 -b .perl580
Comment 2 Fedora Update System 2023-05-30 10:49:04 UTC 
FEDORA-2023-393414462a has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-393414462a
Comment 3 Fedora Update System 2023-05-30 10:52:30 UTC 
FEDORA-2023-393414462a has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.