Processed: tagging 903855

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 903855 + upstream
Bug #903855 [ruby-rails-admin] CVE-2016-10522
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 903855 in 0.8.1+dfsg-3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 903855 0.8.1+dfsg-3
Bug #903855 [ruby-rails-admin] CVE-2016-10522
Marked as found in versions ruby-rails-admin/0.8.1+dfsg-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#885918: marked as done (Fail to start with UTF-8 anthy dict)

[Debian Bug Tracking System]

Your message dated Mon, 16 Jul 2018 04:19:44 +
with message-id 
and subject line Bug#885918: fixed in kasumi 2.5-9
has caused the Debian Bug report #885918,
regarding Fail to start with UTF-8 anthy dict
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kasumi
Version: 2.5-5+b2
Severity: important

With the new ibus 1.5.17 which uses UTF-8 disctinary, kasumi doesn't
start:

$ /usr/bin/kasumi
kasumi: KasumiDic.cxx:78: void KasumiDic::load(KasumiConfiguration*): Assertion 
`anthy_version != 0' failed.
Aborted
$ /usr/bin/kasumi -a
kasumi: KasumiDic.cxx:78: void KasumiDic::load(KasumiConfiguration*): Assertion 
`anthy_version != 0' failed.
Aborted

As I read the code around:

void KasumiDic::load(KasumiConfiguration *conf)
throw(KasumiException){

  const int FREQ_LBOUND = conf->getPropertyValueByInt("MinFrequency");
  const int FREQ_UBOUND = conf->getPropertyValueByInt("MaxFrequency");

  int anthy_version = atoi(anthy_get_version_string());
  assert(anthy_version != 0);

...

OLD ANTHY  9100h
NEW ANTHY  0.3

Is this problem???

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

Kernel: Linux 4.14.0-2-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 kasumi depends on:
ii  libanthy11:0.3-6
ii  libatk1.0-0  2.26.1-2
ii  libc62.25-5
ii  libcairo21.15.8-3
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.8.1-0.1
ii  libgcc1  1:7.2.0-18
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.54.2-4
ii  libgtk2.0-0  2.24.31-5
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libpangoft2-1.0-01.40.14-1
ii  libstdc++6   7.2.0-18

Versions of packages kasumi recommends:
ii  anthy  1:0.3-6

kasumi suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kasumi
Source-Version: 2.5-9

We believe that the bug you reported is fixed in the latest version of
kasumi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 885...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Osamu Aoki  (supplier of updated kasumi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Jul 2018 11:51:12 +0900
Source: kasumi
Binary: kasumi
Architecture: source amd64
Version: 2.5-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Osamu Aoki 
Description:
 kasumi - Simple dictionary utility for Anthy
Closes: 885918 900216
Changes:
 kasumi (2.5-9) unstable; urgency=medium
 .
   * Team upload.
   * New maintainer: Debian Input Method Team.  Closes: #900216
   * Fix breakage due to anthy version string.  Closes: #885918
   * Update manpage with Fedora patch.
   * Update upstream URL with https://osdn.net/projects/kasumi
Checksums-Sha1:
 19bc094348911a0a95a994d81aaffe5c2982f4f7 1845 kasumi_2.5-9.dsc
 ae95fba23677ee1396010cf3c9566254153f9d01 6536 kasumi_2.5-9.debian.tar.xz
 0e516865306d4984932c213d39a7fce838a2be9e 595128 kasumi-dbgsym_2.5-9_amd64.deb
 204358cfdb5ce2778f87ee66b8ac285bcbc72057 10355 kasumi_2.5-9_amd64.buildinfo
 77465287561483872be7619c4e50876c75b533f2 63132 kasumi_2.5-9_amd64.deb
Checksums-Sha256:
 788b6a54ed282b64b065da9c6efae39757ff4e46756d75d099a74a82d8e832d6 1845 
kasumi_2.5-9.dsc
 a68ca25edcc83639a747a5808090c7873c19ef54468e7aa0feafa619cb371116 6536 
kasumi_2.5-9.debian.tar.xz
 d5cab817cf829875adbcdd4c50e028fe99d682234a0833ff8654d602bf8d1bd4 595128 
kasumi-dbgsym_2.5-9_amd64.deb
 d3a5d7eed8f22dcde553f1f2ad252f4976e6b12e46f7f481f581cfa535ffce85 10355 
kasumi_2.5-9_amd64.buildinfo
 47ea34b7b2a876778f05e253d8db91699ec0eaebe8c85e40924e96fae657ff52 63132 
kasumi_2.5-9_amd64.deb
Files:
 7fa4a5c48b79f986db972ba63e455afd 1845 x11 

Processed: tagging 903767

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 903767 + pending
Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 
4.8
Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / 
kernel panic at boot
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903767
903800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903800
903821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903862: FTBFS: override_dh_auto_test exits with exit 2

[Dmitry Smirnov]

On Monday, 16 July 2018 9:03:59 AM AEST Vincent Lefevre wrote:
> Start  22: test-real-data
>  22/118 Test  #22: test-real-data ...***Failed 
>   0.01 sec

There is not enough information in this bug report to have a slightest clue 
about the problem. Could you please at least quote a relevant part of log?

Test failure is followed by cat of "LastTest.log" that should have some 
information about the failure.

I can not reproduce the problem in clean build environment.

-- 
Best wishes,
 Dmitry Smirnov.

---

Democracy is a pathetic belief in the collective wisdom of individual
ignorance.
-- H. L. Mencken


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

Processed: tagging 903862

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 903862 + unreproducible moreinfo
Bug #903862 [src:gnucash] FTBFS: override_dh_auto_test exits with exit 2
Added tag(s) moreinfo and unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 903862 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 903862 normal
Bug #903862 [src:gnucash] FTBFS: override_dh_auto_test exits with exit 2
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#900897: marked as done (missing dependency on pciutils)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 23:33:59 +
with message-id 
and subject line Bug#900897: fixed in ladvd 1.1.2-1
has caused the Debian Bug report #900897,
regarding missing dependency on pciutils
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
900897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ladvd
Version: 1.1.1~pre1-2+b2
Severity: grave

Hi Marco,

ladvd, on startup, reads /usr/share/misc/pci.ids. If it can't read it, then it
segfaults. You probably have missed it because you've only used ladvd on
machines installed by d-i with recommends activated, which isn't my case (I
used a home-brewed installer that is simply using debootstrap).

In my book, this:

"makes the package in question unusable by most or all users"

which grants a severity: grave.

Please note that the issue is on both Sid and Stable, and it would be nice if
you could fix the package in Stretch as well.

Also, the /var/run/ladvd seemed missing on startup of ladvd. This also needs
investigation (though that's not the core of this bug report).

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Source: ladvd
Source-Version: 1.1.2-1

We believe that the bug you reported is fixed in the latest version of
ladvd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 900...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marco d'Itri  (supplier of updated ladvd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Jul 2018 00:26:03 +0200
Source: ladvd
Binary: ladvd
Architecture: source amd64
Version: 1.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Marco d'Itri 
Changed-By: Marco d'Itri 
Description:
 ladvd  - LLDP/CDP sender
Closes: 890051 900897
Changes:
 ladvd (1.1.2-1) unstable; urgency=medium
 .
   * New upstream release. Fixes:
 - a segfault on startup on some systems. (Closes: #890051)
   * Depend on pciutils. (Closes: #900897)
Checksums-Sha1:
 aa361dcdebcdd53cb09683047bcd766574c57846 1739 ladvd_1.1.2-1.dsc
 399144bf42016ab9b9bd8bfe8c35ff3ed5ac68da 85264 ladvd_1.1.2.orig.tar.xz
 420923b60a919b2cd97c4675fb34c2c6a44bbf7f 4416 ladvd_1.1.2-1.debian.tar.xz
 0cc2f8e128c338017882112ddaec6cfbeaf4ed48 122420 ladvd-dbgsym_1.1.2-1_amd64.deb
 482c3c13fccd5f2dd96cb73239838b678cb6e66d 6475 ladvd_1.1.2-1_amd64.buildinfo
 59797b9fd001e9f214314c4cee9f7b4680c1fcff 48368 ladvd_1.1.2-1_amd64.deb
Checksums-Sha256:
 07ddf0f881bc66fdf18dcfdc38fc930cc250a8c76e220a03ef8d04152fd97ae6 1739 
ladvd_1.1.2-1.dsc
 7f976c81fc07d59d6580de992c534e7c35873ca40d5af9f8cb6daa5c69176e37 85264 
ladvd_1.1.2.orig.tar.xz
 be8e0f94cf389c90df841f7466d64a80b6230e4594c742c3be1a999bcfcf45ba 4416 
ladvd_1.1.2-1.debian.tar.xz
 7f91d9b552fa94e8a3146aff3068953d7526e57f926ee443a72cf78a723033ea 122420 
ladvd-dbgsym_1.1.2-1_amd64.deb
 cd7c554b6e508342f9e717608147c04e0245109f6c4e3bddda173daf9c365507 6475 
ladvd_1.1.2-1_amd64.buildinfo
 9ff1c87c7d1e6da79d1c51e06b2262e930cc34b97decbf80ca741f46346a8958 48368 
ladvd_1.1.2-1_amd64.deb
Files:
 3e660336927fd77ca1f2ef5b3f0b52ab 1739 net optional ladvd_1.1.2-1.dsc
 f765ee0cd01c7c78fc136872b12aba1f 85264 net optional ladvd_1.1.2.orig.tar.xz
 a110ff22ae0aaeba9d499a994131c8f1 4416 net optional ladvd_1.1.2-1.debian.tar.xz
 0cff44772974877c1c3ede5d43040fcb 122420 debug optional 
ladvd-dbgsym_1.1.2-1_amd64.deb
 5a18b440c5ec76c70678aaab3210498b 6475 net optional 
ladvd_1.1.2-1_amd64.buildinfo
 3d5580de765b8547a9b29084e937c142 48368 net optional ladvd_1.1.2-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEGBsIcS5ipP0URKfyK/WlwSLE96QFAltLyyAACgkQK/WlwSLE
96SkZgv/WOYfuyWvuvTGYpZHJ+yMJCSzO8JF3re8lfwfIoQ54WyH5kdfz+RrLPg7
zt05MIwZU+KsnkfOcdeVImnut+U3wg2xvY0oVTiu9jBIuoQCEM8tqOir71RM0JMA
fFUKDSRqhxhtNzPrZ2de0fJdNkh6X8esA/1i6kgQq1IoMh/TAe7ML6HBVOnufWEC
WMLPnsN+MyPPIoPqfRWq/Tx7jBR71AE4aDXERqgGphxSfiZbVsF2avfAkIYkCutG
Wpg05cQU4Agwq9ZDsnQxTIoXuIsLJ2/6vudC6+pCm42g8LdIfYOE0W2+CffFZTT1
P1BD7JmlNgI8zj1maDtBJbhcU91tcZaHTXO335X4JhQPqpMo7mGlJREHOv71gaa4
UihbNOpvfehDYAzoJiZpFj2p6Q4d1xdipY/G5C0LPns8zsONNl8qdrlBFJGTDjhg

Bug#903862: FTBFS: override_dh_auto_test exits with exit 2

[Vincent Lefevre]

It is the following test that fails:

Start  22: test-real-data
 22/118 Test  #22: test-real-data ...***Failed
0.01 sec

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#903868: heat: FTBFS in buster/sid (dh_installman: Cannot find "doc/build/man/heat-api.1")

[Santiago Vila]

Package: src:heat
Version: 1:10.0.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python3,sphinxdoc,systemd
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_autoreconf -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

writing output... [ 92%] template_guide/hot_guide
writing output... [ 93%] template_guide/hot_spec
writing output... [ 94%] template_guide/index
writing output... [ 95%] template_guide/openstack
writing output... [ 96%] template_guide/software_deployment
writing output... [ 97%] template_guide/unsupported
writing output... [ 98%] templates/cfn/WordPress_Single_Instance
writing output... [ 99%] templates/hot/hello_world
writing output... [100%] templates/index

/<>/doc/source/admin/auth-model.rst:74: WARNING: unknown document: 
identity-management
WARNING: Cannot get gitsha from git repository.
/<>/doc/source/admin/stack-domain-users.rst:120: WARNING: unknown 
document: identity-management
/<>/doc/source/template_guide/environment.rst:55: WARNING: unknown 
option: -e
/<>/doc/source/template_guide/environment.rst:58: WARNING: unknown 
option: --parameter
/<>/doc/source/template_guide/environment.rst:62: WARNING: unknown 
option: --parameter
generating indices... genindex
writing additional pages... search
copying static files... done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 59 warnings.

The HTML pages are in debian/heat-doc/usr/share/doc/heat-doc/html.
dh_sphinxdoc
dh_sphinxdoc: ignoring unknown JavaScript code: 
debian/heat-doc/usr/share/doc/heat-doc/html/_static/js/bootstrap.min.js
dh_sphinxdoc: ignoring unknown JavaScript code: 
debian/heat-doc/usr/share/doc/heat-doc/html/_static/js/docs.js
dh_sphinxdoc: ignoring unknown JavaScript code: 
debian/heat-doc/usr/share/doc/heat-doc/html/_static/js/navigation.js
dh_sphinxdoc: ignoring unknown JavaScript code: 
debian/heat-doc/usr/share/doc/heat-doc/html/_static/js/webui-popover.js
make[1]: Leaving directory '/<>'
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
if [ -e /<>/debian/CHANGELOG ] ; then \
dh_installchangelogs /<>/debian/CHANGELOG ; \
else \
dh_installchangelogs ; \
fi
make[1]: Leaving directory '/<>'
   dh_installman -i -O--buildsystem=python_distutils
dh_installman: Cannot find (any matches for) "doc/build/man/heat-api.1" (tried 
in .)

dh_installman: Aborting due to earlier error
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

[ Note: There has been a recent change in debhelper behaviour, the current
  behaviour is the intended one. See Bug #903133 for details ].

Thanks.

Bug#903867: cod-tools: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Package: src:cod-tools
Version: 2.2+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --no-parallel
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>/cod-tools-2.2+dfsg'
Makefile:138: .diff.depend: No such file or directory
tools/mkperldepend scripts/cif-to-utf8 > scripts/.cif-to-utf8.d
tools/mkperldepend scripts/cif2cod > scripts/.cif2cod.d
tools/mkperldepend scripts/cif2csv > scripts/.cif2csv.d
tools/mkperldepend scripts/cif2json > scripts/.cif2json.d
tools/mkperldepend scripts/cif2rdf > scripts/.cif2rdf.d

[... snipped ...]

pycodcif.c:322:43: warning: passing argument 3 of 'PyDict_SetItemString' makes 
pointer from integer without a cast [-Wint-conversion]
 PyDict_SetItemString( ret, "nerrors", PyInt_FromLong( nerrors ) );
   ^~
In file included from /usr/include/python3.6m/Python.h:90:0,
 from pycodcif.c:1:
/usr/include/python3.6m/dictobject.h:160:17: note: expected 'PyObject * {aka 
struct _object *}' but argument is of type 'int'
 PyAPI_FUNC(int) PyDict_SetItemString(PyObject *dp, const char *key, PyObject 
*item);
 ^~~~
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,-z,relro -Wl,-z,now -g -O2 
-fdebug-prefix-map=/<>/cod-tools-2.2+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/externals/cexceptions/cxprintf.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/externals/cexceptions/stringx.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/externals/cexceptions/allocx.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/externals/cexceptions/stdiox.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/externals/cexceptions/cexceptions.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/cif_options.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/common.o
 build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/compo
 nents/codcif/ciftable.o 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/cif2_lexer.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/cifvalue.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/cifmessage.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/cif_grammar_flex.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/cif_lexer.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/cif.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/datablock.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/cif_compiler.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/ciflist.o
 
build/temp.linux-x86_64-3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/cif_grammar.tab.o
 build/temp.linux-x86_64-
 3.6/<>/cod-tools-2.2+dfsg/src/components/codcif/cif2_grammar.tab.o 
build/temp.linux-x86_64-3.6/pycodcif_wrap.o 
build/temp.linux-x86_64-3.6/pycodcif.o -o 
build/lib.linux-x86_64-3.6/pycodcif/_pycodcif.cpython-36m-x86_64-linux-gnu.so
running install_lib
creating /<>/cod-tools-2.2+dfsg/debian/python3-pycodcif
creating /<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr
creating /<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr/local
creating /<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr/local/lib
creating 
/<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr/local/lib/python3.6
creating 
/<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr/local/lib/python3.6/dist-packages
creating 
/<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr/local/lib/python3.6/dist-packages/pycodcif
copying 
build/lib.linux-x86_64-3.6/pycodcif/_pycodcif.cpython-36m-x86_64-linux-gnu.so 
-> 
/<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr/local/lib/python3.6/dist-packages/pycodcif
copying build/lib.linux-x86_64-3.6/pycodcif/__init__.py -> 
/<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr/local/lib/python3.6/dist-packages/pycodcif
copying build/lib.linux-x86_64-3.6/pycodcif/pycodcif.py -> 
/<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr/local/lib/python3.6/dist-packages/pycodcif
byte-compiling 
/<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr/local/lib/python3.6/dist-packages/pycodcif/__init__.py
 to __init__.cpython-36.pyc
byte-compiling 
/<>/cod-tools-2.2+dfsg/debian/python3-pycodcif/usr/local/lib/python3.6/dist-packages/pycodcif/pycodcif.py
 to pycodcif.cpython-36.pyc
running install_egg_info
running egg_info

Bug#903866: python-{clang,lldb}-4.0: missing Breaks+Replaces against python-clang-3.[45], python-lldb-3.5

[Andreas Beckmann]

Package: python-clang-4.0,python-lldb-4.0
Version: 1:4.0.1-10~deb9u2
Severity: serious
Tags: stretch
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb ...
  Unpacking python-clang-4.0 (1:4.0.1-10~deb9u2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/clang/__init__.py', 
which is also in package python-clang-3.4 1:3.4.2-13
  Errors were encountered while processing:
   /var/cache/apt/archives/python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb

  Preparing to unpack .../python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb ...
  Unpacking python-clang-4.0 (1:4.0.1-10~deb9u2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/clang/__init__.py', 
which is also in package python-clang-3.5 1:3.5-10
  Errors were encountered while processing:
   /var/cache/apt/archives/python-clang-4.0_1%3a4.0.1-10~deb9u2_amd64.deb

  Selecting previously unselected package python-lldb-4.0.
  Preparing to unpack .../python-lldb-4.0_1%3a4.0.1-10~deb9u2_amd64.deb ...
  Unpacking python-lldb-4.0 (1:4.0.1-10~deb9u2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-lldb-4.0_1%3a4.0.1-10~deb9u2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/lldb', which is also 
in package python-lldb-3.5 1:3.5-10

The inclusion of llvm-4.0 in stretch brought it into proximity of the
old packages from jessie (that predate the virtual python-{clang,lldb}-x.y
packages), which might remain after an upgrade from jessie to stretch.



cheers,

Andreas


python-clang-3.4=1%3.4.2-13_python-clang-4.0=1%4.0.1-10~deb9u2.log.gz
Description: application/gzip

Processed: Re: FTBFS: override_dh_auto_test exits with exit 2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 903862 ftbfs
Bug #903862 [src:gnucash] FTBFS: override_dh_auto_test exits with exit 2
Added tag(s) ftbfs.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
903862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903862: FTBFS: override_dh_auto_test exits with exit 2

[Vincent Lefevre]

Source: gnucash
Version: 3.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The build with "apt-get source -b gnucash" ends with:

[...]
118/118 Testing: python-bindings
118/118 Test: python-bindings
Command: "/usr/bin/python3" 
"/home/vinc17/tmp/gnucash-3.2/bindings/python/tests/runTests.py.in"
Directory: /home/vinc17/tmp/gnucash-3.2/.build/bindings/python/tests
"python-bindings" start time: Jul 15 23:33 CEST
Output:
--
* 23:33:21  WARN  no backend loaded, or the backend doesn't 
define register_cb, returning 0
* 23:33:21  WARN  no backend loaded, or the backend doesn't 
define register_cb, returning 0
* 23:33:21  WARN  no backend loaded, or the backend doesn't 
define register_cb, returning 0
* 23:33:21  WARN  no backend loaded, or the backend doesn't 
define register_cb, returning 0
* 23:33:21  WARN  no backend loaded, or the backend doesn't 
define register_cb, returning 0
.
--
Ran 41 tests in 0.150s

OK

Test time =   0.35 sec
--
Test Passed.
"python-bindings" end time: Jul 15 23:33 CEST
"python-bindings" time elapsed: 00:00:00
--

End testing: Jul 15 23:33 CEST
+ exit 2
make[1]: *** [debian/rules:83: override_dh_auto_test] Error 2
make[1]: Leaving directory '/home/vinc17/tmp/gnucash-3.2'
make: *** [debian/rules:26: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
E: Build command 'cd gnucash-3.2 && dpkg-buildpackage -b -uc' failed.

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

Kernel: Linux 4.16.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)
LSM: AppArmor: enabled

-- no debconf information

Bug#903860: python3-stem: File "/usr/lib/python3/dist-packages/stem/util/test/test_tools.py", line 151 / self.method.async = self /

[Jacobi]

Package: python3-stem
Version: 1.6.0-1
Severity: serious
Tags: a11y
Justification: fails to build from source

Dear Maintainer,



   * What led up to the situation?
Package was pulled in as a dependency for nyx which is a dependency for tor-arm 
and onionshare
   * What exactly did you do (or not do) that was effective (or
 ineffective)?  Have tried purging and building from source.  Have dpkg 
--purge to reinstall the package but was also not effective. 
   * What was the outcome of this action?
Package still will not install
   * What outcome did you expect instead?
Hoping a rebuild would have helped



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

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 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 python3-stem depends on:
ii  python3  3.6.6-1

python3-stem recommends no packages.

python3-stem suggests no packages.

-- no debconf information

Bug#903849: marked as done (klibc rebuilt with toolchain from unstable crashes at startup on amd64)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 21:37:06 +
with message-id 
and subject line Bug#903849: fixed in klibc 2.0.4-12
has caused the Debian Bug report #903849,
regarding klibc rebuilt with toolchain from unstable crashes at startup on amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
903849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:klibc
Version: 2.0.4-11
Severity: grave

Rebuilding the current version of klibc for amd64 adds a large amount
of padding to the .text and .rodata sections of klibc.so:

/lib/klibc-MiRPTuou9LIwcm_gDpcF7E1m-p8.so: file format elf64-x86-64

Sections:
Idx Name  Size  VMA   LMA   File off  Algn
  0 .text d1ff  00200200  00200200  0200  2**2
  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .rodata   31af  0030  0030  0010  2**5
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  2 .data.rel.ro  0990  00403660  00403660  00103660  2**5
  CONTENTS, ALLOC, LOAD, DATA
  3 .data 0140  00404000  00404000  00104000  2**5
  CONTENTS, ALLOC, LOAD, DATA
  4 .bss  42f8  00404140  00404140  00104140  2**5
  ALLOC

This results in an address conflict with all klibc binaries and an
immediate crash when klibc jumps to the start of the binary.

Other architectures might also be affected.

Ben.

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

Kernel: Linux 4.17.0-1-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)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: klibc
Source-Version: 2.0.4-12

We believe that the bug you reported is fixed in the latest version of
klibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated klibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jul 2018 22:22:07 +0100
Source: klibc
Binary: libklibc-dev libklibc klibc-utils
Architecture: source
Version: 2.0.4-12
Distribution: unstable
Urgency: medium
Maintainer: maximilian attems 
Changed-By: Ben Hutchings 
Description:
 klibc-utils - small utilities built with klibc for early boot
 libklibc   - minimal libc subset for use with initramfs
 libklibc-dev - kernel headers used during the build of klibc
Closes: 863761 884716 886939 891924 903849
Changes:
 klibc (2.0.4-12) unstable; urgency=medium
 .
   [ Ben Hutchings ]
   * debian/control: Point Vcs URLs to Salsa
   * debian/klibc-utils.postinst: Remove diversion of initramfs-tools hook
 script (Closes: #886939)
   * [klibc] mips64: compile with -mno-abicalls, thanks to James Cowgill
 (Closes: #891924)
   * reboot: Add support for reboot syscall argument, thanks to Alfonso
 Sanchez-Beato (Closes: #863761, LP: #1692494)
   * [klibc] x86_64: Reduce ld max-page-size option again (Closes: #903849)
   * Never clean files in quilt status directory
 .
   [ Frank Scheiner ]
   * [klibc] ia64: Build static tools (again)
 .
   [ Benjamin Drung ]
   * ipconfig: Implement classless static routes (Closes: #884716, LP: #1526956)
   * mount_main: Fix empty string check
Checksums-Sha1:
 fa6f64a531a165ff4bdb91ca1837937665ff5481 2031 klibc_2.0.4-12.dsc
 fb18065967c348abf6d7f244cca72d5fa3ebe167 37588 klibc_2.0.4-12.debian.tar.xz
 66dda1bc3a2c3ca5182ab589c7ff47c8b00fba8e 5944 klibc_2.0.4-12_source.buildinfo
Checksums-Sha256:
 de8078b3b7e13a2242b470cf54ffed8b94ea8251ee9754125e46cbd1c49c01eb 2031 
klibc_2.0.4-12.dsc
 

Bug#886939: marked as done (klibc-utils: leaves diversion after upgrade from stretch)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 21:37:06 +
with message-id 
and subject line Bug#886939: fixed in klibc 2.0.4-12
has caused the Debian Bug report #886939,
regarding klibc-utils: leaves diversion after upgrade from stretch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
886939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: klibc-utils
Version: 2.0.4-11
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove some
diversions after upgrading from stretch and removing the package
afterwards.

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

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

0m26.9s ERROR: FAIL: Installed diversions (dpkg-divert) not removed by purge:
  diversion of /usr/share/initramfs-tools/hooks/klibc to 
/usr/share/initramfs-tools/hooks/klibc^i-t by klibc-utils


The test did the following:
  setup minimal stretch chroot
  install $package/stretch
  distupgrade buster
  remove $package
  purge $package

cheers,

Andreas


klibc-utils_2.0.4-11.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: klibc
Source-Version: 2.0.4-12

We believe that the bug you reported is fixed in the latest version of
klibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 886...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated klibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jul 2018 22:22:07 +0100
Source: klibc
Binary: libklibc-dev libklibc klibc-utils
Architecture: source
Version: 2.0.4-12
Distribution: unstable
Urgency: medium
Maintainer: maximilian attems 
Changed-By: Ben Hutchings 
Description:
 klibc-utils - small utilities built with klibc for early boot
 libklibc   - minimal libc subset for use with initramfs
 libklibc-dev - kernel headers used during the build of klibc
Closes: 863761 884716 886939 891924 903849
Changes:
 klibc (2.0.4-12) unstable; urgency=medium
 .
   [ Ben Hutchings ]
   * debian/control: Point Vcs URLs to Salsa
   * debian/klibc-utils.postinst: Remove diversion of initramfs-tools hook
 script (Closes: #886939)
   * [klibc] mips64: compile with -mno-abicalls, thanks to James Cowgill
 (Closes: #891924)
   * reboot: Add support for reboot syscall argument, thanks to Alfonso
 Sanchez-Beato (Closes: #863761, LP: #1692494)
   * [klibc] x86_64: Reduce ld max-page-size option again (Closes: #903849)
   * Never clean files in quilt status directory
 .
   [ Frank Scheiner ]
   * [klibc] ia64: Build static tools (again)
 .
   [ Benjamin Drung ]
   * ipconfig: Implement classless static routes (Closes: #884716, LP: #1526956)
   * mount_main: Fix empty string check
Checksums-Sha1:
 fa6f64a531a165ff4bdb91ca1837937665ff5481 2031 klibc_2.0.4-12.dsc
 fb18065967c348abf6d7f244cca72d5fa3ebe167 37588 klibc_2.0.4-12.debian.tar.xz
 66dda1bc3a2c3ca5182ab589c7ff47c8b00fba8e 5944 klibc_2.0.4-12_source.buildinfo
Checksums-Sha256:
 de8078b3b7e13a2242b470cf54ffed8b94ea8251ee9754125e46cbd1c49c01eb 2031 
klibc_2.0.4-12.dsc
 626471808ca50fc7812c05b91dc21c9ee170dd0908052707c6dedd3f0a0dd77f 37588 
klibc_2.0.4-12.debian.tar.xz
 8cb10acbaa2dab9f60ca5fa35902d01e0921ce86677a68b8ccdfc436f6ee907a 5944 
klibc_2.0.4-12_source.buildinfo
Files:
 ff65d734e012b8015ed2453ff772b1d2 2031 libs optional klibc_2.0.4-12.dsc
 fb8b4a2c57822aadd1992723d9f01df6 37588 libs optional 
klibc_2.0.4-12.debian.tar.xz
 ca06e9bc2786acf8ee7e7e895579d999 5944 libs optional 
klibc_2.0.4-12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAltLuyQACgkQ57/I7JWG
EQlfpw//dX5zfuZPaKnVDfyCXM9Usx6mhLCeI6DI/b85IlPGcMQGfftRfIMXSfsW
mp1SEHaNuforocIleoTAOWiDIITaFhbX8BxnZF20VesEYjzjxbZBS1tF8wOm/mbO
giFkjIzko2RCqlso0/RL0RZj+n4ISHZlo/IsFUNngR5520DnC3S7ARQockGRxyus
3GUzfv7CxXgQPOjChTE9NskK10vC749vOwlsmfkW4adSOVn6Ney0bBhvNViurRmj
Yc1EVWSSolmVcivLIKFosRhcvO3Sv7XbvZ8yZ1k/QCAOlEpfHF929ztfSwnkQqaZ

Bug#903855: CVE-2016-10522

[Moritz Muehlenhoff]

Package: ruby-rails-admin
Severity: grave
Tags: security

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10522

Bug#903803: marked as done (puredata-gui: missing Breaks+Replaces: puredata-core (<< 0.48.1-6))

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 20:43:07 +
with message-id 
and subject line Bug#903803: fixed in puredata 0.48.1-7
has caused the Debian Bug report #903803,
regarding puredata-gui: missing Breaks+Replaces: puredata-core (<< 0.48.1-6)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
903803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puredata-gui
Version: 0.48.1-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../puredata-gui_0.48.1-6_all.deb ...
  Unpacking puredata-gui (0.48.1-6) ...
  dpkg: error processing archive 
/var/cache/apt/archives/puredata-gui_0.48.1-6_all.deb (--unpack):
   trying to overwrite '/usr/share/pixmaps/puredata.xpm', which is also in 
package puredata-core 0.48.1-4
  Errors were encountered while processing:
   /var/cache/apt/archives/puredata-gui_0.48.1-6_all.deb


cheers,

Andreas


puredata-core=0.48.1-4_puredata-gui=0.48.1-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: puredata
Source-Version: 0.48.1-7

We believe that the bug you reported is fixed in the latest version of
puredata, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
puredata package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Jul 2018 22:03:54 +0200
Source: puredata
Binary: puredata puredata-core puredata-gui puredata-gui-l10n puredata-doc 
puredata-dev puredata-utils puredata-extra
Architecture: source
Version: 0.48.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 puredata   - realtime computer music and graphics system
 puredata-core - realtime computer music and graphics system - core components
 puredata-dev - realtime computer music and graphics system - development files
 puredata-doc - realtime computer music and graphics system - documentation
 puredata-extra - realtime computer music and graphics system - extra files
 puredata-gui - realtime computer music and graphics system - GUI
 puredata-gui-l10n - realtime computer music and graphics system - translations
 puredata-utils - realtime computer music and graphics system - utility programs
Closes: 903803
Changes:
 puredata (0.48.1-7) unstable; urgency=medium
 .
   * Updated Breaks+Replaces due to moving puredata.xpm between packages
 (Closes: #903803)
 (LP: #1781512)
Checksums-Sha1:
 34b4b653a633b3cb9ba7913f822dd747e707d06c 2508 puredata_0.48.1-7.dsc
 3043da9a49f4303897190c7cf23054bd02e87c27 30752 puredata_0.48.1-7.debian.tar.xz
 e429d962c9f269c8845a4c7b2695b65ff008ed75 8948 puredata_0.48.1-7_amd64.buildinfo
Checksums-Sha256:
 cf00955bec4235765e8058dd9a90f11223dadb6d25c5a6bf99e6a780ca4d06b8 2508 
puredata_0.48.1-7.dsc
 5bd722479b90a3f2fe522be6ef9adc3d86a4df25de44e628ff4c23d870435f0e 30752 
puredata_0.48.1-7.debian.tar.xz
 7e2ca29ed33f935ae886186c17bd8bb684315b62052969e9c1442718c4541c18 8948 
puredata_0.48.1-7_amd64.buildinfo
Files:
 5de2f88b7327b521c3da687b520050d3 2508 sound optional puredata_0.48.1-7.dsc
 60cf55f842337cf4c1f4024049feb628 30752 sound optional 
puredata_0.48.1-7.debian.tar.xz
 0af0c9496f56e46c3152915797036b45 8948 sound optional 
puredata_0.48.1-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAltLqZ0ACgkQtlAZxH96
Nvh1iRAAg9crSbto4hQDV5hh5KUKP/YP909tQHcHprJCB3R6bAUc7OHTwUbCRhD1
tz1B9hfc26uYBstEp3RI3m98NMocyzNahkqYY5K1KxoaIZp3nHeOCOiu5PnykFoH

Bug#903821: [Pkg-xen-devel] Bug#903821: xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)

[Hans van Kranenburg]

Hi,

On 07/15/2018 12:16 PM, Benoît Tonnerre wrote:
> [...]
> 
> After updating 3 Xen servers from stretch (9.4) to stretch (9.5), I
> notice a kernel panic on these 3 servers.

Thanks for the report.

This is probably all related:

This went into 4.9.102:
https://www.spinics.net/lists/kernel/msg2808364.html

This into 4.9.107:
https://www.spinics.net/lists/stable/msg242657.html

And this went into 4.9.112:
https://www.spinics.net/lists/stable/msg246729.html

Apparently kernels from 4.9.107 to 4.9.111 don't boot correctly.

Hans

Processed: Bug #903803 in puredata marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #903803 [puredata-gui] puredata-gui: missing Breaks+Replaces: puredata-core 
(<< 0.48.1-6)
Added tag(s) pending.

-- 
903803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903803: Bug #903803 in puredata marked as pending

[IOhannes m zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/pd/puredata/commit/219623bc1b4ffea19b9def09db27e0e45415ace7


Updated Breaks+Replaces due to moving puredata.xpm between packages

Closes: #903803



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/903803

Bug#903849: klibc rebuilt with toolchain from unstable crashes at startup on amd64

[Ben Hutchings]

Package: src:klibc
Version: 2.0.4-11
Severity: grave

Rebuilding the current version of klibc for amd64 adds a large amount
of padding to the .text and .rodata sections of klibc.so:

/lib/klibc-MiRPTuou9LIwcm_gDpcF7E1m-p8.so: file format elf64-x86-64

Sections:
Idx Name  Size  VMA   LMA   File off  Algn
  0 .text d1ff  00200200  00200200  0200  2**2
  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .rodata   31af  0030  0030  0010  2**5
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  2 .data.rel.ro  0990  00403660  00403660  00103660  2**5
  CONTENTS, ALLOC, LOAD, DATA
  3 .data 0140  00404000  00404000  00104000  2**5
  CONTENTS, ALLOC, LOAD, DATA
  4 .bss  42f8  00404140  00404140  00104140  2**5
  ALLOC

This results in an address conflict with all klibc binaries and an
immediate crash when klibc jumps to the start of the binary.

Other architectures might also be affected.

Ben.

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

Kernel: Linux 4.17.0-1-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)
LSM: AppArmor: enabled

Bug#903821: 4.16 kernel

[Maxmédia Kft Szerviz]

Hi,

Thanks your report! I can start my system with 4.16 backport kernel.

Bug#903821: linux-image-4.9.0-7-amd64: Can not boot 4.9.0_7_amd64 with Xen

[Sebastien KOECHLIN]

Package: src:linux
Followup-For: Bug #903821

When booting with the new kernel, I got the following Dom0 crash:

Loading Xen 4.8-amd64 ...
Loading Linux 4.9.0-7-amd64 ...
Loading initial ramdisk ...
(XEN) Xen version 4.8.4-pre (Debian 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9) 
(ijack...@chiark.greenend.org.uk) (gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516) 
debug=n  Fri Jun 22 15:50:19 UTC 2018
(XEN) Bootloader: GRUB 2.02~beta3-5
(XEN) Command line: placeholder dom0_mem=4096M,max:4096M com2=57600,8n1 
console=com2,vga
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 2 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 4 MBR signatures
(XEN)  Found 4 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)   - 000a (usable)
(XEN)  0010 - 7faa (usable)
(XEN)  7faa - 7fab6000 (reserved)
(XEN)  7fab6000 - 7fad5c00 (ACPI data)
(XEN)  7fad5c00 - 8000 (reserved)
(XEN)  e000 - f000 (reserved)
(XEN)  fe00 - 0001 (reserved)
(XEN)  0001 - 00068000 (usable)
(XEN) ACPI: RSDP 000F23D0, 0024 (r2 DELL  )
(XEN) ACPI: XSDT 000F245C, 00AC (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: FACP 7FAD34F8, 00F4 (r3 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: DSDT 7FAB6000, 3E0D (r1 DELL   PE_SC3  1 INTL 20050624)
(XEN) ACPI: FACS 7FAD5C00, 0040
(XEN) ACPI: APIC 7FAD3078, 008A (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: SPCR 7FAD3104, 0050 (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: HPET 7FAD3158, 0038 (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: MCFG 7FAD3194, 003C (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: WD__ 7FAD31D4, 0134 (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: SLIC 7FAD330C, 0024 (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: ERST 7FABBB88, 0210 (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: HEST 7FABBD98, 027C (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: BERT 7FABBA08, 0030 (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: EINJ 7FABBA38, 0150 (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: TCPA 7FAD3490, 0064 (r1 DELL   PE_SC3  1 DELL1)
(XEN) ACPI: SSDT 7FAB9E0D, 0454 (r1 DELL   PE_SC3 11 INTL 20050624)
(XEN) ACPI: SSDT 7FABA4B3, 0454 (r1 DELL   PE_SC3 11 INTL 20050624)
(XEN) ACPI: SSDT 7FABAB59, 0454 (r1 DELL   PE_SC3 11 INTL 20050624)
(XEN) ACPI: SSDT 7FABB1FF, 0454 (r1 DELL   PE_SC3 11 INTL 20050624)
(XEN) ACPI: SSDT 7FABB8A5, 0162 (r1 DELL   PE_SC3 10 INTL 20050624)
(XEN) System RAM: 24570MB (25159936kB)
(XEN) Domain heap initialised
(XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec0, GSI 0-23
(XEN) IOAPIC[1]: apic_id 5, version 32, address 0xfec1, GSI 256-279
(XEN) IOAPIC[2]: apic_id 6, version 32, address 0xfec1, GSI 64-87
(XEN) Enabling APIC mode:  Flat.  Using 3 I/O APICs
(XEN) Failed to get Error Log Address Range.
(XEN) xstate: size: 0x240 and states: 0x3
(XEN) Unrecognised CPU model 0x17 - assuming vulnerable to LazyFPU
(XEN) Speculative mitigation facilities:
(XEN)   Hardware features:
(XEN)   Compiled-in support: INDIRECT_THUNK
(XEN)   Xen settings: BTI-Thunk RETP(XEN) Allocated console ring of 16 KiB.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: ASIDs disabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) not detected
(XEN) Brought up 4 CPUs
(XEN) Dom0 has maximum 856 PIRQs
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x1f66000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   00066a00->00066c00 (1035540 pages to be 
allocated)
(XEN)  Init. ramdisk: 00067ed14000->00067e7e
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: 8100->81f66000
(XEN)  Init. ramdisk: ->
(XEN)  Phys-Mach map: 0080->00800080
(XEN)  Start info:81f66000->81f664b4
(XEN)  Page tables:   81f67000->81f7a000
(XEN)  Boot stack:81f7a000->81f7b000
(XEN)  TOTAL: 8000->8200
(XEN)  ENTRY ADDRESS: 81d3d180
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs
(XEN) done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch 

Processed: limit source to klibc, tagging 891924, tagging 886939, tagging 884716

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source klibc
Limiting to bugs with field 'source' containing at least one of 'klibc'
Limit currently set to 'source':'klibc'

> tags 891924 + pending
Bug #891924 [libklibc] klibc: crashes on mips64el if any syscall fails
Added tag(s) pending.
> tags 886939 + pending
Bug #886939 [klibc-utils] klibc-utils: leaves diversion after upgrade from 
stretch
Added tag(s) pending.
> tags 884716 + pending
Bug #884716 [klibc-utils] klibc-utils: Please support classless static routes 
(RFC3442)
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884716
886939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886939
891924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903800: Confirming same problem as Dom0 or DomU

[Jered Floyd]

I'm seeing the same behavior; this kernel cannot be used as a Dom0 or DomU 
kernel on xen-hypervisor-4.8-amd64. 

So glad for remote IPMI KVM... that was almost a disaster. 

--Jered 

Bug#896725: marked as done (dlmodelbox: missing build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 17:49:05 +
with message-id 
and subject line Bug#896725: fixed in dlmodelbox 0.1.3-1
has caused the Debian Bug report #896725,
regarding dlmodelbox: missing build dependency on dh-python
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
896725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dlmodelbox
Version: 0.1.2-2
Severity: serious

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

...
 fakeroot debian/rules clean
dh clean --with python3
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 7) line 
1.
BEGIN failed--compilation aborted at (eval 7) line 1.

make: *** [debian/rules:8: clean] Error 2
--- End Message ---
--- Begin Message ---
Source: dlmodelbox
Source-Version: 0.1.3-1

We believe that the bug you reported is fixed in the latest version of
dlmodelbox, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bofu Chen (bafu)  (supplier of updated dlmodelbox package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 12 Jul 2018 17:25:07 +0800
Source: dlmodelbox
Binary: dlmodelbox
Architecture: source all
Version: 0.1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Bofu Chen (bafu) 
Changed-By: Bofu Chen (bafu) 
Description:
 dlmodelbox - Swiss Army Knife of Deep Learning Models
Closes: 896725
Changes:
 dlmodelbox (0.1.3-1) unstable; urgency=medium
 .
   * Upstream updates.
   * debian/control:
 - Fix build dependency issue. (Closes: #896725)
Checksums-Sha1:
 f8cc1c2b561bc7ab2fcbed956950f7e0e4a85074 1751 dlmodelbox_0.1.3-1.dsc
 6a0d5ec3a4a2d58971575606993b2ff270b21d2b 3493 dlmodelbox_0.1.3.orig.tar.gz
 72977047982adf0fb2c0659d50746b1df480c869 3048 dlmodelbox_0.1.3-1.debian.tar.xz
 8ffcb46f8c0b0b54d74e343b3f427a933134f81b 6244 dlmodelbox_0.1.3-1_all.deb
 8a2e94711af29f254b72bb99dc38cd48942ec966 6341 
dlmodelbox_0.1.3-1_amd64.buildinfo
Checksums-Sha256:
 0fc74f3e69e1f5cd2f253f71672a8dcc573969de2f48cea3c925a16b9709122f 1751 
dlmodelbox_0.1.3-1.dsc
 a0777252ed2804e5ec6af3094c6667c04eb811bfd55cd7f2ffecfff72e10b28e 3493 
dlmodelbox_0.1.3.orig.tar.gz
 b429fce541734be6b1822041f98786268b585ac1168300d12562f2d9e1ad6235 3048 
dlmodelbox_0.1.3-1.debian.tar.xz
 60d4bec19fab0329a052ad9ad2e6b8cf7869e5ec017bdf977c1f7eb1cec6a1d0 6244 
dlmodelbox_0.1.3-1_all.deb
 df204e1de3c4bf5d81cd5c4088c20acb37f4ab6c8d3b4f31cfd4740d0820e798 6341 
dlmodelbox_0.1.3-1_amd64.buildinfo
Files:
 faee221b9e8ae3cc61fbbc20ad9629c2 1751 science optional dlmodelbox_0.1.3-1.dsc
 1604aaf26b1a599d171542f2630f7ed5 3493 science optional 
dlmodelbox_0.1.3.orig.tar.gz
 6639829fc31f358573a4c18105db679a 3048 science optional 
dlmodelbox_0.1.3-1.debian.tar.xz
 6fa48cf6e78fd54c21210845f4ddbada 6244 science optional 
dlmodelbox_0.1.3-1_all.deb
 cca6cea0c1267b9ef8486542da352338 6341 science optional 
dlmodelbox_0.1.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAltLhYsACgkQRBc/oT0F
iIjGRg/9FeJ58nMRBleFtBib6dehFwMOnksrlToA5cXHixv53OiffoRzji3g10eG
mIVzvtZ73oS3iFQvxGUGMQnvqRrpo1BHRJx+oKMn+oo1lgdJVtlF2koyVcLCE68O
kJgrAh8W2mVJn5ItpmnNE3OBVa9PYx4dg6ZNJ2TyPW2PFrdk86Sx2C5z3dncxPc8
o/FOLXS/fEH0vnl7XgsmMb5nL3GDL74qqlQ9MbKrhILVPCXeKgn8P5zdtNVMo5RY
jxXRsw9QYGBxt6NnUNMXUUJqcKgCqli2MsCftG1nTIdfKCy7bujBUQQ7Z1L/KMW5
9PMZWasqu2gJOMPQqwE+pFZCTDNHh6qbwZ6e/D7PWkXYiqlYUJ5rYEz3J75cbahQ
PDUQsP9vUuGm32iOfzXj0UFLEfQllC5Ifo7kCJDD2rXMmHmW68RcP8cnYqU8+AzU
0/8+1DNxElcHlmHK1Dvq2YT1aHZCxRo5OzV2PlpZ61ZTfyeqy4YgGk/A95WqZ6w+
ONwAxPc1aW4gsFXlSDw6jl5FKI4xR7FLeRO0LAOouJ648AFOuw3I2EqrDnoKVcXf

Bug#903328: marked as done (cobertura: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 17:48:57 +
with message-id 
and subject line Bug#903328: fixed in cobertura 2.1.1-2
has caused the Debian Bug report #903328,
regarding cobertura: FTBFS in buster/sid (dh_installdocs: Cannot find "README")
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
903328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cobertura
Version: 2.1.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with javahelper
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
mh_patchpoms -plibcobertura-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
[ERROR] Cannot find parent dependency 
net.sourceforge.cobertura.poms:cobertura-api-parent:pom:2.1.1, use --no-parent 
option to resolve this issue or install the parent POM in the Maven repository
[ERROR] Cannot find parent dependency 
net.sourceforge.cobertura.poms:cobertura-parent:pom:2.1.1, use --no-parent 
option to resolve this issue or install the parent POM in the Maven repository
   jh_linkjars -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
WARNING: An illegal reflective access operation has occurred

[... snipped ...]

[INFO] [ pom ]-
[INFO] 
[INFO] --- debian-maven-plugin:2.3:install (default-cli) @ cobertura-runtime ---
[INFO] Cleaning pom file: /<>/cobertura-runtime/pom.xml.save with 
options:
[INFO]  --keep-pom-version --package=libcobertura-java --has-package-version
[INFO]  --rules=/<>/debian/maven.rules
[INFO]  --ignore-rules=/<>/debian/maven.ignoreRules
[INFO]  --published-rules=/<>/debian/maven.ignoreRules
[INFO]  --no-parent
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] cobertura-parent ... SUCCESS [  0.469 s]
[INFO] cobertura-api-parent ... SUCCESS [  0.190 s]
[INFO] cobertura-reactor 2.1.1  SUCCESS [  0.044 s]
[INFO] cobertura-poms-reactor . SUCCESS [  0.097 s]
[INFO] cobertura-annotations-api .. SUCCESS [  0.087 s]
[INFO] cobertura-interaction-reactor .. SUCCESS [  0.026 s]
[INFO] cobertura-annotations-reactor .. SUCCESS [  0.032 s]
[INFO] Cobertura code coverage  SUCCESS [  0.180 s]
[INFO] Cobertura Limited Runtime 2.1.1  SUCCESS [  0.034 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 2.551 s
[INFO] Finished at: 2018-07-08T09:42:45Z
[INFO] 
mh_resolve_dependencies --non-interactive --offline --build 
-plibcobertura-java --base-directory=/<> --non-explore
Analysing pom.xml...
Analysing cobertura/pom.xml...
Analysing cobertura-runtime/pom.xml...
Analysing interaction/pom.xml...
Checking the parent dependency in the sub project interaction/pom.xml
Analysing interaction/annotations/pom.xml...
Checking the parent dependency in the sub project 
interaction/annotations/pom.xml
Analysing interaction/annotations/annotations-api/pom.xml...
Analysing poms/pom.xml...
Checking the parent dependency in the sub project poms/pom.xml
Analysing poms/cobertura-api-parent/pom.xml...
Analysing poms/cobertura-parent/pom.xml...
mh_unpatchpoms -plibcobertura-java
   dh_install -i
   jh_installjavadoc -i
   dh_installdocs -i
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:4: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2

Processed: reassign 903767 to src:linux, forcibly merging 903767 903800, severity of 903767 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 903767 src:linux 4.9.110-1
Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 
4.8
Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / 
kernel panic at boot
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Ignoring request to reassign bug #903767 to the same package
Ignoring request to reassign bug #903800 to the same package
Ignoring request to reassign bug #903821 to the same package
Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 
4.8
Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / 
kernel panic at boot
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Ignoring request to alter found versions of bug #903767 to the same values 
previously set
Ignoring request to alter found versions of bug #903800 to the same values 
previously set
Ignoring request to alter found versions of bug #903821 to the same values 
previously set
> forcemerge 903767 903800
Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 
4.8
Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / 
kernel panic at boot
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / 
kernel panic at boot
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Merged 903767 903800 903821
> severity 903767 serious
Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 
4.8
Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / 
kernel panic at boot
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Ignoring request to change severity of Bug 903767 to the same value.
Ignoring request to change severity of Bug 903800 to the same value.
Ignoring request to change severity of Bug 903821 to the same value.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903767
903800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903800
903821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 903767 903800

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 903767 903800
Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 
4.8
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / 
kernel panic at boot
Severity set to 'serious' from 'critical'
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Merged 903767 903800 903821
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903767
903800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903800
903821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug #903328 in cobertura marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #903328 [src:cobertura] cobertura: FTBFS in buster/sid (dh_installdocs: 
Cannot find "README")
Added tag(s) pending.

-- 
903328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903328: Bug #903328 in cobertura marked as pending

[tony mancill]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/cobertura/commit/5b4ef953e7230a4573593824d6acf893ca9ae970


Correct name of README file (Closes: #903328)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/903328

Bug#903183: marked as done (mygpoclient: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 16:49:13 +
with message-id 
and subject line Bug#903183: fixed in mygpoclient 1.8-2
has caused the Debian Bug report #903183,
regarding mygpoclient: FTBFS in buster/sid (dh_installdocs: Cannot find 
"README")
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
903183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mygpoclient
Version: 1.8-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
pybuild --configure -i python{version} -p 2.7
D: pybuild pybuild:540: version: 3.20180326
D: pybuild pybuild:541: ['/usr/bin/pybuild', '--configure', '-i', 
'python{version}', '-p', '2.7']
D: pybuild pybuild:36: cfg: Namespace(after_build=None, after_clean=None, 
after_configure=None, after_install=None, after_test=None, before_build=None, 
before_clean=None, before_configure=None, before_install=None, 
before_test=None, build_args=None, build_only=False, clean_args=None, 
clean_only=False, configure_args=None, configure_only=True, custom_tests=False, 
destdir='debian/tmp', detect_only=False, dir='/<>', disable=None, 
ext_destdir=None, ext_pattern='\\.so(\\.[^/]*)?$', ext_sub_pattern=None, 
ext_sub_repl=None, install_args=None, install_dir=None, install_only=False, 
interpreter=['python{version}'], list_systems=False, name='mygpoclient', 
print_args=None, quiet=False, really_quiet=False, system=None, test_args=None, 
test_nose=False, test_only=False, test_pytest=False, test_tox=False, 
verbose=True, versions=['2.7'])
D: pybuild tools:230: invoking: /usr/bin/dpkg-architecture
D: pybuild pybuild:129: detected build system: distutils (certainty: 50%)
D: pybuild plugin_distutils:56: pydistutils config file:
[clean]

[... snipped ...]

byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/json_test.py
 to json_test.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/json.py
 to json.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/feeds.py
 to feeds.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/api.py
 to api.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/public.py
 to public.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/public_test.py
 to public_test.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/simple.py
 to simple.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/api_test.py
 to api_test.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/http_test.py
 to http_test.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/simple_test.py
 to simple_test.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/testing.py
 to testing.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/http.py
 to http.cpython-36.pyc
byte-compiling 
/<>/debian/python3-mygpoclient/usr/lib/python3.6/dist-packages/mygpoclient/__init__.py
 to __init__.cpython-36.pyc
running install_scripts
creating /<>/debian/python3-mygpoclient/usr/bin
copying build/scripts-3.6/mygpo-list-devices -> 
/<>/debian/python3-mygpoclient/usr/bin
copying build/scripts-3.6/mygpo-bpsync -> 
/<>/debian/python3-mygpoclient/usr/bin
copying build/scripts-3.6/mygpo-simple-client -> 
/<>/debian/python3-mygpoclient/usr/bin
changing mode of 
/<>/debian/python3-mygpoclient/usr/bin/mygpo-list-devices to 775
changing mode of 
/<>/debian/python3-mygpoclient/usr/bin/mygpo-bpsync to 775
changing mode of 
/<>/debian/python3-mygpoclient/usr/bin/mygpo-simple-client to 775
running install_data
creating /<>/debian/python3-mygpoclient/usr/share
creating /<>/debian/python3-mygpoclient/usr/share/man
creating 

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Gianluigi Tiesi]

Source: linux
Version: 4.9.110-1
Followup-For: Bug #903800

I have same problems but on dum0, server reboots forever, by adding
no reboot the screen goes black just after the hypervisor loads (instead of
reboot)

This happens on i7-2600 and i7-4770

4.9.0-6 worked fine

I've also upgraded bios but same results



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

Kernel: Linux 4.9.0-7-amd64 (SMP w/8 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: sysvinit (via /sbin/init)

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Samuel Thibault]

Control: reassign -1 dh-python
Control: affect -1 sphinxbase

AFAIU the issue is in dh_python3 then, thus reassigning for now.

Samuel Thibault, le sam. 14 juil. 2018 22:52:16 +0200, a ecrit:
> Paul Gevers, le ven. 13 juil. 2018 13:46:45 +0200, a ecrit:
> > I think this is caused by the fact that we loop over $pyver in the
> > d/rules file, but apparently that is broken for multiple python3 versions.
> 
> I don't think that's the problem: I tried to pause after the
> dh_install step, and we have this:
> 
> € find debian | grep pyt
> debian/tmp/usr/lib/python2.7
> debian/tmp/usr/lib/python2.7/dist-packages
> debian/tmp/usr/lib/python2.7/dist-packages/sphinxbase
> debian/tmp/usr/lib/python2.7/dist-packages/sphinxbase/sphinxbase.py
> debian/tmp/usr/lib/python2.7/dist-packages/sphinxbase/__init__.py
> debian/tmp/usr/lib/python2.7/dist-packages/sphinxbase/_sphinxbase.so.0.0.0
> debian/tmp/usr/lib/python2.7/dist-packages/sphinxbase/sphinxbase.pyc
> debian/tmp/usr/lib/python2.7/dist-packages/sphinxbase/sphinxbase.pyo
> debian/tmp/usr/lib/python2.7/dist-packages/sphinxbase/__init__.pyc
> debian/tmp/usr/lib/python2.7/dist-packages/sphinxbase/_sphinxbase.so.0
> debian/tmp/usr/lib/python2.7/dist-packages/sphinxbase/_sphinxbase.so
> debian/tmp/usr/lib/python2.7/dist-packages/sphinxbase/__init__.pyo
> debian/tmp/usr/lib/python3.6
> debian/tmp/usr/lib/python3.6/site-packages
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase/sphinxbase.py
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase/__init__.py
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase/_sphinxbase.so.0.0.0
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase/_sphinxbase.so.0
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase/_sphinxbase.so
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase/__pycache__
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase/__pycache__/sphinxbase.cpython-36.pyc
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase/__pycache__/__init__.cpython-36.opt-1.pyc
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase/__pycache__/sphinxbase.cpython-36.opt-1.pyc
> debian/tmp/usr/lib/python3.6/site-packages/sphinxbase/__pycache__/__init__.cpython-36.pyc
> debian/tmp/usr/lib/python3.7
> debian/tmp/usr/lib/python3.7/site-packages
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase/sphinxbase.py
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase/__init__.py
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase/_sphinxbase.so.0.0.0
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase/_sphinxbase.so.0
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase/_sphinxbase.so
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase/__pycache__
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase/__pycache__/sphinxbase.cpython-37.opt-1.pyc
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase/__pycache__/__init__.cpython-37.opt-1.pyc
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase/__pycache__/__init__.cpython-37.pyc
> debian/tmp/usr/lib/python3.7/site-packages/sphinxbase/__pycache__/sphinxbase.cpython-37.pyc
> debian/python3-sphinxbase.debhelper.log
> debian/python3-sphinxbase.install
> debian/python-sphinxbase
> debian/python-sphinxbase/usr
> debian/python-sphinxbase/usr/lib
> debian/python-sphinxbase/usr/lib/python2.7
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages/sphinxbase
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages/sphinxbase/sphinxbase.py
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages/sphinxbase/__init__.py
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages/sphinxbase/_sphinxbase.so.0.0.0
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages/sphinxbase/sphinxbase.pyc
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages/sphinxbase/sphinxbase.pyo
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages/sphinxbase/__init__.pyc
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages/sphinxbase/_sphinxbase.so.0
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages/sphinxbase/_sphinxbase.so
> debian/python-sphinxbase/usr/lib/python2.7/dist-packages/sphinxbase/__init__.pyo
> debian/python3-sphinxbase
> debian/python3-sphinxbase/usr
> debian/python3-sphinxbase/usr/lib
> debian/python3-sphinxbase/usr/lib/python3.6
> debian/python3-sphinxbase/usr/lib/python3.6/site-packages
> debian/python3-sphinxbase/usr/lib/python3.6/site-packages/sphinxbase
> debian/python3-sphinxbase/usr/lib/python3.6/site-packages/sphinxbase/sphinxbase.py
> debian/python3-sphinxbase/usr/lib/python3.6/site-packages/sphinxbase/__init__.py
> debian/python3-sphinxbase/usr/lib/python3.6/site-packages/sphinxbase/_sphinxbase.so.0.0.0
> debian/python3-sphinxbase/usr/lib/python3.6/site-packages/sphinxbase/_sphinxbase.so.0
> 

Processed: Re: Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dh-python
Bug #903698 [src:sphinxbase] sphinxbase: build appears broken for multiple 
python3 versions
Bug reassigned from package 'src:sphinxbase' to 'dh-python'.
No longer marked as found in versions sphinxbase/0.8+5prealpha+1-2.
Ignoring request to alter fixed versions of bug #903698 to the same values 
previously set
> affect -1 sphinxbase
Bug #903698 [dh-python] sphinxbase: build appears broken for multiple python3 
versions
Added indication that 903698 affects sphinxbase

-- 
903698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903829: myspell-bg: Package not installable; upgrades from 4.1-4 impossible

[Yavor Doganov]

Package: myspell-bg
Version: 4.1-5
Severity: serious

This change (commit 311c4d9)

   * make myspell-bg a transitional package depending on hunspell-bg
 (Closes: #898709)

does not work as intended, because hunspell-bg conflicts with
myspell-bg.  It also prevents migration to testing:

$ grep-excuses bgoffice
bgoffice (4.1-4 to 4.1-6)
Maintainer: Damyan Ivanov
31 days old (needed 5 days)
Rejected due to piuparts regression -
https://piuparts.debian.org/sid/source/b/bgoffice.html

I'm not sure what is the best course of action (perhaps reassign to
hunspell-bg with request to remove the Conflicts relationship or replace
it with versioned Breaks, downgrading severity).

Bug#903767: verbose kernel log

[Jaap Eldering]

I'm seeing the same problem with linux-image-4.9.0-7-amd64:4.9.110-1 from the 
9.5 point release running on Xen/pvgrub.

In case it's useful, here's the verbose kernel log:

[2.028120] registered taskstats version 1
[2.028149] zswap: loaded using pool lzo/zbud
[2.030226] ima: No TPM chip found, activating TPM-bypass!
[2.030238] ima: Allocated hash algorithm: sha256
[2.030281] xenbus_probe_frontend: Device with no driver: device/vbd/51712
[2.030286] xenbus_probe_frontend: Device with no driver: device/vbd/51728
[2.030291] xenbus_probe_frontend: Device with no driver: device/vif/0
[2.030297] xenbus_probe_frontend: Device with no driver: device/vif/1
[2.030317] hctosys: unable to open rtc device (rtc0)
[2.031657] Freeing unused kernel memory: 1420K
[2.031668] Write protecting the kernel read-only data: 12288k
[2.038529] Freeing unused kernel memory: 1928K
[2.039863] Freeing unused kernel memory: 1228K
[2.050421] x86/mm: Checked W+X mappings: FAILED, 6123 W+X pages found.
[2.050922] general protection fault:  [#1] SMP
[2.050932] Modules linked in:
[2.050941] CPU: 1 PID: 1 Comm: init Not tainted 4.9.0-7-amd64 #1 Debian 
4.9.110-1
[2.050949] task: 88003e367040 task.stack: c9004018c000
[2.050954] RIP: e030:[]  [] 
ret_from_fork+0x2d/0x70
[2.050967] RSP: e02b:c9004018ff50  EFLAGS: 00010006
[2.050972] RAX: 000a7338d000 RBX: 816076d0 RCX: eaf4ac9f
[2.050978] RDX: 0003 RSI: 0002 RDI: c9004018ff58
[2.050984] RBP:  R08:  R09: 880039b18000
[2.050991] R10: 8080808080808080 R11: fefefefefefefeff R12: 
[2.050997] R13:  R14: 00116359 R15: 53dc
[2.051006] FS:  () GS:88003f88() 
knlGS:
[2.051013] CS:  e033 DS:  ES:  CR0: 80050033
[2.051019] CR2: 7ffea17fded0 CR3: 39b8c000 CR4: 00042660
[2.051024] Stack:
[2.051029]     

[2.051041]     

[2.051050]     

[2.051060] Call Trace:
[2.051066] Code: c7 e8 b8 fe a8 ff 48 85 db 75 2f 48 89 e7 e8 5b ed 9e ff 
50 90 0f 20 d8 65 48 0b 04 25 e0 02 01 00 78 08 65 88 04 25 e7 02 01 00 <0f> 22 
d8 58 66 0f 1f 44 00 00 e9 c1 07 00 00 4c 89 e7 eb 11 e8 
[2.051125] RIP  [] ret_from_fork+0x2d/0x70
[2.051132]  RSP 
[2.051140] ---[ end trace d3783fae70c9b202 ]---
[2.051262] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
[2.051262] 
[2.051280] Kernel Offset: disabled

Bug#902897: marked as done (virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED))

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 13:04:43 +
with message-id 
and subject line Bug#902897: fixed in virtualbox 5.2.14-dfsg-5
has caused the Debian Bug report #902897,
regarding virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
902897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox
Version: 5.2.14-dfsg-1
Severity: important

After upgrading from 5.2.12 to the latest version in debian unstable,
virtualbox fails to start my windows vm with the error message:

Failed to open a session for the virtual machine Win7.

Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed 
(VERR_LDRELF_RELOCATION_NOT_SUPPORTED).

Failed to load VMMR0.r0 (VERR_LDRELF_RELOCATION_NOT_SUPPORTED).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


Let me know if you have any further questions.

Best regards,
Matthias Liertzer



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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 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)
LSM: AppArmor: enabled

Versions of packages virtualbox depends on:
ii  adduser   3.117
ii  iproute2  4.16.0-4
ii  libc6 2.27-3
ii  libcurl3-gnutls   7.60.0-2
ii  libdevmapper1.02.12:1.02.145-4.1
ii  libgcc1   1:8.1.0-9
ii  libgsoap-2.8.60   2.8.60-2
ii  libopus0  1.3~beta+20180518-1
ii  libpng16-16   1.6.34-1
ii  libpython3.6  3.6.6-1
ii  libsdl1.2debian   1.2.15+dfsg2-1
ii  libssl1.1 1.1.0h-4
ii  libstdc++68.1.0-9
ii  libvncserver1 0.9.11+dfsg-1.1
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.5-1
ii  libxcursor1   1:1.1.15-1
ii  libxext6  2:1.3.3-1+b2
ii  libxml2   2.9.4+dfsg1-7+b1
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.15-2
ii  python3   3.6.6-1
ii  python3.6 3.6.6-1
ii  virtualbox-dkms [virtualbox-modules]  5.2.14-dfsg-1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages virtualbox recommends:
ii  libgl1  1.0.0+git20180308-3
ii  libqt5core5a5.10.1+dfsg-7
ii  libqt5opengl5   5.10.1+dfsg-7
ii  libqt5widgets5  5.10.1+dfsg-7
ii  virtualbox-qt   5.2.14-dfsg-1

Versions of packages virtualbox suggests:
pn  vde2
ii  virtualbox-guest-additions-iso  5.2.14-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: virtualbox
Source-Version: 5.2.14-dfsg-5

We believe that the bug you reported is fixed in the latest version of
virtualbox, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
virtualbox package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Jul 2018 14:54:31 +0200
Source: virtualbox
Binary: virtualbox-qt virtualbox virtualbox-dkms virtualbox-source 
virtualbox-guest-dkms virtualbox-guest-source virtualbox-guest-x11 
virtualbox-guest-utils
Architecture: source
Version: 5.2.14-dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Virtualbox Team  

Bug#903028: closing 903028

[Philipp Huebner]

close 903028 0.2018.07.13~dfsg0-1
thanks

The problem has been solved upstream and a fixed versions is now in unstable.

Processed: closing 903028

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 903028 0.2018.07.13~dfsg0-1
Bug #903028 [src:ejabberd-contrib] ejabberd-contrib: FTBFS with ejabberd >= 
18.06
The source 'ejabberd-contrib' and version '0.2018.07.13~dfsg0-1' do not appear 
to match any binary packages
Marked as fixed in versions ejabberd-contrib/0.2018.07.13~dfsg0-1.
Bug #903028 [src:ejabberd-contrib] ejabberd-contrib: FTBFS with ejabberd >= 
18.06
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: python3-pycuda: fails to install with python 3.7 as a supported python version

[Debian Bug Tracking System]

Processing control commands:

> block 902788 with -1
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 903528 903527 903457 902794 902989 903388 903522 902757 
903030 903031 902761 903784 902715 903526 903145 903529 903525 903218 902766 
903558 903423 902900 902646 902650 902631 903016
902788 was blocking: 902582 903432
Added blocking bug(s) of 902788: 903826

-- 
902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788
903826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903818: marked as done (screen: should not try to link with -lelf)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 12:34:19 +
with message-id 
and subject line Bug#903818: fixed in screen 4.6.2-3
has caused the Debian Bug report #903818,
regarding screen: should not try to link with -lelf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
903818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: screen
Version: 4.6.2-2
Severity: normal
Tags: fixed-upstream

The latest upload has dropped libelf-dev from Build-Conflicts which is a
welcome change.  However, there is the problem that screen automagically
links with -lelf if it is available, and screen-udeb then gains an
unfulfillable dependency on libelf1:

,
| $ dpkg-deb -f screen-udeb_4.6.2-2_i386.udeb Depends 
| libc6-udeb (>= 2.27), libelf1 (>= 0.132), libtinfo6-udeb (>= 6.1)
`

Upstream has stopped linking with libelf in commit d641761d83[1], I
suggest doing the same in the Debian package.  According to
dpkg-shlibdeps, screen does not use any symbols from libelf.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64
--- End Message ---
--- Begin Message ---
Source: screen
Source-Version: 4.6.2-3

We believe that the bug you reported is fixed in the latest version of
screen, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated screen package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 15 Jul 2018 14:11:39 +0200
Source: screen
Binary: screen screen-udeb
Architecture: source amd64
Version: 4.6.2-3
Distribution: unstable
Urgency: medium
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Description:
 screen - terminal multiplexer with VT100/ANSI terminal emulation
 screen-udeb - terminal multiplexer with VT100/ANSI terminal emulation - udeb 
(udeb)
Closes: 903818
Changes:
 screen (4.6.2-3) unstable; urgency=medium
 .
   * Cherry-pick upstream commit d340b02c to stop linking against libelf if
 available.  This upstream commit is from 2014, but accidentally has
 been reverted upstream in 2015 while configure.in was renamed to
 configure.ac.  (Closes: #903818)
Checksums-Sha1:
 8a614e923cbe23f53b9badacfb933063312bc676 2312 screen_4.6.2-3.dsc
 4f1824666cc2689bef7a454d75c9f445fba919ca 47028 screen_4.6.2-3.debian.tar.xz
 c39464ee52ebff6af90ff8ad7b93b12eb16142ca 443636 screen-dbgsym_4.6.2-3_amd64.deb
 a335e0294a77c14ef1af6790a41efbaf8b962de4 385036 screen-udeb_4.6.2-3_amd64.udeb
 bb0af43e974a1903d3d32ec427062875c80911a5 6472 screen_4.6.2-3_amd64.buildinfo
 75a0194f370392c7c5cbf0a2eb0a05235d3acdd2 603104 screen_4.6.2-3_amd64.deb
Checksums-Sha256:
 71c846d34ad585825ae5301ec52bdf7ef0670a07ff6c8a2c542c6ec93050d274 2312 
screen_4.6.2-3.dsc
 a89527557018c881267f91097799214fa6dc6cdc60c723df1131a55f55267f90 47028 
screen_4.6.2-3.debian.tar.xz
 dbb7420d1cdd5ad2e1f364c33bfb40c42af2bf5bf59d8adb18d1617dc245e4fc 443636 
screen-dbgsym_4.6.2-3_amd64.deb
 454a10d5abbc29af35bb7541ff76be10e0ecd500a86a3cce4c27ad288015097b 385036 
screen-udeb_4.6.2-3_amd64.udeb
 11a14b936e4b91dea20e9407b08205d8288e96b14f11615aed76c09a5dbf035b 6472 
screen_4.6.2-3_amd64.buildinfo
 27297c72f0db65717587dc34ce9719471ad7397ab123f675c13ea959f57b70dd 603104 
screen_4.6.2-3_amd64.deb
Files:
 6aece8f74edc33d2fdb4c3bd6195f8af 2312 misc standard screen_4.6.2-3.dsc
 4cb0e1e05cb9e95b7ea60789e4b4d1d8 47028 misc standard 
screen_4.6.2-3.debian.tar.xz
 10659031c47fe6d7c5800a9378b66217 443636 debug optional 
screen-dbgsym_4.6.2-3_amd64.deb
 b724ff1bd480bbf210a1f7b28129f893 385036 debian-installer standard 
screen-udeb_4.6.2-3_amd64.udeb
 af29407e5cbe41bf8f5ba3386ee64a10 6472 misc standard 
screen_4.6.2-3_amd64.buildinfo
 00f9ee4b052e1b712c951ec95edf65a6 603104 misc standard screen_4.6.2-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAltLOq4ACgkQa+Zjx1o1
yXUkTBAAw0X2DF9gEHQyrZZau/XxVadCCmz52WZ0NVc5hiRoEBdT3xEmT6PXLeMK

Processed: reassign 903821 to src:linux, forcibly merging 903767 903821, severity of 903821 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 903821 src:linux 4.9.110-1
Bug #903821 [xen-hypervisor-4.8-amd64] xen-hypervisor-4.8-amd64: Kernel Panic 
after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)
Bug reassigned from package 'xen-hypervisor-4.8-amd64' to 'src:linux'.
No longer marked as found in versions 
xen/4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9.
Ignoring request to alter fixed versions of bug #903821 to the same values 
previously set
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Marked as found in versions linux/4.9.110-1.
> forcemerge 903767 903821
Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 
4.8
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Severity set to 'normal' from 'critical'
Merged 903767 903821
> # regression
> severity 903821 serious
Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading 
to stretch 9.5 (linux-image-4.9.0-7-amd64)
Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 
4.8
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903767
903821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903826: python3-pycuda: fails to install with python 3.7 as a supported python version

[Andreas Beckmann]

Package: python3-pycuda
Version: 2017.1.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package python3-pycuda.
  (Reading database ... 
(Reading database ... 13293 files and directories currently installed.)
  Preparing to unpack .../python3-pycuda_2017.1.1-2_amd64.deb ...
  Unpacking python3-pycuda (2017.1.1-2) ...
  Setting up python3-pycuda (2017.1.1-2) ...
File "/usr/lib/python3/dist-packages/pycuda/gpuarray.py", line 230
  def set(self, ary, async=False, stream=None):
 ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-pycuda (--configure):
   installed python3-pycuda package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-pycuda


async has become a reserved keyword in 3.7


cheers,

Andreas


python3-pycuda_2017.1.1-2.log.gz
Description: application/gzip

Bug#903818: screen: should not try to link with -lelf

[Sven Joachim]

On 2018-07-15 14:04 +0200, Axel Beckert wrote:

> Control: tag -1 + confirmed pending
>
> Hi Sven,
>
> I just noticed the following:
>
> Sven Joachim wrote:
>> ,
>> | $ dpkg-deb -f screen-udeb_4.6.2-2_i386.udeb Depends 
>> | libc6-udeb (>= 2.27), libelf1 (>= 0.132), libtinfo6-udeb (>= 6.1)
>> `
>
> So this seems to stem from being build in a not so clean chroot,
> because my pbuilder-built upload on amd64 doesn't show that
> dependency.

Surely, it only happens if libelf-dev is present on the build system
which is usually not the case for official builds.  That's why I
reported it at normal severity and KiBi has not yelled at you yet. ;-)

> But I was able to reproduce the issue by rebuilding 4.6.2-2 locally
> after installing libelf-dev. And hence I can confirm that applying
> that commit against configure.ac fixes the issue.
>
> Will upload 4.6.2-3 with the fix soon.

Thanks.

Cheers,
   Sven

Bug#903825: xserver-xorg-video-sunffb: sparc64 architecture is disabled

[Gregor Riepl]

Package: xserver-xorg-video-sunffb
Version: 1:1.2.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Debian has dropped support for the sparc (32-bit) architecture some time ago,
but a dedicated debian-ports team has started working on a sparc64 port.

Since this port is already very mature, it would make sense to bring back
some old packages that were only supported on sparc.
The Xorg sunffb driver is one of them.

Please add the "sparc64" to the list of build Architectures: in d/control, so
this package returns to the repositories.

I have verified that building on sparc64 works, but I haven't tested the
resulting driver yet.

Thank you!

-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable'), (50, 'experimental')
Architecture: sparc64

Kernel: Linux 4.16.0-2-sparc64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#867886: marked as done (python-neovim: build sometimes hangs with python 3.6 as supported version)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 13:53:30 +0200
with message-id <9e9688bd-6339-d24a-b337-e5c6e9b3e...@viccuad.me>
and subject line 
has caused the Debian Bug report #867886,
regarding python-neovim: build sometimes hangs with python 3.6 as supported 
version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
867886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-neovim
Version: 0.1.13-2
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/python-neovim-0.1.13'
NVIM_CHILD_ARGV='["nvim", "-u", "NONE", "--embed"]' dh_auto_test
I: pybuild base:184: cd 
/build/1st/python-neovim-0.1.13/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose 
test
...
--
Ran 51 tests in 4.927s

OK
I: pybuild base:184: cd 
/build/1st/python-neovim-0.1.13/.pybuild/pythonX.Y_3.6/build; python3.6 -m nose 
test
Sun Jul  9 17:06:17 UTC 2017 - pbuilder was killed by timeout 
after 18h.
Sun Jul  9 17:06:19 UTC 2017  I: 
https://tests.reproducible-builds.org/debian/unstable/i386/python-neovim : 
reproducible ➤ FTBFS
Sun Jul  9 17:06:24 UTC 2017 - total duration: 18h 0m 18s.
--- End Message ---
--- Begin Message ---
Closing bug, see reason in previous message.

Sorry for the noise.


-- 
Víctor Cuadrado Juan   m...@viccuad.me

PGP key ID: 4096R: 0xA2591E231E251F36
Key fingerprint: E3C5 114C 0C5B 4C49 BA03  0991 A259 1E23 1E25 1F36
My signed E-Mails are trustworthy.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#902897: virtualbox broken by binutils master (new R_X86_64_PLT32 relocation type)

[Jörg Krywkow]

Dear Gianfranco,

thank you very much for your fix indeed. It works like a charm on my
siduction box.
You really saved my a... .
Best wishes
jk



On Thu, 12 Jul 2018 08:52:59 + (UTC) Gianfranco Costamagna
 wrote:
> Hello,
>
>
> >VMMR0.r0 has been built (presumably due to the recent binutils
upgrades in unstable) with the new PLT32 relocation type, which the
virtualbox ELF relocation >code cannot handle at the moment. Having a
quick glance at .text and .rela.text of VMMR0.r0, it seems to me that
PC32 and PLT32 can be handled identically, >similar to what commit
b21ebf2fb4cd of the Linux kernel did?
>
>
> I really liked the analysis, the linux commit and the binutils stuff,
I crafted a patch based on this comment, and uploaded in unstable
>
> If anybody wants to test the "fix", please grab the deb files from there
>
http://debomatic-amd64.debian.net/distribution#unstable/virtualbox/5.2.14-dfsg-2/buildlog
>
>
> or wait some hours for the package to appear on unstable
repositories/mirrors.
>
> I'm not sure if this causes regressions or whatever else, the
assumption "they might behave in the same way" might not apply as it did
in the kernel,
> even if my basic tests confirmed the VM to start.
>
> Use at your own risk, like everything that comes from unstable, the
urgency is set to low, so I presume we will have 10 days of people
testing this before
> going in buster.
>
> thanks you all, I also submitted the patch to upstream mail list and
irc for review
>
> G.
>
>

Processed: Re: Bug#903818: screen: should not try to link with -lelf

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed pending
Bug #903818 [src:screen] screen: should not try to link with -lelf
Added tag(s) pending and confirmed.

-- 
903818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903818: screen: should not try to link with -lelf

[Axel Beckert]

Control: tag -1 + confirmed pending

Hi Sven,

I just noticed the following:

Sven Joachim wrote:
> ,
> | $ dpkg-deb -f screen-udeb_4.6.2-2_i386.udeb Depends 
> | libc6-udeb (>= 2.27), libelf1 (>= 0.132), libtinfo6-udeb (>= 6.1)
> `

So this seems to stem from being build in a not so clean chroot,
because my pbuilder-built upload on amd64 doesn't show that
dependency.

But I was able to reproduce the issue by rebuilding 4.6.2-2 locally
after installing libelf-dev. And hence I can confirm that applying
that commit against configure.ac fixes the issue.

Will upload 4.6.2-3 with the fix soon.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#867886: (no subject)

[Víctor Cuadrado Juan]

closes 867886
thanks

Just uploaded a new version, with upstream 0.2.6. With the move to pytest and
the redoing of tests, I have not seen this behavior again.

Closing this bug so the package migrates; I will keep looking at
  https://tests.reproducible-builds.org/debian/history/python-neovim.html
for regressions.


Kind regards,


-- 
Víctor Cuadrado Juan   m...@viccuad.me

PGP key ID: 4096R: 0xA2591E231E251F36
Key fingerprint: E3C5 114C 0C5B 4C49 BA03  0991 A259 1E23 1E25 1F36
My signed E-Mails are trustworthy.



signature.asc
Description: OpenPGP digital signature

Processed: bug 903818 is forwarded to https://lists.gnu.org/archive/html/screen-devel/2018-07/msg00003.html

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 903818 
> https://lists.gnu.org/archive/html/screen-devel/2018-07/msg3.html
Bug #903818 [src:screen] screen: should not try to link with -lelf
Set Bug forwarded-to-address to 
'https://lists.gnu.org/archive/html/screen-devel/2018-07/msg3.html'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 903818

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Has been accidentially reverted again at upstream
> tags 903818 - fixed-upstream
Bug #903818 [src:screen] screen: should not try to link with -lelf
Removed tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Luis Miguel Parra]

Hi,

I am having the same issue.
After upgrade to 4.9.0-7-amd64 from 4.9.0-6-amd64 my xen vm they stop
working.

I run xenserver 6.2 and as a temporal fix I just convert the VM to HVM from
PV

xe vm-param-set uuid=YOURVMUID HVM-boot-policy="BIOS order" PV-bootloader=""


So looks like running in Hardware-assisted Virtualization (HVM) helps

Processed: Re: Bug#903818: screen: should not try to link with -lelf

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #903818 [src:screen] screen: should not try to link with -lelf
Severity set to 'serious' from 'normal'
> tag -1 + upstream
Bug #903818 [src:screen] screen: should not try to link with -lelf
Added tag(s) upstream.

-- 
903818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903821: Re : xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)

[Benoît Tonnerre]

Hi,

If you prefer, you can find a kernel panic screenshot from R720 Dell
server's :

https://s33.postimg.cc/b2t056y8f/S_lection_027.png

Best regards

Benoît

Bug#903821: xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64)

[Benoît Tonnerre]

Package: xen-hypervisor-4.8-amd64
Version: 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

After updating 3 Xen servers from stretch (9.4) to stretch (9.5), I notice
a kernel panic on these 3 servers.

If I boot xen hypervisor with advanced option in grub menu, and If i select
linux-image-4.9.0-6-amd64 kernel, everything work.

The 3 servers are from Dell :

- 1 PowerEdge R720
- 2 PowerEdge R430

You can find the message displayed on IDRAC console when booting with
4.9.0-7-amd64 :

Call Trace:
Code: c7 e8 b8 fe a8 ff 48 85 db 75 2f 48 89 e7 e8 5b ed 9e ff 50 90 0f 20
d8 65 48 0b 04 25 e0 02 01 00 78 08 65 88 04 25 e7 02 01 00 <0f> 22 d8 58
66 90 66 66 90 e9 c1 07 00 00 4c 89 e7 eb 11 e8
RIP [] ret_form_fork+0x2d/0x70
 RSP 
 ---[ end trace 28169cf87e381c4e ]---
 Kernel panci - not syncing: Attempted to kill init! exicode=0x000b
 Kernel Offset: disabled

 After this, the servers reboot in loop.

 If you need any others informations, please let me know.

 Best regards.

 Benoît


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

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

xen-hypervisor-4.8-amd64 depends on no packages.

Versions of packages xen-hypervisor-4.8-amd64 recommends:
ii  xen-utils-4.8  4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9

xen-hypervisor-4.8-amd64 suggests no packages.

-- Configuration Files:
/etc/default/grub.d/xen.cfg changed:
XEN_OVERRIDE_GRUB_DEFAULT=1
echo "Including Xen overrides from /etc/default/grub.d/xen.cfg"
GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=2G,max:2G dom0_max_vcpus=2
dom0_vcpus_pin"
if [ "$XEN_OVERRIDE_GRUB_DEFAULT" = "" ]; then
echo "WARNING: GRUB_DEFAULT changed to boot into Xen by default!"
echo " Edit /etc/default/grub.d/xen.cfg to avoid this warning."
XEN_OVERRIDE_GRUB_DEFAULT=1
fi
if [ "$XEN_OVERRIDE_GRUB_DEFAULT" = "1" ]; then
GRUB_DEFAULT="Debian GNU/Linux, with Xen hypervisor"
fi


-- no debconf information

Bug#903631: openjdk-11: FTBFS on several architectures: dh_install: Cannot find (any matches for) "usr/lib/jvm/java-11-openjdk-armel/bin/jhsdb"

[Emilio Pozuelo Monfort]

Hi Matthias,

On 12/07/18 10:52, Emilio Pozuelo Monfort wrote:
> openjdk-11 11~21 failed to build on several architectures due to missing
> jhsdb. Either that should be enabled on them (if possible) or not
> installed.

This is still not fixed for armel,mips64el,mipsel.

Cheers,
Emilio

Bug#903070: marked as done (haproxyctl FTBFS: update Build-Depends: ruby-ronn -> ronn)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 08:48:52 +
with message-id 
and subject line Bug#903070: fixed in haproxyctl 1.3.0-3
has caused the Debian Bug report #903070,
regarding haproxyctl FTBFS: update Build-Depends: ruby-ronn -> ronn
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
903070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haproxyctl
Version: 1.3.0-2
Severity: serious

Since ronn got split out of ruby-ronn, haproxyctl fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with ronn as haproxyctl uses the
command line tool.

Helmut
--- End Message ---
--- Begin Message ---
Source: haproxyctl
Source-Version: 1.3.0-3

We believe that the bug you reported is fixed in the latest version of
haproxyctl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated haproxyctl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jul 2018 09:32:18 +0200
Source: haproxyctl
Binary: haproxyctl
Architecture: source
Version: 1.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Sebastien Badia 
Description:
 haproxyctl - Utility to manage HAProxy
Closes: 903070
Changes:
 haproxyctl (1.3.0-3) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Cédric Boutillier ]
   * Run wrap-and-sort on packaging files
 .
   [ Sebastien Badia ]
   * d/control:
 + Update ronn B-D (Closes: #903070)
 + Bump Standards-Version to 4.1.5 (no changes needed)
 + Use salsa.debian.org in Vcs-* fields
 + Bump compat version to 11
   * d/watch: Migrate to gemwatch.d.n (alioth is gone)
   * d/copyright: Use HTTPS for URI
   * d/upstream: Added Upstream metadata
Checksums-Sha1:
 ccd311895379636b2be443adddb22027686d37ad 2003 haproxyctl_1.3.0-3.dsc
 346defaea473b635d8923c9b71f8c28e85ac0d0c 2896 haproxyctl_1.3.0-3.debian.tar.xz
 0212b91e9616425118f38a80a565bcb546f234ab 7094 
haproxyctl_1.3.0-3_source.buildinfo
Checksums-Sha256:
 2f87544251ba703e9057a91fff8c8d0a3dfbb613d6a3d5e5c31c35b7ac810981 2003 
haproxyctl_1.3.0-3.dsc
 f351c82c18200de2fa9fa7faa25590eddf543141424c168acac6df7c3a32036c 2896 
haproxyctl_1.3.0-3.debian.tar.xz
 19cff25320228bb4125a6b6029c2180a1c16138899f832714bad6d8a400b13cb 7094 
haproxyctl_1.3.0-3_source.buildinfo
Files:
 a338935ec8ce0e244c520380937b 2003 admin optional haproxyctl_1.3.0-3.dsc
 d41447818dd35a9b7cc1dfd0081d968e 2896 admin optional 
haproxyctl_1.3.0-3.debian.tar.xz
 330824deaa9f919a275881212be6fabf 7094 admin optional 
haproxyctl_1.3.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfkPprL9yerPPCIUzhxbORhSkUtgFAltK+XwACgkQhxbORhSk
UtgtWg//av2y8ZM+pGI38rIhpkbYX/7+dONNDxxN716Rf4vs2AebAo2tzaqI9zFv
wTIzFv7A5Yohqba9mRphuA9IqXy2Mwx1A109tU3lPiLqZHJgnyJrqZ059R0HmzEc
H91l8MqQUSM7u3VPvdWIwL9z9eNbJls2kOQqxXQPVYXqAVCFD01esrLJKjmVpv54
/Dr1HCeuL83ZnmO+Y3LF1j8psmRnir/8FTPgx2UmNel90+8aOYAnLhS3koI5YvEk
yFyDb24c4/qKvto3vhlKQSTg2pZNXLvSK/6FgBuXi7Y5QfnO+GwtxnG+q3xMOG4T
tWDgpAe1MDSDIoXS9yJyQkk89XtdfOEFMWD51b/nYGlzR6m+McZsHVUBhlvy0GUU
SOEYOTat87FrjYoNhJg/wPA4zUZ1x+20P0qY0feydD7voNweJBziEu89pjBO2IHf
rRYNiwwLtwWnJS205jK4x9NL1V8LkJZ9AHwgim3HSV8eDREmB0xFxR80f1VJPUMN
ay0dkbZLeqi1/mrjOiYO3amzAWzdxf6d7qNUySOeKAQqLd2eTMJjtCU9DUFhrkED
Q7yRJPnh/HF1nY/1QgLEjo71IlWfAq07EyIAv9OSsLegUpH/7kcw1lV+Lti+wD4V
k6EM2iZdFp8Wume1XJjtBKSVdeRWuGDh2t0ga5LlxE2c9OUrpqQ=
=zPzG
-END PGP SIGNATURE End Message ---

Bug#903070: Bug #903070 in haproxyctl marked as pending

[Sebastien Badia]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/haproxyctl/commit/1af719dc68889571305c7cafd6656481464a3e35


d/control: Update ronn B-D (Closes: #903070)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/903070

Processed: Bug #903070 in haproxyctl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #903070 [src:haproxyctl] haproxyctl FTBFS: update Build-Depends: ruby-ronn 
-> ronn
Added tag(s) pending.

-- 
903070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 728144 squid3 squid3/3.3.8-1
Bug #728144 [squid3] squid3: Pinger Segmentation fault in Debug::finishDebug on 
delete CurrentDebug; 
Bug #771778 [squid3] squid3: Pinger segfault with libc
Ignoring request to reassign bug #728144 to the same package
Ignoring request to reassign bug #771778 to the same package
Bug #728144 [squid3] squid3: Pinger Segmentation fault in Debug::finishDebug on 
delete CurrentDebug; 
Bug #771778 [squid3] squid3: Pinger segfault with libc
No longer marked as found in versions squid3/3.4.8-6 and squid3/3.4.8-6+deb8u1.
No longer marked as found in versions squid3/3.4.8-6+deb8u1 and squid3/3.4.8-6.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
728144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728144
771778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903784: marked as done (python3-pycsw: fails to install: SyntaxError)

[Debian Bug Tracking System]

Your message dated Sun, 15 Jul 2018 08:36:16 +
with message-id 
and subject line Bug#903784: fixed in pycsw 2.2.0+dfsg-4
has caused the Debian Bug report #903784,
regarding python3-pycsw: fails to install: SyntaxError
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
903784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pycsw
Version: 2.2.0+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package python3-pycsw.
  (Reading database ... 
(Reading database ... 9155 files and directories currently installed.)
  Preparing to unpack .../python3-pycsw_2.2.0+dfsg-3_all.deb ...
  Unpacking python3-pycsw (2.2.0+dfsg-3) ...
  Setting up python3-pycsw (2.2.0+dfsg-3) ...
File "/usr/lib/python3/dist-packages/pycsw/ogc/csw/csw2.py", line 1936
  if self.parent.async:
 ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/pycsw/ogc/csw/csw3.py", line 2013
  if self.parent.async:
 ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/pycsw/server.py", line 78
  self.async = False
   ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-pycsw (--configure):
   installed python3-pycsw package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   python3-pycsw


Could this be related to python 3.7?


cheers,

Andreas


python3-pycsw_2.2.0+dfsg-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pycsw
Source-Version: 2.2.0+dfsg-4

We believe that the bug you reported is fixed in the latest version of
pycsw, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated pycsw package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 15 Jul 2018 09:59:41 +0200
Source: pycsw
Binary: pycsw python-pycsw python3-pycsw pycsw-wsgi python-pycsw-wsgi pycsw-doc 
python-pycsw-doc
Architecture: source all
Version: 2.2.0+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 pycsw  - OGC compliant metadata (Catalogue Service for the Web) server
 pycsw-doc  - OGC compliant metadata (Catalogue Service for the Web) server - d
 pycsw-wsgi - WSGI Apache CSW service based on pycsw
 python-pycsw - OGC compliant metadata (Catalogue Service for the Web) server - 
P
 python-pycsw-doc - Transitional dummy package to pycsw-doc
 python-pycsw-wsgi - Transitional dummy package to pycsw-wsgi
 python3-pycsw - OGC compliant metadata (Catalogue Service for the Web) server 
- P
Closes: 903784
Changes:
 pycsw (2.2.0+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
   * Refresh patches.
   * Add patch to fix SyntaxError with Python 3.7 by
 renaming 'async' property to 'asynchronous'.
 (closes: #903784)
Checksums-Sha1:
 2852a7f53185df4b312507ba1238c8bcb5d3e065 2842 pycsw_2.2.0+dfsg-4.dsc
 4c662ffcf9822c5f5dc39f98672583109df489d1 17240 pycsw_2.2.0+dfsg-4.debian.tar.xz
 f9c7f075d5ae2f73d90095c22c47e199cb866927 94948 pycsw-doc_2.2.0+dfsg-4_all.deb
 2d00bee127c094c6e1fbe4fe3f654c4a09e4c8a0 124248 pycsw-wsgi_2.2.0+dfsg-4_all.deb
 24658ca1962293bcd9b5e97561b8c43b7ab2dd69 20696 pycsw_2.2.0+dfsg-4_all.deb
 0f117d6d50ef2e463473d5b62ee35ec9d85527b0 12881 
pycsw_2.2.0+dfsg-4_amd64.buildinfo
 01e39b27f710ceea6a6ba3072e7b8d3746af7df9 11984 
python-pycsw-doc_2.2.0+dfsg-4_all.deb
 88678f23d437d6e0db369787863fc0080596b563 11984 
python-pycsw-wsgi_2.2.0+dfsg-4_all.deb
 cdfbad31bf88cd69eba1d393e616ad841f90e8db 243772 
python-pycsw_2.2.0+dfsg-4_all.deb
 b4337d19e3debb6977a0ae3e11e1a0e92e695b2b 244000 

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Vincent Lefevre]

On 2018-07-15 04:27:39 +0100, Ben Hutchings wrote:
> On Sun, 2018-07-15 at 02:27 +0200, Vincent Lefevre wrote:
> > Package: src:linux
> > Version: 4.9.110-1
> > Severity: critical
> > Justification: breaks the whole system
> > 
> > After upgrade to Debian 9.5, I get a kernel panic with 4.9.0-7-amd64:
> [...]
> 
> Are you running it on Xen?

Yes.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: tagging 903784

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 903784 + pending
Bug #903784 [python3-pycsw] python3-pycsw: fails to install: SyntaxError
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903788: znc: path traversal flaw

[Salvatore Bonaccorso]

Control: retitle -1 znc: CVE-2018-14056: path traversal flaw

On Sat, Jul 14, 2018 at 10:02:58PM +0200, Salvatore Bonaccorso wrote:
> Source: znc
> Version: 0.045-1
> Severity: grave
> Tags: patch security upstream
> Justification: user security hole
> 
> Hi
> 
> See https://github.com/znc/znc/commit/a4a5aeeb17d32937d8c7d743dae9a4cc755ce773
> allowing path traversal and can lead to expose some files which
> shouldn't be, or potentially lead to a crash.

This issue has been assigned CVE-2018-14056.

Regards,
Salvatore

Processed: Re: Bug#903788: znc: path traversal flaw

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 znc: CVE-2018-14056: path traversal flaw
Bug #903788 [src:znc] znc: path traversal flaw
Changed Bug title to 'znc: CVE-2018-14056: path traversal flaw' from 'znc: path 
traversal flaw'.

-- 
903788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#903787: znc: privilege escalation to admin permission (injection of rogue values in znc.conf)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 znc: CVE-2018-14055: privilege escalation to admin permission 
> (injection of rogue values in znc.conf)
Bug #903787 [src:znc] znc: privilege escalation to admin permission (injection 
of rogue values in znc.conf)
Changed Bug title to 'znc: CVE-2018-14055: privilege escalation to admin 
permission (injection of rogue values in znc.conf)' from 'znc: privilege 
escalation to admin permission (injection of rogue values in znc.conf)'.

-- 
903787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903787: znc: privilege escalation to admin permission (injection of rogue values in znc.conf)

[Salvatore Bonaccorso]

Control: retitle -1 znc: CVE-2018-14055: privilege escalation to admin 
permission (injection of rogue values in znc.conf)

On Sat, Jul 14, 2018 at 10:01:02PM +0200, Salvatore Bonaccorso wrote:
> Source: znc
> Version: 1.6.5-1
> Severity: grave
> Tags: patch security upstream
> Justification: user security hole
> 
> Hi
> 
> See
> 
> https://github.com/znc/znc/commit/a7bfbd93812950b7444841431e8e297e62cb524e
> https://github.com/znc/znc/commit/d22fef8620cdd87490754f607e7153979731c69d
> 
> which would allow privilege escalation by a remote non-admin user.

This issue has been assigned CVE-2018-14055.

Regards,
Salvatore