search for: removing

Seeing a build problem after updating my git tree: $ git remote -v origin git://git.samba.org/samba.git (fetch) origin git://git.samba.org/samba.git (push) $ git pull $ ./configure ... $ make clean WAF_MAKE=1 python ./buildtools/bin/waf build ./buildtools/wafsamba/samba_utils.py:397: DeprecationWarning: the md5 module is deprecated; use hashlib instead

HI Philippos, Try this: dat1<- read.csv("Validation_data_set3.csv",sep=",",stringsAsFactors=FALSE) #converted to csv str(dat1) #'data.frame':??? 12573 obs. of? 17 variables: # $ Removed.AGC????????????????????????????? : num? 65.67 46.17 41.26 14.09 5.38 ... # $ Removed.SST????????????????????????????? : chr? "" "46.1658" "41.2566"

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...

...15 +++++++++++++++ 11 files changed, 35 insertions(+), 1 deletion(-) New commits: diff-tree f21416fa0be5658c7e88bc2e57d77eacd369ff85 (from 3bd9ef83c764e80467cb95163ad7f7a779100d45) Author: Benjamin Otte <otte at gnome.org> Date: Wed Aug 22 08:50:12 2007 +0200 add test for depth when removing diff --git a/test/trace/Makefile.am b/test/trace/Makefile.am index 6d0d774..aec7f1d 100644 --- a/test/trace/Makefile.am +++ b/test/trace/Makefile.am @@ -859,6 +859,15 @@ EXTRA_DIST = \ relational-6.swf.trace \ relational-7.swf \ relational-7.swf.trace \ + remove-depths.as \ + remove-depths-5...

libswfdec/swfdec_codec_video.c | 2 libswfdec/swfdec_movie.c | 3 test/trace/Makefile.am | 193 ++++++++++++ test/trace/place-object-5.swf |binary test/trace/place-object-5.swf.trace | 4 test/trace/place-object-6.swf

...WFDEC_DEBUG", "2", FALSE); commit 6c5f74ac52e60d861bd7bba83efc4eda2607a17e Author: Benjamin Otte <otte at gnome.org> Date: Tue Nov 27 11:33:25 2007 +0100 make swfdec_movie_queue_script not return TRUE/FALSE instead, check for availability of an unload event when removing a movie diff --git a/libswfdec/swfdec_movie.c b/libswfdec/swfdec_movie.c index d529d01..856443c 100644 --- a/libswfdec/swfdec_movie.c +++ b/libswfdec/swfdec_movie.c @@ -277,7 +277,14 @@ swfdec_movie_do_remove (SwfdecMovie *movie) swfdec_movie_invalidate (movie); swfdec_movie_set_depth (movie...

Johnny Hughes wrote: > > You are trying to remove kernel-utils ...you don't want to do that. > That might cut back the deps a bit. Also, i never remove packages with > yum, but with: > > rpm -e `cat list` > > But, that is just my advise. I didn't think there was any functional difference between: rpm -e package-name and yum remove package-name Isn't

Hi Andres, Postgres uses removable code support and Orcv1. I does make me quite > worried to see a phase where there'll be no viable way of using both in > llvm. Why isn't the right answer here to at lest develop the > replacement as a set of patches / as a branch that then can be merged as > a whole / shortly after each other, rather than just starting to develop > a

Hello, this patch series adapts the platform drivers below drivers/gpu/drm to use the .remove_new() callback. Compared to the traditional .remove() callback .remove_new() returns no value. This is a good thing because the driver core doesn't (and cannot) cope for errors during remove. The only effect of a non-zero return value in .remove() is that the driver core emits a warning. The device

ya trivial series... Joe Perches (44): arch/arm: Remove unnecessary semicolons arch/microblaze: Remove unnecessary semicolons arch/um: Remove unnecessary semicolons drivers/cpufreq: Remove unnecessary semicolons drivers/gpio: Remove unnecessary semicolons drivers/i2c: Remove unnecessary semicolons drivers/isdn: Remove unnecessary semicolons drivers/leds: Remove unnecessary

ya trivial series... Joe Perches (44): arch/arm: Remove unnecessary semicolons arch/microblaze: Remove unnecessary semicolons arch/um: Remove unnecessary semicolons drivers/cpufreq: Remove unnecessary semicolons drivers/gpio: Remove unnecessary semicolons drivers/i2c: Remove unnecessary semicolons drivers/isdn: Remove unnecessary semicolons drivers/leds: Remove unnecessary

ya trivial series... Joe Perches (44): arch/arm: Remove unnecessary semicolons arch/microblaze: Remove unnecessary semicolons arch/um: Remove unnecessary semicolons drivers/cpufreq: Remove unnecessary semicolons drivers/gpio: Remove unnecessary semicolons drivers/i2c: Remove unnecessary semicolons drivers/isdn: Remove unnecessary semicolons drivers/leds: Remove unnecessary

ya trivial series... Joe Perches (44): arch/arm: Remove unnecessary semicolons arch/microblaze: Remove unnecessary semicolons arch/um: Remove unnecessary semicolons drivers/cpufreq: Remove unnecessary semicolons drivers/gpio: Remove unnecessary semicolons drivers/i2c: Remove unnecessary semicolons drivers/isdn: Remove unnecessary semicolons drivers/leds: Remove unnecessary

Hi All, The time has finally come to remove OrcV1. I expect to remove it some time after the 14th of September. This will remove all the legacy layers, legacy utilities, the old Orc C bindings, and OrcMCJITReplacement. ExecutionEngine and MCJIT will *not* be affected by this. I had hoped to have removable code enabled before deleting OrcV1, but it turns out that implementing removable code in

...e than that -- I'm hoping it ends up being a nice compromise. If you ignore tracking in your API it is effectively JITDylib-at-a-time (through the default tracker), but if you do want to do fine grained removal you can, you just assume responsibility for properly handling dependencies (i.e. not removing anything that the JIT program might still be using). I'll be re-hashing this in more detail in this week's ORC Weekly update, hopefully with examples and cleaner code. Regards, Lang. On Mon, Sep 7, 2020 at 9:26 PM Lang Hames <lhames at gmail.com> wrote: > Hi Andres, > > T...

There was a patch merged in on 9/29 that changed remove() calls to unlink(): - (djm) Merged big SCO portability patch from Tim Rice <tim at multitalents.net> Does SCO's libc not include remove()? Note that sftp-server.c is currently using remove. The reason I ask is I'd like to keep the portable tree as close to openbsd as possible, and if we need remove() for SCO we should

Hello, I have a data frame with one column: > remove V1 1 ABAFT_g_4RWG569_BI_SNP_A10_35096 2 ABAFT_g_4RWG569_BI_SNP_B12_35130 3 ABAFT_g_4RWG569_BI_SNP_E09_35088 4 ABAFT_g_4RWG569_BI_SNP_E12_35136 5 ABAFT_g_4RWG569_BI_SNP_F11_35122 6 ABAFT_g_4RWG569_BI_SNP_F12_35138 7 ABAFT_g_4RWG569_BI_SNP_G07_35060 8 ABAFT_g_4RWG569_BI_SNP_G12_35140 I want to remove these 8

I'm seeing a bunch of failures on AArch64 after updating this morning. These are NOT failing on x86-64. These all seem to be caused by segfaults (example backtrace below). Is anyone else seeing this? -David LLVM :: DebugInfo/symbolize-no-debug-str.test LLVM :: tools/gold/X86/comdat.ll LLVM :: tools/gold/X86/visibility.ll LLVM ::

...python2.7 libroken18-heimdal libtalloc2 libtdb1 libtevent0 libwbclient0 libwind0-heimdal python-crypto python-dnspython samba-common samba-common-bin Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ? cleanup : ? apt-get autoremove ? Removing libaio1:amd64 (0.3.110-1) ... Removing samba-common-bin (99:4.2.3-7) ... Removing libkdc2-heimdal:amd64 (1.6~rc2+dfsg-9) ... Removing libgssapi3-heimdal:amd64 (1.6~rc2+dfsg-9) ... Removing libheimntlm0-heimdal:amd64 (1.6~rc2+dfsg-9) ... Removing libhdb9-heimdal:amd64 (1.6~rc2+dfsg-9) ... Removing l...