Processed: fixed 912288 in 3.7.1-5

[Debian Bug Tracking System]

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

> fixed 912288 3.7.1-5
Bug #912288 {Done: Jose Gutierrez de la Concha } 
[src:zeroc-ice] zeroc-ice FTBFS with OpenJDK 11
Marked as fixed in versions zeroc-ice/3.7.1-5.
> thanks
Stopping processing here.

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

Processed: severity of 913022 is normal

[Debian Bug Tracking System]

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

> severity 913022 normal
Bug #913022 {Done: Norbert Preining } [systemd] systemd: 
restarts user jobs indefinitely without a way to stop it
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#892353: marked as done (xdvik-ja: Please use 'pkg-config' to find FreeType 2)

[Debian Bug Tracking System]

Your message dated Tue, 06 Nov 2018 07:38:36 +
with message-id 
and subject line Bug#892353: fixed in xdvik-ja 22.87.03+j1.42-2
has caused the Debian Bug report #892353,
regarding xdvik-ja: Please use 'pkg-config' to find FreeType 2
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.)


-- 
892353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdvik-ja
Severity: important

Dear Maintainer,

The next release of libfreetype6-dev will *not* ship
`freetype-config', as the script has now been deprecated in favour of
`pkg-config'.

This is an upstream change:

"Use of the `freetype-config' script to get compilation and

linking options is deprecated since it doesn't support

cross-compiling, among other deficiencies. Instead, you should

use the `pkg-config' interface." [1]

Please use `pkg-config' to detect the FreeType 2 headers and
libraries in xdvik-ja.

If this bug is not resolved prior to the release of FreeType 2.9.1,
your package may FTBFS.

Thank you

[1]
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0
a93839b52818abbfe9b4c8755b4aa0f5232063 
--- End Message ---
--- Begin Message ---
Source: xdvik-ja
Source-Version: 22.87.03+j1.42-2

We believe that the bug you reported is fixed in the latest version of
xdvik-ja, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Youhei SASAKI  (supplier of updated xdvik-ja 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: Tue, 06 Nov 2018 15:06:53 +0900
Source: xdvik-ja
Binary: xdvik-ja
Architecture: source amd64
Version: 22.87.03+j1.42-2
Distribution: unstable
Urgency: medium
Maintainer: Youhei SASAKI 
Changed-By: Youhei SASAKI 
Description:
 xdvik-ja   - Japanized DVI Previewer for the X Window System
Closes: 892353
Changes:
 xdvik-ja (22.87.03+j1.42-2) unstable; urgency=medium
 .
   [ Youhei SASAKI ]
   * d/control: Bump Standard-Version 4.2.1
   * d/control: update Vcs-{Git,Browser}. use salsa
   * d/changelog: remove trailing-whitespace
 .
   [ Hilko Bengen ]
   * Add patch to detect freetype2 via pkg-config (Closes: #892353)
   * Debian release
Checksums-Sha1:
 9944e71cffce74b3f2c7340f7eefa2118288e50e 2087 xdvik-ja_22.87.03+j1.42-2.dsc
 cfb8bb5948f4975901cb3fe177de79bda4135c62 127636 
xdvik-ja_22.87.03+j1.42-2.debian.tar.xz
 6cb73343740ddf603c33662c50efed93cadea85a 1120348 
xdvik-ja-dbgsym_22.87.03+j1.42-2_amd64.deb
 92a6df32bdf4f132832d622e7b5cbfe5b7164b53 9399 
xdvik-ja_22.87.03+j1.42-2_amd64.buildinfo
 02451c7f3bd4b0a0a51faee189c0ba71fbb30c74 450072 
xdvik-ja_22.87.03+j1.42-2_amd64.deb
Checksums-Sha256:
 f50735ff502255dc33d244a39d54cdcd55bb32fb0f180cf30875b6b2cbef37b7 2087 
xdvik-ja_22.87.03+j1.42-2.dsc
 8f7bbaeb5b04838a253d71b69210330aae2a458da9e53a1b9712def5b3927c3f 127636 
xdvik-ja_22.87.03+j1.42-2.debian.tar.xz
 d80e802088ee368b31c4d6a73d028fd5fe1f70e571d0e9e0528c68c4d567ac77 1120348 
xdvik-ja-dbgsym_22.87.03+j1.42-2_amd64.deb
 77720a7fd71c2fabf050bb1f3650c32558661236c12b7c59fb2a98ac52beb4b8 9399 
xdvik-ja_22.87.03+j1.42-2_amd64.buildinfo
 56d64e0eb88b465a2883ca9b8621e27c4b8645c078b039c5df6cbb6800e8b490 450072 
xdvik-ja_22.87.03+j1.42-2_amd64.deb
Files:
 51191d24c18b237ed7ce9491e56e40e9 2087 tex optional 
xdvik-ja_22.87.03+j1.42-2.dsc
 d05f48dd8f32978949fd07ad38a9538d 127636 tex optional 
xdvik-ja_22.87.03+j1.42-2.debian.tar.xz
 fd0157fecb731313c6914cde6e295d83 1120348 debug optional 
xdvik-ja-dbgsym_22.87.03+j1.42-2_amd64.deb
 21a3f71a44cadc468dc98c2d45758340 9399 tex optional 
xdvik-ja_22.87.03+j1.42-2_amd64.buildinfo
 c06b5798abf288fba1bd74a29737397e 450072 tex optional 
xdvik-ja_22.87.03+j1.42-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZqTqcE/iQFWNasLmk5TzVIkdfgcFAlvhOp8ACgkQk5TzVIkd
fgehCA/+P75qf5e0NuLH6vjVTh5hpbqLZbpSoztnGiMbd/Q8/0uXo/YFrsy873fX
wI4CA/+HNqhiZETarHwbH7p4uFM2ub2TNcXhw+zhA2RaxDWHZkq66uaqg4LB1V5a
v3hbJXaY7Z847S/88Ss5w25xEHpv4834rDmxoV5dPBtqIW1D2cOJ5zoXp4aFDZTK
XIodQdNKKBAGnPK9kZt2ILjtTw0LodV6ujsKw/wrvIFNRWx+slH4zmcgGLd7x2kU

Processed: bug 912253 is forwarded to https://github.com/rails/protected_attributes/issues/93

[Debian Bug Tracking System]

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

> forwarded 912253 https://github.com/rails/protected_attributes/issues/93
Bug #912253 [src:ruby-protected-attributes] ruby-protected-attributes: FTBFS 
reliably (failing tests)
Set Bug forwarded-to-address to 
'https://github.com/rails/protected_attributes/issues/93'.
> thanks
Stopping processing here.

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

Bug#897474: marked as done (kwalify: FTBFS: ERROR: Test "ruby2.5" failed.)

[Debian Bug Tracking System]

Your message dated Tue, 06 Nov 2018 07:34:11 +
with message-id 
and subject line Bug#897474: fixed in kwalify 0.7.2-8
has caused the Debian Bug report #897474,
regarding kwalify: FTBFS: ERROR: Test "ruby2.5" failed.
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.)


-- 
897474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kwalify
Version: 0.7.2-6
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby2.5 from debian/ruby-test-files.yaml  
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/kwalify/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=debian/kwalify/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
>  ruby2.5 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ 
> \{\ \|f\|\ require\ f\ \}
> /<>/test/test-users-guide.rb:5: warning: already initialized 
> constant UsersGuideTest::DATA_DIR
> /<>/.pc/test_paths_fix.patch/test/test-users-guide.rb:5: 
> warning: previous definition of DATA_DIR was here
> /<>/test/test-users-guide.rb:6: warning: already initialized 
> constant UsersGuideTest::CURR_DIR
> /<>/.pc/test_paths_fix.patch/test/test-users-guide.rb:6: 
> warning: previous definition of CURR_DIR was here
> Loaded suite [.]
> Started
> N
> ===
> Notification:  was redefined 
> [test_address_book_ruby(UsersGuideTest)]
> /<>/test/test-users-guide.rb:21:in `'
> ===
> .N
> ===
> Notification:  was redefined 
> [test_example_address_book_ruby(UsersGuideTest)]
> /<>/test/test-users-guide.rb:26:in `'
> ===
> .N
> ===
> Notification:  was redefined 
> [test_databind1(DataBindingTest)]
> (eval):1:in `block in load_yaml_testdata'
> ===
> .N
> ===
> Notification:  was redefined 
> [test_databind2(DataBindingTest)]
> (eval):1:in `block in load_yaml_testdata'
> ===
> .N
> ===
> Notification:  was redefined 
> [test_databind3(DataBindingTest)]
> (eval):1:in `block in load_yaml_testdata'
> ===
> .N
> ===
> Notification:  was redefined 
> [test_databind4(DataBindingTest)]
> (eval):1:in `block in load_yaml_testdata'
> ===
> ...
> ...
> ...
> ...
> .E
> ===
> Error: 
> test_require_build_kwalify_nHbfNW_kwalify_0_7_2_pc_proper_string_split_patch_test_test_validator_rb(RequireFailedErrors):
>  LoadError: failed to load 
> >/.pc/proper_string_split.patch/test/test-validator.rb>: 
> cannot load such file -- 
> /<>/.pc/proper_string_split.patch/test/test.rb
> /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
> /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
> /<>/.pc/proper_string_split.patch/test/test-validator.rb:7:in 
> `'
> /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
> 

Processed: bug 912239 is forwarded to https://github.com/jnunemaker/httparty/issues/621

[Debian Bug Tracking System]

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

> forwarded 912239 https://github.com/jnunemaker/httparty/issues/621
Bug #912239 [src:ruby-httparty] ruby-httparty FTBFS: SSL_CTX_use_certificate: 
ee key too small
Set Bug forwarded-to-address to 
'https://github.com/jnunemaker/httparty/issues/621'.
> thanks
Stopping processing here.

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

Bug#913026: libwww-curl-perl: Uninstallable on armhf due to being built against Perl 5.26 instead of 5.28

[Axel Beckert]

Package: libwww-curl-perl
Version: 4.17-5
Severity: serious

Hi,

it seems as if libwww-curl-perl 4.17-5 has been built for armhf in a
outdated chroot:

# apt-cache show libwww-curl-perl | egrep 'Version|Depends|Architecture|^$'
Version: 4.17-5
Architecture: armhf
Depends: perl (>= 5.26.2-7+b1), perlapi-5.26.2, libc6 (>= 2.15), 
libcurl3-gnutls (>= 7.16.2)
^^
Version: 4.17-4+b3
Architecture: armhf
Depends: perl (>= 5.28.0-3), perlapi-5.28.0, libc6 (>= 2.15), libcurl3-gnutls 
(>= 7.16.2)
#

(Underlining has been done manual.)

Could please the armhf buildd admins chase down which buildds are
affected (at least arm-arm-01 where this package was built) and trigger
BinNMUs for all affected packages? (And then probably close this bug
report.)

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libwww-curl-perl depends on:
ii  libc6   2.27-8
ii  libcurl3-gnutls 7.62.0-1
ii  perl5.28.0-3
ii  perl-base [perlapi-5.28.0]  5.28.0-3

libwww-curl-perl recommends no packages.

Versions of packages libwww-curl-perl suggests:
ii  libcurl4-gnutls-dev  7.62.0-1

-- no debconf information

Bug#913025: emacspeak: emacspeak post-installation failed

[Remi Vanicat]

Package: emacspeak
Version: 47.0+dfsg-4
Severity: grave

When upgrading emacspeak, post-installation failed. Compile log is
attached. 

/usr/lib/emacsen-common/packages/install/emacspeak byte-compiling for emacs

Configure in /usr/share/emacs/site-lisp/emacspeak...
make[1] : on entre dans le répertoire « 
/usr/share/emacs/site-lisp/emacspeak/etc »
make[1] : on quitte le répertoire « /usr/share/emacs/site-lisp/emacspeak/etc »
make[1] : on entre dans le répertoire « 
/usr/share/emacs/site-lisp/emacspeak/lisp »
emacs -batch -q -no-site-file --eval '(setq file-name-handler-alist nil 
gc-cons-threshold 6400)'   -l ./emacspeak-load-path.el  \
-l ./emacspeak-autoload.el  \
-f emacspeak-auto-generate-autoloads
emacs -batch -q -no-site-file --eval '(setq file-name-handler-alist nil 
gc-cons-threshold 6400)'  -l ./emacspeak-load-path.el  -l cus-dep -l 
./emacspeak-autoload.el \
-f emacspeak-auto-custom-make-dependencies "."
Scanning . for custom
Generating /usr/share/emacs/site-lisp/emacspeak/lisp/cus-load.el...
Generating /usr/share/emacs/site-lisp/emacspeak/lisp/cus-load.el...done
mv cus-load.el emacspeak-cus-load.el
make[1] : on quitte le répertoire « /usr/share/emacs/site-lisp/emacspeak/lisp »
make[1] : on entre dans le répertoire « 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client »
make[1]: rien à faire pour « config ».
make[1] : on quitte le répertoire « 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client »
Configured emacspeak in directory /usr/share/emacs/site-lisp/emacspeak.

Byte-compile...
make[1] : on entre dans le répertoire « 
/usr/share/emacs/site-lisp/emacspeak/lisp »
emacs -batch -q -no-site-file --eval '(setq file-name-handler-alist nil 
gc-cons-threshold 6400)'   -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-loaddefs.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-loaddefs.el  -f 
batch-byte-compile tts.el
emacs -batch -q -no-site-file --eval '(setq file-name-handler-alist nil 
gc-cons-threshold 6400)'   -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-loaddefs.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-loaddefs.el  -f 
batch-byte-compile acss-structure.el
emacs -batch -q -no-site-file --eval '(setq file-name-handler-alist nil 
gc-cons-threshold 6400)'   -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-loaddefs.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-loaddefs.el  -f 
batch-byte-compile dtk-interp.el
emacs -batch -q -no-site-file --eval '(setq file-name-handler-alist nil 
gc-cons-threshold 6400)'   -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-loaddefs.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-loaddefs.el  -f 
batch-byte-compile dtk-unicode.el
emacs -batch -q -no-site-file --eval '(setq file-name-handler-alist nil 
gc-cons-threshold 6400)'   -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-loaddefs.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-loaddefs.el  -f 
batch-byte-compile dtk-speak.el
emacs -batch -q -no-site-file --eval '(setq file-name-handler-alist nil 
gc-cons-threshold 6400)'   -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-loaddefs.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/emacspeak-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-load-path.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-cus-load.el -l 
/usr/share/emacs/site-lisp/emacspeak/lisp/g-client/g-loaddefs.el  -f 
batch-byte-compile voice-setup.el
emacs -batch -q -no-site-file --eval '(setq 

Bug#899870: marked as done (pycangjie: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 06 Nov 2018 02:58:44 +
with message-id 
and subject line Bug#899870: fixed in pycangjie 1.3-1
has caused the Debian Bug report #899870,
regarding pycangjie: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
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.)


-- 
899870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pycangjie
Version: 1.2-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of pycangjie,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package pycangjie since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pycangjie
Source-Version: 1.3-1

We believe that the bug you reported is fixed in the latest version of
pycangjie, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated pycangjie 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, 05 Nov 2018 19:43:04 -0500
Source: pycangjie
Binary: python3-pycangjie
Architecture: source
Version: 1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 python3-pycangjie - Python wrapper to libcangjie
Closes: 899870
Changes:
 pycangjie (1.3-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release 1.3.
   * debian: Apply "wrap-and-sort -abst".
   * debian/control:
 + Bump Standards-Version to 4.2.1 (no changes needed).
 + Bump debhelper compat to v11.
 + Update maintainer email address and use Debian Input Method Team.
   (Closes: #899870)
 + Update Vcs-* fields and use git repo under Salsa input-method team.
   * debian/rules: Use "dh_missing --fail-missing".
   * debian/copyright: Use secure uri.
   * debian/patches:
 - Drop patches that are merged upstream.
 + Cherry-pick an upstream patch to fix typo.
   * debian/watch: Rewrite in v4 format and watch new upstream
 GitHub project.
Checksums-Sha1:
 7bed566f83be730350896fea58063534a9fad477 2031 pycangjie_1.3-1.dsc
 bb81dba1b0b3b1b5cd967024cef19f2963d0833d 13593 pycangjie_1.3.orig.tar.gz
 7036699b7625b0547840071b30065cbe011fb7eb 3340 pycangjie_1.3-1.debian.tar.xz
 

Bug#908681: libsane1: pointless package rename

[John Paul Adrian Glaubitz]

Hi Laurent!

On 11/6/18 2:09 AM, Laurent Bigonville wrote:
> This bug is open for more than a month without any recent reaction from the 
> maintainer, multiple people have asked for the status over the month of 
> October (including mails addressed directly to the maintainer), nothing.

That bug was forced upon the maintainer. He made his decision, others disagreed
and used their positions to push their opinion on him. However, so far I have 
not
seen any reference to the Debian Policy which grants such a particular right.

> This is/was blocking the migration of some packages to testing (at least one 
> from GNOME, that's why I start caring).

That was not Joerg's fault. He maintained his package with a lot of diligence
while no one else was interested in maintaining this package.

> I felt reading https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908681#99 
> that some kind of consensus was reached, that was maybe incorrect.

There was no consensus from the maintainer. There were people pushing on Joerg,
you jumping on the bandwagon and forcing the change on him. Again, no 
justification
with reference to corresponding parts of the Debian Policy.

> Not much more to say here.

So you think it's acceptable to override maintainer decisions without the CTTE
which is supposed to be used in this context? Would you be okay for this to
be done with your packages, too?

> Laurent Bigonville who just spent his last care replying to this mail.

Not sure I understand what you mean?

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#913019: src:haskell-text: now a ghc bootlib

[Clint Adams]

Package: src:haskell-text
Version: 1.2.3.0-1
Severity: serious

1.2.3.0 is bundled with ghc and should not be released separately in
buster

Bug#908681: libsane1: pointless package rename

[Laurent Bigonville]

Le 5/11/18 à 23:54, John Paul Adrian Glaubitz a écrit :

Hello Lauren!

Hello,

Is there any reason why you are hijacking the package here and overriding
a maintainer's decision without contacting the Debian CTTE?


This bug is open for more than a month without any recent reaction from 
the maintainer, multiple people have asked for the status over the month 
of October (including mails addressed directly to the maintainer), nothing.


This is/was blocking the migration of some packages to testing (at least 
one from GNOME, that's why I start caring).


I felt reading 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908681#99 that some 
kind of consensus was reached, that was maybe incorrect.


Not much more to say here.

Laurent Bigonville who just spent his last care replying to this mail.

Processed: Re: Bug#901214 closed by Gert Wollny (Bug#901214: fixed in vtk-dicom 0.8.7-1)

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.8.7-1
Bug #901214 {Done: Gert Wollny } [libvtkdicom0.8] 
libvtkdicom0.8: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/cmake/DICOMConfig.cmake
Marked as found in versions vtk-dicom/0.8.7-1; no longer marked as fixed in 
versions vtk-dicom/0.8.7-1 and reopened.

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

Bug#901214: closed by Gert Wollny (Bug#901214: fixed in vtk-dicom 0.8.7-1)

[Andreas Beckmann]

Control: found -1 0.8.7-1

On 2018-10-30 17:15, Debian Bug Tracking System wrote:
>* d/*.install: move cmake files into -dev package, Closes: #901214

You are still missing
  Breaks+Replaces: libvtkdicom0.7
since the library package in stretch shipped the cmake files as well.


Andreas

Bug#913017: tesseract-ocr: missing Breaks+Replaces: libtesseract-dev (<< 4)

[Andreas Beckmann]

Package: tesseract-ocr
Version: 4.00~git3241-1066f696-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' 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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../tesseract-ocr_4.00~git3241-1066f696-1_amd64.deb ...
  Unpacking tesseract-ocr (4.00~git3241-1066f696-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tesseract-ocr_4.00~git3241-1066f696-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/tesstrain.sh', which is also in package 
libtesseract-dev 3.04.01-5
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/tesseract-ocr_4.00~git3241-1066f696-1_amd64.deb


cheers,

Andreas


libtesseract-dev=3.04.01-5_tesseract-ocr=4.00~git3241-1066f696-1.log.gz
Description: application/gzip

Bug#913016: cpp-6-x86-64-linux-gnu:amd64: ships /usr/bin/x86_64-linux-gnu-cpp-6, already in cpp-6:amd64

[Andreas Beckmann]

Package: cpp-6-x86-64-linux-gnu
Version: 6.5.0-2cross1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package cpp-6-x86-64-linux-gnu.
  Preparing to unpack .../cpp-6-x86-64-linux-gnu_6.5.0-2cross1_amd64.deb ...
  Unpacking cpp-6-x86-64-linux-gnu (6.5.0-2cross1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cpp-6-x86-64-linux-gnu_6.5.0-2cross1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/x86_64-linux-gnu-cpp-6', which is also in 
package cpp-6 6.5.0-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/cpp-6-x86-64-linux-gnu_6.5.0-2cross1_amd64.deb


This seems to affect several other -cross packages as well.


cheers,

Andreas


cpp-6=6.5.0-2_cpp-6-x86-64-linux-gnu=6.5.0-2cross1.log.gz
Description: application/gzip

Processed: Re: eboard: add Conflicts: eboard-extras-pack1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #913011 [eboard] eboard: add Conflicts: eboard-extras-pack1
Severity set to 'serious' from 'important'

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

Bug#913015: python{,3}-dcmstack: both ship /usr/bin/dcmstack, /usr/bin/nitool

[Andreas Beckmann]

Package: python-dcmstack,python3-dcmstack
Version: 0.7-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package python3-dcmstack.
  Preparing to unpack .../12-python3-dcmstack_0.7-1_all.deb ...
  Unpacking python3-dcmstack (0.7-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-X49jxg/12-python3-dcmstack_0.7-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/dcmstack', which is also in package 
python-dcmstack 0.7-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-X49jxg/12-python3-dcmstack_0.7-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/bin/dcmstack
  usr/bin/nitool

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


python-dcmstack=0.7-1_python3-dcmstack=0.7-1.log.gz
Description: application/gzip

Bug#909000: Fixed for new point release

[Paul van der Vlis]

First I did not understand this fix. But now I see the new version is in
proposed-updates. So it's in the queue for the new Debian 9.6.
https://release.debian.org/proposed-updates/stable.html

Bug#912359: marked as done (msv: FTBFS with Java 11 due to CORBA removal)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 23:23:58 +
with message-id 
and subject line Bug#912359: fixed in msv 2009.1+dfsg1-6
has caused the Debian Bug report #912359,
regarding msv: FTBFS with Java 11 due to CORBA removal
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.)


-- 
912359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: msv
Version: 2009.1+dfsg1-5
Severity: serious
Tags: buster sid ftbfs

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

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile 
(default-testCompile) on project msv-core: Compilation 
failure
[ERROR] 
/build/1st/msv-2009.1+dfsg1/msv/test/batch/model/IValidator.java:[15,21] 
package org.omg.CORBA does not exist
[ERROR] 
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug 
logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with 
the command
[ERROR]   mvn  -rf :msv-core
make: *** [/usr/share/cdbs/1/class/maven.mk:95: mvn-build] Error 1
--- End Message ---
--- Begin Message ---
Source: msv
Source-Version: 2009.1+dfsg1-6

We believe that the bug you reported is fixed in the latest version of
msv, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated msv 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, 05 Nov 2018 23:37:18 +0100
Source: msv
Binary: libmsv-java
Architecture: source
Version: 2009.1+dfsg1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libmsv-java - Sun multi-schema XML validator
Closes: 912359
Changes:
 msv (2009.1+dfsg1-6) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 11 (Closes: #912359)
   * Build with the DH sequencer instead of CDBS
   * Standards-Version updated to 4.2.1
   * Switch to debhelper level 11
   * Use salsa.debian.org Vcs-* URLs
   * Changed the priority from extra to optional
   * Removed the documentation from the package
   * Track and download the new releases from GitHub
Checksums-Sha1:
 198bca4511a42de5ab1dee267feaa9b5f47dfcf6 2119 msv_2009.1+dfsg1-6.dsc
 c90d0788194cdd998ebc08b2ab1d97c208f94b4d 7588 msv_2009.1+dfsg1-6.debian.tar.xz
 fd9ed82ca1ee23270c094d052e9d1afdcd8f0f07 14649 
msv_2009.1+dfsg1-6_source.buildinfo
Checksums-Sha256:
 1f8331eb307b149bb85ff7a2ecb99f0747cbe8f33ae624a7af861e7c7be1f39c 2119 
msv_2009.1+dfsg1-6.dsc
 a87df3508ef0b0edb6655c5973748d4fcc05d81090b9c5d03d1ae71635f23cc6 7588 
msv_2009.1+dfsg1-6.debian.tar.xz
 b1b767bd3863bcee5ce113b259aa8aa28863e9dab5a42a787ba42fef4d44a473 14649 
msv_2009.1+dfsg1-6_source.buildinfo
Files:
 0f5773ad606a4bfc7fab0bebeec9a39a 2119 java optional msv_2009.1+dfsg1-6.dsc
 b12c879e8488bcfc5160aef59fc36fb8 7588 java optional 
msv_2009.1+dfsg1-6.debian.tar.xz
 aa68631d0a77b8979d2e554366ad1ad4 14649 java optional 
msv_2009.1+dfsg1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlvgxsoSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsYZAP/i/hTMKkU9RNzzSFpuPLU+PeWvIAqJBB
wLn4o6mLv71ojxUEr8PbYRRaBeU+o2GVD2woYUOsLeGBDpLoVsCBK6cJ2gyCeaE7
U8R3HEjSqxuAfex3yWynoGqBUFhF/eJkCmngySUpDh8lBBsr60IsEsBuMa9RqGgb
2meycrciXG6ghpdO3HDK/t8OOHSfu2Zeg52/HrgxqGKI+Ifp2x7bITRa+kaFqTl3
KN7pe2cejtCb3XUoMiHsp4OAF/vHfGj5w10D5fcHLiJSzZFwKudrG07MBaIVdxow
qSgWeFVFvfaD+DDt/TTxAqO3Tk1lqyVBIl92Puxaqb3Z45RJyKRG/J28pVQp+VT7

Bug#859784: NMU for validns

[Sebastian Andrzej Siewior]

On 2018-11-03 18:12:07 [+0100], Christoph Biedl wrote:
> Subject: Build against openssl 1.1.
> Author: Chris West 
> Bug: https://github.com/tobez/validns/pull/64
> Bug-Debian: https://bugs.debian.org/859784
> Last-Update: 2018-11-03
> 
> --- a/dnskey.c
> +++ b/dnskey.c
> @@ -154,6 +154,7 @@
>   unsigned int e_bytes;
>   unsigned char *pk;
>   int l;
> + BIGNUM *n, *e;
>  
>   rsa = RSA_new();
>   if (!rsa)
> @@ -174,11 +175,14 @@
>   if (l < e_bytes) /* public key is too short */
>   goto done;
>  
> - rsa->e = BN_bin2bn(pk, e_bytes, NULL);
> + e = BN_bin2bn(pk, e_bytes, NULL);
> + if (e == NULL) goto done;

putting the goto into a new line would look better and match the coding
style.

>   pk += e_bytes;
>   l -= e_bytes;
>  
> - rsa->n = BN_bin2bn(pk, l, NULL);
> + n = BN_bin2bn(pk, l, NULL);
> + if (n == NULL) goto done;
> + RSA_set0_key(rsa, n, e, NULL);
>  
>   pkey = EVP_PKEY_new();
>   if (!pkey)
…
> --- a/rrsig.c
> +++ b/rrsig.c
> @@ -374,7 +374,7 @@
>  static pthread_mutex_t *lock_cs;
>  static long *lock_count;
>  
> -static unsigned long pthreads_thread_id(void)
> +unsigned long pthreads_thread_id(void)
>  {
>   unsigned long ret;
>  
> @@ -382,7 +382,7 @@
>   return(ret);
>  }
>  
> -static void pthreads_locking_callback(int mode, int type, char *file, int 
> line)
> +void pthreads_locking_callback(int mode, int type, char *file, int line)

This is noise. Plus lock_cs, lock_count, CRYPTO_set_id_callback(),
CRYPTO_set_locking_callback() is not required since OpenSSL 1.1.0:
|git grep CRYPTO_set_locking_callback include/
|include/openssl/crypto.h:#  define CRYPTO_set_locking_callback(func)

I would suggest to put it behind a version ifdef so it is left out. I
_assume_ the static has been removed to avoid "defined but not used
warning".

>  {
>   if (mode & CRYPTO_LOCK) {
>   pthread_mutex_lock(&(lock_cs[type]));
> @@ -446,6 +446,7 @@
>   if (k->to_verify[i].openssl_error != 0)
>   e = k->to_verify[i].openssl_error;
>   }
> + EVP_MD_CTX_free(k->to_verify[i].ctx);
>   }
>   if (!ok) {
>   struct named_rr *named_rr;

Otherwise it looks okay, thank you.

Sebastian

Bug#908681: libsane1: pointless package rename

[John Paul Adrian Glaubitz]

On 11/6/18 12:04 AM, Paul Tagliamonte wrote:
> Was this a hijack or NMU? I saw a NMU to DELAYED with a log
> in the bug announcing it. I may have missed something

I'm the sponsor, I was not put in the loop over this decision
and Joerg may not have been available the past three days.

Joerg Frings-Fuerst as the maintainer made a decision. That decision
was not accepted by Julien who opened an RC bug. Joerg disagreed with
that but felt he didn't have any voice against a member of the stable
release team.

Then Laurent came around, not knowing the discussion and uploaded a
an NMU just informing the maintainer not me with just a three days
heads-up and now we have another person overriding a maintainer's
decision.

I'm not sure why that upload happened. 

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#913014: e3 (all binaries): immediate segmentation fault

[s3v]

Package: e3
Version: 1:2.71-1
Severity: grave


Dear maintainer,

I'm unable to run e3 and related binaries (e3em, e3ne, e3pi, e3vi and e3ws):

 $ e3
 Segmentation fault

 $ gdb e3
 [...]
 Reading symbols from e3...(no debugging symbols found)...done.
 (gdb) run
 Starting program: /usr/bin/e3
 During startup program terminated with signal SIGSEGV, Segmentation fault.
 (gdb) bt
 No stack.

A little bit more infos after executing the same command on tty1:

 $ e3
 3938 (e3): Uhuuh, elf segment at 0804b000 requested but the memory is
mapped already
 Segmentation fault

On a virtualized Debian Stretch this problem doesn't occurs.

Kind regards.


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

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

-- no debconf information

Bug#908681: libsane1: pointless package rename

[Paul Tagliamonte]

Was this a hijack or NMU? I saw a NMU to DELAYED with a log in the bug
announcing it. I may have missed something

paultag

Bug#908681: libsane1: pointless package rename

[John Paul Adrian Glaubitz]

Hello Lauren!

Is there any reason why you are hijacking the package here and overriding
a maintainer's decision without contacting the Debian CTTE?

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#912359: Bug #912359 in msv marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #912359 in msv 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/msv/commit/459af5a51cb848e50208862d757eacfc1b92c932


Fixed the build failure with Java 11 (Closes: #912359)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912359

Processed: Bug #912359 in msv marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912359 [src:msv] msv: FTBFS with Java 11 due to CORBA removal
Added tag(s) pending.

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

Bug#880047: postgrey: Regression - Postgrey doesn't start after installing new stable proposed-update

[Roger Lynn]

Package: postgrey
Version: 1.36-3+deb9u1
Followup-For: Bug #880047

On a Stable system installed about a year ago, Postgrey 1.36-3 has always run
fine. When installing 1.36-3+deb9u1 I get:

Setting up postgrey (1.36-3+deb9u1) ...
Installing new version of config file /etc/init.d/postgrey ...
[] Starting postfix greylisting daemon: postgreymkdir: cannot create 
directory ‘/var/run/postgrey/’: File exists
invoke-rc.d: initscript postgrey, action "start" failed.

# /etc/init.d/postgrey stop
[] Stopping postfix greylisting daemon: postgreystart-stop-daemon: unable 
to open pidfile /var/run/postgrey/postgrey.pid (Not a directory)

# /etc/init.d/postgrey start
[] Starting postfix greylisting daemon: postgreymkdir: cannot create 
directory ‘/var/run/postgrey/’: File exists

$ ls -al /var/run/postgrey 
srw-rw-rw- 1 postgrey postgrey 0 Oct 27 23:14 /var/run/postgrey

After deleting /var/run/postgrey Postgrey will start, although subsequent
restarts give:

# /etc/init.d/postgrey start
[] Starting postfix greylisting daemon: postgreyPid_file 
"/var/run/postgrey/postgrey.pid" already exists.  Overwriting!
. ok 

Thanks,

Roger

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

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

Versions of packages postgrey depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.61
ii  libberkeleydb-perl 0.55-1+b2
ii  libnet-dns-perl1.07-1
ii  libnet-server-perl 2.008-3
ii  libnetaddr-ip-perl 4.079+dfsg-1+b1
ii  perl   5.24.1-3+deb9u4
ii  ucf3.0036

Versions of packages postgrey recommends:
ii  exim4  4.89-2+deb9u3
ii  libnet-rblclient-perl  0.5-3
ii  libparse-syslog-perl   1.10-2

postgrey suggests no packages.

-- debconf information:
  postgrey/1.32-3_changeport:

Bug#909689: asterisk: autopkgtest regression

[Bernhard Schmidt]

Hi,

> 
> this is where asterisk is actually segfaulting (not during the
> testsuite, but when collecting the results). I haven't managed to pull
> the backtrace from the autopkgtest worker yet.

Backtrace:

#0  ___fprintf_chk (fp=fp@entry=0x0, flag=flag@entry=1,
format=format@entry=0x555981d58a08 "\t\t\n")
at fprintf_chk.c:30
_IO_acquire_lock_file = 0x0
ap = {{gp_offset = 2202655248, fp_offset = 21849,
overflow_arg_area = 0x7fac1e6721c8, reg_save_area = 0x555981dae8b0
}}
done = 
#1  0x555981cf8ae1 in fprintf (__fmt=0x555981d58a08 "\t\t\n", __stream=0x0)
at /usr/include/x86_64-linux-gnu/bits/stdio2.h:97
No locals.
#2  test_xml_entry (test=test@entry=0x55598349da10, f=f@entry=0x0) at
test.c:335
test_cat = 0x7fac380057d9 "apps.app_gosub"
next_cat = 
test_name = 0x7fac27fc216f "gosub application"
category = 
#3  0x555981cfa013 in test_generate_results
(xml_path=xml_path@entry=0x0,
txt_path=txt_path@entry=0x7fac3801b24a
"/tmp/autopkgtest.Be0rXk/build.Ign/real-tree/debian/tests/testmods/output/results.txt",
category=0x0, name=0x0) at test.c:574
f_xml = 
f_txt = 
res = 
test = 0x55598349da10
__PRETTY_FUNCTION__ = "test_generate_results"
#4  0x555981cfa527 in test_generate_results (txt_path=0x7fac3801b24a
"/tmp/autopkgtest.Be0rXk/build.Ign/real-tree/debian/tests/testmods/output/results.txt",

xml_path=0x0, category=0x0, name=0x0) at ./include/asterisk/strings.h:67
f_txt = 0x0
test = 0x0
mode = TEST_ALL
f_xml = 0x0
res = 0
mode = 
f_xml = 
f_txt = 
res = 
test = 
__PRETTY_FUNCTION__ = "test_generate_results"
#5  test_cli_generate_results (e=, cmd=,
a=0x7fac1e6722e0) at test.c:1047
option = {0x555981d3a92d "xml", 0x555981d3cd2a "txt", 0x0}
file = 0x7fac3801b24a
"/tmp/autopkgtest.Be0rXk/build.Ign/real-tree/debian/tests/testmods/output/results.txt"
type = 
isxml = 0
res = 0
buf = 
time = {tv_sec = 1541457075, tv_usec = }

Bernhard

Bug#909689: asterisk: autopkgtest regression

[Bernhard Schmidt]

Hi,

> I don't know how much time I'll have to check on this in the next days.
> Raising severity to block testing migration for now.

Okay, I tried to have a look at this and I have to admit I'm a bit confused.

First, I do see a failing unittest in MY autopkgtest qemu instance that
is not visible on
https://ci.debian.net/data/autopkgtest/testing/amd64/a/asterisk/1270861/log.gz

START  /main/uri/ - uri_parse
[test_uri.c:uri_parse:78]: Condition failed: (uri =
ast_uri_parse(scenario[0]))
END/main/uri/ - uri_parse Time: <1ms Result: FAIL

Neither main/uri.c nor test_uri.c has been changed in the last couple of
years, and the code looks so dead simple that I can't see anything wrong.

In the end it logs

494 Test(s) Executed  493 Passed  1 Failed

Then the test executes

$asterisk -rx "test generate results txt $results_file"

this is where asterisk is actually segfaulting (not during the
testsuite, but when collecting the results). I haven't managed to pull
the backtrace from the autopkgtest worker yet.

asterisk  8990 21.9  9.3 942052 94380 ?SLsl 21:49   0:40
/usr/sbin/asterisk -U asterisk -C
/tmp/autopkgtest.Be0rXk/build.Ign/real-tree/debian/tests/testmods/output/asterisk.conf
-U asterisk
+ debian/tests/testmods/asterisk -rx 'test generate results txt
/tmp/autopkgtest.Be0rXk/build.Ign/real-tree/debian/tests/testmods/output/results.txt'
asterisk  8990 21.9  0.0  0 0 ?Zsl  21:49   0:40
[asterisk] 

The official Asterisk Jenkins jobs seems to use "test generate results
xml", which

a) does not segfault
b) shows slightly different numbers



[...]




So it says 0 errors and one more test than on the CLI output, but does
list the failing unittest.

Tzafrir, any idea?

Bernhard

Bug#912351: marked as done (stax-ex: FTBFS with Java 11 due to JAXB removal)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 21:36:59 +
with message-id 
and subject line Bug#912351: fixed in stax-ex 1.7.8-3
has caused the Debian Bug report #912351,
regarding stax-ex: FTBFS with Java 11 due to JAXB removal
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.)


-- 
912351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stax-ex
Version: 1.7.8-2
Severity: serious
Tags: ftbfs

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

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2.422 s
[INFO] Finished at: 2019-12-02T10:47:40-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project stax-ex: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/stax-ex-1.7.8/src/java/org/jvnet/staxex/util/MtomStreamWriter.java:[43,33]
 package javax.xml.bind.attachment does not exist
[ERROR] 
/build/1st/stax-ex-1.7.8/src/java/org/jvnet/staxex/util/MtomStreamWriter.java:[56,5]
 cannot find symbol
[ERROR]   symbol:   class AttachmentMarshaller
[ERROR]   location: interface org.jvnet.staxex.util.MtomStreamWriter
[ERROR] 
/build/1st/stax-ex-1.7.8/src/java/org/jvnet/staxex/util/XMLStreamReaderToXMLStreamWriter.java:[45,33]
 package javax.xml.bind.attachment does not exist
[ERROR] 
/build/1st/stax-ex-1.7.8/src/java/org/jvnet/staxex/util/XMLStreamReaderToXMLStreamWriter.java:[89,5]
 cannot find symbol
[ERROR]   symbol:   class AttachmentMarshaller
[ERROR]   location: class org.jvnet.staxex.util.XMLStreamReaderToXMLStreamWriter
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
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=/build/1st/stax-ex-1.7.8 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/stax-ex-1.7.8/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/stax-ex-1.7.8/debian 
-Dmaven.repo.local=/build/1st/stax-ex-1.7.8/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 2
--- End Message ---
--- Begin Message ---
Source: stax-ex
Source-Version: 1.7.8-3

We believe that the bug you reported is fixed in the latest version of
stax-ex, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated stax-ex 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, 05 Nov 2018 22:16:31 +0100
Source: stax-ex
Binary: libstax-ex-java
Architecture: source
Version: 1.7.8-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libstax-ex-java - Extended StAX API
Closes: 912351
Changes:
 stax-ex (1.7.8-3) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 11 (Closes: #912351)
   * Standards-Version updated to 4.2.1
Checksums-Sha1:
 469f2664513694099834db6b1d5d6bc08e5d50f5 2068 stax-ex_1.7.8-3.dsc
 46b972be6f0cc8f150ae8ba059da5cdef7c9f4b3 9424 stax-ex_1.7.8-3.debian.tar.xz
 356c291f53c095c6215054bd9277b42c6c3f39cc 17481 stax-ex_1.7.8-3_source.buildinfo
Checksums-Sha256:
 12fa2ac6dad77ab00297f11034f99042d19f6fca7d07f6214986dcd70fe09505 2068 
stax-ex_1.7.8-3.dsc
 

Bug#877162: marked as done (fontconfig-config: Configuration fails on upgrade from <2.12)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 21:34:17 +
with message-id 
and subject line Bug#877162: fixed in fontconfig 2.13.1-2
has caused the Debian Bug report #877162,
regarding fontconfig-config: Configuration fails on upgrade from <2.12
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.)


-- 
877162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fontconfig-config
Version: 2.12.3-0.2
Severity: important

Dear Maintainer,

I previously had a /etc/fonts/conf.d/10-hinting-slight.conf to use the
hintslight style. When I tried to upgrade from stretch to the current
2.12.3-0.2, dpkg --configure failed:

Setting up fontconfig-config (2.12.3-0.2) ...
Installing new version of config file /etc/fonts/fonts.conf ...
ln: failed to create symbolic link
'/etc/fonts/conf.d/10-hinting-slight.conf': File exists
dpkg: error processing package fontconfig-config (--configure):
 subprocess installed post-installation script returned error exit status 1

Even if there is no previous 10-hinting-slight.conf, the problem
occurs on a downgrade-upgrade round-trip.

IMHO a reasonable behavior might be to check whether
/etc/fonts/conf.d/10-hinting-*.conf exists and skip the linking in the
affirmative case.

Best regards,
Timo
--- End Message ---
--- Begin Message ---
Source: fontconfig
Source-Version: 2.13.1-2

We believe that the bug you reported is fixed in the latest version of
fontconfig, 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 877...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated fontconfig 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: Mon, 05 Nov 2018 21:42:38 +0100
Source: fontconfig
Binary: fontconfig fontconfig-config fontconfig-udeb libfontconfig1-dev 
libfontconfig1
Architecture: source all amd64
Version: 2.13.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Laurent Bigonville 
Description:
 fontconfig - generic font configuration library - support binaries
 fontconfig-config - generic font configuration library - configuration
 fontconfig-udeb - generic font configuration library - minimal runtime (udeb)
 libfontconfig1 - generic font configuration library - runtime
 libfontconfig1-dev - generic font configuration library - development
Closes: 877162 896684 909728 909818 909841 912699
Changes:
 fontconfig (2.13.1-2) unstable; urgency=medium
 .
   * Team upload.
   [ Jelmer Vernooij ]
   * Replace XC-Package-Type with Package-Type.
 .
   [ Andreas Henriksson ]
   * Only create 10-hinting-slight.conf symlink if its non-existant
 (Closes: #877162)
 .
   [ Laurent Bigonville ]
   * debian/patches/path_max.patch: Fix FTBFS on hurd (Closes: #912699)
   * Do not build the documentation if the nodoc build profile is set, that
 should help to remove a (build) dependency cycle
   * debian/control: Bump Standards-Version to 4.2.1 (no further changes)
   * debian/control: Make fontconfig-config Breaks against libfontconfig1 (<<
 2.13.0), some config files are containing stanza not recognized with older
 versions (Closes: #896684)
   * debian/patches/do_not_remove_uuid.patch: Revert the cleanup of the .uuid
 files, this is causing multiple issues and it's not even fixing #897040,
 from upstream (Closes: #909728,#909841,#909818)
Checksums-Sha1:
 dd6eb4294856d7e95f5a7a406925c9a52e476c9a 2185 fontconfig_2.13.1-2.dsc
 e127e5cc61d8c8b2245cdd0915eede154a46e107 53600 
fontconfig_2.13.1-2.debian.tar.xz
 00d0006ac2f132fcdafcbe94792c24dbf119c4cf 280392 
fontconfig-config_2.13.1-2_all.deb
 38578586ed7d8c4f550cd88063631b9671e6a113 57608 
fontconfig-dbgsym_2.13.1-2_amd64.deb
 9a68451a3e01e35c71f6009e7cb6ef8fbbcb4a2f 121332 
fontconfig-udeb_2.13.1-2_amd64.udeb
 81e2461fb0f2a80fcd91bb9989de8aece357dafb 10503 
fontconfig_2.13.1-2_amd64.buildinfo
 6370c03f2d42967278d693702e2dd6a28d5fa94a 405176 fontconfig_2.13.1-2_amd64.deb
 829ecc37f1f8759a847ddac4e47dc9ce1dfe78ee 353532 
libfontconfig1-dbgsym_2.13.1-2_amd64.deb
 

Bug#896684: marked as done (fontconfig-config: Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf, due to many errors)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 21:34:17 +
with message-id 
and subject line Bug#896684: fixed in fontconfig 2.13.1-2
has caused the Debian Bug report #896684,
regarding fontconfig-config: Fontconfig error: Cannot load config file from 
/etc/fonts/fonts.conf, due to many errors
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.)


-- 
896684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fontconfig-config
Version: 2.13.0-4
Severity: important

After the upgrade of fontconfig-config from 2.12.6-0.1 to 2.13.0-4,
I get when running emacs25:

Fontconfig warning: "/etc/fonts/fonts.conf", line 5: unknown element "its:rules"
Fontconfig warning: "/etc/fonts/fonts.conf", line 6: unknown element 
"its:translateRule"
Fontconfig error: "/etc/fonts/fonts.conf", line 6: invalid attribute 'translate'
Fontconfig error: "/etc/fonts/fonts.conf", line 6: invalid attribute 'selector'
Fontconfig error: "/etc/fonts/fonts.conf", line 7: invalid attribute 'xmlns:its'
Fontconfig error: "/etc/fonts/fonts.conf", line 7: invalid attribute 'version'
Fontconfig warning: "/etc/fonts/fonts.conf", line 9: unknown element 
"description"
Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 4: unknown 
element "its:rules"
Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: unknown 
element "its:translateRule"
Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: invalid 
attribute 'translate'
Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: invalid 
attribute 'selector'
Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 6: invalid 
attribute 'xmlns:its'
Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 6: invalid 
attribute 'version'
Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 8: unknown 
element "description"
Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 4: 
unknown element "its:rules"
Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: 
unknown element "its:translateRule"
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: 
invalid attribute 'translate'
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: 
invalid attribute 'selector'
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 6: 
invalid attribute 'xmlns:its'
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 6: 
invalid attribute 'version'
Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 8: 
unknown element "description"
[...]
Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf

Note: I have upgraded fontconfig-config alone (the other fontconfig
related packages are not upgradable yet due to a blocking bug). If
I downgrade fontconfig-config to 2.12.6-0.1, these errors disappear.

-- 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)
Foreign Architectures: i386

Kernel: Linux 4.15.0-3-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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages fontconfig-config depends on:
ii  debconf [debconf-2.0]  1.5.66
ii  fonts-dejavu-core  2.37-1
ii  fonts-liberation   1:1.07.4-5
ii  ttf-bitstream-vera 1.10-8
ii  ucf3.0038

fontconfig-config recommends no packages.

fontconfig-config suggests no packages.

-- debconf information:
* fontconfig/hinting_type: Native
  fontconfig/hinting_style: hintslight
* fontconfig/enable_bitmaps: true
* fontconfig/subpixel_rendering: Automatic
--- End Message ---
--- Begin Message ---
Source: fontconfig
Source-Version: 2.13.1-2

We believe that the bug you reported is fixed in the latest version of
fontconfig, 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.
Laurent Bigonville  (supplier of updated fontconfig package)

(This message was generated automatically 

Bug#911776: marked as done (fontconfig: makes Firefox, Gimp, Inkscape occasionally freeze)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 21:34:17 +
with message-id 
and subject line Bug#909818: fixed in fontconfig 2.13.1-2
has caused the Debian Bug report #909818,
regarding fontconfig: makes Firefox, Gimp, Inkscape occasionally freeze
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.)


-- 
909818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fontconfig
Version: 2.13.0-5
Severity: grave

Details are reported in bug #909818

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

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=C:en_GB:en:en_US:it:fr:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fontconfig depends on:
ii  fontconfig-config  2.13.1-1
ii  libc6  2.27-6
pn  libfontconfig1 
ii  libfreetype6   2.8.1-2

fontconfig recommends no packages.

fontconfig suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fontconfig
Source-Version: 2.13.1-2

We believe that the bug you reported is fixed in the latest version of
fontconfig, 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 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated fontconfig 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: Mon, 05 Nov 2018 21:42:38 +0100
Source: fontconfig
Binary: fontconfig fontconfig-config fontconfig-udeb libfontconfig1-dev 
libfontconfig1
Architecture: source all amd64
Version: 2.13.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Laurent Bigonville 
Description:
 fontconfig - generic font configuration library - support binaries
 fontconfig-config - generic font configuration library - configuration
 fontconfig-udeb - generic font configuration library - minimal runtime (udeb)
 libfontconfig1 - generic font configuration library - runtime
 libfontconfig1-dev - generic font configuration library - development
Closes: 877162 896684 909728 909818 909841 912699
Changes:
 fontconfig (2.13.1-2) unstable; urgency=medium
 .
   * Team upload.
   [ Jelmer Vernooij ]
   * Replace XC-Package-Type with Package-Type.
 .
   [ Andreas Henriksson ]
   * Only create 10-hinting-slight.conf symlink if its non-existant
 (Closes: #877162)
 .
   [ Laurent Bigonville ]
   * debian/patches/path_max.patch: Fix FTBFS on hurd (Closes: #912699)
   * Do not build the documentation if the nodoc build profile is set, that
 should help to remove a (build) dependency cycle
   * debian/control: Bump Standards-Version to 4.2.1 (no further changes)
   * debian/control: Make fontconfig-config Breaks against libfontconfig1 (<<
 2.13.0), some config files are containing stanza not recognized with older
 versions (Closes: #896684)
   * debian/patches/do_not_remove_uuid.patch: Revert the cleanup of the .uuid
 files, this is causing multiple issues and it's not even fixing #897040,
 from upstream (Closes: #909728,#909841,#909818)
Checksums-Sha1:
 dd6eb4294856d7e95f5a7a406925c9a52e476c9a 2185 fontconfig_2.13.1-2.dsc
 e127e5cc61d8c8b2245cdd0915eede154a46e107 53600 
fontconfig_2.13.1-2.debian.tar.xz
 00d0006ac2f132fcdafcbe94792c24dbf119c4cf 280392 
fontconfig-config_2.13.1-2_all.deb
 38578586ed7d8c4f550cd88063631b9671e6a113 57608 
fontconfig-dbgsym_2.13.1-2_amd64.deb
 9a68451a3e01e35c71f6009e7cb6ef8fbbcb4a2f 121332 
fontconfig-udeb_2.13.1-2_amd64.udeb
 81e2461fb0f2a80fcd91bb9989de8aece357dafb 10503 
fontconfig_2.13.1-2_amd64.buildinfo
 6370c03f2d42967278d693702e2dd6a28d5fa94a 405176 fontconfig_2.13.1-2_amd64.deb
 829ecc37f1f8759a847ddac4e47dc9ce1dfe78ee 353532 
libfontconfig1-dbgsym_2.13.1-2_amd64.deb
 efa5a2366d87e9f57610b121ae18650f1c96cc1e 966256 
libfontconfig1-dev_2.13.1-2_amd64.deb
 

Bug#909818: marked as done (firefox: Web Content is eating nearly 100% CPU, several of them)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 21:34:17 +
with message-id 
and subject line Bug#909818: fixed in fontconfig 2.13.1-2
has caused the Debian Bug report #909818,
regarding firefox: Web Content is eating nearly 100% CPU, several of them
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.)


-- 
909818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox
Version: 62.0.2-1
Severity: grave
Justification: renders package unusable

Since some recent update (within the last week) firefox is behaving
completely maniac on one of my computers. I have already removed
all of ~/.mozilla, started firefox with 
MOZILLA_DISABLE_PLUGINS=1 firefox
no extensions installed, all clean slate. Still, even the most simple
pages don't load. The typical output of top is:
  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
 8666 norbert   20   0 1617680 216316 101096 R  70.4   1.3   2:38.40 Web Content
 8855 norbert   20   0 1509408 147020  69056 R  70.1   0.9   1:18.98 Web Content
 8573 norbert   20   0 1637532 227256 105332 R  67.1   1.4   2:39.35 Web Content
 8520 norbert   20   0 2010728 265448 145644 D  42.9   1.6   1:16.82 firefox

As said, removing all extensions, plugins, everything and still the
browser behaves completely crazy.

What else then fully removing .mozilla and starting without plugins can
be done to get it back? It doesn't crash, just eats all the CPU and
doesn't display anything.

Thanks

Norbert

-- Package-specific info:


-- Addons package information

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

Kernel: Linux 4.18.10 (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)

Versions of packages firefox depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.1-1
ii  libatk1.0-0   2.30.0-1
ii  libc6 2.27-6
ii  libcairo-gobject2 1.15.12-1
ii  libcairo2 1.15.12-1
ii  libdbus-1-3   1.12.10-1
ii  libdbus-glib-1-2  0.110-3
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.1-1
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.2.0-7
ii  libgdk-pixbuf2.0-02.38.0+dfsg-6
ii  libglib2.0-0  2.58.1-2
ii  libgtk-3-03.24.0-3
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.39-1
ii  libpango-1.0-01.42.4-3
ii  libsqlite3-0  3.25.2-1
ii  libstartup-notification0  0.12-5
ii  libstdc++68.2.0-7
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.6-1
ii  libx11-xcb1   2:1.6.6-1
ii  libxcb-shm0   1.13-3
ii  libxcb1   1.13-3
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.15-2
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages firefox recommends:
ii  libavcodec-extra57  7:3.4.3-1
ii  libavcodec587:4.0.2-2

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-5
ii  fonts-stix [otf-stix]  1.1.1-4
ii  libcanberra0   0.30-6
ii  libgssapi-krb5-2   1.16-2
ii  libgtk2.0-02.24.32-3
ii  pulseaudio 12.2-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fontconfig
Source-Version: 2.13.1-2

We believe that the bug you reported is fixed in the latest version of
fontconfig, 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 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated fontconfig package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the 

Processed: Bug #912351 in stax-ex marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912351 [src:stax-ex] stax-ex: FTBFS with Java 11 due to JAXB removal
Added tag(s) pending.

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

Bug#912351: Bug #912351 in stax-ex marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #912351 in stax-ex 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/stax-ex/commit/9cf0509baafa0a42f4a4ad93759a2f6323e9b6fb


Fixed the build failure with Java 11 (Closes: #912351)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912351

Processed: Re: Bug#912970: Max. recursion depth with nested structures exceeded

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 912695 912970
Bug #912695 [apt-show-versions] apt-show-versions: breaks "apt-get update" and 
uninstallable after Perl 5.28 upgrade
Bug #912709 [apt-show-versions] Max. recursion depth with nested structures 
exceeded
Bug #912970 [apt-show-versions] Max. recursion depth with nested structures 
exceeded
Severity set to 'critical' from 'normal'
Bug #912709 [apt-show-versions] Max. recursion depth with nested structures 
exceeded
Merged 912695 912709 912970

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

Bug#912288: zeroc-ice FTBFS with OpenJDK 11

[Jose Gutierrez de la Concha]

Fixed in 3.7.1-5



On Mon, Oct 29, 2018 at 10:00 PM Adrian Bunk  wrote:

> Source: zeroc-ice
> Version: 3.7.1-3
> Severity: serious
> Tags: ftbfs
>
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zeroc-ice.html
>
> ...
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':test:compileJava'.
> > error: invalid source release: 1.11
>


-- 
José Gutiérrez de la Concha
ZeroC, Inc.

Bug#912288: marked as done (zeroc-ice FTBFS with OpenJDK 11)

[Debian Bug Tracking System]

Your message dated Mon, 5 Nov 2018 23:06:13 +0100
with message-id 

and subject line Re: Bug#912288: zeroc-ice FTBFS with OpenJDK 11
has caused the Debian Bug report #912288,
regarding zeroc-ice FTBFS with OpenJDK 11
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.)


-- 
912288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zeroc-ice
Version: 3.7.1-3
Severity: serious
Tags: ftbfs

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

...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test:compileJava'.
> error: invalid source release: 1.11
--- End Message ---
--- Begin Message ---
Fixed in 3.7.1-5



On Mon, Oct 29, 2018 at 10:00 PM Adrian Bunk  wrote:

> Source: zeroc-ice
> Version: 3.7.1-3
> Severity: serious
> Tags: ftbfs
>
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zeroc-ice.html
>
> ...
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':test:compileJava'.
> > error: invalid source release: 1.11
>


-- 
José Gutiérrez de la Concha
ZeroC, Inc.
--- End Message ---

Bug#908681: marked as done (libsane1: pointless package rename)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 20:59:33 +
with message-id 
and subject line Bug#908681: fixed in sane-backends 1.0.27-3.1
has caused the Debian Bug report #908681,
regarding libsane1: pointless package rename
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.)


-- 
908681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsane1
Severity: serious

Hi,

libsane was renamed to libsane1 for apparently no good reason.  Renames
for library packages should be tied to ABI breakage (and associated
SONAME changes).

Either there was ABI breakage and the SONAME should be bumped (and
Provides: libsane would be wrong), or there wasn't and the package name
change ought to be reverted.

I don't know which it is, and when I asked I didn't get a clear answer,
so I'll ask again here.

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: sane-backends
Source-Version: 1.0.27-3.1

We believe that the bug you reported is fixed in the latest version of
sane-backends, 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 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated sane-backends 
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: Fri, 02 Nov 2018 20:30:06 +0100
Source: sane-backends
Binary: sane-utils libsane-common libsane libsane-dev
Architecture: source all amd64
Version: 1.0.27-3.1
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst 
Changed-By: Laurent Bigonville 
Description:
 libsane- API library for scanners
 libsane-common - API library for scanners -- documentation and support files
 libsane-dev - API development library for scanners [development files]
 sane-utils - API library for scanners -- utilities
Closes: 908681
Changes:
 sane-backends (1.0.27-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rename libsane1 back to libsane, make the renamed package provide libsane1
 (Closes: #908681)
Checksums-Sha1:
 a49151ba9d500ac77ced701ce7216c411bbcae27 2033 sane-backends_1.0.27-3.1.dsc
 9f752ca80dcde48205b1d64f55d305d77d1c8d0e 113556 
sane-backends_1.0.27-3.1.debian.tar.xz
 d25cf3d33c7268d80faf1d5a48c5509da01ebdcf 583500 
libsane-common_1.0.27-3.1_all.deb
 a0bc9fba371e4b42fa4f96217744e4b96aac1c8f 8699236 
libsane-dbgsym_1.0.27-3.1_amd64.deb
 f67eadb11bc049bf398726315e61b7f34d949fef 2135936 
libsane-dev_1.0.27-3.1_amd64.deb
 bda1380fe6d775533f9c903133393f434b414f3a 2185572 libsane_1.0.27-3.1_amd64.deb
 c762a9c7587f045e2aeee5606d21310d30e8b668 8902 
sane-backends_1.0.27-3.1_amd64.buildinfo
 c08bc93a1aff055176c1d6c6a7a5243b08e3a410 332480 
sane-utils-dbgsym_1.0.27-3.1_amd64.deb
 da7e960a0775f747135c2a644b7c72c91292e615 261172 sane-utils_1.0.27-3.1_amd64.deb
Checksums-Sha256:
 8a762d53a8aa47b3421aeba0f5f3aa61075b528032f6758ff139cdddf7d2e406 2033 
sane-backends_1.0.27-3.1.dsc
 6daa8f445e59b4823a5f754483c9f09b4f37b531eb72fb895cb1f8b74a0273c5 113556 
sane-backends_1.0.27-3.1.debian.tar.xz
 d860e3f436f9a9affd1fd02e198f25c50b17fa44af3ba14d4c0d43e7be111af5 583500 
libsane-common_1.0.27-3.1_all.deb
 3d9436d1f5f0c56b9daa4b1b4af4d13d6915951c771d69e5ed2d6130888513b0 8699236 
libsane-dbgsym_1.0.27-3.1_amd64.deb
 c0b9f9bb8113a4c4e5d63e7c941b8fc3fda21084d160662cb1be09b1376e97fd 2135936 
libsane-dev_1.0.27-3.1_amd64.deb
 34909b08ad9368af32604f023ca8f6012a46eee2985818a355b30b3d047ccd7a 2185572 
libsane_1.0.27-3.1_amd64.deb
 d5c087af64559cec8bcffa6eb55352119a2ba4fc1c1c471d87819fddaf2c1b02 8902 
sane-backends_1.0.27-3.1_amd64.buildinfo
 b7e1b71bfffda6a2abf70a610b1f1423a09d0025e26fef2b92f59498c7229b80 332480 
sane-utils-dbgsym_1.0.27-3.1_amd64.deb
 c00c3bc20dd9beda7b20a3de88cc334474fe3b10a8a5b6990228d2b73769a3a2 261172 
sane-utils_1.0.27-3.1_amd64.deb
Files:
 c2eea362ee781373957b1413d98c2990 2033 graphics optional 
sane-backends_1.0.27-3.1.dsc
 751cced67111356a460864200eb22bc4 113556 graphics optional 
sane-backends_1.0.27-3.1.debian.tar.xz
 c9e1b8286274806f5abb4d89e407e0cd 583500 libs optional 
libsane-common_1.0.27-3.1_all.deb
 bafb8ff3d4697e0b9ed8f7c1468f0e92 8699236 

Bug#912630: marked as done (haskell-lens-aeson: FTBFS on various archs)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 20:54:20 +
with message-id 
and subject line Bug#912630: fixed in haskell-lens-aeson 1.0.2-6
has caused the Debian Bug report #912630,
regarding haskell-lens-aeson: FTBFS on various archs
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.)


-- 
912630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-lens-aeson
Version: 1.0.2-5
Severity: serious
Justification: FTBFS

Hello,

It seems that haskell-lens-aeson's testsuite is failing on various
archs:

armel, armhf, i386, mipsel, hurd-i386, x32.

These look like the little-endian 32bit archs.

Samuel

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

Kernel: Linux 4.19.0 (SMP w/8 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)

-- 
Samuel
 on se croirait en cool : Some browsers close comments on the first ">" 
character, so to hide script content from such browsers, you can transpose 
operands for relational and shift operators (e.g., use "y < x" rather than "x > 
y") or use scripting language-dependent escapes for ">".
 -+- #ens-mim -+-
--- End Message ---
--- Begin Message ---
Source: haskell-lens-aeson
Source-Version: 1.0.2-6

We believe that the bug you reported is fixed in the latest version of
haskell-lens-aeson, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-lens-aeson 
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, 05 Nov 2018 22:37:16 +0200
Source: haskell-lens-aeson
Binary: libghc-lens-aeson-dev libghc-lens-aeson-prof libghc-lens-aeson-doc
Architecture: source
Version: 1.0.2-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 libghc-lens-aeson-dev -
 libghc-lens-aeson-doc -
 libghc-lens-aeson-prof -
Closes: 912630
Changes:
 haskell-lens-aeson (1.0.2-6) unstable; urgency=medium
 .
   * Backport upstream patch to fix failing tests (Closes: #912630)
Checksums-Sha1:
 65a7721beae2da5fcb1a88e2a1b4d169186d01b8 3360 haskell-lens-aeson_1.0.2-6.dsc
 78ffdabefcbc80822a18dbefd459c83b5dd4ba25 3788 
haskell-lens-aeson_1.0.2-6.debian.tar.xz
 47c9c72f7d7eebfbb0b302c6623bb9b801eabe55 11147 
haskell-lens-aeson_1.0.2-6_amd64.buildinfo
Checksums-Sha256:
 683096ff15ae38931db8f41ad563c65660656295ca4063daf3809ea4bb06f61b 3360 
haskell-lens-aeson_1.0.2-6.dsc
 6af9279e1bffa3f9ad081bf9e0de367ec4fbe0a65acf8936442e93217f8c858c 3788 
haskell-lens-aeson_1.0.2-6.debian.tar.xz
 3dae0c69168278a47d7e5a59f07b3d60e1ed2623ce45ce34f6d88d5d986e323c 11147 
haskell-lens-aeson_1.0.2-6_amd64.buildinfo
Files:
 5bc10f7fae2de7dfb631c35a5af26fbc 3360 haskell optional 
haskell-lens-aeson_1.0.2-6.dsc
 e6093ce9e753cb647748699c438a971f 3788 haskell optional 
haskell-lens-aeson_1.0.2-6.debian.tar.xz
 9387916752f50c0b470406cf72fe7225 11147 haskell optional 
haskell-lens-aeson_1.0.2-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlvgrGcUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDzpMQ/7BCYs8aJs6s+u/IXQ4fxyEKv8UUe2
eftjLEzNTG2lMKEDSKD5ruMwLq/Aq9DRajUTRg9Dr1hh4ghuBjgSDZNi1H18ENmX
ece978zq/LTqS987C3/B659nn6ROVYPX5vJiXu5rKjfnRspSEyBR6dV+SOP2EYL6
+dDBujD4XpG2TRmDqdBnHeWT+Z+7jwdOx0ibidP23fj1W+89+CSwI3P/BAquKMsN
HRz3UjmGdWAK4c6xGZaGfbIrP104qUKZ4NiwyNJgf9XyEC9Ar+3IJ4DjBOLzt6Gk
X9utdQ9ApSoDNVdf8FQqz3A7CRte6svkRPH3wo3Wdz9mTeBQHD5inSJHwfuPqbKc
cIBImWwXE7gVtiSCT9q3ny9TU7USWI/qDTOYpjwQtz7emeuudv+jixhX6OkLNZDz

Bug#912714: mistral: CVE-2018-16849: std.ssh action may disclose presence of arbitrary files

[Salvatore Bonaccorso]

Hi Thomas,

On Mon, Nov 05, 2018 at 03:52:57PM +0100, Thomas Goirand wrote:
> On 11/3/18 8:26 AM, Salvatore Bonaccorso wrote:
> > Source: mistral
> > Version: 7.0.0-1
> > Severity: grave
> > Tags: patch security upstream
> > Forwarded: https://bugs.launchpad.net/mistral/+bug/1783708
> > 
> > Hi,
> > 
> > The following vulnerability was published for mistral.
> > 
> > CVE-2018-16849[0]:
> > | A flaw was found in openstack-mistral. By manipulating the SSH private
> > | key filename, the std.ssh action can be used to disclose the presence
> > | of arbitrary files within the filesystem of the executor running the
> > | action. Since std.ssh private_key_filename can take an absolute path,
> > | it can be used to assess whether or not a file exists on the
> > | executor's filesystem.
> > 
> > If you fix the vulnerability please also make sure to include the
> > CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> > 
> > For further information see:
> > 
> > [0] https://security-tracker.debian.org/tracker/CVE-2018-16849
> > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16849
> > [1] https://bugs.launchpad.net/mistral/+bug/1783708
> > 
> > Please adjust the affected versions in the BTS as needed.
> > 
> > Regards,
> > Salvatore
> 
> Hi Salvatore,
> 
> I have fixed the package in Sid, and uploaded a fixed version at:
> http://sid.gplhost.com/stretch-proposed-updates/mistral/

Thanks, I have updated the tracker information.

> The debdiff is here:
> http://sid.gplhost.com/stretch-proposed-updates/mistral/mistral_3.0.0-4+deb9u1.debdiff
> 
> It's basically a one liner that is outputing on the log instead of
> stdout, so trivial to review. Let me know if I should upload (in which
> case, I'll need to rebuild with --force-orig-source, I believe).

The issue was determined to be not severe enough to warrant a DSA (on
its own).  Might you reschedule an update for the next (9.6 is now to
late) point release of stretch?

Thanks already!

Regards,
Salvatore

Processed: raise severity of upnp transition bugs

[Debian Bug Tracking System]

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

> severity 884243 serious
Bug #884243 [src:djmount] djmount: FTBFS against upnp 1.8
Severity set to 'serious' from 'important'
> tags 884243 ftbfs
Bug #884243 [src:djmount] djmount: FTBFS against upnp 1.8
Added tag(s) ftbfs.
> severity 884996 serious
Bug #884996 [src:amule] src:amule: FTBFS against upnp 1.8
Severity set to 'serious' from 'important'
> tags 884996 ftbfs
Bug #884996 [src:amule] src:amule: FTBFS against upnp 1.8
Added tag(s) ftbfs.
> severity 912066 serious
Bug #912066 [src:linux-igd] linux-igd: FTBFS with upnp 1.8.4
Severity set to 'serious' from 'important'
> tags 912066 ftbfs
Bug #912066 [src:linux-igd] linux-igd: FTBFS with upnp 1.8.4
Added tag(s) ftbfs.
> severity 885025 serious
Bug #885025 [src:gerbera] gerbera: FTBFS against upnp 1.8.3
Severity set to 'serious' from 'important'
> tags 885025 ftbfs
Bug #885025 [src:gerbera] gerbera: FTBFS against upnp 1.8.3
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#913005: ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack

[Salvatore Bonaccorso]

Source: ruby-rack
Version: 1.6.4-4
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for ruby-rack.

CVE-2018-16471[0]:
Possible XSS vulnerability in Rack

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16471
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16471
[1] https://www.openwall.com/lists/oss-security/2018/11/05/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#913003: ruby-rack: CVE-2018-16470: Possible DoS vulnerability in Rack

[Salvatore Bonaccorso]

Source: ruby-rack
Version: 2.0.5-1
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for ruby-rack, which is only
affecting experimental version. Filling with RC severity as the
vulernable version should not enter unstable.

CVE-2018-16470[0]:
Possible DoS vulnerability in Rack

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16470
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16470
[1] https://www.openwall.com/lists/oss-security/2018/11/05/1

Regards,
Salvatore

Processed: limit source to fontconfig, tagging 896684

[Debian Bug Tracking System]

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

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

> tags 896684 + pending
Bug #896684 [fontconfig-config] fontconfig-config: Fontconfig error: Cannot 
load config file from /etc/fonts/fonts.conf, due to many errors
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: php-defaults

[Debian Bug Tracking System]

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

> affects 912114 src:php-defaults
Bug #912114 [src:php-doctrine-data-fixtures] php-doctrine-data-fixtures FTBFS 
with PHP 7.3
Added indication that 912114 affects src:php-defaults
> thanks
Stopping processing here.

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

Processed: Re: Bug#911620: shared-mime-info,gconf2: trigger cycle during upgrade from stretch to buster

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dpkg 1.19.2
Bug #911620 [shared-mime-info,gconf2] shared-mime-info,gconf2: trigger cycle 
during upgrade from stretch to buster
Bug reassigned from package 'shared-mime-info,gconf2' to 'dpkg'.
No longer marked as found in versions shared-mime-info/1.10-1 and gconf/3.2.6-5.
Ignoring request to alter fixed versions of bug #911620 to the same values 
previously set
Bug #911620 [dpkg] shared-mime-info,gconf2: trigger cycle during upgrade from 
stretch to buster
Marked as found in versions dpkg/1.19.2.
> affects -1 shared-mime-info gconf2
Bug #911620 [dpkg] shared-mime-info,gconf2: trigger cycle during upgrade from 
stretch to buster
Added indication that 911620 affects shared-mime-info and gconf2

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

Bug#911620: shared-mime-info,gconf2: trigger cycle during upgrade from stretch to buster

[Adrian Bunk]

Control: reassign -1 dpkg 1.19.2
Control: affects -1 shared-mime-info gconf2

On Mon, Oct 22, 2018 at 07:29:33PM +0200, Andreas Beckmann wrote:
> Package: shared-mime-info,gconf2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: found -1 1.10-1
> Control: found -1 3.2.6-5
> Control: affects -1 + microhope
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch'.
> It installed fine in 'stretch', then the upgrade to 'buster' fails.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Setting up libgl1-mesa-glx:amd64 (18.1.7-1) ...
>   dpkg: cycle found while processing triggers:
>chain of packages whose triggers are or may be responsible:
> shared-mime-info -> gconf2
>packages' pending triggers which are or may be unresolvable:
> shared-mime-info: /usr/share/mime/packages
> libc-bin: ldconfig
> gconf2: /usr/share/gconf/schemas
>   dpkg: error processing package shared-mime-info (--configure):
>triggers looping, abandoned
> 
> 
> This was observed during a 2-stage upgrade from stretch to buster:
>   apt-get upgrade && apt-get dist-upgrade
> Both shared-mime-info and gconf2 were already upgraded successfully
> during the first stage.
> The package being tested was microhope.
> 
> IIRC shared-mime-info switched to no-await triggers - so this trigger
> cycle problem should have vanished...

Guillem confirmed that this looks like a trigger cycle problem in dpkg
with already existing bugs.

> cheers,
> 
> Andreas

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: found 912997 in 4.1.4-1

[Debian Bug Tracking System]

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

> found 912997 4.1.4-1
Bug #912997 [glusterfs] glusterfs: Several security vulnerabilities
There is no source info for the package 'glusterfs' at version '4.1.4-1' with 
architecture ''
Unable to make a source version for version '4.1.4-1'
Marked as found in versions 4.1.4-1.
> thanks
Stopping processing here.

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

Processed: php-defaults

[Debian Bug Tracking System]

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

> affects 911832 src:php-defaults
Bug #911832 [src:php-symfony-polyfill] php-defaults breaks php-symfony-polyfill 
autopkgtest
Added indication that 911832 affects src:php-defaults
> retitle 911832 php-symfony-polyfill: ftbfs since php 7.3 is the default
Bug #911832 [src:php-symfony-polyfill] php-defaults breaks php-symfony-polyfill 
autopkgtest
Changed Bug title to 'php-symfony-polyfill: ftbfs since php 7.3 is the default' 
from 'php-defaults breaks php-symfony-polyfill autopkgtest'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#907974: perl-doc-html: Should be updated to 5.28 at the point of the transition

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #907974 [src:perl-doc-html] perl-doc-html: Should be updated to 5.28 at the 
point of the transition
Severity set to 'serious' from 'wishlist'

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

Bug#912997: glusterfs: Several security vulnerabilities

[Markus Koschany]

Package: glusterfs
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for glusterfs.

CVE-2018-14651[0]:
| It was found that the fix for CVE-2018-10927, CVE-2018-10928,
| CVE-2018-10929, CVE-2018-10930, and CVE-2018-10926 was incomplete. A
| remote, authenticated attacker could use one of these flaws to execute
| arbitrary code, create arbitrary files, or cause denial of service on
| glusterfs server nodes via symlinks to relative paths.

CVE-2018-14652[1]:
| The Gluster file system through versions 3.12 and 4.1.4 is vulnerable
| to a buffer overflow in the 'features/index' translator via the code
| handling the 'GF_XATTR_CLRLK_CMD' xattr in the 'pl_getxattr' function.
| A remote authenticated attacker could exploit this on a mounted volume
| to cause a denial of service.

CVE-2018-14653[2]:
| The Gluster file system through versions 4.1.4 and 3.12 is vulnerable
| to a heap-based buffer overflow in the '__server_getspec' function via
| the 'gf_getspec_req' RPC message. A remote authenticated attacker
| could exploit this to cause a denial of service or other potential
| unspecified impact.

CVE-2018-14654[3]:
| The Gluster file system through version 4.1.4 is vulnerable to abuse
| of the 'features/index' translator. A remote attacker with access to
| mount volumes could exploit this via the 'GF_XATTROP_ENTRY_IN_KEY'
| xattrop to create arbitrary, empty files on the target server.

CVE-2018-14659[4]:
| The Gluster file system through versions 4.1.4 and 3.1.2 is vulnerable
| to a denial of service attack via use of the
| 'GF_XATTR_IOSTATS_DUMP_KEY' xattr. A remote, authenticated attacker
| could exploit this by mounting a Gluster volume and repeatedly calling
| 'setxattr(2)' to trigger a state dump and create an arbitrary number
| of files in the server's runtime directory.

CVE-2018-14660[5]:
| A flaw was found in glusterfs server through versions 4.1.4 and 3.1.2
| which allowed repeated usage of GF_META_LOCK_KEY xattr. A remote,
| authenticated attacker could use this flaw to create multiple locks
| for single inode by using setxattr repetitively resulting in memory
| exhaustion of glusterfs server node.

CVE-2018-14661[6]:
| It was found that usage of snprintf function in feature/locks
| translator of glusterfs server 3.8.4, as shipped with Red Hat Gluster
| Storage, was vulnerable to a format string attack. A remote,
| authenticated attacker could use this flaw to cause remote denial of
| service.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-14651
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14651
[1] https://security-tracker.debian.org/tracker/CVE-2018-14652
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14652
[2] https://security-tracker.debian.org/tracker/CVE-2018-14653
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14653
[3] https://security-tracker.debian.org/tracker/CVE-2018-14654
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14654
[4] https://security-tracker.debian.org/tracker/CVE-2018-14659
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14659
[5] https://security-tracker.debian.org/tracker/CVE-2018-14660
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14660
[6] https://security-tracker.debian.org/tracker/CVE-2018-14661
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14661

Please adjust the affected versions in the BTS as needed.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#912995: FTBFS: missing build-dep on python-packaging

[Sebastian Harl]

Package: ansible
Version: 2.7.1+dfsg-1
Severity: serious
Justification: FTBFS

Hi,

rebuilding ansible 2.7.1 fails when in a clean chroot:

make[2]: Entering directory '/build/1st/ansible-2.7.1+dfsg'
Traceback (most recent call last):
  File "packaging/release/versionhelper/version_helper.py", line 9, in 
from packaging.version import Version, VERSION_PATTERN
ImportError: No module named packaging.version
Makefile:40: *** "version_helper failed".  Stop.

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

packaging.version is provided by python-packaging.

Cheers,
Sebastian

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x2F1FFCC7 +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin



signature.asc
Description: Digital signature

Processed: Re: boost1.67: for loops without set -e

[Debian Bug Tracking System]

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

> severity 912910 wishlist
Bug #912910 [src:boost1.67] boost1.67: for loops without set -e
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.

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

Bug#912910: boost1.67: for loops without set -e

[Dimitri John Ledkov]

severity 912910 wishlist
thanks

On Sun, 4 Nov 2018 21:36:14 +0100 Mattia Rizzolo  wrote:
> Source: boost1.67
> Version: 1.67.0-9
> Severity: serious
> Control: clone -1 -2 boost1.62 1.62.0+dfsg-10
> Control: retitle -2 boost1.62: for loops without set -e
> Justification: Policy §4.6
>
>
> Hi boost maintainers,
>
> I've noticed that your for loops in your rules files are buggy.
> This things:
>
> for pyver in $(pyversions); do \
> echo "Building Boost.Python for python version $$pyver"; \
> $(JAM) --build-dir=build-$$pyver --stagedir=stage-$$pyver 
> --user-config=$(CURDIR)/user-config-$$pyver.jam --with-python --with-mpi 
> python=$$pyver; \
> done
>
> is buggy, as it wouldn't cause a build failure in the instance $(JAM)
> failed.

This is intentional, such that when new pythons are added as supported
the build doesn't fail, as it is typical that adjustments are needed.

I do not believe this is in fact serious. As the build does error out
eventually, if none of the pythons managed to build.

I am planning to change this a bit, such that the default first build
is done with the default python3 enabled. Such that only python2 /
other supported python3s may fail to compile.

I don't believe this is serious at all.

Are you working on testing python3.8 or some such and noticed lack of compat?

Regards,

Dimitri.

Bug#912916: mysql-connector-java: CVE-2018-3258: allows low privileged attacker to compromise it

[Markus Koschany]

Am 05.11.18 um 14:13 schrieb Moritz Mühlenhoff:
[...]
> The Java connector follows the horrible Oracle policy of not disclosing
> vulnerability information. Given that we now have mariadb-connector-java
> in the archive (with a transparent upstream), can we migrate existing
> reverse deps towards libmariadb-java and simply get rid of libmysql-java?
> 
> List of buils deps is rather short:
> 
> jabref
> pegasus-wms
> jython
> osmosis
> netbeans
> igv (non-free)

I agree it would be nice if we could replace mysql-connector-java with
the MariaDB version. I don't know how much effort is required to make
the switch, hopefully it is just a drop-in-replacement. I think we
should file bugs and let's see how it goes. I can do that.

There are a few more r-deps for libmysql-java

apt-cache rdepends libmysql-java

Reverse Depends:
  jabref
  solr-common
 |sqlline
  pegasus-wms
  osmosis
  libnb-ide14-java
  solr-common
 |libreoffice-canzeley-client
  libreoffice-base-drivers
  jython
  jclic
  jameica



signature.asc
Description: OpenPGP digital signature

Bug#912713: marked as done (Incorrect filename for jquery-ui makes rdm test server not work properly)

[Debian Bug Tracking System]

Your message dated Mon, 5 Nov 2018 16:33:58 +0100
with message-id <20181105153358.gb6...@grep.be>
and subject line Re: done in unstable
has caused the Debian Bug report #912713,
regarding Incorrect filename for jquery-ui makes rdm test server not work 
properly
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.)


-- 
912713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ola-rdm-tests
Version: 0.10.3.nojsmin-2
Severity: serious

The replacement of the jquery-ui code by the Debian-packaged version was
done incorrectly; as a result, jquery-ui is not found by the rdm test
server's HTML interface. This means that nothing works the way it
should.
--- End Message ---
--- Begin Message ---
Version: 0.10.5.nojsmin-3

On Mon, Nov 05, 2018 at 03:42:01PM +0100, Ivo De Decker wrote:
> Hi Wouter,
> 
> On Sat, Nov 03, 2018 at 10:10:45AM +0100, Wouter Verhelst wrote:
> > Date: Sat, 3 Nov 2018 10:10:45 +0100
> > From: Wouter Verhelst 
> > To: 912713-d...@bugs.debian.org
> > Subject: done in unstable
> > 
> > Version: 0.10.3.nojsmin-3
> > 
> > This bug does not exist in any package since that version.
> 
> Could you check which version fixes the issue? It seems there was no
> 0.10.3.nojsmin-3, so the BTS still thinks this bug affects tesitng and
> unstable.

Whoops, I typo'ed that. Copy/pasted this time ;-)

-- 
To the thief who stole my anti-depressants: I hope you're happy

  -- seen somewhere on the Internet on a photo of a billboard--- End Message ---

Bug#909442: marked as done (outguess: FTBFS in some architectures)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 14:58:03 +
with message-id 
and subject line Bug#909442: fixed in outguess 1:0.2+dfsg.1-3
has caused the Debian Bug report #909442,
regarding outguess: FTBFS in some architectures
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.)


-- 
909442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: outguess
Version: 0.2+dfsg.1-1
Severity: grave
Tags: upstream
Justification: renders package unusable

outguess is causing a FTBFS in experimental[1] for amd64, arm64, ppc64el,
powerpc and ppc64. It is a consequence of the changes to try solve #882538.

[1] https://buildd.debian.org/status/package.php?p=outguess=experimental

Regards,

Eriberto
--- End Message ---
--- Begin Message ---
Source: outguess
Source-Version: 1:0.2+dfsg.1-3

We believe that the bug you reported is fixed in the latest version of
outguess, 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 909...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated outguess 
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, 05 Nov 2018 11:11:37 -0200
Source: outguess
Binary: outguess
Architecture: source
Version: 1:0.2+dfsg.1-3
Distribution: experimental
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Joao Eriberto Mota Filho 
Description:
 outguess   - universal steganographic tool
Closes: 909442
Changes:
 outguess (1:0.2+dfsg.1-3) experimental; urgency=medium
 .
   * debian/patches/:
   - 60_generate-configure.patch: changed to use makefile.ansi instead of
 makefile.unix to fix a FTBFS in some architectures. Thanks to Frédéric
 Bonnard . (Closes: #909442)
   - 70_fix-parallel-build.patch: dropped. Thanks to Frédéric
 Bonnard .
Checksums-Sha1:
 0708add3bff3fabfb7ca5212c6b99bb7c1b65d6c 2002 outguess_0.2+dfsg.1-3.dsc
 dec02d460b65c9690009abbbedc218ef65a30645 26968 
outguess_0.2+dfsg.1-3.debian.tar.xz
 0623be1d1a842f5141f2f1e2af2c435ae634d38b 5053 
outguess_0.2+dfsg.1-3_source.buildinfo
Checksums-Sha256:
 0d6a48c074143a8d401ef273f86071628eac9b54a19c5750459912699287b2e4 2002 
outguess_0.2+dfsg.1-3.dsc
 defc591d4aa85034a2555ba21b5f47750252f3de29dfd1a81a97f63e35b4b44b 26968 
outguess_0.2+dfsg.1-3.debian.tar.xz
 e49b39797bbfdd5dfe25001722f3636ebad229966013f1a18abe1367269e47ea 5053 
outguess_0.2+dfsg.1-3_source.buildinfo
Files:
 f22a4fba21dc5b1b8e8161546ee0750c 2002 utils optional outguess_0.2+dfsg.1-3.dsc
 eca325dd5eeacc718e64a6fe689b0596 26968 utils optional 
outguess_0.2+dfsg.1-3.debian.tar.xz
 09f8115e114602394089b46c09992ff9 5053 utils optional 
outguess_0.2+dfsg.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlvgSBUACgkQ3mO5xwTr
6e+jfg/+NnC9ALKEFKWdh/9SrnN1XXHVD4RuxS8JprndgaPSIQoNCwTGexLZE23K
1KBAlmn8Z+06+ML14HtG5T+OA6MZO6uIVdSyDobILcGwjb8Nn+D8UgukMzkkhOY8
uM5zn+VHtwY9E6eP6A3rhcRDs1wpVakZoVUHNzbUbt36QFryVTUgn/Qwe49Wl8DI
zCQx9CFDqH8Am+GrX6xUnfT/O+arzuWUlikZJWDJOLdZRYu3eJMKDSjkhDCYrYPT
5o0BGHgbVkVcZdVZFeZiqYgSeZC7QIF1iyciHM2q70XBeD+iFygjMib0qwBmeyw/
KvUkMlJxioW8ZNCnKjPfXI6ltbKdYqaCxEJ2HVBXKNII8RJo3WZIvtILkPy8gDRl
ytaBhPQZZCOj6uhmfHv0PubVGkyU3dk7D2wtEPIBd/pwaDHgWCioDelaE5zNyqKe
Hj00dVEiX2gcuubjiiZhtsCrMy7fPBhulkYRO89TRl82r0mHrqIjQtF+FCrE+qcm
ScyEChFhI6fsmLAW5/GHeCPxOkMRz7/MCIDgvET8/w9OY88HQsdGn5V26ZFOBzfc
RLavCURvQhTgH+QrWThDJmNIqsH/1yYuh6Fc4euCHOYh53JD6QlbxJvoj25UhozM
jWT94YX4/dB18gns/T9ipNILQaI0H6oQoSd4GMl5A+vGkatgad0=
=QjCc
-END PGP SIGNATURE End Message ---

Bug#912714: marked as done (mistral: CVE-2018-16849: std.ssh action may disclose presence of arbitrary files)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 14:57:56 +
with message-id 
and subject line Bug#912714: fixed in mistral 7.0.0-2
has caused the Debian Bug report #912714,
regarding mistral: CVE-2018-16849: std.ssh action may disclose presence of 
arbitrary files
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.)


-- 
912714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mistral
Version: 7.0.0-1
Severity: grave
Tags: patch security upstream
Forwarded: https://bugs.launchpad.net/mistral/+bug/1783708

Hi,

The following vulnerability was published for mistral.

CVE-2018-16849[0]:
| A flaw was found in openstack-mistral. By manipulating the SSH private
| key filename, the std.ssh action can be used to disclose the presence
| of arbitrary files within the filesystem of the executor running the
| action. Since std.ssh private_key_filename can take an absolute path,
| it can be used to assess whether or not a file exists on the
| executor's filesystem.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16849
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16849
[1] https://bugs.launchpad.net/mistral/+bug/1783708

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mistral
Source-Version: 7.0.0-2

We believe that the bug you reported is fixed in the latest version of
mistral, 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 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated mistral 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: Mon, 05 Nov 2018 15:32:27 +0100
Source: mistral
Binary: mistral-api mistral-common mistral-engine mistral-event-engine 
mistral-executor python3-mistral
Architecture: source all
Version: 7.0.0-2
Distribution: unstable
Urgency: high
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 mistral-api - OpenStack Workflow service - API
 mistral-common - OpenStack Workflow service - common files
 mistral-engine - OpenStack Workflow service - Engine
 mistral-event-engine - OpenStack Workflow service - Event Engine
 mistral-executor - OpenStack Workflow service - Executor
 python3-mistral - OpenStack Workflow Service - Python libraries
Closes: 912714
Changes:
 mistral (7.0.0-2) unstable; urgency=high
 .
   * CVE-2018-16849: add upstream patch "remove extra information from std.ssh
 action" (Closes: #912714).
Checksums-Sha1:
 690b36aaef4d1ea65208fbcee8438161023450e0 4599 mistral_7.0.0-2.dsc
 9ad0f4e39fc710978bef6938aaef6ecc88c237f9 7372 mistral_7.0.0-2.debian.tar.xz
 a9a0c15b7d9e20753b99aee25a1a8f78cb3d2823 20672 mistral-api_7.0.0-2_all.deb
 76ae067852d749165dd3806de171a49f8cc284ca 38984 mistral-common_7.0.0-2_all.deb
 7164356359e3b5974ef1c82f59d7a905eb8340ab 7288 mistral-engine_7.0.0-2_all.deb
 90534926575e6215630e74eb097d12764e8c6093 7328 
mistral-event-engine_7.0.0-2_all.deb
 4495271f8be9e83b44cab0ce6a299c8c69e0da9f 7284 mistral-executor_7.0.0-2_all.deb
 ee8166f3282c875094999c4dca7bfbdf185958f7 17272 mistral_7.0.0-2_amd64.buildinfo
 bf296a24275b67dca154314bcfbead0e3317491e 280060 python3-mistral_7.0.0-2_all.deb
Checksums-Sha256:
 d673e99a12949ce23a87a4628e739be91e8b6ea1983686f669a1b6734bb20218 4599 
mistral_7.0.0-2.dsc
 83ddd3dcfa9ba068da4427a8b045a9ba8adea7eac06489832f81b388d174cbdd 7372 
mistral_7.0.0-2.debian.tar.xz
 aef0f6aa27543d2167aff15350b3d506ba286e33d478c54f83d9e95a0617f14d 20672 
mistral-api_7.0.0-2_all.deb
 73f8d636b351d91ae437deca711f822a61dbfbda64fb58349d2e7706d44bb148 38984 
mistral-common_7.0.0-2_all.deb
 d50a38f7a04652b9d6b493eaebb6524f530db5616e0163e9c1514aa426ceab90 7288 
mistral-engine_7.0.0-2_all.deb
 ac7cdcd697bc927a4ead0796fb0e65aea2d811ef2f8c73ee1b0dfe8cbbf3483b 7328 
mistral-event-engine_7.0.0-2_all.deb
 dad5b3d88ce6b943aae9cb28aea655fcffd23c95945c353282fee2eb2ed2afd2 7284 

Bug#911947: marked as done (glance FTBFS: tests fail: RecursionError: maximum recursion depth exceeded while calling a Python object)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 14:55:09 +
with message-id 
and subject line Bug#911947: fixed in glance 2:17.0.0-3
has caused the Debian Bug report #911947,
regarding glance FTBFS: tests fail: RecursionError: maximum recursion depth 
exceeded while calling a Python object
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.)


-- 
911947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glance
Version: 2:17.0.0-2
Severity: serious
Tags: ftbfs

glance fails to build from source in unstable. It has many test
failures. A fair number of "RecursionError: maximum recursion depth
exceeded while calling a Python object" are among them. See e.g.:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/glance_17.0.0-2.rbuild.log.gz

Most include this:

|   File "/build/1st/glance-17.0.0/glance/domain/__init__.py", line 316, in keys
| return dict(self).keys()
|   File "/build/1st/glance-17.0.0/glance/domain/__init__.py", line 316, in keys
| return dict(self).keys()
|   File "/build/1st/glance-17.0.0/glance/domain/__init__.py", line 316, in keys
| return dict(self).keys()
| RecursionError: maximum recursion depth exceeded while calling a Python object

Helmut
--- End Message ---
--- Begin Message ---
Source: glance
Source-Version: 2:17.0.0-3

We believe that the bug you reported is fixed in the latest version of
glance, 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 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated glance 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: Mon, 05 Nov 2018 10:54:12 +0100
Source: glance
Binary: glance glance-api glance-common glance-doc glance-registry 
python3-glance
Architecture: source all
Version: 2:17.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 glance - OpenStack Image Registry and Delivery Service - Daemons
 glance-api - OpenStack Image Registry and Delivery Service - API server
 glance-common - OpenStack Image Registry and Delivery Service - common files
 glance-doc - OpenStack Image Registry and Delivery Service - Documentation
 glance-registry - OpenStack Image Registry and Delivery Service - registry 
server
 python3-glance - OpenStack Image Registry and Delivery Service - Python library
Closes: 911947
Changes:
 glance (2:17.0.0-3) unstable; urgency=medium
 .
   * Add fix-never-ending-recursion-in-py3.7.1.patch (Closes: #911947).
Checksums-Sha1:
 b60ea8cd8deecac9a955002eacee4ac20c5ed3a0 4014 glance_17.0.0-3.dsc
 ca8d15383f1eda7528e2d78d8aecc2fcf7ea12e9 20348 glance_17.0.0-3.debian.tar.xz
 c30c59b2640190a364e41031cc593680af2466b7 40708 glance-api_17.0.0-3_all.deb
 bd75999a61543b7872a05d24fb4264dec149df45 91496 glance-common_17.0.0-3_all.deb
 d2537ec784b1e7e5a8291997ff3a90826ba3eb82 2272344 glance-doc_17.0.0-3_all.deb
 d40ce12dccd5545307379e8fcf918b8a27c1dd17 16116 glance-registry_17.0.0-3_all.deb
 488d26218ba4683545b2981c9cdd853fe060dbb7 11008 glance_17.0.0-3_all.deb
 2fcd3e807126b3e431185e0240acba91870a723b 16390 glance_17.0.0-3_amd64.buildinfo
 14c49bf4de6b8fa8ee35d2397d3002a076e54f33 388324 python3-glance_17.0.0-3_all.deb
Checksums-Sha256:
 bf081b17bff4da26a09bd10ddca9223b19f260545dc003b460e009f8954380c0 4014 
glance_17.0.0-3.dsc
 4a6e8fb35363272d0ad761f05c5cbf7bfa490de5de62fcb1f8f88294fb75a728 20348 
glance_17.0.0-3.debian.tar.xz
 ca25cf2aa4244ae9ed50da3524df163790859779c4647676412fc31cc5a8cf90 40708 
glance-api_17.0.0-3_all.deb
 3eda34abd672ffd028e70255a5f6f9a8812b7be41bec392cc08cd3f226ba72be 91496 
glance-common_17.0.0-3_all.deb
 05722c6aa66bc5f90875c1e4f3d3e3b8a5708fb42428df2bf27ec27395ea8553 2272344 
glance-doc_17.0.0-3_all.deb
 ea450e15a2f5fddd82505ad5bd03c98e71f85f14d998652f7f61c2da2ab21b3e 16116 
glance-registry_17.0.0-3_all.deb
 777d2ae4103e3d3989cdd738aa5e23f9a46408a269f1fb4b4e99062ad9212e9b 11008 
glance_17.0.0-3_all.deb
 f2b33b8041b2f06e7735a72d3a397a6bcd91342bd9d021ebac46e55e89b2c8e7 16390 
glance_17.0.0-3_amd64.buildinfo
 

Bug#912714: mistral: CVE-2018-16849: std.ssh action may disclose presence of arbitrary files

[Thomas Goirand]

On 11/3/18 8:26 AM, Salvatore Bonaccorso wrote:
> Source: mistral
> Version: 7.0.0-1
> Severity: grave
> Tags: patch security upstream
> Forwarded: https://bugs.launchpad.net/mistral/+bug/1783708
> 
> Hi,
> 
> The following vulnerability was published for mistral.
> 
> CVE-2018-16849[0]:
> | A flaw was found in openstack-mistral. By manipulating the SSH private
> | key filename, the std.ssh action can be used to disclose the presence
> | of arbitrary files within the filesystem of the executor running the
> | action. Since std.ssh private_key_filename can take an absolute path,
> | it can be used to assess whether or not a file exists on the
> | executor's filesystem.
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2018-16849
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16849
> [1] https://bugs.launchpad.net/mistral/+bug/1783708
> 
> Please adjust the affected versions in the BTS as needed.
> 
> Regards,
> Salvatore

Hi Salvatore,

I have fixed the package in Sid, and uploaded a fixed version at:
http://sid.gplhost.com/stretch-proposed-updates/mistral/

The debdiff is here:
http://sid.gplhost.com/stretch-proposed-updates/mistral/mistral_3.0.0-4+deb9u1.debdiff

It's basically a one liner that is outputing on the log instead of
stdout, so trivial to review. Let me know if I should upload (in which
case, I'll need to rebuild with --force-orig-source, I believe).

Cheers,

Thomas Goirand (zigo)

Bug#912713: done in unstable

[Ivo De Decker]

Hi Wouter,

On Sat, Nov 03, 2018 at 10:10:45AM +0100, Wouter Verhelst wrote:
> Date: Sat, 3 Nov 2018 10:10:45 +0100
> From: Wouter Verhelst 
> To: 912713-d...@bugs.debian.org
> Subject: done in unstable
> 
> Version: 0.10.3.nojsmin-3
> 
> This bug does not exist in any package since that version.

Could you check which version fixes the issue? It seems there was no
0.10.3.nojsmin-3, so the BTS still thinks this bug affects tesitng and
unstable.

Cheers,

Ivo

Bug#912714: Bug #912714 in mistral marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #912714 in mistral 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/openstack-team/services/mistral/commit/da953cf769defe9115dd93706047ab48ce0c6ecc


  * CVE-2018-16849: add upstream patch "remove extra information from std.ssh
action" (Closes: #912714).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912714

Processed: Bug #912714 in mistral marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912714 [src:mistral] mistral: CVE-2018-16849: std.ssh action may disclose 
presence of arbitrary files
Ignoring request to alter tags of bug #912714 to the same tags previously set

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

Processed: Bug #911947 in glance marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #911947 [src:glance] glance FTBFS: tests fail: RecursionError: maximum 
recursion depth exceeded while calling a Python object
Added tag(s) pending.

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

Bug#911947: Bug #911947 in glance marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #911947 in glance 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/openstack-team/services/glance/commit/4d14b088177a43006339863470c0d685a3227930


Add fix-never-ending-recursion-in-py3.7.1.patch (Closes: #911947).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/911947

Bug#912814: Messes up newsreader cache and history

[vitaminx]

On Mon, Nov 05, 2018 at 03:35:44PM +0800, Yangfl wrote:
> On Sun, 4 Nov 2018 00:10:16 +0100 vitaminx  wrote:
> > Package: wallstreet
> > Version: 1.14-1
> > Severity: grave
> >
> > I just installed this package out of curiosity and found that it messes up 
> > my newsreader's cache (I'm using newsbeuter).
> > All downloaded newsfeeds are completely gone and everything new appears as 
> > unread.
> >
> Not using any newsreader so can't figure out why. Any suggestion?
> 
> The command wallstreet invokes is `newsbeuter -r -C
> /usr/share/wallstreet/newsbeuter.config -u
> /usr/share/wallstreet/newsbeuter.urls`
> 
> Thanks

I don't know how to work around this, it just seems that newsbeuter uses a 
single cache location even with a different config file - which then is lost 
when you change the feed URLs.

Bug#859784: Bug #859784: validns: Please migrate to openssl1.1 in Buster

[Joost van Baal-Ilić]

Hi,

FWIW, this work:

> validns (0.8+git20170804-1) unstable; urgency=medium
> 
>   * Upstream fix for https://github.com/tobez/validns/issues/66 RSIG(CAA).
> 
>  -- Casper Gielen Fri, 04 Aug 2017 10:52:03 +0200
> 
> validns (0.8+git20170801-2) unstable; urgency=medium
> 
>   * Switch to openssl1.1, patch by Sebastian Andrzej Siewior (Closes: 859784).
> 
>  -- Casper Gielen   Wed, 02 Aug 2017 17:46:03 +0200
> 
> validns (0.8+git20170801-1) unstable; urgency=medium
> 
>   * New upstream with support for AAC, CDS, CDNSKEY, SMIMEA resource records.
>   * debian/control Allow both ssl1.0 and ssl1.1 for backwards compatibiltiy.
>   * debian/control Upgrade to Standards-Version 4.0.0 (no changes).
> 
>  -- Casper Gielen   Tue, 01 Aug 2017 16:52:23 +0200
> 
> validns (0.8+git20160720-3) unstable; urgency=medium
> 
>   * debian/copyright Add License: statement.
>   * debian/control Upgrade to Standards-Version 3.9.8 (no changes).
> 
>  -- Casper Gielen   Wed, 14 Dec 2016 16:01:55 +0100
> 
> validns (0.8+git20160720-2) unstable; urgency=medium
> 
>   * Depend on OpenSSL 1.0 (Closes: #828591)
> 
>  -- Casper Gielen   Thu, 01 Dec 2016 14:51:30 +0100
> 
> validns (0.8+git20160720-1) stable; urgency=medium
> 
>   * New upstream with support for INCLUDE.
> 
>  -- Casper Gielen   Wed, 20 Jul 2016 11:27:36 +0200

is available from
https://non-gnu.uvt.nl/debian/stretch/validns/validns_0.8+git20170804-1.dsc .
I _*might*_ have time to merge this back with what's in the Debian archive,
before the freeze.

HTH, Bye,

Joost

Bug#909442: outguess: patch for #909442

[Eriberto]

Thanks a lot! Uploading!


Em seg, 5 de nov de 2018 às 09:23, Frédéric Bonnard
 escreveu:
>
> Hi Eriberto,
> here is a new merge request :
> https://salsa.debian.org/pkg-security-team/outguess/merge_requests/3
>
> Here is the details from the commit message for better clarity in this
> bug :
>
> Due to the changes brought with 70_fix-parallel-build.patch, all builds
> but arm64 worked. Arm64 build failed because of ans2knr executable
> producing random wrong prototypes. I saw this was due to an unsafe use
> of strcpy that most of the time works but not on arm64. Actually,
> conversion of ansi to knr standard is not necessary as cc is ansi. So we
> can :
> - use the ansi build makefile
> - get of rid the parallel build fix that is needed only in the
>   unix build because of ansi2knr use, which we avoid in the ansi build
>
> I tried this change on a few architectures, but can't test it on a broad
> range of architectures, so I just hope that this will build properly on
> all archs this time. I feel confident as it worked well on arm64 and all
> other archs already built in knr style and it should work in ansi too.
>
> F.
>
> On Fri, 2 Nov 2018 19:43:20 -0300, Eriberto  wrote:
> > Em qua, 31 de out de 2018 às 06:33, Frédéric Bonnard
> >  escreveu:
> > >
> > > Hi Eriberto,
> > >
> > > the errors you see in the builds of 2018-10-29 are the same issues : I
> > > initially tried to reproduce the bug but failed, so I asked a give back.
> > > The new errors you see just occurred during that rebuild but are not
> > > different issues.
> > > So the merge request I sent should fix all the errors on amd64 and power
> > > arches.
> > >
> > > F.
> >
> >
> > Yeap! Thanks. I uploaded to experimental few days ago[1].
> >
> > [1] 
> > https://buildd.debian.org/status/package.php?p=outguess=experimental
> >
> > Now, arm64 fails, so I can't upload to unstable. Do you think that it
> > is a new issue from makefile.unix?
> >
> > Cheers,
> >
> > Eriberto
> >

Bug#912714: Bug #912714 in mistral marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #912714 in mistral 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/openstack-team/services/mistral/commit/3775850e20befca2286969df3d221bb6cbc52738


  * CVE-2018-16849: std.ssh action may disclose presence of arbitrary files,
applied upstream patch: remove extra information from std.ssh action.
(Closes: #912714).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912714

Processed: Bug #912714 in mistral marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912714 [src:mistral] mistral: CVE-2018-16849: std.ssh action may disclose 
presence of arbitrary files
Added tag(s) pending.

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

Bug#912714: Bug #912714 in mistral marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #912714 in mistral 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/openstack-team/services/mistral/commit/a9ed372faad22ce141fc7b8d765888553ccad0e8


  * CVE-2018-16849: std.ssh action may disclose presence of arbitrary files,
applied upstream patch: remove extra information from std.ssh action.
(Closes: #912714).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912714

Processed: Bug #912714 in mistral marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912714 [src:mistral] mistral: CVE-2018-16849: std.ssh action may disclose 
presence of arbitrary files
Ignoring request to alter tags of bug #912714 to the same tags previously set

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

Bug#912916: mysql-connector-java: CVE-2018-3258: allows low privileged attacker to compromise it

[Moritz Mühlenhoff]

On Sun, Nov 04, 2018 at 10:35:42PM +0100, Markus Koschany wrote:
> Package: mysql-connector-java
> X-Debbugs-CC: t...@security.debian.org
> Severity: grave
> Tags: security
> 
> Hi,
> 
> The following vulnerability was published for mysql-connector-java.
> 
> CVE-2018-3258[0]:
> | Vulnerability in the MySQL Connectors component of Oracle MySQL
> | (subcomponent: Connector/J). Supported versions that are affected are
> | 8.0.12 and prior. Easily exploitable vulnerability allows low
> | privileged attacker with network access via multiple protocols to
> | compromise MySQL Connectors. Successful attacks of this vulnerability
> | can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.8
> | (Confidentiality, Integrity and Availability impacts). CVSS Vector:
> | (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

The Java connector follows the horrible Oracle policy of not disclosing
vulnerability information. Given that we now have mariadb-connector-java
in the archive (with a transparent upstream), can we migrate existing
reverse deps towards libmariadb-java and simply get rid of libmysql-java?

List of buils deps is rather short:

jabref
pegasus-wms
jython
osmosis
netbeans
igv (non-free)

Cheers,
Moritz

Bug#909442: Bug #909442 in outguess marked as pending

[Joao Eriberto Mota Filho]

Control: tag -1 pending

Hello,

Bug #909442 in outguess 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/pkg-security-team/outguess/commit/adc581f472202381f05e897a96b3bc476b440365


Switch to ansi build (Closes: #909442)

Due to the changes brought with 70_fix-parallel-build.patch, all builds
but arm64 worked. Arm64 build failed because of ans2knr executable
producing random wrong prototypes. I saw this was due to an unsafe use of
strcpy that most of the time works but not on arm64.
Actually, conversion of ansi to knr standard is not necessary as cc is
ansi. So we can :
- use the ansi build makefile
- get of rid the parallel build fix that is needed only in the unix
build because of ansi2knr use, which we avoid in the ansi build



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909442

Bug#909442: Bug #909442 in outguess marked as pending

[Joao Eriberto Mota Filho]

Control: tag -1 pending

Hello,

Bug #909442 in outguess 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/pkg-security-team/outguess/commit/623bd69c98ff1422269442513b55d2468f016e6d


Merge branch 'ansi-build' into 'debian/master'

Switch to ansi build (Closes: #909442)

See merge request pkg-security-team/outguess!3


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909442

Processed: Bug #909442 in outguess marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909442 [outguess] outguess: FTBFS in some architectures
Ignoring request to alter tags of bug #909442 to the same tags previously set

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

Processed: Bug #909442 in outguess marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909442 [outguess] outguess: FTBFS in some architectures
Ignoring request to alter tags of bug #909442 to the same tags previously set

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

Bug#899801: marked as done (php-facedetect: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:49:57 +
with message-id 
and subject line Bug#899801: fixed in php-facedetect 1.1.0+git20170801-2
has caused the Debian Bug report #899801,
regarding php-facedetect: Invalid maintainer address 
pkg-php-p...@lists.alioth.debian.org
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.)


-- 
899801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php-facedetect
Version: 1.1.0+git20170801-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of php-facedetect,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package php-facedetect since the list address
pkg-php-p...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-php-p...@lists.alioth.debian.org is 35.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: php-facedetect
Source-Version: 1.1.0+git20170801-2

We believe that the bug you reported is fixed in the latest version of
php-facedetect, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathieu Parent  (supplier of updated php-facedetect 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: Mon, 05 Nov 2018 13:13:13 +0100
Source: php-facedetect
Binary: php-facedetect
Architecture: source amd64
Version: 1.1.0+git20170801-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Mathieu Parent 
Description:
 php-facedetect - Detect faces with PHP
Closes: 899801
Changes:
 php-facedetect (1.1.0+git20170801-2) unstable; urgency=medium
 .
   * Standards-Version: 4.2.1
   * Update debhelper compat from 9 to 11
   * Package moved to salsa
   * Use secure copyright format URI
   * Update maintainer email to team+php-p...@tracker.debian.org
 (Closes: #899801)
Checksums-Sha1:
 fc5a19b2e29c5b9baac4286422d5de9e30802231 2095 
php-facedetect_1.1.0+git20170801-2.dsc
 314f5a7e95999a0845d158d0f7018b5043ab09e3 2812 
php-facedetect_1.1.0+git20170801-2.debian.tar.xz
 95cbd4dd98ac464f0965d0c2a79c4ebc1d607338 27036 
php-facedetect-dbgsym_1.1.0+git20170801-2_amd64.deb
 8a2e4e16414a40ad1b1eedbf6c7569961fe53743 17402 
php-facedetect_1.1.0+git20170801-2_amd64.buildinfo
 cab4f0a870e91641f5cd080d0c3b80cc0a5dc96b 7316 
php-facedetect_1.1.0+git20170801-2_amd64.deb
Checksums-Sha256:
 6fa83b5062e98e6b7d7b307cdc19d9b9cd779522f1dd229fd551c85cf5270d10 2095 

Bug#912593: sagemath has unfulfillable build-dependencies

[Tobias Hansen]

Control: tags -1 + pending

This bug is easy enough to fix, however it doesn't make sense to upload a new 
version at the moment due to #912980.

debian/control is in .gitignore because it is generated in debian/rules from 
debian/control.in, mostly to avoid writing the control fields for all the 
documentation packages in different languages.

Best,
Tobias

On 11/02/2018 09:59 AM, Graham Inggs wrote:
> Control: tags -1 + ftbfs
>
> Hi Maintainers
>
> This causes reproducible builds of sagemath [1] to FTBFS (depwait) currently.
> BTW, it seems really odd to me to have /control in /debian/.gitignore [2].
>
> Regards
> Graham
>
> [1] https://tests.reproducible-builds.org/debian/history/amd64/sagemath.html
> [2] 
> https://salsa.debian.org/science-team/sagemath/blob/master/debian/.gitignore
>

Processed: Re: Bug#912593: sagemath has unfulfillable build-dependencies

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #912593 [src:sagemath] sagemath has unfulfillable build-dependencies
Added tag(s) pending.

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

Bug#912924: classy-prelude-yesod: not worth maintenance burden?

[Clint Adams]

On Mon, Nov 05, 2018 at 10:04:52AM +0100, Mattia Rizzolo wrote:
> you typoed the package name here… reassigning.

Thanks

Bug#912980: sagemath is incompatible with GAP 4.9

[Tobias Hansen]

Package: src:sagemath
Version: 8.4-2
Severity: serious
Tags: sid buster
Control: forwarded -1 https://trac.sagemath.org/ticket/22626
Control: block -1 by 912862

gap 4.9.3 was recently uploaded to Debian unstable. sagemath is not yet 
compatible to this version, see upstream bug.

Processed: sagemath is incompatible with GAP 4.9

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://trac.sagemath.org/ticket/22626
Bug #912980 [src:sagemath] sagemath is incompatible with GAP 4.9
Set Bug forwarded-to-address to 'https://trac.sagemath.org/ticket/22626'.
> block -1 by 912862
Bug #912980 [src:sagemath] sagemath is incompatible with GAP 4.9
912980 was not blocked by any bugs.
912980 was not blocking any bugs.
Added blocking bug(s) of 912980: 912862

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

Processed: Bug #899801 in php-facedetect marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #899801 [src:php-facedetect] php-facedetect: Invalid maintainer address 
pkg-php-p...@lists.alioth.debian.org
Added tag(s) pending.

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

Bug#899801: Bug #899801 in php-facedetect marked as pending

[Mathieu Parent]

Control: tag -1 pending

Hello,

Bug #899801 in php-facedetect 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/php-team/pecl/php-facedetect/commit/dc5e1d83ffd63f52bd381e4a12ba938d13938df0


Update maintainer email to team+php-p...@tracker.debian.org (Closes: #899801)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/899801

Bug#893992: marked as done (xfreerdp: command line syntax not documented, matches neither manpage nor usage)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:19:58 +
with message-id 
and subject line Bug#896780: Removed package(s) from unstable
has caused the Debian Bug report #893992,
regarding xfreerdp: command line syntax not documented, matches neither manpage 
nor usage
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.)


-- 
893992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freerdp-x11
Version: 1.1.0~git20140921.1.440916e+dfsg1-15
Severity: grave
Justification: renders package unusable

SYNOPSIS
   xfreerdp [file] [options] [/v:server[:port]]
[…]
OPTIONS
   /v [:port]
   Server hostname
[…]
   /rfx
   RemoteFX
[…]

Hmm. Okay, let’s try it. Even though the manpage in itself
is unsure whether there has to be a colon after the /v or not.

tglase@tglase-nb:~ $ xfreerdp /v 172.26.3.108 /w 1000 /h 768 /multimedia /rfx
WARNING: Using deprecated command-line interface!
/rfx -> /v:/rfx
connect: No such file or directory
Error: protocol security negotiation or connection failure
131|tglase@tglase-nb:~ $ xfreerdp  /w 1000 /h 768 /multimedia /rfx /v 
172.26.3.108
error: server hostname was not specified with /v:[:port]
tglase@tglase-nb:~ $ xfreerdp  /w 1000 /h 768 /multimedia /rfx /v:172.26.3.108
WARNING: Using deprecated command-line interface!
/v -> /v:/v /port:172
connect: No such file or directory
Error: protocol security negotiation or connection failure

So… how *do* I actually use this thing? I was just trying
to demonstrate xrdp, but with rdesktop, video playback is
lagging a bit, and Nik always said xfreerdp can do RFX and
make it fast.

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

Kernel: Linux 4.15.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages freerdp-x11 depends on:
ii  libc6 2.27-2
ii  libfreerdp-cache1.1   1.1.0~git20140921.1.440916e+dfsg1-15
ii  libfreerdp-client1.1  1.1.0~git20140921.1.440916e+dfsg1-15
ii  libfreerdp-codec1.1   1.1.0~git20140921.1.440916e+dfsg1-15
ii  libfreerdp-common1.1.01.1.0~git20140921.1.440916e+dfsg1-15
ii  libfreerdp-core1.11.1.0~git20140921.1.440916e+dfsg1-15
ii  libfreerdp-crypto1.1  1.1.0~git20140921.1.440916e+dfsg1-15
ii  libfreerdp-gdi1.1 1.1.0~git20140921.1.440916e+dfsg1-15
ii  libfreerdp-locale1.1  1.1.0~git20140921.1.440916e+dfsg1-15
ii  libfreerdp-primitives1.1  1.1.0~git20140921.1.440916e+dfsg1-15
ii  libfreerdp-rail1.11.1.0~git20140921.1.440916e+dfsg1-15
ii  libfreerdp-utils1.1   1.1.0~git20140921.1.440916e+dfsg1-15
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  libssl1.0.2   1.0.2n-1
ii  libwinpr-crt0.1   1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-crypto0.11.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-dsparse0.1   1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-environment0.1   1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-file0.1  1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-handle0.11.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-heap0.1  1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-input0.1 1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-interlocked0.1   1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-library0.1   1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-path0.1  1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-pool0.1  1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-registry0.1  1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-rpc0.1   1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-sspi0.1  1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-synch0.1 1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-sysinfo0.1   1.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-thread0.11.1.0~git20140921.1.440916e+dfsg1-15
ii  libwinpr-utils0.1 1.1.0~git20140921.1.440916e+dfsg1-15
ii  libx11-6  2:1.6.5-1
ii  libxcursor1   1:1.1.15-1
ii  libxext6  2:1.3.3-1+b2
ii  libxfreerdp-client1.1 1.1.0~git20140921.1.440916e+dfsg1-15
ii  libxi62:1.7.9-1
ii  libxinerama1  2:1.1.3-1+b3
ii  libxkbfile1   1:1.0.9-2
ii  libxrender1   1:0.9.10-1
ii  libxv1

Bug#851079: marked as done (freerdp: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:19:58 +
with message-id 
and subject line Bug#896780: Removed package(s) from unstable
has caused the Debian Bug report #851079,
regarding freerdp: Please migrate to openssl1.1 in buster
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.)


-- 
851079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freerdp
Version: 1.1.0~git20140921.1.440916e+dfsg1-10
Severity: important
Control: block 827061 by -1

Hi,

Your package is failing to build with openssl 1.1.0:
/<>/freerdp-1.1.0~git20140921.1.440916e+dfsg1/winpr/libwinpr/sspi/NTLM/ntlm_compute.c:
 In function 'ntlm_compute_message_integrity_check':
/<>/freerdp-1.1.0~git20140921.1.440916e+dfsg1/winpr/libwinpr/sspi/NTLM/ntlm_compute.c:649:11:
 error: storage size of 'hmac_ctx' isn't known
  HMAC_CTX hmac_ctx;
   ^
/<>/freerdp-1.1.0~git20140921.1.440916e+dfsg1/winpr/libwinpr/sspi/NTLM/ntlm_compute.c:656:2:
 warning: implicit declaration of function 'HMAC_CTX_init' 
[-Wimplicit-function-declaration]
  HMAC_CTX_init(_ctx);
  ^
/<>/freerdp-1.1.0~git20140921.1.440916e+dfsg1/winpr/libwinpr/sspi/NTLM/ntlm_compute.c:662:2:
 warning: implicit declaration of function 'HMAC_CTX_cleanup' 
[-Wimplicit-function-declaration]
  HMAC_CTX_cleanup(_ctx);
  ^
/<>/freerdp-1.1.0~git20140921.1.440916e+dfsg1/winpr/libwinpr/sspi/NTLM/ntlm_compute.c:649:11:
 warning: unused variable 'hmac_ctx' [-Wunused-variable]
  HMAC_CTX hmac_ctx;
   ^

HMAC_CTX has been made opaque and now needs to be allocated with
HMAC_CTX_new().

See https://wiki.openssl.org/index.php/1.1_API_Changes and the
manpages for more information.

openssl 1.1.0 is available in experimental.


Kurt
--- End Message ---
--- Begin Message ---
Version: 1.1.0~git20140921.1.440916e+dfsg1-15+rm

Dear submitter,

as the package freerdp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/896780

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#890928: marked as done (freerdp: do not ship with buster)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:19:58 +
with message-id 
and subject line Bug#896780: Removed package(s) from unstable
has caused the Debian Bug report #890928,
regarding freerdp: do not ship with buster
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.)


-- 
890928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freerdp
Version: 1.1.0~git20140921.1.440916e+dfsg1-15
Severity: serious

We have src:freerdp2, which superseedes freerdp. We shouldn't ship
freerdp with buster. This should prevent freerdp from re-entering
testing once it gets removed.

Emilio
--- End Message ---
--- Begin Message ---
Version: 1.1.0~git20140921.1.440916e+dfsg1-15+rm

Dear submitter,

as the package freerdp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/896780

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#888372: marked as done (freerdp: FTBFS with FFmpeg 4.0)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:19:58 +
with message-id 
and subject line Bug#896780: Removed package(s) from unstable
has caused the Debian Bug report #888372,
regarding freerdp: FTBFS with FFmpeg 4.0
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.)


-- 
888372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freerdp
Version: 1.1.0~git20140921.1.440916e+dfsg1-15
Severity: important
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-3.5-transition

Hi,

Your package FTBFS with the upcoming version 3.5 of FFmpeg. In FFmpeg 3.5,
there are a number of API changes which will cause many packages to FTBFS.
For this reason I have uploaded an early development snapshot to experimental
before the 3.5 release in an attempt to fix some of these a bit quicker.
While 3.5 has not been finalized and the ABI is not stable yet, there should
not be any significant API breakages before the release.

Incomplete list of changes (based on looking at common build failures):
- Some fields in AVCodecContext have been removed and replaced with private
  options which can be set using the av_opt_set* APIs
- Most CODEC_* constants have been renamed to AV_CODEC_*
- The buffer constants FF_INPUT_BUFFER_PADDING_SIZE and FF_MIN_BUFFER_SIZE
  have been renamed to AV_INPUT_BUFFER_PADDING_SIZE and
  AV_INPUT_BUFFER_MIN_SIZE.
- The old resampling API provided by libavcodec has been removed. Use
  libswresample instead.
- The libavfilter/avfiltergraph.h header has been removed, include
  libavfilter/avfilter.h instead.
- The AVFrac structure (representing mixed rational numbers) has been
  removed.

Build log:
https://people.debian.org/~jcowgill/ffmpeg-3.5-20180122/freerdp_amd64.build

Thanks,
James
--- End Message ---
--- Begin Message ---
Version: 1.1.0~git20140921.1.440916e+dfsg1-15+rm

Dear submitter,

as the package freerdp has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/896780

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#897803: marked as done (llvm-toolchain-3.9: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:15:23 +
with message-id 
and subject line Bug#87: Removed package(s) from unstable
has caused the Debian Bug report #897803,
regarding llvm-toolchain-3.9: ftbfs with GCC-8
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.)


-- 
897803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:llvm-toolchain-3.9
Version: 1:3.9.1-19
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/llvm-toolchain-3.9_3.9.1-19_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] ArrayRefTest.InitializerList

 1 FAILED TEST


Testing: 0  2  4  6  8  10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 
46 48 50 52 54 56 58 60 62 64 66 68 70 72 74 76 78 80 82 84 86 88 90 92 94 96 
98 
Testing Time: 89.48s

Unexpected Passing Tests (17):
LLVM :: CodeGen/SPARC/LeonInsertNOPsDoublePrecision.ll
LLVM :: ExecutionEngine/MCJIT/cross-module-sm-pic-a.ll
LLVM :: ExecutionEngine/MCJIT/eh-lg-pic.ll
LLVM :: ExecutionEngine/MCJIT/eh-sm-pic.ll
LLVM :: ExecutionEngine/MCJIT/multi-module-sm-pic-a.ll
LLVM :: ExecutionEngine/MCJIT/stubs-sm-pic.ll
LLVM :: ExecutionEngine/MCJIT/test-global-init-nonzero-sm-pic.ll
LLVM :: ExecutionEngine/MCJIT/test-ptr-reloc-sm-pic.ll
LLVM :: ExecutionEngine/OrcMCJIT/cross-module-sm-pic-a.ll
LLVM :: ExecutionEngine/OrcMCJIT/eh-lg-pic.ll
LLVM :: ExecutionEngine/OrcMCJIT/eh-sm-pic.ll
LLVM :: ExecutionEngine/OrcMCJIT/multi-module-sm-pic-a.ll
LLVM :: ExecutionEngine/OrcMCJIT/remote/test-global-init-nonzero-sm-pic.ll
LLVM :: ExecutionEngine/OrcMCJIT/remote/test-ptr-reloc-sm-pic.ll
LLVM :: ExecutionEngine/OrcMCJIT/stubs-sm-pic.ll
LLVM :: ExecutionEngine/OrcMCJIT/test-global-init-nonzero-sm-pic.ll
LLVM :: ExecutionEngine/OrcMCJIT/test-ptr-reloc-sm-pic.ll


Failing Tests (1):
LLVM-Unit :: ADT/ADTTests/ArrayRefTest.InitializerList

  Expected Passes: 16742
  Expected Failures  : 124
  Unsupported Tests  : 339
  Unexpected Passes  : 17
  Unexpected Failures: 1
make[5]: *** [test/CMakeFiles/check-llvm.dir/build.make:61: 
test/CMakeFiles/check-llvm] Error 1
make[5]: Leaving directory '/<>/build-llvm'
make[4]: *** [CMakeFiles/Makefile2:92279: test/CMakeFiles/check-llvm.dir/all] 
Error 2
make[4]: Leaving directory '/<>/build-llvm'
make[3]: *** [CMakeFiles/Makefile2:92286: test/CMakeFiles/check-llvm.dir/rule] 
Error 2
make[3]: Leaving directory '/<>/build-llvm'
make[2]: *** [Makefile:20807: check-llvm] Error 2
make[2]: Leaving directory '/<>/build-llvm'
make[1]: *** [debian/rules:500: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:162: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Version: 1:3.9.1-19+rm

Dear submitter,

as the package llvm-toolchain-3.9 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/87

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive 

Bug#912977: iptables: nftables layer breaks ipsec/policy keyword

[Pierre Chifflier]

Package: iptables
Version: 1.8.1-2
Severity: grave
Tags: security
Justification: breaks rules, inserts pass-all rules
X-Debbugs-Cc: t...@security.debian.org, 
secure-testing-t...@lists.alioth.debian.org

Hi,

The debian package for iptables now transparently converts inserted
rules to nftables, which is great.

However, some keywords are not supported (like the 'policy' keyword for
IPsec transforms). The bad part is, these rules are inserted
*without* the matches, which makes in some cases your firewall useless.

For ex:
# iptables -F
# iptables -A OUTPUT -m policy --dir out --pol ipsec --strict --mode tunnel -o 
eth0 -j ACCEPT
# echo $?
0
# nft list ruleset

chain OUTPUT {
type filter hook output priority 0; policy accept;
oifname "eth0"  counter packets 90 bytes 26085 accept
}
}

As you can see, the inserted rule allows everything, while the expected
behavior would be 'only if going through an IPsec tunnel'.
Even worse: inserting the rule did not fail.

Until the 'ipsec' (or 'secpath') keyword works properly (and supports
all options), an acceptable behavior would be to reject the rule if one
or more keywords are not supported by nftables.

Regards,
Pierre

Bug#840305: marked as done (libatteanx-store-memorytriplestore-perl: depends on unavailable AtteanX::RDFQueryTranslator)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:08:24 +
with message-id 
and subject line Bug#912830: Removed package(s) from experimental
has caused the Debian Bug report #840305,
regarding libatteanx-store-memorytriplestore-perl: depends on unavailable 
AtteanX::RDFQueryTranslator
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.)


-- 
840305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libatteanx-store-memorytriplestore-perl
Version: 0.001~20150811-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package FTBFS against perl 5.24 or against a perl without . in @INC:

https://buildd.debian.org/status/package.php?p=libatteanx-store-memorytriplestore-perl=experimental

[...]
/usr/bin/make -C . OPTIMIZE="-g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security -fblocks -D_REENTRANT 
-D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe 
-I/usr/local/include" LDDLFLAGS="-Wl,-z,relro -lBlocksRuntime -shared 
-L/usr/local/lib -fstack-protector-strong" test TEST_VERBOSE=1
make[1]: Entering directory '/«PKGBUILDDIR»'
true
true
true
echo "Running Mkbootstrap for AtteanX::Store::MemoryTripleStore ()"
Running Mkbootstrap for AtteanX::Store::MemoryTripleStore ()
"/usr/bin/perl" \
"-MExtUtils::Mkbootstrap" \
-e "Mkbootstrap('MemoryTripleStore','');"
touch "MemoryTripleStore.bs"
chmod 644 "MemoryTripleStore.bs"
true
true
true
PERL_DL_NONLAZY=1 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" 
"-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef 
*Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t
Can't locate AtteanX/RDFQueryTranslator.pm in @INC (you may need to install the 
AtteanX::RDFQueryTranslator module) (@INC contains: /«PKGBUILDDIR»/blib/lib 
/«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 
/usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at t/planning.t 
line 12,  line 1.
BEGIN failed--compilation aborted at t/planning.t line 12,  line 1.
t/planning.t .. 
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 
Can't locate AtteanX/RDFQueryTranslator.pm in @INC (you may need to install the 
AtteanX::RDFQueryTranslator module) (@INC contains: /«PKGBUILDDIR»/blib/lib 
/«PKGBUILDDIR»/blib/arch /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 
/usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at t/query.t 
line 12,  line 1.
BEGIN failed--compilation aborted at t/query.t line 12,  line 1.
t/query.t . 
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 
Can't apply Attean::API::Plan to AtteanX::Store::MemoryTripleStore::Query - 
missing plan_as_string at /usr/share/perl5/Moo/Role.pm line 279.
Compilation failed in require at 
/«PKGBUILDDIR»/blib/lib/AtteanX/Store/MemoryTripleStore.pm line 54.
BEGIN failed--compilation aborted at 
/«PKGBUILDDIR»/blib/lib/AtteanX/Store/MemoryTripleStore.pm line 54.
Compilation failed in require at /usr/share/perl/5.24/Module/Load.pm line 77.
Can't locate AtteanX/Store/MemoryTripleStore in @INC (@INC contains: 
/«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/perl/5.24/Module/Load.pm line 77.

#   Failed test at t/simple.t line 8.
#  got: undef
# expected: 'AtteanX::Store::MemoryTripleStore'
Can't call method "new" on an undefined value at t/simple.t line 11.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 2 just after 1.
t/simple.t  
not ok 1
Dubious, test returned 2 (wstat 512, 0x200)
Failed 1/1 subtests 
Can't apply Attean::API::Plan to AtteanX::Store::MemoryTripleStore::Query - 
missing plan_as_string at /usr/share/perl5/Moo/Role.pm line 279.
Compilation failed in require at 

Bug#832127: marked as done (libtest-aggregate-perl: Breaks with Test-Simple >= 1.3)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:05:28 +
with message-id 
and subject line Bug#912744: Removed package(s) from unstable
has caused the Debian Bug report #832127,
regarding libtest-aggregate-perl: Breaks with Test-Simple >= 1.3
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.)


-- 
832127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtest-aggregate-perl
Version: 0.372-2
Severity: serious
Tags: upstream
Justification: not fit for release
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=100035

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Test::Aggregate up to 0.373 doesn't work with the new Test-Simple
(>= 1.3), in libtest-simple-perl (still in experimental but will go
into unstable soon), and in perl core since 5.25.1 (not in Debian for
another ~9 months). The new libtest-simple-perl already has a Breaks
on libtest-aggregate-perl.

So the current versions 0.372-2/testing and 0.373-1/unstable should
not go into a release.

I fixed the 2 reverse build dependencies, so libtest-aggregate-perl
can savely be removed from testing (and wait in unstable for an
upstream fix).


Cheers,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXkjtmXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG/AAP/1e7mG1CwSMn//fk2FTcBecJ
yHrDsWSKv/CjDiM0mR888KYZ0LfVW9uzME+V9XtSV4jhO5nKV9e71AjJqgJ3+Dce
gqX26FfgbCIXXnANEJ0nv5G8LXu6tQpxGRZuNl1ijqwJQwqIrObBi9SvliTensmk
B5M1FD88fLcn4hk46Wa9zdwc/4U4mwroaw9hqvID+v2bOPWt+3qBPpslwCwkENvP
lgOx1X94QnSzyCQaiUHsVp18V4H/uP/ual6EvsF3jlCKv8I6mCg9/DSMFNerPg29
vVoccxGGylDIJkjujfR+K78PoiAj0bw0Tnas8OL6/cVRAiV8pO2gYbT/rpB/kjEa
m1Klek/RuFYhjxBaerDtuJwTvuAjAyixePCEJTCjCZB/pxQ1ULnqTTJsRZKft6EZ
pTYaTMNMfJPGqSBe5iIdOsxipdxC7ABsvQ9phpo6StXey8/gTCBz71kCVcGsFur0
gOykajZf7H5By+yuxJ8o9GiXOP43KPOw8R+AfkJpKiA2G3cMfNlDy97GHmqsI/2F
7ofx2FWpCryGXOHt5/BUP3vuDzt4ZaO/q6XyZKHTWibi4AqzDoqoKdng7hxj7orz
tUUCC4A25yfJnbOxox4E2+b4/aZwllumzVBSNskVj6KJcCqSMbfBfmcBv/6D1Z8U
7x9ihncOlDWteMU61MoH
=7IHz
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 0.374-1+rm

Dear submitter,

as the package libtest-aggregate-perl has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/912744

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#906858: marked as done (xul-ext-livehttpheaders no longer works with firefox-esr 60)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:03:34 +
with message-id 
and subject line Bug#912623: Removed package(s) from unstable
has caused the Debian Bug report #906858,
regarding xul-ext-livehttpheaders no longer works with firefox-esr 60
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.)


-- 
906858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-livehttpheaders
Version: 0.17.1-2
Severity: serious

XUL addons are no longer supported.
--- End Message ---
--- Begin Message ---
Version: 0.17.1-2+rm

Dear submitter,

as the package livehttpheaders has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/912623

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#906849: marked as done (xul-ext-all-in-one-sidebar no longer works with firefox-esr 60)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:03:06 +
with message-id 
and subject line Bug#912621: Removed package(s) from unstable
has caused the Debian Bug report #906849,
regarding xul-ext-all-in-one-sidebar no longer works with firefox-esr 60
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.)


-- 
906849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-all-in-one-sidebar
Version: 0.7.28-2
Severity: serious

XUL addons are no longer supported.
--- End Message ---
--- Begin Message ---
Version: 0.7.31-1+rm

Dear submitter,

as the package all-in-one-sidebar has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/912621

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#825231: marked as done (libdevel-beginlift-perl: FTBFS with Perl 5.24: t/constcalc.t failure)

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:04:02 +
with message-id 
and subject line Bug#912743: Removed package(s) from unstable
has caused the Debian Bug report #825231,
regarding libdevel-beginlift-perl: FTBFS with Perl 5.24: t/constcalc.t failure
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.)


-- 
825231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdevel-beginlift-perl
Version: 0.001003-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

This package fails to build with Perl 5.24 (currently in experimental).
A full build log is available at
  
http://perl.debian.net/rebuild-logs/perl-5.24/libdevel-beginlift-perl_0.001003-1/


  t/constcalc.t .. 
  ok 1 - compile-time foo call first
  ok 2 - manual warning
  not ok 3 - const return from compile-time foo
  
  #   Failed test 'const return from compile-time foo'
  #   at t/constcalc.t line 28.
  #  got: 'Warning: something's wrong at t/constcalc.t line 15.
  # '
  # expected: '4
  # '
  ok 4 - bar called at run-time
  ok 5 - $int was incremented
  ok 6 - run-time foo after BeginLift disabled
  ok 7 - no more warnings
  1..7
  # Looks like you failed 1 test of 7.
  Dubious, test returned 1 (wstat 256, 0x100)
  Failed 1/7 subtests 
 
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Version: 0.001003-1+rm

Dear submitter,

as the package libdevel-beginlift-perl has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/912743

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#904402: marked as done (libdevel-beginlift-perl: FTBFS with perl 5.25+: 'OP' {aka 'struct op'} has no member named 'op_sibling')

[Debian Bug Tracking System]

Your message dated Mon, 05 Nov 2018 12:04:02 +
with message-id 
and subject line Bug#912743: Removed package(s) from unstable
has caused the Debian Bug report #904402,
regarding libdevel-beginlift-perl: FTBFS with perl 5.25+: 'OP' {aka 'struct 
op'} has no member named 'op_sibling'
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.)


-- 
904402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdevel-beginlift-perl
Severity: serious
Version:  0.001003-1

Running Mkbootstrap for BeginLift ()
chmod 644 "BeginLift.bs"
"/usr/bin/perl" "-Iinc" -MExtUtils::Command::MM -e 'cp_nonempty' -- 
BeginLift.bs blib/arch/auto/Devel/BeginLift/BeginLift.bs 644
"/usr/bin/perl" "-Iinc" "/usr/share/perl/5.26/ExtUtils/xsubpp"  -typemap 
'/usr/share/perl/5.26/ExtUtils/typemap' -typemap 
'/usr/lib/x86_64-linux-gnu/perl5/5.26/B/Utils/Install/typemap'  BeginLift.xs > 
BeginLift.xsc
mv BeginLift.xsc BeginLift.c
x86_64-linux-gnu-gcc -c  
-I/usr/lib/x86_64-linux-gnu/perl5/5.26/B/Hooks/OP/Check/Install 
-I/usr/lib/x86_64-linux-gnu/perl5/5.26/B/Hooks/OP/Check/EntersubForCV/Install 
-I/usr/lib/x86_64-linux-gnu/perl5/5.26/B/Utils/Install -D_REENTRANT 
-D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   
-DVERSION=\"0.001003\" -DXS_VERSION=\"0.001003\" -fPIC 
"-I/usr/lib/x86_64-linux-gnu/perl/5.26/CORE"   BeginLift.c
BeginLift.xs:13: warning: "LINKLIST" redefined
 #define LINKLIST(o) ((o)->op_next ? (o)->op_next : linklist((OP*)o))
 
In file included from /usr/lib/x86_64-linux-gnu/perl/5.26/CORE/perl.h:3921,
 from BeginLift.xs:4:
/usr/lib/x86_64-linux-gnu/perl/5.26/CORE/op.h:641: note: this is the location 
of the previous definition
 #define LINKLIST(o) ((o)->op_next ? (o)->op_next : op_linklist((OP*)o))
 
BeginLift.xs: In function 'THX_linklist':
BeginLift.xs:27:16: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
   if (kid->op_sibling) {
^~
op_sibparent
BeginLift.xs:28:33: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
kid->op_next = LINKLIST(kid->op_sibling);
 ^~
BeginLift.xs:13:23: note: in definition of macro 'LINKLIST'
 #define LINKLIST(o) ((o)->op_next ? (o)->op_next : linklist((OP*)o))
   ^
BeginLift.xs:28:33: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
kid->op_next = LINKLIST(kid->op_sibling);
 ^~
BeginLift.xs:13:38: note: in definition of macro 'LINKLIST'
 #define LINKLIST(o) ((o)->op_next ? (o)->op_next : linklist((OP*)o))
  ^
BeginLift.xs:28:33: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
kid->op_next = LINKLIST(kid->op_sibling);
 ^~
BeginLift.xs:16:41: note: in definition of macro 'linklist'
 # define linklist(o) THX_linklist(aTHX_ o)
 ^
BeginLift.xs:28:19: note: in expansion of macro 'LINKLIST'
kid->op_next = LINKLIST(kid->op_sibling);
   ^~~~
BeginLift.xs:29:15: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
kid = kid->op_sibling;
   ^~
   op_sibparent
BeginLift.xs: In function 'lift_cb':
BeginLift.xs:64:24: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
 for ( arg = curop->op_sibling; arg->op_sibling; arg = arg->op_sibling ) {
^~
op_sibparent
BeginLift.xs:64:41: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
 for ( arg = curop->op_sibling; arg->op_sibling; arg = arg->op_sibling ) {
 ^~
 op_sibparent
BeginLift.xs:64:64: error: 'OP' {aka 'struct op'} has no member named 
'op_sibling'; did you mean 'op_sibparent'?
 for ( arg = curop->op_sibling; arg->op_sibling; arg = arg->op_sibling ) {
^~