date:20030921

also sprach Matthew Garrett [EMAIL PROTECTED] [2003.09.21.1614 +0200]:
 FWIW, I basically agree. goodies are welcome, but backporting
 things from the unstable branch migh= t not be that good idea.
 
 Should we stop shipping security fixes backported from development
 code?

It always depends, doesn't it? We are backporting *security* fixes
to packages, but we take care not to introduce new features. I don't
oppose some small modifications to the kernel, fixes and security
backports, but including a 2.5 IPsec stack in 2.4.21 is kinda not in
accordance with that policy, now is it?

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpM0WSZYEzOX.pgp
Description: PGP signature

Re: Debian should not modify the kernels!

also sprach Mark Brown [EMAIL PROTECTED] [2003.09.21.1644 +0200]:
 This is very standard practice for distribution kernels.  It's
 fairly rare for users to notice negative effects and the positive
 effects (better hardware support, more features, better
 performance or what have we) are generally seen to be worthwhile.

... in addition to possibly more bugs and the inability of
interaction with the kernel and the rest of the world. linux-kernel
can not help you anymore, as you don't run the linux kernel anymore,
and third-party software may just fail.

I am not saying that all this shouldn't happen. I am just saying it
shouldn't be the default. Debian is about choice, isn't it? Well,
opt-in choice it should be!

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpQ6krB4s05F.pgp
Description: PGP signature

Re: Debian should not modify the kernels!

also sprach Domenico Andreoli [EMAIL PROTECTED] [2003.09.21.1647 +0200]:
 which features should be removed from grsec in order to make it
 patch the debian kernel?

IP randomisation, and there might well me more. This is where
I stopped.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpUoAAuYMa2b.pgp
Description: PGP signature

Bug#211991: ITP: libcamomile-ocaml-dev -- Unicode for OCaml

2003-09-21 Thread Sylvain LE GALL

Package: wnpp
Version: unavailable; reported 2003-09-21
Severity: wishlist


* Package name: libcamomile-ocaml-dev
  Version : 0.4.1
  Upstream Author : Yamagata Yoriyuki [EMAIL PROTECTED]
* URL : http://camomile.sourceforge.net/
* License : LGPL
  Description : Unicode for OCaml

Camomile is a comprehensive Unicode library for OCaml

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux grand 2.4.22 #3 sam sep 13 02:31:10 CEST 2003 i686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

Re: Debian should not modify the kernels!

2003-09-21 Thread John Hasler

Andi writes:
 I hope that you're joking. (Well, I fear that you're not.)

It's not the American audience that has the limited vocabulary.  It's the
American publisher.
-- 
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI

Fw: coIIege naive girIs ready for H/\RD /\CTlON jBk LwO N F oV ZRE Akwya

2003-09-21 Thread Pybofob

Title: ctzgu DI


things do happen.  world OFFBEAT Open your
ïðèâåò in 1929 AtQ and make them better?XOpJ nlTNKLw the blackout Lovely day
Religion divides  in 1831  First or standart class? in 1953 It's nice

Fw: coIIege naive girIs ready for H/\RD /\CTlON Abt KNn Z z EH NqH fcBBd

2003-09-21 Thread Pawisuhov

Title: mKpTo MZ


in 1906  Small world! in 1845
Don't get excited! to sign here qJU in 1888 vagx tbTtTUg Take it easy! the U.S. 
by seat When is the next?  Real bad. in 1850 in 1948

Re: Horrific new levels of changelog abuse

On Sun, Sep 21, 2003 at 04:18:10PM +1000, Herbert Xu wrote:

 Matt Zimmerman [EMAIL PROTECTED] wrote:
 
  I think I do understand your position; I simply disagree.  I feel that
  changes which close Debian bugs should be documented in debian/changelog
  whether or not they are Debian-specific changes, because:
  
  - The bug submitter should receive a reasonable explanation for the bug's
closure in the -done message
 
 Well can you please give an operable definition of what a reasonable
 explanation is?

A reasonable explanation includes enough information for:

- the submitter to recognize that their bug was in fact fixed

- a user to be able to read the changelog, with an idea of the bug in his
  head, and find where it was fixed.  For example, a stable user reading an
  unstable changelog to see if a bug affecting him is fixed

- a developer to be able to determine what version of the package he needs
  to depend on if he requires a certain fix which was requested through the
  BTS

- the changelog to stand on its own, and be useful without digging through
  the BTS

 I've read a number of closure messages on bugs of your packages, and
 they really coveyed no more information than a message which simply
 said that the bug is fixed in version x.

Can you provide an example?  The rootstrap example you gave certainly
provided more information than bug # was fixed; it documented the
addition of a feature which justified the closure of the bug.

  - Other Debian packages may be affected by the bug, requiring versioned
dependencies
 
 This is irrelevant unless we start putting all closures in debian/changelog.
 Otherwise you miss out on all bugs closed manually.
 
 Although this is a worthy goal, it should be addressed in the BTS and
 not debian/changelog.

My position on changelogs is completely unrelated to the BTS, because I
think that the changelog should stand on its own, documenting all changes to
the package which are considered relevant to Debian.

For example, if I am aware of an upstream bug which I think may be troubling
Debian users, and it is fixed in a new upstream release, I do not hesitate
to note this fact in the changelog.

It just happens that, to me, a Debian bug report is solid justification that
information about the fix is relevant to Debian.  This seems self-evident to
me.

  - The fact that the bug was reported to the Debian BTS means that the bug
(and hence the fix) is relevant to Debian users and deveopers
 
 I'm afraid I don't follow your logic on this point.  There is a lot
 of information that is relevant to Debian users and developers, that
 is no reason for them to end up in debian/changelog.

I certainly did not suggest that all information that is relevant to Debian
users and developers should be in the changelog.

I do feel strongly that changes in the package which are relevant to Debian
users and developers, whether they happen to be in the debian/ directory or
not, should be documented in debian/changelog.

-- 
 - mdz

Bug#211996: ITP: liblivejournal-perl -- Perl implementation of the LiveJournal protocol

2003-09-21 Thread Decklin Foster

Package: wnpp
Version: unavailable; reported 2003-09-21
Severity: wishlist


* Package name: liblivejournal-perl
  Version : 1.3
  Upstream Author : Frank Sheiness [EMAIL PROTECTED]
* URL : http://www.livejournal.com/files/code/lib/perl/LiveJournal/
* License : Artistic
  Description : Perl implementation of the LiveJournal protocol

 This module is implements the LiveJournal protocol. See
 http://www.livejournal.com/developer/protocol.bml for details. Data
 is requested from the server through mode lines. Many methods return
 a hash reference containing key/value pairs returned by the server.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux terminus 2.4.22 #1 SMP Thu Sep 18 12:25:09 EDT 2003 i686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Re: Horrific new levels of changelog abuse

On Sun, Sep 21, 2003 at 11:00:14AM +0200, Thomas Hood wrote:

 On Sun, 2003-09-21 at 10:21, Herbert Xu wrote:
  The only disagreement is with what to do with upstream changes that
  happen to close Debian bugs.
 
 Is there any chance of everyone agreeing to leave it up to the
 maintainer to decide whether or not to document such changes
 in the Debian changelog?  A big advantage of such an agreement
 would be that it would reduce the amount of time wasted on
 discussions like this one.

You could submit the same argument about the Debian Policy Manual, and half
of the other discussions on the mailing lists.  There is value in having
consistent practices for maintainers.

-- 
 - mdz

Re: Horrific new levels of changelog abuse

On Sun, Sep 21, 2003 at 02:56:35AM -0400, Glenn Maynard wrote:

 On Sat, Sep 20, 2003 at 05:38:50PM -0500, Adam Heath wrote:
   As far as the BTS is concerned, it is irrelevant how a bug is fixed.
  
  Wrong.  The BTS is a front-end to users.  When bugs are closed, the
  submitter(a normal user) is notified.  This notification *must* include
  a user-oriented response.  This is fixed is not such a response.
 
 Speaking as a user, that's fine with me.  All I care about is that it was
 fixed; as a user, I couldn't care less *how* it was fixed.  It's
 irrelevant to me.
 
 Doesn't crash when --foo is used is not any more useful to me--the
 summary line of the bug is included with the acknowledgement mail, so
 that's redundant to me most of the time.  (Of course, it may be more
 useful to others, but it seems we're talking about the BTS side of things
 here, not the changelog side.)

Your position overlooks the fact that you are most likely not the only user
of the package, nor the only user affected by the bug.

 Also, bug 12345 fixed is not useless; it'd be convenient if I want to
 find out in which version fixed a given bug.

It is practically useless.  If you already have the bug number, then you
probably got it from the BTS, and the BTS will already contain enough
information for you to determine in which version the bug was closed.

-- 
 - mdz

Re: Request for APT :: Preferences

On Sun, Sep 21, 2003 at 01:07:20PM +0200, JL wrote:

 Would it be possible (if a sensible question at all) to include a
 feature into apt wich generates an /etc/apt/preferences.db file wich
 would include any information required to build the preferences file ?

I do not understand your question.  What information would be stored in this
hypothetical preferences.db file, and what sort of preferences file would it
generate?

-- 
 - mdz

[OT] American version of Harry Potter (Was: Debian should not modify the kernels!)

2003-09-21 Thread Lukas Geyer

Russell Coker [EMAIL PROTECTED] writes:

 Bad analogy.  Consider the way that the Harry Potter books have been
 modified for the limited vocabulary of the American audience.

Ha, the Australians want American kids to read sentences like Fred
and I managed to keep our peckers up somehow. (In the American
edition peckers was changed to spirits.) Be aware that the current
administration and Fox News might view this as an act of war...

Lukas

Re: Debian should not modify the kernels!

2003-09-21 Thread Marc Wilson

On Mon, Sep 22, 2003 at 12:07:18AM +1000, Russell Coker wrote:
 Bad analogy.  Consider the way that the Harry Potter books have been modified 
 for the limited vocabulary of the American audience.

You mean they were even worse before they were published in the US?  Hard
to believe.

-- 
 Marc Wilson | What use is magic if it can't save a unicorn?  --
 [EMAIL PROTECTED] | Peter S. Beagle, The Last Unicorn

To what extent should Debian modify the kernel? (Re: Debian should not modify the kernels!)

On Sun, Sep 21, 2003 at 09:41:41PM +1000, Herbert Xu wrote:

 I've got a few points for you:
 
 * The vanilla kernel source is readily available:
 
 apt-get install kernel-source-2.4.22 kernel-patch-debian-2.4.22
 tar xjf /usr/src/kernel-source-2.4.22.tar.bz2
 cd kernel-source-2.4.22
 /usr/src/kernel-patches/all/2.4.22/unpatch/debian
 
 * The IPSEC backport can be easily reversed by unapplying
 the patches given in the README.Debian file.
 
 * The IPSEC backport has minimal effect on the binary images.  It
 has no effect unless you load the relevant modules.  The increase
 in size is tiny compared to the increases brought on by ACPI and
 compiler changes.  

Let me say first that I very much appreciate having IPsec available in
2.4.x.  This feature is important to me, as is the relative stability of
2.4.x kernels.  However, it does require that I either maintain
modifications to the UML patch so that it applies cleanly (which is what I
currently do), or revert the entire Debian kernel patch (which otherwise
causes no problems for my patch packages).

So, I'm curious why you chose to make it a part of the Debian kernel source,
rather than a separate patch (kernel-patch-ipsec or such).

I suppose the more fundamental question is, what is your vision for the
Debian kernel source?  What do you feel belongs there, and what does not?

-- 
 - mdz

To what extent should Debian modify the kernel? (Re: Debian should not modify the kernels!)

On Sun, Sep 21, 2003 at 03:54:15PM +0200, martin f krafft wrote:

 I run vanilla sources anyhow, so I am not too concerned as a user.  But as
 a maintainer of a kernel patch, I am not willing to modify the source to
 make it fit the inofficial kernel Debian provides. If I were to do so, I'd
 have to lessen the package's value by removing features, which I am sure
 is not going to be approved by upstream.

Why would you have to remove features?  I routinely modify my patch packages
to apply to Debian kernel source, and this has never required removing a
feature.

 I don't see why we don't provide kernel-source packages that feature the
 normal kernels

One good reason is that the normal kernels do not meet the DFSG.  Another is
that they often contain known security vulnerabilities, and it would be
irresponsible to distribute them that way.

-- 
 - mdz

Re: Debian should not modify the kernels!

On Mon, Sep 22, 2003 at 12:07:18AM +1000, Russell Coker wrote:

 Also there's the issue of whether we should try to have one kernel source
 tree that everything applies to.  I think that perhaps we should have
 options as to which tree things apply to.  So we can have kernel patches
 to apply against the kernel.org kernel, we can have patches to apply
 against Herbert's kernel (the official Debian kernel), and maybe we can
 include the Red Hat kernel in Debian and have patches against it too.

While I think it would be nice to have some of the third-party kernels
available in Debian, I think that in the case of kernel patch packages, this
creates more problems than it solves.  If there is no One True Kernel to
which patches should apply, then each maintainer may make a different
decision as to which kernel they support (probably the one that they use
themselves), and then a user's chances of being able to build a kernel which
includes all of the patches that he wants is drastically reduced (the
maintainer must choose to support his kernel in each case).

-- 
 - mdz

Re: propose new virtual package: libxaw-dev

2003-09-21 Thread Branden Robinson

[Followups set.]

On Thu, Sep 18, 2003 at 09:00:03PM -0500, Craig P. Steffen wrote:
 I am prospective DD; as one of my opening packages, I intend to adopt the 
 sound file editor xwave.  One of the bugs against it, 170005, says that 
 depending on the virtual package libxaw-dev is wrong.  
 
 However, reading the debian policy manual sections 3.6 and 7.4, it seems to 
 me to be a perfectly reasonable thing to do.  The real packages libxaw6-dev 
 and libxaw7-dev exist, and are listed as Providing libxaw-dev.  The only 
 other thing that the policy manuals suggest is that virtual packages be 
 mentioned in the virtual-packages-name-list.txt.  
 
 So I propose that libxaw-dev be added to that list.

I disagree; instead, I'm going to kill off libxaw-dev.

My decision to use the libxaw-dev virtual package in the first place
appears to date back to the time when we had multiple implementations of
the Athena library (NeXTaw, Xaw95, and Xaw3D).  The -dev packages for
these implementations could not coexist with each other, nor with
libXaw6's -dev package, because all of them tried to provide
/usr/X11R6/lib/libXaw.so for compile-time linking.

This is no longer a problem.  NeXTaw and Xaw95 have been withdrawn from
the distribution, and Xaw3D now uses the shared object name libXaw3d.

The only two packages that will collide with each other now are
libxaw6-dev and libxaw7-dev, both of which are under my control.  A
virtual package is not needed to coordinate between two packages I
maintain.

Thanks for bringing this to my attention.

-- 
G. Branden Robinson| I suspect Linus wrote that in a
Debian GNU/Linux   | complicated way only to be able to
[EMAIL PROTECTED] | have that comment in there.
http://people.debian.org/~branden/ | -- Lars Wirzenius


signature.asc
Description: Digital signature

Re: Horrific new levels of changelog abuse

2003-09-21 Thread Bernd Eckenfels

On Sun, Sep 21, 2003 at 11:55:37AM +0100, Mark Brown wrote:
 Simply saying that the bug was fixed in the new upstream release doesn't
 tell the user why

Why a bug wa gixed is obvious, because it was a bug.

- XXX does nt delete temp file
- Fixed in new upstream release

I mean, hell this is not hard to understand.

Greetings
Bernd
-- 
  (OO)  -- [EMAIL PROTECTED] --
 ( .. )  [EMAIL PROTECTED],linux.de,debian.org} http://home.pages.de/~eckes/
  o--o *plush*  2048/93600EFD  [EMAIL PROTECTED]  +497257930613  BE5-RIPE
(OO)  When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!

Re: [OT] American version of Harry Potter (Was: Debian should not modify the kernels!)

2003-09-21 Thread Branden Robinson

On Sun, Sep 21, 2003 at 12:44:59PM -0400, Lukas Geyer wrote:
 Ha, the Australians want American kids to read sentences like Fred
 and I managed to keep our peckers up somehow.

At least from puberty until middle age, that doesn't seem too impressive
a feat for most males...

-- 
G. Branden Robinson| There's nothing an agnostic can't
Debian GNU/Linux   | do if he doesn't know whether he
[EMAIL PROTECTED] | believes in it or not.
http://people.debian.org/~branden/ | -- Graham Chapman


signature.asc
Description: Digital signature

Re: Debian should not modify the kernels!

2003-09-21 Thread Sebastian

I have been following the discussion and just want to add some things
from a user's point of view:

1.
I appreciate the additional functionality and included bug fixes of the
Debian kernels, but in the end I often have to use the vanilla kernel,
because most patches - like grsecurity - don't apply otherwise.

2.
In the past, there was a problem with security fixes regarding the linux
kernel and stable distribution (woody). Only recently the security team
started to backport security fixes for the kernel versions included in
stable. Additionally, for most modern hardware a more recent kernel
release is needed. Thus I need to fetch newer kernel releases from
unstable or from kernel.org (and hope that they will work with woody),
and I have to look for security issues by myself.

Thus, while I really like the stability of woody, I frequently need
kernel updates. This means that the kernel packages don't really fit
into Debian's concept of stable and unstable.


As a user, I really would prefer a second set of current kernel-sources
and kernel-images that can be used to update a woody system and that
promises the same level of stability as woody does in general. These
kernels should thus be tested with woody and only include the vanilla
kernels plus important bugfixes, but no additional features.

Sebastian

Re: Debian should not modify the kernels!

On Sun, Sep 21, 2003 at 07:09:55PM +0200, Sebastian wrote:

 Thus, while I really like the stability of woody, I frequently need
 kernel updates. This means that the kernel packages don't really fit into
 Debian's concept of stable and unstable.

Debian's concept of stable and unstable applies equally to the kernel as
with any other package.  Under certain circumstances, users require newer
versions of certain software.

 As a user, I really would prefer a second set of current kernel-sources
 and kernel-images that can be used to update a woody system and that
 promises the same level of stability as woody does in general. These
 kernels should thus be tested with woody and only include the vanilla
 kernels plus important bugfixes, but no additional features.

How is this different from the kernels in stable-security and
proposed-updates?

-- 
 - mdz

Debian policy about experimental ?

2003-09-21 Thread jjluza

Hi all,

I read this :
http://lists.debian.org/debian-devel-announce/2003/
debian-devel-announce-200308/msg00010.html

So we should put development packages (like cvs snapshot) in experimental, not 
in unstable. But there is a problem, and I don't find any solution to solve 
it. For example, let's take mozilla and mozilla-snapshot packages :
- the first one has a version number (1.4) higher than the second one 
(0.0)
- the second one is obviously more recent than the first one.

The announcement tells we should get out -snapshot from the name of the 
package, before puting it in experimental.
So there is no difference in the package name anymore.
So now, since cvs package version is 0.0.date, apt always ask for upgrading to 
an older version (the stable one : 1.4 for mozilla).

I'm right, or do I make a mistake ? If I'm right, What is the solution ?

Re: grsecurity bugs

2003-09-21 Thread Martin-Éric Racine

In-Reply-To=[EMAIL PROTECTED]Subject=Re:%20Re: Debian should not modify the 
kernels!

On Sun, 21 Sep 2003, martin f krafft wrote:
 I have uploaded a new version of grsecurity. However, it won't support
 Debian kernels 2.4.20 and up. README.2.4.2x in the package will tell you
 why. In addition:
 
   http://lists.debian.org/debian-devel/2003/debian-devel-200309/msg01133.html
 
 I am sorry if this inconveniences you. I don't have a choice, not only
 because I can't afford to put more time into this, but also because I am not
 going to remove functionality from grsecurity, which would be required to
 cater for the Debian kernels.
 
 Please complain to the kernel maintainer(s) if you don't like this.
 Or just use a vanilla kernel source tree.
X

On Sun, 21 Sep 2003 21:41:41 Herbert Xu wrote:

 martin f krafft [EMAIL PROTECTED] wrote:
  
  I am the kernel-patch-2.4-grsecurity maintainer, and I have been
  flooded with grave and important bugs ever since kernel version
  2.4.20, since grsecurity does not apply to these kernel versions
  anymore. It doesn't apply to the Debianised versions of these
  kernels anymore, it applies to the vanilla kernel just fine.

 I've got a few points for you:
 
 * The vanilla kernel source is readily available:

 apt-get install kernel-source-2.4.22 kernel-patch-debian-2.4.22
 tar xjf /usr/src/kernel-source-2.4.22.tar.bz2
 cd kernel-source-2.4.22
 /usr/src/kernel-patches/all/2.4.22/unpatch/debian

Stop the sarcasm, Herbert!  That is NOT the vanilla kernel!  

What's the friggin point of downloading a Debian kernel-source package (mostly
because we need the convenience of a make-kpkg ready tarball), only to end up
unpatching everything Debian has put it right away?  I might as well download
the upstream tarball from kernel.org myself and then make my own debian/ folder!
Then again, that would disqualify the whole point of having Debian kernel-source
packages.  Now, _that_ is really smart.  Not.


 * The IPSEC backport can be easily reversed by unapplying
 the patches given in the README.Debian file.

 * The IPSEC backport has minimal effect on the binary images.  It
 has no effect unless you load the relevant modules.  The increase
 in size is tiny compared to the increases brought on by ACPI and
 compiler changes.  

 So either get the people who're complaining to you to unapply the
 IPSEC patch, or fix your patch instead.

The whole point of having a stable branch (currently 2.4) is to guarantee that
people can have a _reliable_ kernel that they can trust will:

1) Behave in a predictable way that is consistant with previous releases from
the same branch (currently 2.4).

2) Remain consistant in terms of features and modus operandi, only bringing in
bugfixes between releases.

3) Can easily receive the most popular patches designed to apply to that branch.

4) When using Debian, that the said patch will apply as easily as downloading
the corresponding kernel-source-version and kernel-patch-version-foobar,
then running make-kpkg.

Herbert, What you are doing by backporting stuff from kernel 2.6, well beyond
the occasional backporting work that happens on the upstream vanilla kernel 2.4
branch, is _wrong_, because it breaks all 4 points and because it turns the job
of packaging well-known kernel patches into a full recoding chore, instead of
the simple Debian packaging job it ought to be.

Stop it. 

If you really want to have kernel 2.6 features, then go ahead and use that
kernel release and please have the decency of passing on the kernel-2.4
maintenance to someone else, right away.

-- 
Martin-Éric Racine
http://www.pp.fishpool.fi/~q-funk/

Re: Debian policy about experimental ?

2003-09-21 Thread Simon Law

On Sun, Sep 21, 2003 at 08:09:57PM +0200, jjluza wrote:
 The announcement tells we should get out -snapshot from the name of
 the package, before puting it in experimental.  So there is no
 difference in the package name anymore.  So now, since cvs package
 version is 0.0.date, apt always ask for upgrading to an older version
 (the stable one : 1.4 for mozilla).
 
 I'm right, or do I make a mistake ? If I'm right, What is the solution ?

Apt supports pinning.  See man apt_preferences for more details.

Simon

Re: grsecurity bugs

On Sun, Sep 21, 2003 at 08:31:36PM +0300, Martin-?ric Racine wrote:

 The whole point of having a stable branch (currently 2.4) is to guarantee that
 people can have a _reliable_ kernel that they can trust will:
 
 1) Behave in a predictable way that is consistant with previous releases from
 the same branch (currently 2.4).
 
 2) Remain consistant in terms of features and modus operandi, only bringing in
 bugfixes between releases.

Er...what 2.4 kernel are you talking about?  That doesn't sound like Linux
2.4 at all.

-- 
 - mdz

Re: Bug#211991: ITP: libcamomile-ocaml-dev -- Unicode for OCaml

2003-09-21 Thread Stefano Zacchiroli

On Sun, Sep 21, 2003 at 05:45:54PM +0200, Sylvain LE GALL wrote:
 * Package name: libcamomile-ocaml-dev

You should check carefully licensing issues of some unicode stuff
distributed inside the camomile tarball.

I've already had a chat with the author about that issue, I told me that
he should have clarified the issues with the Unicode people, but I've
never received any answer from him on that issue.

Cheers.

-- 
Stefano Zacchiroli  --  Master in Computer Science @ Uni. Bologna, Italy
[EMAIL PROTECTED],debian.org,bononia.it}  -  http://www.bononia.it/zack/
  I know you believe you understood what you think I said, but I am not
sure you realize that what you heard is not what I meant!   -- G.Romney


signature.asc
Description: Digital signature

Re: Debian should not modify the kernels!

2003-09-21 Thread Erik Steffl

Martin Michlmayr wrote:
* martin f krafft [EMAIL PROTECTED] [2003-09-21 14:44]:
What you distribute as 2.4.22 is not 2.4.22.

So what?  Most packages in Debian devate from upstream in one way or
another.  That's the added value we provide.  I'm happy that Herbert
carefully selects what to backport and I appreciate this effort.
(Also note that Red Hat modify the upstream kernel and libc in a quite
drastic way; in fact, their kernel is much more modified than ours).
  yeah, officer, he was speeding too...
  if I get kernel 2.4.22 as a debian package I expect kernel 2.4.22 as 
a debian package, not something else... any debian specific changes 
should result in kernel name change, that's what's expected in kernel 
world (when I get ac kernel I get 2.4.22-ac3)

  kernel is quite different from other packages - it is fairly often 
that people who get kernel source want to patch the kernel... I might 
not care that packageX is not vanilla packageX because it is VERY 
unlikely for me to even get the source for that package - the kernel is 
quite often customized (=recompiled locally).

erik

Re: To what extent should Debian modify the kernel? (Re: Debian should not modify the kernels!)

also sprach Matt Zimmerman [EMAIL PROTECTED] [2003.09.21.1906 +0200]:
 Why would you have to remove features?  I routinely modify my patch packages
 to apply to Debian kernel source, and this has never required removing a
 feature.

Because maybe you are a kernel hacker and have a clue. While I am
quite good with C, networking, and operating systems, I am not
willing to port grsecurity's changes to the official IP stack to
a 2.5 backport.

Moreover, I am not really willing to weed through 47 reject files
and apply everything by hand. The reason is not that I am lazy, but
because I am afraid to be introducing bugs.


  I don't see why we don't provide kernel-source packages that
  feature the normal kernels
 
 One good reason is that the normal kernels do not meet the DFSG.
 Another is that they often contain known security vulnerabilities,
 and it would be irresponsible to distribute them that way.

I fully agree that security vulnerabilities should be fixed by
backport. But not features!

Also, please explain: how is the normal kernel not DFSG but
a derived version is?

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpN88Hfbwk1N.pgp
Description: PGP signature

Re: auric down?

2003-09-21 Thread bcollins

On Sat, Sep 20, 2003 at 02:04:55AM +0200, Domenico Andreoli wrote:
 On Fri, Sep 19, 2003 at 04:19:55PM +0200, Andreas Metzler wrote:
  Hello,
  Am I having network problems or is ftp-master down?
 cu andreas
  
 it's up for me, but its key seems to be changed.

Auric and Vore are in Virginia, USA where a pretty good hurricane just
hit. I personally am still without power, and some areas wont get it
back for a few weeks. I know that visi.net has a backup generator, but
that doesn't help MAE-EAST and other POP's that may have also been in
the hurricane's path. Expect things to be ok soon.

Re: To what extent should Debian modify the kernel? (Re: Debian should not modify the kernels!)

also sprach Matt Zimmerman [EMAIL PROTECTED] [2003.09.21.1857 +0200]:
 So, I'm curious why you chose to make it a part of the Debian
 kernel source, rather than a separate patch (kernel-patch-ipsec or
 such).

Thanks, this is indeed the right questions.

And so is this:

 I suppose the more fundamental question is, what is your vision
 for the Debian kernel source?  What do you feel belongs there, and
 what does not?

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgp2luFxHyfK6.pgp
Description: PGP signature

Re: grsecurity bugs

also sprach Martin-?ric Racine [EMAIL PROTECTED] [2003.09.21.1931 +0200]:
 I might as well download the upstream tarball from kernel.org
 myself and then make my own debian/ folder!

No need. make-kpkg will create it.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpxwjzjToQtG.pgp
Description: PGP signature

Re: grsecurity bugs

also sprach Matt Zimmerman [EMAIL PROTECTED] [2003.09.21.2035 +0200]:
 Er...what 2.4 kernel are you talking about?  That doesn't sound
 like Linux 2.4 at all.

With respect to Debian packaging, it should. The fact that Linux
2.4 kernels osciallate features is irrelevant in this discussion,
because it applies to *all* Linux 2.4 kernels, be they vanilla,
Debian, RedHat or MattZimmermanSpecial.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpniZFj2tRyi.pgp
Description: PGP signature

Re: Debian policy about experimental ?

2003-09-21 Thread jjluza

Le Dimanche 21 Septembre 2003 20:14, Simon Law a écrit :
 On Sun, Sep 21, 2003 at 08:09:57PM +0200, jjluza wrote:
  The announcement tells we should get out -snapshot from the name of
  the package, before puting it in experimental.  So there is no
  difference in the package name anymore.  So now, since cvs package
  version is 0.0.date, apt always ask for upgrading to an older version
  (the stable one : 1.4 for mozilla).
 
  I'm right, or do I make a mistake ? If I'm right, What is the solution ?

   Apt supports pinning.  See man apt_preferences for more details.

 Simon


Yes, I know this solution, but in fact, I asked for a solution in debian 
policy, without needing to edit a file, what -snapshot allowed.
But maybe there is no other solution ?

Re: Debian policy about experimental ?

2003-09-21 Thread Santiago Vila

On Sun, 21 Sep 2003, jjluza wrote:

 I read this :
 http://lists.debian.org/debian-devel-announce/2003/
 debian-devel-announce-200308/msg00010.html

 So we should put development packages (like cvs snapshot) in experimental, not
 in unstable. But there is a problem, and I don't find any solution to solve
 it. For example, let's take mozilla and mozilla-snapshot packages :
 - the first one has a version number (1.4) higher than the second one
 (0.0)
 - the second one is obviously more recent than the first one.

 The announcement tells we should get out -snapshot from the name of the
 package, before puting it in experimental.
 So there is no difference in the package name anymore.
 So now, since cvs package version is 0.0.date, apt always ask for upgrading to
 an older version (the stable one : 1.4 for mozilla).

 I'm right, or do I make a mistake ? If I'm right, What is the solution ?

If the snaphots are betas for version 1.5, the solution is to give it
a version number like 2:1.4.20030921-1, so that whenever 1.5 is
officially released you can upload it to unstable as 2:1.5-1.

[ If the snapshots are betas for 1.4.1, use 2:1.4.0.20030921-1 instead, etc. ]

Re: To what extent should Debian modify the kernel? (Re: Debian should not modify the kernels!)

2003-09-21 Thread Christoph Hellwig

On Sun, Sep 21, 2003 at 09:11:29PM +0200, martin f krafft wrote:
  Why would you have to remove features?  I routinely modify my patch packages
  to apply to Debian kernel source, and this has never required removing a
  feature.
 
 Because maybe you are a kernel hacker and have a clue. While I am
 quite good with C, networking, and operating systems, I am not
 willing to port grsecurity's changes to the official IP stack to
 a 2.5 backport.

So you're maintaining a kernelpatch for debian that has sever security
implication but you don't know enough about it and the code it touches
to do some forward porting?

 Also, please explain: how is the normal kernel not DFSG but
 a derived version is?

Debian seems to have problems with certain firmware images.  Note
that the way it's removed in kernel-source is rather useless to meet
DFSG as it's a) still in the orig.tar.gz and b) many of the arch
kernel patches back out the removal of this code in the diff of
the kernel-source package again..

Re: [debian-i18n] i18n of man-db improved; please test

2003-09-21 Thread Marco d'Itri

On Sep 21, Colin Watson [EMAIL PROTECTED] wrote:

  Another bug I noticed is that in the ru_RU.UTF-8 locale, man won't
  find the man pages under ru_RU.KOI8-R.
 Hm. Yes, that is a bug (although not a regression; I think man-db
 2.4.1
 behaved the same way). I wonder how to solve that correctly and
 generally.
Why not require UTF-8 man pages? Maybe dh_installwhatever could recode
them on the fly when the package is built.

-- 
ciao, |
Marco | [1998 deCHVmpcOBDe.]

Re: Debian policy about experimental ?

2003-09-21 Thread Daniel Burrows

On Sun, Sep 21, 2003 at 10:01:40PM +0200, jjluza [EMAIL PROTECTED] was heard 
to say:
 Le Dimanche 21 Septembre 2003 20:14, Simon Law a écrit :
  On Sun, Sep 21, 2003 at 08:09:57PM +0200, jjluza wrote:
   The announcement tells we should get out -snapshot from the name of
   the package, before puting it in experimental.  So there is no
   difference in the package name anymore.  So now, since cvs package
   version is 0.0.date, apt always ask for upgrading to an older version
   (the stable one : 1.4 for mozilla).
  
   I'm right, or do I make a mistake ? If I'm right, What is the solution ?
 
  Apt supports pinning.  See man apt_preferences for more details.
 
  Simon
 
 
 Yes, I know this solution, but in fact, I asked for a solution in debian 
 policy, without needing to edit a file, what -snapshot allowed.
 But maybe there is no other solution ?

  Well, you could always make the snapshot's version larger than the
non-snapshot version.  I think some packages use stuff like 1.4+cvs0.0.date.
Then you get the reverse problem going from experimental to unstable, of
course..

  Daniel

-- 
/ Daniel Burrows [EMAIL PROTECTED] ---\
| Hmm, do I understand correctly that we've introduced a 1970 bug in |
|  order to move the 2038 bug to 2106?   |
|   -- Richard Braakman   |
\ Be like the kid in the movie!  Play chess! -- http://www.uschess.org ---/

Re: [debian-i18n] i18n of man-db improved; please test

2003-09-21 Thread Colin Watson

On Sun, Sep 21, 2003 at 10:46:28PM +0200, Marco d'Itri wrote:
 On Sep 21, Colin Watson [EMAIL PROTECTED] wrote:
  Rüdiger Kuhlmann wrote:
   Another bug I noticed is that in the ru_RU.UTF-8 locale, man won't
   find the man pages under ru_RU.KOI8-R.
  Hm. Yes, that is a bug (although not a regression; I think man-db
  2.4.1 behaved the same way). I wonder how to solve that correctly
  and generally.
 
 Why not require UTF-8 man pages? Maybe dh_installwhatever could recode
 them on the fly when the package is built.

I think that's an extremely bad idea until groff supports them.

-- 
Colin Watson  [EMAIL PROTECTED]

Bug#212046: ITP: libiox-ocaml-dev -- Framework for concurrent single-threaded network applications in OCaml

2003-09-21 Thread Sylvain LE GALL

Package: wnpp
Version: unavailable; reported 2003-09-21
Severity: wishlist


* Package name: libiox-ocaml-dev
  Version : 1.00b3
  Upstream Author : J.H. Woodyatt [EMAIL PROTECTED]
* URL : http://www.wetware.com/jhw/src/
* License : BSD-like
  Description : Framework for concurrent single-threaded network 
applications in OCaml

   The Iox library is a foundation layer for concurrent, single-threaded
  network application servers.  It comprises the following subsystems:
   
  + Modular event loop kernel.
  + Functional buffer-chained messages.
  + Flow-control mechanisms.
  + I/O reactor (for multiplexing network events).
  + Abstractions for reactive socket I/O.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux grand 2.4.22 #3 sam sep 13 02:31:10 CEST 2003 i686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

Re: Debian policy about experimental ?

2003-09-21 Thread jjluza

Le Dimanche 21 Septembre 2003 22:12, Santiago Vila a écrit :
 On Sun, 21 Sep 2003, jjluza wrote:
  I read this :
  http://lists.debian.org/debian-devel-announce/2003/
  debian-devel-announce-200308/msg00010.html
 
  So we should put development packages (like cvs snapshot) in
  experimental, not in unstable. But there is a problem, and I don't find
  any solution to solve it. For example, let's take mozilla and
  mozilla-snapshot packages : - the first one has a version number (1.4)
  higher than the second one (0.0)
  - the second one is obviously more recent than the first one.
 
  The announcement tells we should get out -snapshot from the name of the
  package, before puting it in experimental.
  So there is no difference in the package name anymore.
  So now, since cvs package version is 0.0.date, apt always ask for
  upgrading to an older version (the stable one : 1.4 for mozilla).
 
  I'm right, or do I make a mistake ? If I'm right, What is the solution ?

 If the snaphots are betas for version 1.5, the solution is to give it
 a version number like 2:1.4.20030921-1, so that whenever 1.5 is
 officially released you can upload it to unstable as 2:1.5-1.

 [ If the snapshots are betas for 1.4.1, use 2:1.4.0.20030921-1 instead,
 etc. ]

Le Dimanche 21 Septembre 2003 22:52, vous avez écrit :
 On Sun, Sep 21, 2003 at 10:01:40PM +0200, jjluza [EMAIL PROTECTED] was 
 heard 
to say:
  Le Dimanche 21 Septembre 2003 20:14, Simon Law a écrit :
   On Sun, Sep 21, 2003 at 08:09:57PM +0200, jjluza wrote:
The announcement tells we should get out -snapshot from the name of
the package, before puting it in experimental.  So there is no
difference in the package name anymore.  So now, since cvs package
version is 0.0.date, apt always ask for upgrading to an older version
(the stable one : 1.4 for mozilla).
   
I'm right, or do I make a mistake ? If I'm right, What is the
solution ?
  
 Apt supports pinning.  See man apt_preferences for more details.
  
   Simon
 
  Yes, I know this solution, but in fact, I asked for a solution in debian
  policy, without needing to edit a file, what -snapshot allowed.
  But maybe there is no other solution ?

   Well, you could always make the snapshot's version larger than the
 non-snapshot version.  I think some packages use stuff like
 1.4+cvs0.0.date. Then you get the reverse problem going from experimental
 to unstable, of course..

   Daniel


Yes ! I think you give me the better solution
I thought about a solution like 1.5+pre... but I were not convinced by the 
relevance of this solution.
So yours one are good : now I should decide if I put a '+' or a '.' ... wooh, 
difficult to choose. I think I'll use '+'

To Daniel : I don't think there is a problem to go from experimental to 
unstable since we need to use -t experimental with apt-get, when we want to 
install a package in it. So the problem is cleanly solved, I think.


JJ.

Re: Debian policy about experimental ?

2003-09-21 Thread Remi Vanicat

Santiago Vila [EMAIL PROTECTED] writes:

 If the snaphots are betas for version 1.5, the solution is to give it
 a version number like 2:1.4.20030921-1, so that whenever 1.5 is
 officially released you can upload it to unstable as 2:1.5-1.

 [ If the snapshots are betas for 1.4.1, use 2:1.4.0.20030921-1
 instead, etc. ]

Why use epoch ? 1.4.0.20030921-1 should work (or am i missing something
here ?)

epoch should only be used when needed...

-- 
Rémi Vanicat
[EMAIL PROTECTED]

Re: Debian policy about experimental ?

2003-09-21 Thread Mike Hommey

On Sunday 21 September 2003 23:10, Remi Vanicat wrote:
 Why use epoch ? 1.4.0.20030921-1 should work (or am i missing something
 here ?)

 epoch should only be used when needed...

and it is... since current mozilla package version is 2:1.4-4

Mike

-- 
I have sampled every language, french is my favorite. Fantastic language,
especially to curse with. Nom de dieu de putain de bordel de merde de
saloperie de connard d'enculé de ta mère. It's like wiping your ass
with silk! I love it. -- The Merovingian, in the Matrix Reloaded

Re: To what extent should Debian modify the kernel? (Re: Debian should not modify the kernels!)

On Sun, Sep 21, 2003 at 09:11:29PM +0200, martin f krafft wrote:

 Also, please explain: how is the normal kernel not DFSG but
 a derived version is?

See the bottom of /usr/share/doc/kernel-source-2.4.22/README.Debian.gz

-- 
 - mdz

Re: Horrific new levels of changelog abuse

2003-09-21 Thread Russ Allbery

Bernd Eckenfels [EMAIL PROTECTED] writes:

 Why a bug wa gixed is obvious, because it was a bug.

 - XXX does nt delete temp file
 - Fixed in new upstream release

 I mean, hell this is not hard to understand.

That's great if I knew what the bug was.  You seem to be assuming that the
only people who are interested in the resolution of a bug are the
submitter and people who regularly read the bug database for that package.
I may well have been encountering the same temp file problem and had just
not gotten around to reporting it.

This seems like a lot of argument over avoiding putting six more words
into the changelog file giving information that the maintainer clearly
already has (since otherwise they wouldn't know that they could close the
bug), and which is obviously useful for users.

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

Debian provide un-modified source for kernel-patch

2003-09-21 Thread Osamu Aoki

Hi,

Flame aside ... let's look at technical side.

On Sun, Sep 21, 2003 at 02:44:03PM +0200, martin f krafft wrote:
 also sprach Herbert Xu [EMAIL PROTECTED] [2003.09.21.1341 +0200]:
  * The vanilla kernel source is readily available:
 
 I don't consider this readily available. It's faster to just
 download it from kernel.org.

But that requires net connection.  You know we burn to CD as *stable* too.

 Plus: why do you make the backport default? Shouldn't users have the
 choice to apply the patch if they wish, rather than those that don't
 want it having to unpatch?

I am not an expert but I think you should try along what Herbert Xu
suggested which seems to give you very easy path to patch files.  I did
not know but looks very nice.

 $ apt-get install kernel-source-2.4.22 kernel-patch-debian-2.4.22
 $ tar xjf /usr/src/kernel-source-2.4.22.tar.bz2
 $ cd /usr/src/kernel-patch

There is a file /usr/src/kernel-patches/all/2.4.22/debian/list whose
content goes like:
-
# This file is sorted by patch dependency.  The patch which applies to the
# upstream kernel must come first.

patch-2.4.22-1  2.4.22  2.4.22-1
-

This seem to offer very good path to apply patch to the upstream kernel 
which must be applied first.  

Did you try using this?

Osamu

Re: To what extent should Debian modify the kernel? (Re: Debian should not modify the kernels!)

also sprach Christoph Hellwig [EMAIL PROTECTED] [2003.09.21.2301 +0200]:
 So you're maintaining a kernelpatch for debian that has sever security
 implication but you don't know enough about it and the code it touches
 to do some forward porting?

I know enough about it; I don't (yet) know enough about the 2.5/2.6
IPsec stack. Don't try to read into my lines what I didn't write.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpuuFD4LHUNa.pgp
Description: PGP signature

Bug#212028: apt-cache uses dependency backards

2003-09-21 Thread Daniel B.

Matt Zimmerman wrote:
 
 reassign 212028 general
 thanks
 
 On Sun, Sep 21, 2003 at 03:36:03PM -0400, Daniel B. wrote:
 
  apt-cache and its manual page uses the word dependency backwards.
  This error makes the documentation hard to understand.
 
 apt's documentation is consistent with everything else in Debian, including
 the policy manual.  I think it would be significantly more confusing for apt
 to deviate from that usage than from the particular definition you cited.

No, apt shouldn't deviate from the rest of Debian.  If other things are
wrong too, they should fixed too.

Also, note that eliminating incorrect and confusing usage of dependency
does not require using dependency it its correct sense as the replacement.
In fact, something like depended-on package would be much clearer to
start with and would be unambiguous.

Daniel
-- 
Daniel Barclay
[EMAIL PROTECTED]

Bug#212049: dependency used backwards

2003-09-21 Thread Daniel B.

Package: general
Version: n/a?

Debian seems to use the word dependency backwards a lot, making
things confusing and hard to understand.

Per the The American Heritage Dictionary (via
http://dictionary.reference.com/search?q=dependency), a dependency
is:
1. Dependence. 
2. Something dependent or subordinate. 
3. A territory under the jurisdiction of a state of
   which it does not form an integral part. 

Note the direction of sense 2:  If A depends on B, then A is a 
dependency (A is dependent on B).  B is _not_ a dependency of A.


In Debian (documentation, executable output, e-mail), uses of 
dependency in sense 1 are usually fine.

However, uses in sense 2 are usually backwards (see bugs 212028,
212013, and especially 212034, which also shows how weak an 
understanding some Debian developers have of the word).


Obviously, Debian documentation and tools (and developers) shouldn't 
use dependency backwards.  

(Well, that should be obvious, but if it isn't, consider the confusion
it generates.  Given the international nature of Debian, consider 
readers who aren't native speakers of English, trying to figure out
what dependency means in English and then trying to figure out what
Debian documentation/etc. is really saying.)


Since merely using dependency correctly would be ambiguous given
all the incorrect usage, Debian should probably refer to depended-on 
package (or library, etc., as the case may be).  That construct would 
be unambiguous and perfectly clear (and wouldn't be much longer than 
dependency).



Daniel
-- 
Daniel Barclay
[EMAIL PROTECTED]

Processed: Re: Bug#212028: apt-cache uses dependency backards

2003-09-21 Thread Debian Bug Tracking System

Processing commands for [EMAIL PROTECTED]:

 reassign 212028 general
Bug#212028: apt-cache  uses dependency backards 
Bug reassigned from package `apt' to `general'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Re: Debian should not modify the kernels!

2003-09-21 Thread Osamu Aoki

HI,

I have no issue how you ship debian kernel :-)

On Sun, Sep 21, 2003 at 09:41:41PM +1000, Herbert Xu wrote:
 I've got a few points for you:
 
 * The vanilla kernel source is readily available:

good.
 
 apt-get install kernel-source-2.4.22 kernel-patch-debian-2.4.22
 tar xjf /usr/src/kernel-source-2.4.22.tar.bz2
 cd kernel-source-2.4.22
 /usr/src/kernel-patches/all/2.4.22/unpatch/debian
 
 * The IPSEC backport can be easily reversed by unapplying
 the patches given in the README.Debian file.

  :-(

Can your patch file to be more modular like X package?  It is a big
chunk.

Osamu

Re: To what extent should Debian modify the kernel? (Re: Debian should not modify the kernels!)

On Sun, Sep 21, 2003 at 11:01:51PM +0200, Christoph Hellwig wrote:

 Debian seems to have problems with certain firmware images.  Note that the
 way it's removed in kernel-source is rather useless to meet DFSG as it's
 a) still in the orig.tar.gz and b) many of the arch kernel patches back
 out the removal of this code in the diff of the kernel-source package
 again..

Clearly you didn't check the source before stating this.

-- 
 - mdz

apt-get'able Release file format

2003-09-21 Thread Jeremy T. Bouse

In looking to try and setup pinning on a couple of my machines I went
looking at the Release files for the various sites I use... For the most
part I found them to have a similar suite of attributes to work from but
I did notice a difference betwen Components and Component and just
trying to figure out which is the correct one...

In my looking I check'd out http.us.debian.org, debian.seabone.net and
security.debian.org... The IPv6 repository was the one in question that
used Component while the others used the plural version... Although
obviously the values after it were plural in the case of the other or
does it not matter? I'm just trying to better understand it so I can
setup pinning myself personally but also to setup the apt-get'able
repositories I make use of...

Regards,
Jeremy


signature.asc
Description: Digital signature

Processed: merging 212028 212049

2003-09-21 Thread Debian Bug Tracking System

Processing commands for [EMAIL PROTECTED]:

 merge 212028 212049
Bug#212028: apt-cache  uses dependency backards 
Bug#212049: dependency used backwards
Merged 212028 212049.


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Re: Horrific new levels of changelog abuse

2003-09-21 Thread Kenneth Pronovici

 This seems like a lot of argument over avoiding putting six more words
 into the changelog file giving information that the maintainer clearly
 already has (since otherwise they wouldn't know that they could close the
 bug), and which is obviously useful for users.

Hear, hear.  

You can't tell me that it's so much more difficult to write:

   * New upstream release
 - Fix such-and-such behavior (closes: #)

instead of just:

   * New upstream release (closes: #)

The question in my mind is, if you can make some of your users and
fellow developers happier just by adding a few words of detail to your
changelog, why would you *not* do it?  What's the point?  Add the six
words and get on with life.

Sheesh.

KEN

-- 
Kenneth J. Pronovici [EMAIL PROTECTED]


pgp8xqIrEDcAe.pgp
Description: PGP signature

Re: apt-get'able Release file format

On Sun, Sep 21, 2003 at 03:53:00PM -0700, Jeremy T. Bouse wrote:

   In my looking I check'd out http.us.debian.org, debian.seabone.net and
 security.debian.org... The IPv6 repository was the one in question that
 used Component while the others used the plural version... Although
 obviously the values after it were plural in the case of the other or
 does it not matter? I'm just trying to better understand it so I can
 setup pinning myself personally but also to setup the apt-get'able
 repositories I make use of...

That sounds backwards.  Component is the one recognized by apt, and
(naturally) the one used by official Release files in the Debian archive.


-- 
 - mdz

Re: Maintaining kernel source in sarge

On Sun, 18 May 2003 20:32:05 -0400, Matt Zimmerman [EMAIL PROTECTED] said: 

 On Sun, May 18, 2003 at 12:06:21PM -0500, Manoj Srivastava wrote:
 There is also a mechanism to order the order in which
 kernel-patches are applied -- so if, say, a m68k kernel image
 maintainer wanted to create a patch relative to the i386 patches,
 they could depend on that patch, and order the m68k kernel-pacth to
 be applied later in the chain than the i386 patch.

 This dependency-and-ordering mechanism could be extended to third
 party modules.

 People interested in hammering out details of this mechanism, and
 kernel image maintainers, please contact me; perhaps it is time to
 create policy for kernel patches.

 dh-kpatches provides a dependency/ordering facility which has worked
 well for me in my packages.  It also provides
 /usr/share/doc/kernel-image-foo/applied-patches documenting the
 package and version for each patch that is applied.  I think this
 would be a good starting point for such a policy, since it is
 already being applied in Debian.

Is this dependency information easily accessible to external
 scripts? It is nice that the patch scripts themselves realize when a
 required patch has been installed or not, but it would work much
 better if the order in which these patches were applied could also be
 ordered nicely (so patches are applied in dependency order), and so
 that we can abort early (before anything was modified in the local
 sources) in case some dependencies have not been met.

So, is there a way that kernel-package can interface with this
 dependency/ordering facility? 

manoj
-- 
love, n.: When it's growing, you don't mind watering it with a few
tears.
Manoj Srivastava   [EMAIL PROTECTED]  http://www.debian.org/%7Esrivasta/
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Bug#212049: {Virus?} Latest Network Critical Update

2003-09-21 Thread MS Public Support

Warning: This message has had one
or more attachments removed. Please read the "VirusWarning.txt"
attachment(s) for more information.

Postmaster
Goldrush World Access
http://www.goldrush.com

Microsoft

All Products|
Support|
Search|

Microsoft.com Guide

Microsoft Home

Microsoft Consumer
this is the latest version of security update, the
"September 2003, Cumulative Patch" update which eliminates
all known security vulnerabilities affecting
MS Internet Explorer, MS Outlook and MS Outlook Express
as well as three newly discovered vulnerabilities.
Install now to continue keeping your computer secure
from these vulnerabilities, the most serious of which could
allow an attacker to run executable on your system.
This update includes the functionality of all previously released patches.

System requirements

Windows 95/98/Me/2000/NT/XP

This update applies to

MS Internet Explorer, version 4.01 and later
MS Outlook, version 8.00 and later
MS Outlook Express, version 4.01 and later

Recommendation
Customers should install the patch at the earliest opportunity.

How to install
Run attached file. Choose Yes on displayed dialog box.

How to use
You don't need to do anything after installing this item.

Microsoft Product Support Services and Knowledge Base articles
can be found on the Microsoft Technical Support web site. For security-related information about Microsoft products, please visit the
Microsoft Security Advisor web site, or Contact Us.

Thank you for using Microsoft products.
Please do not reply to this message. It was sent from an unmonitored e-mail address and we are unable to respond to any replies.

The names of the actual companies and products mentioned herein are the trademarks of their respective owners.

2003 Microsoft Corporation. All rights reserved.
Terms of Use
|

Privacy Statement|
Accessibility

This is a message from the MailScanner E-Mail Virus Protection Service
--
The original e-mail attachment Upgrade.exe
was believed to be infected by a virus and has been replaced by this warning
message.

Due to limitations placed on us by the Regulation of Investigatory Powers
Act 2000, we were unable to keep a copy of the infected attachment. Please
ask the sender of the message to disinfect their original version and send
you a clean copy.

At Sun Sep 21 16:57:22 2003 the virus scanner said:
Upgrade.exe Infection: W32/[EMAIL PROTECTED]

--
Postmaster
Goldrush World Access
http://www.goldrush.com

Re: Maintaining kernel source in sarge

On Sun, Sep 21, 2003 at 06:36:25PM -0500, Manoj Srivastava wrote:

 On Sun, 18 May 2003 20:32:05 -0400, Matt Zimmerman [EMAIL PROTECTED] said: 
  dh-kpatches provides a dependency/ordering facility which has worked
  well for me in my packages.  It also provides
  /usr/share/doc/kernel-image-foo/applied-patches documenting the
  package and version for each patch that is applied.  I think this
  would be a good starting point for such a policy, since it is
  already being applied in Debian.
 
   Is this dependency information easily accessible to external
  scripts? It is nice that the patch scripts themselves realize when a
  required patch has been installed or not, but it would work much
  better if the order in which these patches were applied could also be
  ordered nicely (so patches are applied in dependency order), and so
  that we can abort early (before anything was modified in the local
  sources) in case some dependencies have not been met.
 
   So, is there a way that kernel-package can interface with this
  dependency/ordering facility? 

As far as I know, there is no external interface (the dependency information
is stored in shell variables inside the script).

The scripts handle ordering by testing each dependency, and if it is not
already applied, invoking the corresponding apply script.  In this way, all
dependencies should be applied in proper order.  Rollback could presumably
be implemented by unapplying all patches if any patch fails (dh-kpatches
should now implement correct ordering for unapplication as well).

It may indeed make sense to move some of this logic into kernel-package, if
you are willing to do it.

-- 
 - mdz

http://202.103.7.45/www/909/

2003-09-21 Thread ggfttftf

debian-devel:!

ttp://202.103.7.45/www/909/


!
   
   [EMAIL PROTECTED]
   2003-10-23

Re: Maintaining kernel source in sarge

On Sun, 21 Sep 2003 20:12:26 -0400, Matt Zimmerman [EMAIL PROTECTED] said: 

 On Sun, Sep 21, 2003 at 06:36:25PM -0500, Manoj Srivastava wrote:
 On Sun, 18 May 2003 20:32:05 -0400, Matt Zimmerman [EMAIL PROTECTED]
 said:
  dh-kpatches provides a dependency/ordering facility which has
  worked well for me in my packages.  It also provides
  /usr/share/doc/kernel-image-foo/applied-patches documenting the
  package and version for each patch that is applied.  I think this
  would be a good starting point for such a policy, since it is
  already being applied in Debian.

 Is this dependency information easily accessible to external
 scripts? It is nice that the patch scripts themselves realize when
 a required patch has been installed or not, but it would work much
 better if the order in which these patches were applied could also
 be ordered nicely (so patches are applied in dependency order), and
 so that we can abort early (before anything was modified in the
 local sources) in case some dependencies have not been met.

 So, is there a way that kernel-package can interface with this
 dependency/ordering facility?

 As far as I know, there is no external interface (the dependency
 information is stored in shell variables inside the script).

 The scripts handle ordering by testing each dependency, and if it is
 not already applied, invoking the corresponding apply script.  In
 this way, all dependencies should be applied in proper order.
 Rollback could presumably be implemented by unapplying all patches
 if any patch fails (dh-kpatches should now implement correct
 ordering for unapplication as well).

Well, if I have asked for 5 patches to be applied (preempt,
 lowlatency, skas, device-mapper, lsm2, and debianlogo, in a recent
 invocation), the lsm2 script indeed failed -- but only after preempt,
 lowlatency, skas,  and device-mapper patches were applied (I did not
 have acl kernel-patch on the machine). It would have been nice to
 know about that before all the patches were applied. 


 It may indeed make sense to move some of this logic into
 kernel-package, if you are willing to do it.

I am always willing to improve my packages; the constraints
 are ability (I would need to grok the details of the current
 implementation), time, and collaboration (I would need to find out
 how to get a hook into the current patch dependency setup).

I would also like to incorporate conflict mechanisms -- so
 patch developers can give a hint about patches that are not
 compatible (the swsusp patches are incompatible with most other
 patches I wanted to apply).

Where do I start?

manoj
-- 
No proper program contains an indication which as an operator-applied
occurrence identifies an operator-defining occurrence which as an
indication-applied occurrence identifies an indication-defining
occurrence different from the one identified by the given indication
as an indication-applied occurrence. ALGOL 68 Report
Manoj Srivastava   [EMAIL PROTECTED]  http://www.debian.org/%7Esrivasta/
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Bug#212028: apt-cache uses dependency backards

2003-09-21 Thread Jason Gunthorpe


On Sun, 21 Sep 2003, Daniel B. wrote:

 Per the The American Heritage Dictionary (via
 http://dictionary.reference.com/search?q=dependency), a dependency
 is:
 ...
 2. Something dependent or subordinate. 
 ...
 
 That is, if A depends on B, A is a dependency of B.  (B is not a 
 dependency of A.)

 Definition #1 for Dependency is 'Dependence'. Which is defined as

   1. The state of being dependent, as for support.

So if package A requires some supporting functionality from package B then
'A has a dependence on B' - which is also correctly said as 'A has a
dependency for B'.

Consider a commonly heard phrase today: 'Jack depends on drugs', 'Jack has
a drug dependency', 'Jack is dependent on drugs', 'Jack has dependency on
drugs'. 'Package: jack\n Depends: drugs'. 

In this case, your example results in something very odd indeed -
'Jack is a dependency of drugs' but 'Drugs are not a dependency of Jack'
Which is clearly not the expected meaning of 'Jack depends on drugs'.

You might say 'Drugs are a dependency of Jack's' however..

Then again, I am not an English major.

Jason

Accepted defoma 0.11.5 (all source)

2003-09-21 Thread Angus Lees

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 13:26:56 +1000
Source: defoma
Binary: defoma dfontmgr defoma-doc psfontmgr
Architecture: source all
Version: 0.11.5
Distribution: unstable
Urgency: low
Maintainer: Angus Lees [EMAIL PROTECTED]
Changed-By: Angus Lees [EMAIL PROTECTED]
Description: 
 defoma - Debian Font Manager -- automatic font configuration framework
 defoma-doc - Debian Font Manager documentation
 dfontmgr   - GUI frontend for Defoma, DEbian FOnt MAnager
 psfontmgr  - PostScript font manager -- part of Defoma, Debian Font Manager
Closes: 94323 115642 207018 207675
Changes: 
 defoma (0.11.5) unstable; urgency=low
 .
   * Remove unused psfontmgr.templates.{de,fr}. Closes: #207675
   * Apply patch to allow defoma-hints to parse type1 files with different
 newline characters, thanks to Neil Schemenauer. Closes: #207018
   * Mention --no-question in defoma-hints manpage, helps #194106.
   * Support whiptail as well as dialog, using patch from YAMASHITA Junji.
 Closes: #94323
   * Defoma docs need updating, but they have a doc-base control file now.
 Closes: #115642
Files: 
 4a8ba4744dfa2e39990789118305f358 542 admin optional defoma_0.11.5.dsc
 f3504a827787e241ee6633fb3624e88d 137306 admin optional defoma_0.11.5.tar.gz
 191342f1bd9e034392048d042d225910 77702 admin optional defoma_0.11.5_all.deb
 004151283dbdb5b1de5052d61defbe94 60616 doc optional defoma-doc_0.11.5_all.deb
 fa86ba3aa2bce4da3bdb3d26cd10fa6c 20698 admin optional psfontmgr_0.11.5_all.deb
 ca64b7f2558a9a3324922c55343a4e91 40728 admin optional dfontmgr_0.11.5_all.deb

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

iD8DBQE/bUA9g//Ie9Avh3MRAn1/AJ9zP6pSjcyubKjJZBxB6tCWi1C6UQCfaVsc
qH9xy0q7QggoKMlixuJ+fs8=
=pbpI
-END PGP SIGNATURE-


Accepted:
defoma-doc_0.11.5_all.deb
  to pool/main/d/defoma/defoma-doc_0.11.5_all.deb
defoma_0.11.5.dsc
  to pool/main/d/defoma/defoma_0.11.5.dsc
defoma_0.11.5.tar.gz
  to pool/main/d/defoma/defoma_0.11.5.tar.gz
defoma_0.11.5_all.deb
  to pool/main/d/defoma/defoma_0.11.5_all.deb
dfontmgr_0.11.5_all.deb
  to pool/main/d/defoma/dfontmgr_0.11.5_all.deb
psfontmgr_0.11.5_all.deb
  to pool/main/d/defoma/psfontmgr_0.11.5_all.deb


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

Accepted a2ps 4.13b+cvs.2003.09.20-1 (i386 source)

2003-09-21 Thread Masayuki Hatta

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sat, 20 Sep 2003 18:51:32 +0900
Source: a2ps
Binary: a2ps
Architecture: source i386
Version: 4.13b+cvs.2003.09.20-1
Distribution: unstable
Urgency: low
Maintainer: Masayuki Hatta [EMAIL PROTECTED]
Changed-By: Masayuki Hatta [EMAIL PROTECTED]
Description: 
 a2ps   - GNU a2ps - 'Anything to PostScript' converter and pretty-printer
Closes: 39488 62053 113057 126436 143127 156077 185983 187178 188347 191372 193034 
194061 194464 195249 201887 201911 207612
Changes: 
 a2ps (4.13b+cvs.2003.09.20-1) unstable; urgency=low
 .
   * Basically test release - more will come soon.
   * New upstream release (CVS snapshot).
   * Acknowledged NMU - closes: #191372
   * Fixed in the upstream - closes: #156077, #143127, #185983, #195249, #126436, 
#62053, #113057
   * Added some Build-Depends - closes: #207612, #187178, #188347, #193034
   * Added Recommends: cupsys-client - closes: #194061
   * Added composeglyphs.1 manpage by Kevin Kreamer - closes: #39488
   * Ran bootstrap - closes: #201911
   * Patch#10 handles ISO-8859-5 correctly - closes: #201887
   * Patch#11 adds gnuplot support for ogonkify - closes: #194464
   * libpaper support is missing in the upstream.  I'll port it ASAP.
Files: 
 88a4176a820259ffc0e470dc5400657b 739 text optional a2ps_4.13b+cvs.2003.09.20-1.dsc
 b189b76bcce0729e568e4f19df1e1e36 2737391 text optional 
a2ps_4.13b+cvs.2003.09.20.orig.tar.gz
 420825d7c1de3070a37b1ccb041a0252 54112 text optional 
a2ps_4.13b+cvs.2003.09.20-1.diff.gz
 b6e003fc460d548ea349070d11c440fd 717644 text optional 
a2ps_4.13b+cvs.2003.09.20-1_i386.deb

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

iD8DBQE/bUY4vA5bJSX0Hx8RAtNkAJ91WutdoVs7/vdnYUFppuvznA6wdwCeJ/0u
hSqE7t37C3VDU5l5WzIHvxo=
=acMu
-END PGP SIGNATURE-


Accepted:
a2ps_4.13b+cvs.2003.09.20-1.diff.gz
  to pool/main/a/a2ps/a2ps_4.13b+cvs.2003.09.20-1.diff.gz
a2ps_4.13b+cvs.2003.09.20-1.dsc
  to pool/main/a/a2ps/a2ps_4.13b+cvs.2003.09.20-1.dsc
a2ps_4.13b+cvs.2003.09.20-1_i386.deb
  to pool/main/a/a2ps/a2ps_4.13b+cvs.2003.09.20-1_i386.deb
a2ps_4.13b+cvs.2003.09.20.orig.tar.gz
  to pool/main/a/a2ps/a2ps_4.13b+cvs.2003.09.20.orig.tar.gz


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

Accepted dacode 1.4.1-2.1 (all source)

2003-09-21 Thread Christian Perrier

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 09:49:21 +0200
Source: dacode
Binary: dacode dacode-doc
Architecture: source all
Version: 1.4.1-2.1
Distribution: unstable
Urgency: low
Maintainer: Benjamin Drieu [EMAIL PROTECTED]
Changed-By: Christian Perrier [EMAIL PROTECTED]
Description: 
 dacode - Powerful and full-featured news engine written in PHP
 dacode-doc - HTML documentation for daCode
Closes: 199690
Changes: 
 dacode (1.4.1-2.1) unstable; urgency=low
 .
   * Non-maintainer upload
   * Switch to po-debconf for templates. Closes: #199690
   * Review by the french l10n team of the french translation for templates
Files: 
 f9b2b11f42e661bd9b487013b043073e 581 web optional dacode_1.4.1-2.1.dsc
 161fb3dcdad2c91bacbb2b868f4e2d54 12581 web optional dacode_1.4.1-2.1.diff.gz
 f2c1d221a67dfe49ece2858ba39aebb4 1045730 web optional dacode_1.4.1-2.1_all.deb
 f08d88bbc73003f32f6e707799f5d0e4 862834 doc optional dacode-doc_1.4.1-2.1_all.deb

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

iD8DBQE/bVlIiONoszDJNIoRAorvAJ0ZTdhNRR4WUBu+i4AqcMkFLagEiwCfUcOe
7BK1w4BPxULWd2ec4TVivvQ=
=SV4C
-END PGP SIGNATURE-


Accepted:
dacode-doc_1.4.1-2.1_all.deb
  to pool/main/d/dacode/dacode-doc_1.4.1-2.1_all.deb
dacode_1.4.1-2.1.diff.gz
  to pool/main/d/dacode/dacode_1.4.1-2.1.diff.gz
dacode_1.4.1-2.1.dsc
  to pool/main/d/dacode/dacode_1.4.1-2.1.dsc
dacode_1.4.1-2.1_all.deb
  to pool/main/d/dacode/dacode_1.4.1-2.1_all.deb


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

Accepted powertweak 0.99.5-2 (powerpc i386 source all)

2003-09-21 Thread Mark Brown

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Format: 1.7
Date: Sun, 21 Sep 2003 11:50:58 +0100
Source: powertweak
Binary: powertweak lspowertweak powertweak-extra powertweakd powertweak-gtk
Architecture: source i386 all powerpc
Version: 0.99.5-2
Distribution: unstable
Urgency: low
Maintainer: Mark Brown [EMAIL PROTECTED]
Changed-By: Mark Brown [EMAIL PROTECTED]
Description: 
 lspowertweak - Simple front end to powertweak
 powertweak-extra - Plugins for powertweakd
 powertweak-gtk - GTK mode tool to configure hardware tweaks for powertweakd
 powertweakd - Tool to tune system for optimal performance
Closes: 206330 211908
Changes: 
 powertweak (0.99.5-2) unstable; urgency=low
 .
   * Add Dutch Debconf translation provided by cobaco [EMAIL PROTECTED]
 (closes: #206330).
   * Add Japanese Debconf translation provided by Kenshi Muto
 [EMAIL PROTECTED] (closes: #211908).
   * Update to policy 3.6.1 (no changes).
Files: 
 385497138ff297716c579e078195442a 692 admin optional powertweak_0.99.5-2.dsc
 3309bf16bd24ae4450ea73f63995c537 13665 admin optional powertweak_0.99.5-2.diff.gz
 fdecc7e481d615362544f4ebb857b592 6284 admin extra powertweak_0.99.5-2_all.deb
 51b3b4c59f0e5d890ee804dd73d84b64 155052 admin optional powertweakd_0.99.5-2_i386.deb
 7d35072d1eb3859b9306175fc59d56e7 78016 admin extra powertweak-extra_0.99.5-2_i386.deb
 53b574e64e63c4daa6c5d10ce715e918 34790 admin optional powertweak-gtk_0.99.5-2_i386.deb
 1872677433e96783d315b295e108c9c5 22062 admin optional lspowertweak_0.99.5-2_i386.deb
 1f4a9f59428ea4f57b9e59038fc8da6f 166484 admin optional 
powertweakd_0.99.5-2_powerpc.deb
 762596bd320aab02c34e2ee2f372b78d 73046 admin extra 
powertweak-extra_0.99.5-2_powerpc.deb
 61d213076c754a373e5e9ca39ca8f8cd 35024 admin optional 
powertweak-gtk_0.99.5-2_powerpc.deb
 910d6ffc83dd504dbc75c0211abaa0e7 23744 admin optional 
lspowertweak_0.99.5-2_powerpc.deb

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

iD8DBQE/bYTHJ2Vo11xhU60RAmgaAJ9t3rC5aVBLcSOaH2AeeIOVxNhnfQCeLTLU
ApJTOMQ6Cn0nfYQzSf8GiBI=
=cpw1
-END PGP SIGNATURE-


Accepted:
lspowertweak_0.99.5-2_i386.deb
  to pool/main/p/powertweak/lspowertweak_0.99.5-2_i386.deb
lspowertweak_0.99.5-2_powerpc.deb
  to pool/main/p/powertweak/lspowertweak_0.99.5-2_powerpc.deb
powertweak-extra_0.99.5-2_i386.deb
  to pool/main/p/powertweak/powertweak-extra_0.99.5-2_i386.deb
powertweak-extra_0.99.5-2_powerpc.deb
  to pool/main/p/powertweak/powertweak-extra_0.99.5-2_powerpc.deb
powertweak-gtk_0.99.5-2_i386.deb
  to pool/main/p/powertweak/powertweak-gtk_0.99.5-2_i386.deb
powertweak-gtk_0.99.5-2_powerpc.deb
  to pool/main/p/powertweak/powertweak-gtk_0.99.5-2_powerpc.deb
powertweak_0.99.5-2.diff.gz
  to pool/main/p/powertweak/powertweak_0.99.5-2.diff.gz
powertweak_0.99.5-2.dsc
  to pool/main/p/powertweak/powertweak_0.99.5-2.dsc
powertweak_0.99.5-2_all.deb
  to pool/main/p/powertweak/powertweak_0.99.5-2_all.deb
powertweakd_0.99.5-2_i386.deb
  to pool/main/p/powertweak/powertweakd_0.99.5-2_i386.deb
powertweakd_0.99.5-2_powerpc.deb
  to pool/main/p/powertweak/powertweakd_0.99.5-2_powerpc.deb


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

Accepted resolvconf 0.42 (all source)

2003-09-21 Thread Thomas Hood

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 12 Sep 2003 19:34:53 +0200
Source: resolvconf
Binary: resolvconf
Architecture: source all
Version: 0.42
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED]
Description: 
 resolvconf - Nameserver information manager
Closes: 210283
Changes: 
 resolvconf (0.42) unstable; urgency=low
 .
   * Eliminate /var/run/resolvconf
   * debian/config, debian/templates:
 * Change configuration process so that there is only one question.
   The question asks whether the package should linkify /etc/resolv.conf
   _and_ downup all interfaces _and_ restart all DNS caches.  The
   alternative is to do none of these things.  The debconf description
   now provides a lot more information about the alternatives.  The
   priority of the question is now high.  (Closes: #210283)
   * etc/resolvconf/update.d/libc:
 * Trap EXIT in order to remove the temporary file.
Files: 
 d33c106daf20450bcb62bf0726329106 506 net optional resolvconf_0.42.dsc
 b4cf29a00677ea331c875327a3b274b8 26310 net optional resolvconf_0.42.tar.gz
 864ece635544fe05b21e128da0ed30dd 23584 net optional resolvconf_0.42_all.deb

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

iD8DBQE/ZZJoTo5vwBMoL/IRArTPAJ9K37vBUPnB0fWu7rwNgkEEKMwfEgCfXGuV
TiyJOz060QPwhU3Rs2pbzyM=
=jFbJ
-END PGP SIGNATURE-


Accepted:
resolvconf_0.42.dsc
  to pool/main/r/resolvconf/resolvconf_0.42.dsc
resolvconf_0.42.tar.gz
  to pool/main/r/resolvconf/resolvconf_0.42.tar.gz
resolvconf_0.42_all.deb
  to pool/main/r/resolvconf/resolvconf_0.42_all.deb


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

Accepted dupload 2.6.2 (all source)

2003-09-21 Thread Josip Rodin

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 16 Sep 2003 12:40:59 +0200
Source: dupload
Binary: dupload
Architecture: source all
Version: 2.6.2
Distribution: unstable
Urgency: low
Maintainer: Josip Rodin [EMAIL PROTECTED]
Changed-By: Josip Rodin [EMAIL PROTECTED]
Description: 
 dupload- utility to upload Debian packages
Closes: 146840 179711 195903
Changes: 
 dupload (2.6.2) unstable; urgency=low
 .
   * Added security.debian.org:/org/security.debian.org/queue/unchecked
 to the config file.
   * Properly detects Changes and Files multi-line tags, thanks to
 Matthias Urlichs, closes: #195903.
   * Added testing to the list of accepted distributions because of
 mini-dinstall, by request of Bruno Rodrigues, closes: #179711.
   * Added the delayed upload stuff from the Developer's Reference
 to the config file, but renamed the DELAY variable to DEBDELAY
 to cause less namespace pollution, closes: #146840.
Files: 
 413151c294003ddfef7a51f693fa7788 529 devel optional dupload_2.6.2.dsc
 c133ce48744a61f1900fee0310326520 20792 devel optional dupload_2.6.2.tar.gz
 88240cff30891d4270a92440fa25ae78 8016 devel optional dupload_2.6.2_all.deb

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

iD8DBQE/bYxVC1RHoiANFZYRAtcVAKDGw4QBjSz+lrpogBxj9Z1j+G61KQCgsTfD
Len4eqcSM14hZlZLVFRznXQ=
=NTu4
-END PGP SIGNATURE-


Accepted:
dupload_2.6.2.dsc
  to pool/main/d/dupload/dupload_2.6.2.dsc
dupload_2.6.2.tar.gz
  to pool/main/d/dupload/dupload_2.6.2.tar.gz
dupload_2.6.2_all.deb
  to pool/main/d/dupload/dupload_2.6.2_all.deb


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

Accepted wmifinfo 0.06-2 (i386 source)

2003-09-21 Thread Gordon Fraser

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 12:57:38 +0200
Source: wmifinfo
Binary: wmifinfo
Architecture: source i386
Version: 0.06-2
Distribution: unstable
Urgency: low
Maintainer: Gordon Fraser [EMAIL PROTECTED]
Changed-By: Gordon Fraser [EMAIL PROTECTED]
Description: 
 wmifinfo   - Dockapp that shows information for all interfaces
Closes: 210793
Changes: 
 wmifinfo (0.06-2) unstable; urgency=low
 .
   * New maintainer (Closes: #210793)
   * Bump standards-version to 3.6.1.0
   * Update DEB_BUILD_OPTIONS handling
   * Minor update to description
   * Remove dh_make boilerplate from debian/copyright
   * Add menu entry
Files: 
 350faeab9275a62d522218e1712bdbff 574 x11 optional wmifinfo_0.06-2.dsc
 90e93fd2fe5bb27fef1628d66c797561 2916 x11 optional wmifinfo_0.06-2.diff.gz
 50dfd13cb4cf8f72014f343dd494d4de 19574 x11 optional wmifinfo_0.06-2_i386.deb

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

iD8DBQE/bYrxFgAj91iLfZwRApRTAKCK4lmvivVLwyrZndQWXLZOpKgYgACbBfIw
AYhWKpcZCo+1z0w6WrEePOM=
=WWYU
-END PGP SIGNATURE-


Accepted:
wmifinfo_0.06-2.diff.gz
  to pool/main/w/wmifinfo/wmifinfo_0.06-2.diff.gz
wmifinfo_0.06-2.dsc
  to pool/main/w/wmifinfo/wmifinfo_0.06-2.dsc
wmifinfo_0.06-2_i386.deb
  to pool/main/w/wmifinfo/wmifinfo_0.06-2_i386.deb


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

Accepted kernel-patch-2.4-grsecurity 1.9.12-2 (all source)

2003-09-21 Thread martin f. krafft

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 13:44:43 +0200
Source: kernel-patch-2.4-grsecurity
Binary: kernel-patch-2.4-grsecurity
Architecture: source all
Version: 1.9.12-2
Distribution: unstable
Urgency: low
Maintainer: martin f. krafft [EMAIL PROTECTED]
Changed-By: martin f. krafft [EMAIL PROTECTED]
Description: 
 kernel-patch-2.4-grsecurity - grsecurity kernel patch - 2.4.x security patch
Closes: 203759 204424
Changes: 
 kernel-patch-2.4-grsecurity (1.9.12-2) unstable; urgency=low
 .
   * Fixed the patch to apply to Debian kernel version 2.4.17
   * Fixed the patch to apply to Debian kernel version 2.4.18
   closes: Bug#203759, Bug#204424
   * Fixed the patch to apply to Debian kernel version 2.4.19
   * Decided to *not* support Debian kernel versions 2.4.20 and up. This
 decision is documented in
 /usr/share/doc/kernel-patch-2.4-grsecurity/README.2.4.2x.
   * Added note pertaining to the latter to debian/control.
   * Added debconf notice pertaining to the latter.
   * Changed debhelper scripts to use -i.
Files: 
 fe9650e46901a9fb5a77b433cbf8657d 580 devel extra 
kernel-patch-2.4-grsecurity_1.9.12-2.dsc
 6d9ec48ec9b71578a02d9a7073d1d9c0 835108 devel extra 
kernel-patch-2.4-grsecurity_1.9.12-2.tar.gz
 a2144cb0ba761a0c38fba78954da5602 844328 devel extra 
kernel-patch-2.4-grsecurity_1.9.12-2_all.deb

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

iD8DBQE/bZAHIgvIgzMMSnURAoCJAKDgM4J0cd66L2LKazjm7O8Dh+kp9ACeNbjy
WzwZfrgTtz8s0olGjZI65Iw=
=wYdQ
-END PGP SIGNATURE-


Accepted:
kernel-patch-2.4-grsecurity_1.9.12-2.dsc
  to pool/main/k/kernel-patch-2.4-grsecurity/kernel-patch-2.4-grsecurity_1.9.12-2.dsc
kernel-patch-2.4-grsecurity_1.9.12-2.tar.gz
  to 
pool/main/k/kernel-patch-2.4-grsecurity/kernel-patch-2.4-grsecurity_1.9.12-2.tar.gz
kernel-patch-2.4-grsecurity_1.9.12-2_all.deb
  to 
pool/main/k/kernel-patch-2.4-grsecurity/kernel-patch-2.4-grsecurity_1.9.12-2_all.deb


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

Accepted wmcalclock 1.25-9 (i386 source)

2003-09-21 Thread Gordon Fraser

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 13:40:03 +0200
Source: wmcalclock
Binary: wmcalclock
Architecture: source i386
Version: 1.25-9
Distribution: unstable
Urgency: low
Maintainer: Gordon Fraser [EMAIL PROTECTED]
Changed-By: Gordon Fraser [EMAIL PROTECTED]
Description: 
 wmcalclock - A dock.app which simply tells time and date
Closes: 149916
Changes: 
 wmcalclock (1.25-9) unstable; urgency=low
 .
   * Use lower case only letters for binary name (Closes: #149916)
   * Add symbolic links to wmcalclock and wmcalclock.1.gz for
 backward compatibility.
   * Standards-version to 3.6.1.0
   * Remove dh_make boilerplate from debian/copyright
   * Update DH_BUILD_OPTIONS handling
   * Remove trailing dot from short description
Files: 
 dfc48486ffcff048174a5ea1f983a047 582 x11 optional wmcalclock_1.25-9.dsc
 0f2e1ac3e8b0c2411011a155e54f56f0 2662 x11 optional wmcalclock_1.25-9.diff.gz
 f9230dbcb81735390ccd9c6b735dc12d 48008 x11 optional wmcalclock_1.25-9_i386.deb

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

iD8DBQE/bZN4FgAj91iLfZwRAi2OAJ9PJL1KWuCJ7XNHxYBMZhLOVAnYqACeIXPR
QFytHWpqzd+fEs4i8RdVNfk=
=U8B/
-END PGP SIGNATURE-


Accepted:
wmcalclock_1.25-9.diff.gz
  to pool/main/w/wmcalclock/wmcalclock_1.25-9.diff.gz
wmcalclock_1.25-9.dsc
  to pool/main/w/wmcalclock/wmcalclock_1.25-9.dsc
wmcalclock_1.25-9_i386.deb
  to pool/main/w/wmcalclock/wmcalclock_1.25-9_i386.deb


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

Accepted libroxen-safequote 1.7-4 (all source)

2003-09-21 Thread Turbo Fredriksson

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 14:37:13 +0200
Source: libroxen-safequote
Binary: libroxen-safequote
Architecture: source all
Version: 1.7-4
Distribution: unstable
Urgency: low
Maintainer: Turbo Fredriksson [EMAIL PROTECTED]
Changed-By: Turbo Fredriksson [EMAIL PROTECTED]
Description: 
 libroxen-safequote - Safe quoting module for the Roxen Challenger web server
Closes: 205257
Changes: 
 libroxen-safequote (1.7-4) unstable; urgency=low
 .
   * Remove double spaces in description
 Closes: #205257
Files: 
 4a5cca6c78ca41c27b0aa8a489592077 632 web optional libroxen-safequote_1.7-4.dsc
 f62d8a6519ddaafe53b297e8c65c5c59 1543 web optional libroxen-safequote_1.7-4.diff.gz
 c8e1ddae209e5f9aee60c7888ec0c136 3854 web optional libroxen-safequote_1.7-4_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/bZwRmlWzPKccHgARAjFEAJ4+ABQSAOCIbzfofFunhuiFrNTWngCeIAfJ
lhaA/kxopK7KgRlUo9h99wA=
=JI6G
-END PGP SIGNATURE-


Accepted:
libroxen-safequote_1.7-4.diff.gz
  to pool/main/libr/libroxen-safequote/libroxen-safequote_1.7-4.diff.gz
libroxen-safequote_1.7-4.dsc
  to pool/main/libr/libroxen-safequote/libroxen-safequote_1.7-4.dsc
libroxen-safequote_1.7-4_all.deb
  to pool/main/libr/libroxen-safequote/libroxen-safequote_1.7-4_all.deb


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

Accepted glibc 2.3.2-8 (i386 source all)

2003-09-21 Thread Philip Blundell

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Wed, 17 Sep 2003 20:44:48 +0100
Source: glibc
Binary: libc6.1-prof libc1 libc0.3-pic locales glibc-doc libc6-pic libc-udeb 
libc1-prof libc0.3 libc0.3-dbg libc6.1-dev libc1-pic libc6-s390x libc6-prof libc1-dbg 
libc6-dev-sparc64 libc6 libc0.3-dev libc6-dbg nscd libc6.1-dbg libc6.1-pic 
libc6-sparc64 libc6-dev libc0.3-prof libc6.1 libc6-dev-s390x libc1-dev
Architecture: source i386 all
Version: 2.3.2-8
Distribution: unstable
Urgency: low
Maintainer: GNU Libc Maintainers [EMAIL PROTECTED]
Changed-By: Philip Blundell [EMAIL PROTECTED]
Description: 
 glibc-doc  - GNU C Library: Documentation
 libc-udeb  - GNU C Library: Shared libraries and Timezone data - udeb (udeb)
 libc6  - GNU C Library: Shared libraries and Timezone data
 libc6-dbg  - GNU C Library: Libraries with debugging symbols
 libc6-dev  - GNU C Library: Development Libraries and Header Files.
 libc6-pic  - GNU C Library: PIC archive library
 libc6-prof - GNU C Library: Profiling Libraries.
 locales- GNU C Library: National Language (locale) data [support]
 nscd   - GNU C Library: Name Service Cache Daemon
Closes: 205234 210301 211135
Changes: 
 glibc (2.3.2-8) unstable; urgency=low
 .
   * Phil Blundell [EMAIL PROTECTED]
 .
 - debian/control.in/main: add gawk to Build-Depends, since testsuite
   apparently requires it.
 .
 - debian/patches/pthread-cleanup.dpatch: Vector __pthread_cleanup_push
   and __pthread_cleanup_pop through __libc_pthread_functions.
   (Closes: #205234)
 .
 - debian/patches/arm-no-hwcap.dpatch: Admit HWCAP_FAST_MULT again,
   since we want to start using this for openssh.
 - debian/patches/arm-updates.dpatch: Add some miscellaneous arm
   changes taken from upstream.
 - debian/patches/arm-vfork.dpatch: Avoid bad interaction between
   vfork and libpthread.
 .
   * GOTO Masanori  [EMAIL PROTECTED]
 .
 - debian/patches/80_glibc232-fesetround-fix.dpatch: Fix fesetround static
   link time failure.  (Closes: #211135)
 .
 - debian/patches/lo_LA.UTF-8_not_supported.dpatch: Dropped, to support
   lo_LA.UTF-8 again.
 - debian/patches/80_glibc232-locales-lo_LA.dpatch: Added to support
   lo_LA.UTF-8 again.
 .
 - debian/locales/usr/sbin/locale-gen: Fix locale-gen breaks with bash
   2.03, unset POSIXLY_CORRECT iff it's previously defined.
   Patched by Daniel Verite [EMAIL PROTECTED].  (Closes: #210301)
Files: 
 f3992dbcef29a645e5a4b64027565981 1684 libs required glibc_2.3.2-8.dsc
 2777f39352b0762105e4b42bcec575f8 1178096 libs required glibc_2.3.2-8.diff.gz
 9c0f14841ea4fec579a6dc86a9f1ceb3 3717572 base required libc6_2.3.2-8_i386.deb
 d4edda6aa25ca67c494dec277d01b4cb 1066086 debian-installer required 
libc-udeb_2.3.2-8_i386.udeb
 47cd8c1fce8913e868ee930367491c1d 2633324 libdevel standard libc6-dev_2.3.2-8_i386.deb
 c1b73aaef7ff64e73e5b6bd61f41420a 1027080 libdevel extra libc6-prof_2.3.2-8_i386.deb
 86f88c315d7410295e33b424a40053d5 8527672 libdevel extra libc6-dbg_2.3.2-8_i386.deb
 6f08f99dad3e773ca7f2040b77735788 997168 libdevel optional libc6-pic_2.3.2-8_i386.deb
 1498b580cc1ae118e01e755cdaf49657 77948 admin optional nscd_2.3.2-8_i386.deb
 b825730dcdafdb19fa366a83c0bd2eca 3799972 base standard locales_2.3.2-8_all.deb
 216fde46ac173740bf4ed351330990be 3705298 doc optional glibc-doc_2.3.2-8_all.deb

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

iD8DBQE/baGYVTLPJe9CT30RAgBOAKDI4w58Gw7UdtwrlhGQrce7QUssjwCfWeeI
CmAo3cErnd1umEt4yYOOCrk=
=3D+U
-END PGP SIGNATURE-


Accepted:
glibc-doc_2.3.2-8_all.deb
  to pool/main/g/glibc/glibc-doc_2.3.2-8_all.deb
glibc_2.3.2-8.diff.gz
  to pool/main/g/glibc/glibc_2.3.2-8.diff.gz
glibc_2.3.2-8.dsc
  to pool/main/g/glibc/glibc_2.3.2-8.dsc
libc-udeb_2.3.2-8_i386.udeb
  to pool/main/g/glibc/libc-udeb_2.3.2-8_i386.udeb
libc6-dbg_2.3.2-8_i386.deb
  to pool/main/g/glibc/libc6-dbg_2.3.2-8_i386.deb
libc6-dev_2.3.2-8_i386.deb
  to pool/main/g/glibc/libc6-dev_2.3.2-8_i386.deb
libc6-pic_2.3.2-8_i386.deb
  to pool/main/g/glibc/libc6-pic_2.3.2-8_i386.deb
libc6-prof_2.3.2-8_i386.deb
  to pool/main/g/glibc/libc6-prof_2.3.2-8_i386.deb
libc6_2.3.2-8_i386.deb
  to pool/main/g/glibc/libc6_2.3.2-8_i386.deb
locales_2.3.2-8_all.deb
  to pool/main/g/glibc/locales_2.3.2-8_all.deb
nscd_2.3.2-8_i386.deb
  to pool/main/g/glibc/nscd_2.3.2-8_i386.deb


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

Accepted console-tools 1:0.2.3dbs-43 (i386 source all)

2003-09-21 Thread Alastair McKinstry

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 11:12:05 +0100
Source: console-tools
Binary: kbd-compat console-tools-dev libconsole console-tools
Architecture: source all i386
Version: 1:0.2.3dbs-43
Distribution: unstable
Urgency: low
Maintainer: Alastair McKinstry [EMAIL PROTECTED]
Changed-By: Alastair McKinstry [EMAIL PROTECTED]
Description: 
 console-tools - Linux console and font utilities
 console-tools-dev - Development files for Linux console and font manipulation
 kbd-compat - Wrappers around console-tools for backward compatibility with `kb
 libconsole - Shared libraries for Linux console and font manipulation
Closes: 211059 211061
Changes: 
 console-tools (1:0.2.3dbs-43) unstable; urgency=low
 .
   * Remove bashisms from console-screen.sh. Closes: #211059.
   * Report error messages from unicode_{start,stop}. Closes: #211061.
Files: 
 5ee486a4c7e494489eecabe60b5c32c5 642 base important console-tools_0.2.3dbs-43.dsc
 1e725136ec401d4fe534e109926c2363 914498 base important 
console-tools_0.2.3dbs-43.tar.gz
 411484044669bb03d0de36678745bfc1 40044 utils optional kbd-compat_0.2.3dbs-43_all.deb
 14906f07577822c2791071eabbb43164 296210 utils important 
console-tools_0.2.3dbs-43_i386.deb
 0bf1baa1cadbe8a24aef05e3e24d9b75 107380 libs important libconsole_0.2.3dbs-43_i386.deb
 8c1a8d88bb36622d399210dccadfa636 79402 devel optional 
console-tools-dev_0.2.3dbs-43_i386.deb

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

iD8DBQE/baUq+o43kJBROPQRAqtAAJ0d8XqpQgjZABBL4IjHnvBEPt4dMwCg64dV
j8DCnWSyCq5wrIiAebZnqok=
=so4O
-END PGP SIGNATURE-


Accepted:
console-tools-dev_0.2.3dbs-43_i386.deb
  to pool/main/c/console-tools/console-tools-dev_0.2.3dbs-43_i386.deb
console-tools_0.2.3dbs-43.dsc
  to pool/main/c/console-tools/console-tools_0.2.3dbs-43.dsc
console-tools_0.2.3dbs-43.tar.gz
  to pool/main/c/console-tools/console-tools_0.2.3dbs-43.tar.gz
console-tools_0.2.3dbs-43_i386.deb
  to pool/main/c/console-tools/console-tools_0.2.3dbs-43_i386.deb
kbd-compat_0.2.3dbs-43_all.deb
  to pool/main/c/console-tools/kbd-compat_0.2.3dbs-43_all.deb
libconsole_0.2.3dbs-43_i386.deb
  to pool/main/c/console-tools/libconsole_0.2.3dbs-43_i386.deb


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

Accepted cinepaint 0.18.1-3 (i386 source all)

2003-09-21 Thread Andrew Lau

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sat, 20 Sep 2003 14:07:11 +1000
Source: cinepaint
Binary: libcinepaint0 libcinepaint-dev cinepaint-data cinepaint
Architecture: source i386 all
Version: 0.18.1-3
Distribution: unstable
Urgency: low
Maintainer: Andrew Lau [EMAIL PROTECTED]
Changed-By: Andrew Lau [EMAIL PROTECTED]
Description: 
 cinepaint  - A motion picture image painting and retouching tool
 cinepaint-data - Data files for CinePaint
 libcinepaint-dev - Development library files for CinePaint
 libcinepaint0 - Runtime library files for CinePaint
Changes: 
 cinepaint (0.18.1-3) unstable; urgency=low
 .
   * The I shot myself in the foot Debian release. Sorry.
 Forgot to actually include the fixed icon file in 0.18.1-2!
Files: 
 8c023bdc51e82cf5d7d680c3e63f81b1 743 graphics optional cinepaint_0.18.1-3.dsc
 8c958f7978f4a4bebeda47a56a3348ad 4294 graphics optional cinepaint_0.18.1-3.diff.gz
 4cf12573119b6efad8546475045a9573 5406796 graphics optional 
cinepaint-data_0.18.1-3_all.deb
 4ca79f14a0317db2f9b27a00fae522cf 994704 graphics optional cinepaint_0.18.1-3_i386.deb
 1eea95f2347337a3217e0899b2257db4 121788 libdevel optional 
libcinepaint-dev_0.18.1-3_i386.deb
 183ba669e0baa0e6df2016a2fc09f00f 105358 libs optional libcinepaint0_0.18.1-3_i386.deb

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

iD8DBQE/bcn9nDLqtZBL50ERAkWqAKCCm7k3XvhNj7+LRmkEkyUhlEiT7gCgnF2S
NuDXWwFTzmivmDPIqC3XDW8=
=SgGa
-END PGP SIGNATURE-


Accepted:
cinepaint-data_0.18.1-3_all.deb
  to pool/main/c/cinepaint/cinepaint-data_0.18.1-3_all.deb
cinepaint_0.18.1-3.diff.gz
  to pool/main/c/cinepaint/cinepaint_0.18.1-3.diff.gz
cinepaint_0.18.1-3.dsc
  to pool/main/c/cinepaint/cinepaint_0.18.1-3.dsc
cinepaint_0.18.1-3_i386.deb
  to pool/main/c/cinepaint/cinepaint_0.18.1-3_i386.deb
libcinepaint-dev_0.18.1-3_i386.deb
  to pool/main/c/cinepaint/libcinepaint-dev_0.18.1-3_i386.deb
libcinepaint0_0.18.1-3_i386.deb
  to pool/main/c/cinepaint/libcinepaint0_0.18.1-3_i386.deb


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

Accepted man-db 2.4.2-2 (i386 source)

2003-09-21 Thread Colin Watson

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 14:38:27 +0100
Source: man-db
Binary: man-db
Architecture: source i386
Version: 2.4.2-2
Distribution: unstable
Urgency: low
Maintainer: Colin Watson [EMAIL PROTECTED]
Changed-By: Colin Watson [EMAIL PROTECTED]
Description: 
 man-db - The on-line manual pager
Closes: 211977
Changes: 
 man-db (2.4.2-2) unstable; urgency=low
 .
   * mandb only complains if it failed to do anything on create, not on
 update (closes: #211977).
   * Teach encodings layer about Galician, Indonesian, Croatian, and Slovak.
Files: 
 d873fb2f16aa7872cf1af98ef73ca4df 658 doc important man-db_2.4.2-2.dsc
 1a95a8c34cd749ae40e2977cea6c207e 60723 doc important man-db_2.4.2-2.diff.gz
 063fe8c15d0398ac3f64a6205825b513 575368 doc important man-db_2.4.2-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Colin Watson [EMAIL PROTECTED] -- Debian developer

iD8DBQE/bdE29t0zAhD6TNERAnypAJ4q9uiPxKK/P1ItLUXSCd2Q9FtNpwCaApji
SlTgqwSH+pn0E2yfBQTfUJA=
=+MQN
-END PGP SIGNATURE-


Accepted:
man-db_2.4.2-2.diff.gz
  to pool/main/m/man-db/man-db_2.4.2-2.diff.gz
man-db_2.4.2-2.dsc
  to pool/main/m/man-db/man-db_2.4.2-2.dsc
man-db_2.4.2-2_i386.deb
  to pool/main/m/man-db/man-db_2.4.2-2_i386.deb


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

Accepted rcconf 1.6 (all source)

2003-09-21 Thread Atsushi KAMOSHIDA

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 22 Sep 2003 01:41:31 +0900
Source: rcconf
Binary: rcconf
Architecture: source all
Version: 1.6
Distribution: unstable
Urgency: low
Maintainer: Atsushi KAMOSHIDA [EMAIL PROTECTED]
Changed-By: Atsushi KAMOSHIDA [EMAIL PROTECTED]
Description: 
 rcconf - Debian Runlevel configuration tool
Changes: 
 rcconf (1.6) unstable; urgency=low
 .
   * Fixed remaing lock file problem(Close #144053).
   * Fixed description(Close #144560,#166518,#168414).
   * Add whiptail-privider dependancy(Close #141179).
   * Fixed copyright(Close #151968).
   * Close #67852 and #60405.
   * Delete /var/lib/rcconf/services if purged(Close #205468).
Files: 
 20b991f44710b17e9c9b996eef04f41e 480 admin optional rcconf_1.6.dsc
 070f83c82f739f3f21e8c19506c2021a 6839 admin optional rcconf_1.6.tar.gz
 11ea93381b8eff52be210c67cf86135b 9870 admin optional rcconf_1.6_all.deb

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

iD8DBQE/bdqzYxU8kEKVVoIRAiToAJ9I28SzFmzfrJPquP9bOUssoU4yVgCfVvHm
aJKlglU3Sdx3ZtqJNWXWRo4=
=aL8e
-END PGP SIGNATURE-


Accepted:
rcconf_1.6.dsc
  to pool/main/r/rcconf/rcconf_1.6.dsc
rcconf_1.6.tar.gz
  to pool/main/r/rcconf/rcconf_1.6.tar.gz
rcconf_1.6_all.deb
  to pool/main/r/rcconf/rcconf_1.6_all.deb


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

Accepted tpctl 4.7-1 (i386 source)

2003-09-21 Thread Thomas Hood

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 10 Aug 2003 14:49:33 -0400
Source: tpctl
Binary: tpctl
Architecture: source i386
Version: 4.7-1
Distribution: unstable
Urgency: low
Maintainer: Thomas Hood [EMAIL PROTECTED]
Changed-By: Thomas Hood [EMAIL PROTECTED]
Description: 
 tpctl  - IBM ThinkPad hardware configuration tools
Closes: 206084 206514
Changes: 
 tpctl (4.7-1) unstable; urgency=low
 .
   * debian/po/nl.po:
 * Add  (Closes: #206514).  Met dank aan cobaco.
   * debian/postinst:
 * try-restart apmiser on upgrade
   * debian/rules:
 * Make use of dh_installinit's new --name option.
   Thanks to Joey Hess for implementing this.
   * debian/control:
 * Build-Depend on debhelper 4.1.68 because of above
 * Standards-Version: 3.6.1  (No changes required)
   * /etc/init.d/tpctl:
 * Create to control sedate-on-lid-closure -- disable it during
   boot and shutdown sequences.  (Closes: #206084)
   Thanks to Andrew Lau for this idea.
   * /etc/default/tpctl:
 * Create to control initscript
   * /usr/sbin/apmiser:
 * Make more intelligent.  New options have been added.
   See the upstream ChangeLog for more details.
   Thanks to wayne schlitt for this work.
   * /etc/init.d/apmiser:
 * Take advantage of the fact that apmiser now generates a pidfile
 * Improve messages and error handling
 * Add try-restart option for use by postinst
   * /etc/apm/event.d/apmiser:
 * Create
   * /etc/default/apmiser:
 * Create to control initscript and apm event script
   * apmiser/README
 * Update
Files: 
 e9e5d2a72986e001b660eef9cf394040 505 utils extra tpctl_4.7-1.dsc
 6048200f65bfea1dab0ed308091d4b42 89728 utils extra tpctl_4.7-1.tar.gz
 eac65fe1192301db7869ecea6dd4d566 72976 utils extra tpctl_4.7-1_i386.deb

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

iD8DBQE/bcVWflgj9+6E5x0RAoadAJ9jN1E8550/+/u1lohcCgibfyfHQgCeJZ/3
zO7ah1FuSYyjKL2BqivPeRg=
=6U0n
-END PGP SIGNATURE-


Accepted:
tpctl_4.7-1.dsc
  to pool/main/t/tpctl/tpctl_4.7-1.dsc
tpctl_4.7-1.tar.gz
  to pool/main/t/tpctl/tpctl_4.7-1.tar.gz
tpctl_4.7-1_i386.deb
  to pool/main/t/tpctl/tpctl_4.7-1_i386.deb


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

Accepted libjcode-pm-perl 0.83-1 (i386 source)

2003-09-21 Thread Atsushi KAMOSHIDA

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 22 Sep 2003 02:23:22 +0900
Source: libjcode-pm-perl
Binary: libjcode-pm-perl
Architecture: source i386
Version: 0.83-1
Distribution: unstable
Urgency: low
Maintainer: Atsushi KAMOSHIDA [EMAIL PROTECTED]
Changed-By: Atsushi KAMOSHIDA [EMAIL PROTECTED]
Description: 
 libjcode-pm-perl - Perl extension interface to convert Japanese text
Changes: 
 libjcode-pm-perl (0.83-1) unstable; urgency=low
 .
   * New upstream Release.
   * Closed #147047.
Files: 
 00dc72615d39e5c879cb3f099baa8a92 525 interpreters optional libjcode-pm-perl_0.83-1.dsc
 e32427b8b36067a3fa83be095fc8fb6b 190441 interpreters optional 
libjcode-pm-perl_0.83-1.tar.gz
 09c52bd541a5f602ae396d0485b1c610 159632 interpreters optional 
libjcode-pm-perl_0.83-1_i386.deb

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

iD8DBQE/beCnYxU8kEKVVoIRAuqiAKCXgsBmUlELxvLkqWmxjhZK4Fl49QCgk4kX
2rAv+nU9TQIKtlz6/z8VbMY=
=qGt6
-END PGP SIGNATURE-


Accepted:
libjcode-pm-perl_0.83-1.dsc
  to pool/main/libj/libjcode-pm-perl/libjcode-pm-perl_0.83-1.dsc
libjcode-pm-perl_0.83-1.tar.gz
  to pool/main/libj/libjcode-pm-perl/libjcode-pm-perl_0.83-1.tar.gz
libjcode-pm-perl_0.83-1_i386.deb
  to pool/main/libj/libjcode-pm-perl/libjcode-pm-perl_0.83-1_i386.deb


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

Accepted aish 1.13-2 (i386 source)

2003-09-21 Thread Atsushi KAMOSHIDA

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Mon, 22 Sep 2003 02:44:19 +0900
Source: aish
Binary: aish
Architecture: source i386
Version: 1.13-2
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-2) unstable; urgency=low
 .
   * Maintainer release.
Files: 
 a58dd6417a73ec52b2f0d6e7e08d2e5b 537 misc optional aish_1.13-2.dsc
 b3df9555fcdcf37cf365026fb6b1a5ef 3154 misc optional aish_1.13-2.diff.gz
 9f83f3b16e7fa9e064fe50c847c8c865 36378 misc optional aish_1.13-2_i386.deb

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

iD8DBQE/bePPYxU8kEKVVoIRAgBdAJoDmyin4ENCypO1+w30qE3PGtYFAwCgncsa
r+uUxwiAkzmN0h9YP11GrRc=
=o9KS
-END PGP SIGNATURE-


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


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

Accepted fakeroot 0.7.7 (source)

2003-09-21 Thread Clint Adams

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 12:13:17 -0400
Source: fakeroot
Binary: fakeroot
Architecture: source
Version: 0.7.7
Distribution: unstable
Urgency: medium
Maintainer: Clint Adams [EMAIL PROTECTED]
Changed-By: Clint Adams [EMAIL PROTECTED]
Description: 
 fakeroot   - Gives a fake root environment
Closes: 211617 211915
Changes: 
 fakeroot (0.7.7) unstable; urgency=medium
 .
   * doc/fr/fakeroot.1 update from Sylvain Cherrier.  closes: #211915.
   * faked.cc: Patch from Marc Horowitz to use long longs for
 the persistent db.  closes: #211617.
   * faked.cc: Change long longs to uint64_t.
Files: 
 901486843733ea9468352087c7f6d1a4 571 utils optional fakeroot_0.7.7.dsc
 ad3c17f216fe92bf85f0b2d12d0c5ffe 677812 utils optional fakeroot_0.7.7.tar.gz

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

iD8DBQE/bfHh5m0u66uWM3ARArYXAJ4k/xZmAb9R75AB6jpK/WAHvue9tQCfTsjT
bmT3B7EGp0BPsowadvm9l8I=
=/eIe
-END PGP SIGNATURE-


Accepted:
fakeroot_0.7.7.dsc
  to pool/main/f/fakeroot/fakeroot_0.7.7.dsc
fakeroot_0.7.7.tar.gz
  to pool/main/f/fakeroot/fakeroot_0.7.7.tar.gz


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

Accepted vsftpd 1.2.0-3 (i386 source)

2003-09-21 Thread Daniel Jacobowitz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 14:03:39 -0400
Source: vsftpd
Binary: vsftpd
Architecture: source i386
Version: 1.2.0-3
Distribution: unstable
Urgency: high
Maintainer: Daniel Jacobowitz [EMAIL PROTECTED]
Changed-By: Daniel Jacobowitz [EMAIL PROTECTED]
Description: 
 vsftpd - The Very Secure FTP Daemon
Changes: 
 vsftpd (1.2.0-3) unstable; urgency=HIGH
 .
   * Remove pam_ftp.so from the default PAM configuration.
Files: 
 d79d8816236eaced982a10ab3c65b654 598 net extra vsftpd_1.2.0-3.dsc
 0536fd820aaf19401c82627215ea74bf 5561 net extra vsftpd_1.2.0-3.diff.gz
 cec4793c843d12d3eb050f44152c3c28 92488 net extra vsftpd_1.2.0-3_i386.deb

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

iD8DBQE/bemXbgOPXuCjg3cRAoFuAKCLsRMe2H1Y470rTY+BSDocW1MCVACgwAsU
8CxSUREXtndU/ZTIMQuA7Uk=
=5tz/
-END PGP SIGNATURE-


Accepted:
vsftpd_1.2.0-3.diff.gz
  to pool/main/v/vsftpd/vsftpd_1.2.0-3.diff.gz
vsftpd_1.2.0-3.dsc
  to pool/main/v/vsftpd/vsftpd_1.2.0-3.dsc
vsftpd_1.2.0-3_i386.deb
  to pool/main/v/vsftpd/vsftpd_1.2.0-3_i386.deb


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

Accepted gftp 2.0.15-1 (i386 source all)

2003-09-21 Thread Aurelien Jarno

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 20:17:02 +0200
Source: gftp
Binary: gftp gftp-text gftp-common gftp-gtk
Architecture: source i386 all
Version: 2.0.15-1
Distribution: unstable
Urgency: low
Maintainer: Aurelien Beaujean [EMAIL PROTECTED]
Changed-By: Aurelien Jarno [EMAIL PROTECTED]
Description: 
 gftp   - X/GTK+ FTP client
 gftp-common - shared files for other gFTP packages
 gftp-gtk   - X/GTK+ FTP client
 gftp-text  - colored FTP client using GLib
Closes: 157018 167185 176188 176206 176337 176682 192598 211998
Changes: 
 gftp (2.0.15-1) unstable; urgency=low
 .
   * New maintainer (closes: bug#211998).
   * Acknowledge previous NMU (closes: bug#157018, #167185, #176188, #176206,
 #176337, #176682, #192598).
   * Updated debian/copyright.
   * Uses debian/compat instead of DH_COMPAT.
   * debian/control:
 + Added homepage and author to the description.
 + Depends on ${misc:Depends}.
 + Changed gftp to arch all as it is only a transitionnal package.
   * debian/control:
 + Uses dh_install instead of dh_movefiles.
 + Uses autotools-dev to update config.{guess,sub}.
 + Don't install README, THANKS, TODO and USERS-GUIDE in all three gftp-*
   packages. Put them only in gftp-common and create links to them in
   gftp-gtk and gftp-text.
Files: 
 5143ace17506fdc7abd38973a906a292 688 net optional gftp_2.0.15-1.dsc
 5a076c251c1d81cace49ebe197c0d70a 1590363 net optional gftp_2.0.15.orig.tar.gz
 2497ea083f94a042544811f66f7e44fb 4241 net optional gftp_2.0.15-1.diff.gz
 26e1c8447551084807c4c7fa2a3aca2d 54794 net optional gftp_2.0.15-1_all.deb
 29bd12bbebbfdbdd43b594885a0cac8b 247174 net optional gftp-gtk_2.0.15-1_i386.deb
 236ed52a1e1662eff74cf21212a0852a 88406 net optional gftp-text_2.0.15-1_i386.deb
 e466c0c5244323ebf61e56eda3a37011 538532 net optional gftp-common_2.0.15-1_i386.deb

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

iD8DBQE/beyjw3ao2vG823MRAtvwAJ9Qiu+4SyVOJTNb7LuHC6rTRpdM4QCfRZKC
qFfkRbWuF58QGOSQG359WHo=
=FjAo
-END PGP SIGNATURE-


Accepted:
gftp-common_2.0.15-1_i386.deb
  to pool/main/g/gftp/gftp-common_2.0.15-1_i386.deb
gftp-gtk_2.0.15-1_i386.deb
  to pool/main/g/gftp/gftp-gtk_2.0.15-1_i386.deb
gftp-text_2.0.15-1_i386.deb
  to pool/main/g/gftp/gftp-text_2.0.15-1_i386.deb
gftp_2.0.15-1.diff.gz
  to pool/main/g/gftp/gftp_2.0.15-1.diff.gz
gftp_2.0.15-1.dsc
  to pool/main/g/gftp/gftp_2.0.15-1.dsc
gftp_2.0.15-1_all.deb
  to pool/main/g/gftp/gftp_2.0.15-1_all.deb


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

Accepted gftp 2.0.15-2 (i386 source all)

2003-09-21 Thread Aurelien Jarno

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 20:42:00 +0200
Source: gftp
Binary: gftp gftp-text gftp-common gftp-gtk
Architecture: source i386 all
Version: 2.0.15-2
Distribution: unstable
Urgency: low
Maintainer: Aurelien Jarno [EMAIL PROTECTED]
Changed-By: Aurelien Jarno [EMAIL PROTECTED]
Description: 
 gftp   - X/GTK+ FTP client
 gftp-common - shared files for other gFTP packages
 gftp-gtk   - X/GTK+ FTP client
 gftp-text  - colored FTP client using GLib
Changes: 
 gftp (2.0.15-2) unstable; urgency=low
 .
   * Oops, I forgot to change the maintainer in debian/control. Done.
Files: 
 f916985b77c5b7aacec34b28385fc36d 688 net optional gftp_2.0.15-2.dsc
 09e660d53f6b4eddc7682b5f229d728a 4294 net optional gftp_2.0.15-2.diff.gz
 48a117a2219501d1b84849c21380cceb 54832 net optional gftp_2.0.15-2_all.deb
 a09c8c89eb0020be8e37376755cadbf4 247198 net optional gftp-gtk_2.0.15-2_i386.deb
 23e47bb54999089de3e944ac18058a9f 88442 net optional gftp-text_2.0.15-2_i386.deb
 8d25179c174b157466eb443361b5c32b 538578 net optional gftp-common_2.0.15-2_i386.deb

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

iD8DBQE/bfFpw3ao2vG823MRAgfFAJ4xse1sYelygE+PaIz6GCc/ZfiBygCeNdgB
kBawzIT6oGneYHNo97HthrI=
=nBvI
-END PGP SIGNATURE-


Accepted:
gftp-common_2.0.15-2_i386.deb
  to pool/main/g/gftp/gftp-common_2.0.15-2_i386.deb
gftp-gtk_2.0.15-2_i386.deb
  to pool/main/g/gftp/gftp-gtk_2.0.15-2_i386.deb
gftp-text_2.0.15-2_i386.deb
  to pool/main/g/gftp/gftp-text_2.0.15-2_i386.deb
gftp_2.0.15-2.diff.gz
  to pool/main/g/gftp/gftp_2.0.15-2.diff.gz
gftp_2.0.15-2.dsc
  to pool/main/g/gftp/gftp_2.0.15-2.dsc
gftp_2.0.15-2_all.deb
  to pool/main/g/gftp/gftp_2.0.15-2_all.deb


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

Accepted dict-devil 1.0-6 (all source)

2003-09-21 Thread Bob Hilliard

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 15:48:30 -0400
Source: dict-devil
Binary: dict-devil
Architecture: source all
Version: 1.0-6
Distribution: unstable
Urgency: low
Maintainer: Bob Hilliard [EMAIL PROTECTED]
Changed-By: Bob Hilliard [EMAIL PROTECTED]
Description: 
 dict-devil - The Devil's Dictionary by Ambrose Bierce
Closes: 204618
Changes: 
 dict-devil (1.0-6) unstable; urgency=low
 .
   * Fixed typo in entry for woman - s/Greeland/Greenland/ - Closes: #204618
 (At first I thought this might be deliberate - Bierce was fond of
 invented proper names and fanciful expressions, and this line contains
 three apparent typos.  I obtained a hard-copy of the Devil's
 Dictionary, and verified that this was a typo in the e-text.)  (All
 copies of the Devil's Dictionary that I could find on line are based n
 the same e-test as this package.)
Files: 
 190e95dbda773d43b255302e88af011d 587 text optional dict-devil_1.0-6.dsc
 4b61c39856ea2d9ebddf1fe7df6f858e 4800 text optional dict-devil_1.0-6.diff.gz
 ad3608dc2184724f7b0f5b6c2b9b3f7d 17 text optional dict-devil_1.0-6_all.deb

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

iD8DBQE/bgJ/n+Nh6TkNZVkRAosoAJwKCtNpEOmLM3O+5x5moMav+f9OAACgmE+4
EtCgHfWXNQ/reH13hZecVUI=
=SVLN
-END PGP SIGNATURE-


Accepted:
dict-devil_1.0-6.diff.gz
  to pool/main/d/dict-devil/dict-devil_1.0-6.diff.gz
dict-devil_1.0-6.dsc
  to pool/main/d/dict-devil/dict-devil_1.0-6.dsc
dict-devil_1.0-6_all.deb
  to pool/main/d/dict-devil/dict-devil_1.0-6_all.deb


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

Accepted kernel-package 8.059 (all source)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 14:22:49 -0500
Source: kernel-package
Binary: kernel-package
Architecture: source all
Version: 8.059
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava [EMAIL PROTECTED]
Changed-By: Manoj Srivastava [EMAIL PROTECTED]
Description: 
 kernel-package - A utility for building Linux kernel related Debian packages.
Closes: 210686 211140 211406 211949
Changes: 
 kernel-package (8.059) unstable; urgency=low
 .
   * Added handling of the /lib/modules/`uname -r`/build symbolic link, if
 it is dangling. A link to the corresponding kernel-headers location is
 added if it exists. One can also force not checking for the existence
 of the kernel-headers link. closes: Bug#211949
   * In some cases, the symlink creation code created a dangling relative
 link, instead of an absolute, non dangling link, since the test
 relative code only looked at the directory names of the source, rather
 than testing for the actual file we needed to link to.
 closes: Bug#211140
   * We used to silently ignore individual patches and unpatches that were
 not found from the list of user requested patches; only complaining if
 none of the user requested patches were found. Now we stop early
 (before doing any patching at all) if any of the requested patches
 can't be found. closes: Bug#211406
   * No longer recommend debianutils, since it is an essential package.
 closes: Bug#210686
Files: 
 e9ea4d072bb8755893627bfc61480c7e 483 misc optional kernel-package_8.059.dsc
 4d674259a0f1c0235789537292d60104 267058 misc optional kernel-package_8.059.tar.gz
 558bf218ee38ea0bedb3fc4054d48c49 280160 misc optional kernel-package_8.059_all.deb

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

iD8DBQE/bfygIbrau78kQkwRAlEcAJ9cSoL6wj21ozUHls2A/tyNISxQTwCfYQff
vMwnhQ4m7y2SLRQNiBOu8jE=
=jiWR
-END PGP SIGNATURE-


Accepted:
kernel-package_8.059.dsc
  to pool/main/k/kernel-package/kernel-package_8.059.dsc
kernel-package_8.059.tar.gz
  to pool/main/k/kernel-package/kernel-package_8.059.tar.gz
kernel-package_8.059_all.deb
  to pool/main/k/kernel-package/kernel-package_8.059_all.deb


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

Accepted gcc-avr 1:3.2.90.20030512-0.1 (source hppa)

2003-09-21 Thread LaMont Jones

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 13:09:18 -0600
Source: gcc-avr
Binary: gcc-avr
Architecture: hppa source
Version: 1:3.2.90.20030512-0.1
Distribution: unstable
Urgency: low
Maintainer: LaMont Jones [EMAIL PROTECTED]
Changed-By: LaMont Jones [EMAIL PROTECTED]
Description: 
 gcc-avr- The GNU C compiler (cross compiler for avr).
Closes: 207189 207493
Changes: 
 gcc-avr (1:3.2.90.20030512-0.1) unstable; urgency=low
 .
   * NMU
   * Add toolchain-source build-depends.  Closes: #207189, #207493
Files: 
 0f1b53182793b6e35d5565d264c6285d 3216996 devel extra 
gcc-avr_3.2.90.20030512-0.1_hppa.deb
 7978cda0219800efe8415e40bcc872c4 4651 devel extra gcc-avr_3.2.90.20030512-0.1.diff.gz
 ac92f523de50942d7005bdc26e92d5f8 806 devel extra gcc-avr_3.2.90.20030512-0.1.dsc

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

iD8DBQE/bf/dzN/kmwoKyScRAiDuAKCct3xROzbn3d+iZyADc9hUdBEs9wCeORoa
PRZC1mkYmmchgDqSovJG96U=
=B8WD
-END PGP SIGNATURE-


Accepted:
gcc-avr_3.2.90.20030512-0.1.diff.gz
  to pool/main/g/gcc-avr/gcc-avr_3.2.90.20030512-0.1.diff.gz
gcc-avr_3.2.90.20030512-0.1.dsc
  to pool/main/g/gcc-avr/gcc-avr_3.2.90.20030512-0.1.dsc
gcc-avr_3.2.90.20030512-0.1_hppa.deb
  to pool/main/g/gcc-avr/gcc-avr_3.2.90.20030512-0.1_hppa.deb


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

Accepted gnus 5.10.2-5 (all source)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Sun, 21 Sep 2003 14:34:05 -0500
Source: gnus
Binary: gnus
Architecture: source all
Version: 5.10.2-5
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava [EMAIL PROTECTED]
Changed-By: Manoj Srivastava [EMAIL PROTECTED]
Description: 
 gnus   - A versatile News and mailing list reader for Emacsen.
Closes: 208968
Changes: 
 gnus (5.10.2-5) unstable; urgency=low
 .
   * No longer conflict with flim -- instead, conflict with older versions
 of  flim, semi, wemi, and t-gnus.closes: Bug#208968
Files: 
 d9f70e62f1194d27e2eb7eefb4d12d67 565 news optional gnus_5.10.2-5.dsc
 ebf24033bdd279a91895031a3f2ad451 20686 news optional gnus_5.10.2-5.diff.gz
 117d8d5740e350d4ce12a40e13dc1227 2093320 news optional gnus_5.10.2-5_all.deb

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

iD8DBQE/bgY3Ibrau78kQkwRAqhEAKC6W9Ax6hK5nxfNbEIwnVie6iu02QCgwbW6
PzDc4iiZxgRmTh0kBnFX9yI=
=bBza
-END PGP SIGNATURE-


Accepted:
gnus_5.10.2-5.diff.gz
  to pool/main/g/gnus/gnus_5.10.2-5.diff.gz
gnus_5.10.2-5.dsc
  to pool/main/g/gnus/gnus_5.10.2-5.dsc
gnus_5.10.2-5_all.deb
  to pool/main/g/gnus/gnus_5.10.2-5_all.deb


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

Accepted psgml 1.3.1-4 (all source)