On Wed, May 25, 2005 at 02:17:25PM -0600, Jeremy Nickurak wrote: > On mer, 2005-05-25 at 21:52 +0200, Javier Fernández-Sanguino Peña wrote: > > Maybe it's best if you provided a patch to the Release Notes, we might need > > to draft a section on "known upgrade issues" (was there in previous > > versions of the RN) and add that info (and other similar stuff) there. > > I should probabbly point out that I am not a debian developer, nor do I > really have any clue where to go with this. Just wanted to make sure > somebody more involved in the process than me was involved in the > process. No need to be a DD to provide a patch to the document. Just write the issue down as well as the steps that need to be taken to solve it and submit it to the debian-doc mailing list. If you go all the way and take the release note SGML sources and provide a patch (diff -u prefered) with the changes included then that would be best. If you think that's too much maybe you would like to detail the steps you took to fix this issue, more specifically: - which databases did you had in db2 format? - what did you do to convert these databases? - how did you verify that the database integrity was preserved in the upgrade? The Release team would be grateful if you submitted this (if you haven't done it already) to the upgrade-reports virtual package in the BTS as a bug report. Thanks Javier
Attachment:
signature.asc
Description: Digital signature