Bug#1022321: marked as pending in node-nouislider

[Doug Torrance]

Control: tag -1 pending

Hello,

Bug #1022321 in node-nouislider reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-nouislider/-/commit/e721d77d1de4f18383931d372a891b68e2483c91


d/t/pkg-js/test.py: Update test for Selenium 4.5 (Closes: #1022321).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022321

Bug#960614: normaliz: version `LIBEANTIC_0_1_2' not found

[Doug Torrance]

Package: normaliz
Version: 3.8.3+ds-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I am getting the following error message when running normaliz:

$ normaliz
normaliz: /usr/lib/x86_64-linux-gnu/libeanticxx.so.0: version 
`LIBEANTICXX_0_1_2' not found (required by normaliz)
normaliz: /usr/lib/x86_64-linux-gnu/libeantic.so.0: version `LIBEANTIC_0_1_2' 
not found (required by normaliz)
normaliz: /usr/lib/x86_64-linux-gnu/libeantic.so.0: version `LIBEANTIC_0_1_2' 
not found (required by /usr/lib/x86_64-linux-gnu/libnormaliz.so.3)
normaliz: /usr/lib/x86_64-linux-gnu/libeanticxx.so.0: version 
`LIBEANTICXX_0_1_2' not found (required by 
/usr/lib/x86_64-linux-gnu/libnormaliz.so.3)

This is also being reported by Debian Continuous Integration, e.g.:
https://ci.debian.net/data/autopkgtest/testing/amd64/n/normaliz/5446108/log.gz

This appears to be due to the recent upload of e-antic 0.1.5 to sid.

Bug#959611: wmauda: FTBFS: dbus.h:23:10: fatal error: dbus/dbus-glib.h: No such file or directory

[Doug Torrance]

On Sun, May 3, 2020 at 3:33 PM Doug Torrance  wrote:
> On Sun, May 3, 2020 at 9:12 AM Lucas Nussbaum  wrote:
> > > In file included from wmauda.c:29:
> > > /usr/include/audacious/dbus.h:23:10: fatal error: dbus/dbus-glib.h: No 
> > > such file or directory
> > >23 | #include 
> > >   |  ^~
> > > compilation terminated.
> > > make[1]: *** [: wmauda.o] Error 1
>
> Thanks for the report!  It turns out wmauda was missing a build
> dependency on libdbus-glib-1-dev.  This has been fixed in git [1].

I've just added a couple more commits, bumping the Standards Version
and drafting a new d/changelog entry.  Andreas, would you be able to
take a look and sponsor?

https://salsa.debian.org/wmaker-team/wmauda

Thanks!
Doug

Bug#959611: wmauda: FTBFS: dbus.h:23:10: fatal error: dbus/dbus-glib.h: No such file or directory

[Doug Torrance]

Control: tags -1 pending

On Sun, May 3, 2020 at 9:12 AM Lucas Nussbaum  wrote:
> > In file included from wmauda.c:29:
> > /usr/include/audacious/dbus.h:23:10: fatal error: dbus/dbus-glib.h: No such 
> > file or directory
> >23 | #include 
> >   |  ^~
> > compilation terminated.
> > make[1]: *** [: wmauda.o] Error 1

Thanks for the report!  It turns out wmauda was missing a build
dependency on libdbus-glib-1-dev.  This has been fixed in git [1].

Doug

[1] https://salsa.debian.org/wmaker-team/wmauda/-/commit/1a5857e

Bug#952233: frobby: FTBFS: ! LaTeX Error: File `listofitems.sty' not found.

[Doug Torrance]

Control: reassign -1 texlive-latex-extra
Control: merge 921297 -1

On Sun, Feb 23, 2020 at 8:21 AM Lucas Nussbaum  wrote:
> > ! LaTeX Error: File `listofitems.sty' not found.

Thanks for the report!  This bug was previously reported in #921300,
which was merged with #921297.

Bug#564173: wmcalc: wrong result in simple calculation, then abort on _XSend:

[Doug Torrance]

This bug still persists in wmcalc 0.6, although a fix has been submitted 
upstream [1].


[1] https://groups.google.com/forum/#!topic/wmaker-dev/4uEVw8bm-cU

Bug#907010: fflas-ffpack: baseline violation on i386

[Doug Torrance]

On 08/22/2018 11:35 PM, Adrian Bunk wrote:

Source: fflas-ffpack
Version: 2.3.2-1~exp3
Severity: serious

SSE is not part of the i386 baseline.


Thanks for your report!

Is it documented anywhere which instruction sets are part of which 
architectures' baselines?


We could of course disable all instruction sets on all architectures in 
fflas-ffpack, but perhaps there's a more nuanced solution using 
dpkg-architecture?


Doug

Bug#905300: gfan: FTBFS on 32bit architectures: test 0602ResultantFanProjection hangs

[Doug Torrance]

Control: forwarded -1 jen...@imf.au.dk

Hello!

I am one of the maintainers of gfan in Debian.  We recently received the 
following bug report.  In particular, one of the tests introduced in 
version 0.6 hangs on 32-bit systems:


On 08/02/2018 01:46 PM, Andreas Beckmann wrote:

Source: gfan
Version: 0.6.2-1~exp1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

gfan/experimental FTBFS on all 32bit architectures since a test hangs:

https://buildd.debian.org/status/package.php?p=gfan=experimental

[...]
Running command:"cat testsuite/0602ResultantFanProjection/outputNew"
E: Build killed with signal TERM after 150 minutes of inactivity


Thanks!
Doug Torrance

Bug#897801: linbox: ftbfs with GCC-8

[Doug Torrance]

On 07/18/2018 01:16 PM, Juhani Numminen wrote:

On Fri, 04 May 2018 12:22:31 + Matthias Klose  wrote:

Package: src:linbox
Version: 1.4.2-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8



../../linbox/matrix/densematrix/blas-transposed-matrix.h:74:8: error: too many 
template-parameter-lists


There is a recent commit that mentions "too many template-parameter-lists"
https://github.com/linbox-team/linbox/commit/1a048eb


Thanks for your note!

Although that particular commit doesn't apply to the current upstream 
version, it prompted me to do some digging.  This bug has been fixed 
upstream [1] based on a patch from Arch [2].


I've applied the patch in git [3] and prepared a new Debian version.

I'm CC'ing the Sage list -- would anyone be able to sponsor?

[1] https://github.com/linbox-team/linbox/commit/56be867
[2] 
https://git.archlinux.org/svntogit/community.git/commit/trunk/linbox-gcc8.patch?h=packages/linbox=153798a17b01b88c97d315e596d8ccb3408f3bfb

[3] https://salsa.debian.org/science-team/linbox/commit/81cc283

Bug#902753: fflas-ffpack FTBFS on 32bit big endian: test failure

[Doug Torrance]

Control: forwarded -1 https://github.com/linbox-team/fflas-ffpack/issues/155

On 06/30/2018 09:03 AM, Adrian Bunk wrote:
> Source: fflas-ffpack
> Version: 2.3.2-1~exp1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/package.php?p=fflas-ffpack=sid
> 
> ...
> Checking Modular, RecInt::ruint<8>> modulo 
> 137086259543411796519661122363958397351 ... FAIL
> alpha   :1, beta   : 0
> m   :10, k   : 37
> ldA :49, incX : 1, incY : 8
> Error Y[0]=1992134205620791178773468912365171 
> D[0]=33516737080336839904404042326759926523
> Error Y[1]=19012610462383539819047065227639652127 
> D[1]=33027539844715459854001461431663776355
> Error Y[2]=36275471608480693956989447364591853611 
> D[2]=71305711375164665192185413746827937790
> Error Y[3]=16802259068307208301092687002429463235 
> D[3]=111805956383619924708206385812549612197
> Error Y[4]=37497646901470143638708872110055354636 
> D[4]=10851073192729426488164756656238986655
> Error Y[5]=111941573376661391371080194781913260186 
> D[5]=87502874614680165651743215857944944321
> Error Y[6]=24854382304849165236729549431699250443 
> D[6]=100589182556177209784894408578247046121
> Error Y[7]=64877439080209582754648837426698863426 
> D[7]=75580908271244353910959300344839680750
> Error Y[8]=77890500635456927145236262383571288034 
> D[8]=84739061027717235821509912345371008426
> Error Y[9]=68356228138285939741967710419270414124 
> D[9]=13534641280687414727768176760958703984
> XX
> FAILED
> FAIL test-fgemv (exit status: 1)
> 
> 
> Testsuite summary for FFLAS-FFPACK 2.3.2
> 
> # TOTAL: 31
> # PASS:  29
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  2
> # XPASS: 0
> # ERROR: 0
> 
> See tests/test-suite.log
> Please report to ffpack-de...@googlegroups.com
> 
> make[5]: *** [Makefile:1513: test-suite.log] Error 1
> 

Thanks for the report!

I noticed this bug and forwarded it upstream back in January.

Bug#894905: fflas-ffpack: missing Depends: libgivaro-dev (>= 4.0.3)

[Doug Torrance]

On 04/05/2018 08:24 AM, Andreas Beckmann wrote:

Package: fflas-ffpack
Version: 2.3.2-1~exp1
Severity: serious

Hi,

noticed this while rebuilding linbox/experimental in sid+experimental:

...
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FFLAS_FFPACK... no
configure: error: Package requirements (fflas-ffpack >= 2.3.0) were not met:

Package 'fflas-ffpack' requires 'givaro >= 4.0.3' but version of givaro is 4.0.2
You may find new versions of Givaro at http://givaro.forge.imag.fr

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables FFLAS_FFPACK_CFLAGS
and FFLAS_FFPACK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
...


The pkg-config file contains:

/-- fflas-ffpack.pc 
prefix=/usr
exec_prefix=/usr
libdir=/usr/lib
includedir=/usr/include

Name: fflas-ffpack
Description: Finite Field Linear Algebra Suroutines/Package
URL: http://github.com/linbox-team/fflas-ffpack
Version: 2.3.2
Requires: givaro >= 4.0.3
Libs: -fopenmp  -lblas -llapack
Cflags: -I${prefix}/include-fopenmp   -fabi-version=6
\---



Thanks for the report!

This would explain why I had to manually install givaro from 
experimental in my sbuild when I was packaging the new upstream version 
of linbox.  It never occurred to me that the mistake was in fflas-ffpack...


Anyway, I've fixed the problem in git [1].  I've copied this message to 
the Sage team -- would anyone be able to sponsor?


Doug

[1] https://salsa.debian.org/science-team/fflas-ffpack/commit/be453b1

Bug#857164: libwmaker-dev: missing Depends: libwmaker1 (= ${binary:Version})

[Doug Torrance]

On 03/08/2017 09:12 AM, Andreas Beckmann wrote:

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m23.2s ERROR: FAIL: Broken symlinks:
   /usr/lib/x86_64-linux-gnu/libWMaker.so -> libWMaker.so.1.0.1
Thank you for the report!  I have pushed the fix to our packaging git 
repository [1] and will hopefully get an upload sponsored soon.


Doug

[1] 
https://anonscm.debian.org/git/pkg-wmaker/wmaker.git/commit/?id=eb4556e4451eccbba8fc7ff6528835e4c6355375

Bug#845081: Bug #845081: wmbiff FTBFS on s390x: test failure

[Doug Torrance]

Control: severity -1 important

With wmbiff version 0.4.30-2, just uploaded to sid, the offending test 
(test_wmbiff) is now skipped on big endian archs like s390x.  Therefore, 
the package now builds on these archs.


The underlying problem still exists, but I am reducing the severity to 
important.


Doug

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

[Doug Torrance]

On 12/02/2016 12:58 PM, Bastian Blank wrote:

On Fri, Dec 02, 2016 at 10:44:05AM -0500, Doug Torrance wrote:

On 12/02/2016 09:26 AM, Bastian Blank wrote:

You know, Debian actually has a s390x porter machine.  You can use it to
test such problems.

Yeah, I've used porterboxes in the past.  I'm not a DD or DM, and
the process of getting porterbox access is kind of a headache.  If
this fix doesn't work, I'll go that route.


Oh, I'm sorry.  I missed that you only got a guest user; they are not
marked specially on db.debian.org.


No worries.  It looks like the signed short problem was fixed, but the 
build is still failing [1], so I'll be applying for porterbox access 
after all.  :)


Doug

[1] 
https://buildd.debian.org/status/fetch.php?pkg=wmbiff=s390x=0.4.30-1=1480698922

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

[Doug Torrance]

On 12/02/2016 09:26 AM, Bastian Blank wrote:

On Thu, Dec 01, 2016 at 09:37:23AM -0500, Doug Torrance wrote:

Thanks for your reply!
I've changed all the shorts to uint16_t's -- hopefully this works!


You know, Debian actually has a s390x porter machine.  You can use it to
test such problems.


Yeah, I've used porterboxes in the past.  I'm not a DD or DM, and the 
process of getting porterbox access is kind of a headache.  If this fix 
doesn't work, I'll go that route.


Doug

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

[Doug Torrance]

On 11/24/2016 08:25 AM, Bastian Blank wrote:

On Tue, Nov 22, 2016 at 12:46:27PM -0500, Doug Torrance wrote:

Error connecting: Invalid argument
connect(0.0.3.255:-7907) failed: Invalid argument


I would start here.  The IP/port information is converted incorrectly.

I assume it's this function:
| static int ipv4_sock_connect(struct in_addr *address, short port)

short is signed and incapable of carrying a port.


Thanks for your reply!

I've changed all the shorts to uint16_t's -- hopefully this works!

Doug

Bug#840458: [Debian-science-sagemath] linbox: FTBFS on i386: illegal instruction in test-{cra, charpoly}

[Doug Torrance]

Yes, please do.

On Tue, Nov 29, 2016, 1:52 PM Tobias Hansen <than...@debian.org> wrote:

> On 11/29/2016 06:01 PM, Tobias Hansen wrote:
> > On 11/29/2016 03:53 PM, Doug Torrance wrote:
> >> Control: reassign -1 src:givaro
> >>
> >> On 11/29/2016 09:58 AM, Tobias Hansen wrote:
> >>> I think I figured out at least the test failures with "Illegal
> >>> instruction" on i386. The problem is that givaro is built using cpu
> >>> extensions that are not allowed.
> >>>
> >>> Jerome figured out in [1] that the problem happens when givaro code is
> >>> called. And sure enough:
> >>>
> >>> objdump -S /usr/lib/i386-linux-gnu/libgivaro.so.9.0.0 | grep
> >>> '\b\(ymm\|zmm\|vfm\)'
> >>> 15411:c4 e3 79 6b 8b a4 29 vfmaddsd
> >>> %xmm2,-0x1d65c(%ebx),%xmm0,%xmm1
> >>> 154d1:c4 e3 69 6b 8b ac 29 vfmaddsd
> >>> %xmm0,-0x1d654(%ebx),%xmm2,%xmm1
> >>>
> >>> And in the i386 build logs for givaro there are these flags:
> >>> -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -msse4a -mavx
> >>> -mfma4 -mfpmath=sse
> >>>
> >>> Do you have time in the next days to disable these flags? Otherwise I
> >>> can do it. (I'm not sure if some of these flags (mmx, sse ?) are
> allowed
> >>> on i386 and didn't find that info. Ximin, do you know this?)
> >>
> >> Sure, I can take a look.  I think it should be a simple --disable-simd
> >> in d/rules (we did the same in fflas-ffpack).
> >>
> >> Doug
> >
> > Thanks! I tried building it but now there seems to be an issue similar
> > to [1]:
> >
> > FAIL: test-ringarith
> > 
> >
> > 997167681959697!=997167682008849 failed (at line 123)
> > x y failed !
> > MEDmax failed !
> > FAIL test-ringarith (exit status: 255)
> >
> > And it even fails when setting the flag -ffp-contract=off .
> > Note that now the failure seems to be related to ModularExtended
> > instead of ModularExtended (MEDmax instead of MEFmax in the error
> > message).
> >
> > Best,
> > Tobias
> >
> > [1] https://github.com/linbox-team/givaro/issues/25
>
> Ok, a workaround is to set -ffloat-store (like the Fedora package). I
> pushed this change to the git repo. Can I upload this?
>
> Best,
> Tobias
>

Bug#840458: linbox: FTBFS on i386: illegal instruction in test-{cra,charpoly}

[Doug Torrance]

Control: reassign -1 src:givaro

On 11/29/2016 09:58 AM, Tobias Hansen wrote:

I think I figured out at least the test failures with "Illegal
instruction" on i386. The problem is that givaro is built using cpu
extensions that are not allowed.

Jerome figured out in [1] that the problem happens when givaro code is
called. And sure enough:

objdump -S /usr/lib/i386-linux-gnu/libgivaro.so.9.0.0 | grep
'\b\(ymm\|zmm\|vfm\)'
15411:  c4 e3 79 6b 8b a4 29vfmaddsd 
%xmm2,-0x1d65c(%ebx),%xmm0,%xmm1
154d1:  c4 e3 69 6b 8b ac 29vfmaddsd 
%xmm0,-0x1d654(%ebx),%xmm2,%xmm1

And in the i386 build logs for givaro there are these flags:
-mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -msse4a -mavx
-mfma4 -mfpmath=sse

Do you have time in the next days to disable these flags? Otherwise I
can do it. (I'm not sure if some of these flags (mmx, sse ?) are allowed
on i386 and didn't find that info. Ximin, do you know this?)


Sure, I can take a look.  I think it should be a simple --disable-simd 
in d/rules (we did the same in fflas-ffpack).


Doug

Bug#845081: Bug##845081: wmbiff FTBFS on s390x: test failure

[Doug Torrance]

Hello!

I am copying the RC bug below to the s390 mailing list.  I am stumped as 
to what is going on.  Does anyone have any suggestions?


Thank you!

On Sun, 20 Nov 2016 11:30:55 +0200 Adrian Bunk  wrote:
> Source: wmbiff
> Version: 0.4.29-1
> Severity: serious
>
> 
https://buildd.debian.org/status/fetch.php?pkg=wmbiff=s390x=0.4.29-1=1479607292

>
> ...
> wmbiff/ imap4: Couldn't parse line imap:foo:mi@ta@bar/mybox (0)
> If this used to work, run wmbiff with the -relax option, and
> send mail to wmaker-...@lists.windowmaker.org with the hostname
> of your mail server.
> wmbiff/ imap4: Couldn't parse line imap:user pa ss bar/"space box" 12 (0)
> If this used to work, run wmbiff with the -relax option, and
> send mail to wmaker-...@lists.windowmaker.org with the hostname
> of your mail server.
> wmbiff/ pop3: Couldn't parse line pop3:user pa ss bar 12 (0)
> If this used to work, run wmbiff with the -relax option, and
> send mail to wmaker-...@lists.windowmaker.org with the hostname
> of your mail server.
> Error connecting: Invalid argument
> connect(0.0.3.255:-7907) failed: Invalid argument
> SOME TESTS FAILED!
> FAIL test_wmbiff (exit status: 1)
>
> 


> Testsuite summary for WMBiff 0.4.29
> 


> # TOTAL: 1
> # PASS: 0
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
> 

Bug#835759: fflas-ffpack: FTBFS: unsatisfiable build-dependency: libgivaro-dev (< 4.0.2) but 4.0.2-1 is to be installed

[Doug Torrance]

On 08/28/2016 04:48 AM, Lucas Nussbaum wrote:

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


> ...
>

The following packages have unmet dependencies:
  sbuild-build-depends-fflas-ffpack-dummy : Depends: libgivaro-dev (< 4.0.2) 
but 4.0.2-1 is to be installed


Thanks for your report!

This is a known issue.  The latest upstream version of fflas-ffpack 
(2.2.2) does work with givaro 4.0.2.  Packaging work for this newer 
version is in progress.


Doug

Bug#833846: fflas-ffpack: don't generate optimised code based on the build machine

[Doug Torrance]

Control: tags -1 pending

On 08/09/2016 07:53 AM, Ximin Luo wrote:

Control: severity -1 serious

I was recommended by multiple people to bump the severity of this bug. Also to clarify that i386 
should have no optimisation flags, and not "-msse -msse2". My earlier comment was based 
on a misunderstanding of what "i386 doesn't have mmx" meant; sse and sse2 build on top of 
mmx.

X

Ximin Luo:

Package: fflas-ffpack
Version: 2.2.1-1
Severity: important

Dear Maintainer,

fflas-ffpack on amd64 was built with "-msse4.1 -mfma -mavx2" as can be seen
from the output of `pkg-config --cflags fflas-ffpack`. This unfortunately makes
it crash on amd64 machines that don't support these instructions, and we are
running into this issue whilst testing SageMath.

Please disable any build options that set optimisations based on autodetection
of the CPU features of the build machine.

It should be OK to hard-code "-mmmx -msse -msse2" for amd64 and "-msse -msse2"
for i386, according to wRAR on #debian-devel. This is somewhat based on
information from [1]. There might be other optimisations you can make, but I
haven't yet done the detailed research for that.

X

[1] https://lists.debian.org/debian-devel-announce/2016/05/msg1.html


Thanks for your report!  I had figured that there was an issue like 
this, as both the CI and reproducible build tasks have been failing.


I've disabled the use of these extensions and a new version is in git 
[1] awaiting sponsorship.


Doug

[1] 
https://anonscm.debian.org/cgit/debian-science/packages/fflas-ffpack.git/commit/?id=88c339f745dc54351d4c437eedd38a5b83dca993 

Bug#811847: givaro RC bug #811847

[Doug Torrance]

On 07/18/2016 01:53 AM, Julien Puydt wrote:

On 17/07/2016 19:54, Doug Torrance wrote:

I see that you've recently pushed some changes to git which close the RC
bug #811847 [1].  Were you planning on uploading them?  I ask because
givaro is currently scheduled for auto-removal from testing.  I'm also
interested in givaro as it is a dependency for Macaulay2, which I'm
trying to get into Debian.

If you'd like, I'd be happy to help.


I started a transition for NTL and wanted to get it through before
starting a transition for givaro.

If I'm the one asking for the transition, I'll first need to
re-double-check the deps before RFS-ing to experimental and starting the
ball rolling -- and I won't have time before a few days.


Ah, makes sense!


If you take over, you can do it right away : I'll consider you're
helping, not stepping on my toes :-)



Sounds good.  Upstream actually switched to GitHub a few months ago and 
released a new version (4.0.1) [1].  I'd also like to backport a recent 
commit that's necessary for Macaulay2 to build.


Doug

[1] https://github.com/linbox-team/givaro

Bug#811847: givaro RC bug #811847

[Doug Torrance]

Hi Julien,

I see that you've recently pushed some changes to git which close the RC 
bug #811847 [1].  Were you planning on uploading them?  I ask because 
givaro is currently scheduled for auto-removal from testing.  I'm also 
interested in givaro as it is a dependency for Macaulay2, which I'm 
trying to get into Debian.


If you'd like, I'd be happy to help.

Thanks!
Doug

[1] https://anonscm.debian.org/git/debian-science/packages/givaro.git

Bug#831109: mathic: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

[Doug Torrance]

Control: tags -1 pending

On 07/14/2016 04:06 AM, Lucas Nussbaum wrote:

Source: mathic
Version: 1.0~git20160320-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):

make[1]: Entering directory '/«PKGBUILDDIR»'
dh_strip --dbgsym-migration='libmathic-dbg (<< 1.0~git20160320-1~)'
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_makeshlibs -a
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libmathic0v5/DEBIAN/symbols doesn't match 
completely debian/libmathic0v5.symbols
--- debian/libmathic0v5.symbols (libmathic0v5_1.0~git20160320-3_amd64)
+++ dpkg-gensymbols3hUTVg   2016-07-13 19:29:21.32400 +
@@ -102,7 +102,7 @@
   _ZNK6mathic10HelpAction5topicB5cxx11Ev@Base 1.0~git20160320
   _ZNK6mathic11BitTriangle12getMemoryUseEv@Base 1.0~git20130827
   
_ZNK6mathic11NameFactoryINS_6ActionEE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
 1.0~git20160320
- 
(optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
 1.0~git20160320
+#MISSING: 1.0~git20160320-3# 
(optional)_ZNK6mathic11NameFactoryIPvE15namesWithPrefixERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIS8_SaIS8_EE@Base
 1.0~git20160320
   _ZNK6mathic13BoolParameter12argumentTypeB5cxx11Ev@Base 1.0~git20160320
   _ZNK6mathic13BoolParameter13valueAsStringB5cxx11Ev@Base 1.0~git20160320
   _ZNK6mathic13ColumnPrinter14getColumnCountEv@Base 1.0~git20130827
@@ -118,15 +118,15 @@
   
_ZNK6mathic9CliParser29pushBackRegisteredActionNamesERSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE@Base
 1.0~git20160320
   
_ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED1Ev@Base 
1.0~git20160320
   
_ZNSt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS2_EED2Ev@Base 
1.0~git20160320
- 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
 1.0~git20160320
+#MISSING: 1.0~git20160320-3# 
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIIRKS5_EEEvDpOT_@Base
 1.0~git20160320
   
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJRKS5_EEEvDpOT_@Base
 1.0~git20160320
   
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base
 1.0~git20160320
   
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base
 1.0~git20160320
- 
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base
 1.0~git20130827
+#MISSING: 1.0~git20160320-3# 
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIIS6_EEEvDpOT_@Base
 1.0~git20130827
   
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EE19_M_emplace_back_auxIJS6_EEEvDpOT_@Base
 1.0~git20130827
   
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EED1Ev@Base
 1.0~git20130827
   
_ZNSt6vectorISt10unique_ptrIN6mathic13ColumnPrinter3ColESt14default_deleteIS3_EESaIS6_EED2Ev@Base
 1.0~git20130827
- 
_ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIISE_EEEvDpOT_@Base
 1.0~git20160320
+#MISSING: 1.0~git20160320-3# 
_ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIISE_EEEvDpOT_@Base
 1.0~git20160320
   
_ZNSt6vectorISt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFSt10unique_ptrIPvSt14default_deleteIS8_EEvEESaISE_EE19_M_emplace_back_auxIJSE_EEEvDpOT_@Base
 1.0~git20160320
   _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 
1.0~git20160320
   _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 
1.0~git20160320
dh_makeshlibs: failing due to earlier errors
make: *** [binary-arch] Error 255


The full build log is available from:

http://people.debian.org/~lucas/logs/2016/07/13/mathic_1.0~git20160320-3_unstable_gcc6.log


Thanks for the report!

I have pushed a fix to git marking the offending tags as optional [1] 
and have requested sponsorship for an upload of the new version.


Doug

[1] 

Bug#811805: gfan: FTBFS with GCC 6: error: reference is ambiguous

[Doug Torrance]

Control: tags -1 pending

On Tue, 19 Jan 2016 18:08:29 -0800 Martin Michlmayr  wrote:
> This package fails to build with GCC 6. GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.

This was fixed in Gentoo [1].  I have converted their patch to quilt and
prepared a new release of the package.

The new release also fixes a couple Lintian warnings and bumps to the latest
Standards-Version.  I've pushed it to git [2] and will request sponsorship.

Doug

[1] 
https://gitweb.gentoo.org/repo/gentoo.git/commit/sci-mathematics/gfan/files/gfan-0.5-gcc6.1-compat.patch

[2] https://anonscm.debian.org/git/debian-science/packages/gfan.git

Bug#814213: wmaker: FTBFS: Error: program option '--with-aix-soname' is not in the documentation './INSTALL-WMAKER'

[Doug Torrance]

On 02/09/2016 03:59 AM, Chris Lamb wrote:
> Source: wmaker
> Version: 0.95.7-3
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> wmaker fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   make  check-local
>   make[4]: Entering directory 
> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>   ./script/check-cmdline-options-doc.sh \
>   --program "./configure" --text-doc "./INSTALL-WMAKER" \
>   --ignore-prg 'with-PACKAGE,without-PACKAGE # only template names from 
> Autoconf' \
>   --ignore-prg 'program-prefix,program-suffix,program-transform-name # in 
> INSTALL' \
>   --ignore-prg 'version,quiet,srcdir,build,host,cache-file,no-create # in 
> INSTALL' \
>   --ignore-prg 'enable-silent-rules,disable-silent-rules # should be in 
> INSTALL' \
>   --ignore-prg 'enable-dependency-tracking,disable-dependency-tracking # 
> in INSTALL' \
>   --ignore-prg 'enable-shared,enable-static # should be in INSTALL' \
>   --ignore-prg 'disable-option-checking,enable-fast-install # should be 
> in INSTALL' \
>   --ignore-prg 'disable-libtool-lock,with-pic,with-gnu-ld,with-sysroot # 
> for libtool' \
>   --ignore-prg 'runstatedir #new in autoconf 2.70, backported in Debian' \
>   --ignore-prg 'with-x # no use, it would not work without X'
>   Error: program option '--with-aix-soname' is not in the documentation 
> './INSTALL-WMAKER'
>   Makefile:951: recipe for target 'configure-documentation' failed
>   make[4]: *** [configure-documentation] Error 1
>   make[4]: Leaving directory 
> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>   Makefile:766: recipe for target 'check-am' failed
>   make[3]: *** [check-am] Error 2
>   make[3]: Leaving directory 
> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>   Makefile:478: recipe for target 'check-recursive' failed
>   make[2]: *** [check-recursive] Error 1
>   make[2]: Leaving directory 
> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>   Makefile:768: recipe for target 'check' failed
>   make[1]: *** [check] Error 2
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>   dh_auto_test: make -j9 check returned exit code 2
>   debian/rules:30: recipe for target 'build' failed
>   make: *** [build] Error 2
> 
>   [..]

Thanks for your report!

This is because libtool 2.4.6 was just uploaded to sid on Sunday [1].
>From [2]:
  * m4/ltoptions.m4 (_LT_WITH_AIX_SONAME): New. Provides
  commandline option --with-aix-soname=aix|svr4|both. Declares
  $shared_archive_member_spec as libtool variable.

[1] https://packages.qa.debian.org/libt/libtool/news/20160207T173014Z.html
[2] 
http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=8fa719e81dba828d3e22cd59f825fac456c20809

Bug#814213: wmaker: FTBFS: Error: program option '--with-aix-soname' is not in the documentation './INSTALL-WMAKER'

[Doug Torrance]

Control: tags -1 pending

On 02/09/2016 05:57 AM, Doug Torrance wrote:
> On 02/09/2016 03:59 AM, Chris Lamb wrote:
>> Source: wmaker
>> Version: 0.95.7-3
>> Severity: serious
>> Justification: fails to build from source
>> User: reproducible-bui...@lists.alioth.debian.org
>> Usertags: ftbfs
>> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
>>
>> Dear Maintainer,
>>
>> wmaker fails to build from source in unstable/amd64:
>>
>>   [..]
>>
>>   make  check-local
>>   make[4]: Entering directory 
>> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>>   ./script/check-cmdline-options-doc.sh \
>>  --program "./configure" --text-doc "./INSTALL-WMAKER" \
>>  --ignore-prg 'with-PACKAGE,without-PACKAGE # only template names from 
>> Autoconf' \
>>  --ignore-prg 'program-prefix,program-suffix,program-transform-name # in 
>> INSTALL' \
>>  --ignore-prg 'version,quiet,srcdir,build,host,cache-file,no-create # in 
>> INSTALL' \
>>  --ignore-prg 'enable-silent-rules,disable-silent-rules # should be in 
>> INSTALL' \
>>  --ignore-prg 'enable-dependency-tracking,disable-dependency-tracking # 
>> in INSTALL' \
>>  --ignore-prg 'enable-shared,enable-static # should be in INSTALL' \
>>  --ignore-prg 'disable-option-checking,enable-fast-install # should be 
>> in INSTALL' \
>>  --ignore-prg 'disable-libtool-lock,with-pic,with-gnu-ld,with-sysroot # 
>> for libtool' \
>>  --ignore-prg 'runstatedir #new in autoconf 2.70, backported in Debian' \
>>  --ignore-prg 'with-x # no use, it would not work without X'
>>   Error: program option '--with-aix-soname' is not in the documentation 
>> './INSTALL-WMAKER'
>>   Makefile:951: recipe for target 'configure-documentation' failed
>>   make[4]: *** [configure-documentation] Error 1
>>   make[4]: Leaving directory 
>> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>>   Makefile:766: recipe for target 'check-am' failed
>>   make[3]: *** [check-am] Error 2
>>   make[3]: Leaving directory 
>> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>>   Makefile:478: recipe for target 'check-recursive' failed
>>   make[2]: *** [check-recursive] Error 1
>>   make[2]: Leaving directory 
>> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>>   Makefile:768: recipe for target 'check' failed
>>   make[1]: *** [check] Error 2
>>   make[1]: Leaving directory 
>> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>>   dh_auto_test: make -j9 check returned exit code 2
>>   debian/rules:30: recipe for target 'build' failed
>>   make: *** [build] Error 2
>>
>>   [..]
> 
> Thanks for your report!
> 
> This is because libtool 2.4.6 was just uploaded to sid on Sunday [1].
> From [2]:
>   * m4/ltoptions.m4 (_LT_WITH_AIX_SONAME): New. Provides
>   commandline option --with-aix-soname=aix|svr4|both. Declares
>   $shared_archive_member_spec as libtool variable.
> 
> [1] https://packages.qa.debian.org/libt/libtool/news/20160207T173014Z.html
> [2] 
> http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=8fa719e81dba828d3e22cd59f825fac456c20809

I've just pushed a patch to git which fixes this issue. [1]

Andreas or kix, would either of you be willing to review and sponsor an
upload?

Thanks!
Doug

[1] 
http://anonscm.debian.org/cgit/pkg-wmaker/wmaker.git/commit/?id=dd955a763d8f1189d9f06e9447811915d89c50b4

Bug#814213: [PATCH 2/2] check-doc: Ignore with-aix-soname in check-cmdline-options-doc.sh

[Doug Torrance]

Control: tags -1 forwarded wmaker-...@lists.windowmaker.org

libtool 2.4.4 will add a --with-aix-soname option.  Ignore it when checking
whether INSTALL-WMAKER is up to date.

Fixes Debian bug #814213 [1].  Proposed fix to Debian package at [2].

   From: Chris Lamb 
   Subject: wmaker: FTBFS: Error: program option '--with-aix-soname' is not in
 the documentation './INSTALL-WMAKER'
   Date: Tue, 09 Feb 2016 09:59:14 +0100

   Dear Maintainer,

   wmaker fails to build from source in unstable/amd64:

 [..]

 make  check-local
 make[4]: Entering directory '/home/lamby/temp/
   cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
 ./script/check-cmdline-options-doc.sh \
--program "./configure" --text-doc "./INSTALL-WMAKER" \
--ignore-prg 'with-PACKAGE,without-PACKAGE # only template names from
  Autoconf' \
--ignore-prg 'program-prefix,program-suffix,program-transform-name
  # in INSTALL' \
--ignore-prg 'version,quiet,srcdir,build,host,cache-file,no-create
  # in INSTALL' \
--ignore-prg 'enable-silent-rules,disable-silent-rules # should be in
  INSTALL' \
--ignore-prg 'enable-dependency-tracking,disable-dependency-tracking
  # in INSTALL' \
--ignore-prg 'enable-shared,enable-static # should be in INSTALL' \
--ignore-prg 'disable-option-checking,enable-fast-install # should be
  in INSTALL' \
--ignore-prg 'disable-libtool-lock,with-pic,with-gnu-ld,with-sysroot
  # for libtool' \
--ignore-prg 'runstatedir #new in autoconf 2.70, backported in Debian' \
--ignore-prg 'with-x # no use, it would not work without X'
 Error: program option '--with-aix-soname' is not in the documentation
   './INSTALL-WMAKER'
 Makefile:951: recipe for target 'configure-documentation' failed
 make[4]: *** [configure-documentation] Error 1

 [..]

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814213
[2] http://anonscm.debian.org/cgit/pkg-wmaker/wmaker.git/commit/?id=dd955a7
---
 Makefile.am | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Makefile.am b/Makefile.am
index e925ab6..638cfed 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -107,6 +107,7 @@ configure-documentation:
--ignore-prg 'disable-option-checking,enable-fast-install # 
should be in INSTALL' \
--ignore-prg 
'disable-libtool-lock,with-pic,with-gnu-ld,with-sysroot # for libtool' \
--ignore-prg 'runstatedir #new in autoconf 2.70, backported in 
Debian' \
+   --ignore-prg 'with-aix-soname #new in libtool 2.4.4' \
--ignore-prg 'with-x # no use, it would not work without X'
 
 .PHONY: configure-documentation
-- 
2.5.0

Bug#800193: wmpinboard: Please migrate a supported debhelper compat level

[Doug Torrance]

Control: tags -1 pending

On Sun, 27 Sep 2015 17:35:06 +0200 ni...@thykier.net wrote:
> The package wmpinboard is using a debhelper compat level of 3 or less
> according to lintian. These compat levels have been deprecated for
> the past ~10 years and debhelper will remove support for them in the near
> future (as declared in [1]).
>
> * Please migrate the package to a supported debhelper compat level.
> - Compat 9 is recommended
> - Compat 5 is the bare minimum (compat 4 will be removed soon as
> well)
>
> * If your package uses any of the following tools, please remove them
> from the rules files. Neither of them does anything except warn
> about their deprecation.
> - dh_desktop
> - dh_scrollkeeper (deadline: January 1st 2016)
> - dh_suidregister
> - dh_undocumented
>
> * Please note that your package might have been flagged for using
> e.g. "DH_COMPAT=2 dh_foo ...".
> - This will still cause issues when the compat level is removed.
>
> * If the package has been relying on dh_install being lenient about
> missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].
>
> * Deadline:
> - compat 1+2: November 1st 2015
> - compat 3: January 1st 2016
>
> If you are using other deprecated debhelper features (such as omitting
> the debian/compat file), please consider fixing those while you are at
> it.
>
> Thanks,
> ~Niels
>
> [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html

After receiving permission from the previous maintainer, I will be
adopting wmpinboard as a member of the Debian Window Maker Team.

A new version of the package (1.0.1-1) using debhelper 9 is currently on
mentors waiting for review from my sponsor.

Bug#811304: [Pkg-wmaker-devel] Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Doug Torrance]

On 01/19/2016 02:41 PM, Andreas Metzler wrote:

We can choose one of these hacks:
1 Find a way to ship unpatched libwraster 0.95.7 in Debian.

2a Patch the source to fix back the symbol versioning to
LIBWRASTER3

2b Patch the source to use a different soname. (If the ABI breaks in
an incompatible way, requiring rebuilds library maintance 101 says: bump
the soname.)

1 cannot be done /properly/. libwraster-0.95.6 and libwraster-0.95.7
have the same soname and are therefore not co-installable but would
need to conflict. So we cannot do the usual seamless partial upgrades,
it won't be possible to upgrade wmaker (built against
libwraster-0.95.7) while keeping wmweather+ 2.15-1.1 (built against
libwraster-0.95.6) functional.

Both 2a and 2b have the downside that Debian's libwraster/0.95.7 will
be binary incompatible with unpatched libwraster/0.95.7 (as possible
shipped by e.g. Fedora)

2a has the benefit of avoiding an actually useless library transition.
There is little to speak for 2b, except perhaps the fact that it shows
that our ABI differs from upstream.

So, having to choose I would strongly vote for 2a, adding attached
patch to debian/patches/ and updating the symbol file (again).

I have not got more time to spend on this today, but if you agree that
this is best course of action I can make an upload along these lines.
Ideally upstream would fix this instead of us.


Thank you for the clarification, Andreas!  I completely neglected to 
think about the fact that libwraster5 and my proposed libwraster5v2 
would both be trying to install the same file.


Option 2a sounds good to me.  Feel free to revert my last few commits if 
you get to it before I do.


Just to clarify, would the best course of action for upstream to be to 
go ahead and bump the soname for libwraster to 6 for the next release? 
If so, I can prepare a patch.


Doug

Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Doug Torrance]

On Sun, 17 Jan 2016 20:58:13 +0100 Julien Puydt
 wrote:
> upgrading libwraster5 broke wdm with the above error message.

As Andreas noted in his forwarding message to the dev mailing list [1],
this is due to a change made upstream between versions 0.95.6 and 0.95.7
which changed the version from LIBWRASTER3 to LIBWRASTER5.

When I try rebuilding wdm against libwraster5 from version 0.95.7, it
works fine.  However, it still shows Depends on libwraster5 (>=
0.95.6).  So there's still a problem if, say, wdm had a binNMU against
0.95.7 and then someone were to install it alongside libwraster5 from
0.95.6.

I think the solution is to rename libwraster5 to something like
libwraster5v2 and trigger an auto transition.

Doug

[1]
http://permalink.gmane.org/gmane.compw.window-managers.windowmaker.devel/9757

Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Doug Torrance]

Control: tags -1 pending

On 01/18/2016 02:55 PM, Doug Torrance wrote:
> I think the solution is to rename libwraster5 to something like
> libwraster5v2 and trigger an auto transition.

I've pushed these changes to git.  Note that the new library already
means we'll have to wait for the NEW queue, so I've kept the new
wmaker-utils package for #78119 in.

Andreas or kix, would either of you be able to take a look and upload?

Thanks!
Doug

Bug#798136: wmbattery does not update display after launching

[Doug Torrance]

Control: tags -1 unreproducible moreinfo
Control: severity -1 important

On Sat, 05 Sep 2015 23:35:22 -0400 Norman Ramsey <n...@cs.tufts.edu> wrote:
> After a recent upgrade from wheezy to jessie, wmbattery no longer
> tracks battery information in real time. The time remaining and
> charge percentage are accurate when launched, but they don't change.
>
> wmbattery *does* notice a power-loss or power-acquisition event,
> and when it responds to these, it also updates percentage charge and
> time remaining. But otherwise they do not track.
>
> On the command line, acpi reports good information, and gkrellm's
> battery monitor tracks changes to charge percentage in real time.
>
> I marked the bug 'grave' since the only purpose of the package is to
> monitor battery status in real time, and if the status is not updated,
> the package is not fulfilling its intended purpose.
>
> I mostly run a standard jessie installation, but just in case I did
> install the latest wmbattery from stretch. Still not updating.

Thanks for your report!

I'm not able to reproduce this problem, so I'm downgrading the bug to
important.  Could you provide some more information?

In particular, could you run "upower --monitor-detail" from the command
line?  It should periodically print out a status report with information
about your battery.  If it doesn't, then this is likely an issue with
upower.  (Note that wmbattery switched to using upower in 2.42, right
after the version that was in wheezy.)

Thanks!
Doug Torrance

Bug#798188: wmacpi: FTBFS when rebuild against libdockapp3

[Doug Torrance]

Control: tags -1 pending

On Sun, 06 Sep 2015 16:14:17 +0200 Niels Thykier  wrote:
> The wmacpi package FTBFS when rebuild against libdockapp3.
>
> """
> gcc -MM -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -O2 -Wall -W -g -ansi wmacpi.c > wmacpi.d
> gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-O2 -Wall -W -g -ansi -D_FORTIFY_SOURCE=2 -c -o wmacpi.o wmacpi.c
> wmacpi.c:22:21: fatal error: dockapp.h: No such file or directory
> compilation terminated.
> make[1]: *** [wmacpi.o] Error 1
> """

Thanks for your report!

I've prepared a new version of the wmacpi package which fixes this
issue.  It should be uploaded soon, once my sponsor takes a look at it.

Bug#798115: wmail: FTBFS with libdockapp v0.7.0

[Doug Torrance]

On Sat, 05 Sep 2015 15:45:31 -0400 Doug Torrance
<dtorra...@piedmont.edu> wrote:
> P.S. If you are interested, you might consider developing wmail as a
member
> of the Debian Window Maker Team [1].
>
> [1]

My apologies, I neglected to paste the URL:

https://pkg-wmaker.alioth.debian.org/

Bug#798115: wmail: FTBFS with libdockapp v0.7.0

[Doug Torrance]

Package: wmail
Version: 2.0-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Beginning with version 0.7.0, the dockapp.h header file included with
libdockapp has been moved from /usr/include to /usr/include/libdockapp.

Therefore, its reverse dependencies, including wmail, should take this into
account when building.

I have attached a patch which fixes this issue.

Thanks!
Doug Torrance

P.S.  If you are interested, you might consider developing wmail as a member
of the Debian Window Maker Team [1].

[1] 
diff -rupN wmail-2.0/debian/rules wmail-fix/debian/rules
--- wmail-2.0/debian/rules	2015-09-05 15:28:48.0 -0400
+++ wmail-fix/debian/rules	2015-09-05 15:30:03.060035687 -0400
@@ -11,7 +11,7 @@ DEB_HOST_GNU_TYPE   ?= $(shell dpkg-arch
 DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 
 
-CFLAGS = -Wall -g
+CFLAGS = -Wall -g -I/usr/include/libdockapp
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
 	CFLAGS += -O0

Bug#798118: wmdate: FTBFS with libdockapp v0.7.0

[Doug Torrance]

Package: wmdate
Version: 0.7-4
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Beginning with version 0.7.0, the dockapp.h header file included with
libdockapp has been moved from /usr/include to /usr/include/libdockapp.

Therefore, its reverse dependencies, including wmdate, should take this into
account when building.

I have attached a patch which fixes this issue.

Thanks!
Doug Torrance

P.S.  If you are interested, you might consider developing wmdate as a member
of the Debian Window Maker Team [1].

[1] https://pkg-wmaker.alioth.debian.org/
diff -rupN wmdate-0.7/debian/rules wmdate-fix/debian/rules
--- wmdate-0.7/debian/rules	2015-09-05 15:48:06.0 -0400
+++ wmdate-fix/debian/rules	2015-09-05 16:11:43.544225122 -0400
@@ -7,5 +7,7 @@ include /usr/share/cdbs/1/rules/patchsys
 DEB_MAKE_CLEAN_TARGET	:= distclean
 DEB_MAKE_INSTALL_TARGET := install DESTDIR=$(CURDIR)/debian/wmdate
 
+CPPFLAGS += -I/usr/include/libdockapp
+
 configure/wmdate::
 	xmkmf

Bug#784711: wmaker: diff for NMU version 0.95.6-1.1

[Doug Torrance]

Control: tags 784711 + patch
Control: tags 784711 + pending

Dear maintainer,

I've prepared an NMU for wmaker (versioned as 0.95.6-1.1) and
have asked my sponsor to upload it to DELAYED/2. Please feel
free to tell me if I should delay it longer.

Regards.
diff -Nru wmaker-0.95.6/debian/changelog wmaker-0.95.6/debian/changelog
--- wmaker-0.95.6/debian/changelog	2014-10-31 07:12:59.0 -0500
+++ wmaker-0.95.6/debian/changelog	2015-05-21 13:34:40.0 -0500
@@ -1,3 +1,12 @@
+wmaker (0.95.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control:
+- Add Breaks/Replaces for libwraster3-dev; remove Provides for
+  libwraster-dev (Closes: #784711).
+
+ -- Doug Torrance dtorra...@monmouthcollege.edu  Thu, 21 May 2015 13:34:40 -0500
+
 wmaker (0.95.6-1) unstable; urgency=medium
 
   * New upstream version 0.95.6. [Closes: #148856]
diff -Nru wmaker-0.95.6/debian/control wmaker-0.95.6/debian/control
--- wmaker-0.95.6/debian/control	2014-10-31 04:05:38.0 -0500
+++ wmaker-0.95.6/debian/control	2015-05-21 13:28:12.0 -0500
@@ -45,7 +45,8 @@
 Depends: libwraster5 (= ${binary:Version}), libc6-dev, libx11-dev,
  libxext-dev, libxpm-dev, libjpeg-dev, libpng-dev, libgif-dev,
  libtiff5-dev, ${misc:Depends}
-Provides: libwraster-dev
+Breaks: libwraster3-dev
+Replaces: libwraster3-dev
 Description: Static libraries and headers of Window Maker rasterizer
  This library is used to manipulate images and convert them to
  a format that can be displayed through the X window system.

Bug#784702: wmweather+: diff for NMU version 2.15-1.1

[Doug Torrance]

Control: tags 784702 + pending

Dear maintainer,

I've prepared an NMU for wmweather+ (versioned as 2.15-1.1) and
have asked my sponsor to upload it to DELAYED/2. Please feel free
to tell me if I should delay it longer.

Regards.
diff -Nru wmweather+-2.15/debian/changelog wmweather+-2.15/debian/changelog
--- wmweather+-2.15/debian/changelog	2014-10-31 14:33:32.0 -0500
+++ wmweather+-2.15/debian/changelog	2015-05-19 18:56:59.0 -0500
@@ -1,3 +1,12 @@
+wmweather+ (2.15-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control:
+- Switch libwraster3-dev in Build-Depends to libwraster-dev
+  (Closes: #784702).
+
+ -- Doug Torrance dtorra...@monmouthcollege.edu  Tue, 19 May 2015 18:55:55 -0500
+
 wmweather+ (2.15-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru wmweather+-2.15/debian/control wmweather+-2.15/debian/control
--- wmweather+-2.15/debian/control	2014-11-05 08:32:10.0 -0600
+++ wmweather+-2.15/debian/control	2015-05-19 18:55:03.0 -0500
@@ -2,7 +2,7 @@
 Section: x11
 Priority: optional
 Maintainer: Martin Stigge mar...@stigge.org
-Build-Depends: libpcre3-dev, libcurl4-gnutls-dev, libwraster3-dev, debhelper (= 9)
+Build-Depends: libpcre3-dev, libcurl4-gnutls-dev, libwraster-dev, debhelper (= 9)
 Standards-Version: 3.9.6
 Vcs-Browser: http://anonscm.debian.org/viewvc/collab-maint/deb-maint/wmweather%2B/
 Vcs-Svn: svn://anonscm.debian.org/collab-maint/deb-maint/wmweather+/

Bug#784701: Should Build-Depend on libwraster-dev.

[Doug Torrance]

Package: wdm
Version: 1.28-17
Severity: serious
Tags: patch

Beginning with wmaker version 0.95.6-1, libwraster3-dev has been renamed to
libwraster-dev.  As this is a build dependency of wdm, debian/control should
be updated accordingly.
diff --git a/debian/control b/debian/control
index 2342db0..38ac52f 100644
--- a/debian/control
+++ b/debian/control
@@ -14,7 +14,7 @@ Build-Depends: debhelper (= 9~),
libpng-dev,
libselinux1-dev [linux-any],
libwings-dev,
-   libwraster3-dev,
+   libwraster-dev,
libx11-dev,
libxau-dev,
libxdmcp-dev,

Bug#784702: wmweather+: Should Build-Depend on libwraster-dev.

[Doug Torrance]

Package: wmweather+
Version: 2.15-1
Severity: serious
Tags: patch
Justification: Policy 4.2

Beginning with wmaker version 0.95.6-1, libwraster3-dev has been renamed to
libwraster-dev.  As this is a build dependency of wdm, debian/control should
be updated accordingly.
diff --git a/debian/control b/debian/control
index 4be3317..c1cf0ac 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: wmweather+
 Section: x11
 Priority: optional
 Maintainer: Martin Stigge mar...@stigge.org
-Build-Depends: libpcre3-dev, libcurl4-gnutls-dev, libwraster3-dev, debhelper (= 9)
+Build-Depends: libpcre3-dev, libcurl4-gnutls-dev, libwraster-dev, debhelper (= 9)
 Standards-Version: 3.9.6
 Vcs-Browser: http://anonscm.debian.org/viewvc/collab-maint/deb-maint/wmweather%2B/
 Vcs-Svn: svn://anonscm.debian.org/collab-maint/deb-maint/wmweather+/