Bug#813125: [pkg-php-pear] Bug#813125: Bug#813125: php-proxy-manager 2.0.0* has a dependency on a new PHP API PackageVersions

[Nish Aravamudan]

On 30.01.2016 [09:10:58 -0400], David Prévot wrote:
> Le 29/01/2016 18:45, Nish Aravamudan a écrit :
> > On 29.01.2016 [18:31:11 -0400], David Prévot wrote:
> >> Le 29/01/2016 12:39, Nishanth Aravamudan a écrit :

> >>> […] it has a dependency that prevents it
> >>> from successfully packaging currently. The upstream code has introduced
> >>> a new dependency on https://github.com/Ocramius/PackageVersions, which I
> >>> am guessing would need to be packaged as a new package, i.e.,
> >>> php-package-versions.
> >>
> >> I instead patched the package to not use this new dependency.
> > 
> > Ok, I'll look at your version when it's in the VCS tomorrow.
> 
> 
> http://anonscm.debian.org/cgit/pkg-php/php-proxy-manager.git/commit/?id=599baa2548cfc9be768f7436c9457796acad2094
> 

I was finally able to get to this, and I see build failures using that
base (due to phpcs issues):

phpcs --standard=PSR2 ./src/

FILE:
0.0/src/ProxyManager/Exception/InvalidProxiedClassException.php
--
FOUND 2 ERRORS AFFECTING 2 LINES
--
 54 | ERROR | [x] Multi-line function call not indented correctly;
|   | expected 20 spaces but found 24
 59 | ERROR | [x] Multi-line function call not indented correctly;
|   | expected 24 spaces but found 28
--
PHPCBF CAN FIX THE 2 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--


FILE:
0/src/ProxyManager/ProxyGenerator/LazyLoadingGhostGenerator.php
--
FOUND 1 ERROR AFFECTING 1 LINE
--
 150 | ERROR | [x] Multi-line function call not indented correctly;
 |   | expected 12 spaces but found 16
--
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--


FILE:
...-2.0.0/src/ProxyManager/ProxyGenerator/RemoteObjectGenerator.php
--
FOUND 1 ERROR AFFECTING 1 LINE
--
 75 | ERROR | [x] Multi-line function call not indented correctly;
|   | expected 20 spaces but found 24
--
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--


FILE:
.../src/ProxyManager/ProxyGenerator/Assertion/CanProxyAssertion.php
--
FOUND 1 ERROR AFFECTING 1 LINE
--
 90 | ERROR | [x] Multi-line function call not indented correctly;
|   | expected 12 spaces but found 16
--
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--


FILE:
0/src/ProxyManager/ProxyGenerator/Util/ProxiedMethodsFilter.php
--
FOUND 1 ERROR AFFECTING 1 LINE
--
 83 | ERROR | [x] Multi-line function call not indented correctly;
|   | expected 12 spaces but found 16
--
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--


FILE:
...anager-2.0.0/src/ProxyManager/ProxyGenerator/Util/Properties.php
--
FOUND 1 ERROR AFFECTING 1 LINE
--
 59 | ERROR | [x] Multi-line function call not indented correctly;
|   | expected 20 spaces but found 24
--
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
--


FILE:
...rc/ProxyManager/ProxyGenerator/Util/UnsetPropertiesGenerator.php
--
FOUND 1 ERROR AFFECTING 1 LINE
--
 104 | ERROR | [x] Multi-line function call not indented correctly;
 |   | expected 20 spaces but found 24
--
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY

Bug#812861: marked as done (ssh key upload is not working)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 19:05:01 +
with message-id 
and subject line Bug#812861: fixed in gitlab 8.4.3+dfsg-1
has caused the Debian Bug report #812861,
regarding ssh key upload is not working
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.)


-- 
812861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

package: gitlab
version: 8.4.0+dfsg~rc2-1
severity: important

moving this https://gitlab.com/debian-ruby/TaskTracker/issues/58 to
bts as gitlab is in the archive now.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWqKLkAAoJEM4fnGdFEsIqvM0P/jddPdcpGMZMyQwIN1o5H2+n
+RT+nDlN3yCeDFLNSYt+c5OlRmhYFSBqLCPMZ0IoU2HbGPzdQeNm5O8csMh2MUeW
vYm7mHYFOrx7g318ROtKBjENYBm3ShMlKmuN0rTbpXQDW9WwoX41xJsBm0uLB97P
MvaKeJaLAyfvEeAmlLPLnwJNdWVrL+3qCR8ZwDCXokbRaEzHSGwxIDMRc973Rneo
EO/XTTxvW4mNKfI9WsdYWWbDtrAEcGv6DF4G3xhkbtsDmNrZl0nptc4mK9qQbTTM
GzbhzxooE2Fw/vGQ5/Gnzj7tkQJF1JpN5Ct4yzWb8+pNyYUAsekktASe0mIz8ZD2
ZvhfR397IQkjBEXfsfii68GCzsyGbPGzyP+1d3gCqDrnr+DdYa3y3j1JBPYIrqSa
mDpGrj6ealAgygWIKUjF7tcJK3aEEe32HrE9L7wTJauQSSWCwT1MbhYe04V6KTsi
ADgl5dd4tfHj/SWqpXxC3cLmYHy6E7gSpj1tLjAGSz2UcoMn7e4xlqHBbFK/U5PR
1+Znx05qyvDEi5Xb3ZhW1F0hwvsQ+E9qTwmtkSzCMY+YsKwnXJLgz77ugaUtc8W2
tq+r7GMspYsdW8s4gS7lxiRhRtT+XJt8+lr223M50ooHMdcl6sbiFoybsFRzLqOU
aXfHxse7Pu8vGy0Auh5h
=uvbm
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 8.4.3+dfsg-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated gitlab package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Feb 2016 23:39:34 +0530
Source: gitlab
Binary: gitlab
Architecture: source all
Version: 8.4.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code
Closes: 812861 813770 813807
Changes:
 gitlab (8.4.3+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
   * Refresh patches (rails version is in sync)
   * Configure ssl for nginx if selected
   * Use letsencrypt certificate paths if selected
   * Add git as dependency (Closes: #813807)
   * SSH key upload is working (Closes: #812861)
   * Configure gitlab_url as workwround (Closes: #813770 )
Checksums-Sha1:
 f0e26b3bbc7fc261375996ffeadd1be9dbc119ee 2058 gitlab_8.4.3+dfsg-1.dsc
 46df20cdaf8c6fba49cfb20a6b60741ec6c93762 12214011 gitlab_8.4.3+dfsg.orig.tar.gz
 6003648efdccc328de8c328f4fc53f8bcd214bfd 31084 
gitlab_8.4.3+dfsg-1.debian.tar.xz
 01b5a61e2cc7ecf28cdced09de336511bb4d97a7 11470484 gitlab_8.4.3+dfsg-1_all.deb
Checksums-Sha256:
 a2f92c4c7fe98a8d31c88cc379aabdf93cbb466f2a2e1b6ef83adddcaa745b46 2058 
gitlab_8.4.3+dfsg-1.dsc
 91e28c1d8c5a628d21a45afb4f5d91f955d2c580f5e1a4ec8ffa703de447f3e9 12214011 
gitlab_8.4.3+dfsg.orig.tar.gz
 f81b70cd1858283a46dc70c8a9efc958b0dd42d972abf5d65bbe72cfc6e56779 31084 
gitlab_8.4.3+dfsg-1.debian.tar.xz
 d7211a4aa752c39e779b59b74695f56ce3c747f4bb71ec90cdcdf412590cae60 11470484 
gitlab_8.4.3+dfsg-1_all.deb
Files:
 915d968a10b1506b86f0ec87db224b7e 2058 ruby optional gitlab_8.4.3+dfsg-1.dsc
 f3e527687718d52925401bf657d113b0 12214011 ruby optional 
gitlab_8.4.3+dfsg.orig.tar.gz
 a80d7d546430587626a2cff14805dc46 31084 ruby optional 
gitlab_8.4.3+dfsg-1.debian.tar.xz
 8fc94fc62f6ce1c8d5dcce940eac80a6 11470484 ruby optional 
gitlab_8.4.3+dfsg-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWujMKAAoJEM4fnGdFEsIqsa0P/RFZUgTjTQA3diItcOQoRNl7
BHEn5aQ2l4dV4gA334faLIn+/TsvGGbla9WR9nnmghDHGS+Zk/9GGRPzOTh3yjnD
QIW+Kvk/U83ATxNQWrJIN84eUy1IG+DHc4G+DnX/jPMthY8HXFiY8F/IHcTeK908
RRBH0cjjSl0FVQbAtXqNihJ9UJFhdbKn+iWXMtSs71sTcqrwyrkNTf86Q4JstMZs

Bug#812750: wine: Gecko integration is broken

[Rhonda D'Vine]

   Hey,

* Jens Reyer  [2016-02-09 19:49:43 CET]:
> In Wine we depend on libwine-gecko-xxx before it's added to the archive,
> knowing/hoping/assuming that it will be added to the archive, which has
> always been true for Debian stable releases, but not for all
> intermittent Gecko versions that were needed in between (maintainer is
> in both cases the Wine packaging team, unfortunately afaik every new
> Gecko upstream release takes a lot of work, especially for reevaluating
> the copyrights).

 Thanks for explaining the situation at hand, that helps better with
understanding how this situation happened. :)

> This has the benefit of having the dependency already ready, once Gecko
> is added to the archive, without the need to reupload Wine.

 Unfortunately unsatisfyable recommends are a policy violation though,
and even while I understand the sentiments of not wanting to have to
reupload wine to add it, I don't see a way around this.

> It may also show people more easily where work needs to be done
> (increasing the people who help from 0 to 0).

 Yeah, that's always the issue; unfortunately I have different areas in
which I put my effort and I only stumbled upon it in the context of
backports.

> Rhonda, do you see any flexibility in interpreting the policy for this
> case? If not, I'll do something like

 Unfortunately I don't see it, it's a clear must requirement and there
for very specific reasons, to keep main untainted from non-free
packages.

 So yes, seperating the issue of that it might help to where to find
gecko to install it personally, and lowering the recommends to suggests
could definitely be tackled seperately.

 Thanks for the headsup,
Rhonda
-- 
Fühlst du dich mutlos, fass endlich Mut, los  |
Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los|

Bug#812750: [pkg-wine-party] Bug#812750: wine: Gecko integration is broken

[Rhonda D'Vine]

   Hi,

* Austin English  [2016-02-09 17:45:02 CET]:
> On Feb 9, 2016 8:39 PM, austinengl...@gmail.com wrote:
> > On Feb 9, 2016 8:25 PM, "Rhonda D'Vine"  wrote:
> > > > >   Hi!
> > > > >
> > > > > * Ralf Jung  [2016-01-26 10:57:49 CET]:
> > > > > > From all I can tell, the Gecko integration is entirely broken. There
> > > > > > is no wine-gecko packaged in Debian
> > > > > > (the recommendation of libwine-gecko-2.40 is unsatisfiable),
> > >^
> > > >
> > > > mingw64 is in main, what package are you referring to?
> > >
> > >  No clue why you mention mingw64, I am to the package I did quote in my
> > > mail and this bugreport is about, libwine-gecko-2.40.
> >
> > I'm asking what recommended package is the problem. It's not on
> > packages.d.o and not specified in the mail as far as I can tell.

 Erm, it is both on packages.debian.org/wine32 and also in this
bugreport mentioned multiple times.  So let me write it a third and
three time in this very email:
libwine-gecko-2.40 libwine-gecko-2.40 libwine-gecko-2.40

> Or is it that libwine-gecko-2.40 isn't in main that is the problem? I
> thought the problem was a gecko recommend.

 Maybe you should read what is written instead of guessing.
libwine-gecko-2.40 is not only not in main but not even nowhere in the
archive.

 So long,
Rhonda
-- 
Fühlst du dich mutlos, fass endlich Mut, los  |
Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los|

Bug#813125: phpcs upstream issue [was: php-proxy-manager 2.0.0* has a dependency on a new PHP API PackageVersions]

[David Prévot]

Hi Nish,

Le 09/02/2016 15:05, Nish Aravamudan a écrit :

> I was finally able to get to this, and I see build failures using that
> base (due to phpcs issues):
> 
> phpcs --standard=PSR2 ./src/
[…]
> I can fix this up on my end by putting in a staged build, but it seems
> like something needs to be fixed still?

That’s probably caused by a new issue in php-codesniffer 2.5.1, e.g.,

https://github.com/squizlabs/PHP_CodeSniffer/issues/876

FWIW, the build runs fine with php-codesniffer 2.5.1 (not in the
archive, but I can push my update to the VCS if you wish), but
php-codesniffer 2.5.1 does break other packages build, so I’d prefer to
see an upstream php-codesniffer (and php-proxy-manager) fix before
uploading it (unless I push both to experimental for the time being,
would that be useful?).

Regards

David



signature.asc
Description: OpenPGP digital signature

Processed: Forward 814071 to upstream

[Debian Bug Tracking System]

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

> forwarded 814071 https://github.com/pytroll/pyorbital/issues/8
Bug #814071 [src:pyorbital] pyorbital: FTBFS: AssertionError: 
60.371433482573323 != 60.37143348255783
Set Bug forwarded-to-address to 'https://github.com/pytroll/pyorbital/issues/8'.
> thanks
Stopping processing here.

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

Bug#813125: [pkg-php-pear] Bug#813125: phpcs upstream issue [was: php-proxy-manager 2.0.0* has a dependency on a new PHP API PackageVersions]

[David Prévot]

Hi Nish,

>> On 09.02.2016 [15:17:17 -0400], David Prévot wrote:
>>> Le 09/02/2016 15:05, Nish Aravamudan a écrit :
>>>
 I was finally able to get to this, and I see build failures using that
 base (due to phpcs issues):
> […]
 I can fix this up on my end by putting in a staged build, but it seems
 like something needs to be fixed still?
>>>
>>> That’s probably caused by a new issue in php-codesniffer 2.5.1, e.g.,
>>>
>>> https://github.com/squizlabs/PHP_CodeSniffer/issues/876
>>
>> Did you mean an issue with 2.5.0?
>
> No. I believed 2.5.1 introduced an indent issue, and that
> php-proxy-manager was (probably automatically, with phpcbf) fixed to use
> the new (broken) phpcs behavior. I just run phpcbf/2.5.0 and now believe
> that I was wrong, so I’ll have a closer look at what broke with
> phpcs/2.5.1, and may upload the updated packages, or file/document a
> proper upstream issue.

Filed as https://github.com/squizlabs/PHP_CodeSniffer/issues/889

I guess nothing is stopping us to upload both php-codesniffer 2.5.1 and
php-proxy-manager 2.0.0 to experimental. I’ll upload a recent
php-codesniffer to unstable once the aforementioned upstream issue will be
fixed (one way or the other ;).

Regards

David

Processed: Re: Bug#788257: Info received and FILED only (SSH packet_write_wait: Connection to ...: Broken pipe / Marvell 88E8071 PCI-E Gigabit Ethernet)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 linux 3.16.7-ckt9-3~deb8u1
Bug #788257 [ssh] SSH packet_write_wait: Connection to ...: Broken pipe / 
Marvell 88E8071 PCI-E Gigabit Ethernet
Bug reassigned from package 'ssh' to 'linux'.
No longer marked as found in versions openssh/1:6.7p1-5.
Ignoring request to alter fixed versions of bug #788257 to the same values 
previously set
Bug #788257 [linux] SSH packet_write_wait: Connection to ...: Broken pipe / 
Marvell 88E8071 PCI-E Gigabit Ethernet
There is no source info for the package 'linux' at version 
'3.16.7-ckt9-3~deb8u1' with architecture ''
Unable to make a source version for version '3.16.7-ckt9-3~deb8u1'
Marked as found in versions 3.16.7-ckt9-3~deb8u1.
> retitle -1 sky2 NIC driver freezes the system (Marvell 0x436B / 88E8071)
Bug #788257 [linux] SSH packet_write_wait: Connection to ...: Broken pipe / 
Marvell 88E8071 PCI-E Gigabit Ethernet
Changed Bug title to 'sky2 NIC driver freezes the system (Marvell 0x436B / 
88E8071)' from 'SSH packet_write_wait: Connection to ...: Broken pipe / Marvell 
88E8071 PCI-E Gigabit Ethernet'

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

Bug#788257: Info received and FILED only (SSH packet_write_wait: Connection to ...: Broken pipe / Marvell 88E8071 PCI-E Gigabit Ethernet)

[Sebastian Andrzej Siewior]

Control: reassign -1 linux 3.16.7-ckt9-3~deb8u1
Control: retitle -1 sky2 NIC driver freezes the system (Marvell 0x436B / 
88E8071)

I hereby reassing the bug to the linux package since it has nothing to
do with openssh. Based on the last feedback from the submitter he
replaced the NIC and the problem is gone is it is looks like the sky2
driver. I assume it is the sky2 driver due to
|git grep 88E8071
|drivers/net/ethernet/marvell/sky2.c:{ PCI_DEVICE(PCI_VENDOR_ID_MARVELL, 
0x436B) }, /* 88E8071 */

I kept the severity as-is and leave to the maintainer in charge to deal
with it as appropriate.

Sebastian

Bug#812750: wine: Gecko integration is broken

[Jens Reyer]

Hi

In Wine we depend on libwine-gecko-xxx before it's added to the archive,
knowing/hoping/assuming that it will be added to the archive, which has
always been true for Debian stable releases, but not for all
intermittent Gecko versions that were needed in between (maintainer is
in both cases the Wine packaging team, unfortunately afaik every new
Gecko upstream release takes a lot of work, especially for reevaluating
the copyrights).

Stephen, can you shed some light on the main problem(s) blocking
frequent Gecko releases? Let's say, there's some chance that I help.

This has the benefit of having the dependency already ready, once Gecko
is added to the archive, without the need to reupload Wine.

It may also show people more easily where work needs to be done
(increasing the people who help from 0 to 0).


Rhonda, do you see any flexibility in interpreting the policy for this
case? If not, I'll do something like

clone -1 -2
retitle -1 wine: doesn't find Gecko in documented place
severity -1 important
retitle -2 wine: recommends package not in main

and commit a fix for -2. Of course this doesn't solve the main problem
that the current libwine-gecko (2.40 for current wine, and 2.44 for
current wine-development package) is not available in the archive.

Greets
jre

Bug#812750: [pkg-wine-party] Bug#812750: wine: Gecko integration is broken

[Austin English]

On Feb 9, 2016 11:08 PM, "Rhonda D'Vine"  wrote:
>
>Hi,
>
> * Austin English  [2016-02-09 17:45:02 CET]:
> > On Feb 9, 2016 8:39 PM, austinengl...@gmail.com wrote:
> > > On Feb 9, 2016 8:25 PM, "Rhonda D'Vine"  wrote:
> > > > > >   Hi!
> > > > > >
> > > > > > * Ralf Jung  [2016-01-26 10:57:49 CET]:
> > > > > > > From all I can tell, the Gecko integration is entirely
broken. There
> > > > > > > is no wine-gecko packaged in Debian
> > > > > > > (the recommendation of libwine-gecko-2.40 is unsatisfiable),
> > > >^
> > > > >
> > > > > mingw64 is in main, what package are you referring to?
> > > >
> > > >  No clue why you mention mingw64, I am to the package I did quote
in my
> > > > mail and this bugreport is about, libwine-gecko-2.40.
> > >
> > > I'm asking what recommended package is the problem. It's not on
> > > packages.d.o and not specified in the mail as far as I can tell.
>
>  Erm, it is both on packages.debian.org/wine32 and also in this
> bugreport mentioned multiple times.  So let me write it a third and
> three time in this very email:
> libwine-gecko-2.40 libwine-gecko-2.40 libwine-gecko-2.40
>
> > Or is it that libwine-gecko-2.40 isn't in main that is the problem? I
> > thought the problem was a gecko recommend.
>
>  Maybe you should read what is written instead of guessing.
> libwine-gecko-2.40 is not only not in main but not even nowhere in the
> archive.
>
>  So long,
> Rhonda
> --
> Fühlst du dich mutlos, fass endlich Mut, los  |
> Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
> Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf
Anfang
> Fühlst du dich haltlos, such Halt und lass los|

Yes, I got it now. Being condescending was neither necessary nor helpful.

Guess I'll go back to contributing upsream/elsewhere instead of trying to
help Debian get a more functional Wine.

Good luck.

Bug#812750: wine: Gecko integration is broken

[Stephen Kitt]

Hi Jens,

On Tue, 9 Feb 2016 19:49:43 +0100, Jens Reyer  wrote:
> Stephen, can you shed some light on the main problem(s) blocking
> frequent Gecko releases? Let's say, there's some chance that I help.

There are two issues:
* wine-gecko typically requires a git snapshot of mingw-w64, so supporting
  its build in Debian (with the aim of stable releases) requires identifying
  and porting the required patches to the current mingw-w64 release (upstream
  are quite helpful with this)
* updating the licensing information for each new wine-gecko release is
  extraordinarily time-consuming, on the order of 150-200h per release (and
  even then I miss issues) – TBH I've stalled on this, I'm thinking of
  working on a new approach where I just package the files that actually get
  used for the build and worry about the licensing information once I've
  figured that out

Ideally we could piggy-back on the iceweasel licensing information, since the
upstream code is pretty much the same, but that doesn't get updated all that
often so it isn't necessarily all that accurate. (Take that with a pinch of
salt though, I haven't checked the situation recently.)

Regards,

Stephen


pgp29I9YNFDr_.pgp
Description: OpenPGP digital signature

Bug#814207: lambdabot: FTBFS (missing build-dependency libghc-lambdabot-haskell-plugins-dev (>= 5.0.3)

[Ralf Treinen]

Source: lambdabot   
Version: 5.0.3-3
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

lambdabot FTBFS on all architectures since it has a build-dependency on

libghc-lambdabot-reference-plugins-dev (>= 5.0.3)

However the version of that package in sid is only 5.0.1-3+b1.

-Ralf.

Bug#814213: wmaker: FTBFS: Error: program option '--with-aix-soname' is not in the documentation './INSTALL-WMAKER'

[Doug Torrance]

On 02/09/2016 03:59 AM, Chris Lamb wrote:
> Source: wmaker
> Version: 0.95.7-3
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> wmaker fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   make  check-local
>   make[4]: Entering directory 
> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>   ./script/check-cmdline-options-doc.sh \
>   --program "./configure" --text-doc "./INSTALL-WMAKER" \
>   --ignore-prg 'with-PACKAGE,without-PACKAGE # only template names from 
> Autoconf' \
>   --ignore-prg 'program-prefix,program-suffix,program-transform-name # in 
> INSTALL' \
>   --ignore-prg 'version,quiet,srcdir,build,host,cache-file,no-create # in 
> INSTALL' \
>   --ignore-prg 'enable-silent-rules,disable-silent-rules # should be in 
> INSTALL' \
>   --ignore-prg 'enable-dependency-tracking,disable-dependency-tracking # 
> in INSTALL' \
>   --ignore-prg 'enable-shared,enable-static # should be in INSTALL' \
>   --ignore-prg 'disable-option-checking,enable-fast-install # should be 
> in INSTALL' \
>   --ignore-prg 'disable-libtool-lock,with-pic,with-gnu-ld,with-sysroot # 
> for libtool' \
>   --ignore-prg 'runstatedir #new in autoconf 2.70, backported in Debian' \
>   --ignore-prg 'with-x # no use, it would not work without X'
>   Error: program option '--with-aix-soname' is not in the documentation 
> './INSTALL-WMAKER'
>   Makefile:951: recipe for target 'configure-documentation' failed
>   make[4]: *** [configure-documentation] Error 1
>   make[4]: Leaving directory 
> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>   Makefile:766: recipe for target 'check-am' failed
>   make[3]: *** [check-am] Error 2
>   make[3]: Leaving directory 
> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>   Makefile:478: recipe for target 'check-recursive' failed
>   make[2]: *** [check-recursive] Error 1
>   make[2]: Leaving directory 
> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>   Makefile:768: recipe for target 'check' failed
>   make[1]: *** [check] Error 2
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>   dh_auto_test: make -j9 check returned exit code 2
>   debian/rules:30: recipe for target 'build' failed
>   make: *** [build] Error 2
> 
>   [..]

Thanks for your report!

This is because libtool 2.4.6 was just uploaded to sid on Sunday [1].
>From [2]:
  * m4/ltoptions.m4 (_LT_WITH_AIX_SONAME): New. Provides
  commandline option --with-aix-soname=aix|svr4|both. Declares
  $shared_archive_member_spec as libtool variable.

[1] https://packages.qa.debian.org/libt/libtool/news/20160207T173014Z.html
[2] 
http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=8fa719e81dba828d3e22cd59f825fac456c20809

Bug#807251: marked as done (libdebug-client-perl: FTBFS: tests hang with current Term::ReadLine::Gnu)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:09:16 +
with message-id 
and subject line Bug#814006: Removed package(s) from unstable
has caused the Debian Bug report #807251,
regarding libdebug-client-perl: FTBFS: tests hang with current 
Term::ReadLine::Gnu
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.)


-- 
807251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdebug-client-perl
Version: 0.29-2
Severity: serious
Tags: sid

This package fails to build on current sid. The tests
hang in t/07-initialize.t after
  ok 1 - initialize with prams

This broke with libterm-readline-gnu-perl 1.28-1. Debug::Client
creates a network server that a 'perl -d' process configured with
PERLDB_OPTS='RemotePort=host:port' can connect to. With the new
Term::ReadLine::Gnu, the perl debugger no longer outputs its prompt and
other messages to the socket, so Debug::Client can't interact with it
and hangs forever waiting.

The package build-depends on libterm-readline-gnu-perl, so the build
fails. I suppose a workaround would be to build-conflict on it instead.

Without libterm-readline-gnu-perl installed, with netcat listening
for connections in place of Debug::Client, we see everything working
correctly:

(window 1)
 % nc -l -p 65400
(window 2)
 % PERLDB_OPTS="RemotePort=127.0.0.1:65400" perl -d -e 'print "Hello, world!\n"'
(window 1)
 Loading DB routines from perl5db.pl version 1.44
 Editor support available.
 
 Enter h or 'h h' for help, or 'man perldebug' for more help.
 
 main::(-e:1):   print "Hello, world!\n"
 DB<1> c
 Debugged program terminated.  Use q to quit or R to restart,
 use o inhibit_exit to avoid stopping after program termination,
 h q, h R or h o to get additional info.
 DB<1> q
(window 2)
 Hello, world!

With libterm-readline-gnu-perl_1.28-1, we no longer get the DB prompts
or the 'Debugged program terminated' messages, but typing blindly works.

(window 1)
 nc -l -p 65400
(window 2)
 % PERLDB_OPTS="RemotePort=127.0.0.1:65400" perl -d -e 'print "Hello, world!\n"'
(window 1)
 Loading DB routines from perl5db.pl version 1.44
 Editor support available.
 
 Enter h or 'h h' for help, or 'man perldebug' for more help.
 
 main::(-e:1):   print "Hello, world!\n"
 c
 q
(window 2)
 Hello, world!

The upstream version that broke this is Term-ReadLine-Gnu-1.26.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Version: 0.29-2+rm

Dear submitter,

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

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

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

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

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

Bug#790335: marked as done (libdebug-client-perl: FTBFS with perl 5.22: test failure)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:09:16 +
with message-id 
and subject line Bug#814006: Removed package(s) from unstable
has caused the Debian Bug report #790335,
regarding libdebug-client-perl: FTBFS with perl 5.22: test failure
to be marked as done.

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

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


-- 
790335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdebug-client-perl
Version: 0.29-2
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition
Tags: sid stretch upstream

This package FTBFS with perl 5.22 (currently in experimental):

#   Failed test 'y (0) $line = 1'
#   at t/24-y_zero.t line 34.
# Compared $data->[0]
#got : 'Not nested deeply enough'
# expect : '$line = 1'
# Not nested deeply enough

#   Failed test 'y (0) $line = 2'
#   at t/24-y_zero.t line 34.
# Compared $data->[0]
#got : 'Not nested deeply enough'
# expect : '$line = 2'
# Not nested deeply enough

#   Failed test 'y (0) $line = 3'
#   at t/24-y_zero.t line 34.
# Compared $data->[0]
#got : 'Not nested deeply enough'
# expect : '$line = 3'
# Not nested deeply enough
# Looks like you failed 3 tests of 3.
t/24-y_zero.t . 
1..3
not ok 1 - y (0) $line = 1
not ok 2 - y (0) $line = 2
not ok 3 - y (0) $line = 3
Dubious, test returned 3 (wstat 768, 0x300)
Failed 3/3 subtests 

This bug will become release critical nearer the time of the perl 5.22
migration, expected during the (northern hemisphere) summer.

Cheers,
Dominic.
--- End Message ---
--- Begin Message ---
Version: 0.29-2+rm

Dear submitter,

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

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

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

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

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

Bug#809419: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:15:04 +
with message-id 
and subject line Bug#814105: Removed package(s) from unstable
has caused the Debian Bug report #809419,
regarding Useless in Debian
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.)


-- 
809419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-html-table
Version: 1.8.3-1
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

Upstream hasn’t been active in over five years, didn’t respond to the
bug filed either (even with patch), so it may be considered dead
upstream.
The package is only used by php-structures-datagrid-renderer-htmltable,
but this package is going away (#783419), so there is a priori little
point to ship it in the next stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.8.3-1+rm

Dear submitter,

as the package php-html-table has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#804904: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:17:49 +
with message-id 
and subject line Bug#814108: Removed package(s) from unstable
has caused the Debian Bug report #804904,
regarding Useless in Debian
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.)


-- 
804904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-structures-datagrid-renderer-htmltable
Version: 0.1.6-1
Severity: minor

Hi Cyril,

The Homepage set in php-structures-datagrid-renderer-htmltable should
point to the following URL:
http://pear.php.net/package/Structures_DataGrid_Renderer_HTMLTable/

I can’t help noticing in that page that the upstream package is not
maintained, that the Debian package does not have any reverse
(build-)dependencies, and (thus) have a very low popcon, do you still
use/need it in the archive?

If you want to keep the package in the archive, I’d encourage you to
maintain it within the Debian PHP PEAR Maintainers team
( X-Debbug-CC).

Regards

David

P.-S.: I stumbled upon this package while looking at the php-html-common
status (also unmaintained upstream with low popcon), that has only one
reverse dependency you also maintain: php-html-table (also unmaintained
upstream with a very low popcon), that only has this package as a
reverse dependency. I was then wondering if there was still a point
keeping all those in the Debian archive (if there is, I’ll also
encourage you to maintain php-html-table in the Debian PHP PEAR
Maintainers team).


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 0.1.6-1+rm

Dear submitter,

as the package php-structures-datagrid-renderer-pager has just been removed 
from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#813995: flash-kernel: writes to nand without being aware of bad blocks

[Uwe Kleine-König]

Hello *,

On 02/07/2016 12:34 PM, Ian Campbell wrote:
> So far I see no evidence for the claim that flashcp should not be used
> for writing to NAND devices in either its --help or its source (it has
> no man page AFAICS).
> 
> Having a tool in Debian called "flashcp" which can (according to this
> report, I haven't checked this myself) destroy some classes of flash
> device with no warning is a clear problem irrespective of flash
> -kernel's use of that tool.
> 
> At the very least flashcp should either abort when used on NAND devices
> or should be renamed norwrite (cf. nandwrite) but ideally it would Just
> Work properly when used on a nand device.

"Work properly" might not be well defined here. If flashcp should be
taught to write to nand, how should it behave? Like nandwrite with -p?
What about -m? Probably without -o.

I would guess that renaming flashcp to (say) norwrite isn't an option
for upstream. I think the naming was coined before nand flash was widely
adopted. So I still think the best thing to do here is to teach
flash-kernel about nand chips and let it use nandwrite then. Adding a
note to flashcp -h that it is only supposed to work on nor and let it
fail for nand also sounds right.

> mtd-utils maintainer(s), please let me know if this is either wontfix
> or if the fix is going to take some time, in either case I will
> workaround flashcp in flash-kernel (either permanently or temporarily
> respectively).
> 
> I suppose it is also possible that this is a bug in the underlying
> /dev/mtdN and/or mtdblockN device or in the h/w specific driver at the
> bottom of the stack?

No, mtdblockN exposes bad blocks by design:


http://linux-kernel.2935.n7.nabble.com/PATCH-Make-the-mtdblock-read-write-skip-the-bad-nand-sector-td756524.html

Best regards
Uwe

Bug#798901: marked as done (padre: FTBFS with perl 5.22: test failure)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:08:18 +
with message-id 
and subject line Bug#814005: Removed package(s) from unstable
has caused the Debian Bug report #798901,
regarding padre: FTBFS with perl 5.22: test failure
to be marked as done.

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

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


-- 
798901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: padre
Version: 1.00+dfsg-4
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition
Tags: sid stretch

This package FTBFS with perl 5.22.0-2:

#   Failed test 'text of error message'
#   at t/82_plugin_manager.t line 104.
#   'Padre::Plugin::A - Crashed while loading: Global symbol 
"$syntax_error" requires explicit package name (did you forget to declare "my 
$syntax_error"?) at 
/«BUILDDIR»/padre-1.00+dfsg/t/files/plugins/Padre/Plugin/A.pm line 7.
# Compilation failed in require at (eval 2535) line 1.
# BEGIN failed--compilation aborted at (eval 2535) line 1.
# '
# doesn't match '(?^:^(?^:.*) Global symbol "\$syntax_error" requires 
explicit package name at)'
# Looks like you failed 1 test of 29.
t/82_plugin_manager.t .. 

Cheers,
Dominic.
--- End Message ---
--- Begin Message ---
Version: 1.00+dfsg-5+rm

Dear submitter,

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

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

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

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

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

Bug#814073: tzdata: FTBFS: Error: Unable to access jarfile /usr/lib/jvm/default-java//jre/lib/javazic.jar

[Aurelien Jarno]

reassign 814073 openjdk-8-jre-headless
retitle 814073 openjdk-8-jre-headless doesn't provide javazic.jar
affect 814073 tzdata
thanks

On 2016-02-08 09:14, Chris Lamb wrote:
> Source: tzdata
> Version: 2016a-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,
> 
> tzdata fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   # Generate a java version
>   /usr/lib/jvm/default-java//bin/java -jar 
> /usr/lib/jvm/default-java//jre/lib/javazic.jar -V 2016a -d 
> /home/lamby/temp/cdt.20160208085405.3qp2pN3cIl/tzdata-2016a/tzgen-java africa 
> antarctica asia australasia europe northamerica southamerica etcetera factory 
> backward systemv pacificnew gmt jdk11_backward
>   Error: Unable to access jarfile 
> /usr/lib/jvm/default-java//jre/lib/javazic.jar
>   debian/rules:53: recipe for target 'build-indep-stamp' failed
>   make: *** [build-indep-stamp] Error 1
> 
>   [..]

The problem is that the default java has recently been switched to
openjdk-8, which doesn't provide javazic.jar. As such we can't build
tzdata-java anymore.

Aurelien

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

Bug#722918: marked as done (php-spreadsheet-excel-writer: depends on non-existent php-ole)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:20:35 +
with message-id 
and subject line Bug#814111: Removed package(s) from unstable
has caused the Debian Bug report #722918,
regarding php-spreadsheet-excel-writer: depends on non-existent php-ole
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.)


-- 
722918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-spreadsheet-excel-writer
Version: 0.9.3-1
Severity: serious

Hi,

php-spreadsheet-excel-writer depends on php-ole, but there's no such
package in the archive.

Regards,

Adam
--- End Message ---
--- Begin Message ---
Version: 0.9.3-1+rm

Dear submitter,

as the package php-spreadsheet-excel-writer has just been removed from the 
Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#804903: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:19:51 +
with message-id 
and subject line Bug#814107: Removed package(s) from unstable
has caused the Debian Bug report #804903,
regarding Useless in Debian
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.)


-- 
804903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-structures-datagrid-renderer-htmltable
Version: 0.1.6-1
Severity: minor

Hi Cyril,

The Homepage set in php-structures-datagrid-renderer-htmltable should
point to the following URL:
http://pear.php.net/package/Structures_DataGrid_Renderer_HTMLTable/

I can’t help noticing in that page that the upstream package is not
maintained, that the Debian package does not have any reverse
(build-)dependencies, and (thus) have a very low popcon, do you still
use/need it in the archive?

If you want to keep the package in the archive, I’d encourage you to
maintain it within the Debian PHP PEAR Maintainers team
( X-Debbug-CC).

Regards

David

P.-S.: I stumbled upon this package while looking at the php-html-common
status (also unmaintained upstream with low popcon), that has only one
reverse dependency you also maintain: php-html-table (also unmaintained
upstream with a very low popcon), that only has this package as a
reverse dependency. I was then wondering if there was still a point
keeping all those in the Debian archive (if there is, I’ll also
encourage you to maintain php-html-table in the Debian PHP PEAR
Maintainers team).


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 0.2.2~dev1-1+rm

Dear submitter,

as the package php-structures-datagrid-datasource-array has just been removed 
from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#809425: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:26:51 +
with message-id 
and subject line Bug#814121: Removed package(s) from unstable
has caused the Debian Bug report #809425,
regarding Useless in Debian
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.)


-- 
809425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-html-template-it
Version: 1:1.3.0-3
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

php-html-template-it is not used by any Debian package currently, and
hasn’t seen any upstream activity for over five years. It has a low (and
shrinking) popcon, so probably isn’t of any use anymore. There is a
priori little point to ship it in the next stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1:1.3.0-3+rm

Dear submitter,

as the package php-html-template-it has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#812644: marked as done (jenkins-remoting: FTBFS - artifact asm:asm-all:jar:3.x has not been downloaded)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:24:37 +
with message-id 
and subject line Bug#814118: Removed package(s) from unstable
has caused the Debian Bug report #812644,
regarding jenkins-remoting: FTBFS - artifact asm:asm-all:jar:3.x has not been 
downloaded
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.)


-- 
812644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jenkins-remoting
Version: 2.45-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building Jenkins remoting layer 2.45
[INFO] 
[WARNING] The POM for asm:asm-all:jar:3.x is missing, no dependency information 
available
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 1.887 s
[INFO] Finished at: 2016-01-24T20:32:31+00:00
[INFO] Final Memory: 23M/1963M
[INFO] 
[ERROR] Failed to execute goal on project remoting: Could not resolve 
dependencies for project org.jenkins-ci.main:remoting:jar:2.45: Cannot access 
repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/) in offline mode and 
the artifact asm:asm-all:jar:3.x has not been downloaded from it before. -> 
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
/usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
make: *** [mvn-build] Error 1


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


jenkins-remoting-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 2.45-1+rm

Dear submitter,

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

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

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

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

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

Bug#814211: rr: FTBFS: CMake Error at CMakeLists.txt:110 (message): Couldn't find gdb.

[Chris Lamb]

Source: rr
Version: 4.1.0-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,

rr fails to build from source in unstable/amd64:

  [..]

  dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var returned 
exit code 1
  debian/rules:20: recipe for target 'build' failed
  make: *** [build] Error 255

  [..]

The full build log is attached.


Regards,

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

Bug#814209: xmlbeans: FTBFS: SchemaCompiler.java:221: error: cannot access TypeStoreUser

[Chris Lamb]

Source: xmlbeans
Version: 2.6.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,

xmlbeans fails to build from source in unstable/amd64:

  [..]

  
  xmlcomp.classes:
  [mkdir] Created dir: 
/home/lamby/temp/cdt.20160209093732.zwOyCh46W5/xmlbeans-2.6.0/build/classes/xmlcomp
  [javac] 
/home/lamby/temp/cdt.20160209093732.zwOyCh46W5/xmlbeans-2.6.0/build.xml:682: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
  [javac] Compiling 21 source files to 
/home/lamby/temp/cdt.20160209093732.zwOyCh46W5/xmlbeans-2.6.0/build/classes/xmlcomp
  [javac] warning: [options] bootstrap class path not set in conjunction 
with -source 1.4
  [javac] warning: [options] source value 1.4 is obsolete and will be 
removed in a future release
  [javac] warning: [options] target value 1.4 is obsolete and will be 
removed in a future release
  [javac] warning: [options] To suppress warnings about obsolete options, 
use -Xlint:-options.
  [javac] 
/home/lamby/temp/cdt.20160209093732.zwOyCh46W5/xmlbeans-2.6.0/src/xmlcomp/org/apache/xmlbeans/impl/tool/SchemaCompiler.java:221:
 error: cannot access TypeStoreUser
  [javac] new 
HashSet(Arrays.asList(XmlListImpl.split_list(allowmdef;
  [javac]  ^
  [javac]   class file for org.apache.xmlbeans.impl.values.TypeStoreUser 
not found
  [javac] Note: Some input files use or override a deprecated API.
  [javac] Note: Recompile with -Xlint:deprecation for details.
  [javac] 1 error
  [javac] 4 warnings
  
  BUILD FAILED
  /home/lamby/temp/cdt.20160209093732.zwOyCh46W5/xmlbeans-2.6.0/build.xml:682: 
Compile failed; see the compiler error output for details.
  
  Total time: 12 seconds
  /usr/share/cdbs/1/class/ant.mk:40: recipe for target 'debian/stamp-ant-build' 
failed
  make: *** [debian/stamp-ant-build] Error 1

  [..]

The full build log is attached.


Regards,

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


xmlbeans.2.6.0-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#814210: python-pbh5tools: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Chris Lamb]

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

Dear Maintainer,

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

  [..]
  
  ==
  ERROR: 
test_cmph5lib_CmpH5Sort.TestGetOverlappingRanges.test_get_overlapping_ranges
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
  self.test(*self.arg)
File 
"/home/lamby/temp/cdt.20160209093420.uLfTkBHk0Y/python-pbh5tools-0.8.0+dfsg/tests/test_cmph5lib_CmpH5Sort.py",
 line 98, in test_get_overlapping_ranges
  ar = generate_positions(i, j)
File 
"/home/lamby/temp/cdt.20160209093420.uLfTkBHk0Y/python-pbh5tools-0.8.0+dfsg/tests/test_cmph5lib_CmpH5Sort.py",
 line 18, in generate_positions
  tS = random.randint(0, size, NN)
File "mtrand.pyx", line 1266, in mtrand.RandomState.randint 
(numpy/random/mtrand/mtrand.c:14344)
File "mtrand.pyx", line 1267, in mtrand.RandomState.randint 
(numpy/random/mtrand/mtrand.c:14299)
File "mtrand.pyx", line 749, in mtrand._rand_int64 
(numpy/random/mtrand/mtrand.c:9900)
  TypeError: 'float' object cannot be interpreted as an index
  
  --
  Ran 10 tests in 1.770s
  
  FAILED (errors=1)
  Makefile:20: recipe for target 'test' failed
  make[2]: *** [test] Error 123
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160209093420.uLfTkBHk0Y/python-pbh5tools-0.8.0+dfsg'
  E: pybuild pybuild:274: test: plugin custom failed with: exit code=2: 
PATH=/home/lamby/temp/cdt.20160209093420.uLfTkBHk0Y/python-pbh5tools-0.8.0+dfsg/build/scripts-2.7:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
 /usr/bin/make test
  dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 --dir . 
returned exit code 13
  debian/rules:25: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 25
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160209093420.uLfTkBHk0Y/python-pbh5tools-0.8.0+dfsg'
  debian/rules:11: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-pbh5tools.0.8.0+dfsg-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#814213: wmaker: FTBFS: Error: program option '--with-aix-soname' is not in the documentation './INSTALL-WMAKER'

[Chris Lamb]

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

Dear Maintainer,

wmaker fails to build from source in unstable/amd64:

  [..]

  make  check-local
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
  ./script/check-cmdline-options-doc.sh \
--program "./configure" --text-doc "./INSTALL-WMAKER" \
--ignore-prg 'with-PACKAGE,without-PACKAGE # only template names from 
Autoconf' \
--ignore-prg 'program-prefix,program-suffix,program-transform-name # in 
INSTALL' \
--ignore-prg 'version,quiet,srcdir,build,host,cache-file,no-create # in 
INSTALL' \
--ignore-prg 'enable-silent-rules,disable-silent-rules # should be in 
INSTALL' \
--ignore-prg 'enable-dependency-tracking,disable-dependency-tracking # 
in INSTALL' \
--ignore-prg 'enable-shared,enable-static # should be in INSTALL' \
--ignore-prg 'disable-option-checking,enable-fast-install # should be 
in INSTALL' \
--ignore-prg 'disable-libtool-lock,with-pic,with-gnu-ld,with-sysroot # 
for libtool' \
--ignore-prg 'runstatedir #new in autoconf 2.70, backported in Debian' \
--ignore-prg 'with-x # no use, it would not work without X'
  Error: program option '--with-aix-soname' is not in the documentation 
'./INSTALL-WMAKER'
  Makefile:951: recipe for target 'configure-documentation' failed
  make[4]: *** [configure-documentation] Error 1
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
  Makefile:766: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
  Makefile:478: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
  Makefile:768: recipe for target 'check' failed
  make[1]: *** [check] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
  dh_auto_test: make -j9 check returned exit code 2
  debian/rules:30: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


wmaker.0.95.7-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#814212: wikidiff2: FTBFS: cp: cannot stat 'modules/*': No such file or directory

[Chris Lamb]

Source: wikidiff2
Version: 1.2+git03ea59f-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,

wikidiff2 fails to build from source in unstable/amd64:

  [..]

   fakeroot debian/rules binary
  dh binary
 dh_testroot
 dh_prep
 dh_installdirs
 debian/rules override_dh_auto_install
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f'
  
INSTALL_ROOT=/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/debian/php-wikidiff2
 make install
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f'
  /bin/bash 
/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/libtool 
--mode=compile g++  -I. 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f 
-DPHP_ATOM_INC 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/include
 -I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/main 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f 
-I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM 
-I/usr/include/php5/Zend -I/usr/include/php5/ext 
-I/usr/include/php5/ext/date/lib  -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_CONFIG_H  -Wno-write-strings -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-write-strings   -c 
/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/php_wikidiff2.cpp
 -o php_wikidiff2.lo 
  /bin/bash 
/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/libtool 
--mode=compile g++  -I. 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f 
-DPHP_ATOM_INC 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/include
 -I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/main 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f 
-I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM 
-I/usr/include/php5/Zend -I/usr/include/php5/ext 
-I/usr/include/php5/ext/date/lib  -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_CONFIG_H  -Wno-write-strings -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-write-strings   -c 
/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/Wikidiff2.cpp
 -o Wikidiff2.lo 
  /bin/bash 
/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/libtool 
--mode=compile g++  -I. 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f 
-DPHP_ATOM_INC 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/include
 -I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/main 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f 
-I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM 
-I/usr/include/php5/Zend -I/usr/include/php5/ext 
-I/usr/include/php5/ext/date/lib  -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_CONFIG_H  -Wno-write-strings -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-write-strings   -c 
/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/TableDiff.cpp
 -o TableDiff.lo 
  /bin/bash 
/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/libtool 
--mode=compile g++  -I. 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f 
-DPHP_ATOM_INC 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/include
 -I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/main 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f 
-I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM 
-I/usr/include/php5/Zend -I/usr/include/php5/ext 
-I/usr/include/php5/ext/date/lib  -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_CONFIG_H  -Wno-write-strings -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-write-strings   -c 
/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/InlineDiff.cpp
 -o InlineDiff.lo 
  /bin/bash 
/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/libtool 
--mode=link cc -DPHP_ATOM_INC 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/include
 -I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f/main 
-I/home/lamby/temp/cdt.20160209093555.dFyEsCBR1Y/wikidiff2-1.2+git03ea59f 
-I/usr/include/php5 -I/usr/include/php5/main -I/usr/include/php5/TSRM 
-I/usr/include/php5/Zend -I/usr/include/php5/ext 
-I/usr/include/php5/ext/date/lib  -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_CONFIG_H  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -o wikidiff2.la -export-dynamic 
-avoid-version -prefer-pic -module -rpath 

Bug#814152: [libkscreenlocker5] Conflict with plasma-workspace

[Rares Marian]

On Mon, 8 Feb 2016 19:28:37 + (UTC) Franz Schrober 
 wrote:

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

> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Preparing to unpack .../kde-config-screenlocker_5.5.4-1_amd64.deb ...
> Unpacking kde-config-screenlocker (5.5.4-1) ...
> dpkg: error processing archive 
/var/cache/apt/archives/kde-config-screenlocker_5.5.4-1_amd64.deb 
(--unpack):
> trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qt5/plugins/screenlocker_kcm.so', which is 
also in package plasma-workspace 4:5.4.3-1

> Processing triggers for libc-bin (2.21-7) ...
>
>

I can confirm that there is no conflict with plasma-workspace 5.5.4-1.

Bug#800255: marked as done (manpages-posix: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 10:43:16 +
with message-id 
and subject line Bug#800255: fixed in manpages-posix 2013a-1
has caused the Debian Bug report #800255,
regarding manpages-posix: Please migrate a supported debhelper compat level
to be marked as done.

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

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


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

Hi,

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

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

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

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

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: manpages-posix
Source-Version: 2013a-1

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

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

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated 
manpages-posix 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: Tue, 09 Feb 2016 10:04:01 +0100
Source: manpages-posix
Binary: manpages-posix manpages-posix-dev
Architecture: source all
Version: 2013a-1
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Francesco Paolo Lovergine 
Description:
 manpages-posix - Manual pages about using POSIX system
 manpages-posix-dev - Manual pages about using a POSIX system for development
Closes: 520162 522292 539989 622918 705032 736824 800255
Changes:
 manpages-posix (2013a-1) unstable; urgency=medium
 .
   [ Ilias Tsitsimpis ]
   * New upstream release
 (Closes: #520162, #522292, #539989, #622918, #705032, #736824)
   * Change versioning schema.
 Since kernel v3.0, the POSIX man-pages are no longer shipped alongside
 the rest of the kernel man-pages and have been versioned as "2013-a".
   * Convert source package to '3.0 (quilt)' format
   * Migrate to debhelper compat level 9 (Closes: #800255)
   * Bump Standards-Version to 3.9.7
   * Convert d/copyright to DEP-5 and update its entries
   * Cleanup d/rules file
   * Cleanup/Update installation script
 - Fix manpage-section-mismatch lintian warning
 - Fix package-contains-timestamped-gzip lintian warning
   * Remove d/readme since the URL is invalid
   * Add d/watch file
   * Add homepage field in d/control file
   * Override manpage-has-errors-from-man lintian warning.
 We are not allowed to modify the manpages, so disable the
 lintian warnings.
 .
   [ Francesco Paolo Lovergine ]
   * Ready for unstable
Checksums-Sha1:
 8ede0a0b2ed71b60a205e07ca761aa11d90544e5 1870 manpages-posix_2013a-1.dsc
 91b5b10a7a596615789782dad0adb477a8bf9f84 930736 
manpages-posix_2013a.orig.tar.xz
 ee8550117082659c82f447dcb97215a4aadc4ef7 3544 

Bug#814211: marked as done (rr: FTBFS: CMake Error at CMakeLists.txt:110 (message): Couldn't find gdb.)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 10:43:50 +
with message-id 
and subject line Bug#814211: fixed in rr 4.1.0-2
has caused the Debian Bug report #814211,
regarding rr: FTBFS: CMake Error at CMakeLists.txt:110 (message): Couldn't find 
gdb.
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.)


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

rr fails to build from source in unstable/amd64:

  [..]

  dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var returned 
exit code 1
  debian/rules:20: recipe for target 'build' failed
  make: *** [build] Error 255

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: rr
Source-Version: 4.1.0-2

We believe that the bug you reported is fixed in the latest version of
rr, 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.
Stephen Kitt  (supplier of updated rr 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, 09 Feb 2016 10:45:20 +0100
Source: rr
Binary: rr
Architecture: source
Version: 4.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 rr - application execution recorder, player and debugger
Closes: 814211
Changes:
 rr (4.1.0-2) unstable; urgency=medium
 .
   * Add missing build-dependency on gdb (with thanks to the ever-
 vigilant Chris Lamb; closes: #814211).
Checksums-Sha1:
 5766a74ef42370e8f4407915a06b9be878cadfb6 1880 rr_4.1.0-2.dsc
 aeec5213bd65c93d1adea58a57acb52d4d801527 7436 rr_4.1.0-2.debian.tar.xz
Checksums-Sha256:
 89e01a2d9ffbb23dc033a789b4eb68e2c6717076354d1221bac8f673afb6 1880 
rr_4.1.0-2.dsc
 7093fe64491dfa36e78b09276eb6817454d49e3da83238aa600f69ebcd973c21 7436 
rr_4.1.0-2.debian.tar.xz
Files:
 a7a3ae6b9cb4439a8d8fc16647540f01 1880 devel optional rr_4.1.0-2.dsc
 539abcd8f24f7f976881254619a4c31b 7436 devel optional rr_4.1.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWubWhAAoJEIDTAvWIbYOc/ggP/2NccBiKWcIhjILZsyaCui3/
usWHkvKxk+k68MUbQvg40TlWF9taGE/QW/PdcLpd8pF+xyDpoabmX7LfOP1BGoYJ
ENIEdbgH7S9AioDJbcFdv4WcmNWbuZfroRxzZeDPKT65XlfXtzEQnMrIbzztLyG6
UNets3881WnxH79egfD2tB2s6X/r8PeUwS6QqzUepS6e0TYKSkEss0X6Ez2xzDHF
MeYNp9ylMLcMYBIsX7nCTCsPz0aNs2EDSlyxIH2SZT2JJBkeb7NWC+ExDuQ0ykbc
COAJn3lPFRmFZusqSCU7xWelnTFKimRqzHfsxZJ2XXWeCJO2DyV0ICzd9q57iF+C
spFZk0G8H+AguFHB1lCJfJb7X7cUXT8owey9z5eMTLQw/YqtcvR0Pfkp1/IRjcpg
VpmNNYsG5pEi94epW7J4LKeQiE5N/nEDbuFPGOtCXoty8pH5HBmG42WYkoJRiek4
ITmIEr/T/Xe3+eprOLMY0lDscNhJX+eTfHXruJsgnX9PECPvYnepQOfXqlYof+Qq
GI+DaVenecmYLdnoLd3uncw7g1sPLvWIfcn67wGtn7FGgMnUTamxzpuxMhpuQpKc
LPw1TwdcwNyOsF1j/tldqdcw00PjvHNUDkgeohYwVhst2j0K6DSJDmWh/sM7p2Sl
/iAsCHlQPuyFHQzICGPG
=v21n
-END PGP SIGNATURE End Message ---

Bug#809426: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:25:23 +
with message-id 
and subject line Bug#814119: Removed package(s) from unstable
has caused the Debian Bug report #809426,
regarding Useless in Debian
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.)


-- 
809426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-xml-dtd
Version: 0.5.2+dfsg1-3
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

php-xml-dtd is not used by any Debian package currently, and hasn’t seen
any upstream activity for over five years. It has a low (and shrinking)
popcon, so probably isn’t of any use anymore. There is a priori little
point to ship it in the next stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.5.2+dfsg1-3+rm

Dear submitter,

as the package php-xml-dtd has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#802077: marked as done (jenkins-memory-monitor: FTBFS: java.io.IOException: 'top' unavailable)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:25:59 +
with message-id 
and subject line Bug#814120: Removed package(s) from unstable
has caused the Debian Bug report #802077,
regarding jenkins-memory-monitor: FTBFS: java.io.IOException: 'top' unavailable
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.)


-- 
802077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jenkins-memory-monitor
Version: 1.8-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

---
 T E S T S
---
Running org.jvnet.hudson.MemoryMonitorTest
Memory:22982/24058MB  Swap:274491/274747MB
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.347 sec <<< 
FAILURE! - in org.jvnet.hudson.MemoryMonitorTest
top(org.jvnet.hudson.MemoryMonitorTest)  Time elapsed: 0.302 sec  <<< ERROR!
java.io.IOException: 'top' unavailable
at org.jvnet.hudson.Top.monitor(Top.java:78)
at org.jvnet.hudson.MemoryMonitorTest.top(MemoryMonitorTest.java:17)


Results :

Tests in error: 
  MemoryMonitorTest.top:17 �� IO 'top' unavailable

Tests run: 2, Failures: 0, Errors: 1, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to /jenkins-memory-monitor-1.8/target/surefire-reports for the 
individual test results.

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/jenkins-memory-monitor.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Version: 1.9-1+rm

Dear submitter,

as the package jenkins-memory-monitor has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#804899: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:13:34 +
with message-id 
and subject line Bug#814100: Removed package(s) from unstable
has caused the Debian Bug report #804899,
regarding Useless in Debian
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.)


-- 
804899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-net-checkip
Version: 1.2.2-1
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

php-net-checkip is just a trivial validator of IP (v4 only) addresses,
i.e. a few lines of code, not used by any Debian package currently, so
there is a priori little point to ship it in the next stable release. It
hasn’t seen any upstream activity for over five years.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David




signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.2.2-1+rm

Dear submitter,

as the package php-net-checkip has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#804894: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:12:48 +
with message-id 
and subject line Bug#814099: Removed package(s) from unstable
has caused the Debian Bug report #804894,
regarding Useless in Debian
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.)


-- 
804894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-xml-rpc
Version: 1.5.5-1
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

Upstream declared that “This package has been superseded, but is still
maintained for bugs and security fixes. Use XML_RPC2 instead.”
php-xml-rpc2 is already in Debian. No packages in Debian depends on
php-xml-rpc, so there is a priori little point to ship it in the next
stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.5.5-1+rm

Dear submitter,

as the package php-xml-rpc has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#804906: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:14:14 +
with message-id 
and subject line Bug#814101: Removed package(s) from unstable
has caused the Debian Bug report #804906,
regarding Useless in Debian
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.)


-- 
804906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-net-portscan
Version: 1.0.3-2
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

php-net-portscan is not used by any Debian package currently, and hasn’t
seen any upstream activity for over five years. It has a low (and
shrinking) popcon, so isn’t of any use anymore a priori. There is a
priori little point to ship it in the next stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.0.3-2+rm

Dear submitter,

as the package php-net-portscan has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#804902: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:16:48 +
with message-id 
and subject line Bug#814107: Removed package(s) from unstable
has caused the Debian Bug report #804902,
regarding Useless in Debian
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.)


-- 
804902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-structures-datagrid-renderer-htmltable
Version: 0.1.6-1
Severity: minor

Hi Cyril,

The Homepage set in php-structures-datagrid-renderer-htmltable should
point to the following URL:
http://pear.php.net/package/Structures_DataGrid_Renderer_HTMLTable/

I can’t help noticing in that page that the upstream package is not
maintained, that the Debian package does not have any reverse
(build-)dependencies, and (thus) have a very low popcon, do you still
use/need it in the archive?

If you want to keep the package in the archive, I’d encourage you to
maintain it within the Debian PHP PEAR Maintainers team
( X-Debbug-CC).

Regards

David

P.-S.: I stumbled upon this package while looking at the php-html-common
status (also unmaintained upstream with low popcon), that has only one
reverse dependency you also maintain: php-html-table (also unmaintained
upstream with a very low popcon), that only has this package as a
reverse dependency. I was then wondering if there was still a point
keeping all those in the Debian archive (if there is, I’ll also
encourage you to maintain php-html-table in the Debian PHP PEAR
Maintainers team).


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 0.9.3-1+rm

Dear submitter,

as the package php-structures-datagrid has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#783419: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:15:45 +
with message-id 
and subject line Bug#814106: Removed package(s) from unstable
has caused the Debian Bug report #783419,
regarding Useless in Debian
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.)


-- 
783419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-structures-datagrid-renderer-htmltable
Version: 0.1.6-1
Severity: minor

Hi Cyril,

The Homepage set in php-structures-datagrid-renderer-htmltable should
point to the following URL:
http://pear.php.net/package/Structures_DataGrid_Renderer_HTMLTable/

I can’t help noticing in that page that the upstream package is not
maintained, that the Debian package does not have any reverse
(build-)dependencies, and (thus) have a very low popcon, do you still
use/need it in the archive?

If you want to keep the package in the archive, I’d encourage you to
maintain it within the Debian PHP PEAR Maintainers team
( X-Debbug-CC).

Regards

David

P.-S.: I stumbled upon this package while looking at the php-html-common
status (also unmaintained upstream with low popcon), that has only one
reverse dependency you also maintain: php-html-table (also unmaintained
upstream with a very low popcon), that only has this package as a
reverse dependency. I was then wondering if there was still a point
keeping all those in the Debian archive (if there is, I’ll also
encourage you to maintain php-html-table in the Debian PHP PEAR
Maintainers team).


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 0.1.6-1+rm

Dear submitter,

as the package php-structures-datagrid-renderer-htmltable has just been removed 
from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#804907: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:22:30 +
with message-id 
and subject line Bug#814114: Removed package(s) from unstable
has caused the Debian Bug report #804907,
regarding Useless in Debian
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.)


-- 
804907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-file
Version: 1.3.0-2
Severity: serious
Tags: stretch sid

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

Upstream declared that “This package is not maintained”. Only
php-structures-datagrid depends on it, but is not maintained either
(#804902), so there is a priori little point to ship it in the next
stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.3.0-2+rm

Dear submitter,

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

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

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

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

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

Bug#809420: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:21:13 +
with message-id 
and subject line Bug#814112: Removed package(s) from unstable
has caused the Debian Bug report #809420,
regarding Useless in Debian
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.)


-- 
809420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-html-common
Version: 1.2.5-2
Severity: serious
Tags: stretch sid


[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

Hi,

Upstream hasn’t been active in over five years, and declared that “This
package has been superseded […] Use HTML_Common2 instead.”
The package is only used by php-html-table, but this package is going
away (#809419), so there is a priori little point to ship it in the next
stable release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.2.5-2+rm

Dear submitter,

as the package php-html-common has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

Bug#804785: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:23:20 +
with message-id 
and subject line Bug#814116: Removed package(s) from unstable
has caused the Debian Bug report #804785,
regarding Useless in Debian
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.)


-- 
804785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpunit-selenium
Version: 1.3.3-1
Severity: serious
Tags: sid stretch

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

phpunit-selenium used to be part of phpunit, and this package was
uploaded when it was split out. PHPUnit 5 removed all mention if it,
PHPUnit upstream doesn’t take care of it anymore, and the Debian package
never moved to the new upstream source [0].

0: https://github.com/giorgiosironi/phpunit-selenium

Not sure anyone actually uses it, but if so, now would be a good time to
step up, or this package will not be part of Stretch.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.3.3-1+rm

Dear submitter,

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

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

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

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

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

Bug#809422: marked as done (Useless in Debian)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:21:50 +
with message-id 
and subject line Bug#814113: Removed package(s) from unstable
has caused the Debian Bug report #809422,
regarding Useless in Debian
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.)


-- 
809422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-jama
Version: 0~2+dfsg-1
Severity: serious
Tags: stretch sid

Hi,

I initially packaged php-jama as a dependency of php-excel (#718585),
but this package is not going to happen in the near future a priori, so
there is little point to ship it in the next stable release.
Furthermore, the upstream website is dead for a few months now.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0~2+dfsg-1+rm

Dear submitter,

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

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

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

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

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

Processed: tagging 814152

[Debian Bug Tracking System]

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

> tags 814152 + pending
Bug #814152 [libkscreenlocker5] [libkscreenlocker5] Conflict with 
plasma-workspace
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#790271: Fix build failure in stable/jessie (Was: Bug#790271: fixed in pagekite 0.5.6d-4)

[Petter Reinholdtsen]

This RC bug affect stable, and should be fixed there.  I've
confirmed that the package fail to build in a jessie chroot without
python-openssl, and that installing python-openssl solve it.

Because of this, I propose to apply this patch to the stable version:

diff --git a/debian/control b/debian/control
index 6707331..9936cec 100644
--- a/debian/control
+++ b/debian/control
@@ -10,6 +10,7 @@ Build-Depends:
  , python-setuptools
  , dh-python
  , python-socksipychain
+ , python-openssl
 X-Python-Version: >= 2.3, << 3.0
 Standards-Version: 3.9.5
 Homepage: https://pagekite.net/

I do not remember the procedure for getting changes into stable, but
hope to find time to investigate that some time in the future.

-- 
Happy hacking
Petter Reinholdtsen

Bug#796118: dnscache is buggy (failing to resolve indymedia.org)

[Daniel Kahn Gillmor]

Following up on the discussion about dnscache problems in
https://bugs.debian.org/796118:

dnscache is, sadly, buggy even beyond the concerns about cache
poisoning.  It is unable to resolve the domain name indymedia.org, while
other DNS resolvers like unbound can do.
 
The following test produces traces of activity comparing dnscache and
unbound:

As a normal user:

WORKDIR=$(mktemp -d)
dnscache-conf $(id -un) $(id -un) $WORKDIR/dnscache 127.1.2.3

as the superuser:

cd $WORKDIR/dnscache
./run > ../dnscache.indymedia.org.log

as the normal user again:

dig -t a @127.1.2.3 indymedia.org

this will time out with "no servers could be reached"; then kill the
superuser's process.


Doing the same for unbound:

as a normal user:

 mkdir -p $WORKDIR/unbound
 cat > $WORKDIR/unbound/unbound.conf < ../unbound.indymedia.org.log

as the normal user again:

dig -t a @127.1.2.3 indymedia.org

This should respond immediately with the correct information.

The two generated traces are attached below.

--dkg


starting
query 1 7f01:c743:08e3 1 indymedia.org.
tx 0 1 indymedia.org. . 803f0235 c0249411 c6290004 c021040c c00505f1 c0e44fc9 
c707532a 80080a5a c0cbe60a ca0c1b21 c0702404 c03a801e c1000e81
rr c0249411 172800 1 b0.org.afilias-nst.org. c7133601
rr c0249411 172800 1 b2.org.afilias-nst.org. c7f97801
rr c0249411 172800 1 d0.org.afilias-nst.org. c7133901
rr c0249411 172800 1 a0.org.afilias-nst.info. c7133801
rr c0249411 172800 1 a2.org.afilias-nst.info. c7f97001
rr c0249411 172800 1 c0.org.afilias-nst.info. c7133501
rr c0249411 172800 ns org. a2.org.afilias-nst.info.
rr c0249411 172800 ns org. b2.org.afilias-nst.org.
rr c0249411 172800 ns org. c0.org.afilias-nst.info.
rr c0249411 172800 ns org. a0.org.afilias-nst.info.
rr c0249411 172800 ns org. b0.org.afilias-nst.org.
rr c0249411 172800 ns org. d0.org.afilias-nst.org.
rr c0249411 172800 28 b0.org.afilias-nst.org. 2001050c0001
rr c0249411 172800 28 b2.org.afilias-nst.org. 200105480001
rr c0249411 172800 28 d0.org.afilias-nst.org. 2001050f0001
rr c0249411 172800 28 a0.org.afilias-nst.info. 2001050e0001
rr c0249411 172800 28 a2.org.afilias-nst.info. 20010541
rr c0249411 172800 28 c0.org.afilias-nst.info. 2001050b0001
stats 1 864 1 0
cached 1 a2.org.afilias-nst.info.
cached 1 b2.org.afilias-nst.org.
cached 1 c0.org.afilias-nst.info.
cached 1 a0.org.afilias-nst.info.
cached 1 b0.org.afilias-nst.org.
cached 1 d0.org.afilias-nst.org.
tx 0 1 indymedia.org. org. c7133501 c7133601 c7133801 c7133901 c7f97001 c7f97801
rr c7133501 86400 ns indymedia.org. ns2.riseup.net.
rr c7133501 86400 ns indymedia.org. ns2.fs-dl.net.
stats 1 932 1 0
tx 1 1 ns2.riseup.net. . c6290004 c03a801e c0e44fc9 c00505f1 c0702404 80080a5a 
c0cbe60a c707532a ca0c1b21 c1000e81 803f0235 c0249411 c021040c
rr c03a801e 172800 1 a.gtld-servers.net. c005061e
rr c03a801e 172800 1 b.gtld-servers.net. c0210e1e
rr c03a801e 172800 1 c.gtld-servers.net. c01a5c1e
rr c03a801e 172800 1 d.gtld-servers.net. c01f501e
rr c03a801e 172800 1 e.gtld-servers.net. c00c5e1e
rr c03a801e 172800 1 f.gtld-servers.net. c023331e
rr c03a801e 172800 1 g.gtld-servers.net. c02a5d1e
rr c03a801e 172800 1 h.gtld-servers.net. c036701e
rr c03a801e 172800 1 i.gtld-servers.net. c02bac1e
rr c03a801e 172800 1 j.gtld-servers.net. c0304f1e
rr c03a801e 172800 1 k.gtld-servers.net. c034b21e
rr c03a801e 172800 1 l.gtld-servers.net. c029a21e
rr c03a801e 172800 1 m.gtld-servers.net. c037531e
rr c03a801e 172800 ns net. a.gtld-servers.net.
rr c03a801e 172800 ns net. b.gtld-servers.net.
rr c03a801e 172800 ns net. c.gtld-servers.net.
rr c03a801e 172800 ns net. d.gtld-servers.net.
rr c03a801e 172800 ns net. e.gtld-servers.net.
rr c03a801e 172800 ns net. f.gtld-servers.net.
rr c03a801e 172800 ns net. g.gtld-servers.net.
rr c03a801e 172800 ns net. h.gtld-servers.net.
rr c03a801e 172800 ns net. i.gtld-servers.net.
rr c03a801e 172800 ns net. j.gtld-servers.net.
rr c03a801e 172800 ns net. k.gtld-servers.net.
rr c03a801e 172800 ns net. l.gtld-servers.net.
rr c03a801e 172800 ns net. m.gtld-servers.net.
rr c03a801e 172800 28 a.gtld-servers.net. 20010503a83e00020030
stats 1 1877 1 0
cached 1 a.gtld-servers.net.
cached 1 b.gtld-servers.net.
cached 1 c.gtld-servers.net.
cached 1 d.gtld-servers.net.
cached 1 e.gtld-servers.net.
cached 1 f.gtld-servers.net.
cached 1 g.gtld-servers.net.
cached 1 h.gtld-servers.net.
cached 1 i.gtld-servers.net.
cached 1 j.gtld-servers.net.
cached 1 k.gtld-servers.net.
cached 1 l.gtld-servers.net.
cached 1 m.gtld-servers.net.
tx 1 1 ns2.riseup.net. net. c034b21e c037531e c00c5e1e c0304f1e c023331e 
c036701e c01f501e c0210e1e c005061e c029a21e c02bac1e c01a5c1e c02a5d1e
rr c034b21e 172800 1 primary.riseup.net. cc0da403
rr c034b21e 172800 1 secondary.riseup.net. c73a508f
rr c034b21e 172800 ns riseup.net. primary.riseup.net.
rr c034b21e 172800 ns riseup.net. 

Processed: tagging 814200

[Debian Bug Tracking System]

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

> tags 814200 + pending
Bug #814200 [kdepimlibs] kdepimlibs: Incorrect Build-Deps
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#695303: marked as done (ghdl: Please change Build-Depends: gnat-4.4 to gnat-4.8)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:29:18 +
with message-id 
and subject line Bug#814147: Removed package(s) from unstable
has caused the Debian Bug report #695303,
regarding ghdl: Please change Build-Depends: gnat-4.4 to gnat-4.8
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.)


-- 
695303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ghdl
Version: 0.29+gcc4.3.4+dfsg-1.1
Severity: important

Dear Maintainer,

since gnat-4.4 is about to be removed from Debian (see bug #669513),
please use gnat-4.6 to build this package.

Best regards,
Tobias Hansen
--- End Message ---
--- Begin Message ---
Version: 0.29+gcc4.3.4+dfsg-1.1+rm

Dear submitter,

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

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

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

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

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

Bug#814166: marked as done (libsbml: (Build-)Depends on OpenJDK 7)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 12:19:24 +
with message-id 
and subject line Bug#814166: fixed in libsbml 5.12.0+dfsg-3
has caused the Debian Bug report #814166,
regarding libsbml: (Build-)Depends on OpenJDK 7
to be marked as done.

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

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


-- 
814166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsbml
Version: 5.12.0+dfsg-2
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.
--- End Message ---
--- Begin Message ---
Source: libsbml
Source-Version: 5.12.0+dfsg-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Feb 2016 11:28:36 +0100
Source: libsbml
Binary: libsbml5-dev libsbml5-dbg libsbml5 libsbml5-python libsbml5-java 
libsbml5-perl libsbml5-octave libsbml5-cil libsbml5-examples libsbml5-doc 
libsbml5-cil-doc libsbml5-java-doc libsbml5-perl-doc libsbml5-python-doc
Architecture: source
Version: 5.12.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libsbml5   - System Biology Markup Language library
 libsbml5-cil - System Biology Markup Language library - CLI bindings
 libsbml5-cil-doc - System Biology Markup Language library -- CLI documentation
 libsbml5-dbg - System Biology Markup Language library - debug symbols
 libsbml5-dev - System Biology Markup Language library - development files
 libsbml5-doc - System Biology Markup Language library -- documentation
 libsbml5-examples - System Biology Markup Language library -- example files
 libsbml5-java - System Biology Markup Language library - Java bindings
 libsbml5-java-doc - System Biology Markup Language library -- Java 
documentation
 libsbml5-octave - System Biology Markup Language library - Octave bindings
 libsbml5-perl - System Biology Markup Language library - Perl bindings
 libsbml5-perl-doc - System Biology Markup Language library -- Perl 
documentation
 libsbml5-python - System Biology Markup Language library - Python bindings
 libsbml5-python-doc - System Biology Markup Language library -- Python 
documentation
Closes: 814166
Changes:
 libsbml (5.12.0+dfsg-3) unstable; urgency=medium
 .
   * Build-Depend from default-jdk instead a specific version
 Closes: #814166
Checksums-Sha1:
 5cf16018f4976f024842e9bcbfcefdcb763ab4fc 3041 libsbml_5.12.0+dfsg-3.dsc
 6744d9976b8ba1e07e9f1d1429f96c5407790f86 21380 
libsbml_5.12.0+dfsg-3.debian.tar.xz
Checksums-Sha256:
 9d3b4839907713c65ee0b1465b6660bd5407ccc1910fc299a8567ca555f4682e 3041 
libsbml_5.12.0+dfsg-3.dsc
 361e656e806470c3b050d103b67192ff0916b6006966258240b9a3e023af732e 21380 
libsbml_5.12.0+dfsg-3.debian.tar.xz
Files:
 1204683ca072e5a85e3b454e0f5b2ecf 3041 science optional 
libsbml_5.12.0+dfsg-3.dsc
 e070aa18f37b9c6e306fbe25dbb130fc 21380 science optional 
libsbml_5.12.0+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWudTQAAoJEFeKBJTRxkbRI7MP/3n+s10JA5Lipmh5AhShikQv
qsgGVXSXC559ZBFKiCIO5czMuMdViLFlGLeVErPwU4LuDDVNiEW9yaLH5nbXvzRq
TK5LTrPBnfNv5t9ptjXursQPd0LkT+GJnEs4fdZONfBtmhB65w1V+UTIqVQsZuDR
A62gbAWM0S+IxLDK8OQdJRaoJxogmTfRL/CU5snJK3Tm2PF1E7IDJcwMS/ns3WYl
IUpPGnEVhPNAX+jQ90f+RbZbBG4GaHBjraEZagpKcouqxZu8hqc47pos1HzkcOWY
TLiilqc70+DGulxladeP67YDrCc8t/svGFGqqeB72V5sBqEtwUXu+btbdyVsEWFd
A4TprYi/EA7uPbMgWhjPRfcfy8ao0XZMZqdairVaG0YSeopn6OpfAP4lSwVAdcmq

Bug#751700: marked as done (vdkbuilder2: FTBFS - libvdkxdb2-dev has been removed)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 11:30:03 +
with message-id 
and subject line Bug#814155: Removed package(s) from unstable
has caused the Debian Bug report #751700,
regarding vdkbuilder2: FTBFS - libvdkxdb2-dev has been removed
to be marked as done.

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

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


-- 
751700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vdkbuilder2
Version: 2.4.0-4.4
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
 -> Attempting to parse the build-deps 
 -> Considering build-dep debhelper (>= 4.0)
   -> Trying debhelper
 -> Considering build-dep libgtk2.0-dev (>= 2.4.0-1)
   -> Trying libgtk2.0-dev
 -> Considering build-dep libglib2.0-dev
   -> Trying libglib2.0-dev
 -> Considering build-dep libvdk2-dev (>= 2.4.0-5.2)
   -> Trying libvdk2-dev
 -> Considering build-dep libxbase2.0-dev
   -> Trying libxbase2.0-dev
 -> Considering build-dep libvdkxdb2-dev (>= 2.4.0-3.3)
  Tried versions: 
   -> Does not satisfy version, not trying
E: Could not satisfy build-dependency.

As vdkxdb2 has been removed from the archive (#743295) on the maintainer's
request, should this package possibly be removed as well?

Best,
Michael



pgpg7W6yTEWlc.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 2.4.0-4.4+rm

Dear submitter,

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

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

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

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

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

Bug#814238: teckit: conflicts with texlive-binaries 2015.20150524.37493-7+b1 (teckit_compile)

[Stephen Kitt]

Package: teckit
Version: 2.5.4~svn140+ds2-1
Severity: serious
Justification: Policy 7.4

Dear Maintainer,

teckit ships /usr/bin/teckit_compile, which is also installed by
texlive-binaries 2015.20150524.37493-7+b1. The "Conflicts" stanza in
teckit was foiled by texlive-binaries' binNMU...

Regards,

Stephen


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

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

Processed: #807705

[Debian Bug Tracking System]

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

> severity 782330 serious
Bug #782330 [src:xserver-xorg-video-openchrome] FTBFS with libc6-dev >= 2.21: 
/usr/include/xorg/os.h:579:1: error: expected identifier or '(' before 
'__extension__' strndup(const char *str, size_t n);
Severity set to 'serious' from 'minor'
> merge 807705 782330
Bug #807705 [src:xserver-xorg-video-openchrome] xserver-xorg-video-openchrome: 
FTBFS: /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before 
'__extension__'
Bug #807705 [src:xserver-xorg-video-openchrome] xserver-xorg-video-openchrome: 
FTBFS: /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before 
'__extension__'
Added tag(s) fixed-upstream, upstream, and patch.
Bug #782330 [src:xserver-xorg-video-openchrome] FTBFS with libc6-dev >= 2.21: 
/usr/include/xorg/os.h:579:1: error: expected identifier or '(' before 
'__extension__' strndup(const char *str, size_t n);
Added tag(s) sid and stretch.
Merged 782330 807705
> forwarded 782330 https://bugs.freedesktop.org/show_bug.cgi?id=88334
Bug #782330 [src:xserver-xorg-video-openchrome] FTBFS with libc6-dev >= 2.21: 
/usr/include/xorg/os.h:579:1: error: expected identifier or '(' before 
'__extension__' strndup(const char *str, size_t n);
Bug #807705 [src:xserver-xorg-video-openchrome] xserver-xorg-video-openchrome: 
FTBFS: /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before 
'__extension__'
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=88334'.
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=88334'.
> thanks
Stopping processing here.

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

Bug#814230: sss_ssh_knownhostsproxy breaks "ssh -4"

[Harald Dunkel]

Package: sssd-common
Version: 1.12.5-3
Severity: serious

Apparently sss_ssh_knownhostsproxy breaks "ssh -4 host.example.com".
No connection.

ssh -4 -o ConnectTimeout=10 r...@host.example.com
Connection timed out during banner exchange

If I use host's IPv4 address or omit the proxy then there is
no problem.

This bug is serious. The reason for "-4" and "-6" is to
explicitly work around network problems.

openssh-client is version 6.7p1-5+deb8u1. Please reassign, if
necessary.


Regards
Harri

Bug#806473: msort: FTBFS: gmp.h: error: 'UINT_MAX' undeclared

[Jakub Wilk]

* Chris West (Faux) , 2015-11-27, 19:44:

gcc -DHAVE_CONFIG_H -I. -I. -I.   -D_FORTIFY_SOURCE=2 
-DLOCALEDIR=\"/usr/local/share/locale\" -DALLOCAOK -std=gnu99-DUSEUNINUMOK 
-g -O2 -c info.c
In file included from /usr/include/uninum/uninum.h:19:0,
from info.c:34:
/usr/include/x86_64-linux-gnu/gmp.h: In function ‘__gmpz_fits_uint_p’:
/usr/include/x86_64-linux-gnu/gmp.h:1740:3: error: ‘UINT_MAX’ undeclared (first 
use in this function)


The problem is that by default Automake adds "." to the include path 
(which is a pretty dumb idea IMO), and that msort has a header named 
"limits.h". So now when GMP requests , the msort's one gets 
included, instead of the system-wide one. Of course, the msort's header 
doesn't define UINT_MAX and friends, hence the error.


Adding "nostdinc" to AUTOMAKE_OPTIONS in Makefile.am and then 
regenerating Makefile.in should fix the bug.


--
Jakub Wilk

Processed: Re: Bug#812750: wine: Gecko integration is broken

[Debian Bug Tracking System]

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

> severity 812750 serious
Bug #812750 [wine] wine: Gecko integration is broken
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#814213: wmaker: FTBFS: Error: program option '--with-aix-soname' is not in the documentation './INSTALL-WMAKER'

[Doug Torrance]

Control: tags -1 pending

On 02/09/2016 05:57 AM, Doug Torrance wrote:
> On 02/09/2016 03:59 AM, Chris Lamb wrote:
>> Source: wmaker
>> Version: 0.95.7-3
>> Severity: serious
>> Justification: fails to build from source
>> User: reproducible-bui...@lists.alioth.debian.org
>> Usertags: ftbfs
>> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
>>
>> Dear Maintainer,
>>
>> wmaker fails to build from source in unstable/amd64:
>>
>>   [..]
>>
>>   make  check-local
>>   make[4]: Entering directory 
>> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>>   ./script/check-cmdline-options-doc.sh \
>>  --program "./configure" --text-doc "./INSTALL-WMAKER" \
>>  --ignore-prg 'with-PACKAGE,without-PACKAGE # only template names from 
>> Autoconf' \
>>  --ignore-prg 'program-prefix,program-suffix,program-transform-name # in 
>> INSTALL' \
>>  --ignore-prg 'version,quiet,srcdir,build,host,cache-file,no-create # in 
>> INSTALL' \
>>  --ignore-prg 'enable-silent-rules,disable-silent-rules # should be in 
>> INSTALL' \
>>  --ignore-prg 'enable-dependency-tracking,disable-dependency-tracking # 
>> in INSTALL' \
>>  --ignore-prg 'enable-shared,enable-static # should be in INSTALL' \
>>  --ignore-prg 'disable-option-checking,enable-fast-install # should be 
>> in INSTALL' \
>>  --ignore-prg 'disable-libtool-lock,with-pic,with-gnu-ld,with-sysroot # 
>> for libtool' \
>>  --ignore-prg 'runstatedir #new in autoconf 2.70, backported in Debian' \
>>  --ignore-prg 'with-x # no use, it would not work without X'
>>   Error: program option '--with-aix-soname' is not in the documentation 
>> './INSTALL-WMAKER'
>>   Makefile:951: recipe for target 'configure-documentation' failed
>>   make[4]: *** [configure-documentation] Error 1
>>   make[4]: Leaving directory 
>> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>>   Makefile:766: recipe for target 'check-am' failed
>>   make[3]: *** [check-am] Error 2
>>   make[3]: Leaving directory 
>> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>>   Makefile:478: recipe for target 'check-recursive' failed
>>   make[2]: *** [check-recursive] Error 1
>>   make[2]: Leaving directory 
>> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>>   Makefile:768: recipe for target 'check' failed
>>   make[1]: *** [check] Error 2
>>   make[1]: Leaving directory 
>> '/home/lamby/temp/cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
>>   dh_auto_test: make -j9 check returned exit code 2
>>   debian/rules:30: recipe for target 'build' failed
>>   make: *** [build] Error 2
>>
>>   [..]
> 
> Thanks for your report!
> 
> This is because libtool 2.4.6 was just uploaded to sid on Sunday [1].
> From [2]:
>   * m4/ltoptions.m4 (_LT_WITH_AIX_SONAME): New. Provides
>   commandline option --with-aix-soname=aix|svr4|both. Declares
>   $shared_archive_member_spec as libtool variable.
> 
> [1] https://packages.qa.debian.org/libt/libtool/news/20160207T173014Z.html
> [2] 
> http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=8fa719e81dba828d3e22cd59f825fac456c20809

I've just pushed a patch to git which fixes this issue. [1]

Andreas or kix, would either of you be willing to review and sponsor an
upload?

Thanks!
Doug

[1] 
http://anonscm.debian.org/cgit/pkg-wmaker/wmaker.git/commit/?id=dd955a763d8f1189d9f06e9447811915d89c50b4

Processed: Re: Bug#814213: wmaker: FTBFS: Error: program option '--with-aix-soname' is not in the documentation './INSTALL-WMAKER'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #814213 [src:wmaker] wmaker: FTBFS: Error: program option 
'--with-aix-soname' is not in the documentation './INSTALL-WMAKER'
Added tag(s) pending.

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

Bug#813973: dogecoin and libbitcoinconsensus0: error when trying to install together

[Keng-Yu Lin]

reported in dogecoin upstream: https://github.com/dogecoin/dogecoin/issues/1325.

2016-02-07 16:19 GMT+08:00 Ralf Treinen :
> Package: libbitcoinconsensus0,dogecoin
> Version: libbitcoinconsensus0/0.11.2-1
> Version: dogecoin/1.8.10-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
>
> Date: 2016-02-07
> Architecture: amd64
> Distribution: sid
>
> Hi,
>
> automatic installation tests of packages that share a file and at the
> same time do not conflict by their package dependency relationships has
> detected the following problem:
>
>
>
> Extracting templates from packages: 30%
> Extracting templates from packages: 60%
> Extracting templates from packages: 90%
> Extracting templates from packages: 100%
> Preconfiguring packages ...
> Selecting previously unselected package libexpat1:amd64.
> (Reading database ... 10944 files and directories currently installed.)
> Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
> Unpacking libexpat1:amd64 (2.1.0-7) ...
> Selecting previously unselected package libpng12-0:amd64.
> Preparing to unpack .../libpng12-0_1.2.54-1_amd64.deb ...
> Unpacking libpng12-0:amd64 (1.2.54-1) ...
> Selecting previously unselected package libfreetype6:amd64.
> Preparing to unpack .../libfreetype6_2.6.1-0.1_amd64.deb ...
> Unpacking libfreetype6:amd64 (2.6.1-0.1) ...
> Selecting previously unselected package ucf.
> Preparing to unpack .../archives/ucf_3.0033_all.deb ...
> Moving old data out of the way
> Unpacking ucf (3.0033) ...
> Selecting previously unselected package fonts-dejavu-core.
> Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ...
> Unpacking fonts-dejavu-core (2.35-1) ...
> Selecting previously unselected package fontconfig-config.
> Preparing to unpack .../fontconfig-config_2.11.0-6.3_all.deb ...
> Unpacking fontconfig-config (2.11.0-6.3) ...
> Selecting previously unselected package libfontconfig1:amd64.
> Preparing to unpack .../libfontconfig1_2.11.0-6.3_amd64.deb ...
> Unpacking libfontconfig1:amd64 (2.11.0-6.3) ...
> Selecting previously unselected package fontconfig.
> Preparing to unpack .../fontconfig_2.11.0-6.3_amd64.deb ...
> Unpacking fontconfig (2.11.0-6.3) ...
> Selecting previously unselected package x11-common.
> Preparing to unpack .../x11-common_1%3a7.7+13_all.deb ...
> Unpacking x11-common (1:7.7+13) ...
> Selecting previously unselected package libice6:amd64.
> Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ...
> Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
> Selecting previously unselected package libmtdev1:amd64.
> Preparing to unpack .../libmtdev1_1.1.5-1_amd64.deb ...
> Unpacking libmtdev1:amd64 (1.1.5-1) ...
> Selecting previously unselected package libsm6:amd64.
> Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
> Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
> Selecting previously unselected package libgcrypt20:amd64.
> Preparing to unpack .../libgcrypt20_1.6.4-5_amd64.deb ...
> Unpacking libgcrypt20:amd64 (1.6.4-5) ...
> Processing triggers for libc-bin (2.21-7) ...
> Processing triggers for man-db (2.7.5-1) ...
> Setting up libgcrypt20:amd64 (1.6.4-5) ...
> Processing triggers for libc-bin (2.21-7) ...
> Selecting previously unselected package libsystemd0:amd64.
> (Reading database ... 11204 files and directories currently installed.)
> Preparing to unpack .../libsystemd0_228-6_amd64.deb ...
> Unpacking libsystemd0:amd64 (228-6) ...
> Selecting previously unselected package libxau6:amd64.
> Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ...
> Unpacking libxau6:amd64 (1:1.0.8-1) ...
> Selecting previously unselected package libxdmcp6:amd64.
> Preparing to unpack .../libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
> Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
> Selecting previously unselected package libxcb1:amd64.
> Preparing to unpack .../libxcb1_1.11.1-1_amd64.deb ...
> Unpacking libxcb1:amd64 (1.11.1-1) ...
> Selecting previously unselected package libx11-data.
> Preparing to unpack .../libx11-data_2%3a1.6.3-1_all.deb ...
> Unpacking libx11-data (2:1.6.3-1) ...
> Selecting previously unselected package libx11-6:amd64.
> Preparing to unpack .../libx11-6_2%3a1.6.3-1_amd64.deb ...
> Unpacking libx11-6:amd64 (2:1.6.3-1) ...
> Selecting previously unselected package libx11-xcb1:amd64.
> Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
> Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
> Selecting previously unselected package libxfixes3:amd64.
> Preparing to unpack .../libxfixes3_1%3a5.0.1-2+b2_amd64.deb ...
> Unpacking libxfixes3:amd64 (1:5.0.1-2+b2) ...
> Selecting previously unselected package libxdamage1:amd64.
> Preparing to unpack .../libxdamage1_1%3a1.1.4-2+b1_amd64.deb ...
> Unpacking libxdamage1:amd64 (1:1.1.4-2+b1) ...
> Selecting previously unselected package libxext6:amd64.
> Preparing to unpack .../libxext6_2%3a1.3.3-1_amd64.deb ...
> Unpacking libxext6:amd64 (2:1.3.3-1) ...
> Selecting previously unselected package libxshmfence1:amd64.
> Preparing to 

Bug#813974: dogecoin and libbitcoinconsensus-dev: error when trying to install together

[Keng-Yu Lin]

reported in dogecoin upstream: https://github.com/dogecoin/dogecoin/issues/1325.

2016-02-07 16:19 GMT+08:00 Ralf Treinen :
> Package: libbitcoinconsensus-dev,dogecoin
> Version: libbitcoinconsensus-dev/0.11.2-1
> Version: dogecoin/1.8.10-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
>
> Date: 2016-02-07
> Architecture: amd64
> Distribution: sid
>
> Hi,
>
> automatic installation tests of packages that share a file and at the
> same time do not conflict by their package dependency relationships has
> detected the following problem:
>
>
>
> Extracting templates from packages: 29%
> Extracting templates from packages: 59%
> Extracting templates from packages: 89%
> Extracting templates from packages: 100%
> Preconfiguring packages ...
> Selecting previously unselected package libexpat1:amd64.
> (Reading database ... 10944 files and directories currently installed.)
> Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
> Unpacking libexpat1:amd64 (2.1.0-7) ...
> Selecting previously unselected package libpng12-0:amd64.
> Preparing to unpack .../libpng12-0_1.2.54-1_amd64.deb ...
> Unpacking libpng12-0:amd64 (1.2.54-1) ...
> Selecting previously unselected package libfreetype6:amd64.
> Preparing to unpack .../libfreetype6_2.6.1-0.1_amd64.deb ...
> Unpacking libfreetype6:amd64 (2.6.1-0.1) ...
> Selecting previously unselected package ucf.
> Preparing to unpack .../archives/ucf_3.0033_all.deb ...
> Moving old data out of the way
> Unpacking ucf (3.0033) ...
> Selecting previously unselected package fonts-dejavu-core.
> Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ...
> Unpacking fonts-dejavu-core (2.35-1) ...
> Selecting previously unselected package fontconfig-config.
> Preparing to unpack .../fontconfig-config_2.11.0-6.3_all.deb ...
> Unpacking fontconfig-config (2.11.0-6.3) ...
> Selecting previously unselected package libfontconfig1:amd64.
> Preparing to unpack .../libfontconfig1_2.11.0-6.3_amd64.deb ...
> Unpacking libfontconfig1:amd64 (2.11.0-6.3) ...
> Selecting previously unselected package fontconfig.
> Preparing to unpack .../fontconfig_2.11.0-6.3_amd64.deb ...
> Unpacking fontconfig (2.11.0-6.3) ...
> Selecting previously unselected package x11-common.
> Preparing to unpack .../x11-common_1%3a7.7+13_all.deb ...
> Unpacking x11-common (1:7.7+13) ...
> Selecting previously unselected package libice6:amd64.
> Preparing to unpack .../libice6_2%3a1.0.9-1+b1_amd64.deb ...
> Unpacking libice6:amd64 (2:1.0.9-1+b1) ...
> Selecting previously unselected package libmtdev1:amd64.
> Preparing to unpack .../libmtdev1_1.1.5-1_amd64.deb ...
> Unpacking libmtdev1:amd64 (1.1.5-1) ...
> Selecting previously unselected package libsm6:amd64.
> Preparing to unpack .../libsm6_2%3a1.2.2-1+b1_amd64.deb ...
> Unpacking libsm6:amd64 (2:1.2.2-1+b1) ...
> Selecting previously unselected package libgcrypt20:amd64.
> Preparing to unpack .../libgcrypt20_1.6.4-5_amd64.deb ...
> Unpacking libgcrypt20:amd64 (1.6.4-5) ...
> Processing triggers for libc-bin (2.21-7) ...
> Processing triggers for man-db (2.7.5-1) ...
> Setting up libgcrypt20:amd64 (1.6.4-5) ...
> Processing triggers for libc-bin (2.21-7) ...
> Selecting previously unselected package libsystemd0:amd64.
> (Reading database ... 11204 files and directories currently installed.)
> Preparing to unpack .../libsystemd0_228-6_amd64.deb ...
> Unpacking libsystemd0:amd64 (228-6) ...
> Selecting previously unselected package libxau6:amd64.
> Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ...
> Unpacking libxau6:amd64 (1:1.0.8-1) ...
> Selecting previously unselected package libxdmcp6:amd64.
> Preparing to unpack .../libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
> Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
> Selecting previously unselected package libxcb1:amd64.
> Preparing to unpack .../libxcb1_1.11.1-1_amd64.deb ...
> Unpacking libxcb1:amd64 (1.11.1-1) ...
> Selecting previously unselected package libx11-data.
> Preparing to unpack .../libx11-data_2%3a1.6.3-1_all.deb ...
> Unpacking libx11-data (2:1.6.3-1) ...
> Selecting previously unselected package libx11-6:amd64.
> Preparing to unpack .../libx11-6_2%3a1.6.3-1_amd64.deb ...
> Unpacking libx11-6:amd64 (2:1.6.3-1) ...
> Selecting previously unselected package libx11-xcb1:amd64.
> Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
> Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
> Selecting previously unselected package libxfixes3:amd64.
> Preparing to unpack .../libxfixes3_1%3a5.0.1-2+b2_amd64.deb ...
> Unpacking libxfixes3:amd64 (1:5.0.1-2+b2) ...
> Selecting previously unselected package libxdamage1:amd64.
> Preparing to unpack .../libxdamage1_1%3a1.1.4-2+b1_amd64.deb ...
> Unpacking libxdamage1:amd64 (1:1.1.4-2+b1) ...
> Selecting previously unselected package libxext6:amd64.
> Preparing to unpack .../libxext6_2%3a1.3.3-1_amd64.deb ...
> Unpacking libxext6:amd64 (2:1.3.3-1) ...
> Selecting previously unselected package libxshmfence1:amd64.
> Preparing to 

Bug#812750: [pkg-wine-party] Bug#812750: wine: Gecko integration is broken

[Rhonda D'Vine]

* Austin English  [2016-02-09 17:19:30 CET]:
> On Feb 9, 2016 8:15 PM, "Rhonda D'Vine"  wrote:
> > severity 812750 serious
> > thanks
> >
> >   Hi!
> >
> > * Ralf Jung  [2016-01-26 10:57:49 CET]:
> > > From all I can tell, the Gecko integration is entirely broken. There
> > > is no wine-gecko packaged in Debian
> > > (the recommendation of libwine-gecko-2.40 is unsatisfiable),
   ^
> >
> >  From policy:
> >
> >  In addition, the packages in _main_
> > * must not require or recommend a package outside of _main_ for
> >   compilation or execution (thus, the package must not declare a
> >   "Pre-Depends", "Depends", "Recommends", "Build-Depends", or
> >   "Build-Depends-Indep" relationship on a non-_main_ package),
> >
> >  Given that the package Recommends a package that isn't available in the
> > pool this is a policy violation.
> 
> mingw64 is in main, what package are you referring to?

 No clue why you mention mingw64, I am to the package I did quote in my
mail and this bugreport is about, libwine-gecko-2.40.

 Hope that helps,
Rhonda 
-- 
Fühlst du dich mutlos, fass endlich Mut, los  |
Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los|

Bug#813875: insighttoolkit4: FTBFS on i386 (member reference base type 'void' is not a structure or union)

[Brad King]

On 02/06/2016 06:34 AM, Gert Wollny wrote:
> As you can see, this  is actually a bug in castxml
[snip]
> would you please consider filing a bug upstream

I've recorded the issue upstream here:

https://github.com/CastXML/CastXML/issues/47

Please follow that for updates.

-Brad

Bug#812750: [pkg-wine-party] Bug#812750: wine: Gecko integration is broken

[Austin English]

On Feb 9, 2016 8:15 PM, "Rhonda D'Vine"  wrote:
>
> severity 812750 serious
> thanks
>
>   Hi!
>
> * Ralf Jung  [2016-01-26 10:57:49 CET]:
> > >From all I can tell, the Gecko integration is entirely broken. There
is no wine-gecko packaged in Debian
> > (the recommendation of libwine-gecko-2.40 is unsatisfiable),
>
>  From policy:
>
>  In addition, the packages in _main_
> * must not require or recommend a package outside of _main_ for
>   compilation or execution (thus, the package must not declare a
>   "Pre-Depends", "Depends", "Recommends", "Build-Depends", or
>   "Build-Depends-Indep" relationship on a non-_main_ package),
>
>  Given that the package Recommends a package that isn't available in the
> pool this is a policy violation.
>
>  Thanks,
> Rhonda
> --
> Fühlst du dich mutlos, fass endlich Mut, los  |
> Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
> Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf
Anfang
> Fühlst du dich haltlos, such Halt und lass los|
>
> ___
> pkg-wine-party mailing list
> pkg-wine-pa...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-wine-party

mingw64 is in main, what package are you referring to?

Processed: Re: Bug#814200: kdepimlibs: Incorrect Build-Deps

[Debian Bug Tracking System]

Processing control commands:

> tag 814200 + unreproducible
Bug #814200 [kdepimlibs] kdepimlibs: Incorrect Build-Deps
Added tag(s) unreproducible.

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

Bug#808015: marked as done (acpid: FTBFS: libnetlink.c:497:54: error: comparison between signed and unsigned integer expressions)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 17:19:23 +
with message-id 
and subject line Bug#808015: fixed in acpid 1:2.0.26-1
has caused the Debian Bug report #808015,
regarding acpid: FTBFS: libnetlink.c:497:54: error: comparison between signed 
and unsigned integer expressions
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.)


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

acpid fails to build from source in unstable/amd64:

  [..]

  gcc -DHAVE_CONFIG_H -I. -I..  -include ../config.h -D_FORTIFY_SOURCE=2 -Wall 
-Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wshadow 
-Wstrict-prototypes -Wformat=2 -W -Wall -Werror -Wundef -Wshadow -D_GNU_SOURCE 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-fno-strict-aliasing -c -o libnetlink.o libnetlink.c
  libnetlink.c: In function 'addattr_l':
  libnetlink.c:497:54: error: comparison between signed and unsigned integer 
expressions [-Werror=sign-compare]
if ((int)NLMSG_ALIGN(n->nlmsg_len) + RTA_ALIGN(len) > maxlen) {
^
  libnetlink.c: In function 'rta_addattr32':
  libnetlink.c:527:36: error: comparison between signed and unsigned integer 
expressions [-Werror=sign-compare]
if (RTA_ALIGN(rta->rta_len) + len > maxlen) {
  ^
  libnetlink.c: In function 'rta_addattr_l':
  libnetlink.c:545:47: error: comparison between signed and unsigned integer 
expressions [-Werror=sign-compare]
if (RTA_ALIGN(rta->rta_len) + RTA_ALIGN(len) > maxlen) {
 ^
  cc1: all warnings being treated as errors
  Makefile:389: recipe for target 'libnetlink.o' failed
  make[3]: *** [libnetlink.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20151215105238.YtstkitUES/acpid-2.0.25/kacpimon'
  Makefile:635: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151215105238.YtstkitUES/acpid-2.0.25'
  Makefile:384: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151215105238.YtstkitUES/acpid-2.0.25'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


acpid.1:2.0.25-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: acpid
Source-Version: 1:2.0.26-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Feb 2016 17:34:08 +0100
Source: acpid
Binary: acpid kacpimon
Architecture: source amd64
Version: 1:2.0.26-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Acpi Team 
Changed-By: Michael Meskes 
Description:
 acpid  - Advanced Configuration and Power Interface event daemon
 kacpimon   - Kernel ACPI Event Monitor
Closes: 805865 808015
Changes:
 acpid (1:2.0.26-1) unstable; urgency=medium
 .
   * Imported Upstream version 2.0.26 (Closes: #808015)
   * Updated watch file
   * Fixwed typo in powerbtn.sh (Closes: #805865)
Checksums-Sha1:
 107b79362e9fdf5dcc84fbeb6fff8af74a28e521 2001 acpid_2.0.26-1.dsc
 957969660dad1f33b6750e018731b0a5f5123d4d 154856 acpid_2.0.26.orig.tar.xz
 67790c8cb213879eba29088116227b610efdbf4e 18144 

Bug#805193: marked as done (aster: FTBFS: Fatal Error: finclude/petscsys.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 17:20:04 +
with message-id 
and subject line Bug#805193: fixed in aster 11.5.0+dfsg2-4
has caused the Debian Bug report #805193,
regarding aster: FTBFS: Fatal Error: finclude/petscsys.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.)


-- 
805193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aster
Version: 11.5.0+dfsg2-3
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

[5245/7161] fc: bibfor/petsc/apbloc.F90 -> 
build/release/bibfor/petsc/apbloc.F90.1.o
/aster-11.5.0+dfsg2/bibfor/include/aster_petsc.h:21:0:

 #   include "finclude/petscsys.h"
 ^
Fatal Error: finclude/petscsys.h: No such file or directory
compilation terminated.
/aster-11.5.0+dfsg2/bibfor/include/aster_petsc.h:21:0:

 #   include "finclude/petscsys.h"
 ^
Fatal Error: finclude/petscsys.h: No such file or directory
compilation terminated.
Waf: Leaving directory `/aster-11.5.0+dfsg2/build/release'
Build failed
 -> task failed (exit status 1): 
{task 139982077600720: fc apalmc.F90 -> apalmc.F90.1.o}

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/aster.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: aster
Source-Version: 11.5.0+dfsg2-4

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated aster 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, 09 Feb 2016 18:19:56 +0200
Source: aster
Binary: code-aster code-aster-mpi-engine code-aster-test
Architecture: source
Version: 11.5.0+dfsg2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Graham Inggs 
Description:
 code-aster - Code_Aster finite element program - metapackage
 code-aster-mpi-engine - Code_Aster finite element program - parallel binary
 code-aster-test - Code_Aster finite element program - test files and examples
Closes: 805193
Changes:
 aster (11.5.0+dfsg2-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Florent Cayré ]
   * Add a patch to set the default renumbering algorithm to MD instead of
 METIS.
 .
   [ Graham Inggs ]
   * Fix build with PETSc >= 3.6 (Closes: #805193):
 - Append PETSc include path to C/F/FCFLAGS.
 - Change to PETSC_DEFAULT_REAL, thanks Peter Michael Green.
   * Build-depend on debhelper (>= 9) to match compat level.
   * Bump Standards-Version, no further changes.
Checksums-Sha1:
 cacfd9a6e397d82d7c4bbb1ab392e13c077bfcf8 2529 aster_11.5.0+dfsg2-4.dsc
 ef3c8e6149c063e7b6ecf4e059c5ccf0aeb62e64 11828 
aster_11.5.0+dfsg2-4.debian.tar.xz
Checksums-Sha256:
 fe4c7972b9190a098d8abcf82ba9fa9066e4b13057c16f193f6954a7a4f4379d 2529 
aster_11.5.0+dfsg2-4.dsc
 97b06c4dcc2ddda07b91db47157c37e26bfe392c376e16bc0a27427b3afd0b79 11828 
aster_11.5.0+dfsg2-4.debian.tar.xz
Files:
 004edb2d6c830d4e16002f5fa0f0d8e9 2529 science extra aster_11.5.0+dfsg2-4.dsc
 dfdd866b3bd67cc0b7b2d63c9dd38624 11828 science extra 
aster_11.5.0+dfsg2-4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWuhLhAAoJEK/P7I5mnOHClHAQAJyqaBAuKBNZoglMqAoEkB4u
UglTj7Y65ky/gFqyY8DUdp1ScuNiyLhTWkO0mhHoKfB9gQZTxS3Co7lOP1fvF1LU
QMX9sgvYEQzTiqE1ClQzP91pSpXBJsnUPmTajyjekDnC+3AJTHOQX0XTznR+5WCg
WN6cJ2t+gLayWgRIArSA2Rl5c5l187FSv7VAMjnYKx4uye/mTJsDHYdZ3ylrtZGH
5RszCvgNPdEvf6lrUoU+TZCC5PKphmray1fKRT/9Q1YDhs2h5VTuFXzGXIo3c/A3
A8xc78jSJ9Dw78RQxYM8ferY3TWkir/EL1HwK4F3Fid2s4fBDo9WBlEMFQBtWtmY
d+bMYtCb9lcHGmdYRoC4bPdti1lUfvqYyMLQ2vjy0N0Ao7UnbUbSHdOBMa3FDpjk

Bug#814200: kdepimlibs: Incorrect Build-Deps

[Maximiliano Curia]

Control: tag 814200 + unreproducible

Hi,

On Tuesday, 9 February 2016 10:59:29 CET Zhang Jingqiang wrote:
> Package: kdepimlibs
> Version: 4:15.12.1-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the
> past)

> It should build-depend on kgendesignerplugin, which install the needed cmake
> files.

This can't be the reason for the failed build, kgendesignerplugin is a 
dependency of libkf5kdelibs4support-dev, so it's available at build time.

But definetly the kdesignerplugin and kgendesignerplugin packages need a 
review.
 
> And the optional prison-dev is not needed, as the really needed one is
> kf5prison which has not been released yet.

Also not a reason to failed to build from source.

The buildds logs show that the issue in experimental was related to the 
version of akonadi-server at the time of the build try. Right now, the buildds 
should be able to rebuild kdepimlibs, afaik (if we kindly ask for a retry).

Am I missing something?

Happy hacking,
-- 
: You are in a dark room with a compiler, emacs, an internet connection,
: and a thermos of coffee.
: Your move ?
Saludos /\/\ /\ >< `/

Bug#812750: [pkg-wine-party] Bug#812750: wine: Gecko integration is broken

[Austin English]

On Feb 9, 2016 8:25 PM, "Rhonda D'Vine"  wrote:
>
> * Austin English  [2016-02-09 17:19:30 CET]:
> > On Feb 9, 2016 8:15 PM, "Rhonda D'Vine"  wrote:
> > > severity 812750 serious
> > > thanks
> > >
> > >   Hi!
> > >
> > > * Ralf Jung  [2016-01-26 10:57:49 CET]:
> > > > From all I can tell, the Gecko integration is entirely broken. There
> > > > is no wine-gecko packaged in Debian
> > > > (the recommendation of libwine-gecko-2.40 is unsatisfiable),
>^
> > >
> > >  From policy:
> > >
> > >  In addition, the packages in _main_
> > > * must not require or recommend a package outside of _main_
for
> > >   compilation or execution (thus, the package must not
declare a
> > >   "Pre-Depends", "Depends", "Recommends", "Build-Depends", or
> > >   "Build-Depends-Indep" relationship on a non-_main_ package),
> > >
> > >  Given that the package Recommends a package that isn't available in
the
> > > pool this is a policy violation.
> >
> > mingw64 is in main, what package are you referring to?
>
>  No clue why you mention mingw64, I am to the package I did quote in my
> mail and this bugreport is about, libwine-gecko-2.40.
>
>  Hope that helps,
> Rhonda
> --
> Fühlst du dich mutlos, fass endlich Mut, los  |
> Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
> Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf
Anfang
> Fühlst du dich haltlos, such Halt und lass los|

I'm asking what recommended package is the problem. It's not on
packages.d.o and not specified in the mail as far as I can tell.

Bug#812750: [pkg-wine-party] Bug#812750: wine: Gecko integration is broken

[Austin English]

On Feb 9, 2016 8:39 PM, austinengl...@gmail.com wrote:
>
> On Feb 9, 2016 8:25 PM, "Rhonda D'Vine"  wrote:
> >
> > * Austin English  [2016-02-09 17:19:30 CET]:
> > > On Feb 9, 2016 8:15 PM, "Rhonda D'Vine"  wrote:
> > > > severity 812750 serious
> > > > thanks
> > > >
> > > >   Hi!
> > > >
> > > > * Ralf Jung  [2016-01-26 10:57:49 CET]:
> > > > > From all I can tell, the Gecko integration is entirely broken.
There
> > > > > is no wine-gecko packaged in Debian
> > > > > (the recommendation of libwine-gecko-2.40 is unsatisfiable),
> >^
> > > >
> > > >  From policy:
> > > >
> > > >  In addition, the packages in _main_
> > > > * must not require or recommend a package outside of _main_
for
> > > >   compilation or execution (thus, the package must not
declare a
> > > >   "Pre-Depends", "Depends", "Recommends", "Build-Depends",
or
> > > >   "Build-Depends-Indep" relationship on a non-_main_
package),
> > > >
> > > >  Given that the package Recommends a package that isn't available
in the
> > > > pool this is a policy violation.
> > >
> > > mingw64 is in main, what package are you referring to?
> >
> >  No clue why you mention mingw64, I am to the package I did quote in my
> > mail and this bugreport is about, libwine-gecko-2.40.
> >
> >  Hope that helps,
> > Rhonda
> > --
> > Fühlst du dich mutlos, fass endlich Mut, los  |
> > Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
> > Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf
Anfang
> > Fühlst du dich haltlos, such Halt und lass los|
>
> I'm asking what recommended package is the problem. It's not on
packages.d.o and not specified in the mail as far as I can tell.

Or is it that libwine-gecko-2.40 isn't in main that is the problem? I
thought the problem was a gecko recommend.

So the question is why gecko isn't in main. I suppose there's a bug, I
haven't checked (on mobile).

Processed: Merging bugs

[Debian Bug Tracking System]

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

> severity 808433 grave
Bug #808433 [nethogs] nethogs doesn't start, saying "creating socket failed"
Severity set to 'grave' from 'normal'
> merge 808433 811273
Bug #808433 [nethogs] nethogs doesn't start, saying "creating socket failed"
Bug #808433 [nethogs] nethogs doesn't start, saying "creating socket failed"
Added tag(s) fixed-upstream.
Bug #811273 [nethogs] nethogs: creating socket failed while establishing local 
IP
Merged 808433 811273
> thanks
Stopping processing here.

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

Bug#801902: marked as done (python-pysph: ships /usr/lib/python2.7/dist-packages/site.py)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 16:35:26 +
with message-id 
and subject line Bug#801902: fixed in pysph 0~20160122.git1fe4786-1
has caused the Debian Bug report #801902,
regarding python-pysph: ships /usr/lib/python2.7/dist-packages/site.py
to be marked as done.

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

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


-- 
801902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pysph
Version: 0~20150606.gitfa26de9-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files:

  Selecting previously unselected package python-pysph.
  Preparing to unpack .../python-pysph_0~20150606.gitfa26de9-5+b1_amd64.deb ...
  Unpacking python-pysph (0~20150606.gitfa26de9-5+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pysph_0~20150606.gitfa26de9-5+b1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/site.py', which is 
also in package python-wxglade 0.7.1~rc1-1
  Processing triggers for libc-bin (2.19-22) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pysph_0~20150606.gitfa26de9-5+b1_amd64.deb

site.py sounds like a very generic name and probably should not be
shipped by any package.


Andreas
--- End Message ---
--- Begin Message ---
Source: pysph
Source-Version: 0~20160122.git1fe4786-1

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated pysph 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: Tue, 09 Feb 2016 14:36:27 +0100
Source: pysph
Binary: python-pysph pysph-viewer pysph-doc
Architecture: source
Version: 0~20160122.git1fe4786-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 pysph-doc  - documentation and examples for PySPH
 pysph-viewer - viewer for PySPH - framework for Smoothed Particle Hydrodynamics
 python-pysph - open source framework for Smoothed Particle Hydrodynamics
Closes: 801902
Changes:
 pysph (0~20160122.git1fe4786-1) unstable; urgency=medium
 .
   * [725acf5] Imported Upstream version 0~20160122.git1fe4786
   * [a1a3d77] Refresh patches.
   * [456e370] Add python-moko as Depends.
   * [f6238bf] Minor fix in d/rules.
   * [a8f501b] Apply cme fix dpkg.
   * [73d0d1d] Drop site.py. (Closes: #801902)
Checksums-Sha1:
 0c74f5bdb026a0167703f12397ef911713be11b1 2338 pysph_0~20160122.git1fe4786-1.dsc
 cd41de1473a10e7945334dd9167efc22121b161b 2181524 
pysph_0~20160122.git1fe4786.orig.tar.xz
 1885bcb150766411169f390ba996bd1d1b62a4ed 9604 
pysph_0~20160122.git1fe4786-1.debian.tar.xz
Checksums-Sha256:
 cc33458e3a4a358f192075158e8dc886006221a1db77b9395bb7e2b1063159d9 2338 
pysph_0~20160122.git1fe4786-1.dsc
 6098f295ca3152785e7f271a403537cf258f64c26c022993417684bb8a72b71d 2181524 
pysph_0~20160122.git1fe4786.orig.tar.xz
 f7b1a62ff994c01c834459d8f95b6b8f9e6df0dbb49b4190d86141ef5c8aafa7 9604 
pysph_0~20160122.git1fe4786-1.debian.tar.xz
Files:
 bd43867a638f46bf054e019cc3abf8a5 2338 science optional 
pysph_0~20160122.git1fe4786-1.dsc
 79d9251bf10f4b7971e79867dec51aac 2181524 science optional 
pysph_0~20160122.git1fe4786.orig.tar.xz
 ce1d856a6ce6e8e96f7e394ca59f462a 9604 science optional 
pysph_0~20160122.git1fe4786-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWufW4AAoJENPhc4PPp/8G0YgP/R4FyRuHq0aC0Rv87J3QVPtk
+DpZYwlX2OrDVR9AQSy59IFnLZjaeeht3DfD0+SESeo0t9TQT9wgC7qU6HzddXcn
hE0dQNUmMAbkRkaGFR/QV0O+MxooUM600haIvdAezKhCPShIODZ5413hERqDz0gf
eZvPlFBXlSo/jmwnazIFI3B7FPfPe0ltYnp6dZ4EET6a54CDyg5e/roSp1JgfcSc
y2mp1BUNkcKAmPq/IjX63xbACUMiqvNrRaXBurdIhu5Vz+rOfwRy1yh0evegalq9
ejhaM8+pzPyFerEuBAhSBJfifFKM78l9wwxgWY8KWxQPHg5WGjpLK9tsqLie8kT0

Bug#814069: marked as done (python-six-whl and python-pip-whl: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 16:35:55 +
with message-id 
and subject line Bug#814069: fixed in six 1.10.0-3
has caused the Debian Bug report #814069,
regarding python-six-whl and python-pip-whl: error when trying to install 
together
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.)


-- 
814069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pip-whl,python-six-whl
Version: python-pip-whl/8.0.2-3
Version: python-six-whl/1.10.0-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-02-08
Architecture: amd64
Distribution: sid

Hi,

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


Selecting previously unselected package python-pip-whl.
(Reading database ... 10940 files and directories currently installed.)
Preparing to unpack .../python-pip-whl_8.0.2-3_all.deb ...
Unpacking python-pip-whl (8.0.2-3) ...
Selecting previously unselected package python-six-whl.
Preparing to unpack .../python-six-whl_1.10.0-2_all.deb ...
Unpacking python-six-whl (1.10.0-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/python-six-whl_1.10.0-2_all.deb (--unpack):
 trying to overwrite 
'/usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl', which is also in 
package python-pip-whl 8.0.2-3
Errors were encountered while processing:
 /var/cache/apt/archives/python-six-whl_1.10.0-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

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

  /usr/share/python-wheels/six-1.10.0-py2.py3-none-any.whl

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

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Source: six
Source-Version: 1.10.0-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Feb 2016 09:18:14 -0500
Source: six
Binary: python-six python3-six pypy-six
Architecture: source all
Version: 1.10.0-3
Distribution: unstable
Urgency: medium
Maintainer: Barry Warsaw 
Changed-By: Barry Warsaw 
Description:
 pypy-six   - Python 2 and 3 compatibility library (PyPy interface)
 python-six - Python 2 and 3 compatibility library (Python 2 interface)
 python3-six - Python 2 and 3 compatibility library (Python 3 interface)
Closes: 814069
Changes:
 six (1.10.0-3) unstable; urgency=medium
 .
   * d/control:
 - Drop the python-six-whl binary package as it's no longer necessary.
   (Closes: #814069)
 - Drop the Build-Depends on python3-wheel.
   * d/rules: Drop override_dh_auto_install since we no longer need to
 build the 

Bug#814213: [PATCH 2/2] check-doc: Ignore with-aix-soname in check-cmdline-options-doc.sh

[Doug Torrance]

Control: tags -1 forwarded wmaker-...@lists.windowmaker.org

libtool 2.4.4 will add a --with-aix-soname option.  Ignore it when checking
whether INSTALL-WMAKER is up to date.

Fixes Debian bug #814213 [1].  Proposed fix to Debian package at [2].

   From: Chris Lamb 
   Subject: wmaker: FTBFS: Error: program option '--with-aix-soname' is not in
 the documentation './INSTALL-WMAKER'
   Date: Tue, 09 Feb 2016 09:59:14 +0100

   Dear Maintainer,

   wmaker fails to build from source in unstable/amd64:

 [..]

 make  check-local
 make[4]: Entering directory '/home/lamby/temp/
   cdt.20160209093619.fGSQWYa4PE/wmaker-0.95.7'
 ./script/check-cmdline-options-doc.sh \
--program "./configure" --text-doc "./INSTALL-WMAKER" \
--ignore-prg 'with-PACKAGE,without-PACKAGE # only template names from
  Autoconf' \
--ignore-prg 'program-prefix,program-suffix,program-transform-name
  # in INSTALL' \
--ignore-prg 'version,quiet,srcdir,build,host,cache-file,no-create
  # in INSTALL' \
--ignore-prg 'enable-silent-rules,disable-silent-rules # should be in
  INSTALL' \
--ignore-prg 'enable-dependency-tracking,disable-dependency-tracking
  # in INSTALL' \
--ignore-prg 'enable-shared,enable-static # should be in INSTALL' \
--ignore-prg 'disable-option-checking,enable-fast-install # should be
  in INSTALL' \
--ignore-prg 'disable-libtool-lock,with-pic,with-gnu-ld,with-sysroot
  # for libtool' \
--ignore-prg 'runstatedir #new in autoconf 2.70, backported in Debian' \
--ignore-prg 'with-x # no use, it would not work without X'
 Error: program option '--with-aix-soname' is not in the documentation
   './INSTALL-WMAKER'
 Makefile:951: recipe for target 'configure-documentation' failed
 make[4]: *** [configure-documentation] Error 1

 [..]

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814213
[2] http://anonscm.debian.org/cgit/pkg-wmaker/wmaker.git/commit/?id=dd955a7
---
 Makefile.am | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Makefile.am b/Makefile.am
index e925ab6..638cfed 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -107,6 +107,7 @@ configure-documentation:
--ignore-prg 'disable-option-checking,enable-fast-install # 
should be in INSTALL' \
--ignore-prg 
'disable-libtool-lock,with-pic,with-gnu-ld,with-sysroot # for libtool' \
--ignore-prg 'runstatedir #new in autoconf 2.70, backported in 
Debian' \
+   --ignore-prg 'with-aix-soname #new in libtool 2.4.4' \
--ignore-prg 'with-x # no use, it would not work without X'
 
 .PHONY: configure-documentation
-- 
2.5.0

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 814213 wmaker-...@lists.windowmaker.org
Bug #814213 [src:wmaker] wmaker: FTBFS: Error: program option 
'--with-aix-soname' is not in the documentation './INSTALL-WMAKER'
Set Bug forwarded-to-address to 'wmaker-...@lists.windowmaker.org'.
> thanks
Stopping processing here.

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

Bug#813125: pkg-php-tools for php7? [Was: phpcs upstream issue]

[David Prévot]

Hi,

> I guess nothing is stopping us to upload […]
> php-proxy-manager 2.0.0 to experimental.

Actually, it requires "php": "~7.0" in composer.json, that is currently
translated as php5-common (>= 7.0) by pkg-php-tools, and is thus is pretty
useless.

Mathieu, what are the blockers in pkg-php-tools preventing us from
starting the PHP 7 transition?

https://lists.debian.org/debian-devel-announce/2016/01/msg2.html

Regards

David

Bug#814272: simgrid: FTBFS: Could not figure the stack direction.

[Martin Quinson]

Hello,

On Tue, Feb 09, 2016 at 03:09:09PM -0500, Aaron M. Ucko wrote:
> 
> Automated builds of simgrid generally failed:

Yes, that hurts. It's all red! pitty.

>   ERRORCould not figure the stack direction.
>   -- LTO seems usable.
>   -- Add CFLAGS: "-g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -O3" to CMAKE_C_FLAGS
>   [...]
>   /«PKGBUILDDIR»/src/simix/smx_context.c:142:16: error: 'PTH_STACKGROWTH' 
> undeclared (first use in this function)
> 
> It's not entirely clear from the public logs what went wrong, but I
> suspect CMake may have tried to build prog_stackgrowth.c with -O3,
> which turns on -finline-functions, breaking the test.

Parallel building does not help here, for sure. And the diagnosis
further is complicated by the fact that my cmake output was broken
when the stack direction detection fails (I'm in the upstream team). 
I just commited a fix for that message, so that we get more info.

That is why the build starts even after the line "ERRORCould not
figure the stack direction", sorry.

Your analysis would be correct: these flags clearly break the stack
test. That is why they get added at the end of the configuration, once
all tests are ran. So, this is not it.

> The fallback
> logic didn't help even on the limited set of processor types it tried
> to cover because CMAKE_SYSTEM_PROCESSOR corresponds to the output of
> uname -p (typically "unknown" on Debian) rather than uname -m.

I would say that the fallback works, as it managed to compile on i386 ;)

But this is not an option, I'll investiguate further. Right now, I
forgot my laptop adapter at lab, and I will soon be offline... If you
want to give it a spin, the modified version is in the package git.

> Could you please take a look?

Many thanks to you for investigating so far. 

Bye, Mt.

-- 
It is not in improving the candle technology that 
electricty was discovered, understood and mastered.


signature.asc
Description: PGP signature

Bug#811172: Fixed upstream

[Tristan Seligmann]

This is fixed in e7316a1 [1] upstream, may be worth backporting that patch.

[1] https://bitbucket.org/durin42/hg-git/commits/e7316a1

Bug#770369: I may have a solution for the bug 770369

[S Andreason]

Arnaud Ceyrolle wrote:
Hello, I think I might have found why Eterm is behaving like this and 
have also a solution.


From the source tarball listed in the page:
https://packages.debian.org/jessie/eterm

at the link in the right :
eterm_0.9.6.orig.tar.gz 



My modification is to just change the line 1564 in src/command.c
from
unsigned short i;
to
unsigned long i;

and recompile, it works for me.

Let me know if it works for you.


Hi Arnaud,

Good job! That fixes the bug.
Eterm is working now.

Stewart

Bug#814276: Non-Free file: src/stdlib/SDL_qsort.c

[stressware2]

Package: libsdl2
Version: 2.0.2+dfsg1-6
Severity: serious

The file 'src/stdlib/SDL_qsort.c' in SDL2 seems to disallow
modification.

The Debian copyright file simply mentions the license as:

  You may use it in anything you like; you may make money
  out of it; you may distribute it in object form or as
  part of an executable without including source code;
  you don't have to credit me. (But it would be nice if
  you did.)'.

What it does not mention is the text before that:

  * This code may be reproduced freely provided
  *   - this file is retained unaltered apart from minor
  * changes for portability and efficiency
  *   - no changes are made to this comment
  *   - any changes that *are* made are clearly flagged
  *   - the _ID string below is altered by inserting, after
  * the date, the string " altered" followed at your option
  * by other material. (Exceptions: you may change the name
  * of the exported routine without changing the ID string.
  * You may change the values of the macros TRUNC_* and
  * PIVOT_THRESHOLD without changing the ID string, provided
  * they remain constants with TRUNC_nonaligned, TRUNC_aligned
  * and TRUNC_words/WORD_BYTES between 8 and 24, and
  *   PIVOT_THRESHOLD between 32 and 200.)'.

Although the file states 'You may use it in anything you like', it
either contradicts itself, or is simply talking about using the
unmodified file in any program you like. The part before that clearly
says that the file cannot be 'reproduced freely' unless '[the] file is
retained unaltered apart from minor changes for portability and
efficiency'.

Processed: bug 813973 is forwarded to https://github.com/dogecoin/dogecoin/issues/1325

[Debian Bug Tracking System]

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

> forwarded 813973 https://github.com/dogecoin/dogecoin/issues/1325
Bug #813973 [libbitcoinconsensus0,dogecoin] dogecoin and libbitcoinconsensus0: 
error when trying to install together
Set Bug forwarded-to-address to 
'https://github.com/dogecoin/dogecoin/issues/1325'.
> thanks
Stopping processing here.

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

Bug#811708: [PKG-OpenRC-Debian] Bug#811708: need help?

[Svante Signell]

On Mon, 2016-02-08 at 13:13 +0100, Svante Signell wrote:
> On Mon, 2016-02-08 at 08:26 +0100, Adam Borowski wrote:
> > > init-system-helpers: file conflict with openrc: /usr/sbin/update-rc.d
> > 
> > Uhm, guys... are you alive?  This bug keeps openrc uninstallable, and will
> > cause its autoremoval soon.
> > 
> > If you're too busy and need help, I could help with fixing or NMUing, but
> > you need to decide whether to:
> > * cooperate with init-system-helpers and put the logic there (like sysv-rc)
> > * divert update-rc.d (like file-rc)
> > 
> > Note that I'm not the best person to help, though, as I use openrc only on a
> > single desktop and thus don't know anything about its advanced features nor
> > internals.
> 
> Hi Adam,
> Cc: Roger
> 
> I sent the following mail to the openrc maintainers: Benda Xu, Thomas Goirand
> and Roger Leigh on Friday February 5th (no reply so far). The mail to Roger
> bounced, he is no longer a Debian maintainer.
> 
> > Hello,
> > 
> > Due to the serious bug 811708 openrc (0.18.3-1) will be removed from Debian
> > testing on February 18. In my opinion it would be a pity if it disappears.
> > 
> > Is it possible to do as file-rc (0.8.17) did in bug 812337: add a diversion?
> > 
> > From changelog: divert update-rc.d + invoke-rc.d files to cooperate with
> > init-
> > system-helpers =1.25. It seems like only divert() in preinst and
> > undivert() in
> > postrm scripts has to be created and called.

Attached are patches of debian/changelog and new files debian/preinst and
debian/postrm. Maybe the debian/control file has to be modified too. Are they
sufficient to create a diversion of openrc so that bug 811708 can be closed? I
have not yet had time to test-install, the plan is to do that for GNU/Linux and
GNU/Hurd.

--- a/debian/changelog.orig	2015-11-09 15:11:35.0 +0100
+++ b/debian/changelog	2016-02-09 22:41:37.0 +0100
@@ -1,3 +1,11 @@
+openrc (0.18.3-2) unstable; urgency=medium
+  * Create debian/{preinst,postrm} scripts as for file-rc to
+divert update-rc.d + invoke-rc.d files to cooperate with
+init-system-helpers >=1.25
+(Closes: #811708)
+
+ -- Svante Signell   Tue, 09 Feb 2016 16:53:58 +0100
+
 openrc (0.18.3-1) unstable; urgency=medium
 
   [ Dmitry Yu Okunev ]


postrm
Description: application/shellscript


preinst
Description: application/shellscript

Bug#790271: Fix build failure in stable/jessie

[Petter Reinholdtsen]

[Petter Reinholdtsen]
> I do not remember the procedure for getting changes into stable, but
> hope to find time to investigate that some time in the future.

I did, and submitted https://bugs.debian.org/814266 > to request
an update.  If it is accepted, we can upload to stable to get the fix
into the next point release.

-- 
Happy hacking
Petter Reinholdtsen

Processed: bug 813974 is forwarded to https://github.com/dogecoin/dogecoin/issues/1325

[Debian Bug Tracking System]

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

> forwarded 813974 https://github.com/dogecoin/dogecoin/issues/1325
Bug #813974 [libbitcoinconsensus-dev,dogecoin] dogecoin and 
libbitcoinconsensus-dev: error when trying to install together
Set Bug forwarded-to-address to 
'https://github.com/dogecoin/dogecoin/issues/1325'.
> thanks
Stopping processing here.

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

Bug#814272: simgrid: FTBFS: Could not figure the stack direction.

[Aaron M. Ucko]

Martin Quinson  writes:

> I would say that the fallback works, as it managed to compile on i386 ;)

It failed on kfreebsd-* with this same error, though.

> Many thanks to you for investigating so far. 

Thanks for the quick response.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#813770: marked as done (gitlab_url for gitlab-shell is set incorrectly only GITLAB_HOST is set and host is not set in gitlab.yml)

[Debian Bug Tracking System]

Your message dated Tue, 09 Feb 2016 19:05:01 +
with message-id 
and subject line Bug#813770: fixed in gitlab 8.4.3+dfsg-1
has caused the Debian Bug report #813770,
regarding gitlab_url for gitlab-shell is set incorrectly only GITLAB_HOST is 
set and host is not set in gitlab.yml
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.)


-- 
813770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: gitlab
severity: grave
version: 8.4.0+dfsg-2

though a simple fix exist, it makes the default installation unusable.
If you change gitlab_url in /usr/share/gitlab-shell/config.yml, things
start working.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 8.4.3+dfsg-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated gitlab package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Feb 2016 23:39:34 +0530
Source: gitlab
Binary: gitlab
Architecture: source all
Version: 8.4.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code
Closes: 812861 813770 813807
Changes:
 gitlab (8.4.3+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
   * Refresh patches (rails version is in sync)
   * Configure ssl for nginx if selected
   * Use letsencrypt certificate paths if selected
   * Add git as dependency (Closes: #813807)
   * SSH key upload is working (Closes: #812861)
   * Configure gitlab_url as workwround (Closes: #813770 )
Checksums-Sha1:
 f0e26b3bbc7fc261375996ffeadd1be9dbc119ee 2058 gitlab_8.4.3+dfsg-1.dsc
 46df20cdaf8c6fba49cfb20a6b60741ec6c93762 12214011 gitlab_8.4.3+dfsg.orig.tar.gz
 6003648efdccc328de8c328f4fc53f8bcd214bfd 31084 
gitlab_8.4.3+dfsg-1.debian.tar.xz
 01b5a61e2cc7ecf28cdced09de336511bb4d97a7 11470484 gitlab_8.4.3+dfsg-1_all.deb
Checksums-Sha256:
 a2f92c4c7fe98a8d31c88cc379aabdf93cbb466f2a2e1b6ef83adddcaa745b46 2058 
gitlab_8.4.3+dfsg-1.dsc
 91e28c1d8c5a628d21a45afb4f5d91f955d2c580f5e1a4ec8ffa703de447f3e9 12214011 
gitlab_8.4.3+dfsg.orig.tar.gz
 f81b70cd1858283a46dc70c8a9efc958b0dd42d972abf5d65bbe72cfc6e56779 31084 
gitlab_8.4.3+dfsg-1.debian.tar.xz
 d7211a4aa752c39e779b59b74695f56ce3c747f4bb71ec90cdcdf412590cae60 11470484 
gitlab_8.4.3+dfsg-1_all.deb
Files:
 915d968a10b1506b86f0ec87db224b7e 2058 ruby optional gitlab_8.4.3+dfsg-1.dsc
 f3e527687718d52925401bf657d113b0 12214011 ruby optional 
gitlab_8.4.3+dfsg.orig.tar.gz
 a80d7d546430587626a2cff14805dc46 31084 ruby optional 
gitlab_8.4.3+dfsg-1.debian.tar.xz
 8fc94fc62f6ce1c8d5dcce940eac80a6 11470484 ruby optional 
gitlab_8.4.3+dfsg-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWujMKAAoJEM4fnGdFEsIqsa0P/RFZUgTjTQA3diItcOQoRNl7
BHEn5aQ2l4dV4gA334faLIn+/TsvGGbla9WR9nnmghDHGS+Zk/9GGRPzOTh3yjnD
QIW+Kvk/U83ATxNQWrJIN84eUy1IG+DHc4G+DnX/jPMthY8HXFiY8F/IHcTeK908
RRBH0cjjSl0FVQbAtXqNihJ9UJFhdbKn+iWXMtSs71sTcqrwyrkNTf86Q4JstMZs
Yc/HWpJQJLoxFF9Uuoyy7WJTHhP2uK0BH53oJJBkD8ixvAUZTuaZ5afuPn1JqfF2
h88+aG+XtL1yYgkNBQe4l0QMsX9ox8NAicnWWkKTF/zjFcUzI/fGwP7t5w0ct7n+
sHLNNREpy5w9sVj7YR/8EHWwNXKt4arAOnK3Re+wjQPnFcWx4coT7hewMBCt3J4D
wCFDSqqglU5OXUhCGNsm/aU08o702wBPlrgsMmE6OsFuZD2UyiisE/t5a7A0cDHI
1zcf0Iq2hk+5Fin5O8My/vA76uGGcWLzZ1kUyP6PzhZ4aDpzuwewEL6AxoEaFHGK
mHGHkJ2KIA/MSd8lKSWqexIHSZbd0mKAL2N1sXUKyCs3HI38gtXrze5hjbi09Ks3
bSThWtIEgz9jeLri/F5R2k8uIxKNRa2oIaeRIlc4fIzH+fi4o8nUFZJehzjqtO7x
VwK2whU8H1AzzLjqUdNQ
=auom
-END PGP SIGNATURE End Message ---

Bug#791232: openvrml NMU

[Wookey]

OK. I just tested the fixes in openvrml for building on new arches (arm64, 
ppc64le, ppc64)
And I included the java fixes so that it would build.
But now neither of us can upload our NMU due to this g++-5 ABI issue.

The maintainer seems to be MIA (Sam - are you out there?) so I'd very
much like to just upload something if we can.

If we were really keen we'd do a library transition just to be on the
safe side. Does anyone know what's involved with that?

openvrml is kind of old and unloved these days, but I would expect
some software to be using it as it's a file format still supported by
some things. libg3d, meshlab and openscenegraph claim vrml support for
example? Did they drop it, do we not build the osg-vrml plugin,
perhaps they have internal code for reading? These are questions the
maintainer should be able to help answer.

I've tried a build but it failed after the src build, because debian
patches back in Makefile.am a 'lookat' target into, the source file
for which was removed in 2006! after dh_autoreconfing this gets back
into the build and it barfs.

GUess I'd better fix that and try again...

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: Digital signature

Bug#814272: simgrid: FTBFS: Could not figure the stack direction.

[Aaron M. Ucko]

Source: simgrid
Version: 3.12-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Automated builds of simgrid generally failed:

  ERRORCould not figure the stack direction.
  -- LTO seems usable.
  -- Add CFLAGS: "-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -O3" to CMAKE_C_FLAGS
  [...]
  /«PKGBUILDDIR»/src/simix/smx_context.c:142:16: error: 'PTH_STACKGROWTH' 
undeclared (first use in this function)

It's not entirely clear from the public logs what went wrong, but I
suspect CMake may have tried to build prog_stackgrowth.c with -O3,
which turns on -finline-functions, breaking the test.  The fallback
logic didn't help even on the limited set of processor types it tried
to cover because CMAKE_SYSTEM_PROCESSOR corresponds to the output of
uname -p (typically "unknown" on Debian) rather than uname -m.

Could you please take a look?

Thanks!

Bug#813125: phpcs upstream issue [was: php-proxy-manager 2.0.0* has a dependency on a new PHP API PackageVersions]

[Nish Aravamudan]

On 09.02.2016 [15:17:17 -0400], David Prévot wrote:
> Hi Nish,
> 
> Le 09/02/2016 15:05, Nish Aravamudan a écrit :
> 
> > I was finally able to get to this, and I see build failures using that
> > base (due to phpcs issues):
> > 
> > phpcs --standard=PSR2 ./src/
> […]
> > I can fix this up on my end by putting in a staged build, but it seems
> > like something needs to be fixed still?
> 
> That’s probably caused by a new issue in php-codesniffer 2.5.1, e.g.,
> 
> https://github.com/squizlabs/PHP_CodeSniffer/issues/876

Did you mean an issue with 2.5.0?

> FWIW, the build runs fine with php-codesniffer 2.5.1 (not in the
> archive, but I can push my update to the VCS if you wish), but
> php-codesniffer 2.5.1 does break other packages build, so I’d prefer to
> see an upstream php-codesniffer (and php-proxy-manager) fix before
> uploading it (unless I push both to experimental for the time being,
> would that be useful?).

Well, for the purposes of syncing with Debian, it's probably only worth
pushing something to experimental once upstream has the fixes in, I
agree. I'll just wait on those and I'll request a sync once Debian
updates.

-Nish

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd

Bug#813125: phpcs upstream issue [was: php-proxy-manager 2.0.0* has a dependency on a new PHP API PackageVersions]

[David Prévot]

Hi Nish,

> On 09.02.2016 [15:17:17 -0400], David Prévot wrote:
>> Le 09/02/2016 15:05, Nish Aravamudan a écrit :
>>
>>> I was finally able to get to this, and I see build failures using that
>>> base (due to phpcs issues):
[…]
>>> I can fix this up on my end by putting in a staged build, but it seems
>>> like something needs to be fixed still?
>>
>> That’s probably caused by a new issue in php-codesniffer 2.5.1, e.g.,
>>
>> https://github.com/squizlabs/PHP_CodeSniffer/issues/876
>
> Did you mean an issue with 2.5.0?

No. I believed 2.5.1 introduced an indent issue, and that
php-proxy-manager was (probably automatically, with phpcbf) fixed to use
the new (broken) phpcs behavior. I just run phpcbf/2.5.0 and now believe
that I was wrong, so I’ll have a closer look at what broke with
phpcs/2.5.1, and may upload the updated packages, or file/document a
proper upstream issue.

Regards

David

Bug#814183: openmpi 1.10.2 is broken on powerpc

[Graham Inggs]

Petsc rebuilt successfully [1] a couple of hours ago on poulenc.d.o. [2].
My previous tests were done on partch.d.o. [3].  Partch has 2GB of RAM
vs Poulenc's 5GB, I don't know if this is significant.


[1] 
https://buildd.debian.org/status/fetch.php?pkg=petsc=powerpc=3.6.2.dfsg1-3%2Bb3=1455016089
[2] https://db.debian.org/machines.cgi?host=poulenc
[3] https://db.debian.org/machines.cgi?host=partch

Bug#812750: wine: Gecko integration is broken

[Stephen Kitt]

On Tue, 9 Feb 2016 21:06:29 +0100, Stephen Kitt  wrote:
> * updating the licensing information for each new wine-gecko release is
>   extraordinarily time-consuming, on the order of 150-200h per release (and
>   even then I miss issues) – TBH I've stalled on this, I'm thinking of

Just to be clear, I haven't spent that amount of time on any release yet,
that's just what 2.40 feels like (I'm about a quarter of the way through).

Stephen


pgp4M54NQjm8R.pgp
Description: OpenPGP digital signature

Processed: severity of 813601 is minor

[Debian Bug Tracking System]

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

> severity 813601 minor
Bug #813601 {Done: Ben Hutchings } [src:linux] 
linux-image-3.16: kernel panic when umounting rootfs
Severity set to 'minor' from 'critical'
> thanks
Stopping processing here.

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

Bug#796118: dnscache is buggy (failing to resolve indymedia.org)

[Robert Edmonds]

Daniel Kahn Gillmor wrote:
> Following up on the discussion about dnscache problems in
> https://bugs.debian.org/796118:
> 
> dnscache is, sadly, buggy even beyond the concerns about cache
> poisoning.  It is unable to resolve the domain name indymedia.org, while
> other DNS resolvers like unbound can do.

Hi, Daniel:

I suspect this issue is caused by a design flaw in dnscache: it has a
hardcoded maximum amount of "gluelessness" that it will tolerate from
domains that aren't set up using the preferred DJB style of
"in-bailiwick servers with glue":

[...]

``As far as I know, the Internet has not yet lost any domains to
gluelessness,'' I wrote in 2000. ``But there are an increasing
number of glueless domains, and I've spotted a glueless domain with
glueless DNS servers. How much gluelessness must a cache tolerate?
Currently dnscache allows three levels of gluelessness. This seems
to be enough for now, but will it be enough in the future?''

[...]

I recommend that all DNS servers be in-bailiwick servers with glue.
External DNS servers should be given internal names, with address
records copied automatically (preferably by some secure mechanism)
from the external names to the internal names.

DNS should have been designed with addresses, not names, in NS
records and MX records. The ``additional section'' of DNS responses
should have been eliminated. RFC 1035 observes correctly that NS
indirection and MX indirection ``insure [sic] consistency'' of
addresses; however, this indirection should have been handled by the
server, not the client. [...]

-- "Gluelessness" from http://cr.yp.to/djbdns/notes.html

The static "gluelessness" limit (QUERY_MAXLEVEL in the source) was later
increased from 3 to 5, about 15 (!) years ago:

20010105
ui: increased MAXLEVEL to 5. the Internet is becoming more
glueless every day.

-- "CHANGES" from src:djbdns-1.05

The "QUERY_MAXLEVEL" constant in the source is then used to allocate
statically sized arrays when spawning query objects.  (Some servers that
used a more flexible design that permitted more gluelessness had to be
hardened recently, though: https://www.kb.cert.org/vuls/id/264212.)  You
could probably patch dnscache to increase this number by a small amount
in order to tolerate slightly more gluelessness, but increasing it by a
large amount would waste memory, due to the statically sized arrays.  If
I understand correctly, BIND and Unbound have various per-resolution
counters that might permit something like an order of magnitude more
"gluelessness".

I might be wrong, but it looks like it's possible for indymedia.org to
exceed the gluelessness limit when resolving one of its nameservers,
ns2.fs-dl.net.  At least, if you grep your dnscache log:

grep ^cached dnscache.indymedia.org.log | sort -u

It looks like it was able to find an address record for ns2.riseup.net
but not ns2.fs-dl.net.  But if that's the case, why didn't it at least
try to resolve indymedia.org using the one nameserver address that it
found?  (I suspect it may have found the non-authoritative glue record
for ns2.riseup.net but wasn't able to find the authoritative address
record.)

ns2.riseup.net is 204.13.164.8, which is cc0da408 in DJB's IPv4
presentation format.  ns2.fs-dl.net is 147.95.16.164, which is 935f10a4
in DJB.  dnscache never tries to contact those servers in your log:

edmonds@chase{0}:/tmp$ grep ^tx dnscache.indymedia.org.log | grep cc0da408
edmonds@chase{1}:/tmp$ grep ^tx dnscache.indymedia.org.log | grep 935f10a4
edmonds@chase{1}:/tmp$ 

I agree with your conclusion that dnscache is buggy.  There are many
domains on the Internet that rely on amounts of gluelessness beyond the
small amount that dnscache is willing to tolerate.  The operators of
those domains still get good performance from modern DNS resolvers and
the DNS standards do not specify concrete upper or lower bounds on the
amount of gluelessness that must be supported by resolvers.  So I don't
see a good standards-based argument that those operators are doing
something wrong.

-- 
Robert Edmonds
edmo...@debian.org

Bug#809263: [Pkg-opencl-devel] Bug#809263: Bug#809263: beignet: FTBFS: /usr/include/CL/cl_egl.h:31:21: fatal error: EGL/egl.h: No such file or directory

[J Price]

On 25 January 2016 at 07:29, Rebecca N. Palmer  wrote:
> What's the status of this?  Nothing has happened in either the upstream or
> Debian repositories.

Sorry for the lack of activity here - internal review of this took
much longer than I expected. This change has now been pushed to the
Khronos public GitHub (for OpenCL 1.2, 2.0 and 2.1):
https://github.com/KhronosGroup/OpenCL-Headers/commit/c1770dcc6cf1daadec1905e7393f3691c1dde200

The khronos-opencl-headers package hasn't yet been updated to use the
GitHub repository as the upstream sources, so if an urgent fix is
required it may be best to simply patch the header for now as Vincent
proposed.

James

Bug#808906: marked as done (gnome-shell-extensions: overwriting /usr/share/gnome-shell/theme/calendar-today.svg)

[Debian Bug Tracking System]

Your message dated Wed, 10 Feb 2016 00:49:06 +
with message-id 
and subject line Bug#808906: fixed in gnome-shell-extensions 3.18.3-2
has caused the Debian Bug report #808906,
regarding gnome-shell-extensions: overwriting 
/usr/share/gnome-shell/theme/calendar-today.svg
to be marked as done.

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

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


-- 
808906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: gnome-shell-extensions
version: 3.18.2-1
severity: serious

Hi,

seen on 
https://jenkins.debian.net/job/chroot-installation_jessie_install_gnome_upgrade_to_stretch/64//console
today:

[...]
Preparing to unpack .../gnome-shell-extensions_3.18.2-1_all.deb ...
Unpacking gnome-shell-extensions (3.18.2-1) over (3.14.2-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/gnome-shell-extensions_3.18.2-1_all.deb (--unpack):
 trying to overwrite '/usr/share/gnome-shell/theme/calendar-today.svg', which 
is also in package gnome-shell-common 
3.14.4-1~deb8u1
Preparing to unpack .../gnome-shell-common_3.18.1-1_all.deb ...
Unpacking gnome-shell-common (3.18.1-1) over (3.14.4-1~deb8u1) ...
[...]
Errors were encountered while processing:
 /var/cache/apt/archives/gnome-shell-extensions_3.18.2-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extensions
Source-Version: 3.18.3-2

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extensions, 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.
Andreas Henriksson  (supplier of updated 
gnome-shell-extensions 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, 10 Feb 2016 01:24:42 +0100
Source: gnome-shell-extensions
Binary: gnome-shell-extensions
Architecture: source all
Version: 3.18.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Andreas Henriksson 
Description:
 gnome-shell-extensions - Extensions to extend functionality of GNOME Shell
Closes: 808906
Changes:
 gnome-shell-extensions (3.18.3-2) unstable; urgency=medium
 .
   * Add Breaks/Replaces gnome-shell-common (<< 3.18) (Closes: #808906)
 - Helps upgrades from Jessie by allowing overwriting
   /usr/share/gnome-shell/theme/calendar-today.svg et.al.
   which was previously shipped in gnome-shell-common.
Checksums-Sha1:
 0ffa261d59bd25a9ab043094cfdfeed22daab31e 2415 
gnome-shell-extensions_3.18.3-2.dsc
 012bbbf3e01fa86a6d7ac603c9541ded5dc495be 6000 
gnome-shell-extensions_3.18.3-2.debian.tar.xz
 d92b39c783c4ea46fc45c0c7660b2dc4d4e282fe 159690 
gnome-shell-extensions_3.18.3-2_all.deb
Checksums-Sha256:
 8b2e400a29f47ebaa8a26aac203fe2106657908a9c57665dd45d8c8246532c52 2415 
gnome-shell-extensions_3.18.3-2.dsc
 e2277013f9b973158e18a70c243d5dae4fb39d2770f5e0e82fef01d87c493cad 6000 
gnome-shell-extensions_3.18.3-2.debian.tar.xz
 5f7696c1b7b2c5986410f392443ac282b900df702f7cfb33cbe34d2c28e073ef 159690 
gnome-shell-extensions_3.18.3-2_all.deb
Files:
 03ee15f6bd0d53034fa496140f587158 2415 gnome optional 
gnome-shell-extensions_3.18.3-2.dsc
 5e2004d29906d99d964c7e4ab4ef862c 6000 gnome optional 
gnome-shell-extensions_3.18.3-2.debian.tar.xz
 98f9f3a2959cfee9b92818a0780ba97f 159690 gnome optional 
gnome-shell-extensions_3.18.3-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWuoVmAAoJEAvEfcZNE1MG3iYP/2Zs9l3ll00rcBjg/HHLuBNp
AwGzNKeXPhxnWn4zNKTVNhY3GHKUkt6fVhmBlRMSfBljLEWDVYJNMweZq2N8bhR6
a3tRLpr5X5k7RlOGCR+GBe9IkqPRHxPsV9edmsnieHhjNMg2EDHKio8J78XfoSSH
r7kEzlsrraAoAqiCLIzLBP5baYPK6t2tBdwSkYJcD3eNTR6cFCNFjvBU7l5Zfxvz
4IVqwLXp9KJVPHXWORv112EkSGqWdUnQsk0LUCNKy3TWKn6v1tjMeTn4N1ZKN4C0
qNFkpA2bVAM/dBSlZuLMfARE3j1fd8EGl0Y4YGQ7R53twiQWgPXx0aG2gdjpWhZO
L4fzfAmlUsw3wUgJpKd+ed+v7I7YQATNT89V1XTgXA6DVG3pWEe98LDh2n0UMzVC

Bug#808920: calligrastage not installable / [calligra-libs] not installable

[peter green]

If you use and care about calligra can you please try building with the 
patch I posted at


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797389#17

And tell me

1. Is that patch still sufficient to make the package build in current sid?
2. Are the resulting packages installable?
3. Do the resulting packages actually work?

If I can get some confirmation that the patch results in packages that 
actually works then I will NMU my patch.

Bug#792171: util-linux - sulogin, no way to continue

[Andreas Henriksson]

Control: tags -1 + upstream help
Control: severity -1 wishlist
Control: retitle -1 sulogin: no way to continue on dumb terminals (s390*)

Hello Bastian Blank.

Thanks for your bug report, and sorry for the late reply

On Sun, Jul 12, 2015 at 01:42:29PM +0200, Bastian Blank wrote:
> Package: util-linux
> Version: 2.26.2-6
> Severity: grave
> 
> sulogin have no other way then Ctrl-D to continue.  On s390* only dumb
> terminals without any control characters exists, so there is no way to
> provide this input.

... but I personally have no interest in s390* and apparently this bug
report hasn't generated anyone else to jump on fixing this either
(despite having it sit at grave severity for a long time to make it as
discoverable as possible).

I would like to consider this a problem that s390* porters should work
out together with upstream. (Feel free to poke me once this is sorted
out upstream if you consider backporting it urgent enough to not wait
for next upstream stable release.) It's in my opinion a new feature
since sulogin has as far as I know never supported anything but non-dumb
terminals. Either way I doubt this would be considered a release
blocker by the release team if there genuinely is noone willing to fix
this. If you disagree, please ask their opinion and quote it here.

I'm thus tagging and adjusting severity accordingly.

Regards,
Andreas Henriksson

Processed: Re: util-linux - sulogin, no way to continue

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream help
Bug #792171 [util-linux] util-linux - sulogin, no way to continue
Added tag(s) upstream and help.
> severity -1 wishlist
Bug #792171 [util-linux] util-linux - sulogin, no way to continue
Severity set to 'wishlist' from 'grave'
> retitle -1 sulogin: no way to continue on dumb terminals (s390*)
Bug #792171 [util-linux] util-linux - sulogin, no way to continue
Changed Bug title to 'sulogin: no way to continue on dumb terminals (s390*)' 
from 'util-linux - sulogin, no way to continue'

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

Bug#796118: Re: Should djbdns be removed?

[Robert Edmonds]

Hi, Matija:

Matija Nalis wrote:
> On Tue, Oct 06, 2015 at 04:26:49PM +0200, Ondřej Surý wrote:
> > > On Tue, Sep 08, 2015 at 08:29:18PM +0200, Moritz Mühlenhoff wrote:
> > > > On Wed, Aug 19, 2015 at 05:45:30PM +0200, Moritz Muehlenhoff wrote:
> > > > > djbdns is RC-buggy for many years now and was out of testing since 
> > > > > 2009.
> > > > > Should we remove it from unstable?
> > > 
> > > No, I don't think so.
> > 
> > Any solid arguments supporting your opinion?
> > 
> > djbdns is RC buggy, upstream orphaned, outdated, has to be heavily
> > patched, doesn't support recent DNS standards and it still even carries
> > old J-ROOT IP address that was decommissioned a ***13*** years ago.
> 
> dnscache component only is RC-buggy. The solution has been proposed
> by Robert Edmonds (remove only buggy component /usr/bin/dnscache).
> 
> It is not upstream orphaned.

As far as I can tell, the only maintenance activity that djbdns has
received from its upstream developer has been the release of a two-line
patch, about 7 years ago:

http://marc.info/?l=djbdns=123613000920446=2

That email states that "The next release of djbdns will be backed by a
new security guarantee", but no new release has been published since
then.  The latest version on cr.yp.to is still djbdns 1.05, released
about 15 years ago, so presumably the original djbdns security guarantee
is still in effect:

https://cr.yp.to/djbdns/guarantee.html

The only upstream maintenance attention djbdns has received in the past
15 years has been related to the security guarantee, and that security
guarantee is very narrowly tailored to problems that DJB finds
worthwhile; attacks enabled by the ease of forging UDP packets on the
Internet, or denial-of-service attacks are both specifically excluded
classes of problems.

Other routine maintenance such as updating the list of root nameserver
address hints has simply been neglected.  E.g., the dnsroots.global file
shipped in djbdns-1.05 lists five IP addresses (out of thirteen) that
are no longer official root server IP addresses, if I counted correctly.
Developers of actively maintained recursive DNS servers promptly update
these values in their next scheduled release, especially after the
widely publicized "old L-root" incident:

http://research.dyn.com/2008/05/identity-theft-hits-the-root-n-1/

djbdns may not be "orphaned" upstream in the literal definition, but it
is certainly unmaintained by now.

> It is just stable piece of software which does not change often, as it
> was engineered on KISS principle, so it does not *need* to be changed.
> That is great engineering feat, and I'd love if way more software
> would be like that instead of having everincreasing featurecreep.

Many djbdns users speak about how well engineered or elegant the servers
are, but I suspect this comes from the experience of configuring the
daemons (which have very few configuration knobs compared to other DNS
implementations), rather than reading the code.  Here are comments from
a security researcher with extensive experience analyzing source code:

tptacek 2304 days ago

DJB's code is a lot of things, but when someone says "beautiful" is
one of them, I start thinking about how I might quiz them to get
them to prove that they've actually read it. Smarter coders than me
have sat in rooms for nightlong studies of qmail and come to the
conclusion that, while clever, the C code in qmail and djbdns has
clearly been compiled down from some higher level language[1]. If
that code is anything, it is idiosyncratic.

[1] Having asked this question directly to DJB in person, I can say
that I am at least convinced he wrote this stuff in C.

[...]

tptacek 2304 days ago

The formatting, the heavy reliance on idiosyncratic CPP macros,
and more than anything else the repetitively procedural nature
of it is what set off alarm bells for us.

But really that's just the way he codes. It's very intricate.
It's like a very ugly Swiss watch.

[...]

(https://news.ycombinator.com/item?id=890558)

> I do not know why you think it *has* to be heavily patched. 
> It works for me without patching just fine, for example.

Many users have requirements that are not satisfied by the original
djbdns-1.05 source release.  For example, the following post from a
Facebook developer mentions that tinydns is used at Facebook, with
multiple patches, including an in-house IPv6 support patch:


https://lists.dns-oarc.net/pipermail/dns-operations/2016-February/014250.html

> The recent DNS standards (DNSSEC, I assume) it doesn't support is by
> design, as it is deemed broken by upstream author (see
> http://dnscurve.org/ for more details, for example) and the whole
> point of KISS principle is to keep it simple and use modular design
> for extra bloat if wanted (for example, even DJB's dnscurve is to be 
> implemented as separate independent software 

Processed: Re: Bug#808866: (snappy:15699): Clutter-CRITICAL **: The Clutter backend is not a X11 backend

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #808866 [snappy] (snappy:15699): Clutter-CRITICAL **: The Clutter backend 
is not a X11 backend
Added tag(s) confirmed.
> found -1 snappy/0.3.7-1.1
Bug #808866 [snappy] (snappy:15699): Clutter-CRITICAL **: The Clutter backend 
is not a X11 backend
The source snappy and version 0.3.7-1.1 do not appear to match any binary 
packages
Marked as found in versions snappy/0.3.7-1.1.

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