A freeze sounds good to me. Sorry about this, I had a bit of misunderstanding on the state of play.
Rob On Sat, 26 Jun 2004 06:46:25 -0500 Colin Watson <[EMAIL PROTECTED]> wrote: > On Thu, Jun 24, 2004 at 09:32:19PM -0400, Rob Taylor wrote: > > Format: 1.7 > > Date: Thu, 24 Jun 2004 16:43:58 -0300 > > Source: libgnomeprint > > Binary: libgnomeprint2.2-0 libgnomeprint2.2-doc libgnomeprint2.2-data > > libgnomeprint2.2-dev > > Architecture: source all i386 > > Version: 2.6.2-1 > > Distribution: unstable > > Urgency: medium > > Maintainer: Rob Taylor <[EMAIL PROTECTED]> > > Changed-By: Rob Taylor <[EMAIL PROTECTED]> > > Description: > > libgnomeprint2.2-0 - The GNOME 2.2 print architecture - runtime files > > libgnomeprint2.2-data - The GNOME 2.2 print architecture - data files > > libgnomeprint2.2-dev - The GNOME 2.2 print architecture - development files > > libgnomeprint2.2-doc - The GNOME 2.2 print architecture - documentation > > files > > Changes: > > libgnomeprint (2.6.2-1) unstable; urgency=medium > > . > > * upgrade to new upstream > > * Fixed debian/watch to use pasv > > Could we please have a mini-freeze of everything depending on cupsys? We > need to get this all into testing quite soon. > > (Sorry for picking on this upload, it's just one that was brought up on > IRC and seems fairly central.) > > Thanks, > > -- > Colin Watson [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
