Bug#284855: billard-gl: starts in unusable resolution

2004-12-09 Thread Ronny Standtke
Package: billard-gl
Version: 1.75-6
Severity: important


When I start billard-gl it lowers the real screen resolution but uses a
higher virtual screen resolution. I have to scroll with the mouse at the
screen borders to see the whole program. In addition to that kicker
remains visible at the bottom of the screen.

In the current state the program is completely unusable.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-686
Locale: LANG=de_CH, LC_CTYPE=de_CH (charmap=ISO-8859-1)

Versions of packages billard-gl depends on:
ii  freeglut3 [libglut3]  2.2.0-8OpenGL Utility Toolkit
ii  libc6 2.3.2.ds1-18   GNU C Library: Shared libraries an
ii  libgcc1   1:3.4.2-2  GCC support library
ii  libglut3  3.7-25 the OpenGL Utility Toolkit
ii  libstdc++51:3.3.4-13 The GNU Standard C++ Library v3
ii  libx11-6  4.3.0.dfsg.1-8 X Window System protocol client li
ii  libxext6  4.3.0.dfsg.1-8 X Window System miscellaneous exte
ii  libxi64.3.0.dfsg.1-8 X Window System Input extension li
ii  libxmu6   4.3.0.dfsg.1-8 X Window System miscellaneous util
ii  xlibmesa-gl [libgl1]  4.3.0.dfsg.1-8 Mesa 3D graphics library [XFree86]
ii  xlibmesa-glu [libglu1]4.3.0.dfsg.1-8 Mesa OpenGL utility library [XFree
ii  xlibs 4.3.0.dfsg.1-8 X Window System client libraries m

-- no debconf information



Re: Bug#273053: marked as done (autofs: no kernel notifications for a "missing" or unmountable mount point (e.g. floppy))

2004-12-09 Thread Francesco P. Lovergine
reopen 27305 
reassing 27305 kernel
severity 27305 normal
thanks

Ehm, better reassigning to kernel.
He's referring to AUTOFS_NEGATIVE_TIMEOUT probably. It's not evident
to me if some sort of auto-adjustament is missing...

On Wed, Dec 08, 2004 at 02:18:31PM -0800, Debian Bug Tracking System wrote:
> Package: autofs
> Version: 3.9.99-4.0.0pre10-16
> Severity: normal
> 
> 
> okay.  when a floppy drive is accessed, and there happens not to be a
> floppy in the drive, you get an error "directory does not exist".
> 
> then you put a floppy _in_ the drive and access it  and it
> _still_ says "directory does not exist".
> 
> 30 seconds _later_ is a different story: access is granted.
> 
> >  i found out what the problem is: the auto-timeout field in the autofs.h
> >  linux kernel header file is set to a ridiculously long time period 
> >  of 60 (sixty) seconds.
> 
> OK, so no autofs bug (a kernel bug if any); closing. :-)
> 
> /* Steinar */

-- 
Francesco P. Lovergine



autofs

2004-12-09 Thread Steinar H. Gunderson
Hi,

I'm currently preparing to take over autofs (as should be evident from my
recent activity in the BTS :-) ), but I'm awaiting the response on
#278229 (to find out if the patch is worthwhile or not), and I'll have to
find out what went wrong in the previous parse_sun.c patch (it still isn't
right, and I'd rather fix that patch than add another one on top of it).
(Just making sure, as it seems you suddently uploaded a new version to
unstable :-) )

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



Re: autofs

2004-12-09 Thread Francesco P. Lovergine
On Thu, Dec 09, 2004 at 01:23:55PM +0100, Steinar H. Gunderson wrote:
> I'm currently preparing to take over autofs (as should be evident from my
> recent activity in the BTS :-) ), but I'm awaiting the response on
> #278229 (to find out if the patch is worthwhile or not), and I'll have to
> find out what went wrong in the previous parse_sun.c patch (it still isn't
> right, and I'd rather fix that patch than add another one on top of it).
> (Just making sure, as it seems you suddently uploaded a new version to
> unstable :-) )
> 

Yes, just a fix of my previous QA upload. I'm aware of your
current activities. Eventually, I'll post patches or comments on BTS. I have
a working NIS environment here, just if you need a testbed or something.

BTW, i did try to subscribe the autofs devel list, without results.
I think communicating a few patches and comments upstream is mandatory
for autofs...

Also, if i had time, I would start experiments with autofs-ng which 
is potentially a complete rewrote and improvement of current
kernel and user space tools.

-- 
Francesco P. Lovergine



Re: autofs

2004-12-09 Thread Steinar H. Gunderson
On Thu, Dec 09, 2004 at 01:58:17PM +0100, Francesco P. Lovergine wrote:
> Yes, just a fix of my previous QA upload. I'm aware of your
> current activities. Eventually, I'll post patches or comments on BTS. I have
> a working NIS environment here, just if you need a testbed or something.

If you could test and verify the patch for #278229, that would be very good.

> BTW, i did try to subscribe the autofs devel list, without results.
> I think communicating a few patches and comments upstream is mandatory
> for autofs...

Yes, indeed. I don't even know the upstream distribution site (nor how to
subscribe to the list); do you know where it is? :-)

> Also, if i had time, I would start experiments with autofs-ng which 
> is potentially a complete rewrote and improvement of current
> kernel and user space tools.

I think I'll leave that for somebody else; my primary intention now is to
clean up the bug list a bit and make sure autofs is in a releasable state for
sarge (which I guess it is, after you fixed all the RC bugs :-) ).

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



Re: autofs

2004-12-09 Thread Francesco P. Lovergine
On Thu, Dec 09, 2004 at 02:08:05PM +0100, Steinar H. Gunderson wrote:
> On Thu, Dec 09, 2004 at 01:58:17PM +0100, Francesco P. Lovergine wrote:
> > Yes, just a fix of my previous QA upload. I'm aware of your
> > current activities. Eventually, I'll post patches or comments on BTS. I have
> > a working NIS environment here, just if you need a testbed or something.
> 
> If you could test and verify the patch for #278229, that would be very good.
> 
> > BTW, i did try to subscribe the autofs devel list, without results.
> > I think communicating a few patches and comments upstream is mandatory
> > for autofs...
> 
> Yes, indeed. I don't even know the upstream distribution site (nor how to
> subscribe to the list); do you know where it is? :-)
> 

http://linux.kernel.org/mailman/listinfo/autofs

distribution is done on the kernel.org ftp site, AFAIK. Collecting
patches from the devel list and possibly other distros like Fedora or
Suse is also a good thing.

There is an interesting non-deamon mode patch, which could be useful
for debugging purpose, but it seems creating problems with current
debian package.

> > Also, if i had time, I would start experiments with autofs-ng which 
> > is potentially a complete rewrote and improvement of current
> > kernel and user space tools.
> 
> I think I'll leave that for somebody else; my primary intention now is to
> clean up the bug list a bit and make sure autofs is in a releasable state for
> sarge (which I guess it is, after you fixed all the RC bugs :-) ).
> 

that's good, my todos list is damn lng...

-- 
Francesco P. Lovergine



Bug#285003: python-simpy new release

2004-12-09 Thread Tony Vignaux

Package: python-simpy
Version: 1.5
Severity: wishlist

A new release of SimPy, the Python simulation package, is now
available at http://sourceforge.net/projects/simpy/. 
The unix version is in SimPy-1.5.tar.gz. It can be installed using setup.py


This release adds two new process interaction capabilities as described 
in the

release notes.

Tony Vignaux