A problem remains: Was having considerable difficulty installing NUT.
Same symptoms as above. That is:
u...@host:~$ sudo upsdrvctl start
resulted in:
Can't chdir to /var/run/nut: Permission denied
Driver failed to start (exit status=1)
After considerable difficulty I was convinced that I had
2009/2/18 Steve Beattie sbeat...@ubuntu.com
I reproduced the problem with the original version of nut in the hardy
release, 2.2.1-2.1ubuntu7, and confirmed that upgrading to the version
in hardy-proposed, 2.2.1-2.1ubuntu7.2, corrected this issue. I also
verified that things work properly
This bug was fixed in the package nut - 2.2.1-2.1ubuntu7.2
---
nut (2.2.1-2.1ubuntu7.2) hardy-proposed; urgency=low
* debian/{nut-cgi,nut-hal-drivers,nut}.preinst: don't call adduser or
addgroup *at all*, these operations should be handled in the postinst.
Since this is the
I reproduced the problem with the original version of nut in the hardy
release, 2.2.1-2.1ubuntu7, and confirmed that upgrading to the version
in hardy-proposed, 2.2.1-2.1ubuntu7.2, corrected this issue. I also
verified that things work properly when:
- upgrading via 2.2.1-2.1ubuntu7 (release) -
This bug was fixed in the package nut - 2.2.2-10ubuntu3
---
nut (2.2.2-10ubuntu3) jaunty; urgency=low
* debian/{nut-cgi,nut}.preinst: don't call adduser or addgroup *at
all*, these operations should be handled in the postinst. Since
this is the only custom action at all
** Tags removed: verification-failed
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
Ubuntu-server-bugs mailing list
Steve, that patch looks good to me, thank you! Please also apply it to
jaunty, and send it to Debian.
** Changed in: nut (Ubuntu Hardy)
Status: In Progress = Fix Committed
Target: ubuntu-8.04.3 = None
** Tags added: verification-needed
--
[SRU] upsd doesn't start NOT 221737
** Changed in: nut (Ubuntu Hardy)
Target: None = ubuntu-8.04.3
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
Ubuntu-server-bugs
** Changed in: nut (Ubuntu Hardy)
Target: ubuntu-8.04.2 = ubuntu-8.04.3
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
** Changed in: nut (Ubuntu Hardy)
Assignee: (unassigned) = Steve Langasek (vorlon)
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
I've uploaded a new version of nut to hardy-proposed which fixes several
serious issues with the maintainer scripts, this one chief among them.
Martin, please review and tell me if you think this is adequate.
I'll also check over the package's state in jaunty and prepare an upload
if necessary; I
With no other fixes available at this point, I'm copying nut
2.2.1-2.1ubuntu7.1 to hardy-updates so that users who install the
package fresh from 8.04.1 will have a working setup. This bug is still
verification-failed and I'm not closing it, because we should still be
trying to deliver a working
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 skipping: user \nut\ already exists... see
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
On Fri, Jun 13, 2008 at 06:32:27AM -, Martin Pitt wrote:
Steve, what was the problem when you tested upgrade? Did the upgrade
fail (i. e. did addgroup error out because the group already existed),
or was the problem that an already existing nut user isn't in some
important group?
The
Arnaud Quette [2008-06-13 7:35 -]:
seconded. iirc, this fallback (nut already exist) should result in simply
checking if nut is already part of the dialout group (ie using a test -z
getent group dialout | grep nut) and adding it if it's not.
Please do if groups nut | grep -qw dialout,
I rejected the current upload, since consensus now seems to be that the
current patch is not sufficient (and not necessary either).
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team,
I believe I have addressed these issues in the most recent upload.
Thanks
chuck
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
I reproduced the initial problem using nut-2.2.1-2.1ubuntu7. I verified
that using the package in -proposed, nut-2.2.1-2.1ubuntu7.1, corrects
the issue, but *only* if the -proposed package is a new installation of
the nut package. Upgrading to the nut package in -proposed from the
version released
** Tags added: verification-failed
** Tags removed: verification-needed
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
Ubuntu-server-bugs
For those who were having problems can you enable hardy-proposed in your
/etc/apt/sources.list and try it out?
Thanks
chuck
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Accepted into -proposed, please test and give feedback here
** Changed in: nut (Ubuntu Hardy)
Status: Triaged = Fix Committed
Target: ubuntu-8.04.1 = None
** Tags added: verification-needed
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received
Please test your changes...
$ sudo adduser --quiet --system nut --home /var/lib/nut --no-create-home nut
adduser: Specify only one name in this mode.
I guess you want
adduser --quiet --system --group --home /var/lib/nut --no-create-home
nut
--
[SRU] upsd doesn't start NOT 221737
** Attachment added: Diff
http://launchpadlibrarian.net/14256483/diff
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
Ubuntu-server-bugs
** Attachment added: Fixed diff
http://launchpadlibrarian.net/14225619/diff
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
** Changed in: nut (Ubuntu)
Target: ubuntu-8.04.1 = None
** Changed in: nut (Ubuntu Hardy)
Importance: Undecided = Medium
Status: New = Triaged
Target: None = ubuntu-8.04.1
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this
On Tue, 2008-04-29 at 07:41 +, Martin Pitt wrote:
Chuck, that looks much better already. However, the changelog says nut
group, whereas the patch puts the nut user into dialout. Which one is
right and intended?
This comment suggests that a fix to the problem is adding the user nut
to the
** Changed in: nut (Ubuntu)
Importance: Undecided = Medium
Target: None = ubuntu-8.04.1
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
** Summary changed:
- upsd doesn't start NOT 221737
+ [SRU] upsd doesn't start NOT 221737
--
[SRU] upsd doesn't start NOT 221737
https://bugs.launchpad.net/bugs/222761
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
+# Make sure that the nut group actually exists
+adduser nut nut
First, the comment and command do not match. This will *not* create a
nut group. Second, this is missing a test whether both the user and the
group have a system ID (100 = id 500). Third, this call looks really
weird in the
30 matches
Mail list logo
