Bug#816577: src:python-attrs: please add dependency “Suggests: python-attr-doc”

2016-03-03 Thread Ben Finney
Package: src:python-attrs
Version: 15.2.0-1
Severity: minor

Dear Maintainer,

Working with the ‘python-attrs’ packages requires understanding how
they work and what they do.

Please set a “Suggests: python-attr-doc” dependency to the library
packages, so that administrators choosing to install those will
receive the suggestion.

-- 
 \  “The trouble with the rat race is that even if you win, you're |
  `\   still a rat.” —Jane Wagner, via Lily Tomlin |
_o__)  |
Ben Finney 



Bug#816578: twitterwatch: Section should be “net”

2016-03-03 Thread Ben Finney
Package: twitterwatch
Version: 0.1-1
Severity: minor

Dear Maintainer,

The section “python” is for packages that install the Python
programming language or libraries. Its packages are primarily of
interest only to Python programmers.

The package ‘twitterwatch’ installs primarily an application of
interest regardless of the programming language. It should not be in
the “python” section.

By the section descriptions, this package belongs in section
“net”.

Please set the field “Section” appropriately on this package.


Since the package is already in Debian under a different section, you
will also need to submit a request to override the existing section
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#override-file>,
and then mark this bug report as blocked by that one.

-- 
 \ “We are human only to the extent that our ideas remain humane.” |
  `\  —_Breakfast of Champions_, Kurt Vonnegut |
_o__)  |
Ben Finney 



Bug#784070: mdadm Software RAID1 with GPT on Debian 8.0.0 amd64 - Does not mount/boot on disk removal

2016-03-03 Thread Sandro Tosi
(resending now that the bug is unarchived, sorry for duplicates)

this bug was fixed in 3.3.4-1.1 but the 3.4-1 upload didnt acknowledge
the NMU, so the patch is lost (it is not present in
https://anonscm.debian.org/cgit/pkg-mdadm/mdadm.git/tree/debian/patches)
- please either integrate the patch from the NMU or implement a
different solution with the same result.

this is, and remains, a critical bug.

Thanks for maintaining mdadm!



Bug#816583: kodi-pvr-wmc: FTBFS: error: 'PVR_ADDON_CAPABILITIES {aka struct PVR_ADDON_CAPABILITIES}' has no member named 'bSupportsRecordingFolders'

2016-03-03 Thread Chris Lamb
Source: kodi-pvr-wmc
Version: 0.5.8+git20150717-1
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,

kodi-pvr-wmc fails to build from source in unstable/amd64:

  [..]

  [ 14%] Building CXX object CMakeFiles/pvr.wmc.dir/src/client.cpp.o
  /usr/bin/c++   -DBUILD_KODI_ADDON -DTARGET_LINUX -DTARGET_POSIX -DUSE_DEMUX 
-D_LINUX -Dpvr_wmc_EXPORTS -I/usr/include/kodi -I/usr/include/cec-platform  -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu++11 -flto -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/pvr.wmc.dir/src/client.cpp.o -c 
/home/lamby/temp/cdt.20160303080500.RHbdt4ZGYZ/kodi-pvr-wmc-0.5.8+git20150717/src/client.cpp
  
/home/lamby/temp/cdt.20160303080500.RHbdt4ZGYZ/kodi-pvr-wmc-0.5.8+git20150717/src/client.cpp:
 In function 'PVR_ERROR GetAddonCapabilities(PVR_ADDON_CAPABILITIES*)':
  
/home/lamby/temp/cdt.20160303080500.RHbdt4ZGYZ/kodi-pvr-wmc-0.5.8+git20150717/src/client.cpp:331:18:
 error: 'PVR_ADDON_CAPABILITIES {aka struct PVR_ADDON_CAPABILITIES}' has no 
member named 'bSupportsRecordingFolders'
 pCapabilities->bSupportsRecordingFolders = false;
^
  CMakeFiles/pvr.wmc.dir/build.make:65: recipe for target 
'CMakeFiles/pvr.wmc.dir/src/client.cpp.o' failed
  make[3]: *** [CMakeFiles/pvr.wmc.dir/src/client.cpp.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160303080500.RHbdt4ZGYZ/kodi-pvr-wmc-0.5.8+git20150717/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:102: recipe for target 'CMakeFiles/pvr.wmc.dir/all' 
failed
  make[2]: *** [CMakeFiles/pvr.wmc.dir/all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160303080500.RHbdt4ZGYZ/kodi-pvr-wmc-0.5.8+git20150717/obj-x86_64-linux-gnu'
  Makefile:152: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160303080500.RHbdt4ZGYZ/kodi-pvr-wmc-0.5.8+git20150717/obj-x86_64-linux-gnu'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


kodi-pvr-wmc.0.5.8+git20150717-1.unstable.amd64.log.txt.gz
Description: Binary data


Bug#816582: kodi-pvr-vuplus: FTBFS: client.cpp:339:18: error: 'PVR_ADDON_CAPABILITIES {aka struct PVR_ADDON_CAPABILITIES}' has no member named 'bSupportsRecordingFolders'

2016-03-03 Thread Chris Lamb
Source: kodi-pvr-vuplus
Version: 1.10.7+git20150717-1
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,

kodi-pvr-vuplus fails to build from source in unstable/amd64:

  [..]

  
/home/lamby/temp/cdt.20160303080444.gZ68UazG2P/kodi-pvr-vuplus-1.10.7+git20150717/src/client.cpp:
 In function 'PVR_ERROR GetAddonCapabilities(PVR_ADDON_CAPABILITIES*)':
  
/home/lamby/temp/cdt.20160303080444.gZ68UazG2P/kodi-pvr-vuplus-1.10.7+git20150717/src/client.cpp:339:18:
 error: 'PVR_ADDON_CAPABILITIES {aka struct PVR_ADDON_CAPABILITIES}' has no 
member named 'bSupportsRecordingFolders'
 pCapabilities->bSupportsRecordingFolders   = true;
^
  CMakeFiles/pvr.vuplus.dir/build.make:65: recipe for target 
'CMakeFiles/pvr.vuplus.dir/src/client.cpp.o' failed
  make[3]: *** [CMakeFiles/pvr.vuplus.dir/src/client.cpp.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160303080444.gZ68UazG2P/kodi-pvr-vuplus-1.10.7+git20150717/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:102: recipe for target 'CMakeFiles/pvr.vuplus.dir/all' 
failed
  make[2]: *** [CMakeFiles/pvr.vuplus.dir/all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160303080444.gZ68UazG2P/kodi-pvr-vuplus-1.10.7+git20150717/obj-x86_64-linux-gnu'
  Makefile:152: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160303080444.gZ68UazG2P/kodi-pvr-vuplus-1.10.7+git20150717/obj-x86_64-linux-gnu'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


kodi-pvr-vuplus.1.10.7+git20150717-1.unstable.amd64.log.txt.gz
Description: Binary data


Bug#816579: arachne-pnr: FTBFS: src/chipdb.cc:852: void ChipDB::finalize(): Assertion `tile_pos_cell[t][pos] == 0' failed.

2016-03-03 Thread Chris Lamb
Source: arachne-pnr
Version: 0~20150927gitefdb026-2
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,

arachne-pnr fails to build from source in unstable/amd64:

  [..]

  g++ -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security 
-Isrc -std=c++11 -Wall -Wshadow -Wsign-compare -Werror -fPIE -pie -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed -o bin/arachne-pnr src/arachne-pnr.o src/netlist.o 
src/blif.o src/pack.o src/place.o src/util.o src/io.o src/route.o src/chipdb.o 
src/location.o src/configuration.o src/line_parser.o src/pcf.o src/global.o 
src/constant.o src/designstate.o -lm
  mkdir -p share/arachne-pnr
  bin/arachne-pnr -d 1k -c /usr/share/fpga-icestorm/chipdb/chipdb-1k.txt 
--write-binary-chipdb share/arachne-pnr/chipdb-1k.bin
  seed: 1
  device: 1k
  read_chipdb /usr/share/fpga-icestorm/chipdb/chipdb-1k.txt...
  arachne-pnr: src/chipdb.cc:852: void ChipDB::finalize(): Assertion 
`tile_pos_cell[t][pos] == 0' failed.
  Makefile:25: recipe for target 'share/arachne-pnr/chipdb-1k.bin' failed
  make[1]: *** [share/arachne-pnr/chipdb-1k.bin] Aborted (core dumped)
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160303075549.jMwsadjjqr/arachne-pnr-0~20150927gitefdb026'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:11: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


arachne-pnr.0~20150927gitefdb026-2.unstable.amd64.log.txt.gz
Description: Binary data


Bug#816581: kodi-pvr-mythtv: FTBFS: error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'

2016-03-03 Thread Chris Lamb
Source: kodi-pvr-mythtv
Version: 2.8.0+git20151119-1
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,

kodi-pvr-mythtv fails to build from source in unstable/amd64:

  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:
 In member function 'PVR_ERROR PVRClientMythTV::GetTimers(ADDON_HANDLE)':
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1523:11:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
 tag.bIsRepeating = meta.isRepeating;
 ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1534:11:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
 tag.bIsRepeating = false;
 ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1614:9:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
   tag.bIsRepeating = false;
   ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:
 In member function 'MythRecordingRule 
PVRClientMythTV::PVRtoMythRecordingRule(const PVR_TIMER&)':
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1736:13:
 error: 'const PVR_TIMER {aka const struct PVR_TIMER}' has no member named 
'bIsRepeating'
 if (timer.bIsRepeating)
   ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:
 In member function 'PVR_ERROR PVRClientMythTV::UpdateTimer(const PVR_TIMER&)':
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1848:20:
 error: 'struct PVR_TIMER' has no member named 'bIsRepeating'
 if (old->second->bIsRepeating && !newTimer.bIsRepeating)
  ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1848:46:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
 if (old->second->bIsRepeating && !newTimer.bIsRepeating)
^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1850:14:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
   newTimer.bIsRepeating = true;
^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1856:20:
 error: 'struct PVR_TIMER' has no member named 'bIsRepeating'
 if (old->second->bIsRepeating != newTimer.bIsRepeating || 
old->second->iWeekdays != newTimer.iWeekdays)
  ^
  
/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/src/pvrclient-mythtv.cpp:1856:45:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
 if (old->second->bIsRepeating != newTimer.bIsRepeating || 
old->second->iWeekdays != newTimer.iWeekdays)
   ^
  CMakeFiles/pvr.mythtv.dir/build.make:449: recipe for target 
'CMakeFiles/pvr.mythtv.dir/src/pvrclient-mythtv.cpp.o' failed
  make[3]: *** [CMakeFiles/pvr.mythtv.dir/src/pvrclient-mythtv.cpp.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:102: recipe for target 'CMakeFiles/pvr.mythtv.dir/all' 
failed
  make[2]: *** [CMakeFiles/pvr.mythtv.dir/all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/obj-x86_64-linux-gnu'
  Makefile:152: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160303080359.w2w1oozu0F/kodi-pvr-mythtv-2.8.0+git20151119/obj-x86_64-linux-gnu'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:15: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


kodi-pvr-mythtv.2.8.0+git20151119-1.unstable.amd64.log.txt.gz
Description: Binary data


Bug#816585: opensp: FTBFS: ! LaTeX Error: File `ulem.sty' not found.

2016-03-03 Thread Chris Lamb
Source: opensp
Version: 1.5.2-13
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,

opensp fails to build from source in unstable/amd64:

  [..]

  (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/marvosym/marvosym.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)))
  (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)
  
  ! LaTeX Error: File `ulem.sty' not found.
  
  Type X to quit or  to proceed,
  or enter new name. (Default extension: sty)
  
  Enter file name: 
  ! Emergency stop.
   
   
  l.27 \RequirePackage
  {fancyhdr}^^M
  !  ==> Fatal error occurred, no output PDF file produced!
  Transcript written on pdfjadetex.log.
  mktexfmt [ERROR]: running `pdftex -ini   -jobname=pdfjadetex 
-progname=pdfjadetex *pdfjadetex.ini >&2 &2 

opensp.1.5.2-13.unstable.amd64.log.txt.gz
Description: Binary data


Bug#816584: libraw1394: FTBFS: ! LaTeX Error: File `ulem.sty' not found.

2016-03-03 Thread Chris Lamb
Source: libraw1394
Version: 2.1.1-2
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,

libraw1394 fails to build from source in unstable/amd64:

  [..]

  (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/color.cfg)
  (/usr/share/texlive/texmf-dist/tex/latex/pdftex-def/pdftex.def
  (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
  (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)))
  (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/marvosym/marvosym.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)))
  (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)
  
  ! LaTeX Error: File `ulem.sty' not found.
  
  Type X to quit or  to proceed,
  or enter new name. (Default extension: sty)
  
  Enter file name: 
  ! Emergency stop.
   
   
  l.27 \RequirePackage
  {fancyhdr}^^M
  !  ==> Fatal error occurred, no output PDF file produced!
  Transcript written on pdfjadetex.log.
  mktexfmt [ERROR]: running `pdftex -ini   -jobname=pdfjadetex 
-progname=pdfjadetex *pdfjadetex.ini >&2 &2 

libraw1394.2.1.1-2.unstable.amd64.log.txt.gz
Description: Binary data


Bug#816496: ITP: pycodestyle -- Python code style checker

2016-03-03 Thread Daniel Stender
I'll go for it, Prospector is going to need this.

DS

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/



Bug#816580: kodi-pvr-dvbviewer: FTBFS: DvbData.cpp:301:9: error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'

2016-03-03 Thread Chris Lamb
Source: kodi-pvr-dvbviewer
Version: 1.10.35+git20150717-1
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,

kodi-pvr-dvbviewer fails to build from source in unstable/amd64:

  
/home/lamby/temp/cdt.20160303080342.kJYepBFIIF/kodi-pvr-dvbviewer-1.10.35+git20150717/src/DvbData.cpp:
 In member function 'bool Dvb::GetTimers(ADDON_HANDLE)':
  
/home/lamby/temp/cdt.20160303080342.kJYepBFIIF/kodi-pvr-dvbviewer-1.10.35+git20150717/src/DvbData.cpp:301:9:
 error: 'PVR_TIMER {aka struct PVR_TIMER}' has no member named 'bIsRepeating'
   tag.bIsRepeating  = (timer->weekdays != 0);
   ^
  CMakeFiles/pvr.dvbviewer.dir/build.make:89: recipe for target 
'CMakeFiles/pvr.dvbviewer.dir/src/DvbData.cpp.o' failed
  make[3]: *** [CMakeFiles/pvr.dvbviewer.dir/src/DvbData.cpp.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160303080342.kJYepBFIIF/kodi-pvr-dvbviewer-1.10.35+git20150717/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:102: recipe for target 
'CMakeFiles/pvr.dvbviewer.dir/all' failed
  make[2]: *** [CMakeFiles/pvr.dvbviewer.dir/all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160303080342.kJYepBFIIF/kodi-pvr-dvbviewer-1.10.35+git20150717/obj-x86_64-linux-gnu'
  Makefile:152: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160303080342.kJYepBFIIF/kodi-pvr-dvbviewer-1.10.35+git20150717/obj-x86_64-linux-gnu'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


kodi-pvr-dvbviewer.1.10.35+git20150717-1.unstable.amd64.log.txt.gz
Description: Binary data


Bug#816586: ruby-riddle: FTBFS: sphinx.rb:28:in `setup_mysql': uninitialized constant Sphinx::Mysql2 (NameError)

2016-03-03 Thread Chris Lamb
Source: ruby-riddle
Version: 1.5.12-2
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,

ruby-riddle fails to build from source in unstable/amd64:

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/debian/ruby-riddle/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-riddle/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*_spec.rb
  
/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/spec/support/sphinx.rb:28:in
 `setup_mysql': uninitialized constant Sphinx::Mysql2 (NameError)
from 
/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/spec/spec_helper.rb:11:in
 `block in '
from /usr/lib/ruby/vendor_ruby/rspec/core.rb:97:in `configure'
from 
/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/spec/spec_helper.rb:7:in
 `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from 
/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/spec/riddle_spec.rb:1:in
 `'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in 
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in 
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in 
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in 
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in `invoke'
from /usr/bin/rspec:4:in `'
  /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*_spec.rb failed
  ERROR: Test "ruby2.3" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160303080938.TbUuhLfL1p/ruby-riddle-1.5.12/debian/ruby-riddle
 returned exit code 1
  debian/rules:16: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


ruby-riddle.1.5.12-2.unstable.amd64.log.txt.gz
Description: Binary data


Bug#811474: Bug #811474 - libreoffice-calc: LibreOffice Calc forces workspace switch when its window is acted on

2016-03-03 Thread David Guyot
Good morning, Stéphane.

The problem seeems to have vanished with the backports version. Great!
Thank you for the suggestion, I didn't think about this.

Regards.

Le mercredi 02 mars 2016 à 22:56 +0100, Stéphane Aulery a écrit :
> Hello David,
> 
> Can you test with version 1:5.0.5~rc2-1~bpo8+2 of LO?
> 
> LO devs refuse to receive bug report for an old version.
> 
> Regards,
> 

-- 
David Guyot
Administrateur système, réseau et télécom / Sysadmin
Europe Camions Interactive / Stockway
Moulin Collot
F-88500 Ambacourt
03 29 30 47 85


signature.asc
Description: This is a digitally signed message part


Bug#816587: shared-mime-info: FTBFS: LaTeX Error: File `ulem.sty' not found.

2016-03-03 Thread Chris Lamb
Source: shared-mime-info
Version: 1.5-2
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,

shared-mime-info fails to build from source in unstable/amd64:

  [..]

  (/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty
  (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/color.cfg)
  (/usr/share/texlive/texmf-dist/tex/latex/pdftex-def/pdftex.def
  (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
  (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)))
  (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/marvosym/marvosym.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)))
  (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)
  
  ! LaTeX Error: File `ulem.sty' not found.
  
  Type X to quit or  to proceed,
  or enter new name. (Default extension: sty)
  
  Enter file name: 
  ! Emergency stop.
   
   
  l.27 \RequirePackage
  {fancyhdr}^^M
  !  ==> Fatal error occurred, no output PDF file produced!
  Transcript written on pdfjadetex.log.
  mktexfmt [ERROR]: running `pdftex -ini   -jobname=pdfjadetex 
-progname=pdfjadetex *pdfjadetex.ini >&2 &2 

shared-mime-info.1.5-2.unstable.amd64.log.txt.gz
Description: Binary data


Bug#816588: siproxd: FTBFS: LaTeX Error: File `ulem.sty' not found.

2016-03-03 Thread Chris Lamb
Source: siproxd
Version: 1:0.8.1-4.1
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,

siproxd fails to build from source in unstable/amd64:

  [..]

  (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
  (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)))
  (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/marvosym/marvosym.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
  (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
  (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)))
  (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty)
  
  ! LaTeX Error: File `ulem.sty' not found.
  
  Type X to quit or  to proceed,
  or enter new name. (Default extension: sty)
  
  Enter file name: 
  ! Emergency stop.
   
   
  l.27 \RequirePackage
  {fancyhdr}^^M
  !  ==> Fatal error occurred, no output PDF file produced!
  Transcript written on pdfjadetex.log.
  mktexfmt [ERROR]: running `pdftex -ini   -jobname=pdfjadetex 
-progname=pdfjadetex *pdfjadetex.ini >&2 &2 

siproxd.1:0.8.1-4.1.unstable.amd64.log.txt.gz
Description: Binary data


Bug#687172: Fontconfig file warnings for fonts-sil-andika in Jessie

2016-03-03 Thread Petter Reinholdtsen

The problem with the fontconfig warning about 65-andika.conf is fixed in
unstable, but still exist in stable.  Is it OK if I request a stable
update of fonts-sil-andika?  The attached patch show what I believe is
needed to fix the issue.

I've requested membership in the alioth group and can push a git branch
with these changes, if there is any interest.

-- 
Happy hacking
Petter Reinholdtsen
diff --git a/debian/changelog b/debian/changelog
index 0e319e6..9271605 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+fonts-sil-andika (1.004-2+deb8u1) stable; urgency=low
+
+  * Backport fix from unstable.
+  * really remove 65-andika.conf, Closes: #768232
+  delete d/links with useless symlink
+  d/maintscript to remove 65-andika.conf
+
+ -- Petter Reinholdtsen   Thu, 03 Mar 2016 09:37:43 +0100
+
 fonts-sil-andika (1.004-2) unstable; urgency=low
 
   * Drop the now useless 65-andika.conf fontconfig file
diff --git a/debian/links b/debian/links
deleted file mode 100644
index afe457e..000
--- a/debian/links
+++ /dev/null
@@ -1 +0,0 @@
-etc/fonts/conf.avail/65-andika.conf etc/fonts/conf.d/65-andika.conf
diff --git a/debian/maintscript b/debian/maintscript
new file mode 100644
index 000..0a5f689
--- /dev/null
+++ b/debian/maintscript
@@ -0,0 +1 @@
+rm_conffile /etc/fonts/conf.avail/65-andika.conf 1.004-2~ fonts-sil-andika


Bug#816587: shared-mime-info: FTBFS: LaTeX Error: File `ulem.sty' not found.

2016-03-03 Thread Sebastian Dröge
On Do, 2016-03-03 at 08:36 +, Chris Lamb wrote:
> Source: shared-mime-info
> Version: 1.5-2
> 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,
> 
> shared-mime-info fails to build from source in unstable/amd64:

Yes, for whatever reason texlive-generic-recommended is not
automatically pulled in anymore. Should check first if this was
intentional.

signature.asc
Description: This is a digitally signed message part


Bug#815413: fixed in libu2f-host 1.0.0-1.1

2016-03-03 Thread Simon Josefsson
Hi Neil.  Thank you for this!  Sorry for not having sufficient time for
this package right now.

/Simon

Neil Williams  writes:

> Source: libu2f-host
> Source-Version: 1.0.0-1.1
>
> We believe that the bug you reported is fixed in the latest version of
> libu2f-host, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 815...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Neil Williams  (supplier of updated libu2f-host package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
> Format: 1.8
> Date: Sun, 21 Feb 2016 11:52:27 +
> Source: libu2f-host
> Binary: libu2f-host0 libu2f-host-dev u2f-host
> Architecture: source
> Version: 1.0.0-1.1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Authentication Maintainers 
> 
> Changed-By: Neil Williams 
> Description:
>  libu2f-host-dev - Development files for the U2F host C library libu2f-host
>  libu2f-host0 - Universal 2nd Factor (U2F) host communication C Library
>  u2f-host   - Command line tool to do Universal 2nd Factor (U2F) operations
> Closes: 815413
> Changes:
>  libu2f-host (1.0.0-1.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* Switch from libjson0-dev to libjson-c-dev (Closes: #815413)
> Checksums-Sha1:
>  0d1dae85b1e2c95b72cb63a4bc5572b53a2bb39f 2217 libu2f-host_1.0.0-1.1.dsc
>  8f769d3540ffd27d63f049ab3dc37fd5a2e9893c 60704 
> libu2f-host_1.0.0-1.1.debian.tar.xz
> Checksums-Sha256:
>  8ddfcfab794f390defb0ad8a21527078bdf9049f13afed1d4824e333c5cdea47 2217 
> libu2f-host_1.0.0-1.1.dsc
>  b47567a1d39e04f0606cfb4fc534931903ce8a1ddc712db14f2e61ebaf772eb4 60704 
> libu2f-host_1.0.0-1.1.debian.tar.xz
> Files:
>  bb9ac75df0cf9e23969dd3fae68bfb7f 2217 utils extra libu2f-host_1.0.0-1.1.dsc
>  027a7b351c1530be830245e16ac49eb4 60704 utils extra 
> libu2f-host_1.0.0-1.1.debian.tar.xz
>


signature.asc
Description: PGP signature


Bug#815413: fixed in libu2f-host 1.0.0-1.1

2016-03-03 Thread Simon Josefsson
Hi Neil.  Thank you for this!  Sorry for not having sufficient time for
this package right now.

/Simon

Neil Williams  writes:

> Source: libu2f-host
> Source-Version: 1.0.0-1.1
>
> We believe that the bug you reported is fixed in the latest version of
> libu2f-host, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 815...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Neil Williams  (supplier of updated libu2f-host package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
> Format: 1.8
> Date: Sun, 21 Feb 2016 11:52:27 +
> Source: libu2f-host
> Binary: libu2f-host0 libu2f-host-dev u2f-host
> Architecture: source
> Version: 1.0.0-1.1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Authentication Maintainers 
> 
> Changed-By: Neil Williams 
> Description:
>  libu2f-host-dev - Development files for the U2F host C library libu2f-host
>  libu2f-host0 - Universal 2nd Factor (U2F) host communication C Library
>  u2f-host   - Command line tool to do Universal 2nd Factor (U2F) operations
> Closes: 815413
> Changes:
>  libu2f-host (1.0.0-1.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* Switch from libjson0-dev to libjson-c-dev (Closes: #815413)
> Checksums-Sha1:
>  0d1dae85b1e2c95b72cb63a4bc5572b53a2bb39f 2217 libu2f-host_1.0.0-1.1.dsc
>  8f769d3540ffd27d63f049ab3dc37fd5a2e9893c 60704 
> libu2f-host_1.0.0-1.1.debian.tar.xz
> Checksums-Sha256:
>  8ddfcfab794f390defb0ad8a21527078bdf9049f13afed1d4824e333c5cdea47 2217 
> libu2f-host_1.0.0-1.1.dsc
>  b47567a1d39e04f0606cfb4fc534931903ce8a1ddc712db14f2e61ebaf772eb4 60704 
> libu2f-host_1.0.0-1.1.debian.tar.xz
> Files:
>  bb9ac75df0cf9e23969dd3fae68bfb7f 2217 utils extra libu2f-host_1.0.0-1.1.dsc
>  027a7b351c1530be830245e16ac49eb4 60704 utils extra 
> libu2f-host_1.0.0-1.1.debian.tar.xz
>


signature.asc
Description: PGP signature


Bug#812184: sg3-utils: /usr/bin/rescan-scsi-bus.sh requires usleep command

2016-03-03 Thread fire
Hi,

i can cofirm the replace-usleep.patch is working. 

How long does it need to get this Bug fixed in stable (Jessie) ?

 
kr

fire

 


Bug#812087: [pcscd]

2016-03-03 Thread Philippe Teuwen
Hi Ludovic,

I'm getting the same problem with my Debian Testing.

I'll try to generate more logs related to libusb as explained in the bug
thread but here are some things I noticed:

I've a Yubikey Neo-n plugged constantly.

When the 100% problem arises, nothing special in pcscd logs, even with
-f -a -d
cf attached log.
And pcscd and Yubikey remain fully functional despite the 100%.

Now the interesting bits:

Without the yubikey inserted the problem never occurs.

With the yubikey inserted there are two cases:

1) works as normal, the problem never arises

2) sometimes when yubikey gets inserted or when pcscd service is
restarted I get the following error in syslog:

pcscd[26168]:  ifdhandler.c:144:CreateChannelByNameOrChannel()
failed
pcscd[26168]: 0012 readerfactory.c:1097:RFInitializeReader() Open
Port 0x20 Failed (usb:1050/0115:libudev:0:/dev/bus/usb/001/025)
pcscd[26168]: 0002 readerfactory.c:372:RFAddReader() Yubico Yubikey
NEO U2F+CCID init failed.

At this point besides those lines in syslog, yubikey is functional and
CPU is ok *but* starting from this situation, whenever there will be a
change on another usb port, no matter what (inserting or removing
anything, even a simple USB hub) => CPU goes to 100%
Restarting pcscd brings CPU back to normal till another USB
insert/remove event.

Cheers
Phil


Package: pcscd
Version: 1.8.15-1

--- Please enter the report below this line. ---


--- System information. ---
Architecture: amd64
Kernel: Linux 4.5.0-rc4-amd64

Debian Release: stretch/sid
900 testing security.debian.org
900 testing ftp.be.debian.org
500 unstable ftp.be.debian.org
500 stable security.debian.org
500 stable ftp.be.debian.org
500 stable dl.google.com
500 debian-stretch apt.dockerproject.org
1 experimental httpredir.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.



 debuglog.c:289:DebugLogSetLevel() debug level=debug
0025 utils.c:82:GetDaemonPid() Can't open /var/run/pcscd/pcscd.pid: No such file or directory
0061 configfile.l:281:DBGetReaderListDir() Parsing conf directory: /etc/reader.conf.d
0139 configfile.l:353:DBGetReaderList() Parsing conf file: /etc/reader.conf.d/libccidtwin
0182 configfile.l:315:DBGetReaderListDir() Skipping non regular file: .
0003 configfile.l:315:DBGetReaderListDir() Skipping non regular file: ..
0004 pcscdaemon.c:567:main() pcsc-lite 1.8.15 daemon ready.
3391 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
0062 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
0070 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x0C45, PID: 0x6713, path: /dev/bus/usb/001/008
0063 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x0C45, PID: 0x6713, path: /dev/bus/usb/001/008
0059 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001
0063 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x1050, PID: 0x0115, path: /dev/bus/usb/001/003
0004 hotplug_libudev.c:433:HPAddDevice() Adding USB device: Yubico Yubikey NEO U2F+CCID
0022 readerfactory.c:1066:RFInitializeReader() Attempting startup of Yubico Yubikey NEO U2F+CCID 00 00 using /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so
0690 readerfactory.c:951:RFBindFunctions() Loading IFD Handler 3.0
0104 ifdhandler.c:1950:init_driver() Driver version: 1.4.22
0357 ifdhandler.c:1967:init_driver() LogLevel: 0x0003
0003 ifdhandler.c:1978:init_driver() DriverOptions: 0x
0084 ifdhandler.c:110:CreateChannelByNameOrChannel() Lun: 0, device: usb:1050/0115:libudev:0:/dev/bus/usb/001/003
0010 ccid_usb.c:284:OpenUSBByName() Using: /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Info.plist
0356 ccid_usb.c:302:OpenUSBByName() ifdManufacturerString: Ludovic Rousseau (ludovic.rouss...@free.fr)
0003 ccid_usb.c:303:OpenUSBByName() ifdProductString: Generic CCID driver
0001 ccid_usb.c:304:OpenUSBByName() Copyright: This driver is protected by terms of the GNU Lesser General Public License version 2.1, or (at your option) any later version.
1842 ccid_usb.c:587:OpenUSBByName() Found interface 1 but expecting 0
0003 ccid_usb.c:589:OpenUSBByName() Wrong interface for USB device 1/3. Checking next one.
0019 ccid_usb.c:729:OpenUSBByName() Device not found?
0002 ifdhandler.c:144:CreateChannelByNameOrChannel() failed
0002 readerfactory.c:1097:RFInitializeReader() Open Port 0x20 Failed (usb:1050/0115:libudev:0:/dev/bus/usb/001/003)
0002 readerfactory.c:372:RFAddReader() Yubico Yubikey NEO U2F+CCID init failed.
0002 readerfactory.c:605:RFRemoveReader() UnrefReader() count was: 1
0002 readerfactory.c:1117:RFUnInitializeReader() Attempting shutdown of Yubico Yub

Bug#816575: libtotem-plparser18: [regression] no longer depends on libquvi after the quvi transition

2016-03-03 Thread Andreas Henriksson
Control: tags -1 + patch

Hello again.

On Thu, Mar 03, 2016 at 01:05:31PM +0800, Paul Wise wrote:
> Package: libtotem-plparser18
> Version: 3.10.6-2
> Severity: important
> X-Debbugs-Cc: Andreas Henriksson , 
> libq...@packages.debian.org
> 
> The quvi transition has broken playing Youtube videos in totem.
[...]

As already mentioned by mbiebl there's no optimal place to put the
videosite helper binary. Discussed possible solutions with him
on IRC and we're now leaning towards the attached patch.

Testing welcome.

Regards,
Andreas Henriksson
Index: debian/changelog
===
--- debian/changelog	(revision 47402)
+++ debian/changelog	(working copy)
@@ -1,3 +1,14 @@
+totem-pl-parser (3.10.6-4) UNRELEASED; urgency=medium
+
+  * debian/rules: set libexecdir to a (multiarched) so-versioned path
+where we install the videosite helper. (Nothing else uses libexecdir.)
+  * debian/libtotem-pl-parser18.install:
+install usr/lib/*/libtotem-plparser*/totem-pl-parser directory
+which contains 99-totem-pl-parser-videosite helper.
+(Closes: #816575)
+
+ -- Andreas Henriksson   Thu, 03 Mar 2016 09:02:03 +0100
+
 totem-pl-parser (3.10.6-2) unstable; urgency=medium
 
   * Upload to unstable. (Closes: #810952)
Index: debian/libtotem-plparser18.install
===
--- debian/libtotem-plparser18.install	(revision 47402)
+++ debian/libtotem-plparser18.install	(working copy)
@@ -1 +1,3 @@
 usr/lib/*/lib*.so.*
+# for videosite helper binary:
+usr/lib/*/libtotem-plparser*/totem-pl-parser
Index: debian/rules
===
--- debian/rules	(revision 47402)
+++ debian/rules	(working copy)
@@ -11,6 +11,7 @@
 DEB_DH_MAKESHLIBS_ARGS_$(libtotem-plparserN) += -V -- -c4
 
 DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
+ --libexecdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)/$(libtotem-plparserN) \
  --enable-gtk-doc
 
 DEB_DH_AUTORECONF_ARGS += ./autogen.sh


Bug#816589: RFP: libconfig-crontab-perl -- Config::Crontab - Read/Write Vixie compatible crontab(5) files

2016-03-03 Thread Dave
Package: wnpp
Severity: wishlist

* Package name: libconfig-crontab-perl
  Version : 1.40
  Upstream Author : Scott Wiersdorf 
  X-Debbugs-CC: debian-p...@lists.debian.org
* URL : https://metacpan.org/pod/Config::Crontab
* License : Perl
  Programming Lang: Perl
  Description : Config::Crontab - Read/Write Vixie compatible crontab(5) 
files

Config::Crontab provides an object-oriented interface to Vixie-style crontab(5) 
files for Perl.

A Config::Crontab object allows you to manipulate an ordered set of Event, Env, 
or Comment objects.

In short, Config::Crontab reads and writes crontab(5) files (and does a little 
pretty-printing too) using objects. The general idea is that you create a 
Config::Crontab object and associate it with a file (if unassociated, it will 
work over a pipe to crontab -l). From there, you can add lines to your crontab 
object, change existing line attributes, and write everything back to file.

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



Bug#743877: ITP: numba -- NumPy-aware optimizing compiler for Python

2016-03-03 Thread Daniel Stender
I'm going to close this bug shortly.

DS

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/



Bug#815001: Causes HP LaserJet 9000 Series printers to crash with error 49.60FF

2016-03-03 Thread Brian Potkin
On Sat 27 Feb 2016 at 14:03:03 +, Brian Potkin wrote:

> On Fri 26 Feb 2016 at 18:10:48 -0500, Ryan Kavanagh wrote:
> 
> > Using the "HP LaserJet 9000 Series pcl3, hpcups 3.16.2 (color, 2-sided
> > printing)" and "HP LaserJet 9050 - CUPS+Gutenprint v5.2.11 (grayscale,
> > 2-sided printing)" and "Local Raw Printer' drivers with lpd:// causes a
> > sheet of paper complaining about attempting to print a binary file to
> > come out (this leads me to believe that the address I have for the
> > printer does not point to the actual printer but to some print server in
> > between, which may be the source of the problem).
> 
> The info sheet you have should have the printer's IP address.
> 
> > This appears to occur for all files, though on the odd occasion, I'll
> > try my luck and manage to print something without killing the printer.
> 
> All three logs have
> 
>   D [26/Feb/2016:17:23:31 -0500] [Job 142] Switching to Poppler\'s  pdftops
> instead of Ghostscript for old HP LaserJet (\"LaserJet \",
> no letters before ) printers to work around bugs in the printer\'s
> PS interpreters
> 
> Please see #742765
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742765
> 
> for the reason this is done.
> 
> About the best I can suggest is to see how you go on with the Ghostscript
> renderer:
> 
>   lpadmin -p  -v lpd://... -E -o pdftops-renderer-default=gs -m 
> 

Any luck with either of these?

Cheers,

Brian.



Bug#743877: ITP: numba -- NumPy-aware optimizing compiler for Python

2016-03-03 Thread Pietro Battiston
Il giorno mar, 15/12/2015 alle 17.53 +0100, Daniel Stender ha scritto:
> Hi Pietro,
> 
> I've got llvmlite in NEW now. I would be interested in maintaining
> Numba, too. Is that
> allright with you?
> 

Sorry Daniel, I had missed your email.

I think the fact that you adopt Numba is just great.

Pietro



Bug#816083: android-platform-build: Please change B-D for the android-platform-frameworks-native transition

2016-03-03 Thread 殷啟聰
Control: tags -1 confirmed

I'm sorry that the transition has affected libpng1.6.

android-sdk-meta being uninstallable does not seem to be the problem
here. The problem is src:android-platform-build still depends on
android-libutils-dev, which is however moved to
src:android-platform-system-core in unstable. Do you know how to
handle this kind of transition that one binary package is moved to
another source package?



Bug#815465: gitlab wiki content doesn't show up

2016-03-03 Thread Johannes Schauer
Hi,

On Thu, 03 Mar 2016 08:30:49 +0100 =?utf-8?b?TGlib3IgS2xlcMOhxI0=?= 
 wrote:
> can you please try this little patch?
> I use it on gitlab 8.3.0 packages from Praveen.

I can confirm that this patch fixes the reported issue in my setup.

Thanks!

cheers, josch


signature.asc
Description: signature


Bug#816590: elpa: still FTBFS on mipsel/powerpc

2016-03-03 Thread Emilio Pozuelo Monfort
Source: elpa
Version: 2015.05.001-6
Severity: serious

Your package failed to build on mipsel/powerpc:

Build killed with signal TERM after 150 minutes of inactivity

Logs at https://buildd.debian.org/status/logs.php?pkg=elpa&ver=2015.05.001-6

Emilio



Bug#743877: ITP: numba -- NumPy-aware optimizing compiler for Python

2016-03-03 Thread Daniel Stender
On 03.03.2016 10:06, Pietro Battiston wrote:
> Il giorno mar, 15/12/2015 alle 17.53 +0100, Daniel Stender ha scritto:
>> Hi Pietro,
>>
>> I've got llvmlite in NEW now. I would be interested in maintaining
>> Numba, too. Is that
>> allright with you?
> 
> Sorry Daniel, I had missed your email.
> 
> I think the fact that you adopt Numba is just great.
> 
> Pietro

O.k. all right!

So, I'm taking over the ownership of this bug.

Best,
Daniel

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/



Bug#813237: transition: ruby2.3

2016-03-03 Thread Emilio Pozuelo Monfort
On 03/03/16 04:52, Antonio Terceiro wrote:
> On Wed, Mar 02, 2016 at 05:10:54PM +0100, Emilio Pozuelo Monfort wrote:
>> On 02/03/16 13:25, Christian Hofstaedtler wrote:
>>> Emilio,
>>>
>>> I think we're quite close to be able to drop 2.2 - it's already in
>>> experimental, we're quite confident it works, etc.
>>>
>>> Right now we know that uwsgi and weechat will need manual fixing and
>>> there are open bugs against them (#816315, #816312).
>>>
>>> When do you think it would be ok for us to drop 2.2? We'll need
>>> another round of binNMUs for all the packages listed on the tracker.
>>> (We're running another test rebuild of those right now.)
>>
>> You can go ahead.
> 
> So I have uploaded ruby-defaults making the switch on unstable earlier
> today. Please binNMU the following packages:
> 
> broccoli-ruby
> geos
> graphviz
> marisa
> ngraph-gtk
> notmuch
> qtruby
> redland-bindings
> ruby-standalone
> rubyluabridge
> subversion
> treil
> vim
> vim-command-t
> libguestfs

Scheduled.

I've also scheduled zeroc-ice as that can be built on the buildds (the bad
packages are in Build-Depends-Indep and the buildds don't install those except
for arch:all builds).

Emilio



Bug#814871: I was able to close

2016-03-03 Thread Johannes Schauer
Hi,

On Thu, 18 Feb 2016 23:41:26 +0530 Pirate Praveen  wrote:
> and reopen the issue though. No comment box here as you reported.

can you attach the upstream bugnumber to this bugreport as "forwarded"?

Maybe I'm able to test fixes upstream proposes to fix this issue.

Thanks!

cheers, josch


signature.asc
Description: signature


Bug#816584: libraw1394: FTBFS: ! LaTeX Error: File `ulem.sty' not found.

2016-03-03 Thread Guus Sliepen
reassign 816584 texlive-htmlxml
thanks

On Thu, Mar 03, 2016 at 08:34:53AM +, Chris Lamb wrote:

> libraw1394 fails to build from source in unstable/amd64:
> 
> [...]
> 
> make[2]: Entering directory 
> '/home/lamby/temp/cdt.20160303080517.0tVkw1XhhH/libraw1394-2.1.1/doc'
> db2pdf libraw1394.sgml
> 
> [...]
> 
> mktexfmt [INFO]: --- remaking pdfjadetex with pdftex mktexfmt:
> running `pdftex -ini   -jobname=pdfjadetex -progname=pdfjadetex 
> *pdfjadetex.ini' ...
> 
> [...]
> 
> ! LaTeX Error: File `ulem.sty' not found.

I believe the error is in the texlive-htmlxml package; if it depends on
ulem.sty, it should depend on texlive-generic-recommended.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature


Bug#816591: RFA: python-xmp-toolkit -- XMP library for Python

2016-03-03 Thread Daniel Stender
Package: wnpp
Severity: normal

If somebody would like to take owner the maintenance of this package that's all
right with me.

Best,
DS

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/



signature.asc
Description: OpenPGP digital signature


Bug#816592: RFA: vcr.py -- Python library to record and replay HTML interactions

2016-03-03 Thread Daniel Stender
Package: wnpp
Severity: normal

If somebody wants to take over the maintenance of this package that's all right 
with
me.

Thanks,
DS

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/



signature.asc
Description: OpenPGP digital signature


Bug#814600: android-tools: B-D on obsolete android-system-dev

2016-03-03 Thread 殷啟聰
Anyone is fixing this bug? Having my tips it shouldn't be hard to fix.
I believe this bug is currently stopping
src:android-platform-system-core from getting into testing. We should
either fix this bug or remove this package ASAP. See
.



Bug#816497: aptitude: problems with (un)markauto

2016-03-03 Thread Jörg-Volker Peetz
Hi Manual,

Manuel A. Fernandez Montecelo wrote on 03/03/16 02:57:
> Control: tags -1 + moreinfo
> 
> 
> Hi Jörg,
> 

> 
> Seems to work fine around here:
> 
>  # aptitude -F '%M %p' search '~n^gnupg2$~ramd64'
>  A gnupg2
> 
>  # aptitude markauto '~n^gnupg2$~ramd64'
>  No packages will be installed, upgraded, or removed.
>  0 packages upgraded, 0 newly installed, 0 to remove and 92 not upgraded.
>  Need to get 0 B of archives. After unpacking 0 B will be used.
> 
>  # aptitude -F '%M %p' search '~n^gnupg2$~ramd64'
>  A gnupg2
> 
>  # aptitude unmarkauto '~n^gnupg2$~ramd64'
>  No packages will be installed, upgraded, or removed.
>  0 packages upgraded, 0 newly installed, 0 to remove and 92 not upgraded.
>  Need to get 0 B of archives. After unpacking 0 B will be used.
> 
>  # aptitude -F '%M %p' search '~n^gnupg2$~ramd64'
>gnupg2
> 
thanks for looking into this. I should've been more specific.

On my system the output stays unchanged and always says:

# aptitude -F '%M %p' search '~n^gnupg2$~ramd64'
A gnupg2

And I think the difference is that on my system the package gnupg2 has the
additional new attribute "Auto-New-Install" set to "yes" in the file
/var/lib/aptitude/pkgstates.
Indeed, for any package with this new attribute in var/lib/aptitude/pkgstates
"aptitude (un)markauto" doesn't work.
For a package without this new attribute "(un)markauto" still works here.

Regarding the interaction between aptitude and apt-mark, I thought that at least
the (un)markauto actions of aptitude were written to the apt database.

Best regards,
Jörg-Volker.



Bug#816497: aptitude: problems with (un)markauto

2016-03-03 Thread Jörg-Volker Peetz
Hi Manuel,

sorry for the typo in your name. I just realized when I had sent the previous
e-mail.

Best regards,
Jörg-Volker.



Bug#810947: kwin-x11: iceweasel locks up when multiple windows restored

2016-03-03 Thread Arthur Marsh
Package: kwin-x11
Version: 4:5.5.4-2
Followup-For: Bug #810947

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

After latest updates in unstable, had 3 attempts now in a row of logging into
a plasma session, restarting iceweasel and experiencing a kwin_x11 lock-up.

Currently using Plastik window decoration theme, will test with org.kde.breeze 
next.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-rc6+ (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages kwin-x11 depends on:
ii  kwin-common  4:5.5.4-2
ii  libc62.21-9
ii  libkf5i18n5  5.16.0-1
ii  libkf5windowsystem5  5.16.0-1
ii  libqt5core5a 5.5.1+dfsg-14
ii  libqt5gui5   5.5.1+dfsg-14
ii  libqt5widgets5   5.5.1+dfsg-14
ii  libqt5x11extras5 5.5.1-3
ii  libstdc++6   6-20160220-1
ii  libxcb1  1.11.1-1

kwin-x11 recommends no packages.

kwin-x11 suggests no packages.

-- debconf-show failed



Bug#810947: kwin-x11: iceweasel locks up when multiple windows restored

2016-03-03 Thread Arthur Marsh
Package: kwin-x11
Version: 4:5.5.4-2
Followup-For: Bug #810947

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

When using Plastik window decoration, kwin_x11 locks up when iceweasel
restores multiple windows (tried 3 times in a row today).

After setting window decoration to org.kde.breeze and restarting the session,
iceweasel restores without any problems with kwin_x11.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-rc6+ (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages kwin-x11 depends on:
ii  kwin-common  4:5.5.4-2
ii  libc62.21-9
ii  libkf5i18n5  5.16.0-1
ii  libkf5windowsystem5  5.16.0-1
ii  libqt5core5a 5.5.1+dfsg-14
ii  libqt5gui5   5.5.1+dfsg-14
ii  libqt5widgets5   5.5.1+dfsg-14
ii  libqt5x11extras5 5.5.1-3
ii  libstdc++6   6-20160220-1
ii  libxcb1  1.11.1-1

kwin-x11 recommends no packages.

kwin-x11 suggests no packages.

-- debconf-show failed



Bug#816520: aptitude: apt "fancy" progress bar does not work anymore with recent aptitude versions

2016-03-03 Thread Antonio Ospite
On Wed, 2 Mar 2016 23:29:27 +
"Manuel A. Fernandez Montecelo"  wrote:

> Control: tags -1 + pending
> 
> 
> Hi Antonio,
> 
> 2016-03-02 14:38 Antonio Ospite:
> >Package: aptitude
> >Version: 0.7.7-1
> >Severity: normal
> >
> >Dear Maintainer,
> >
> >apt has this handy feature of showing a progress bar when installing
> >packages, see [1].
> >
> >AFAIK the feature is enabled by default in recent apt versions but has
> >to be enabled explicitly as described in [1] to work with apt-get and
> >other programs:
> >
> > $ sudo sh -c "echo 'Dpkg::Progress-Fancy \"1\";' > 
> > /etc/apt/apt.conf.d/99progressbar"
> >
> >This used to work with aptitude too.
> >
> >I verified that after the command above aptitude on Jessie (0.6.11-1+b1)
> >shows the fancy progress bar on the terminal when installing packages.
> >
> >However, the progress bar does not seem to show anymore with recent
> >aptitude versions (0.7.5, 0.7.6 or 0.7.7 as confirmed by mafm on IRC).
> >
> >Any idea about what may have made it stop working?
> 
> This will work again now.
> 
> It happened a few versions ago because of adapting aptitude for changes
> in apt 1.1 (deprecated function), and using only one type of progress
> which the old function uses internally.
>

Thanks Manuel,

I can see the fix at:
https://anonscm.debian.org/cgit/aptitude/aptitude.git/commit/?id=f4742858515a75b94db8448f2723cfafc77721cd

Ciao ciao,
   Antonio

-- 
Antonio Ospite
http://ao2.it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?



Bug#816593: iceweasel-38.6.1esr-1~deb7u1: FTBFS on amd64

2016-03-03 Thread matthias.hinkfoth2
Package: iceweasel
Version: 38.6.1esr-1~deb7u1
Source: iceweasel

Dear maintainers,

May be this is stupid, but I tried to build iceweasel from source
on an amd64-machine running wheezy.
I did (from with in a Makefile, therefore an additional level of make):

$ apt-get source iceweasel
$ apt-get build-dep iceweasel
$ cd iceweasel-38.6.1esr
$ dpkg-buildpackage -us -uc

The last command fails.
For readability, I manually shortened the source path to /src/...
Did not help that much, though.

[...]
gcc-4.7 -shared -m64 -Wl,--gc-sections -Wl,-z,defs -Wl,-soname 
-Wl,libnssutil3.so  
-Wl,--version-script,/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/nssutil.def
 -o /src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/libnssutil3.so 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/quickder.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/secdig.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/derdec.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/derenc.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/dersubr.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/dertime.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/errstrs.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/nssb64d.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/nssb64e.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/nssrwlk.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/nssilock.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/oidstring.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/pkcs1sig.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/portreg.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/secalgid.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/secasn1d.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/secasn1e.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/secasn1u.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/secitem.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/secload.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/secoid.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/sectime.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/secport.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/templates.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/utf8.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/utilmod.o 
/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/utilpars.o
-L/src/iceweasel-38.6.1esr/build-browser/dist/lib 
-L/src/iceweasel-38.6.1esr/build-browser/dist/lib -lplc4 -lplds4 -lnspr4  
-lpthread  -ldl -lc
/src/iceweasel-38.6.1esr/build-browser/dist/lib/libnspr4.a(unix.o): In function 
`_PR_UNIX_GetInterval2':
/src/iceweasel-38.6.1esr/nsprpub/pr/src/md/unix/unix.c:3049: undefined 
reference to `clock_gettime'
collect2: error: ld returned 1 exit status
make[8]: *** 
[/src/iceweasel-38.6.1esr/build-browser/security/nss/lib/util/libnssutil3.so] 
Error 1
make[8]: Leaving directory `/src/iceweasel-38.6.1esr/security/nss/lib/util'
make[7]: *** [libs] Error 2
make[7]: Leaving directory `/src/iceweasel-38.6.1esr/security/nss/lib'
make[6]: *** [libs-nss/lib] Error 2
make[6]: Leaving directory 
`/src/iceweasel-38.6.1esr/build-browser/config/external/nss'
make[5]: *** [config/external/nss/target] Error 2
make[5]: Leaving directory `/src/iceweasel-38.6.1esr/build-browser'
make[4]: *** [compile] Error 2
make[4]: Leaving directory `/src/iceweasel-38.6.1esr/build-browser'
make[3]: *** [default] Error 2
make[3]: Leaving directory `/src/iceweasel-38.6.1esr/build-browser'
dh_auto_build: make -j1 _LEAKTEST_FILES=leaktest.py returned exit code 2
make[2]: *** [stamps/build-browser] Error 2
make[2]: Leaving directory `/src/iceweasel-38.6.1esr'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/src/iceweasel-38.6.1esr'
dpkg-buildpackage: error: debian/rules build gave error exit status 2
make: *** [build] Error 2


I am puzzled.
How do you build the package?

Regards,
Matthias



Bug#816594: list.debian.org: Ukrainian FTP server is offline

2016-03-03 Thread Nickolay Ilyushin
Package: list.debian.org
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.3.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Bug#811474: Re : Bug#811474: Bug #811474 - libreoffice-calc: LibreOffice Calc forces workspace switch when its window is acted on

2016-03-03 Thread Stéphane Aulery
fixed 811474 1:5.0.5~rc2-1~bpo8+2
stop
-

Good morning David,

- David Guyot  a écrit :
> 
> The problem seeems to have vanished with the backports version. Great!
> Thank you for the suggestion, I didn't think about this.

Nothing, thanks for yours test. I close this bug.

Regards,

-- 
Stéphane Aulery



Bug#815742: verbiste: diff for NMU version 0.1.42-2.1

2016-03-03 Thread Tomasz Buchert
On 02/03/16 08:05, Raúl Benencia wrote:
> Control: tags 815742 + patch
> Control: tags 815742 + pending
> 
> Dear Tomasz,
> 
> I've prepared an NMU for verbiste (versioned as 0.1.42-2.1). As I don't
> have privileges to upload it to DELAYED, I've uploaded it to the mentors
> repository.
> 
> To access further information about this package, please visit the
> following URL:
> 
>   http://mentors.debian.net/package/verbiste
> 
> Alternatively, one can download the package with dget using this command:
> 
> dget -x 
> http://mentors.debian.net/debian/pool/main/v/verbiste/verbiste_0.1.42-2.1.dsc
> 
> Regards,
> Rul

Hi Raúl,
thank you very much for this! Can you explain what the problem is? I
didn't have time to work on this recently. I'll upload the new version soon.

Cheers,
Tomasz


signature.asc
Description: PGP signature


Bug#816595: pyfits: FTBFS with libcfitsio4

2016-03-03 Thread Mattia Rizzolo
Source: pyfits
Version: 1:3.4-2
Severity: serious

Dear maintainer, during a rebuild for the cfitsio transition your
package FTBFS on all architectures on the buildds:

https://buildd.debian.org/status/logs.php?pkg=pyfits&ver=1%3A3.4-2%2Bb1

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#816596: gtk3 programs segfault in init_randr15 when odd monitors are configured

2016-03-03 Thread chrysn
Package: libgtk-3-0
Version: 3.18.8-1
Severity: important

when odd monitors are configured in xrandr, no gtk3 program can start up
any more, as it segfaults in init_randr15.

i can't pinpoint what "odd monitor" exactly means, but it appears that
it's about xrandr 1.5 monitors (more of an abstraction of what one means
when saying "fullscreen" than actual graphics cards outputs which are
called outputs) that are not 1:1 related to an output.

to reproduce the behavior, i'm executing

$ xrandr --setmonitor foobar 1000/1000x1000/1000+1920+0 none

and then try running any gtk3 application. the offending monitor can be
removed again by running

$ xrandr --delmonitor foobar

. the segfault occurs in gdkscreen-x11.c line 659, where output_info
should be checked for being NULL before accessing the *struct's members.
i didn't find the documentation on XRRGetOutputInfo on whether it can
return NULL without overthrowing the complete protocol, but here it
does, and the output should be checked, but [1] indicated it does.


this issue might now only surface when playing around low-level with
xrandr, but might easily become an issue once the capabilities of xrandr
1.5 are leveraged outside of developer boxes.

best regards
chrysn

[1] 
https://bitbucket.org/portix/srandrd/commits/8b4627f80bd18a247222705da8d1a01dc57e9f35

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc5 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libgtk-3-0 depends on:
ii  libatk-bridge2.0-0  2.18.1-2
ii  libatk1.0-0 2.18.0-1
ii  libc6   2.21-9
ii  libcairo-gobject2   1.14.6-1
ii  libcairo2   1.14.6-1
ii  libcolord2  1.2.12-1
ii  libcups22.1.3-3
ii  libepoxy0   1.3.1-1
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.6.3-3
ii  libgdk-pixbuf2.0-0  2.32.3-1.2
ii  libglib2.0-02.46.2-3
ii  libgtk-3-common 3.18.8-1
ii  libjson-glib-1.0-0  1.0.4-2
ii  libpango-1.0-0  1.38.1-1
ii  libpangocairo-1.0-0 1.38.1-1
ii  libpangoft2-1.0-0   1.38.1-1
ii  librest-0.7-0   0.7.93-1
ii  libsoup2.4-12.52.2-1
ii  libwayland-client0  1.9.0-1
ii  libwayland-cursor0  1.9.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  11.1.2-1
ii  libx11-62:1.6.3-1
ii  libxcomposite1  1:0.4.4-1
ii  libxcursor1 1:1.1.14-1+b1
ii  libxdamage1 1:1.1.4-2+b1
ii  libxext62:1.3.3-1
ii  libxfixes3  1:5.0.1-2+b2
ii  libxi6  2:1.7.6-1
ii  libxinerama12:1.1.3-1+b1
ii  libxkbcommon0   0.5.0-1
ii  libxml2 2.9.3+dfsg1-1
ii  libxrandr2  2:1.5.0-1
ii  shared-mime-info1.5-2

Versions of packages libgtk-3-0 recommends:
ii  libgtk-3-bin  3.18.8-1

Versions of packages libgtk-3-0 suggests:
ii  gvfs 1.26.2-1+b1
ii  librsvg2-common  2.40.13-3

-- no debconf information

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom


signature.asc
Description: PGP signature


Bug#816597: wicd-curses: Wicd crashes on keypress after start AttributeError

2016-03-03 Thread Valentin Heinz
Package: wicd-curses
Version: 1.7.4+tb2-1
Severity: normal

Dear Maintainer,

i started wicd-curses and press "key down". Sometimes wicd crashes with
the following message:


-
vh@box ~ [i] % wicd-curses 
Traceback (most recent call last):
  File "/usr/share/wicd/curses/wicd-curses.py", line 1149, in call_update_ui
self.update_ui(True)
  File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1162, in update_ui
self.handle_keys(input_data)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1131, in handle_keys
k = self.frame.keypress(self.size, k)
  File "/usr/lib/python2.7/dist-packages/urwid/container.py", line 1128, in 
keypress
return self.body.keypress( (maxcol, remaining), key )
  File "/usr/lib/python2.7/dist-packages/urwid/container.py", line 1587, in 
keypress
key = self.focus.keypress(tsize, key)
  File "/usr/lib/python2.7/dist-packages/urwid/decoration.py", line 836, in 
keypress
return self._original_widget.keypress((maxcol,), key)
  File "/usr/share/wicd/curses/wicd-curses.py", line 474, in keypress
key = ComboBox.keypress(self, size, key)
  File "/usr/share/wicd/curses/curses_misc.py", line 497, in keypress
return self._w.keypress(size, key)
  File "/usr/lib/python2.7/dist-packages/urwid/container.py", line 2269, in 
keypress
key = w.keypress((mc,) + size[1:], key)
AttributeError: 'Text' object has no attribute 'keypress'
--

This might be related to #814090.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (950, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wicd-curses depends on:
ii  python-urwid  1.3.1-2
pn  python:any
ii  wicd-daemon   1.7.4+tb2-1

Versions of packages wicd-curses recommends:
ii  sudo  1.8.15-1.1

wicd-curses suggests no packages.

Versions of packages wicd depends on:
ii  wicd-daemon  1.7.4+tb2-1

Versions of packages wicd-cli depends on:
pn  python:any   
ii  wicd-daemon  1.7.4+tb2-1

Versions of packages wicd-cli recommends:
ii  sudo  1.8.15-1.1

Versions of packages wicd-gtk depends on:
ii  python-glade2  2.24.0-4
ii  python-gtk22.24.0-4
pn  python:any 
ii  wicd-daemon1.7.4+tb2-1

Versions of packages wicd-gtk recommends:
ii  gksu   2.0.2-9
ii  python-notify  0.1.1-4

Versions of packages wicd-daemon depends on:
ii  adduser  3.113+nmu3
ii  dbus 1.10.6-1
ii  debconf  1.5.58
ii  ethtool  1:4.2-1
ii  iproute2 4.3.0-1+b1
ii  iputils-ping 3:20121221-5+b2
ii  isc-dhcp-client  4.3.3-8
ii  lsb-base 9.20160110
ii  net-tools1.60+git20150829.73cef8a-2
ii  psmisc   22.21-2.1+b1
ii  python-dbus  1.2.0-3
ii  python-gobject   3.18.2-2
ii  python-wicd  1.7.4+tb2-1
pn  python:any   
ii  wireless-tools   30~pre9-8
ii  wpasupplicant2.3-2.3

Versions of packages wicd-daemon recommends:
ii  rfkill  0.5-1

Versions of packages wicd-daemon suggests:
pn  pm-utils  

Versions of packages python-wicd depends on:
pn  python:any  

-- debconf information:
* wicd/users:



Bug#815931: transition: cfitsio

2016-03-03 Thread Mattia Rizzolo
On Sun, Feb 28, 2016 at 10:22:27PM +0100, Emilio Pozuelo Monfort wrote:
> On 26/02/16 19:17, Aurelien Jarno wrote:
> > Thanks, I have just uploaded the package.
> 
> binNMUs scheduled.

And I uploaded manual binNMUs for wcslib-contrib amd64 and i386.

Though, it won't migrate yet because wookey uploaded once an arm64
binary, but after that time he didn't more.  I'll ask him whether he
wants to continue building this at home at every upload.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#816598: RFP: fonts-crimson-text -- nice true type font

2016-03-03 Thread Petter Reinholdtsen

Package: wnpp
Severity: wishlist
X-Debbugs-CC: pkg-fonts-de...@lists.alioth.debian.org

* Package name: fonts-crimson-text
  Version : 2013.12
  Upstream Author : Sebastian Kosch 
* URL : https://box.aldusleaf.org/crimson.html
https://github.com/skosch/Crimson/
* License : Open Font License
  Programming Lang: n/a
  Description : Nice font for typesetting books

I used this font when a published a book a few months ago, and would
love to have all the tools needed to build the book from its docbook
source in Debian.

There are many versions and sources for this font.  I used the version
available from http://www.fontsquirrel.com/fonts/download/crimson >
for my book, while there is also a version available from
https://github.com/google/fonts/tree/master/ofl/crimsontext >.

-- 
Happy hacking
Petter Reinholdtsen



Bug#781493: Bug #781493 - libreoffice-writer: Page number field does not increment

2016-03-03 Thread Stéphane Aulery
tags 781493 + moreinfo
tags 781493 + upstream
stop
-

Hello David,

Does this bug fits your problem?

 https://bugs.documentfoundation.org/show_bug.cgi?id=34502

Did you make a merge?

Can you test with a newer version please?

Regards,

-- 
Stéphane Aulery



Bug#809848: tag 809848 wontfix

2016-03-03 Thread Benoit Mortier

-- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/



signature.asc
Description: OpenPGP digital signature


Bug#816246:

2016-03-03 Thread Gianfranco Costamagna
control: fixed -1 7.6.6+dfsg-1exp1

Uploading on jessie-backports in 5 days, as soon as boinc 7.6.29 reaches
testing.

feel free to point folks to jessie backports.

cheers,

G.

On Wed, 2 Mar 2016 22:14:22 +0200 Juha  wrote:
> Gianfranco hi,
> 
> 7.4.23 Manager does have a few bugs, such as not updating Task/Project
> panels properly. These bugs were found when 7.4 was still in alpha testing.
> 
> The worst GUI bugs were fixed around 7.4.39-41. It would be nice if you
> could arrange so that a newer version of BOINC is automatically available.
> Even the last 7.4 version would do.
> 
> If Debian policies prevent that then at least please add the latest version
> to backports. In BOINC forums Ubuntu/Mint users are often told to install
> newer BOINC from your PPA but can't do that with Debian :/
> 
> Thanks,
> Juha



signature.asc
Description: OpenPGP digital signature


Bug#726789: milter-manager: changing from ITP to RFP

2016-03-03 Thread Youhei SASAKI
retitle 726789 ITP: milter-manager -- A milter to use milters effectively
owner 726789 !
thanks

On Sun, 27 Dec 2015 21:16:58 +0900,
Lucas Nussbaum  wrote:
> 
> retitle 726789 RFP: milter-manager -- A milter to use milters effectively
> noowner 726789
> tag 726789 - pending
> thanks
> 
> Hi,
> 
> A long time ago, you expressed interest in packaging milter-manager. 
> Unfortunately,
> it seems that it did not happen. In Debian, we try not to keep ITP bugs open
> for a too long time, as it might cause other prospective maintainers to
> refrain from packaging the software.
> 
> This is an automatic email to change the status of milter-manager from ITP
> (Intent to Package) to RFP (Request for Package), because this bug hasn't seen
> any activity during the last 12 months.
> 
> If you are still interested in packaging milter-manager, please send a mail to
>  with:
> 
>  retitle 726789 ITP: milter-manager -- A milter to use milters effectively
>  owner 726789 !
>  thanks
> 
> It is also a good idea to document your progress on this ITP from time to
> time, by mailing <726...@bugs.debian.org>.  If you need guidance on how to
> package this software, please reply to this email, and/or contact the
> debian-ment...@lists.debian.org mailing list.
> 
> Thank you for your interest in Debian,
> -- 
> Lucas, for the QA team 
> 



Bug#809848: closed by Benoit Mortier (Re: fusiondirectory: please provide a gender-neutral 'users' icon)

2016-03-03 Thread IEM - network operating center (IOhannes m zmoelnig)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

hi,

On 2016-03-03 11:03, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report which
> was filed against the fusiondirectory package:
> 
> #809848: fusiondirectory: please provide a gender-neutral 'users'
> icon
> 
> It has been closed by Benoit Mortier
> .
> 
> Their explanation is attached below along with your original
> report. If this explanation is unsatisfactory and you have not
> received a better one in a separate message then please contact
> Benoit Mortier  by replying to this
> email.

thanks for caring about the bug.

however, it is totally unclear how this has been resolved.
- - fusiondirectory_1.0.8.8-3_all.deb still contains the exclusionary
symbol.
- - there hasn't been any upload of a newer version of fusiondirectory.

- - if the problem has been resolved in a newer upstream version (either
released or unreleased), please do not close the Debian bug until this
new version has hit the Debian archive.
tag the bug as "pending" instead.

- - if the problem can be resolved by installing another icon theme,
please say so (and mention a possible package to install).
from your original answer i was under the impression that chosing a
different icon themes won't help because fd explicetly does NOT use a
theme for the very icon this bug-report is about.

- - if you think that the problem is really none and should not be
fixed, you should clearly state this (and probably tag the bug as
"wontfix").

please do not close bugs if they are not resolved.

asdmr
IOhannes




- -- 
IEM - network operation center
mailto:n...@iem.at
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJW2BHbAAoJELZQGcR/ejb4jRcP/1UEcYuY3JJ0KeNKVeiyz5Ia
0Jp/8YV+fJusw3fDaY5w20FNqHif9RLfeqgxwEVAxJ/i8px1EYY+clFd7SYVo5EW
Q6YHE6gfl1d5MYJZMo7JPjwk4rCmveYszYIRT4aAPYN16NGvuHdybuYoMQKDMMy+
gm9zhjZHMb0d68D9fg6gmiTtzpHtahtPJjyFeqSitQuUHvLXALNm31F1Hgtoqp7F
cWVd+FxwZo6CxooIALtkYxgMmrfxL9W6KXYPR/FZlxWK/ezOkrP2s11NKd9V9ugf
HfdqSRmCfiDISKupreTtLCnVEn/1LA7RsmuClVCAItI1howdlLvR0Zo+puJ6BXq7
VozSnRra1bisCW9mhML4GcV2Kayv2xBbZWUt/X/QRP5MMOEh45tOzHSCBx2GWF+5
uZVW0xhplinivvPptwt6bRQOQxob5uBq3z/l6fF5IUHjv/RDtumZsWSs9uGYVkkX
3OC+TIyReC+5cmwlkiL2Fyydr7re8C/Dx1Gpp8KwnomefLBJMvyt/RKi6RRWfDWV
xkxjVPsSAP73wpjDN+264No2WpIIwmpNs4tWY/Lq1hzC3iqUz0+C05IESQ4gRrhp
Pu3rSW/EbLrhj9ktw4W4znHuVuteJgPvPyh5PTvIBXENfs6Pxtwt7Z3OFSc4rdFz
W868dDs/yJ/rS7k97fY4
=6A4C
-END PGP SIGNATURE-



Bug#781087: Bug #781087 - libreoffice-impress: impress animation "strechy" dosn't work with drawings

2016-03-03 Thread Stéphane Aulery
forwarded 781087 https://bugs.documentfoundation.org/show_bug.cgi?id=63443
tags 781087 + upstream
tags 781087 + moreinfo
stop
-

Hello Wolfgang,

I think yours bug is similar to this other bug :

https://bugs.documentfoundation.org/show_bug.cgi?id=63443

Can you send me the output of "lsusb" and "lspci" commands please?

If you can test with a newer version of LO (from backports maybe), it's fine.

Regards,

-- 
Stéphane Aulery



Bug#816599: lintian: false-positive spelling error 'homogenous'

2016-03-03 Thread Debian/GNU
Package: lintian
Version: 2.5.41
Severity: normal

Dear Maintainer,

In one of my packages, lintian reported a spelling error 'homogenous' which
should be fixed to 'homogeneous'.
Not being a native English speaker, I trusted lintian, created a patch and
submitted it upstream, only to get a reply:

> My dictionary (American Heritage) says 'homogenous' is an acceptable spelling
> of 'homogeneous', and it's how I pronounce the word.

So I did a quick check, and Merriam-Webster [1] seems to allow the 'homogenous'
spelling as well.
Other sources [2] even suggest that 'homogenous' is the de-facto spelling of the
word, while the Online Etymology Dictionary - which according to [3] suggested
that this is an 'erroneous spelling of "homogeneous"' - claims in it's current
edition [4] that it is 'a spelling of "homogeneous" that represents a common
pronunciation' (thus accepting the spelling).

I would therefore suggest to consider 'homogenous' to be a false positive and
drop it from the lintian database.

[1] http://www.merriam-webster.com/dictionary/homogenous
[2] http://grammarist.com/usage/homogenous-homogeneous/
[3] http://dictionary.reference.com/browse/homogenous
[4] http://www.etymonline.com/index.php?search=homogenous


-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.26-5
ii  bzip2 1.0.6-8
ii  diffstat  1.61-1
ii  file  1:5.25-2
ii  gettext   0.19.7-2
ii  hardening-includes2.8+nmu2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.29+b5
ii  libarchive-zip-perl   1.56-2
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-1+b1
ii  libdpkg-perl  1.18.4
ii  libemail-valid-perl   1.198-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.413-1+b1
ii  libparse-debianchangelog-perl 1.2.0-8
ii  libperl5.22 [libdigest-sha-perl]  5.22.1-8
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  libyaml-libyaml-perl  0.41-6+b1
ii  man-db2.7.5-1
ii  patchutils0.3.4-1
ii  perl  5.22.1-8
ii  t1utils   1.39-2
ii  xz-utils  5.1.1alpha+20120614-2.1

Versions of packages lintian recommends:
ii  dpkg 1.18.4
ii  libperlio-gzip-perl  0.19-1+b1
ii  perl 5.22.1-8
ii  perl-modules-5.22 [libautodie-perl]  5.22.1-8

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.4
ii  libhtml-parser-perl3.72-1
ii  libtext-template-perl  1.46-1

-- no debconf information



Bug#816600: postinst: IPv6 address is not displayed in 'Start SSH' invitation

2016-03-03 Thread Hendrik Brueckner
Package: network-console
Version: 1.53
Severity: normal
Tags: d-i patch

Dear Maintainer,

in IPv6-only environments, the "Start SSH" invitation does not include
the IPv6 address to log in to the installer system.  Below is a patch
that extends the postinst script to detect an IPv6 address if no IPv4
address could be found.

Thanks and kind regards,
  Hendrik
>From 46f274510e68bc3ce843a14b2c229ab30706d68d Mon Sep 17 00:00:00 2001
From: Hendrik Brueckner 
Date: Thu, 3 Mar 2016 10:51:01 +0100
Subject: [PATCH] network-console: display IPv6 address to access installer 
system

The IP address in the ssh command to log into the installer system
is not display in IPv6-only environments.  Enhance the post install
to detect and display IPv6 addresses if no IPv4 address could be
found.

Signed-off-by: Hendrik Brueckner 
---
 debian/network-console.postinst |7 +++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/debian/network-console.postinst b/debian/network-console.postinst
index f164446..512f121 100755
--- a/debian/network-console.postinst
+++ b/debian/network-console.postinst
@@ -87,6 +87,13 @@ case "$(udpkg --print-os)" in
linux)
IPADDR=$(ip addr | grep '^[[:space:]]*inet ' | grep -v 
"127\.0\." | \
 head -n 1 | sed 's/.*inet \([0-9.]*\).*/\1/')
+
+   if test -z "$IPADDR"; then
+   # Check for an IPv6 address if an IPv4 address
+   # could not be found
+   IPADDR=$(ip addr |grep '^[[:space:]]*inet6 ' | grep -v 
"::1" | \
+head -n 1 | sed 's/.*inet6 
\([a-fA-F0-9:]*\).*/\1/')
+   fi
;;
kfreebsd)
IPADDR=$(ifconfig| grep '^[[:space:]]*inet ' | grep -v 
"127\.0\." | \
-- 
1.7.1



Bug#816590: [Debichem-devel] Bug#816590: elpa: still FTBFS on mipsel/powerpc

2016-03-03 Thread Michael Banck
Hi,

On Thu, Mar 03, 2016 at 10:10:41AM +0100, Emilio Pozuelo Monfort wrote:
> Source: elpa
> Version: 2015.05.001-6
> Severity: serious
> 
> Your package failed to build on mipsel/powerpc:
> 
> Build killed with signal TERM after 150 minutes of inactivity
> 
> Logs at https://buildd.debian.org/status/logs.php?pkg=elpa&ver=2015.05.001-6

Well, yeah.

I've extensively debugged the powerpc issue on a porter box the other
day, and it only hangs if I use more than one MPI process (otherwise it
segfaults unless we use a very small testsuite size). In other news, I
think it's an OpenMPI issue, but the mpi-testsuite package I've uploaded
is still in NEW.

So I've done the following now for ELPA:

 * I've (hopefully) forced mpiexec -n 1 (i.e. one process only) on
   powerpc.

 * I've further reduced the testsuite matrix size from 2000 to 500 on
   mipsel.

Let's see how -7 goes, I've just uploaded it.


Michael



Bug#816542: RFS: connman/1.31-0.1 [RC]

2016-03-03 Thread Gianfranco Costamagna
control: owner -1 !
control: tags -1 moreinfo



Hi Mateusz!

>I am looking for a sponsor for my package "connman"


lets review:


1)
>   * New upstream release (1.31) (Closes: #813580, #813647)



#813647 seems not fixed, according to the upstream commits referenced in RC bug.

http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=acea08a0e4234a4c1a87bedc087c73ff36de0c7b
http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=754cc1678f5c61501299bbde70a73c58d691609b

2) you seem to have changed a previous changelog entry

connman (1.21-1) unstable; urgency=low

-  * New upstream release. (Closes: #688238)
-  * Add myself to the list of uploaders.
-  * Bump Standards Version to 3.9.5 (no changes required).
-  * Build from upstream git:
-- Use dh-autoreconf.
-  * Use init-system-helpers/dh-systemd.
-  * Split off connman-vpn.
-  * Rework descriptions (From Patrik Flykt ).
-  * Also install manpage for connmanctl.
-  * Add patch to remove obsolete After=syslog.target
-from systemd service file:
-- debian/patches/0001-remove-After-syslog.target-obsolete.patch
+  * New upstream release.
+  * Bump Standards Version to 3.9.5 (no changes required)
+  * Build from upstream git
+- Use dh-autoreconf
+  * Use init-system-helpers/dh-systemd
+  * Split off connman-vpn
+  * Rework descriptions (From Patrik Flykt )

-- Shawn Landden   Mon, 10 Feb 2014 19:40:38 -0800


3) std-version is 3.9.7 now


other stuff LGTM, even if it seems a little too much for an NMU, but since most 
work
has been done by an uploader (Shawn), and the package gained 4 NMUs in 2 
uploads, I can
sponsor it if you fix the above.

thanks a lot for the nice work!

Gianfranco



Bug#815734: ess: FTBFS: doc/newfeat.texi:29: Argument of @gobblespaces has an extra }.

2016-03-03 Thread Dirk Eddelbuettel

On 24 February 2016 at 16:21, Kurt Hornik wrote:
| > Dirk Eddelbuettel writes:
| 
| > On 24 February 2016 at 09:48, Chris Lamb wrote:
| > | Source: ess
| > | Version: 15.09.2-1
| > | 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,
| > | 
| > | ess fails to build from source in unstable/amd64:
| > | 
| > |   [..]
| > | 
| > |   LC_ALL=C LANG=en makeinfo --html --no-split 
--css-include=atouchofstyle.css -o html/news.html allnews.texi
| > |   LANG=C texi2dvi --pdf ess.texi
| > |   This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) 
(preloaded format=pdfetex)
| > |restricted \write18 enabled.
| > |   entering extended mode
| > |   (./ess.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
| > |   Loading texinfo [version 2016-02-05.07.deb1]: pdf, fonts, markup, 
glyphs,
| > |   page headings, tables, conditionals, indexing, sectioning, toc, 
environments,
| > |   defuns, macros, cross references, insertions,
| > |   (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
| > |   This is `epsf.tex' v2.7.4 <14 February 2011>
| > |   ) localization, formatting, and turning on texinfo input format.)
| > |   
(/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/ess-defs.texi)
| > |   (../VERSION) [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [-1]
| > |   Chapter 1
| > |   
(/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/currfeat.texi
| > |   [1]) Cross reference values unknown; you must run TeX again. [2]
| > |   
(/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi
| > |   [3]
| > |   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:29:
| > |Argument of @gobblespaces has an extra }.
| > |
| > |   @par 
| > |
| > |  }
| > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| > | @def @temp {#2}@ifx 
@temp ...
| > |   l.1 @acronym{ESS@gobblespaces }
| > |  @texinfoc
| > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| > | @aftermacro 
| > |   l.29 @item @ESS{}
| > |: A test framework has been set up.
| > |   ? Runaway argument?
| > |   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:29:
| > |Paragraph ended before @gobblespaces was complete.
| > |
| > |  @par 
| > |
| > |  }
| > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| > | @def @temp {#2}@ifx 
@temp ...
| > |   l.1 @acronym{ESS@gobblespaces }
| > |  @texinfoc
| > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| > | @aftermacro 
| > |   l.29 @item @ESS{}
| > |: A test framework has been set up.
| > |   ? 
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
| > |Argument of @gobblespaces has an extra }.
| > |
| > |   @par 
| > |
| > |  }
| > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| > | @def @temp {#2}@ifx 
@temp ...
| > |   l.1 @acronym{ESS@gobblespaces @gobblespaces }
| > |@texinfoc
| > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| > | @aftermacro 
| > |   @w #1->@leavevmode @hbox {#1
| > |   }
| > |   ...
| > |   l.72 @item @iESS{}
| > | : For naming inferior processes, ESS can use 
@code{project...
| > |   
| > |   ? 
| > |   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
| > |Emergency stop.
| > |
| > |   @par 
| > |
| > |  }
| > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| > | @def @temp {#2}@ifx 
@temp ...
| > |   l.1 @acronym{ESS@gobblespaces @gobblespaces }
| > |@texinfoc
| > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| > | @aftermacro 
| > |   @w #1->@leavevmode @hbox {#1
| > |   }
| > |   ...
| > |   l.72 @item @iESS{}
| > | : For naming inferior processes, ESS can use 
@code{project...
| > |   
| > |   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
| > | ==> Fatal error occurred, no output PDF file produced!
| > |   Transcript written on ess.log.
| > |   /usr

Bug#816590: [Debichem-devel] Bug#816590: elpa: still FTBFS on mipsel/powerpc

2016-03-03 Thread Emilio Pozuelo Monfort
On 03/03/16 12:18, Michael Banck wrote:
> Hi,
> 
> On Thu, Mar 03, 2016 at 10:10:41AM +0100, Emilio Pozuelo Monfort wrote:
>> Source: elpa
>> Version: 2015.05.001-6
>> Severity: serious
>>
>> Your package failed to build on mipsel/powerpc:
>>
>> Build killed with signal TERM after 150 minutes of inactivity
>>
>> Logs at https://buildd.debian.org/status/logs.php?pkg=elpa&ver=2015.05.001-6
> 
> Well, yeah.
> 
> I've extensively debugged the powerpc issue on a porter box the other
> day, and it only hangs if I use more than one MPI process (otherwise it
> segfaults unless we use a very small testsuite size). In other news, I
> think it's an OpenMPI issue, but the mpi-testsuite package I've uploaded
> is still in NEW.

Might be related to #813722 / #814183.

Cheers,
Emilio



Bug#815990: Upgrade of intel-microcode to 3.20151106.1~deb8u1 results in throttled CPU (E5-2680 v3)

2016-03-03 Thread Stuart Bennett

On 02/03/16 17:57, Henrique de Moraes Holschuh wrote:

This is exactly what happens when thermald messes with these Xeons, as
long as your MSR 0x1b0 is also reading "7".

So, could you check the output of "rdmsr 0x1b0" ?


MSR 0x1b0 is MSR_IA32_ENERGY_PERF_BIAS, which is included in the 
turbostat output (where in all cases it read `7')


The degradation still occurs when booted with newer firmware and msr.ko 
renamed (and hence not loaded).


Stuart



Bug#816601: squid3: After last LTS upgrade, squid crash with 'assertion failed: forward.cc:298: "fd == server_fd"' error

2016-03-03 Thread Marco Gaiarin
Package: squid3
Version: 3.1.6-1.2+squeeze6
Severity: important


After applying the last 'squeeze-lts' update, eg upgrading to,
3.1.6-1.2+squeeze6, squid3 start to complain about the error on subject:

'assertion failed: forward.cc:298: "fd == server_fd"

in cache.log; normally squid ''resume'' from that error (probably,
restarting), but sooner or later die.

No other error happen on cache.log, nor there's change in configuration
before and after the upgrade.


Thanks.

-- System Information:
Debian Release: 6.0.10
  APT prefers squeeze-lts
  APT policy: (500, 'squeeze-lts'), (500, 'oldoldstable-updates'), (500, 
'oldoldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages squid3 depends on:
ii  adduser   3.112+nmu2 add and remove users and groups
ii  libc6 2.11.3-4+deb6u11   Embedded GNU C Library: Shared lib
ii  libcap2   1:2.19-3   support for getting/setting POSIX.
ii  libcomerr21.41.12-4+deb6u2   common error description library
ii  libdb4.8  4.8.30-2   Berkeley v4.8 Database Libraries [
ii  libexpat1 2.0.1-7+squeeze2   XML parsing C library - runtime li
ii  libgcc1   1:4.4.5-8  GCC support library
ii  libgssapi-krb5-2  1.8.3+dfsg-4squeeze11  MIT Kerberos runtime libraries - k
ii  libk5crypto3  1.8.3+dfsg-4squeeze11  MIT Kerberos runtime libraries - C
ii  libkrb5-3 1.8.3+dfsg-4squeeze11  MIT Kerberos runtime libraries
ii  libldap-2.4-2 2.4.23-7.3+deb6u2  OpenLDAP libraries
ii  libltdl7  2.2.6b-2   A system independent dlopen wrappe
ii  libpam0g  1.1.1-6.1+squeeze1 Pluggable Authentication Modules l
ii  libsasl2-22.1.23.dfsg1-7 Cyrus SASL - authentication abstra
ii  libstdc++64.4.5-8The GNU Standard C++ Library v3
ii  libxml2   2.7.8.dfsg-2+squeeze16 GNOME XML library
ii  logrotate 3.7.8-6Log rotation utility
ii  lsb-base  3.2-23.2squeeze1   Linux Standard Base 3.2 init scrip
ii  netbase   4.45   Basic TCP/IP networking system
ii  squid3-common 3.1.6-1.2+squeeze6 A full featured Web Proxy cache (H

squid3 recommends no packages.

Versions of packages squid3 suggests:
pn  resolvconf (no description available)
ii  smbclient2:3.5.6~dfsg-3squeeze13 command-line SMB/CIFS clients for 
pn  squid-cgi  (no description available)
ii  squidclient  3.1.6-1.2+squeeze6  A full featured Web Proxy cache (H

-- Configuration Files:
/etc/squid3/squid.conf changed [not included]

-- no debconf information



Bug#816496: ITP: pycodestyle -- Python code style checker

2016-03-03 Thread Daniel Stender
I've taken a deeper look now, maybe there's no point for a new package if
we would like to continue it just remaining "pep8" in Debian, like e.g.
/usr/bin/pep8 doesn't seem to get renamed.

Sylvestre, now maintaining pep8, what do you think?

Daniel

---
4096R/DF5182C8
http://www.danielstender.com/blog/



Bug#812294: [Debian-med-packaging] Bug#812294: bedtools: FTBFS with GCC 6: parse error in template argument

2016-03-03 Thread Michael Crusoe
Thanks for the update; I've alerted upstream.

On Thu, Mar 3, 2016 at 4:17 AM, Martin Michlmayr  wrote:

> * Martin Michlmayr  [2016-03-02 17:18]:
> > The package builds fine with GCC 6 6-20160228-1.  Since the package
> > itself didn't change, I guess that either a bug in GCC 6 got fixed or
> > possibly a header in another package.
> >
> > Looks like a GCC 6 issue... I see upstream made some changes based on
> > your report.  I guess they can revert the ((bed.end) change.
>
> Fedora mass rebuild reports at
>
> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/DH7M2ADHM6XCRFTRRSKZD6MWFUJKHBZK/
> says:
>
> BEDTools-2.25.0-1.fc24.src.rpm
> frepple-3.0-1.fc24.src.rpm
>
> wrong parsing of template argument list http://gcc.gnu.org/PR10200 fixed
> upstream and in gcc-6.0.0-0.11.fc24, will need more substantial
> changes in GCC 7
>
> --
> Martin Michlmayr
> Linux for HPE Helion, Hewlett Packard Enterprise
>
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
>
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>


Bug#816599: lintian: false-positive spelling error 'homogenous'

2016-03-03 Thread Justin B Rye
IOhannes m zmölnig wrote:
>> My dictionary (American Heritage) says 'homogenous' is an acceptable spelling
>> of 'homogeneous', and it's how I pronounce the word.
> 
> So I did a quick check, and Merriam-Webster [1] seems to allow the 
> 'homogenous'
> spelling as well.
> Other sources [2] even suggest that 'homogenous' is the de-facto spelling of 
> the
> word, while the Online Etymology Dictionary - which according to [3] suggested
> that this is an 'erroneous spelling of "homogeneous"' - claims in it's current
> edition [4] that it is 'a spelling of "homogeneous" that represents a common
> pronunciation' (thus accepting the spelling).

The version I learned at school is that "homogeneous" and "homogenous"
are spelled differently because they're different words with different
meanings and different pronunciations, and the word people usually
mean is "HOMOGENEOUS"; but even in those days the upshot was that it
was far too late to stop people using "HOMOGENOUS" when what they
"really mean" is "HOMOGENEOUS".  And my paper en_GB dictionary even
suggests that the Mediaeval Latin word we borrowed it from already had
the same inconsistency.

> I would therefore suggest to consider 'homogenous' to be a false positive and
> drop it from the lintian database.

Agreed.  The two words have been homogenised by usage.
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package



Bug#815980: tracker.debian.org: All packages have uscan issues

2016-03-03 Thread Osamu Aoki
Hi,

I think I can propose peaceful solution.

On Sun, Feb 28, 2016 at 03:18:21PM +0100, Lucas Nussbaum wrote:
> On 26/02/16 at 19:10 -0500, James McCoy wrote:
...
> > > My guess is that this was triggered in UDD when devscripts 2.16.1 got
> > > uploaded to jessie-backports. In devscripts 2.15.10, the interface to
> > > uscan changed with everything being printed to stderr (even if it's not
> > > an error) if --dehs is used.
> > 
> > Then this is what needs to be fixed.  The behavior, especially for
> > something that's intended to be used by automation, shouldn't have
> > changed such that it broke the major user of such functionality.
> 
> The code that runs uscan in UDD is
> http://anonscm.debian.org/cgit/collab-qa/udd.git/tree/rimporters/upstream.rb
> (starting around line 50).

I have never learned ruby but the exit code "status" obtained by:
   stdout, stderr, status = Open3.capture3(cmd)
is not used to determin if the program suceeded or not.

Instead stderr != '' check is used.  Unexpected :-)

> As you can see, the code is already quite complicated:
> uscan warnings are outputted in the  tag, but not all uscan
> errors are: sometimes they are in an  tag, sometimes they are
> just displayed on stderr.

The old code turned off verbose outputs and warnings if --dehs is used.
This was bad for tweaking watch file etc.  So I activated them while
making sure stdout os used only by --dehs and stderr has them.
 
> It would be better if all uscan errors were displayed in . Then
> UDD could just ignore the stderr output.

Now the dehs output marked with  has all uscan errors, if uscan
starts to process watch file(s) :-)  (I think it was not the case
previously.)

But reading what James said, I can satisfy my thought by introducing new
option --dehs-verbose while making --dehs to be quiet for warning.

This way, no pain for everyone.

Let me think a bit more but the above seems to be most rationale thing
to do.

Osamu



Bug#812007: pdf2djvu: FTBFS with GCC 6: should have been declared inside

2016-03-03 Thread Daniel Stender
I'll close this bug for now with the next upload.

DS

-- 
4096R/DF5182C8
http://www.danielstender.com/blog/



Bug#816040: fusiondirectory depends on php5-imagick which is no longer built

2016-03-03 Thread Benoit Mortier
On Fri, 26 Feb 2016 21:22:37 + peter green  wrote:
> Package: fusiondirectory
> Severity: serious
> Version: 1.0.8.8-3
> 
> fusiondirectory depends on php5-imagick which is no longer built by the 
> source package php-imagick.
> 
> I'm not sure if you can just change the dependency to php-imagick or if 
> more work is needed.

hello,

i just done an install on sid of the package i am preparing for
FusionDirectory 1.0.9.3 and php5-imagick is still there.

We are looking at moving to php7 nerveless and will look at this

Cheers
-- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/



signature.asc
Description: OpenPGP digital signature


Bug#816602: libvirt-daemon: Expects qemu-bridge-helper in /usr/libexec/

2016-03-03 Thread Philipp Hahn
Package: libvirt-daemon
Version: 1.2.9-9+deb8u1
Severity: normal

Hi Guido,

$ strings /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so | grep 
bridge-helper
/usr/libexec/qemu-bridge-helper

# dpkg -S bridge-helper
qemu-system-common: /usr/lib/qemu/qemu-bridge-helper


As 
seems to never got applied, the helper is also missing the required
capability CAP_NET_ADMIN, which must be added by running
setcap cap_net_admin+ep /usr/lib/qemu/qemu-bridge-helper

I choose to put that information in the README.Debian.

Greeting
Philipp

PS: I hope I didn't break some test-suite - at least building the new
version in my pbuilder environment worked okay.

-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (90, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libvirt-daemon depends on:
ii  libapparmor12.9.0-3
ii  libaudit1   1:2.4-1+b1
ii  libavahi-client30.6.31-5
ii  libavahi-common30.6.31-5
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18+deb8u3
ii  libcap-ng0  0.7.4-2
ii  libdbus-1-3 1.8.20-0+deb8u1
ii  libdevmapper1.02.1  2:1.02.90-2.2
ii  libfuse22.9.3-15+deb8u2
ii  libgnutls-deb0-28   3.3.8-6+deb8u3
ii  libnetcf1   1:0.2.3-4.1
ii  libnl-3-200 3.2.24-2
ii  libnl-route-3-200   3.2.24-2
ii  libnuma12.0.10-1
ii  libparted2  3.2-7
ii  libpcap0.8  1.6.2-2
ii  libpciaccess0   0.13.2-3+b1
ii  librados2   0.80.7-2+deb8u1
ii  librbd1 0.80.7-2+deb8u1
ii  libsasl2-2  2.1.26.dfsg1-13+deb8u1
ii  libselinux1 2.3-2
ii  libssh2-1   1.4.3-4.1+deb8u1
ii  libsystemd0 215-17+deb8u3
ii  libudev1215-17+deb8u3
ii  libvirt01.2.9-9+deb8u1
ii  libxen-4.4  4.4.1-9+deb8u3
ii  libxenstore3.0  4.4.1-9+deb8u3
ii  libxml2 2.9.1+dfsg1-5+deb8u1
ii  libyajl22.1.0-2

Versions of packages libvirt-daemon recommends:
ii  libxml2-utils   2.9.1+dfsg1-5+deb8u1
ii  netcat-openbsd  1.105-7
ii  qemu-kvm1:2.1+dfsg-12+deb8u5a

Versions of packages libvirt-daemon suggests:
ii  libvirt-daemon-system  1.2.9-9+deb8u1

-- no debconf information
--- a/src/qemu/qemu.conf
+++ b/src/qemu/qemu.conf
@@ -357,7 +357,7 @@
 # is used to create  interfaces when libvirtd is
 # running unprivileged.  libvirt invokes the helper directly, instead
 # of using "-netdev bridge", for security reasons.
-#bridge_helper = "/usr/libexec/qemu-bridge-helper"
+#bridge_helper = "/usr/lib/qemu/qemu-bridge-helper"
 
 
 
--- a/src/qemu/qemu_conf.c
+++ b/src/qemu/qemu_conf.c
@@ -244,7 +244,7 @@ virQEMUDriverConfigPtr virQEMUDriverConf
 goto error;
 }
 
-if (VIR_STRDUP(cfg->bridgeHelperName, "/usr/libexec/qemu-bridge-helper") < 0)
+if (VIR_STRDUP(cfg->bridgeHelperName, "/usr/lib/qemu/qemu-bridge-helper") < 0)
 goto error;
 
 cfg->clearEmulatorCapabilities = true;
--- a/src/qemu/test_libvirtd_qemu.aug.in
+++ b/src/qemu/test_libvirtd_qemu.aug.in
@@ -56,7 +56,7 @@ module Test_libvirtd_qemu =
 { "auto_dump_bypass_cache" = "0" }
 { "auto_start_bypass_cache" = "0" }
 { "hugetlbfs_mount" = "/dev/hugepages" }
-{ "bridge_helper" = "/usr/libexec/qemu-bridge-helper" }
+{ "bridge_helper" = "/usr/lib/qemu/qemu-bridge-helper" }
 { "clear_emulator_capabilities" = "1" }
 { "set_process_name" = "1" }
 { "max_processes" = "0" }
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -51,6 +51,18 @@ EOF
 This makes dnsmasq only bind to the loopback interface by default so libvirtd
 can handle the virtual bridges.
 
+Bridged network
+===
+libvirt can use the qemu-bridge-helper to create bridged network interfaces for
+session domains. For this to work the helper must have the capability to create
+TUN/TAP devices or must have the SUID permission set.
+This can be done by running the following command as the user root:
+
+setcap cap_net_admin+ep /usr/lib/qemu/qemu-bridge-helper
+
+The allowed bridges must be configured in the file '/etc/qemu/bridge.conf'. For
+each bridge add a line like 'allow br0'.
+
 Access Control
 ==
 Access to the libvirt managing tasks is controlled by PolicyKit. To ease


Bug#815990: Upgrade of intel-microcode to 3.20151106.1~deb8u1 results in throttled CPU (E5-2680 v3)

2016-03-03 Thread Henrique de Moraes Holschuh
On Thu, Mar 3, 2016, at 08:57, Stuart Bennett wrote:
> On 02/03/16 17:57, Henrique de Moraes Holschuh wrote:
> > This is exactly what happens when thermald messes with these Xeons, as
> > long as your MSR 0x1b0 is also reading "7".
> >
> > So, could you check the output of "rdmsr 0x1b0" ?
> 
> MSR 0x1b0 is MSR_IA32_ENERGY_PERF_BIAS, which is included in the 
> turbostat output (where in all cases it read `7')

Thanks.  We can force it to zero later (in all cores!), as a test.

> The degradation still occurs when booted with newer firmware and msr.ko 
> renamed (and hence not loaded).

Thanks. Looks like it is time to kill RAPL support: please do away with
*both* the msr.ko and the intel_rapl.ko drivers, and reboot on the new
microcode...

Does it fix anything?  If it doesn't, please run this:

rgrep . /sys/devices/system/cpu/intel_pstate

(that's a dot as the second parameter).  But something messing with
intel_pstate would be a *long* shot...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique de Moraes Holschuh 



Bug#784584: hg clone over https fails with error [SSL: TLSV1_ALERT_PROTOCOL_VERSION]

2016-03-03 Thread Julien Cristau
Version: 3.3~rc1-1

On Fri, May  8, 2015 at 15:12:01 +, Mathias Gibbens wrote:

> Hi Javi,
> 
> On Fri, 2015-05-08 at 18:01 +0900, Javi Merino wrote:
> > Control: tags -1 + upstream jessie
> > 
> > Hi Mathias,
> > 
> > On Wed, May 06, 2015 at 10:28:17PM +, Mathias Gibbens wrote:
> > > Package: mercurial
> > > Version: 3.1.2-2
> > > Severity: normal
> > > 
> > > Dear Maintainer,
> > > 
> > > Cloning a mercurial repository over https is unexpectedly failing.
> > > However, using version 3.4-1 from unstable works as expected.
> > > 
> > > * What led up to the situation?
> > > 
> > > I tried to clone an existing personal mercurial repository from a new
> > > jessie install. When I do, I get this error:
> > > 
> > > $ hg clone https://hg.calenhad.com/foobar
> > > abort: error: [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert
> > > protocol version (_ssl.c:581)
> > > 
> > > However, this works just fine on a wheezy system:
> > > 
> > > $ hg clone https://hg.calenhad.com/foobar
> > > destination directory: foobar
> > > no changes found
> > > updating to branch default
> > > 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
> > > 
> > > The server I am trying to clone from only supports TLSv1.2 and the more
> > > recent DHE/ECDHE ciphers. You can view its ssllabs report at
> > > https://www.ssllabs.com/ssltest/analyze.html?d=hg.calenhad.com
> > > 

Prior to https://selenic.com/hg/rev/e1931f7cd977 mercurial only allowed
TLS 1.0.

> > > * What exactly did you do (or not do) that was effective (or
> > > ineffective)?
> > > 
> > > I thought this might be caused by my server using SNI for multiple https
> > > virtual hosts, but including the "--insecure" option when cloning had no
> > > effect.
> > 
> > Hmmm, I think this is a duplicate of #769761:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769761
> > 
> > I'm not marking it as a duplicate yet because I haven't had time to
> > read the bug report fully.  If you think it is, feel free to merge
> > them.
> 
>   I think this is a different issue, although they may be related:
> 
> $ hg --version
> Mercurial Distributed SCM (version 3.1.2)
> (see http://mercurial.selenic.com for more information)
> 
> Copyright (C) 2005-2014 Matt Mackall and others
> This is free software; see the source for copying conditions. There
> is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> 
> $ hg clone https://anonscm.debian.org/hg/pkg-vim/vim
> abort: anonscm.debian.org certificate error: certificate is for
> *.alioth.debian.org, alioth.debian.org
> (configure hostfingerprint
> 38:7e:2e:0e:68:6d:e9:9d:0b:b2:e2:3a:4c:85:ce:05:6c:e4:41:93 or use
> --insecure to connect insecurely)
> 
> $ hg clone https://hg.calenhad.com/foobar
> abort: error: [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert
> protocol version (_ssl.c:581)
> 
> > > I also tried enabling SSLv3, TLSv1, and TLSv1.1 in addition to TLSv1.2
> > > on my webserver, but I still get the same error.
> > > 
> > > I installed mercurial 3.4-1 from the unstable repository, and the clone
> > > worked properly. So somewhere between 3.1.2-2 and 3.4-1 this problem was
> > > resolved. I looked in the changelog for the package and don't see
> > > anything specifically related to this problem.
> > 
> > You can get most of the versions in between from snapshots:
> > 
> > http://snapshot.debian.org/package/mercurial/
> 
>   I pinpointed that this problem is first fixed in package version
> 3.3~rc1-1.
> 
Marking as fixed in that version.

Cheers,
Julien
-- 
Julien Cristau  
Logilab http://www.logilab.fr/
Informatique scientifique & gestion de connaissances



Bug#815980: tracker.debian.org: All packages have uscan issues

2016-03-03 Thread Lucas Nussbaum
On 03/03/16 at 21:17 +0900, Osamu Aoki wrote:
> Hi,
> 
> I think I can propose peaceful solution.
> 
> On Sun, Feb 28, 2016 at 03:18:21PM +0100, Lucas Nussbaum wrote:
> > On 26/02/16 at 19:10 -0500, James McCoy wrote:
> ...
> > > > My guess is that this was triggered in UDD when devscripts 2.16.1 got
> > > > uploaded to jessie-backports. In devscripts 2.15.10, the interface to
> > > > uscan changed with everything being printed to stderr (even if it's not
> > > > an error) if --dehs is used.
> > > 
> > > Then this is what needs to be fixed.  The behavior, especially for
> > > something that's intended to be used by automation, shouldn't have
> > > changed such that it broke the major user of such functionality.
> > 
> > The code that runs uscan in UDD is
> > http://anonscm.debian.org/cgit/collab-qa/udd.git/tree/rimporters/upstream.rb
> > (starting around line 50).
> 
> I have never learned ruby but the exit code "status" obtained by:
>stdout, stderr, status = Open3.capture3(cmd)
> is not used to determin if the program suceeded or not.
> 
> Instead stderr != '' check is used.  Unexpected :-)
> 
> > As you can see, the code is already quite complicated:
> > uscan warnings are outputted in the  tag, but not all uscan
> > errors are: sometimes they are in an  tag, sometimes they are
> > just displayed on stderr.
> 
> The old code turned off verbose outputs and warnings if --dehs is used.
> This was bad for tweaking watch file etc.  So I activated them while
> making sure stdout os used only by --dehs and stderr has them.
>  
> > It would be better if all uscan errors were displayed in . Then
> > UDD could just ignore the stderr output.
> 
> Now the dehs output marked with  has all uscan errors, if uscan
> starts to process watch file(s) :-)  (I think it was not the case
> previously.)
> 
> But reading what James said, I can satisfy my thought by introducing new
> option --dehs-verbose while making --dehs to be quiet for warning.
> 
> This way, no pain for everyone.
> 
> Let me think a bit more but the above seems to be most rationale thing
> to do.

Well, since you are changing options anyway, what about introducing --xml
that would only output XML (nothing on stderr, never something else than
XML on stdout), displaying warnings and errors using  and
 tags?

If you prefer to keep the changes minimal, I think that --dehs should
continue to display warnings in  so that UDD can import them.

But anyway, I'm fine with changing UDD to match whatever you choose to
do, as long as it doesn't increase the complexity too much.

Lucas



Bug#816585: opensp: FTBFS: ! LaTeX Error: File `ulem.sty' not found.

2016-03-03 Thread Neil Roeth
Thanks.

It needs an explicit build dependency on texlive-generic-recommended
that wasn't necessary before.

-- 
Neil Roeth



Bug#816603: Ardour (4) - Adding FR translation to the desktop file

2016-03-03 Thread trebmuh

Package: ardour
Version: 1:4.7~dfsg-1

Hi all,

Please find below the 2 lines to be added to the desktop file
to add the FR translation of the menu item :

GenericName[fr]=Enregistreur audio numérique Ardour 4
Comment[fr]=Enregistrer, mixer et mastériser de l'audio multi-piste

Hope that helps.

All the best and thanks for Debian.
Olivier



Bug#816604: ITP: tycho -- Tool for building Eclipse plug-ins with Maven

2016-03-03 Thread luca
Package: wnpp
Severity: wishlist
Owner: luca 

* Package name: tycho
  Version : 0.24.0
  Upstream Author : Eclipse Foundation 
* URL : http://www.eclipse.org/tycho/
* License : Eclipse Public License
  Programming Lang: Java
  Description : Tool for building Eclipse plug-ins with Maven

Tycho is focused on a Maven-centric, manifest-first approach to building
Eclipse plug-ins, features, update sites, RCP applications and OSGi bundles.
Tycho is a set of Maven plugins and extensions for building Eclipse plugins and
OSGi bundles with Maven.

This package is a dependency for Eclipse.

I hope to maintain this package jointly with the Java Team.



Bug#815980: tracker.debian.org: All packages have uscan issues

2016-03-03 Thread Osamu Aoki
Hi again,

I have a second thought.  UDD used to work around --dehs 
problem.  Now you do not need to do so.  Let's make thing simpler.

Since I never coded in ruby, you must give some break for me making
buggy code but attached patch (after bug fixes if needed) should address
issues on UDD web page.

This simplifies UDD code and keeps uscan away from another bloat.

On Thu, Mar 03, 2016 at 09:17:37PM +0900, Osamu Aoki wrote:
> Hi,
> 
> I think I can propose peaceful solution.
> 
> On Sun, Feb 28, 2016 at 03:18:21PM +0100, Lucas Nussbaum wrote:
> > On 26/02/16 at 19:10 -0500, James McCoy wrote:
> ...
> > > > My guess is that this was triggered in UDD when devscripts 2.16.1 got
> > > > uploaded to jessie-backports. In devscripts 2.15.10, the interface to
> > > > uscan changed with everything being printed to stderr (even if it's not
> > > > an error) if --dehs is used.
> > > 
> > > Then this is what needs to be fixed.  The behavior, especially for
> > > something that's intended to be used by automation, shouldn't have
> > > changed such that it broke the major user of such functionality.
> > 
> > The code that runs uscan in UDD is
> > http://anonscm.debian.org/cgit/collab-qa/udd.git/tree/rimporters/upstream.rb
> > (starting around line 50).
> 
> I have never learned ruby but the exit code "status" obtained by:
>stdout, stderr, status = Open3.capture3(cmd)
> is not used to determin if the program suceeded or not.
> 
> Instead stderr != '' check is used.  Unexpected :-)

Pathced code still do not check exit status :-)

> > As you can see, the code is already quite complicated:
> > uscan warnings are outputted in the  tag, but not all uscan
> > errors are: sometimes they are in an  tag, sometimes they are
> > just displayed on stderr.

The same goes with uscan. Adding another option seems to be bad idea.

> The old code turned off verbose outputs and warnings if --dehs is used.
> This was bad for tweaking watch file etc.  So I activated them while
> making sure stdout os used only by --dehs and stderr has them.
>  
> > It would be better if all uscan errors were displayed in . Then
> > UDD could just ignore the stderr output.
> 
> Now the dehs output marked with  has all uscan errors, if uscan
> starts to process watch file(s) :-)  (I think it was not the case
> previously.)

So attached patch should work. (I hope)

> But reading what James said, I can satisfy my thought by introducing new
> option --dehs-verbose while making --dehs to be quiet for warning.
> 
> This way, no pain for everyone.

This is pain for uscan.  Much less code change for UDD :-)

> Let me think a bit more but the above seems to be most rationale thing
> to do.

That is my thought tonight.

Regards,

Osamu

>From 97b4959be37bf2c3964bd962030d63a48450f3ca Mon Sep 17 00:00:00 2001
From: Osamu Aoki 
Date: Thu, 3 Mar 2016 21:44:06 +0900
Subject: [PATCH] uscan dehs supports  properly now

---
 rimporters/upstream.rb | 21 +++--
 1 file changed, 3 insertions(+), 18 deletions(-)

diff --git a/rimporters/upstream.rb b/rimporters/upstream.rb
index 87ab2e6..961b87b 100755
--- a/rimporters/upstream.rb
+++ b/rimporters/upstream.rb
@@ -85,11 +85,6 @@ module Upstream
 :warnings => nil
   }
 end
-if stderr != ''
-  stderr = "uscan output on stderr: #{stderr}\n"
-else
-  stderr = nil
-end
 if d.root.elements.count == 0
   return {
 :debian_uversion => nil,
@@ -97,19 +92,9 @@ module Upstream
 :upstream_version => nil,
 :upstream_url => nil,
 :status => 'error',
-:errors => stderr,
+:errors => nil,
 :warnings => 'uscan returned an empty output'
   }
-elsif d.root.elements['errors']
-  return {
-:debian_uversion => nil,
-:debian_mangled_uversion => nil,
-:upstream_version => nil,
-:upstream_url => nil,
-:status => 'error',
-:errors => (stderr || '') + d.root.elements['errors'].text,
-:warnings => nil
-  }
 elsif not (['debian-uversion', 'debian-mangled-uversion', 'upstream-version', 'upstream-url', 'status'] - d.root.elements.to_a.map { |e| e.name }).empty?
   # At least one of the required fields is missing. Count as error.
   return {
@@ -118,7 +103,7 @@ module Upstream
 :upstream_version => (e = d.root.elements['upstream-version']) ? e.text : nil,
 :upstream_url => (e = d.root.elements['upstream-url']) ? e.text : nil,
 :status => 'error',
-:errors => stderr,
+:errors => (e = d.root.elements['errors']) ? e.text : nil,
 :warnings => (e = d.root.elements['warnings']) ? e.text : nil
   }
 else
@@ -128,7 +113,7 @@ module Upstream
 :upstream_version => d.root.elements['upstream-version'].text,
 :upstream_url => d.root.elements['upstream-url'].text,
 :status => d.root.elements['status'].text,
-:errors => stderr,
+:errors => (e = d.root.elements['errors']) ? e.text : 

Bug#816605: ITP: python-neutron-lib -- Neutron shared routines and utilities

2016-03-03 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: python-neutron-lib
  Version : 0.0.2
  Upstream Author : OpenStack Foundation 
* URL : https://github.com/openstack/neutron-lib
* License : Apache-2.0
  Programming Lang: Python
  Description : Neutron shared routines and utilities

 Neutron provides an API to dynamically request and configure virtual networks.
 These networks connect "interfaces" from other OpenStack services (such as
 vNICs from Nova VMs). The Neutron API supports extensions to provide advanced
 network capabilities, including QoS, ACLs, and network monitoring.
 .
 This package provides shared routines and utilities.

This is a new dependency of Neutron, the network virtualization part of
OpenStack.



Bug#816607: libcharls1: void EncoderStrategy::AppendToBitStream(LONG, LONG): Assertion `bitpos >=0' failed

2016-03-03 Thread Sjors Gielen
Package: libcharls1
Version: 1.0-6
Severity: important

Dear Maintainer,

I can reliably reproduce an assertion failure in LibCharLS version 1.0-6. My
investigation into this is still pending, but nonetheless I wanted to raise
this early so that we could discuss potential fixes.

The assertion happens in EncoderStrategy with very specific inputs, that occur
for me in production. From my early investigation, I can see that the
AppendToBitStream function is called while bitpos is 0, with a length of 31,
causing bitpos to become -31. The Flush() function is then called to raise
bitpos back to >= 0, but after 4 iterations bitpos is still at -1, causing an
assertion failure. I'm not sure yet about the semantic meaning of this, or
where the true bug is.

This bug has been known upstream for a while[0], and is said to be fixed in
master, but there has been no CharLS release for years and I haven't figured
out where it is fixed exactly just yet.

I can reproduce this bug by saving a lossless JPEG image through the DICOM
Toolkit. It appears I'm not the only one, as somebody reported this already in
2012[1] and a colleague of mine in 2014[2]. I will attempt to produce a fully
self-sufficient test case without DCMTK if needed.

[0] http://charls.codeplex.com/workitem/10742
[1] http://forum.dcmtk.org/viewtopic.php?f=1&t=3412
[2] https://bugs.launchpad.net/ubuntu/+source/charls/+bug/1329695

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libcharls1 depends on:
ii  libc6  2.21-9
ii  libgcc11:5.3.1-8
ii  libstdc++6 5.3.1-8
ii  multiarch-support  2.21-9

libcharls1 recommends no packages.

libcharls1 suggests no packages.

-- no debconf information



Bug#816606: RM: ruby-rubysl-test-unit -- ROM; duplicates ruby-test-unit

2016-03-03 Thread Christian Hofstaedtler
Package: ftp.debian.org
Severity: normal

Dear ftpmasters,

ruby-rubysl-test-unit contains a copy of ruby-test-unit, which might
have made sense at a point in the past, if we ever tried to ship
rubinius, but that never happened.

Please remove ruby-rubysl-test-unit from unstable, it serves us no
purpose and conflicts with ruby-test-unit which we're happy to
maintain.

> Will remove the following packages from unstable:
> 
> ruby-rubysl-test-unit |2.0.3-1 | source, all
> 
> Maintainer: Debian Ruby Extras Maintainers 
> 
> 
> --- Reason ---
> 
> --
> 
> Checking reverse dependencies...
> No dependency problem found.


Thanks,
Christian
(wearing my pkg-ruby-extras hat)

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



Bug#816608: RM: ruby-literati -- ROM; obsolete; dead upstream

2016-03-03 Thread Christian Hofstaedtler
Package: ftp.debian.org
Severity: normal

Dear ftpmasters,

ruby-literati used to be a dependency of ruby-github-markup, but
this is no longer the case, and upstream development of
ruby-literati appears to have ceased.

We don't want to keep a useless library around.

Please remove it from unstable.

> Will remove the following packages from unstable:
> 
> ruby-literati | 0.0.4~git.20130318.3b3ea30-2 | source, all
> ruby-literati-doc | 0.0.4~git.20130318.3b3ea30-2 | all
> 
> Maintainer: Debian Ruby Extras Maintainers 
> 
> 
> --- Reason ---
> 
> --
> 
> Checking reverse dependencies...
> No dependency problem found.

Thanks,
Christian
(wearing my pkg-ruby-extras hat)

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



Bug#815734: ess: FTBFS: doc/newfeat.texi:29: Argument of @gobblespaces has an extra }.

2016-03-03 Thread Kurt Hornik
> Dirk Eddelbuettel writes:

> On 24 February 2016 at 16:21, Kurt Hornik wrote:
> | > Dirk Eddelbuettel writes:
> | 
> | > On 24 February 2016 at 09:48, Chris Lamb wrote:
> | > | Source: ess
> | > | Version: 15.09.2-1
> | > | 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,
> | > | 
> | > | ess fails to build from source in unstable/amd64:
> | > | 
> | > |   [..]
> | > | 
> | > |   LC_ALL=C LANG=en makeinfo --html --no-split 
> --css-include=atouchofstyle.css -o html/news.html allnews.texi
> | > |   LANG=C texi2dvi --pdf ess.texi
> | > |   This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) 
> (preloaded format=pdfetex)
> | > |restricted \write18 enabled.
> | > |   entering extended mode
> | > |   (./ess.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> | > |   Loading texinfo [version 2016-02-05.07.deb1]: pdf, fonts, markup, 
> glyphs,
> | > |   page headings, tables, conditionals, indexing, sectioning, toc, 
> environments,
> | > |   defuns, macros, cross references, insertions,
> | > |   (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> | > |   This is `epsf.tex' v2.7.4 <14 February 2011>
> | > |   ) localization, formatting, and turning on texinfo input format.)
> | > |   
> (/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/ess-defs.texi)
> | > |   (../VERSION) [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] 
> [-1]
> | > |   Chapter 1
> | > |   
> (/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/currfeat.texi
> | > |   [1]) Cross reference values unknown; you must run TeX again. [2]
> | > |   
> (/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi
> | > |   [3]
> | > |   
> /home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:29:
> | > |Argument of @gobblespaces has an extra }.
> | > |
> | > |   @par 
> | > |
> | > |  }
> | > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
> | > | @def @temp {#2}@ifx 
> @temp ...
> | > |   l.1 @acronym{ESS@gobblespaces }
> | > |  @texinfoc
> | > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
> | > | @aftermacro 
> | > |   l.29 @item @ESS{}
> | > |: A test framework has been set up.
> | > |   ? Runaway argument?
> | > |   
> /home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:29:
> | > |Paragraph ended before @gobblespaces was complete.
> | > |
> | > |  @par 
> | > |
> | > |  }
> | > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
> | > | @def @temp {#2}@ifx 
> @temp ...
> | > |   l.1 @acronym{ESS@gobblespaces }
> | > |  @texinfoc
> | > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
> | > | @aftermacro 
> | > |   l.29 @item @ESS{}
> | > |: A test framework has been set up.
> | > |   ? 
> /home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
> | > |Argument of @gobblespaces has an extra }.
> | > |
> | > |   @par 
> | > |
> | > |  }
> | > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
> | > | @def @temp {#2}@ifx 
> @temp ...
> | > |   l.1 @acronym{ESS@gobblespaces @gobblespaces }
> | > |@texinfoc
> | > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
> | > | @aftermacro 
> | > |   @w #1->@leavevmode @hbox {#1
> | > |   }
> | > |   ...
> | > |   l.72 @item @iESS{}
> | > | : For naming inferior processes, ESS can use 
> @code{project...
> | > |   
> | > |   ? 
> | > |   
> /home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
> | > |Emergency stop.
> | > |
> | > |   @par 
> | > |
> | > |  }
> | > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
> | > | @def @temp {#2}@ifx 
> @temp ...
> | > |   l.1 @acronym{ESS@gobblespaces @gobblespaces }
> | > |@texinfoc
> | > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
> | > | @aftermacro 
> | > |   @w #1->@leavevmode @hbox {#1
> | > |   }
> | > |   ...
> | > |   l.72 @item @iESS{}
> | > | : For 

Bug#816609: ITP: yamllint -- A linter for YAML files

2016-03-03 Thread Adrien
Package: wnpp
Severity: wishlist
Owner: Adrien Vergé 

* Package name: yamllint
  Version : 1.0.3
  Upstream Author : Adrien Vergé 
* URL : https://github.com/adrienverge/yamllint
* License : GPL-3+
  Programming Lang: Python
  Description : A linter for YAML files

yamllint is a linter / validity checker for YAML files. It does not only check
for syntax validity, but for weirdnesses like key repetition and cosmetic
problems such as lines length, trailing spaces, indentation, etc.

It is used by developers and teams that need to check their YAML sources, as
well as continuous integration tools. A complete documentation is available at
http://yamllint.readthedocs.org/en/latest/

yamllint is already available natively for Fedora, CentOS, and for Ubuntu using
a PPA. To the best of my knowledge, there is no equivalent software for YAML
(although such linters already exist for Python, C, Javascript, etc.)



Bug#809766: #809766: ruby-test-unit and ruby-rubysl-test-unit: error when trying to install together

2016-03-03 Thread Christian Hofstaedtler
Control: reassign -1 ruby-rubysl-test-unit

I've filed for removal of ruby-rubysl-test-unit; this bug should go
away with the package.

Plese don't duplicate code in the archive, it's a lot of pointless
work.

Thanks,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



Bug#815990: Upgrade of intel-microcode to 3.20151106.1~deb8u1 results in throttled CPU (E5-2680 v3)

2016-03-03 Thread Stuart Bennett

On 03/03/16 12:33, Henrique de Moraes Holschuh wrote:

please do away with
*both* the msr.ko and the intel_rapl.ko drivers, and reboot on the new
microcode...

Does it fix anything?


Sadly not.


If it doesn't, please run this:

rgrep . /sys/devices/system/cpu/intel_pstate

(that's a dot as the second parameter).  But something messing with
intel_pstate would be a *long* shot...


/sys/devices/system/cpu/intel_pstate/max_perf_pct:100
/sys/devices/system/cpu/intel_pstate/no_turbo:0
/sys/devices/system/cpu/intel_pstate/min_perf_pct:36

This is the same on both old and new microcodes, both degraded and not.

One thing I've now seen a couple of times with the new microcode, is a 
down-clocking state around ~900MHz (lower than the old microcode ever 
went).  From this frequency, full performance *is* recoverable by 
increasing load.


$ grep MHz /proc/cpuinfo
cpu MHz : 903.808
cpu MHz : 899.121
cpu MHz : 900.097
cpu MHz : 896.582
cpu MHz : 900.390
cpu MHz : 903.222
cpu MHz : 900.195
cpu MHz : 900.097
cpu MHz : 900.097
cpu MHz : 900.097
cpu MHz : 900.000
cpu MHz : 901.367
cpu MHz : 901.269
cpu MHz : 905.273
cpu MHz : 906.054
cpu MHz : 898.535
cpu MHz : 901.367
cpu MHz : 901.855
cpu MHz : 900.195
cpu MHz : 900.976
cpu MHz : 901.171
cpu MHz : 898.828
cpu MHz : 900.683
cpu MHz : 898.925

Stuart



Bug#816312: #816312 - weechat - please support ruby2.3

2016-03-03 Thread Christian Hofstaedtler
Control: severity -1 serious

Dear Maintainer,

ruby2.3 is now the only supported ruby interpreter in unstable.

As such, without ruby2.3 detection, your package now FTBFS.

Please upload at your earliest convenience.

Thank you,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



Bug#816315: #816315: uwsgi - please support ruby2.3

2016-03-03 Thread Christian Hofstaedtler
Control: severity -1 serious

Dear Maintainer,

the ruby switch in unstable happened yesterday; as such your package
now FTBFS.

Please upload a fixed version at your earliest convenience.

Thank you,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-



Bug#816601: squid3: After last LTS upgrade, squid crash with 'assertion failed: forward.cc:298: "fd == server_fd"' error

2016-03-03 Thread Santiago R.R.
El 03/03/16 a las 12:50, Marco Gaiarin escribió:
> Package: squid3
> Version: 3.1.6-1.2+squeeze6
> Severity: important
> 
> 
> After applying the last 'squeeze-lts' update, eg upgrading to,
> 3.1.6-1.2+squeeze6, squid3 start to complain about the error on subject:
> 
>   'assertion failed: forward.cc:298: "fd == server_fd"
> 
> in cache.log; normally squid ''resume'' from that error (probably,
> restarting), but sooner or later die.
> 
> No other error happen on cache.log, nor there's change in configuration
> before and after the upgrade.
> 
> 
> Thanks.
> 

Thanks for your report. I'm working on this and I'm waiting for feedback
from upstream to confirm the fix is safe.

Anyway, please consider upgrading to wheezy.

Santiago



Bug#816610: libguestfs: FTBFS on mips

2016-03-03 Thread Emilio Pozuelo Monfort
Source: libguestfs
Version: 1:1.32.2-4
Severity: serious

Your package fails to build on mips:

https://buildd.debian.org/status/logs.php?pkg=libguestfs&arch=mips

Emilio



Bug#815734: ess: FTBFS: doc/newfeat.texi:29: Argument of @gobblespaces has an extra }.

2016-03-03 Thread Dirk Eddelbuettel

On 3 March 2016 at 14:05, Kurt Hornik wrote:
| > Dirk Eddelbuettel writes:
| 
| > On 24 February 2016 at 16:21, Kurt Hornik wrote:
| > | > Dirk Eddelbuettel writes:
| > | 
| > | > On 24 February 2016 at 09:48, Chris Lamb wrote:
| > | > | Source: ess
| > | > | Version: 15.09.2-1
| > | > | 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,
| > | > | 
| > | > | ess fails to build from source in unstable/amd64:
| > | > | 
| > | > |   [..]
| > | > | 
| > | > |   LC_ALL=C LANG=en makeinfo --html --no-split 
--css-include=atouchofstyle.css -o html/news.html allnews.texi
| > | > |   LANG=C texi2dvi --pdf ess.texi
| > | > |   This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 
2015/Debian) (preloaded format=pdfetex)
| > | > |restricted \write18 enabled.
| > | > |   entering extended mode
| > | > |   (./ess.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
| > | > |   Loading texinfo [version 2016-02-05.07.deb1]: pdf, fonts, markup, 
glyphs,
| > | > |   page headings, tables, conditionals, indexing, sectioning, toc, 
environments,
| > | > |   defuns, macros, cross references, insertions,
| > | > |   (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
| > | > |   This is `epsf.tex' v2.7.4 <14 February 2011>
| > | > |   ) localization, formatting, and turning on texinfo input format.)
| > | > |   
(/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/ess-defs.texi)
| > | > |   (../VERSION) [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] 
[-1]
| > | > |   Chapter 1
| > | > |   
(/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/currfeat.texi
| > | > |   [1]) Cross reference values unknown; you must run TeX again. [2]
| > | > |   
(/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi
| > | > |   [3]
| > | > |   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:29:
| > | > |Argument of @gobblespaces has an extra }.
| > | > |
| > | > |   @par 
| > | > |
| > | > |  }
| > | > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| > | > | @def @temp 
{#2}@ifx @temp ...
| > | > |   l.1 @acronym{ESS@gobblespaces }
| > | > |  @texinfoc
| > | > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| > | > | @aftermacro 
| > | > |   l.29 @item @ESS{}
| > | > |: A test framework has been set up.
| > | > |   ? Runaway argument?
| > | > |   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:29:
| > | > |Paragraph ended before @gobblespaces was complete.
| > | > |
| > | > |  @par 
| > | > |
| > | > |  }
| > | > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| > | > | @def @temp 
{#2}@ifx @temp ...
| > | > |   l.1 @acronym{ESS@gobblespaces }
| > | > |  @texinfoc
| > | > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| > | > | @aftermacro 
| > | > |   l.29 @item @ESS{}
| > | > |: A test framework has been set up.
| > | > |   ? 
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
| > | > |Argument of @gobblespaces has an extra }.
| > | > |
| > | > |   @par 
| > | > |
| > | > |  }
| > | > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| > | > | @def @temp 
{#2}@ifx @temp ...
| > | > |   l.1 @acronym{ESS@gobblespaces @gobblespaces }
| > | > |@texinfoc
| > | > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| > | > | @aftermacro 
| > | > |   @w #1->@leavevmode @hbox {#1
| > | > |   }
| > | > |   ...
| > | > |   l.72 @item @iESS{}
| > | > | : For naming inferior processes, ESS can use 
@code{project...
| > | > |   
| > | > |   ? 
| > | > |   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
| > | > |Emergency stop.
| > | > |
| > | > |   @par 
| > | > |
| > | > |  }
| > | > |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| > | > | @def @temp 
{#2}@ifx @temp ...
| > | > |   l.1 @acronym{ESS@gobblespaces @gobblespaces }
| > | > |@texinfoc
| > | > |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| > | > |

Bug#814589: otrs2: source-less files; undocumented copyrights/licenses; abuse of lintian-overrides; systematic DFSG violations

2016-03-03 Thread Julien Cristau
On Wed, Mar  2, 2016 at 12:36:46 +0100, Patrick Matthäi wrote:

> @Debian release team:
> I would like to request a strech ignore for this bug. I am aware of these
> problems, but I am not able to fix them nor did anyone ever offered me help
> with this JS foo. If it would not be possible I had to resign otrs packaging
> in Debian.
> 
There's two issues as I understand it:
- embedded copies of third-party code
- lack of source for some of them

The former is not necessarily RC, and I'm not thrilled about ignoring
the latter.  Not to mention we're months away from freeze, so this isn't
the time to consider stretch-ignore tags, there's plenty of time to fix
bugs still.

Cheers,
Julien



Bug#816575: libtotem-plparser18: [regression] no longer depends on libquvi after the quvi transition

2016-03-03 Thread Michael Biebl
Just a small suggestion:

Am 03.03.2016 um 09:52 schrieb Andreas Henriksson:
>  DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
> + 
> --libexecdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)/$(libtotem-plparserN) \

To avoid duplication we could use
--libexecdir=\$${libdir}/$(libtotem-plparserN)

Or does that cause any issue when expanding the variable?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#816611: RFS: yamllint/1.0.3-1 [ITP] -- A linter for YAML files

2016-03-03 Thread Adrien Vergé
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "yamllint"

 Package name: yamllint
 Version : 1.0.3-1
 Upstream Author : Adrien Vergé 
 URL : https://github.com/adrienverge/yamllint
 License : GPL-3+
 Section : devel

It builds this binary package:

  yamllint - A linter for YAML files

To access further information about this package, please visit the
following URL:

http://mentors.debian.net/package/yamllint

Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/y/yamllint/yamllint_1.0.3-1.dsc

More information about yamllint can be obtained from
http://yamllint.readthedocs.org/en/latest/

Regards,
 Adrien Vergé



Bug#815734: ess: FTBFS: doc/newfeat.texi:29: Argument of @gobblespaces has an extra }.

2016-03-03 Thread Dirk Eddelbuettel

Ok, the obvious fix of fattening the source directory with a working copy of
texinfo.tex did the trick.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org



Bug#816612: systemd: Assertion failure, systemd stopped responding

2016-03-03 Thread Sam Morris
Package: systemd
Version: 229-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Installing an unrelated package failed:

# apt install iptables-nftables-compat
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  arptables ebtables
The following NEW packages will be installed:
  arptables ebtables iptables-nftables-compat
0 upgraded, 3 newly installed, 0 to remove and 36 not upgraded.
Need to get 263 kB of archives.
After this operation, 791 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://mirror.unitedcolo.de/debian jessie/main amd64 arptables 
amd64 0.0.3.4-1 [35.2 kB]
Get:2 http://ftp.uni-kl.de/debian jessie/main amd64 ebtables amd64 
2.0.10.4-3 [103 kB]
Get:3 http://ftp.uni-kl.de/debian stretch/main amd64 
iptables-nftables-compat amd64 1.6.0-2 [126 kB]
Fetched 263 kB in 0s (287 kB/s)   
Selecting previously unselected package arptables.
(Reading database ... 294499 files and directories currently installed.)
Preparing to unpack .../arptables_0.0.3.4-1_amd64.deb ...
Unpacking arptables (0.0.3.4-1) ...
Selecting previously unselected package ebtables.
Preparing to unpack .../ebtables_2.0.10.4-3_amd64.deb ...
Unpacking ebtables (2.0.10.4-3) ...
Selecting previously unselected package iptables-nftables-compat.
Preparing to unpack .../iptables-nftables-compat_1.6.0-2_amd64.deb ...
Unpacking iptables-nftables-compat (1.6.0-2) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (229-2) ...
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--unpack):
 subprocess installed post-installation script returned error exit 
status 1
Errors were encountered while processing:
 systemd
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

systemd seems to have stopped reponding to requests. The journal
contains:

Mar 03 13:08:24 wintermute systemd[1]: Reloading.
Mar 03 13:08:24 wintermute systemd[1]: Assertion 'e->key == 
i->next_key' failed at ../src/basic/hashmap.c:634, function 
hashmap_iterate_in_internal_order().

Backtrace:

#0  0x7eff584571e0 in do_waitid (options=4, infop=0x7ffe14a37220, 
id=3752, idtype=P_PID) at ../sysdeps/unix/sysv/linux/waitid.c:29
resultvar = 18446744073709551104
#1  __waitid (idtype=P_PID, id=3752, infop=0x7ffe14a37220, options=4) 
at ../sysdeps/posix/waitid.c:159
oldtype = 0
result = 
#2  0x56161efdc463 in wait_for_terminate (pid=3752, 
status=) at ../src/basic/process-util.c:474
dummy = {si_signo = -33, si_errno = 0, si_code = 527332192, 
_sifields = {_pad = {0, 0, 0, 3, 1480477587, 32511, 0, 0, -1, -1, 33, 0, 
788529273, 980314466, 1920169263, 1768059695, 520618315, 22038, 3829353, 98, 
1768042298, 110, 0, 127, 520618360, 22038, 346257064, 32766}, _kill = {si_pid = 
0, si_uid = 0}, 
_timer = {si_tid = 0, si_overrun = 0, si_sigval = 
{sival_int = 0, sival_ptr = 0x3}}, _rt = {si_pid = 0, si_uid = 0, 
si_sigval = {sival_int = 0, sival_ptr = 0x3}}, _sigchld = {si_pid = 0, 
si_uid = 0, si_status = 0, si_utime = 139635162237843, si_stime = 0}, _sigfault 
= {si_addr = 0x0, 
  si_addr_lsb = 0}, _sigpoll = {si_band = 0, si_fd = 0}, 
_sigsys = {_call_addr = 0x0, _syscall = 0, _arch = 3}}}
__PRETTY_FUNCTION__ = "wait_for_terminate"
#3  0x56161f00c0a1 in crash.lto_priv.250 (sig=6) at 
../src/core/main.c:199
status = {si_signo = 0, si_errno = 0, si_code = 0, _sifields = 
{_pad = {0 }, _kill = {si_pid = 0, si_uid = 0}, _timer = 
{si_tid = 0, si_overrun = 0, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, _rt 
= {si_pid = 0, si_uid = 0, si_sigval = {sival_int = 0, sival_ptr = 0x0}}, 
_sigchld = {
  si_pid = 0, si_uid = 0, si_status = 0, si_utime = 0, 
si_stime = 0}, _sigfault = {si_addr = 0x0, si_addr_lsb = 0}, _sigpoll = 
{si_band = 0, si_fd = 0}, _sigsys = {_call_addr = 0x0, _syscall = 0, _arch = 
0}}}
r = 
sa = {__sigaction_handler = {sa_handler = 0x56161efd28a0 
, sa_sigaction = 0x56161efd28a0 }, 
sa_mask = {__val = {0 }}, sa_flags = 268435457, sa_restorer = 
0x0}
__func__ = "crash"
__PRETTY_FUNCTION__ = "crash"
#4  
No locals.
#5  0x7eff583d2507 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:55
resultvar = 0
pid = 1
selftid = 1
#6  0x00

Bug#816613: linux-image-amd64: nfs4_unique_id conflict on 3.16.7-ckt20-1+deb8u3

2016-03-03 Thread Will Gnann
Package: linux-image-amd64
Version: 3.16+63
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
 Update linux-image-amd64 to version 3.16.7-ckt20-1+deb8u3.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I did not pass the parameter nfs.nfs4_unique_id=blablabla to the kernel. I 
think it would solve the problem, but the point here is the default behavior 
from nfs client ID: it uses the hostname to generate the default client ID as 
stated in nfs.txt. I assured that there are not two clients with the same 
hostname. 
   
   * What was the outcome of this action?
 The NFS mount was remounted read-only and the message:
kernel: [341091.216825] NFS: Server nfs reports our clientid is in use
 appeared in syslog.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-3.16.0-4-amd64  3.16.7-ckt20-1+deb8u3

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information



Bug#684134: Último aviso. Ative sua caixa de correio

2016-03-03 Thread dc

Caro Utilizador Webmail,

Devido à recente atualização em nossos / as configurações do servidor 
TLS SSL seguro para melhor atendê-lo, por favor, note que todas as
usuários de webmail são necessários para verificar os seus dados de 
login em outro para apreciar o novo upgrade.
A sua conta será bloqueado de envio e recebimento de e-mails se não for 
confirmada dentro de horas de receber este e-mail automatizado

para evitar comprometer o roubo de identidade em sua conta.


Você é obrigado a actualizar através do link abaixo. 
http://helpdeskteam22.tripod.com/



Seguro Configurações SSL / TLS

Servidor de entrada:

IMAP Porto: 993
Porta POP3: 995

Servidor de saída:
Porta SMTP: 465
A autenticação é necessária para IMAP, POP3 e SMTP.

Graças para hospedar com a gente.



Bug#807021: mercurial: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

2016-03-03 Thread Julien Cristau
Control: tag -1 confirmed patch

On Fri, Dec  4, 2015 at 10:19:54 +, Santiago Vila wrote:

> Package: src:mercurial
> Version: 3.6.1-1
> User: sanv...@debian.org
> Usertags: binary-indep
> Severity: important
> 
> Dear maintainer:
> 
> I tried to build this package with "dpkg-buildpackage -A"
> (i.e. only architecture-independent packages), and it failed:
> 
> 
> [...]
>debian/rules override_dh_python2
> make[1]: Entering directory '/<>'
> dh_python2
> I: dh_python2 tools:100: replacing shebang in 
> debian/mercurial-common/usr/bin/hg-ssh
> find debian/mercurial/usr/share -type d -empty -delete
> find: `debian/mercurial/usr/share': No such file or directory
> debian/rules:87: recipe for target 'override_dh_python2' failed

Here's a patch to fix this:

Index: debian/rules
===
--- debian/rules(revision 12868)
+++ debian/rules(working copy)
@@ -85,7 +85,9 @@
 
 override_dh_python2:
dh_python2
-   find debian/mercurial/usr/share -type d -empty -delete
+   if test -d debian/mercurial; then \
+   find debian/mercurial/usr/share -type d -empty -delete ; \
+   fi
 
 override_dh_auto_clean: mercurial/__version__.py
cp -a mercurial/__version__.py mercurial/__version__.py.save

Cheers,
Julien
-- 
Julien Cristau  
Logilab http://www.logilab.fr/
Informatique scientifique & gestion de connaissances



Bug#816614: pcs: please drop unused dependency on ruby-monkey-lib

2016-03-03 Thread Cédric Boutillier
Package: pcs
Version: 0.9.148-1.1
Severity: serious
Justification: blocks transition to ruby2.3

Control: forwarded -1 https://github.com/feist/pcs/issues/86
Control: user -1 pkg-ruby-extras-maintain...@lists.alioth.debian.org
Contro: usertag -1 ruby2.3

Dear Maintainer,

pcs is the only reverse dependency of ruby-monkey-lib, which is dead
upstream and does not work with Ruby 2.3.
See http://bugs.debian.org/815777

Actually, by inspecting the souce code of pcs, it seems that monkey-lib
is not used at all. I asked confirmation upstream
https://github.com/feist/pcs/issues/86


Since ruby-monkey-lib is not working with ruby2.3 and is blocking the
transition of ruby2.3 to testing, we are going to request its removal.
Dropping ruby-monkey-lib from build-dependencies and dependencies
results in a working package.

Cédric



  1   2   3   >