similar to: R CMD build: "Subdirectory 'R' contains invalid file names"

i'm trying to use the ssh command's -f option with OpenSSH v2.1.1p4 on linux (RedHat v6.2). this option doesn't seem to be working properly on my system - the specified is run succesfully but it isn't put to the background. is this a known problem? also, OpenSSH doesn't seem to interoperate with SSH Communications Security's ssh v2.3.0 (apparently because of different

Greetings everyone, I'm trying to compile asterisk for an AVR32 (Atmel NGW100). Buildroot for AVR32 already has the asterisk package, though it has bugs. Firstly it tries to apply a patch for 1.2 on a 1.6, but deleting the contents of the patch file did the trick. Now, the problem is making asterisk. The first error is because asterisk needed to be ./configure:ed. Trying to just do

Hi, I am having a really strange problem with my Samba shares on Debian Buster. None of the users can access any shares, which reside on ZFS-filesystem. Any other share works just fine. For example, if I create a normal folder to /home with same permissions and replace a ZFS-share with that, it works fine. When accessing any ZFS-shares the following error is recorded: Jan 08 22:39:56

Hello, I tried lunch something but the anwer was "can't find apps" (I used absolute path too) [serge@rex wineserver-rex]$ wine /windows/ProgramFiles/Office/winword.exe Invoking /opt/wine/bin/wine.bin /windows/ProgramFiles/Office/winword.exe ... Wine failed with return code 2 /usr/bin/wine: line 516: 1046 Compl?t? tail -f $log_name Deleting /tmp/wine.log.Vv4t6C

I added one testshare /home/testijako and connected to it with the same credentials as I would connect to ZFS-shares. Then I did the strace to that particular PID and tried connecting to one ZFS-share. There was indeed an error which might have something to do with this issue: Line 2001: lstat("/tank/rex", 0x7fff1f6fb2c0) = -1 ENOENT (No such file or directory) Im sure that folder

On Wed, Dec 24, 2014 at 2:43 PM, Craig Topper <craig.topper at gmail.com> wrote: > I believe this particular error is caused by this. That seems easy enough > to just drop the bit. Do you have other non-mmx examples? > > case TYPE_MM: \ > if (index > 7) \ > *valid = 0;

Greetings, The following question has come up in an off-list discussion. Is it possible to construct a regular expression 'rex' out of two given regular expressions 'rex1' and 'rex2', such that a character string X matches 'rex' if and only if X matches 'rex1' AND X does not match 'rex2'? The desired end result can be achieved by logically combining

Create an object hierarchy to represent different bootloaders for Linux guests, moving the separate handling of grub1 and grub2 in different classes: this isolates the code for each type of bootloader together, instead of scattering it all around. This is mostly code refactoring, with no actual behaviour change. --- po/POTFILES-ml | 1 + v2v/Makefile.am | 2 + v2v/bootloaders.ml

hi, i think the current X86 disassembler is quite broken and fails badly on handling REX for x86_64 code. below are some examples: $ echo "0x0f,0xeb,0xc3"|./Release+Asserts/bin/llvm-mc -disassemble -triple=x86_64 .text por %mm3, %mm0 $ echo "0x40,0x0f,0xeb,0xc3"|./Release+Asserts/bin/llvm-mc -disassemble -triple=x86_64 .text por %mm3, %mm0 $ echo

I'm trying to troubleshoot a case where R crashes on Windows. It does not occur at all with my R v2.1.0 patched (2005-05-09), but happens on R v2.1.1 (patched or non-patched) in many different cases. The R v2.2.0dev (2005-07-15) also got this problem (although it won't crash on the below example). I previously reported this

> On 02 August 2018 at 16:08 Henrik Larsson <dovecot-user at spambox.dk> wrote: > > > On 15-07-2018 11:42, Henrik Larsson wrote: > > After upgrading Dovecot to 2.3.2.1 and Pigeonhole to 0.5.2, > > managesieve stopped working. > > > > I'm using FreeBSD ports tree, to build these. Only domains have been > > modified in below output. > >

Tracking down a problem with one of our benchmark codes, we've discovered that some of the patterns in X86InstrX86-64.td are wrong. Specifically: def MOV64toPQIrm : RPDI<0x6E, MRMSrcMem, (outs VR128:$dst), (ins i64mem:$src), "mov{d|q}\t{$src, $dst|$dst, $src}", [(set VR128:$dst, (v2i64 (scalar_to_vector

pigeonhole 0.5.0 has been already released... ---Aki TuomiDovecot oy -------- Original message --------From: Daniel Kenzelmann <dovecot.org at k8n.de> Date: 03/01/2018 21:31 (GMT+02:00) To: Rhys Williams <lux+mailinglists at melted.me>, dovecot at dovecot.org Subject: Re: dovecot v2.3.0: imap segfault when sieve_extprograms_plugin.so ? called Hi, see the following thread:

Tabs should not be doubly-escaped in regexp. Signed-off-by: Shahar Lev <shahar@stratoscale.com> --- v2v/convert_linux.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml index adbcaa2..1e9e689 100644 --- a/v2v/convert_linux.ml +++ b/v2v/convert_linux.ml @@ -581,7 +581,7 @@ let rec convert ~keep_serial_console (g : G.guestfs)

Hello, On 31.01.2018 22:35, Stephan Bosch wrote: > Op 1/31/2018 om 6:17 PM schreef Christian Authmann: >> Hello, >> >> Sometimes, when delivering mails, this warning appears in my syslog: >> >>> lda(...): Warning: Failed to parse return-path header: Invalid >> character in localpart >> >> dovecot-lda still exits with 0 and the mail is inserted

1. AWS the name tag is not mandatory - using default as a name 2. AWD doesn't prefix 'ovf:' as prefix to disk path There is an open bug for oVirt: https://bugzilla.redhat.com/show_bug.cgi?id=1371843 Signed-off-by: Shahar Havivi <shaharh@redhat.com> --- v2v/input_ova.ml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/v2v/input_ova.ml

Try to improve the way packages of VMware tools are removed from YUM-based guests: - when filtering the package itself from its providers, do a stricter check so either the provide is the unversioned package, or it is exactly its own name - if the package has no other providers, then going further will cause the invocation of 'yum install' with no packages, and thus the package

1. AWS the name tag is not mandatory - using default as a name 2. AWD doesn't prefix 'ovf:' as prefix to disk path There is an open bug for oVirt: https://bugzilla.redhat.com/show_bug.cgi?id=1371843 Signed-off-by: Shahar Havivi <shaharh@redhat.com> --- v2v/input_ova.ml | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/v2v/input_ova.ml

The OVF standard allows the use of SHA256 hashes in the manifest file. Adding support for this. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- v2v/input_ova.ml | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index 513fe30..5420c85 100644 --- a/v2v/input_ova.ml +++ b/v2v/input_ova.ml @@ -133,7 +133,7

Hi, Intel's Xed can interpret "43 40 04 75" as "add al, 0x75", but LLVM's X86 disassembler considers this invalid code. I guess the reason is that LLVM fails to recognize the REX prefix in this case. Is this correct? Thanks. Jun -------------- next part -------------- An HTML attachment was scrubbed... URL: