similar to: 'username = @group' not working correctly

[Was initially posted on cfe-users, sorry.] Hi, I'm sorry my message is quite long, the TL;DR version is "g++ and clang++ seem to have different opinions on how RTTI, templates, and ELF visibility should interact". I can't tell whether this is a bug or not: I have found no relevant documentation that could help me decide whether this behavior is meant, or not. All I can say

In the mandriva rpm of rsync, we apply for our rpm the acl patch in the patches directory. I am trying to update our rpm to rsync 2.6.6 but one of the test failed with this patch. It seems to be a minor problem, but can you have a look ? Thanks by advance. Following the message (a bit long): ----- itemize log follows Testing for symlinks using 'test -h' +

---------- Forwarded message ---------- From: noreply at rubyforge.org <noreply at rubyforge.org> Date: 11-Apr-2007 15:31 Subject: [ mocha-Bugs-8687 ] Block''s return value is dropped on stubbed yielding methods. To: noreply at rubyforge.org Bugs item #8687, was opened at 2007-02-15 17:29 You can respond by visiting:

https://bugzilla.samba.org/show_bug.cgi?id=5297 Summary: merge test fails Product: rsync Version: 3.0.0 Platform: Other OS/Version: SunOS Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: bfriesen@simple.dallas.tx.us QAContact:

HI, rsync-3.0.2 with patches/acls.diff,patches/xattrs.diff,patches/slp.diff fails (most of the time) in the itemize test: ----- itemize log follows Testing for symlinks using 'test -h' makepath /usr/src/packages/BUILD/rsync-3.0.2/testtmp/itemize/from/foo makepath /usr/src/packages/BUILD/rsync-3.0.2/testtmp/itemize/from/bar/baz cd+++++++++ ./ cd+++++++++ bar/

I'm using rsync-2.5.7-2 on an updated Fedora Core 1 athlon system. The -vn option lists all files to be copied or deleted, including symlinks, but it does not appear to list empty directories to be copied, even tough it copies them. It does list empty directories to be deleted. The -v option does list and copy empty directories. -v should behave the same in both instances, and the desired

Hi, There appears to be a bug in 2.5.1p2 that is not present on 2.3.0p1. The environment in question is Solaris, on either Intel or Sparc. The arrangement is as follows: System bar forwards a port from itself to system baz by doing su portfw -c 'ssh -2 -P -N -f -g -L 3333:baz:22 baz' System foo, which can talk to bar but not baz, initiates an ssh connection to bar port 3333, and is

Hi, I have a situation where I want to delete some of my excluded patterns but still want to preserve some other. For example consider below source and destination directory hierarchy. Source Dest ---------- --------- /foo/bar/ /foo/bar/ | -> baz | -> baz | -> xyz | -> xyz | ->

Hi all, I expect I'm getting something wrong, but cat("foo bar baz foo bar baz foo bar baz", fill = 10) should be broken into lines of width 10, whereas I get: > cat("foo bar baz foo bar baz foo bar baz", fill = 10) foo bar baz foo bar baz foo bar baz This is on R 3.4.3, but I don't see mentions of it fixed in 3.4.4 or r-devel NEWS. Cheers, David

Erik Hetzner has submitted a bug with a suggested patch... > Best explained with an example: > > test: > > foo = mock() > bar = mock().stubs(:get_baz).returns(:baz) > foo.stubs(:with_something).yields(bar) > > real code: > > baz = foo.with_something do |bar| > bar.get_baz.to_s > end > > baz should now be "baz", but is nil because we have

On Sun, Jan 08, 2017 at 11:13:42PM +0000, Richard W.M. Jones wrote: > let other_func ~foo ~bar ?baz = > func ~foo ~bar ?baz Actually there is a third issue which is what makes this even more confusing. ?baz (when calling a function) expects that baz (the binding) is an option, and passes either nothing (if baz = None) or the optional argument (if baz <> None). In effect it

How can I do this?: foo { name: $bar => "frob" } define foo( $bar = false, $baz = false ) { if #$bar and $baz both defined $cmd = "frobnicate --bar=$bar --baz=$baz ${name}" else if #$bar defined $cmd = "frobnicate --bar=$bar ${name}" else if #$baz defined $cmd = "frobnicate --baz=$baz ${name}" else

Duncan Sands wrote: > Hi, > >> If yes then this doesnt look all that bad or invasive at first sight (if >> the put_user() workaround can be expressed in a cleaner way), but in any >> case it would be nice to hear an LLVM person's opinion about roughly when >> this is going to be solved in LLVM itself. > > one thing that seems to be clear to everyone

Hi, I read below lines in rsync v3.0.5 for --relative option. if you used this command: rsync -av /foo/bar/baz.c remote:/tmp/ ... this would create a file named baz.c in /tmp/ on the remote machine. If instead you used rsync -avR /foo/bar/baz.c remote:/tmp/ then a file named /tmp/foo/bar/baz.c would be created on the remote machine, preserving its full path It is also possible to limit the

On Jun 18, 2012, at 1:22 PM, Nick Kledzik wrote: >>> But this interface has become awkward to use. There are two "return" values. This method is a unique_ptr "source" but the use of a by-refernce parameter means you have to start with an uninitialized unique_ptr and the readFile() has to std::move() into it. unique_ptr is much nicer to use as a return value.

Hi, There seems to be a straightforward bug in src/lib-storage/list/mailbox-list-fs.c:79. set->index_dir is unchecked prior to dereferencing (unlike on line 126 in the same file, where it is properly checked). This manifested on a FreeBSD server running dovecot 2.3.6 when clients tried to retrieve mail with subscriptions like `~/bar/baz`. This caused the `imap` child to crash, e.g.

Dear R core developers, One feature from Python that I have been wanting in R is the ability to capture groups in regular expressions using names. Consider the following example in R. > notables <- c(" Ben Franklin and Jefferson Davis","\tMillard Fillmore") > name.rex <- "(?<first>[A-Z][a-z]+) (?<last>[A-Z][a-z]+)" > (parsed <-

Hi, I know S manuals used to warn against using the same names for a variable and a function, but I have never seen that cause problems in R, so I usually don't pay much attention to it. Which is why the following behaviour came as a surprise: > bar <- function() 1 > foo <- function(bar = bar()) { + bar + } > foo(9) [1] 9 > foo() Error in foo() : recursive default

If I have the following route defined: map.connect ''/foo/bar/:baz'', :requirements => {:baz => /^\d+$/} then if someone asks for /foo/bar/3 I noticed that :baz == "3" instead of :baz == 3. I.E. it is a string not a number. (At least it does this in the functional testing of the routing). This seems reasonable because I have not told it to expect a number but

Note that I turned up to -d5 but the relevant output didn't seem to change. I just cleaned up my obfuscation for clarity (all referenced DNs were identical): DRS replication add DN of aca72580-587e-4dab-adee-07a5f8027dfa is CN=foo,OU=bar,DC=baz Failed to apply records: Failed to locally apply remote add of CN=foo,OU=bar,DC=baz: ../lib/ldb/ldb_tdb/ldb_index.c:2012: Failed to re-index