reopen 493745
found 493745 1.0.19-17
thanks
On Fri, Aug 08, 2008 at 07:46:29PM +0200, Julien BLACHE wrote:
Wolfgang [EMAIL PROTECTED] wrote:
Hi,
just disabled standalone daemon. Only running from inetd.
Good :)
Can you quickly check, whether you get this error too when standalone
Olivier Berger [EMAIL PROTECTED] wrote:
Hi,
Well... but that currently prevents completing sane-utils upgrade on my
host.
Did you enable saned in standalone mode when prompted?
If yes, you're banging your head against the wall and then complaining
that it hurts. Learn not to do that.
JB.
Julien BLACHE [EMAIL PROTECTED] writes:
Olivier Berger [EMAIL PROTECTED] wrote:
Hi,
Well... but that currently prevents completing sane-utils upgrade on my
host.
Did you enable saned in standalone mode when prompted?
It previously worked, I upgraded and wasn't prompted, and it won't end
Olivier Berger [EMAIL PROTECTED] wrote:
Hi,
Did you enable saned in standalone mode when prompted?
It previously worked, I upgraded and wasn't prompted, and it won't end
the upgrade process.
Either you were prompted with the question, in which case you answered
it at some point in time, or
Hi Julien,
version -12 no more available. Neither locally nor on a server.
So I did a purge on it and a new installation.
saned would not start, /etc/default/saned was disabled.
As I could remember I setup the network option in etch long time ago by hand
and never edited /etc/defaults/saned
Wolfgang [EMAIL PROTECTED] wrote:
Hi,
saned would not start, /etc/default/saned was disabled.
As I could remember I setup the network option in etch long time ago by hand
and never edited /etc/defaults/saned (was this necessary in etch, too?) but
setup net.conf and inetd.conf.
There
Julien,
just disabled standalone daemon. Only running from inetd.
Voila!
and upgrade to -17 works too.
Can you quickly check, whether you get this error too when standalone and
inetd are configured by hand?
If so, close the bug.
Am Freitag, 8. August 2008 18:47:45 schrieb Julien BLACHE:
Wolfgang [EMAIL PROTECTED] wrote:
Hi,
just disabled standalone daemon. Only running from inetd.
Good :)
Can you quickly check, whether you get this error too when standalone and
inetd are configured by hand?
If so, close the bug.
When saned is enabled in inetd, the port is bound by
notfound 493745 1.0.19-15
close 493745
thanks
just disabled standalone daemon. Only running from inetd.
Voila!
and upgrade to -17 works too.
JB.
--
Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED]
Public key available on http://www.jblache.org - KeyID: F5D6 5169
GPG
Hi Julien,
my apt-update told me two things for 4th aug 2008:
sane-utils/lenny upgradeable from 1.0.19-12 to 1.0.19-15
initscripts/lenny upgradeable from 2.86.ds1-59 to 2.86.ds1-60
Wolfgang
Am Montag, 4. August 2008 18:49:09 schrieb Julien BLACHE:
Wolfgang Schnitker [EMAIL PROTECTED]
Wolfgang [EMAIL PROTECTED] wrote:
Hi,
i did an update from
sane-utils/lenny upgradeable from 1.0.19-12 to 1.0.19-15
on amd64.
1.0.19-17 will be available in unstable tomorrow. Can you please try
the following:
- downgrade to 1.0.19-12
- upgrade to 1.0.19-15 again
To see if the problem
Package: sane-utils
Version: 1.0.19-15
Severity: normal
after update the package stops to install with this error:
Starting SANE network scanner server: invoke-rc.d: initscript saned, action
start failed.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (300,
Wolfgang Schnitker [EMAIL PROTECTED] wrote:
Hi,
after update the package stops to install with this error:
Starting SANE network scanner server: invoke-rc.d: initscript saned, action
start failed.
What version were you upgrading from?
JB.
--
Julien BLACHE - Debian GNU/Linux Developer -
13 matches
Mail list logo
