Re: Thoughts about changing Debian's release process

2005-04-09 Thread Andrew Pollock
On Thu, Apr 07, 2005 at 08:09:16PM +0200, Torsten Landschoff wrote:
> 
> Yep. The problem is that you need umpteen iterations for the
> installation and you'll end up changing the FAI setup, installing,
> waiting half an hour, testing, doesn't work, change FAI, repeat.

Been there, done that, got the t-shirt :-(
 
It is one of the deficiencies of FAI, but also why the documentation says to
plan your installation :-)

That said, I've had a preliminary look at gluck, and the fact that it has a
SmartArray and funny device names is going to make testing out a FAI install
rather interesting for me...

regards

Andrew


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



Re: Thoughts about changing Debian's release process

2005-04-09 Thread Andrew Pollock
On Thu, Apr 07, 2005 at 08:10:58PM +0200, Torsten Landschoff wrote:
> On Thu, Apr 07, 2005 at 09:36:36AM +0200, Wouter Verhelst wrote:
> > > sausage-machine style. Then of course you need to keep it up to date as
> > > well.
> > 
> > I think that last phrase is the major problem...
> 
> Yep, likewise. I still think having each part of our infrastructure as a
> package would be a good solution but I can't currently volunteer for
> that.
> 

Yeah, I'm thinking this is a more feasible approach than FAI now that I put
a bit of thought into it. Any given Debian box does a whole bunch of things,
and you want to be able to take (using the example) packages.d.o and move
it, so if all the infrastructure for packages.d.o was in a package, you'd be
laughing. You could then reshuffle services between boxes very easily.

regards

Andrew


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



Re: Why do we still have this on the distribution?

2005-04-09 Thread Andrew Pollock
On Fri, Apr 08, 2005 at 04:16:18PM +0200, Martin Schulze wrote:
> 
> FWIW: This would mean to remove all of Mozilla and friends, since they
> don't receive any security support upstream, and neither the maintainer
> or the security team are in a position to backport all fixes and correcte
> all stuff in the older versions.  (upstream does only support the most
> recent version, which will be different about one month after the sarge
> release).
> 

This is the sort of stuff suited for volatile, for this very reason.

regards

Andrew


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



Re: Work-needing packages report for Apr 8, 2005

2005-04-09 Thread Nico Golde
Hallo Frank,

* Frank Lichtenheld <[EMAIL PROTECTED]> [2005-04-09 11:10]:
> On Fri, Apr 08, 2005 at 03:41:24PM +0200, Nico Golde wrote:
> > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2005-04-08 14:05]:
> > [...] 
> > >acl-installer (#297344), orphaned 38 days ago
> > >  Description: Installer for Franz' Allegro 6.2 Lisp Trial Edition
> > >  Reverse Depends: acl-mlisp acl-mlisp8 acl-alisp8 acl-alisp acldoc-el
> > > 
> > >admesh (#297345), orphaned 38 days ago
> > 
> > A question I ask me any time I get this mail:
> > Why are there packages listed which have no Description?
> > Is it a bug in the script, in the package or do I forget 
> > something?
> 
> The descriptions are extracted from the bug subject. #297345
> has "O: admesh" so clearly nothing to extract there ;) 

Ok thanks.

> Feel
> free to fix any of those WNPP bugs.

Maybe, if i have the time...
Regards Nico
-- 
Nico Golde - [EMAIL PROTECTED] | GPG: 1024D/73647CFF
http://www.ngolde.de | http://www.muttng.org | http://grml.org 
VIM has two modes - the one in which it beeps 
and the one in which it doesn't -- encrypted mail preferred


pgpkrQsTXrknR.pgp
Description: PGP signature


Re: Thoughts about changing Debian's release process

2005-04-09 Thread Henning Glawe
On Sat, Apr 09, 2005 at 05:15:34PM +1000, Andrew Pollock wrote:
> On Thu, Apr 07, 2005 at 08:10:58PM +0200, Torsten Landschoff wrote:
> > On Thu, Apr 07, 2005 at 09:36:36AM +0200, Wouter Verhelst wrote:
> > > > sausage-machine style. Then of course you need to keep it up to date as
> > > > well.
> > > 
> > > I think that last phrase is the major problem...
> > 
> > Yep, likewise. I still think having each part of our infrastructure as a
> > package would be a good solution but I can't currently volunteer for
> > that.
> > 
> 
> Yeah, I'm thinking this is a more feasible approach than FAI now that I put
> a bit of thought into it. Any given Debian box does a whole bunch of things,
> and you want to be able to take (using the example) packages.d.o and move
> it, so if all the infrastructure for packages.d.o was in a package, you'd be
> laughing. You could then reshuffle services between boxes very easily.

... which I do at my department using fai-update-system ;)
packaging configuration files is not really a good idea: it is too hard to
change them.
take a setup with FAI and cvs stored configuration files, and you can change
your config easily, are motivated to document the purpose of your changes and
push them easily to your clients...
ATM I am using pserver for the clients' read-only cvs access, because I
consider my net trusted. but using cvs over ssh should work too.

the main problem is: for the initial installation, you need a way to transfer
an ssh key for config space access; maybe fai-bootcd would be a solution for
this: it puts the whole installer root on a cd, so you don't even need a way
for safely doing nfs...
-- 
c u
henning


signature.asc
Description: Digital signature


openswan 2.3.1 is now available - Call for Help

2005-04-09 Thread Rene Mayrhofer
Hi all,

[Please CC me in replies, I am currently not subscribed to this list.]

Since yesterday, openswan upstream 2.3.1 is on the download servers, and it 
should supposedly fix the problems of 2.3.0 (specifically that it caused all 
other openswan daemons, be it 2.2.0 or 2.3.0, to crash in some cases) that 
prevented me from pushing that version into testing (and subsequently led to 
the removal of openswan from testing). I am currently working hard on 
updating the package to 2.3.1 (which unfortunately again changed the source 
tree layout, sigh) and will then go through the bug reports and check if 
2.3.1 fixes them. 
Since we are very late in the sarge release process, I know well that it is an 
extremely bad time for updating to new upstream versions. Nonetheless, I 
really think that openswan (a working version) should be part of the new 
stable and am now trying to get this back into testing. 

I will probably need some help with this to do it in the next few days. 
Anybody who is using freeswan or openswan right now and is interested in 
having it in testing (and unstable, in fact), please help. I could definitely 
use help in testing, but anybody who wants to work on packaging itself is of 
course also welcome (e.g. on the minor bugs like debconf translations).

If I am completely wrong in trying this now, at the current stage of the 
release cycle, then please tell me now and I'll use my weekend for something 
else and only work on getting this into unstable during next week

with best regards,
Rene


pgpEWsPxC97z8.pgp
Description: PGP signature


Re: Why do we still have this on the distribution?

2005-04-09 Thread Martin Schulze
Andrew Pollock wrote:
> On Fri, Apr 08, 2005 at 04:16:18PM +0200, Martin Schulze wrote:
> > 
> > FWIW: This would mean to remove all of Mozilla and friends, since they
> > don't receive any security support upstream, and neither the maintainer
> > or the security team are in a position to backport all fixes and correcte
> > all stuff in the older versions.  (upstream does only support the most
> > recent version, which will be different about one month after the sarge
> > release).
> > 
> 
> This is the sort of stuff suited for volatile, for this very reason.

Judging from the concept of volatile.debian.net, no.  It's rather for
unsupported.debian.net or something which needs to be started.

Regards,

Joey

-- 
WARNING: Do not execute!  This call violates patent DE10108564.
http://www.elug.de/projekte/patent-party/patente/DE10108564

wget -O patinfo-`date +"%Y%m%d"`.html http://patinfo.ffii.org/

Please always Cc to me when replying to me on the lists.


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



Re: Bug#303725: specter: FTBFS (amd64/gcc-4.0): syntax error before '{' token

2005-04-09 Thread Bill Allombert
On Fri, Apr 08, 2005 at 07:23:52PM +0200, Verdan wrote:
> Hello
> 
> > With the attached patch 'specter' can be compiled
> > on amd64 using gcc-4.0.
> 
> It's not so easy. It was done that way to allow specter compile on gcc
> 2.95. This patch makes it impossible, so I hesitate to apply it.

How is it relevant to the Debian package ?

> Moreover fourth version of gcc is really experimental, and if I had to
> choose specter compiling on 4 or 2.95 version I would choose 2.95.
> For telling truth I don't know what to do now; upstream doesn't aprove
> this patch and won't include it in 1.4pre2 version of specter.
> I consider setting ,,wontfix'' tag.
> What do You think about that ?

Debian packages are not required to build with gcc 2.95.
They are not required either to build with gcc 4.0 for sarge, but will
be for etch. It is a better policy to be proactive than to wait until 
problems do happen.

Moreover fixing this bug means fixing compilation with gcc-4.0, not 
applying the patch provided by the submitter. If the patch has issues
you can reject it, and work with the submitter to write a better one.

Furthermore, there is no technical reason why the patch cannot work with
both 4.0 and 2.95. At worse a bit of cpp magic will fix that.

In the case at hand you could add a macro ENTRY like

#ifdef __GNUC__ 
#if __GNUC__ >= 4
#define ENTRY(base,name,dat) .base.name.dat = dat
#else
#define ENTRY(base,name,dat) .base.{name.dat = dat}
#endif
#endif

and replace 
.value{.ptr = static_values.if_modified_since }}
by
ENTRY(value,ptr,static_values.if_modified_since)

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here.


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



Bug#303891: ITP: gcfilms -- a GTK2 application for managing dvd and video collections

2005-04-09 Thread Alexander Wirt
Package: wnpp
Severity: wishlist
Owner: Alexander Wirt <[EMAIL PROTECTED]>

* Package name: gcfilms
  Version : 4.8
  Upstream Author : Tian <[EMAIL PROTECTED]>
* URL : https://gna.org/projects/gcfilms/
* License : GPL
  Description : a GTK2 application for managing dvd and video collections

gcfilms is a program for managing dvd and video collections. 
It 
 * retrieves and display movie informations from severeal 
   online sources like amazon or imdb
 * can import movie informations from Ant oder DVD Profiler collections
 * can export movie informations to CSV, HTML, SQL or XML
 * has a flexible plugin system for export, import or search plugins
 * has a borrower system to track where are movies are


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


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



Bug#303892: ITP: log4cxx -- A logging library for C++

2005-04-09 Thread Andreas Fester
Package: wnpp
Severity: wishlist
Owner: Andreas Fester <[EMAIL PROTECTED]>


* Package name: log4cxx
  Version : 0.9.7
  Upstream Author : Michael Catanzariti <[EMAIL PROTECTED]>
Edmond Nolan <[EMAIL PROTECTED]>
* URL : http://logging.apache.org/site/binindex.html
* License : Apache License Version 2.0
  Description : A logging library for C++

Log4cxx is the C++ port of log4j, a widely used logging library for
Java. Log4cxx attempts to mimic log4j usage as much as the language
will allow and to be compatible with log4j configuration and output formats.

Since log4j is already in Debian its natural to also 
include its C++ port. Additionally this could close Bugs #288336 and
#288337 in the long term because log4cpp is orphaned and the upstream
is not maintained anymore. Log4cxx is better maintained, and
a new version is in progress. Log4cxx should therefore replace
log4cpp.

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


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



Re: debram and packages temporarily absent from sarge

2005-04-09 Thread Thaddeus H. Black
For those following this thread [1], the advice I have
received suggests option (3),

>   (3) to purge metadata for packages not presently in
>   sarge.

and no one suggests otherwise, so this is what I have
done.  With Giacomo Catenazzi's sponsorship, the
resultant final debram (0.6.4) is in sid now.

Several people have mailed me asking that metadata for
certain binaries be added or retained not purged; and I
have honored these requests.  Thus, in addition to all
of sarge testing main (i386) 2 April 2005, the final
debram (0.6.4) also ramifies the following:

belocs-locales-bin belocs-locales-data
gaim-extendedprefs gaim-themes libuniconf4.0
libwvstreams-dev libwvstreams4.0-base
libwvstreams4.0-doc libwvstreams4.0-extras
libwvstreams4.0-fft libwvstreams4.0-qt
libwvstreams4.0-speex libwvstreams4.0-vorbis retchmail
uniconf-tools uniconfd wvdial

-- 
Thaddeus H. Black
508 Nellie's Cave Road
Blacksburg, Virginia 24060, USA
+1 540 961 0920, [EMAIL PROTECTED]

[1] http://lists.debian.org/debian-devel/2005/04/msg00161.html


pgpeTyUxcopep.pgp
Description: PGP signature


ITP: kpopup -- sending and receiving with Microsoft WinPopup (using Samba)

2005-04-09 Thread Markus Fischer
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Markus Fischer <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: ITP: kpopup -- sending and receiving with Microsoft WinPopup (using 
Samba)
X-Mailer: reportbug 3.9
Date: Sat, 09 Apr 2005 16:17:45 +0200
X-Debbugs-Cc: debian-devel@lists.debian.org

Package: wnpp
Severity: wishlist
Owner: none 


* Package name: kpopup
  Version : 0.9.7
  Upstream Author : Henschel
* URL : http://www.henschelsoft.de/
* License : GPL
  Description : sending and receiving with Microsoft WinPopup (using 
Samba)

(Include the long description here.)

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


pgpFm4GhS51m1.pgp
Description: PGP signature


Re: Bug#303725: specter: FTBFS (amd64/gcc-4.0): syntax error before '{' token

2005-04-09 Thread Verdan
Hello,

Day Sat, 9 Apr 2005 07:40:04 -0500
Bill Allombert <[EMAIL PROTECTED]> wrote:

> Furthermore, there is no technical reason why the patch cannot work
> with both 4.0 and 2.95. At worse a bit of cpp magic will fix that.

It's done, new patch has been written, that provide successful
compilation on gcc-2.95 and gcc-4.0.
specter package with new patch applied will be uploaded afer
official 1.4pre1 release, which is coming soon. 

Best regards,
 Grzegorz ,,Verdan'' Bizon

-- 
[  ,''`.  [EMAIL PROTECTED] // [EMAIL PROTECTED] ]
[ : :' :  GG: 830398 //   JID: verdan(at)chrome.pl ]
[ `. `'   [EMAIL PROTECTED]  //GPG: 0xDF32F531 ]
[   `-  1A6F A0A1 01D1 3033 332A  60FE 4C7B 8037 DF32 F531 ]


pgp9rrGeUl6Bp.pgp
Description: PGP signature


Re: dynamic partial mirror, apt-get fails

2005-04-09 Thread Cristian Barbarosie
On Thu, 7 Apr 2005, Wouter Verhelst wrote:
> Apt-cacher is written in perl. Install it on your Debian box, edit the
> CGI script to modify some paths, and copy that to the HTTP server.

Do you think I can do that wihtout being root on the http server ?

> Alternatively, just install it on a Debian box, point sources.list files
> to that box, and do not shut it down. That's what I do.

This might be a solution. Actually, my linux boxes are all behind a
firewall and I all their ports are disabled except port 22 (for ssh).
But I shall ask our network administrator to see if I can install
an http server to be used from inside the local network only.
If it is possible, then this is the solution.

Thank you for your help. Cristian Barbarosie
__
Professor Auxiliar, DMFCUL  tel. (351) 217904919
CMAF, Av. Prof. Gama Pinto, 2   fax. (351) 217954288
1649-003 Lisboa Portugal
http://cmaf.fc.ul.pt/~barbaros  e-mail [EMAIL PROTECTED]
--




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



Mail loss, please resend

2005-04-09 Thread Colin Watson
In the process of getting my mail back after gluck returned, a mistake
in one of my mail-handling scripts means that I appear to have lost the
best part of four days' worth of mail to [EMAIL PROTECTED] If you
sent anything there that you want me to see, I'd appreciate it if you
could resend.

Thanks,

-- 
Colin Watson   [EMAIL PROTECTED]


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



Re: ddtp.d.o is not alive

2005-04-09 Thread Daniel Macêdo Batista

Em 7/4/2005, "Guilherme de S. Pastore" <[EMAIL PROTECTED]>
escreveu:

>Em Qui, 2005-04-07 às 17:53 -0300, Daniel Macêdo Batista escreveu:
>> Hi!
>
>Hey, Daniel,

Hi!

>
>> Is there any idea to when ddtp.d.o will come back?
>
>The ddtp server is hosted on gluck, which imploded some days ago (disk
>failure?). When I saw that, I even thought about messaging -l10n-pt to
>warn you guys, but didn't have the time to do so, sorry. gluck has been
>put back online today, though, so your problems should already be
>solved. =)
>

Unfortunately the problems weren't solved :(. http://ddtp.debian.org
still is redirect to http://www.debian.org/distrib/ftplist

>Regards,

[]'s

>
>--
>Guilherme de S. Pastore (fatalerror)
><[EMAIL PROTECTED]>
>
>
>--
>To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>



Re: openswan 2.3.1 is now available - Call for Help

2005-04-09 Thread Paul TBBle Hampson
On Sat, Apr 09, 2005 at 01:24:20PM +0200, Rene Mayrhofer wrote:
> Hi all,

> [Please CC me in replies, I am currently not subscribed to this list.]

> Since yesterday, openswan upstream 2.3.1 is on the download servers, and it 
> should supposedly fix the problems of 2.3.0 (specifically that it caused all 
> other openswan daemons, be it 2.2.0 or 2.3.0, to crash in some cases) that 
> prevented me from pushing that version into testing (and subsequently led to 
> the removal of openswan from testing). I am currently working hard on 
> updating the package to 2.3.1 (which unfortunately again changed the source 
> tree layout, sigh) and will then go through the bug reports and check if 
> 2.3.1 fixes them. 

> Since we are very late in the sarge release process, I know well that it is 
> an 
> extremely bad time for updating to new upstream versions. Nonetheless, I 
> really think that openswan (a working version) should be part of the new 
> stable and am now trying to get this back into testing. 

I definately agree with this. ^_^

> I will probably need some help with this to do it in the next few days. 
> Anybody who is using freeswan or openswan right now and is interested in 
> having it in testing (and unstable, in fact), please help. I could definitely 
> use help in testing, but anybody who wants to work on packaging itself is of 
> course also welcome (e.g. on the minor bugs like debconf translations).

I'm interested in testing the new version, although the problem I was
suffering was a windows interoperability bug (Win2K Ipsec would crash
pluto) which I reported to the Openswan list and was told it would
probably be fixed in 2.3.1. I've built from the debian/ directory in CVS
at the moment, but haven't tried it in a few weeks to see if CVS fixed
my problem.

I also had two 2.3.0 openswans talking to each other for L2TP, but I
didn't see the crashing problem you've mentioned above (and which is to
do with NAT-T if the 2.3.1 changelog is anything to go by), both using
the 2.6 built-in IPSec stack for kernel support.

-- 
---
Paul "TBBle" Hampson, MCSE
8th year CompSci/Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
[EMAIL PROTECTED]

"No survivors? Then where do the stories come from I wonder?"
-- Capt. Jack Sparrow, "Pirates of the Caribbean"

This email is licensed to the recipient for non-commercial
use, duplication and distribution.
---


pgpRKYMKLgqnK.pgp
Description: PGP signature


Re: dynamic partial mirror, apt-get fails

2005-04-09 Thread Wouter Verhelst
On Sat, Apr 09, 2005 at 03:20:21PM +0100, Cristian Barbarosie wrote:
> On Thu, 7 Apr 2005, Wouter Verhelst wrote:
> > Apt-cacher is written in perl. Install it on your Debian box, edit the
> > CGI script to modify some paths, and copy that to the HTTP server.
> 
> Do you think I can do that wihtout being root on the http server ?

I don't see why not.

-- 
 EARTH
 smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
 WATER
 -- with thanks to fortune


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



Re: acenic firmware rewrite

2005-04-09 Thread Andres Salomon
On Thu, 07 Apr 2005 01:11:38 +0200, Peter 'p2' De Schrijver wrote:

> Hi,
> 
> Reading http://lists.debian.org/debian-legal/2004/12/msg00078.html I
> wondered if people would be willing to work on a free firmware for the
> Tigon II chip.  I didn't look at the existing code yet, but looking at the
> datasheet
> (http://alteon.shareable.org/firmware-source/12.4.13/tigonbk.pdf.bz2) it
> doesn't seem to be a very complicated chip to code for. I'm not sure
> however, how to handle the development in such a way the resulting
> firmware can be released under a free license without any legal risks. I
> have 2 PCI boards with the Tigon II chip and a 1000BaseSX PHY. I also have
> an Ace Director III loadbalancer which consist of 10 Tigon II chips. 8 of
> those are used for 100BaseT interfaces, 1 has a 1000BaseSX PHY and the
> 10th is used as a system controller.
> 

I can't imagine there would be any issues if you released both the source
and binary, and licensed them under the GPL.  The firmware source and
binary can both be distributed in the kernel (with the binary actually in
the driver source code).





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



Re: acenic firmware rewrite

2005-04-09 Thread Peter 'p2' De Schrijver
On Sat, Apr 09, 2005 at 01:13:57PM -0400, Andres Salomon wrote:
> On Thu, 07 Apr 2005 01:11:38 +0200, Peter 'p2' De Schrijver wrote:
> 
> > Hi,
> > 
> > Reading http://lists.debian.org/debian-legal/2004/12/msg00078.html I
> > wondered if people would be willing to work on a free firmware for the
> > Tigon II chip.  I didn't look at the existing code yet, but looking at the
> > datasheet
> > (http://alteon.shareable.org/firmware-source/12.4.13/tigonbk.pdf.bz2) it
> > doesn't seem to be a very complicated chip to code for. I'm not sure
> > however, how to handle the development in such a way the resulting
> > firmware can be released under a free license without any legal risks. I
> > have 2 PCI boards with the Tigon II chip and a 1000BaseSX PHY. I also have
> > an Ace Director III loadbalancer which consist of 10 Tigon II chips. 8 of
> > those are used for 100BaseT interfaces, 1 has a 1000BaseSX PHY and the
> > 10th is used as a system controller.
> > 
> 
> I can't imagine there would be any issues if you released both the source
> and binary, and licensed them under the GPL.  The firmware source and
> binary can both be distributed in the kernel (with the binary actually in
> the driver source code).
> 

Sure. That's ok. I was more thinking of someone reading the existing
firmware sources, writing a spec and a second person/group implementing
the new free firmware based on the spec. AFAICS the implementors and the
spec writers should be different people/groups. Or do you think it would
be ok if the same people read the existing non-free sources and reimplement 
its functionality in a new free firmware ?

Thanks,

Peter (p2).


signature.asc
Description: Digital signature


Re: acenic firmware rewrite

2005-04-09 Thread Andres Salomon
On Sat, 09 Apr 2005 19:26:09 +0200, Peter 'p2' De Schrijver wrote:

[...]
> Sure. That's ok. I was more thinking of someone reading the existing
> firmware sources, writing a spec and a second person/group implementing
> the new free firmware based on the spec. AFAICS the implementors and the
> spec writers should be different people/groups. Or do you think it would
> be ok if the same people read the existing non-free sources and
> reimplement its functionality in a new free firmware ?
> 

Ah, yes, a cleanroom implementation would work for that.  The spec writer
and code writers should definitely be different people.

Before you get started on this, however, let's see if we can't get some
clarification on the license of the firmware source
(http://wiki.debian.net/?KernelFirmwareLicensing).



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



Re: acenic firmware rewrite

2005-04-09 Thread John Hasler
Peter 'p2' De Schrijver wrote:
> I didn't look at the existing code yet, but looking at the datasheet
> (http://alteon.shareable.org/firmware-source/12.4.13/tigonbk.pdf.bz2) it
> doesn't seem to be a very complicated chip to code for. I'm not sure
> however, how to handle the development in such a way the resulting
> firmware can be released under a free license without any legal risks.

Unless you've signed an NDA you're fine.  Just do it.
-- 
John Hasler


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



Re: acenic firmware rewrite

2005-04-09 Thread John Hasler
Peter 'p2' De Schrijver writes:
> I was more thinking of someone reading the existing firmware sources,
> writing a spec and a second person/group implementing the new free
> firmware based on the spec. AFAICS the implementors and the spec writers
> should be different people/groups.

You can do that if you expect the authors of the existing sources to sue
and want an absolutely bulletproof case, but it isn't legally necessary.

> Or do you think it would be ok if the same people read the existing
> non-free sources and reimplement its functionality in a new free
> firmware?

As long as they don't copy any protected code you'll be fine.
-- 
John Hasler


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



Bug#303924: ITP: visitors -- fast web log analyzer

2005-04-09 Thread Romain Francoise
Package: wnpp
Severity: wishlist
Owner: Romain Francoise <[EMAIL PROTECTED]>

* Package name: visitors
  Version : 0.4a
  Upstream Author : Salvatore Sanfilippo 
* URL or Web page : http://www.hping.org/visitors/
* License : GPL
  Description : a fast web server log analyzer

Visitors is a very fast web server log analyzer designed to be run from
the command line, with support for text or html output and real-time
statistics generation.  It can handle most web server logs including
Apache access logs and is very easy to use: no configuration file and no
database are required.  It can also generate visual trail analysis
graphs using Graphviz.

For further information see http://www.hping.org/visitors/>.

-- 
  ,''`.
 : :' :Romain Francoise <[EMAIL PROTECTED]>
 `. `' http://people.debian.org/~rfrancoise/
   `-


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



Re: openswan 2.3.1 is now available - Call for Help

2005-04-09 Thread Rene Mayrhofer
Am Samstag, 9. April 2005 17:31 schrieb Paul TBBle Hampson:
> I'm interested in testing the new version, although the problem I was
> suffering was a windows interoperability bug (Win2K Ipsec would crash
> pluto) which I reported to the Openswan list and was told it would
> probably be fixed in 2.3.1. I've built from the debian/ directory in CVS
> at the moment, but haven't tried it in a few weeks to see if CVS fixed
> my problem.
>
> I also had two 2.3.0 openswans talking to each other for L2TP, but I
> didn't see the crashing problem you've mentioned above (and which is to
> do with NAT-T if the 2.3.1 changelog is anything to go by), both using
> the 2.6 built-in IPSec stack for kernel support.
If you can, then please test as much as you can. My current test packages are 
at
http://www.gibraltar.at/~rene/openswan/

I have tried openswan-modules-source with both 2.4 and 2.6 kernel trees and it 
compiles fine now (many fixes during the last hours...), although I have not 
yet tried the modules that have been built. I still need to try 
kernel-patch-openswan and work further on that earlier crash problem.

with best regards,
Rene


pgpp6HgVkay1f.pgp
Description: PGP signature


Re: Right of a maintainer not to respect FHS

2005-04-09 Thread Tollef Fog Heen
* Don Armstrong 

| The maintainer is primarily responsible for the severity levels of the
| bugs in their package. Basically, the only exception[1] to this are
| the RMs, who may decide that a bug needs to be above or below the RC
| threshold.[2]

Actually, they can say a bug is RC even if it's not a bug of the
«RC-severities», or the other way around (aka «sarge-ignore»).

-- 
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about who its friends are  : :' :
  `. `' 
`-  


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



Re: openswan 2.3.1 is now available - Call for Help

2005-04-09 Thread Rene Mayrhofer
Am Samstag, 9. April 2005 22:32 schrieb Rene Mayrhofer:
> If you can, then please test as much as you can. My current test packages
> are at
> http://www.gibraltar.at/~rene/openswan/
I have just uploaded new packages with a small change in kernel-patch-openswan 
(a file was missing). If anybody has already downloaded this package, please 
re-get it,

with best regards,
Rene


pgphkJO4dhA4M.pgp
Description: PGP signature


Bug#303941: ITP: raster3d -- tools for generating images of proteins or other molecules

2005-04-09 Thread Nelson A. de Oliveira
Package: wnpp
Severity: wishlist
Owner: "Nelson A. de Oliveira" <[EMAIL PROTECTED]>


* Package name: raster3d
  Version : 2.7c
  Upstream Author : Ethan A. Merritt <[EMAIL PROTECTED]>
* URL : http://www.bmsc.washington.edu/raster3d/raster3d.html
* License : None specified. Permission granted to distribute on Debian
  Description : tools for generating images of proteins or other molecules

 Raster3D is a set of tools for generating high quality raster images of
 proteins or other molecules. The core program renders spheres, triangles,
 cylinders, and quadric surfaces with specular highlighting, Phong shading,
 and shadowing. It uses an efficient software Z-buffer algorithm which is
 independent of any graphics hardware. Ancillary programs process atomic
 coordinates from PDB files into rendering descriptions for pictures composed
 of ribbons, space-filling atoms, bonds, ball+stick, etc. Raster3D can also be
 used to render pictures composed in other programs such as Molscript in
 glorious 3D with highlights, shadowing, etc. Output is to pixel image files
 with 24 bits of color information per pixel.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-mm1-biolinux1
Locale: LANG=pt_BR, LC_CTYPE=pt_BR (charmap=ISO-8859-1) (ignored: LC_ALL set to 
pt_BR)


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



litet tips

2005-04-09 Thread sandra karlsson
kolla in den bästa annonswebbplatsen (som är helt gratis): http://www.byten.se/


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



Bug#303971: ITP: ocaml-getopt -- command line parsing library for OCaml

2005-04-09 Thread Mike Furr
Package: wnpp
Severity: wishlist
Owner: Mike Furr <[EMAIL PROTECTED]>

  Package name: ocaml-getopt
  Version : 0.0.20040811
  Upstream Author : Alain Frisch <[EMAIL PROTECTED]>
  URL : http://www.http://www.eleves.ens.fr/home/frisch/soft.html
  License : MIT
  Description : command line parsing library for OCaml

This package provides the Getopt module that is an alternative to the
Arg module in the standard distribution.  Getopt supports the general
command line syntax of GNU getopt and getopt_long, but is close to the
spirit of the Arg module: the programmer gives to the general parsing
function a list of possible options, together with the behavior of
these options.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


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



[no subject]

2005-04-09 Thread yama

(B
(B
(B@;
(B 

Re: openswan 2.3.1 is now available - Call for Help

2005-04-09 Thread Paul TBBle Hampson
On Sat, Apr 09, 2005 at 10:32:06PM +0200, Rene Mayrhofer wrote:
> Am Samstag, 9. April 2005 17:31 schrieb Paul TBBle Hampson:
> > I'm interested in testing the new version, although the problem I was
> > suffering was a windows interoperability bug (Win2K Ipsec would crash
> > pluto) which I reported to the Openswan list and was told it would
> > probably be fixed in 2.3.1. I've built from the debian/ directory in CVS
> > at the moment, but haven't tried it in a few weeks to see if CVS fixed
> > my problem.

> > I also had two 2.3.0 openswans talking to each other for L2TP, but I
> > didn't see the crashing problem you've mentioned above (and which is to
> > do with NAT-T if the 2.3.1 changelog is anything to go by), both using
> > the 2.6 built-in IPSec stack for kernel support.
> If you can, then please test as much as you can. My current test packages are 
> at
> http://www.gibraltar.at/~rene/openswan/

> I have tried openswan-modules-source with both 2.4 and 2.6 kernel trees and 
> it 
> compiles fine now (many fixes during the last hours...), although I have not 
> yet tried the modules that have been built. I still need to try 
> kernel-patch-openswan and work further on that earlier crash problem.

I just tried openswan-modules-source under 2.6.10 with make-kpkg, and it
installed
/lib/modules/2.6.10/kernel/net/ipsec/ipsec.o
instead of
/lib/modules/2.6.10/kernel/net/ipsec/ipsec.ko

Also, 2.3.1 didn't fix my problem with Windows, so I'll build a local
unstripped version and see if I can get some useful answers from upstream.

-- 
---
Paul "TBBle" Hampson, MCSE
8th year CompSci/Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
[EMAIL PROTECTED]

"No survivors? Then where do the stories come from I wonder?"
-- Capt. Jack Sparrow, "Pirates of the Caribbean"

This email is licensed to the recipient for non-commercial
use, duplication and distribution.
---


pgp9h1mWsNq18.pgp
Description: PGP signature