I'm somewhat concerned about this particular bug. If a fake bug is necessary to keep the new kdelibs out of testing, this seems to indicate that any breakages that would result from an updated kdelibs without an updated kdebase are not expressed in the package relationships, which means they will still be a problem for partial upgrade scenarios even after kdebase is ready and this bug is closed. The other possibility is that kdelibs *will* break parts of kdebase if it precedes kdebase into testing, but that this is already documented appropriately using Conflicts between the relevant binary packages, in which case this bug is redundant and can be closed. You say that having split kdebase/kdelibs version is not a good idea "for various reasons". Could you please enumerate them? -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature