Why is the 'figlet' binary package still in main?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274950&archive=yes
--
Karl 2005-03-22 19:59
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Mar 22, 2005 at 10:46:50PM +0100, Arnaud Vandyck wrote:
> Tue, 22 Mar 2005 13:00:21 -0800,
> Steve Langasek <[EMAIL PROTECTED]> wrote:
> > Arnaud, if ia64 and mipsel are fixed, can we get this uploaded *now*,
> Done ;-)
Indeed -- thanks for the quick response!
--
Steve Langasek
postm
Tue, 22 Mar 2005 13:00:21 -0800,
Steve Langasek <[EMAIL PROTECTED]> wrote:
> Arnaud, if ia64 and mipsel are fixed, can we get this uploaded *now*,
Done ;-)
--
.''`.
: :' :rnaud
`. `'
`-
Java Trap: http://www.gnu.org/philosophy/java-trap.html
--
To UNSUBSCRIBE, email to [EMAIL
On Tue, Mar 22, 2005 at 04:34:27PM +0100, Dalibor Topic wrote:
> Am Dienstag, den 22.03.2005, 13:46 +0100 schrieb Arnaud Vandyck:
> > FYI.
> >
> > A new kaffe upstream snapshot with debian support for mips and
> > mipsel has been uploaded. It seems it couldn't be built on mipsel :'(
> >
> > http
HEY,ARE U ONLINE,THIS IS JAIME.
On Tue, Mar 22, 2005 at 03:41:19AM -0800, Steve Langasek wrote:
> I'm happy to consider possible release tracking systems for etch; David
> Nusinow seems to be enjoying the task of prototyping his rails/debbugs
> system. But that's not useful for "initially submitting" anything today.
It's been a
On Tuesday 22 March 2005 12:41, Steve Langasek wrote:
> On Wed, Mar 16, 2005 at 03:11:28PM -0300, Daniel Ruoso wrote:
> > My suggestion is to initially submitting the "major
> > package changes" as bugs to the (future) etch pseudo-package, allowing
> > others to suggest expected features/changes in
On Wed, Mar 16, 2005 at 03:11:28PM -0300, Daniel Ruoso wrote:
> My suggestion is to initially submitting the "major
> package changes" as bugs to the (future) etch pseudo-package, allowing
> others to suggest expected features/changes in etch and finalizing the
> list of release issues for etch jus
On Tue, Mar 22, 2005 at 10:46:36AM +0100, Bastian Blank wrote:
> On Mon, Mar 21, 2005 at 11:33:18PM -0800, Steve Langasek wrote:
> > What RC bug does the lvm2 update fix? I don't see any closed RC bugs in the
> > BTS.
> #297010, it was reassigned to libc6-dev for the real fix.
Hrm. It would hav
On Mon, Mar 21, 2005 at 11:33:18PM -0800, Steve Langasek wrote:
> What RC bug does the lvm2 update fix? I don't see any closed RC bugs in the
> BTS.
#297010, it was reassigned to libc6-dev for the real fix.
Bastian
--
A princess should not be afraid -- not with a brave knight to protect her.
Hi Norbert,
On Tue, Mar 15, 2005 at 07:48:31AM +0100, Norbert Tretkowski wrote:
> The non-free code which was removed in 4.74.dfsg.1-1 should not be
> released with sarge. No new RC bugs were introduced between 4.71-1
> (which is currently in sarge) and 4.74.dfsg.1-1 (which is still in
> incoming)
* Thomas Bushnell BSG ([EMAIL PROTECTED]) [050322 04:15]:
> (Why not wait the freeze until NEW processing has caught up?)
If the new processing continues with the current speed, it will catch up
before the freeze in either case.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
PGP 1024
On Mon, Mar 21, 2005 at 08:28:49PM +0100, Thomas Hood wrote:
> On Mon, 21 Mar 2005 13:10:09 +0100, Colin Watson wrote:
> > This doesn't look right:
> >
> > - ;;
> > - restart)
> > - $0 start
> > ;;
> > *)
> > echo "Usage: $0
13 matches
Mail list logo
