Bug 604553 - libxslt has extra characters after %{?dist}
libxslt has extra characters after %{?dist}
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libxslt (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Daniel Veillard
Michal Nowak
Depends On:
  Show dependency treegraph
Reported: 2010-06-16 04:32 EDT by Daniel Mach
Modified: 2013-03-07 21:10 EST (History)
5 users (show)

See Also:
Fixed In Version: libxslt-1.1.26-2.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-10 16:06:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Mach 2010-06-16 04:32:57 EDT
There are extra characters after %{?dist} in package release.

actual NVR:

correct NVR:
Comment 1 RHEL Product and Program Management 2010-06-16 04:33:13 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 2 Daniel Veillard 2010-07-06 04:19:11 EDT
That's a pure packaging problem, I can think this can be trivially fixed
and better fixed before GA because that can't be easilly corrected thereafter,

Comment 3 Don Dutile 2010-07-08 10:28:12 EDT
Is there a patch posted yet?  it _MUST_ be posted today to make snapshot8
(approved exception deadline), or it has to be moved to blocker for future
Comment 5 Daniel Veillard 2010-07-13 11:24:06 EDT
okay, trivial to fix, it's now built in RHEL-6-candidate:

2591918 build (RHEL-6-candidate, /cvs/dist:rpms/libxslt/RHEL-6:libxslt-1_1_26-2_el6) completed successfully

Comment 8 releng-rhel@redhat.com 2010-11-10 16:06:06 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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