Bug#838596: Re : Bug#838596: libreoffice-gtk3: When installed, LibreOffice is slow

[nicolas . patrois]

Le 22/09/2016 22:18:10, Rene Engelhard a écrit :

> You definitely didn't search enough. You would have seen that this 
> was already reported (and fixed)

> See #837356 and #836531

reportbug did not show me these bugs.
If it had showed them, I wouldn’t have reported the bug.

Regards,
nicolas patrois : pts noir asocial
-- 
RÉALISME

M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des 
humains ? Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...

Bug#829745: kimwitu: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Samuel Henrique]

Control: tags 829745 patch
Control: tags 829745 pending

Hi,

I uploaded a NMU to 7-day/delay queue two days ago
(sorry for not sending this email before). Feel free
to cancel this upload if needed.

The debian/changelog is:
kimwitu (4.6.1-7.2) unstable; urgency=medium

  * Non-maintainer upload.
  [Logan Rosen]
  * Bump DH level to 9 (closes: #829745).
  * debian/rules:
- Remove legacy DH_COMPAT export.
- Add recommended build-arch and build-indep targets.
- Use dh_prep instead of dh_clean -k.
  * debian/control:
- Depend on ${misc:Depends}.
  [Samuel Henrique]
  * Bump Standards-Version to 3.9.8.

I attached a debdiff.

Regards,



Samuel Henrique 


kimwitu.debdiff
Description: Binary data

Processed: Re: kimwitu: FTBFS: dh_clean: Please specify the compatibility level in debian/compat

[Debian Bug Tracking System]

Processing control commands:

> tags 829745 patch
Bug #829745 [src:kimwitu] kimwitu: FTBFS: dh_clean: Please specify the 
compatibility level in debian/compat
Ignoring request to alter tags of bug #829745 to the same tags previously set
> tags 829745 pending
Bug #829745 [src:kimwitu] kimwitu: FTBFS: dh_clean: Please specify the 
compatibility level in debian/compat
Added tag(s) pending.

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

Processed: re: chromium: ::MoveToNewUserNS().

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #838534 [chromium] chromium: ::MoveToNewUserNS().
Severity set to 'important' from 'grave'
> forwarded -1 http://crbug.com/571277
Bug #838534 [chromium] chromium: ::MoveToNewUserNS().
Set Bug forwarded-to-address to 'http://crbug.com/571277'.

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

Bug#838534: chromium: ::MoveToNewUserNS().

[Michael Gilbert]

control: severity -1 important
control: forwarded -1 http://crbug.com/571277

There are a few suggestions in the upstream bug, do any of them help?
Also bug #833342 seems similar.

Best wishes,
Mike

Bug#838418: marked as done (libreoffice-gtk3: Font corruption - both content and dialogs)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 22:49:47 +0200
with message-id <20160922204947.gj17...@rene-engelhard.de>
and subject line Re: Bug#838418: Bug#838549: libreoffice-gtk3: Fails to make 
libreoffice work
has caused the Debian Bug report #838418,
regarding libreoffice-gtk3: Font corruption - both content and dialogs
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.)


-- 
838418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-gtk3
Version: 1:5.2.1-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Upgrade of libreoffice. It was definitely working fine on August 16th,
then I haven't done any upgrades until this last week, so I suspect the
move from 5.2.0 to 5.2.1

   * What exactly did you do (or not do) that was effective (or
ineffective)?

Loaded a spreadsheet, then changed a filter or preference that caused
the display to refresh.

   * What was the outcome of this action?

Cell content was illegible - sometimes just garbarge, sometimes the
characters were replaced with other (random?) characters, sometimes some
characters were emboldened.

Also dialog boxes were corrupted - such as the save/discard/cancel
buttons, and even the text in the input line.

I tried various things - deleting the user profile, running as root,
rolling back to 5.2.1-1, reinstalling fonts, nothing worked other than
uninstalling libreoffice-gtk3.

Its not a driver issue as I get the same problem on Nvidia (nouveau)
desktop and Intel laptop.



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

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

Versions of packages libreoffice-gtk3 depends on:
ii  dpkg  1.18.10
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-3
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.10-1
ii  libdbus-glib-1-2  0.108-1
ii  libgcc1   1:6.2.0-4
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libgl1-mesa-glx [libgl1]  12.0.3-1
ii  libglew2.02.0.0-3
ii  libglib2.0-0  2.49.7-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgtk-3-03.21.6-1
ii  libice6   2:1.0.9-1+b1
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libreoffice-core  1:5.2.1-3
ii  libsm62:1.2.2-1+b1
ii  libstdc++66.2.0-4
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  uno-libs3 5.2.1-3
ii  ure   5.2.1-3

Versions of packages libreoffice-gtk3 recommends:
ii  libreoffice-style-tango  1:5.2.1-3

Versions of packages libreoffice-gtk3 suggests:
ii  libreofficekit-data  1:5.2.1-3

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:5.2.2~rc2-1

Hi,

On Thu, Sep 22, 2016 at 04:44:30PM +0100, Simon John wrote:
> 5.2.2 packages fix the rendering issue for me too.

Thanks. I am uploading it to unstable right now.

> So was it an upstream issue, not packaging?

Yes. Why should it have been a packaging issue? Upstream has Gtk3 in their
source, too. (just not enable in their builds ttbomk due to their old build
baseline), and the new Gtk3 broke stuff..

Regards,

Rene--- End Message ---

Processed: namazu2: FTBFS when built with dpkg-buildpackage -A

[Debian Bug Tracking System]

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

> found 832531 2.0.21-18
Bug #832531 {Done: NOKUBI Takatsugu } [src:namazu2] 
namazu2: FTBFS (No such file or directory)
Marked as found in versions namazu2/2.0.21-18 and reopened.
> thanks
Stopping processing here.

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

Processed: Bug#832531: I can still reproduce it in unstable

[Debian Bug Tracking System]

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

> unarchive 832531
Bug #832531 {Done: NOKUBI Takatsugu } [src:namazu2] 
namazu2: FTBFS (No such file or directory)
Unarchived Bug 832531
>
End of message, stopping processing here.

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

Bug#834928: marked as done (isc-dhcp-client: ifup fails with "Can't bind to dhcp address: Cannot assign, requested address")

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 18:15:59 -0400
with message-id 

Bug#837277: marked as done (erlang-meck: FTBFS: Uncaught error in rebar_core: {'EXIT',)

[Debian Bug Tracking System]

Your message dated Fri, 23 Sep 2016 07:13:46 +0900
with message-id 

and subject line Close bug
has caused the Debian Bug report #837277,
regarding erlang-meck: FTBFS: Uncaught error in rebar_core: {'EXIT',
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.)


-- 
837277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-meck
Version: 0.8.4+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=rebar --with rebar
>dh_testdir -O--buildsystem=rebar
>dh_auto_clean -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Consult config file "/<>/erlang-meck-0.8.4+dfsg/rebar.config"
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{crypto,start,[],[]},
>  {rebar,run_aux,2,
>   [{file,"src/rebar.erl"},{line,212}]},
>  {rebar,main,1,
>   [{file,"src/rebar.erl"},{line,58}]},
>  {escript,run,2,
>   [{file,"escript.erl"},{line,757}]},
>  {escript,start,1,
>   [{file,"escript.erl"},{line,277}]},
>  {init,start_em,1,[]},
>  {init,do_boot,3,[]}]}}
> /usr/share/dh-rebar/make/dh-rebar.Makefile:116: recipe for target 'clean' 
> failed
> make[1]: *** [clean] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/erlang-meck_0.8.4+dfsg-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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

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

Hi,

This bug fixed on rebar version 2.6.4-1.
I close this bug.

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6--- End Message ---

Processed: Re: gnome-python-desktop: FTBFS: autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools".

[Debian Bug Tracking System]

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

> reassign 838592 cdbs
Bug #838592 [src:gnome-python-desktop] gnome-python-desktop: FTBFS: 
autotools.mk:44: *** no python implementation resolved from binary package 
"stamp-autotools".
Bug reassigned from package 'src:gnome-python-desktop' to 'cdbs'.
No longer marked as found in versions gnome-python-desktop/2.32.0+dfsg-3.
Ignoring request to alter fixed versions of bug #838592 to the same values 
previously set
> affects 838592 src:gnome-python-desktop
Bug #838592 [cdbs] gnome-python-desktop: FTBFS: autotools.mk:44: *** no python 
implementation resolved from binary package "stamp-autotools".
Added indication that 838592 affects src:gnome-python-desktop
> forcemerge 837006 838592
Bug #837006 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837018 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837024 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837220 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837239 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837243 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837244 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837248 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837260 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837266 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837270 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837274 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837278 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #838359 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #838592 [cdbs] gnome-python-desktop: FTBFS: autotools.mk:44: *** no python 
implementation resolved from binary package "stamp-autotools".
Removed indication that 838592 affects src:gnome-python-desktop
Added indication that 838592 affects 
sugar-toolkit-gtk3,gnome-python-desktop,python-xklavier,sugar-base-0.88,sugar-datastore-0.88,sugar-presence-service-0.88,sugar-datastore,sugar-toolkit-0.88,sugar-presence-service,gupnp-igd,gamin,sugar-toolkit,sugar-base
Added tag(s) sid and stretch.
Bug #837018 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837024 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837220 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837239 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837243 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837244 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837248 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837260 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837266 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837270 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837274 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837278 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #838359 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Merged 837006 837018 837024 837220 837239 837243 837244 837248 837260 837266 
837270 837274 837278 838359 838592
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
837006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837006
837018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837018
837024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837024

Bug#838592: gnome-python-desktop: FTBFS: autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools".

[Santiago Vila]

reassign 838592 cdbs
affects 838592 src:gnome-python-desktop
forcemerge 837006 838592
thanks

On Thu, 22 Sep 2016, Chris Lamb wrote:

>  /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
> resolved from binary package "stamp-autotools".  Stop.

This is Bug #837006 again (which is a bug in cdbs, not in gnome-python-desktop).

We should really stop filing duplicates and use "affects" instead.

Thanks.

Processed: don't use gold if it doesn't work

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #834147 [src:binutils] binutils: breaks mips and mipsel link of blender
Severity set to 'important' from 'serious'

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

Bug#834147: don't use gold if it doesn't work

[Matthias Klose]

Control: severity -1 important

downgrading, it's not the default linker.

Bug#837286: marked as done (erlang-bitcask: FTBFS: Uncaught error in rebar_core: {'EXIT',)

[Debian Bug Tracking System]

Your message dated Fri, 23 Sep 2016 06:43:22 +0900
with message-id 

and subject line Close bugs
has caused the Debian Bug report #837286,
regarding erlang-bitcask: FTBFS: Uncaught error in rebar_core: {'EXIT',
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.)


-- 
837286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-bitcask
Version: 2.0.2+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/erlang-bitcask-2.0.2+dfsg'
> dh_auto_clean
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Evaluating config script 
> "/<>/erlang-bitcask-2.0.2+dfsg/rebar.config.script"
> DEBUG: Consult config file 
> "/<>/erlang-bitcask-2.0.2+dfsg/rebar.config"
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{crypto,start,[],[]},
>  {rebar,run_aux,2,
>   [{file,"src/rebar.erl"},{line,212}]},
>  {rebar,main,1,
>   [{file,"src/rebar.erl"},{line,58}]},
>  {escript,run,2,
>   [{file,"escript.erl"},{line,757}]},
>  {escript,start,1,
>   [{file,"escript.erl"},{line,277}]},
>  {init,start_em,1,[]},
>  {init,do_boot,3,[]}]}}
> /usr/share/dh-rebar/make/dh-rebar.Makefile:116: recipe for target 'clean' 
> failed
> make[2]: *** [clean] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/09/10/erlang-bitcask_2.0.2+dfsg-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)


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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: src:rebar
Version: 2.6.4-1

Hi,

This bug fixed on rebar version 2.6.4-1.
I close this bug.

Best regards,
  Nobuhiro--- End Message ---

Bug#837275: marked as done (erlang-jiffy: FTBFS: Uncaught error in rebar_core: {'EXIT',)

[Debian Bug Tracking System]

Your message dated Fri, 23 Sep 2016 06:43:22 +0900
with message-id 

and subject line Close bugs
has caused the Debian Bug report #837275,
regarding erlang-jiffy: FTBFS: Uncaught error in rebar_core: {'EXIT',
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.)


-- 
837275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-jiffy
Version: 0.14.6+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/erlang-jiffy-0.14.6+dfsg'
> rm -rf ebin priv
> dh_auto_clean
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Evaluating config script 
> "/<>/erlang-jiffy-0.14.6+dfsg/rebar.config.script"
> DEBUG: Consult config file 
> "/<>/erlang-jiffy-0.14.6+dfsg/rebar.config"
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{crypto,start,[],[]},
>  {rebar,run_aux,2,
>   [{file,"src/rebar.erl"},{line,212}]},
>  {rebar,main,1,
>   [{file,"src/rebar.erl"},{line,58}]},
>  {escript,run,2,
>   [{file,"escript.erl"},{line,757}]},
>  {escript,start,1,
>   [{file,"escript.erl"},{line,277}]},
>  {init,start_em,1,[]},
>  {init,do_boot,3,[]}]}}
> /usr/share/dh-rebar/make/dh-rebar.Makefile:116: recipe for target 'clean' 
> failed
> make[2]: *** [clean] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/erlang-jiffy_0.14.6+dfsg-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: src:rebar
Version: 2.6.4-1

Hi,

This bug fixed on rebar version 2.6.4-1.
I close this bug.

Best regards,
  Nobuhiro--- End Message ---

Bug#837252: marked as done (erlang-folsom: FTBFS: Uncaught error in rebar_core: {'EXIT',)

[Debian Bug Tracking System]

Your message dated Fri, 23 Sep 2016 06:43:22 +0900
with message-id 

and subject line Close bugs
has caused the Debian Bug report #837252,
regarding erlang-folsom: FTBFS: Uncaught error in rebar_core: {'EXIT',
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.)


-- 
837252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-folsom
Version: 0.8.2+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=rebar --with rebar
>dh_testdir -O--buildsystem=rebar
>dh_auto_clean -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Consult config file 
> "/<>/erlang-folsom-0.8.2+dfsg/rebar.config"
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{crypto,start,[],[]},
>  {rebar,run_aux,2,
>   [{file,"src/rebar.erl"},{line,212}]},
>  {rebar,main,1,
>   [{file,"src/rebar.erl"},{line,58}]},
>  {escript,run,2,
>   [{file,"escript.erl"},{line,757}]},
>  {escript,start,1,
>   [{file,"escript.erl"},{line,277}]},
>  {init,start_em,1,[]},
>  {init,do_boot,3,[]}]}}
> /usr/share/dh-rebar/make/dh-rebar.Makefile:116: recipe for target 'clean' 
> failed
> make[1]: *** [clean] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/erlang-folsom_0.8.2+dfsg-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: src:rebar
Version: 2.6.4-1

Hi,

This bug fixed on rebar version 2.6.4-1.
I close this bug.

Best regards,
  Nobuhiro--- End Message ---

Bug#837231: marked as done (erlang-cherly: FTBFS: Uncaught error in rebar_core: {'EXIT',)

[Debian Bug Tracking System]

Your message dated Fri, 23 Sep 2016 06:43:22 +0900
with message-id 

and subject line Close bugs
has caused the Debian Bug report #837231,
regarding erlang-cherly: FTBFS: Uncaught error in rebar_core: {'EXIT',
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.)


-- 
837231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-cherly
Version: 0.12.8+dfsg-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=rebar --with rebar
>dh_testdir -O--buildsystem=rebar
>dh_auto_clean -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Consult config file 
> "/<>/erlang-cherly-0.12.8+dfsg/rebar.config"
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{crypto,start,[],[]},
>  {rebar,run_aux,2,
>   [{file,"src/rebar.erl"},{line,212}]},
>  {rebar,main,1,
>   [{file,"src/rebar.erl"},{line,58}]},
>  {escript,run,2,
>   [{file,"escript.erl"},{line,757}]},
>  {escript,start,1,
>   [{file,"escript.erl"},{line,277}]},
>  {init,start_em,1,[]},
>  {init,do_boot,3,[]}]}}
> /usr/share/dh-rebar/make/dh-rebar.Makefile:116: recipe for target 'clean' 
> failed
> make[1]: *** [clean] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/09/10/erlang-cherly_0.12.8+dfsg-5_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: src:rebar
Version: 2.6.4-1

Hi,

This bug fixed on rebar version 2.6.4-1.
I close this bug.

Best regards,
  Nobuhiro--- End Message ---

Bug#837283: marked as done (erlang-cuttlefish: FTBFS: Uncaught error in rebar_core: {'EXIT',)

[Debian Bug Tracking System]

Your message dated Fri, 23 Sep 2016 06:43:22 +0900
with message-id 

and subject line Close bugs
has caused the Debian Bug report #837283,
regarding erlang-cuttlefish: FTBFS: Uncaught error in rebar_core: {'EXIT',
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.)


-- 
837283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-cuttlefish
Version: 2.0.7+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/erlang-cuttlefish-2.0.7+dfsg'
> dh_auto_clean
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Consult config file 
> "/<>/erlang-cuttlefish-2.0.7+dfsg/rebar.config"
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{crypto,start,[],[]},
>  {rebar,run_aux,2,
>   [{file,"src/rebar.erl"},{line,212}]},
>  {rebar,main,1,
>   [{file,"src/rebar.erl"},{line,58}]},
>  {escript,run,2,
>   [{file,"escript.erl"},{line,757}]},
>  {escript,start,1,
>   [{file,"escript.erl"},{line,277}]},
>  {init,start_em,1,[]},
>  {init,do_boot,3,[]}]}}
> /usr/share/dh-rebar/make/dh-rebar.Makefile:116: recipe for target 'clean' 
> failed
> make[2]: *** [clean] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/09/10/erlang-cuttlefish_2.0.7+dfsg-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: src:rebar
Version: 2.6.4-1

Hi,

This bug fixed on rebar version 2.6.4-1.
I close this bug.

Best regards,
  Nobuhiro--- End Message ---

Bug#837227: marked as done (neotoma: FTBFS: Uncaught error in rebar_core: {'EXIT',)

[Debian Bug Tracking System]

Your message dated Fri, 23 Sep 2016 06:43:22 +0900
with message-id 

and subject line Close bugs
has caused the Debian Bug report #837227,
regarding neotoma: FTBFS: Uncaught error in rebar_core: {'EXIT',
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.)


-- 
837227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: neotoma
Version: 1.7.3+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=rebar --with rebar
>dh_testdir -O--buildsystem=rebar
>dh_auto_clean -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Consult config file "/<>/neotoma-1.7.3+dfsg/rebar.config"
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{crypto,start,[],[]},
>  {rebar,run_aux,2,
>   [{file,"src/rebar.erl"},{line,212}]},
>  {rebar,main,1,
>   [{file,"src/rebar.erl"},{line,58}]},
>  {escript,run,2,
>   [{file,"escript.erl"},{line,757}]},
>  {escript,start,1,
>   [{file,"escript.erl"},{line,277}]},
>  {init,start_em,1,[]},
>  {init,do_boot,3,[]}]}}
> /usr/share/dh-rebar/make/dh-rebar.Makefile:116: recipe for target 'clean' 
> failed
> make[1]: *** [clean] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/neotoma_1.7.3+dfsg-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: src:rebar
Version: 2.6.4-1

Hi,

This bug fixed on rebar version 2.6.4-1.
I close this bug.

Best regards,
  Nobuhiro--- End Message ---

Bug#837250: marked as done (erlang-bear: FTBFS: Uncaught error in rebar_core: {'EXIT',)

[Debian Bug Tracking System]

Your message dated Fri, 23 Sep 2016 06:43:22 +0900
with message-id 

and subject line Close bugs
has caused the Debian Bug report #837250,
regarding erlang-bear: FTBFS: Uncaught error in rebar_core: {'EXIT',
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.)


-- 
837250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-bear
Version: 0.8.2+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=rebar --with rebar
>dh_testdir -O--buildsystem=rebar
>dh_auto_clean -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Consult config file "/<>/erlang-bear-0.8.2+dfsg/rebar.config"
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{crypto,start,[],[]},
>  {rebar,run_aux,2,
>   [{file,"src/rebar.erl"},{line,212}]},
>  {rebar,main,1,
>   [{file,"src/rebar.erl"},{line,58}]},
>  {escript,run,2,
>   [{file,"escript.erl"},{line,757}]},
>  {escript,start,1,
>   [{file,"escript.erl"},{line,277}]},
>  {init,start_em,1,[]},
>  {init,do_boot,3,[]}]}}
> /usr/share/dh-rebar/make/dh-rebar.Makefile:116: recipe for target 'clean' 
> failed
> make[1]: *** [clean] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/erlang-bear_0.8.2+dfsg-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: src:rebar
Version: 2.6.4-1

Hi,

This bug fixed on rebar version 2.6.4-1.
I close this bug.

Best regards,
  Nobuhiro--- End Message ---

Bug#837259: marked as done (erlang-getopt: FTBFS: Uncaught error in rebar_core: {'EXIT',)

[Debian Bug Tracking System]

Your message dated Fri, 23 Sep 2016 06:43:22 +0900
with message-id 

and subject line Close bugs
has caused the Debian Bug report #837259,
regarding erlang-getopt: FTBFS: Uncaught error in rebar_core: {'EXIT',
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.)


-- 
837259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-getopt
Version: 0.8.2+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=rebar --with rebar
>dh_testdir -O--buildsystem=rebar
>dh_auto_clean -O--buildsystem=rebar
>   make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile 
> clean
> clean
> rebar clean skip_deps=true -vv
> DEBUG: Consult config file 
> "/<>/erlang-getopt-0.8.2+dfsg/rebar.config"
> Uncaught error in rebar_core: {'EXIT',
>{undef,
> [{crypto,start,[],[]},
>  {rebar,run_aux,2,
>   [{file,"src/rebar.erl"},{line,212}]},
>  {rebar,main,1,
>   [{file,"src/rebar.erl"},{line,58}]},
>  {escript,run,2,
>   [{file,"escript.erl"},{line,757}]},
>  {escript,start,1,
>   [{file,"escript.erl"},{line,277}]},
>  {init,start_em,1,[]},
>  {init,do_boot,3,[]}]}}
> /usr/share/dh-rebar/make/dh-rebar.Makefile:116: recipe for target 'clean' 
> failed
> make[1]: *** [clean] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/erlang-getopt_0.8.2+dfsg-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: src:rebar
Version: 2.6.4-1

Hi,

This bug fixed on rebar version 2.6.4-1.
I close this bug.

Best regards,
  Nobuhiro--- End Message ---

Bug#837230: marked as done (erlang-cowlib: FTBFS: src/cow_multipart.erl:427: crypto:rand_bytes/1 is deprecated and will be removed in a future release; use crypto:strong_rand_bytes/1)

[Debian Bug Tracking System]

Your message dated Fri, 23 Sep 2016 06:43:22 +0900
with message-id 

and subject line Close bugs
has caused the Debian Bug report #837230,
regarding erlang-cowlib: FTBFS: src/cow_multipart.erl:427: crypto:rand_bytes/1 
is deprecated and will be removed in a future release; use 
crypto:strong_rand_bytes/1
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.)


-- 
837230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-cowlib
Version: 1.3.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_auto_configure
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> dh_auto_build
>   make -j1
> make[2]: Entering directory '/<>'
>  ERLC   cow_multipart.erl cow_http_hd.erl cow_ws.erl cow_http.erl 
> cow_spdy.erl cow_cookie.erl cow_mimetypes.erl cow_http_te.erl cow_qs.erl 
> cow_date.erl
> compile: warnings being treated as errors
> src/cow_multipart.erl:427: crypto:rand_bytes/1 is deprecated and will be 
> removed in a future release; use crypto:strong_rand_bytes/1
> erlang.mk:359: recipe for target 'ebin/cowlib.app' failed
> make[3]: *** [ebin/cowlib.app] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/erlang-cowlib_1.3.0-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: src:rebar
Version: 2.6.4-1

Hi,

This bug fixed on rebar version 2.6.4-1.
I close this bug.

Best regards,
  Nobuhiro--- End Message ---

Bug#838551: mediawiki: Update breaks mediawiki-extensions, leaving unusable system

[Kunal Mehta]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

On 09/22/2016 01:06 AM, Thomas Erichsen wrote:
> Today I installed a pending upgrade for mediawiki, leaving my
> system in a complete mess: obviously, the upgrade breaks
> mediawiki-extensions, from which I used several and specifically
> the Ldap-authentication. I understand, that the former extensions
> are now partly included in the mediawiki package, right? Shouldn't
> there be a note how to configure the system to work again after
> breaking it by this upgrade?

Sorry to hear about that :(

I've updated  to note that the
mediawiki-extensions* packages are no longer supported. You should
download a more modern version of the extension from mediawiki.org.

The extensions which are bundled with the upstream tarball are
included in the "mediawiki" package itself.

Is there anywhere else you'd expect a note to let you know how to
upgrade/migrate?

- -- Kunal
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQI0BAEBCgAeBQJX5DwiFxxsZWdva3RtQG1lbWJlci5mc2Yub3JnAAoJEFL8jnvt
t/yiRL8P/0uL2Lh2Vd/aO4ZM0WnuY1SJApXrM9F6HHBQgcgyj9vQIWbF+5P4v1At
1TGZcVkFWb5cT4/EkMgsGBhOK20zfmnZptpauOUNm0lWuc1+KggXyqCTSOTTUejM
1H4XCMQRXibMarYAOZ1Ki41geuhFJLCYwx8V3QfmoJTmbFZ4JW/SD1pJf13Uld4L
dzg+66iHRQx4BpLEX28OebE6QiD2lalC7/JjMSXYkFs4J3ef4SDrYzzIXfGyb02l
yJUfMW//yHZPqoEmNS026cesT9kD47BgJm9lbETN18JX4GJUHsR51hWdNwWw4ZOL
4qQxL8eRT5VF4SWhgW/yOzgp5ETGg+U3CUkrnKmmU4DWYD/vCCur6C3e5By6Ibso
AFDq6cViPSm1VTTSyYXlPGQ9J4Js5Jk/atRW7orIUNbAmcqU3HsL56uUeOI+pJlU
U5KathWboYBJAP+L64hJyCdW/yGsfiUMDnqUEXbUfCGgUXmP/aEDN6axQp5P0sos
C+mUK14WwxS2oNq84K6yvGfN3qPNcV9CcvGSff2bQgE+1mRTk0g2EXCcU+z6BPJI
+SjCZh5lEqfr2HesPsop+vH/mr5W8QA9aRCVDA3nZ7aNWxXAZcnhN8qi1LLXD4gD
EWtp9d+RiY+KwHeV5xEgitkjMsniaN0ttvQdHXqkxAsT7lG8W3BA
=0arX
-END PGP SIGNATURE-

Processed: Re: Bug#838596: libreoffice-gtk3: When installed, LibreOffice is slow

[Debian Bug Tracking System]

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

> severity 838596 grave
Bug #838596 [libreoffice-gtk3] libreoffice-gtk3: When installed, LibreOffice is 
slow
Severity set to 'grave' from 'important'
> forcemerge 837356 838596
Bug #837356 {Done: Rene Engelhard } [libreoffice-gtk3] 
LibreOffice unusably slow on GNOME 3 with libreoffice-gtk3 installed with Gtk 
3.21
Bug #838002 {Done: Rene Engelhard } [libreoffice-gtk3] 
Libreoffice-writer formatting dialogs take too long to open
Bug #838596 [libreoffice-gtk3] libreoffice-gtk3: When installed, LibreOffice is 
slow
Set Bug forwarded-to-address to 'caol...@redhat.com'.
Marked Bug as done
Marked as fixed in versions libreoffice/1:5.2.1-3.
Marked as found in versions libreoffice/1:5.2.1-2.
Added tag(s) patch, fixed-upstream, and upstream.
Bug #838002 {Done: Rene Engelhard } [libreoffice-gtk3] 
Libreoffice-writer formatting dialogs take too long to open
Merged 837356 838002 838596
> thanks
Stopping processing here.

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

Bug#838594: [Pkg-utopia-maintainers] Bug#838594: network-manager: FTBFS: ERROR:test-crypto.c:243:test_load_pkcs8: assertion failed: (nm_utils_file_is_private_key (path, NULL))

[Michael Biebl]

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=771623

Am 2016-09-22 19:24, schrieb Chris Lamb:

  # ERROR:test-crypto.c:243:test_load_pkcs8: assertion failed:


Hi Chris,

thanks for the bug report. It's a known issue caused by the recent 
GnuTLS update.

I've already filed this issue upstream a couple of days ago.
Marking accordingly.

Michael

Processed: Re: [Pkg-utopia-maintainers] Bug#838594: network-manager: FTBFS: ERROR:test-crypto.c:243:test_load_pkcs8: assertion failed: (nm_utils_file_is_private_key (path, NULL))

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=771623
Bug #838594 [src:network-manager] network-manager: FTBFS: 
ERROR:test-crypto.c:243:test_load_pkcs8: assertion failed: 
(nm_utils_file_is_private_key (path, NULL))
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=771623'.

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

Bug#836664: wsjtx: please drop the build dependency on hardening-wrapper

[Moritz Muehlenhoff]

tags 836664 patch
thanks

On Sun, Sep 04, 2016 at 01:17:05PM +, Matthias Klose wrote:
> Package: wsjtx
> Version: 1.1.r3496-3
> Severity: important
> Tags: sid stretch
> User: debian-...@lists.debian.org
> Usertags: hardening-wrapper
> 
> This package builds using the hardening-wrapper package, which
> is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.
> 
> Please consider dropping the build dependency of hardening-wrapper
> and use the DEB_BUILD_MAINT_OPTIONS settings.
> 
> The goal is to remove hardening-wrapper for the stretch release.
> Discussion about the removal is tracked in https://bugs.debian.org/836162
> 
> The severity of this report is likely to be raised before the release,
> so that the hardening-wrapper package can be removed for the release.

Patch attached. I've verified that it uses the same hardening flags.

Cheers,
Moritz 
diff -aur wsjtx-1.1.r3496.orig/debian/control wsjtx-1.1.r3496/debian/control
--- wsjtx-1.1.r3496.orig/debian/control	2013-09-04 00:45:49.0 +0200
+++ wsjtx-1.1.r3496/debian/control	2016-09-22 00:35:44.255965990 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Hams group 
 Uploaders: John T. Nogatch , Kamal Mostafa 
-Build-Depends: debhelper (>= 8.0.0), qt4-dev-tools, qt4-qmake, libqt4-dev, gfortran, hardening-wrapper, libfftw3-dev, libhamlib-dev, libqwt5-qt4-dev, libsamplerate0-dev, portaudio19-dev (>= 19+svn2021-1~) 
+Build-Depends: debhelper (>= 8.0.0), qt4-dev-tools, qt4-qmake, libqt4-dev, gfortran, libfftw3-dev, libhamlib-dev, libqwt5-qt4-dev, libsamplerate0-dev, portaudio19-dev (>= 19+svn2021-1~) 
 Standards-Version: 3.9.4
 Homepage: http://www.physics.princeton.edu/pulsar/K1JT/wsjtx.html
 #Vcs-Git: git://git.debian.org/collab-maint/wsjt.git
diff -aur wsjtx-1.1.r3496.orig/debian/rules wsjtx-1.1.r3496/debian/rules
--- wsjtx-1.1.r3496.orig/debian/rules	2013-07-22 18:59:55.0 +0200
+++ wsjtx-1.1.r3496/debian/rules	2016-09-22 00:38:29.316744521 +0200
@@ -16,15 +16,8 @@
 # This has to be exported to make some magic below work.
 export DH_OPTIONS
 
-# enable hardening-wrapper
-export DEB_BUILD_HARDENING=1
-export DEB_BUILD_HARDENING_FORMAT=1
-export DEB_BUILD_HARDENING_FORTIFY=1
-export DEB_BUILD_HARDENING_STACKPROTECTOR=1
-# PIE causes wsjtx to seg fault immediately
-export DEB_BUILD_HARDENING_PIE=0
-export DEB_BUILD_HARDENING_RELRO=1
-export DEB_BUILD_HARDENING_BINDNOW=1
+export DEB_BUILD_MAINT_OPTIONS= hardening=+relro,+bindnow
+# Don't use PIE, causes wsjtx to seg fault immediately
 
 override_dh_auto_configure:
 	echo "running debian/rules/override_dh_auto_configure"
diff -aur wsjtx-1.1.r3496.orig/lib/Makefile.linux wsjtx-1.1.r3496/lib/Makefile.linux
--- wsjtx-1.1.r3496.orig/lib/Makefile.linux	2016-09-22 14:33:50.0 +0200
+++ wsjtx-1.1.r3496/lib/Makefile.linux	2016-09-22 00:25:24.573388316 +0200
@@ -2,7 +2,7 @@
 FC = gfortran
 
 FFLAGS = -O2 -fbounds-check -Wall -Wno-conversion -fno-second-underscore
-CFLAGS = -I. -fbounds-check
+CFLAGS = -I. -fbounds-check `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS`
 
 # Default rules
 %.o: %.c
@@ -44,7 +44,7 @@
 OBJS2 = jt9.o jt9a.o jt9b.o jt9c.o
 
 jt9: 	$(OBJS2) libjt9.a 
-	g++ -o jt9 $(OBJS2) libjt9.a -lfftw3f -lgfortran -lQtCore
+	g++ -o jt9 $(OBJS2) libjt9.a -lfftw3f -lgfortran -lQtCore `dpkg-buildflags --get LDFLAGS`
 	cp jt9 ../wsjtx_install
 
 OBJS3 = jt9sim.o 

Processed: Re: wsjtx: please drop the build dependency on hardening-wrapper

[Debian Bug Tracking System]

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

> tags 836664 patch
Bug #836664 [wsjtx] wsjtx: please drop the build dependency on hardening-wrapper
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#836677: pysparse: still worth maintaining?

[Anton Gladky]

Hi Ghis,

thanks for working on the package! Even it is abandoned by
upstream, we have to support it in Debian, because it has
reverse-dependency.

Feel free to ping me, if one need the package sponsoring.

Best regards

Anton


2016-09-22 9:33 GMT+02:00 Ghislain Vaillant :
> I have had a look at updating the package to the newest upstream
> release and fixing this FTBFS. However, I have got strong concerns as
> to whether it is worth keeping this package maintained in the archive:
>
> - The latest release on PyPI [1] is busted (missing files). The issue
> was reported [2] but never addressed since.
>
> - Latest activity on the upstream repository is from 2013. By now, I
> expected upstream would have fixed the PyPI tarball, at least.
>
> - No Python 3 support. A manual call to 2to3 on the Python sources
> allows the build process to run, but fails at the compilation stage.
>
> [1] https://pypi.python.org/pypi/pysparse
> [2] https://sourceforge.net/p/pysparse/mailman/message/33117282/
>
> Best regards,
> Ghis

Processed: Re: Bug#838394: openbabel: FTBFS on mips,mips64el: internal compiler errors

[Debian Bug Tracking System]

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

> tag 838394 unreproducible
Bug #838394 [openbabel] openbabel: FTBFS on mips,mips64el: internal compiler 
errors
Added tag(s) unreproducible.
> close 838394
Bug #838394 [openbabel] openbabel: FTBFS on mips,mips64el: internal compiler 
errors
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#838394: openbabel: FTBFS on mips,mips64el: internal compiler errors

[Niko Tyni]

tag 838394 unreproducible
close 838394
thanks

On Thu, Sep 22, 2016 at 04:32:34PM +0200, gregor herrmann wrote:
> On Thu, 22 Sep 2016 10:59:13 +0200, Julien Cristau wrote:
> 
> > On Thu, Sep 22, 2016 at 10:34:29 +0300, Niko Tyni wrote:
> > > @debian-wb-team: could you please give it back to see if it happens
> > > again on buildds?
> > >  gb openbabel_2.3.2+dfsg-2.4 . mips mips64el
> > Given back.
> 
> Thanks!
> And it built everywhere:
> https://buildd.debian.org/status/logs.php?pkg=openbabel=2.3.2%2Bdfsg-2.4

Good.
 
> I guess we can close this bug?
> Unless Niko would like to keep track of the issues he discovered, of
> course.

Didn't discover much as the issues were unreproducible. Closing for now.
-- 
Niko Tyni   nt...@debian.org

Bug#838516: FTBFS: conflicts between build dependencies

[Joachim Reichel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Removing libglew-dev from Build-Depends seems to work (in the sense that I did
not spot any related build errors), but I have no idea whether this is the
correct solution.

However, the build does not complete because of

/tmp/k3d-0.8.0.5/k3dsdk/ngui/utility.cpp: In function ‘void
k3d::ngui::non_blocking_sleep(double)’:
/tmp/k3d-0.8.0.5/k3dsdk/ngui/utility.cpp:63:2: error: ‘signal_timeout’ is not
a member of ‘Glib’
  Glib::signal_timeout().connect(

which can be fixed by adding "#include ".

Joachim

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJX5BuPAAoJELj6/xxDiGdxB/wP/0U2C73NtPyJFViMXQPRwm0h
0c+p18stcTnNlQk1vuZocPADKPHHTaSdD+7xTxMRIqK3BsIhrGehPdA7WzJ/DcAj
zHsSDTaPOM+L+4tBp7M5tLZTWGEBXL+4jk3flU70XW4R0+W4ivj+bkf1kZs4f9WX
w+bEpOWfp/8qNRy7SXzys5lFVJ4yRget2JnlXHukOAh8Y4wW525XB2pnZZ8Wr48F
ynQZuuLTarZH67dVEoT9nRXHG/cJUS5Y7/4gdh8Jc+K9KorFG11ugRMy6hFHpXZh
wfGvqXkHhFAjF+7VwYcS2oS7neSaDIJ57RBeKnIXeqsaESe+7VzmQga7woGOYGIb
OW16Ua43vOFb3a8BysH7+dg4FFcBu6wR6I+AgJyOG1zw95QcyH7Her4x1pQJ4YPd
VvmotJW+x4Z6p5ORdF1NyzELTGrm7Xxnea+zfZR+PxxQgRkJpSiu5sVx8fYtYTn5
+3ySHKhr+VqDjgWtac8HJV4SbU8uBPoUiqNQJS16ick7w3T0QLKSmWgTkr0HPz/I
hlLmPl3+2fQ1ZdgmMSZcOytICVfkl98rt7aDPBAK/INerLs7WdbOIwQSunxQ0Pri
M33KLPnT37oYthsu7U3vOYTAJdrYmAmenWUada/bTp/+R9bB48vJntdx3I3h399G
wTG+QmLQNPbqv0APynxb
=DPXf
-END PGP SIGNATURE-

Bug#838593: marked as done (easytag: FTBFS: dh_install: Cannot find (any matches for) "usr/lib/nautilus/*/*.so" (tried in "." and "debian/tmp"))

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 18:52:02 +0100
with message-id 
and subject line Re: Bug#838593: easytag: FTBFS: dh_install: Cannot find (any 
matches for) "usr/lib/nautilus/*/*.so" (tried in "." and "debian/tmp")
has caused the Debian Bug report #838593,
regarding easytag: FTBFS: dh_install: Cannot find (any matches for) 
"usr/lib/nautilus/*/*.so" (tried in "." and "debian/tmp")
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.)


-- 
838593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: easytag
Version: 2.4.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

easytag fails to build from source in unstable/amd64:

  [..]

  /usr/bin/install -c -m 644 C/legal.xml 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/legal.xml
  /usr/bin/install -c -m 644 C/playlist-generate.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/playlist-generate.page
  /usr/bin/install -c -m 644 C/problems-id3.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/problems-id3.page
  /usr/bin/install -c -m 644 C/problems-ogg-split.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/problems-ogg-split.page
  /usr/bin/install -c -m 644 C/scanner.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/scanner.page
  /usr/bin/install -c -m 644 C/starting.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/starting.page
  /usr/bin/install -c -m 644 C/tag-capitalization.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/tag-capitalization.page
  /usr/bin/install -c -m 644 C/tag-field.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/tag-field.page
  /usr/bin/install -c -m 644 C/tag.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/tag.page
  /usr/bin/install -c -m 644 ca/cddb-search.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/cddb-search.page
  /usr/bin/install -c -m 644 ca/file-rename.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/file-rename.page
  /usr/bin/install -c -m 644 ca/file-select.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/file-select.page
  /usr/bin/install -c -m 644 ca/format-specifier.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/format-specifier.page
  /usr/bin/install -c -m 644 ca/image-delete.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/image-delete.page
  /usr/bin/install -c -m 644 ca/image-export.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/image-export.page
  /usr/bin/install -c -m 644 ca/image.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/image.page
  /usr/bin/install -c -m 644 ca/index.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/index.page
  /usr/bin/install -c -m 644 ca/introduction.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/introduction.page
  /usr/bin/install -c -m 644 ca/keyboard-shortcuts.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/keyboard-shortcuts.page
  /usr/bin/install -c -m 644 ca/legal.xml 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/legal.xml
  /usr/bin/install -c -m 644 ca/playlist-generate.page 

Bug#835678: marked as done (yosys: FTBFS: latex errors)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 17:55:45 +
with message-id 
and subject line Bug#835678: fixed in yosys 0.6-7
has caused the Debian Bug report #835678,
regarding yosys: FTBFS: latex errors
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.)


-- 
835678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yosys
Version: 0.6-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> [Makefile.conf] CONFIG := gcc
> 
>   Build successful.
> 
> cd manual && bash appnotes.sh
> + for job in APPNOTE_010_Verilog_to_BLIF APPNOTE_011_Design_Investigation 
> APPNOTE_012_Verilog_to_BTOR
> + '[' -f APPNOTE_010_Verilog_to_BLIF.ok -a APPNOTE_010_Verilog_to_BLIF.ok -nt 
> APPNOTE_010_Verilog_to_BLIF.tex ']'
> + '[' -f APPNOTE_010_Verilog_to_BLIF/make.sh ']'
> ++ '[' -f APPNOTE_010_Verilog_to_BLIF.aux ']'
> ++ true
> + old_md5=
> + pdflatex -shell-escape -halt-on-error APPNOTE_010_Verilog_to_BLIF.tex
> This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) 
> (preloaded format=pdflatex)
>  \write18 enabled.
> entering extended mode
> (./APPNOTE_010_Verilog_to_BLIF.tex
> LaTeX2e <2016/03/31> patch level 3
> Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/IEEEtran/IEEEtran.cls
> Document Class: IEEEtran 2015/08/26 V1.8b by Michael Shell
> -- See the "IEEEtran_HOWTO" manual for usage information.
> -- http://www.michaelshell.org/tex/ieeetran/
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/ot1ptm.fd)
> -- Using 210mm x 297mm (a4) paper.
> -- Using PDF output.
> -- This is a 9 point document.
> ) (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ptm.fd))
> (/usr/share/texlive/texmf-dist/tex/latex/libertine/libertine.sty
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty
> (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex
> (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex
> (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/keyval.tex
> (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def))
> (/usr/share/texlive/texmf-dist/tex/latex/mweights/mweights.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/fontaxes/fontaxes.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/libertine/LinLibertine_I.tex))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/puenc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
> 
> Package hyperref Message: Driver (autodetected): hpdftex.
> 
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/utf8.def
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.dfu)
> (/usr/share/texlive/texmf-dist/tex/latex/base/ot1enc.dfu)
> (/usr/share/texlive/texmf-dist/tex/latex/base/omsenc.dfu)
> (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.dfu)))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> 

Bug#838516: FTBFS: conflicts between build dependencies

[Manuel A. Fernandez Montecelo]

2016-09-22 3:26 GMT+02:00 Paul Wise :
> On Wed, 2016-09-21 at 21:38 +0200, Joachim Reichel wrote:
>
>> Build-Depends: [...] libglew-dev, libglewmx-dev, [...]
>
> Why does it build-depend against both variants?
>
>> but libglewmx-dev 1.13.0-3 has
>>
>> Conflicts: libglew-dev
>
> The background here is that glew 2.0.0 removed MX support but things
> like quesoglc and chromium-browser use the MX variant so I uploaded the
> old version of glew as glewmx and dropped the non-MX variants of it.
>
> There are a few possibilities here:
>
> The k3d maintainer can try to figure out the reason for it using both
> variants and switch to just one of them if possible.

Yep, I will try to do that in the next few days.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Processed: [bts-link] source package hhvm

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package hhvm
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #812023 (http://bugs.debian.org/812023)
> # Bug title: hhvm: FTBFS with GCC 6: flexible array member...
> #  * https://github.com/facebook/hhvm/issues/6933
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 812023 + fixed-upstream
Bug #812023 [hhvm] hhvm: FTBFS with GCC 6: flexible array member...
Added tag(s) fixed-upstream.
> usertags 812023 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 812023 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#838586: roxterm false on start up segfault

[Tony Houghton]

I've discontinued roxterm because the amount of work needed to fix 
outstanding bugs and continue to maintain it was more than it was worth. 
gnome-terminal is pretty good these days, and there are other terminals.


This bug looks like it's caused by an ABI change in VTE, which you would 
need roxterm version 3 for, but there was also another nasty 
incompatibility with GTK 3.20, hence its removal from Debian.


If you really badly want to keep using roxterm and don't mind missing 
some features you could try roxterm-gtk2.


--
TH

Bug#838594: network-manager: FTBFS: ERROR:test-crypto.c:243:test_load_pkcs8: assertion failed: (nm_utils_file_is_private_key (path, NULL))

[Chris Lamb]

Source: network-manager
Version: 1.4.0-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

network-manager fails to build from source in unstable/amd64:

  [..]

  mkhtml_options=""; \
  gtkdoc-mkhtml 2>&1 --help | grep  >/dev/null "\-\-verbose"; \
  if test "$?" = "0"; then \
if test "x" = "x1"; then \
  mkhtml_options="$mkhtml_options --verbose"; \
fi; \
  fi; \
  gtkdoc-mkhtml 2>&1 --help | grep  >/dev/null "\-\-path"; \
  if test "$?" = "0"; then \
mkhtml_options="$mkhtml_options 
--path=\"/home/lamby/temp/cdt.20160922191524.YuLDocelz6.db.network-manager/network-manager-1.4.0/docs/libnm-glib\"";
 \
  fi; \
  cd html && gtkdoc-mkhtml $mkhtml_options  libnm-glib ../libnm-glib-docs.xml
  gtkdoc-fixxref --module=libnm-glib --module-dir=html 
--html-dir=/usr/share/gtk-doc/html 
  html/NMDeviceTeam.html:107: warning: no link for: 'NMObjectArray' -> (NMObjectArray).
  html/NMDeviceTeam.html:167: warning: no link for: 'api-index-0.9.10' -> 
(0.9.10).
  html/NMDeviceTeam.html:173: warning: no link for: 'DBusGConnection' -> (DBusGConnection).
  html/NMDeviceTeam.html:285: warning: no link for: 'NMDevices' -> (NMDevices).
  html/NMDeviceBt.html:279: warning: no link for: 'NMBluetoothCapabilities' -> 
(NMBluetoothCapabilities).
  html/libnm-glib-NMVpnPluginUiWidget.html:265: warning: no link for: 
'NMConnection' -> (NMConnection).
  html/NMIP4Config.html:120: warning: no link for: 'NMStringArray' -> (NMStringArray).
  html/NMIP4Config.html:132: warning: no link for: 'NMUintArray' -> (NMUintArray).
  html/NMIP4Config.html:291: warning: no link for: 'NMIP4Address' -> (NMIP4Address).
  html/NMIP4Config.html:320: warning: no link for: 'NMIP4Routes' -> (NMIP4Routes).
  html/NMIP4Config.html:520: warning: no link for: 'NMSettingIP4Routes' -> 
(NMSettingIP4Routes).
  html/NMDevice.html:491: warning: no link for: 'GValueArray-guint+guint-*' -> 
(GValueArray_guint+guint_*).
  html/NMDevice.html:1041: warning: no link for: 'api-index-1.2' -> (1.2).
  html/NMDevice.html:1280: warning: no link for: 'NMDeviceStateReason' -> 
(NMDeviceStateReason).
  html/NMDevice.html:1344: warning: no link for: 'NMRemoteConnections' -> 
(NMRemoteConnections).
  html/NMDevice.html:1369: warning: no link for: 'api-index-0.9.8' -> (0.9.8).
  html/NMDevice.html:1456: warning: no link for: 'api-index-1.0' -> (1.0).
  html/NMDevice.html:1847: warning: no link for: 'NMSetting' -> (NMSetting).
  html/NMActiveConnection.html:658: warning: no link for: 
'NM-ACTIVE-CONNECTION-STATE-ACTIVATED:CAPS' -> (NM_ACTIVE_CONNECTION_STATE_ACTIVATED).
  html/NMDeviceWifi.html:540: warning: no link for: 'NMAccessPoints' -> (NMAccessPoints).
  html/NMAccessPoint.html:209: warning: no link for: 'NMSsid' -> (NMSsid).
  html/NMIP6Config.html:123: warning: no link for: 'NMIP6AddressObjectArray' -> 
(NMIP6AddressObjectArray).
  html/NMIP6Config.html:141: warning: no link for: 'NMIP6AddressArray' -> 
(NMIP6AddressArray).
  html/NMIP6Config.html:147: warning: no link for: 'NMIP6RouteObjectArray' -> 
(NMIP6RouteObjectArray).
  html/NMIP6Config.html:292: warning: no link for: 'NMIP6Address' -> (NMIP6Address).
  html/NMIP6Config.html:321: warning: no link for: 'NMIP6Routes' -> (NMIP6Routes).
  html/NMIP6Config.html:522: warning: no link for: 
'nm-utils-ip6-addresses-from-gvalue' -> (nm_utils_ip6_addresses_from_gvalue()).
  html/NMIP6Config.html:523: warning: no link for: 'NMSettingIP6Address' -> 
(NMSettingIP6Address).
  html/NMIP6Config.html:555: warning: no link for: 
'nm-utils-ip6-routes-from-gvalue' -> (nm_utils_ip6_routes_from_gvalue()).
  html/NMClient.html:751: warning: no link for: 'NM-IS-DEVICE-:CAPS' -> 
(NM_IS_DEVICE_()).
  html/NMClient.html:1402: warning: no link for: 'NMState' -> (NMState).
  html/NMClient.html:1483: warning: no link for: 'NMActiveConnections' -> 
(NMActiveConnections).
  html/NMClient.html:1677: warning: no link for: 'api-index-0.9.8.6' -> 
(0.9.8.6).
  html/NMDeviceWimax.html:457: warning: no link for: 'NMWimaxNsps' -> (NMWimaxNsps).
  html/NMDeviceBond.html:286: warning: no link for: 'api-index-0.9.6.4' -> 
(0.9.6.4).
  html/libnm-glib-NMVPNPlugin.html:183: warning: no link for: 
'NMVPNServiceState' -> (NMVPNServiceState).
  html/libnm-glib-NMVPNPlugin.html:238: warning: no link for: 
'NMVPNPluginFailure' -> (NMVPNPluginFailure).
  html/NMSecretAgent.html:914: warning: no link for: 'a-z' -> (A-Z).
  html/libnm-glib-nm-vpn-plugin-utils.html:114: warning: no link for: 
'NMSettingSecretFlags' -> (NMSettingSecretFlags).
  touch html-build.stamp
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160922191524.YuLDocelz6.db.network-manager/network-manager-1.4.0/docs/libnm-glib'
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160922191524.YuLDocelz6.db.network-manager/network-manager-1.4.0/docs'
  make[4]: Nothing to be done for 'all-am'.
  make[4]: Leaving directory 

Bug#838592: gnome-python-desktop: FTBFS: autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools".

[Chris Lamb]

Source: gnome-python-desktop
Version: 2.32.0+dfsg-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

gnome-python-desktop fails to build from source in unstable/amd64:

  [..]

  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libgmpxx4ldbl:amd64 (2:6.1.1+dfsg-1) ...
  Setting up libvorbis0a:amd64 (1.3.5-3) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up ca-certificates (20160104) ...
  Setting up hicolor-icon-theme (0.15-1) ...
  Setting up libglib2.0-bin (2.50.0-1) ...
  Setting up python2.7-dev (2.7.12-3) ...
  Setting up python-all (2.7.11-2) ...
  Setting up libgraphite2-dev (1.3.8-1) ...
  Setting up libwww-robotrules-perl (6.01-1) ...
  Setting up orbit2 (1:2.14.19-1+b1) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.10-1) ...
  Setting up liblzo2-2:amd64 (2.08-1.2) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libhttp-negotiate-perl (6.00-2) ...
  Setting up libidn11-dev (1.33-1) ...
  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libvorbisfile3:amd64 (1.3.5-3) ...
  Setting up libgmp-dev:amd64 (2:6.1.1+dfsg-1) ...
  Setting up libpython-dev:amd64 (2.7.11-2) ...
  Setting up gconf2-common (3.2.6-3) ...
  
  Creating config file /etc/gconf/2/path with new version
  Setting up libdbus-1-dev:amd64 (1.10.10-1) ...
  Setting up libpcre3-dev:amd64 (2:8.39-2) ...
  Setting up gir1.2-atk-1.0:amd64 (2.22.0-1) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libhttp-cookies-perl (6.01-1) ...
  Setting up libcanberra0:amd64 (0.30-3) ...
  Setting up libdbus-glib-1-2:amd64 (0.108-1) ...
  Setting up python-dev (2.7.11-2) ...
  Setting up liblapack3 (3.6.1-2) ...
  update-alternatives: using /usr/lib/lapack/liblapack.so.3 to provide 
/usr/lib/liblapack.so.3 (liblapack.so.3) in auto mode
  Setting up libgconf-2-4:amd64 (3.2.6-3) ...
  Setting up libcanberra-dev:amd64 (0.30-3) ...
  Setting up libpython-all-dev:amd64 (2.7.11-2) ...
  Setting up libharfbuzz0b:amd64 (1.2.7-1+b1) ...
  Setting up libxau-dev:amd64 (1:1.0.8-1) ...
  Setting up libthai0:amd64 (0.1.25-1) ...
  Setting up libicu-dev (57.1-4) ...
  Setting up liborbit2:amd64 (1:2.14.19-1+b1) ...
  Setting up libglib2.0-dev (2.50.0-1) ...
  Setting up python-numpy (1:1.11.1~rc1-1) ...
  Setting up python-gobject-2-dev (2.28.6-13) ...
  Setting up libgnome-keyring0:amd64 (3.12.0-1+b1) ...
  Setting up libxml2-dev:amd64 (2.9.4+dfsg1-2) ...
  Setting up libbonobo2-0:amd64 (2.32.1-3) ...
  Setting up gconf-service (3.2.6-3) ...
  Setting up libxdmcp-dev:amd64 (1:1.1.2-1.1) ...
  Setting up python-all-dev (2.7.11-2) ...
  Setting up gir1.2-gnomekeyring-1.0 (3.12.0-1+b1) ...
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up x11proto-resource-dev (1.2.0-3) ...
  Setting up nettle-dev (3.2-1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libavahi-glib1:amd64 (0.6.32-1) ...
  Setting up libgnome-keyring-dev (3.12.0-1+b1) ...
  Setting up libpng-dev:amd64 (1.6.25-1) ...
  Setting up x11proto-render-dev (2:0.11.1-2) ...
  Setting up dbus (1.10.10-1) ...
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libselinux1-dev:amd64 (2.5-3) ...
  Setting up libxcb1:amd64 (1.11.1-1.1) ...
  Setting up x11proto-input-dev (2.3.2-1) ...
  Setting up libharfbuzz-gobject0:amd64 (1.2.7-1+b1) ...
  Setting up libidl-dev:amd64 (0.8.14-4) ...
  Setting up python-gconf (2.28.1+dfsg-1.1) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.7) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxcb-render0:amd64 (1.11.1-1.1) ...
  Setting up libxcb-util0:amd64 (0.3.8-3) ...
  Setting up libharfbuzz-icu0:amd64 (1.2.7-1+b1) ...
  Setting up python-pyorbit (2.24.0-7.1+b1) ...
  Setting up libavahi-common-dev:amd64 (0.6.32-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libavahi-glib-dev:amd64 (0.6.32-1) ...
  Setting up dbus-x11 (1.10.10-1) ...
  Setting up libatk1.0-dev:amd64 (2.22.0-1) ...
  Setting up libgnutls28-dev:amd64 (3.5.4-2) ...
  Setting up gir1.2-gconf-2.0 (3.2.6-3) ...
  Setting up libx11-xcb1:amd64 (2:1.6.3-1) ...
  Setting up x11proto-xext-dev (7.3.0-1) ...
  Setting up libfreetype6-dev (2.6.3-3+b1) ...
  Setting up liborbit2-dev (1:2.14.19-1+b1) ...
  Setting up libice-dev:amd64 (2:1.0.9-1+b1) ...
  Setting up libxcomposite1:amd64 (1:0.4.4-1) ...
  Setting up libxcb-shm0:amd64 (1.11.1-1.1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libxcb1-dev:amd64 (1.11.1-1.1) ...
  Setting up 

Bug#838593: easytag: FTBFS: dh_install: Cannot find (any matches for) "usr/lib/nautilus/*/*.so" (tried in "." and "debian/tmp")

[Chris Lamb]

Source: easytag
Version: 2.4.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

easytag fails to build from source in unstable/amd64:

  [..]

  /usr/bin/install -c -m 644 C/legal.xml 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/legal.xml
  /usr/bin/install -c -m 644 C/playlist-generate.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/playlist-generate.page
  /usr/bin/install -c -m 644 C/problems-id3.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/problems-id3.page
  /usr/bin/install -c -m 644 C/problems-ogg-split.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/problems-ogg-split.page
  /usr/bin/install -c -m 644 C/scanner.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/scanner.page
  /usr/bin/install -c -m 644 C/starting.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/starting.page
  /usr/bin/install -c -m 644 C/tag-capitalization.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/tag-capitalization.page
  /usr/bin/install -c -m 644 C/tag-field.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/tag-field.page
  /usr/bin/install -c -m 644 C/tag.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/C/easytag/tag.page
  /usr/bin/install -c -m 644 ca/cddb-search.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/cddb-search.page
  /usr/bin/install -c -m 644 ca/file-rename.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/file-rename.page
  /usr/bin/install -c -m 644 ca/file-select.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/file-select.page
  /usr/bin/install -c -m 644 ca/format-specifier.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/format-specifier.page
  /usr/bin/install -c -m 644 ca/image-delete.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/image-delete.page
  /usr/bin/install -c -m 644 ca/image-export.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/image-export.page
  /usr/bin/install -c -m 644 ca/image.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/image.page
  /usr/bin/install -c -m 644 ca/index.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/index.page
  /usr/bin/install -c -m 644 ca/introduction.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/introduction.page
  /usr/bin/install -c -m 644 ca/keyboard-shortcuts.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/keyboard-shortcuts.page
  /usr/bin/install -c -m 644 ca/legal.xml 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/legal.xml
  /usr/bin/install -c -m 644 ca/playlist-generate.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/playlist-generate.page
  /usr/bin/install -c -m 644 ca/problems-id3.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/problems-id3.page
  /usr/bin/install -c -m 644 ca/problems-ogg-split.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/problems-ogg-split.page
  /usr/bin/install -c -m 644 ca/scanner.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/scanner.page
  /usr/bin/install -c -m 644 ca/starting.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/starting.page
  /usr/bin/install -c -m 644 ca/tag-capitalization.page 
/home/lamby/temp/cdt.20160922190956.m6TreDVxuM.db.easytag/easytag-2.4.2/debian/tmp/usr/share/help/ca/easytag/tag-capitalization.page
  /usr/bin/install -c -m 644 ca/tag-field.page 

Bug#835416: imagevis3d: FTBFS: singleton.hpp:131: undefined reference to `boost::serialization::singleton_module::is_locked()'

[Tom Fogal]

Hi, thanks for looking into this.

On 09/20/2016 02:45 AM, peter green wrote:
>> 1. It's failing in the doc/genlua stuff, which is an internal tool meant
>> to generate documentation that is currently unfinished.  Arguably it
>> should be removed from source releases anyway.  So a simple fix is for
>> debian to just remove this directory from SUBDIRS in TuvokSubdirs.pro.
>
> I don't see a file called TuvokSubdirs.pro , I guess you mean 
> Tuvok/Tuvok.pro ?

Ahh, this must just be an older version, mea culpa.  Yeah, IIRC it would
be there.

> Anyway I removed doc/genlua from SUBDIRS in Tuvok/Tuvok.pro and tried a 
> build in raspbian stretch.
> 
> Unfortunately it failed with
> 
> g++ -fopenmp -Wl,-z,relro -o ../Build/ImageVis3D 
[snip]
> ../Tuvok/Build/libTuvok.a(SysTools.o): In function 
> `SysTools::GetTempDirectory(std::__cxx11::basic_string std::char_traits, std::allocator >&)':
> ./Tuvok/Basics/SysTools.cpp:1060: warning: the use of `tmpnam' is 
> dangerous, better use `mkstemp'
> ../Build/objects/ImageVis3D_WindowHandling.o: In function 
> `boost::serialization::singleton::get_mutable_instance()':
> /usr/include/boost/serialization/singleton.hpp:131: undefined reference 
> to `boost::serialization::singleton_module::is_locked()'

Yes, this is the same issue that was causing 'genlua' to fail; looks
like simply removing that code wasn't a great workaround.  Sorry.

I dug a bit deeper, by downloading boost 1.61 and verifying that,
indeed, the singleton.hpp included there is NOT a header-only library,
yet the one included in Tuvok's 3rdParty directory IS a header-only library.

Looking closer at the build log, I note that it is missing many of the
-I options that upstream has.  Notably in this case:
-IIO/3rdParty/boost.  This in turn causes it to use the system copy of
boost, which has changed behavior to require a new link option.

I can think of a number of solutions:

  * build-dep require a similar version of boost on the system.  I
can confirm 1.58 is fine.  Note that the runtime is irrelevant
since IV3D restricts itself to header-only parts of boost.

  * don't hack out the -I flags from upstream so that IV3D uses its
internal copy of boost.

  * edit the .pro files to force this to link against
libboost_serialization.so.

Bug#838590: dymo-cups-drivers: FTBFS: CupsFilterLabelWriter.h:58:104: error: 'ppd_file_t' has not been declared

[Chris Lamb]

Source: dymo-cups-drivers
Version: 1.4.0-5
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

dymo-cups-drivers fails to build from source in unstable/amd64:

  [..]


 ^~
  CupsFilterLabelWriter.h:58:104: error: 'ppd_file_t' has not been declared
 static void ProcessPPDOptions (CLabelWriterDriverTwinTurbo& Driver, 
CLabelWriterLanguageMonitor& LM, ppd_file_t* ppd);

  ^~
  CupsFilterLabelWriter.cpp:26:110: error: 'ppd_file_t' has not been declared
   void CDriverInitializerLabelWriter::ProcessPPDOptions(CLabelWriterDriver& 
Driver, CDummyLanguageMonitor& LM, ppd_file_t* ppd)

^~
  CupsFilterLabelWriter.cpp: In static member function 'static void 
DymoPrinterDriver::CDriverInitializerLabelWriter::ProcessPPDOptions(DymoPrinterDriver::CLabelWriterDriver&,
 DymoPrinterDriver::CDummyLanguageMonitor&, int*)':
  CupsFilterLabelWriter.cpp:28:3: error: 'ppd_choice_t' was not declared in 
this scope
 ppd_choice_t* choice = ppdFindMarkedChoice(ppd, "Resolution");
 ^~~~
  CupsFilterLabelWriter.cpp:28:17: error: 'choice' was not declared in this 
scope
 ppd_choice_t* choice = ppdFindMarkedChoice(ppd, "Resolution");
   ^~
  CupsFilterLabelWriter.cpp:28:63: error: 'ppdFindMarkedChoice' was not 
declared in this scope
 ppd_choice_t* choice = ppdFindMarkedChoice(ppd, "Resolution");
 ^
  CupsFilterLabelWriter.cpp:37:57: error: 'stderr' was not declared in this 
scope
   fputs("WARNING: unable to get Resolution choice\n", stderr);
   ^~
  CupsFilterLabelWriter.cpp:37:63: error: 'fputs' was not declared in this scope
   fputs("WARNING: unable to get Resolution choice\n", stderr);
 ^
  CupsFilterLabelWriter.cpp:48:59: error: 'stderr' was not declared in this 
scope
   fputs("WARNING: unable to get PrintQuality choice\n", stderr);
 ^~
  CupsFilterLabelWriter.cpp:48:65: error: 'fputs' was not declared in this scope
   fputs("WARNING: unable to get PrintQuality choice\n", stderr);
   ^
  CupsFilterLabelWriter.cpp:64:59: error: 'stderr' was not declared in this 
scope
   fputs("WARNING: unable to get PrintDensity choice\n", stderr);
 ^~
  CupsFilterLabelWriter.cpp:64:65: error: 'fputs' was not declared in this scope
   fputs("WARNING: unable to get PrintDensity choice\n", stderr);
   ^
  CupsFilterLabelWriter.cpp:66:24: error: request for member 'modelname' in '* 
ppd', which is of non-class type 'int'
 if (!strcasecmp(ppd->modelname, "DYMO LabelWriter 300")
  ^
  CupsFilterLabelWriter.cpp:67:23: error: request for member 'modelname' in '* 
ppd', which is of non-class type 'int'
 || !strcasecmp(ppd->modelname, "DYMO LabelWriter 310")
 ^
  CupsFilterLabelWriter.cpp:68:23: error: request for member 'modelname' in '* 
ppd', which is of non-class type 'int'
 || !strcasecmp(ppd->modelname, "DYMO LabelWriter 315"))
 ^
  CupsFilterLabelWriter.cpp:71:24: error: request for member 'modelname' in '* 
ppd', which is of non-class type 'int'
 if (!strcasecmp(ppd->modelname, "DYMO LabelWriter 4XL"))
  ^
  CupsFilterLabelWriter.cpp:74:24: error: request for member 'modelname' in '* 
ppd', which is of non-class type 'int'
 if (!strcasecmp(ppd->modelname, "DYMO LabelWriter SE450"))
  ^
  CupsFilterLabelWriter.cpp: In static member function 'static void 
DymoPrinterDriver::CDriverInitializerLabelWriter::ProcessPageOptions(DymoPrinterDriver::CLabelWriterDriver&,
 DymoPrinterDriver::CDummyLanguageMonitor&, cups_page_header2_t&)':
  CupsFilterLabelWriter.cpp:88:13: error: 'stderr' was not declared in this 
scope
   fprintf(stderr, "WARNING: Invalid value for cupsMediaType (%d)\n", 
PageHeader.cupsMediaType);
   ^~
  CupsFilterLabelWriter.cpp:88:96: error: 'fprintf' was not declared in this 
scope
   fprintf(stderr, "WARNING: Invalid value for cupsMediaType (%d)\n", 
PageHeader.cupsMediaType);
  

Bug#835684: marked as done (syncthing: FTBFS: dh_auto_test: go test -v -p 1 github.com/syncthing/syncthing/cmd/stbench github.com/syncthing/syncthing/cmd/stcompdirs github.com/syncthing/syncthing/cmd/

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 12:48:54 -0400
with message-id 

Bug#838586: roxterm false on start up segfault

[fisherman]

Package: roxterm
Version: 2.9.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When I start roxterm from gnome-terminal, it crashes with tons(>1000) of
strings like
"** (roxterm:28783): WARNING **: VTE's inner-border property unavailable"
and segfault. Numbers after "roxterm:" are the same in all strings, but new
after each crash.
Thats realy stange, becouse I hadn`t changed any options in my system or
roxterm for a while
when I found roxterm doesn`t work. May be problem is in my new themse for GTK+
(Flat - Plat)
and Gnome Shell (Sequoia-ng). I installed them in 3-4 days before first crash
so it looks like wrong idea.
Also I installed some packages for themse:
albatross-gtk-theme blackbird-gtk-theme bluebird-gtk-theme greybird-gtk-theme
gtk2-engines-murrine murrine-themes
but deleting them with aptitude purge, reinstalling roxterm, restarting gnome,
creating and reloginig to a new user
(with standart themse: Adwaita) and evean rebooting don`t fix my problem.
So I don`t know, what caused that error. According to the error string the
problem is in VTE,
but it doesn`t looks broken. Gnome terminal, for example, works with no
problem.

I forgot to say, I have transparent background in roxterm. May be that`s
important.

Thank you for your consideration.



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

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

Versions of packages roxterm depends on:
ii  roxterm-gtk3  2.9.5-1

roxterm recommends no packages.

roxterm suggests no packages.

-- no debconf information

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

On 2016-09-22 18:42:21 +0300, Anton Zinoviev wrote:
> On Thu, Sep 22, 2016 at 02:17:54PM +0200, Sven Joachim wrote:
> > I'm pretty sure it is.  The list of keyboard models is generated by
> > running "./kbdnames-maker KeyboardNames.pl" from the Keyboard/
> > directory, and currently this command does not print anything.  I
> > tracked the problem down to the removal of the current directory from
> > @INC in perl, running "perl -I. kbdnames-maker KeyboardNames.pl" gives
> > the long list of keyboard models again.
> 
> I am adding to this bug a 'help' tag because the bug is grave and at the 
> moment I don't have updated Debian machine so I can not debug.  
> 
> Conceivably, the fix will be trivial.  I don't know if the following 
> will fix the bug and if this is the right thing to do, but it seems 
> simple to change the first line
> 
> #!/usr/bin/perl
> 
> of Keyboard/kbdcompiler and Keyboard/kbdnames-maker to
> 
> #!/usr/bin/perl -I.

This solves the issue for the keyboard-configuration.config file.

This also introduces the following change in
"/usr/share/console-setup/kbdnames-maker":

@@ -1,4 +1,4 @@
-#!/usr/bin/perl
+#!/usr/bin/perl -I.
 
 use warnings 'all';
 use strict;

I suppose that this is OK if /usr/share/console-setup/kbdnames-maker
is expected to be run with /usr/share/console-setup as the current
working directory. Otherwise, I'm wondering... What is the goal of
this script here?

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

Bug#838583: libconfig-model-lcdproc-perl: FTBFS with "Syntax error: spurious char at command end"

[Santiago Vila]

Package: src:libconfig-model-lcdproc-perl
Version: 2.049-1
Severity: serious

Dear Perl maintainers:

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
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Config-Model-LcdProc' version '--installdirs'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
touch lcdproc/LCDd.conf
dh_auto_build
perl Build
Load command error:
command: 'max='
Syntax error: spurious char at command end: '='. Did you forget double 
quotes ?
Exception thrown  at /usr/share/perl5/Config/Model/Exception.pm line 69.

Config::Model::Exception::rethrow(Config::Model::Exception::Load=HASH(0x7bf99a8))
 called at /usr/share/perl5/Config/Model/Exception.pm line 64
Config::Model::Exception::throw("Config::Model::Exception::Load", 
"command", "max=", "error", "Syntax error: spurious char at command end: '='. 
Did you forg"...) called at /usr/share/perl5/Config/Model/Loader.pm line 161
Config::Model::Loader::_split_cmd("max=") called at 
/usr/share/perl5/Config/Model/Loader.pm line 222
Config::Model::Loader::_load(Config::Model::Loader=HASH(0x7ada6a0), 
Config::Model::Node=HASH(0x7d2e978), "yes", ARRAY(0x19ef0a0)) called at 
/usr/share/perl5/Config/Model/Loader.pm line 683

Config::Model::Loader::_load_hash(Config::Model::Loader=HASH(0x7ada6a0), 
Config::Model::Node=HASH(0x78c2230), "yes", ARRAY(0x2ce4e78), ARRAY(0x19ef0a0)) 
called at /usr/share/perl5/Config/Model/Loader.pm line 296
Config::Model::Loader::_load(Config::Model::Loader=HASH(0x7ada6a0), 
Config::Model::Node=HASH(0x78c2230), "yes", ARRAY(0x19ef0a0)) called at 
/usr/share/perl5/Config/Model/Loader.pm line 683

Config::Model::Loader::_load_hash(Config::Model::Loader=HASH(0x7ada6a0), 
Config::Model::Node=HASH(0x26d4208), "yes", ARRAY(0x19fdec8), ARRAY(0x19ef0a0)) 
called at /usr/share/perl5/Config/Model/Loader.pm line 296
Config::Model::Loader::_load(Config::Model::Loader=HASH(0x7ada6a0), 
Config::Model::Node=HASH(0x26d4208), "yes", ARRAY(0x19ef0a0), 1) called at 
/usr/share/perl5/Config/Model/Loader.pm line 80
Config::Model::Loader::load(Config::Model::Loader=HASH(0x7ada6a0), 
"node", Config::Model::Node=HASH(0x26d4208), "steps", "class:\"LCDd::picolcd\" 
element:LircFlushThreshold type=leaf  v"...) called at 
/usr/share/perl5/Config/Model/Node.pm line 918
Config::Model::Node::load(Config::Model::Node=HASH(0x26d4208), 
"class:\"LCDd::picolcd\" element:LircFlushThreshold type=leaf  v"...) called at 
script/lcdconf2model.pl line 342
Building lcdproc model from upstream LCDd.conf file...
note: unhandled legal  spec: '0x200-0x400'. Sending it back to doc
note: unhandled legal  spec: '1x1-640x480'. Sending it back to doc
lcdconf2model failed: 512 at /<>/_build/lib/Module/Build/Custom.pm 
line 8.
dh_auto_build: perl Build returned exit code 2
debian/rules:7: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

It fails in unstable as well:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libconfig-model-lcdproc-perl.html

As usual, if this is really a bug in one of the build-depends, please
use reassign and affects, so that this is still visible in the page
for this package. I tried to find some build-dependency to blame, but
did not found any.

Thanks.

Bug#838585: libstoragemgmt: current version (1.2.3) shouldn't be part of Stretch

[Ritesh Raj Sarraf]

Source: libstoragemgmt
Severity: grave
Justification: renders package unusable

This is a placeholder bug to indicate that libstoragemgmt shouldn't, in
its current form, be part of the Stretch Release.

I could request the removal of it from the archive, but I'm hopeful that
someone else may step up and take over its maintenance.

The package has been orphaned as mentioned in #824749

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

Kernel: Linux 4.8.0-rc7alxb+ (SMP w/4 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#838579: zeroc-ice: FTBFS in testing (Build failed with an exception)

[Jose Gutierrez de la Concha]

Hi Santiago,

We will upload a new version that solve the issue

 What went wrong:
A problem occurred evaluating root project 'java'.
> Could not resolve all dependencies for configuration 'classpath'.
   > Could not resolve com.zeroc.gradle.ice-builder:slice:1.3.6.
 Required by:
 unspecified:unspecified:unspecified
  > No cached version of com.zeroc.gradle.ice-builder:slice:1.3.6
available for offline mode.
  > No cached version of com.zeroc.gradle.ice-builder:slice:1.3.6
available for offline mode.


We recently updated gradle.ice-builder to version 1.3.13, Java build should
not hardcode the builder version and
use instead `debian` version.

That bug is already fixed in upstream packaging
https://github.com/zeroc-ice/ice-debian-packaging/tree/3.6

Still need to import latest Ice 3.6 changes there and upload to testing


On Thu, Sep 22, 2016 at 5:56 PM, Santiago Vila  wrote:

> Package: src:zeroc-ice
> Version: 3.6.2-stretch-51-gba6baa6-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.
>
> 
> 
> [...]
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file '/<>/java/build.gradle' line: 16
>
> * What went wrong:
> A problem occurred evaluating root project 'java'.
> > Could not resolve all dependencies for configuration 'classpath'.
> 
> 
>
> I'm attaching two different build logs.
>
> Sorry, I have not tried "dpkg-buildpackage" alone, but this package has
> separate override_dh_auto_build-arch and override_dh_auto_build-indep
> targets, so this could be "dpkg-buildpackage -A" specific indeed.
>
> Thanks.




-- 
José Gutiérrez de la Concha
ZeroC, Inc.

Bug#838418: Bug#838549: libreoffice-gtk3: Fails to make libreoffice work

[Simon John]

5.2.2 packages fix the rendering issue for me too.

So was it an upstream issue, not packaging?

Regards.


On 22/09/16 14:18, g.l. gragnani wrote:
> It works for me.
> 
> Best regards,
> 
> Gigi
> 
> On 09/22/2016 01:46 PM, Rene Engelhard wrote:
[...]
>> Does it work for you with the 5.2.2 packages from
>> http://people.debian.org/~rene/libreoffice/5.2.2?
>>
>> Regards,
>>
>> Rene
>>

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Anton Zinoviev]

tags 838310 +help
thanks

On Thu, Sep 22, 2016 at 02:17:54PM +0200, Sven Joachim wrote:
> 
> I'm pretty sure it is.  The list of keyboard models is generated by
> running "./kbdnames-maker KeyboardNames.pl" from the Keyboard/
> directory, and currently this command does not print anything.  I
> tracked the problem down to the removal of the current directory from
> @INC in perl, running "perl -I. kbdnames-maker KeyboardNames.pl" gives
> the long list of keyboard models again.

I am adding to this bug a 'help' tag because the bug is grave and at the 
moment I don't have updated Debian machine so I can not debug.  

Conceivably, the fix will be trivial.  I don't know if the following 
will fix the bug and if this is the right thing to do, but it seems 
simple to change the first line

#!/usr/bin/perl

of Keyboard/kbdcompiler and Keyboard/kbdnames-maker to

#!/usr/bin/perl -I.

Anton Zinoviev

Processed: Re: Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Debian Bug Tracking System]

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

> tags 838310 +help
Bug #838310 [keyboard-configuration] keyboard-configuration: user configuration 
lost + error message from setupcon
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#831844: [debian-mysql] Bug#831844: mysql-5.6: Multiple security fixes from the July 2016 CPU

[Robie Basak]

Hi Dominic,

On Thu, Sep 22, 2016 at 04:10:37PM +0100, Dominic Hargreaves wrote:
> > Do you have any ETA for this update being in unstable?
> 
> I assume that there is no more work for mysql-5.6 planned by the
> MySQL team, given the silence on this bug and that you are about to
> upload mysql-5.7 (cf #837615).

That's right - I intend to fix the bug by uploading mysql-5.7 to
unstable.

> As I need to have a MySQL 5.6 backport supported for the foreseeable
> future, I intend to NMU a new upstream release in the next few weeks.
> 
> Does anyone have any objections to this?


I'm happy for you to do this - please join the team! Perhaps you could
maintain a backport branch in VCS with us?

I did see
http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2016-September/009435.html
scroll past, and didn't feel in a position to be able to help, because
I've not looked at the backport at all. I believe there's a bug reported
against the backports package too, though I'm not sure how to locate
that easily right now.

So I suppose I only have one request, which is that if you want to
continue to maintain the backport, that you please also watch and manage
the ML and BTS for issues against those backported packages. Does that
sound OK to you?

Robie

Processed: bug 837786 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=771815

[Debian Bug Tracking System]

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

> forwarded 837786 https://bugzilla.gnome.org/show_bug.cgi?id=771815
Bug #837786 [mutter] mutter: Issues repainting the display on mouse movement
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=771815'.
> thanks
Stopping processing here.

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

Bug#831844: mysql-5.6: Multiple security fixes from the July 2016 CPU

[Dominic Hargreaves]

On Tue, Aug 16, 2016 at 04:32:20PM +0100, Dominic Hargreaves wrote:
> On Wed, Jul 20, 2016 at 07:42:21AM +0200, Salvatore Bonaccorso wrote:
> > Source: mysql-5.6
> > Version: 5.6.30-1
> > Severity: grave
> > Tags: security upstream
> > Justification: user security hole
> > 
> > Hi
> > 
> > Please see
> > http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html#AppendixMSQL
> 
> Hi maintainers,
> 
> Do you have any ETA for this update being in unstable?

I assume that there is no more work for mysql-5.6 planned by the
MySQL team, given the silence on this bug and that you are about to
upload mysql-5.7 (cf #837615).

As I need to have a MySQL 5.6 backport supported for the foreseeable
future, I intend to NMU a new upstream release in the next few weeks.

Does anyone have any objections to this?

Thanks,
Dominic.

Bug#837593: marked as done (gnome-shell-extension-redshift: Not compatible with gnome-shell 3.21.x/3.22)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 10:51:51 -0400
with message-id <20160922145151.2v3tl3ej62v3jyk6@gambit>
and subject line Re: Bug#837593: gnome-shell-extension-redshift: Not compatible 
with gnome-shell 3.21.x/3.22
has caused the Debian Bug report #837593,
regarding gnome-shell-extension-redshift: Not compatible with gnome-shell 
3.21.x/3.22
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.)


-- 
837593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-extension-redshift
Version: 3.20.1-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-3-22

Hi,

your package gnome-shell-extension-redshift declares a strictly
versioned dependency on gnome-shell. We've uploaded gnome-shell
3.21.91 to unstable, which makes gnome-shell-extension-redshift
uninstallable.

Please test if your package is compatible with that version and
update the information in metadata.json and the package dependencies
accordingly.

There will be one more development release, 3.21.92, before the final
version 3.22.0 is released [1]. gnome-shell development is frozen, so
if gnome-shell-extension-redshift works with 3.21.91, it's pretty
safe to assume it will also work with 3.21.92 and 3.22. So you might
list those as supported versions as well

Regards, Michael

[1] https://wiki.gnome.org/ThreePointTwentyone
--- End Message ---
--- Begin Message ---
Version: 3.20.1-2

Forgot to close in changelog.

* Michael Biebl (em...@michaelbiebl.de) wrote:
> There are some recent updates:
> 
> In the past, it was necessary to explicitly declare supported
> gnome-shell versions in metadata.json. This was lifted in gnome-shell
> 3.21.92 [1].
> 
> "Nowadays, the user interface has mostly stabilized with most changes
> happening under the hood. As a result, extensions written for
> previous versions of GNOME Shell are very much expected to keep
> working on updates, if it wasn't for the version check that requires
> a version bump in the extension metadata. There has been a setting to
> disable that check for a while, but it's existence isn't widely known
> (hence the common perception that "everything breaks on updates").
> While there is still some risk that an out-of-date extension can be
> enabled without error, but fails spectacularly later (where we cannot
> catch the exception), it is reasonably small by now when compared to
> the ~95% of extensions that can be "unbroken", so swap the default
> value to disable version checks by default."
> 
> As a result, you could drop the gnome-shell << XXX version limitation
> altogether. The Debian release cycle is pretty long though, so we
> don't know yet if the gnome-shell version in Buster will actually be
> compatible with your extension today. We will release Stretch with
> GNOME Shell 3.22, so my recommendation would be to use gnome-shell
> (<< 3.23) as upper limt.
> 
> Modifications for metadata.json are no longer required.
> 
> Regards, Michael
> 
> [1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e
> 




-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: PGP signature
--- End Message ---

Bug#836947: marked as done (gnome-shell-extension-redshift: uninstallable in sid)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 10:51:51 -0400
with message-id <20160922145151.2v3tl3ej62v3jyk6@gambit>
and subject line Re: Bug#837593: gnome-shell-extension-redshift: Not compatible 
with gnome-shell 3.21.x/3.22
has caused the Debian Bug report #837593,
regarding gnome-shell-extension-redshift: uninstallable in sid
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.)


-- 
837593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-redshift
Version: 3.20.1-1
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

  The following packages have unmet dependencies:
   gnome-shell-extension-redshift : Depends: gnome-shell (< 3.21) but 3.21.91-2 
is to be installed


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Version: 3.20.1-2

Forgot to close in changelog.

* Michael Biebl (em...@michaelbiebl.de) wrote:
> There are some recent updates:
> 
> In the past, it was necessary to explicitly declare supported
> gnome-shell versions in metadata.json. This was lifted in gnome-shell
> 3.21.92 [1].
> 
> "Nowadays, the user interface has mostly stabilized with most changes
> happening under the hood. As a result, extensions written for
> previous versions of GNOME Shell are very much expected to keep
> working on updates, if it wasn't for the version check that requires
> a version bump in the extension metadata. There has been a setting to
> disable that check for a while, but it's existence isn't widely known
> (hence the common perception that "everything breaks on updates").
> While there is still some risk that an out-of-date extension can be
> enabled without error, but fails spectacularly later (where we cannot
> catch the exception), it is reasonably small by now when compared to
> the ~95% of extensions that can be "unbroken", so swap the default
> value to disable version checks by default."
> 
> As a result, you could drop the gnome-shell << XXX version limitation
> altogether. The Debian release cycle is pretty long though, so we
> don't know yet if the gnome-shell version in Buster will actually be
> compatible with your extension today. We will release Stretch with
> GNOME Shell 3.22, so my recommendation would be to use gnome-shell
> (<< 3.23) as upper limt.
> 
> Modifications for metadata.json are no longer required.
> 
> Regards, Michael
> 
> [1] https://git.gnome.org/browse/gnome-shell/commit/?id=5e0e3e
> 




-- 
Eric Dorland 
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93


signature.asc
Description: PGP signature
--- End Message ---

Bug#838414: gpick: colors.txt is non-free

[Elías Alejandro]

Hello,

On Wed, Sep 21, 2016 at 9:45 PM, Ben Finney  wrote:
> Elías Alejandro  writes:
>
>> Could you review this issue?
>
> What kind of review are you asking for? What new information has
> appeared that prompts a review?
>
> For what it's worth, I agree with the earlier assessment that the
> restriction on usage violates DFSG §6.
>
> Further, the term “use” is hopelessly vague and AFAIK null in copyright.
> There are various common interpretations of what actions “use” could
> mean in a copyright license text, that are incompatible with each other.
> Better to change the conditions to be specific about what actions are
> permitted.
>
I understood the terms "These RGB colour formulations" are more about
how they made this color list and the names for each color and color
codes. I'm not sure but probably they made this list under their own
way and not under "standards". In this way, it may not be used to the
detriment of them because of this. Maybe you have another
interpretation.

Best regards.
Elías Alejandro

Bug#837786: Upstream bug

[GEHA]

https://bugzilla.gnome.org/show_bug.cgi?id=771815

Bug#838394: openbabel: FTBFS on mips,mips64el: internal compiler errors

[gregor herrmann]

On Thu, 22 Sep 2016 10:59:13 +0200, Julien Cristau wrote:

> On Thu, Sep 22, 2016 at 10:34:29 +0300, Niko Tyni wrote:
> > @debian-wb-team: could you please give it back to see if it happens
> > again on buildds?
> >  gb openbabel_2.3.2+dfsg-2.4 . mips mips64el
> Given back.

Thanks!
And it built everywhere:
https://buildd.debian.org/status/logs.php?pkg=openbabel=2.3.2%2Bdfsg-2.4

I guess we can close this bug?
Unless Niko would like to keep track of the issues he discovered, of
course.


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#838418: Bug#838549: libreoffice-gtk3: Fails to make libreoffice work

[g.l. gragnani]

It works for me.

Best regards,

Gigi

On 09/22/2016 01:46 PM, Rene Engelhard wrote:

tag 838549 + moreinfo
tag 838418 + moreinfo
thanks

[ also CCing #838418. maybe the same reason? ]

Hi,

On Thu, Sep 22, 2016 at 10:45:45AM +0200, Rene Engelhard wrote:

On Thu, Sep 22, 2016 at 10:34:49AM +0200, Rene Engelhard wrote:

On Thu, Sep 22, 2016 at 09:50:33AM +0200, Rene Engelhard wrote:

  more important, I was no longer able to export in PDF.
Exporting to PDF, when not crashing the application, produces a file
with garbage random characters.

That needs to be tried...

Just tried it in a clean sid chroot + LO + libreoffice-gnome (which installs
also -gtk3)

New document, "Test", export to PDF. Indeed I get something looking like 
"dfiffjfk" :(

As counter-check: works with -gtk2...

Let's use this bug for this, the (probably) only thing which makes sense in this
report.

More tests: After a downgrade to libbgtk-3-0 3.20.9-1 it works again. So one 
more
bug introduced by the Gtk update, which also means that your Version: field was 
wrong
to begin with as it's not new in 5.2.1-3...

We discussed this on IRC today:

10:17 < _rene_> caolan: new churns of "gtk3 is brokenone" coming in.
 seen https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838418?
 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838549 is
 basically not useful.)
10:17 < loircbot> LibreOffice (core) noel.grandin *
   sc/source/core/tool/charthelper.cxx: tdf#101894 Copying a
   single sheet with a chart on it garbles the chart
10:20 -!- JoNi
   [~chatzi...@ipservice-092-208-087-160.092.208.pools.vodafone-ip.de]
   has joined #libreoffice-dev
10:21 -!- aruiz [~aruiz@90.216.49.139] has joined #libreoffice-dev
10:22 <@caolan> _rene_: and do you have
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-5-2=2c91b
27a968afb36b77e447dd623bbe81ea542f0 applied ?
0:22 < IZBot> core - Resolves: rhbz#1373933 gtk 3.21 emits a lot more
"style-set" signals
10:22 -!- willcooke [~willcooke@ubuntu/member/willcooke] has quit [Remote host
   closed the connection]
10:23 <@caolan> _rene_: also, that reminds me, I think you mentioned some deb
 bug about the libreoffice icons not correct under gnome ?
 https://bugzilla.gnome.org/show_bug.cgi?id=771731 for the
 upstream fix for that if so
10:24 < _rene_> caolan: yep, that was the point if 5.2.1-3
10:24 < _rene_> 2c91b27a968afb36b77e447dd623bbe81ea542f0 I mean
10:24 < IZBot> core - Resolves: rhbz#1373933 gtk 3.21 emits a lot more
"style-set" signals -
http://cgit.freedesktop.org/libreoffice/core/commit/?id=2c91b27a968afb36b77e447dd623bbe81ea542f0
10:25 <@caolan> then its an unknown problem
10:25 <@caolan> "I tried reverting to libgtk-3-0_3.20.9-1_amd64.deb and it made
 no difference" makes it sound unrelated to the style-set thing
10:26 <@caolan> I got 3.20.9 here and I'm as happy as a clam
10:26 -!- xrmx [~rm@213.215.163.27] has joined #libreoffice-dev
10:26 -!- xrmx [~rm@213.215.163.27] has quit [Changing host]
10:26 < _rene_> yeah, I just asked him to go sure
10:26 < _rene_> the problem is, we do have 3.21/3.22 in testing/unstable.
[...]
10:34 <@caolan> _rene_: this is good I guess, you can try a gtk3 downgrade to
 isolate if that's the trigger or not ?
[...]
10:41 < _rene_> caolan: after downgrade it works
[...]
10:44 <@caolan> _rene_: when you saw the problem with pdf export, where did you
 see it, in the pdf export dialog itself, or the outputted pdf ?
[...]
10:44 < _rene_> caolan: the outputted PDF. entered Test in a odt, export, got
 something looking like "dfiffjfk"
10:44 < buovjaga> some deeper philosophy, do we close this as wontfix for now?
   tdf#101746
10:44 < IZBot> LibreOffice-framework normal/medium UNCONFIRMED all operations
of one Libreoffice application are quued one-thread
https://bugs.documentfoundation.org/show_bug.cgi?id=101746
10:45 <@caolan> let me upgrade to gtk3 and check that out locally
10:46  * _rene_ updates the bug
[...]
10:56 <@caolan> _rene_: no problem for me on F24 if I upgrade to rawhide
 gtk3-3.22.0 and export to pdf (even if I revert the style-set
 patch) so I got nothing useful
10:57 -!- lplatypus [~chatzilla@101.161.34.40] has joined #libreoffice-dev
10:57 < _rene_> hrmpf.
10:59 < _rene_> hrm, now it worked here, too? wtf?
10:59 <@caolan> this is not the bug you are looking for
10:59  * caolan waves hand mystically
10:59 < _rene_> ah, no, wait
10:59 < _rene_> -rw-r--r--  1 root root 6263 Sep 22 08:58 Test.pdf
10:59 < _rene_> too old :)
[...]
11:34 < _rene_> caolan: rechecked again, timestamp was confusing. it's as I
 said, 3.20 works, 3.22 not...
[...]
11:37 <@caolan> _rene_: I just downloaded

Processed: Re: Bug#827744: bzip2: CVE-2016-3189: heap use after free in bzip2recover

[Debian Bug Tracking System]

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

> tag 827744 + pending
Bug #827744 [src:bzip2] bzip2: CVE-2016-3189: heap use after free in 
bzip2recover
Added tag(s) pending.
> stop
Stopping processing here.

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

Bug#837247: marked as done (obfsproxy: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 12:19:28 +
with message-id 
and subject line Bug#837247: fixed in obfsproxy 0.2.13-2
has caused the Debian Bug report #837247,
regarding obfsproxy: FTBFS: Tests 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.)


-- 
837247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: obfsproxy
Version: 0.2.13-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>   File "/usr/lib/python2.7/dist-packages/twisted/trial/runner.py", line 405, 
> in findByName
> return filenameToModule(name)
>   File "/usr/lib/python2.7/dist-packages/twisted/trial/runner.py", line 96, 
> in filenameToModule
> return _importFromFile(fn)
>   File "/usr/lib/python2.7/dist-packages/twisted/trial/runner.py", line 119, 
> in _importFromFile
> module = imp.load_source(moduleName, fn, fd)
>   File "obfsproxy/__init__.py", line 1, in 
> from ._version import get_versions
> exceptions.ValueError: Attempted relative import in non-package
> 
> obfsproxy
> ---
> Ran 1 tests in 0.060s
> 
> FAILED (errors=1)
> debian/rules:17: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/09/10/obfsproxy_0.2.13-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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

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

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

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated obfsproxy 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, 22 Sep 2016 13:15:38 +0200
Source: obfsproxy
Binary: obfsproxy
Architecture: source
Version: 0.2.13-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: Ximin Luo 
Description:
 obfsproxy  - pluggable transport proxy for Tor
Closes: 837247
Changes:
 obfsproxy (0.2.13-2) unstable; urgency=medium
 .
   * Team upload.
   * Add PYTHONPATH=. when running the tests. (Closes: #837247)
   * Update to latest Standards-Version; no changes required.
Checksums-Sha1:
 5f00ef7a55454ee0e81a70a58e40e5a5b94de1c8 2188 obfsproxy_0.2.13-2.dsc
 ed977d2bfab375827132dbd193219cc1b9671585 14584 obfsproxy_0.2.13-2.debian.tar.xz
Checksums-Sha256:
 2871cbab3a9a83ef261b4d42f9ce20d8e60da3fb30a85cf15449c24ec7aa3d17 2188 
obfsproxy_0.2.13-2.dsc
 1f59d8cbbd5ab44db03c3965998e30520c84c64861746e8782473089bb878850 14584 
obfsproxy_0.2.13-2.debian.tar.xz
Files:
 db1a9237c9bca13fdc071b4bee1e3b14 2188 net extra obfsproxy_0.2.13-2.dsc
 1baaaec534ada8082f27d9dad69bfe2e 14584 net extra 
obfsproxy_0.2.13-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJX48opAAoJEIYN7zuPZQt5NTgP/2FEzrxOeJqXJ+Zhp2We5Tnl
T0SUhFBbBJAKwyLuQf4QVeVckr0SHTpVKLNfX5ZAz/PpXvy/axSIAvFyxcQ0/MLv
hw5riF1zN3bPrWqYPN8CIvt9G9w8/B4YrlsgMwQSfkH6X5yvnzGD3Jqy7H/N7t9L
oOiIDfGQNqsuPC/3a4OjzG35bCsby4IYX5pUSWGPMjhmeIF507seVNi6UW0uWnXj
XnhN6Q9C+0nSBTwlFRf60eFuj0bWA2mGrSjI74FETD2ValxNRyCLPE2XwAf9xOvP
OxaOj37SeYUVCAVUZL583/CrjrmzwGv+74DVllpjh6isnH2kxuYXj5V21+//g2+R
h3vTigj1tbbNsK5BPZq/HsMWwsxHC6uJlHgmJyQe3wRTYHNoxMbRExxB1VuhC2vB

Bug#788513: marked as done (aufs-tools: FTBFS: linux/aufs_type.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 14:33:13 +0200
with message-id <8fc5b663-143c-2bef-f442-121830aba...@fu-berlin.de>
and subject line Bug#788513: fixed in aufs-tools 1:4.1+20160919-1
has caused the Debian Bug report #788513,
regarding aufs-tools: FTBFS: linux/aufs_type.h: No such file or directory
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.)


-- 
788513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aufs-tools
Version: 1:3.2+20130722-1.1
Severity: serious

>From my pbuilder build log:

...
 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
   dh_auto_build
make -j1
make[1]: Entering directory '/tmp/buildd/aufs-tools-3.2+20130722'
cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -I./libau 
-O -Wall -D_FORTIFY_SOURCE=2 -DMOUNT_CMD_PATH=\"\" -Wl,-z,relro  ver.c   -o ver
ver.c:19:29: fatal error: linux/aufs_type.h: No such file or directory
 #include 
 ^
compilation terminated.
: recipe for target 'ver' failed
make[1]: *** [ver] Error 1
make[1]: Leaving directory '/tmp/buildd/aufs-tools-3.2+20130722'
dh_auto_build: make -j1 returned exit code 2
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: aufs-tools
Source-Version: 1:4.1+20160919-1

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

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

Debian distribution maintenance software
pp.
Jan Luca Naumann  (supplier of updated
aufs-tools package)



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Sven Joachim]

Control: user debian-p...@lists.debian.org
Control: usertags -1 perl-cwd-inc-removal

On 2016-09-22 12:45 +0200, Vincent Lefevre wrote:

> In the keyboard-configuration 1.148 binary package, one has:
>
> -rwxr-xr-x 1 1862421 2016-07-29 08:06:33 DEBIAN/config
>
> But in the 1.149 version:
>
> -rwxr-xr-x 1 48945 2016-09-18 17:53:38 DEBIAN/config
>
> The diff:
>
> --- keyboard-configuration_1.148_all/DEBIAN/config  2016-07-29 
> 08:06:33.0 +0200
> +++ keyboard-configuration_1.149_all/DEBIAN/config  2016-09-18 
> 17:53:38.0 +0200
> @@ -159,33732 +159,6 @@
>  
>  all_kbdnames () {
>   cat <<'EOF'
> -C*model*a4techKB21*A4Tech KB-21
> -C*model*a4techKBS8*A4Tech KBS-8
> -C*model*a4_rfkb23*A4Tech Wireless Desktop RFKB-23
> [...]
> -zh_TW*layout*sn*渥魯夫語
> -zh_TW*variant*sn**渥魯夫語
>  EOF
>  }
>  
>
> Couldn't this be the cause of the problem?

I'm pretty sure it is.  The list of keyboard models is generated by
running "./kbdnames-maker KeyboardNames.pl" from the Keyboard/
directory, and currently this command does not print anything.  I
tracked the problem down to the removal of the current directory from
@INC in perl, running "perl -I. kbdnames-maker KeyboardNames.pl" gives
the long list of keyboard models again.

HTH,
Sven

Bug#838418: font corruption and dialogs extremely slow to open

[Rene Engelhard]

On Thu, Sep 22, 2016 at 01:02:16PM +0200, Pierre Haessig wrote:
> Just to confirm that indeed Libreoffice 5.2.1-1 in testing also has the
> issue. Sorry I don't remember when it appeared, but as Simon John said,
> it was some time between late August and the first half of September.
> 
> I also want to add one symptom that I have (and maybe Simon John can
> confirm?): dialogs are extremely slow to open. One example is the
> paragraph style dialog in Libreoffice writer.

Not again mixing different things in bugs, please..

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838002

So that one is fixed with 5.2.1-3.

(that was the first part; a second part will be backported which will make
it more faster, too.)

Regards,

Rene

Bug#838418: Bug#838549: libreoffice-gtk3: Fails to make libreoffice work

[Rene Engelhard]

tag 838549 + moreinfo
tag 838418 + moreinfo
thanks

[ also CCing #838418. maybe the same reason? ]

Hi,

On Thu, Sep 22, 2016 at 10:45:45AM +0200, Rene Engelhard wrote:
> On Thu, Sep 22, 2016 at 10:34:49AM +0200, Rene Engelhard wrote:
> > On Thu, Sep 22, 2016 at 09:50:33AM +0200, Rene Engelhard wrote:
> > > >  more important, I was no longer able to export in PDF.
> > > > Exporting to PDF, when not crashing the application, produces a file
> > > > with garbage random characters.
> > > 
> > > That needs to be tried...
> > 
> > Just tried it in a clean sid chroot + LO + libreoffice-gnome (which installs
> > also -gtk3)
> > 
> > New document, "Test", export to PDF. Indeed I get something looking like 
> > "dfiffjfk" :(
> > 
> > As counter-check: works with -gtk2...
> > 
> > Let's use this bug for this, the (probably) only thing which makes sense in 
> > this
> > report.
> 
> More tests: After a downgrade to libbgtk-3-0 3.20.9-1 it works again. So one 
> more
> bug introduced by the Gtk update, which also means that your Version: field 
> was wrong
> to begin with as it's not new in 5.2.1-3...

We discussed this on IRC today:

10:17 < _rene_> caolan: new churns of "gtk3 is brokenone" coming in. 
seen https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838418? 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838549 is 
basically not useful.)
10:17 < loircbot> LibreOffice (core) noel.grandin * 
  sc/source/core/tool/charthelper.cxx: tdf#101894 Copying a 
  single sheet with a chart on it garbles the chart
10:20 -!- JoNi 
  [~chatzi...@ipservice-092-208-087-160.092.208.pools.vodafone-ip.de] 
  has joined #libreoffice-dev
10:21 -!- aruiz [~aruiz@90.216.49.139] has joined #libreoffice-dev
10:22 <@caolan> _rene_: and do you have 
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-5-2=2c91b
27a968afb36b77e447dd623bbe81ea542f0 applied ?
0:22 < IZBot> core - Resolves: rhbz#1373933 gtk 3.21 emits a lot more 
   "style-set" signals
10:22 -!- willcooke [~willcooke@ubuntu/member/willcooke] has quit [Remote host 
  closed the connection]
10:23 <@caolan> _rene_: also, that reminds me, I think you mentioned some deb 
bug about the libreoffice icons not correct under gnome ? 
https://bugzilla.gnome.org/show_bug.cgi?id=771731 for the 
upstream fix for that if so
10:24 < _rene_> caolan: yep, that was the point if 5.2.1-3
10:24 < _rene_> 2c91b27a968afb36b77e447dd623bbe81ea542f0 I mean
10:24 < IZBot> core - Resolves: rhbz#1373933 gtk 3.21 emits a lot more 
   "style-set" signals - 
http://cgit.freedesktop.org/libreoffice/core/commit/?id=2c91b27a968afb36b77e447dd623bbe81ea542f0
10:25 <@caolan> then its an unknown problem
10:25 <@caolan> "I tried reverting to libgtk-3-0_3.20.9-1_amd64.deb and it made 
no difference" makes it sound unrelated to the style-set thing
10:26 <@caolan> I got 3.20.9 here and I'm as happy as a clam
10:26 -!- xrmx [~rm@213.215.163.27] has joined #libreoffice-dev
10:26 -!- xrmx [~rm@213.215.163.27] has quit [Changing host]
10:26 < _rene_> yeah, I just asked him to go sure
10:26 < _rene_> the problem is, we do have 3.21/3.22 in testing/unstable.
[...]
10:34 <@caolan> _rene_: this is good I guess, you can try a gtk3 downgrade to 
isolate if that's the trigger or not ?
[...]
10:41 < _rene_> caolan: after downgrade it works
[...]
10:44 <@caolan> _rene_: when you saw the problem with pdf export, where did you 
see it, in the pdf export dialog itself, or the outputted pdf ?
[...]
10:44 < _rene_> caolan: the outputted PDF. entered Test in a odt, export, got 
something looking like "dfiffjfk"
10:44 < buovjaga> some deeper philosophy, do we close this as wontfix for now? 
  tdf#101746
10:44 < IZBot> LibreOffice-framework normal/medium UNCONFIRMED all operations 
   of one Libreoffice application are quued one-thread 
   https://bugs.documentfoundation.org/show_bug.cgi?id=101746
10:45 <@caolan> let me upgrade to gtk3 and check that out locally
10:46  * _rene_ updates the bug
[...]
10:56 <@caolan> _rene_: no problem for me on F24 if I upgrade to rawhide 
gtk3-3.22.0 and export to pdf (even if I revert the style-set 
patch) so I got nothing useful
10:57 -!- lplatypus [~chatzilla@101.161.34.40] has joined #libreoffice-dev
10:57 < _rene_> hrmpf.
10:59 < _rene_> hrm, now it worked here, too? wtf?
10:59 <@caolan> this is not the bug you are looking for
10:59  * caolan waves hand mystically
10:59 < _rene_> ah, no, wait
10:59 < _rene_> -rw-r--r--  1 root root 6263 Sep 22 08:58 Test.pdf
10:59 < _rene_> too old :)
[...]
11:34 < _rene_> caolan: rechecked again, timestamp was confusing. it's as I 
said, 3.20 works, 3.22 not...
[...]
11:37 <@caolan> _rene_: I just downloaded 

Processed: Re: Bug#838549: libreoffice-gtk3: Fails to make libreoffice work

[Debian Bug Tracking System]

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

> tag 838549 + moreinfo
Bug #838549 [libreoffice-gtk3] libreoffice-gtk3: PDF export broken since Gtk3 
3.21.x
Added tag(s) moreinfo.
> tag 838418 + moreinfo
Bug #838418 [libreoffice-gtk3] libreoffice-gtk3: Font corruption - both content 
and dialogs
Ignoring request to alter tags of bug #838418 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#755992: proftpd-mod-clamav: error: Can not stat file (9): Bad file descriptor

[Hilmar Preuße]

Am 25.07.2014 um 11:43 schrieb Stanislav German-Evtushenko:

Hi all,


mod_clamav.c doesn't work and reports "error: Can not stat file (9): Bad
file descriptor" on a new file coming to ftp folder. As I discovered with
strace it closes a file descriptor before it tries to "stat" that
descriptor.

I assume that it has been fixed in [1], Further I suspect(!) that the 
fix is already in our git repository. I've build packages based on our 
git[2] for i386. Would you be so kind to test them?


If you need other arches (e.g. amd64) please call back.

Regards,
  Hilmar

[1] 
https://github.com/jbenden/mod_clamav/commit/ee6e8e20421e4eb1e521d1afca9e361640f6f9e3

[2] https://freeshell.de/~hille42/proftpd_mod_clamav/
--
http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

Control: found -1 1.150

On 2016-09-22 12:45:09 +0200, Vincent Lefevre wrote:
> In the keyboard-configuration 1.148 binary package, one has:
> 
> -rwxr-xr-x 1 1862421 2016-07-29 08:06:33 DEBIAN/config
> 
> But in the 1.149 version:
> 
> -rwxr-xr-x 1 48945 2016-09-18 17:53:38 DEBIAN/config

Version 1.150, which has just appeared in unstable, has the same
issue. And upgrading doesn't fix the problem.

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

Processed: Re: Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.150
Bug #838310 [keyboard-configuration] keyboard-configuration: user configuration 
lost + error message from setupcon
Marked as found in versions console-setup/1.150.

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

Processed: affects

[Debian Bug Tracking System]

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

> affects 837618 src:w3c-sgml-lib
Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837620 [xml-core] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837618 affects src:w3c-sgml-lib
Added indication that 837620 affects src:w3c-sgml-lib
Added indication that 837745 affects src:w3c-sgml-lib
>
End of message, stopping processing here.

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

Processed: Re: [Pkg-sugar-devel] Bug#836889: sugar: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Debian Bug Tracking System]

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

> reassign 836889 cdbs
Bug #836889 {Done: Chris Lamb } [src:sugar] sugar: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:sugar' to 'cdbs'.
No longer marked as found in versions sugar/0.106.1-1.
Ignoring request to alter fixed versions of bug #836889 to the same values 
previously set
> affects 836889 src:sugar
Bug #836889 {Done: Chris Lamb } [cdbs] sugar: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Added indication that 836889 affects src:sugar
> thanks
Stopping processing here.

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

Bug#836889: [Pkg-sugar-devel] Bug#836889: sugar: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Santiago Vila]

reassign 836889 cdbs
affects 836889 src:sugar
thanks

This is still failing for me in unstable, and it's also failing here:

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

I think this is Bug #837006, which is not fixed yet.

Feel free to triple-check :-) but for now I'm doing the usual reassign + 
affects,
and leave the merge and reopening to Jonas.

Thanks.

Bug#838418: font corruption and dialogs extremely slow to open

[Pierre Haessig]

Just to confirm that indeed Libreoffice 5.2.1-1 in testing also has the
issue. Sorry I don't remember when it appeared, but as Simon John said,
it was some time between late August and the first half of September.

I also want to add one symptom that I have (and maybe Simon John can
confirm?): dialogs are extremely slow to open. One example is the
paragraph style dialog in Libreoffice writer.

Thanks Simon John for the workaround: indeed uninstalling
libreoffice-gtk3 solves the issue (UI style becomes ugly, but it works!)

best,
Pierre

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

In the keyboard-configuration 1.148 binary package, one has:

-rwxr-xr-x 1 1862421 2016-07-29 08:06:33 DEBIAN/config

But in the 1.149 version:

-rwxr-xr-x 1 48945 2016-09-18 17:53:38 DEBIAN/config

The diff:

--- keyboard-configuration_1.148_all/DEBIAN/config  2016-07-29 
08:06:33.0 +0200
+++ keyboard-configuration_1.149_all/DEBIAN/config  2016-09-18 
17:53:38.0 +0200
@@ -159,33732 +159,6 @@
 
 all_kbdnames () {
  cat <<'EOF'
-C*model*a4techKB21*A4Tech KB-21
-C*model*a4techKBS8*A4Tech KBS-8
-C*model*a4_rfkb23*A4Tech Wireless Desktop RFKB-23
[...]
-zh_TW*layout*sn*渥魯夫語
-zh_TW*variant*sn**渥魯夫語
 EOF
 }
 

Couldn't this be the cause of the problem?

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

Processed: affects

[Debian Bug Tracking System]

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

> affects 837618 src:docbook-xsl
Bug #837618 [xml-core] docbook-slides: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837620 [xml-core] w3-dtd-mathml: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Bug #837745 [xml-core] sgml-data: FTBFS: dh_installxmlcatalogs: Unexpected 
debhelper version format
Added indication that 837618 affects src:docbook-xsl
Added indication that 837620 affects src:docbook-xsl
Added indication that 837745 affects src:docbook-xsl
>
End of message, stopping processing here.

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

Bug#836614: marked as done (animals: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 10:19:24 +
with message-id 
and subject line Bug#836614: fixed in animals 201207131226-2
has caused the Debian Bug report #836614,
regarding animals: please drop the build dependency on hardening-wrapper
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.)


-- 
836614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: animals
Version: 201207131226-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-wrapper
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: animals
Source-Version: 201207131226-2

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

Debian distribution maintenance software
pp.
Alberto Fuentes  (supplier of updated animals 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: Sun, 11 Sep 2016 20:20:18 +0200
Source: animals
Binary: animals
Architecture: source amd64
Version: 201207131226-2
Distribution: unstable
Urgency: medium
Maintainer: Alberto Fuentes 
Changed-By: Alberto Fuentes 
Description:
 animals- Traditional AI animal guessing engine using a binary tree DB
Closes: 836614
Changes:
 animals (201207131226-2) unstable; urgency=medium
 .
   * Switch to dh
   * Compat bump to 9
   * Drop -dbg package to transition to new dbgsym package
   * drop hardening-wrapper (Closes: #836614)
Checksums-Sha1:
 cb669436729a0c816e52d7f85fba10a675e305e8 1752 animals_201207131226-2.dsc
 5df0c446600b2967df98f06eee457f4063446d2d 4692 
animals_201207131226-2.debian.tar.xz
 6f668c75b6295117bfa6af6a15c3eb5c2eba0101 145558 
animals-dbgsym_201207131226-2_amd64.deb
 7273bf0d144bc52729e6b2a5a31e23f4d2c7fc52 22936 animals_201207131226-2_amd64.deb
Checksums-Sha256:
 7dbfc1777d50546d8585ef5c0203895f8fd2e0e7ceeada13d2c8fdd230279b38 1752 
animals_201207131226-2.dsc
 2c735d752e57489d49b739c59e42335b4812f97d4f07ec346c5a389e601b5fdd 4692 
animals_201207131226-2.debian.tar.xz
 233d3d20c865072585a22ff59ff57e133abdb7267e5a804a115a36982450222a 145558 
animals-dbgsym_201207131226-2_amd64.deb
 2469a4b09b9afb83fab34ee3a96141fc01642a3d202af4844c1164b0f19f54ad 22936 
animals_201207131226-2_amd64.deb
Files:
 1493ca4c97b3f86890a277c2882230f1 1752 games optional animals_201207131226-2.dsc
 29450e53762faf2395d57402b843575c 4692 games optional 
animals_201207131226-2.debian.tar.xz
 0fbcf6aa166de356d6faade83161753d 145558 debug extra 
animals-dbgsym_201207131226-2_amd64.deb
 a82bdd46f61b2437b1829afd3bec073d 22936 games optional 
animals_201207131226-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJX45cAAAoJEBLZsEqQy9jk2CoP/jb8FiMcMcnpDQvV5/HLncm9
SEECsVv8tKBzOEe+V467PXWjYP6JH/RO0EUmj7/rQfv/phwppaY98umm0wsZni6t
j2sjnD4RL+dN+doiLYnlq1v/ZvHrvAP6AniypiSVhivkj2IKEZbV6YxKyrqCHazz
2gtT750ZWO9+qbnQj1LazdfPhDDZ8GUBeOqampKnhRTd8tOcJ/3vVb0AErfXBtrx
cU2XemAVTJRyB0psSy0VDYtpWSghnTBuarGJ3DJ2xtRct5hqpz20/cMnEy7AeBLY
1kkXOV40UTVes00JfNlizcIxT2ZnBNG3HbUmoW2GtdPmBLC9qBN6BQ0dJu9W+H5B
q95DmxVks9eyfwqARZgQ8hFZpeGKr215cAFHcy8/Ml/U4bZG2aDYoRHK/4FtNKDm
umnngJm61wE4pkGvnom1sJtgxA06m2cRrUqfoYq0Hu2dPy9HlLD6bQcPlbCBKl1J
npQ/ekEPhL36lE5YXGMOjEup2TvqaF9+ui/JoQoeaSlmSITaijLHwWi17sCbmILS
Q1LYoyXh/D47lW4/mf6utagihnNmOFOOxR5gkHF+OeTkqxYMOR3avk5Pj9W44HjU
dpmX4yTkhVeyhquB7+/BVvHSGE+zhAD2by0UIl7R8n2r7yYdQVTYs1/kpu2yAj7W
I1F5xZiFxuoJnuxqfCmA
=8Ool
-END PGP SIGNATURE End Message ---

Bug#837329: marked as done (ndiswrapper-dkms: module FTBFS against Linux 4.7)

[Debian Bug Tracking System]

Your message dated Thu, 22 Sep 2016 10:23:26 +
with message-id 
and subject line Bug#837329: fixed in ndiswrapper 1.60-3
has caused the Debian Bug report #837329,
regarding ndiswrapper-dkms: module FTBFS against Linux 4.7
to be marked as done.

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

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


-- 
837329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ndiswrapper-dkms
Version: 1.60-2
Severity: serious
Justification: fails to build from source

Hi,

the kernel module cannot be built against the latest kernel in sid:

/var/lib/dkms/ndiswrapper/1.60/build/make.log:

DKMS make.log for ndiswrapper-1.60 for kernel 4.7.0-1-amd64 (x86_64)
Sat Sep 10 15:27:52 UTC 2016
make: Entering directory '/usr/src/linux-headers-4.7.0-1-amd64'
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h
  MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h
  LD  /var/lib/dkms/ndiswrapper/1.60/build/built-in.o
  MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/hal.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/loader.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/pnp.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/proc.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/rtl.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/usb.o
  AS [M]  /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o
  AS [M]  /var/lib/dkms/ndiswrapper/1.60/build/lin2win.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/crt.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ndis.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o
  CC [M]  /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o
/var/lib/dkms/ndiswrapper/1.60/build/wrapndis.c: In function 'tx_worker':
/var/lib/dkms/ndiswrapper/1.60/build/wrapndis.c:707:16: error: 'struct 
net_device' has no member named 'trans_start'
wnd->net_dev->trans_start = jiffies;
^
/usr/src/linux-headers-4.7.0-1-common/scripts/Makefile.build:294: recipe for 
target '/var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o' failed
make[3]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o] Error 1
make[3]: *** Waiting for unfinished jobs
/usr/src/linux-headers-4.7.0-1-common/Makefile:1474: recipe for target 
'_module_/var/lib/dkms/ndiswrapper/1.60/build' failed
make[2]: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2
Makefile:150: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.7.0-1-amd64'


Andreas
--- End Message ---
--- Begin Message ---
Source: ndiswrapper
Source-Version: 1.60-3

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

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated ndiswrapper 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, 22 Sep 2016 11:01:46 +0200
Source: ndiswrapper
Binary: ndiswrapper ndiswrapper-source ndiswrapper-dkms ndiswrapper-utils-1.9
Architecture: source
Version: 1.60-3
Distribution: unstable
Urgency: medium
Maintainer: Julian Andres Klode 
Changed-By: Julian Andres Klode 
Description:
 ndiswrapper - Userspace utilities for the ndiswrapper Linux kernel module
 

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

On 2016-09-22 11:10:45 +0200, Vincent Lefevre wrote:
> On 2016-09-22 01:29:12 +0300, Anton Zinoviev wrote:
> > On Mon, Sep 19, 2016 at 07:31:12PM +0200, Vincent Lefevre wrote:
> > > -XKBMODEL="pc105"
> > > +XKBMODEL=""
> > >  XKBLAYOUT="gb"
> > >  XKBVARIANT=""
> > >  XKBOPTIONS=""
> > 
> > This doesn't look as a file created by console-setup.
> 
> It is created by "dpkg-reconfigure keyboard-configuration".
[...]

I have a 3rd machine (which doesn't use systemd).

ypig:~> cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""

BACKSPACE="guess"

So, this is OK before the upgrade. Then, I upgraded only the
following with aptitude:

Preconfiguring packages ...
(Reading database ... 556584 files and directories currently installed.)
Preparing to unpack .../0-console-setup-linux_1.149_all.deb ...
Unpacking console-setup-linux (1.149) over (1.148) ...
Preparing to unpack .../1-console-setup_1.149_all.deb ...
Unpacking console-setup (1.149) over (1.148) ...
Preparing to unpack .../2-keyboard-configuration_1.149_all.deb ...
Unpacking keyboard-configuration (1.149) over (1.148) ...
Setting up keyboard-configuration (1.149) ...
Processing triggers for systemd (231-7) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up console-setup-linux (1.149) ...
Setting up console-setup (1.149) ...

I got a question:

  Configuring keyboard-configuration

  The current keyboard layout in the configuration file
  /etc/default/keyboard is defined as XKBLAYOUT="gb" and
  XKBVARIANT="".

  Please choose whether you want to keep it. If you choose this
  option, no questions about the keyboard layout will be asked
  and the current configuration will be preserved.

  Keep the current keyboard layout in the configuration file?



I chose "Yes", so that I didn't expect any change. But now:

ypig:~> cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL=""
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""

BACKSPACE="guess"

which is wrong!!! And /var/cache/debconf/config.dat changed in the
same way as the other machines.

Note: I don't remember getting this question on the other machines,
but the effect was the same.

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

Processed: Bug#834684

[Debian Bug Tracking System]

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

> retitle 834684 python-pbr: FTBFS in testing (failing tests, missing 
> build-depends on gnupg)
Bug #834684 {Done: Thomas Goirand } [src:python-pbr] 
python-pbr: FTBFS too much often (failing tests)
Changed Bug title to 'python-pbr: FTBFS in testing (failing tests, missing 
build-depends on gnupg)' from 'python-pbr: FTBFS too much often (failing 
tests)'.
> thanks
Stopping processing here.

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

Bug#838310: keyboard-configuration: user configuration lost + error message from setupcon

[Vincent Lefevre]

On 2016-09-22 01:29:12 +0300, Anton Zinoviev wrote:
> On Mon, Sep 19, 2016 at 07:31:12PM +0200, Vincent Lefevre wrote:
> > -XKBMODEL="pc105"
> > +XKBMODEL=""
> >  XKBLAYOUT="gb"
> >  XKBVARIANT=""
> >  XKBOPTIONS=""
> 
> This doesn't look as a file created by console-setup.

It is created by "dpkg-reconfigure keyboard-configuration".
If I start with the original /etc/default/keyboard file
(which was the file after the installation of the machine):


# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""

BACKSPACE="guess"


I can reproduce the issue with:

  dpkg-reconfigure -fnoninteractive keyboard-configuration

I get:


# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL=""
XKBLAYOUT="gb"
XKBVARIANT=""
XKBOPTIONS=""

BACKSPACE="guess"


> Because of the missing XKBMODEL, it looks like a file created by
> systemd-localed.service.
> 
> Would you experiment with the command
> 
> # localectl set-keymap 

This has no effect on /etc/default/keyboard.

> and
> 
> # localectl set-x11-keymap ...
> 
> and see if it corrupts /etc/default/keyboard.

This recreates /etc/default/keyboard, but with only 2 lines, e.g.

# localectl set-x11-keymap foo
# cat /etc/default/keyboard
XKBLAYOUT=foo
BACKSPACE=guess

> > I don't know the possible consequences, though. The
> > /usr/share/doc/keyboard-configuration/changelog.gz file just says:
> > 
> > console-setup (1.149) unstable; urgency=medium
> > 
> >   [ Updated translations ]
> >   * Danish (da.po) by Joe Hansen
> 
> If I am right that the file was corrupted by systemd-localed, then 
> /etc/default/keyboard must have been corrupted after the upgrade of 
> console-setup.  If this file was corrupted before the upgrade, then 
> console-setup would have repaired it.
> 
> > Note: I have
> > 
> > -rw-r--r-- 1 root root 145 2016-09-19 19:03:19 /etc/default/keyboard
> > 
> > Thus this file was modified when keyboard-configuration was upgraded
> > (and before this upgrade of the Linux kernel and the nvidia packages).
> 
> Do you know what other packages were upgraded after console-setup and 
> before the Linux kernel and nvidia?

Here's the aptitude log:

Aptitude 0.8.3: log report
Mon, Sep 19 2016 19:00:23 +0200

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 94 packages, and remove 0 packages.
1169 kB of disk space will be freed

[HOLD, DEPENDENCIES] libegl-nvidia0:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libegl1-glvnd-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgl1-nvidia-glx:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgldispatch0-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgles-nvidia1:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgles-nvidia2:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgles1-glvnd-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libgles2-glvnd-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libglx-nvidia0:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libglx0-glvnd-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libnvidia-cfg1:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libnvidia-glcore:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libnvidia-ml1:amd64 361.45.18-2
[HOLD, DEPENDENCIES] libopengl0-glvnd-nvidia:amd64 361.45.18-2
[HOLD, DEPENDENCIES] linux-compiler-gcc-5-x86:amd64 4.7.2-1
[HOLD, DEPENDENCIES] linux-doc-4.7:amd64 4.7.2-1
[HOLD, DEPENDENCIES] linux-headers-4.7.0-1-amd64:amd64 4.7.2-1
[HOLD, DEPENDENCIES] linux-headers-4.7.0-1-common:amd64 4.7.2-1
[HOLD, DEPENDENCIES] linux-kbuild-4.7:amd64 4.7.2-1
[HOLD, DEPENDENCIES] linux-libc-dev:amd64 4.7.2-1
[HOLD, DEPENDENCIES] nvidia-alternative:amd64 361.45.18-2
[HOLD, DEPENDENCIES] nvidia-driver:amd64 361.45.18-2
[HOLD, DEPENDENCIES] nvidia-driver-libs:amd64 361.45.18-2
[HOLD, DEPENDENCIES] nvidia-kernel-support:amd64 361.45.18-2
[HOLD, DEPENDENCIES] nvidia-legacy-check:amd64 361.45.18-2
[HOLD, DEPENDENCIES] nvidia-vdpau-driver:amd64 361.45.18-2
[HOLD, DEPENDENCIES] xserver-xorg-video-nvidia:amd64 361.45.18-2
[HOLD] gcc-snapshot:amd64 20160508-1
[HOLD] libnvidia-eglcore:amd64 361.45.18-2
[HOLD] nvidia-driver-bin:amd64 361.45.18-2
[HOLD] nvidia-kernel-dkms:amd64 361.45.18-2
[UPGRADE] bash:amd64 4.3-15 -> 4.4-1
[UPGRADE] console-setup:amd64 1.148 -> 1.149
[UPGRADE] console-setup-linux:amd64 1.148 -> 1.149
[UPGRADE] fonts-noto:amd64 20160724-2 -> 20160724-3
[UPGRADE] fonts-noto-hinted:amd64 20160724-2 -> 20160724-3
[UPGRADE] fonts-noto-mono:amd64 20160724-2 -> 20160724-3
[UPGRADE] fonts-noto-unhinted:amd64 20160724-2 -> 20160724-3
[UPGRADE] fonts-opensymbol:amd64 2:102.7+LibO5.2.1-2 -> 2:102.7+LibO5.2.1-3
[UPGRADE] fop:amd64 1:2.1-3 -> 1:2.1-4
[UPGRADE] gedit:amd64 3.21.90-2 

Bug#838394: openbabel: FTBFS on mips,mips64el: internal compiler errors

[Julien Cristau]

On Thu, Sep 22, 2016 at 10:34:29 +0300, Niko Tyni wrote:

> @debian-wb-team: could you please give it back to see if it happens
> again on buildds?
> 
>  gb openbabel_2.3.2+dfsg-2.4 . mips mips64el
> 
Given back.

Cheers,
Julien

Processed: Re: Bug#838549: libreoffice-gtk3: Fails to make libreoffice work

[Debian Bug Tracking System]

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

> retitle 838549 libreoffice-gtk3: breaks PDF export
Bug #838549 [libreoffice-gtk3] libreoffice-gtk3: Fails to make libreoffice work
Changed Bug title to 'libreoffice-gtk3: breaks PDF export' from 
'libreoffice-gtk3: Fails to make libreoffice work'.
> severity 838549 important
Bug #838549 [libreoffice-gtk3] libreoffice-gtk3: breaks PDF export
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#838549: libreoffice-gtk3: Fails to make libreoffice work

[Rene Engelhard]

retitle 838549 libreoffice-gtk3: breaks PDF export
severity 838549 important
thanks

Hi,

On Thu, Sep 22, 2016 at 09:50:33AM +0200, Rene Engelhard wrote:
> >  more important, I was no longer able to export in PDF.
> > Exporting to PDF, when not crashing the application, produces a file
> > with garbage random characters.
> 
> That needs to be tried...

Just tried it in a clean sid chroot + LO + libreoffice-gnome (which installs
also -gtk3)

New document, "Test", export to PDF. Indeed I get something looking like 
"dfiffjfk" :(

As counter-check: works with -gtk2...

Let's use this bug for this, the (probably) only thing which makes sense in this
report.

Regards,
 
Rene

Bug#838551: mediawiki: Update breaks mediawiki-extensions, leaving unusable system

[Thomas Erichsen]

Package: mediawiki
Version: 1:1.27.1-2~bpo8+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Today I installed a pending upgrade for mediawiki, leaving my system in a 
complete mess: obviously, the upgrade breaks mediawiki-extensions, from which I 
used several and specifically the Ldap-authentication. I understand, that the 
former extensions are now partly included in the mediawiki package, right? 
Shouldn't there be a note how to configure the system to work again after 
breaking it by this upgrade?

Regards,
Thomas


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mediawiki depends on:
ii  apache2 [httpd]  2.4.10-10+deb8u7
ii  apache2-mpm-prefork [httpd]  2.4.10-10+deb8u7
ii  libjs-jquery 1.7.2+dfsg-3.2
ii  mediawiki-classes1:1.27.1-2~bpo8+1
ii  mime-support 3.58
ii  php5 5.6.24+dfsg-0+deb8u1
ii  php5-common  5.6.24+dfsg-0+deb8u1
ii  php5-mysql   5.6.24+dfsg-0+deb8u1

Versions of packages mediawiki recommends:
ii  mysql-server   5.5.52-0+deb8u1
ii  php-wikidiff2  1.2+git03ea59f-1
ii  php5-cli   5.6.24+dfsg-0+deb8u1
ii  php5-curl  5.6.24+dfsg-0+deb8u1
ii  php5-intl  5.6.24+dfsg-0+deb8u1
ii  python 2.7.9-1

Versions of packages mediawiki suggests:
pn  clamav   
pn  hhvm 
ii  imagemagick  8:6.8.9.9-5+deb8u4
pn  memcached
pn  php5-apcu
ii  php5-gd  5.6.24+dfsg-0+deb8u1

-- Configuration Files:
/etc/apache2/conf-available/mediawiki.conf changed:
Alias /mediawiki /var/lib/mediawiki
Alias /wiki /var/lib/mediawiki

Options +FollowSymLinks
AllowOverride All
= 2.3>

Require ip 134.147.66.128/25
Require ip 10.147.66.128/25
Require ip 134.147.139.128/26
Require ip 10.147.139.128/26
Require ip 127.0.0.1



order allow,deny
allow from all



Options -FollowSymLinks
AllowOverride None

php_admin_flag engine off



Options -FollowSymLinks
AllowOverride None

php_admin_flag engine off



Options -FollowSymLinks
AllowOverride None

php_admin_flag engine off



/etc/mediawiki/apache.conf 2fc573bdfa17c1f85e93dbff87b8face [Errno 2] No such 
file or directory: u'/etc/mediawiki/apache.conf 
2fc573bdfa17c1f85e93dbff87b8face'
/etc/mediawiki/cherokee.conf 9bef51969672b3abea3c9ca960bd1163 [Errno 2] No such 
file or directory: u'/etc/mediawiki/cherokee.conf 
9bef51969672b3abea3c9ca960bd1163'

-- debconf information:
  mediawiki/webserver: apache2

Processed: Re: Bug#838549: libreoffice-gtk3: Fails to make libreoffice work

[Debian Bug Tracking System]

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

> tag 838549 + moreinfo
Bug #838549 [libreoffice-gtk3] libreoffice-gtk3: Fails to make libreoffice work
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#838549: libreoffice-gtk3: Fails to make libreoffice work

[Rene Engelhard]

tag 838549 + moreinfo
thanks

Hi,

On Thu, Sep 22, 2016 at 09:26:06AM +0200, g.l. gragnani wrote:
> after upgrading to libreoffice-gtk3 1:5.2.1-3 I experienced repeted

So so you suggest it worked with 5.2.1-2? -3 is fixing some important stuff
(slwness, see below) up, so I don't think we should leave it blocking
that upload.

> random crashes of lowriter

If that was the case it would already have been reported in the last ~ 5 days,
don't you think?

> random changes of fonts in both dialogs and main window and,

Guess what? This is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838418.
What if you would actually do your bug submitter duties (especially when you
report a RC bug) and check whether stuff already is reported?

>  more important, I was no longer able to export in PDF.
> Exporting to PDF, when not crashing the application, produces a file
> with garbage random characters.

That needs to be tried...

> Purging libreoffice-gtk3 not only fixes the problems, but also make the whole
> application much more responsive.

A bit more responsive. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837356. That is fixed
with 5.2.1-3.

And you believe I should take a broken mix lke

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

seriously? Either you are at sid or not. APT prefers stable-updates is broken
here. Try with clean system.

(And you of couse miss all the other reportbug info)

Regards,

Rene

Bug#838509: proftpd-mod-clamav: please drop the build dependency on hardening-wrapper

[Hilmar Preuße]

notfound 838509 0.10-1
stop

Am 21.09.2016 um 20:30 schrieb Hilmar Preuße:

Package: proftpd-mod-clamav
Version: 0.10-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-wrapper package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-includes
and use the DEB_BUILD_MAINT_OPTIONS settings.

Well, that version statement is actually wrong. The B-D on 
hardening-wrapper is implemented in our git repository (not in unstable) 
and needs to be removed before release.


H.
--
http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org

Processed: Re: Processed: raise severity of hardening-wrapper issues, to be removed for stretch

[Debian Bug Tracking System]

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

> severity 838508 important
Bug #838508 [proftpd-mod-case] proftpd-mod-case: please drop the build 
dependency on hardening-wrapper
Severity set to 'important' from 'serious'
> severity 838509 important
Bug #838509 [proftpd-mod-clamav] proftpd-mod-clamav: please drop the build 
dependency on hardening-wrapper
Severity set to 'important' from 'serious'
> stop
Stopping processing here.

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

Processed: Re: Bug#838509: proftpd-mod-clamav: please drop the build dependency on hardening-wrapper

[Debian Bug Tracking System]

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

> notfound 838509 0.10-1
Bug #838509 [proftpd-mod-clamav] proftpd-mod-clamav: please drop the build 
dependency on hardening-wrapper
No longer marked as found in versions proftpd-mod-clamav/0.10-1.
> stop
Stopping processing here.

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

Processed: raise severity of hardening-wrapper issues, to be removed for stretch

[Debian Bug Tracking System]

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

> severity 838508 serious
Bug #838508 [proftpd-mod-case] proftpd-mod-case: please drop the build 
dependency on hardening-wrapper
Severity set to 'serious' from 'important'
> severity 838509 serious
Bug #838509 [proftpd-mod-clamav] proftpd-mod-clamav: please drop the build 
dependency on hardening-wrapper
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#836677: pysparse: still worth maintaining?

[Ghislain Vaillant]

I have had a look at updating the package to the newest upstream
release and fixing this FTBFS. However, I have got strong concerns as
to whether it is worth keeping this package maintained in the archive:

- The latest release on PyPI [1] is busted (missing files). The issue
was reported [2] but never addressed since.

- Latest activity on the upstream repository is from 2013. By now, I
expected upstream would have fixed the PyPI tarball, at least.

- No Python 3 support. A manual call to 2to3 on the Python sources
allows the build process to run, but fails at the compilation stage.

[1] https://pypi.python.org/pypi/pysparse
[2] https://sourceforge.net/p/pysparse/mailman/message/33117282/

Best regards,
Ghis

Bug#838394: openbabel: FTBFS on mips,mips64el: internal compiler errors

[Niko Tyni]

On Tue, Sep 20, 2016 at 10:43:39PM +0300, Niko Tyni wrote:
> Package: openbabel
> Version: 2.3.2+dfsg-2.4
> Severity: serious
> Control: block 830200 with -1
> 
> This package failed to build on mips and mips64el.
> 
> - on mips:
> "c++: internal compiler error: Segmentation fault (program cc1plus)"
> https://buildd.debian.org/status/fetch.php?pkg=openbabel=mips=2.3.2%2Bdfsg-2.4=1474379322
> 
> - on mips64el:
> "openbabel-perl.cpp:17073:86: internal compiler error: in 
> df_reg_chain_unlink, at df-scan.c:790"
> https://buildd.debian.org/status/fetch.php?pkg=openbabel=mips64el=2.3.2%2Bdfsg-2.4=1474385515
> 
> I'm running test builds on the porter boxes to see if these are
> reproducible there and to gather data for gcc bug reports.

It builds on the porter boxes (minkus and eller). There are some test
failures but those get ignored and don't seem to be regressions. The
gcc version is the same as in the failed builds.

@debian-wb-team: could you please give it back to see if it happens
again on buildds?

 gb openbabel_2.3.2+dfsg-2.4 . mips mips64el

-- 
Niko Tyni   nt...@debian.org

Bug#838549: libreoffice-gtk3: Fails to make libreoffice work

[g.l. gragnani]

Package: libreoffice-gtk3
Version: 1:5.2.1-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after upgrading to libreoffice-gtk3 1:5.2.1-3 I experienced repeted
random crashes of lowriter, random changes of fonts in both dialogs and main
window and, more important, I was no longer able to export in PDF.
Exporting to PDF, when not crashing the application, produces a file
with garbage random characters.
Purging libreoffice-gtk3 not only fixes the problems, but also make the whole
application much more responsive.

Best regards


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

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