search for: metapackag

...n other ways, anything you would prefer? Then we can go ahead splitting hypervisor and userspace... Preferences for the naming? Shall we keep the hypervisor as "xen" and call the rest "xen-userspace"? or "xen-hypervisor" and "xen-userspace" and have xen be a metapackage depending on both, for the sake of compatibility with the past? (So we solve even the "xen-system" metapackage proposed) Unfortunately the name "xen-tools" isn't available, but I think it would have been the best for the userspace (as it's how upstream calls it "ma...

Hi Charles, Ok, I missed the absence from the backports as well. Again, some unfamiliarity here, so 1) I presume I cannot use a metapackage meant for jessie or stretch on wheezy? Or if I can, is there a way to deploy it from console? 2) If not and I use the 2.7.4 tar found at http://networkupstools.org/download.html, do i just run the classical process? i.e. ./configure make sudo make install ./configure has a no under "install...

Hi, I''ve defined this module: package {[''build-essential'', "linux-headers-${kernelrelease}", ''dkms'', ''linux-headers-server'']: ensure => installed, } and when the package linux-headers-server it''s upgraded in the repositories puppet tries to upgrade in client too. And as that package has a dependency

...ying to get everything happy again. System is running "Linux golgotha.tklapp.com 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux" Nut Version: ii nut 2.7.2-4 all network UPS tools - metapackage Installed via apt-get Monitoring: CyberPower 1500PFCLCD UPS Communication: USB, Serial I'm able to start the NUT service on my system and it runs for a couple of hours up to just under 24 hours. I have scrubbed the logs and have not been able to pinpoint the exact issue. I have attac...

...at gmail.com> wrote: > On Aug 1, 2017, at 12:01 PM, Song Teck <songteck at gmail.com> wrote: > > > > Hi Charles, > > > > Ok, I missed the absence from the backports as well. Again, some > unfamiliarity here, so > > > > 1) I presume I cannot use a metapackage meant for jessie or stretch on > wheezy? Or if I can, is there a way to deploy it from console? > > The "nut" metapackage just depends on "nut-client" and "nut-server". The > drivers are in the server package - you'd need to find a way to install a &gt...

A first draft of the wxruby binary release for the macintosh is now available at: http://www.nicreations.net/wxruby-0.2-osx-panther.dmg Install the metapackage (mpkg). You will need to choose a folder for the sample apps. wxruby.bundle is installed in /usr/lib/ruby/1.6/powerpc-darwin7.0 A few questions: 1) Should I just leave the samples in a folder instead of making the user ''install'' them? 2) How much interest is there in a Jagua...

On Aug 1, 2017, at 12:01 PM, Song Teck <songteck at gmail.com> wrote: > > Hi Charles, > > Ok, I missed the absence from the backports as well. Again, some unfamiliarity here, so > > 1) I presume I cannot use a metapackage meant for jessie or stretch on wheezy? Or if I can, is there a way to deploy it from console? The "nut" metapackage just depends on "nut-client" and "nut-server". The drivers are in the server package - you'd need to find a way to install a newer nut-server packa...

...ying to get everything happy again. System is running "Linux golgotha.tklapp.com 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux" Nut Version: ii nut 2.7.2-4 all network UPS tools - metapackage Installed via apt-get Monitoring: CyberPower 1500PFCLCD UPS Communication: USB, Serial I'm able to start the NUT service on my system and it runs for a couple of hours up to just under 24 hours. I have scrubbed the logs and have not been able to pinpoint the exact issue. I have attac...

Hi there, I just saw this morning after mistakenly installing the -amd64 packages on a 32bit machine, that the i386 packages had disappeared from debian from jessie onwards. I was wondering about the reason for this disappearance. Is it because upstream cut off support for 32 bit systems? I scratched really fast on the bug reports and couldn't see one that talked about this. -- Gabriel

Hi Charles, That package is supposed to install both server and client (according to the description at https://packages.debian.org/stretch/nut anyway). I'll try both server and client individually later and see if that helps. Cheers, ST On 3 Aug 2017 7:26 a.m., "Charles Lepple" <clepple at gmail.com> wrote: > On Aug 2, 2017, at 12:09 PM, Song Teck <songteck at

Package: src:xen Severity: important Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 I recently upgrade from Squeeze to Wheezy on a system which had the xen-linux-system-686-pae metapackage (one of two which Provides: xen-linux-system). After dist-upgrade I had the new xen-utils-common and xenstore-utils (and a few others) but not the xen-utils-4.1 or xen-hypervisor-4.1-i386 or xen-hypervisor-amd64 package. (dpkg -l "*xen*" output is below). I have marked this bug importan...

...to test it, but before playing with it, I''d like to ask for the main problems I saw in CFE and try to save some time. 1.-) RPM. In CFE I wanted to use "yum install", "yum group install" and "rpm -Uvh" in same host group (or class), but for different packages/metapackages. I was no able, and I think, for replies I got from list, I will not... So, is puppet able to use many rpm install commands in same host? *Did not find the answer here: http://reductivelabs.com/trac/puppet/wiki/TypeReference#package 2.-) CFE logs are crazy... I need syslog or nagios and parse...

...I'll > try both server and client individually later and see if that helps. > > > Right, but only if you install it via apt. If you install the 2.7.4 .deb > with dpkg, and you have the 2.6.4 nut-client and nut-server .debs > installed, the dependencies are satisfied. (The nut metapackage does not > depend on specific versions.) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170804/665292b6/attachment.html>

...ibxentoollog xen-doc - XEN documentation xen-hypervisor-4.11-amd64 - Xen Hypervisor on AMD64 xen-hypervisor-4.11-arm64 - Xen Hypervisor on ARM64 xen-hypervisor-4.11-armhf - Xen Hypervisor on ARMHF xen-hypervisor-common - Xen Hypervisor - common files xen-system-amd64 - Xen System on AMD64 (metapackage) xen-system-arm64 - Xen System on ARM64 (metapackage) xen-system-armhf - Xen System on ARMHF (metapackage) xen-utils-4.11 - XEN administrative tools xen-utils-common - Xen administrative tools - common files xenstore-utils - Xenstore command line utilities for Xen Changes: xen (4.11.1~pre.20...

...a beginner Linux user and I ?will install your new driver <nutdrv_atcl_usb > to work with networkupstools.org, but I can?t. > > We have a raspberry pi with debian, and I only installed a ?nut? with version: > > ii nut 2.6.4-2.3+de all network UPS tools - metapackage > ii nut-client 2.6.4-2.3+de armhf network UPS tools - clients > ii nut-server 2.6.4-2.3+de armhf network UPS tools - core system > > ? But it not contain your NUTDRV_ATCL_USB to put in my ups.conf file configuration > > Could you help me how we can us...

...ying to get everything happy again. System is running "Linux golgotha.tklapp.com 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux" Nut Version: ii nut 2.7.2-4 all network UPS tools - metapackage Installed via apt-get Monitoring: CyberPower 1500PFCLCD UPS Communication: USB, Serial I'm able to start the NUT service on my system and it runs for a couple of hours up to just under 24 hours. I have scrubbed the logs and have not been able to pinpoint the exact issue. I have attac...

...ying to get everything happy again. System is running "Linux golgotha.tklapp.com 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux" Nut Version: ii nut 2.7.2-4 all network UPS tools - metapackage Installed via apt-get Monitoring: CyberPower 1500PFCLCD UPS Communication: USB, Serial I'm able to start the NUT service on my system and it runs for a couple of hours up to just under 24 hours. I have scrubbed the logs and have not been able to pinpoint the exact issue. I have attac...

...org/stretch/nut anyway). I'll try both server and client individually later and see if that helps. > Right, but only if you install it via apt. If you install the 2.7.4 .deb with dpkg, and you have the 2.6.4 nut-client and nut-server .debs installed, the dependencies are satisfied. (The nut metapackage does not depend on specific versions.)

...ry both server and client individually later and see if that helps. >> > >> Right, but only if you install it via apt. If you install the 2.7.4 .deb >> with dpkg, and you have the 2.6.4 nut-client and nut-server .debs >> installed, the dependencies are satisfied. (The nut metapackage does not >> depend on specific versions.) > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170815/62ba447b/attachment.html>

...eared from debian > from jessie onwards. There is no i386 hypervisor upstream any more (since Xen 4.3) and hence no more xen-hypervisor-*-i386 packages in Debian Jessie onwards. However the i386 tools still exist (e.g. [0]) and can be used with the xen-hypervisor-*-amd64 package[1] (or via the metapackage[2]) with an i386 kernel+userspace in a "32on64" configuration. Ian. [0]?https://packages.debian.org/jessie/i386/xen-utils-4.4/download [1]?https://packages.debian.org/jessie/i386/xen-hypervisor-4.4-amd64/download [2]?https://packages.debian.org/jessie/i386/xen-system-amd64/download