At 06 Aug 2003 01:42:08 +0100,
Philip Blundell wrote:
> On Wed, 2003-08-06 at 01:36, GOTO Masanori wrote:
> > That's right, it's nice idea to update cvs.dpatch into the latest or
> > at least 2003-07-22 cvs. I update it later.
>
> I'm a little scared of doing a wholesale update of cvs.dpatch to the
> current HEAD just at the minute. Right now we do have a codebase that
> at least builds on every architecture and doesn't have too many known
> problems; it doesn't necessarily seem like a good time to import a whole
> pile of new changes.
>
> I was thinking more of just dropping the fix for that one bug in as a
> separate .dpatch file, uploading 2.3.2-2 to unstable, then updating
> cvs.dpatch for 2.3.2-3.
Yup, it's safe, seconded. I've added a separate .dpatch for this:
debian/patches/80_glibc232-wcsmbs-fix.dpatch
After the last build and test on various architectures, I would like
to dupload 2.3.2-2.
Regards,
-- gotom
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
