Bug#930348: marked as done (chromium: missing intrinsics on armhf)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2019 05:39:15 +
with message-id 
and subject line Bug#930348: fixed in chromium 75.0.3770.90-1
has caused the Debian Bug report #930348,
regarding chromium: missing intrinsics on armhf
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.)


-- 
930348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:chromium
severity: serious
version: 75.0.3770.80-1

The latest upload fails to build on armhf due to missing intrinsics [0].

Best wishes,
Mike

[0]https://buildd.debian.org/status/fetch.php?pkg=chromium=armhf=75.0.3770.80-1=1560141959=0
--- End Message ---
--- Begin Message ---
Source: chromium
Source-Version: 75.0.3770.90-1

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium 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, 14 Jun 2019 00:10:43 +
Source: chromium
Architecture: source
Version: 75.0.3770.90-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Team 
Changed-By: Michael Gilbert 
Closes: 914886 926032 930348
Changes:
 chromium (75.0.3770.90-1) unstable; urgency=medium
 .
   [ Riku Voipio ]
   * Fix build on armhf (closes: #930348).
 .
   [ Michael Gilbert ]
   * New upstream security release.
 - CVE-2019-5842: Use-after-free in Blink. Reported by BUGFENSE
   * Disable hardware accelerated video (closes: #926032).
   * Fix signedness error when built with gcc (closes: #914886).
 - Thanks to Maciej S. Szmigiero.
Checksums-Sha1:
 4b98b2ce5d44f87ab5eaa6edd1730fbc02d52133 4203 chromium_75.0.3770.90-1.dsc
 e2a3f434a1c7d9cafea1c92a55ceefa851800d0b 249885236 
chromium_75.0.3770.90.orig.tar.xz
 272136d3bce9af91047d71eeb7aa94f143c0c1e4 189628 
chromium_75.0.3770.90-1.debian.tar.xz
 094591cef561fdb5ef1bfb9a372d81157a764226 21207 
chromium_75.0.3770.90-1_source.buildinfo
Checksums-Sha256:
 ae71a4d2639d641b8b8c964673a1e24961469f030a724d88dbcc247d064efb1a 4203 
chromium_75.0.3770.90-1.dsc
 45ef52ec4993dc626bf1676def320a1fa8f418c50d3d500af017c22dbe29805f 249885236 
chromium_75.0.3770.90.orig.tar.xz
 c7ac00401b461d7242215d73598c43f8029db315a82be955b3bc29ce2525 189628 
chromium_75.0.3770.90-1.debian.tar.xz
 59f9bf0496526b826687f500dbe982b699c7ccc6713c3b706579b3ca0c598ebd 21207 
chromium_75.0.3770.90-1_source.buildinfo
Files:
 bcefe95f8c71b961553bceaeca69c676 4203 web optional chromium_75.0.3770.90-1.dsc
 28841d8f923401c863958e815eec118e 249885236 web optional 
chromium_75.0.3770.90.orig.tar.xz
 7806bbe3d6b238a09f31b90509f77daf 189628 web optional 
chromium_75.0.3770.90-1.debian.tar.xz
 dfb8196c5b3ee404b4314526ca029fb5 21207 web optional 
chromium_75.0.3770.90-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEluhy7ASCBulP9FUWuNayzQLW9HMFAl0DLecACgkQuNayzQLW
9HMxWR/+Py2O2dLEvYtgioD9UqLeOYEqrRIexijdUgmDnsBtRG3GtJs60HwuC+aO
fzKqoI6JBAqWSuqeomWeCI9xCFjqjXQ7gU2BuSR0R37v5p7RDVboVO2VjCXSBfvj
1MGkcAjpeOv/fGUvbuBJMUuuoEH0Z766PZ0oYYyY+rmx5sMWqy3BzNkVrigGrJY5
UaB/59v/VA2zWQVyXRtHIwlUmcmCbSSKF9zQoju5o65znMCPLP2wcBMziiQutK1W
VSFbrbwPBtQXK6W40oHS1hPfMTljAXmaMJTvLajyGEjMhbLh50G+zhSFxeW89nPH
6TzgEvSdltW6rlqTAuHpL9Hm2mZTe16WQpKar+lsqjzXYQTnEnWW6+pOBoHtGXZB
C9fQ58PHrA3blYkvulMwTFtzD1BtrgkdRCZKZYLE1hJHgOUfAWL6xpOWCcLIgMpy
cOR1rScTaFcZi/KFHSR01LW4+FXz8tR2pOYa5ZW/aI4us/2vyYHWXOIOtD5+GA7F
rLe3DiChFsk0Bt8l9NysHSO+AJC4J9PkHwuOWSvecgmHeKPPJr8sgO/n+uFLIRSy
t45nr4gL4cA6eUxNrcDxWMQoSCrPp/ghrhgol+OEk+HwLWclfbVu+itbzCY1XNzR
BQHaP5Y3LQeHYorcro9W/0HXGxuXD5+m0p5vbYeDAbZtVdONLtjBfNKMEkMXnjvR
i55lBnpBx6Wt833SC8tMKcuyiZ1FRi9vEDI0SXhcssr+zqAQ17yOW3h+/9JiiPH9
8EfUXxcYhs6tZfcYqYi6eIbPvto09/sQM1WBPgAMtVY3PpI7U68eLD+0Pqo4xUn6
F9rDDL7753qIyyJPJ6Os7/8iSvy0rQQJlttpjt9HBHyp92w+qc95Ja61+6s98apm
SkMQ4Wrg9gwEUHHMwirHcOEbw4vHHub6K15rNYuLTh4jtnl1f5Kp9Spd8iLwr/6z
NviJyxhG0rdXZXNGqgjpR85pCw5c04UZuqJ8wAEKOg2M/LS4+xLD2kzWZcobRmbs
tZHjELzZeJGVY5JETv5B3o+5fMPiQZBlP/EEEIbgGMVR/aC63qD3wK9M22ASkxXt

Bug#923298: marked as done (chromium: file overlap with chromium-sandbox without Conficts and/or Replaces)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jun 2019 23:11:53 -0400
with message-id 

and subject line Re: Bug#923298: chromium: file overlap with chromium-sandbox 
without Conficts and/or Replaces
has caused the Debian Bug report #923298,
regarding chromium: file overlap with chromium-sandbox without Conficts and/or 
Replaces
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.)


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

I have been tracking testing for several months.

This looks to me like a missing or insufficiently versioned Replaces
declaration, but I did not dig deeply into this except to check the BTS
to see if it had bitten anyone else.  To my surprise, it looks like it
has not.

# apt install chromium-sandbox
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  chromium-sandbox
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 137 kB of archives.
After this operation, 851 kB of additional disk space will be used.
Get:1 http://ftp.au.debian.org/debian buster/main amd64 chromium-sandbox amd64 
72.0.3626.53-1 [137 kB]
Fetched 137 kB in 1s (179 kB/s)  
Selecting previously unselected package chromium-sandbox.
(Reading database ... 351969 files and directories currently installed.)
Preparing to unpack .../chromium-sandbox_72.0.3626.53-1_amd64.deb ...
Unpacking chromium-sandbox (72.0.3626.53-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/chromium-sandbox_72.0.3626.53-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/chromium/chrome-sandbox', which is also in 
package chromium 72.0.3626.96-1~deb9u1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/chromium-sandbox_72.0.3626.53-1_amd64.deb

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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.8-1
ii  libatk1.0-0  2.30.0-2
ii  libatomic1   8.2.0-21
ii  libatspi2.0-02.30.0-7
ii  libavcodec57 7:3.2.12-1~deb9u1
ii  libavformat577:3.2.12-1~deb9u1
ii  libavutil55  7:3.2.12-1~deb9u1
ii  libc62.28-7
ii  libcairo21.16.0-2
ii  libcups2 2.2.10-3
ii  libdbus-1-3  1.12.12-1
ii  libdrm2  2.4.97-1
ii  libevent-2.0-5   2.0.21-stable-3
ii  libexpat12.2.6-1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgcc1  1:8.2.0-21
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-7
ii  libglib2.0-0 2.58.3-1
ii  libgtk2.0-0  2.24.32-3
ii  libicu57 57.1-6+deb9u2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.42.1-1
ii  libopenjp2-7 2.3.0-1.1
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpangoft2-1.0-01.42.4-6
ii  libpci3  1:3.5.2-1
ii  libpng16-16  1.6.36-5
ii  libpulse012.2-4
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.2.0-21
ii  libvpx4  1.6.1-3+deb9u1
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux2  0.5.2-1
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+4
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages 

Processed: Re: Bug#930469: chromium: Insta-segfault on start

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #930469 [chromium] chromium: Insta-segfault on start
Added tag(s) moreinfo.

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

Bug#930469: chromium: Insta-segfault on start

[Michael Gilbert]

control: tag -1 moreinfo

On Thu, Jun 13, 2019 at 5:36 AM Guillem Jover wrote:
>   [23609:23609:0613/102304.872428:FATAL:render_process_host_impl.cc(4060)] 
> Check failed: render_process_host->InSameStoragePartition( 
> BrowserContext::GetStoragePartition(browser_context, site_instance, false )).

This is the error.  FATAL errors in chromium intentionally abort
execution.  That output should have also been seen without --debug,
although upstream's handling of FATAL messages can be flaky.

My best guess is that there is an incompatibility with profiles
created before 75.  If you start with --temp-profile, does that avoid
the problem?

Best wishes,
Mike

Bug#930462: marked as done (ERROR: unable to download video data: HTTP Error 403: Forbidden)

[Debian Bug Tracking System]

Your message dated Fri, 14 Jun 2019 00:48:33 +
with message-id 
and subject line Bug#930462: fixed in youtube-dl 2019.06.08-1
has caused the Debian Bug report #930462,
regarding ERROR: unable to download video data: HTTP Error 403: Forbidden
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.)


-- 
930462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: youtube-dl
Version: 2019.01.17-1.1
Severity: grave

Hi,

I get  this error when  trying to download  videos from youtube.  Updating the
package to 2019.06.08 fixes the issue.

Cheers,
Arnaud Fontaine
--- End Message ---
--- Begin Message ---
Source: youtube-dl
Source-Version: 2019.06.08-1

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

Debian distribution maintenance software
pp.
Rogério Brito  (supplier of updated youtube-dl 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: SHA384

Format: 1.8
Date: Thu, 13 Jun 2019 21:24:55 -0300
Source: youtube-dl
Binary: youtube-dl
Architecture: source all
Version: 2019.06.08-1
Distribution: unstable
Urgency: medium
Maintainer: Rogério Brito 
Changed-By: Rogério Brito 
Description:
 youtube-dl - downloader of videos from YouTube and other sites
Closes: 930462
Changes:
 youtube-dl (2019.06.08-1) unstable; urgency=medium
 .
   * ACK NMU. Thanks Antoine and Salvatore for the upload!
   * New upstream version 2019.06.08. Closes: #930462.
   * debian/README.source: Update steps used to create new release.
   * debian/patches:
 + Remove patch cherry-picked from upstream for the NMU.
 + Refresh patches to apply cleanly.
Checksums-Sha1:
 054dd1ffc37975340f03775a7d690e4a05656d53 2274 youtube-dl_2019.06.08-1.dsc
 3c665c7cbf6f58c176cdc19e29df16b7ff63c61a 3169571 
youtube-dl_2019.06.08.orig.tar.gz
 72071ca75c91527fb87f96a8e312023bf67fe8b0 833 
youtube-dl_2019.06.08.orig.tar.gz.asc
 812e4b8b36a08695730615a655c8b8b729d3b0f1 29560 
youtube-dl_2019.06.08-1.debian.tar.xz
 afb9f2dfc3da3210d0c15374e53e152ccf0ca685 1053952 
youtube-dl_2019.06.08-1_all.deb
 e0dd93fc9e4b2fc7057ba148275a6c18e028fe46 6723 
youtube-dl_2019.06.08-1_amd64.buildinfo
Checksums-Sha256:
 3bfe46b68f361062353d7608d9637cbda7bec0af94b68d54496937e1b1ac7cb3 2274 
youtube-dl_2019.06.08-1.dsc
 275a8506ecd6c72589bfc66b749cd80847e7393df1d6e1becd1d11ba90980837 3169571 
youtube-dl_2019.06.08.orig.tar.gz
 6c10c0d4faac67762c3907a17bfdb6d161c2736d6c77df192bc9736ba2637852 833 
youtube-dl_2019.06.08.orig.tar.gz.asc
 0a8cd9cfd4ce841bfa373bd7fb48be87383bca091aa1eba2726f67320f52ae29 29560 
youtube-dl_2019.06.08-1.debian.tar.xz
 71577dc4ca997f6bc93b7b488851705dd7bf655b3de1770e6cdf265bd49a8239 1053952 
youtube-dl_2019.06.08-1_all.deb
 1a4bb2a646179e6a6e14a9546763ab8aa022ca215be8b55c228ed18e5b5bcfac 6723 
youtube-dl_2019.06.08-1_amd64.buildinfo
Files:
 787a2b1625d1316d6eabefee2a616a02 2274 web optional youtube-dl_2019.06.08-1.dsc
 b2ae5875d91e9100233d11e9e4fa7649 3169571 web optional 
youtube-dl_2019.06.08.orig.tar.gz
 a2124d4b4722faebe1d07ebf3633b1a2 833 web optional 
youtube-dl_2019.06.08.orig.tar.gz.asc
 e06e9324f8588fb80ca168be3cf01745 29560 web optional 
youtube-dl_2019.06.08-1.debian.tar.xz
 906f3c416c11c8189c01222f08698480 1053952 web optional 
youtube-dl_2019.06.08-1_all.deb
 de1ccea688397babbb051d3bcf18904b 6723 web optional 
youtube-dl_2019.06.08-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEj5ML0ZNMPiFAolh5B0e9Obz8qqoFAl0C6dkACgkQB0e9Obz8
qqqi8A//ZjniycRh9nJsgaQZZ6PkAkiuVSSVRHP9JAd9J8+tjpaObHJYilQc48Tu
+khKKHE48UPm70j4/UJZQx+I+yevl39nB7xETlUPG1oFmR7HPfMHDFLvQDUHiRry
uIY5V5k/CW6UkVmxJTLzbQKkrxsDbtte8lhEkAjH4J6O5+q+UuPaFLTgrYl6agI1
1Bj1ceazjSc7Uu+m1krmfJpEFRrjc8Mxb3+tI122FlHaETHKMq4RdObI6sM3jF74
r5sa+PQS8yvgQUddtfQbz+Khhz873yZ8wE5wyQ6tU6TkxWF7cTly94YHfmsGula/
8HGORQVw4rjzYdJuF8NAQhYCddfE7Oyns59GjzlBFe46LOijaW5JyiukfJhG6N8l
v19QBsSTcpaWdm54D7alBWROW9lBRKrANFMpUiW8NQpc7UmOHhOZga+b/hawc2/b
s6jCK/2nXnVcgw8yvfm3ol3ZosN+TV/5NpXKfdRejtKwXu9oaEFRFcjeCgy3664+
3pSbH9ABouU+hgB4lWavELroqPguHD+yh3OgHQpv/DtnNwrFmoWE8zDYVMga9eQ4

Bug#916610: marked as done (spacenavd: conflict with /dev/input/js0)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jun 2019 20:41:23 +
with message-id 
and subject line Bug#916610: fixed in spacenavd 0.6-1.1
has caused the Debian Bug report #916610,
regarding spacenavd: conflict with /dev/input/js0
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.)


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

Dear Maintainer,


While everything works on older kernels (like 4.9) spacenavd
stopped working with latest kernels (like 4.18). Problem
is present on Debian 9 with backported kernel and Debian 10
that has 4.18 kernel by default.

In SystemD logs I see spacenavd complaining about inability
to turn led on. Blender does not respond to 3D mouse either.

If I manually delete joystick file:

  sudo rm /dev/input/js0

And restart spacenavd service, led turns on and navigation
works in Blender.

I suspect that latest kernel detects space navigator
mouse successfully as joystick (and Joystick test program
jstest-gtk successfully displays 3D mouse movements!)
and because of that spacenavd either is blocked from
3D mouse or attaches itself to /dev/input/js0 and
it causes spacenavd to malfunction.




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

Kernel: Linux 4.18.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:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages spacenavd depends on:
ii  init-system-helpers  1.56
ii  libc62.28-2
ii  libx11-6 2:1.6.7-1

spacenavd recommends no packages.

spacenavd suggests no packages.

-- Configuration Files:
/etc/init.d/spacenavd [Errno 2] No such file or directory: 
'/etc/init.d/spacenavd'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: spacenavd
Source-Version: 0.6-1.1

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

Debian distribution maintenance software
pp.
Jakob Haufe  (supplier of updated spacenavd 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, 01 Jun 2019 11:13:33 +
Source: spacenavd
Architecture: source
Version: 0.6-1.1
Distribution: unstable
Urgency: medium
Maintainer: Rodolphe PELLOUX-PRAYER 
Changed-By: Jakob Haufe 
Closes: 916610
Changes:
 spacenavd (0.6-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "conflict with /dev/input/js0" (Closes: #916610)
 - Fixed upstream in 34ddda1246ad07e8ff2e6606224e710852e3e3d8
Checksums-Sha1:
 9271d376c95d1899a9d71e7d2c2a03aa8f521b40 1866 spacenavd_0.6-1.1.dsc
 6e8d37b3628c2c19bdeb431acc2f22fc4b1957e3 6676 spacenavd_0.6-1.1.debian.tar.xz
Checksums-Sha256:
 5051a0a0f60d0ea87d57ce6d3f381a6f95af46e0066fff85e2aa36d9b05322a0 1866 
spacenavd_0.6-1.1.dsc
 ab1a778ebc4d88f300eb67ed15ff9120bfe961b5840483fffea0e0fc6cc61d25 6676 
spacenavd_0.6-1.1.debian.tar.xz
Files:
 d6702df293a0ce2b191541c3e4620fec 1866 utils optional spacenavd_0.6-1.1.dsc
 15c24cc88a3e5eb15eb896b8312b102e 6676 utils optional 
spacenavd_0.6-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAlz1eZsACgkQafL8UW6n
GZOJlBAAlW3aGuvYqedHHynFLgaBXhggyGMkwV4uCxy5IwtWAvT0GS9oXhYZLYU8
avlsA+ajpOAv/EwLL0JvFLEQGbxQheBPSvSgWZQYq7hn1W2oGudzBlHGqBXXOdZ+
n9oC7gsqY7aIK8+X2oIXDWKNx9UzI9OFfaPjyPIBBL8mPqLmWa1M1pnvj5OY8Wx8
hNshCAG7AV3Gt/04h5H5rNZQfENGBw5zA2CIshjEorX2PTyk2enUBOXCi/FSawxP
PBf6AuJgCHSncxDsSZm2tXtX9ckhyARBom66T8VdifPNyK6oHuV39iRPXGOH/2qc
2BmC8zXxLy5Mwhl7SMQXV4QbBQOYxCMZxFKHuadSi3RG3SFBjHrvfRcBsDC285O+
+8tIzCZcbTclOG38sY7HC+tUfYMtwi4xv2FJKHR6BNWVijlJOhZuDk05xWZqFbsV
7/uCCOzTqN8p8BqDRtHkLG2cKT/Ts2vRlVPeHITOoKvd+MkKUTjgw7YxVzbHwmvb
nZp6y2Cj2opSSRWYTUpaSpDHQp8q16nzpFUcfIuntX29Px6F8k0kuc8uaxOidcjr
9Kft5Vhy/KYGaTposFSjisvaJuwCkxzQB8mfcTBLqLgX4Z46YYoAqrsWQn5GM+mk

Processed: Re: Bug#930484: e2fsck corrupts sparse files with -E bmap2extent

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #930484 [e2fsprogs] e2fsck corrupts sparse files with -E bmap2extent
Severity set to 'normal' from 'critical'
> fixed -1 1.43.5-1
Bug #930484 [e2fsprogs] e2fsck corrupts sparse files with -E bmap2extent
Marked as fixed in versions e2fsprogs/1.43.5-1.

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

Bug#930484: e2fsck corrupts sparse files with -E bmap2extent

[Theodore Ts'o]

Control: severity -1 normal
Control: fixed -1 1.43.5-1

On Thu, Jun 13, 2019 at 04:09:15PM +0200, Florian Zumbiehl wrote:
> Package: e2fsprogs
> Version: 1.43.4-2
> Severity: critical
> 
> e2fsck potentially moves blocks around in sparse files when running with
> -E bmap2extent, in particular when the blocks are physically adjacent on
> the underlying block device, but have a hole in between in the file.
> ...
>
> With version 1.44.5-1~bpo9+1, the test above does not produce corruption on
> my system, but I have not investigated whether that is just coincidence or
> because the bug has been fixed. As this silently corrupts files, I would
> think it should get some fix in stretch, and be it by disabling the
> feature.

The bug was fixed in e2fsprogs 1.43.5, via the fix:

commit 855c2ecb21d1556c26d61df9b014e1c79dbbc956
Author: Darrick J. Wong 
Date:   Wed May 24 21:56:36 2017 -0400

e2fsck: fix sparse bmap to extent conversion

When e2fsck is trying to convert a sparse block-mapped file to an extent
file, we incorrectly merge block mappings that are physically contiguous
but not logically contiguous because of insufficient checking with the
extent we're constructing.  Therefore, compare the logical offsets for
contiguity as well.

Signed-off-by: Darrick J. Wong 
Signed-off-by: Theodore Ts'o 

It's an unfortunate bug, but we've lived with it for about ten years,
and it was only noticed in 2017.  The reality is very few people
actually try to convert an indirect mapped file system the new
extent-mapped system, because you get much more of the benefits of
using a more modern version of ext4 by doing a backup, reformat, and
restore of the file system.

Given that so few people have noticed, I don't believe this qualifies
as even "important", since doing the conversion is not a fundamental
aspect of e2fsck, so it doesn't qualify as a significant impact on the
usability of the package.  For similar reasons, I don't believe the
release team would agree to a new release of e2fsprogs to stretch ---
especially since (a) it's fixed in buster, (b) the fix is also
available in stretch-backports, and (c) in three weeks, Stretch will
become oldstable and Buster will become the new stable release of
Debian.

Feel free to escalate this to the Debain release team but I don't
think this is going to be considered worth their time (or mine) to be
worth a backport of the fix to e2fsprogs 1.43.4-2.

Cheers,

- Ted

Processed: [bts-link] source package src:django-prometheus

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:django-prometheus
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #918418 (http://bugs.debian.org/918418)
> # Bug title: django-prometheus FTBFS: test failures
> #  * https://github.com/korfuri/django-prometheus/issues/83
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 918418 + fixed-upstream
Bug #918418 [src:django-prometheus] django-prometheus FTBFS: test failures
Added tag(s) fixed-upstream.
> usertags 918418 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 918418 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package systemd

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package systemd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #929469 (http://bugs.debian.org/929469)
> # Bug title: systemd-networkd: fails with "could not set address: Permission 
> denied"
> #  * https://github.com/systemd/systemd/issues/12656
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 929469 + fixed-upstream
Bug #929469 [systemd] systemd-networkd: fails with "could not set address: 
Permission denied"
Added tag(s) fixed-upstream.
> usertags 929469 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 929469 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: fixed 930375 in 1.10.28-0+deb9u1

[Debian Bug Tracking System]

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

> # upcoming version in DSA
> fixed 930375 1.10.28-0+deb9u1
Bug #930375 {Done: Simon McVittie } [libdbus-1-3] 
CVE-2019-12749: DBusServer DBUS_COOKIE_SHA1 authentication bypass
There is no source info for the package 'libdbus-1-3' at version 
'1.10.28-0+deb9u1' with architecture ''
Unable to make a source version for version '1.10.28-0+deb9u1'
Marked as fixed in versions 1.10.28-0+deb9u1.
> thanks
Stopping processing here.

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

Bug#930464: marked as done (mednafen: PS1 emulation regression)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jun 2019 19:18:47 +
with message-id 
and subject line Bug#930464: fixed in mednafen 1.22.1+dfsg-2
has caused the Debian Bug report #930464,
regarding mednafen: PS1 emulation regression
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.)


-- 
930464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mednafen
Version: 1.22.1+dfsg-1
Severity: serious
Tags: patch
Justification: regression

Dear Maintainer,

Upstream fixed a PS1 regression in 1.22.2; in 1.22.1, a few games are
unplayable (SimCity 2000 and Rise 2 for example). The attached patch
fixes this.

Regards,

Stephen


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

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

Versions of packages mednafen depends on:
ii  libasound21.1.3-5
ii  libc6 2.24-11+deb9u4
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.10+20150825git1ed50c92~dfsg-5
ii  libmpcdec62:0.1~r495-1+b1
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libsndfile1   1.0.27-3
ii  libstdc++66.3.0-18+deb9u1
ii  libtrio2  1.16+dfsg1-3+b2
ii  libvorbisidec11.0.2+svn18153-1+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages mednafen recommends:
ii  mednaffe  0.8.4-1+b1

mednafen suggests no packages.

-- no debconf information
--- a/src/psx/cdc.cpp
+++ b/src/psx/cdc.cpp
@@ -1874,7 +1874,7 @@
 
   if(CommandLoc_Dirty)
SeekTarget = CommandLoc;
-  else
+  else if(DriveStatus != DS_PAUSED && DriveStatus != DS_STANDBY)
SeekTarget = CurSector;
 
   PSRCounter = 33868800 / (75 * ((Mode & MODE_SPEED) ? 2 : 1)) + 
CalcSeekTime(CurSector, SeekTarget, DriveStatus != DS_STOPPED, DriveStatus == 
DS_PAUSED);
--- End Message ---
--- Begin Message ---
Source: mednafen
Source-Version: 1.22.1+dfsg-2

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated mednafen 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, 13 Jun 2019 21:06:02 +0200
Source: mednafen
Binary: mednafen
Architecture: source
Version: 1.22.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Stephen Kitt 
Description:
 mednafen   - multi-platform emulator, including NES, GB/A, Lynx, PC Engine
Closes: 930463 930464
Changes:
 mednafen (1.22.1+dfsg-2) unstable; urgency=medium
 .
   * Apply upstream patch to fix unchecked memory accesses in the Lynx
 emulator. Closes: #930463.
   * Apply upstream patch to fix a regression in the PlayStation emulator,
 which rendered games such as SimCity 2000 and Rise 2 unplayable.
 Closes: #930464.
Checksums-Sha1:
 6f50753b4140d8696c4c4fe1a297a800d72f87b4 2212 mednafen_1.22.1+dfsg-2.dsc
 6fc9bea2f0f3e91e0e1afbf92d91f258b00d2e24 13724 
mednafen_1.22.1+dfsg-2.debian.tar.xz
 427c42f98450331fe473a2e65311e4c32c5d8b85 12060 
mednafen_1.22.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 0a0476bb8f4132d36726763662b5e479bf61ad068bee51192f410605c5327d87 2212 
mednafen_1.22.1+dfsg-2.dsc
 255602a9dcf0fe1115c8de8502aa654d5f926310cffda77b6abcbdc3500a31d3 13724 
mednafen_1.22.1+dfsg-2.debian.tar.xz
 96d505e151660ecedc5abd58f3659f64ec2d8292b845f5cf39c70e5d8420 12060 
mednafen_1.22.1+dfsg-2_source.buildinfo
Files:
 7211aec3a84839ad4c5804c58ca07c86 2212 games optional 

Bug#930463: marked as done (mednafen: potential unchecked memory access in the Lynx emulator)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jun 2019 19:18:47 +
with message-id 
and subject line Bug#930463: fixed in mednafen 1.22.1+dfsg-2
has caused the Debian Bug report #930463,
regarding mednafen: potential unchecked memory access in the Lynx emulator
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.)


-- 
930463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mednafen
Version: 0.9.41+dfsg-2+b1
Severity: serious
Tags: patch security
Justification: security

Dear Maintainer,

(Note for the security team: this has been published in the 1.22.2
upstream release. I’m not aware of any exploit for this issue. This is
qualified as a potential security issue by upstream, hence the
“serious” severity rather than grave. The patch applies to both the
Stretch and Buster versions.)

Upstream fixed a potential unchecked memory access in the Lynx
emulator in the latest release of Mednafen; the attached patch fixes
it.

Regards,

Stephen


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

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

Versions of packages mednafen depends on:
ii  libasound21.1.3-5
ii  libc6 2.24-11+deb9u4
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.10+20150825git1ed50c92~dfsg-5
ii  libmpcdec62:0.1~r495-1+b1
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libsndfile1   1.0.27-3
ii  libstdc++66.3.0-18+deb9u1
ii  libtrio2  1.16+dfsg1-3+b2
ii  libvorbisidec11.0.2+svn18153-1+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages mednafen recommends:
ii  mednaffe  0.8.4-1+b1

mednafen suggests no packages.

-- no debconf information
diff -rupN 1.22.1/src/lynx/ram.h 1.22.2/src/lynx/ram.h
--- 1.22.1/src/lynx/ram.h   2019-01-27 22:52:37.0 -0800
+++ 1.22.2/src/lynx/ram.h   2019-04-23 14:54:58.0 -0700
@@ -65,8 +65,8 @@ class CRam : public CLynxBase
 
voidReset(void) MDFN_COLD;
 
-   voidPoke(uint32 addr, uint8 data){ mRamData[addr]=data;};
-   uint8   Peek(uint32 addr){ return(mRamData[addr]);};
+   voidPoke(uint32 addr, uint8 data){ 
mRamData[(uint16)addr]=data;};
+   uint8   Peek(uint32 addr){ return(mRamData[(uint16)addr]);};
uint32  ReadCycle(void) {return 5;};
uint32  WriteCycle(void) {return 5;};
uint32   ObjectSize(void) {return RAM_SIZE;};
diff -rupN 1.22.1/src/lynx/susie.cpp 1.22.2/src/lynx/susie.cpp
--- 1.22.1/src/lynx/susie.cpp   2019-01-27 22:52:37.0 -0800
+++ 1.22.2/src/lynx/susie.cpp   2019-04-23 14:54:58.0 -0700
@@ -58,13 +58,9 @@
 // wa can access this directly without the hassle of
 // going through the system object, much faster
 //
-//#define RAM_PEEK(m)  (mSystem.Peek_RAM((m)))
-//#define RAM_POKE(m1,m2)  (mSystem.Poke_RAM((m1),(m2)))
-//#define RAM_PEEKW(m) (mSystem.PeekW_RAM((m)))
-
-#define RAM_PEEK(m)(mRamPointer[(m)])
-#define RAM_PEEKW(m)   
(mRamPointer[(m)]+(mRamPointer[(m)+1]<<8))
-#define RAM_POKE(m1,m2){mRamPointer[(m1)]=(m2);}
+#define RAM_PEEK(m)(mRamPointer[(uint16)(m)])
+#define RAM_PEEKW(m)   
(mRamPointer[(uint16)(m)]+(mRamPointer[(uint16)((m)+1)]<<8))
+#define RAM_POKE(m1,m2)
{mRamPointer[(uint16)(m1)]=(m2);}
 
 uint32 cycles_used=0;
 
@@ -838,7 +834,7 @@ uint32 CSusie::PaintSprites(void)
 
 INLINE void CSusie::WritePixel(uint32 hoff,uint32 pixel)
 {
-uint32 scr_addr=mLineBaseAddress+(hoff/2);
+const uint16 scr_addr=mLineBaseAddress+(hoff/2);
 
 uint8 dest=RAM_PEEK(scr_addr);
 if(!(hoff&0x01))
@@ -861,7 +857,7 @@ INLINE void CSusie::WritePixel(uint32 ho
 
 INLINE uint32 CSusie::ReadPixel(uint32 hoff)
 {
-uint32 scr_addr=mLineBaseAddress+(hoff/2);

Bug#929450: caml-crush, build-dependencies unsatisfiable on armel

[Peter Green]

On 13/06/19 10:00, Thomas Calderon wrote:

Hi there,

It's unfortunate that OCaml has removed the support for ocamlopt for armel, it 
sounds like CamlCrush will not be able to ship for armel.
Is it required that I create an updated Debian release excluding armel as a 
target or as you said, ftpmaster can just remove the binaries?

Removing the binaries is enough in cases like this, they won't be rebuilt 
until/unless their build-dependencies become available again.

I'm not sure if the binary removal will propagate automatically from unstable 
to testing during the freeze or if one needs to ask the release team for that.

Bug#912916: Bible Yes, Constitution No! 03-21-53

[santos]

это единственный шанс для вознесения церкви, СЛУЖЕНИЯ восстановления.
https://youtu.be/gfpUwOnpwlM
 

Поколение Иисуса Христа



The voice of restoration, the last entry for the rapture of the disciples of 
Jesus Christ.
2070 Jesus returns
 
 

 74830016

Bug#919216: marked as done (lrslib: Tree truncated at depth -1 on i386)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jun 2019 13:47:00 -0300
with message-id <87y325v3ej@tethera.net>
and subject line closing as suggested
has caused the Debian Bug report #919216,
regarding lrslib: Tree truncated at depth -1 on i386
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Control: fixed -1 0.70-2

On i386, I tried 3 or for sample ine files from the source and each
one terminated after reporting a single basis. Sample run follows.


(unstable-i386-sbuild)bremner@convex:~/lrslib/ine/cocoa13$ lrs bv8.ine 

*lrs:lrslib v.6.2 2016.3.28(64bit,lrsgmp.h gmp v.6.1)
*Copyright (C) 1995,2016, David Avis   a...@cs.mcgill.ca 
*Input taken from file bv8.ine
V-representation
begin
* 73 rational
 1  0  0  0  0  0  0  0  1  0  0  0  0  0  0  1  0  0  0  0  0  0  1  0  0  0  
0  0  0  1  0  0  0  0  0  0  1  0  0  0  0  0  0  1  0  0  0  0  0  0  1  0  0 
 0  0  0  0  1  0  0  0  0  0  0  0  1  2  3  4  5  6  7  8 
V#1 R#0 B#1 h=0 facets  24 25 26 27 28 29 32 33 34 35 36 39 40 41 42 43 46 47 
48 49 50 53 54 55 56 57 60 61 62 63 64 67 68 69 70 71 74 75 76 77 78 79 81 82 
83 84 85 86 87 I#56 det= 1  in_det= 1  z= 0 
end
*Tree truncated at depth -1
*Totals: vertices=1 rays=0 bases=1 integer_vertices=1 
*Dictionary Cache: max size= 1 misses= 1/1   Tree Depth= 0
*lrs:lrslib v.6.2 2016.3.28(64bit,lrsgmp.h)
*0.017u 0.000s 1692Kb 0 flts 0 swaps 32 blks-in 0 blks-out 

I'm not sure this is really worth debugging, as it seems fixed in the
version in experimental.


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

Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lrslib depends on:
ii  libc6 2.28-2
ii  libgmp10  2:6.1.2+dfsg-4
ii  liblrs0   0.70-1

lrslib recommends no packages.

lrslib suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlw7Z+oACgkQ8gKXHaSn
niy2GAwAkfkrEq2++ySRFA82ydX6vvvLSexbCpn/h+UFwdxOZYtV4kgDwZDBrHww
0W5PZrbKTvMNiVQCDW7lqdKlgEofiiaTRCQunosM2biSQYhpoX+fDjf5SkrDArUL
nuwbnr1ue9af0HvVXHiKpRuNONiJ/6JeIwxhceXS89AM1SJrjhMrePIkVtnjvtkL
r+npIlckY5ToGWpuXay5BJ6wTpZGuoWQkSffGPbRB84efQTfayd76xDRSPOhv2SA
wl9aye1mxESVztZZYXDsNasuBpKpHdqM9TQsMG8uTpLin1p6CNvLhwITfyaUgooG
zzDY/cSu2+huzvLvLjmoaqevw5v09n1/HjIrk1a0Qf6seFN++apogXt25B1i1Wg+
kSKvFC0h9QUcYzpI5mn6Rf91RsQD/N4a5q+MqaHG9HLy2r/FnroFAYwxnqVEJXGl
ctHQPVT7QAvBjzhuomJG3IDoVW2xCFROf0S/tP1M7eU8B1Dn6HWcb2qCyHJxRZla
qkhPA1eg
=wiBa
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 8684--- End Message ---

Bug#929451: marked as done (spurious crashes with “vertex shader lacks main()” on i965)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jun 2019 16:33:47 +
with message-id 
and subject line Bug#929451: fixed in nageru 1.8.4-1+buster1
has caused the Debian Bug report #929451,
regarding spurious crashes with “vertex shader lacks main()” on i965
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.)


-- 
929451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgl1-mesa-dri
Version: 18.3.4-2
Severity: important

Hi,

I've got a problem that essentially breaks Nageru on my Haswell laptop;
if you try to link a GLSL program twice (to get a new program number for it),
the second attempt fails with

  Error linking program: error: vertex shader lacks `main'

This fails with libgl1-mesa-dri from testing _only_ (both unstable
and experimental are fine), and even more interesting; if I recompile
mesa 18.3.4-2 myself with zero changes and install the resulting
libgl1-mesa-dri package, the problem goes away! So either the build
was made on a broken machine, or something in unstable has changed
in the meantime.

So, please binNMU libgl1-mesa-dri for at least amd64, since this is
likely to break a fair amount of applications.

-- Package-specific info:
glxinfo:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_no_error, 
GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_no_config_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context, 
GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, 
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) Haswell Mobile  (0xa16)
Version: 18.3.4
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.4
OpenGL core profile shading language version string: 4.50
OpenGL core profile 

Bug#930484: e2fsck corrupts sparse files with -E bmap2extent

[Florian Zumbiehl]

Package: e2fsprogs
Version: 1.43.4-2
Severity: critical

e2fsck potentially moves blocks around in sparse files when running with
-E bmap2extent, in particular when the blocks are physically adjacent on
the underlying block device, but have a hole in between in the file.

This script reproduces the problem on my system (run as root in an empty
directory!):

#!/bin/bash -ex
rm -f image
mkdir -p m
umount m || true
dd if=/dev/zero bs=1M seek=99 count=1 of=image
mkfs.ext3 -E nodiscard -b 4096 image
mount -o loop image m
echo -n a > m/x
echo -n b | dd of=m/x bs=1 seek=8k
ls -i m/x
ino=$(stat -c%i m/x)
sha1sum m/x
umount m
debugfs image -R "stat <$ino>" | cat
tune2fs -O extent image
e2fsck -fE bmap2extent image || true
debugfs image -R "stat <$ino>" | cat
mount -o loop image m
sha1sum m/x
umount m
rm image
rmdir m

The e2fsck invocation turns this part of the debugfs output:

BLOCKS:
(0):24576, (2):24577

into this:

EXTENTS:
(0-1):24576-24577

With version 1.44.5-1~bpo9+1, the test above does not produce corruption on
my system, but I have not investigated whether that is just coincidence or
because the bug has been fixed. As this silently corrupts files, I would
think it should get some fix in stretch, and be it by disabling the
feature.

Bug#930426: marked as done (gokey: Output of gokey is not deterministic any more)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jun 2019 14:35:02 +
with message-id 
and subject line Bug#930426: fixed in gokey 
0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2
has caused the Debian Bug report #930426,
regarding gokey: Output of gokey is not deterministic any more
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.)


-- 
930426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gokey
Version: 0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Hi,

Currently the output of gokey is not deterministic any more and
therefore renders it completely useless. This was fixed in gokey
0.0~git20190103.40eba7e-1 by upstream:

  - Import deterministic RSA key generation code from Go 1.10
crypto/rsa package

Please either upgrade to 0.0~git20190103.40eba7e or cherry-pick the
relevant change.

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany
E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de

Head Office: Berlin, Germany
District Court Berlin Charlottenburg, Registration number: HRB 125506 B
Executive Management: Christoph Steffens, Matthias Steinberg, Achim
Weiss

Member of United Internet
--- End Message ---
--- Begin Message ---
Source: gokey
Source-Version: 0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated gokey 
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, 13 Jun 2019 15:51:37 +0200
Source: gokey
Architecture: source
Version: 0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Benjamin Drung 
Closes: 930426
Changes:
 gokey (0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2) unstable; 
urgency=medium
 .
   * Cherry-pick patch from upstream to import deterministic RSA key generation
 code from Go 1.10 crypto/rsa package (Closes: #930426)
Checksums-Sha1:
 f4d4c4e5a6ace88b5c3bbd5dc55c3850da2e9491 2488 
gokey_0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2.dsc
 23a1128b25f58aea4d5a3352ea9ee9107ed3c16a 10192 
gokey_0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2.debian.tar.xz
 2288f3a294663bed35e0c7fd60223ecacf3c3080 6721 
gokey_0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2_source.buildinfo
Checksums-Sha256:
 1e247f3a43fa788ef2f29ed5b8f000aca4a5a188e75c12eeed0b45607e580976 2488 
gokey_0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2.dsc
 0a85d7b7853edd4a9d51607fddb8b35a5d1b6ac2837cca3c42d7ba5ddd45ceac 10192 
gokey_0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2.debian.tar.xz
 8c8513ec8a23d45ea0f2def89cbede871078854de97002441772ed8c18014397 6721 
gokey_0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2_source.buildinfo
Files:
 123478f4bfa3d16cbaa8a87a1db07275 2488 utils optional 
gokey_0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2.dsc
 9c8c9c00f69af0625b95ca1d92272b12 10192 utils optional 
gokey_0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2.debian.tar.xz
 3220ea492abd8bb0181d1fe23ec841be 6721 utils optional 
gokey_0.0~git20190103.40eba7e+really0.0~git20181023.b4e2780-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE5/q3CzlQJ15towl13YzVpd6MfnoFAl0CVbsACgkQ3YzVpd6M
fnrqaA/5AYzxHWiofmmjXQjK11ujBIkd6cFDSGdzMVjCzSollu1j/DAuxz7BvPY5
vjRJHx5ZlS7cH/ytsUgOc6K4nHhVYSyM0aVZmpI8IvRNLuTeIINZlSaQnniO8Wk/
duSz77B5HuIsJz4RUb6NOl/YiZoY8FsCg8+Nti5Cq9tzG6H0EaD8q0aT0kUyJo64
5UYI9EnqRt1kvfuDPvSZ/GbtQz+bDe2bYxeKMf3q66vY2cZyXTB9TSe/+mws/UOC
kyg7yXX73h6aaO+lDVSy3DndB5XCvHqTF0z7uVmfNbVoVcSBcAD+vmpAJ5buM3x3
d7CaUJv9bg2QtiPny/l4odLerxM8DzlQm+zFmOMJDxbLNRpUjnPERIOZyn8xBxZR
kVHYuLCp1nr6DerJwotLB7WB56L4m3E8Vg0cRqHuK20T4EQvIw2veka0W13TCiFI

Bug#899307: ruby-sequel-pg: All SELECT ::Dataset methods fails with FrozenError

[Andrey Nikitin]

В Wed, 12 Jun 2019 15:45:30 -0700
Joseph Herlant  пишет:

> Can you try to reproduce it with your current version of packages and
> let us know if you still see the issue please?

Hi.

Currently, the problem is not happens in Buster,
it disappeared with some updates.

P.S. But the problem remained in Ubuntu 18.04 :)
Solution: apt-get purge ruby-sequel-pg

Bug#929929: marked as done (Being unable to build with >= 4.19.38 is an RC)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jun 2019 13:03:50 +
with message-id 
and subject line Bug#929929: fixed in zfs-linux 0.7.12-2+deb10u1
has caused the Debian Bug report #929929,
regarding Being unable to build with >= 4.19.38 is an RC
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.)


-- 
929929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zfs-linux
Version: 0.7.12-2
Severity: grave
Clarification: a foreseeable stable RC is grave enough.

Buster will be released with 4.19.37 kernel. That's fine
and it doesn't break ZFS. However, the changes introduced
in 4.19.38 and linux 5.0 break ZFS. That means the current
0.7.12-2 will fail to build everywhere after the first
Buster point release (with kernel version bump).
RC in stable is terrible enough.

We have two choices:
1. just unblock 0.7.13-1 .
2. revert diff(0.7.12-2,0.7.12-5), then cherry-pick
   the commits that fix the build issue, then go
   through t-p-u for 0.7.12-6 .

I dislike the second one but the first one seems hard
to achieve. Sigh.
--- End Message ---
--- Begin Message ---
Source: zfs-linux
Source-Version: 0.7.12-2+deb10u1

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated zfs-linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 09 Jun 2019 03:17:40 +
Source: zfs-linux
Architecture: source
Version: 0.7.12-2+deb10u1
Distribution: testing-proposed-updates
Urgency: high
Maintainer: Debian ZFS on Linux maintainers 

Changed-By: Mo Zhou 
Closes: 929929
Changes:
 zfs-linux (0.7.12-2+deb10u1) testing-proposed-updates; urgency=high
 .
   * Patch: Disable SIMD on 4.19.37+ or 5.0+ kernels. (Closes: #929929)
Checksums-Sha1:
 936e7636f4d225e8b548706360ef4872cb78ec8a 3089 zfs-linux_0.7.12-2+deb10u1.dsc
 1aa92e1f8049d502ca95706f1d805713fea39618 45292 
zfs-linux_0.7.12-2+deb10u1.debian.tar.xz
 9338c6418dc5aac50a920107c890762b92c6831a 6638 
zfs-linux_0.7.12-2+deb10u1_source.buildinfo
Checksums-Sha256:
 9480c2216bb1c82e31acc7df980ca7c2cb8ef4d288651c220f163be054fc8e03 3089 
zfs-linux_0.7.12-2+deb10u1.dsc
 a49da8783b82a2485bacb592b0fde463cad710bda0ae6aefa775492e3871b34f 45292 
zfs-linux_0.7.12-2+deb10u1.debian.tar.xz
 b51e5ffbd673719b2bf67fc5f62b1a1af2ed323cc5b1185e10d5bca8571c599c 6638 
zfs-linux_0.7.12-2+deb10u1_source.buildinfo
Files:
 6186ac90587afdfcf869352baac1b134 3089 contrib/kernel optional 
zfs-linux_0.7.12-2+deb10u1.dsc
 60d49849b00b646c22577d6bd3ecb4f4 45292 contrib/kernel optional 
zfs-linux_0.7.12-2+deb10u1.debian.tar.xz
 97b029aec4aaefd76677b92447c44723 6638 contrib/kernel optional 
zfs-linux_0.7.12-2+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAlz8e+UACgkQYmRes19o
aopjqw/9Fhumuq0Z4EevGSlDFYgxM6gM5kv6lcQinM1huNOJmQOZtJskiFso3JNp
oFz4E8KhXJ6/LnM4L3Q6m5yu3XWS7ps5/zIKWltj+6amTadvuHLFjOeEaymMUoCY
L70DTnt7NtjY4ofyqFNDNXn9juFNVkkJqP4vntBVWThw7mQHsxHMxHeZuv9J+HSg
vrMeXuJiCutRb8oZlbJIg2GFs8kFOOea9Oomkkd38wkYMGrYvBL5CIaAPvqVFoVV
sA55Wu2Nre6jGeGGHYU2b234M1kmpCdCIlVIaCUjqm4yheFUWKP19V33aveSkYie
vklBZdlOYZCocfJ2VBhC3VuPrp8atvfCrug1Ty2OYu8zAaeSaXM+14Lm86aDNDAz
DSNp5bQvJ4c/d4kTi5+C2tVHwbsfihkXgR9Nmcks0mwZm3QjB+To3Tbo803yEjam
tquLmkM580EwLw9E0zYxhROSAtKnpsX+6CF06eFRvv1a42YRj48rWx+hs3uWi9J/
4spL4/G+1XdXoFThLychX30XI6CkJsJewQKMfdW+zrxFW5sI/YL/R7/XIX1J91TC
UmlOkHIsq89oiENi1qu+8d1BAWwscpfDXY9ZOKouWVSH26IiKeJxHZsrxXgHb4FN
x2+PmuP2l3jXYKs1l2n3Xv4UvokYoRukdbBG+o2XsJMO3Z4z0S0=
=l8UG
-END PGP SIGNATURE End Message ---

Processed: severity of 930439 is grave

[Debian Bug Tracking System]

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

> severity 930439 grave
Bug #930439 {Done: Xavier Guimard } [node-chart.js] gitlab's 
webpack is failing to find node-chartjs
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: retitle 930439 to node-chart.js is unusable because Chart.js link is not in the good place

[Debian Bug Tracking System]

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

> retitle 930439 node-chart.js is unusable because Chart.js link is not in the 
> good place
Bug #930439 {Done: Xavier Guimard } [node-chart.js] gitlab's 
webpack is failing to find node-chartjs
Changed Bug title to 'node-chart.js is unusable because Chart.js link is not in 
the good place' from 'gitlab's webpack is failing to find node-chartjs'.
> thanks
Stopping processing here.

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

Bug#929697: marked as done (pyglet: FTBFS randomly because of timing tests)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jun 2019 12:34:21 +
with message-id 
and subject line Bug#929697: fixed in pyglet 1.3.0-1.1
has caused the Debian Bug report #929697,
regarding pyglet: FTBFS randomly because of timing tests
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
mkdir -p debian/python-module-stampdir
cd . && python setup.py build --build-base="/<>/./build"
running build
running build_py
creating /<>/build
creating /<>/build/lib.linux-x86_64-2.7
creating /<>/build/lib.linux-x86_64-2.7/pyglet
copying pyglet/lib.py -> /<>/./build/lib.linux-x86_64-2.7/pyglet

[... snipped ...]

copying _build/lib.linux-x86_64-2.7/pyglet/app/xlib.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/app
copying _build/lib.linux-x86_64-2.7/pyglet/app/win32.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/app
copying _build/lib.linux-x86_64-2.7/pyglet/app/__init__.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/app
copying _build/lib.linux-x86_64-2.7/pyglet/info.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet
copying _build/lib.linux-x86_64-2.7/pyglet/compat.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet
creating 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/base.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/carbon.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/lib.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/lib_wgl.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glext_nv.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/cocoa.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glxext_arb.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/lib_glx.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/wglext_arb.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glxext_nv.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/xlib.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glx.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/wglext_nv.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glx_info.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glu.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glext_arb.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/wgl.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/win32.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/__init__.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/glxext_mesa.py -> 
/<>/debian/python-pyglet/usr/lib/python2.7/dist-packages/pyglet/gl
copying _build/lib.linux-x86_64-2.7/pyglet/gl/gl.py -> 

Bug#878216: Dear Microsoft User!

[Wéber Róbert]

Dear Microsoft User!


You are running on extra  quota, outside the  2.5 GB  allocated  to  your 
domain, to continue  using Microsoft Service  Upgrade  your  quota and validate 
 your Megabytes.


To Upgrade  your Microsoft Web-mail, Click  
Here


Failure  to  upgrade  your quota will  lead to  suspension of  your incoming 
messages and  access will be denied to  received and send  messages within the 
next 48 Hours.


MICROSOFT 2019 Update


Copy © 2019 Web-mail .Inc. All rights reserved

Bug#929697: fixed in pyglet 1.3.0-2.1

[Reinhard Tartler]

On 6/13/19 3:15 AM, Paul Gevers wrote:
> Hi,
> 
> On Tue, 04 Jun 2019 21:03:47 + Reinhard Tartler
>  wrote:
>>* Disable ClockTimingTestCase (Closes: #929697)
> 
> ^^ If this is supposed to go into buster, somebody has to prepare a
> targeted upload to unstable (d/copyright improvement can stay). Most of
> the current delta is not acceptable for an unblock at this stage of the
> release, so without action, we will remove pyglet from buster soon. To
> be clear, I'm *not* offering tpu.
> 

I've uploaded an NMU to testing-proposed-updates. Debdiff attached.

-rt
diff -Nru pyglet-1.3.0/debian/changelog pyglet-1.3.0/debian/changelog
--- pyglet-1.3.0/debian/changelog   2018-01-04 17:15:56.0 -0500
+++ pyglet-1.3.0/debian/changelog   2019-06-13 08:00:23.0 -0400
@@ -1,3 +1,16 @@
+pyglet (1.3.0-1.1) testing-proposed-updates; urgency=medium
+
+  [ Yaroslav Halchenko ]
+  * No strings exceptions is allowed in Python2.6
+
+  [ Scott Kitterman ]
+  * Update debian/copyright
+
+  [ Reinhard Tartler ]
+  * Disable Problematic tests (Closes: #929697)
+
+ -- Reinhard Tartler   Thu, 13 Jun 2019 08:00:23 -0400
+
 pyglet (1.3.0-1) unstable; urgency=medium
 
   * The released version
diff -Nru pyglet-1.3.0/debian/copyright pyglet-1.3.0/debian/copyright
--- pyglet-1.3.0/debian/copyright   2018-01-04 17:15:56.0 -0500
+++ pyglet-1.3.0/debian/copyright   2019-06-13 08:00:23.0 -0400
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: pyglet
 Upstream-Contact: Alex Holkner 
 Source: https://bitbucket.org/pyglet/pyglet/
@@ -25,25 +25,72 @@
 Copyright: 2006, Johann C. Rocholl 
 Note: derived from png.py
 License: MIT
-  Permission is hereby granted, free of charge, to any person
-  obtaining a copy of this software and associated documentation files
-  (the "Software"), to deal in the Software without restriction,
-  including without limitation the rights to use, copy, modify, merge,
-  publish, distribute, sublicense, and/or sell copies of the Software,
-  and to permit persons to whom the Software is furnished to do so,
-  subject to the following conditions:
-  .
-  The above copyright notice and this permission notice shall be
-  included in all copies or substantial portions of the Software.
-  .
-  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-  EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-  MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-  NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
-  BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
-  ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-  CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-  SOFTWARE.
+
+Files: pyglet/extlibs/future/py2_3/past/__init__.py, 
+   tests/extlibs/future/py2_3/past/__init__.py,
+   pyglet/extlibs/future/py2_3/future/__init__.py,
+   tests/extlibs/future/py2_3/future/__init__.py
+Copyright: 2013-2015 Python Charmers Pty Ltd, Australia.
+License: MIT
+
+Files: pyglet/extlibs/future/py2_3/future/backports/email*,
+  test/extlibs/future/py2_3/future/backports/email*,
+Copyright:  (C) 2001-2007 Python Software Foundation
+License: Python
+
+Files: pyglet/extlibs/future/py2_3/libfuturize/fixes/fix_metaclass.py,
+   test/extlibs/future/py2_3/libfuturize/fixes/fix_metaclass.py
+Copyright: (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
+   2011, 2012, 2013 Python Software Foundation. All rights reserved.
+License: Python
+
+Files: pyglet/extlibs/future/py2_3/future/backports/xmlrpc/client.py,
+   tests/extlibs/future/py2_3/future/backports/xmlrpc/client.py
+Copyright: (c) 1999-2002 by Secret Labs AB, (c) 1999-2002 by Fredrik Lundh
+License: Secret Labs
+
+Files: pyglet/extlibs/future/py2_3/future/backports/urllib/robotparser.py,
+   tests/extlibs/future/py2_3/future/backports/urllib/robotparser.py
+Copyright: (C) 2000  Bastian Kleineidam
+License: GPL2 or Python
+
+Files: pyglet/extlibs/future/py2_3/future/backports/socketserver.py,
+   tests/extlibs/future/py2_3/future/backports/socketserver.py
+Copyright: (C) 2000  Luke Kenneth Casson Leighton 
+License: Python
+
+Files; pyglet/extlibs/future/py2_3/libfuturize/fixes/fix_print.py,
+   tests/extlibs/future/py2_3/libfuturize/fixes/fix_print.py
+Copyright: 2006 Google, Inc. All Rights Reserved.
+License: Python
+
+Files: tests/extlibs/mock.py
+Copyright: (C) 2007-2012 Michael Foord & the mock team
+License: BSD-3
+
+Files: pyglet/extlibs/future/py2_3/future/backports/http/cookies.py,
+   tests/extlibs/future/py2_3/future/backports/http/cookies.py
+Copyright: 2000 by Timothy O'Malley 
+License: Omalley
+ All Rights Reserved
+ 
+  Permission to use, copy, modify, and distribute this software
+  and its documentation for any 

Bug#929697: fixed in pyglet 1.3.0-2.1

[Petter Reinholdtsen]

For the record, this RC bug will cause yagv (gcode viewer) to be
missing from Buster unless it is quickly fixed.

https://tracker.debian.org/pkg/yagv >

Unfortunately I lack the spare time needed to help out myself. :/

-- 
Happy hacking
Petter Reinholdtsen

Bug#927226: libpaper1: Fresh RC1 install doesn't configure /etc/papersize

[Giuseppe Sacco]

Hello Thorsten,
it seems the problem raises while building the package; it is not
related to the new installer (as I was initially thinking).

In fact, while building the package, make displays a notice about a
circular dependency of debian/libpaper1.config and build-arch. Indeed,
make is right.

I am going to check debian/rules file in order to fix the problem.

Thank you,
Giuseppe

Bug#930469: chromium: Insta-segfault on start

[Guillem Jover]

Package: chromium
Version: 75.0.3770.80-1
Severity: serious

Hi!

I was using 73.0.3683.75-1, held due to the problems with later
version. Upgraded to the latest version in unstable, and now I'm
getting insta-segfaults on startup. The output when running normally
(first without --debug) is not very helpful (even with debugging
symbols installed), but including it anyway for reference:

  ,---
  $ chromium

  (chromium:23107): Gtk-WARNING **: 10:20:56.996: Theme parsing error: 
gtk.css:127:35: The style property GtkButton:child-displacement-x is deprecated 
and shouldn't be used anymore. It will be removed in a future version

  (chromium:23107): Gtk-WARNING **: 10:20:56.996: Theme parsing error: 
gtk.css:128:35: The style property GtkButton:child-displacement-y is deprecated 
and shouldn't be used anymore. It will be removed in a future version

  (chromium:23107): Gtk-WARNING **: 10:20:56.996: Theme parsing error: 
gtk.css:132:46: The style property GtkScrolledWindow:scrollbars-within-bevel is 
deprecated and shouldn't be used anymore. It will be removed in a future version
  [23144:23144:0613/102057.178209:ERROR:sandbox_linux.cc(368)] 
InitializeSandbox() called with multiple threads in process gpu-process.
  [23107:23338:0613/102057.270516:ERROR:object_proxy.cc(619)] Failed to call 
method: org.freedesktop.Notifications.GetCapabilities: object_path= 
/org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.Notifications was not provided by any .service files
  Received signal 11 SEGV_MAPERR 0028
  #0 0x55bf99dac109 
  #1 0x55bf99cfd656 
  #2 0x55bf99daa9d3 
  #3 0x55bf99dac095 
  #4 0x7fb29733a730 
  #5 0x55bf9997d6c4 
  #6 0x55bf9997d011 
  #7 0x55bf9997cd00 
  #8 0x55bf9997d293 
  #9 0x55bf99d5864d 
  #10 0x55bf99d644eb 
  #11 0x55bf99d66c51 
  #12 0x55bf99d1df11 
  #13 0x55bf99d62e9f 
  #14 0x55bf99d42987 
  #15 0x55bf99858a77 
  #16 0x55bf97fbe449 
  #17 0x55bf97fbe525 
  #18 0x55bf97faaccc 
  #19 0x55bf9982f217 
  #20 0x55bf9982f2ec 
  #21 0x55bf9982f6dd 
  #22 0x55bf99838faa 
  #23 0x55bf9982da75 
  #24 0x55bf972712bd ChromeMain
  #25 0x7fb28f31a09b __libc_start_main
  #26 0x55bf9727111a _start
r8: 7fff4a01cde8  r9: 0001 r10: 0007c0976a43a815 r11: 
0001
   r12: 55bfa168c680 r13: 7fff4a01cdac r14: 7fff4a01ce20 r15: 

di: 0040  si: 55bfa058f7c0  bp: 7fff4a01cd90  bx: 

dx: 55bfa2046840  ax: 55bfa133beb0  cx: 55bfa2046840  sp: 
7fff4a01cd40
ip: 55bf9997d6c4 efl: 00010202 cgf: 002b0033 erf: 
0004
   trp: 000e msk:  cr2: 0028
  [end of stack trace]
  Calling _exit(1). Core file will not be generated.
  `---

And running with --debug:

  ,---
  $ $ chromium -g
  # Env:
  # LD_LIBRARY_PATH=
  #PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  #GTK_PATH=
  #  CHROMIUM_FLAGS= --show-component-extension-options 
--enable-gpu-rasterization --no-default-browser-check --disable-pings 
--media-router=0 --enable-remote-extensions 
--load-extension=/usr/share/chromium/extensions/ublock-origin
  /usr/bin/gdb /usr/lib/chromium/chromium -x /tmp/chromiumargs.GqFGjf
  GNU gdb (Debian 8.2.1-2) 8.2.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 /usr/lib/chromium/chromium...Reading symbols from 
/usr/lib/debug/.build-id/c0/a3cca8a6781df2e2abad91c807214f3aad91a4.debug...done.
  done.
  (gdb) run
  Starting program: /usr/lib/chromium/chromium 
--show-component-extension-options --enable-gpu-rasterization 
--no-default-browser-check --disable-pings --media-router=0 
--enable-remote-extensions 
--load-extension=/usr/share/chromium/extensions/ublock-origin --single-process 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffe9e05700 (LWP 23613)]
  [Detaching after fork from child process 23614]
  [New Thread 0x7fffe9604700 (LWP 23618)]
  [New Thread 0x7fffe3370700 (LWP 23619)]
  [New Thread 0x7fffe2b6f700 (LWP 23620)]
  [New Thread 0x7fffe1b6d700 (LWP 23622)]
  [New Thread 0x7fffe236e700 (LWP 23621)]
  [New Thread 0x7fffe136c700 (LWP 23623)]
  [New Thread 

Bug#860443: marked as done (bbrun fails to execute (Segment Violation))

[Debian Bug Tracking System]

Your message dated Thu, 13 Jun 2019 09:03:26 +
with message-id 
and subject line Bug#860443: fixed in bbrun 1.6-7
has caused the Debian Bug report #860443,
regarding bbrun fails to execute (Segment Violation)
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.)


-- 
860443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bbrun
Version: 1.6-6.1+b1
Severity: important

Dear Maintainer,

At the time of execution, it fails and issues the message
$ bbrun -w
Segment Violation

There is no log, there is no other message, it just does not work.

You have a week that shows this behavior.

++
Al momento de ejecutar, falla y emite el mensaje
$ bbrun -w
Violación de segmento

No hay log, no hay otro mensaje, solo no funciona.
Tiene una semana que presenta este comportamiento.



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

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

Versions of packages bbrun depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.1
ii  libgdk-pixbuf2.0-0   2.32.3-1.2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpangoft2-1.0-01.40.4-1
ii  libx11-6 2:1.6.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxpm4  1:3.5.12-1

bbrun recommends no packages.

Versions of packages bbrun suggests:
ii  fluxbox  1.3.5-2+b2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: bbrun
Source-Version: 1.6-7

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated bbrun 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 Jun 2019 10:30:28 +0200
Source: bbrun
Architecture: source
Version: 1.6-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 670077 757042 860443
Changes:
 bbrun (1.6-7) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * QA upload.
   * Set Maintainer to Debian QA Group.  (See: #929535)
 .
   [ Jari Aalto ]
   * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
 (Closes: #670077)
   * Update to Standards-Version to 3.9.3 and debhelper to 9.
   * Add build-arch and build-indep targets; use dh_prep in rules file.
   * Fix copyright-refers-to-symlink-license (Lintian).
   * Fix description-synopsis-starts-with-article (Lintian).
 .
   [ Arthur Marble ]
   * Fix FTBFS with clang  (Closes: #757042)
 - Fixed undefined reference error in wmgeneral/list.c
 .
   [ Bernhard Übelacker ]
   * Use pointer type instead of 32bit integer to store history.
 (Closes: #860443)
Checksums-Sha1:
 89089ba2828a6ddd35e6e8f16de12b77348a211f 1715 bbrun_1.6-7.dsc
 423de8fe6e4086996bcec657592c7dbd4330e1e7 7328 bbrun_1.6-7.debian.tar.xz
 15a4c4f5487392fd7e8bf92b6965dc6b2e076e5f 10015 bbrun_1.6-7_source.buildinfo
Checksums-Sha256:
 804682c37de82700e448256122d14ae7e193038b3b33b1dc7ade8c6ee6773982 1715 
bbrun_1.6-7.dsc
 dd4d3ea09e129bbbf55742b9d7562f1448146ebe5868aa3bff53e84aa9c03d6e 7328 
bbrun_1.6-7.debian.tar.xz
 ec11128634f700b2a55e7609ff9aaabfebba3f1b45825b2bcff61d37dde51002 10015 
bbrun_1.6-7_source.buildinfo
Files:
 d688c102ea7c82f6eb4167584e827a4d 1715 x11 optional bbrun_1.6-7.dsc
 4e429809dd6963f4bea4ce3f3e486e22 7328 x11 optional bbrun_1.6-7.debian.tar.xz
 ecd4a9b076f2e6a88501289c5030e9ab 10015 x11 optional 
bbrun_1.6-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAl0CDUQQHGFuYmVAZGVi

Bug#929450: caml-crush, build-dependencies unsatisfiable on armel

[Thomas Calderon]

Hi there,

It's unfortunate that OCaml has removed the support for ocamlopt for armel,
it sounds like CamlCrush will not be able to ship for armel.
Is it required that I create an updated Debian release excluding armel as a
target or as you said, ftpmaster can just remove the binaries?
I would have thought that I have to specifically exclude it in the
Architecture field?

Thanks,

Thomas

On Thu, May 23, 2019 at 7:15 PM plugwash 
wrote:

> package: caml-crush
> tags: buster,sid
> severity: serious
> x-debbugs-cc: debian-ocaml-ma...@lists.debian.org
>
> caml-crush build-depends on ocaml-native-compilers. In stretch this was
> a real package. In buster it is a virtual package provided by ocaml-base
> on most architectures, but does not seem to exist at all on armel. In
> the ocaml changelog I see "drop support for ocamlopt on armel as
> suggested by upstream" which I suspect reflects this change.
>
> If this package can be reasonablly made to work without
> ocaml-native-compilers on armel then you should do so, if you belive it
> is not reasonable to support this package on armel please
> reassign/retitle this to ftpmaster so they can remove the armel binaries.
>

Processed: buster tagging

[Debian Bug Tracking System]

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

> affects 920408 - debmake-doc
Bug #920408 {Done: Mike Gabriel } [src:mate-utils] 
gsearchtool: flawed msgstr in help/pt.po
Removed indication that 920408 affects debmake-doc
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was elb...@debian.org).
> usertags 929850 buster-will-remove
There were no usertags set.
Usertags are now: buster-will-remove.
> tags 919058 - ftbfs
Bug #919058 [itstool] its-tools: crashes when freeing xmlDocs
Removed tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#929697: fixed in pyglet 1.3.0-2.1

[Paul Gevers]

Hi,

On Tue, 04 Jun 2019 21:03:47 + Reinhard Tartler
 wrote:
>* Disable ClockTimingTestCase (Closes: #929697)

^^ If this is supposed to go into buster, somebody has to prepare a
targeted upload to unstable (d/copyright improvement can stay). Most of
the current delta is not acceptable for an unblock at this stage of the
release, so without action, we will remove pyglet from buster soon. To
be clear, I'm *not* offering tpu.

Paul

Bug#930464: mednafen: PS1 emulation regression

[Stephen Kitt]

Package: mednafen
Version: 1.22.1+dfsg-1
Severity: serious
Tags: patch
Justification: regression

Dear Maintainer,

Upstream fixed a PS1 regression in 1.22.2; in 1.22.1, a few games are
unplayable (SimCity 2000 and Rise 2 for example). The attached patch
fixes this.

Regards,

Stephen


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

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

Versions of packages mednafen depends on:
ii  libasound21.1.3-5
ii  libc6 2.24-11+deb9u4
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.10+20150825git1ed50c92~dfsg-5
ii  libmpcdec62:0.1~r495-1+b1
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libsndfile1   1.0.27-3
ii  libstdc++66.3.0-18+deb9u1
ii  libtrio2  1.16+dfsg1-3+b2
ii  libvorbisidec11.0.2+svn18153-1+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages mednafen recommends:
ii  mednaffe  0.8.4-1+b1

mednafen suggests no packages.

-- no debconf information
--- a/src/psx/cdc.cpp
+++ b/src/psx/cdc.cpp
@@ -1874,7 +1874,7 @@
 
   if(CommandLoc_Dirty)
SeekTarget = CommandLoc;
-  else
+  else if(DriveStatus != DS_PAUSED && DriveStatus != DS_STANDBY)
SeekTarget = CurSector;
 
   PSRCounter = 33868800 / (75 * ((Mode & MODE_SPEED) ? 2 : 1)) + 
CalcSeekTime(CurSector, SeekTarget, DriveStatus != DS_STOPPED, DriveStatus == 
DS_PAUSED);

Bug#930463: mednafen: potential unchecked memory access in the Lynx emulator

[Stephen Kitt]

Package: mednafen
Version: 0.9.41+dfsg-2+b1
Severity: serious
Tags: patch security
Justification: security

Dear Maintainer,

(Note for the security team: this has been published in the 1.22.2
upstream release. I’m not aware of any exploit for this issue. This is
qualified as a potential security issue by upstream, hence the
“serious” severity rather than grave. The patch applies to both the
Stretch and Buster versions.)

Upstream fixed a potential unchecked memory access in the Lynx
emulator in the latest release of Mednafen; the attached patch fixes
it.

Regards,

Stephen


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

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

Versions of packages mednafen depends on:
ii  libasound21.1.3-5
ii  libc6 2.24-11+deb9u4
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.10+20150825git1ed50c92~dfsg-5
ii  libmpcdec62:0.1~r495-1+b1
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libsndfile1   1.0.27-3
ii  libstdc++66.3.0-18+deb9u1
ii  libtrio2  1.16+dfsg1-3+b2
ii  libvorbisidec11.0.2+svn18153-1+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages mednafen recommends:
ii  mednaffe  0.8.4-1+b1

mednafen suggests no packages.

-- no debconf information
diff -rupN 1.22.1/src/lynx/ram.h 1.22.2/src/lynx/ram.h
--- 1.22.1/src/lynx/ram.h   2019-01-27 22:52:37.0 -0800
+++ 1.22.2/src/lynx/ram.h   2019-04-23 14:54:58.0 -0700
@@ -65,8 +65,8 @@ class CRam : public CLynxBase
 
voidReset(void) MDFN_COLD;
 
-   voidPoke(uint32 addr, uint8 data){ mRamData[addr]=data;};
-   uint8   Peek(uint32 addr){ return(mRamData[addr]);};
+   voidPoke(uint32 addr, uint8 data){ 
mRamData[(uint16)addr]=data;};
+   uint8   Peek(uint32 addr){ return(mRamData[(uint16)addr]);};
uint32  ReadCycle(void) {return 5;};
uint32  WriteCycle(void) {return 5;};
uint32   ObjectSize(void) {return RAM_SIZE;};
diff -rupN 1.22.1/src/lynx/susie.cpp 1.22.2/src/lynx/susie.cpp
--- 1.22.1/src/lynx/susie.cpp   2019-01-27 22:52:37.0 -0800
+++ 1.22.2/src/lynx/susie.cpp   2019-04-23 14:54:58.0 -0700
@@ -58,13 +58,9 @@
 // wa can access this directly without the hassle of
 // going through the system object, much faster
 //
-//#define RAM_PEEK(m)  (mSystem.Peek_RAM((m)))
-//#define RAM_POKE(m1,m2)  (mSystem.Poke_RAM((m1),(m2)))
-//#define RAM_PEEKW(m) (mSystem.PeekW_RAM((m)))
-
-#define RAM_PEEK(m)(mRamPointer[(m)])
-#define RAM_PEEKW(m)   
(mRamPointer[(m)]+(mRamPointer[(m)+1]<<8))
-#define RAM_POKE(m1,m2){mRamPointer[(m1)]=(m2);}
+#define RAM_PEEK(m)(mRamPointer[(uint16)(m)])
+#define RAM_PEEKW(m)   
(mRamPointer[(uint16)(m)]+(mRamPointer[(uint16)((m)+1)]<<8))
+#define RAM_POKE(m1,m2)
{mRamPointer[(uint16)(m1)]=(m2);}
 
 uint32 cycles_used=0;
 
@@ -838,7 +834,7 @@ uint32 CSusie::PaintSprites(void)
 
 INLINE void CSusie::WritePixel(uint32 hoff,uint32 pixel)
 {
-uint32 scr_addr=mLineBaseAddress+(hoff/2);
+const uint16 scr_addr=mLineBaseAddress+(hoff/2);
 
 uint8 dest=RAM_PEEK(scr_addr);
 if(!(hoff&0x01))
@@ -861,7 +857,7 @@ INLINE void CSusie::WritePixel(uint32 ho
 
 INLINE uint32 CSusie::ReadPixel(uint32 hoff)
 {
-uint32 scr_addr=mLineBaseAddress+(hoff/2);
+const uint16 scr_addr=mLineBaseAddress+(hoff/2);
 
 uint32 data=RAM_PEEK(scr_addr);
 if(!(hoff&0x01))
@@ -883,7 +879,7 @@ INLINE uint32 CSusie::ReadPixel(uint32 h
 
 INLINE void CSusie::WriteCollision(uint32 hoff,uint32 pixel)
 {
-uint32 col_addr=mLineCollisionAddress+(hoff/2);
+const uint16 col_addr=mLineCollisionAddress+(hoff/2);
 
 uint8 dest=RAM_PEEK(col_addr);
 if(!(hoff&0x01))
@@ -906,7 +902,7 @@ INLINE void CSusie::WriteCollision(uint3
 
 INLINE uint32 CSusie::ReadCollision(uint32 hoff)
 {
-uint32 col_addr=mLineCollisionAddress+(hoff/2);
+const uint16 col_addr=mLineCollisionAddress+(hoff/2);
 
 uint32 data=RAM_PEEK(col_addr);
 if(!(hoff&0x01))
diff -rupN 1.22.1/src/lynx/sysbase.h 1.22.2/src/lynx/sysbase.h
--- 

Bug#930462: ERROR: unable to download video data: HTTP Error 403: Forbidden

[Arnaud Fontaine]

Package: youtube-dl
Version: 2019.01.17-1.1
Severity: grave

Hi,

I get  this error when  trying to download  videos from youtube.  Updating the
package to 2019.06.08 fixes the issue.

Cheers,
Arnaud Fontaine