File conflict on Lucid -> Precise upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libksane (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Scott Kitterman |
Bug Description
No need to fix in Quantal since there's no upgrade path from Lucid to Quantal that isn't through Precise.
[IMPACT]
* Possible upgrade failures for people not using update-manager (update-manager will force-overwrite to bull it's way through this issue, but it's better to correct it).
[TESTCASE]
* Since package order isn't deterministic, this won't happen with every upgrade. The best way to test it is inspect the package metadata and verify that the new libksane-data conflicts/replaces libksane0 << 4:4.6.80.
[Regression Potential]
* None.
[Other Info]
* Should be landed as part of the update to 4.8.5.
Precise:
Filelist of package libksane0 in precise of architecture i386
/usr/lib/
/usr/lib/
/usr/share/
/usr/share/
/usr/share/
Filelist of package libksane-data in precise of architecture all
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
Lucid:
Filelist of package libksane0 in lucid of architecture i386
/usr/lib/
/usr/lib/
/usr/lib/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
/usr/share/
libksane needs to break/replace libksane0.
Related branches
Changed in libksane (Ubuntu): | |
status: | New → Invalid |
Changed in libksane (Ubuntu Precise): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Scott Kitterman (kitterman) |
milestone: | none → ubuntu-12.04.2 |
Hello Scott, or anyone else affected,
Accepted libksane into precise-proposed. The package will build now and be available at http:// launchpad. net/ubuntu/ +source/ libksane/ 4:4.8.5- 0ubuntu0. 2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification- failed. In either case, details of your testing will help us make a better decision.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance!