date:20080515

On Thursday 15 May 2008 11:24, Olivier Berger wrote:
 I guess openssh-blacklist is only available on stable/updates and not in
 testing/updates ... any reason why not ?

It is currently available in unstable; I have no doubt that the release 
managers will push it into testing as soon as possible.


Thijs


pgpoyuPFMZko4.pgp
Description: PGP signature

acpid package needs love and an active maintainer

2008-05-15 Thread Raphael Hertzog

Hello,

I just reassigned a bug to acpid and discovered how badly maintained it
is. Despite a new maintainer in january this year, the BTS still shows
many RC bugs and a bunch with patches.

Hopefully this mail will draw some attention to the problem and some
volunteers will step up to help maintain this package.

http://packages.qa.debian.org/a/acpid.html

Jose, I see you have many other packages. Please don't pick up important
packages if you don't have the time or the motivation to bring them back
in a good shape. And if you see that you don't cope, please look for help
and/or orphan some of your packages (I see several with new upstream
versions and quite a few that were NMUed, probably due to lack of action
on your part).

http://qa.debian.org/[EMAIL PROTECTED]

Cheers,
-- 
Raphaël Hertzog

Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

openssh-blacklist for testing-updates ?

2008-05-15 Thread Olivier Berger

Hi.

I guess openssh-blacklist is only available on stable/updates and not in
testing/updates ... any reason why not ?

Thanks in advance.

-- 
Olivier BERGER [EMAIL PROTECTED] (*NEW ADDRESS*)
http://www-inf.it-sudparis.eu/~olberger/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM / TELECOM  Management SudParis (http://www.it-sudparis.eu/), 
Evry



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: db.debian.org/password.html : Why ~/.ssh/id_dsa.pub to setup OpenSSH for RSA

2008-05-15 Thread Osamu Aoki

Hi,

Considering recent issues,  http://db.debian.org/password.html requires
updated as s/id_dsa.pub/id_rsa.pub/.

Discussion as below.  Do I need to make rt thingy?  I am not yet
familiar with it.

On Wed, May 14, 2008 at 07:50:29PM +0200, Luk Claes wrote:
 Osamu Aoki wrote:
  Hi,
  
  Recent openssl issue lead me to http://db.debian.org/password.html and
  made me wonder why script example uses DSA key while main text only
  talks about RSA key.
 
 The text talks about RSA keys as they are preferred over DSA keys.
 
  | Alternatively, you can do without a password and use PGP to manipulate 
  your
  | LDAP information through the mail gateway and use SSH RSA Authentication 
  to
  | access the servers. To setup OpenSSH for RSA you need to first generate a
  | private RSA key using ssh-keygen and select a good passphrase for it. 
  Then send
  | the public portion of the key to the LDAP directory:
  | 
  | gpg --clearsign  ~/.ssh/id_dsa.pub | mail [EMAIL PROTECTED]
  | 
  | NB: Only version 2 RSA keys are accepted. Version 1 RSA keys (i.e. 
  identity.pub
  | files) will not work.
  
  
  If main text is s/RSA/RSA\/DSA/g , I understand script example but ...
  
  Is there any reason to use DSA key insted of RSA key(~/.ssh/id_rsa.pub) ?
 
 On the contrary, it's better to use RSA keys as they can be bigger and
 are faster.

Ok,  

With today's announcement on Alioth and SSH by Roland Mas made me to use
RSA anyway.

FYI:

| From: [EMAIL PROTECTED]
| Subject: Mail Gateway failed: Message is not PGP signed:
| To: [EMAIL PROTECTED]
| Date: Thu, 15 May 2008 12:29:33 +
| 
| Hello!
| 
| Your request to the mail gateway is malformed, or an internal processing
| error occured. The information below may help you, or the gateway
| administrator to identify the problem.
| 
| Error: Message is not PGP signed:
| == Message Error: No PGP signature
| 
| 
| Please email [EMAIL PROTECTED] if you have any questions.
 

This is what I got for me sending DSA key.  


After sending RSA key, I got:
| From: [EMAIL PROTECTED]
| Subject: DB Change Request
| To: Osamu Aoki [EMAIL PROTECTED]
| Date: Thu, 15 May 2008 12:29:49 +
| 
| Hello Osamu Aoki [EMAIL PROTECTED]!
| 
| Your request to change your directory information has been processed.
| Note that there is a propagation time for many of the entries so please
| be patient. Here are the results:
| 
|  ssh-rsa
| ...

So this page needs to be updated.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

ssl security desaster (was: Re: SSH keys: DSA vs RSA)

2008-05-15 Thread Martin Uecker

Steinar H. Gunderson [EMAIL PROTECTED]:
 On Thu, May 15, 2008 at 05:11:27AM +0200, Goswin von Brederlow wrote:


  Also if you have 2 messages signed with the same random number you can
  compute the secret key. It is more complicated then this but
  simplified boils down to is computing k given (k + r) * Message1 ==
  Signature1 and (k + r) * Message2 == Signature2.

 For the details, since everyone doesn't read Planet Debian:

  http://blog.sesse.net/blog/tech/2008-05-14-17-21_some_maths

 /* Steinar */


If I understand this correctly, this means that not only should keys
generated with the broken ssl lib be considered compromised, but all
keys which were potentially used to create DSA signatures by those
broken libs.

In this case, the security advisory should clearly be updated. And
all advise about searching for weak keys should be removed as well,
because it leads to false sense of security. In fact, *all* keys used
on Debian machines should be considered compromised.

I also wonder, what will the Debian community change in their
processes to make such a security desaster less likely in the
future?


Martin







-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

On Thursday 15 May 2008 14:04, Martin Uecker wrote:
 If I understand this correctly, this means that not only should keys
 generated with the broken ssl lib be considered compromised, but all
 keys which were potentially used to create DSA signatures by those
 broken libs.

 In this case, the security advisory should clearly be updated. 

The original advisory has this text:
Furthermore, all DSA keys ever used on affected Debian systems for signing or 
authentication purposes should be considered compromised; the Digital 
Signature Algorithm relies on a secret random value used during signature 
generation.

I read there exactly the thing you describe above. What is your suggestion?

 And all advise about searching for weak keys should be removed as well,
 because it leads to false sense of security. In fact, *all* keys used
 on Debian machines should be considered compromised.

The reasoning above does not go for the more common RSA keys, so this advice 
would not be appropriate I think.

 I also wonder, what will the Debian community change in their
 processes to make such a security desaster less likely in the
 future?

You mean less likely than once in 15 years? We're open to your suggestions.


Thijs


pgpyhLOdSozzB.pgp
Description: PGP signature

Re: db.debian.org/password.html : Why ~/.ssh/id_dsa.pub to setup OpenSSH for RSA

2008-05-15 Thread Peter Palfrader

On Thu, 15 May 2008, Osamu Aoki wrote:

 Considering recent issues,  http://db.debian.org/password.html requires
 updated as s/id_dsa.pub/id_rsa.pub/.

My mail to d-i-a said that you need to use RSA keys.  You have read
that, right?

The page on db.d.o will get updated eventually, for now think of it as
You need to be at least this smart to get your key into LDAP.

weasel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: conglomeration packages (Re: Will nvidia-graphics-drivers ever transition to testing?)

2008-05-15 Thread Lennart Sorensen

On Wed, May 14, 2008 at 08:13:53PM -0400, Filipus Klutiero wrote:
 Your second parenthesis is wrong. Just like LKM-s when the stock kernels' 
 ABINAME is bumped, applications need to be rebuilt when the ABI of one of the 
 libraries they link to changes in a way which is not backwards-compatible. 
 You can check http://wiki.debian.org/OngoingTransitions for examples of 
 library transitions.

The old libraries don't go away right away though.  With the kernel you
can only be running one at a time, so you have to recompile the modules
to make them work.  libraries also change ABI versions a lot less often
than the kernel changes.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Is sbackup maintained? If not, what to do?

2008-05-15 Thread Charles Plessy

Dear all,

it is almost one year that sbackup was modified to use a group ID that
exists on Ubuntu but not on Debian systems. As suggested on
[EMAIL PROTECTED], I have increased the severity of the bug to
'serious' three weeks ago. (#427697)

sbackup is a native Debian package whose maintainer is also upstream
developper. As a native package, it is translated by Debian voluteers,
whose work is ignored by the maintainer. (#431936)

The homepage of sbackup has not been updated recently, except by
spammers (http://sbackup.sourceforge.net/RecentChanges).

Despite the fact that the maintainer of sbackup is actively blogging on
planet.d.o, I wonder if sbackup is maintained. From a user perspective
(and I am a user of sbackup, that is why I feel concerned), I think that
if there is no future for sbackup, it can be discussed wether it is
better to remove it and save volunteer time to fix other bugs than the
ones of sbackup.

Have a nice day,

-- 
Charles Plessy
http://charles.plessy.org
Wakō, Saitama, Japan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: db.debian.org/password.html : Why ~/.ssh/id_dsa.pub to setup OpenSSH for RSA

2008-05-15 Thread Osamu Aoki

On Thu, May 15, 2008 at 03:03:55PM +0200, Peter Palfrader wrote:
 On Thu, 15 May 2008, Osamu Aoki wrote:
 
  Considering recent issues,  http://db.debian.org/password.html requires
  updated as s/id_dsa.pub/id_rsa.pub/.
 
 My mail to d-i-a said that you need to use RSA keys.  You have read
 that, right?

Yes.

 The page on db.d.o will get updated eventually, for now think of it as
 You need to be at least this smart to get your key into LDAP.

Good.  

I tried DSA key before you send the mail though :-)

Osamu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl problems: gpg affected?

2008-05-15 Thread Florian Weimer

* Michal Čihař:

 GnuPG does not use OpenSSL, so it should be safe. But generally it
 could be possible to use same key for both GnuPG and OpenSSL and then
 you would have a problem.

There is no benefit from doing that, so this is highly unlikely.  It
requires manual key conversion, too.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [DSA 1571-1] Heimdal

2008-05-15 Thread Guido Günther

Hi Brian,
On Thu, May 15, 2008 at 03:33:41PM +1000, Brian May wrote:
 Apparently, Heimdal in Debian also is affected. I am not aware of any  
 solution other then to manually regenerate all keys.
Could you give some details here? Password based principals aren't
affected? For those using a keytabs ktutil -k keytab change; ktutil -k
purge --age=short is sufficient?
Cheers,
 -- Guido


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster

Martin Uecker [EMAIL PROTECTED] writes:

 In this case, the security advisory should clearly be updated. And all
 advise about searching for weak keys should be removed as well, because
 it leads to false sense of security. In fact, *all* keys used on Debian
 machines should be considered compromised.

All *DSA* keys.  RSA keys do not have the same problem, as I understand
it.

-- 
Russ Allbery ([EMAIL PROTECTED])   http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [DSA 1571-1] Heimdal

Guido Günther [EMAIL PROTECTED] writes:
 On Thu, May 15, 2008 at 03:33:41PM +1000, Brian May wrote:

 Apparently, Heimdal in Debian also is affected. I am not aware of any
 solution other then to manually regenerate all keys.

 Could you give some details here? Password based principals aren't
 affected?

Password-based principals are not affected.  No randomness is used in
generating those keys; the secure material is the password itself, which
is run through a hash algorithm.  Only randomly generated keys (generally
the keys you put into keytabs, but also randomized user principals if you
have any) are affected.

 For those using a keytabs ktutil -k keytab change; ktutil -k purge
 --age=short is sufficient?

That looks right to me, although take that with a grain of salt since I
use MIT personally and am not that familiar with the Heimdal ktutil
command syntax.

-- 
Russ Allbery ([EMAIL PROTECTED])   http://www.eyrie.org/~eagle/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: db.debian.org/password.html : Why ~/.ssh/id_dsa.pub to setup OpenSSH for RSA

2008-05-15 Thread Mike Hommey

On Thu, May 15, 2008 at 03:03:55PM +0200, Peter Palfrader [EMAIL PROTECTED] 
wrote:
 On Thu, 15 May 2008, Osamu Aoki wrote:
 
  Considering recent issues,  http://db.debian.org/password.html requires
  updated as s/id_dsa.pub/id_rsa.pub/.
 
 My mail to d-i-a said that you need to use RSA keys.  You have read
 that, right?

This mail should have been sent to d-d-a, really.

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

2008-05-15 Thread Martin Uecker

Am Donnerstag, den 15.05.2008, 15:20 +0200 schrieb Thijs Kinkhorst:
 On Thursday 15 May 2008 14:04, Martin Uecker wrote:
  If I understand this correctly, this means that not only should keys
  generated with the broken ssl lib be considered compromised, but all
  keys which were potentially used to create DSA signatures by those
  broken libs.
 
  In this case, the security advisory should clearly be updated. 
 
 The original advisory has this text:
 Furthermore, all DSA keys ever used on affected Debian systems for signing 
 or 
 authentication purposes should be considered compromised; the Digital 
 Signature Algorithm relies on a secret random value used during signature 
 generation.
 
 I read there exactly the thing you describe above. What is your suggestion?

I missed this, sorry. The advisory for ssh does not include this
information. Is this not relevant for ssh for some reason?

To be clear, I have been quite impressed by the professional reaction to
this (and other) security problems. But it still would like to see some
more information here. (Which might already be in the works.)

  And all advise about searching for weak keys should be removed as well,
  because it leads to false sense of security. In fact, *all* keys used
  on Debian machines should be considered compromised.
 
 The reasoning above does not go for the more common RSA keys, so this advice 
 would not be appropriate I think.

Ok.

  I also wonder, what will the Debian community change in their
  processes to make such a security desaster less likely in the
  future?
 
 You mean less likely than once in 15 years? We're open to your suggestions.

Something as bad as this might be rare, still, if something can be
improved, it should.

Upstream complained about the extensive Debian patching. I think this
is a valid criticism.

For security sensitive packages, requiring changes to be signed-off
by a second person might be a good idea too.

Another problem I have argued about before, not directly related to this
incident, but IMHO another desaster waiting to happen: There is no
way to independetly validate that a debian binary package was
created from the corresponding source.

What bothers me too is the fact that the installer scripts of 
all packages have root permissions during installation. While
this might be hard to do, in principle I see no good reason
why installer scripts could not be limited to certain tasks.


Martin













-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: db.debian.org/password.html : Why ~/.ssh/id_dsa.pub to setup OpenSSH for RSA

2008-05-15 Thread Peter Palfrader

On Thu, 15 May 2008, Mike Hommey wrote:

 On Thu, May 15, 2008 at 03:03:55PM +0200, Peter Palfrader [EMAIL PROTECTED] 
 wrote:
  On Thu, 15 May 2008, Osamu Aoki wrote:
  
   Considering recent issues,  http://db.debian.org/password.html requires
   updated as s/id_dsa.pub/id_rsa.pub/.
  
  My mail to d-i-a said that you need to use RSA keys.  You have read
  that, right?
 
 This mail should have been sent to d-d-a, really.

No.  the original mail to d-d-a explicitly said that all future mails,
especially this, will be posted to d-i-a.

dia is the correct mailinglist for this.

weasel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: db.debian.org/password.html : Why ~/.ssh/id_dsa.pub to setup OpenSSH for RSA

2008-05-15 Thread Mike Hommey

On Thu, May 15, 2008 at 05:11:30PM +0200, Peter Palfrader [EMAIL PROTECTED] 
wrote:
 On Thu, 15 May 2008, Mike Hommey wrote:
 
  On Thu, May 15, 2008 at 03:03:55PM +0200, Peter Palfrader [EMAIL 
  PROTECTED] wrote:
   On Thu, 15 May 2008, Osamu Aoki wrote:
   
Considering recent issues,  http://db.debian.org/password.html requires
updated as s/id_dsa.pub/id_rsa.pub/.
   
   My mail to d-i-a said that you need to use RSA keys.  You have read
   that, right?
  
  This mail should have been sent to d-d-a, really.
 
 No.  the original mail to d-d-a explicitly said that all future mails,
 especially this, will be posted to d-i-a.
 
 dia is the correct mailinglist for this.

I beg to differ. This particular mail is important enough to be sent to
d-d-a instead of d-i-a.

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: db.debian.org/password.html : Why ~/.ssh/id_dsa.pub to setup OpenSSH for RSA

2008-05-15 Thread Norbert Preining

On Do, 15 Mai 2008, Mike Hommey wrote:
 I beg to differ. This particular mail is important enough to be sent to
 d-d-a instead of d-i-a.

I agree, dia is not what I would be subscribed to under normal
circumstances, and with all the caos that type of announce is for dda.

Best wishes

Norbert

---
Dr. Norbert Preining [EMAIL PROTECTED]Vienna University of Technology
Debian Developer [EMAIL PROTECTED] Debian TeX Group
gpg DSA: 0x09C5B094  fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
---
BISHOP'S CAUNDLE
An opening gambit before a game of chess whereby the missing pieces
are replaced by small ornaments from the mantelpiece.
--- Douglas Adams, The Meaning of Liff


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

On Thursday 15 May 2008 16:47, Martin Uecker wrote:
  You mean less likely than once in 15 years? We're open to your
  suggestions.

 Something as bad as this might be rare, still, if something can be
 improved, it should.

 Upstream complained about the extensive Debian patching. I think this
 is a valid criticism.

Of course things can be improved, probably always. I don't think that just one 
incident means that nothing must be changed, but I also contest that this 
incident in and of itself requires changes to be made. One incident just 
doesn't tell us much about the quality of Debian patches in general, either 
way.

That's also what I dislike in Ben Laurie's blog post: he bases his conclusion 
on just this thing that indeed went horribly wrong, but is far from examplary 
for all patching that Debian, or distributions in general, do. I don't think 
he realises that far from all upstreams are as ideal as he seems to think.

I welcome change and review of our processes, but taking one extreme incident 
as the base on which to draw conclusions seems not the wise thing to do. If 
you're interested in for example changing the level to which software is 
patched in Debian, I suggest to start with a representative review of what 
gets patched and why it's done. That would give more base to see whether the 
extensive patching is indeed excessive.


cheers,
Thijs


pgpDorSiUyayM.pgp
Description: PGP signature

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

On Thu May 15 2008 06:20:10 Thijs Kinkhorst wrote:
 You mean less likely than once in 15 years? We're open to your suggestions.

Leaving millions of systems open to crackers for 2 years out of 15
is not a joke.  I don't blame the DD - we have all made mistakes
and most of us are lucky they weren't this serious - but we should
blame the process.  And fix it.

The notification process, with the fix in the archive long before
users were notified, failed to live up to Debian's usually high
standards.  The delay in getting some of the fixes into Testing
may also be an issue.

The rollout of information and updates was appalling - even adding in
the material from Ubuntu the information was piecemeal and inadequate
to properly secure systems within the limited time before crackers
might be expected to have exploits.

The vulnerability scanner didn't handle keys in many forms (e.g.
Apache keys) and gave false negatives because it doesn't use
~/.ssh/config to check the correct port in the common case where
ssh is running on a port other than 22.  In the wonderful light
of hindsight, it would probably have been better to devote less
effort to the scanner and more effort to documenting all the
kinds of key replacements that are needed, and to simply assume
that all keys are potentially compromised.

Serious efforts are needed on two fronts.  Second, we must ensure
that nothing like this ever happens again.  This calls for a thorough 
investigation and carefully updated policies and procedures.  It will
take a while to do properly.  It must be apparent to both the Debian
community and the world that the effort is authoritative, sincere,
and open.

But first we must carefully avoid any communication, however intended,
which might be construed as a flippant attitude to this disaster.

--Mike Bird


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

On Thu May 15 2008 08:33:54 Thijs Kinkhorst wrote:
 I welcome change and review of our processes, but taking one extreme
 incident as the base on which to draw conclusions seems not the wise thing
 to do. If you're interested in for example changing the level to which
 software is patched in Debian, I suggest to start with a representative
 review of what gets patched and why it's done. That would give more base to
 see whether the extensive patching is indeed excessive.

This is not the time to be making statements which will be regretted
later.

It only takes one incident as bad as this to compromise millions of
systems and to seriously harm Debian's reputation.  You can't average
out over all packages and say Debian is 99% secure.

99% secure is 100% insecure.

This incident needs to be reviewed carefully but the time is not yet.  
Information is not as accessible to Debian users as it should be and
some packages don't seem to have reached Testing.  Focus at this time
must still be on disaster response and recovery.

Next come the most important phases - learning from this disaster,
ensuring that a repetition is impossible (or several orders of magnitude
less likely), and preparing Debian's response for the next disaster.

--Mike Bird


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

2008-05-15 Thread Martin Uecker

Am Donnerstag, den 15.05.2008, 17:33 +0200 schrieb Thijs Kinkhorst:
 On Thursday 15 May 2008 16:47, Martin Uecker wrote:
   You mean less likely than once in 15 years? We're open to your
   suggestions.
 
  Something as bad as this might be rare, still, if something can be
  improved, it should.
 
  Upstream complained about the extensive Debian patching. I think this
  is a valid criticism.
 
 Of course things can be improved, probably always. I don't think that just 
 one 
 incident means that nothing must be changed, but I also contest that this 
 incident in and of itself requires changes to be made. One incident just 
 doesn't tell us much about the quality of Debian patches in general, either 
 way.

I don't question the quality of Debian patches in general. But I
still think that something can be learned from this single
incident. The security advantage of open source software 
is said to be: Many Eyes Make All Bugs Shallow! This of course
can not work if every distribution basically creates its own 
branch. 

 That's also what I dislike in Ben Laurie's blog post: he bases his conclusion 
 on just this thing that indeed went horribly wrong, but is far from examplary 
 for all patching that Debian, or distributions in general, do. I don't think 
 he realises that far from all upstreams are as ideal as he seems to think.

I am missing some self-criticism too. The use of uninitialized memory
should have been fixed upstream long ago. (And this is *not* a rare
case where the use of uninitialized memory is ok.)

 I welcome change and review of our processes, but taking one extreme incident 
 as the base on which to draw conclusions seems not the wise thing to do.

Why not? A plane crash is a very rare incident. Still every single
crash is investigated to make recommendations for their future
avoidance.

 If you're interested in for example changing the level to which software is 
 patched in Debian, I suggest to start with a representative review of what 
 gets patched and why it's done. That would give more base to see whether the 
 extensive patching is indeed excessive.

I do not have time to do statistics, but from looking at a lot of
packages over the years I know that their a many changes in Debian
packages which are not related to packaging. Besides security
fixes or other really important fixes which have to go in very fast,
I do not see no reason for all this Debian specific changes.

Martin






-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

On Thursday 15 May 2008 18:26, Martin Uecker wrote:
 Why not? A plane crash is a very rare incident. Still every single
 crash is investigated to make recommendations for their future
 avoidance.

Maybe that wasn't clear from my first mail, but I don't think that nothing can 
be learned from this incident (and already has been learned!). I just think 
that the conclusion that Debian patches too much is at all justified when 
looking solely at this bug.

  If you're interested in for example changing the level to which software
  is patched in Debian, I suggest to start with a representative review of
  what gets patched and why it's done. That would give more base to see
  whether the extensive patching is indeed excessive.

 I do not have time to do statistics, but from looking at a lot of
 packages over the years I know that their a many changes in Debian
 packages which are not related to packaging. Besides security
 fixes or other really important fixes which have to go in very fast,
 I do not see no reason for all this Debian specific changes.

I can understand that this doesn't seem necessary from the outside. However, 
I've been working on Debian for a few years now, and I've come to see that 
large numbers of patches are very justified. For example, because upstream 
isn't quite as cooperative, or even responds at all. Or because upstream is 
not interested in problems that affect Debian users specifically. There are 
many more examples, and probably also quite some counterexamples. There's a 
net win there, however.

Let me state it again, surely things can be learned from this incident, but 
the general conclusion that Debian patches too much is in my opinion far from 
justified. And I think it would be a good idea to get more overview of the 
reasons that these patches are applied before drawing the conclusion that 
it's a bad idea.


cheers,
Thijs


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

2008-05-15 Thread Kevin B. McCarty

Martin Uecker wrote:

 Am Donnerstag, den 15.05.2008, 17:33 +0200 schrieb Thijs Kinkhorst:

 If you're interested in for example changing the level to which software is 
 patched in Debian, I suggest to start with a representative review of what 
 gets patched and why it's done. That would give more base to see whether the 
 extensive patching is indeed excessive.
 
 I do not have time to do statistics, but from looking at a lot of
 packages over the years I know that their a many changes in Debian
 packages which are not related to packaging. Besides security
 fixes or other really important fixes which have to go in very fast,
 I do not see no reason for all this Debian specific changes.

If you see packages for which a Debian-specific patch seems unnecessary,
please by all means file a bug (severity wishlist) requesting that the
patch be either reverted or submitted upstream.  The worst that can
happen is that the bug will be ignored or closed with no reason given by
the maintainer.  More likely (at least I hope so), you'll either get an
explanation of why the patch is needed, or have your request to remove
the patch actually implemented.

Speaking only for myself, let me comment on some extensive patching.
I guess that some of my physics-related packages (cernlib, paw) are
among the more heavily patched in Debian.  Unfortunately upstream is
dead, so there is *no way* to see the patches incorporated there.  And
even before they gave up the ghost, they were very conservative,
refusing to consider most patches more complicated than trivial changes
to fix complete breakage.

The Debian-specific patches (which have also been incorporated into
Fedora's packages) incorporate things that upstream was unwilling to
include, such as:

- building shared libraries instead of only static ones
- support for architectures other than x86 and powerpc on Linux
- minimal 64-bit support
- support for newer compilers (gfortran instead of g77)
- fixes for bugs when programs were built against lesstif instead of
  the non-free OpenMotif (upstream did not see any reason to support
  lesstif)
- removal of non-free code, and fixing the build system to work
  around this removal

Believe me, there are lots of upstreams for which extensive patching
really is necessary.  (I have no idea whether OpenSSL is one of those,
as I have no familiarity with its code nor the Debian packaging of it.)

best regards,

-- 
Kevin B. McCarty [EMAIL PROTECTED]
WWW: http://www.starplot.org/
WWW: http://people.debian.org/~kmccarty/
GPG: public key ID 4F83C751



signature.asc
Description: OpenPGP digital signature

Re: ssl security desaster

2008-05-15 Thread Mikhail Gusarov

Twas brillig at 10:30:44 15.05.2008 UTC-07 when Kevin B. McCarty did gyre and 
gimble:

 KBM Believe me, there are lots of upstreams for which extensive
 KBM patching really is necessary.  (I have no idea whether OpenSSL is
 KBM one of those, as I have no familiarity with its code nor the
 KBM Debian packaging of it.)

Probably the work then should be clearly labeled as fork (especially
given the other distro maintainers also share some patches)? It will
reduce the confusion, like oh, erm, our foo is not quite upstream
foo, we rewrote it from scratch, and left the name and this cute
logo.

-- 


pgpFaI1HR5xJr.pgp
Description: PGP signature

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

2008-05-15 Thread Peter Samuelson


[Mike Bird]
 but we should blame the process.  And fix it.

 it would probably have been better to devote less effort to the
 scanner and more effort to documenting all the kinds of key
 replacements

 Serious efforts are needed

 Second, we must ensure

 This calls for a thorough investigation

 we must carefully avoid

Who is this we?  Whose serious efforts?  Who is investigating?  Most
importantly, should we assume that, as in the past, you, Mike Bird,
intend to do nothing but talk?
-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster

Mikhail Gusarov [EMAIL PROTECTED] writes:

 Probably the work then should be clearly labeled as fork (especially
 given the other distro maintainers also share some patches)? It will
 reduce the confusion, like oh, erm, our foo is not quite upstream
 foo, we rewrote it from scratch, and left the name and this cute
 logo.

I try to document any such modifications in README.Debian, particularly in
cases where upstream disagrees with a patch.

-- 
Russ Allbery ([EMAIL PROTECTED])   http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

On Thu May 15 2008 10:34:01 Peter Samuelson wrote:
 Who is this we?  Whose serious efforts?  Who is investigating?  Most
 importantly, should we assume that, as in the past, you, Mike Bird,
 intend to do nothing but talk?

Debian is still one of the world's best distros and I hope it
continues as such.  I use Debian on more systems than any other
distro.

Yet Debian makes it hard for people to help.  Like most software
engineers I simply don't have the time to waste on Debian's NM
process.  Debian's processes are indisputably Debian's decision
alone, but Debian has to live with the consequences ... falling
mindshare, orphaned packages, and slow releases.

Nevertheless, non-DD's can and do help by filing bug reports and
patches (upstream is best), helping people on d-u, and offering
constructive advice to DDs.  And one should not forget that most
of the software in Debian is developed and maintained by non-DD's.

--Mike Bird


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

2008-05-15 Thread Peter Samuelson


[Mike Bird]
 Nevertheless, non-DD's can and do help by filing bug reports and
 patches (upstream is best), helping people on d-u, and offering
 constructive advice to DDs.

Very well.  I propose that anyone who wishes to give constructive
advice to developers, but who doesn't actually do any of our
development work, should use the pronoun you rather than we.

This might make your posts sound like you're trying to boss us around
... but that's exactly what you're doing, so it's basically more
honest.  I prefer honest bossiness to implicit bossiness.
-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

2008-05-15 Thread Thibaut Paumard


Hi,

Le 15 mai 08 à 20:17, Mike Bird a écrit :


Nevertheless, non-DD's can and do help by filing bug reports and
patches (upstream is best), helping people on d-u, and offering
constructive advice to DDs.


And maintaining packages! It can be long to find a sponsor for your  
first package (especially if it's a very specialized software no DD  
uses), but you don't need to go through NM to become a (co-) 
maintainer. If you feel the itch, please step forward of adopt an  
orphaned package, as you noted there's a large pool to choose from.  
If you look a package with a request for help, you're sponsor is  
found already: your prospective comaintainer.


Besides, many packages are orphaned because they are obsolete. If  
nobody adopts them and they get too buggy, they'll be terminated  
eventually. The only alternative would be to remove them right away  
when the maintainer feels he doesn't care anymore, but this would be  
worse (unless the package was so obsolete that only the maintainer  
still used it).


Cheers, Thibaut (DM, not DD).


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster

2008-05-15 Thread Kevin B. McCarty

Hi Mikhail,

Mikhail Gusarov wrote:

 Twas brillig at 10:30:44 15.05.2008 UTC-07 when Kevin B. McCarty did gyre and 
 gimble:
 
  KBM Believe me, there are lots of upstreams for which extensive
  KBM patching really is necessary.  (I have no idea whether OpenSSL is
  KBM one of those, as I have no familiarity with its code nor the
  KBM Debian packaging of it.)
 
 Probably the work then should be clearly labeled as fork (especially
 given the other distro maintainers also share some patches)? It will
 reduce the confusion, like oh, erm, our foo is not quite upstream
 foo, we rewrote it from scratch, and left the name and this cute
 logo.

I'm not sure if you are addressing me specifically, or just maintainers
in general who have a large patch set.

I don't view my maintainership of cernlib, paw, etc. as a fork in the
same sense that, say, X.org is from XFree86 or Xemacs from Emacs.  (In
the most technical sense, *all* Debian packages are forks of upstream,
though in some happy cases the only difference is a little added
packaging infrastructure, and Debian users are generally aware of this.)
 My patches, if somewhat extensive, are still at most a few percent of
the total size of upstream's code, so there is no rewriting from scratch
going on.

I've also tried to make it very clear through README.Debian files, FAQ
web pages, etc. how the software in Debian behaves differently from
upstream's original version in the cases where the difference is visible
to the end user.

I have zero desire to be considered as cernlib upstream myself -- that
would imply that the software was supported at a level that I am not
able to guarantee.  If my upstream were to reanimate (or someone else
took over upstream), I'd happily continue to package new releases from
them, keeping any of my patch set that continued to be necessary that
they wouldn't themselves accept.

Mainly, I see my packaging of this software as a caretaker effort that
makes it possible for people to install it with a minimum of trouble,
while being able to expect that it follows Debian policy and has some
chance of getting fixes for reported bugs.  If some future change to the
operating system occurred that broke cernlib in a hard-to-fix way, I
would be much more likely to orphan the package and request its removal
from Debian than to try to make big changes to the architecture of the
software.  Doing the latter, IMO, *would* deserve to be called a real fork.

-- 
Kevin B. McCarty [EMAIL PROTECTED]
WWW: http://www.starplot.org/
WWW: http://people.debian.org/~kmccarty/
GPG: public key ID 4F83C751



signature.asc
Description: OpenPGP digital signature

Re: db.debian.org/password.html : Why ~/.ssh/id_dsa.pub to setup OpenSSH for RSA

2008-05-15 Thread Peter Palfrader

On Thu, 15 May 2008, Norbert Preining wrote:

 On Do, 15 Mai 2008, Mike Hommey wrote:
  I beg to differ. This particular mail is important enough to be sent to
  d-d-a instead of d-i-a.
 
 I agree, dia is not what I would be subscribed to under normal
 circumstances, and with all the caos that type of announce is for dda.

Which is why the initial mail about the issue went to both.  If you read
the first mail you will know where to find the rest.  If you can't be
bothered to read carefully when asked to (and lots can't) then I cannot
help you.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Sorting out mail-transport-agent mess

2008-05-15 Thread Sune Vuorela

Hi!

Noticing among others this bug report 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322751 and observing the 
many packages depending on $MTA | mail-transport-agent with $MTA having 
values like postfix, exim, exim4, sendmail, nullmailer and probably others. 
And some packages just depending on mail-transport-agent without providing a 
preferred.

The latter, just depending on mail-transport-agent, makes apt, at least 
currently, pick the package first in the alphabet providing m-t-a. (A bit 
ago, this was courier. now it is citadel). This definately needs fixing, but 
why not sort everything out while we are at it?

I think something needs to be done somewhere. There is several solutions, 
among others the following:

1) Exim4 is currently the default installed MTA. So any package requiring a 
MTA should depend on exim4 | mail-transport-agent. Defined by policy and all 
packages should be fixed to this.

2) Introduce a default-mta package (currently) depending on exim4. All 
packages requiring a MTA should depend on default-mta | mail-transport-agent.  
This will have the extra advantage that we (and others like CDDs and derived 
distros) easily could swap default MTA.

3) do the real ugly hack and invent a a-m-t-a depending on the default mta

Any comments? Depending on the outcome, I guess I will take this to 
either -policy or tech-ctte or wherever required.

And please please please. Don't take this into a flamewar about which MTA 
should be the one installed by default.

/Sune


Some stats:
$ grep-dctrl -FDepends -sDepends 
mail-transport-agent /var/lib/apt/lists/*unstable*Packages | 
sed -e's/Depends:\( .*,\)\?\([^,]*mail-transport-agent\).*/\2/' | sort | 
uniq -c
  6  exim | mail-transport-agent
135  exim4 | mail-transport-agent
  6  exim4 | postfix | sendmail | mail-transport-agent
  3  exim4-daemon-light | mail-transport-agent
 15  mail-transport-agent
  3  nullmailer | mail-transport-agent
 33  postfix | mail-transport-agent
  3  sendmail (= 8.9) | mail-transport-agent
  9  sendmail | mail-transport-agent
  3  sendmail | postfix | exim4 | mail-transport-agent
  6  sendmail-bin | mail-transport-agent
  3  ssmtp | mail-transport-agent
-- 
Genius, I cannot save on the kernel, how does it work?

From Excel 6.5 you can't reset the RO monitor, so that from Outlook 8.4.7 or 
from the control preferences menu inside MS-DOS you either must boot the 
processor to a firewall, or can never ping a login over a mousepad for 
exploring a serial IP desktop to a 2-bit 2D case of a computer on the memory 
on the secret code.


signature.asc
Description: This is a digitally signed message part.

Re: Sorting out mail-transport-agent mess

On Thu May 15 2008 14:33:04 Sune Vuorela wrote:
 The latter, just depending on mail-transport-agent, makes apt, at least
 currently, pick the package first in the alphabet providing m-t-a. (A bit
 ago, this was courier. now it is citadel). This definately needs fixing,
 but why not sort everything out while we are at it?

All of the MTA's provide mail-transport-agent.  I had assumed that apt
would choose between them on the basis that exim4-daemon-light is the
only provider with priority standard, the others being optional or extra.

If apt does not consider package priorities in resolving disjunctions,
a possible solution would be for apt to do so.

--Mike Bird


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: conglomeration packages (Re: Will nvidia-graphics-drivers ever transition to testing?)

2008-05-15 Thread Filipus Klutiero

Le May 15, 2008 09:55:40 am Lennart Sorensen, vous avez écrit :
 On Wed, May 14, 2008 at 08:13:53PM -0400, Filipus Klutiero wrote:
  Your second parenthesis is wrong. Just like LKM-s when the stock kernels'
  ABINAME is bumped, applications need to be rebuilt when the ABI of one of
  the libraries they link to changes in a way which is not
  backwards-compatible. You can check
  http://wiki.debian.org/OngoingTransitions for examples of library
  transitions.

 The old libraries don't go away right away though.  With the kernel you
 can only be running one at a time, so you have to recompile the modules
 to make them work.
I don't see your point.

 libraries also change ABI versions a lot less often 
 than the kernel changes.
We were talking about nvidia-graphics-drivers. Prebuilt nvidia LKM packages 
are already built by dedicated source packages.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Bug#427697: Is sbackup maintained? If not, what to do?

2008-05-15 Thread Aigars Mahinovs

2008/5/15 Charles Plessy [EMAIL PROTECTED]:
 Despite the fact that the maintainer of sbackup is actively blogging on
 planet.d.o, I wonder if sbackup is maintained. From a user perspective
 (and I am a user of sbackup, that is why I feel concerned), I think that
 if there is no future for sbackup, it can be discussed wether it is
 better to remove it and save volunteer time to fix other bugs than the
 ones of sbackup.

The upstream situation is not as clear cut - I've been making every
effort to a new and enthusiastic developer (Ouattara Oumar Aziz) take
over the upstream development of SBackup peacefully. I must say that
this process along with a partial rewrite of the software that Aziz
started even earlier might have turned out a bit more complex than he
expected. I on my part did not follow up on the fate of the upstream
development as much as I should have.

If you find this package important for you or your users and have some
time to provide a NMU, I would welcome that with open hands. Meanwhile
I am discussing the future of the SBackup software with Aziz and it
should see a revitalization that is rather common among free software
towards the summer.

Note: there have been a couple private emails on the same subject that
I have not answered yet, because the situation is not 100% certain,
but all patches, bug reports and translations will be acted upon
eventually. Help is welcome however.
-- 
Best regards,
 Aigars Mahinovs mailto:[EMAIL PROTECTED]
 #--#
 | .''`. Debian GNU/Linux LAKA |
 | : :' : http://www.debian.org  http://www.laka.lv |
 | `. `' |
 | `- |
 #--#


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

re: Sorting out mail-transport-agent mess

2008-05-15 Thread peter green

2) Introduce a default-mta package (currently) depending on exim4. All 
packages requiring a MTA should depend on default-mta | mail-transport-agent.  
This will have the extra advantage that we (and others like CDDs and derived 
distros) easily could swap default MTA.
What concerns me about this approach is that it could easilly end up with 
dist-upgrades swapping out users mail systems without warning. I would consider 
such behaviour unacceptable as it could easilly cause mail loss if the user has

a customised configuration.

It seems to me that the ideal soloution would be to fix apt/the repositry system
so that the defaults for a virtual package can be explicitly designed.

Failing that how about a default-mta virtual package that is provided by 
*exactly
one* real package. That way it is easy to change the default but upgrades should 
stay with the version that they have. Under that system changing the default MTA

would require changes to two packages which seems manageable to me.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Sorting out mail-transport-agent mess

peter green [EMAIL PROTECTED] writes:

 It seems to me that the ideal soloution would be to fix apt/the
 repositry system so that the defaults for a virtual package can be
 explicitly designed.

I have no idea how to do this and no time to help, but I think this would
be really cool and would solve a lot of annoying problems, particularly
around transitions of the default for some alternative.

-- 
Russ Allbery ([EMAIL PROTECTED])   http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Sorting out mail-transport-agent mess

On Thu, May 15, 2008 at 11:39:36PM +0100, peter green wrote:
 2) Introduce a default-mta package (currently) depending on exim4. All  
 packages requiring a MTA should depend on default-mta | 
 mail-transport-agent.  This will have the extra advantage that we (and 
 others like CDDs and derived distros) easily could swap default MTA.
 What concerns me about this approach is that it could easilly end up with 
 dist-upgrades swapping out users mail systems without warning. I would 
 consider such behaviour unacceptable as it could easilly cause mail loss 

Er, no, that wouldn't happen.  As long as packages correctly depend on
default-mta | mail-transport-agent, this will have no impact on upgrades.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Sorting out mail-transport-agent mess

2008-05-15 Thread Ben Finney

Mike Bird [EMAIL PROTECTED] writes:

 All of the MTA's provide mail-transport-agent.  I had assumed that apt
 would choose between them on the basis that exim4-daemon-light is the
 only provider with priority standard, the others being optional or extra.
 
 If apt does not consider package priorities in resolving disjunctions,
 a possible solution would be for apt to do so.

+1

This solution seems superior to my next choice, the introduction of a
'sensible-mta' package (to be used much as the OP's suggestion of
'default-mta').

-- 
 \   Ice Water? Get some onions - that'll make your eyes water!  |
  `\   -- Groucho Marx |
_o__)  |
Ben Finney


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Sorting out mail-transport-agent mess

On Thu, May 15, 2008 at 11:33:04PM +0200, Sune Vuorela wrote:

 Noticing among others this bug report 
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322751 and observing the 
 many packages depending on $MTA | mail-transport-agent with $MTA having 
 values like postfix, exim, exim4, sendmail, nullmailer and probably others. 
 And some packages just depending on mail-transport-agent without providing a 
 preferred.

 The latter, just depending on mail-transport-agent, makes apt, at least 
 currently, pick the package first in the alphabet providing m-t-a. (A bit 
 ago, this was courier. now it is citadel). This definately needs fixing, but 
 why not sort everything out while we are at it?

 I think something needs to be done somewhere. There is several solutions, 
 among others the following:

 1) Exim4 is currently the default installed MTA. So any package requiring a 
 MTA should depend on exim4 | mail-transport-agent. Defined by policy and all 
 packages should be fixed to this.

 2) Introduce a default-mta package (currently) depending on exim4. All 
 packages requiring a MTA should depend on default-mta | mail-transport-agent. 
  
 This will have the extra advantage that we (and others like CDDs and derived 
 distros) easily could swap default MTA.

I believe that 2) is the correct option, and can see no reason that it
shouldn't be implemented straight away.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Sorting out mail-transport-agent mess

2008-05-15 Thread Eugeniy Meshcheryakov

15 травня 2008 о 16:24 -0700 Steve Langasek написав(-ла):
  What concerns me about this approach is that it could easilly end up with 
  dist-upgrades swapping out users mail systems without warning. I would 
  consider such behaviour unacceptable as it could easilly cause mail loss 
 
 Er, no, that wouldn't happen.  As long as packages correctly depend on
 default-mta | mail-transport-agent, this will have no impact on upgrades.
 
This can happen if user has 'default-mta' package installed, and it
changes (if it is done like with 'gcc' package now).


signature.asc
Description: Digital signature

Re: Bug#427697: Is sbackup maintained? If not, what to do?

2008-05-15 Thread Charles Plessy

Le Fri, May 16, 2008 at 01:22:12AM +0300, Aigars Mahinovs a écrit :
 
 The upstream situation is not as clear cut - I've been making every
 effort to a new and enthusiastic developer (Ouattara Oumar Aziz) take
 over the upstream development of SBackup peacefully.

 I am discussing the future of the SBackup software with Aziz and it
 should see a revitalization that is rather common among free software
 towards the summer.

Hi Aigars, hi Aziz,

thanks for the update.

Since the revitalisation of sbackup is expected after the freezing of
Lenny, we have to solve the most important bugs of the current version
of sbackup. I do not know enough of python for helping on bug #427697
(the gid of the backups). If Aziz provides a patch, I can prepare a NMU
for this one, #479826 (using su-t-root-X as su wrapper) and #431936
(tranlations). I can also make the package non-native (as it has anyway
been suggested on this list for NMUs).

By the way, can somebody suggest an appropriate gid ?

Have a nice day,

-- 
Charles


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Sorting out mail-transport-agent mess

On Fri, May 16, 2008 at 02:10:39AM +0200, Eugeniy Meshcheryakov wrote:
 15 травня 2008 о 16:24 -0700 Steve Langasek написав(-ла):
   What concerns me about this approach is that it could easilly end up with 
   dist-upgrades swapping out users mail systems without warning. I would 
   consider such behaviour unacceptable as it could easilly cause mail loss 

  Er, no, that wouldn't happen.  As long as packages correctly depend on
  default-mta | mail-transport-agent, this will have no impact on upgrades.

 This can happen if user has 'default-mta' package installed, and it
 changes (if it is done like with 'gcc' package now).

Ah, ok.  Yes, that's a possibility; I was only considering the case that a
user had an MTA installed that was not the default.

So the best option here does seem after all to get apt to look at package
priorities when satisfying virtual packages.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

2008-05-15 Thread Stephen Gran

This one time, at band camp, Mike Bird said:
Yet Debian makes it hard for people to help. Like most software
engineers I simply don't have the time to waste on Debian's NM
process. Debian's processes are indisputably Debian's decision
alone, but Debian has to live with the consequences ... falling
mindshare, orphaned packages, and slow releases.

Nevertheless, non-DD's can and do help by filing bug reports and
patches (upstream is best), helping people on d-u, and offering
constructive advice to DDs. And one should not forget that most
of the software in Debian is developed and maintained by non-DD's.

While we all thank you for the great amount of work you put into Debian
[1] [2], I personally prefer to be told what to do and think in a slightly
less agressive tone, and by someone who knows slightly more about the
subject at hand. I understand that those 6 bug reports probably took
quite a lot of your valuable time, and I don't mean to denigrate that.

If you feel that the NM process may be too rigorous for you, there are
plenty of other ways to contribute to Debian. Perhaps you could tell
us what obstacles we have put in your way (I'm assuming that all these
efforts like DM, alioth packaging teams, QA efforts and so on don't
present a low enough barrier to entry for you, so we won't sully this
conversation by mentioning them).

Again, really, thank you.

1.http://qa.debian.org/developer.php?login=mgb-debian%40yosemite.netcomaint=yes
2.http://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;submitter=mgb-debian%40yosemite.net
--
-
| ,''`.Stephen Gran |
| : :' :[EMAIL PROTECTED] |
| `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
-

signature.asc
Description: Digital signature

Re: Sorting out mail-transport-agent mess

2008-05-15 Thread Ben Finney

Steve Langasek [EMAIL PROTECTED] writes:

 On Thu, May 15, 2008 at 11:33:04PM +0200, Sune Vuorela wrote:
 
  2) Introduce a default-mta package (currently) depending on exim4.
  All packages requiring a MTA should depend on default-mta |
  mail-transport-agent. This will have the extra advantage that we
  (and others like CDDs and derived distros) easily could swap
  default MTA.
 
 I believe that 2) is the correct option, and can see no reason that it
 shouldn't be implemented straight away.

If 'default-mta' is renamed to 'sensible-mta' to follow the existing
convention (evidenced by 'sensible-editor', etc.), I agree.

-- 
 \ For every complex problem, there is a solution that is simple, |
  `\neat, and wrong.  -- Henry L. Mencken |
_o__)  |
Ben Finney


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Sorting out mail-transport-agent mess

On Fri, May 16, 2008 at 10:53:03AM +1000, Ben Finney wrote:
 Steve Langasek [EMAIL PROTECTED] writes:

  On Thu, May 15, 2008 at 11:33:04PM +0200, Sune Vuorela wrote:

   2) Introduce a default-mta package (currently) depending on exim4.
   All packages requiring a MTA should depend on default-mta |
   mail-transport-agent. This will have the extra advantage that we
   (and others like CDDs and derived distros) easily could swap
   default MTA.

  I believe that 2) is the correct option, and can see no reason that it
  shouldn't be implemented straight away.

 If 'default-mta' is renamed to 'sensible-mta' to follow the existing
 convention (evidenced by 'sensible-editor', etc.), I agree.

That's not at all consistent with how sensible-foo is used in Debian today.
sensible-editor and sensible-browser are /commands/ that are guaranteed to
be available for other packages to use and which respect the user- and
site-preferences; default-mta is not at all like this.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Sorting out mail-transport-agent mess

2008-05-15 Thread Ben Finney

Steve Langasek [EMAIL PROTECTED] writes:

 sensible-editor and sensible-browser are /commands/

Provided by the 'debianutils' package.

 default-mta is not at all like this.

You're right, I'm wrong. Thanks for clearing my confusion.

-- 
 \ Hey Homer! You're late for English!  Pff! English, who needs |
  `\   that? I'm never going to England!  -- Barney  Homer, _The |
_o__)Simpsons_ |
Ben Finney


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Sorting out mail-transport-agent mess

2008-05-15 Thread Goswin von Brederlow

Steve Langasek [EMAIL PROTECTED] writes:

 On Fri, May 16, 2008 at 02:10:39AM +0200, Eugeniy Meshcheryakov wrote:
 15 ÑÑÐ°Ð²Ð½Ñ 2008 Ð¾ 16:24 -0700 Steve Langasek Ð½Ð°Ð¿Ð¸ÑÐ°Ð²(-Ð»Ð°):
   What concerns me about this approach is that it could easilly end up 
   with 
   dist-upgrades swapping out users mail systems without warning. I would 
   consider such behaviour unacceptable as it could easilly cause mail loss 

  Er, no, that wouldn't happen.  As long as packages correctly depend on
  default-mta | mail-transport-agent, this will have no impact on upgrades.

 This can happen if user has 'default-mta' package installed, and it
 changes (if it is done like with 'gcc' package now).

 Ah, ok.  Yes, that's a possibility; I was only considering the case that a
 user had an MTA installed that was not the default.

 So the best option here does seem after all to get apt to look at package
 priorities when satisfying virtual packages.

Package exim4:
Provides: default-mta

Package: foo
Depends: default-mta | mail-transport-agent

This should be enough to single out one MTA as the one to be installed
if in doubt and should not cause a change in who provides default-mta
to suddenly install a different mta.

Any reasons against that?

MfG
Goswin

PS: This is not to say apt shouldn't also be fixed to look at
priorities but that is a longer process.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Bug#427697: Is sbackup maintained? If not, what to do?

2008-05-15 Thread Andrew Vaughan

On Friday 16 May 2008 10:20, Charles Plessy wrote:
 Since the revitalisation of sbackup is expected after the freezing of
 Lenny, we have to solve the most important bugs of the current version
 of sbackup. I do not know enough of python for helping on bug #427697
 (the gid of the backups). If Aziz provides a patch, I can prepare a NMU
 for this one, #479826 (using su-t-root-X as su wrapper) and #431936
 (tranlations). I can also make the package non-native (as it has anyway
 been suggested on this list for NMUs).

 By the way, can somebody suggest an appropriate gid ?

There is the adm group, but please think very carefully about the security of 
private/privileged information. 

I'm not familiar with sbackup, but if its backuping mode 0600 files, then the 
resulting backups should be readably only by the original owner or root, 
unless explicitly configured otherwise.

HTH




 Have a nice day,

 --
 Charles


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

pwsafe and OpenSSL?

2008-05-15 Thread Daniel Burrows

  I notice that pwsafe is linked against openssl.  Is it affected by the
recent debacle and if so, how?  Do I need to regenerate all my
randomized passwords, or somehow re-encrypt the pwsafe database?

   Thanks,
  Daniel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: ssl security desaster (was: Re: SSH keys: DSA vs RSA)

2008-05-15 Thread Kevin Buhr

Peter Samuelson [EMAIL PROTECTED] writes:

 Who is this we?  Whose serious efforts?  Who is investigating?  Most
 importantly, should we assume that, as in the past, you, Mike Bird,
 intend to do nothing but talk?

I think this is a common stylistic choice.  I consider myself part of
the Debian community, though I don't contribute very much directly.
When I post to Debian lists, I frequently use we as both a means of
building on an existing community feeling and occasionally to soften
criticism.  I don't use it to claim credit.  I assume Mike uses it the
same way.  In the future, I'll keep in mind not to lump myself with
Debian developers, to avoid this sort of misunderstanding.

In that spirit, maybe YOU should all be more careful about YOUR
pronouns, too.  After all, one of YOU, namely Thijs Kinkhorst,
followed up to Martin Uecker (one of US) with:

 You mean less likely than once in 15 years? We're open to your
 suggestions.

Some of US (not YOU, just US) may have interpreted this not as
pointless sarcasm but as a genuine call for constructive criticism
from US.  If YOU had meant to solicit just Martin's suggestions and
not to hear any suggestions from any of the rest of US, then YOU could
have been more clear in YOUR wording.

Thank YOU for YOUR continued work on Debian.  Despite the occasional
misstep, WE appreciate YOUR efforts.  If YOU ever *do* want to hear
any of OUR suggestions, WE'd be happy to share them, but please be
explicit when YOU ask, so WE don't embarrass OURselves again.

-- 
Kevin Buhr [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted xfce4-quicklauncher-plugin 1.9.4-2 (source amd64)

2008-05-15 Thread Yves-Alexis Perez

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 08:10:08 +0200
Source: xfce4-quicklauncher-plugin
Binary: xfce4-quicklauncher-plugin
Architecture: source amd64
Version: 1.9.4-2
Distribution: unstable
Urgency: low
Maintainer: Debian Xfce Maintainers [EMAIL PROTECTED]
Changed-By: Yves-Alexis Perez [EMAIL PROTECTED]
Description: 
 xfce4-quicklauncher-plugin - rapid launcher plugin for the Xfce4 panel
Closes: 481085
Changes: 
 xfce4-quicklauncher-plugin (1.9.4-2) unstable; urgency=low
 .
   [ Simon Huggins ]
   * debian/control: Move fake Homepage field to a real one now dpkg
 supports it.
   * Add Vcs-* headers to debian/control
 .
   [ Yves-Alexis Perez ]
   * debian/patches: 01-fix-multiscreen added. Fix the screen an application
 opens on when using “zaphod mode”. Patch from David Mohr.   closes: #481085
   * debian/control:
 - updated my email address.
 - updated standards version.
 - removed Rudy Godoy from Uploaders:, many thanks from the work!
   * debian/copyright: updated copyright dates.
Checksums-Sha1: 
 73b60f2ce313809491ef781df659f902c17090e1 1558 
xfce4-quicklauncher-plugin_1.9.4-2.dsc
 0fafd7d5fdb634b3fcbde9fe905bb41fa465cfd1 2548 
xfce4-quicklauncher-plugin_1.9.4-2.diff.gz
 d4b5dca90a7cbf9b877e1437f9691d70ed4c790f 26106 
xfce4-quicklauncher-plugin_1.9.4-2_amd64.deb
Checksums-Sha256: 
 b745ea95cc684531f66fa9c40dacecadf387f6ac2db65d130545cd6f2f15287a 1558 
xfce4-quicklauncher-plugin_1.9.4-2.dsc
 06d4f5e798b4e176b1569ff50dc30780273e6d56fea428f0a8599afa7b607da7 2548 
xfce4-quicklauncher-plugin_1.9.4-2.diff.gz
 84866af47fd62430b270d952b02253047fa87cf02bdd640fec88dd7f6c331a2f 26106 
xfce4-quicklauncher-plugin_1.9.4-2_amd64.deb
Files: 
 bae7919bf7a404127318ee15e8f68b4e 1558 x11 optional 
xfce4-quicklauncher-plugin_1.9.4-2.dsc
 aaa09f050d8967d5d2c7a466f0acebe6 2548 x11 optional 
xfce4-quicklauncher-plugin_1.9.4-2.diff.gz
 36dc65fbcddbea9761e86584d3c281ee 26106 x11 optional 
xfce4-quicklauncher-plugin_1.9.4-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIK9aBTUTAIMXAW64RAkd5AJ9UUo2zOXzF36Ixkit6vi0xMEYpTgCfagTs
f5QsDIUWjmvQsta7GFwZR2k=
=B5mt
-END PGP SIGNATURE-


Accepted:
xfce4-quicklauncher-plugin_1.9.4-2.diff.gz
  to 
pool/main/x/xfce4-quicklauncher-plugin/xfce4-quicklauncher-plugin_1.9.4-2.diff.gz
xfce4-quicklauncher-plugin_1.9.4-2.dsc
  to 
pool/main/x/xfce4-quicklauncher-plugin/xfce4-quicklauncher-plugin_1.9.4-2.dsc
xfce4-quicklauncher-plugin_1.9.4-2_amd64.deb
  to 
pool/main/x/xfce4-quicklauncher-plugin/xfce4-quicklauncher-plugin_1.9.4-2_amd64.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted xfce4-panel 4.4.2-5 (source amd64)

2008-05-15 Thread Yves-Alexis Perez

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 08:48:41 +0200
Source: xfce4-panel
Binary: xfce4-panel xfce4-panel-dev xfce4-panel-dbg
Architecture: source amd64
Version: 4.4.2-5
Distribution: unstable
Urgency: low
Maintainer: Debian Xfce Maintainers [EMAIL PROTECTED]
Changed-By: Yves-Alexis Perez [EMAIL PROTECTED]
Description: 
 xfce4-panel - The Xfce4 desktop environment panel
 xfce4-panel-dbg - debugging informations for xfce4-panel
 xfce4-panel-dev - The Xfce4 panel development files
Closes: 481086
Changes: 
 xfce4-panel (4.4.2-5) unstable; urgency=low
 .
   * debian/patches:
 - 01_fix-dnd-file-panel added, fix a crash when drag  droping a file over
   the panel. (Xfce #3815, r26669).
 - 02_fix-screen-config-dialog added, fix multiscreen support for
   configuration dialogs. (Xfce r26937). closes: #481086
   * debian/rules: use quilt make rule.
   * debian/control: remove Martin Loschwitz from Uploaders:. Thanks for the
 work!
Checksums-Sha1: 
 0e43c7e9a0767055a103bb9062e0066985983c95 1437 xfce4-panel_4.4.2-5.dsc
 5a17ecdee3b57bce5b909574a7ff5e682e195039 17609 xfce4-panel_4.4.2-5.diff.gz
 3ea5f2b01c96b1431de9be7835a6266ab0fbb00b 498152 xfce4-panel_4.4.2-5_amd64.deb
 a4c5325f9aad2fb728c557800fae4a4ee07211ec 93452 
xfce4-panel-dev_4.4.2-5_amd64.deb
 6a11a7ce0ec9b93270cd8acd7824de7a3c092ec2 499630 
xfce4-panel-dbg_4.4.2-5_amd64.deb
Checksums-Sha256: 
 c273c0f95b7e846f80f3be209259373bcf9de7698136dbbeeac3ad2b178468a3 1437 
xfce4-panel_4.4.2-5.dsc
 d681ca0ea9e51f67bc5a9e0576986143e33e34a97b720c8361363a87f85dcc19 17609 
xfce4-panel_4.4.2-5.diff.gz
 bbfb39458867f448af93ed7ded3d87358115dc4f610ff9c5aa0f1f5e7353fe13 498152 
xfce4-panel_4.4.2-5_amd64.deb
 b2920260c77ae5fcbad8f6274aafff0532f5b494c81827d032ce6c68a2ec0960 93452 
xfce4-panel-dev_4.4.2-5_amd64.deb
 f3d4245c3810a726dae6d76e532ca6b8d603c13938809a605adb99f359c73e30 499630 
xfce4-panel-dbg_4.4.2-5_amd64.deb
Files: 
 4745d53a8fccff6d5cde97db6162b504 1437 x11 optional xfce4-panel_4.4.2-5.dsc
 1c1f390ee090827c8dbb413078fb 17609 x11 optional xfce4-panel_4.4.2-5.diff.gz
 6e804e58d4eedb23131d6989eac37225 498152 x11 optional 
xfce4-panel_4.4.2-5_amd64.deb
 c2f25b0655c603b50a7306769c89e22a 93452 devel optional 
xfce4-panel-dev_4.4.2-5_amd64.deb
 fd9a52ba07d78a3eba1ce361d89f20cc 499630 x11 extra 
xfce4-panel-dbg_4.4.2-5_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIK96BTUTAIMXAW64RAs3KAKCjK2DInx0JrL2AEgoPodSHlOpEeACfWrD/
k2rPMnvZwCSLK8mMUT18qO8=
=x47C
-END PGP SIGNATURE-


Accepted:
xfce4-panel-dbg_4.4.2-5_amd64.deb
  to pool/main/x/xfce4-panel/xfce4-panel-dbg_4.4.2-5_amd64.deb
xfce4-panel-dev_4.4.2-5_amd64.deb
  to pool/main/x/xfce4-panel/xfce4-panel-dev_4.4.2-5_amd64.deb
xfce4-panel_4.4.2-5.diff.gz
  to pool/main/x/xfce4-panel/xfce4-panel_4.4.2-5.diff.gz
xfce4-panel_4.4.2-5.dsc
  to pool/main/x/xfce4-panel/xfce4-panel_4.4.2-5.dsc
xfce4-panel_4.4.2-5_amd64.deb
  to pool/main/x/xfce4-panel/xfce4-panel_4.4.2-5_amd64.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted bum 2.2.1-1 (source all)

2008-05-15 Thread Fabio Marzocca

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 8 May 2008 10:17:20 +0100
Source: bum
Binary: bum
Architecture: source all
Version: 2.2.1-1
Distribution: unstable
Urgency: low
Maintainer: Fabio Marzocca [EMAIL PROTECTED]
Changed-By: Fabio Marzocca [EMAIL PROTECTED]
Description: 
 bum- graphical runlevel editor
Closes: 479810
Changes: 
 bum (2.2.1-1) unstable; urgency=low
 .
   * replaced gksu with su-to-root in menu file (Closes: #479810)
   * New upstream version
  - Introduced new service descriptions
Checksums-Sha1: 
 aae31fdc68c5f791ded0667a217adadf4d3b65b9 977 bum_2.2.1-1.dsc
 db8c49f87650301b79e6bee63acf33b477ccea20 226180 bum_2.2.1.orig.tar.gz
 1de8937f1b5b93c67af9fb00045f84c9a4955ecb 2548 bum_2.2.1-1.diff.gz
 922f874c1abb1a2d956592a5cc9eea89a8eea8f6 85720 bum_2.2.1-1_all.deb
Checksums-Sha256: 
 a8439766134e28a0c5f5fada91e81bda8f592ab1a08339a2c20a89c6ca5f49e0 977 
bum_2.2.1-1.dsc
 615cee89c38b33ca759aafccbd6cf1f3aa90769f4f135e1d93458365ff868313 226180 
bum_2.2.1.orig.tar.gz
 6b90be793c309597153e844b9f8c60d0ce38c7c5815ae78b19111e741be0e9f8 2548 
bum_2.2.1-1.diff.gz
 5c8bf224d1d8e885c54596f0d3db60a8cbd3d3a45cdad08669e800158b86ab35 85720 
bum_2.2.1-1_all.deb
Files: 
 3fd2eb39d95c6ad4e7dbce1c7fa1789c 977 admin optional bum_2.2.1-1.dsc
 ed0cc28383152689b92e86996d77e17d 226180 admin optional bum_2.2.1.orig.tar.gz
 74b3ffe9b6845e73b1a608dd27df58fc 2548 admin optional bum_2.2.1-1.diff.gz
 ab81cfb534d56c16f03d04f1930728f3 85720 admin optional bum_2.2.1-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIK+WtvcCgrgZGjesRAoAmAKCWpiqejSfrewHWXTStVWIGpWRMIgCfQ2in
diJJVbYE89L2vdrOxnQBcH0=
=KRkC
-END PGP SIGNATURE-


Accepted:
bum_2.2.1-1.diff.gz
  to pool/main/b/bum/bum_2.2.1-1.diff.gz
bum_2.2.1-1.dsc
  to pool/main/b/bum/bum_2.2.1-1.dsc
bum_2.2.1-1_all.deb
  to pool/main/b/bum/bum_2.2.1-1_all.deb
bum_2.2.1.orig.tar.gz
  to pool/main/b/bum/bum_2.2.1.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted kdebase-runtime 4:4.0.73+svn807734-1 (source all amd64)

2008-05-15 Thread Debian Qt/KDE Maintainers

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 14 May 2008 21:20:39 +0200
Source: kdebase-runtime
Binary: kdebase-runtime kdebase-runtime-bin-kde4 kdebase-runtime-data 
kdebase-runtime-data-common kde-icons-oxygen kdebase-runtime-dbg
Architecture: source all amd64
Version: 4:4.0.73+svn807734-1
Distribution: experimental
Urgency: low
Maintainer: Fathi Boudra [EMAIL PROTECTED]
Changed-By: Debian Qt/KDE Maintainers [EMAIL PROTECTED]
Description: 
 kde-icons-oxygen - Oxygen icon theme for KDE 4
 kdebase-runtime - runtime components from the official KDE 4 release
 kdebase-runtime-bin-kde4 - core binaries for the KDE 4 base runtime module
 kdebase-runtime-data - shared data files for the KDE 4 base runtime module
 kdebase-runtime-data-common - shared data files for the KDE 4 base runtime 
module
 kdebase-runtime-dbg - debugging symbols for KDE 4 base runtime module
Changes: 
 kdebase-runtime (4:4.0.73+svn807734-1) experimental; urgency=low
 .
   * New upstream development snapshot:
 - The latest upstream commit is r807734 by mkretz
 - Date: Wed May 14 15:44:43 2008 UTC
Checksums-Sha1: 
 12747131db7f7224a2ae18968881e1d4b6d66d57 2074 
kdebase-runtime_4.0.73+svn807734-1.dsc
 b92eb9df103a33f91c6a745210c07cd4c73b374e 52299193 
kdebase-runtime_4.0.73+svn807734.orig.tar.gz
 952e85326ca963132c8a8deb768810c4af7ee468 32563 
kdebase-runtime_4.0.73+svn807734-1.diff.gz
 be09cab139d788ce2432b6a18461193038bc9514 2896016 
kdebase-runtime-data_4.0.73+svn807734-1_all.deb
 183c79702cfcfa131e80ea45e70f1fa9ddee2861 321298 
kdebase-runtime-data-common_4.0.73+svn807734-1_all.deb
 f16dadae7125b05aacd48057e31846f166009ddd 46890766 
kde-icons-oxygen_4.0.73+svn807734-1_all.deb
 59c7f60867e0ee40ffe9acb3d8534eabf1573868 1941804 
kdebase-runtime_4.0.73+svn807734-1_amd64.deb
 2d0ce705811db2d7f64a06146d0a2aced42e47a7 67196 
kdebase-runtime-bin-kde4_4.0.73+svn807734-1_amd64.deb
 29c9a0913a0e3b3046ae4ea5e783cb2d81108ad3 13792164 
kdebase-runtime-dbg_4.0.73+svn807734-1_amd64.deb
Checksums-Sha256: 
 042f8ece43faaa03c399be7416950d16120aa23179512af936798ee26fa09cdf 2074 
kdebase-runtime_4.0.73+svn807734-1.dsc
 6a0c151b8ae9ab0703139ce540ad64e5ee5e35ce682b3e3cbc7d00631070b6ca 52299193 
kdebase-runtime_4.0.73+svn807734.orig.tar.gz
 ff7dcbaa74c6c04e80de8414062b25f94998d093fa8b5702822daeca192d7714 32563 
kdebase-runtime_4.0.73+svn807734-1.diff.gz
 bbf3f9e0ef1eb0eddf74bfcd6b5dff5e30372a4d20570d1b02e17a4994317a99 2896016 
kdebase-runtime-data_4.0.73+svn807734-1_all.deb
 e39c4001294a8e956b03180b730bdba81489d9f36173ba7f0c010bb6e4b4 321298 
kdebase-runtime-data-common_4.0.73+svn807734-1_all.deb
 9729b35b1f4d685711cbbbdbe2e6c39c3634c2eaeebeba35def184e99438e711 46890766 
kde-icons-oxygen_4.0.73+svn807734-1_all.deb
 a7ecca547438cc293f3cc1e35467d4a7c2f9f953410974bb3b2aa5b04e4f962d 1941804 
kdebase-runtime_4.0.73+svn807734-1_amd64.deb
 52674c2063f26c27fbf2148398904adaec1488ca269e2f4c334bc8c57f572cca 67196 
kdebase-runtime-bin-kde4_4.0.73+svn807734-1_amd64.deb
 97a7fa86fa51156cdc153d4f89a9760e69a6e7077da8fd99e9d6fdad6f0a425a 13792164 
kdebase-runtime-dbg_4.0.73+svn807734-1_amd64.deb
Files: 
 9e9ad0230530732e2220afaa0193cf61 2074 kde optional 
kdebase-runtime_4.0.73+svn807734-1.dsc
 e4be57f0b0efdd7aae77d85c3da2164a 52299193 kde optional 
kdebase-runtime_4.0.73+svn807734.orig.tar.gz
 f6bc664f16aca74bb4c5aa8199a4b027 32563 kde optional 
kdebase-runtime_4.0.73+svn807734-1.diff.gz
 1597df97ba209db37275f6f99014b82b 2896016 kde optional 
kdebase-runtime-data_4.0.73+svn807734-1_all.deb
 2704cbbd788e621a87aa4bf03d774a8b 321298 kde optional 
kdebase-runtime-data-common_4.0.73+svn807734-1_all.deb
 a1bb720ad69a2397af69dc6b63cf143a 46890766 kde optional 
kde-icons-oxygen_4.0.73+svn807734-1_all.deb
 5dd1922d1bac1af809a051664c86aa07 1941804 kde optional 
kdebase-runtime_4.0.73+svn807734-1_amd64.deb
 fd268b890a60f67946b335fbb5ab37e6 67196 kde optional 
kdebase-runtime-bin-kde4_4.0.73+svn807734-1_amd64.deb
 e50dda7fe84b74ef847d64ead8cf4a97 13792164 devel extra 
kdebase-runtime-dbg_4.0.73+svn807734-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iQCVAwUBSCtEP4z1NfZqpXL3AQIDWgQAvpSd645P3BwggXIuRa8MsTgRE+lw/f8V
+YRKjdmuu/zf85cU8fMz8EcC/5rEny98ViUbueKWATSBX1nt2TdsIMkafu9qZ3a4
chXY3PplztdTj28eVYVAQktmcokMMkc5eDC4IVNuqxQG9+9FoYg622xEtIJ7KpdW
frAtpi4rHCo=
=oJ7y
-END PGP SIGNATURE-


Accepted:
kde-icons-oxygen_4.0.73+svn807734-1_all.deb
  to pool/main/k/kdebase-runtime/kde-icons-oxygen_4.0.73+svn807734-1_all.deb
kdebase-runtime-bin-kde4_4.0.73+svn807734-1_amd64.deb
  to 
pool/main/k/kdebase-runtime/kdebase-runtime-bin-kde4_4.0.73+svn807734-1_amd64.deb
kdebase-runtime-data-common_4.0.73+svn807734-1_all.deb
  to 
pool/main/k/kdebase-runtime/kdebase-runtime-data-common_4.0.73+svn807734-1_all.deb
kdebase-runtime-data_4.0.73+svn807734-1_all.deb
  to pool/main/k/kdebase-runtime/kdebase-runtime-data_4.0.73+svn807734-1_all.deb
kdebase-runtime-dbg_4.0.73+svn807734-1_amd64.deb
  to

Accepted gtkorphan 0.4.4-1 (source all)

2008-05-15 Thread Fabio Marzocca

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 8 May 2008 11:40:47 +0100
Source: gtkorphan
Binary: gtkorphan
Architecture: source all
Version: 0.4.4-1
Distribution: unstable
Urgency: low
Maintainer: Fabio Marzocca [EMAIL PROTECTED]
Changed-By: Fabio Marzocca [EMAIL PROTECTED]
Description: 
 gtkorphan  - A graphical tool to find and remove orphaned libraries
Closes: 479819
Changes: 
 gtkorphan (0.4.4-1) unstable; urgency=low
 .
   * Replaced gksu with su-to-root (Closes:#479819)
Checksums-Sha1: 
 c8d10110e20684341405b35b1174d75ccf2edb39 1005 gtkorphan_0.4.4-1.dsc
 5b17eebe76c5e332c33d7806fce34dd6ffdc2368 172784 gtkorphan_0.4.4.orig.tar.gz
 257765a4edaf1ad678a4a9f5d7e9ceb9f4ad0a0d 1947 gtkorphan_0.4.4-1.diff.gz
 8cd5b0254659869decae685106a8fbfaa35e0db0 31418 gtkorphan_0.4.4-1_all.deb
Checksums-Sha256: 
 75e334107be9090ea3dc4709a56065b39b26fd8e8c4cffe26a30c42102124279 1005 
gtkorphan_0.4.4-1.dsc
 ed7394bb239710aa33ca250a36930252dbb6f767132ec180819196a5f3778b5e 172784 
gtkorphan_0.4.4.orig.tar.gz
 e245d245e98d9dfff0ad4abe902d339f7bf982164d01d3852f58f7cd0bea8b43 1947 
gtkorphan_0.4.4-1.diff.gz
 4a90d6fbaa5cd52fecc38115b8281c354ce2343f069f9724fc1c425c5396d3ea 31418 
gtkorphan_0.4.4-1_all.deb
Files: 
 cadf85572e31c5a899d66816a92b1e9e 1005 admin optional gtkorphan_0.4.4-1.dsc
 c53a44630b7d7a773388ae64ce956288 172784 admin optional 
gtkorphan_0.4.4.orig.tar.gz
 d755402caded7b287fdd0a4ec3c11ca4 1947 admin optional gtkorphan_0.4.4-1.diff.gz
 ce3eb695b20a861db7e3b6411efed308 31418 admin optional gtkorphan_0.4.4-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIK+VPvcCgrgZGjesRAvRYAJ4slRLpTDJHVYIHHQuzCiS8c/ldtQCcDzrw
3ta8s/5buzTVUYDUKrLIDyQ=
=EGuF
-END PGP SIGNATURE-


Accepted:
gtkorphan_0.4.4-1.diff.gz
  to pool/main/g/gtkorphan/gtkorphan_0.4.4-1.diff.gz
gtkorphan_0.4.4-1.dsc
  to pool/main/g/gtkorphan/gtkorphan_0.4.4-1.dsc
gtkorphan_0.4.4-1_all.deb
  to pool/main/g/gtkorphan/gtkorphan_0.4.4-1_all.deb
gtkorphan_0.4.4.orig.tar.gz
  to pool/main/g/gtkorphan/gtkorphan_0.4.4.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted gst-plugins-ugly0.10 0.10.7.3-1 (source all i386)

2008-05-15 Thread Sebastian Dröge

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 09:53:02 +0200
Source: gst-plugins-ugly0.10
Binary: gstreamer0.10-plugins-ugly-doc gstreamer0.10-plugins-ugly 
gstreamer0.10-plugins-ugly-dbg
Architecture: source all i386
Version: 0.10.7.3-1
Distribution: unstable
Urgency: low
Maintainer: Maintainers of GStreamer packages [EMAIL PROTECTED]
Changed-By: Sebastian Dröge [EMAIL PROTECTED]
Description: 
 gstreamer0.10-plugins-ugly - GStreamer plugins from the ugly set
 gstreamer0.10-plugins-ugly-dbg - GStreamer plugins from the ugly set
 gstreamer0.10-plugins-ugly-doc - GStreamer documentation for plugins from the 
ugly set
Changes: 
 gst-plugins-ugly0.10 (0.10.7.3-1) unstable; urgency=low
 .
   * New upstream pre-release.
Checksums-Sha1: 
 1357c1018992b72104b0ae0dde3325f72e60c275 1705 
gst-plugins-ugly0.10_0.10.7.3-1.dsc
 47235ad190d5515bfacf71ae3c320c3ce588743a 1232425 
gst-plugins-ugly0.10_0.10.7.3.orig.tar.gz
 016d9723bdef301f4d24b7e843f878f7a9a72658 22456 
gst-plugins-ugly0.10_0.10.7.3-1.diff.gz
 738553ce48e08ab2fd6705b12a2827bfbcd26234 51418 
gstreamer0.10-plugins-ugly-doc_0.10.7.3-1_all.deb
 6ee5df308a067b9aceb8c7ee9d89ba18b81e7de3 283734 
gstreamer0.10-plugins-ugly_0.10.7.3-1_i386.deb
 4d06ae5495a317e9f510dc2559b9f2b2661805d3 543110 
gstreamer0.10-plugins-ugly-dbg_0.10.7.3-1_i386.deb
Checksums-Sha256: 
 5f7248ea795aadcdab3bd2f50ebddfa30d8a034c154c34b1c11e67afe484b12f 1705 
gst-plugins-ugly0.10_0.10.7.3-1.dsc
 2cc3f49413724975783a52f52cf50d8ad8d692147ca166a5143749563bd3931d 1232425 
gst-plugins-ugly0.10_0.10.7.3.orig.tar.gz
 35b92e239cf41b2bc624684a66b3f520b99484ae7051f7ed2d127f35c4650e25 22456 
gst-plugins-ugly0.10_0.10.7.3-1.diff.gz
 3a34a78258d6a640ada180d9a1e6f6dcdc51c667312a1cc380fbfeb286d7e5a4 51418 
gstreamer0.10-plugins-ugly-doc_0.10.7.3-1_all.deb
 6f3dcf7cc0ef05df132d005d27e3bc4e43011c0e4bfab137dba30084fa74fb88 283734 
gstreamer0.10-plugins-ugly_0.10.7.3-1_i386.deb
 f8c2d306f074995780fb15e62118cd8ea19dc1aa8a8d6d48b3dfb90b0f19cb13 543110 
gstreamer0.10-plugins-ugly-dbg_0.10.7.3-1_i386.deb
Files: 
 b7cef8dc2b162fe58ec340b6d4dae582 1705 libs optional 
gst-plugins-ugly0.10_0.10.7.3-1.dsc
 210af7a1f12509f8aad9d55faac331f8 1232425 libs optional 
gst-plugins-ugly0.10_0.10.7.3.orig.tar.gz
 5b6c8a1c60c8cd0125d9f598c0a4af10 22456 libs optional 
gst-plugins-ugly0.10_0.10.7.3-1.diff.gz
 c96da1e94ec2f8f8084d19dcda9da5c4 51418 doc optional 
gstreamer0.10-plugins-ugly-doc_0.10.7.3-1_all.deb
 c25131664340aa4e0c06fd28220c357d 283734 libs optional 
gstreamer0.10-plugins-ugly_0.10.7.3-1_i386.deb
 6bd10e3d3fd950d7aa71bbec0e4afdea 543110 libdevel extra 
gstreamer0.10-plugins-ugly-dbg_0.10.7.3-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIK+4nBsBdh1vkHyERAqAlAKCqJiw4l0Jw/zbvatTndNHGKH5TqACggH9t
vbaYl0IXmnBGp+6Rndp9vmc=
=JDFu
-END PGP SIGNATURE-


Accepted:
gst-plugins-ugly0.10_0.10.7.3-1.diff.gz
  to pool/main/g/gst-plugins-ugly0.10/gst-plugins-ugly0.10_0.10.7.3-1.diff.gz
gst-plugins-ugly0.10_0.10.7.3-1.dsc
  to pool/main/g/gst-plugins-ugly0.10/gst-plugins-ugly0.10_0.10.7.3-1.dsc
gst-plugins-ugly0.10_0.10.7.3.orig.tar.gz
  to pool/main/g/gst-plugins-ugly0.10/gst-plugins-ugly0.10_0.10.7.3.orig.tar.gz
gstreamer0.10-plugins-ugly-dbg_0.10.7.3-1_i386.deb
  to 
pool/main/g/gst-plugins-ugly0.10/gstreamer0.10-plugins-ugly-dbg_0.10.7.3-1_i386.deb
gstreamer0.10-plugins-ugly-doc_0.10.7.3-1_all.deb
  to 
pool/main/g/gst-plugins-ugly0.10/gstreamer0.10-plugins-ugly-doc_0.10.7.3-1_all.deb
gstreamer0.10-plugins-ugly_0.10.7.3-1_i386.deb
  to 
pool/main/g/gst-plugins-ugly0.10/gstreamer0.10-plugins-ugly_0.10.7.3-1_i386.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted proguard 4.2-1 (source all)

2008-05-15 Thread Sam Clegg

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 10:39:48 +0100
Source: proguard
Binary: proguard
Architecture: source all
Version: 4.2-1
Distribution: unstable
Urgency: low
Maintainer: Sam Clegg [EMAIL PROTECTED]
Changed-By: Sam Clegg [EMAIL PROTECTED]
Description: 
 proguard   - java class file shrinker, optimizer, and obfuscator
Closes: 459829
Changes: 
 proguard (4.2-1) unstable; urgency=low
 .
   * New upstream release
   * Fix build of ant task (Closes: #459829)
 Thanks to Hans van Kranenburg [EMAIL PROTECTED]
Checksums-Sha1: 
 863a5677da17eedc2ab4d464816d1e5dde5f6a4a 965 proguard_4.2-1.dsc
 4dac1c7182d789989f7ff147156951541b7b537e 1041855 proguard_4.2.orig.tar.gz
 fb5a874cd4c13dbaad5dd01b891327fdababc469 2425 proguard_4.2-1.diff.gz
 b03dfdcf9af3c0a9755b3bd47c930bcbc3ef1c31 1173422 proguard_4.2-1_all.deb
Checksums-Sha256: 
 ebae67038dd931213ed33fa4c08dc2b1a99109fbcb24d475ccc753f25ac572f2 965 
proguard_4.2-1.dsc
 742be59d5d22b1d8ba22cb277954fa9b7f3691334b5dc1ac08363eeb4e6e7f3b 1041855 
proguard_4.2.orig.tar.gz
 274a5448e7a546a523a33ee85064d9ecad3285682dbcab46ae78ffe2cfbb 2425 
proguard_4.2-1.diff.gz
 463a230d72bc35421196ea4e4866b893c931635fda0f3a715d4ba5187e39675f 1173422 
proguard_4.2-1_all.deb
Files: 
 041f7969ea098d09e59b8a76f1d765b7 965 devel optional proguard_4.2-1.dsc
 a83faa39184f5cb354907fc0e4ad371d 1041855 devel optional 
proguard_4.2.orig.tar.gz
 4dbdcb89159dd0fdadde2539d544d601 2425 devel optional proguard_4.2-1.diff.gz
 c394fef7c39af5c198d8692d4eea0270 1173422 devel optional proguard_4.2-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILAX8LOvxONke42kRAirAAKCYsBEEExB1Cs6EcNEt84QJvsw9yACfV4Cf
TnrvKw2EJ04+8x81aT6VmVA=
=P7hG
-END PGP SIGNATURE-


Accepted:
proguard_4.2-1.diff.gz
  to pool/main/p/proguard/proguard_4.2-1.diff.gz
proguard_4.2-1.dsc
  to pool/main/p/proguard/proguard_4.2-1.dsc
proguard_4.2-1_all.deb
  to pool/main/p/proguard/proguard_4.2-1_all.deb
proguard_4.2.orig.tar.gz
  to pool/main/p/proguard/proguard_4.2.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted octave-statistics 1.0.6-1 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 12:43:43 +0200
Source: octave-statistics
Binary: octave-statistics
Architecture: source all
Version: 1.0.6-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber [EMAIL PROTECTED]
Description: 
 octave-statistics - additional statistical functions for Octave
Changes: 
 octave-statistics (1.0.6-1) unstable; urgency=low
 .
   [ Ólafur Jens Sigurðsson ]
   * New upstream version
Checksums-Sha1: 
 1018faca21f4409a696e884722991351ae76ace8 1460 octave-statistics_1.0.6-1.dsc
 a65774d7cd380bf9ef50e787aaf84a76471a13e1 71449 
octave-statistics_1.0.6.orig.tar.gz
 1d842b579c76a1ae37c2c4cf1c372d34353930ed 1574 octave-statistics_1.0.6-1.diff.gz
 573bf8c9b42e4a6348ddcdfad2d0b24560c9658e 71372 
octave-statistics_1.0.6-1_all.deb
Checksums-Sha256: 
 c97ab27658effec28cdec020fe8b6e80d37446c28174cc8c0dd45f95a44a0e29 1460 
octave-statistics_1.0.6-1.dsc
 03e99cb092a838e85a93fa635f466e75bcf4bff98d5829a982ec9bbaad627916 71449 
octave-statistics_1.0.6.orig.tar.gz
 8293bdbd8b11c6db1be1be144a20cb74c2a54e6ee80161e74d6c1a08b3ae6ac1 1574 
octave-statistics_1.0.6-1.diff.gz
 d342e5737d2b6179ae951b2d646db278d822478a269bfaccbc3dcdabc5e2cabf 71372 
octave-statistics_1.0.6-1_all.deb
Files: 
 7f0c5ed1bcfaace9af46f7bb5b199095 1460 math optional 
octave-statistics_1.0.6-1.dsc
 693b7c03a9087bf69e7e23989efffd99 71449 math optional 
octave-statistics_1.0.6.orig.tar.gz
 cd24a283984329934ad907bc3f9ae139 1574 math optional 
octave-statistics_1.0.6-1.diff.gz
 88e0dfc91dc2555931cc438b850616fa 71372 math optional 
octave-statistics_1.0.6-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILBR1PqD4a3lPnXwRAt9+AKCmVjWr3kLep5Ax4tMn+Qm5ZOVeSwCeNSpT
y5jdbaCrq3l8GHMdnYxUjeQ=
=NK7Q
-END PGP SIGNATURE-


Accepted:
octave-statistics_1.0.6-1.diff.gz
  to pool/main/o/octave-statistics/octave-statistics_1.0.6-1.diff.gz
octave-statistics_1.0.6-1.dsc
  to pool/main/o/octave-statistics/octave-statistics_1.0.6-1.dsc
octave-statistics_1.0.6-1_all.deb
  to pool/main/o/octave-statistics/octave-statistics_1.0.6-1_all.deb
octave-statistics_1.0.6.orig.tar.gz
  to pool/main/o/octave-statistics/octave-statistics_1.0.6.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted octave-struct 1.0.5-1 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 12:33:51 +0200
Source: octave-struct
Binary: octave-struct
Architecture: source all
Version: 1.0.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber [EMAIL PROTECTED]
Description: 
 octave-struct - additional structure manipulation functions for Octave
Changes: 
 octave-struct (1.0.5-1) unstable; urgency=low
 .
   [ Ólafur Jens Sigurðsson ]
   * New upstream version
Checksums-Sha1: 
 0ed1c778f8ebea6608258fe98305f2774f57 1416 octave-struct_1.0.5-1.dsc
 a43e6fdeaed6fa93345b508293a1bde4a2e0f556 34143 octave-struct_1.0.5.orig.tar.gz
 a02e85a11050aae25f403c72353887bafc1abc00 1082 octave-struct_1.0.5-1.diff.gz
 9b50058254cf43eb71ad236d847b009eebd97b2d 27448 octave-struct_1.0.5-1_all.deb
Checksums-Sha256: 
 8ac3dd7139669231e3efebb44e7890df507b926f8cf7365a22ec9a65bb83 1416 
octave-struct_1.0.5-1.dsc
 928178ea43cae5cda52d9d38d779496b9a7ee2c065ebcba5d58a4fcaa5114a52 34143 
octave-struct_1.0.5.orig.tar.gz
 72f58b114a87aae83433daaf94407fb7c51f458c5c2dc37fbe9c17cfd8d79095 1082 
octave-struct_1.0.5-1.diff.gz
 3ce444d621e76b1b7106681e3f8a9d2f9c03e008c70064ba85c3f66b1feffbe6 27448 
octave-struct_1.0.5-1_all.deb
Files: 
 aacd1979a8887da3db00493a97c05b61 1416 math optional octave-struct_1.0.5-1.dsc
 d403a86bef71300f121ce6d5cb5f48d3 34143 math optional 
octave-struct_1.0.5.orig.tar.gz
 1d553e4b4adde0dd9d2fc47296c9a540 1082 math optional 
octave-struct_1.0.5-1.diff.gz
 e2a587632c7e017354ae00cf551822f6 27448 math optional 
octave-struct_1.0.5-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILBJMPqD4a3lPnXwRAgfFAJ94sdvjAbw0uDjUPBGK1OuhLP2G+wCgll5b
q80z2BoohCi3f12moTcYvJo=
=myvR
-END PGP SIGNATURE-


Accepted:
octave-struct_1.0.5-1.diff.gz
  to pool/main/o/octave-struct/octave-struct_1.0.5-1.diff.gz
octave-struct_1.0.5-1.dsc
  to pool/main/o/octave-struct/octave-struct_1.0.5-1.dsc
octave-struct_1.0.5-1_all.deb
  to pool/main/o/octave-struct/octave-struct_1.0.5-1_all.deb
octave-struct_1.0.5.orig.tar.gz
  to pool/main/o/octave-struct/octave-struct_1.0.5.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted keynav 0.20080509-1 (source i386)

2008-05-15 Thread Wen-Yen Chuang

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 09:36:48 +0800
Source: keynav
Binary: keynav
Architecture: source i386
Version: 0.20080509-1
Distribution: unstable
Urgency: low
Maintainer: Wen-Yen Chuang [EMAIL PROTECTED]
Changed-By: Wen-Yen Chuang [EMAIL PROTECTED]
Description: 
 keynav - a keyboard-driven mouse cursor mover
Changes: 
 keynav (0.20080509-1) unstable; urgency=low
 .
   * New upstream release
   * Replace rm with dh_clean in debian/rules
Checksums-Sha1: 
 6dbae4799a23706471c11cd30a2a255b1ebe610d 1024 keynav_0.20080509-1.dsc
 fce86da4802ba38b45b1a89e2e16ad408b789ce9 30874 keynav_0.20080509.orig.tar.gz
 79683f87936783518a570cc3d9ec970c751e8d18 2699 keynav_0.20080509-1.diff.gz
 52c15dbcb5f9bc19950a315061ac30363cd41e3c 16366 keynav_0.20080509-1_i386.deb
Checksums-Sha256: 
 1418143a8c4ab8e1caa392cf7e3eaad329c8f9c701290cd0b76de7faf3fcebbf 1024 
keynav_0.20080509-1.dsc
 e1d78eb6fa168e65facc9b84e7606a90c61753db1ae6e44f692345d0f8e0fca7 30874 
keynav_0.20080509.orig.tar.gz
 9d0a5a5f749c4d8c378a77252f1d8743e8ced2a71208426a99a6361a8915246a 2699 
keynav_0.20080509-1.diff.gz
 49d8ff92653ce0827b16e0575913a0ecd080ac9c1b674802caa7356c44e1fa2f 16366 
keynav_0.20080509-1_i386.deb
Files: 
 3a87f015001a49db9e19c91d60b6e85c 1024 utils optional keynav_0.20080509-1.dsc
 528a65b99ccf57e856bec2d074564edf 30874 utils optional 
keynav_0.20080509.orig.tar.gz
 c2f42f0239bdd588f0a08254794556f1 2699 utils optional 
keynav_0.20080509-1.diff.gz
 502872822b195a8a1b5638aeea6b44ce 16366 utils optional 
keynav_0.20080509-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILBLBsKTFpDfZQSwRAnvnAKCXOJ0jM7ivigODeV6e5tP6w/elFACcCDCz
mV60uT/CDjAEVkb09C2qM88=
=Aw3y
-END PGP SIGNATURE-


Accepted:
keynav_0.20080509-1.diff.gz
  to pool/main/k/keynav/keynav_0.20080509-1.diff.gz
keynav_0.20080509-1.dsc
  to pool/main/k/keynav/keynav_0.20080509-1.dsc
keynav_0.20080509-1_i386.deb
  to pool/main/k/keynav/keynav_0.20080509-1_i386.deb
keynav_0.20080509.orig.tar.gz
  to pool/main/k/keynav/keynav_0.20080509.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted libclass-meta-perl 0.61-1 (source all)

2008-05-15 Thread eloy

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 12:13:58 +0200
Source: libclass-meta-perl
Binary: libclass-meta-perl
Architecture: source all
Version: 0.61-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group [EMAIL PROTECTED]
Changed-By: Krzysztof Krzyżaniak (eloy) [EMAIL PROTECTED]
Description: 
 libclass-meta-perl - Class automation, introspection, and data validation
Changes: 
 libclass-meta-perl (0.61-1) unstable; urgency=low
 .
   * New upstream release
Checksums-Sha1: 
 fb2afea4b8f2234c5e0bbaf4526fa3407477eaf0 1371 libclass-meta-perl_0.61-1.dsc
 231bb4dfdab670605d3055ebb89b4b8e41034070 66534 
libclass-meta-perl_0.61.orig.tar.gz
 f953521dc874f5d7b8a1829a027c0dfb2f0326df 2415 libclass-meta-perl_0.61-1.diff.gz
 2d7ee81b776223e957b2fa7a5e2e9e0749a0f0f5 107414 
libclass-meta-perl_0.61-1_all.deb
Checksums-Sha256: 
 b9fd688064c2af5ff0af4046c0b42544c345692ec4beadacce8e2f4bbf2519d2 1371 
libclass-meta-perl_0.61-1.dsc
 2a98f6dd3f843d7365141f23865ccecaf78106f9a8a5714c6484fe9f9f4e488a 66534 
libclass-meta-perl_0.61.orig.tar.gz
 6efd0088a0dde3c8d7681c5c57ca224a2035ae3193059ce93656904c5d21e657 2415 
libclass-meta-perl_0.61-1.diff.gz
 204897767146e83ca384dadcec6a8d9a80c49e37b92d601a380887b25d6419e7 107414 
libclass-meta-perl_0.61-1_all.deb
Files: 
 85ecc2b6ebb4e7b4f944fba7e0e3f78e 1371 perl optional 
libclass-meta-perl_0.61-1.dsc
 272986668c83629492e6f18d8c1b4b2a 66534 perl optional 
libclass-meta-perl_0.61.orig.tar.gz
 0af4275b02bde89397b3efc4bfdeae34 2415 perl optional 
libclass-meta-perl_0.61-1.diff.gz
 536f063a001b79025adc5240b0806d1f 107414 perl optional 
libclass-meta-perl_0.61-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILA+/y+HP4f7iC8sRAlxYAJwOHwAQi6QLgFm1UWp+HvpQlaqaqgCePw2X
6khLqW3mh7oHHjW0tpywArc=
=1scF
-END PGP SIGNATURE-


Accepted:
libclass-meta-perl_0.61-1.diff.gz
  to pool/main/libc/libclass-meta-perl/libclass-meta-perl_0.61-1.diff.gz
libclass-meta-perl_0.61-1.dsc
  to pool/main/libc/libclass-meta-perl/libclass-meta-perl_0.61-1.dsc
libclass-meta-perl_0.61-1_all.deb
  to pool/main/libc/libclass-meta-perl/libclass-meta-perl_0.61-1_all.deb
libclass-meta-perl_0.61.orig.tar.gz
  to pool/main/libc/libclass-meta-perl/libclass-meta-perl_0.61.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted octave-strings 1.0.5-1 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 12:38:29 +0200
Source: octave-strings
Binary: octave-strings
Architecture: source i386
Version: 1.0.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber [EMAIL PROTECTED]
Description: 
 octave-strings - additional string manipulation functions for Octave
Changes: 
 octave-strings (1.0.5-1) unstable; urgency=low
 .
   [ Ólafur Jens Sigurðsson ]
   * New upstream version
Checksums-Sha1: 
 f74fc4a10b87598ca885719b1220a6717186d28e 1427 octave-strings_1.0.5-1.dsc
 1ba64a6670ef7bd2fca51c68d6c9db84faea9310 70616 octave-strings_1.0.5.orig.tar.gz
 2d1a8ccfe98479971a772086cf71338570426d21 1935 octave-strings_1.0.5-1.diff.gz
 a3bf2d34454f4363413b21d5b0a16f8a5769ef5f 33648 octave-strings_1.0.5-1_i386.deb
Checksums-Sha256: 
 8edd47933706864426f2b0576023f39713120d5c652b378e28a7fe33d1c423b5 1427 
octave-strings_1.0.5-1.dsc
 d05c907dd90f97e2305fb67a14666c6b4ed649dbaead0743be36c46ec97c9f48 70616 
octave-strings_1.0.5.orig.tar.gz
 b1715a36f8bba386dc35db746a030b453f305ac2290eb05577104c3712a20ae9 1935 
octave-strings_1.0.5-1.diff.gz
 ac172af0c418463a5e71747cc4084f55cdd6989c91a9cecb406ba0c1a08947db 33648 
octave-strings_1.0.5-1_i386.deb
Files: 
 0c533a14ae2f337a466886807968a7ef 1427 math optional octave-strings_1.0.5-1.dsc
 6ef1756c63729754bd467f79f82e0406 70616 math optional 
octave-strings_1.0.5.orig.tar.gz
 6fca2a8a19f2a93a4b833842774abc30 1935 math optional 
octave-strings_1.0.5-1.diff.gz
 829c3ad725f47cb50acadb6919060804 33648 math optional 
octave-strings_1.0.5-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILBOcPqD4a3lPnXwRAnjmAKCVi5D6Adnvxi3JtaRZCE2pq31VGQCeOP59
FyUmEP0cyk3KUHzPEpq1An8=
=BJFq
-END PGP SIGNATURE-


Accepted:
octave-strings_1.0.5-1.diff.gz
  to pool/main/o/octave-strings/octave-strings_1.0.5-1.diff.gz
octave-strings_1.0.5-1.dsc
  to pool/main/o/octave-strings/octave-strings_1.0.5-1.dsc
octave-strings_1.0.5-1_i386.deb
  to pool/main/o/octave-strings/octave-strings_1.0.5-1_i386.deb
octave-strings_1.0.5.orig.tar.gz
  to pool/main/o/octave-strings/octave-strings_1.0.5.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted gramadoir 0.6-3 (source all)

2008-05-15 Thread Alastair McKinstry

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 13 May 2008 16:59:18 +0100
Source: gramadoir
Binary: gramadoir liblingua-ga-gramadoir-perl
Architecture: source all
Version: 0.6-3
Distribution: unstable
Urgency: low
Maintainer: Alastair McKinstry [EMAIL PROTECTED]
Changed-By: Alastair McKinstry [EMAIL PROTECTED]
Description: 
 gramadoir  - Irish language grammar checker (integration scripts)
 liblingua-ga-gramadoir-perl - Irish language grammar checker
Closes: 467124
Changes: 
 gramadoir (0.6-3) unstable; urgency=low
 .
   * Fix dependency on Perl 5.8.8. Closes:  #467124.
   * Move to Standards-Version: 3.7.3. No changes required.
   * Replace DH_COMPAT=5 in debian/rules with debian/compat file.
   * Put liblingya-ga-gramadoir-perl in Section: perl
Checksums-Sha1: 
 ecdafa1bf35a605a5b3a2482bded2f47a41b0e73 1042 gramadoir_0.6-3.dsc
 7e1cc2a601a825a6aaf8bf4658fd9398d0b3 2979 gramadoir_0.6-3.diff.gz
 7f9430c0428b087ea13c77d696a3d1a713d4ae94 50334 gramadoir_0.6-3_all.deb
 2fe019ac54727e11ec51cc5ca14c3ccb1740394b 2749572 
liblingua-ga-gramadoir-perl_0.6-3_all.deb
Checksums-Sha256: 
 24f257ce7abdce4f1d2f81d7e925751f2d590d1568f4cee1fab149f70b7430a6 1042 
gramadoir_0.6-3.dsc
 bb80a75319fd5f023ab22b7821f16858f0b094261098aa0d1b0f03d147a20579 2979 
gramadoir_0.6-3.diff.gz
 e57316d56af77d04374b2bdf2e7e6e1d4ec1f2c8b2d4e5c4f42c2c5a832f9635 50334 
gramadoir_0.6-3_all.deb
 34ee2993b0bd0338e20983ca8c63f77283f636804e3b6f41e75f6ea66acf7be0 2749572 
liblingua-ga-gramadoir-perl_0.6-3_all.deb
Files: 
 ada25a6b50d4af45a1eb75eab301a7b5 1042 misc optional gramadoir_0.6-3.dsc
 9d8f9df00e8ab4c85c959a287b0c1f60 2979 misc optional gramadoir_0.6-3.diff.gz
 8159f8b2ccaf3657320d758c022cc5e3 50334 misc optional gramadoir_0.6-3_all.deb
 67c40b5541749720eef128f5e35fc859 2749572 perl optional 
liblingua-ga-gramadoir-perl_0.6-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIKrCkQTK/kCo4XFcRAvNcAKCGXhoACHhYtMg11H0Uai57KsTwCQCfVaZt
xHObFmhn2mP9NCUS86QewWY=
=VXVg
-END PGP SIGNATURE-


Accepted:
gramadoir_0.6-3.diff.gz
  to pool/main/g/gramadoir/gramadoir_0.6-3.diff.gz
gramadoir_0.6-3.dsc
  to pool/main/g/gramadoir/gramadoir_0.6-3.dsc
gramadoir_0.6-3_all.deb
  to pool/main/g/gramadoir/gramadoir_0.6-3_all.deb
liblingua-ga-gramadoir-perl_0.6-3_all.deb
  to pool/main/g/gramadoir/liblingua-ga-gramadoir-perl_0.6-3_all.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted asterisk-sounds-extra 1.4.7-1 (source all)

2008-05-15 Thread Mark Purcell

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 20:51:33 +1000
Source: asterisk-sounds-extra
Binary: asterisk-sounds-extra
Architecture: source all
Version: 1.4.7-1
Distribution: unstable
Urgency: low
Maintainer: Debian VoIP Team [EMAIL PROTECTED]
Changed-By: Mark Purcell [EMAIL PROTECTED]
Description: 
 asterisk-sounds-extra - Additional sound files for the Asterisk PBX
Closes: 450238 453722
Changes: 
 asterisk-sounds-extra (1.4.7-1) unstable; urgency=low
 .
   [ Mark Purcell ]
   * New upstream release
 - overwrites hours.gsm which is also in package asterisk-sounds-main
 (Closes: #453722)
   * Switch to cdbs
 .
   [ Kilian Krause ]
   * Update debian/watch
 .
   [ Faidon Liambotis ]
   * Add Homepage field as added in dpkg-dev 1.14.6.
   * Add myself to Uploaders.
   * Add Recommends: asterisk
   * Fix debian/watch by using a pkg-voip wrapper to avoid upstream's silly
 redirections. (Closes: #450238)
Checksums-Sha1: 
 565566cfe0ecf6554f221b266f69f0674b3f3663 1507 asterisk-sounds-extra_1.4.7-1.dsc
 a38ef300e5bb30eb6768154a6ef8c64f0b2f8347 3155242 
asterisk-sounds-extra_1.4.7.orig.tar.gz
 17b6425e9dc98fd637ceaa90e7867a5e8182289c 2339 
asterisk-sounds-extra_1.4.7-1.diff.gz
 68e5ffe131283b21008aa03210ca513cf21fafcd 3224160 
asterisk-sounds-extra_1.4.7-1_all.deb
Checksums-Sha256: 
 7bd5f2a9d9573b4fa4a55a507d14ea5dd6564434f6c8b5a02495867cd1dcabcd 1507 
asterisk-sounds-extra_1.4.7-1.dsc
 de15f3dbf5e1688ebb853e84439d2ef48fd7eab66b1e19469485ed6e47e66161 3155242 
asterisk-sounds-extra_1.4.7.orig.tar.gz
 714ef0a85c93bf00d7595ac0a72b1c0e0b0812514646b6e00c5c258e4b2e4c37 2339 
asterisk-sounds-extra_1.4.7-1.diff.gz
 7d32006ad5052a54e043e9c0ace5a86b907f5adf3a58b745b8f6fc841da46619 3224160 
asterisk-sounds-extra_1.4.7-1_all.deb
Files: 
 1bd0441ebff9b4ef9d61e4ea4dbab79d 1507 comm optional 
asterisk-sounds-extra_1.4.7-1.dsc
 c5ac7e08d98762d5cbb59b0838370fc9 3155242 comm optional 
asterisk-sounds-extra_1.4.7.orig.tar.gz
 e3ab5f1b6130c420261c3a4e55b63a51 2339 comm optional 
asterisk-sounds-extra_1.4.7-1.diff.gz
 db8c786afb276d84aafffeab02835cdb 3224160 comm optional 
asterisk-sounds-extra_1.4.7-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILBXnoCzanz0IthIRAiT8AJsEAbIF5xQ67cCF6e28eie5Dh8APgCggwiG
RlehbBM0kcCrr78sYlFGrUY=
=033b
-END PGP SIGNATURE-


Accepted:
asterisk-sounds-extra_1.4.7-1.diff.gz
  to pool/main/a/asterisk-sounds-extra/asterisk-sounds-extra_1.4.7-1.diff.gz
asterisk-sounds-extra_1.4.7-1.dsc
  to pool/main/a/asterisk-sounds-extra/asterisk-sounds-extra_1.4.7-1.dsc
asterisk-sounds-extra_1.4.7-1_all.deb
  to pool/main/a/asterisk-sounds-extra/asterisk-sounds-extra_1.4.7-1_all.deb
asterisk-sounds-extra_1.4.7.orig.tar.gz
  to pool/main/a/asterisk-sounds-extra/asterisk-sounds-extra_1.4.7.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted octave-specfun 1.0.6-1 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 13:05:29 +0200
Source: octave-specfun
Binary: octave-specfun
Architecture: source i386
Version: 1.0.6-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber [EMAIL PROTECTED]
Description: 
 octave-specfun - special mathematical functions for Octave
Changes: 
 octave-specfun (1.0.6-1) unstable; urgency=low
 .
   [ Ólafur Jens Sigurðsson ]
   * New upstream version
Checksums-Sha1: 
 c9f13f3df814bb0a055fee87ea3768f13b561bea 1427 octave-specfun_1.0.6-1.dsc
 e5d85212f9bb698268e2851061989c16af48b6fc 50999 octave-specfun_1.0.6.orig.tar.gz
 77ddbdb0b78a50ed1159811f1f0719f6cbe3aadc 1336 octave-specfun_1.0.6-1.diff.gz
 f530425c02220207c84da8ce956b4c4c17697a16 62816 octave-specfun_1.0.6-1_i386.deb
Checksums-Sha256: 
 a75c599681cc83ad7611c5f96e56f3ee6146722844ad3d21a48ecda6b6f72629 1427 
octave-specfun_1.0.6-1.dsc
 f2fd1d9d33904b977ea0c3a3984ac935a53a8cecb1f6f391cfacb27b11b1de00 50999 
octave-specfun_1.0.6.orig.tar.gz
 883aaa5498165b1109084bd1f162defdfb34192e515a27a4e17f76ea3f3fccb3 1336 
octave-specfun_1.0.6-1.diff.gz
 91700294cdf48f5a3f76c438cc1612070c3d5d5847a2f30c8298e5057867a750 62816 
octave-specfun_1.0.6-1_i386.deb
Files: 
 1d8ce414f4674c77ce210b5d97011d73 1427 math optional octave-specfun_1.0.6-1.dsc
 4783835af19cc8a16933628bcb31c154 50999 math optional 
octave-specfun_1.0.6.orig.tar.gz
 14fe7ea3b8fd7609a9939af050145458 1336 math optional 
octave-specfun_1.0.6-1.diff.gz
 b07dd1d34690cd46dfa85e1565cf52ee 62816 math optional 
octave-specfun_1.0.6-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILBokPqD4a3lPnXwRAjjqAJ94XCOeTuu9VshGg1XNDbUB4sO9+gCfUXTD
06G/OMovWoOvUw8V5zVyu/8=
=lNfg
-END PGP SIGNATURE-


Accepted:
octave-specfun_1.0.6-1.diff.gz
  to pool/main/o/octave-specfun/octave-specfun_1.0.6-1.diff.gz
octave-specfun_1.0.6-1.dsc
  to pool/main/o/octave-specfun/octave-specfun_1.0.6-1.dsc
octave-specfun_1.0.6-1_i386.deb
  to pool/main/o/octave-specfun/octave-specfun_1.0.6-1_i386.deb
octave-specfun_1.0.6.orig.tar.gz
  to pool/main/o/octave-specfun/octave-specfun_1.0.6.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted italc 1:1.0.8-1 (source i386)

2008-05-15 Thread Patrick Winnertz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 13 May 2008 10:54:16 +0200
Source: italc
Binary: italc-master italc-client libitalc
Architecture: source i386
Version: 1:1.0.8-1
Distribution: unstable
Urgency: low
Maintainer: Patrick Winnertz [EMAIL PROTECTED]
Changed-By: Patrick Winnertz [EMAIL PROTECTED]
Description: 
 italc-client - Intelligent Teaching and Learning with Computers
 italc-master - Intelligent Teaching and Learning with Computers
 libitalc   - Intelligent Teaching and Learning with Computers
Closes: 477022
Changes: 
 italc (1:1.0.8-1) unstable; urgency=low
 .
   * Fix FTBFS by switching from openssl to libssl-dev build-dep.
 Thanks to Laurent Bigonville [EMAIL PROTECTED] (Closes: #477022)
   * Packaging new upstream version.
   *
Checksums-Sha1: 
 f65d46c149ec4690e2baf33b5f5d8443c36b5f3d 1089 italc_1.0.8-1.dsc
 1dcac01e7c54a0004ad6415a6d59eef9f50eea68 3084830 italc_1.0.8.orig.tar.gz
 07630c4fa53b5f9c8dd2d76fef1f6733114a03d3 5084 italc_1.0.8-1.diff.gz
 b2f98e6b40194a44c677fd4294ad2d088a97a878 1099172 italc-master_1.0.8-1_i386.deb
 3c4eed1574cc99a2b488ac91fbe1a3e6b26ac4fb 518142 italc-client_1.0.8-1_i386.deb
 b9ca56e2f911fda60ff14863e31af1c4dcf7350d 227892 libitalc_1.0.8-1_i386.deb
Checksums-Sha256: 
 082664863836f30b5e1248ec118b6480d29eec5d6cb12759db506cc827311e95 1089 
italc_1.0.8-1.dsc
 14be9b2e8348eceaa81c2c90c5ad822997fc7da36620da7c4d6357f0912c0da2 3084830 
italc_1.0.8.orig.tar.gz
 53a4d900960f2e1a4457312ea9fec464e1b6c8ebc00cccaa8d7e8ef63d67c78e 5084 
italc_1.0.8-1.diff.gz
 a2dafbae245c03191e393b851841575d8374db4e85db6f0a37af4213d7ff7345 1099172 
italc-master_1.0.8-1_i386.deb
 68870cfcc8868470d7b8985132672ae45db5104fcf14ca01c0a0888d2f81642a 518142 
italc-client_1.0.8-1_i386.deb
 e02a01b6f01dd39c782f9abe674ecfa6e5fe816776120ef8ebdeee1af6d055a9 227892 
libitalc_1.0.8-1_i386.deb
Files: 
 d7d3696d1f19acf6e4c3e7e3fcda368d 1089 x11 optional italc_1.0.8-1.dsc
 2f1dae1aef6bdca58bcdcc0c832a127e 3084830 x11 optional italc_1.0.8.orig.tar.gz
 1c901b20c391a320dacf5927c4c55753 5084 x11 optional italc_1.0.8-1.diff.gz
 d69208518716d13851ac07cb109a41d1 1099172 x11 optional 
italc-master_1.0.8-1_i386.deb
 17169de02cb5549f48bf297c920ce3f0 518142 x11 optional 
italc-client_1.0.8-1_i386.deb
 344a62f750759b835d37582796e7ea22 227892 x11 optional libitalc_1.0.8-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILBv7zgm26bkTFDoRAuPeAKDBrA6QGWD9dhuwiY9fKclgDtB+8wCgv/mW
uP8XQ8ygkfsMr6BTEPGGnMk=
=HgC+
-END PGP SIGNATURE-


Accepted:
italc-client_1.0.8-1_i386.deb
  to pool/main/i/italc/italc-client_1.0.8-1_i386.deb
italc-master_1.0.8-1_i386.deb
  to pool/main/i/italc/italc-master_1.0.8-1_i386.deb
italc_1.0.8-1.diff.gz
  to pool/main/i/italc/italc_1.0.8-1.diff.gz
italc_1.0.8-1.dsc
  to pool/main/i/italc/italc_1.0.8-1.dsc
italc_1.0.8.orig.tar.gz
  to pool/main/i/italc/italc_1.0.8.orig.tar.gz
libitalc_1.0.8-1_i386.deb
  to pool/main/i/italc/libitalc_1.0.8-1_i386.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted octave-splines 1.0.5-1 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 12:47:15 +0200
Source: octave-splines
Binary: octave-splines
Architecture: source all
Version: 1.0.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber [EMAIL PROTECTED]
Description: 
 octave-splines - cubic spline functions for Octave
Changes: 
 octave-splines (1.0.5-1) unstable; urgency=low
 .
   [ Ólafur Jens Sigurðsson ]
   * New upstream version
Checksums-Sha1: 
 56ea53971fe4475e491e2cabff6751cdec6f0650 1427 octave-splines_1.0.5-1.dsc
 c1ef7554db7c23c8d5f3dd22b6fd34cd8191d664 34141 octave-splines_1.0.5.orig.tar.gz
 0ceca0a54835d9f3538eddb6f1f9516d40979360 1209 octave-splines_1.0.5-1.diff.gz
 d7187ce5652b125084b964d92a4bf332693d7061 27910 octave-splines_1.0.5-1_all.deb
Checksums-Sha256: 
 304ca487ad2204ec20fc3b860c39691cef332e83644e149ea51391e768cabc82 1427 
octave-splines_1.0.5-1.dsc
 d68eee1b5f5e60f337230b66402ac85c19751bda2653d036e3c38b7aa075b7cd 34141 
octave-splines_1.0.5.orig.tar.gz
 035acb66fc3df26432c0cee1a9e6266aa5752fcd3643c067c74ea5a41bba8ff0 1209 
octave-splines_1.0.5-1.diff.gz
 88c865fecec26058b01cebd14d0a59964cc38a302509b05917bc44267cce178f 27910 
octave-splines_1.0.5-1_all.deb
Files: 
 b8319265a8bc23541c23d9a5b2b538db 1427 math optional octave-splines_1.0.5-1.dsc
 020796a7b10564b58ad23feeb2b2006d 34141 math optional 
octave-splines_1.0.5.orig.tar.gz
 a75b5c2b608ef46dbbc47ed51e745e72 1209 math optional 
octave-splines_1.0.5-1.diff.gz
 462618011dc2728ca6ef41935fa99336 27910 math optional 
octave-splines_1.0.5-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILBirPqD4a3lPnXwRAm7lAJ99oLEhB3vHPiEJ6Y/Rjjq/Hbn5MgCfRBlL
epHe0f5lBYELa7bwWGskGGc=
=veLq
-END PGP SIGNATURE-


Accepted:
octave-splines_1.0.5-1.diff.gz
  to pool/main/o/octave-splines/octave-splines_1.0.5-1.diff.gz
octave-splines_1.0.5-1.dsc
  to pool/main/o/octave-splines/octave-splines_1.0.5-1.dsc
octave-splines_1.0.5-1_all.deb
  to pool/main/o/octave-splines/octave-splines_1.0.5-1_all.deb
octave-splines_1.0.5.orig.tar.gz
  to pool/main/o/octave-splines/octave-splines_1.0.5.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted libcatalyst-modules-perl 29 (source all)

2008-05-15 Thread eloy

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 24 Apr 2008 12:39:41 +0200
Source: libcatalyst-modules-perl
Binary: libcatalyst-modules-perl
Architecture: source all
Version: 29
Distribution: unstable
Urgency: low
Maintainer: Debian Catalyst Maintainers [EMAIL PROTECTED]
Changed-By: Krzysztof Krzyżaniak (eloy) [EMAIL PROTECTED]
Description: 
 libcatalyst-modules-perl - Modules for Catalyst
Changes: 
 libcatalyst-modules-perl (29) unstable; urgency=low
 .
   * debian/control: narrow dependency from libcatalyst-perl to (= 5.7012-7)
   * Updated modules:
+ Test::WWW::Mechanize::Catalyst 0.42
+ Catalyst::Action::RenderView 0.08
+ Catalyst::Plugin::ConfigLoader 0.20
+ Catalyst::Plugin::Session::Store::DBI 0.13
Checksums-Sha1: 
 8c7ca17f3b9850c08b0b71c75309cab44f5b4ad4 1936 libcatalyst-modules-perl_29.dsc
 871daf80b85e2dc32e93fe58e0d42c0b2699a653 892958 
libcatalyst-modules-perl_29.tar.gz
 74650619439166a0f96454401c095ad8878f723f 773228 
libcatalyst-modules-perl_29_all.deb
Checksums-Sha256: 
 2eaab8d8dde1436612f1168ffab9c395bcfb37b14058dd28750adf7a6448cd0a 1936 
libcatalyst-modules-perl_29.dsc
 8e16f14a0f0ce2c72afef33b8e221d63fd80f055b605c51fb5adff37a45f5986 892958 
libcatalyst-modules-perl_29.tar.gz
 33e2fa42f50b9127a849c76140d36cf2523af49ae653f3c40b9933925879b7b3 773228 
libcatalyst-modules-perl_29_all.deb
Files: 
 ca82b8b069463212e97c3383df41061e 1936 perl optional 
libcatalyst-modules-perl_29.dsc
 046eabee1c49dec474b3e49e9a9c46d4 892958 perl optional 
libcatalyst-modules-perl_29.tar.gz
 f0a4619454a792e573356c956cecdb3e 773228 perl optional 
libcatalyst-modules-perl_29_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILCi3y+HP4f7iC8sRAlOyAJ9bXIVSFvSlIP/bBWG/TuSQqIHhYgCfTgkp
mvKmivJ2avkTICBeKnr1z+M=
=+hsa
-END PGP SIGNATURE-


Accepted:
libcatalyst-modules-perl_29.dsc
  to pool/main/libc/libcatalyst-modules-perl/libcatalyst-modules-perl_29.dsc
libcatalyst-modules-perl_29.tar.gz
  to pool/main/libc/libcatalyst-modules-perl/libcatalyst-modules-perl_29.tar.gz
libcatalyst-modules-perl_29_all.deb
  to pool/main/libc/libcatalyst-modules-perl/libcatalyst-modules-perl_29_all.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted octave-sockets 1.0.4-1 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 13:28:47 +0200
Source: octave-sockets
Binary: octave-sockets
Architecture: source i386
Version: 1.0.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber [EMAIL PROTECTED]
Description: 
 octave-sockets - communication through Internet sokects in Octave
Changes: 
 octave-sockets (1.0.4-1) unstable; urgency=low
 .
   [ Ólafur Jens Sigurðsson ]
   * New upstream version
 .
   [ Thomas Weber ]
   * Drop patch pkg-add-autoloads.diff, applied (somewhat) upstream.
   * debian/rules, debian/control: Drop dependency on quilt, no more patches
 currently.
Checksums-Sha1: 
 2b364cb8e35d55e4b61e1647a4955b32afd29bbe 1427 octave-sockets_1.0.4-1.dsc
 f6fd497472d0eec305c3e1a39b41796c3756a226 14222 octave-sockets_1.0.4.orig.tar.gz
 e319ca1312f644fbcef22a55cfc9b8a8d7a974bf 1370 octave-sockets_1.0.4-1.diff.gz
 a4c259536b049e8ed7814d50c009ea5477039b37 34146 octave-sockets_1.0.4-1_i386.deb
Checksums-Sha256: 
 fa6081e8f8871956a668c876ef915313fc9b0fdfd816454da3308e77e6c12bfe 1427 
octave-sockets_1.0.4-1.dsc
 a65c9134196ab9a1d910a0b1d99fa6bf7acce684e9e1dab6b4a3e0e6b63560cd 14222 
octave-sockets_1.0.4.orig.tar.gz
 03da65364c03dd1b1549ca1482e2dc7269a1282c3e468209efb20d5ba4aacec5 1370 
octave-sockets_1.0.4-1.diff.gz
 8237b8be1b1e1a966fca174a38ded6dde954b4954097578f1a2d062044b4fc23 34146 
octave-sockets_1.0.4-1_i386.deb
Files: 
 f0f7bd2f76ba0329eb27ce797af9278a 1427 math optional octave-sockets_1.0.4-1.dsc
 6a70a287abc7d3e9977c07c5da686c47 14222 math optional 
octave-sockets_1.0.4.orig.tar.gz
 bf14b2f07bdc23babb549338b0c8c698 1370 math optional 
octave-sockets_1.0.4-1.diff.gz
 25bac66b5fa6375277af3b808d4ab833 34146 math optional 
octave-sockets_1.0.4-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILCY8PqD4a3lPnXwRAkpXAJ9YWiYJbpfkDjZYUeIrWB4cKBjljwCgly+6
yy+S/tgy+XhYVc05/IlqMNg=
=6mZZ
-END PGP SIGNATURE-


Accepted:
octave-sockets_1.0.4-1.diff.gz
  to pool/main/o/octave-sockets/octave-sockets_1.0.4-1.diff.gz
octave-sockets_1.0.4-1.dsc
  to pool/main/o/octave-sockets/octave-sockets_1.0.4-1.dsc
octave-sockets_1.0.4-1_i386.deb
  to pool/main/o/octave-sockets/octave-sockets_1.0.4-1_i386.deb
octave-sockets_1.0.4.orig.tar.gz
  to pool/main/o/octave-sockets/octave-sockets_1.0.4.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted audacious-plugins 1.5.0-2 (source i386)

2008-05-15 Thread William Pitcock

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 06:21:07 -0500
Source: audacious-plugins
Binary: audacious-plugins audacious-plugins-extra audacious-plugins-dev
Architecture: source i386
Version: 1.5.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Audacious Packagers [EMAIL PROTECTED]
Changed-By: William Pitcock [EMAIL PROTECTED]
Description: 
 audacious-plugins - Base plugins for audacious
 audacious-plugins-dev - Audacious-plugins development library and header files
 audacious-plugins-extra - Various extra plugins for audacious
Closes: 471041
Changes: 
 audacious-plugins (1.5.0-2) unstable; urgency=low
 .
   * Remove unnecessary Pre-Depends. (Closes: #471041)
Checksums-Sha1: 
 77ee37e5137534e0c9881f1741e69ae86b7a7286 2447 audacious-plugins_1.5.0-2.dsc
 cb58964f6cd31211d7aabdab2f8112c864fa44f3 10836 
audacious-plugins_1.5.0-2.diff.gz
 3d6b0d9cdb4de324f937af9eae3e58b9ae110fe3 419274 
audacious-plugins_1.5.0-2_i386.deb
 88ee47a82a57a18fbad97ab5788820f4c86b7e97 1144912 
audacious-plugins-extra_1.5.0-2_i386.deb
 37a0bcd291c87cc5490ee4720b289503c501ff17 1326 
audacious-plugins-dev_1.5.0-2_i386.deb
Checksums-Sha256: 
 0d28fead0dea78ca42ee8605a577935e4db1659352d408ef418501da82cbe0f3 2447 
audacious-plugins_1.5.0-2.dsc
 beda4a093e798cce4708a5c418e955d6f9ac860734891a2a5f192e3477f2b92d 10836 
audacious-plugins_1.5.0-2.diff.gz
 f7c7dd0e04bf25f5eba302b8a3b678b4bb0e0d583db3d37d6998b895ff82bb74 419274 
audacious-plugins_1.5.0-2_i386.deb
 63da7c8b115c5c6b4e5369561fa22835c26f81955788c890095c496ed736f067 1144912 
audacious-plugins-extra_1.5.0-2_i386.deb
 74d18bc59c36bf41c089d9e764b4f33b2a78e66d12d149f0c78c7a3b775c92b2 1326 
audacious-plugins-dev_1.5.0-2_i386.deb
Files: 
 86051c9980078ece27a9c734b857c5ff 2447 sound optional 
audacious-plugins_1.5.0-2.dsc
 8629eacacd63eba4c3fb857735f0c834 10836 sound optional 
audacious-plugins_1.5.0-2.diff.gz
 6b8b93774a4f4fdba2a5b7de5e722640 419274 sound optional 
audacious-plugins_1.5.0-2_i386.deb
 8b07a085514213a31aabc9a164f0fb18 1144912 sound optional 
audacious-plugins-extra_1.5.0-2_i386.deb
 3ece155a93290e7f3bb2601ee1fd23f7 1326 devel optional 
audacious-plugins-dev_1.5.0-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILCv7ibPvMsrqrwMRAp0AAKDHJvYcbbPZgRQEsc2Gz6wCHJhqRACfTike
QHV49g+yMUKMHHG7ejbmIBM=
=ZNUD
-END PGP SIGNATURE-


Accepted:
audacious-plugins-dev_1.5.0-2_i386.deb
  to pool/main/a/audacious-plugins/audacious-plugins-dev_1.5.0-2_i386.deb
audacious-plugins-extra_1.5.0-2_i386.deb
  to pool/main/a/audacious-plugins/audacious-plugins-extra_1.5.0-2_i386.deb
audacious-plugins_1.5.0-2.diff.gz
  to pool/main/a/audacious-plugins/audacious-plugins_1.5.0-2.diff.gz
audacious-plugins_1.5.0-2.dsc
  to pool/main/a/audacious-plugins/audacious-plugins_1.5.0-2.dsc
audacious-plugins_1.5.0-2_i386.deb
  to pool/main/a/audacious-plugins/audacious-plugins_1.5.0-2_i386.deb


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted rsyncrypto 1.09-1 (source i386)

2008-05-15 Thread Shachar Shemesh

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 15:09:43 +0300
Source: rsyncrypto
Binary: rsyncrypto
Architecture: source i386
Version: 1.09-1
Distribution: unstable
Urgency: low
Maintainer: Shachar Shemesh [EMAIL PROTECTED]
Changed-By: Shachar Shemesh [EMAIL PROTECTED]
Description: 
 rsyncrypto - rsync friendly encryption
Changes: 
 rsyncrypto (1.09-1) unstable; urgency=low
 .
   * New upstream release
   * New tool, rsyncrypto_recover, for recovering corrupted file maps
Checksums-Sha1: 
 a729e0be43f18ede9ad7734a2666575c88120edc 1003 rsyncrypto_1.09-1.dsc
 8bf4b0bed9f8a57427003df3ab7e18939bdf3f67 418717 rsyncrypto_1.09.orig.tar.gz
 16dec51a1dfc116f8a8b90a744929cfc1ac92543 26842 rsyncrypto_1.09-1.diff.gz
 e5fef4d7702efa9bae389987eb284ee4b0f88561 300456 rsyncrypto_1.09-1_i386.deb
Checksums-Sha256: 
 d4c47eaa7e3af929ba8b7da1696e5dc2f38007eb3826caba7bb64dbe2f32014a 1003 
rsyncrypto_1.09-1.dsc
 af9d3bc690a36905c108db9636ea6b47cbc37da0f6ecdd099b30216d954c88c7 418717 
rsyncrypto_1.09.orig.tar.gz
 7ea78b55b08fee24cd3190f2db0ed43c643370eb158792740f1c7c6a026d3e20 26842 
rsyncrypto_1.09-1.diff.gz
 c04ce84371331cd974c4c76d2a35ce287318d9ca6b894a3c3b598e1d15eb8f7b 300456 
rsyncrypto_1.09-1_i386.deb
Files: 
 63fc8d36570ff5c33ce678c28ea9b0cb 1003 utils optional rsyncrypto_1.09-1.dsc
 1fc648f9533ded3ab24e6316f869c3e4 418717 utils optional 
rsyncrypto_1.09.orig.tar.gz
 c7d76170809166b5830879e236a56f9f 26842 utils optional rsyncrypto_1.09-1.diff.gz
 b35d262d0cc8ffc8cafba067ee01964c 300456 utils optional 
rsyncrypto_1.09-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILCxdg8ByFc29vOIRAve9AJ4l5h5LyGcQn/QYlqg8cNXKQE8NDgCeOPQX
aszcUtyYVWZHcr/2w/x6m5o=
=m3WW
-END PGP SIGNATURE-


Accepted:
rsyncrypto_1.09-1.diff.gz
  to pool/main/r/rsyncrypto/rsyncrypto_1.09-1.diff.gz
rsyncrypto_1.09-1.dsc
  to pool/main/r/rsyncrypto/rsyncrypto_1.09-1.dsc
rsyncrypto_1.09-1_i386.deb
  to pool/main/r/rsyncrypto/rsyncrypto_1.09-1_i386.deb
rsyncrypto_1.09.orig.tar.gz
  to pool/main/r/rsyncrypto/rsyncrypto_1.09.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted zaptel 1:1.4.10.1~dfsg-1 (source all powerpc)

2008-05-15 Thread Tzafrir Cohen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu,  8 May 2008 02:03:34 +0300
Source: zaptel
Binary: zaptel libtonezone1 libtonezone-dev zaptel-source
Architecture: source all powerpc
Version: 1:1.4.10.1~dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Debian VoIP Team [EMAIL PROTECTED]
Changed-By: Tzafrir Cohen [EMAIL PROTECTED]
Description: 
 libtonezone-dev - tonezone library (development)
 libtonezone1 - tonezone library (runtime)
 zaptel - zapata telephony utilities
 zaptel-source - Zapata telephony interface (source code for kernel driver)
Changes: 
 zaptel (1:1.4.10.1~dfsg-1) unstable; urgency=low
 .
   [ Tzafrir Cohen ]
   * New upstream bugfix release.
   * Note the buid error from http://bugs.digium.com/12426 .
   * Fix the generation of tonezone.txt.
   * Patch xpp_fix_t1: allow the xpp pri module to initialize as T1.
   * Set OSLEC as the default echo canceller.
   * The unload init.d script operation will now also attempt to unload
 oslec.
Checksums-Sha1: 
 7122be4867299ca40e85b2608c3f940174635026 1420 zaptel_1.4.10.1~dfsg-1.dsc
 6a242858bc79fe186bf7555689793f6858168a3c 1430747 
zaptel_1.4.10.1~dfsg.orig.tar.gz
 87de784d49717a123410c058aae8d5c1d015aa85 184287 zaptel_1.4.10.1~dfsg-1.diff.gz
 f36ba884e156eee4d34ea6bca70012cd361c262d 1170406 
zaptel-source_1.4.10.1~dfsg-1_all.deb
 9a9f77fcd0e755967d506918eed9ab64dd5540fd 304614 
zaptel_1.4.10.1~dfsg-1_powerpc.deb
 f26d329590b8b6afe20673ff006c1be5e0f7ef55 72666 
libtonezone1_1.4.10.1~dfsg-1_powerpc.deb
 9b70f3b0022ba4eb3ba3c32f5a4f91b14f06b5f4 70968 
libtonezone-dev_1.4.10.1~dfsg-1_powerpc.deb
Checksums-Sha256: 
 a77eca11a7dd86e723d75a909b32d3a03f59431feab293dfe91dcf5b032aa99c 1420 
zaptel_1.4.10.1~dfsg-1.dsc
 f696ec456f0065fcc1948355ebb5b0b4cb640bdd9b2c363ea53365ada02bd5b3 1430747 
zaptel_1.4.10.1~dfsg.orig.tar.gz
 6fd04dbf33fad4b9dd19d68441a669380193029340bbc7953b338b66cfd14416 184287 
zaptel_1.4.10.1~dfsg-1.diff.gz
 e1652d39a420daaaf660a854dcd95d8900d21d3252c759ad1068353318884f97 1170406 
zaptel-source_1.4.10.1~dfsg-1_all.deb
 d0baad13f33b5e4315885ee207221784c02b1d7f0c24d0b57132d9e6cf8804f7 304614 
zaptel_1.4.10.1~dfsg-1_powerpc.deb
 d8ebc7c23e2ea724527e7b85339693f2b5edc6a39c222fb0405da91e5ffc1edb 72666 
libtonezone1_1.4.10.1~dfsg-1_powerpc.deb
 38ee0f35ce7b33c09c377e3352c868b7b0ac604193e4d1bc005890fb3b0b85f3 70968 
libtonezone-dev_1.4.10.1~dfsg-1_powerpc.deb
Files: 
 7afb24fed8bb5d5d93718a60ce5ef91b 1420 comm optional zaptel_1.4.10.1~dfsg-1.dsc
 6e51976e68ab733ac7d0b944e63e50ec 1430747 comm optional 
zaptel_1.4.10.1~dfsg.orig.tar.gz
 273b78dd09da61aa56b911d5055d8a74 184287 comm optional 
zaptel_1.4.10.1~dfsg-1.diff.gz
 b95d7f81b52c1d752cffb7980a3fa6ba 1170406 devel optional 
zaptel-source_1.4.10.1~dfsg-1_all.deb
 7b7eaa20a51b3a6a867dff975a62ac9b 304614 comm optional 
zaptel_1.4.10.1~dfsg-1_powerpc.deb
 5c9946d53a6f3db407775077efaf498f 72666 libs optional 
libtonezone1_1.4.10.1~dfsg-1_powerpc.deb
 0449d1c73ecc39aceedc2f3ae793 70968 libdevel optional 
libtonezone-dev_1.4.10.1~dfsg-1_powerpc.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILC67oCzanz0IthIRAkwvAJ9wl63N+zVvbA0vpd9TnM5hVehKSACfVWqV
ZnlLTIRoLnx+tD+VKwDHnes=
=n06h
-END PGP SIGNATURE-


Accepted:
libtonezone-dev_1.4.10.1~dfsg-1_powerpc.deb
  to pool/main/z/zaptel/libtonezone-dev_1.4.10.1~dfsg-1_powerpc.deb
libtonezone1_1.4.10.1~dfsg-1_powerpc.deb
  to pool/main/z/zaptel/libtonezone1_1.4.10.1~dfsg-1_powerpc.deb
zaptel-source_1.4.10.1~dfsg-1_all.deb
  to pool/main/z/zaptel/zaptel-source_1.4.10.1~dfsg-1_all.deb
zaptel_1.4.10.1~dfsg-1.diff.gz
  to pool/main/z/zaptel/zaptel_1.4.10.1~dfsg-1.diff.gz
zaptel_1.4.10.1~dfsg-1.dsc
  to pool/main/z/zaptel/zaptel_1.4.10.1~dfsg-1.dsc
zaptel_1.4.10.1~dfsg-1_powerpc.deb
  to pool/main/z/zaptel/zaptel_1.4.10.1~dfsg-1_powerpc.deb
zaptel_1.4.10.1~dfsg.orig.tar.gz
  to pool/main/z/zaptel/zaptel_1.4.10.1~dfsg.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted octave-odebvp 1.0.4-1 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 14:47:23 +0200
Source: octave-odebvp
Binary: octave-odebvp
Architecture: source all
Version: 1.0.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber [EMAIL PROTECTED]
Description: 
 octave-odebvp - linear ordinary differential equations package for Octave
Changes: 
 octave-odebvp (1.0.4-1) unstable; urgency=low
 .
   [ Ólafur Jens Sigurðsson ]
   * New upstream version
Checksums-Sha1: 
 cff848d7bbaf96a8786d3e6fee0c169fd27a68dc 1416 octave-odebvp_1.0.4-1.dsc
 f36fc6480ebb64a93b7900f7f7692dbe29a9f903 17309 octave-odebvp_1.0.4.orig.tar.gz
 594d1cb5f4f30b5395942488d8e9882a4411e910 1174 octave-odebvp_1.0.4-1.diff.gz
 82f9b0d7753f00fb2378f6afaf74bfff29594590 11420 octave-odebvp_1.0.4-1_all.deb
Checksums-Sha256: 
 724cabc7d7904430c28db7c3f04ba42fa7c6ecb907de7d5faaef7a7b3146bd26 1416 
octave-odebvp_1.0.4-1.dsc
 2e4d23eb398c889532132f90c01bbffd5e49da917eb7f423a12b1b3ff515e108 17309 
octave-odebvp_1.0.4.orig.tar.gz
 76fffe3f9d56ec0e50c99d649e8cc5951c993cb9d43905c2f781342c256f3909 1174 
octave-odebvp_1.0.4-1.diff.gz
 b9b2c740c0293d52f408ff608f2a4b83076d1202b00ddb8312d72fe6bc95d59f 11420 
octave-odebvp_1.0.4-1_all.deb
Files: 
 789c375ff61190fafbe073ad2b17331e 1416 math optional octave-odebvp_1.0.4-1.dsc
 266792970891e79fab7b3fb97421e4b5 17309 math optional 
octave-odebvp_1.0.4.orig.tar.gz
 cd40fefe4c1b09878bdaa3fffc664d32 1174 math optional 
octave-odebvp_1.0.4-1.diff.gz
 edddb4577c3c9dd34b0099f6edc24281 11420 math optional 
octave-odebvp_1.0.4-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILDHoPqD4a3lPnXwRAmdaAJ9RFrMWsRDXYczeoOWx2zRANtqvnwCfcYwE
v1fe5a+Gy1nuGIGOK3uBzwY=
=wSHA
-END PGP SIGNATURE-


Accepted:
octave-odebvp_1.0.4-1.diff.gz
  to pool/main/o/octave-odebvp/octave-odebvp_1.0.4-1.diff.gz
octave-odebvp_1.0.4-1.dsc
  to pool/main/o/octave-odebvp/octave-odebvp_1.0.4-1.dsc
octave-odebvp_1.0.4-1_all.deb
  to pool/main/o/octave-odebvp/octave-odebvp_1.0.4-1_all.deb
octave-odebvp_1.0.4.orig.tar.gz
  to pool/main/o/octave-odebvp/octave-odebvp_1.0.4.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted octave-signal 1.0.7-1 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 15 May 2008 14:28:40 +0200
Source: octave-signal
Binary: octave-signal
Architecture: source i386
Version: 1.0.7-1
Distribution: unstable
Urgency: low
Maintainer: Debian Octave Group [EMAIL PROTECTED]
Changed-By: Thomas Weber [EMAIL PROTECTED]
Description: 
 octave-signal - signal processing functions for Octave
Changes: 
 octave-signal (1.0.7-1) unstable; urgency=low
 .
   [ Ólafur Jens Sigurðsson ]
   * New upstream version
Checksums-Sha1: 
 1124f3feab86b8c10a9aaffcbead423952e455c4 1419 octave-signal_1.0.7-1.dsc
 a8aa6ec455ad7222cfaaf735a4f2b62f46962dea 155684 octave-signal_1.0.7.orig.tar.gz
 b736754e958b1425d74e72d639758cbf94a72f3b 2781 octave-signal_1.0.7-1.diff.gz
 40dd7ae8d88db3c6dd7419bc66bec3639a322eb1 171202 octave-signal_1.0.7-1_i386.deb
Checksums-Sha256: 
 463ebc297f84992b6e7280cc0470983e8604efa97d903b56c38b81cc1f88d1b8 1419 
octave-signal_1.0.7-1.dsc
 6254c23fdeca5d338d3405d39c8e4489cc7439935d71e0253981e94200c8a31c 155684 
octave-signal_1.0.7.orig.tar.gz
 bc32befe4a109d5a7becb6349ba1f5229bb91939f0c5d7d24dc5e099f8145080 2781 
octave-signal_1.0.7-1.diff.gz
 f9a7717a7883e26eb8bcf8fba205f6df6e4005f1051ccd858c4faf626a925650 171202 
octave-signal_1.0.7-1_i386.deb
Files: 
 72144f28b0361e75bc03595127043515 1419 math optional octave-signal_1.0.7-1.dsc
 9fd567bbbad92184eb53656fb873d381 155684 math optional 
octave-signal_1.0.7.orig.tar.gz
 4f4f275e06304d72b437704dccf993f9 2781 math optional 
octave-signal_1.0.7-1.diff.gz
 e65718fdf17fe603b83e24dcbaacfcca 171202 math optional 
octave-signal_1.0.7-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILC6TPqD4a3lPnXwRAljRAKCHUrbNYpRA+kcvwUTpOo3mN0utPgCgoYZQ
HLN0hsFRdvYgN9fkecZjnUg=
=gbCo
-END PGP SIGNATURE-


Accepted:
octave-signal_1.0.7-1.diff.gz
  to pool/main/o/octave-signal/octave-signal_1.0.7-1.diff.gz
octave-signal_1.0.7-1.dsc
  to pool/main/o/octave-signal/octave-signal_1.0.7-1.dsc
octave-signal_1.0.7-1_i386.deb
  to pool/main/o/octave-signal/octave-signal_1.0.7-1_i386.deb
octave-signal_1.0.7.orig.tar.gz
  to pool/main/o/octave-signal/octave-signal_1.0.7.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Accepted octave-sockets 1.0.4-2 (source i386)