in discover are:
/sbin/discover-modprobe
/bin/discover-static
/usr/bin/discover
/usr/bin/discover-config
In discover1 there is only:
/sbin/discover
Where does the faulty discover command occur?
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
idea when 2.0.7 will be out? Will it include the patch that
(reportedly) fixes #269372?
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: alsa-source
Version: 1.0.8-4
Severity: minor
An alsa-modules package has a Dependency on modutils | module-init-tools.
This is too weak; each such package really Depends on one or the other.
This is not a major problem because every alsa-modules package in the
archive Depends on an
without removing the information about
the VERBOSITY variable.
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: squid
Version: 2.5.7-5
Severity: minor
I run squid in its default configuration. Today for the first time I
got this message from logcheck:
System Events
=-=-=-=-=-=-=
Feb 1 12:24:29 thanatos squid[4226]: Request header is too large (20997 bytes)
Feb 1 12:24:29 thanatos squid[4226]:
because dpkg is the more senior program, or is there some
other hindrance to deleting the space before ... in dpkg's output?
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: doc-base
Version: 0.7.18
Severity: minor
command -v is not POSIX. The doc-base preinst and prerm both use
it and have #!/bin/sh at the top, so they violate policy 10.4.
Possible solutions:
* Using #!/bin/bash eliminates the 10.4 violation. However, there
remains the additional
Package: bzip2
Version: 1.0.2-1
Severity: minor
command -v is not POSIX. bzip2.postinst uses it and has #!/bin/sh
at the top, so it violates 10.4.
Possible solutions:
* Using #!/bin/bash eliminates the 10.4 violation. However, there
remains the additional problem that command -v doesn't
Package: fingerd
Version: 0.17-7
Severity: minor
command -v is not POSIX. However, the postrm uses it and has #!/bin/sh
at the top, so it violates policy 10.4.
Possible solutions:
* Using #!/bin/bash eliminates the 10.4 violation. However, there
remains the additional problem that command
Package: fcron
Version: 2.9.5.1-1
Severity: minor
command -v is not POSIX. The postrm uses it and has #!/bin/sh
at the top, so it violates policy 10.4.
Possible solutions:
* Using #!/bin/bash eliminates the 10.4 violation. However, there
remains the additional problem that command -v
Package: doc-debian
Version: 3.1
Severity: minor
command -v is not POSIX. However, the postinst and prerm scripts use
it and have #!/bin/sh at the top, so they violate policy 10.4.
Possible solutions:
* Using #!/bin/bash eliminates the 10.4 violation. However, there
remains the additional
Package: dpkg-doc
Version: 1.10.26
Severity: minor
command -v is not POSIX. However, the postinst and prerm scripts use
it and have #!/bin/sh at the top, so they violate policy 10.4.
Possible solutions:
* Using #!/bin/bash eliminates the 10.4 violation. However, there
remains the additional
Package: partimage-doc
Version: 20020126-8
Severity: minor
partimage-doc.postinst contains two stanzas that do the same thing,
one static and one inserted by dh_installdocs. Ditto for the prerm.
The code inserted by dh_installdocs has the advantage of being in
conformance with policy 10.4.
--
Package: latex2html
Version: 2002-2-1-8
Severity: minor
command -v is not POSIX. The postinst and prerm scripts use it and
have #!/bin/sh at the top, so they violate policy 10.4.
Possible solutions:
* Using #!/bin/bash eliminates the 10.4 violation. However, there
remains the additional
Package: lintian
Version: 1.23.7
Severity: minor
command -v is not POSIX. The postinst and prerm scripts use it and have
#!/bin/sh at the top, so they violate policy 10.4.
Possible solutions:
* Using #!/bin/bash eliminates the 10.4 violation. However, there
remains the additional problem
Package: linuxlogo
Version: 4.09-2
Severity: wishlist
/etc/init.d/linuxlogo writes the files issue.linuxlogo and
issue.linuxlogo.ascii to /etc/ at run time. This is one of very
few remaining obstacles to mounting the root filesystem read-only[0]
and is arguably a FHS violation. Fortunately
Package: linuxlogo
Version: 4.09-2
Severity: normal
The preinst assumes that the user has sysv-rc rather than file-rc:
# If the init script symlinks have the default priority (20) we will
# delete them so that they will be reinstalled with priority 99 in postinst.
if [ `find /etc/rc*.d
# dh_installpam
# dh_installmime
- dh_installinit -- start 99 2 3 4 5 .
+ dh_installinit --no-start -- start 99 2 3 4 5 .
# dh_installcron
# dh_installinfo
dh_installman
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
The one problems is that this prints an unwanted:
bash: foo: command not found
if foo is not executable. Do particular shells provide some means of
switching that message off?
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
kernel_is_2_6_or_above || return 1
return 0
}
udev_is_active exit 0
case $1 in
snd-emu8000-synth)
echo -n Loading SoundFonts...
/usr/bin/asfxload $ASFXLOAD_OPTS $SOUNDFONT_FILE echo done. ||
echo failed.
;;
esac
exit 0
--
Thomas Hood [EMAIL PROTECTED
-emu8000-synth)
/usr/bin/asfxload $ASFXLOAD_OPTS $SOUNDFONT_FILE || :
;;
esac
exit 0
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: scrollkeeper
Version: 0.3.14-9.1
Severity: normal
I don't know how it got there, but I have a directory named
'scrollkeeper' in /usr/var/. /usr/var/ is not a FHS directory.
The files seem to be comparable to those in /var/lib/scrollkeeper.
$ ls /tmp/1
am az be C ca cs da de el es fr hu
Hi. What is happening with this bug? It's still rated RC and there
hasn't been any visible (in the log) activity for a couple of months
now.
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi. I was looking at the bug logs and it isn't obvious to me why this
bug is rated RC. What's the status of this bug? Can it be downgraded?
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
If a package is upgraded and new-preinst upgrade old-version fails,
old-postinst abort-upgrade new-version is called.
Is the latter called instead of, or in addition to,
new-postrm abort-upgrade old-version, or is one called in case
the other fails?
--
Thomas Hood [EMAIL PROTECTED
Package: alsa-base
Version: 1.0.8-2~unreleased3
Severity: wishlist
As discussed in ubuntu bug report #5525 ...
https://bugzilla.ubuntu.com/show_bug.cgi?id=5525
if there is no asound.state file (as at the time of initial installation)
then mixer levels should be initialized to reasonable
Package: modutils
Version: 2.4.26-1.2
Severity: normal
[EMAIL PROTECTED]:~$ sudo update-modules
[EMAIL PROTECTED]:~$ sudo ln -sf posh /bin/sh
[EMAIL PROTECTED]:~$ sudo update-modules
/sbin/update-modules.modutils:148: local: not found
-- System Information:
Debian Release: 3.1
APT prefers
Please note that it would be good if this patch were applied to the 2.6
kernel that releases with sarge; otherwise users of sarge may encounter
bug #288423.
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
=== mail received after chkrootkit cron job ===
/etc/cron.daily/chkrootkit:
/usr/lib/kaffe/.system
wlanp_0: PACKET SNIFFER(/sbin/dhcpcd-bin[20318])
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
] ...
--install genname symlink altern priority [--slave sgen slink salt] ...
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: bash
Version: 3.0-5
Severity: normal
Please consider the following sequence of commands which illustrates
that command -v foo prints the name of the first executable file foo
it finds on the PATH, failing which it prints the first non-executable
file foo it finds on the PATH.
[EMAIL
fi
;;
esac
fi
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
found on the
patch can actually be executed. So I guess you need to do this:
#!/bin/bash
...
if CMD=$(command -v update-menus 2/dev/null) [ $CMD ] [ -x
$CMD ] ; then
update-menus
fi
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
So I guess you need to do this:
Actually, the snippet I gave can be simplified since test -x simply
returns false if it is given an empty string as argument.
#!/bin/bash
...
if CMD=$(command -v update-menus 2/dev/null) [ -x $CMD ] ; then
update-menus
fi
--
Thomas
Package: debian-policy
Version: 3.6.1.1
Severity: minor
Section 9.3.3.2 gives this as an example of how to check for the
availability of invoke-rc.d:
if command -v invoke-rc.d /dev/null 21; then
1. It would be helpful to mention that command -v is not POSIX and
that therefore, to be
Package: kernel-source-2.6.8
Version: 2.6.8-12
Severity: normal
Tags: patch
The attached patch modifies sound/core/init.c so that a negative index
value is interpreted as a bitmask indicating the allowed indices for the
driver. This extends the current semantics according to which:
value
, but it isn`t because - no sound
Is this a bug in the driver or in the Debian packaging?
--
Thomas Hood [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
601 - 637 of 637 matches
Mail list logo
