Bug 439764 – ypop traceback

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 439764 - ypop traceback

Summary:	ypop traceback

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	gnome-packagekit (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Luke Macken
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-03-31 05:21 EDT by Rahul Sundaram
Modified:	2016-09-19 22:38 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-03-31 12:48:21 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
traceback related to ypops (70.46 KB, image/png) 2008-03-31 05:21 EDT, Rahul Sundaram	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Rahul Sundaram 2008-03-31 05:21:19 EDT

Description of problem:

Ypop rpm package installs fine but throw ups a traceback when clicking on it via
pk-application

Version-Release number of selected component (if applicable):


How reproducible:

everytime


Steps to Reproduce:
1. Go to http://www.freewebs.com/casualprogrammer/downloads.htm
2. Install the Fedora 7 ypops rpm package
3. Search for it and click on it in pk-application
4. Get nice traceback
  
Actual results:

Screenshot attached

Comment 1 Rahul Sundaram 2008-03-31 05:21:19 EDT

Created attachment 299693 [details]
traceback related to ypops

Comment 2 Luke Macken 2008-03-31 12:48:21 EDT

Looks to be triggered by a 3rd party packaging bug.  Fedora's packaging
guidelines require everything to be utf-8 encoded, and there are a couple of
non-utf encoded bytes in the RPM description.

I fixed this in a70532c2fb3bcec8d10fcaa41dd276626b986b1b by replacing decoding
errors with question marks.

Note You need to log in before you can comment on or make changes to this bug.