Package: btrfs-tools
Version: 3.16-1
Severity: normal
Dear Maintainer,
btrfs send fails if the filesystem is mounted on / with the error:
ERROR: doesn't belong to btrfs mount point
There appears to be a patch available at
https://patchwork.kernel.org/patch/4842201/
James
-- System Informati
The header of the init script /etc/init.d/clvm requires that cman be
running, giving these errors on install:
insserv: Service cman has to be enabled to start service clvm
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing clvm (--install):
subproc
> Hi,
>
> I haven't been using the modass based package for some time. The newer
> dkms package is more convenient. It takes care of auto-rebuilding the
> modules on new kernel image installs and upgrades.
>
>
> Are you guys still using the old package for a reason?
> I was thinking of getting r
The following patch gets the build going for me. I'm sure there is a
better way than calling out to printf though. It accomplishes two things
- expand kernel version to a canonical string instead of making the
assumption that the revision is 2 digits, and uses .ko for anything
greater or equal than
I have been seeing this problem also. It is still present in 0.11.3-4,
and the patch at https://sharesource.org/hg/pymsnt/rev/b704db19896a as
detailed by the OP fixes the problem.
IMHO, the severity of 'normal' is not doing this bug justice. It causes
copious amounts of traffic to be generated by
Just in case anyone else goes looking for a resolution that doesn't
involve using a package from unstable, there is a workaround documented
on this link
(http://issues.apache.org/bugzilla/show_bug.cgi?id=37770#c34) that
worked for me.
Add the following two lines to file httpd.conf:
SetEnv force-p
Xenman appears to look for itself in /usr/sbin, and it isn't there
anymore!
When I open a vnc console I get:
"
sh: /usr/sbin/xenman: No such file or directory
"
The VNC console still opens up though so I'm not sure if the regression
is anything other than a benign error message... It will be eas
Package: greylistd
Version: 0.8.3.2
Severity: normal
Tags: patch
I'm using greylisting very successfully, and have included a quick enhancement.
My original setup under exim4 was:
1. accept MAIL FROM and RCPT TO
2. perform greylist check and store result
3. accept DATA
4. perform spam check to ge
> On Fri, Feb 09, 2007 at 03:03:33PM +1100, James Harper wrote:
> > Would it be possible for watchdog to detect a change to runlevel 0
or
> > 6, and simply stop doing the checks which become unreliable once a
> > shutdown has started? This behaviour could be controlled by a
Package: watchdog
Version: 5.2.6-6
Followup-For: Bug #353053
I'm having a problem where xen needs an unknown amount of time to shut down the
virtual machines before it can shut down itself, which means shutting down
watchdog when nowayout has been set causes a premature reboot.
Would it be poss
Package: dfsbuild
Version: 0.99.2
Severity: grave
Justification: renders package unusable
the version of grub that ships with etch puts its files in /usr/lib/grub
instead of /lib/grub, which breaks dfsbuild.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'tes
Package: dfsbuild
Version: 0.99.2
Severity: grave
Justification: renders package unusable
cdebootstrap saves the Release file as _dists_.Release, which causes
dfsbuild to break. Changing Release to _dists_.Release in
Actions/Mirror.hs appears to resolve the problem.
Would it make sense to use ano
Package: ppp
Version: 2.4.4rel-2
Severity: normal
When using the rp-pppoe plugin and pppoe, the fragments used are tiny (8 bytes
of ppp data), and consequently the link behaves really really poorly. The
correct behaviour is that MLPPP fragments should be (packet size) / (number of
links), but
> Hi,
>
> James Harper, le Sat 08 Jul 2006 23:02:57 +1000, a écrit :
> > linux-modules-2.6.16-2-xen-686 only contains modules for xen domains,
> > and should not require any initrd or initramfs tools.
>
> Mmm, but for dom0 you need to build an initrd.
Yes, but
I'm using cyrus21-imapd, but the problem I saw was so similar to the
problem you describe that I suspect they are related.
An strace shows the following:
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8)
Package: linux-modules-2.6.16-2-xen-686
Version: 2.6.16-15
Severity: important
linux-modules-2.6.16-2-xen-686 only contains modules for xen domains,
and should not require any initrd or initramfs tools.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (
Package: grub
Version: 0.97-12
Severity: normal
Tags: patch
grub-install fails to install on AoE devices (eg /dev/etherd/e0.0). This
patch allows grub-install to correctly detect the drive and partitions.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy:
If anyone is interested, I have a patch that fixes this.
James
I'm just testing OCFS2 as a root filesystem, and apt breaks because
OCFS2 (and probably GFS) don't support shared writable mmap's. For OCFS2
at least, this support is on the todo list but not really near the top.
Any chance of an updated patch or, even better, something that detects
at runtime wha
FWIW, the posted modification works for me, and without it the entire
package is unusable.
James
Package: gdm
Version: 2.13.0.10-2
Severity: normal
I don't run a gdm session on the console, only xdmcp, which I did previously by
commenting out the '0=standard' line in gdm.conf. Now this is set in
/usr/share/gdm/default.conf and either can't be disabled locally or is lacking
documentation to
Package: gdm
Version: 2.8.0.6-2
Severity: normal
Not sure that this is actually a gdm bug. I did a dist-upgrade on my Etch
system to pick up the latest patches, and now I can't log in using xdmcp
(probably not at the console either but the server is headless so I can't test
it). Everything just
Package: ifupdown
Version: 0.6.7
Severity: wishlist
See bug 354933 for more information, but the way the interfaces file allows
multiple interface stanzas (inet, inet6, ipx) with different protocols breaks
vlan and possibly bridge interfaces scripts if you try and configure the same
interface t
> Personally I always added the static addresses in the up after
> the ipv4 stuff. Yours seems like the correct way. Hmmm. I have to
> look into it. For me it is new behaviour that ifup will handle
> multiple iface eth0 entries. (I probably didn't read the manpages
> right).
It seems that it is al
> Sent: Thursday, 2 March 2006 19:24
> To: James Harper; [EMAIL PROTECTED]
> Cc: Debian Bug Tracking System
> Subject: Re: Bug#354933: vlan: vconfig is called again for inet6
stanzas
>
> Hello,
> On Thu, Mar 02, 2006 at 05:23:30PM +1100, James Harper wrote:
> > with a sta
>
> I can submit a patch to do this if it is considered a good idea.
>
Unfortunately, my patch works on ifup because the vlan-ignore option is
set in the inet6 stanza, but because ifdown hits the inet entry first,
by the time the inet6 stanza is processed the interface is gone :(
Package: vlan
Version: 1.9-1
Severity: normal
with a static inet6 entry in /etc/interfaces, the vlan ifupdown script try
and do a second vconfig because they think it is a second interface. I'm not
sure of the best way to work around this, but i'd be happy just to be able
to add a 'vlan-ignore' en
Package: nagat
Version: 1.0a2-6
Severity: important
Tags: patch
serviceedit.php does not write out the contact groups. need to add:
$saveobject['contact_groups'] =
@implode(",",$saveobject['contact_groups']);
to serviceedit.php
-- System Information:
Debian Release: 3.1
APT prefers testing
28 matches
Mail list logo
