Bug#628564: debhelper: dh_installmenu should no longer add the postinst/postrm snippet for registering menu entries

[Niels Thykier]

Hi,

Reading through this bug, it occurred to me that the use-case for having
debhelper inject the postinst script is for executable menu files.

@Bill: Would it work for you if debhelper only added the snippet for the
menu files that are executable?  To my knowledge, there are at most a
handful of these so it would help a lot in removing postinst scripts.

Thanks,
~Niels

Bug#871263: libmspack: CVE-2017-6419

[Stuart Caie]

On 12/08/17 20:40, Sebastian Andrzej Siewior wrote:

On 2017-08-12 00:42:06 [+0100], Stuart Caie wrote:

On 11/08/17 19:07, Sebastian Andrzej Siewior wrote:

[0] https://security-tracker.debian.org/tracker/CVE-2017-6419
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6419
[1] 
https://github.com/vrtadmin/clamav-devel/commit/a83773682e856ad6529ba6db8d1792e6d515d7f1

Stuart, is this enough information or do you need more?

I'm interested in how the fix is to add a check to see if
window_posn+this_run wraps the window, immediately below a comment that
expressly states that won't happen, with the reasoning: this_run has already
been clamped to ensure it does not wrap a frame, and frames don't wrap
windows.

If this is incorrect reasoning, what part of the reasoning is wrong? Is
this_run somehow not being clamped to <=FRAME_SIZE through some code path?
If so, the fix is to clamp it. Is window size not a multiple of frame size?
If so, something is very wrong.

The CVE links the following link:
   
https://github.com/varsleak/varsleak-vul/blob/master/clamav-vul/heap-overflow/clamav_chm_crash.md
and that folder contains also
   
https://github.com/varsleak/varsleak-vul/raw/master/clamav-vul/heap-overflow/clamav.crash.chm

and clamav segfaults on that one. Could you please check?


OK, so now I know why.

mspack/chmd.c:1191 (read_reset_table) can't read reset table
mspack/lzxd.c:327 (lzxd_init) output_length=-884758871994
mspack/lzxd.c:336 (lzxd_init) reset_interval=16386
mspack/lzxd.c:467 (lzxd_decompress) length=-884758871994
mspack/lzxd.c:468 (lzxd_decompress) offset=0
mspack/lzxd.c:469 (lzxd_decompress) length-offset=-884758871994
mspack/lzxd.c:470 (lzxd_decompress) frame_size=4390982
mspack/lzxd.c:474 (lzxd_decompress) bytes_todo=4390982
mspack/lzxd.c:539 (lzxd_decompress) this_run=4390982
mspack/lzxd.c:777 (lzxd_decompress) uncompressed: window_posn=0, 
this_run=4390982, window_size=65536


The root cause is that chmd.c initialises the lzx stream with an 
incorrect output_length.


We decide how large the LZX frame will be. It'll either be 32k, or, if 
we know how far we are along in the output stream, and we know there is 
less than 32k left to decode, this must be the final frame, which is 
allowed to be less than 32k:


frame_size = LZX_FRAME_SIZE;
if (lzx->length && (lzx->length - lzx->offset) < (off_t)frame_size) {
  frame_size = lzx->length - lzx->offset;
}

(lzx->length - lzx->offset) should always be a positive number.. but 
only if length is positive!


With negative output_length, it fails this test, and sets frame_size to 
any value (the bottom 32 bits of output_length).


Complete control of frame_size could cause trouble in lots of places, 
not just at the uncompressed block copy.


So, the right thing to do is to guard against negative output_length. 
I've done this, and additionally added checking to chmd read_spaninfo() 
to place the blame where it lies:


https://github.com/kyz/libmspack/commit/6139a0b9e93fcb7fcf423e56aa825bc869e02229

The example file is now rejected as invalid data:

mspack/chmd.c:1191 (read_reset_table) can't read reset table
mspack/chmd.c:1276 (read_spaninfo) output length is invalid
clamav.crash.chm: extract error on "/#IDXHDR": error in data format


Yeah. The problem is probably that the reporter did not forward the report to
the upstream project (you) but only to ClamAV. And ClamAV itself isn't very
good at handling such things. I noticed this by chance while checking Debian's
bug report on the other CVE and I assumed it would be best to let you know :)

Thanks very much, I appreciate it.

Regards
Stuart

Bug#871992: juffed FTBFS on !amd64 64bit: missing symbol

[Adrian Bunk]

Source: juffed
Version: 0.10-85-g5ba17f9-12
Severity: serious

https://buildd.debian.org/status/package.php?p=juffed=sid

...
   dh_makeshlibs -a -O--buildsystem=cmake -O--fail-missing 
-O--builddirectory=./build
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libjuffed-engine-qsci0.10/DEBIAN/symbols 
doesn't match completely debian/libjuffed-engine-qsci0.10.symbols
--- debian/libjuffed-engine-qsci0.10.symbols 
(libjuffed-engine-qsci0.10_0.10-85-g5ba17f9-12_arm64)
+++ dpkg-gensymbols1_O3Nv   2017-08-12 21:35:07.207296281 +
@@ -390,7 +390,7 @@
  (c++)"Ui_FileTypesPage::setupUi(QWidget*)::{lambda()#8}::operator()() 
const::qstring_literal@Base" 0.10
  (c++)"Ui_FileTypesPage::setupUi(QWidget*)::{lambda()#9}::operator()() 
const::qstring_literal@Base" 0.10
  (c++)"Ui_FileTypesPage::setupUi(QWidget*)@Base" 0.10
- (c++|arch= !amd64)"int const* std::__find_if >(int const*, int const*, 
__gnu_cxx::__ops::_Iter_equals_val, 
std::random_access_iterator_tag)@Base" 0.10
+#MISSING: 0.10-85-g5ba17f9-12# (c++|arch= !amd64)"int const* 
std::__find_if >(int 
const*, int const*, __gnu_cxx::__ops::_Iter_equals_val, 
std::random_access_iterator_tag)@Base" 0.10
  (c++)"non-virtual thunk to Juff::FileTypesPage::~FileTypesPage()@Base" 0.10
  (c++)"non-virtual thunk to Juff::JuffScintilla::~JuffScintilla()@Base" 0.10
  (c++)"non-virtual thunk to Juff::PrintingPage::~PrintingPage()@Base" 0.10
dh_makeshlibs: failing due to earlier errors
debian/rules:14: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2

Bug#871909: dgit gbp-build fails if user specifies --git-builder

[Ian Jackson]

Sean Whitton writes ("Bug#871909: dgit gbp-build fails if user specifies 
--git-builder"):
> On Sat, Aug 12 2017, Sam Hartman wrote:
> > Recommendation: if the user passes --git-builder as a gbp-build
> > option, perhaps dgit shouldn't pass builder-specific options.
> 
> That sounds reasonable -- dgit should probably strip the signature after
> the build, in order to leave consistent output, probably printing a
> warning.

Parsing the arguments to other programs is quite a lot of work and
makes for a fragile program.  Normally, where I can, I have taken a
different approach: provide a specific option to dgit that 1. causes
the corresponding argument to be passed to a subprogram and 2. makes
whatever other changes are ncecessary.  gbp is more consistent than
many programs so pre-parsing its arguments is perhaps tolerable, but:

> > Alternatively, you can say that I shouldn't pass git-builder, but if
> > you're going to say that, I'd appreciate some mechanism to accomplish
> > my pristine-tar goal.  I guess I can also run gbp buildpackage without
> > dgit, and that'll mostly work for me, but it seems not entirely
> > desirable.
> 
> I would use origtargz(1) to check out the pristine tarball.

I think the right direction might be for there to be a way to tell
dgit that you are wanting to use this workflow, but perhaps indeed
running origtargz and the dgit sbuild will DTRT.

>  Though I guess you have to rm the orig that dgit downloads.

I don't see why that would be needed.  If dgit clone or dgit fetch
gets an orig, then surely it will be the same as the pristine-tar one.

It might be nice to provide a way to avoid having dgit unnecessarily
download origs that can be generated by origtargz.

Ian.

-- 
Ian Jackson    These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#844431: Revised patch: seeking seconds

[Holger Levsen]

On Sat, Aug 12, 2017 at 03:34:35PM -0700, Sean Whitton wrote:
> Here is an updated patch addressing these.  I reworded it to use
> 'recommended' and changed the tone to better suit policy.
> 
> Thank you Ximin, Russ and Johannes!
> 
> > "precisification" -> "more precise version"
> 
> Our definition is not actually a /version/ of the
> reproducible-builds.org definition -- that would imply that our
> definition could replace the reproducible-builds.org definition, like
> upgrading a package.
> 
> 'precisification' means roughly "filling out the missing specification
> when it is appropriate to fill it out", which is what the r-p.org
> definition instructs distributors to do.
> 
> diff --git a/policy/ch-source.rst b/policy/ch-source.rst
> index 127b125..6e32870 100644
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -661,6 +661,28 @@ particularly complex or unintuitive source layout or 
> build system (for
>  example, a package that builds the same source multiple times to
>  generate different binary packages).
>  
> +Reproducibility
> +---
> +
> +Packages should build reproducibly, which for the purposes of this
> +document [#]_ means that given
> +
> +- a version of a source package unpacked at a given path;
> +- a set of versions of installed build dependencies;
> +- a set of environment variable values;
> +- a build architecture; and
> +- a host architecture,
> +
> +repeatedly building the source package for the build architecture on
> +any machine of the host architecture with those versions of the build
> +dependencies installed and exactly those environment variable values
> +set will produce bit-for-bit identical binary packages.
> +
> +It is recommended that packages produce bit-for-bit identical binaries
> +even if most environment variables and build paths are varied.  It is
> +intended for this stricter standard to replace the above when it is
> +easier for packages to meet it.
> +
>  .. [#]
> See the file ``upgrading-checklist`` for information about policy
> which has changed between different versions of this document.
> @@ -790,3 +812,7 @@ generate different binary packages).
> often creates either static linking or shared library conflicts, and,
> most importantly, increases the difficulty of handling security
> vulnerabilities in the duplicated code.
> +
> +.. [#]
> +   This is Debian's precisification of the `reproducible-builds.org
> +   definition `_.

seconded & thanks for these improvements!


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#871994: python-cryptography FTBFS: TypeError: putenv() argument 2 must be string without null bytes, not str

[Tristan Seligmann]

On Sun, 13 Aug 2017 at 14:36 Adrian Bunk  wrote:

> Some recent change in unstable makes python-cryptography FTBFS:
>

Control: reassign -1 python-pytest
Control: affects -1 python-cryptography
Control: tags -1 + upstream fixed-upstream

This is caused by an upstream bug in pytest, that should be fixed by pytest
3.2.1: https://github.com/pytest-dev/pytest/issues/2644

Bug#871959: [debhelper-devel] Bug#871959: debhelper: dh_installdeb does not run executable package.triggers to generate triggers

[Niels Thykier]

Andreas Beckmann:
> On 2017-08-13 10:48, Niels Thykier wrote:
> 
>> Would you also expect that "postinst" (etc.) behaved the same?  AFAICT,
>> there is no reason why it should not apply to them as well if triggers
>> started doing this.
> 
> I don't have a usecase for generating the postscript, yet :-)
> But anything that needs a "list of things" seems to be a candidate for
> being generated.
> 
> 
> Andreas
> 
> ___
> debhelper-devel mailing list
> debhelper-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debhelper-devel
> 

So conffiles and shlibs as well? :P

Thanks,
~Niels

Bug#872020: frobby FTBFS: latex: not found

[Adrian Bunk]

Source: frobby
Version: 0.9.0-3
Severity: serious

https://buildd.debian.org/status/package.php?p=frobby=sid

...
for i in 1 2 3; do latex -output-directory=bin/doc/ doc/manual.tex; done
/bin/sh: 1: latex: not found
/bin/sh: 1: latex: not found
/bin/sh: 1: latex: not found
Makefile:253: recipe for target 'docPs' failed
make[2]: *** [docPs] Error 127

Bug#868284: stretch-pu: package suricata/3.2.1-1

[Arturo Borrero Gonzalez]

On 8 August 2017 at 17:39, Adam D. Barratt  wrote:
>
> Thanks. Please go ahead, with the tweaks from the earlier discussion -
> i.e. 3.2.1-1+deb9u1, with a changelog distribution of "stretch".
>

Uploaded, thanks.

Bug#871629: Problem solved with unstable version

[Vinzenz Vietzke]

Hi,

the version available from unstable solves this issue for me (Buster, Xfce).

thunderbird:
  Installiert:   1:52.2.1-5
  Installationskandidat: 1:52.2.1-5
  Versionstabelle:
 *** 1:52.2.1-5 500
500 http://http.debian.net/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
 1:52.2.1-4+b1 500
500 http://ftp.de.debian.org/debian buster/main amd64 Packages

Regards,
vinz.

--
Xfce.space | skyrocket your desktop usage
https://xfce.space

Bug#872022: RFS: evolution/3.22.6-1+nmu1

[Phil Wyett]

Updated upload.

https://mentors.debian.net/package/evolution


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

dget -x https://mentors.debian.net/debian/pool/main/e/evolution/evolution_3.22.6
-1.1.dsc

Regards

Phil

-- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Web: https://kathenas.org

Twitter: kathenasorg

Instagram: kathenasorg

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

Bug#868068: ([xserver-xorg-core] Upgrade from 2:1.16.4-1 to 2:1.16.4-1+deb8u1 loses keyboard and mouse)

[Stéphane Lavergne]

On Sun, Aug 13, 2017 at 6:22 AM, Fungi4All  wrote:
>
> The only cure I have found for both of my usb key-b and mouse is to unplug 
> them and plug them back on.

That hadn't worked in my case.

> It appears as an irq map conflict.

Are you on an Intel Haswell chipset, by any chance?

-- 
Stéphane Lavergne

Bug#871993: fail2ban.system PartOf is broken causing firewalld to fail

[Joe Cooper]

I forgot to include the error message when attempting to restart firewalld
with the problematic fail2ban.service configuration:

Failed to restart firewalld.service: Transaction contains conflicting jobs
'restart' and 'stop' for fail2ban.service. Probably contradicting
requirement dependencies configured.
See system logs and 'systemctl status firewalld.service' for details.

Bug#871999: spectral-cube FTBFS: AttributeError: 'NoneType' object has no attribute 'lineno'

[Adrian Bunk]

Source: spectral-cube
Version: 0.4.0-3
Severity: serious

Some recent change in unstable makes spectral-cube FTBFS:

https://tests.reproducible-builds.org/debian/history/spectral-cube.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/spectral-cube.html

...
spectral_cube/tests/test_spectral_cube.py::test_jybeam_upper PASSED
spectral_cube/tests/test_spectral_cube.py::test_jybeam_lower PASSED
spectral_cube/tests/test_spectral_cube.py::test_jybeam_whitespace PASSED
spectral_cube/tests/test_spectral_cube.py::test_beam_proj_meta SKIPPED
spectral_cube/tests/test_spectral_cube.py::test_proj_meta PASSED
spectral_cube/tests/test_spectral_cube.py::test_pix_sign PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_direct_init
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_direct_init_invalid_type
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_direct_init_invalid_shape
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_valid_component_name[I]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_valid_component_name[Q]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_valid_component_name[U]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_valid_component_name[V]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_valid_component_name[RR]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_valid_component_name[RL]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_valid_component_name[LR]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_valid_component_name[LL]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_invalid_component_name[A]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_invalid_component_name[B]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_invalid_component_name[IQUV]
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_invalid_wcs
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_attributes
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_dir
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_mask
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_mask_invalid_component_name
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_mask_invalid_shape
 PASSED
spectral_cube/tests/test_stokes_spectral_cube.py::TestStokesSpectralCube::test_separate_mask
 PASSED
spectral_cube/tests/test_subcubes.py::test_subcube PASSED
spectral_cube/tests/test_subcubes.py::test_ds9region[fk5.reg-result0] SKIPPED
spectral_cube/tests/test_subcubes.py::test_ds9region[image.reg-result1] SKIPPED
spectral_cube/tests/test_subcubes.py::test_ds9region[partial_overlap_image.reg-result2]
 SKIPPED
spectral_cube/tests/test_subcubes.py::test_ds9region[no_overlap_image.reg-ValueError]
 SKIPPED
spectral_cube/tests/test_subcubes.py::test_ds9region[partial_overlap_fk5.reg-result4]
 SKIPPED
spectral_cube/tests/test_subcubes.py::test_ds9region[no_overlap_fk5.reg-ValueError]
 SKIPPED
spectral_cube/tests/test_subcubes.py::test_ds9region_255[255-fk5.reg] SKIPPED
spectral_cube/tests/test_subcubes.py::test_ds9region_255[255-pixel.reg] SKIPPED
spectral_cube/tests/test_visualization.py::test_to_pvextractor SKIPPED
spectral_cube/tests/test_visualization.py::test_projvis SKIPPED
spectral_cube/tests/test_visualization.py::test_mask_quicklook SKIPPED
spectral_cube/tests/test_wcs_utils.py::test_wcs_dropping PASSED
spectral_cube/tests/test_wcs_utils.py::test_wcs_swapping PASSED
spectral_cube/tests/test_wcs_utils.py::test_add_stokes PASSED
spectral_cube/tests/test_wcs_utils.py::test_axis_names PASSED
spectral_cube/tests/test_wcs_utils.py::test_wcs_slice PASSED
spectral_cube/tests/test_wcs_utils.py::test_wcs_slice_reversal PASSED
spectral_cube/tests/test_wcs_utils.py::test_wcs_comparison PASSED
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
110, in wrap_session
INTERNALERROR> session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
146, in _main
INTERNALERROR> config.hook.pytest_runtestloop(session=session)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 

Bug#872000: montage-wrapper FTBFS: AttributeError: 'NoneType' object has no attribute 'lineno'

[Adrian Bunk]

Source: montage-wrapper
Version: 0.9.9-1
Severity: serious

Some recent change in unstable makes montage-wrapper FTBFS:

https://tests.reproducible-builds.org/debian/history/montage-wrapper.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/montage-wrapper.html

...
= test session starts ==
platform linux2 -- Python 2.7.13+, pytest-3.2.0, py-1.4.34, pluggy-0.4.0 -- 
/usr/bin/python2.7
cachedir: ..

Running tests with montage_wrapper version 0.9.9.
Running tests in lib.linux-x86_64-2.7/montage_wrapper docs.

Date: 2018-09-15T02:46:59

Platform: Linux-4.9.0-3-amd64-x86_64-with-debian-buster-sid

Executable: /usr/bin/python2.7

Full Python Version: 
2.7.13+ (default, Jul 19 2017, 18:15:03) 
[GCC 6.4.0 20170704]

encodings: sys: ascii, locale: ANSI_X3.4-1968, filesystem: ANSI_X3.4-1968, 
unicode bits: 20
byteorder: little
float info: dig: 15, mant_dig: 15

Numpy: 1.12.1
Matplotlib: not available
Pandas: not available
Astropy: 2.0.1
Using Astropy options: remote_data: none.

rootdir: /tmp/montage_wrapper-test-y1E9At, inifile: setup.cfg
collecting ... collected 5 items

montage_wrapper/mpi.py::montage_wrapper.mpi.set_mpi_command PASSED
montage_wrapper/tests/test_commands.py::test_all xfail
montage_wrapper/tests/test_wrappers.py::TestMosaic::test_mosaic PASSED
montage_wrapper/tests/test_wrappers.py::TestMosaic::test_mosaic_background_match
 PASSED
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
110, in wrap_session
INTERNALERROR> session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
146, in _main
INTERNALERROR> config.hook.pytest_runtestloop(session=session)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
614, in execute
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
169, in pytest_runtestloop
INTERNALERROR> item.config.hook.pytest_runtest_protocol(item=item, 
nextitem=nextitem)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
265, in __init__
INTERNALERROR> self.result = func()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
265, in __init__
INTERNALERROR> self.result = func()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
614, in execute
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/runner.py", 
line 65, in 

Bug#872006: python-drizzle FTBFS: AttributeError: 'NoneType' object has no attribute 'lineno'

[Adrian Bunk]

Source: python-drizzle
Version: 1.10-1
Severity: serious

Some recent change in unstable makes python-drizzle FTBFS:

https://tests.reproducible-builds.org/debian/history/python-drizzle.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-drizzle.html

...
= test session starts ==
platform linux2 -- Python 2.7.13+, pytest-3.2.0, py-1.4.34, pluggy-0.4.0 -- 
/usr/bin/python2.7
cachedir: ..

Running tests with Astropy version 2.0.1.
Running tests in lib.linux-x86_64-2.7/drizzle docs.

Date: 2017-08-12T20:27:05

Platform: Linux-4.9.0-3-amd64-x86_64-with-debian-buster-sid

Executable: /usr/bin/python2.7

Full Python Version: 
2.7.13+ (default, Jul 19 2017, 18:15:03) 
[GCC 6.4.0 20170704]

encodings: sys: ascii, locale: ANSI_X3.4-1968, filesystem: ANSI_X3.4-1968, 
unicode bits: 20
byteorder: little
float info: dig: 15, mant_dig: 15

Numpy: 1.12.1
Scipy: not available
Matplotlib: not available
h5py: not available
Pandas: not available
Using Astropy options: remote_data: none.

rootdir: /tmp/drizzle-test-TM3poP, inifile: setup.cfg
collecting ... collected 26 items

drizzle/util.py::drizzle.util.parse_extn PASSED
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
110, in wrap_session
INTERNALERROR> session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
146, in _main
INTERNALERROR> config.hook.pytest_runtestloop(session=session)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
614, in execute
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
169, in pytest_runtestloop
INTERNALERROR> item.config.hook.pytest_runtest_protocol(item=item, 
nextitem=nextitem)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
265, in __init__
INTERNALERROR> self.result = func()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
265, in __init__
INTERNALERROR> self.result = func()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
614, in execute
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/runner.py", 
line 65, in pytest_runtest_protocol
INTERNALERROR> nodeid=item.nodeid, location=item.location,
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
571, in location
INTERNALERROR> location = self.reportinfo()

Bug#872010: ccdproc FTBFS: AttributeError: 'NoneType' object has no attribute 'lineno'

[Adrian Bunk]

Source: ccdproc
Version: 1.2.0-2
Severity: serious

Some recent change in unstable makes ccdproc FTBFS:

https://tests.reproducible-builds.org/debian/history/ccdproc.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ccdproc.html

...
ccdproc/utils/slices.py::ccdproc.utils.slices.slice_from_string PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_needs_enclosing_brackets[1:2]
 PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_needs_enclosing_brackets[[1:2]
 PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_needs_enclosing_brackets[1:2]]
 PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[None-None--1] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[5-10-None] PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[None-25-None] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[2-30-3] PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[30-None--2] PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_1d[None-None-None] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_spaces[  [ 1:  45]] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_spaces[[ 1  :4 5]] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_spaces[  [1:45] ] 
PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_2d PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_fits_style PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_fits_inverted PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_empty PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_bad_fits_slice PASSED
ccdproc/utils/tests/test_slices.py::test_slice_from_string_fits_wildcard PASSED
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
110, in wrap_session
INTERNALERROR> session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
146, in _main
INTERNALERROR> config.hook.pytest_runtestloop(session=session)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
614, in execute
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
169, in pytest_runtestloop
INTERNALERROR> item.config.hook.pytest_runtest_protocol(item=item, 
nextitem=nextitem)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
265, in __init__
INTERNALERROR> self.result = func()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 

Bug#871953: apparmor: init script unconditionally uses systemd-detect-virt

[intrigeri]

Control: tag -1 + pending

Hi!

Guillem Jover:
> The apparmor init script uses systemd-detect-virt unconditionally,
> which is not available when systemd is not installed, and prints an
> error message.

> The program should be checked for its existence first before its
> usage.

Indeed, thanks!

I've committed a fix in Vcs-Bzr:
https://alioth.debian.org/scm/loggerhead/collab-maint/apparmor/revision/1655
Reviews/comments are welcome :)

Cheers,
-- 
intrigeri

Bug#872023: transition: nodejs

[Jérémy Lal]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Transition from nodejs 4 to nodejs 6, with module abi change from
version 46 to version 48.
All nodejs c++ addons (build-depending on nodejs-dev) must be rebuilt.

Also Julien Puydt rebuilt all node modules packages against nodejs 6
to check for failures and report them:
- node-chai #868319 fixed upstream
- node-argparse #868294 might be fixed upstream
- node-evp-bytestokey fails and is deprecated. #868298

Also i'm using nodejs 6 from experimental for some time now, and i don't
see breakage.

Ben file:

title = "nodejs";
is_affected = .build-depends ~ /nodejs-dev/;
is_good = .depends ~ /nodejs-abi-48/;
is_bad = .depends ~ /nodejs-abi-46/;


Regards,

Jérémy

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

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

Bug#872022: RFS: evolution/3.22.6-1+nmu1

[Phil Wyett]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "evolution":

* Package name: evolution
  Version: 3.22.6-1+nmu1
  Upstream Author: GNOME Project
* URL: https://wiki.gnome.org/Apps/Evolution
* License: LGPLv2/LGPLv3
  Section: gnome

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

https://mentors.debian.net/package/evolution

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

dget -x https://mentors.debian.net/debian/pool/main/e/evolution/evolution_3.22.6
-1+nmu1.dsc

Changes since the last upload:

evolution (3.22.6-1+nmu1) unstable; urgency=medium

  * Non-maintainer upload.
  * Added debian/patches/20_composer_hangs_right_click.patch (Closes: #871626)
- Backport patch from git - Fix hangs on right click in composer window.

 -- Phil Wyett   Sat, 12 Aug 2017 20:35:40 +0100

Additional info:

See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871626

Gnome Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=777086

This, once accepted, will be submitted as a PU for stretch.

Regards

Phil

-- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Web: https://kathenas.org

Twitter: kathenasorg

Instagram: kathenasorg

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

Bug#872032: ITP: zap -- Blazing fast, structured, leveled logging in Go

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org,
pkg-go-maintain...@lists.alioth.debian.org

* Package name: zap
  Version : 1.5.0+git20170802.3.e68420e-1
  Upstream Author : Uber Technologies, Inc.
* URL : https://go.uber.org/zap
* License : Expat
  Programming Lang: Go
  Description : Blazing fast, structured, leveled logging in Go.

In contexts where performance is nice, but not critical, use the
 SugaredLogger. It's 4-10x faster than than other structured logging
 packages and includes both structured and printf-style APIs.
 .
 When performance and type safety are critical, use the Logger. It's even
 faster than the SugaredLogger and allocates far less, but it only supports
 structured logging.

Build dependency of gitaly, a component of gitlab



signature.asc
Description: OpenPGP digital signature

Bug#870121: mate-power-manager: sometimes hits not-reached assertion on startup

[James Lu]

Control: retitle -1 mate-power-manager: crashes with upower 0.99.5 on any 
device with a backlit keyboard
Control: severity -1 grave
Justification: renders package unusable on a large range of systems

Hi everyone,

According to the upstream issue, mate-power-manager is now completely broken 
with upower
0.99.5 on any device with a backlit keyboard. This makes it effectively 
unusable on a wide
slew of devices, so I'm bumping the severity to make the issue more notable.

Best,
James

Bug#872021: gnome-software: Tagaini Jisho (Could not find the repository)

[Phil]

Package: gnome-software
Version: 3.22.5-1
Severity: minor

Dear Maintainer,

   * What led up to the situation?
I was trying to install Tagaini Jisho from the gnome software.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I pressed install but was presented with 'Sorry, this did not work'

   * What was the outcome of this action?
Message says 'Detailed errors from the package manager follow:

E: Could not find the repository'

   * What outcome did you expect instead?
Installation of the package.



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

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

Versions of packages gnome-software depends on:
ii  appstream0.10.6-2
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gnome-software-common3.22.5-1
ii  gsettings-desktop-schemas3.22.0-1
ii  libappstream-glib8   0.6.8-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u1
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libenchant1c2a   1.6.0-11+b1
ii  libfwupd10.7.4-2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgnome-desktop-3-123.22.2-1
ii  libgtk-3-0   3.22.11-1
ii  libgtkspell3-3-0 3.0.9-1
ii  libgudev-1.0-0   230-3
ii  libjson-glib-1.0-0   1.2.6-1
ii  libpackagekit-glib2-18   1.1.5-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpolkit-gobject-1-00.105-18
ii  libsecret-1-00.18.5-3.1
ii  libsoup2.4-1 2.56.0-2+deb9u1
ii  libsqlite3-0 3.16.2-5
ii  packagekit   1.1.5-2
ii  software-properties-gtk  0.96.20.2-1

gnome-software recommends no packages.

Versions of packages gnome-software suggests:
pn  fwupd  
pn  gnome-software-plugin-flatpak  
pn  gnome-software-plugin-limba

-- no debconf information

Bug#872027: chkrootkit: not tested noise in quiet mode

[Christian Göttsche]

Package: chkrootkit
Version: 0.52-1

chkrootkit produces some noise in quiet mode

$ chkrootkit -q
not tested
not tested

They seem to be out of

$ chkrootkit
[...]
Checking `syslogd'...   not tested
Searching for Linux/Ebury - Operation Windigo ssh...not tested
Checking `OSX_RSPLUG'...not tested

Bug#869965: vim: please add syntax highlighting for debian/copyright files

[James McCoy]

On Fri, Jul 28, 2017 at 09:10:57AM +0100, Chris Lamb wrote:
> A patch is attached that adds simple syntax highlighting for
> DEP-5 debian/copyright files.

Thanks!

> diff --git a/runtime/syntax/debcopyright.vim b/runtime/syntax/debcopyright.vim
> new file mode 100644
> index 000..dd34be4
> --- /dev/null
> +++ b/runtime/syntax/debcopyright.vim
> @@ -0,0 +1,32 @@
> +" Vim syntax file
> +" Language:Debian copyright file
> +" Maintainer:  Chris Lamb 

Do you want to maintain this under the umbrella of pkg-vim-maintainers?
I'd be glad to add you to the team. :)

If not, I'd prefer having you send this upstream since Bram will only
accept updates from the Maintainer.

> +syn match debcopyrightUrl   
> "\vhttps?://[[:alnum:]][-[:alnum:]]*[[:alnum:]]?(\.[[:alnum:]][-[:alnum:]]*[[:alnum:]]?)*\.[[:alpha:]][-[:alnum:]]*[[:alpha:]]?(:\d+)?(/[^[:space:]]*)?$"
> +syn match debcopyrightKey   
> "^\%(Format\|Upstream-Name\|Upstream-Contact\|Disclaimer\|Source\|Comment\|Files\|Copyright\|License\):
>  *"

What do you think about handling single-line vs. multi-line fields, like
in debcontrol.vim?

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#872028: scikit-learn FTBFS on big endian: FAIL: sklearn.feature_extraction.tests.test_feature_hasher.test_hasher_alternate_sign

[Adrian Bunk]

Source: scikit-learn
Version: 0.19.0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=scikit-learn=sid

...
==
FAIL: 
sklearn.feature_extraction.tests.test_feature_hasher.test_hasher_alternate_sign
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py",
 line 291, in wrapper
return fn(*args, **kwargs)
  File 
"/«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/feature_extraction/tests/test_feature_hasher.py",
 line 122, in test_hasher_alternate_sign
assert_true(len(Xt.data) < len(X[0]))
AssertionError: False is not true

--
Ran 7994 tests in 367.585s

FAILED (SKIP=74, failures=1)
debian/rules:88: recipe for target 'python-test2.7' failed
make[1]: *** [python-test2.7] Error 1
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:41: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2

Bug#864358: ITP: bitfield -- bit array manipulation library

[Vitalie Ciubotaru]

Hi.

On 08/06/2017 12:28 AM, Guillem Jover wrote:
>
> Well, obviously not entirely as complete but the BSDs (and libbsd
> otherwise) do have something like .
> 

The difference between sys/bitstring.h and the package I propose is that
bitstring.h implements a bit array within one unit of data storage (unsigned
char, 1 byte, 8 bits), while my package uses an array of units (array of
unsigned long integers, usually 32 or 64 bits EACH). This means that BSD's bit
array can't be longer that 8 bits, while mine is limited by memory size only.

> BTW, I noticed when I checked the implementation that you are using
> HAVE_BITFIELD_H as the header macro protector, but that's actually a
> bad idea, as with the typical autoconf based build-system that macro
> will already be defined if the build-system does something like
> AC_CHECK_HEADERS([bitfield.h]), which means the contents will be
> secluded.

Oh, yes, you are right. I was able to reproduce this problem. The name of the
header guard needs to be changed. Thank you very much for pointing it out.

Best regards,
Vitalie Ciubotaru

Bug#871357: packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at /usr/share/perl5/Locale/Po4a/TransTractor.pm line 6

[gregor herrmann]

On Tue, 08 Aug 2017 23:55:26 +0200, Martin Quinson wrote:

> Thanks for investigating this bug.

Thanks for looking into this issue.
 
> > The error is in /usr/share/perl5/Locale/Po4a/TransTractor.pm:643
> > which is
> > my $found = scalar grep { /$position/ } @{$self->{TT}{doc_out}};
> > and $position (comes from addendum_parse() in the same file and)
> > contains '\\end{document}' at that point.
> > 
> > And this '\\end{document}' itself comes from files in the
> > packaging-tutorial po4a directory.
> > 
> > So I don't know if po4a needs a generic fix, or packaging-tutorial
> > needs to change how it uses it.
> 
> I would be unable to generate a patch for the first option. My perl is
> rather rotten nowadays. 

I also think it would be difficult; all tha po4a sees at this point
is a string, and it's probably impossible to preprocess it into a
regexp.

What po4a could maybe do is to mention in the documentation that the
string in "position=something" in addendums will be interpreted as a
Perl regexp later.

> I think that the second option is sensible:
> packaging-tutorial is providing some code that is interpreted by po4a,
> so it should ensure that it provides correct code.

I tend to agree. (And it aleady escapes the backslash.)
 

Lucas, what do you think?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#865429: libc6-dev-i386: gcc-multilib should not be recommended

[Aurelien Jarno]

On 2017-06-21 13:54, Vincent Lefevre wrote:
> Package: libc6-dev-i386
> Version: 2.24-12
> Severity: normal
> 
> The libc6-dev-i386 package has:
> 
>   Recommends: gcc-multilib
> 
> But recommended packages are installed by default, and the above
> "Recommends:" is too strong as gcc-multilib is not the only way to
> use libc6-dev-i386.

This is actually not correct. gcc-multilib is required even for
compiling with another gcc-X-mutilib compiler as it provides the
/usr/include/linux/asm symlink.

I'll therefore revert the change in the next upload. Feel free to report
bugs against gcc-multilib or gcc-X-multilib if you feel it's provided in
the wrong package.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#872039: initscripts: umountfs leaves /var mounted (rw)

[Elrond]

Package: initscripts
Version: 2.88dsf-59.9
Severity: serious
Tags: patch


Hi,


Reason for Severity=serious: This leaves /var (or other
filesystems) in an unclean state, so could possibly lead to
data loss!
(not to mention the lengthy fsck at every boot.)


umountfs in stretch changed the sed-calculation of
ROTECTED_MOUNTS. The new one includes /var on my system:

# sed -n ':a;/^[^ ]* \(\/\|\/usr\) /!{H;n;ba};{H;s/.*//;x;s/\n//;p}' 
/proc/mounts
/dev/root / ext2 rw,relatime,errors=continue 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=305176k,mode=755 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,relatime,size=10240k,nr_inodes=381118,mode=755 0 0
tmpfs /run/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=610340k 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
/dev/mapper/intvg1-sys_var /var ext2 rw,relatime,errors=continue 0 0
/dev/md3 /boot ext2 ro,relatime,errors=continue 0 0
/dev/mapper/intvg1-sys_usr /usr ext2 rw,relatime,errors=continue 0 0

The new sed was likely changed to include /usr in the list
of protected filesystems (it's remounted ro later).
But the new version basicly means (at least, I understand
it that way): Include all filesystems in ROTECTED_MOUNTS,
that are above the last mention of / or /usr.  While the
old one was about / only.


I propose to undo the sed changes and include /usr in the
specific list of filesystems to exclude from unmounting.

See attached patch.


Can you please try to include a fix in the next point
release of stretch?


Cheers

Elrond
--- umountfs.orig	2017-07-20 09:23:26.0 +0200
+++ umountfs	2017-08-13 19:24:16.0 +0200
@@ -17,7 +17,7 @@
 umask 022
 
 do_stop () {
-	PROTECTED_MOUNTS="$(sed -n ':a;/^[^ ]* \(\/\|\/usr\) /!{H;n;ba};{H;s/.*//;x;s/\n//;p}' /proc/mounts)"
+	PROTECTED_MOUNTS="$(sed -n ':a;/^[^ ]* \/ /!{H;n;ba};{H;s/.*//;x;s/\n//;p}' /proc/mounts)"
 	WEAK_MTPTS="" # be gentle, don't use force
 	REG_MTPTS=""
 	TMPFS_MTPTS=""
@@ -25,7 +25,7 @@
 	do
 		echo "$PROTECTED_MOUNTS" | grep -qs "^$DEV $MTPT " && continue
 		case "$MTPT" in
-		  /|/proc|/dev|/.dev|/dev/pts|/dev/shm|/dev/.static/dev|/proc/*|/sys|/sys/*|/run|/run/*|/dev/vcs)
+		  /|/usr|/proc|/dev|/.dev|/dev/pts|/dev/shm|/dev/.static/dev|/proc/*|/sys|/sys/*|/run|/run/*|/dev/vcs)
 			continue
 			;;
 		esac

Bug#872043: opencv: CVE-2016-1516 CVE-2016-1516

[Salvatore Bonaccorso]

Source: opencv
Version: 2.4.9.1+dfsg1-2
Severity: important
Tags: upstream security
Forwarded: https://github.com/opencv/opencv/issues/5956

Hi,

the following vulnerabilities were published for opencv.

CVE-2016-1516[0]:
| OpenCV 3.0.0 has a double free issue that allows attackers to execute
| arbitrary code.

CVE-2016-1516[1]:
| OpenCV 3.0.0 has a double free issue that allows attackers to execute
| arbitrary code.

Unfortunately the reporters are not helping out upstream to identify
the issues, and after several pings still not replies. Filling this
bug so we are able to track in Debian the status about those issues in
the BTS.

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-1516
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1516
[1] https://security-tracker.debian.org/tracker/CVE-2016-1516
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1516

Please adjust the affected versions in the BTS as needed, none
versions were really testable. The report mentions 3.0.0 but might
affect any version.

Regards,
Salvatore

Bug#872042: lintian: please check for missing calls to dpkg-maintscript-helper

[Chris Lamb]

Package: lintian
Version: 2.5.52
Severity: wishlist

Hi

Please check for missing calls to dpkg-maintscript-helper(1) in
maintainer scripts.

They require coordinated actions from several maintainer scripts
and can be easily missed.


Regards,

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

Bug#865633: [Pkg-libvirt-maintainers] Bug#865633: can't drag windows or click "Activities" in GNOME 3 guest

[Daniel Pocock]

On 13/08/17 10:17, Petter Reinholdtsen wrote:
> This RC issue has caused virt-viewer to be thrown out of testing.  Anyone
> got any idea how to fix it?
> 

I did a full reboot of the physical host and the guest VM and after that
I was able to connect successfully from virt-viewer on stretch.

This is not ideal though.  Has anybody else seen the issue?

Bug#872043: opencv: CVE-2016-1516 CVE-2016-1516

[Salvatore Bonaccorso]

Control: retitle -1 opencv: CVE-2016-1516 CVE-2016-1517

On Sun, Aug 13, 2017 at 08:39:14PM +0200, Salvatore Bonaccorso wrote:
> Source: opencv
> Version: 2.4.9.1+dfsg1-2
> Severity: important
> Tags: upstream security
> Forwarded: https://github.com/opencv/opencv/issues/5956
> 
> Hi,
> 
> the following vulnerabilities were published for opencv.
> 
> CVE-2016-1516[0]:
> | OpenCV 3.0.0 has a double free issue that allows attackers to execute
> | arbitrary code.
> 
> CVE-2016-1516[1]:
> | OpenCV 3.0.0 has a double free issue that allows attackers to execute
> | arbitrary code.

One of those should have been CVE-2016-1517.

Sorry about that. So to reiterate, the two CVEs are CVE-2016-1516 and
CVE-2016-1517.

Regards,
Salvatore

Bug#834239: blends-tasks: Add FreedomBox to debian-blends-tasks

[Andreas Tille]

Hi Mike,

On Sat, Aug 12, 2017 at 05:42:39AM +, Mike Gabriel wrote:
> HI James, hi Andreas,
> 
> On  Sa 13 Aug 2016 18:36:02 CEST, James Valleroy wrote:
> 
> > Package: blends-tasks
> > Severity: wishlist
> > Tags: patch
> > 
> > Dear Maintainer,
> > 
> > The attached patch will add FreedomBox to the blends tasks list, shown
> > in Debian installer.
> > 
> > Note one issue: Selecting this item will install freedombox-setup
> > package, but that is not quite sufficient to get a working FreedomBox.
> > The user will need to run /usr/lib/freedombox/setup and reboot, to
> > complete the setup process.
> > 
> > We are working to resolve this issue. But, I'm hoping that it is not so
> > bad that it would prevent FreedomBox from being added to the list.
> 
> @Andreas: is there any reason for not applying the provided patch for
> FreedomBox inclusion? Shall I apply the provided patch for the 0.6.99
> upload?

The reason is that the installer does not really use this method (see
bug #847132)
 
> OT here, but still... The GPG clean room people (Daniel Pocock) might also
> be interested in a Debian Blend.

Fine for me.  I discussed the issue here at DebConf and there might be a
solution in the future. 

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#871996: suds FTBFS: TypeError: putenv() argument 2 must be string without null bytes, not str

[Adrian Bunk]

Source: suds
Version: 0.7~git20150727.94664dd-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes suds FTBFS:

https://tests.reproducible-builds.org/debian/history/suds.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/suds.html

...
= test session starts ==
platform linux2 -- Python 2.7.13+, pytest-3.2.0, py-1.4.34, pluggy-0.4.0
rootdir: /build/1st/suds-0.7~git20150727.94664dd, inifile: setup.cfg
collected 1846 items

tests/test_argument_parser.py 
.x.x..
tests/test_cache.py 

tests/test_client.py ..
tests/test_compare_sax.py 

tests/test_date_time.py 
.
tests/test_dependency_sort.py .
tests/test_document_store.py .
tests/test_input_parameters.py x.x...
tests/test_mx.py ..
tests/test_plugin.py 
tests/test_reader.py .
tests/test_reply_handling.py ...x...
tests/test_request_construction.py 
xx.x.xxxx.xx.x.xx.
tests/test_sax_document.py .
tests/test_sax_element.py 
tests/test_sax_encoder.py 
...xxx...xxx.
tests/test_suds.py xx
tests/test_timezone.py 
tests/test_transport.py 
EE.EE.
tests/test_transport_http.py 
.......
tests/test_xsd_builtins.py 
.
tests/test_xsd_element.py 
.

 ERRORS 
__ ERROR at setup of TestRequest.test_URL[�] ___

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'.pybuild/pythonX.Y_2.7/build/tests/test_transport.py::TestRequest::()::test_URL[\x00]
 (setup)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
_ ERROR at teardown of TestRequest.test_URL[�] _

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'.pybuild/pythonX.Y_2.7/build/tests/test_transport.py::TestRequest::()::test_URL[\x00]
 (teardown)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
 ERROR at setup of TestRequest.test_URL[Jurko�] 

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'.pybuild/pythonX.Y_2.7/build/tests/test_transport.py::TestRequest::()::test_URL[Jurko\x00]
 (setup)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

Bug#871997: usbguard-applet-qt: multiple instances

[Christian Göttsche]

Package: usbguard-applet-qt
Version: 0.7.0+ds1-1
Severity: important

Please incorporate the upstream fix for an issue with multiple instances.

Bug: https://github.com/dkopecek/usbguard/issues/160
Patch: 
https://github.com/dkopecek/usbguard/commit/f96794a76f02833c77a2218d1820164cf06839c7

Thanks in advance,
Christian Göttsche

Bug#872002: libxaw7: mixing international and non-international asciiTextWidgets segfaults

[Johann Klammer]

Package: libxaw7
Version: 2:1.0.12-2
Severity: normal

The text widgets have this resource, XtNinternational. 
It is a boolean.
If it is set to True for one Widget, and False for another, 
a call to XtSetValues to set the text will crash the application.

compile the testcase using:
cc -std=gnu99 -DBUG -D_REENTRANT -DDMALLOC_DISABLE -D_FORTIFY_SOURCE=2 -g -Os 
-fno-common -fstrict-aliasing -fstack-protector -Wall -Wextra -lXext -lX11 -lXt 
-lXaw ./asciitext.c

Then:

gdb ./a.out
[...]
(gdb) run
Starting program: 
/home/klammerj/projects/fixes/libxaw-1.0.12/debian/patches/a.out 




Program received signal SIGSEGV, Segmentation fault.
0xb7d87397 in AsciiPreparePaint (w=0x0, y=2, line=257, from=0, to=26, 
highlight=0) at ../../src/AsciiSink.c:518
warning: Source file is more recent than executable.
518 ascent = XawMax(sink->ascii_sink.font->ascent, ascent);

(gdb) bt
#0  0xb7d87397 in AsciiPreparePaint (w=0x0, y=2, line=257, from=0, to=26, 
highlight=0) at ../../src/AsciiSink.c:518
#1  0xb7dacb18 in XawTextSinkPreparePaint (w=0x806deb0, y=2, line=0, from=0, 
to=26, highlight=0) at ../../src/TextSink.c:938
#2  0xb7da43db in DisplayText (w=0x806ccd8, left=, right=493) at 
../../src/Text.c:2792
#3  0xb7da415c in FlushUpdate (ctx=0x806ccd8) at ../../src/Text.c:3329
#4  0xb7da8a5b in _XawTextExecuteUpdate (ctx=0x806ccd8) at ../../src/Text.c:3600
#5  0xb7da9292 in _XawTextSetSource (w=0x806ccd8, source=0x806e1e0, 
top=, startPos=) at ../../src/Text.c:3891
#6  0xb7da9712 in XawTextSetSource (w=0x806ccd8, source=0x806e1e0, top=0) at 
../../src/Text.c:3901
#7  0xb7d974f4 in XawMultiSrcSetValues (current=0xbfffdf18, request=0xbfffe238, 
cnew=0x806e1e0, args=0xbfffeea0, num_args=0xbfffdd4c) at 
../../src/MultiSrc.c:840
#8  0xb7e196a0 in CallSetValues (class=0xb7de2980 , 
current=0xbfffdf18, request=0xbfffe238, new=0x806e1e0, args=0xbfffeea0, 
num_args=1)
at ../../src/SetValues.c:133
#9  0xb7e19a80 in XtSetValues (w=0x806e1e0, args=0xbfffeea0, num_args=1) at 
../../src/SetValues.c:269
#10 0xb7da94a5 in XawTextSetValues (current=0x0, request=0xbfffeb48, 
cnew=0x806ccd8, args=0xbfffeea0, num_args=0xbfffe61c) at ../../src/Text.c:3709
#11 0xb7e196a0 in CallSetValues (class=0xb7de4b40 , 
current=current@entry=0xbfffe828, request=0xbfffeb48, new=0x806ccd8, 
args=0xbfffeea0, num_args=1)
at ../../src/SetValues.c:133
#12 0xb7e19659 in CallSetValues (class=0xb7de1480 , 
current=0xbfffe828, request=0xbfffeb48, new=0x806ccd8, args=0xbfffeea0, 
num_args=1)
at ../../src/SetValues.c:126
#13 0xb7e19f8b in XtSetValues (w=0x806ccd8, args=0xbfffeea0, num_args=1) at 
../../src/SetValues.c:269
#14 0x08048ddc in set_string (w=0x80654c8, client_data=0x0, call_data=0x0) at 
./asciitext.c:53
#15 0xb7df5027 in XtCallCallbackList (widget=0x80654c8, callbacks=0x8065fb0, 
call_data=0x0) at ../../src/Callback.c:625
#16 0xb7d8baad in Notify (w=0x80654c8, event=0xb38c, params=0x0, 
num_params=0x80651b8) at ../../src/Command.c:413
#17 0xb7e2914c in HandleActions (w=w@entry=0x80654c8, event=0xb38c, 
accelWidget=, procs=0x8069294, actions=, 
stateTree=)
at ../../src/TMstate.c:644
#18 0xb7e29555 in HandleSimpleState (w=w@entry=0x80654c8, 
tmRecPtr=tmRecPtr@entry=0x80654f8, curEventPtr=0xb0b8) at 
../../src/TMstate.c:883
---Type  to continue, or q  to quit---
#19 0xb7e2a493 in _XtTranslateEvent (w=0x80654c8, event=0xb38c) at 
../../src/TMstate.c:1101
#20 0xb7e02b9d in XtDispatchEventToWidget (widget=0x80654c8, event=0xb38c) 
at ../../src/Event.c:906
#21 0xb7e032a0 in _XtDefaultDispatcher (event=0xb38c) at 
../../src/Event.c:1367
#22 0xb7e0341b in XtDispatchEvent (event=0xb38c) at ../../src/Event.c:1423
#23 0xb7e0f128 in XtAppProcessEvent (app=0x804d868, mask=15) at 
../../src/NextEvent.c:1397
#24 0xb7e0386b in XtAppMainLoop (app=0x804d868) at ../../src/Event.c:1554
#25 0x08048c91 in main (argc=1, argv=0xb5c4) at ./asciitext.c:169


As far as I can tell the cast at line 440 in AsciiSink.c does the damage.
(it is actually a MultiSink)
But it is possible it took a wrong turn at some function pointer further up.

compile without -DBUG and it will work.(omits the non-intl box)

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include
#include
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

static void quit (Widget w, XEvent * event, String * params,
  Cardinal * num_params);

static Atom wm_delete_window;
static XtActionsRec devgui_actions[] = {
  {"quit", quit},
};

static char *test = "(Dokumentation, AUT 2011)\n\
Viermal im Leben umrunden wir in ihnen den Erdball. Sie geben uns Geborgenheit, manchmal quälen sie uns auch: Schuhe. Kein anderes Kleidungsstück hat so viele Spuren in der Menschheitsgeschichte hinterlassen und ist mit so vielen Botschaften und Zeichen behaftet. Schuhe erzählen viel von Menschen. Und 

Bug#868431: wmaker: uses static upstream menu

[Doug Torrance]

On 08/13/2017 08:22 AM, Andreas Metzler wrote:

On 2017-08-13 Doug Torrance  wrote:

On 08/07/2017 08:51 AM, Andreas Metzler wrote:

On 2017-07-29 Andreas Metzler  wrote:

On 2017-07-29 Andreas Metzler  wrote:

[...]

#1 Providing a new full menu in /etc/GNUstep/Defaults/WMRootMenu does
not make the new content available to users. Anybody who has started
wmaker before will continue using ~/GNUstep/Defaults/WMRootMenu which
references "menu.hook". So I think we need to provide a file named
menu.hook in wmaker's search path with the new content.

[...]

Afaict #1 only has an imperfect solution, shipping the menu in
/usr/share/WindowMaker/menu.hook.

[...]


which does not seem to work, since with a WMRootMenu consisting of
"menu.hook"
  

wmaker expects the menu.hook file to contain a menu file in plain-text,
i.e. non proplist format.



Okay. Plan C (commited to GIT for review):
* Revert WMRootMenu to contain just "menu.hook".
* Convert dynamic menu to old style format and install it as
/etc/GNUstep/Defaults/menu.Debian
* Symlink /etc/GNUstep/Defaults/menu.Debian to
/usr/share/WindowMaker/menu.hook to let WMRootMenu use it.
* Ship dynamic plmenu in wmaker-common examples.



I just submitted a patch upstream which would allow WMRootMenu to point to
the new menu in proplist format.  If we include the patch, then we wouldn't
need to ship both formats, and we could use your "imperfect solution" from
above.


I am all for not shipping two formats, but also firmly believe that our
menu should live in /etc/.


Is menu.hook (or whatever we end up calling it) really a configuration file?
WMRootMenu definitely is, but there are tons of of other menu files already
in /usr/share/WindowMaker.  These just serve as defaults/examples, and
aren't configuring anything unless WMRootMenu points to them.


They are a little bit more than examples, they are also fallbacks if the
normal menu is unreadable.


So I think
there's an argument for putting menu.hook in /usr/share/WindowMaker,
pointing WMRootMenu to it, and not violating policy.


I think that makes it unnecessary hard for a sysadmin to customize the
menu. If menu.hook lives in /etc [1] he/she just edits the menu and
stuff works. If not he/she needs to edit
/etc/GNUstep/Defaults/WMRootMenu *and* needs to make sure that
~/GNUstep/Defaults/WMRootMenu of every user is updated.


Sounds good.  I've added the patch and removed the old-style menu in git.


Out of curiosity, why not use dpkg-maintscript-helper to remove
appearance.menu and menu.hook as you did for wmappearance and menu-methods?


Afaiui dpkg-maintscript-helper only handles dpkg-conffiles.


Ok, that makes sense.  I deleted the blurb in d/changelog about deleting 
all the maintainer scripts.


Have a good one,
Doug

Bug#872012: [tex-common] Installing fails due to fmtutil failure

[Norbert Preining]

severity 872012 normal
tags 872012 + moreinfo unreproducible
thanks

Hi Holger,

> in a clean sid chroot, I tried to install tex-common package, which fails,
> because of fmtutil failure:

Very unlikely that you only installed tex-common into a clean chroot,
because there are many formats that need at least texlive-latex-base.

Here is a log that shows a *real* installation into a clean chroot:
root@bulldog:/root/# cowbuilder --login
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.6585
I: forking: cp -al /var/cache/pbuilder/base.cow 
/var/cache/pbuilder/build/cow.6585
I: removed stale ilistfile /var/cache/pbuilder/build/cow.6585/.ilist
I: Invoking pbuilder
I: forking: pbuilder login --buildplace /var/cache/pbuilder/build/cow.6585 
--no-targz --internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.6585 
cow-shell'
W: /root/.pbuilderrc does not exist
I: Running in no-targz mode
I: copying local configuration
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: mounting /dev/pts/3 over /dev/console
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: entering the shell
root@bulldog:/# apt-get update 
Get:1 http://ftp.nara.wide.ad.jp/debian sid InRelease [228 kB]
Get:2 http://ftp.nara.wide.ad.jp/debian sid/main amd64 Packages.diff/Index 
[27.9 kB]
Get:3 http://ftp.nara.wide.ad.jp/debian sid/main Translation-en.diff/Index 
[27.9 kB]
Get:4 http://ftp.nara.wide.ad.jp/debian sid/contrib amd64 Packages.diff/Index 
[27.8 kB]
Get:5 http://ftp.nara.wide.ad.jp/debian sid/main amd64 Packages 
2017-08-13-0216.43.pdiff [14.5 kB]
Get:6 http://ftp.nara.wide.ad.jp/debian sid/main amd64 Packages 
2017-08-13-0816.47.pdiff [4358 B]
Get:6 http://ftp.nara.wide.ad.jp/debian sid/main amd64 Packages 
2017-08-13-0816.47.pdiff [4358 B]
Get:7 http://ftp.nara.wide.ad.jp/debian sid/main Translation-en 
2017-08-13-0216.43.pdiff [3950 B]
Get:8 http://ftp.nara.wide.ad.jp/debian sid/main Translation-en 
2017-08-13-0816.47.pdiff [408 B]
Get:8 http://ftp.nara.wide.ad.jp/debian sid/main Translation-en 
2017-08-13-0816.47.pdiff [408 B]
Get:9 http://ftp.nara.wide.ad.jp/debian sid/contrib amd64 Packages 
2017-08-13-0816.47.pdiff [567 B]
Get:9 http://ftp.nara.wide.ad.jp/debian sid/contrib amd64 Packages 
2017-08-13-0816.47.pdiff [567 B]
Fetched 336 kB in 1s (278 kB/s) 
   
Reading package lists... Done
root@bulldog:/# apt-get install tex-common
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  ucf
Suggested packages:
  debhelper
The following NEW packages will be installed:
  tex-common ucf
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/636 kB of archives.
After this operation, 1047 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package ucf.
(Reading database ... 14688 files and directories currently installed.)
Preparing to unpack .../archives/ucf_3.0036_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0036) ...
Selecting previously unselected package tex-common.
Preparing to unpack .../tex-common_6.07_all.deb ...
Unpacking tex-common (6.07) ...
Setting up ucf (3.0036) ...
Setting up tex-common (6.07) ...
update-language: texlive-base not installed and configured, doing nothing!
root@bulldog:/# 

Don't know what to say ...

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#872026: openafs: French debconf translation update

[Alban Vidal]

Package: openafs
Version: 1.6.21-1
Severity: wishlist
Tags: patch l10n

Please find attached the French debconf templates update, proofread by the
debian-l10n-french mailing list contributors.

Best regards

Alban Vidal
# Translation of openafs debconf templates to French
# Copyright (C) 2006, 2013, 2017 Debian French l10n team 

# This file is distributed under the same license as the openafs package.
#
# translation of fr.po to French
#
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections dedicated to
#this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
#Some information specific to po-debconf are available at
#/usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
#Developers do not need to manually edit POT or PO files.
#
# Translators:
# Christian Perrier , 2006, 2013.
# Alban Vidal , 2017.
msgid ""
msgstr ""
"Project-Id-Version: openafs 1.6.21-1\n"
"Report-Msgid-Bugs-To: open...@packages.debian.org\n"
"POT-Creation-Date: 2017-07-10 15:27-0500\n"
"PO-Revision-Date: 2017-08-04 10:36+0100\n"
"Last-Translator: Alban Vidal \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 2.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid "DB server host names for your home cell:"
msgstr ""
"Hôtes serveurs de bases de données pour votre cellule locale (« home "
"cell ») :"

#. Type: string
#. Description
#: ../openafs-client.templates:1001
msgid ""
"AFS uses the file /etc/openafs/CellServDB to hold the list of servers that "
"should be contacted to find parts of a cell.  The cell you claim this "
"workstation belongs to is not in that file.  Enter the host names of the "
"database servers separated by spaces. IMPORTANT: If you are creating a new "
"cell and this machine is to be a database server in that cell, only enter "
"this machine's name; add the other servers later after they are functioning. "
"Also, do not enable the AFS client to start at boot on this server until the "
"cell is configured.  When you are ready you can edit /etc/openafs/afs.conf."
"client to enable the client."
msgstr ""
"AFS utilise le fichier /etc/openafs/CellServDB pour conserver la liste des "
"serveurs à contacter pour trouver les constituants d'une cellule. La cellule "
"dont ce poste de travail est censé faire partie n'est pas indiquée dans ce "
"fichier. Veuillez indiquer les noms des serveurs de bases de données, "
"séparés par des espaces. IMPORTANT : si vous créez une nouvelle cellule et "
"que cette machine doit être un serveur de bases de données dans cette "
"cellule, veuillez seulement indiquer le nom de cette machine. N'ajoutez les "
"autres serveurs que plus tard, lorsqu'ils seront opérationnels. Enfin, "
"n'activez pas le client AFS au démarrage tant que cette cellule n'est pas "
"configurée. Quand vous serez prêt, vous pourrez modifier /etc/openafs/afs."
"conf.client pour mettre en service le client."

#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid "AFS cell this workstation belongs to:"
msgstr "Cellule AFS dont ce poste de travail fait partie :"

#. Type: string
#. Description
#: ../openafs-client.templates:2001
msgid ""
"AFS filespace is organized into cells or administrative domains. Each "
"workstation belongs to one cell.  Usually the cell is the DNS domain name of "
"the site."
msgstr ""
"L'espace des fichiers AFS est organisé en cellules ou domaines "
"administratifs. Chaque poste de travail appartient à une cellule. "
"Habituellement, la cellule est le nom de domaine du site."

#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid "Size of AFS cache in kB:"
msgstr "Taille du cache d'AFS (ko) :"

#. Type: string
#. Description
#: ../openafs-client.templates:3001
msgid ""
"AFS uses an area of the disk to cache remote files for faster access.  This "
"cache will be mounted on /var/cache/openafs.  It is important that the cache "
"not overfill the partition it is located on.  Often, people find it useful "
"to dedicate a partition to their AFS cache."
msgstr ""
"AFS utilise une partie du disque pour mettre en cache des fichiers distants "
"et accélérer les accès. Ce cache sera monté sur /var/cache/openafs. Il est "
"important que le cache ne remplisse pas la partition sur laquelle il est "
"situé. De nombreux utilisateurs choisissent de dédier une partition au cache "
"d'AFS."

#. Type: boolean
#. Description
#: ../openafs-client.templates:4001
msgid "Run Openafs client now and at boot?"
msgstr "Faut-il lancer le client AFS maintenant, 

Bug#870834: Bug is due to an API break in GLib

[Uli Schlachter]

Hi,

FYI, the bug was already reported upstream:

https://github.com/pavouk/lgi/issues/167

The reason seems to be a (GObject-introspection) API break in GLib.
Previously g_object_newv was [rename-to g_object_new], but now this
annotation is on g_object_new_with_properties().

If you ask me, this is a regression in GLib, but I guess only breaking
the C API is considered an API break and the introspection API has no
stable guarantees, right?

Cheers,
Uli
-- 
Sent from my Game Boy.

Bug#869895: installations-reports: Install on Apple iBook G4 A1133 sid netinst 20170614

[Mathieu Malaterre]

On Thu, Jul 27, 2017 at 3:18 PM, John Paul Adrian Glaubitz
 wrote:
> On 07/27/2017 03:14 PM, Mathieu Malaterre wrote:
>> Did you notice the red/blue inversion during install ? It appears you
>> are using radeonfb, so I just wanted to make that clear from the
>> report.
>
> Yes, the standard background was red while the error background was
> blue. The rest of the colors seemed normal to me, however.

Great, thanks. Technically you could get radeonfb (instead of offb) to
load with the patch:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826629#71

> Another issue I observed is that suspend doesn't seem to work reliably,
> suspending works when the lid is closed. However, the machine doesn't
> wake up again upon opening the lid again.

Can you try again with package pbbuttonsd installed ?

Thanks

Bug#871987: openssl breaks dovecot

[Sebastian Andrzej Siewior]

On 2017-08-13 11:13:25 [+0200], Harald Dunkel wrote:
> Since the upgrade to 1.1.0f-4 I cannot read EMails via imap from 
> my old ipad anymore (unless I disable encryption). Moving back to 
> 1.1.0f-3 fixes the problem.
is blue mail working?

Sebastian

Bug#870103: freeplane: a Java (knopflerfish) exception will prevent freeplane from starting

[Felix Natter]

hello Sophoklis,

unfortunately I cannot reproduce this, but I'll look into it.

Does that file exist (could be a permission problem...)?

Could you try to touch that file (as root) as a possible workaround?
If that doesn't work, try to "sudo cp" the attached "props.xargs" to
/usr/share/freeplane/fwdir/fwprops.xargs?

Cheers and Best Regards,
-- 
Felix Natter


props.xargs
Description: Binary data

Bug#872041: OpenJPEG 2.2.0 is out !

[Mathieu Malaterre]

Source: openjpeg2
Version: 2.1.2-1.1
Severity: normal

A new version is available, please package it.

Thanks

Bug#872044: opencv: CVE-2017-12597 CVE-2017-12598 CVE-2017-12599 CVE-2017-12601 CVE-2017-12603 CVE-2017-12604 CVE-2017-12605 CVE-2017-12606

[Salvatore Bonaccorso]

Source: opencv
Version: 2.4.9.1+dfsg1-2
Severity: important
Tags: upstream security
Forwarded: https://github.com/opencv/opencv/issues/9309

Hi,

the following vulnerabilities were published for opencv. I'm still not
filling them as individual bugs, since all are tracked in the upstream
report at [8]. I suggest though to split the bug as eneeded up once
more details are sorted out/and or fixes available making clear the
set of affected versions.

CVE-2017-12597[0]:
| OpenCV (Open Source Computer Vision Library) through 3.3 has an
| out-of-bounds write error in the function FillColorRow1 in utils.cpp
| when reading an image file by using cv::imread.

CVE-2017-12598[1]:
| OpenCV (Open Source Computer Vision Library) through 3.3 has an
| out-of-bounds read error in the cv::RBaseStream::readBlock function in
| modules/imgcodecs/src/bitstrm.cpp when reading an image file by using
| cv::imread, as demonstrated by the 8-opencv-invalid-read-fread test
| case.

CVE-2017-12599[2]:
| OpenCV (Open Source Computer Vision Library) through 3.3 has an
| out-of-bounds read error in the function icvCvt_BGRA2BGR_8u_C4C3R when
| reading an image file by using cv::imread.

CVE-2017-12601[3]:
| OpenCV (Open Source Computer Vision Library) through 3.3 has a buffer
| overflow in the cv::BmpDecoder::readData function in
| modules/imgcodecs/src/grfmt_bmp.cpp when reading an image file by using
| cv::imread, as demonstrated by the 4-buf-overflow-readData-memcpy test
| case.

CVE-2017-12603[4]:
| OpenCV (Open Source Computer Vision Library) through 3.3 has an invalid
| write in the cv::RLByteStream::getBytes function in
| modules/imgcodecs/src/bitstrm.cpp when reading an image file by using
| cv::imread, as demonstrated by the 2-opencv-heapoverflow-fseek test
| case.

CVE-2017-12604[5]:
| OpenCV (Open Source Computer Vision Library) through 3.3 has an
| out-of-bounds write error in the FillUniColor function in utils.cpp
| when reading an image file by using cv::imread.

CVE-2017-12605[6]:
| OpenCV (Open Source Computer Vision Library) through 3.3 has an
| out-of-bounds write error in the FillColorRow8 function in utils.cpp
| when reading an image file by using cv::imread.

CVE-2017-12606[7]:
| OpenCV (Open Source Computer Vision Library) through 3.3 has an
| out-of-bounds write error in the function FillColorRow4 in utils.cpp
| when reading an image file by using cv::imread.

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-12597
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12597
[1] https://security-tracker.debian.org/tracker/CVE-2017-12598
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12598
[2] https://security-tracker.debian.org/tracker/CVE-2017-12599
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12599
[3] https://security-tracker.debian.org/tracker/CVE-2017-12601
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12601
[4] https://security-tracker.debian.org/tracker/CVE-2017-12603
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12603
[5] https://security-tracker.debian.org/tracker/CVE-2017-12604
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12604
[6] https://security-tracker.debian.org/tracker/CVE-2017-12605
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12605
[7] https://security-tracker.debian.org/tracker/CVE-2017-12606
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12606
[8] https://github.com/opencv/opencv/issues/9309

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#871185: [Pkg-ime-devel] Bug#871185: ibus-kkc: FTBFS with vala 0.36

[Mitsuya Shibata]

Owner: mty.shib...@gmail.com

Hi Jeremy,

Thank you for your reporting and patch.

I pushed fixed and new upstream code to package's vcs,
and uploaded to mentors.debian.net.
If package's information will be appeared, then I will send request sponsorship.

Regards,
-- 
Mitsuya Shibata

Bug#871991: sbuild: please add build-essential to the sbuild-build-depends-foobar-dummy package

[Johannes Schauer]

Package: sbuild
Version: 0.73.0-4
Severity: normal

Currently, the dummy package created by sbuild to satisfy build
dependencies does not depend on (cross)build-essential. This can lead to
the situation that the resolver or the explainer removes build-essential
to be able to satisfy the dependencies. This should not happen.

Instead, add (cross)build-essential to the Depends or even merge the
dummy binary package with the other package for the core dependencies.

Bug#871995: astroscrappy FTBFS: AttributeError: 'NoneType' object has no attribute 'lineno'

[Adrian Bunk]

Source: astroscrappy
Version: 1.0.5-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes astroscrappy FTBFS:

https://tests.reproducible-builds.org/debian/history/astroscrappy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/astroscrappy.html

...
Numpy: 1.12.1
Scipy: 0.18.1
Matplotlib: not available
Pandas: not available
Astropy: 2.0.1
Using Astropy options: remote_data: none.

rootdir: /tmp/astroscrappy-test-1Xfh3S, inifile: setup.cfg
collecting ... collected 26 items

astroscrappy/tests/test_astroscrappy.py::test_main PASSED
astroscrappy/tests/test_cleaning.py::test_median_clean PASSED
astroscrappy/tests/test_cleaning.py::test_medmask_clean PASSED
astroscrappy/tests/test_cleaning.py::test_meanmask_clean PASSED
astroscrappy/tests/test_cleaning.py::test_idw_clean PASSED
astroscrappy/tests/test_utils.py::test_median PASSED
astroscrappy/tests/test_utils.py::test_optmed3 PASSED
astroscrappy/tests/test_utils.py::test_optmed5 PASSED
astroscrappy/tests/test_utils.py::test_optmed7 PASSED
astroscrappy/tests/test_utils.py::test_optmed9 PASSED
astroscrappy/tests/test_utils.py::test_optmed25 PASSED
astroscrappy/tests/test_utils.py::test_medfilt3 PASSED
astroscrappy/tests/test_utils.py::test_medfilt5 PASSED
astroscrappy/tests/test_utils.py::test_medfilt7 PASSED
astroscrappy/tests/test_utils.py::test_sepmedfilt3 PASSED
astroscrappy/tests/test_utils.py::test_sepmedfilt5 PASSED
astroscrappy/tests/test_utils.py::test_sepmedfilt7 PASSED
astroscrappy/tests/test_utils.py::test_sepmedfilt9 PASSED
astroscrappy/tests/test_utils.py::test_dilate5 PASSED
astroscrappy/tests/test_utils.py::test_dilate3 PASSED
astroscrappy/tests/test_utils.py::test_subsample PASSED
astroscrappy/tests/test_utils.py::test_rebin PASSED
astroscrappy/tests/test_utils.py::test_laplaceconvolve PASSED
astroscrappy/tests/test_utils.py::test_convolve PASSED
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
110, in wrap_session
INTERNALERROR> session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
146, in _main
INTERNALERROR> config.hook.pytest_runtestloop(session=session)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
614, in execute
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 
169, in pytest_runtestloop
INTERNALERROR> item.config.hook.pytest_runtest_protocol(item=item, 
nextitem=nextitem)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
745, in __call__
INTERNALERROR> return self._hookexec(self, self._nonwrappers + 
self._wrappers, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
339, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
334, in 
INTERNALERROR> _MultiCall(methods, kwargs, hook.spec_opts).execute()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> _reraise(*ex)  # noqa
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
265, in __init__
INTERNALERROR> self.result = func()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
613, in execute
INTERNALERROR> return _wrapped_call(hook_impl.function(*args), self.execute)
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
254, in _wrapped_call
INTERNALERROR> return call_outcome.get_result()
INTERNALERROR>   File 
"/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py", line 
280, in get_result
INTERNALERROR> 

Bug#871994: python-cryptography FTBFS: TypeError: putenv() argument 2 must be string without null bytes, not str

[Adrian Bunk]

Source: python-cryptography
Version: 1.9-1
Severity: serious

Some recent change in unstable makes python-cryptography FTBFS:

https://tests.reproducible-builds.org/debian/history/python-cryptography.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-cryptography.html

...
 ERRORS 
 ERROR at setup of TestPKCS7.test_invalid_padding[128-] 

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestPKCS7::()::test_invalid_padding[128-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00]
 (setup)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
__ ERROR at teardown of TestPKCS7.test_invalid_padding[128-] ___

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestPKCS7::()::test_invalid_padding[128-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00]
 (teardown)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
__ ERROR at setup of TestANSIX923.test_invalid_padding[128-] ___

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestANSIX923::()::test_invalid_padding[128-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00]
 (setup)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
_ ERROR at teardown of TestANSIX923.test_invalid_padding[128-] _

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestANSIX923::()::test_invalid_padding[128-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00]
 (teardown)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
___ ERROR at setup of TestANSIX923.test_pad[128-11-11�] ___

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestANSIX923::()::test_pad[128-11-11\x00\x00\x00\x00\x00\x06]
 (setup)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
_ ERROR at teardown of TestANSIX923.test_pad[128-11-11�] __

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': '1'}
key = 'PYTEST_CURRENT_TEST'
item = 
'tests/hazmat/primitives/test_padding.py::TestANSIX923::()::test_pad[128-11-11\x00\x00\x00\x00\x00\x06]
 (teardown)'

def __setitem__(self, key, item):
>   putenv(key, item)
E   TypeError: putenv() argument 2 must be string without null bytes, not 
str

/usr/lib/python2.7/os.py:473: TypeError
 ERROR at setup of 
TestANSIX923.test_pad[128-22-22�]
 

self = {'CPPFLAGS': '-Wdate-time -D_FORTIFY_SOURCE=2', 'DEB_BUILD_MULTIARCH': 
'x86_64-linux-gnu', 'http_proxy': 'http://127.0...-O2 -fstack-protector-strong 
-Wformat -Werror=format-security', 'DEB_TARGET_ARCH': 'amd64', 
'PERL_USE_UNSAFE_INC': 

Bug#872004: linux: Please enable CONFIG_SPI_PXA2XX

[russm]

Source: linux
Severity: wishlist

Dear Maintainer,

CONFIG_SPI_PXA2XX is necessary (but not sufficient) for keyboard/
trackpad support in new-model Apple MacBook Pro laptops. Please enable
this to ease use of the in-development keyboard/trackpad drivers.

https://github.com/cb22/macbook12-spi-driver/issues/9#issuecomment-307612240

Thank you.


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#872013: texlive-science-doc: Upgrading from texlive-math-extra causes conflict

[Russell Sim]

Package: texlive-science-doc
Version: 2017.20170809-1
Severity: normal

Dear Maintainer,

During the process of updating some texlive packages, I ended up in a situation
where a package was trying to overwrite a file from another texlive package.

I'm not sure what the correct process is here, but should texlive-science
conflict with texlive-math-extra so that this can't happen?

I did get into this situation by running an apt-get install command to try and
only upgrade a few texlive packages without updating everything.  So using apt-
get upgrade may have avoided this situation?  I don't really know.

Cheers,
Russell

sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libavformat56 libexiv2-13 libgif4 libjson-c3:i386 libnm-gtk-common libnma-
common libwebrtc-audio-processing-0 linux-image-3.10-3-amd64 linux-
image-3.13-1-amd64 linux-image-3.16.0-4-amd64
  linux-image-3.2.0-1-amd64 linux-image-3.2.0-2-amd64 linux-image-4.0.0-2-amd64
linux-image-4.3.0-1-amd64 texlive-math-extra tla tla-doc
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  texlive-science texlive-science-doc
The following NEW packages will be installed:
  texlive-science texlive-science-doc
0 upgraded, 2 newly installed, 0 to remove and 2114 not upgraded.
149 not fully installed or removed.
Need to get 52.4 MB of archives.
After this operation, 73.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.dk.debian.org/debian unstable/main amd64 texlive-science all
2017.20170809-1 [3,085 kB]
Get:2 http://ftp.dk.debian.org/debian unstable/main amd64 texlive-science-doc
all 2017.20170809-1 [49.3 MB]
Fetched 52.4 MB in 4s (11.2 MB/s)
(Reading database ... 756895 files and directories currently installed.)
Preparing to unpack .../texlive-science_2017.20170809-1_all.deb ...
Unpacking texlive-science (2017.20170809-1) ...
dpkg: error processing archive /var/cache/apt/archives/texlive-
science_2017.20170809-1_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/amstex.1.gz', which is also in
package texlive-math-extra 2016.20161008-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack .../texlive-science-doc_2017.20170809-1_all.deb ...
Unpacking texlive-science-doc (2017.20170809-1) ...
dpkg: error processing archive /var/cache/apt/archives/texlive-science-
doc_2017.20170809-1_all.deb (--unpack):
 trying to overwrite '/usr/share/doc/texlive-doc/amstex/base/README.gz', which
is also in package texlive-math-extra 2016.20161008-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/texlive-science_2017.20170809-1_all.deb
 /var/cache/apt/archives/texlive-science-doc_2017.20170809-1_all.deb



-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-rw-r-- 1 root staff 80 Jul 28  2012 /usr/local/share/texmf/ls-R
-rw-r--r-- 1 root root 1895 Aug 13 14:10 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Jan 17  2017 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root 

Bug#872034: apt: add option to autoremove while upgrading

[Felipe Sateler]

Package: apt
Version: 1.5~beta1
Severity: wishlist
Tags: upstream

Hi,

Since #855891 apt no longer autoremoves packages while upgrading. I
understand that #855891 is correct as the option was only documented for
install. Please add a new option for enabling the behavior on
upgrade/dist-upgrade, and ideally enabled by default for the apt
command.

Saludos

-- Package-specific info:

-- (/etc/apt/preferences present, but not submitted) --


-- (/etc/apt/preferences.d/apt-exp present, but not submitted) --


-- (/etc/apt/preferences.d/apt-listbugs present, but not submitted) --


-- (/etc/apt/preferences.d/syncthing present, but not submitted) --


-- (/etc/apt/sources.list present, but not submitted) --


-- (/etc/apt/sources.list.d/apt-file.sources present, but not submitted) --


-- (/etc/apt/sources.list.d/debug.sources present, but not submitted) --


-- (/etc/apt/sources.list.d/google-chrome.list present, but not submitted) --


-- (/etc/apt/sources.list.d/local-apt-repository.list present, but not 
submitted) --


-- (/etc/apt/sources.list.d/mono-xamarin.list present, but not submitted) --


-- (/etc/apt/sources.list.d/nilarimogard-webupd8-sid.sources present, but not 
submitted) --


-- (/etc/apt/sources.list.d/syncthing-release.sources present, but not 
submitted) --


-- (/etc/apt/sources.list.d/vscode.list present, but not submitted) --


-- (/etc/apt/sources.list.d/vscode.sources present, but not submitted) --


-- (/etc/apt/sources.list.d/yarn.sources present, but not submitted) --


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

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

Versions of packages apt depends on:
ii  adduser 3.116
ii  debian-archive-keyring  2017.5
ii  gpgv2.1.18-8
ii  init-system-helpers 1.49
ii  libapt-pkg5.0   1.5~beta1
ii  libc6   2.24-14
ii  libgcc1 1:7.1.0-13
ii  libgnutls30 3.5.14-2
ii  libstdc++6  7.1.0-13

Versions of packages apt recommends:
ii  ca-certificates  20161130+nmu1

Versions of packages apt suggests:
pn  apt-doc 
ii  aptitude0.8.8-1
ii  dpkg-dev1.18.24
ii  gnupg   2.1.18-8
ii  gnupg2  2.1.18-8
ii  powermgmt-base  1.31+nmu1
ii  python-apt  1.4.0~beta3+b1

-- no debconf information

Bug#872037: libvigrampex: Failure in MultiArrayPointoperatorsTest::testCombine2() [mips64el]

[Daniel Stender]

Source: libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Current Vigra FTBFS on mips64el [1]:


[ 63%] Building CXX object 
test/multiarray/CMakeFiles/test_multiarray.dir/testsuccess.cxx.o
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& /usr/bin/c++  -DHasHDF5 -DHasJPEG -DHasPNG -DHasTIFF 
-I/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include 
-I/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/include 
-I/usr/include/hdf5/serial  -std=c++11 -pthread -W -Wall -Wextra 
-Wno-unused-parameter -Wno-sign-compare -Wno-unused-variable -Wno-type-limits 
-g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2   -o CMakeFiles/test_multiarray.dir/testsuccess.cxx.o -c 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray/testsuccess.cxx
[ 65%] Linking CXX executable test_multiarray
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& /usr/bin/cmake -E cmake_link_script CMakeFiles/test_multiarray.dir/link.txt 
--verbose=1
/usr/bin/c++  -std=c++11 -pthread -W -Wall -Wextra -Wno-unused-parameter 
-Wno-sign-compare -Wno-unused-variable -Wno-type-limits -g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2  -rdynamic CMakeFiles/test_multiarray.dir/test.cxx.o 
CMakeFiles/test_multiarray.dir/testsuccess.cxx.o  -o test_multiarray 
-Wl,-rpath,/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/src/impex:/usr/lib/mips64el-linux-gnuabi64/hdf5/serial
 ../../src/impex/libvigraimpex.so.6.1.11.0 -ljpeg -lpng -lz -ltiff -lIlmImf 
-lImath -lHalf -lIex -lIlmThread 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5.so 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5_hl.so -lsz -lz -ltiff 
-lIlmImf -lImath -lHalf -lIex -lIlmThread 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5.so 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5_hl.so -lsz 
Running test_multiarray
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& ./run_test_multiarray.sh
Entering test suite MultiArrayTestSuite
All (24) tests passed in test suite MultiArrayTestSuite
Leaving test suite MultiArrayTestSuite

Entering test suite MultiArrayDataTestSuite
All (32) tests passed in test suite MultiArrayDataTestSuite
Leaving test suite MultiArrayDataTestSuite

Entering test suite ImageViewTestSuite
All (16) tests passed in test suite ImageViewTestSuite
Leaving test suite ImageViewTestSuite

Entering test suite MultiArrayPointOperatorsTestSuite

Failure in MultiArrayPointoperatorsTest::testCombine2()
Unexpected signal: memory access violation

Fatal error - aborting test suite MultiArrayPointOperatorsTestSuite.

test/multiarray/CMakeFiles/test_multiarray.dir/build.make:146: recipe for 
target 'test/multiarray/test_multiarray' failed
make[5]: *** [test/multiarray/test_multiarray] Error 1


DS

[1] 
https://buildd.debian.org/status/fetch.php?pkg=libvigraimpex=mips64el=1.10.0%2Bgit20160211.167be93%2Bdfsg-4=1502638529=0

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

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

Bug#872038: Dell Vostro 1000 not powering down. (Debian 9)

[Batman Forever]

Package: linux-image-4.9.0-3-amd64
Version: 4.9.30-2+deb9u3

Laptop does not power down.  Screen stays on.
This was working in Debian 8.

This might be related to APM not configured into the kernel?

#grep APM /boot/config-4.9.0-3-amd64

This does not return any options configured into the kernel for APM.
I had a similar issue with a Dell Latitude D505

grep APM config-4.9.0-3-686
CONFIG_X86_APM_BOOT=y
CONFIG_APM=n
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_ALLOW_INTS is not set

I set the CONFIG_AMP=y

This fixed the issue on the Dell Latitude D505.

Dell Vostro 1000 lspci output

lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI]
RS480/RS482/RS485 Host Bridge (rev 10)
00:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RC4xx/RS4xx PCI
Bridge [int gfx]
00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RC4xx/RS4xx PCI
Express Port 2
00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RC4xx/RS4xx PCI
Express Port 3
00:12.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600
Non-Raid-5 SATA
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB
(OHCI0)
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB
(OHCI1)
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB
(OHCI2)
00:13.3 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB
(OHCI3)
00:13.4 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB
(OHCI4)
00:13.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB600 USB
Controller (EHCI)
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus
Controller (rev 14)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB600 IDE
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia
(Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB600 PCI to LPC
Bridge
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI
Bridge
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8
[Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8
[Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8
[Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8
[Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
RS482/RS485 [Radeon Xpress 1100/1150]
05:00.0 Network controller: Broadcom Limited BCM4311 802.11a/b/g (rev 01)
08:00.0 Ethernet controller: Broadcom Limited BCM4401-B0 100Base-TX (rev 02)
08:01.0 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host
Adapter (rev 22)
08:01.1 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)

dmesg ACPI error messages

dmesg | grep ACPI | grep Erro
[0.231956] ACPI Error: Needed type [Reference], found [Device]
94a5754a68e8 (20160831/exresop-103)
[0.232177] ACPI Error: Method parse/execution failed [\_SB.PCI0._OSC]
(Node 94a5754b3140), AE_AML_OPERAND_TYPE (20160831/psparse-543)

Bug#872045: opencv: CVE-2017-12600 CVE-2017-12602

[Salvatore Bonaccorso]

Source: opencv
Version: 2.4.9.1+dfsg1-2
Severity: important
Tags: security upstream
Forwarded: https://github.com/opencv/opencv/issues/9311

Hi,

the following vulnerabilities were published for opencv.

CVE-2017-12600[0]:
| OpenCV (Open Source Computer Vision Library) through 3.3 has a denial
| of service (CPU consumption) issue, as demonstrated by the
| 11-opencv-dos-cpu-exhaust test case.

CVE-2017-12602[1]:
| OpenCV (Open Source Computer Vision Library) through 3.3 has a denial
| of service (memory consumption) issue, as demonstrated by the
| 10-opencv-dos-memory-exhaust test case.

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-12600
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12600
[1] https://security-tracker.debian.org/tracker/CVE-2017-12602
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12602
[2] https://github.com/opencv/opencv/issues/9311

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#862397: thunar: Thunar crashes when left open for a time showing a folder with thousands of items in it

[Roberto Garcia Carvajal]

This is very similar to this:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1679488

I have a similar problem: Open thunar on a directory. Modify one or two
files on directory, come back to thunar and is totally non-responsive. CPU
usage is 0 so probably is a deadlock. I test the patch from launchpad.net (
https://launchpadlibrarian.net/321070348/02_fix-deadlock-in-mutex-causing-thunar-to-hang.patch)
and it solves my issue. My debian release is stretch and thunar version is
1.6.11-1.

I hope it helps.

Bug#872005: libmtp: Please report this VID/PID and the device model to the libmtp development team

[leonardo]

Source: libmtp
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

Aug 13 14:56:00 hostmaster kernel: [284186.993960] usb 1-2: new high-speed USB 
device number 6 using xhci_hcd
Aug 13 14:56:00 hostmaster kernel: [284187.135153] usb 1-2: New USB device 
found, idVendor=0e8d, idProduct=4001
Aug 13 14:56:00 hostmaster kernel: [284187.135159] usb 1-2: New USB device 
strings: Mfr=2, Product=3, SerialNumber=4
Aug 13 14:56:00 hostmaster kernel: [284187.135163] usb 1-2: Product: JERRY
Aug 13 14:56:00 hostmaster kernel: [284187.135166] usb 1-2: Manufacturer: JERRY
Aug 13 14:56:00 hostmaster kernel: [284187.135169] usb 1-2: SerialNumber: 
LS1649791336
Aug 13 14:56:00 hostmaster mtp-probe: checking bus 1, device 6: 
"/sys/devices/pci:00/:00:14.0/usb1/1-2"
Aug 13 14:56:00 hostmaster mtp-probe: bus: 1, device: 6 was an MTP device
Aug 13 14:56:01 hostmaster gvfsd[1629]: Device 0 (VID=0e8d and PID=4001) is 
UNKNOWN in libmtp v1.1.13.
Aug 13 14:56:01 hostmaster gvfsd[1629]: Please report this VID/PID and the 
device model to the libmtp development team
Aug 13 14:56:01 hostmaster gvfsd[1629]: Error 1: Get Storage information failed.

phone is mounted but i do not see anything ... looks as 0 space 0 used ...


   * 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: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Bug#871833: conntrack-tools: Fix autopkgtests for compatibility with Ubuntu kernel, containers

[Arturo Borrero Gonzalez]

On 12 August 2017 at 06:15, Steve Langasek  wrote:
>
> The conntrack-tools 1.4.4+snapshot20161117 update was blocked from reaching
> Ubuntu's 17.04 release, because it regresses its autopkgtests in Ubuntu
> compared to 1.4.3-3.

Hi Steve,

thanks for your work, comments below.

>
> I have so far identified two problems with the tests when running on Ubuntu:
>
>  - the tests modprobe a bunch of nf_conntrack_* modules; if some of these
>modules don't load because they are built into the kernel (as is the case
>for some of them on Ubuntu), these tests fail.

This is good to have. I can upstream the patch.

>  - several tests are marked 'isolation-container', but provide a
>configuration to conntrackd that requires host-level privileges, so
>conntrackd fails at startup when run in a container.
>

The scheduling & bufsize things seems a bit hackish for what we need:
a simple test run of conntrackd.
I would simplify the logic by just ignoring these configuration
options and using conntrackd/system defaults.
I mean: in this test case, we are interested in checking that
conntrackd can run with a basic configuration. The actual
configuration is less important.

Please note, that scheduling defaults have changed in conntrackd [0].
If we don't specify a scheduling configuration, conntrackd will try to
use SCHED_RR by default. Which may require further privileges? I don't
have a full autopkgtest environment to test different setups (i.e.,
LXC, virtualization, etc).

So, please, I would ask you to:

1) send a (separate) patch for the modules things
2) make changes to the test suite according to the simplifications I
mentioned (separate patch)

I believe that by following this approach Ubuntu will benefit as well.

[0] 
http://git.netfilter.org/conntrack-tools/commit/?id=210f5429678dba06f361b1f37bcb946f27e2e20b

Bug#869670: Dependency missing

[Andrea Villa]

The reason for this bug is a dependency problem:

The current sid kernel is linux-image-4.11.0-2-amd64
->
corresponding headers are linux-headers-4.11.0-2-amd64:
->
they depend on linux-headers-4.11.0-2-common (= 4.11.11-1+b1)
->
there is no such version (only 4.11.11-1 *NO +b1*), maybe never made it
from experimental?

Only work around is to boot to an older kernel and install the
corresponding linux-headers-VERSION package.

Do not try to fix by installing/upgrading meta-package linux-headers-amd64
since in sid this depends on linux-headers-4.11.0-2-amd64 thus initiating
the broken dependency links described above.
Don't try to fix 4.11 kernel (it's EOL anyway), we should probably just
wait for 4.12 coming from experimental soon.

Hope this helps you folks!

Bests,

Andrea

Bug#872014: python-gtkglext1: depends on transitional package libpango1.0-0

[Vincent Lefevre]

Package: python-gtkglext1
Version: 1.1.0-9.1
Severity: minor

python-gtkglext1 depends on libpango1.0-0, which has been a
transitional package since May 2013! It should be updated.

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

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

Versions of packages python-gtkglext1 depends on:
ii  libatk1.0-0   2.24.0-1
ii  libc6 2.24-14
ii  libcairo2 1.14.10-1
ii  libfontconfig12.12.3-0.2
ii  libfreetype6  2.6.3-3.2
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libgl1-mesa-glx [libgl1]  17.1.5-1
ii  libglib2.0-0  2.53.4-3
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgtk2.0-0   2.24.31-2
pn  libgtkglext1  
ii  libice6   2:1.0.9-2
pn  libpango1.0-0 
ii  libsm62:1.2.2-1+b3
ii  libx11-6  2:1.6.4-3
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  python2.7.13-2
ii  python-gtk2   2.24.0-5.1
pn  python-opengl 
ii  python2.7 2.7.13-4

python-gtkglext1 recommends no packages.

python-gtkglext1 suggests no packages.

Bug#871992: juffed FTBFS on !amd64 64bit: missing symbol

[Alf Gaida]

Right, but you missed one point - it is missed in arm64, not amd64. And
ppc64el, s390x, alpha, ppc64 and some of the architectures that are not
built yet. And your are right, it is serious and I'm aware of it.

Switching from optional|c++ to c++|arch= !foo !bar !baz has it's up- and
downsides. The upside is: it is more readable and more precise, the
downside is: i have to collect the missed symbols after this build and
fix the symbols again. But it is not wasted work or build time as it
will ease the maintainance for future uploads.

Cheers Alf




signature.asc
Description: OpenPGP digital signature

Bug#871927: forwarded upstream

[Ghislain Vaillant]

control: forwarded -1 
https://github.com/QuantStack/xtensor-python/issues/102

Bug#845925: autopkgtest boostrap qemu

[SZALAY Attila]

Hi,

I run through this at DebConf when I tried to set up my new laptop for
debian work. The problem is, that vmdebootsrap is actually just create
a file, mount it through a loop device and after bootsrapping it it
will run the customizer script in the HOST environment. And if we think
about it, it is logical, because this allows the customizer script to
copy any file from the host os to the disk image if it want.

The mentioned customizer script (/usr/share/autopkgtest/setup-
commands/setup-testbed) also uses this feature when, for example, tries
to detect the used apt proxy.

So, all commands (especially installing packages) which the script want
to run inside the new image is run by/through the chroot command. For
example:

# install some necessary packages
# some tests use a lot of /dev/random, avoid hangs; eatmydata for fast
dpkg, a
# lot of tests expect a logind session
chroot "$root" apt-get install -y eatmydata dbus < /dev/null

And yes, the problem is, that in some cases the /etc/resolv.conf just a
symlink and point to a file which does not exists until the qemu guest
is booted up.

I'm not 100% sure, but I have the feeling that this depends on your
host environment. Because, I think, the debootstrap copies the
/etc/resolv.cong file as-is to the chroot environment.

My first idea was to use the AUTOPKGTEST_APT_PROXY environment
variable, but that did not work because the proxy only set at the end
of the customization script and all the apt-get install command already
 run.

So, my solution was, as a dirty hack, to copy the content of the
/etc/resolv.conf into the chroot. Something like this what is attached
to this email.--- /usr/share/autopkgtest/setup-commands/setup-testbed~	2017-04-30 13:09:57.0 -0400
+++ /usr/share/autopkgtest/setup-commands/setup-testbed	2017-08-06 17:22:16.942392522 -0400
@@ -196,6 +196,11 @@
 fi
 fi
 
+if [ "$root" != "/" ]; then
+chroot "$root" mv /etc/resolv.conf /etc/resolv.conf.backup
+cat /etc/resolv.conf > "$root/etc/resolv.conf"
+fi
+
 if [ -z "${AUTOPKGTEST_IS_SETUP_COMMAND:-}" ]; then
 chroot "$root" apt-get update || (sleep 15; chroot "$root" apt-get update)
 fi
@@ -288,3 +293,8 @@
 
 # avoid cron interference with apt-get update
 echo 'APT::Periodic::Enable "0";' > "$root/etc/apt/apt.conf.d/02periodic"
+
+
+if [ "$root" != "/" ]; then
+chroot "$root" mv /etc/resolv.conf.backup /etc/resolv.conf
+fi


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

Bug#872019: RFS: dcm2niix/1.0.20170724-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for the following package:

* Package name: dcm2niix
  Version : 1.0.20170724-1
  Upstream Author : Chris Rorden
* URL : https://github.com/rordenlab/dcm2niix
* License : BSD
  Section : science

One can check out the package by visiting the following URL:

   https://anonscm.debian.org/git/debian-med/dcm2niix.git

Changes since the last upload:

  * Upgrade watch file to version 4
  * New upstream version 1.0.20170724
  * Bump standards version to 4.0.1, no changes required
  * Add missing get-orig-source target
  * Build with JPEG support using TurboJPEG

Regards,
Ghis

Bug#871986: [Pkg-postgresql-public] Bug#871986: postgresql-9.6: PostgreSQL fails to start after upgrade

[Christoph Berg]

Control: tags -1 moreinfo

Re: Jacob Sparre Andersen 2017-08-13 
<150261237312.2459.10119247764903837989.report...@franka.jacob-sparre.dk>
> Last night I upgraded "postgresql-9.6" to the most recent version
> (went from 9.6.3-3 to 9.6.4-0+deb9u1).
> 
> As a part of the upgrade PostgreSQL was shut down, and it has not come
> up since then.

Hi Jacob,

can we see the output of "systemctl status postgresql@9.6-main"?

Is /etc/postgresql/9.6/main/start.conf set to "auto"?
Do you have /usr/sbin/policy-rc.d installed?

> I've tried "sudo service postgresql restart" without any visible effect.

postgresql.service is just a stub which forwards all actions to the
individual services like postgresql@9.6-main.service. Unfortunately
systemctl doesn't really relay any errors back if there's any.

Christoph

Bug#872025: glibc: French debconf translation update

[Alban Vidal]

Package: glibc
Version: 2.24-14
Severity: wishlist
Tags: patch l10n

Please find attached the French debconf templates update, proofread by the
debian-l10n-french mailing list contributors.

Best regards

Alban Vidal
# Translation of glibc debconf templates to French
# Copyright (C) 2001-2009, 2011, 2015, 2017 Debian French l10n team 

# This file is distributed under the same license as the glibc package.
#
# Translators:
# Denis Barbier 2001-2006.
# Christian Perrier , 2007, 2008, 2009, 2011, 2015.
# Alban Vidal , 2017.
msgid ""
msgstr ""
"Project-Id-Version: glibc 2.24-14\n"
"Report-Msgid-Bugs-To: gl...@packages.debian.org\n"
"POT-Creation-Date: 2017-06-13 22:11+0200\n"
"PO-Revision-Date: 2017-08-04 14:44+0100\n"
"Last-Translator: Alban Vidal \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 2.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

#. Type: multiselect
#. Choices
#: ../debhelper.in/locales.templates:1001
msgid "All locales"
msgstr "Tous les choix possibles"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid "Locales to be generated:"
msgstr "Jeux de paramètres régionaux à créer :"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid ""
"Locales are a framework to switch between multiple languages and allow users "
"to use their language, country, characters, collation order, etc."
msgstr ""
"Les jeux de paramètres régionaux (aussi appelés « locales ») permettent de "
"gérer des langues multiples et offrent aux utilisateurs la possibilité de "
"choisir la langue, le pays, le jeu de caractères, l'ordre de tri, etc."

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid ""
"Please choose which locales to generate. UTF-8 locales should be chosen by "
"default, particularly for new installations. Other character sets may be "
"useful for backwards compatibility with older systems and software."
msgstr ""
"Veuillez choisir les paramètres régionaux à créer. Des paramètres régionaux "
"utilisant l'encodage UTF-8 devraient être le choix par défaut, notamment "
"pour de nouvelles installations. Les autres jeux de caractères peuvent être "
"utiles pour conserver la compatibilité avec d'anciens systèmes ou logiciels."

#. Type: select
#. Choices
#: ../debhelper.in/locales.templates:2001
msgid "None"
msgstr "Aucun"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid "Default locale for the system environment:"
msgstr "Jeu de paramètres régionaux actif par défaut :"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid ""
"Many packages in Debian use locales to display text in the correct language "
"for the user. You can choose a default locale for the system from the "
"generated locales."
msgstr ""
"De nombreux paquets utilisent le mécanisme de localisation pour afficher les "
"messages destinés aux utilisateurs dans la langue adéquate. Vous pouvez "
"changer la valeur par défaut de l'ensemble du système pour utiliser un des "
"jeux de paramètres régionaux qui seront créés."

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid ""
"This will select the default language for the entire system. If this system "
"is a multi-user system where not all users are able to speak the default "
"language, they will experience difficulties."
msgstr ""
"Veuillez noter que cette valeur modifiera la langue utilisée par le système. "
"Si l'environnement est multi-utilisateurs et que certains utilisateurs ne "
"parlent pas votre langue, ils risquent d'avoir des difficultés."

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid "Do you want to upgrade glibc now?"
msgstr "Faut-il mettre à niveau le paquet glibc maintenant ?"

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid ""
"Running services and programs that are using NSS need to be restarted, "
"otherwise they might not be able to do lookup or authentication any more. "
"The installation process is able to restart some services (such as ssh or "
"telnetd), but other programs cannot be restarted automatically. One such "
"program that needs manual stopping and restart after the glibc upgrade by "
"yourself is xdm - because automatic restart might disconnect your active X11 "
"sessions."
msgstr ""
"Les services et programmes qui utilisent NSS (« Name Service Switch ») "
"doivent être redémarrés car leur système d'authentification risque de ne "
"plus fonctionner. Il est possible de redémarrer certains services (comme SSH "
"ou telnetd) pendant l'installation, mais d'autres ne peuvent l'être "
"automatiquement. Il est notamment indispensable d'arrêter et redémarrer "
"manuellement 

Bug#871986: [Pkg-postgresql-public] Bug#871986: postgresql-9.6: PostgreSQL fails to start after upgrade

[Jacob Sparre Andersen]

Christoph Berg wrote:


Is /etc/postgresql/9.6/main/start.conf set to "auto"?


No. :-(

It appears that I simply hadn't switched from "manual" to "auto" after I 
finished the upgrade from 9.4 (Jessie) to 9.6.


I'm sorry about filling trivial problems like that in the bug database.


> I've tried "sudo service postgresql restart" without any visible effect.

postgresql.service is just a stub which forwards all actions to the
individual services like postgresql@9.6-main.service. Unfortunately
systemctl doesn't really relay any errors back if there's any.


Could "postgresql.service" be expanded such that running "service 
postgresql" will output a suggestion to use "systemctl" instead?


Thanks for the help!

/Jacob

Bug#872030: rear: Please recommend the 'extlinux' package

[Reinhard Tartler]

Package: rear
Version: 2.00+dfsg-2
Severity: normal

Dear Maintainer,

Rear can be used to create a bootable USB drive. For this to work, the
package 'extlinux' needs to be installed on the system. If you do not
have the package installed, rear will produce this error message:

  | root@sandy:~# rear mkbackuponly
  | Aborting due to an error, check /var/log/rear/rear-sandy.5348.log for 
details
  | Terminated


Please add a Recommends or Suggests 'extlinux' to the rear package.

Reinhard

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

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

Versions of packages rear depends on:
ii  attr  1:2.4.47-2+b2
ii  binutils  2.28-5
ii  dosfstools4.1-1
ii  ethtool   1:4.8-1+b1
ii  gawk  1:4.1.4+dfsg-1
ii  iproute   1:4.9.0-1
ii  iputils-ping  3:20161105-1
ii  isolinux  3:6.03+dfsg-14.1
ii  lsb-release   9.20161125
ii  openssl   1.1.0f-3
ii  parted3.2-17
ii  syslinux  3:6.03+dfsg-14.1
ii  xorriso   1.4.6-1+b1

Versions of packages rear recommends:
ii  nfs-common [nfs-client]  1:1.3.4-2.1
ii  rpcbind [portmap]0.2.3-0.6

rear suggests no packages.

-- Configuration Files:
/etc/rear/local.conf changed [not included]

-- no debconf information

Bug#872031: rear: New upstream version: 2.2

[Reinhard Tartler]

Package: rear
Version: 2.00+dfsg-2
Severity: normal

Dear Maintainer,

There is a new upstream version of the rear package available:

http://relax-and-recover.org/documentation/release-notes-2-2

In that list, I spotted this entry in the Changelog:

 > Add missing privilege separation dir to start sshd on Debian 9 (issue #1381)

This may important even for debian stretch (currently stable).

Thank you for preparing this package. I think it would be a great
addition to the backports archive!

Let me know if I can assist you in any way.

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

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

Versions of packages rear depends on:
ii  attr  1:2.4.47-2+b2
ii  binutils  2.28-5
ii  dosfstools4.1-1
ii  ethtool   1:4.8-1+b1
ii  gawk  1:4.1.4+dfsg-1
ii  iproute   1:4.9.0-1
ii  iputils-ping  3:20161105-1
ii  isolinux  3:6.03+dfsg-14.1
ii  lsb-release   9.20161125
ii  openssl   1.1.0f-3
ii  parted3.2-17
ii  syslinux  3:6.03+dfsg-14.1
ii  xorriso   1.4.6-1+b1

Versions of packages rear recommends:
ii  nfs-common [nfs-client]  1:1.3.4-2.1
ii  rpcbind [portmap]0.2.3-0.6

rear suggests no packages.

-- Configuration Files:
/etc/rear/local.conf changed [not included]

-- no debconf information

Bug#872033: apt edit-sources: missing newline at the end of "file changed, please run 'apt-get update'."

[s3v]

Package: apt
Version: 1.5~beta1
Severity: minor
Tags: patch
Control: found -1 1.4.7


Dear maintainer,

after some changes in sources.list file, "apt edit-sources" sends to output
the message below:

  "Your '/etc/apt/sources.list' file changed, please run 'apt-get update'"

but a missing newline induces the shell prompt to appear on the same line.

 root:~#  apt edit-sources
 Your '/etc/apt/sources.list' file changed, please run 'apt-get update'.root:~#

Please find attached a trivial patch to fix this issue.

Thanks for reading.
--- private-sources.cc	2017-08-13 18:16:53.105652765 +0200
+++ private-sources.cc-new	2017-08-13 18:16:57.965554388 +0200
@@ -100 +100 @@
- std::cout, _("Your '%s' file changed, please run 'apt-get update'."),
+ std::cout, _("Your '%s' file changed, please run 'apt-get update'.\n"),

Bug#791494: Finally fixed

[Joseph Herlant]

Control: tags -1 + pending

Fixed along with the new version of the package uploaded to mentors.

Bug#777004: dnsmasq breaks dns lookup with resolvconf

[Alexey Dobrovolskiy]

Hi all,
perhaps it could be solved by setting

DNSMASQ_EXCEPT=lo

in /etc/default/dnsmasq
According to dnsmasq's init script, it prevents providing local DNS, so
don't add 127.0.0.1  to the resolvconf server set.

I also ask maintainer or developers to explicitly include this variable in
/etc/default/dnsmasq as a comment.

-- 
Best regards,
Alexey

Bug#872017: [Pkg-zsh-devel] Bug#872017: zsh-syntax-highlighting FTBFS with zsh 5.4.1-1

[Daniel Shahaf]

Control: tag -1 + fixed-upstream
Control: fixed -1 0.6.0~rc1-2

Adrian Bunk wrote on Sun, 13 Aug 2017 16:39 +0300:
> # alias
> /build/1st/zsh-syntax-highlighting-0.5.0/./highlighters/main/test-data/alias.zsh:32:
>  defining function based on alias `alias1'
> /build/1st/zsh-syntax-highlighting-0.5.0/./highlighters/main/test-data/alias.zsh:32:
>  parse error near `()'
> Bail out! Either 'PREBUFFER' or 'BUFFER' must be declared and non-blank
> Bail out! output on stderr

Fixed upstream in 9523d6d49cb3d4db5bd84c3cec6168a2057fe3ab, already in
experimental and due to be uploaded to sid soon.

To be clear, there is no bug in z-sy-h itself; this is entirely a test suite 
issue.

Thanks,

Daniel

Bug#872040: duktape: please ship a duktape library

[Paul Gevers]

Source: duktape
Version: 2.0.0-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As discussed on the mailinglist¹², there is a use-case for using a duktape
library in Debian: the upstream of the edbrowse package shifted to it. So
please provide a duktape library that edbrowse could use.

Paul

PS: I'll try to figure out if edbrowse works with the default config, but
haven't done that yet.

¹ 
https://lists.alioth.debian.org/pipermail/debian-iot-maintainers/Week-of-Mon-20170807/000197.html
² 
https://lists.debian.org/msgid-search/fb3e250e-67d6-ec8f-aa71-5935296d6...@debian.org

- -- System Information:
Debian Release: 9.1
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable'), (200, 'stable'), (50, 
'stable')
Architecture: amd64 (x86_64)

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlmQlUUACgkQnFyZ6wW9
dQqrXAgAiF2pIWr7w98zGZQw8OkZxfcpl7ak5yi+hdFnUdcXUetBbAOGCWGDLs+8
PZ9c63sAZe5HggicX92mGvYMDvZW/9LN0pmItf1VuFOhtzDcHvi/LpCOWtr2Mhs4
YgdPrAqoYz0nSN69WD59R+7F3FZ8hS71MIS4usUheUQPBOODF9DeBxfc509DQFxN
vLfk5zZZ+B7N4tna6NPYNrAuMIaXcYKw0cJTCrRRDMPa9zzgtJF4Q5CRL26lddXI
cOI6VxszwQttu6h2U/d22YSQ1ONe5AUl2kXWgK/m1SFru2XB2zzYf4xfwhtqRieB
oH7NtYZYHDg1ynrUnRy34/ktae2iuA==
=pVuE
-END PGP SIGNATURE-

Bug#871957: [lintian] orig-tarball-missing-upstream-signature should exclude repacks

[Chris Lamb]

tags 871957 + pending
thanks

Added the "repack" bit here:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=6094948b0e09b997df75dbc748cef25d4ada44c0


Regards,

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

Bug#854962:

[H.-Dirk Schmitt]

This bug renders mpd-sima completly unusable if mpd 0.20 is installed.
This is the case in buster/sid and ubuntu artful.

Bug#872042: lintian: please check for missing calls to dpkg-maintscript-helper

[Chris Lamb]

tags 872042 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=e7427666c926db64302f2b6e5bf7eac70ce795a7


Regards,

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

Bug#871187: [Pkg-ime-devel] Bug#871187: libkkc: FTBFS with vala 0.36

[Mitsuya Shibata]

Owner: mty.shib...@gmail.com
Source: libkkc

Hi Jeremy,

Thank you for your reporting and patch.

I pushed fixed code to package's vcs, and uploaded to mentors.debian.net.
If package's information will be appeared, then I will send request sponsorship.

Regards,
-- 
Mitsuya Shibata

Bug#844431: Revised patch: seeking seconds

[Sean Whitton]

On Sat, Aug 12 2017, Ximin Luo wrote:

> Thanks! Seconded.

Just to be clear, we are waiting on one more second for the version
that refers to build and target architecture.

-- 
Sean Whitton

Bug#872001: libreoffice-common: please stop shipping mimelnk desktop files

[Pino Toscano]

Package: libreoffice-common
Severity: wishlist

Hi,

libreoffice-common ships desktop files under /usr/share/mimelnk: they
are mimetypes for kdelibs v3.x (and older), which had its own mimetype
system.

Since:
- kdelibs v4.x uses XDG mimetypes
- kdelibs 3.x was shipped last in Debian in Squeeze (and thus no more
  other kdelibs v3-based application)
- that mimetype system was exclusively used by kdelibs 3.x
I suggest to simply drop those files at least from libreoffice-common
in Debian.  Most probably, they could be removed upstream too.

Thanks,
-- 
Pino

Bug#872003: RM: eventlog -- ROM; eventlog library merged to syslog-ng and abandoned by upstream

[SZALAY Attila]

Package: ftp.debian.org
Severity: normal


The eventlog library is/was a reverse dependency of syslog-ng.  Lately it
was a bit neglected by upstream, there were no updates for ages.  Also there
were at least three different "official" version in the wild.  So I
convinced upstream that the best way to come out of this situation is to
merge the eventlog library into syslog-ng.  This happened with syslog-ng
version 3.11.1, so the libevtlog not needed by syslog-ng any more.  Also
there is/were no other reverse dependency of the project than syslog-ng.  So
it not needed in the archive any more.

Bug#844431: Revised patch: seeking seconds

[gregor herrmann]

On Sat, 12 Aug 2017 15:34:35 -0700, Sean Whitton wrote:

> diff --git a/policy/ch-source.rst b/policy/ch-source.rst
> index 127b125..6e32870 100644
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -661,6 +661,28 @@ particularly complex or unintuitive source layout or 
> build system (for
>  example, a package that builds the same source multiple times to
>  generate different binary packages).
>  
> +Reproducibility
> +---
> +
> +Packages should build reproducibly, which for the purposes of this
> +document [#]_ means that given
> +
> +- a version of a source package unpacked at a given path;
> +- a set of versions of installed build dependencies;
> +- a set of environment variable values;
> +- a build architecture; and
> +- a host architecture,
> +
> +repeatedly building the source package for the build architecture on
> +any machine of the host architecture with those versions of the build
> +dependencies installed and exactly those environment variable values
> +set will produce bit-for-bit identical binary packages.
> +
> +It is recommended that packages produce bit-for-bit identical binaries
> +even if most environment variables and build paths are varied.  It is
> +intended for this stricter standard to replace the above when it is
> +easier for packages to meet it.
> +
>  .. [#]
> See the file ``upgrading-checklist`` for information about policy
> which has changed between different versions of this document.
> @@ -790,3 +812,7 @@ generate different binary packages).
> often creates either static linking or shared library conflicts, and,
> most importantly, increases the difficulty of handling security
> vulnerabilities in the duplicated code.
> +
> +.. [#]
> +   This is Debian's precisification of the `reproducible-builds.org
> +   definition `_.


Seconded.

Thanks to everyone for their work on this.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#869836: stretch-pu: package nvidia-graphics-drivers/375.82-1~deb9u1

[Julien Aubin]

On Sat, 12 Aug 2017 12:41:20 -0400 "Adam D. Barratt" <
a...@adam-barratt.org.uk> wrote:
> Control: tags -1 + pending
>
> On Wed, 2017-08-09 at 17:17 +0200, Andreas Beckmann wrote:
> > On Tue, 08 Aug 2017 16:12:47 -0400 "Adam D. Barratt"
> >  wrote:
> > > Please go ahead, and we'll hope it looks sane after that. :-p
> >
> > Uploaded, with the attached diff (from svn, excluding the blobs).
>
> Flagged for acceptance.
>
> Regards,
>
> Adam
>
>
>

Hi Adam,

Just to confirm the fix does work fine for me, no regression seen.

Hardware used :
Intel Core i7 4790
32 GB RAM
NVidia GeForce GTX 1070
Debian Stretch AMD64 w/ 4.9 kernel (i.e. not bpo)

Environment : KDE

Games tested :
Civilization VI (benchmark only)
Shadow of Mordor (benchmark only)
Sudden Strike 4
Wargame Red Dragon


Also tested on a GeForce GTX 970 (just boot test) w/o issue.

Bug#872024: ITP: golang-go.uber-multierr -- multierr allows combining one or more Go errors together

[Pirate Praveen]

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 
X-Debbugs-CC: debian-de...@lists.debian.org,
pkg-go-maintain...@lists.alioth.debian.org

* Package name: golang-go.uber-multierr
  Version : 1.1.0-1
  Upstream Author : Uber Technologies, Inc.
* URL : https://go.uber.org/multierr
* License : Expat
  Programming Lang: Go
  Description : multierr allows combining one or more Go errors together

Build dependency for gitaly (component of gitlab, a git based
collaboration platform)




signature.asc
Description: OpenPGP digital signature

Bug#872022: RFS: evolution/3.22.6-1+nmu1

[Andrey Rahmatullin]

Control: tags -1 + moreinfo
Control: severity -1 normal

The RFS bug severity is wrong.

Please read
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu

The version suffix is wrong (you can use dch --nmu to make a correct one
but you should read the devref article on the NMU versions anyway).
You haven't sent the nmudiff to the bug, only the updated files (which is
wrong).
It's not usual to upload a NMU for an important severity bug 3 days after
it was filed.
The changelog contains lots of unrelated whitespace changes (you would see
them if you made a nmudiff).

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#872035: sysdig FTBFS with curl 7.55.0-1

[Adrian Bunk]

Source: sysdig
Version: 0.17.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sysdig.html

...
/build/1st/sysdig-0.17.0/userspace/libsinsp/marathon_http.cpp:10:10: fatal 
error: curl/curlbuild.h: No such file or directory
 #include "curl/curlbuild.h"
  ^~
compilation terminated.
userspace/libsinsp/CMakeFiles/sinsp.dir/build.make:1049: recipe for target 
'userspace/libsinsp/CMakeFiles/sinsp.dir/marathon_http.cpp.o' failed
make[3]: *** [userspace/libsinsp/CMakeFiles/sinsp.dir/marathon_http.cpp.o] 
Error 1

Bug#871810: cvs: CVE-2017-12836: CVS and ssh command injection

[Chris Lamb]

Hi Thorsten,

> […]

Thanks for uploading. I'll send the DLA announcement out now…


Regards,

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

Bug#868068: [xserver-xorg-core] Loss of keyboard and mouse at Debian 9.1 ("Stretch" under AMD64), too.

[Kim Olsen]

Hi,

when running Debian-9.1 on an AMD64-machine with

xserver-xorg-core (2:1.19.2-1+deb9u1) and
xserver-common (2:1.19.2-1+deb9u1)

keyboard and mouse are freezing up sometimes, too.

Shutting down the PC or unplug/plug the USB-units
can't be a solution for a longer period!

Greetings

Kim Olsen

Bug#868068: ([xserver-xorg-core] Upgrade from 2:1.16.4-1 to 2:1.16.4-1+deb8u1 loses keyboard and mouse)

[Fungi4All]

Intel 82Q35 Express Integrated Graphics Controller
Intel(R) Core(TM)2 Duo CPU E6550
lshw does not return anything about Haswell
lspci returns
00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 82Q35 Express PCI Express Root Port (rev 
02)
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated 
Graphics Controller (rev 02)
00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated Graphics 
Controller (rev 02)
00:03.0 Communication controller: Intel Corporation 82Q35 Express MEI 
Controller (rev 02)
00:03.2 IDE interface: Intel Corporation 82Q35 Express PT IDER Controller (rev 
02)
00:03.3 Serial controller: Intel Corporation 82Q35 Express Serial KT Controller 
(rev 02)
00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network 
Connection (rev 02)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 02)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IO (ICH9DO) LPC Interface Controller 
(rev 02)
00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port 
SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)

lsusb
Bus 002 Device 004: ID 148f:2770 Ralink Technology, Corp. RT2770 Wireless 
Adapter
Bus 006 Device 003: ID 0461:4dbf Primax Electronics, Ltd
Bus 006 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse

Bug#837871: no need for addgroup: The group `input' already exists as a system group. Exiting. messages

[Michael Biebl]

Hi Afif!

Am 13.08.2017 um 05:12 schrieb Afif Elghraoui:
> Control: reassign -1 udev
> 
> Hi, Michael,
> 
> على الخميس 15 أيلول 2016 ‫04:20، كتب Michael Biebl:
>>
>> Feel free to ping us once --quiet has been fixed and we'll re-add those
>> to our maintainer scripts.
>>
> 
> I just uploaded adduser with a resolution for #763055. I'm very sorry
> for the delay and hope to be much faster in the future.

Don't worry. It's great to see work being done for adduser.
This is very much appreciated. Thanks a lot!

> I think it was a mistake for me to reassign this particular ticket,
> since this is about you not using --quiet, but you aren't using --quiet
> because it was broken in adduser (the "blocks" relationship you had
> added). I think reassigning back, as I did here, will allow its closure
> to properly notify the submitters that the problem they encountered is
> resolved.
> 
> Let me know if there are further issues.
> 

I quickly tested it, i.e. I readded the --quiet flag to the addgroup
call in udev's postinst.
It did properly hide any messages on success and it did show an error
message if I triggered an error (by pre-creating an input group which
was not a system group but had a gid >= 1000).

So I plan to re-add the --quiet flag to systemd/udev for the next
upload. Should issues pop out, I'll keep you informed.

Thanks again,
Michael


-- 
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#856685: closed by Osamu Aoki <os...@debian.org> (non-GNOME desktop not supported well by ibus)

[積丹尼 Dan Jacobson]

Yes even today I had to hold a glass magnifying glass up to the computer
screen to choose the last character of "生育酮".

Bug#871908: dgit fails to work when .git is a reference not a directory

[Sean Whitton]

Hello,

On Sun, Aug 13 2017, Ian Jackson wrote:

> Sean, if you felt like it you could take my chiark master
> (92667fc40d49284a19475b031f79eba6fc883548) finalise the changelog and
> upload it to experimental as 4.1.

I can't obtain your master over an authenticated channel, but I too lack
my key -- I'll review the diff from dgit/dgit/experimental on the plane
and then if I get home before you I will upload :)

-- 
Sean Whitton

Bug#861741: src:sympy: Relax the Recommends dependency chain

[magnu...@gmail.com]

I'm in the process of packaging up a python library which depends on sympy,
and having the same issue. Due to texlive-fonts-extra being recommended in
sympy, the install size is increased by about 2 GB.

So I agree with Ghis' suggestion of changing (at least) dvipng and
texlive-fonts-extra from recommends to suggests.

Magnus

Bug#871909: dgit gbp-build fails if user specifies --git-builder

[Sean Whitton]

Hello,

On Sat, Aug 12 2017, Sam Hartman wrote:

> Recommendation: if the user passes --git-builder as a gbp-build
> option, perhaps dgit shouldn't pass builder-specific options.

That sounds reasonable -- dgit should probably strip the signature after
the build, in order to leave consistent output, probably printing a
warning.

> Alternatively, you can say that I shouldn't pass git-builder, but if
> you're going to say that, I'd appreciate some mechanism to accomplish
> my pristine-tar goal.  I guess I can also run gbp buildpackage without
> dgit, and that'll mostly work for me, but it seems not entirely
> desirable.

I would use origtargz(1) to check out the pristine tarball.  Though I
guess you have to rm the orig that dgit downloads.

-- 
Sean Whitton

Bug#871959: debhelper: dh_installdeb does not run executable package.triggers to generate triggers

[Andreas Beckmann]

On 2017-08-13 10:48, Niels Thykier wrote:

> Would you also expect that "postinst" (etc.) behaved the same?  AFAICT,
> there is no reason why it should not apply to them as well if triggers
> started doing this.

I don't have a usecase for generating the postscript, yet :-)
But anything that needs a "list of things" seems to be a candidate for
being generated.


Andreas

Bug#872011: photutils FTBFS with pytest 3.2.0

[Adrian Bunk]

Source: photutils
Version: 0.3.2-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/photutils.html

...
= test session starts ==
platform linux2 -- Python 2.7.13+, pytest-3.2.0, py-1.4.34, pluggy-0.4.0 -- 
/usr/bin/python2.7
cachedir: ..

Running tests with photutils version 0.3.2.
Running tests in lib.linux-x86_64-2.7/photutils.

Date: 2017-08-12T20:33:33

Platform: Linux-4.9.0-3-amd64-x86_64-with-debian-buster-sid

Executable: /usr/bin/python2.7

Full Python Version: 
2.7.13+ (default, Jul 19 2017, 18:15:03) 
[GCC 6.4.0 20170704]

encodings: sys: ascii, locale: ANSI_X3.4-1968, filesystem: ANSI_X3.4-1968, 
unicode bits: 20
byteorder: little
float info: dig: 15, mant_dig: 15

Numpy: 1.12.1
Scipy: not available
Matplotlib: not available
Pandas: not available
Astropy: 2.0.1
scikit-image: not available
Using Astropy options: remote_data: none.

rootdir: /tmp/photutils-test-o_Rm6f, inifile: setup.cfg
collecting ... collected 1058 items / 1 errors

 ERRORS 
_ ERROR collecting lib.linux-x86_64-2.7/photutils/psf/tests/test_photometry.py _
/usr/lib/python2.7/dist-packages/_pytest/runner.py:191: in __init__
self.result = func()
/usr/lib/python2.7/dist-packages/_pytest/runner.py:370: in 
lambda: list(collector.collect()),
/usr/lib/python2.7/dist-packages/_pytest/python.py:389: in collect
return super(Module, self).collect()
/usr/lib/python2.7/dist-packages/_pytest/python.py:330: in collect
res = self.makeitem(name, obj)
/usr/lib/python2.7/dist-packages/_pytest/python.py:342: in makeitem
collector=self, name=name, obj=obj)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:745: in 
__call__
return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:339: in 
_hookexec
return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:334: in 

_MultiCall(methods, kwargs, hook.spec_opts).execute()
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:613: in 
execute
return _wrapped_call(hook_impl.function(*args), self.execute)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:250: in 
_wrapped_call
wrap_controller.send(call_outcome)
/usr/lib/python2.7/dist-packages/_pytest/python.py:188: in 
pytest_pycollect_makeitem
res = list(collector._genfunctions(name, obj))
/usr/lib/python2.7/dist-packages/_pytest/python.py:362: in _genfunctions
self.ihook.pytest_generate_tests(metafunc=metafunc)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:745: in 
__call__
return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:339: in 
_hookexec
return self._inner_hookexec(hook, methods, kwargs)
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:334: in 

_MultiCall(methods, kwargs, hook.spec_opts).execute()
/usr/lib/python2.7/dist-packages/_pytest/vendored_packages/pluggy.py:614: in 
execute
res = hook_impl.function(*args)
/usr/lib/python2.7/dist-packages/_pytest/python.py:113: in pytest_generate_tests
metafunc.parametrize(*marker.args, **marker.kwargs)
/usr/lib/python2.7/dist-packages/_pytest/python.py:781: in parametrize
for x in argvalues]
/usr/lib/python2.7/dist-packages/_pytest/mark.py:66: in extract_from
warnings.warn(MARK_PARAMETERSET_UNPACKING)
E   RemovedInPytest4Warning: Applying marks directly to parameters is 
deprecated, please use pytest.param(..., marks=...) instead.
E   For more details, see: https://docs.pytest.org/en/latest/parametrize.html
=== warnings summary ===
None
  [pytest] section in setup.cfg files is deprecated, use [tool:pytest] instead.

-- Docs: http://doc.pytest.org/en/latest/warnings.html
!!! Interrupted: 1 errors during collection 
= 1 warnings, 1 error in 7.49 seconds ==
debian/rules:18: recipe for target 'test-python2.7' failed
make[1]: *** [test-python2.7] Error 2
make[1]: Leaving directory '/build/1st/photutils-0.3.2'
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2

Bug#871187: [Pkg-ime-devel] Bug#871187: Bug#871187: libkkc: FTBFS with vala 0.36

[Osamu Aoki]

Thanks

Once I get back from debconf I will take care

On Aug 13, 2017 07:15, "Mitsuya Shibata"  wrote:

> Owner: mty.shib...@gmail.com
> Source: libkkc
>
> Hi Jeremy,
>
> Thank you for your reporting and patch.
>
> I pushed fixed code to package's vcs, and uploaded to mentors.debian.net.
> If package's information will be appeared, then I will send request
> sponsorship.
>
> Regards,
> --
> Mitsuya Shibata
>
> ___
> Pkg-ime-devel mailing list
> pkg-ime-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ime-devel
>

Bug#872015: convert import path to url for homepage and source

[Pirate Praveen]

package: dh-golang
version: 1.22
severity: wishlist

example package go.uber.org/atomic. Same for Source in copyright.



signature.asc
Description: OpenPGP digital signature