Ticker Updt'ae

2008-06-16 Thread shlomo_versano
Dd.in't we tell you_? Company: Angstorm Micro-ssyetms Ticke r otbcb:, agms Recommend: Strong Buy Prc ie_: 0._40 Hi gh Trading: 331,485 S in-ce the hedalines rela'esed, more shraes were traded th-an h' ave been since March . More events will unfold, sales are up and product is moivng this

Re: Considerations for lilo removal

2008-06-16 Thread Romain Beauxis
Le Monday 16 June 2008 07:31:49 William Pitcock, vous avez écrit : With grub being stable and grub2 approaching stability itself, do we really need lilo anymore? It's not even installed by default anymore, and the only systems I have that are still on lilo are installations of Debian I have

Re: Considerations for lilo removal

2008-06-16 Thread William Pitcock
Hi, On Mon, 2008-06-16 at 09:08 +0200, Romain Beauxis wrote: Le Monday 16 June 2008 07:31:49 William Pitcock, vous avez écrit : With grub being stable and grub2 approaching stability itself, do we really need lilo anymore? It's not even installed by default anymore, and the only systems I

Re: Considerations for lilo removal

2008-06-16 Thread Sune Vuorela
On 2008-06-16, William Pitcock [EMAIL PROTECTED] wrote: That doesn't strike me as a valid configuration. Infact, it shouldn't work with lilo because lilo wants /boot to be on a real device. The fact that it does should be considered a bug, not a feature. lilo-22.8$ head

Re: Considerations for lilo removal

2008-06-16 Thread William Pitcock
Hi, On Mon, 2008-06-16 at 07:20 +, Sune Vuorela wrote: On 2008-06-16, William Pitcock [EMAIL PROTECTED] wrote: That doesn't strike me as a valid configuration. Infact, it shouldn't work with lilo because lilo wants /boot to be on a real device. The fact that it does should be

Re: Considerations for lilo removal

2008-06-16 Thread Sune Vuorela
On 2008-06-16, William Pitcock [EMAIL PROTECTED] wrote: That patch only makes lilo map LVMs to an appropriate physical device. It does not guarantee that you will be able to boot off of an LV on a physical volume. As such, the behaviour is still undefined. Consider a situation where /boot

Re: Considerations for lilo removal

2008-06-16 Thread Mike Hommey
On Mon, Jun 16, 2008 at 02:27:11AM -0500, William Pitcock wrote: Hi, On Mon, 2008-06-16 at 07:20 +, Sune Vuorela wrote: On 2008-06-16, William Pitcock [EMAIL PROTECTED] wrote: That doesn't strike me as a valid configuration. Infact, it shouldn't work with lilo because lilo wants

Re: Considerations for lilo removal

2008-06-16 Thread Joerg Platte
Am Montag, 16. Juni 2008 schrieb William Pitcock: Hi, That patch only makes lilo map LVMs to an appropriate physical device. It does not guarantee that you will be able to boot off of an LV on a physical volume. As such, the behaviour is still undefined. Consider a situation where /boot

Re: Considerations for lilo removal

2008-06-16 Thread Goswin von Brederlow
Mike Hommey [EMAIL PROTECTED] writes: On Mon, Jun 16, 2008 at 02:27:11AM -0500, William Pitcock wrote: Hi, On Mon, 2008-06-16 at 07:20 +, Sune Vuorela wrote: On 2008-06-16, William Pitcock [EMAIL PROTECTED] wrote: That doesn't strike me as a valid configuration. Infact, it shouldn't

Re: Considerations for lilo removal

2008-06-16 Thread Shachar Shemesh
William Pitcock wrote: It seems like moving to grub for everything may be a good choice on the archs where lilo is used. Lilo has one killer feature that is totally missing from GRUB - the -R option. It allows me to upgrade a kernel on remote servers, knowing that if the upgrade fails, I

Re: Considerations for lilo removal

2008-06-16 Thread Frans Pop
William Pitcock wrote: I am wondering if it is a good idea to remove lilo entirely. At the moment, lilo has been pulled from testing, and the code is in a shape That's just great. That means that whoever did this just broke an option that's been available in Debian Installer since forever: to

Re: Considerations for lilo removal

2008-06-16 Thread Goswin von Brederlow
William Pitcock [EMAIL PROTECTED] writes: Hi, I am wondering if it is a good idea to remove lilo entirely. At the moment, lilo has been pulled from testing, and the code is in a shape where a grave bug (bug #479607) is unlikely fixable without severe refactoring of the codebase. I don't

Re: Considerations for lilo removal

2008-06-16 Thread Mike Hommey
On Mon, Jun 16, 2008 at 11:54:52AM +0300, Shachar Shemesh wrote: William Pitcock wrote: It seems like moving to grub for everything may be a good choice on the archs where lilo is used. Lilo has one killer feature that is totally missing from GRUB - the -R option. It allows me to

Re: Considerations for lilo removal

2008-06-16 Thread Adam Borowski
On Mon, Jun 16, 2008 at 11:04:35AM +0200, Mike Hommey wrote: On Mon, Jun 16, 2008 at 11:54:52AM +0300, Shachar Shemesh wrote: Lilo has one killer feature that is totally missing from GRUB - the -R option. It allows me to upgrade a kernel on remote servers, knowing that if the

Re: Bug#486425: ITP: bomstrip -- strip Byte-Order Marks from UTF-8 text files

2008-06-16 Thread Guus Sliepen
On Mon, Jun 16, 2008 at 03:08:02AM +0300, Peter Pentchev wrote: * Package name: bomstrip Programming Lang: Awk, Brainf*ck, C, C++, Forth, Haskell, OCaml, Ook!, Pascal, PHP, Perl, PostScript, Python, Ruby, sed, Unlambda All these programming

Re: Considerations for lilo removal

2008-06-16 Thread Mike Hommey
On Mon, Jun 16, 2008 at 10:53:22AM +0200, Goswin von Brederlow wrote: Mike Hommey [EMAIL PROTECTED] writes: On Mon, Jun 16, 2008 at 02:27:11AM -0500, William Pitcock wrote: Hi, On Mon, 2008-06-16 at 07:20 +, Sune Vuorela wrote: On 2008-06-16, William Pitcock [EMAIL PROTECTED]

Re: Considerations for lilo removal

2008-06-16 Thread Mike Hommey
On Mon, Jun 16, 2008 at 10:57:32AM +0200, Frans Pop wrote: We still very regularly get installation reports where people use lilo rather than grub, so it must still have a fairly significant user base. I would say that the activity on the bug report shows the same. OTOH, aren't most of these

Re: Bug#486425: ITP: bomstrip -- strip Byte-Order Marks from UTF-8 text files

2008-06-16 Thread Peter Pentchev
On Mon, Jun 16, 2008 at 10:55:47AM +0200, Guus Sliepen wrote: On Mon, Jun 16, 2008 at 03:08:02AM +0300, Peter Pentchev wrote: * Package name: bomstrip Programming Lang: Awk, Brainf*ck, C, C++, Forth, Haskell, OCaml, Ook!, Pascal, PHP, Perl, PostScript, Python,

Re: cupsys renamed to cups, please adjust your (build-)depends

2008-06-16 Thread Jörg Sommer
Hallo Bernhard, Bernhard R. Link [EMAIL PROTECTED] wrote: * Martin Pitt [EMAIL PROTECTED] [080612 18:04]: after many years of calling our CUPS package cupsys it has finally be renamed to the proper upstream name cups, including init scripts, library packages, etc. This makes us compatible

Re: Considerations for lilo removal

2008-06-16 Thread Alexander Zangerl
On Mon, 16 Jun 2008 11:19:03 +0200, Mike Hommey writes: On Mon, Jun 16, 2008 at 10:57:32AM +0200, Frans Pop wrote: We still very regularly get installation reports where people use lilo rather than grub, so it must still have a fairly significant user base. I would say that the activity on

Re: Considerations for lilo removal

2008-06-16 Thread frank paulsen
William Pitcock [EMAIL PROTECTED] writes: With grub being stable and grub2 approaching stability itself, do we really need lilo anymore? It's not even installed by default anymore, and the only systems I have that are still on lilo are installations of Debian I have had since Woody. Debian

Re: Considerations for lilo removal

2008-06-16 Thread Ron Johnson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/16/08 04:19, Mike Hommey wrote: On Mon, Jun 16, 2008 at 10:57:32AM +0200, Frans Pop wrote: We still very regularly get installation reports where people use lilo rather than grub, so it must still have a fairly significant user base. I

Re: Considerations for lilo removal

2008-06-16 Thread William Pitcock
Hi, On Mon, 2008-06-16 at 19:27 +1000, Alexander Zangerl wrote: please don't remove lilo. It certaintly won't be happening in lenny. This may be revisited in lenny+1 though. William signature.asc Description: This is a digitally signed message part

Re: Considerations for lilo removal

2008-06-16 Thread peter green
I am wondering if it is a good idea to remove lilo entirely. At the moment, lilo has been pulled from testing, and the code is in a shape Can either version of grub handle all the cases that lilo can? for example can either of them handle the situation where root is on lvm and there is

Re: bits/news from the users of Debian?

2008-06-16 Thread Michelle Konzack
Hello Paul and *, Unfortunately I have found your message very late... Let us begin: Am 2008-03-30 21:51:14, schrieb Paul Wise: If you are using Debian on your phone, embedded computer, laptop, desktop, server, network, telecommunications equipment or other part of your information

Re: Considerations for lilo removal

2008-06-16 Thread Michael Banck
On Mon, Jun 16, 2008 at 09:37:34AM +0200, Joerg Platte wrote: Am Montag, 16. Juni 2008 schrieb William Pitcock: Hi, That patch only makes lilo map LVMs to an appropriate physical device. It does not guarantee that you will be able to boot off of an LV on a physical volume. As such, the

Re: Considerations for lilo removal

2008-06-16 Thread Frans Pop
(Dropping d-release for this part of the discussion.) On Monday 16 June 2008, Mike Hommey wrote: On Mon, Jun 16, 2008 at 10:57:32AM +0200, Frans Pop wrote: We still very regularly get installation reports where people use lilo rather than grub, so it must still have a fairly significant

Re: Considerations for lilo removal

2008-06-16 Thread Michael Banck
On Mon, Jun 16, 2008 at 11:03:10AM +0200, Goswin von Brederlow wrote: I don't really see this as a bug, certainly not as grave. The problem seems to be that lilo simply can't handle large images and the default ramdisk just has now hit that limit on amd64. So it's broken on amd64 for the

Re: Considerations for lilo removal

2008-06-16 Thread Romain Beauxis
Le Monday 16 June 2008 12:03:09 Michael Banck, vous avez écrit : On some of my boxes all filesystems are on LVMs and the Debian installer used lilo to boot the systems. It would be nice if these systems can still be used with future Debian versions. Please remove lilo only if there's a

Re: Considerations for lilo removal

2008-06-16 Thread Frans Pop
(Dropping d-release again.) On Monday 16 June 2008, peter green wrote: I am wondering if it is a good idea to remove lilo entirely. At the moment, lilo has been pulled from testing, and the code is in a shape Can either version of grub handle all the cases that lilo can? D-I currently

Re: Re: Considerations for lilo removal

2008-06-16 Thread Jon Dowland
That doesn't strike me as a valid configuration. Infact, it shouldn't work with lilo because lilo wants /boot to be on a real device. The fact that it does should be considered a bug, not a feature. Valid or not, the installer actually gives you lilo if you configure the partitions this way

Bug#486470: ITP: peak-linux-driver -- PEAK-System CAN-bus interface driver source

2008-06-16 Thread Teemu Ikonen
Package: wnpp Severity: wishlist Owner: Teemu Ikonen [EMAIL PROTECTED] * Package name: peak-linux-driver Version : 6.7 Upstream Author : PEAK System-Technik GmbH [EMAIL PROTECTED] * URL : http://www.peak-system.com/linux/ * License : GPL-2+ Programming Lang:

Re: Considerations for lilo removal

2008-06-16 Thread Goswin von Brederlow
Mike Hommey [EMAIL PROTECTED] writes: On Mon, Jun 16, 2008 at 10:53:22AM +0200, Goswin von Brederlow wrote: Mike Hommey [EMAIL PROTECTED] writes: On Mon, Jun 16, 2008 at 02:27:11AM -0500, William Pitcock wrote: Hi, On Mon, 2008-06-16 at 07:20 +, Sune Vuorela wrote: On

Re: Considerations for lilo removal

2008-06-16 Thread Frans Pop
Michael Banck wrote: On Mon, Jun 16, 2008 at 11:03:10AM +0200, Goswin von Brederlow wrote: I don't really see this as a bug, certainly not as grave. The problem seems to be that lilo simply can't handle large images and the default ramdisk just has now hit that limit on amd64. So it's

Re: Considerations for lilo removal

2008-06-16 Thread Francesco P. Lovergine
On Mon, Jun 16, 2008 at 12:31:49AM -0500, William Pitcock wrote: If we do not need lilo, then I will file a RM bug in the next couple of weeks. I had at least a couple of boxes in the past where grub were problematic and I used the old good linux loader. I generally agree that grub is more

Re: Considerations for lilo removal

2008-06-16 Thread Lennart Sorensen
On Mon, Jun 16, 2008 at 11:54:52AM +0300, Shachar Shemesh wrote: Lilo has one killer feature that is totally missing from GRUB - the -R option. It allows me to upgrade a kernel on remote servers, knowing that if the upgrade fails, I will get the original kernel after a few minutes without

Re: Considerations for lilo removal

2008-06-16 Thread John Hasler
Francesco P. Lovergine writes: I had at least a couple of boxes in the past where grub were problematic and I used the old good linux loader. When I installed Lenny on this AMD64 box (ASUS A8V-XE) a few weeks ago Grub was unable to boot it. I had to go back and reinstall, selecting Lilo. --

Re: Considerations for lilo removal

2008-06-16 Thread Darren Salt
I demand that Frans Pop may or may not have written... William Pitcock wrote: [snip] With grub being stable and grub2 approaching stability itself, do we really need lilo anymore? It's not even installed by default anymore, and the only systems I have that are still on lilo are installations

Re: Considerations for lilo removal

2008-06-16 Thread Bernd Schubert
William Pitcock wrote: Hi, I am wondering if it is a good idea to remove lilo entirely. At the moment, lilo has been pulled from testing, and the code is in a shape where a grave bug (bug #479607) is unlikely fixable without severe refactoring of the codebase. Well, grub is also not free

Re: Considerations for lilo removal

2008-06-16 Thread David Duggins
I would also have to say that the Linux Community has always been about freedom and choice. Although I use GRUB my self, why should we remove a useful package that is being used? Wouldn't that take away from the freedom just a bit? Just because you might not like it, or like another program

Non-free question regarding upstream releasing different binary-only tarballs for different architectures

2008-06-16 Thread Martin Meredith
Hi there. I currently maintain rar and unrar-nonfree in debian. When uscanning for the latest version of rar - it started to download the x64 version, which I haven't seen before. Anyway - It seems that upstream are now packaging a i386 binary, and an x64 binary. I'm not too sure how I should

Re: Considerations for lilo removal

2008-06-16 Thread William Pitcock
Hi, On Mon, 2008-06-16 at 00:31 -0500, William Pitcock wrote: [a lot of stuff] As many people have brought up usecases not covered by alternatives, the plan seems to be: * Cope with the growing initramfs issue as best we can, e.g. by displaying a warning to the user that the kernel may not be

Re: future of esound

2008-06-16 Thread Frans Pop
Hi Martin, Thanks for replying. Martin Pitt wrote: esound should *so much* die completely. It has very poor sound quality (huge A/V desync when playing videos, etc.), very poor code quality (it causes complete desktop locks very often, due to not being thread safe), and is abandoned

Re: Considerations for lilo removal

2008-06-16 Thread Mike Bird
FWIW, adding -9 to the gzip in mkinitramfs gives a 0.5% saving, which may help with some marginal cases. OTOH using bzip2 instead of gzip saves 10.5% but I have no idea how much work it would take to support bzip'd initrd's. --Mike Bird -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Re: Considerations for lilo removal

2008-06-16 Thread Frans Pop
William Pitcock wrote: * Cope with the growing initramfs issue as best we can, e.g. by displaying a warning to the user that the kernel may not be bootable by lilo due to the 8MiB boundry in liloconfig. Having only a warning is not sufficient for the use of lilo in new installations! We

Re: Considerations for lilo removal

2008-06-16 Thread Florian Weimer
* William Pitcock: I am wondering if it is a good idea to remove lilo entirely. At the moment, lilo has been pulled from testing, and the code is in a shape where a grave bug (bug #479607) is unlikely fixable without severe refactoring of the codebase. BTW, the bug report lacks this

Accepted apt-p2p 0.1.4 (source all)

2008-06-16 Thread Cameron Dale
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Jun 2008 23:20:28 -0700 Source: apt-p2p Binary: apt-p2p Architecture: source all Version: 0.1.4 Distribution: unstable Urgency: low Maintainer: Cameron Dale [EMAIL PROTECTED] Changed-By: Cameron Dale [EMAIL PROTECTED]

Accepted libassuan 1.0.5-1 (source amd64)

2008-06-16 Thread Eric Dorland
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 02:38:31 -0400 Source: libassuan Binary: libassuan-dev Architecture: source amd64 Version: 1.0.5-1 Distribution: unstable Urgency: low Maintainer: Eric Dorland [EMAIL PROTECTED] Changed-By: Eric Dorland [EMAIL

Accepted findimagedupes 2.7-3 (source i386)

2008-06-16 Thread Andreas Tille
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 29 May 2008 08:26:37 +0200 Source: findimagedupes Binary: findimagedupes Architecture: source i386 Version: 2.7-3 Distribution: unstable Urgency: low Maintainer: Debian Science Maintainers [EMAIL PROTECTED] Changed-By: Andreas

Accepted streamripper 1.63.5-1 (source amd64)

2008-06-16 Thread Michael Ablassmeier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 09:04:25 +0200 Source: streamripper Binary: streamripper Architecture: source amd64 Version: 1.63.5-1 Distribution: unstable Urgency: low Maintainer: [EMAIL PROTECTED] Changed-By: Michael Ablassmeier [EMAIL

Accepted schroedinger 1.0.3-2 (source all i386)

2008-06-16 Thread Sebastian Dröge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 09:39:54 +0200 Source: schroedinger Binary: libschroedinger-1.0-0 libschroedinger-dev libschroedinger-doc gstreamer0.10-schroedinger Architecture: source all i386 Version: 1.0.3-2 Distribution: unstable Urgency: low

Accepted libconvert-asn1-perl 0.21-1 (source all)

2008-06-16 Thread Damyan Ivanov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:23:01 +0300 Source: libconvert-asn1-perl Binary: libconvert-asn1-perl Architecture: source all Version: 0.21-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group [EMAIL PROTECTED] Changed-By: Damyan

Accepted liboil 0.3.14-5 (source all i386)

2008-06-16 Thread Sebastian Dröge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 09:56:02 +0200 Source: liboil Binary: liboil0.3 liboil0.3-dev liboil0.3-dbg liboil0.3-doc Architecture: source all i386 Version: 0.3.14-5 Distribution: unstable Urgency: low Maintainer: Maintainers of GStreamer

Accepted libextutils-cbuilder-perl 0.23-1 (source all)

2008-06-16 Thread Damyan Ivanov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:58:27 +0300 Source: libextutils-cbuilder-perl Binary: libextutils-cbuilder-perl Architecture: source all Version: 0.23-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group [EMAIL PROTECTED]

Accepted freetype 2.3.6-1 (source amd64)

2008-06-16 Thread Steve Langasek
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Jun 2008 23:52:53 -0700 Source: freetype Binary: libfreetype6 libfreetype6-dev freetype2-demos libfreetype6-udeb Architecture: source amd64 Version: 2.3.6-1 Distribution: unstable Urgency: low Maintainer: Steve Langasek

Accepted git-core 1:1.5.6~rc3-1 (source all)

2008-06-16 Thread Gerrit Pape
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Jun 2008 11:14:49 + Source: git-core Binary: git-core git-doc git-arch git-cvs git-svn git-email git-daemon-run git-gui gitk gitweb Architecture: all source Version: 1:1.5.6~rc3-1 Distribution: experimental Urgency: low

Accepted thailatex 0.4.2-4 (source all)

2008-06-16 Thread Theppitak Karoonboonyanan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 10:07:25 +0700 Source: thailatex Binary: thailatex Architecture: source all Version: 0.4.2-4 Distribution: unstable Urgency: low Maintainer: Theppitak Karoonboonyanan [EMAIL PROTECTED] Changed-By: Theppitak

Accepted vlock 2.2.2-1 (source i386)

2008-06-16 Thread Alexander Wirt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 25 May 2008 15:15:41 +0200 Source: vlock Binary: vlock Architecture: source i386 Version: 2.2.2-1 Distribution: unstable Urgency: low Maintainer: Alexander Wirt [EMAIL PROTECTED] Changed-By: Alexander Wirt [EMAIL PROTECTED]

Accepted cxxtools 1.4.8-2 (source i386)

2008-06-16 Thread Kari Pahula
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 12:24:28 +0300 Source: cxxtools Binary: libcxxtools6 libcxxtools-dev Architecture: source i386 Version: 1.4.8-2 Distribution: unstable Urgency: low Maintainer: Kari Pahula [EMAIL PROTECTED] Changed-By: Kari Pahula

Accepted tntdb 1.0.1-1 (source i386)

2008-06-16 Thread Kari Pahula
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 12:12:24 +0300 Source: tntdb Binary: libtntdb1 tntdb-mysql1 tntdb-postgresql1 tntdb-sqlite1 libtntdb-dev Architecture: source i386 Version: 1.0.1-1 Distribution: unstable Urgency: low Maintainer: Kari Pahula [EMAIL

Accepted molphy 2.3b3-5 (source i386)

2008-06-16 Thread Andreas Tille
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:31:02 +0200 Source: molphy Binary: molphy Architecture: source i386 Version: 2.3b3-5 Distribution: unstable Urgency: low Maintainer: Debian-Med Packaging Team [EMAIL PROTECTED] Changed-By: Andreas Tille [EMAIL

Accepted sendfile 2.1b.20080311-2 (source i386)

2008-06-16 Thread Joey Schulze
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:41:30 +0200 Source: sendfile Binary: sendfile Architecture: source i386 Version: 2.1b.20080311-2 Distribution: unstable Urgency: low Maintainer: Martin Schulze [EMAIL PROTECTED] Changed-By: Joey Schulze [EMAIL

Accepted gerstensaft 0.3-4 (source i386)

2008-06-16 Thread Joey Schulze
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:46:23 +0200 Source: gerstensaft Binary: gerstensaft Architecture: source i386 Version: 0.3-4 Distribution: unstable Urgency: low Maintainer: Martin Schulze [EMAIL PROTECTED] Changed-By: Joey Schulze [EMAIL

Accepted xenomai 2.4.4-3 (source all i386)

2008-06-16 Thread Roland Stigge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:44:01 +0200 Source: xenomai Binary: xenomai-runtime linux-patch-xenomai libxenomai1 libxenomai-dev xenomai-doc Architecture: source all i386 Version: 2.4.4-3 Distribution: unstable Urgency: low Maintainer: Roland

Accepted dia 0.96.1-7 (source all i386)

2008-06-16 Thread Roland Stigge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 10 Jun 2008 11:32:13 +0200 Source: dia Binary: dia-common dia-libs dia dia-gnome Architecture: source all i386 Version: 0.96.1-7 Distribution: unstable Urgency: low Maintainer: Debian Dia Team [EMAIL PROTECTED] Changed-By:

Accepted apt-build 0.12.34 (source amd64)

2008-06-16 Thread Julien Danjou
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:55:00 +0200 Source: apt-build Binary: apt-build Architecture: source amd64 Version: 0.12.34 Distribution: unstable Urgency: low Maintainer: Julien Danjou [EMAIL PROTECTED] Changed-By: Julien Danjou [EMAIL

Accepted mirage 0.9.3-2 (source powerpc)

2008-06-16 Thread Xavier Oswald
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:35:12 +0200 Source: mirage Binary: mirage Architecture: source powerpc Version: 0.9.3-2 Distribution: unstable Urgency: low Maintainer: Xavier Oswald [EMAIL PROTECTED] Changed-By: Xavier Oswald [EMAIL PROTECTED]

Accepted babl 0.0.22-1 (source all i386)

2008-06-16 Thread Ross Burton
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:32:54 +0100 Source: babl Binary: libbabl-0.0-0 libbabl-0.0-0-dev libbabl-0.0-doc Architecture: source all i386 Version: 0.0.22-1 Distribution: unstable Urgency: low Maintainer: Ross Burton [EMAIL PROTECTED]

Accepted tagcoll2 2.0.11-1 (source amd64)

2008-06-16 Thread Enrico Zini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:15:01 +0100 Source: tagcoll2 Binary: tagcoll libtagcoll2-dev Architecture: source amd64 Version: 2.0.11-1 Distribution: unstable Urgency: low Maintainer: Enrico Zini [EMAIL PROTECTED] Changed-By: Enrico Zini

Accepted dnsmasq 2.42-3 (source all i386)

2008-06-16 Thread Simon Kelley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2008 11:26:20 + Source: dnsmasq Binary: dnsmasq dnsmasq-base Architecture: source all i386 Version: 2.42-3 Distribution: unstable Urgency: low Maintainer: Simon Kelley [EMAIL PROTECTED] Changed-By: Simon Kelley [EMAIL

Accepted kdeedu 4:4.0.82+svn819867-1 (source all amd64 i386)

2008-06-16 Thread Ana Beatriz Guerrero Lopez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 08:53:40 +0200 Source: kdeedu Binary: kdeedu kdeedu-dbg blinken kalgebra kalzium kalzium-data kanagram kbruch kgeography kgeography-data khangman kig kiten klettres klettres-data kmplot kpercentage kstars

Accepted ntp 1:4.2.4p4+dfsg-6 (source all i386)

2008-06-16 Thread Peter Eisentraut
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 12:55:54 +0200 Source: ntp Binary: ntp ntpdate ntp-doc Architecture: source all i386 Version: 1:4.2.4p4+dfsg-6 Distribution: unstable Urgency: low Maintainer: Debian NTP Team [EMAIL PROTECTED] Changed-By: Peter

Accepted kdegames 4:4.0.82+svn819867-1 (source all amd64 i386)

2008-06-16 Thread Ana Beatriz Guerrero Lopez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 08:57:38 +0200 Source: kdegames Binary: kdegames libkdegames4 kdegames-dbg libkdegames-dev kdegames-card-data kdegames-mahjongg-data bovo katomic kbattleship kblackbox kbounce kdiamond kgoldrunner kiriki

Accepted gcj-4.2 4.2.4-2 (source all i386)

2008-06-16 Thread Matthias Klose
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 13 Jun 2008 18:03:40 +0200 Source: gcj-4.2 Binary: gcj-4.2-base gcj-4.2 gij-4.2 libgcj8-1 libgcj8-jar libgcj8-1-awt gappletviewer-4.2 libgcj8-dev libgcj8-dbg libgcj8-src Architecture: source all i386 Version: 4.2.4-2

Accepted pycurl 7.18.2-1 (source amd64)

2008-06-16 Thread Bernd Zeimetz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 13:15:53 +0200 Source: pycurl Binary: python-pycurl python-pycurl-dbg Architecture: source amd64 Version: 7.18.2-1 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team [EMAIL PROTECTED]

Accepted ncurses-ruby 1.1-3 (source all amd64)

2008-06-16 Thread Michael Ablassmeier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 13:09:18 +0200 Source: ncurses-ruby Binary: libncurses-ruby libncurses-ruby1.8 libncurses-ruby1.9 Architecture: source all amd64 Version: 1.1-3 Distribution: unstable Urgency: high Maintainer: [EMAIL PROTECTED]

Accepted pngcheck 2.0.0-1.1 (source amd64)

2008-06-16 Thread Marco Rodrigues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Jun 2008 21:04:57 +0100 Source: pngcheck Binary: pngcheck Architecture: source amd64 Version: 2.0.0-1.1 Distribution: unstable Urgency: low Maintainer: Lucas Wall [EMAIL PROTECTED] Changed-By: Marco Rodrigues [EMAIL

Accepted xserver-xorg-video-nsc 1:2.8.3-4 (source i386)

2008-06-16 Thread Brice Goglin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 14:10:24 +0200 Source: xserver-xorg-video-nsc Binary: xserver-xorg-video-nsc Architecture: source i386 Version: 1:2.8.3-4 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force [EMAIL PROTECTED]

Accepted syslinux 2:3.70~pre18+dfsg-1 (source i386)

2008-06-16 Thread Daniel Baumann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 12:43:00 +0200 Source: syslinux Binary: syslinux Architecture: source i386 Version: 2:3.70~pre18+dfsg-1 Distribution: experimental Urgency: low Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann

Accepted scmxx 0.9.0-2.1 (source i386)

2008-06-16 Thread Peter Eisentraut
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 14:14:14 +0200 Source: scmxx Binary: scmxx Architecture: source i386 Version: 0.9.0-2.1 Distribution: unstable Urgency: low Maintainer: Michael Banck [EMAIL PROTECTED] Changed-By: Peter Eisentraut [EMAIL PROTECTED]

Accepted apt-build 0.12.35 (source amd64)

2008-06-16 Thread Julien Danjou
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 14:33:15 +0200 Source: apt-build Binary: apt-build Architecture: source amd64 Version: 0.12.35 Distribution: unstable Urgency: low Maintainer: Julien Danjou [EMAIL PROTECTED] Changed-By: Julien Danjou [EMAIL

Accepted munin 1.2.6-1 (source all)

2008-06-16 Thread Holger Levsen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 11 May 2008 22:42:14 +0200 Source: munin Binary: munin-node munin-plugins-contrib munin Architecture: source all Version: 1.2.6-1 Distribution: unstable Urgency: low Maintainer: Munin Debian Maintainers [EMAIL PROTECTED]

Accepted ruby-pkg-tools 0.14 (source all)

2008-06-16 Thread Lucas Nussbaum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 14:27:09 +0200 Source: ruby-pkg-tools Binary: ruby-pkg-tools Architecture: source all Version: 0.14 Distribution: unstable Urgency: high Maintainer: Paul van Tilburg [EMAIL PROTECTED] Changed-By: Lucas Nussbaum

Accepted pidgin-lastfm 0.3b-1 (source all)

2008-06-16 Thread Jan Hauke Rahm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Jun 2008 18:00:12 +0200 Source: pidgin-lastfm Binary: pidgin-lastfm Architecture: source all Version: 0.3b-1 Distribution: unstable Urgency: low Maintainer: Jan Hauke Rahm [EMAIL PROTECTED] Changed-By: Jan Hauke Rahm [EMAIL

Accepted minisat2 070721-2 (source i386)

2008-06-16 Thread Michael Tautschnig
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 12:51:36 + Source: minisat2 Binary: minisat2 Architecture: source i386 Version: 070721-2 Distribution: unstable Urgency: low Maintainer: Michael Tautschnig [EMAIL PROTECTED] Changed-By: Michael Tautschnig [EMAIL

Accepted matrixssl 1.8.5-1 (source all)

2008-06-16 Thread Gerrit Pape
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Jun 2008 18:29:35 + Source: matrixssl Binary: libmatrixssl1.8-dev libmatrixssl1.8 libmatrixssl1.8-doc Architecture: all source Version: 1.8.5-1 Distribution: unstable Urgency: low Maintainer: Gerrit Pape [EMAIL PROTECTED]

Accepted python-pysnmp4-mibs 0.0.5a-3 (source all)

2008-06-16 Thread Arnaud Fontaine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 19:01:48 +0900 Source: python-pysnmp4-mibs Binary: python-pysnmp4-mibs Architecture: source all Version: 0.0.5a-3 Distribution: unstable Urgency: low Maintainer: Jan Lübbe [EMAIL PROTECTED] Changed-By: Arnaud

Accepted libopenusb 1.0.1-3 (source all powerpc)

2008-06-16 Thread Simon Richter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 15:19:42 +0200 Source: libopenusb Binary: libopenusb-dev libopenusb-doc Architecture: source all powerpc Version: 1.0.1-3 Distribution: unstable Urgency: low Maintainer: Simon Richter [EMAIL PROTECTED] Changed-By:

Accepted libtext-template-perl 1.44-1.2 (source all)

2008-06-16 Thread Thijs Kinkhorst
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Jun 2008 18:11:52 +0200 Source: libtext-template-perl Binary: libtext-template-perl Architecture: source all Version: 1.44-1.2 Distribution: unstable Urgency: high Maintainer: Scott M. Dier [EMAIL PROTECTED] Changed-By: Thijs

Accepted samba4 4.0.0~alpha4~20080615-1 (source amd64)

2008-06-16 Thread Jelmer Vernooij
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 14 Jun 2008 20:39:13 +0200 Source: samba4 Binary: samba4 samba4-common samba4-clients samba4-testsuite registry-tools libparse-pidl-perl samba4-dev samba-ldb-tools libldb-samba4-dev libldb-samba4-0 libgensec0 libgensec-dev

Accepted krb5 1.6.dfsg.4~beta1-2 (source all i386)

2008-06-16 Thread Sam Hartman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jun 2008 09:29:00 -0400 Source: krb5 Binary: libkadm55 libkrb53 krb5-user krb5-clients krb5-rsh-server krb5-ftpd krb5-telnetd krb5-kdc krb5-kdc-ldap krb5-admin-server libkrb5-dev libkrb5-dbg krb5-pkinit krb5-doc

Accepted xserver-xorg-video-geode 2.10.0-2 (source i386)

2008-06-16 Thread Martin-Éric Racine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 14:49:38 +0300 Source: xserver-xorg-video-geode Binary: xserver-xorg-video-geode xserver-xorg-video-geode-dbg xserver-xorg-video-amd xserver-xorg-video-amd-dbg Architecture: source i386 Version: 2.10.0-2

Accepted mauve 20080616-1 (source all)

2008-06-16 Thread Matthias Klose
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 16:29:03 +0200 Source: mauve Binary: mauve Architecture: source all Version: 20080616-1 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Matthias Klose [EMAIL

Accepted ardour 1:2.4.1-2 (source amd64)

2008-06-16 Thread Free Ekanayaka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 14:44:48 +0100 Source: ardour Binary: ardour ardour-altivec ardour-i686 Architecture: source amd64 Version: 1:2.4.1-2 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Team [EMAIL PROTECTED]

Accepted ftgl 2.1.3~rc5-2 (source all amd64)

2008-06-16 Thread Debian packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 14:32:00 + Source: ftgl Binary: libftgl-dev libftgl2 ftgl-dev Architecture: source all amd64 Version: 2.1.3~rc5-2 Distribution: unstable Urgency: low Maintainer: Sam Hocevar (Debian packages) [EMAIL PROTECTED]

Accepted specimen 0.5.2rc3-1.1 (source i386)

2008-06-16 Thread Riku Voipio
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 17:07:53 +0300 Source: specimen Binary: specimen Architecture: source i386 Version: 0.5.2rc3-1.1 Distribution: unstable Urgency: low Maintainer: Eduardo Marcel Macan [EMAIL PROTECTED] Changed-By: Riku Voipio [EMAIL

Accepted intercal 28:0.28-4 (source powerpc)

2008-06-16 Thread Albin Tonnerre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 15:30:31 +0200 Source: intercal Binary: intercal Architecture: source powerpc Version: 28:0.28-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Albin Tonnerre [EMAIL

Accepted shoes 0.r396-4 (source amd64)

2008-06-16 Thread Bram Senders
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Jun 2008 09:46:18 +0200 Source: shoes Binary: shoes Architecture: source amd64 Version: 0.r396-4 Distribution: unstable Urgency: low Maintainer: Bram Senders [EMAIL PROTECTED] Changed-By: Bram Senders [EMAIL PROTECTED]

Accepted gegl 0.0.18-1 (source all i386)

2008-06-16 Thread Ross Burton
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 11:45:24 +0100 Source: gegl Binary: gegl libgegl-0.0-0 libgegl-0.0-dev libgegl-0.0-doc Architecture: source all i386 Version: 0.0.18-1 Distribution: unstable Urgency: low Maintainer: Ross Burton [EMAIL PROTECTED]

Accepted xuxen-eu-spell 0.3.20070215b-3 (source all)

2008-06-16 Thread Agustin Martin Domingo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 16 Jun 2008 13:38:15 +0200 Source: xuxen-eu-spell Binary: myspell-eu-es hunspell-eu-es aspell-eu-es Architecture: source all Version: 0.3.20070215b-3 Distribution: unstable Urgency: low Maintainer: Agustin Martin Domingo [EMAIL

  1   2   >