Processed: bts

[Debian Bug Tracking System]

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

> close 827378 20160615-2
Bug #827378 [open-infrastructure-container-tools] 
open-infrastructure-container-tools: missing Depends: lsb-release
There is no source info for the package 'open-infrastructure-container-tools' 
at version '20160615-2' with architecture ''
Unable to make a source version for version '20160615-2'
Marked as fixed in versions 20160615-2.
Bug #827378 [open-infrastructure-container-tools] 
open-infrastructure-container-tools: missing Depends: lsb-release
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#827332: marked as done (FTBFS: uses Qt5's private headers)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jun 2016 04:51:25 +
with message-id 
and subject line Bug#827332: fixed in hime 0.9.10+git20150916+dfsg1-3
has caused the Debian Bug report #827332,
regarding FTBFS: uses Qt5's private headers
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.)


-- 
827332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hime
Version: 0.9.10+git20150916+dfsg1-2
Severity: serious

Hi! hime fails to build from source due to changes in Qt5's private headers.
We Qt maintainers can guarantee private headers' API/ABI stability, so I'm
afraid the only possible fix here is to fix hime's code.

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: hime
Source-Version: 0.9.10+git20150916+dfsg1-3

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

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated hime package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Jun 2016 12:08:09 +0800
Source: hime
Binary: hime hime-data hime-tables libhime hime-gtk2-immodule 
hime-gtk3-immodule hime-qt4-immodule hime-qt5-immodule hime-anthy hime-chewing
Architecture: source amd64 all
Version: 0.9.10+git20150916+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: IME Packaging Team 
Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 hime   - GTK+ based input method for Chinese users
 hime-anthy - support library to use Anthy in HIME
 hime-chewing - support library to use Chewing in HIME
 hime-data  - icons, locales and scripts for HIME
 hime-gtk2-immodule - GTK2 input method module with HIME as backend
 hime-gtk3-immodule - GTK3 input method module with HIME as backend
 hime-qt4-immodule - Qt4 input method module with HIME as backend
 hime-qt5-immodule - Qt5 input method module with HIME as backend
 hime-tables - input method tables for HIME
 libhime- library for HIME
Closes: 827332
Changes:
 hime (0.9.10+git20150916+dfsg1-3) unstable; urgency=medium
 .
   * Fix FTBFS on Qt 5.6.1. (Closes: #827332)
   * Bump Standards-Version to 3.9.8.
   * Update Vcs-* fields.
   * Remove im-switch config.
Checksums-Sha1:
 71696a4871bed3ed83aed56d8590d133a9ba037d 2776 
hime_0.9.10+git20150916+dfsg1-3.dsc
 dcf8c059160b6afb1a4042ccbb9466e2d93c35d6 10092 
hime_0.9.10+git20150916+dfsg1-3.debian.tar.xz
 38fc041d3b0640f6da4c71cf3a986ccf1db7299d 26240 
hime-anthy-dbgsym_0.9.10+git20150916+dfsg1-3_amd64.deb
 75a3071457e69753d863f0de1a6705527a739798 26446 
hime-anthy_0.9.10+git20150916+dfsg1-3_amd64.deb
 22df8642cfb205fea68b1307dcd04b34d452fe0d 35736 
hime-chewing-dbgsym_0.9.10+git20150916+dfsg1-3_amd64.deb
 dc0b5d15fc03a42ebf7d812625bf80f9fc15a58a 21174 
hime-chewing_0.9.10+git20150916+dfsg1-3_amd64.deb
 0c0ac96be034bce8b3aa3be2dc81e2e279422e88 489308 
hime-data_0.9.10+git20150916+dfsg1-3_all.deb
 27089a756340763d98532989af0ee6a6eca4704c 1009134 
hime-dbgsym_0.9.10+git20150916+dfsg1-3_amd64.deb
 d0b975119bfb3a5dca68de7342412f1f5d4d33dc 18212 
hime-gtk2-immodule-dbgsym_0.9.10+git20150916+dfsg1-3_amd64.deb
 a5c84824988d12bceba7b1750e3a02e0de4b5e3f 16802 
hime-gtk2-immodule_0.9.10+git20150916+dfsg1-3_amd64.deb
 f3ae0d871b75eefaa9f16f974372fde9457bc61f 15736 
hime-gtk3-immodule-dbgsym_0.9.10+git20150916+dfsg1-3_amd64.deb
 e602ea2958181f416319a50acf2b50b23c790349 16802 
hime-gtk3-immodule_0.9.10+git20150916+dfsg1-3_amd64.deb
 1372dae425bb97e42d9e32c010f546f6df7a7fa0 216332 

Bug#808697: marked as done (kadu: Uses qtquick1 which is going away)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jun 2016 04:21:37 +
with message-id 
and subject line Bug#808697: fixed in kadu 3.0-1.1
has caused the Debian Bug report #808697,
regarding kadu: Uses qtquick1 which is going away
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.)


-- 
808697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kadu
Version: 2.1-2
Severity: important

Dear Maintainer,

QtQuick1 is going away real soon. Please migrate to QtQuick2. If you
need help, feel free to ask, including providing guidance on how to use
the current qtquick1 thing in kadu.

/Sune

-- 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.2.0-1-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)
--- End Message ---
--- Begin Message ---
Source: kadu
Source-Version: 3.0-1.1

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

Debian distribution maintenance software
pp.
Mateusz Łukasik  (supplier of updated kadu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Jun 2016 20:12:26 +0200
Source: kadu
Binary: kadu libkadu kadu-common kadu-dev kadu-themes
Architecture: source
Version: 3.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Patryk Cisek 
Changed-By: Mateusz Łukasik 
Description:
 kadu   - Gadu-Gadu/XMPP client for X11
 kadu-common - Gadu-Gadu/XMPP client for X11
 kadu-dev   - Development files needed to compile plugins for kadu
 kadu-themes - Additional icons and emoticons for Kadu
 libkadu- Gadu-Gadu/XMPP client for X11
Closes: 784472 808697 821275
Changes:
 kadu (3.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop all QT4 and no needed depends. (Closes: #784472, #808697)
   * Update description for QT5.
   * Use secured links for VCS.
   * Enable parallel building. (Closes: #821275)
   * Bump Standards-Version to 3.9.8.
   * Fix watch file.
Checksums-Sha1:
 ae3691f484ad01ac84187dedfc4ac5e5b59ad2ae 2731 kadu_3.0-1.1.dsc
 fb8a6e458206f0e1268c6edd46074d5544f7c294 19008 kadu_3.0-1.1.debian.tar.xz
Checksums-Sha256:
 cba4648e1df880aab2489a53e3e09a1989d13b06af0df95770a7687c85af3855 2731 
kadu_3.0-1.1.dsc
 fe9e2e61e8196ab76480dc26c5d814e2838b5e3a027a8d0b2bb0d76050cc13af 19008 
kadu_3.0-1.1.debian.tar.xz
Files:
 3429592a5236ec07b617a3ebc9ae0d6e 2731 net optional kadu_3.0-1.1.dsc
 1154b74f58025aa0fa796de2616e2c33 19008 net optional kadu_3.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJXYhDFAAoJECw7Q2/qxoEBwtQH/RSwak7o0WQ/wVVf3P4VzZFd
lM+5mYW3+25AZTPUGQ7DHVDcY1NiH7bXwkvk6Cm5bjOBFE/ATGQ3qP7diQsZAVax
K8OkLsTyGDI8bJmY9bx6wu/e6rNX22RXUNGFvLRofjWGhXoQy0zeJrNawkk7SiI0
51QE+Twrf+WMCLJHZLA3QUnhxt8u8GgJQsujAqF7lOQgFtQrfKkamrfssebtpqmo
GM86x8iauidwk4C5bRFmMxSC0Xe9fqdJKpOuY25R+nEUSao8+JodeOc4co54jnNG
Fslamlt6XNilyF9oKZXRALOfNfMJvHgSqjOO+XVtAhiPMyNJ7stzeySc98l5EyM=
=19HG
-END PGP SIGNATURE End Message ---

Bug#825568: marked as done (spacefm-gtk3: purging deletes conffile /etc/spacefm/spacefm.conf owned by spacefm-common)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jun 2016 04:23:08 +
with message-id 
and subject line Bug#825568: fixed in spacefm 1.0.5-2
has caused the Debian Bug report #825568,
regarding spacefm-gtk3: purging deletes conffile /etc/spacefm/spacefm.conf 
owned by spacefm-common
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.)


-- 
825568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: spacefm
Source-Version: 1.0.5-2

We believe that the bug you reported is fixed in the latest version of
spacefm, 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.
Mateusz Łukasik  (supplier of updated spacefm 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, 10 Jun 2016 10:42:45 +0200
Source: spacefm
Binary: spacefm spacefm-common spacefm-gtk3
Architecture: source
Version: 1.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Mateusz Łukasik 
Changed-By: Mateusz Łukasik 
Description:
 spacefm- Multi-panel tabbed file manager - GTK2 version
 spacefm-common - Multi-panel tabbed file manager - common files
 spacefm-gtk3 - Multi-panel tabbed file manager - GTK3 version
Closes: 825568
Changes:
 spacefm (1.0.5-2) unstable; urgency=medium
 .
   * debian/control:
 + Drop libdbus-1-dev from B-D and move dbus from Depends to Suggests.
 + Bump to Standards-Version to 3.9.8.
 + Add Breaks and Replaces for spacefm-common (<< 1.0.5-2).
   * debian/watch: Bump to version 4.
   * debian/*.install: move /etc/spacefm/spacefm.conf from spacefm-common to
 spacefm{,-gtk3}. (Closes: #825568)
   * Cherry-pick fixes from upstream next git branch:
 + cf19fb3: Rename dlg canonicalize Copy Target/Link Target target when
   possible
 + 9ca8616: [installer] fix mktemp template and error handling for busybox
 + 83332d0: [GTK2] fix black background dir load regression
 + d75271e: [GTK2] fix black background dir load regression
 + 6ee12b2: [GTK3.20] fix theme parse warnings re close btn css
Checksums-Sha1:
 e8cef051a62b0357ea93b59cda200ead6c137a82 1836 spacefm_1.0.5-2.dsc
 04260c05e5f56467bb72c4b4070f8f7b122b35b4 17364 spacefm_1.0.5-2.debian.tar.xz
Checksums-Sha256:
 a14b1c02a537876bda1bedf040f4eff90e007a465c355f54e3e491ee81917cc3 1836 
spacefm_1.0.5-2.dsc
 81d5227a2d167b8086d65608b7db0b3f6ecd0c83ce7efaf77978b34f09818cba 17364 
spacefm_1.0.5-2.debian.tar.xz
Files:
 ab1e2a69414d184e0b9a31c193dea4dd 1836 utils optional spacefm_1.0.5-2.dsc
 bfe4686c44c3c4279862ffb642d2ce3e 17364 utils optional 
spacefm_1.0.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJXYhspAAoJECw7Q2/qxoEBZboH+QGC3vpLMuiv1JM8O3p5YzTb
AaxnOotiH+bdZcZvqvoVBpD97IVJFI4VFa8kYIBfvBlCPQdvuxA+JkLnEbrwdWdp
rVoVyuhHTZvTMFTZC8ZzwdoOxSIUjM8cPLFH0Qsjo9JGgw6a9sc31H+eFU2mVKgS
iAEoCTskHX6csScMj0dYo7ri74aelFR+fHk/EZw+ee+XBrZ54Q7Ji/tsefVNJ901
d0AJ1pzeAnT6lH/C+u9vzDcHJRAsHDA9PHpwDcD2gmauxUtEg8b1/eijrdbUeaSi
PJy891u3jAPM4rnsXBKm1WI4KKexAe10IC4TA5By8t5C2y9oBIwF5pGBmx/ti20=
=maWs
-END PGP SIGNATURE End Message ---

Bug#827403: marked as done (fails to run as root------------------------------------------Dear someone)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jun 2016 00:19:01 +
with message-id <20160616001851.ga6...@chase.mapreri.org>
and subject line Re: Bug#827403: fails to run as root
has caused the Debian Bug report #827403,
regarding fails to run as root--Dear 
someone
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.)


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

i did

ln -s /opt/viber/Viber /usr/bin/viber
ls -al /opt/viber/Viber
ls -al /usr/bin/viber

when i hit viber in console
i got the below output

# viber 
This application failed to start because it could not find or load the Qt 
platform plugin "xcb".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, 
wayland-egl, wayland, xcb.

Reinstalling the application may fix this problem.
Aborted

i've installed the xcb package i have the same results

---

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 viber depends on:
ii  libasound2  1.0.28-1
ii  libcurl37.38.0-4+deb8u3
ii  libnss3 2:3.17.2-1.1+deb8u2
ii  libpulse0   5.0-13
ii  libssl1.0.0 1.0.1t-1+deb8u2
ii  libxcomposite1  1:0.4.4-1
ii  libxcursor1 1:1.1.14-1+b1
ii  libxdamage1 1:1.1.4-2+b1
ii  libxss1 1:1.2.2-1

viber recommends no packages.

viber suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

I can't even figure how such an email could be possible...

But anywawy, package 'viber' is not in debian, so we're not responsible
for it and its bugs.
Please send your bugs to your provider of the package in question.


On Thu, Jun 16, 2016 at 12:09:12AM +, unknown wrote:
> --
> Dear someone
> Reply-To: stargazer , 827...@bugs.debian.org
> Resent-From: stargazer 
> Resent-To: debian-bugs-d...@lists.debian.org
> Resent-CC: bisso...@gmail.com, unknown-pack...@qa.debian.org
> X-Loop: ow...@bugs.debian.org
> Resent-Date: Wed, 15 Jun 2016 18:30:01 +
> Resent-Message-ID: 
> Resent-Sender: ow...@bugs.debian.org
> X-Debian-PR-Message: report 827403
> X-Debian-PR-Package: viber
> X-Debian-PR-Keywords: 
> Received: via spool by sub...@bugs.debian.org id=B.146601526426805
>   (code B); Wed, 15 Jun 2016 18:30:01 +
> Received: (at submit) by bugs.debian.org; 15 Jun 2016 18:27:44 +
> X-Spam-Checker-Version: SpamAssassin 3.4.0-bugs.debian.org_2005_01_02
>   (2014-02-07) on buxtehude.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, score=-9.0 required=4.0 
> tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
>   
> FOURLA,FREEMAIL_FROM,HAS_PACKAGE,HELO_MISC_IP,NML_ADSP_CUSTOM_MED,RCVD_IN_PBL,
>   RDNS_DYNAMIC,SPF_SOFTFAIL,XMAILER_REPORTBUG,X_DEBBUGS_CC autolearn=ham
>   autolearn_force=no version=3.4.0-bugs.debian.org_2005_01_02
> X-Spam-Bayes: score:0. Tokens: new, 12; hammy, 148; neutral, 70; spammy,
>   2. spammytokens:1.000-7--viber, 1.000-5--Viber 
> hammytokens:0.000-+--systemd,
>   0.000-+--H*x:6.6.3, 0.000-+--H*UA:6.6.3, 0.000-+--31604amd64,
>   0.000-+--3.16.0-4-amd64
> Received: from adsl-68.176.58.184.tellas.gr ([176.58.184.68] helo=[127.0.1.1])
>   by buxtehude.debian.org with esmtp (Exim 4.84_2)
>   (envelope-from )
>   id 1bDFXT-0006xk-UR
>   for sub...@bugs.debian.org; Wed, 15 Jun 2016 18:27:44 +
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> From: stargazer 
> To: Debian Bug Tracking System 
> Message-ID: <20160615182733.1669.78029.reportbug@debian>
> X-Mailer: reportbug 6.6.3
> Date: Wed, 15 Jun 2016 14:27:33 -0400
> Delivered-To: sub...@bugs.debian.org
> 
> Package: viber
> Version: 6.0.1.5
> Severity: serious
> Justification: fails to build from source
> 
> i did
> 
> ln -s /opt/viber/Viber /usr/bin/viber
> ls -al /opt/viber/Viber
> ls -al /usr/bin/viber
> 
> when i hit viber in console
> i got 

Bug#827421: phantomjs: FTBFS: Project ERROR: This program can only be compiled with Qt 5.5.x.

[Chris Lamb]

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

Dear Maintainer,

phantomjs fails to build from source in unstable/amd64:

  [..]

  Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
  Setting up libpng-dev:amd64 (1.6.22-1) ...
  Setting up libfreetype6-dev (2.6.3-3+b1) ...
  Setting up libjpeg62-turbo:amd64 (1:1.5.0-1) ...
  Setting up libjpeg62-turbo-dev:amd64 (1:1.5.0-1) ...
  Setting up libjpeg-dev (1:1.5.0-1) ...
  Setting up libsqlite3-dev:amd64 (3.13.0-1) ...
  Setting up libssl-dev:amd64 (1.0.2h-1) ...
  Setting up ucf (3.0036) ...
  Setting up fonts-dejavu-core (2.35-1) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.4) ...
  Setting up libexpat1-dev:amd64 (2.1.1-3) ...
  Setting up pkg-config (0.29-4) ...
  Setting up libfontconfig1-dev:amd64 (2.11.0-6.4) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libxcb1:amd64 (1.11.1-1) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up xorg-sgml-doctools (1:1.11-1) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libxau-dev:amd64 (1:1.0.8-1) ...
  Setting up libxdmcp-dev:amd64 (1:1.1.2-1.1) ...
  Setting up x11proto-input-dev (2.3.2-1) ...
  Setting up x11proto-kb-dev (1.0.7-1) ...
  Setting up xtrans-dev (1.3.5-1) ...
  Setting up libpthread-stubs0-dev:amd64 (0.3-4) ...
  Setting up libxcb1-dev:amd64 (1.11.1-1) ...
  Setting up libx11-dev:amd64 (2:1.6.3-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up x11proto-xext-dev (7.3.0-1) ...
  Setting up libxext-dev:amd64 (2:1.3.3-1) ...
  Setting up libdrm2:amd64 (2.4.68-1) ...
  Setting up libglapi-mesa:amd64 (11.2.2-1) ...
  Setting up libx11-xcb1:amd64 (2:1.6.3-1) ...
  Setting up libxcb-dri2-0:amd64 (1.11.1-1) ...
  Setting up libxcb-dri3-0:amd64 (1.11.1-1) ...
  Setting up libxcb-glx0:amd64 (1.11.1-1) ...
  Setting up libxcb-present0:amd64 (1.11.1-1) ...
  Setting up libxcb-randr0:amd64 (1.11.1-1) ...
  Setting up libxcb-render0:amd64 (1.11.1-1) ...
  Setting up libxcb-shape0:amd64 (1.11.1-1) ...
  Setting up libxcb-sync1:amd64 (1.11.1-1) ...
  Setting up libxcb-xfixes0:amd64 (1.11.1-1) ...
  Setting up libxfixes3:amd64 (1:5.0.1-2+b2) ...
  Setting up libxdamage1:amd64 (1:1.1.4-2+b1) ...
  Setting up libxshmfence1:amd64 (1.2-1) ...
  Setting up libxxf86vm1:amd64 (1:1.1.4-1) ...
  Setting up libgl1-mesa-glx:amd64 (11.2.2-1) ...
  Setting up libgstreamer1.0-0:amd64 (1.8.2-1) ...
  Setcap worked! gst-ptp-helper is not suid!
  Setting up liborc-0.4-0:amd64 (1:0.4.25-1) ...
  Setting up iso-codes (3.68-1) ...
  Setting up libgstreamer-plugins-base1.0-0:amd64 (1.8.2-1) ...
  Setting up libpcre16-3:amd64 (2:8.38-3.1) ...
  Setting up libqt5core5a:amd64 (5.6.1+dfsg-2) ...
  Setting up fontconfig (2.11.0-6.4) ...
  Regenerating fonts cache... done.
  Setting up libglew1.13:amd64 (1.13.0-2) ...
  Setting up libglu1-mesa:amd64 (9.0.0-2.1) ...
  Setting up mesa-utils (8.3.0-1) ...
  Setting up libwayland-client0:amd64 (1.11.0-2) ...
  Setting up libwayland-server0:amd64 (1.11.0-2) ...
  Setting up libgbm1:amd64 (11.2.2-1) ...
  Setting up libegl1-mesa:amd64 (11.2.2-1) ...
  Setting up libgraphite2-3:amd64 (1.3.8-1) ...
  Setting up libharfbuzz0b:amd64 (1.2.6-2) ...
  Setting up x11-common (1:7.7+15) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libevdev2:amd64 (1.5.1+dfsg-1) ...
  Setting up libmtdev1:amd64 (1.1.5-1) ...
  Setting up libgudev-1.0-0:amd64 (230-3) ...
  Setting up libwacom-common (0.19-1) ...
  Setting up libwacom2:amd64 (0.19-1) ...
  Setting up libinput-bin (1.3.1-1) ...
  Setting up libinput10:amd64 (1.3.1-1) ...
  Setting up libdbus-1-3:amd64 (1.10.8-1) ...
  Setting up libqt5dbus5:amd64 (5.6.1+dfsg-2) ...
  Setting up libproxy1v5:amd64 (0.4.11-5) ...
  Setting up libqt5network5:amd64 (5.6.1+dfsg-2) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxcb-icccm4:amd64 (0.4.1-1) ...
  Setting up libxcb-shm0:amd64 (1.11.1-1) ...
  Setting up libxcb-util0:amd64 (0.3.8-3) ...
  Setting up libxcb-image0:amd64 (0.4.0-1) ...
  Setting up libxcb-keysyms1:amd64 (0.4.0-1) ...
  Setting up libxcb-render-util0:amd64 (0.3.9-1) ...
  Setting up libxcb-xinerama0:amd64 (1.11.1-1) ...
  Setting up libxcb-xkb1:amd64 (1.11.1-1) ...
  Setting up libxi6:amd64 (2:1.7.6-1) ...
  Setting up xkb-data (2.17-1) ...
  Setting up libxkbcommon0:amd64 (0.5.0-1) ...
  Setting up libxkbcommon-x11-0:amd64 (0.5.0-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libqt5gui5:amd64 (5.6.1+dfsg-2) ...
  Setting up 

Bug#789038: jitsi: Unable to install on sid/unstable

[Ingo Bauersachs]

On Tue, 19 Jan 2016 04:05:36 +0100 Kurt Roeckx  wrote:
> The problem is getting a version from upstream that meets the DFSG
> requirements.  And usptream doesn't seem to care about it anymore.

This relates to the javax.sip headers and has been solved. We (I) do
have interest to get this into Debian, but I don't have the resources.

Ingo

Bug#827302: marked as done (v4l-utils: FTBFS: jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src')

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 22:48:36 +
with message-id 
and subject line Bug#827302: fixed in v4l-utils 1.10.1-1
has caused the Debian Bug report #827302,
regarding v4l-utils: FTBFS: jpeg_memsrcdest.h:6:1: error: conflicting types for 
'jpeg_mem_src'
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.)


-- 
827302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: v4l-utils
Version: 1.10.0-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,

v4l-utils fails to build from source in unstable/amd64:

  [..]

  checking for inttypes.h... yes
  checking for stdint.h... yes
  checking for unistd.h... yes
  checking minix/config.h usability... no
  checking minix/config.h presence... no
  checking for minix/config.h... no
  checking whether it is safe to define __EXTENSIONS__... yes
  checking for a BSD-compatible install... /usr/bin/install -c
  checking whether build environment is sane... yes
  checking for a thread-safe mkdir -p... /bin/mkdir -p
  checking for gawk... no
  checking for mawk... mawk
  checking whether make sets $(MAKE)... yes
  checking for style of include used by make... GNU
  checking whether make supports nested variables... yes
  checking dependency style of gcc... none
  checking whether to enable maintainer-specific portions of Makefiles... no
  checking whether make supports nested variables... (cached) yes
  checking for g++... g++
  checking whether we are using the GNU C++ compiler... yes
  checking whether g++ accepts -g... yes
  checking dependency style of g++... none
  checking for gcc option to accept ISO C99... none needed
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking how to print strings... printf
  checking for a sed that does not truncate output... /bin/sed
  checking for fgrep... /bin/grep -F
  checking for ld used by gcc... /usr/bin/ld
  checking if the linker (/usr/bin/ld) is GNU ld... yes
  checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
  checking the name lister (/usr/bin/nm -B) interface... BSD nm
  checking whether ln -s works... yes
  checking the maximum length of command line arguments... 1572864
  checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
  checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
  checking for /usr/bin/ld option to reload object files... -r
  checking for objdump... objdump
  checking how to recognize dependent libraries... pass_all
  checking for dlltool... no
  checking how to associate runtime and link libraries... printf %s\n
  checking for ar... ar
  checking for archiver @FILE support... @
  checking for strip... strip
  checking for ranlib... ranlib
  checking command to parse /usr/bin/nm -B output from gcc object... ok
  checking for sysroot... no
  checking for a working dd... /bin/dd
  checking how to truncate binary pipes... /bin/dd bs=4096 count=1
  checking for mt... no
  checking if : is a manifest tool... no
  checking for dlfcn.h... yes
  checking for objdir... .libs
  checking if gcc supports -fno-rtti -fno-exceptions... no
  checking for gcc option to produce PIC... -fPIC -DPIC
  checking if gcc PIC flag -fPIC -DPIC works... yes
  checking if gcc static flag -static works... yes
  checking if gcc supports -c -o file.o... yes
  checking if gcc supports -c -o file.o... (cached) yes
  checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
  checking whether -lc should be explicitly linked in... no
  checking dynamic linker characteristics... GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking whether stripping libraries is possible... yes
  checking if libtool supports shared libraries... yes
  checking whether to build shared libraries... yes
  checking whether to build static libraries... yes
  checking how to run the C++ preprocessor... g++ -E
  checking for ld used by g++... /usr/bin/ld -m elf_x86_64
  checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
  checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
  checking for g++ option to produce PIC... -fPIC -DPIC
  checking if g++ PIC flag -fPIC -DPIC works... yes
  

Bug#821715: PHP 7.0 transition - PHP bindings removed and uploaded to DELAYED/2

[Torsten Landschoff]

Hi Ondrej,

On 06/15/2016 10:24 AM, Ondřej Surý wrote:
> in an effort to finally finish PHP 7.0 transition started in April, I
> removed PHP bindings from swig as it doesn't look like swig will support
> PHP 7.0 anytime soon and also from the remaining packages using swig to
> build PHP bindings.
not sure if there is a misunderstanding: SWIG can generate bindings for
all supported languages (which does not currently include PHP7)
regardless of configure arguments.
AFAICT you just passed --without-php to configure in the new SWIG
release. The resulting binary will still allow creating PHP bindings
(albeit broken).

So I don't see how this helps in the transition - looks like I am
missing something!?

tracker.debian.org states
> This package is part of the ongoing testing transition known as php7.0
> . Please
> avoid uploads unrelated to this transition
which is why I uploaded 3.0.8 to experimental only to not disturb the
php7.0 transition hoping that upstream will update the PHP generation.
So, sorry. Just uploading swig dropping the php dependencies is
something I should have done to help I guess...

Greetings, Torsten

Processed: severity of 827409 is serious

[Debian Bug Tracking System]

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

> # The class can’t work without its proper dependencies.
> severity 827409 serious
Bug #827409 [php-text-captcha] php-text-captcha depends on php-pear
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Bug#827405: marked as done (cgit: update to version 1.0 fixes CVE-2016-2315)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 22:26:06 +
with message-id 
and subject line Bug#827405: fixed in cgit 1.0+git2.8.3-1
has caused the Debian Bug report #827405,
regarding cgit: update to version 1.0 fixes CVE-2016-2315
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.)


-- 
827405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cgit
Version: 0.12.0.git2.7.0-1
Severity: grave
Tags: security upstream
Justification: user security hole

Dear Maintainer,

The above version of cgit embeds git 2.7.0, which is affected
by CVE-2016-2315 [1]. The update to cgit 1.0 [2, 3] includes
git 2.8.3, which fixes the issue.

[1] https://security-tracker.debian.org/tracker/CVE-2016-2315
[2] http://article.gmane.org/gmane.comp.version-control.cgit/3076
[2] https://bugs.debian.org/826764

Regards,
Peter
--- End Message ---
--- Begin Message ---
Source: cgit
Source-Version: 1.0+git2.8.3-1

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

Debian distribution maintenance software
pp.
Peter Colberg  (supplier of updated cgit 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: Wed, 15 Jun 2016 15:18:24 -0400
Source: cgit
Binary: cgit
Architecture: source
Version: 1.0+git2.8.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cgit Packaging Team 
Changed-By: Peter Colberg 
Description:
 cgit   - hyperfast web frontend for git repositories written in C
Closes: 826764 827405
Changes:
 cgit (1.0+git2.8.3-1) unstable; urgency=medium
 .
   * New upstream release
 - Uses internally Git 2.8.3, which fixes CVE-2016-2315 (Closes: #827405)
   * Update patch headers to conform to DEP-3
   * Set Maintainer to Debian Cgit Packaging Team (Closes: #826764)
   * Add myself to Uploaders
   * Update Homepage to https
   * Add Vcs-Git and Vcs-Browser
   * Bump Standards-Version to 3.9.8
   * Update debian/copyright
   * Enable verbose compilation
   * Re-enable hardening flags
   * Revise debian/rules
   * Fix spelling
   * Add debian/watch
   * Add debian/gbp.conf
   * Add get-orig-source target to pack orig tarball
Checksums-Sha1:
 b587b2c8912fe805b99da87bde12384762a0736f 2059 cgit_1.0+git2.8.3-1.dsc
 f20e086fca3757307217a310d9ba2309d56d829b 5897262 cgit_1.0+git2.8.3.orig.tar.gz
 10a3a69faf2e22052506fcb54a1ffa7ee4f0170b 10072 
cgit_1.0+git2.8.3-1.debian.tar.xz
Checksums-Sha256:
 f2e2e8915577558e57b8f8e01c991d16aa019d65296732dbd93039e0c8c147fa 2059 
cgit_1.0+git2.8.3-1.dsc
 c4a22466ae735c4f94668b6c3a1e6b15e7b71fd11068ec6852772f8274c0d07b 5897262 
cgit_1.0+git2.8.3.orig.tar.gz
 5f597027bf80b98c0cb62a364d47116de6b1c16d395e6cc6ce21a564b3652f79 10072 
cgit_1.0+git2.8.3-1.debian.tar.xz
Files:
 e93af93215cb48f188c565defd376ce4 2059 net extra cgit_1.0+git2.8.3-1.dsc
 d7349aab440877a6a6921c08828d2ffb 5897262 net extra 
cgit_1.0+git2.8.3.orig.tar.gz
 4653d6e98a6fec4865e1e15bd3d253f6 10072 net extra 
cgit_1.0+git2.8.3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJXYbKvAAoJEB5F+Mqd4jsW+88QAI7xI77FCJFHLjplIfCVqhix
SzIG5JcyJq/GkyqoOhNRly10qVn47M8zrxxNTE3bamGYvQXU4jpFM7P5CAVY1Jof
zp1bhoKly/K/91Ux3BPyN14/EuREav/1MBNYHmmoWG9QHG/2p3wBs2i8E+RdlC6R
Pj31qW6JtdDbMUKcYAIvu38Q8cRayNyeeOqTWRGBBlhZESmpHuY5TYCnN4JItSJY
auvW44HkC6HjOExRy0Hm/WyuELB64vuYq/Pf5ZtVh0kgk+QfJ40dBh0SI2Z8DqTM
2n0S8Jk+F1CkhTsyyXyB96I8bPsdf/wQLIUwVnqtcRgqSHFZDuk65ZcHAAo72lik
PtD1DFtvRA7HeBAEGx1srN+Yv2nlxWcp2f/AArGrCm/ERd8CGZ/2uIUOSHdnclic
56Z4nJ8quFettbzSaHe8ob7+fb3dgy+UgbQexkWOnkR/MuLdOaNQ3dZ4K/s6r6uW
0TmyJQuYl/y0Zmn/JlX7M60BHIwkp7a8XwQnmgFBBGNXzfrdkuNvpdZYTl0JzWE6
gmeYw881MrRQUuq6Ti8VFqfQCD/nJskTw0DzX3LjTeh7WGYUICKMb5vJURokt7U5
bFbjTgfcWcR2p9J7S2MdV/M+uKxGdzkpPHkZdKt1kUnKiILlky3BfW7ldyhYDmFc
6sOkcjxVaxbiwVpnZBKL
=TpPG
-END PGP SIGNATURE End Message ---

Bug#827383: RFS: gmp-ecm/7.0.1+ds-2 [RC] -- Factor integers using the Elliptic Curve Method

[Jerome BENOIT]

Hi Again:

On 15/06/16 22:19, Eric Heintzmann wrote:
> 
> 
> Le 15/06/2016 à 23:12, Jerome BENOIT a écrit :
>> Hello Eric,
>>
>> On 15/06/16 20:57, Eric Heintzmann wrote:
>>
>>
>>> Le 15/06/2016 à 16:41, Jerome Benoit a écrit :
 Package: sponsorship-requests
 Severity: serious
 Justification: fails to build from source (but built successfully
>> in the past)

 Dear Sponsors,

 I am looking for sponsorship for the Debian package gmp-ecm
>> [1], a mathematical package.
 This release mainly works around an unisolated gcc-5 issue for
>> arch s390x which caused
 a FTBFS.

>>> How did you fixed this issue ?
>>> I would like to use you solution on gnustep-base.
>>
>> The lazy way. As it works well with gcc-6, the package is built with
>> gcc-6 (only on s390x arch).
>> See the git repository at Alitoh (and certainly sooner, the source
>> material at Debian Sources).
> Thanks for you quick answer.
> In your changelogs you write about a not isolated gcc.
> Is there a bug report somewhere (in debian, in gcc upstream ...)?
> 

I parsed the Debian gcc-5 bugreport list, and I found nothing related.
I also Googled, but I got nothing relevant.

For me, debugging a compiler is as debugging a kernel: not my cup of tea
and certainly out of my scope.

Note that for my issue, I could also build with the -O0 option:
given that gcc-6 will become the default sooner or later, I choose to built with
gcc that does not raise the issue.

Cheers,
Jerome

> Thanks
> 
> 

Bug#827279: libcpputest-dev: generated/CppUTestGeneratedConfig.h not installed, breaks reverse dependencies build

[Luca Boccassi]

On 15 June 2016 at 20:41, Raphael Hertzog  wrote:
> Hello,
>
> Thanks for the report.
>
> On Tue, 14 Jun 2016, Luca Boccassi wrote:
>> The simple solution is to have libcpputest-dev install
>> generated/CppUTestGeneratedConfig.h in /usr/include/CppUTest. A simple
>> patch for the install file is attached.
>
> In fact "make install" did the right thing already but I was blindly
> copying the files from the include directory in the source tree... so
> instead of using your patch I made sure to install the files installed
> by make install.
>
> And since I plead guilty of not having tested my upload I added a DEP-8
> test so that I can easily test updated versions in the future...
>
> Cheers,
> --
> Raphaël Hertzog ◈ Debian Developer
>
> Support Debian LTS: http://www.freexian.com/services/debian-lts.html
> Learn to master Debian: http://debian-handbook.info/get/

Thanks for quickly fixing it, I can confirm the new upload works fine
with my packages.

Kind regards,
Luca Boccassi

Bug#827383: RFS: gmp-ecm/7.0.1+ds-2 [RC] -- Factor integers using the Elliptic Curve Method

[Eric Heintzmann]

Le 15/06/2016 à 23:12, Jerome BENOIT a écrit :
> Hello Eric,
>
> On 15/06/16 20:57, Eric Heintzmann wrote:
>
>
> > Le 15/06/2016 à 16:41, Jerome Benoit a écrit :
> >> Package: sponsorship-requests
> >> Severity: serious
> >> Justification: fails to build from source (but built successfully
> in the past)
> >>
> >> Dear Sponsors,
> >>
> >> I am looking for sponsorship for the Debian package gmp-ecm
> [1], a mathematical package.
> >> This release mainly works around an unisolated gcc-5 issue for
> arch s390x which caused
> >> a FTBFS.
> >>
> > How did you fixed this issue ?
> > I would like to use you solution on gnustep-base.
>
> The lazy way. As it works well with gcc-6, the package is built with
> gcc-6 (only on s390x arch).
> See the git repository at Alitoh (and certainly sooner, the source
> material at Debian Sources).
Thanks for you quick answer.
In your changelogs you write about a not isolated gcc.
Is there a bug report somewhere (in debian, in gcc upstream ...)?

Thanks




signature.asc
Description: OpenPGP digital signature

Bug#827411: piuparts: FTBFS on jessie: 'wheezy' != 'squeeze'

[Dominic Hargreaves]

Source: piuparts
Version: 0.62
Severity: serious
Justification: FTBFS

This package fails to build on a clean jessie sbuild chroot:

==
FAIL: testConfStdDistroNames (test_config.ConfStdDistroTests)
--
Traceback (most recent call last):
  File "/<>/tests/test_config.py", line 20, in 
testConfStdDistroNames
self.assertEqual(self.oldstable, 'squeeze')
AssertionError: 'wheezy' != 'squeeze'

--
Ran 39 tests in 0.536s

FAILED (failures=1)

The complete log is at

http://perl.debian.net/rebuild-logs/jessie/piuparts_0.62/piuparts_0.62_amd64-20160615-1509.build

Cheers,
Dominic.

Bug#827383: RFS: gmp-ecm/7.0.1+ds-2 [RC] -- Factor integers using the Elliptic Curve Method

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Eric,

On 15/06/16 20:57, Eric Heintzmann wrote:
> 
> 
> Le 15/06/2016 à 16:41, Jerome Benoit a écrit :
>> Package: sponsorship-requests
>> Severity: serious
>> Justification: fails to build from source (but built successfully in the 
>> past)
>>
>> Dear Sponsors,
>>
>>  I am looking for sponsorship for the Debian package gmp-ecm [1], a 
>> mathematical package.
>>  This release mainly works around an unisolated gcc-5 issue for arch 
>> s390x which caused
>>  a FTBFS.
>>
> How did you fixed this issue ?
> I would like to use you solution on gnustep-base.

The lazy way. As it works well with gcc-6, the package is built with gcc-6 
(only on s390x arch).
See the git repository at Alitoh (and certainly sooner, the source material at 
Debian Sources).

Cheers,
Jerome

> 
> Thanks
> Eric
> 

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJXYcS4AAoJED+SGaZ/NsaL+REgAKrsZK6Smn/g3Aewm3To1/n1
4FPZ2MaJG1vZs5bT155s8j1tpvtz7rJHLrAsIWQ6STXiXXJrIj/hzYaHRdoH8EBY
9z3y6TYfps4ebG8TI802IFgrT25yQkuuvX9B1PO3Yh4OyZxme/fNj+wd5gcryiZu
ue5Z5iHva4yX7ZtFhucrzv3NkYJS7CLWTdPXZLemDx1n9FwHwgGH9npAacTpyrwg
wyg8bn0OQGScH6a1CcwuWQHDU36HC6LaL/FsfTrtBZ1QoDfkiQLMok5TXVql657X
VQ0SHsl/rcx4PJ8RbT3Y5ea4gKCQzNbW/k9005u4JhU+cYv+/Ak6Kd8eOjsxurf3
PjNIaFStno36NIr69F2lHa1QVTAVNAoV1CmzPeAjYfX0xe37GNSYSbGGL4LydLVj
jSg4xb+bwoFo9JPQTtrLH4FU89cedtWmvUZQQi4GbdOVmV/nmbc5CVmux6l/unES
UKmZohYwW+L/06kbg9h+wQFQp+UWXhfWiWudaKEHIphymlaVqPk84CNJCyUHQ7dv
Re5KmFIzkK9F8ZzxAqJ47i4DZksN2q4TAOwv6o+qIUynRTXK4k1Bge38tc8ElBJk
tj9GJ3FzCF/W4ZrWdogvjb0NbLEUoI7lP44ULMVD9KMPi4jZv7b7VwJRzQyUXySs
Ess8bwIMjTxX6R4N1Kcm5MgRJX9YaUH7VYIuspKz8eJwrkMGNjqVr98gyPRUOaFC
c0WE0yid+RSRnakf1iCGsaBQrhlI3IvyY4/z2g7z+oZgb2Ot41vYQwoG2J9POOvB
OCJMJ2OSlkHk21MCk797FQUDEArW4XmcQGYN6CHYzjDaf8ZaNmyYcrBx6h3KKHSS
xgSUBFTizpJZsu2NF94/Jzdz1oMJMgQIwc+giT7L3NfkI9yB0TH4JHYl5hxxudAv
2U3hTzDsRjq0o1hypp6BN3BsPfUAYKtWt11+dOk2+biLIaBnizupupYsiCbsuSAl
CXEgfgWtR3f/oAyQlrNbyyDnqIcUymHjXrZnXDmSlXXZfta/oTbbEHUEf4plr6h1
tcuyo45MvhyL01gAvakZwkYmWGl48yQWnI/OzGCyHpvDEfoXw9CDGFfKJy4XI3jx
HyEG5b40/uJtzQodUE9ut2OsV8bB+7e4jBpOtamwBiQpRSqJJSmPXao2eq93s+cp
wws3hCMXCe40VDNflzVaRZimDX+CoRbuuSf1i+wadPT1HHIEMBeHVaOBliARq0nu
iBSIWonbcjR1DIcZhJccuCNBnBrdkGBs309YWUN5pAc5+iLyhnpxZ1AyahDbPy2b
/rV0sw3RjAfqX3585+FN23UxswZDMg/Bd9dD2lPBT7zbAX8B16nrZcGCMiHNhok=
=zYxV
-END PGP SIGNATURE-

Bug#827383: RFS: gmp-ecm/7.0.1+ds-2 [RC] -- Factor integers using the Elliptic Curve Method

[Eric Heintzmann]

Le 15/06/2016 à 16:41, Jerome Benoit a écrit :
> Package: sponsorship-requests
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Dear Sponsors,
>
>   I am looking for sponsorship for the Debian package gmp-ecm [1], a 
> mathematical package.
>   This release mainly works around an unisolated gcc-5 issue for arch 
> s390x which caused
>   a FTBFS.
>
How did you fixed this issue ?
I would like to use you solution on gnustep-base.

Thanks
Eric

Bug#827279: libcpputest-dev: generated/CppUTestGeneratedConfig.h not installed, breaks reverse dependencies build

[Raphael Hertzog]

Hello,

Thanks for the report.

On Tue, 14 Jun 2016, Luca Boccassi wrote:
> The simple solution is to have libcpputest-dev install
> generated/CppUTestGeneratedConfig.h in /usr/include/CppUTest. A simple
> patch for the install file is attached.

In fact "make install" did the right thing already but I was blindly
copying the files from the include directory in the source tree... so
instead of using your patch I made sure to install the files installed
by make install.

And since I plead guilty of not having tested my upload I added a DEP-8
test so that I can easily test updated versions in the future...

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Processed: Re: cgit: update to version 1.0 fixes CVE-2016-2315

[Debian Bug Tracking System]

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

> block 827405 by 826764
Bug #827405 [cgit] cgit: update to version 1.0 fixes CVE-2016-2315
827405 was not blocked by any bugs.
827405 was not blocking any bugs.
Added blocking bug(s) of 827405: 826764
>
End of message, stopping processing here.

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

Bug#827405: cgit: update to version 1.0 fixes CVE-2016-2315

[Peter Colberg]

Package: cgit
Version: 0.12.0.git2.7.0-1
Severity: grave
Tags: security upstream
Justification: user security hole

Dear Maintainer,

The above version of cgit embeds git 2.7.0, which is affected
by CVE-2016-2315 [1]. The update to cgit 1.0 [2, 3] includes
git 2.8.3, which fixes the issue.

[1] https://security-tracker.debian.org/tracker/CVE-2016-2315
[2] http://article.gmane.org/gmane.comp.version-control.cgit/3076
[2] https://bugs.debian.org/826764

Regards,
Peter

Bug#767905: kwallet: after upgrade from jessie to stretch kwalletmanager doesn't see my old wallets

[Paul Gevers]

Hi

On 15-06-16 09:16, Martin Steigerwald wrote:
> I bet you can have it have another go at it by setting alreadyMigrated to 
> false
> 
> martin@merkaba:~/.config> grep Migr kwalletrc
> [Migration]
> alreadyMigrated=true

paul@ruapehu ~ $ cat .config/kwalletrc
[Wallet]
First Use=false

That is all there was in my kwalletrc file.

> and restarting KWallet. You may need to restart your Plasma session in order 
> to do that, or restart the kwallet service manually (but I didn´t find it in 
> background services kcm).

I terminated logged out of KDE, restarted with "startx" and still, the
wallets are not migrated. The kwalletrc after restart still looks like

paul@ruapehu ~ $ cat .config/kwalletrc
[Wallet]
First Use=false
[Migration]
alreadyMigrated=false

Paul



signature.asc
Description: OpenPGP digital signature

Processed: found 780424 in 0.7.8+dfsg-1

[Debian Bug Tracking System]

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

> found 780424 0.7.8+dfsg-1
Bug #780424 [galette] Emedded ZendDb component affected by several security 
issues
Marked as found in versions galette/0.7.8+dfsg-1.
> thanks
Stopping processing here.

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

Bug#822476: python-django-authority: Package is useless

[Herbert Fortes]

Hi Raphael Rigo,

> Package: python-django-authority
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> current version of the package does not support Django 1.7, which is the
> version included in jessie. As such, the package is probably useless for
> all users.
> 
> Django 1.7 support was added in version 0.9, released in november 2015.
> Version 0.5, which is in Debian, has been released in March 2013.
> 
> The package should be removed or upgraded.
> 

I will try to close this bug doing the upgrade to
the last version[0]:

 - 0.11 (2016-03-29):

Added Migration in order to support Django 1.8
Dropped Support for Django 1.7 and lower
Fix linter issues

[0] - https://github.com/jazzband/django-authority



regards,
-- 
Herbert Parentes Fortes Neto (hpfn)

Processed: Re: Bug#827391: nvidia-driver: Add support to Nvidia GeForce 10xx GPUs w/ driver 367.27

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #827391 [nvidia-driver] nvidia-driver: Add support to Nvidia GeForce 10xx 
GPUs w/ driver 367.27
Severity set to 'important' from 'critical'

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

Bug#827391: nvidia-driver: Add support to Nvidia GeForce 10xx GPUs w/ driver 367.27

[Luca Boccassi]

Control: severity -1 important

On Wed, 2016-06-15 at 18:23 +0200, Julien Aubin wrote:
> Package: nvidia-driver
> Version: 352.79-1~bpo8+1
> Severity: critical
> Justification: breaks the whole system
> 
> Hello,
> 
> GPUs GeForce 10xx are out now for several weeks, and the first stable Linux
> driver series which support them is 367.27 available from there :
> http://www.nvidia.com/download/driverResults.aspx/104284/en-us
> 
> Note this is a LTS branch for the drivers.
> 
> Users of this hardware will be unable to reach any usable X session, nor
> using
> any graphical mode. The bug is critical as this hardware will become more
> and
> more widespread over time.

Sorry but this bug is not critical nor grave, as it clearly only affect
a given specific configuration, and not all (and not even the majority)
of the users of the package. So it would be a grave disservice for the
vast majority of users to remove the package from the archive and the
distribution, for whom the driver works just fine, only because it's too
old to work with some new hardware. Hence the downgrading.

> So could you please :
> 1/ at least upload this driver version on experimental repo so that it is
> installable using jessie w/ backports, testing and sid ?
> 2/ integrate this driver for stretch release, which seems reasonable since
> the
> development window is still 6 months away ?
> 
> Please notify me when you've packaged it to experimental so that I could
> give
> it a test with my current hardware. Once I've upgraded to a GeForce 10xx
> I'll
> perform the test again with various games.
> 
> Many thanks and regards

The newer releases are all packaged and ready, but the uploads are in
the new queue, in some cases since February. There is literally nothing
we as maintainers can do until they have been manually approved by the
FTP masters.

Meanwhile, you can build the package from our SVN repositories following
the instructions on the wiki:

https://wiki.debian.org/NvidiaGraphicsDrivers#Building_newer_releases_from_SVN

Feedback on the current state of the packages in SVN is greatly
appreciated. Feel free to open bugs if you find any issue with them.

Kind regards,
Luca Boccassi


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

Bug#826687: marked as done (translate-toolkit-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc-base/translate-toolkit)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 17:18:43 +
with message-id 
and subject line Bug#826687: fixed in translate-toolkit 2.0.0~b2-1
has caused the Debian Bug report #826687,
regarding translate-toolkit-doc: fails to upgrade from 'sid' - trying to 
overwrite /usr/share/doc-base/translate-toolkit
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.)


-- 
826687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: translate-toolkit-doc
Version: 2.0.0~b1-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 translate-toolkit-doc.
  Preparing to unpack .../translate-toolkit-doc_2.0.0~b1-1_all.deb ...
  Unpacking translate-toolkit-doc (2.0.0~b1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/translate-toolkit-doc_2.0.0~b1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/translate-toolkit', which is also 
in package translate-toolkit 1.13.0-1
  Errors were encountered while processing:
   /var/cache/apt/archives/translate-toolkit-doc_2.0.0~b1-1_all.deb


cheers,

Andreas


translate-toolkit=1.13.0-1_translate-toolkit-doc=2.0.0~b1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: translate-toolkit
Source-Version: 2.0.0~b2-1

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated translate-toolkit 
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, 16 Jun 2016 01:00:39 +1000
Source: translate-toolkit
Binary: translate-toolkit python-translate python3-translate 
translate-toolkit-doc
Architecture: source
Version: 2.0.0~b2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian l10n developers 
Changed-By: Stuart Prescott 
Closes: 826687
Description: 
 python3-translate - Toolkit assisting in the localization of software (Python 
3)
 python-translate - Toolkit assisting in the localization of software (Python 2)
 translate-toolkit-doc - Toolkit assisting in the localization of software 
(documentation)
 translate-toolkit - Toolkit assisting in the localization of software
Changes:
 translate-toolkit (2.0.0~b2-1) experimental; urgency=medium
 .
   * New upstream release.
   * Add missing Breaks/Replaces for translate-toolkit-doc (Closes: #826687).
Checksums-Sha1: 
 5cfaa28ca78bd015dc7f70fc6abd7806c2f83ae6 3055 translate-toolkit_2.0.0~b2-1.dsc
 2a390b42a806e85781d5e028e12c7787c2b497e7 1087095 
translate-toolkit_2.0.0~b2.orig.tar.gz
 5c33bc22ad938f9254dad1e58d64798122454c42 34912 
translate-toolkit_2.0.0~b2-1.debian.tar.xz
Checksums-Sha256: 
 085e7c0e3fe1d8e1a3f0c7eb2b34cc686ac60ec8588a0b9789d73f5e330b9b92 3055 
translate-toolkit_2.0.0~b2-1.dsc
 db88eea06e7d87c1ca4f8a9036bd781d9d815b9650a355b987f8984c51dbd436 1087095 
translate-toolkit_2.0.0~b2.orig.tar.gz
 419c40b8bfa3ae5ff57cd98add21784476978110f4664451e8cf6fd1dd642745 34912 
translate-toolkit_2.0.0~b2-1.debian.tar.xz
Files: 
 01062f84f4508acb5f73bddfe119f873 3055 python optional 
translate-toolkit_2.0.0~b2-1.dsc
 622ea1ac60a2ee44de7bb80eae5273af 1087095 python optional 
translate-toolkit_2.0.0~b2.orig.tar.gz
 ef45632d2e0aed7d8314b9e89e4e7e0c 34912 python optional 
translate-toolkit_2.0.0~b2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXYXC9AAoJELvBfrsTlvL3RygP/300gxNMlKpTBbTA60lznbIL

Bug#827034: marked as done (FTBFS: test failure on s390x architecture)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 17:15:18 +
with message-id 
and subject line Bug#827034: fixed in gmp-ecm 7.0.1+ds-2
has caused the Debian Bug report #827034,
regarding FTBFS: test failure on s390x architecture
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.)


-- 
827034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gmp-ecm
Version: 7.0.1+ds-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Dear All,

it appears that some test failures persist on the s390x architectecture
when a shared library is built instead of a static one.

Thanks,
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)

Versions of packages gmp-ecm depends on:
ii  libc6 2.19-18+deb8u4
ii  libecm1   7.0.1+ds-1
ii  libgmp10  2:6.1.0+dfsg-2

gmp-ecm recommends no packages.

gmp-ecm suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gmp-ecm
Source-Version: 7.0.1+ds-2

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated gmp-ecm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Jun 2016 14:00:32 +
Source: gmp-ecm
Binary: gmp-ecm libecm1 libecm1-dev libecm1-dev-common libecm-dev
Architecture: source
Version: 7.0.1+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Description:
 gmp-ecm- Factor integers using the Elliptic Curve Method
 libecm-dev - dummy package
 libecm1- factor integers using the Elliptic Curve Method -- lib
 libecm1-dev - factor integers using the Elliptic Curve Method -- libdev
 libecm1-dev-common - factor integers using the Elliptic Curve Method -- header
Closes: 827034
Changes:
 gmp-ecm (7.0.1+ds-2) unstable; urgency=medium
 .
   * FTBFS[s390x] fix release (Closes: #827034), ad hoc workaround a gcc-5 bug
 not fully isolated.
   * Debianization:
 - debian/rules, force -O3 option.
Checksums-Sha1:
 1455d2928ca980c15c03f1d6f1194fae672a7811 2291 gmp-ecm_7.0.1+ds-2.dsc
 2461d2e6057c4cc029853e59fdae69d4d74a4b0c 10800 gmp-ecm_7.0.1+ds-2.debian.tar.xz
Checksums-Sha256:
 6345cc3eb1ff4a196af81c9dbcf028e353ef344180f08ba3a2b17e953b4a0fd7 2291 
gmp-ecm_7.0.1+ds-2.dsc
 02e848fed65d9c9425b31db50cae830eb2840ca36e02e85f6b778151c4830be0 10800 
gmp-ecm_7.0.1+ds-2.debian.tar.xz
Files:
 704cf1c8741879c03ab9819d6f3deefa 2291 math optional gmp-ecm_7.0.1+ds-2.dsc
 e9eab6b2b3fac600a4c3a1d7986b7933 10800 math optional 
gmp-ecm_7.0.1+ds-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXYWrLAAoJEPNPCXROn13ZgF4QALN5D/GAlrmHWEIn+kdBmGxW
/JcUhsmY5F/FqAn4zYAXeydonCvC3HHnIblmJJJtF2zPGf/t4mK0F6qCkITKas8M
4IzOpOa/VhdU8wVe+1uw0SqYeq23MEh4Y40RMe5e9Jw2JS3H3UAB4C57tCv49LmZ
4mDndHOsxlM59G2KR5KesP7JG/hIEtVqtQEjwMWLDAd+xr4rYd/ZBjUd/+6RndOL
HkdBKxZ8E1V/kCqePDLRbxZB9X/d9SVASFDOcpH5noCpi2fyZlzlJ08q/dQTpcnF
tbXmH15cIdhc+vKlowdIo3lXpWTC1UF1ABIQNGfOwVkveYTUTYGwBoQ7qsKX4XV0
iujaE9M2OVk8/KlOj6aU4b74IUx3OHw1msLsnBfmcEFXfnKVlv06uTY3/+bXLVKm
+SSOMQZ42h13eI3i8UOEd+gbZMZ51YxT3A2wfflCgGfkEV4Pe+VN9E5xxaewEdAw
wDaPtHc0eLpERhNWwRSNMlRI1o47KtFT9eCCdB/NSKBvJl6epKZNIMhBSk3SADS5
t3/8yOOtD4YM5VY9F0KV2XjH9NieHhOGBeGQmXPrY6lGHCn9/wI3XKuL/zmzL0Nw
x/5KdBVmKM/gioXP6C06NYLOED3VAU+tov1pyg49CxdY//y5t/9hEaR+FspOx1v+
KyUPycwxl7ryW+0VjYby
=rwBc
-END PGP SIGNATURE End Message ---

Bug#827262: marked as done (gcin: FTBFS: fatal error: QtCore/qplugin.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 17:14:42 +
with message-id 
and subject line Bug#827262: fixed in gcin 2.8.4+dfsg1-3
has caused the Debian Bug report #827262,
regarding gcin: FTBFS: fatal error: QtCore/qplugin.h: No such file or directory
to be marked as done.

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

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


-- 
827262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcin
Version: 2.8.4+dfsg1-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,

gcin fails to build from source in unstable/amd64:

  [..]

   ^
  gcc -o pin-juyin pin-juyin.o util.o pho-lookup.o locale.o pho-sym.o 
-Wl,-z,relro -Wl,--as-needed -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 
-latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 
-lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lX11 -ldl -lm -lappindicator3 
-ldbusmenu-glib -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 
-lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0
  rm -f gcin-fedora.spec
  sed -e "s/__gcin_version__/2.8.4/" < gcin-fedora.spec.in > gcin-fedora.spec
  make -C data
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160614102505.Vxible93Ts.gcin/gcin-2.8.4+dfsg1/data'
  export LD_LIBRARY_PATH=../im-client;../phoa2d pho.tab2.src
  export LD_LIBRARY_PATH=../im-client;../tsa2d32 tsin.src
  3倍 3 ㄅㄟ4 0
  Sorting 
  before delete duplicate N:49911
  after delete duplicate N:49911  max_len:15
  Sorting by usecount 
  Writing data tsin32 928657
  49911 phrases
  ../gcin2tab NewCJ3.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:33 keybits:6
  char def
  MaxPress: 5
  Defined Characters:140007
  phrase count:69725
  ../gcin2tab cj.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:27 keybits:6
  char def
  MaxPress: 5
  Defined Characters:13209
  phrase count:41
  ../gcin2tab ar30.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:41 keybits:6
  char def
  MaxPress: 5
  Defined Characters:25011
  phrase count:49
  ../gcin2tab ar30-big.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:41 keybits:6
  char def
  MaxPress: 5
  Defined Characters:86141
  phrase count:50
  ../gcin2tab pinyin.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:37 keybits:6
  char def
  MaxPress: 7
  Defined Characters:6865
  phrase count:9
  ../gcin2tab jyutping.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:33 keybits:6
  char def
  MaxPress: 7
  Defined Characters:13305
  ../gcin2tab cj5.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:27 keybits:6
  char def
  MaxPress: 5
  Defined Characters:74944
  phrase count:2
  ../kbmcv et.kbmsrc
  ../kbmcv et26.kbmsrc
  ../kbmcv zo.kbmsrc
  ../kbmcv pinyin.kbmsrc
  ../kbmcv dvorak.kbmsrc
  ../kbmcv mitac.kbmsrc
  ../kbmcv colemak.kbmsrc
  ../kbmcv ibm.kbmsrc
  ../kbmcv hsu.kbmsrc
  export LD_LIBRARY_PATH=../im-client;../phoa2d pho-huge.tab2.src
  ../gcin2tab simplex.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:27 keybits:6
  char def
  MaxPress: 2
  Defined Characters:17457
  phrase count:2
  ../gcin2tab symbols.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:48 keybits:6
  char def
  MaxPress: 1
  Defined Characters:47
  ../gcin2tab russian.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:48 keybits:6
  char def
  MaxPress: 1
  Defined Characters:47
  phrase count:2
  ../gcin2tab greek.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:50 keybits:6
  char def
  MaxPress: 2
  Defined Characters:56
  phrase count:2
  ../gcin2tab cj-punc.cin
  -- gcin2tab encoding UTF-8 --
  --- please use iconv -f big5 -t utf-8 if your file is in big5 encoding
  KeyNum:34 keybits:6
  char def
  MaxPress: 5
  

Processed: Re: Bug#796625: CLVM don't start

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #796625 [clvm] clvm: Has init script in runlevel S but no matching service 
file
Severity set to 'serious' from 'important'

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

Bug#827349: Thanks for reporting

[Martin Quinson]

This bug is "very similar" to #794704, that was reported and fixed a
year ago. This calls for more investigations, but I just wanted to
point that fact out.


Bye, Mt.

-- 
For every complex problem there is a solution which is simple, neat and wrong.


signature.asc
Description: PGP signature

Bug#827199: hfst: FTBFS: twolc test fails on big-endian systems

[Tino Didriksen]

On 13 June 2016 at 18:00, Aaron M. Ucko  wrote:

> Justification: fails to build from source (but built successfully in the
> past)
>
> Thanks for taking care of the twolc errors I reported in #826659.  The
> twolc test now succeeds on little-endian systems, and no longer hangs
> anywhere, but still fails on big-endian architectures (mips, powerpc,
> s390x, and several non-release architectures).  I don't have further
> details, but perhaps you can reproduce the problem on a porterbox.
> Could you please take a look?


Can reproduce. Looking into it upstream:
https://github.com/hfst/hfst/issues/328

While it did successfully build in the past, that was only because the test
suite was disabled until recently. The tests revealed the unsigned char
issue which was easy to fix, and now the endian issue which will not be as
easy.

-- Tino Didriksen

Bug#827383: marked as done (RFS: gmp-ecm/7.0.1+ds-2 [RC] -- Factor integers using the Elliptic Curve Method)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 14:52:05 + (UTC)
with message-id <669543560.6241828.1466002325552.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#827383: RFS: gmp-ecm/7.0.1+ds-2 [RC] -- Factor 
integers using the Elliptic Curve Method
has caused the Debian Bug report #827383,
regarding RFS: gmp-ecm/7.0.1+ds-2 [RC] -- Factor integers using the Elliptic 
Curve Method
to be marked as done.

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

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


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

Dear Sponsors,

I am looking for sponsorship for the Debian package gmp-ecm [1], a 
mathematical package.
This release mainly works around an unisolated gcc-5 issue for arch 
s390x which caused
a FTBFS.

Thanks in advance,
Jerome

[1] https://packages.qa.debian.org/g/gmp-ecm.html

-- 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 ---
hi,
>I am looking for sponsorship for the Debian package gmp-ecm [1], a 
>mathematical package.
>This release mainly works around an unisolated gcc-5 issue for arch s390x 
>which caused
>a FTBFS.

sponsored, but just FYI the testsuite seems to fail on some 32 bit archs


https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/armhf/g/gmp-ecm/20160615_082704@/log.gz
http://autopkgtest.ubuntu.com/packages/g/gmp-ecm/yakkety/armhf/
http://autopkgtest.ubuntu.com/packages/g/gmp-ecm/yakkety/i386/

I'm pretty sure this is an issue for Debian too
but I'm not aware of a similar test on Debian
https://ci.debian.net/packages/g/gmp-ecm/
(seems Debian is not running armhf and i386 on ci)

G.--- End Message ---

Bug#827383: RFS: gmp-ecm/7.0.1+ds-2 [RC] -- Factor integers using the Elliptic Curve Method

[Jerome Benoit]

Package: sponsorship-requests
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Sponsors,

I am looking for sponsorship for the Debian package gmp-ecm [1], a 
mathematical package.
This release mainly works around an unisolated gcc-5 issue for arch 
s390x which caused
a FTBFS.

Thanks in advance,
Jerome

[1] https://packages.qa.debian.org/g/gmp-ecm.html

-- 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)

Processed: notfound 822980 in ruby-email-reply-parser/0.5.8-1

[Debian Bug Tracking System]

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

> notfound 822980 ruby-email-reply-parser/0.5.8-1
Bug #822980 {Done: prav...@pod.pxq.in} [src:ruby-email-reply-parser] 
ruby-email-reply-parser: FTBFS: test_runner.rb:126:in `exit': no implicit 
conversion from nil to integer (TypeError)
No longer marked as found in versions ruby-email-reply-parser/0.5.8-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#802889: please don't depend on all python3 versions

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #802889 [python3-coverage] please don't depend on all python3 versions
Added tag(s) moreinfo.

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

Bug#802889: please don't depend on all python3 versions

[Ben Finney]

Control: tag -1 + moreinfo

On 15-Jun-2016, Mattia Rizzolo wrote:
> dunno and I haven't checked

Okay, so the “moreinfo” tag still applies as the relevant questions
are not answered.

> but now python3.4 is going away, and this is one of the last 2
> blockers, so somehow get rid of python3.4 dependency (after making
> it build, I guess)

Yes, making it build is a pre-requisite :-)

The build has been blocked by bug#801719 until only a few days ago. I
will now be able to work again on a new version.

-- 
 \“No matter how cynical you become, it's never enough to keep |
  `\up.” —Jane Wagner, via Lily Tomlin |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#802916: python-coverage: post-build tests fail: “coverage.misc.CoverageException: No data to report.”

[Ben Finney]

On 14-Jun-2016, Emilio Pozuelo Monfort wrote:
> So can you update coverage to 4.1 and hopefully fix #802801 with
> that? Or is there still blocking the update?

The last blocker of bug#799629 was resolved a few days ago, hooray! I
am now working on the new release.

-- 
 \  “The best mind-altering drug is truth.” —Jane Wagner, via Lily |
  `\Tomlin |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#814862: fix for qt4 Conflicts

[Gianfranco Costamagna]

control: tags -1 pending


Hi Ian!
>Gianfranco, can you take a look at this in alioth git and upload the 

>package if you are happy?


I added a patch to fix a build failure, rebased the changelog, tested, signed
and uploaded :)

thanks!

G.

Bug#814862: marked as done (gambas3: fails to find an upgrade path from jessie to stretch)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 13:49:26 +
with message-id 
and subject line Bug#814862: fixed in gambas3 3.8.4-3
has caused the Debian Bug report #814862,
regarding gambas3: fails to find an upgrade path from jessie to stretch
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.)


-- 
814862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gambas3
Version: 3.8.4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails and
the jessie version is kept installed rather than upgraded.

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

This is apt problemresolver output from the jessie->stretch upgrade.

[...]
  The following NEW packages will be installed:
[...]
  The following packages have been kept back:
gambas3 gambas3-ide
  The following packages will be upgraded:
[...]

[...]
  Investigating (0) gambas3-ide [ amd64 ] < 3.5.4-2 -> 3.8.4-2 > ( devel )
  Broken gambas3-ide:amd64 Conflicts on gambas3-gb-qt4 [ amd64 ] < 3.5.4-2+b1 
-> 3.8.4-2 > ( libdevel )
Considering gambas3-gb-qt4:amd64 12 as a solution to gambas3-ide:amd64 1
Holding Back gambas3-ide:amd64 rather than change gambas3-gb-qt4:amd64
[...]
  Investigating (0) gambas3 [ amd64 ] < 3.5.4-2 -> 3.8.4-2 > ( devel )
  Broken gambas3:amd64 Depends on gambas3-ide [ amd64 ] < 3.5.4-2 -> 3.8.4-2 > 
( devel ) (>= 3.8.4-2)
Considering gambas3-ide:amd64 1 as a solution to gambas3:amd64 0
Holding Back gambas3:amd64 rather than change gambas3-ide:amd64
   Try to Re-Instate (1) gambas3-ide:amd64
   Try to Re-Instate (1) gambas3:amd64
  Done

So what happened here?

gambas3-gb-qt4 is installed in jessie and an upgradable candidate,
but gambas3-ide, which is also installed in jessie, now
Conflicts: gambas3-gb-qt4.

gambas3-gb-qt4 has a score of 12 (there are several rdepends) while the
gambas3-ide and gambas3 meta-packages only have rather low scores of
1 and 0, respectively. So gambas3-gb-qt4 wins and does not get removed.

So one ends up with the jessie versions of gambas3 and gambas3-ide still
installed while all other packages have been upgraded to the stretch
version.

Right now I have no suggestions how to solve this upgrade issue.

That Conflicts: gambas3-gb-qt4 is nasty. Is the gambas3-gb-qt4 package
still needed? Could it be converted into a transitional package?


cheers,

Andreas


gambas.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gambas3
Source-Version: 3.8.4-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Jun 2016 14:40:21 +0200
Source: gambas3
Binary: gambas3 gambas3-dev gambas3-templates gambas3-gb-cairo 
gambas3-gb-clipper gambas3-gb-dbus gambas3-gb-form-stock gambas3-gb-gmp 
gambas3-gb-chart gambas3-gb-compress gambas3-gb-compress-bzlib2 
gambas3-gb-compress-zlib gambas3-gb-crypt gambas3-gb-db gambas3-gb-db-form 
gambas3-gb-db-mysql gambas3-gb-db-odbc gambas3-gb-db-postgresql 
gambas3-gb-db-sqlite2 gambas3-gb-db-sqlite3 gambas3-gb-desktop 
gambas3-gb-desktop-x11 gambas3-gb-form gambas3-gb-form-dialog 
gambas3-gb-form-editor gambas3-gb-form-mdi gambas3-gb-gtk gambas3-gb-gtk3 
gambas3-gb-gtk-opengl gambas3-gb-gui gambas3-gb-gui-opengl gambas3-gb-pdf 
gambas3-gb-image gambas3-gb-image-io gambas3-gb-image-imlib 
gambas3-gb-image-effect gambas3-gb-inotify gambas3-gb-markdown gambas3-gb-net 
gambas3-gb-scanner gambas3-gb-util gambas3-gb-util-web gambas3-gb-net-curl 
gambas3-gb-net-smtp gambas3-gb-net-pop3 gambas3-gb-openal gambas3-gb-opengl 
gambas3-gb-opengl-glsl gambas3-gb-opengl-glu gambas3-gb-opengl-sge 
gambas3-gb-openssl
 

Processed: Re: Bug#814862: fix for qt4 Conflicts

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #814862 [gambas3] gambas3: fails to find an upgrade path from jessie to 
stretch
Added tag(s) pending.

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

Bug#825354: marked as done (mudlet: FTBFS on armel/armhf: glu development package not found)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 13:20:03 +
with message-id 
and subject line Bug#825354: fixed in mudlet 1:3.0.0~delta-3
has caused the Debian Bug report #825354,
regarding mudlet: FTBFS on armel/armhf: glu development package not found
to be marked as done.

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

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


-- 
825354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mudlet
Version: 1:3.0.0~delta-2
Severity: serious

Hi,

Your package failed to build on armel/armhf:

Project MESSAGE: mudlet will be installed to /usr/local/bin...
Project MESSAGE: Lua files will be installed to /usr/local/share/mudlet/lua...
Project MESSAGE: Geyser lua files will be installed to 
/usr/local/share/mudlet/lua/geyser...
Project ERROR: glu development package not found
debian/rules:24: recipe for target 'override_dh_auto_configure' failed

Full logs at

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

Emilio
--- End Message ---
--- Begin Message ---
Source: mudlet
Source-Version: 1:3.0.0~delta-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 31 May 2016 21:03:18 +1000
Source: mudlet
Binary: mudlet
Architecture: source amd64
Version: 1:3.0.0~delta-3
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 mudlet - Graphical MUD client with fast lua scripting support
Closes: 825354
Changes:
 mudlet (1:3.0.0~delta-3) unstable; urgency=medium
 .
   * Remove arm from the builds Closes: #825354
   * Update to standards 3.9.8
Checksums-Sha1:
 9e5f78022842dbf56e7733d4fb95819edfaa119d 2248 mudlet_3.0.0~delta-3.dsc
 811c02ebd50777ab47208cf2ae6f003c908f3cc5 11080 
mudlet_3.0.0~delta-3.debian.tar.xz
 4fe4c347f2e54331dff83a9a0b8eb390de1d5047 16876928 
mudlet-dbgsym_3.0.0~delta-3_amd64.deb
 a7aa1b5c111d118cdf536ea2607ccde1fbbf87b4 2906002 mudlet_3.0.0~delta-3_amd64.deb
Checksums-Sha256:
 9bb2a4d0aac6256c16f524aba1267d9c56700ee3b1f8bd2b4ffa8027f1d6b042 2248 
mudlet_3.0.0~delta-3.dsc
 07bb8db25fdc1b968b7bb11249ce0254acb60e878b22f178dd002b227a528bd2 11080 
mudlet_3.0.0~delta-3.debian.tar.xz
 9ac3529a2769127d790a52516b2270917fd111f6973885b7318f1d1ae7ae9292 16876928 
mudlet-dbgsym_3.0.0~delta-3_amd64.deb
 220b85a8fd7cb1ae8ec2729fedb1aa991293d867ddbed760ee525031bc79c212 2906002 
mudlet_3.0.0~delta-3_amd64.deb
Files:
 d0cb308fc8cb011a1b20df0873972e04 2248 games extra mudlet_3.0.0~delta-3.dsc
 003a0e8fa108a6ee74e9fd52a1b0a276 11080 games extra 
mudlet_3.0.0~delta-3.debian.tar.xz
 d8f41c6c32f50ff96c54974c1eb32086 16876928 debug extra 
mudlet-dbgsym_3.0.0~delta-3_amd64.deb
 3f5f207c6254a8c1335942cc1454856c 2906002 games extra 
mudlet_3.0.0~delta-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXYVAHAAoJEAIhZsD/PITjH9MP/2cw2k75S2WWPbOKPIkkoWWT
7N4wf3WISlQGU6fdkbywMwDQzvunGdNJhDBNeihhB2LH1cKyxrNjf0Sl6JJZ7fcj
eUr7Gc9wz8yLexelF2sc+5ou9PSqfUBW7eOhUczsJILFWTvX097j25LxfGmW1sCG
x16PNL2MqEznFIRMnDgQoYh8y46URjNB5CB6Bw7hfuIFxPzeCbIm/DHlBUsWFvgk
86gtjLl919S8X/CCGMa96L7IF4KK+e+hD9lPtbQGmdVroByB4fHmClwD6QgiTd5C
ct91aa1rX37tbjUuY+ZaydN1KKuf5HriL/wyqfL8HRJyVG30YYXdRkj4nblE4n2p
TCiQluODG7UQ7hZxe3ny0wRF5y2WUZ6Bet4g2YhGeDiDhsxl7Pbqua6d/u82hwv2
RTqr3F2OonsUsmQ/lNfPJvn1WvDkPy4UydhJ5DQOXOpdq/kuK/2fOjMVlaBL44W3
RBTRv0EBAz2wYQvLiE5Tlahb3DsxTsEvvdkIk5w+1HKjaqecCXv8PfLq816WGHr0
LwpKbb/0PIcN3HVZESzHa3DPWp6/Dg8pzqG9klgnvy08Y/xqoJgY7tvzAhuEGTsk
rJbmQIOYyHXDLHs61ioZuyHu1JW/ttadNw3Va4ZV1Qwy7hpcYSIMPp4ifSrQZ4Io
L3yJrESv6b4Y/BY8Y7y2
=7ONd
-END PGP SIGNATURE End Message ---

Bug#827378: open-infrastructure-container-tools: missing Depends: lsb-release

[Andreas Beckmann]

Package: open-infrastructure-container-tools
Version: 20160615-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package open-infrastructure-container-tools.
  (Reading database ... 
(Reading database ... 7482 files and directories currently installed.)
  Preparing to unpack 
.../open-infrastructure-container-tools_20160615-1_all.deb ...
  Unpacking open-infrastructure-container-tools (20160615-1) ...
  Setting up open-infrastructure-container-tools (20160615-1) ...
  dpkg: error processing package open-infrastructure-container-tools 
(--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   open-infrastructure-container-tools


Debugging this a bit further, I found that the .config script dies here:

DISTRIBUTOR="$(lsb_release -is 2>/dev/null)"

since lsb_release is not found.


cheers,

Andreas


open-infrastructure-container-tools_20160615-1.log.gz
Description: application/gzip

Bug#821148: Fwd: Re: License for CDAT software

[Alastair McKinstry]

For records.


 Forwarded Message 
Subject:Re: License for CDAT software
Date:   Mon, 13 Jun 2016 11:40:24 -0700
From:   Denis Nadeau 
To: Williams, Dean N. , Alastair McKinstry
, Rogers, Leah L. ,
dr...@llnl.gov 
CC: Taylor, Karl E. 



Hi Alastair,


I should be releasing cmor 3.1 this week for CMIP6 project.  You can
take a loot at the "beta" code here:

https://github.com/PCMDI/cmor/tree/cmor3


I am still working on the documentation and will make sure that the
copyright has been refreshed.

I'll  get the announcement for the 3.1 release.

Regards,
Denis
On 6/13/16 6:34 AM, Williams, Dean N. wrote:
> Dear Alastair:
>
> Both Leah and Bob have left LLNL. Denis is now in charge of the
> development of CMOR. I am surprised to see the 1996 copyright and Bob
> Drach as the author.
>
> In any case, it is okay to use CMOR independent of UV-CDAT. It is
> still under the same BSD open-souruce license agreement.
>
> Best regards,
> Dean 
>
> From: Alastair McKinstry  >
> Date: Monday, June 13, 2016 at 4:25 AM
> To: "Rogers, Leah L." >,
> Dean Williams >,
> "dr...@llnl.gov "  >
> Subject: Re: License for CDAT software
>
> Dear Leah,
>
> Some time ago you gave some reassurances (below) on the distribution
> of the CMOR software. Thank you for this.  However two questions have
> arisen that I hope you can clarify.
>
> (1) A user has pointed out certain files included in CMOR have the header:
>
> c  Copyright:   1996, Regents of the University of California
> c   This software may not be distributed to others without
> c   permission of the author.
> c
> c  Author:  Bob Drach, Lawrence Livermore National Laboratory
> c   dr...@llnl.gov
>
> Can you confirm that it is acceptable to distribute these with the
> assurance / caveat given previously?
>
> (2) The libcmor library is also usable independent of CDAT and some
> users have started linking against it in their applications; eg. the
> popular 'cdo' climate data operators utility has experimental
> functionality to to 'cmorization' using the libcmor library.  Unless a
> copy of CDAT is shipped with 'cdo' this would technically be a breach
> of the licensing terms, which is unlikely to be what anyone intends.
>
> Would it be possible then to state that (1) is covered by the previous
> agreement  and that (2) shipping a copy of CDAT with libcmor is not
> required?
>
> Best regards
> Alastair McKinstry
>
>
> On 04/06/2010 00:40, Rogers, Leah L. wrote:
>>
>> Dear Alistair,
>>
>> Dean tells me that you also are interested in distributing CMOR as
>> well as CDAT.  CMOR is approved for unrestricted release which is not
>> an official open source license, but from our institution’s
>> perspective we are supportive of it being included in your Debian
>> distribution along with CDAT. I will be happy to work with you to
>> achieve this. Feel free to call me at 925 422 3538 if you would like
>> to discuss it by phone. All the best, Leah
>>
>>  
>>
>> *From:*Dean N. Williams [mailto:william...@llnl.gov]
>> *Sent:* Saturday, May 29, 2010 6:50 PM
>> *To:* Alastair McKinstry
>> *Cc:* Rogers, Leah L.
>> *Subject:* Re: License for CDAT software
>>
>>  
>>
>> I'll have Leah Rogers get back to you after next week.
>>
>>  
>>
>> Best regards,
>>
>> Dean
>>
>>  
>>
>> On May 29, 2010, at 1:25 PM, Alastair McKinstry wrote:
>>
>>
>>
>> Hi Dean,
>>
>> Thanks for replying so quickly! I would be very happy if it can be
>> confirmed that CDAT is available
>> under the BSD license. From:
>> *http://*www2-pcmdi.llnl.gov/cdat/docs/cdat-license/?searchterm=None
>> *I was afraid that the "No commercialisation" clause would conflict
>> with the "Free distribution" clause
>> of the Debian (and Ubuntu) Free software guidelines:
>> http://*www.*debian.org/social_contract#guidelines
>>
>> If an appropriate legal person at LLNL can say they are happy that
>> CDAT is distributed with
>> Debian (and derivatives) as per the DFSG pointed to, then thats great
>>
>> Best regards
>> Alastair
>>
>> On 2010-05-29 19:13, Dean N. Williams wrote:
>>
>> Hi Alastair,
>>
>>  
>>
>>  CDAT is BSD licensed, so I don't understand your question. I cc'ed
>> our LLNL legal person to confirm this. 
>>
>>  
>>
>>  Also, I would like to thank you for including CDAT in the
>> distribution of Debian, and Ubuntu...
>>
>>  
>>
>> Best regards,
>>
>>  Dean
>>
>>  
>>
>> On May 29, 2010, at 6:13 AM, Alastair McKinstry wrote:
>>
>>

Processed: block 825988 with 826797

[Debian Bug Tracking System]

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

> block 825988 with 826797
Bug #825988 [pdf2htmlex] pdf2htmlex: FTBFS on s390x: pngquant readpng: unable 
to allocate image data
825988 was not blocked by any bugs.
825988 was not blocking any bugs.
Added blocking bug(s) of 825988: 826797
> thanks
Stopping processing here.

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

Bug#827302: v4l-utils: FTBFS: jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'

[Bill Allombert]

On Wed, Jun 15, 2016 at 02:09:05PM +0200, Gregor Jasny wrote:
> Hello Bill and Ondřej,
> 
> Do you know how to properly detect jpeg_mem_src presence in libjpeg(turbo)?
> 
> Since the transition to jpegturbo my package FTBFS:
> 
> On 14/06/16 20:42, Chris Lamb wrote:
> >  In file included from jpeg.c:28:0:
> >  jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'
> >   jpeg_mem_src (j_decompress_ptr cinfo, unsigned char * buffer,
> >   ^
> >  In file included from libv4lconvert-priv.h:31:0,
> >   from jpeg.c:26:
> >  /usr/include/jpeglib.h:923:14: note: previous declaration of 
> > 'jpeg_mem_src' was here
> >   EXTERN(void) jpeg_mem_src (j_decompress_ptr cinfo,
> >^
> 
> Would it make sense to change the check in the emulation layer [1] from
> 
> #if JPEG_LIB_VERSION < 80

As far as IJG jpeg  is converned, the above is correct.
I do not know for turbo.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#826712: im a little too late to the party

[alberto fuentes]

On Wed, Jun 15, 2016 at 2:21 PM, Luca Boccassi 
wrote:

> Wouldn't have made a difference, a package in non-free cannot block the
> migration of a package in the main archive.
> And we wouldn't want to block the migration of the kernel even if it
> would be possible.
>

Oh, I didnt check it and assume this was the package migrating and breaking

Thanks for your work!

Lets offer some of our crops to the ftp masters so this and the rest of the
nvidia drivers make it soon to the archive :)

Bug#827279: marked as done (libcpputest-dev: generated/CppUTestGeneratedConfig.h not installed, breaks reverse dependencies build)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 12:49:40 +
with message-id 
and subject line Bug#827279: fixed in cpputest 3.8-2
has caused the Debian Bug report #827279,
regarding libcpputest-dev: generated/CppUTestGeneratedConfig.h not installed, 
breaks reverse dependencies build
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.)


-- 
827279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcpputest-dev
Version: 3.8-1
Justification: renders package unusable
Severity: grave
Tags: patch

Dear Maintainer,

Since libcpputest-dev 3.8 generated/CppUTestGeneratedConfig.h is
generated at
build time and included by include/CppUTest/CppUTestGeneratedConfig.h
which is
included by include/CppUTest/CppUTestConfig.h,  but it is not installed,
causing a build failure for any project that includes
include/CppUTest/CppUTestGeneratedConfig.h.

I set the severity to grave to stop migration to testing since this bug
will
cause a build failure for almost any project using cpputest.

[  169s] In file included
from /usr/include/CppUTest/CppUTestConfig.h:32:0,
[  169s]  from /usr/include/CppUTest/TestHarness.h:31,
[  169s] /usr/include/CppUTest/CppUTestGeneratedConfig.h:45:47: fatal
error:
generated/CppUTestGeneratedConfig.h: No such file or directory
[  169s]  #include "generated/CppUTestGeneratedConfig.h"
[  169s]^
[  169s] compilation terminated.

The simple solution is to have libcpputest-dev install
generated/CppUTestGeneratedConfig.h in /usr/include/CppUTest. A simple
patch
for the install file is attached.

Thanks!

Kind regards,
Luca Boccassi

-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable'), (104, 'testing'), (103, 'unstable'), (102, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-0.bpo.2-amd64 (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: systemd (via /run/systemd/system)

-- no debconf information

From 49c5fe9b2cf90e7b021bf798f440cbc4321e87fa Mon Sep 17 00:00:00 2001
From: Luca Boccassi 
Date: Tue, 14 Jun 2016 14:15:59 +0100
Subject: [PATCH] Install generated config in libcpputest-dev

generated/CppUTestGeneratedConfig.h is generated at build time and
included by include/CppUTest/CppUTestGeneratedConfig.h which is
included by include/CppUTest/CppUTestConfig.h,  but it is not
installed, causing a build failure for any project that includes
include/CppUTest/CppUTestGeneratedConfig.h. Have libcpputest-dev
install it.
---
 debian/libcpputest-dev.install | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/libcpputest-dev.install b/debian/libcpputest-dev.install
index d088890..f59daff 100644
--- a/debian/libcpputest-dev.install
+++ b/debian/libcpputest-dev.install
@@ -1,4 +1,5 @@
 include/CppUTest usr/include/
 include/CppUTestExt usr/include/
+generated/CppUTestGeneratedConfig.h usr/include/CppUTest/generated
 usr/lib/*/*.a
 usr/lib/*/pkgconfig/cpputest.pc
-- 
2.1.4
--- End Message ---
--- Begin Message ---
Source: cpputest
Source-Version: 3.8-2

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated cpputest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Jun 2016 14:17:11 +0200
Source: cpputest
Binary: cpputest libcpputest-dev
Architecture: source
Version: 3.8-2
Distribution: unstable
Urgency: medium
Maintainer: Raphaël Hertzog 
Changed-By: Raphaël Hertzog 
Description:
 cpputest   - C/C++ based unit test framework — main package
 libcpputest-dev - C/C++ based unit test framework — headers and static 
libraries
Closes: 827279
Changes:
 cpputest (3.8-2) unstable; 

Bug#827374: gitlab: fails to install: Could not find gem 'addressable (~> 2.3.8)'

[Andreas Beckmann]

Package: gitlab
Version: 8.8.2+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package gitlab.
  Preparing to unpack .../gitlab_8.8.2+dfsg-4_all.deb ...
  Unpacking gitlab (8.8.2+dfsg-4) ...
  Setting up gitlab (8.8.2+dfsg-4) ...
  Creating/updating gitlab user account...
  adduser: Warning: The home directory `/var/lib/gitlab' does not belong to the 
user you are currently creating.
  Creating runtime directories for gitlab...
  Updating file permissions...
  Configuring hostname and email...
  Registering /etc/gitlab/gitlab.yml via ucf
  
  Creating config file /etc/gitlab/gitlab.yml with new version
  Registering /etc/gitlab/gitlab-debian.conf via ucf
  
  Creating config file /etc/gitlab/gitlab-debian.conf with new version
  
  Creating config file /etc/nginx/sites-available/localhost with new version
  Reloading nginx configuration...
  /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of reload.
  Create database if not present
  psql: FATAL:  database "gitlab_production" does not exist
  psql: FATAL:  role "gitlab" does not exist
  Create gitlab user with create database privillege...
  CREATE ROLE
  Make gitlab user owner of gitlab_production database...
  ALTER DATABASE
  Grant all privileges to gitlab user...
  GRANT
  CREATE EXTENSION
  Verifying we have all required libraries...
  Could not find gem 'addressable (~> 2.3.8)' in any of the gem sources 
listed in
  your Gemfile or available on this machine.
  dpkg: error processing package gitlab (--configure):
   subprocess installed post-installation script returned error exit status 7
  Errors were encountered while processing:
   gitlab


cheers,

Andreas


gitlab_8.8.2+dfsg-4.log.gz
Description: application/gzip

Processed: found 818764 in 1.2.0~rc2+dfsg-1, tagging 818764, fixed 818764 in 1.1.4+dfsg-5 ...

[Debian Bug Tracking System]

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

> # it is even worse in experimental: GCC 4.8
> found 818764 1.2.0~rc2+dfsg-1
Bug #818764 [starpu-contrib] starpu-contrib: non-standard gcc/g++ used for 
build (gcc-4.9)
There is no source info for the package 'starpu-contrib' at version 
'1.2.0~rc2+dfsg-1' with architecture ''
Unable to make a source version for version '1.2.0~rc2+dfsg-1'
Marked as found in versions 1.2.0~rc2+dfsg-1.
> tags 818764 =
Bug #818764 [starpu-contrib] starpu-contrib: non-standard gcc/g++ used for 
build (gcc-4.9)
Removed tag(s) sid and stretch.
> fixed 818764 1.1.4+dfsg-5
Bug #818764 [starpu-contrib] starpu-contrib: non-standard gcc/g++ used for 
build (gcc-4.9)
There is no source info for the package 'starpu-contrib' at version 
'1.1.4+dfsg-5' with architecture ''
Unable to make a source version for version '1.1.4+dfsg-5'
Marked as fixed in versions 1.1.4+dfsg-5.
> severity 818764 serious
Bug #818764 [starpu-contrib] starpu-contrib: non-standard gcc/g++ used for 
build (gcc-4.9)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#827302: v4l-utils: FTBFS: jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'

[Ondřej Surý]

Hi Gregor,

[removing Bill Allombert from Cc as he was not involved in the
transition to LJT]

$ grep -r MEM_SRCDST_SUPPORTED /usr/include
/usr/include/x86_64-linux-gnu/jconfig.h:#define MEM_SRCDST_SUPPORTED 1

so

#if JPEG_LIB_VERSION < 80 && !defined(MEM_SRCDST_SUPPORTED)

should be sufficient.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver

On Wed, Jun 15, 2016, at 14:09, Gregor Jasny wrote:
> Hello Bill and Ondřej,
> 
> Do you know how to properly detect jpeg_mem_src presence in
> libjpeg(turbo)?
> 
> Since the transition to jpegturbo my package FTBFS:
> 
> On 14/06/16 20:42, Chris Lamb wrote:
> >   In file included from jpeg.c:28:0:
> >   jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'
> >jpeg_mem_src (j_decompress_ptr cinfo, unsigned char * buffer,
> >^
> >   In file included from libv4lconvert-priv.h:31:0,
> >from jpeg.c:26:
> >   /usr/include/jpeglib.h:923:14: note: previous declaration of 
> > 'jpeg_mem_src' was here
> >EXTERN(void) jpeg_mem_src (j_decompress_ptr cinfo,
> > ^
> 
> Would it make sense to change the check in the emulation layer [1] from
> 
> #if JPEG_LIB_VERSION < 80
> 
> to
> 
> #if JPEG_LIB_VERSION < 80 && !defined(MEM_SRCDST_SUPPORTED)
> 
> or should I add a check during autoconf?
> 
> Thanks,
> Gregor
> 
> [1] 
> https://git.linuxtv.org/v4l-utils.git/tree/lib/libv4lconvert/jpeg_memsrcdest.h

Bug#826712: im a little too late to the party

[Luca Boccassi]

On Wed, 2016-06-15 at 13:20 +0200, alberto fuentes wrote:
> Control: severity -1 grave
> 
> 
> im a little too late to the party since this already migrated to testing
> and now im affected.
> 
> New version is in new queue yet :(
> 
> thanks for working on this!

Wouldn't have made a difference, a package in non-free cannot block the
migration of a package in the main archive.
And we wouldn't want to block the migration of the kernel even if it
would be possible.

There is nothing we can do, the packages are in the NEW queue, so it's
up to the FTP masters.

https://ftp-master.debian.org/new.html

Kind regards,
Luca Boccassi


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

Bug#827302: v4l-utils: FTBFS: jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'

[Gregor Jasny]

Hello Bill and Ondřej,

Do you know how to properly detect jpeg_mem_src presence in libjpeg(turbo)?

Since the transition to jpegturbo my package FTBFS:

On 14/06/16 20:42, Chris Lamb wrote:

  In file included from jpeg.c:28:0:
  jpeg_memsrcdest.h:6:1: error: conflicting types for 'jpeg_mem_src'
   jpeg_mem_src (j_decompress_ptr cinfo, unsigned char * buffer,
   ^
  In file included from libv4lconvert-priv.h:31:0,
   from jpeg.c:26:
  /usr/include/jpeglib.h:923:14: note: previous declaration of 'jpeg_mem_src' 
was here
   EXTERN(void) jpeg_mem_src (j_decompress_ptr cinfo,
^


Would it make sense to change the check in the emulation layer [1] from

#if JPEG_LIB_VERSION < 80

to

#if JPEG_LIB_VERSION < 80 && !defined(MEM_SRCDST_SUPPORTED)

or should I add a check during autoconf?

Thanks,
Gregor

[1] 
https://git.linuxtv.org/v4l-utils.git/tree/lib/libv4lconvert/jpeg_memsrcdest.h

Processed: RM: python3.4 -- RoQA; obsolete; superseded by python3.5

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 802889 820186
Bug #827366 [ftp.debian.org] RM: python3.4 -- RoQA; obsolete; superseded by 
python3.5
827366 was not blocked by any bugs.
827366 was not blocking any bugs.
Added blocking bug(s) of 827366: 820186 and 802889

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

Processed: Re: Bug#802889: please don't depend on all python3 versions

[Debian Bug Tracking System]

Processing control commands:

> tag -1 -moreinfo
Bug #802889 [python3-coverage] please don't depend on all python3 versions
Removed tag(s) moreinfo.
> severity -1 serious
Bug #802889 [python3-coverage] please don't depend on all python3 versions
Severity set to 'serious' from 'important'

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

Processed: im a little too late to the party

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #826712 [nvidia-legacy-304xx-kernel-dkms] [nvidia-legacy-304xx-kernel-dkms] 
Does not build for kernel 4.6.0-1, -rt (also 4.4.0-1-rt)
Severity set to 'grave' from 'normal'

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

Processed: fix src version

[Debian Bug Tracking System]

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

> found 821675 0.9.1-15
Bug #821675 {Done: Sven Eckelmann } [src:exactimage] 
src:exactimage: PHP 7.0 Transition
Marked as found in versions exactimage/0.9.1-15.
> thanks
Stopping processing here.

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

Bug#771829: marked as done (python-googlecloudapis: build-depend on python-setuptools and python3-setuptools)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 11:04:12 +
with message-id 
and subject line Bug#771829: fixed in python-googlecloudapis 0.9.30+debian1-1.1
has caused the Debian Bug report #771829,
regarding python-googlecloudapis: build-depend on python-setuptools and 
python3-setuptools
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.)


-- 
771829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-googlecloudapis
Version: 0.9.30+debian1-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch

Dear Maintainer,

This package's setup.py imports setuptools, but it doesn't build-depend on 
python-setuptools or python3-setuptools, which causes an FTBFS in Ubuntu. 
Please explicitly build-depend on these packages.

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

  * Build-depend on python-setuptools and python3-setuptools to fix FTBFS.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-24-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru python-googlecloudapis-0.9.30+debian1/debian/control python-googlecloudapis-0.9.30+debian1/debian/control
--- python-googlecloudapis-0.9.30+debian1/debian/control	2014-08-29 14:23:53.0 -0400
+++ python-googlecloudapis-0.9.30+debian1/debian/control	2014-12-02 12:48:32.0 -0500
@@ -9,10 +9,12 @@
python-oauth2client,
python-pbr,
python-protorpc-standalone,
+   python-setuptools,
python3-all (>= 3.2),
python3-oauth2client,
python3-pbr,
-   python3-protorpc-standalone
+   python3-protorpc-standalone,
+   python3-setuptools
 Standards-Version: 3.9.5
 Vcs-Browser: https://anonscm.debian.org/gitweb/?p=cloud/python-googlecloudapis.git;a=summary
 Vcs-Git: git://anonscm.debian.org/cloud/python-googlecloudapis.git
--- End Message ---
--- Begin Message ---
Source: python-googlecloudapis
Source-Version: 0.9.30+debian1-1.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated python-googlecloudapis 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Jun 2016 08:42:38 +
Source: python-googlecloudapis
Binary: python-googlecloudapis python3-googlecloudapis
Architecture: source
Version: 0.9.30+debian1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cloud 
Changed-By: Mattia Rizzolo 
Description:
 python-googlecloudapis - collection of utilities for client-side tools - 
Python 2.x
 python3-googlecloudapis - collection of utilities for client-side tools - 
Python 3.x
Closes: 771829 771831 810043
Changes:
 python-googlecloudapis (0.9.30+debian1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Matthias Klose ]
   * Fix timestamps to accept build in Launchpad.  Closes: #771831
 .
   [ Mattia Rizzolo ]
   * Rebuild for python3.4 → python3.5 transition.
   * Change Maintainer from DPMT to Debian Cloud.
   * Use HTTPS in Vcs-Git.
   * Add python(3)-setuptools to Build-Depends.  Closes: #771829
   * Fix python3-googlecloudapis description.  Closes: #810043
   * Fix order of paragraph in d/copyright to comply with DEP-5
Checksums-Sha1:
 9e6a95df34c95ba49ef700f52e76810b2cc59965 2447 
python-googlecloudapis_0.9.30+debian1-1.1.dsc
 5374e62b9a59e7133efca211bb26bd23a158260f 4612 
python-googlecloudapis_0.9.30+debian1-1.1.debian.tar.xz

Bug#826379: marked as done (codeblocks: incompatibility between GPL and RSA md5 license makes package non-distributable)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 10:58:05 +
with message-id 
and subject line Bug#826379: fixed in codeblocks 16.01+dfsg-2
has caused the Debian Bug report #826379,
regarding codeblocks: incompatibility between GPL and RSA md5 license makes 
package non-distributable
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.)


-- 
826379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: codeblocks
Version: 16.01+dfsg-1
Severity: serious
X-Debbugs-CC: g...@debian.org

Codeblocks is licensed under GPL v3, but some files in the source
tarball contain code that is licensed as per the terms of RSA Data
Security, Inc.'s MD5 Message Digest Algorithm; this license is as
follows:

src/plugins/contrib/source_exporter/wxPdfDocument/src/pdfencrypt.cpp
src/plugins/contrib/source_exporter/wxPdfDocument/src/pdfxml.cpp

/*
 **
 ** Copyright (C) 1990, RSA Data Security, Inc. All rights reserved. **
 **  **
 ** License to copy and use this software is granted provided that   **
 ** it is identified as the "RSA Data Security, Inc. MD5 Message **
 ** Digest Algorithm" in all material mentioning or referencing this **
 ** software or this function.   **
 **  **
 ** License is also granted to make and use derivative works **
 ** provided that such works are identified as "derived from the RSA **
 ** Data Security, Inc. MD5 Message Digest Algorithm" in all **
 ** material mentioning or referencing the derived work. **
 **  **
 ** RSA Data Security, Inc. makes no representations concerning  **
 ** either the merchantability of this software or the suitability   **
 ** of this software for any particular purpose.  It is provided "as **
 ** is" without express or implied warranty of any kind. **
 **  **
 ** These notices must be retained in any copies of any part of this **
 ** documentation and/or software.   **
 **
 */

This license is problematic for codeblocks because while it is free /
DFSG-compatible, it contains an advertising clause akin to the
original / 4-clause BSD license that renders it incompatible with the
GPL, which is what the majority of codeblocks' codebase is licensed
under. The GNU project has documented this incompatibility at [1].
There's also some discussion of this issue on debian-legal [2].

The RSA md5 license only applies to code used by the exporter plugin
in codeblocks, so we can avoid shipping a non-distributable codeblocks
package merely by not including that plugin (no DFSG violation here,
no need to repack source tarball). This is what I plan to do until
upstream replaces the current md5 implementation with one that does
not happen to be GPL-incompatible.

Regards,
Vincent

[1] http://www.gnu.org/licenses/license-list.html#OriginalBSD
[2] https://lists.debian.org/debian-legal/2016/05/msg00011.html
--- End Message ---
--- Begin Message ---
Source: codeblocks
Source-Version: 16.01+dfsg-2

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

Debian distribution maintenance software
pp.
Vincent Cheng  (supplier of updated codeblocks package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Jun 2016 01:41:09 PDT
Source: codeblocks
Binary: codeblocks codeblocks-common libcodeblocks0 codeblocks-dbg 
codeblocks-contrib codeblocks-dev libwxsmithlib0 libwxsmithlib-dev
Architecture: source all
Version: 16.01+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: David Paleino 

Bug#821675: marked as done (src:exactimage: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 11:00:07 +
with message-id 
and subject line Bug#821675: fixed in exactimage 0.9.1-16
has caused the Debian Bug report #821675,
regarding src:exactimage: 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.)


-- 
821675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:exactimage
Version: 0.9.1-15+b1
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 exactimage package currently build-depends on php5 php5-dev .

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: exactimage -- 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

iQJ8BAEBCgBmBQJXFUtcXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHHWUQAI80ym1YBgz7QhaCuxEifWdo
veNbdqNoWH9ZegWG9wPvc+ApbU1efob2rUXxCetv/g9rt3MlZHAtz7NBfzlgrOQX
wHmiiH7V1PlgzYtFUgAyTOA5mhvg1oWIL2PzsJKQP2JwInMcs2ZsUkJCCMr9sfnR
GR79aAC2W1XQOXTbe5o2YSLhHeZuQm+BCqsjb85FZxCfYsl+ANta+SDZAhx+Zyui

Bug#826968: mercurial-buildpackage rebuild issue

[Emilio Pozuelo Monfort]

On Fri, 10 Jun 2016 17:56:13 + (UTC) Gianfranco Costamagna
 wrote:
> source: mercurial-buildpackage
> severity: serious
> version: 0.10-1
> tags: patch
> 
> Hi Darren,
> I had to patch the package on Ubuntu, because you have a parsechangelog that 
> doesn't take care of rebuilds, NMUs, or whatever.
> 
> In Ubuntu it seems fine now, the following patch
> diff -Nru mercurial-buildpackage-0.10.1/debian/changelog 
> mercurial-buildpackage-0.10.1ubuntu1/debian/changelog
> --- mercurial-buildpackage-0.10.1/debian/changelog  2014-10-28 
> 03:27:29.0 +0100
> +++ mercurial-buildpackage-0.10.1ubuntu1/debian/changelog   2016-06-10 
> 19:43:53.0 +0200
> @@ -1,3 +1,10 @@
> +mercurial-buildpackage (0.10.1ubuntu1) yakkety; urgency=medium
> +
> +  * Rebuild against libneko2.
> +  * Strip the "build*" and "ubuntu*" from changelog
> +
> + -- Gianfranco Costamagna   Tue, 07 Jun 2016 
> 16:23:35 +0200
> +
> mercurial-buildpackage (0.10.1) unstable; urgency=low
> 
> * Fix ‘class not found’ FTBFS. (Closes: #719405)
> diff -Nru mercurial-buildpackage-0.10.1/debian/rules 
> mercurial-buildpackage-0.10.1ubuntu1/debian/rules
> --- mercurial-buildpackage-0.10.1/debian/rules  2012-02-25 20:10:58.0 
> +0100
> +++ mercurial-buildpackage-0.10.1ubuntu1/debian/rules   2016-06-07 
> 20:11:01.0 +0200
> @@ -2,7 +2,7 @@
> # debian/rules for mercurial-buildpackage.
> 
> PACKAGE := $(shell dpkg-parsechangelog | head -1 | cut -c9-)
> -CHANGELOG := $(shell dpkg-parsechangelog | sed -e '/^Version: /! d; s/^.* 
> //')
> +CHANGELOG := $(shell dpkg-parsechangelog | sed -e '/^Version: /! d; s/^.* 
> //' | sed '-e s/build.*//' | sed '-e s/ubuntu.*//')
> 
> clean:
> dh_testdir
> 
> 
> 
> of course something more appropriate is needed, but this should become 
> shortly an RC bug in Debian too.
> 
> Can you please give it a look?
> 
> the failure is:
> 
> ./macro-expand < MercurialImportDsc.man > mercurial-importdsc.1
> ./macro-expand < MercurialPristineTar.man > mercurial-pristinetar.1
> ./macro-expand < MercurialPort.man > mercurial-port.1
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> touch build-stamp
> [ "0.10.1build1" = 0.10.1 ]
> debian/rules:22: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 1
> dpkg-buildpackage: error: debian/rules build gave error exit status 2

This broke in Debian because of binNMUs:

[ "0.10.1+b1" = 0.10.1 ]
debian/rules:22: recipe for target 'build-arch' failed

What is that check needed for anyway?

Emilio

Bug#827349: viva: FTBFS: Parse error at "BOOST_JOIN"

[Emilio Pozuelo Monfort]

Package: viva
Version: 1.1+git20150820.1a3d1f680f-1
Severity: serious

Your package failed to build everywhere:

[ 60%] Generating src/vv_treemap/moc_VTApplication.cxx
cd 
/«BUILDDIR»/viva-1.1+git20150820.1a3d1f680f/obj-x86_64-linux-gnu/src/vv_treemap 
&& /usr/lib/x86_64-linux-gnu/qt4/bin/moc 
@/«BUILDDIR»/viva-1.1+git20150820.1a3d1f680f/obj-x86_64-linux-gnu/src/vv_treemap/moc_VTApplication.cxx_parameters
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at 
"BOOST_JOIN"
CMakeFiles/vv_treemap.dir/build.make:65: recipe for target 
'src/vv_treemap/moc_VTApplication.cxx' failed
make[3]: *** [src/vv_treemap/moc_VTApplication.cxx] Error 1

Logs at https://buildd.debian.org/status/package.php?p=viva

Emilio

Bug#821548: PHP 7.0 transition - PHP bindings removed and uploaded to DELAYED/2

[Ondřej Surý]

Dear maintainers,

in an effort to finally finish PHP 7.0 transition started in April, I
removed PHP bindings from swig as it doesn't look like swig will support
PHP 7.0 anytime soon and also from the remaining packages using swig to
build PHP bindings.

I uploaded these fixed packages to DELAYED/2 parallel to writing this
email.

Please let me know if you intend to proceed differently, so we can
coordinate the upload and finish the transition in timely manner.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

Bug#814862: fix for qt4 Conflicts

[Ian Haywood]

Ok, I have patched the detection routine in Gambas so if both Qt4 and 
Qt5 are present then Qt5 is loaded.
This means the IDE will actually work (given qt4-webkit is gone, and the 
IDE needs webkit to display the online documentation), but the Conflicts 
isn't required anymore,


I have tested the build and checked the IDE runs.

Gianfranco, can you take a look at this in alioth git and upload the 
package if you are happy?


Thanks

Ian Haywood

Processed: Re: Bug#790102: swig choke on -Wdate-time, makes packages FTBFS

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #790102 [swig] swig choke on -Wdate-time, makes packages FTBFS
Severity set to 'important' from 'serious'

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

Bug#790102: swig choke on -Wdate-time, makes packages FTBFS

[Ondřej Surý]

Control: severity -1 important

I don't think that severity serious is justifiable in swig directly.
While it would be nice if swig didn't choke on -Wdate-time, it's not
unreasonable for it to fail when unknown options are passed to it.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

Processed: bug 818219 is forwarded to https://bugs.kde.org/show_bug.cgi?id=364231

[Debian Bug Tracking System]

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

> forwarded 818219 https://bugs.kde.org/show_bug.cgi?id=364231
Bug #818219 [src:digikam] digikam: Jasper removal
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=364231'.
> thanks
Stopping processing here.

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

Bug#767905: kwallet: after upgrade from jessie to stretch kwalletmanager doesn't see my old wallets

[Martin Steigerwald]

On Montag, 13. Juni 2016 20:41:18 CEST Paul Gevers wrote:
> Package: kwalletmanager
> Version: 4:16.04.1-1
> Followup-For: Bug #767905
> Control: severity -1 serious
> 
> I just upgraded my system from jessie (with only jessie-backports as
> additional archive) to stretch and now, after reboot, my old wallets aren't
> available. Would be good if the new kwalletmanager would pick up my old
> wallets automatically.

As I upgraded a migrator was run, which migrated all KDE SC 4 wallets to the 
KF/Plasma 5 one. Yet, it can´t run completely without user interaction if you 
used master password(s) to encrypt your wallet with. So you need to enter your 
old master password(s).

I bet you can have it have another go at it by setting alreadyMigrated to 
false

martin@merkaba:~/.config> grep Migr kwalletrc
[Migration]
alreadyMigrated=true

and restarting KWallet. You may need to restart your Plasma session in order 
to do that, or restart the kwallet service manually (but I didn´t find it in 
background services kcm).

There might be another way to trigger the migration again by DBUS or what have 
you, but I didn´t find it easily.

[…]
-- 
Martin

Bug#827330: marked as done (golang-github-gorilla-mux-dev: missing Breaks+Replaces against golang-mux-dev)

[Debian Bug Tracking System]

Your message dated Wed, 15 Jun 2016 06:18:51 +
with message-id 
and subject line Bug#827330: fixed in golang-github-gorilla-mux 1.1-2
has caused the Debian Bug report #827330,
regarding golang-github-gorilla-mux-dev: missing Breaks+Replaces against 
golang-mux-dev
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.)


-- 
827330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-gorilla-mux-dev
Version: 1.1-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 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package golang-github-gorilla-mux-dev.
  Preparing to unpack .../golang-github-gorilla-mux-dev_1.1-1_all.deb ...
  Unpacking golang-github-gorilla-mux-dev (1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-github-gorilla-mux-dev_1.1-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/gocode/src/github.com/gorilla/mux/bench_test.go', which is also in 
package golang-mux-dev 0.0~git20140505.1.136d54f-2
  Errors were encountered while processing:
   /var/cache/apt/archives/golang-github-gorilla-mux-dev_1.1-1_all.deb


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: golang-github-gorilla-mux
Source-Version: 1.1-2

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated 
golang-github-gorilla-mux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 15 Jun 2016 16:08:52 +1000
Source: golang-github-gorilla-mux
Binary: golang-github-gorilla-mux-dev
Architecture: source all
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: pkg-go 
Changed-By: Dmitry Smirnov 
Description:
 golang-github-gorilla-mux-dev - powerful URL router and dispatcher for golang
Closes: 827330
Changes:
 golang-github-gorilla-mux (1.1-2) unstable; urgency=medium
 .
   * Team upload
   * Fixed Breaks/Replaces (Closes: #827330).
   * Vcs-Git URL to HTTPS.
   * Removed "Built-Using" field from -dev package.
Checksums-Sha1:
 7f0a90b9e6d13e9636d5f9ec5cc3766e7f9e83d6 2190 
golang-github-gorilla-mux_1.1-2.dsc
 6bba54ccbf44e90e3e617800b5f20016fd457351 4988 
golang-github-gorilla-mux_1.1-2.debian.tar.xz
 1d2901052bdd23f831842eb14535a601107a964a 26020 
golang-github-gorilla-mux-dev_1.1-2_all.deb
Checksums-Sha256:
 e3cea54005437c7e44a1028bf645c63af826afb70f0fb9aa540d7518a4d456a7 2190 
golang-github-gorilla-mux_1.1-2.dsc
 6c7aa6a45eefce728f1cc3a62bf99b60faab0de34d9858b96112be652762fbaa 4988 
golang-github-gorilla-mux_1.1-2.debian.tar.xz
 94ee105b2b6d90ef4e74225960be05c5e877336a18b2cdb67a2a2d175687fdae 26020 
golang-github-gorilla-mux-dev_1.1-2_all.deb
Files:
 2d0a5b83ed3ed09a14b48b090a8eface 2190 devel extra 
golang-github-gorilla-mux_1.1-2.dsc
 1071b1919d7ffec98ddaecaee1ad2215 4988 devel extra 
golang-github-gorilla-mux_1.1-2.debian.tar.xz
 cb928ee052e47e37b7befbea20cb2ad9 26020 devel extra 
golang-github-gorilla-mux-dev_1.1-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXYPGNAAoJEFK2u9lTlo0buSQQAMgnBEvFo/gQdHfo7mtyugBi
Wp0WSgJB0l7aZsMNl+q1pDHyLDnVu4gWC6aMcsfJiznXyIt+dukDiricB2F/9sRq
EWE74tLm5ilBk0UDhWuH1iZtovgfoo5HIZ5toYxR+wp0uR8Ti4XBsTGHqxXmopiA
JOpdSrIl/eBDFY5t6s8eb2CGUJ1NJFk+/GTcYK8Zs4O0nzMPiqKFpkxcgs9hoS32
HSIghZ+g/Xk+Pc4mV2sP6qLFZvot25aNU6o68LGYEalVmWlFON57kLj56JQoA0rD
liYHXl1HRscjW3oyq8HAtRF3KDHYDhlQOLgjWB7xcVTJG1Y5gbR8CA7Gkp9OmYY+

Processed: Pending fixes for bugs in the golang-github-gorilla-mux package

[Debian Bug Tracking System]

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

> tag 827330 + pending
Bug #827330 [golang-github-gorilla-mux-dev] golang-github-gorilla-mux-dev: 
missing Breaks+Replaces against golang-mux-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#827330: Pending fixes for bugs in the golang-github-gorilla-mux package

[pkg-go-maintainers]

tag 827330 + pending
thanks

Some bugs in the golang-github-gorilla-mux package are closed in
revision dc309ae5e7da68ea20d3de4d327e9d2ede0cc3c3 in branch 'master'
by Dmitry Smirnov

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-gorilla-mux.git/commit/?id=dc309ae

Commit message:

Fixed Breaks/Replaces (Closes: #827330)