Bug 1551543
| Summary: | Upgrade fails due to incorrect version checking | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mark Stanton <mark> | ||||||
| Component: | rpm | Assignee: | Packaging Maintenance Team <packaging-team-maint> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 26 | CC: | awilliam, bugzilla.redhat.com, dmach, extras-orphan, ignatenko, jmracek, mark, mblaha, mhatina, mjw, packaging-team-maint, pmatilai, pmoravco, rpm-software-management, russell, samuel-rhbugs, vmukhame | ||||||
| Target Milestone: | --- | Keywords: | CommonBugs, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | https://fedoraproject.org/wiki/Common_F26_bugs#upgrade-rich-deps | ||||||||
| Fixed In Version: | rpm-4.13.1-1.fc26 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-04-15 18:12:04 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Mark Stanton
2018-03-05 12:02:29 UTC
Please, can you provide /var/log/dnf.log file? (In reply to Marek Blaha from comment #1) > Please, can you provide /var/log/dnf.log file? Yes. I haven't been able to find a way of attaching it here, so I've put it up as a paste, the link is https://paste.fedoraproject.org/paste/ntci42fPDhQkGEczEP66Vg It's rather large, but claims it's uploaded. I'm trying to view it to check now, but it's taking a very long time to display, so I'll leave it for you to see. If it's not worked, let me know how I can get the file to you. I should say, the upgrade attempt was first actioned yesterday, 5th March. There should be Attachments block with link to add a new one just above the comments. Or try this link: https://bugzilla.redhat.com/attachment.cgi?bugid=1551543&action=enter I'm sorry, but I'm not able to download it from paste.fedoraproject.org. Created attachment 1404887 [details]
dnf log, part one
I think this covers the situation properly.
I have multiple subsequent attempts, making the file 21Mb, too big to upload in one go.
Let me know if you want the other half.
Hi, your uploaded log is good enough, no need of the other half. I can reproduce this problem when package php-pdepend-PHP-Depend is installed on F26. Attempt to upgrade to F27 then fails with error very similar to yours (not exactly the same, I've got only first 7 of your error messages, so there probably is another problematic package). So this is reproducer of problem: 1. install and upgrade F26 2. dnf install php-pdepend-PHP-Depend 3. dnf system-upgrade download --releasever=27 As a workaround, I can suggest uninstalling php-pdepend-PHP-Depend (and probably other packages, phpMyAdmin is one of suspects) and try to upgrade. Another workaround can be installing newer rpm (4.14) on your F26 machine. I switch this bug to rpm and kindly ask them for help with these questions: 1. there is change in dependencies for package php-pdepend-PHP-Depend between F26: php-composer(composer/ca-bundle) < 2 php-composer(composer/ca-bundle) >= 1.0 and F27: (php-composer(composer/ca-bundle) >= 1.0 with php-composer(composer/ca-bundle) < 2) Is this rich dependency right and working? 2. Is this (with) rich dependency fully supported on F26 (because transaction is checked by F26 rpm)? Documentation says that with operator works from rpm 4.14, but F26 contains 4.13. Many thanks for this. While waiting I will try removing the "depend" package and report back. I have previously tried after removing phpMyAdmin without success (log in the second half ;) ), but perhaps it matters in combination with the "depend" package. Hi Mark, there is another workaround you can try, without uninstalling any of your packages. On F26: # dnf system-upgrade download --releasever=27 --disablerepo=updates --no-downgrade # dnf system-upgrade reboot And then after F27 boots: # dnf upgrade rpm # dnf upgrade dnf # dnf distrosync DNF should always use target RPM to perform the upgrade. Nothing to do from RPM side. *** Bug 1552547 has been marked as a duplicate of this bug. *** Yeah, although the flaw on rpm-side is that these later additions to rich deps are not separately tracked with new rpmlib() dependencies. Preciously little that can be done about it after the fact though. (In reply to Panu Matilainen from comment #11) > Yeah, although the flaw on rpm-side is that these later additions to rich > deps are not separately tracked with new rpmlib() dependencies. Preciously > little that can be done about it after the fact though. This would definitely give better error messages, but won't help with upgrades. I think owner of this bugreport wants transaction to succeed instead of getting better error message ;) F25 to F27 upgrades also broken (gives error related to php-composer too). Same work around from #8 works. Correction needed --allowerase too It was decided this particular upgrade case will be fixed by backporting the missing rich dependencies to rpm 4.13.x, reassigning and changing version to f26. rpm-4.13.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-d4cacdf9bc rpm-4.13.1-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-d4cacdf9bc rpm-4.13.1-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. |