Bug#979621: pandas: autopkgtest regression in testing: No tables found

[Paul Gevers]

Source: pandas
Version: 1.1.5+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent change in testing the autopkgtest of your package started
to fail. I copied some of the output at the bottom of this report. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul
By the way: as your test is accessing the internet, you should add a
"needs-internet" restriction

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pandas/9462264/log.gz

=== FAILURES
===
_ TestReadHtml.test_banklist_url_positional_match[bs4]
_

self = 

@tm.network
def test_banklist_url_positional_match(self):
url = "http://www.fdic.gov/bank/individual/failed/banklist.html;
# Passing match argument as positional should cause a FutureWarning.
with tm.assert_produces_warning(FutureWarning):
>   df1 = self.read_html(
url, "First Federal Bank of Florida", attrs={"id": "table"}
)



OpenPGP_signature
Description: OpenPGP digital signature

Bug#979620: sonic-pi: flaky armhf and arm64 autopkgtest on ci.debian.net: unknown bpm

[Paul Gevers]

Source: sonic-pi
Version: 3.2.2~repack-6
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

The autopkgtest of your package turned up as blocking xorg-server. I
looked into the history of your autopkgtest and it fails regularly on
arm64 and armhf [1, 2]. I copied some of the output at the bottom of
this report.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Please do get in touch if we need to dive into this together. Or if you
want to discuss this issue.

Paul

[1] https://ci.debian.net/packages/s/sonic-pi/testing/arm64/
[2] https://ci.debian.net/packages/s/sonic-pi/testing/armhf/

https://ci.debian.net/data/autopkgtest/testing/arm64/s/sonic-pi/9392735/log.gz

Source: sonic-pi
Version: 3.2.2~repack-6
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

The autopkgtest of your package turned up as blocking xorg-server. I
looked into the history of your autopkgtest and it fails regularly on
arm64 and armhf [1, 2]. I copied some of the output at the bottom of
this report.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Please do get in touch if we need to dive into this together. Or if you
want to discuss this issue.

Paul

[1] https://ci.debian.net/packages/s/sonic-pi/testing/arm64/
[2] https://ci.debian.net/packages/s/sonic-pi/testing/armhf/

https://ci.debian.net/data/autopkgtest/testing/arm64/s/sonic-pi/9392735/log.gz

Buffer: 4.03s./4.03sTime: 0.09m.   DHP: [ ]  Overruns: 0
Xruns: 0
00:|
  |
01:| |
Buffer: 4.03s./4.03sTime: 0.09m.   DHP: [ ]  Overruns: 0
Xruns: 0
00:|
  |
01:| |
Buffer: 4.03s./4.03sTime: 0.09m.   DHP: [ ]  Overruns: 0
Xruns: 0


>>> Please wait while writing all data to disk. (shouldn't take long)
   |"|
00:|
  |
01:| |
Buffer: 4.05s./4.05sTime: 0.10m.   DHP: [ ]  Overruns: 0
Xruns: 0
00:|
  |
01:| |
Buffer: 4.05s./4.05sTime: 0.10m.   DHP: [ ]  Overruns: 0
Xruns: 0
Finished.
unknown bpm
autopkgtest [17:56:12]: test gui: ---]



OpenPGP_signature
Description: OpenPGP digital signature

Bug#979612: firefox-esr: after upgrade from 78.6.0esr-1~deb10u1 to 78.6.1esr-1~deb10u1 gnome interface behave erratically

[Damien]

Package: firefox-esr
Version: 78.6.1esr-1~deb10u1
Severity: serious
Justification: 4

Dear Maintainer,

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

   * What led up to the situation?
I executed package updates and upgrades using apt

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I tried loggin out and back in, rebooting the host, none helped. 

   After running an apt upgrade on Debian 10 (Buster) running a Gnome Desktop, 
when Firefox is running, strange behavior takes place. 
1. Unable to grab and move windows of other applications like gedit. 
2. Unable to click or activate menu items of TorBrowser
3. Unable to close, click or access menu items of a multiple other application. 

When Firefox-ESR is closed, all above issues go away. 
When Firefox-ESR version  78.6.1esr-1~deb10u1 running, all kind of strange and 
unexpected behavior of the Gnome UI takes place.




-- Package-specific info:

-- Extensions information
Name: Amazon.com
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Dark theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Default theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled

Name: DoH Roll-Out
Location: /usr/lib/firefox-esr/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: eBay
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: HTTPS Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywh...@eff.org.xpi
Status: enabled

Name: Light theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled

Name: Web Compat
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: WebCompat Reporter
Location: 
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled

Name: Wikipedia (en)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

-- Plugins information

-- Addons package information
ii  firefox-esr78.6.1esr-1~deb10u1 amd64Mozilla Firefox web browser 
- Extended Support Release (ESR)

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

Kernel: Linux 4.19.0-13-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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox-esr depends on:
ii  debianutils 4.8.6.1
ii  fontconfig  2.13.1-2
ii  libatk1.0-0 2.30.0-2
ii  libc6   2.28-10
ii  libcairo-gobject2   1.16.0-4
ii  libcairo2   1.16.0-4
ii  libdbus-1-3 1.12.20-0+deb10u1
ii  libdbus-glib-1-20.110-4
ii  libevent-2.1-6  2.1.8-stable-4
ii  libffi6 3.2.1-9
ii  libfontconfig1  2.13.1-2
ii  libfreetype62.9.1-3+deb10u2
ii  libgcc1 1:8.3.0-6
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgtk-3-0  3.24.5-1
ii  libpango-1.0-0  1.42.4-8~deb10u1
ii  libstdc++6  8.3.0-6
ii  libx11-62:1.6.7-1+deb10u1
ii  libx11-xcb1 2:1.6.7-1+deb10u1
ii  libxcb-shm0 1.13.1-2
ii  libxcb1 1.13.1-2
ii  libxcomposite1  1:0.4.4-2
ii  libxdamage1 1:1.1.4-3+b3
ii  libxext62:1.3.3-1+b2
ii  libxfixes3  1:5.0.3-1
ii  libxrender1 1:0.9.10-1
ii  procps  2:3.3.15-2
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages firefox-esr recommends:
ii  libavcodec58  7:4.1.6-1~deb10u1

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-7
ii  libgssapi-krb5-2   1.17-3+deb10u1
ii  libgtk2.0-02.24.32-3
ii  pulseaudio 12.2-4+deb10u1

-- no debconf information

Bug#979524: debian-reference: build-depends on libopencc2-data, which no longer exists

[Osamu Aoki]

Hi,

I think it is time to fix this bug and upload package.  Let me make
final check.  Osamu

On Fri, 2021-01-08 at 23:28 -0500, Boyuan Yang wrote:
> Hi,
> 
> 在 2021-01-08星期五的 09:49 +0800，xiao sheng wen(肖盛文)写道：
> > Hi,
> > 
> >  libopencc2-data had change name to libopencc-data in bullseye
> > sid.
> > 
> > As the opencc upstream had changed the version number, SONAME, etc.
> > 
> > Update debian-reference build-depends on libopencc-data should fix
> > this bug.
> 
> This bug as well as the python2->3 migration has long been fixed in
> git
> trunk. We just need another upload.
> 
> Osamu: do you have time to review all changes after 2.76 tag and make
> another upload for debian-reference package? This will fix at least
> one
> RC-buggy bug so it might be worthwhile to get fixed before freeze.
> 
> Thanks,
> Boyuan Yang
> 
> 
> > 在 2021/1/8 上午12:55, Ivo De Decker 写道:
> > > package: src:debian-reference
> > > version: 2.76
> > > tags: bullseye sid ftbfs
> > > severity: serious
> > > 
> > > Hi,
> > > 
> > > It seems debian-reference build-depends on libopencc2-data, which
> > > no longer
> > > exists.
> > > 
> > > Cheers,
> > > 
> > > Ivo
> > > 
> 
> 

Bug#979618: chromium freezes on start, triggering a force quit by gnome

[Lee Garrett]

Package: chromium
Version: 87.0.4280.88-0.4
Severity: grave
X-Debbugs-Cc: deb...@rocketjump.eu

Hi,

starting chromium on bullseye will render a window (with various elements
shifted down by half a screen), which is impossible to interact with, and causes
gnome to offer a "force quit" prompt after a few seconds.

Output from the CLI:
->8-->8-->8-->8-->8-->8-->8-->8-->8-->8-->8-
$ chromium
libva error: vaGetDriverNameByIndex() failed with unknown libva error, 
driver_name = (null)
[9413:9413:0109/060426.733876:ERROR:vaapi_wrapper.cc(541)] vaInitialize failed: 
unknown libva error
[9413:9413:0109/060426.735693:ERROR:sandbox_linux.cc(374)] InitializeSandbox() 
called with multiple threads in process gpu-process.
[9413:9413:0109/060426.855283:ERROR:shared_context_state.cc(74)] Skia shader 
compilation error


Errors:

[9413:9413:0109/060426.858413:ERROR:shared_context_state.cc(74)] Skia shader 
compilation error


Errors:

[9413:9413:0109/060426.860282:ERROR:shared_context_state.cc(74)] Skia shader 
compilation error


Errors:

[9413:9413:0109/060426.867099:ERROR:shared_context_state.cc(74)] Skia shader 
compilation error


Errors:

[9413:9413:0109/060426.869489:ERROR:shared_context_state.cc(74)] Skia shader 
compilation error


Errors:

[9415:9428:0109/060426.876651:ERROR:nss_util.cc(283)] After loading Root Certs, 
loaded==false: NSS error code: -8018
[9413:9413:0109/060426.993836:ERROR:shared_context_state.cc(74)] Skia shader 
compilation error


Errors:

[9413:9413:0109/060430.833703:ERROR:gl_surface_presentation_helper.cc(259)] 
GetVSyncParametersIfAvailable() failed for 1 times!
[9413:9413:0109/060430.839756:ERROR:gl_surface_presentation_helper.cc(259)] 
GetVSyncParametersIfAvailable() failed for 2 times!
Killed
->8-->8-->8-->8-->8-->8-->8-->8-->8-->8-->8-

Various things I've tried:
- reverting to chromium(,-common,-sandbox) to 87.0.4280.88-0.3 -> same problem
- reverting to chromium(,-common,-sandbox) to 87.0.4280.88-0.3 -> same problem
- starting chromium with a fresh profile -> same problem

Installing debug symbols and starting `chromium -g` will result in the same
errors, except for chromium complaining about being started in single-process
mode.

One user on #debian-next IRC reported no such errors on sid and KDE, so it might
not effect all users. I *think* about a week ago chromium still ran fine (I only
use it for debugging purposes). Checking /var/log/apt/history.log, I don't see
any libva* packages being updated in that timeframe.

Regards,
Lee


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

Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  87.0.4280.88-0.4
ii  libasound2   1.2.4-1.1
ii  libatk-bridge2.0-0   2.38.0-1
ii  libatk1.0-0  2.36.0-2
ii  libatomic1   10.2.1-3
ii  libatspi2.0-02.38.0-2
ii  libavcodec58 7:4.3.1-5
ii  libavformat587:4.3.1-5
ii  libavutil56  7:4.3.1-5
ii  libc62.31-6
ii  libcairo21.16.0-5
ii  libcups2 2.3.3op1-4
ii  libdbus-1-3  1.12.20-1
ii  libdrm2  2.4.103-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libexpat12.2.10-1
ii  libflac8 1.3.3-2
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgbm1  20.3.2-1
ii  libgcc-s110.2.1-3
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.4-1
ii  libgtk-3-0   3.24.24-1
ii  libharfbuzz0b2.6.7-1
ii  libicu67 67.1-5
ii  libjpeg62-turbo  1:2.0.5-2
ii  libjsoncpp24 1.9.4-4
ii  liblcms2-2   2.9-4+b1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.60-1
ii  libopenjp2-7 2.3.1-1
ii  libopus0 1.3.1-0.1
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpulse014.0-2
ii  libre2-9 20201101+dfsg-2
ii  libsnappy1v5 1.1.8-1
ii  libstdc++6   10.2.1-3
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.6.12-1
ii  libx11-xcb1  2:1.7.0-1
ii  libxcb1  1.14-2.1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1   

Bug#979524: debian-reference: build-depends on libopencc2-data, which no longer exists

[Boyuan Yang]

Hi,

在 2021-01-08星期五的 09:49 +0800，xiao sheng wen(肖盛文)写道：
> Hi,
> 
>  libopencc2-data had change name to libopencc-data in bullseye
> sid.
> 
> As the opencc upstream had changed the version number, SONAME, etc.
> 
> Update debian-reference build-depends on libopencc-data should fix
> this bug.

This bug as well as the python2->3 migration has long been fixed in git
trunk. We just need another upload.

Osamu: do you have time to review all changes after 2.76 tag and make
another upload for debian-reference package? This will fix at least one
RC-buggy bug so it might be worthwhile to get fixed before freeze.

Thanks,
Boyuan Yang


> 在 2021/1/8 上午12:55, Ivo De Decker 写道:
> > package: src:debian-reference
> > version: 2.76
> > tags: bullseye sid ftbfs
> > severity: serious
> > 
> > Hi,
> > 
> > It seems debian-reference build-depends on libopencc2-data, which
> > no longer
> > exists.
> > 
> > Cheers,
> > 
> > Ivo
> > 

Bug#969275: marked as done (python-uvicorn: CVE-2020-7695)

[Debian Bug Tracking System]

Your message dated Sat, 09 Jan 2021 04:18:57 +
with message-id 
and subject line Bug#969275: fixed in python-uvicorn 0.13.3-1
has caused the Debian Bug report #969275,
regarding python-uvicorn: CVE-2020-7695
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.)


-- 
969275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-uvicorn
Version: 0.11.5-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1  0.11.3-1

Hi,

The following vulnerability was published for python-uvicorn.

CVE-2020-7695[0]:
| Uvicorn before 0.11.7 is vulnerable to HTTP response splitting. CRLF
| sequences are not escaped in the value of HTTP headers. Attackers can
| exploit this to add arbitrary headers to HTTP responses, or even
| return an arbitrary response body, whenever crafted input is used to
| construct HTTP headers.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-7695
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7695
[1] https://snyk.io/vuln/SNYK-PYTHON-UVICORN-570471
[2] https://github.com/encode/uvicorn/issues/719

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-uvicorn
Source-Version: 0.13.3-1
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-uvicorn 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, 08 Jan 2021 23:00:04 -0500
Source: python-uvicorn
Architecture: source
Version: 0.13.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sandro Tosi 
Closes: 969275 969276
Changes:
 python-uvicorn (0.13.3-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Sandro Tosi ]
   * New upstream release
 - Closes: #969275 CVE-2020-7695
 - Closes: #969276 CVE-2020-7694
   * debian/control
 - run wrap-and-sort
 - add httpx, pytest-mock, trustme to b-d, needed for tests
 - bump Standards-Version to 4.5.1 (no changes needed)
Checksums-Sha1:
 ebfffe1323ccaa7bf32e3b422edfc514ba717c6e 2468 python-uvicorn_0.13.3-1.dsc
 b3ff2458e7ba2fcb4eac0b38ba9f4e568c180840 495096 
python-uvicorn_0.13.3.orig.tar.xz
 2320db0df048272af97c5acaa8ac96227584686e 7420 
python-uvicorn_0.13.3-1.debian.tar.xz
 ff3499d217ce24817fc8cb67d191f072ff51f105 8519 
python-uvicorn_0.13.3-1_source.buildinfo
Checksums-Sha256:
 2b4a0d914b9599dc236ed28f342588accc511ec112d1bf1a8d5da8ef92fa7bfd 2468 
python-uvicorn_0.13.3-1.dsc
 ffe16af85ccab64387830953972ea91aa8b2647130d201e91305cb52e8516a87 495096 
python-uvicorn_0.13.3.orig.tar.xz
 efa714dde12db5f1e7aeff37184130de6e58873ee01be9ca038d066d18581147 7420 
python-uvicorn_0.13.3-1.debian.tar.xz
 c36e46bdb3f1254f555ddf03fa3285b48e851f8a1b08c5dbe8e9dc20e5b4d9a9 8519 
python-uvicorn_0.13.3-1_source.buildinfo
Files:
 db891cbd806a54fdc2e74b5ecd154aff 2468 python optional 
python-uvicorn_0.13.3-1.dsc
 5ece58af87b38d46040c14ea07859eb7 495096 python optional 
python-uvicorn_0.13.3.orig.tar.xz
 9021abc4d659376b54ddd535595a8380 7420 python optional 
python-uvicorn_0.13.3-1.debian.tar.xz
 5f57743d4a1996f8ef7cf33fba17e840 8519 python optional 
python-uvicorn_0.13.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl/5KmIACgkQh588mTgB
qU8Qtg//czIVIokl7RJaLBZAKG/vrYIsLhr2uX9TcHKSUMFDBp1o8WhSlZgDBfnh
GrXvstt9dcUQGoozFmdID9lsZXDVj+8HktOp6pkyeJUtNt16Vpg+yoYbMkrK1xZN
wmc6aLeL0jg5SOKTnPHlnLzzs3mzU9PiG2AUpgoASL63UE3tkXMd0gAVhBqYpVv2

Bug#969276: marked as done (python-uvicorn: CVE-2020-7694)

[Debian Bug Tracking System]

Your message dated Sat, 09 Jan 2021 04:18:57 +
with message-id 
and subject line Bug#969276: fixed in python-uvicorn 0.13.3-1
has caused the Debian Bug report #969276,
regarding python-uvicorn: CVE-2020-7694
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.)


-- 
969276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-uvicorn
Version: 0.11.5-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/encode/uvicorn/issues/723
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 0.11.3-1

Hi,

The following vulnerability was published for python-uvicorn.

CVE-2020-7694[0]:
| This affects all versions of package uvicorn. The request logger
| provided by the package is vulnerable to ASNI escape sequence
| injection. Whenever any HTTP request is received, the default
| behaviour of uvicorn is to log its details to either the console or a
| log file. When attackers request crafted URLs with percent-encoded
| escape sequences, the logging component will log the URL after it's
| been processed with urllib.parse.unquote, therefore converting any
| percent-encoded characters into their single-character equivalent,
| which can have special meaning in terminal emulators. By requesting
| URLs with crafted paths, attackers can: * Pollute uvicorn's access
| logs, therefore jeopardising the integrity of such files. * Use ANSI
| sequence codes to attempt to interact with the terminal emulator
| that's displaying the logs (either in real time or from a file).


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-7694
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7694
[1] https://snyk.io/vuln/SNYK-PYTHON-UVICORN-575560
[2] https://github.com/encode/uvicorn/issues/723

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-uvicorn
Source-Version: 0.13.3-1
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-uvicorn 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, 08 Jan 2021 23:00:04 -0500
Source: python-uvicorn
Architecture: source
Version: 0.13.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sandro Tosi 
Closes: 969275 969276
Changes:
 python-uvicorn (0.13.3-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Sandro Tosi ]
   * New upstream release
 - Closes: #969275 CVE-2020-7695
 - Closes: #969276 CVE-2020-7694
   * debian/control
 - run wrap-and-sort
 - add httpx, pytest-mock, trustme to b-d, needed for tests
 - bump Standards-Version to 4.5.1 (no changes needed)
Checksums-Sha1:
 ebfffe1323ccaa7bf32e3b422edfc514ba717c6e 2468 python-uvicorn_0.13.3-1.dsc
 b3ff2458e7ba2fcb4eac0b38ba9f4e568c180840 495096 
python-uvicorn_0.13.3.orig.tar.xz
 2320db0df048272af97c5acaa8ac96227584686e 7420 
python-uvicorn_0.13.3-1.debian.tar.xz
 ff3499d217ce24817fc8cb67d191f072ff51f105 8519 
python-uvicorn_0.13.3-1_source.buildinfo
Checksums-Sha256:
 2b4a0d914b9599dc236ed28f342588accc511ec112d1bf1a8d5da8ef92fa7bfd 2468 
python-uvicorn_0.13.3-1.dsc
 ffe16af85ccab64387830953972ea91aa8b2647130d201e91305cb52e8516a87 495096 
python-uvicorn_0.13.3.orig.tar.xz
 efa714dde12db5f1e7aeff37184130de6e58873ee01be9ca038d066d18581147 7420 
python-uvicorn_0.13.3-1.debian.tar.xz
 c36e46bdb3f1254f555ddf03fa3285b48e851f8a1b08c5dbe8e9dc20e5b4d9a9 8519 
python-uvicorn_0.13.3-1_source.buildinfo
Files:
 db891cbd806a54fdc2e74b5ecd154aff 2468 python optional 

Processed: Re: xfce4-sensors-plugin: FTBFS: NVCtrlLib.h:42:1: error: unknown type name ‘Bool’; did you mean ‘bool’?

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libxnvctrl-dev
Bug #978192 [src:xfce4-sensors-plugin] xfce4-sensors-plugin: FTBFS: 
NVCtrlLib.h:42:1: error: unknown type name ‘Bool’; did you mean ‘bool’?
Bug reassigned from package 'src:xfce4-sensors-plugin' to 'libxnvctrl-dev'.
No longer marked as found in versions xfce4-sensors-plugin/1.3.0-3.
Ignoring request to alter fixed versions of bug #978192 to the same values 
previously set
> affects -1 + src:xfce4-sensors-plugin
Bug #978192 [libxnvctrl-dev] xfce4-sensors-plugin: FTBFS: NVCtrlLib.h:42:1: 
error: unknown type name ‘Bool’; did you mean ‘bool’?
Added indication that 978192 affects src:xfce4-sensors-plugin

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

Bug#978192: xfce4-sensors-plugin: FTBFS: NVCtrlLib.h:42:1: error: unknown type name ‘Bool’; did you mean ‘bool’?

[Andreas Beckmann]

Followup-For: Bug #978192
Control: reassign -1 libxnvctrl-dev
Control: affects -1 + src:xfce4-sensors-plugin

NVCtrlLib.h uses macros from X11/Xlib.h but does not include that header.
So including NVCtrlLib.h only worked if X11/Xlib.h was accidentally
included earlier, which no longer is the case: rebuilding
xfce4-sensors-plugin/sid fails in sid and bullseye, but works in buster.

In buster the include chain was
  /usr/include/xfce4/libxfce4panel-2.0/libxfce4panel/xfce-panel-macros-46.h
  /usr/include/gtk-3.0/gdk/gdkx.h
  /usr/include/X11/Xlib.h
but in bullseye
  /usr/include/xfce4/libxfce4panel-2.0/libxfce4panel/xfce-panel-macros.h
no longer includes gdkx.h
And nvidia.c itself includes NVCtrlLib.h and X11/Xlib.h in the wrong^Wunlucky
order.


Andreas

Bug#979614: seamly2d: virtually dead fork of valentina

[Jonas Smedegaard]

Package: seamly2d
Version: 0.6.0.2+20201207+ds-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Seamly2D is a fork of Valentina.  Valentina is already in Debian.

Original author Roman Telezhynskyi a.k.a. dismine developed the code
until git commit a7cadff on August 27, 2017.

Since then, he continued develop under original project name Valentina,
whereas Seamly2D virtually stalled with no substantial code changes ,
only superficial changes to build infrastructure, locales, and icons.

Check for yourself:

  git clone https://github.com/FashionFreedom/Seamly2D
  cd Seamly2D
  git diff --stat -p --ignore-all-space a7cadff..

...compared to Valentina:

  git clone https://gitlab.com/smart-pattern/valentina.git
  cd valentina
  git diff --stat -p --ignore-all-space 3ea3371..

Or skim through those histories e.g. with "tig".


I recommend that Debian does not carry Seamly3D, and encourage helping
out with maintaining Valentina instead.

If you disagree, then I just wish you the best of luck with Seamly3D.
I admit the severity is bloated - feel free to lower as you see fit.


Kind regards,

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/5GPIACgkQLHwxRsGg
ASEzJA//QzXmeEZOhHcQ/qUJVtXoepXcWCmSnSxHI+4e0vR+ruDEaQhzM6teA4Bj
WakhTeIvg3mUE3QYpzI1JhD+YbDao3ifZ17zJ7TmLzEdA30NBzk5DXkjR0Eza2Lp
o8PQEqBNPoGd7yU1LdfdlzbSezaR/KHZswPWSRsmPqmTxMWUAknQykxj3Tmd4bb/
jyf+Bels7bBbnkRf1nluKnIbI+KpjL3/2lIq2WOskS8aoMYWhFjCRj22BxT6KxQI
33dgEn+rJGsqfHPKDfvdRZK/LbvS7gb0uoLc6aUbsA7dqNH37DEcXS2tfmm54l2F
jkIQJZR50SToVDTMmal9XNim1aDj870OogjdZHQKVecCmEaTrQgdAJg+B8vTt+ks
5K8MtvGHThaz5nymos6f27qUilvxw19w0DJnUobtCRocwL//dkSmxfW/l3J0qQQo
3J3p85Y16xycP90Z7v442wEYCNJ4NuPfA/qML9o1tqH//KJEk5rYYZAVKbMLUBbC
JhRpCA2fGe6wc3NaAaza4V/26lYrgUDBAAJiYqDXRFQ6lKst3+4wrpj4bywI058k
ZTAhyleLmeyvYDNwrghEbqJDevOouBh4n10J84itLGF/YDH7gsFpMxA/hK5X8FS5
GyVoh1M7N0/vXBqrT+8iJnrFIyIn58CorZl/HHcRhp+Hbblxc6o=
=OVq+
-END PGP SIGNATURE-

Processed: found 972729 in 0.0~git20200918.3dc0328-3, found 972306 in 4:20.12.0-1, found 972302 in 5.2.0-2 ...

[Debian Bug Tracking System]

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

> found 972729 0.0~git20200918.3dc0328-3
Bug #972729 [gloo] gloo: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
There is no source info for the package 'gloo' at version 
'0.0~git20200918.3dc0328-3' with architecture ''
Unable to make a source version for version '0.0~git20200918.3dc0328-3'
Marked as found in versions 0.0~git20200918.3dc0328-3.
> found 972306 4:20.12.0-1
Bug #972306 [analitza] analitza: FTBFS with 
DEB_BUILD_OPTIONS=reproducible=+fixfilepath
There is no source info for the package 'analitza' at version '4:20.12.0-1' 
with architecture ''
Unable to make a source version for version '4:20.12.0-1'
Marked as found in versions 4:20.12.0-1.
> found 972302 5.2.0-2
Bug #972302 [grantlee5] grantlee5: FTBFS with 
DEB_BUILD_OPTIONS=reproducible=+fixfilepath
There is no source info for the package 'grantlee5' at version '5.2.0-2' with 
architecture ''
Unable to make a source version for version '5.2.0-2'
Marked as found in versions 5.2.0-2.
> found 972300 20.12.0-1
Bug #972300 [keditbookmarks] keditbookmarks: FTBFS with 
DEB_BUILD_OPTIONS=reproducible=+fixfilepath
Marked as found in versions keditbookmarks/20.12.0-1.
> found 972298 5:0.26.4-1
Bug #972298 [okteta] okteta: FTBFS with 
DEB_BUILD_OPTIONS=reproducible=+fixfilepath
Marked as found in versions okteta/5:0.26.4-1.
> found 972294 0.9.4-1
Bug #972294 [openorienteering-mapper] openorienteering-mapper: FTBFS with 
DEB_BUILD_OPTIONS=reproducible=+fixfilepath 
Marked as found in versions openorienteering-mapper/0.9.4-1.
> found 972297 0.16.2-2
Bug #972297 [scram] scram: FTBFS with 
DEB_BUILD_OPTIONS=reproducible=+fixfilepath
Marked as found in versions scram/0.16.2-2.
> tags 956958 + sid bullseye
Bug #956958 [simple-cdd] simple-cdd on Bullseye gives reprepro error
Added tag(s) bullseye and sid.
> found 972301 3.5.0+dfsg1-4
Bug #972301 {Done: Jochen Sprickerhof } [ignition-common] 
ignition-common: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
There is no source info for the package 'ignition-common' at version 
'3.5.0+dfsg1-4' with architecture ''
Unable to make a source version for version '3.5.0+dfsg1-4'
Marked as found in versions 3.5.0+dfsg1-4.
> found 972308 0.2.1-1
Bug #972308 {Done: Stuart Prescott } [kookbook] kookbook: 
FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
Marked as found in versions kookbook/0.2.1-1.
> tags 972308 + sid bullseye
Bug #972308 {Done: Stuart Prescott } [kookbook] kookbook: 
FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
956958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956958
972294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972294
972297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972297
972298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972298
972300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972300
972301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972301
972302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972302
972306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972306
972308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972308
972729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#978954: pepperflashplugin-nonfree: should not be part of next stable Debian release

[Gunnar Hjalmarsson]

Another reminder about why it's important to handle this also in the 
supported releases:


https://askubuntu.com/q/1306202

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

Bug#976780: marked as done (pycuda needs a manual upload to drop Python 3.8 support)

[Debian Bug Tracking System]

Your message dated Sat, 09 Jan 2021 01:25:37 +
with message-id 
and subject line Bug#976780: fixed in pycuda 2020.1~dfsg-1
has caused the Debian Bug report #976780,
regarding pycuda needs a manual upload to drop Python 3.8 support
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.)


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

Sources+binaries might be easier than a manual binNMU.
--- End Message ---
--- Begin Message ---
Source: pycuda
Source-Version: 2020.1~dfsg-1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated pycuda 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, 09 Jan 2021 01:55:29 +0100
Source: pycuda
Binary: python-pycuda-doc python3-pycuda python3-pycuda-dbg
Architecture: source all amd64
Version: 2020.1~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 python-pycuda-doc - module to access Nvidia‘s CUDA computation API 
(documentation)
 python3-pycuda - Python 3 module to access Nvidia‘s CUDA parallel computation 
API
 python3-pycuda-dbg - Python 3 module to access Nvidia‘s CUDA API (debug 
extensions)
Closes: 976780
Changes:
 pycuda (2020.1~dfsg-1) unstable; urgency=medium
 .
   * New upstream release.  (Closes: #976780) (LP: #1899750)
   * Refresh patches.
   * Let uscan repack the main tarball with a ~dfsg suffix.
   * Add create-compyte-tarball target to pack compyte as a separate component
 tarball.
   * Fix building twice in a row.
Checksums-Sha1:
 83040437a543230641ee79abf76d3e4b46321ffd 2812 pycuda_2020.1~dfsg-1.dsc
 81b05d1cdff2fd7c61531be84d3a4ae37076b3a3 47344 
pycuda_2020.1~dfsg.orig-compyte.tar.xz
 22bb3780d613255be6bc60690a359c0957a4b62f 144396 pycuda_2020.1~dfsg.orig.tar.xz
 d1df8451117e34a082e0ed23a09bb952db0aef98 22480 
pycuda_2020.1~dfsg-1.debian.tar.xz
 4fbef6148477dab99e6defeb9fa818627be70f6c 12549 
pycuda_2020.1~dfsg-1_amd64.buildinfo
 e98d98ea8dee8877c38e8a6832f2c98007d0df8c 121516 
python-pycuda-doc_2020.1~dfsg-1_all.deb
 160754309b1b0e9e0f8ca8b9fe6d6c25fbfebaa1 6312756 
python3-pycuda-dbg_2020.1~dfsg-1_amd64.deb
 7e4bc0faaf485a2c806874904ae550df07ecc40b 323756 
python3-pycuda_2020.1~dfsg-1_amd64.deb
Checksums-Sha256:
 52cd61f834bb4a991c8eaf3b7762d4776dc7d6744ed17311f56a76ca0d7b19d0 2812 
pycuda_2020.1~dfsg-1.dsc
 3271fb82c0eba4674e80a456dcdeee753faf4894671ac5e3cbb3037d017ce499 47344 
pycuda_2020.1~dfsg.orig-compyte.tar.xz
 a9c5c9557ae999a3453d98aa72ea45aa4c9e4c83bbcbc495c2d84a3ccf740590 144396 
pycuda_2020.1~dfsg.orig.tar.xz
 d3b778b768ff52fa6bc168b8a222d869888adb217d15802b516577121a392d86 22480 
pycuda_2020.1~dfsg-1.debian.tar.xz
 ab56a7219ec00e3d742aefae6040d085fb0c7ed01744fd4ec07244edf61d998e 12549 
pycuda_2020.1~dfsg-1_amd64.buildinfo
 36719a8064a43f7479d8590395bdd2d9eb0f8d22ec1066971d4e89c3472b03a1 121516 
python-pycuda-doc_2020.1~dfsg-1_all.deb
 a8be1a1fd41a9ae81c33d57b8aaed22cdddffcd4337686dba9a8456f15ff0d12 6312756 
python3-pycuda-dbg_2020.1~dfsg-1_amd64.deb
 b1d59550b6e20433902fd9f1e66a850fccdd1caf2de4e2ced9185f49d9f46a49 323756 
python3-pycuda_2020.1~dfsg-1_amd64.deb
Files:
 cb3f9458621ab100d740e0201247802f 2812 contrib/python optional 
pycuda_2020.1~dfsg-1.dsc
 2b19e67078ff1fd0987cf5b6c5c89866 47344 contrib/python optional 
pycuda_2020.1~dfsg.orig-compyte.tar.xz
 aa73d81ec048ddbc0ca92ae8209cde30 144396 contrib/python optional 
pycuda_2020.1~dfsg.orig.tar.xz
 54b74f477a97a18d345046c9a99bef50 22480 contrib/python optional 
pycuda_2020.1~dfsg-1.debian.tar.xz
 e0127b57e25f847bdd52ac6c323bed5e 12549 contrib/python optional 
pycuda_2020.1~dfsg-1_amd64.buildinfo
 c65958a2ee9421d5284a2dca3962a9d7 121516 contrib/doc optional 
python-pycuda-doc_2020.1~dfsg-1_all.deb
 db34ab683f6414fa99ed918a12e32339 6312756 contrib/debug optional 

Bug#979601: marked as done (git-lfs: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Sat, 09 Jan 2021 01:04:19 +
with message-id 
and subject line Bug#979601: fixed in git-lfs 2.13.1-2
has caused the Debian Bug report #979601,
regarding git-lfs: autopkgtest failure
to be marked as done.

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

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


-- 
979601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-lfs
Version: 2.13.1-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

git-lfs is currently unable to migrate to testing because it fails its
autopkgtest:
| rm obj-x86_64-linux-gnu/bin/cmd
| rm: cannot remove 'obj-x86_64-linux-gnu/bin/cmd': No such file or directory
| make[1]: *** [debian/rules:22: override_dh_auto_build] Error 1
| make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.yac8wpzf/downtmp/autopkgtest_tmp'
| make: *** [debian/rules:12: build] Error 2
| autopkgtest [21:23:16]: test dh-golang-autopkgtest: ---]
| autopkgtest [21:23:16]: test dh-golang-autopkgtest:  - - - - - - - - - - 
results - - - - - - - - - -
| dh-golang-autopkgtest FAIL non-zero exit status 2

See
https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-lfs/9492689/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: git-lfs
Source-Version: 2.13.1-2
Done: Stephen Gelman 

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

Debian distribution maintenance software
pp.
Stephen Gelman  (supplier of updated git-lfs 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, 08 Jan 2021 17:20:36 -0600
Source: git-lfs
Architecture: source
Version: 2.13.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Stephen Gelman 
Closes: 979601
Changes:
 git-lfs (2.13.1-2) unstable; urgency=medium
 .
   * Only remove superfluous files during build if they exist (Closes: #979601)
Checksums-Sha1:
 6730be4815c848a73795ec89ff53ed33ba92797c 2755 git-lfs_2.13.1-2.dsc
 3b26567d30eb3f82bba769a9316d1c9e6b790f54 4380 git-lfs_2.13.1-2.debian.tar.xz
 d2c8abd45c0902273e1792acc132f7a239731e1f 11066 git-lfs_2.13.1-2_amd64.buildinfo
Checksums-Sha256:
 556e97b1872e2978f85ea9fc67293d18274fbbcb5b6a37b5923742e47cdfc4fc 2755 
git-lfs_2.13.1-2.dsc
 3e510246e96e7fbc7e878674b0d1273d2236c19ae24d3798952ea21b643eb856 4380 
git-lfs_2.13.1-2.debian.tar.xz
 225870925c16ea94167416a329c84506e8abfda6e7b40cf2ede427171bb576d4 11066 
git-lfs_2.13.1-2_amd64.buildinfo
Files:
 c4a8f083af9601a58dbbe460fca8e8c3 2755 vcs optional git-lfs_2.13.1-2.dsc
 34e89a5afc3c9711fd87c00127ecacd2 4380 vcs optional 
git-lfs_2.13.1-2.debian.tar.xz
 0ad5fdb024c618d48803ebcb0cb5a85e 11066 vcs optional 
git-lfs_2.13.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAwFiEEPwDop1BN06KlsbfijqM4hED8f1wFAl/4/BkSHHNzZ2VsbUBk
ZWJpYW4ub3JnAAoJEI6jOIRA/H9cA04P+OpGRx4YyjxaZwvOfOg7yefSFXIruCA7
6UYo4IaFYzj7Mt78COmUVKWnKmMXRMDX3IYFn3cmEYR0MhYtnKKg93Tbrv2KNE8B
hAhS9RMDKr3lAKFsVEl5/8DdWRLEI3FuZj5vKjixfN8ADJXJW+myW2BgmpARXol6
1UJXmqPNlfxFiErCKZ2S6/zlVUw3ct3f70DCsDqdMMsKpgVhZmmdbJcZKV9KlSps
p32aRIJETKdhHSba04plunGFD6/bYHM4dIXQCVtHAjOcxG7hA0RNrFh6wxDjhBCC
4oiV41kQJQIhTDjUCGb3MBDmOqAoeQRp4X/B9YJe0F8azFCyrqo5HkGrreHUyXz0
KRt5x18F2Xuzb1H9AN0cPHO4BGuUYspan8mvdw8Y6eMonkBBe8j7oXpjV4v+iG9L
bSCBqI/s+9vof0nJDgTN1OaV7ph3giZfq9o6mVvvhZ+BQ+i6xiOgN1otnLPE3mKD
z2qtIrLmc53Xj2PHi6JBxy6cNr3Qu7ohdbwVOJhf7xPKMCWWnKSh6RWFXTRg3yk5
mJSNwsv6cHUMCJbAO3t30j3QdAvHHkkqhJaoB8we7i+5aDQIaWz/b0z1bDxnCOj3
QlNVWNg6BOVkcgieYtsd9qvQLMDZHZ4XhV/XX6ghKUJ7GofUAViBRG4RjnxoqE9Q
4jYffke2ULM=
=T8B1
-END PGP SIGNATURE End Message ---

Processed: severity of 978336 is normal

[Debian Bug Tracking System]

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

> severity 978336 normal
Bug #978336 {Done: Adrian Bunk } [src:picolisp] picolisp: 
FTBFS: flood -- Undefined
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

[Lisandro Damián Nicanor Pérez Meyer]

On Fri, 8 Jan 2021 at 21:15, Lisandro Damián Nicanor Pérez Meyer
 wrote:
>
> Hi! Explicitely CCing my bug, since it seems it missed my previous reply.
>
> On Fri, 8 Jan 2021 at 20:49, Guillem Jover  wrote:
> >
> > On Fri, 2021-01-08 at 19:23:13 -0300, Lisandro Damián Nicanor Pérez Meyer 
> > wrote:
> > > [snip]
> > > > We did a full archive rebuild testing this change, and I provided
> > > > patches to all known affected packages several months ago. It is a
> > > > one-line change in debian/rules in most cases:
> > > >
> > > >   
> > > > https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=reproducible-builds%40lists.alioth.debian.org=fixfilepath
> > > >
> > > > It seems there are less than 10 packages left that have not applied the
> > > > patch.
> > > >
> > > > Longer-term, it would be nice to be able to fix QFINDTESTDATA to be
> > > > compatible, sure.
> > >
> > > >From a couple of "fixes":
> > >
> > > -export DEB_BUILD_MAINT_OPTIONS = hardening=+all
> > > +# Disable fixfilepath feature, as it triggers build failures when
> > > +# enabled.
> > > +export DEB_BUILD_MAINT_OPTIONS = hardening=+all reproducible=-fixfilepath
> > >
> > > That's not a fix but hiding the dirt under the carpet. You are not
> > > fixing the root issue nor the reproducibility one.
> >
> > I'm not sure I understand this objection. Reverting the patch from
> > dpkg would do the same but at a global scale, which would make many
> > packages that would benefit from the new default, not reproducible,
> > and would still "hide the dirt under the carpet" for the very few
> > that would otherwise need the option disabled.

In fact most of those packages would not be unreproducible if the
environment would be the same as the original build. That includes the
build path.

I do understand that it is *desirable* to be able to reproducibly
build a package no matter the build path, but that's just desirable.

The real fix here is to do the right thing, ie, provide the very same
environment as the original build, including the build path.

So again, mangling __FILE__ should not be a default.


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

Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

[Lisandro Damián Nicanor Pérez Meyer]

Hi! Explicitely CCing my bug, since it seems it missed my previous reply.

On Fri, 8 Jan 2021 at 20:49, Guillem Jover  wrote:
>
> On Fri, 2021-01-08 at 19:23:13 -0300, Lisandro Damián Nicanor Pérez Meyer 
> wrote:
> > [snip]
> > > We did a full archive rebuild testing this change, and I provided
> > > patches to all known affected packages several months ago. It is a
> > > one-line change in debian/rules in most cases:
> > >
> > >   
> > > https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=reproducible-builds%40lists.alioth.debian.org=fixfilepath
> > >
> > > It seems there are less than 10 packages left that have not applied the
> > > patch.
> > >
> > > Longer-term, it would be nice to be able to fix QFINDTESTDATA to be
> > > compatible, sure.
> >
> > >From a couple of "fixes":
> >
> > -export DEB_BUILD_MAINT_OPTIONS = hardening=+all
> > +# Disable fixfilepath feature, as it triggers build failures when
> > +# enabled.
> > +export DEB_BUILD_MAINT_OPTIONS = hardening=+all reproducible=-fixfilepath
> >
> > That's not a fix but hiding the dirt under the carpet. You are not
> > fixing the root issue nor the reproducibility one.
>
> I'm not sure I understand this objection. Reverting the patch from
> dpkg would do the same but at a global scale, which would make many
> packages that would benefit from the new default, not reproducible,
> and would still "hide the dirt under the carpet" for the very few
> that would otherwise need the option disabled.

__FILE__ has defined behaviour: the path the preprocessor finds. The
only place where __FILE__ is mangled, to the best of my knowledge, is
Debian. So expecting that any developer out there makes code that runs
with this Debian specific variation is unreasonable. In other words:
breaking perfectly valid code *by default*, even in the name of
reproducibility, is not right.

>
> Disabling this option in these few places gives you room to possibly
> look for a fix, or not, w/o the pressure of the freeze, while not
> affecting the other packages.

But still breaking perfectly valid code.


> As stated in the thread in d-d, I still fail to see the weight of the
> objections, TBH. And given this I'm planning on closing the bug in
> dpkg.

In that case we at least should agree that we disagree, so I would ask
the tech-ctte to review this case.



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

Bug#961958: marked as done (librdkafka++1: Zero-size library on several architectures)

[Debian Bug Tracking System]

Your message dated Sat, 9 Jan 2021 00:13:15 +0200
with message-id <20210108221312.ga26...@tty.gr>
and subject line Re: Bug#961958: librdkafka++1: Zero-size library on several 
architectures
has caused the Debian Bug report #961958,
regarding librdkafka++1: Zero-size library on several architectures
to be marked as done.

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

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


-- 
961958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librdkafka++1
Version: 1.4.2-1
Severity: grave
Tags: patch fixed-upstream
Forwarded: https://github.com/edenhill/librdkafka/pull/2874

https://buildd.debian.org/status/fetch.php?pkg=librdkafka=amd64=1.4.2-1=1589341196=0

...
librdkafka++1_1.4.2-1_amd64.deb
...
-rw-r--r-- root/root 0 2020-05-13 03:17 
./usr/lib/x86_64-linux-gnu/librdkafka++.so.1
...
--- End Message ---
--- Begin Message ---
Version: 1.5.0-1

On Tue, Dec 15, 2020 at 03:55:32PM +0100, s3v wrote:
> this issue seems fixed after 1.5.0-2 upload.

Indeed, and in fact fixed with 1.5.0-1 as well. Thanks!

Faidon--- End Message ---

Bug#966877: termtris: FTBFS: ld: src/game.o:/<>/src/game.h:21: multiple definition of `quit'; src/ansi.o:/<>/src/game.h:21: first defined here

[Logan Rosen]

Package: termtris
Version: 1.3-1
Followup-For: Bug #966877
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/gcc-10.patch: Fix compilation with GCC 10.

Thanks for considering the patch.

Logan
diff -Nru termtris-1.3/debian/patches/gcc-10.patch 
termtris-1.3/debian/patches/gcc-10.patch
--- termtris-1.3/debian/patches/gcc-10.patch1969-12-31 19:00:00.0 
-0500
+++ termtris-1.3/debian/patches/gcc-10.patch2021-01-08 17:44:33.0 
-0500
@@ -0,0 +1,46 @@
+--- a/src/game.h
 b/src/game.h
+@@ -18,12 +18,12 @@
+ #ifndef GAME_H_
+ #define GAME_H_
+ 
+-int quit;
+-long tick_interval;
+-int use_bell;
+-int monochrome;
++extern int quit;
++extern long tick_interval;
++extern int use_bell;
++extern int monochrome;
+ 
+-int term_width, term_height;
++extern int term_width, term_height;
+ 
+ int init_game(void);
+ void cleanup_game(void);
+--- a/src/game.c
 b/src/game.c
+@@ -26,6 +26,9 @@
+ #include "ansi.h"
+ #include "scoredb.h"
+ 
++int quit;
++long tick_interval;
++
+ enum {
+   G_DIAMOND   = 0x04,
+   G_CHECKER   = 0xb1,
+--- a/src/main.c
 b/src/main.c
+@@ -35,6 +35,11 @@
+ #define USE_JOYSTICK
+ #endif
+ 
++int use_bell;
++int monochrome;
++
++int term_width, term_height;
++
+ int init(void);
+ void cleanup(void);
+ int parse_args(int argc, char **argv);
diff -Nru termtris-1.3/debian/patches/series termtris-1.3/debian/patches/series
--- termtris-1.3/debian/patches/series  2019-06-06 03:01:11.0 -0400
+++ termtris-1.3/debian/patches/series  2021-01-08 17:44:04.0 -0500
@@ -1 +1,2 @@
 0001_install_to_usr_game.patch
+gcc-10.patch

Processed: Re: termtris: FTBFS: ld: src/game.o:/<>/src/game.h:21: multiple definition of `quit'; src/ansi.o:/<>/src/game.h:21: first defined here

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #966877 [src:termtris] termtris: FTBFS: ld: 
src/game.o:/<>/src/game.h:21: multiple definition of `quit'; 
src/ansi.o:/<>/src/game.h:21: first defined here
Added tag(s) patch.

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

Processed: Re: uronode: ftbfs with GCC-10

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #957902 [src:uronode] uronode: ftbfs with GCC-10
Added tag(s) patch.

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

Bug#957902: uronode: ftbfs with GCC-10

[Logan Rosen]

Package: uronode
Version: 2.10-1
Followup-For: Bug #957902
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/gcc-10.patch: Fix compilation with GCC 10.

Thanks for considering the patch.

Logan
diff -Nru uronode-2.10/debian/patches/gcc-10.patch 
uronode-2.10/debian/patches/gcc-10.patch
--- uronode-2.10/debian/patches/gcc-10.patch1969-12-31 19:00:00.0 
-0500
+++ uronode-2.10/debian/patches/gcc-10.patch2021-01-08 17:16:03.0 
-0500
@@ -0,0 +1,13 @@
+--- a/util.c
 b/util.c
+@@ -17,8 +17,8 @@
+ #include "procinfo.h"
+ 
+ static char buf[256];
+-char *HostName;
+-char *Prompt;
++extern char *HostName;
++extern char *Prompt;
+ 
+ void node_msg(const char *fmt, ...)
+ {
diff -Nru uronode-2.10/debian/patches/series uronode-2.10/debian/patches/series
--- uronode-2.10/debian/patches/series  2019-08-17 17:43:25.0 -0400
+++ uronode-2.10/debian/patches/series  2021-01-08 17:15:15.0 -0500
@@ -4,3 +4,4 @@
 install-dir-creation
 makefile-install-locations
 
+gcc-10.patch

Bug#979569: marked as done (frama-c ftbfs on armel, mipsel and mips64el)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 21:18:26 +
with message-id 
and subject line Bug#979569: fixed in frama-c 20201209+titanium-3
has caused the Debian Bug report #979569,
regarding frama-c ftbfs on armel, mipsel and mips64el
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.)


-- 
979569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package:src:frama-c
Version: 20201209+titanium-2
Severity: serious
Tags: sid bullseye

[...]
ocamlfind: Not supported in your configuration: ocamlopt
make[1]: *** [share/Makefile.generic:88: src/libraries/stdlib/extlib.cmx] Error 
2
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j4 returned exit code 2
--- End Message ---
--- Begin Message ---
Source: frama-c
Source-Version: 20201209+titanium-3
Done: Ralf Treinen 

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated frama-c 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, 08 Jan 2021 21:32:55 +0100
Source: frama-c
Architecture: source
Version: 20201209+titanium-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Ralf Treinen 
Closes: 979569
Changes:
 frama-c (20201209+titanium-3) unstable; urgency=medium
 .
   * Patch 0001-E-ACSL-avoid-cmx-dependencies-when-in-a-byte-only-ar.patch:
 fix FTBFS on bytecode architectures (closes: #979569).
 Thanks to André Maroneze for the patch
   * Add Recommends libwhy3-ocaml-dev, as it is needed by frama-c to run why3.
   * Test wp:
 - add test-dependency libwhy3-ocaml-dev
 - run why3 config
Checksums-Sha1:
 d3798960a1951d34a589d4b2b4987a49eb4b3515 2367 frama-c_20201209+titanium-3.dsc
 97aabdd2df5477d3366b9127e0fdfb6ae832e7cc 15924 
frama-c_20201209+titanium-3.debian.tar.xz
 a52e44d3c6b8939852e12861c0cd679066116baa 15723 
frama-c_20201209+titanium-3_source.buildinfo
Checksums-Sha256:
 72f884ba7dcb8fe28951899f76f015c07c0d826c84fe1149e94eaf3eb8c99911 2367 
frama-c_20201209+titanium-3.dsc
 cdb46bb4b366829f2083666d12975ec3dfb159139f243a46ac08483f4b244e88 15924 
frama-c_20201209+titanium-3.debian.tar.xz
 01b47ae4b32bc8cb89f6dbbed22bf0eeb0c6745185125cd823cd4a44a3ba0877 15723 
frama-c_20201209+titanium-3_source.buildinfo
Files:
 95012496c270a37380cf9a31f1dae33f 2367 devel optional 
frama-c_20201209+titanium-3.dsc
 bc1250ec1e3442eefaca49f6e419b96c 15924 devel optional 
frama-c_20201209+titanium-3.debian.tar.xz
 12c17ba925f16280694398cf8e2c46a5 15723 devel optional 
frama-c_20201209+titanium-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEAgVIKeEtDyqOZI5idFxHZtTKzf8FAl/4yPsACgkQdFxHZtTK
zf9sgw//WqwYOGc12KOTawzpk9dMxa/0nEi2IglH14GvJ1GUtH9S8SKqgsXH2MYp
jQVY1PhcQUGgQSD8SG02Q1cqsBoRQvsIeQALsHg5qgUcxydaCsaGDp2LbKotq6gl
26MRHka4hlrSZIpy/b3hwG5tVhLHRPruXRDIXtCRXqcdwN4K9YAggW4boMqtqLRJ
RZZ64OMociF5mEnbwhazkFziRSnPLYE0N4euEgVmqgAtLwGsgurkhBdnnElkNNpK
2FWDb59uYuY7bS5HH8irBXfXByVtABm60SIMu2oEHIn3rtVTaLowZnpDxRnZENp9
8mQGmZxWmwn+RwI2qPKBwFeGMmGtW4hiCuDoZN6aO8reHXY6OMZP9asTRq9qS5lZ
qyAVzxrBRWMM2KmoxluJ4a7oTvdxEihEtxpTisu9GEjWta3YCMcckOgYfelu8rzE
dTlyImrDCPbZY4dD7rBWdgHUV8BKiKpnEFXTwCvOuOE+uNZD7qfxqSiNvbQznC2a
HAUCWVm5+NLCTSqJINHcJitb/Q6lCzpJFsnwGtigchz4LCnYxCWE7lDyUCJijTb0
KFfiGQDuL9pptakI7L1nTzXW19/vRxwO3vpmOSXITofVf1B97aJOB/6CLFigqBrl
gxyif6CHaAmj3oHXNFQaHT1KNSBeKeLF3+KhKJaauOZb8B0+GF8=
=2xtn
-END PGP SIGNATURE End Message ---

Bug#979601: git-lfs: autopkgtest failure

[Sebastian Ramacher]

Source: git-lfs
Version: 2.13.1-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

git-lfs is currently unable to migrate to testing because it fails its
autopkgtest:
| rm obj-x86_64-linux-gnu/bin/cmd
| rm: cannot remove 'obj-x86_64-linux-gnu/bin/cmd': No such file or directory
| make[1]: *** [debian/rules:22: override_dh_auto_build] Error 1
| make[1]: Leaving directory 
'/tmp/autopkgtest-lxc.yac8wpzf/downtmp/autopkgtest_tmp'
| make: *** [debian/rules:12: build] Error 2
| autopkgtest [21:23:16]: test dh-golang-autopkgtest: ---]
| autopkgtest [21:23:16]: test dh-golang-autopkgtest:  - - - - - - - - - - 
results - - - - - - - - - -
| dh-golang-autopkgtest FAIL non-zero exit status 2

See
https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-lfs/9492689/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#979562: lightdm session termination does not stop xscreensaver

[Jamie Zawinski]

> In xscreensaver (or maybe lightdm).
> Why is xscreensaver started in the lightdm session anyway?
> Is xscreensaver really usable as a per user service or should it be per 
> session?
> Why is the lightdm xscreensaver instance interfering with the xscreensaver 
> instance of the logged in user?
> Questions that only the xscreensaver maintainer can answer.
> 
> If he thinks there is a genuine systemd issue, then I'd appreciate if it was 
> reassigned back with more details.

XScreenSaver author here. I know nothing about lightdm, and didn't write the 
code attempting to integrate the two. However:

1) XScreenSaver should be running as the logged-in user, and terminate when 
they log out. Typically this happens when the X server dies and the $DISPLAY 
socket is closed, but SIGTERM works just as well.

2) It is also reasonable to configure things so that XScreenSaver is running 
when no one is logged in (so that there is a screensaver atop the login 
screen). If it is launched as root, it will setuid to "nobody" at startup, etc. 
But in this case, when a user logs in, it must be killed and re-started as that 
user.

Bug#979600: src:ucx: invalid maintainer address

[Ansgar]

Source: ucx
Version: 1.10.0~rc1-1
Severity: serious
X-Debbugs-Cc: Alastair McKinstry 

The maintainer address is invalid, see below.

Ansgar

 Start of forwarded message 
From: Mail Delivery System 
Subject: Mail delivery failed: returning message to sender
Date: Fri, 08 Jan 2021 19:49:42 +

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  debian-science-maintain...@lists.alioth.debian.net
Unrouteable address
Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;debian-science-maintainers@lists.alioth.debian.net
Status: 5.0.0

Bug#961814: marked as pending in golang-google-protobuf

[Alberto Bertogli]

On Fri, Jan 08, 2021 at 11:30:21PM +0800, Shengjing Zhu wrote:

On Fri, Jan 8, 2021 at 11:17 PM Alberto Bertogli
 wrote:


On Thu, Jan 07, 2021 at 11:12:24PM +0800, Shengjing Zhu wrote:
>On Thu, Jan 7, 2021 at 10:59 PM Alberto Bertogli
> wrote:
>> But those issues are not made worse by allowing golang-google-protobuf
>> to go in, right?
>>
>
>Let golang-google-protobuf go in is one thing, it's not difficult.
>However without golang-goprotobuf 1.4.x it's not useful currently. But
>it will be changed if upstream has switched to golang-google-protobuf
>only.

But IIUC that's what foka@'s lastest changes do - now the two packages
are independent so golang-google-protobuf can go in?

This would unblock:
1) Some upstream packages that have upgraded to the new library and are
using pregenerated pb.go without the dependency.
2) Packages that have moved/want to move to the new library and generate
pb.go as part of the build (without needing grpc).

And no packages are forced into anything, since upstream needs to do the
update explicitly anyway, the ones using golang-goprotobuf will continue
to function just fine.

I understand not all problems are fixed and some things remain, but it
seems it'd be a step in the right direction since at least some packages
will be able to move forward, without causing any new
complications/regressions.

Or am I missing something?



You are right. The only concern from my side is the usefulness of
golang-google-protobuf without upgrading golang-goprotobuf to 1.4.
If some packages are already ready for using golang-google-protobuf
solely, sure we should try.


Yeah, the reason I'm personally interested in this is I have one package 
I'm upstream for (chasquid) in this situation. I've already done the 
required patching and is blocked on this package.


I am also waiting on the change to move other projects forward for the 
same reason :)


Let me know if there's anything I can do, or how can I help!

Thanks again!
Alberto

Bug#978382: marked as done (phpmyadmin: FTBFS: Test directory "./test/engines" not found)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 20:22:32 +
with message-id 
and subject line Bug#978382: fixed in phpmyadmin 4:5.0.4+dfsg1-1
has caused the Debian Bug report #978382,
regarding phpmyadmin: FTBFS: Test directory "./test/engines" not found
to be marked as done.

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

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


-- 
978382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phpmyadmin
Version: 4:4.9.7+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # keep in sync with debian/tests/phpunit
> find test/ -type f -print0 | xargs -0 sed -i 's/function 
> setUpBeforeClass()/function setUpBeforeClass(): void/g'
> find test/ -type f -print0 | xargs -0 sed -i 's/function setUp()/function 
> setUp(): void/g'
> find test/ -type f -print0 | xargs -0 sed -i 's/function tearDown()/function 
> tearDown(): void/g'
> LC_ALL=en_US.UTF-8 phpunit --config phpunit.xml.nocoverage --exclude-group 
> selenium,network,git-revision,environment,extension-iconv
> PHPUnit 9.5.0 by Sebastian Bergmann and contributors.
> 
> Test directory "./test/engines" not found
> make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/phpmyadmin_4.9.7+dfsg1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: phpmyadmin
Source-Version: 4:5.0.4+dfsg1-1
Done: William Desportes 

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

Debian distribution maintenance software
pp.
William Desportes  (supplier of updated phpmyadmin 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, 08 Jan 2021 20:31:40 +0100
Source: phpmyadmin
Architecture: source
Version: 4:5.0.4+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: phpMyAdmin Packaging Team 
Changed-By: William Desportes 
Closes: 950531 977983 978382
Changes:
 phpmyadmin (4:5.0.4+dfsg1-1) unstable; urgency=medium
 .
   [ William Desportes ]
   * New upstream version 5.0.4 (Closes: #950531, Closes: #978382)
   * Remove phpunit 7 patch file
   * Remove packages version patch
   * Refresh the Debian patch for the vendor constants config
   * Refresh the test-autoload patch
   * Add some of the new dependencies for 5.0
   * Adjust autload for Twig-i18n-extension
   * Remove fix tests sed commands
   * Add a upstream patch to make the test suite work fine
   * Add Williamdes/MariaDBMySQLKBS to vendor autoload
   * Add some debian php-symfony dependencies
   * Remove duplicated config.manyhosts
   * Add lintian overrides for Metro theme
   * Exclude built documentation from upstream dfsg
   * Exclude node_module from upstream dfsg
   * Do not delete selenium tests folder
   * Replace phpunit custom xml by --no-coverage argument
   * Add new php-symfony- autoload requires
   * Add .yml files to installed package version
   * Add robots.txt to installed package version
   * Disable 32bit incompatible tests
   * Fix 2 unnecessary greater-than versioned dependency
   * Run "cme fix dpkg" and "wrap-and-sort"
   * Rename MIT to Expat on d/copyright
   * Apply formatting rules from "cme fix dpkg"
   * Drop 

Bug#977246: marked as done (lutris should depend on python3-dbus)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 20:20:44 +
with message-id 
and subject line Bug#977246: fixed in lutris 0.5.8.2-1
has caused the Debian Bug report #977246,
regarding lutris should depend on python3-dbus
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.)


-- 
977246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lutris
Version: 0.5.8.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: edo...@gmail.com

Hi,

The lutris package should depends on python3-dbus to work, or at least on my
recently installed system (were I didn't had python3-dbus installed) it refused
to work with this error:

Traceback (most recent call last):
  File "/usr/games/lutris", line 54, in 
from lutris.gui.application import Application  # pylint: disable=no-name-
in-module
  File "/usr/lib/python3/dist-packages/lutris/gui/application.py", line 37, in

from lutris.game import Game
  File "/usr/lib/python3/dist-packages/lutris/game.py", line 15, in 
from lutris.config import LutrisConfig
  File "/usr/lib/python3/dist-packages/lutris/config.py", line 8, in 
from lutris import settings, sysoptions
  File "/usr/lib/python3/dist-packages/lutris/sysoptions.py", line 13, in

from lutris.util.display import DISPLAY_MANAGER, SCREEN_SAVER_INHIBITOR,
USE_DRI_PRIME
  File "/usr/lib/python3/dist-packages/lutris/util/display.py", line 19, in

from lutris.util.graphics.displayconfig import MutterDisplayManager
  File "/usr/lib/python3/dist-packages/lutris/util/graphics/displayconfig.py",
line 4, in 
import dbus
ModuleNotFoundError: No module named 'dbus'

After installing python3-dbus it started working without problems.

Greets.
Ernesto



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

Kernel: Linux 5.9.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lutris depends on:
ii  cabextract   1.9-3
ii  curl 7.72.0-1
ii  fluid-soundfont-gs   3.1-5.1
ii  gir1.2-gnomedesktop-3.0  3.38.2-1
ii  gir1.2-gtk-3.0   3.24.24-1
ii  gir1.2-notify-0.70.7.9-2
ii  gir1.2-webkit2-4.0   2.30.3-1
ii  mesa-utils   8.4.0-1+b1
ii  p7zip16.02+dfsg-8
ii  psmisc   23.3-1
ii  python3  3.9.0-4
ii  python3-distro   1.5.0-1
ii  python3-gi   3.38.0-1+b2
ii  python3-magic2:0.4.15-5
ii  python3-pil  8.0.1-1+b1
ii  python3-requests 2.25.0+dfsg-1
ii  python3-setproctitle 1.2.1-1+b1
ii  python3-yaml 5.3.1-3+b1
ii  unzip6.0-25
ii  x11-xserver-utils7.7+8

Versions of packages lutris recommends:
ii  gvfs-backends1.46.1-1
pn  libwine-development  
ii  python3-evdev1.3.0+dfsg-1+b3
pn  winetricks   

Versions of packages lutris suggests:
ii  gamemode  1.6-1+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lutris
Source-Version: 0.5.8.2-1
Done: Stephan Lachnit 

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

Debian distribution maintenance software
pp.
Stephan Lachnit  (supplier of updated lutris 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Jan 2021 11:55:46 +0100
Source: lutris
Architecture: source
Version: 0.5.8.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Stephan Lachnit 
Closes: 977246 978557
Changes:
 lutris (0.5.8.2-1) unstable; urgency=medium
 .
   * New upstream version 0.5.8.2
   * Closes: #977246, #978557
Checksums-Sha1:
 2cb1c9b726e1fceda5a8ee399fb6a22159606dbb 1979 lutris_0.5.8.2-1.dsc
 711c1537e8574d5ad4b1e722c51a394710fcbfad 820147 lutris_0.5.8.2.orig.tar.gz
 

Processed: limit source to phpmyadmin, tagging 977983, tagging 950531, tagging 978382

[Debian Bug Tracking System]

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

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

> tags 977983 + pending
Bug #977983 [phpmyadmin] Should not build-depend on composer
Added tag(s) pending.
> tags 950531 + pending
Bug #950531 [phpmyadmin] new upstream (5.0.1)
Added tag(s) pending.
> tags 978382 + pending
Bug #978382 [src:phpmyadmin] phpmyadmin: FTBFS: Test directory "./test/engines" 
not found
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: vilistextum: FTBFS: ld: html.o:./src/text.h:16: multiple definition of `ch'; charset.o:./src/text.h:16: first defined here

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #966861 [src:vilistextum] vilistextum: FTBFS: ld: html.o:./src/text.h:16: 
multiple definition of `ch'; charset.o:./src/text.h:16: first defined here
Added tag(s) patch.

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

Bug#966861: vilistextum: FTBFS: ld: html.o:./src/text.h:16: multiple definition of `ch'; charset.o:./src/text.h:16: first defined here

[Logan Rosen]

Package: vilistextum
Version: 2.6.9-1.2
Followup-For: Bug #966861
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch

Hi,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/gcc-10.patch: Fix compilation with GCC 10.

Thanks for considering the patch.

Logan
diff -u vilistextum-2.6.9/debian/patches/series 
vilistextum-2.6.9/debian/patches/series
--- vilistextum-2.6.9/debian/patches/series
+++ vilistextum-2.6.9/debian/patches/series
@@ -1 +1,2 @@
 01-add-format-arguments.patch
+gcc-10.patch
only in patch2:
unchanged:
--- vilistextum-2.6.9.orig/debian/patches/gcc-10.patch
+++ vilistextum-2.6.9/debian/patches/gcc-10.patch
@@ -0,0 +1,120 @@
+--- a/src/main.h
 b/src/main.h
+@@ -3,22 +3,22 @@
+ 
+ #include "multibyte.h"
+ 
+-int palm;
+-int   convert_tags;
+-int errorlevel;
+-int convert_characters;
+-int shrink_lines;
+-int remove_empty_alt;
+-int option_links;
+-int option_links_inline;
+-int option_title;
+-int sevenbit;
+-int transliteration;
++extern int palm;
++extern intconvert_tags;
++extern int errorlevel;
++extern int convert_characters;
++extern int shrink_lines;
++extern int remove_empty_alt;
++extern int option_links;
++extern int option_links_inline;
++extern int option_title;
++extern int sevenbit;
++extern int transliteration;
+ 
+-int option_no_image;
+-int option_no_alt;
+-int option_output_utf8;
++extern int option_no_image;
++extern int option_no_alt;
++extern int option_output_utf8;
+ 
+-CHAR *default_image;
++extern CHAR *default_image;
+ 
+ #endif
+--- a/src/text.h
 b/src/text.h
+@@ -9,23 +9,23 @@
+ 
+ #include "multibyte.h"
+ 
+-int LEFT;  
+-int CENTER;
+-int RIGHT;
+-
+-CHAR ch;
+-
+-int paragraph;
+-int div_test;
+-int nooutput;
++extern int LEFT;  
++extern int CENTER;
++extern int RIGHT;
++
++extern CHAR ch;
++
++extern int paragraph;
++extern int div_test;
++extern int nooutput;
+ 
+-int breite;
+-int hr_breite;
++extern int breite;
++extern int hr_breite;
+ 
+ void status();
+ 
+-int tab;
+-int spaces;  
++extern int tab;
++extern int spaces;  
+ 
+ void print_zeile();
+ int is_zeile_empty();
+--- a/src/html.h
 b/src/html.h
+@@ -4,13 +4,13 @@
+ #include "text.h"
+ #include "multibyte.h"
+ 
+-int pre;
++extern int pre;
+ 
+ int get_attr();
+ int get_new_attr(CHAR *name, CHAR *content);
+ 
+-CHAR attr_name[DEF_STR_LEN];
+-CHAR attr_ctnt[DEF_STR_LEN];
++extern CHAR attr_name[DEF_STR_LEN];
++extern CHAR attr_ctnt[DEF_STR_LEN];
+ 
+ void html();
+ void check_for_center();
+--- a/src/text.c
 b/src/text.c
+@@ -47,6 +47,8 @@
+   anz_leere_zeilen=0, /* how many line were blank */
+   noleadingblanks=0;  /* remove blanks lines at the start of the output */
+ 
++CHAR ch;
++
+ /*  */
+ 
+ void center_zeile()
+--- a/src/main.c
 b/src/main.c
+@@ -134,6 +134,8 @@
+ CHAR *default_image=STRING("Image"); /* Default string for IMG without 
ALT-tag */
+ CHAR user_image[DEF_STR_LEN]; /* string supplied by user */
+ 
++int transliteration;
++
+ char help_text[] = 
+ "Usage: vilistextum [OPTIONS] [inputfile|-] [outputfile|-]\n"
+ "\n"

Processed: your mail

[Debian Bug Tracking System]

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

> severity 978146 important
Bug #978146 [geary] geary: Geary segfaults on startup after upgrade to 3.38.1-1
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.

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

Processed: Re: Bug#974779 closed by Debian FTP Masters (reply to Gianfranco Costamagna ) (Bug#974779: fixed in llvm-toolchain-9 1:9.0.1-16)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #974779 [julia] julia: Please upgrade to llvm-toolchain-11
Severity set to 'important' from 'serious'

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

Bug#974779: closed by Debian FTP Masters (reply to Gianfranco Costamagna ) (Bug#974779: fixed in llvm-toolchain-9 1:9.0.1-16)

[Gianfranco Costamagna]

control: severity -1 important

I agree on reopening, but I don't think this is a serious issue anymore, since 
we plan to ship stable with
llvm-9 and llvm-11

G.

On Fri, 8 Jan 2021 13:21:40 +0100 Sylvestre Ledru  wrote:
> control: reopen -1
> 
> It isn't fixed for real as Julia needs to be updated!
> 
> S
> 
> 
> Le 08/01/2021 à 13:06, Debian Bug Tracking System a écrit :
> > This is an automatic notification regarding your Bug report
> > which was filed against the julia package:
> >
> > #974779: julia: Please upgrade to llvm-toolchain-11
> >
> > It has been closed by Debian FTP Masters  
> > (reply to Gianfranco Costamagna ).
> >
> > Their explanation is attached below along with your original report.
> > If this explanation is unsatisfactory and you have not received a
> > better one in a separate message then please contact Debian FTP Masters 
> >  (reply to Gianfranco Costamagna 
> > ) by
> > replying to this email.
> >
> >
> 
> 

Processed: reopening 976930

[Debian Bug Tracking System]

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

> reopen 976930
Bug #976930 {Done: Carsten Schoenert } [src:arduino] 
arduino: FTBFS on ppc64el (arch:all-only src pkg): Target "${platform}-build" 
does not exist in the project "Arduino".
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions arduino/2:1.8.13+dfsg1-1~exp1.
> thanks
Stopping processing here.

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

Bug#952313: marked as done (arduino-builder: FTBFS: failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent: permission denied)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 18:33:24 +
with message-id 
and subject line Bug#952313: fixed in arduino-builder 1.3.25-2~exp1
has caused the Debian Bug report #952313,
regarding arduino-builder: FTBFS: failed to initialize build cache at 
/sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent: permission 
denied
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.)


-- 
952313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arduino-builder
Version: 1.3.25-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Remove tests which download stuff:
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/add_build_board_property_if_missing_test.go'
> removed 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/builder_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/hardware_loader_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/includes_to_include_folders_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/prototypes_adder_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/load_vid_pid_specific_properties_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/setup_build_properties_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/try_build_of_problematic_sketch_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/tools_loader_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/ctags_runner_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/merge_sketch_with_bootloader_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/libraries_loader_test.go'
> removed 
> 'obj-x86_64-linux-gnu/src/arduino.cc/builder/test/target_board_resolver_test.go'
> # Execute the rest of the tests
> cd obj-* &&\
> export GOPATH=$(pwd) &&\
> go test -v -timeout 30m arduino.cc/...
> warning: ignoring symlink 
> /<>/obj-x86_64-linux-gnu/src/arduino.cc/builder/test/user_hardware/my_symlinked_avr_platform
> failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: 
> mkdir /sbuild-nonexistent: permission denied
> make[1]: *** [debian/rules:34: override_dh_auto_test] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/arduino-builder_1.3.25-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: arduino-builder
Source-Version: 1.3.25-2~exp1
Done: Rock Storm 

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

Debian distribution maintenance software
pp.
Rock Storm  (supplier of updated arduino-builder 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, 08 Jan 2021 17:52:00 +
Source: arduino-builder
Architecture: source
Version: 1.3.25-2~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Rock Storm 
Closes: 952313
Changes:
 arduino-builder (1.3.25-2~exp1) experimental; urgency=medium
 .
   [ Rock Storm ]
   * [822d52f] d/rules: Export a writable home directory.
 - Patch contributed by Logan Rosen. Thanks a lot.
 - Closes: #952313
   * [ae5fcf4] d/control: Update to use debhelper-compat
   * [dea05bb] d/control: Bump-up Standards-Version.
 - No changes needed.
   * [4459878] d/control: Rules does not require root
   * [2e44208] Add minimum upstream meta info
   * [26c1421] 

Processed: reassign 979520 to src:chromium, forcibly merging 979533 979520

[Debian Bug Tracking System]

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

> reassign 979520 src:chromium
Bug #979520 [chromium] chromium: Security upgrade to version 87.0.4280.141
Bug reassigned from package 'chromium' to 'src:chromium'.
No longer marked as found in versions chromium/87.0.4280.88-0.4.
Ignoring request to alter fixed versions of bug #979520 to the same values 
previously set
> forcemerge 979533 979520
Bug #979533 [src:chromium] chromium: New 87.0.4280.141 (CVE-2020-15995 
CVE-2020-16043 CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109 
CVE-2021-21110 CVE-2021-2 CVE-2021-21112 CVE-2021-21113 CVE-2021-21114  
CVE-2021-21115 CVE-2021-21116)
Bug #979520 [src:chromium] chromium: Security upgrade to version 87.0.4280.141
Severity set to 'grave' from 'normal'
Marked as found in versions chromium/87.0.4280.88-0.4~deb10u1 and 
chromium/87.0.4280.88-0.4.
Added tag(s) security and upstream.
Merged 979520 979533
> thanks
Stopping processing here.

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

Bug#979562: lightdm session termination does not stop xscreensaver

[Michael Biebl]

Am 08.01.21 um 14:12 schrieb Eduard Bloch:

Hallo,

I don't fully agree. If you don't see a problem here, WHERE do you see
it?


In xscreensaver (or maybe lightdm).
Why is xscreensaver started in the lightdm session anyway?
Is xscreensaver really usable as a per user service or should it be per 
session?
Why is the lightdm xscreensaver instance interfering with the 
xscreensaver instance of the logged in user?

Questions that only the xscreensaver maintainer can answer.

If he thinks there is a genuine systemd issue, then I'd appreciate if it 
was reassigned back with more details.


Michael




OpenPGP_signature
Description: OpenPGP digital signature

Bug#977814: fixed in llvm-toolchain-11 1:11.0.1-1

[Pino Toscano]

In data venerdì 8 gennaio 2021 12:38:20 CET, Gianfranco Costamagna ha scritto:
> llvm-toolchain-11 is now fixed, and clazy should be fixed too.

No, llvm-toolchain-11 is not fixed yet.

> Unfortunately clazy seems to be missing a "break" relationship against old 
> llvm, and britney uses
> the broken testing version to test it.

It makes no sense for clazy to break and old llvm, it should be rather
the other way round... but it shouldn't be needed.

Also, the version in testing is *not* broken. clazy in testing is
perfectly working, and it was the llvm-toolchain-11 upload that broke
it.

> I don't know if we can hint to let it migrate anyway,

Considering nothing was actually done to fix the problems I reported
earlier in this bug, I don't think that letting the newer
llvm-toolchain-11 migrate and break also testing is an acceptable way
forward. Even more so when there was *no* attempt by the Debian LLVM
Maintainers (of which you are part) to debug what was the issue.

All this "fix" did was to apply the diff I mentioned, which was to fix
only a small part of the problems I reported. Also, reading it further,
even the shlibs of all the other libraries need to be fixed: they all
specify old versions (like 9~something) that are satisfied by any
llvm-toolchain-11 version available, including prereleases.

> Let me know if you have a solution for this issue,

The Debian LLVM Maintainers ought to help debug why updating a new
version suddently breaks software built against old versions of it.
Sorry if I seem harsh: LLVM is a key component in a modern Debian
system, so uploading new versions and providing almost no help on
problems does not seem like a good idea for the distribution.

-- 
Pino Toscano

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

Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

[Vagrant Cascadian]

On 2021-01-08, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Fri, 13 Nov 2020 at 17:40, Vagrant Cascadian
>  wrote:
>>
>> On 2020-11-13, Sune Vuorela wrote:
>> > On 2020-10-27, Vagrant Cascadian  wrote:
>> >> Though, of course, identifying the exact reproducibility problem would
>> >> be preferable. One of the common issues is test suites relying on the
>> >> behavior of __FILE__ returning a full path to find fixtures or other
>> >> test data.
>> >
>> > has QFIND_TESTDATA been adapted to work with this, or are we just
>> > "lucky" that most packages don't actually build and run test suites?
>>
>> Yes, QFINDTESTDATA is one of the primary (only?) issues with test suites
>> found in about 20-30 packages in the archive, according to the
>> archive-wide rebuild that was performed. For most of those packages
>> patches have been submitted, and some are already either fixed or marked
>> as pending.
>
> But QFINDTESTDATA is using __FILE__ in a valid way. It might not be
> what you are expecting, but still a valid usage.
>
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901 We have
> discussed this before.
>
>
>> If it could be fixed at the core for QFINDTESTDATA, that would be nicer
>> than fixing 20-30 packages individually, though we're not there right
>> now.
>
> In that case I would expect a valid patch from the people interested
> in enabling this. In the meantime the dpkg change broke a very valid
> usage. Inconvenient for reproducibility? yes, probably, but still very
> valid.

We did a full archive rebuild testing this change, and I provided
patches to all known affected packages several months ago. It is a
one-line change in debian/rules in most cases:

  
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=reproducible-builds%40lists.alioth.debian.org=fixfilepath

It seems there are less than 10 packages left that have not applied the
patch.

Longer-term, it would be nice to be able to fix QFINDTESTDATA to be
compatible, sure.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#978232: orage: FTBFS: build-dependency not installable: xfce4-panel (= 4.14.4-1)

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, 2021-01-08 at 14:10 +0200, Juhani Numminen wrote:
> Thank you Yves-Alexis for implementing this in orage/4.12.1-8.
> 
> I noticed that the removal request still stands (
> https://bugs.debian.org/977628 ).
> Do you still intend to remove orage from Debian or are you happy to keep it
> for now?

I don't really think it's sustainable if upstream is gone. I think it's better
if the “last state” doesn't FTBFS, but I don't think we can ship it in
Bullseye since the last upstream version is so old.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl/4ktMACgkQ3rYcyPpX
RFsGmAgA0QIwFK+q4h59CKfUxtctOlb1fxmK3wT8795VeePesR/zAFZOqta8BeUI
nQ7W6/RoCSMvfkvVogjB8A2sFrT/lD6OlwlsI+AxzfAaNUcqbiMaixlutGobIojd
wOATph21h908/pmPv9OGGb4JC+/xOP7myw50TzU6DQs2j0hu7FzsoOA5iEjIpfMe
D6QAe5wYATyLL/E5VuEdgqKvejm7ja0TAZEVqMLzYw7myGBg13xiTsJ6SYxKGNRS
eL9i8QHorYDLPzy6c/1/+vl9K6XiChqh73VOzzYq4qjGqXm7/ez7iG9r0wu/Xs2l
isupbJDgsg+kZuJGWR9CEpn6LroCug==
=Nu2L
-END PGP SIGNATURE-

Bug#979533: chromium: New 87.0.4280.141

[Michel Le Bihan]

Hello,

I'm working on the update, but I encountered an unexpected issue. The
update was easy. Patches did not require updating. The problem, is that
Chromium IU is frozen. Chromium itself isn't and the globe on
https://en.wikipedia.org/wiki/GIF spins, but Chromium doesn't react to
any UI input. I'm debugging that, but haven't made much progress.

Michel Le Bihan

Bug#977779: geary FTBFS on mipsel: test suite failure

[Alberto Garcia]

On Mon, Dec 21, 2020 at 11:30:14PM +0200, Adrian Bunk wrote:
> > I see that the build eventually succeeded:
> > 
> >
> > https://buildd.debian.org/status/logs.php?pkg=geary=3.38.1-1=mipsel
> > 
> > The webkit2gtk build is flaky itself in mipsel, we discussed this
> > already in the past (#962616), I wonder if this is the same root
> > problem?
> 
> This is the same problem.
> 
> Note that the build is not and never was flaky, it does 100%
> determinisitically fail on Loongson buildds and succeed on Octeon
> buildds.
> 
> Jiaxun Yang discovered this weekend that CeilingOnPageSize is wrong
> for Loongson which has 16 kB pagesize and this matches when the
> problems started in 2.28.1, but unfortunately fixing this does not
> seem to fix all problems.

But this a bug in the CPU, right? Do I understand correctly that the
package can fail depending on what CPU it is run on regardless of how
it was built?

I'm trying to understand what we can do in WebKit in order to fix or
work around this.

Berto

Bug#979582: nageru: please drop the Build-Depends on libsrt-gnutls-dev which is RC-buggy

[Steinar H. Gunderson]

On Fri, Jan 08, 2021 at 05:36:58PM +0100, Paul Gevers wrote:
> The srt source package is RC buggy and has just been orphaned. We'll
> probably remove it soon from bullseye. nageru will go too then, unless
> it drop the (apparent optional) Build-Depends.

That's sad to hear. I'll drop the B-D in an upcoming upload; thanks for the
heads-up.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#978146: geary: Geary segfaults on startup after upgrade to 3.38.1-1

[debian]

Severity: important

Changing the severity to important as it turns out that a workaround 
exists (ie: remove the user's geary config).


Also, since Geary does not support POP accounts, I don't believe any 
data loss would happen (one just need to resync their imap emails).


Given those info, this bug doesn't qualify for severity grave imho.

Best regards,

Henry-Nicolas Tourneur

Bug#979583: golang-github-spf13-cobra: autopkgtest regression in testing: date of execution is capture in comparison

[Paul Gevers]

Source: golang-github-spf13-cobra
Version: 1.1.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With time moving the year to 2021, the autopkgtest of your package
started to fail. I copied some of the output at the bottom of this
report. Can you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-spf13-cobra/9459756/log.gz

=== RUN   TestGoldenAddCmd
add_test.go:26:
"/tmp/autopkgtest-lxc.0dv6r0gd/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/spf13/cobra/cobra/cmd/testproject/cmd/test.go"
and "testdata/test.go.golden" are not equal!

$ diff -u
/tmp/autopkgtest-lxc.0dv6r0gd/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/spf13/cobra/cobra/cmd/testproject/cmd/test.go
testdata/test.go.golden
---
/tmp/autopkgtest-lxc.0dv6r0gd/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/spf13/cobra/cobra/cmd/testproject/cmd/test.go
2021-01-06 19:13:34.418670146 +
+++ testdata/test.go.golden 2020-10-24 09:28:37.0 +
@@ -1,5 +1,5 @@
 /*
-Copyright © 2021 NAME HERE 
+Copyright © 2020 NAME HERE 

 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.

exit status 1
--- FAIL: TestGoldenAddCmd (0.00s)



OpenPGP_signature
Description: OpenPGP digital signature

Processed: nageru: please drop the Build-Depends on libsrt-gnutls-dev which is RC-buggy

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 971754
Bug #979582 [src:nageru] nageru: please drop the Build-Depends on 
libsrt-gnutls-dev which is RC-buggy
979582 was not blocked by any bugs.
979582 was not blocking any bugs.
Added blocking bug(s) of 979582: 971754

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

Bug#979582: nageru: please drop the Build-Depends on libsrt-gnutls-dev which is RC-buggy

[Paul Gevers]

Source: nageru
Version: 2.0.1-1
Severity: serious
Justification: B-D RC buggy
Control: block -1 by 971754

Hi Steinar,

The srt source package is RC buggy and has just been orphaned. We'll
probably remove it soon from bullseye. nageru will go too then, unless
it drop the (apparent optional) Build-Depends.

src:gst-plugins-bad1.0 is currently preventing autoremoval as that's a
key package, but I requested its maintainer to drop the plugin in the
follow-up of bug #978564.

Alternatively, you could adopt src:srt and fix the issue, but please be
aware that srt upstream has a bad record for breaking ABI.

Paul


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#976930: marked as done (arduino: FTBFS on ppc64el (arch:all-only src pkg): Target "${platform}-build" does not exist in the project "Arduino".)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 16:33:34 +
with message-id 
and subject line Bug#976930: fixed in arduino 2:1.8.13+dfsg1-1~exp1
has caused the Debian Bug report #976930,
regarding arduino: FTBFS on ppc64el (arch:all-only src pkg): Target 
"${platform}-build" does not exist in the project "Arduino".
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.)


-- 
976930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arduino
Version: 2:1.0.5+dfsg2-4.1
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el

Hi,

During a rebuild of all packages in sid, your package failed to build
on ppc64el. At the same time, it did not fail on amd64.

I'm marking this bug as severity:serious since your package has only
Architecture:all binary packages, and should thus, in theory, build
everywhere. Failure to build on ppc64el might indicate a serious issue
in this package or in another package.

But feel free to downgrade or close if you believe that this is only a
build-time issue. (I would personnally prefer a severity:minor bug just to
track that the package can only be built on specific architectures.)

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> jh_linkjars
> jh_linkjars: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> mkdir -p build/linux/work/hardware/tools
> #remove unneeded macosx support
> rm -rf app/src/processing/app/macosx
> cd core/methods && ant
> Buildfile: /<>/core/methods/build.xml
> 
> compile:
> [mkdir] Created dir: /<>/core/methods/bin
> [javac] Using javac -target 1.5 is no longer supported, switching to 6
> [javac] Compiling 1 source file to /<>/core/methods/bin
> [javac] 
> [javac]   WARNING
> [javac] 
> [javac] The -source switch defaults to 9 in JDK 9.
> [javac] If you specify -target 6 you now must also specify -source 6.
> [javac] Ant will implicitly add -source 6 for you.  Please change your 
> build file.
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 6
> [javac] warning: [options] source value 6 is obsolete and will be removed 
> in a future release
> [javac] warning: [options] target value 1.6 is obsolete and will be 
> removed in a future release
> [javac] warning: [options] To suppress warnings about obsolete options, 
> use -Xlint:-options.
> [javac] 4 warnings
> 
> task-lib:
>   [jar] Building jar: /<>/core/methods/methods.jar
> 
> BUILD SUCCESSFUL
> Total time: 0 seconds
> cd build && ant
> Buildfile: /<>/build/build.xml
> 
> build:
> 
> BUILD FAILED
> /<>/build/build.xml:69: The following error occurred while 
> executing this line:
> Target "${platform}-build" does not exist in the project "Arduino". 
> 
> Total time: 0 seconds
> make[1]: *** [debian/rules:27: override_jh_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/09/arduino_1.0.5+dfsg2-4.1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on a Power8 cluster part of the
Grid'5000 testbed. Hardware specs: 
https://www.grid5000.fr/w/Grenoble:Hardware#drac
--- End Message ---
--- Begin Message ---
Source: arduino
Source-Version: 2:1.8.13+dfsg1-1~exp1
Done: Carsten Schoenert 

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated arduino 
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

Bug#891901: marked as done (arduino: Doesn't open.)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 16:33:34 +
with message-id 
and subject line Bug#891901: fixed in arduino 2:1.8.13+dfsg1-1~exp1
has caused the Debian Bug report #891901,
regarding arduino: Doesn't open.
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.)


-- 
891901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arduino
Version: 2:1.5.6.2+sdfsg2-3
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

nicola@nicola-debian:~$ arduino
Exception in thread "main" java.lang.NoClassDefFoundError: 
org/slf4j/LoggerFactory
at 
javax.jmdns.impl.NetworkTopologyDiscoveryImpl.(NetworkTopologyDiscoveryImpl.java:24)
at 
javax.jmdns.NetworkTopologyDiscovery$Factory.newNetworkTopologyDiscovery(NetworkTopologyDiscovery.java:114)
at 
javax.jmdns.NetworkTopologyDiscovery$Factory.getInstance(NetworkTopologyDiscovery.java:126)
at 
cc.arduino.packages.discoverers.NetworkDiscovery.start(NetworkDiscovery.java:89)
at cc.arduino.packages.DiscoveryManager.(DiscoveryManager.java:52)
at processing.app.Base.(Base.java:85)
Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 6 more


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

Kernel: Linux 4.14.0-3-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)
LSM: AppArmor: enabled

Versions of packages arduino depends on:
ii  arduino-core   2:1.5.6.2+sdfsg2-3
ii  default-jre [java7-runtime]2:1.8-59
ii  libastylej-jni 3.0.1-1
ii  libcommons-exec-java   1.3-1
ii  libcommons-httpclient-java 3.1-14
ii  libcommons-logging-java1.2-2
ii  libjmdns-java  3.5.3-1
ii  libjna-java4.5.1-1
ii  libjsch-java   0.1.54-1
ii  libjssc-java   2.8.0-1
ii  openjdk-7-jre [java7-runtime]  7u161-2.6.12-1
ii  openjdk-8-jre [java7-runtime]  8u151-b12-1

Versions of packages arduino recommends:
ii  astyle   3.0.1-1
pn  extra-xdg-menus  
ii  policykit-1  0.105-18

arduino suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: arduino
Source-Version: 2:1.8.13+dfsg1-1~exp1
Done: Carsten Schoenert 

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated arduino 
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, 08 Jan 2021 12:42:57 +0100
Source: arduino
Binary: arduino
Architecture: source amd64
Version: 2:1.8.13+dfsg1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Carsten Schoenert 
Description:
 arduino- AVR development board IDE from Arduino CC
Closes: 723929 724804 757223 758039 780609 780706 786405 849213 850784 850964 
857463 876495 877201 885830 891901 894770 894823 923496 925578 927329 947228 
976930
Changes:
 arduino (2:1.8.13+dfsg1-1~exp1) experimental; urgency=medium
 .
   * Team upload
 .
   [ Scott Howard ]
   * [b3ae605] Imported Upstream version 1.6.0+dfsg
 .
   [ Geert Stappers ]
   * [1cd9f55] Imported Upstream version 1.6.8
   * [c01e14d] Imported Upstream version 1.8.2
   * [cf271e6] Imported Upstream version 1.8.2+dfsg
 .
   [ Carsten Schoenert ]
   * [8bf88fc] Adding config file for git-buildpackage
   * [82131c9] New upstream 

Bug#877201: marked as done (arduino: broken symlink: /usr/share/arduino/lib/libastylej.so -> ../../../lib/jni/libastylej.so)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 16:33:34 +
with message-id 
and subject line Bug#877201: fixed in arduino 2:1.8.13+dfsg1-1~exp1
has caused the Debian Bug report #877201,
regarding arduino: broken symlink: /usr/share/arduino/lib/libastylej.so -> 
../../../lib/jni/libastylej.so
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.)


-- 
877201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: arduino
Version: 2:1.5.6.2+sdfsg2-3
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...):

2m18.2s ERROR: FAIL: Broken symlinks:
  /usr/share/arduino/lib/libastylej.so -> ../../../lib/jni/libastylej.so


Since libastylej-jni was marked Multi-Arch:same it no longer provides the
/usr/lib/jni/libastylej.so symlink, only
/usr/lib/jni//libastylej.so

Assuming arduino will fail with this library missing, I set the severity
to serious.

Given that arduino is an arch:all package, I find it interesting to see
it require a (arch dependent) shared library.


cheers,

Andreas


arduino_2:1.5.6.2+sdfsg2-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: arduino
Source-Version: 2:1.8.13+dfsg1-1~exp1
Done: Carsten Schoenert 

We believe that the bug you reported is fixed in the latest version of
arduino, 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.
Carsten Schoenert  (supplier of updated arduino 
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, 08 Jan 2021 12:42:57 +0100
Source: arduino
Binary: arduino
Architecture: source amd64
Version: 2:1.8.13+dfsg1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Carsten Schoenert 
Description:
 arduino- AVR development board IDE from Arduino CC
Closes: 723929 724804 757223 758039 780609 780706 786405 849213 850784 850964 
857463 876495 877201 885830 891901 894770 894823 923496 925578 927329 947228 
976930
Changes:
 arduino (2:1.8.13+dfsg1-1~exp1) experimental; urgency=medium
 .
   * Team upload
 .
   [ Scott Howard ]
   * [b3ae605] Imported Upstream version 1.6.0+dfsg
 .
   [ Geert Stappers ]
   * [1cd9f55] Imported Upstream version 1.6.8
   * [c01e14d] Imported Upstream version 1.8.2
   * [cf271e6] Imported Upstream version 1.8.2+dfsg
 .
   [ Carsten Schoenert ]
   * [8bf88fc] Adding config file for git-buildpackage
   * [82131c9] New upstream version 1.8.13+dfsg1
 (Closes: #723929, #724804, #757223, #758039, #780609, #780706, #786405,
  #850784, #850964, #857463, #885830, #876495, #877201, #891901,
  #894770, #894823, #925578, #927329, #947228, #976930)
   * [77d4a95] rebuild patch queue from patchqueue branch
 Rebuild and reorder the existing patches.
 Added patches:
 debian-hacks/Don-t-call-assemble-hardware-target.patch
 debian-hacks/Don-t-use-functions-from-jtouchbar.patch
 debian-hacks/Ignore-Apple-specific-check-from-apple-lib.patch
 debian-hacks/Install-appdata.xml-into-propriate-folder.patch
 Dropped patches:
 gcc47_avr.patch
   * [4c43fd7] running wrap-and-sort to improve readability
   * [4714c7b] debhelper: move over to debhelper 13
   * [0f1249c] d/control: Adjust dependencies for package built
   * [c49f415] d/control: remove version requirement on librxtx-java
 The previous used minimal version is always fulfilled now, we only have
 higher versions within the archive.
   * [b27f91e] d/control: Update upstream homepage to use https
   * [bb5a6d5] d/control: Adjust depending packages on binary packages
 Removing now useless versions on various depending packages, all
 available versions are higher than the declared old minimal versions for
 the binary packages.
 Replacing java6-runtime by openjdk-11-jre, the former package isn't
 available any more.
   * [8a31b55] d/control: Switching Priority from extra to 

Bug#876495: marked as done (arduino: FTBFS error: is not abstract and does not override abstract method startResponder(DNSIncoming,In

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 16:33:34 +
with message-id 
and subject line Bug#876495: fixed in arduino 2:1.8.13+dfsg1-1~exp1
has caused the Debian Bug report #876495,
regarding arduino: FTBFS  error:  is not abstract and does 
not override abstract method startResponder(DNSIncoming,InetAddress,int) in 
DNSTaskStarter
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.)


-- 
876495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: arduino
Version: 2:1.5.6.2+sdfsg2-3
Severity: serious
Justification: fails to build from source

Hi,

arduino/experimental FTBFS in a curent sid/experimental environment:

[...]
[javac] 
/build/arduino-1.5.6.2+sdfsg2/app/src/processing/app/zeroconf/jmdns/ArduinoDNSTaskStarter.java:17:
 error:  is 
not abstract and does not override abstract method 
startResponder(DNSIncoming,InetAddress,int) in DNSTaskStarter
[javac] return new DNSTaskStarter() {
[javac] ^
[javac] 
/build/arduino-1.5.6.2+sdfsg2/app/src/processing/app/zeroconf/jmdns/ArduinoDNSTaskStarter.java:77:
 error: method startResponder in class DNSTaskStarterImpl cannot be applied to 
given types;
[javac] delegate.startResponder(in, port);
[javac] ^
[javac]   required: DNSIncoming,InetAddress,int
[javac]   found: DNSIncoming,int
[javac]   reason: actual and formal argument lists differ in length
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 2 errors
[javac] 100 warnings


Full log attached.

Andreas


arduino_2%1.5.6.2+sdfsg2-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: arduino
Source-Version: 2:1.8.13+dfsg1-1~exp1
Done: Carsten Schoenert 

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

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

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated arduino 
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, 08 Jan 2021 12:42:57 +0100
Source: arduino
Binary: arduino
Architecture: source amd64
Version: 2:1.8.13+dfsg1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Carsten Schoenert 
Description:
 arduino- AVR development board IDE from Arduino CC
Closes: 723929 724804 757223 758039 780609 780706 786405 849213 850784 850964 
857463 876495 877201 885830 891901 894770 894823 923496 925578 927329 947228 
976930
Changes:
 arduino (2:1.8.13+dfsg1-1~exp1) experimental; urgency=medium
 .
   * Team upload
 .
   [ Scott Howard ]
   * [b3ae605] Imported Upstream version 1.6.0+dfsg
 .
   [ Geert Stappers ]
   * [1cd9f55] Imported Upstream version 1.6.8
   * [c01e14d] Imported Upstream version 1.8.2
   * [cf271e6] Imported Upstream version 1.8.2+dfsg
 .
   [ Carsten Schoenert ]
   * [8bf88fc] Adding config file for git-buildpackage
   * [82131c9] New upstream version 1.8.13+dfsg1
 (Closes: #723929, #724804, #757223, #758039, #780609, #780706, #786405,
  #850784, #850964, #857463, #885830, #876495, #877201, #891901,
  #894770, #894823, #925578, #927329, #947228, #976930)
   * [77d4a95] rebuild patch queue from patchqueue branch
 Rebuild and reorder the existing patches.
 Added patches:
 debian-hacks/Don-t-call-assemble-hardware-target.patch
 debian-hacks/Don-t-use-functions-from-jtouchbar.patch
 debian-hacks/Ignore-Apple-specific-check-from-apple-lib.patch
 debian-hacks/Install-appdata.xml-into-propriate-folder.patch
 Dropped patches:
 gcc47_avr.patch
   * [4c43fd7] running wrap-and-sort to improve readability
   * [4714c7b] debhelper: move over to debhelper 13
   * [0f1249c] d/control: Adjust dependencies for package built
   * [c49f415] d/control: remove version requirement on librxtx-java
 The previous used minimal version is always fulfilled now, we only have
 higher versions within 

Bug#978564: src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating

[Paul Gevers]

HI Sebastian,

On Thu, 07 Jan 2021 12:56:42 +0200 Sebastian =?ISO-8859-1?Q?Dr=F6ge?=
 wrote:
> That seems like something for the maintainer to figure out IMHO but
> they didn't even respond to #971754 yet.

They orphaned the package today after I inquired on the progress.

> There's going to be another GStreamer bugfix release beginning of next
> week, which I'll be uploading after this has migrated to then.

I think it's best to drop the srt plugin when that happens, such that we
can remove src:srt from bullseye. Once the srt package has a proper
maintainer again you can add it back.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#979581: OpenJDK 15 should stay out of testing

[Matthias Klose]

Package: src:openjdk-15
Version: 15.0.1+9-3
Severity: serious

OpenJDK 15 should stay out of testing. We stil want to keep it unstable, as it
is the latest released version.

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> forcemerge 979533 979520
Bug #979533 [src:chromium] chromium: New 87.0.4280.141 (CVE-2020-15995 
CVE-2020-16043 CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109 
CVE-2021-21110 CVE-2021-2 CVE-2021-21112 CVE-2021-21113 CVE-2021-21114  
CVE-2021-21115 CVE-2021-21116)
Unable to merge bugs because:
package of #979520 is 'chromium' not 'src:chromium'
Failed to forcibly merge 979533: Did not alter merged bugs.

>
End of message, stopping processing here.

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

Bug#957991: marked as done (xneur: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 16:05:34 +
with message-id 
and subject line Bug#957991: fixed in xneur 0.20.0-3
has caused the Debian Bug report #957991,
regarding xneur: ftbfs with GCC-10
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.)


-- 
957991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xneur
Version: 0.20.0-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/xneur_0.20.0-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -g0 -std=gnu99 
-fPIC -I../../lib/config -I../../lib/lib -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o libxnmisc_la-text.lo `test -f 'text.c' || echo 
'./'`text.c
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -g0 -std=gnu99 
-fPIC -I../../lib/config -I../../lib/lib -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o libxnmisc_la-regexp.lo `test -f 'regexp.c' || 
echo './'`regexp.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -g0 -std=gnu99 -fPIC 
-I../../lib/config -I../../lib/lib -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c list_char.c -o 
libxnmisc_la-list_char.o >/dev/null 2>&1
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -g0 -std=gnu99 -fPIC 
-I../../lib/config -I../../lib/lib -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c text.c  -fPIC 
-DPIC -o .libs/libxnmisc_la-text.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -g0 -std=gnu99 -fPIC 
-I../../lib/config -I../../lib/lib -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c regexp.c  -fPIC 
-DPIC -o .libs/libxnmisc_la-regexp.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -g0 -std=gnu99 -fPIC 
-I../../lib/config -I../../lib/lib -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c mail.c -o 
libxnmisc_la-mail.o >/dev/null 2>&1
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -g0 -std=gnu99 -fPIC 
-I../../lib/config -I../../lib/lib -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c regexp.c -o 
libxnmisc_la-regexp.o >/dev/null 2>&1
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -g0 -std=gnu99 -fPIC 
-I../../lib/config -I../../lib/lib -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c text.c -o 
libxnmisc_la-text.o >/dev/null 2>&1
/bin/bash ../../libtool  --tag=CC   --mode=link gcc -Wall -Wextra -Werror -g0 
-std=gnu99 -fPIC -I../../lib/config -I../../lib/lib -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -static -lpcre -lz -lpthread -ldl -Wl,-z,relro -o 
libxnmisc.la  libxnmisc_la-archiver.lo libxnmisc_la-debug.lo 
libxnmisc_la-list_char.lo 

Bug#956680: marked as done (xneur: Please migrate to enchant-2)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 16:05:34 +
with message-id 
and subject line Bug#956680: fixed in xneur 0.20.0-3
has caused the Debian Bug report #956680,
regarding xneur: Please migrate to enchant-2
to be marked as done.

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

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


-- 
956680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xneur
Version: 0.20.0-2
Severity: important
Tags: patch
Control: block 947979 by -1

Dear maintainer,

Your package is affected by an ongoing transition from enchant(1) to
enchant- 2. You may find the transition information at
https://release.debian.org/transitions/html/enchant-2.html and
https://bugs.debian.org/947979 .

Current source code in Debian does not support enchant-2 yet.

The attached patch allows the package to build with enchant-2, I didn't
test the resulting package though.

Kind regards,
Laurent Bigonville


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
diff -Nru xneur-0.20.0/debian/control xneur-0.20.0/debian/control
--- xneur-0.20.0/debian/control 2018-07-19 00:38:47.0 +0200
+++ xneur-0.20.0/debian/control 2020-04-14 02:40:22.0 +0200
@@ -9,7 +9,7 @@
  libxt-dev,
  libpcre3-dev,
  pkg-config,
- libenchant-dev,
+ libenchant-2-dev,
  libgstreamer1.0-dev,
  libxosd-dev,
  libnotify-dev,
@@ -47,7 +47,7 @@
 Section: libdevel
 Depends: ${shlibs:Depends}, ${misc:Depends},
  libpcre3-dev,
- libenchant-dev,
+ libenchant-2-dev,
  libxneur (= ${binary:Version})
 Description: development files for xneur frontends and plugins.
  This package provides development files for building XNeur frontends and
diff -Nru xneur-0.20.0/debian/patches/enchant2.patch 
xneur-0.20.0/debian/patches/enchant2.patch
--- xneur-0.20.0/debian/patches/enchant2.patch  1970-01-01 01:00:00.0 
+0100
+++ xneur-0.20.0/debian/patches/enchant2.patch  2020-04-14 03:09:01.0 
+0200
@@ -0,0 +1,119 @@
+--- a/configure.ac
 b/configure.ac
+@@ -158,7 +158,7 @@ if test "x$with_spell" != "xno"; then
+ 
+   case $with_spell in
+   enchant|yes)
+-  PKG_CHECK_MODULES(ENCHANT, [enchant >= 1.0])
++  PKG_CHECK_MODULES(ENCHANT, [enchant-2 >= 1.0])
+   AC_DEFINE(WITH_ENCHANT, 1, [Define if you want enchant 
support])
+   ;;
+   aspell)
+--- a/xneur.pc
 b/xneur.pc
+@@ -6,5 +6,5 @@ includedir=${prefix}/include
+ Name: xneur
+ Description: XNeur library
+ Version: 0.20.0
+-Libs: -L${exec_prefix}/lib -lxneur  -lpcre -lenchant -lpthread -ldl
++Libs: -L${exec_prefix}/lib -lxneur  -lpcre -lenchant-2 -lpthread -ldl
+ Cflags: -I${prefix}/include
+--- a/plugins/statistic/Makefile.am
 b/plugins/statistic/Makefile.am
+@@ -7,7 +7,7 @@ pkglib_LTLIBRARIES = libxnstatistic.la
+ libxnstatistic_la_SOURCES = \
+   statistic.c
+ 
+-libxnstatistic_la_CFLAGS = -I@top_srcdir@/lib/config -I@top_srcdir@/lib/lib 
@DEFAULT_CFLAGS@
++libxnstatistic_la_CFLAGS = -I@top_srcdir@/lib/config -I@top_srcdir@/lib/lib 
@ASPELL_CFLAGS@ @ENCHANT_CFLAGS@ @DEFAULT_CFLAGS@
+ libxnstatistic_la_LDFLAGS = @X11_LIBS@
+
+ libxnstatistic_la_LIBADD = 
+--- a/lib/lib/xneur.h
 b/lib/lib/xneur.h
+@@ -29,7 +29,7 @@
+ #endif
+ 
+ #ifdef WITH_ENCHANT
+-# include 
++# include 
+ #endif
+ 
+ struct _window *main_window;
+--- a/lib/lib/xneurlib.c
 b/lib/lib/xneurlib.c
+@@ -30,7 +30,7 @@
+ #endif
+ 
+ #ifdef WITH_ENCHANT
+-# include 
++# include 
+ #endif
+ 
+ #include "xneur.h"
+--- a/lib/notify/Makefile.am
 b/lib/notify/Makefile.am
+@@ -16,7 +16,9 @@ libxnnotify_la_CFLAGS = -I@top_srcdir@/l
+   
@GSTREAMER_CFLAGS@  \
+   
@XOSD_CFLAGS@   \
+   
@LIBNOTIFY_CFLAGS@  \
+-  
@GTK_CFLAGS@
++   

Bug#970809: python3-venv is gone

[Raphael Hertzog]

Hi,

the package has been dropped from testing a while ago due to this bug
but it's not clear to me that there's a real bug here.

On Wed, 23 Sep 2020, Matthias Klose wrote:
> Package: pipx
> Version: 0.12.3.1-3
> Severity: serious
> Tags: sid bullseye
> 
> This package depends or build-depends on python3-venv, which is gone upstream.
> Please remove or re-implement that usage.

Can you be more verbose and back up this assertion with something
concrete?

What is gone exactly?

I still see the "venv" module in python3.9-stdlib. The reason why
python3-venv has been added in the Depends is because "ensurepip" was
required for the "python3 -m venv" to actually work.

See https://bugs.debian.org/954939

How is that wrong?

Cheers,

PS: Jonas, the package could use some love anyway, it's behind several
upstream releases.
-- 
  ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
  ⣾⠁⢠⠒⠀⣿⡁
  ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
  ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS

Bug#961814: marked as pending in golang-google-protobuf

[Shengjing Zhu]

On Fri, Jan 8, 2021 at 11:17 PM Alberto Bertogli
 wrote:
>
> On Thu, Jan 07, 2021 at 11:12:24PM +0800, Shengjing Zhu wrote:
> >On Thu, Jan 7, 2021 at 10:59 PM Alberto Bertogli
> > wrote:
> >> But those issues are not made worse by allowing golang-google-protobuf
> >> to go in, right?
> >>
> >
> >Let golang-google-protobuf go in is one thing, it's not difficult.
> >However without golang-goprotobuf 1.4.x it's not useful currently. But
> >it will be changed if upstream has switched to golang-google-protobuf
> >only.
>
> But IIUC that's what foka@'s lastest changes do - now the two packages
> are independent so golang-google-protobuf can go in?
>
> This would unblock:
> 1) Some upstream packages that have upgraded to the new library and are
> using pregenerated pb.go without the dependency.
> 2) Packages that have moved/want to move to the new library and generate
> pb.go as part of the build (without needing grpc).
>
> And no packages are forced into anything, since upstream needs to do the
> update explicitly anyway, the ones using golang-goprotobuf will continue
> to function just fine.
>
> I understand not all problems are fixed and some things remain, but it
> seems it'd be a step in the right direction since at least some packages
> will be able to move forward, without causing any new
> complications/regressions.
>
> Or am I missing something?
>

You are right. The only concern from my side is the usefulness of
golang-google-protobuf without upgrading golang-goprotobuf to 1.4.
If some packages are already ready for using golang-google-protobuf
solely, sure we should try.

-- 
Shengjing Zhu

Bug#961814: marked as pending in golang-google-protobuf

[Alberto Bertogli]

On Thu, Jan 07, 2021 at 11:12:24PM +0800, Shengjing Zhu wrote:

On Thu, Jan 7, 2021 at 10:59 PM Alberto Bertogli
 wrote:

But those issues are not made worse by allowing golang-google-protobuf
to go in, right?



Let golang-google-protobuf go in is one thing, it's not difficult.
However without golang-goprotobuf 1.4.x it's not useful currently. But
it will be changed if upstream has switched to golang-google-protobuf
only.


But IIUC that's what foka@'s lastest changes do - now the two packages 
are independent so golang-google-protobuf can go in?


This would unblock:
1) Some upstream packages that have upgraded to the new library and are 
   using pregenerated pb.go without the dependency.
2) Packages that have moved/want to move to the new library and generate 
   pb.go as part of the build (without needing grpc).


And no packages are forced into anything, since upstream needs to do the 
update explicitly anyway, the ones using golang-goprotobuf will continue 
to function just fine.


I understand not all problems are fixed and some things remain, but it 
seems it'd be a step in the right direction since at least some packages 
will be able to move forward, without causing any new 
complications/regressions.


Or am I missing something?

Thanks!
Alberto

Bug#978066: marked as done (pmix: breaks openmpi autopkgtest)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 14:51:00 +
with message-id 
and subject line Bug#978066: fixed in pmix 4.0.0-2
has caused the Debian Bug report #978066,
regarding pmix: breaks openmpi autopkgtest
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.)


-- 
978066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pmix
Version: 4.0.0~rc1-1
Severity: serious
Tags: ftbfs
Control: affects -1 + src:deal.ii
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

Hi Maintainer

The upload of pmix 4.0.0~rc1-1 to unstable causes the autopkgtests of
openmpi in testing to fail [1].  I've copied what I hope is the
relevant part of the log below.

There's also a FTBFS in the recent binNMU of deal.ii [2]. I believe
this is related to pmix rather than openmpi as the binNMU failed in
Ubuntu as well, where they have the new pmix, but not the new openmpi.

Regards
Graham


[1] https://ci.debian.net/packages/o/openmpi/testing/amd64/
[2] https://buildd.debian.org/status/package.php?p=deal.ii=unstable


autopkgtest [06:32:43]: test hello2: [---
[ci-359-a03b0931:01932] *** Process received signal ***
[ci-359-a03b0931:01932] Signal: Segmentation fault (11)
[ci-359-a03b0931:01932] Signal code: Invalid permissions (2)
[ci-359-a03b0931:01932] Failing at address: 0x5632cd610c70
[ci-359-a03b0931:01932] [ 0]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7fcc11a84d00]
[ci-359-a03b0931:01932] [ 1] [0x5632cd610c70]
[ci-359-a03b0931:01932] *** End of error message ***
Segmentation fault
autopkgtest [06:32:46]: test hello2: ---]
autopkgtest [06:32:46]: test hello2:  - - - - - - - - - - results - -
- - - - - - - -
hello2   FAIL non-zero exit status 139
autopkgtest [06:32:46]: test hello2:  - - - - - - - - - - stderr - - -
- - - - - - -
[ci-359-a03b0931:01932] *** Process received signal ***
[ci-359-a03b0931:01932] Signal: Segmentation fault (11)
[ci-359-a03b0931:01932] Signal code: Invalid permissions (2)
[ci-359-a03b0931:01932] Failing at address: 0x5632cd610c70
[ci-359-a03b0931:01932] [ 0]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7fcc11a84d00]
[ci-359-a03b0931:01932] [ 1] [0x5632cd610c70]
[ci-359-a03b0931:01932] *** End of error message ***
Segmentation fault
autopkgtest [06:32:47]: test hello4: preparing testbed
Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up autopkgtest-satdep (0) ...
(Reading database ... 18479 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [06:32:53]: test hello4: [---
[ci-359-a03b0931:02130] *** Process received signal ***
[ci-359-a03b0931:02130] Signal: Segmentation fault (11)
[ci-359-a03b0931:02130] Signal code: Invalid permissions (2)
[ci-359-a03b0931:02130] Failing at address: 0x55dfd16e6d00
[ci-359-a03b0931:02130] [ 0]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7f137754cd00]
[ci-359-a03b0931:02130] [ 1] [0x55dfd16e6d00]
[ci-359-a03b0931:02130] *** End of error message ***
Segmentation fault
autopkgtest [06:32:54]: test hello4: ---]
autopkgtest [06:32:55]: test hello4:  - - - - - - - - - - results - -
- - - - - - - -
hello4   FAIL non-zero exit status 139
autopkgtest [06:32:55]: test hello4:  - - - - - - - - - - stderr - - -
- - - - - - -
[ci-359-a03b0931:02130] *** Process received signal ***
[ci-359-a03b0931:02130] Signal: Segmentation fault (11)
[ci-359-a03b0931:02130] Signal code: Invalid permissions (2)
[ci-359-a03b0931:02130] Failing at address: 0x55dfd16e6d00
[ci-359-a03b0931:02130] [ 0]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bd00)[0x7f137754cd00]
[ci-359-a03b0931:02130] [ 1] [0x55dfd16e6d00]
[ci-359-a03b0931:02130] *** End of error message ***
Segmentation fault
autopkgtest [06:32:55]:  summary
hello1   FAIL non-zero exit status 139
hello2   FAIL non-zero exit status 139
hello4   FAIL non-zero exit status 139
--- End Message ---
--- Begin Message ---
Source: pmix
Source-Version: 4.0.0-2
Done: Alastair McKinstry 

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

A summary of the changes between this 

Bug#971615: marked as done (golang-github-russellhaering-goxmldsig: CVE-2020-15216)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 14:49:47 +
with message-id 
and subject line Bug#971615: fixed in golang-github-russellhaering-goxmldsig 
1.1.0-1
has caused the Debian Bug report #971615,
regarding golang-github-russellhaering-goxmldsig: CVE-2020-15216
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.)


-- 
971615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-russellhaering-goxmldsig
Version: 0.0~git20180430.7acd5e4-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for 
golang-github-russellhaering-goxmldsig.

CVE-2020-15216[0]:
| In goxmldsig (XML Digital Signatures implemented in pure Go) before
| version 1.1.0, with a carefully crafted XML file, an attacker can
| completely bypass signature validation and pass off an altered file as
| a signed one. A patch is available, all users of goxmldsig should
| upgrade to at least revision f6188febf0c29d7ffe26a0436212b19cb9615e64
| or version 1.1.0


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-15216
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15216
[1] 
https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7
[2] 
https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: golang-github-russellhaering-goxmldsig
Source-Version: 1.1.0-1
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated 
golang-github-russellhaering-goxmldsig 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, 07 Jan 2021 23:13:56 +
Source: golang-github-russellhaering-goxmldsig
Architecture: source
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Thorsten Alteholz 
Closes: 971615
Changes:
 golang-github-russellhaering-goxmldsig (1.1.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #971615)
   * add myself to Uploaders:
   * debian/control: use dh13
   * debian/control: bump standard to 4.5.1 (no changes)
   * reverse dependencies successfully built with ratt:
 - nothing todo for this package
Checksums-Sha1:
 a039996a5d073ed61274372764368c211c05d630 2706 
golang-github-russellhaering-goxmldsig_1.1.0-1.dsc
 9d6af0ce66bce57ce08b75e25f6f9d47326bfb4a 28875 
golang-github-russellhaering-goxmldsig_1.1.0.orig.tar.gz
 170cb2c7fb0d046bcf5460a02e1a9444c2d101fa 2724 
golang-github-russellhaering-goxmldsig_1.1.0-1.debian.tar.xz
 2eba28269d3eecece3a4bc0957d8699a98d01925 6975 
golang-github-russellhaering-goxmldsig_1.1.0-1_amd64.buildinfo
Checksums-Sha256:
 6447045329a1d2eb442ecc3e087255fd2c6d75ed8540712ec57d27aecdd13dec 2706 
golang-github-russellhaering-goxmldsig_1.1.0-1.dsc
 50837e3c87af633d8edce12d51ecab906443a5efe5d79e1c537d5942b21e4f71 28875 
golang-github-russellhaering-goxmldsig_1.1.0.orig.tar.gz
 074b371935ddb4b0607646d6c3a9ba233e2a577a6f1cd039e94a245db605f06c 2724 
golang-github-russellhaering-goxmldsig_1.1.0-1.debian.tar.xz
 bf87f0b967f7e7111426a8c15219281eab766c5206fed5bd0447ed684cb277b2 6975 
golang-github-russellhaering-goxmldsig_1.1.0-1_amd64.buildinfo
Files:
 d0001a4ebcbef7e8b8e0b9f6e0ca62dd 2706 devel optional 
golang-github-russellhaering-goxmldsig_1.1.0-1.dsc
 a69a942ef20f1a2ff45bfb49912d0e8a 28875 devel optional 
golang-github-russellhaering-goxmldsig_1.1.0.orig.tar.gz
 07257b27a72664a0b940b92cfd85b341 2724 devel optional 
golang-github-russellhaering-goxmldsig_1.1.0-1.debian.tar.xz
 84382da7a8a18c213df3b3fe4306809a 6975 devel optional 

Bug#979573: nvidia-driver: Screen freezes since upgrade to 455.45

[Andreas Beckmann]

My reply bounced with

: host gretel.discordia.ch[185.95.218.132] said: 530
5.7.0 Must issue a STARTTLS command first (in reply to MAIL FROM command)

Andreas

Bug#979443: chromium: desktop GUI locks up as Xorg process goes to 100%

[Steve A.]

Thanks, Jan.  I killed chromium, upgraded to 87* again, and re-launched 
with the recommended command last night.  The user is back on this 
morning and I'm monitoring from another machine.


Steve


Jan Luca Naumann wrote on 1/7/21 2:30 AM:

Dear Steve,

with the upgrade to 87.* we included the ANGLE library which manages the
OpenGL access of chromium. Maybe this is the cause of your problem.

Could you try to launch "$ chromium --use-gl=desktop"? This should
disable the usage of ANGLE.

Best,
Jan

Bug#979573: nvidia-driver: Screen freezes since upgrade to 455.45

[Andreas Beckmann]

On 1/8/21 3:15 PM, Peter Keel wrote:
> [82609.756755] nvidia-modeset/: page allocation failure: order:4, 
> mode:0x40cc0(GFP_KERNEL|__GFP_COMP), nodemask=
You could try the 460.xx beta driver from experimental which seems to 
have a fix for that:

 - Improved the memory allocation strategy in nvidia-modeset.ko to reduce
   the likelihood of out-of-memory errors, which typically manifest as
   "page allocation failure" messages in the kernel log.


Andreas

Bug#971127: marked as done (ofxstatement-plugins: FTBFS: AssertionError: Failed doctest test for ofxstatement.plugins.tests.test_lbbamazon.doctest_LbbAmazonCsvStatementParser)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 14:26:51 +
with message-id 
and subject line Bug#971127: fixed in ofxstatement-plugins 20210108
has caused the Debian Bug report #971127,
regarding ofxstatement-plugins: FTBFS: AssertionError: Failed doctest test for 
ofxstatement.plugins.tests.test_lbbamazon.doctest_LbbAmazonCsvStatementParser
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.)


-- 
971127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ofxstatement-plugins
Version: 20200505
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd ofxstatement-1822direkt && python3 setup.py test
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> writing src/ofxstatement_germany_1822direkt.egg-info/PKG-INFO
> writing dependency_links to 
> src/ofxstatement_germany_1822direkt.egg-info/dependency_links.txt
> writing entry points to 
> src/ofxstatement_germany_1822direkt.egg-info/entry_points.txt
> writing namespace_packages to 
> src/ofxstatement_germany_1822direkt.egg-info/namespace_packages.txt
> writing requirements to 
> src/ofxstatement_germany_1822direkt.egg-info/requires.txt
> writing top-level names to 
> src/ofxstatement_germany_1822direkt.egg-info/top_level.txt
> reading manifest file 
> 'src/ofxstatement_germany_1822direkt.egg-info/SOURCES.txt'
> writing manifest file 
> 'src/ofxstatement_germany_1822direkt.egg-info/SOURCES.txt'
> running build_ext
> 
> --
> Ran 0 tests in 0.000s
> 
> OK
> # run pytest with doctest and ignore exit code 5 (no tests found)
> cd ofxstatement-1822direkt && PYTEST_ADDOPTS=--doctest-modules python3 
> setup.py pytest; \
>   PYTEST_RESULT=$?; \
>   test $PYTEST_RESULT -eq 5 && exit 0; \
>   exit $PYTEST_RESULT
> running pytest
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> writing src/ofxstatement_germany_1822direkt.egg-info/PKG-INFO
> writing dependency_links to 
> src/ofxstatement_germany_1822direkt.egg-info/dependency_links.txt
> writing entry points to 
> src/ofxstatement_germany_1822direkt.egg-info/entry_points.txt
> writing namespace_packages to 
> src/ofxstatement_germany_1822direkt.egg-info/namespace_packages.txt
> writing requirements to 
> src/ofxstatement_germany_1822direkt.egg-info/requires.txt
> writing top-level names to 
> src/ofxstatement_germany_1822direkt.egg-info/top_level.txt
> reading manifest file 
> 'src/ofxstatement_germany_1822direkt.egg-info/SOURCES.txt'
> writing manifest file 
> 'src/ofxstatement_germany_1822direkt.egg-info/SOURCES.txt'
> running build_ext
> = test session starts 
> ==
> platform linux -- Python 3.8.6, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>/_ofxstatement-germany/germany_1822direkt
> collected 0 items
> 
> = no tests ran in 0.01 seconds 
> =
> cd ofxstatement-airbankcz && python3 setup.py test
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> writing src/ofxstatement_airbankcz.egg-info/PKG-INFO
> writing dependency_links to 
> src/ofxstatement_airbankcz.egg-info/dependency_links.txt
> writing entry points to src/ofxstatement_airbankcz.egg-info/entry_points.txt
> writing namespace_packages to 
> src/ofxstatement_airbankcz.egg-info/namespace_packages.txt
> writing requirements to src/ofxstatement_airbankcz.egg-info/requires.txt
> writing top-level names to src/ofxstatement_airbankcz.egg-info/top_level.txt
> reading manifest file 'src/ofxstatement_airbankcz.eg

Processed: Bug#971615 marked as pending in golang-github-russellhaering-goxmldsig

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #971615 [src:golang-github-russellhaering-goxmldsig] 
golang-github-russellhaering-goxmldsig: CVE-2020-15216
Added tag(s) pending.

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

Bug#971615: marked as pending in golang-github-russellhaering-goxmldsig

[Thorsten Alteholz]

Control: tag -1 pending

Hello,

Bug #971615 in golang-github-russellhaering-goxmldsig 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/go-team/packages/golang-github-russellhaering-goxmldsig/-/commit/f3b3d217ce0259a460fc000518008928e66978e8


Import Debian changes 1.1.0-1

golang-github-russellhaering-goxmldsig (1.1.0-1) unstable; urgency=medium

  * New upstream release (Closes: #971615)
  * add myself to Uploaders:
  * debian/control: use dh13
  * debian/control: bump standard to 4.5.1 (no changes)
  * reverse dependencies successfully built with ratt:
- nothing todo for this package


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/971615

Bug#972912: [Pkg-samba-maint] Bug#972912: Incorrect fix to bug

[Sven Mueller]

Ack, merge request created.
I had already built ldb with the patch for both unstable and the
environment I ran into issues due to the symbols check and also rebuilt
samba in both afterwards. Both built fine and at least basic functionality
tests also worked fine.

Am Fr., 8. Jan. 2021 um 13:33 Uhr schrieb Mathieu Parent <
math.par...@gmail.com>:

> Le lun. 21 déc. 2020 à 16:06, Sven Mueller  a
> écrit :
> >
> > Well, turns out that apparently nobody else bothers with a .symbols file
> for Python extensions. I looked at the packages for samba, numpy, mypy and
> python-stdlib-extensions. And if the Python maintainers themselves don't do
> it, you probably shouldn't.
> >
> > I attached a diff to remove the relevant file and the setup for it. I
> also added some verbosity to the stuff debhelper does (I find it harder to
> debug build issues without it).
> > I verified that except for this symbols file going away, nothing else
> changed. (Most notable, the main libldb-dev package still looks the same.)
> - Verified via diffoscope which only showed expected changes (timestamps,
> mostly)
> >
> > I'll see if I can turn it into a pull request on Salsa, but my git-foo
> is weaker than it probably should be, so feel free to just apply my patch
> yourself.
> > If I create a pull request, should that include an update to
> debian/changelog?
>
> Hello, just a quick note that I won't work on this for bullseye. If
> you can propose a MR in salsa and test that samba builds and works,
> I'll happily review it.
>
> Regards
> --
> Mathieu Parent
>

Bug#972301: closing 972301

[Jochen Sprickerhof]

close 972301 3.5.0+dfsg1-5
thanks

Bug#979570: dpkg: Breaks perfectly valid usage of __FILE__

[Lisandro Damián Nicanor Pérez Meyer]

Source: dpkg
Version: 1.20.6
Severity: serious
Justification: Breaks well defined functionality
X-Debbugs-Cc: pkg-kde-t...@alioth-lists.debian.net, 
reproducible-bui...@lists.alioth.debian.org

Hi! As discussed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901
mangling __FILE__, even if for reproducible builds, breaks a perfectly valid
usage of __FILE__.

Please revert #974087 until someone provides a valid patch for QFINDTESTDATA
and it's well tested.

-- Package-specific info:

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64, armhf

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Processed: closing 972301

[Debian Bug Tracking System]

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

> close 972301 3.5.0+dfsg1-5
Bug #972301 [ignition-common] ignition-common: FTBFS with 
DEB_BUILD_OPTIONS=reproducible=+fixfilepath
There is no source info for the package 'ignition-common' at version 
'3.5.0+dfsg1-5' with architecture ''
Unable to make a source version for version '3.5.0+dfsg1-5'
Marked as fixed in versions 3.5.0+dfsg1-5.
Bug #972301 [ignition-common] ignition-common: FTBFS with 
DEB_BUILD_OPTIONS=reproducible=+fixfilepath
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#979569: frama-c ftbfs on armel, mipsel and mips64el

[Matthias Klose]

Package:src:frama-c
Version: 20201209+titanium-2
Severity: serious
Tags: sid bullseye

[...]
ocamlfind: Not supported in your configuration: ocamlopt
make[1]: *** [share/Makefile.generic:88: src/libraries/stdlib/extlib.cmx] Error 
2
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j4 returned exit code 2

Bug#972308: marked as done (kookbook: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 13:19:04 +
with message-id 
and subject line Bug#972308: fixed in kookbook 0.2.1-2
has caused the Debian Bug report #972308,
regarding kookbook: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
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.)


-- 
972308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kookbook
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fixfilepath ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

When the reproducible=+fixfilepath feature is enabled (either through
DEB_BUILD_OPTIONS, or using a dpkg that enables this by default),
kookbook fails to build from source:

  
http://qa-logs.debian.net/2020/09/26.fixfilepath/kookbook_0.2.1-1_unstable_fixfilepath.log


While the "fixfilepath" feature is not currently enabled by
dpkg-buildflags by default, it may become the default at some point in
the future, and can be triggered manually by setting
DEB_BUILD_OPTIONS=reproducible=+fixfilepath in the build environment. It
is also used in the tests.reproducible-builds.org infrastructure when
testing unstable and experimental.

More information about this issue is available at:

  
https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html


I have not identified the exact cause of this issue, but a common
trigger is test suites expecting __FILE__ to resolve to an absolute
path.

The attached patch works around this issue by disabling the fixfilepath
feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath.


Thanks for maintaining kookbook!


live well,
  vagrant

From 91638d097b1f535450a283647f3ca42618d3ee95 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Fri, 16 Oct 2020 00:11:55 +
Subject: [PATCH] debian/rules: Disable fixfilepath feature, as it triggers
 build failures when enabled.

https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html
---
 debian/rules | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index e31c6bd..747b7d3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,7 +1,8 @@
 #!/usr/bin/make -f
 
 # Enable additional hardening options.
-export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+# Disable fixfilepath as it triggers build failures.
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all reproducible=-fixfilepath
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
 %:
-- 
2.28.0



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: kookbook
Source-Version: 0.2.1-2
Done: Stuart Prescott 

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated kookbook 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, 09 Jan 2021 00:05:23 +1100
Source: kookbook
Architecture: source
Version: 0.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Stuart Prescott 
Closes: 972308
Changes:
 kookbook (0.2.1-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Update standards version to 4.4.1, no changes needed.
 .
   [ Stuart Prescott ]
   * Update Standards-Version to 4.5.1 (no changes required).
   * Update to debhelper-compat (= 13).
   * Set build option reproducible=-fixfilepath to prevent dpkg change from
 breaking test suite (Closes: #972308).
Checksums-Sha1:
 ab4a835f825ef44edff8bf95e15eb6cdf118e0d2 2031 kookbook_0.2.1-2.dsc
 ed01c22928a10bf70cab52b20558b333eb30d2b0 7780 kookbook_0.2.1-2.debian.tar.xz
 2483d483c444570cfe8ca5552290237f8d6513ca 11161 kookbook_0.2.1-2_amd64.buildinfo
Checksums-Sha256:
 78c0e35b858369ccda84cf5953c10db37cef1be8befb7917381f2480d3458e57 2031 
kookbook_0.2.1-2.dsc
 

Bug#979562: lightdm session termination does not stop xscreensaver

[Eduard Bloch]

Hallo,

I don't fully agree. If you don't see a problem here, WHERE do you see
it?

Under my naive assumptions, it looks like SIGTERM is not sent when
lightdm stops the service. So apparently a systemd issue.

I would like to investigate more but a there seems to be no "debug" or
"trace" mode for such kind of issues in systemd. Mind to share your
knowledge?

* Michael Biebl [Fri, Jan 08 2021, 01:34:43PM]:
> Control: reassign -1 xscreensaver
> 
> I don't see a systemd problem here, so re-assigning to xscreensaver.
> 
> Am 08.01.21 um 13:04 schrieb Eduard Bloch:
> > Package: systemd
> > Version: 247.2-4
> > Severity: serious
> > 
> > Hi,
> > 
> > I am reporting this with high severity because it might affect system
> > security.
> > 
> > For details of this issue, see 978589. There are different symptoms to
> > see but the originating cause is apparently the same:
> > 
> >   - xscreensaver user service is enabled as documented in its README
> >   - lightdm starts the service in its internal user session (owned by
> > "lightdm" user)
> >   - lightdm stops its session when the login happens. However,
> > xscreensaver process is NOT terminated for unknown reason.
> >   - having this xscreensaver hanging around disturbs the startup of
> > another xscreensaver process in the new user session
> >   - after ~15s the old xscreensaver process (from lightdm) is finally
> > dead, apparently a SIGTERM is emited only then!
> > 
> > Visible symptoms:
> > 
> > In the meantime, someone might lock the system (by xscreensaver-command)
> > and go away, assuming that xscreensaver is locked. And then it suddenly
> > dies.
> > 
> > Same things happens if xscreensaver is invoked from .xsession or similar
> > contents instead of user service.
> > 
> > Best regards,
> > Eduard.
> > 
> > -- Package-specific info:
> > 
> > -- System Information:
> > Debian Release: bullseye/sid
> >APT prefers unstable-debug
> >APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), 
> > (1, 'experimental-debug'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> > 
> > Kernel: Linux 5.10.5+ (SMP w/12 CPU threads)
> > Kernel taint flags: TAINT_OOT_MODULE
> > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE 
> > not set
> > Shell: /bin/sh linked to /bin/bash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> > 
> > Versions of packages systemd depends on:
> > ii  adduser  3.118
> > ii  libacl1  2.2.53-9
> > ii  libapparmor1 2.13.6-3
> > ii  libaudit11:3.0-2
> > ii  libblkid12.36.1-4
> > ii  libc62.31-9
> > ii  libcap2  1:2.44-1
> > ii  libcrypt11:4.4.17-1
> > ii  libcryptsetup12  2:2.3.4-1
> > ii  libgcrypt20  1.8.7-2
> > ii  libgnutls30  3.7.0-5
> > ii  libgpg-error01.38-2
> > ii  libip4tc21.8.6-1
> > ii  libkmod2 28-1
> > ii  liblz4-1 1.9.3-1
> > ii  liblzma5 5.2.5-1.0
> > ii  libmount12.36.1-4
> > ii  libpam0g 1.4.0-2
> > ii  libseccomp2  2.5.1-1
> > ii  libselinux1  3.1-2+b2
> > ii  libsystemd0  247.2-4
> > ii  libzstd1 1.4.8+dfsg-1
> > ii  mount2.36.1-4
> > ii  systemd-timesyncd [time-daemon]  247.2-4
> > ii  util-linux   2.36.1-4
> > 
> > Versions of packages systemd recommends:
> > ii  dbus  1.12.20-1
> > 
> > Versions of packages systemd suggests:
> > ii  policykit-10.105-29
> > pn  systemd-container  
> > 
> > Versions of packages systemd is related to:
> > pn  dracut   
> > ih  initramfs-tools  0.139
> > ii  libnss-systemd   247.2-4
> > ii  libpam-systemd   247.2-4
> > ii  udev 247.2-4
> > 
> > -- no debconf information
> > 
> > --
> > Chirurgen sind die einzigen Menschen, die ohne fremden Blinddarm und
> > ohne fremde Mandeln nicht leben können.
> > -- Peter Sellers
> > 
> 
> 


Best regards,
Eduard.


signature.asc
Description: PGP signature

Bug#979567: src:libnfo: invalid maintainer address

[Ansgar]

Source: libnfo
Version: 1.0.1-1
Severity: serious
Tags: bullseye sid
X-Debbugs-Cc: Holger Levsen 

The maintainer address is invalid, see below.

Ansgar

 Start of forwarded message 
From: Mail Delivery System 
Subject: Mail delivery failed: returning message to sender
Date: Fri, 08 Jan 2021 12:52:12 +

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  dav...@geexbox.org
host fry.geexbox.org [208.70.252.90]
SMTP error from remote mail server after RCPT TO::
550 5.1.1 : Recipient address rejected:
User unknown in local recipient table
Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;davide@geexbox.org
Status: 5.0.0
Remote-MTA: dns; fry.geexbox.org
Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in local recipient table

Bug#978936: marked as done (darktable: FTBFS on arm64)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 12:48:40 +
with message-id 
and subject line Bug#978936: fixed in darktable 3.4.0-2
has caused the Debian Bug report #978936,
regarding darktable: FTBFS on arm64
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.)


-- 
978936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: darktable
Version: 3.4.0-1
Severity: serious
Tags: upstream
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Control: -1 forwarded https://github.com/darktable-org/darktable/issues/7583

The new release requires xmmintrin.h in several places, and that
include file is only present (in Debian) on amd64.


https://buildd.debian.org/status/fetch.php?pkg=darktable=arm64=3.4.0-1=1608929069=0


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

Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages darktable depends on:
ii  libc62.31-6
ii  libcairo21.16.0-4
ii  libcolord-gtk1   0.1.26-2
ii  libcolord2   1.4.4-2
ii  libcups2 2.3.3op1-3
ii  libcurl3-gnutls  7.72.0-1
ii  libexiv2-27  0.27.3-3
ii  libgcc-s110.2.1-3
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.4-1
ii  libgomp1 10.2.1-3
ii  libgphoto2-6 2.5.26-2
ii  libgphoto2-port122.5.26-2
ii  libgraphicsmagick-q16-3  1.4+really1.3.36-1
ii  libgtk-3-0   3.24.24-1
ii  libilmbase25 2.5.3-2
ii  libjpeg62-turbo  1:2.0.5-1.1
ii  libjson-glib-1.0-0   1.6.0-2
ii  liblcms2-2   2.9-4+b1
ii  liblensfun1  0.3.2-5
ii  liblua5.3-0  5.3.3-1.1+b1
ii  libopenexr25 2.5.3-2
ii  libopenjp2-7 2.3.1-1
ii  libosmgpsmap-1.0-1   1.1.0-7
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpugixml1v51.11.4-1
ii  librsvg2-2   2.50.2+dfsg-1
ii  libsecret-1-00.20.4-1
ii  libsoup2.4-1 2.72.0-2
ii  libsqlite3-0 3.34.0-1
ii  libstdc++6   10.2.1-3
ii  libtiff5 4.2.0-1
ii  libwebp6 0.6.1-2+b1
ii  libx11-6 2:1.6.12-1
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  zlib1g   1:1.2.11.dfsg-2

darktable recommends no packages.

darktable suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl/uD6kACgkQA0U5G1Wq
FSFD8A/+KlBt0LMrGwiDWI/p56Gcdg5EMMbPMG7G7E1LJBBMSyQ5EhEUjo+TQRhR
HRBzfEKPgkYJu+93XvDRVeITJtq9xIL1KTISWgcQRTIC71SDDHGtG7nvJTLVK/fD
7+PnVI3hTPoyNmg2WAK8PtX/TbsOcGNIsx3h173/vonGpL7PUMkhJOWNhH4u/OB8
R7NgusGmji5ylnaPFVNYHII0Ig4r2pBQa7crNiBbCCS7gLMV/BZbp+zbcsnFyLsR
Iynu2+I0S0lCHIEbMblwwz68eHoC0cwaJQ6ypcansMT/4v8pYWnByc9U9qZfc8yf
g4ZhQKBxofq3GRFY/k+CguIDXub1jBP23WWM7lWZgRL/l0BYQDybPvJ7kqCevDM3
xdJNA2/XZA7M6e0VlNR7V4wuuSaThhUusqE+FZebS2yfCfV2n4QdW74vBDV+E7dP
DqexnuS5Xig0lC/PZ5Eg49ZN4k65Qpf945UMjbHzSKNa45m4+wJLigxdvdMXBN0H
E0cdYwGecL0WAlzZNUtfLLEYG0zyZxijrWHV3DjysDf3AnxWcuS+3fFoy/aR/oNw
niQFX+M21HLUaqpJBTBs3xCZWMvmMK6vbETuWqEzSR18HDKIXnuTCkpNsZ23BnQ7
5OrPfb2eZZUWkfg9fhFS6lgv6Ysk/Liv7FJ9YVrR4V7XKx7m6Ow=
=HiaZ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: darktable
Source-Version: 3.4.0-2
Done: David Bremner 

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

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated darktable package)

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

Processed: Re: Bug#979562: lightdm session termination does not stop xscreensaver

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 xscreensaver
Bug #979562 [systemd] lightdm session termination does not stop xscreensaver
Bug reassigned from package 'systemd' to 'xscreensaver'.
No longer marked as found in versions systemd/247.2-4.
Ignoring request to alter fixed versions of bug #979562 to the same values 
previously set

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

Bug#979562: lightdm session termination does not stop xscreensaver

[Michael Biebl]

Control: reassign -1 xscreensaver

I don't see a systemd problem here, so re-assigning to xscreensaver.

Am 08.01.21 um 13:04 schrieb Eduard Bloch:

Package: systemd
Version: 247.2-4
Severity: serious

Hi,

I am reporting this with high severity because it might affect system
security.

For details of this issue, see 978589. There are different symptoms to
see but the originating cause is apparently the same:

  - xscreensaver user service is enabled as documented in its README
  - lightdm starts the service in its internal user session (owned by
"lightdm" user)
  - lightdm stops its session when the login happens. However,
xscreensaver process is NOT terminated for unknown reason.
  - having this xscreensaver hanging around disturbs the startup of
another xscreensaver process in the new user session
  - after ~15s the old xscreensaver process (from lightdm) is finally
dead, apparently a SIGTERM is emited only then!

Visible symptoms:

In the meantime, someone might lock the system (by xscreensaver-command)
and go away, assuming that xscreensaver is locked. And then it suddenly
dies.

Same things happens if xscreensaver is invoked from .xsession or similar
contents instead of user service.

Best regards,
Eduard.

-- Package-specific info:

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

Kernel: Linux 5.10.5+ (SMP w/12 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-9
ii  libapparmor1 2.13.6-3
ii  libaudit11:3.0-2
ii  libblkid12.36.1-4
ii  libc62.31-9
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.17-1
ii  libcryptsetup12  2:2.3.4-1
ii  libgcrypt20  1.8.7-2
ii  libgnutls30  3.7.0-5
ii  libgpg-error01.38-2
ii  libip4tc21.8.6-1
ii  libkmod2 28-1
ii  liblz4-1 1.9.3-1
ii  liblzma5 5.2.5-1.0
ii  libmount12.36.1-4
ii  libpam0g 1.4.0-2
ii  libseccomp2  2.5.1-1
ii  libselinux1  3.1-2+b2
ii  libsystemd0  247.2-4
ii  libzstd1 1.4.8+dfsg-1
ii  mount2.36.1-4
ii  systemd-timesyncd [time-daemon]  247.2-4
ii  util-linux   2.36.1-4

Versions of packages systemd recommends:
ii  dbus  1.12.20-1

Versions of packages systemd suggests:
ii  policykit-10.105-29
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ih  initramfs-tools  0.139
ii  libnss-systemd   247.2-4
ii  libpam-systemd   247.2-4
ii  udev 247.2-4

-- no debconf information

--
Chirurgen sind die einzigen Menschen, die ohne fremden Blinddarm und
ohne fremde Mandeln nicht leben können.
-- Peter Sellers






OpenPGP_signature
Description: OpenPGP digital signature

Bug#972912: [Pkg-samba-maint] Bug#972912: Incorrect fix to bug

[Mathieu Parent]

Le lun. 21 déc. 2020 à 16:06, Sven Mueller  a écrit :
>
> Well, turns out that apparently nobody else bothers with a .symbols file for 
> Python extensions. I looked at the packages for samba, numpy, mypy and 
> python-stdlib-extensions. And if the Python maintainers themselves don't do 
> it, you probably shouldn't.
>
> I attached a diff to remove the relevant file and the setup for it. I also 
> added some verbosity to the stuff debhelper does (I find it harder to debug 
> build issues without it).
> I verified that except for this symbols file going away, nothing else 
> changed. (Most notable, the main libldb-dev package still looks the same.) - 
> Verified via diffoscope which only showed expected changes (timestamps, 
> mostly)
>
> I'll see if I can turn it into a pull request on Salsa, but my git-foo is 
> weaker than it probably should be, so feel free to just apply my patch 
> yourself.
> If I create a pull request, should that include an update to debian/changelog?

Hello, just a quick note that I won't work on this for bullseye. If
you can propose a MR in salsa and test that samba builds and works,
I'll happily review it.

Regards
-- 
Mathieu Parent

Bug#954270: kmc: arm64 autopkgtest time out

[Juhani Numminen]

For the record in bug #954270,

to delay autoremoval of iva and kmc from testing scheduled on 2021-01-09,
I'm writing this little status update regarding their testing migration.

My understanding is that kmc and iva shall migrate to testing once the
FTP Team processes this removal request: https://bugs.debian.org/977498


--
Juhani

Processed: Re: Bug#974779 closed by Debian FTP Masters (reply to Gianfranco Costamagna ) (Bug#974779: fixed in llvm-toolchain-9 1:9.0.1-16)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #974779 {Done: Gianfranco Costamagna } [julia] 
julia: Please upgrade to llvm-toolchain-11
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions julia/1.5.3+dfsg-3 and 
llvm-toolchain-9/1:9.0.1-16.

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

Bug#974779: closed by Debian FTP Masters (reply to Gianfranco Costamagna ) (Bug#974779: fixed in llvm-toolchain-9 1:9.0.1-16)

[Sylvestre Ledru]

control: reopen -1

It isn't fixed for real as Julia needs to be updated!

S


Le 08/01/2021 à 13:06, Debian Bug Tracking System a écrit :

This is an automatic notification regarding your Bug report
which was filed against the julia package:

#974779: julia: Please upgrade to llvm-toolchain-11

It has been closed by Debian FTP Masters  (reply to 
Gianfranco Costamagna ).

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Debian FTP Masters 
 (reply to Gianfranco Costamagna 
) by
replying to this email.

Bug#979563: gitlab: file listing on web interface and git push over ssh fails

[Pirate Praveen]

Package: gitlab
Version: 13.5.6-1
Severity: grave

Uploaded gitlab 13.5.6 to experimental for more testing, but some core 
features are broken, likely due to new version of rugged/libgit2 
already in debian which upstream does not support yet.


When visiting any project, for example,
http://gitlab.lxc/praveen/test

The UI has this error message,
An error occurred while fetching folder content.

The browser error console has this,

Failed to load resource: the server responded with a status of 500 
(Internal Server Error)

commons-pages.projects.show-pages.projects.tree.show.1cb74241.chunk.js:1:60290

pravi@mahishi:/tmp$ git clone git...@gitlab.lxc:praveen/test.git
Cloning into 'test'...
remote: Enumerating objects: 34, done.
remote: Counting objects: 100% (34/34), done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 34 (delta 10), reused 32 (delta 9), pack-reused 0
Receiving objects: 100% (34/34), done.
Resolving deltas: 100% (10/10), done.
pravi@mahishi:/tmp$ cd test/
pravi@mahishi:/tmp/test$ ls
hello-there help kfdhgkfdjg README.md sdhffjh test testing xzy y
pravi@mahishi:/tmp/test$ git rm kfdhgkfdjg
rm 'kfdhgkfdjg'
pravi@mahishi:/tmp/test$ git commit -a
[master 60a10f1] remove
1 file changed, 0 insertions(+), 0 deletions(-)
delete mode 100644 kfdhgkfdjg
pravi@mahishi:/tmp/test$ git push
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Delta compression using up to 4 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (2/2), 219 bytes | 219.00 KiB/s, done.
Total 2 (delta 1), reused 0 (delta 0), pack-reused 0
remote: GitLab: Push operation timed out
remote:
remote: Timing information for debugging purposes:
remote: Running checks for ref: master
remote: Checking if you are allowed to push... (9.09ms)
remote: Checking if default branch is being deleted... (0.03ms)
remote: Checking if you are force pushing to a protected branch... 
(35.18ms)
remote: Checking if you are allowed to push to the protected branch... 
(41.35ms)
remote: Scanning repository for blobs stored in LFS and verifying their 
files have been uploaded to GitLab... (cancelled after 29523.48ms)

To gitlab.lxc:praveen/test.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'gitlab.lxc:praveen/test.git'

Bug#978232: orage: FTBFS: build-dependency not installable: xfce4-panel (= 4.14.4-1)

[Juhani Numminen]

tags 977628 + moreinfo
thanks

On Tue, 5 Jan 2021 16:13:29 +0100 Slavko  wrote:
> Hi,
> 
> quick look into ./configure --help shows the --disable-libxfce4panel
> option, while i do not understand it in depth, but can be quick
> solution.
> 
> If i properly understand, it will not be usable with XFCE's panel, but
> retains as standalone application. Actually, here is not standalone
> alternative, which is able to show ICS files calendars, thus keeping
> orage is important, at least for me.

Thank you Yves-Alexis for implementing this in orage/4.12.1-8.

I noticed that the removal request still stands ( 
https://bugs.debian.org/977628 ).
Do you still intend to remove orage from Debian or are you happy to keep it for 
now?


Regards,
Juhani

Bug#974779: [Pkg-julia-devel] Bug#974779: Bug#974779: severity - Julia: Please upgrade to llvm-toolchain-11

[Norbert Preining]

Hi Gianfranco,

Thanks for looking into this, very much appreciated!

Do we really need a new upload of Julia, or can't we kick of a new trial build 
at ppc64el?

Also, if an upload is necessary and someone else in the Julia team beats me, no 
problem with that ;-)

Again thanks a lot for your help, let us hope that the build problems are 
really fixed with the patches...

All the best

Norbert
-- 
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#974779: marked as done (julia: Please upgrade to llvm-toolchain-11)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 12:03:40 +
with message-id 
and subject line Bug#974779: fixed in llvm-toolchain-9 1:9.0.1-16
has caused the Debian Bug report #974779,
regarding julia: Please upgrade to llvm-toolchain-11
to be marked as done.

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

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


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

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the 
archive, please upgrade to -11.

Thanks,
Sylvestre

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (500, 'stable-updates'), 
(500, 'stable'), (500, 'oldstable'), (300, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages julia depends on:
pn  julia-common   
ii  libamd21:5.8.1+dfsg-2
ii  libarpack2 3.7.0-3
ii  libc6  2.31-4
ii  libcamd2   1:5.8.1+dfsg-2
ii  libcholmod31:5.8.1+dfsg-2
ii  libcolamd2 1:5.8.1+dfsg-2
ii  libcurl3-gnutls7.72.0-1
pn  libdsfmt-19937-1   
ii  libfftw3-double3   3.3.8-2
ii  libfftw3-single3   3.3.8-2
ii  libgcc-s1 [libgcc1]10.2.0-16
ii  libgcc11:8.3.0-6
ii  libgfortran5   10.2.0-16
pn  libgit2-27 
ii  libgit2-28 0.28.5+dfsg.1-1
ii  libgmp10   2:6.2.0+dfsg-6
pn  libjulia1  
ii  libllvm10  1:10.0.1-8
pn  libllvm3.8 
ii  libmbedcrypto3 2.16.5-1
ii  libmbedtls12   2.16.5-1
ii  libmbedx509-0  2.16.5-1
pn  libmpfr4   
ii  libmpfr6   4.1.0-3
pn  libopenblas-base   
pn  libopenlibm2   
pn  libopenlibm3   
pn  libopenspecfun1
ii  libpcre2-8-0   10.34-7
ii  libquadmath0   10.2.0-16
pn  libspqr2   
ii  libssh2-1  1.8.0-2.1
ii  libstdc++6 10.2.0-16
pn  libsuitesparseconfig4  
ii  libsuitesparseconfig5  1:5.8.1+dfsg-2
ii  libumfpack51:5.8.1+dfsg-2
ii  libunwind8 1.3.2-2
ii  libutf8proc2   2.5.0-1

Versions of packages julia recommends:
ii  git  1:2.29.2-1
ii  openssl  1.1.1h-1

Versions of packages julia suggests:
pn  ess
pn  julia-doc  
pn  vim-julia  
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-9
Source-Version: 1:9.0.1-16
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
llvm-toolchain-9 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, 08 Jan 2021 12:48:25 +0100
Source: llvm-toolchain-9
Architecture: source
Version: 1:9.0.1-16
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Gianfranco Costamagna 
Closes: 974779
Changes:
 llvm-toolchain-9 (1:9.0.1-16) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * Fix the fuzzer build on i386.
 .
   [ Gianfranco Costamagna ]
   * Add two patches backported to fix ppc64el julia build (Closes: #974779)
Checksums-Sha1:
 3f5d31c885e2a8b963b90bda7c3209a33c037903 6002 llvm-toolchain-9_9.0.1-16.dsc
 376b81a13ace56e39f179ed6f3c4d8505a0d4a1b 137356 
llvm-toolchain-9_9.0.1-16.debian.tar.xz
 7d52827c9b609ad18d850d5713e9767561ca98b0 11549 
llvm-toolchain-9_9.0.1-16_source.buildinfo
Checksums-Sha256:
 fbd716b9e8169e67b293bfde30ad2336097cd1e3140b545c94af0d332e419450 6002 
llvm-toolchain-9_9.0.1-16.dsc
 dd0a10b1d75f0e51eb596733386c53156a1adf3dc859190736676e57eff3d1cd 137356 
llvm-toolchain-9_9.0.1-16.debian.tar.xz
 f2d2d69ee3fa81dd0f3e693f410e64bc4e7595c83f5bc4aa7186ae7c33da05b8 11549 

Bug#978452: version dependency

[grin]

Watch out version dependency, too. It will not work with v2.0 (2.0.0+dfsg-1+b1)

g

Bug#974779: [Pkg-julia-devel] Bug#974779: severity - Julia: Please upgrade to llvm-toolchain-11

[Gianfranco Costamagna]

Hello Norbert,

On Fri, 8 Jan 2021 19:59:10 +0900 Norbert Preining  
wrote:
> Dear Sebastian,
> 
> thanks for your email!
> 
> > Sylvestre, could you apply the two patches to llvm-toolchain-9 so that
> > we can check if that fixes the julia build on ppc64el?
> 
> If you want me to do anything regarding testing, please let me know, but
> I don't have a ppc64el at home ;-)
> 
> > FWIW, I have already added the removal hint for llvm-toolchain-10, but
> > removal is still blocked by julia:
> 
> Ahh, indeed, because it cannot transition to testing. So we need to do
> one of the two.
> 
> JFYI: we are having a long (3-day) weekend here in Japan and I will be
> mostly offline till Tuesday morning JST.
> 
> Thanks and all the best
> 

When you come back from VAC, I think a fixed llvm-toolchain-9 will wait for you 
to upload julia!

(uploaded some seconds ago)

cheers,

Gianfranco

> Norbert
> 
> --
> PREINING Norbert  https://www.preining.info
> Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
> 
> 

Bug#977814: fixed in llvm-toolchain-11 1:11.0.1-1

[Gianfranco Costamagna]

control: reopen -1

Hello Pino,
llvm-toolchain-11 is now fixed, and clazy should be fixed too.

Unfortunately clazy seems to be missing a "break" relationship against old 
llvm, and britney uses
the broken testing version to test it.

I don't know if we can hint to let it migrate anyway, or we should reupload 
with a fixed break relationship to let
Britney understand that they have to migrate together.

Let me know if you have a solution for this issue, and if we really need the 
break or not.
(I don't know if the old package works only with llvm-* new or its runtime 
retro-compatible)

G.

On Wed, 06 Jan 2021 11:50:25 + Debian FTP Masters 
 wrote:
> Source: llvm-toolchain-11
> Source-Version: 1:11.0.1-1
> Done: Sylvestre Ledru 
> 
> We believe that the bug you reported is fixed in the latest version of
> llvm-toolchain-11, 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 977...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Sylvestre Ledru  (supplier of updated llvm-toolchain-11 
> 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: Wed, 06 Jan 2021 09:21:24 +0100
> Source: llvm-toolchain-11
> Architecture: source
> Version: 1:11.0.1-1
> Distribution: unstable
> Urgency: medium
> Maintainer: LLVM Packaging Team 
> Changed-By: Sylvestre Ledru 
> Closes: 977814
> Changes:
>  llvm-toolchain-11 (1:11.0.1-1) unstable; urgency=medium
>  .
>[ Sylvestre Ledru ]
>* New stable release
>  .
>[ Gianfranco Costamagna ]
>* Drop old patch, upstream now
>* Run dh_makeshlibs with -V parameter (Closes: #977814)
> Checksums-Sha1:
>  eecd206b0409aed5b630bf3eef4ee484fe5be632 5975 llvm-toolchain-11_11.0.1-1.dsc
>  30d7160c402e88747afe83aef5a45e067bffe9ed 78748920 
> llvm-toolchain-11_11.0.1.orig.tar.xz
>  364b66028f7187abd4b220e092ae4d01ede114ef 129488 
> llvm-toolchain-11_11.0.1-1.debian.tar.xz
>  f50de002773ff899d9cdbc5dd003b5225ab814a6 26645 
> llvm-toolchain-11_11.0.1-1_amd64.buildinfo
> Checksums-Sha256:
>  74768bfd5fdf35bc73796a102bce654c7ed157b0cfb4b5da530bac6177a521c1 5975 
> llvm-toolchain-11_11.0.1-1.dsc
>  39ed2924a4bc0e4db79dfdd97f97bca64a26ff398b9128934c3fc7b3186e4c45 78748920 
> llvm-toolchain-11_11.0.1.orig.tar.xz
>  17bc5ad3b58148eb168f4a2f45fbc1c1188d06b163962a687a82d0dc916d3472 129488 
> llvm-toolchain-11_11.0.1-1.debian.tar.xz
>  b9e5c36cf3c00d2ac301d212bebb4be471b996b5f520266c0fbd329818f588dd 26645 
> llvm-toolchain-11_11.0.1-1_amd64.buildinfo
> Files:
>  127e27b0f27865b4d253080eacd31e3b 5975 devel optional 
> llvm-toolchain-11_11.0.1-1.dsc
>  04f17a9ae5a379fbadb56c306f9d959f 78748920 devel optional 
> llvm-toolchain-11_11.0.1.orig.tar.xz
>  513bdcc906ea9bcc9870c902ed88d5ff 129488 devel optional 
> llvm-toolchain-11_11.0.1-1.debian.tar.xz
>  f8bc7db5a0dd5bd974ea1893cd47d6df 26645 devel optional 
> llvm-toolchain-11_11.0.1-1_amd64.buildinfo

Processed: Re: Bug#977814: fixed in llvm-toolchain-11 1:11.0.1-1

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #977814 {Done: Sylvestre Ledru } 
[src:llvm-toolchain-11] llvm-toolchain-11/1:11.0.1~+rc1-1 breaks behaviour with 
1:11.0.0-5
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions llvm-toolchain-11/1:11.0.1-1.

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

Bug#971309: marked as done (ansible: Switch to python3-pycryptodome)

[Debian Bug Tracking System]

Your message dated Fri, 08 Jan 2021 11:33:33 +
with message-id 
and subject line Bug#971309: fixed in ansible 2.9.16+dfsg-1.1
has caused the Debian Bug report #971309,
regarding ansible: Switch to python3-pycryptodome
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.)


-- 
971309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ansible
Version: 2.9.13+dfsg-1
Severity: important
Tags: sid bullseye
Usertags: pycrypto

Dear maintainer,

ansible currently Build-Depends or Depends on python3-crypto from
PyCrypto. This project is no longer maintained and PyCryptodome
(https://www.pycryptodome.org/en/latest/) provides a drop in
replacement. Please switch to python3-pycryptodome. I'd like to
remove python-crypto before the release of bullseye.

Cheers 
--- End Message ---
--- Begin Message ---
Source: ansible
Source-Version: 2.9.16+dfsg-1.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated ansible 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: Wed, 06 Jan 2021 11:56:22 +0100
Source: ansible
Architecture: source
Version: 2.9.16+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Harlan Lieberman-Berg 
Changed-By: Sebastian Ramacher 
Closes: 971309
Changes:
 ansible (2.9.16+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Replace python3-crypto with python3-cryptography (Closes:
 #971309). The cryptography based backend is the default crypto backend.
Checksums-Sha1:
 0f869915ac2961fa272e2de1bfc58b710c7c4b75 2240 ansible_2.9.16+dfsg-1.1.dsc
 c1c03424400e14d8a1d3c15e7955b25ce3ef8f98 26184 
ansible_2.9.16+dfsg-1.1.debian.tar.xz
Checksums-Sha256:
 67b44432d7a033c9950a1635bf5973e12b1a37be8206f8b63e682730ccb8af0a 2240 
ansible_2.9.16+dfsg-1.1.dsc
 17dfaf05e5e077f9097cda732f5f387cd8bda41cb923467598f8b5661116d34d 26184 
ansible_2.9.16+dfsg-1.1.debian.tar.xz
Files:
 1168783059da65a6df12023c8c1dd407 2240 admin optional 
ansible_2.9.16+dfsg-1.1.dsc
 99c0c2b9ea185856ab35e7daa38750f5 26184 admin optional 
ansible_2.9.16+dfsg-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl/1mfUACgkQafL8UW6n
GZOf9BAAl+uiAFMV5LtceV7XW8CK1Mj4eO6rTivl7KzDg393fEZZc443Yp0D4hXs
0kUpHlzJskHTgHh6mlieT5L4wNDpnXJnkoLVOie/mF3JlOqfpGteNz71d7O7N7c2
X48LL8DNh2xcZmq2rDXElm+rLEZLdSUMw2NBmeiU7glKRZzdLzxG2fL/x9ub0A3z
fHKactWmrZCQ3dtIeaG5qhvOsFSSw9h3T5g5wk0dIyJy6oSKCddSEeRrpowpvIAG
YGWY49FOkJn1vi8GL/pRdhD7a4IdLlQIlHIdS9C2J2pwEh92a/wxfKwChHPnsdR5
h6VioDls3AlFcEDH8d4KNlrAFrRNprKcGFBIlibqCj3EagyQ+awE31vGheuxwae3
4hKc9KXLTUg+ynWa7J6//dr85U8QOSFA2hu4bx1UZr2w7JT9Oop6dys8X294713Y
6NGB9kPSx3w3I7IYZ+UP3dKjGl+aFkwTlpM3dOcD9GCzvUKUl4uPBiz5J4TZrVpK
UiAqz9rf8PdzlxOwBPmVd/rm5qNgjWl/GB32V0Ek2ftuHh/phQbGP0RApJeJp4i+
VHIhbOKRhe3WBq2ZKjSCToglYZkmn+ObAFTl6+7NHNCqme2VVqJ7UAscpvXP2Z5F
F8g1rVxdyhujV6C3GGRgDEZ4MN1QQjW3hK2XOKXFW645vY2p/Cs=
=R1ls
-END PGP SIGNATURE End Message ---

Bug#974779: [Pkg-julia-devel] Bug#974779: severity - Julia: Please upgrade to llvm-toolchain-11

[Norbert Preining]

Dear Sebastian,

thanks for your email!

> Sylvestre, could you apply the two patches to llvm-toolchain-9 so that
> we can check if that fixes the julia build on ppc64el?

If you want me to do anything regarding testing, please let me know, but
I don't have a ppc64el at home ;-)

> FWIW, I have already added the removal hint for llvm-toolchain-10, but
> removal is still blocked by julia:

Ahh, indeed, because it cannot transition to testing. So we need to do
one of the two.

JFYI: we are having a long (3-day) weekend here in Japan and I will be
mostly offline till Tuesday morning JST.

Thanks and all the best

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: Re: python-fabio's autopkg tests are failing with python3.9

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.11.0+dfsg-1
Bug #973028 [src:python-fabio] python-fabio's autopkg tests are failing with 
python3.9
Marked as fixed in versions python-fabio/0.11.0+dfsg-1.
> close -1
Bug #973028 [src:python-fabio] python-fabio's autopkg tests are failing with 
python3.9
Marked Bug as done

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

Bug#973028: python-fabio's autopkg tests are failing with python3.9

[Gianfranco Costamagna]

control: fixed -1 0.11.0+dfsg-1
control: close -1

thanks

On Tue, 27 Oct 2020 13:34:47 +0100 Matthias Klose  wrote:
> Package: src:python-fabio
> Version: 0.10.2+dfsg-2
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9
> 
> see
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fabio/7758092/log.gz
> 
> 

Bug#974779: [Pkg-julia-devel] Bug#974779: severity - Julia: Please upgrade to llvm-toolchain-11

[Sebastian Ramacher]

Hi Norbert

On 2021-01-08 12:17:54, Norbert Preining wrote:
> Hi Sebastian,
> 
> coming back to the llvm-9 vs -10 vs -11 issue.
> 
> So, julia fails to build on ppc64el with llvm-9 because llvm-9 has bugs
> there, and we cannot use llvm-11 since this is not supported in the
> current version of julia.
> 
> There are thus the following options:
> - keep llvm-10
> - drop julia on ppc64el
> - fix llvm-9
> 
> The necessary fixes for llvm-9 are described here:
> https://github.com/JuliaLang/julia/pull/35477
> in particular in the two patches that are included in the PR

Sylvestre, could you apply the two patches to llvm-toolchain-9 so that
we can check if that fixes the julia build on ppc64el?

If that doesn't help, we can still look at droping julia from ppc64el.

> * deps/patches/llvm9-D71443-PPC-MC-redef-symbol.patch **
> From 5cd52dbfa9c60cfd12676924bed97701ee9bc4ef Mon Sep 17 00:00:00 2001
> From: Fangrui Song 
> Date: Thu, 12 Dec 2019 16:18:57 -0800
> Subject: [PATCH] [MC][PowerPC] Fix a crash when redefining a symbol after .set
> 
> Fix PR44284. This is probably not valid assembly but we should not crash.
> 
> Reviewed By: luporl, #powerpc, steven.zhang
> 
> Differential Revision: https://reviews.llvm.org/D71443
> 
> (cherry picked from commit f99eedeb72644671cd584f48e4c136d47f6b0020)
> ---
>  llvm/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp | 3 ++-
>  llvm/test/MC/PowerPC/ppc64-localentry-symbols.s  | 5 +
>  2 files changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git llvm/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp 
> llvm/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp
> index 90c3c8d20ed..71f926c265e 100644
> --- llvm/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp
> +++ llvm/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp
> @@ -196,7 +196,8 @@ public:
> 
>void finish() override {
>  for (auto *Sym : UpdateOther)
> -  copyLocalEntry(Sym, Sym->getVariableValue());
> +  if (Sym->isVariable())
> +copyLocalEntry(Sym, Sym->getVariableValue());
>}
> 
>  private:
> diff --git llvm/test/MC/PowerPC/ppc64-localentry-symbols.s 
> llvm/test/MC/PowerPC/ppc64-localentry-symbols.s
> index f1d5c5d0ab1..a663af57ad4 100644
> --- llvm/test/MC/PowerPC/ppc64-localentry-symbols.s
> +++ llvm/test/MC/PowerPC/ppc64-localentry-symbols.s
> @@ -32,3 +32,8 @@ func:
>nop
>nop
>.localentry func, 8
> +
> +## PR44284 Don't crash if err is redefined after .set
> +.set err, _err
> +.globl err
> +err:
> --
> 2.26.0
> **
> 
> 
> 
> 
> *** deps/patches/llvm-9.0-D78196.patch 
> diff --git a/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp 
> b/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp
> --- a/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp
> +++ b/lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp
> @@ -210,6 +210,10 @@
>  for (auto *Sym : UpdateOther)
>if (Sym->isVariable())
>  copyLocalEntry(Sym, Sym->getVariableValue());
> +
> +// Clear the set of symbols that needs to be updated so the streamer can
> +// be reused without issues.
> +UpdateOther.clear();
>}
> 
>  private:
> 
> 
> 
> I cannot guarantee that Julia will build with these fixes applied to the
> LLVM-9 sources, but at least that is what I read out of the above PR.
> 
> In particular looking at the list of other patches applied to LLVM-9:
> ifeq ($(LLVM_VER_SHORT),9.0)
> $(eval $(call LLVM_PATCH,llvm-D27629-AArch64-large_model_6.0.1))
> $(eval $(call LLVM_PATCH,llvm8-D34078-vectorize-fdiv))
> $(eval $(call LLVM_PATCH,llvm-6.0-NVPTX-addrspaces)) # NVPTX -- warning: this 
> fails check-llvm-codegen-nvptx
> $(eval $(call LLVM_PATCH,llvm-7.0-D44650)) # mingw32 build fix
> $(eval $(call LLVM_PATCH,llvm9-D50010-VNCoercion-ni))
> $(eval $(call LLVM_PATCH,llvm8-WASM-addrspaces)) # WebAssembly
> $(eval $(call LLVM_PATCH,llvm-exegesis-mingw)) # mingw build
> $(eval $(call LLVM_PATCH,llvm-test-plugin-mingw)) # mingw build
> $(eval $(call LLVM_PATCH,llvm7-revert-D44485))
> $(eval $(call LLVM_PATCH,llvm-8.0-D66657-codegen-degenerate)) # remove for 
> 10.0
> $(eval $(call LLVM_PATCH,llvm-8.0-D71495-vectorize-freduce)) # remove for 10.0
> $(eval $(call LLVM_PATCH,llvm-D75072-SCEV-add-type))
> $(eval $(call LLVM_PATCH,llvm-9.0-D65174-limit-merge-stores)) # remove for 
> 10.0
> 
> )
> 
> 
> I guess you prefer that we drop julia for ppc64el, which would of course
> be the easiest way. But I still would like to hear your opinion,
> especially since llvm-10-dev is still present as of now, in both testing
> and unstable.

FWIW, I have already added the removal hint for llvm-toolchain-10, but
removal is still blocked by julia:

trying: -llvm-toolchain-10
skipped: -llvm-toolchain-10 (61, 0, 187)
got: 29+0: a-5:a-23:a-0:a-0:i-0:m-0:m-0:p-0:s-1
* amd64: cantor-backend-julia, julia, libjulia-dev, libjulia1

(from https://release.debian.org/britney/update_output.txt)

So once 

Bug#979443: chromium: desktop GUI locks up as Xorg process goes to 100%

[Phil Armstrong]

Additionally, I’ve found that the official releases of Chrome from 
Google suffer from the same problem for me, but that the beta is fine. 
So it looks like it might be fixed upstream in Chrome release 88.


Phil

On Thu, 7 Jan 2021 11:30:25 +0100 Jan Luca Naumann 
 wrote:

Dear Steve,

with the upgrade to 87.* we included the ANGLE library which manages the
OpenGL access of chromium. Maybe this is the cause of your problem.

Could you try to launch "$ chromium --use-gl=desktop"? This should
disable the usage of ANGLE.

Bug#978954: pepperflashplugin-nonfree: should not be part of next stable Debian release

[Gunnar Hjalmarsson]

Right, it should certainly not be included in its current state in next 
release.


But there is more into it. If you for instance try to install Opera from 
stable (or oldstable or testing or unstable...) the .deb recommends 
pepperflashplugin-nonfree, and you may end up to a situation like this:


https://askubuntu.com/q/1305914

So instead of dropping the package, I think the best thing to do is to 
convert it to a dummy transitional package in all supported releases as 
well as testing and unstable.


flashplugin-nonfree was handled by just dropping it:

https://bugs.debian.org/969112

But that has already happened, and so be it.

More talk about this topic at .

--
Cheers,

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