date:20050921

On Tue, Sep 20, 2005 at 11:41:13PM +0200, Andreas Barth wrote:

 Now, looking more into details, the criteria are:
 |  * Availability:
 | The architecture needs to be available for everybody, i.e.
 The reason for this should be obvious

The requirement of available as new has been dropped? Good. 

 | it must be available without NDAs and
 Same for this. We're about free software.
 | it must be possible to buy machines on the market.
 The reason should be obvious: Our users should be able to use the
 architecture.

And it doesn't matter if you can buy that piece of hardware in shops or on
ebay? Good.

 |  * Developer availability: The architecture must have a
 |developer-available (i.e. debian.org) machine that contains the
 |usual development chroots (at least stable, testing, unstable).
 This criterion is there so that any developer can actually find out what the
 issue is if his package fails to work on a specific architecture.  Of
 course, when adding a new architecture, there will be a time without a
 stable release, and there will be some special arrangement how such a
 machine can be provided without having even some packages in testing.  But
 that's not meant as a no-go, as long as we are quite optimistic that adding
 the new machine will actually work in time.

Well, for established ports, that shouldn't be a big deal, right?
For new ports this could be a chicken/egg problem, but you mentioned some
special arrangements, so I guess, that's no problem as well. 

 |  * Users: The architecture needs to prove that developers and users
 |are actually using it. Five Developers needs to certify in that
 |they're actively developing on this architecture, and it needs to
 |be demonstrated that at least 50 users are using the platform. We
 |are counting users, not machines; e.g., one s390-installation
 |with 50,000 users fullfils the user criterion just fine.
 As already discussed multiple times, the 50 users really means 50
 individuals using that architecture.  Both criteria are there to make
 sure that an architecture gets just enough usage so that
 architecture-specific bugs are found in time.

Although it was discussed several times, I have still no idea how those
users should be counted? 
Who has to show those numbers? The users? The porters?
Is it intended that a user should mail debian-release to say Hi! I'm using
port X!? I doubt so. 
So, a little more info is needed, how those numbers are counted. 
Are users just meant to be ordinary users of does that included developers?
Are developers meant to be DDs or are other developers count as well? 
F.e. Roman Zippel on m68k does a lot of development work and even hinted
Wouter Verhelst to a solution for the gcc 4.0 ICE bugs, but he's not a DD. 

 |  * Installer: The architecture must have a working, tested installer.
 Obviously, we need an installer. Though that doesn't say debian
 installer, we think that our users expect that there are not too many
 different ways for them to install the released version of Debian etch one
 day.

Some obscure bootloader and a tarball of a mini-installation would be fine
as well?

 |  * Porters and Upstream support: There is support by the porters and
 |upstream. This is especially true for the toolchain and the
 |kernel.
 Obviously, we cannot keep a port alive if there is nobody doing support for
 it.  Of course, it is quite possible that Debian and upstream support is
 done by the same persons.  And our experiences with support of gcc-4.0
 on m68k have shown that it is possible to get such issues fixed, if the
 porters are notified in time and are really interested in their port (and
 if there are enough porters).

Uh, well, I hope that slower archs will be given a large time frame to fix
things than faster archs? It would be unfair to give just a week time to fix
a problem, when the recompilation of the package would take 10 days,
wouldn't it? ;)

 |  * Archive coverage: The architecture needs to have successfully
 |compiled the current version of the overwhelming part of the
 |archive, excluding architecture-specific packages.
 Our back-of-the-envelope number for this criterion is 98%.  As pointed
 out multiple times during recent discussions, we don't have a good way
 to measure an architecture's compliance with this yet, but we'll work on
 figuring that out; of course we will exclude hardware-specific packages and
 buggy optional/extra packages with severe portability issues, but
 porters must take responsibility for working with maintainers to fix
 portability issues.

I still believe this definition is far too strict (without being precise).
You can't say, you have to be 98% uptodate without saying what you
understand by being uptodate. As already outlined during the last
discussion: when all m68k buildds are building package, that can easily be
more than 110 packages marked as building and therefore missing as installed
(given a total of 5500 packages).

Re: architecture-specific release criteria - requalification needed

[Ingo Juergensmann]
 Although it was discussed several times, I have still no idea how those
 users should be counted? 

Two ideas.

 - Get them to install popularity-contest.  This will make their
   machine show up on popcon.debian.org, and we would assume there are
   users of the given machine.  Not very accurate, as machines !=
   individuals.  Easy to fool, but I believe we should assume people
   are honest.

 - Set up a wiki page, and get people to put up their name and mail
   address (perhaps slightly obfuscated to make it harder for address
   harwesters), and count the number of names on the page.  When the
   count is reached, send email to all the addresses asking them to
   confirm that the list is correct.  Easy to fool, but I believe we
   should assume people are honest.  If we start to suspect
   non-existing people on the list, we can start asking for GPG
   signatures.

I would recommend the last option myself, but would like all m68k
machines to report to popcon.debian.org too. :)

 Is it intended that a user should mail debian-release to say Hi!
 I'm using port X!? I doubt so.

That is probably not necessary, yes. :)


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

Re: architecture-specific release criteria - requalification needed

2005-09-21 Thread Josselin Mouette

Le mardi 20 septembre 2005 à 23:41 +0200, Andreas Barth a écrit :
 For that reason, we discussed in multiple meetings, together with porters,
 ftp-masters and other people more than once how the criteria should
 look.  Also, there was more than one discussion on debian-devel. [1, 2]

This has been indeed discussed to death. The result of the discussion
seems to be that a large majority of the developers doesn't agree with
all your criteria. Why are you trying to force this change regardless of
that? It will only result in resurrecting the neverending discussion on
debian-devel.
-- 
 .''`.   Josselin Mouette/\./\
: :' :   [EMAIL PROTECTED]
`. `'[EMAIL PROTECTED]
   `-  Debian GNU/Linux -- The power of freedom

Re: architecture-specific release criteria - requalification needed

On Wed, Sep 21, 2005 at 03:19:16PM +0200, Petter Reinholdtsen wrote:
 [Ingo Juergensmann]
  Although it was discussed several times, I have still no idea how those
  users should be counted? 
 Two ideas.
  - Get them to install popularity-contest.  This will make their
machine show up on popcon.debian.org, and we would assume there are
users of the given machine.  Not very accurate, as machines !=
individuals.  Easy to fool, but I believe we should assume people
are honest.

Well, I'm already running popcon on my two m68ks, but that doesn't say much
about how many users are using that machines, as you state yourself. ;)

  - Set up a wiki page, and get people to put up their name and mail
address (perhaps slightly obfuscated to make it harder for address
harwesters), and count the number of names on the page.  When the
count is reached, send email to all the addresses asking them to
confirm that the list is correct.  Easy to fool, but I believe we
should assume people are honest.  If we start to suspect
non-existing people on the list, we can start asking for GPG
signatures.
 I would recommend the last option myself, but would like all m68k
 machines to report to popcon.debian.org too. :)

I'm already in the progress of setting up such a webpage... 
I think I can finish it this evening.

  Is it intended that a user should mail debian-release to say Hi!
  I'm using port X!? I doubt so.
 That is probably not necessary, yes. :)

... and can be faked easily, too. ;)

-- 
Ciao...//Fon: 0381-2744150 
  Ingo   \X/ SIP: [EMAIL PROTECTED]

gpg pubkey: http://www.juergensmann.de/ij/public_key.asc


signature.asc
Description: Digital signature

Re: architecture-specific release criteria - requalification needed

[Josselin Mouette]
 This has been indeed discussed to death. The result of the
 discussion seems to be that a large majority of the developers
 doesn't agree with all your criteria.

I guess that depends on the viewpoint of the reader what the results
were.  It is hard to tell if there is a vocal minority making a lot of
noise, or if there is a majority disagreeing with the criteria.

Personally, I find the list of requirements sensible, and very
understandable after the clarifying rounds on the lists.  This colors
my view of the discussion.


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

Re: architecture-specific release criteria - requalification needed

* Ingo Juergensmann ([EMAIL PROTECTED]) [050921 14:54]:
 On Tue, Sep 20, 2005 at 11:41:13PM +0200, Andreas Barth wrote:
  |  * Developer availability: The architecture must have a
  |developer-available (i.e. debian.org) machine that contains the
  |usual development chroots (at least stable, testing, unstable).
  This criterion is there so that any developer can actually find out what the
  issue is if his package fails to work on a specific architecture.  Of
  course, when adding a new architecture, there will be a time without a
  stable release, and there will be some special arrangement how such a
  machine can be provided without having even some packages in testing.  But
  that's not meant as a no-go, as long as we are quite optimistic that adding
  the new machine will actually work in time.

 Well, for established ports, that shouldn't be a big deal, right?

I so wish this would be true ...

  |  * Installer: The architecture must have a working, tested installer.
  Obviously, we need an installer. Though that doesn't say debian
  installer, we think that our users expect that there are not too many
  different ways for them to install the released version of Debian etch one
  day.

 Some obscure bootloader and a tarball of a mini-installation would be fine
 as well?

Well, probably not. As I said, we think that our users expect that there
are not too many different ways for them to install the released version
of Debian etch one day. So, there shouldn't be ten different and obscure
installers. But in the end, that will be of course a case-by-case
decision.


  |  * Porters and Upstream support: There is support by the porters and
  |upstream. This is especially true for the toolchain and the
  |kernel.
  Obviously, we cannot keep a port alive if there is nobody doing support for
  it.  Of course, it is quite possible that Debian and upstream support is
  done by the same persons.  And our experiences with support of gcc-4.0
  on m68k have shown that it is possible to get such issues fixed, if the
  porters are notified in time and are really interested in their port (and
  if there are enough porters).
 
 Uh, well, I hope that slower archs will be given a large time frame to fix
 things than faster archs? It would be unfair to give just a week time to fix
 a problem, when the recompilation of the package would take 10 days,
 wouldn't it? ;)

I think the current way with m68k really works for all involved parties
(at least it does from my point of view :).

  |  * Archive coverage: The architecture needs to have successfully
  |compiled the current version of the overwhelming part of the
  |archive, excluding architecture-specific packages.
  Our back-of-the-envelope number for this criterion is 98%.  As pointed
  out multiple times during recent discussions, we don't have a good way
  to measure an architecture's compliance with this yet, but we'll work on
  figuring that out; of course we will exclude hardware-specific packages and
  buggy optional/extra packages with severe portability issues, but
  porters must take responsibility for working with maintainers to fix
  portability issues.
 
 I still believe this definition is far too strict (without being precise).
 You can't say, you have to be 98% uptodate without saying what you
 understand by being uptodate. As already outlined during the last
 discussion: when all m68k buildds are building package, that can easily be
 more than 110 packages marked as building and therefore missing as installed
 (given a total of 5500 packages). 
 Currently m68k has ~650 packages listed that are not in state Installed (203
 Needs-Build, 142 Building, 180 Failed, 123 Dep-Wait (+ 5 Failed-Removed + 25
 Not-For-Us)). That's roughly 6% of all packages. 
 And when does that percent mark need to be reached? After freeze or at any
 time before a release?

Basically any time. However, we might need to readjust the number. If it
makes you feel better, please read the number above as a very high
number.


  When reviewing the past however, m68k as the architecture with the most
  autobuilders isn't performing too bad regarding the availability of the
  autobuilders.  So, there is the chance for m68k to get grandfathered in
  for this clause.  However, we expect that they explain why the higher
  numbers of buildds they use are not as bad increasing the maintenance
  overhead.
 
 I think (and believe that many DDs will agree) that m68k, although being one
 of the slowest archs, is one of the most responsive ports within Debian and
 that having that many buildds is nothing negative at all. 

As I said: We think the m68k port is doing well, and for this reason, we
consider to grandfather it in. But that won't happen without a mail from
one of the porters asking us to do it, and providing some facts why this
is a good idea. :)


  |keeps their autobuilders running for 24x7,
  Of course, autobuilders can have hardware maintainence.  But the

Re: architecture-specific release criteria - requalification needed

* Josselin Mouette ([EMAIL PROTECTED]) [050921 15:25]:
 Le mardi 20 septembre 2005 à 23:41 +0200, Andreas Barth a écrit :
  For that reason, we discussed in multiple meetings, together with porters,
  ftp-masters and other people more than once how the criteria should
  look.  Also, there was more than one discussion on debian-devel. [1, 2]

 This has been indeed discussed to death. The result of the discussion
 seems to be that a large majority of the developers doesn't agree with
 all your criteria. Why are you trying to force this change regardless of
 that? It will only result in resurrecting the neverending discussion on
 debian-devel.

I disagree with you. All of the discussions that I had have shown me
that most of the developers agree with the basic goals. Of course, some
of the discussions were unnecessary heated through presenting the ideas
in a too mixed way with other ideas.

And, BTW, there is no trying to force. We need to explicitly set
architecture requirements, or etch will become even worse manageable
than sarge was. For this reason, the release team decided that this list
is now part of the release policy, as well as the RC criteria list is
part of our release policy.


Cheers,
Andi


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

Re: architecture-specific release criteria - requalification needed

* Ingo Juergensmann ([EMAIL PROTECTED]) [050921 15:28]:
 On Wed, Sep 21, 2005 at 03:19:16PM +0200, Petter Reinholdtsen wrote:
  [Ingo Juergensmann]
   Although it was discussed several times, I have still no idea how those
   users should be counted? 
  Two ideas.
   - Get them to install popularity-contest.  This will make their
 machine show up on popcon.debian.org, and we would assume there are
 users of the given machine.  Not very accurate, as machines !=
 individuals.  Easy to fool, but I believe we should assume people
 are honest.

 Well, I'm already running popcon on my two m68ks, but that doesn't say much
 about how many users are using that machines, as you state yourself. ;)

Well, it's up to the porters to count the users, but of course, if you
state that you have two m68ks with 10 users each, that counts as 20
users.

Of course, I might get curious how big the m68ks are, or how much work
the people really do on them, and we may ask on further input. :)


Cheers,
Andi


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

Request: Anyone able to test printing with CUPS on woody?

2005-09-21 Thread Kevin B. McCarty

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi folks,

I've come across a strange behavior printing a certain postscript file
with the CUPS server in Sarge.  (See bug # 329207 for further details.)
 I would like to request someone who is still running oldstable - Woody
- - to see whether or not two files will print correctly on the Woody
version of CUPS.  Specifically, I need someone who is using the generic
Foomatic/Postscript driver on their CUPS server.

If you still have a Woody CUPS server with that driver and you are
willing to run the test (just printing a couple of one-page PostScript
files), please email me privately for further details.

Thanks,

- --
Kevin B. McCarty [EMAIL PROTECTED]   Physics Department
WWW: http://www.princeton.edu/~kmccarty/Princeton University
GPG: public key ID 4F83C751 Princeton, NJ 08544
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDMWQ8fYxAIk+Dx1ERAirsAJ4wGt+ntnH995LENdQfyq0fSs2yEQCfY2A2
p+ilg4fFttZK0g75Si8pGlI=
=bhxp
-END PGP SIGNATURE-


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

modifying home directories by maintainer scripts (was: Re: Bug#329347: common-lisp-controller: checking of permissions of the output directory)

2005-09-21 Thread René van Bevern

On 21.09.05, Faré wrote:
 On 9/21/05, René van Bevern [EMAIL PROTECTED] wrote:
  On 21.09.05, Faré wrote:
 
  Hi Faré,
 
   The only possible downside is having to walk /etc/passwd to locate
   all the places where to purge the cache, if you wish to do such
   thing.
 
  No, it is the plain and true evil for package maintainer scripts to
  delete or modify files in users' home directories. It's the user's
  personal space and you never know what he uses ~/.cache for. The
  system should never modify the home directory and I do not know of one
  single package that does.

Hi Faré,

 A lot of packages install stuff in the user directory.

I doubt that any package does this.

 Mozilla, Gimp, OpenOffice, KDE, GNOME, etc., will all create their
 own directories under ~/.foo and install a shitload of crap.

But this is done by the applications themselves and not by packages or
their maintainer scripts -- and not for all home directories they can
find. It's up to each user if that happens or not.

 Sometimes, their offer to upgrade from a previous version,
 and optionally offer to delete cruft from previous versions.

That is fine. The application themselves can offer transitions from
previous versions. But a maintainer script in a package that runs
through the home directory of all users to delete files is not fine.

The applications *offer* it, it's in the user's hands what happens
finally. This would not be the case if a maintainer script traversed
all home directories to delete caches.

 Modifying users' directories is something done casually.

Not by packages or their scripts and not without user
interaction. It's dangerous.

René



pgpA0HEoIUOhc.pgp
Description: PGP signature

Re: architecture-specific release criteria - requalification needed

2005-09-21 Thread Kalle Kivimaa

Petter Reinholdtsen [EMAIL PROTECTED] writes:
 I guess that depends on the viewpoint of the reader what the results
 were.  It is hard to tell if there is a vocal minority making a lot of
 noise, or if there is a majority disagreeing with the criteria.

It's actually pretty easy. Count the number of posters that seem to
disagree. If this number is over half of the current developer count,
then yes, a majority of the developers are in opposition. What you
_cannot_ do is say because over 50% of the people participating in
the discussion disagree with the proposal, over 50% of the developers
disagree.

 Personally, I find the list of requirements sensible, and very
 understandable after the clarifying rounds on the lists.  This colors
 my view of the discussion.

Me too.

-- 
* Sufficiently advanced magic is indistinguishable from technology (T.P)  *
*   PGP public key available @ http://www.iki.fi/killer   *


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

Re: architecture-specific release criteria - requalification needed

[Kalle Kivimaa]
 It's actually pretty easy. Count the number of posters that seem to
 disagree. If this number is over half of the current developer
 count, then yes, a majority of the developers are in
 opposition. What you _cannot_ do is say because over 50% of the
 people participating in the discussion disagree with the proposal,
 over 50% of the developers disagree.

Counting and verifying that the number of participants in the
discussion was less then half the number of DDs will not really tell
us anything, as we can not reasonably claim anything about the meaning
of the silent majority.

There is no doubt that most of the debian developers did not
participate in the discussion.  This does not tell anything about
those not participating.  They could agree, disagree, or not care.

I suspect your retorical suggestion would lead you to conclude that
there only was a vocal minority protesting against the suggestion, but
it could equally well lead to the conclusion that there was a vocal
minority proposing this list of requirements.

It is probably safe to avoid drawing any conclusions based on these
criteria, and instead use ones own judgement when weighting the
arguments previosly presented in the way too long mailing list thread.


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

Re: architecture-specific release criteria - requalification needed

On Wed, Sep 21, 2005 at 03:46:14PM +0200, Andreas Barth wrote:

  Well, I'm already running popcon on my two m68ks, but that doesn't say much
  about how many users are using that machines, as you state yourself. ;)
 Well, it's up to the porters to count the users, but of course, if you
 state that you have two m68ks with 10 users each, that counts as 20
 users.
 Of course, I might get curious how big the m68ks are, or how much work
 the people really do on them, and we may ask on further input. :)

Aha! 
That's not only must have 50 users but more a must have 50 users that do
stuff on those machines. 
See, that's the problem, when you don't define those rules exactly: what
qualifies for a user - how often needs the user on the machine, how much
time must he waste there, and so on and so on?
Is it ok when a user only logins every half year or is it needed that he is
there on a daily basis? Does it qualify as a user when there's an IMAP
folder that the user is using or maybe a uucp account?
It's difficult to judge when a user is a user sometimes... ;)

-- 
Ciao...//Fon: 0381-2744150 
  Ingo   \X/ SIP: [EMAIL PROTECTED]

gpg pubkey: http://www.juergensmann.de/ij/public_key.asc


signature.asc
Description: Digital signature

Re: architecture-specific release criteria - requalification needed

2005-09-21 Thread Steinar H. Gunderson

On Wed, Sep 21, 2005 at 04:22:27PM +0200, Ingo Juergensmann wrote:
 That's not only must have 50 users but more a must have 50 users that do
 stuff on those machines. 
 See, that's the problem, when you don't define those rules exactly: what
 qualifies for a user - how often needs the user on the machine, how much
 time must he waste there, and so on and so on?

Come on -- seriously, if a port has a problem demonstrating 50 users in a
form that is acceptable to the release team, it has a problem anyhow. Heck,
almost every port I can think of (perhaps except s390) should be able to
easily gather 50 people on IRC from a machine running that architecture,
announcing “hey, I'm a user!” :-) I do not seriously think this will be a
blocked for any realistic architecture.

/* Steinar */
-- 
Homepage: http://www.sesse.net/


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

Re: architecture-specific release criteria - requalification needed

On Wed, Sep 21, 2005 at 03:37:25PM +0200, Andreas Barth wrote:

   |  * Developer availability: The architecture must have a
   |developer-available (i.e. debian.org) machine that contains the
   |usual development chroots (at least stable, testing, unstable).
   This criterion is there so that any developer can actually find out what 
   the
   issue is if his package fails to work on a specific architecture.  Of
   course, when adding a new architecture, there will be a time without a
   stable release, and there will be some special arrangement how such a
   machine can be provided without having even some packages in testing.  But
   that's not meant as a no-go, as long as we are quite optimistic that 
   adding
   the new machine will actually work in time.
  Well, for established ports, that shouldn't be a big deal, right?
 I so wish this would be true ...

*giggle*
Yes, I've heard stories where someone wanted to use such a machine, but
wasn't allowed to built a package there, because that machine (a SMP box)
was running a buildd as well. So, there was actually a machine available,
but of no big use. 

  I still believe this definition is far too strict (without being precise).
  You can't say, you have to be 98% uptodate without saying what you
  understand by being uptodate. As already outlined during the last
  discussion: when all m68k buildds are building package, that can easily be
  more than 110 packages marked as building and therefore missing as installed
  (given a total of 5500 packages). 
  Currently m68k has ~650 packages listed that are not in state Installed (203
  Needs-Build, 142 Building, 180 Failed, 123 Dep-Wait (+ 5 Failed-Removed + 25
  Not-For-Us)). That's roughly 6% of all packages. 
  And when does that percent mark need to be reached? After freeze or at any
  time before a release?
 Basically any time. However, we might need to readjust the number. If it
 makes you feel better, please read the number above as a very high
 number.

I think it would be better to concentrate that high value for essential
or important packages and to judge upon the rest on a rational sense. That
sounds quite fuzzy, but makes more sense IMHO than an abstract high number.

  I think (and believe that many DDs will agree) that m68k, although being one
  of the slowest archs, is one of the most responsive ports within Debian and
  that having that many buildds is nothing negative at all. 
 As I said: We think the m68k port is doing well, and for this reason, we
 consider to grandfather it in. But that won't happen without a mail from
 one of the porters asking us to do it, and providing some facts why this
 is a good idea. :)

Uhm, that raises the next question: who qualifies as a porter? ;)
Questions over questions. ;)

  Sometimes it seems problematic to find a porting machine, though, because
  db.debian.org/machines.cgi is not always very uptodate. 
 And that is why we require to have a available porting machine (see
 above).

See above. Maybe machines.cgi lists a machine as available, but it still can
be unavailable, because of some strange machine related policies or the data
on machines.cgi is simply wrong/outdated. 
Well, then again there might be other resources where you can see if a
porting machine is up and running *dumdidums* ;o)

  For m68k: 
  [...]
 don't go so fast :)
 Well, it's of course the decision of the m68k porters team who of them
 will do the mail. But I think some more bits than just it's available
 would be good.

As I tried to say: there need more exact quidelines for this. Currently they
are very vague in my eyes.
Maybe setting up website with a reporting form might be a good idea, dunno,
but you should know how and what you want to know from the porters before
setting a dead line. 

-- 
Ciao...//Fon: 0381-2744150 
  Ingo   \X/ SIP: [EMAIL PROTECTED]

gpg pubkey: http://www.juergensmann.de/ij/public_key.asc


signature.asc
Description: Digital signature

Re: architecture-specific release criteria - requalification needed

[Ingo Juergensmann]
 As I tried to say: there need more exact quidelines for
 this. Currently they are very vague in my eyes.

You failed to say why the guidelines need to be more exact.  In my
view, the guidelines are good enough.  This is probably colored by the
fact that I trust the good judgement of the release team, and the good
will of both the release team and the porters to make sure any unclear
issues are resolved together.

I'm starting to suspect you do not trust the release team nor the
porters to make good judgement and be able to work together to figure
this out based on the given guidelines.  Is this so?

If so, it might be an idea to work on your lack of trust, instead of
spending the time trying to formulate the guidelines in a waterproof
way, as no guidelines will ever be able to cover all possible corner
cases if the lack of trust between the users of the guidelines are
present.


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

Re: architecture-specific release criteria - requalification needed

On Wed, Sep 21, 2005 at 04:28:07PM +0200, Steinar H. Gunderson wrote:
 On Wed, Sep 21, 2005 at 04:22:27PM +0200, Ingo Juergensmann wrote:
  That's not only must have 50 users but more a must have 50 users that do
  stuff on those machines. 
  See, that's the problem, when you don't define those rules exactly: what
  qualifies for a user - how often needs the user on the machine, how much
  time must he waste there, and so on and so on?
 Come on -- seriously, if a port has a problem demonstrating 50 users in a
 form that is acceptable to the release team, it has a problem anyhow. Heck,
 almost every port I can think of (perhaps except s390) should be able to
 easily gather 50 people on IRC from a machine running that architecture,
 announcing ???hey, I'm a user!??? :-) I do not seriously think this will be a
 blocked for any realistic architecture.

No, seriously, I don't know how to achieve this for m68k yet. 
I think many m68k users out there are running there m68ks as it is, without
contact to any list related to debian. They might upgrade from time to time
their boxes, but how will you reach them, when you don't know how to contact
them? And not everyone will be hooked up to IRC anyway. 
I once made a poll on debian-68k about the usage of the machines there. IIRC
there were around 30 votes, but I don't believe that everyone answered in
that poll who's using a m68k machine. 
The problem still exists: how will you reach those users and get them to
give a live sign? 
What about such ports like m32r? Some embedded devices might run that port,
but the user doesn't even know about which arch he's using nor that he's
using Debian and certainly not that he is intended to give a hey, i'm using
that port message to Debian...  

-- 
Ciao...//Fon: 0381-2744150 
  Ingo   \X/ SIP: [EMAIL PROTECTED]

gpg pubkey: http://www.juergensmann.de/ij/public_key.asc


signature.asc
Description: Digital signature

Re: architecture-specific release criteria - requalification needed

* Ingo Juergensmann ([EMAIL PROTECTED]) [050921 16:53]:
 What about such ports like m32r? Some embedded devices might run that port,
 but the user doesn't even know about which arch he's using nor that he's
 using Debian and certainly not that he is intended to give a hey, i'm using
 that port message to Debian...  

Well, it doesn't necessarily be the user himself. But if a port is only
used on embedded devices, the question arrises if it is necessary to
include that port in testing and stable.


Cheers,
Andi


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

Re: architecture-specific release criteria - requalification needed

Petter Reinholdtsen wrote:
 [Ingo Juergensmann]
 As I tried to say: there need more exact quidelines for
 this. Currently they are very vague in my eyes.
 You failed to say why the guidelines need to be more exact.  In my
 view, the guidelines are good enough.  This is probably colored by the
 fact that I trust the good judgement of the release team, and the good
 will of both the release team and the porters to make sure any unclear
 issues are resolved together.

 I'm starting to suspect you do not trust the release team nor the
 porters to make good judgement and be able to work together to figure
 this out based on the given guidelines.  Is this so?

Nono... of course not!
It's just my personal experience that this sort of guidelines need
either to be precise or need to be judged by a common sense.
The proposal make some very exact guidelines like the 98% rule whereas
it is very unprecise in other regards. I find this quite irrating and
thus asking for clarification.
And I want to prevent misunderstandings. I want to know with what I'll
be faced in the future, especially because I think that the current
ruleset is sufficient and have other opinions in some areas (number of
buildds, eg.).
I would prefer a different approach to the release problem, which I
already have outlined in some older discussions.

Please do not expect bad things when someone asks questions.

-- 
Ciao...//
  Ingo   \X/


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

Re: modifying home directories by maintainer scripts (was: Re: Bug#329347: common-lisp-controller: checking of permissions of the output directory)

2005-09-21 Thread Henrique de Moraes Holschuh

On Wed, 21 Sep 2005, René van Bevern wrote:
 Not by packages or their scripts and not without user
 interaction. It's dangerous.

Often it IS done without interaction, with the expected screwups and massive
loss of data.  Openoffice deleted a ton of user files with their
super-braindead upgrade script [oo's, I am *NOT* talking about any
maintainer scripts of the oo packages!].

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh

Re: architecture-specific release criteria - requalification needed

2005-09-21 Thread W. Borgert

Quoting Andreas Barth [EMAIL PROTECTED]:
 * Ingo Juergensmann ([EMAIL PROTECTED]) [050921 16:53]:
  What about such ports like m32r? Some embedded devices might run that port,
  but the user doesn't even know about which arch he's using nor that he's
  using Debian and certainly not that he is intended to give a hey, i'm using
  that port message to Debian...

 Well, it doesn't necessarily be the user himself. But if a port is only
 used on embedded devices, the question arrises if it is necessary to
 include that port in testing and stable.

1. If the user theirself don't know about using Debian on the
   embedded device, I'm sure that someone knows about the fact
   and can easily provide information about it.  E.g. we all
   know about the Nokia 770 arm machines.  If we can believe
   that Nokia sold more than fifty gadgets, the goal is reached.

2. Even for embedded systems, stable releases are a good thing.
   (Easier to follow GPL rules of having sources available for
   some years.  Easier to build/install additional software, if
   one knows, which Debian release is used.  Easier to clone.)

Btw., IMHO, the new release criteria are very sensible, maybe
with the exception of the 98%-rule, which might be too strict.

Cheers, WB


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

Re: architecture-specific release criteria - requalification needed

2005-09-21 Thread Daniel Stone

On Wed, 2005-09-21 at 17:05 +0200, Ingo Juergensmann wrote:
 Petter Reinholdtsen wrote:
  I'm starting to suspect you do not trust the release team nor the
  porters to make good judgement [...]
   ^^^

 Nono... of course not!
 It's just my personal experience that this sort of guidelines need
 either to be precise or need to be judged by a common sense.
  ^^^


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

Re: architecture-specific release criteria - requalification needed

2005-09-21 Thread Kalle Kivimaa

Ingo Juergensmann [EMAIL PROTECTED] writes:
 The proposal make some very exact guidelines like the 98% rule whereas
 it is very unprecise in other regards. I find this quite irrating and
 thus asking for clarification.

Actually, the 98% rule is not in the proposal. It was given as a
possible rule of thumb when you asked for more concrete guidelines.

-- 
* Sufficiently advanced magic is indistinguishable from technology (T.P)  *
*   PGP public key available @ http://www.iki.fi/killer   *


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

Re: last change to save (adopt) some packages

2005-09-21 Thread Thomas Bushnell BSG

Nathanael Nerode [EMAIL PROTECTED] writes:

 Thomas Bushnell wrote:
This is not the correct way to orphan a package.

 True.  However, it is entirely legitimate for a maintainer to decide that a 
 package is worthless and withdraw it, which is what Andres Salomon is 
 planning to do.  In fact, it's a kindness to the QA volunteers.

Yes, but this is not true for some of the packages which Andres
mentioned.  Some of them simply lack ongoing upstream support, which
is not the same thing as worthless.


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

Bug#329420: ITP: cbrpager -- viewer for CBR and CBZ (comic book archive) files

2005-09-21 Thread Roberto Lumbreras

Package: wnpp
Severity: wishlist
Owner: Roberto Lumbreras [EMAIL PROTECTED]


* Package name: cbrpager
  Version : 0.9.14
  Upstream Author : John Coppens
* URL : http://cbrpager.sourceforge.net
* License : GPL 2
  Description : viewer for CBR and CBZ (comic book archive) files

cbrPager is a no-nonsense, simple to use, small viewer for cbr and cbz
(comic book archive) files. As it is written in C, the executable is
small and fast.  It views jpg (or jpeg), gif and png images, and you can
zoom in and out.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)


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

SELinux

2005-09-21 Thread Arvind Autar

Helllo,

I have been using debian for quite some time now, how ever I have
watched several distrobutions implentating so many great ideas, and I
have been wondering why such a robust distorbution as debian
GNU/Linux(*) hasn't done this. One of them is:

SELinux

If SELinux is also suitable for desktop users for example if we look
at the targeted policy (for fedora and RHEL) it
shows that it doesn't restrict users sessions. Short conclusion, there
is no loss  of functionality, why hasn't debian implented SELinux as
default?


(Even we could get the right support for it in 'experimental')


- Arvind

(Could you be so kind to CC me, I'm not subscribed.)

Bug#329425: RFA: psutils -- A collection of PostScript document handling utilities

2005-09-21 Thread Rob Browning


Package: wnpp

I'd like to give up maintainership of psutils.

As it stands now, there hasn't been any upstream work on it in a long
time, and my impression from the last time I spoke with the author was
that he wasn't sure when he might be able to work on it heavily again.

It also looks like fixing a number of the bugs may require someone
with more postscript expertise than I plan to acquire anytime soon.

I have also wondered a bit about the current status of the domain.  Is
psutils still needed, or are there better, more actively pursued
alternatives now?  For example, can similar functionality be provided
by convenience wrappers around ghostscript, as suggested in #159888?
I don't know, but I thought perhaps someone else might.

thanks

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


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

Re: init.d script for iptables ruleset

2005-09-21 Thread Javier Fernández-Sanguino Peña

On Wed, Sep 21, 2005 at 04:34:49AM -0700, Steve Langasek wrote:
I don't remember any such rationale ever being given; IIRC, ljlane changed
it in response to pressure from users, who may have objected for any number
of reasons. The presence of an optional startup script for iptables doesn't

That's not what happened IMHO. ljlane removed them because he didn't want to
have any built-in firewall functionality in iptables. He wanted the package
to provide just the software itself. You might want to consider checking
out the maintainer response to #212692.

preclude having per-interface rules, anyway; and one may have a need for
both per-interface rules *and* static rules that should always be loaded...

IIRC the startup scripts were removed because the maintainer believed them to
be a kludge and actively encouraged users to use firewall packages
instead of the built-in functionality initially added in the iptables package.
Notice that iptables' current README.Debian file has changed since I filed
bug #307934. Now the maintainer does not mention firewall packages at all
there.

Anyway, this is still in the pre-proposal stage and needs plenty more work,
but since the topic has come up: http://wiki.debian.org/FirewallByDefault.
Feel free to add comments. :)

How about pointing to the Adding firewall capabilities section of
the Securing Manual? Available at
http://www.debian.org/doc/manuals/securing-debian-howto/ch-sec-services.en.html#s-firewall-setup

Also fixing #324593 might be relevant here as some network security features
are configered at the kernel level. I tried to describe this in the
Securing network access section of the Securing Manual:
http://www.debian.org/doc/manuals/securing-debian-howto/ch4.en.html#s-network-secure

Regards

Javier

signature.asc
Description: Digital signature

Re: SELinux

2005-09-21 Thread Henrique de Moraes Holschuh

On Wed, 21 Sep 2005, Arvind Autar wrote:
 is no loss  of functionality, why hasn't debian implented SELinux as
 default?

It is not that simple.  We are doing it slowly.

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


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

Re: SELinux

2005-09-21 Thread Mike McCarty


Arvind Autar wrote:

Helllo,

I have been using debian for quite some time now, how ever I have
watched several distrobutions implentating so many great ideas, and I
have been wondering why such a robust distorbution as debian
GNU/Linux(*) hasn't done this. One of them is:

SELinux

If SELinux is also suitable for desktop users for example if we look
at the targeted policy (for fedora and RHEL) it
shows that it doesn't restrict users sessions. Short conclusion, there
is no loss  of functionality, why hasn't debian implented SELinux as
default?


Over in the Fedora lists, quite a number of the defects are related
to SELinux. I've noticed that enabling SELinux took away quite a bit
of functionality, not by design, but by defect.

If it gets added to Debian, I suggest that it be shipped disabled.

Frankly, unless one is running an Apache server or the like, I see
no usefulness in it. And even if one runs a server like Apache,
who is to say that SELinux doesn't add as many exploitable defects
as holes it plugs, if not more?

Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!


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

Re: Bug#329425: RFA: psutils -- A collection of PostScript document handling utilities

2005-09-21 Thread Henning Makholm

Scripsit Rob Browning [EMAIL PROTECTED]

 I have also wondered a bit about the current status of the domain.  Is
 psutils still needed, or are there better, more actively pursued
 alternatives now?  For example, can similar functionality be provided
 by convenience wrappers around ghostscript, as suggested in #159888?

As far as I'm aware, psutils are the default tools for doing black-box
manipulation of postscript files at the Document Structuring
Conventions level. For things that logically belong at that level it
would be an ugly kludge to have to simulate them by ghostscript
wrappers.

(For example, some postscript files explode in size when they are
passed through ghostscripts pswrite backend - which is more or less by
design. Others become smaller, but in any case this ought to be kept
orthogonal from simple page rearrangements and such).

In my experience, tools like psnup, psselect, pstops, psbook, psresize
are things that people expect to just exist on any unix-like
system. (In fact I thought psutils was priority Standard until I just
now checked). It would be wrong not to have them in Debian.

The general utility value of fix*ps is more dubious; and I don't have
a quick opinion about psmerge, epsffit, getafm, extractres, and
includeres. I have no idea what showchar does. If the package had not
been so small already, it might be worth considering whether to split
some of the more obscure filters into a separate package.

I'm be willing to throw some effort at keeping the common psutils
tools in Debian (and keeping them well-maintained), preferably as part
of a team [thus not retitling to ITA just yet].

-- 
Henning Makholm  Den nyttige hjemmedatamat er og forbliver en myte.
Generelt kan der ikke peges på databehandlingsopgaver af
  en sådan størrelsesorden og af en karaktér, som berettiger
  forestillingerne om den nye hjemme- og husholdningsteknologi.

Re: Bug#329425: RFA: psutils -- A collection of PostScript document handling utilities

2005-09-21 Thread Steinar H. Gunderson

On Wed, Sep 21, 2005 at 10:07:12PM +0200, Henning Makholm wrote:
 (For example, some postscript files explode in size when they are
 passed through ghostscripts pswrite backend - which is more or less by
 design. Others become smaller, but in any case this ought to be kept
 orthogonal from simple page rearrangements and such).

pswrite is really crappy, but it's being worked on -- it basically rasterizes
about everything. Try current CVS of AFPL Ghostscript -- it has a “pswrite2”
driver, which is pased on pdfwrite and is supposed to be a lot more
intelligent.

/* Steinar */
-- 
Homepage: http://www.sesse.net/


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

Bug#329429: ITP: libavg -- avg Ain't Vector Graphics

2005-09-21 Thread Torsten Werner

Package: wnpp
Severity: wishlist
Owner: Torsten Werner [EMAIL PROTECTED]

* Package name: libavg
  Version : 0.2.0
  Upstream Author : Ulrich von Zadow [EMAIL PROTECTED]
* URL : http://www.libavg.de/
* License : LGPL
  Description : libavg Ain't Vector Graphics

 libavg plays back multimedia presentations in a format similar to svg that
 contain bitmap, video and/or text data.  The avg file format is loosely based
 on svg (Scalable Vector Graphics - http://www.w3.org/Graphics/SVG/), but with
 a focus on pixel- rather than vector-oriented graphics. Hence the name.



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

Link Exchange Request

2005-09-21 Thread Bellagio Directory

Dear fellow Webmaster,

I'm the webmaster of a Bellagio resource at
http://www.bellagiodir.com . 

I've collected quality links to other resources on the Internet
on my links page. 

I feel that your site would be a nice fit in my collection of
quality links.

I've already placed a link to your web site along with a
description at http://www.bellagiodir.com/gericombellagio . 

I'd appreciate if you'd place a link back to my site using the
following link and description:

Title: Bellagio Directory
Desc: A one stop resource for all your Bellagio needs.
URL: http://www.bellagiodir.com

If you'd like the description of your site changed at all or if you
have any other cross-promotion suggestions just let me know.

Best regards,

Sarah Williams

Bellagio Directory
[EMAIL PROTECTED]//

Re: Bug#329425: RFA: psutils -- A collection of PostScript document handling utilities

2005-09-21 Thread Jay Berkenbilt


I use these and would be happy to adopt the package.

-- 
Jay Berkenbilt [EMAIL PROTECTED]


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

Re: Bug#329425: RFA: psutils -- A collection of PostScript document handling utilities

2005-09-21 Thread Henning Makholm

Scripsit Steinar H. Gunderson [EMAIL PROTECTED]
 On Wed, Sep 21, 2005 at 10:07:12PM +0200, Henning Makholm wrote:

 (For example, some postscript files explode in size when they are
 passed through ghostscripts pswrite backend - which is more or less by
 design. Others become smaller, but in any case this ought to be kept
 orthogonal from simple page rearrangements and such).

 pswrite is really crappy, but it's being worked on -- it basically rasterizes
 about everything. Try current CVS of AFPL Ghostscript -- it has a “pswrite2”
 driver, which is pased on pdfwrite and is supposed to be a lot more
 intelligent.

That's good, but size increases will still be a risk (depending, of
course, on how intelligent and specialized the original postscript
producer was).  It does not change the principle that I want to
flatten my page descriptions to sequences of basic drawing operations
should be as orthogonal to I want to change the order of pages as we
can make it.

The point in bug #159888 about psmerge being a horribly brittle kludge
and ought to be superseded by a ghostscript wrapper is well made, but
that does not mean that the same point applies to, say, psselect or
psnup.

-- 
Henning Makholm  En tapper tinsoldat. En dame i
 spagat. Du er en lykkelig mand ...

Re: SELinux

2005-09-21 Thread Ron Johnson

On Wed, 2005-09-21 at 16:49 -0300, Henrique de Moraes Holschuh wrote:
 On Wed, 21 Sep 2005, Arvind Autar wrote:
  is no loss  of functionality, why hasn't debian implented SELinux as
  default?
 
 It is not that simple.  We are doing it slowly.

To flesh that out some:
Fine-grain security is a *pain* in the arse.  It's not 
easy to do right, and it necessitates vigilance, since adding new
apps very well might mean new or changed MAC rules.

For systems on insecure or restricted/classified networks, it's
wonderful.  For 98% of us, it's too much complexity for not enough
benefit over:
carefully chosen apps
turned-off unused daemons
a good h/w firewall
strong iptables rules.

-- 
-
Ron Johnson, Jr.
Temporarily not of Jefferson, LA USA
PGP Key ID 8834C06B I prefer encrypted mail.

Everybody today seems to be in such a terrible rush, anxious for
greater developments and greater riches and so on, so that
children have very little time for their parents. Parents have
very little time for each other, and in the home begins the
disruption of peace of the world.
Mother Teresa



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

ITP: ree -- Extract ROM extensions

2005-09-21 Thread Gürkan Sengün

Package: wnpp
Severity: wishlist

* Package name: ree
   Version : 1.3
   Upstream Authors: Gürkan Sengün [EMAIL PROTECTED]
* URL : http://www.linuks.mine.nu/ree/
* License : GNU GPL
   Description : Extract ROM extensions
 ROM extension extractor (ree) is a tool which extracts ROM extensions
 from the hardware of a PC computer. It can also extract font data from
 video card ROMs. It includes a shell utility and a C program which are
 functionally identical.
 .
 Homepage: http://www.linuks.mine.nu/ree/

This is useful to find out if your computers network card(s) can netboot or not.
There's also a little tool to dump bitmap fonts out of the video roms (vga).

Re: SELinux

2005-09-21 Thread Bernd Eckenfels

In article [EMAIL PROTECTED] you wrote:
 For systems on insecure or restricted/classified networks, it's
 wonderful.  For 98% of us, it's too much complexity for not enough
 benefit over:
carefully chosen apps
turned-off unused daemons
a good h/w firewall
strong iptables rules.

Biba Low-Watermark is here pretty interesting, since it requires a bit less
setup. Linux supports that with Lomac. 

Looks like IBM is researching on some SELinux based hybrid models which they
call SLIM (with TPM hardware support):
http://www.acsac.org/2004/workshop/David-Safford.pdf

However looks like lomac is kind of postponed, since nobody is funding LSM
work. However it is part of FreeBSD current.
http://opensource.sparta.com/lomac/

Gruss
Bernd


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

Bug#329462: general: standard value $LANG=[EMAIL PROTECTED] - very tiny GTK1 font

2005-09-21 Thread Annett Fritz

Package: general
Severity: grave
Tags: l10n
Justification: renders package unusable

The standard value $LANG=[EMAIL PROTECTED] breaks fontsize for some gtk1
programs like gxedit or tipptrainer. With $LANG=de_DE they show a
readable font. 
A normal user doesn't know that when he chooses the locale
dpkg-reconfigure locales during installation.


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)


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

Re: [cl-debian] modifying home directories by maintainer scripts (was: Re: Bug#329347: common-lisp-controller: checking of permissions of the output directory)

2005-09-21 Thread Peter Van Eynde

On Wednesday 21 September 2005 15:49, René van Bevern wrote:

  A lot of packages install stuff in the user directory.

 I doubt that any package does this.

1/[EMAIL PROTECTED]:~ :( $ grep '^/home/' /var/lib/dpkg/info/*.list
1/[EMAIL PROTECTED]:~ :( $

None on my system.

 Not by packages or their scripts and not without user
 interaction. It's dangerous.


After thinking it over I do agree with this. I will resist any change to move 
the cache directory over to a location beneath /home unless there is a change 
in debian policy on this.

I am willing to provide hooks to permit a user to move the fasls to a location 
of choice.

I fear I did not have time yet to investigate cl-launch but I'll try to make 
some time for it.

Groetjes, Peter

-- 
signature -at- pvaneynd.mailworks.org 
http://www.livejournal.com/users/pvaneynd/
God, root, what is difference? Pitr | God is more forgiving. Dave Aronson| 


pgpSZS30mOjT4.pgp
Description: PGP signature

Accepted empire 1.7-2 (source i386)

2005-09-21 Thread Peter Palfrader

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 03:29:45 +0200
Source: empire
Binary: empire
Architecture: source i386
Version: 1.7-2
Distribution: unstable
Urgency: low
Maintainer: Peter Palfrader [EMAIL PROTECTED]
Changed-By: Peter Palfrader [EMAIL PROTECTED]
Description: 
 empire - the war game of the century
Changes: 
 empire (1.7-2) unstable; urgency=low
 .
   * Update upstream url in debian/copyright.
   * Update FSF address in debian/copyright.
   * Increase standards-version to 3.6.2 from 3.6.1.
   * Change DH_COMPAT to 4, from 2.  This or at least the rebuild with a
 recent debhelper will cause the menu fil to be installed in usr/share
 now.  Of course also increase version in Build-Depends.
   * Some whitespace change in the manpage, so that a line does not start with
 'empmovie.
Files: 
 bf3d2313d6258198f0d22938157a92bf 564 games extra empire_1.7-2.dsc
 9464d9a32376206c81b0d3f0f12c7aeb 6410 games extra empire_1.7-2.diff.gz
 424ca38e159539a8cee4507dec26c2bf 61340 games extra empire_1.7-2_i386.deb

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

iD8DBQFDMQVCz/ccs6+kS90RAu5VAJ9xwQWWlOhZRZCa6wnhdbYiU24mzQCdFLZK
y/lQn6FnaVZh1cvc5Rsgr2A=
=44P6
-END PGP SIGNATURE-


Accepted:
empire_1.7-2.diff.gz
  to pool/main/e/empire/empire_1.7-2.diff.gz
empire_1.7-2.dsc
  to pool/main/e/empire/empire_1.7-2.dsc
empire_1.7-2_i386.deb
  to pool/main/e/empire/empire_1.7-2_i386.deb


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

Accepted knutclient 0.8.6-2 (source i386)

2005-09-21 Thread Arnaud Quette

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 13 Sep 2005 11:12:18 +0200
Source: knutclient
Binary: knutclient
Architecture: source i386
Version: 0.8.6-2
Distribution: unstable
Urgency: low
Maintainer: Arnaud Quette [EMAIL PROTECTED]
Changed-By: Arnaud Quette [EMAIL PROTECTED]
Description: 
 knutclient - A KDE GUI that displays UPS statistics from NUT's upsd
Closes: 327959
Changes: 
 knutclient (0.8.6-2) unstable; urgency=low
 .
   * Rebuilt against KDE 3.4 with g++-4 for the C++ ABI transition
 (closes: #327959). Build-dependencies and shlibs updated accordingly.
   * debian/control: change Section to kde, and rework a bit the Homepage URL
Files: 
 ddf21bcd51cb3a7dc8b9937ef0f2106b 603 kde optional knutclient_0.8.6-2.dsc
 9565d2bb549a82760e8e64f99474c5fa 25845 kde optional knutclient_0.8.6-2.diff.gz
 8b109bff7a1d3ef907004b7db4fbe6d0 705754 kde optional 
knutclient_0.8.6-2_i386.deb

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

iD8DBQFDMP+M22QUyiBN3xsRAnqVAJ0Q5uN1U8VKf78vWWP74WXKG21VdACbBZVM
ClONgVwGTHU6CktjpKqbk3o=
=PCbm
-END PGP SIGNATURE-


Accepted:
knutclient_0.8.6-2.diff.gz
  to pool/main/k/knutclient/knutclient_0.8.6-2.diff.gz
knutclient_0.8.6-2.dsc
  to pool/main/k/knutclient/knutclient_0.8.6-2.dsc
knutclient_0.8.6-2_i386.deb
  to pool/main/k/knutclient/knutclient_0.8.6-2_i386.deb


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

Accepted ipw2200 1.0.6-6 (source all)

2005-09-21 Thread Mike Hommey

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 09:30:36 +0200
Source: ipw2200
Binary: ipw2200-source
Architecture: source all
Version: 1.0.6-6
Distribution: unstable
Urgency: low
Maintainer: Mike Hommey [EMAIL PROTECTED]
Changed-By: Mike Hommey [EMAIL PROTECTED]
Description: 
 ipw2200-source - Source for the ipw2200 driver
Changes: 
 ipw2200 (1.0.6-6) unstable; urgency=low
 .
   * Makefile: use $(CC) instead of gcc.
Files: 
 6677b998b4c7339bbc40a350c35678a3 569 contrib/net optional ipw2200_1.0.6-6.dsc
 7092770fff78908606084b47e39f9ee0 11638 contrib/net optional 
ipw2200_1.0.6-6.diff.gz
 5cd0737dbf5a55e7a6bb69ba864ad195 116222 contrib/net optional 
ipw2200-source_1.0.6-6_all.deb

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

iD8DBQFDMQxe3kvaLFT9KlgRAkBCAKCK4SzBxefP8QS4drxFJQRTUbComwCeMjrf
PeWr3hqJc8kXoR5ze6vAfEM=
=wtSG
-END PGP SIGNATURE-


Accepted:
ipw2200-source_1.0.6-6_all.deb
  to pool/contrib/i/ipw2200/ipw2200-source_1.0.6-6_all.deb
ipw2200_1.0.6-6.diff.gz
  to pool/contrib/i/ipw2200/ipw2200_1.0.6-6.diff.gz
ipw2200_1.0.6-6.dsc
  to pool/contrib/i/ipw2200/ipw2200_1.0.6-6.dsc


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

Accepted mozilla-locale-de-at 1.7.11-1 (source all)

2005-09-21 Thread Johannes Rohr

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 18 Sep 2005 09:10:48 +0200
Source: mozilla-locale-de-at
Binary: mozilla-locale-de-at
Architecture: source all
Version: 1.7.11-1
Distribution: unstable
Urgency: low
Maintainer: Florian M. Weps [EMAIL PROTECTED]
Changed-By: Johannes Rohr [EMAIL PROTECTED]
Description: 
 mozilla-locale-de-at - Mozilla German Language/Region Package
Changes: 
 mozilla-locale-de-at (1.7.11-1) unstable; urgency=low
 .
   * New upstream release
Files: 
 45de2f155816a1e28ebc2fc3fbbd8590 681 web optional 
mozilla-locale-de-at_1.7.11-1.dsc
 2278db68a1c399bd29d161d476cc6362 1741756 web optional 
mozilla-locale-de-at_1.7.11.orig.tar.gz
 89a2fbf5148e8969cafd9b3a2d0df107 29835 web optional 
mozilla-locale-de-at_1.7.11-1.diff.gz
 cebb6837a927a0b604253819b9a1f6b9 724944 web optional 
mozilla-locale-de-at_1.7.11-1_all.deb

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

iD8DBQFDMQ+JQxo87aLX0pIRAhcEAKDbD2RaV0v8s3vGc5EWwWOj06uotQCeMNUv
sDXl6SHbPg5RJLMx+Zb4DuU=
=XSD3
-END PGP SIGNATURE-


Accepted:
mozilla-locale-de-at_1.7.11-1.diff.gz
  to pool/main/m/mozilla-locale-de-at/mozilla-locale-de-at_1.7.11-1.diff.gz
mozilla-locale-de-at_1.7.11-1.dsc
  to pool/main/m/mozilla-locale-de-at/mozilla-locale-de-at_1.7.11-1.dsc
mozilla-locale-de-at_1.7.11-1_all.deb
  to pool/main/m/mozilla-locale-de-at/mozilla-locale-de-at_1.7.11-1_all.deb
mozilla-locale-de-at_1.7.11.orig.tar.gz
  to pool/main/m/mozilla-locale-de-at/mozilla-locale-de-at_1.7.11.orig.tar.gz


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

Accepted rrdtool 1.2.11-0.4 (source all i386)

2005-09-21 Thread Matthias Klose

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 18 Sep 2005 06:04:13 +
Source: rrdtool
Binary: librrds-perl python2.3-rrd librrdp-perl python-rrd librrd2-dev librrd2 
rrdtool-tcl python2.4-rrd rrdtool
Architecture: source all i386
Version: 1.2.11-0.4
Distribution: unstable
Urgency: low
Maintainer: Matt Zimmerman [EMAIL PROTECTED]
Changed-By: Matthias Klose [EMAIL PROTECTED]
Description: 
 librrd2- Time-series data storage and display system (runtime)
 librrd2-dev - Time-series data storage and display system (development)
 librrdp-perl - Time-series data storage and display system (perl-piped)
 librrds-perl - Time-series data storage and display system (perl-shared)
 python-rrd - Python bindings for RRD
 python2.3-rrd - Python bindings for RRD
 python2.4-rrd - Python bindings for RRD
 rrdtool- Time-series data storage and display system (programs)
 rrdtool-tcl - Time-series data storage and display system (tcl)
Closes: 240369 323771
Changes: 
 rrdtool (1.2.11-0.4) unstable; urgency=low
 .
   * NMU.
   * Tighten the dependency of the binary packages on librrd2 to assert the use
 of a recent version depending on ttf-dejavu.
   * Fix 'rrdtool restore', replace the workaround from 1.2.11-0.3 with a patch
 from the upstream repository.  Closes: #323771.
   * Set the priority of the language bindings, which only depend on librrd2,
 to optional, as aleady done for python-rrd (rrdtool-tcl, librrds-perl).
 Closes: #240369.
Files: 
 c3b53b0a6fa35a349162b65254487f9b 873 utils optional rrdtool_1.2.11-0.4.dsc
 60a46cd740ff0ccc0d75e445ed933b41 11269 utils optional 
rrdtool_1.2.11-0.4.diff.gz
 4edcab693bb339be5fe42b65a3a98e72 23252 perl optional 
librrdp-perl_1.2.11-0.4_all.deb
 bf402c37e41d40e9750d99fccb3103e3 17680 python optional 
python-rrd_1.2.11-0.4_all.deb
 0435ca3168fe826027896aa148b5ecfb 478340 utils optional 
rrdtool_1.2.11-0.4_i386.deb
 cea8759092b9e4fe5833946a5400579e 235022 libs optional 
librrd2_1.2.11-0.4_i386.deb
 acbff8b83566f255ea28264e4b8d9a7f 288332 libdevel optional 
librrd2-dev_1.2.11-0.4_i386.deb
 1b2a7a0b605bf0f26b5e7be020ef33f0 35842 perl optional 
librrds-perl_1.2.11-0.4_i386.deb
 aeb177905f837d24c13503719a23206c 23180 utils optional 
rrdtool-tcl_1.2.11-0.4_i386.deb
 761dc759e2788bb8ebce38b26c1b4bc8 25206 python optional 
python2.3-rrd_1.2.11-0.4_i386.deb
 76e3fcf8192a401d8e8425aaefe8 25206 python optional 
python2.4-rrd_1.2.11-0.4_i386.deb

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

iD8DBQFDMRCsStlRaw+TLJwRAg4jAJ43bj1XNGR/VH0grezZx5XfeLBMKgCglqwx
egjHvJfr+VjZK4rX02TbriI=
=jY7F
-END PGP SIGNATURE-


Accepted:
librrd2-dev_1.2.11-0.4_i386.deb
  to pool/main/r/rrdtool/librrd2-dev_1.2.11-0.4_i386.deb
librrd2_1.2.11-0.4_i386.deb
  to pool/main/r/rrdtool/librrd2_1.2.11-0.4_i386.deb
librrdp-perl_1.2.11-0.4_all.deb
  to pool/main/r/rrdtool/librrdp-perl_1.2.11-0.4_all.deb
librrds-perl_1.2.11-0.4_i386.deb
  to pool/main/r/rrdtool/librrds-perl_1.2.11-0.4_i386.deb
python-rrd_1.2.11-0.4_all.deb
  to pool/main/r/rrdtool/python-rrd_1.2.11-0.4_all.deb
python2.3-rrd_1.2.11-0.4_i386.deb
  to pool/main/r/rrdtool/python2.3-rrd_1.2.11-0.4_i386.deb
python2.4-rrd_1.2.11-0.4_i386.deb
  to pool/main/r/rrdtool/python2.4-rrd_1.2.11-0.4_i386.deb
rrdtool-tcl_1.2.11-0.4_i386.deb
  to pool/main/r/rrdtool/rrdtool-tcl_1.2.11-0.4_i386.deb
rrdtool_1.2.11-0.4.diff.gz
  to pool/main/r/rrdtool/rrdtool_1.2.11-0.4.diff.gz
rrdtool_1.2.11-0.4.dsc
  to pool/main/r/rrdtool/rrdtool_1.2.11-0.4.dsc
rrdtool_1.2.11-0.4_i386.deb
  to pool/main/r/rrdtool/rrdtool_1.2.11-0.4_i386.deb


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

Accepted xscreensaver 4.21-6 (source i386 sparc)

2005-09-21 Thread Ralf Hildebrandt

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 19 Sep 2005 11:20:43 +0200
Source: xscreensaver
Binary: xscreensaver xscreensaver-gl
Architecture: source i386 sparc
Version: 4.21-6
Distribution: unstable
Urgency: low
Maintainer: Ralf Hildebrandt [EMAIL PROTECTED]
Changed-By: Ralf Hildebrandt [EMAIL PROTECTED]
Description: 
 xscreensaver - Automatic screensaver for X
 xscreensaver-gl - GL(Mesa) screen hacks for xscreensaver
Closes: 118089 118881 127276 129124 137073 145814 302777 318512 320446 323841 
326534
Changes: 
 xscreensaver (4.21-6) unstable; urgency=low
 .
   * patch against stop_the_insanity() (closes: #323841)
   * patch typo in the whirlygig.6x man page (closes: #326534)
   * patch against run_hack() in driver/demo-Gtk.c (closes: #302777)
   * fix dependencies (closes: #318512)
   * closing old stuff that's already fixed (closes: #118089, #118881, #137073, 
#145814, #129124)
   * closing old stuff that's WONTFIX (closes: #127276)
   * relax dependency on netpbm (closes: #320446)
   * fix build dependencies for gl and glu
   * fix lintian bugs about debian-control-with-duplicate-fields conflicts: 12, 
15
   * fix lintian bug (man pages for flow and intermomentary)
   * fix lintian bug syntax-error-in-debian-changelog line 313 unrecognised 
line
Files: 
 6e87e6f8e440bc4e8228328f69b0a18d 872 x11 optional xscreensaver_4.21-6.dsc
 b729e140946d08561e6e14779346174b 118203 x11 optional 
xscreensaver_4.21-6.diff.gz
 71683a5fbfa1af87ddc5eaf626919341 3747514 x11 optional 
xscreensaver_4.21-6_i386.deb
 02b60e9b3f715dd39ffe7620b849cd02 2831368 x11 optional 
xscreensaver-gl_4.21-6_i386.deb
 348c6a52f5f8b33ae7850bc734c50bc3 3971404 x11 optional 
xscreensaver_4.21-6_sparc.deb
 b494a5f29b57fc8ea6c87d87e958cb2c 2935430 x11 optional 
xscreensaver-gl_4.21-6_sparc.deb

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

iD8DBQFDMQxBgY5NIXPNpFURAmGaAKC0XlU8fc7FMIhxJxXlUJRMB3erxgCgmK0t
Etz7kRp8ngWWYP4cKz3AzxM=
=cTql
-END PGP SIGNATURE-


Accepted:
xscreensaver-gl_4.21-6_i386.deb
  to pool/main/x/xscreensaver/xscreensaver-gl_4.21-6_i386.deb
xscreensaver-gl_4.21-6_sparc.deb
  to pool/main/x/xscreensaver/xscreensaver-gl_4.21-6_sparc.deb
xscreensaver_4.21-6.diff.gz
  to pool/main/x/xscreensaver/xscreensaver_4.21-6.diff.gz
xscreensaver_4.21-6.dsc
  to pool/main/x/xscreensaver/xscreensaver_4.21-6.dsc
xscreensaver_4.21-6_i386.deb
  to pool/main/x/xscreensaver/xscreensaver_4.21-6_i386.deb
xscreensaver_4.21-6_sparc.deb
  to pool/main/x/xscreensaver/xscreensaver_4.21-6_sparc.deb


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

Accepted ksynaptics 0.2.1-1 (source i386)

2005-09-21 Thread Arnaud Quette

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 16 Sep 2005 20:56:22 +0200
Source: ksynaptics
Binary: ksynaptics
Architecture: source i386
Version: 0.2.1-1
Distribution: unstable
Urgency: low
Maintainer: Arnaud Quette [EMAIL PROTECTED]
Changed-By: Arnaud Quette [EMAIL PROTECTED]
Description: 
 ksynaptics - A KDE application to configure Synaptics TouchPad
Closes: 301274 327994
Changes: 
 ksynaptics (0.2.1-1) unstable; urgency=low
 .
   * New upstream release
 - fixes FTBFS (amd64/gcc-4.0): undefined reference to
 `TouchPad::coastingSpeedThreshold' (Closes: #301274)
   * Rebuild for new C++ ABI (Closes: #327994)
   * debian/control: upgrade Debian Policy to 3.6.2
   * debian/lintian-override: add this file to override
 package-name-doesnt-match-sonames libkdeinit-syndock warning and
 ksynaptics binary: no-shlibs-control-file usr/lib/libkdeinit_syndock.so
 error. The 2nd one is not 100 % sure!
   * debian/rules:
 - install the above override file
 - install the upstream ksynaptics.1x manpage
 - add --disable-rpath configure option
 - activate dh_makeshlibs
 - make a bit of cleaning
   * debian/dirs: added for lintian-override path
   * debian/TODO.Debian: added to track the above shlib issue
Files: 
 b6eeb2ebcb13faf68465e1224dee0543 610 kde optional ksynaptics_0.2.1-1.dsc
 f1ef99d0bea5aa4ffa270b2a98f7d8de 685272 kde optional 
ksynaptics_0.2.1.orig.tar.gz
 cb3e95dc81db74ad790bcc60dd4a38f9 25379 kde optional ksynaptics_0.2.1-1.diff.gz
 94ddb59341ceecb2b8e11ed7bc09a7d8 82118 kde optional ksynaptics_0.2.1-1_i386.deb

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

iD8DBQFDMRcz22QUyiBN3xsRAt0WAJ9KahmaArMJCBSsQDrlPpfzqpBTdQCfcdpZ
8TMq1l0RkYYxd+oYGy2v/94=
=mZ+5
-END PGP SIGNATURE-


Accepted:
ksynaptics_0.2.1-1.diff.gz
  to pool/main/k/ksynaptics/ksynaptics_0.2.1-1.diff.gz
ksynaptics_0.2.1-1.dsc
  to pool/main/k/ksynaptics/ksynaptics_0.2.1-1.dsc
ksynaptics_0.2.1-1_i386.deb
  to pool/main/k/ksynaptics/ksynaptics_0.2.1-1_i386.deb
ksynaptics_0.2.1.orig.tar.gz
  to pool/main/k/ksynaptics/ksynaptics_0.2.1.orig.tar.gz


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

Accepted evolution-data-server 1.4.0-2 (source i386)

2005-09-21 Thread Takuo KITAME

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 16:55:06 +0900
Source: evolution-data-server
Binary: libebook1.2-5 libcamel1.2-0 libedataserver1.2-dev libedata-cal1.2-dev 
libecal1.2-dev libedata-cal1.2-1 libcamel1.2-dev libegroupwise1.2-8 
evolution-data-server libedataserverui1.2-6 libedata-book1.2-2 
libedataserver1.2-4 libedata-book1.2-dev libedataserverui1.2-dev 
evolution-data-server-dev libegroupwise1.2-dev libebook1.2-dev libecal1.2-3
Architecture: source i386
Version: 1.4.0-2
Distribution: experimental
Urgency: low
Maintainer: Takuo KITAME [EMAIL PROTECTED]
Changed-By: Takuo KITAME [EMAIL PROTECTED]
Description: 
 evolution-data-server - evolution database backend server
 evolution-data-server-dev - Development files for evolution-data-server (meta 
package)
 libcamel1.2-0 - The Evolution MIME message handling library
 libcamel1.2-dev - Development files for libcamel
 libebook1.2-5 - Client library for evolution address books
 libebook1.2-dev - Client library for evolution address books (development 
files)
 libecal1.2-3 - Client library for evolution calendars
 libecal1.2-dev - Client library for evolution calendars (development files)
 libedata-book1.2-2 - Backend library for evolution address books
 libedata-book1.2-dev - Backend library for evolution address books 
(development files)
 libedata-cal1.2-1 - Backend library for evolution calendars
 libedata-cal1.2-dev - Backend library for evolution calendars (development 
files)
 libedataserver1.2-4 - Utily library for evolution data servers
 libedataserver1.2-dev - Utility library for evolution data servers 
(development files)
 libedataserverui1.2-6 - GUI utily library for evolution data servers
 libedataserverui1.2-dev - GUI utility library for evolution data servers 
(development files
 libegroupwise1.2-8 - Client library for accessing groupwise POA through SOAP 
interface
 libegroupwise1.2-dev - Development files for libegroupwise
Changes: 
 evolution-data-server (1.4.0-2) experimental; urgency=low
 .
   * Build against libdb4.2
Files: 
 9098304a7cea3c7a4881140ab8e8d638 1148 gnome optional 
evolution-data-server_1.4.0-2.dsc
 b59b85df628dc0fe78c4af52b95f51ce 30637 gnome optional 
evolution-data-server_1.4.0-2.diff.gz
 d315da84105fe18d5773a6d4e56d159a 1712912 gnome optional 
evolution-data-server_1.4.0-2_i386.deb
 992ef43c8e029fddac98d58d9750945b 35470 devel optional 
evolution-data-server-dev_1.4.0-2_i386.deb
 18560addac8b9a6531eaa58a7a8accec 89318 libs optional 
libedataserver1.2-4_1.4.0-2_i386.deb
 4f64afa14a9a82d47fb88b103e273c8f 47896 libdevel optional 
libedataserver1.2-dev_1.4.0-2_i386.deb
 910a261e3eba3f0f45b99088fe9e6a91 85934 libs optional 
libedataserverui1.2-6_1.4.0-2_i386.deb
 5a81aad6cc2691175f0ba740f9884f61 41070 libdevel optional 
libedataserverui1.2-dev_1.4.0-2_i386.deb
 42cc981b51da36e159493447ef39fade 103942 libs optional 
libebook1.2-5_1.4.0-2_i386.deb
 dc73e0c99f7019f689f91257d8121fa5 54932 libdevel optional 
libebook1.2-dev_1.4.0-2_i386.deb
 d3e7460b79c1c47efeb73ff412fc5bbe 70312 libs optional 
libedata-book1.2-2_1.4.0-2_i386.deb
 fedcc2469beee03fe81358f4309c0b7f 49016 libdevel optional 
libedata-book1.2-dev_1.4.0-2_i386.deb
 65ff607820fd9266c23cc78c9b14a1d4 251128 libs optional 
libecal1.2-3_1.4.0-2_i386.deb
 3eebfdd226eacfec9f30e93436a13d12 98420 libdevel optional 
libecal1.2-dev_1.4.0-2_i386.deb
 c912504ae0356bb4c24797df22aabffc 79868 libs optional 
libedata-cal1.2-1_1.4.0-2_i386.deb
 8cc508a261a36b6d7c4dcf3efb4f364b 53246 libdevel optional 
libedata-cal1.2-dev_1.4.0-2_i386.deb
 314e5838c03f9974941cf07317e1bec2 83654 libs optional 
libegroupwise1.2-8_1.4.0-2_i386.deb
 57d88e8682a804ec2936be830a6ff10f 42030 libdevel optional 
libegroupwise1.2-dev_1.4.0-2_i386.deb
 1c6df5621e36cf2e6145bb7184df5538 523364 libdevel optional 
libcamel1.2-0_1.4.0-2_i386.deb
 778062372d6b6ed190083a7efa10561a 97410 libdevel optional 
libcamel1.2-dev_1.4.0-2_i386.deb

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

iD8DBQFDMRfKU+WZW1FVMwoRAhdFAKCL7PsjA1B3nawiulmZS9IO5uUa3ACdGbDo
TCSFjQUmvHkIbgNczxpxG50=
=1ntA
-END PGP SIGNATURE-


Accepted:
evolution-data-server-dev_1.4.0-2_i386.deb
  to 
pool/main/e/evolution-data-server/evolution-data-server-dev_1.4.0-2_i386.deb
evolution-data-server_1.4.0-2.diff.gz
  to pool/main/e/evolution-data-server/evolution-data-server_1.4.0-2.diff.gz
evolution-data-server_1.4.0-2.dsc
  to pool/main/e/evolution-data-server/evolution-data-server_1.4.0-2.dsc
evolution-data-server_1.4.0-2_i386.deb
  to pool/main/e/evolution-data-server/evolution-data-server_1.4.0-2_i386.deb
libcamel1.2-0_1.4.0-2_i386.deb
  to pool/main/e/evolution-data-server/libcamel1.2-0_1.4.0-2_i386.deb
libcamel1.2-dev_1.4.0-2_i386.deb
  to pool/main/e/evolution-data-server/libcamel1.2-dev_1.4.0-2_i386.deb
libebook1.2-5_1.4.0-2_i386.deb
  to pool/main/e/evolution-data-server/libebook1.2-5_1.4.0-2_i386.deb
libebook1.2-dev_1.4.0-2_i386.deb
  to

Accepted tor 0.1.0.14-2 (source i386)

2005-09-21 Thread Peter Palfrader

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 10:23:25 +0200
Source: tor
Binary: tor-dbg tor
Architecture: source i386
Version: 0.1.0.14-2
Distribution: unstable
Urgency: low
Maintainer: Peter Palfrader [EMAIL PROTECTED]
Changed-By: Peter Palfrader [EMAIL PROTECTED]
Description: 
 tor- anonymizing overlay network for TCP
 tor-dbg- debugging symbols for Tor
Changes: 
 tor (0.1.0.14-2) unstable; urgency=low
 .
   * Ship debugging information in a separate package now, instead
 of simply not stripping tor.  This is still useful while tor is
 young.  Ideally it would go away some time.
   * Add LSB comments to init script as suggested by Petter Reinholdtsen
 on the debian-devel list:
 - http://lists.debian.org/debian-devel/2005/08/msg01172.html
 - http://wiki.debian.net/?LSBInitScripts
   * Work around broken chroots that do not resolve localhost or resolve
 it to the wrong IP.  We now catch such cases in debian/rules, shout
 at the buildd maintainer, and ignore the result of our test suite.
Files: 
 d56c229206f865afb8239f256192709c 687 comm optional tor_0.1.0.14-2.dsc
 0a012b94177891ad2a79166546b1994e 68023 comm optional tor_0.1.0.14-2.diff.gz
 206473cb0b9d414b128559b79081025d 545812 comm optional tor_0.1.0.14-2_i386.deb
 5c221ec1dada1ba920fd9d7d1fa0e1c6 309812 comm extra tor-dbg_0.1.0.14-2_i386.deb

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

iD8DBQFDMR2rz/ccs6+kS90RAizmAJ96wpqlBfvGw7kzxGgTHSUISvR+GACgnBCU
68KUPFOatWQeTAuMk5aBNnM=
=tlP3
-END PGP SIGNATURE-


Accepted:
tor-dbg_0.1.0.14-2_i386.deb
  to pool/main/t/tor/tor-dbg_0.1.0.14-2_i386.deb
tor_0.1.0.14-2.diff.gz
  to pool/main/t/tor/tor_0.1.0.14-2.diff.gz
tor_0.1.0.14-2.dsc
  to pool/main/t/tor/tor_0.1.0.14-2.dsc
tor_0.1.0.14-2_i386.deb
  to pool/main/t/tor/tor_0.1.0.14-2_i386.deb


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

Accepted readline4 4.3-17 (source i386)

2005-09-21 Thread Matthias Klose

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 07:32:05 +
Source: readline4
Binary: libreadline4-dev libreadline4 libreadline4-dbg lib64readline4 
lib64readline4-dev
Architecture: source i386
Version: 4.3-17
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose [EMAIL PROTECTED]
Changed-By: Matthias Klose [EMAIL PROTECTED]
Description: 
 libreadline4 - GNU readline and history libraries, run-time libraries
 libreadline4-dbg - GNU readline and history libraries, debugging libraries
 libreadline4-dev - GNU readline and history libraries, development files
Changes: 
 readline4 (4.3-17) unstable; urgency=medium
 .
   * Fix lib64readline4 dependency.
Files: 
 7bf2712884e19cb247010fe51b56cbd9 696 base standard readline4_4.3-17.dsc
 91bfb65ef2bf1ff437c86bcc163515b8 20886 base standard readline4_4.3-17.diff.gz
 c755519e62cab4605ffe1877cbc728e0 105684 libs standard 
libreadline4_4.3-17_i386.deb
 679e7e663ee00347733261d46313f93f 196584 libdevel optional 
libreadline4-dev_4.3-17_i386.deb
 cd272c35bdf704e1906a277334a22fd8 214224 libdevel extra 
libreadline4-dbg_4.3-17_i386.deb

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

iD8DBQFDMR6IStlRaw+TLJwRAnxuAKC22fre1QK9TlyUQSjQEKs/5ox+pQCeNGN3
nvFCra/QADRfouDjxYL6b2E=
=+7GA
-END PGP SIGNATURE-


Accepted:
libreadline4-dbg_4.3-17_i386.deb
  to pool/main/r/readline4/libreadline4-dbg_4.3-17_i386.deb
libreadline4-dev_4.3-17_i386.deb
  to pool/main/r/readline4/libreadline4-dev_4.3-17_i386.deb
libreadline4_4.3-17_i386.deb
  to pool/main/r/readline4/libreadline4_4.3-17_i386.deb
readline4_4.3-17.diff.gz
  to pool/main/r/readline4/readline4_4.3-17.diff.gz
readline4_4.3-17.dsc
  to pool/main/r/readline4/readline4_4.3-17.dsc


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

Accepted qsynaptics 0.22.0-3 (source i386)

2005-09-21 Thread Arnaud Quette

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 16 Sep 2005 20:56:22 +0200
Source: qsynaptics
Binary: qsynaptics
Architecture: source i386
Version: 0.22.0-3
Distribution: unstable
Urgency: low
Maintainer: Arnaud Quette [EMAIL PROTECTED]
Changed-By: Arnaud Quette [EMAIL PROTECTED]
Description: 
 qsynaptics - A QT application to configure Synaptic TouchPad
Closes: 327998
Changes: 
 qsynaptics (0.22.0-3) unstable; urgency=low
 .
   * debian/control: update Standards-Version to 3.6.2
   * Rebuild for new C++ ABI (Closes: #327998)
   * debian/copyright: update FSF address
Files: 
 936ce3781492714864c70cd9a8706214 648 x11 optional qsynaptics_0.22.0-3.dsc
 bf21574c8b6d3a84b42297006da562e5 3657 x11 optional qsynaptics_0.22.0-3.diff.gz
 d50e0e866aadf0cbc0425bb93500ff30 67756 x11 optional 
qsynaptics_0.22.0-3_i386.deb

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

iD8DBQFDMR/022QUyiBN3xsRAiBgAJ9iQYV52QJ0GZzhAmhozs592qpBRwCeOv4b
hPppbK1DJ4Znnzz2viJiUxk=
=1GcN
-END PGP SIGNATURE-


Accepted:
qsynaptics_0.22.0-3.diff.gz
  to pool/main/q/qsynaptics/qsynaptics_0.22.0-3.diff.gz
qsynaptics_0.22.0-3.dsc
  to pool/main/q/qsynaptics/qsynaptics_0.22.0-3.dsc
qsynaptics_0.22.0-3_i386.deb
  to pool/main/q/qsynaptics/qsynaptics_0.22.0-3_i386.deb


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

Accepted mutt-ng 0.0+20050916-1 (source i386)

2005-09-21 Thread Elimar Riesebieter

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sat, 17 Sep 2005 10:43:46 +0200
Source: mutt-ng
Binary: mutt-ng
Architecture: source i386
Version: 0.0+20050916-1
Distribution: experimental
Urgency: low
Maintainer: Elimar Riesebieter [EMAIL PROTECTED]
Changed-By: Elimar Riesebieter [EMAIL PROTECTED]
Description: 
 mutt-ng- text-based mailreader supporting MIME, GPG, PGP and threading
Closes: 328159
Changes: 
 mutt-ng (0.0+20050916-1) experimental; urgency=low
 .
   * Updated to snapshot 20050916
   * Correctly handle Maildir with and without trailing slash when printing
 sidebar entries.
   * Merged in mutt 1.5.11 by upstream.
   * Excluded muttng_dotlock from fixperms (closes: #328159)
   * Added patches/208_init.h.diff.
   * This is as of version devel-r529.
   * Upload sponsored by Norbert Tretkowski [EMAIL PROTECTED]
Files: 
 6344d592480ef23be7d063858ff24c97 806 mail optional mutt-ng_0.0+20050916-1.dsc
 33d1a3aa97ff9e39fac3b0dcc14670e4 2597288 mail optional 
mutt-ng_0.0+20050916.orig.tar.gz
 97abd15a21790f6ae15e193545828b10 108257 mail optional 
mutt-ng_0.0+20050916-1.diff.gz
 7c437231ece487651ec5ba3a336cf2b9 1680170 mail optional 
mutt-ng_0.0+20050916-1_i386.deb

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

iD8DBQFDMSrur/RnCw96jQERAg8wAJ4ns40wvAAkRopT8W32qwMLaPonzgCeNFm+
9NSeyE/XhXCVfJXIAusglIY=
=B8Np
-END PGP SIGNATURE-


Accepted:
mutt-ng_0.0+20050916-1.diff.gz
  to pool/main/m/mutt-ng/mutt-ng_0.0+20050916-1.diff.gz
mutt-ng_0.0+20050916-1.dsc
  to pool/main/m/mutt-ng/mutt-ng_0.0+20050916-1.dsc
mutt-ng_0.0+20050916-1_i386.deb
  to pool/main/m/mutt-ng/mutt-ng_0.0+20050916-1_i386.deb
mutt-ng_0.0+20050916.orig.tar.gz
  to pool/main/m/mutt-ng/mutt-ng_0.0+20050916.orig.tar.gz


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

Accepted libgef-java 0.11.1-2 (source all)

2005-09-21 Thread Arnaud Vandyck

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 11:22:34 +0200
Source: libgef-java
Binary: libgef-java
Architecture: source all
Version: 0.11.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 
pkg-java-maintainers@lists.alioth.debian.org
Changed-By: Arnaud Vandyck [EMAIL PROTECTED]
Description: 
 libgef-java - Graph Editing Framework written entirely in Java
Closes: 321853 329325
Changes: 
 libgef-java (0.11.1-2) unstable; urgency=low
 .
   * debian/control (*Depends*), debian/rules: build with kaffe, can move
 to main, thanks to Andreas Jochens for the patch (closes: #329325)
   * debian/control (Description): corrected typo, thanks to Julian Gilbey
 for the patch (closes: #321853)
Files: 
 14c6bd8048f2875bf0a35a35b18ab827 799 libs optional libgef-java_0.11.1-2.dsc
 345bd072213202777559b467d480362f 379867 libs optional 
libgef-java_0.11.1.orig.tar.gz
 fef6f5433cbc92dc5545b822d2ee430b 3267 libs optional 
libgef-java_0.11.1-2.diff.gz
 89bdbf862e5f7c73cd99b6876accb40d 594586 libs optional 
libgef-java_0.11.1-2_all.deb

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

iD8DBQFDMSfR4vzFZu62tMIRAiqHAJ4gzrU39uaWjoe/vXE5yLKlVzRNFgCgv3kS
rSSOBipxe1V6JGQHBIGe4w4=
=xoNf
-END PGP SIGNATURE-


Accepted:
libgef-java_0.11.1-2.diff.gz
  to pool/main/libg/libgef-java/libgef-java_0.11.1-2.diff.gz
libgef-java_0.11.1-2.dsc
  to pool/main/libg/libgef-java/libgef-java_0.11.1-2.dsc
libgef-java_0.11.1-2_all.deb
  to pool/main/libg/libgef-java/libgef-java_0.11.1-2_all.deb


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

Accepted imapfilter 1:1.1-2 (source i386)

2005-09-21 Thread Francesco Paolo Lovergine

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 13:22:49 +0200
Source: imapfilter
Binary: imapfilter
Architecture: source i386
Version: 1:1.1-2
Distribution: unstable
Urgency: high
Maintainer: Francesco Paolo Lovergine [EMAIL PROTECTED]
Changed-By: Francesco Paolo Lovergine [EMAIL PROTECTED]
Description: 
 imapfilter - filter mail in your IMAP account
Closes: 326007
Changes: 
 imapfilter (1:1.1-2) unstable; urgency=high
 .
   * Removed a double free, present from old days in debian version.
 (closes: #326007)
Files: 
 db4c0a8dbf514f4716e342be6dd480ca 618 mail optional imapfilter_1.1-2.dsc
 a50c69a3cd109af2bb2b3c253395d617 3332 mail optional imapfilter_1.1-2.diff.gz
 3caf7a5b442de878284ee17ddf18467d 36110 mail optional imapfilter_1.1-2_i386.deb

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

iD8DBQFDMUL8pFNRmenyx0cRAvFcAKDgu6vL/HmBcNsD5VyD/VZQs14IhgCdH5IU
mQOGS9ft/klQR0KJoW951lg=
=1RO2
-END PGP SIGNATURE-


Accepted:
imapfilter_1.1-2.diff.gz
  to pool/main/i/imapfilter/imapfilter_1.1-2.diff.gz
imapfilter_1.1-2.dsc
  to pool/main/i/imapfilter/imapfilter_1.1-2.dsc
imapfilter_1.1-2_i386.deb
  to pool/main/i/imapfilter/imapfilter_1.1-2_i386.deb


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

Accepted man-db 2.4.3-3 (source powerpc)

2005-09-21 Thread Colin Watson

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 13:03:47 +0100
Source: man-db
Binary: man-db
Architecture: source powerpc
Version: 2.4.3-3
Distribution: unstable
Urgency: low
Maintainer: Colin Watson [EMAIL PROTECTED]
Changed-By: Colin Watson [EMAIL PROTECTED]
Description: 
 man-db - The on-line manual pager
Closes: 326488 328982
Changes: 
 man-db (2.4.3-3) unstable; urgency=low
 .
   * Ignore SIGINT and SIGQUIT in the parent while running subprocesses
 (closes: #328982).
   * Improve SIGCHLD handling in pipeline library (closes: #326488):
 - Queue SIGCHLD for the whole time we're collecting child process
   statuses; we need to keep a careful count of processes.
 - Forget any previous errno before calling reap_children.
   * Explicitly tell po2debconf to use the 'popular' output encoding, so that
 the woody-compatibility hack works even with po-debconf 0.9.0.
Files: 
 3fb92c7b8cd6ef767633ec9cd4c63e30 594 doc important man-db_2.4.3-3.dsc
 650d6dabef735dd6e96c1304de70d494 74008 doc important man-db_2.4.3-3.diff.gz
 827897852218df9830594154731f79e2 691382 doc important 
man-db_2.4.3-3_powerpc.deb

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

iD8DBQFDMU1F9t0zAhD6TNERAkmjAJ4jPmH7RT5uzPQazkw6rDpRlCGGRQCggt55
2p1nmu5SbI6F7c1GylHjm4o=
=37PH
-END PGP SIGNATURE-


Accepted:
man-db_2.4.3-3.diff.gz
  to pool/main/m/man-db/man-db_2.4.3-3.diff.gz
man-db_2.4.3-3.dsc
  to pool/main/m/man-db/man-db_2.4.3-3.dsc
man-db_2.4.3-3_powerpc.deb
  to pool/main/m/man-db/man-db_2.4.3-3_powerpc.deb


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

Accepted zsh-beta 4.3.0-dev-1+20050920-1 (source all)

2005-09-21 Thread Clint Adams

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 20 Sep 2005 20:21:52 -0400
Source: zsh-beta
Binary: zsh-beta-static zsh-beta-doc zsh-beta
Architecture: source all
Version: 4.3.0-dev-1+20050920-1
Distribution: unstable
Urgency: low
Maintainer: Clint Adams [EMAIL PROTECTED]
Changed-By: Clint Adams [EMAIL PROTECTED]
Description: 
 zsh-beta   - A shell with lots of features (dev tree)
 zsh-beta-doc - zsh beta documentation - info/HTML format
Changes: 
 zsh-beta (4.3.0-dev-1+20050920-1) unstable; urgency=low
 .
   * Update to HEAD.
Files: 
 a9b310d195bd5f66e1a58cf192b0bcff 745 shells optional 
zsh-beta_4.3.0-dev-1+20050920-1.dsc
 5b7a38c6e91127de7223969fa69b593d 2178485 shells optional 
zsh-beta_4.3.0-dev-1+20050920.orig.tar.gz
 e9737548c31466188dd3bd56aa2aedb2 671828 shells optional 
zsh-beta_4.3.0-dev-1+20050920-1.diff.gz
 78ee8aa9801479820f2584c87ca74781 678300 shells optional 
zsh-beta-doc_4.3.0-dev-1+20050920-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Debian!

iD8DBQFDMU035m0u66uWM3ARAoywAJ9PVARwTyx6ZKrWg8WsV/8L43npoACfRF75
Gcl0DPk1MdIgcOMryM20Wkg=
=uD+m
-END PGP SIGNATURE-


Accepted:
zsh-beta-doc_4.3.0-dev-1+20050920-1_all.deb
  to pool/main/z/zsh-beta/zsh-beta-doc_4.3.0-dev-1+20050920-1_all.deb
zsh-beta_4.3.0-dev-1+20050920-1.diff.gz
  to pool/main/z/zsh-beta/zsh-beta_4.3.0-dev-1+20050920-1.diff.gz
zsh-beta_4.3.0-dev-1+20050920-1.dsc
  to pool/main/z/zsh-beta/zsh-beta_4.3.0-dev-1+20050920-1.dsc
zsh-beta_4.3.0-dev-1+20050920.orig.tar.gz
  to pool/main/z/zsh-beta/zsh-beta_4.3.0-dev-1+20050920.orig.tar.gz


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

Accepted ipw2100 1.1.2-2 (source all)

2005-09-21 Thread Sebastian Ley

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 13:48:41 +0200
Source: ipw2100
Binary: ipw2100-source
Architecture: source all
Version: 1.1.2-2
Distribution: unstable
Urgency: low
Maintainer: Sebastian Ley [EMAIL PROTECTED]
Changed-By: Sebastian Ley [EMAIL PROTECTED]
Description: 
 ipw2100-source - source for the ipw2100 driver
Closes: 328226 328775
Changes: 
 ipw2100 (1.1.2-2) unstable; urgency=low
 .
   * Use dpatch and add three patches:
 - 01-fix_build_kernel_2.6.13
   + Enables builds against kernel version 2.6.13 (Closes: #328226),
 Thanks to Mike Hommey for the patch.
 - 02-fixup_makefile
   + Adds $DESTDIR variable and removes depmod call during install
 (Has been patched before)
 - 03-fix_build_ieee80211_1.0.3
   + Enables builds against ieee80211 version 1.0.3
 (Has been patched before)
   * Small README.Debian fix (Closes: #328775)
Files: 
 52d2ffb544613e4c0d308978cc96c7fe 572 contrib/net optional ipw2100_1.1.2-2.dsc
 1f117d7f3e07d87130102b4d1b362492 9854 contrib/net optional 
ipw2100_1.1.2-2.diff.gz
 754f602bb7f578722425484994f235ed 100390 contrib/net optional 
ipw2100-source_1.1.2-2_all.deb

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

iD8DBQFDMUjzl+AzCZ/W4+YRAgcpAKD4HjHLFBdRjP6xoF94WIAzay+QBQCg3QRV
ewMXt+fx8RKx3irxcpdOxjQ=
=PPZZ
-END PGP SIGNATURE-


Accepted:
ipw2100-source_1.1.2-2_all.deb
  to pool/contrib/i/ipw2100/ipw2100-source_1.1.2-2_all.deb
ipw2100_1.1.2-2.diff.gz
  to pool/contrib/i/ipw2100/ipw2100_1.1.2-2.diff.gz
ipw2100_1.1.2-2.dsc
  to pool/contrib/i/ipw2100/ipw2100_1.1.2-2.dsc


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

Accepted vlc 0.8.4-svn20050920-3 (source i386)

2005-09-21 Thread Debian packages

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 11:36:24 +0200
Source: vlc
Binary: wxvlc vlc-plugin-sdl kvlc vlc-plugin-ggi gvlc vlc-plugin-alsa qvlc 
vlc-plugin-glide vlc-plugin-esd gnome-vlc mozilla-plugin-vlc vlc 
vlc-plugin-arts vlc-plugin-svgalib libvlc0-dev
Architecture: source i386
Version: 0.8.4-svn20050920-3
Distribution: unstable
Urgency: low
Maintainer: Sam Hocevar (Debian packages) [EMAIL PROTECTED]
Changed-By: Sam Hocevar (Debian packages) [EMAIL PROTECTED]
Description: 
 gnome-vlc  - GNOME frontend for VLC (dummy legacy package)
 gvlc   - GTK+ frontend for VLC (dummy legacy package)
 kvlc   - KDE frontend for VLC (dummy legacy package)
 libvlc0-dev - development files for VLC
 mozilla-plugin-vlc - multimedia plugin for Mozilla based on VLC
 qvlc   - Qt frontend for VLC (dummy legacy package)
 vlc- multimedia player for all audio and video formats
 vlc-plugin-alsa - ALSA audio output plugin for VLC
 vlc-plugin-arts - aRts audio output plugin for VLC
 vlc-plugin-esd - Esound audio output plugin for VLC
 vlc-plugin-ggi - GGI video output plugin for VLC
 vlc-plugin-glide - Glide video output plugin for VLC
 vlc-plugin-sdl - SDL video and audio output plugin for VLC
 vlc-plugin-svgalib - SVGAlib video output plugin for VLC
 wxvlc  - wxWindows frontend for VLC
Closes: 329317
Changes: 
 vlc (0.8.4-svn20050920-3) unstable; urgency=low
 .
   * configure.ac:
 + Fixed a bug in the gnomevfs plugin configuration.
   * debian/rules:
 + Explicitly disable the GnomeVFS plugin (Closes: #329317).
   * debian/control:
 + Buuild-depend on yasm on amd64.
Files: 
 820d852628b8edeb737f52976bbc0dbc 1885 graphics optional 
vlc_0.8.4-svn20050920-3.dsc
 01b21b5e6f809661f7821f98363447d2 1741 graphics optional 
vlc_0.8.4-svn20050920-3.diff.gz
 04013be714eaa0a6a1e80387de9b81b4 7583452 graphics optional 
vlc_0.8.4-svn20050920-3_i386.deb
 faafd1612a08c1704690198667e20315 918854 libdevel optional 
libvlc0-dev_0.8.4-svn20050920-3_i386.deb
 e1e26582d854dc1db27a46fc35c58ba5 1232 oldlibs optional 
gnome-vlc_0.8.4-svn20050920-3_i386.deb
 065832b56677b03162a685d7815730c1 1238 oldlibs optional 
gvlc_0.8.4-svn20050920-3_i386.deb
 90b8636730bdab34b8f8ddfdf11ec790 4454 graphics optional 
vlc-plugin-esd_0.8.4-svn20050920-3_i386.deb
 1a94f31bbb2cfc336861177233071abd 10154 graphics optional 
vlc-plugin-alsa_0.8.4-svn20050920-3_i386.deb
 0a8b9fb60c724b36bf381911ff8f37c3 10074 graphics optional 
vlc-plugin-sdl_0.8.4-svn20050920-3_i386.deb
 7008f319502fb73d6f6e3344f2eee0ff 5668 graphics optional 
vlc-plugin-ggi_0.8.4-svn20050920-3_i386.deb
 e9ecfb28e4217e31825cc1c7060c0d14 4022 graphics optional 
vlc-plugin-glide_0.8.4-svn20050920-3_i386.deb
 def5084479c0e82cd21d5cb99091a17e 956 oldlibs optional 
qvlc_0.8.4-svn20050920-3_i386.deb
 6a5cccdc5a55c6eb0b92b59e4097a5ab 3752 graphics optional 
vlc-plugin-arts_0.8.4-svn20050920-3_i386.deb
 449bfb5f7bd2e2b320aeeabd145cb195 687320 graphics optional 
mozilla-plugin-vlc_0.8.4-svn20050920-3_i386.deb
 b1202f27d75ea9598f934233191a7a6f 974 oldlibs optional 
kvlc_0.8.4-svn20050920-3_i386.deb
 cf1ab5fe917e3df5ee9ac238571164a4 4248 graphics optional 
vlc-plugin-svgalib_0.8.4-svn20050920-3_i386.deb
 587575fa7769f6d138a47b747c86ce47 384314 graphics optional 
wxvlc_0.8.4-svn20050920-3_i386.deb

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

iD8DBQFDMUiDfPP1rylJn2ERAukrAJkBzujSslxSFLjhyiLv7hYopvK3fQCfbnTB
0hakHWgIGHt7bfbS0dhvoNo=
=tGHE
-END PGP SIGNATURE-


Accepted:
gnome-vlc_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/gnome-vlc_0.8.4-svn20050920-3_i386.deb
gvlc_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/gvlc_0.8.4-svn20050920-3_i386.deb
kvlc_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/kvlc_0.8.4-svn20050920-3_i386.deb
libvlc0-dev_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/libvlc0-dev_0.8.4-svn20050920-3_i386.deb
mozilla-plugin-vlc_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/mozilla-plugin-vlc_0.8.4-svn20050920-3_i386.deb
qvlc_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/qvlc_0.8.4-svn20050920-3_i386.deb
vlc-plugin-alsa_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/vlc-plugin-alsa_0.8.4-svn20050920-3_i386.deb
vlc-plugin-arts_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/vlc-plugin-arts_0.8.4-svn20050920-3_i386.deb
vlc-plugin-esd_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/vlc-plugin-esd_0.8.4-svn20050920-3_i386.deb
vlc-plugin-ggi_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/vlc-plugin-ggi_0.8.4-svn20050920-3_i386.deb
vlc-plugin-glide_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/vlc-plugin-glide_0.8.4-svn20050920-3_i386.deb
vlc-plugin-sdl_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/vlc-plugin-sdl_0.8.4-svn20050920-3_i386.deb
vlc-plugin-svgalib_0.8.4-svn20050920-3_i386.deb
  to pool/main/v/vlc/vlc-plugin-svgalib_0.8.4-svn20050920-3_i386.deb
vlc_0.8.4-svn20050920-3.diff.gz
  to pool/main/v/vlc/vlc_0.8.4-svn20050920-3.diff.gz
vlc_0.8.4-svn20050920-3.dsc

Accepted hddtemp 0.3-beta14-1 (source mips)

2005-09-21 Thread Aurelien Jarno

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 14:48:43 +0200
Source: hddtemp
Binary: hddtemp
Architecture: source mips
Version: 0.3-beta14-1
Distribution: unstable
Urgency: low
Maintainer: Aurelien Jarno [EMAIL PROTECTED]
Changed-By: Aurelien Jarno [EMAIL PROTECTED]
Description: 
 hddtemp- Utility to monitor the temperature of your hard drive
Changes: 
 hddtemp (0.3-beta14-1) unstable; urgency=low
 .
   * New upstream version.
Files: 
 598eba49acacb7321b0e58442c98d776 616 utils extra hddtemp_0.3-beta14-1.dsc
 012a3a76e06e8a91eae97cf2822112f9 318772 utils extra 
hddtemp_0.3-beta14.orig.tar.gz
 f77ff3586cbfe510f730f86fa70d2f8d 26508 utils extra hddtemp_0.3-beta14-1.diff.gz
 b47c45bd5d36e8aa63a00a161b76d61c 47422 utils extra 
hddtemp_0.3-beta14-1_mips.deb

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

iD8DBQFDMVuYw3ao2vG823MRAmwSAJ4/dQY9Sd52nyVmAC1ScZSQG5NOlwCeIC8b
7SfGpfPXihc9mvJ69QELDqw=
=/y/5
-END PGP SIGNATURE-


Accepted:
hddtemp_0.3-beta14-1.diff.gz
  to pool/main/h/hddtemp/hddtemp_0.3-beta14-1.diff.gz
hddtemp_0.3-beta14-1.dsc
  to pool/main/h/hddtemp/hddtemp_0.3-beta14-1.dsc
hddtemp_0.3-beta14-1_mips.deb
  to pool/main/h/hddtemp/hddtemp_0.3-beta14-1_mips.deb
hddtemp_0.3-beta14.orig.tar.gz
  to pool/main/h/hddtemp/hddtemp_0.3-beta14.orig.tar.gz


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

Accepted blootbot 1.2.0-4 (source all)

2005-09-21 Thread Neil McGovern

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 14:25:08 +
Source: blootbot
Binary: blootbot
Architecture: source all
Version: 1.2.0-4
Distribution: unstable
Urgency: low
Maintainer: Neil McGovern [EMAIL PROTECTED]
Changed-By: Neil McGovern [EMAIL PROTECTED]
Description: 
 blootbot   - a severely modified infobot for IRC
Closes: 329375
Changes: 
 blootbot (1.2.0-4) unstable; urgency=low
 .
   * Added debconf-updatepo to clean stanza of debian/rules to update debconf
 translations. (closes: #329375) Thanks to Thomas Huriaux
 [EMAIL PROTECTED]
Files: 
 3433f453bfb8e3ae4ff28928dd34a8d2 625 net optional blootbot_1.2.0-4.dsc
 064cfd48dd76f456c380338df9287f99 19944 net optional blootbot_1.2.0-4.diff.gz
 807cbb7584aad102949eae7a9db4b956 249410 net optional blootbot_1.2.0-4_all.deb

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

iD8DBQFDMW2/97LBwbNFvdMRAhW/AKCOSA/f+JzMydmPcYV8IZxLPnrF/ACeJ3k4
W4jB/av176liNiVva7OHSVM=
=gijc
-END PGP SIGNATURE-


Accepted:
blootbot_1.2.0-4.diff.gz
  to pool/main/b/blootbot/blootbot_1.2.0-4.diff.gz
blootbot_1.2.0-4.dsc
  to pool/main/b/blootbot/blootbot_1.2.0-4.dsc
blootbot_1.2.0-4_all.deb
  to pool/main/b/blootbot/blootbot_1.2.0-4_all.deb


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

Accepted dhis-server 5.1-5 (source i386)

2005-09-21 Thread Guus Sliepen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 15:24:08 +0200
Source: dhis-server
Binary: dhis-server
Architecture: source i386
Version: 5.1-5
Distribution: unstable
Urgency: low
Maintainer: Guus Sliepen [EMAIL PROTECTED]
Changed-By: Guus Sliepen [EMAIL PROTECTED]
Description: 
 dhis-server - Dynamic Host Information System - server
Closes: 329272
Changes: 
 dhis-server (5.1-5) unstable; urgency=low
 .
   * Link against libgmp3c2. Closes: #329272
   * Add missing .El tag in manpage.
Files: 
 d1a9667b4dee77a4d0029f367c221e02 580 net optional dhis-server_5.1-5.dsc
 b21eb4b534bf52805ebeee7cb5d734fb 4566 net optional dhis-server_5.1-5.diff.gz
 ea3bc32c4c94cf687579ab95ee6fc588 29118 net optional dhis-server_5.1-5_i386.deb

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

iD8DBQFDMV8UAxLow12M2nsRAiOgAJ0XZ+BIUJUinWlrNiXGctWoVArZwACeIsky
OjvCptYAlZpQd72H3xakT50=
=YGwY
-END PGP SIGNATURE-


Accepted:
dhis-server_5.1-5.diff.gz
  to pool/main/d/dhis-server/dhis-server_5.1-5.diff.gz
dhis-server_5.1-5.dsc
  to pool/main/d/dhis-server/dhis-server_5.1-5.dsc
dhis-server_5.1-5_i386.deb
  to pool/main/d/dhis-server/dhis-server_5.1-5_i386.deb


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

Accepted dhis-tools-dns 5.0-4 (source i386)

2005-09-21 Thread Guus Sliepen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 15:27:47 +0200
Source: dhis-tools-dns
Binary: dhis-tools-dns dhis-tools-genkeys
Architecture: source i386
Version: 5.0-4
Distribution: unstable
Urgency: low
Maintainer: Guus Sliepen [EMAIL PROTECTED]
Changed-By: Guus Sliepen [EMAIL PROTECTED]
Description: 
 dhis-tools-dns - Dynamic Host Information System - DNS configuration tools
 dhis-tools-genkeys - Dynamic Host Information System - key generation tools
Closes: 329274
Changes: 
 dhis-tools-dns (5.0-4) unstable; urgency=low
 .
   * Link against libgmp3c2. Closes: #329274
Files: 
 3c7e1f711293f0990bf523724cb8c226 611 net optional dhis-tools-dns_5.0-4.dsc
 fb6cbf23988f3a9a4c9dd6e5efe20fa5 4221 net optional dhis-tools-dns_5.0-4.diff.gz
 7f7042383c153b66790207fa29cf87b2 7018 net optional 
dhis-tools-dns_5.0-4_i386.deb
 25141b71e2cd9b2f22d023ded1ecc44b 7450 net optional 
dhis-tools-genkeys_5.0-4_i386.deb

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

iD8DBQFDMWAiAxLow12M2nsRArO5AKCtiz4J31R2Dd0G9NOr8WDy+A3bEwCfaRmP
HyYyVi2bDCbRBrw/027HFhE=
=oQFi
-END PGP SIGNATURE-


Accepted:
dhis-tools-dns_5.0-4.diff.gz
  to pool/main/d/dhis-tools-dns/dhis-tools-dns_5.0-4.diff.gz
dhis-tools-dns_5.0-4.dsc
  to pool/main/d/dhis-tools-dns/dhis-tools-dns_5.0-4.dsc
dhis-tools-dns_5.0-4_i386.deb
  to pool/main/d/dhis-tools-dns/dhis-tools-dns_5.0-4_i386.deb
dhis-tools-genkeys_5.0-4_i386.deb
  to pool/main/d/dhis-tools-dns/dhis-tools-genkeys_5.0-4_i386.deb


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

Accepted mdk 1.2.1-1 (source i386)

2005-09-21 Thread Baruch Even

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 11:26:25 +0100
Source: mdk
Binary: mdk
Architecture: source i386
Version: 1.2.1-1
Distribution: unstable
Urgency: low
Maintainer: Baruch Even [EMAIL PROTECTED]
Changed-By: Baruch Even [EMAIL PROTECTED]
Description: 
 mdk- MIX Development Kit
Changes: 
 mdk (1.2.1-1) unstable; urgency=low
 .
   * New upstream version
Files: 
 8ec0fa53cd89eb62dd70f544f3e86edc 638 otherosfs optional mdk_1.2.1-1.dsc
 51c10c384b03016412729051091f63a7 1044323 otherosfs optional 
mdk_1.2.1.orig.tar.gz
 cc51a06a8206d21502ff0786d3d3b59f 5409 otherosfs optional mdk_1.2.1-1.diff.gz
 d2d4cefb43df6d3fec556c75c403da3d 510188 otherosfs optional mdk_1.2.1-1_i386.deb

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

iD8DBQFDMWBBHCar6qtHRZgRAtHtAKCGPIeCvPYRsV/0kSVqt8NILo7FmgCgmpKF
GY+47Y87VlblzNFJSlt+HXw=
=KcL7
-END PGP SIGNATURE-


Accepted:
mdk_1.2.1-1.diff.gz
  to pool/main/m/mdk/mdk_1.2.1-1.diff.gz
mdk_1.2.1-1.dsc
  to pool/main/m/mdk/mdk_1.2.1-1.dsc
mdk_1.2.1-1_i386.deb
  to pool/main/m/mdk/mdk_1.2.1-1_i386.deb
mdk_1.2.1.orig.tar.gz
  to pool/main/m/mdk/mdk_1.2.1.orig.tar.gz


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

Accepted cowdancer 0.5 (source i386)

2005-09-21 Thread Junichi Uekawa

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 22:54:34 +0900
Source: cowdancer
Binary: cowdancer
Architecture: source i386
Version: 0.5
Distribution: unstable
Urgency: low
Maintainer: Junichi Uekawa [EMAIL PROTECTED]
Changed-By: Junichi Uekawa [EMAIL PROTECTED]
Description: 
 cowdancer  - Copy-on-write directory tree utility.
Closes: 329344
Changes: 
 cowdancer (0.5) unstable; urgency=low
 .
   * cowdancer: cow-shell does not start, gives error (closes: #329344)
Files: 
 15415d903d2d48b2e12982d1942e613d 493 utils optional cowdancer_0.5.dsc
 6fa498269e90a29ed718ebb914e31d58 28262 utils optional cowdancer_0.5.tar.gz
 d28483a7cd20a716dbc468cca0c19e8c 10296 utils optional cowdancer_0.5_i386.deb

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

iD8DBQFDMWZD2Dd9TugeVcERAub4AJ9SeBKNdRTx13SbhAYeCTvcaBq0CwCeLGpZ
UVaEOc8pKSuN73mDSD+wZgU=
=AKve
-END PGP SIGNATURE-


Accepted:
cowdancer_0.5.dsc
  to pool/main/c/cowdancer/cowdancer_0.5.dsc
cowdancer_0.5.tar.gz
  to pool/main/c/cowdancer/cowdancer_0.5.tar.gz
cowdancer_0.5_i386.deb
  to pool/main/c/cowdancer/cowdancer_0.5_i386.deb


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

Accepted jcifs 1.2.3-1 (source all)

2005-09-21 Thread Wolfgang Baer

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 11 Sep 2005 16:48:45 +0200
Source: jcifs
Binary: libjcifs-java libjcifs-java-doc
Architecture: source all
Version: 1.2.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 
pkg-java-maintainers@lists.alioth.debian.org
Changed-By: Wolfgang Baer [EMAIL PROTECTED]
Description: 
 libjcifs-java - java library for the CIFS/SMB networking protocol
 libjcifs-java-doc - Documentation for libjcifs-java (CIFS/SMB library for java)
Changes: 
 jcifs (1.2.3-1) unstable; urgency=low
 .
   * New upstream release
   * Upload to unstable
   * Registered documentation with doc-base
   * libant1.6-java to ant transition
   * Updated FSF address
   * Fixed double spaces in description to fix linda warning
   * Standards-Version 3.6.2 (no changes)
 .
   * Upload sponsored by Arnaud Vandyck
Files: 
 843660ac9ba4e8090f64169d04bbe93a 702 - optional jcifs_1.2.3-1.dsc
 fb9faed0a1c6d62574bd3e4ccf9fa818 335164 - optional jcifs_1.2.3.orig.tar.gz
 5f97bffca04b65c4d784898c10550b5f 3286 - optional jcifs_1.2.3-1.diff.gz
 3248a10e3ab312ca02cfc0f235d3cde1 251496 libs optional 
libjcifs-java_1.2.3-1_all.deb
 16c42e1b11624ab2210f40c373ede08f 161012 doc optional 
libjcifs-java-doc_1.2.3-1_all.deb

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

iD8DBQFDMWlB4vzFZu62tMIRArBIAKCi23yBJlRio+7JfbIKH7iPIjou8QCdFAOH
LS3t/wqVitMGVIUD0t7BGAg=
=gOOI
-END PGP SIGNATURE-


Accepted:
jcifs_1.2.3-1.diff.gz
  to pool/main/j/jcifs/jcifs_1.2.3-1.diff.gz
jcifs_1.2.3-1.dsc
  to pool/main/j/jcifs/jcifs_1.2.3-1.dsc
jcifs_1.2.3.orig.tar.gz
  to pool/main/j/jcifs/jcifs_1.2.3.orig.tar.gz
libjcifs-java-doc_1.2.3-1_all.deb
  to pool/main/j/jcifs/libjcifs-java-doc_1.2.3-1_all.deb
libjcifs-java_1.2.3-1_all.deb
  to pool/main/j/jcifs/libjcifs-java_1.2.3-1_all.deb


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

Accepted mysql-dfsg-4.1 4.1.14-3 (source i386)

2005-09-21 Thread Christian Hammers

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Thu, 15 Sep 2005 22:26:03 +0200
Source: mysql-dfsg-4.1
Binary: libmysqlclient14-dev mysql-client libmysqlclient14 mysql-server 
mysql-server-4.1 mysql-client-4.1
Architecture: source i386
Version: 4.1.14-3
Distribution: unstable
Urgency: medium
Maintainer: Christian Hammers [EMAIL PROTECTED]
Changed-By: Christian Hammers [EMAIL PROTECTED]
Description: 
 libmysqlclient14 - mysql database client library
 libmysqlclient14-dev - mysql database development files
 mysql-client - mysql database client (transitional dummy package)
 mysql-client-4.1 - mysql database client binaries
 mysql-server - mysql database server (transitional dummy package)
 mysql-server-4.1 - mysql database server binaries
Closes: 236288 329166
Changes: 
 mysql-dfsg-4.1 (4.1.14-3) unstable; urgency=medium
 .
   * Symbol versioning support!  wohoo!
 (thanks to Steve Langasek) Closes: #236288
   * Moved libndbcclient.so.0 to the -dev package as it is provided by
 libmysqlclient14 and -15 which must be installable simultaneously.
 (it is version 0.0.0 and really not intended to be used in production)
   * Removed recommends to libmysqlclient14-dev from libmysqlclient14
 (thanks to Adam Majer). Closes: #329166
Files: 
 b33d527a7eba5d16a2e1011a0b37cb5a 1042 misc optional mysql-dfsg-4.1_4.1.14-3.dsc
 fe433946f38620e3839042e77f6e48f9 166143 misc optional 
mysql-dfsg-4.1_4.1.14-3.diff.gz
 f9e5e51747a90987b89f0baef8c80609 845560 misc optional 
mysql-client-4.1_4.1.14-3_i386.deb
 d62d8a8bfd26d40c255f8a332d0f3678 14690448 misc optional 
mysql-server-4.1_4.1.14-3_i386.deb
 16a1d8238a81dec1687a13b00e1e05c8 1208912 libs optional 
libmysqlclient14_4.1.14-3_i386.deb
 a4836003fdc6a7e25867363532add3c3 5523914 libdevel optional 
libmysqlclient14-dev_4.1.14-3_i386.deb
 ae4293723d994e2afc9c5596a06ca668 34840 misc optional 
mysql-server_4.1.14-3_i386.deb
 68ef5740796bcc8673bc812b81a3b5b4 34840 misc optional 
mysql-client_4.1.14-3_i386.deb

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

iEYEARECAAYFAkMxcOoACgkQkR9K5oahGObt7QCffL0aCczE/AGWWm+MXeQqB/Yd
tEwAoO/i3GHXrWGlq7WtwuRwnpxOTq3q
=SCzU
-END PGP SIGNATURE-


Accepted:
libmysqlclient14-dev_4.1.14-3_i386.deb
  to pool/main/m/mysql-dfsg-4.1/libmysqlclient14-dev_4.1.14-3_i386.deb
libmysqlclient14_4.1.14-3_i386.deb
  to pool/main/m/mysql-dfsg-4.1/libmysqlclient14_4.1.14-3_i386.deb
mysql-client-4.1_4.1.14-3_i386.deb
  to pool/main/m/mysql-dfsg-4.1/mysql-client-4.1_4.1.14-3_i386.deb
mysql-client_4.1.14-3_i386.deb
  to pool/main/m/mysql-dfsg-4.1/mysql-client_4.1.14-3_i386.deb
mysql-dfsg-4.1_4.1.14-3.diff.gz
  to pool/main/m/mysql-dfsg-4.1/mysql-dfsg-4.1_4.1.14-3.diff.gz
mysql-dfsg-4.1_4.1.14-3.dsc
  to pool/main/m/mysql-dfsg-4.1/mysql-dfsg-4.1_4.1.14-3.dsc
mysql-server-4.1_4.1.14-3_i386.deb
  to pool/main/m/mysql-dfsg-4.1/mysql-server-4.1_4.1.14-3_i386.deb
mysql-server_4.1.14-3_i386.deb
  to pool/main/m/mysql-dfsg-4.1/mysql-server_4.1.14-3_i386.deb


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

Accepted lm-sensors 1:2.9.2-2 (source i386 all)

2005-09-21 Thread Aurelien Jarno

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 15:24:28 +0200
Source: lm-sensors
Binary: lm-sensors-2.4.27-2-386 lm-sensors-source lm-sensors-2.4.27-2-k7 
libsensors-dev lm-sensors-2.4.27-2-k7-smp lm-sensors-2.4.27-2-586tsc lm-sensors 
sensord kernel-patch-2.4-lm-sensors lm-sensors-2.4.27-2-686 
lm-sensors-2.4.27-2-k6 lm-sensors-2.4.27-2-686-smp libsensors3
Architecture: source i386 all
Version: 1:2.9.2-2
Distribution: unstable
Urgency: low
Maintainer: Aurelien Jarno [EMAIL PROTECTED]
Changed-By: Aurelien Jarno [EMAIL PROTECTED]
Description: 
 kernel-patch-2.4-lm-sensors - drivers to read temperature/voltage/fan sensors
 libsensors-dev - lm-sensors development kit
 libsensors3 - library to read temperature/voltage/fan sensors
 lm-sensors - utilities to read temperature/voltage/fan sensors
 lm-sensors-2.4.27-2-386 - kernel drivers to read temperature/voltage/fan 
sensors
 lm-sensors-2.4.27-2-586tsc - kernel drivers to read temperature/voltage/fan 
sensors
 lm-sensors-2.4.27-2-686 - kernel drivers to read temperature/voltage/fan 
sensors
 lm-sensors-2.4.27-2-686-smp - kernel drivers to read temperature/voltage/fan 
sensors
 lm-sensors-2.4.27-2-k6 - kernel drivers to read temperature/voltage/fan sensors
 lm-sensors-2.4.27-2-k7 - kernel drivers to read temperature/voltage/fan sensors
 lm-sensors-2.4.27-2-k7-smp - kernel drivers to read temperature/voltage/fan 
sensors
 lm-sensors-source - kernel drivers to read temperature/voltage/fan sensors 
(source)
 sensord- hardware sensor information logging daemon
Changes: 
 lm-sensors (1:2.9.2-2) unstable; urgency=low
 .
   * The conflict between i2c-viapro and via686a modules has been fixed in
 kernel 2.6.10. As the problem is not present anymore in kernels shipped
 by Debian, don' blacklist i2c-viapro anymore.
Files: 
 049e5727b1b2fbd4a07814a9625261dc 1086 utils extra lm-sensors_2.9.2-2.dsc
 3bf79edc78f80c71298829ec592c9822 32225 utils extra lm-sensors_2.9.2-2.diff.gz
 f443b2385e57510debeca941bd2af280 475492 utils extra lm-sensors_2.9.2-2_i386.deb
 9c3201f4951bc83d3e4c171a80bfc40a 78570 libs optional 
libsensors3_2.9.2-2_i386.deb
 2d2f38ab7ab34f1ab4f808433e48525d 94034 libdevel extra 
libsensors-dev_2.9.2-2_i386.deb
 fbf2063a3f3ddb0801e8553a1d44b212 57156 utils extra sensord_2.9.2-2_i386.deb
 a2656a0e040a9adcf715e422736bf6e6 261758 utils extra 
lm-sensors-2.4.27-2-386_2.9.2-2_i386.deb
 a5d57db0ff74b6174cc505d545cb6cd7 261694 utils extra 
lm-sensors-2.4.27-2-586tsc_2.9.2-2_i386.deb
 8c7f1bcc2919db6485f771ef7c4207ad 261758 utils extra 
lm-sensors-2.4.27-2-686_2.9.2-2_i386.deb
 b0a5cb6d39b364934ce53bfdbe2d4a97 262298 utils extra 
lm-sensors-2.4.27-2-686-smp_2.9.2-2_i386.deb
 511c186260af4e60d6e8676a5bb0c28c 261782 utils extra 
lm-sensors-2.4.27-2-k6_2.9.2-2_i386.deb
 c450c80ec48a03aa595ad55888ed728c 262100 utils extra 
lm-sensors-2.4.27-2-k7_2.9.2-2_i386.deb
 34be8c940673cdfabc86629c46878e62 262644 utils extra 
lm-sensors-2.4.27-2-k7-smp_2.9.2-2_i386.deb
 85ae843a91ca231dadc7e644fbe8b5f1 318588 devel extra 
kernel-patch-2.4-lm-sensors_2.9.2-2_all.deb
 b621a1bd3c05888634cd9010087b46e1 932908 misc extra 
lm-sensors-source_2.9.2-2_all.deb

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

iD8DBQFDMWcaw3ao2vG823MRAtqoAKCE3umgSoNBoH60FE8pPk8cAEm0WwCeKbPM
ueMHRrJriXG2YvrHns7wzp8=
=M/9b
-END PGP SIGNATURE-


Accepted:
kernel-patch-2.4-lm-sensors_2.9.2-2_all.deb
  to pool/main/l/lm-sensors/kernel-patch-2.4-lm-sensors_2.9.2-2_all.deb
libsensors-dev_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/libsensors-dev_2.9.2-2_i386.deb
libsensors3_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/libsensors3_2.9.2-2_i386.deb
lm-sensors-2.4.27-2-386_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/lm-sensors-2.4.27-2-386_2.9.2-2_i386.deb
lm-sensors-2.4.27-2-586tsc_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/lm-sensors-2.4.27-2-586tsc_2.9.2-2_i386.deb
lm-sensors-2.4.27-2-686-smp_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/lm-sensors-2.4.27-2-686-smp_2.9.2-2_i386.deb
lm-sensors-2.4.27-2-686_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/lm-sensors-2.4.27-2-686_2.9.2-2_i386.deb
lm-sensors-2.4.27-2-k6_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/lm-sensors-2.4.27-2-k6_2.9.2-2_i386.deb
lm-sensors-2.4.27-2-k7-smp_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/lm-sensors-2.4.27-2-k7-smp_2.9.2-2_i386.deb
lm-sensors-2.4.27-2-k7_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/lm-sensors-2.4.27-2-k7_2.9.2-2_i386.deb
lm-sensors-source_2.9.2-2_all.deb
  to pool/main/l/lm-sensors/lm-sensors-source_2.9.2-2_all.deb
lm-sensors_2.9.2-2.diff.gz
  to pool/main/l/lm-sensors/lm-sensors_2.9.2-2.diff.gz
lm-sensors_2.9.2-2.dsc
  to pool/main/l/lm-sensors/lm-sensors_2.9.2-2.dsc
lm-sensors_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/lm-sensors_2.9.2-2_i386.deb
sensord_2.9.2-2_i386.deb
  to pool/main/l/lm-sensors/sensord_2.9.2-2_i386.deb


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

Accepted prelink 0.0.20050901-1 (source i386)

2005-09-21 Thread Andrés Roldán

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 14:25:11 +
Source: prelink
Binary: prelink
Architecture: source i386
Version: 0.0.20050901-1
Distribution: unstable
Urgency: low
Maintainer: AndrÃ©s RoldÃ¡n [EMAIL PROTECTED]
Changed-By: AndrÃ©s RoldÃ¡n [EMAIL PROTECTED]
Description: 
 prelink- ELF prelinking utility to speed up dynamic linking
Changes: 
 prelink (0.0.20050901-1) unstable; urgency=low
 .
   * New upstream version.
   * Standards-Version is now 3.6.2.
Files: 
 66c4b7ffd2504bf144d1b69bb933cb8c 790 admin optional prelink_0.0.20050901-1.dsc
 c783d27b94fe778ff0a3e41aead43045 1019411 admin optional 
prelink_0.0.20050901.orig.tar.gz
 d9b1516c44ecdc904931e51901ec4f49 18438 admin optional 
prelink_0.0.20050901-1.diff.gz
 9d9c6f9643010dcaefbbbf43ba79abd3 681734 admin optional 
prelink_0.0.20050901-1_i386.deb

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

iD8DBQFDMW9T2OByS7KTlusRAnSQAKDhdrTzbPau86z10XVqSBAN2s4gzQCeO2Pm
ejMi1eANu3ufyva7q8WH1kI=
=cSyZ
-END PGP SIGNATURE-


Accepted:
prelink_0.0.20050901-1.diff.gz
  to pool/main/p/prelink/prelink_0.0.20050901-1.diff.gz
prelink_0.0.20050901-1.dsc
  to pool/main/p/prelink/prelink_0.0.20050901-1.dsc
prelink_0.0.20050901-1_i386.deb
  to pool/main/p/prelink/prelink_0.0.20050901-1_i386.deb
prelink_0.0.20050901.orig.tar.gz
  to pool/main/p/prelink/prelink_0.0.20050901.orig.tar.gz


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

Accepted util-linux 2.12p-8 (source all i386)

2005-09-21 Thread LaMont Jones

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 08:36:17 -0600
Source: util-linux
Binary: util-linux fdisk-udeb util-linux-locales bsdutils mount
Architecture: all i386 source 
Version: 2.12p-8
Distribution: unstable
Urgency: high
Maintainer: LaMont Jones [EMAIL PROTECTED]
Changed-By: LaMont Jones [EMAIL PROTECTED]
Description: 
 bsdutils   - Basic utilities from 4.4BSD-Lite
 fdisk-udeb - Partition a hard drive (manual, cfdisk)
 mount  - Tools for mounting and manipulating filesystems
 util-linux - Miscellaneous system utilities
 util-linux-locales - Locales files for util-linux
Closes: 328141 329063
Changes: 
 util-linux (2.12p-8) unstable; urgency=high
 .
   * if /etc/adjtime is a dangling symlink, don't use it in hwclock*.sh
   * Applited patch by Max Vozeler to fix a local privilege escalation
 vulnerability in umount -r [debian/patches/51security_CAN-2005-2876.dpatch]
 Closes: #328141, #329063
Files: 
 05dc3e83e483b500a188941d4ec58ca0 700 base required util-linux_2.12p-8.dsc
 262121de89e4a4d5da64a9a3043978a9 66258 base required bsdutils_2.12p-8_i386.deb
 9ae6656ec71c88fd133b065491ab5079 76281 base required util-linux_2.12p-8.diff.gz
 a7c20de195c91631b873ee77745f66f2 140396 base required mount_2.12p-8_i386.deb
 d415a1a9db5caa576f2b674183aba292 369144 base required 
util-linux_2.12p-8_i386.deb
 f07516de7a286e0d396aa9dafa95fc3b 1072692 utils optional 
util-linux-locales_2.12p-8_all.deb
 f28485490ec5b6208c4850bdec4d2fc0 537254 debian-installer extra 
fdisk-udeb_2.12p-8_i386.udeb

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

iD8DBQFDMXGRzN/kmwoKyScRAsj5AJ0dhwzeGrFvt4qByplpRYb8Sq1QiwCdEvAy
QDMHhcsAA129GQwDOx8gJBQ=
=M26d
-END PGP SIGNATURE-


Accepted:
bsdutils_2.12p-8_i386.deb
  to pool/main/u/util-linux/bsdutils_2.12p-8_i386.deb
fdisk-udeb_2.12p-8_i386.udeb
  to pool/main/u/util-linux/fdisk-udeb_2.12p-8_i386.udeb
mount_2.12p-8_i386.deb
  to pool/main/u/util-linux/mount_2.12p-8_i386.deb
util-linux-locales_2.12p-8_all.deb
  to pool/main/u/util-linux/util-linux-locales_2.12p-8_all.deb
util-linux_2.12p-8.diff.gz
  to pool/main/u/util-linux/util-linux_2.12p-8.diff.gz
util-linux_2.12p-8.dsc
  to pool/main/u/util-linux/util-linux_2.12p-8.dsc
util-linux_2.12p-8_i386.deb
  to pool/main/u/util-linux/util-linux_2.12p-8_i386.deb


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

Accepted aish 1.13-5 (source i386)

2005-09-21 Thread Atsushi Kamoshida

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 23:55:48 +0900
Source: aish
Binary: aish
Architecture: source i386
Version: 1.13-5
Distribution: unstable
Urgency: low
Maintainer: Atsushi KAMOSHIDA [EMAIL PROTECTED]
Changed-By: Atsushi Kamoshida [EMAIL PROTECTED]
Description: 
 aish   - ish/base64/uuencoded_file converter
Changes: 
 aish (1.13-5) unstable; urgency=low
 .
   * Removed old documents.
Files: 
 2f69c379ff5ecbb5958d327810fb3a9c 537 utils optional aish_1.13-5.dsc
 8e0ce3831d51f26540187d361a64be9c 3507 utils optional aish_1.13-5.diff.gz
 1f86d6ae17348e4c4cd30dd13f4ab020 35848 utils optional aish_1.13-5_i386.deb

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

iD8DBQFDMXTgYxU8kEKVVoIRAtOEAJ9OvT7C801ubY4nxWqKcYkRK4BNkQCfSeZ6
z271g/N4+mwj10fsczLMQQ8=
=IfHm
-END PGP SIGNATURE-


Accepted:
aish_1.13-5.diff.gz
  to pool/main/a/aish/aish_1.13-5.diff.gz
aish_1.13-5.dsc
  to pool/main/a/aish/aish_1.13-5.dsc
aish_1.13-5_i386.deb
  to pool/main/a/aish/aish_1.13-5_i386.deb


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

Accepted trophy 1.1.3-3 (source i386 all)

2005-09-21 Thread Guus Sliepen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 22 Jul 2005 15:01:42 +0200
Source: trophy
Binary: trophy-data trophy
Architecture: source i386 all
Version: 1.1.3-3
Distribution: unstable
Urgency: low
Maintainer: Guus Sliepen [EMAIL PROTECTED]
Changed-By: Guus Sliepen [EMAIL PROTECTED]
Description: 
 trophy - A 2D car racing action game
 trophy-data - A 2D car racing action game - graphics and sounds
Closes: 311035
Changes: 
 trophy (1.1.3-3) unstable; urgency=low
 .
   * Recompile needed for C++ ABI change.
   * Add menu hints. Closes: #311035
Files: 
 4062bd5ff402374056b7250ce2e1fc1a 594 games optional trophy_1.1.3-3.dsc
 e003a45cfd59305a99928666b258a870 6589 games optional trophy_1.1.3-3.diff.gz
 e9a7df5bf6170a8bb2983e412aadb928 9137550 games optional 
trophy-data_1.1.3-3_all.deb
 076499522b0556f0d3022dae4d37832e 86094 games optional trophy_1.1.3-3_i386.deb

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

iD8DBQFDMXcKAxLow12M2nsRAlNpAJwNt52RLCoBhUqhgpi73sGpDKrM9gCdGFM8
Oj+WVm/AP+hAedWAcIcb0qo=
=b8+0
-END PGP SIGNATURE-


Accepted:
trophy-data_1.1.3-3_all.deb
  to pool/main/t/trophy/trophy-data_1.1.3-3_all.deb
trophy_1.1.3-3.diff.gz
  to pool/main/t/trophy/trophy_1.1.3-3.diff.gz
trophy_1.1.3-3.dsc
  to pool/main/t/trophy/trophy_1.1.3-3.dsc
trophy_1.1.3-3_i386.deb
  to pool/main/t/trophy/trophy_1.1.3-3_i386.deb


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

Accepted libjdom1-java 1.0-2 (source all)

2005-09-21 Thread Wolfgang Baer

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 11 Sep 2005 18:36:14 +0200
Source: libjdom1-java
Binary: libjdom1-java
Architecture: source all
Version: 1.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 
pkg-java-maintainers@lists.alioth.debian.org
Changed-By: Wolfgang Baer [EMAIL PROTECTED]
Description: 
 libjdom1-java - lightweight and fast library using XML
Changes: 
 libjdom1-java (1.0-2) unstable; urgency=low
 .
   * Removed libjdom0-java.links file from old release
   * libant1.6-java to ant transition
   * Patched build.xml to build with target=1.3 to support JDK 1.3
   * Removed clean:: target - not needed anymore
   * Added suggests java-virtual-machine
   * Generated (normal) javadoc through gjdoc
 + Added javadoc target to ant targets
 + Removed doxygen stuff (debian/rules, debian/control, doxygen.cfg)
 + Register documentation with doc-base
   * Standards-Version 3.6.2 (no changes)
   * Added myself to uploaders
 .
   * Upload sponsored by Petter Reinholdtsen
Files: 
 19384b7489bdd3aee8cf508835a8c565 785 libs optional libjdom1-java_1.0-2.dsc
 abc05f2eeba1f15a58a21a51cb2565a2 3693 libs optional libjdom1-java_1.0-2.diff.gz
 934458c18a13050a7b9289eed39e3edd 336082 libs optional 
libjdom1-java_1.0-2_all.deb

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

iD8DBQFDMXk34vzFZu62tMIRAjTAAJ9+7bWgqOzYKWV+EgGaOpfpuzthXACfThBs
HPp3mh8X4l1wD7YyH9Mw5eY=
=XfrK
-END PGP SIGNATURE-


Accepted:
libjdom1-java_1.0-2.diff.gz
  to pool/main/libj/libjdom1-java/libjdom1-java_1.0-2.diff.gz
libjdom1-java_1.0-2.dsc
  to pool/main/libj/libjdom1-java/libjdom1-java_1.0-2.dsc
libjdom1-java_1.0-2_all.deb
  to pool/main/libj/libjdom1-java/libjdom1-java_1.0-2_all.deb


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

Accepted vkeybd 1:0.1.17-2 (source powerpc)

2005-09-21 Thread Free Ekanayaka

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 14 Sep 2005 10:13:50 +0100
Source: vkeybd
Binary: vkeybd
Architecture: source powerpc
Version: 1:0.1.17-2
Distribution: unstable
Urgency: low
Maintainer: Free Ekanayaka [EMAIL PROTECTED]
Changed-By: Free Ekanayaka [EMAIL PROTECTED]
Description: 
 vkeybd - Virtual MIDI Keyboard
Closes: 310506
Changes: 
 vkeybd (1:0.1.17-2) unstable; urgency=low
 .
   * Better description (closes: #310506), thanks to
 [EMAIL PROTECTED]
   * Added desktop file
Files: 
 c3b61d68be33b6bab7c1d96eb71ddaf9 634 sound optional vkeybd_0.1.17-2.dsc
 2c605c4f3f9f6cae308b4e750a93c2b0 7967 sound optional vkeybd_0.1.17-2.diff.gz
 8b33f58cde6126bca76065e583f2ddec 31710 sound optional 
vkeybd_0.1.17-2_powerpc.deb

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

iD8DBQFDMX3d2PLmgVuXpdIRAlaUAJ9Ev99lAiOkSKIB6OTsThDULdubiACfcny7
tDYEI+sDWubyWiRM/GnPFU8=
=X4zP
-END PGP SIGNATURE-


Accepted:
vkeybd_0.1.17-2.diff.gz
  to pool/main/v/vkeybd/vkeybd_0.1.17-2.diff.gz
vkeybd_0.1.17-2.dsc
  to pool/main/v/vkeybd/vkeybd_0.1.17-2.dsc
vkeybd_0.1.17-2_powerpc.deb
  to pool/main/v/vkeybd/vkeybd_0.1.17-2_powerpc.deb


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

Accepted haskelldb 0.9.cvs.601-7 (source i386)

2005-09-21 Thread John Goerzen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 05:38:29 -0500
Source: haskelldb
Binary: haskelldb-bin libghc6-haskelldb-dev
Architecture: source i386
Version: 0.9.cvs.601-7
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
Changed-By: John Goerzen [EMAIL PROTECTED]
Description: 
 haskelldb-bin - Utilities for use with HaskellDB
 libghc6-haskelldb-dev - Haskell library for expressing database queries
Closes: 329275
Changes: 
 haskelldb (0.9.cvs.601-7) unstable; urgency=low
 .
   * [NMU] Rebuilt to get newer gmp3.  Closes: #329275.
   * Updated dep on haskell-hsql to version in sid.
Files: 
 6992bf65ba9b95b6659dcab2c1931380 715 - optional haskelldb_0.9.cvs.601-7.dsc
 7a9de82ecac7281c89aa734d8438accb 5967 - optional 
haskelldb_0.9.cvs.601-7.diff.gz
 9f5d93516e00a294f32a2ffd2cd5ae99 661640 libdevel optional 
libghc6-haskelldb-dev_0.9.cvs.601-7_i386.deb
 bab135c9b60849ba7705e266e1f182c3 329440 devel optional 
haskelldb-bin_0.9.cvs.601-7_i386.deb

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

iD8DBQFDMX8N7B2mSKdID5ERArUkAKCYzK8sABkkxWldp6kxAoK3G76kHACfX0AJ
vSOpYA7l7Co/OhMqX5clT4s=
=mCnu
-END PGP SIGNATURE-


Accepted:
haskelldb-bin_0.9.cvs.601-7_i386.deb
  to pool/main/h/haskelldb/haskelldb-bin_0.9.cvs.601-7_i386.deb
haskelldb_0.9.cvs.601-7.diff.gz
  to pool/main/h/haskelldb/haskelldb_0.9.cvs.601-7.diff.gz
haskelldb_0.9.cvs.601-7.dsc
  to pool/main/h/haskelldb/haskelldb_0.9.cvs.601-7.dsc
libghc6-haskelldb-dev_0.9.cvs.601-7_i386.deb
  to pool/main/h/haskelldb/libghc6-haskelldb-dev_0.9.cvs.601-7_i386.deb


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

Accepted lhs2tex 1.9-2 (source i386)

2005-09-21 Thread John Goerzen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 05:32:01 -0500
Source: lhs2tex
Binary: lhs2tex
Architecture: source i386
Version: 1.9-2
Distribution: unstable
Urgency: low
Maintainer: John Goerzen [EMAIL PROTECTED]
Changed-By: John Goerzen [EMAIL PROTECTED]
Description: 
 lhs2tex- Generates LaTeX code from literate Haskell sources
Closes: 329276
Changes: 
 lhs2tex (1.9-2) unstable; urgency=low
 .
   * Rebuilt to get dep on correct new libgmp3 in sid.  Closes: #329276.
Files: 
 0123a18edff2916e57b084af5853d2a6 597 text optional lhs2tex_1.9-2.dsc
 eb8a8a315ffb2fa8d89d9a9ee4f99fcd 25376 text optional lhs2tex_1.9-2.diff.gz
 2c44916bb57479a540753017f144b5aa 506704 text optional lhs2tex_1.9-2_i386.deb

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

iD8DBQFDMX2J7B2mSKdID5ERAu0TAKCeEpoqSodQLLeZpyLWseND2RVKxgCdEu1M
yb00VZrIgwqYNGDyxnP3K28=
=ITV+
-END PGP SIGNATURE-


Accepted:
lhs2tex_1.9-2.diff.gz
  to pool/main/l/lhs2tex/lhs2tex_1.9-2.diff.gz
lhs2tex_1.9-2.dsc
  to pool/main/l/lhs2tex/lhs2tex_1.9-2.dsc
lhs2tex_1.9-2_i386.deb
  to pool/main/l/lhs2tex/lhs2tex_1.9-2_i386.deb


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

Accepted tvtime 1.0.1-2 (source i386)

2005-09-21 Thread Simon Law

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 10:06:30 -0400
Source: tvtime
Binary: tvtime
Architecture: source i386
Version: 1.0.1-2
Distribution: unstable
Urgency: low
Maintainer: Simon Law [EMAIL PROTECTED]
Changed-By: Simon Law [EMAIL PROTECTED]
Description: 
 tvtime - A high quality television application
Changes: 
 tvtime (1.0.1-2) unstable; urgency=low
 .
   * Switch architecture to any, since tvtime no longer depends on i386
 assembly.
   * Add debian/watch file.
Files: 
 c215798133568f994a9927c91026fae0 633 x11 optional tvtime_1.0.1-2.dsc
 0c486d265ada4efd77bcff7e3be647bd 33975 x11 optional tvtime_1.0.1-2.diff.gz
 a7772df72157093233b14684b17a60f9 648602 x11 optional tvtime_1.0.1-2_i386.deb

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

iD8DBQFDMYARLiz2e3eWpgsRAvv4AKDMEdwhJqC+SGgEyebwnDlAunirCACffan5
ZXt/g0sWmVldSpU7GvCduvU=
=i3Zf
-END PGP SIGNATURE-


Accepted:
tvtime_1.0.1-2.diff.gz
  to pool/main/t/tvtime/tvtime_1.0.1-2.diff.gz
tvtime_1.0.1-2.dsc
  to pool/main/t/tvtime/tvtime_1.0.1-2.dsc
tvtime_1.0.1-2_i386.deb
  to pool/main/t/tvtime/tvtime_1.0.1-2_i386.deb


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

Accepted rootskel 1.22 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 17:28:00 +0200
Source: rootskel
Binary: rootskel-bootfloppy rootskel
Architecture: source i386
Version: 1.22
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team debian-boot@lists.debian.org
Changed-By: Joey Hess [EMAIL PROTECTED]
Description: 
 rootskel   - Skeleton root filesystem used by debian-installer (udeb)
 rootskel-bootfloppy - Skeleton root filesystem used by debian-installer boot 
floppy (udeb)
Closes: 328729
Changes: 
 rootskel (1.22) unstable; urgency=low
 .
   * src-bootfloppy/init: export PATH. Closes: #328729.
 Necessary because busybox sh sets but does not export PATH anymore.
   * src/init, src/sbin/init: export PATH here too, for good measure.
Files: 
 f77b257c1195335e49a7509a96cc6527 772 debian-installer standard 
rootskel_1.22.dsc
 fb47a6ff2d04db5537866ce6f3264d65 22778 debian-installer standard 
rootskel_1.22.tar.gz
 c9c08103d4130bcb71d2f05cb3cb8982 5608 debian-installer standard 
rootskel_1.22_i386.udeb
 8c9c466d3d827c4a251dd6d58e0620f9 2698 debian-installer extra 
rootskel-bootfloppy_1.22_i386.udeb
Package-Type: udeb

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

iD8DBQFDMYOZ2tp5zXiKP0wRAqnLAKCWiRTkHcQsoAbBNbhoYq9foTQDwQCfXdON
geGrH0er0nysGnvFfQvPqmA=
=RVkk
-END PGP SIGNATURE-


Accepted:
rootskel-bootfloppy_1.22_i386.udeb
  to pool/main/r/rootskel/rootskel-bootfloppy_1.22_i386.udeb
rootskel_1.22.dsc
  to pool/main/r/rootskel/rootskel_1.22.dsc
rootskel_1.22.tar.gz
  to pool/main/r/rootskel/rootskel_1.22.tar.gz
rootskel_1.22_i386.udeb
  to pool/main/r/rootskel/rootskel_1.22_i386.udeb


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

Accepted base-config 2.72 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 18:21:48 +0200
Source: base-config
Binary: base-config
Architecture: source all
Version: 2.72
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team debian-boot@lists.debian.org
Changed-By: Joey Hess [EMAIL PROTECTED]
Description: 
 base-config - Debian base system configurator
Closes: 327499
Changes: 
 base-config (2.72) unstable; urgency=low
 .
   [ Debconf translations ]
   * Ukrainian updated by Eugeniy Meshcheryakov
 .
   [ Program translations ]
   * Ukrainian updated by Eugeniy Meshcheryakov
 .
   [ Joey Hess ]
   * Run preseed late and early commands in a subshell so that they can
 cd without messing up base-config. Thanks, Paul Millar. Closes: #327499
   * If tasksel fails, don't use debconf to display an error message, since
 that clears the screen with the default frontend and makes it hard to see
 what broke. Instead, use gettext/read.
   * Remove base-config/install-problem template, now unused.
Files: 
 c17302a650f0def3252716b314fe4657 713 base important base-config_2.72.dsc
 aa81813d15244b7e63edb9b6e30190fd 401064 base important base-config_2.72.tar.gz
 71508a2b9918ca335cc549f35bd62e55 252596 base important base-config_2.72_all.deb

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

iD8DBQFDMYrQ2tp5zXiKP0wRAg0MAJ92Tm/4H2jKUOEDBKGvo7Pc3qxAQwCggst7
SdvlaNOlBb909fj7N2yyOuo=
=q7XL
-END PGP SIGNATURE-


Accepted:
base-config_2.72.dsc
  to pool/main/b/base-config/base-config_2.72.dsc
base-config_2.72.tar.gz
  to pool/main/b/base-config/base-config_2.72.tar.gz
base-config_2.72_all.deb
  to pool/main/b/base-config/base-config_2.72_all.deb


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

Accepted maxima 5.9.1-10 (source all i386)

2005-09-21 Thread Camm Maguire

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 16:21:03 +
Source: maxima
Binary: maxima-test maxima-share maxima-emacs maxima-doc maxima-src xmaxima 
maxima
Architecture: source all i386
Version: 5.9.1-10
Distribution: unstable
Urgency: high
Maintainer: Camm Maguire [EMAIL PROTECTED]
Changed-By: Camm Maguire [EMAIL PROTECTED]
Description: 
 maxima - A fairly complete computer algebra system-- base system
 maxima-doc - A fairly complete computer algebra system-- documentation
 maxima-emacs - A fairly complete computer algebra system-- emacs interface
 maxima-share - A fairly complete computer algebra system-- extra code
 maxima-src - A fairly complete computer algebra system-- source code
 maxima-test - A fairly complete computer algebra system-- test suite
 xmaxima- A fairly complete computer algebra system-- x interface
Closes: 301515 301516 303224 323563 325852 326325 329016
Changes: 
 maxima (5.9.1-10) unstable; urgency=high
 .
   * Rebuild against libgmp3c2, Closes: #323563, Closes: #325852
   * libreadline5-dev build dep, Closes: #326325.  Closes: #301515
   * Remove binutils-dev dependency and depend on = gcl 2.6.7-6 which has
 it built in
   * Incorporate libreadline Control-D fix from gcl, Closes: 301516.
   * Depend on gnuplot_nox, Closes: #329016
   * Rename doc-base files .shtml - .html, Closes: #303224
   * newer standards
Files: 
 c8900879073dd01bea26919ebbc27bb0 803 math optional maxima_5.9.1-10.dsc
 68713828488067bf7ec0438ee07c4780 2093723 math optional maxima_5.9.1-10.diff.gz
 82c5da797940daff2a898545cc3c6bd5 1126144 math optional 
maxima-src_5.9.1-10_all.deb
 fea8abb5309fcb57dd3ddaea59c834ff 44706 math optional 
maxima-test_5.9.1-10_all.deb
 f09bb7b2da961e2e7ed742c3d16eec0e 5520792 math optional 
maxima-doc_5.9.1-10_all.deb
 2d2644e382268c275a8df1e108e2e888 90410 math optional 
maxima-emacs_5.9.1-10_all.deb
 fec9328f79439c67c582b00d70634eea 2267508 math optional 
maxima-share_5.9.1-10_all.deb
 521e089a8255b5e462641b956288660d 7526240 math optional maxima_5.9.1-10_i386.deb
 e926447c1a6d5dc647bd761b204a0520 190366 math optional xmaxima_5.9.1-10_i386.deb

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

iD8DBQFDMYvCczG1wFfwRdwRAjK5AJ94DysxX+St5aOSl8wwx4AXlWny+gCglS0T
Vl1A/6yvzle4wq0r3Candbc=
=BzWJ
-END PGP SIGNATURE-


Accepted:
maxima-doc_5.9.1-10_all.deb
  to pool/main/m/maxima/maxima-doc_5.9.1-10_all.deb
maxima-emacs_5.9.1-10_all.deb
  to pool/main/m/maxima/maxima-emacs_5.9.1-10_all.deb
maxima-share_5.9.1-10_all.deb
  to pool/main/m/maxima/maxima-share_5.9.1-10_all.deb
maxima-src_5.9.1-10_all.deb
  to pool/main/m/maxima/maxima-src_5.9.1-10_all.deb
maxima-test_5.9.1-10_all.deb
  to pool/main/m/maxima/maxima-test_5.9.1-10_all.deb
maxima_5.9.1-10.diff.gz
  to pool/main/m/maxima/maxima_5.9.1-10.diff.gz
maxima_5.9.1-10.dsc
  to pool/main/m/maxima/maxima_5.9.1-10.dsc
maxima_5.9.1-10_i386.deb
  to pool/main/m/maxima/maxima_5.9.1-10_i386.deb
xmaxima_5.9.1-10_i386.deb
  to pool/main/m/maxima/xmaxima_5.9.1-10_i386.deb


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

Accepted base-installer 1.30 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 18:39:59 +0200
Source: base-installer
Binary: base-installer
Architecture: source i386
Version: 1.30
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team debian-boot@lists.debian.org
Changed-By: Joey Hess [EMAIL PROTECTED]
Description: 
 base-installer - Install the base system (udeb)
Closes: 329391
Changes: 
 base-installer (1.30) unstable; urgency=low
 .
   * Switch i386 and ia64 to use linux-image-2.6-foo for
 base-installer/kernel/image-2.6. Now that debian-cd always includes these
 packages, this should be safe to do. On i386 this solves the issue of
 base-installer failing to install linux-image-2.6-686 as it is not
 on the netinst CD, and then falling back to linux-image-2.6.12-686 which
 was the previous default value. With the new default the installed system
 will properly track minor kernel revisions automatically.
   * Deal with similar issues on amd64.
   * Fix name of base-installer/kernel/linux/link_in_boot. Closes: #329391
 .
   * Updated translations:
 - Greek, Modern (1453-) (el.po) by Greek Translation Team
 - Galician (gl.po) by Jacobo Tarrio
 - Dutch (nl.po) by Frans Pop
Files: 
 900d0da1fcaed6ed5414e551b26c69a4 777 debian-installer required 
base-installer_1.30.dsc
 cf066de3070348409c7f7faa83156099 144788 debian-installer required 
base-installer_1.30.tar.gz
 c4ab332c3db23651d150a3d39af2c4c0 80062 debian-installer required 
base-installer_1.30_i386.udeb
Package-Type: udeb

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

iD8DBQFDMY8e2tp5zXiKP0wRAtJeAKCjpeNS9PeWMHPLLndF9rSnaRQ6NQCeM7Ky
asyBAnkohV97Ft4ICB7Bav0=
=DOW4
-END PGP SIGNATURE-


Accepted:
base-installer_1.30.dsc
  to pool/main/b/base-installer/base-installer_1.30.dsc
base-installer_1.30.tar.gz
  to pool/main/b/base-installer/base-installer_1.30.tar.gz
base-installer_1.30_i386.udeb
  to pool/main/b/base-installer/base-installer_1.30_i386.udeb


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

Accepted arc 5.21m-1 (source i386)

2005-09-21 Thread Klaus Reimer

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 18:28:00 +0100
Source: arc
Binary: arc
Architecture: source i386
Version: 5.21m-1
Distribution: unstable
Urgency: high
Maintainer: Klaus Reimer [EMAIL PROTECTED]
Changed-By: Klaus Reimer [EMAIL PROTECTED]
Description: 
 arc- Archive utility based on the MSDOS ARC program
Closes: 329053
Changes: 
 arc (5.21m-1) unstable; urgency=high
 .
   * New upstream release
   * Fixed insecure permissions of a temporary file [arcsvc.c,
 CAN-2005-2945] (Closes: #329053)
   * Fixed insecure temporary file creation [arcsvc.c, CAN-2005-2992]
Files: 
 1d9c6dff296e49959ad4f3ea246109fa 540 utils optional arc_5.21m-1.dsc
 3af4a95c608dd56cc9d64f3e0a300614 82350 utils optional arc_5.21m.orig.tar.gz
 07634c2b830b82965e91ae7d2b817c4c 2986 utils optional arc_5.21m-1.diff.gz
 7e267a9debb1990da0c0087f1718a3bf 55976 utils optional arc_5.21m-1_i386.deb

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

iD8DBQFDMY6QqgNhc6cj45ERAi0/AJ4wDqIWl1ddPZAqVGgfq51HU5hs7ACfZZrj
CyFVFCjGWixx3IGVYQs1tmQ=
=59t9
-END PGP SIGNATURE-


Accepted:
arc_5.21m-1.diff.gz
  to pool/main/a/arc/arc_5.21m-1.diff.gz
arc_5.21m-1.dsc
  to pool/main/a/arc/arc_5.21m-1.dsc
arc_5.21m-1_i386.deb
  to pool/main/a/arc/arc_5.21m-1_i386.deb
arc_5.21m.orig.tar.gz
  to pool/main/a/arc/arc_5.21m.orig.tar.gz


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

Accepted jackbeat 0.5.3-1 (source powerpc)

2005-09-21 Thread Paul Brossier

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 19 Sep 2005 13:51:50 +0100
Source: jackbeat
Binary: jackbeat
Architecture: source powerpc
Version: 0.5.3-1
Distribution: unstable
Urgency: low
Maintainer: Guillaume Pellerin [EMAIL PROTECTED]
Changed-By: Paul Brossier [EMAIL PROTECTED]
Description: 
 jackbeat   - a drummachine-like audio sequencer with JACK support
Changes: 
 jackbeat (0.5.3-1) unstable; urgency=low
 .
   * New upstream release
Files: 
 50eba5f8ee75854c05c8f5a253eb8f2a 796 sound optional jackbeat_0.5.3-1.dsc
 e3415fb8e9b691f88424598bda06a1ac 325110 sound optional 
jackbeat_0.5.3.orig.tar.gz
 14f2b4740d7dadb5a8e7e78fd8a42087 19784 sound optional jackbeat_0.5.3-1.diff.gz
 c47a803a9143e62a4987016193b6e8c9 52626 sound optional 
jackbeat_0.5.3-1_powerpc.deb

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

iD8DBQFDMZRJ2PLmgVuXpdIRAqBEAJ95BDQpGaxSKAT25rAm++aaSllrOACdFevu
o80nIASXCSb8dj7FAe3xIOU=
=HIKY
-END PGP SIGNATURE-


Accepted:
jackbeat_0.5.3-1.diff.gz
  to pool/main/j/jackbeat/jackbeat_0.5.3-1.diff.gz
jackbeat_0.5.3-1.dsc
  to pool/main/j/jackbeat/jackbeat_0.5.3-1.dsc
jackbeat_0.5.3-1_powerpc.deb
  to pool/main/j/jackbeat/jackbeat_0.5.3-1_powerpc.deb
jackbeat_0.5.3.orig.tar.gz
  to pool/main/j/jackbeat/jackbeat_0.5.3.orig.tar.gz


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

Accepted apt-zip 0.13.5 (source all)

2005-09-21 Thread Giacomo Catenazzi

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 21 Sep 2005 09:04:14 +0200
Source: apt-zip
Binary: apt-zip
Architecture: source all
Version: 0.13.5
Distribution: unstable
Urgency: low
Maintainer: Giacomo Catenazzi [EMAIL PROTECTED]
Changed-By: Giacomo Catenazzi [EMAIL PROTECTED]
Description: 
 apt-zip- Update a non-networked computer using apt and removable media
Closes: 319887 326946
Changes: 
 apt-zip (0.13.5) unstable; urgency=low
 .
   [ Giacomo Catenazzi ]
   * Correct an other bug. And this time I tested more. (closes: #326946)
   * apt-zip-inst now find the apt-zip.options file!
 .
   [ Eddy PetriÈor ] (closes: #319887)
   * relative paths for mount points are now supported
   * fixed broken formating in generated scripts
   * the download size is exact, not aproximative
   * added aptitude-update method in the TODO list
   * added more space protections, where necessary
   * updated copyright owners list
Files: 
 3b7e2df2d59a45bc3f001633a83f915e 513 admin extra apt-zip_0.13.5.dsc
 c2e88af997f5a7988c8185849ca65c43 14260 admin extra apt-zip_0.13.5.tar.gz
 2fc93a4d55159c63b1007386c0496361 15286 admin extra apt-zip_0.13.5_all.deb

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

iD8DBQFDMZcK+ZNUJLHfmlcRAgzAAJ0bstm/7WuXXHrDrTH+9PmtvDfNowCeMZe5
yVgVfI8AwveyXWjwmGjXQXU=
=FwMl
-END PGP SIGNATURE-


Accepted:
apt-zip_0.13.5.dsc
  to pool/main/a/apt-zip/apt-zip_0.13.5.dsc
apt-zip_0.13.5.tar.gz
  to pool/main/a/apt-zip/apt-zip_0.13.5.tar.gz
apt-zip_0.13.5_all.deb
  to pool/main/a/apt-zip/apt-zip_0.13.5_all.deb


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

Accepted bogl 0.1.18-1.2 (source i386)