date:20070905

Hi,

I might be running on incomplete information, but to me it seems that we
had a package hijack over night. Being an uploader and thus part of the
team I'm more than just interested in this and would like the parties to
speak up here and explain. Here's what I know so far:

Both, Patrick Winnertz and Daniel Baumann ITPed virtualbox at about the
same time without knowing that the other ITPed too. I have no idea
what Daniel really did on the package. I cannot find him in the
changelog file. However, he's listed in one README and in the copyright
file with:

This package was debianized by Daniel Baumann [EMAIL PROTECTED] on
Mon, 15 Jan 2007 14:33:00 +0100.

Please note that the first release which according to the changelog
contains work by Patrick and Philipp Hug was released on August 30th. I
heard about some work being done during Debconf but have no idea if
anything was done between January and June.

Anyway, earlier this week Daniel apparently approached Patrick to be
listed as uploader and was denied which seemingly led to him doing the
upload with this change among others on his own.

To me this is clearly a hijack and I'd like to see a very valid
reasoning for this behaviour.

But he not just added himself, he also changed some packaging stuff and
upgraded to a new upstream version. This seems to be done in a hurry as
he missed some licensing issues. We now have several files in the
archive with the following license:

;
;  Copyright (C) 2006-2007 innotek GmbH
;
;  innotek GmbH confidential
;  All rights reserved

Uh, ouch, shouldn't be there, right? That's why I CC ftpmasters. Work is
underway to create a valid 1.5.0 package, but there's a reason why we
first fixed stuff in the 1.4.0 version. Since this may take another day
or two, I wonder whether out admins would like to react and remover this
version asap.

Michael

-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!


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

Bug#440901: ITP: val-and-rick -- shooter game

Package: wnpp
Severity: wishlist
Owner: Debian Games Team [EMAIL PROTECTED]


* Package name: val-and-rick
  Version : 0.1a
  Upstream Author : Kenta Cho [EMAIL PROTECTED]
* URL : http://www.asahi-net.or.jp/~cs8k-cyu/windows/vr0_1a.zip
* License : BSD
  Programming Lang: D
  Description : shooter game

 Val  Rick is probably the precursor to Gunroar, featuring similar
 controls but in a different environment. Only 2D sprites and backgrounds
 are used in what seems like a tribute to Xevious and Star Soldier.

 Val  Rick is another gem among many by Kenta Cho.


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

Re: virtualbox-ose: package hijack?

Michael Meskes wrote:
 I have no idea
 what Daniel really did on the package.

I did about 90% of the inital packaging.

Can be seen on http://svn.debian.org/wsvn/pkg-virtualbox/

 I cannot find him in the
 changelog file.

Patrick uploaded removed me from changelog in the two last uploads
(virtualbox 1.4.0svn4130-dfsg-1 and virtualbox-ose 1.4.0svn4130-dfsg-1
that is) without notifying me. In all previous uploads to NEW, I was in
the co-maintainer.

Can be seen on http://svn.debian.org/wsvn/pkg-virtualbox/

 Please note that the first release which according to the changelog
 contains work by Patrick and Philipp Hug was released on August 30th. I
 heard about some work being done during Debconf but have no idea if
 anything was done between January and June.

Phillipp asked me about virtualbox on Debconf, I welcomed him and
immediately added him to the alioth project and he uploaded a fixed
version to NEW at the same evening.

 To me this is clearly a hijack and I'd like to see a very valid
 reasoning for this behaviour.

I was removed unjustified from uploaders and just fixed that inital
error from Patrick.

 Uh, ouch, shouldn't be there, right? That's why I CC ftpmasters. Work is
 underway to create a valid 1.5.0 package, but there's a reason why we
 first fixed stuff in the 1.4.0 version. Since this may take another day
 or two, I wonder whether out admins would like to react and remover this
 version asap.

As both me and also Patrick are in contact with upstream, this is a
pending issue solved in hopefully short time.

Upstream is generally cooperative and understands the problems, hence I
see this a bit more relaxed (for the next few days only, until it's
sorted out). However, if ftp-master do disagree, I'll can re-upload
1.4.0, superseeding the 1.5.0 upload.

Regards,
Daniel

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


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

Re: RFC: changes to default password strength checks in pam_unix

2007-09-05 Thread Gabor Gombas

On Tue, Sep 04, 2007 at 08:26:41PM +, Oleg Verych: gmane reading wrote:

 I.e *i don't care* about entering passwords on middle ground, without
 knowing, WTF this installer may do with them, not having comfortable
 environment for that _important_ action.
 
 Thus i have silly, empty passwords after installation. Then, i get my
 imagination and compose really super-druper passwords for root and users
 (that i create myself by script with, IDs i want/have on filesystems, not
 by installation process).

Well, if you give public network access to any machine before the
initial configuration is complete, that's _your_ problem. The UNIX way
was always if the admin wants to shot himself in the foot, let him.

Gabor

-- 
 -
 MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
 -


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

Re: Why no Opera?

2007-09-05 Thread Ben Finney

Johan Herland [EMAIL PROTECTED] writes:

 Thanks for the email. I can assure you that there are many Debianers
 at Opera, although my personal preference is Gentoo. :)
 
 We're genuinely interested in making our product work as well as
 possible on Debian (and as many other distros as practically
 possible).

That's excellent to hear. The best way to make software work in a free
operating system is to release it as free software, so the entire
community can get actively involved in its maintenance. When can we
expect this?

-- 
 \  One thing vampire children have to be taught early on is, |
  `\   don't run with a wooden stake.  -- Jack Handey |
_o__)  |
Ben Finney


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

Re: virtualbox-ose: package hijack?

2007-09-05 Thread Patrick Winnertz

Am Mittwoch, 5. September 2007 11:39:42 schrieb Daniel Baumann:
 I did about 90% of the inital packaging.
I removed one line from the changelog.. sorry for this. I'll readd it 
within the next upload.

 Patrick uploaded removed me from changelog in the two last uploads
 (virtualbox 1.4.0svn4130-dfsg-1 and virtualbox-ose 1.4.0svn4130-dfsg-1
 that is) without notifying me. In all previous uploads to NEW, I was in
 the co-maintainer.
There were only one upload to NEW with you as co-maintainer. This was the 
upload right after debconf.

After this nothing happened at all. 
I started to check in the dfsg- tarball and you remove it again from the 
svn... who should a team work on a package if they doesn't use the same 
tarball at all?

After some weeks were silence and nothing happens. I decided to close *my* 
ITP (there were 3 ITPs for virtualbox... one was mine), without the team 
maintainance on alioth since the removal of the dfsg tarball shows me 
another time that this has no sense so. 

I spoke with you about the removal, but you doesn't listen to me at all. So 
sorry, I started to work further at it with a new team.

  To me this is clearly a hijack and I'd like to see a very valid
  reasoning for this behaviour.

See above. You showed me several times that you wasn't able to team - 
maintain this package. You doesn't listened to me if I try to speak with 
you about this issue in IRC. Both ITPs were over a half year old... much 
time to finish this work. 

 I was removed unjustified from uploaders and just fixed that inital
 error from Patrick.

See above... this wasn't an error. 
We spoke yesterday (Sunday) about this issue in IRC and you ask me if you 
are allowed to reupload the 1.4.0 version with som minor fixes. 
I told you that I have against this strong objections.

For people who can read german here a (small) part from the chat:

09:12:56   panthera | wie ich sehe, hast du mich aus vbox entfernt. 
hast du was dagegen, wenn ich mich als uploader reinsetze und ein paar 
dinge poliere in 1.4.0svn4130-dfsg-2?
09:52:34 winnie | ja.. 
[ ... removed some stuff ... ]
10:38:30   panthera | gut, dann lade ich morgen abend -2 hoch.
10:38:59winnie | nein.
Day changed to 04 Sep 2007
[ ... ]


  Uh, ouch, shouldn't be there, right? That's why I CC ftpmasters. Work
  is underway to create a valid 1.5.0 package, but there's a reason why
  we first fixed stuff in the 1.4.0 version. Since this may take another
  day or two, I wonder whether out admins would like to react and
  remover this version asap.

 As both me and also Patrick are in contact with upstream, this is a
 pending issue solved in hopefully short time.

Sorry... I didn't see you in the vbox-devel channel over a lng time 
period. At least: This issue is already fixed. I regulary speak with the 
upstream authors. But non the less this have to be fixed in debian too. 
I prepared an correct tarball which could be uploaded right after this one 
is removed. 

Please do not upload any corrected version. 


 Upstream is generally cooperative and understands the problems, hence I
 see this a bit more relaxed (for the next few days only, until it's
 sorted out). However, if ftp-master do disagree, I'll can re-upload
 1.4.0, superseeding the 1.5.0 upload.

See above.


In my eyes this is clearly a hijack of the package. We both had ITPs for 
this package and you doesn't act for a long time. If I haven't uploaded it 
last week, I'm sure that nothing would have happened. 
I'll readd this entry to the changelog, yes. But I think a group 
maintaining with us both in this group would fail, since I reallly like to 
communicate everything quite intensive. 

Greetings
Patrick

-- 
 .''`.   Patrick Winnertz [EMAIL PROTECTED]
:  :' :  GNU/Linux Debian-Edu Developer
`. `'`   http://www.der-winnie.de http://d.skolelinux.org/~winnie
  `-  Debian - when you have better things to do than fixing systems


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

Re: Accepted librpcsecgss 0.14-2etch1 (source i386)

2007-09-05 Thread Aníbal Monsalve Salazar

On Wed, Sep 05, 2007 at 07:56:21AM +, Moritz Muehlenhoff wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 26 Aug 2007 20:54:40 +
Source: librpcsecgss
Binary: librpcsecgss-dev librpcsecgss3
Architecture: source i386
Version: 0.14-2etch1
Distribution: stable-security
Urgency: high
Maintainer: Anibal Monsalve Salazar [EMAIL PROTECTED]
Changed-By: Moritz Muehlenhoff [EMAIL PROTECTED]
Description: 
 librpcsecgss-dev - header files and docs for librpcsecgss
 librpcsecgss3 - allows secure rpc communication using the rpcsec_gss protocol
Changes: 
 librpcsecgss (0.14-2etch1) stable-security; urgency=high
 .
   * Fix buffer overflow in RPCSEC_GSS (CVE-2007-3799).

The line above has a typo, it should read CVE-2007-3999 [¹].

[¹] http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-3999

Files: 
 253bb12cce7ac18b200108dfcb430b6a 746 libs optional 
 librpcsecgss_0.14-2etch1.dsc
 0d4cdee46a98731b1b71e30504589281 363503 libs optional 
 librpcsecgss_0.14.orig.tar.gz
 b655fc49163d87b9b0a61ae4ead7721b 1479 libs optional 
 librpcsecgss_0.14-2etch1.diff.gz
 f5482b2709d90570e398c191ccd1893f 41846 libdevel optional 
 librpcsecgss-dev_0.14-2etch1_i386.deb
 56656d7169d4ac2339a1e5ec705ff68d 31140 libs standard 
 librpcsecgss3_0.14-2etch1_i386.deb

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

iD8DBQFG0zzAXm3vHE4uyloRAgKoAJ98+SzGrYEQQxP6THvYjJ3WGYxwyQCgyT/f
tLLKzCYLk+I8zoxMuoabGLU=
=IgmG
-END PGP SIGNATURE-


Accepted:
librpcsecgss-dev_0.14-2etch1_i386.deb
  to pool/main/libr/librpcsecgss/librpcsecgss-dev_0.14-2etch1_i386.deb
librpcsecgss3_0.14-2etch1_i386.deb
  to pool/main/libr/librpcsecgss/librpcsecgss3_0.14-2etch1_i386.deb
librpcsecgss_0.14-2etch1.diff.gz
  to pool/main/libr/librpcsecgss/librpcsecgss_0.14-2etch1.diff.gz
librpcsecgss_0.14-2etch1.dsc
  to pool/main/libr/librpcsecgss/librpcsecgss_0.14-2etch1.dsc

Aníbal Monsalve Salazar
-- 
http://v7w.com/anibal


signature.asc
Description: Digital signature

Re: virtualbox-ose: package hijack?

Patrick Winnertz wrote:
 I started to check in the dfsg- tarball and you remove it again from the 
 svn... who should a team work on a package if they doesn't use the same 
 tarball at all?

tarballs can be produced with the invokation of 'debian/rules upstream'.

it is debatable if the upstream tarball has to be inside the svn, rather
than the alioth webspace (which I recommended you to do instead). other
teams, such as the kernel-team, do it similar. I still do not understand
why this is a problem for you, but that's not actually the point.

 I spoke with you about the removal, but you doesn't listen to me at all. So 
 sorry, I started to work further at it with a new team.

Shall I cite the IRC log? I explained to you why I removed the tarball
and how we should do it in a, imho, better way (means, not storing
tarballs in svn, but on alioth webspace).

 See above. You showed me several times that you wasn't able to team - 
 maintain this package. You doesn't listened to me if I try to speak with 
 you about this issue in IRC.

I fail to see where I did not listen to you.

 We spoke yesterday (Sunday) about this issue in IRC and you ask me if you 
 are allowed to reupload the 1.4.0 version with som minor fixes. 
 I told you that I have against this strong objections.
 
 For people who can read german here a (small) part from the chat:
 
 09:12:56   panthera | wie ich sehe, hast du mich aus vbox entfernt. 
 hast du was dagegen, wenn ich mich als uploader reinsetze und ein paar 
 dinge poliere in 1.4.0svn4130-dfsg-2?
 09:52:34 winnie | ja.. 
 [ ... removed some stuff ... ]

you do cut out the important stuff, where you did give no rational
reason not upload it. instead, you refused to communicate.

 10:38:30   panthera | gut, dann lade ich morgen abend -2 hoch.
 10:38:59winnie | nein.
 Day changed to 04 Sep 2007
 [ ... ]
 

 Sorry... I didn't see you in the vbox-devel channel over a lng time 
 period. At least: This issue is already fixed. I regulary speak with the 
 upstream authors. But non the less this have to be fixed in debian too. 
 I prepared an correct tarball which could be uploaded right after this one 
 is removed. 

great, can you please upload it as 1.5.0-dfsg2-1 then?

 In my eyes this is clearly a hijack of the package.

It's not and I also ask you to not remove me from uploaders in a next
upload.

 We both had ITPs for 
 this package and you doesn't act for a long time. If I haven't uploaded it 
 last week, I'm sure that nothing would have happened.

This is a wild assumption. I'm just back from some intensive work in
real-life last four weeks...

 I'll readd this entry to the changelog, yes. But I think a group 
 maintaining with us both in this group would fail,

For the records: I do appreciate the work you did in the last weeks, and
I also do not care who is listed in the maintainer fields as long as I'm
in the upload field.

 since I reallly like to 
 communicate everything quite intensive. 

Then please do so and use e.g. the alioth mailinglist before removing
people who did the inital grunt wort and like to work on the package too?

Regards,
Daniel

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


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

Bug#440911: ITP: policyd-spf-fs -- Postfix policy server for SPF checking

2007-09-05 Thread Magnus Holmgren

Package: wnpp
Severity: wishlist
Owner: Magnus Holmgren [EMAIL PROTECTED]

* Package name: policyd-spf-fs
  Version : 0+svn21
  Upstream Author : Matthias Cramer [EMAIL PROTECTED]
* URL : http://www.freestone.net/software/policyd-spf-fs/
* License : LGPL 2.1 and/or 2-clause BSD
  Programming Lang: C
  Description : Postfix policy server for SPF checking

policyd-spf-fs is a simple Sender Policy Framework (SPF) policy
engine for the Postfix MTA, written in C.

Postfix SMTP Access Policy Delegation is described at
http://www.postfix.org/SMTPD_POLICY_README.html


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

Re: Bug#440823: ITP: kelbt -- backtracking LR parser

2007-09-05 Thread Robert Lemmen

On Tue, Sep 04, 2007 at 09:24:18PM +0200, Guus Sliepen wrote:
Description : backtracking LR parser
  
   Kelbt generates backtracking LALR(1) parsers. Standard LALR(1) parser
 
 If it is a parser _generator_, mention this in de short description as
 well.

absolutely correct, will update this

 Which CASCON paper? I don't think you should mention this in the
 description. The description is meant for a user to decide if he wants
 to install this package or not. You shouldn't make a user follow
 references, that is besides the point. I also don't think that the
 paragraph about the proof of concept is useful. The only useful
 information is C++. Does Kelbt indeed output C++ code? 

the reference to the paper is indeed a bit weird, but i think the rest
of the paragraph is ok. the information that the tool is capable of
handling a complex case like this, and that the code for it is included
as an example _is_ interesting. will rephrase the paragraph accordingly.

cu  robert

-- 
Robert Lemmen   http://www.semistable.com 


signature.asc
Description: Digital signature

Re: virtualbox-ose: package hijack?

2007-09-05 Thread Joerg Jaspert

On 11133 March 1977, Michael Meskes wrote:

Not rating the act of adding/removing maintainers in an upload, just one
thing:

 But he not just added himself, he also changed some packaging stuff and
 upgraded to a new upstream version. This seems to be done in a hurry as
 he missed some licensing issues. We now have several files in the
 archive with the following license:
 ;  Copyright (C) 2006-2007 innotek GmbH

 ;  innotek GmbH confidential
 ;  All rights reserved

 Uh, ouch, shouldn't be there, right? That's why I CC ftpmasters. Work is
 underway to create a valid 1.5.0 package, but there's a reason why we
 first fixed stuff in the 1.4.0 version. Since this may take another day
 or two, I wonder whether out admins would like to react and remover this
 version asap.

 As both me and also Patrick are in contact with upstream, this is a
 pending issue solved in hopefully short time.

NO. There is absolutely no reason to *knowingly* upload a non-free
tarball, even named .dfsg. People doing that should immediately
resign.

Especially not after that one package here got some 3 or 4 rejects due
to non-free / license problems.

 Upstream is generally cooperative and understands the problems, hence I
 see this a bit more relaxed (for the next few days only, until it's
 sorted out). However, if ftp-master do disagree, I'll can re-upload
 1.4.0, superseeding the 1.5.0 upload.

Yay, Upstream understands the problem, lets upload non-free crap to main does
not work.

Fix it.

-- 
bye Joerg
[2.6.15.4 direkt nach 2.6.15.3]
HE Linus muss Gentooler hassen.
formorer wieso?
HE Naja, die dürften ihre optimierten Kernel gerade fertig gebaut
haben und müssen jetzt aus prompter Versionitis auf das
Ausprobieren verzichten und den neuen kompilieren... 


pgpbbi31P4zBa.pgp
Description: PGP signature

Bug#440914: ITP: sketch -- produce 3D line drawings from scene description language

2007-09-05 Thread David Bremner

Package: wnpp
Severity: wishlist
Owner: David Bremner [EMAIL PROTECTED]


* Package name: sketch
  Version : 0.2.9
  Upstream Author : Eugene Ressler
* URL : http://www.frontiernet.net/~eugene.ressler
* License : Unknown Copyleft
  Programming Lang: C
  Description :  produce 3D line drawings from scene description language

Sketch is a simple system for producing line drawings of
three-dimensional objects and scenes. Sketch is intended to produce finely
wrought, mathematically-based illustrations with no extraneous detail
and be able to easily overlay TeX math and text. The input language is
reminiscent of PSTricks, so will be easy to learn for current PSTricks
users.  It generates either PSTricks or TikZ/PGF code as output.

LICENSING NOTES:

On the website it states, 

   I've developed some tools while writing a textbook. They're good 
   enough to get real work done, so I'm offering them free under 
   Copyleft. 

But there seems to be no explicit licensing information in the source. 
Obviously I need to figure this out before the package can be considered 
for inclusion in Debian.

NAME NOTES:

There was another package named sketch; it seems to be gone now. If this 
is problematic, an alternative name could be sketch3d

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.22 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


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

Re: Fwd: Re: Why no Opera?

2007-09-05 Thread Edward Welbourne

Hi debian-devel,

 The web of trust gave me Mr Johan Herland as the only member of strong set 
 and I took the freedom to place him on the CC line.

Johan forwarded you to me.  For reference, dpkg -s, or the package's
control file, would have told you:

Maintainer: Opera Packaging Team [EMAIL PROTECTED]

 Opera could offer an apt repository for the .deb

We already do :-)
Here's the line from my /etc/apt/sources.list:

deb http://deb.opera.com/opera/ testing non-free

There are two packages available (for each of several configurations):
opera is the shared-linkage version, opera-static is the
statically-linked version.  The former comes in two flavours; .5 for
sarge and .6 for etch onwards.  Things older than sarge are the reason
for the static version.  With any luck, Claudio (one of the other
parties to [EMAIL PROTECTED]) can add more detail on what's behind
that ...

 On Tuesday 28 August 2007 06:46:47 Bruce Sass wrote:
 On Mon August 27 2007 05:33:05 pm Romain Beauxis wrote:
  Le Tuesday 28 August 2007 00:17:40 Bruce Sass, vous avez Ã©critÂ :
   On Mon August 27 2007 04:05:24 pm Pierre Habouzit wrote:
And it's no way we will accept the statically linked version
in Debian.

 Of course, obviously---for software where there is a choice, but for
 software which can not be built from source because it is closed or not
 redistributable once modified (which seems to be the case with Opera),
 putting a statically linked version into the archive sounds like the
 correct solution.

I'm confused.  Pierre appears to be saying static is bad, Bruce
closed must be static.  We have both static and shared packages, so
you can take your pick, but which is the one the official Debian
repository wants ?

I should also note that the existing Opera packages have not been very
lintian-compliant.  The new 9.50 release (we recently released an
alpha) shall deploy my re-write of the scripts that do packaging: this
fixes many of the deficiencies you'll find in packages up to 9.23, but
I'd greatly appreciate guidance on how to improve what 9.50 does !

Thanks for mirroring our package,

Eddy.


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

Re: virtualbox-ose: package hijack?

Joerg Jaspert wrote:
 NO. There is absolutely no reason to *knowingly* upload a non-free
 tarball, even named .dfsg.

For the records: I did *not* knowingly see that one.

 Yay, Upstream understands the problem, lets upload non-free crap to main 
 does
 not work.

My point is, that it is, of course, a serious error, but not a critical
one. It may have not been put well enough in words by me.

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


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

Re: virtualbox-ose: package hijack?

On Wed, Sep 05, 2007 at 11:39:42AM +0200, Daniel Baumann wrote:
 Upstream is generally cooperative and understands the problems, hence I
 see this a bit more relaxed (for the next few days only, until it's
 sorted out). However, if ftp-master do disagree, I'll can re-upload
 1.4.0, superseeding the 1.5.0 upload.

Are we talking about the same upstream here? The ones that knew the
package seemingly from the get go and then AFTER it made it into the archive 
threatened with a lawyer because the package was named virtualbox
instead of virtualbox-ose?

Michael
-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!


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

Re: virtualbox-ose: package hijack?

Michael Meskes wrote:
 Are we talking about the same upstream here?

i did answer to this question to michael in private (nda reasons).

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


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

Re: virtualbox-ose: package hijack?

2007-09-05 Thread Patrick Winnertz

Am Mittwoch, 5. September 2007 12:54:23 schrieb Daniel Baumann:
 tarballs can be produced with the invokation of 'debian/rules upstream'.

 it is debatable if the upstream tarball has to be inside the svn, rather
 than the alioth webspace (which I recommended you to do instead). other
 teams, such as the kernel-team, do it similar. I still do not understand
 why this is a problem for you, but that's not actually the point.

Mh... I would really prefer to do not post here private logs, but if you 
agree I can easily do:
But to summarize this issue: 
 I add it to the svn you removed it and when i ask you why you do it, you 
told me that the tarballs doesn't belong into svn. you never mention any 
other place where to put the tarball. 

The only thing you mentioned were debian/rules upstream to build it, so 
that everybody can build his own tarball to work on sorry but this 
won't work.
Furthermore your tone was not very friendly but very nerved and tersely. 

 Shall I cite the IRC log? I explained to you why I removed the tarball
 and how we should do it in a, imho, better way (means, not storing
 tarballs in svn, but on alioth webspace).

See above.

  See above. You showed me several times that you wasn't able to team -
  maintain this package. You doesn't listened to me if I try to speak
  with you about this issue in IRC.

 I fail to see where I did not listen to you.

As I mentioned above i would prefer not to post private logs here. But if 
you like I can easily do. 
You told me several times that you prepared a finished package but you 
simply forgot to commit your changes into the svn, and that you will 
upload it debian this night. When I remember correct you told me this 3 
times. 3 times nothing happens.


  We spoke yesterday (Sunday) about this issue in IRC and you ask me if
  you are allowed to reupload the 1.4.0 version with som minor fixes. I
  told you that I have against this strong objections.
 
  For people who can read german here a (small) part from the chat:
  
  09:12:56   panthera | wie ich sehe, hast du mich aus vbox
  entfernt. hast du was dagegen, wenn ich mich als uploader reinsetze
  und ein paar dinge poliere in 1.4.0svn4130-dfsg-2?
  09:52:34 winnie | ja..
  [ ... removed some stuff ... ]

 you do cut out the important stuff, where you did give no rational
 reason not upload it. instead, you refused to communicate.

As I mentioned above I would prefer not to post the full communication, 
since this is private. (And as you know there are some things within you 
won't want to see in public).
But to summarize:
I told you that I don't have to explain why you shouldn't in the group, but 
you have to explain why to be in it. 
Then you try to threaten me with do you really want a 
schlammschlacht?  (freely translated, sorry doesn't no a fitting 
english word).
As reason why I do not want you to be within the maintaining group I told 
you that I group maintain it with Michael and Marvin and this is more than 
enough people for this package. 

  Sorry... I didn't see you in the vbox-devel channel over a lng
  time period. At least: This issue is already fixed. I regulary speak
  with the upstream authors. But non the less this have to be fixed in
  debian too. I prepared an correct tarball which could be uploaded
  right after this one is removed.

 great, can you please upload it as 1.5.0-dfsg2-1 then?

No. This thing have to be removed from the archive fast... see mail from 
ganneff. I'll upload it as 1.5.0-dfsg-1. 

Furthermore upstream states several months ago that they doesn't like your 
packaging, and doesn't really want you as maintainer.. if you like I'll 
can also show some logs here, or you simply believe me. This discussion 
was made in #vbox-dev on freenode. (where you doesn't show up since 
several months.) So.. where is your active discussion with this license 
issues with upstream? There were really hugh problems concerning 
virtualbox which you simply do not see when uploading the package the 
first time (sponsored for Philipp Hug) at debconf.

I'll merge some of your changes you made in your fast and dirty made 
package and mention you in the changelog. Thats all. 



  In my eyes this is clearly a hijack of the package.

 It's not and I also ask you to not remove me from uploaders in a next
 upload.

Sorry?!? You'll never talked with me after the debconf upload (which was 
also a very fast and dirty hack). Everytime I started after this a 
communication with you I got as a answer: Sorry I have no time. Please do 
not distrurb (also freely translated). 


  We both had ITPs for
  this package and you doesn't act for a long time. If I haven't
  uploaded it last week, I'm sure that nothing would have happened.

 This is a wild assumption. I'm just back from some intensive work in
 real-life last four weeks...

s/four weeks/more than six months/ ...

It's okay to have a real-life.. I also have one. But if you have one and do 
not do anything

Re: virtualbox-ose: package hijack?

2007-09-05 Thread Julien BLACHE

Daniel Baumann [EMAIL PROTECTED] wrote:

 Are we talking about the same upstream here?

 i did answer to this question to michael in private (nda reasons).

Please post this explanation to -private.

JB.

-- 
 Julien BLACHE - Debian  GNU/Linux Developer - [EMAIL PROTECTED] 
 
 Public key available on http://www.jblache.org - KeyID: F5D6 5169 
 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 


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

Re: virtualbox-ose: package hijack?

2007-09-05 Thread Josselin Mouette

Le mercredi 05 septembre 2007 à 14:08 +0200, Daniel Baumann a écrit :
 Michael Meskes wrote:
  Are we talking about the same upstream here?
 
 i did answer to this question to michael in private (nda reasons).

If there are restrictions on the package name, this definitely looks
like something all Debian developers, especially FTP masters, should be
aware of.

-- 
 .''`.   Josselin Mouette/\./\
: :' :   [EMAIL PROTECTED]
`. `'[EMAIL PROTECTED]
  `-  Debian GNU/Linux -- The power of freedom


signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: virtualbox-ose: package hijack?

2007-09-05 Thread Patrick Winnertz

Am Mittwoch, 5. September 2007 14:01:39 schrieb Daniel Baumann:
 Joerg Jaspert wrote:
  NO. There is absolutely no reason to *knowingly* upload a non-free
  tarball, even named .dfsg.

 For the records: I did *not* knowingly see that one.

Yes. bt a simply find . -type f | sort  /tmp/new.txt in the Virtualbox 
1.5.0 source 
and a find . -type f | sort  /tmp/old.txt  in the virtualbox 
1.4.0svn4130 source
and then a 
diff -u /tmp/old.txt /tmp/new.txt would show you the new files... 

This was no good work which was quicked hacked together. 


  Yay, Upstream understands the problem, lets upload non-free crap to
  main does not work.

 My point is, that it is, of course, a serious error, but not a critical
 one. It may have not been put well enough in words by me.

That is in my critical. You upload things without checking them intensivly. 
I'm not yet a DD, but this 3 commands above costs me 2 minutes to check 
which files are new. 
The upload after the debconf shows me that you doesn't really check what 
you do there. 

Greetings
Patrick

-- 
 .''`.   Patrick Winnertz [EMAIL PROTECTED]
:  :' :  GNU/Linux Debian-Edu Developer
`. `'`   http://www.der-winnie.de http://d.skolelinux.org/~winnie
  `-  Debian - when you have better things to do than fixing systems


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

Re: virtualbox-ose: package hijack?

On Wed, Sep 05, 2007 at 02:08:47PM +0200, Daniel Baumann wrote:
 Michael Meskes wrote:
  Are we talking about the same upstream here?
 
 i did answer to this question to michael in private (nda reasons).

You're kidding right? This has to be a joke. Please tell me it is. Or is
there another email coming and I act on the wrong one?

I can summarize his email without having an nda problem at all as it was
essantially empty. His order to respect the privacy of this email is
about as long as the rest of the email, both are one liners. And no,
there is neither a real explanation nor anything worth being called nda
reasons. 

Still shaking my head in disbelief.

Michael
-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!


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

Re: virtualbox-ose: package hijack?

On Wed, Sep 05, 2007 at 02:01:39PM +0200, Daniel Baumann wrote:
 My point is, that it is, of course, a serious error, but not a critical
 one. It may have not been put well enough in words by me.

I cannot speak for our ftp admins here, but I definitely would call this
very critical if I was one of the guys responsible for the archive.

Michael
-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!


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

Re: virtualbox-ose: package hijack?

Patrick Winnertz wrote:
I add it to the svn you removed it and when i ask you why you do it, you
told me that the tarballs doesn't belong into svn. you never mention any
other place where to put the tarball.

The only thing you mentioned were debian/rules upstream to build it, so
that everybody can build his own tarball to work on sorry but this
won't work.
Furthermore your tone was not very friendly but very nerved and tersely.

Note: this was done when I had some spare internet acces while vacation
in Berlin. I explained that to you why I don't have time to explain it
in more detail.

You told me several times that you prepared a finished package but you
simply forgot to commit your changes into the svn, and that you will
upload it debian this night. When I remember correct you told me this 3
times. 3 times nothing happens.

Because new issues with it arrised. I though at that time to better not
upload the package with those issues. History says I should have
probably had.

As I mentioned above I would prefer not to post the full communication,
since this is private. (And as you know there are some things within you
won't want to see in public).

for others: the parenteses refere to nda related stuff.

I told you that I don't have to explain why you shouldn't in the group, but
you have to explain why to be in it.
Then you try to threaten me with do you really want a
schlammschlacht? (freely translated, sorry doesn't no a fitting
english word).

i still think there is no problem with me beeing in uploaders and you
beeing the maintainer. i still don't think we should 'discuss' the issue
as we do right now and why there cannot be a team with a mailinglist for
communication.

As reason why I do not want you to be within the maintaining group I told
you that I group maintain it with Michael and Marvin and this is more than
enough people for this package.

There were really hugh problems concerning
virtualbox which you simply do not see when uploading the package the
first time (sponsored for Philipp Hug) at debconf.

Phillip Hug is a DD. He can upload packages on his own. Hence he did
upload the package on his own, I did not see it before as I was busy
working together with Otavio at most parts of Debconf.

Sorry?!? You'll never talked with me after the debconf upload (which was
also a very fast and dirty hack). Everytime I started after this a
communication with you I got as a answer: Sorry I have no time. Please do
not distrurb (also freely translated).

Philip did the upload, not me. You did contact me one time after
Debconf, when I was, as announced, on vacation (with infrequent and
unstable internet access).

It's okay to have a real-life.. I also have one. But if you have one and do
not do anything the last 6 months you can state that and say: Sorry I have
atm no time for this.

from your mouth, it sounds like I was MIA the last several months :))

Please have a look on the bugs which are all assigned to you... and how
many are fixed there. You have much to many packages which you maintain
and many of them are more or less unmaintained and have several serious
bugs assigned to them.

umaintained? That's an unfair and untruth claim. There is one or two
packages which definitely deserved more love, both are beeing taken care
of (ipac-ng and thttpd that is).

I do understand that you don't have that time to
work on virtualbox, but then you should also accept that we do not want to
add you to the Uploader field only because you would like to be a
maintainer of it.

I don't want to be the maintainer of it, I want to be a, or one of
several, co-maintainers.

I've looked at the svn commits... for all who also want to have a look on
it please see here:

http://svn.debian.org/wsvn/pkg-virtualbox/dists/trunk/virtualbox/debian/?op=logrev=0sc=1isdir=1

All things you do was the initial commit loong ago and then twice you
changed only the changelog.
And then after I start working in it, you revert my complete changes.

That's wrong. The *only* thing I reverted is the layout change in the
svn (rational for it is given in the previous mail).

--
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: [EMAIL PROTECTED]
Internet: http://people.panthera-systems.net/~daniel-baumann/

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

Re: virtualbox-ose: package hijack?

Patrick Winnertz wrote:
 The upload after the debconf shows me that you doesn't really check what 
 you do there. 

This package was done and uploaded by Phillip, not me.

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


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

Re: virtualbox-ose: package hijack?

2007-09-05 Thread Raphael Hertzog

On Wed, 05 Sep 2007, Patrick Winnertz wrote:
 This was no good work which was quicked hacked together. 

I'm sorry, but when I upload a new upstream release of Django, I don't
check every new file.

It's all good that you do it, but it's not necessarily a requirement
and I find it hard to blame daniel for that. You can blame him for many
other things (too many packages, etc.) but this is overdone.

I'd really prefer that you stop attacking him for the sake of it and accept
his help and review his work exactly like he can review your work. For
this, using the public project on Alioth seems the right thing and as you
know Daniel is the admin of that project and you're part of it. You do
have everything you need to effectively collaborate.

Of course, each one has his personal preferences and everyone has to make
some compromises to be able to work together. I haven't seen you ready to
make any compromise up to now.

I know that Virtualbox is hype and it's good to have his name associated
to the official Debian package, but pretty please keep in mind the best
interest of the project...

 That is in my critical. You upload things without checking them intensivly. 
 I'm not yet a DD, but this 3 commands above costs me 2 minutes to check 
 which files are new. 

If you accepted collaborating, you'd have had the possibility to review
the work. Now you're forced to discuss the ownership of the package which
is just useless. :-(

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/


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

Re: Fwd: Re: Why no Opera?

2007-09-05 Thread Steffen Moeller

Dear Edward,

many thanks for joining in.

On Wednesday 05 September 2007 13:23:46 Edward Welbourne wrote:

  Opera could offer an apt repository for the .deb

 We already do :-)
 Here's the line from my /etc/apt/sources.list:

 deb http://deb.opera.com/opera/ testing non-free

I was pointed to it by others on the list and have indicated it on this wiki 
page http://wiki.debian.org/UnofficialRepositories

 There are two packages available (for each of several configurations):
 opera is the shared-linkage version, opera-static is the
 statically-linked version.  The former comes in two flavours; .5 for
 sarge and .6 for etch onwards.  Things older than sarge are the reason
 for the static version.  With any luck, Claudio (one of the other
 parties to [EMAIL PROTECTED]) can add more detail on what's behind
 that ...

this sounds all very reasonable to me.

  On Tuesday 28 August 2007 06:46:47 Bruce Sass wrote:
  On Mon August 27 2007 05:33:05 pm Romain Beauxis wrote:
   Le Tuesday 28 August 2007 00:17:40 Bruce Sass, vous avez Ã©critÂ :
On Mon August 27 2007 04:05:24 pm Pierre Habouzit wrote:
 And it's no way we will accept the statically linked version
 in Debian.
 
  Of course, obviously---for software where there is a choice, but for
  software which can not be built from source because it is closed or not
  redistributable once modified (which seems to be the case with Opera),
  putting a statically linked version into the archive sounds like the
  correct solution.

 I'm confused.  Pierre appears to be saying static is bad, Bruce
 closed must be static.  We have both static and shared packages, so
 you can take your pick, but which is the one the official Debian
 repository wants ?
There are multiple views on this. Everyone is confused, the minimal confusion 
is probably on your side since you can see the source. The 
Non-Opera-Debianers can only guess about it all  and remain confused. For 
efficiency we want it all dynamic, for safety it is probably static.

 I should also note that the existing Opera packages have not been very
 lintian-compliant.  The new 9.50 release (we recently released an
 alpha) shall deploy my re-write of the scripts that do packaging: this
 fixes many of the deficiencies you'll find in packages up to 9.23, but
 I'd greatly appreciate guidance on how to improve what 9.50 does !
The ultimate solution of course would be an Open Source release. Though you'd 
certainly do that if you wanted to and others on this list probably will 
remind you of this idea anyway. So I will be quiet about it :)

For a closed source release it would be lovely if you had a Debian developer 
amongst your Opera developers who can upload packages to the distribution. 
This way, he could make sure that all the LGPL libraries that you may be 
shipping as part of your binary distribution appear as Debian packages 
themselves. Together with the other DDs he would have ensure that those 
libraries that are already in the distribution are working with Opera. And 
finally, he could prepare binary uploads of your package for the non-free 
section.

So, the Debian community would have someone (and sadly only one) who can 
inspect your source and fix issues that arise. The benefit I see for Opera is 
a further decreased footprint.

For an involvement of the community in the packaging of your latest versions I 
do not see how this would be possible without any knowledge about how Opera 
is working internally and about what libraries it uses. But this list is 
certainly the right one for technical issues, be it for packages aiming at 
your separate repository or for Debian's main one.

Best regards

Steffen

[PROPOSAL] virtual package for Japanese font package name

2007-09-05 Thread Nobuhiro Iwamatsu

Hi all.

We, the Japanese font packages maintainers and their 
collaborators (Japanese Task Force: JTF), propose 
following action items to ease the task of the default
font selection for applications under the Debian system. 
 
 * The creation of new virtual package name: 
  - ttf-japanese-mincho 
  - ttf-japanese-gothic 
 * The creation of new alternative name: 
  - ttf-japanese-mincho.ttf 
  - ttf-japanese-gothic.ttf 
 * The adjustment of font packages which provide newly created virtual 
   package name. 
 * The adjustment of application packages which directly declare 
   dependency to the Japanese ttf font packages. 
 
[Packages which are affected]

 * Japanese font packages
 * Application packages which declare dependency to the Japanese ttf package
  - libpango1.0-common
  - xpdf-japanese
  - gs-cjk-resource
  - xdvik-ja
  - vflib2
  - mgp
  - libkiten1
  - kiten
  - kanjipad
  - kanatest
  - gjiten
  - advi-examples
  - advi

[Packages which are not affected]

 * The application packages which use defoma or fontconfig for their
   font configuration.

[Details of proposed action items]
 1. Each Japanese font packages provides one of the virtual package name in its 
Provides stanza based on the glyph style:
  - ttf-japanese-mincho (for Mincho-style. The glyph style corresponds to 
sans-serif.)
  - ttf-japanese-gothic (for Gothic-style. The glyph style corresponds to 
gothic.)

 2. Each Japanese font packages registers to the alternative system while making
link from ttf-japanese-mincho.ttf or ttf-japanese-gothic.ttf in
/usr/share/fonts/truetype/ directory.  The priority level of alternative is
specified as follows.

   above 100: Third party or user created fonts
   60:ttf-vlgothic
   50:ttf-sazanami-mincho, ttf-sazanami-gothic
   20:ttf-kochi-mincho, ttf-kochi-gothic
   below 20:  fonts which are deprecated for use in Japanese environment,
  (e.g..,  fonts which use Chinese style glyph for the unified
  region characters.)

 3. The application that specifies a specific Japanese font package dependency 
replaces its dependency to ttf-japanese-mincho | ttf-japanese-gothic (or
ttf-japanese-mincho, ttf-japanese-gothic) as needed.  Then, the path to the
specific font is replaced by the path to
/usr/share/fonts/truetype/ttf-japanese-mincho.ttf and
/usr/share/fonts/truetype/ttf-japanese-gothic.ttf.

[Time line]
N-x   The discussion period ends and the formal request to add virtual package 
names 
  is sent to debian-policy from the JTF.
N The proposed new virtual packages are approved.
  Uploading of the updated Japanese font packages is started by the JTF.
  The making and testing of the patch to the affected application packages 
  which depend on the Japanese ttf are started by the JTF.

N+3   Uploadings of all Japanese font packages are completed. (including NMUs)

N+13  The ttf-vlgothic and ttf-sazanami-mincho packages which are the core font 
  packages enters into testing (at least).
  The tested patches to the affected packages which depend on the Japanese
  ttf packages are sent out to the BTS by the JTF.

N+25  The JTF requests non-responsive maintainers for the permission to perform
  the NMUs of the affected packages.

N+30  The NMUs of updated packages are completed.

[Proposer]
Kenshi Muto (Debian developer)
Hideki Yamane (Debian contributor)
Junichi Uekawa (Debian developer)
Nobuhiro Iwamatsu (Debian contributor)

regards,
 Nobuhiro
-- 
Nobuhiro Iwamatsu
[EMAIL PROTECTED]
[EMAIL PROTECTED]

GPG ID : 3170EBE9


pgpFrX1PkRng8.pgp
Description: PGP signature

Bug#440923: ITP: tatan -- pointing STG shooter game

Package: wnpp
Severity: wishlist
Owner: Debian Games Team [EMAIL PROTECTED]


* Package name: tatan
  Version : 1.0
  Upstream Author : HIZ [EMAIL PROTECTED]
* URL : http://hizuoka.web.fc2.com/game/tatan/index_en.html
* License : http://www5.atwiki.jp/yaruhara/pages/56.html
  Programming Lang: D
  Description : pointing STG shooter game

 Tatan is a shooter game with simplified controls: use the mouse to aim
 and shoot, and the space bar to toggle your position. You have to collect
 the yellow stars (or shoot the white ones circumscribed in spheres) for
 power-ups.

 The game is played in some sort of quantum universe, and you are
 either positioned on the left or the right.

 The license more or less says you can do whatever you want with it, as
 long as you keep the author's name there.


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

Re: [PROPOSAL] virtual package for Japanese font package name

2007-09-05 Thread Josselin Mouette

Le mercredi 05 septembre 2007 à 22:15 +0900, Nobuhiro Iwamatsu a écrit :
  * The creation of new alternative name: 
   - ttf-japanese-mincho.ttf 
   - ttf-japanese-gothic.ttf 

  3. The application that specifies a specific Japanese font package 
 dependency 
 replaces its dependency to ttf-japanese-mincho | ttf-japanese-gothic (or
 ttf-japanese-mincho, ttf-japanese-gothic) as needed.  Then, the path to 
 the
 specific font is replaced by the path to
 /usr/share/fonts/truetype/ttf-japanese-mincho.ttf and
 /usr/share/fonts/truetype/ttf-japanese-gothic.ttf.

I'd rather see this new alternative outside the path used by fontconfig.
This will avoid reading the font file twice.

Cheers,
-- 
 .''`.   Josselin Mouette/\./\
: :' :   [EMAIL PROTECTED]
`. `'[EMAIL PROTECTED]
  `-  Debian GNU/Linux -- The power of freedom


signature.asc
Description: Ceci est une partie de message	numériquement signée

Bug#440924: ITP: projectl -- sword action shooting

Package: wnpp
Severity: wishlist
Owner: Debian Games Team [EMAIL PROTECTED]


* Package name: projectl
  Version : 1.001
  Upstream Author : HIZ [EMAIL PROTECTED]
* URL : http://hizuoka.web.fc2.com/game/projectL/index_en.html
* License : (GPL, LGPL, BSD, MIT/X, etc.)
  Programming Lang: D
  Description : sword action shooting

 The sword mechanic is everything in this game. Your sword rotates away
 from the direction your ship moves, and in doing so slices through the
 various enemies.

 The license more or less says you can do whatever you want with it, as
 long as you keep the author's name there.


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

Re: Fwd: Re: Why no Opera?

2007-09-05 Thread Roberto C . Sánchez

On Wed, Sep 05, 2007 at 03:16:07PM +0200, Steffen Moeller wrote:
 
 On Wednesday 05 September 2007 13:23:46 Edward Welbourne wrote:
 
  I'm confused.  Pierre appears to be saying static is bad, Bruce
  closed must be static.  We have both static and shared packages, so
  you can take your pick, but which is the one the official Debian
  repository wants ?
 There are multiple views on this. Everyone is confused, the minimal confusion 
 is probably on your side since you can see the source. The 
 Non-Opera-Debianers can only guess about it all  and remain confused. For 
 efficiency we want it all dynamic, for safety it is probably static.
 
The problem runs a little deeper than that.

Static linking is considered bad because it is a security nightmare.
You now have extra copies of library code floating around.  The security
team is not particularly happy about this sort of thing.  Especially in
something non-free to which they do not have source-level access.

Additionally, static linking destroys any memory utilization benefit of
library code.  That is, if I have an app that dynamically links to
libfoo and another app also uses the same library, but is static linked,
then the second app will cause a copy of the code to be loaded.  On low
resource machines (which is one of Opera's targets), I would consider
that bad.

Of course, the advantage is that the release engineers would be assured
of the versions of the libraries used from the point of release.

Dynamic linking is what the security team likes since it means that you
only update the code once for the whole system.  However, in the event
that there is an update which makes the library non-binary compatible,
then there is another problem.  That is, apps linking against it must be
recompiled.  With a non-free product like opera, there would be ability
for some well-meaning Debian Developer to NMU the package (since there
is no source) or for a binNMU to take place if that could fix the
problem.

One possible solution would be for Opera to produce a source package
of unlinked binary object files.  This would allow relinking against new
versions of the libraries (at least in most cases) without the need for
access to the source.

However, I tend to be in agreement with others on this list that the
best solution would be a Free software release of Opera.

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Bug#440925: ITP: es-shooter -- shooter game

Package: wnpp
Severity: wishlist
Owner: Debian Games Team [EMAIL PROTECTED]


* Package name: es-shooter
  Version : 1.0a
  Upstream Author : HIZ [EMAIL PROTECTED]
* URL : http://hizuoka.web.fc2.com/game/ES/ES_d.zip
* License : http://www5.atwiki.jp/yaruhara/pages/56.html
  Programming Lang: D
  Description : shooter game

Your ship is surrounded by two circles. You shoot in the direction of
your mouse points, and you move if the mouse pointer is outside the
inner circle.

The license more or less says you can do whatever you want with it, as
long as you keep the author's name there.


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

Re: Fwd: Re: Why no Opera?

2007-09-05 Thread Bernd Zeimetz

Hi,
 So, the Debian community would have someone (and sadly only one) who can 
 inspect your source and fix issues that arise. The benefit I see for Opera is 
 a further decreased footprint.

   

if opera would be come open-source, I'd be willing to co-maintain and
check packages - it would be worth the work. But I'm not willing to
spend my free time on closed source if there's no really good reason to
do so.

Cheers,

Bernd

-- 
Bernd Zeimetz
[EMAIL PROTECTED] http://bzed.de/


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

Re: virtualbox-ose: package hijack?

2007-09-05 Thread Anthony Towns

On Wed, Sep 05, 2007 at 11:39:42AM +0200, Daniel Baumann wrote:
 Michael Meskes wrote:
  I have no idea what Daniel really did on the package.
 I did about 90% of the inital packaging.

Which just left the last 90% of the packaging, I guess.

 Patrick uploaded removed me from changelog in the two last uploads
 (virtualbox 1.4.0svn4130-dfsg-1 and virtualbox-ose 1.4.0svn4130-dfsg-1
 that is) without notifying me. In all previous uploads to NEW, I was in
 the co-maintainer.

FWIW, the uploads of virtualbox to NEW were:

|virtualbox_1.4.0-1_amd64.changes:
20070618213209|process-unchecked|Moving to new
20070709174342|process-new|rejected
|virtualbox_1.4.0svn3946-dfsg-1_i386.changes
20070801121715|process-unchecked|Moving to new
20070801222037|process-new|rejected
|virtualbox_1.4.0svn3946-dfsg-2_i386.changes
20070801143204|process-unchecked|Moving to new
20070801222028|process-new|rejected
|virtualbox_1.4.0svn3946-dfsg-1_i386.changes
20070802113206|process-unchecked|Moving to new
20070812215652|process-new|rejected
|virtualbox_1.4.0svn4130-dfsg-1_amd64.changes
20070824113207|process-unchecked|Moving to new
20070827060822|process-new|rejected

The .dsc from the first 3946-dfsg-1 above (1st August) listed:
  Maintainer: Patrick Winnertz [EMAIL PROTECTED]
  Uploaders: Philipp Hug [EMAIL PROTECTED], Marvin Stark [EMAIL PROTECTED]

If you weren't involved in the uploads to NEW over the past month to
notice, it seems reasonably fair to say you weren't co-maintaining the
package. If that's something that was just a one month thing, fine;
but it's not the end of the world either way.

|virtualbox_1.4.0svn4130-dfsg-1_amd64.changes
20070830124706|process-unchecked|Moving to new
20070901080307|process-new|Accepting changes
|virtualbox_1.4.0svn4130-dfsg-1_i386.changes
20070901194714|process-unchecked|Accepting changes

|virtualbox-ose_1.4.0svn4130-dfsg-1_amd64.changes
20070903134705|process-unchecked|Moving to new
20070903173435|process-new|Accepting changes
|virtualbox-ose_1.4.0svn4130-dfsg-1_i386.changes
20070904094702|process-unchecked|Accepting changes

|virtualbox-ose_1.5.0-dfsg-1_i386.changes
20070905054704|process-unchecked|Accepting changes
|virtualbox-ose_1.5.0-dfsg-1_amd64.changes
20070905070206|process-unchecked|Accepting changes

Then doing an upload that goes to a new upstream revision, adds code
which doesn't have a license at all, let alone a DFSG-free one, without
consulting the people you're claiming to be co-maintaining the package
with doesn't sound very impressive either.

 Upstream is generally cooperative and understands the problems, hence I
 see this a bit more relaxed (for the next few days only, until it's
 sorted out). However, if ftp-master do disagree, I'll can re-upload
 1.4.0, superseeding the 1.5.0 upload.

Personally, I don't think you should be even considering uploading
anything right now -- the above seems to me to have been some pretty bad
judgement calls, and the contents of an Uploaders: field or the lack of
a proper license for something upstream intends to be free software can
all wait for a day or two.

For a package that's been in unstable for under a week to require a
renaming due to trademarks, have a hijack war and thread on -devel,
and start getting new upstream versions with non-DFSG code strikes me
as pretty unimpressive all round, really...

Cheers,
aj


signature.asc
Description: Digital signature

Re: virtualbox-ose: package hijack?

2007-09-05 Thread Anthony Towns

On Wed, Sep 05, 2007 at 02:49:25PM +0200, Raphael Hertzog wrote:
 On Wed, 05 Sep 2007, Patrick Winnertz wrote:
  This was no good work which was quicked hacked together. 
 I'm sorry, but when I upload a new upstream release of Django, I don't
 check every new file.
 It's all good that you do it, but it's not necessarily a requirement
 and I find it hard to blame daniel for that. 

Uh, Daniel included a file that doesn't have a DFSG license in an upload
to main. That's not good enough. Reviewing diffs of upstream changes is
one way to avoid it; it's not the only way, but if you're not going to do
it, you still need to accept the blame for the mistakes you let through.

Patrick's packages got a pretty thorough grilling for copyright issues
by Joerg in the rejections from NEW over the past month, that Daniel's
upload wrecked that work is something to be really quite embarassed about,
not to excuse because it'd take a lot of effort to avoid.

Cheers,
aj



signature.asc
Description: Digital signature

Re: Fwd: Re: Why no Opera?

2007-09-05 Thread Hendrik Sattler


Zitat von Roberto C. Sánchez [EMAIL PROTECTED]:

Dynamic linking is what the security team likes since it means that you
only update the code once for the whole system.  However, in the event
that there is an update which makes the library non-binary compatible,
then there is another problem.  That is, apps linking against it must be
recompiled.


That's what ABIs are for. If a new version of a library breaks an  
application that uses the not-changed API as intended, it is the  
library that needs to use a new soname.
The package dependencies will indicate the needed libraries. Library  
packages in Debian should reflect the soname, thus the package name  
changes when the soname changes. No problem, then.


HS

Re: Fwd: Re: Why no Opera?

2007-09-05 Thread Edward Welbourne

Steffen:
 So, the Debian community would have someone (and sadly only one) who can 
 inspect your source and fix issues that arise. The benefit I see for Opera 
 is 
 a further decreased footprint.
Bernd:
 if opera would be come open-source, I'd be willing to co-maintain and
 check packages - it would be worth the work. But I'm not willing to
 spend my free time on closed source if there's no really good reason to
 do so.

I'm afraid this humble coder isn't about to sway that argument; for
the present, Opera remains closed, all I can do is make life easier
for users.  I entirely appreciate that I can't expect help improving
our closed packages, but any help that *is* volunteered would make one
more package be a bit closer to conforming to Debian's standards.
We've had some very welcome help from the Ubuntu folks, who are
largely responsible for the improvements between 9.23 and 9.50, and
I'll be reviewing the remaining issues (two of my nine outstanding
packaging bugs are Debian-specific) when I have time.

Steffen:
 For a closed source release it would be lovely if you had a Debian  
 developer amongst your Opera developers who can upload packages to  
 the distribution.

That's one of the (too many) things I've got on my todo list - get
myself trained as a proper Debian developer.  For the moment, I just
have some scripts (mostly inherited, I've only had time to clean them
up so far) that do the packaging mostly right; the scripts know more
about Debian packaging than I do, though.  Tollef Fog Heen directed me
to http://www.debian.org/doc/manuals/maint-guide/ when he was my
Ubuntu contact, so I guess I should familiarize myself with that
before asking for a sponsor !

Eddy.


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

Re: Fwd: Re: Why no Opera?

2007-09-05 Thread Roberto C . Sánchez

On Wed, Sep 05, 2007 at 04:43:09PM +0200, Hendrik Sattler wrote:
 Zitat von Roberto C. Sánchez [EMAIL PROTECTED]:
 Dynamic linking is what the security team likes since it means that you
 only update the code once for the whole system.  However, in the event
 that there is an update which makes the library non-binary compatible,
 then there is another problem.  That is, apps linking against it must be
 recompiled.
 
 That's what ABIs are for. If a new version of a library breaks an  
 application that uses the not-changed API as intended, it is the  
 library that needs to use a new soname.
 The package dependencies will indicate the needed libraries. Library  
 packages in Debian should reflect the soname, thus the package name  
 changes when the soname changes. No problem, then.
 
I understand that.  The point I was trying to get at is that in such
cases Debian tries to minimize the proliferation of many versions of
libraries in the archive.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

sshd defaults (Re: RFC: changes to default password strength checks in pam_unix)

2007-09-05 Thread Oleg Verych (Gmane)

05-09-2007, Gabor Gombas:
 On Tue, Sep 04, 2007 at 08:26:41PM +, Oleg Verych: gmane reading wrote:

 I.e *i don't care* about entering passwords on middle ground, without
 knowing, WTF this installer may do with them, not having comfortable
 environment for that _important_ action.
 
 Thus i have silly, empty passwords after installation. Then, i get my
 imagination and compose really super-druper passwords for root and users
 (that i create myself by script with, IDs i want/have on filesystems, not
 by installation process).

 Well, if you give public network access to any machine before the
 initial configuration is complete, that's _your_ problem. The UNIX way
 was always if the admin wants to shot himself in the foot, let him.

Oh, sure! I did network friendly install by downloading only vmlinuz
and netinstall initramfs, and i've shot myself in the foot, nice!

Give me more of that prehistoric crap, please!

Or maybe i just want to test Sid like that. Again i need running OS after
reboot, but nothing else, like password management. Test means creating
rootfs and all other things, so don't propose me useing some ready fs.

I didn't traced issue, but Sid have problem with filesystems, like XFS,
which support sparse files. I've gigs of /var/log/lastlog and faillog
in every Sid install tests!!!



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

Agreement between parties achieved on IRC (Re: virtualbox-ose: package hijack?)

2007-09-05 Thread Adeodato Simó

Just a quick note to say that after some discussion in #debian-devel
involving Daniel, Patrick, and Michael, and fostered by various DDs
(azeem, buxy, Ganneff, myself), a solution to resolve this situation was
achieved.

In particular, development will return to the pkg-virtualbox Alioth
project (Patrick had been preparing his packages in an external
repository), Michael Meskes will be the new admin of this project
(instead of Daniel), the maintainer will be set to a mailing list
(instead of Patrick), and Daniel will return to the Uploaders field of
the package, with the promise that for any non-trivial commits he will
mail the mailing list first.

Hopefully that sums up what was agreed on on IRC, and everybody will
uphold their part of the deal.

Cheers,

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
   Listening to: Nacho Vegas - Las manos dentro del agua


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

Bug#440938: ITP: xulrunner-l10n -- language packages for xulrunner

2007-09-05 Thread arno renevier

Package: wnpp
Severity: wishlist
Owner: arno renevier [EMAIL PROTECTED]


* Package name: xulrunner-l10n
  Version : 1.8.1-1
  Upstream Author : Mozilla Project and Mozilla Localization Projects
* URL : http://www.mozilla.org/projects/l10n/
* License : GPL, LGPL, and MPL
  Description : language packages for xulrunner

 XULRunner is a single gecko runtime that can be used to bootstrap
 multiple XUL + XPCOM applications that are as rich as Firefox and
 Thunderbird.
 .
 This package provides localizations for xulrunner


Additional informations:
xulrunner-l10n will have similarity with iceweasel-l10n; some part of
xulrunner-l10n source will come from iceweasel-l10n source package, other part
will come from mozilla cvs.

source package will provide 43 localization packages + one meta package
xulrunner-l10n-all which depends on all localization packages.

Unlike iceweasel-l10n, localization packages will not be installed as
extensions, but directly in /usr/share/xulrunner/chrome because current version
of xulrunner does not allow global extensions for all applications. Hopefully,
that will change in the future, and localization packages could be real mozilla
extensions.

arno.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-486
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


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

Re: Bug#440938: ITP: xulrunner-l10n -- language packages for xulrunner

2007-09-05 Thread Mike Hommey

On Wed, Sep 05, 2007 at 05:11:51PM +0200, arno renevier [EMAIL PROTECTED] 
wrote:
 Package: wnpp
 Severity: wishlist
 Owner: arno renevier [EMAIL PROTECTED]
 
 
 * Package name: xulrunner-l10n
   Version : 1.8.1-1
   Upstream Author : Mozilla Project and Mozilla Localization Projects
 * URL : http://www.mozilla.org/projects/l10n/
 * License : GPL, LGPL, and MPL
   Description : language packages for xulrunner
 
  XULRunner is a single gecko runtime that can be used to bootstrap
  multiple XUL + XPCOM applications that are as rich as Firefox and
  Thunderbird.
  .
  This package provides localizations for xulrunner
 
 
 Additional informations:
 xulrunner-l10n will have similarity with iceweasel-l10n; some part of
 xulrunner-l10n source will come from iceweasel-l10n source package, other part
 will come from mozilla cvs.
 
 source package will provide 43 localization packages + one meta package
 xulrunner-l10n-all which depends on all localization packages.
 
 Unlike iceweasel-l10n, localization packages will not be installed as
 extensions, but directly in /usr/share/xulrunner/chrome because current 
 version
 of xulrunner does not allow global extensions for all applications. Hopefully,
 that will change in the future, and localization packages could be real 
 mozilla
 extensions.

Actually, it *does* allow global extensions, but applications embedding 
libxul or using xulrunner have to initialize the extensions manager by
themselves in order to get these extensions enabled. This is something that
is, unfortunately, not very likely to change.

Note having added stuff in the chrome without extensions recently, I can't
tell you if it will be necessary to go through a registration phase, but
I think putting a chrome.manifest file alongside should be enough.

If it is not, please bug me so that we find something (which might be in 
the form of a script provided by the libxul package)

Cheers,

Mike


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

Re: Fwd: Re: Why no Opera?

2007-09-05 Thread Bernd Zeimetz

Hi,
 That's one of the (too many) things I've got on my todo list - get
 myself trained as a proper Debian developer.  For the moment, I just
 have some scripts (mostly inherited, I've only had time to clean them
 up so far) that do the packaging mostly right; the scripts know more
 about Debian packaging than I do, though.  Tollef Fog Heen directed me
 to http://www.debian.org/doc/manuals/maint-guide/ when he was my
 Ubuntu contact, so I guess I should familiarize myself with that
 before asking for a sponsor !
   

you can at least use linda and lintian (-iI) to check your packages,
that should help a lot.

Cheers,

Bernd

-- 
Bernd Zeimetz
[EMAIL PROTECTED] http://bzed.de/


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

Re: Bug#440938: ITP: xulrunner-l10n -- language packages for xulrunner

2007-09-05 Thread arno

Le mercredi 05 septembre 2007, à 17:50:35 +0200, Mike a écrit : 
 
 Actually, it *does* allow global extensions, but applications embedding 
 libxul or using xulrunner have to initialize the extensions manager by
 themselves in order to get these extensions enabled. This is something that
 is, unfortunately, not very likely to change.

What I meant here is you can use global extension for some applications, but 
not 
for xulrunner globally. ie: an extension has to provide an install.rdf 
referencing all xulrunner application it works with.

So if you have a xulrunner extension, and you create a new application, you 
must:
- enable extension manager (easy: can be done in the application itself)
- change something in extension install.rdf (difficult: you must modify another 
debian package). That's what I want to avoid here.

I think it will be easier to avoid that in xulrunner 1.9 (I'm not totally sure, 
but that's what I understand from mozilla bug 299716)

 Note having added stuff in the chrome without extensions recently, I can't
 tell you if it will be necessary to go through a registration phase, but
 I think putting a chrome.manifest file alongside should be enough.

adding a .jar and a manifest in /usr/share/xulrunner/chrome/ seems to work 
fine. 
That's the way we do things in my paid job. But if you want to provide 
a components/ directory, you have to provide a real extension - otherwise, the 
component(s) may not be reregistered after modifications.

Regards
arno


signature.asc
Description: Digital signature

Re: Bug#440938: ITP: xulrunner-l10n -- language packages for xulrunner

2007-09-05 Thread Mike Hommey

On Wed, Sep 05, 2007 at 06:45:18PM +0200, arno [EMAIL PROTECTED] wrote:
 Le mercredi 05 septembre 2007, à 17:50:35 +0200, Mike a écrit : 
  
  Actually, it *does* allow global extensions, but applications embedding 
  libxul or using xulrunner have to initialize the extensions manager by
  themselves in order to get these extensions enabled. This is something that
  is, unfortunately, not very likely to change.
 
 What I meant here is you can use global extension for some applications, but 
 not 
 for xulrunner globally. ie: an extension has to provide an install.rdf 
 referencing all xulrunner application it works with.
 
 So if you have a xulrunner extension, and you create a new application, you 
 must:
 - enable extension manager (easy: can be done in the application itself)
 - change something in extension install.rdf (difficult: you must modify 
 another 
 debian package). That's what I want to avoid here.
 
 I think it will be easier to avoid that in xulrunner 1.9 (I'm not totally 
 sure, 
 but that's what I understand from mozilla bug 299716)

Yes, in this case, the changes scheduled for xulrunner 1.9 might be
helpful.

  Note having added stuff in the chrome without extensions recently, I can't
  tell you if it will be necessary to go through a registration phase, but
  I think putting a chrome.manifest file alongside should be enough.
 
 adding a .jar and a manifest in /usr/share/xulrunner/chrome/ seems to work 
 fine. 
 That's the way we do things in my paid job. But if you want to provide 
 a components/ directory, you have to provide a real extension - otherwise, 
 the 
 component(s) may not be reregistered after modifications.

You can add the component(s) in /usr/lib/xulrunner/components and
touch the /usr/lib/xulrunner/.autoreg file. The new component(s) will be
autoregistered at application startup. (Works the same with removed
components). See the xulrunner-gnome-support package.

Mike


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

debian/rules and environment variables

2007-09-05 Thread Peter Eisentraut

It has been suggested in bug #411520 that cdbs should be set up so that 
it preserves CFLAGS set in the environment.  But I haven't found any 
clear specification about how debian/rules, being a makefile, should 
deal with environment variables.

The best I could find is Policy 10.1 which states that the following 
compilation parameters should be used:

CC = gcc
CFLAGS = -O2 -g -Wall

(It doesn't say, these variables should be set this way.)  It appears, 
however, that hardly any package (containing C language code) 
explicitly sets CC, and I think it is certainly useful to be able to 
set a different CC in the environment.  Yet at the same time most 
packages set CFLAGS explicitly, overriding anything that's there 
before.  The language in the policy and various rules templates appear 
to encourage that.  But as the submitter of #411520 stated, it could 
also be useful to be able to build a package with different compiler 
flags.

What this might come down to is that most variable assignments in rules 
files should be changed from = to ?=.

Since debuild and pbuilder and other tools exist that give pretty good 
control over the environment for final package builds, I don't think 
there is much of a risk in allowing that, but I think some consistent 
approach ought to be worked out.

Comments?

-- 
please CC me


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

Re: debian/rules and environment variables

2007-09-05 Thread Neil Williams

On Wed, 5 Sep 2007 19:31:48 +0200
Peter Eisentraut [EMAIL PROTECTED] wrote:

 It has been suggested in bug #411520 that cdbs should be set up so that 
 it preserves CFLAGS set in the environment.  But I haven't found any 
 clear specification about how debian/rules, being a makefile, should 
 deal with environment variables.

http://lists.debian.org/debian-embedded/2007/08/msg00033.html

Where MAKEFLAGS are concerned, packages and build tools should not be
overriding environment variables and there is an issue in CDBS
regarding this which I need to get around to filing.

 CDBS is a culprit but also very easy to fix:
 DEB_CONFIGURE_SCRIPT_ENV=
 
 The reason is that CDBS presets 
 DEB_CONFIGURE_SCRIPT_ENV = CC=$(CC) CXX=$(CXX) CFLAGS=$(CFLAGS) 
 CXXFLAGS=$(CXXFLAGS) CPPFLAGS=$(CPPFLAGS) LDFLAGS=$(LDFLAGS)
 
 but passes those values TO ./configure instead of reading them
 AFTER ./configure has had a chance to process --build= and --host=.

This used to work because dpkg-cross explicitly overrode MAKEFLAGS but
this caused build failures with packages that need to compile tools
during the build - wrong architecture when executing. (#425445)

Now the CDBS behaviour actually re-implements the broken dpkg-cross
behaviour that is being fixed during the rewrite for #439979 so that
although the dpkg-cross changes fix builds like libx11-6 (which
compiles and then runs a tool {see #425445}, grep now fails to
cross-build without the above patch to debian/rules because
the ./configure setting (safely managed via dpkg-architecture) is
thrown out.

I would like to see that debian/rules and any other build tool NEVER
changes MAKEFLAGS or any related environment variable to make
cross-building easier.

 The best I could find is Policy 10.1 which states that the following 
 compilation parameters should be used:
 
 CC = gcc
 CFLAGS = -O2 -g -Wall
 
 (It doesn't say, these variables should be set this way.)  It appears, 
 however, that hardly any package (containing C language code) 
 explicitly sets CC, and I think it is certainly useful to be able to 
 set a different CC in the environment. 

Only with care. Just changing $CC is insufficient because you also need
to change the include path for libraries and the LD_LIBRARY path,
otherwise you'll end up compiling with arm-linux-gnu-gcc but linking
against libraries from /usr/lib instead of /usr/arm-linux-gnu/lib.

This is currently handled by remapping the paths for each command
during the build using symlinks and a perl parser script in dpkg-cross.
Guillem is working on a replacement dpkg method for ensuring that the
cross-compiler finds the correct libraries.

http://lists.debian.org/debian-devel/2007/08/msg01152.html

 Yet at the same time most 
 packages set CFLAGS explicitly, overriding anything that's there 
 before. 

CFLAGS is less of a problem for cross-building (so far) - it is CC that
has been the most problematic.

 The language in the policy and various rules templates appear 
 to encourage that.  But as the submitter of #411520 stated, it could 
 also be useful to be able to build a package with different compiler 
 flags.

Not just the flags.

On a related note, I'm thinking that *all* packages using ./configure
should be using:
DEB_HOST_GNU_TYPE := $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
DEB_BUILD_GNU_TYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
...
./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
 ...

This then allows cross-builders to simply call dpkg-architecture to set
the correct environment and ./configure will do the right thing.

Once the dpkg-cross rewrite makes it into unstable (hopefully in the
next dpkg upload after the one today - i.e. in dpkg 1.14.7) I'll go for
a rebuild of the Emdebian packages and start filing bugs against those
packages that don't bother with these simple checks, tagged with the
usertag 'cross-build'.

-- 


Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/



pgpCVgjXcTYdM.pgp
Description: PGP signature

Re: Agreement between parties achieved on IRC (Re: virtualbox-ose: package hijack?)

2007-09-05 Thread Andrew M.A. Cater

On Wed, Sep 05, 2007 at 05:33:40PM +0200, Adeodato Simó wrote:
 Just a quick note to say that after some discussion in #debian-devel
 involving Daniel, Patrick, and Michael, and fostered by various DDs
 (azeem, buxy, Ganneff, myself), a solution to resolve this situation was
 achieved.
 

Can I just say a heartfelt thank you to all concerned. This is a
useful precedent where problems have been sorted out relatively
amicably despite initial disagreements to the benefit and credit 
of all involved in a short space of time.

Everybody wins from this sort of cooperation and consensus-building

Andy

Bug#440968: ITP: qmailadmin -- web interface for managing a qmail system with virtual domains

2007-09-05 Thread Giuseppe Iuculano

Package: wnpp
Severity: wishlist
Owner: Giuseppe Iuculano [EMAIL PROTECTED]

* Package name: qmailadmin
  Version : 1.2.11
  Upstream Author : Ken Jones [EMAIL PROTECTED]
* URL : http://sourceforge.net/projects/qmailadmin/
* License : GPL
  Programming Lang: C
  Description : free software package that provides a web interface for 
managing a qmail system with virtual domains

QmailAdmin is a web interface for managing email addresses in virtual
domains created by Vpopmail.

It provides admin for adding/deleting users, Aliases, Forwards, Mailing
lists and Autoresponders.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'proposed-updates'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.22.5-iuculano
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)


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

Re: [EMAIL PROTECTED]: Delivery Status Notification]

2007-09-05 Thread Max Vozeler

On Sat, Sep 01, 2007 at 11:34:05AM +0100, Colin Watson wrote:
 The manpages-es maintainer's e-mail bounces. Does anyone know how to
 contact Rubén Porras Campo?

I spoke with Rubén and told him about the mail troubles. I think
he can be reached at [EMAIL PROTECTED] for now. He said he'll be
making uploads shortly to fix the broken maintainer address.

Max


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

Re: debian/rules and environment variables

2007-09-05 Thread Bernd Zeimetz

Hi,

 On a related note, I'm thinking that *all* packages using ./configure
 should be using:
 DEB_HOST_GNU_TYPE := $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 DEB_BUILD_GNU_TYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 ...
 ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
  ...
 
 This then allows cross-builders to simply call dpkg-architecture to set
 the correct environment and ./configure will do the right thing.

What about packages which do not use configure?
Are there any rules to follow, especially if you need to pass CC and
other options to upstream's build system, which is just a bunch of
Makefiles in this case. Although I doubt that anybody would
cross-compile this package, I'd appreciate some general hints.


Thanks,

Bernd

-- 
Bernd Zeimetz
[EMAIL PROTECTED] http://bzed.de/


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

Bug#440975: ITP: libhx -- a C library providing queues, trees, I/O and utility functions

2007-09-05 Thread Bastian Kleineidam

Package: wnpp
Severity: wishlist
Owner: Bastian Kleineidam [EMAIL PROTECTED]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

* Package name: libhx
  Version : 1.10.0
  Upstream Author : Jan Engelhardt jengelh [at] gmx de
* URL : http://freshmeat.net/projects/libhx/
* License : GPL2, GPL3, LGPL2, LGPL3
  Programming Lang: C
  Description : a C library providing queues, trees, I/O and utility 
functions

A C library for:
 - A+R/B trees to use for lists or maps (associative arrays)
 - Deques (double-ended queues) (Stacks (LIFO) / Queues (FIFOs))
 - platform independent opendir-style directory access
 - platform independent dlopen-style shared library access
 - auto-storage strings with direct access
 - command line option (argv) parser
 - shell-style config file parser
 - platform independent random number generator with transparent
   /dev/urandom support
 - various string, memory and zvec ops


I intend to package this library since newer versions of
libpam-mount (= 0.19) depend on libhx.


- -- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-ck1treasure3 (PREEMPT)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

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

iD8DBQFG3xLAeBwlBDLsbz4RApsHAJ0V8rSQWE0cAm2dF8qWEnynEyhYuwCgj/KB
HGh3dsO7ALMwkDOTnaoq3zQ=
=WFt3
-END PGP SIGNATURE-


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

Re: debian/rules and environment variables

2007-09-05 Thread Neil Williams

On Wed, 05 Sep 2007 22:51:30 +0200
Bernd Zeimetz [EMAIL PROTECTED] wrote:

 Hi,
 
  On a related note, I'm thinking that *all* packages using ./configure
  should be using:
  DEB_HOST_GNU_TYPE := $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
  DEB_BUILD_GNU_TYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
  ...
  ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
   ...
  
  This then allows cross-builders to simply call dpkg-architecture to set
  the correct environment and ./configure will do the right thing.
 
 What about packages which do not use configure?

Then it is up to the cross-building scripts to set the correct
environment and up to the package NOT to override those environment
settings. Right now, the way to do this is being rewritten and previous
behaviour is known to be causing build failures so just try to leave
the environment variables alone.

If you need to change the upstream behaviour, use a patch. Get your
package to build cleanly on a native system (i.e. without overwriting
environment variables) and it should cross-build cleanly.

 Are there any rules to follow, especially if you need to pass CC and
 other options to upstream's build system, 

Don't do that. There should be no reason to change CC. If you want
optimisations, that's CFLAGS or CPPFLAGS.

 which is just a bunch of
 Makefiles in this case. Although I doubt that anybody would
 cross-compile this package, I'd appreciate some general hints.

Every package is likely to need to be cross-compiled by someone at some
point - except Architecture: all. That's why I was working on a patch
for gcc during Debconf - to cross-build gcc using a gcc cross-compiler
to package libraries built from the gcc source on amd64 (or powerpc) to
link against packages cross built for arm.

-- 


Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/



pgpOHeZBJXD6X.pgp
Description: PGP signature

US mirror troubles

2007-09-05 Thread John Goerzen

Hi,

35.9.37.225, in http.us.debian.org, and ftp.us.debian.org, has been 
unreachable on port 80 from all the networks I have access to for days.

This is ftp.egr.msu.edu.

It is also still listed at http://www.debian.org/mirror/list

It is listed bad at http://mirror.debian.org/status.html

Can someone remove it from http.us.debian.org and the list until it's back?

Also, would it be possible to notify mirror admins of bad mirrors 
autoamtically in the future, so this problem can be avoided?

Meanwhile, I can't seem to find a list of rsyncable US mirrors anymore.  Does 
anyone know where that list is kept?

I'm not sure what list is best for this.  Apologies if I found the wrong one.  
(Should it be -project?  Some ticket with the admins RT?)

Thanks,

-- John


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

Re: US mirror troubles

2007-09-05 Thread Tom Moore

I get the same thing as well.
Lots of my machines hang on pulling package lists sometimes, and they 
hang for sure on package updates.

Tom

On Wed, Sep 
05, 2007 at 08:41:51PM 
-0500, 
John Goerzen wrote:
 Hi,
 
 35.9.37.225, in http.us.debian.org, and ftp.us.debian.org, has been 
 unreachable on port 80 from all the networks I have access to for days.
 
 This is ftp.egr.msu.edu.
 
 It is also still listed at http://www.debian.org/mirror/list
 
 It is listed bad at http://mirror.debian.org/status.html
 
 Can someone remove it from http.us.debian.org and the list until it's back?
 
 Also, would it be possible to notify mirror admins of bad mirrors 
 autoamtically in the future, so this problem can be avoided?
 
 Meanwhile, I can't seem to find a list of rsyncable US mirrors anymore.  Does 
 anyone know where that list is kept?
 
 I'm not sure what list is best for this.  Apologies if I found the wrong one. 
  
 (Should it be -project?  Some ticket with the admins RT?)
 
 Thanks,
 
 -- John
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 


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

Accepted sisu 0.58.1-1 (source all)

2007-09-05 Thread Ralph Amissah

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 04 Sep 2007 22:23:59 +0100
Source: sisu
Binary: sisu-sqlite sisu-postgresql sisu-pdf sisu sisu-complete
Architecture: source all
Version: 0.58.1-1
Distribution: unstable
Urgency: low
Maintainer: Ralph Amissah [EMAIL PROTECTED]
Changed-By: Ralph Amissah [EMAIL PROTECTED]
Description: 
 sisu   - documents - structuring, publishing in multiple formats and searc
 sisu-complete - installs all SiSU related packages
 sisu-pdf   - dependencies to convert SiSU LaTeX output to pdf
 sisu-postgresql - SiSU dependencies for use with postgresql database
 sisu-sqlite - SiSU dependencies for use with sqlite database
Changes: 
 sisu (0.58.1-1) unstable; urgency=low
 .
   * new upstream with minor fixes for grouped text (primarily code-blocks),
 see changelog
Files: 
 877f060a4c8e6298cf6f527f82a6b7c3 606 text optional sisu_0.58.1-1.dsc
 2b46ddfcfd9985c13535733eb822cdbd 1277392 text optional sisu_0.58.1.orig.tar.gz
 4e3492a6dccc10c2998aaae9526b46c8 142045 text optional sisu_0.58.1-1.diff.gz
 e45440c2ed902cbe7ee92f3664c15dda 1739894 text optional sisu_0.58.1-1_all.deb
 68ddf29c51b035b8be9d50d69531989c 123114 text optional 
sisu-complete_0.58.1-1_all.deb
 a15dfa11e51b1e7e50c17611369e9b68 123072 text optional sisu-pdf_0.58.1-1_all.deb
 f3f9ae1d5af8e5285bac7394f31effbf 123658 text optional 
sisu-postgresql_0.58.1-1_all.deb
 7d818d64322f93280913eb68e4724b15 123612 text optional 
sisu-sqlite_0.58.1-1_all.deb

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

iD8DBQFG3kkD+C5cwEsrK54RAvC7AJ9D65SBCNlDcHX/zbjnfClwK8kVjQCfSQ6s
9N7pwf5G2Zzj7WBrkbMFqSE=
=J5pC
-END PGP SIGNATURE-


Accepted:
sisu-complete_0.58.1-1_all.deb
  to pool/main/s/sisu/sisu-complete_0.58.1-1_all.deb
sisu-pdf_0.58.1-1_all.deb
  to pool/main/s/sisu/sisu-pdf_0.58.1-1_all.deb
sisu-postgresql_0.58.1-1_all.deb
  to pool/main/s/sisu/sisu-postgresql_0.58.1-1_all.deb
sisu-sqlite_0.58.1-1_all.deb
  to pool/main/s/sisu/sisu-sqlite_0.58.1-1_all.deb
sisu_0.58.1-1.diff.gz
  to pool/main/s/sisu/sisu_0.58.1-1.diff.gz
sisu_0.58.1-1.dsc
  to pool/main/s/sisu/sisu_0.58.1-1.dsc
sisu_0.58.1-1_all.deb
  to pool/main/s/sisu/sisu_0.58.1-1_all.deb
sisu_0.58.1.orig.tar.gz
  to pool/main/s/sisu/sisu_0.58.1.orig.tar.gz


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

Accepted epiphany-extensions 2.18.3-1 (source i386)

2007-09-05 Thread Sebastian Dröge

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 08:12:53 +0200
Source: epiphany-extensions
Binary: epiphany-extensions
Architecture: source i386
Version: 2.18.3-1
Distribution: unstable
Urgency: low
Maintainer: Josselin Mouette [EMAIL PROTECTED]
Changed-By: Sebastian DrÃ¶ge [EMAIL PROTECTED]
Description: 
 epiphany-extensions - Extensions for Epiphany web browser
Changes: 
 epiphany-extensions (2.18.3-1) unstable; urgency=low
 .
   * New upstream release.
Files: 
 f4d9ff07aaccaba94bd2dd9d87a848ac 1177 gnome optional 
epiphany-extensions_2.18.3-1.dsc
 58190405bb528d8d7d14e75fe109f9ec 1332720 gnome optional 
epiphany-extensions_2.18.3.orig.tar.gz
 fb31b99a064a76984e9010684d1b1014 7470 gnome optional 
epiphany-extensions_2.18.3-1.diff.gz
 cfe5698cd3546d0a5d037d2bb85e7a76 766460 gnome optional 
epiphany-extensions_2.18.3-1_i386.deb

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

iD8DBQFG3kvIBsBdh1vkHyERApBCAKCEbLgkgpMIUrrXrqLVsqjv8RjVQACcDbh9
7a8t5HKL9JaRCVtRfLY5pvY=
=AaV4
-END PGP SIGNATURE-


Accepted:
epiphany-extensions_2.18.3-1.diff.gz
  to pool/main/e/epiphany-extensions/epiphany-extensions_2.18.3-1.diff.gz
epiphany-extensions_2.18.3-1.dsc
  to pool/main/e/epiphany-extensions/epiphany-extensions_2.18.3-1.dsc
epiphany-extensions_2.18.3-1_i386.deb
  to pool/main/e/epiphany-extensions/epiphany-extensions_2.18.3-1_i386.deb
epiphany-extensions_2.18.3.orig.tar.gz
  to pool/main/e/epiphany-extensions/epiphany-extensions_2.18.3.orig.tar.gz


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

Accepted mono 1.2.5-2 (source i386 all)

2007-09-05 Thread Sebastian Dröge

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 07:02:15 +0200
Source: mono
Binary: libmono-peapi1.0-cil libmono-cscompmgd8.0-cil libmono-security2.0-cil 
libmono-system-runtime2.0-cil libmono-security1.0-cil libmono-relaxng2.0-cil 
mono-mjs libmono-system-web2.0-cil mono-common libmono-accessibility2.0-cil 
libmono-bytefx0.7.6.1-cil libmono-system-messaging2.0-cil libmono-system2.0-cil 
libmono-system-runtime1.0-cil libmono-relaxng1.0-cil libmono-oracle1.0-cil 
libmono-microsoft7.0-cil libmono-sharpzip0.84-cil mono-gac mono mono-mcs 
libmono-sqlite1.0-cil libmono-sharpzip0.6-cil libmono-bytefx0.7.6.2-cil 
libmono-npgsql2.0-cil libmono-data-tds1.0-cil mono-jay libmono-cairo1.0-cil 
libmono-sharpzip2.6-cil libmono-system1.0-cil libmono-npgsql1.0-cil 
libmono-system-messaging1.0-cil libmono-accessibility1.0-cil 
libmono-system-web1.0-cil mono-jit libmono-corlib1.0-cil 
libmono-microsoft8.0-cil libmono-ldap2.0-cil mono-gmcs libmono2.0-cil 
libmono1.0-cil mono-jit-dbg mono-devel libmono-system-ldap2.0-cil 
libmono-peapi2.0-cil libmono-corlib2.0-cil libmono-cairo2.0-cil 
libmono-sqlite2.0-cil libmono0 libmono-microsoft-build2.0-cil 
libmono-system-data1.0-cil libmono-dev libmono-system-ldap1.0-cil 
libmono-sharpzip2.84-cil mono-runtime libmono-winforms1.0-cil 
libmono-firebirdsql1.7-cil libmono0-dbg mono-utils libmono-cscompmgd7.0-cil 
libmono-c5-1.0-cil libmono-ldap1.0-cil libmono-data-tds2.0-cil 
libmono-winforms2.0-cil mono-dbg libmono-system-data2.0-cil 
libmono-oracle2.0-cil
Architecture: source i386 all
Version: 1.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Mono Group [EMAIL PROTECTED]
Changed-By: Sebastian DrÃ¶ge [EMAIL PROTECTED]
Description: 
 libmono-accessibility1.0-cil - Mono Accessibility library
 libmono-accessibility2.0-cil - Mono Accessibility library
 libmono-bytefx0.7.6.1-cil - Mono ByteFX.Data library
 libmono-bytefx0.7.6.2-cil - Mono ByteFX.Data library
 libmono-c5-1.0-cil - Mono C5 library
 libmono-cairo1.0-cil - Mono Cairo library
 libmono-cairo2.0-cil - Mono Cairo library
 libmono-corlib1.0-cil - Mono core library (1.0)
 libmono-corlib2.0-cil - Mono core library (2.0)
 libmono-cscompmgd7.0-cil - Mono cscompmgd library
 libmono-cscompmgd8.0-cil - Mono cscompmgd library
 libmono-data-tds1.0-cil - Mono Data library
 libmono-data-tds2.0-cil - Mono Data Library
 libmono-dev - libraries for the Mono JIT - Development files
 libmono-firebirdsql1.7-cil - Mono FirebirdSql library
 libmono-ldap1.0-cil - Mono LDAP library
 libmono-ldap2.0-cil - Mono LDAP library
 libmono-microsoft-build2.0-cil - Mono Microsoft.Build libraries
 libmono-microsoft7.0-cil - Mono Microsoft libraries
 libmono-microsoft8.0-cil - Mono Microsoft libraries
 libmono-npgsql1.0-cil - Mono Npgsql library
 libmono-npgsql2.0-cil - Mono Npgsql library
 libmono-oracle1.0-cil - Mono Oracle library
 libmono-oracle2.0-cil - Mono Oracle library
 libmono-peapi1.0-cil - Mono PEAPI library
 libmono-peapi2.0-cil - Mono PEAPI library
 libmono-relaxng1.0-cil - Mono Relaxng library
 libmono-relaxng2.0-cil - Mono Relaxng library
 libmono-security1.0-cil - Mono Security library
 libmono-security2.0-cil - Mono Security library
 libmono-sharpzip0.6-cil - Mono SharpZipLib library
 libmono-sharpzip0.84-cil - Mono SharpZipLib library
 libmono-sharpzip2.6-cil - Mono SharpZipLib library
 libmono-sharpzip2.84-cil - Mono SharpZipLib library
 libmono-sqlite1.0-cil - Mono Sqlite library
 libmono-sqlite2.0-cil - Mono Sqlite library
 libmono-system-data1.0-cil - Mono System.Data library
 libmono-system-data2.0-cil - Mono System.Data Library
 libmono-system-ldap1.0-cil - Mono System.DirectoryServices library
 libmono-system-ldap2.0-cil - Mono System.DirectoryServices library
 libmono-system-messaging1.0-cil - Mono System.Messaging library
 libmono-system-messaging2.0-cil - Mono System.Messaging Library
 libmono-system-runtime1.0-cil - Mono System.Runtime library
 libmono-system-runtime2.0-cil - Mono System.Runtime Library
 libmono-system-web1.0-cil - Mono System.Web library
 libmono-system-web2.0-cil - Mono System.Web Library
 libmono-system1.0-cil - Mono System libraries (1.0)
 libmono-system2.0-cil - Mono System libraries (2.0)
 libmono-winforms1.0-cil - Mono System.Windows.Forms library
 libmono-winforms2.0-cil - Mono System.Windows.Forms library
 libmono0   - libraries for the Mono JIT
 libmono0-dbg - libraries for the Mono JIT, debugging symbols
 libmono1.0-cil - Mono libraries (1.0)
 libmono2.0-cil - Mono libraries (2.0)
 mono   - Mono CLI (.NET) runtime
 mono-common - common files for Mono
 mono-dbg   - Mono debugging symbols
 mono-devel - Mono CLI runtime with development tools
 mono-gac   - Mono GAC tool
 mono-gmcs  - Mono C# 2.0 compiler
 mono-jay   - LALR(1) parser generator oriented to Java/CLI
 mono-jit   - fast CLI JIT/AOT compiler for Mono
 mono-jit-dbg - fast CLI JIT/AOT compiler for Mono, debugging symbols
 mono-mcs   - Mono C# compiler
 mono-mjs   - Mono JScript compiler
 mono-runtime

Accepted lucene2 2.2.0-2 (source all)

2007-09-05 Thread Jan-Pascal van Best

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 04 Sep 2007 21:02:06 +0200
Source: lucene2
Binary: liblucene2-java-doc liblucene2-java
Architecture: source all
Version: 2.2.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers [EMAIL PROTECTED]
Changed-By: Jan-Pascal van Best [EMAIL PROTECTED]
Description: 
 liblucene2-java - Full-text search engine library for Java(TM)
 liblucene2-java-doc - Documentation for Lucene
Changes: 
 lucene2 (2.2.0-2) unstable; urgency=low
 .
   * Use libdb4.5-java instead of libdb4.3-java, which is removed from Debian.
   * Move to cdbs
   * Expanded man page a little
Files: 
 7193fe281856a2deebf20028e3a97c12 1269 contrib/text optional lucene2_2.2.0-2.dsc
 4b4ec08e5f5049a3e4665935822b6214 23607 contrib/text optional 
lucene2_2.2.0-2.diff.gz
 f9cf03e17ae2a825bfb666f4ab39c44c 1093952 contrib/text optional 
liblucene2-java_2.2.0-2_all.deb
 24187df434708b9efd783397a66fa46d 2082154 contrib/doc optional 
liblucene2-java-doc_2.2.0-2_all.deb

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

iD8DBQFG3miVWSOgCCdjSDsRAt7PAJ0d6Amp9ImT/9Meyhh8tVuTfkDLAACghSHo
10UhRNLtFuE2UvTQwXg/rZs=
=mZQb
-END PGP SIGNATURE-


Accepted:
liblucene2-java-doc_2.2.0-2_all.deb
  to pool/contrib/l/lucene2/liblucene2-java-doc_2.2.0-2_all.deb
liblucene2-java_2.2.0-2_all.deb
  to pool/contrib/l/lucene2/liblucene2-java_2.2.0-2_all.deb
lucene2_2.2.0-2.diff.gz
  to pool/contrib/l/lucene2/lucene2_2.2.0-2.diff.gz
lucene2_2.2.0-2.dsc
  to pool/contrib/l/lucene2/lucene2_2.2.0-2.dsc


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

Accepted librpcsecgss 0.14-3 (source i386 sparc)

2007-09-05 Thread Anibal Monsalve Salazar

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 28 Aug 2007 13:42:11 +1000
Source: librpcsecgss
Binary: librpcsecgss-dev librpcsecgss3
Architecture: source i386 sparc
Version: 0.14-3
Distribution: unstable
Urgency: high
Maintainer: Anibal Monsalve Salazar [EMAIL PROTECTED]
Changed-By: Anibal Monsalve Salazar [EMAIL PROTECTED]
Description: 
 librpcsecgss-dev - header files and docs for librpcsecgss
 librpcsecgss3 - allows secure rpc communication using the rpcsec_gss protocol
Changes: 
 librpcsecgss (0.14-3) unstable; urgency=high
 .
   * Fix buffer overflow in RPCSEC_GSS (CVE-2007-3999).
   * Fixed the following lintian message:
 - W: librpcsecgss source: substvar-source-version-is-deprecated 
librpcsecgss-dev
Files: 
 a86e1886bc53c4de2a3d0ba900feb7e0 736 libs optional librpcsecgss_0.14-3.dsc
 58e4c4182bcdb82efc0b90f0d874f1b6 1506 libs optional librpcsecgss_0.14-3.diff.gz
 5f2b917f27f671d16270a32c9e747f47 41482 libdevel optional 
librpcsecgss-dev_0.14-3_i386.deb
 175a007185dd5e7eee7ae0df511df221 31146 libs standard 
librpcsecgss3_0.14-3_i386.deb
 ce7a0a92d08f8d1d29a0b10c2f6a94a0 44548 libdevel optional 
librpcsecgss-dev_0.14-3_sparc.deb
 b85061cebd81d5d647d59b8d75c59395 30912 libs standard 
librpcsecgss3_0.14-3_sparc.deb

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

iD8DBQFG3lbogY5NIXPNpFURApnCAJ0dax9SHHpwqb2m8I0vIMiN+xOejACeOnzG
huusA4fvJCqlCco81p17+UE=
=JA70
-END PGP SIGNATURE-


Accepted:
librpcsecgss-dev_0.14-3_i386.deb
  to pool/main/libr/librpcsecgss/librpcsecgss-dev_0.14-3_i386.deb
librpcsecgss-dev_0.14-3_sparc.deb
  to pool/main/libr/librpcsecgss/librpcsecgss-dev_0.14-3_sparc.deb
librpcsecgss3_0.14-3_i386.deb
  to pool/main/libr/librpcsecgss/librpcsecgss3_0.14-3_i386.deb
librpcsecgss3_0.14-3_sparc.deb
  to pool/main/libr/librpcsecgss/librpcsecgss3_0.14-3_sparc.deb
librpcsecgss_0.14-3.diff.gz
  to pool/main/libr/librpcsecgss/librpcsecgss_0.14-3.diff.gz
librpcsecgss_0.14-3.dsc
  to pool/main/libr/librpcsecgss/librpcsecgss_0.14-3.dsc


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

Accepted sysstat 8.0.0-1 (source i386 all)

2007-09-05 Thread Robert Luberda

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 03 Sep 2007 19:55:11 +0200
Source: sysstat
Binary: isag sysstat
Architecture: source i386 all
Version: 8.0.0-1
Distribution: unstable
Urgency: low
Maintainer: Robert Luberda [EMAIL PROTECTED]
Changed-By: Robert Luberda [EMAIL PROTECTED]
Description: 
 isag   - Interactive System Activity Grapher for sysstat
 sysstat- sar, iostat and mpstat - system performance tools for Linux
Changes: 
 sysstat (8.0.0-1) unstable; urgency=low
 .
   * New upstream version (stable):
 + daily data files format has changed again.
   * Change isag's menu section to Applications/System/Monitoring (lintian).
   * Update upstream e-mail in the copyright file.
Files: 
 3a1a7f4ebc1452c2df941a67cd72a3eb 578 admin optional sysstat_8.0.0-1.dsc
 4a8c5010d61c57284f8489660abffa9e 209423 admin optional 
sysstat_8.0.0.orig.tar.gz
 c7ee825e38ea83fcf4259b4f7a8bd8c9 25685 admin optional sysstat_8.0.0-1.diff.gz
 35847c642b2806cd9eda00f22397a0b4 24910 admin optional isag_8.0.0-1_all.deb
 e82a93ed79450aff85ee98a64ef9f221 179966 admin optional sysstat_8.0.0-1_i386.deb

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

iD8DBQFG3EwKThh1cJ0wnDsRAsM3AJ93xWAh//EKGFg4rluHRKlkOiUojwCeL24i
SBlutQ5p15J0SGg40EDL+2o=
=9yDr
-END PGP SIGNATURE-


Accepted:
isag_8.0.0-1_all.deb
  to pool/main/s/sysstat/isag_8.0.0-1_all.deb
sysstat_8.0.0-1.diff.gz
  to pool/main/s/sysstat/sysstat_8.0.0-1.diff.gz
sysstat_8.0.0-1.dsc
  to pool/main/s/sysstat/sysstat_8.0.0-1.dsc
sysstat_8.0.0-1_i386.deb
  to pool/main/s/sysstat/sysstat_8.0.0-1_i386.deb
sysstat_8.0.0.orig.tar.gz
  to pool/main/s/sysstat/sysstat_8.0.0.orig.tar.gz


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

Accepted wesnoth 1.3.7-1 (source all powerpc)

2007-09-05 Thread Gerfried Fuchs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 27 Aug 2007 11:02:08 +0200
Source: wesnoth
Binary: wesnoth-httt wesnoth-data wesnoth-sof wesnoth-nr wesnoth wesnoth-trow 
wesnoth-ei wesnoth-sotbe wesnoth-utbs wesnoth-l wesnoth-did wesnoth-ttb 
wesnoth-server wesnoth-editor wesnoth-tsg wesnoth-music
Architecture: source all powerpc
Version: 1.3.7-1
Distribution: experimental
Urgency: low
Maintainer: Isaac Clerencia [EMAIL PROTECTED]
Changed-By: Gerfried Fuchs [EMAIL PROTECTED]
Description: 
 wesnoth- fantasy turn-based strategy game
 wesnoth-data - data files for Wesnoth
 wesnoth-did - Descent into Darkness official campaign for Wesnoth
 wesnoth-editor - map editor for Wesnoth
 wesnoth-ei - Eastern Invasion official campaign for Wesnoth
 wesnoth-httt - Heir to the Throne official campaign for Wesnoth
 wesnoth-l  - Liberty official campaign for Wesnoth
 wesnoth-music - music files for Wesnoth
 wesnoth-nr - Northern Rebirth official campaign for Wesnoth
 wesnoth-server - multiplayer network server for Wesnoth
 wesnoth-sof - Sceptre of Fire official campaign for Wesnoth
 wesnoth-sotbe - Son of the Black Eye official campaign for Wesnoth
 wesnoth-trow - The Rise of Wesnoth official campaign for Wesnoth
 wesnoth-tsg - The South Guard official campaign for Wesnoth
 wesnoth-ttb - A Tale of Two Brothers official campaign for Wesnoth
 wesnoth-utbs - Under the Burning Suns official campaign for Wesnoth
Closes: 423439 435874 438173 439574
Changes: 
 wesnoth (1.3.7-1) experimental; urgency=low
 .
   * New upstream release which includes fix for:
 - crash in last Scepter of Fire scenario, closes: #438173
   * Fixed the menu xpm files--somehow they were displayed b0rked while the
 content was proper xpm, closes: #435874
   * Added XS-Vcs-{Svn,Browser} lines to control file.
   * Added Homepage: to control file, removed it from Package descriptions,
 closes: #439574
   * New campaign package: wesnoth-l
   * Install the wesnoth_editor desktop file, closes: #423439
   * Added LSB section to init.d script of wesnothd.
Files: 
 c1cab3d6eae0f4c879b545afaa8820fd 1173 games optional wesnoth_1.3.7-1.dsc
 d13fa8a08e3d4b81e961a64d92f2e453 101186470 games optional 
wesnoth_1.3.7.orig.tar.gz
 3d7f55efabe30ce660e5eb79d3d5bc06 16597 games optional wesnoth_1.3.7-1.diff.gz
 15cb9339080fe0c81cfa704eb7d2be6c 28755476 games optional 
wesnoth-data_1.3.7-1_all.deb
 34352490495fc79b56a4e9009354dbbb 30098580 games optional 
wesnoth-music_1.3.7-1_all.deb
 0474a6319eca2e609ac829e47138669d 5165388 games optional 
wesnoth-httt_1.3.7-1_all.deb
 67d877c7baecee3d35a64159de2d427e 1435374 games optional 
wesnoth-tsg_1.3.7-1_all.deb
 1ebe53303419857008a661e360d3b513 4190810 games optional 
wesnoth-trow_1.3.7-1_all.deb
 3e7bad32b8ebacce0f4d32b7bdc7c0b7 427302 games optional 
wesnoth-ttb_1.3.7-1_all.deb
 df6d5ce96d718b4537c17e189b41c3a4 1101388 games optional 
wesnoth-ei_1.3.7-1_all.deb
 1cf88b3975d928876e787fbb618b17f5 5358562 games optional 
wesnoth-utbs_1.3.7-1_all.deb
 92dcad28fe5c6592d7fa9c94328dafcc 575704 games optional 
wesnoth-did_1.3.7-1_all.deb
 64b779b133d15a9d1cfc0db897aa4f6c 4772630 games optional 
wesnoth-nr_1.3.7-1_all.deb
 2cdf1823432655912193a2a6c2cf4875 965844 games optional 
wesnoth-sof_1.3.7-1_all.deb
 08c10d28f7a6b79c9bed0e2f98dcf23d 2499458 games optional 
wesnoth-sotbe_1.3.7-1_all.deb
 aac8096e5eebeac49cb0e1b1edf63354 1564546 games optional 
wesnoth-l_1.3.7-1_all.deb
 d999ba42e96d549aed5881460857035d 2386422 games optional 
wesnoth_1.3.7-1_powerpc.deb
 0f1ed4ed28cd7d476e5082277feeff86 375102 games optional 
wesnoth-server_1.3.7-1_powerpc.deb
 3a6a4489335b18da212b528c3133f1b4 907306 games optional 
wesnoth-editor_1.3.7-1_powerpc.deb

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

iD8DBQFG0s6sELuA/Ba9d8YRAol2AJ9IxkSTy2Im9z3w8q009baVfWTeYwCgqzz5
xTYHksPAxbxgDzuWc0Vuu3E=
=XQsN
-END PGP SIGNATURE-


Accepted:
wesnoth-data_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-data_1.3.7-1_all.deb
wesnoth-did_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-did_1.3.7-1_all.deb
wesnoth-editor_1.3.7-1_powerpc.deb
  to pool/main/w/wesnoth/wesnoth-editor_1.3.7-1_powerpc.deb
wesnoth-ei_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-ei_1.3.7-1_all.deb
wesnoth-httt_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-httt_1.3.7-1_all.deb
wesnoth-l_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-l_1.3.7-1_all.deb
wesnoth-music_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-music_1.3.7-1_all.deb
wesnoth-nr_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-nr_1.3.7-1_all.deb
wesnoth-server_1.3.7-1_powerpc.deb
  to pool/main/w/wesnoth/wesnoth-server_1.3.7-1_powerpc.deb
wesnoth-sof_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-sof_1.3.7-1_all.deb
wesnoth-sotbe_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-sotbe_1.3.7-1_all.deb
wesnoth-trow_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-trow_1.3.7-1_all.deb
wesnoth-tsg_1.3.7-1_all.deb
  to pool/main/w/wesnoth/wesnoth-tsg_1.3.7-1_all.deb

Accepted tn5250 0.17.3-2 (source i386)

2007-09-05 Thread Carey Evans

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue,  4 Sep 2007 22:27:39 +1200
Source: tn5250
Binary: tn5250
Architecture: source i386
Version: 0.17.3-2
Distribution: unstable
Urgency: low
Maintainer: Carey Evans [EMAIL PROTECTED]
Changed-By: Carey Evans [EMAIL PROTECTED]
Description: 
 tn5250 - 5250 telnet emulator for accessing an IBM iSeries (AS/400)
Closes: 418731
Changes: 
 tn5250 (0.17.3-2) unstable; urgency=low
 .
   * Revert to upstream XTerm keyboard translations for function keys
 (closes: #418731).
   * Update description (OS/400 to i5/OS).
   * Change menu section to Applications/Network/Communication.
   * Update watch file to version 3, using Sourceforge redirector.
   * Rerun autoreconf with etch autotools-dev, etc.
Files: 
 397700154608ba2e3ce46ff535b21b6f 663 net extra tn5250_0.17.3-2.dsc
 c83c69b77ff44b16f6d65c57050834b1 242007 net extra tn5250_0.17.3-2.diff.gz
 54d9a8b5552dca3640105e17c7ad8304 164456 net extra tn5250_0.17.3-2_i386.deb

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

iD8DBQFG3o+ZJSzEyHPURsIRAgMWAJwMSz/+Y0UHnGM7rPmJvgkuIznS/wCghhvk
+jV4OJYCHOTrZiAauU0apt8=
=/WqL
-END PGP SIGNATURE-


Accepted:
tn5250_0.17.3-2.diff.gz
  to pool/main/t/tn5250/tn5250_0.17.3-2.diff.gz
tn5250_0.17.3-2.dsc
  to pool/main/t/tn5250/tn5250_0.17.3-2.dsc
tn5250_0.17.3-2_i386.deb
  to pool/main/t/tn5250/tn5250_0.17.3-2_i386.deb


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

Accepted taktuk 3.2.4-1 (source i386 all)

2007-09-05 Thread Lucas Nussbaum

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 11:28:48 +0200
Source: taktuk
Binary: libtaktuk0 taktuk libtaktuk0-dev
Architecture: source i386 all
Version: 3.2.4-1
Distribution: unstable
Urgency: low
Maintainer: Lucas Nussbaum [EMAIL PROTECTED]
Changed-By: Lucas Nussbaum [EMAIL PROTECTED]
Description: 
 libtaktuk0 - C bindings for taktuk
 libtaktuk0-dev - C bindings for taktuk (development files)
 taktuk - efficient, large scale, parallel remote execution of commands
Changes: 
 taktuk (3.2.4-1) unstable; urgency=low
 .
   * New upstream release.
   * Added /usr/lib/pkgconfig/taktuk.pc.
   * taktuk now suggests kanif.
Files: 
 bd2aa951587df2fcfa65162041a22652 744 net optional taktuk_3.2.4-1.dsc
 9319d96794748a32aff8ebf65ee1b522 411750 net optional taktuk_3.2.4.orig.tar.gz
 4dbdbc7cddcf6bfb7366366a935dce86 1967 net optional taktuk_3.2.4-1.diff.gz
 19210b1b8d1ef4533fb2009450a9ee24 63140 net optional taktuk_3.2.4-1_all.deb
 ac2761b7071d6016b16cf99bc96d1057 9946 libs optional libtaktuk0_3.2.4-1_i386.deb
 589f8d69b275bdd5cb1442635dc9a092 7576 devel optional 
libtaktuk0-dev_3.2.4-1_i386.deb

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

iD8DBQFG3ngv2hliNwI7P08RApa1AKCoCN4f31uxxij8s/5or0QvJVvbbQCfdjd3
skhyqUAg8CeCwR3+m09OdzA=
=OXNX
-END PGP SIGNATURE-


Accepted:
libtaktuk0-dev_3.2.4-1_i386.deb
  to pool/main/t/taktuk/libtaktuk0-dev_3.2.4-1_i386.deb
libtaktuk0_3.2.4-1_i386.deb
  to pool/main/t/taktuk/libtaktuk0_3.2.4-1_i386.deb
taktuk_3.2.4-1.diff.gz
  to pool/main/t/taktuk/taktuk_3.2.4-1.diff.gz
taktuk_3.2.4-1.dsc
  to pool/main/t/taktuk/taktuk_3.2.4-1.dsc
taktuk_3.2.4-1_all.deb
  to pool/main/t/taktuk/taktuk_3.2.4-1_all.deb
taktuk_3.2.4.orig.tar.gz
  to pool/main/t/taktuk/taktuk_3.2.4.orig.tar.gz


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

Accepted tunapie 2.0-rc10-1 (source all)

2007-09-05 Thread James Stone

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed,  5 Sep 2007 10:32:57 +0100
Source: tunapie
Binary: tunapie
Architecture: source all
Version: 2.0-rc10-1
Distribution: unstable
Urgency: low
Maintainer: James Stone [EMAIL PROTECTED]
Changed-By: James Stone [EMAIL PROTECTED]
Description: 
 tunapie- Lists audio and video streams from Shoutcast and Icecast
Changes: 
 tunapie (2.0-rc10-1) unstable; urgency=low
 .
   * New upstream release
   * Updated menu to 2.1.35 format
   * Upload sponsored by Daniel Baumann [EMAIL PROTECTED]
Files: 
 e6d690b07ff7fca42f5aeefcb058f6b6 613 net optional tunapie_2.0-rc10-1.dsc
 27f417f7c0ee2e59843ad40387eccb8a 48530 net optional 
tunapie_2.0-rc10.orig.tar.gz
 03c6d35d3315b5aa642a257f07dd9a2b 4582 net optional tunapie_2.0-rc10-1.diff.gz
 37f2ce287ef6dadcd10116dc754ee2b4 44736 net optional tunapie_2.0-rc10-1_all.deb

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

iD8DBQFG3n2d+C5cwEsrK54RAosBAKDMQKeVaafjHUiqqqcVLL/BPkFzywCfe4fp
N9gHvQdxgmnoKjjIFJyMQq8=
=00QR
-END PGP SIGNATURE-


Accepted:
tunapie_2.0-rc10-1.diff.gz
  to pool/main/t/tunapie/tunapie_2.0-rc10-1.diff.gz
tunapie_2.0-rc10-1.dsc
  to pool/main/t/tunapie/tunapie_2.0-rc10-1.dsc
tunapie_2.0-rc10-1_all.deb
  to pool/main/t/tunapie/tunapie_2.0-rc10-1_all.deb
tunapie_2.0-rc10.orig.tar.gz
  to pool/main/t/tunapie/tunapie_2.0-rc10.orig.tar.gz


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

Accepted kanif 1.0.2-1 (source all)

2007-09-05 Thread Lucas Nussbaum

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 11:40:58 +0200
Source: kanif
Binary: kanif
Architecture: source all
Version: 1.0.2-1
Distribution: unstable
Urgency: low
Maintainer: Lucas Nussbaum [EMAIL PROTECTED]
Changed-By: Lucas Nussbaum [EMAIL PROTECTED]
Description: 
 kanif  - cluster management and administration swiss army knife
Changes: 
 kanif (1.0.2-1) unstable; urgency=low
 .
   * New upstream release.
Files: 
 68908e8574a1b3487d3d52d17fd04b78 723 net optional kanif_1.0.2-1.dsc
 bbe8b90c7b1ed24eb4ffdf26656db569 90098 net optional kanif_1.0.2.orig.tar.gz
 96c19dd91c1e9cf87cdf54e682462da7 1505 net optional kanif_1.0.2-1.diff.gz
 8d079a9deb0b68ec1eacce071ecd6080 25628 net optional kanif_1.0.2-1_all.deb

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

iD8DBQFG3n+g2hliNwI7P08RAsI4AJ4i+YElisohBWP/Lm1L3pZgjXwsmACeJ4q2
2nxmI93LfX1AGlEIWS9/bbM=
=Ogyb
-END PGP SIGNATURE-


Accepted:
kanif_1.0.2-1.diff.gz
  to pool/main/k/kanif/kanif_1.0.2-1.diff.gz
kanif_1.0.2-1.dsc
  to pool/main/k/kanif/kanif_1.0.2-1.dsc
kanif_1.0.2-1_all.deb
  to pool/main/k/kanif/kanif_1.0.2-1_all.deb
kanif_1.0.2.orig.tar.gz
  to pool/main/k/kanif/kanif_1.0.2.orig.tar.gz


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

Accepted tar 1.18-2 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 10:20:45 +0100
Source: tar
Binary: tar
Architecture: source i386
Version: 1.18-2
Distribution: unstable
Urgency: high
Maintainer: Bdale Garbee [EMAIL PROTECTED]
Changed-By: Bdale Garbee [EMAIL PROTECTED]
Description: 
 tar- GNU tar
Closes: 433553 439335 439916
Changes: 
 tar (1.18-2) unstable; urgency=high
 .
   * patch from Neil Moore improving the man page, closes: #439916
   * patch from Justin Pryzby improving the man page, closes: #433553
   * patch from upstream to fix directory traversal concern on extraction
 documented in (CVE-2007-4131), closes: #439335
   * urgency to high since preceding bug has having security implications
Files: 
 87af661dc549fb89e70d4f8850859cd4 569 utils required tar_1.18-2.dsc
 7bcd67a71acb9d4c4e6b9ababc309ef9 40112 utils required tar_1.18-2.diff.gz
 d6c6861cbbf9a04cba3519f8f265d243 732978 utils required tar_1.18-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG3oA+ZKfAp/LPAagRAnQKAJwLlYJ+ar/e8eree7HkcoSPTv9LywCfWxL+
320FXmkTEdoJohy87O9D964=
=Ae4x
-END PGP SIGNATURE-


Accepted:
tar_1.18-2.diff.gz
  to pool/main/t/tar/tar_1.18-2.diff.gz
tar_1.18-2.dsc
  to pool/main/t/tar/tar_1.18-2.dsc
tar_1.18-2_i386.deb
  to pool/main/t/tar/tar_1.18-2_i386.deb


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

Accepted sudo 1.6.8p12-6 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 11:26:58 +0100
Source: sudo
Binary: sudo-ldap sudo
Architecture: source i386
Version: 1.6.8p12-6
Distribution: unstable
Urgency: low
Maintainer: Bdale Garbee [EMAIL PROTECTED]
Changed-By: Bdale Garbee [EMAIL PROTECTED]
Description: 
 sudo   - Provide limited super user privileges to specific users
 sudo-ldap  - Provide limited super user privileges to specific users
Closes: 418886 419749 438073
Changes: 
 sudo (1.6.8p12-6) unstable; urgency=low
 .
   * fix typos in visudo.pod relating to env_editor variable, closes: #418886
   * have init.d touch directories in /var/run/sudo, not just files, as a
 followup to #330868.
   * fix various typos in sudoers.pod, closes: #419749
   * don't let Makefile strip binaries, closes: #438073
Files: 
 8f067ae83ee3ae6889c938b9d7c76b1e 617 admin optional sudo_1.6.8p12-6.dsc
 85d7226ada0c4f77a7f9896ce3af5d58 35669 admin optional sudo_1.6.8p12-6.diff.gz
 ace0cb4758a6675f1ebdcb6628f4849d 163336 admin optional sudo_1.6.8p12-6_i386.deb
 528e6385219add60818add2b862587c8 173476 admin optional 
sudo-ldap_1.6.8p12-6_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG3oWPZKfAp/LPAagRAl+zAJ46hTpNMrj4iUm6HovdIJIkQs1M6wCeK/0C
ZEhyZuHmv4M+U1ccp3mwmqg=
=x9Jg
-END PGP SIGNATURE-


Accepted:
sudo-ldap_1.6.8p12-6_i386.deb
  to pool/main/s/sudo/sudo-ldap_1.6.8p12-6_i386.deb
sudo_1.6.8p12-6.diff.gz
  to pool/main/s/sudo/sudo_1.6.8p12-6.diff.gz
sudo_1.6.8p12-6.dsc
  to pool/main/s/sudo/sudo_1.6.8p12-6.dsc
sudo_1.6.8p12-6_i386.deb
  to pool/main/s/sudo/sudo_1.6.8p12-6_i386.deb


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

Accepted gnat-4.2 4.2.1-5 (source all amd64)

2007-09-05 Thread Ludovic Brenta

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue,  4 Sep 2007 23:03:57 +0200
Source: gnat-4.2
Binary: libgnatprj4.2 libgnat-4.2 libgnat-4.2-dbg gnat-4.2 libgnatvsn4.2 
gnat-4.2-base libgnatvsn4.2-dbg gnat-4.2-doc libgnatprj4.2-dbg
Architecture: source amd64 all
Version: 4.2.1-5
Distribution: unstable
Urgency: low
Maintainer: Debian GCC Maintainers [EMAIL PROTECTED]
Changed-By: Ludovic Brenta [EMAIL PROTECTED]
Description: 
 gnat-4.2   - The GNU Ada compiler
 gnat-4.2-base - The GNU Compiler Collection (gnat base package)
 gnat-4.2-doc - Documentation for the GNU Ada compiler (gnat)
 libgnat-4.2 - Runtime library for GNU Ada applications
 libgnat-4.2-dbg - Runtime library for GNU Ada applications
 libgnatprj4.2 - GNU Ada Project Manager
 libgnatprj4.2-dbg - GNU Ada Project Manager
 libgnatvsn4.2 - GNU Ada compiler version library
 libgnatvsn4.2-dbg - GNU Ada compiler version library
Closes: 434754
Changes: 
 gnat-4.2 (4.2.1-5) unstable; urgency=low
 .
   * Merge from gcc-4.2, in particular this change from 4.2.1-1:
   * Update kbsd-gnu-ada patch (Aurelien Jarno): Closes: #434754.
Files: 
 6a9a729cb268766f47cf465c4796 1993 devel optional gnat-4.2_4.2.1-5.dsc
 0eacf691ee0338d25b9f49b8b6e2848e 1401963 devel optional 
gnat-4.2_4.2.1-5.diff.gz
 a1d4fd38810014505492c391312f0f3f 1065106 doc optional 
gnat-4.2-doc_4.2.1-5_all.deb
 6943b2c739e9ba959143d632b00a93dd 389384 libs optional 
gnat-4.2-base_4.2.1-5_amd64.deb
 d9ea47ec5abc36dc936c4a17d95ec409 448032 libs optional 
libgnatprj4.2_4.2.1-5_amd64.deb
 3270422cae737674a459a1d1634164e3 498418 libdevel extra 
libgnatprj4.2-dbg_4.2.1-5_amd64.deb
 25f8ccfb3014a2d8263c19780fea337f 1105996 libs optional 
libgnat-4.2_4.2.1-5_amd64.deb
 4b1250a762f8a11a09863ebc377e7040 1401894 libdevel extra 
libgnat-4.2-dbg_4.2.1-5_amd64.deb
 08e21448b3485113779f3decbfddc795 311154 libs optional 
libgnatvsn4.2_4.2.1-5_amd64.deb
 41aad195431ff7ce631d184992e9e9d4 354726 libdevel extra 
libgnatvsn4.2-dbg_4.2.1-5_amd64.deb
 3079c8a84fe75109b3cefc651a095161 8227866 devel optional 
gnat-4.2_4.2.1-5_amd64.deb

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

iD8DBQFG3pK6x9kwJZ3/qtQRAiv0AJ9svJi6Z7JC29AzjTH9GFsbH9R9MwCeNKzY
AFqSEUItXOVcj6yTy7071Aw=
=GJBQ
-END PGP SIGNATURE-


Accepted:
gnat-4.2-base_4.2.1-5_amd64.deb
  to pool/main/g/gnat-4.2/gnat-4.2-base_4.2.1-5_amd64.deb
gnat-4.2-doc_4.2.1-5_all.deb
  to pool/main/g/gnat-4.2/gnat-4.2-doc_4.2.1-5_all.deb
gnat-4.2_4.2.1-5.diff.gz
  to pool/main/g/gnat-4.2/gnat-4.2_4.2.1-5.diff.gz
gnat-4.2_4.2.1-5.dsc
  to pool/main/g/gnat-4.2/gnat-4.2_4.2.1-5.dsc
gnat-4.2_4.2.1-5_amd64.deb
  to pool/main/g/gnat-4.2/gnat-4.2_4.2.1-5_amd64.deb
libgnat-4.2-dbg_4.2.1-5_amd64.deb
  to pool/main/g/gnat-4.2/libgnat-4.2-dbg_4.2.1-5_amd64.deb
libgnat-4.2_4.2.1-5_amd64.deb
  to pool/main/g/gnat-4.2/libgnat-4.2_4.2.1-5_amd64.deb
libgnatprj4.2-dbg_4.2.1-5_amd64.deb
  to pool/main/g/gnat-4.2/libgnatprj4.2-dbg_4.2.1-5_amd64.deb
libgnatprj4.2_4.2.1-5_amd64.deb
  to pool/main/g/gnat-4.2/libgnatprj4.2_4.2.1-5_amd64.deb
libgnatvsn4.2-dbg_4.2.1-5_amd64.deb
  to pool/main/g/gnat-4.2/libgnatvsn4.2-dbg_4.2.1-5_amd64.deb
libgnatvsn4.2_4.2.1-5_amd64.deb
  to pool/main/g/gnat-4.2/libgnatvsn4.2_4.2.1-5_amd64.deb


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

Accepted libgdchart-gd2 0.11.5-4 (source amd64)

2007-09-05 Thread Jonas Smedegaard

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 13:09:48 +0200
Source: libgdchart-gd2
Binary: libgdchart-gd2-xpm-dev libgdchart-gd2-xpm libgdchart-gd2-noxpm 
libgdchart-gd2-noxpm-dev
Architecture: source amd64
Version: 0.11.5-4
Distribution: unstable
Urgency: low
Maintainer: Jonas Smedegaard [EMAIL PROTECTED]
Changed-By: Jonas Smedegaard [EMAIL PROTECTED]
Description: 
 libgdchart-gd2-noxpm - Generate graphs using the GD library
 libgdchart-gd2-noxpm-dev - Generate graphs using the GD library (development 
version)
 libgdchart-gd2-xpm - Generate graphs using the GD library
 libgdchart-gd2-xpm-dev - Generate graphs using the GD library (development 
version)
Closes: 427326
Changes: 
 libgdchart-gd2 (0.11.5-4) unstable; urgency=low
 .
   * Add XS-Vcs-Svn and XS-Vcs-Browser fields to debian/control.
   * Bump standards-version to 3.7.2 (no changes needed).
   * Tighten d-shlibs build-dependency and adjust -noxpm override, to fix
 resolving -dev dependencies with recent libgd2 releases. Closes:
 bug#427326, thanks to Lucas Nussbaum and Luis Rodrigo Gallardo Cruz.
   * Drop deprecated fallback build-dependencies on xfree86 packages, and
 override similar dependencies resolved by d-shlibs.
   * Update CDBS tweaks:
 + Add new upstream-tarball.mk: Add get-orig-source target and more.
 + Add new copyright-check.mk: Fail building if source contains new
   or changed copyrights.
 + Update buildinfo.mk: Fix touchfile to run only once.
 + Add new buildcore.mk: Enable auto-updating build-dependencies in
   debian/control when DEB_BUILD_OPTIONS contains cdbs-autoupdate
   (replacing similar custom tweak in debian/rules).
 + Add README.cdbs-tweaks documenting the added tweaks.
 + Advertise README.cdbs-tweaks in debian/rules.
 + Use patchsys-quilt (instead of simple-patchsys).
 + Declare (and strip duplicate) build-dependencies in debian/rules.
   * Use binNMU-safe ${binary:Version} (not ${Source-Version}) in
 debian/control.
   * Semi-auto-update debian/control:
   DEB_BUILD_OPTIONS=cdbs-autoupdate fakeroot debian/rules pre-build
Files: 
 afe4374a0d2695c0f78684e92d83654c 931 libs optional libgdchart-gd2_0.11.5-4.dsc
 9cc7027b30cdc14fb52970f07c550103 10470 libs optional 
libgdchart-gd2_0.11.5-4.diff.gz
 6bd44135eebb613f91e1cf78f9503433 55918 libdevel optional 
libgdchart-gd2-noxpm-dev_0.11.5-4_amd64.deb
 0a43cedab5895431d55c0f5c7c0b19b4 55928 libdevel optional 
libgdchart-gd2-xpm-dev_0.11.5-4_amd64.deb
 0b022302d655fafdd6d454dbbaa3810f 45604 libs optional 
libgdchart-gd2-noxpm_0.11.5-4_amd64.deb
 63d1516770d164aeda096cfdf4ec2f42 45610 libs optional 
libgdchart-gd2-xpm_0.11.5-4_amd64.deb

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

iD8DBQFG3pP2n7DbMsAkQLgRAn2wAJ0T+Hq7JcWv/S01uzb72Jeff44Q4gCghkmF
cuZOSnmrO60wCezacG3/Nqc=
=48f7
-END PGP SIGNATURE-


Accepted:
libgdchart-gd2-noxpm-dev_0.11.5-4_amd64.deb
  to pool/main/libg/libgdchart-gd2/libgdchart-gd2-noxpm-dev_0.11.5-4_amd64.deb
libgdchart-gd2-noxpm_0.11.5-4_amd64.deb
  to pool/main/libg/libgdchart-gd2/libgdchart-gd2-noxpm_0.11.5-4_amd64.deb
libgdchart-gd2-xpm-dev_0.11.5-4_amd64.deb
  to pool/main/libg/libgdchart-gd2/libgdchart-gd2-xpm-dev_0.11.5-4_amd64.deb
libgdchart-gd2-xpm_0.11.5-4_amd64.deb
  to pool/main/libg/libgdchart-gd2/libgdchart-gd2-xpm_0.11.5-4_amd64.deb
libgdchart-gd2_0.11.5-4.diff.gz
  to pool/main/libg/libgdchart-gd2/libgdchart-gd2_0.11.5-4.diff.gz
libgdchart-gd2_0.11.5-4.dsc
  to pool/main/libg/libgdchart-gd2/libgdchart-gd2_0.11.5-4.dsc


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

Accepted camlzip 1.03-6 (source amd64)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 13:40:47 +0200
Source: camlzip
Binary: libzip-ocaml libzip-ocaml-dev
Architecture: source amd64
Version: 1.03-6
Distribution: unstable
Urgency: low
Maintainer: Debian OCaml Maintainers [EMAIL PROTECTED]
Changed-By: Sylvain Le Gall [EMAIL PROTECTED]
Description: 
 libzip-ocaml - ocaml compression libraries
 libzip-ocaml-dev - ocaml compression libraries
Changes: 
 camlzip (1.03-6) unstable; urgency=low
 .
   * Change distribution to unstable
   * Use ocaml = 3.10.8 to have the .doc-base.ocamldoc-apiref template
Files: 
 ed3aaaeb0c7b16855c910ac614d539df 1001 libdevel optional camlzip_1.03-6.dsc
 8b88e71c0fc82264a1a8f91b3554721d 5260 libdevel optional camlzip_1.03-6.diff.gz
 1253c8c7608592daaefa02672dd766a8 7342 libs optional 
libzip-ocaml_1.03-6_amd64.deb
 8c16c8c3d0e21fd50a3ccf65275f4a5d 90376 libdevel optional 
libzip-ocaml-dev_1.03-6_amd64.deb

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

iD8DBQFG3pXsir2bofsN/psRApFiAJ9M9ufH+EwnFOLj4TBWAU8dpln4AwCdHbSj
NNWBCXjJY1i27bfoKDz9MdU=
=wCU/
-END PGP SIGNATURE-


Accepted:
camlzip_1.03-6.diff.gz
  to pool/main/c/camlzip/camlzip_1.03-6.diff.gz
camlzip_1.03-6.dsc
  to pool/main/c/camlzip/camlzip_1.03-6.dsc
libzip-ocaml-dev_1.03-6_amd64.deb
  to pool/main/c/camlzip/libzip-ocaml-dev_1.03-6_amd64.deb
libzip-ocaml_1.03-6_amd64.deb
  to pool/main/c/camlzip/libzip-ocaml_1.03-6_amd64.deb


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

Accepted singularity 0.26a+r409-2 (source all)

2007-09-05 Thread Kari Pahula

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 14:21:01 +0300
Source: singularity
Binary: singularity
Architecture: source all
Version: 0.26a+r409-2
Distribution: unstable
Urgency: low
Maintainer: Kari Pahula [EMAIL PROTECTED]
Changed-By: Kari Pahula [EMAIL PROTECTED]
Description: 
 singularity - game where one becomes the singularity
Closes: 440736
Changes: 
 singularity (0.26a+r409-2) unstable; urgency=low
 .
   * Removed the semi-finished construction task (Closes: #440736)
Files: 
 f36f9920aad375cc7be05035636c732c 714 games optional 
singularity_0.26a+r409-2.dsc
 1ccae55286c3216bc83462205767b0a9 14731 games optional 
singularity_0.26a+r409-2.diff.gz
 22e4b469e2394639ba3846513ecef47f 1180286 games optional 
singularity_0.26a+r409-2_all.deb

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

iD8DBQFG3pMceYl9593Atw0RAp+vAJ4zoYJKOGqG4ruznCSGYLWYnfttnwCgktgD
wTVczzE794UbfbDI9aFUY0U=
=EOQC
-END PGP SIGNATURE-


Accepted:
singularity_0.26a+r409-2.diff.gz
  to pool/main/s/singularity/singularity_0.26a+r409-2.diff.gz
singularity_0.26a+r409-2.dsc
  to pool/main/s/singularity/singularity_0.26a+r409-2.dsc
singularity_0.26a+r409-2_all.deb
  to pool/main/s/singularity/singularity_0.26a+r409-2_all.deb


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

Accepted ogre 1.4.4-2 (source all amd64)

2007-09-05 Thread Andres Mejia

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 03 Sep 2007 23:38:07 -0400
Source: ogre
Binary: libogre14 libogre-dev libogre14-dbg ogre-tools-dbg ogre-tools ogre-doc 
blender-ogrexml
Architecture: source all amd64
Version: 1.4.4-2
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team [EMAIL PROTECTED]
Changed-By: Andres Mejia [EMAIL PROTECTED]
Description: 
 blender-ogrexml - Blender Exporter for Ogre
 libogre-dev - Object-oriented Graphics Rendering Engine (development files)
 libogre14  - Object-oriented Graphics Rendering Engine (libraries)
 libogre14-dbg - Object-oriented Graphics Rendering Engine (debugging libs)
 ogre-doc   - Object-oriented Graphics Rendering Engine (documentation)
 ogre-tools - Object-oriented Graphics Rendering Engine (tools)
 ogre-tools-dbg - Object-oriented Graphics Rendering Engine (tools)
Changes: 
 ogre (1.4.4-2) unstable; urgency=low
 .
   [ Andres Mejia ]
   * Added Homepage field in source stanza that will be supported soon.
   * Add Vcs-{Svn,Browser} fields in control file.
Files: 
 b4bda208fdd49c35d47dbacb32ff8b12 1135 libs optional ogre_1.4.4-2.dsc
 7fe602c37871d04e58aeb43378d4cbda 386622 libs optional ogre_1.4.4-2.diff.gz
 d260045cb85ffdd0b70bb62aff7aa7fc 7703384 doc optional ogre-doc_1.4.4-2_all.deb
 c143c5e0be0541ad34f79ecf220adbbf 266888 graphics optional 
blender-ogrexml_1.4.4-2_all.deb
 837f47f931127f7a5a169a8f118a50f6 2442308 libs optional 
libogre14_1.4.4-2_amd64.deb
 61a27f0970bc87a1016f92a4f73c2901 39591898 libdevel optional 
libogre14-dbg_1.4.4-2_amd64.deb
 c1e5057cc56f37cbaaaeef0bdd386629 716614 libdevel optional 
libogre-dev_1.4.4-2_amd64.deb
 1bc0ba117c9454b608ca3e52602310f3 292742 devel optional 
ogre-tools_1.4.4-2_amd64.deb
 14bc2d2963d4f76763ffa7b1268b3dda 3358028 devel optional 
ogre-tools-dbg_1.4.4-2_amd64.deb

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

iD8DBQFG3nRyvcCgrgZGjesRAt19AJ9MJUY2Cc7UZHElamBeG09Ikb2anACaA1AO
oI3O3dIzy5YuDXUUaS1JwW8=
=nHJX
-END PGP SIGNATURE-


Accepted:
blender-ogrexml_1.4.4-2_all.deb
  to pool/main/o/ogre/blender-ogrexml_1.4.4-2_all.deb
libogre-dev_1.4.4-2_amd64.deb
  to pool/main/o/ogre/libogre-dev_1.4.4-2_amd64.deb
libogre14-dbg_1.4.4-2_amd64.deb
  to pool/main/o/ogre/libogre14-dbg_1.4.4-2_amd64.deb
libogre14_1.4.4-2_amd64.deb
  to pool/main/o/ogre/libogre14_1.4.4-2_amd64.deb
ogre-doc_1.4.4-2_all.deb
  to pool/main/o/ogre/ogre-doc_1.4.4-2_all.deb
ogre-tools-dbg_1.4.4-2_amd64.deb
  to pool/main/o/ogre/ogre-tools-dbg_1.4.4-2_amd64.deb
ogre-tools_1.4.4-2_amd64.deb
  to pool/main/o/ogre/ogre-tools_1.4.4-2_amd64.deb
ogre_1.4.4-2.diff.gz
  to pool/main/o/ogre/ogre_1.4.4-2.diff.gz
ogre_1.4.4-2.dsc
  to pool/main/o/ogre/ogre_1.4.4-2.dsc


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

Accepted libparams-classify-perl 0.005-1 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 14:51:38 +0300
Source: libparams-classify-perl
Binary: libparams-classify-perl
Architecture: source all
Version: 0.005-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group [EMAIL PROTECTED]
Changed-By: Damyan Ivanov [EMAIL PROTECTED]
Description: 
 libparams-classify-perl - Perl module for argument type classification
Changes: 
 libparams-classify-perl (0.005-1) unstable; urgency=low
 .
   * New upstream release
Files: 
 d4ba7e012f907584225fde2d44b16ef6 1066 perl optional 
libparams-classify-perl_0.005-1.dsc
 c8be0fe096d5c95ce7d52f15a62bc7e4 6868 perl optional 
libparams-classify-perl_0.005.orig.tar.gz
 8aa1fbf15e3f7f3f32da258802654744 2255 perl optional 
libparams-classify-perl_0.005-1.diff.gz
 7828fae864df0468b309f839c0fd0665 13512 perl optional 
libparams-classify-perl_0.005-1_all.deb

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

iD8DBQFG3piGHqjlqpcl9jsRAmfUAKDEB7mhWBkrWjLQJAvbHGZ4NgTklQCfSJZq
1BFh3IvEmbsqy1MYwP1uk4k=
=Jyy2
-END PGP SIGNATURE-


Accepted:
libparams-classify-perl_0.005-1.diff.gz
  to 
pool/main/libp/libparams-classify-perl/libparams-classify-perl_0.005-1.diff.gz
libparams-classify-perl_0.005-1.dsc
  to pool/main/libp/libparams-classify-perl/libparams-classify-perl_0.005-1.dsc
libparams-classify-perl_0.005-1_all.deb
  to 
pool/main/libp/libparams-classify-perl/libparams-classify-perl_0.005-1_all.deb
libparams-classify-perl_0.005.orig.tar.gz
  to 
pool/main/libp/libparams-classify-perl/libparams-classify-perl_0.005.orig.tar.gz


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

Accepted libscalar-number-perl 0.002-1 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 15:01:53 +0300
Source: libscalar-number-perl
Binary: libscalar-number-perl
Architecture: source all
Version: 0.002-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group [EMAIL PROTECTED]
Changed-By: Damyan Ivanov [EMAIL PROTECTED]
Description: 
 libscalar-number-perl - Perl module for handling numeric aspects of scalars
Changes: 
 libscalar-number-perl (0.002-1) unstable; urgency=low
 .
   * New upstream release
   * Add myself to Uploaders:
   * debian/rules:
 + move test suite from install to build target
 + drop unneeded OPTIMIZE parameter to $(MAKE)
Files: 
 a50e0968acfe9b84896dcd91a00b3a28 974 perl optional 
libscalar-number-perl_0.002-1.dsc
 ebd958cfc9b78077e9730fc8b5efae50 9337 perl optional 
libscalar-number-perl_0.002.orig.tar.gz
 860c8e9bc258866f8ee0f3eb3f27723b 2257 perl optional 
libscalar-number-perl_0.002-1.diff.gz
 ad36f2bf61d6d365c4f33e611e7cfeb1 11728 perl optional 
libscalar-number-perl_0.002-1_all.deb

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

iD8DBQFG3psUHqjlqpcl9jsRAoOJAJ9WFgG8ubg4b/4w7SFqbZzwuNT+BQCeOpq/
U0hYGiDXiB+QvNs5/OjhBas=
=YkAV
-END PGP SIGNATURE-


Accepted:
libscalar-number-perl_0.002-1.diff.gz
  to pool/main/libs/libscalar-number-perl/libscalar-number-perl_0.002-1.diff.gz
libscalar-number-perl_0.002-1.dsc
  to pool/main/libs/libscalar-number-perl/libscalar-number-perl_0.002-1.dsc
libscalar-number-perl_0.002-1_all.deb
  to pool/main/libs/libscalar-number-perl/libscalar-number-perl_0.002-1_all.deb
libscalar-number-perl_0.002.orig.tar.gz
  to 
pool/main/libs/libscalar-number-perl/libscalar-number-perl_0.002.orig.tar.gz


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

Accepted ocurl 0.2.1-11 (source amd64)

2007-09-05 Thread Enrico Tassi

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 16 May 2007 11:52:03 +0200
Source: ocurl
Binary: libcurl-ocaml libcurl-ocaml-dev
Architecture: source amd64
Version: 0.2.1-11
Distribution: unstable
Urgency: low
Maintainer: Enrico Tassi [EMAIL PROTECTED]
Changed-By: Enrico Tassi [EMAIL PROTECTED]
Description: 
 libcurl-ocaml - ocaml curl bindings
 libcurl-ocaml-dev - ocaml libcurl bindings
Changes: 
 ocurl (0.2.1-11) unstable; urgency=low
 .
   * rebuilt against ocaml 3.10.0
   * added automatic generation of documentation
Files: 
 434f6dd7b5f9bc964e80b5e1b13d8ca2 854 libdevel optional ocurl_0.2.1-11.dsc
 a201cf7ef4731fd403776532588f21e4 3635 libdevel optional ocurl_0.2.1-11.diff.gz
 36d72139e0c3caaa7909d98f12ebc949 91562 libdevel optional 
libcurl-ocaml-dev_0.2.1-11_amd64.deb
 870323a0445b0fe5948476ab0851b877 21026 libs optional 
libcurl-ocaml_0.2.1-11_amd64.deb

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

iD8DBQFG3qzt7kkcPgEj8vIRAolGAKCZkCPnANxthVRUTqOBbCDCHDX6mwCeMl9E
GumbKCMibMQaH/zv0iwSVsU=
=Zyn0
-END PGP SIGNATURE-


Accepted:
libcurl-ocaml-dev_0.2.1-11_amd64.deb
  to pool/main/o/ocurl/libcurl-ocaml-dev_0.2.1-11_amd64.deb
libcurl-ocaml_0.2.1-11_amd64.deb
  to pool/main/o/ocurl/libcurl-ocaml_0.2.1-11_amd64.deb
ocurl_0.2.1-11.diff.gz
  to pool/main/o/ocurl/ocurl_0.2.1-11.diff.gz
ocurl_0.2.1-11.dsc
  to pool/main/o/ocurl/ocurl_0.2.1-11.dsc


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

Accepted libsub-exporter-perl 0.976-1 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 15:21:53 +0300
Source: libsub-exporter-perl
Binary: libsub-exporter-perl
Architecture: source all
Version: 0.976-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group [EMAIL PROTECTED]
Changed-By: Damyan Ivanov [EMAIL PROTECTED]
Description: 
 libsub-exporter-perl - A sophisticated exporter for custom-built routines
Changes: 
 libsub-exporter-perl (0.976-1) unstable; urgency=low
 .
   * New upstream release
   * debian/rules
 + move test suite from install to build target
 + drop unneeded OPTIMIZE parameter to $(MAKE)
 + drop unneeded dh_strip and dh_link calls
   * Added libtest-pod(-coverage)?-perl to Build-Depends for more testing
   * Added myself to Uploaders:
   * Improved debian/copyright
 + Use generic download URL
 + Corrected years of copyright
Files: 
 2bc4da20bebfa01a43eb045d0789ca8b 1014 perl optional 
libsub-exporter-perl_0.976-1.dsc
 9a3cffc080b40f3e9916aec23d7f2019 48949 perl optional 
libsub-exporter-perl_0.976.orig.tar.gz
 d424410819af88e69339f64a2706c4e6 2292 perl optional 
libsub-exporter-perl_0.976-1.diff.gz
 daded747269ab7ef86f328a4e5b1770d 48672 perl optional 
libsub-exporter-perl_0.976-1_all.deb

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

iD8DBQFG3p+dHqjlqpcl9jsRAgU+AKCLEPZM8ufGQFDqd0CSFHMI0Ndy/QCfXkDp
F37ptGsqUkv3TxfmgCH4wHc=
=AdLo
-END PGP SIGNATURE-


Accepted:
libsub-exporter-perl_0.976-1.diff.gz
  to pool/main/libs/libsub-exporter-perl/libsub-exporter-perl_0.976-1.diff.gz
libsub-exporter-perl_0.976-1.dsc
  to pool/main/libs/libsub-exporter-perl/libsub-exporter-perl_0.976-1.dsc
libsub-exporter-perl_0.976-1_all.deb
  to pool/main/libs/libsub-exporter-perl/libsub-exporter-perl_0.976-1_all.deb
libsub-exporter-perl_0.976.orig.tar.gz
  to pool/main/libs/libsub-exporter-perl/libsub-exporter-perl_0.976.orig.tar.gz


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

Accepted camomile 0.7.1-3 (source all amd64)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 04 Sep 2007 00:26:44 +0200
Source: camomile
Binary: libcamomile-ocaml-data libcamomile-ocaml-dev
Architecture: source all amd64
Version: 0.7.1-3
Distribution: unstable
Urgency: low
Maintainer: Sylvain Le Gall [EMAIL PROTECTED]
Changed-By: Sylvain Le Gall [EMAIL PROTECTED]
Description: 
 libcamomile-ocaml-data - Unicode data for OCaml
 libcamomile-ocaml-dev - Unicode library for OCaml
Changes: 
 camomile (0.7.1-3) unstable; urgency=low
 .
   * Build for ocaml 3.10.0
   * Move API documentation in to usr/share/doc/libcamomile-ocaml-dev/html/api
Files: 
 aa42c8ac1bb64e8a90ea7a4d7fd0fc08 959 libdevel optional camomile_0.7.1-3.dsc
 396f79b5c1e9d5f75f078f1221cfde51 9298 libdevel optional 
camomile_0.7.1-3.diff.gz
 5e3d01abbb3b606c64ba2e8b4dd9aa57 5011714 libdevel optional 
libcamomile-ocaml-data_0.7.1-3_all.deb
 f16189321cd07edcb17cf1350c71f1b1 1722622 libdevel optional 
libcamomile-ocaml-dev_0.7.1-3_amd64.deb

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

iD8DBQFG3qYCir2bofsN/psRAmOlAJ9tMgPoZ2fcgcx9vhqFg7pv+GIuKQCfbAG3
5MX7Y0qzGBHNqjeQX9h5/fo=
=Zmn9
-END PGP SIGNATURE-


Accepted:
camomile_0.7.1-3.diff.gz
  to pool/main/c/camomile/camomile_0.7.1-3.diff.gz
camomile_0.7.1-3.dsc
  to pool/main/c/camomile/camomile_0.7.1-3.dsc
libcamomile-ocaml-data_0.7.1-3_all.deb
  to pool/main/c/camomile/libcamomile-ocaml-data_0.7.1-3_all.deb
libcamomile-ocaml-dev_0.7.1-3_amd64.deb
  to pool/main/c/camomile/libcamomile-ocaml-dev_0.7.1-3_amd64.deb


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

Accepted xtrkcad 1:4.0.1-1 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 13:43:47 +0100
Source: xtrkcad
Binary: xtrkcad
Architecture: source i386
Version: 1:4.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Bdale Garbee [EMAIL PROTECTED]
Changed-By: Bdale Garbee [EMAIL PROTECTED]
Description: 
 xtrkcad- Model Train Track CAD Program
Closes: 424098 438353
Changes: 
 xtrkcad (1:4.0.1-1) unstable; urgency=low
 .
   * new upstream version
   * building twice in a row appears to work now, closes: #424098
   * don't strip in bin/Makefile, closes: #438353
Files: 
 f8603a89c7177fac5c43af63c9069752 621 editors optional xtrkcad_4.0.1-1.dsc
 c19e8e0321105c628766e8c0afa180c6 1361332 editors optional 
xtrkcad_4.0.1.orig.tar.gz
 c0692c411c950c8d363c56665b913ee3 3686 editors optional xtrkcad_4.0.1-1.diff.gz
 191a49478c9bccd44455631f16b3836f 816266 editors optional 
xtrkcad_4.0.1-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG3qc6ZKfAp/LPAagRAvRIAJ9K72X7BJpJProJMe/lXw1YbNb4QwCggAwm
rHzaAwfOAyufRjGIiSWOLig=
=XQMp
-END PGP SIGNATURE-


Accepted:
xtrkcad_4.0.1-1.diff.gz
  to pool/main/x/xtrkcad/xtrkcad_4.0.1-1.diff.gz
xtrkcad_4.0.1-1.dsc
  to pool/main/x/xtrkcad/xtrkcad_4.0.1-1.dsc
xtrkcad_4.0.1-1_i386.deb
  to pool/main/x/xtrkcad/xtrkcad_4.0.1-1_i386.deb
xtrkcad_4.0.1.orig.tar.gz
  to pool/main/x/xtrkcad/xtrkcad_4.0.1.orig.tar.gz


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

Accepted dsbltesters 0.9.5-2 (source i386)

2007-09-05 Thread Al Nikolov

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 13:56:02 +0400
Source: dsbltesters
Binary: dsbltesters
Architecture: source i386
Version: 0.9.5-2
Distribution: unstable
Urgency: low
Maintainer: Al Nikolov [EMAIL PROTECTED]
Changed-By: Al Nikolov [EMAIL PROTECTED]
Description: 
 dsbltesters - open proxy/relay testing utilities
Closes: 436775
Changes: 
 dsbltesters (0.9.5-2) unstable; urgency=low
 .
   * DEB_BUILD_OPTIONS=nostrip support (Closes: #436775)
Files: 
 b2ddffe616f81dea3150586bd6d79359 584 net extra dsbltesters_0.9.5-2.dsc
 af1187369e43e8ad27ab825dc30ada6b 2208 net extra dsbltesters_0.9.5-2.diff.gz
 6b0db9b28e7a535d0c4321cb6973dfca 41462 net extra dsbltesters_0.9.5-2_i386.deb

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

iD8DBQFG3qeTzWA7Wi7PmEsRAtqNAJ9ofUf76cNN6g1FMaCT0KrKyhdVXQCfekfw
G54dznQyFhzdxRfj1gtlQVQ=
=EJIq
-END PGP SIGNATURE-


Accepted:
dsbltesters_0.9.5-2.diff.gz
  to pool/main/d/dsbltesters/dsbltesters_0.9.5-2.diff.gz
dsbltesters_0.9.5-2.dsc
  to pool/main/d/dsbltesters/dsbltesters_0.9.5-2.dsc
dsbltesters_0.9.5-2_i386.deb
  to pool/main/d/dsbltesters/dsbltesters_0.9.5-2_i386.deb


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

Accepted mlpcap 0.9-11 (source amd64)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 04 Sep 2007 00:26:45 +0200
Source: mlpcap
Binary: libmlpcap-ocaml-dev libmlpcap-ocaml
Architecture: source amd64
Version: 0.9-11
Distribution: unstable
Urgency: low
Maintainer: Sylvain Le Gall [EMAIL PROTECTED]
Changed-By: Sylvain Le Gall [EMAIL PROTECTED]
Description: 
 libmlpcap-ocaml - binding of libpcap for OCaml
 libmlpcap-ocaml-dev - binding of libpcap for OCaml
Changes: 
 mlpcap (0.9-11) unstable; urgency=low
 .
   * Build for ocaml 3.10.0
   * Install documentation in the ocaml standard html/api dir
Files: 
 a0125070601bdda5f3c62d1a8c6a35da 901 libdevel optional mlpcap_0.9-11.dsc
 ce7f05ab2ab9d0180147d908d653672f 73997 libdevel optional mlpcap_0.9-11.diff.gz
 75b80d0461a0a8bf94393a521fab2594 12492 libs optional 
libmlpcap-ocaml_0.9-11_amd64.deb
 0ddd1abaa7210145cd69af0fbe3bd88f 22196 libdevel optional 
libmlpcap-ocaml-dev_0.9-11_amd64.deb

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

iD8DBQFG3qp6ir2bofsN/psRApMSAJ0f0CLYdBo2OisZg1l9sNCyonBFHwCfYioH
7QT5g+i8SVkMQTSXJYp+Y/U=
=nu8D
-END PGP SIGNATURE-


Accepted:
libmlpcap-ocaml-dev_0.9-11_amd64.deb
  to pool/main/m/mlpcap/libmlpcap-ocaml-dev_0.9-11_amd64.deb
libmlpcap-ocaml_0.9-11_amd64.deb
  to pool/main/m/mlpcap/libmlpcap-ocaml_0.9-11_amd64.deb
mlpcap_0.9-11.diff.gz
  to pool/main/m/mlpcap/mlpcap_0.9-11.diff.gz
mlpcap_0.9-11.dsc
  to pool/main/m/mlpcap/mlpcap_0.9-11.dsc


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

Accepted ocaml-benchmark 0.6-7 (source amd64)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 04 Sep 2007 00:26:45 +0200
Source: ocaml-benchmark
Binary: libbenchmark-ocaml-dev
Architecture: source amd64
Version: 0.6-7
Distribution: unstable
Urgency: low
Maintainer: Sylvain Le Gall [EMAIL PROTECTED]
Changed-By: Sylvain Le Gall [EMAIL PROTECTED]
Description: 
 libbenchmark-ocaml-dev - OCaml benchmarking library
Changes: 
 ocaml-benchmark (0.6-7) unstable; urgency=low
 .
   * Build for ocaml 3.10.0
   * Move API documentation to the standard directory of OCaml
Files: 
 be17537ea632a8fe3d82640d081916dc 852 libdevel optional 
ocaml-benchmark_0.6-7.dsc
 e9e88eba94ba845fb3ca0e74e1cef48a 3253 libdevel optional 
ocaml-benchmark_0.6-7.diff.gz
 38f1071ceac7a64f77db83c0f505fe9d 39498 libdevel optional 
libbenchmark-ocaml-dev_0.6-7_amd64.deb

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

iD8DBQFG3qxVir2bofsN/psRArZlAJ4gJg1jcNqwKw4qia7+2g+DYGelRQCfaK4K
YrRiUevw6CXLJcsjrkEAbf0=
=W+7+
-END PGP SIGNATURE-


Accepted:
libbenchmark-ocaml-dev_0.6-7_amd64.deb
  to pool/main/o/ocaml-benchmark/libbenchmark-ocaml-dev_0.6-7_amd64.deb
ocaml-benchmark_0.6-7.diff.gz
  to pool/main/o/ocaml-benchmark/ocaml-benchmark_0.6-7.diff.gz
ocaml-benchmark_0.6-7.dsc
  to pool/main/o/ocaml-benchmark/ocaml-benchmark_0.6-7.dsc


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

Accepted libmime-lite-perl 3.020-1 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 16:51:54 +0300
Source: libmime-lite-perl
Binary: libmime-lite-perl
Architecture: source all
Version: 3.020-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group [EMAIL PROTECTED]
Changed-By: Damyan Ivanov [EMAIL PROTECTED]
Description: 
 libmime-lite-perl - Perl5 module for convenient generation of MIME messages
Changes: 
 libmime-lite-perl (3.020-1) unstable; urgency=low
 .
   * New upstream release
   * Add download URL to debian/copyright
   * Add information about contrib/MailTool.pm debian/copyright
   * debian/watch version 3; drop uupdate hook
   * Drop unused dh_installdirs from debian/rules
   * Add nullmailer|mail-transport-agent to Build-Depends-Indep as well as
 other needed modules so that tests run OK
   * Add nullmailer|mail-transport-agent to Depends:
   * Added myself to Uploaders:
   * remove testout/* in clean target
Files: 
 2d222918368a9a771079c17b6b93f39a 1080 perl optional 
libmime-lite-perl_3.020-1.dsc
 e8e5e29b32bd44ddc747cc3f9b7f97da 62654 perl optional 
libmime-lite-perl_3.020.orig.tar.gz
 0766434d84c3136e3b2f187b298cd997 3570 perl optional 
libmime-lite-perl_3.020-1.diff.gz
 32d65433d3e51994973e206bbeb62b0c 74738 perl optional 
libmime-lite-perl_3.020-1_all.deb

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

iD8DBQFG3rcMHqjlqpcl9jsRAmo0AKCLXHrcXNVxm7+HMTjlQeOXDCnFMwCcC4m8
mZgM7j0ZHEd3tsGFqg2tIH4=
=wuW6
-END PGP SIGNATURE-


Accepted:
libmime-lite-perl_3.020-1.diff.gz
  to pool/main/libm/libmime-lite-perl/libmime-lite-perl_3.020-1.diff.gz
libmime-lite-perl_3.020-1.dsc
  to pool/main/libm/libmime-lite-perl/libmime-lite-perl_3.020-1.dsc
libmime-lite-perl_3.020-1_all.deb
  to pool/main/libm/libmime-lite-perl/libmime-lite-perl_3.020-1_all.deb
libmime-lite-perl_3.020.orig.tar.gz
  to pool/main/libm/libmime-lite-perl/libmime-lite-perl_3.020.orig.tar.gz


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

Accepted edos-debcheck 1.0-6 (source i386)

2007-09-05 Thread Ralf Treinen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 09:39:45 +0200
Source: edos-debcheck
Binary: edos-debcheck edos-rpmcheck
Architecture: source i386
Version: 1.0-6
Distribution: unstable
Urgency: low
Maintainer: Ralf Treinen [EMAIL PROTECTED]
Changed-By: Ralf Treinen [EMAIL PROTECTED]
Description: 
 edos-debcheck - Checks whether dependencies of debian packages can be satisfied
 edos-rpmcheck - Checks whether dependencies of RPM packages can be satisfied
Changes: 
 edos-debcheck (1.0-6) unstable; urgency=low
 .
   * Build-dependency on ocaml = 3.10 to force autobuilders to use the
 right ocaml version.
Files: 
 eac633d5e778ec30147dc7c6f8a26f33 791 devel optional edos-debcheck_1.0-6.dsc
 0f992e80324aa1fbeafaaa5d46c5fe99 5218 devel optional 
edos-debcheck_1.0-6.diff.gz
 447a148426e246dd081aa286ed688723 143914 devel optional 
edos-debcheck_1.0-6_i386.deb
 c16ac774317208a53847d9d097cf8c2a 146992 devel optional 
edos-rpmcheck_1.0-6_i386.deb

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

iD8DBQFG3rlitzWmSeC6BMERAuBGAJ4n2JVOwpYt+EL4gT+BydhK9ru2uACg3akj
hGVi+Ky8iF0qSTAN46pgtHk=
=JVAV
-END PGP SIGNATURE-


Accepted:
edos-debcheck_1.0-6.diff.gz
  to pool/main/e/edos-debcheck/edos-debcheck_1.0-6.diff.gz
edos-debcheck_1.0-6.dsc
  to pool/main/e/edos-debcheck/edos-debcheck_1.0-6.dsc
edos-debcheck_1.0-6_i386.deb
  to pool/main/e/edos-debcheck/edos-debcheck_1.0-6_i386.deb
edos-rpmcheck_1.0-6_i386.deb
  to pool/main/e/edos-debcheck/edos-rpmcheck_1.0-6_i386.deb


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

Accepted ocaml-sha 1.4-4 (source i386)

2007-09-05 Thread Eric Cooper

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 03 Sep 2007 18:18:40 -0400
Source: ocaml-sha
Binary: libsha-ocaml-dev libsha-ocaml
Architecture: source i386
Version: 1.4-4
Distribution: unstable
Urgency: low
Maintainer: Eric Cooper [EMAIL PROTECTED]
Changed-By: Eric Cooper [EMAIL PROTECTED]
Description: 
 libsha-ocaml - SHA cryptographic hash functions for OCaml
 libsha-ocaml-dev - SHA cryptographic hash functions for OCaml
Changes: 
 ocaml-sha (1.4-4) unstable; urgency=low
 .
   * Use support for ocamldoc in OCaml cdbs class
Files: 
 2fe4cb284f9a3a70a7fb7273f02826dd 838 devel optional ocaml-sha_1.4-4.dsc
 ecc821b7dfcb103e42a494ccc473f2e1 2308 devel optional ocaml-sha_1.4-4.diff.gz
 f6a0d5dc906c30c30e89af8f3a405475 30708 libs optional 
libsha-ocaml_1.4-4_i386.deb
 d0ff44844e95ca511827ab3cb1321e99 41956 libdevel optional 
libsha-ocaml-dev_1.4-4_i386.deb

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

iD8DBQFG3rxktzWmSeC6BMERAgZmAJ45HvTVt00+89cFBg8gtCOK4NTn3ACfcLkx
WkTg63CQu/BDQZW1QalXJL4=
=ui6O
-END PGP SIGNATURE-


Accepted:
libsha-ocaml-dev_1.4-4_i386.deb
  to pool/main/o/ocaml-sha/libsha-ocaml-dev_1.4-4_i386.deb
libsha-ocaml_1.4-4_i386.deb
  to pool/main/o/ocaml-sha/libsha-ocaml_1.4-4_i386.deb
ocaml-sha_1.4-4.diff.gz
  to pool/main/o/ocaml-sha/ocaml-sha_1.4-4.diff.gz
ocaml-sha_1.4-4.dsc
  to pool/main/o/ocaml-sha/ocaml-sha_1.4-4.dsc


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

Accepted elilo 3.7-1 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 15:12:13 +0100
Source: elilo
Binary: elilo
Architecture: source i386
Version: 3.7-1
Distribution: unstable
Urgency: low
Maintainer: Bdale Garbee [EMAIL PROTECTED]
Changed-By: Bdale Garbee [EMAIL PROTECTED]
Description: 
 elilo  - Bootloader for systems using EFI-based firmware
Closes: 413897 413899 414116 414211 414662 414663 414947 415369 418396 427512 
433498
Changes: 
 elilo (3.7-1) unstable; urgency=low
 .
   * new upstream version
   * patch from upstream CVS via Alex Williamson to clear vmm= options,
 closes: #433498
   * patch from Eric Schwartz to fix eliloalt, closes: #427512
   * fix typo in elilo.templates, closes: #414663
   * documentation / translation fixes coalesced by Christian Perrier
 - Remove extra spaces in debconf templates. Closes: #413899
 - Galician. Closes: #414116
 - Swedish
 - Tamil
 - German. Closes: #413897
 - French
 - Czech.
 - Portuguese. Closes: #414211
 - Brazilian Portuguese.
 - Japanese. Closes: #414662
 - Italian.
 - Romanian. Closes: #414947, #415369
   * merge Dutch translation, closes: #418396
Files: 
 9778cf5c39aad9c5b2fe8f65efade89c 578 admin optional elilo_3.7-1.dsc
 980311f59f7c7ab1aa2a77f74db825d0 398151 admin optional elilo_3.7.orig.tar.gz
 27ddcb7aa5307e72b661612fe1c06645 32206 admin optional elilo_3.7-1.diff.gz
 7242df96bdad480063ca57753f5e5223 130486 admin optional elilo_3.7-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG3rpwZKfAp/LPAagRAvzwAJ9bjdBiFFo0on/d16ZM9cQyPflqYACZAbF/
+CyMlriw99//ECZljAdkeGo=
=u5uM
-END PGP SIGNATURE-


Accepted:
elilo_3.7-1.diff.gz
  to pool/main/e/elilo/elilo_3.7-1.diff.gz
elilo_3.7-1.dsc
  to pool/main/e/elilo/elilo_3.7-1.dsc
elilo_3.7-1_i386.deb
  to pool/main/e/elilo/elilo_3.7-1_i386.deb
elilo_3.7.orig.tar.gz
  to pool/main/e/elilo/elilo_3.7.orig.tar.gz


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

Accepted pango-graphite 0.9.2-3 (source i386)

2007-09-05 Thread Daniel Glassey

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 15:13:34 +0100
Source: pango-graphite
Binary: pango-graphite pango-graphite-dbg
Architecture: source i386
Version: 0.9.2-3
Distribution: unstable
Urgency: low
Maintainer: Daniel Glassey [EMAIL PROTECTED]
Changed-By: Daniel Glassey [EMAIL PROTECTED]
Description: 
 pango-graphite - SILGraphite support for pango
 pango-graphite-dbg - SILGraphite support for pango - debug symbols
Closes: 431382
Changes: 
 pango-graphite (0.9.2-3) unstable; urgency=low
 .
   * Upload to Debian with source this time
   * [pango-graphite] broken B-D: libgraphite-dev (Closes: #431382)
   pango-graphite now includes files as graphite/blah.h not just
   blah.h
Files: 
 29ea60cea170fa9a574662fe04fb5d14 742 libs optional pango-graphite_0.9.2-3.dsc
 73fdaa761e2070b3e3572256db623c93 369076 libs optional 
pango-graphite_0.9.2.orig.tar.gz
 fd769c5ee2e098b3c8784077082807b9 2504 libs optional 
pango-graphite_0.9.2-3.diff.gz
 b85c889bc32394f0da3d9ccfcd3a9212 23184 libs optional 
pango-graphite_0.9.2-3_i386.deb
 75e78df2c4ba55a594c7be28989d2eff 180016 libdevel optional 
pango-graphite-dbg_0.9.2-3_i386.deb

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

iD8DBQFG3r5p/offrSwPzRoRAg7UAJ9fm/tHY9oOlz5kgXLqn2MqnkACYwCguW+A
6qVdKT18L7ciTp9DfwmvxR8=
=Sf4y
-END PGP SIGNATURE-


Accepted:
pango-graphite-dbg_0.9.2-3_i386.deb
  to pool/main/p/pango-graphite/pango-graphite-dbg_0.9.2-3_i386.deb
pango-graphite_0.9.2-3.diff.gz
  to pool/main/p/pango-graphite/pango-graphite_0.9.2-3.diff.gz
pango-graphite_0.9.2-3.dsc
  to pool/main/p/pango-graphite/pango-graphite_0.9.2-3.dsc
pango-graphite_0.9.2-3_i386.deb
  to pool/main/p/pango-graphite/pango-graphite_0.9.2-3_i386.deb
pango-graphite_0.9.2.orig.tar.gz
  to pool/main/p/pango-graphite/pango-graphite_0.9.2.orig.tar.gz


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

Accepted ocaml-fileutils 0.3.0-13 (source amd64)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 04 Sep 2007 00:26:45 +0200
Source: ocaml-fileutils
Binary: libfileutils-ocaml-dev
Architecture: source amd64
Version: 0.3.0-13
Distribution: unstable
Urgency: low
Maintainer: Sylvain Le Gall [EMAIL PROTECTED]
Changed-By: Sylvain Le Gall [EMAIL PROTECTED]
Description: 
 libfileutils-ocaml-dev - File manipulation for OCaml
Changes: 
 ocaml-fileutils (0.3.0-13) unstable; urgency=low
 .
   * Build for ocaml 3.10.0
Files: 
 83f954215f76576259a709af5fafce4a 882 libdevel optional 
ocaml-fileutils_0.3.0-13.dsc
 aae413fe6da8c171ba7869ce055b2c1e 3672 libdevel optional 
ocaml-fileutils_0.3.0-13.diff.gz
 11a13747664853780d658e478eab093b 220378 libdevel optional 
libfileutils-ocaml-dev_0.3.0-13_amd64.deb

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

iD8DBQFG3r95ir2bofsN/psRAvVKAJ0eG+F4aX37YP7/2d8vOj1NMU72EwCgjElT
C2f4n4iWX4WU/7eitxTW+YY=
=Ktuh
-END PGP SIGNATURE-


Accepted:
libfileutils-ocaml-dev_0.3.0-13_amd64.deb
  to pool/main/o/ocaml-fileutils/libfileutils-ocaml-dev_0.3.0-13_amd64.deb
ocaml-fileutils_0.3.0-13.diff.gz
  to pool/main/o/ocaml-fileutils/ocaml-fileutils_0.3.0-13.diff.gz
ocaml-fileutils_0.3.0-13.dsc
  to pool/main/o/ocaml-fileutils/ocaml-fileutils_0.3.0-13.dsc


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

Accepted maildir-filter 1.20-2 (source i386)

2007-09-05 Thread Daniel Ruoso

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed,  5 Sep 2007 15:11:17 +0100
Source: maildir-filter
Binary: maildir-filter
Architecture: source i386
Version: 1.20-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Ruoso [EMAIL PROTECTED]
Changed-By: Daniel Ruoso [EMAIL PROTECTED]
Description: 
 maildir-filter - Simple program to filter messages into Maildir folders from 
dot-q
Closes: 390051 422610
Changes: 
 maildir-filter (1.20-2) unstable; urgency=low
 .
   * Check the return of realloc in maildir-filter.c:108
 (Closes: #422610).
   * Uses a more efficient alogorithm, provided by Steve Langasek.
   * Fixes a minor typing error (Closes: #390051).
   * Removes reference to homepage, as its offline for a very long time
 now.
   * Updated standards-version.
   * Removed reference to non-free package in suggests.
   * Promoted to DH_COMPAT 5.
   * No longer ignores make clean errors.
Files: 
 f4a677c69d8dfc9adc1cf90950aac488 598 mail optional maildir-filter_1.20-2.dsc
 d57d122509d96c7440d983ee0cdfd474 2798 mail optional 
maildir-filter_1.20-2.diff.gz
 11d01e7175fa7148d562563883e7168f 7698 mail optional 
maildir-filter_1.20-2_i386.deb

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

iD8DBQFG3sBmHXNlp1WBXUIRAlqMAKCnvx/i/hvt56xGLXFIQ9cWzTsVYACeNbU5
DI0fNWSHDku+ni8/BKDp7po=
=MoH4
-END PGP SIGNATURE-


Accepted:
maildir-filter_1.20-2.diff.gz
  to pool/main/m/maildir-filter/maildir-filter_1.20-2.diff.gz
maildir-filter_1.20-2.dsc
  to pool/main/m/maildir-filter/maildir-filter_1.20-2.dsc
maildir-filter_1.20-2_i386.deb
  to pool/main/m/maildir-filter/maildir-filter_1.20-2_i386.deb


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

Accepted pida 0.5.1-2 (source i386)

2007-09-05 Thread Jan Luebbe

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 05 Sep 2007 17:54:09 +0200
Source: pida
Binary: pida
Architecture: source i386
Version: 0.5.1-2
Distribution: unstable
Urgency: low
Maintainer: Jan Luebbe [EMAIL PROTECTED]
Changed-By: Jan Luebbe [EMAIL PROTECTED]
Description: 
 pida   - Python Integrated Development Application, a Python IDE
Closes: 349009 394860 421378 436431 440375
Changes: 
 pida (0.5.1-2) unstable; urgency=low
 .
   * Depend on librsvg2-common, which is not pulled in by the other depends
 (closes: #394860)
   * gvim is no alternative for python-gnome2 and python-gnome2-extras
 (closes: #436431)
   * Pida now uses ~/.pida2, so it can no longer be confused by old
 configurations (closes: #421378)
   * Culebra is no longer supported by upstream (closes: #349009)
   * Update manpage (closes: #440375)
   * Update watchfile (pida is now called PIDA)
Files: 
 889582aa5bfc6aec0a1fec0a95569334 672 devel optional pida_0.5.1-2.dsc
 c6bf63e4ab609b604c2e9129f439177f 4785 devel optional pida_0.5.1-2.diff.gz
 f066ae0b19cf8bcebca1e43708cff13d 425008 devel optional pida_0.5.1-2_i386.deb

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

iD8DBQFG3tHsioOL5NhIDy4RAtzNAJ9Vam/9CYM05kVu2IuRAqzLThNXUACgqUHD
wupNppNKz5jnByYBPZNF7rI=
=EcXe
-END PGP SIGNATURE-


Accepted:
pida_0.5.1-2.diff.gz
  to pool/main/p/pida/pida_0.5.1-2.diff.gz
pida_0.5.1-2.dsc
  to pool/main/p/pida/pida_0.5.1-2.dsc
pida_0.5.1-2_i386.deb
  to pool/main/p/pida/pida_0.5.1-2_i386.deb


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

Accepted elilo 3.7-2 (source i386)