Merge lp:~cjwatson/auto-upgrade-testing/obsolete-conffiles into lp:~auto-upgrade-testing-dev/auto-upgrade-testing/trunk
| Status: | Merged |
|---|---|
| Merged at revision: | 10 |
| Proposed branch: | lp:~cjwatson/auto-upgrade-testing/obsolete-conffiles |
| Merge into: | lp:~auto-upgrade-testing-dev/auto-upgrade-testing/trunk |
| Diff against target: |
42 lines (+16/-9) 1 file modified
AutoUpgradeTester/post_upgrade_tests/test_conffiles.py (+16/-9) |
| To merge this branch: | bzr merge lp:~cjwatson/auto-upgrade-testing/obsolete-conffiles |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Jean-Baptiste Lallement | 2012-03-27 | Approve on 2012-03-27 | |
|
Review via email:
|
|||
Description of the Change
18:02 <slangasek> cjwatson: which reminds me; half the "obsolete conffiles" still listed on the jenkins reports are actually ones that have been taken over by replacing packages, so should fall out of 'obsolete' the next time the packages are upgraded, I think - is there really anything more we should be doing here? ...
18:02 <slangasek> ... https:/
18:03 <slangasek> (console-setup, file, fuse, grub are all in this category)
18:03 <cjwatson> slangasek: sounds like we should fix the autotester to notice that then?
18:03 <cjwatson> I haven't been looking at obsolete conffiles at all, though
18:03 <pitti> cjwatson: it does?
18:04 <slangasek> cjwatson: prolly - just wanted confirmation you didn't think there was anything further we should do packaging side
18:04 <pitti> they become yellow (i. e. tests failed, but upgrade succeeded)
18:04 <cjwatson> pitti: I mean it should not even list cases where some other package has taken them over
18:04 <pitti> ah
18:05 <slangasek> pitti: well, things we don't care about at all should IMHO be green, not yellow :)
18:05 <slangasek> (for whatever value of "don't care about" applies)
18:05 <cjwatson> slangasek: I don't *think* so; in my head that's something Replaces should deal with
18:06 <cjwatson> keyboard-
18:06 <slangasek> yes
18:06 <infinity> I thought Replaces did deal with it...
18:06 <slangasek> and none of these conffiles are listed as "obsolete" on my system
18:06 <slangasek> so I *think* it gets flushed when you do a subsequent upgrade of the replaced package
18:06 <cjwatson> sounds plausible, yes
18:15 <slangasek> cjwatson: confirmed; apt-get install console-setup --> obsolete, apt-get install --reinstall console-setup --> disappeared
This branch removes these cases from the test output.

Thanks for the fix!