Bug 1220883
Summary: | rt-4.2.11 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ralf Corsepius <rc040203> |
Component: | rt | Assignee: | Ralf Corsepius <rc040203> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 21 | CC: | j, perl-devel, rc040203 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rt-4.2.11-1.fc22 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-06-30 00:15: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: |
Description
Ralf Corsepius
2015-05-12 18:03:12 UTC
Unfortunately because your local patch generation procedure is not easy to duplicate (patch1 should be done by deleting the files in the spec, not with a patch) and you haven't pushed your local update to git at all, nobody else can easily look at these test suite failures. Please consider at least pushing your changes to rawhide. You don't have to build the new package. (In reply to Jason Tibbitts from comment #1) > Unfortunately because your local patch generation procedure is not easy to > duplicate (patch1 should be done by deleting the files in the spec, not with > a patch) and you haven't pushed your local update to git at all, nobody else > can easily look at these test suite failures. I do not understand. I am using a local git repository consistiong of imported tarballs, because the upstream git-repository lacks any (tree-) structure/trees. I the past, their release tarballs did not even match with git. I.e. these patches are against the tarballs and should be applicable against the tarball's release tags in git. > Please consider at least pushing your changes to rawhide. You don't have to > build the new package. I disagree. The contents in fedora gits should match the last Fedora packages, because pushing broken package into fedora's git would render the Fedora package un-bug-fixable. Maybe an srpm or something? Unless you simply are not interested in having anyone else having a chance to look at the test suite failures. Also, not only are you completely wrong about your statement that git has to match what's actually built at all times, but you completely ignore the concept of git branches. rt-4.2.11-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/rt-4.2.11-1.fc21 rt-4.2.11-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/rt-4.2.11-1.fc22 The issues from comment#1 seem have "automagically" healed, without me having changed anything on my testsystem or rt's packaging. I can not reproduce them anymore and don't have the faintest clues about what could have been the culprit (likely f22's initial immaturity). Package rt-4.2.11-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rt-4.2.11-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-10342/rt-4.2.11-1.fc21 then log in and leave karma (feedback). rt-4.2.11-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. rt-4.2.11-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |