Bug#437525: The bug is about the kernel warning

reassign 437525 linux-image-2.6.21-2-686 thanks On Mon, Aug 27, 2007 at 04:32:42PM -0500, Nelson Castillo wrote: > As I told you before, I reported the bug (the message printed by > the kernel) because I found the message to be misleading and I > wasted some time with it. OK, that wasn't really c

Bug#418596: nfs-common: Can not nfs-mount using second interface during boot

On Fri, Aug 17, 2007 at 01:08:01AM +0200, Steinar H. Gunderson wrote: >> I'll test with etch,lenny and sid and provide more information > Great, thanks. Any progress on this? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] wit

Bug#418596: nfs-common: Can not nfs-mount using second interface during boot

On Mon, Sep 03, 2007 at 05:25:32PM +0200, Gebhardt Thomas wrote: > I consider this bug important enough to be fixed in stable etch. Are you serious? It's an edge case that affects a tiny fraction of all users, can by worked around in the majority of cases (simply mount NFS later in the boot proces

Bug#440676: nfs-kernel-server: Simultaneous transfer on mirrored nfs mounts causes service freezes

reassign 440676 linux-image-2.6.18-5-powerpc thanks On Mon, Sep 03, 2007 at 11:38:31AM -0400, Jeffrey B. Green wrote: > The setup is having nfs mounts on various machines and backups to > "non-local" mounts. Having cron jobs starting on more than one machine and > backing up to the other while the

Bug#418596: nfs-common: Can not nfs-mount using second interface during boot

On Tue, Sep 04, 2007 at 09:25:19AM +1200, Phil Snowdon wrote: > However the issues still need to be addressed in Lenny/Sid. The last thing I heard was that it was OK in sid... Did I misunderstand, or are we talking about two different problems now? /* Steinar */ -- Homepage: http://www.sesse.net

Bug#433133: still not fixed... downgraded to 1.1.0-4

On Tue, Jul 17, 2007 at 04:22:24PM +0200, Ivan Sergio Borgonovo wrote: > I had to downgrade nfs-common to make it work. > > nfs-common_1%3a1.1.0-10_amd64.deb > still doesn't work. Try setting ASYNCMOUNTNFS=no in /etc/default/rcS. I'm currently talking to the initscripts maintainers to try to find

Bug#433386: Patch for fixing boot-time NFS

reassign 433386 initscripts tags 433386 + patch thanks Hi, As discussed with Petter on IRC, initscripts is going to need fixing in addition to the latest nfs-common changes. The following patch is a fixed version of a previous patch I proposed; I've been asked to wait for feedback for a few days

Bug#389557: remove rpc.idmapd and rpc.gssd pid file checks from nfs4mount.c

Version: 1:1.1.0-10 On Tue, Jan 30, 2007 at 10:14:51PM -0500, Robert Edmonds wrote: > The attached patch removes them. This seems to have been already fixed in the new mount.nfs, so I'm marking it as closed. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL

Bug#433133: ASYNCMOUNTNFS=no

On Wed, Jul 18, 2007 at 05:28:42PM -0600, Bruce Sass wrote: > This doesn't work for me, it kinda makes things worse because now the > messages telling me that statd isn't running disappear off the screen > before I can read them. OK, thanks. > I can manually start rpc.statd, then mount the miss

Bug#433133: ASYNCMOUNTNFS=no

On Thu, Jul 19, 2007 at 03:58:58AM -0600, Bruce Sass wrote: > First thing I tried (with the -10 build, both by adding it to the > options list in fstab and "mount -o..."), mount complained that nolocks > was unsupported by(for?) nfs. Hm, that's interesting. I'll check it out at some point. > I'

Bug#433881: Regression: no longer handles port and mountport

On Thu, Jul 19, 2007 at 07:53:25PM -0700, David Liontooth wrote: > In /etc/fstab, I use this line to mount an NFS drive behind a firewall that > forwards ports with iptables: > > system:/esb /mnt/esb1 nfs > noauto,user,exec,rw,rsize=16k,wsize=16k,hard,intr,port=4000,mountport=5000 0 0 Could you

Bug#434096: nfs-kernel-server in testing has funny dependencies; wants to remove the C++ compiler!

On Sat, Jul 21, 2007 at 03:36:11PM +0200, Folkert van Heusden wrote: > When I want to install nfs-kernel-server, it wants to remove all kinds > of non-related packages: Could you please include the entire command line and the _entire_ output from apt? /* Steinar */ -- Homepage: http://www.sesse.

Bug#434528: nfs-common: No longer supports grpid option

On Tue, Jul 24, 2007 at 11:24:08AM -0500, Dale Purdy wrote: > After upgrading from 1:1.1.0-4 version to 1:1.1.0-11 version, the > grpid option is no longer supported. What is the option supposed to do? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECT

Bug#434387: nfs-common: Please ignore (no)browse option (passed by automount)

On Mon, Jul 23, 2007 at 04:12:51PM +0200, Jochen Eisinger wrote: > mount.nfs shipped with nfs-common does not now about option (no)browse, > which is passed by automount (if present in auto.master). The result is > that it's not possible to access automounted nfs volumes. Neither does the old moun

Bug#434528: nfs-common: No longer supports grpid option

On Tue, Jul 24, 2007 at 11:24:08AM -0500, Dale Purdy wrote: > After upgrading from 1:1.1.0-4 version to 1:1.1.0-11 version, the > grpid option is no longer supported. Actually, I checked, and grpid is for ext2/ext3 file systems only. It does not seem to be supported under NFS at all. > revert to

Bug#434528: nfs-common: No longer supports grpid option

On Tue, Jul 24, 2007 at 01:42:18PM -0500, Dale Purdy wrote: > Perhaps the 1:1.1.0-4 version was filtering out the grpid option so > that the mount still took place. I've considered the same, but it really doesn't make sense. Could you please try a manual mount with 1:1.1.0-4 and 1:1.1.0-11? I'm wo

Bug#433881: Regression: no longer handles port and mountport

On Fri, Jul 20, 2007 at 07:26:09AM -0700, David Liontooth wrote: > Please close -- but this should be documented (or the default changed to > what used to be in effect before nfs-common 1.1.0-6). Thanks, closing. BTW, it seems upstream thinks it is not a bug that there's no fallback to UDP, as i

Bug#434528: Bug#434387: nfs-common: Please ignore (no)browse option (passed by automount)

retitle 434387 mount should pass -s to mount.* helpers reassign 434387 mount forcemerge 434387 434528 thanks On Tue, Jul 24, 2007 at 09:46:12PM +0200, Jochen Eisinger wrote: > the point is, mount from util-linux does not pass the -s (sloppy) option > to external mount commands. That's why mount.nf

Bug#418596: nfs-common: Can not nfs-mount using second interface during boot

On Tue, Apr 10, 2007 at 08:43:41PM +0200, Thomas Nilsson wrote: > I have two network interfaces on "worktoo". One comes up as eth0 during boot. > This is a 10/100 interface. > The second is eth2 which is a 1000 Mb/s connected to a NAS. Hi, It seems like I've gotten this bug back into my lap due

Bug#434775: nfs-common: fails to mount nfs volumes when booted with ip= command line

reassign 434775 initscripts thanks On Thu, Jul 26, 2007 at 10:33:21AM -0700, Andy Sharp wrote: > When booted with ip= on the kernel command line, setting the IP > address, NFS volumns are not mounted because the logic of the > interlocking pieces believes that the interface(s) have not been brough

Bug#430580: can no longer associate with wireless networks

On Mon, Jun 25, 2007 at 08:49:24PM +0200, Steinar H. Gunderson wrote: > Starting just after coming home from DebConf (I believe I updated my > machine the last day), I can suddenly no longer associate with any > networks -- open or not -- with network-manager. The progress indicator >

Bug#351720: tune2fs -O resize_inode

On Sat, Mar 18, 2006 at 08:35:27AM -0500, Theodore Ts'o wrote: > Trying to get ext2prepare's functionality into e2fsprogs is still > pending... You _can_ do it using some careful use of debugfs and > e2fsck, but it's not very safe. Any progress on this? Most of my filesystems are with the resize

Bug#418596: nfs-common: Can not nfs-mount using second interface during boot

On Sat, Jul 28, 2007 at 11:52:52AM +0200, Thomas Nilsson wrote: > I have just returned from vacation and have quite a few things to catch > up with here. But I will take a look at it. I do hope that nothing else > breaks (dependencies) as I am running stable here. I can't guarantee that, sorry. Th

Bug#435056: nfs server hangs on /proc bind-mount

severity 435056 normal thanks On Sat, Jul 28, 2007 at 08:21:47PM -0400, Aron Griffis wrote: > When a client attempts to read a bind-mounted proc directory from the > server, the server never responds. Found this with wireshark and > narrowed down to a simple test. Other bind-mounts seem to be >

Bug#435056: nfs server hangs on /proc bind-mount

On Sat, Jul 28, 2007 at 09:15:30PM -0400, Aron Griffis wrote: > I don't want to export my /proc, I want to export a filesystem that > has proc mounted on a subdir. But NFS exports filesystems, so at least in theory, the /proc in there should be ignored completely unless you export it. > /chr

Bug#435056: nfs server hangs on /proc bind-mount

On Sat, Jul 28, 2007 at 09:33:38PM -0400, Aron Griffis wrote: >> But NFS exports filesystems, so at least in theory, the /proc in there should >> be ignored completely unless you export it. > Exactly. But instead it's hanging Well, nfs-utils does not mess with the mount after it has handed it ove

Bug#444406: VLC does not start in Gnome 2.20

reassign 06 libwxgtk2.6-0 severity 06 grave tags 06 pending sid merge 06 441766 On Fri, Sep 28, 2007 at 12:23:24PM +0200, Jean-Michel Pouré wrote: > Description: VLC segfaults on startup when Gnome 2.6.20 is installed. This is a bug in wxWidgets, not VLC; reassigning and merging.

Bug#444687: ITP: open-vm-tools -- open source implementation of VMware Tools

On Sun, Sep 30, 2007 at 01:13:56PM +0200, Julian Andres Klode wrote: > Description : open source implementation of VMware Tools > > Provides functions like file transfers between host and guest, > and improved performance. You might want to specify a bit what this works with. Does it work o

Bug#444697: vnc4server: segfaults on key press with newer X.org

Package: vnc4server Version: 4.1.1+X4.3.0-21 Severity: grave Justification: renders package unusable Hi, Since I upgraded X.org I can no longer press keys remotely. If I do so, the X server crashes with: Backtrace: 0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c644e] 1: [0xe420] 2: /usr/lib/xorg

Bug#444697: vnc4server: segfaults on key press with newer X.org

On Sun, Sep 30, 2007 at 02:12:29PM +0200, Steinar H. Gunderson wrote: > Since I upgraded X.org I can no longer press keys remotely. If I do so, > the X server crashes with: It turns out that the input ABI changed with version 1.4.0 of the X server, but since VNC does not register as an

Bug#444697: vnc4server: segfaults on key press with newer X.org

On Sun, Sep 30, 2007 at 08:32:14PM +0200, Ola Lundqvist wrote: > But how did you get it work when it FTBFS? Interested... I cp-ed the .so in to the right place. The FTBFS was in some man page stuff I didn't care much about. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE,

Bug#408669: Funny error message: errno 0 (Sucess)

On Sat, Jan 27, 2007 at 06:22:51PM +0100, Oliver Chief O'Cordes wrote: > I got now some funny error messages during the start fo nfsd: > > nfsd[8663]: nfssvc: writting fds to kernel failed: errno 0 (Success) > > I think this message will confuse someone, please check carefully the > error codes.

Bug#408669: Funny error message: errno 0 (Sucess)

On Sat, Jan 27, 2007 at 08:05:43PM +0100, Oliver-Mark Cordes wrote: > Okay, but how? If I start rpc.nfsd with strace I get only some lines > because rpc.nfsd is detaching after this. I don't see this error message > during the day on another machine with the same setup. But the message is > com

Bug#396653: listen: Fails to start with home over NFS

On Sun, Jan 28, 2007 at 11:35:58AM -0200, [EMAIL PROTECTED] wrote: > I've just tested it on a different setup. Instead of getting the same > error as I've got before, listen simply takes forever to start. > > This time I've tried harder to fix it. Installing nfs-common in the > client solved the p

Bug#408669: Funny error message: errno 0 (Sucess)

On Sat, Jan 27, 2007 at 08:28:52PM +0100, Steinar H. Gunderson wrote: > Use strace -vff or similar. But yes, it looks like it's coming from rpc.nfsd; > there are two different lines capable of emitting that message, though. The > "success" thing is a bit of a misnomer; the

Bug#409839: kismet: newer version available

Package: kismet Version: 2006.04.R1-1.1 Severity: wishlist Kismet-2007-01-R1b is the latest version, according to the web page; Debian's version is in other words now nine months old. It would be nice to have this version in experimental (or unstable, when etch is released). Thanks! :-) -- System

Bug#396902: polygen: FTBFS: File "parser.mli", line 1, characters 0-1: Syntax error

On Thu, Nov 16, 2006 at 01:01:33AM +0100, Enrico Zini wrote: > I'm not very skilled at spotting bashisms: could please you point me to > the one in it? echo -e? Yes: fugl:~> dash -c 'echo -e "hello\n"' -e hello fugl:~> bash -c 'echo -e "hello\n"' hello A better suggestion would using printf,

Bug#396528: fixed in hunspell 1.1.4-3.1

On Wed, Nov 15, 2006 at 06:45:56PM -0800, Steve Langasek wrote: > hunspell is still failing to build on arm: OK. In that case, we'll have to wait for the build-deps to be installed on leisner, unless someone can provide another arm for testing. /* Steinar */ -- Homepage: http://www.sesse.net/

Bug#396528: fixed in hunspell 1.1.4-3.1

I already got access to one, but thanks for the offer. Anyhow, the following dpatch fixes the issue: #! /bin/sh /usr/share/dpatch/dpatch-run ## arm_structure_alignment.dpatch by Steinar H. Gunderson <[EMAIL PROTECTED]> ## ## All lines beginning with `## DP:' are a description of the patc

Bug#397759: fails to configure: mv: cannot stat `/etc/chrony/chrony.keys.1.21-2': No such file or directory

On Thu, Nov 09, 2006 at 01:11:05PM -0600, John Hasler wrote: > I will add your patch as it makes the script more robust. I won't be able > to get to it until this weekend. Any progress on this? /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] wit

Bug#396704: nut: diff for NMU version 2.0.4-2.2

: #396704) + + -- Steinar H. Gunderson <[EMAIL PROTECTED]> Thu, 16 Nov 2006 15:38:43 +0100 + nut (2.0.4-2.1) unstable; urgency=low * NMU diff -Nru /tmp/LRfH3vNJyo/nut-2.0.4/debian/nut-usbups.rules /tmp/xC08KP7paL/nut-2.0.4/debian/nut-usbups.rules --- /tmp/LRfH3vNJyo/nut-2.0.4/debi

Bug#397412: wmaker: Wmaker crash on creating desktop

On Thu, Nov 16, 2006 at 10:35:02AM +0500, jamhed wrote: > It doesnt crash :) Aieee :-) OK, here's a version of wmaker built with -g -O2 (the other one was built with -g -O0 -DDEBUG). Is it capable of giving a proper backtrace? http://people.debian.org/~sesse/wmaker_0.92.0-6.1~debug2_i386.deb

Bug#397830: xsabre: It works here

On Sun, Nov 12, 2006 at 04:38:05PM +0100, Frank Gevaerts wrote: > I can't reproduce this here. sabresdl works fine in 8, 16 and 24 bit, so > I guess this shouldn't be grave. The original submitter was using powerpc; you are using i386. That's quite probably related... /* Steinar */ -- Homepage:

Bug#323741: muse-el: FTBFS: emacs not found

tags 323741 + moreinfo unreproducible tags 323741 - patch thanks On Thu, Nov 16, 2006 at 01:17:57PM +0100, Julien Danjou wrote: >> Setting up emacs21 (21.4a+1-1) ... >> [...] >> Done >> [...] >> make[2]: Entering directory `/build/buildd/muse-el-3.02.8/examples' >> EMACS=emacs SITEFLAG=--no-site-f

Bug#396704: nut: diff for NMU version 2.0.4-2.2

On Thu, Nov 16, 2006 at 09:59:45PM +0100, Arnaud Quette wrote: > [quickly passing by, since I just had my 2nd baby this morning ;-) ... ] Congratulations :-) > it's not sufficient (otherwise I would have quickly done it ;-) since > it only addresses udev enabled systems so post 2.6.3 kernels iirc

Bug#397830: xsabre: It does _not_ work on powerpc

On Thu, Nov 16, 2006 at 10:54:03PM +0100, Cyril Brulebois wrote: > I confirm I can reproduce this bug on powerpc. I'll be happy to help > debugging it. Well, it sure sounds like an endianness problem to me. For starters, try running it in gdb and print the backtrace? /* Steinar */ -- Homepage: h

Bug#397830: xsabre: It does _not_ work on powerpc

On Thu, Nov 16, 2006 at 11:18:47PM +0100, Steinar H. Gunderson wrote: > Well, it sure sounds like an endianness problem to me. Looks like I was right. src/txtrmap.C, line 218: fread(&map_w,sizeof(map_w),1,f); fread(&map_h,sizeof(map_h),1,f); fread(&n,sizeof(n),1,f); Fixin

Bug#396704: nut: diff for NMU version 2.0.4-2.3

udev. Correspondingly, rename the + substvar to ${udev}. (Closes: #396704) +* Drop debian/nut-usbups.rules and use upstream's rules instead. Modify + debian/rules correspondigly, patch from Arnaud Quette. + + -- Steinar H. Gunderson <[EMAIL PROTECTED]> Fri, 17 Nov 2006 01:12

Bug#397859: elinks: diff for NMU version 0.11.1-1.1

/5M6mniFYRl/elinks-0.11.1/debian/changelog 2006-11-17 02:26:07.0 +0100 @@ -1,3 +1,11 @@ +elinks (0.11.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Clean up properly in the clean target; patch from Bart Martens. +(Closes: #397859) + + -- Steinar H. Gunderson <[EM

Bug#397828: efp: diff for NMU version 1.4-1.1

) + + -- Steinar H. Gunderson <[EMAIL PROTECTED]> Fri, 17 Nov 2006 02:29:18 +0100 + efp (1.4-1) unstable; urgency=low * New upstream release diff -Nru /tmp/yZM03XRMOb/efp-1.4/debian/control /tmp/Xmqu9ova6d/efp-1.4/debian/control --- /tmp/yZM03XRMOb/efp-1.4/debian/control 2006-11-17

Bug#397412: wmaker: Wmaker crash on creating desktop

On Fri, Nov 17, 2006 at 01:55:17PM +0500, jamhed wrote: > We got it. Finally :) Well, it's a step, at least, but it doesn't really help all that much. Lines 123 and 124 are 123 wWorkspaceMenuUpdate(scr, scr->workspace_menu); 124 wWorkspaceMenuUpdate(scr, scr->clip_ws_menu); And t

Bug#397412: wmaker: Wmaker crash on creating desktop

On Fri, Nov 17, 2006 at 04:59:28PM +0500, jamhed wrote: > What is strange to me that different compiler optimization > produces such a devastating difference. Not really; if it's doing undefined stuff (like writing outside structs), it's just what you would expect happening: Crashes that vary at r

Bug#397412: wmaker: Wmaker crash on creating desktop

On Fri, Nov 17, 2006 at 05:13:17PM +0500, jamhed wrote: > .xinitrc: > valgrind --tool=memcheck --leak-check=full --log-file=/tmp/wmaker.grind wmaker Well, could you please try the debug2 version too? It looks like this was the debug1 version -- or doesn't it crash in valgrind? /* Steinar */ -- H

Bug#397902: seq24: diff for NMU version 0.8.6-1.1

building, to ensure that our +configure script is built from macros that are reliably consistent +with the Makefile.in's generated by automake. Closes: #397902. + * Add autoconf to the build-depends for the above. + + -- Steinar H. Gunderson <[EMAIL PROTECTED]> Fri, 17 Nov 20

Bug#397412: wmaker: Wmaker crash on creating desktop

On Fri, Nov 17, 2006 at 11:59:27PM +0500, jamhed wrote: >> Well, could you please try the debug2 version too? It looks like this was >> the debug1 version -- or doesn't it crash in valgrind? > What is debug2 ? I didnt figured it from man. The last Debian package I sent you. /* Steinar */ -- Hom

Bug#397412: wmaker: Wmaker crash on creating desktop

On Sat, Nov 18, 2006 at 12:21:57AM +0500, jamhed wrote: >> The last Debian package I sent you. > It was debug2. I've run it with valgrind and crash it. That's odd; the valgrind log you sent didn't contain anything about a crash. Actually, when I look at it, it looks incomplete; it's supposed to pr

Bug#396653: listen: Fails to start with home over NFS

severity 396653 important thanks On Tue, Nov 14, 2006 at 07:13:43PM +0100, Julien Valroff wrote: > I have been able to launch listen with home over NFS (tested with NFS > server in both Sarge and Unstable, with both clients in Etch and > Unstable). > > Please try the proposed tests to check if yo

Bug#399127: FTBFS

Package: missingpy Version: 0.8.9 Severity: serious Hi, When trying to build missingpy to look closer at #395104, I discovered that it does not build from source: [ 9 of 12] Compiling MissingPy.FileArchive.GZip ( MissingPy/FileArchive/GZip.hs, dist/build/MissingPy/FileArchive/GZip.o ) [10 o

Bug#399127: FTBFS

On Fri, Nov 17, 2006 at 05:49:19PM -0600, John Goerzen wrote: > That is weird. libghc6-missingh-dev is a build-depend. > Did you have it installed? fugl:~/nmu/missingpy-0.8.9> dpkg -s libghc6-missingh-dev | grep -E '(Status|Version)'

Bug#392953: [NONFREE-DOC:GFDL] package contains non-free documentation

On Sat, Nov 18, 2006 at 01:54:42PM +1030, Ron wrote: > I don't profess to be an authority on the details of this, which is why > I'm seeking clarification -- but it does seem fairly obvious to me that > any invariant section which inhibits our freedom to modify the source is > clearly not DFSG free

Bug#337562: qsynaptics: diff for NMU version 0.22.0-6.1

. (Closes: #337562) + + -- Steinar H. Gunderson <[EMAIL PROTECTED]> Sat, 18 Nov 2006 12:52:40 +0100 + qsynaptics (0.22.0-6) unstable; urgency=low * New maintainer (Closes: #373897) diff -Nru /tmp/uPsn7lvAZS/qsynaptics-0.22.0/debian/control /tmp/SP7YEQSWCs/qsynaptics-0.22.0/debian/c

Bug#389695: up-imapproxy: diff for NMU version 1.2.4-5.1

e non-zero return status of grep killed the init +script. (Closes: #389695) + + -- Steinar H. Gunderson <[EMAIL PROTECTED]> Sat, 18 Nov 2006 15:51:36 +0100 + up-imapproxy (1.2.4-5) unstable; urgency=high * Code enhancements

Bug#398563: poppassd: diff for NMU version 1.8.5-3.1

from Andreas Henriksson. +(Closes: #398563) + + -- Steinar H. Gunderson <[EMAIL PROTECTED]> Tue, 21 Nov 2006 19:54:57 +0100 + poppassd (1.8.5-3) unstable; urgency=low * Move debian/copyright and debian/watch back to the old location. With diff -Nru /tmp/dnGDzWSJFT/poppassd-1.8.5/de

Bug#398634: [phpgacl] alternative patch without hard dependencies on both db clients.

On Wed, Nov 22, 2006 at 01:44:43PM +0100, Andreas Henriksson wrote: > Since I've already created it I'll send this patch to the BTS just for > reference. > This one takes the alternative route of not having a hard-dependency on > both mysql- and postgresql-client, but instead recommends them both a

Bug#399523: [Pkg-uml-pkgs] Processed: really reassign

On Thu, Nov 23, 2006 at 02:28:12PM +0100, Nicolas Boullis wrote: > Some more information: if I set my filesystem to noauto, everything goes > fine (rpc.statd is correctly registered) except that I have to mount it > manually after booting... In that case, it sounds more like a bug in initscripts t

Bug#399454: [autodir] [EMAIL PROTECTED]: Bug#399454: autodir: fails with alert: unexpected autofs packet type 3]

On Thu, Nov 23, 2006 at 05:49:08AM -0800, ramana wrote: > As for the compatibility check, Autodir supports only protocol 4 and in > the future 5. So only check for protocol 4 is needed at this moment. FWIW, after etch I'll put autofs 5 into Debian; etch will, however, stay with autofs 4. /* Stein

Bug#399523: [Pkg-uml-pkgs] Processed: really reassign

On Thu, Nov 23, 2006 at 04:51:40PM +0100, Nicolas Boullis wrote: >> In that case, it sounds more like a bug in initscripts to me? > Sorry, I don't understand why you think it would be a bug in initscripts... Because initscripts is the package checking the fstab for NFS file systems, attempting to

Bug#363435: libmultisync-plugin-syncml: syncml plugin closes the server almost immediately after connection

Package: libmultisync-plugin-syncml Version: 0.82-5.2 Severity: grave I'm trying to use the SyncML plugin (in server mode, without encryption) against a Nokia 3250. Ethereal shows the phone connecting, dumping a full request on the server, but the server almost immediately disconnects. Debugging s

Bug#364017: evms_activate segfaults and locks the machine completely on boot with degraded RAID-5

Package: evms Version: 2.5.2-1.sarge1 Severity: critical Justification: Breaks the entire system Even with the patch for #339891, there are still bugs left with degraded RAID-5s. In my particular case, evms_activate segfaulted and then completely locked the system on boot with a degraded RAID-5. E

Bug#364289: udev: fails to configure

Package: udev Version: 0.090-2 Severity: serious Justification: fails to configure Upgrading udev from 0.087-2 to 0.090-2 gives: Unpacking udev (from .../udev_0.090-2_amd64.deb) ... /var/lib/dpkg/tmp.ci/preinst: line 89: /lib/udev/write_net_rules: No such file or directory dpkg: error proc

Bug#364290: wmaker: segfaults since upgrade to x11r7

Package: wmaker Version: 0.92.0-5.3 Severity: grave Justification: renders package unusable Directly after upgrading to X11R7, wmaker simply segfaults on startup, giving me the familiar crash dialog. I'm not really sure why it would do this, but it's reproducible every time, so I'd guess something

Bug#364429: initramfs-tools: fails to boot with EVMS root

Package: initramfs-tools Version: 0.59b Severity: important Since I upgraded initramfs-tools from 0.53c -> 0.59b (testing machine), new initramfs-es refuse to boot my EVMS root. The boot log is a little long to paste, but a summary follows: [boot] Loading, please wait... Begin: Loading esse

Bug#364290: wmaker: segfaults since upgrade to x11r7

severity 364290 important retitle 364290 wmaker segfaults if it rgb.txt is missing thanks On Sat, Apr 22, 2006 at 03:01:00PM +0200, Steinar H. Gunderson wrote: > Directly after upgrading to X11R7, wmaker simply segfaults on startup, > giving me the familiar crash dialog. I'm not real

Bug#363932: nfs-kernel-server: fails to start

On Thu, Apr 20, 2006 at 01:37:12PM -0400, R. Scott Bailey wrote: > The change introduced in this update to check for "init_nfsd" instead of > "nfsd_version" caused the server to fail to restart on my system after > this upgrade. I manually edited /etc/init.d/nfs-kernel-server to change > the tes

Bug#364625: nfs-common: init script fails to guess whether idmapd is needed

On Mon, Apr 24, 2006 at 04:06:47PM +0200, [EMAIL PROTECTED] wrote: > /etc/default/nfs-common has a comment that says: > > # If you are not using NFSv4 and wish to disable the idmapd daemon, > # then set NEED_IDMAPD to "no". > NEED_IDMAPD= > > This implies that idmapd will be started if not

Bug#364607: horrible nfs read performance

reassign 364607 linux-image-2.6.15-1-686-smp thanks On Mon, Apr 24, 2006 at 03:34:54PM +0200, Arthur de Jong wrote: > If this is a kernel problem rather than an nfs-common problem, please > reassign this bug. It definitely is; nfs-common doesn't touch the mount once it's up (and in the case of th

Bug#363932: nfs-kernel-server: fails to start

On Thu, Apr 20, 2006 at 01:37:12PM -0400, R. Scott Bailey wrote: > I am guessing this symbol was introduced after kernel version 2.6.15-8? > Perhaps it would be better for the interim to check for either init_nfsd > or nfsd_version rather than one alone... This is somewhat odd; this is on an 2.6

Bug#364902: nfs-utils: upstream version 1.0.8 is out

Package: nfs-utils Severity: wishlist Upstream version 1.0.8 is out. Unfortunately, it now depends on librpcsecgss, which is waiting for ITP (see #359648). I'm keeping a placeholder bug here for now, until it can be fixed. -- System Information: Debian Release: testing/unstable APT prefers unst

Bug#359176: initscripts: needs to start rpc.gssd when there are Kerberos NFS mounts involved

On Sat, Apr 01, 2006 at 03:16:57AM +0200, Steinar H. Gunderson wrote: > I implemented it a bit differently, inspired by the way the portmapper is > handled. Basically, if it finds a situation it can't handle (NFSv4 mounts, > which need idmapd and the nfs4 kernel module, or Kerberos

Bug#365447: Cannot upgrade nfs-common in a chroot environment

On Sun, Apr 30, 2006 at 05:59:10PM +1200, Adam Warner wrote: > invoke-rc.d: > invoke-rc.d: WARNING: invoke-rc.d called during shutdown sequence > invoke-rc.d: enabling safe mode: initscript policy layer disabled > invoke-rc.d: ---

Bug#365447: /home/statd

unmerge 365447 thanks On Mon, May 01, 2006 at 04:42:54PM +0200, Josselin Mouette wrote: > merge 365447 365514 > severity 365447 serious > thanks > > Using /home goes against the FHS, which mandates applications not to > rely on it. This seems to be two different bugs caused by different changes

Bug#365447: nfs-common: Can't create /home/statd in post-installation script

On Sun, Apr 30, 2006 at 06:11:53PM +0200, Thomas Krennwallner wrote: > nfs-common tries to add a new user with homedir /home/statd. However, > /home is an nfs-mounted filesystem and user root is not allowed to > create/modify files on it: Actually, it adds a system user; if system users aren't cre

Bug#365514: nfs-common: failed to install for 1.0.7-12

On Fri, May 05, 2006 at 09:53:31AM -0700, Scott Anderson wrote: > Adding new user `statd' (107) with group `nogroup'. > useradd: > /home/devel/openldap/openldap2-2.1.30/libraries/liblber/io.c:161: > ber_free_buf: Assertion `((ber)->ber_opts.lbo_valid==0x2)' failed. > adduser: `/usr/sbin/useradd -d

Bug#366182: fix statd home directory

On Sat, May 06, 2006 at 12:01:11AM +0200, Oskar Liljeblad wrote: > + if [ "$2" = "" ] || dpkg --compare-versions "$2" gt 1.0.7-12; then This line makes no sense. The only version really containing the old directory is 1.0.7-10; however, a user with 1.0.7-11 or 1.0.7-12 could have upgraded fr

Bug#364760: can't export server root filesystem

On Tue, Apr 25, 2006 at 07:16:25AM -0700, Ian Bruce wrote: > I find that it's impossible to successfully export a root filesystem > which is locally mounted from a hard disk. All other exports involving > the same client/server pair work fine; it only fails when the client > attempts to NFS mount t

Bug#365447: acknowledged by developer (Re: Cannot upgrade nfs-common in a chroot environment)

reopen 365447 reassign 365447 initscripts severity 365447 normal merge 365447 359651 thanks On Thu, May 04, 2006 at 12:38:04PM +1200, Adam Warner wrote: > This is the most similar bug report: > "mountall.sh: additional proc mountpoints (for chroots) are not mounted" >

Bug#341887: nfs-kernel-server: fails on starting nfsd --- nfssvc already in use

On Sat, Dec 03, 2005 at 04:17:56PM -0500, Jeff Green wrote: > Port 2049 seems to have been grabbed by some other package (and am unable to > pin down which it is). See for example: > > % netstat -ap | grep 2049 > tcp0 0 *:2049 *:* LISTEN > -

Bug#341887: nfs-kernel-server: fails on starting nfsd --- nfssvc already in use

On Fri, May 05, 2006 at 08:54:09PM -0400, Jeffrey B. Green wrote: > Yes, in particular, I did a complete reinstall and the problem has not > reappeared. We may have to label this one a mystery. Well, it isn't really a mystery as such -- the main problem is that portmap is very fond of assigning r

Bug#341887: nfs-kernel-server: fails on starting nfsd --- nfssvc already in use

On Fri, May 05, 2006 at 09:48:02PM -0400, Jeffrey B. Green wrote: > Yes, I like to think of them as co-dependent servers. I'm assuming that > the init levels have something to do with when they are mounted, > therefore: (I'm off to bed now...) -jeff NFS crossmounts are usually problematic :-) I

Bug#366242: diff for 1:0.7.0-3.1 NMU

/debian/changelog @@ -1,3 +1,11 @@ +abuse-sdl (1:0.7.0-3.1) unstable; urgency=low + + * Non-maintainer upload. + * Change all the S_* variables from long to int32_t to fix several problems +on amd64; patch from Maximiliano Curia. (Closes: #352834). + + -- Steinar H. Gunderson <[EMAIL PROTEC

Bug#359176: Intent to NMU (2.86.ds1-14.1)

Hi, Since I never received any feedback on this bug, I've put an NMU in DELAYED/14-day on gluck. The full patch is attached; please let me know if there are any problems. /* Steinar */ -- Homepage: http://www.sesse.net/ diff -u sysvinit-2.86.ds1/debian/initscripts/etc/init.d/mountnfs.sh sysvini

Bug#363932: Debian bug #363932 / Re: nfs-kernel-server: fails to start

found 363932 1:1.0.7-13 thanks On Tue, May 09, 2006 at 08:06:44PM +0100, Hendrik wrote: > Doh! I guess tar doesn't like reading strange /proc things! I'll try > again... I looked at it, and lo and behold: fffc0022e000 t init_nf [nfsd] Looks like several of your other symbols are man

Bug#366770: debbugs: shows bug reports twice if they're assigned to two binary packages and both are shown

Package: debbugs Version: 2.4.1 Severity: minor debbugs seems to handle display bugs not-so-well, for instance in: http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=nfs-utils;version=1:1.0.7-13;arch=source Some bugs (#246939, #312720) are assigned to two different packages due to merging; thes

Bug#315774: segfault when running grub

On Tue, Aug 16, 2005 at 05:08:51PM +0200, Daniel Sievers wrote: > Btw, the segfault also happens when I try to manually install grub into > the boot sector using the grub shell: > > device (hd0) /dev/hda > root (hd0,0) > setup (hd0) -> segfault FWIW, I get exactly the same -- but when I compiled

Bug#315774: segfault when running grub

On Thu, May 11, 2006 at 08:47:52PM +0200, Daniel Sievers wrote: > Actually it turned out that for me the problem was related to the > grsecurity kernel patch, which (intentionally i guess) kept grub from > installing the mbr. No such thing here; vanilla 2.6.17-rc2 (although in 64-bit mode). /* St

Bug#367009: nfs-common - fails to upgrade

On Fri, May 12, 2006 at 09:33:20PM +0200, Bastian Blank wrote: > nfs-common fails to upgrade: > >> Setting up nfs-common (1.0.7-14) ... >> Stopping NFS common utilities: statd. >> Starting NFS common utilities: statdinvoke-rc.d: initscript nfs-common, >> action "restart" failed. >> dpkg: error pr

Bug#364760: can't export server root filesystem

On Sat, May 06, 2006 at 02:01:56AM +0200, Steinar H. Gunderson wrote: > I'm unable to reproduce this; I can export and mount the root file system > like any other file system, both read-only and read-write. What architecture > are you on? Have you tried a newer kernel than 2.4.27

Bug#364760: can't export server root filesystem

On Sat, May 13, 2006 at 02:03:22AM -0700, Ian Bruce wrote: > Sorry. I've been trying to figure out what kernel package I'm supposed > to use to run Linux v2.6 on a Pentium I, which is what the NFS server > in question is. Do you have any idea about that? linux-image-2.6-486 should do. There are no

Bug#367009: Fails to upgrade for me too

On Sat, May 13, 2006 at 10:27:05AM +0300, Yavor Doganov wrote: > I'm trying to upgrade from 1.0.7-13 and get the same error. > `/etc/init.d/nfs-common restart' works. Here's the output you > requested: Thanks, that's useful. What about "ls -ld /var/lib/nfs/"? I'm unable to reproduce this, but it

Bug#367009: Fails to upgrade for me too

On Sat, May 13, 2006 at 04:54:38PM +0300, Yavor Doganov wrote: >> What about "ls -ld /var/lib/nfs/"? I'm unable to reproduce this, but >> it might be a case of statd not being able to write to /var/lib/nfs. > [EMAIL PROTECTED]:~$ ls -ld /var/lib/nfs/ > drwxr-xr-x 5 root root 4096 2006-05-13 09:56 /

<    7   8   9   10   11   12   13   >