The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 287 (new: 2)
Total number of packages offered up for adoption: 83 (new: 2)
Total number of packages requeste
David Pashley <[EMAIL PROTECTED]>
> Out of interest, if[0] that is saying that "we agree that anything isn't
> Sun's fault isn't Sun's fault" (which is fair enough) then that doesn't
> mention anything about any warranty that we might offer. For the large
> majority of the software we ship, we disc
raw answers...
> Who does decide which files are being imported?
I would say the team who administers the server (what we defined as
"Administrators" in the infrastructure targets). This is of course
coordinated with the upstream itself, to determine what notification
method they prefer.
An alte
On Thu, Jun 08, 2006 at 08:50:32PM -0400, Joshua D. Abraham wrote:
> * Package name : Nmap::Parser
> * URL : http://search.cpan.org/~apersaud/Nmap-Parser-1.05/Parser.pm
I guess the package should be named libnmap-parser-perl like all
other Perl module packages.
Cf. also
http://www.debian.org/doc/
On Wed, Jun 07, 2006 at 08:52:13AM +0200, Christian Perrier wrote:
> > If the content we're merging is free, there's no problem show this to the
> > reviewer and let him accept or refuse the translation. It's way simpler to
> > do
> > than rewrite everything again. If the translation was overwritt
Tyler MacDonald wrote:
> I moved the server because wedohosting.com's bandwidth fees were
> getting prohibitive (i'm with iweb.ca now).. otherwise I would have been
> happy to have it continue running for another few thousand days. :-)
I find that Tera-Byte.com in Edmonton has nice colo rate
Package: wnpp
Version: NA; reported 2006-06-8
Severity: wishlist
* Package name : Nmap::Parser
Version : 1.05
Upstream Author : Anthony G Persaud <[EMAIL PROTECTED]>
* URL : http://search.cpan.org/~apersaud/Nmap-Parser-1.05/Parser.pm
* License : GPL
Description :
This module implements a interfac
On Thu, Jun 08, 2006 at 05:57:22PM -0700, Tyler MacDonald wrote:
> This is the most sensible answer I've heard about this (and I've
> bitched about the limitation a lot). Maybe it's time for me to delve into
> the kernel source for the first time in 10 years.
I gather this was "fixed" in Linux 2.5
James Westby <[EMAIL PROTECTED]> writes:
>> It is true that gnutls uses libgcrypt, but libgcrypt doesn't provide
>> anything like the same symbols as libcrypto.
>
> What functionality are you after? libgcrypto provides most of the
> ciphers of libcrypto (the big players at least) as well as hash e
On (08/06/06 16:47), Thomas Bushnell BSG wrote:
>
> Is there a GPL-compatible libcrypto replacement? The only libcrypto I
> know of is the one bundled with openssl, which AFAICT is under the
> same license as openssl itself, which is GPL-incompatible.
Correct.
> We have gnutls as a replacement
Anthony Towns wrote:
> No it wouldn't; it'd just require you to have two extra ints, and something
> that
> ran every so often (and as part of any syscall that tells userspace the
> uptime),
> that does:
>
> static unsigned last_uptime = 0;
> static unsigned wraps = 0;
> if (u
Ron Johnson <[EMAIL PROTECTED]> writes:
> Would it be statically linked?
No. Take a look at the symbols in libcrypto, and notice that they are
not in any of those libraries.
It is the case that libssl requires libcrypto, and that
libgnutls-openssl does not need anything like that.
But libcrypt
On Thu, Jun 08, 2006 at 10:39:48PM +0300, Lars Wirzenius wrote:
> Fixing this would require having every increment of the jiffies counter
> to check for overflow, and using two counters. This is unnecessary
> overhead (a very small overhead, granted, but still), for a very small
> benefit.
No it w
Hi all, I got an FTBFS bug yesterday;
On Thu, 8 Jun 2006 08:13:53 +0200, Bastian Blank wrote:
> Package: lynx-cur
> Version: 2.8.6dev18-1
> Severity: serious
>
> There was an error while trying to autobuild your package:
...
> > install -m 755 debian/lynx
> > /build/buildd/lynx-cur-2.8.6dev18/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Bushnell BSG wrote:
> Is there a GPL-compatible libcrypto replacement? The only libcrypto I
> know of is the one bundled with openssl, which AFAICT is under the
> same license as openssl itself, which is GPL-incompatible.
>
> We have gnutls as
Tyler MacDonald wrote:
> I moved the server because wedohosting.com's bandwidth fees were
> getting prohibitive (i'm with iweb.ca now).. otherwise I would have been
> happy to have it continue running for another few thousand days. :-)
>
I don't suppose you could have moved it while still r
Is there a GPL-compatible libcrypto replacement? The only libcrypto I
know of is the one bundled with openssl, which AFAICT is under the
same license as openssl itself, which is GPL-incompatible.
We have gnutls as a replacement for openssl itself, but what about
libcrypto?
(Indeed, some things
Steinar H. Gunderson <[EMAIL PROTECTED]> wrote:
> > It was finally retired today, after 875 days of uptime, not because there
> > was a problem with it, just because there was a price problem with the
> > hosting provider it's colocated at. For an "unstable" distribution, it gave
> > me the most st
On Thu, Jun 08, 2006 at 11:29:21AM -0700, Tyler MacDonald wrote:
> It was finally retired today, after 875 days of uptime, not because there
> was a problem with it, just because there was a price problem with the
> hosting provider it's colocated at. For an "unstable" distribution, it gave
> me th
Ron Johnson <[EMAIL PROTECTED]> wrote:
> > That production server has been running debian/unstable since it's inception
> > in january of 2004, with dselect updates happening every couple of days. It
> > was running apache, postfix, mysql, mydns. Despite being "unstable", there
> > was never a prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tyler MacDonald wrote:
> http://www.crackerjack.net/adserton3.png
>
> That production server has been running debian/unstable since it's inception
> in january of 2004, with dselect updates happening every couple of days. It
> was running apache, post
Sebastian Harl, 2006-06-08 21:10:11 +0200 :
>> http://www.crackerjack.net/adserton3.png
>
> On that picture it says the box is up for 378 days. How does that go
> with 875 days idle time?
Old Linux kernels have their uptime roll over at about 497 days
(which is like 2^32 ticks of a hundredth of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Harl wrote:
>> http://www.crackerjack.net/adserton3.png
>
> On that picture it says the box is up for 378 days. How does that go with 875
> days idle time?
zoom in
- --
e-mail: Miguel Gea Milvaques <[EMAIL PROTECTED]>
Blog: http://www.
On Thu, Jun 08, 2006 at 12:20:03PM -0700, Tyler MacDonald wrote:
> Due to a bug with "w", or the kernel, or whatever, which nobody seems to
> want to fix, the system uptime wraps around to 0 days after 400-and-someodd
> days. That's why I circled the login/idle time on the screenshot. :-)
The jiff
to, 2006-06-08 kello 12:20 -0700, Tyler MacDonald kirjoitti:
> Sebastian Harl <[EMAIL PROTECTED]> wrote:
> > > http://www.crackerjack.net/adserton3.png
> >
> > On that picture it says the box is up for 378 days. How does that go with
> > 875 days idle time?
> >
>
> Due to a bug with "w", or the
Sebastian Harl <[EMAIL PROTECTED]> wrote:
> > http://www.crackerjack.net/adserton3.png
>
> On that picture it says the box is up for 378 days. How does that go with
> 875 days idle time?
>
Due to a bug with "w", or the kernel, or whatever, which nobody seems to
want to fix, the system uptime wra
> http://www.crackerjack.net/adserton3.png
On that picture it says the box is up for 378 days. How does that go with 875
days idle time?
Cheers,
Sebastian
--
Sebastian "tokkee" Harl
GnuPG-ID: 0x8501C7FC
http://tokkee.org/
signature.asc
Description: Digital signature
Le mercredi 07 juin 2006 à 12:18 +0100, Ian Jackson a écrit :
> Jeremy Hankins writes ("Non-DD's in debian-legal"):
> > I'm not sure I understand this part, though. Do you think that folks
> > like myself, who are not DD's, should not participate in the discussions
> > on d-l?
>
> Actually, I thi
On Thu, Jun 08, 2006 at 02:47:24PM +1000, Anthony Towns wrote:
> On Wed, Jun 07, 2006 at 09:07:07AM -0500, John Goerzen wrote:
> > So what am I trying to do?
> > Most importantly, make sure that SPI and Debian aren't exposed to
> > serious legal risks.
> Then why don't you contact Greg and the SPI
http://www.crackerjack.net/adserton3.png
That production server has been running debian/unstable since it's inception
in january of 2004, with dselect updates happening every couple of days. It
was running apache, postfix, mysql, mydns. Despite being "unstable", there
was never a problem that resu
My broken wrist has healed -- yeah! -- so I'm back from that
`vacation', and now I'm on my way to Montréal for a week.
Cheers,
Shaun
On Jun 08, 2006 at 12:19, MJ Ray praised the llamas by saying:
> Wouter Verhelst <[EMAIL PROTECTED]>
> > On Wed, Jun 07, 2006 at 05:42:27PM +0100, MJ Ray wrote:
> > > Exactly! It's not our fault, so why should we indemnify Sun against it?
> >
> > If it's not our fault, it's not under our control,
Hi Pasi,
The situation:
I have a file server running on Sarge AMD64 connected
with a 1GBit interface to a GBit uplink off the switch.
Do not think that this sounds like a common problem. It isn't!!!
Btw what switch do you have?
There is a known problem in HP switches where traffic from port
* Gordon Grubert <[EMAIL PROTECTED]> [060607 21:30]:
> The most interesting fact is, that I obtain about 10MB/s with
> my Debian client if I connect the file server to a 100MBit Port
> on the switch.
You might also want to try another GB switch to see if that has the same
problem. NFS seems to do
On Wed, Jun 07, 2006 at 03:25:10PM +0200, Gordon Grubert wrote:
> Dear Debian developers,
>
> it seems that there is a little problem with the NFS client
> in Debian sarge. I hope this is the best place to post this
> problem. I have discussed this on
> http://lists.debian.org/debian-user-german/2
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the package maintainer(s)
and to other interested parties to accompany the original report.
Your message has been sent to the package maintainer(s):
Luca Capello <[EMAIL PROTECTED]>
Processing commands for [EMAIL PROTECTED]:
> tags 356948 + help
Bug#356948: stumpwm: Clarify README.Debian - can't understand a thing how to
start this wm
There were no tags set.
Tags added: help
> retitle 356948 stumpwm: clarify how to start this WM in the README.Debian
Bug#356948: stumpwm: Cla
tags 356948 + help
retitle 356948 stumpwm: clarify how to start this WM in the README.Debian
thanks
Hello!
For d-d: I'd like a more general advice about the user request, which
I'm quite reluctant to accomplish.
For all: please honor the R-T and M-F-T headers (no need to cc: me).
On Fri, 02 Jun
Wouter Verhelst <[EMAIL PROTECTED]>
> On Wed, Jun 07, 2006 at 05:42:27PM +0100, MJ Ray wrote:
> > Exactly! It's not our fault, so why should we indemnify Sun against it?
>
> If it's not our fault, it's not under our control, and we *don't* need
> to indemnify. That's what the FAQ says; and whethe
I have a file server running on Sarge AMD64 connected
with a 1GBit interface to a GBit uplink off the switch.
Do not think that this sounds like a common problem. It isn't!!!
...
The most interesting fact is, that I obtain about 10MB/s with
my Debian client if I connect the file server to a 10
Package: wnpp
Severity: wishlist
Owner: Mark Purcell <[EMAIL PROTECTED]>
* Package name: codeine
Version : 1.0.1-3
Upstream Author : Max Howell <[EMAIL PROTECTED]>
* URL : http://www.methylblue.com/codeine/
* License : GPL
Programming Lang: C++
Description
Package: wnpp
Severity: wishlist
Owner: Andrew McMillan <[EMAIL PROTECTED]>
The maintainer of this package has not updated it for nearly a year and
has been put on hold in the NM queue due to being uncontactable.
I have uploaded a newer version as an NMU, but unless someone
strenuously objects I
Selon Martin Michlmayr <[EMAIL PROTECTED]>:
> * Matthias Klose <[EMAIL PROTECTED]> [2006-06-07 02:20]:
> > We did pick two compiler warnings and scanned the build logs of one
> > archive rebuild on alpha (64bit), where wrong code may be generated.
> > These warnings can be found in 1600 packages [
On Wed, Jun 07, 2006 at 05:42:27PM +0100, MJ Ray wrote:
> Wouter Verhelst <[EMAIL PROTECTED]>
> > Alternatively, I don't think it's hard for a judge to understand that
> > there is this piece of software which we indeed do distribute, but which
> > is used by many other people as well, and they all
On 6/7/06, Martin Michlmayr <[EMAIL PROTECTED]> wrote:
* Matthias Klose <[EMAIL PROTECTED]> [2006-06-07 02:20]:
> We did pick two compiler warnings and scanned the build logs of one
> archive rebuild on alpha (64bit), where wrong code may be generated.
> These warnings can be found in 1600 packag
Package: wnpp
Severity: wishlist
Owner: Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: cpm
Version : 0.22beta
Upstream Author : Harry Brueckner <[EMAIL PROTECTED]>
* URL : http://www.harry-b.de/dokuwiki/doku.p
On Tue, Jun 06, 2006 at 05:00:26PM +0300, Linas ??virblis wrote:
> Mike Hommey wrote:
>
> > Could you tell us what kind of harm can do a "hidden" empty file in /usr ?
>
> First of all, false positives in rootkit and security scanners. And too
> many false positives lead to false negatives sooner
47 matches
Mail list logo
