Re: Request for substitute sponsor (vim-vimoutliner) and some questions

2005-10-10 Thread Justin Pryzby 
On Mon, Oct 10, 2005 at 11:26:55PM -0400, Matej Cepl wrote:
> 2) Bug# 216626  -- I have tried to close
> (because it was already fixed in 0.3.4-1), but then the reporter reopened
> it claiming that it was not fixed in sarge, so it should stay opened. That
> IMHO isn't correct -- bug is closed when it is fixed in unstable, isn't it?
Read about bts version tracking.

> Moreover, when I was going through debian/changelog I found that I have
> really forgot to close it there, so I have created new version 0.3.4-2
Don't say that its closed in this version, if this version doesn't
actually change something which closes it.  Just send an email to the
BTS to set the bug to the correct state (close 216626 0.3.4-1 if I
understand correctly).

> Will it get rid of that bug at all?
With version tracking, the found, clouse, and notfound commands will
put the bug in the correctly versioned state.

> Or what should I do with persistent user claiming that he wants to
> have it fixed in stable? On the other hand, 0.3.3-6 (which is what
> is in sarge) really IS broken -- how do I get package to
> stable/proposed-updates?
Contact the stable release manager, as the bug reported said.  Its
possible that this update will be approved:
 
  http://people.debian.org/~joey/3.0r6/

-- 
Clear skies,
Justin


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

Request for substitute sponsor (vim-vimoutliner) and some questions

2005-10-10 Thread Matej Cepl 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

my sponsor (Martin F. Krafft) got tendonitis, so I need somebody to help me
with vim-vimoutliner. Is there any nice DD willing to sponsor next upload
of vim-vimoutliner package? Version 0.3.4-2 is available at
. However, before uploading,
please consider these questions:

1) I've got message on 2005-07-07 that VO 0.3.4-1 was uploaded, but when I
checked today , it shows
0.3.3-6 even in unstable (I have testing here, so I am not sure what is
really in unstable). What's going on? How can I find out where my package
got lost?
2) Bug# 216626  -- I have tried to close
(because it was already fixed in 0.3.4-1), but then the reporter reopened
it claiming that it was not fixed in sarge, so it should stay opened. That
IMHO isn't correct -- bug is closed when it is fixed in unstable, isn't it?
Moreover, when I was going through debian/changelog I found that I have
really forgot to close it there, so I have created new version 0.3.4-2
which is again available at  
which I would like to ask you to upload on my behalf. Will it get rid of
that bug at all? Or what should I do with persistent user claiming that he
wants to have it fixed in stable? On the other hand, 0.3.3-6 (which is what
is in sarge) really IS broken -- how do I get package to
stable/proposed-updates?

Thanks a lot,

Matej

- -- 
Matej Cepl, http://www.ceplovi.cz/matej/blog/
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
 
They never open their mouths without subtracting from the sum of
human knowledge.
  -- Thomas Brackett Reed
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDSzEF4J/vJdlkhKwRAv0+AJ40Jn8cgg1Jv97L8Yrr4knsikD2SwCfXavB
/DJ4LAIfrz7H7Y16rihCOdo=
=u6mm
-END PGP SIGNATURE-


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

Re: [RFC/RFS] adm8211-source - driver for ADMtek wifi card

2005-10-10 Thread Jean-Marc Ranger 

Hi Geert,

Thanks for your feedback.


There are no signs of an ITP   ( Intented To Package )
Please file an "ITP bugreport"


I thought it was optional.  Fixed anyway, see http://bugs.debian.org/333237

A newer version is available at http://web.ncf.ca/jmranger/adm8211/ with 
the following changes:


- improved README.Debian (typo fix + additional info)
- changelog now reports closing 333237 (the ITP bug report)

In addition, package was finally tested on Sid.  No changes required, 
tesst passed as-is.  The only thing is that adm8211-source must be added 
in /usr/share/modass/compliant.list - that wasn't required for my 
initial Sarge test setup.  But since ipw2100-source (which I took my 
inspiration from) is listed there too, I consider it's OK.


Jean-Marc


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

RFS: fbgetty

2005-10-10 Thread Sylvain LE GALL 
Hello,

I am looking for a sponsor to fbgetty. This package has been orphaned
and i want to take his maintainance.

I have prepared a package, that can be found here:
http://le-gall.net/sylvain/debian-public/

The package seems almost lintian clean (2 warnings about outdated
config.sub/config.guess which are patched during the build, so it should
not generate any real errors).

I have rebuild it in a pbuilder also, without problem.

Thanks in advance,
Sylvain Le Gall

ps:
http://packages.debian.org/unstable/admin/fbgetty


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

Re: [RFC/RFS] adm8211-source - driver for ADMtek wifi card

2005-10-10 Thread Geert Stappers 
On Sat, Oct 08, 2005 at 09:03:40PM -0400, Jean-Marc Ranger wrote:
> Hi,
> 
> Here's a new candidate for inclusion in Sid:  Jouni Malinen and Michael
> Wu 's GPL driver for ADMtek's adm8211-based 802.11b wireless cards,

Hardware with GPL drivers is COOL!


> Candidate package is available at http://web.ncf.ca/jmranger/adm8211/

> So please have a look, and let me know how what you think.



There are no signs of an ITP   ( Intented To Package )

Doing the packaging is good,
Telling that you are packaging is better.

Please file an "ITP bugreport"


> Jean-Marc


HTH
Geert Stappers



signature.asc
Description: Digital signature

RFS: synopsis -- Source code documentation tool

2005-10-10 Thread Andreas Fester 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I adopted synopsis (http://synopsis.fresco.org), a source code
documentation tool, especially suited for (but not limited to)
creating documentation from python code.
The package I created from the latest upstream version is
available on mentors.debian.net
(http://mentors.debian.net/debian/pool/main/s/synopsis).
The package is linda and lintian clean, with an override
though; hope that someone nevertheless is willing to sponsor me ;-)

Thanks and best Regards,

Andreas

- --
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://www.littletux.net
ICQ: 326674288
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDSrxUZ3bQVzeW+rsRAs7zAKCTxTTP6PI897N5hwrw/ebm5u9WtwCeOA9H
EX+7cLQnAjLXLZAtGD7lC6M=
=2D2L
-END PGP SIGNATURE-


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

Re: first steps (pcfitsio, pyraf and iraf)

2005-10-10 Thread Justin Pryzby 
On Mon, Oct 10, 2005 at 09:48:31AM +0200, Cedric BRINER wrote:
> Hi,
> 
> I'm working as a sysadmin at the Geneva Observatory and we do need
> some softwares which are not provided by the debian distribution. So
> I thought that it will be a good idea to do this job well once and
> to give this back to the debian community.

> pcfitsio : http://panoramix.stsci.edu/~npirzkal/python/pcfitsio/index.html
> 
This seems like a good package, if its useful to you and others.

> pyraf : http://www.stsci.edu/resources/software_hardware/pyraf
I have a quick pyraf 1.1.1 .deb on my site, which I don't use.  Others
have reported using it successfully; I suspect that its not the most
recent version.  Since pyraf is just an iraf add-on, best you can do
in debian is an upload to contrib (right?).  And I think that is
pushing it, even, since iraf probably won't be in non-free..

-- 
Clear skies,
Justin

debian and astronomy (was: Re: first steps (pcfitsio, pyraf and iraf))

2005-10-10 Thread Justin Pryzby 
On Mon, Oct 10, 2005 at 09:04:57AM -0400, Kevin B. McCarty wrote:
> Cedric BRINER wrote:
> 
> > Hi,
> > 
> > I'm working as a sysadmin at the Geneva Observatory and we do need
> > some softwares which are not provided by the debian distribution. So
> > I thought that it will be a good idea to do this job well once and to
> > give this back to the debian community.
> > 
> > the software that I'm willing to package are: pcfitsio, pyraf, iraf
> 
> IIRC, Justin Pryzby (justinpryzby at users.sourceforge.net) has made
> unofficial packages of at least IRAF.  There have been some possible
> copyright issues with the package.  You should probably coordinate work
> on packaging IRAF with him, especially since he owns the open ITP:
Morning,

Yes, IRAF has issues; the main CL parser is copyright Stephen C.
Johnson; I believe its ripped from 1970s unix YACC.
(./iraf-2.12.2a/unix/boot/xyacc/README; the copyright listed in the
*.c files here were apparently mass-added by NOAO, inaccurately).

I don't anticipate seeing IRAF included by Debian anytime soon.
Creating packages isn't that bad, the worst part is doing some strange
things to get it to compile (and, were I to spend more time on the
iraf packages, I would probably NOT compile from source, but write a
wget wrapper for the binaries provided by upstream, since I'm not able
to get shared libraries working with iraf's present "memory
management" scheme in conflict with my kernel's MM scheme).  There is
involving relocation of ~5 conffiles to /etc/, splitting between
/usr/lib/iraf/ and /usr/share/iraf/ ... nothing terrible here.

But IMHO the iraf system is ill-designed by today's standards.  I have
just uploaded a page about this:

  http://justinpryzby.com/astro/code/iraf.html

Then there is the rumor that NOAO is/has discontinued (financial)
support of iraf.  The references I've seen are linked to from:

  http://www.owlnet.rice.edu/~marcosh/iraf/

I don't feel that this is a bad thing .. iraf is an old system, and
probably should have been heavily rewritten several times in the last
20 years.  Now, it looks like that is actually happening.

As an aside, you might (or well might not) be interested in

  http://justinpryzby.com/astro/code/libastro.html

which is a from-scratch implementation of algorithms for astronomy
which I personally have used.  It is presently capable of image
calibration, photometry, star extraction, centroiding, moving object
detection, and includes a simiilar-triangle pattern matching routine.
(Might I add that this is 100x faster than the iraf implementation,
ccxymatch?  I can't fathom why).  I'm also working on an imtool, but
this is in very early stages of development.  Anyway, source is
X11/MIT licensed, and available as tarballs in the ./code/ directory.

I don't intend to make any use of iraf ever again, not until somebody
pays me good money to do so.

I don't expect that you're going to be able to convince your
observers/data analysts to use anything but iraf.  So I suggest my
3-step Hacker's Installation Procedure for Iraf:

Download as.pcix.gen.gz, ib.lnux.x86.gz, nb.lnux.x86.gz, and
extract them as follows:

Extract thisTo here
---
as.pcix.gen.gz  ./iraf/
ib.lnux.x86.gz  ./irafbin/bin.linux/
nb.lnux.x86.gz  ./irafbin/noao.bin.linux/

The root directory ("./") is arbitrary; for this type of installation,
I suggest /opt/iraf/ or /usr/local/iraf/; /usr/iraf/ and /iraf/ are
other possibilities (but don't fit into the standard hierarchy as
nicely).

You must edit ./iraf/unix/hlib/libc/iraf.h with the chosen
installation path and create a symlink:

/usr/include/iraf.h => ./iraf/unix/hlib/libc/iraf.h

That's enough to run ./irafbin/bin.linux/cl.e, and probably do most
analysis but you should run the full install script to do other stuff
too (edit other files, set up networking, make symlinks in /usr/bin/,
etc.):

./iraf/unix/hlib/install

(This is the part that scares most people, but I save it for last, since it
doesn't seem to be necessary for most things).

Lastly, Florian Ernst kindly sponsored my sextractor package last
week; it is now waiting in the new queue.  ds9 is already available in
Debian (though it won't be for much longer if upstream doesn't provide
unobfuscated source in their v4 release).

Iraf aside, what software do your astronomers need?  And, what iraf
tasks do they use?

-- 
Clear skies,
Justin


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

RFS: libpam-abl - PAM module to blacklist hosts/users with many login failures

2005-10-10 Thread Nicolai Ehemann 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello!

I just (err, over the last 4 or 5 days) created a (hopefully
standards-compliant) package for the pam_abl PAM module.

The pam_abl module provides a fully configurable way to automatically
blacklist users and/or hosts with many login failures within specified
intervals of time to be temporarily blacklisted, so that any subsequent
authentication attempt fails (without disclosing the attacker beeing
blacklisted). As the number of password guessing attacks on ssh servers
on the net has strongly grown in the past time, i think this is a useful
addition to security on hosts exposed to the net.

The package I built is lintian and linda clean, closes the ITP bug
#333081 filed by me and is available via
deb-src http://mentors.debian.net/debian unstable main
or
http://mentors.debian.net/debian/pool/main/l/libpam-abl/
It is also listed at http://sponsors.debian.net/viewpkg.php?id=95

The original package is available from http://www.hexten.net/pam_abl/.
It is licensed with either a BSD-style license or GPL, at users option.
I already contacted the upstream author and got his approval to package
the pam_abl module for debian.

In an effort to make sure the package does what is intended and only
what is intended, I already inspected the source code and found it to be
clean, readable and unsuspicious. Of course, I also use the module on
different machines, and have encountered no problems so far.

I know the package is very security relevant, and as such, imposes some
more work from a potential sponsor, but I hope that someone is willing
to pick it up, as it might really be interesting for a relatively
wide-spread audience.

Thank you in advance

Nico
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFDSn49Ym+MkvsfJ58RAq0fAJ9LCI0Z9biVk6w1/3VVzh9dGyKGzgCcCYp/
oDi8E582M+5OpZmVXMlJcXE=
=2l2g
-END PGP SIGNATURE-


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

Re: first steps (pcfitsio, pyraf and iraf)

2005-10-10 Thread Kevin B. McCarty 
Cedric BRINER wrote:

> Hi,
> 
> I'm working as a sysadmin at the Geneva Observatory and we do need
> some softwares which are not provided by the debian distribution. So
> I thought that it will be a good idea to do this job well once and to
> give this back to the debian community.
> 
> the software that I'm willing to package are: pcfitsio, pyraf, iraf

IIRC, Justin Pryzby (justinpryzby at users.sourceforge.net) has made
unofficial packages of at least IRAF.  There have been some possible
copyright issues with the package.  You should probably coordinate work
on packaging IRAF with him, especially since he owns the open ITP:

http://bugs.debian.org/244711

-- 
Kevin B. McCarty <[EMAIL PROTECTED]>   Physics Department
WWW: http://www.princeton.edu/~kmccarty/Princeton University
GPG: public key ID 4F83C751 Princeton, NJ 08544


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

[RFS] qterm(0.4.0pre3-2): BBS client for X Window System written in Qt

2005-10-10 Thread LI Daobing 
lintian and linda clean, uploaded to mentors

http://mentors.debian.net/debian/pool/main/q/qterm/

changelog:

qterm (0.4.0pre3-2) unstable; urgency=low

  * rebuild depends on libssl-dev (>= 0.9.8-1)
  * configure with '--enable-arts --enable-esd'
  * patches/02-openssl.dpatch:
work with one libssl-dev's bug(#333101)

 -- LI Daobing <[EMAIL PROTECTED]>  Mon, 10 Oct 2005 19:11:05 +0800

qterm (0.4.0pre3-1) unstable; urgency=low

  * New upstream release
  * debian/copyright:
- new fsf address
- update copyright information
  * debian/menu: fix format
  * debian/control: update package description
  * debian/README.Debian: how to setup detecting location from ip environment
  * debian/qterm.dbk: new manpage in docbook format
  * use dpatch to manage patches
- 01-amd64.dpatch: make qterm buildable under amd64.

 -- LI Daobing <[EMAIL PROTECTED]>  Sat, 10 Sep 2005 06:18:43 +0800

Thanks.

--
LI Daobing

Re: first steps (pcfitsio, pyraf and iraf)

2005-10-10 Thread Paul Wise 
Cedric BRINER wrote:

> I'm working as a sysadmin at the Geneva Observatory and we do need
> some softwares which are not provided by the debian distribution. So I
> thought that it will be a good idea to do this job well once and to
> give this back to the debian community.

Really, you will need to do it more than once - each new upstream
version of each package will need adapting for and uploading to debian.
If you don't want to be the maintainer, but you want to package these
packages, you will need to find someone else to be the maintainer for
them once they are packaged. I'd suggest asking on the debian-science
list if you need someone for this.

> pcfitsio :
> I've send last firday an email to the author of pcfitsio to ask him
> the kind of copyright which is not given on his software

Excellent. It is a pity so much free software needs this kind of
copyright clarification and auditing.

> iraf : http://iraf.noao.edu/

This used to be in debian, but it was removed:

http://packages.debian.org/oldstable/science/iraf
http://ftp-master.debian.org/removals.txt
http://bugs.debian.org/232472
=
[Date: Wed, 25 Feb 2004 13:50:58 -0500] [ftpmaster: James Troup]
Removed the following packages from unstable:

  iraf |   2.11.3-2 | source, i386
  iraf-dev |   2.11.3-2 | all
 iraf-ibin |   2.11.3-3 | source, i386
iraf-noaobin |   2.11.3-2 | source, i386
   x11iraf |  1.2-4 | source, alpha, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, s390, sparc
Closed bugs: 232472
--- Reason ---
RoQA; FTBFS, FHS violations, needs to be repackaged.
Explanation:
Request of debian Quality Assurance
Fails to build from source
File hierarchy standard violations
--

> So please tell me where shall I start ?

Read the new maintainers guide, the debian mentors FAQ, then file some
ITP bugs. Since the software you want to package are mainly python bits,
you should read the python policy, and look at using cdbs (it simplifies
making debian packages for python and other packages). An example cdbs
debian/rules file for a python package is listed below.

http://www.debian.org/doc/maint-guide/
http://people.debian.org/~mpalmer/debian-mentors_FAQ.html
http://svn.debian.org/wsvn/python-modules/pygoogle/debian/rules?op=file&rev=0&sc=0

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

unsubscribe

2005-10-10 Thread HStoiser 



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

first steps (pcfitsio, pyraf and iraf)

2005-10-10 Thread Cedric BRINER 
Hi,

I'm working as a sysadmin at the Geneva Observatory and we do need some 
softwares which are not provided by the debian distribution. So I thought that 
it will be a good idea to do this job well once and to give this back to the 
debian community.

the software that I'm willing to package are: pcfitsio, pyraf, iraf

pcfitsio : http://panoramix.stsci.edu/~npirzkal/python/pcfitsio/index.html

   I've send last firday an email to the author of pcfitsio to ask him the kind 
of copyright which is not given on his software:
   
http://panoramix.stsci.edu/~npirzkal/python/pcfitsio/downloads/pCFITSIO-0.99.2.tar.gz
   this software is a python module which is a wrapper to cfitsio (cfitsio is 
the c implementation of fitsion which was written in fortran), and provide the 
ability to r/w fits file which are commonly used on astronomy

   I've already compile this on my machine and install it. So it seems that it 
won't be that difficult


iraf : http://iraf.noao.edu/

Image Reduction and Analysis Facility
I've not already send them an email.
I've thought to package it when the pcfitsio and pyraf will be done.


pyraf : http://www.stsci.edu/resources/software_hardware/pyraf
-
   I've send an email to them, and they told me that they will kindly help me 
in this work. And that the only reason that they are not packaging their work 
for different distribution was due to a lake of ressources : )
   this soft is a command language based on python to enpower the iraf with 
python.
   the installation steps are provided at : 
http://www.stsci.edu/resources/software_hardware/pyraf/stsci_python/Installation
   Not yet tried to install this on my machine


So please tell me where shall I start ?

Regards

Ced.

-- 

Cedric BRINER
Geneva - Switzerland


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