Accepted chromium 83.0.4103.116-3.1 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 15 Sep 2020 13:10:35 +0000
Source: chromium
Architecture: source
Version: 83.0.4103.116-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Team <chromium@packages.debian.org>
Changed-By: Peter Michael Green <plugwash@debian.org>
Changes:
chromium (83.0.4103.116-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add 64-bit time syscalls to syscall whitelist and clock selection
parameter filtering code
* Switch to explicitly versioned python2
+ Update build-depends
+ Replace references to /usr/bin/python and to env python
with /usr/bin/python2 and env python2
+ make exec_script in gn use python2
+ add code in debian/rules clean to set the shebang in
third_party/closure_compiler/compiler.py it seems someting in the upstream
build system sometimes resets it.
Checksums-Sha1:
70437421cc48ff0b74e8d5b3d7f7555741696ce9 3602 chromium_83.0.4103.116-3.1.dsc
635ef8820c7de8b183dc5b2ebb16e829c6b58905 239708 chromium_83.0.4103.116-3.1.debian.tar.xz
804b27851fb974a08b7f5e2b57253b012f5f6df1 20920 chromium_83.0.4103.116-3.1_source.buildinfo
Checksums-Sha256:
eefb899d4ce5713ce1fffa1a674860c16fbd9b3f45e01087948017d2fb3fbc6a 3602 chromium_83.0.4103.116-3.1.dsc
a0ae6a20b3cfe6d20ded9be0f52cbea9188e4869ce8e49eb1b76990ec9555376 239708 chromium_83.0.4103.116-3.1.debian.tar.xz
dfd3e25b28020be563aef93b973c7a454f0c8afb1d85e7fc5fff6daaab32a52f 20920 chromium_83.0.4103.116-3.1_source.buildinfo
Files:
9809215fc0092ed1c192a6669baa84f3 3602 web optional chromium_83.0.4103.116-3.1.dsc
5ca8b0a378e62939adc0c139727e1b4f 239708 web optional chromium_83.0.4103.116-3.1.debian.tar.xz
c0d8316fa7e4d68458b5166bd29bbed7 20920 web optional chromium_83.0.4103.116-3.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl9gwkYUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtcEw//f2i8mhWH/CWMrwrBoydYoWdl5xhc
+Y2eHZT+0foOUPROR9JUw/h7OxriooJRF5oP1BhIQhHrtd5uGyHdrEzL3u5DoQpZ
r3iwCD96C6qZzt5ocK1yfmNd/Fg3q2sobLo+HAAKas2u8iUIGV+zdsP5Zk+fxtxJ
MrIWS5Zll/9YWY1IerlMnSk5EZ3qIlJOOTf1VfM+3pckRYNKkHMjz+XqAx6AJ+Be
a7KKq/8BFzsfmKNwuxZZhD0Pgmj/ppJIc01Fi91PfL2zWXinmZ7nbfKd8OlfsboO
p1V+0ZL/ykbAlcLedDUSpsQGnV2PKKi9vWuW2hE6Ny9BPymK8NptNT1WSt0Ton8K
SJNP1UysMbuhxtIAsNhLndK6jHiJW9C7pJVM5bn8MeTXxm5LFF6NrVhQnlYr0aEl
k+bXHe0IOomU0GOR7Cx1onpp3N3oLkPshnJX1V9ZLX72ZnjG9qkcz2y/JATJFWnE
IusfuiNcKB9eWzTiCaaJhPOkGV+Lq9oMIjuwF4MsKdrzIWUjxD7TZwxrzWkhImi5
weuY70exzJzwxz29V+01lzGmFCRHEyQwD0NlhWbcE/kvY4yIf129SPSp5/1jFTmx
2inpatPkulX3y7hJ8siCgZIiPfN1bjhUlWDPSoSV60+14yNV4I3KZj0/IjFsQ3Ol
SpprJ2jMjrvZ9F4=
=0aHb
-----END PGP SIGNATURE-----
Reply to: