Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 926195

Summary:	nano: Does not support aarch64 in f19 and rawhide
Product:	[Fedora] Fedora	Reporter:	Dennis Gilmore <dennis>
Component:	nano	Assignee:	Kamil Dudka <kdudka>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dwmw2, jaswinder, kdudka
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nano-2.3.2-2.fc20	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-20 19:38:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	922257

Description Dennis Gilmore 2013-03-23 15:33:33 UTC

Support for the ARM 64 bit CPU architecture (aarch64) was introduced in 
autoconf 2.69.  nano appears to use an earlier version of 
autoconf, preventing its being built.  This can be fixed in of three ways (In order of preference):

1. Work with upstream to migrate the package to autoconf 2.69.

2. Rerun autoconf or autoreconf in %prep or %build prior to running 
configure.

3. Apply the patch at http://ausil.fedorapeople.org/aarch64/nano/nano-aarch64.patch
which updates config.guess and config.sub to recognize aarch64.

Comment 1 Kamil Dudka 2013-04-03 14:01:11 UTC

(In reply to comment #0)
> 1. Work with upstream to migrate the package to autoconf 2.69.

This already the case for the latest upstream release, which is now in rawhide.

> 2. Rerun autoconf or autoreconf in %prep or %build prior to running 
> configure.

I will do this for the f19 branch.

Comment 2 Kamil Dudka 2013-04-04 13:15:33 UTC

fixed in nano-2.3.2-2.fc20

Comment 3 Fedora Update System 2013-04-04 13:22:13 UTC

nano-2.3.1-7.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/nano-2.3.1-7.fc19

Comment 4 Fedora Update System 2013-04-05 02:56:40 UTC

Package nano-2.3.1-7.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing nano-2.3.1-7.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4905/nano-2.3.1-7.fc19
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-04-20 19:38:41 UTC

nano-2.3.1-7.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.