Processed: Link to the upstream bug

[Debian Bug Tracking System]

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

> forwarded 885777 https://sourceforge.net/p/xournal/feature-requests/211/
Bug #885777 [src:xournal] xournal: Depends on libgnomecanvas
Set Bug forwarded-to-address to 
'https://sourceforge.net/p/xournal/feature-requests/211/'.
> thanks
Stopping processing here.

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

Bug#885763: invada-studio-plugins-lv2: Depends on libgnome

[Adrian Bunk]

On Fri, Dec 29, 2017 at 08:20:11PM +0100, Jaromír Mikeš wrote:
>...
> as you see there is ongoing process of removing of old libs in debian.
> ​invada-studio-plugins-lv2 package depends on one of them unfortunately.
>...

Is there actually any reason why the package does depend on libgnome?

No plugin is linked with libgnome (there is also no build dependency),
and all these manual library dependencies look wrong to me 
(${shlibs:Depends} already does the right thing).

In other words, I'd suggest to:

--- invada-studio-plugins-lv2-1.2.0+repack0/debian/control  2016-12-19 
20:44:37.0 +0200
+++ invada-studio-plugins-lv2-1.2.0+repack0/debian/control  2018-01-27 
09:40:48.0 +0200
@@ -18,12 +18,6 @@
 Package: invada-studio-plugins-lv2
 Architecture: any
 Depends:
- libcairo2,
- libglade2-0,
- libglib2.0-0,
- libgnome2-0,
- libgtk2.0-0,
- libxml2,
  ${misc:Depends},
  ${shlibs:Depends}
 Provides:


> best regards
> 
> mira

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#888567: gnome-tweaks: Incomplete debian/copyright?

[Chris Lamb]

Source: gnome-tweaks
Version: 3.27.4-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jeremy Bicha 

Hi!

I just ACCEPTed gnome-tweaks from NEW but noticed it was missing 
attribution in debian/copyright for at least, Cosimo Cecchi,
Canonical, Red Hat, etc. etc. :)

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


Regards,

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

Bug#888302: marked as done (recollgui,recollcmd: missing Breaks+Replaces: recoll (<< 1.23.7-2))

[Debian Bug Tracking System]

Your message dated Sat, 27 Jan 2018 06:05:02 +
with message-id 
and subject line Bug#888302: fixed in recoll 1.23.7-3
has caused the Debian Bug report #888302,
regarding recollgui,recollcmd: missing Breaks+Replaces: recoll (<< 1.23.7-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.)


-- 
888302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: recollgui,recollcmd
Version: 1.23.7-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package recollcmd.
  Preparing to unpack .../8-recollcmd_1.23.7-2_amd64.deb ...
  Unpacking recollcmd (1.23.7-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-k0Z6Ai/8-recollcmd_1.23.7-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/recollindex', which is also in package recoll 
1.23.7-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Selecting previously unselected package recollgui.
  Preparing to unpack .../9-recollgui_1.23.7-2_amd64.deb ...
  Unpacking recollgui (1.23.7-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-k0Z6Ai/9-recollgui_1.23.7-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/recoll', which is also in package recoll 
1.23.7-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-k0Z6Ai/8-recollcmd_1.23.7-2_amd64.deb
   /tmp/apt-dpkg-install-k0Z6Ai/9-recollgui_1.23.7-2_amd64.deb


cheers,

Andreas


recoll=1.23.7-1_recollgui=1.23.7-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: recoll
Source-Version: 1.23.7-3

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated recoll 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, 26 Jan 2018 21:14:45 -0800
Source: recoll
Binary: recoll recollcmd recollgui python-recoll python3-recoll
Architecture: source amd64 all
Version: 1.23.7-3
Distribution: experimental
Urgency: low
Maintainer: Kartik Mistry 
Changed-By: Kartik Mistry 
Description:
 python-recoll - Python extension for recoll
 python3-recoll - Python extension for recoll (Python3)
 recoll - Personal full text search package
 recollcmd  - Command line programs for recoll
 recollgui  - GUI program and elements for recoll
Closes: 888302
Changes:
 recoll (1.23.7-3) experimental; urgency=low
 .
   * debian/control:
 + Fixed version in Breaks and Replaces (Closes: #888302)
Checksums-Sha1:
 515857acddefdf4b35bd924a18c03c209e0dfd8a 2435 recoll_1.23.7-3.dsc
 5aabbbef2e99040f7f9c685ab6637ba0c55f6ee7 2601930 recoll_1.23.7.orig.tar.gz
 f2a7416c85c9b1be7cab8b8f3010a0cff1dc46e8 833 recoll_1.23.7.orig.tar.gz.asc
 0df74a7ae968bf4b78d39e63f9770cd5b281d791 11008 recoll_1.23.7-3.debian.tar.xz
 f35314bdc3c9dd0db2af22421913db6496c5da0c 128856 
python-recoll_1.23.7-3_amd64.deb
 6fc882adae8ddc4b5d7e7c330201e21948d80b9f 129332 
python3-recoll_1.23.7-3_amd64.deb
 527472193052784c24f9219b18bd990d8690da0c 148812 recoll_1.23.7-3_all.deb
 63ef343bb62ec4df425fdb30e69276952cc776ed 12576 recoll_1.23.7-3_amd64.buildinfo
 524b46c7feefe51b8d123788da4053cbcc445dd2 1146464 recollcmd_1.23.7-3_amd64.deb
 7be0eecdd29e2a82466e55fce2986544cc5c9192 722048 recollgui_1.23.7-3_amd64.deb
Checksums-Sha256:
 c684f9f06b945d43d4b74340c73aa868d7f5344c92c60802c3e74a714957e13c 2435 
recoll_1.23.7-3.dsc
 

Processed: found 887952 in 0.0~git20161111.0.293ce0c+dfsg1-5, found 887940 in 3.1.0-1, found 888080 in 0.7.7-1 ...

[Debian Bug Tracking System]

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

> found 887952 0.0~git2016.0.293ce0c+dfsg1-5
Bug #887952 [golang-github-jacobsa-crypto] Revert to Arch:all
There is no source info for the package 'golang-github-jacobsa-crypto' at 
version '0.0~git2016.0.293ce0c+dfsg1-5' with architecture ''
Unable to make a source version for version '0.0~git2016.0.293ce0c+dfsg1-5'
Marked as found in versions 0.0~git2016.0.293ce0c+dfsg1-5.
> found 887940 3.1.0-1
Bug #887940 [src:libpreludedb] libpq-dev: changed version format in pg_config 
causes other packages to FTBFS
Marked as found in versions libpreludedb/3.1.0-1.
> found 888080 0.7.7-1
Bug #888080 [python-cmd2] python-tackerclient FTBFS: AttributeError: 'module' 
object has no attribute 'exceptions'
Marked as found in versions cmd2/0.7.7-1.
> notfound 887765 4.2+dfsg.1-2
Bug #887765 {Done: Ben Finney } [python3-coverage] 
python3-coverage: FTBFS
No longer marked as found in versions python-coverage/4.2+dfsg.1-2.
> tags 887765 + unreproducible
Bug #887765 {Done: Ben Finney } [python3-coverage] 
python3-coverage: FTBFS
Added tag(s) unreproducible.
> tags 886116 + unreproducible
Bug #886116 [src:xppaut] FTBFS: chown: cannot access '.../t.so': No such file 
or directory
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Processed: Re: glances: FTBFS during sphinx-build: The configuration file called sys.exit()

[Debian Bug Tracking System]

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

> tags 887786 + moreinfo unreproducible
Bug #887786 [src:glances] glances: FTBFS during sphinx-build: The configuration 
file called sys.exit()
Added tag(s) unreproducible and moreinfo.
> severity 887786 normal
Bug #887786 [src:glances] glances: FTBFS during sphinx-build: The configuration 
file called sys.exit()
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: affects 888461, found 886816 in 1.7.1+git20171031.f85c78b-4

[Debian Bug Tracking System]

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

> affects 888461 + nvidia-persistenced
Bug #888461 {Done: Andreas Beckmann } [glx-alternative-nvidia] 
nvidia-persistenced: Daemon will not start
Added indication that 888461 affects nvidia-persistenced
> found 886816 1.7.1+git20171031.f85c78b-4
Bug #886816 [golang-go.uber-zap-dev,zap] golang-go.uber-zap-dev,zap: duplicate 
packages
There is no source info for the package 'zap' at version 
'1.7.1+git20171031.f85c78b-4' with architecture ''
Marked as found in versions golang-go.uber-zap/1.7.1+git20171031.f85c78b-4.
> thanks
Stopping processing here.

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

Bug#888058: marked as done (xfce4-power-manager-data,deepin-icon-theme: file conflict on /usr/share/icons/hicolor/scalable/status/display-brightness-symbolic.svg)

[Debian Bug Tracking System]

Your message dated Sat, 27 Jan 2018 04:04:36 +
with message-id 
and subject line Bug#888058: fixed in deepin-icon-theme 15.12.52+git20180126-1
has caused the Debian Bug report #888058,
regarding xfce4-power-manager-data,deepin-icon-theme: file conflict on 
/usr/share/icons/hicolor/scalable/status/display-brightness-symbolic.svg
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.)


-- 
888058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-power-manager-data,deepin-icon-theme
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 15.12.52-1
Control: found -1 1.6.0-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package deepin-icon-theme.
  Preparing to unpack .../deepin-icon-theme_15.12.52-1_all.deb ...
  Unpacking deepin-icon-theme (15.12.52-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/deepin-icon-theme_15.12.52-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/icons/hicolor/scalable/status/display-brightness-symbolic.svg', 
which is also in package xfce4-power-manager-data 1.6.0-1
  Errors were encountered while processing:
   /var/cache/apt/archives/deepin-icon-theme_15.12.52-1_all.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/share/icons/hicolor/scalable/status/display-brightness-symbolic.svg

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


xfce4-power-manager-data=1.6.0-1_deepin-icon-theme=15.12.52-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: deepin-icon-theme
Source-Version: 15.12.52+git20180126-1

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

Debian distribution maintenance software
pp.
Boyuan Yang <073p...@gmail.com> (supplier of updated deepin-icon-theme package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 27 Jan 2018 11:49:11 +0800
Source: deepin-icon-theme
Binary: deepin-icon-theme
Architecture: source
Version: 15.12.52+git20180126-1
Distribution: unstable
Urgency: high
Maintainer: Debian Deepin Packaging Team 

Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 deepin-icon-theme - Icon Theme for Deepin software and Deepin Desktop 
Environment
Closes: 888058
Changes:
 deepin-icon-theme (15.12.52+git20180126-1) unstable; urgency=high
 .
   * New upstream snapshot.
 + Fix file conflict with xfce4-power-manager-data. Closes: #888058
   * Fix package description, remove lintian override.
Checksums-Sha1:
 39ee2c290318a570ef339d27e3d3eb039f5fca0c 2197 
deepin-icon-theme_15.12.52+git20180126-1.dsc
 6c675ee4e91d3e6d963986c3ac9512b2e00898d6 10831885 

Bug#888560: mpfi dependencies inconsistency

[Vincent Lefevre]

Package: src:mpfi
Version: 1.5.3+ds-1
Severity: serious
Justification: Policy 7.2

The current libmpfi-dev version is 1.5.3+ds-1+b1, which has:

Depends: libmpfi0 (= 1.5.3+ds-1+b1), libmpfi-dev-common (= 1.5.3+ds-1), 
libmpfr-dev, libgmp-dev

but libmpfi-dev-common 1.5.3+ds-1 has:

Recommends: libmpfi-dev (= 1.5.3+ds-1)

This is inconsistent.

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

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

libmpfi-dev-common depends on no packages.

Versions of packages libmpfi-dev-common recommends:
ii  libmpfi-dev  1.5.3+ds-1

libmpfi-dev-common suggests no packages.

-- no debconf information

Bug#888558: python-backports.tempfile: ships file with generic name: /usr/lib/python2.7/dist-packages/backports/__init__.py

[Andreas Beckmann]

Package: python-backports.tempfile
Version: 1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other packages files.

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

  Selecting previously unselected package python-backports.tempfile.
  Preparing to unpack .../python-backports.tempfile_1.0-1_all.deb ...
  Unpacking python-backports.tempfile (1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-backports.tempfile_1.0-1_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/python2.7/dist-packages/backports/__init__.py', which is also in 
package python-backports-shutil-get-terminal-size 1.0.0-3
  Errors were encountered while processing:
   /var/cache/apt/archives/python-backports.tempfile_1.0-1_all.deb

I don't think Breaks+Replaces is the correct approach to handle this very
generic file name.


cheers,

Andreas


python-backports-shutil-get-terminal-size=1.0.0-3_python-backports.tempfile=1.0-1.log.gz
Description: application/gzip

Bug#888557: eom-dev,gir1.2-eom-1.0: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/girepository-1.0/Eom-1.0.typelib, /usr/share/gir-1.0/Eom-1.0.gir

[Andreas Beckmann]

Package: eom-dev,gir1.2-eom-1.0
Version: 1.18.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package gir1.2-eom-1.0.
  Preparing to unpack .../42-gir1.2-eom-1.0_1.18.3-2_amd64.deb ...
  Unpacking gir1.2-eom-1.0 (1.18.3-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-CQq0kj/42-gir1.2-eom-1.0_1.18.3-2_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/girepository-1.0/Eom-1.0.typelib', which is also in 
package gir1.2-eom 1.18.3-1
  Selecting previously unselected package eom-dev.
  Preparing to unpack .../43-eom-dev_1.18.3-2_amd64.deb ...
  Unpacking eom-dev (1.18.3-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-CQq0kj/43-eom-dev_1.18.3-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/gir-1.0/Eom-1.0.gir', which is also in 
package gir1.2-eom 1.18.3-1


cheers,

Andreas


gir1.2-eom=1.18.3-1_eom-dev=1.18.3-2.log.gz
Description: application/gzip

Bug#888556: libetsf-io-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libetsf-io-dev/AUTHORS

[Andreas Beckmann]

Package: libetsf-io-doc
Version: 1.0.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libetsf-io-doc.
  Preparing to unpack .../libetsf-io-doc_1.0.4-2_all.deb ...
  Unpacking libetsf-io-doc (1.0.4-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libetsf-io-doc_1.0.4-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libetsf-io-dev/AUTHORS', which is also 
in package libetsf-io-dev 1.0.4-1.1+b3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libetsf-io-doc_1.0.4-2_all.deb

This is probably caused by a dh_installdocs behavior change in
debhelper compat level 11.


cheers,

Andreas


libetsf-io-dev=1.0.4-1.1+b3_libetsf-io-doc=1.0.4-2.log.gz
Description: application/gzip

Bug#888484: clamav: Security release 0.99.3 available

[Bernhard Schmidt]

Control: unfixed 888484 0.99.3~beta2+dfsg-1
Control: fixed 888511 0.99.3~beta2+dfsg-1

Hi 

>> 
>> We've have started seeing unexpected clamd crashes on a high-traffic mail
>> system today, though I've been unable to isolate a test case. It's seems like
>> too much of a coincidence that these crashes start happening the day after a
>> security release was announced. We've implemented mitigations but an updated
>> package would be even better.
> 
> I *think* the crashes you obsereved might be due to FD desc issue. This
> was fixed in Stretch by chance but not in Jessie. However the remaining
> CVEs were not addressed yet and I'm looking into it…
> 
> [0] 
> http://blog.clamav.net/2018/01/update-on-recent-file-descriptors-issue.html

Indeed. There is a separate Bug#888511 for that, I have migrated the fixed 
Version above to avoid confusion.

Are you sure about the Stretch thing? Stretch contains 0.99.2 which should be 
affected by this bug. But I’m not 100% sure, as all my high traffic mail 
gateways are still running Jessie.

According to reports 0.99.3~beta2 was indeed not affected by the signature bug, 
so Buster/Sid where fine. What makes things even more confusing is that 0.99.3 
does not contain this fix, because 0.99.3 is 0.99.2+security fixes, while 
0.99.3~beta was a development tree that is now called 0.100 :-(

http://blog.clamav.net/2018/01/clamav-version-number-adjustment.html

Upstream announcement suggests you cannot do a clean switch from 0.99.3~beta to 
0.99.3

As previously mentioned, if you downloaded the beta version of ClamAV 0.99.3, 
you will need to completely uninstall it and do a fresh install with the 
production version of 0.99.3 as there are significant code differences


Bernhard

Bug#888555: clang-tools: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/clang-apply-replacements.1.gz

[Andreas Beckmann]

Package: clang-tools
Version: 1:5.0-41~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package clang-tools.
  Preparing to unpack .../clang-tools_1%3a5.0-41~exp2_amd64.deb ...
  Unpacking clang-tools (1:5.0-41~exp2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/clang-tools_1%3a5.0-41~exp2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/clang-apply-replacements.1.gz', 
which is also in package clang 1:4.0-40
  Errors were encountered while processing:
   /var/cache/apt/archives/clang-tools_1%3a5.0-41~exp2_amd64.deb

Full list of conflicting files:

usr/share/man/man1/clang-apply-replacements.1.gz
usr/share/man/man1/clang-check.1.gz
usr/share/man/man1/clang-query.1.gz
usr/share/man/man1/sancov.1.gz
usr/share/man/man1/scan-build.1.gz
usr/share/man/man1/scan-view.1.gz


cheers,

Andreas


clang=1%4.0-40_clang-tools=1%5.0-41~exp2.log.gz
Description: application/gzip

Bug#888484: clamav: Security release 0.99.3 available

[Rob N ★]

On Sat, Jan 27, 2018, at 11:08 AM, Sebastian Andrzej Siewior wrote:
> I **think** the crashes you obsereved might be due to FD desc
> issue. This> was fixed in Stretch by chance but not in Jessie. However the
> remaining> CVEs were not addressed yet and I'm looking into it…

Yes, I found this too after reviewing discussion on clamav-users. I've
been running the latest daily.cvd on a test server this morning without
issue, which is a good enough solution for me at the moment.
I will of course be watching for updated packages, but it's definitiely
no long urgent.
Thanks you all for the pointers; I appreciate the assist :)

Rob N.

Bug#888551: salt FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 828: ordinal not in range(128)

[Adrian Bunk]

Source: salt
Version: 2017.7.2+dfsg1-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=salt=all=2017.7.2%2Bdfsg1-1=1516915304=0

...
==
ERROR: test_list_products (unit.modules.test_zypper.ZypperTestCase)
[CPU:0.0%|MEM:23.2%] 
--
Traceback (most recent call last):
  File "/<>/salt-2017.7.2+dfsg1/tests/unit/modules/test_zypper.py", 
line 236, in test_list_products
'stdout': get_test_data(filename)
  File "/<>/salt-2017.7.2+dfsg1/tests/unit/modules/test_zypper.py", 
line 53, in get_test_data
return rfh.read()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 828: 
ordinal not in range(128)

==
ERROR: test_non_ascii (unit.templates.test_jinja.TestGetTemplate)
[CPU:0.0%|MEM:23.2%] 
--
Traceback (most recent call last):
  File "/<>/salt-2017.7.2+dfsg1/tests/unit/templates/test_jinja.py", 
line 341, in test_non_ascii
result = fp.read()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 5: ordinal 
not in range(128)

==
ERROR: test_non_ascii_encoding (unit.templates.test_jinja.TestGetTemplate)
[CPU:0.0%|MEM:23.2%] 
--
Traceback (most recent call last):
  File "/<>/salt-2017.7.2+dfsg1/tests/unit/templates/test_jinja.py", 
line 303, in test_non_ascii_encoding
fp_.read(),
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 5: ordinal 
not in range(128)

--
Ran 5870 tests in 702.684s

FAILED (errors=3, skipped=1503, expected failures=2)
debian/rules:18: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#888302: recollgui,recollcmd: missing Breaks+Replaces: recoll (<< 1.23.7-2)

[Andreas Beckmann]

On 2018-01-27 00:33, Kartik Mistry wrote:
> hmm. Wondering why this is happening. Both package mentions Breaks +
> Replaces in debian/control.
> 
> Package: recollcmd
> Breaks: recoll (<< 1.23.7-1)
> Replaces: recoll (<< 1.23.7-1)

Which is the wrong version, since the split happened in -2, see Subject.


Andreas

Bug#853369: marked as done (dbus-c++: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 27 Jan 2018 00:49:43 +
with message-id 
and subject line Bug#853369: fixed in dbus-c++ 0.9.0-8.1
has caused the Debian Bug report #853369,
regarding dbus-c++: ftbfs with GCC-7
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.)


-- 
853369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dbus-c++
Version: 0.9.0-8
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/dbus-c++_0.9.0-8_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 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-7/porting_to.html

[...]
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..  
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/efl-1 -I/usr/include/ecore-1 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/efl-1 
-I/usr/include/eo-1 -I/usr/include/efl-1 -I/usr/include/eina-1 
-I/usr/include/eina-1/eina -Wdate-time -D_FORTIFY_SOURCE=2 -I../include 
-Wno-unused-parameter -g -O2 
-fdebug-prefix-map=/build/dbus-c++-7nmvU2/dbus-c++-0.9.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-c -o libdbus_c___1_la-message.lo `test -f 'message.cpp' || echo 
'./'`message.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/efl-1 
-I/usr/include/ecore-1 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/efl-1 
-I/usr/include/eo-1 -I/usr/include/efl-1 -I/usr/include/eina-1 
-I/usr/include/eina-1/eina -Wdate-time -D_FORTIFY_SOURCE=2 -I../include 
-Wno-unused-parameter -g -O2 
-fdebug-prefix-map=/build/dbus-c++-7nmvU2/dbus-c++-0.9.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-c message.cpp  -fPIC -DPIC -o .libs/libdbus_c___1_la-message.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/efl-1 
-I/usr/include/ecore-1 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/efl-1 
-I/usr/include/eo-1 -I/usr/include/efl-1 -I/usr/include/eina-1 
-I/usr/include/eina-1/eina -Wdate-time -D_FORTIFY_SOURCE=2 -I../include 
-Wno-unused-parameter -g -O2 
-fdebug-prefix-map=/build/dbus-c++-7nmvU2/dbus-c++-0.9.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-c message.cpp -o libdbus_c___1_la-message.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I..  
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/efl-1 -I/usr/include/ecore-1 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/efl-1 
-I/usr/include/eo-1 -I/usr/include/efl-1 -I/usr/include/eina-1 
-I/usr/include/eina-1/eina -Wdate-time -D_FORTIFY_SOURCE=2 -I../include 
-Wno-unused-parameter -g -O2 
-fdebug-prefix-map=/build/dbus-c++-7nmvU2/dbus-c++-0.9.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-c -o libdbus_c___1_la-object.lo `test -f 

Processed: Pending fixes for bugs in the gocryptfs package

[Debian Bug Tracking System]

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

> tag 864809 + pending
Bug #864809 {Done: Felix Lechner } [src:gocryptfs] 
gocryptfs: FTBFS: "does not implement nodefs.File (missing Flock method)"
Added tag(s) pending.
> tag 868070 + pending
Bug #868070 {Done: Felix Lechner } [gocryptfs] 
gocryptfs: '--version' option is useless, containing only 'gocryptfs'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#864809: Pending fixes for bugs in the gocryptfs package

[pkg-go-maintainers]

tag 864809 + pending
tag 868070 + pending
thanks

Some bugs in the gocryptfs package are closed in revision
af0f436694f9a17bcfddb9a1ad60c8a8372f12a8 in branch 'debian' by Felix
Lechner

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/gocryptfs.git/commit/?id=af0f436

Commit message:

Created new changelog entry for Debian revision 2
Imported upstream commits fixing FTBS on i386 (dirent size)
Built with new version of go-fuse (Closes: #864809)
Passed upstream version, go-fuse version and timestamp to build process 
(Closes: #868070)
Built with tag 'without_openssl'
Marked changelog for release

Bug#888484: clamav: Security release 0.99.3 available

[Sebastian Andrzej Siewior]

control: fixed -1  0.99.3~beta2+dfsg-1

On 2018-01-26 09:35:25 [+], Rob N wrote:
> Package: clamav
> Version: 0.99.2+dfsg-0+deb8u2
> Severity: important
> 
> 0.99.3 has been released, see 
> http://blog.clamav.net/2018/01/clamav-0993-has-been-released.html.
> 
> This fixed a number of overflow bugs, each of which has assigned CVE numbers
> due to the potential for denial of service.
> 
> We've have started seeing unexpected clamd crashes on a high-traffic mail
> system today, though I've been unable to isolate a test case. It's seems like
> too much of a coincidence that these crashes start happening the day after a
> security release was announced. We've implemented mitigations but an updated
> package would be even better.

I *think* the crashes you obsereved might be due to FD desc issue. This
was fixed in Stretch by chance but not in Jessie. However the remaining
CVEs were not addressed yet and I'm looking into it…

[0] http://blog.clamav.net/2018/01/update-on-recent-file-descriptors-issue.html

> Cheers!
> Rob N.

Sebastian

Processed: Re: Bug#888484: clamav: Security release 0.99.3 available

[Debian Bug Tracking System]

Processing control commands:

> fixed -1  0.99.3~beta2+dfsg-1
Bug #888484 [clamav] clamav: Security release 0.99.3 available (CVE-2017-12374 
CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 
CVE-2017-12380)
Marked as fixed in versions clamav/0.99.3~beta2+dfsg-1.

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

Bug#888550: glm has some silly GCC version checks, removed upstream

[Matthias Klose]

Package: src:glm
Version: 0.9.8.4-1.1
Severity: serious
Tags: sid buster patch

glm has some silly GCC version checks, removed upstream

see https://launchpad.net/bugs/1745685

patch at
http://launchpadlibrarian.net/354819354/glm_0.9.8.4-1.1_0.9.8.4-1.1ubuntu1.diff.gz

Bug#888302: recollgui,recollcmd: missing Breaks+Replaces: recoll (<< 1.23.7-2)

[Kartik Mistry]

On Wed, Jan 24, 2018 at 11:45 AM, Andreas Beckmann  wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'experimental'.
> It installed fine in 'sid', then the upgrade to 'experimental' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
>
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

hmm. Wondering why this is happening. Both package mentions Breaks +
Replaces in debian/control.

Package: recollcmd
Breaks: recoll (<< 1.23.7-1)
Replaces: recoll (<< 1.23.7-1)

and,

Package: recollgui
Breaks: recoll (<< 1.23.7-1)
Replaces: recoll (<< 1.23.7-1)

-- 
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com

Processed: tag gcc-3.3 issue

[Debian Bug Tracking System]

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

> tags 887782 + sid buster
Bug #887782 [src:gcc-3.3] gcc-3.3 FTBFS: unwind-dw2.c:954: error: dereferencing 
pointer to incomplete type
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#851093: marked as done (bip: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Fri, 26 Jan 2018 23:19:34 +
with message-id 
and subject line Bug#851093: fixed in bip 0.8.9-1.2
has caused the Debian Bug report #851093,
regarding bip: Please migrate to openssl1.1 in buster
to be marked as done.

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

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


-- 
851093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bip
Version: 0.8.9-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/bip_0.8.9-1_amd64-20160529-1407

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: bip
Source-Version: 0.8.9-1.2

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

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated bip 
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: Mon, 22 Jan 2018 23:28:55 +0100
Source: bip
Binary: bip bip-dbg
Architecture: source
Version: 0.8.9-1.2
Distribution: unstable
Urgency: medium
Maintainer: Pierre-Louis Bonicoli 
Changed-By: Sebastian Andrzej Siewior 
Description:
 bip- multiuser irc proxy with conversation replay and more
 bip-dbg- multiuser irc proxy with conversation replay and more (debugging
Closes: 851093 876953
Changes:
 bip (0.8.9-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Cherry-pick a few patches from upstream in order to get it built against
 OpenSSL 1.1 (Closes: #851093).
   * Remove Arnaud Cornet  from Uploaders. Thank you for
 all your work (Closes: #876953).
Checksums-Sha1:
 21ca38b966f0e92b772069b164c924036e4455ad 1972 bip_0.8.9-1.2.dsc
 0409672a8557d46cdec3f5fd6851a77782eb649a 11688 bip_0.8.9-1.2.debian.tar.xz
 f18b04e9fbc2a612796d407380f43f2620fc3bef 5786 bip_0.8.9-1.2_source.buildinfo
Checksums-Sha256:
 03afbb693c19a7f45341337b1e03105d97a6a3c8e0a8ce1e72ea0e361b7b5531 1972 
bip_0.8.9-1.2.dsc
 fe080b017f059fa84c87334f9388c01bdfa7c5fc5065defcb6648466be9fac05 11688 
bip_0.8.9-1.2.debian.tar.xz
 663f14f22b1890879c27e175f13ce847b64c5c44cd78cc1d3987a746b522f222 5786 
bip_0.8.9-1.2_source.buildinfo
Files:
 f17e75a233a5443b1b42d999c7fd68c1 1972 net optional bip_0.8.9-1.2.dsc
 615d51dcd56d08235ff085e4362bc25d 11688 net optional bip_0.8.9-1.2.debian.tar.xz
 db94535ad466532375b9b42ec1fa2176 5786 net optional 
bip_0.8.9-1.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErHvQgQWZUb1RregAT+XjJihy5MwFAlpmaZYACgkQT+XjJihy
5MwSjhAAkzw/6iFWQwNBE4lYFzPl1vvsz8ZjkCExPmxlPMEZhQobHd+mb6A1rlUK
qEUuHp1DM6oUbfv7Vbh5cc1oIrBHmXOQbTXhqwixTsxLTSV8+QELIeMgAuWgy6BQ
AkqvUuqAUMV4I6qJ91Icd3FetYdWU/vqHq33UNv/4cSbxpr69YZx5i7pnNoMZ901
UrOBjtd0eoC6XRDN4lVLHPqTD/3y647VyruxLRNjMKtETWN/s12mjI4QdG5bHBtV
4yxZffIp/5fjHcLiOQEWuSVXD4V25Kc2BGuwlqwIVmcrjPylpC55qGKk3IavfRE2
TDYnOaEyvkZPpYOqCRu/6rucQ5R/8gsXqLbWDf7FTW35vebtyE9yJteO4S6IVR53
oqZyEjWfNpO5f4BOBj6lBVZ+rXh9CO8Be8xm7DhyBegeoLvYJhuqqn+wXl1e/Pdp
Cgn7nyqtX5MKBYuK1tOw51+k+A9HdDS4OP9BTpd6KJ0M8ZKRKup4Hp+lpL5+Opa/
iXHmprO2SIV57Opl9ohnT33zD67aQpLbBJ46l0xj9TrRoUkgk5gbSAVNYcWqpgjL
6NtwHQDdmQNpEltsjHdCHC38dlQk5DtHXfL/vcaLqCjh86VW6hcY+J/9bI81bLH5
+t7m6sbRPtbQlhrtPd6JHBDwhVkEqnzKITAczv8AUQiKa3KK2Sg=
=wYWy
-END PGP SIGNATURE End Message ---

Bug#876592: gconf FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available

[John Paul Adrian Glaubitz]

Package: src:gconf
Followup-For: Bug #876592

Hi!

Since gconf is dead upstream, I don't think that someone will convert
the documentation format away from gtk-doc. I therefore just suggest
to turn off gtk-doc support for the time being until gconf can be
removed from the archives.

Attaching a suggested patch.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
diff -Nru old/gconf-3.2.6/debian/control.in new/gconf-3.2.6/debian/control.in
--- old/gconf-3.2.6/debian/control.in   2016-10-11 16:56:10.0 +0200
+++ new/gconf-3.2.6/debian/control.in   2018-01-26 23:37:45.854551064 +0100
@@ -7,7 +7,6 @@
cdbs (>= 0.4.93),
dh-autoreconf,
gnome-pkg-tools (>= 0.14),
-   gtk-doc-tools (>= 1.0),
libglib2.0-dev (>= 2.31.0),
libdbus-1-dev (>= 1.0.0),
libdbus-glib-1-dev (>= 0.74),
diff -Nru old/gconf-3.2.6/debian/rules new/gconf-3.2.6/debian/rules
--- old/gconf-3.2.6/debian/rules2016-10-11 16:56:08.0 +0200
+++ new/gconf-3.2.6/debian/rules2018-01-26 23:38:03.939217937 +0100
@@ -21,7 +21,7 @@
 
 DEB_INSTALL_DOCS_gconf2 += doc/FAQ.txt NEWS README TODO
 
-DEB_CONFIGURE_EXTRA_FLAGS += --enable-gtk-doc \
+DEB_CONFIGURE_EXTRA_FLAGS += --disable-gtk-doc \
  --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
  --libexecdir=\$${libdir}/gconf \
  --with-gtk=3.0 \

Bug#864809: marked as done (gocryptfs: FTBFS: "does not implement nodefs.File (missing Flock method)")

[Debian Bug Tracking System]

Your message dated Fri, 26 Jan 2018 22:19:29 +
with message-id 
and subject line Bug#864809: fixed in gocryptfs 1.4.2-2
has caused the Debian Bug report #864809,
regarding gocryptfs: FTBFS: "does not implement nodefs.File (missing Flock 
method)"
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.)


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

This arm64 build log shows the error:

https://buildd.debian.org/status/fetch.php?pkg=gocryptfs=arm64=1.2.1-1=1497480941=0

The same error also happens on amd64 with the latest
golang-github-hanwen-go-fuse-dev from unstable,
0.0~git20170609.0.5690be4-1.

There seems to be a new upstream version of gocryptfs in any case...
--- End Message ---
--- Begin Message ---
Source: gocryptfs
Source-Version: 1.4.2-2

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

Debian distribution maintenance software
pp.
Felix Lechner  (supplier of updated gocryptfs 
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, 26 Jan 2018 14:02:27 -0800
Source: gocryptfs
Binary: gocryptfs
Architecture: source
Version: 1.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Felix Lechner 
Description:
 gocryptfs  - Encrypted overlay filesystem written in Go
Closes: 864809 868070
Changes:
 gocryptfs (1.4.2-2) unstable; urgency=medium
 .
   * Imported upstream commits fixing FTBS on i386 (dirent size)
   * Built with new version of go-fuse (Closes: #864809)
   * Passed upstream version, go-fuse version and timestamp to
 build process (Closes: #868070)
   * Built with tag 'without_openssl'
Checksums-Sha1:
 3b18cf284f99f41868e70d0239937c702d5b722b 2795 gocryptfs_1.4.2-2.dsc
 d557407a79f3c2e5a9e962ab15dfc803e3546141 9468 gocryptfs_1.4.2-2.debian.tar.xz
 73723d30efbbb22a8731ba59ac5c072fe0108988 6843 
gocryptfs_1.4.2-2_source.buildinfo
Checksums-Sha256:
 aa02bbbab77b5484bb5bc703552fca8c76d758cd0d631ca3a0ccf587143e5124 2795 
gocryptfs_1.4.2-2.dsc
 e2be8f85a320111f778f5286ee67aa0cfd798e0f093867d63f1b28af42d74034 9468 
gocryptfs_1.4.2-2.debian.tar.xz
 e7cf1d8fa17b5e265e2ddc6b9e8a1480bc7ca7b92fc609042d44e1b9a1004e48 6843 
gocryptfs_1.4.2-2_source.buildinfo
Files:
 71a8a92a18731cd22a9556af68b64ea3 2795 devel optional gocryptfs_1.4.2-2.dsc
 a432f9022ccf6cd5c344be86513ad5ea 9468 devel optional 
gocryptfs_1.4.2-2.debian.tar.xz
 b02cf7628fa6fa17e0092c742ab76d7d 6843 devel optional 
gocryptfs_1.4.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKvBAEBCgCZFiEE8E0cIgLi+g0BiFTarFipTxFhjuAFAlprpcNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYw
NEQxQzIyMDJFMkZBMEQwMTg4NTREQUFDNThBOTRGMTE2MThFRTAbHGZlbGl4Lmxl
Y2huZXJAbGVhc2UtdXAuY29tAAoJEKxYqU8RYY7gHQEQAJhZ4U6HgYaAl3aydUn8
6ZGNPIPU7KnUxn4VjiH+Dyx/VtfFL73+XvNtisBwRX3ENVHvTi90RDkaobsXNUJs
iHEF+f6m1VGs2jHuAVhK41JtircCWdn3QuQn1Gt1t6z3PeFxUFjPbeeZwYABUirD
CNqpNsIKnYU9tsj2kKa119CJP5O458L/sNgAfGr+P91K+dM54jyb17Miaye0psS0
pvwK3K2Go6YPdq0Ja/cpoyioHeJEs0Ce1KZ43EVzsJjW2pBtTDbu2qvHt+bhIhcW
JcgsZy84f+3+0ZEsS1YwIO0kDa79uFx8lsgE+kaAbBQdOmy164rgOFqEacniRLZp
JtXRoOV5/XSSfW5PJZWDSMWI4rjUJTR/p8iKGnikOaA8kqNT5KlQGXwRVs7tdhHF
utnkLHIEyTc53g7yQCqFkKvOFiBjt3e7kH8wKgJrMd4UDIBKXIbL1rQO1xR+Uo81
LpfelIDRxT9pRzKzAcb7UsfBrl2MzakURlV/R12Tq6+nPwPui3soWLdxBhv5cjZ4
q4kb0YMftduIiGOf8HTawEdNI8HeQUHuapTycHHqunXFFuzq4P3LDeYfWxxuPwLv
7AYTK2e7MpYPcyBmrk4Qjhz4XapSXJoDxXTC8BdCuPEyDWyWMcgTQjB+HCWcHlAI
6OldRCvkXKLJoNxF0SJQowmK
=gCZp
-END PGP SIGNATURE End Message ---

Bug#888423: firefox: FF 58.0 segfaults each 1-2 minute

[Dmitry E. Oboukhov]

>> Package: firefox
>> Version: 58.0-1
>> Severity: grave
>> 
>> I used FF58b4, it works fine.
>> Then I upgraded it to FF58b14, it crashed from time to time.
>> 
>> Today I upgraded FF to 58.0, it crashes each 1 minute (see backtrace)
>> (see below).
>> 
>> I can't find `firefox-dbg` package, so the backtrace doesn't contain symbols.

> You can add
> deb http://deb.debian.org/debian-debug unstable-debug main
> to your sources.list and install the firefox-dbgsym package.


Thanks!

The full backtrace here:

(gdb) bt
#0  mozilla::ipc::MessageChannel::OnChannelErrorFromLink (this=0x7f2f2aee6128)
at /build/firefox-WvkEP5/firefox-58.0/ipc/glue/MessageChannel.cpp:2543
#1  0x7f2f1cd7954f in mozilla::ipc::ProcessLink::OnChannelError 
(this=0x7f2f15369df0)
at /build/firefox-WvkEP5/firefox-58.0/ipc/glue/MessageLink.cpp:397
#2  0x7f2f1a4e99ba in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#3  0x7f2f1a4ea537 in event_base_loop () from 
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#4  0x7f2f1cd5074e in base::MessagePumpLibevent::Run (this=0x7f2f2ae53e00, 
delegate=0x7f2f191c0d20)
at 
/build/firefox-WvkEP5/firefox-58.0/ipc/chromium/src/base/message_pump_libevent.cc:381
#5  0x7f2f1cd53000 in MessageLoop::RunInternal (this=0x7f2f191c0d20)
at 
/build/firefox-WvkEP5/firefox-58.0/ipc/chromium/src/base/message_loop.cc:326
#6  MessageLoop::RunHandler (this=0x7f2f191c0d20)
at 
/build/firefox-WvkEP5/firefox-58.0/ipc/chromium/src/base/message_loop.cc:319
#7  MessageLoop::Run (this=this@entry=0x7f2f191c0d20)
at 
/build/firefox-WvkEP5/firefox-58.0/ipc/chromium/src/base/message_loop.cc:299
#8  0x7f2f1cd5fa19 in base::Thread::ThreadMain (this=0x7f2f2ae2b528)
at /build/firefox-WvkEP5/firefox-58.0/ipc/chromium/src/base/thread.cc:181
#9  0x7f2f1cd5029a in ThreadFunc (closure=)
at 
/build/firefox-WvkEP5/firefox-58.0/ipc/chromium/src/base/platform_thread_posix.cc:38
#10 0x7f2f2c0bc494 in start_thread (arg=0x7f2f191c1700) at 
pthread_create.c:333
#11 0x7f2f2b661aff in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97


-- 

. ''`.Dmitry E. Oboukhov 
: :’  :
`. `~’   GPG key: 4096R/08EEA756 2014-08-30
  `- 71ED ACFC 6801 0DD9 1AD1  9B86 8D1F 969A 08EE A756


signature.asc
Description: PGP signature

Bug#888297: p7zip: CVE-2017-17969: ZIP Shrink: Heap Buffer Overflow

[Antoine Beaupre]

Control: tags -1 +patch

Since a fix was published in upstream 18.00-beta, I looked at the source
there and was able to produce a simple patch for wheezy, which should be
trivial to port to jessie and easy to port to stretch:

https://sourceforge.net/p/p7zip/bugs/_discuss/thread/0920f369/c296/attachment/CVE-2017-17969.patch

Attached as well.

Looks good?

A.
Subject: backport of the CVE-2017-17969 fix from 7zip 18.00-beta
Forwarded: https://sourceforge.net/p/p7zip/bugs/204/
Bug-Debian: http://bugs.debian.org/888297
Author: Antoine Beaupré 
Applied-Upstream: 18.00-beta
Last-Update: 2018-01-26

--- p7zip-9.20.1~dfsg.1/CPP/7zip/Compress/ShrinkDecoder.cpp.orig	2011-04-01 15:14:01.0 -0400
+++ p7zip-9.20.1~dfsg.1/CPP/7zip/Compress/ShrinkDecoder.cpp	2018-01-26 16:00:19.944166092 -0500
@@ -99,7 +99,13 @@
 corectionIndex = i;
   _stack[i++] = _suffixes[cur];
   cur = _parents[cur];
+  if (cur == kEmpty || i >= kNumItems)
+break;
 }
+
+if (cur == kEmpty || i >= kNumItems)
+  break;
+
 _stack[i++] = (Byte)cur;
 if (needPrev)
 {


signature.asc
Description: PGP signature

Processed: Re: p7zip: CVE-2017-17969: ZIP Shrink: Heap Buffer Overflow

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #888297 [p7zip] p7zip: CVE-2017-17969: ZIP Shrink: Heap Buffer Overflow
Added tag(s) patch.

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

Bug#885670: kino: diff for NMU version 1.3.4-2.4

[Adrian Bunk]

Control: tags 885670 + pending

Dear maintainer,

I've prepared an NMU for kino (versioned as 1.3.4-2.4) and uploaded it 
to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

diff -u kino-1.3.4/debian/changelog kino-1.3.4/debian/changelog
--- kino-1.3.4/debian/changelog
+++ kino-1.3.4/debian/changelog
@@ -1,3 +1,11 @@
+kino (1.3.4-2.4) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove the unused libgnome2-dev and libgnomeui-dev
+build dependencies. (Closes: #885670)
+
+ -- Adrian Bunk   Fri, 26 Jan 2018 22:58:22 +0200
+
 kino (1.3.4-2.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u kino-1.3.4/debian/control kino-1.3.4/debian/control
--- kino-1.3.4/debian/control
+++ kino-1.3.4/debian/control
@@ -15,9 +15,7 @@
libdv4-dev,
libv4l-dev,
libavc1394-dev (>= 0.4.1),
-   libgnome2-dev,
libglade2-dev,
-   libgnomeui-dev,
libx11-dev,
libxt-dev,
libxv-dev,

Processed: kino: diff for NMU version 1.3.4-2.4

[Debian Bug Tracking System]

Processing control commands:

> tags 885670 + pending
Bug #885670 [src:kino] kino: Don't Build-Depend on libgnome
Added tag(s) pending.

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

Bug#804272: fails to synchronize caldav to OpenXChange without notice

[Martin Steigerwald]

Control: tags -1 upstream
Control: severity -1 important
kthxbye

Hello Thomas, hello Enrico, hello Petter.

I am sorry that you received no response to this bug report earlier.

I am downgrading the bug to important as its not a policy violation and also 
the package is not unsuitable for everyone.

Of course some time has passed and current Debian Stable aka Stretch has the 
updated Akonadi version 16.04.3. Could you reproduce this issue with this 
version or a newer one?

If so, I kindly ask you to report the bug upstream if not already done. We 
greatly appreciate your help.

Please report it via Help -> Report bug... menu item of the respective 
application or by visiting https://bugs.kde.org/ and following instructions
to report a new bug.

Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs and therefore it is unlikely that
your bug will be solved if you do not report it to KDE developers
directly (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one on the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded {debbug} KDE-BUG-URL
thanks
[ copy this ]

Thanks,
-- 
Martin

Processed: Re: fails to synchronize caldav to OpenXChange without notice

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #804272 [akonadi-server] fails to synchronize caldav to OpenXChange without 
notice
Ignoring request to alter tags of bug #804272 to the same tags previously set
> severity -1 important
Bug #804272 [akonadi-server] fails to synchronize caldav to OpenXChange without 
notice
Severity set to 'important' from 'serious'

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

Bug#888513: huge graphical bug

[Cyril Brulebois]

Control: found -1 20170615+deb9u2
Control: severity -1 important

Hi melissa,

and thanks for your report.

melissa M.  (2018-01-26):
> Package: debian-installer
> Version: stable
> Severity: grave

I'm adjusting version and severity with the commands above. While this
is a grave issue for you, that only affects one particular equipment and
doesn't make d-i unusable for everyone else.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#888513: huge graphical bug

[Debian Bug Tracking System]

Processing control commands:

> found -1 20170615+deb9u2
Bug #888513 [debian-installer] huge graphical bug
Marked as found in versions debian-installer/20170615+deb9u2.
> severity -1 important
Bug #888513 [debian-installer] huge graphical bug
Severity set to 'important' from 'grave'

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

Bug#887316: marked as done (haskell-tldr FTBFS on arm64/armel/mips*/s390x: tldr: unknown RTS option: -N)

[Debian Bug Tracking System]

Your message dated Fri, 26 Jan 2018 18:35:12 +
with message-id 
and subject line Bug#887316: fixed in haskell-tldr 0.2.3-3
has caused the Debian Bug report #887316,
regarding haskell-tldr FTBFS on arm64/armel/mips*/s390x: tldr: unknown RTS 
option: -N
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.)


-- 
887316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-tldr
Version: 0.2.3-2
Severity: serious

https://buildd.debian.org/status/package.php?p=haskell-tldr=sid

...
Running dh_haskell_provides -plibghc-tldr-prof
Running dh_haskell_depends -plibghc-tldr-prof
dh_haskell_blurbs "ghc" -plibghc-tldr-prof
Adding cdbs dependencies to debian/tldr.substvars
dh_installdirs -ptldr \

dh_haskell_blurbs "ghc" -ptldr
./dist-ghc/build/tldr/tldr --help
tldr: unknown RTS option: -N
tldr: 
tldr: Usage:   [+RTS  | -RTS ] ... --RTS 
tldr: 
tldr:+RTSIndicates run time system options follow
tldr:-RTSIndicates program arguments follow
tldr:   --RTSIndicates that ALL subsequent arguments will be given to the
tldr:program (including any of these RTS flags)
tldr: 
tldr: The following run time system options are available:
tldr: 
tldr:   -?   Prints this message and exits; the program is not executed
tldr:   --info   Print information about the RTS used by this program
tldr: 
tldr:   -K  Sets the maximum stack size (default: 80% of the heap)
tldr: Egs: -K32k -K512k -K8M
tldr:   -ki Sets the initial thread stack size (default 1k)  Egs: -ki4k 
-ki2m
tldr:   -kc Sets the stack chunk size (default 32k)
tldr:   -kb Sets the stack chunk buffer size (default 1k)
tldr: 
tldr:   -A Sets the minimum allocation area size (default 512k) Egs: -A1m 
-A10k
tldr:   -n Allocation area chunk size (0 = disabled, default: 0)
tldr:   -O Sets the minimum size of the old generation (default 1M)
tldr:   -M Sets the maximum heap size (default unlimited)  Egs: -M256k 
-M1G
tldr:   -H Sets the minimum heap size (default 0M)   Egs: -H24m  -H1G
tldr:   -xb Sets the address from which a suitable start for the heap 
memory
tldr: will be searched from. This is useful if the default address
tldr: clashes with some third-party library.
tldr:   -mMinimum % of heap which must be available (default 3%)
tldr:   -GNumber of generations (default: 2)
tldr:   -cUse in-place compaction instead of copying in the oldest 
generation
tldr:when live data is at least % of the maximum heap size set 
with
tldr:-M (default: 30%)
tldr:   -c   Use in-place compaction for all oldest generation collections
tldr:(the default is to use copying)
tldr:   -w   Use mark-region for the oldest generation (experimental)
tldr:   -I  Perform full GC after  idle time (default: 0.3, 0 == off)
tldr: 
tldr:   -T Collect GC statistics (useful for in-program statistics 
access)
tldr:   -t[] One-line GC statistics (if  omitted, uses stderr)
tldr:   -s[] Summary  GC statistics (if  omitted, uses stderr)
tldr:   -S[] Detailed GC statistics (if  omitted, uses stderr)
tldr: 
tldr: 
tldr:   -Z   Don't squeeze out update frames on stack overflow
tldr:   -B   Sound the bell at the start of each garbage collection
tldr: 
tldr:   -h   Heap residency profile (output file .hp)
tldr:   -i  Time between heap profile samples (seconds, default: 0.1)
tldr: 
tldr:   -C  Context-switch interval in seconds.
tldr: 0 or no argument means switch as often as possible.
tldr: Default: 0.02 sec.
tldr:   -V  Master tick interval in seconds (0 == disable timer).
tldr: This sets the resolution for -C and the heap profile timer -i,
tldr: and is the frequence of time profile samples.
tldr: Default: 0.01 sec.
tldr: 
tldr:   --install-signal-handlers=
tldr: Install signal handlers (default: yes)
tldr:   -e Maximum number of outstanding local sparks (default: 4096)
tldr:   -xq   The allocation limit given to a thread after it receives
tldr: an AllocationLimitExceeded exception. (default: 100k)
tldr: 
tldr: RTS options may also be specified using the GHCRTS environment variable.
tldr: 
tldr: Other RTS options may be available for programs compiled a different way.
tldr: The GHC User's Guide has full details.
tldr: 
debian/rules:16: recipe for target 'tldr-hs.1' failed
make: *** [tldr-hs.1] Error 1
--- End Message ---
--- Begin Message ---
Source: haskell-tldr

Bug#888513: huge graphical bug

[Samuel Thibault]

melissa M., on ven. 26 janv. 2018 19:12:32 +0100, wrote:
> despite the different options, there is no change, the bug persists...

If there is no change, there must be an error in passing the kernel arg,
how do you pass them?

vga=normal fb=false 

should get you to a pure textmode, there's no way you can get the split
image you sent to the bug, or your graphic card is *seriously* broken if
it can't even properly display pure text.

Samuel

Bug#888020: Package conflict between primus and nvidia 384.111-3 drivers

[Luca Boccassi]

On Wed, 2018-01-24 at 07:49 +0100, Andreas Beckmann wrote:
> On 2018-01-22 21:10, Andreas Beckmann wrote:
> > I think we may have to update some documentation for this recent
> > change
> > (nvidia-driver.README.Debian),
> 
> Luca,
> 
> can you update the instructions to use the
> nvidia-driver-libs{,-nonglvnd} metapackages? With tested commands :-)
> I did a lot of tests installing, switching and upgrading in chroots
> (with apt-get). More testing, especially if more package become
> available in backports would be welcome.
> 
> Maybe also mention that primus/optimus users will need the nonglvnd
> variant.
> 
> Thanks
> 
> 
> Andreas

Sure will look at that during the week-end.

What do you think about adding a dependency to nvidia-libs-nonglvnd in
bumblebee-nvidia? It already depends on nvidia-driver

-- 
Kind regards,
Luca Boccassi

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

Processed: tagging 888199, tagging 888052

[Debian Bug Tracking System]

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

> tags 888199 - pending
Bug #888199 [libgjs0g] gnome-shell crashes at different circumstances (not 
usable anymore)
Removed tag(s) pending.
> tags 888052 - pending
Bug #888052 [libgjs0g] gnome-shell: Restarts every 10 minutes related to 
dbus-org.freedesktop.hostname1.service
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#887766: marked as done (thunderbird FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Fri, 26 Jan 2018 17:41:54 +
with message-id 
and subject line Bug#887766: fixed in thunderbird 1:52.6.0-1
has caused the Debian Bug report #887766,
regarding thunderbird FTBFS with glibc 2.26
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.)


-- 
887766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thunderbird
Version: 1:52.5.2-2
Severity: serious
Tags: buster sid
Control: found -1 1:52.4.0-1

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

...
/build/1st/thunderbird-52.5.2/mozilla/intl/icu/source/i18n/digitlst.cpp:67:24: 
fatal error: xlocale.h: No such file or directory
 #   include 
^
compilation terminated.
/build/1st/thunderbird-52.5.2/mozilla/intl/icu/source/config/mh-linux:49: 
recipe for target 'digitlst.ao' failed
make[3]: *** [digitlst.ao] Error 1
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:52.6.0-1

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated thunderbird 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 25 Jan 2018 20:21:10 +0100
Source: thunderbird
Binary: thunderbird thunderbird-dev lightning calendar-google-provider 
thunderbird-l10n-all thunderbird-l10n-ar thunderbird-l10n-ast 
thunderbird-l10n-be thunderbird-l10n-bg thunderbird-l10n-bn-bd 
thunderbird-l10n-br thunderbird-l10n-ca thunderbird-l10n-cs thunderbird-l10n-da 
thunderbird-l10n-de thunderbird-l10n-dsb thunderbird-l10n-el 
thunderbird-l10n-en-gb thunderbird-l10n-es-ar thunderbird-l10n-es-es 
thunderbird-l10n-et thunderbird-l10n-eu thunderbird-l10n-fi thunderbird-l10n-fr 
thunderbird-l10n-fy-nl thunderbird-l10n-ga-ie thunderbird-l10n-gd 
thunderbird-l10n-gl thunderbird-l10n-he thunderbird-l10n-hr 
thunderbird-l10n-hsb thunderbird-l10n-hu thunderbird-l10n-hy-am 
thunderbird-l10n-id thunderbird-l10n-is thunderbird-l10n-it thunderbird-l10n-ja 
thunderbird-l10n-kab thunderbird-l10n-ko thunderbird-l10n-lt 
thunderbird-l10n-nb-no thunderbird-l10n-nl thunderbird-l10n-nn-no 
thunderbird-l10n-pa-in thunderbird-l10n-pl thunderbird-l10n-pt-br 
thunderbird-l10n-pt-pt
 thunderbird-l10n-rm thunderbird-l10n-ro thunderbird-l10n-ru 
thunderbird-l10n-si thunderbird-l10n-sk thunderbird-l10n-sl thunderbird-l10n-sq 
thunderbird-l10n-sr thunderbird-l10n-sv-se thunderbird-l10n-ta-lk 
thunderbird-l10n-tr thunderbird-l10n-uk thunderbird-l10n-vi 
thunderbird-l10n-zh-cn thunderbird-l10n-zh-tw lightning-l10n-ar 
lightning-l10n-ast lightning-l10n-be lightning-l10n-bg lightning-l10n-bn-bd 
lightning-l10n-br lightning-l10n-ca lightning-l10n-cs lightning-l10n-cy 
lightning-l10n-da lightning-l10n-de lightning-l10n-dsb lightning-l10n-el 
lightning-l10n-es-ar lightning-l10n-es-es lightning-l10n-en-gb 
lightning-l10n-et lightning-l10n-eu lightning-l10n-fi lightning-l10n-fr 
lightning-l10n-fy-nl lightning-l10n-ga-ie lightning-l10n-gd lightning-l10n-gl 
lightning-l10n-he lightning-l10n-hr lightning-l10n-hsb lightning-l10n-hu 
lightning-l10n-hy-am lightning-l10n-id lightning-l10n-is lightning-l10n-it 
lightning-l10n-ja lightning-l10n-kab lightning-l10n-ko
 lightning-l10n-lt lightning-l10n-nb-no lightning-l10n-nl lightning-l10n-nn-no 
lightning-l10n-pa-in lightning-l10n-pl lightning-l10n-pt-br 
lightning-l10n-pt-pt lightning-l10n-rm lightning-l10n-ro lightning-l10n-ru 
lightning-l10n-si lightning-l10n-sk lightning-l10n-sl lightning-l10n-sr 
lightning-l10n-sq lightning-l10n-sv-se lightning-l10n-ta-lk lightning-l10n-tr 
lightning-l10n-uk lightning-l10n-vi lightning-l10n-zh-cn
 lightning-l10n-zh-tw
Architecture: source
Version: 1:52.6.0-1
Distribution: unstable
Urgency: high
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Description:
 calendar-google-provider - Google Calendar 

Processed: Re: Bug#888199: gnome-shell crashes at different circumstances (not usable anymore)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #888199 [libgjs0g] gnome-shell crashes at different circumstances (not 
usable anymore)
Ignoring request to alter tags of bug #888199 to the same tags previously set

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

Bug#888199: gnome-shell crashes at different circumstances (not usable anymore)

[Simon McVittie]

Control: tags -1 + moreinfo

On Fri, 26 Jan 2018 at 00:02:57 +, Simon McVittie wrote:
> On Thu, 25 Jan 2018 at 21:39:22 +0100, Thomas Renard wrote:
> > I downgraded libgjs0g to 1.50.2-2 and the whole desktop is stable again.
> 
> Would you be able to install systemd-coredump, upgrade libgjs0g to the
> broken version, let gnome-shell crash a few times, downgrade back to
> 1.50.2-2 so you can get back into a working GUI, and report what was
> logged about the crashes?

I've uploaded version 1.50.3-2 which reverts some of the upstream changes
that were brought in with 1.50.2-3. When it has built and propagated to
your mirror, please could you try that version and report whether it's
stable for you? This would be useful information in working out how to
fix this properly. Be prepared to downgrade back to 1.50.2-2 if that
doesn't work.

Please also report any warnings from gnome-shell in the Journal that seem
to be correlated with the times when it would previously have crashed.

Thanks,
smcv

Bug#871566: swarmkit FTBFS: cannot find package "github.com/docker/docker/api/types"

[Edmund Grimley Evans]

swarmkit should build-dep on golang-github-docker-docker-dev (>=
1.13.1~), or something like that.

Bug#888199: Bug #888199 in gjs marked as pending

[smcv]

Control: tag -1 pending

Hello,

Bug #888199 in gjs 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/gnome-team/gjs/commit/e6674aa1a11c47e034aae3985d5a73df6cc03728


Revert some of the upstream changes from 1.50.3

They appear to cause crashes.

Closes: #888485
Related to: #888052, #888199



(this message was generated automatically)
-- 
Greetings

Bug#888236: torbrowser-launcher: broken by Tor Browser 7.5: No such file or directory: '.../Docs/sources/versions'

[Ivan Vilata i Balaguer]

Package: torbrowser-launcher
Version: 0.2.8-6
Followup-For: Bug #888236

Also bitten by this.

The Tor Browser is still installed under the home directory.  To run it while
this issue gets fix, open a shell and execute:


~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/start-tor-browser

(This is for x86_64 machines, evidently.  This seems to work for me but I'm
not guaranteeing that it's a recommendable way to run it!)

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

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

Versions of packages torbrowser-launcher depends on:
ii  ca-certificates   20170717
ii  gnupg 2.2.4-1
ii  libdbus-glib-1-2  0.108-3
ii  python2.7.14-4
ii  python-gtk2   2.24.0-5.1+b1
ii  python-lzma   0.5.3-3
ii  python-parsley1.2-1
ii  python-psutil 5.4.2-1
ii  python-twisted17.9.0-1
ii  python-txsocksx   1.15.0.2-1

Versions of packages torbrowser-launcher recommends:
ii  tor  0.3.2.9-1

Versions of packages torbrowser-launcher suggests:
ii  apparmor   2.12-1
ii  python-pygame  1.9.3+dfsg-2+b1

-- no debconf information

Processed: Bug #888199 in gjs marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888199 [libgjs0g] gnome-shell crashes at different circumstances (not 
usable anymore)
Added tag(s) pending.

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

Bug#888508: gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory

[Pirate Praveen]

On വെള്ളി 26 ജനുവരി 2018 07:32 വൈകു, Salvatore Bonaccorso wrote:
> See
> https://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/
> for which several go back to 8.9.0 versions.
> 
> There are three CVEs out of
> https://security-tracker.debian.org/tracker/source-package/gitlab
> belonging to that list wich are yet marked undetermined, because not
> clear from the advisory if 8.13.11=dfsg1-12 might be affected.
> But assuming the 'version affected' information is correct, they are
> not, please confirm so we can adjust the security-tracker information.

We are working on backporting the patches (8.13.12 don't have most of
these patches). We will confirm once we go through all of it.



signature.asc
Description: OpenPGP digital signature

Bug#887530: cen64-qt FTBFS with libquazip5-headers 0.7.3-3

[Dan]

On Wed, 24 Jan 2018 23:29:33 +0200 Juhani Numminen  
wrote:

John Paul Adrian Glaubitz kirjoitti 24.01.2018 klo 23:06:
> On 01/24/2018 09:42 PM, Juhani Numminen wrote:
>> Fixed in this upstream commit:
>> 
https://github.com/dh4/cen64-qt/commit/2592c4f977a798e9787f9f50f5d1d334db9ad94d
> 
> Thanks.
> 
> If you could release a new upstream release. I could go ahead and package that

> version. Then I wouldn't have to carry the patch in the Debian package.

To clear a possible misunderstanding, I am not the upstream, rather I was
connecting upstream fixes to FTBFS bugs in Debian ("Bug squasher view" at
https://udd.debian.org/bugs/).

In the case of this bug, I reported the problem for mupen64plus-qt first
https://github.com/dh4/mupen64plus-qt/issues/33#issuecomment-359922529
and then the upstream developer fixed both mupen64plus-qt and cen64-qt.

Cheers,
Juhani




I've released a new upstream version incorporating the fix for this bug:
https://github.com/dh4/cen64-qt/releases/tag/20180125-alpha

- Dan

Bug#888519: python-cliff: FTBFS: Test failures

[Daniel Schepler]

Source: python-cliff
Version: 2.8.0-3
Severity: serious

>From my pbuilder build log (on amd64):

...
cliff.tests.test_utils.TestTerminalWidth.test
cliff.tests.test_utils.TestTerminalWidth.test ... ok
cliff.tests.test_utils.TestTerminalWidth.test_get_terminal_size
cliff.tests.test_utils.TestTerminalWidth.test_get_terminal_size ...
skipped u'only needed for python 3.3 onwards'
cliff.tests.test_utils.TestTerminalWidth.test_ioctl
cliff.tests.test_utils.TestTerminalWidth.test_ioctl ... ok
cliff.tests.test_utils.TestTerminalWidth.test_windows
cliff.tests.test_utils.TestTerminalWidth.test_windows ... ok

==
FAIL: cliff.tests.test_app.TestInteractiveMode.test_interactive_mode_cmdloop
cliff.tests.test_app.TestInteractiveMode.test_interactive_mode_cmdloop
--
_StringException: Traceback (most recent call last):
 File "cliff/tests/test_app.py", line 77, in test_interactive_mode_cmdloop
   app.run([])
 File "cliff/app.py", line 277, in run
   result = self.interact()
 File "cliff/app.py", line 316, in interact
   from .interactive import InteractiveApp
 File "cliff/interactive.py", line 20, in 
   import cmd2
 File "/usr/lib/python2.7/dist-packages/cmd2.py", line 333, in 
   except pyperclip.exceptions.PyperclipException:
AttributeError: 'module' object has no attribute 'exceptions'


==
FAIL: unittest2.loader._FailedTest.cliff.tests.test_interactive
unittest2.loader._FailedTest.cliff.tests.test_interactive
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: cliff.tests.test_interactive
Traceback (most recent call last):
 File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line
456, in _find_test_path
   module = self._get_module_from_name(name)
 File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line
395, in _get_module_from_name
   __import__(name)
 File "cliff/tests/test_interactive.py", line 15, in 
   import cmd2
 File "/usr/lib/python2.7/dist-packages/cmd2.py", line 333, in 
   except pyperclip.exceptions.PyperclipException:
AttributeError: 'module' object has no attribute 'exceptions'


--
Ran 151 tests in 1.026s

FAILED (failures=2, skipped=1)
debian/rules:35: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/build/python-cliff-2.8.0'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
-- 
Daniel Schepler

Bug#888513: huge graphical bug

[Lennart Sorensen]

On Fri, Jan 26, 2018 at 04:21:08PM +0100, melissa M. wrote:
> Package: debian-installer
> Version: stable
> Severity: grave
> 
> hi maintainer,
> 
> big graphical bug with the installer netinstall of Debian Stretch 9.3, but
> also Testing and Sid.
> 
> Ditto with the installer mini iso-Stretch 9.3
> 
> I created my bootable usb drive with "dd", unetbootin, etcher, but the big
> graphical bug still present :(
> 
> I have a laptop pc Toshiba Satellite P870-338 with the Optimus technology
> (graphics chipset intel i7 3630qm and nvidia GT 630m) with a bios 100% uefi
> 
> this is the screen that I get with the installer, it is impossible to
> install in these conditions.
> http://pix.toile-libre.org/upload/original/1516915180.jpg
> 
> I think I might be an isolated case, but I still haven't found solution to
> resolve this bug very annoying.
> 
> the bug has been present since two years...
> 
> is there a workaround ??
> a parameter to pass to the kernel ??
> 
> this bug est present on the mini iso, and the iso netinstall (testing,
> stable and sid). :'(
> 
> please consider my bug report.

Does it happen in both graphical and text mode install?

-- 
Len Sorensen

Bug#888513: huge graphical bug

[Samuel Thibault]

melissa M., on ven. 26 janv. 2018 16:21:08 +0100, wrote:
> is there a workaround ??
> a parameter to pass to the kernel ??

There is documentation about it in the help screen of the boot menu.

Samuel

Bug#888513: huge graphical bug

[melissa M.]

Package: debian-installer
Version: stable
Severity: grave

hi maintainer,

big graphical bug with the installer netinstall of Debian Stretch 9.3, but
also Testing and Sid.

Ditto with the installer mini iso-Stretch 9.3

I created my bootable usb drive with "dd", unetbootin, etcher, but the big
graphical bug still present :(

I have a laptop pc Toshiba Satellite P870-338 with the Optimus technology
(graphics chipset intel i7 3630qm and nvidia GT 630m) with a bios 100% uefi

this is the screen that I get with the installer, it is impossible to
install in these conditions.
http://pix.toile-libre.org/upload/original/1516915180.jpg

I think I might be an isolated case, but I still haven't found solution to
resolve this bug very annoying.

the bug has been present since two years...

is there a workaround ??
a parameter to pass to the kernel ??

this bug est present on the mini iso, and the iso netinstall (testing,
stable and sid). :'(

please consider my bug report.

Bug#884173: Extensions are just part of it

[Matías Bellone]

Tollef, I don have the Signal extension to disable unfortunately.

After a month of testing, I couldn't isolate the issue to one particular
extension either. I tried uninstalling all my extensions one by one. I even
tried creating a new profile, but the issue still happens no matter what.
Granted, I did sync up the new profile with my google account - which
pulled my extensions.

Unless it is being run with --disable-extensions. If run with the latter I
have been running for weeks without issues (even through suspends and doing
regular browsing). I just tried running with extensions again and didn't
make it through the first few minutes.

Regards,
Toote

PS: it is still possible that I am not uninstalling the extensions correctly

Bug#887761: user-mode-linux FTBFS with glibc 2.26

[Juhani Numminen]

On Fri, 19 Jan 2018 20:05:45 +0200 Adrian Bunk  wrote:
> Source: user-mode-linux
> ...
> arch/um/os-Linux/signal.c:163:22: error: dereferencing pointer to incomplete 
> type 'struct ucontext'
>   mcontext_t *mc = >uc_mcontext;

It seems that there is a patch for this:
https://patchwork.kernel.org/patch/10110461/

Regards,
Juhani

Bug#887777: indigo FTBFS with glibc 2.26

[Juhani Numminen]

On Fri, 19 Jan 2018 22:53:11 +0200 Adrian Bunk  wrote:
> Source: indigo
> ...
> /build/1st/indigo-1.1.12/common/base_cpp/locale_guard.h:20:10: fatal error: 
> xlocale.h: No such file or directory

More info on “Removal of xlocale.h”:
https://sourceware.org/glibc/wiki/Release/2.26#Removal_of_.27xlocale.h.27

Regards,
Juhani

Bug#888459: flint-arb's tests fail on 32bit archs using mpfr 4.0.0

[Vincent Lefevre]

On 2018-01-25 23:43:14 +0100, Matthias Klose wrote:
> the testsuite fails on all 32bit architectures.
[...]
> divFAIL (aliasing 4)!
> prec = 352, rnd = 4
> 
> x =
> (4586997233048136541430758450064474100387735230759824291973833691816938709832156080645343570059119116156929
> * 2^-154742412678922490659733883)
> 
> y =
> (51814976846671518298238808760042830604686502339620382299366747655022166929406808804341858227567903870767891933265103849315791036770763130077955430384829058539908460614800988509303528381975119100503701824233100229972596599113543202092890645352456600459286399836135725531911334505568114757105479020098464557517116791851426250751
> * 2^-154742431125385089392575577)
> 
> v =
> (2135987036418233318920600437589210504846524088997312026086185915310372929010612927677735486095361
> * 2^-154742412678922490659733852)
> 
> r1 = 1, r2 = 1

It may be a bug in MPFR 4.

I've built a 32-bit version on my machine, after adding a few
flint_printf because above, one just has one input and two outputs.

default:
flint_printf("x = "); arf_print(x); flint_printf("\n");
flint_printf("y = "); arf_print(y); flint_printf("\n");
r2 = arf_div_naive(v, y, x, prec, rnd);
flint_printf("v = "); arf_print(v); flint_printf("\n");
r1 = arf_div(x, y, x, prec, rnd);
flint_printf("x = "); arf_print(x); flint_printf("\n\n");
if (!arf_equal(x, v) || r1 != r2)
{
flint_printf("FAIL (aliasing 4)!\n");
flint_printf("prec = %wd, rnd = %d\n\n", prec, rnd);
flint_printf("x = "); arf_print(x); flint_printf("\n\n");
flint_printf("y = "); arf_print(y); flint_printf("\n\n");
flint_printf("v = "); arf_print(v); flint_printf("\n\n");
flint_printf("r1 = %wd, r2 = %wd\n", r1, r2);
flint_abort();
}
break;

I can reproduce the failure:

x = (4294967295 * 2^-18446462598732840995)
y = 
(51814976846671518298238808760042830604686502339620382299366747655022166929406808804341858227567903870767891933265103849315791036770763130077955430384829058539908460614800988509303528381975119100503701824233100229972596599113543202092890645352456600459286399836135725531911334505568114757105479020098464557517116791851426250751
 * 2^-154742431125385089392575577)
v = 
(2135987036418233318920600437589210504846524088997312026086185915310372929010612927677735486095361
 * 2^-154742412678922490659733852)
x = 
(4586997233048136541430758450064474100387735230759824291973833691816938709832156080645343570059119116156929
 * 2^-154742412678922490659733883)

FAIL (aliasing 4)!
prec = 352, rnd = 4

x = 
(4586997233048136541430758450064474100387735230759824291973833691816938709832156080645343570059119116156929
 * 2^-154742412678922490659733883)

y = 
(51814976846671518298238808760042830604686502339620382299366747655022166929406808804341858227567903870767891933265103849315791036770763130077955430384829058539908460614800988509303528381975119100503701824233100229972596599113543202092890645352456600459286399836135725531911334505568114757105479020098464557517116791851426250751
 * 2^-154742431125385089392575577)

v = 
(2135987036418233318920600437589210504846524088997312026086185915310372929010612927677735486095361
 * 2^-154742412678922490659733852)

r1 = 1, r2 = 1

I'm going to look at it more closely.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#871566: swarmkit FTBFS: cannot find package "github.com/docker/docker/api/types"

[Edmund Grimley Evans]

I was able to build swarmkit on arm64 after I manually installed a
newer golang-github-docker-docker-dev.

There's some kind of circular dependency between swarmkit and
docker.io. I think someone will have to break it with a binary upload.
(There was a binary upload on amd64, I notice.)

According to my "history", I did something like:

apt-get build-dep docker.io
apt-get build-dep swarmkit
apt-get install golang-github-docker-docker-dev
wget 
http://ftp.uk.debian.org/debian/pool/main/d/docker.io/golang-github-docker-docker-dev_1.13.1~ds2-3_all.deb
dpkg -i golang-github-docker-docker-dev_1.13.1~ds2-3_all.deb
apt-get install golang-github-opencontainers-docker-runc-dev
apt --fix-broken install
dpkg -i golang-github-docker-docker-dev_1.13.1~ds2-3_all.deb
apt-get source swarmkit
cd swarmkit-1.12.0+git20170111.763.296fcfcf
dpkg-buildpackage -b

Bug#888508: gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory

[Salvatore Bonaccorso]

Source: gitlab
Version: 8.13.11+dfsg1-12
Severity: grave
Tags: upstream security

Hi 

See
https://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/
for which several go back to 8.9.0 versions.

There are three CVEs out of
https://security-tracker.debian.org/tracker/source-package/gitlab
belonging to that list wich are yet marked undetermined, because not
clear from the advisory if 8.13.11=dfsg1-12 might be affected.
But assuming the 'version affected' information is correct, they are
not, please confirm so we can adjust the security-tracker information.

Regards,
Salvatore


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

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

Bug#888182: qemu-system-arm: qemu-system-arm crashes when run as part of the nbdkit testsuite

[Richard W.M. Jones]

I was able to reproduce a crashing bug in qemu-system-arm on armv7
host.  I'm _not_ going to claim this is the same bug that Debian is
seeing, but it might be.

It's deep inside TCG and unfortunately there is not a lot of useful
information in the stack trace.  However it's clearly a bug in qemu.

Core was generated by `/usr/bin/qemu-system-arm -global 
virtio-blk-device.scsi=off -enable-fips -nodef'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xab6a7aa8 in ?? ()
[Current thread is 1 (Thread 0xaa9f7f90 (LWP 25252))]
(gdb) bt
#0  0xab6a7aa8 in ?? ()
#1  0xaba87ad0 in code_gen_buffer ()
#2  0x006291e0 in cpu_tb_exec (itb=, itb=, 
cpu=)
at /usr/src/debug/qemu-2.11.0-4.fc28.arm/accel/tcg/cpu-exec.c:167
#3  cpu_loop_exec_tb (tb_exit=, 
last_tb=, tb=, cpu=)
at /usr/src/debug/qemu-2.11.0-4.fc28.arm/accel/tcg/cpu-exec.c:627
#4  cpu_exec (cpu=)
at /usr/src/debug/qemu-2.11.0-4.fc28.arm/accel/tcg/cpu-exec.c:736
#5  0x005efae4 in qemu_tcg_cpu_thread_fn (arg=0x13ce3e0)
at /usr/src/debug/qemu-2.11.0-4.fc28.arm/cpus.c:1270
#6  0xb53f3f1c in start_thread () from /lib/libpthread.so.0
#7  0xb53790d8 in ?? () from /lib/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

I'm using:

* qemu-system-arm-2.11.0-4.fc28.armv7hl
* kernel-lpae-4.15.0-0.rc9.git2.1.fc28.armv7hl

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v

Bug#887763: cctools FTBFS with glibc 2.26

[Juhani Numminen]

Control: tags -1 patch

On Fri, 19 Jan 2018 20:18:04 +0200 Adrian Bunk  wrote:
> Source: cctools
> ...
> mpi_queue_worker.c:551:23: error: array type has incomplete element type 
> 'struct option'
>   static struct option long_options[] = {
> mpi_queue_worker.c:552:13: error: 'required_argument' undeclared (first use 
> in this function)
>{"debug", required_argument, 0, 'd'},
> mpi_queue_worker.c:562:13: warning: implicit declaration of function 
> 'getopt_long'; did you mean 'getpayload'? [-Wimplicit-function-declaration]

The attached patch seems to resolve this FTBFS by adding #include "getopt.h".

Cheers,
Juhani
Description: Add missing includes to fix FTBFS with glibc 2.26
Author: Juhani Numminen 
Bug-Debian: https://bugs.debian.org/887763
Last-Update: 2018-01-26

--- a/work_queue/src/mpi_queue_worker.c
+++ b/work_queue/src/mpi_queue_worker.c
@@ -14,6 +14,7 @@
 #include "itable.h"
 #include "debug.h"
 #include "create_dir.h"
+#include "getopt.h"
 
 #include 
 #include 
--- a/parrot/src/parrot_cp.c
+++ b/parrot/src/parrot_cp.c
@@ -7,6 +7,7 @@
 #include "pfs_types.h"
 #include "full_io.h"
 #include "parrot_client.h"
+#include "getopt.h"
 
 #include 
 #include 

Processed: Re: cctools FTBFS with glibc 2.26

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #887763 [src:cctools] cctools FTBFS with glibc 2.26
Added tag(s) patch.

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

Processed: retitle 888484 to clamav: Security release 0.99.3 available (CVE-2017-12374 CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 CVE-2017-12380)

[Debian Bug Tracking System]

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

> retitle 888484 clamav: Security release 0.99.3 available (CVE-2017-12374 
> CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 
> CVE-2017-12380)
Bug #888484 [clamav] clamav: Security release 0.99.3 available (CVE-2017-12374 
CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 
CVE-2017-12379 CVE-2017-12380)
Changed Bug title to 'clamav: Security release 0.99.3 available (CVE-2017-12374 
CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 
CVE-2017-12380)' from 'clamav: Security release 0.99.3 available 
(CVE-2017-12374 CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 
CVE-2017-12379 CVE-2017-12379 CVE-2017-12380)'.
> thanks
Stopping processing here.

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

Processed: tagging 888484

[Debian Bug Tracking System]

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

> tags 888484 + fixed-upstream
Bug #888484 [clamav] clamav: Security release 0.99.3 available (CVE-2017-12374 
CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 
CVE-2017-12380)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#888501: gstreamer1.0-vaapi: Latests versions does not work at all

[Junior Polegato]

Package: gstreamer1.0-vaapi
Version: 1.12.4-1+b2
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

Hi!

I am using Debian Testing with lastests Gnome/Xorg and I have had a problem
with gstreamer1.0-vaapi.

With vaapi enabled, I see about 120 streams without problems or lags, otherwise
I just can see about 14 ~ 16 streams.

I did some tests with old packages versions from snapshot, where I got this
problems:


Versions: 1.10.4-1+b1 or 1.11.91-1 or 1.12.0-1

libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/i386-linux-gnu/dri/i965_drv_video.so
libva error: /usr/lib/i386-linux-gnu/dri/i965_drv_video.so has no function
__vaDriverInit_0_32
libva info: va_openDriver() returns -1


Versions: 1.12.1-1 or 1.12.2-1 or 1.12.2-1+b1 or 1.12.3-1 or 1.12.3-1+b1 or
1.12.3-2

libva error: /usr/lib/i386-linux-gnu/dri/i965_drv_video.so has no function
__vaDriverInit_0_32


Versions: 1.12.3-2+b1 or 1.12.4-1 or 1.12.4-1+b1 or 1.12.4-1+b2




So I downgrade i965-va-driver package and hold it, "hold" because this didn't
broken apt:

dpkg -i i965-va-driver_1.8.3-1_i386.deb
echo i965-va-driver hold | dpkg --set-selections


Now I a get this:


Versions: 1.10.4-1+b1 or 1.11.91-1 or 1.12.0-1 ==> THIS WORKS

libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/i386-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_40
libva info: va_openDriver() returns 0


Versions: 1.12.1-1 or 1.12.2-1 or 1.12.2-1+b1 or 1.12.3-1 or 1.12.3-1+b1 or
1.12.3-2 or 1.12.3-2+b1 or 1.12.4-1 or 1.12.4-1+b1 or 1.12.4-1+b2




Can someone solve this for lastest gstreamer1.0-vaapi and i965-va-driver to
work?

Thanks.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (65, 'unstable'), (60, 'stable'), (55, 
'experimental')
Architecture: i386 (i686)

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

Versions of packages gstreamer1.0-vaapi depends on:
pn  libc6   
ii  libdrm2 2.4.89-1
ii  libegl1 1.0.0-1.1
ii  libgl1  1.0.0-1.1
ii  libglib2.0-02.54.3-1
ii  libgstreamer-plugins-bad1.0-0   1.12.4-2+b1
ii  libgstreamer-plugins-base1.0-0  1.12.4-1
ii  libgstreamer1.0-0   1.12.4-1
ii  libudev1236-3
ii  libva-drm2  2.0.0-2
ii  libva-wayland2  2.0.0-2
ii  libva-x11-2 2.0.0-2
ii  libva2  2.0.0-2
ii  libwayland-client0  1.14.0-1+b1
ii  libx11-62:1.6.4-3
ii  libxrandr2  2:1.5.1-1
ii  libxrender1 1:0.9.10-1

gstreamer1.0-vaapi recommends no packages.

Versions of packages gstreamer1.0-vaapi suggests:
pn  gstreamer1.0-vaapi-doc  

-- no debconf information

Processed: tagging 888484

[Debian Bug Tracking System]

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

> tags 888484 + upstream
Bug #888484 [clamav] clamav: Security release 0.99.3 available (CVE-2017-12374 
CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 
CVE-2017-12379 CVE-2017-12380)
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: found 888484 in 0.98.6+dfsg-1 ...

[Debian Bug Tracking System]

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

> found 888484 0.98.6+dfsg-1
Bug #888484 [clamav] clamav: Security release 0.99.3 available
Marked as found in versions clamav/0.98.6+dfsg-1.
> retitle 888484 clamav: Security release 0.99.3 available (CVE-2017-12374 
> CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 
> CVE-2017-12379 CVE-2017-12380)
Bug #888484 [clamav] clamav: Security release 0.99.3 available
Changed Bug title to 'clamav: Security release 0.99.3 available (CVE-2017-12374 
CVE-2017-12375 CVE-2017-12376 CVE-2017-12377 CVE-2017-12378 CVE-2017-12379 
CVE-2017-12379 CVE-2017-12380)' from 'clamav: Security release 0.99.3 
available'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#888484: clamav: Security release 0.99.3 available

[Debian Bug Tracking System]

Processing control commands:

> tags -1 security
Bug #888484 [clamav] clamav: Security release 0.99.3 available
Added tag(s) security.
> severity -1 grave
Bug #888484 [clamav] clamav: Security release 0.99.3 available
Severity set to 'grave' from 'important'

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

Processed: Bug#888477 marked as pending

[Debian Bug Tracking System]

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

> tag 888477 pending
Bug #888477 [src:glibc] glibc FTBFS on arm64: dangerous relocation: unsupported 
relocation
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#888477: marked as pending

[Aurelien Jarno]

tag 888477 pending
thanks

Hello,

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

https://anonscm.debian.org/cgit/pkg-glibc/glibc.git/commit/?id=741cbe1

---
commit 741cbe1479259e28e5641a749be0a02e5b50435c
Author: Aurelien Jarno 
Date:   Fri Jan 26 12:14:33 2018 +0100

debian/patches/git-updates.diff: update from upstream stable branch:

* debian/patches/git-updates.diff: update from upstream stable branch:
  - Fix build with binutils 2.30 on arm64.  Closes: #888477.

diff --git a/debian/changelog b/debian/changelog
index c0372ce..b1c4649 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+glibc (2.26-6) UNRELEASED; urgency=medium
+
+  [ Aurelien Jarno ]
+  * debian/patches/git-updates.diff: update from upstream stable branch:
+- Fix build with binutils 2.30 on arm64.  Closes: #888477.
+
+ -- Aurelien Jarno   Fri, 26 Jan 2018 12:13:38 +0100
+
 glibc (2.26-5) unstable; urgency=medium
 
   [ Samuel Thibault ]

Bug#887694: vpcs FTBFS with glibc 2.26

[Juhani Numminen]

Control: tags -1 patch

On Fri, 19 Jan 2018 07:03:51 +0200 Adrian Bunk  wrote:
> Source: vpcs
> ...
> gcc  -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -DLinux -Wall -I. -DTAP -DHV -Wno-strict-aliasing -c 
> hv.c
> In file included from hv.c:45:0:
> ./getopt.h:53:5: error: conflicting types for 'getopt'
>  int getopt(int argc, char** argv, char* optstr);
>  ^~
> In file included from /usr/include/x86_64-linux-gnu/bits/getopt_posix.h:27:0,
>  from /usr/include/unistd.h:872,
>  from hv.c:33:
> /usr/include/x86_64-linux-gnu/bits/getopt_core.h:91:12: note: previous 
> declaration of 'getopt' was here
>  extern int getopt (int ___argc, char *const *___argv, const char 
> *__shortopts)

I came up with the attached patch that renames src/getopt.h to force the use of
/usr/include/getopt.h from libc6-dev. Fixes the FTBFS for me on amd64.

Regards,
Juhani
diff --git a/debian/rules b/debian/rules
index bc09966..acdb8b9 100755
--- a/debian/rules
+++ b/debian/rules
@@ -22,7 +22,11 @@ export DEB_LDFLAGS_MAINT_APPEND = -lpthread -lutil -s
 	dh $@
 
 override_dh_auto_build:
+	# src/getopt.h clashes with /usr/include/getopt.h
+	mv src/getopt.h src/getopt.h_RENAMED
 	dh_auto_build
+	mv src/getopt.h_RENAMED src/getopt.h
+
 	sed -n -e '1,/History/!p' readme.txt > CHANGELOG
 
 override_dh_auto_clean:

Processed: Re: vpcs FTBFS with glibc 2.26

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #887694 [src:vpcs] vpcs FTBFS with glibc 2.26
Added tag(s) patch.

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

Processed: Workaround, reduce severity, report upstream

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #887578 [src:bioperl-run] bioperl-run FTBFS: t/Bowtie.t failures
Severity set to 'important' from 'serious'
> forwarded -1 https://github.com/bioperl/bioperl-run/issues/55
Bug #887578 [src:bioperl-run] bioperl-run FTBFS: t/Bowtie.t failures
Set Bug forwarded-to-address to 
'https://github.com/bioperl/bioperl-run/issues/55'.

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

Bug#887578: Workaround, reduce severity, report upstream

[Andreas Tille]

Control: severity -1 important
Control: forwarded -1 https://github.com/bioperl/bioperl-run/issues/55

I've prevented the build problem by simply deactivating the failed
tests.  Since the package builds now severity is downgraded from
serious to important.  I also reported the issue upstream.

Kind regards

Andreas.

-- 
http://fam-tille.de

Processed: astroplan: FTBFS and Debci failure

[Debian Bug Tracking System]

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

> forwarded 887446 https://github.com/astropy/astroplan/issues/342
Bug #887446 [src:astroplan] astroplan: FTBFS and Debci failure
Set Bug forwarded-to-address to 
'https://github.com/astropy/astroplan/issues/342'.
>
End of message, stopping processing here.

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

Processed: Re: cxref FTBFS on amd64/i386 with glibc 2.26

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #887866 [src:cxref] cxref FTBFS on amd64/i386 with glibc 2.26
Added tag(s) fixed-upstream and patch.

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

Bug#887866: cxref FTBFS on amd64/i386 with glibc 2.26

[Juhani Numminen]

Control: tags -1 patch fixed-upstream

On Sun, 21 Jan 2018 08:01:04 +0200 Adrian Bunk  wrote:
> Source: cxref
> ...
> /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:21: cxref: 
> syntax error, unexpected IDENTIFIER, expecting ')'
> ...
>  -1 | 258 :   IDENTIFIER : _Float128

It seems that this was fixed upstream in revision 663:
https://www.gedanken.org.uk/viewvc/cxref?view=revision=663
Patch with DEP-3 metadata attached.

Regards,
Juhani
Description: Add support for extended floating point formats (e.g. _Float128).
Author: Andrew M. Bishop
Origin: http://www.gedanken.org.uk/viewvc/cxref?view=revision=663
Bug-Debian: https://bugs.debian.org/887866
Last-Update: 2018-01-26

--- a/src/parse.l
+++ b/src/parse.l
@@ -24,7 +24,7 @@
   **/ /**
   Written by Andrew M. Bishop
 
-  This file Copyright 1995-2011, 2014 Andrew M. Bishop
+  This file Copyright 1995-2011, 2014, 2017 Andrew M. Bishop
   It may be distributed under the GNU Public License, version 2, or
   any higher version.  See section COPYING of the GNU Public license
   for conditions under which this file may be redistributed.
@@ -319,6 +319,12 @@
 "_Complex"  {  }
 "_Bool" { yylval="_Bool";return(BOOL); }
 
+ /* ISO/IEC TS 18661-3:2015 */
+
+"_Float128" { yylval="_Float128"; return(FLOAT_EXTENSION); }
+"_Float80"  { yylval="_Float80" ; return(FLOAT_EXTENSION); }
+"_Float64x" { yylval="_Float64x"; return(FLOAT_EXTENSION); }
+
  /* C language keywords. */
 
 "auto"  { yylval="auto"; return(AUTO); }
--- a/src/parse.y
+++ b/src/parse.y
@@ -152,7 +152,7 @@
 %token LEFT_SHIFT RIGHT_SHIFT
 %token SIZEOF
 %token TYPEDEF EXTERN STATIC AUTO REGISTER CONST VOLATILE VOID INLINE
-%token CHAR SHORT INT LONG SIGNED UNSIGNED FLOAT DOUBLE BOOL
+%token CHAR SHORT INT LONG SIGNED UNSIGNED FLOAT DOUBLE BOOL FLOAT_EXTENSION
 %token STRUCT UNION ENUM
 %token CASE DEFAULT IF ELSE SWITCH WHILE DO FOR GOTO CONTINUE BREAK RETURN
 %token ASM
@@ -448,6 +448,7 @@
 floating_type_specifier
 	: FLOAT
 	| DOUBLE
+	| FLOAT_EXTENSION
 	| DOUBLE LONG
 { $$=ConcatStrings(3,$1," ",$2); }
 	| LONG DOUBLE
@@ -1424,7 +1425,7 @@
last_yyl==GOTO ||
last_yyl==CHAR || last_yyl==SHORT || last_yyl==INT || last_yyl==LONG ||
last_yyl==SIGNED || last_yyl==UNSIGNED ||
-   last_yyl==FLOAT || last_yyl==DOUBLE ||
+   last_yyl==FLOAT || last_yyl==DOUBLE || last_yyl==FLOAT_EXTENSION ||
last_yyl==BOOL)
yyl=IDENTIFIER;
 

Bug#886483: marked as done (sssd gets confused by existing config file)

[Debian Bug Tracking System]

Your message dated Fri, 26 Jan 2018 09:25:10 +
with message-id 
and subject line Bug#886483: fixed in sssd 1.16.0-4
has caused the Debian Bug report #886483,
regarding sssd gets confused by existing config file
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.)


-- 
886483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sssd
Version: 1.16.0-3
Severity: minor

Dear Maintainer,

There is a regression in 1.16.0-2 and -3, rendering existing sssd configurations
unable to authenticate users. This happens if the old config file has 

services = nss, pam

in it. This used to be "the right way" of doing things but now with socket 
activated
nss and pam services sssd gets confused and its pam service no longer works. 
Removing
said line fixes it (hence "Severity: minor") but this is highly confusign to 
the admin
as the service seems to be up and running.

The clue is in the log:

Jan 06 14:50:47 rigel sssd_check_socket_activated_responders[8175]: (Sat Jan  6 
14:50:47:876645 2018) [sssd] [main] (0x0010): Misconfiguration found for the 
pam responder.
Jan 06 14:50:47 rigel sssd_check_socket_activated_responders[8175]: The pam 
responder has been configured to be socket-activated but it's still mentioned 
in the services' line in /etc/sssd/sssd.conf.
Jan 06 14:50:47 rigel sssd_check_socket_activated_responders[8175]: Please, 
consider either adjusting your services' line in /etc/sssd/sssd.conf or 
disabling the pam's socket by calling:
Jan 06 14:50:47 rigel sssd_check_socket_activated_responders[8175]: "systemctl 
disable sssd-pam.socket"
Jan 06 14:50:47 rigel systemd[1]: sssd-pam-priv.socket: Control process exited, 
code=exited status=17
Jan 06 14:50:47 rigel systemd[1]: sssd-pam-priv.socket: Failed with result 
'exit-code'.
Jan 06 14:50:47 rigel systemd[1]: Failed to listen on SSSD PAM Service 
responder private socket.
Jan 06 14:50:47 rigel systemd[1]: Dependency failed for SSSD PAM Service 
responder socket.
Jan 06 14:50:47 rigel systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start 
failed with result 'dependency'.
Jan 06 14:50:47 rigel systemd[1]: Listening on SSSD NSS Service responder 
socket.

Note how the log says "please consider" instead of "this is an error, this will 
not work" and
later shows a failure.

>From the first "please consider" message I would presume sssd is supposed to 
>gracefully
recover. The service seems to start when needed and responds to some queries 
but always ends
auth process with

[sssd[pam]] [pam_dp_process_reply] (0x0010): Reply error.

And this means auth failure for pam of course.

Cheers,
Juha

P.S. This may be "works as intended" but considering it took me quite a while 
to figure
out why my existing, working configuration got broken and google came up with 
no help at all,
I would think at least getting this report onto google results would be helpful 
to some people.

Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages sssd depends on:
ii  python3-sss  1.16.0-3
ii  sssd-ad  1.16.0-3
ii  sssd-common  1.16.0-3
ii  sssd-ipa 1.16.0-3
ii  sssd-krb51.16.0-3
ii  sssd-ldap1.16.0-3
ii  sssd-proxy   1.16.0-3

sssd recommends no packages.

sssd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sssd
Source-Version: 1.16.0-4

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated sssd 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

Bug#888478: systemd FTBFS on mipsel: /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.90.20180122 assertion fail ../../bfd/elflink.c:9757

[Adrian Bunk]

Control: reassign -1 binutils 2.29.90.20180122-1
Control: affects -1 src:systemd

On Fri, Jan 26, 2018 at 08:29:08AM +0100, Helmut Grohne wrote:
> Source: systemd
> Version: 236-3
> Severity: serious
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> systemd fails to build from source on mipsel. Very likely this is not
> caused by this particular systemd upload, but by the binutils upload
> instead. In any case, the build log (attached) ends with:
> 
> | [1514/1858] cc  -o test-dhcp-server 
> 'test-dhcp-server@exe/src_libsystemd-network_test-dhcp-server.c.o' -flto 
> -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -pie 
> -Wl,--gc-sections -g -O2 -fdebug-prefix-map=/home/helmutg/systemd-236=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
> -Wl,--start-group src/shared/libsystemd-shared-236.so 
> src/libsystemd-network/libsystemd-network.a -Wl,--end-group 
> '-Wl,-rpath,$ORIGIN/src/shared' 
> -Wl,-rpath-link,/home/helmutg/systemd-236/build-deb/src/shared  
> | FAILED: test-dhcp-server 
> | cc  -o test-dhcp-server 
> 'test-dhcp-server@exe/src_libsystemd-network_test-dhcp-server.c.o' -flto 
> -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -pie 
> -Wl,--gc-sections -g -O2 -fdebug-prefix-map=/home/helmutg/systemd-236=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
> -Wl,--start-group src/shared/libsystemd-shared-236.so 
> src/libsystemd-network/libsystemd-network.a -Wl,--end-group 
> '-Wl,-rpath,$ORIGIN/src/shared' 
> -Wl,-rpath-link,/home/helmutg/systemd-236/build-deb/src/shared  
> | /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.90.20180122 assertion fail 
> ../../bfd/elflink.c:9757
> | collect2: error: ld returned 1 exit status
> | [1515/1858] cc  -o test-ipv4ll 
> 'test-ipv4ll@exe/src_libsystemd-network_test-ipv4ll.c.o' -flto 
> -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -pie 
> -Wl,--gc-sections -g -O2 -fdebug-prefix-map=/home/helmutg/systemd-236=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
> -Wl,--start-group src/shared/libsystemd-shared-236.so 
> src/libsystemd-network/libsystemd-network.a -Wl,--end-group 
> '-Wl,-rpath,$ORIGIN/src/shared' 
> -Wl,-rpath-link,/home/helmutg/systemd-236/build-deb/src/shared  
> | FAILED: test-ipv4ll 
> | cc  -o test-ipv4ll 'test-ipv4ll@exe/src_libsystemd-network_test-ipv4ll.c.o' 
> -flto -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -pie 
> -Wl,--gc-sections -g -O2 -fdebug-prefix-map=/home/helmutg/systemd-236=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
> -Wl,--start-group src/shared/libsystemd-shared-236.so 
> src/libsystemd-network/libsystemd-network.a -Wl,--end-group 
> '-Wl,-rpath,$ORIGIN/src/shared' 
> -Wl,-rpath-link,/home/helmutg/systemd-236/build-deb/src/shared  
> | /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.90.20180122 assertion fail 
> ../../bfd/elflink.c:9757
> | collect2: error: ld returned 1 exit status
> | [1516/1858] cc  -o test-dhcp-client 
> 'test-dhcp-client@exe/src_libsystemd-network_test-dhcp-client.c.o' -flto 
> -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -pie 
> -Wl,--gc-sections -g -O2 -fdebug-prefix-map=/home/helmutg/systemd-236=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
> -Wl,--start-group src/shared/libsystemd-shared-236.so 
> src/libsystemd-network/libsystemd-network.a -Wl,--end-group 
> '-Wl,-rpath,$ORIGIN/src/shared' 
> -Wl,-rpath-link,/home/helmutg/systemd-236/build-deb/src/shared  
> | FAILED: test-dhcp-client 
> | cc  -o test-dhcp-client 
> 'test-dhcp-client@exe/src_libsystemd-network_test-dhcp-client.c.o' -flto 
> -Wl,--no-undefined -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -pie 
> -Wl,--gc-sections -g -O2 -fdebug-prefix-map=/home/helmutg/systemd-236=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
> -Wl,--start-group src/shared/libsystemd-shared-236.so 
> src/libsystemd-network/libsystemd-network.a -Wl,--end-group 
> '-Wl,-rpath,$ORIGIN/src/shared' 
> -Wl,-rpath-link,/home/helmutg/systemd-236/build-deb/src/shared  
> | /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.90.20180122 assertion fail 
> ../../bfd/elflink.c:9757
> | /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.90.20180122 assertion fail 
> ../../bfd/elflink.c:9757
> | /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.90.20180122 assertion fail 
> ../../bfd/elflink.c:9757
> | collect2: error: ld returned 1 exit status
> | [1517/1858] cc  -o test-sched-prio 
> 'test-sched-prio@exe/src_test_test-sched-prio.c.o' 
> 'test-sched-prio@exe/src_test_test-helper.c.o' -flto -Wl,--no-undefined 
> -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -pie -Wl,--gc-sections -g -O2 
> -fdebug-prefix-map=/home/helmutg/systemd-236=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wl,-z,relro -Wl,--start-group 
> src/core/libcore.a src/shared/libsystemd-shared-236.a 
> src/shared/libsystemd-shared-236.so -pthread -lrt -lseccomp -lselinux 

Processed: found 888477 in glibc/2.26-1

[Debian Bug Tracking System]

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

> found 888477 glibc/2.26-1
Bug #888477 [src:glibc] glibc FTBFS on arm64: dangerous relocation: unsupported 
relocation
Marked as found in versions glibc/2.26-1.
> thanks
Stopping processing here.

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

Bug#888422: libmpfr6 should add Breaks: libmpfr4

[Julien Cristau]

Ok, I agree about the severity. I would recommend retitling the bug to describe 
the problem (mpfr4 and mpfr6 don't mix) we need to solve rather than prescribe 
a particular resolution though. 

Cheers, 
Julien 

On January 26, 2018 6:55:47 AM GMT+01:00, Adrian Bunk  wrote:
>Control: severity -1 serious
>
>On Thu, Jan 25, 2018 at 09:53:21PM +0200, Adrian Bunk wrote:
>> Control: tags -1 - moreinfo
>> 
>> On Thu, Jan 25, 2018 at 07:39:27PM +0100, Julien Cristau wrote:
>> > Control: severity -1 normal
>> > Control: tag -1 moreinfo
>> > 
>> > On Thu, Jan 25, 2018 at 14:11:49 +0200, Adrian Bunk wrote:
>> > 
>> > > Package: libmpfr6
>> > > Version: 4.0.0-5
>> > > Severity: serious
>> > > 
>> > > Mixing libmpfr4 and libmpfr6 doesn't work well:
>> > > 
>> > > flint-arb FTBFS with:
>> > > /usr/bin/ld: warning: libmpfr.so.4, needed by
>/usr/lib/libflint.so, may conflict with libmpfr.so.6
>> > > /usr/bin/ld: mpfr_free_func: TLS definition in
>//usr/lib/x86_64-linux-gnu/libmpfr.so.4 section .tbss mismatches
>non-TLS definition in
>/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libmpfr.so
>section .text
>> > > //usr/lib/x86_64-linux-gnu/libmpfr.so.4: error adding symbols:
>Bad value
>> > > collect2: error: ld returned 1 exit status
>> > > 
>> > > Some packages like fractalnow FTBFS when gcc and libmpc3 use
>> > > different mpfr libraries, with a gcc ICE:
>> > > ../../src/init2.c:52: MPFR assertion failed: p >= 2 && p <=
>((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))
>> > > src/fractal_compute_engine.c: In function
>'FractalLoopMANDELBROTPINTAVERAGECOLORINGDISCRETECURVATURENONESINGLE':
>> > > src/fractal_compute_engine.c:285:1: internal compiler error:
>Aborted
>> > > 
>> > > It is not even obvious in the latter case that this is always
>only an ICE,
>> > > and not sometimes a miscompilation.
>> > > 
>> > > The libmpc3 issue is also expected to hit users who have older
>gcc versions
>> > > still installed, e.g. gcc-6 still installed after stretch->buster
>upgrade.
>> > > 
>> > > When the dependencies are fulfilled users can expect to have
>working software,
>> > > even a forced removal on stretch->buster upgrades is better than
>runtime problems.
>> > 
>> > Is this actually a problem between libmpfr4 and libmpfr6, or
>libmpfr4
>> > and the new libmpfr-dev?
>> >...
>> 
>> This is a problem between libmpfr4 and libmpfr6.
>> 
>> libmpfr-dev is not installed when gcc ICEs building mathgl.[1,2]
>>...
>
>It is not even obvious that we will always be lucky and get an ICE,
>it is even possible that in some cases gcc might end up silenty
>miscompiling code.
>
>ICE or worse, this would be a problem for anyone still having gcc-6
>or older compiler packages from previous releases installed when 
>upgrading to buster.
>
>And without an RC bug it would already cause problems much earlier for 
>derivates based on testing, since mpfr4 and mpclib3 would currently
>migrate to testing before gcc-7 migrates.
>
>cu
>Adrian
>
>-- 
>
>   "Is there not promise of rain?" Ling Tan asked suddenly out
>of the darkness. There had been need of rain for many days.
>   "Only a promise," Lao Er said.
>   Pearl S. Buck - Dragon Seed

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#888477: glibc FTBFS on arm64: dangerous relocation: unsupported relocation

[Aurelien Jarno]

control: tag -1 + fixed-upstream

On 2018-01-26 08:03, Helmut Grohne wrote:
> Source: glibc
> Version: 2.26-5
> Severity: serious
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> glibc fails to build from source on amd64. Very likely this is not
> caused by the particular glibc upload, but by the binutils upload
> instead. In any case, the build log (attached) ends with:
> 
> | make[4]: Leaving directory '/home/helmutg/glibc-2.26/elf'
> | aarch64-linux-gnu-gcc-7 -no-pie -fno-PIE   -nostdlib -nostartfiles -r -o 
> /home/helmutg/glibc-2.26/build-tree/arm64-libc/elf/librtld.os '-Wl,-(' 
> /home/helmutg/glibc-2.26/build-tree/arm64-libc/elf/dl-allobjs.os 
> /home/helmutg/glibc-2.26/build-tree/arm64-libc/elf/rtld-libc.a -lgcc '-Wl,-)' 
> \
> |   
> -Wl,-Map,/home/helmutg/glibc-2.26/build-tree/arm64-libc/elf/librtld.os.map
> | aarch64-linux-gnu-gcc-7 -no-pie -fno-PIE   -nostdlib -nostartfiles -shared 
> -o /home/helmutg/glibc-2.26/build-tree/arm64-libc/elf/ld.so.new  \
> |   -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both -Wl,-z,defs   
> \
> |   /home/helmutg/glibc-2.26/build-tree/arm64-libc/elf/librtld.os 
> -Wl,--version-script=/home/helmutg/glibc-2.26/build-tree/arm64-libc/ld.map
>   \
> |   -Wl,-soname=ld-linux-aarch64.so.1 \
> |   -Wl,-defsym=_begin=0
> | /usr/bin/ld: /home/helmutg/glibc-2.26/build-tree/arm64-libc/elf/librtld.os: 
> relocation R_AARCH64_ABS32 against `a local symbol' can not be used when 
> making a shared object
> | /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.90.20180122 assertion fail 
> ../../bfd/elfnn-aarch64.c:4386
> | /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.90.20180122 assertion fail 
> ../../bfd/elfnn-aarch64.c:4386
> | /home/helmutg/glibc-2.26/build-tree/arm64-libc/elf/librtld.os: In function 
> `process_envvars':

The bug has already been fixed upstream in the master branch. However I
am waiting the opinion of the patch author before backporting it to the
2.26 branch. See:

  https://sourceware.org/ml/libc-stable/2018-01/msg00053.html

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: Re: Bug#888477: glibc FTBFS on arm64: dangerous relocation: unsupported relocation

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + fixed-upstream
Bug #888477 [src:glibc] glibc FTBFS on arm64: dangerous relocation: unsupported 
relocation
Added tag(s) fixed-upstream.

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