Bug 129196
| Summary: | up2date fails to update some packages | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Quentin Armitage <quentin.armitage> |
| Component: | up2date | Assignee: | Bret McMillan <bretm> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0 | CC: | overholt |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-10-19 19:21:30 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I think this might be because it's coming from the rhel-3-as-i386-rhaps-beta channel which has packages signed by a different GPG key. Try changing to the "Red Hat Application Server 1.0" channel and see if it's reproduceable (I'm doing the same here). Thanks. Andrew, I am not familiar with how to change to the "Red Hat Application Server 1.0" channel. If you could let me know what to do (and also how to revert to the channel I am currently using), then I will try it. What result did you get from trying this? I have just had an email about the case to say that the status is NEEDINFO. What info is currently needed? Regards, Quentin Armitage Hi Quentin, I think Adrian changed it to NEEDINFO because he wanted to see if things worked if you changed to the non-beta channel. You can do that by logging into RHN (rhn.redhat.com), going to the "Systems" tab and clicking on the system you wish to modify. Once there, click on "Alter Channel Subscriptions", uncheck "Red Hat Application Server Beta" and check "Red Hat Application Server 1.0". Finally, click the "Change Subscriptions" button. Now go to that machine and re-try your up2date command. Thanks, Andrew This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322) Description of problem: up2date will not update ant, bcel, jaf, javamail, junit or mx4j to the latest versions. Version-Release number of selected component (if applicable): up2date-4.2.33-1 How reproducible: Always Steps to Reproduce: 1.up2date --download ant (or any of the packages mentioned) 2. 3. Actual Results: Fetching Obsoletes list for channel: rhel-i386-as- 3... Fetching Obsoletes list for channel: rhel-i386-as-3-extras... Fetching Obsoletes list for channel: rhel-i386-as-3-devsuite... Fetching Obsoletes list for channel: rhel-i386-as-3-cluster... Fetching Obsoletes list for channel: rhel-3-as-i386-rhaps-beta... Fetching rpm headers... Name Version Rel ---------------------------------------------------------- ant 1.6.1 1jpp_2rh noarch Testing package set / solving RPM inter-dependencies... ant-1.6.1-1jpp_2rh.noarch.r Retrieved. ant-1.6.1-1jpp_2rh.src.rpm: Retrieved. The package ant-1.6.1-1jpp_2rh is signed, but with an uknown GPG key. Aborting.. . Package ant-1.6.1-1jpp_2rh has a unknown GPG signature. Aborting... Expected Results: The package should be successfully downloaded Additional info: The same problem occurred with version 4.2.16-1.