Processed: severity of 812680 is serious

[Debian Bug Tracking System]

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

> severity 812680 serious
Bug #812680 [src:python-poppler] python-poppler: FTBFS with Poppler 0.39.0
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#824166: texlive-bin: FTBFS due to luajit issues

[Norbert Preining]

> Well, with TL 2015.20160222 the luajittex package did still exist in
> mips(el). Now, with the new version, the packages would disappear on
> mips(el), which is an regression.

Well, things disappear.

> Make the package build on mips(el) again. ;-) That did work in the past.

Maybe, but I don't want to invest much time into these things.
We have tried many of the same problems when building for tlbuild,
and I don't see that it worked.

So if nobody steps up I will ask release mangers / ftp masters to
remove the pakcage.

Norbert

--
PREINING Norbert + TeX Live & Debian Developer + http://www.preining.info
GPG: 0x860CDC13fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#825600: libmpfi-dev: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: libmpfi-dev
Version: 1.5.1+ds-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  jessie -> stretch

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

1m45.5s ERROR: WARN: Inadequate results from running adequate!
  libmpfi-dev:amd64: missing-copyright-file /usr/share/doc/libmpfi-dev/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libmpfi-dev/copyright
  # ls -lad /usr/share/doc/libmpfi-dev
  drwxr-xr-x 2 root root 40 May 22 17:02 /usr/share/doc/libmpfi-dev
  # ls -la /usr/share/doc/libmpfi-dev/
  total 0
  drwxr-xr-x   2 root root   40 May 22 17:02 .
  drwxr-xr-x 114 root root 2400 May 22 17:02 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


libmpfi-dev_1.5.1+ds-3.log.gz
Description: application/gzip

Bug#816373: marked as done (libscreenlocker5: Missing Replaces: / Conflicts:)

[Debian Bug Tracking System]

Your message dated Sat, 28 May 2016 00:23:53 +
with message-id 
and subject line Bug#814152: fixed in kscreenlocker 5.6.4-1
has caused the Debian Bug report #814152,
regarding libscreenlocker5: Missing Replaces: / Conflicts:
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.)


-- 
814152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libscreenlocker5
Version: 5.5.4-1
Severity: important

Unpacking libkscreenlocker5:amd64 (5.5.4-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libkscreenlocker5_5.5.4-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libexec/kcheckpass', which is 
also in package plasma-workspace 4:5.4.3-1


-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-trunk-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)
--- End Message ---
--- Begin Message ---
Source: kscreenlocker
Source-Version: 5.6.4-1

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated kscreenlocker package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 May 2016 01:54:48 +0200
Source: kscreenlocker
Binary: kscreenlocker-dev libkscreenlocker5 kde-config-screenlocker
Architecture: source
Version: 5.6.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 kde-config-screenlocker - KCM Module for kscreenlocker
 kscreenlocker-dev - Development files for kscreenlocker
 libkscreenlocker5 - Secure lock screen architecture
Closes: 814152
Changes:
 kscreenlocker (5.6.4-1) unstable; urgency=medium
 .
   [ Maximiliano Curia ]
   * Missing epoch in plasma-workspace breaks/replaces. (Closes: #814152)
   * New upstream release (5.5.5).
   * Add a .gitattributes file to use dpkg-mergechangelogs
   * debian/control: Update Vcs-Browser and Vcs-Git fields
   * Fix break/replaces against the l10n packages
   * Add upstream metadata (DEP-12)
   * Update install files.
 .
   [ Automatic packaging ]
   * Update build-deps and deps with the info from cmake
   * Bump Standards-Version to 3.9.8
Checksums-Sha1:
 b476509658f1dd1066607b191d0384d5ed7ba6bc 2853 kscreenlocker_5.6.4-1.dsc
 d2f2026406b20f1fdf35198d8987440f62adf458 104212 kscreenlocker_5.6.4.orig.tar.xz
 e7c6488d8688ac2171369cecb662b25af120be37 3636 
kscreenlocker_5.6.4-1.debian.tar.xz
Checksums-Sha256:
 bcf7ff7f3c154539c687f24dca8352400517181c2048e8cdfeb3ff85ad7eefbd 2853 
kscreenlocker_5.6.4-1.dsc
 104c31bc886358273bfab2f2605fbfb8a1030046b64611483ca1835ce865d02a 104212 
kscreenlocker_5.6.4.orig.tar.xz
 afbc8d19f84f30cf2eb10b8a4e4281f920b8b861506b176310261b9ad2f33c11 3636 
kscreenlocker_5.6.4-1.debian.tar.xz
Files:
 9674797ce115d92f0b3f40c75f3492e3 2853 libs optional kscreenlocker_5.6.4-1.dsc
 3df10c588206b4cfa52bab047c84265d 104212 libs optional 
kscreenlocker_5.6.4.orig.tar.xz
 69366a48624184db0e32709856ecc773 3636 libs optional 
kscreenlocker_5.6.4-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXSN6DAAoJEMcZdpmymyMqyhwP/RU2JrhctorQf0Fjtox58yti
fPsrvSZT+ipHYgKyOhjMwwW8y2Q9mVRRIh/rwGhDXXLTvuT460f0bUjGRrGOgwAE
Syqe6aLTifln8AI2MZ/tu0uZctmQTwEXbwto6TJlogqvEQoD8gcRuI20RlzXaY4M
iKkKs3Je+Sk0MnzL5/HPDoqG5ivlkh3MyGTRSUuN/SJX4W+WfsyMLeA6a7AHb1cE
kw7zvPI+EzCts8DHghGlzGQy53RK3QrIhX499cXBekmUdlLYGL0RyGOk/7fGnQnE
+FcPsxpro6lb3Csh9MKiU7005WhEESauCz10Q0Sn6S88WJ6BwqUJqTnTpRw7L7tb
yfBrAT6ynHyL9K8HnYifXR3ybG2TyloDGMmWM/YDvvXE0AcihYqV3qb4lhIdRE3o
KDP9vnVvfl/EJELT2kxb0JBRz+YjLCQTg0yCHT3Gu0nrbNeC1tRCDObcXL9X/izj

Bug#814152: marked as done ([libkscreenlocker5] Conflict with plasma-workspace)

[Debian Bug Tracking System]

Your message dated Sat, 28 May 2016 00:23:53 +
with message-id 
and subject line Bug#814152: fixed in kscreenlocker 5.6.4-1
has caused the Debian Bug report #814152,
regarding [libkscreenlocker5] Conflict with plasma-workspace
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.)


-- 
814152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkscreenlocker5
Version: 5.5.4-1
Severity: normal

Unpacking libkscreenlocker5:amd64 (5.5.4-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libkscreenlocker5_5.5.4-1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libexec/kcheckpass', which is 
also in package plasma-workspace 4:5.4.3-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack .../kde-config-screenlocker_5.5.4-1_amd64.deb ...
Unpacking kde-config-screenlocker (5.5.4-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/kde-config-screenlocker_5.5.4-1_amd64.deb (--unpack):
trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qt5/plugins/screenlocker_kcm.so', which is also in 
package plasma-workspace 4:5.4.3-1
Processing triggers for libc-bin (2.21-7) ...
--- End Message ---
--- Begin Message ---
Source: kscreenlocker
Source-Version: 5.6.4-1

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated kscreenlocker package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 May 2016 01:54:48 +0200
Source: kscreenlocker
Binary: kscreenlocker-dev libkscreenlocker5 kde-config-screenlocker
Architecture: source
Version: 5.6.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 kde-config-screenlocker - KCM Module for kscreenlocker
 kscreenlocker-dev - Development files for kscreenlocker
 libkscreenlocker5 - Secure lock screen architecture
Closes: 814152
Changes:
 kscreenlocker (5.6.4-1) unstable; urgency=medium
 .
   [ Maximiliano Curia ]
   * Missing epoch in plasma-workspace breaks/replaces. (Closes: #814152)
   * New upstream release (5.5.5).
   * Add a .gitattributes file to use dpkg-mergechangelogs
   * debian/control: Update Vcs-Browser and Vcs-Git fields
   * Fix break/replaces against the l10n packages
   * Add upstream metadata (DEP-12)
   * Update install files.
 .
   [ Automatic packaging ]
   * Update build-deps and deps with the info from cmake
   * Bump Standards-Version to 3.9.8
Checksums-Sha1:
 b476509658f1dd1066607b191d0384d5ed7ba6bc 2853 kscreenlocker_5.6.4-1.dsc
 d2f2026406b20f1fdf35198d8987440f62adf458 104212 kscreenlocker_5.6.4.orig.tar.xz
 e7c6488d8688ac2171369cecb662b25af120be37 3636 
kscreenlocker_5.6.4-1.debian.tar.xz
Checksums-Sha256:
 bcf7ff7f3c154539c687f24dca8352400517181c2048e8cdfeb3ff85ad7eefbd 2853 
kscreenlocker_5.6.4-1.dsc
 104c31bc886358273bfab2f2605fbfb8a1030046b64611483ca1835ce865d02a 104212 
kscreenlocker_5.6.4.orig.tar.xz
 afbc8d19f84f30cf2eb10b8a4e4281f920b8b861506b176310261b9ad2f33c11 3636 
kscreenlocker_5.6.4-1.debian.tar.xz
Files:
 9674797ce115d92f0b3f40c75f3492e3 2853 libs optional kscreenlocker_5.6.4-1.dsc
 3df10c588206b4cfa52bab047c84265d 104212 libs optional 
kscreenlocker_5.6.4.orig.tar.xz
 69366a48624184db0e32709856ecc773 3636 libs optional 
kscreenlocker_5.6.4-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXSN6DAAoJEMcZdpmymyMqyhwP/RU2JrhctorQf0Fjtox58yti
fPsrvSZT+ipHYgKyOhjMwwW8y2Q9mVRRIh/rwGhDXXLTvuT460f0bUjGRrGOgwAE
Syqe6aLTifln8AI2MZ/tu0uZctmQTwEXbwto6TJlogqvEQoD8gcRuI20RlzXaY4M
iKkKs3Je+Sk0MnzL5/HPDoqG5ivlkh3MyGTRSUuN/SJX4W+WfsyMLeA6a7AHb1cE
kw7zvPI+EzCts8DHghGlzGQy53RK3QrIhX499cXBekmUdlLYGL0RyGOk/7fGnQnE
+FcPsxpro6lb3Csh9MKiU7005WhEESauCz10Q0Sn6S88WJ6BwqUJqTnTpRw7L7tb
yfBrAT6ynHyL9K8HnYifXR3ybG2TyloDGMmWM/YDvvXE0AcihYqV3qb4lhIdRE3o

Bug#825585: libelk0-dev: missing Depends: libelk0 (= ${binary:Version})

[Andreas Beckmann]

Package: libelk0-dev
Version: 3.99.8-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your -dev package misses a
dependency on the corresponding library package libelk0.


Andreas

Bug#825583: libopencv-gpu-dev: missing Depends: libopencv-gpu2.4v5

[Andreas Beckmann]

Package: libopencv-gpu-dev
Version: 2.4.9.1+dfsg-1.5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your -dev package misses a dependency
on the corresponding library package libopencv-gpu2.4v5.


Andreas

Bug#825580: libxen-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libxlutil.so -> libxlutil.so.

[Andreas Beckmann]

Package: libxen-dev
Version: 4.6.0-1+nmu2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships a broken
symlink:

/usr/lib/x86_64-linux-gnu/libxlutil.so -> libxlutil.so.

(notice the trailing dot, it is part of the target).
You probably want this target instead:

libxlutil-4.6.so


Andreas

Bug#825579: libemos-data: ships broken symlink /usr/share/emos/land_sea_mask -> /interpol

[Andreas Beckmann]

Package: libemos-data
Version: 2:4.4.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships a broken
symlink:

/usr/share/emos/land_sea_mask -> /interpol

A much more likely and existing target would be

/usr/share/emos/interpol


Andreas

Processed: limit source to php-sabre-vobject, tagging 825572

[Debian Bug Tracking System]

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

> limit source php-sabre-vobject
Limiting to bugs with field 'source' containing at least one of 
'php-sabre-vobject'
Limit currently set to 'source':'php-sabre-vobject'

> tags 825572 + pending
Bug #825572 [php-sabre-vobject] php-sabre-vobject: broken symlink 
/usr/bin/vobjectvalidate -> ../Sabre/VObject/vobjectvalidate.php
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#823112: opensips: switch from freeradius-client to radcli

[Julián Moreno Patiño]

Hello Razvan Crainea,

Just change libfreeradius-client-dev | libradiusclient-ng-dev
build dependencies to libradcli-dev.

Kind regards,

-- 
Julián Moreno Patiño
Debian Developer
 .''`. Debian GNU/{Linux,KfreeBSD}
: :' : Free Operating Systems
`. `'  http://debian.org/
  `-   GPG Fingerprint:
C2C8 904E 314C D8FA 041D 9B00 D5FD FC15 6168 BF60
Registered GNU Linux User ID 488513


signature.asc
Description: PGP signature

Bug#820476: opensips: unsatisfiable dependency on db4.6-util

[Julián Moreno Patiño]

Hello Razvan Crainea,

Just change db4.6-util dependency to db-util (>= 4.6.19)
in opensips-berkeley-module.

Kind regards,

-- 
Julián Moreno Patiño
Debian Developer
 .''`. Debian GNU/{Linux,KfreeBSD}
: :' : Free Operating Systems
`. `'  http://debian.org/
  `-   GPG Fingerprint:
C2C8 904E 314C D8FA 041D 9B00 D5FD FC15 6168 BF60
Registered GNU Linux User ID 488513


signature.asc
Description: PGP signature

Bug#825528: marked as done (ndiff: jessie-proposed-updates: uninstallable together with zenmap)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 22:32:30 +
with message-id 
and subject line Bug#825528: fixed in nmap 6.47-3+deb8u2
has caused the Debian Bug report #825528,
regarding ndiff: jessie-proposed-updates: uninstallable together with zenmap
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.)


-- 
825528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ndiff
Version: 6.47-3+deb8u1
Severity: grave
Justification: renders package unusable
Tags: jessie

The current ndiff package in jessie-proposed-updates is considered
uninstallable by at least aptitude when zenmap is installed.

This probably happens because ndiff in jessie-proposed-updates declares
Breaks and Replaces on zenmap (<< 6.47-5~), instead of 6.47-3+deb8u1.

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

Versions of packages ndiff recommends:
ii  nmap  6.47-3+b1

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--- End Message ---
--- Begin Message ---
Source: nmap
Source-Version: 6.47-3+deb8u2

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated nmap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 May 2016 17:50:57 +0200
Source: nmap
Binary: nmap zenmap ndiff
Architecture: source amd64 all
Version: 6.47-3+deb8u2
Distribution: jessie
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description:
 ndiff  - The Network Mapper - result compare utility
 nmap   - The Network Mapper
 zenmap - The Network Mapper Front End
Closes: 825528
Changes:
 nmap (6.47-3+deb8u2) jessie; urgency=medium
 .
   * Fix versioned Breaks/Depends for ndiff (Closes: #825528)
Checksums-Sha1:
 4986dc444a3377e78cc1b15ec3211658ecf8bbfb 2029 nmap_6.47-3+deb8u2.dsc
 8eb24c36f98e1bd9c99988d9f21535b3a863023d 29424 nmap_6.47-3+deb8u2.debian.tar.xz
 d9e78340c24a8a95ff787eeb75df4e5c2ae5ae20 3972832 nmap_6.47-3+deb8u2_amd64.deb
 4ca306fdc7920aad76b753cbe04601839a1ab8b8 642488 zenmap_6.47-3+deb8u2_all.deb
 2ab931f8d1421964ba7d362ab38097f9cd5f4eb7 256722 ndiff_6.47-3+deb8u2_all.deb
Checksums-Sha256:
 bc1d940b547b8915fdd6a9fb68ddf0b86c7ec1ec47ad7db51c9cdd13f0b84608 2029 
nmap_6.47-3+deb8u2.dsc
 e4c07753f4d35f8429b7447b8184246746b7c838c25bf3ac08b1b932a2640571 29424 
nmap_6.47-3+deb8u2.debian.tar.xz
 4be6cf4b5ad86fe64d81df78db15ad57a2b86e898a4f5fdc3eb6fb23cd9b9ce5 3972832 
nmap_6.47-3+deb8u2_amd64.deb
 642603fd5ff62ee6cb1777d91ac672c53ecf0bd8f5f4e00ab6dc7e57482b738a 642488 
zenmap_6.47-3+deb8u2_all.deb
 9a1e944b20b3be2360f18f9d4ebfeaa00ea433f749c79031e66049985756dba9 256722 
ndiff_6.47-3+deb8u2_all.deb
Files:
 8f41ae0a4a732b669899b868f0166b72 2029 net extra nmap_6.47-3+deb8u2.dsc
 d08f78879a47476d39d29f553feb13a4 29424 net extra 
nmap_6.47-3+deb8u2.debian.tar.xz
 d3e85219b7d16199763e5bd9c6ad57aa 3972832 net extra nmap_6.47-3+deb8u2_amd64.deb
 254dd4d300a477362bcba975fe2212cb 642488 net extra zenmap_6.47-3+deb8u2_all.deb
 a125dcf0e8d7fc57e97a3c0982b7633b 256722 net extra ndiff_6.47-3+deb8u2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXSJHcAAoJEHW3EGNcITp+VIEP/1QSlK441s3ZWCjtykpacdZC
DSX3dZCSeZVqr1DUtJpu4lEYrSB1BhaWw8H0qEhfTuRYab8DWVvnfhXHBRupZsi6
1n1kiWVuN2NoNzsj11+imuiRfToTOU87Ky11wzsUcsU6LSQ7gs+Xm8KdE4uEvFvM
lRRlGKXCm0nUefMZbVlqwGJ/XLSEtIPxb6Hq+wERWEdE7wA1wctHVq9OPRW9n3Fs
VoAeoidJEIYWcveUOvcNSgHcPeuQIqB9y/UAzvdihIzwNhdqIEER6g9sW54l35d+
98ITYsjjNnZ0sDknWubyrI/Jw/ZerEt9cuPa8roVwXNSKvwfitHlLN/s9Yz+5G3A
ou2Ez/lilFzUvvY3YXQwsrHLaayfD/bkgJ2y15YCTMOaksRzpmuGW1kU8Pts02TI

Bug#825572: php-sabre-vobject: broken symlink /usr/bin/vobjectvalidate -> ../Sabre/VObject/vobjectvalidate.php

[Andreas Beckmann]

Package: php-sabre-vobject
Version: 2.1.7-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships a broken
symlink in /usr/bin:

  /usr/bin/vobjectvalidate -> ../Sabre/VObject/vobjectvalidate.php

An existing target would be 

  /usr/share/php/Sabre/VObject/vobjectvalidate.php


Andreas

Bug#742429: (not) fixed in isenkram 0.23

[Tobias Frost]

Hi Petter,

Looking into it, I think the Depenencies needs to be adjusted as this:

However, isenkram is still importing lots of aptdaemon stuff,
so guess this bug needs more hands-on (I read it that this was the goal
for this bug report) 

--
tobi


diff -Nru isenkram-0.23/debian/control isenkram-0.24/debian/control
--- isenkram-0.23/debian/control2015-12-18 16:40:51.0
+0100
+++ isenkram-0.24/debian/control2016-05-27 23:07:51.0
+0200
@@ -5,8 +5,8 @@
 Build-Depends: debhelper (>= 9), po-debconf
 Build-Depends-Indep: dash (>= 0.5.4-12)
   , python (>= 2.6.6-3~)
-  , aptdaemon
-  , python-aptdaemon.gtk3widgets
+  , packagekit
+  , gir1.2-packagekitglib-1.0
   , libgnome2-perl
   , python-gi,
   , gir1.2-gudev-1.0
@@ -24,7 +24,6 @@
 Depends: ${misc:Depends}
   , ${python:Depends}
   , isenkram-cli
-  , python-aptdaemon.gtk3widgets
   , libgnome2-perl
   , python-gi,
   , gir1.2-gudev-1.0
@@ -44,6 +43,8 @@
   , python-gi
   , gir1.2-appstream
   , lsb-release
+  , packagekit
+  , gir1.2-packagekitglib-1.0
 Replaces: isenkram (<< 0.9+exp.1)
 Breaks: isenkram (<< 0.9+exp.1)
 Description: Suggest packages to install when inserting new hardware
(CLI tool)

Processed: severity of 822962 is normal, severity of 825129 is normal, severity of 825094 is normal ...

[Debian Bug Tracking System]

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

> severity 822962 normal
Bug #822962 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: kig [hurd-i386] -- ROM; Newer versions no longer build in 
hurd-i386
Severity set to 'normal' from 'important'
> severity 825129 normal
Bug #825129 {Done: Scott Kitterman } [ftp.debian.org] RM: 
ttf-cjk-compact -- replaced by fonts-droid
Severity set to 'normal' from 'wishlist'
> severity 825094 normal
Bug #825094 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: htcheck-php -- ROM; abandoned upstream, obsolete, doesn't 
support PHP 7.0
Severity set to 'normal' from 'serious'
> severity 823495 normal
Bug #823495 {Done: Scott Kitterman } [ftp.debian.org] RM: 
php5-vtkgdcm -- ROM;doesn't support PHP7.0
Severity set to 'normal' from 'serious'
> severity 821677 normal
Bug #821677 {Done: Scott Kitterman } [ftp.debian.org] RM: 
php5-gdcm -- ROM;doesn't support PHP7.0
Severity set to 'normal' from 'serious'
> severity 804310 normal
Bug #804310 [ftp.debian.org] RM: oxygen-transparent/experimental -- ROM; 
Obsoleted by plasma 5
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#825568: spacefm-gtk3: purging deletes conffile /etc/spacefm/spacefm.conf owned by spacefm-common

[Andreas Beckmann]

Package: spacefm-gtk3
Version: 1.0.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package deletes conffiles
owned by other packages during purge.

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

1m30.5s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/spacefm/spacefm.conf (from spacefm-common package)

The postrm contains:

purge)
#fix 782975
rm -rf /etc/spacefm
;;

which is unsafe. You should only delete the files this package
is responsible for.


Cheers,

Andreas


spacefm-gtk3_1.0.5-1.log.gz
Description: application/gzip

Bug#825564: slapos-node-unofficial: purging deletes configuration file /etc/slapos/slapos-client.cfg

[Andreas Beckmann]

Package: slapos-node-unofficial
Version: 1.3.10-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package deletes configuration
files owned by other packages upon purge.

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

1m10.3s ERROR: FAIL: After purging files have disappeared:
  /etc/slapos/   owned by: slapos-client
  /etc/slapos/slapos-client.cfg  not owned
  /etc/slapos/ssl/   owned by: slapos-client


slapos-node-unofficial.postrm contains:

case "$1" in
purge)
ucf --purge /etc/slapos/slapos-node-unofficial.cfg || true
db_get slapos-node-unofficial/software_root
SOFTWARE_ROOT="$RET"

rm -rf /etc/slapos/ /var/log/slapos/ /var/lib/slapos/ \
/var/cache/slapos/certificates/ "$SOFTWARE_ROOT"
;;
esac

slapos-client.postrm contains:

case "$1" in
purge)
ucf --purge /etc/slapos/slapos-client.cfg || true
rm -rf /etc/slapos/
;;
esac


Both packages are handling /etc/slapos/ in an unsave way.
Only the files managed by that package must be deleted.
slapos-node-unofficial should ship /etc/slapos/ as an empty
directory and let dpkg handle this.


cheers,

Andreas


slapos-node-unofficial_1.3.10-1.log.gz
Description: application/gzip

Bug#825563: fuel-agent, python-fuel-agent: file vs. alternative clash: /usr/bin/fa_fix-configs-on-startup

[Andreas Beckmann]

Package: fuel-agent,python-fuel-agent
Version: 9.0+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your packages do nasty things that
are not covered by piuparts bug reporting templates :-)

fuel-agent ships /usr/bin/fa_fix-configs-on-startup as a file
while python-fuel-agent manages it as an alternative
(and both packages are co-installable)
Luckily both usr/bin/fa_fix-configs-on-startup and
usr/bin/python2-fa_fix-configs-on-startup are identical.

/var/lib/dpkg/info/fuel-agent.md5sums:853956bdd381108ce60974dec11c0de9  
usr/bin/fa_fix-configs-on-startup
/var/lib/dpkg/info/fuel-agent.list:/usr/bin/fa_fix-configs-on-startup
/var/lib/dpkg/info/python-fuel-agent.md5sums:853956bdd381108ce60974dec11c0de9  
usr/bin/python2-fa_fix-configs-on-startup
/var/lib/dpkg/info/python-fuel-agent.postinst:  update-alternatives --install 
/usr/bin/fa_fix-configs-on-startup fa_fix-configs-on-startup 
/usr/bin/python2-fa_fix-configs-on-startup 300
/var/lib/dpkg/info/python-fuel-agent.postrm:update-alternatives --remove 
fa_fix-configs-on-startup /usr/bin/python2-fa_fix-configs-on-startup
/var/lib/dpkg/info/python-fuel-agent.prerm: update-alternatives --remove 
fa_fix-configs-on-startup /usr/bin/python2-fa_fix-configs-on-startup
/var/lib/dpkg/info/python-fuel-agent.list:/usr/bin/python2-fa_fix-configs-on-startup


cheers,

Andreas

Bug#824166: texlive-bin: FTBFS due to luajit issues

[Preuße]

On 27.05.2016 04:21, Norbert Preining wrote:

Hi,

>> Some of those are official architectures, but the arm64, mips
>> and mipsel failures are separate, however ppc64el and s390x
> 
> After disabling mips and mipsel builds of lua*, now texlive-bin
> is not entering testing anymore ...
> 
>   texlive-bin is not yet built on mips: 2015.20160222.37495-1 vs 
> 2016.20160513.41080-2 (missing 2 binaries: libtexluajit-dev, libtexluajit2) 
> 
> Did I miss an important step here? It seems that I need to get rid
> of these packages somehow?
> 
Well, with TL 2015.20160222 the luajittex package did still exist in
mips(el). Now, with the new version, the packages would disappear on
mips(el), which is an regression.

> Any suggestion?
> 
Make the package build on mips(el) again. ;-) That did work in the past.

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

Bug#825561: mpd-sima: leaves statoverrides after purge, breaking dpkg

[Andreas Beckmann]

Package: mpd-sima
Version: 0.14.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to
install, purge, and install again.

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

[first installation went fine]

1m16.1s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp2bGUnx', 'dpkg', 
'--purge', 'mpd-sima']
1m16.6s DUMP: 
  (Reading database ... 9109 files and directories currently installed.)
  Removing mpd-sima (0.14.1-1) ...
  Purging configuration files for mpd-sima (0.14.1-1) ...
  Removing user `mpd-sima' ...
  Warning: group `mpd-sima' has no more members.
  Done.
1m16.6s DEBUG: Command ok: ['chroot', '/tmp/piupartss/tmp2bGUnx', 'dpkg', 
'--purge', 'mpd-sima']

[second installation fails:]
1m26.2s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp2bGUnx', 
'apt-get', '-y', 'install', 'mpd-sima=0.14.1-1']
1m27.5s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Suggested packages:
mpd
  The following NEW packages will be installed:
mpd-sima
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 64.0 kB of archives.
  After this operation, 292 kB of additional disk space will be used.
  Get:1 http://ftp.de.debian.org/debian sid/main amd64 mpd-sima all 0.14.1-1 
[64.0 kB]
  debconf: delaying package configuration, since apt-utils is not installed
  Fetched 64.0 kB in 0s (0 B/s)
  dpkg: unrecoverable fatal error, aborting:
   unknown user 'mpd-sima' in statoverride file
  E: Sub-process /usr/bin/dpkg returned an error code (2)
1m27.5s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmp2bGUnx', 'apt-get', '-y', 'install', 'mpd-sima=0.14.1-1']


cheers,

Andreas


mpd-sima_0.14.1-1.log.gz
Description: application/gzip

Bug#825528: ndiff: jessie-proposed-updates: uninstallable together with zenmap

[Hilko Bengen]

* Henrique de Moraes Holschuh:

> The current ndiff package in jessie-proposed-updates is considered
> uninstallable by at least aptitude when zenmap is installed.
>
> This probably happens because ndiff in jessie-proposed-updates declares
> Breaks and Replaces on zenmap (<< 6.47-5~), instead of 6.47-3+deb8u1.

Oh man, that was a stupid oversight on my part, it should be fixed in
version 6.47-3+deb8u2. Thank you.

Cheers,
-Hilko

Bug#825556: abi-compliance-checker,dh-acc: copyright file missing

[Andreas Beckmann]

Package: abi-compliance-checker,dh-acc
Version: 1.99.20-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

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

1m8.4s ERROR: WARN: Inadequate results from running adequate!
  abi-compliance-checker: missing-copyright-file 
/usr/share/doc/abi-compliance-checker/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/abi-compliance-checker/copyright
  # ls -lad /usr/share/doc/abi-compliance-checker
  drwxr-xr-x 2 root root 100 May 23 17:33 /usr/share/doc/abi-compliance-checker
  # ls -la /usr/share/doc/abi-compliance-checker/
  total 20
  drwxr-xr-x   2 root root   100 May 23 17:33 .
  drwxr-xr-x 120 root root  2880 May 23 17:33 ..
  -rw-r--r--   1 root root  2468 May 23 07:56 changelog.Debian.gz
  -rw-r--r--   1 root root42 May 23 11:17 changelog.gz
  -rw-r--r--   1 root root 10398 May 23 11:17 changelog.html.gz

Same problem in dh-acc


cheers,

Andreas


abi-compliance-checker_1.99.20-2.log.gz
Description: application/gzip

Bug#804310: [Pkg-kde-extras] Bug#804310: oxygen-transparent: Build-Depends on kde-workspace-dev which is gone

[Maximiliano Curia]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: oxygen-transparent/experimental -- ROM; Obsoleted by 
plasma 5

¡Hola Andreas!

El 2016-05-27 a las 19:07 +0200, Andreas Beckmann escribió:

On Sat, 07 Nov 2015 09:35:34 +0100 Andreas Beckmann  wrote:
oxygen-transparent cannot be build in experimental any longer since 
kde-workspace-dev is gone.


That package had only a single upload 2.5 years ago - maybe it should be 
removed?


Agreed.

Happy hacking,
--
"Whenever possible, steal code." -- Tom Duff
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Processed: Re: [Pkg-kde-extras] Bug#804310: oxygen-transparent: Build-Depends on kde-workspace-dev which is gone

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #804310 [oxygen-transparent] oxygen-transparent: Build-Depends on 
kde-workspace-dev which is gone
Bug reassigned from package 'oxygen-transparent' to 'ftp.debian.org'.
No longer marked as found in versions oxygen-transparent/0~20130220-1.
Ignoring request to alter fixed versions of bug #804310 to the same values 
previously set
> retitle -1 RM: oxygen-transparent/experimental -- ROM; Obsoleted by plasma 5
Bug #804310 [ftp.debian.org] oxygen-transparent: Build-Depends on 
kde-workspace-dev which is gone
Changed Bug title to 'RM: oxygen-transparent/experimental -- ROM; Obsoleted by 
plasma 5' from 'oxygen-transparent: Build-Depends on kde-workspace-dev which is 
gone'.

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

Bug#825495: gnunet: FTBFS: mv: cannot stat 't-vi.gmo': No such file or directory

[Bertrand Marc]

Hi,

Thanks for the report. It is not that clear from the log, but the build
failure is caused by an error of msgfmt, which comes from the
libunistring lack of transition (#825471 and friends).

This should be fixed in a few hours when libunistring is reverted to 0.9.3.

Best regards,
Bertrand

Bug#804310: oxygen-transparent: Build-Depends on kde-workspace-dev which is gone

[Andreas Beckmann]

On Sat, 07 Nov 2015 09:35:34 +0100 Andreas Beckmann  wrote:
> oxygen-transparent cannot be build in experimental any longer since
> kde-workspace-dev is gone.

That package had only a single upload 2.5 years ago - maybe it should be
removed?


Andreas

Bug#825546: noise: unsatisfiable Build-Depends

[Andreas Beckmann]

Source: noise
Version: 0.3.0-1~experimental1
Severity: serious

noise has Build-Depends that no longer exist in the archive:
   libsqlheavy0.1-dev | libsqlheavy-dev
   libzeitgeist-dev

Given that noise hasn't seen any maintenance since its initial upoload
to experimental, perhaps the package should be removed from the archive?


Andreas

Bug#821659: marked as done (slbackup-php: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 16:52:11 +
with message-id 
and subject line Bug#821659: fixed in slbackup-php 0.4.5-3
has caused the Debian Bug report #821659,
regarding slbackup-php: PHP 7.0 Transition
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.)


-- 
821659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slbackup-php
Version: 0.4.5-2
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The slbackup-php package currently depends on libapache2-mod-php5 php5
php5-cgi php5-cli .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: slbackup-php -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUrhXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHLm0QAKJTOLVQYL1BsaA74GEstFJg
YZb/pSSxBNVtRB4uiQNOxeSucWj47oXF6n/smK/JZxV2xUwDjGJm/s9lhMBtkxOm
O3SteyWhL8ybYcfOb108h/NEq69WgxF7k+aK8iEP+mjxANjWQCaeGlOVof+M/rhe
fgfLTcUowVe5LEnqw0UwtyE8xVP/JHJgu4vZDwu9Xxm3JXirXPTTz5zwncvUDRrK

Bug#820026: marked as done (icedove crashes (segfaults) when installed along with xul-ext-foxyproxy-standard)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 16:33:09 +
with message-id 
and subject line Bug#820026: fixed in icedove 1:45.1.0-1
has caused the Debian Bug report #820026,
regarding icedove crashes (segfaults) when installed along with 
xul-ext-foxyproxy-standard
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.)


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

Hi,

I've been fighting to understand why icedove was crashing on me (either
segfaults or with bus error) for both versions 38 and 44, after finally
discovering that Firefox extension foxyproxy 4.5.6 was causing the
crashes

see bug #815000

if the problem cannot be solved (from what I understand after a quick
look at the upstream bug report), that needs to be dealt in the icedove
package to prevent others from having both packages installed alongside

foxyproxy 4.5.6 is already in testing since 31 March, and I fear that
many Debian users who have both programs don't understand at first
glance that the instability comes from this bad interaction

please, add a tag to put xul-ext-foxyproxy-standard in conflict with
icedove (at least with this specific version if you think that it will
be solved in an upcoming release)


Thanks for your understanding


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (101, 'stable'), (99, 'experimental'), (9, 
'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: icedove
Source-Version: 1:45.1.0-1

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

Debian distribution maintenance software
pp.
Christoph Goehre  (supplier of updated icedove package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 May 2016 12:13:26 -0400
Source: icedove
Binary: icedove icedove-dev icedove-dbg iceowl-extension 
calendar-google-provider icedove-l10n-all icedove-l10n-ar icedove-l10n-ast 
icedove-l10n-be icedove-l10n-bg icedove-l10n-bn-bd icedove-l10n-br 
icedove-l10n-ca icedove-l10n-cs icedove-l10n-da icedove-l10n-de icedove-l10n-el 
icedove-l10n-en-gb icedove-l10n-es-ar icedove-l10n-es-es icedove-l10n-et 
icedove-l10n-eu icedove-l10n-fi icedove-l10n-fr icedove-l10n-fy-nl 
icedove-l10n-ga-ie icedove-l10n-gd icedove-l10n-gl icedove-l10n-he 
icedove-l10n-hr icedove-l10n-hu icedove-l10n-hy-am icedove-l10n-id 
icedove-l10n-is icedove-l10n-it icedove-l10n-ja icedove-l10n-ko icedove-l10n-lt 
icedove-l10n-nb-no icedove-l10n-nl icedove-l10n-nn-no icedove-l10n-pa-in 
icedove-l10n-pl icedove-l10n-pt-br icedove-l10n-pt-pt icedove-l10n-rm 
icedove-l10n-ro icedove-l10n-ru icedove-l10n-si icedove-l10n-sk icedove-l10n-sl 
icedove-l10n-sq icedove-l10n-sr icedove-l10n-sv-se icedove-l10n-ta-lk 
icedove-l10n-tr icedove-l10n-uk icedove-l10n-vi
 icedove-l10n-zh-cn icedove-l10n-zh-tw iceowl-l10n-ar iceowl-l10n-be 
iceowl-l10n-bg iceowl-l10n-bn-bd iceowl-l10n-br iceowl-l10n-ca iceowl-l10n-cs 
iceowl-l10n-cy iceowl-l10n-da iceowl-l10n-de iceowl-l10n-el iceowl-l10n-es-ar 
iceowl-l10n-es-es iceowl-l10n-en-gb iceowl-l10n-et iceowl-l10n-eu 
iceowl-l10n-fi iceowl-l10n-fr iceowl-l10n-fy-nl iceowl-l10n-ga-ie 
iceowl-l10n-gd iceowl-l10n-gl iceowl-l10n-he iceowl-l10n-hr iceowl-l10n-hu 
iceowl-l10n-hy-am iceowl-l10n-id iceowl-l10n-is iceowl-l10n-it iceowl-l10n-ko 
iceowl-l10n-ja iceowl-l10n-lt iceowl-l10n-nb-no iceowl-l10n-nl 
iceowl-l10n-nn-no iceowl-l10n-pa-in iceowl-l10n-pl iceowl-l10n-pt-br 
iceowl-l10n-pt-pt iceowl-l10n-rm iceowl-l10n-ro iceowl-l10n-ru iceowl-l10n-si 
iceowl-l10n-sk iceowl-l10n-sl iceowl-l10n-sr iceowl-l10n-sq iceowl-l10n-sv-se 
iceowl-l10n-ta-lk iceowl-l10n-tr iceowl-l10n-uk 

Bug#675112: marked as done (directfb: FTBFS in experimental: C compiler cannot create executables)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 16:20:09 +
with message-id 
and subject line Bug#675112: fixed in directfb 1.4.3-1.1
has caused the Debian Bug report #675112,
regarding directfb: FTBFS in experimental: C compiler cannot create executables
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.)


-- 
675112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: directfb
Version: 1.4.3-1
Severity: serious
Justification: FTBFS
Tags: experimental
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.7

Hello,

The experimental version of directfb currently FTBFS in experimental,
most probably due to the switch to gcc-4.7:

configure: error: in `/tmp/buildd/directfb-1.4.3/directfb-build':
configure: error: C compiler cannot create executables
See `config.log' for more details

configure:3979: gcc -Wall -g  -wl,--as-needed conftest.c  >&5
gcc-4.7.real: error: unrecognized command line option '-wl,--as-needed'

Samuel

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

Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Samuel Thibault 
 >   ±z¬O§_¸g±`¬°¦p¦ó©Ý®i¦æ¾PºÞ¹D¶Ë¸£µ¬?
 > ¥Zµn³ø¯È,Âø»x¼s§i©Î¶l±H¢Ò¢Û (Direct Mail)¬O§_¤w¸gµLªk¹F¦¨±z¹w´Áªº¼s§i®ÄªG?
 Je vous invite a consulter dans un premier temps le french-Howto.
 -+- JCD in Guide du linuxien pervers - "Bien configurer la lisibilité de fcolm"


--- End Message ---
--- Begin Message ---
Source: directfb
Source-Version: 1.4.3-1.1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated directfb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 May 2016 12:27:27 +0200
Source: directfb
Binary: libdirectfb-1.4-0 libdirectfb-1.4-0-udeb libdirectfb-bin 
libdirectfb-bin-udeb libdirectfb-extra libdirectfb-dev libdirectfb-1.4-0-dbg 
libdirectfb-bin-dbg libdirectfb-extra-dbg
Architecture: source
Version: 1.4.3-1.1
Distribution: experimental
Urgency: medium
Maintainer: Debian DirectFB Team 
Changed-By: Andreas Beckmann 
Description:
 libdirectfb-1.4-0 - direct frame buffer graphics - shared libraries
 libdirectfb-1.4-0-dbg - direct frame buffer graphics - shared libraries debug 
symbols
 libdirectfb-1.4-0-udeb - direct frame buffer graphics - shared libraries (udeb)
 libdirectfb-bin - direct frame buffer graphics - binaries
 libdirectfb-bin-dbg - direct frame buffer graphics - binaries debug symbols
 libdirectfb-bin-udeb - direct frame buffer graphics - binaries (udeb)
 libdirectfb-dev - direct frame buffer graphics library - development files
 libdirectfb-extra - direct frame buffer graphics - extra providers
 libdirectfb-extra-dbg - direct frame buffer graphics - extra provider debug 
symbols
Closes: 675112
Changes:
 directfb (1.4.3-1.1) experimental; urgency=medium
 .
   * Non-maintainer upload.
   * Merge from 1.2.10.0-5.1:
 - d/control: drop build depend on libts-dev.
 - d/libdirectfb-1.4-0.install.*: drop install libdirectfb_tslib.so
 - d/libdirectfb-dev.install.*: drop install libdirectfb_tslib.a
   * Merge from 1.2.10.0-5:
 - add support for libpng 1.5.
 - replace libpng12-dev build dependency by libpng-dev.
   * Merge from 1.2.10.0-4.3:
 - Fix "directfb ftbfs on armel. Implicit declaration error"
   * Merge from 1.2.10.0-4.1:
 - Fix typo for LDFLAGS.  (Closes: #675112)
Checksums-Sha1:
 fa916e6fc8dc10168f8df0ee9ad7da1e6411bfe0 2754 directfb_1.4.3-1.1.dsc
 22777c5309cb88a59dc3be8a1747e9d3189ca969 21048 directfb_1.4.3-1.1.debian.tar.xz
Checksums-Sha256:
 ef539a33fb4217230e31028044c88cb984d1e9f9682b1fac7a5095fbe285cdfa 2754 

Bug#708726: marked as done (FTBFS as typo of LDFLAGS)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 16:20:09 +
with message-id 
and subject line Bug#675112: fixed in directfb 1.4.3-1.1
has caused the Debian Bug report #675112,
regarding FTBFS as typo of LDFLAGS
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.)


-- 
675112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: directfb

In debian/rules, the LDFLAGS is defined as

-wl,--as-need

while the -w should be upper case,

-Wl,--as-need

--
YunQiang Su
--- End Message ---
--- Begin Message ---
Source: directfb
Source-Version: 1.4.3-1.1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated directfb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 May 2016 12:27:27 +0200
Source: directfb
Binary: libdirectfb-1.4-0 libdirectfb-1.4-0-udeb libdirectfb-bin 
libdirectfb-bin-udeb libdirectfb-extra libdirectfb-dev libdirectfb-1.4-0-dbg 
libdirectfb-bin-dbg libdirectfb-extra-dbg
Architecture: source
Version: 1.4.3-1.1
Distribution: experimental
Urgency: medium
Maintainer: Debian DirectFB Team 
Changed-By: Andreas Beckmann 
Description:
 libdirectfb-1.4-0 - direct frame buffer graphics - shared libraries
 libdirectfb-1.4-0-dbg - direct frame buffer graphics - shared libraries debug 
symbols
 libdirectfb-1.4-0-udeb - direct frame buffer graphics - shared libraries (udeb)
 libdirectfb-bin - direct frame buffer graphics - binaries
 libdirectfb-bin-dbg - direct frame buffer graphics - binaries debug symbols
 libdirectfb-bin-udeb - direct frame buffer graphics - binaries (udeb)
 libdirectfb-dev - direct frame buffer graphics library - development files
 libdirectfb-extra - direct frame buffer graphics - extra providers
 libdirectfb-extra-dbg - direct frame buffer graphics - extra provider debug 
symbols
Closes: 675112
Changes:
 directfb (1.4.3-1.1) experimental; urgency=medium
 .
   * Non-maintainer upload.
   * Merge from 1.2.10.0-5.1:
 - d/control: drop build depend on libts-dev.
 - d/libdirectfb-1.4-0.install.*: drop install libdirectfb_tslib.so
 - d/libdirectfb-dev.install.*: drop install libdirectfb_tslib.a
   * Merge from 1.2.10.0-5:
 - add support for libpng 1.5.
 - replace libpng12-dev build dependency by libpng-dev.
   * Merge from 1.2.10.0-4.3:
 - Fix "directfb ftbfs on armel. Implicit declaration error"
   * Merge from 1.2.10.0-4.1:
 - Fix typo for LDFLAGS.  (Closes: #675112)
Checksums-Sha1:
 fa916e6fc8dc10168f8df0ee9ad7da1e6411bfe0 2754 directfb_1.4.3-1.1.dsc
 22777c5309cb88a59dc3be8a1747e9d3189ca969 21048 directfb_1.4.3-1.1.debian.tar.xz
Checksums-Sha256:
 ef539a33fb4217230e31028044c88cb984d1e9f9682b1fac7a5095fbe285cdfa 2754 
directfb_1.4.3-1.1.dsc
 536cb349104df736362a9dc5710499b240ffa3b3c9752cac1c05d2bcd8e44d9b 21048 
directfb_1.4.3-1.1.debian.tar.xz
Files:
 bb04aabedf43a6c9d3df5ce1c6ff8c89 2754 libs optional directfb_1.4.3-1.1.dsc
 2c570c3731546ffddc8f0eb8f17ecd8f 21048 libs optional 
directfb_1.4.3-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXSFJ5AAoJEF+zP5NZ6e0I1MIP/RkzvjxUWKA57QOgtbcFkxZz
3K5Ehqi+G46l5H0MeQwePaeKPVqFAH0mOdy4mFSq5H3CJ5ImOy1eMf/dehkGiLfe
TupQvi//QkFFF1BBjaoNDgcogYib1wqE7CcQwPF26eSUInsM2+fj1iq7x86p+F7k
gdPRDCmr9iRPTlhHAO2sS66oQPlo4trdgCQlnDLHOP1oISuj+P86QvLhmGZb9eGt
TAA54pUi3dn+yo9qHRB+Rjfmx3smpcVfpTS0yaMycs8VeaBhliaUMmgu7khIrTAF
nCHyDIDwZo6gyUn8ENnTnDiR0olS1IiJMYAAy90e3rUp3kieU5iXLHJS15Zl1Hpc
IC46dt+hoZjguoa9jmCwV7Nfkv8G+YWdc9Ck4UkQ/0rDPghU5G9kR4Ke307gtRM/
fDHOyluBfHpZ9s5a72XQ2jq8DxlNg+Han1BEaY9yEnfWO3tdrR3zbJBAQiZYyKvX
1a6u8EOckCW8bggZ21udv7NXSyc9RJ1Q2eobbo796DFzqgMXyfZ2oedr38tgbPLK
BYy9uyMfE/LOBY1jxrUPgis9SbazK+ELJo/RZgaAXnfLTephsu1C2hmigvTbN4Z7
Ln15tS6Vsjb2hi5yGshpq5EYdspnO8ruxtg4GcIj8FKDZW/LyfABU1ZvzbXyA5vX
nZT4k5BTnUsbsNNaJFyW
=B8FB
-END PGP SIGNATURE End 

Bug#825542: php-arc: FTBFS: Tests: 40, Assertions: 87, Errors: 5.

[Chris Lamb]

Source: php-arc
Version: 2.2.5-2
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,

php-arc fails to build from source in unstable/amd64:

  [..]

  Get:34 http://httpredir.debian.org/debian sid/main amd64 
php-phpdocumentor-reflection-docblock all 2.0.4-2 [17.8 kB]
  Get:35 http://httpredir.debian.org/debian sid/main amd64 phpunit-diff all 
1.4.1-2 [8252 B]
  Get:36 http://httpredir.debian.org/debian sid/main amd64 phpunit-comparator 
all 1.2.0-2 [8614 B]
  Get:37 http://httpredir.debian.org/debian sid/main amd64 php-phpspec-prophecy 
all 1.6.0-2 [36.1 kB]
  Get:38 http://httpredir.debian.org/debian sid/main amd64 phpunit-global-state 
all 1.1.1-2 [6108 B]
  Get:39 http://httpredir.debian.org/debian sid/main amd64 
phpunit-object-enumerator all 1.0.0-2 [3794 B]
  Get:40 http://httpredir.debian.org/debian sid/main amd64 
phpunit-resource-operations all 1.0.0-2 [6302 B]
  Get:41 http://httpredir.debian.org/debian sid/main amd64 php-deepcopy all 
1.5.1-1 [43.2 kB]
  Get:42 http://httpredir.debian.org/debian sid/main amd64 phpunit all 
5.3.4+dfsg-2 [107 kB]
  Fetched 3930 kB in 0s (75.6 MB/s)
  Selecting previously unselected package libedit2:amd64.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23096 files and directories currently installed.)
  Preparing to unpack .../libedit2_3.1-20150325-1+b1_amd64.deb ...
  Unpacking libedit2:amd64 (3.1-20150325-1+b1) ...
  Selecting previously unselected package psmisc.
  Preparing to unpack .../psmisc_22.21-2.1+b1_amd64.deb ...
  Unpacking psmisc (22.21-2.1+b1) ...
  Selecting previously unselected package php-common.
  Preparing to unpack .../php-common_1%3a41_all.deb ...
  Unpacking php-common (1:41) ...
  Selecting previously unselected package ucf.
  Preparing to unpack .../archives/ucf_3.0036_all.deb ...
  Moving old data out of the way
  Unpacking ucf (3.0036) ...
  Selecting previously unselected package php7.0-common.
  Preparing to unpack .../php7.0-common_7.0.7-1_amd64.deb ...
  Unpacking php7.0-common (7.0.7-1) ...
  Selecting previously unselected package php7.0-json.
  Preparing to unpack .../php7.0-json_7.0.7-1_amd64.deb ...
  Unpacking php7.0-json (7.0.7-1) ...
  Selecting previously unselected package php7.0-opcache.
  Preparing to unpack .../php7.0-opcache_7.0.7-1_amd64.deb ...
  Unpacking php7.0-opcache (7.0.7-1) ...
  Selecting previously unselected package php7.0-readline.
  Preparing to unpack .../php7.0-readline_7.0.7-1_amd64.deb ...
  Unpacking php7.0-readline (7.0.7-1) ...
  Selecting previously unselected package php7.0-cli.
  Preparing to unpack .../php7.0-cli_7.0.7-1_amd64.deb ...
  Unpacking php7.0-cli (7.0.7-1) ...
  Selecting previously unselected package php-cli.
  Preparing to unpack .../php-cli_1%3a7.0+41_all.deb ...
  Unpacking php-cli (1:7.0+41) ...
  Selecting previously unselected package libxslt1.1:amd64.
  Preparing to unpack .../libxslt1.1_1.1.28-4_amd64.deb ...
  Unpacking libxslt1.1:amd64 (1.1.28-4) ...
  Selecting previously unselected package php7.0-xml.
  Preparing to unpack .../php7.0-xml_7.0.7-1_amd64.deb ...
  Unpacking php7.0-xml (7.0.7-1) ...
  Selecting previously unselected package php-xml.
  Preparing to unpack .../php-xml_1%3a7.0+41_all.deb ...
  Unpacking php-xml (1:7.0+41) ...
  Selecting previously unselected package php-pear.
  Preparing to unpack .../php-pear_1%3a1.10.1+submodules+notgz-8_all.deb ...
  Unpacking php-pear (1:1.10.1+submodules+notgz-8) ...
  Selecting previously unselected package pkg-php-tools.
  Preparing to unpack .../pkg-php-tools_1.34_all.deb ...
  Unpacking pkg-php-tools (1.34) ...
  Selecting previously unselected package php-symfony-yaml.
  Preparing to unpack .../php-symfony-yaml_2.8.6+dfsg-1_all.deb ...
  Unpacking php-symfony-yaml (2.8.6+dfsg-1) ...
  Selecting previously unselected package phpunit-recursion-context.
  Preparing to unpack .../phpunit-recursion-context_1.0.2-2_all.deb ...
  Unpacking phpunit-recursion-context (1.0.2-2) ...
  Selecting previously unselected package phpunit-exporter.
  Preparing to unpack .../phpunit-exporter_1.2.1-2_all.deb ...
  Unpacking phpunit-exporter (1.2.1-2) ...
  Selecting previously unselected package php-file-iterator.
  Preparing to unpack .../php-file-iterator_1.4.1-2_all.deb ...
  Unpacking php-file-iterator (1.4.1-2) ...
  Selecting previously unselected package 

Bug#825543: sugar-browse-activity: FTBFS: mv: cannot stat 'debian/sugar-browse-activity/usr/share/locale/aym': No such file or directory

[Chris Lamb]

Source: sugar-browse-activity
Version: 157.2-2
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,

sugar-browse-activity fails to build from source in unstable/amd64:

  [..]

  Wide character (U+3B1) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B1) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3C0) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3C0) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3C0) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3C0) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3C0) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3CC) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3CC) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3CC) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3CC) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3CC) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+393) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+393) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+393) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+393) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+393) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3AF) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3AF) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3AF) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3AF) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3AF) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3BD) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3BD) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3BD) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3BD) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3BD) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B5) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B5) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B5) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B5) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B5) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3C4) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3C4) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3C4) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3C4) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3C4) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B1) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B1) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B1) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B1) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B1) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B9) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B9) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B9) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B9) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3B9) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3BB) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character (U+3BB) in pattern match (m//) at /usr/bin/licensecheck line 
531,  line 322.
  Wide character 

Bug#825541: libmojolicious-plugin-mailexception-perl: FTBFS: t/010-tplugun.t failure

[Niko Tyni]

Package: libmojolicious-plugin-mailexception-perl
Version: 0.19-1
Severity: serious

This package fails to build on current sid/amd64.

  PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
"-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" 
t/*.t
  [Fri May 27 16:05:14 2016] [debug] GET "/"
  [Fri May 27 16:05:14 2016] [debug] Routing to controller "MpemTest::Ctl" and 
action "hello"
  [Fri May 27 16:05:14 2016] [debug] 200 OK (0.000865s, 1156.069/s)
  [Fri May 27 16:05:14 2016] [debug] GET "/crash"
  [Fri May 27 16:05:14 2016] [debug] Routing to controller "MpemTest::Ctl" and 
action "crash"
  [Fri May 27 16:05:14 2016] [error] die marker1 outside eval at 
t/010-tplugun.t line 110.
   at t/010-tplugun.t line 110
  [Fri May 27 16:05:14 2016] [debug] Template "exception.development.html.ep" 
not found
  [Fri May 27 16:05:14 2016] [debug] Rendering template "exception.html.ep" 
from DATA section
  Use of uninitialized value in concatenation (.) or string at template 
exception.html.ep from DATA section line 2,  line 167.
  [Fri May 27 16:05:14 2016] [debug] 500 Internal Server Error (0.006281s, 
159.210/s)
  
  #   Failed test 'content is similar'
  #   at t/010-tplugun.t line 43.
  #   'Exception: die marker1 outside eval at t/010-tplugun.t 
line 110.
  #  at t/010-tplugun.t line 110
  # Exception Line: 
  # '
  # doesn't match '(?^:Exception Line: die "die marker1 outside eval"; 
### die marker1\n$)'
  
  #   Failed test 'line'
  #   at t/010-tplugun.t line 55.
  #   undef
  # doesn't match '(?^:^die "die marker1 outside eval"; ### die 
marker1$)'
  [Fri May 27 16:05:14 2016] [debug] GET "/crash_sig"
  [Fri May 27 16:05:14 2016] [debug] Routing to controller "MpemTest::Ctl" and 
action "crash_sig"
  [Fri May 27 16:05:14 2016] [error] die marker2 sig at t/010-tplugun.t line 
118,  line 167.
  
  [Fri May 27 16:05:14 2016] [debug] Template "exception.development.html.ep" 
not found
  [Fri May 27 16:05:14 2016] [debug] Rendering cached template 
"exception.html.ep" from DATA section
  Use of uninitialized value in concatenation (.) or string at template 
exception.html.ep from DATA section line 2.
  [Fri May 27 16:05:14 2016] [debug] 500 Internal Server Error (0.002414s, 
414.250/s)
  
  #   Failed test 'content is similar'
  #   at t/010-tplugun.t line 76.
  #   'Exception: die marker2 sig at t/010-tplugun.t line 118, 
 line 167.
  # 
  # Exception Line: 
  # '
  # doesn't match '(?^:Exception Line: die "die marker2 sig"; ### die 
marker2\n$)'
  [Fri May 27 16:05:14 2016] [debug] GET "/crash_sub"
  [Fri May 27 16:05:14 2016] [debug] Routing to controller "MpemTest::Ctl" and 
action "crash_sub"
  [Fri May 27 16:05:14 2016] [error] mail exception marker3 at t/010-tplugun.t 
line 122
  [Fri May 27 16:05:14 2016] [debug] Template "exception.development.html.ep" 
not found
  [Fri May 27 16:05:14 2016] [debug] Rendering cached template 
"exception.html.ep" from DATA section
  Use of uninitialized value in concatenation (.) or string at template 
exception.html.ep from DATA section line 2.
  [Fri May 27 16:05:14 2016] [debug] 500 Internal Server Error (0.00265s, 
377.358/s)
  # Looks like you failed 3 tests of 29.
  t/010-tplugun.t .. 
  1..29
  ok 1 - use Test::Mojo;
  ok 2 - require Mojolicious;
  ok 3 - require MIME::Lite;
  ok 4 - require MIME::Words;
  ok 5 - require Mojolicious::Plugin::MailException;
  ok 6 - GET /
  ok 7 - 200 OK
  ok 8 - exact match for content
  ok 9 - GET /crash
  ok 10 - 500 Internal Server Error
  ok 11 - content is similar
  not ok 12 - content is similar
  ok 13 - one caugth exception
  ok 14 - text of message
  not ok 15 - line
  ok 16 - one prepared mail
  ok 17 - An object of class 'MIME::Lite' isa 'MIME::Lite'
  ok 18 - Stack
  ok 19 - Content-Disposition
  ok 20 - GET /crash_sig
  ok 21 - 500 Internal Server Error
  ok 22 - content is similar
  not ok 23 - content is similar
  ok 24 - one prepared mail
  ok 25 - GET /crash_sub
  ok 26 - 500 Internal Server Error
  ok 27 - content is similar
  ok 28 - one prepared mail
  ok 29 - Additional header
  Dubious, test returned 3 (wstat 768, 0x300)
  Failed 3/29 subtests 
  
  Test Summary Report
  ---
  t/010-tplugun.t (Wstat: 768 Tests: 29 Failed: 3)
Failed tests:  12, 15, 23
Non-zero exit status: 3
  Files=1, Tests=29,  1 wallclock secs ( 0.03 usr  0.01 sys +  0.44 cusr  0.02 
csys =  0.50 CPU)
  Result: FAIL

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

Bug#825291: otrs2: fails to upgrade from 'jessie': DBUpdate-to-5.pl: DBD::Pg::db do failed: ERROR: invalid byte sequence for encoding "UTF8"

[Andreas Beckmann]

On 2016-05-27 15:12, Patrick Matthäi wrote:
> could you also test if it fails on your system if you update to 5.0.8
> instead of 5.0.10?

You are lucky, I some old jessie2stretch logfiles:
  archive/pass/otrs_4.0.8-1.log.xz
  archive/fail/otrs2_5.0.8+dfsg1-1.log.xz
The first one succeeded and second one failed the upgrade in the same way.
All other old logfiles were not helpful, mostly database connection
failures (but these can be caused by the piuparts environment,
i.e. postgresql running on the wrong port).

rerunning the tests with old packages is not trivial and would mean more manual 
work

[...]
  applying upgrade sql for 3.3.9-3 -> 5.0.0.
  applying upgrade script for 3.3.9-3 -> 5.0.1.
  
  Migration started...
  
  Step 1 of 17: Refresh configuration cache...[Thu Apr  7 14:12:20 2016] 
DBUpdate-to-5.pl: Subroutine Load redefined at (eval 16) line 2.
  
  If you see warnings about 'Subroutine Load redefined', that's fine, no need 
to worry!
  done.
  
  Step 2 of 17: Check framework version...[Thu Apr  7 14:12:21 2016] 
DBUpdate-to-5.pl: Subroutine Load redefined at (eval 1727) line 2.
  done.
  
  Step 3 of 17: Migrate Database Column Types...done.
  
  Step 4 of 17: Migrate charset to UTF-8 on auto_response table...done.
  
  Step 5 of 17: Migrate charset to UTF-8 on notification_event table...done.
  
  Step 6 of 17: Migrate event based notifications to support multiple 
languages...done.
  
  Step 7 of 17: Migrate notifications to event based notifications...[Thu Apr  
7 14:12:21 2016] DBUpdate-to-5.pl: DBD::Pg::db do failed: ERROR:  invalid byte 
sequence for encoding "UTF8": 0xeb 0x73 0x63 at /usr/sha
re/otrs/Kernel/System/DB.pm line 449.
  ERROR: OTRS-DBUpdate-to-5.pl-10 Perl: 5.22.1 OS: linux Time: Thu Apr  7 
14:12:21 2016
  
   Message: ERROR:  invalid byte sequence for encoding "UTF8": 0xeb 0x73 0x63, 
SQL: '
  INSERT INTO notification_event_message
  (notification_id, subject, text, content_type, language)
  VALUES (?, ?, ?, ?, ?)'
  
   Traceback (10036): 
 Module: Kernel::System::NotificationEvent::NotificationAdd Line: 375
 Module: main::_MigrateNotifications Line: 1115
 Module: ./scripts/DBUpdate-to-5.pl Line: 162
  
  error.
  
  [Thu Apr  7 14:12:21 2016] DBUpdate-to-5.pl: Died at 
./scripts/DBUpdate-to-5.pl line 167.
  error encountered processing 
/usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/5.0.1:
  /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/5.0.1 exited with 
non-zero status
  dbconfig-common: otrs2 configure: aborted.
  dbconfig-common: flushing administrative password
  dpkg: error processing package otrs2 (--configure):
   subprocess installed post-installation script returned error exit status 1

Andreas

Bug#821659: marked as pending

[Ondřej Surý]

Hi Mike,

lgtm, go ahead and upload.

Cheers, Ondřej


On 27 May 2016 4:24:18 PM Mike Gabriel  
wrote:



tag 821659 pending
thanks

Hello,

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


http://git.debian.org/?p=debian-edu/pkg-team/slbackup-php.git;a=commitdiff;h=4caa619

---
commit 4caa619ac74823b69e5b3caa73eb70c5e4c6373b
Author: Mike Gabriel 
Date:   Fri May 27 16:20:38 2016 +0200

upload to unstable (debian/0.4.5-3)

diff --git a/debian/changelog b/debian/changelog
index f0dcf61..7aad637 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,18 @@
+slbackup-php (0.4.5-3) unstable; urgency=medium
+
+  * debian/control:
++ Drop explicit PHP5 dependencies, make package fit for PHP7.
+  (Closes: #821659).
++ Bump Standards: to 3.9.8. No changes needed.
+  * debian/patches:
++ Add 1002_php7-compat.patch. Use preg_split() instead of split()
+  Thanks to Wolfgang Schweer for providing that patch (via #821659).
+  * debian/po:
++ Add pt_BR.po translation file. Thanks to Adriano Rafael Gomes for
+  working on the internationalization of slbackup-php. (Closes: #816957).
+
+ -- Mike Gabriel   Fri, 27 May 2016 16:12:38 +0200
+
 slbackup-php (0.4.5-2) unstable; urgency=medium

   * debian/po:

Bug#820344: [PKG-Openstack-devel] Bug#820344: python-oslo.privsep: FTBFS: _StringException: Empty attachments:

[Chris Lamb]

> Could I then suppose that this is a specific issue with your Docker
> setup?

Hm, I don't think so - I'm doing nothing out of the ordinary to be quite honest 
or really "using" Docker, ie. nothing that wouldn't come up with someone else 
building in namespaces, cgroups, etc. :)


Regards,

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

Bug#821659: marked as pending

[Mike Gabriel]

tag 821659 pending
thanks

Hello,

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


http://git.debian.org/?p=debian-edu/pkg-team/slbackup-php.git;a=commitdiff;h=4caa619

---
commit 4caa619ac74823b69e5b3caa73eb70c5e4c6373b
Author: Mike Gabriel 
Date:   Fri May 27 16:20:38 2016 +0200

upload to unstable (debian/0.4.5-3)

diff --git a/debian/changelog b/debian/changelog
index f0dcf61..7aad637 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,18 @@
+slbackup-php (0.4.5-3) unstable; urgency=medium
+
+  * debian/control:
++ Drop explicit PHP5 dependencies, make package fit for PHP7.
+  (Closes: #821659).
++ Bump Standards: to 3.9.8. No changes needed.
+  * debian/patches:
++ Add 1002_php7-compat.patch. Use preg_split() instead of split()
+  Thanks to Wolfgang Schweer for providing that patch (via #821659).
+  * debian/po:
++ Add pt_BR.po translation file. Thanks to Adriano Rafael Gomes for
+  working on the internationalization of slbackup-php. (Closes: #816957).
+
+ -- Mike Gabriel   Fri, 27 May 2016 16:12:38 +0200
+
 slbackup-php (0.4.5-2) unstable; urgency=medium
 
   * debian/po:

Processed: Bug#821659 marked as pending

[Debian Bug Tracking System]

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

> tag 821659 pending
Bug #821659 [slbackup-php] slbackup-php: PHP 7.0 Transition
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#816528: marked as done (plasma-framework-dev: fails to upgrade from 'sid' - trying to overwrite /usr/share/kdevappwizard/templates/qml-plasmoid.tar.bz2)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 13:56:04 +
with message-id 
and subject line Bug#816528: fixed in plasma-framework 5.22.0-1
has caused the Debian Bug report #816528,
regarding plasma-framework-dev: fails to upgrade from 'sid' - trying to 
overwrite /usr/share/kdevappwizard/templates/qml-plasmoid.tar.bz2
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.)


-- 
816528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-framework-dev
Version: 5.19.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package plasma-framework-dev.
  Preparing to unpack .../plasma-framework-dev_5.19.0-1_amd64.deb ...
  Unpacking plasma-framework-dev (5.19.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/plasma-framework-dev_5.19.0-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/share/kdevappwizard/templates/qml-plasmoid.tar.bz2', which is also in 
package kapptemplate 4:15.12.1-1


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: plasma-framework
Source-Version: 5.22.0-1

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated plasma-framework 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 May 2016 15:28:35 +0200
Source: plasma-framework
Binary: plasma-framework-dev plasma-framework libkf5plasmaquick5 libkf5plasma5
Architecture: source
Version: 5.22.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 libkf5plasma5 - Plasma Runtime components
 libkf5plasmaquick5 - Plasma Runtime components
 plasma-framework - Plasma Runtime components
 plasma-framework-dev - development files for plasma-framework
Closes: 816528
Changes:
 plasma-framework (5.22.0-1) unstable; urgency=medium
 .
   [ Maximiliano Curia ]
   * Bump kapptemplate breaks/replaces, the conflicting file is going to be
 removed from kapptemplate in the next upload. (Closes: #816528) Thanks to
 Andreas Beckmann for the report.
   * Update install files
   * Update testsuite scripts
   * Update copyright information
   * Update acc test script
   * testsuite: Missing XDG_DATA_DIRS, use breeze by default
   * Add new patch: upstream_fix_iconitem_test.patch
   * testsuite: add hicolor icon theme as a dependency
   * uscan no longer supports more than one main upstream tarball being listed
 .
   [ Automatic packaging ]
   * Update build-deps and deps with the info from cmake
   * Bump Standards-Version to 3.9.8
   * Update symbols files (private class was wrongly exported)
   * Update symbols files
   * Refresh patches
Checksums-Sha1:
 4603a9d1fd9407496e4412bfb3ba701453772a3d 3474 plasma-framework_5.22.0-1.dsc
 6272e501eb6485ef223b093b257c06eaaf7a84d7 4018324 
plasma-framework_5.22.0.orig.tar.xz
 124a1eeeddbf1cee9463ea4950962930aab8f4d6 16544 
plasma-framework_5.22.0-1.debian.tar.xz
Checksums-Sha256:
 322d1fd9cb0b78b3b2a80dbfd33ba8996dd547c13072e0b39355cb5e7154f0de 3474 
plasma-framework_5.22.0-1.dsc
 ec1f9398221c9d6ef2e369b95ca925bb0d46fe5f88e6db8acc883730c08ac7f2 4018324 
plasma-framework_5.22.0.orig.tar.xz
 ac38760e1cab87e32ccc7298bf6750bda3ad826f00a8affb5ea9557b3b4f00b8 16544 
plasma-framework_5.22.0-1.debian.tar.xz
Files:
 9cde4fe6cc369d10de075d1847129fdc 3474 libs optional 
plasma-framework_5.22.0-1.dsc
 

Bug#823484: marked as done (hg-git: FTBFS: AttributeError: 'overlaychangelog' object has no attribute 'changelogrevision')

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 13:52:24 +
with message-id 
and subject line Bug#823484: fixed in hg-git 0.8.5-3
has caused the Debian Bug report #823484,
regarding hg-git: FTBFS: AttributeError: 'overlaychangelog' object has no 
attribute 'changelogrevision'
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.)


-- 
823484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hg-git
Version: 0.8.5-2
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,

hg-git fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'hg-git-build-deps' in 
'../hg-git-build-deps_0.8.5-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package hg-git-build-deps.
  (Reading database ... 23072 files and directories currently installed.)
  Preparing to unpack hg-git-build-deps_0.8.5-2_all.deb ...
  Unpacking hg-git-build-deps (0.8.5-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
libjs-excanvas mercurial mercurial-common python-dulwich ucf unzip
  Suggested packages:
qct kdiff3 | kdiff3-qt | kompare | meld | tkcvs | mgdiff wish python-mysqldb
python-pygments python-openssl python-dulwich-dbg zip
  Recommended packages:
javascript-common openssh-client ca-certificates python-fastimport
  The following NEW packages will be installed:
libjs-excanvas mercurial mercurial-common python-dulwich ucf unzip
  0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 2480 kB of archives.
  After this operation, 12.6 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 unzip amd64 6.0-20 
[161 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 ucf all 3.0036 [70.2 
kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libjs-excanvas all 
0.r3-4 [45.3 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 mercurial-common all 
3.8.1-1 [1901 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 mercurial amd64 
3.8.1-1 [74.7 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 python-dulwich amd64 
0.13.0-1 [228 kB]
  Fetched 2480 kB in 0s (71.6 MB/s)
  Selecting previously unselected package unzip.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23076 files and directories currently installed.)
  Preparing to unpack .../unzip_6.0-20_amd64.deb ...
  Unpacking unzip (6.0-20) ...
  Selecting previously unselected package ucf.
  Preparing to unpack .../archives/ucf_3.0036_all.deb ...
  Moving old data out of the way
  Unpacking ucf (3.0036) ...
  Selecting previously unselected package libjs-excanvas.
  Preparing to unpack .../libjs-excanvas_0.r3-4_all.deb ...
  Unpacking libjs-excanvas (0.r3-4) ...
  Selecting previously unselected package mercurial-common.
  Preparing to unpack .../mercurial-common_3.8.1-1_all.deb ...
  Unpacking mercurial-common (3.8.1-1) ...
  Selecting previously unselected package mercurial.
  Preparing to unpack .../mercurial_3.8.1-1_amd64.deb ...
  Unpacking mercurial (3.8.1-1) ...
  Selecting previously unselected package python-dulwich.
  Preparing to unpack .../python-dulwich_0.13.0-1_amd64.deb ...
  Unpacking python-dulwich (0.13.0-1) ...
  Processing triggers for mime-support (3.60) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up unzip (6.0-20) ...
  Setting up ucf 

Bug#825528: ndiff: jessie-proposed-updates: uninstallable together with zenmap

[Henrique de Moraes Holschuh]

Package: ndiff
Version: 6.47-3+deb8u1
Severity: grave
Justification: renders package unusable
Tags: jessie

The current ndiff package in jessie-proposed-updates is considered
uninstallable by at least aptitude when zenmap is installed.

This probably happens because ndiff in jessie-proposed-updates declares
Breaks and Replaces on zenmap (<< 6.47-5~), instead of 6.47-3+deb8u1.

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

Versions of packages ndiff recommends:
ii  nmap  6.47-3+b1

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Processed: Re: Bug#825527: nautilus: error while loading shared libraries: libunistring.so.0

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libunistring0
Bug #825527 [nautilus] nautilus: error while loading shared libraries: 
libunistring.so.0
Bug reassigned from package 'nautilus' to 'libunistring0'.
No longer marked as found in versions nautilus/3.20.1-2.
Ignoring request to alter fixed versions of bug #825527 to the same values 
previously set
> forcemerge 825471 -1
Bug #825471 {Done: Stephen Kitt } [libunistring0] 
libunistring0: soname change without package name change
Bug #825472 {Done: Stephen Kitt } [libunistring0] 
libunistring0: soname bump without name change
Bug #825473 {Done: Stephen Kitt } [libunistring0] 
libunistring0: Upstream had a SONAME filename change, but libunitstring0 
package name didn't change.
Bug #825474 {Done: Stephen Kitt } [libunistring0] 
libunistring0: upgrading to 0.9.6-1.1 leads to a problem with shared libraries
Bug #825527 [libunistring0] nautilus: error while loading shared libraries: 
libunistring.so.0
Severity set to 'critical' from 'important'
Marked Bug as done
Marked as fixed in versions libunistring/0.9.6+really0.9.3-0.1.
Marked as found in versions libunistring/0.9.6-1.1.
Bug #825472 {Done: Stephen Kitt } [libunistring0] 
libunistring0: soname bump without name change
Bug #825473 {Done: Stephen Kitt } [libunistring0] 
libunistring0: Upstream had a SONAME filename change, but libunitstring0 
package name didn't change.
Bug #825474 {Done: Stephen Kitt } [libunistring0] 
libunistring0: upgrading to 0.9.6-1.1 leads to a problem with shared libraries
Merged 825471 825472 825473 825474 825527

-- 
825471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825471
825472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825472
825473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825473
825474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825474
825527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#800195: marked as done (vpim: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 13:37:52 +
with message-id 
and subject line Bug#800195: fixed in vpim 0.695-1.4
has caused the Debian Bug report #800195,
regarding vpim: Please migrate a supported debhelper compat level
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.)


-- 
800195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vpim
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package vpim is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: vpim
Source-Version: 0.695-1.4

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

Debian distribution maintenance software
pp.
Herbert Parentes Fortes Neto  (supplier of updated vpim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 May 2016 10:45:07 -0300
Source: vpim
Binary: vpim
Architecture: source
Version: 0.695-1.4
Distribution: unstable
Urgency: medium
Maintainer: Joey Schulze 
Changed-By: Herbert Parentes Fortes Neto 
Description:
 vpim   - Ruby support for vCard and iCalendar
Closes: 800195
Changes:
 vpim (0.695-1.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * DH_LEVEL: 9. (Closes: #800195)
   * debian/control:
   - dh-exec added to Build-Depends.
   - Bump Standards-Version from 3.8.0 to 3.9.8
   - some fields were reorganized.
   - using ${misc:Depends}.
   * debian/docs created.
   * debian/install created.
   * debian/patches ( 3.0 - quilt):
   - split up vpim*.diff.gz archive. Two distinct patches:
   - event_size.patch
   - path_to_plist.patch
   * debian/post{inst,rm}
   - 'set -e' added.
   - '#DEBHELPER#' token added.
   - 'exit 0' added.
   * debian/rules:
   - new format. Authentict ruby package.
Checksums-Sha1:
 330187008ea0de1e18d6094a695d815c273af22f 1702 vpim_0.695-1.4.dsc
 28fb39c096f4ed373ceadba3a10c5d2cbd2650e8 4860 vpim_0.695-1.4.debian.tar.xz
Checksums-Sha256:
 11a7fc35820790b16a021b32dfa4c4a2d9a585497e616be36b82fa3bb6f34cf6 1702 
vpim_0.695-1.4.dsc
 5653224b8514ca8434f9a6f7752979a11d34c198ff3513b59ba268259486bd21 4860 
vpim_0.695-1.4.debian.tar.xz
Files:
 46301318453c6c17de26511cf4089f4f 1702 libs optional vpim_0.695-1.4.dsc
 458fc58f23be2b0588fbf821387261e3 4860 libs optional 
vpim_0.695-1.4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXSELiAAoJEPwNsbvNRgveq70P/1zzjrEZ2/5tXewnvSv7EZZi
ZdBEZX62CwsYFW4kbi3kHuivLqB7hxVUtfZ8cGFlp6HSNGmv79r6H8hZprTFi/D8
4wzu3xuFsCKOrkoeaTFRVzslpF5GdmFCSHtbncau6XvVKTrY4tYZmkVz+yFZXoqU
xNM5pnjyezLnr1Yo2KvtMu7k7l4tCK9AnPDenkf4WJ8ebFwmO7384hwIsqgBA++O

Bug#793465: marked as done (DoS and privilege escalation by local users (CVE-2015-3245 and CVE-2015-3246))

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 13:28:52 +
with message-id 
and subject line Bug#793465: fixed in libuser 1:0.62~dfsg-0.1
has caused the Debian Bug report #793465,
regarding DoS and privilege escalation by local users (CVE-2015-3245 and 
CVE-2015-3246)
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.)


-- 
793465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libuser
Version: 1:0.56.9.dfsg.1-1.2
Severity: grave
Tags: security upstream patch

During a code audit by Qualys, multiple libuser-related vulnerabilities 
were discovered that can allow local users to perform denial-of-service and
privilege-escalation attacks:

- Race condition in password file update (CVE-2015-3246, Important)

A flaw was found in the way the libuser library handled the /etc/passwd file.
Even though traditional programs like passwd, chfn, and chsh work on a
temporary copy of /etc/passwd and eventually use the rename() function to
rename the temporary copy, libuser modified /etc/passwd directly.
Unfortunately, if anything went wrong during these modifications,
libuser may have left/etc/passwd in an inconsistent state.

This behavior could result in a local denial-of-service attack; in addition,
when combined with a second vulnerability (CVE-2015-3245, described below),
it could result in the escalation of privileges to the root user.

- Lack of validation of GECOS field contents (CVE-2015-3245, Moderate)

It was found that the chfn function of the userhelper utility did not properly
filter out newline characters. The chfn function implemented by the userhelper
utility verified that the fields it was given on the command line were valid
(that is, contain no forbidden characters).
Unfortunately, these forbidden characters (:,=) did not include the \n character
and allowed local attackers to inject newline characters into the /etc/passwd
file and alter this file in unexpected ways.
A local attacker could use this flaw to corrupt the /etc/passwd file,
which could result in a denial-of-service attack on the system.



Both issues have been fixed upstream, and shipped in relase 0.62.
Please mention the CVE numbers in the changelog when fixing the issue.

References:
 * RedHat security bulletin
   https://access.redhat.com/articles/1537873
 * PoC
   http://www.openwall.com/lists/oss-security/2015/07/23/16
 * libuser 0.62 changelog
   https://fedorahosted.org/libuser/browser/NEWS?rev=libuser-0.62
 * Fixing commit
   
https://fedorahosted.org/libuser/changeset/d73aa2a5a9ce5bdd349dff46e3e4885f2b194a95/


Cheers, Luca
--- End Message ---
--- Begin Message ---
Source: libuser
Source-Version: 1:0.62~dfsg-0.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated libuser package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 May 2016 12:56:43 +
Source: libuser
Binary: libuser libuser1-dev libuser1 python-libuser
Architecture: source
Version: 1:0.62~dfsg-0.1
Distribution: unstable
Urgency: high
Maintainer: Ghe Rivero 
Changed-By: Mattia Rizzolo 
Description:
 libuser- user and group account administration library - utilities
 libuser1   - user and group account administration library - shared libraries
 libuser1-dev - user and group account administration library - development 
files
 python-libuser - user and group account administration library - Python 2.7 
bindin
Closes: 793465
Changes:
 libuser (1:0.62~dfsg-0.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Imported Upstream version 0.62~dfsg.
 + CVE-2015-3245 (Lack of validation of GECOS field contents) (low/local)
 + CVE-2015-3246 (Race condition in passwd file update) (high/local)
 + Closes: #793465
   * d/copyright:
 + convert to copyright-format 1.0.
 + add a Files-Excluded field to drop docs/rfc2307.txt from the 

Bug#823105: marked as done (usermode: Build-Depends on libuser which has been requested to be removed)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 13:31:20 +
with message-id <20160527133118.ga27...@chase.mapreri.org>
and subject line Re: Bug#823105: usermode: Build-Depends on libuser which has 
been requested to be removed
has caused the Debian Bug report #823105,
regarding usermode: Build-Depends on libuser which has been requested to be 
removed
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.)


-- 
823105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: usermode
Version: 1.109-1
Severity: serious
Tags: sid
Control: block 818238 with -1

Hi,

usermode build-depends on libuser1-dev, but src:libuser has been
requested to be removed. (#818238)
Should usermode be removed as well? Or can the dependency on libuser1 be
dropped/replaced by something else?


Andreas
--- End Message ---
--- Begin Message ---
On Sat, Apr 30, 2016 at 10:02:12PM +0200, Andreas Beckmann wrote:
> usermode build-depends on libuser1-dev, but src:libuser has been
> requested to be removed. (#818238)
> Should usermode be removed as well? Or can the dependency on libuser1 be
> dropped/replaced by something else?

I uploaded the new libuser upstream release, fixing the security issues
that warrented libuser's removal.
So, no action in usermode is needed anymore.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 823484 + pending
Bug #823484 [src:hg-git] hg-git: FTBFS: AttributeError: 'overlaychangelog' 
object has no attribute 'changelogrevision'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#825291: otrs2: fails to upgrade from 'jessie': DBUpdate-to-5.pl: DBD::Pg::db do failed: ERROR: invalid byte sequence for encoding "UTF8"

[Debian Bug Tracking System]

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

> tag #825291 + moreinfo
Bug #825291 [otrs2] otrs2: fails to upgrade from 'jessie': DBUpdate-to-5.pl: 
DBD::Pg::db do failed: ERROR: invalid byte sequence for encoding "UTF8"
Added tag(s) moreinfo.
> tag #825291 + upstream
Bug #825291 [otrs2] otrs2: fails to upgrade from 'jessie': DBUpdate-to-5.pl: 
DBD::Pg::db do failed: ERROR: invalid byte sequence for encoding "UTF8"
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#825291: otrs2: fails to upgrade from 'jessie': DBUpdate-to-5.pl: DBD::Pg::db do failed: ERROR: invalid byte sequence for encoding "UTF8"

[Patrick Matthäi]

tag #825291 + moreinfo
tag #825291 + upstream
thanks

Hi,

could you also test if it fails on your system if you update to 5.0.8
instead of 5.0.10?

I already reported this to upstream:

http://bugs.otrs.org/show_bug.cgi?id=12103


Am 25.05.2016 um 17:49 schrieb Andreas Beckmann:
> Package: otrs2
> Version: 5.0.10-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'stretch' fails.
>
> >From the attached log (scroll to the bottom...):
>
> [...]
>   Migration completed!
>   applying upgrade sql for 3.3.9-3 -> 5.0.0.
>   applying upgrade script for 3.3.9-3 -> 5.0.1.
>   
>   Migration started...
>   
>   Step 1 of 17: Refresh configuration cache...[Mon May 23 13:17:50 2016] 
> DBUpdate-to-5.pl: Subroutine Load redefined at (eval 16) line 2.
>   
>   If you see warnings about 'Subroutine Load redefined', that's fine, no need 
> to worry!
>   done.
>   
>   Step 2 of 17: Check framework version...[Mon May 23 13:17:51 2016] 
> DBUpdate-to-5.pl: Subroutine Load redefined at (eval 1736) line 2.
>   done.
>   
>   Step 3 of 17: Migrate Database Column Types...done.
>   
>   Step 4 of 17: Migrate charset to UTF-8 on auto_response table...done.
>   
>   Step 5 of 17: Migrate charset to UTF-8 on notification_event table...done.
>   
>   Step 6 of 17: Migrate event based notifications to support multiple 
> languages...done.
>   
>   Step 7 of 17: Migrate notifications to event based notifications...[Mon May 
> 23 13:17:51 2016] DBUpdate-to-5.pl: DBD::Pg::db do failed: ERROR:  invalid 
> byte sequence for encoding "UTF8": 0xeb 0x73 0x63 at 
> /usr/share/otrs/Kernel/System/DB.pm line 449.
>   ERROR: OTRS-DBUpdate-to-5.pl-10 Perl: 5.22.2 OS: linux Time: Mon May 23 
> 13:17:51 2016
>   
>Message: ERROR:  invalid byte sequence for encoding "UTF8": 0xeb 0x73 
> 0x63, SQL: '
>   INSERT INTO notification_event_message
>   (notification_id, subject, text, content_type, language)
>   VALUES (?, ?, ?, ?, ?)'
>   
>Traceback (13340): 
>  Module: Kernel::System::NotificationEvent::NotificationAdd Line: 375
>  Module: main::_MigrateNotifications Line: 1115
>  Module: ./scripts/DBUpdate-to-5.pl Line: 162
>   
>   error.
>   
>   [Mon May 23 13:17:51 2016] DBUpdate-to-5.pl: Died at 
> ./scripts/DBUpdate-to-5.pl line 167.
>   error encountered processing 
> /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/5.0.1:
>   /usr/share/dbconfig-common/scripts/otrs2/upgrade/pgsql/5.0.1 exited with 
> non-zero status
>   dbconfig-common: otrs2 configure: aborted.
>   dbconfig-common: flushing administrative password
>   dpkg: error processing package otrs2 (--configure):
>subprocess installed post-installation script returned error exit status 1
>
>
>
> cheers,
>
> Andreas

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Processed: Re: Bug#825515: lolcat: just hangs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed
Bug #825515 [lolcat] lolcat: just hangs
Added tag(s) confirmed.
> severity -1 serious
Bug #825515 [lolcat] lolcat: just hangs
Severity set to 'serious' from 'important'

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

Bug#824166: texlive-bin: FTBFS due to luajit issues

[Thorsten Glaser]

On Fri, 27 May 2016, Norbert Preining wrote:

> After disabling mips and mipsel builds of lua*, now texlive-bin
> is not entering testing anymore ...
> 
>   texlive-bin is not yet built on mips: 2015.20160222.37495-1 vs 
> 2016.20160513.41080-2 (missing 2 binaries: libtexluajit-dev, libtexluajit2) 
> 
> Did I miss an important step here? It seems that I need to get rid
> of these packages somehow?

Uh, sorry, no idea :( ask some release manager, I think?

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#825064: Bacula director does not start silently due to database mismatch

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Am Fr den 27. Mai 2016 um 13:08 schrieb Paul Gevers:
> I'd like to note that while I was investigating what to write below, I
> discovered three unrelated issues in two packages in how they react with
> dpkg-reconfigure (in dbconfig-common and cacti), so whatever the outcome
> of this bug is, it is going to improve the world. I will file those bugs
> shortly.

Nice. :-)

> > I didn't get the option at all to upgrade the database. I only always
> > got the quoted question ever.
> 
> I am not sure if you are now talking about the current upgrade. If you
> are than that is correct, you didn't get the question because you had
> dbc_install=false. If you are talking about "ever" than something
> clearly failed during the migration.

True, with upgrade I did not get any question.

I got this (and only this) question when using dpkg-reconfigure.

> As bacula migrated to
> dbconfig-common support for their MySQL and PostgreSQL databases way
> before that time (in 2006), I suspect you got the old (install) question
> and this would explain why you haven't seen the question in mentioned in
> my previous e-mail.

Well, I do not know how long, but I use bacula for really long time now.
I have file dates up to begin of 2009 but using bacula much longer.

As database, I always used sqlite. (And yes, I know that it might be
dangerous to use eatmydata as preload and that mysql or postgresql might
be a better solution. Without that preload, the backup postprocessing
(feeding data into the database) needs more than 1½ hours instead of
far under 1 minute now. And the danger to exactly break in that small
time is much lower than in 1½ hours.)

> >> The reason why dbc_install=false drops the full support of
> >> dbconfig-common is because that is the variable that is set during the
> >> initial installation (and the only one if one opts-out of support). So
> >> we need to check this before anything else. If you didn't want install
> >> support, it doesn't make sense to ask if you want upgrade support.
> > 
> > And that might be the problem.
> 
> Why?

Well, I want to use the upgrade but not the install of a new database.

> > At the initial installation that was
> > handled via dbconfig, I already had a populated database that I couldn't
> > risk to lose. For that reason I answered the already quoted question
> > with "no" in the first place.
> 
> As mentioned, if bacula switched before 2010, than the bug that you got
> the wrong question has long been fixed.

Well, I used dpkg-reconfigure to get that question I pasted.

> > There was never a question about update.
> 
> As explained, with dbc_install=false that is to be expected.

I mean, there as never a question about that even when dbc gots
installed in the begin.

> > I never edited that file before. I always used dpkg-reconfigure (or the
> > debconf question at the begin). And that was when the database already
> > existed.
> 
> Interestingly, (and we could consider this a bug in dbconfig-common) you
> can't get the dbc-install variable set to "true" via dpkg-reconfigure if
> you are answering "no, I don't want you to reinstall the database". So
> the only way to get dbconfig-common support after the first time is
> answered with "no" is to edit the file. But, as it stands, you told the
> package to NOT use dbconfig-common, and now you are expecting from the
> package that even without dbconfig-common help it should do the right
> thing?

Well, from the user perspective, I just vote for not overwriting my
existing database. I did not get any question about migrating the
database. (That was working bevore bacula switched to dbc.)

> I think that is unreasonable to expect (although I grant you that
> you may expect an option with dpkg-reconfigure to actually opt-in
> again). Just so you know why I think the current behavior (again, minus
> the reconfigure option) is correct, I am pointing you to the policy on
> asking questions, paragraph 3.9.1¹ which says: "should ensure that the
> user will only ever be asked each question once". Therefore, if you say
> no, that is what we will honor.

Thats fine. But as stated above, the quote came from a recent manual run
of dpkg-reconfigure.

> > However, I don't think that the name should be changed but it should do
> > what it is named for.
> 
> You just confessed that you never changed the file manually, so the name
> of the variable doesn't matter.

True.

> The question it stands for is, "do you want dbconfig-common to manage
> the database on behalf of ${pkg}". And as already noted, the question
> that is actually asked has been changed more than 6 years ago.

Well, it asked to purge my existing database.

> > However, beside that problem of the upgrade itself, I also complained
> > about that bacula-dir died silently and the only way to find out why is
> > using the debug switch. More over, the init script told a successful
> > restart.
> 
> Here I defer to the bacula-dir 

Bug#825064: Bacula director does not start silently due to database mismatch

[Paul Gevers]

Hi

tl;dr: In the (long) past, the question during migration was different
and extremely confusing with respect to the underlaying logic. Klaus
probably got the old question, opted out of assistance and now had
problems during the upgrade. With respect to the current situation in
all involved packages, there is only a possible improvement in
dbconfig-common with respect to dpkg-reconfigure behavior.

I propose to reassign this bug to dbconfig-common to implement
dpkg-reconfigure options to opt-in for dbconfig-common support while not
reinstalling the database.

I'd like to note that while I was investigating what to write below, I
discovered three unrelated issues in two packages in how they react with
dpkg-reconfigure (in dbconfig-common and cacti), so whatever the outcome
of this bug is, it is going to improve the world. I will file those bugs
shortly.

On 24-05-16 22:40, Klaus Ethgen wrote:
> Am Di den 24. Mai 2016 um 18:02 schrieb Paul Gevers:
>> dbconfig-common will not reinstall the database on updates. If it ever
>> does that it is a grave bug. Klaus is right however that the database
>> can be reinstalled with dpkg-reconfigure, so you can loose the old
>> database that way, but that is intended behavior. The text he quotes is
>> however not the question that gets asked during upgrades. The text
>> during upgrades is given below and says nothing about reinstallation of
>> the database.
> 
> I didn't get the option at all to upgrade the database. I only always
> got the quoted question ever.

I am not sure if you are now talking about the current upgrade. If you
are than that is correct, you didn't get the question because you had
dbc_install=false. If you are talking about "ever" than something
clearly failed during the migration. Note however, this the question
that got asked (not the underlaying logic) has changed since
dbconfig-common 1.8.45 (released on 23 Feb 2010). As bacula migrated to
dbconfig-common support for their MySQL and PostgreSQL databases way
before that time (in 2006), I suspect you got the old (install) question
and this would explain why you haven't seen the question in mentioned in
my previous e-mail.

>> The reason why dbc_install=false drops the full support of
>> dbconfig-common is because that is the variable that is set during the
>> initial installation (and the only one if one opts-out of support). So
>> we need to check this before anything else. If you didn't want install
>> support, it doesn't make sense to ask if you want upgrade support.
> 
> And that might be the problem.

Why?

> At the initial installation that was
> handled via dbconfig, I already had a populated database that I couldn't
> risk to lose. For that reason I answered the already quoted question
> with "no" in the first place.

As mentioned, if bacula switched before 2010, than the bug that you got
the wrong question has long been fixed. A package that switches to
dbconfig-common MUST tell dbconfig-common the version in which the
switch took place. If you are upgrading from a version before the
switch, dbconfig-common will not install (I haven't checked yet, but I
believe not even before the question changed), but merely upgrades your
database.

> There was never a question about update.

As explained, with dbc_install=false that is to be expected.

> I never edited that file before. I always used dpkg-reconfigure (or the
> debconf question at the begin). And that was when the database already
> existed.

Interestingly, (and we could consider this a bug in dbconfig-common) you
can't get the dbc-install variable set to "true" via dpkg-reconfigure if
you are answering "no, I don't want you to reinstall the database". So
the only way to get dbconfig-common support after the first time is
answered with "no" is to edit the file. But, as it stands, you told the
package to NOT use dbconfig-common, and now you are expecting from the
package that even without dbconfig-common help it should do the right
thing? I think that is unreasonable to expect (although I grant you that
you may expect an option with dpkg-reconfigure to actually opt-in
again). Just so you know why I think the current behavior (again, minus
the reconfigure option) is correct, I am pointing you to the policy on
asking questions, paragraph 3.9.1¹ which says: "should ensure that the
user will only ever be asked each question once". Therefore, if you say
no, that is what we will honor.

> However, I don't think that the name should be changed but it should do
> what it is named for.

You just confessed that you never changed the file manually, so the name
of the variable doesn't matter. The question it stands for is, "do you
want dbconfig-common to manage the database on behalf of ${pkg}". And as
already noted, the question that is actually asked has been changed more
than 6 years ago.

> If install is false and upgrade is true, that is
> exactly what I have here and it should upgrade the database independent
> of the install setting.

Again, 

Bug#728144: squid3: Pinger Segmentation fault in Debug::finishDebug on delete CurrentDebug;

[Fernando Toledo]

Bug still exists in 3.4.8-6+deb8u2, please apply the patch that solved it!
Thanks!

-- 
Fernando Toledo
Dock Sud BBS
http://bbs.docksud.com.ar
telnet://bbs.docksud.com.ar

Processed: Re: espresso: FTBFS on armel: hangs during the build

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #818432 [src:espresso] espresso: FTBFS on armel: hangs during the build
Severity set to 'normal' from 'serious'

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

Bug#818432: espresso: FTBFS on armel: hangs during the build

[Andreas Beckmann]

Followup-For: Bug #818432
Control: severity -1 normal

I just had espresso decrufted to remove the outdated armel build, thus
downgrading the severity.


Andreas

Bug#820344: [PKG-Openstack-devel] Bug#820344: python-oslo.privsep: FTBFS: _StringException: Empty attachments:

[Thomas Goirand]

On 05/26/2016 05:04 PM, Chris Lamb wrote:
> Hi zigo,
> 
>> Any idea what could be different between your sbuild run and mine?
> 
> I'm building under Docker

Could I then suppose that this is a specific issue with your Docker
setup? I don't see how it could be otherwise, as the package builds
cleanly for me in a normal sbuild. Could you retry without docker?

> perhaps that has something to do with the capabilities?

That's really possible, as oslo.privsep is really about dealing with
root privileges (ie: it's a replacement for rootwrap that, at some
point, will be deprecated).

> "KeyError: 4" is something to do with CAP_FSETID according to 
> , but 4 isn't mentioned in oslo.privsep.capabilities.
> 
> Hope that helps :)

I'm not sure it does ... yet ! :)

Cheers,

Thomas Goirand (zigo)

Bug#722608: marked as done (libcrypt-nettle-perl: FTBFS with perl 5.18)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 11:52:28 +
with message-id 
and subject line Bug#825447: Removed package(s) from experimental
has caused the Debian Bug report #722608,
regarding libcrypt-nettle-perl: FTBFS with perl 5.18
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.)


-- 
722608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcrypt-nettle-perl
Version: 0.3-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

libcrypt-nettle-perl FTBFS in experimental:

 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
syntax error at inc/Devel/CheckLib.pm line 180, near "$mm_attr_key qw(LIBS INC)"
syntax error at inc/Devel/CheckLib.pm line 187, near "}"
Global symbol "%args" requires explicit package name at inc/Devel/CheckLib.pm 
line 191.
syntax error at inc/Devel/CheckLib.pm line 195, near "}"
syntax error at inc/Devel/CheckLib.pm line 201, near "}"
Global symbol "@headers" requires explicit package name at 
inc/Devel/CheckLib.pm line 209.
Global symbol "@headers" requires explicit package name at 
inc/Devel/CheckLib.pm line 252.
Global symbol "@libs" requires explicit package name at inc/Devel/CheckLib.pm 
line 255.
Global symbol "@libpaths" requires explicit package name at 
inc/Devel/CheckLib.pm line 262.
Global symbol "@libpaths" requires explicit package name at 
inc/Devel/CheckLib.pm line 269.
Global symbol "@libpaths" requires explicit package name at 
inc/Devel/CheckLib.pm line 279.
Global symbol "@libpaths" requires explicit package name at 
inc/Devel/CheckLib.pm line 289.
syntax error at inc/Devel/CheckLib.pm line 304, near "}"
inc/Devel/CheckLib.pm has too many errors.
Compilation failed in require at Makefile.PL line 2.
BEGIN failed--compilation aborted at Makefile.PL line 2.
dh_auto_configure: perl Makefile.PL INSTALLDIRS=vendor create_packlist=0 
returned exit code 255
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Andreas
--- End Message ---
--- Begin Message ---
Version: 0.3-1+rm

Dear submitter,

as the package libcrypt-nettle-perl has just been removed from the Debian 
archive
experimental we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/825447

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#825497: marked as done (mono: uninstallable packages on arm64)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 10:59:46 +
with message-id 
and subject line Bug#825497: fixed in mono 4.2.1.102+dfsg2-8
has caused the Debian Bug report #825497,
regarding mono: uninstallable packages on arm64
to be marked as done.

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

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


-- 
825497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mono
Version: 4.2.1.102+dfsg2-7
Severity: serious

Your package is broken on arm64:

mono-complete/arm64 unsatisfiable Depends: libmono-2.0-1 (= 4.2.1.102+dfsg2-7)
mono-runtime-dbg/arm64 unsatisfiable Depends: mono-runtime-boehm (= 
4.2.1.102+dfsg2-7)

See how some packages are built on arm64 but others aren't:
 mono-complete deb cli-mono optional 
arch=amd64,armel,arm64,armhf,i386,mipsel,kfreebsd-amd64,kfreebsd-i386,ppc64,ppc64el,s390x
 libmono-2.0-1 deb cli-mono optional 
arch=amd64,armel,armhf,i386,mipsel,kfreebsd-amd64,kfreebsd-i386,ppc64,ppc64el,s390x
 libmono-2.0-dev deb cli-mono optional 
arch=amd64,armel,arm64,armhf,i386,mipsel,kfreebsd-amd64,kfreebsd-i386,ppc64,ppc64el,s390x

That prevents mono (and other packages) from entering testing.

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: mono
Source-Version: 4.2.1.102+dfsg2-8

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

Debian distribution maintenance software
pp.
Jo Shields  (supplier of updated mono 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: SHA1

Format: 1.8
Date: Fri, 27 May 2016 10:46:30 +0100
Source: mono
Binary: mono-runtime-common mono-runtime mono-runtime-sgen mono-runtime-boehm 
mono-runtime-dbg mono-utils ca-certificates-mono mono-complete libmono-2.0-1 
libmono-2.0-dev libmonosgen-2.0-1 libmonosgen-2.0-1-dbg libmonosgen-2.0-dev 
libmonoboehm-2.0-1 libmonoboehm-2.0-1-dbg libmonoboehm-2.0-dev libmono-profiler 
libmono-cil-dev libmono-posix4.0-cil libmono-codecontracts4.0-cil 
libmono-compilerservices-symbolwriter4.0-cil libmono-csharp4.0c-cil 
libmono-http4.0-cil libmono-cecil-private-cil libmono-c5-1.1-cil 
libmono-webbrowser4.0-cil libmono-management4.0-cil libmono-messaging4.0-cil 
libmono-messaging-rabbitmq4.0-cil libmono-rabbitmq4.0-cil libmono-simd4.0-cil 
libmono-smdiagnostics0.0-cil libmono-corlib4.5-cil libmono-i18n4.0-all 
libmono-i18n4.0-cil libmono-i18n-cjk4.0-cil libmono-i18n-mideast4.0-cil 
libmono-i18n-other4.0-cil libmono-i18n-rare4.0-cil libmono-i18n-west4.0-cil 
libmono-parallel4.0-cil libmono-system4.0-cil 
libmono-system-componentmodel-composition4.0-cil
 libmono-system-componentmodel-dataannotations4.0-cil 
libmono-system-configuration4.0-cil libmono-system-configuration-install4.0-cil 
libmono-system-core4.0-cil libmono-system-drawing4.0-cil 
libmono-system-dynamic4.0-cil libmono-system-enterpriseservices4.0-cil 
libmono-system-json4.0-cil libmono-system-json-microsoft4.0-cil 
libmono-system-management4.0-cil libmono-system-net4.0-cil 
libmono-system-net-http4.0-cil libmono-system-net-http-formatting4.0-cil 
libmono-system-numerics4.0-cil libmono-system-security4.0-cil 
libmono-system-serviceprocess4.0-cil 
libmono-system-threading-tasks-dataflow4.0-cil 
libmono-system-transactions4.0-cil libmono-system-xml4.0-cil 
libmono-system-xml-linq4.0-cil libmono-custommarshalers4.0-cil 
libmono-system-messaging4.0-cil libmono-security4.0-cil libmono-data-tds4.0-cil 
libmono-system-data4.0-cil libmono-system-data-datasetextensions4.0-cil 
libmono-system-data-services4.0-cil libmono-system-data-services-client4.0-cil
 libmono-system-data-linq4.0-cil libmono-system-drawing-design4.0-cil 
libmono-system-design4.0-cil libmono-system-identitymodel4.0-cil 
libmono-system-identitymodel-selectors4.0-cil 
libmono-system-reactive-core2.2-cil libmono-system-reactive-debugger2.2-cil 
libmono-system-reactive-experimental2.2-cil 
libmono-system-reactive-interfaces2.2-cil libmono-system-reactive-linq2.2-cil 
libmono-system-reactive-observable-aliases0.0-cil 

Bug#825021: marked as done (metview: FTBFS on i386 architecture (and also on kfreebsd-i386))

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 10:52:38 +
with message-id 
and subject line Bug#825021: fixed in metview 4.6.5-3
has caused the Debian Bug report #825021,
regarding metview: FTBFS on i386 architecture (and also on kfreebsd-i386)
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.)


-- 
825021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:metview
Version: 4.6.5-2
Severity: serious

Dear maintainer:

This package FTBFS on the (release architecture) i386:

--
[...]
make[3]: *** No rule to make target 
'/usr/lib/gcc/i586-linux-gnu/5/libgfortran.so', needed by 'bin/GeoTool'.  Stop.
--

It also fails on (non-release architecture) kfreebsd-i386 and the error is 
almost the same:

--
[...]
make[3]: *** No rule to make target 
'/usr/lib/gcc/i586-kfreebsd-gnu/5/libgfortran.so', needed by 'bin/GeoTool'.  
Stop.
--

Build logs available here:

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

and also here:

https://reproducible.debian.net/rb-pkg/unstable/amd64/metview.html

Thanks.
--- End Message ---
--- Begin Message ---
Source: metview
Source-Version: 4.6.5-3

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 May 2016 10:14:42 +0100
Source: metview
Binary: metview metview-data libmetview-dev
Architecture: source amd64 all
Version: 4.6.5-3
Distribution: sid
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libmetview-dev - Development files for MetView
 metview- Interactive data visualization and analysis environment,
 metview-data - Data needed for the Metview data analysis environment
Closes: 825021
Changes:
 metview (4.6.5-3) unstable; urgency=medium
 .
   * Depend on magics >= 2.28.0-2 to get fixed gfortran dependency.
 Closes: #825021
Checksums-Sha1:
 e52fd69d14b4e8d791e0274de2274ba294e3b59d 2424 metview_4.6.5-3.dsc
 786de536ebcc3987b87a4c39a8a185641e44cf22 47636 metview_4.6.5-3.debian.tar.xz
 0bb278873bd177e446abacb33a9f8deb346d7c9e 233322 
libmetview-dev_4.6.5-3_amd64.deb
 ffe71db5dbb468ac727be83682edcb939eb7d673 1710474 metview-data_4.6.5-3_all.deb
 a5f28a1d5f525a14776626f59a968e544c9ada18 118249882 
metview-dbgsym_4.6.5-3_amd64.deb
 649ff8e9ec72745392a4b6d88c30d45f8ae8fe71 8249644 metview_4.6.5-3_amd64.deb
Checksums-Sha256:
 7626656085e0beb9ff068581b56bec5d280f43ae00bb036b20297dedb4061313 2424 
metview_4.6.5-3.dsc
 a06e215324aaf78535f9b7c5beb56f0138b6d622f170e8607d79ed5ee6c92453 47636 
metview_4.6.5-3.debian.tar.xz
 a52df80b1dffb1209a2229b33c00f294fb006f08a7dedb9c4f0de7b0daa1a28d 233322 
libmetview-dev_4.6.5-3_amd64.deb
 0d61a471556fecc9a3075db0bce7ef9b69e5ab781e5d890fa109395be7b9b1e4 1710474 
metview-data_4.6.5-3_all.deb
 af0f8ae17cb75537b185d5c1c81e702bfba08b75e884cd5e7bbdb04b2bf4166a 118249882 
metview-dbgsym_4.6.5-3_amd64.deb
 a73ce685eadd1b133340b3fddf0ffb87fd1a023be417e2606e65b19d757cd12f 8249644 
metview_4.6.5-3_amd64.deb
Files:
 c27bcf50fa3d153c681c03960504b184 2424 science optional metview_4.6.5-3.dsc
 d928573dfc6ec5734b60fc54bd39eb93 47636 science optional 
metview_4.6.5-3.debian.tar.xz
 263bb3ec5a5c288e3d1bd0410f113674 233322 libdevel optional 
libmetview-dev_4.6.5-3_amd64.deb
 c40258d576a7f8886d6d5a23b25b77fa 1710474 science optional 
metview-data_4.6.5-3_all.deb
 

Bug#825473: marked as done (libunistring0: Upstream had a SONAME filename change, but libunitstring0 package name didn't change.)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 10:24:14 +
with message-id 
and subject line Bug#825471: fixed in libunistring 0.9.6+really0.9.3-0.1
has caused the Debian Bug report #825471,
regarding libunistring0: Upstream had a SONAME filename change, but 
libunitstring0 package name didn't change.
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.)


-- 
825471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libunistring0
Version: 0.9.6-1.1
Severity: important

Dear Maintainer,

I was attempting to build some package that uses gettext and got the
following error:

msgmerge: error while loading shared libraries: libunistring.so.0:
cannot open shared object file: No such file or directory

I was able to replicate it by just running /usr/bin/msgmerge

Version:

i  libunistring0:amd64 0.9.3-5.2+b1   amd64  Unicode string
library for C

has the files:

dpkg --listfiles libunistring0 | grep libunistring.so.0
/usr/lib/x86_64-linux-gnu/libunistring.so.0.1.2
/usr/lib/x86_64-linux-gnu/libunistring.so.0

Version
ii  libunistring0:amd64 0.9.6-1.1  amd64  Unicode string
library for C

has the files:

dpkg --listfiles libunistring0 | grep libunistring.so
/usr/lib/x86_64-linux-gnu/libunistring.so.2.0.0
/usr/lib/x86_64-linux-gnu/libunistring.so.2

I'm pretty sure that means the package name libunistring0 should've
been named
libunistring2 and there probably needs to be a transition.

Diane Trout


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

Kernel: Linux 4.5.0-2-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: unable to detect

Versions of packages libunistring0 depends on:
ii  libc6  2.22-9

libunistring0 recommends no packages.

libunistring0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libunistring
Source-Version: 0.9.6+really0.9.3-0.1

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated libunistring package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 May 2016 10:11:04 +0200
Source: libunistring
Binary: libunistring-dev libunistring0
Architecture: source
Version: 0.9.6+really0.9.3-0.1
Distribution: unstable
Urgency: medium
Maintainer: Andreas Rottmann 
Changed-By: Stephen Kitt 
Description:
 libunistring-dev - Unicode string library for C - development files
 libunistring0 - Unicode string library for C
Closes: 825471
Changes:
 libunistring (0.9.6+really0.9.3-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Re-upload 0.9.3-5.4 to revert the soname bump in 0.9.6-1.1. (Closes:
 #825471.)
   * Drop the explicit ldconfig triggers, debhelper handles this on its
 own.
Checksums-Sha1:
 d3148917b321d07e986fa05218bceb405fdc45b3 2109 
libunistring_0.9.6+really0.9.3-0.1.dsc
 e1ea13c24a30bc93932d19eb5ad0704a618506dd 2555215 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 dbe46c35ce77b20d86437a6280eaec16ea082ad2 35372 
libunistring_0.9.6+really0.9.3-0.1.debian.tar.xz
Checksums-Sha256:
 bf73a89a416333268ac9b457a06d1d92e5402c4f392187ad30e6146ffd3600ae 2109 
libunistring_0.9.6+really0.9.3-0.1.dsc
 610d3ec724fbdaa654afe3cff20b9f4d504be3fd296fded2e0f7f764041006a3 2555215 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 2d7636b16a56f1ad09748121a2181db4c2687fa83324c2f17bf451ee01b9de93 35372 
libunistring_0.9.6+really0.9.3-0.1.debian.tar.xz
Files:
 7014d83db609900c76bfbbc77a486a44 2109 libs optional 
libunistring_0.9.6+really0.9.3-0.1.dsc
 db8eca3b64163abadf8c40e5cecc261f 2555215 libs optional 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 276fbe32ac3782fbe487d10327441d19 35372 libs optional 
libunistring_0.9.6+really0.9.3-0.1.debian.tar.xz

Bug#825096: dolfin: FTBFS: No rule to make target '/usr/lib/libgl2ps.so', needed by

[Gert Wollny]

This is indeed a transition problem because gl2ps moved to multiarch,
and the vtk cmake files specify full path names of the dependent
libraries. 

I think this is a good moment to move vtk-6.3 to unstable - 
which I will do this weekend.

(The alternative would be a vtk-6.2 binNMU, but IMHO at this point this
would be a waste of computing cycles.) 

Best, 
Gert

Bug#825471: marked as done (libunistring0: soname change without package name change)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 10:24:14 +
with message-id 
and subject line Bug#825471: fixed in libunistring 0.9.6+really0.9.3-0.1
has caused the Debian Bug report #825471,
regarding libunistring0: soname change without package name change
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.)


-- 
825471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libunistring0
Version: 0.9.6-1.1
Severity: serious

0.9.6-1.1 features a soname bump from libunistring.so.0 to
libunistring.so.2, without changing the package name and making a
library transition. This breaks all reverse dependencies, e.g.:

(sid)ametzler@argenau:~$ ldd /usr/lib/x86_64-linux-gnu/libguile-2.0.so \ |
  grep unis
libunistring.so.0 => not found


ametzler@argenau:/chroots/sid/var/cache/apt/archives$ ls libunistring0_*
libunistring0_0.9.3-5.2+b1_amd64.deb  libunistring0_0.9.6-1.1_amd64.deb
ametzler@argenau:/chroots/sid/var/cache/apt/archives$ debdiff libunistring0_*
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/lib/x86_64-linux-gnu/libunistring.so.2.0.0
-rw-r--r--  root/root   DEBIAN/triggers
lrwxrwxrwx  root/root   /usr/lib/x86_64-linux-gnu/libunistring.so.2 -> 
libunistring.so.2.0.0

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/lib/x86_64-linux-gnu/libunistring.so.0.1.2
-rw-r--r--  root/root   /usr/share/doc/libunistring0/changelog.Debian.amd64.gz
-rwxr-xr-x  root/root   DEBIAN/postinst
-rwxr-xr-x  root/root   DEBIAN/postrm
lrwxrwxrwx  root/root   /usr/lib/x86_64-linux-gnu/libunistring.so.0 -> 
libunistring.so.0.1.2

Control files: lines which differ (wdiff format)

Installed-Size: [-1133-] {+1504+}
[-Pre-Depends: multiarch-support-]
Source: libunistring [-(0.9.3-5.2)-]
Version: [-0.9.3-5.2+b1-] {+0.9.6-1.1+}


cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
Source: libunistring
Source-Version: 0.9.6+really0.9.3-0.1

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated libunistring package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 May 2016 10:11:04 +0200
Source: libunistring
Binary: libunistring-dev libunistring0
Architecture: source
Version: 0.9.6+really0.9.3-0.1
Distribution: unstable
Urgency: medium
Maintainer: Andreas Rottmann 
Changed-By: Stephen Kitt 
Description:
 libunistring-dev - Unicode string library for C - development files
 libunistring0 - Unicode string library for C
Closes: 825471
Changes:
 libunistring (0.9.6+really0.9.3-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Re-upload 0.9.3-5.4 to revert the soname bump in 0.9.6-1.1. (Closes:
 #825471.)
   * Drop the explicit ldconfig triggers, debhelper handles this on its
 own.
Checksums-Sha1:
 d3148917b321d07e986fa05218bceb405fdc45b3 2109 
libunistring_0.9.6+really0.9.3-0.1.dsc
 e1ea13c24a30bc93932d19eb5ad0704a618506dd 2555215 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 dbe46c35ce77b20d86437a6280eaec16ea082ad2 35372 
libunistring_0.9.6+really0.9.3-0.1.debian.tar.xz
Checksums-Sha256:
 bf73a89a416333268ac9b457a06d1d92e5402c4f392187ad30e6146ffd3600ae 2109 
libunistring_0.9.6+really0.9.3-0.1.dsc
 610d3ec724fbdaa654afe3cff20b9f4d504be3fd296fded2e0f7f764041006a3 2555215 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 

Bug#825462: marked as done (FTBFS: build-arch failure)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 10:29:37 +
with message-id 
and subject line Bug#825462: fixed in scscp-imcce 1.0.2+ds-2
has caused the Debian Bug report #825462,
regarding FTBFS: build-arch failure
to be marked as done.

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

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


-- 
825462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scscp-imcce
Version: 1.0.2+ds-1
Severity: serious
Justification: fails to build from source

Dear Folks,

it appears that the newly introduced build-arch machinery fails
because it also composes the documentation while it must not:
this faulty behaviour is caused by the debian patch
d/p/debianization-doc-texinfo.patch which should be discarded.

Sorry for the noise,
Jerome


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

Kernel: Linux 3.16.7-ckt20-0001-mbp62 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: scscp-imcce
Source-Version: 1.0.2+ds-2

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated scscp-imcce package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 May 2016 00:47:47 +
Source: scscp-imcce
Binary: libscscp1 libscscp1-dev libscscp-doc
Architecture: source
Version: 1.0.2+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Description:
 libscscp-doc - IMCCE SCSCP C Library -- reference manual
 libscscp1  - IMCCE SCSCP C Library -- library package
 libscscp1-dev - IMCCE SCSCP C Library -- development package
Closes: 825462
Changes:
 scscp-imcce (1.0.2+ds-2) unstable; urgency=medium
 .
   * FTBFS fix release (Closes: #825462), fix build-arch failure.
   * Debianization:
 - debian/patches/debianization-doc-texinfo.patch, discard.
Checksums-Sha1:
 e1f9674bd3e7b23a2c975bf85b11d2beeb8af581 2247 scscp-imcce_1.0.2+ds-2.dsc
 c86f3747e970b6b1012612e8912a0c1435e866d3 16440 
scscp-imcce_1.0.2+ds-2.debian.tar.xz
Checksums-Sha256:
 e0bb8dd8f4db5a97e3169202660f9d35c73893ad94ba2b30c56358daa70c 2247 
scscp-imcce_1.0.2+ds-2.dsc
 3739c4c4be93a977a9572f50374918e1bd3e54f4d13c44cfbda7057c9eb5e470 16440 
scscp-imcce_1.0.2+ds-2.debian.tar.xz
Files:
 dc84b3c82572d2bf7e1cea530a7a53cf 2247 math extra scscp-imcce_1.0.2+ds-2.dsc
 48338bdaeda95a4ca014a70ffd5ffe4a 16440 math extra 
scscp-imcce_1.0.2+ds-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXR//IAAoJEPNPCXROn13ZuiIQALqq+5Js7WJhjjjEVYMUOKGR
lqBjvQ4jnepxUJAVZ9nVklGPGvQ2ikYQ+ll1JkTp17SB5qUdFYaLseGDBceQqo3B
P8w8SwZY8c3e1G9bX3Kx3FmeDbmP7c2hOMFnZGpjti9NwhhBWY72/7SSOivq8duQ
/C0GR3XzWsv5/Cpnw/UHKv5rvRHQHmlGp0wI651V4s5S+nObZG6MkjmLZ3Ww9V7Y
0sTaIevB7zTXR7D2J8sG74C77n3QyrWGJxhvU4Bs7P8+rDtVukr77uERoZKPk7N1
WIpxWx6bzVTMOokeb5I6R2R0+Cp90Hf9wURHl0T1EdBSmzRWhON4HHNV1Fep55oy
zccIMUJ45sFo3q9eGvJjmUbCN+YETtoeXu7ulLXlOBJampJ7vd4HyVgOIQymQ7qF
eUTK7fghOxkCad1z5EaXhmGfxP6BLdoFmsxL148bgjeKgtuBHOWyzJWa1Pbj+xG0
8yFTrRE+E0ck97WvC805LOsRsE7SFi0GJ2O/dFQWX5lErIowj1rqAZolWQ89+tmN
mUs/asZ/L3aR/bW92AaRYyOexZM6xJnWfOkKUq1ssDUviqYo7fBJ4lyWbUzRR77A
InP8rPPuXhmBj+wBFTnoQjpdzS5/O4z3s/3RsxcXcBADCaZw36FQssxggtV5FIbA
N2XAZQ0/ybqBqYk4+bJ5
=av8G
-END PGP SIGNATURE End Message ---

Bug#825474: marked as done (libunistring0: upgrading to 0.9.6-1.1 leads to a problem with shared libraries)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 10:24:14 +
with message-id 
and subject line Bug#825471: fixed in libunistring 0.9.6+really0.9.3-0.1
has caused the Debian Bug report #825471,
regarding libunistring0: upgrading to 0.9.6-1.1 leads to a problem with shared 
libraries
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.)


-- 
825471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libunistring0
Version: 0.9.6-1.1
Severity: critical
Justification: breaks unrelated software

Dear maintainer and non-maintainer,

upgrading libunistring0 to 0.9.6-1.1:amd64 leads to a problem with shared
libraries in other packages.

For instance, nautilus (in its version 3.20.1-2:amd64) won't start, sending the
following error message:

nautilus: error while loading shared libraries: libunistring.so.0: cannot open
shared object file: No such file or directory

as seen when launching nautilus from command line ; then nautilus does not
open. Restarting gnome-shell does not solve the issue.

It seems that a shared library is missing. Could you investigate the problem?
Many thanks.

Downgrading to libunistring0 testing 0.9.3-5.2+b1 resolves the issue (nautilus
starts without error message).

Best,

Ara



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

Kernel: Linux 4.5.0-2-amd64 (SMP w/8 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)

Versions of packages libunistring0 depends on:
ii  libc6  2.22-9

libunistring0 recommends no packages.

libunistring0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libunistring
Source-Version: 0.9.6+really0.9.3-0.1

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated libunistring package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 May 2016 10:11:04 +0200
Source: libunistring
Binary: libunistring-dev libunistring0
Architecture: source
Version: 0.9.6+really0.9.3-0.1
Distribution: unstable
Urgency: medium
Maintainer: Andreas Rottmann 
Changed-By: Stephen Kitt 
Description:
 libunistring-dev - Unicode string library for C - development files
 libunistring0 - Unicode string library for C
Closes: 825471
Changes:
 libunistring (0.9.6+really0.9.3-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Re-upload 0.9.3-5.4 to revert the soname bump in 0.9.6-1.1. (Closes:
 #825471.)
   * Drop the explicit ldconfig triggers, debhelper handles this on its
 own.
Checksums-Sha1:
 d3148917b321d07e986fa05218bceb405fdc45b3 2109 
libunistring_0.9.6+really0.9.3-0.1.dsc
 e1ea13c24a30bc93932d19eb5ad0704a618506dd 2555215 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 dbe46c35ce77b20d86437a6280eaec16ea082ad2 35372 
libunistring_0.9.6+really0.9.3-0.1.debian.tar.xz
Checksums-Sha256:
 bf73a89a416333268ac9b457a06d1d92e5402c4f392187ad30e6146ffd3600ae 2109 
libunistring_0.9.6+really0.9.3-0.1.dsc
 610d3ec724fbdaa654afe3cff20b9f4d504be3fd296fded2e0f7f764041006a3 2555215 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 2d7636b16a56f1ad09748121a2181db4c2687fa83324c2f17bf451ee01b9de93 35372 
libunistring_0.9.6+really0.9.3-0.1.debian.tar.xz
Files:
 7014d83db609900c76bfbbc77a486a44 2109 libs optional 
libunistring_0.9.6+really0.9.3-0.1.dsc
 db8eca3b64163abadf8c40e5cecc261f 2555215 libs optional 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 276fbe32ac3782fbe487d10327441d19 35372 libs optional 
libunistring_0.9.6+really0.9.3-0.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXSAEnAAoJEIDTAvWIbYOcVyoP/2lidSvbe1b+vhKms8rZ8j4b

Processed: found 825501 in 1.5-1, tagging 825501

[Debian Bug Tracking System]

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

> found 825501 1.5-1
Bug #825501 [src:tika] CVE-2016-4434
Marked as found in versions tika/1.5-1.
> tags 825501 + upstream fixed-upstream
Bug #825501 [src:tika] CVE-2016-4434
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#825472: marked as done (libunistring0: soname bump without name change)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 10:24:14 +
with message-id 
and subject line Bug#825471: fixed in libunistring 0.9.6+really0.9.3-0.1
has caused the Debian Bug report #825471,
regarding libunistring0: soname bump without name change
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.)


-- 
825471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libunistring0
Version: 0.9.6-1.1
Severity: grave
User: helm...@debian.org
Usertags: rebootstrap

Manuel's NMU introduces a soname bump (from 0 to 2) without changing the
binary package name. This is a policy violation and makes any reverse
dependency of libunistring0 fail. Please revert and use a proper
transition requesting a transition slot from the release team in
advance.

Helmut
--- End Message ---
--- Begin Message ---
Source: libunistring
Source-Version: 0.9.6+really0.9.3-0.1

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated libunistring package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 27 May 2016 10:11:04 +0200
Source: libunistring
Binary: libunistring-dev libunistring0
Architecture: source
Version: 0.9.6+really0.9.3-0.1
Distribution: unstable
Urgency: medium
Maintainer: Andreas Rottmann 
Changed-By: Stephen Kitt 
Description:
 libunistring-dev - Unicode string library for C - development files
 libunistring0 - Unicode string library for C
Closes: 825471
Changes:
 libunistring (0.9.6+really0.9.3-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Re-upload 0.9.3-5.4 to revert the soname bump in 0.9.6-1.1. (Closes:
 #825471.)
   * Drop the explicit ldconfig triggers, debhelper handles this on its
 own.
Checksums-Sha1:
 d3148917b321d07e986fa05218bceb405fdc45b3 2109 
libunistring_0.9.6+really0.9.3-0.1.dsc
 e1ea13c24a30bc93932d19eb5ad0704a618506dd 2555215 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 dbe46c35ce77b20d86437a6280eaec16ea082ad2 35372 
libunistring_0.9.6+really0.9.3-0.1.debian.tar.xz
Checksums-Sha256:
 bf73a89a416333268ac9b457a06d1d92e5402c4f392187ad30e6146ffd3600ae 2109 
libunistring_0.9.6+really0.9.3-0.1.dsc
 610d3ec724fbdaa654afe3cff20b9f4d504be3fd296fded2e0f7f764041006a3 2555215 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 2d7636b16a56f1ad09748121a2181db4c2687fa83324c2f17bf451ee01b9de93 35372 
libunistring_0.9.6+really0.9.3-0.1.debian.tar.xz
Files:
 7014d83db609900c76bfbbc77a486a44 2109 libs optional 
libunistring_0.9.6+really0.9.3-0.1.dsc
 db8eca3b64163abadf8c40e5cecc261f 2555215 libs optional 
libunistring_0.9.6+really0.9.3.orig.tar.gz
 276fbe32ac3782fbe487d10327441d19 35372 libs optional 
libunistring_0.9.6+really0.9.3-0.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXSAEnAAoJEIDTAvWIbYOcVyoP/2lidSvbe1b+vhKms8rZ8j4b
kIQqUGVEAdxOkkMWl65J3QWd/prfTPAVIcu+UQZJD6tMSaBbeOYxD5JvFGUlJZLi
Q396sxHJydmRx50Gkp3aAj4ii/FEBiBg9xPuZFNktH26ohZ+hJebkA7+42+nk/AH
R/mBcWlAC/A9LBYrTLnmY9NTFjMIqGHGlMJZh/9XqH7UbjTnqstrfwuBFFy9eCMr
LgLI/Qv3UEkL/oYTvqu/MAtDF7AIzKd4797xI5lzD4hiyPE8wkOshxOce4lD8TAw
WzYrdSHjpPD+1OmEQIS62V9rHiyghm9oJ6nrBtvTpm4XCfiMv6Of4Igm6DBJFCDa
H9NOP/vRdZRytwTfRAUqvzkYpcGzwJqP2BJSAHS72vJQ+CvvDT5v8S8c0Bw+GeBG
UMXqtHif4JRQYQCregA98Ti2aKlHyu7Wre7fBhi4NUZyInL0AtRtEg1SB+Gv+/ke
tysOJV+jF2MsMtNETF3plxzVHPSn4mBuILBT5VuTsoCI0YkSp3JoTTMiwEPOGl1M
dcU/zElQuSluqp9VoIBEiySGn2k5oxi84CyADvShql33mARtoxLrZLl79hxpRr77
mQiUb1O5XTFLTGYZyFfNRqvgKEkxhaAGYHz6I+X9v5FWWdMeRMyqMLtojPaKqosG
AmWgtscRaWCxRIX9K8Tf
=m5da
-END PGP SIGNATURE End Message ---

Bug#818214: marked as done (grads: Jasper removal)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 10:21:32 +
with message-id 
and subject line Bug#818214: fixed in grads 2:2.1.a3-1
has caused the Debian Bug report #818214,
regarding grads: Jasper removal
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.)


-- 
818214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grads
Severity: important
User: j...@debian.org
Usertags: jasper-rm

Hi, jasper will be removed from Debian for the stretch release (and
following that, the archive in general).

It's been unmaintained for nearly a decade, please als see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812630

Your package uses jasper, so please either remove the JPEG2000
functionality or move to a supported implementation (e.g. openjpeg or
ffmpeg).

A removal tracker has been setup by the release team at
https://release.debian.org/transitions/html/jasper-rm.html

This bug will be bumped to release-critical status in a few weeks.

Cheers,

Moritz 
--- End Message ---
--- Begin Message ---
Source: grads
Source-Version: 2:2.1.a3-1

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated grads 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: Tue, 24 May 2016 14:13:26 +0100
Source: grads
Binary: grads
Architecture: source amd64
Version: 2:2.1.a3-1
Distribution: sid
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 grads  - Grid Analysis and Display System for earth science data
Closes: 818214
Changes:
 grads (2:2.1.a3-1) unstable; urgency=medium
 .
   * Standards-Version: 3.9.8
   * Add data, examples tarballs
   * Depend on libgrib2c-dev >= 1.6.0-3 to remove Jasper. Closes: #818214.
   * Depend on libpng-dev >= 1.6.21; png16 transition done.
   * Enable png16 patch, look for it, not png15
   * Patch to use NC_CONFIG in /usr/bin
Checksums-Sha1:
 a075a296a6d347e679923744d1c8f08f0e40a238 2721 grads_2.1.a3-1.dsc
 f24019d391cac79d6e36e74fe2aa294098bd4c81 1137696 grads_2.1.a3.orig-data.tar.xz
 77a1e13ac328e766078dcdbeabea3efdf673d1c3 1387936 
grads_2.1.a3.orig-example.tar.xz
 1c649cdee9b24b4fe1e16d35859e43163aaa0f0e 4439380 grads_2.1.a3.orig.tar.xz
 c15fa55c016467f697fcd79bc91c095ded74b018 10564 grads_2.1.a3-1.debian.tar.xz
 359bdbb91e28e099fad40f3c07dfbbd7f1751941 962342 grads-dbgsym_2.1.a3-1_amd64.deb
 d6090fedcd04e16030406bde8567473fb12f2b36 4029286 grads_2.1.a3-1_amd64.deb
Checksums-Sha256:
 5f584686ce91c76b062e8e814c73f257e28da5d445d9e18addf15dfc4b790094 2721 
grads_2.1.a3-1.dsc
 e8d239dc06248365ae2ba966e6691b9ce41f82a198a31bfa165f19d5061ef181 1137696 
grads_2.1.a3.orig-data.tar.xz
 28ce375aa90eb15a12267efaad0f8216468f69ec2a47ed0f6c76490a79d19eb3 1387936 
grads_2.1.a3.orig-example.tar.xz
 48836097f9c251659072fb3aeff21cd5adbc82297a83d770252d41deacc7 4439380 
grads_2.1.a3.orig.tar.xz
 4ac9cff9ede1dc5008cfd47d0cbf51dcef436ed2f7f7904762f7efed17a17c25 10564 
grads_2.1.a3-1.debian.tar.xz
 a5d525608c6cf722d82ead7917f4ec37457c4fed21408aad49ef863893472a1f 962342 
grads-dbgsym_2.1.a3-1_amd64.deb
 485d6dd2df3413457b86bf18ec5243f7fc40ac148d356c7a43e73bd21a7bd107 4029286 
grads_2.1.a3-1_amd64.deb
Files:
 5da75bcb6c7d5d37a6cf94a0d2647a76 2721 science extra grads_2.1.a3-1.dsc
 abd002b0ff8276d6c7c2097ef471101c 1137696 science extra 
grads_2.1.a3.orig-data.tar.xz
 34ab6609ffdd41df5622380f56a845f4 1387936 science extra 
grads_2.1.a3.orig-example.tar.xz
 d819306b57909c2b4fa9b66c7440078c 4439380 science extra grads_2.1.a3.orig.tar.xz
 9317cafa8d8b0ceb1e6b93269d375ad3 10564 science extra 
grads_2.1.a3-1.debian.tar.xz
 c8a9856f938289bf7c18601512ad123d 962342 debug extra 
grads-dbgsym_2.1.a3-1_amd64.deb
 fa17f1c0b6ea534c7a72814aec59b716 4029286 science extra grads_2.1.a3-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Processed: fixed 824017 in 1.8.6-1

[Debian Bug Tracking System]

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

> fixed 824017 1.8.6-1
Bug #824017 [src:hgsubversion] hgsubversion: uninstallable in sid
Marked as fixed in versions hgsubversion/1.8.6-1.
> thanks
Stopping processing here.

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

Bug#825501: CVE-2016-4434

[Emmanuel Bourg]

Thank you for the notice Moritz. Tika isn't really used in Debian yet, I
packaged it as a dependency of Apache JMeter but didn't enable it. I'll
fix it in unstable, but I don't think it's worth fixing in Jessie.

Emmanuel Bourg

Bug#825501: CVE-2016-4434

[Moritz Muehlenhoff]

Source: tika
Severity: grave
Tags: security

Hi,
please see http://seclists.org/oss-sec/2016/q2/413  for details.

Cheers,
Moritz

Processed: tagging 750344, found 770240 in 1.2.7-2, tagging 770240, tagging 753189, tagging 753179 ...

[Debian Bug Tracking System]

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

> tags 750344 = sid
Bug #750344 [src:festvox-czech-dita] festvox-czech-dita: FTBFS: US DB: failed 
to read coefs file from ./lpc/dita0001.lpc
Removed tag(s) stretch and jessie.
> found 770240 1.2.7-2
Bug #770240 [src:libsigc++-1.2] libsigc++-1.2: Keep out of testing
Marked as found in versions libsigc++-1.2/1.2.7-2.
> tags 770240 = sid
Bug #770240 [src:libsigc++-1.2] libsigc++-1.2: Keep out of testing
Removed tag(s) stretch.
> tags 753189 = sid
Bug #753189 [src:festvox-czech-krb] festvox-czech-krb: FTBFS: Error reading 
ESPS file ./lpc/krb0012.lpc
Removed tag(s) jessie and stretch.
> tags 753179 = sid
Bug #753179 [src:festvox-czech-machac] festvox-czech-machac: FTBFS: Error 
reading ESPS file ./lpc/machac0004.lpc
Removed tag(s) jessie and stretch.
> notfound 825437 2.1.6
Bug #825437 [src:talloc] talloc fails building on very clean system.
The source 'talloc' and version '2.1.6' do not appear to match any binary 
packages
No longer marked as found in versions talloc/2.1.6.
> found 825437 2.1.6-1
Bug #825437 [src:talloc] talloc fails building on very clean system.
Marked as found in versions talloc/2.1.6-1.
> tags 825370 + sid stretch
Bug #825370 [src:unicap] unicap: FTBFS: mv: cannot stat './config.guess': No 
such file or directory
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Bug#825497: mono: uninstallable packages on arm64

[Emilio Pozuelo Monfort]

Source: mono
Version: 4.2.1.102+dfsg2-7
Severity: serious

Your package is broken on arm64:

mono-complete/arm64 unsatisfiable Depends: libmono-2.0-1 (= 4.2.1.102+dfsg2-7)
mono-runtime-dbg/arm64 unsatisfiable Depends: mono-runtime-boehm (= 
4.2.1.102+dfsg2-7)

See how some packages are built on arm64 but others aren't:
 mono-complete deb cli-mono optional 
arch=amd64,armel,arm64,armhf,i386,mipsel,kfreebsd-amd64,kfreebsd-i386,ppc64,ppc64el,s390x
 libmono-2.0-1 deb cli-mono optional 
arch=amd64,armel,armhf,i386,mipsel,kfreebsd-amd64,kfreebsd-i386,ppc64,ppc64el,s390x
 libmono-2.0-dev deb cli-mono optional 
arch=amd64,armel,arm64,armhf,i386,mipsel,kfreebsd-amd64,kfreebsd-i386,ppc64,ppc64el,s390x

That prevents mono (and other packages) from entering testing.

Cheers,
Emilio

Bug#825495: gnunet: FTBFS: mv: cannot stat 't-vi.gmo': No such file or directory

[Chris Lamb]

Source: gnunet
Version: 0.10.1-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,

gnunet fails to build from source in unstable/amd64:

  [..]

  libtool: link: gcc -shared  -fPIC -DPIC  .libs/plugin_namestore_sqlite.o   
-Wl,-rpath 
-Wl,/home/lamby/temp/cdt.20160527084346.rNJKvUt9zA.gnunet/gnunet-0.10.1/src/gnsrecord/.libs
 -Wl,-rpath 
-Wl,/home/lamby/temp/cdt.20160527084346.rNJKvUt9zA.gnunet/gnunet-0.10.1/src/statistics/.libs
 -Wl,-rpath 
-Wl,/home/lamby/temp/cdt.20160527084346.rNJKvUt9zA.gnunet/gnunet-0.10.1/src/util/.libs
 ../../src/gnsrecord/.libs/libgnunetgnsrecord.so 
../../src/statistics/.libs/libgnunetstatistics.so 
../../src/util/.libs/libgnunetutil.so /usr/lib/x86_64-linux-gnu/libsqlite3.so 
-lm  -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro   -Wl,-soname 
-Wl,libgnunet_plugin_namestore_sqlite.so -o 
.libs/libgnunet_plugin_namestore_sqlite.so
  libtool: link: ( cd ".libs" && rm -f "libgnunet_plugin_namestore_sqlite.la" 
&& ln -s "../libgnunet_plugin_namestore_sqlite.la" 
"libgnunet_plugin_namestore_sqlite.la" )
  /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..  -I../../src/include -Wdate-time -D_FORTIFY_SOURCE=2  
-fno-strict-aliasing -Wall -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security  -c -o plugin_namestore_postgres.lo 
plugin_namestore_postgres.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include 
-Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -Wall -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -c 
plugin_namestore_postgres.c  -fPIC -DPIC -o .libs/plugin_namestore_postgres.o
  /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -fno-strict-aliasing 
-Wall -g -O2 -fstack-protector-strong -Wformat -Werror=format-security  
-export-dynamic -avoid-version -module -no-undefined -Wl,-z,relro -o 
libgnunet_plugin_namestore_postgres.la -rpath /usr/lib/x86_64-linux-gnu/gnunet 
plugin_namestore_postgres.lo ../../src/gnsrecord/libgnunetgnsrecord.la 
../../src/postgres/libgnunetpostgres.la 
../../src/statistics/libgnunetstatistics.la ../../src/util/libgnunetutil.la  
-lpq  -lm 
  libtool: link: gcc -shared  -fPIC -DPIC  .libs/plugin_namestore_postgres.o   
-Wl,-rpath 
-Wl,/home/lamby/temp/cdt.20160527084346.rNJKvUt9zA.gnunet/gnunet-0.10.1/src/gnsrecord/.libs
 -Wl,-rpath 
-Wl,/home/lamby/temp/cdt.20160527084346.rNJKvUt9zA.gnunet/gnunet-0.10.1/src/postgres/.libs
 -Wl,-rpath 
-Wl,/home/lamby/temp/cdt.20160527084346.rNJKvUt9zA.gnunet/gnunet-0.10.1/src/statistics/.libs
 -Wl,-rpath 
-Wl,/home/lamby/temp/cdt.20160527084346.rNJKvUt9zA.gnunet/gnunet-0.10.1/src/util/.libs
 ../../src/gnsrecord/.libs/libgnunetgnsrecord.so 
../../src/postgres/.libs/libgnunetpostgres.so 
../../src/statistics/.libs/libgnunetstatistics.so 
../../src/util/.libs/libgnunetutil.so -lpq -lm  -g -O2 -fstack-protector-strong 
-Wl,-z -Wl,relro   -Wl,-soname -Wl,libgnunet_plugin_namestore_postgres.so -o 
.libs/libgnunet_plugin_namestore_postgres.so
  libtool: link: ( cd ".libs" && rm -f "libgnunet_plugin_namestore_postgres.la" 
&& ln -s "../libgnunet_plugin_namestore_postgres.la" 
"libgnunet_plugin_namestore_postgres.la" )
  gcc -DHAVE_CONFIG_H -I. -I../..  -I../../src/include -Wdate-time 
-D_FORTIFY_SOURCE=2  -fno-strict-aliasing -Wall -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security  -c -o gnunet-namestore.o gnunet-namestore.c
  /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -fno-strict-aliasing 
-Wall -g -O2 -fstack-protector-strong -Wformat -Werror=format-security   
-Wl,-z,relro -o gnunet-namestore gnunet-namestore.o 
../../src/identity/libgnunetidentity.la 
../../src/gnsrecord/libgnunetgnsrecord.la ../../src/util/libgnunetutil.la 
libgnunetnamestore.la  -lm 
  libtool: link: gcc -fno-strict-aliasing -Wall -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z -Wl,relro -o .libs/gnunet-namestore 
gnunet-namestore.o  ../../src/identity/.libs/libgnunetidentity.so 
../../src/gnsrecord/.libs/libgnunetgnsrecord.so 
../../src/util/.libs/libgnunetutil.so ./.libs/libgnunetnamestore.so -lm
  gcc -DHAVE_CONFIG_H -I. -I../..  -I../../src/include -Wdate-time 
-D_FORTIFY_SOURCE=2  -fno-strict-aliasing -Wall -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security  -c -o gnunet-service-namestore.o 
gnunet-service-namestore.c
  /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -fno-strict-aliasing 
-Wall -g -O2 -fstack-protector-strong -Wformat -Werror=format-security   
-Wl,-z,relro -o gnunet-service-namestore gnunet-service-namestore.o 
../../src/namecache/libgnunetnamecache.la 
../../src/gnsrecord/libgnunetgnsrecord.la 
../../src/statistics/libgnunetstatistics.la ../../src/util/libgnunetutil.la 
libgnunetnamestore.la  -lm 
  libtool: link: gcc -fno-strict-aliasing -Wall -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z 

Bug#825471: libunistring0: soname change without package name change

[Stephen Kitt]

On Fri, May 27, 2016 at 09:56:18AM +0100, Manuel A. Fernandez Montecelo wrote:
> 2016-05-27 9:02 GMT+01:00 Stephen Kitt :
> > On Fri, May 27, 2016 at 07:15:48AM +0200, Andreas Metzler wrote:
> >> 0.9.6-1.1 features a soname bump from libunistring.so.0 to
> >> libunistring.so.2, without changing the package name and making a
> >> library transition. This breaks all reverse dependencies, e.g.:
> >
> > I'm preparing an NMU to revert to 0.9.3 (so the version will end up
> > being 0.9.6+really0.9.3 since I need to re-upload an orig tarball).
> 
> Oh dear, sorry for the mess :(
> 
> I can work on that if needed, but if you are ready please go ahead.

Thanks, I've uploaded a fixed package. I'm attaching the diff (which
applies on 0.9.3-5.3) — I don't think there's any point in integrating
it for future uploads :-).

> > Manuel, if you want to re-do the transition, you can simply use
> > version 0.9.6+really0.9.6, until 0.9.7 is released.
> 
> Yes, I'll look into it once the main problem is addressed.

Thanks!

Regards,

Stephen
diff -Nru libunistring-0.9.3/debian/changelog libunistring-0.9.6+really0.9.3/debian/changelog
--- libunistring-0.9.3/debian/changelog	2016-05-26 17:34:55.0 +0200
+++ libunistring-0.9.6+really0.9.3/debian/changelog	2016-05-27 10:11:04.0 +0200
@@ -1,3 +1,13 @@
+libunistring (0.9.6+really0.9.3-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Re-upload 0.9.3-5.4 to revert the soname bump in 0.9.6-1.1. (Closes:
+#825471.)
+  * Drop the explicit ldconfig triggers, debhelper handles this on its
+own.
+
+ -- Stephen Kitt   Fri, 27 May 2016 10:11:04 +0200
+
 libunistring (0.9.3-5.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libunistring-0.9.3/debian/libunistring0.triggers libunistring-0.9.6+really0.9.3/debian/libunistring0.triggers
--- libunistring-0.9.3/debian/libunistring0.triggers	2016-05-26 17:14:45.0 +0200
+++ libunistring-0.9.6+really0.9.3/debian/libunistring0.triggers	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-activate-noawait ldconfig


signature.asc
Description: PGP signature

Bug#825471: libunistring0: soname change without package name change

[Manuel A. Fernandez Montecelo]

2016-05-27 9:02 GMT+01:00 Stephen Kitt :
> On Fri, May 27, 2016 at 07:15:48AM +0200, Andreas Metzler wrote:
>> 0.9.6-1.1 features a soname bump from libunistring.so.0 to
>> libunistring.so.2, without changing the package name and making a
>> library transition. This breaks all reverse dependencies, e.g.:
>
> I'm preparing an NMU to revert to 0.9.3 (so the version will end up
> being 0.9.6+really0.9.3 since I need to re-upload an orig tarball).

Oh dear, sorry for the mess :(

I can work on that if needed, but if you are ready please go ahead.


> Manuel, if you want to re-do the transition, you can simply use
> version 0.9.6+really0.9.6, until 0.9.7 is released.

Yes, I'll look into it once the main problem is addressed.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#583177: marked as done (dvtm does not spawn a shell in new windows)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 08:41:51 + (UTC)
with message-id <673220110.278354.1464338511339.javamail.ya...@mail.yahoo.com>
and subject line already fixed in old-old-stable
has caused the Debian Bug report #583177,
regarding dvtm does not spawn a shell in new windows
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.)


-- 
583177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dvtm
Version: 0.5.2-2
Severity: grave
Justification: renders package unusable

dvtm does not spawn a shell in new windows created by ^g c, sometimes it
does not even create a shell in the first window after starting. dvtm
does not hand, if there is a shell, its usable, creating, resizing and
moving windows works, too.

-- System Information:
Debian Release: squeeze/sid
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dvtm depends on:
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib
ii  libncursesw5  5.7+20081213-1 shared libraries for terminal hand

Versions of packages dvtm recommends:
ii  ncurses-term  5.7+20081213-1 additional terminal type definitio

dvtm suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
As said, no need to keep it open.

G.--- End Message ---

Bug#825483: mame: FTBFS on ppc64el: vector type mismatches

[Andreas Beckmann]

Source: mame
Version: 0.173-6
Severity: serious
Justification: fails to build from source

Hi,

mame FTBFS on ppc64el:
https://buildd.debian.org/status/fetch.php?pkg=mame=ppc64el=0.173-6=1463964270

g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -MMD -MP -MP -DPTR64=1 
-DNDEBUG -DCRLF=2 -DLSB_FIRST -DXMD_H -DFLAC__NO_DLL -DLUA_COMPAT_ALL 
-DLUA_COMPAT_5_1 -DLUA_COMPAT_5_2 -DNO_AFFINITY_NP -I../../../../../src/osd 
-I../../../../../src/emu -I../../../../../src/lib -I../../../../../src/lib/util 
-I../../../../../3rdparty -I../../../../generated/emu 
-I../../../../generated/emu/layout -I../../../../../scripts/src 
-I/usr/include/lua5.3  -m64 --pipe -Wno-deprecated-declarations -O3 
-fno-strict-aliasing -Wno-unknown-pragmas -Wall -Wcast-align -Wundef 
-Wformat-security -Wwrite-strings -Wno-sign-compare -Wno-conversion 
-Wno-unused-result -Wno-array-bounds -m64 -x c++ -std=c++14 
-Woverloaded-virtual -Wsuggest-override -include 
../../../../linux_gcc/obj/x64/Release/emu.h -o 
"../../../../linux_gcc/obj/x64/Release/src/emu/debug/textbuf.o" -c "../.
 ./../../../src/emu/debug/textbuf.cpp"
In file included from ../../../../../src/emu/video/rgbutil.h:19:0,
 from ../../../../../src/emu/rendersw.inc:14,
 from ../../../../../src/osd/modules/render/drawsdl.cpp:20:
../../../../../src/emu/video/rgbvmx.h: In member function 'void 
rgbaint_t::set(UINT32)':
../../../../../src/emu/video/rgbvmx.h:42:73: warning: vec_lvsl is deprecated 
for little endian; use assignment for unaligned loads and stores [-Wdeprecated]
   const VECS8 temp = vec_perm(vec_lde(0, ), zero, vec_lvsl(0, ));
 ^
../../../../../src/emu/video/rgbvmx.h:42:74: note: use -flax-vector-conversions 
to permit conversions between vectors with differing element types or numbers 
of subparts
   const VECS8 temp = vec_perm(vec_lde(0, ), zero, vec_lvsl(0, ));
  ^
../../../../../src/emu/video/rgbvmx.h:42:74: error: cannot convert '__vector(4) 
unsigned int' to 'const VECS8 {aka const __vector(16) signed char}' in 
initialization
../../../../../src/emu/video/rgbvmx.h:43:11: error: cannot convert '__vector(8) 
short int' to 'rgbaint_t::VECS32 {aka __vector(4) int}' in assignment
   m_value = vec_mergeh((VECS16)zero, (VECS16)vec_mergeh((VECS8)zero, temp));
   ^
../../../../../src/emu/video/rgbvmx.h: In member function 'void 
rgbaint_t::set(rgb_t&)':
../../../../../src/emu/video/rgbvmx.h:55:81: warning: vec_lvsl is deprecated 
for little endian; use assignment for unaligned loads and stores [-Wdeprecated]
   const VECS8 temp = vec_perm(vec_lde(0, rgb.ptr()), zero, vec_lvsl(0, 
rgb.ptr()));

 ^
../../../../../src/emu/video/rgbvmx.h:55:82: error: cannot convert '__vector(4) 
unsigned int' to 'const VECS8 {aka const __vector(16) signed char}' in 
initialization
   const VECS8 temp = vec_perm(vec_lde(0, rgb.ptr()), zero, vec_lvsl(0, 
rgb.ptr()));

  ^
../../../../../src/emu/video/rgbvmx.h:56:11: error: cannot convert '__vector(8) 
short int' to 'rgbaint_t::VECS32 {aka __vector(4) int}' in assignment
   m_value = vec_mergeh((VECS16)zero, (VECS16)vec_mergeh((VECS8)zero, temp));
   ^
../../../../../src/emu/video/rgbvmx.h: In member function 'rgb_t 
rgbaint_t::to_rgba()':
../../../../../src/emu/video/rgbvmx.h:61:43: error: cannot convert '__vector(8) 
short int' to 'rgbaint_t::VECU32 {aka __vector(4) unsigned int}' in 
initialization
   VECU32 temp = vec_packs(m_value, m_value);
   ^
../../../../../src/emu/video/rgbvmx.h:62:8: error: cannot convert '__vector(16) 
unsigned char' to 'rgbaint_t::VECU32 {aka __vector(4) unsigned int}' in 
assignment
   temp = vec_packsu((VECS16)temp, (VECS16)temp);
^
[and so on]


Andreas

Bug#825437: AW: [Pkg-samba-maint] Bug#825437: talloc fails building on very clean system.

[Louis van Belle]

Hello Jelmer, 


Maybe i missed something. so bit more explained, after the basic install, i 
setup for the pbuilder environment. 

pbuilder setup from debian wiki with some extra packages installed with : 

apt-get install -y --no-install-recommends pbuilder devscripts dpkg-dev 
build-essential fakeroot debhelper dpkg-sig gnupg gnupg-agent dh-systemd

( im was missing dh-systemd somehere also which is also needed, ill recheck 
that. ) 



And i setup the pbuilder env. 

pbuilder create --configfile ${USERHOMEDIR}/pbuilder/pbuilderrc-jessie-amd64 



with this config file.

DISTRIBUTION="jessie"
COMPONENTS="main contrib non-free"
ARCHITECTURE="amd64"

MIRRORSITE=http://ftp.nl.debian.org/debian 
 
OTHERMIRROR=  "deb [trusted=yes] 
file:///home/builder/pbuilder/build-dep-debs ./"

BINDMOUNTS="/home/builder/pbuilder/build-dep-debs"
HOOKDIR="/home/builder/pbuilder/hookdir"
EXTRAPACKAGES="apt-utils"

BUILDPLACE=/home/builder/pbuilder/build-amd64
BASETGZ=/home/builder/pbuilder/base-${DISTRIBUTION}-amd64.tgz
BUILDRESULT=/home/builder/pbuilder/result-amd64
APTCACHE=/home/builder/pbuilder/apt-cache
APTCACHEHARDLINK="no"

USEPROC=yes
USEDEVPTS=yes
USENETWORK=no
USERUNSHM=yes
USEDEVFS=no

DEBBUILDOPTS="-sa"
# make debconf not interact with user
export DEBIAN_FRONTEND="noninteractive"

if [[ -n $SUDO_USER ]]; then
  BUILDRESULTUID=$SUDO_UID
  BUILDRESULTGID=$SUDO_GID
fi

then i run my build script. 

in short for every PACKAGE i run. 

(PACKAGE="libtalloc-dev libtevent-dev libtdb-dev libldb-dev libcmocka-dev 
libnss-wrapper libresolv-wrapper libuid-wrapper socket-wrapper samba" )



apt-get source $PACKAGE

pdebuild --configfile ${SET_BASEDIR}/pbuilderrc-jessie-amd64





So I was presuming pdebuild takes care of the dependecies in the chroot, which 
it does, but the build failed. 

I installed python-minimal in the host and not in the pbuilder env and pdebuild 
worked fine. 



when i follow the build depends.. 

Build-Depends: talloc_2.1.6-1.dsc
 debhelper (>= 9), docbook-xml, docbook-xsl, xsltproc, dh-exec, dh-python, 
libpopt-dev, python-dev (>= 2.6.6-3), python3-dev
so needs python-dev 



python-dev > python-defaults_2.7.11-1.dsc and i noticed. 

Build-Depends: debhelper (>= 8~), dpkg-dev (>= 1.17.11), python2.7 (>= 
2.7.11-2), lsb-release, python-all, debiandoc-sgml



python2.7_2.7.11-9.dsc

Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.17.11), quilt, autoconf, 
autotools-dev, lsb-release, sharutils, libreadline-dev, libtinfo-dev, 
libncursesw5-dev (>= 5.3), tk-dev, blt-dev (>= 2.4z), libssl-dev, zlib1g-dev, 
libbz2-dev, libexpat1-dev, libbluetooth-dev [linux-any], locales [!armel !avr32 
!hppa !ia64 !mipsel], libsqlite3-dev, libffi-dev (>= 3.0.5) [!or1k !avr32], 
libgpm2 [linux-any], mime-support, netbase, net-tools, bzip2, time, libdb-dev 
(<< 1:6.0), libgdbm-dev, python:any, help2man, xvfb, xauth
Build-Depends-Indep: python-sphinx


but i did see 

dh-python_2.20151103.dsc

Build-Depends: debhelper (>= 9), python3-minimal, libpython3-stdlib, 
libdpkg-perl, python-docutils


so i believe we are missing python-minimal somewhere in these packages. 



I guess dh-python because it does include python3-minimal but not 
python-minimal (2.7)



I can replay my setup if you want, its all scripted. 







-Oorspronkelijk bericht-
Afzender: Jelmer Vernooij 
Verstuurd: Donderdag 26 Mei 2016 23:51
Aan: Louis van Belle ; 825...@bugs.debian.org
Onderwerp: Re: [Pkg-samba-maint] Bug#825437: talloc fails building on very 
clean system.


tags 825437 +moreinfo
thanks

On Thu, May 26, 2016 at 11:18:14PM +0200, Louis van Belle wrote:
> Source: talloc
> Version: 2.1.6
> Severity: serious
> Tags: patch
> Justification: fails to build from source
> 
> Talloc fails builing when you install debian in expert mode and deselect all 
> defaults,
> installed ssh only. 

> 
> The build errors missing pyversions.
> 
> Installing pyton-minimal fixes the problem.

Have you installed the build dependencies of talloc? The build depends include
python-dev, which depends on python, which pre-depends on python-minimal.

Jelmer

Bug#825461: [Help] Re: Bug#825461: staden: FTBFS in testing

[Andreas Tille]

On Fri, May 27, 2016 at 10:05:03AM +0200, Jakub Wilk wrote:
> * Andreas Tille , 2016-05-27, 09:27:
> >>/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/Scrt1.o: In 
> >>function `_start':
> >>(.text+0x20): undefined reference to `main'
> >>collect2: error: ld returned 1 exit status
> 
> The command line that causes this is:
> 
> gcc -shared -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  
> -I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc 
> -I/build/staden-2.0.0+b10/./tk_utils -I/usr/include 
> -I"/usr/include/tcl8.6/tk-private/generic" 
> -I"/usr/include/tcl8.6/tk-private/unix" 
> -I"/usr/include/tcl8.6/tk-private/generic/ttk" 
> -I"/usr/include/tcl8.6/tcl-private/generic" 
> -I"/usr/include/tcl8.6/tcl-private/unix" 
> -I/build/staden-2.0.0+b10/./seq_utils   -I/build/staden-2.0.0+b10  
> -DSVN_VERSION="" -fPIC   -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  
> -I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc 
> -I/build/staden-2.0.0+b10/./tk_utils -I/usr/include 
> -I"/usr/include/tcl8.6/tk-private/generic" 
> -I"/usr/include/tcl8.6/tk-private/unix" 
> -I"/usr/include/tcl8.6/tk-private/generic/ttk" 
> -I"/usr/include/tcl8.6/tcl-private/generic" 
> -I"/usr/include/tcl8.6/tcl-private/unix" 
> -I/build/staden-2.0.0+b10/./seq_utils   -I/build/staden-2.0.0+b10  
> -DSVN_VERSION="" -fPIC  -L/build/staden-2.0.0+b10/lib -Wl,-z,relro 
> -Wl,--export-dynamic  -Wl,-rpath,/usr/lib/staden -o 
> /build/staden-2.0.0+b10/lib/libtk_utils.so  cli_arg.o tclXkeylist.o 
> tclXutil.o tcl_utils.o tcl_debug.o misc.o init.o text_output.o tkRaster.o 
> tkRasterBuiltIn.o sheet.o tkSheet.o tkSheet_common.o trace_print.o 
> postscript.o split.o tkTrace.o tkTraceComp.o tkTraceIO.o tkTraceDisp.o 
> capture.o canvas_box.o ruler_tick.o restriction_enzyme_map.o element_canvas.o 
> container.o container_ruler.o tcl_io_lib.o  -L/usr/lib/x86_64-linux-gnu 
> -lstaden-read -fPIE -pie -Wl,-z,relro -Wl,-z,now -lm -lpthread   -lcurl -lz 
> -L/usr/lib/x86_64-linux-gnu -ltk8.6 -L/usr/lib/x86_64-linux-gnu -ltcl8.6 
> -lX11 -lXss -lXext -lXft -lfontconfig -lfreetype -lfontconfig  -lpthread -ldl 
> -lz  -lpthread -lieee -lm  -lmisc  -lpng -lz
> 
> This is trying to build a shared library with -pie, which is not going to
> fly. -pie (and -fPIE) is only for executables.
> 
> Now, I don't see any mention of pie in debian/rules, or in the old build
> log, so I guess this flag must have come from a (broken) library.

Most probably this is due to libstaden-read-dev where I added

   export DEB_BUILD_MAINT_OPTIONS = hardening=+all

I'll revert this change and see what might happen ...

Thanks for the pointer

  Andreas.


-- 
http://fam-tille.de

Bug#825461: [Help] Re: Bug#825461: staden: FTBFS in testing

[Jakub Wilk]

* Jakub Wilk , 2016-05-27, 10:05:

gcc -shared -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  -I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc 
-I/build/staden-2.0.0+b10/./tk_utils -I/usr/include -I"/usr/include/tcl8.6/tk-private/generic" -I"/usr/include/tcl8.6/tk-private/unix" 
-I"/usr/include/tcl8.6/tk-private/generic/ttk" -I"/usr/include/tcl8.6/tcl-private/generic" -I"/usr/include/tcl8.6/tcl-private/unix" -I/build/staden-2.0.0+b10/./seq_utils 
  -I/build/staden-2.0.0+b10  -DSVN_VERSION="" -fPIC   -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  
-I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc -I/build/staden-2.0.0+b10/./tk_utils -I/usr/include -I"/usr/include/tcl8.6/tk-private/generic" 
-I"/usr/include/tcl8.6/tk-private/unix" -I"/usr/include/tcl8.6/tk-private/generic/ttk" -I"/usr/include/tcl8.6/tcl-private/generic" 
-I"/usr/include/tcl8.6/tcl-private/unix" -I/build/staden-2.0.0+b10/./seq_utils   -I/build/staden-2.0.0+b10  -DSVN_VERSION="" -fPIC  -L/build/staden-2.0.0+b10/lib -Wl,-z,relro 
-Wl,--export-dynamic  -Wl,-rpath,/usr/lib/staden -o /build/staden-2.0.0+b10/lib/libtk_utils.so  cli_arg.o tclXkeylist.o tclXutil.o tcl_utils.o tcl_debug.o misc.o init.o text_output.o tkRaster.o 
tkRasterBuiltIn.o sheet.o tkSheet.o tkSheet_common.o trace_print.o postscript.o split.o tkTrace.o tkTraceComp.o tkTraceIO.o tkTraceDisp.o capture.o canvas_box.o ruler_tick.o restriction_enzyme_map.o 
element_canvas.o container.o container_ruler.o tcl_io_lib.o  -L/usr/lib/x86_64-linux-gnu -lstaden-read -fPIE -pie -Wl,-z,relro -Wl,-z,now -lm -lpthread   -lcurl -lz -L/usr/lib/x86_64-linux-gnu 
-ltk8.6 -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -lX11 -lXss -lXext -lXft -lfontconfig -lfreetype -lfontconfig  -lpthread -ldl -lz  -lpthread -lieee -lm  -lmisc  -lpng -lz

This is trying to build a shared library with -pie, which is not going 
to fly. -pie (and -fPIE) is only for executables.


Now, I don't see any mention of pie in debian/rules, or in the old 
build log, so I guess this flag must have come from a (broken) 
library.


If you grep for -pie in config.log you get this:

IO_LIB_LDFLAGS='-L/usr/lib/i386-linux-gnu -lstaden-read -fPIE -pie -Wl,-z,relro 
-Wl,-z,now -lm -lpthread   -lcurl -lz'

which was apparently generated by:

$ io_lib-config --libs
-L/usr/lib/i386-linux-gnu -lstaden-read -fPIE -pie -Wl,-z,relro -Wl,-z,now -lm 
-lpthread   -lcurl -lz

This will have to be fixed in libstaden-read-dev.

--
Jakub Wilk

Processed: Re: Bug#819714

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #819714 {Done: Gianfranco Costamagna } [src:vtk6] 
nifti2dicom: FTBFS:  No rule to make target 
'/usr/lib/x86_64-linux-gnu/libproj.so'
Bug reopened
Ignoring request to alter fixed versions of bug #819714 to the same values 
previously set

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

Bug#819714:

[Gianfranco Costamagna]

control: reopen -1

Hi, lets keep it open, sorry for closing in advance!

>If this is a bug in vtk6, then I'm reassigning it to vtk6.
>Please feel free to forcemerge with the real bug if there is one
>already reported.
>
>The "affects" helps people like me who find FTBFS bugs to avoid filing
>duplicate bugs.


thanks for that!
>I'm keeping the bug closed for now, but in this case I've just checked
>that nifti2dicom FTBFS in stretch, which is something should never
>happen (packages in testing should be buildable in testing too).
>
>Can you comment on the status of the transition?


I did some NMUs/Uploads to help the transition move forward, and I think 
reverse-dependencies
are mostly in place, but in the meanwhile gdcm got an RC bug (from me), because 
build-dependencies
aren't installable anymore.

So, while vtk6 folks prepares the transition, keeping this one open is the best 
solution.
(and closing in advance was a wrong choice, but I was mostly sure the 
transition was ready at that
point).

Thanks!

Gianfranco

Bug#825461: [Help] Re: Bug#825461: staden: FTBFS in testing

[Andreas Tille]

Hi Gianfranco,

On Fri, May 27, 2016 at 07:53:45AM +, Gianfranco Costamagna wrote:
> Hi, some quick googling found some possible solutions
> https://www.google.it/search?client=ubuntu=fs=%22Scrt1.o%3A+In+function+`_start%27%3A%22=utf-8=utf-8_rd=cr=5ftHV7_JI8fA8geO-LmABQ
> 
> I remember having that issue on ettercap some years ago, this is how I fixed 
> it [1], but probably it was a little different issue.
> 
> 
> [1] 
> https://github.com/Ettercap/ettercap/commit/cf90ed99361b266e4d0d8a24f61fe5ffa82fc323

Hmmm, both is not really enlightening my poor brain - but thanks for the
pointers any way.
 
> however, it seems to be related to some build flags missing or added (in a 
> library used or in that tool itself)

Its probably some other Build-Depends that changed since staden
packaging itself is rather static.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#825461: [Help] Re: Bug#825461: staden: FTBFS in testing

[Jakub Wilk]

* Andreas Tille , 2016-05-27, 09:27:

/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/Scrt1.o: In function 
`_start':
(.text+0x20): undefined reference to `main'
collect2: error: ld returned 1 exit status


The command line that causes this is:

gcc -shared -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  -I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc 
-I/build/staden-2.0.0+b10/./tk_utils -I/usr/include -I"/usr/include/tcl8.6/tk-private/generic" -I"/usr/include/tcl8.6/tk-private/unix" 
-I"/usr/include/tcl8.6/tk-private/generic/ttk" -I"/usr/include/tcl8.6/tcl-private/generic" -I"/usr/include/tcl8.6/tcl-private/unix" -I/build/staden-2.0.0+b10/./seq_utils 
  -I/build/staden-2.0.0+b10  -DSVN_VERSION="" -fPIC   -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  
-I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc -I/build/staden-2.0.0+b10/./tk_utils -I/usr/include -I"/usr/include/tcl8.6/tk-private/generic" 
-I"/usr/include/tcl8.6/tk-private/unix" -I"/usr/include/tcl8.6/tk-private/generic/ttk" -I"/usr/include/tcl8.6/tcl-private/generic" 
-I"/usr/include/tcl8.6/tcl-private/unix" -I/build/staden-2.0.0+b10/./seq_utils   -I/build/staden-2.0.0+b10  -DSVN_VERSION="" -fPIC  -L/build/staden-2.0.0+b10/lib -Wl,-z,relro 
-Wl,--export-dynamic  -Wl,-rpath,/usr/lib/staden -o /build/staden-2.0.0+b10/lib/libtk_utils.so  cli_arg.o tclXkeylist.o tclXutil.o tcl_utils.o tcl_debug.o misc.o init.o text_output.o tkRaster.o 
tkRasterBuiltIn.o sheet.o tkSheet.o tkSheet_common.o trace_print.o postscript.o split.o tkTrace.o tkTraceComp.o tkTraceIO.o tkTraceDisp.o capture.o canvas_box.o ruler_tick.o restriction_enzyme_map.o 
element_canvas.o container.o container_ruler.o tcl_io_lib.o  -L/usr/lib/x86_64-linux-gnu -lstaden-read -fPIE -pie -Wl,-z,relro -Wl,-z,now -lm -lpthread   -lcurl -lz -L/usr/lib/x86_64-linux-gnu 
-ltk8.6 -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -lX11 -lXss -lXext -lXft -lfontconfig -lfreetype -lfontconfig  -lpthread -ldl -lz  -lpthread -lieee -lm  -lmisc  -lpng -lz

This is trying to build a shared library with -pie, which is not going 
to fly. -pie (and -fPIE) is only for executables.


Now, I don't see any mention of pie in debian/rules, or in the old build 
log, so I guess this flag must have come from a (broken) library.


--
Jakub Wilk

Bug#825471: libunistring0: soname change without package name change

[Stephen Kitt]

On Fri, May 27, 2016 at 07:15:48AM +0200, Andreas Metzler wrote:
> 0.9.6-1.1 features a soname bump from libunistring.so.0 to
> libunistring.so.2, without changing the package name and making a
> library transition. This breaks all reverse dependencies, e.g.:

I'm preparing an NMU to revert to 0.9.3 (so the version will end up
being 0.9.6+really0.9.3 since I need to re-upload an orig tarball).

Manuel, if you want to re-do the transition, you can simply use
version 0.9.6+really0.9.6, until 0.9.7 is released.

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#825461: [Help] Re: Bug#825461: staden: FTBFS in testing

[Gianfranco Costamagna]

Hi, some quick googling found some possible solutions
https://www.google.it/search?client=ubuntu=fs=%22Scrt1.o%3A+In+function+`_start%27%3A%22=utf-8=utf-8_rd=cr=5ftHV7_JI8fA8geO-LmABQ

I remember having that issue on ettercap some years ago, this is how I fixed it 
[1], but probably it was a little different issue.


[1] 
https://github.com/Ettercap/ettercap/commit/cf90ed99361b266e4d0d8a24f61fe5ffa82fc323


however, it seems to be related to some build flags missing or added (in a 
library used or in that tool itself)


HTH

Gianfranco
Il Venerdì 27 Maggio 2016 9:27, Andreas Tille  ha scritto:



Hi,

On Fri, May 27, 2016 at 02:29:28AM +0200, Santiago Vila wrote:
> --
> capture.o: In function `tcl_capture':
> /<>/staden-2.0.0+b10/tk_utils/capture.c:31: warning: the use of 
> `tmpnam' is dangerous, better use `mkstemp'

I've fixed this in Git, but this does not help. :-(

> /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/Scrt1.o: In 
> function `_start':
> (.text+0x20): undefined reference to `main'
> collect2: error: ld returned 1 exit status

Any help would be welcome

 Andreas.


-- 
http://fam-tille.de

Bug#825461: [Help] Re: Bug#825461: staden: FTBFS in testing

[Andreas Tille]

Hi,

On Fri, May 27, 2016 at 02:29:28AM +0200, Santiago Vila wrote:
> --
> capture.o: In function `tcl_capture':
> /<>/staden-2.0.0+b10/tk_utils/capture.c:31: warning: the use of 
> `tmpnam' is dangerous, better use `mkstemp'

I've fixed this in Git, but this does not help. :-(

> /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/Scrt1.o: In 
> function `_start':
> (.text+0x20): undefined reference to `main'
> collect2: error: ld returned 1 exit status

Any help would be welcome

 Andreas.


-- 
http://fam-tille.de

Bug#825307: gdcm: build-dependencies not installable

[Mathieu Malaterre]

Control: tags -1 fixed-upstream

While not 100% perfect, one can pull two patches from upstream:
4f793f6005c794de633d01e42e00d37f80340fac &
0511b1d6d356a1c5d1f4e22cd5bb862ef233a332 to have this issue fixed.

The behavior is not fantastic, but at least GDCM do compile against
OPJ 2.1.0, and the change should be unnoticeable by most users.

Processed: gdcm: build-dependencies not installable

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #825307 [src:gdcm] gdcm: build-dependencies not installable
Added tag(s) fixed-upstream.

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

Processed: severity of 825473 is critical, severity of 825471 is critical, severity of 825472 is critical ...

[Debian Bug Tracking System]

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

> severity 825473 critical
Bug #825473 [libunistring0] libunistring0: Upstream had a SONAME filename 
change, but libunitstring0 package name didn't change.
Severity set to 'critical' from 'important'
> severity 825471 critical
Bug #825471 [libunistring0] libunistring0: soname change without package name 
change
Severity set to 'critical' from 'serious'
> severity 825472 critical
Bug #825472 [libunistring0] libunistring0: soname bump without name change
Severity set to 'critical' from 'grave'
> merge 825472 825474 825473 825471
Bug #825472 [libunistring0] libunistring0: soname bump without name change
Bug #825471 [libunistring0] libunistring0: soname change without package name 
change
Bug #825473 [libunistring0] libunistring0: Upstream had a SONAME filename 
change, but libunitstring0 package name didn't change.
Bug #825474 [libunistring0] libunistring0: upgrading to 0.9.6-1.1 leads to a 
problem with shared libraries
Merged 825471 825472 825473 825474
> thanks
Stopping processing here.

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

Processed (with 1 error): reopening 825473, merging 825472 825474 825473 825471

[Debian Bug Tracking System]

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

> reopen 825473
Bug #825473 {Done: Diane Trout } [libunistring0] libunistring0: 
Upstream had a SONAME filename change, but libunitstring0 package name didn't 
change.
Bug reopened
Ignoring request to alter fixed versions of bug #825473 to the same values 
previously set
> merge 825472 825474 825473 825471
Bug #825472 [libunistring0] libunistring0: soname bump without name change
Unable to merge bugs because:
severity of #825474 is 'critical' not 'grave'
severity of #825471 is 'serious' not 'grave'
severity of #825473 is 'important' not 'grave'
Failed to merge 825472: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: severity of 824780 is normal

[Debian Bug Tracking System]

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

> severity 824780 normal
Bug #824780 [iceowl-l10n-is] iceowl-l10n-is: should recommend hunspell-is (not 
bogus myspell-is)
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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