hi there,
Morten is fully right, and the fix I've done was a temporary (and bad
bad) fix, waiting for the cdbs/debhelper rewritte.
sadly, I can't be everywhere at the same time, so Morten's
contribution is welcome (thanks Morten).
I'll try to have a look at Morten's patch this evening, though no
Blueprint changed by Arnaud Quette:
Whiteboard changed to:
* Powerman - PDU support (http://powerman.sourceforge.net/):
- Debian ITP (done)
- Debian package upload (underway)
* Network UPS Tools - NUT:
- dummy-ups repeater mode (communication link redundancy and forwarding)
(done, trunk
hi there,
Morten is fully right, and the fix I've done was a temporary (and bad
bad) fix, waiting for the cdbs/debhelper rewritte.
sadly, I can't be everywhere at the same time, so Morten's
contribution is welcome (thanks Morten).
I'll try to have a look at Morten's patch this evening, though no
I've just uploaded nut 2.2.2-9 to Sid, with this fix and some more.
a sync has to be requested...
** Changed in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
Status: New = Fix Released
--
[jaunty] /usr/lib/libupsclient1.so is a dangling link
https
I've just uploaded nut 2.2.2-9 to Sid, with this fix and some more.
a sync has to be requested...
** Changed in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
Status: New = Fix Released
--
[jaunty] /usr/lib/libupsclient1.so is a dangling link
https
2008/11/18 Laurent Dinclaux [EMAIL PROTECTED]:
Had a look to nut web site. Current version is 2.2. So 2.4 seems far away.
Can't the fix be applied to Ubutnu version of nut?
2.2.2 is the current stable.
2.4.0 is the next, scheduled for the end of december.
I'll prepare a PPA with 2.3.0-svnXXX
2008/11/18 Laurent Dinclaux [EMAIL PROTECTED]:
Had a look to nut web site. Current version is 2.2. So 2.4 seems far away.
Can't the fix be applied to Ubutnu version of nut?
2.2.2 is the current stable.
2.4.0 is the next, scheduled for the end of december.
I'll prepare a PPA with 2.3.0-svnXXX
it's not NUT by itself (meaning upsd) but the megatec_usb driver.
so upsd waits for it to be available.
this behavior has been fixed in NUT trunk, and this fix will be
available in NUT 2.4.
the loss/restoration of connexion has also been improved...
Arnaud
--
Linux / Unix Expert RD - MGE Office
it's not NUT by itself (meaning upsd) but the megatec_usb driver.
so upsd waits for it to be available.
this behavior has been fixed in NUT trunk, and this fix will be
available in NUT 2.4.
the loss/restoration of connexion has also been improved...
Arnaud
--
Linux / Unix Expert RD - MGE Office
Hi Adam,
2008/11/6 Adam Niedling [EMAIL PROTECTED]:
What version of Ubuntu are you using? Is this still an issue?
** Changed in: linux-meta (Ubuntu)
Status: New = Incomplete
ooch, this goes back 1,5 year ago. I was running 6.10
I'm running Intrepid now, still with the same KVM, and
with a Dell Latitude D630, I got lot's of buffer underuns as soon as I enable
the external display.
In that case, the dual display (with an external LCD display) doesn't work and
I got an empty desktop.
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics
uh, strange. while I failed all the morning in my attempt to switch to dual
screen (see my above report), it's now working!
And I've obviously not changed anything, nor rebooted nor done anything (except
coding and mailing ;-)
here is the output from Xorg.0.log, just after the successful switch
Hi Alexander and Chuck,
2008/10/29 [EMAIL PROTECTED]:
Arnaud,
On Wed, Oct 29, 2008 at 03:17:45PM +0100, Arnaud Quette wrote:
2008/10/29 [EMAIL PROTECTED]:
Hi Arnaud,
Hi Alexander,
thanks for your sum up.
First of all I want to note that there is no phoenix subdriver in both
2008/10/30 Alexander I. Gordeev [EMAIL PROTECTED]:
Hi Arnaud,
On Thursday 30 October 2008 13:25:20 you wrote:
Hi Alexander and Chuck,
ok, the situation is now clear to me.
So the mentioned patch hasn't been reconducted for 2.2.2!
thanks for having recalled me everything (I'm managing far
Hi Alexander and Chuck,
2008/10/29 [EMAIL PROTECTED]:
Arnaud,
On Wed, Oct 29, 2008 at 03:17:45PM +0100, Arnaud Quette wrote:
2008/10/29 [EMAIL PROTECTED]:
Hi Arnaud,
Hi Alexander,
thanks for your sum up.
First of all I want to note that there is no phoenix subdriver in both
2008/10/30 Alexander I. Gordeev [EMAIL PROTECTED]:
Hi Arnaud,
On Thursday 30 October 2008 13:25:20 you wrote:
Hi Alexander and Chuck,
ok, the situation is now clear to me.
So the mentioned patch hasn't been reconducted for 2.2.2!
thanks for having recalled me everything (I'm managing far
2008/10/29 [EMAIL PROTECTED]:
Hi Arnaud,
Hi Alexander,
thanks for your sum up.
On Mon, Oct 27, 2008 at 04:30:20PM +0100, Arnaud Quette wrote:
2008/10/27 Chuck Short [EMAIL PROTECTED]:
Arnaud,
Any thought about this? Its a regression from 2.2.1.
not yet! @Alex: any idea on your side
2008/10/29 [EMAIL PROTECTED]:
Hi Arnaud,
Hi Alexander,
thanks for your sum up.
On Mon, Oct 27, 2008 at 04:30:20PM +0100, Arnaud Quette wrote:
2008/10/27 Chuck Short [EMAIL PROTECTED]:
Arnaud,
Any thought about this? Its a regression from 2.2.1.
not yet! @Alex: any idea on your side
2008/10/27 Chuck Short [EMAIL PROTECTED]:
Arnaud,
Any thought about this? Its a regression from 2.2.1.
not yet! @Alex: any idea on your side (change of the default driver or
something alike)
this seems to be a timing or reading problem according to the short read msg
Artin, can you also post
2008/10/27 Artin [EMAIL PROTECTED]:
Arnaud
I have already posted the debug output of 2.2.1 :
http://launchpadlibrarian.net/18231851/debug2.txt
uh, right. I was off doing another update for Lenny...
looking a bit at the trunk's changelog, I would guess this is a
regression. not dug much
for
2008/10/27 Chuck Short [EMAIL PROTECTED]:
Arnaud,
Any thought about this? Its a regression from 2.2.1.
not yet! @Alex: any idea on your side (change of the default driver or
something alike)
this seems to be a timing or reading problem according to the short read msg
Artin, can you also post
2008/10/27 Artin [EMAIL PROTECTED]:
Arnaud
I have already posted the debug output of 2.2.1 :
http://launchpadlibrarian.net/18231851/debug2.txt
uh, right. I was off doing another update for Lenny...
looking a bit at the trunk's changelog, I would guess this is a
regression. not dug much
for
Hi there,
2008/8/27 Charles Lepple :
On Aug 26, 2008, at 8:11 PM, Steve Langasek wrote:
...
This is starting to stray from the original issue in this bug
regarding 2.2.1. I don't want to misrepresent the intentions of the
rest of the NUT team - do you mind if I quote this message and some
Hi there,
2008/8/27 Charles Lepple :
On Aug 26, 2008, at 8:11 PM, Steve Langasek wrote:
...
This is starting to stray from the original issue in this bug
regarding 2.2.1. I don't want to misrepresent the intentions of the
rest of the NUT team - do you mind if I quote this message and some
reported through launchpad: https://bugs.launchpad.net/bugs/253999
the possible regression is between nut 2.0.1 (sarge) and 2.2.1
(confirmed Jamie?)
@Arjen: it may be related to some of your changes there...
@Jamie: we'll need some debug output from the drivers (-DDD)
Arnaud
--
nut with
reported through launchpad: https://bugs.launchpad.net/bugs/253999
the possible regression is between nut 2.0.1 (sarge) and 2.2.1
(confirmed Jamie?)
@Arjen: it may be related to some of your changes there...
@Jamie: we'll need some debug output from the drivers (-DDD)
Arnaud
--
nut with
Jamie,
I have a Tripplite OmniSmart 1400 UPS configured with:
[tripplite1]
driver = genericups
upstype = 5
port = /dev/ttyS0
desc = Tripplite UPS
we have not that specific model listed in our compat list.
the only ref I've found is:
Jamie,
I have a Tripplite OmniSmart 1400 UPS configured with:
[tripplite1]
driver = genericups
upstype = 5
port = /dev/ttyS0
desc = Tripplite UPS
we have not that specific model listed in our compat list.
the only ref I've found is:
I've fixed this in 2.2.2-5, and a -6 is even available.
so you should request another sync with Debian.
check this for more info:
http://bugs.debian.org/489831
-- Arnaud
--
nut 2.2.2-3ubuntu1 postinst error on Intrepid alpha3 : /sbin/udevtrigger: not
found
I've fixed this in 2.2.2-5, and a -6 is even available.
so you should request another sync with Debian.
check this for more info:
http://bugs.debian.org/489831
-- Arnaud
--
nut 2.2.2-3ubuntu1 postinst error on Intrepid alpha3 : /sbin/udevtrigger: not
found
I'm uploading 0.5.8 to Debian right now, with fixes for:
- Debian #489198
- Ubuntu #209884 and the present, using tagpy instead of mtag
cheers
--
Missing dependencies for mediadb backend.
https://bugs.launchpad.net/bugs/235910
You received this bug notification because you are a member of
I'm uploading 0.5.8 to Debian right now, with fixes for:
- Debian #489198
- Ubuntu #235910 and the present
cheers
--
coherence library is not the latest version
https://bugs.launchpad.net/bugs/209884
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
2008/7/5 Doug Minderhout
...
An updated package for 2.2.2 would be really nice
2.2.2-3 is in Debian, so you should request a sync.
note that I have a -4 upload scheduled later this week or the next.
--
usbhid-ups not behaving with Tripplite UPS
https://bugs.launchpad.net/bugs/239025
You
2008/7/5 Doug Minderhout
...
An updated package for 2.2.2 would be really nice
2.2.2-3 is in Debian, so you should request a sync.
note that I have a -4 upload scheduled later this week or the next.
--
usbhid-ups not behaving with Tripplite UPS
https://bugs.launchpad.net/bugs/239025
You
2008/6/11 Gavin Hurlbut [EMAIL PROTECTED]:
...
Tue Apr 22 17:58:12 UTC 2008 / Arjen de Korte [EMAIL PROTECTED]
- drivers/usbhid-ups: only check once for input reports in
upsdrv_updateinfo() to prevent lockups if the UPS floods the
driver (some Tripplite units will generate one each
2008/6/11 Gavin Hurlbut [EMAIL PROTECTED]:
...
Tue Apr 22 17:58:12 UTC 2008 / Arjen de Korte [EMAIL PROTECTED]
- drivers/usbhid-ups: only check once for input reports in
upsdrv_updateinfo() to prevent lockups if the UPS floods the
driver (some Tripplite units will generate one each
2008/6/13 Martin Pitt [EMAIL PROTECTED]:
if [ -z `getent group nut` ]; then
addgroup --quiet --system nut
-# else
-# printf error: user \nut\ already exists... see
/usr/share/doc/nut/README.Debian\nexit 1
+ else
+ printf
2008/6/13 Martin Pitt [EMAIL PROTECTED]:
if [ -z `getent group nut` ]; then
addgroup --quiet --system nut
-# else
-# printf error: user \nut\ already exists... see
/usr/share/doc/nut/README.Debian\nexit 1
+ else
+ printf
you have probably missed /etc/default/nut and reading
/usr/share/doc/nut/README.Debian.
but you're right that providing a nut-client package would help slave config...
and that's what I've in mind for long (scheduled for Nut Packaging
Standard and nut 2.4).
--
Missing support for upsmon only
2008/4/30 Al Grimstad [EMAIL PROTECTED]:
Public bug reported:
Binary package hint: nut
This bug concerns the ill-fated nut 2.2.1-2.1ubuntu7 in ubuntu 8.04.
The bug is that upsmon, which I've configured to write its warnings to
tty sessions is frequently reporting spurious low-battery
both!
the aim is to keep nut in the nut group (which is the base for the
framework to operate) and to add it to the dialout group to solve the
need of user action for accessing serial devices.
as I state in the README.Debian, USB devices access is already handled
via udev...
-- Arnaud
--
moot point guys.
NUT can be a network master (same for standalone boxes), requiring
driver+upsd+upsmon, or a net slave requiring only upsmon.
So if there was a component to be started in all cases, that would be upsmon.
but this is void, and it would simply fail if there is no upsd running
and no
2008/4/26, Wayne Steenburg [EMAIL PROTECTED]:
Public bug reported:
...
Can't chdir to /var/run/nut: Permission denied
good catch.
Chuck: this (--ingroup nut) is part of the default debian settings...
has this been changed in Ubuntu (ex: to the benefit of dialout)?
-- Arnaud
--
upsd doesn't
moot point guys.
NUT can be a network master (same for standalone boxes), requiring
driver+upsd+upsmon, or a net slave requiring only upsmon.
So if there was a component to be started in all cases, that would be upsmon.
but this is void, and it would simply fail if there is no upsd running
and no
2008/4/26, Wayne Steenburg [EMAIL PROTECTED]:
Public bug reported:
...
Can't chdir to /var/run/nut: Permission denied
good catch.
Chuck: this (--ingroup nut) is part of the default debian settings...
has this been changed in Ubuntu (ex: to the benefit of dialout)?
-- Arnaud
--
upsd doesn't
You possibly missed the boot time configuration in /etc/default/nut
please validate this and get back to us
--
upsd doesn't start on system startup
https://bugs.launchpad.net/bugs/221737
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut
You possibly missed the boot time configuration in /etc/default/nut
please validate this and get back to us
--
upsd doesn't start on system startup
https://bugs.launchpad.net/bugs/221737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Alessandro, Florian, the UMC Team and u-devel,
I should have stepped up for long to announce this on the UMC mailing list.
I hereby resign of my position of UMC Team leader. Running a community
and such an effort requires more energy and time that I can give to
this specific task. And this
2008/4/10, David Erosa [EMAIL PROTECTED]:
Public bug reported:
Binary package hint: nut
After updating to last nut package (2.2.1-2.1ubuntu6), the megatec_usb
driver seems to be working, except for the charge percentage:
$ /lib/nut/megatec_usb -D -a SAI
...
Checking device
2008/4/10, David Erosa [EMAIL PROTECTED]:
Public bug reported:
Binary package hint: nut
After updating to last nut package (2.2.1-2.1ubuntu6), the megatec_usb
driver seems to be working, except for the charge percentage:
$ /lib/nut/megatec_usb -D -a SAI
...
Checking device
thanks for your testing and feedback Andrew.
@Chuck: it seems that you have not taken the right patch(s).
@Alex: can you please point to Chuck the right ones?
possibly using Charles' Trac (http://boxster.ghz.cc/projects/nut/timeline)
-- Arnaud
--
Nut no longer functions with belkin usb avr
2008/4/10, Launchpad Bug Tracker [EMAIL PROTECTED]:
This bug was fixed in the package nut - 2.2.1-2.1ubuntu6
...
it's your turn Andrew ;-)
-- /me
--
Nut no longer functions with belkin usb avr
https://bugs.launchpad.net/bugs/209001
You received this bug notification because you are a member
thanks for your testing and feedback Andrew.
@Chuck: it seems that you have not taken the right patch(s).
@Alex: can you please point to Chuck the right ones?
possibly using Charles' Trac (http://boxster.ghz.cc/projects/nut/timeline)
-- Arnaud
--
Nut no longer functions with belkin usb avr
2008/4/10, Alexander I. Gordeev [EMAIL PROTECTED]:
On Thu, 10 Apr 2008 15:19:09 +0400, Arnaud Quette [EMAIL PROTECTED] wrote:
thanks for your testing and feedback Andrew.
@Chuck: it seems that you have not taken the right patch(s).
@Alex: can you please point to Chuck the right ones
2008/4/10, Launchpad Bug Tracker [EMAIL PROTECTED]:
This bug was fixed in the package nut - 2.2.1-2.1ubuntu6
...
it's your turn Andrew ;-)
-- /me
--
Nut no longer functions with belkin usb avr
https://bugs.launchpad.net/bugs/209001
You received this bug notification because you are a member
2008/4/8, Andrew:
There is no configure executable file provided with nut. So I tried
autoconf:
...
right, I forgot to add that, but you need to call autoreconf not
simply autoconf (note the re)
the problem you're facing might be due to an oldish autoconf/automake set.
which version are you
2008/4/8, Andrew [EMAIL PROTECTED]:
Please re-open this bug.
I downloaded 2.2.1-2.1ubuntu5 from here:
http://launchpadlibrarian.net/13167950/nut_2.2.1-2.1ubuntu5_amd64.deb
$ Installed it and ran the daemon and the problem is still present.
2.2.0-2build1 is still the latest driver that
Hi Carlos,
2008/4/3, Carlos Rodrigues [EMAIL PROTECTED]:
On Thu, Apr 3, 2008 at 8:11 AM, Arnaud Quette [EMAIL PROTECTED] wrote:
@Carlos, Andrey, Alexander, Jon: can one of you take care of
backporting this to Testing for -pre2?
With all the stuff happening with usbhid-ups
Hi Carlos,
2008/4/3, Carlos Rodrigues [EMAIL PROTECTED]:
On Thu, Apr 3, 2008 at 8:11 AM, Arnaud Quette [EMAIL PROTECTED] wrote:
@Carlos, Andrey, Alexander, Jon: can one of you take care of
backporting this to Testing for -pre2?
With all the stuff happening with usbhid-ups
2008/4/3, Arjen de Korte [EMAIL PROTECTED]:
so there are chances that this has been backported in Testing /
2.2.2-pre1 (released today).
No, it hasn't been backported as far as I can see, so this is something
that needs to be done for nut-2.2.2-pre2. Since we have active maintainers
2008/4/3, Arjen de Korte [EMAIL PROTECTED]:
so there are chances that this has been backported in Testing /
2.2.2-pre1 (released today).
No, it hasn't been backported as far as I can see, so this is something
that needs to be done for nut-2.2.2-pre2. Since we have active maintainers
Carlos,
is this bug a known regression of 2.2.1 vs 2.2.0?
I can't find much in the ChangeLog.
https://bugs.launchpad.net/bugs/209001
thanks,
-- Arnaud
--
Nut no longer functions with belkin usb avr
https://bugs.launchpad.net/bugs/209001
You received this bug notification because you are a
thanks for this update Arjen.
so there are chances that this has been backported in Testing /
2.2.2-pre1 (released today).
Can you (the bug reporters) grab this, call configure as per the
packaging/debian/rules, make and test from the build dir?
-- Arnaud
--
Nut no longer functions with
Carlos,
is this bug a known regression of 2.2.1 vs 2.2.0?
I can't find much in the ChangeLog.
https://bugs.launchpad.net/bugs/209001
thanks,
-- Arnaud
--
Nut no longer functions with belkin usb avr
https://bugs.launchpad.net/bugs/209001
You received this bug notification because you are a
thanks for this update Arjen.
so there are chances that this has been backported in Testing /
2.2.2-pre1 (released today).
Can you (the bug reporters) grab this, call configure as per the
packaging/debian/rules, make and test from the build dir?
-- Arnaud
--
Nut no longer functions with
2008/3/21, Chuck Short [EMAIL PROTECTED]:
There isnt one, this was mismerge that got sponsored, not by me.
there is one !
(2 in fact ; nut.postinst and nut-hal-drivers.postinst), and this is
not due to a mismerge.
these calls are there to refresh udev rules after the nut one installation.
the
Hi Basilio,
thanks for recalling me that I forgot to update this one.
in fact, it has been solved since Feisty...
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Fix Released
--
DNS entries mismatch and loss when switching from network (resolv.conf not
updated)
if somebody needs an MGE (and possibly a Powerware), please let me know.
For the recall, the former is the official NUT sponsor, and the only
UPS manufacturer 100 % pro FLOSS. And the latter might come soon (I'm
working hardly on this).
Arnaud
--
main inclusion report
kudos fellows.
I really like working with you ;-)
expect some new features and a better integration for HH+1...
--
main inclusion report
https://bugs.launchpad.net/bugs/182790
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
that did indeed ;-)
code committed.
the only remaining point is the bug: I'm not sure to understand you.
Should I add a comment on the present bug or? The QA Regression
Testing does not use Launchpad as its bug tracker.
The branch is as located as per your comment:
2008/2/27, Nick Barcet:
I added your branch to this bug. Thanks a lot!
ok, I now see the light, thanks ;-)
-- Arnaud
--
main inclusion report
https://bugs.launchpad.net/bugs/182790
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi Chuck
2008/2/27, Chuck Short
Hi Arnaud,
What is the status of this tool?
postponed to 2.4 (the major feature for this release, along with a
shiny new doc).
I'm currently finishing the Integrated Power Management, which was a big task.
Check:
Fellows,
Following our discussion of last friday with Nick, I've quickly
created a test-nut.py for the QA Regression Testing (master branch).
I've already explained the general idea to Nick, but for the others,
here is a quick brief:
- NUT provides a dummy driver (dummy-ups) that loads its data
2008/2/21, Dustin Kirkland [EMAIL PROTECTED]:
Cool package!
thanks
I've had an APC BackUPS ES with a usb since 2002 but never even hooked
it up, assuming that was for a Windows world only. I'm glad to have
emerged from the darkness. I managed to get it monitoring working well
with
fellows,
2008/2/20, Martin Pitt [EMAIL PROTECTED]:
Thanks, Arnaud for the report improvements, and Jamie for the security
review.
you're welcome ;-)
The packages, as well as the current level of proactive security
seems adequate to me.
Since this package is likely to need some real
well, that will have to wait for NUT 2.4, so HH+1...
--
main inclusion report
https://bugs.launchpad.net/bugs/182790
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
just some comments to ease your audit:
- all the mentioned functions (upslog*, upsdebug*, fatal*) point to
vupslog, and vupslog use only numbered copy functions,
- we centralize as much as possible such kind of functions to manage
the security and reliability of NUT,
- we enforce in general the
2008/2/7, Siegfried Gevatter (RainCT) [EMAIL PROTECTED]:
If Sunday version 2.2.2 isn't yet in Debian, please resubscribe u-u-s so
that we get this into Ubuntu before Feature Freeze. Thanks.
--
[sync request] nut 2.2.1 from debian unstable
https://bugs.launchpad.net/bugs/185565
You received
Hi Jamie,
2008/2/8, Jamie Strandboge [EMAIL PROTECTED]:
Arnaud,
I was curious as to why the Debian packaging doesn't do the 'security
domains' as listed in:
http://www.networkupstools.org/faq/
or even the chrooting as in:
http://www.networkupstools.org/doc/2.2.0/chroot.html
well, the
Public bug reported:
Binary package hint: nut
nut 2.2.1 has been released in Debian.
please sync.
** Affects: nut (Ubuntu)
Importance: Undecided
Status: New
--
[sync request] nut 2.2.1
https://bugs.launchpad.net/bugs/185565
You received this bug notification because you are a
I've uploaded nut 2.2.1-1 yesterday in Debian.
I've logged a sync request too:
https://bugs.edge.launchpad.net/ubuntu/+source/nut/+bug/185565
--
main inclusion report
https://bugs.launchpad.net/bugs/182790
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Public bug reported:
Binary package hint: wmnut
I've uploaded wmnut 0.62-2 in Debian.
It fixes and update several bugs (build failing, many lintian problems, ...)
** Affects: wmnut (Ubuntu)
Importance: Undecided
Status: New
--
[sync request] wmnut 0.62.2
guys,
first; it's a pleasure to see this since I wasn't aware of ;-)
I took the liberty to complete it a bit the report.
some more notes:
- 2.2.1 packages are underway (should be done by the end of this
week). I've been busy with many things upstream... and real life
- the shared libraries
+1 (for the Elisa Media Center and Ubuntu Media Center which use
Coherence)
--
Request for sync in Hardy
https://bugs.launchpad.net/bugs/184766
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
this has been fixed in the 2.2.0 release: nut-usb is now part of the
nut package, and the udev rule is installed as 52_nut-usbups.rules
thanks for your report,
Arnaud
--
Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools (NUT) Project Leader -
thanks guys!
I take this opportunity to mention that there is a blueprint for Hardy
Heron linked to nut 2.2.0:
https://blueprints.edge.launchpad.net/ubuntu/+spec/integrated-usb-ups-support
Arnaud
--
Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools
Hi Sarah,
This is linked to 2 points:
- nut was previously in the dialout group. There was a discussion
years ago on the Debian devel ml about this, and it was decided to
remove it for security reason, and add a mention in the README.Debian
file (check changelog.Debian/0.44.1-3),
- I've planned
Hi Luca,
thanks for this update.
Two side notes:
- I've added a blueprint for HH and the integrated UPS support:
https://blueprints.edge.launchpad.net/ubuntu/+spec/integrated-usb-ups-support
This is really the way forward in terms of desktop integration, and
user experience (the simplest way,
2007/10/15, Andrew [EMAIL PROTECTED]:
Public bug reported:
Binary package hint: nut
I have just switched over from debian testing and cannot get my Belkin
USB UPS working with kubuntu gutsy on amd64.
I was surprised to see that nut is still on 2.0.5 in ubuntu. My UPS
requires the driver
Hi Seb,
thanks for your action. But you also need to import python-coherence, otherwise
elisa won't be working fine.
see https://bugs.launchpad.net/ubuntu/+source/elisa/+bug/128205
As mentioned, I've already updated and uploaded 0.4 into Sid.
thanks.
--
upgrade elisa to 0.3.1
the package nut-usb has to be installed ;-)
nut 2.2.0 packages will fixed that since I've merged nut-usb into nut...
--
bcmxcp_usb powerware 3105 can not connect to UPS.
https://bugs.launchpad.net/bugs/132998
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've uploaded 0.4.0 into Sid...
--
import python-coherence depends from Debian
https://bugs.launchpad.net/bugs/128205
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
0.0.5 has hit Sid, and should hit testing by August 9th.
--
import python-lirc depends from Debian
https://bugs.launchpad.net/bugs/128473
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
coherence 0.2.1 has hit Sid, and is should hit testing by August 6th.
I'll then upload 0.4.0 (only need to remove the python-soappy dependency).
--
import python-coherence depends from Debian
https://bugs.launchpad.net/bugs/128205
You received this bug notification because you are a member of
fully right Stephen,
I've developed the following plans, since I took over the project 2
years ago, to address this problem:
- make nut configless for USB UPS. NUT 2.2.0 has opened the door to
the HAL bridge.
but for those still needing a classic NUT installation (for
redundancy, network UPS
I meant that it's in the NEW queue...
--
import python-lirc depends from Debian
https://bugs.launchpad.net/bugs/128473
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: elisa
python-lirc is needed for remote controls support through LIRC.
The Debian Sid upload is pending:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430642
** Affects: elisa (Ubuntu)
Importance: Undecided
Status: New
--
import
Public bug reported:
Binary package hint: elisa
coherence is needed for Elisa to support uPnP.
it's only available in Debian experimental for the moment (I'm checking with
[EMAIL PROTECTED] why, since I don't remember why it hasn't reached Sid):
thanks a lot Michael.
I just realize that I will have to open one more bug for coherence (UPnP
support, already in Debian), and another for pylirc (remote controls support,
not yet uploaded to Debian)
--
import python-pigment depends from Debian
https://bugs.launchpad.net/bugs/127347
You
Public bug reported:
Binary package hint: elisa
pigment is mandatory to run Elisa:
http://packages.debian.org/unstable/python/python-pigment
currently, elisa is not installable.
** Affects: elisa (Ubuntu)
Importance: Undecided
Status: New
--
import python-pigment depends from
301 - 400 of 431 matches
Mail list logo
