Bug#907819: I'm temped to drop python support from jellyfish - please help if you need this

[Andreas Tille]

On Fri, Sep 14, 2018 at 08:15:26AM +0200, Andreas Tille wrote:
> 
> If I will not get any help I'll consider removing the Python module
> package to safe all other dependencies from jellyfish.  Sorry, but we
> are loosing currently more and more packages due to RC bugs and I need
> to draw a cutting line where to spent my time.

Python module removed.  I'd love to get it back with your help.
 
Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#907819: marked as done (jellyfish: Does not build on paths containing "-L" resulting in random FTBFS when built by sbuild)

[Debian Bug Tracking System]

Your message dated Fri, 21 Sep 2018 07:19:42 +
with message-id 
and subject line Bug#907819: fixed in jellyfish 2.2.10-1
has caused the Debian Bug report #907819,
regarding jellyfish: Does not build on paths containing "-L" resulting in 
random FTBFS when built by sbuild
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.)


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

Dear maintainer:

I tried to build this package in sid and it failed with this error:


/usr/bin/ld: cannot find -ljellyfish-2.0
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-g++' failed with exit status 1


I'm building on amd64 and this error happens randomly for me
(sometimes it fails, sometimes it does not), but it happened at least
once in the official autobuilders in another architecture:

https://buildd.debian.org/status/fetch.php?pkg=jellyfish&arch=powerpc&ver=2.2.8-3&stamp=1531093335&raw=0

so it seems that the error is not architecture-specific and we can
assume it will also fail randomly on the official buildds too.

I've put all my failed build logs (buster and sid) here:

https://people.debian.org/~sanvila/build-logs/jellyfish/

(but some of those failures are not linking failures).

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: jellyfish
Source-Version: 2.2.10-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated jellyfish package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 21 Sep 2018 08:45:53 +0200
Source: jellyfish
Binary: jellyfish libjellyfish-2.0-2 libjellyfish-2.0-dev libjellyfish-perl 
jellyfish-examples
Architecture: source
Version: 2.2.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 jellyfish  - count k-mers in DNA sequences
 jellyfish-examples - count k-mers in DNA sequences (examples for testing)
 libjellyfish-2.0-2 - count k-mers in DNA sequences (dynamic library of 
jellyfish)
 libjellyfish-2.0-dev - count k-mers in DNA sequences (development files of 
jellyfish)
 libjellyfish-perl - count k-mers in DNA sequences (Perl bindings of jellyfish)
Closes: 907819
Changes:
 jellyfish (2.2.10-1) unstable; urgency=medium
 .
   * New upstream version
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.1.4
   * Adapt watch file to also catch v$VERSION tarball names
   * Clean up quilt patches
   * Catch exceptions by reference
   * Do not replace random '-L' strings in command line
 Closes: #907819
   * Drop python3-dna-jellyfish package since the Python module had issues in
 build process and nobody seemed to be interested to help solving theses
Checksums-Sha1:
 0e5bdedd201409d6dccd4b9b3e8a50630e00c596 2466 jellyfish_2.2.10-1.dsc
 ff6da36047de84a94925623bd7355d467e58f4e9 677009 jellyfish_2.2.10.orig.tar.gz
 bc6a020795b7287796b9ad5d24c4cb5559eb8778 11856 jellyfish_2.2.10-1.debian.tar.xz
Checksums-Sha256:
 ce72c4977a972d97810a3e1813cd2cf758691e6a2a0ca52ff8098716de074a0a 2466 
jellyfish_2.2.10-1.dsc
 49137356b1cdd014cb70e866f0739fc3fafea6421fa22cc64bcfeba55fc1dc27 677009 
jellyfish_2.2.10.orig.tar.gz
 9dc571e8a0666d4e4755169f35f88e25b2f9d5100fa60257055ce55ff5375e08 11856 
jellyfish_2.2.10-1.debian.tar.xz
Files:
 521f5071f06a1ef8a782cc376c8386cd 2466 science optional jellyfish_2.2.10-1.dsc
 f500fe1a92299b41524e508580cd1192 677009 science optional 
jellyfish_2.2.10.orig.tar.gz
 f092157cd0590d11adb1f8e5c5f7557d 11856 science optional 
jellyfish_2.2.10-1.debian.tar.xz

Processed: Bug #908766 in liblog-dispatch-message-passing-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #908766 [src:liblog-dispatch-message-passing-perl] 
liblog-dispatch-message-passing-perl: FTBFS (test failures) with 
liblog-dispatch-perl 2.68-1
Added tag(s) pending.

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

Bug#909292: cm-super FTBFS: dh_installtex no longer supports --priority

[Adrian Bunk]

Source: cm-super
Version: 0.3.4-12
Severity: serious
Tags: ftbfs

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

...
dh_installtex --package=cm-super --priority=50  \
map=MixedMap,cm-super-extended-t1.map 
map=MixedMap,cm-super-extended-t2a.map map=MixedMap,cm-super-extended-t2b.map 
map=MixedMap,cm-super-extended-t2c.map map=MixedMap,cm-super-extended-ts1.map 
map=MixedMap,cm-super-extended-x2.map
Unknown option: priority
dh_installtex: unknown option or error during option parsing; aborting
make: *** [debian/rules:136: install-stamp-cmsuper] Error 25

Bug#908766: Bug #908766 in liblog-dispatch-message-passing-perl marked as pending

[Damyan Ivanov]

Control: tag -1 pending

Hello,

Bug #908766 in liblog-dispatch-message-passing-perl reported by you has been 
fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/liblog-dispatch-message-passing-perl/commit/0ee95a4538a3fd4d77b7a092b160a23208f7ebc2


add patch adapting to the changes in Log::Dispatch 2.68

Fixes test failures and Closes: #908766



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/908766

Bug#908766: marked as done (liblog-dispatch-message-passing-perl: FTBFS (test failures) with liblog-dispatch-perl 2.68-1)

[Debian Bug Tracking System]

Your message dated Fri, 21 Sep 2018 07:49:52 +
with message-id 
and subject line Bug#908766: fixed in liblog-dispatch-message-passing-perl 
0.009-4
has caused the Debian Bug report #908766,
regarding liblog-dispatch-message-passing-perl: FTBFS (test failures) with 
liblog-dispatch-perl 2.68-1
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.)


-- 
908766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblog-dispatch-message-passing-perl
Version: 0.009-3
Severity: serious
Tags: upstream ftbfs sid buster
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.debian.net, liblog-dispatch-perl 2.68-1 breaks
liblog-dispatch-message-passing-perl('s test suite):


t/00_compile.t .. 
ok 1 - use Log::Dispatch::Message::Passing;
1..1
ok
t/basic.t ... 
ok 1
not ok 2

#   Failed test at t/basic.t line 23.
# Structures begin differing at:
#  $got->[0]{name} = Does not exist
# $expected->[0]{name} = 'myapp_logstash'
1..2
# Looks like you failed 1 test of 2.
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/2 subtests 
t/log_message_structured.t .. skipped: Broken currently

Test Summary Report
- ---
t/basic.t (Wstat: 256 Tests: 2 Failed: 1)
  Failed test:  2
  Non-zero exit status: 1
Files=3, Tests=3,  0 wallclock secs ( 0.02 usr  0.01 sys +  0.36 cusr  0.05 
csys =  0.44 CPU)
Result: FAIL


I'm not sure if the changes in Log::Dispatch::Output 2.68 are (not
only the cause but also) the actual problem, or if
Log::Dispatch::Message::Passing somehow needs to adapt ...
Hence not forwarding upstream yet; maybe someone gets a clearer
picture of this issue?


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAluaegxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYTWg//bhffDM2qSgZCCyaoV3x24l93LS4JL0O/Nf9nI1y4jdLSHxQtKpWmEp1y
T0umYjUUvoDBXUV3kpyxF0xSd3qFsXz9jNts26R4/tmbClF5bqjHDsRrgxdE8J0t
Ejb4gQW1s9icCrYVdAY2GQ6q8H0kXfJaophgfVJZiTwHiqvbMlKTbBbkAIvqoyRQ
K86CqjzjMbG1bxYR4JDR2rz1SQQVFd1MFA3YU1LhFT/g5zC8LwDwE3CpfJQaWirP
3pUb58ScLf+C2VT1UIOwIFS0JR/QychFkwDkRBlHAuLJimXN2wPeGYu3oMoMXkFj
Efw1q3MErjEKaNMWYj1BnOR1iga/5jSxtZc9B5aSw567A5Mcutt6ck/6khJqVWaf
hmguTekFij14cbqke5Dovm3kX3Sl3VkFeaLXpgR0TnbTikGgSeY1XLh8PllaaO09
ssERnA9XqK0UmIhaLwy9lP5B08fvC9B9M3g/3Rt+lYIcvzhvLHDfAvba2gweYseb
AK5YFUWsJNFtKGv56Nk6NkjH0TW3iQiv8A0kqO9I3AaXbKELIyWlv6ETbwfC5vJV
DAB6CM0yzRXhyYBKhmPfZuyqPZpPeGPaEaup1okwNA45X9R0/2WwWsfRI3mDwS0j
sGG4Beszwa4O96wBZXoaeBhFykF2wqdvDENcjZSLP6XU7HgKfwM=
=msdK
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: liblog-dispatch-message-passing-perl
Source-Version: 0.009-4

We believe that the bug you reported is fixed in the latest version of
liblog-dispatch-message-passing-perl, which is due to be installed in the 
Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated 
liblog-dispatch-message-passing-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 21 Sep 2018 07:24:27 +
Source: liblog-dispatch-message-passing-perl
Binary: liblog-dispatch-message-passing-perl
Architecture: source
Version: 0.009-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Closes: 908766
Description: 
 liblog-dispatch-message-passing-perl - log events to Message::Passing
Changes:
 liblog-dispatch-message-passing-perl (0.009-4) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * debian/*: update URLs from {search,www}.cpan.org to MetaCPAN.
   * debian/*: update GitHub URLs to use HTTPS.
 .
   [ Damyan Ivanov ]
   * add patch adapting to the changes in Log::Dispatch 2.68.
 Fixes test failures and Closes: #908766
   * bump debhelper compatibility level to 11
   * convert packaging from cdbs 

Bug#863520: Same problem here

[rollop...@gmail.com]

Sep 21 07:56:39 mailserver cyrus/master[430]: process type:SERVICE
name:imaps path:/usr/lib/cyrus/bin/imapd age:1.911s pid:24508 exited,
status 75
Sep 21 07:56:39 mailserver cyrus/imaps[24509]: TLS server engine: No
client CA certs specified. Client side certs may not work
Sep 21 07:57:02 mailserver cyrus/imaps[24509]: Fatal error: Internal
error: assertion failed: lib/cyrusdb_twoskip.c: 1727: key && keylen
Sep 21 07:57:02 mailserver cyrus/master[430]: process type:SERVICE
name:imaps path:/usr/lib/cyrus/bin/imapd age:23.130s pid:24509 exited,
status 75
Sep 21 07:57:03 mailserver cyrus/imaps[24515]: TLS server engine: No
client CA certs specified. Client side certs may not work


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

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

Versions of packages cyrus-imapd depends on:
ii  cyrus-common  2.5.10-3
ii  dpkg  1.18.25
ii  libc6 2.24-11+deb9u3
ii  libicu57  57.1-6+deb9u2
ii  libsasl2-2    2.1.27~101-g0780600+dfsg-3
ii  libssl1.1 1.1.0f-3+deb9u2
ii  libwrap0  7.6.q-26
ii  zlib1g    1:1.2.8.dfsg-5

Bug#909287: Bug #909287 in python-httpretty marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/python/python-httpretty/commit/0583dae1d0bec29cc4fe338e9bee212a704fbfe7


  * Remove test that is doing network access during the build. Thanks to
Adrian Bunk for the bug report (Closes: #909287).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909287

Processed: Bug #909287 in python-httpretty marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909287 [src:python-httpretty] python-httpretty accesses the internet 
during the build
Added tag(s) pending.

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

Processed: severity of 889064 is serious

[Debian Bug Tracking System]

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

> severity 889064 serious
Bug #889064 [automysqlbackup] automysqlbackup: monthly backup fails with line 
427: [: too many arguments
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 888847 is serious

[Debian Bug Tracking System]

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

> severity 47 serious
Bug #47 [src:grokmirror] grokmirror: missing dependency on 
python-pkg-resources
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#909292: marked as done (cm-super FTBFS: dh_installtex no longer supports --priority)

[Debian Bug Tracking System]

Your message dated Fri, 21 Sep 2018 08:40:42 +
with message-id 
and subject line Bug#909292: fixed in cm-super 0.3.4-13
has caused the Debian Bug report #909292,
regarding cm-super FTBFS: dh_installtex no longer supports --priority
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.)


-- 
909292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cm-super
Version: 0.3.4-12
Severity: serious
Tags: ftbfs

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

...
dh_installtex --package=cm-super --priority=50  \
map=MixedMap,cm-super-extended-t1.map 
map=MixedMap,cm-super-extended-t2a.map map=MixedMap,cm-super-extended-t2b.map 
map=MixedMap,cm-super-extended-t2c.map map=MixedMap,cm-super-extended-ts1.map 
map=MixedMap,cm-super-extended-x2.map
Unknown option: priority
dh_installtex: unknown option or error during option parsing; aborting
make: *** [debian/rules:136: install-stamp-cmsuper] Error 25
--- End Message ---
--- Begin Message ---
Source: cm-super
Source-Version: 0.3.4-13

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

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

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated cm-super 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, 21 Sep 2018 17:02:20 +0900
Source: cm-super
Binary: cm-super-minimal cm-super cm-super-x11
Architecture: source all
Version: 0.3.4-13
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX maintainers 
Changed-By: Norbert Preining 
Description:
 cm-super   - TeX font package (full version) with CM (EC) in Type1 in T1, T2*,
 cm-super-minimal - TeX font package (minimal version) with CM/EC in Type1 in 
T1, T2*
 cm-super-x11 - Make the cm-super fonts available to X11
Closes: 909292
Changes:
 cm-super (0.3.4-13) unstable; urgency=medium
 .
   * remove a forgotten --priority (Closes: #909292)
Checksums-Sha1:
 aa59b4c9da59a0428b1bd4819719a86e9c133dea 1671 cm-super_0.3.4-13.dsc
 e512c76b6edfc895980dc1a6f2d5642bc203119f 13467 cm-super_0.3.4-13.diff.gz
 e138c757d0a7bd59099f1b760870df6d69b825d4 5814136 
cm-super-minimal_0.3.4-13_all.deb
 8acd655e9910ca6e904ca1700523845ced6e71a0 270112 cm-super-x11_0.3.4-13_all.deb
 1d8a6e9c1f428854307b1c20c8d94ef4186bfbb3 18680680 cm-super_0.3.4-13_all.deb
 6a66558b89c43338353360530b8418acfc9b88b9 6913 cm-super_0.3.4-13_amd64.buildinfo
Checksums-Sha256:
 68feea2d119fdc4f20d05b9a5feed32c6ff51185a461bde6ac8c0784fdaeaf04 1671 
cm-super_0.3.4-13.dsc
 52822c5069ea0e7fb0f6912dce49f5d84fdafb00bee0d05e23e9f68b95ca565b 13467 
cm-super_0.3.4-13.diff.gz
 772f3942da81a1babe6287426c873528d7472733f451187500fcbeff3683b6b3 5814136 
cm-super-minimal_0.3.4-13_all.deb
 08cdd915d1f7883b3dc61f93789c5056c4646120b2fbb0b217ac22c9b4fde22b 270112 
cm-super-x11_0.3.4-13_all.deb
 4e1c9123b764b251c683c1b57d236c97c0258f9f9c6c6d48f5b99dc5f656cdea 18680680 
cm-super_0.3.4-13_all.deb
 d13fea575b81961db6d821f00e0317d635f805e4effcbdd380a7fd8916641d3b 6913 
cm-super_0.3.4-13_amd64.buildinfo
Files:
 5078e4a2a2cf62e789326f9019f5f9b8 1671 fonts optional cm-super_0.3.4-13.dsc
 ed7e1ecbac66321824e22da7e76d4910 13467 fonts optional cm-super_0.3.4-13.diff.gz
 84d0155a9888ebba67bab5c0fb4d1cb0 5814136 fonts optional 
cm-super-minimal_0.3.4-13_all.deb
 f3ee7fc81fc4a1ece78fc9e074c97a67 270112 fonts optional 
cm-super-x11_0.3.4-13_all.deb
 fb2b9e81ed8d73ab51bea793d0e71022 18680680 fonts optional 
cm-super_0.3.4-13_all.deb
 933c8172f7dce508d343d96e751ad366 6913 fonts optional 
cm-super_0.3.4-13_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAlukpeYACgkQ2A4JsIcU
AGb7zQgAjrzl1A1hG1kfKKxn9B3A3ud+fCjONIurYJlr3S8L87UWu1tf0+rhLFaP
TKGV/QqlzqdEpN4V0vvuQeO/uft+ltDO3CoKqzFrQFLds/ThMvtIcN8u/YPn7kdq
fr+DLJO2vXsyRplCJaUJhels5GvHjoc5pzmOydGYIm6Xv4BY2+5iB8kAUUwrI8Jj
zW69R9VXyprI5rYdB74zH+UX3KYjflgDsRZjZBp5tvx1e4IgcQFPgoq9MLGFodNU
XtywdiW2Lec1uIm4vEEuIPgQT9vbB7DUoYI/YPjWQMOI1d3LJA/supjua//KINF+
7D6m7D/11zfPlLsEm5WpgCXQKbOguQ==
=M1uZ
-

Bug#909287: marked as done (python-httpretty accesses the internet during the build)

[Debian Bug Tracking System]

Your message dated Fri, 21 Sep 2018 08:41:31 +
with message-id 
and subject line Bug#909287: fixed in python-httpretty 0.9.5-2
has caused the Debian Bug report #909287,
regarding python-httpretty accesses the internet during the build
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.)


-- 
909287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-httpretty
Version: 0.9.5-1
Severity: serious
Tags: ftbfs

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

...
-
1) ERROR: fakesock.socket#getpeercert should return a hardcoded fake certificate

   Traceback (most recent call last):
/usr/lib/python2.7/dist-packages/nose/case.py line 197 in runTest
  self.test(*self.arg)
/usr/lib/python2.7/dist-packages/mock/mock.py line 1305 in patched
  return func(*args, **keywargs)
tests/unit/test_core.py line 201 in test_fakesock_socket_getpeercert
  socket.connect(('somewhere.com', 80))
httpretty/core.py line 404 in connect
  self.truesock.connect(self._address)
/usr/lib/python2.7/socket.py line 228 in meth
  return getattr(self._sock,name)(*args)
   gaierror: [Errno -3] Temporary failure in name resolution


-
12 tests run in 1.5 seconds. 
1 error (11 tests passed)
make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: python-httpretty
Source-Version: 0.9.5-2

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-httpretty package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 21 Sep 2018 10:12:41 +0200
Source: python-httpretty
Binary: python-httpretty python3-httpretty
Architecture: source all
Version: 0.9.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-httpretty - HTTP client mock - Python 2.x
 python3-httpretty - HTTP client mock - Python 3.x
Closes: 909287
Changes:
 python-httpretty (0.9.5-2) unstable; urgency=medium
 .
   * Add RES_OPTIONS=attempts:0 to avoid resolving in unit tests.
   * Remove test that is doing network access during the build. Thanks to
 Adrian Bunk for the bug report (Closes: #909287).
Checksums-Sha1:
 5f6afa0092836219b0b64eab71073be350b22c44 2653 python-httpretty_0.9.5-2.dsc
 ea5ec06e9635cebbf4a6ad03789b184b9ff64df3 4720 
python-httpretty_0.9.5-2.debian.tar.xz
 e70ba6ce3bf2c65bdfe2133ea7059081e1ad0697 19612 python-httpretty_0.9.5-2_all.deb
 651bffaf1232bea9ab182a3152274bf5af5e7b65 9024 
python-httpretty_0.9.5-2_amd64.buildinfo
 bffec2878c62aece5784b64c72ec9c42e04e61d5 19684 
python3-httpretty_0.9.5-2_all.deb
Checksums-Sha256:
 d30e8bf2a9d01093fd1565f041c18c8f2d728884159dc809e1c4dc651fc5fc87 2653 
python-httpretty_0.9.5-2.dsc
 55c61e5a78cf9adacb9489d6d2b2927076c9311511ffb4be997aecd719ac617c 4720 
python-httpretty_0.9.5-2.debian.tar.xz
 5dc1ba1824c79938383e372e900a277b32874bb776d3d95d9953d41685a7112e 19612 
python-httpretty_0.9.5-2_all.deb
 4b1ee40d9ecfd007d4e9367a43adc96f2107b194412de7b26c983d2d3aa23b8e 9024 
python-httpretty_0.9.5-2_amd64.buildinfo
 bf42a44e1fb7bc9857ded43b697657844c645d072fb5930315ded32b86c934ca 19684 
python3-httpretty_0.9.5-2_all.deb
Files:
 a7e00bde363c9066ef23e02c562424ea 2653 python optional 
python-httpretty_0.9.5-2.dsc
 716085151feda04d160714bcef7681f5 4720 python optional 
python-httpretty_0.9.5-2.debian.tar.xz
 b2cac9a3f807aca665423cc4636fd09e 19612 python optional 
python-httpretty_0.9.5-2_all.deb
 43d014c5a8033d258f9a5494c6e7c6a8 9024 python optional 
python-httpretty_0.9.5-2_amd64.buildinfo
 a766e48c26a6e6ac368df9e8f46c1f9c 19684 python optional 
python3-httpretty_0.9.5-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtKCq/KhshgVdBnYUq1PlA1hod6

Bug#902256: Bug#909285: [freshplayerplugin] update to the latest version

[Vincent Danjean]

On 21/09/2018 03:44, Alex Volkov wrote:
> Package: freshplayerplugin
> Severity: wishlist
> 
> --- Please enter the report below this line. ---
> 
> The version 0.3.9 fixing the single reported bug is out almost a year ago, is 
> the maintainer doing any job at all?

  The maintainer do not use this package anymore and missed the previous
bug report (probably due to a lack of time when the mail have been received
and then forgetting about it).

  I tried to use the new upstream version. It does not compile strait :
[...]
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:119:12:
 warning: ‘vaapi_context’ is deprecated [-Wdeprecated-declarations]
 struct vaapi_contextva_context;
^
In file included from 
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:45:
/usr/include/x86_64-linux-gnu/libavcodec/vaapi.h:56:29: note: declared here
 struct attribute_deprecated vaapi_context {
 ^
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:
 In function ‘initialize_decoder’:
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:623:37:
 error: ‘CODEC_CAP_TRUNCATED’ undeclared (first use in this function); did you 
mean ‘AV_CODEC_CAP_TRUNCATED’?
 if (vd->avcodec->capabilities & CODEC_CAP_TRUNCATED) {
 ^~~
 AV_CODEC_CAP_TRUNCATED
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:623:37:
 note: each undeclared identifier is reported only once for each function it 
appears in
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:625:29:
 error: ‘CODEC_FLAG_TRUNCATED’ undeclared (first use in this function); did you 
mean ‘AV_CODEC_FLAG_TRUNCATED’?
 vd->avctx->flags |= CODEC_FLAG_TRUNCATED;
 ^~~~
 AV_CODEC_FLAG_TRUNCATED
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:634:5:
 warning: ‘refcounted_frames’ is deprecated [-Wdeprecated-declarations]
 vd->avctx->refcounted_frames = 1;
 ^~
In file included from 
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:44:
/usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:2344:9: note: declared here
 int refcounted_frames;
 ^
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:
 In function ‘issue_frame’:
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:787:5:
 warning: ‘pkt_pts’ is deprecated [-Wdeprecated-declarations]
 int32_t  bitstream_buffer_id = (int32_t)frame->pkt_pts;
 ^~~
In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:38,
 from 
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:44:
/usr/include/x86_64-linux-gnu/libavutil/frame.h:319:13: note: declared here
 int64_t pkt_pts;
 ^~~
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:
 In function ‘decode_frame’:
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:871:5:
 warning: ‘avcodec_decode_video2’ is deprecated [-Wdeprecated-declarations]
 int len = avcodec_decode_video2(vd->avctx, vd->avframe, &got_frame, 
&packet);
 ^~~
In file included from 
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:44:
/usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:4755:5: note: declared here
 int avcodec_decode_video2(AVCodecContext *avctx, AVFrame *picture,
 ^
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:
 In function ‘constructor_ppb_video_decoder’:
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:1193:5:
 warning: ‘avcodec_register_all’ is deprecated [-Wdeprecated-declarations]
 avcodec_register_all();
 ^~~~
In file included from 
/home/vdanjean/debian/mainteneur/freshplayerplugin/build-area/freshplayerplugin-0.3.9/src/ppb_video_decoder.c:44:
/usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:4086:6: note: declared here
 void avcodec_register_all(void);
  ^~~~
make[3]: *** [src/CMakeFiles/freshwrapper-obj.dir/build.make:1054: 
src/CMakeFiles/freshwrapper-obj.dir/ppb_video_decoder.c

Bug#902760: Two failed tests remaining in igraph which are arpack related

[Andreas Tille]

On Mon, Sep 17, 2018 at 09:44:32PM +0200, Andreas Tille wrote:
> Please send `tests/testsuite.log' and all information you think might help:
> 
>To: 
>Subject: [igraph 0.7.1] testsuite: 196 197 failed

with recent libarpack2-dev (3.6.3-1) we are down to one remaining error
inside the test suite:

...
196: Eigenvector centrality (igraph_eigenvector_centrality): ok
197: Non-symmetric ARPACK solver (igraph_arpack_rnsolve): FAILED (arpack.at:66)

Bipartite graphs
...

...
Please send `tests/testsuite.log' and all information you think might help:

   To: 
   Subject: [igraph 0.7.1] testsuite: 197 failed
...

As suggested I'm sending this to  as well and I
also attach the gzipped part of the test log to this mail.

Kind regards

   Andreas.

-- 
http://fam-tille.de


test_197.log.gz
Description: application/gzip

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[Chris Lamb]

Hi Kai-Chung,

> I just polished [1] the changelog file and I'm about to upload the fix. 
> Could you grant me the upload rights to this package? 

I will happily sponsor individual uploads if provided with a .dsc but I
am not in a position to evaluate the DM (I assume?) status.

Or, you can ask the rest of your team?


Best wishes,

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

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[殷啟聰 | Kai-Chung Yan]

Hello Chris,

I just polished [1] the changelog file and I'm about to upload the fix. Could 
you grant me the upload rights to this package? Thank you.

Cheers,
Kai-Chung Yan

[1]: 
https://salsa.debian.org/android-tools-team/android-platform-external-boringssl/commit/f38e0d39c033508d3eaffe354ebedcac33e74813



signature.asc
Description: OpenPGP digital signature

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[殷啟聰 | Kai-Chung Yan]

Hello Chris,
> I will happily sponsor individual uploads if provided with a .dsc but I
> am not in a position to evaluate the DM (I assume?) status.

Then sponsor it is, thanks. I just gave you access to the repository, and 
prepared the changelog. We use the standard git-buildpackage workflow.

> Or, you can ask the rest of your team?

The only actively-involved DD (eighthave) isn't active these days, so had to 
ask you.



signature.asc
Description: OpenPGP digital signature

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[Chris Lamb]

Hi Kai-Chung,

> > I will happily sponsor individual uploads if provided with a .dsc but I
> > am not in a position to evaluate the DM (I assume?) status.
> 
> Then sponsor it is, thanks. I just gave you access to the repository, 
> and prepared the changelog. We use the standard git-buildpackage 
> workflow.

Sorry, please provide a .dsc; I am very busy, alas...


Regards,

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

Bug#908752: marked as done (r-cran-stan: epends on version of libgdal-dev that doesn't exist)

[Debian Bug Tracking System]

Your message dated Fri, 21 Sep 2018 09:34:33 +
with message-id 
and subject line Bug#908752: fixed in r-cran-rstan 2.17.3+dfsg-2
has caused the Debian Bug report #908752,
regarding r-cran-stan: epends on version of libgdal-dev that doesn't exist
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.)


-- 
908752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-stan
Version: 2.17.3+dfsg-1
Severity: important

Dear Maintainer,

The package depends on libgdal-dev >= 2.17.2 which I think is a typo.  The 
highest version of libgdal that is available in both Debian and at the gdal 
site is 2.3.1.



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

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: r-cran-rstan
Source-Version: 2.17.3+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-rstan 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: Thu, 13 Sep 2018 16:30:42 +0200
Source: r-cran-rstan
Binary: r-cran-rstan
Architecture: source
Version: 2.17.3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Description:
 r-cran-rstan - GNU R interface to Stan
Closes: 908752
Changes:
 r-cran-rstan (2.17.3+dfsg-2) unstable; urgency=medium
 .
   * Rebuild with fixed dh-r
 Closes: #908752
   * Standards-Version: 4.2.1
   * Build-Depends: r-cran-stanheaders
Checksums-Sha1:
 6adb8c477a2dfccdd9e38a112ba238913a2d0774 2215 r-cran-rstan_2.17.3+dfsg-2.dsc
 5b65343c2df380fbc02b89fb48060e1d7238a2f4 2588 
r-cran-rstan_2.17.3+dfsg-2.debian.tar.xz
Checksums-Sha256:
 b7260084b9ef977feec1b1a6f53f73ecb1b69d3aaf0e04918ed78ea5cfb8cb6b 2215 
r-cran-rstan_2.17.3+dfsg-2.dsc
 94fcfcd2603fc22f8188b9a40b8e0d496c8924b4058a9c31ea57e62d28bd94e2 2588 
r-cran-rstan_2.17.3+dfsg-2.debian.tar.xz
Files:
 05e14c5249153038f261cbeaa89b0438 2215 gnu-r optional 
r-cran-rstan_2.17.3+dfsg-2.dsc
 5d7ea06444166ea6ccfb625579c94caa 2588 gnu-r optional 
r-cran-rstan_2.17.3+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlukti8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFUYRAAkWJmEJREAl/Zwvtb9RCJDdoMfB+wAiGT
Zt2m8j4ihKD5rbmdAHLmiZc7T8/gRvpItrxEqE7WH/odQD6C0zJNTjYBffjOaR0+
G4d+XuSTJGYPAIQ1ZA19MiFSp1Kpdx3VErBy3avpW/7Oh2FnIlpRWqtF8BZXIK12
SUjYaXbYyOFlVcUsVAluu17C8BhG0bJ7k38sPh0G4cl9QOpqIjRUQ8D/slyMHlzX
sezgHIeFQMj955Vp/ziw8/f+2HfzX3I0dMQRdavTEtUdF5Dixo6KpGTmHedAt+Sc
JA8//GBbII2d/dypAa4EzV/wBE3VVqbwl5mlYo3VAvd7dED6z5Ps33ORuc5LSjEo
aaDEyWsK+QgRxZPyahyOXH0x3cLN+aM6fsvodxUr5NDX7LX+79u9KoeMGj1KDiAH
U/W0FgkMEtXsNMdueRHieEEDNEe+obkIXOVbSKdJyPZqX05kUXIsfCC4/brOeYhR
XuLNQrTpNbajkMujsaz4L35O1AcfmP8mkPm9aQawLOLU7dvJqphAdkBVmAGd3cwJ
OJElz4KCqcA/FJ7TQG+hvnVF5/9W1ASrMQ5mSsDTiIFUG56MImsA/6DqHx6w/B+I
DoLTFM46KaqiuoBNnU6MS4w6mRNE6oGd710BFKRhcH2SkA8KrRswnxziClrvktEI
f5ceOb9oqAM=
=WD9o
-END PGP SIGNATURE End Message ---

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[殷啟聰 | Kai-Chung Yan]

Hello Chris,

> Sorry, please provide a .dsc; I am very busy, alas...

Understood...

I have attached the .buildinfo, .dsc and .changes files, hopefully they are 
sufficient?
Format: 3.0 (quilt)
Source: android-platform-external-boringssl
Binary: android-libboringssl, android-libboringssl-dev
Architecture: armel armhf arm64 amd64 i386 ppc64el
Version: 8.1.0+r23-2
Maintainer: Android Tools Maintainers 

Uploaders: Kai-Chung Yan 
Homepage: https://android.googlesource.com/platform/external/boringssl
Standards-Version: 4.2.1
Vcs-Browser: 
https://salsa.debian.org/android-tools-team/android-platform-external-boringssl
Vcs-Git: 
https://salsa.debian.org/android-tools-team/android-platform-external-boringssl.git
Build-Depends: debhelper (>= 11), dh-exec
Package-List:
 android-libboringssl deb libs optional 
arch=armel,armhf,arm64,amd64,i386,ppc64el
 android-libboringssl-dev deb libdevel optional 
arch=armel,armhf,arm64,amd64,i386,ppc64el
Checksums-Sha1:
 97fae12ac5fbec3282eb17f5d00543e14c094811 20346200 
android-platform-external-boringssl_8.1.0+r23.orig.tar.gz
 10393ba6868a536c9a1d9a0953db8f1e901dc156 7668 
android-platform-external-boringssl_8.1.0+r23-2.debian.tar.xz
Checksums-Sha256:
 51eb22c5f68ce49e35a1726623a257e8e89b29c23bf374a3420a8ac88afe2078 20346200 
android-platform-external-boringssl_8.1.0+r23.orig.tar.gz
 84873533e9be896bb1e252722edb91471fe71e7e018222d9e7669262fda57ec5 7668 
android-platform-external-boringssl_8.1.0+r23-2.debian.tar.xz
Files:
 cdc934e3446620108599fa3870c4c103 20346200 
android-platform-external-boringssl_8.1.0+r23.orig.tar.gz
 6fe74238b3fe7a8bcc75f3626bbed99b 7668 
android-platform-external-boringssl_8.1.0+r23-2.debian.tar.xz
Format: 1.0
Source: android-platform-external-boringssl
Binary: android-libboringssl android-libboringssl-dev
Architecture: source
Version: 8.1.0+r23-2
Checksums-Md5:
 a2d3c17ee2c770c5b3aef455fa03d89d 1559 
android-platform-external-boringssl_8.1.0+r23-2.dsc
Checksums-Sha1:
 fb64107b1154cb4e6a9d880c69e83e03ea13fb35 1559 
android-platform-external-boringssl_8.1.0+r23-2.dsc
Checksums-Sha256:
 a33239d1b82852424cec91575ce3796c72a24b5abf6b0aa254ce1501f5fd2309 1559 
android-platform-external-boringssl_8.1.0+r23-2.dsc
Build-Origin: Ubuntu
Build-Architecture: amd64
Build-Date: Fri, 21 Sep 2018 17:34:00 +0800
Installed-Build-Depends:
 autoconf (= 2.69-11),
 automake (= 1:1.16.1-1.1ubuntu1),
 autopoint (= 0.19.8.1-7),
 autotools-dev (= 20180224.1),
 base-files (= 10.1ubuntu6),
 base-passwd (= 3.5.45),
 bash (= 4.4.18-2ubuntu3),
 binutils (= 2.31.1-6ubuntu1),
 binutils-common (= 2.31.1-6ubuntu1),
 binutils-x86-64-linux-gnu (= 2.31.1-6ubuntu1),
 bsdmainutils (= 11.1.2ubuntu2),
 bsdutils (= 1:2.32-0.1ubuntu1),
 build-essential (= 12.5ubuntu2),
 bzip2 (= 1.0.6-9),
 coreutils (= 8.28-1ubuntu1),
 cpp (= 4:8.2.0-1ubuntu1),
 cpp-8 (= 8.2.0-7ubuntu1),
 dash (= 0.5.8-2.10),
 debconf (= 1.5.69),
 debhelper (= 11.3.2ubuntu1),
 debianutils (= 4.8.6),
 dh-autoreconf (= 19),
 dh-exec (= 0.23build1),
 dh-strip-nondeterminism (= 0.042-1),
 diffutils (= 1:3.6-1),
 dpkg (= 1.19.0.5ubuntu5),
 dpkg-dev (= 1.19.0.5ubuntu5),
 dwz (= 0.12-2),
 fdisk (= 2.32-0.1ubuntu1),
 file (= 1:5.34-2),
 findutils (= 4.6.0+git+20180808-2),
 g++ (= 4:8.2.0-1ubuntu1),
 g++-8 (= 8.2.0-7ubuntu1),
 gcc (= 4:8.2.0-1ubuntu1),
 gcc-8 (= 8.2.0-7ubuntu1),
 gcc-8-base (= 8.2.0-7ubuntu1),
 gettext (= 0.19.8.1-7),
 gettext-base (= 0.19.8.1-7),
 grep (= 3.1-2ubuntu1),
 groff-base (= 1.22.3-10),
 gzip (= 1.6-5ubuntu1),
 hostname (= 3.20),
 init-system-helpers (= 1.54),
 install-info (= 6.5.0.dfsg.1-4),
 intltool-debian (= 0.35.0+20060710.4),
 libacl1 (= 2.2.52-3build1),
 libarchive-zip-perl (= 1.63-1),
 libasan5 (= 8.2.0-7ubuntu1),
 libatomic1 (= 8.2.0-7ubuntu1),
 libattr1 (= 1:2.4.47-2build1),
 libaudit-common (= 1:2.8.3-1ubuntu2),
 libaudit1 (= 1:2.8.3-1ubuntu2),
 libbinutils (= 2.31.1-6ubuntu1),
 libblkid1 (= 2.32-0.1ubuntu1),
 libbsd0 (= 0.9.1-1),
 libbz2-1.0 (= 1.0.6-9),
 libc-bin (= 2.28-0ubuntu1),
 libc-dev-bin (= 2.28-0ubuntu1),
 libc6 (= 2.28-0ubuntu1),
 libc6-dev (= 2.28-0ubuntu1),
 libcap-ng0 (= 0.7.9-1),
 libcc1-0 (= 8.2.0-7ubuntu1),
 libcroco3 (= 0.6.12-2),
 libdb5.3 (= 5.3.28+dfsg1-0.1),
 libdebconfclient0 (= 0.213ubuntu1),
 libdpkg-perl (= 1.19.0.5ubuntu5),
 libelf1 (= 0.170-0.5),
 libfdisk1 (= 2.32-0.1ubuntu1),
 libffi6 (= 3.2.1-8),
 libfile-stripnondeterminism-perl (= 0.042-1),
 libgcc-8-dev (= 8.2.0-7ubuntu1),
 libgcc1 (= 1:8.2.0-7ubuntu1),
 libgcrypt20 (= 1.8.3-1ubuntu1),
 libgdbm-compat4 (= 1.14.1-6),
 libgdbm5 (= 1.14.1-6),
 libglib2.0-0 (= 2.58.0-4),
 libgmp10 (= 2:6.1.2+dfsg-3),
 libgomp1 (= 8.2.0-7ubuntu1),
 libgpg-error0 (= 1.32-1),
 libicu60 (= 60.2-6ubuntu1),
 libisl19 (= 0.20-2),
 libitm1 (= 8.2.0-7ubuntu1),
 liblsan0 (= 8.2.0-7ubuntu1),
 liblz4-1 (= 1.8.2-1ubuntu1),
 liblzma5 (= 5.2.2-1.3),
 libmagic-mgc (= 1:5.34-2),
 libmagic1 (= 1:5.34-2),
 libmount1 (= 2.32-0.1ubuntu1),
 libmpc3 (= 1.1.0-1),
 libmpfr6 (= 4.0.1-1),
 libmpx2 (= 8.2.0-7ubuntu1),
 libncursesw6 (= 6.1+20180210-4ubuntu1),
 libpa

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[Chris Lamb]

Hi,

> > Sorry, please provide a .dsc; I am very busy, alas...
> 
> Understood...

No, sorry, please provide a HTTP-accessible link to .dsc with all the
sources, etc. Just like a regular sponsor request…


Regards,

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

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[殷啟聰 | Kai-Chung Yan]

> No, sorry, please provide a HTTP-accessible link to .dsc with all the
> sources, etc. Just like a regular sponsor request…

I understand now, sorry I haven't used that procedure for a long time...

Here it is: 
https://mentors.debian.net/package/android-platform-external-boringssl

And the link to the DSC is: 
https://mentors.debian.net/debian/pool/main/a/android-platform-external-boringssl/android-platform-external-boringssl_8.1.0+r23-2.dsc



signature.asc
Description: OpenPGP digital signature

Processed: severity of 886499 is serious

[Debian Bug Tracking System]

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

> severity 886499 serious
Bug #886499 [kodi-pvr-hdhomerun] kodi-pvr-hdhomerun: Incompatible with Kodi 
2:17.1+dfsg1-3 from Stretch
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 884658 is serious

[Debian Bug Tracking System]

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

> severity 884658 serious
Bug #884658 [dkms] dkms: Should really depends on dpkg-dev for dpkg-architecture
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#908294: marked as done (hamlib: FTBFS (Syntax error: "then" unexpected))

[Debian Bug Tracking System]

Your message dated Fri, 21 Sep 2018 10:19:42 +
with message-id 
and subject line Bug#908294: fixed in hamlib 3.2-3
has caused the Debian Bug report #908294,
regarding hamlib: FTBFS (Syntax error: "then" unexpected)
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.)


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

Dear maintainer:

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


[...]

   debian/rules override_dh_auto_install-indep
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
mkdir -p /<>/debian/tmp/usr/share/doc/hamlib
cp -r /<>/build-indep/doc/html \
/<>/debian/tmp/usr/share/doc/hamlib/
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh_install
lts=/<>/debian/lua-hamlib2/usr/share/doc/lua-hamlib2/luatest.lua \
if [ -f "$lts" ]; then \
rm -f $lts; \
fi
/bin/sh: 2: Syntax error: "then" unexpected
make[1]: *** [debian/rules:105: override_dh_install] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:18: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Looking at the code:

override_dh_install:
dh_install
lts=$(CURDIR)/debian/lua-hamlib2/usr/share/doc/lua-hamlib2/luatest.lua \
if [ -f "$$lts" ]; then \
rm -f $$lts; \
fi

it seems there is a missing ";" at the end of lts= line.

However, if you want to remove a file unconditionally no matter what, I wonder
why don't you do this instead:

--- a/debian/rules
+++ b/debian/rules
@@ -102,10 +102,7 @@ override_dh_auto_install-indep:
 
 override_dh_install:
dh_install
-   lts=$(CURDIR)/debian/lua-hamlib2/usr/share/doc/lua-hamlib2/luatest.lua \
-   if [ -f "$$lts" ]; then \
-   rm -f $$lts; \
-   fi
+   rm -f debian/lua-hamlib2/usr/share/doc/lua-hamlib2/luatest.lua
 
 override_dh_auto_clean:
dh_auto_clean


Or maybe it would be even better to use "dh_install -Xexcluded_file" in a 
single line.

Thanks.
--- End Message ---
--- Begin Message ---
Source: hamlib
Source-Version: 3.2-3

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

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

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

Debian distribution maintenance software
pp.
Enrico Rossi  (supplier of updated hamlib 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, 08 Sep 2018 14:35:53 +0200
Source: hamlib
Binary: libhamlib2 libhamlib2++c2 libhamlib-dev libhamlib++-dev libhamlib2-perl 
libhamlib2-tcl python-libhamlib2 python3-libhamlib2 libhamlib-utils 
libhamlib-doc lua-hamlib2
Architecture: source
Version: 3.2-3
Distribution: unstable
Urgency: low
Maintainer: Debian Hamradio Maintainers 
Changed-By: Enrico Rossi 
Description:
 libhamlib++-dev - Development C++ library to control radio transceivers and 
receive
 libhamlib-dev - Development library to control radio transceivers and receivers
 libhamlib-doc - Documentation for the hamlib radio control library
 libhamlib-utils - Utilities to support the hamlib radio control library
 libhamlib2 - Run-time library to control radio transceivers and receivers
 libhamlib2++c2 - Run-time C++ library to control radio transceivers and 
receivers
 libhamlib2-perl - R

Bug#889064: marked as done (automysqlbackup: monthly backup fails with line 427: [: too many arguments)

[Debian Bug Tracking System]

Your message dated Fri, 21 Sep 2018 11:34:24 +
with message-id 
and subject line Bug#889064: fixed in automysqlbackup 2.6+debian.4-2
has caused the Debian Bug report #889064,
regarding automysqlbackup: monthly backup fails with line 427: [: too many 
arguments
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.)


-- 
889064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: automysqlbackup
Version: 2.6+debian.4-1
Severity: important

Dear Maintainer,

Today, first of month, a new installed server has reported an error
trying to backup MariaDB using the package automysqlbackup.

The error is:

/usr/sbin/automysqlbackup: line 427: [: too many arguments

My configuration does not use separate directories. I've googled the
error and found what seems to be a bug reported to Ubuntu.

https://bugs.launchpad.net/ubuntu/+source/automysqlbackup/+bug/1718887

So it seems that some quotes are needed.


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

Kernel: Linux 4.9.0-5-amd64 (SMP w/1 CPU core)
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 automysqlbackup depends on:
ii  bsd-mailx [mailx]   8.1.2-0.20160123cvs-4
ii  mariadb-client-10.1 [virtual-mysql-client]  10.1.26-0+deb9u1

Versions of packages automysqlbackup recommends:
pn  mutt  

automysqlbackup suggests no packages.

-- Configuration Files:
/etc/default/automysqlbackup changed:
DBHOST=localhost
DBNAMES=`mysql --defaults-file=/etc/mysql/debian.cnf --execute="SHOW
DATABASES" | awk '{print $1}' | grep -v ^Database$ | grep -v ^mysql$ | grep
-v ^performance_schema$ | grep -v ^information_schema$ | tr \\\r\\\n ,\ `
BACKUPDIR="/var/lib/automysqlbackup"
MAILCONTENT="quiet"
MAXATTSIZE="4000"
MAILADDR="[redacted]"
MDBNAMES="mysql $DBNAMES"
DBEXCLUDE=""
CREATE_DATABASE=yes
SEPDIR=no
DOWEEKLY=6
COMP=bzip2
COMMCOMP=no
LATEST=no
MAX_ALLOWED_PACKET=
SOCKET=
ROUTINES=yes


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: automysqlbackup
Source-Version: 2.6+debian.4-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated automysqlbackup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 21 Sep 2018 13:13:00 +0200
Source: automysqlbackup
Binary: automysqlbackup
Architecture: source all
Version: 2.6+debian.4-2
Distribution: unstable
Urgency: medium
Maintainer: Thomas Goirand 
Changed-By: Thomas Goirand 
Description:
 automysqlbackup - daily, weekly and monthly backup for your MySQL database
Closes: 889064
Changes:
 automysqlbackup (2.6+debian.4-2) unstable; urgency=medium
 .
   * Fix "monthly backup fails with line 427", thanks to Sergi Baila for
 reporting (Closes: #889064).
Checksums-Sha1:
 e3d1c2b0b2fc7884614a017c989424ba409bc9e4 1960 
automysqlbackup_2.6+debian.4-2.dsc
 518da7d5da18874fa2bd0be0c337ea05f2643e98 6564 
automysqlbackup_2.6+debian.4-2.debian.tar.xz
 cf8199a2cec2053568771b271ab02a3181d9995f 14152 
automysqlbackup_2.6+debian.4-2_all.deb
 e20dc1eadc64640744de3ac19b988aaaea66f4e9 5539 
automysqlbackup_2.6+debian.4-2_amd64.buildinfo
Checksums-Sha256:
 f82b1d486c5de1abfefed81ee2e03803f5a2cc9aceac945114fd70bc102b5e31 1960 
automysqlbackup_2.6+debian.4-2.dsc
 03266eb462b5678dd13b84407cf4aabb66e1fb2436fe43a3d0107a5d9515e4ee 6564 
automysqlbackup_2.6+debian.4-2.debian.tar.xz
 070b3749227bc321897c6107e82feb2f1dd36f7474631f2d5ed122a192c88f38 14152 
automysqlbackup_2.6+debian.4-2_all.deb
 25ea365e4fbc5345af4b3a08760407b899c7882dd2f87f6773687b7d44aaa7ac 5539 
automysqlbackup_2.6+debian.4-2_amd64.buildinfo
Files:
 652bba21c9a29c83496639eeb7be8aa2 1960 admin extra 
automysqlbackup_2.6+debian.4-2.dsc
 73a5b0e0bcc73c6f2c301f4

Processed: tagging 884632

[Debian Bug Tracking System]

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

> tags 884632 + stretch
Bug #884632 [rtv] rtv crashes when viewing submission
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Processed: severity of 884632 is serious

[Debian Bug Tracking System]

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

> severity 884632 serious
Bug #884632 [rtv] rtv crashes when viewing submission
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Cannot reproduce

[Debian Bug Tracking System]

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

> severity 908862 normal
Bug #908862 [src:neutron] neutron: FTBFS (failing tests)
Severity set to 'normal' from 'serious'
> tags 908862 + moreinfo
Bug #908862 [src:neutron] neutron: FTBFS (failing tests)
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#909312: initramfs: The bug is in version 0.132, but I can't boot with that version and kernel 4.16 so I went back to kernel 4.9 and initramfs 0.130. Error tells something like: trying to boot nobo

[Nicola]

Package: initramfs-tools
Version: 0.130
Severity: critical
File: initramfs
Justification: breaks the whole system

Dear Maintainer,

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

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

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


-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 22M Sep 20 15:41 /boot/initrd.img-4.9.0-7-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.9.0-7-amd64 
root=UUID=b79e5351-dad2-4314-81f2-fad299c247e1 ro splash quiet splash

-- resume
RESUME=UUID=d8332b39-17c5-4bc0-82d2-0105153d787a
-- /proc/filesystems
ext3
ext2
ext4
fuseblk
xfs
reiserfs

-- lsmod
Module  Size  Used by
nfsv3  40960  1
nfs_acl16384  1 nfsv3
rpcsec_gss_krb540960  0
auth_rpcgss61440  1 rpcsec_gss_krb5
oid_registry   16384  1 auth_rpcgss
nfsv4 565248  0
dns_resolver   16384  1 nfsv4
nfs   253952  3 nfsv4,nfsv3
lockd  90112  2 nfs,nfsv3
grace  16384  1 lockd
fscache61440  2 nfsv4,nfs
cpufreq_conservative16384  0
cpufreq_powersave  16384  0
cpufreq_userspace  16384  0
reiserfs  233472  1
xfs  1224704  1
libcrc32c  16384  1 xfs
fuse   98304  7
intel_powerclamp   16384  0
joydev 20480  0
evdev  24576  20
videodev  176128  0
media  40960  1 videodev
amdkfd139264  1
radeon   1490944  3
serio_raw  16384  0
ttm98304  1 radeon
drm_kms_helper155648  1 radeon
drm   360448  6 radeon,ttm,drm_kms_helper
i2c_algo_bit   16384  1 radeon
sg 32768  0
shpchp 36864  0
rng_core   16384  0
button 16384  0
acpi_cpufreq   20480  0
abituguru  40960  0
w83627hf   32768  0
snd_hda_codec_realtek90112  1
snd_hda_codec_generic69632  1 snd_hda_codec_realtek
hwmon_vid  16384  1 w83627hf
snd_hda_intel  36864  2
snd_hda_codec 135168  3 
snd_hda_intel,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_core   86016  4 
snd_hda_intel,snd_hda_codec,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hwdep  16384  1 snd_hda_codec
snd_pcm   110592  3 snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer  32768  1 snd_pcm
snd86016  11 
snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_generic,snd_hda_codec_realtek,snd_pcm
soundcore  16384  1 snd
loop   28672  0
firewire_sbp2  24576  0
parport_pc 28672  0
ppdev  20480  0
lp 20480  0
parport49152  3 lp,parport_pc,ppdev
sunrpc344064  11 
auth_rpcgss,rpcsec_gss_krb5,nfsv4,nfs_acl,lockd,nfs,nfsv3
ip_tables  24576  0
x_tables   36864  1 ip_tables
autofs440960  2
ext4  585728  5
crc16  16384  1 ext4
jbd2  106496  1 ext4
crc32c_generic 16384  5
fscrypto   28672  1 ext4
ecb16384  0
glue_helper16384  0
lrw16384  0
gf128mul   16384  1 lrw
ablk_helper16384  0
cryptd 24576  1 ablk_helper
aes_x86_64 20480  1
mbcache16384  6 ext4
memstick   20480  0
sdhci_pci  28672  0
sdhci  45056  1 sdhci_pci
mmc_core  147456  2 sdhci,sdhci_pci
uas24576  0
usb_storage73728  1 uas
hid_microsoft  16384  0
hid_generic16384  0
usbhid 53248  0
hid   122880  3 hid_generic,usbhid,hid_microsoft
sr_mod 24576  0
cdrom  61440  1 sr_mod
sd_mod 49152  13
ata_generic16384  0
ahci   36864  0
libahci32768  1 ahci
ata_piix   36864  13
libata249856  4 ahci,ata_piix,libahci,ata_generic
psmouse   135168  0
i2c_i801   24576  0
i2c_smbus  16384  1 i2c_i801
scsi_mod  225280  7 
firewire_sbp2,sd_mod,usb_storage,libata,uas,sr_mod,sg
e100   36864  0
mii16384  1 e100
floppy 69632  0
firewire_ohci  40960  0
firewire_core  65536  2 firewire_sbp2,firewire_ohci
crc_itu_t  16384  1 firewire_core
e1000 143360  0
thermal20480  0
ehci_pci

Bug#864827: Please go ahead adding explanations to the wiki

[Stefan Monnier]

>> This bug basically makes the package unusable.  
> Unfortunately that's true.
>> I understand that adapting the packaging to the new structure of
>> Zotero-5 will take some time, but in the mean time, could someone add
>> a page to the Debian wiki outlining how to install Zotero-5 by hand on
>> a Debian system
> You are more than welcomed to do so.  Everyone can contribute to the
> Debian wiki.

I know that, but I need to read this wiki page ;-)


Stefan

Processed: Version fix

[Debian Bug Tracking System]

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

> notfound 909312 0.130
Bug #909312 [initramfs-tools] initramfs: The bug is in version 0.132, but I 
can't boot with that version and kernel 4.16 so I went back to kernel 4.9 and 
initramfs 0.130. Error tells something like: trying to boot nobody cared IRQ19 
try irqpoll, but even if I use irqpoll nothing changes. Problem on this libs 
i801_isr , usbcore , libahci. If I disconnect an hard drive sometimes it boot 
but with 3 SATA and 2 DVD in PATA no way, tried many configurations in BIOS 
without solve. 0.130 an kernel 4.9 are working.
No longer marked as found in versions initramfs-tools/0.130.
> found 909312 0.132
Bug #909312 [initramfs-tools] initramfs: The bug is in version 0.132, but I 
can't boot with that version and kernel 4.16 so I went back to kernel 4.9 and 
initramfs 0.130. Error tells something like: trying to boot nobody cared IRQ19 
try irqpoll, but even if I use irqpoll nothing changes. Problem on this libs 
i801_isr , usbcore , libahci. If I disconnect an hard drive sometimes it boot 
but with 3 SATA and 2 DVD in PATA no way, tried many configurations in BIOS 
without solve. 0.130 an kernel 4.9 are working.
Marked as found in versions initramfs-tools/0.132.
> thanks
Stopping processing here.

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

Processed: severity of 884352 is serious

[Debian Bug Tracking System]

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

> severity 884352 serious
Bug #884352 [virtualenvwrapper] virtualenvwrapper: Python interpreter inside 
virtualenv breaks after system python upgrade
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)

[Graham Inggs]

Hi Abou

On 27/08/2018 18:03, Abou Al Montacir wrote:

Maybe we shall think more about this change. Removing the manually flag leads to
a deeper question: Do we need to distribute LCL units in binary form if they
will get recompiled anyway?


Have you had any time to consider this?

Both doublecmd and ddrescueview have been removed from testing now.

Regards
Graham

Processed: severity of 882108 is serious

[Debian Bug Tracking System]

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

> severity 882108 serious
Bug #882108 [xmonad] xmonad is almost entirely nonfunctional
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Move to correct package and adjust severity

[Debian Bug Tracking System]

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

> reassign 878623 python3-acoustid 1.1.2-2
Bug #878623 [python-acoustid] python-acoustid: acoustid.fingerprint_file(p) 
fails with TypeError: data must be bytes, buffer, or memoryview
Bug reassigned from package 'python-acoustid' to 'python3-acoustid'.
No longer marked as found in versions pyacoustid/1.1.2-2.
Ignoring request to alter fixed versions of bug #878623 to the same values 
previously set
Bug #878623 [python3-acoustid] python-acoustid: acoustid.fingerprint_file(p) 
fails with TypeError: data must be bytes, buffer, or memoryview
Marked as found in versions pyacoustid/1.1.2-2.
> severity 878623 serious
Bug #878623 [python3-acoustid] python-acoustid: acoustid.fingerprint_file(p) 
fails with TypeError: data must be bytes, buffer, or memoryview
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: Sorry, I mixed up bug numbers

[Debian Bug Tracking System]

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

> reassign 878623 python-acoustid 1.1.2-2
Bug #878623 [python3-acoustid] python-acoustid: acoustid.fingerprint_file(p) 
fails with TypeError: data must be bytes, buffer, or memoryview
Bug reassigned from package 'python3-acoustid' to 'python-acoustid'.
No longer marked as found in versions pyacoustid/1.1.2-2.
Ignoring request to alter fixed versions of bug #878623 to the same values 
previously set
Bug #878623 [python-acoustid] python-acoustid: acoustid.fingerprint_file(p) 
fails with TypeError: data must be bytes, buffer, or memoryview
Marked as found in versions pyacoustid/1.1.2-2.
> severity 878623 normal
Bug #878623 [python-acoustid] python-acoustid: acoustid.fingerprint_file(p) 
fails with TypeError: data must be bytes, buffer, or memoryview
Severity set to 'normal' from 'serious'
> reassign 881565 python3-acoustid 1.1.2-2
Bug #881565 [python-acoustid] python-acoustid: incompatible with python3 (fix 
availble upstream)
Bug #881566 [python-acoustid] python-acoustid: incompatible/broken on Python 3 
(fix available upstream)
Bug reassigned from package 'python-acoustid' to 'python3-acoustid'.
Bug reassigned from package 'python-acoustid' to 'python3-acoustid'.
No longer marked as found in versions pyacoustid/1.1.2-2.
No longer marked as found in versions pyacoustid/1.1.2-2.
Ignoring request to alter fixed versions of bug #881565 to the same values 
previously set
Ignoring request to alter fixed versions of bug #881566 to the same values 
previously set
Bug #881565 [python3-acoustid] python-acoustid: incompatible with python3 (fix 
availble upstream)
Bug #881566 [python3-acoustid] python-acoustid: incompatible/broken on Python 3 
(fix available upstream)
Marked as found in versions pyacoustid/1.1.2-2.
Marked as found in versions pyacoustid/1.1.2-2.
> severity 881565 serious
Bug #881565 [python3-acoustid] python-acoustid: incompatible with python3 (fix 
availble upstream)
Bug #881566 [python3-acoustid] python-acoustid: incompatible/broken on Python 3 
(fix available upstream)
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 909313 is serious

[Debian Bug Tracking System]

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

> severity 909313 serious
Bug #909313 [xul-ext-sogo-connector] [xul-ext-sogo-connector] Not compatible 
with thunderbird 60 (New version exists)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#906472: How should sparse depend on gcc?

[Uwe Kleine-König]

Hello,

sparse is a C code checker that reuses include files from gcc. Currently
there are missing the needed dependencies
(https://bugs.debian.org/906472).

Now I wonder, what is the right way to depend on gcc. For sparse it
would be enough to depend on libgcc-8-dev (I think), but as cgcc (which
is included in the sparse package) calls gcc, too, I need a dependency
on the gcc package directly (which via gcc-8 depends on libgcc-8-dev).

As gcc-7 doesn't provide the needed paths, gcc 4:7.whatever isn't enough
though.

I can imagine the following options to depend on:

a) gcc, libgcc-8-dev
b) gcc (>= 4:8~), gcc (<< 4:9)

. Both have the disadvantage that they need manual adaption when gcc
bumps it's major version.

a) also has the disadvantage that gcc might provide gcc-9 and so sparse
uses different includes than the default compiler (not sure this is bad
enough to care).

b) is bad, because gcc_4:9~prerelease12 would be good enough to make
dpkg happy, but sparse would fail anyhow.

Alternatively sparse could stop hardcoding the include path and ask gcc
on each invokation. But I don't like that much as the path hardly ever
changes and it adds some overhead to sparse.

Do you have any thoughts/recommendations?

Best regards
Uwe


signature.asc
Description: PGP signature

Processed: severity of 880393 is serious

[Debian Bug Tracking System]

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

> severity 880393 serious
Bug #880393 [libsasl2-modules-gssapi-heimdal] libsasl2-modules-gssapi-heimdal 
seems built against MIT
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 880093 is serious

[Debian Bug Tracking System]

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

> severity 880093 serious
Bug #880093 [pyotherside] pyotherside 1.2 cannot convert QVariant to QJSValue 
with qt5.7
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#899961: marked as done (fcitx-table-extra: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 21 Sep 2018 14:42:22 +
with message-id 
and subject line Bug#899961: fixed in fcitx-table-extra 0.3.8-2
has caused the Debian Bug report #899961,
regarding fcitx-table-extra: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fcitx-table-extra
Version: 0.3.8-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of fcitx-table-extra,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: fcitx-table-extra
Source-Version: 0.3.8-2

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated fcitx-table-extra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 20 Sep 2018 15:29:43 -0400
Source: fcitx-table-extra
Binary: fcitx-table-array30 fcitx-table-array30-big fcitx-table-boshiamy 
fcitx-table-cangjie-big fcitx-table-cangjie3 fcitx-table-cangjie5 
fcitx-table-cantonese fcitx-table-cantonhk fcitx-table-easy-big 
fcitx-table-jyutping fcitx-table-quick-classic fcitx-table-quick3 
fcitx-table-quick5 fcitx-table-scj6 fcitx-table-stroke5 fcitx-table-t9 
fcitx-table-wu fcitx-table-wubi-large fcitx-table-zhengma 
fcitx-table-zhengma-large
Architecture: source
Version: 0.3.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 fcitx-table-array30 - Flexible Input Method Framework - Array30 table
 fcitx-table-array30-big - Flexible Input Method Framework - Array30-Big table
 fcitx-table-boshiamy - Flexible Input Method Framework - Boshiamy table
 fcitx-table-cangjie-big - Flexible Input Method Framework - Cangjie-Big table
 fcitx-table-cangjie3 - Flexible Input Method Framework - Cangjie3 table
 fcitx-table-cangjie5 - Flexible Input Method Framework - Cangjie5 table
 fcitx-table-cantonese - Flexible Input Method Framework - Cantonese table
 fcitx-table-cantonhk - Flexible Input Meth

Processed: severity of 879756 is serious

[Debian Bug Tracking System]

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

> severity 879756 serious
Bug #879756 [marble-maps] marble-maps: does not start
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#909317: texlive-bin: buffer overflow (DSA-4299-1)

[Salvatore Bonaccorso]

Source: texlive-bin
Version: 2016.20160513.41080.dfsg-2
Severity: grave
Tags: patch security upstream fixed-upstream
Control: fixed -1 2016.20160513.41080.dfsg-2+deb9u1
Control: fixed -1 2018.20180907.48586-2

Filling for tracking of the issue fixed in DSA-4299-1, CVE assignment
is pending.

Nick Roessler from the University of Pennsylvania has found a buffer overflow
in texlive-bin, the executables for TexLive, the popular distribution of TeX
document production system.

This buffer overflow can be used for arbitrary code execution by crafting a
special type1 font (.pfb) and provide it to users running pdf(la)tex, dvips or
luatex in a way that the font is loaded.

https://lists.debian.org/debian-security-announce/2018/msg00230.html

Regards,
Salvatore

Bug#907008: marked as done (mod-gnutls FTBFS: FAIL: test-16_view-status.bash)

[Debian Bug Tracking System]

Your message dated Fri, 21 Sep 2018 14:49:49 +
with message-id 
and subject line Bug#907008: fixed in mod-gnutls 0.8.4-2
has caused the Debian Bug report #907008,
regarding mod-gnutls FTBFS: FAIL: test-16_view-status.bash
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.)


-- 
907008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mod-gnutls
Version: 0.8.4-1
Severity: serious
Tags: ftbfs

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

...
FAIL: test-16_view-status.bash
...
===
test/logs/16_view-status.error.log
[Wed Aug 22 10:57:04.566902 2018] [gnutls:debug] [pid 51559:tid 
140369585579072] gnutls_hooks.c(532): set_default_dh_param: Setting DH params 
for security level 'Medium'.
[Wed Aug 22 10:57:04.567788 2018] [gnutls:debug] [pid 51559:tid 
140369585579072] gnutls_hooks.c(532): set_default_dh_param: Setting DH params 
for security level 'High'.
[Wed Aug 22 10:57:04.613420 2018] [gnutls:debug] [pid 51573:tid 
140369585579072] gnutls_hooks.c(532): set_default_dh_param: Setting DH params 
for security level 'Medium'.
[Wed Aug 22 10:57:04.614289 2018] [gnutls:debug] [pid 51573:tid 
140369585579072] gnutls_hooks.c(532): set_default_dh_param: Setting DH params 
for security level 'High'.
[Wed Aug 22 10:57:04.614349 2018] [watchdog:debug] [pid 51573:tid 
140369585579072] mod_watchdog.c(454): AH010033: Watchdog: Running with 
WatchdogInterval 1000ms
[Wed Aug 22 10:57:04.614357 2018] [watchdog:debug] [pid 51573:tid 
140369585579072] mod_watchdog.c(462): AH02974: Watchdog: found parent providers.
[Wed Aug 22 10:57:04.614362 2018] [watchdog:debug] [pid 51573:tid 
140369585579072] mod_watchdog.c(508): AH02977: Watchdog: found child providers.
[Wed Aug 22 10:57:04.614366 2018] [watchdog:debug] [pid 51573:tid 
140369585579072] mod_watchdog.c(516): AH02978: Watchdog: Looking for child 
(_singleton_).
[Wed Aug 22 10:57:04.614370 2018] [watchdog:debug] [pid 51573:tid 
140369585579072] mod_watchdog.c(516): AH02978: Watchdog: Looking for child 
(_default_).
[Wed Aug 22 10:57:04.617438 2018] [mpm_worker:notice] [pid 51573:tid 
140369585579072] AH00292: Apache/2.4.34 (Debian) mod_gnutls/0.8.4 GnuTLS/3.5.19 
configured -- resuming normal operations
[Wed Aug 22 10:57:04.617471 2018] [mpm_worker:info] [pid 51573:tid 
140369585579072] AH00293: Server built: 2018-07-27T19:37:37
[Wed Aug 22 10:57:04.617487 2018] [core:notice] [pid 51573:tid 140369585579072] 
AH00094: Command line: '/usr/sbin/apache2 -f 
/build/1st/mod-gnutls-0.8.4/test/tests/16_view-status/apache.conf'
[Wed Aug 22 10:57:04.617495 2018] [core:debug] [pid 51573:tid 140369585579072] 
log.c(1571): AH02639: Using SO_REUSEPORT: yes (1)
[Wed Aug 22 10:57:04.617531 2018] [mpm_worker:debug] [pid 51573:tid 
140369585579072] worker.c(1728): AH00294: Accept mutex: sysvsem (default: 
sysvsem)
[Wed Aug 22 10:57:04.617976 2018] [watchdog:debug] [pid 51575:tid 
140369585579072] mod_watchdog.c(565): AH02980: Watchdog: nothing configured?
[Wed Aug 22 10:57:04.626623 2018] [watchdog:debug] [pid 51576:tid 
140369585579072] mod_watchdog.c(565): AH02980: Watchdog: nothing configured?
[Wed Aug 22 10:57:04.626625 2018] [watchdog:debug] [pid 51577:tid 
140369585579072] mod_watchdog.c(565): AH02980: Watchdog: nothing configured?
[Wed Aug 22 10:57:04.659114 2018] [gnutls:info] [pid 51575:tid 140369245165312] 
[client ::1:55042] GnuTLS: Handshake Failed (-21) 'Could not negotiate a 
supported cipher suite.'
[Wed Aug 22 10:57:04.659259 2018] [gnutls:debug] [pid 51575:tid 
140369245165312] gnutls_io.c(571): [client ::1:55042] mgs_filter_input : 
ap_get_brigade
[Wed Aug 22 10:57:04.659287 2018] [gnutls:debug] [pid 51575:tid 
140369245165312] gnutls_io.c(571): [client ::1:55042] mgs_filter_input : 
ap_get_brigade
[Wed Aug 22 10:57:04.666300 2018] [gnutls:debug] [pid 51575:tid 
140369245165312] gnutls_io.c(571): [client ::1:55042] mgs_filter_input : 
ap_get_brigade
[Wed Aug 22 10:57:04.878313 2018] [core:info] [pid 51573:tid 140369585579072] 
AH00096: removed PID file /build/1st/mod-gnutls-0.8.4/test/apache2.pid 
(pid=51573)
[Wed Aug 22 10:57:04.878343 2018] [mpm_worker:notice] [pid 51573:tid 
140369585579072] AH00295: caught SIGTERM, shutting down
===
...


The start of the FTBFS would match when gnutls 3.5.19-1
entered unstable, this might be related to the cipher changes:
https://lists.gnupg.org/pipermail/gnutls-devel/2018-July/008583.html
--- End Message ---
--- Begin Message ---
Source: mod-gnutls
Source-Version: 0.8.4-2

We believe that the bug you reported is fi

Processed: texlive-bin: buffer overflow (DSA-4299-1)

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2016.20160513.41080.dfsg-2+deb9u1
Bug #909317 [src:texlive-bin] texlive-bin: buffer overflow (DSA-4299-1)
Marked as fixed in versions texlive-bin/2016.20160513.41080.dfsg-2+deb9u1.
> fixed -1 2018.20180907.48586-2
Bug #909317 [src:texlive-bin] texlive-bin: buffer overflow (DSA-4299-1)
Marked as fixed in versions texlive-bin/2018.20180907.48586-2.

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

Processed: closing 909317

[Debian Bug Tracking System]

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

> close 909317 2018.20180907.48586-2
Bug #909317 [src:texlive-bin] texlive-bin: buffer overflow (DSA-4299-1)
Ignoring request to alter fixed versions of bug #909317 to the same values 
previously set
Bug #909317 [src:texlive-bin] texlive-bin: buffer overflow (DSA-4299-1)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[Chris Lamb]

tags 905820 + pending
thanks

Hi Kai,

> https://mentors.debian.net/debian/pool/main/a/android-platform-external-boringssl/android-platform-external-boringssl_8.1.0+r23-2.dsc

Uploaded; thanks! Please address the Lintian errors on the next upload,
mind you...


Regards,

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

Processed: Re: android-platform-external-boringssl: Incomplete debian/copyright?

[Debian Bug Tracking System]

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

> tags 905820 + pending
Bug #905820 [src:android-platform-external-boringssl] 
android-platform-external-boringssl: Incomplete debian/copyright?
Warning: Unknown package 'src:android-platform-external-boringssl'
Added tag(s) pending.
Warning: Unknown package 'src:android-platform-external-boringssl'
> thanks
Stopping processing here.

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

Bug#905820: marked as done (android-platform-external-boringssl: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Fri, 21 Sep 2018 15:19:24 +
with message-id 
and subject line Bug#905820: fixed in android-platform-external-boringssl 
8.1.0+r23-2
has caused the Debian Bug report #905820,
regarding android-platform-external-boringssl: 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.)


-- 
905820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-external-boringssl
Version: 8.1.0+r23-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Kai-Chung Yan , 
ftpmas...@debian.org

Hi,

I just ACCEPTed android-platform-external-boringssl from NEW but 
noticed it was missing attribution in debian/copyright for at least 
Sun Microsystems, Nokia, Network Resonance, etc. etc.

This is in no way 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: android-platform-external-boringssl
Source-Version: 8.1.0+r23-2

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

Debian distribution maintenance software
pp.
Kai-Chung Yan  (supplier of updated 
android-platform-external-boringssl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 21 Sep 2018 16:43:18 +0800
Source: android-platform-external-boringssl
Binary: android-libboringssl android-libboringssl-dev
Architecture: source amd64
Version: 8.1.0+r23-2
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Kai-Chung Yan 
Description:
 android-libboringssl - Google's internal fork of OpenSSL for the Android SDK
 android-libboringssl-dev - Google's internal fork of OpenSSL for the Android 
SDK - devel
Closes: 905820
Changes:
 android-platform-external-boringssl (8.1.0+r23-2) unstable; urgency=medium
 .
   * Update d/copyright:
 * Cover all copyright holders (Closes: #905820)
 * Point the Source to AOSP
   * Standards-Version => 4.2.1
Checksums-Sha1:
 3a0721dc83d5cbf40d16074f2fe30912a5f58247 2442 
android-platform-external-boringssl_8.1.0+r23-2.dsc
 97fae12ac5fbec3282eb17f5d00543e14c094811 20346200 
android-platform-external-boringssl_8.1.0+r23.orig.tar.gz
 10393ba6868a536c9a1d9a0953db8f1e901dc156 7668 
android-platform-external-boringssl_8.1.0+r23-2.debian.tar.xz
 c6b4c52b66f376040da4b67c2a75dcf6df3d991e 2456544 
android-libboringssl-dbgsym_8.1.0+r23-2_amd64.deb
 5fbc01226e4db10a779e719921584ee9c4f4008b 181732 
android-libboringssl-dev_8.1.0+r23-2_amd64.deb
 76b2bd397ca99cf3759bc0a9f2de7557bbc11c47 540916 
android-libboringssl_8.1.0+r23-2_amd64.deb
 31ec67d734ac5e77bdde33e009ccf0b9472ecc9b 6171 
android-platform-external-boringssl_8.1.0+r23-2_amd64.buildinfo
Checksums-Sha256:
 ca87712968ac64ad6ddca32776df2c1c77a37ae9303ee6f63cef0f7e1a324123 2442 
android-platform-external-boringssl_8.1.0+r23-2.dsc
 51eb22c5f68ce49e35a1726623a257e8e89b29c23bf374a3420a8ac88afe2078 20346200 
android-platform-external-boringssl_8.1.0+r23.orig.tar.gz
 84873533e9be896bb1e252722edb91471fe71e7e018222d9e7669262fda57ec5 7668 
android-platform-external-boringssl_8.1.0+r23-2.debian.tar.xz
 057010e02dd78fe12ea221144581a98226aecc56874d842479db34f3f3cd6067 2456544 
android-libboringssl-dbgsym_8.1.0+r23-2_amd64.deb
 db185f57a572b801f7208a450b4722873098a7b24e736e532161723f66582e19 181732 
android-libboringssl-dev_8.1.0+r23-2_amd64.deb
 7c54506ffa95e465f1abf7083bcb193c0b4f4de752fb28fa72eaf958052cfb62 540916 
android-libboringssl_8.1.0+r23-2_amd64.deb
 9377ad7af987fd66be1e79de61ee3256ac6c763fe5898aa3db9c367a88d75d9e 6171 
android-platform-external-boringssl_8.1.0+r23-2_amd64.buildinfo
Files:
 2e4bede34e994174448aade381609979 2442 libs optional 
android-platform-external-boringssl_8.1.0+r23-2.dsc
 cdc934e3446620108599fa3870c4c103 20346200 libs optional 
android-platform-external-boringssl_8.1.0+r23.orig.tar.gz
 6f

Bug#909313: [xul-ext-sogo-connector] Not compatible with thunderbird 60 (New version exists)

[Carsten Schoenert]

Please use Reply-All to update the BTS as well.

Am 21.09.18 um 17:34 schrieb Michael Meier:
...
> I've just tested out the nightly build, and it seems to be working. I've 
> created some events, tried to sync them in both ways, delete them.
> 
> So at least basic functionality seems to be working. The rest time will 
> show...
> 
> The new version is not compatibly to thunderbird version <60.

Thanks, unfortunately this package has some low priority at the moment
on my side.

-- 
Regards
Carsten Schoenert

Bug#909313: [xul-ext-sogo-connector] Not compatible with thunderbird 60 (New version exists)

[Michael Meier]

ups, I didn't reply to the list...

On 9/21/18 9:21 AM, Carsten Schoenert


Hello Michael,

Am 21.09.18 um 15:29 schrieb Michael Meier:

The version 31.0.5-2 is not compatible with thunderbird 60.
But it seems there exists already a new sogo-connector version which is
compatible. Please update.

have you tested this?

Updating to 31.0.6 is not that easy as simply importing the updated 
version.

First we need to be able to build every thing from source due the DFSG
and secondly the packaging need to be moved over to the packaging format
of webextension packages.

Before doing all this we need to be sure that the new version of
sogo-connector is really working with TB >= 60.x.

I've just tested out the nightly build, and it seems to be working. I've 
created some events, tried to sync them in both ways, delete them.


So at least basic functionality seems to be working. The rest time will 
show...


The new version is not compatibly to thunderbird version <60.

Bug#907491: closed by Paul Gevers (Re: goobook fails to authenticate)

[Ilias Tsitsimpis]

Hi Sergio,

On Sat, Sep 15, 2018 at 11:28AM, Sergio Mendoza wrote:
> Hi again,
> 
>   Today after an upgrade once again the problem appears:

Do you know which package you updated that broke goobook?

> sergio@izta:~$ goobook query sergio
> Traceback (most recent call last):
>   File "/usr/bin/goobook", line 11, in 
> load_entry_point('goobook==1.9', 'console_scripts', 'goobook')()
>   File "/usr/share/goobook/goobook/application.py", line 94, in main
> args.func(config, args)
>   File "/usr/share/goobook/goobook/application.py", line 125, in do_query
> goobk = GooBook(config)
>   File "/usr/share/goobook/goobook/goobook.py", line 59, in __init__
> self.cache.load()
>   File "/usr/share/goobook/goobook/goobook.py", line 257, in load
> self.update()
>   File "/usr/share/goobook/goobook/goobook.py", line 264, in update
> self.contacts = list(self._parse_contacts(gc.fetch_contacts()))
>   File "/usr/share/goobook/goobook/goobook.py", line 395, in fetch_contacts
> res = self._get(query)
>   File "/usr/share/goobook/goobook/goobook.py", line 371, in _get
> connection_type=httplib2.HTTPSConnectionWithTimeout)
>   File "/usr/local/lib/python2.7/dist-packages/oauth2client/client.py", line 
> 562, in new_request
> redirections, connection_type)
>   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 
> 1608, in request
> (response, content) = self._request(conn, authority, uri, request_uri, 
> method, body, headers, redirections, cachekey)
>   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 
> 1350, in _request
> (response, content) = self._conn_request(conn, request_uri, method, body, 
> headers)
>   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 
> 1272, in _conn_request
> conn.connect()
>   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 
> 1059, in connect
> raise SSLHandshakeError(e)
> httplib2.SSLHandshakeError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate 
> verify failed (_ssl.c:726)

The above traceback mentions 
"/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py".
This is not the canonical location where Debian Python packages get
installed. I believe you have installed a different version of the
httplib2 module using pip. Could you please test using the Python module
provided by the python-httplib2 package?

Cheers,

-- 
Ilias

Processed: severity of 879007 is serious

[Debian Bug Tracking System]

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

> severity 879007 serious
Bug #879007 [cyrus-imapd] cyrus-imapd does not accept new connections
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 877162 is serious

[Debian Bug Tracking System]

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

> severity 877162 serious
Bug #877162 [fontconfig-config] fontconfig-config: Configuration fails on 
upgrade from <2.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#909120: camitk FTBFS: tests segfault (Bug #909120)

[Emmanuel Promayon]

Dear Bernhard,

Thank you for your investigation and your time. You are right about 
these double delete and this will have to be fixed.


But I am still puzzled:
1) your patch is absolutely required for handling delete properly (btw 
thanks for the corresponding references!) but unfortunately it can fix 
only some of the tests
2) this bug only appeared recently, no segfault were detected before on 
sid (first trace I found of a failure is in our weekly packaging test 
last Sunday 15 September, everything was fine on Sunday 9 September)

3) the segfaults are generated during testing

This probably means that the problem comes from a deeper (darker, harder 
to find) side of the build.


So I started with the first test on the list that generates a segfaults 
(test #27 named action-editframes-level1-1) and run it through the 
debugger (I run it through the same xvfb-run command line as in the 
debian/control file).


Here is the first outcome:

xvfb-run --auto-servernum --server-args="-screen 0 1024x768x24" 
/usr/bin/gdb 
/root/packaging/camitk-debian-ci/camitk-build/bin/camitk-testactions

GNU gdb (Debian 8.1-4+b1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/root/packaging/camitk-debian-ci/camitk-build/bin/camitk-testactions...done.
(gdb) r "-i" 
"/root/packaging/camitk-debian-ci/camitk-build/share/camitk-4.2/testdata/brain.mha" 
"-a" 
"/root/packaging/camitk-debian-ci/camitk-build/lib/camitk-4.2/actions/libeditframes.so"
Starting program: 
/root/packaging/camitk-debian-ci/camitk-build/bin/camitk-testactions 
"-i" 
"/root/packaging/camitk-debian-ci/camitk-build/share/camitk-4.2/testdata/brain.mha" 
"-a" 
"/root/packaging/camitk-debian-ci/camitk-build/lib/camitk-4.2/actions/libeditframes.so"

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
camitk-testactions run with arguments:
- action library file: 
"/root/packaging/camitk-debian-ci/camitk-build/lib/camitk-4.2/actions/libeditframes.so"
- input test file: 
"/root/packaging/camitk-debian-ci/camitk-build/share/camitk-4.2/testdata/brain.mha"

Working directory: /root/packaging/camitk-debian-ci/camitk-build
Starting the camitk default application...
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[New Thread 0x7fffec879700 (LWP 8505)]
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[New Thread 0x7fffe7f46700 (LWP 8507)]
[OK]
Opening component: 
/root/packaging/camitk-debian-ci/camitk-build/share/camitk-4.2/testdata/brain.mha...

[New Thread 0x7fffda562700 (LWP 8514)]
[New Thread 0x7fffd9d61700 (LWP 8515)]
[New Thread 0x7fffd9560700 (LWP 8516)]
[Thread 0x7fffda562700 (LWP 8514) exited]
[New Thread 0x7fffd8d5f700 (LWP 8517)]
[Thread 0x7fffd9d61700 (LWP 8515) exited]
[New Thread 0x7fffd3fff700 (LWP 8518)]
[New Thread 0x7fffd37fe700 (LWP 8519)]
[New Thread 0x7fffd2ffd700 (LWP 8520)]
[Thread 0x7fffd9560700 (LWP 8516) exited]
[Thread 0x7fffd8d5f700 (LWP 8517) exited]
[Thread 0x7fffd3fff700 (LWP 8518) exited]
[Thread 0x7fffd2ffd700 (LWP 8520) exited]
[Thread 0x7fffd37fe700 (LWP 8519) exited]
[New Thread 0x7fffd2ffd700 (LWP 8521)]
[New Thread 0x7fffd37fe700 (LWP 8522)]
[New Thread 0x7fffd3fff700 (LWP 8523)]
[New Thread 0x7fffd8d5f700 (LWP 8524)]
[New Thread 0x7fffd25c4700 (LWP 8525)]
[New Thread 0x7fffd1dc3700 (LWP 8526)]
[New Thread 0x7fffd15c2700 (LWP 8527)]
[New Thread 0x7fffd0dc1700 (LWP 8528)]

Thread 1 "camitk-testacti" received signal SIGSEGV, Segmentation fault.
0x75718f15 in vtkTextProperty::ShallowCopy(vtkTextProperty*) () 
from /lib/x86_64-linux-gnu/libvtkRenderingCore-6.3.so.6.3

(gdb) where
#0  0x75718f15 in vtkTextProperty::ShallowCopy(vtkTextProperty*) 
() from /lib/x86_64-linux-gnu/libvtkRenderingCore-6.3.so.6.3
#1  0x77f457d7 in 
camitk::RendererWidget::RendererWidget(QWidget*, 
camitk::RendererWidget::ControlMode) () at 
/usr/include/vtk-6.3/vtkSmartPointer.h:77
#2  0x77f31d42 in 
camitk::InteractiveViewer::InteractiveViewer(QString&, 
camitk::InteractiveViewer::ViewerType) ()

    at ./sdk/libraries/core/viewer/InteractiveViewer.cpp:192
#3  0x77f33533 in 
camitk::InteractiveViewer::getNewViewer(QString, 
camitk::InteractiveViewer::ViewerType) ()

    at ./sdk/libraries/core/viewer/InteractiveViewer.cpp:90
#4  0x77f3

Bug#893647: time to go

[Adam Borowski]

Control: clone -1 -2
Control: reassign -2 ftp.debian.org
Control: severity -2 normal
Control: retitle -2 RM: kterm -- RoQA, obsolete, alternatives exist, dead 
upstream

> I believe that kterm is no longer suitable for inclusion in Debian, and thus
> propose its removal.  It lacks features considered basic for a terminal
> emulator, such as UTF-8 support; its compatibility with terminal abilities
> taken for granted these days is poor, and it has been dead upstream since
> times immemorial (predating the first Debian version in 1996).

Reassigning for RM -- goodbye kterm!

-- 
⢀⣴⠾⠻⢶⣦⠀ What Would Jesus Do, MUD/MMORPG edition:
⣾⠁⢰⠒⠀⣿⡁ • multiplay with an admin char to benefit your mortal [Mt3:16-17]
⢿⡄⠘⠷⠚⠋⠀ • abuse item cloning bugs [Mt14:17-20, Mt15:34-37]
⠈⠳⣄ • use glitches to walk on water [Mt14:25-26]

Processed: severity of 908166 is serious

[Debian Bug Tracking System]

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

> severity 908166 serious
Bug #908166 [src:swt4-gtk] swt4-gtk: compilation with openjdk-10 results in 
empty jar
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: time to go

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #893647 [kterm] kterm: should this package be removed?
Bug 893647 cloned as bug 909322
> reassign -2 ftp.debian.org
Bug #909322 [kterm] kterm: should this package be removed?
Bug reassigned from package 'kterm' to 'ftp.debian.org'.
No longer marked as found in versions kterm/6.2.0-46.2.
Ignoring request to alter fixed versions of bug #909322 to the same values 
previously set
> severity -2 normal
Bug #909322 [ftp.debian.org] kterm: should this package be removed?
Severity set to 'normal' from 'serious'
> retitle -2 RM: kterm -- RoQA, obsolete, alternatives exist, dead upstream
Bug #909322 [ftp.debian.org] kterm: should this package be removed?
Changed Bug title to 'RM: kterm -- RoQA, obsolete, alternatives exist, dead 
upstream' from 'kterm: should this package be removed?'.

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

Processed: severity of 907807 is serious

[Debian Bug Tracking System]

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

> severity 907807 serious
Bug #907807 [python-requests] After upgrading to OpenSSL 1.1.1, many sites are 
unreachable
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 907788 is serious

[Debian Bug Tracking System]

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

> severity 907788 serious
Bug #907788 [curl] "dh key too small" since openssl upgrade
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#860064: 860064 fixed in 2.72-3+deb8u3

[Santiago Ruano Rincón]

Control: fixed -1 2.72-3+deb8u3

The bug doesn't occur in stretch. I think it can be tagged as notfound.


signature.asc
Description: PGP signature

Processed: severity of 907255 is serious

[Debian Bug Tracking System]

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

> severity 907255 serious
Bug #907255 [oz] Missing dependencies (python-monotonic and python-requests)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: 860064 fixed in 2.72-3+deb8u3

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.72-3+deb8u3
Bug #860064 {Done: Simon Kelley } [dnsmasq] [dnsmasq] 
startup failue when dns-root-data installed
Bug #863896 {Done: Simon Kelley } [dnsmasq] dnsmasq: 
systemd appends junk to the dnsmasq commandline
There is no source info for the package 'dnsmasq' at version '2.72-3+deb8u3' 
with architecture ''
Unable to make a source version for version '2.72-3+deb8u3'
Marked as fixed in versions 2.72-3+deb8u3.
Marked as fixed in versions 2.72-3+deb8u3.

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

Bug#909327: unattended-upgrades FTBFS: test failures

[Adrian Bunk]

Source: unattended-upgrades
Version: 1.5
Severity: serious
Tags: ftbfs

Some recent change in unstable makes unattended-upgrades FTBFS:

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

...
==
FAIL: test_remove_unused_dependencies (__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 111, in test_remove_unused_dependencies
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'Packages that were 
successfully auto-removed: old-unused-dependency test-package-dependency' in 
'2018-09-20 20:38:43,234 INFO Initial blacklisted packages: 
2018-09-20 20:38:43,235 INFO Initial whitelisted packages: 
2018-09-20 20:38:43,235 INFO Starting unattended upgrades script
2018-09-20 20:38:43,236 INFO Allowed origins are: o=Ubuntu,a=lucid-security
2018-09-20 20:38:43,464 DEBUG APT::VersionedKernelPackages is not set
2018-09-20 20:38:43,466 DEBUG Checking: test-package ([])
2018-09-20 20:38:43,470 DEBUG pkgs that look like they should be upgraded: 
test-package
2018-09-20 20:38:43,478 DEBUG fetch.run() result: 0
2018-09-20 20:38:43,479 DEBUG http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' ID:0 
ErrorText: ''>
2018-09-20 20:38:43,480 DEBUG 
check_conffile_prompt(/build/1st/unattended-upgrades-1.5/test/root.unused-deps/var/cache/apt/archives/test-package_2.0_all.deb)
2018-09-20 20:38:43,481 DEBUG found pkg: test-package
2018-09-20 20:38:43,481 DEBUG blacklist: []
2018-09-20 20:38:43,481 DEBUG whitelist: []
2018-09-20 20:38:43,481 INFO Packages that will be upgraded: test-package
2018-09-20 20:38:43,482 INFO Writing dpkg log to 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2018-09-20 20:38:43,490 DEBUG applying set ['test-package']
2018-09-20 20:38:43,951 DEBUG left to upgrade set()
2018-09-20 20:38:43,951 INFO All upgrades installed
2018-09-20 20:38:43,960 DEBUG InstCount=1 DelCount=0 BrokenCount=0
2018-09-20 20:38:43,968 DEBUG Extracting content from 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log 
since 2018-09-20 20:38:43
'

==
FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 138, in 
test_remove_unused_dependencies_new_unused_only
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'Packages that were 
successfully auto-removed: test-package-dependency' in '2018-09-20 20:38:43,984 
INFO Initial blacklisted packages: 
2018-09-20 20:38:43,985 INFO Initial whitelisted packages: 
2018-09-20 20:38:43,985 INFO Starting unattended upgrades script
2018-09-20 20:38:43,985 INFO Allowed origins are: o=Ubuntu,a=lucid-security
2018-09-20 20:38:44,278 DEBUG Using (^linux-image|^.*-modules|^linux-headers) 
regexp to find kernel packages
2018-09-20 20:38:44,284 DEBUG Using 
(^linux-image.*4.9.0-8-amd64|4.9.0-8-amd64.*-modules|^linux-headers.*4.9.0-8-amd64)
 regexp to find running kernel packages
2018-09-20 20:38:44,286 DEBUG Checking: test-package ([])
2018-09-20 20:38:44,288 DEBUG pkgs that look like they should be upgraded: 
test-package
2018-09-20 20:38:44,298 DEBUG fetch.run() result: 0
2018-09-20 20:38:44,299 DEBUG http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' ID:0 
ErrorText: ''>
2018-09-20 20:38:44,299 DEBUG 
check_conffile_prompt(/build/1st/unattended-upgrades-1.5/test/root.unused-deps/var/cache/apt/archives/test-package_2.0_all.deb)
2018-09-20 20:38:44,299 DEBUG found pkg: test-package
2018-09-20 20:38:44,300 DEBUG blacklist: []
2018-09-20 20:38:44,300 DEBUG whitelist: []
2018-09-20 20:38:44,301 INFO Packages that will be upgraded: test-package
2018-09-20 20:38:44,301 INFO Writing dpkg log to 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2018-09-20 20:38:44,312 DEBUG applying set ['test-package']
2018-09-20 20:38:44,318 DEBUG InstCount=1 DelCount=0 BrokenCount=0
2018-09-20 20:38:44,318 DEBUG InstCount=1 DelCount=0 BrokenCount=0
2018-09-20 20:38:44,322 DEBUG Extracting content from 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log 
since 2018-09-20 20:38:43
2018-09-20 20:38:44,322 DEBUG Extracting content from 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log 
since 2018-09-20 20:38:43
'

--
Ran 2 tests in 1.110s

FAILED (failures=2)
/build/1st/unattended-upgrades-1.5/test/unattended_upgrade.py:1158: 
ResourceWarning: unclosed file <_io.TextIOWrapper name

Bug#907988: rubber must specify the encoding when opening files

[Hilmar Preuße]

On 09.09.2018 15:33, Adrian Bunk wrote:

Hi Adrian,

Did you find the time to answer my question and re-test? Thanks!

> I can confirm that it fixes the why3 build.
> 
> Your solution is a bit ouch, but I understand why it is not easy to 
> fix in a better way.
> 
Upstream decided to solve the problem a different way and has released
version 1.5.1. New package is on [1], could you retest?

Thanks!

Hilmar

[1] https://freeshell.de/~hille42/rubber/
-- 
sigfault
#206401 http://counter.li.org

Bug#909330: newmat packages are completely broken

[Adrian Bunk]

Source: newmat
Version: 1.10.4-7
Severity: serious
Control: affects -1 libnewmat10ldbl libnewmat10-dev src:sofa-framework

Please do a debdiff of all binaries when doing non-trivial
changes to debian/rules or bumping the debhelper compat.

Contents lost in libnewmat10ldbl:
-rw-r--r--  root/root   /usr/lib/libnewmat.so.10.0.0
-rw-r--r--  root/root   /usr/share/doc/libnewmat10ldbl/changelog.gz
-rw-r--r--  root/root   DEBIAN/shlibs
-rw-r--r--  root/root   DEBIAN/triggers
lrwxrwxrwx  root/root   /usr/lib/libnewmat.so.10 -> libnewmat.so.10.0.0

Contents lost in libnewmat10-dev:
-rw-r--r--  root/root   /usr/include/newmat/boolean.h
-rw-r--r--  root/root   /usr/include/newmat/config.h
-rw-r--r--  root/root   /usr/include/newmat/controlw.h
-rw-r--r--  root/root   /usr/include/newmat/include.h
-rw-r--r--  root/root   /usr/include/newmat/myexcept.h
-rw-r--r--  root/root   /usr/include/newmat/newmat.h
-rw-r--r--  root/root   /usr/include/newmat/newmatap.h
-rw-r--r--  root/root   /usr/include/newmat/newmatio.h
-rw-r--r--  root/root   /usr/include/newmat/newmatnl.h
-rw-r--r--  root/root   /usr/include/newmat/newmatrc.h
-rw-r--r--  root/root   /usr/include/newmat/newmatrm.h
-rw-r--r--  root/root   /usr/include/newmat/precisio.h
-rw-r--r--  root/root   /usr/include/newmat/solution.h
-rw-r--r--  root/root   /usr/lib/libnewmat.a
-rw-r--r--  root/root   /usr/lib/libnewmat.la
-rw-r--r--  root/root   /usr/share/doc/libnewmat10-dev/changelog.gz

Processed: newmat packages are completely broken

[Debian Bug Tracking System]

Processing control commands:

> affects -1 libnewmat10ldbl libnewmat10-dev src:sofa-framework
Bug #909330 [src:newmat] newmat packages are completely broken
Added indication that 909330 affects libnewmat10ldbl, libnewmat10-dev, and 
src:sofa-framework

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

Bug#907491: closed by Paul Gevers (Re: goobook fails to authenticate)

[Sergio Mendoza]

Hi Ilias,

  Unfortunately, no matter how hard I look for to spot the problem, I have
not find the culprit package.  I tried and tried, but couldn't.  This is
the reason I reported the bug to goobook.  Sorry for not being more
helpful.

Regards,

Sergio.

-- 
Sergio Mendoza  
Instituto de Astronomia, UNAM
http://www.mendozza.org/sergio

On Fri, Sep 21, 2018 at 07:39:29PM +0300, Ilias Tsitsimpis wrote:
> Hi Sergio,
> 
> On Sat, Sep 15, 2018 at 11:28AM, Sergio Mendoza wrote:
> > Hi again,
> > 
> >   Today after an upgrade once again the problem appears:
> 
> Do you know which package you updated that broke goobook?
> 
> > sergio@izta:~$ goobook query sergio
> > Traceback (most recent call last):
> >   File "/usr/bin/goobook", line 11, in 
> > load_entry_point('goobook==1.9', 'console_scripts', 'goobook')()
> >   File "/usr/share/goobook/goobook/application.py", line 94, in main
> > args.func(config, args)
> >   File "/usr/share/goobook/goobook/application.py", line 125, in do_query
> > goobk = GooBook(config)
> >   File "/usr/share/goobook/goobook/goobook.py", line 59, in __init__
> > self.cache.load()
> >   File "/usr/share/goobook/goobook/goobook.py", line 257, in load
> > self.update()
> >   File "/usr/share/goobook/goobook/goobook.py", line 264, in update
> > self.contacts = list(self._parse_contacts(gc.fetch_contacts()))
> >   File "/usr/share/goobook/goobook/goobook.py", line 395, in fetch_contacts
> > res = self._get(query)
> >   File "/usr/share/goobook/goobook/goobook.py", line 371, in _get
> > connection_type=httplib2.HTTPSConnectionWithTimeout)
> >   File "/usr/local/lib/python2.7/dist-packages/oauth2client/client.py", 
> > line 562, in new_request
> > redirections, connection_type)
> >   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 
> > 1608, in request
> > (response, content) = self._request(conn, authority, uri, request_uri, 
> > method, body, headers, redirections, cachekey)
> >   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 
> > 1350, in _request
> > (response, content) = self._conn_request(conn, request_uri, method, 
> > body, headers)
> >   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 
> > 1272, in _conn_request
> > conn.connect()
> >   File "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py", line 
> > 1059, in connect
> > raise SSLHandshakeError(e)
> > httplib2.SSLHandshakeError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate 
> > verify failed (_ssl.c:726)
> 
> The above traceback mentions 
> "/usr/local/lib/python2.7/dist-packages/httplib2/__init__.py".
> This is not the canonical location where Debian Python packages get
> installed. I believe you have installed a different version of the
> httplib2 module using pip. Could you please test using the Python module
> provided by the python-httplib2 package?
> 
> Cheers,
> 
> -- 
> Ilias

Processed: found 907887 2.76-5+deb9u1, owner 902341 Emilio Pozuelo Monfort

[Debian Bug Tracking System]

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

> found 907887 2.76-5+deb9u1
Bug #907887 [src:dnsmasq] dnsmasq: Update root DNSSEC trust anchor in stretch 
and jessie
Marked as found in versions dnsmasq/2.76-5+deb9u1.
> owner 902341 Emilio Pozuelo Monfort 
Bug #902341 {Done: Santiago Ruano Rincón } [dnsmasq] 
dns-root-data update breaks dnsmasq startup
Owner recorded as Emilio Pozuelo Monfort .
> thanks
Stopping processing here.

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

Bug#909120: camitk FTBFS: tests segfault (Bug #909120)

[Andreas Tille]

On Fri, Sep 21, 2018 at 07:05:40PM +0200, Emmanuel Promayon wrote:
> Andreas, do you have any smart way to check the list of packages that have
> changed/been uploaded in sid in the dependencies of a package during a
> period of time (here from 9 Sep to 15 Sep)? This might help me finding how
> to solve this.

Since you mentioned vtk in your long text I simply checked

https://tracker.debian.org/libvtkgdcm2-dev

I think we have found a probably candidate (see "news" section).
(gdcm Uploaders in CC - please check the full bug log of this bug)

Hope this helps

Andreas.

-- 
http://fam-tille.de

Bug#902256: [freshplayerplugin] Broken with the latest Firefox versions

[Gunnar Hjalmarsson]

Thanks for working on this! There are two things you need to deal with to be 
able to build:

* The libpdf and NaCl wrappers have been dropped upstream, so you need
  to drop the -libpdf and -nacl binaries.

* You need to patch an upstream commit to make it build with latest
  ffmpeg. It's this commit:

  https://github.com/i-rinat/freshplayerplugin/commit/934aa9c2

We have built it successfully on Ubuntu, so you may want to check what the 
debian/ folder looks like there.

https://launchpad.net/ubuntu/+source/freshplayerplugin/0.3.9-0ubuntu3

Please note, though, that we have a couple of Ubuntu specific changes which are 
not suitable for Debian.

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

Bug#892183: Bug #892183 in ruby-rbpdf marked as pending

[Hashem Nasarat]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-rbpdf/commit/d67ba546d678d01678efffb54a97f46d8230227e


Drop unneeded patches due to new upstream

* Alpha channel tests now pass
* similar htmlentities patch applied upstream

Renumbered the remaining patch accordingly.

Now the package builds!

Closes: #892183



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892183

Processed: Bug #892183 in ruby-rbpdf marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892183 [src:ruby-rbpdf] ruby-rbpdf: FTBFS and Debci failure with Ruby 2.5
Ignoring request to alter tags of bug #892183 to the same tags previously set

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

Processed: Bug #892183 in ruby-rbpdf marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892183 [src:ruby-rbpdf] ruby-rbpdf: FTBFS and Debci failure with Ruby 2.5
Added tag(s) pending.

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

Bug#892183: Bug #892183 in ruby-rbpdf marked as pending

[Hashem Nasarat]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-rbpdf/commit/d67ba546d678d01678efffb54a97f46d8230227e


Drop unneeded patches due to new upstream

* Alpha channel tests now pass
* similar htmlentities patch applied upstream

Renumbered the remaining patch accordingly.

Now the package builds!

Closes: #892183



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892183

Bug#906183: libopenhpi-dev: broken symlink: /usr/lib/libopenhpi_snmp.so -> libopenhpi_snmp.so.3.8.0

[Devarajulu, Mohanasundaram]

Hello Andreas,


I have modified the dependencies. Because of that additional packages need to 
be loaded during upgrade to get the missing file. If all the packages are 
already installed upgrade goes well. If only few packages (libopenhpi-dev) is 
loaded then they are held back during upgrade. I understand this is expected 
behavior from apt when new packages are brought in during upgrade. However the 
following work well

a. apt-get --with-new-packages upgrade

b. apt-get dist-upgrade

c. apt-get install libopenhpi-dev

I think the above behavior is ok. Is it ok to upload the new release?


Regards

Mohan



From: Andreas Beckmann 
Sent: Wednesday, August 15, 2018 4:12:20 AM
To: Debian Bug Tracking System
Subject: Bug#906183: libopenhpi-dev: broken symlink: 
/usr/lib/libopenhpi_snmp.so -> libopenhpi_snmp.so.3.8.0

Package: libopenhpi-dev
Version: 3.8.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m34.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/libopenhpi_snmp.so -> libopenhpi_snmp.so.3.8.0


You are probably missing a dependency on the corresponding
library package.


cheers,

Andreas

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 909039 https://bugzilla.mozilla.org/show_bug.cgi?id=1482248
Bug #909039 [thunderbird] thunderbird: Crash when starting Thunderbird after 
latest security update to 1:60.0-3~deb9u1
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1482248'.
> reassign 805854 libsoup2.4-1 2.48.0-1
Bug #805854 [gnome-online-accounts] gnome-online-accounts: unable to add Google 
account as lost keyboard focus when Google Apps requests Kerberos credentials
Bug reassigned from package 'gnome-online-accounts' to 'libsoup2.4-1'.
No longer marked as found in versions gnome-online-accounts/3.14.2-1.
Ignoring request to alter fixed versions of bug #805854 to the same values 
previously set
Bug #805854 [libsoup2.4-1] gnome-online-accounts: unable to add Google account 
as lost keyboard focus when Google Apps requests Kerberos credentials
Marked as found in versions libsoup2.4/2.48.0-1.
> forwarded 805854 https://bugzilla.gnome.org/show_bug.cgi?id=587145
Bug #805854 [libsoup2.4-1] gnome-online-accounts: unable to add Google account 
as lost keyboard focus when Google Apps requests Kerberos credentials
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=587145'.
> tags 805854 fixed-upstream
Bug #805854 [libsoup2.4-1] gnome-online-accounts: unable to add Google account 
as lost keyboard focus when Google Apps requests Kerberos credentials
Added tag(s) fixed-upstream.
> affects 805854 gnome-online-accounts
Bug #805854 [libsoup2.4-1] gnome-online-accounts: unable to add Google account 
as lost keyboard focus when Google Apps requests Kerberos credentials
Added indication that 805854 affects gnome-online-accounts
> # https://bugzilla.gnome.org/show_bug.cgi?id=758333
>
End of message, stopping processing here.

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

Bug#909120: camitk FTBFS: tests segfault (Bug #909120)

[Bernhard Übelacker]

Hello Emmanuel,
I made a mistake and did my first investigations on testing instead of unstable.
So my findings of my first mail are unrelated (but hope they still help).

So I did another try and got all tests fail like in the reproducible build log.


Something bad happens in these lines:
(gdb) list RendererWidget.cpp:589
588 
orientationDecorationsTextMapper[i]->SetInput(orientationDecorationLetters[i].toStdString().c_str());
589 
orientationDecorationsTextMapper[i]->GetTextProperty()->ShallowCopy(orientationDecorationsProp);


Valgrind also points to that location.

For some reason I could not step into the SetInput method and tried
therefore to get further on instruction level and found my self to
my surprise in libvtkRenderingOpenGL2-7.1.so.7.1.

Therefore I assume Andreas is right that libvtkgdcm2.8 started this issue,
as that pulls in libvtk7.1, so we have some vtk6 and some vtk7 libraries in
the same process.

I tried changing debian/control to build agains libvtk7-dev and libvtk7-qt-dev.
With that even more tests crash in the same QGLContext::makeCurrent call,
but thats maybe a different issue.

Kind regards,
Bernhard



With all required dbgsym packages installed the stack looks like this:
(gdb) bt
#0  vtkTextProperty::ShallowCopy (this=0xbae9c9b0, tprop=0x55cdbae92d70) at 
./Rendering/Core/vtkTextProperty.cxx:70
#1  0x7fdb0af837d7 in camitk::RendererWidget::RendererWidget(QWidget*, 
camitk::RendererWidget::ControlMode) () at 
/usr/include/vtk-6.3/vtkSmartPointer.h:77
#2  0x7fdb0af6fd42 in 
camitk::InteractiveViewer::InteractiveViewer(QString&, 
camitk::InteractiveViewer::ViewerType) () at 
./sdk/libraries/core/viewer/InteractiveViewer.cpp:192
#3  0x7fdb0af71533 in camitk::InteractiveViewer::getNewViewer(QString, 
camitk::InteractiveViewer::ViewerType) () at 
./sdk/libraries/core/viewer/InteractiveViewer.cpp:90
#4  0x7fdb0af717c5 in camitk::InteractiveViewer::getViewer(QString) () at 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:953
#5  0x7fdb0af71b25 in camitk::InteractiveViewer::getAxialViewer() () at 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:953
#6  0x7fdb0af3ca2f in camitk::SingleImageComponent::initRepresentation() () 
at ./sdk/libraries/core/component/image/SingleImageComponent.cpp:94
#7  0x7fdb0af3cb67 in 
camitk::SingleImageComponent::SingleImageComponent(camitk::Component*, 
camitk::Slice::SliceOrientation, QString const&, 
vtkSmartPointer) () at 
./sdk/libraries/core/component/image/SingleImageComponent.cpp:58
#8  0x7fdb0af33fbf in camitk::ImageComponent::buildImageComponents() () at 
/usr/include/vtk-6.3/vtkSmartPointer.h:26
#9  0x7fdb0af36b4d in 
camitk::ImageComponent::setImageData(vtkSmartPointer, bool, 
camitk::ImageOrientationHelper::PossibleImageOrientations, 
vtkSmartPointer) () at 
./sdk/libraries/core/component/image/ImageComponent.cpp:313
#10 0x7fdaf567adf9 in VtkImageComponent::createComponent(QString const&) () 
at /usr/include/vtk-6.3/vtkSmartPointer.h:26
#11 0x7fdaf567b905 in VtkImageComponent::VtkImageComponent(QString const&) 
() at ./sdk/components/vtkimage/VtkImageComponent.cpp:53
#12 0x7fdaf567bf3a in VtkImageComponentExtension::open(QString const&) () 
at ./sdk/components/vtkimage/VtkImageComponentExtension.cpp:76
#13 0x7fdb0af04c24 in camitk::Application::open(QString const&) () at 
./sdk/libraries/core/application/Application.cpp:470
#14 0x55cdb93043df in main () at /usr/include/c++/8/bits/basic_string.h:2293
#15 0x7fdb09eccb17 in __libc_start_main (main=0x55cdb9303e80 , 
argc=5, argv=0x7ffd21845c18, init=, fini=, 
rtld_fini=, stack_end=0x7ffd21845c08) at ../csu/libc-start.c:310
#16 0x55cdb93051aa in _start () at 
./sdk/applications/testactions/main.cpp:189


LANG=C dpkg --purge libvtk7.1
dpkg: dependency problems prevent removal of libvtk7.1:
 libvtkgdcm2.8:amd64 depends on libvtk7.1.


(gdb) info share
>FromTo  Syms Read   Shared Object Library
...
0x77265580  0x77458d2d  Yes 
/usr/lib/x86_64-linux-gnu/libvtkCommonCore-6.3.so.6.3
...
0x7fffe934cee0  0x7fffe9515aed  Yes (*) 
/usr/lib/x86_64-linux-gnu/libvtkCommonCore-7.1.so.7.1


# Unstable:


- change sources.list from buster to unstable
apt update
apt dist-upgrade
reboot
apt autoremove
apt install apt-show-versions
apt-show-versions | grep No
dpkg --purge libdns-export1100

apt build-dep camitk
apt install mc htop systemd-coredump fakeroot gdb valgrind git libvtk6.3-dbgsym 
libqt5core5a-dbgsym


mkdir vtk6/orig -p
cdvtk6/orig
apt source vtk6
cd ../..


mkdir qtbase-opensource-src/orig -p
cdqtbase-opensource-src/orig
apt source qtbase-opensource-src
cd ../..


mkdir camitk/orig -p
cdcamitk/orig
apt source camitk
cd ../..


cd camitk
cp -a orig try1
cd try1/camitk-4.1.2
dpkg-buildpackage



[Sa Sep 22 00:00:04 2018] camitk-testacti[24045]: segfault at bae9c9b0 ip 
7fdb08754f15 sp 7ffd21844f50 error 4 in 
libvtkRenderingCore

Processed: severity of 909309 is serious

[Debian Bug Tracking System]

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

> severity 909309 serious
Bug #909309 [clipit] clipit: Unable to access history using hotkeys and crash
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#909000: Enigmail 2.0 needed in Stretch after Thunderbird 60 upload

[Simon Richter]

Hi,

pulling gnupg or enigmail from backports would only solve the problem
for new installations, but doesn't help users who have both thunderbird
and enigmail installed, only have stretch and stretch-security in the
sources.list (what I'd expect to be the majority) and are now trying to
run "apt upgrade":

Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  icedove lightning thunderbird
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

So this is blocking security upgrades.

   Simon



signature.asc
Description: OpenPGP digital signature

Bug#909343: libcatalyst-perl: fails to build with libmoosex-getopt-perl 0.73-1

[gregor herrmann]

Source: libcatalyst-perl
Version: 5.90118-1
Severity: serious
Tags: upstream sid buster
Justification: fails to build from source
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=127050

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first noticed by ci.debian.net, one test in libcatalyst-perl fails
with the new libmoosex-getopt-perl 0.73-1.

t/aggregate/unit_core_script_help.t ...
No subtests run
…
Test Summary Report
- ---
t/aggregate/unit_core_script_help.t (Wstat: 0 
Tests: 0 Failed: 0)
  Parse errors: No plan found in TAP output


The upstream report at https://rt.cpan.org/Public/Bug/Display.html?id=127050
is undecided if the problem is in Catalyst-Runtime or in
MooseX-Getopt, there's also https://rt.cpan.org/Ticket/Display.html?id=127096


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlulr4FfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbYCA//c9H7i6yDCv1RCgKhxvO4uLY1BJEdYAw+uidNV2aLXXyUfCueJorewdHN
ccZirNKbRwxkkIQtSZYCB0qvlhM0RRdk8//aXR+FM+hSiVeEXp/HRXNrAKji19jT
6JJJkRSoTNEkvc0OIgdi/ljRgKS27r+DLBfFjKV18IiTAdfO45Dbz1zso/7QGkUa
tRGTaP9B3jOVTYT9sCB0UFfvtpDuQ9Svl+aWFY4VIGPDbF/1j4Y5QWf/BdXqsyuN
9Gukw2Zy2RxGYTZ4diHR8Dwh9WGzvX9FBZUkkT39EbtqYPazSF0X4QryTXt4KKQ/
0QDTLQV4EAaXp3GP472LCPNvmZxBUg75QEeczC++gAQCFnnTYjW90PvntNEIy3uV
BaIXbkXEdai8A1vDn3ay8gqOPukcASIDwnqYp7GCmpheru4RofBWzxPnxPfB0k+T
2yo4fkPIjXbttrCUmQ2Wlki8ZMuyfhfJN9SFuGxsoOEg+xRSDgum34Hd7Isr99Gi
0hWTpxZYepyUGDx+mJm3m7SpzWZeeH1xj6cJUgzS23UzEkaHyB4ZmVaLFOFvkMhB
YDFDrJjZkBV+53oNNiahJ434GMZWdrqcvko+FxFtYvGpusEaF6YVwQpJe+oeSx3P
913F96sBqq/cfNEcEjQJF4shi6yrWInGGzZxTefVJsG2EdQsboM=
=632F
-END PGP SIGNATURE-

Bug#908396: marked as done (firefox-esr: stopped working after upgrade from 59 to 60)

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:08:43 +
with message-id 
and subject line Bug#908449: fixed in firefox-esr 60.2.1esr-1
has caused the Debian Bug report #908449,
regarding firefox-esr: stopped working after upgrade from 59 to 60
to be marked as done.

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

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


-- 
908449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: important

Dear Maintainer,
firefox-esr does not work anymore, crashes immediately even in safe mode:

$ firefox-esr -safe-mode
ExceptionHandler::GenerateDump cloned child 9620
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...

I suspect it's related to my CPU not having sse2 instructions and Firefox
compiled with some flags requiring them.

$ cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 11
model name  : Intel(R) Celeron(TM) CPU1100MHz
stepping: 1
microcode   : 0x1c
cpu MHz : 1365.108
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov 
pse36 mmx fxsr sse
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips: 2730.21
clflush size: 32
cache_alignment : 32
address sizes   : 36 bits physical, 32 bits virtual
power management:


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (10, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-8-686 (SMP w/1 CPU core)
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 firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:7.2.0-19
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.2.12-1~deb9u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
pn  libcanberra0   
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libgtk2.0-02.24.31-2

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 60.2.1esr-1

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox-esr package)

(This message was generated automatically at th

Bug#908821: marked as done (firefox-esr: updated version and firefox crasehst at start)

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:08:43 +
with message-id 
and subject line Bug#908396: fixed in firefox-esr 60.2.1esr-1
has caused the Debian Bug report #908396,
regarding firefox-esr: updated version and firefox crasehst at start
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.)


-- 
908396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: normal

-- Package-specific info:

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.2.12-1~deb9u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-3
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libgtk2.0-02.24.31-2

-- no debconf information

processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 6
model name  : AMD Athlon(tm) XP 1700+
stepping: 2
cpu MHz : 1466.475
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 2932.95
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 6
model name  : AMD Athlon(tm) XP 1700+
stepping: 2
cpu MHz : 1466.475
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 2932.95
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 60.2.1esr-1

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

A s

Bug#877445: marked as done (Certain sites crash Firefox on pre-SSE2 CPUs)

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:08:43 +
with message-id 
and subject line Bug#877445: fixed in firefox-esr 60.2.1esr-1
has caused the Debian Bug report #877445,
regarding Certain sites crash Firefox on pre-SSE2 CPUs
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.)


-- 
877445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox
Version: 56.0-2
Severity: important

Visiting certain sites such as github crashes with SIGILL on Pentium
III and other CPUs with no SSE2 support due to some parts of Firefox
code assuming SSE2 unconditionally. While the upstream doesn't support
pre-SSE2 processors anymore, my understanding is that the Debian
package does, and therefore it's a bug. AFAIU the fix shouldn't be too
invasive, because the upstream sources still pretty much *have to*,
and do, contain scalar fallbacks for non-x86 platforms.

The same sites work for the time being in firefox-esr, which is what
I'm using as a workaround.

Top of backtrace after receiving SIGILL:

(gdb) bt
#0  0xb0b2dae3 in _mm_unpacklo_epi64(long long __vector(2), long long
__vector(2)) (__B=..., __A=...)
at /usr/lib/gcc/i686-linux-gnu/7/include/emmintrin.h:1011
#1  mozilla::gfx::UnpremultiplyVector_SSE2 (
aSrc=...)
at /build/firefox-yYj8Vc/firefox-56.0/gfx/2d/SwizzleSSE2.cpp:184
#2  mozilla::gfx::Unpremultiply_SSE2 (
aSrc=0x8dd88b00 "", aSrcGap=944, aDst=0x8ddc4000 "",
aDstGap=0, aSize=...)
at /build/firefox-yYj8Vc/firefox-56.0/gfx/2d/SwizzleSSE2.cpp:227
#3  0xb0b8021a in mozilla::gfx::UnpremultiplyData (
aSrc=0x8dd88b00 "", aSrcStride=1200,
aSrcFormat=mozilla::gfx::SurfaceFormat::B8G8R8A8,
aDst=0x8ddc4000 "", aDstStride=256,
aDstFormat=mozilla::gfx::SurfaceFormat::R8G8B8A8,
aSize=...)
at /build/firefox-yYj8Vc/firefox-56.0/gfx/2d/Swizzle.cpp:416
#4  0xb178a64d in mozilla::dom::CanvasRenderingContext2D::GetImageDataArray (
this=0x90b19000, aCx=0xb7073000, aX=0, aY=16,
aWidth=64, aHeight=1, aRetval=0xbfd5d3a8)
at 
/build/firefox-yYj8Vc/firefox-56.0/dom/canvas/CanvasRenderingContext2D.cpp:5936
#5  0xb178a84a in mozilla::dom::CanvasRenderingContext2D::GetImageData (
this=0x90b19000, aCx=0xb7073000, aSx=0, aSy=16,
aSw=64, aSh=1, aError=...)
at 
/build/firefox-yYj8Vc/firefox-56.0/dom/canvas/CanvasRenderingContext2D.cpp:5839
#6  0xb13a3d7e in mozilla::dom::CanvasRenderingContext2DBinding::getImageData (
cx=0xb7073000, obj=..., self=0x90b19000,
args=...)
at 
/build/firefox-yYj8Vc/firefox-56.0/build-browser/dom/bindings/CanvasRenderingContext2DBinding.cpp:4064
#7  0xb1725c5d in mozilla::dom::GenericBindingMethod (
cx=0xb7073000, argc=, vp=0xa8b84210)
at /build/firefox-yYj8Vc/firefox-56.0/dom/bindings/BindingUtils.cpp:3053
#8  0xb329220c in js::CallJSNative (args=...,
native=0xb1725a80 ,
cx=0xb7073000)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/jscntxtinlines.h:293
#9  js::InternalCallOrConstruct (cx=0xb7073000, args=...,
construct=js::NO_CONSTRUCT)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/vm/Interpreter.cpp:469
#10 0xb3292592 in InternalCall (cx=, args=...)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/vm/Interpreter.cpp:514
#11 0xb3285c6a in js::CallFromStack (args=...,
cx=)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/vm/Interpreter.cpp:520
#12 Interpret (cx=0xb7073000, state=...)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/vm/Interpreter.cpp:3064
#13 0xb3291e8d in js::RunScript (cx=0xb7073000, state=...)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/vm/Interpreter.cpp:409
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 60.2.1esr-1

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox-esr 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, 22 Sep 2018 08:10:27 +0900
Source: firefox-esr
Binary: firefox-esr firefox-esr-l10n-

Bug#908449: marked as done ((no subject))

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:08:43 +
with message-id 
and subject line Bug#908449: fixed in firefox-esr 60.2.1esr-1
has caused the Debian Bug report #908449,
regarding (no subject)
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.)


-- 
908449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: grave

Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)


After updating from firefox-esr:i386 52.9.0esr-1~deb9u1 to 60.2.0esr-1~deb9u2, 
it no longer works.

It opens the crashreporter every time when trying to open it:
«Firefox had a problem and crashed. We’ll try to restore your tabs and 
windows when it restarts.

To help us diagnose and fix the problem, you can send us a crash report.»
and choosing to restart it only leads to that same window.

Running under gdb shows it is trying to run an unsupported instruction:
Thread 1 "firefox-esr" received signal SIGILL, Illegal instruction.
0xb352826f in ?? () from /usr/lib/firefox-esr/libxul.so

(gdb) x/i 0xb352826f
=> 0xb352826f:  movsd  -0x18(%ebp),%xmm0

or in intel syntax:
(gdb) set disassembly-flavor intel
(gdb) x/i 0xb352826f
=> 0xb352826f:  movsd  xmm0,QWORD PTR [ebp-0x18]


and indeed, this instruction is not accepted on the -admittedly old- computer 
where the fault happened.

/proc/cpuinfo shows it supports sse, but not sse2. And movsd is a sse2 
instruction [1]


1- https://en.wikipedia.org/wiki/X86_instruction_listings#SSE2_instructions
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 60.2.1esr-1

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox-esr 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, 22 Sep 2018 08:10:27 +0900
Source: firefox-esr
Binary: firefox-esr firefox-esr-l10n-all firefox-esr-l10n-ach 
firefox-esr-l10n-af firefox-esr-l10n-an firefox-esr-l10n-ar firefox-esr-l10n-as 
firefox-esr-l10n-ast firefox-esr-l10n-az firefox-esr-l10n-be 
firefox-esr-l10n-bg firefox-esr-l10n-bn-bd firefox-esr-l10n-bn-in 
firefox-esr-l10n-br firefox-esr-l10n-bs firefox-esr-l10n-ca 
firefox-esr-l10n-cak firefox-esr-l10n-cs firefox-esr-l10n-cy 
firefox-esr-l10n-da firefox-esr-l10n-de firefox-esr-l10n-dsb 
firefox-esr-l10n-el firefox-esr-l10n-en-gb firefox-esr-l10n-en-za 
firefox-esr-l10n-eo firefox-esr-l10n-es-ar firefox-esr-l10n-es-cl 
firefox-esr-l10n-es-es firefox-esr-l10n-es-mx firefox-esr-l10n-et 
firefox-esr-l10n-eu firefox-esr-l10n-fa firefox-esr-l10n-ff firefox-esr-l10n-fi 
firefox-esr-l10n-fr firefox-esr-l10n-fy-nl firefox-esr-l10n-ga-ie 
firefox-esr-l10n-gd firefox-esr-l10n-gl firefox-esr-l10n-gn 
firefox-esr-l10n-gu-in firefox-esr-l10n-he firefox-esr-l10n-hi-in 
firefox-esr-l10n-hr firefox-esr-l10n-hsb firefox-esr-l10n-hu
 firefox-esr-l10n-hy-am firefox-esr-l10n-ia firefox-esr-l10n-id 
firefox-esr-l10n-is firefox-esr-l10n-it firefox-esr-l10n-ja firefox-esr-l10n-ka 
firefox-esr-l10n-kab firefox-esr-l10n-kk firefox-esr-l10n-km 
firefox-esr-l10n-kn firefox-esr-l10n-ko firefox-esr-l10n-lij 
firefox-esr-l10n-lt firefox-esr-l10n-lv firefox-esr-l10n-mai 
firefox-esr-l10n-mk firefox-esr-l10n-ml firefox-esr-l10n-mr firefox-esr-l10n-ms 
firefox-esr-l10n-my firefox-esr-l10n-nb-no firefox-esr-l10n-ne-np 
firefox-esr-l10n-nl firefox-esr-l10n-nn-no firefox-esr-l10n-oc 
firefox-esr-l10n-or firefox-esr-l10n-pa-in firefox-esr-l10n-pl 
firefox-esr-l10n-pt-br firefox-esr-l10n-pt-pt firefox-esr-l10n-rm 
firefox-esr-l10n-ro firefox-esr-l10n-ru firefox-esr-l10n-si firefox-esr-l10n-sk 
firefox-esr-l10n-sl firefox-esr-l10n-son firefox-esr-l10n-sq 
firefox-esr-l10n-sr firefox-esr-l10n-sv-se firefox-esr-l10n-ta 
firefox-esr-l10n-te firefox-esr-l10n-th firefox-esr-l10n-tr firefox-esr-l10n-uk 
firefox-esr-l10n-ur
 firefox-esr-l10n-uz firefox-esr-l10n-vi firefox-es

Bug#908396: marked as done (firefox-esr: stopped working after upgrade from 59 to 60)

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:08:43 +
with message-id 
and subject line Bug#908396: fixed in firefox-esr 60.2.1esr-1
has caused the Debian Bug report #908396,
regarding firefox-esr: stopped working after upgrade from 59 to 60
to be marked as done.

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

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


-- 
908396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: important

Dear Maintainer,
firefox-esr does not work anymore, crashes immediately even in safe mode:

$ firefox-esr -safe-mode
ExceptionHandler::GenerateDump cloned child 9620
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...

I suspect it's related to my CPU not having sse2 instructions and Firefox
compiled with some flags requiring them.

$ cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 11
model name  : Intel(R) Celeron(TM) CPU1100MHz
stepping: 1
microcode   : 0x1c
cpu MHz : 1365.108
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov 
pse36 mmx fxsr sse
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips: 2730.21
clflush size: 32
cache_alignment : 32
address sizes   : 36 bits physical, 32 bits virtual
power management:


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (10, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-8-686 (SMP w/1 CPU core)
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 firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:7.2.0-19
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.2.12-1~deb9u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
pn  libcanberra0   
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libgtk2.0-02.24.31-2

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 60.2.1esr-1

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox-esr package)

(This message was generated automatically at th

Bug#908449: marked as done ((no subject))

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:08:43 +
with message-id 
and subject line Bug#908396: fixed in firefox-esr 60.2.1esr-1
has caused the Debian Bug report #908396,
regarding (no subject)
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.)


-- 
908396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: grave

Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)


After updating from firefox-esr:i386 52.9.0esr-1~deb9u1 to 60.2.0esr-1~deb9u2, 
it no longer works.

It opens the crashreporter every time when trying to open it:
«Firefox had a problem and crashed. We’ll try to restore your tabs and 
windows when it restarts.

To help us diagnose and fix the problem, you can send us a crash report.»
and choosing to restart it only leads to that same window.

Running under gdb shows it is trying to run an unsupported instruction:
Thread 1 "firefox-esr" received signal SIGILL, Illegal instruction.
0xb352826f in ?? () from /usr/lib/firefox-esr/libxul.so

(gdb) x/i 0xb352826f
=> 0xb352826f:  movsd  -0x18(%ebp),%xmm0

or in intel syntax:
(gdb) set disassembly-flavor intel
(gdb) x/i 0xb352826f
=> 0xb352826f:  movsd  xmm0,QWORD PTR [ebp-0x18]


and indeed, this instruction is not accepted on the -admittedly old- computer 
where the fault happened.

/proc/cpuinfo shows it supports sse, but not sse2. And movsd is a sse2 
instruction [1]


1- https://en.wikipedia.org/wiki/X86_instruction_listings#SSE2_instructions
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 60.2.1esr-1

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox-esr 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, 22 Sep 2018 08:10:27 +0900
Source: firefox-esr
Binary: firefox-esr firefox-esr-l10n-all firefox-esr-l10n-ach 
firefox-esr-l10n-af firefox-esr-l10n-an firefox-esr-l10n-ar firefox-esr-l10n-as 
firefox-esr-l10n-ast firefox-esr-l10n-az firefox-esr-l10n-be 
firefox-esr-l10n-bg firefox-esr-l10n-bn-bd firefox-esr-l10n-bn-in 
firefox-esr-l10n-br firefox-esr-l10n-bs firefox-esr-l10n-ca 
firefox-esr-l10n-cak firefox-esr-l10n-cs firefox-esr-l10n-cy 
firefox-esr-l10n-da firefox-esr-l10n-de firefox-esr-l10n-dsb 
firefox-esr-l10n-el firefox-esr-l10n-en-gb firefox-esr-l10n-en-za 
firefox-esr-l10n-eo firefox-esr-l10n-es-ar firefox-esr-l10n-es-cl 
firefox-esr-l10n-es-es firefox-esr-l10n-es-mx firefox-esr-l10n-et 
firefox-esr-l10n-eu firefox-esr-l10n-fa firefox-esr-l10n-ff firefox-esr-l10n-fi 
firefox-esr-l10n-fr firefox-esr-l10n-fy-nl firefox-esr-l10n-ga-ie 
firefox-esr-l10n-gd firefox-esr-l10n-gl firefox-esr-l10n-gn 
firefox-esr-l10n-gu-in firefox-esr-l10n-he firefox-esr-l10n-hi-in 
firefox-esr-l10n-hr firefox-esr-l10n-hsb firefox-esr-l10n-hu
 firefox-esr-l10n-hy-am firefox-esr-l10n-ia firefox-esr-l10n-id 
firefox-esr-l10n-is firefox-esr-l10n-it firefox-esr-l10n-ja firefox-esr-l10n-ka 
firefox-esr-l10n-kab firefox-esr-l10n-kk firefox-esr-l10n-km 
firefox-esr-l10n-kn firefox-esr-l10n-ko firefox-esr-l10n-lij 
firefox-esr-l10n-lt firefox-esr-l10n-lv firefox-esr-l10n-mai 
firefox-esr-l10n-mk firefox-esr-l10n-ml firefox-esr-l10n-mr firefox-esr-l10n-ms 
firefox-esr-l10n-my firefox-esr-l10n-nb-no firefox-esr-l10n-ne-np 
firefox-esr-l10n-nl firefox-esr-l10n-nn-no firefox-esr-l10n-oc 
firefox-esr-l10n-or firefox-esr-l10n-pa-in firefox-esr-l10n-pl 
firefox-esr-l10n-pt-br firefox-esr-l10n-pt-pt firefox-esr-l10n-rm 
firefox-esr-l10n-ro firefox-esr-l10n-ru firefox-esr-l10n-si firefox-esr-l10n-sk 
firefox-esr-l10n-sl firefox-esr-l10n-son firefox-esr-l10n-sq 
firefox-esr-l10n-sr firefox-esr-l10n-sv-se firefox-esr-l10n-ta 
firefox-esr-l10n-te firefox-esr-l10n-th firefox-esr-l10n-tr firefox-esr-l10n-uk 
firefox-esr-l10n-ur
 firefox-esr-l10n-uz firefox-esr-l10n-vi firefox-es

Bug#908821: marked as done (firefox-esr: updated version and firefox crasehst at start)

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:08:43 +
with message-id 
and subject line Bug#908449: fixed in firefox-esr 60.2.1esr-1
has caused the Debian Bug report #908449,
regarding firefox-esr: updated version and firefox crasehst at start
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.)


-- 
908449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: normal

-- Package-specific info:

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.2.12-1~deb9u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-3
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libgtk2.0-02.24.31-2

-- no debconf information

processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 6
model name  : AMD Athlon(tm) XP 1700+
stepping: 2
cpu MHz : 1466.475
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 2932.95
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 6
model name  : AMD Athlon(tm) XP 1700+
stepping: 2
cpu MHz : 1466.475
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 2932.95
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 60.2.1esr-1

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

A s

Bug#908396: marked as done (firefox-esr: stopped working after upgrade from 59 to 60)

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:23:43 +
with message-id 
and subject line Bug#908396: fixed in firefox 62.0.2-1
has caused the Debian Bug report #908396,
regarding firefox-esr: stopped working after upgrade from 59 to 60
to be marked as done.

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

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


-- 
908396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: important

Dear Maintainer,
firefox-esr does not work anymore, crashes immediately even in safe mode:

$ firefox-esr -safe-mode
ExceptionHandler::GenerateDump cloned child 9620
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...

I suspect it's related to my CPU not having sse2 instructions and Firefox
compiled with some flags requiring them.

$ cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 11
model name  : Intel(R) Celeron(TM) CPU1100MHz
stepping: 1
microcode   : 0x1c
cpu MHz : 1365.108
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov 
pse36 mmx fxsr sse
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips: 2730.21
clflush size: 32
cache_alignment : 32
address sizes   : 36 bits physical, 32 bits virtual
power management:


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (10, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-8-686 (SMP w/1 CPU core)
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 firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:7.2.0-19
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.2.12-1~deb9u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
pn  libcanberra0   
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libgtk2.0-02.24.31-2

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: firefox
Source-Version: 62.0.2-1

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox package)

(This message was generated automatically at their request; if you
be

Bug#908449: marked as done ((no subject))

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:23:43 +
with message-id 
and subject line Bug#908449: fixed in firefox 62.0.2-1
has caused the Debian Bug report #908449,
regarding (no subject)
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.)


-- 
908449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: grave

Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)


After updating from firefox-esr:i386 52.9.0esr-1~deb9u1 to 60.2.0esr-1~deb9u2, 
it no longer works.

It opens the crashreporter every time when trying to open it:
«Firefox had a problem and crashed. We’ll try to restore your tabs and 
windows when it restarts.

To help us diagnose and fix the problem, you can send us a crash report.»
and choosing to restart it only leads to that same window.

Running under gdb shows it is trying to run an unsupported instruction:
Thread 1 "firefox-esr" received signal SIGILL, Illegal instruction.
0xb352826f in ?? () from /usr/lib/firefox-esr/libxul.so

(gdb) x/i 0xb352826f
=> 0xb352826f:  movsd  -0x18(%ebp),%xmm0

or in intel syntax:
(gdb) set disassembly-flavor intel
(gdb) x/i 0xb352826f
=> 0xb352826f:  movsd  xmm0,QWORD PTR [ebp-0x18]


and indeed, this instruction is not accepted on the -admittedly old- computer 
where the fault happened.

/proc/cpuinfo shows it supports sse, but not sse2. And movsd is a sse2 
instruction [1]


1- https://en.wikipedia.org/wiki/X86_instruction_listings#SSE2_instructions
--- End Message ---
--- Begin Message ---
Source: firefox
Source-Version: 62.0.2-1

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox 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, 22 Sep 2018 09:02:25 +0900
Source: firefox
Binary: firefox firefox-l10n-all firefox-l10n-ach firefox-l10n-af 
firefox-l10n-an firefox-l10n-ar firefox-l10n-as firefox-l10n-ast 
firefox-l10n-az firefox-l10n-be firefox-l10n-bg firefox-l10n-bn-bd 
firefox-l10n-bn-in firefox-l10n-br firefox-l10n-bs firefox-l10n-ca 
firefox-l10n-cak firefox-l10n-cs firefox-l10n-cy firefox-l10n-da 
firefox-l10n-de firefox-l10n-dsb firefox-l10n-el firefox-l10n-en-ca 
firefox-l10n-en-gb firefox-l10n-en-za firefox-l10n-eo firefox-l10n-es-ar 
firefox-l10n-es-cl firefox-l10n-es-es firefox-l10n-es-mx firefox-l10n-et 
firefox-l10n-eu firefox-l10n-fa firefox-l10n-ff firefox-l10n-fi firefox-l10n-fr 
firefox-l10n-fy-nl firefox-l10n-ga-ie firefox-l10n-gd firefox-l10n-gl 
firefox-l10n-gn firefox-l10n-gu-in firefox-l10n-he firefox-l10n-hi-in 
firefox-l10n-hr firefox-l10n-hsb firefox-l10n-hu firefox-l10n-hy-am 
firefox-l10n-ia firefox-l10n-id firefox-l10n-is firefox-l10n-it firefox-l10n-ja 
firefox-l10n-ka firefox-l10n-kab firefox-l10n-kk firefox-l10n-km
 firefox-l10n-kn firefox-l10n-ko firefox-l10n-lij firefox-l10n-lt 
firefox-l10n-lv firefox-l10n-mai firefox-l10n-mk firefox-l10n-ml 
firefox-l10n-mr firefox-l10n-ms firefox-l10n-my firefox-l10n-nb-no 
firefox-l10n-ne-np firefox-l10n-nl firefox-l10n-nn-no firefox-l10n-oc 
firefox-l10n-or firefox-l10n-pa-in firefox-l10n-pl firefox-l10n-pt-br 
firefox-l10n-pt-pt firefox-l10n-rm firefox-l10n-ro firefox-l10n-ru 
firefox-l10n-si firefox-l10n-sk firefox-l10n-sl firefox-l10n-son 
firefox-l10n-sq firefox-l10n-sr firefox-l10n-sv-se firefox-l10n-ta 
firefox-l10n-te firefox-l10n-th firefox-l10n-tr firefox-l10n-uk firefox-l10n-ur 
firefox-l10n-uz firefox-l10n-vi firefox-l10n-xh firefox-l10n-zh-cn
 firefox-l10n-zh-tw
Architecture: source
Version: 62.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 
Description:
 firefox- Mozilla Firefox web browser
 firefox-l10n-ach - Acoli language package for Firefox
 firefox-l10n-af - Afrikaans language package for Firefox
 firefox-l10n-all - All lang

Bug#908449: marked as done ((no subject))

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:23:43 +
with message-id 
and subject line Bug#908396: fixed in firefox 62.0.2-1
has caused the Debian Bug report #908396,
regarding (no subject)
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.)


-- 
908396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: grave

Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)


After updating from firefox-esr:i386 52.9.0esr-1~deb9u1 to 60.2.0esr-1~deb9u2, 
it no longer works.

It opens the crashreporter every time when trying to open it:
«Firefox had a problem and crashed. We’ll try to restore your tabs and 
windows when it restarts.

To help us diagnose and fix the problem, you can send us a crash report.»
and choosing to restart it only leads to that same window.

Running under gdb shows it is trying to run an unsupported instruction:
Thread 1 "firefox-esr" received signal SIGILL, Illegal instruction.
0xb352826f in ?? () from /usr/lib/firefox-esr/libxul.so

(gdb) x/i 0xb352826f
=> 0xb352826f:  movsd  -0x18(%ebp),%xmm0

or in intel syntax:
(gdb) set disassembly-flavor intel
(gdb) x/i 0xb352826f
=> 0xb352826f:  movsd  xmm0,QWORD PTR [ebp-0x18]


and indeed, this instruction is not accepted on the -admittedly old- computer 
where the fault happened.

/proc/cpuinfo shows it supports sse, but not sse2. And movsd is a sse2 
instruction [1]


1- https://en.wikipedia.org/wiki/X86_instruction_listings#SSE2_instructions
--- End Message ---
--- Begin Message ---
Source: firefox
Source-Version: 62.0.2-1

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox 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, 22 Sep 2018 09:02:25 +0900
Source: firefox
Binary: firefox firefox-l10n-all firefox-l10n-ach firefox-l10n-af 
firefox-l10n-an firefox-l10n-ar firefox-l10n-as firefox-l10n-ast 
firefox-l10n-az firefox-l10n-be firefox-l10n-bg firefox-l10n-bn-bd 
firefox-l10n-bn-in firefox-l10n-br firefox-l10n-bs firefox-l10n-ca 
firefox-l10n-cak firefox-l10n-cs firefox-l10n-cy firefox-l10n-da 
firefox-l10n-de firefox-l10n-dsb firefox-l10n-el firefox-l10n-en-ca 
firefox-l10n-en-gb firefox-l10n-en-za firefox-l10n-eo firefox-l10n-es-ar 
firefox-l10n-es-cl firefox-l10n-es-es firefox-l10n-es-mx firefox-l10n-et 
firefox-l10n-eu firefox-l10n-fa firefox-l10n-ff firefox-l10n-fi firefox-l10n-fr 
firefox-l10n-fy-nl firefox-l10n-ga-ie firefox-l10n-gd firefox-l10n-gl 
firefox-l10n-gn firefox-l10n-gu-in firefox-l10n-he firefox-l10n-hi-in 
firefox-l10n-hr firefox-l10n-hsb firefox-l10n-hu firefox-l10n-hy-am 
firefox-l10n-ia firefox-l10n-id firefox-l10n-is firefox-l10n-it firefox-l10n-ja 
firefox-l10n-ka firefox-l10n-kab firefox-l10n-kk firefox-l10n-km
 firefox-l10n-kn firefox-l10n-ko firefox-l10n-lij firefox-l10n-lt 
firefox-l10n-lv firefox-l10n-mai firefox-l10n-mk firefox-l10n-ml 
firefox-l10n-mr firefox-l10n-ms firefox-l10n-my firefox-l10n-nb-no 
firefox-l10n-ne-np firefox-l10n-nl firefox-l10n-nn-no firefox-l10n-oc 
firefox-l10n-or firefox-l10n-pa-in firefox-l10n-pl firefox-l10n-pt-br 
firefox-l10n-pt-pt firefox-l10n-rm firefox-l10n-ro firefox-l10n-ru 
firefox-l10n-si firefox-l10n-sk firefox-l10n-sl firefox-l10n-son 
firefox-l10n-sq firefox-l10n-sr firefox-l10n-sv-se firefox-l10n-ta 
firefox-l10n-te firefox-l10n-th firefox-l10n-tr firefox-l10n-uk firefox-l10n-ur 
firefox-l10n-uz firefox-l10n-vi firefox-l10n-xh firefox-l10n-zh-cn
 firefox-l10n-zh-tw
Architecture: source
Version: 62.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 
Description:
 firefox- Mozilla Firefox web browser
 firefox-l10n-ach - Acoli language package for Firefox
 firefox-l10n-af - Afrikaans language package for Firefox
 firefox-l10n-all - All lang

Bug#908821: marked as done (firefox-esr: updated version and firefox crasehst at start)

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:23:43 +
with message-id 
and subject line Bug#908396: fixed in firefox 62.0.2-1
has caused the Debian Bug report #908396,
regarding firefox-esr: updated version and firefox crasehst at start
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.)


-- 
908396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: normal

-- Package-specific info:

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.2.12-1~deb9u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-3
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libgtk2.0-02.24.31-2

-- no debconf information

processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 6
model name  : AMD Athlon(tm) XP 1700+
stepping: 2
cpu MHz : 1466.475
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 2932.95
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 6
model name  : AMD Athlon(tm) XP 1700+
stepping: 2
cpu MHz : 1466.475
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 2932.95
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts
--- End Message ---
--- Begin Message ---
Source: firefox
Source-Version: 62.0.2-1

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

A summary of the chan

Bug#908821: marked as done (firefox-esr: updated version and firefox crasehst at start)

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:23:43 +
with message-id 
and subject line Bug#908449: fixed in firefox 62.0.2-1
has caused the Debian Bug report #908449,
regarding firefox-esr: updated version and firefox crasehst at start
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.)


-- 
908449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: normal

-- Package-specific info:

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

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

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.2.12-1~deb9u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-3
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libgtk2.0-02.24.31-2

-- no debconf information

processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 6
model name  : AMD Athlon(tm) XP 1700+
stepping: 2
cpu MHz : 1466.475
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 2932.95
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 6
model name  : AMD Athlon(tm) XP 1700+
stepping: 2
cpu MHz : 1466.475
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow 3dnowprefetch vmmcall
bugs: fxsave_leak sysret_ss_attrs spectre_v1 spectre_v2 
spec_store_bypass
bogomips: 2932.95
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts
--- End Message ---
--- Begin Message ---
Source: firefox
Source-Version: 62.0.2-1

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

A summary of the chan

Bug#908396: marked as done (firefox-esr: stopped working after upgrade from 59 to 60)

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:23:43 +
with message-id 
and subject line Bug#908449: fixed in firefox 62.0.2-1
has caused the Debian Bug report #908449,
regarding firefox-esr: stopped working after upgrade from 59 to 60
to be marked as done.

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

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


-- 
908449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.2.0esr-1~deb9u2
Severity: important

Dear Maintainer,
firefox-esr does not work anymore, crashes immediately even in safe mode:

$ firefox-esr -safe-mode
ExceptionHandler::GenerateDump cloned child 9620
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...

I suspect it's related to my CPU not having sse2 instructions and Firefox
compiled with some flags requiring them.

$ cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 11
model name  : Intel(R) Celeron(TM) CPU1100MHz
stepping: 1
microcode   : 0x1c
cpu MHz : 1365.108
cache size  : 256 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 2
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov 
pse36 mmx fxsr sse
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips: 2730.21
clflush size: 32
cache_alignment : 32
address sizes   : 36 bits physical, 32 bits virtual
power management:


-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (10, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-8-686 (SMP w/1 CPU core)
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 firefox-esr depends on:
ii  debianutils   4.8.1.1
ii  fontconfig2.11.0-6.7+b1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u3
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libdbus-1-3   1.10.26-0+deb9u1
ii  libdbus-glib-1-2  0.108-2
ii  libevent-2.0-52.0.21-stable-3
ii  libffi6   3.2.1-6
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:7.2.0-19
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.40.5-1
ii  libstartup-notification0  0.12-4+b2
ii  libstdc++66.3.0-18+deb9u1
ii  libvpx4   1.6.1-3+deb9u1
ii  libx11-6  2:1.6.4-3
ii  libx11-xcb1   2:1.6.4-3
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.2.12-1~deb9u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
pn  libcanberra0   
ii  libgssapi-krb5-2   1.15-1+deb9u1
ii  libgtk2.0-02.24.31-2

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: firefox
Source-Version: 62.0.2-1

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox package)

(This message was generated automatically at their request; if you
be

Bug#877445: marked as done (Certain sites crash Firefox on pre-SSE2 CPUs)

[Debian Bug Tracking System]

Your message dated Sat, 22 Sep 2018 04:23:43 +
with message-id 
and subject line Bug#877445: fixed in firefox 62.0.2-1
has caused the Debian Bug report #877445,
regarding Certain sites crash Firefox on pre-SSE2 CPUs
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.)


-- 
877445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox
Version: 56.0-2
Severity: important

Visiting certain sites such as github crashes with SIGILL on Pentium
III and other CPUs with no SSE2 support due to some parts of Firefox
code assuming SSE2 unconditionally. While the upstream doesn't support
pre-SSE2 processors anymore, my understanding is that the Debian
package does, and therefore it's a bug. AFAIU the fix shouldn't be too
invasive, because the upstream sources still pretty much *have to*,
and do, contain scalar fallbacks for non-x86 platforms.

The same sites work for the time being in firefox-esr, which is what
I'm using as a workaround.

Top of backtrace after receiving SIGILL:

(gdb) bt
#0  0xb0b2dae3 in _mm_unpacklo_epi64(long long __vector(2), long long
__vector(2)) (__B=..., __A=...)
at /usr/lib/gcc/i686-linux-gnu/7/include/emmintrin.h:1011
#1  mozilla::gfx::UnpremultiplyVector_SSE2 (
aSrc=...)
at /build/firefox-yYj8Vc/firefox-56.0/gfx/2d/SwizzleSSE2.cpp:184
#2  mozilla::gfx::Unpremultiply_SSE2 (
aSrc=0x8dd88b00 "", aSrcGap=944, aDst=0x8ddc4000 "",
aDstGap=0, aSize=...)
at /build/firefox-yYj8Vc/firefox-56.0/gfx/2d/SwizzleSSE2.cpp:227
#3  0xb0b8021a in mozilla::gfx::UnpremultiplyData (
aSrc=0x8dd88b00 "", aSrcStride=1200,
aSrcFormat=mozilla::gfx::SurfaceFormat::B8G8R8A8,
aDst=0x8ddc4000 "", aDstStride=256,
aDstFormat=mozilla::gfx::SurfaceFormat::R8G8B8A8,
aSize=...)
at /build/firefox-yYj8Vc/firefox-56.0/gfx/2d/Swizzle.cpp:416
#4  0xb178a64d in mozilla::dom::CanvasRenderingContext2D::GetImageDataArray (
this=0x90b19000, aCx=0xb7073000, aX=0, aY=16,
aWidth=64, aHeight=1, aRetval=0xbfd5d3a8)
at 
/build/firefox-yYj8Vc/firefox-56.0/dom/canvas/CanvasRenderingContext2D.cpp:5936
#5  0xb178a84a in mozilla::dom::CanvasRenderingContext2D::GetImageData (
this=0x90b19000, aCx=0xb7073000, aSx=0, aSy=16,
aSw=64, aSh=1, aError=...)
at 
/build/firefox-yYj8Vc/firefox-56.0/dom/canvas/CanvasRenderingContext2D.cpp:5839
#6  0xb13a3d7e in mozilla::dom::CanvasRenderingContext2DBinding::getImageData (
cx=0xb7073000, obj=..., self=0x90b19000,
args=...)
at 
/build/firefox-yYj8Vc/firefox-56.0/build-browser/dom/bindings/CanvasRenderingContext2DBinding.cpp:4064
#7  0xb1725c5d in mozilla::dom::GenericBindingMethod (
cx=0xb7073000, argc=, vp=0xa8b84210)
at /build/firefox-yYj8Vc/firefox-56.0/dom/bindings/BindingUtils.cpp:3053
#8  0xb329220c in js::CallJSNative (args=...,
native=0xb1725a80 ,
cx=0xb7073000)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/jscntxtinlines.h:293
#9  js::InternalCallOrConstruct (cx=0xb7073000, args=...,
construct=js::NO_CONSTRUCT)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/vm/Interpreter.cpp:469
#10 0xb3292592 in InternalCall (cx=, args=...)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/vm/Interpreter.cpp:514
#11 0xb3285c6a in js::CallFromStack (args=...,
cx=)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/vm/Interpreter.cpp:520
#12 Interpret (cx=0xb7073000, state=...)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/vm/Interpreter.cpp:3064
#13 0xb3291e8d in js::RunScript (cx=0xb7073000, state=...)
at /build/firefox-yYj8Vc/firefox-56.0/js/src/vm/Interpreter.cpp:409
--- End Message ---
--- Begin Message ---
Source: firefox
Source-Version: 62.0.2-1

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox 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, 22 Sep 2018 09:02:25 +0900
Source: firefox
Binary: firefox firefox-l10n-all firefox-l10n-ach firefox-l10n-

Processed: tagging 909196

[Debian Bug Tracking System]

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

> tags 909196 + buster sid
Bug #909196 [geany-plugin-webhelper] geany: webhelper seems ported to 
webkit2gtk, please reenable it
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#909350: ell FTBFS with kernel 4.18 headers

[Adrian Bunk]

Source: ell
Version: 0.7-1
Severity: serious
Tags: ftbfs

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

...
ell/key.c: In function 'kernel_dh_compute':
ell/key.c:205:38: error: 'struct keyctl_dh_params' has no member named 
'private'; did you mean 'dh_private'?
  struct keyctl_dh_params params = { .private = private,
  ^~~
  dh_private


The suggestion from gcc looks correct to me.

Bug#909352: Is squeak-plugins-scratch still useful?

[Adrian Bunk]

Source: squeak-plugins-scratch
Severity: serious
Tags: buster sid

Bernhard Übelacker noticed in #892016:

<--  snip  -->

When just installing the packages the plugin so.CameraPlugin gets
used from the package squeak-plugins-scratch.
But a similar so.CameraPlugin is already packaged with squeak-vm.

 squeak-vm: /usr/lib/squeak/4.10.2.2614/so.CameraPlugin
squeak-plugins-scratch: /usr/lib/scratch/plugins/so.CameraPlugin

So this probably should be clarified if the plugins are really
needed in both packages.

<--  snip  -->


At first sight I would say that all plugins in squeak-plugins-scratch
are already shipped by squeak-vm, but I might be missing something.