| Summary: | STA-2 "upgrade" and online upgrade from 5.1: lib64 for Samba fails to upgrade, file conflict with "lib64netapi0" | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Rick Stockton <rickstockton> |
| Component: | RPM Packages | Assignee: | Buchan Milne <bgmilne> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | jani.valimaa, marja11, pkg-bugs, rickstockton |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | samba | CVE: | |
| Status comment: | |||
|
Description
Rick Stockton
2017-03-12 05:56:06 CET
Rick Stockton
2017-03-12 05:56:44 CET
Summary:
STA-2 "upgrade" and online upgrade from 5.1. lib64 for Samba fails to upgrade, file conflict with "lib64netapi0" =>
STA-2 "upgrade" and online upgrade from 5.1: lib64 for Samba fails to upgrade, file conflict with "lib64netapi0" Note: I have spare disks to clone my "large" 5.1 system, for testing of future fixes. CC:
(none) =>
rickstockton lib64netapi0 only exists in Mga5, maybe it should have been obsoleted by another Samba package in Mga6? Assigning to the registered maintainer, but CC'ing all packagers collectively, in case the maintainer is unavailable. Priority:
Normal =>
High Should be fixed with samba-4.5.5-2.mga6. CC:
(none) =>
jani.valimaa Jani, has 'samba-4.5.5-2.mga6' been committed to Cooker already, but _later_ than my last "online-upgrade" attempt? If so, I can verify the fix by restoring my "test disk" to 5.1 and re-performing online upgrade again tonight (Monday, early AM in EU). It should result in a working system, with working samba connections to 3 "Windows 7" computers. Since the older RPM exists in STA-2, I won't bother to try anything further with that DVD. And anyway, DVD upgrade blows up completely, just a bit later than the SAMBA error: glibc is newer on my fully-updated "5.1" system. This morning (USA time) I see the new RPM present in Cauldron (from 'Sun Mar 12 14:55:42 2017'). I am running an update test immediately, and will report back in a few hours. I have verified the fix. Let's see if I'm allowed to change the bug status while it's assigned to someone else ;) Status:
NEW =>
RESOLVED |