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 1760302

Summary:	etckeeper-bzr fails to install in Fedora rawhide (switch to breezy maybe?)
Product:	[Fedora] Fedora	Reporter:	Miro Hrončok <mhroncok>
Component:	etckeeper	Assignee:	Thomas Moschny <thomas.moschny>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	thomas.moschny
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-10 11:46:34 UTC	Type:	Bug
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:	1750909, 1690439

Description Miro Hrončok 2019-10-10 11:01:48 UTC

etckeeper-bzr-1.18.10-4.fc32.noarch fails to install in Fedora rawhide:

  package etckeeper-bzr-1.18.10-4.fc32.noarch requires bzr, but none of the providers can be installed
  nothing provides python2-paramiko needed by bzr-2.7.0-23.fc30.x86_64

This is caused by broken bazaar.

An attempted fix it to replace bazaar with breezy, see https://fedoraproject.org/wiki/Changes/ReplaceBazaarWithBreezy

Before the change is accepted, breezy was packaged (command brz).

Is it possible to switch etckeeper-bzr to breezy (and Python 3)?

Comment 1 Thomas Moschny 2019-10-10 11:40:12 UTC

That's the plan, yes (discussed in bug 1741027).

I hope to be able to look at it at the weekend.

Comment 2 Miro Hrončok 2019-10-10 11:46:34 UTC

OK, let's merge the bugz.

*** This bug has been marked as a duplicate of bug 1741027 ***