search for: nvr

Hi, I'm trying to disconnect some iSCSI targets, but can't seem to. [root at localhost ~]# iscsiadm -m session tcp: [1] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:500gb tcp: [3] 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba tcp: [4] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:extent0 tcp: [5] 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.iscsi0.vg0.500gb I need to disconnect all 4 of these [root at localhost ~]# isc...

...ACHE_DIR)/ovirt +OVIRT_NODE_RECIPE ?= ../recipe/ovirt-node-recipe.ks +SUM ?= sha1sum +PKG_FMT = iso +SRC_FMT ?= tar +AUTH_KEYS ?= ~/.ssh/authorized_keys +PACKAGE = ovirt-node-image + +ARCH = $(shell rpm --eval '%{_arch}') + +NVR = $(PACKAGE)-$(VERSION)-$(ARCH) + +# For Release: 0..., set _ovirt_dev=1 so that we get extra_release.GIT- +# annotated rpm version strings. +_ovirt_dev = \ + $(shell grep -q '^[[:space:]]*Release:[[:space:]]*0' \ + $(srcdir)/*.spec.in && echo 1 || :) + +git_head...

On Jan 21, 2015, at 3:41 AM, Maurizio Iacaruso <maurizio.iacaruso at gmail.com> wrote: > The ?device? is this http://www.dlink.com/it/it/business-solutions/network-storage/network-video-recorders/dnr-322l-cloud-network-video-recorder , a NVR with USB port for monitoring UPS. It doesn?t support monitoring by LAN. > So, my aim is to ?replicate? the state of the UPS, in the sense that the information are sent to raspberry (for NUT) AND to NVR, so it may shutdown properly. It is not a simple matter to replicate the UPS state, in that s...

This supercedes the previous patch by incorporating feedback from pmyers and apevec. The ISO building target is in the recipes Makefile rather than a separate one.

Dear all, Through the following code, I wanted to perform correlation test repetedly (through loop) on different combinations of variables of a data set. Code: x=read.table("sample.txt",header=T,sep="\t") out="corout.txt" sink(out) nm = names(x) print(nm) nvr=3 # nvr=Total no. of variables in the input data file for (i in 1:(nvr-1)) { for(j in (i+1):nvr) { frm= as.formula(paste(nm[i+1],",",nm[j+1],sep="")) ($$) crl=cor.test(frm,alternative="two.sided",method="pearson") smr=summary(crl) print(smr) } }...

This one incorporates feedback from mburns to default certain values.

So, the hardware way seems too difficult. I see the raspberry documentation in order to understand if it?s possible ?replicate? an USB signal to GPIO. So, with a TTL-USB cable I send the signal to the NVR. I hope this is possible! Da: Charles Lepple [mailto:clepple at gmail.com] Inviato: mercoled? 21 gennaio 2015 13:41 A: Maurizio Iacaruso Cc: NUT List Oggetto: Re: [Nut-upsuser] R: NUT and relay on USB On Jan 21, 2015, at 3:41 AM, Maurizio Iacaruso <maurizio.iacaruso at gmail.com...

Setup that I was on mind is a little different, but I think your setup works well. In my setup the HUB is connected directly to the UPS, then the cables go to raspberry and device. In your setup the HUB is connected directly to the raspberry, then the cables go to UPS and Device. It?s Ok? In both configurations I need the same things: Male B->female A adaptor, HUB and 2 male A->

....fc30.x86_64 package 2:qemu-3.1.0-4.fc30.x86_64 is not installed (In fact latest RPM does let you use name-epoch:version.release, but that was not true in RHEL 6 or 7). The solution here is to remove the epoch entirely. It's rather unlikely that two kernels will be installed with identical NVR and different Epoch. Just using NVR is sufficient to fix the original bug RHBZ#1161250. Thanks: Germano Veit Michel for bug reporting and analysis. --- v2v/linux.ml | 20 +------------------- 1 file changed, 1 insertion(+), 19 deletions(-) diff --git a/v2v/linux.ml b/v2v/linux.ml index 43449157...

The following two patches fixes / reimplements the oVirt appliance project, installing the entire oVirt stack including all server and node components on one machine. These patches are intended to be checked out and used to build the appliance rpm, after which it is installed provides the /usr/sbin/ovirt-appliance-ctrl script to install/uninstall the appliance. The first patch merely removes

...programme and that I have made use of a sample data (viz., exp.txt): ? Programme: ? # Linear regression modelling with sample data (try5.txt) # Repeated estimation through loop statement x=read.table("try5.txt",header=T,sep="\t") nm=names(x) out="slrout.txt" sink(out) nvr=10;nv1=4;nv2=nvr-nv1 for(i in 1:nv1){ dep=nm[i+1]?????? # The 1st dependent variable is C1 (at column no. 2) for(j in 1:nv2){ ind=nm[j+nv1+1]?? # The first independent variable is C5 (at column no. 6) # Estimation of simple linear regression equation slr=lm(dep ~ ind,data=x) smr=summary(slr) pri...

...ssue is that the bootstrap scheme does not requires to bump the release because with the suffix (~) is considered lower while changing from "%bcond_with check" to "%bcond_without check" requires to bump the release. The issue is that koji does not allow 2 builds with the same nvr. Since we should ensure the upgrade path that also requires to bump the release number in rawhide before applying it on f32 (in this particular case). -- Jos? Ab?lio

...9;t start due to undefined symbols: /usr/sbin/nmbd: symbol lookup error: /usr/sbin/nmbd: undefined symbol: _talloc_realloc_array. ldd -r shows a bunch of similar undefined symbols (shown further below). my samba rpm is samba-3.5.7-1.17.1.x86_64. My package versions: > rpm -qa --qf "%-40{NVR}\t%{DISTRIBUTION}\n" |sort|grp 'sa?mb|cif|alloc|wbcl' cifs-utils-4.6-3.6.1 openSUSE 11.4 fusesmb-0.8.7-110.1 openSUSE 11.4 ldapsmb-1.34b-298.17.1 openSUSE 11.4 libsmbclient0-32bit-3.5.7-1.17.1...

...d python3-libguestfs as a new package in EPEL 7. It's possible to package only the Python bindings as an RPM although I don't know anyone who has actually done it so far. Note also there is a python3-libguestfs package shipped in RHEL 8+ so we'd have to be careful not to ship a higher NVR number than that package. Currently it's python3-libguestfs-1.40.2-20.module+el8.2.0+5433+9e1420c8 > If you are not interested in EPEL or don't feel like you have the > time to put your packages into EPEL, the EPEL project would like to > request that a co-maintainer who is a par...

Just saw this: ================================================================================ Package Arch Version Repository Size ================================================================================ Updating: ansible noarch 2.9.1-2.el7 ovirt-4.3-centos-ovirt43 17 M which seems new. No longer pulling ansible from

...bootstrap scheme does not requires to bump the > release because with the suffix (~) is considered lower while changing from > "%bcond_with check" to "%bcond_without check" requires to bump the release. > > The issue is that koji does not allow 2 builds with the same nvr. > > Since we should ensure the upgrade path that also requires to bump the release > number in rawhide before applying it on f32 (in this particular case). Then probably sticking to bootstrap is the best option. We should propose a change of the template SPEC in the guidelines to reflect...

...m +++ b/Makefile.am @@ -29,6 +29,9 @@ CUR_RAWHIDE = 12 FEDORA = $(shell rpm --eval '%{fedora}') ARCH = $(shell rpm --eval '%{_arch}') +CUR_PREVIEW = 11 +PREVIEW_URL ?= http://markmc.fedorapeople.org/virt-preview/f$(CUR_PREVIEW)/$(ARCH) + NVR = $(PACKAGE)-$(VERSION)-$(ARCH) EXTRA_DIST = \ @@ -76,11 +79,14 @@ repos.ks: FEDORA_REPO=f$(FEDORA) ;\ FEDORA_REPO_LOC="$(if $(FEDORA_URL),--baseurl=$(FEDORA_URL)/releases/$(FEDORA)/Everything/${ARCH}/os,--mirrorlist=$(FEDORA_MIRROR)?repo=fedora-$(FEDORA...

Good morning, I read on ovirt.org to send information about installation procedure issues to this mailing list. I followed ovirt building instructions but "make build" reports the following error on fedora 11: Error creating Live CD : Unable to download from repo : Cannot retrieve repository metadata (repomd.xml) for repository: f11. Please verify its path and try again Could not

...he package.rb, something like: *newparam(:ignoredeps)* Then on the rpm.rb a flag to add "--nodeps" was added. * flags = []* * if @resource[:ignoredeps]* * flags << "--nodeps"* * end* * flags << "-e"* * rpm flags, nvr* All this because we needed to remove some packages without its dependencies. We distributed it with the pluginsync enabled in our puppet.conf, and works as expected. What I don''t like at all is that we have to export all the providers that make use of the package.rb type, all this just...

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Removed ks files, now in ovirt-node-recipe, which is subpackage of ovirt-node. Removed tools, these are now in ovirt-node-recipe which is subpackage of ovirt-node.