Bug#882717: marked as done (src:neomutt: Generated file autosetup/jimsh0.c without source code)

[Debian Bug Tracking System]

Your message dated Sun, 26 Nov 2017 07:33:40 +
with message-id 
and subject line Bug#882717: fixed in neomutt 20171027+dfsg.1-1
has caused the Debian Bug report #882717,
regarding src:neomutt: Generated file autosetup/jimsh0.c without source code
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.)


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


neomutt embeds a copy of jimtcl that is a generated bootstrap
version of jimtcl. The file needs to be removed. It seems likely
that we could just build-depend on jimtcl and use its jimsh or
whatever it's called.

-- Package-specific info:
NeoMutt 20171027
Copyright (C) 1996-2016 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type `neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type `neomutt -vv' for details.

System: Linux 4.13.0-1-amd64 (x86_64)
ncurses: ncurses 6.0.20170902 (compiled with 6.0)
libidn: 1.33 (compiled with 1.33)
hcache backends: tokyocabinet

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 7.2.0-16' 
--with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-7 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto 
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.2.0 (Debian 7.2.0-16) 

Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-lua' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-notmuch' '--disable-fmemopen' 
'--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' 
'--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm' 
'--with-tokyocabinet' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/neomutt-20171027=. -fstack-protector-strong -Wformat 
-Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now' 
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -g -O2 
-fdebug-prefix-map=/build/neomutt-20171027=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-delete-null-pointer-checks

Default options:
  +attach_headers_color +compose_to_sender +compress +cond_date 
  +encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color 
  +initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop 
  +progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar 
  +skip_quoted +smtp +status_color +timeout +tls_sni +trash 

Compile options:
  +bkgdset +color +curs_set +debug +fcntl -flock -fmemopen +futimens 
  +getaddrinfo +gnutls +gpgme +gss +hcache -homespool +idn -locales_hack +lua 
  +meta +mixmaster +nls +notmuch -openssl +pgp +resizeterm +sasl +smime 
  +start_color +sun_attachment +typeahead 
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"

To learn more about NeoMutt, visit: http://www.neomutt.org/
If you find a bug in NeoMutt, 

Bug#876191: most: configure cannot be built from source

[Helmut Grohne]

On Sat, Nov 25, 2017 at 12:36:33PM -0800, Benj. Mako Hill wrote:
> I agree that a hand-modified binary a binary would not mean that you
> don't need to provide source for that binary. I think there's likely
> going to be consensus on that in Debian.

That put's you in a difficult spot as to where to draw the line.

> I also think this situation is different because I think that a
> configure file is more like computer-generated, hand-modified,
> /source/ than like a binary.

What makes configure source? It doesn't come with indentation or things
that make normal source code human-consumable. Even though shell
scripting supports scoped variables, autoconf deliberately avoids using
them. Thus they are much closer to named, global memory locations.
Generated configure scripts are much closer to a disassembly of a
binary.

> I think one could also argue that there is an difference between the
> program binary and a build script which is used to build the package
> in question.

So do you argue that you can use a pre-built binary during build, but
you cannot ship in the binary package?

> To say that DFSG#3 is moot (i.e., that you /can not/ make
> modifications or derived versions) seems to me to be an
> exaggeration. It is more difficult than it might be if the software
> and build scripts were created in a different way. But that's not
> necessary a DFSG issue. Writing your software in a obscure programming
> language makes it harder to modify as well and that is obviously
> allowed.

DFSG #3 is about enabling users. It doesn't really matter if users
refrain from modifying due to licensing or due to being impractical. The
end result is, that the purported freedom hasn't transferred into
reality.

By your very same argument you could ship binaries, because you can
simply disassemble them, edit them and reassemble. It might be a bit
more difficult, but if the binary was liberally licensed would that
prevent you from doing so?

> Are you willing to say that source code can never contain code that
> was partially generated by another program that is provided? Even if
> it is generated by computers and then modified by hand? That's a much
> stronger position than I think is supportable by any reading of the
> DFSG than I've ever heard and it would eliminate many hundreds or even
> thousands of packages from Debian.

That's a tough question indeed. Half a year ago, the strict answer would
have eliminated nothing less than perl (#762638). Even though the Debian
perl maintainers were heavily patching the generated file, they are now
generating it at build time.

To evade answering it, I try to work from the impact. Whenever fixing a
bug is impeded by the inability to regenerate build artifacts, I file a
bug, because it clearly demonstrates that the freedom to modify is
limited here.

> This is distinctly different. The source code in the JS example is
> obviously not minified the Javascript if we use the GPL's "preferred
> form for modification" heuristic regardless of the change in
> question. If upstream wanted to make a change to the Javascript in
> their program, they would almost never use the minified version. If
> most's upstream wanted to make a change to their configure file, they
> would likely modify the pre-built version. Or they would go through
> rebuilding it again.

Most commonly, Javascript is not copy-left, but something like MIT.
Downstream projects commonly embed minified, embedded copies and just
update them whenever convenient. So yes, some upstreams (e.g. a past
Doxygen) do prefer to deal with minified Javascript.

> I agree! But I think that having packages removed from testing (as has
> now happened to most) over this interpretation is an overreaction to
> what I think constitutes an annoyance.

The removal happened due to not responding to the bug. You can defer
automatic removals indefinitely by continuously mailing the bug.

Do you think DFGS #2 would be a better justification for the severity?
The configure script in question was generated with autoconf 2.61. This
version of autoconf has been removed from Debian. Now, most is missing
the source for regenerating configure.

Compare this to bumping gcc versions. When a package fails to build with
a more recent gcc, it receives a FTBFS bug as well. You can temporarily
avoid them by explicitly selecting a lower version, but when that
version gets removed, such a package inevitably becomes RC buggy. The
only difference here is that by not rebuilding from source at build
time, you get the RC bug with a delay as has happened here. That's why
debhelper 10 autoreconfs by default.

I believe that the inability to fix bugs is a serious issue.

Helmut

Bug#882723: src:keepassxc: Generated file without preferred form of source: src/zxcvbn/dict-src.h

[Paul Gevers]

Hi Julian,

On 26-11-17 01:29, Julian Andres Klode wrote:
> The file src/zxcvbn/dict-src.h is an autogenerated dictionary file,
> generated from smaller files. The directory is removed during build.

Are you saying that these smaller files are in the tar ball, but after
one build the files are gone? That would mean you have a problem to
build twice in a row.

> I'm not entirely sure if I need to repackage the source tarball or
> not, given that the file is removed during clean, hence the bug
> report and CCing debian-devel.

I would copy the directory to some tmp folder in debian/ during the
configure step (if not done before) and move it back during the clean
step (and copy it from debian/ in the step where you are building
src/zxcvbn/dict-src.h).

I don't see any issue, except you should ask upstream to fix the
situation. Repacking the source tarball for this feels wrong, except if
you need to do that for other reasons as well.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#882681: mariadb-10.1: Missing mariadb-test package prevents testing migration

[Andreas Metzler]

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

On 2017-11-25 Bas Couwenberg  wrote:
> Source: mariadb-10.1
> Version: 1:10.1.29-6
> Severity: serious
> Justification: makes the package in question unusable or mostly so
> Control: affects -1 src:apr-util src:asterisk src:dovecot src:exim4 src:gammu 
> src:gdal src:gnunet src:gnustep-sqlclient src:grass src:jabberd2 src:kamailio 
> src:kdb src:kopanocore src:mailutils src:mysql-connector-c++ src:pike7.8 
> src:pmacct src:poco src:qtbase-opensource-src src:slurm-llnl src:sope 
> src:vtk6 src:zabbix

> Dear Maintainer,

> The mariadb-10.1 packages no longer build the mariadb-test &
> mariadb-test-data packages, but the version in testing still does.
> This prevents britney from migrating the package to testing [0]:

>  trying: mariadb-10.1
>  skipped: mariadb-10.1 (1827, 1009, 24)
>  got: 71+0: a-10:i-32:a-3:a-3:a-3:m-3:m-7:m-3:p-3:s-4
>  * mips64el: mariadb-test

> Because mariadb-10.2 is not going to migrate to testing any time soon,
> the -test* packages need to be built by the mariadb-10.1 package again
> now that its version uses an epoch.

> [0] https://release.debian.org/britney/update_output.txt

Hello Bas,

this reasoning is incorrect or incomplete. Stopping to build binaries
without reverse dependencies is something Debian packages do all the
time. It is in not a bug in the specific package to do so. Our
infrastructure needs to be able to handle this.

See e.g. https://packages.qa.debian.org/d/d-conf.html which dropped a
transitional package in 0.26.1-1 and migrated without error.

I am downgrading this bug because it now blocks the mariadb from
transitioning to testing itself, hiding other possible problems.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Processed: Re: Bug#882681: mariadb-10.1: Missing mariadb-test package prevents testing migration

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #882681 [src:mariadb-10.1] mariadb-10.1: Missing mariadb-test package 
prevents testing migration
Severity set to 'normal' from 'serious'
> tags -1 moreinfo
Bug #882681 [src:mariadb-10.1] mariadb-10.1: Missing mariadb-test package 
prevents testing migration
Added tag(s) moreinfo.

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

Bug#877245: marked as done (php-codecoverage: FTBFS: tests fail: Error: Class 'PHPUnit\Util\Test' not found)

[Debian Bug Tracking System]

Your message dated Sun, 26 Nov 2017 04:48:57 +
with message-id 
and subject line Bug#877245: fixed in php-codecoverage 5.2.2+dfsg-2
has caused the Debian Bug report #877245,
regarding php-codecoverage: FTBFS: tests fail: Error: Class 'PHPUnit\Util\Test' 
not found
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.)


-- 
877245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-codecoverage
Version: 5.2.2+dfsg-1
Severity: serious
Justification: fails to build from source

Hi,

php-codecoverage/experimental FTBFS in a current sid+exerimental
environment:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/php-codecoverage-5.2.2+dfsg'
ln -s /usr/share/javascript/bootstrap/css/bootstrap.min.css 
/build/php-codecoverage-5.2.2+dfsg/src/Report/Html/Renderer/Template/css
ln -s /usr/share/javascript/bootstrap/js/bootstrap.min.js 
/build/php-codecoverage-5.2.2+dfsg/src/Report/Html/Renderer/Template/js
ln -s /usr/share/javascript/jquery/jquery.min.js 
/build/php-codecoverage-5.2.2+dfsg/src/Report/Html/Renderer/Template/js
ln -s /usr/share/twitter-bootstrap/files/html5shiv/html5shiv.min.js 
/build/php-codecoverage-5.2.2+dfsg/src/Report/Html/Renderer/Template/js
phpunit
PHPUnit 5.4.6 by Sebastian Bergmann and contributors.

Runtime:   PHP 7.0.22-3 with Xdebug 2.5.5
Configuration: /build/php-codecoverage-5.2.2+dfsg/phpunit.xml

E.ESS.EEE...E...E..E...E. 65 / 66 ( 98%)
. 66 / 66 (100%)

Time: 595 ms, Memory: 10.00MB

There were 9 errors:

1) SebastianBergmann\CodeCoverage\Report\BuilderTest::testSomething
Error: Class 'PHPUnit\Util\Test' not found

/build/php-codecoverage-5.2.2+dfsg/tests/TestCase.php:109
/build/php-codecoverage-5.2.2+dfsg/tests/tests/BuilderTest.php:27

2) 
SebastianBergmann\CodeCoverage\Report\CloverTest::testCloverForBankAccountTest
Error: Class 'PHPUnit\Util\Test' not found

/build/php-codecoverage-5.2.2+dfsg/tests/TestCase.php:109
/build/php-codecoverage-5.2.2+dfsg/tests/tests/CloverTest.php:26

3) SebastianBergmann\CodeCoverage\CodeCoverageTest::testCollect
Error: Class 'PHPUnit\Util\Test' not found

/build/php-codecoverage-5.2.2+dfsg/tests/TestCase.php:109
/build/php-codecoverage-5.2.2+dfsg/tests/tests/CodeCoverageTest.php:288

4) SebastianBergmann\CodeCoverage\CodeCoverageTest::testMerge
Error: Class 'PHPUnit\Util\Test' not found

/build/php-codecoverage-5.2.2+dfsg/tests/TestCase.php:173
/build/php-codecoverage-5.2.2+dfsg/tests/tests/CodeCoverageTest.php:308

5) SebastianBergmann\CodeCoverage\CodeCoverageTest::testMerge2
Error: Class 'PHPUnit\Util\Test' not found

/build/php-codecoverage-5.2.2+dfsg/tests/TestCase.php:109
/build/php-codecoverage-5.2.2+dfsg/tests/tests/CodeCoverageTest.php:324

6) SebastianBergmann\CodeCoverage\Report\Crap4jTest::testForBankAccountTest
Error: Class 'PHPUnit\Util\Test' not found

/build/php-codecoverage-5.2.2+dfsg/tests/TestCase.php:109
/build/php-codecoverage-5.2.2+dfsg/tests/tests/Crap4jTest.php:26

7) SebastianBergmann\CodeCoverage\Report\Html\HTMLTest::testForBankAccountTest
Error: Class 'PHPUnit\Util\Test' not found

/build/php-codecoverage-5.2.2+dfsg/tests/TestCase.php:109
/build/php-codecoverage-5.2.2+dfsg/tests/tests/HTMLTest.php:47

8) SebastianBergmann\CodeCoverage\Report\TextTest::testTextForBankAccountTest
Error: Class 'PHPUnit\Util\Test' not found

/build/php-codecoverage-5.2.2+dfsg/tests/TestCase.php:109
/build/php-codecoverage-5.2.2+dfsg/tests/tests/TextTest.php:26

9) SebastianBergmann\CodeCoverage\Report\Xml\XMLTest::testForBankAccountTest
Error: Class 'PHPUnit\Util\Test' not found

/build/php-codecoverage-5.2.2+dfsg/tests/TestCase.php:109
/build/php-codecoverage-5.2.2+dfsg/tests/tests/XMLTest.php:43

--

There were 2 skipped tests:

1) 
SebastianBergmann\CodeCoverage\CodeCoverageTest::testCanBeConstructedForPhpdbgWithoutGivenFilterObject
Requires PHPDBG

/build/php-codecoverage-5.2.2+dfsg/tests/tests/CodeCoverageTest.php:71

2) 
SebastianBergmann\CodeCoverage\CodeCoverageTest::testCanBeConstructedForPhpdbgWithGivenFilterObject
Requires PHPDBG

/build/php-codecoverage-5.2.2+dfsg/tests/tests/CodeCoverageTest.php:90

ERRORS!
Tests: 66, Assertions: 112, Errors: 9, Skipped: 2.
debian/rules:28: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/build/php-codecoverage-5.2.2+dfsg'


Andreas


php-codecoverage_5.2.2+dfsg-1.log.gz

Bug#876497: marked as done (phpunit-mock-object: FTBFS: PHP Fatal error: Interface 'PHPUnit\Framework\SelfDescribing' not found in /build/phpunit-mock-object-4.0.4/src/Matcher/Invocation.php on line

[Debian Bug Tracking System]

Your message dated Sun, 26 Nov 2017 04:49:11 +
with message-id 
and subject line Bug#876497: fixed in phpunit-mock-object 4.0.4-2
has caused the Debian Bug report #876497,
regarding phpunit-mock-object: FTBFS: PHP Fatal error:  Interface 
'PHPUnit\Framework\SelfDescribing' not found in 
/build/phpunit-mock-object-4.0.4/src/Matcher/Invocation.php on line 17
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.)


-- 
876497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phpunit-mock-object
Version: 4.0.4-1
Severity: serious
Justification: fails to build from source

Hi,

phpunit-mock-object/experimental FTBFS in a current sid/experimental
environment:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/phpunit-mock-object-4.0.4'
# Build autoload.php for tests
mkdir --parents vendor
phpab \
--output vendor/autoload.php \
--template debian/autoload.php.tpl \
tests/_fixture
phpab %development% - Copyright (C) 2009 - 2017 by Arne Blankerts

Scanning directory tests/_fixture

Autoload file vendor/autoload.php generated.

# Workaround to ensure the local class takes precedence
mkdir --parents PHPUnit/Framework
ln -s ../../src PHPUnit/Framework/MockObject
# Actually run the tests
phpunit
PHPUnit 5.4.6 by Sebastian Bergmann and contributors.

Runtime:   PHP 7.0.22-3
Configuration: /build/phpunit-mock-object-4.0.4/phpunit.xml

PHP Fatal error:  Interface 'PHPUnit\Framework\SelfDescribing' not found in 
/build/phpunit-mock-object-4.0.4/src/Matcher/Invocation.php on line 17
debian/rules:19: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
make[1]: Leaving directory '/build/phpunit-mock-object-4.0.4'


Full log attached.

Andreas


phpunit-mock-object_4.0.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: phpunit-mock-object
Source-Version: 4.0.4-2

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated phpunit-mock-object 
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: Sat, 25 Nov 2017 14:46:26 -1000
Source: phpunit-mock-object
Binary: phpunit-mock-object
Architecture: source all
Version: 4.0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Description:
 phpunit-mock-object -
Closes: 876497
Changes:
 phpunit-mock-object (4.0.4-2) unstable; urgency=medium
 .
   * Team upload
   * Upload to unstable, with the rest of the latest PHPUnit stack
   * Force recent PHPUnit for tests (Closes: #876497)
   * Update Standards-Version to 4.1.1
   * Drop versioned dependency satisfied in stable
Checksums-Sha1:
 742ea8f6dcbb6bd326e9a2b17d9ce7cf948df7e9 1929 phpunit-mock-object_4.0.4-2.dsc
 1685c1c314f09cd16e2a566703c7f6035b81b7e9 5868 
phpunit-mock-object_4.0.4-2.debian.tar.xz
 c71e17d13e55a78a38c1df9ddd7e0dfb6808657e 23600 
phpunit-mock-object_4.0.4-2_all.deb
 990f1d0619c28b145af20b7c72e38eef1a535156 8545 
phpunit-mock-object_4.0.4-2_amd64.buildinfo
Checksums-Sha256:
 36eb908c448de1410b71ad3b9fac53224c8628513f5af72026a81cde4ff1defd 1929 
phpunit-mock-object_4.0.4-2.dsc
 6776de35d144bdc2e6f7c8d99d1bc1b6495632f731e943969ea97b33e217009f 5868 
phpunit-mock-object_4.0.4-2.debian.tar.xz
 295e956f448e02021d56ece8a65940abc71cb06814b457e0fbe88db2eeb1a79c 23600 
phpunit-mock-object_4.0.4-2_all.deb
 e78bc5f9463e129fc66b4c108536af341d2f373b3e5588ce9ec6f7bf47db71c0 8545 
phpunit-mock-object_4.0.4-2_amd64.buildinfo
Files:
 c8674201003cf22d02d224d3f9de5ac1 1929 php optional 
phpunit-mock-object_4.0.4-2.dsc
 7fe8b3d9d7fe58d0647574dfa67fd92b 5868 php optional 
phpunit-mock-object_4.0.4-2.debian.tar.xz
 f88a9991df4a5d1c229b9d2d868cf54a 23600 php optional 
phpunit-mock-object_4.0.4-2_all.deb
 

Bug#875980: marked as done (kodi-pvr-vuplus: PVR addon not compatible with Kodi from same Debian release)

[Debian Bug Tracking System]

Your message dated Sun, 26 Nov 2017 03:34:32 +
with message-id 
and subject line Bug#875980: fixed in kodi-pvr-vuplus 2.4.12+dfsg1-1
has caused the Debian Bug report #875980,
regarding kodi-pvr-vuplus: PVR addon not compatible with Kodi from same Debian 
release
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.)


-- 
875980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kodi-pvr-vuplus
Version: 2.4.4+git20160820-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The Vuplus PVR addon can be installed, configured and generally works until 
next Kodi start.

After next Kodi start a message box comes up stating that the Vu+/Enigma Client 
Addon is not compatible with this Kodi version and the Addon is automatically 
deactivated.

That behaviour finally renders the Addon and so complete Debian package 
unusable.

The current upstream version of the addon is 3.5.1.

BR
Marko

Log entry is
19:03:19.917 T:139766167123712  NOTICE: ADDON: pvr.vuplus version 2.4.4 is 
incompatible


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

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

Versions of packages kodi-pvr-vuplus depends on:
pn  kodi-api-pvr   
ii  libc6  2.24-11+deb9u1
ii  libgcc11:6.3.0-18
ii  libkodiplatform16  17.1.0-1
ii  libp8-platform22.1.0.1+dfsg1-1
ii  libstdc++6 6.3.0-18
ii  libtinyxml2.6.2v5  2.6.2-4

kodi-pvr-vuplus recommends no packages.

kodi-pvr-vuplus suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kodi-pvr-vuplus
Source-Version: 2.4.12+dfsg1-1

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated kodi-pvr-vuplus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 Nov 2017 03:56:17 +0100
Source: kodi-pvr-vuplus
Binary: kodi-pvr-vuplus
Architecture: source
Version: 2.4.12+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Balint Reczey 
Description:
 kodi-pvr-vuplus - Vu+/Enigma2 PVR Addon for Kodi
Closes: 875980
Changes:
 kodi-pvr-vuplus (2.4.12+dfsg1-1) unstable; urgency=medium
 .
   [ Balint Reczey ]
   * Add watch file and exclude debian dir from upstream tarball via
 debian/copyright
   * Use my @ubuntu.com email address in Uploaders field
 .
   [ Debian's Automated Developer ]
   * New upstream version 2.4.12+dfsg1 (Closes: #875980)
   * Drop 0001-adapt-to-api-change-SeekTime.patch integrated upstream
Checksums-Sha1:
 f558ca57c79a82a0101a8d8c79fcffdec1a9492b 2160 
kodi-pvr-vuplus_2.4.12+dfsg1-1.dsc
 111f9f808873efb7580623bcd749ac947500fea4 78417 
kodi-pvr-vuplus_2.4.12+dfsg1.orig.tar.gz
 3d2d3a87a5f6229ad0a5d2b0edb5dcf092060c11 2824 
kodi-pvr-vuplus_2.4.12+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 6d016f17c1e99c27cab843279e00b62f21310535fbc6a91c01f213bd283b2144 2160 
kodi-pvr-vuplus_2.4.12+dfsg1-1.dsc
 037b6217487f60eafac8918f64db47f8409f541f9c4282debd02fca15779910d 78417 
kodi-pvr-vuplus_2.4.12+dfsg1.orig.tar.gz
 836d9c0a81bafad131ec0d742fb899839697ca4039e22f3090c172121f68a5b7 2824 
kodi-pvr-vuplus_2.4.12+dfsg1-1.debian.tar.xz
Files:
 8adafea91be01203a6f80053d650042d 2160 libs extra 
kodi-pvr-vuplus_2.4.12+dfsg1-1.dsc
 923e248a6bbfaec0a423af770afcadce 78417 libs extra 
kodi-pvr-vuplus_2.4.12+dfsg1.orig.tar.gz
 fdef4696e70a724dad8d265cd27440bd 2824 libs extra 
kodi-pvr-vuplus_2.4.12+dfsg1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#875980: marked as pending

[Balint Reczey]

tag 875980 pending
thanks

Hello,

Bug #875980 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


http://anonscm.debian.org/git/pkg-multimedia/kodi-pvr-vuplus.git/commit/?id=1615680

---
commit 1615680704f37729e0e776d81e553b625acb489c
Author: Balint Reczey 
Date:   Sun Nov 26 03:58:06 2017 +0100

Update changelog

diff --git a/debian/changelog b/debian/changelog
index ce164a2..66846e7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,15 @@
-kodi-pvr-vuplus (2.4.4+git20160820-3) UNRELEASED; urgency=medium
+kodi-pvr-vuplus (2.4.12+dfsg1-1) unstable; urgency=medium
 
-  *
+  [ Balint Reczey ]
+  * Add watch file and exclude debian dir from upstream tarball via
+debian/copyright
+  * Use my @ubuntu.com email address in Uploaders field
 
- -- Balint Reczey   Sun, 26 Nov 2017 03:41:14 +0100
+  [ Debian's Automated Developer ]
+  * New upstream version 2.4.12+dfsg1 (Closes: #875980)
+  * Drop 0001-adapt-to-api-change-SeekTime.patch integrated upstream
+
+ -- Balint Reczey   Sun, 26 Nov 2017 03:56:17 +0100
 
 kodi-pvr-vuplus (2.4.4+git20160820-2) unstable; urgency=medium
 

Processed: Bug#875980 marked as pending

[Debian Bug Tracking System]

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

> tag 875980 pending
Bug #875980 [kodi-pvr-vuplus] kodi-pvr-vuplus: PVR addon not compatible with 
Kodi from same Debian release
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#865671: marked as done (scotch hides build failures)

[Debian Bug Tracking System]

Your message dated Sun, 26 Nov 2017 03:03:46 +
with message-id 
and subject line Bug#865671: fixed in scotch 6.0.4.dfsg1-5
has caused the Debian Bug report #865671,
regarding scotch hides build failures
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.)


-- 
865671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scotch
Version: 5.1.12b.dfsg-2
Severity: serious
Justification: policy 4.6
Tags: jessie stretch buster sid
User: helm...@debian.org
Usertags: rebootstrap

When some part of scotch's build fails (e.g. mpicc), the build continues
and may produce a broken package. This violates Debian Policy section
4.6. The cause is the use of an embedded makefile script without the
recommended "set -e".

Helmut
--- End Message ---
--- Begin Message ---
Source: scotch
Source-Version: 6.0.4.dfsg1-5

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated scotch package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Nov 2017 10:29:40 +0800
Source: scotch
Binary: scotch ptscotch libscotch-dev libptscotch-dev scotch-dbg ptscotch-dbg 
libscotch-dbg libptscotch-dbg libscotchmetis-dev libscotchparmetis-dev 
libscotch-6.0 libptscotch-6.0
Architecture: source
Version: 6.0.4.dfsg1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Description:
 libptscotch-6.0 - MPI programs and libraries for graph, mesh and hypergraph 
partiti
 libptscotch-dbg - MPI programs and libraries for graph, mesh and hypergraph 
partiti
 libptscotch-dev - MPI programs and libraries for graph, mesh and hypergraph 
partiti
 libscotch-6.0 - programs and libraries for graph, mesh and hypergraph 
partitionin
 libscotch-dbg - programs and libraries for graph, mesh and hypergraph 
partitionin
 libscotch-dev - programs and libraries for graph, mesh and hypergraph 
partitionin
 libscotchmetis-dev - programs and libraries for graph, mesh and hypergraph 
partitionin
 libscotchparmetis-dev - programs and libraries for graph, mesh and hypergraph 
partitionin
 ptscotch   - MPI programs and libraries for graph, mesh and hypergraph partiti
 ptscotch-dbg - MPI programs and libraries for graph, mesh and hypergraph 
partiti
 scotch - programs and libraries for graph, mesh and hypergraph partitionin
 scotch-dbg - programs and libraries for graph, mesh and hypergraph partitionin
Closes: 865671
Changes:
 scotch (6.0.4.dfsg1-5) unstable; urgency=medium
 .
   * Team upload.
   * debian/rules: apply "set -e" at the build step to halt on build
 error. Closes: #865671.
 - treat tests (make check) as information-only, don't halt on
   check failure
   * improve thread handling with -DSCOTCH_PTHREAD_NUMBER=2 and
 -DSCOTCH_PTHREAD_AFFINITY_LINUX (see INSTALL.txt)
Checksums-Sha1:
 1162aaf2733b123d58158a4ea80c6fb0c34b1f39 2799 scotch_6.0.4.dfsg1-5.dsc
 568d66fd9cb7df4589ce1e0f6b99d70c6d7a396f 17752 
scotch_6.0.4.dfsg1-5.debian.tar.xz
Checksums-Sha256:
 7e97831d8e7b99527b465435b91554b8ee7603d654e49fd7f463db40d93df3c6 2799 
scotch_6.0.4.dfsg1-5.dsc
 5b44ebb8d1944f4bf2ef9d656353e3047b75f201bf7f2ed0ec7eb84b4aad14ef 17752 
scotch_6.0.4.dfsg1-5.debian.tar.xz
Files:
 471cd6114307bdf6b02d72e0078fc1fa 2799 math optional scotch_6.0.4.dfsg1-5.dsc
 39227f03c15bfa1e411a42306ee7eb3c 17752 math optional 
scotch_6.0.4.dfsg1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAloaKXYUHGRwYXJzb25z
QGRlYmlhbi5vcmcACgkQVz7x5L1aAfrAchAAoSnKOONh1evO8rQoI96K1IRe9nqf
YrIpuHohU1Pg4SZ0CERm8VzpCB3mJrfnNGRiehAYDMPnA5ViDXgENlt6nfjX/vks
u34sQ/95zeO85b9SVZMar0HxIvhdXXNzZjcAc3AkcMkczFXCGlEVOAMx9rTi99Pv
z8bsNvvbPUb4FYc1BpA9pmZgQb/hQC1mrTRPw8CxX/xq+/sDWNzWdOAKsANSi4Mr
0YphybFCDaAdd02xyqqnuCNiKNbb1LAOO7hx4cQp3wOQDKIdSoS8N2YYp+GQhsct

Processed: summary 790204 Blocked by upstream FTBFS bugs...

[Debian Bug Tracking System]

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

> summary 790204 Blocked by upstream FTBFS bugs...
Summary recorded from message bug 790204 message 
> thanks
Stopping processing here.

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

Bug#880276: caused by the fix of #842432

[Cédric Boutillier]

Control: retitle -1 test using GCM with IV option fails after fix for 
CVE-2016-7798 

Hi,

Checking when the package stopped to pass autopkgtests, I could trace
the issue to the fix of #842432 in ruby2.3 to avoid IV reuse in GCM
mode. The title of the failing test
  test_ciphertext_encrypted_with_v2_decrypts_with_v2_gcm_iv_option
also suggests it is the source of the problem.

Cédric

Processed: caused by the fix of #842432

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 test using GCM with IV option fails after fix for CVE-2016-7798
Bug #880276 [src:ruby-encryptor] ruby-encryptor: FTBFS: ERROR: Test "ruby2.3" 
failed: Invalid gemspec in [encryptor.gemspec]: No such file or directory - git
Changed Bug title to 'test using GCM with IV option fails after fix for 
CVE-2016-7798' from 'ruby-encryptor: FTBFS: ERROR: Test "ruby2.3" failed: 
Invalid gemspec in [encryptor.gemspec]: No such file or directory - git'.

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

Bug#882723: src:keepassxc: Generated file without preferred form of source: src/zxcvbn/dict-src.h

[Julian Andres Klode]

Package: src:keepassxc
Severity: serious

The file src/zxcvbn/dict-src.h is an autogenerated dictionary file,
generated from smaller files. The directory is removed during build.

I'm not entirely sure if I need to repackage the source tarball or
not, given that the file is removed during clean, hence the bug
report and CCing debian-devel.

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

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

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#882722: jimtcl: Contains embedded, different bootstrap version of jimtcl in autosetup

[Julian Andres Klode]

Source: jimtcl
Severity: serious

autosetup/jimsh0.c is different from the version generated by 
make-bootstrap-jim. As such
it is a generated file without source code, which are not allowed in the 
archive.

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

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

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#882721: src:openocd: Contains generated file autosetup/jimsh0.c

[Julian Andres Klode]

Control: severity -1 normal

On Sun, Nov 26, 2017 at 01:08:23AM +0100, Julian Andres Klode wrote:
> Package: src:openocd
> Severity: serious
> 
> jimsh0.c is a generated bootstrap version of jimtcl. Please
> repackage the tarball to remove it, and build-depend on jimtcl
> instead (for example).

Actually, it contains an entire copy of jimtcl, so downgrading
this. It still makes sense to regenerate the bootstrap version
of jimtcl at build time to make sure it is identical to the shipped
source code.


-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Processed: Re: Bug#882721: src:openocd: Contains generated file autosetup/jimsh0.c

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #882721 [src:openocd] src:openocd: Contains generated file 
autosetup/jimsh0.c
Severity set to 'normal' from 'serious'

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

Bug#882255: libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc 2.25

[Aurelien Jarno]

On 2017-11-21 01:43, Mikulas Patocka wrote:
> 
> 
> On Tue, 21 Nov 2017, Aurelien Jarno wrote:
> 
> > On 2017-11-21 01:01, Mikulas Patocka wrote:
> > > 
> > > 
> > > On Tue, 21 Nov 2017, Aurelien Jarno wrote:
> > > 
> > > > On 2017-11-21 00:12, Mikulas Patocka wrote:
> > > > > 
> > > > > 
> > > > > On Mon, 20 Nov 2017, Aurelien Jarno wrote:
> > > > > 
> > > > > > On 2017-11-20 19:13, Mikulas Patocka wrote:
> > > > > > > Package: libc6-amd64
> > > > > > > Version: 2.25-1
> > > > > > > Severity: critical
> > > > > > > Justification: breaks the whole system
> > > > > > > 
> > > > > > > Dear Maintainer,
> > > > > > > 
> > > > > > > *** Reporter, please consider answering these questions, where 
> > > > > > > appropriate ***
> > > > > > > 
> > > > > > >* What led up to the situation?
> > > > > > > 
> > > > > > > I have a x86-64 system with i386 and x32 foreign architectures 
> > > > > > > (because I
> > > > > > > need to develop software for i386 and x32 architectures).
> > > > > > > 
> > > > > > >* What exactly did you do (or not do) that was effective (or
> > > > > > >  ineffective)?
> > > > > > > 
> > > > > > > I ran apt update and apt upgrade. Apt tried to upgrade to 
> > > > > > > libc-2.25.
> > > > > > > 
> > > > > > >* What was the outcome of this action?
> > > > > > > 
> > > > > > > Halfway through apt upgrade it failed and I ended up with 
> > > > > > > unusable system where
> > > > > > > large number of binaries were segfauting on startup without doign 
> > > > > > > anything.
> > > > > > > 
> > > > > > >* What outcome did you expect instead?
> > > > > > > 
> > > > > > > The upgrade to libc-2.25 should work.
> > > > > > > 
> > > > > > > 
> > > > > > > The reason for the catastrophic failure is this:
> > > > > > > 
> > > > > > > There is package libc6-amd64:i386 and libc6-amd64:x32 (which 
> > > > > > > provide
> > > > > > 
> > > > > > I guess you mean you have installed one of the two, not both.
> > > > > > 
> > > > > > > x86-64 libc in /lib64/). This package is not technically needed 
> > > > > > > (because
> > > > > > > x86-64 libc is already installed in /lib/x86_64-linux-gnu/), but 
> > > > > > > it is
> > > > > > > installed nonetheless because of some dependencies.
> > > > > > 
> > > > > > Just to be clear, as said in my other email, this *is* technically
> > > > > > needed as gcc-multilib is not able to make use of the libc in
> > > > > > /lib/x86_64-linux-gnu.
> > > > > > 
> > > > > > > apt makes sure that all libc packages are upgraded at once to the 
> > > > > > > same
> > > > > > > version. However, during the upgrade process, the package
> > > > > > > libc6-amd64 is upgraded before libc6:amd64. So, during the 
> > > > > > > upgrade, we
> > > > > > > temporarily have two libcs with different versions on the system, 
> > > > > > > and this
> > > > > > > mismatch makes most of the x86-64 binaries crash. Due to the 
> > > > > > > crashes, the
> > > > > > > upgrade doesn't proceed and it doesn't install the correct libc 
> > > > > > > version in
> > > > > > > /lib/x86_64-linux-gnu/.
> > > > > > > 
> > > > > > > The result is unusable system.
> > > > > > 
> > > > > > I have done some tests, and while I confirm that libc6-i386:amd64 is
> > > > > 
> > > > > The problem is with libc6-amd64:i386 or libc6-amd64:x32.
> > > > > Not libc6-i386:amd64.
> > > > 
> > > > Yes, sorry about that, I really did the test with libc6-amd64:i386, but
> > > > mixed it when typing the mail.
> > > > 
> > > > > I.e. use amd64 Debian Sid base installation, add foreign 
> > > > > architectures 
> > > > > i386 and x32 and use this /etc/apt/sources.list:
> > > > > 
> > > > > deb [ arch=i386,amd64 ] http://ftp.cz.debian.org/debian/ sid main 
> > > > > contrib non-free
> > > > > deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unreleased 
> > > > > main
> > > > > deb [ arch=x32 ] http://ftp.de.debian.org/debian-ports/ unstable main
> > > > > 
> > > > > > unpacked much before libc6:amd64, it doesn't cause any issue here.
> > > > > > Indeed the search path in ld.so is to give higher priority to
> > > > > > /lib/x86_64-linux-gnu/ over /lib64. I have even been able to install
> > > > > > libc6:amd64 in version 2.24 (using force-all), while keeping
> > > > > > libc6-amd64:i386 in version 2.25.
> > > > > > 
> > > > > > The only way to change the priority of the two path is using a
> > > > > > non-standard ld.so.conf. Have you made any change to 
> > > > > > /etc/ld.so.conf or
> > > > > > /etc/ld.so.conf.d/*? Maybe you can share the content of this file 
> > > > > > and
> > > > > > this directory.
> > > > > 
> > > > > On my system, there's a file 
> > > > > /etc/ld.so.conf.d/zz_amd64-biarch-compat.conf 
> > > > > containing:
> > > > > 
> > > > > # Legacy biarch compatibility support
> > > > > /lib64
> > > > > /usr/lib64
> > > > > 
> > > > > and /etc/ld.so.conf.d/zz_i386-biarch-compat.conf containing:
> > > > > 
> > > > > # Legacy biarch compatibility support
> > > > > /lib32
> > > > > /usr/lib32
> > > > > 

Bug#882721: src:openocd: Contains generated file autosetup/jimsh0.c

[Julian Andres Klode]

Package: src:openocd
Severity: serious

jimsh0.c is a generated bootstrap version of jimtcl. Please
repackage the tarball to remove it, and build-depend on jimtcl
instead (for example).

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

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

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#882720: src:fossil: Contains generated file autosetup/jimsh0.c

[Julian Andres Klode]

Package: src:fossil
Severity: serious

jimsh0.c is a generated bootstrap version of jimtcl. Please
repackage the tarball to remove it, and build-depend on jimtcl
instead (for example).

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

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

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#882718: ruby-multi-xml FTBFS: test failure

[Adrian Bunk]

Source: ruby-multi-xml
Version: 0.5.5-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes ruby-multi-xml FTBFS:

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

...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/1st/ruby-multi-xml-0.5.5/debian/ruby-multi-xml/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-multi-xml/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
..Fatal error: Opening and ending tag mismatch: open line 1 and close at :1.
..F...

Failures:

  1) MultiXml Ox parser behaves like a parser .parse a valid XML document with 
an attribute type="yaml" returns the correctly parsed YAML when the type is 
allowed
 Failure/Error: expect(MultiXml.parse(@xml, :disallowed_types => 
[])['tag']).to eq({:message => "Have a nice day", 1 => "returns an integer", 
"array" => [{"has-dashes" => true, "has_underscores" => true}]})

   expected: {:message=>"Have a nice day", 1=>"returns an integer", 
"array"=>[{"has-dashes"=>true, "has_underscores"=>true}]}
got: "--- 1: returns an integer :message: Have a nice day array: - 
has-dashes: true has_underscores: true "

   (compared using ==)

   Diff:
   @@ -1,4 +1,2 @@
   -"array" => [{"has-dashes"=>true, "has_underscores"=>true}],
   -1 => "returns an integer",
   -:message => "Have a nice day",
   +"--- 1: returns an integer :message: Have a nice day array: - 
has-dashes: true has_underscores: true "
 Shared Example Group: "a parser" called from ./spec/multi_xml_spec.rb:37
 # ./spec/parser_shared_example.rb:320:in `block (5 levels) in '

Finished in 0.35634 seconds (files took 0.89699 seconds to load)
328 examples, 1 failure

Failed examples:

rspec ./spec/multi_xml_spec.rb[1:5:1:1:4:18:2] # MultiXml Ox parser behaves 
like a parser .parse a valid XML document with an attribute type="yaml" returns 
the correctly parsed YAML when the type is allowed

/usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-multi-xml-0.5.5/debian/ruby-multi-xml returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1

Bug#882717: src:neomutt: Generated file autosetup/jimsh0.c without source code

[Julian Andres Klode]

Package: neomutt
Version: 20171027-1
Severity: serious


neomutt embeds a copy of jimtcl that is a generated bootstrap
version of jimtcl. The file needs to be removed. It seems likely
that we could just build-depend on jimtcl and use its jimsh or
whatever it's called.

-- Package-specific info:
NeoMutt 20171027
Copyright (C) 1996-2016 Michael R. Elkins and others.
NeoMutt comes with ABSOLUTELY NO WARRANTY; for details type `neomutt -vv'.
NeoMutt is free software, and you are welcome to redistribute it
under certain conditions; type `neomutt -vv' for details.

System: Linux 4.13.0-1-amd64 (x86_64)
ncurses: ncurses 6.0.20170902 (compiled with 6.0)
libidn: 1.33 (compiled with 1.33)
hcache backends: tokyocabinet

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 7.2.0-16' 
--with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-7 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto 
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.2.0 (Debian 7.2.0-16) 

Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-lua' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-notmuch' '--disable-fmemopen' 
'--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' 
'--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm' 
'--with-tokyocabinet' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/neomutt-20171027=. -fstack-protector-strong -Wformat 
-Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now' 
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -g -O2 
-fdebug-prefix-map=/build/neomutt-20171027=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-delete-null-pointer-checks

Default options:
  +attach_headers_color +compose_to_sender +compress +cond_date 
  +encrypt_to_self +forgotten_attachments +forwref +ifdef +imap +index_color 
  +initials +limit_current_thread +multiple_fcc +nested_if +new_mail +nntp +pop 
  +progress +quasi_delete +regcomp +reply_with_xorig +sensible_browser +sidebar 
  +skip_quoted +smtp +status_color +timeout +tls_sni +trash 

Compile options:
  +bkgdset +color +curs_set +debug +fcntl -flock -fmemopen +futimens 
  +getaddrinfo +gnutls +gpgme +gss +hcache -homespool +idn -locales_hack +lua 
  +meta +mixmaster +nls +notmuch -openssl +pgp +resizeterm +sasl +smime 
  +start_color +sun_attachment +typeahead 
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/neomutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"

To learn more about NeoMutt, visit: http://www.neomutt.org/
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to: 


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

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

Versions of packages neomutt depends on:
ii  libassuan02.4.3-3
ii  libc6 2.24-17
ii  libcomerr21.43.7-1
ii  libgnutls30   3.5.16-1
ii  libgpg-error0 1.27-5
ii  libgpgme111.9.0-6
ii  libgssapi-krb5-2  

Bug#859852: marked as done (telegram-desktop: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 22:48:48 +
with message-id 
and subject line Bug#859852: fixed in telegram-desktop 1.1.23-2
has caused the Debian Bug report #859852,
regarding telegram-desktop: 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.)


-- 
859852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: telegram-desktop
Version: 1.0.14-1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle.

Sebastian
--- End Message ---
--- Begin Message ---
Source: telegram-desktop
Source-Version: 1.1.23-2

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

Debian distribution maintenance software
pp.
Nicholas Guriev  (supplier of updated telegram-desktop 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: Sat, 25 Nov 2017 10:28:23 +0300
Source: telegram-desktop
Binary: telegram-desktop
Architecture: source
Version: 1.1.23-2
Distribution: unstable
Urgency: medium
Maintainer: Nicholas Guriev 
Changed-By: Nicholas Guriev 
Description:
 telegram-desktop - official telegram messaging app
Closes: 859172 859852
Changes:
 telegram-desktop (1.1.23-2) unstable; urgency=medium
 .
   * Add Use-OpenSSL-v1.1.patch to migrate to OpenSSL 1.1 (closes: #859852)
   * Add libappindicator as recommended packages (closes: #859172)
   * Bump standards version, no changes
Checksums-Sha1:
 49c7fcbe367d7aa34bf4d006a4302b8878c83fac 2319 telegram-desktop_1.1.23-2.dsc
 cd627e2274435a8c57395648b03f480f5f1d0341 17820 
telegram-desktop_1.1.23-2.debian.tar.xz
 41dae51ec05f04c60fdd8186bd3d863767bb1687 16070 
telegram-desktop_1.1.23-2_amd64.buildinfo
Checksums-Sha256:
 d3da65d11f0d81291b0a8d87f2216f6dbb181330b49019dd3e4033d63d4a2d3a 2319 
telegram-desktop_1.1.23-2.dsc
 9c7da9b0ad4114dfca2922e3bcda9f492faa15ab58b0ddd1ab0c5cf2f734456b 17820 
telegram-desktop_1.1.23-2.debian.tar.xz
 7f2735bdaaa93e7af7f33f6e0cd8a667852142be0a2dc2b73d80b7dc6cda73c8 16070 
telegram-desktop_1.1.23-2_amd64.buildinfo
Files:
 4a543a0c6dbc5a086634b41fd9d40ed6 2319 net optional 
telegram-desktop_1.1.23-2.dsc
 31ef36e20b52c8b111b87699b8e7673c 17820 net optional 
telegram-desktop_1.1.23-2.debian.tar.xz
 57b65a907f015096e41f1e113829c6cb 16070 net optional 
telegram-desktop_1.1.23-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAloZ7bQACgkQCBa54Yx2
K60+UQ/+KTKXYsfFfOeNB06JtKCRCY0AWH+JCsfppMGTYuvhlDDSkn/7p+vB/s/Z
IwnVapfaF8JwYeOIKrKhn7/+LNYc5VEsi9WRaVGKJee68zeFQy0mFXiTY8JKWzYs
XAbY6QcZHWFwJCgyl1GQOAV65VaMQ7ndwJ0YUgrCdaUUjc1OzWyGTHQNgCwWs/e3
MgiRYdOCJ4GyQzN+B0pUHwoiypMDtbau/F3PNhXtU7b3ZXVPCtDc1RI2LvJdusIZ
h0jDUoe2Zshv50fmX7kvKYZP5lZLK3uNLOG0oHfajNeTL2wEOcx65JMBB1WHIiOf
ng7qkyh1gHfr/qMhw2uDgZzWbsQ9LwCaSY4uLApt0knJRrVqtWFO9+/jj01LOqti
T64m2u6xMGDRsAsUj2wjtLCsmgi9Mhq1HKfoUHzubJ+Bd3Q988zrjHL2mxU6g3X2
3Kvfxs5uCMBnGOqA3c+NDEIqRiQ30Qad2OKmezD4nhTxcyYeNvGSY7B0n6o0l5g2
etoLA5GAdRhRq0hiMrml9FTc3ahoa3ZXr+QnIffDX/6fZNCoSmt2C5KzRt1rfeeI
tdzdTqjmQaRxEzmpfynnHw6lLhB2SnuWhHvKePjzL2osCIgd5/CfbxZ1w+15C0F0
vfBouwh/5y/gMsx5Xjw3YuxocIP81F4rb7tfxYHIqsPewBTqWfc=
=vIWN
-END PGP SIGNATURE End Message ---

Bug#873414: Temporary solution

[Lisandro Damián Nicanor Pérez Meyer]

I have tried to update qtcreator and it sadly needs a new qbs.

I don't know if I'll have the time to do that, but I can disable llvm/clang
support to let you finish with the removal.

Please ping me if you need that (CCing me on IRC ;-) )

Cheers!

Bug#876589: welcome to amazon zu

[Thrhonda Thomas]

Confirmed

On Nov 25, 2017 12:20 PM, "confirmation needed" 
wrote:

> welcome to amazon
> 
>
>
> 
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sat, 25 Nov 2017 17:49:23 + with message-id and
> subject line Bug#876589: fixed in libtasn1-6 4.12-3 has caused the Debian
> Bug report #876589, regarding libtasn1-6 FTBFS with gtk-doc-tools 1.26:
> gtkdoc-mktmpl is no longer available 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.) -- 876589:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876589 Debian Bug
> Tracking System Contact ow...@bugs.debian.org with problems
>
> -- Forwarded message --
> From: Adrian Bunk 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Sun, 24 Sep 2017 00:58:00 +0300
> Subject: libtasn1-6 FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no
> longer available
> Source: libtasn1-6
> Version: 4.12-2.1
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/
> unstable/amd64/libtasn1-6.html
>
> ...
> Making all in reference
> make: Entering directory '/build/1st/libtasn1-6-4.12/doc/reference'
>   DOC   Scanning header files
>   DOC   Rebuilding template files
> /bin/bash: gtkdoc-mktmpl: command not found
> Makefile:1240: recipe for target 'tmpl-build.stamp' failed
> make: ***  Error 127
>
>
>
> -- Forwarded message --
> From: Andreas Metzler 
> To: 876589-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 25 Nov 2017 17:49:23 +
> Subject: Bug#876589: fixed in libtasn1-6 4.12-3
> Source: libtasn1-6
> Source-Version: 4.12-3
>
> We believe that the bug you reported is fixed in the latest version of
> libtasn1-6, 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 876...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Andreas Metzler  (supplier of updated libtasn1-6
> 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: Sat, 25 Nov 2017 17:50:16 +0100
> Source: libtasn1-6
> Binary: libtasn1-6-dev libtasn1-doc libtasn1-6 libtasn1-bin
> Architecture: source
> Version: 4.12-3
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian GnuTLS Maintainers  alioth.debian.org>
> Changed-By: Andreas Metzler 
> Closes: 876589 878658
> Description:
>  libtasn1-6-dev - Manage ASN.1 structures (development)
>  libtasn1-6 - Manage ASN.1 structures (runtime)
>  libtasn1-bin - Manage ASN.1 structures (binaries)
>  libtasn1-doc - Manage ASN.1 structures (documentation)
> Changes:
>  libtasn1-6 (4.12-3) unstable; urgency=medium
>  .
>* Always set --disable-gtk-doc-pdf", we never shipped/built these since
>  dblatex rdeps are gigantic.
>* 10_modernize_gtkdoc.diff: Update gtk-doc.make, m4/gtk-doc.m4 and
>  doc/reference/Makefile.am from gtk-doc git head (that is 1.26 +
>  c08cc78562c59082fc83b55b58747177510b7a70).
>  Run gtkdoc-check, but only show result without throwing a testsuite
> error.
>  Also use gtkdocentities in main SGML file. Closes: #876589
>* Drop libtasn1-3-bin transition package. Closes: #878658
>*  Drop trailing whitespace in changelog.
>*  Sync priorities with override file.
>*  Point watchfile to https URL.
>* Upgrade to dh compat 10:
>  - Bump d-d on debhelper, drop b-d on dh-autoreconf and dpkg-dev (>=
>1.17.14) since they are pulled in by recent debhelper.
>  - Stop passing --parallel --with autoreconf to dh, both are enabled by
>default.
>* Set Rules-Requires-Root: no.
> Checksums-Sha1:
>  6812bdc0fb01d35a628d0d3f6f53d5be75b47ccb 2574 libtasn1-6_4.12-3.dsc
>  ba4f1b6e91d90cb3345e23712cf89f416e2077ab 488 libtasn1-6_4.12.orig.tar.gz.
> asc
>  

Bug#882605: Pending fixes for bugs in the uima-as package

[pkg-java-maintainers]

tag 882605 + pending
thanks

Some bugs in the uima-as package are closed in revision
94c6ea86573020a72741e76a1c1cc8e3a5440e70 in branch 'master' by tony
mancill

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/uima-as.git/commit/?id=94c6ea8

Commit message:

Add missing build-dep on libcommons-net-java (Closes: #882605)

Processed: Pending fixes for bugs in the uima-as package

[Debian Bug Tracking System]

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

> tag 882605 + pending
Bug #882605 {Done: tony mancill } [src:uima-as] uima-as 
FTBFS without libcommons-net-java
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882605: marked as done (uima-as FTBFS without libcommons-net-java)

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 21:49:25 +
with message-id 
and subject line Bug#882605: fixed in uima-as 2.3.1-7
has caused the Debian Bug report #882605,
regarding uima-as FTBFS without libcommons-net-java
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.)


-- 
882605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uima-as
Version: 2.3.1-6
Severity: serious

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

...
[INFO] 
[INFO] 
[INFO] Skipping UIMA-AS: uima-as
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] UIMA-AS: uima-as-parent  SUCCESS [  1.154 s]
[INFO] UIMA-AS: uimaj-as-core . SUCCESS [ 13.964 s]
[INFO] UIMA-AS: uimaj-as-jms .. SUCCESS [  4.314 s]
[INFO] UIMA-AS: uimaj-as-activemq . FAILURE [  0.093 s]
[INFO] UIMA AS: uimaj-as-osgi-runtime . SKIPPED
[INFO] UIMA-AS Aggregate: aggregate-uima-as-eclipse-plugins SKIPPED
[INFO] UIMA-AS Aggregate: aggregate-uima-as ... SKIPPED
[INFO] UIMA-AS: uima-as ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 20.193 s
[INFO] Finished at: 2018-12-27T02:55:37-12:00
[INFO] Final Memory: 29M/877M
[INFO] 
[ERROR] Failed to execute goal on project uimaj-as-activemq: Could not resolve 
dependencies for project org.apache.uima:uimaj-as-activemq:jar:2.3.1: Cannot 
access eclipsePlugins (http://repo1.maven.org/eclipse) in offline mode and the 
artifact commons-net:commons-net:jar:debian has not been downloaded from it 
before. -> [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/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :uimaj-as-activemq
dh_auto_build: cd uima-as && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/uima-as-2.3.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/uima-as-2.3.1/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/uima-as-2.3.1/debian 
-Dmaven.repo.local=/build/1st/uima-as-2.3.1/debian/maven-repo --batch-mode 
package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true 
-Dlocale=en_US returned exit code 1
debian/rules:9: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1


The bug might be missing dependency on libcommons-net-java
in a build dependency.
--- End Message ---
--- Begin Message ---
Source: uima-as
Source-Version: 2.3.1-7

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated uima-as 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: 

Bug#882698: Acknowledgement (Chromium 62/63 media router cast segfaults browser, possible security implications)

[wei hong]

Appears related

https://www.reddit.com/r/GalliumOS/comments/6lyho7/chromium_stopped_working_with_my_google_account/

Bug#882698: Acknowledgement (Chromium 62/63 media router cast segfaults browser, possible security implications)

[wei hong]

Another possibly related thread

https://bugs.archlinux.org/task/51832

Bug#878539: marked as done (libsodium: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 21:19:37 +
with message-id 
and subject line Bug#878539: fixed in libsodium 1.0.15-2
has caused the Debian Bug report #878539,
regarding libsodium: Incomplete debian/copyright?
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.)


-- 
878539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsodium
Version: 1.0.15-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Laszlo Boszormenyi (GCS) 

Hi,

I just ACCEPTed libsodium from NEW but noticed it was missing 
attribution in debian/copyright for at least Thomas Pornin in
src/libsodium/crypto_pwhash/argon2/argon2-encoding.c.

This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: libsodium
Source-Version: 1.0.15-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated libsodium 
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, 16 Oct 2017 17:50:26 +
Source: libsodium
Binary: libsodium23 libsodium-dev libsodium-dbg
Architecture: source amd64
Version: 1.0.15-2
Distribution: experimental
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libsodium-dbg - Network communication, cryptography and signaturing library - 
deb
 libsodium-dev - Network communication, cryptography and signaturing library - 
hea
 libsodium23 - Network communication, cryptography and signaturing library
Closes: 878539
Changes:
 libsodium (1.0.15-2) experimental; urgency=medium
 .
   * Update copyright to match current upstream source (closes: #878539).
Checksums-Sha1:
 bea109e7518848aec8211d32c92f9bc8bc17c19e 1970 libsodium_1.0.15-2.dsc
 75403018d879d4d1c4752d33b130a921e10f21a0 7080 libsodium_1.0.15-2.debian.tar.xz
 a56b22beb521fa3e5024a4893496d23a63d46606 439168 
libsodium-dbg_1.0.15-2_amd64.deb
 1f93287c3e014131e14bcda1935f7b4c606f7b86 172672 
libsodium-dev_1.0.15-2_amd64.deb
 83f3b7d595f37335c34ec4677699d2f79841319a 155416 libsodium23_1.0.15-2_amd64.deb
 f8689eb850b4c32085577326643d95a17f4d3339 6808 
libsodium_1.0.15-2_amd64.buildinfo
Checksums-Sha256:
 517bfcc23871376238522c26f8f5a7e6954c33e709a925f12868bb4ab8f85fc5 1970 
libsodium_1.0.15-2.dsc
 51369340b041caa2bfb6f51550f623dbf88c878a4cd90c4b00e48425e658570d 7080 
libsodium_1.0.15-2.debian.tar.xz
 74d83ac0e13229a62e94d9cf35b3dff5af2fd4ab5492827404f4797392f4d4e1 439168 
libsodium-dbg_1.0.15-2_amd64.deb
 7707a172f9467e6798909f9079651d604a1afba9d1928eae9316f7db587d7f28 172672 
libsodium-dev_1.0.15-2_amd64.deb
 b45e8455cfd48d1578fc96f4d2af8b1518a80c1e170ac16f9cc24ccd5aabc691 155416 
libsodium23_1.0.15-2_amd64.deb
 3a2d87928f2aae3176a1408784b09b9aaed3dda6e27c0b0a9dd3222d690d24d5 6808 
libsodium_1.0.15-2_amd64.buildinfo
Files:
 5aead9be308bd56a66fc0eca91844b16 1970 libs optional libsodium_1.0.15-2.dsc
 60eb68aacc90867a932b67b930358c24 7080 libs optional 
libsodium_1.0.15-2.debian.tar.xz
 9aeb21489832441dee1292e7bef5cbda 439168 debug optional 
libsodium-dbg_1.0.15-2_amd64.deb
 44142898435ceafb043308ce4ff8d1f0 172672 libdevel optional 
libsodium-dev_1.0.15-2_amd64.deb
 ef7a111c4203f0916b0a4a99d0fd 155416 libs optional 
libsodium23_1.0.15-2_amd64.deb
 cfd9a40188764b9e6a93d7e18183f7a2 6808 libs optional 
libsodium_1.0.15-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAloZ2y0ACgkQ3OMQ54ZM
yL9G5A/6Aq5w8qVCmz44qRZD8o3SsKLk3y88dj3UIx5IvpQjnwCnscVy56uRSu5p
dDWP6343qbulzUAiAv/fO80AXogLKcK4GS2msydhz38VMxcJMz+TyboT8hlpNeuJ
VU6lJeHN69NBcEK0ws1hCrwW0Pbkn9rhC+76L/EHTq3050UB1wm96GAv7GLZOkIo

Bug#876191: most: configure cannot be built from source

[Benj. Mako Hill]

Greetings Helmut!

Thanks for engaging productively on this!


> I deliberately avoided the FTBFS language, because it is not a FTBFS.
> It's different. It's like shipping a binary that cannot be regenerated
> and using that during build. The term FTBFS is well defined and does not
> cover this case.

Got it. We agree about that.

I'm don't think we agree on what constitutes the source for this
package. Until we do, I think a more descriptive title might be
better. Something like: "configure file cannot be regenerated
automatically."

> Would you say the same if you compile a binary, use a hex editor to fix
> the binary and then ship the binary in your source package? I mean you
> preferred to edit the binary with a hex editor, so wouldn't it be
> preferred form for modification?

I agree that a hand-modified binary a binary would not mean that you
don't need to provide source for that binary. I think there's likely
going to be consensus on that in Debian.

I also think this situation is different because I think that a
configure file is more like computer-generated, hand-modified,
/source/ than like a binary.

I think one could also argue that there is an difference between the
program binary and a build script which is used to build the package
in question.

> Also consider that autoconf projects tend to ship embedded copies of
> .m4 files. A bug in those .m4 files is often fixed upstream. Fixing
> it could be a simple matter of updating the embedded copy if one
> could regenerate configure.
> 
> In both of these examples, I very much do not prefer working with
> the generated configure as it feels very much like editing a binary
> with a hex editor. Thus I argue that configure is not the preferred
> form for modification. Shipping only configure makes DFGS #3
> practically moot.

To say that DFSG#3 is moot (i.e., that you /can not/ make
modifications or derived versions) seems to me to be an
exaggeration. It is more difficult than it might be if the software
and build scripts were created in a different way. But that's not
necessary a DFSG issue. Writing your software in a obscure programming
language makes it harder to modify as well and that is obviously
allowed.

Are you willing to say that source code can never contain code that
was partially generated by another program that is provided? Even if
it is generated by computers and then modified by hand? That's a much
stronger position than I think is supportable by any reading of the
DFSG than I've ever heard and it would eliminate many hundreds or even
thousands of packages from Debian.

> > If this has been discussed elsewhere or if there is Debian policy
> > on this I don't know about, I'd appreciate being pointed to this
> > and I'm happy to defer to this. In the meantime, I'd appreciate
> > help fixing this issue. I'm not likely to have bandwidth for a few
> > more weeks.
> 
> I guess we should document this issue class centrally. It is similar
> to the javascript bundling issue (where people suppose that minified
> or concatenated javascript files could be considered source).

This is distinctly different. The source code in the JS example is
obviously not minified the Javascript if we use the GPL's "preferred
form for modification" heuristic regardless of the change in
question. If upstream wanted to make a change to the Javascript in
their program, they would almost never use the minified version. If
most's upstream wanted to make a change to their configure file, they
would likely modify the pre-built version. Or they would go through
rebuilding it again.

> This issue comes about every time Debian is bootstrapped for a new
> architecture as configure tends to have bugs (e.g. ppc64el). I'm
> seeing it now as I bootstrap Debian for something like a new
> architecture (cross building). So this is the class of bugs to watch
> out.

I agree! But I think that having packages removed from testing (as has
now happened to most) over this interpretation is an overreaction to
what I think constitutes an annoyance.

I think that the main goal should be focusing on trying to fix these
bugs. I think a secondary goal should be discussing this in a
systematic way to get some sort of consensus.

Until then, my sense is to reduce the severity of this (likely to
normal) and to retitle the bug as described above. As I said, I think
this is a real bug. I just don't agree that it's a showstopper or a
DFSG issue.

Regards,
Mako


-- 
Benjamin Mako Hill
http://mako.cc/

Creativity can be a social contribution, but only in so far
as society is free to use the results. --GNU Manifesto


signature.asc
Description: PGP signature

Bug#851084: let's NMU this then

[Adam Borowski]

Control: tags -1 +pending

As Philip Chung's patch sits here rotting, I prepared a NMU with it.
Will upload to DELAYED/7 shortly, here's the debdiff.
Please scream if anything is wrong.

-- 
⢀⣴⠾⠻⢶⣦⠀ Mozilla's Hippocritical Oath: "Keep trackers off your trail"
⣾⠁⢰⠒⠀⣿⡁ blah blah evading "tracking technology" blah blah
⢿⡄⠘⠷⠚⠋⠀ "https://click.e.mozilla.org/?qs=e7bb0dcf14b1013fca3820...;
⠈⠳⣄ (same for all links)
diff -Nru crtmpserver-1.0~dfsg/debian/changelog 
crtmpserver-1.0~dfsg/debian/changelog
--- crtmpserver-1.0~dfsg/debian/changelog   2016-12-30 17:40:06.0 
+0100
+++ crtmpserver-1.0~dfsg/debian/changelog   2017-11-25 16:06:37.0 
+0100
@@ -1,3 +1,10 @@
+crtmpserver (1.0~dfsg-5.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * SSL1.1, patch by Philip Chung (Closes: #851084).
+
+ -- Adam Borowski   Sat, 25 Nov 2017 16:06:37 +0100
+
 crtmpserver (1.0~dfsg-5.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru crtmpserver-1.0~dfsg/debian/control 
crtmpserver-1.0~dfsg/debian/control
--- crtmpserver-1.0~dfsg/debian/control 2016-12-30 17:40:03.0 +0100
+++ crtmpserver-1.0~dfsg/debian/control 2017-11-25 16:06:37.0 +0100
@@ -9,7 +9,7 @@
  cmake,
  debhelper (>= 9),
  liblua5.1-0-dev,
- libssl1.0-dev,
+ libssl-dev,
  libtinyxml-dev,
  pkg-config
 Standards-Version: 3.9.3
diff -Nru crtmpserver-1.0~dfsg/debian/patches/libssl_1_1_compatibility.diff 
crtmpserver-1.0~dfsg/debian/patches/libssl_1_1_compatibility.diff
--- crtmpserver-1.0~dfsg/debian/patches/libssl_1_1_compatibility.diff   
1970-01-01 01:00:00.0 +0100
+++ crtmpserver-1.0~dfsg/debian/patches/libssl_1_1_compatibility.diff   
2017-11-25 16:06:37.0 +0100
@@ -0,0 +1,277 @@
+Description: allow the package to build against OpenSSL 1.1
+ Notice, however, that I inelegantly replace BaseSSLProtocol::DumpBIO()
+ in thelib/src/protocols/ssl/basesslprotocol.cpp with a stub function,
+ because I can't seem to find any way to access the data.
+ .
+ Actually, removing the method entirely still allows the package to
+ build, as no other part of the code actually uses it. Would it be safe
+ to do so?
+Author: Philip Chung 
+Bug-Debian: https://bugs.debian.org/851084
+
+--- 
crtmpserver-1.0~dfsg.orig/applications/applestreamingclient/include/protocols/aes/inboundaesprotocol.h
 
crtmpserver-1.0~dfsg/applications/applestreamingclient/include/protocols/aes/inboundaesprotocol.h
+@@ -30,7 +30,7 @@ namespace app_applestreamingclient {
+   private:
+   IOBuffer _tempBuffer;
+   IOBuffer _inputBuffer;
+-  EVP_CIPHER_CTX _decContex;
++  EVP_CIPHER_CTX *_decContex;
+   bool _lastChunk;
+   uint8_t *_pIV;
+   uint8_t *_pKey;
+--- 
crtmpserver-1.0~dfsg.orig/applications/applestreamingclient/src/protocols/aes/inboundaesprotocol.cpp
 
crtmpserver-1.0~dfsg/applications/applestreamingclient/src/protocols/aes/inboundaesprotocol.cpp
+@@ -31,13 +31,12 @@ InboundAESProtocol::InboundAESProtocol()
+   memset(_pIV, 0, 16);
+   _pKey = new uint8_t[16];
+   memset(_pKey, 0, 16);
+-  memset(&_decContex, 0, sizeof (EVP_CIPHER_CTX));
++  _decContex = EVP_CIPHER_CTX_new();
+   _totalDecrypted = 0;
+ }
+ 
+ InboundAESProtocol::~InboundAESProtocol() {
+-  EVP_CIPHER_CTX_cleanup(&_decContex);
+-  memset(&_decContex, 0, sizeof (EVP_CIPHER_CTX));
++  EVP_CIPHER_CTX_free(_decContex);
+   delete[] _pIV;
+   delete[] _pKey;
+ }
+@@ -60,11 +59,9 @@ bool InboundAESProtocol::Initialize(Vari
+   _inputBuffer.IgnoreAll();
+   _tempBuffer.IgnoreAll();
+ 
+-  EVP_CIPHER_CTX_cleanup(&_decContex);
+-  memset(&_decContex, 0, sizeof (EVP_CIPHER_CTX));
+-  EVP_CIPHER_CTX_init(&_decContex);
+-  EVP_DecryptInit_ex(&_decContex, EVP_aes_128_cbc(), NULL, _pKey, _pIV);
+-  EVP_CIPHER_CTX_set_padding(&_decContex, 0);
++  EVP_CIPHER_CTX_init(_decContex);
++  EVP_DecryptInit_ex(_decContex, EVP_aes_128_cbc(), NULL, _pKey, _pIV);
++  EVP_CIPHER_CTX_set_padding(_decContex, 0);
+ 
+   return true;
+ }
+@@ -105,14 +102,14 @@ bool InboundAESProtocol::SignalInputData
+   int decryptedFinalSize = 0;
+   uint32_t padding = 0;
+ 
+-  EVP_DecryptUpdate(&_decContex, pTempData, , 
GETIBPOINTER(buffer), safeSize);
++  EVP_DecryptUpdate(_decContex, pTempData, , 
GETIBPOINTER(buffer), safeSize);
+   _totalDecrypted += decryptedSize;
+ 
+   //6. Decrypt leftovers
+   bool transferCompleted = false;
+   if (((HTTPBufferProtocol *) GetFarProtocol())->TransferCompleted()) {
+   transferCompleted = true;
+-  EVP_DecryptFinal_ex(&_decContex,
++  EVP_DecryptFinal_ex(_decContex,
+   pTempData + decryptedSize,
+   );
+   _totalDecrypted += decryptedFinalSize;
+--- 

Processed: let's NMU this then

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #851084 [src:crtmpserver] crtmpserver: Please migrate to openssl1.1 in 
buster
Added tag(s) pending.

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

Bug#882698: Chromium 62/63 media router cast segfaults browser, possible security implications

[wei hong]

Package: chromium
Version: 62.0.3202.89-1~deb9u1
Severity: grave
Tags: security, buster

Although --media-router=0 is the default, Chromium now randomly crashes, but 
did not crash in release 61. Only setting media-router to "2" in the Chromium 
"Local State" file fixes the issue temporarily, but still with random crashes. 
Something is really broken in the media router or cast functionality after 
updating to chromium 62/63. Not sure why, but perhaps some maintainers or users 
have seen similar issues? This appears to have broken between the update from 
61 to 62.

>From /etc/chromium.d/default-flags:
# Disable the builtin media router (bug #833477)
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --media-router=0"

$ chromium
Received signal 11 SEGV_MAPERR 0010
#0 0x55aa4d3d6f56 
#1 0x55aa4bfa3a58 
#2 0x55aa4d3d72dc 
#3 0x7fa33249d0c0 
#4 0x55aa4c8c85ba 
#5 0x55aa4c8c943d 
#6 0x55aa4c8c9a4d 
#7 0x55aa4c8c9bb5 
#8 0x55aa4d43af19 
#9 0x55aa4d3d8136 
#10 0x55aa4d3f7318 
#11 0x55aa4d3f7a1f 
#12 0x55aa4d3f86c6 
#13 0x55aa4d3fa822 
#14 0x55aa4d41fffb 
#15 0x55aa4d43fd58 
#16 0x55aa4d43ae10 
#17 0x7fa332493494 start_thread
#18 0x7fa326e2dabf clone
  r8: 0001  r9: 55aa5017290c r10: 55aa50172910 r11: 
7fa326eaee20
 r12: 0008 r13: 7fa2e8b1cdf0 r14: 7fa2e8b1d000 r15: 

  di:   si: 7fa2e8b1cdf0  bp: 7fa2e8b1cf10  bx: 
0008
  dx: 0004  ax: 222ad12c4300  cx:   sp: 
7fa2e8b1cd90
  ip: 55aa4c8c85ba efl: 00010206 cgf: 002b0033 erf: 
0004
 trp: 000e msk:  cr2: 0010
[end of stack trace]
Calling _exit(1). Core file will not be generated.

To get chromium to launch without crashing, use:
$ sed -i 
's/load-media-router-component-extension@./load-media-router-component-extension@2/'
 ~/.config/chromium/Local\ State

This should disable the media router extension and allow you to run chromium 
again without it immediately crashing.
Either the media router should be fixed since this is a blocking bug, or media 
router should be removed. From past experience, the media router or casting 
functionality has been semi broken or only half working for some time. It 
appears to work sometimes, but not others, or crashes during use. As it stands 
now, perhaps permanently removing the functionality is best until it is 
rigorously tested for quality and security issues. This issue may even be 
exploitable due to the segmentation fault parameters that might be controllable 
over the network to attack the media router component.

Processed: severity of 784514 is important

[Debian Bug Tracking System]

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

> severity 784514 important
Bug #784514 {Done: Sebastiaan Couwenberg } [src:qgis] 
[qgis] Qt4's WebKit removal
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: severity of 882663 is important

[Debian Bug Tracking System]

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

> severity 882663 important
Bug #882663 [src:qgis] [qgis] Qt4's WebKit removal
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#882663: serverity important because qtwebkit is still in testing

[Sebastiaan Couwenberg]

Control: tags -1 important

On 11/25/2017 07:53 PM, Adrian Bunk wrote:
> On Sat, Nov 25, 2017 at 12:59:54PM +0100, Sebastiaan Couwenberg wrote:
>> Control: severity -1 important
>>
>> The serious severity is not appropriate as long as qtwebkit is still in
>> testing
> 
> And how should qtwebkit get removed from testing without RC bugs on the
> reverse dependencies first?
By filing an RM bug and having all remaining issues block that, and
whose severity is then raised.

> Due to RC bugs 28 of the 34 reverse dependencies have already been 
> removed from testing, and qgis is one of only 6 packages left.
> 
> Do you agree to testing removal of qgis without any further
> advance notice whenever qtwebkit testing removal is ready?
> 
> The only advance notice you can expect is this bug.
> 
>> and no definitive removal date is known.
> 
> testing removal of qtwebkit is only pending on the upload of
> a few more KDE packages.
> 
> December 2017 is a realistic date for removal from testing.
> 
> In the worst case it will happen in January 2018.

I'll believe it when I see it, previous experience with python-qt4 show
that it may take significantly more time.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: Bug#882663: serverity important because qtwebkit is still in testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #882663 [src:qgis] [qgis] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Bug#876589: welcome to amazon Oe

[Reather Harris]

What

On Nov 25, 2017 2:20 PM, "confirmation needed" 
wrote:
>
> welcome to amazon
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sat, 25 Nov 2017 17:49:23 + with message-id and
subject line Bug#876589: fixed in libtasn1-6 4.12-3 has caused the Debian
Bug report #876589, regarding libtasn1-6 FTBFS with gtk-doc-tools 1.26:
gtkdoc-mktmpl is no longer available 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.) -- 876589:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876589 Debian Bug
Tracking System Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Adrian Bunk 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Sun, 24 Sep 2017 00:58:00 +0300
> Subject: libtasn1-6 FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no
longer available
> Source: libtasn1-6
> Version: 4.12-2.1
> Severity: serious
>
>
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libtasn1-6.html
>
> ...
> Making all in reference
> make: Entering directory '/build/1st/libtasn1-6-4.12/doc/reference'
>   DOC   Scanning header files
>   DOC   Rebuilding template files
> /bin/bash: gtkdoc-mktmpl: command not found
> Makefile:1240: recipe for target 'tmpl-build.stamp' failed
> make: ***  Error 127
>
>
>
> -- Forwarded message --
> From: Andreas Metzler 
> To: 876589-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 25 Nov 2017 17:49:23 +
> Subject: Bug#876589: fixed in libtasn1-6 4.12-3
> Source: libtasn1-6
> Source-Version: 4.12-3
>
> We believe that the bug you reported is fixed in the latest version of
> libtasn1-6, 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 876...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Andreas Metzler  (supplier of updated libtasn1-6
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: Sat, 25 Nov 2017 17:50:16 +0100
> Source: libtasn1-6
> Binary: libtasn1-6-dev libtasn1-doc libtasn1-6 libtasn1-bin
> Architecture: source
> Version: 4.12-3
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian GnuTLS Maintainers <
pkg-gnutls-ma...@lists.alioth.debian.org>
> Changed-By: Andreas Metzler 
> Closes: 876589 878658
> Description:
>  libtasn1-6-dev - Manage ASN.1 structures (development)
>  libtasn1-6 - Manage ASN.1 structures (runtime)
>  libtasn1-bin - Manage ASN.1 structures (binaries)
>  libtasn1-doc - Manage ASN.1 structures (documentation)
> Changes:
>  libtasn1-6 (4.12-3) unstable; urgency=medium
>  .
>* Always set --disable-gtk-doc-pdf", we never shipped/built these since
>  dblatex rdeps are gigantic.
>* 10_modernize_gtkdoc.diff: Update gtk-doc.make, m4/gtk-doc.m4 and
>  doc/reference/Makefile.am from gtk-doc git head (that is 1.26 +
>  c08cc78562c59082fc83b55b58747177510b7a70).
>  Run gtkdoc-check, but only show result without throwing a testsuite
error.
>  Also use gtkdocentities in main SGML file. Closes: #876589
>* Drop libtasn1-3-bin transition package. Closes: #878658
>*  Drop trailing whitespace in changelog.
>*  Sync priorities with override file.
>*  Point watchfile to https URL.
>* Upgrade to dh compat 10:
>  - Bump d-d on debhelper, drop b-d on dh-autoreconf and dpkg-dev (>=
>1.17.14) since they are pulled in by recent debhelper.
>  - Stop passing --parallel --with autoreconf to dh, both are enabled
by
>default.
>* Set Rules-Requires-Root: no.
> Checksums-Sha1:
>  6812bdc0fb01d35a628d0d3f6f53d5be75b47ccb 2574 libtasn1-6_4.12-3.dsc
>  ba4f1b6e91d90cb3345e23712cf89f416e2077ab 488
libtasn1-6_4.12.orig.tar.gz.asc
>  24678bccf7cd6b3487b2a8821a2db25c09b7d8ba 63976
libtasn1-6_4.12-3.debian.tar.xz
> Checksums-Sha256:
>  e281b1f2e1181551e8a693ecf924ddb4a784a475a9fd1d444f8b80042bb45ff5 2574
libtasn1-6_4.12-3.dsc
>  469560e75534a5842916669930bcd97cec0400f49b5358fd962fa1c32475fe61 488
libtasn1-6_4.12.orig.tar.gz.asc
>  

Bug#876589: welcome to amazon U0fq

[Lu Ann Strandt]

This is not me!

On Nov 25, 2017 10:20 AM, "confirmation needed" 
wrote:

> welcome to amazon
> 
>
>
> 
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Your message dated Sat, 25 Nov 2017 17:49:23 + with message-id and
> subject line Bug#876589: fixed in libtasn1-6 4.12-3 has caused the Debian
> Bug report #876589, regarding libtasn1-6 FTBFS with gtk-doc-tools 1.26:
> gtkdoc-mktmpl is no longer available 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.) -- 876589:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876589 Debian Bug
> Tracking System Contact ow...@bugs.debian.org with problems
>
> -- Forwarded message --
> From: Adrian Bunk 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Sun, 24 Sep 2017 00:58:00 +0300
> Subject: libtasn1-6 FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no
> longer available
> Source: libtasn1-6
> Version: 4.12-2.1
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/
> unstable/amd64/libtasn1-6.html
>
> ...
> Making all in reference
> make: Entering directory '/build/1st/libtasn1-6-4.12/doc/reference'
>   DOC   Scanning header files
>   DOC   Rebuilding template files
> /bin/bash: gtkdoc-mktmpl: command not found
> Makefile:1240: recipe for target 'tmpl-build.stamp' failed
> make: ***  Error 127
>
>
>
> -- Forwarded message --
> From: Andreas Metzler 
> To: 876589-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 25 Nov 2017 17:49:23 +
> Subject: Bug#876589: fixed in libtasn1-6 4.12-3
> Source: libtasn1-6
> Source-Version: 4.12-3
>
> We believe that the bug you reported is fixed in the latest version of
> libtasn1-6, 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 876...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Andreas Metzler  (supplier of updated libtasn1-6
> 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: Sat, 25 Nov 2017 17:50:16 +0100
> Source: libtasn1-6
> Binary: libtasn1-6-dev libtasn1-doc libtasn1-6 libtasn1-bin
> Architecture: source
> Version: 4.12-3
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian GnuTLS Maintainers  alioth.debian.org>
> Changed-By: Andreas Metzler 
> Closes: 876589 878658
> Description:
>  libtasn1-6-dev - Manage ASN.1 structures (development)
>  libtasn1-6 - Manage ASN.1 structures (runtime)
>  libtasn1-bin - Manage ASN.1 structures (binaries)
>  libtasn1-doc - Manage ASN.1 structures (documentation)
> Changes:
>  libtasn1-6 (4.12-3) unstable; urgency=medium
>  .
>* Always set --disable-gtk-doc-pdf", we never shipped/built these since
>  dblatex rdeps are gigantic.
>* 10_modernize_gtkdoc.diff: Update gtk-doc.make, m4/gtk-doc.m4 and
>  doc/reference/Makefile.am from gtk-doc git head (that is 1.26 +
>  c08cc78562c59082fc83b55b58747177510b7a70).
>  Run gtkdoc-check, but only show result without throwing a testsuite
> error.
>  Also use gtkdocentities in main SGML file. Closes: #876589
>* Drop libtasn1-3-bin transition package. Closes: #878658
>*  Drop trailing whitespace in changelog.
>*  Sync priorities with override file.
>*  Point watchfile to https URL.
>* Upgrade to dh compat 10:
>  - Bump d-d on debhelper, drop b-d on dh-autoreconf and dpkg-dev (>=
>1.17.14) since they are pulled in by recent debhelper.
>  - Stop passing --parallel --with autoreconf to dh, both are enabled by
>default.
>* Set Rules-Requires-Root: no.
> Checksums-Sha1:
>  6812bdc0fb01d35a628d0d3f6f53d5be75b47ccb 2574 libtasn1-6_4.12-3.dsc
>  ba4f1b6e91d90cb3345e23712cf89f416e2077ab 488 libtasn1-6_4.12.orig.tar.gz.
> asc
>  

Processed: retitle 882671 to exim4: CVE-2017-16944: handles BDAT data incorrectly and leads to crash ...

[Debian Bug Tracking System]

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

> retitle 882671 exim4: CVE-2017-16944: handles BDAT data incorrectly and leads 
> to crash
Bug #882671 [src:exim4] exim4: handles BDAT data incorrectly and leads to crash
Changed Bug title to 'exim4: CVE-2017-16944: handles BDAT data incorrectly and 
leads to crash' from 'exim4: handles BDAT data incorrectly and leads to crash'.
> retitle 882648 exim4: CVE-2017-16943: use-after-free vulnerability while 
> reading mail header
Bug #882648 [exim4] exim4: remote code execution in chunking
Changed Bug title to 'exim4: CVE-2017-16943: use-after-free vulnerability while 
reading mail header' from 'exim4: remote code execution in chunking'.
> tags 882648 + fixed-upstream
Bug #882648 [exim4] exim4: CVE-2017-16943: use-after-free vulnerability while 
reading mail header
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#876589: marked as done (libtasn1-6 FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 17:49:23 +
with message-id 
and subject line Bug#876589: fixed in libtasn1-6 4.12-3
has caused the Debian Bug report #876589,
regarding libtasn1-6 FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer 
available
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.)


-- 
876589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtasn1-6
Version: 4.12-2.1
Severity: serious

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

...
Making all in reference
make[5]: Entering directory '/build/1st/libtasn1-6-4.12/doc/reference'
  DOC   Scanning header files
  DOC   Rebuilding template files
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:1240: recipe for target 'tmpl-build.stamp' failed
make[5]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: libtasn1-6
Source-Version: 4.12-3

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated libtasn1-6 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: Sat, 25 Nov 2017 17:50:16 +0100
Source: libtasn1-6
Binary: libtasn1-6-dev libtasn1-doc libtasn1-6 libtasn1-bin
Architecture: source
Version: 4.12-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuTLS Maintainers 
Changed-By: Andreas Metzler 
Closes: 876589 878658
Description: 
 libtasn1-6-dev - Manage ASN.1 structures (development)
 libtasn1-6 - Manage ASN.1 structures (runtime)
 libtasn1-bin - Manage ASN.1 structures (binaries)
 libtasn1-doc - Manage ASN.1 structures (documentation)
Changes:
 libtasn1-6 (4.12-3) unstable; urgency=medium
 .
   * Always set --disable-gtk-doc-pdf", we never shipped/built these since
 dblatex rdeps are gigantic.
   * 10_modernize_gtkdoc.diff: Update gtk-doc.make, m4/gtk-doc.m4 and
 doc/reference/Makefile.am from gtk-doc git head (that is 1.26 +
 c08cc78562c59082fc83b55b58747177510b7a70).
 Run gtkdoc-check, but only show result without throwing a testsuite error.
 Also use gtkdocentities in main SGML file. Closes: #876589
   * Drop libtasn1-3-bin transition package. Closes: #878658
   * [lintian] Drop trailing whitespace in changelog.
   * [lintian] Sync priorities with override file.
   * [lintian] Point watchfile to https URL.
   * Upgrade to dh compat 10:
 - Bump d-d on debhelper, drop b-d on dh-autoreconf and dpkg-dev (>=
   1.17.14) since they are pulled in by recent debhelper.
 - Stop passing --parallel --with autoreconf to dh, both are enabled by
   default.
   * Set Rules-Requires-Root: no.
Checksums-Sha1: 
 6812bdc0fb01d35a628d0d3f6f53d5be75b47ccb 2574 libtasn1-6_4.12-3.dsc
 ba4f1b6e91d90cb3345e23712cf89f416e2077ab 488 libtasn1-6_4.12.orig.tar.gz.asc
 24678bccf7cd6b3487b2a8821a2db25c09b7d8ba 63976 libtasn1-6_4.12-3.debian.tar.xz
Checksums-Sha256: 
 e281b1f2e1181551e8a693ecf924ddb4a784a475a9fd1d444f8b80042bb45ff5 2574 
libtasn1-6_4.12-3.dsc
 469560e75534a5842916669930bcd97cec0400f49b5358fd962fa1c32475fe61 488 
libtasn1-6_4.12.orig.tar.gz.asc
 89ce2fb121bdb5f9b40745184da58470948e31033bae849e0f24c11257ee3bba 63976 
libtasn1-6_4.12-3.debian.tar.xz
Files: 
 02f8d3deb2d59e19c2cd45ff14b4e4f8 2574 libs standard libtasn1-6_4.12-3.dsc
 cd03c2c2f93abf1469f38e2cc758fa8d 488 libs standard 
libtasn1-6_4.12.orig.tar.gz.asc
 46312208e66fa38ee01310c36455f6ab 63976 libs standard 
libtasn1-6_4.12-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAloZqlAACgkQpU8BhUOC
FIRADw/+NQrbrkOYBpGUfJZ7TGHQe4v6+6ZsuwZAMhGEr1UrGWDUinLqW7KzkzOv
7llAfyT6cP6fLROpj9ntcOvHUlQeHQIL3mNaPPfRxJQvC9CjjCC30a1g+UzSaFfc
4YVSRtIpqh4XtejNDiAHFSFNdPG1Px0GdKwoR/aLBfRGUMjmtC65LQ9kaeJ57pB6
5tMBcC+Cb1EFkCftJR44UcmoQ6JuXUQvfErNaSfUR2ZCjCHLeKmdXAS6V3ADxirA

Bug#882685: onedrive: FTBFS on ppc64el: cc1d: error: cannot find source code for runtime library file 'object.d'

[Andreas Beckmann]

Source: onedrive
Version: 1.1.20170919-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

onedrive FTBFS on ppc64el:

https://buildd.debian.org/status/fetch.php?pkg=onedrive=ppc64el=1.1.20170919-2=1510732130=0

   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
make debug
make[2]: Entering directory '/<>'
gdc --debug -g -oonedrive -lcurl -lsqlite3  -J. src/config.d src/itemdb.d 
src/log.d src/main.d src/monitor.d src/onedrive.d src/qxor.d src/selective.d 
src/sqlite.d src/sync.d src/upload.d src/util.d
cc1d: error: cannot find source code for runtime library file 'object.d'
cc1d: note: dmd might not be correctly installed. Run 'dmd -man' for 
installation instructions.
(null):0: confused by earlier errors, bailing out
Makefile:24: recipe for target 'debug' failed
make[2]: *** [debug] Error 1
make[2]: Leaving directory '/<>'
debian/rules:7: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'


Andreas

Processed: Re: Bug#882659: vice: Segfault on start

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #882659 [vice] vice: Segfault on start
Added tag(s) moreinfo.

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

Bug#882659: vice: Segfault on start

[GCS]

Control: tags -1 moreinfo

On Sat, Nov 25, 2017 at 11:37 AM, Marco Presi  wrote:
> I am using vice since a long time, it always worked perfectly. Yesterday I re-
> installed it and I am not able to run it anymore.
 When was the last time you used it?

> I just type "x64" on the command line and the program segfault immediately.
> Downloading the software from the upstream website and compiling from source
> with default build options solved temporarly the problem.
 What lines you get displayed with the compiled version after the 'See
the "About VICE" command for more info.' line?

> I am attaching here the output of the debian package version. I am available 
> to
> help to solve this issue.
 Thanks in advance. I'm also interested if you have a non-free display
driver installed and/or may you have a dual monitor display.

Regards,
Laszlo/GCS

Bug#881090: marked as done (italc FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev)

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 16:49:07 +
with message-id 
and subject line Bug#881090: fixed in italc 1:3.0.3+dfsg1-2
has caused the Debian Bug report #881090,
regarding italc FTBFS: Qt5LinguistTools*.cmake moved to qttools5-dev
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.)


-- 
881090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: italc
Version: 1:3.0.3+dfsg1-1
Severity: serious
Tags: buster sid

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

...
CMake Error at CMakeLists.txt:129 (FIND_PACKAGE):
  By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Qt5LinguistTools", but CMake did not find one.

  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.


qttools-opensource-src (5.9.2-3) unstable; urgency=medium

  * Move Qt5LinguistTools*.cmake from qttools5-dev-tools to qttools5-dev.
...
--- End Message ---
--- Begin Message ---
Source: italc
Source-Version: 1:3.0.3+dfsg1-2

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated italc 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: Sat, 25 Nov 2017 17:20:02 +0100
Source: italc
Binary: italc-master italc-client italc-management-console libitalccore
Architecture: source
Version: 1:3.0.3+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Packaging Team 

Changed-By: Mike Gabriel 
Description:
 italc-client - intelligent Teaching And Learning with Computers - client
 italc-management-console - intelligent Teaching And Learning with Computers - 
management con
 italc-master - intelligent Teaching And Learning with Computers - master
 libitalccore - intelligent Teaching And Learning with Computers - libraries
Closes: 881090
Changes:
 italc (1:3.0.3+dfsg1-2) unstable; urgency=medium
 .
   * debian/control:
 + Add B-D: qttools5-dev. (Closes: #881090).
 + Bump Standards-Version: to 4.1.1. No changes needed.
   * debian/changelog, debian/man/*.1: White-space cleanup.
   * debian/copyright:
 + Remove file that is not present in upstrean sources anymore.
Checksums-Sha1:
 064887f72d97453340018b058c4c6ae6efa47687 2580 italc_3.0.3+dfsg1-2.dsc
 e1c8abc2e659087d7c4db14afc9925f7d5e6344f 70780 
italc_3.0.3+dfsg1-2.debian.tar.xz
 1bb835712070cb2d25ec7f20e050956f067bd470 14194 
italc_3.0.3+dfsg1-2_source.buildinfo
Checksums-Sha256:
 15e8187feab44a053af2a54877277a0f21076f1fa915b5ad9fc99a6fa5a27204 2580 
italc_3.0.3+dfsg1-2.dsc
 c30dca48503792a7ab718844fc3316415cf42645cd0cd13026b06025998e1e8a 70780 
italc_3.0.3+dfsg1-2.debian.tar.xz
 ad11ca0aa192de6fce1e0c68e2a38d04cb60ae062d6545eea44eb7a77ea76e12 14194 
italc_3.0.3+dfsg1-2_source.buildinfo
Files:
 d300335362b1d6965267cf75a94c785c 2580 x11 optional italc_3.0.3+dfsg1-2.dsc
 0d31036523ffa0d731f40c4bd92f028d 70780 x11 optional 
italc_3.0.3+dfsg1-2.debian.tar.xz
 1689d7edc2bababce24ea59cf46656bc 14194 x11 optional 
italc_3.0.3+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAloZmqIVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxm9AQALhD14lHmQHXiXa5wb+CjxUuhRna
GKD1RVaP56caRdQCOTTBobbl7vYptAET4+Gx4S85OsgR7e7JOPJDDDI/XYTnTyjN
zDgKL8y1KSJJ81YWwaQFDXPIEIFn3jZcFXmSPBtma0h+L5xPnIv2qorIXBI4nXMb
1KsZ7PVCpGLY3Kb0ulq/iZzAKgMLNTTLCYEV8FJyiz+wf1hKX1pkpHe3RWfwbgPp

Bug#881090: marked as pending

[Mike Gabriel]

tag 881090 pending
thanks

Hello,

Bug #881090 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/debian-edu/pkg-team/italc.git/commit/?id=d8c111a

---
commit d8c111a82940c947d4eeb0f4a9129372bd7f0327
Author: Mike Gabriel 
Date:   Sat Nov 25 17:28:16 2017 +0100

debian/changelog, debian/man/*.1: White-space cleanup.

diff --git a/debian/changelog b/debian/changelog
index cd8ec13..d0322b3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+italc (1:3.0.3+dfsg1-2) unstable; urgency=medium
+
+  * debian/control:
++ Add B-D: qttools5-dev. (Closes: #881090).
++ Bump Standards-Version: to 4.1.1. No changes needed.
+
+ -- Mike Gabriel   Sat, 25 Nov 2017 17:20:02 +0100
+
 italc (1:3.0.3+dfsg1-1) unstable; urgency=medium
 
   [ Mike Gabriel ]
@@ -434,10 +442,9 @@ italc (1:1.0.9~rc3-1) unstable; urgency=low
 
 italc (1:1.0.8-1) unstable; urgency=low
 
-  * Fix FTBFS by switching from openssl to libssl-dev build-dep. 
+  * Fix FTBFS by switching from openssl to libssl-dev build-dep.
 Thanks to Laurent Bigonville  (Closes: #477022)
   * Packaging new upstream version.
-  * 
 
  -- Patrick Winnertz   Tue, 13 May 2008 10:54:16 +0200
 
@@ -450,7 +457,7 @@ italc (1:1.0.7-2) unstable; urgency=low
 
 italc (1:1.0.7-1) unstable; urgency=low
 
-  * New upstrem release. 
+  * New upstrem release.
 
  -- Patrick Winnertz   Mon, 17 Mar 2008 10:13:42 +0100
 
@@ -486,7 +493,7 @@ italc (1:1.0.2-2) unstable; urgency=low
 italc (1:1.0.2-1) experimental; urgency=low
 
   * Packaging new upstream release
-  * FTBFS Bug on kfreeBSD send to upstream and this is fixed in 
+  * FTBFS Bug on kfreeBSD send to upstream and this is fixed in
 this version now. (Closes: #414096)
 
  -- Patrick Winnertz   Tue, 10 Apr 2007 
15:29:41 +0200
@@ -508,10 +515,10 @@ italc (1.0.0.0~rc2-1) experimental; urgency=low
   * Packaging new upstream release
   * Adopting this package from Steffen Joeris with his acceptance
   * Increasing the debhelper level to 5
-  * Adding the build-depends: 
- - libqt4-dev 
+  * Adding the build-depends:
+ - libqt4-dev
  - zlib1g-dev
- - libjpeg62-dev 
+ - libjpeg62-dev
  - openssl
   * italc-master now has a dependency against italc-client, since
 the client server (ica ) also have to run on the master.

Processed: Bug#881090 marked as pending

[Debian Bug Tracking System]

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

> tag 881090 pending
Bug #881090 [src:italc] italc FTBFS: Qt5LinguistTools*.cmake moved to 
qttools5-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: mariadb-10.1: Missing mariadb-test package prevents testing migration

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:apr-util src:asterisk src:dovecot src:exim4 src:gammu src:gdal 
> src:gnunet src:gnustep-sqlclient src:grass src:jabberd2 src:kamailio src:kdb 
> src:kopanocore src:mailutils src:mysql-connector-c++ src:pike7.8 src:pmacct 
> src:poco src:qtbase-opensource-src src:slurm-llnl src:sope src:vtk6 src:zabbix
Bug #882681 [src:mariadb-10.1] mariadb-10.1: Missing mariadb-test package 
prevents testing migration
Added indication that 882681 affects src:apr-util, src:asterisk, src:dovecot, 
src:exim4, src:gammu, src:gdal, src:gnunet, src:gnustep-sqlclient, src:grass, 
src:jabberd2, src:kamailio, src:kdb, src:kopanocore, src:mailutils, 
src:mysql-connector-c++, src:pike7.8, src:pmacct, src:poco, 
src:qtbase-opensource-src, src:slurm-llnl, src:sope, src:vtk6, and src:zabbix

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

Bug#882681: mariadb-10.1: Missing mariadb-test package prevents testing migration

[Bas Couwenberg]

Source: mariadb-10.1
Version: 1:10.1.29-6
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:apr-util src:asterisk src:dovecot src:exim4 src:gammu 
src:gdal src:gnunet src:gnustep-sqlclient src:grass src:jabberd2 src:kamailio 
src:kdb src:kopanocore src:mailutils src:mysql-connector-c++ src:pike7.8 
src:pmacct src:poco src:qtbase-opensource-src src:slurm-llnl src:sope src:vtk6 
src:zabbix

Dear Maintainer,

The mariadb-10.1 packages no longer build the mariadb-test &
mariadb-test-data packages, but the version in testing still does.
This prevents britney from migrating the package to testing [0]:

 trying: mariadb-10.1
 skipped: mariadb-10.1 (1827, 1009, 24)
 got: 71+0: a-10:i-32:a-3:a-3:a-3:m-3:m-7:m-3:p-3:s-4
 * mips64el: mariadb-test

Because mariadb-10.2 is not going to migrate to testing any time soon,
the -test* packages need to be built by the mariadb-10.1 package again
now that its version uses an epoch.

[0] https://release.debian.org/britney/update_output.txt

Kind Regards,

Bas

Bug#882680: networking-ovn FTBFS: test failures

[Adrian Bunk]

Source: networking-ovn
Version: 1.0.0-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes networking-ovn FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/networking-ovn-1.0.0'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
ostestr
/usr/lib/python2.7/dist-packages/os_testr/ostestr.py:120: UserWarning: No 
.stestr.conf file found in the CWD. Please create one to to replace the 
.testr.conf. You can find a script to do this in the stestr git repository.
  warnings.warn(msg)

=
Failures during discovery
=
--- import errors ---
Failed to import test module: networking_ovn.tests.unit.common.test_acl
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovn/tests/unit/common/test_acl.py", line 20, in 
from networking_ovn.common import acl as ovn_acl
  File "networking_ovn/common/acl.py", line 21, in 
from networking_ovn.common import config
  File "networking_ovn/common/config.py", line 65, in 
default=portbindings.VIF_TYPE_OVS,
AttributeError: 'module' object has no attribute 'VIF_TYPE_OVS'

Failed to import test module: networking_ovn.tests.unit.l3.test_l3_ovn
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovn/tests/unit/l3/test_l3_ovn.py", line 25, in 
from networking_ovn.ovsdb import impl_idl_ovn
  File "networking_ovn/ovsdb/impl_idl_ovn.py", line 24, in 
from networking_ovn.common import config as cfg
  File "networking_ovn/common/config.py", line 65, in 
default=portbindings.VIF_TYPE_OVS,
AttributeError: 'module' object has no attribute 'VIF_TYPE_OVS'

Failed to import test module: networking_ovn.tests.unit.l3.test_l3_ovn_scheduler
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovn/tests/unit/l3/test_l3_ovn_scheduler.py", line 21, in 

from networking_ovn.common import constants as ovn_const
  File "networking_ovn/common/constants.py", line 24, in 
OVN_PORT_BINDING_PROFILE = portbindings.PROFILE
AttributeError: 'module' object has no attribute 'PROFILE'

Failed to import test module: networking_ovn.tests.unit.ml2.test_mech_driver
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovn/tests/unit/ml2/test_mech_driver.py", line 34, in 
from networking_ovn.common import acl as ovn_acl
  File "networking_ovn/common/acl.py", line 21, in 
from networking_ovn.common import config
  File "networking_ovn/common/config.py", line 65, in 
default=portbindings.VIF_TYPE_OVS,
AttributeError: 'module' object has no attribute 'VIF_TYPE_OVS'

Failed to import test module: networking_ovn.tests.unit.ml2.test_qos_driver
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovn/tests/unit/ml2/test_qos_driver.py", line 20, in 
from networking_ovn.ml2 import qos_driver
  File "networking_ovn/ml2/qos_driver.py", line 17, in 
from neutron import context as n_context
ImportError: cannot import name context

Failed to import test module: networking_ovn.tests.unit.ml2.test_trunk_driver
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovn/tests/unit/ml2/test_trunk_driver.py", line 

Processed: your mail

[Debian Bug Tracking System]

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

> tags 866727 pending
Bug #866727 [oneliner-el] oneliner-el: makes emacs explode on upgrades
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#880848: marked as done (python3-rtmidi still depends on librtmidi3 after binnmu.)

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 15:11:26 +
with message-id 
and subject line Bug#880848: fixed in python-rtmidi 1.1.0-2
has caused the Debian Bug report #880848,
regarding python3-rtmidi still depends on librtmidi3 after binnmu.
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.)


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

package: python3-rtmidi
serverity: serious

After being binnmu'd for the rtmidi transition python3-rtmidi still depends on 
the old librtmidi3. I guess the dependency is hardcoded rather than 
auto-generated and hence need manual attention.
--- End Message ---
--- Begin Message ---
Source: python-rtmidi
Source-Version: 1.1.0-2

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated python-rtmidi 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: Sat, 25 Nov 2017 08:24:34 -0600
Source: python-rtmidi
Binary: python3-rtmidi
Architecture: source amd64
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Description:
 python3-rtmidi - Python wrapper for the RtMidi C++ library written with Cython
Closes: 880848
Changes:
 python-rtmidi (1.1.0-2) unstable; urgency=medium
 .
   * debian/control:
 - Bumps dependency librtmidi3 -> librtmidi4 (Closes: #880848)
 - Bumps debhelper compat from 9 to 10.
   * Bumps Standards-Version to 4.1.1:
 - Changes extra package priority to optional.
Checksums-Sha1:
 5cd4ec9ec0b09e92886998e13f657210306f4583 2095 python-rtmidi_1.1.0-2.dsc
 55032516dd59cd65a8ae833040da7d031d5feec8 2480 
python-rtmidi_1.1.0-2.debian.tar.xz
 25453e81cbd38b0bb5a9deb14c2c8cfcbc552d8a 7897 
python-rtmidi_1.1.0-2_amd64.buildinfo
 2ac713988cd9ac9e82e0283006137953475d5a4f 290560 
python3-rtmidi-dbgsym_1.1.0-2_amd64.deb
 32468ef0a326ce9580e35553638c9e7b21768741 76176 python3-rtmidi_1.1.0-2_amd64.deb
Checksums-Sha256:
 db95f0cf189987764d5493476341f81dcb2b5e87faa236eeb5da8077207b8990 2095 
python-rtmidi_1.1.0-2.dsc
 b766e88774ae60217c69201566248d6fdc81e7a855a69612a113bd06262da555 2480 
python-rtmidi_1.1.0-2.debian.tar.xz
 3bf748d468891b6d59d472fa8c28f39ee413f97c8af8f54d68de0d58cafa42d6 7897 
python-rtmidi_1.1.0-2_amd64.buildinfo
 766f96acf19ad1b63b3af6f52b6d877bafc7662b2a282adc6e8013cbccb8553a 290560 
python3-rtmidi-dbgsym_1.1.0-2_amd64.deb
 c5999cc589d8817921ff0b03f44d370d03fa2a2b020fefd91ac465305875f755 76176 
python3-rtmidi_1.1.0-2_amd64.deb
Files:
 ffda575768b0f9ea3311e0eabb3a12f4 2095 python optional python-rtmidi_1.1.0-2.dsc
 c788125b4f173b3b4575c9d8961db608 2480 python optional 
python-rtmidi_1.1.0-2.debian.tar.xz
 f62e8dd6644bbd8646e7f5833a781b0e 7897 python optional 
python-rtmidi_1.1.0-2_amd64.buildinfo
 d5c91ea895331899fb2f712924278f84 290560 debug optional 
python3-rtmidi-dbgsym_1.1.0-2_amd64.deb
 911c1ac684ed89f76fd45b9d4e1d0d6b 76176 python optional 
python3-rtmidi_1.1.0-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAloZf7QRHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T/uVRAAp9D1ReLCe59AkMhc/38z6MUM15Xlk1CL
BocLZW1S14wKgAyJO6/LpuFN+quAcrby8Eiho3kr4ch3Xlort0GZvO+VlJLJAtpH
rp8/4Aj8e5nlfjxm7r0RKKfxD0qttEObFXBkw3L0MmfTbYqN3aF/wrWaZQiGYVTS
YtfkhbUaef6lDRWbpJlIcuv0kC2i6UJ/lpxFL9r1XYL31hb68WkBE441Ngl03p29
cRZXacP07bTmgabSpINJpHSNu++yYY8rllNXBR9/3oXko06BV9PXUf46kA7yda/r
MK3Yir1EMM9UCJ7GkgFyv7FkPkXxrU/NcoiobvUeOA42666UKRBtsBmoQUOfzPdq
yA/rc7Tr1859HEDxxrvuWmGBODhkcL4m9+Bk80e7FFgL1+qGbSU4951khgNQYVUa
L8ZeICflDsygaovIOYdsTBzWHOda2JqZVLUqvxZrK2GD5plACny1IFpTSGD1bcBM
DaI4S2sE4ZlfBFwizHrnNt/CqRMTlMa4mtG1pUGNOhL6a8MwvV7/S88/75ILLmEp
tMKACl1lTYbawzIysnc7H0ACDE5Q7DciLu1Abp8RcWzpepV0QDh7YeAWAWDeCeJj
CUr0BwjJEkj7NL6cskMiL5IuyIb6Ub+LW87zV6KH8X3thQB+kTwWoWqbmGe31kdi
qasdmED+xCk=
=Uk3+
-END PGP SIGNATURE End Message ---

Bug#859554: RM: pidgin-openfetion -- RoQA; Service provider stopped; RC-buggy; Upstream dead; Orphaned

[Boyuan Yang]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org levin...@gmail.com

Hello all,

I believe it's time to remove package pidgin-openfetion from Debian archive.

Reasons:

* Upstream dead for more than 5 years;
* Popcon declining;
* Package orphaned already;
* RC-buggy (openssl 1.1 migration; see also Bug#859554)
* As a plugin library to provide IM integration into pidgin, its service 
provider, China Mobile, has stopped the old fetion service and heads to a new 
one focusing on enterprise use with different web API. This effectively made 
the library useless.

CC-ing chinese-developers list (original package maintainer on-list) and 
original library author.

Regards,
Boyuan Yang

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

Bug#881097: Removing libnet-ping-external-perl from jessie, stretch and unstable

[tony mancill]

On Sat, Nov 25, 2017 at 08:12:22AM +0100, Salvatore Bonaccorso wrote:
> Hi Tony!
> 
> Thanks for your reply, dropping LTS list since reply is specific for
> oldstable, stable and unstable.
> 
> On Wed, Nov 22, 2017 at 03:32:36PM -0800, tony mancill wrote:
> > On Wed, Nov 22, 2017 at 09:00:59PM +0100, Emilio Pozuelo Monfort wrote:
> > > On 08/11/17 20:19, Ola Lundqvist wrote:
> > > > Hi
> > > > 
> > > > Considering that this package is about to be removed from jessie I
> > > > guess it should be removed from wheezy too. How is that done? Should I
> > > > contact the FTP maintainers about it, or do we simply ignore the
> > > > issue?
> > > 
> > > We don't have point releases, so I'm not sure we can get a package 
> > > removed at
> > > this stage without extra work by the ftp masters. So our options would be:
> > > 
> > > - mark as no-dsa if it's not important enough
> > > - mark as unsupported / end-of-life
> > > - fix it
> > > - get it removed
> > > 
> > > The issue seems only exploitable if it's used by a service that is exposed
> > > remotely or to other issues... and has no rdeps in wheezy. OTOH there is 
> > > at
> > > least one sponsor using that package. So removing it may not be the best 
> > > course
> > > given there is a proposed patch. So I'd go with either no-dsa or fix it,
> > > depending on the assessed importance.
> > 
> > Hi,
> > 
> > My apologies for taking a while to join the thread.  As the most recent
> > uploader of this package, I feel responsible for helping get it into a
> > safe state if we opt to keep it.  However, I am not an active user, so
> > if the package is to remain in Debian, it might be better to transition
> > it to the Debian Perl Team (assuming that is amenable to the team).
> > 
> > I tend to agree with Emilio that removing it might not be the best
> > course of action for our users, particularly given that we have a patch
> > and the popcon [1] is non-zero.  Removing it from the distribution seems
> > like it merely leaves users with a known vulnerability.  Also, the
> > package might be used in derivatives.
> > 
> > I agree with Simon that it's a little odd for the patch to bump the
> > version.  (OTOH, it makes it much easier to differentiate from the
> > vulnerable 0.15.)  Still, I am inclined to take the patch as a patch
> > against upstream 0.15 for the upload to unstable and then backport it
> > for 0.13 for stable and oldstable.  Or perhaps Alexandr Ciornii (on the
> > cc) would be willing to release 0.16 including the patch.
> > 
> > Thoughts?
> 
> The package is basically "unmaintained" (upstream)[*] and for almost
> 10 years did not address
> https://rt.cpan.org/Public/Bug/Display.html?id=33230 (maybe you can
> argue, as well a fault for various "downstreams" to not notice and
> bring that earlier up, defintively. I wonder why only now it got
> attention on oss-security, for which I then requested a CVE)
> 
> IMHO the best course of action is still to have it removed, in all
> suites. For unstable, so that it's not included in buster. And for
> oldstable and stable (as scheduled for the upcoming point releases)
> via the point release announcements. The announcement will contain a
> section which packages are removed from Debian, and for which reason,
> so still users of Net::Ping::External are informed.
> 
> I agree as well that if one starts to argue that way that there are
> old packages which do not see updates from upstream, then a whole more
> should be removed from Debian ;-). My point was not this though, I'm
> concernend that there was a bug with security implications for almost
> 10 years reported in public bugtracker, without even a reply to it to
> acknowledge the problem.

Hi Salvatore,

Understood.  I can appreciate all of the considerations that the
Security Team has to take into account regarding the distribution life
cycle.

I realize it won't be part of the announcement nor is it officially part
of Debian, but in case it helps any users of Net::Ping::External who
come across this bug report, I did prepare an updated package for 0.15
that includes the patch for CVE-2008-7319.  

That packaging can be found here [1].

Cheers,
tony

[1] 
https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-ping-external-perl.git


signature.asc
Description: PGP signature

Bug#882671: exim4: handles BDAT data incorrectly and leads to crash

[Salvatore Bonaccorso]

Source: exim4
Version: 4.89-1
Severity: grave
Tags: security upstream
Forwarded: https://bugs.exim.org/show_bug.cgi?id=2201

Hi

Filling as well the second issue in the Debian BTS to have a Debian
BTS reference, related to
https://lists.exim.org/lurker/message/20171125.034842.d1d75cac.en.html
and #882648.

Upstream report: https://bugs.exim.org/show_bug.cgi?id=2201

Regards,
Salvatore

Bug#882173: marked as done (audacity: FTBFS on !x86 and baseline violation on i386)

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 13:33:52 +
with message-id 
and subject line Bug#882173: fixed in audacity 2.2.0-2
has caused the Debian Bug report #882173,
regarding audacity: FTBFS on !x86 and baseline violation on i386
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.)


-- 
882173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: audacity
Version: 2.2.0-1
Severity: serious

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

...
checking whether C++ compiler accepts -msse... no
configure: error: Need a version of gcc with -msse
configure: error: ./configure failed for lib-src/sbsms


In addition to causing a FTBFS on !x86,
using -msee is also a baseline violation on i386.
--- End Message ---
--- Begin Message ---
Source: audacity
Source-Version: 2.2.0-2

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated audacity 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: Fri, 24 Nov 2017 18:23:25 +0100
Source: audacity
Binary: audacity audacity-data
Architecture: source
Version: 2.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 audacity   - fast, cross-platform audio editor
 audacity-data - fast, cross-platform audio editor (data)
Closes: 882173
Changes:
 audacity (2.2.0-2) unstable; urgency=medium
 .
   * Fix FTBFS on non-x86 archs. (Closes: #882173)
 Thanks to James Cowgill 
Checksums-Sha1:
 947b43c930ef649a1ca594f1c0f10c02ed7a0314 2676 audacity_2.2.0-2.dsc
 5f4ece66d8f168d216abe8f85950a7c2d8c79d2f 39328 audacity_2.2.0-2.debian.tar.xz
 b35874e0ff28d7455840cdb396f4c3780377ea74 15656 audacity_2.2.0-2_amd64.buildinfo
Checksums-Sha256:
 a3cb68d6c9d8cfe50b80d33fdd8487106cfbc305e1415435121dd9a423d4797e 2676 
audacity_2.2.0-2.dsc
 dd47ec0147a5a25e7efe70b022ce98b214e62d3547daa81c8b5579d44147ba0a 39328 
audacity_2.2.0-2.debian.tar.xz
 ca7aa7badc65444a67ab750f653a1655ed100d67daf60b56beec67cc858ca15e 15656 
audacity_2.2.0-2_amd64.buildinfo
Files:
 34bbc4d0faf67f44bd06db50005dc5f2 2676 sound optional audacity_2.2.0-2.dsc
 abc1994cad1276e3aa2abc51cc9bbd3f 39328 sound optional 
audacity_2.2.0-2.debian.tar.xz
 6b78836bd4bdbaeda6b070da2dc830b8 15656 sound optional 
audacity_2.2.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESlQ1E9LfY1GoF46jWwGUVeK4T6UFAloZbR4VHG1pcmEubWlr
ZXNAc2V6bmFtLmN6AAoJEFsBlFXiuE+lX0EP/2/n126R9TS0lKkxFiK2WI8fTGJ0
KaLwIouhCDtkSAsujvOtVDBVDPyxTdfwuGbHKGP7fs3csQAW9yn5ZbIRESdEGLib
+F/htRase9nelif55Pnn7cnsS+a3Tkx5gATIc0PxmIqhjs6gwupYrq/3CHHtPjHH
2BmfIwE7tqIgeOJEaDmQYNyYZWlrVWA1c1n/Rg6Yv88RVZYIsPLqRArFq+UBDkGQ
3k5hfowerrqqSxoz1VGRn5kqgy7bEp4Xq0UumhMtChj8hTV5ZQj+aMMbDVvTmgJ5
GRkJsogMNBRj6kS97t1AFf17g2XJ0dTh5pPQNe1WMHW+lvH8JkZUQ9ZGCHrL09mP
6+popMSRRVTgjtL0eEAB2pH7qMuWrKJ0c88ok9jG/vDwEkCu15DLIOtlnxXtWTVE
YOTqdqK0wz/WEWWelBr9waD4lJEQT9QP4CtpmtTJ6wm9UU9R2W5o7uNa1LIlOODR
uoLqUPTHvkY5LxCRTpbw3aamP7XsUKi8V1Cp38nH+4z06rzLEM3R5+1a8BJgmJLU
GA10HLY7aMB0Rsh/GS+Ozrl+QFquHk8s08Z9Zsd73IvDJsZyaAabKpWspeR2JOSd
F6QUPIz98zvyoOjHEYCsPoZXF1NiDUaQTzmKwxZ5N49vck45nk1psNj2Hb2Hc7mh
Trodq/B2Il81F8TX
=38vH
-END PGP SIGNATURE End Message ---

Bug#879071: 0ad FTBFS with on armhf with gcc 7: error: call of overloaded 'abs(unsigned int)' is ambiguous

[Ludovic Rousseau]

2017-11-21 1:25 GMT+01:00 peter green :

> On 19/11/17 14:38, Ludovic Rousseau wrote:
>
> Peter,
>
> Please go with the NMU.
>
> Done, final debdiff attatched.
>

Thanks.
I pushed your changes in https://anonscm.debian.org/
viewvc/pkg-games/packages/trunk/0ad/debian/


> You may also want to fix the arm64 build failure at the same time.
> See https://buildd.debian.org/status/fetch.php?pkg=0ad=arm6
> 4=0.0.22-1=1508351579=0
>
> That looks like it is failing in buliding an embedded copy of mozjs.
>
> Is there some reason 0ad has to use an embedded copy of mozjs rather than
> one of the versions packaged in Debian.
>

No idea.
0ad has its own list of patches above mozjs 38.2.1. See
http://sources.debian.net/src/0ad/0.0.21-2/libraries/source/spidermonkey/

I have no idea if the official mozjs packaged in Debian can be used
instead. That is something that could be experimented.
I just maintain the 0ad package since 2 months.

Bye,

-- 
 Dr. Ludovic Rousseau

Bug#882328: [Pkg-gauche-devel] Bug#882328: gauche-c-wrapper FTBFS with glibc 2.25

[Jens Thiele]

Adrian Bunk  writes:

> Testing c-wrapper ...
> :444:13: error: invalid "#pragma GCC warning" directive

[...]

> ././ffitest.h:828: GCC exitted abnormally (at token: *eoi*)
> ././ffitest.h:828: #f
> ././ffitest.h:828: process 44299 exitted abnormally with exit code 256 (at 
> token: *eoi*)
> *** ERROR: process 44299 exitted abnormally with exit code 256
> While loading "./cwrappertest.scm" at line 13
> Stack Trace:
> ___
>   0  (with-error-handler (lambda (e) (let ((e e)) (%guard-rec e e  ...
> expanded from (guard (e (( e) (let ((errmsg 
> (make-error
> at "../lib/c-wrapper/c-parser.scm":1104
>   1  (parse-macro include-dirs headers options)
> at "../lib/c-wrapper/c-parser.scm":1159
>   2  (trunk)
> at "../lib/c-wrapper/c-parser.scm":67
>   3  (c-parse (if (list? include-dirs) include-dirs (list include- ...
> at "../lib/c-wrapper.scm":105
> Makefile:69: recipe for target 'check-c' failed
> make[2]: *** [check-c] Error 70

gauche-c-wrapper fails to handle the "__glibc_macro_warning" macro
included by stdio.h -> libio.h -> cdefs.h

/* __glibc_macro_warning (MESSAGE) issues warning MESSAGE.  This is
   intended for use in preprocessor macros.

   Note: MESSAGE must be a _single_ string; concatenation of string
   literals is not supported.  */
#if __GNUC_PREREQ (4,8) || __glibc_clang_prereq (3,5)
# define __glibc_macro_warning1(message) _Pragma (#message)
# define __glibc_macro_warning(message) \
  __glibc_macro_warning1 (GCC warning message)
#else
# define __glibc_macro_warning(msg)
#endif

an ugly workaround would be to skip that macro by name with something
like:

diff -Nur gauche-c-wrapper-0.6.1.orig/lib/c-wrapper/c-parser.scm 
gauche-c-wrapper-0.6.1/lib/c-wrapper/c-parser.scm
--- gauche-c-wrapper-0.6.1.orig/lib/c-wrapper/c-parser.scm  2009-08-08 
16:44:52.0 +0200
+++ gauche-c-wrapper-0.6.1/lib/c-wrapper/c-parser.scm   2017-11-24 
21:57:47.071382470 +0100
@@ -1115,7 +1115,10 @@
 (raise e
  (call-with-gcc-io include-dirs headers options
(lambda (in out)
- (let ((macro-list (queue->list (macro-queue
+ (let ((macro-list (filter (lambda(x)
+(not (string=? (car x)
+   
"__glibc_macro_warning(message)")))
+  (queue->list 
(macro-queue)
(for-each (lambda (macro-def)
(display (car macro-def) out)
(newline out))

Bug#882075: marked as done (ffmpeg: sometimes FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 13:04:33 +
with message-id 
and subject line Bug#882075: fixed in ffmpeg 7:3.4-4
has caused the Debian Bug report #882075,
regarding ffmpeg: sometimes FTBFS on i386
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.)


-- 
882075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ffmpeg
Version: 7:3.4-1
Severity: serious
Tags: sid buster

And just after I upload 3.4-3...

ffmpeg 3.4 sometimes FTBFS on i386, possibly due to some hardware
specific thing. It has worked on the buildds so far, but sometimes fails
on the ubuntu builders and in reproducible builds with checkasm errors
(although often rebuilding helps):

> Test checkasm-float_dsp failed. Look at 
> tests/data/fate/checkasm-float_dsp.err for details.
> checkasm: using random seed 2642491962
> SSE:
>  - float_dsp.vector_fmul [OK]
>  - float_dsp.vector_fmac [OK]
>  - float_dsp.butterflies_float   [OK]
>  - float_dsp.scalarproduct_float [OK]
> 93: -53.395181798898 - -53.395181798898 = -7.1054273576e-15
> SSE2:
>vector_dmul_scalar_sse2 (float_dsp.c:171)
>  - float_dsp.vector_dmul [FAILED]
>  - float_dsp.vector_dmac [OK]
> AVX:
>  - float_dsp.vector_fmul [OK]
>  - float_dsp.vector_fmac [OK]
>  - float_dsp.vector_dmul [OK]
>  - float_dsp.vector_dmac [OK]
> FMA3:
>  - float_dsp.vector_fmul [OK]
>  - float_dsp.vector_fmac [OK]
>  - float_dsp.vector_dmac [OK]
> AVX2:
>  - float_dsp.vector_fmul [OK]
> checkasm: 1 of 20 tests have failed
> /build/1st/ffmpeg-3.4/tests/Makefile:225: recipe for target 
> 'fate-checkasm-float_dsp' failed

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ffmpeg
Source-Version: 7:3.4-4

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated ffmpeg 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: Sat, 25 Nov 2017 10:49:41 +
Source: ffmpeg
Binary: ffmpeg ffmpeg-doc libavcodec57 libavcodec-extra57 libavcodec-extra 
libavcodec-dev libavdevice57 libavdevice-dev libavfilter6 libavfilter-extra6 
libavfilter-extra libavfilter-dev libavformat57 libavformat-dev libavresample3 
libavresample-dev libavutil55 libavutil-dev libpostproc54 libpostproc-dev 
libswresample2 libswresample-dev libswscale4 libswscale-dev libav-tools
Architecture: source
Version: 7:3.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: James Cowgill 
Description:
 ffmpeg - Tools for transcoding, streaming and playing of multimedia files
 ffmpeg-doc - Documentation of the FFmpeg multimedia framework
 libav-tools - Compatibility links for libav-tools (transitional package)
 libavcodec-dev - FFmpeg library with de/encoders for audio/video codecs - 
developm
 libavcodec-extra - FFmpeg library with extra codecs (metapackage)
 libavcodec-extra57 - FFmpeg library with additional de/encoders for 
audio/video codecs
 libavcodec57 - FFmpeg library with de/encoders for audio/video codecs - runtime
 libavdevice-dev - FFmpeg library for handling input and output devices - 
developmen
 libavdevice57 - FFmpeg library for handling input and output devices - runtime 
fi
 libavfilter-dev - FFmpeg library containing media filters - development files
 libavfilter-extra - FFmpeg library with extra filters (metapackage)
 libavfilter-extra6 - FFmpeg library with extra media filters - runtime files
 libavfilter6 - FFmpeg library containing media filters - runtime files
 libavformat-dev - FFmpeg library with (de)muxers for multimedia containers - 
develo
 libavformat57 - FFmpeg library with (de)muxers for multimedia containers - 
runtim
 libavresample-dev - FFmpeg compatibility library for 

Bug#882598: marked as done (libavutil55: ABI broken by "add vector_dmac_scalar()")

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 13:04:33 +
with message-id 
and subject line Bug#882598: fixed in ffmpeg 7:3.4-4
has caused the Debian Bug report #882598,
regarding libavutil55: ABI broken by "add vector_dmac_scalar()"
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.)


-- 
882598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libavutil55
Version: 7:3.4-3
Severity: normal

Dear Maintainer,

After upgrade to sid ffmpeg tools start to segfault like this:
[370710.121304] read_thread[9924]: segfault at 7feff8051ce0 ip 7fef350b7943 
sp 7fef07386ea8 error 4 in libavutil.so.55.78.100[7fef35069000+67000]

After downgrading libavutil55 to 7:3.3.4-2+b3 ffmpeg tools starts working
again.

Regards,


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'unstable'), (500, 'testing'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libavutil55 depends on:
ii  libc62.24-11+deb9u1
ii  libdrm2  2.4.74-1
ii  libva-drm2   2.0.0-2
ii  libva-x11-2  2.0.0-2
ii  libva2   2.0.0-2
ii  libvdpau11.1.1-6
ii  libx11-6 2:1.6.4-3

libavutil55 recommends no packages.

libavutil55 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ffmpeg
Source-Version: 7:3.4-4

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated ffmpeg 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: Sat, 25 Nov 2017 10:49:41 +
Source: ffmpeg
Binary: ffmpeg ffmpeg-doc libavcodec57 libavcodec-extra57 libavcodec-extra 
libavcodec-dev libavdevice57 libavdevice-dev libavfilter6 libavfilter-extra6 
libavfilter-extra libavfilter-dev libavformat57 libavformat-dev libavresample3 
libavresample-dev libavutil55 libavutil-dev libpostproc54 libpostproc-dev 
libswresample2 libswresample-dev libswscale4 libswscale-dev libav-tools
Architecture: source
Version: 7:3.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: James Cowgill 
Description:
 ffmpeg - Tools for transcoding, streaming and playing of multimedia files
 ffmpeg-doc - Documentation of the FFmpeg multimedia framework
 libav-tools - Compatibility links for libav-tools (transitional package)
 libavcodec-dev - FFmpeg library with de/encoders for audio/video codecs - 
developm
 libavcodec-extra - FFmpeg library with extra codecs (metapackage)
 libavcodec-extra57 - FFmpeg library with additional de/encoders for 
audio/video codecs
 libavcodec57 - FFmpeg library with de/encoders for audio/video codecs - runtime
 libavdevice-dev - FFmpeg library for handling input and output devices - 
developmen
 libavdevice57 - FFmpeg library for handling input and output devices - runtime 
fi
 libavfilter-dev - FFmpeg library containing media filters - development files
 libavfilter-extra - FFmpeg library with extra filters (metapackage)
 libavfilter-extra6 - FFmpeg library with extra media filters - runtime files
 libavfilter6 - FFmpeg library containing media filters - runtime files
 libavformat-dev - FFmpeg library with (de)muxers for multimedia containers - 
develo
 libavformat57 - FFmpeg library with (de)muxers for multimedia containers - 
runtim
 libavresample-dev - FFmpeg compatibility library for resampling - development 
files
 libavresample3 - FFmpeg compatibility library for resampling - runtime files
 libavutil-dev - FFmpeg library with functions for simplifying programming - 
devel
 libavutil55 - 

Processed: tagging 845959, severity of 845959 is serious

[Debian Bug Tracking System]

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

> tags 845959 + sid buster
Bug #845959 [src:sugar-toolkit] sugar-toolkit: depends on python-gnome2 which 
deprecated
Added tag(s) sid and buster.
> severity 845959 serious
Bug #845959 [src:sugar-toolkit] sugar-toolkit: depends on python-gnome2 which 
deprecated
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 845954, severity of 845954 is serious

[Debian Bug Tracking System]

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

> tags 845954 + sid buster
Bug #845954 [src:pyrenamer] pyrenamer: depends on python-gnome2 which deprecated
Added tag(s) sid and buster.
> severity 845954 serious
Bug #845954 [src:pyrenamer] pyrenamer: depends on python-gnome2 which deprecated
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 790572

[Debian Bug Tracking System]

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

> tags 790572 - stretch
Bug #790572 [src:flowblade] flowblade: depends on python-gnome2 which is 
deprecated
Removed tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: tagging 845950, severity of 845950 is serious

[Debian Bug Tracking System]

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

> tags 845950 + sid buster
Bug #845950 [src:glipper] glipper: depends on python-gnome2 which deprecated
Added tag(s) buster and sid.
> severity 845950 serious
Bug #845950 [src:glipper] glipper: depends on python-gnome2 which deprecated
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 845960, severity of 845960 is serious

[Debian Bug Tracking System]

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

> tags 845960 + sid buster
Bug #845960 [src:x-tile] x-tile: depends on python-gnome2 which deprecated
Added tag(s) buster and sid.
> severity 845960 serious
Bug #845960 [src:x-tile] x-tile: depends on python-gnome2 which deprecated
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 790591

[Debian Bug Tracking System]

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

> tags 790591 - stretch
Bug #790591 [src:gnome-python-desktop] gnome-python-desktop: depends on 
python-gnome2 which is deprecated
Removed tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: severity of 790572 is serious

[Debian Bug Tracking System]

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

> severity 790572 serious
Bug #790572 [src:flowblade] flowblade: depends on python-gnome2 which is 
deprecated
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 845949, severity of 845949 is serious

[Debian Bug Tracking System]

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

> tags 845949 + sid buster
Bug #845949 [src:guake] guake: depends on python-gnome2 which deprecated
Added tag(s) buster and sid.
> severity 845949 serious
Bug #845949 [src:guake] guake: depends on python-gnome2 which deprecated
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 790591 is serious

[Debian Bug Tracking System]

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

> severity 790591 serious
Bug #790591 [src:gnome-python-desktop] gnome-python-desktop: depends on 
python-gnome2 which is deprecated
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Bug#882598 marked as pending

[Debian Bug Tracking System]

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

> tag 882598 pending
Bug #882598 [libavutil55] libavutil55: ABI broken by "add vector_dmac_scalar()"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882598: marked as pending

[James Cowgill]

tag 882598 pending
thanks

Hello,

Bug #882598 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://anonscm.debian.org/git/pkg-multimedia/ffmpeg.git/commit/?id=5735897

---
commit 5735897fb2bfc92b51aacd3c1c132cb853cdc69d
Author: James Cowgill 
Date:   Sat Nov 25 10:56:30 2017 +

Upload to unstable

diff --git a/debian/changelog b/debian/changelog
index a58e8f9..a77d780 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,12 @@
-ffmpeg (7:3.4-4) UNRELEASED; urgency=medium
+ffmpeg (7:3.4-4) unstable; urgency=medium
 
-  *
+  * debian/control:
+- Require 3.4 avcodec/avfilter when 3.4 avutil is in use. (Closes: #882598)
+  * debian/patches:
+- Add patch to fix random FTBFS on i386 caused by float precision issues.
+  (Closes: #882075)
 
- -- James Cowgill   Sat, 18 Nov 2017 19:32:58 +
+ -- James Cowgill   Sat, 25 Nov 2017 10:49:41 +
 
 ffmpeg (7:3.4-3) unstable; urgency=medium
 

Bug#882075: marked as pending

[James Cowgill]

tag 882075 pending
thanks

Hello,

Bug #882075 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://anonscm.debian.org/git/pkg-multimedia/ffmpeg.git/commit/?id=5735897

---
commit 5735897fb2bfc92b51aacd3c1c132cb853cdc69d
Author: James Cowgill 
Date:   Sat Nov 25 10:56:30 2017 +

Upload to unstable

diff --git a/debian/changelog b/debian/changelog
index a58e8f9..a77d780 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,12 @@
-ffmpeg (7:3.4-4) UNRELEASED; urgency=medium
+ffmpeg (7:3.4-4) unstable; urgency=medium
 
-  *
+  * debian/control:
+- Require 3.4 avcodec/avfilter when 3.4 avutil is in use. (Closes: #882598)
+  * debian/patches:
+- Add patch to fix random FTBFS on i386 caused by float precision issues.
+  (Closes: #882075)
 
- -- James Cowgill   Sat, 18 Nov 2017 19:32:58 +
+ -- James Cowgill   Sat, 25 Nov 2017 10:49:41 +
 
 ffmpeg (7:3.4-3) unstable; urgency=medium
 

Processed: Bug#882075 marked as pending

[Debian Bug Tracking System]

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

> tag 882075 pending
Bug #882075 [src:ffmpeg] ffmpeg: sometimes FTBFS on i386
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#882663: serverity important because qtwebkit is still in testing

[Sebastiaan Couwenberg]

Control: severity -1 important

The serious severity is not appropriate as long as qtwebkit is still in
testing and no definitive removal date is known.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: serverity important because qtwebkit is still in testing

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #882663 [src:qgis] [qgis] Qt4's WebKit removal
Severity set to 'important' from 'serious'

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

Bug#882591: marked as done (gazebo FTBFS: /usr/include/boost/predef/language/stdc.h:52: Parse error at "defined")

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 11:53:56 +
with message-id 
and subject line Bug#882591: fixed in gazebo 7.8.1+dfsg-3
has caused the Debian Bug report #882591,
regarding gazebo FTBFS: /usr/include/boost/predef/language/stdc.h:52: Parse 
error at "defined"
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.)


-- 
882591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gazebo
Version: 7.8.1+dfsg-2
Severity: serious

Some recent change in unstable makes gazebo FTBFS:

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

...
/usr/include/boost/predef/language/stdc.h:52: Parse error at "defined"
gazebo/gui/CMakeFiles/gazebo_gui.dir/build.make:75: recipe for target 
'gazebo/gui/moc_ApplyWrenchDialog.cxx' failed
make[3]: *** [gazebo/gui/moc_ApplyWrenchDialog.cxx] Error 1
--- End Message ---
--- Begin Message ---
Source: gazebo
Source-Version: 7.8.1+dfsg-3

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated gazebo 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: Sat, 25 Nov 2017 12:35:51 +0100
Source: gazebo
Binary: gazebo7-common gazebo7 libgazebo7 libgazebo7-dev gazebo7-plugin-base 
gazebo7-doc
Architecture: source
Version: 7.8.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 gazebo7- Open Source Robotics Simulator - Binaries
 gazebo7-common - Open Source Robotics Simulator - Shared files
 gazebo7-doc - Open Source Robotics Simulator - Documentation
 gazebo7-plugin-base - Open Source Robotics Simulator - base plug-ins
 libgazebo7 - Open Source Robotics Simulator - shared library
 libgazebo7-dev - Open Source Robotics Simulator - Development Files
Closes: 882591
Changes:
 gazebo (7.8.1+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Move dependency according to links file.
   * Add patch for Q_MOC_RUN (Closes: #882591)
Checksums-Sha1:
 a6c43026be868adb5c61ccf7d54d3a8a2b8a8aec 3099 gazebo_7.8.1+dfsg-3.dsc
 782830b977aa10f8697f653a5285e211392a933b 20284 
gazebo_7.8.1+dfsg-3.debian.tar.xz
 2a2e9a7ef06fca8fc08deed9ac194ed89acca9b4 25210 
gazebo_7.8.1+dfsg-3_source.buildinfo
Checksums-Sha256:
 c67520c6c0987f48f92745a9b39c5918e37f8b3692c1bc8f39c921fb16240058 3099 
gazebo_7.8.1+dfsg-3.dsc
 5e1c4f0089f061651fce61c801fef8b5f8b4a1e4721c1b57b5df734780868899 20284 
gazebo_7.8.1+dfsg-3.debian.tar.xz
 acecc5f029de3610de2c05d22eeadc3d9e0e8141c72201ed96db39cb18cc526c 25210 
gazebo_7.8.1+dfsg-3_source.buildinfo
Files:
 165d91f6ebda03c8f1650ede32bc0e8a 3099 science optional gazebo_7.8.1+dfsg-3.dsc
 feed0d0e364bd821422d7e7eb88e021d 20284 science optional 
gazebo_7.8.1+dfsg-3.debian.tar.xz
 8fdfa83a3d9ab809fd052e329abaffd7 25210 science optional 
gazebo_7.8.1+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAloZVxEUHGpzcHJpY2tl
QGRlYmlhbi5vcmcACgkQW//cwljmlDMX5g//ddgEzAApx1zUzxgUN85KNSbUNcJa
a9+zJQRVwgCv48nA42AuZnnzM20EdnbNTYYDW6+sjwST+PWjY8tbvHiBgduUpJ6o
YP9kfLnfj1LwWFAdfvI+SqtYa1qD3eHFHhgbLfzP/g23hxldpJ3e0DCfKdwuGzoR
ia5AKJfJbpnhWKX+VysKpAHv8Sz3HySy9KDVwyXqqnHo6VTiJo5SztHx7btlxWgl
BFrFjN+vTeMeQkqnes+f2nqJMeFqcC9FyJFCyTvSeptWaEz8vjFxN5maCtBViUmE
PJXyH/KfjnFxXKyVNjU+L53a5r5QTOLkyg7fHSzZlvD8RyNy2jwo0Xk1Dx9vsYRA
1eGkw5rMhvFY2g4XjWmGhhLi0O0QeO/sc0Mcm2r/7GmzspgNydHkKjSY56DOMSHZ
4Unu0m967ClEbrjzXqNWmd5rrMk2i5j/IgJqU4cudyxMG/a20wvUZF+fs2iv6zOM
k58DfO/DNUxmbSIP2PgTcQbhF0lP9YA4S6LWS7zU9FMRypsRw67FvTzH4oo7+kSt
3dllL+cwtzThE8fvou0GrcX0txI7b234liDUqS1ApqOYbuwTuFaGb69tvf/nEoo3
MVUFvymSZ+tzev+Zl3YjhBjMOA8yJbDb+4ZYI1+oKdfe6wjD75V1NXH4dxBxdOr0
szNqSrGTq+MbJUs=
=hUYA
-END PGP SIGNATURE End Message ---

Processed: Add the found version

[Debian Bug Tracking System]

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

> found 882663 2.14.7+dfsg-1~exp1
Bug #882663 {Done: Sebastiaan Couwenberg } [src:qgis] 
[qgis] Qt4's WebKit removal
Marked as found in versions qgis/2.14.7+dfsg-1~exp1 and reopened.
> thanks
Stopping processing here.

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

Processed: Re: goocanvas is deprecated & replaced by goocanvas-2.0

[Debian Bug Tracking System]

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

> severity 858636 serious
Bug #858636 [src:goocanvas] goocanvas is deprecated & replaced by goocanvas-2.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#882055: Gedit breaks when writing to a file

[Michael Biebl]

Control: severity -1 normal
Control: retitle -1 gedit aborts when writing to a file with setuid bit

Am 25.11.2017 um 12:17 schrieb Narcis Garcia:
> Sorry, I forgot to test with and without setuid bit:
> 
> $ id -un
> userA
> $ echo "Content text" > file.txt
> $ sudo chown userB file.txt
> $ sudo chmod u+s,g+rw file.txt
> 
> $ nano file.txt
> # Modyfy and save: Fine.
> 
> $ gedit file.txt
> # Modify and save:
> GLib-GIO:ERROR:/build/glib2.0-B1uXKV/glib2.0-2.50.3/./gio/glocalfilemonitor.c:433:g_file_monitor_source_handle_event:
> code should not be reached

Given the special circumstances which are needed to trigger this issue,
I'm downgrading the severity.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#882055: Gedit breaks when writing to a file

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #882055 [gedit] Gedit breaks when writing to a file
Severity set to 'normal' from 'grave'
> retitle -1 gedit aborts when writing to a file with setuid bit
Bug #882055 [gedit] Gedit breaks when writing to a file
Changed Bug title to 'gedit aborts when writing to a file with setuid bit' from 
'Gedit breaks when writing to a file'.

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

Bug#882055: Gedit breaks when writing to a file

[Narcis Garcia]

Sorry, I forgot to test with and without setuid bit:

$ id -un
userA
$ echo "Content text" > file.txt
$ sudo chown userB file.txt
$ sudo chmod u+s,g+rw file.txt

$ nano file.txt
# Modyfy and save: Fine.

$ gedit file.txt
# Modify and save:
GLib-GIO:ERROR:/build/glib2.0-B1uXKV/glib2.0-2.50.3/./gio/glocalfilemonitor.c:433:g_file_monitor_source_handle_event:
code should not be reached

Bug#784514: Cloning

[Lisandro Damián Nicanor Pérez Meyer]

clone 784514 -1
found -1 2.14.7+dfsg-1~exp1
tags -1 buster sid
thanks

Hi! Sebastiaan asked us to separate the python-qt4 bug from the original 
intent of 784514 which Qt4's webkit to better handle the differences, so here 
we are.

He also asked me for a timeframe: I am waiting for KF5's maintainer to push 
the latest release and a couple more packages. If everything goes well I 
expect to ask FTP masters to remove qtwebkit by January, maybe even on 
December.

Regards, Lisandro.

-- 
You know you're brilliant, but maybe you'd like to understand what
you did 2 weeks from now.
  Linus Benedict Torvalds.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Processed (with 3 errors): Cloning

[Debian Bug Tracking System]

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

> clone 784514 -1
Bug #784514 {Done: Sebastiaan Couwenberg } [src:qgis] 
[qgis] Qt4's WebKit removal
Bug 784514 cloned as bug 882663
Failed to clone 784514: Not altering archived bugs; see unarchive.

> found -1 2.14.7+dfsg-1~exp1
Failed to add found on -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_found did not pass regex check
.

> tags -1 buster sid
Failed to alter tags of Bug -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_tag did not pass regex check
.

> thanks
Stopping processing here.

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

Bug#882648: exim4: remote code execution in chunking

[Andreas Metzler]

On 2017-11-25 Salvatore Bonaccorso  wrote:
> On Sat, Nov 25, 2017 at 11:34:56AM +0100, Andreas Metzler wrote:
[...]
>> please note that Debian/stable is patched to set 
>>  chunking_advertise_hosts =
>> by default. Therefore stable users should not be affected unless they
>> have locally set chunking_advertise_hosts to a nonempty value.

> Ack, let's leave the severity though to grave due to the immediate
> issue for unstable/experimental version.
[...]

Agreed. As a workaround I have just uploaded -10 to unstable with
urgency=critical, re-introducing the patch present in Debian/stable.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#882648: exim4: remote code execution in chunking

[Salvatore Bonaccorso]

Hi,

[just some additional comments]

On Sat, Nov 25, 2017 at 11:34:56AM +0100, Andreas Metzler wrote:
> On 2017-11-25 Dominic Hargreaves  wrote:
> > Package: exim4
> > Version: 4.89-9
> > Severity: grave
> > Tags: security
> > Justification: remote code execution
> 
> > - Forwarded message from Phil Pennock  -
> [...]
> > With immediate effect, please apply this workaround: if you are running
> > Exim 4.88 or newer (4.89 is current, 4.90 is upcoming) then in the main
> > section of your Exim configuration, set:
> 
> >   chunking_advertise_hosts =
> [...]
> > - End forwarded message -
> 
> Hello,
> 
> please note that Debian/stable is patched to set 
>  chunking_advertise_hosts =
> by default. Therefore stable users should not be affected unless they
> have locally set chunking_advertise_hosts to a nonempty value.

Ack, let's leave the severity though to grave due to the immediate
issue for unstable/experimental version.

> Also there seem to be two separate issues
> https://bugs.exim.org/show_bug.cgi?id=2199
> and
> https://bugs.exim.org/show_bug.cgi?id=2201

yes. I have explicitly associated #882648 with
https://bugs.exim.org/show_bug.cgi?id=2199 and then
https://bugs.exim.org/show_bug.cgi?id=2201 separately in the
security-tracker, cf. https://security-tracker.debian.org/exim4
(will update it once CVEs assigned).

Regards,
Salvatore

Bug#882659: vice: Segfault on start

[Marco Presi]

Package: vice
Version: 3.1.0.dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I am using vice since a long time, it always worked perfectly. Yesterday I re-
installed it and I am not able to run it anymore.

I just type "x64" on the command line and the program segfault immediately.
Downloading the software from the upstream website and compiling from source
with default build options solved temporarly the problem.

I am attaching here the output of the debian package version. I am available to
help to solve this issue.

Regards,

Marco.


==

zufus@irmafamily:~$ /usr/bin/x64
Detecting ISA HardSID boards.
Could not open '/dev/port'.
Cannot get permission to access $300.
Detecting PCI HardSID boards.
No PCI HardSID boards found.
HW scale not available, forcing to disabled
HW scale not available, forcing to disabled

(x64:15202): Gtk-WARNING **: Theme parsing error: gtk3.css:1463:13: not a
number

(x64:15202): Gtk-WARNING **: Theme parsing error: gtk3.css:1463:13: Expected a
string.

*** VICE Version 3.1 ***
OS compiled for: Linux glibc 2.24
GUI compiled for: GTK+
CPU compiled for: AMD64/x86_64
Compiler used: GCC-6.3.0
Current OS:  (glibc 2.25)
Current CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz

Welcome to x64, the free portable C64 Emulator.

Current VICE team members:
Martin Pottendorfer, Marco van den Heuvel, Fabrizio Gennari, Groepaz,
Olaf Seibert, Marcus Sutton, Kajtar Zsolt, AreaScout, Bas Wassink.

This is free software with ABSOLUTELY NO WARRANTY.
See the "About VICE" command for more info.

X11: GTK version compiled with: 3.22 (xf86 ext:yes cairo:yes pango:yes VTE:yes
hwscale:no fullscreen:yes ui-threads:no)
Errore di segmentazione




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

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

Versions of packages vice depends on:
ii  dpkg 1.19.0.4
ii  install-info 6.5.0.dfsg.1-1
ii  libasound2   1.1.3-5
ii  libatk1.0-0  2.26.1-1
ii  libc62.25-2
ii  libcairo-gobject21.15.8-2
ii  libcairo21.15.8-2
ii  libgcc1  1:7.2.0-16
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.54.2-1
ii  libgnutls30  3.5.16-1
ii  libgtk-3-0   3.22.26-1
ii  libjpeg62-turbo  1:1.5.2-2
ii  libpango-1.0-0   1.40.13-2
ii  libpangocairo-1.0-0  1.40.13-2
ii  libpcre2-8-0 10.22-3
ii  libpng16-16  1.6.34-1
ii  libpulse011.1-2
ii  libreadline7 7.0-3
ii  libstdc++6   7.2.0-16
ii  libvte-2.91-00.50.2-2
ii  libx11-6 2:1.6.4-3
ii  libxrandr2   2:1.5.1-1
ii  libxxf86vm1  1:1.1.4-1+b2
ii  zlib1g   1:1.2.8.dfsg-5

vice recommends no packages.

vice suggests no packages.

Bug#882648: exim4: remote code execution in chunking

[Andreas Metzler]

On 2017-11-25 Dominic Hargreaves  wrote:
> Package: exim4
> Version: 4.89-9
> Severity: grave
> Tags: security
> Justification: remote code execution

> - Forwarded message from Phil Pennock  -
[...]
> With immediate effect, please apply this workaround: if you are running
> Exim 4.88 or newer (4.89 is current, 4.90 is upcoming) then in the main
> section of your Exim configuration, set:

>   chunking_advertise_hosts =
[...]
> - End forwarded message -

Hello,

please note that Debian/stable is patched to set 
 chunking_advertise_hosts =
by default. Therefore stable users should not be affected unless they
have locally set chunking_advertise_hosts to a nonempty value.

Also there seem to be two separate issues
https://bugs.exim.org/show_bug.cgi?id=2199
and
https://bugs.exim.org/show_bug.cgi?id=2201

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#880047: marked as done (postgrey doesn't start because it can't write its pid)

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 10:34:26 +
with message-id 
and subject line Bug#880047: fixed in postgrey 1.36-5
has caused the Debian Bug report #880047,
regarding postgrey doesn't start because it can't write its pid
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.)


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

Dear Maintainer,

The default init script that comes with Postgrey on Debian 9 fails to start 
after a reboot. The installer creates /var/run/postgrey and writes its pid 
there but /var/run is a tmpfs file system and so on a reboot /var/run/postgrey 
ceases to exist. The init script for Postgrey does not attempt to create 
/var/run/postgrey and just fails to start when it can't write to 
/var/run/postgrey. When postgrey fails to start then Postfix starts complaining 
that it is misconfigured and begins bouncing emails. I was able to fix this by 
adding these lines to the do_start function in the init script:

# Assure that /var/run/postgrey exists
[ -d /var/run/postgrey ] || mkdir -p /var/run/postgrey

if [ "$DAEMON_USER" != "root" ]; then
chown "$DAEMON_USER" /var/run/postgrey
fi


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

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

Versions of packages postgrey depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.61
pn  libberkeleydb-perl 
pn  libnet-dns-perl
pn  libnet-server-perl 
pn  libnetaddr-ip-perl 
ii  perl   5.24.1-3+deb9u2
ii  ucf3.0036

Versions of packages postgrey recommends:
pn  libnet-rblclient-perl  
pn  libparse-syslog-perl   
ii  postfix3.1.6-0+deb9u1

postgrey suggests no packages.
--- End Message ---
--- Begin Message ---
Source: postgrey
Source-Version: 1.36-5

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

Debian distribution maintenance software
pp.
Antonio Radici  (supplier of updated postgrey 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: Sat, 25 Nov 2017 10:18:01 +
Source: postgrey
Binary: postgrey
Architecture: source
Version: 1.36-5
Distribution: unstable
Urgency: medium
Maintainer: Antonio Radici 
Changed-By: Antonio Radici 
Description:
 postgrey   - greylisting implementation for Postfix
Closes: 756813 880047
Changes:
 postgrey (1.36-5) unstable; urgency=medium
 .
   * debian/postgrey.init: create /var/run/postgrey if it
 does not exist, patch provided by Laurent Bigonville .
 (Closes: 756813, 880047)
Checksums-Sha1:
 ec22c83a36877d2ccfcf8614d955af5d14c5b46c 1958 postgrey_1.36-5.dsc
 095ef14ed811abacca3da67d4ebbbcc028f08fd0 23428 postgrey_1.36-5.debian.tar.xz
 6d892bb8256ac5c7ab16185a3945b3546405673f 5423 postgrey_1.36-5_amd64.buildinfo
Checksums-Sha256:
 e914fa55284d157e2daddf6eec05b88d7088eaf977dcc3a462c1b60b9b6972ff 1958 
postgrey_1.36-5.dsc
 9dc4ef6c4a0e2defcd095b6023a0dea817be7b6e15ec5914920fe1c8a17182dd 23428 
postgrey_1.36-5.debian.tar.xz
 8566033e19a575fc6cdc5c62254e137c8d60cfdccdaffb4ab595c9db9ea5c264 5423 
postgrey_1.36-5_amd64.buildinfo
Files:
 b14a9a6943c90550ff6ee0ce5afc172a 1958 mail optional postgrey_1.36-5.dsc
 9a35fc71d73a56f555e56b78701e0725 23428 mail optional 
postgrey_1.36-5.debian.tar.xz
 479706fc5c8b2ad39cb856f06991283f 5423 mail optional 
postgrey_1.36-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEQObYrBkA1SRrfOa1NcjIiHLLHu0FAloZRIITHGFudG9uaW9A

Processed: Re: Gedit breaks when writing to a file

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo unreproducible
Bug #882055 [gedit] Gedit breaks when writing to a file
Added tag(s) unreproducible and moreinfo.

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

Bug#882055: Gedit breaks when writing to a file

[Michael Biebl]

Control: tags -1 moreinfo unreproducible


On Thu, 23 Nov 2017 13:28:02 +0100 Narcis Garcia 
wrote:
> Worked fine, with no error, on Gedit version 3.10
> 
> The problem seems to be, although text file is readable and writable to
> owner & group & others, when saving from another user different to file
> owner.

Problem is not reproducible here
I've created a file (userA:userA owned), then ran chmod 646 file.txt.
Gedit will write to the file just fine.

Please install dbgsym packages for gedit and create a proper backtrace.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#882592: Trackpad behaves erratic

[Jörg-Volker Peetz]

Package: libinput10
Version: 1.9.2-1

Dear Maintainer(s),

this is to confirm the regression this version introduces and to describe some
problems.
After update from version 1.8.3-1 (also update of libc6 from version 2.24-15)
the mouse clicks from my Logitech K830 keyboard with built in touchpad
(appearing like a PS/2 mouse) sometimes make problems.
Double tapping to maximize a window in openbox doesn't work at all any more.
Double tapping to select a word in text doesn't work, it needs three taps now.
Sometimes, after using the emulated middle mouse button the left mouse button
behaves like the middle button. To recover, I normally have to press the right
mouse button.

Regards,
jvp.


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

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

Versions of packages libinput10 depends on:
ii  libc6 2.25-2
ii  libevdev2 1.5.7+dfsg-1
ii  libinput-bin  1.9.2-1
ii  libmtdev1 1.1.5-1+b1
ii  libudev1  235-3
ii  libwacom2 0.26-1

Bug#849077: please upgrade wpa and report your experience

[Andrew Shadura]

Hi,

I've just uploaded wpa 2.6 into unstable once again. Please upgrade,
test and let me know if it works for you.

-- 
Cheers,
  Andrew

Processed: bug 882648 is forwarded to https://bugs.exim.org/show_bug.cgi?id=2199

[Debian Bug Tracking System]

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

> forwarded 882648 https://bugs.exim.org/show_bug.cgi?id=2199
Bug #882648 [exim4] exim4: remote code execution in chunking
Set Bug forwarded-to-address to 'https://bugs.exim.org/show_bug.cgi?id=2199'.
> thanks
Stopping processing here.

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

Processed: found 882648 in 4.89-1

[Debian Bug Tracking System]

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

> found 882648 4.89-1
Bug #882648 [exim4] exim4: remote code execution in chunking
Marked as found in versions exim4/4.89-1.
> thanks
Stopping processing here.

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

Processed: found 882648 in 4.89-2+deb9u1

[Debian Bug Tracking System]

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

> found 882648 4.89-2+deb9u1
Bug #882648 [exim4] exim4: remote code execution in chunking
Marked as found in versions exim4/4.89-2+deb9u1.
> thanks
Stopping processing here.

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

Bug#882648: exim4: remote code execution in chunking

[Dominic Hargreaves]

Package: exim4
Version: 4.89-9
Severity: grave
Tags: security
Justification: remote code execution

Source: https://lists.exim.org/lurker/message/20171125.034842.d1d75cac.en.html

- Forwarded message from Phil Pennock  -

Date: Fri, 24 Nov 2017 22:48:42 -0500
From: Phil Pennock 
To: exim-annou...@exim.org
Subject: [exim-announce] Critical Exim Security Vulnerability: disable chunking
Reply-To: exim-announce-ow...@exim.org

Folks,

A remote code execution vulnerability has been reported in Exim, with
immediate public disclosure (we were given no private notice).
A tentative patch exists but has not yet been confirmed.

With immediate effect, please apply this workaround: if you are running
Exim 4.88 or newer (4.89 is current, 4.90 is upcoming) then in the main
section of your Exim configuration, set:

  chunking_advertise_hosts =

That's an empty value, nothing on the right of the equals.  This
disables advertising the ESMTP CHUNKING extension, making the BDAT verb
unavailable and avoids letting an attacker apply the logic.

This should be a complete workaround.  Impact of applying the workaround
is that mail senders have to stick to the traditional DATA verb instead
of using BDAT.

We've requested CVEs.  More news will be forthcoming as we get this
worked out.

-Phil



-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-announce Exim 
details at http://www.exim.org/ ##


- End forwarded message -

Bug#882624: marked as done (sbd FTBFS with glibc 2.25)

[Debian Bug Tracking System]

Your message dated Sat, 25 Nov 2017 09:10:25 +
with message-id 
and subject line Bug#882624: fixed in sbd 1.3.1-2
has caused the Debian Bug report #882624,
regarding sbd FTBFS with glibc 2.25
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.)


-- 
882624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sbd
Version: 1.3.1-1
Severity: serious

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

...
sbd-common.c: In function 'watchdog_populate_list':
sbd-common.c:268:13: error: In the GNU C Library, "makedev" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "makedev", include 
 directly. If you did not intend to use a system-defined macro
 "makedev", you should undefine it after including . [-Werror]
   {makedev(10,130), 0};
 ^~~



   
sbd-common.c:293:13: error: In the GNU C Library, "makedev" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "makedev", include 
 directly. If you did not intend to use a system-defined macro
 "makedev", you should undefine it after including . [-Werror]
   watchdogs[num_watchdogs++] = makedev(major, minor);
 ^  



   
sbd-common.c:342:13: error: In the GNU C Library, "major" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "major", include 
 directly. If you did not intend to use a system-defined macro
 "major", you should undefine it after including . [-Werror]
 major(watchdogs[i]), minor(watchdogs[i]));
 ^~ 



 
sbd-common.c:342:13: error: In the GNU C Library, "minor" is defined
 by . For historical compatibility, it is
 currently defined by  as well, but we plan to
 remove this soon. To use "minor", include 
 directly. If you did not intend to use a system-defined macro
 "minor", you should undefine it after including . [-Werror]
cc1: all warnings being treated as errors
Makefile:397: recipe for target 'sbd-common.o' failed
make[3]: *** [sbd-common.o] Error 1
--- End Message ---
--- Begin Message ---
Source: sbd
Source-Version: 1.3.1-2

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

Debian distribution maintenance software
pp.
Valentin Vidic  (supplier of updated sbd 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: Sat, 25 Nov 2017 08:25:18 +0100
Source: sbd
Binary: sbd
Architecture: source
Version: 1.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Valentin Vidic 
Description:
 sbd- STONITH Block Device daemon
Closes: 882624
Changes:
 sbd (1.3.1-2) unstable; urgency=medium