Bug 588420 – Broken link on updates page

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

Bug 588420 - Broken link on updates page

Summary:	Broken link on updates page

Status:	CLOSED NEXTRELEASE

Aliases:	None

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

Priority	low Severity medium
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:	2010-05-03 13:28 EDT by Hans Ulrich Niedermann
Modified:	2016-09-19 22:40 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-05-03 13:44:06 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Hans Ulrich Niedermann 2010-05-03 13:28:13 EDT

Description of problem:

      https://admin.fedoraproject.org/updates/bodhi

   links to ("Package Database")

      https://admin.fedoraproject.org/pkgdb/packages/name/bodhi

   which only says "Fedora Package Database -- Invalid PackageBuild Name".

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

   Bodhi Version: 0.7.4 -- Server: app02

How reproducible:

   100%

Steps to Reproduce:
1. Visit https://admin.fedoraproject.org/updates/bodhi
2. Click on "Package Database" link.
3. Enjoy error page.
  
Actual results:

   Error page.

Expected results:

   A useful page from the package database, possibly

      https://admin.fedoraproject.org/pkgdb/acls/name/bodhi

Additional info:

Comment 1 Luke Macken 2010-05-03 13:44:06 EDT

I fixed this in upstream commit 00ecf50c5a270452539b293fbb058f7e9cb1474d on March 25th.  I'll be pushing a new release to production shortly.

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