retitle 404073 ITA: autofs -- kernel-based automounter for Linux
owner 404073 !
thankyou
Hi Steinar,
I'm willing to adopt autofs. I work at a site with 120+ clients
running autofs which I could readily use for development and
testing. My present package list is rather small and contains
mostly "a
Hi Daniel and Steinar,
> > This is ok with me.
>
> Fine. :-) Jan: It's yours. Take good care of it. :-)
thanks to both of you! I will. Merry christmas and a happy new year! I doubt
I'll manage to get an upload ready before New Year's Day, because I'm
currently visiting my parents... ;-)
Jan
Hi Luk,
> So, that's something we don't want to do, certainly not at this stage of
> the release cycle.
>
> What's wrong with Steinar's suggestion to change the name of the autofs
> script to be something between 19nis and 20apache?
conclusion first: If that's the ultimate response of the releas
On Thu, Jan 25, 2007 at 01:19:33AM +0100, Steinar H. Gunderson wrote:
> You don't need to rename the /etc/init.d file, just the symlink in
> /etc/rc?.d.
Sure, if I reimplemented the update-rc.d functionality in postinst,
which I'm not very fond of either. Maybe it's worth it, to keep the
hack as m
On Thu, Jan 25, 2007 at 01:35:20AM +, Stephen Gran wrote:
> I may be missing something, but why does it need to be moved? It starts
> in rcS as well as rc2, so this should only ever be an issue in the rare
> cases when you have to switch to runlevel 1 and back, right? This seems
> like a rare
Hi,
> You can also use "Mrxvt" (note the capital M) (or "XTerm") as the
> Resourcename. These settings will be applied whatever the actual
> programm name is.
>
> So if you have any "global" settings that should not be depend on the filename
> this is the name you should use.
>
> I agree, it is
block 341140 by 400952
thankyou
Hi Anibal and Javier,
I (as the new maintainer of autofs) would like to have the issue settled
before Etch is released... what consequences do you fear could arise from
moving the script? The present situation forces all users of nis&autofs
to manually shuffle thei
Hi Norman,
> Package: autofs
> Version: 4.1.4+debian-1
> Severity: normal
are you filing this bug because your map has worked before (behaviour of autofs
has changed), or did it never work?
> I am trying to use autofs to automount a Samba filesystem exported by
> a machine whose IP address is as
severity 398752 wishlist
clone 398752 -1
reassign -1 debian-policy
retitle -1 (Re-)Add "editor" to virtual package list
block 398752 by -1
thankyou
(adding CC:d-policy, last time to CC:d-devel)
Hi Eddy,
> Well, some people provided some (good) counter examples, but they seem
> unreplied.
> Look
Hi Steven!
> I'm working away at a BSP just now, and came across this bug. Do you
> need a sponsored upload? Can I just upload an NMU with the patch in the
> BTS? Whatever works for you.
Sure, just go ahead and do a NMU. I've already got some more changes in
my local build area which I haven't
Hi Eddy,
(CCing d-devel, joining Christoph Haas' thread)
> The nvi package is an editor, but in spite of that it does not provide
> the virtual package "editor".
>
> Please add this Provides.
please see this discussion thread[1] back in 1996 about the virtual packages
list that is included in th
Package: lilo
Version: 22.7.3-1.4
Severity: normal
Tags: patch
Hi,
my xsession's terminals (which I now and then run lilo from) happen
to inherit an inotify file descriptor from the window manager. Lilo
happens to encounter it when descending into /dev/fd, but unluckily
those fds return
] st_mod
Hi Marcus,
I tagged the bug moreinfo because I suspected HAL was causing the timeout
mechanism to fail, and Roman hadn't made a final statement whether stopping
HAL fixed the problem for him.
[indexing your links for easy backreference ;) ]
> But the original problem has been reported elsewhere:
Hi,
a piece of information I forgot to include in the report, explaining
why lilo scans /dev at all: I have a few encrypted device-mapper
containers that show up in /proc/partitions as
] [EMAIL PROTECTED]:~# cat lilo2_parts
] major minor #blocks name
] [...]
] 33719759456 hdf7
] 254
Hi Ethan,
> After further investigation, I discovered that this seems to be unique
> to the amd64 port. The depends for the i386 port include libfreetype6
> and mrxvt-full correctly employes freetype. However, the amd64
> package does not depend on libfreetype6 and does not take advantage of
> f
Hi Clement,
a new package is being worked on. Actually, the most recent
upstream version is 0.16.8.3 (released Aug 17th). ;-)
But note that not only the binary's name has changed - the
user configuration has moved from .enlightenment to .e16
and changed much of its internal structure and syntax
(
package rxvt-beta
tags 379590 + pending
thankyou
Hi,
I've completely rewritten debian/rules. That should also rid us of
that bashism. ;-) Upload follows during the next days.
Regards,
Jan
signature.asc
Description: Digital signature
package firefox
found 361183 1.5.dfsg+1.5.0.6-4
thankyou
Hi,
> > Can you try with the following value in ~/.mozilla/firefox/rc ?
> > MOZ_DISABLE_PANGO=1
>
> Heh, it solves the problem. Thanks.
doesn't solve it here. MathML display is better with Pango disabled,
but far from perfect. Example pag
Hi,
yes, I'm sorry. I've just verified that mrxvt, mrxvt-cjk and mrxvt-mini
now contain a few files simultaneously, which prevents you from installing
them together (unless you enforce it with
dpkg -i --force-overwrite /var/cache/apt/archives/mrxvt*0.5.2-1*deb ).
I'm currently rewriting the bui
retitle 351695 nvi: display of certain 8bit-char/locale combinations ambiguous
thankyou
Hi,
(from iso8859-1, -2, -7, -9, -15, -16)
Oct Dec Hex Char Description
240 160 A0 NO-BREAK SPACE
tags 98407 = wontfix
severity 98407 minor
retitle 98407 nvi init script runs before NIS is up
thankyou
Hi,
there's not much I can do about this. The present situation is:
* Networking is available at S:40.
* Nvi is installed at S:70.
* Nis is called in the multi-user runlevels only, [2-5]:19.
N
tags 218289 + pending
thankyou
Hi,
I've now implemented the temporary umask change around mkstemp(),
setting it to original_umask & 0177. This ensures that the tempfile
is editable and can be properly deleted afterwards.
Regards,
Jan
signature.asc
Description: Digital signature
Hi,
do you have any new information regarding this bug? I have just
taken over maintenance of this package and am looking through
the existing bugs...
I can't reproduce the problem on any 2.6 system, SMP systems
included... can you give me some related information or tips
on how to reproduce it?
Hi,
> dpkg: error processing mt-st (--purge):
> subprocess post-removal script returned error exit status 1
>
> Consecutive calls to 'dpkg --purge' gets the same error and no more
> information.
>
> Looking at /var/lib/dpkg/info/mt-st.postrm, I think it's due to:
>
> if [ "$1" = purge ]; then
tags 381901 pending
thankyou
Hi,
> I didn't know this, good to know, but it's not the point because the
> above command is the last one in the script, which exits with the return
> code of the command, i.e. 1 if the link doesn't exist.
Ah, sure, you're right, I'd forgotten about the last-comma
Package: debhelper
Version: 5.0.37.3
Severity: normal
Hi,
my package's (mt-st) postrm is currently 100% dh-generated, and the last snippet
happens to be written by dh_installudev. This generates something like:
] if [ "$1" = purge ]; then
] [ -L udevrule ] && rm udevrule
] fi
If udevrule does
Hi,
does the problem still exist? - I faintly recall having seen this problem
in a lot of terminal emulators, including xterm... sometimes while using
lynx/links, but also on other occasions.
Could you provide me with your current version(s) and configuration options
if you're still able to repro
Hi,
I was able to track it down...
] [EMAIL PROTECTED]:~$ mpg321 -q favourite.mp3
]
] [1]+ Stopped mpg321 -q favourite.mp3
] [EMAIL PROTECTED]:~$ fg
] mpg321 -q favourite.mp3
] ALSA: underrun, at least 0ms.
]
] [1]+ Stopped mpg321 -q favourite.mp3
] [EMAIL PRO
tags 394778 + pending
thankyou
Hi Paul,
thanks for your report - fix is included, I will ask my sponsor to upload
soon.
Regards,
Jan
signature.asc
Description: Digital signature
Hi Axel, hi Brian,
> Since the current maintainer of screen in Debian is quite busy in real
> life at the moment, I'm thinking about doing an Non-Maintainer Upload
> (NMU) for screen. Your packaging work comes in quite handy there,
> thanks! :-)
thanks to both of you for your work on getting the
clone 375774 -1
reassign -1 amanda-client
retitle -1 amanda: should use tar's new O_NOATIME support
retitle 375774 tar manpage should mention both --atime-preserve flavours
thankyou
Hi Bdale,
tar upstream has now included support for this feature, however the
manpage doesn't mention it yet (there
Hi Roland,
I don't understand your bug description... Do you mean the security
feature that the environment variables LD_LIBRARY_PATH and LD_PRELOAD
are not (or only partially) considered when executing set*id binaries?
This is not specific to screen - it is documented in ld.so(1).
Regards,
Jan
Hi Jeff,
works for me... however, Ctrl+Q alone does not insert a ^Q - you
have to escape it with Ctrl+V. So
:viu ^V^Q|
should work (you'll only see the ^Q - interpret the above as keystroke
sequence).
Regards,
Jan
signature.asc
Description: Digital signature
Hi Brice, hi Joey,
(simultaneously replying to both bugs because the problem in
the underlying C libraries seems to be identical)
I can provide a short bug summary, maybe it's helpful.
For PF_UNIX connections with an XDM-AUTHORIZATION-1 key, the
client (libx11/libxcb) constructs its 24-byte auth
Hi,
> Are you using xdm? If yes, then that might be the corner case. AFAIK
> other DMs are not setting a XDM-AUTHORIZATION-COOKIE[1], so noone sees
> this problem[2].
yes, I know that only xdm users are affected. On the other hand I
couldn't believe that its userbase should be so small, especiall
tags 445360 + unreproducible
thankyou
Hi Josip,
(gdb) p TermWin.nrow
$37 = 24
(gdb) p (text_t *[24])*(screen.text + TermWin.saveLines)
$38 = {
0x543a10 "i:Exit -:PrevPg :NextPg v:View Attachm. d:Del r:Reply
j:Next ?:Help ",
0x543d40 "X-Spam-Level:", ' ' ,
0x544070 "Delivery-date: S
Hi,
> How do I get gdb to work with this? I've tried running it until that point,
> and then Ctrl+Z it in gdb to be able to type commands, but then:
that's exactly the way to do it (I use CTRL+C, but that shouldn't matter).
The problem is that rxvt is built with too little debugging info, regardl
Ah,
forgot one thing, to avoid a misunderstanding, because you quoted
my gdb output: those NULL pointers are in _your_ session. I
extracted that from your second core file.
The contents of the display have already been partially replaced
at the time of the crash... the lines above the five 0x0s ar
Hi,
> Ah, yes, true. Here you go:
ok, the results are really strange. A comparison between the lists of pointers
before and after the crash...
] (BEFORE)
> $1 = {
> 0x54dfa0 "i:Exit -:PrevPg :NextPg v:View Attachm. d:Del r:Reply
> j:Next ?:Help ",
> 0x541d60 "Delivery-date: Sun, 22 Ju
package mrxvt
tags 456033 + pending patch
thankyou
Hi,
I don't get the spurious 'c', but the beep indeed. I only use
nvi (which is unaffected), and I didn't try every editor around,
hoping that the problem description above that AC_INIT macro was
complete. (I initially wanted to make it '0.5.3+sv
Hi Morty,
can you please verify that this problem still exists? I have no problem
reattaching to a screen session whose former parent was killed with HUP...
please try the new 4.0.3-1.
Regards,
Jan
signature.asc
Description: Digital signature
Hi Branden,
I can't even reproduce it on my 43P-140 - paging through the file looks
a bit ugly at times due to missing glyphs in my font, but it doesn't
crash screen.
I'll close the bug report if no further reports of this problem arrive.
Regards,
Jan
signature.asc
Description: Digital signa
Hi Tomas,
> Rationale: I think screen is a shell in the best IT-sense of the word.
> So I ask you to please move it to a more specific section.
screen is not a shell in itself but more some kind of terminal emulator
like xterm IMHO - it provides an interface to an arbitrary number of
shells, just
Hi,
can you still reproduce the bug? Is there a pattern when the bug appears?
Did you manage to produce a log with strace?
Regards,
Jan
signature.asc
Description: Digital signature
tags 287183 + unreproducible
thankyou
Hi Fedor,
is this still the case? I don't have any problems running mc inside
screen, no matter whether the underlying terminal is a tty or a pty
allocated by xterm...
Regards,
Jan
signature.asc
Description: Digital signature
tags 419721 + unreproducible
thankyou
Hi Marc,
can you verify that the problem still exists in 4.0.3-1? I'm unable
to reproduce it...
] echo -e "$(tput bold)test$(tput sgr0)test"
shows eight characters, four of them bold, as it should - inside screen
and without.
Regards,
Jan
signature.asc
package wnpp
owner 305463 !
retitle 305463 ITA: inform-mode -- Emacs mode for editing Inform files
tags 305463 + pending
thankyou
Hey,
more QA work for me. ;) Upload prepared, will enter tomorrow.
(I myself write inform from time to time, so removal from archive
is no admissible option for me)
Hi Esteban,
do you still intend to adopt the package? I'd prepare an QA upload
to fix some of the outstanding bugs, but I don't want to duplicate
work that you've probably already done...
Regards,
Jan
signature.asc
Description: Digital signature
tags 426328 + upstream
thankyou
Hi,
you're absolutely right. Code and documentation obviously contradict each
other. Fixing it is no problem, but I'm waiting for an answer from upstream
telling me which behaviour is the desired one. Shouldn't take too long though.
Regards,
Jan
signature.asc
Hi,
that error is coming from libc, probably as a response to pututline().
Can you reproduce this bug at will? On what line (terminal/pty) are you
when this occurs, and what does your utmp look like?
Regards,
Jan
signature.asc
Description: Digital signature
Hi Ian,
is this still the case? At least your first method of reproducing
the bug does no longer work, i.e. screen does not crash.
Also, if the client screen process dies, the (then detached)
screen instance should continue to work - see #416362 for a
similar report, which I can't reproduce, too.
tags 432089 + patch
thankyou
Hi Craig, hi Wouter,
here's a patch that fixes the bug. sysctl is trying to save every single
byte when malloc()ing buffers, and here it tried to save one byte too much. ;)
Proof (valgrind):
] ==16975== Invalid write of size 1
] ==16975==at 0x8048F10: ReadSetting
Ouch, forgotten to attach.
#! /bin/sh /usr/share/dpatch/dpatch-run
## 30sysctl_off_by_one.dpatch by <[EMAIL PROTECTED]>
##
## DP: Fix off-by-one error. If tmpname is a directory, a trailing slash
## DP: is appended before the buffer is passed on to DisplayAll()...
## DP: but that slash doesn't fit
tags 256376 + patch
thankyou
Hi Craig,
this update fixes the syntax error and adds another line Jeremiah had
apparently forgotten. Now it Works For Me[tm]... I can resize top at
will (down to 1 line and back to 60) without problems.
Regards,
Jan
#! /bin/sh /usr/share/dpatch/dpatch-run
## 40top
Just for the record... in and cs statistics are fine on
]] echo "$(uname -a) // $(grep-status -nP procps -sVersion)"
] Linux hejre 2.6.22.1 #1 PREEMPT Fri Jul 20 00:47:41 CEST 2007 i686 GNU/Linux
// 1:3.2.7-3
] Linux naebdyr 2.6.22.1 #3 Thu Aug 2 23:03:19 CEST 2007 ppc GNU/Linux //
1:3.2.7-3
] L
Hi,
I'm not sure I can follow you here:
> Alternatively, you can call bye_bye() with the
> dont_care_sig parameter, but be aware that there are a few functions
> that take the dont_care_sig parameter, but throw that value away.
The other installed signal-handlers suspend() and wins_resize_sighan
tags 292721 + patch
thankyou
Hi,
nowadays (1:3.2.7-3) it doesn't even display an error message, but just
exits silently. It should at least print a diagnostic. Patch attached.
Regards,
Jan
signature.asc
Description: Digital signature
Thanks for the reminder, Justin. This has happened to me way too often
during the last days...
(really attaching the patch)
Jan
#! /bin/sh /usr/share/dpatch/dpatch-run
## 45_proc_complain_unmounted_proc.dpatch by <[EMAIL PROTECTED]>
##
## DP: Complain when /proc/version cannot be found instead
Hi,
> However, pgrep/pkill does not take a
> parameter to list how to use the command, so usage() should always
> exit with EXIT_USAGE.
in fact, there *is* such a command line parameter: pgrep -?. The problem
here is that the arbitrarily chosen "-?" and the behaviour of getopt(3)
upon encounterin
Hi Thomas,
> to what value did you increase MAXSTR?
I did a quick estimate by resizing my xterm to maximum
(on 1600x1200 with a rather tiny font, yielding 264 columns)
and multiplying by 2 for a possible xinerama/dualhead setup.
The outcome was more than 512, so I increased it to 768.
If it's th
Hi,
I have finally made up my mind and implemented my own workaround,
which I'll include in 4.0.3-3. It gets by without alarm signals and
jumping (which is always a bit awkward to debug) but uses an additional
call to select() instead to make sure the socket in question won't block.
The solution
tags 205531 = patch pending
thankyou
Hi,
this is an undocumented "feature" indeed. I've now extended the manpage
and texinfo paragraphs to include this. I agree that this automatic
activation is quite dubious, but I don't want to fork from upstream here
if there's such a simple solution as adding
Hi,
what is the current status of this bug? Even if screen itself receives SIGHUP
(due to a closing terminal), it shouldn't propagate it to binaries running
inside it, and as far as I can tell, it does not anymore. (I've closed several
other HUP-related reports in the last days, no original submit
Hi,
I can confirm the behaviour. '-d -r' makes screen start in two stages:
first identifying and detaching the displays that are currently attached
to the selected session, and then attaching itself. If the second
'-d -r' starts to search for other displays before the first has
successfully attach
Hi,
could you please verify that this problem still exists with recent versions
of screen? Justin, have you seen recent occurrences of this or do you have
a reliable way to reproduce this? I have read the upstream report, but some
responses there make me believe that at least a few of them are hav
retitle 133807 screen user must own pty (breaks with 'su')
thankyou
Hi,
for the record, even a setuid screen doesn't help, because it explicitly drops
privileges before trying to access the terminal. (And that's fine, otherwise
you could try to hijack arbitrary ptys.) This is clearly wontfix, and
severity 48 normal
tags 48 + pending
thankyou
Hi Benoit,
I don't like the idea of a default buffer file with mode 0666 *at all* -
I am therefore completely disabling the special-casing of /tmp/screen-exchange.
The usual use case of this file will still work, depending on the umask of the
tags 426328 = pending
thankyou
Hi,
I've now implemented a fix on my own to make the program's behaviour
match the documentation. Plain '-q -ls' tells you only the existence
and number of non-dead screens (9 for no sockets at all, 10 for
some sockets (which may be dead) and +1 for each non-dead) -
tags 495806 + unreproducible
thankyou
Hi Troy,
I can't reproduce the problem, no matter which PAM version I have installed
(0.99.7 or 1.0.1). You are referring to the password prompt that screen shows
upon resumption of a screen session that has been locked with the 'lockscreen'
command, right?
Hi Raphael,
your report is correct, but if /var/tmp/vi.recover was really a symlink
to some existing directory (like /), mkdir -p won't fail at all - in fact,
it won't even be executed because the [ -d ] test will already succeed.
I'll fix it properly - thanks for catching it.
Regards,
Jan
-
Package: mt-st
Version: 0.9b-1
Severity: serious
Tags: pending
(filing this bug against myself to prevent 0.9b-1 from migrating to
testing, thus saving our testing users from having to play dependency
ping-pong)
Package's changelog mentions a new build-dep on linux-kernel-headers,
introduced was
tags 524211 + patch
thankyou
Hi,
attached is a patch that fixes the /usr/local problem and also
adjusts the build dependencies (libxaw7 is not necessary at all,
and libglib1.2-dev should be replaced by libglib2.0-dev).
A debhelper upgrade might be in order, too, but I didn't want
to be too invasi
nt"
+exit 1
+fi
+case "$1" in
+-patch) patch $pdir -f --no-backup-if-mismatch -p0 < $0;;
+-unpatch) patch $pdir -f --no-backup-if-mismatch -R -p0 < $0;;
+*)
+ echo >&2 "`basename $0`: script expects -patch|-unpatch as argument"
+ exit
tags 526160 + patch
thankyou
Hi,
ksh is failing because libc0.1-dev does not provide TAB{0,1,2,3}, but
only TAB{0,3} (=> ). As this seems to be intentional (see
http://www.freshports.org/sysutils/coreutils/ for the corresponding
changes to the BSD coreutils), ksh should probably just play along
a
Hi,
this was a bug in libc0.1-dev, not in ksh itself, cf. #522686. ksh
simply needs to be rebuilt on kfreebsd-*.
Regards,
Jan
signature.asc
Description: Digital signature
Hi,
while you're at it, there is another bug in that small perl
function: do_get_use_md5() recurses when it encounters an
'@include' line and overwrites its $use_md5 variable with
the result. Therefore the following /etc/pam.d/passwd would
make the function return 0:
requiredpam_unix.so m
Package: nmap
Severity: important
Hi,
nmap has an internal copy of liblua and uses it instead of the system library
because the configure script fails to detect the header files:
} (package build log)
] checking lua.h usability... no
] checking lua.h presence... no
] checking for lua.h... no
] c
tags 527997 = patch
thankyou
I might as well attach the appropriate patch... (autoconf is called
from the upstream Makefile, which makes the build process a bit
cumbersome now that we're patching configure.ac - you might choose
to patch configure itself instead, or call autoconf early in the
build
Package: wpasupplicant
Version: 0.6.9-2
Severity: important
Tags: security
Hi,
your syslog patch changes _wpa_hexdump() to create the debug string in a
local buffer on the stack before emitting it - however you boldly assume
that 2048B "should be enough for everyone". When connecting to a WPA-EAP
Hi,
> Thanks Jan. But if you get a chance, I'd love to see a patch which
> checks for both the plain "lua" and "lua5.1" versions. That way it
> would still work on platforms which just use plain "lua" and so it
> would be appropriate for upstream integration. If we add it to an
> Nmap release,
Hi,
NMU is about to hit unstable and s-p-u. I've added the attached
patch to the quilt series.
Regards,
Jan
Add fix for CVE 2008-6792 and another related bug in do_get_use_md5().
-- James Westby
-- Jan Christoph Nordholz
--- system-tools-backends-2.6.0.orig/Users/Users.pm 2008-03-
Hi,
> Thanks Jan. Our current svn does not have an nselibs-bin directory
> anyway. I've applied your patch to our configure.ac and regenerated
> configure in our latest SVN.
All the better. SVN checkout works great here, too, system lua5.1 is
detected and linked into nmap instead of the interna
Hi Emmanuel,
> It would be nice if you could attach your patch to this bug report
> even if it is not fully functionnal. It could help upstream developers
> to add this feature more quickly.
ah, I see there has been another 0.2.6 release. I thought that branch
would die soon now that 0.3 developm
Hi,
> i think that the code you produced for 0.2.x branch could helped to
> add this feature in one of the next release.
ah ok, I believed 0.3 was written (almost) from scratch, so I wasn't sure
whether there would be any benefit. I've attached my patch, but there are
a few remarks:
* The gnutls
tags 534732 = confirmed
thankyou
Hi again,
> I can't reproduce that here with 1.81.6-7...
ok, I take that back, it does indeed produce strange expansions sometimes.
Will investigate.
Regards,
Jan
signature.asc
Description: Digital signature
Hi Jeffrey,
> The expansion of numbered backups is incorrect. The actual expansion
> that nvi produces is somewhat random. I get the weirdest results when
> editing from the linux console, logged in as root. The expansion of
> numbered backups used to work correctly with nvi 1.79 version.
I ca
Package: libgnutls13
Version: 1.7.7-1
Tags: experimental
Hi,
code and documentation seem to have diverged when TLS1.2 was introduced:
-> lib/gnutls_priority.c, lines 252 ff., gnutls_set_default_priority()
] [...]
] * The order is TLS 1.2, TLS 1.1, TLS 1.0, SSL3 for protocols.
] * RSA, DHE_D
Hi Julien,
sorry this bug lay around that long... can you reproduce the problem
with recent package and kernel versions? If so, could you post your
current version numbers, the output of 'ifconfig -a' and (if you can
get it) the oops trace?
Thanks,
Jan
signature.asc
Description: Digital signa
severity 362213 minor
thankyou
Hi,
the warnings come from a function-like macro that sanitizes its (pointer)
arguments before performing string operations on them. As this is not the
kind of programming error -Waddress is meant to detect, I would not classify
this as a build error. Currently all
tags 430054 + patch
thankyou
Hi,
apparently just a missing #include. Patch attached.
Regards,
Jan
--- src/gdeb/main.cc.orig 2007-06-28 21:30:55.0 +0200
+++ src/gdeb/main.cc2007-06-28 21:27:15.0 +0200
@@ -27,6 +27,7 @@
#include "config.h"
+#include
#include
#i
Hi,
this patch just replaces x_strdup() with plain strdup(), which makes the
warning go away without changing the behaviour of the code.
However, the benefits of using -Werror are minimal compared to the number
of possible FTBFS bugs that may surface during compiler transitions...
Regards,
Jan
tags 386099 + patch
thankyou
Hi,
this patch removes the definition of those operators for the included Integer
and
Rational classes.
Regards,
Jan
diff -aur magnus-20060324.ORIG/back_end/libg++/include/Integer.h magnus-20060324/back_end/libg++/include/Integer.h
--- magnus-20060324.ORIG/back_en
Hi,
> NIS starts AFTER autofs due to lexicografic order. That prevents NIS
> maps working at boot. Moving to 20 solves the issue. Of course, you need
> to check that autofs starts after ALL other possible back-end engines
> for maps. That's unfortunately also an etch issue :-/
yes, sadly the solu
retitle 431715 ITA: gdome2 -- DOM level2 library for accessing XML files
owner 431715 !
thankyou
Hi Enrico,
if you don't object, I'd like to assimilate this one into my list
of dormant-upstream packages. I have built a new version that
closes all open bug reports and updates the build system (deb
retitle 426808 tar: using -W circumvents sanity checks and provokes data loss
thankyou
Hi,
it gets even worse...
] [EMAIL PROTECTED]:/tmp>touch X
] [EMAIL PROTECTED]:/tmp>tar czf XT X
] [EMAIL PROTECTED]:/tmp>file XT
] XT: gzip compressed data, from Unix, last modified: Sat Jul 7 18:36:01 2007
Hi Daniel,
I don't quite understand. The default socket directory is in /var/run,
so SOCKDIR_IS_LOCAL_TO_HOST is true and therefore enabled (which causes
the hostname checks to be disabled). Did you change that default to
$HOME/.screen or a similar location for your sockets so you accidentally
kil
Hi Victor,
> This patch has been in FreeBSD ports/sysutils/screen for a long time.
> It would be good if we can have it as well.
looks nice! I'll give it a thorough look and include it in -5.
Thanks!
Jan
signature.asc
Description: Digital signature
Hi Kumar,
> Though I am sure you are following this thread, I would, again, urge
> you to consider enabling 256 colours in screen, since I really don't
> want to keep recompiling screen for every upstream release in
> future.
yes, I do - this one is on my short-term todo list (read as: likely to
Hi Modesto,
could you provide some more details? What does your auto.master
exactly look like, and when do those errors appear? (Perhaps you
can paste a bit of context or describe it more verbosely)
Thanks!
Jan
signature.asc
Description: Digital signature
Hi Daniel,
> I have SCREENDIR set in my environment; I have for years. I don't
> remember exactly why any more. I suspect some machine used to eat
> things left in /tmp which was the default at the time.
ah, of course, I'd forgotten about that variable. Hmm, but that makes
a compile-time switch
1 - 100 of 214 matches
Mail list logo
