Bug#851015: nut: FTBFS: a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/asciidoc-dblatex.xsl

[Arnaud Quette]

Hi Michael,

No idea on the why and not much time to look at it before the week end.
Iirc, dblatex is listed for the manpages generation.

Feel free to upload a fix if you find one.

Thanks and cheers.
Arno

Le 19 janv. 2017 19:57, "Michael Stapelberg"  a
écrit :

> [+aquette, bigon directly]
>
> Are you aware of this issue? This RC bug transitively marked freeradius
> for removal from testing. If you need help, please let me know — I have
> some incentive to look into it in order to keep freeradius in stretch.
>
> Lucas Nussbaum  writes:
>
> > Source: nut
> > Version: 2.7.4-4
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20170111 qa-ftbfs
> > Justification: FTBFS on amd64
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> >
> > Relevant part (hopefully):
> >> make[3]: Entering directory '/<>/docs'
> >> make[3]: Nothing to be done for 'all-am'.
> >> make[3]: Leaving directory '/<>/docs'
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=chunked_format --format=chunked --xsl-file=./chunked.xsl
> user-manual.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=chunked_format --format=chunked --xsl-file=./chunked.xsl
> developer-guide.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=chunked_format --format=chunked --xsl-file=./chunked.xsl
> packager-guide.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=xhtml11_format --format=xhtml --xsl-file=./xhtml.xsl FAQ.txt
> >> /usr/bin/a2x  --attribute icons --xsltproc-opts "--nonet"
> --xsltproc-opts "--stringparam nut.localdate \"`TZ=UTC date +%Y-%m-%d`\""
> --xsltproc-opts "--stringparam nut.localtime \"`TZ=UTC date +%H:%M:%S`\""
> --xsltproc-opts "--stringparam nut.nutversion \"2.7.4\"" --attribute
> iconsdir=./images --attribute=badges --attribute=external_title --attribute
> tree_version=2.7 -a toc -a numbered --destination-dir=.
> --attribute=pdf_format --format=pdf -a docinfo1 user-manual.txt
> >> a2x: WARNING: --destination-dir option is only applicable to HTML based
> outputs
> >> a2x: ERROR: missing configuration file: /etc/asciidoc/dblatex/
> asciidoc-dblatex.xsl
> >> Makefile:825: recipe for target 'user-manual.pdf' failed
> >> make[2]: *** [user-manual.pdf] Error 1
> >
> > The full build log is available from:
> >http://aws-logs.debian.net/2017/01/11/nut_2.7.4-4_unstable.log
> >
> > A list of current common problems and possible solutions is available at
> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to
> contribute!
> >
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
> >
> >
>
> --
> Best regards,
> Michael
>

Bug#835703: nut: FTBFS: dh_makeshlibs: failing due to earlier errors

[Arnaud Quette]

2016-09-25 12:09 GMT+02:00 Sebastian Harl :

> Hi,
>
> On Sun, Aug 28, 2016 at 12:27:09PM +0200, Lucas Nussbaum wrote:
> > Source: nut
> > Version: 2.7.4-3
> > Severity: serious
>
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
>
> > > dpkg-gensymbols: warning: some new symbols appeared in the symbols
> file: see diff output below
> > > dpkg-gensymbols: warning: some symbols or patterns disappeared in the
> symbols file: see diff output below
> > > dpkg-gensymbols: warning: debian/libnutclient0/DEBIAN/symbols doesn't
> match completely debian/libnutclient0.symbols
> […]
>
> This looks like a rather straight-forward issue, but I'm not into the
> magic of C++ symbol files much ;-) Anyway I can help with this



Hi Sebastian,

please go ahead and NMU if Laurent is also busy.

Thanks for the help,
Arno

Bug#677054: nut-client: prompting due to modified conffiles which were not modified by the user

[Arnaud Quette]

Hi Sebastien

2012/11/23 Sébastien Villemot sebast...@debian.org

 Control: tags -1 + patch

 Laurent Bigonville bi...@debian.org writes:

  The bug (maintainer script modifying conffile) that bring us to this
  situation (prompting the user for a file he has not modified himself)
  is not happening in the version in wheezy and the root cause is fixed
  (bug #684392) in sid.
 
  The user will still be prompted when upgrading from squeeze (that's
  why I didn't close that bug) BUT chances, in a normal situation, that
  the user didn't changed that file by himself is close to zero, as that
  file is controlling which part of the NUT software
  (client/server/standalone) is running.
 
  If somebody want to provide a patch, I would apply it with joy but I'm
  quite busy now and I'm not sure how to do that properly (handling
  upgrade being aborted,...).

 Please find attached a patch that should fix this bug. It implements the
 dirty hack in nut-client.preinst. With this patch applied, upgrades from
 squeeze go without smoothly without prompting.


this should indeed fix the issue, as best as it can, considering the big
mess of this situation.

Could you please also handle the NMU?
Thanks a lot for your patch.

cheers,
Arnaud
-- 
Engineering Linux/Unix Expert - Opensource Solutions Lead - Eaton -
http://opensource.eaton.com
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr

Bug#677054: nut-client: prompting due to modified conffiles which were not modified by the user

[Arnaud Quette]

2012/8/9 Laurent Bigonville bi...@debian.org

 Hi,


Hi Laurent,

It seems that the issue is that the nut-server postinst script in the
 version currently in squeeze is modifying the freshly
 installed /etc/nut/nut.conf (to remove the white spaces around the
 equal sign) which means that md5 doesn't match anymore.


right, this was an upstream issue.


 I'm not too sure how this could be fixed.


the best would be to patch nut.conf to have spaces already removed.
I don't see anything else.

cheers,
Arnaud
-- 
Linux / Unix / Opensource Engineering Expert - Eaton -
http://opensource.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr

Bug#677054: nut-client: prompting due to modified conffiles which were not modified by the user

[Arnaud Quette]

2012/8/9 Laurent Bigonville bi...@debian.org

 Le Thu, 9 Aug 2012 16:54:33 +0200,
 Arnaud Quette aquette@gmail.com a écrit :

  2012/8/9 Laurent Bigonville bi...@debian.org
 
   Hi,
  
 
  Hi Laurent,
 
  It seems that the issue is that the nut-server postinst script in the
   version currently in squeeze is modifying the freshly
   installed /etc/nut/nut.conf (to remove the white spaces around the
   equal sign) which means that md5 doesn't match anymore.
  
 
  right, this was an upstream issue.
 
 
   I'm not too sure how this could be fixed.
  
 
  the best would be to patch nut.conf to have spaces already removed.
  I don't see anything else.

 In the current version in wheezy/sid, this is already done. Should we
 do this also in stable to limit the number of people impacted by this?


that would probably be better. But I'll (once more) leave it up to you, if
we want to have a solution in a timely fashion.

Thanks again Laurent for all your help on packaging...

cheers,
Arnaud
-- 
Linux / Unix / Opensource Engineering Expert - Eaton -
http://opensource.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr

Bug#675203: [CVE-2012-2944] upsd can be remotely crashed

[Arnaud Quette]

Package: nut
Severity: critical
Tags: security patch

The following potential vulnerability had been reported against NUT
(Network UPS Tools):
https://alioth.debian.org/tracker/index.php?func=detailaid=313636group_id=30602atid=411542

The patch has already been committed upstream (development version),
and include more details on the issue:
http://trac.networkupstools.org/projects/nut/changeset/3633

It will be available in 2.6.4, which will be released by the end of the week.
This will fix Sid and Testing.

But Stable is still exposed (NUT 2.4.3). I'm currently preparing an
upload to fix it (2.4.3-1.1squeeze2).

Please use CVE-2012-2944 for this issue.
This CVE is not yet official, but will be on Friday, June Arst 00:00:00 UTC.

cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#642789: nut: FTBFS: a2x: ERROR: xsltproc ... returned non-zero exit status 5

[Arnaud Quette]

Hi Monica,

thanks for your report.

2011/9/24 Mònica Ramírez mon...@probeta.net:
 Source: nut
 Version: 2.6.1-2
 Severity: serious
 Tags: wheezy sid
 User: debian...@lists.debian.org
 Usertags: qa-ftbfs-20110923 qa-ftbfs
 Justification: FTBFS on amd64

 Hi,

 During a rebuild of all packages in sid, your package failed to build on
 amd64.

 Relevant part:
 make[3]: Entering directory `/build/nut-XXqT8h/nut-2.6.1/docs/website'
 make[3]: Nothing to be done for `all'.
 make[3]: Leaving directory `/build/nut-XXqT8h/nut-2.6.1/docs/website'
 /usr/bin/a2x  --attribute icons --attribute localdate=`TZ=UTC date 
 +%Y-%m-%d` --attribute localtime=`TZ=UTC date +%H:%M:%S` --attribute 
 iconsdir=./images --attribute=badges --attribute=external_title -a toc -a 
 numbered --destination-dir=. --attribute=chunked_format --format=chunked 
 user-manual.txt
 a2x: ERROR: xsltproc  --stringparam callout.graphics 0 --stringparam 
 navig.graphics 0 --stringparam admon.textlabel 1 --stringparam 
 admon.graphics 0  --stringparam base.dir user-manual.chunked/ 
 /etc/asciidoc/docbook-xsl/chunked.xsl 
 /build/nut-XXqT8h/nut-2.6.1/docs/user-manual.xml returned non-zero exit 
 status 5
 make[2]: *** [user-manual.chunked] Error 1

 The full build log is available from:
   http://people.debian.org/~lucas/logs/2011/09/23/nut_2.6.1-2_lsid64.buildlog

strange, since doc build has been well tested.
I'm currently working on 2.6.2-1.
on this specific topic (doc building), it has a workaround in case
there is no internet connection, which is the only potential issue.
See http://bugs.debian.org/635347

Can you please try this patch, or confirm on your net availability?
If it's not the case (ie you have a net connection), can you set
ASCIIDOC_VERBOSE=-v and relaunch make from the nut/docs dir (or
similar)?

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#642789: nut: FTBFS: a2x: ERROR: xsltproc ... returned non-zero exit status 5

[Arnaud Quette]

Hi Monica,

2011/9/25 Mònica Ramírez mon...@probeta.net:
 Hi!

 I'm currently working on 2.6.2-1.
 on this specific topic (doc building), it has a workaround in case
 there is no internet connection, which is the only potential issue.
 See http://bugs.debian.org/635347

 As the above note says:

 ---
 About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
 of the Grid'5000 platform, using a clean chroot.  Internet was not
 accessible from the build systems.
 ---

oh, sorry. Seems I've read too quickly.

 There is no Internet acces in this build test. Probably this is the
 issue. Do you want I merge this bug with #635347?

yes, please.

 Thanks for your work!

thanks for using it and reporting bugs ^_^

cheers,
Arnaud



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#624255: collect: FTBFS: nut dependency error

[Arnaud Quette]

Hi Sebastian and Dominic,

I've  just realised that this mail was blocked in my draft stack :-/
so thanks to Laurent once again.

2011/4/27 Sebastian Harl tok...@debian.org

 reassign 624255 libupsclient1-dev 2.6.0-1
 retitle 624255 libupsclient1-dev: broken .pc file
 severity 624255 serious
 thanks

 Hi,

 Dominic, thanks for reporting this!

 On Tue, Apr 26, 2011 at 11:06:39PM +0100, Dominic Hargreaves wrote:
  Package: collectd

  This package fails to build from source in a clean sid chroot:

  [...]
 
  nut . . . . . . . . . no (dependency error)
 
  configure: error: Some plugins are missing dependencies - see the
 summary above for details

 config.log reveals:

  configure:22249: checking for upscli_connect in -lupsclient
  configure:22274: i486-linux-gnu-gcc -o conftest -Wall -g -O2
 -I/build/dom-collectd_4.10.1-2.1-i386-S9gxuK/collectd-4.10.1/debian/include
 -DLT_LAZY_OR_NOW='RTLD_LAZY|RTLD_GLOBAL' -UCONFIGFILE
 -DCONFIGFILE='/etc/collectd/collectd.conf'@LIBSSL_LDFLAGS@ -L/lib
 -lupsclient   conftest.c -lupsclient  -ldl  5
  i486-linux-gnu-gcc: @LIBSSL_LDFLAGS@: No such file or directory

 This is due to a wrong 'Libs' entry in the libupsclient pkg-config (.pc)
 file: Libs: -L${libdir} -lupsclient @LIBSSL_LDFLAGS@

 collectd determines the linker flags using 'pkg-config --libs
 libupsclient' which obviously returns '@LIBSSL_LDFLAGS@ -L/lib
 -lupsclient'.

 I've reassigned the bug to libupsclient1-dev. I suppose that
 LIBSSL_LDFLAGS has to be replaced with LIBSSL_LIBS in
 lib/libupsclient.pc.in (and lib/libupsclient-config.in).


this is indeed a side effect of a recent fix.
I've fixed the above upstream (r2960), but have not yet had time to get back
on packaging...
@Seb: if you have a bit of time for an NMU

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Bug#531220: nut: diff for NMU version 2.4.1-3.2

[Arnaud Quette]

Hi Stefano,

2009/11/26 Stefano Zacchiroli:
 tags 531220 + patch pending
 thanks

 Dear maintainer,

 I've prepared an NMU for nut (versioned as 2.4.1-3.2) and uploaded it to
 DELAYED/2, according to devref §5.11.1. The patch is based on
 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531220#35 , but is a
 bit more permissive about placement of MODE= in nut.conf (still avoid
 acting on MODE reported in the descriptive comment).

 Hope this helps,

thanks a lot, it indeed helps a lot while too busy upstream.
I've just restarted yesterday to process my Debian stack (with
powerman and pwrkap).
so it will take me a bit more time to complete the nut part...

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#531220: nut.conf overwritten during reinstall with not prompting

[Arnaud Quette]

2009/6/28 Manolo Díaz da...@pleione.es

 El Sun, 28 Jun 2009 21:47:28 +0200
 Arnaud Quette aquette@gmail.com escribi�:

  Hi Daniel and Manolo,
 
  nut.conf is listed as a conffile (automagically by dh_installdeb).
  but the issue is probably the MODE reprocessing at postinst which
  fails when it is source'able (ie MODE=... without spaces). this
  result in an empty string (MODE=).
 
  can you confirm that you end up with the same result?
 
  cheers,
  Arnaud

 Hi,

 doing 'dpkg-reconfigure nut' it will change the line 'MODE=standalone'
 to 'MODE=' in the file /etc/nut/nut.conf

 But if I previously change 'MODE=standalone' to 'MODE =standalone' or to
 'MODE = standalone' the space(s) will be removed and nut will start.
 'MODE= standalone' will fail too.

 So yes, I think your guesses are right.


Hi Manolo,

thanks for the confirmation. I'll do the fix and an upload soon (being back
from a month off is a hell!).

cheers
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Bug#531220: nut.conf overwritten during reinstall with not prompting

[Arnaud Quette]

Hi Daniel and Manolo,

nut.conf is listed as a conffile (automagically by dh_installdeb).
but the issue is probably the MODE reprocessing at postinst which fails when
it is source'able (ie MODE=... without spaces). this result in an empty
string (MODE=).

can you confirm that you end up with the same result?

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Bug#530869: Workaround tested

[Arnaud Quette]

Hi Martin,

2009/5/28 Martin Maney ma...@two14.net

 I had a chance to test this on the Lenny machine where the problem was
 first seen.  Replacing one line in the init script allows the machine
 to send the shutdown command to the UPS:

   poweroff)
 flag=`sed -ne 's#^ *POWERDOWNFLAG *\(.*\)$#\1#p' /etc/nut/upsmon.conf`
 wait_delay=`sed -ne 's#^ *POWEROFF_WAIT= *\(.*\)$#\1#p'
 /etc/default/nut`
 if [ -f $flag ] ; then
 -  if /sbin/upsmon -K /dev/null 21 ; then
 +  if true ; then
 log_daemon_msg Shutting down the UPS ...

 Apparently the author doesn't entirely trust upsmon -K or something,
 since the preceeding line has already found the kill file; all upsmon
 adds, according to the man page, is a check of the text in it.
 Harmless when it works...


I just saw your report, thanks for it.

to answer the above, upsmon -K will not only check if the POWERDOWNFLAG file
exists, but also if it contains the right magic (just to be sure that only
touching the files won't allow to poweroff the UPS!)

so, your above patch will obviously work, but will also remove a security
harness.
it's acceptable as a temp solution, but I will do my best to prioritize an
upload for Lenny.

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Bug#520445: speech-tools: tries to overwrite file owned by powerman

[Arnaud Quette]

salut Ralf,

2009/4/3 Ralf Treinen trei...@free.fr

 Hello Kumar, Arnaud,

 On Thu, Apr 02, 2009 at 08:53:21AM -0500, Kumar Appaiah wrote:
  On Thu, Apr 02, 2009 at 03:44:05PM +0200, Arnaud Quette wrote:
  2009/4/2 Kumar Appaiah [1]a.ku...@alumni.iitm.ac.in
I have uploaded speech-tools/1:1.2.96~beta-4 to unstable, which is
supposed to fix this problem. Unfortunately, it looks as though it
will not migrate to testing automatically as it says Updating
speech-tools introduces new bugs: #520445 on the PTS page. Does
powerman also require an upload? Or is there a way to indicate
 that
this issue has been sorted out?
  
Thanks, and sorry for the trouble.
  
  have you marked the bug as being closed by your upload (ie adding a
  Closes: #520445 in debian/changelog). Since the bug is shared by
 the 2
  packages, this should fix the situation.
  cheers,
 
  Seems so:
 
  http://packages.qa.debian.org/s/speech-tools/news/20090328T153211Z.html
 
  In fact, the graph generated in the BTS also shows this aspect, which
  led me to the confusion.

 Normally it should be OK when one of the two packages closes the bug.
 That is the sematics of assigning a bug to two packages. However,
 I am not sure whether that feature of the BTS is used a lot so I
 wouldn't exclude completely that there is a bug. Please observe
 what is going on with the packages, if they continue to be blocked
 from testing migration please talk to the release team.

 Anyway, hanks for fixing taht bug :-) -Ralf.


I've an upload scheduled for i10n and at least 2 bug fixes around april 14.
so for my part, if nut is still blocked, that will trigger a rebuild...

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/

Bug#520445: speech-tools: tries to overwrite file owned by powerman

[Arnaud Quette]

Hi Kumar,

2009/4/2 Kumar Appaiah a.ku...@alumni.iitm.ac.in

 Dear Arnaud and Ralf (Jim kept in CC),

 I have uploaded speech-tools/1:1.2.96~beta-4 to unstable, which is
 supposed to fix this problem. Unfortunately, it looks as though it
 will not migrate to testing automatically as it says Updating
 speech-tools introduces new bugs: #520445 on the PTS page. Does
 powerman also require an upload? Or is there a way to indicate that
 this issue has been sorted out?

 Thanks, and sorry for the trouble.


have you marked the bug as being closed by your upload (ie adding a Closes:
#520445 in debian/changelog). Since the bug is shared by the 2 packages,
this should fix the situation.

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/

Bug#520445: speech-tools: tries to overwrite file owned by powerman

[Arnaud Quette]

Salut Ralph, Jim,

@Jim (Powerman upstream):
speech-tools and powerman both install files with the same name (namely pm
and its manpage).
while the latter has already been reported and somehow fixed [1] (thanks
Kumar BTW ;-), the former [2] wasn't. The full bug reports are linked below.

A quick investigation seems to show that the problem is limited to these 2
files.

The best solution is to solve this upstream, by renaming one or the other.
In PowerMan, pm stands well for Power Man, and is the client tool.
What is exactly pm in speech-tools?

@Jim (partly off-topic):
I personaly feel that 2 letters command names should be kept for the base
system itself (ls, cp, rm, ...)
A possible quick and acceptable (?) solution would be to rename Powerman's
pm to pmc or pmclient or powermanc or whatever suits you and is coherent.
Note that NUT currently use the former with upsc, but the reflexion underway
with the new PDU support is to merge the 3 client tools (upsc, upscmd,
upsrw) into a single nutclient or nut-client or ... you get the idea.
that might be another point in favor of the nut merge ;-)

cheers,
Arnaud
--
[1] http://bugs.debian.org/520001
[2] http://bugs.debian.org/520445
-- 
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/

Bug#520445: speech-tools: tries to overwrite file owned by powerman

[Arnaud Quette]

Hi Kumar,

Jim has a point with the compat, and the fact that power related topics are
*very* sensible.
so thanks for opening the door.

2009/3/19 Kumar Appaiah a.ku...@alumni.iitm.ac.in

 Dear Arnaud,

 On Thu, Mar 19, 2009 at 10:39:44PM +0100, Arnaud Quette wrote:
 The best solution is to solve this upstream, by renaming one or the
 other.
 In PowerMan, pm stands well for Power Man, and is the client tool.
 What is exactly pm in speech-tools?

 It is a non-sophisticated pitchmarking Perl script. Because the
 pitchmark program does this anyway, I don't think there should be a
 problem in renaming pm to something more sensible, though I can't
 think of any such name. Do you have a suggestion?


since I don't use these, and have only a vague idea of the purpose, it's a
bit hard.
moreover knowing that there is already a pitchmark binary with a man
placeholder too!
a few possibilities: simple-pitchmark, perl-pitchmark

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/

Bug#505101: Reopening #505101: fix in 2.2.2-9 broken; libupsclient.la also points to /usr/lib

[Arnaud Quette]

Hi Sebastian,

thanks for poping this up.

Morten Kjeldgaard, from Ubuntu, already pointed it and provided an
excellent package update, using debhelper files:
https://bugs.edge.launchpad.net/ubuntu/+source/nut/+bug/299489

as told, I'll do my best to integrate these update and upload 2.2.2-10.
though my top 1 priority is currently to have 2.4.0 released for Christmas...

thanks for your support and help,
Arnaud
-- 
Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#505101: Ah, missed the previous bug ...

[Arnaud Quette]

Hi Michael,

2008/11/9 Michael Casadevall [EMAIL PROTECTED]:
 retitle libupsclient-dev points to /usr/lib not /lib
 thankyou

 Sorry, I overlooked that the libraries in /lib are intentional. The
 problem is now that the files in -dev point to /usr/lib, vs /lib
 making anything that builds against libupsclient-dev crash and burn.
 Michael

a -9 is ready for some time for fixing this, but I was looking into
adding more into it before uploading it...
I'll wait a bit more since it's not harmful. or do you have an urgent need?
btw, it doesn't affect lenny, but only sid.

thanks for the report,
Arnaud
-- 
Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#502757: nut-cgi: piuparts test fails: chmod: cannot access `/etc/nut': No such file or directory

[Arnaud Quette]

Hi Luk,

checking back, seems I've pissed on my shoes, while playing with
several packages at the same time! all apologies.
should I re upload 2.2.2-6.1 or .2?

thanks,
Arnaud
-- 
Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#502757: nut-cgi: piuparts test fails: chmod: cannot access `/etc/nut': No such file or directory

[Arnaud Quette]

2008/10/27 Luk Claes [EMAIL PROTECTED]:
 Arnaud Quette wrote:
 Hi Luk,

 checking back, seems I've pissed on my shoes, while playing with
 several packages at the same time! all apologies.
 should I re upload 2.2.2-6.1 or .2?

 .2
done,

thanks again Luk, and ... may the force be with you (sorry, I didn't resist ;-)

-- Arnaud



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#502757: nut-cgi: piuparts test fails: chmod: cannot access `/etc/nut': No such file or directory

[Arnaud Quette]

Hi Lucas,

2008/10/19 Lucas Nussbaum [EMAIL PROTECTED]:
 Package: nut-cgi
 Version: 2.2.2-6
 Severity: serious
 User: [EMAIL PROTECTED]
 Usertags: piuparts-20081019 piuparts

 Hi,

 During tests using piuparts of all packages in lenny,
 I ran into the following problem:
...
   Setting up nut-cgi (2.2.2-6) ...
   chmod: cannot access `/etc/nut': No such file or directory
   dpkg: error processing nut-cgi (--configure):
subprocess post-installation script returned error exit status 1
   Setting up perl-doc (5.10.0-15) ...
   Setting up apache2-mpm-itk (2.2.6-02-1+b1) ...
   Errors were encountered while processing:
nut-cgi
   E: Sub-process /usr/bin/dpkg returned an error code (1)

 It is reproducible by installing your package in a clean chroot - cleaned
 up using:
  debfoster -o MaxPriority=required -o UseRecommends=no -f -n apt debfoster

indeed, the directory existence test isn't done in nut-cgi.postinst.
2.2.2-6.1 uploaded.

thanks for your report,
Arnaud



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#490425: wmnut: FTBFS: Unsatisfiable build-dependency: nut-dev(inst ~*=PROVIDED=*= ! = wanted 2.2.1)

[Arnaud Quette]

Bonjour Lucas,

thanks for your report.
An upload is underway to fix this and some more.

-- Arnaud



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#447961: upcoming NMU for nut

[Arnaud Quette]

Hi Sebastian,

2008/1/7, Sebastian Harl [EMAIL PROTECTED]:
 Hi Arnaud,

 On Mon, Jan 07, 2008 at 09:38:10AM +0100, Arnaud Quette wrote:
  I have an update (2.2.1) underway, but devs drained most of my time.
  I can integrate your changes in it if you prefer...

 Whatever you prefer. If you don't think you will make the upload within the
 near future, I'd suggest, I'll NMU the package - I don't suppose it will
 disrupt any of your work done on 2.2.1 so far.

right, I'll need some more time to work on 2.2.1 and other subjects.
so, please be my guest for the NMU.

  Note that, for #447961, I've suppressed udev from Build-deps, keeping
  it only in Depends.

 I don't think udev is required at package build time but removing it from the
 build dependencies should not have any influence on #447961...

right again. In fact, I've previously listed udev so that configure
can autodetect it.
the new way is to remove the build-dep and force configure --with-udev-dir

So both your solution and mine will solve the entire problem: your one
for the packages depending upon nut, and mine for building nut.

 Thanks for your response!

and thanks for your help and interest in nut.
btw, I'm looking for a co-maint on nut; in order to get more time for
upstream things.
Would you be interested in?

Arnaud
-- 
Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#447961: upcoming NMU for nut

[Arnaud Quette]

Hi Sebastian,

thanks for taking care of this.
I have an update (2.2.1) underway, but devs drained most of my time.
I can integrate your changes in it if you prefer...

Note that, for #447961, I've suppressed udev from Build-deps, keeping
it only in Depends.

2008/1/6, Sebastian Harl [EMAIL PROTECTED]:
 tags 445000 + patch
 tags 447961 + patch
 thanks

 Hi,

 As there was no progress for either of these bugs I will do a 0-day NMU. You
 can find the diff for the NMU at [1]. As the changes for both bugs are trivial
 I did not split it up for each bug.

 Cheers,
 Sebastian

 [1] http://debian.tokkee.org/debian.org/NMU-deltas/nut-2.2.0-2.1.diff

Arnaud
-- 
Linux / Unix Expert RD - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#443003: wmnut: FTBFS: wmnut.h:92: error: expected specifier-qualifier-list before 'UPSCONN'

[Arnaud Quette]

tags 443003 upstream
thanks

Salut Lucas,

thanks for your report.
Note that this is due to a problem in NUT 2.2.0, which has been
addressed in the upcoming 2.2.1: http://bugs.debian.org/439986

Unfortunately, the release of this last has been delayed due to USB problems.
Depending on how long it takes us to fix these problems, I'm
considering the release of nut-2.2.0-3 with the needed dpatch.

Arnaud
-- 
Free Software Developer - http://arnaud.quette.free.fr/
Debian Developer - http://people.debian.org/~aquette/
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Ubuntu Media Center (UMC) Project Leader - https://launchpad.net/~umc-team



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#410405: knutclient: FTBFS on 64 bit arches: ambiguous operator

[Arnaud Quette]

Hi Dan,

can you have a look at this bug (failed to build):
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410405

thanks,
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#400215: nut-usbups.rules being overriden by a symlink

[Arnaud Quette]

2006/12/2, Carlos Rodrigues [EMAIL PROTECTED]:

I decided to further investigate this matter, as the nut-usb package
seems to be effectively broken while this remains unfixed.

From looking into the package's diff file
(http://ftp.debian.org/debian/pool/main/n/nut/nut_2.0.4-2.3.diff.gz),
I noticed this two changes:

In nut-2.0.4/debian/rules:

+   install -m 644 $(CURDIR)/scripts/hotplug-ng/nut-usbups.rules \
+   $(CURDIR)/debian/nut-usb/etc/udev/rules.d/025_nut-usbups.rules

And, in nut-2.0.4/debian/nut-usb.postinst:

+  configure)
+if [ -d /etc/udev/rules.d/ ] ; then
+cd /etc/udev/rules.d/
+ln -sf ../nut-usbups.rules 025_nut-usbups.rules
+fi

So, it looks to me like the file 025_nut-usbups.rules is being
installed correctly, but then (in the postinst stage) it is overriden
by a symlink pointing to a nonexistent file.

So, either the file is installed into /etc/udev/nut-usbups.rules to
fix the symlink, or the symlink isn't created at all.

Am I correct?


right, I thought I've mentionned this, but the file would better be
installed as /etc/udev/rules.d/025_nut-usbups.rules, removing the
symlink creation in nut-usb.postinst.

@Steinar: while we're at it, would you be interested in co maintaining
these packages? I would be really glad if you accept ;-)

Thanks to you all,
Arnaud (young dady again, still more than busy)
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#396704: nut: diff for NMU version 2.0.4-2.2

[Arnaud Quette]

[quickly passing by, since I just had my 2nd baby this morning ;-) ... ]

2006/11/16, Steinar H. Gunderson [EMAIL PROTECTED]:

tags 396704 + patch
thanks

Hi,

Attached is the diff for my nut 2.0.4-2.2 NMU.


it's not sufficient (otherwise I would have quickly done it ;-) since
it only addresses udev enabled systems so post 2.6.3 kernels iirc.
for previous release, hotplug rules are still needed. So there should
be some test done ate nut-usb.postint to test which version is needed
and copy files from nut/scripts/hotplug or nut/scripts/hotplug-ng

I hope this is enough to dig this.
thanks for your help,
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#396704: nut: diff for NMU version 2.0.4-2.2

[Arnaud Quette]

2006/11/17, Steve Langasek [EMAIL PROTECTED]:

On Thu, Nov 16, 2006 at 09:59:45PM +0100, Arnaud Quette wrote:
 it's not sufficient (otherwise I would have quickly done it ;-) since
 it only addresses udev enabled systems so post 2.6.3 kernels iirc.
 for previous release, hotplug rules are still needed. So there should
 be some test done ate nut-usb.postint to test which version is needed
 and copy files from nut/scripts/hotplug or nut/scripts/hotplug-ng

Doing this at install time doesn't sound like a good idea to me; you'd end
up with broken packages when the user *does* upgrade to the etch kernel and
installs udev.


one of the last apt weakness ;-)


Would it be enough to drop the '| hotplug' from the dependencies?  I don't
think anyone's really using hotplug today in etch, I'm surprised to see that
it's still in the archive at all.


ok, in this case, the nmu would suit me fine.

Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#396704: nut-usb: newhidups (2.0.4-2.1) does not find UPS device

[Arnaud Quette]

Hi,

2006/11/2, Luis Llana [EMAIL PROTECTED]:

Package: nut-usb
Version: 2.0.4-2.1
Severity: grave


Hello,
  first of all I would like to apologize if you received this more
than once; I sent this bug report a couple of days ago but I can't
see it at
http://bugs.debian.org/nut-usb

I have a mge usb UPS, see later its description. The stable version of
nut-usb (2.0.1-4) runs correctly, but the testing version doesn't.
This is the output of /lib/nut/newhidups - -a :

Checking device (0463/) (002/002)
- VendorID: 0463
- ProductID: 
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 002
Trying to match device
Device matches
failed to claim USB device, trying 2 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
failed to claim USB device, trying 1 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
failed to claim USB device, trying 0 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
Unable to get HID descriptor (error sending control message: Operation not 
permitted)
...


this is clearly a hotplug / udev (permission settings) problem. Until
now, I've used an hybrid system that run in udev some hotplug rules.
But it was based upon udev' hotplug backward compat which seems no
more available now.

A temporary solution is to edit /etc/udev/nut-usbups.rules and replace every
RUN+=/etc/hotplug/usb/libhidups
by
MODE=664, GROUP=nut

For the reference, the upstream equivalent file:
http://svn.debian.org/wsvn/nut/trunk/scripts/hotplug-ng/nut-usbups.rules.in?op=filerev=0sc=0

As I'm more than busy, I've scheduled the fix along with the 2.0.5
release, but if someone wish to NMU, he's welcome...

thanks for the report,
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#389350: NMU for fixing Bug#38935

[Arnaud Quette]

Hi Florian,

2006/10/12, Florian M. Weps [EMAIL PROTECTED]:

tags 389350 + patch
thanks

Hi,

I've uploaded a fix for that bug - the nut user is no longer removed on
purge - I hope I interpreted your intentions correctly.

Hope you don't mind the NMU, it's very important to lower the RC bug
count so Lars can get his tattoo :)


thanks a lot for your action on this point.
your mod should fit perfectly.
I do hope too that Lars will get his tatoo ;-)

Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#389350: nut: purging the package fails (adduser unavailable)

[Arnaud Quette]

Hi Bill and Steve,

2006/9/26, Steve Langasek [EMAIL PROTECTED]:

On Tue, Sep 26, 2006 at 10:54:26AM +0200, Bill Allombert wrote:
  2006/9/25, Bill Allombert [EMAIL PROTECTED]:
  Package: nut
  Version: 2.0.4-2
  Severity: serious

  There is an error when attempting to purge nut:

Removing nut ...
Purging configuration files for nut ...
/var/lib/dpkg/info/nut.postrm: line 5: deluser: command not found
dpkg: error processing nut (--purge):
 subprocess post-removal script returned error exit status 127

  The postrm script cannot rely on adduser to be available when purging.

  See Policy 7.2:
Note, however, that the `postrm' cannot rely on any non-essential
packages to
be present during the `purge' phase.

  I'm not sure about the best action to be taken:
  - check if deluser exist, and try to deluser if possible = that can
  leave junks...
  - other option?

 Would it be possible to remove the user at remove time instead of purge
 time ?

If the user owns files that aren't removed until purge time, that would
leave dangling files that may end up owned by an unrelated service user when
the uid is reused, which would be a bad thing.  (This is also why it's
generally a bad idea to delete system users at all in maintainer scripts,
because you can't always know that there are no files left owned by the
user.)

Since this package creates a /var/lib/nut directory which may be full of
files owned by this user, and does nothing on removal to clean up these


well, there shouldn't be anything left. This is just for socket
communication, and pid files. So I'll also there care of this one.


files, I think it's best to just not delete the user at all.


If there is no objection, we'll go that way.

thanks to you both.
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#389350: nut: purging the package fails (adduser unavailable)

[Arnaud Quette]

2006/9/27, Steve Langasek [EMAIL PROTECTED]:

On Wed, Sep 27, 2006 at 08:47:02AM +0200, Arnaud Quette wrote:
 If the user owns files that aren't removed until purge time, that would
 leave dangling files that may end up owned by an unrelated service user
 when
 the uid is reused, which would be a bad thing.  (This is also why it's
 generally a bad idea to delete system users at all in maintainer scripts,
 because you can't always know that there are no files left owned by the
 user.)

 Since this package creates a /var/lib/nut directory which may be full of
 files owned by this user, and does nothing on removal to clean up these

 well, there shouldn't be anything left. This is just for socket
 communication, and pid files. So I'll also there care of this one.

Hmm, a socket and pid files in /var/lib/nut?  That sounds like an FHS
violation... :)


right. I'm waiting for another nut sub project I've launched (Nut
Packaging Standard) to make a switch to /var/run/nut, possibly
separating the pid files (into /var/run) and the socket files (into
/var/run/nut)


So if these are the only files the user ever owns, deleting the user on
purge would also be ok, as long as you check for deluser's presence first
before calling it.

But leaving the user in place is also certainly allowed.

 files, I think it's best to just not delete the user at all.

 If there is no objection, we'll go that way.

Definitely no objections from me.


thanks for the feedback,
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#389350: nut: purging the package fails (adduser unavailable)

[Arnaud Quette]

Hi Bill,

2006/9/25, Bill Allombert [EMAIL PROTECTED]:

Package: nut
Version: 2.0.4-2
Severity: serious

Hello Arnaud,

There is an error when attempting to purge nut:

  Removing nut ...
  Purging configuration files for nut ...
  /var/lib/dpkg/info/nut.postrm: line 5: deluser: command not found
  dpkg: error processing nut (--purge):
   subprocess post-removal script returned error exit status 127

The postrm script cannot rely on adduser to be available when purging.

See Policy 7.2:
  Note, however, that the `postrm' cannot rely on any non-essential packages to
  be present during the `purge' phase.


I'm not sure about the best action to be taken:
- check if deluser exist, and try to deluser if possible = that can
leave junks...
- other option?

I'm currently partly off, so I'll investigate asap.

thanks for your report.
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#358696: This is dangerous, please make it default to disabled

[Arnaud Quette]

Hi fellows,

2006/7/29, Daniel Richard G. [EMAIL PROTECTED]:

On Fri, 2006 Jul 28 16:12:35 -0300, Henrique de Moraes Holschuh wrote:
...

Anyway, the disagreement comes down to this:

Me: Keep the system minimally running, so that it powers off when the UPS
cuts the power, so that it will turn on again when the power returns, given
the default behavior and limitations of PC hardware. Do sensible steps to
avoid data loss (stop the disks, etc.). Have this be the default, as PC
users are the common case.

You: Do a normal system shutdown. Rely on server-grade features (e.g. WOL
packet from a networked UPS) to resume operation, or an On/Off state: ON
BIOS setting (despite the problems associated with that). Have this be the
default, as the risk of data loss from fragile storage media trumps that of
system unavailability after an extended outage.

Mr. Quette will have to decide this, but I don't think you've made a strong
case for a power-cut being significantly detrimental to data or hardware.
Yes, there are circumstances where this can happen, but these are
exceptions to the rule. And in one well-known case (RAID arrays), the
scripts can easily do something different.

  I think you'll take issue with the NUT documentation, then, as it
  specifically suggests this approach.

 I will.  But maybe, perchance, the NUT docs don't suggest you do it unless
 you own hardware that cannot do it properly?  I didn't read it yet.

I'm getting the impression that hardware that cannot do it properly, as
you mean it, includes most PCs and non-server machines. Your view carries
the day if NUT's userbase is not mostly these.


The point you're talking about is a long standing problem I haven't
yet found a *perfect* solution for.

As you have well stated both, hardware difference, the huge number of
UPSs setup and bios default configuration make it hard (or impossible)
to find The Solution.

Just to avoid misunderstanding: NUT relies by default upon hardware to
be halted, and (BIOS) configured to power on on AC restored.

I'll thus leave the patch, but disable it in -2 (scheduled for release
by tomorrow), referecing the present thread as a WARNING.
When I'll get more time (too busy for the moment with NUT bridging to
HAL, some major code rewrite and internal projects), I'll restart 2
sub project (NPS - NUT Packaging Standard, and QA - Quality Assurance:
https://alioth.debian.org/pm/?group_id=30602) and try to find The
Solution. While the former will focus on NUT integration (ie halt
procedure), the latter will focus on reliability of the UPS poweroff
and such things (like finding upstream workaround for dumb UPSs to
address power races).

Thank you both for your constructive feedback, and don't hesitate to
add more comments.

Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#372498: News about this bug? (ksynaptics: incompatible with xfree86-driver-synaptics 0.14.5-1)

[Arnaud Quette]

Hi Stefan and others,

2006/6/13, Stefan Kombrink [EMAIL PROTECTED]:

...
That is great news to everyone :)


for sure, but I should have made this step for long

Fathi will take over the {k,q}synaptics, and will also create the one
for libsynaptics.  A big thank to him.

I'll orphan the packages tomorrow, and will look after Fathi's
packages at the beginning, though I'll rely on some others for
sponsorship (mark purcell and pierre habouzit).

This will allow me to give more time to my (growing) family, and to my
last debs, which I'm also upstream of.


I think that's a little sad that Dapper didn't ship with ksynaptics 0.3.1 but
I am looking forward to a 0.3.2 release in some weeks.
libsynaptics supports the latest driver release already, and I am receiving
quite some feedback even from FC and Suse developers.
However, it seems that libsynaptics will ship seperately from the synaptics
driver since its maintainer and me have some different opinions on how to do
it.


you might call for some mediation/discussion, with for example the
packagers. This sometimes helps to sort out things.


At the very moment I tend to commit it into the qsynaptics cvs since non-kde
apps are depending on it as well.

Btw: Is there somebody who wishes to help out for a port of QSynaptics to Qt4?


continue your good work Stefan, and send me a mail from time to time.

A last thanks to Modestas for putting me in touch with Fathi, and to
Mattia for his work on the synaptics driver.

see you my friends,
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#372498: News about this bug? (ksynaptics: incompatible with xfree86-driver-synaptics 0.14.5-1)

[Arnaud Quette]

salut Christian,

2006/6/12, Christian Perrier [EMAIL PROTECTED]:


I'm hit quite hard by this bug which makes the handling of the
Synaptics touchpad very jerky in KDE (bad copy/paste, most functions
inactive, etc)

It seems that a solution has been suggested (package libsynaptics and
rebuild ksynaptics against it). Are there any plans to work on this or
any other possible solution?


I'm thinking about orphaning these packages for some time, as I don't
have the time to maintain these anymore, and I also must focus on my
main upstream and according debs (nut and related).

I'm in touch with Mattia Dongili who should contact somebody to check
for adoption. If I don't have news by next week, I'll orphan these.
Finally note that I have excellent relationship with the upstream
developer, Stefan Kombrik...

Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#372498: News about this bug? (ksynaptics: incompatible with xfree86-driver-synaptics 0.14.5-1)

[Arnaud Quette]

salut Fathi,

thanks to Modestas for pointing out your mail.

2006/6/13, Modestas Vainius [EMAIL PROTECTED]:

Hello,

2006 m. birželis 13 d., antradienis 09:49, Arnaud Quette rašė:
 I'm in touch with Mattia Dongili who should contact somebody to check
 for adoption. If I don't have news by next week, I'll orphan these.
 Finally note that I have excellent relationship with the upstream
 developer, Stefan Kombrik...
FYI, Fathi Boudra expressed a will to package[1] ksynaptics a few days ago. So
he might be interested in adopting the package. Thanks for your work.

1. http://lists.debian.org/debian-kde/2006/06/msg00095.html


if you're still interested in, we can check for sponsorship and adoption...
You would also have to take over libsynaptics (ITP) and qsynaptics
(won't evolve now).

Contact me back privately (french ok ;-) for the details...

Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/

Bug#346981: Fwd: WMNut and XBell()

[Arnaud Quette]

Hi Bastian,thanks for your report.I've meanwhile asked the X team for info, and got the solution, thanks to David.I'll validate the solution, correct the upstream source and upload the corrected pkg asap...
-- Forwarded message --From: David Martínez Moreno [EMAIL PROTECTED]Date: 12 janv. 2006 12:31
Subject: Re: WMNut and XBell()To: Arnaud Quette [EMAIL PROTECTED]Cc: debian-x@lists.debian.org
El jueves, 12 de enero de 2006 11:28, Arnaud Quette escribió: Hi there, It seems I've made the transition too quickly, and I was too confident. I'm now facing another FTBTS due to the XBell() function not found.
  checking for XBell in -lX11... no  The XBell extension stuff could not be found in the X client libraries  make: *** [config.status] Error 1 A complete build log is there:
 http://buildd.debian.org/fetch.php?pkg=wmnutver=0.61-2arch=ia64stamp=1136811182file=logas=raw
 Have I missed something? Any hints welcomed. Thanks to cc me back as I'm not subscribed to this list.Hello, Arnaud. I think that you need the headers in libxi-dev:[EMAIL PROTECTED]
:~/debian/svn/xorg-x11/trunk$ grep XBell xc/ -rxc/include/extensions/XInput.h:} XBellFeedbackState;xc/include/extensions/XInput.h:} XBellFeedbackControl;[...]I guess that you have installed in your system but ignored it in the
Build-Depends on your package.Best regards,Arnaud-- Linux / Unix Expert - MGE UPS SYSTEMS - RD DptNetwork UPS Tools (NUT) Project Leader - 
http://www.networkupstools.org/Debian Developer - http://people.debian.org/~aquette/OpenSource Developer - http://arnaud.quette.free.fr/

Bug#327994: The package FTBFS anyway

[arnaud . quette]

salut Christian

  so you've not yet upgraded to kdelibs4c2?

 Well, this didn't seem to be mandatory but I'm pretty ignorant of this
 issue. Remember that I just wanted to have a look at this software ..:-)

  Or have I missed something on the road?
  I've 2 problems to solve: the kde/qt transition, and
  the FTBTS above. For the 2nd, the upstream author
  mailed me back that he will release a new version soon...

 Well, as long as the maintainer obviously takes care of the problem,
 I'm anyway safe...and I know I'll be able to test the thing when this
 bug will be closed.

I finally found a bit of time. The upstream author has done
his part, so I can now do mine.

The package is now in the incoming queue.

See you,
Arnaud Quette
--
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#327994: The package FTBFS anyway

[arnaud . quette]

 ...
  Side note: I'm facing some problems to rebuild my kde/qt
  dependant apps due to the non existing kdelibs4-dev...
  I've not had much time to dig, so any hints welcome.

 Well, I'm afraid I won't have much clues but I'm surprised by your
 mention of a missing kdelibs4-dev. I have it on my system.

 In case you have problems, it seems I could at least compile a NMU if
 the above patch solves the problem

so you've not yet upgraded to kdelibs4c2?
Or have I missed something on the road?
I've 2 problems to solve: the kde/qt transition, and
the FTBTS above. For the 2nd, the upstream author
mailed me back that he will release a new version soon...

thanks
Arnaud




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#327994: The package FTBFS anyway

[arnaud . quette]

salut bubulle ;-)

 Dato suggested rebuilding this package to have it follow the KDE
 transition.

 However, trying to do so (because I wanted to give it a try), I
 failed:

 ...
 uchpad.cpp:(.text+0xcb9): undefined reference to 
 `TouchPad::coastingSpeedThreshold'
 ...
 I have no clue for solving thisso I will just give up..:-)

there is a patch for it:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=301274

sadly, the upstream author lags in answering...
I've just ping him again, and I'll see. If he doesn't answer,
I'll dpatch the beast while waiting...

Side note: I'm facing some problems to rebuild my kde/qt
dependant apps due to the non existing kdelibs4-dev...
I've not had much time to dig, so any hints welcome.

Arnaud
---
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#301274: ksynaptics: #301274 does also apply for i386 sid after transition

[Arnaud Quette]

2005/9/15, Stefan Kombrink [EMAIL PROTECTED]:
On Thursday 15 September 2005 09:06, Arnaud Quette wrote: Hi Stefan, did you received my last mail. It would be really nice if you make this update: --- ksynaptics-0.2.0.orig
/ksynaptics/src/touchpad.cpp +++ ksynaptics-0.2.0/ksynaptics/src/touchpad.cpp @@ -31,6 +31,7 @@ TouchPad *TouchPad::m_self = 0; static KStaticDeleterTouchPad staticTouchPadDeleter;
 +const double TouchPad::coastingSpeedThreshold; static int finger_low[] = { 53, 38, 25, 18, 10 }; see this Debian bug entry for more info: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=301274 see you, ArnaudHi Arnaud,
Hi Stefan,sorry for the delay!
no problem. I hope everything's fine on your side, and that you have good results in class ;-)

Yes, this one is rather old, shall I simply modify the tar balls or should Irelease a 
0.2.1?
yep, release a 2.1 please. There is a change, so you have to make a new
release in order for users/packagers to acknowledge the change (we have
a system in debian that checks automatically for new releases...)
Tell me and I'll put it on my sf page
thanks to ping me back when it's ok
see you,
Arnaud
-- Linux / Unix Expert - MGE UPS SYSTEMS - RD DptNetwork UPS Tools (NUT) Project Leader - http://www.networkupstools.org/Debian Developer - 
http://people.debian.org/~aquette/OpenSource Developer - http://arnaud.quette.free.fr/

Bug#327959: builds with gcc-4.0

[arnaud . quette]

Hi Josh,

 This is just a quick note to let you know that I rebuilt knutclient locally
 in a clean sid pbuilder chroot, and it built fine.  I have not yet upgraded
 my desktop computer to kde 3.4.2, so I haven't yet tested the new package.
 If knutclient hasn't been uploaded for the transition yet when I do
 upgrade, I'll send another e-mail with my testing results.

I'm facing some problems with 3.4.2 and kdelibs4-dev.
don't have much time to devote to this currently, so I'll get
back on it asap.

thanks for your info,
Arnaud




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#301274: ksynaptics: #301274 does also apply for i386 sid after transition

[arnaud . quette]

Hi Stefan,

here is a followup of the previous problem.
it allows me to ping you on that point, and on your previous request
(about depends, which wasn't clear to me).
hope everything's fine on your side.

Arnaud

-- Envoyée par Arnaud QUETTE/FR/MGE-UPS/User/GIN le 
08/09/2005 08:51 ---


Sune Vuorela [EMAIL PROTECTED] le 08/09/2005 07:44:11

Veuillez répondre à Sune Vuorela [EMAIL PROTECTED]; Veuillez répondre à 
[EMAIL PROTECTED]



Pour : Debian Bug Tracking System [EMAIL PROTECTED]
cc :

Objet : Bug#301274: ksynaptics: #301274 does also apply for i386 sid after 
transition


Package: ksynaptics
Version: 0.2.0-1
Followup-For: Bug #301274


The same problem (and solution) does apply to ksynaptics in sid after the
c++-transition.

right now, in sid, ksynaptics is uninstallable and unbuildable.

/Sune



-- System Information:
Debian Release: unstable/experimental
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.2
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages ksynaptics depends on:
ii  kdelibs4c24:3.4.2-3  core libraries for all KDE applica
ii  libart-2.0-2  2.3.17-1   Library of functions for 2D graphi
ii  libaudio2 1.7-3  The Network Audio System (NAS). (s
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libfontconfig12.3.2-1generic font configuration library
ii  libfreetype6  2.1.10-1   FreeType 2 font engine, shared lib
ii  libgcc1   1:4.0.1-6  GCC support library
ii  libice6   6.8.2.dfsg.1-6 Inter-Client Exchange library
ii  libidn11  0.5.18-1   GNU libidn library, implementation
ii  libpng12-01.2.8rel-1 PNG library - runtime
ii  libqt3-mt 3:3.3.4-7  Qt GUI Library (Threaded runtime v
ii  libsm66.8.2.dfsg.1-6 X Window System Session Management
ii  libstdc++64.0.1-6The GNU Standard C++ Library v3
ii  libx11-6  6.8.2.dfsg.1-6 X Window System protocol client li
ii  libxcursor1   1.1.3-1X cursor management library
ii  libxext6  6.8.2.dfsg.1-6 X Window System miscellaneous exte
ii  libxft2   2.1.7-1FreeType-based font drawing librar
ii  libxinerama1  6.8.2.dfsg.1-6 X Window System multi-head display
ii  libxrandr26.8.2.dfsg.1-6 X Window System Resize, Rotate and
ii  libxrender1   1:0.9.0-2  X Rendering Extension client libra
ii  libxt66.8.2.dfsg.1-6 X Toolkit Intrinsics
ii  xlibs 6.8.2.dfsg.1-6 X Window System client libraries m
ii  zlib1g1:1.2.3-4  compression library - runtime

ksynaptics recommends no packages.

-- no debconf information

Bug#323236: nut: reinstalling nut breaks if user cyrus is not there

[arnaud . quette]

 ...
 i set libgd2 to install but then came:

 unknown user cyrus in statusoverride file
 Errorcode 2

 Then dselect ends with error 100.

 I wonder why nut needs a username or am i reading wrong?

 i added the user cyrus as a normal user (with adduser) then 'apt-get libgd2'
 works. It seems that nut is installed now but i have to check this out in
 detail.

I see no link with nut. Maybe you've left some configuration
file referencing the cyrus user, which stopped install/upgrade
but for another package...

But nut isn't faulty there.
I let you finish your check and get back before closing this bug.

Thanks,
Arnaud
---
Linux / Unix Expert - MGE UPS SYSTEMS - RD Dpt
OpenSource Developer - http://arnaud.quette.free.fr/
Debian Developer - http://people.debian.org/~aquette/
 ... and much more ...





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#312106: preconfiguration bug break woody to sarge upgrade

[arnaud . quette]

Salut Bill,

 When trying to upgrade from woody, nut-cgi .config file fails with:
 
 Preconfiguring packages ...
 nut-cgi failed to preconfigure, with exit status 10
 (Reading database ... 65666 files and directories currently installed.)
 Preparing to replace nut-cgi 0.45.5-rel-1 (using 
.../nut-cgi_2.0.1-3_i386.deb) ...
 dpkg: error processing /var/cache/apt/archives/nut-cgi_2.0.1-3_i386.deb 
(--unpack):
  subprocess pre-installation script returned error exit status 10
 Errors were encountered while processing:
  /var/cache/apt/archives/nut-cgi_2.0.1-3_i386.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 
 See bug #312065.

First, thanks for your report and sorry not to have been
able to answer before...

I think I've found the problem (typo error on db_get and
db_fset, calling nut instead of nut-cgi) or at least one problem!

But as I'm not a debconf guru, I still have some doubt! The
problem seems to occur only when the user reply No,
which abort the install/upgrade process with an exit 1...
Note that I've based this upon nut ones that exists for
a long time (more than 3 years) which produce the same
error under the same condition.

Any advices welcomed.

Arnaud


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]