Bug#461068: release on close

2008-01-18 Thread Julien BLACHE
Uwe Kleine-König <[EMAIL PROTECTED]> wrote: Hi, >> Looks like a good idea. Is it safe if the port has already been >> released ? > Yes, it's save. ieee1284_release looks as follows: > > if (priv->claimed && priv->fn->release) > priv->fn->release (priv); > priv->claimed = 0; >

Bug#461068: release on close

2008-01-17 Thread Uwe Kleine-König
Hi Julien, Julien BLACHE wrote: > Uwe Kleine-König <[EMAIL PROTECTED]> wrote: > > what do you think about that patch? > > > > This is the first step to achive that a port is closed when a Python > > ParportObject is deleted. > > Looks like a good idea. Is it safe if the port has already been > re

Bug#461068: release on close

2008-01-17 Thread Julien BLACHE
Uwe Kleine-König <[EMAIL PROTECTED]> wrote: Hi, > what do you think about that patch? > > This is the first step to achive that a port is closed when a Python > ParportObject is deleted. Looks like a good idea. Is it safe if the port has already been released ? JB. -- Julien BLACHE - Debian

Bug#461068: release on close

2008-01-16 Thread Uwe Kleine-König
Package: libieee1284-3 Version: 0.2.11-3 Severity: minor Tags: patch Hello, what do you think about that patch? This is the first step to achive that a port is closed when a Python ParportObject is deleted. Best regards Uwe #! /bin/sh /usr/share/dpatch/dpatch-run ## 02_release_on_close.dpatch