Bug#867969: ITP: sdformat5 -- Simulation Description Format (SDF) parser

[Jose Luis Rivero]

Package: wnpp
Severity: wishlist
Owner: Jose Luis Rivero <jriv...@osrfoundation.org>

* Package name: sdformat5
Version   : 5.1.0
Upstream Author   : Open Source Robotics Foundation
* URL : http://sdformat.org
* License : BSD
Programming Lang  : C++
Description   : Simulation Description Format (SDF) parser

SDF is an XML file format that describes environments, objects, and
robots in a manner suitable for robotic applications. SDF is capable of
representing and describing different physic engines, lighting
properties, terrain, static or dynamic objects, and articulated robots
with various sensors, and acutators.  The format of SDF is also
described by XML, which facilitates updates and allows conversion from
previous versions. A parser is also contained within this package that
reads SDF files and returns a C++ interface.

Version 4 is already in debian.

Bug#867968: ITP: ign-transport3 -- Ignition Transport library v3

[Jose Luis Rivero]

Package: wnpp
Severity: wishlist
Owner: Jose Luis Rivero <jriv...@osrfoundation.org>

* Package name: ign-transport3
  Version : 3.0.1
  Upstream Author : Open Source Robotics Foundation
* URL : http://ignitionrobotics.org/libraries/transport
* License : Apache
  Programming Lang: C++
  Description : Transport library which combines ZeroMQ and Protobuf

ignition transport library combines ZeroMQ with Protobufs to create a
fast and efficient message passing system. Asynchronous message
publication and subscription is provided along with service calls and
discovery.

The version 1 is already in Debian. Here is the version 3.

Bug#867757: Updating the powertop Uploaders list

[Jose-Luis Rivas]

Sure, will do.

On 09/07/17, 10:56, Tobias Frost wrote:
> Source: powertop
> Version: 2.8-1
> Severity: minor
> User: m...@qa.debian.org
> Usertags: mia-teammaint
> 
> Patrick Winnertz  has not been working on
> the powertop package for quite some time.
> 
> We are tracking their status in the MIA team and would like to ask you
> to remove them from the Uploaders list of the package so we can close
> that part of the file.
> 
> (If the person is listed as Maintainer, what we are asking is to please
> step in as a new maintainer.)
> 
> Thanks.



-- 
⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co

Bug#866783: RFS: gigalomania/0.28+git.20170219.g08f4811-1 [ITP]

[Jose G. López]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: debian-devel-ga...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "gigalomania":

* Package name: gigalomania
  Version : 0.28+git.20170219.g08f4811-1
  Upstream Author : Mark Harman 
* URL : http://gigalomania.sourceforge.net
* License : GPL-2+, CC0, CC BY 3.0 and zlib License
  Section : games

It builds those binary packages:

  gigalomania - Mega-Lo-Mania-like god game
  gigalomania-data - Mega-Lo-Mania-like god game (data files)

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/gigalomania

Alternatively, one can download the package with dget using this
command:

  dget -x 
https://mentors.debian.net/debian/pool/main/g/gigalomania/gigalomania_0.28+git.20170219.g08f4811-1.dsc

Package development is on the following repo:

https://gitlab.com/deb-pkg/gigalomania

Changes since the last upload:

gigalomania (0.28+git.20170219.g08f4811-1) unstable; urgency=medium

  * Initial release. (Closes: #865784)

Regards,


pgpJ0rBtclSAP.pgp
Description: PGP signature

Bug#865979: at: patch for adding -s option to silence standard messages

[Jose M Calhariz]

Thank you.  Your patch seams good and I will add it to the next release
of at.

Kind regards
Jose M Calhariz


On 26/06/17 10:34, Paul Slootman wrote:
> Package: at
> Version: 3.1.20-3
> Severity: wishlist
> Tags: patch
>
> I use at from cronjobs (I can't use cron directly because the cronjob
> calculates the time according to sunrise / sunset). I think it's silly
> that at always outputs two lines to stderr and that there's no way to
> prevent this; I don't need to know the job number and that the script
> will be run using /bin/sh, thank you very much; I know that by now.
>
> I've added an option -s for silent that suppresses these two output
> lines. Please consider adding this to the official build.
>
> Thanks,
> Paul Slootman
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers oldoldstable
>   APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'oldstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.11.3-wurtel-ws (SMP w/8 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: sysvinit (via /sbin/init)
>
> Versions of packages at depends on:
> ii  init-system-helpers  1.48
> ii  libc62.24-11
> ii  libpam-runtime   1.1.8-3.6
> ii  libpam0g 1.1.8-3.6
> ii  libselinux1  2.6-3+b1
> ii  lsb-base 9.20161125
>
> Versions of packages at recommends:
> ii  exim4-daemon-heavy [mail-transport-agent]  4.89-2
>
> at suggests no packages.
>
> -- Configuration Files:
> /etc/at.deny [Errno 13] Permission denied: '/etc/at.deny'
>
> -- no debconf information





signature.asc
Description: OpenPGP digital signature

Bug#862321: libdesktop-notify-perl: Please package 0.05 upstream release

[Jose Miguel Parrella Romero]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 6/24/2017 1:31 PM, intrigeri wrote:
 > Therefore, I intend to adopt this package under the umbrella of the
 > pkg-perl team if I get no reply before the beginning of DebConf17.

You should move forward and adopt libdesktop-notify-perl.

I'm active in areas other than packaging at this time.

Thanks for stepping up and for your contributions to Debian,
bureado

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJZUGU+AAoJEMAyQqmI1LffkrYP/1Gn3XGw+Tqd3ssI3UJHu+sc
TI1dWkWi+uRt5Mcg3LQaqkzUetmF5pWoY//9xLOi4QU2vQ9vGN99C7gE/UCAzpTH
0zQwNol+RYyob04bayCS8arvy9Ee+j7fj83IjD47dXJiA2I8nOg6G3L9swq+FQzd
MjECZnz+fmaa64MQtlfuHjzLbX58E2ZmIlY2PQHVgd4uD9idNFFz5lCZvqZb0+oh
3ZAxZ9Qcr7qw0WiSV8SaIWWVSF9GmzrhB1mVIJAIqFXJQ6QJJU2AuEmyFOZdn+ds
ELOu/UurO6yo9J0r0NHInCj3c5+VR7TNU13V95nrK3XaiVv5Yq6+ZNHAhbELdGtc
M7YPeencVgFEQwATtHI6EWflNJgA1o7py1X1HyQQNbiWfjc5Uy6j18DZGSLKYRyl
tHmTaNpmmB+orSD67ryzXaAmdSmyyhXvRmzZZiUOlSeupqFbHcs/vUKSdxyPkhke
e5FqEmeGV3II6a/S+B3QcJnx29KkC1Zz5eDAeCxoEaFh6EbkfV8F4asO+pElNKJG
7gPPm8g0v0zgKhAevxVoTwqd51VBJGs9YF626vNnCDT2FoMGXtiZAWFdFOaEFDlE
dvbeh7eWuh1D5XVnHSSKZ3+kSjKBXsziFUxUXOKxjxlTIE5q5dVEcRBM+yePcmzI
Pv81i5NH9+8Ik3GyDF6g
=bxtc
-END PGP SIGNATURE-

Bug#865784: ITP: gigalomania -- Mega-Lo-Mania-like god game

[Jose G . López]

Package: wnpp
Severity: wishlist
Owner: Jose G. López <josg...@gmail.com>

* Package name: gigalomania
  Version : 0.29
  Upstream Author : Mark Harman <mark.har...@ntlworld.com>
* URL : http://gigalomania.sourceforge.net
* License : GPL-2+, CC0, CC BY 3.0 and zlib License
  Programming Lang: C++
  Description : Mega-Lo-Mania-like god game
  
Gigalomania is an open source 2D Real Time Strategy god game.
The gameplay consists of researching and developing new technology with which
to conquer your enemies, from rocks and sticks to nuclear weapons and
spaceships. You can advance through ten different ages, from the stone age to
the future. There are 28 different maps to play through.

CCing Debian Games Team as I will need a sponsor and think it should be under
their umbrella.

Bug#865735: mrpt shouldn't disable PIE

[JOSE LUIS BLANCO CLARACO]

Thanks Adrian!

We already addressed this upstream (and in a waiting version in
mentors.debian.org) but by adding "+pie". We'll use your version if
that's more correct. Thanks.

Bug#862855: closed by Mike Gabriel <mike.gabr...@das-netzwerkteam.de> (Bug#862855: fixed in e2guardian 3.4.0.3-2)

[Jose Torres]

1. When do you expect to be available in the Debian FTP?
2. Is the Debian FTP the repository for the upgrades?
3. Will you provide a procedure to do the upgrade?


On Sat, Jun 3, 2017 at 5:21 PM, Debian Bug Tracking System
 wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the e2guardian package:
>
> #862855: e2guardian: Google Chrome changed certificate requirements making 
> mitm unusable
>
> It has been closed by Mike Gabriel .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Mike Gabriel 
>  by
> replying to this email.
>
>
> --
> 862855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862855
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
> -- Forwarded message --
> From: Mike Gabriel 
> To: 862855-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Sat, 03 Jun 2017 21:19:36 +
> Subject: Bug#862855: fixed in e2guardian 3.4.0.3-2
> Source: e2guardian
> Source-Version: 3.4.0.3-2
>
> We believe that the bug you reported is fixed in the latest version of
> e2guardian, 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 862...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Mike Gabriel  (supplier of updated 
> e2guardian 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)
>


https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=icon;
target="_blank">https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif;
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/>
Virus-free. https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail_term=link;
target="_blank" style="color: #4453ea;">www.avast.com

Bug#862117: ITP: ignition-math3 -- A small, fast, and high performance math library (v3)

[Jose Luis Rivero]

Package: wnpp
Severity: wishlist
Owner: Jose Luis Rivero <jriv...@osrfoundation.org>

* Package name: ignition-math3
  Version : 3.1.0
  Upstream Author : Open Source Robotics Foundation
* URL : http://ignitionrobotics.org/libraries/math
* License : Apache
  Programming Lang: C++
  Description : A small, fast, and high performance math library (v3)


Small, fast, and high performance math library. This library is a
self-contained set of classes and functions suitable for robot
applications.

Designed to be co-installable with ignition-math2, already present in
Debian.

Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy

[Jose Antonio Jimenez Madrid]

Hi,

Andy, I have tested a couple of solutions and I think the easiest way 
for you is just to
download the Eterm package for Stretch (testing) and install it in your 
system manually with:


dpkg -i eterm_0.9.6-4_amd64.deb

I have just installed the Eterm version in testing and no new packages 
are needed, just this one and it is working in my system.
(One can use pinning in apt to install packages for several 
distributions, but for just one package I think it is not necessary in 
this case).


Please, let me know if this solution is not working for you to try a 
more elaborate fix until Stretch is released.


Regards,

Jose

P.S.: Do not apologise for the "duplication" of bug numbers. It is not 
your fault, you used "reportbug" correctly. I draw the attention about the
duplication of the bug to close both of them as one is already fixed in 
testing, just to document it and to not forget to close both.




Andy Bennett wrote:

Hi,

Thanks for your help!



I think this bug is the same than bug #770369.


I tried to file this as a followup to the existing bug but must have 
messed up with my usage of `reportbug`; sorry!



This bug is close in stretch (testing). As it is expected the release 
stretch occurs soon, the easiest way is:


1. To wait for the release of stretch to get this problem fixed when 
you upgrade from Wheezy to Stretch.
2. Downgrade the Eterm package to the version in Jessie so you can 
use it until the upgrade to Stretch.


Do you mean wheezy? Do you have a command to hand that can do that for 
me or is it best to fetch the .deb out of the appropriate package pool?



I am trying to maintain Eterm package, but my process of learning to 
do it properly is getting a little long so

I have not prepared a new Eterm package.

I have checked the fix proposed and my local Eterm package is working 
in Jessie-amd64 (thanks to Charles Gorand and Arnaud Ceyroll for the 
fix).


Andy, if you want I can send you my local package to your e-mail, so 
you can use it.


For Santiago Vila (or other developers) I have modified the source 
package in Jessie by performing the fix suggested by Arnaud and 
Charles to the command.c file, just
recompiled in my Jessie system and the new Eterm package is working 
again.


Maybe I can try to build my own local package? Are you able to send me 
the patch for the Jessie package?



Maybe it is worth to propose an update for Jessie so the package will 
be usable again
for all the users. I will have some spare time after the middle of 
June, so I would be able to apply the fix in the correct way (I have 
just edited the source to test it, I have to read deeper the 
maint-guide to

do it in the right way).

After the release of Stretch I will try to fix the UTF8 problem in 
Eterm to finally maintain this package.


Thanks for your help and for giving the time.



Regards,
@ndy

Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy

[Jose Antonio Jimenez Madrid]

(I am writing to bugs #737491 and #770369 as the fix is the same)

Dear Andy,

I think this bug is the same than bug #770369.
This bug is close in stretch (testing). As it is expected the release 
stretch occurs soon, the easiest way is:


1. To wait for the release of stretch to get this problem fixed when you 
upgrade from Wheezy to Stretch.
2. Downgrade the Eterm package to the version in Jessie so you can use 
it until the upgrade to Stretch.


I am trying to maintain Eterm package, but my process of learning to do 
it properly is getting a little long so

I have not prepared a new Eterm package.

I have checked the fix proposed and my local Eterm package is working in 
Jessie-amd64 (thanks to Charles Gorand and Arnaud Ceyroll for the fix).


Andy, if you want I can send you my local package to your e-mail, so you 
can use it.


For Santiago Vila (or other developers) I have modified the source 
package in Jessie by performing the fix suggested by Arnaud and Charles 
to the command.c file, just
recompiled in my Jessie system and the new Eterm package is working 
again. Maybe it is worth to propose an update for Jessie so the package 
will be usable again
for all the users. I will have some spare time after the middle of June, 
so I would be able to apply the fix in the correct way (I have just 
edited the source to test it, I have to read deeper the maint-guide to

do it in the right way).

After the release of Stretch I will try to fix the UTF8 problem in Eterm 
to finally maintain this package.


Sincerely,

Jose

Bug#850731: xorp: segfaults at initialization, linker flags

[Jose M Calhariz]

On 20/04/17 22:04, Dhionel Díaz wrote:
> On 02/03/17 17:08, Ben Greear wrote:
>> Just FYI, I pushed this change plus an additional null check
>> in related code.  If fixes the crash I was seeing on my Fedora-24 systems,
>> and it would appear to be the same bug earlier reported.
>>
>> Thanks,
>> Ben
>>
>> On 01/10/2017 12:50 PM, Dhionel Díaz wrote:
>>> El 10/01/17 a las 15:59, Jose M Calhariz escribió:
>>>> Hi, I have contacted the upstream author, Ben Greear, about this
>>>> problem.  And he requested
>>>> if you have a back trace?
>>>>
>>>>> I would be interested in seeing a backtrace if the user has
>>>> it
>>>>
>>>>> so I could better understand the problem.  Maybe the code should
>>>> never
>>>>
>>>>> actually be trying to call these methods if _root is NULL?
>>>> Can you help the author?
>>>>
>>>> Kind regards
>>>> Jose M Calhariz
>>>>
>>>>
>>> (...)
>>> Hi, attached you will find the requested backtrace. Thanks for your
>>> attention.
>>>
>>> Regards,
>>>
>>
> Hi, I can confirm that the changes have been working properly in our
> router all this time. Thanks for your attention.
>
> Regards,
>
Thank you for your testing.  I have not released a new version to Debian
because of the freeze.

My plan is to quickly release a new version after the release. 


Kind regards

Jose M Calhariz





signature.asc
Description: OpenPGP digital signature

Bug#856629: scid: pgnscid is not installed

[Jose G . López]

Package: scid
Followup-For: Bug #856629

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello Charles,

Thanks for your report!
pgnscid is obsolete as stated on changelog since version 4.6.0. 

- - 
- - - Removed features:
* obsolete executables scidt, pgnscid and eco2epd
- - 

Truly I have to update the man page.

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEN4h6tTAj56l5X2w24gpHPJFt8kYFAljyJEUSHGpvc2dhbG9A
Z21haWwuY29tAAoJEOIKRzyRbfJGD3UQAL/nG41QaX1RGz695DM+z6GONRa8BXU8
R5XAQIdNvRm+ZiCYBdWzAx5Xnku38CgKkOA8mVWpzIKmGWE8yjbDx9jxEg8JiFpa
IIdZYATEfs4jIubfQ+aDdba0tpPJevcFOBueaKphqnQRbo6di1iEFEWP8zwE+8L1
E9t1xDkgbmI3uX+cpVXvRoZhVVAdalMr/xWQW5pnMtCCtwJCFhvyl2GhGVPmbWDb
rZUWXnlw1Zby6nHJYp7jIcAgZrp22GKWuWVVuGG3JCfJTpItT1EQqmto60sWLoso
7652Zob6DaunyAXIgmkFq5slpsXcJk9XxKNTqQjFUx97ccILpD+sR7ScuvbWODKd
y7y0eQ58nVOGzmpSf8U6yN2KiH0OGXm2txDOu+geuuHe/DZ3yr9X/VfWC/bNAhaA
Bo9Xdv/ydTYI5COThLTEdhcpy0o79B46+afe312zw4cEABd6E/ur32uAGlzq7MCi
XFpwk3XxDjSq7JGRB88MdOKHT6MXGElFpvtrAmdtFPMeE7N0Ggd5A195BNT/PtcD
F3xSKS5XHGQaXYeyUB3TSpsFezP3z9TWI3UwQFU4kdKimfbahX5qW2gK4n3g9OIM
AOPpKTcSYQe4vUeYSH8ZE0VFWslvKhlIg81vGSqTxtJB9ltvTn2/07yDvfWYe5zY
+D10QV47bNCg
=whkS
-END PGP SIGNATURE-

Bug#855552: [zeroc-ice] - missing python 2 bindings

[Jose Gutierrez de la Concha]

On Thu, Mar 30, 2017 at 11:39 AM, Mark Carroll  wrote:

> This is rather unfortunate -- a lot of the world is still on Python 2 -
> I didn't think it's meant to be EOL until 2020? I just ran into this in
> looking at installing the new version of OMERO -
> http://www.openmicroscopy.org/site/support/omero/sysadmins/
> version-requirements.html
> says that they do not support Python 3 but OMERO 5.4 will no longer
> support Ice 3.5 at all, which would leave me in a tricky situation.
>

I will check if we can add this back, meanwhile you will be able to install
python2
extensions using pip https://pypi.python.org/pypi/zeroc-ice/3.6.3


> I did try using ZeroC's http://zeroc.com/download/apt/debian8 as an
> alternative but their zeroc-ice-compilers_3.6.3-1000_amd64.deb doesn't
> include slice2java. (I probably just don't know what I'm doing though!)
>

That was a preliminary version that didn't include Java, just packaged
C++/Python


>
> -- Mark
>



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

Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64

[Jose R R]

Niltze,

On Wed, Mar 29, 2017 at 8:48 AM, Cyril Brulebois <k...@debian.org> wrote:
> Hi,
>
> Jose R R <j...@metztli-it.com> (2017-03-29):
>> With all due respect, 99% of the build code for the debian-installer
>> is yours. As well as the build pulls 99% UDEBs from official debian
>> repositories.
>
> That doesn't mean that everything built on top of it has to be reported
> on Debian mailing lists and bug tracker. See derivative distributions,
> they have their own issue tracker, and only forward specific issues.
>
>> i.e., this is a Debian issue, not mine -- as I did not even touch that
>> code and/or modules -- which 1 month ago actually did work smooth:
>>
>> Netboot debian-installer was unable to load firmware from second USB
>> for wifi connection; accordingly, in another virtual screen, I mounted
>> the 2nd USB and manually copied the firmware directory onto the
>> installer environment /lib. d-i then detected the wifi signal, etc.
>>
>>
>> Second, report on this unofficial jessie-backports kernel
>> 4.9.16-1+reiser4.0.1 sheds light on the fact I experienced *no issue*
>> with module i915, as had been reported by (maintainer?): <
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 > thus, in a
>> collateral manner, I am contributing to official debian development.
>
> If you want to reply to submitters/maintainers, reply to specific bug
> reports/threads, instead of sending lengthy mails to other people?
>
>> Finally, I am not requesting *any* support. I am simply reporting that
>> your d-i pulling official UDEBs actually have been successful, with
>> minor modifications and a few extra UDEBs of mine, in my installation
>> experience, following Debian documentation guidelines:
>
> I haven't put words in your mouth and suggested you were requesting some
> support. I'm just not convinced such reports are useful. If you
> encounter specific issues, report specific bug reports against the
> relevant component.
>
> debian-boot@ isn't and shouldn't be the destination of each and every
> thing connected to, or merely using, Debian Installer.
>
>> "We also encourage installation reports to be sent even if the
>> installation is successful, so that we can get as much information as
>> possible on the largest number of hardware configurations." <
>> https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug
>> >
>
> Sure, with official images.
>
>> If you are still 'bothered' with my sporadic submissions, I encourage
>> you to modify the documentation to specifically exclude the glaring
>> omission.
>
> I could be adding a specific “we don't need reiser4-specific reports”

Please do add that phrase; thus removing any ambiguities and cover the
glaring omission in the Debian documentation.

That clarification will prevent other individuals -- who have
downloaded the netboot installer from SourceForge -- from potentially
reporting via the debian mechanism -- once the installation completes.

Additionally, appending “we don't need reiser4-specific reports” will
be a welcome *explicit* change in policy from other FOSS projects,
like GNU Parted, where the unspoken censorship on reiser4 bites anyone
who submits patches in support of the
'Batman Machine': Reiser4
< https://metztli.it/readOnlyEphemeral/Batman_Machine-Reiser4.pdf >


Again, thank you.


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

Bug#858849: installation-reports: Successful Jessie installation with backported kernel 4.9.16-1+reiser4.0.1 on i915 system AMD64

[Jose R R]

Niltze,

On Mon, Mar 27, 2017 at 8:00 PM, Cyril Brulebois <k...@debian.org> wrote:
> Hi,
>
> Metztli Information Technology <j...@metztli-it.com> (2017-03-27):
>> Boot method: CD/USB
>> Image version: https://metztli.it/readOnlyEphemeral/xiuhcohuatl.iso built on 
>> Mar 25 08:35 (2017)
>> Date: Mar 26, 2017, 01:49
>
> A couple of months ago, I asked:
> | Do we need to get installation reports for non-Debian installers?
> | This isn't something we produce, publish, or support, so…
>
> It would be nice if those installation reports could be sent elsewhere;
> thanks already.
>
>
> KiBi.

With all due respect, 99% of the build code for the debian-installer
is yours. As well as the build pulls 99% UDEBs from official debian
repositories.

i.e., this is a Debian issue, not mine -- as I did not even touch that
code and/or modules -- which 1 month ago actually did work smooth:

Netboot debian-installer was unable to load firmware from second USB
for wifi connection;
accordingly, in another virtual screen, I mounted the 2nd USB and
manually copied the firmware
directory onto the installer environment /lib. d-i then detected the
wifi signal, etc.


Second, report on this unofficial jessie-backports kernel
4.9.16-1+reiser4.0.1 sheds light on the fact I experienced *no issue*
with module i915, as had been reported by (maintainer?):
< https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858078 >
thus, in a collateral manner, I am contributing to official debian development.

Finally, I am not requesting *any* support. I am simply reporting that
your d-i pulling official UDEBs actually have been successful, with
minor modifications and a few extra UDEBs of mine, in my installation
experience, following Debian documentation guidelines:

"We also encourage installation reports to be sent even if the
installation is successful, so that we can get as much information as
possible on the largest number of hardware configurations."
< https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug >

If you are still 'bothered' with my sporadic submissions, I encourage
you to modify the documentation to specifically exclude the glaring
omission.


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

Bug#857958: unblock: zeroc-ice/3.6.3-5

[Jose Gutierrez de la Concha]

On Thu, Mar 16, 2017 at 9:05 PM, Jose Gutierrez de la Concha <j...@zeroc.com
> wrote:

> Hi Emilio,
>
> That is expected, we decide to change -debian suffix to -3.6 to be able to
> co install several version in the future -3.7 -4.0,
> as that is something our users my wish. I asked in Java dev list what was
> the proper way to deal with multiple java verions
> of a package and that is the recommended approach.
>

Forget to remove the control tag

>
>
> On Thu, Mar 16, 2017 at 7:01 PM, Emilio Pozuelo Monfort <po...@debian.org>
> wrote:
>
>>
>> Hi José,
>>
>> On 16/03/17 17:57, José Gutiérrez de la Concha wrote:
>> > Package: release.debian.org
>> > Severity: normal
>> > User: release.debian@packages.debian.org
>> > Usertags: unblock
>> >
>> >
>> > Hi,
>> >
>> > I want to request unblock of zeroc-ice/3.6.3-5, it include a fix
>> > for RC bug 857219
>> >
>> > There was a broken symlink in the previous version that should have
>> > not been included in the package.
>> >
>> > The new package also include a minor fix to not install unversioned
>> > jar files.
>> >
>> > debdiff included bellow
>> >
>> > debdiff zeroc-ice_3.6.3-4.dsc zeroc-ice_3.6.3-5.dsc
>> > diff -Nru zeroc-ice-3.6.3/debian/changelog
>> zeroc-ice-3.6.3/debian/changelog
>> > --- zeroc-ice-3.6.3/debian/changelog2016-12-05 08:37:57.0
>> +
>> > +++ zeroc-ice-3.6.3/debian/changelog2017-03-09 15:22:39.0
>> +
>> > @@ -1,3 +1,10 @@
>> > +zeroc-ice (3.6.3-5) unstable; urgency=medium
>> > +
>> > +  * Do not install libIceStormService.so (Closes: #857219)
>> > +  * Fix libzeroc-ice3.6-java install to use 3.6 name
>> > +
>> > + -- Jose <j...@zeroc.com>  Thu, 09 Mar 2017 16:22:39 +0100
>> > +
>> >  zeroc-ice (3.6.3-4) unstable; urgency=medium
>> >
>> >* Move javahelper to Build-Depends to fix Bug#847010
>> > diff -Nru zeroc-ice-3.6.3/debian/libzeroc-ice3.6-java.poms
>> zeroc-ice-3.6.3/debian/libzeroc-ice3.6-java.poms
>> > --- zeroc-ice-3.6.3/debian/libzeroc-ice3.6-java.poms2016-12-05
>> 08:37:57.0 +
>> > +++ zeroc-ice-3.6.3/debian/libzeroc-ice3.6-java.poms2017-03-09
>> 15:22:39.0 +
>> > @@ -1,9 +1,9 @@
>> > -java/lib/ice-3.6.3.pom --artifact=java/lib/ice-3.6.3.jar
>> > -java/lib/icebox-3.6.3.pom --artifact=java/lib/icebox-3.6.3.jar
>> > -java/lib/icediscovery-3.6.3.pom --artifact=java/lib/icediscove
>> ry-3.6.3.jar
>> > -java/lib/icelocatordiscovery-3.6.3.pom --artifact=java/lib/icelocator
>> discovery-3.6.3.jar
>> > -java/lib/icegrid-3.6.3.pom --artifact=java/lib/icegrid-3.6.3.jar
>> > -java/lib/icestorm-3.6.3.pom --artifact=java/lib/icestorm-3.6.3.jar
>> > -java/lib/icepatch2-3.6.3.pom --artifact=java/lib/icepatch2-3.6.3.jar
>> > -java/lib/glacier2-3.6.3.pom --artifact=java/lib/glacier2-3.6.3.jar
>> > -java/lib/freeze-3.6.3.pom --artifact=java/lib/freeze-3.6.3.jar
>> > +java/lib/ice-3.6.3.pom --artifact=java/lib/ice-3.6.3.jar --java-lib
>> --no-usj-versionless
>> > +java/lib/icebox-3.6.3.pom --artifact=java/lib/icebox-3.6.3.jar
>> --java-lib --no-usj-versionless
>> > +java/lib/icediscovery-3.6.3.pom --artifact=java/lib/icediscovery-3.6.3.jar
>> --java-lib --no-usj-versionless
>> > +java/lib/icelocatordiscovery-3.6.3.pom 
>> > --artifact=java/lib/icelocatordiscovery-3.6.3.jar
>> --java-lib --no-usj-versionless
>> > +java/lib/icegrid-3.6.3.pom --artifact=java/lib/icegrid-3.6.3.jar
>> --java-lib --no-usj-versionless
>> > +java/lib/icestorm-3.6.3.pom --artifact=java/lib/icestorm-3.6.3.jar
>> --java-lib --no-usj-versionless
>> > +java/lib/icepatch2-3.6.3.pom --artifact=java/lib/icepatch2-3.6.3.jar
>> --java-lib --no-usj-versionless
>> > +java/lib/glacier2-3.6.3.pom --artifact=java/lib/glacier2-3.6.3.jar
>> --java-lib --no-usj-versionless
>> > +java/lib/freeze-3.6.3.pom --artifact=java/lib/freeze-3.6.3.jar
>> --java-lib --no-usj-versionless
>> > diff -Nru zeroc-ice-3.6.3/debian/maven.rules
>> zeroc-ice-3.6.3/debian/maven.rules
>> > --- zeroc-ice-3.6.3/debian/maven.rules  1970-01-01 00:00:00.0
>> +
>> > +++ zeroc-ice-3.6.3/debian/maven.rules  2017-03-09 15:22:39.0
>> +
>> > @@ -0,0 +1,9 @@
>> > +com.zeroc freeze jar s/3\.6\..*/3.6/
>> > +com.zeroc glacier2 jar s/3\.6\..*/3.6/
>> > +

Bug#857958: unblock: zeroc-ice/3.6.3-5

[Jose Gutierrez de la Concha]

Hi Emilio,

That is expected, we decide to change -debian suffix to -3.6 to be able to
co install several version in the future -3.7 -4.0,
as that is something our users my wish. I asked in Java dev list what was
the proper way to deal with multiple java verions
of a package and that is the recommended approach.


On Thu, Mar 16, 2017 at 7:01 PM, Emilio Pozuelo Monfort <po...@debian.org>
wrote:

> Control: tags -1 moreinfo
>
> Hi José,
>
> On 16/03/17 17:57, José Gutiérrez de la Concha wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> >
> >
> > Hi,
> >
> > I want to request unblock of zeroc-ice/3.6.3-5, it include a fix
> > for RC bug 857219
> >
> > There was a broken symlink in the previous version that should have
> > not been included in the package.
> >
> > The new package also include a minor fix to not install unversioned
> > jar files.
> >
> > debdiff included bellow
> >
> > debdiff zeroc-ice_3.6.3-4.dsc zeroc-ice_3.6.3-5.dsc
> > diff -Nru zeroc-ice-3.6.3/debian/changelog zeroc-ice-3.6.3/debian/
> changelog
> > --- zeroc-ice-3.6.3/debian/changelog2016-12-05 08:37:57.0
> +
> > +++ zeroc-ice-3.6.3/debian/changelog2017-03-09 15:22:39.0
> +
> > @@ -1,3 +1,10 @@
> > +zeroc-ice (3.6.3-5) unstable; urgency=medium
> > +
> > +  * Do not install libIceStormService.so (Closes: #857219)
> > +  * Fix libzeroc-ice3.6-java install to use 3.6 name
> > +
> > + -- Jose <j...@zeroc.com>  Thu, 09 Mar 2017 16:22:39 +0100
> > +
> >  zeroc-ice (3.6.3-4) unstable; urgency=medium
> >
> >* Move javahelper to Build-Depends to fix Bug#847010
> > diff -Nru zeroc-ice-3.6.3/debian/libzeroc-ice3.6-java.poms
> zeroc-ice-3.6.3/debian/libzeroc-ice3.6-java.poms
> > --- zeroc-ice-3.6.3/debian/libzeroc-ice3.6-java.poms2016-12-05
> 08:37:57.0 +
> > +++ zeroc-ice-3.6.3/debian/libzeroc-ice3.6-java.poms2017-03-09
> 15:22:39.0 +
> > @@ -1,9 +1,9 @@
> > -java/lib/ice-3.6.3.pom --artifact=java/lib/ice-3.6.3.jar
> > -java/lib/icebox-3.6.3.pom --artifact=java/lib/icebox-3.6.3.jar
> > -java/lib/icediscovery-3.6.3.pom --artifact=java/lib/
> icediscovery-3.6.3.jar
> > -java/lib/icelocatordiscovery-3.6.3.pom --artifact=java/lib/
> icelocatordiscovery-3.6.3.jar
> > -java/lib/icegrid-3.6.3.pom --artifact=java/lib/icegrid-3.6.3.jar
> > -java/lib/icestorm-3.6.3.pom --artifact=java/lib/icestorm-3.6.3.jar
> > -java/lib/icepatch2-3.6.3.pom --artifact=java/lib/icepatch2-3.6.3.jar
> > -java/lib/glacier2-3.6.3.pom --artifact=java/lib/glacier2-3.6.3.jar
> > -java/lib/freeze-3.6.3.pom --artifact=java/lib/freeze-3.6.3.jar
> > +java/lib/ice-3.6.3.pom --artifact=java/lib/ice-3.6.3.jar --java-lib
> --no-usj-versionless
> > +java/lib/icebox-3.6.3.pom --artifact=java/lib/icebox-3.6.3.jar
> --java-lib --no-usj-versionless
> > +java/lib/icediscovery-3.6.3.pom --artifact=java/lib/icediscovery-3.6.3.jar
> --java-lib --no-usj-versionless
> > +java/lib/icelocatordiscovery-3.6.3.pom 
> > --artifact=java/lib/icelocatordiscovery-3.6.3.jar
> --java-lib --no-usj-versionless
> > +java/lib/icegrid-3.6.3.pom --artifact=java/lib/icegrid-3.6.3.jar
> --java-lib --no-usj-versionless
> > +java/lib/icestorm-3.6.3.pom --artifact=java/lib/icestorm-3.6.3.jar
> --java-lib --no-usj-versionless
> > +java/lib/icepatch2-3.6.3.pom --artifact=java/lib/icepatch2-3.6.3.jar
> --java-lib --no-usj-versionless
> > +java/lib/glacier2-3.6.3.pom --artifact=java/lib/glacier2-3.6.3.jar
> --java-lib --no-usj-versionless
> > +java/lib/freeze-3.6.3.pom --artifact=java/lib/freeze-3.6.3.jar
> --java-lib --no-usj-versionless
> > diff -Nru zeroc-ice-3.6.3/debian/maven.rules
> zeroc-ice-3.6.3/debian/maven.rules
> > --- zeroc-ice-3.6.3/debian/maven.rules  1970-01-01 00:00:00.0
> +
> > +++ zeroc-ice-3.6.3/debian/maven.rules  2017-03-09 15:22:39.0
> +
> > @@ -0,0 +1,9 @@
> > +com.zeroc freeze jar s/3\.6\..*/3.6/
> > +com.zeroc glacier2 jar s/3\.6\..*/3.6/
> > +com.zeroc icebox jar s/3\.6\..*/3.6/
> > +com.zeroc ice jar s/3\.6\..*/3.6/
> > +com.zeroc icediscovery jar s/3\.6\..*/3.6/
> > +com.zeroc icelocatordiscovery jar s/3\.6\..*/3.6/
> > +com.zeroc icegrid jar s/3\.6\..*/3.6/
> > +com.zeroc icepatch2 jar s/3\.6\..*/3.6/
> > +com.zeroc icestorm jar s/3\.6\..*/3.6/
> > diff -Nru zeroc-ice-3.6.3/debian/rules zeroc-ice-3.6.3/debian/rules
> > --- zeroc-ice-3.6.3/debian/rules2016-12-05 08:37:57.0
> +
> > +++ 

Bug#857219: libzeroc-ice-dev: missing Depends: libzeroc-icestorm3.6 (= ${binary:Version})

[Jose Gutierrez de la Concha]

Hi Andreas,

Thanks for reporting this bug, libzeroc-ice-dev must not include
libIceStormService.so
I have push a fix to the package debian/rules and will upload a new version.

On Wed, Mar 8, 2017 at 11:07 PM, Andreas Beckmann  wrote:

> Package: libzeroc-ice-dev
> Version: 3.6.3-4
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
>
> >From the attached log (scroll to the bottom...):
>
> 0m30.1s ERROR: FAIL: Broken symlinks:
>   /usr/lib/x86_64-linux-gnu/libIceStormService.so ->
> libIceStormService.so.36
>
>
> cheers,
>
> Andreas
>



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

Bug#825552: hplip: printing doesn't honour settings paper size

[Jose Luis Gonzalez]

On 07/03/17 19:09, Brian Potkin wrote:

On Tue 07 Mar 2017 at 18:18:28 +0100, Jose Luis Gonzalez wrote:


On 02/03/17 20:48, Brian Potkin wrote:

tags 825552 moreinfo
thanks



On Fri 27 May 2016 at 20:23:09 +0200, José Luis González wrote:


Print dialog on apps shows US Letter as paper size when I have set it
up to A4 in the printer preferences.

Please clarify: what printer preferences are you referring to? And which
apps? An example for a specific app would help.

The printer settings available in XFCE looking for the printer and then its
settings.

The app was google chrome, AFAIR. It's possible that it also happened with
evince.

If I print from Evince with a Paper size of A3, this setting sticks.
Next time Evince is used the paper size is A3. This is the way the app
behaves and has nothing to do with hplip.



I also have a recollection that Evince and Firefox both use Letter as a
default. There might bug reports about this but I haven't checked. Again,
hplip is not involved.


If I understand you correctly Evince has its own printing settings. It's 
very likely that my problem was just with Chromium and not with evince. 
In any case if Chromium also has its own settings and doesn't use HPLIP, 
this is probably a bug in Chromium, as I think I have A4 as system 
default setting. If Chromium doesn't have it's own printing settings and 
uses HPLIP defaults, I understand the problem lies on HPLIP. If you 
want, just move this report to chromium.


Does this sound reasonable to you. If so, I will close the report.
I think it's still a bug (with Chromium at least) and it makes sense to 
remain open. I don't know if Chromium uses HPLIP defaults or has it's 
own settings. If it doesn't, please reassign the bug to chromium, but 
leave it open.


Unfortunately I don't have the printer anymore, so I can't retry anything...

Cheers,
José Luis

Bug#825426: Two sides printing

[Jose Luis Gonzalez]

On 07/03/17 18:40, Brian Potkin wrote:

On Tue 07 Mar 2017 at 18:13:54 +0100, Jose Luis Gonzalez wrote:


Two sides printing doesn't work on my HP Photosmart C3180. The option
gets ignored (the printer prints the whole sequence and there is no
GUI asking for page reinsertion).

As far as I can tell from its specifications the C3180 does not have
auto-duplex. auto-duplex is when the sheet of paper is pulled back into
the printer, turned round and printed on the other side.

I was under the impression that two sides printing wasn't auto-duplex
but manual two sides printing (that is, first printing even pages,
then reversing them manually and then printing odd pages on the
reverse). I seem to remember there were further options for this. If I
was mistaken, please forgive me.

I think I am beginning to understand what it is you are after. Is what
you want descibed here:

  https://answers.launchpad.net/hplip/+question/196818 ?


Yes, it's that. Please, close the report. I thought it was manual duplexing.

Bug#827182: hplip: HP C3180 failing halted with blinking display

[Jose Luis Gonzalez]

On 02/03/17 21:00, Brian Potkin wrote:

tags 827182 moreinfo
thanks



On Mon 13 Jun 2016 at 14:51:42 +0200, José Luis González wrote:


Package: hplip
Version: 3.16.5+repack0-1

After printing inverted even pages on range 1-55 from the
follwing document:

http://www.brilliantclassics.com/media/965989/94840-Vivaldi-Liner-Notes-Download.pdf

my HP C3180 has become unresponding with all the leds and display
blinking very fast and an E letter in the copies display. The end of
the last page was seemingly printed but it didn't get ejected. The
cancel button did not work. I had to turn the printer off and on again
to get it to a working state and eject the end of the page. Afterwards
a test page was printed.

Were the even pages printed correctly? Is the cancel button on the
printer?
I seem to remember the pages printed OK. There was a cancel button on 
the printer but it probably was of no use. Anyway, I suspect this was a 
hardware problem, as I had a similar problem some time afterwards and 
the printer didn't recover at all. I had to throw it away.


I think you can close this report. I can't reproduce it as I don't have 
the printer anymore.


Regards,
José Luis

Bug#825552: hplip: printing doesn't honour settings paper size

[Jose Luis Gonzalez]

On 02/03/17 20:48, Brian Potkin wrote:

tags 825552 moreinfo
thanks



On Fri 27 May 2016 at 20:23:09 +0200, José Luis González wrote:


Print dialog on apps shows US Letter as paper size when I have set it
up to A4 in the printer preferences.

Please clarify: what printer preferences are you referring to? And which
apps? An example for a specific app would help.


The printer settings available in XFCE looking for the printer and then 
its settings.


The app was google chrome, AFAIR. It's possible that it also happened 
with evince.

Bug#825426: Two sides printing

[Jose Luis Gonzalez]

> Two sides printing doesn't work on my HP Photosmart C3180. The option
> gets ignored (the printer prints the whole sequence and there is no
> GUI asking for page reinsertion).



As far as I can tell from its specifications the C3180 does not have
auto-duplex. auto-duplex is when the sheet of paper is pulled back into
the printer, turned round and printed on the other side.


I was under the impression that two sides printing wasn't auto-duplex but 
manual two sides printing (that is, first printing even pages, then reversing 
them manually and then printing odd pages on the reverse). I seem to remember 
there were further options for this. If I was mistaken, please forgive me.

Bug#855552: [zeroc-ice] - missing python 2 bindings

[Jose Gutierrez de la Concha]

Hi,

When we (ZeroC) repackage Ice we decided to not include python2 binding,
there wasn't
any reverse depedencies for python-zeroc-ice package and Python policy
states that a python2
library can be remove in that case.

see
https://www.debian.org/doc/packaging-manuals/python-policy/ch-python3.html

Python 2 is still supported with Ice 3.6/3.7 Ice source distributions
but stretch is moving towards
Python3 and so we thing that removing python-zeroc-ice is a good trade-off

On Mon, Feb 20, 2017 at 1:59 AM,  wrote:

> Package: zeroc-ice
>
> Version: 3.6.3-4
>
> Severity: normal
>
> Source: *zeroc-ice*
>
>
>
> Debian “stretch” no longer contains a package with python2 bindings. In
> previous releases this was available as ‘python-zeroc-ice’.
>
> The source package’s “rules” seem to have been completely re-written
> without the inclusion of python2. The source of zeroc 3.6 still supports
> python2/
>
> I can’t see this being is a deliberate choice as there is no trace in the
> “changelog” or an announcement for dropping this in NEWS.
>
>
>



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

Bug#852147: sawfish: Upstream version 1.12.0 available since August 06

[Jose A. Ortega Ruiz]

On Mon, Jan 23 2017, Jose M Calhariz wrote:

[...]

> Can you open a bug report against Debian about this tiling glitch?  It
> will help me to backport sawfish for stretch, for the benefit of
> stretch users.

done (i hope):

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


thanks a lot!

Bug#852294: sawfish: Non-transient windows ignored in tiling functions

[Jose Antonio Ortega Ruiz]

Package: sawfish
Version: 3:1.12.0-1nano
Severity: normal

Dear Maintainer,

The current version of sawfish has a problem with its tiling layout
functions, described in this upstream report:

  https://github.com/SawfishWM/sawfish/pull/21

it affects tiling in the presence of applications such as Conky or
Corebird.

the problem was fixed upstream in their version 1.12.0.

thanks!
jao

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages sawfish depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgmp10 2:6.1.2+dfsg-1
ii  libgtk2.0-0  2.24.31-1
ii  libice6  2:1.0.9-1+b1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpangoft2-1.0-01.40.3-3
ii  libpangoxft-1.0-01.40.3-3
ii  librep16 3:0.92.6-1nano
ii  libsm6   2:1.2.2-1+b1
ii  libx11-6 2:1.6.4-2
ii  libxext6 2:1.3.3-1
ii  libxft2  2.3.2-1
ii  libxinerama1 2:1.1.3-1+b1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxtst6 2:1.2.3-1
ii  rep  3:0.92.6-1nano
ii  rep-gtk  3:0.90.8.3-1nano
ii  rxvt-unicode-256color [x-terminal-emulator]  9.22-1+b1
ii  sawfish-data 3:1.12.0-1nano
ii  xterm [x-terminal-emulator]  327-2

sawfish recommends no packages.

sawfish suggests no packages.

-- no debconf information

Bug#852147: sawfish: Upstream version 1.12.0 available since August 06

[Jose M Calhariz]

On 22/01/17 23:44, Jose A. Ortega Ruiz wrote:
> Hi Jose,
>
> On Sun, Jan 22 2017, Jose M Calhariz wrote:
>
>> Hi Jose,
>>
>> Sorry, I did not keep up with the upstream because I was busy studying
>> to be a DD.
> no problem! hope your studies went well :)

Yes, my studies are going well, thank you.

>
>> I believe there is little difference between the version in stretch
>> and the upstream.  But if you find any problem with the version in
> actually, version 1.12 solves a little glitch in the tiling code (by
> yours truly) that nagged me in the previous version.  i can patch it
> locally, but it'd be nice to see the fix in our debian package too.

Can you open a bug report against Debian about this tiling glitch?  It
will help me to backport
sawfish for stretch, for the benefit of stretch users.

>
> (also, sawfish has been so long outdated in the past that, in my opinion
> it'd be really nice to have the latest and greatest these days if at all
> possible.)

I think the same.  I just directed my little free time to other packages
with more users.
It is always good to know users that care about my packages. :)

>
>> Debian, please open a bug report and I will update the package via the
>> backports.  The bug report is important before I can update the
>> package via backports.
> hmm, i just used reportbug to generate this request, and i see the bug
> already filled there:
>
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852147

This bug report is about the outdated sawfish in Debian.


>
> or do you mean somewhere else?  i actually use sid, and i don't see
> 1.12.0 there: should i? i'm just asking because you mention backports:
> maybe i'm missing something here?

The backports is for users of stable, in this case for stretch.
It is freeze time on Debian.  When the freeze is over I will upload the
latest sawfish into sid.
If it takes to much time I will upload it to experimental. 


>
> thanks!
> jao

Kind regards

Jose M Calhariz




signature.asc
Description: OpenPGP digital signature

Bug#852147: sawfish: Upstream version 1.12.0 available since August 06

[Jose A. Ortega Ruiz]

Hi Jose,

On Sun, Jan 22 2017, Jose M Calhariz wrote:

> Hi Jose,
>
> Sorry, I did not keep up with the upstream because I was busy studying
> to be a DD.

no problem! hope your studies went well :)

> I believe there is little difference between the version in stretch
> and the upstream.  But if you find any problem with the version in

actually, version 1.12 solves a little glitch in the tiling code (by
yours truly) that nagged me in the previous version.  i can patch it
locally, but it'd be nice to see the fix in our debian package too.

(also, sawfish has been so long outdated in the past that, in my opinion
it'd be really nice to have the latest and greatest these days if at all
possible.)

> Debian, please open a bug report and I will update the package via the
> backports.  The bug report is important before I can update the
> package via backports.

hmm, i just used reportbug to generate this request, and i see the bug
already filled there:

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

or do you mean somewhere else?  i actually use sid, and i don't see
1.12.0 there: should i? i'm just asking because you mention backports:
maybe i'm missing something here?

thanks!
jao
-- 
The folly of mistaking a paradox for a discovery, a metaphor for a proof, a
torrent of verbiage for a spring of capital truths, and oneself for an
oracle, is inborn in us.
 -Paul Valery, poet and philosopher (1871-1945)

Bug#852147: sawfish: Upstream version 1.12.0 available since August 06

[Jose M Calhariz]

Hi Jose,

Sorry, I did not keep up with the upstream because I was busy studying
to be a DD.
I believe there is little difference between the version in stretch and
the upstream. 
But if you find any problem with the version in Debian, please open a
bug report and
I will update the package via the backports.  The bug report is
important before I can
update the package via backports.

Kind regards
Jose M Calhariz

On 21/01/17 23:10, Jose Antonio Ortega Ruiz wrote:
> Package: sawfish
> Version: 3:1.12.0-1nano
> Severity: normal
>
> Dear Maintainer,
>
> I am using the .debs provided upstream by Christian, but it'd be very
> nice if sawfish's packages in debian be updated to the latest version,
> 1.12.0, so that we don't need to depend on non-official repositories.
>
> Thanks a lot!
> jao
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***
>
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages sawfish depends on:
> ii  libatk1.0-0  2.22.0-1
> ii  libc62.24-9
> ii  libcairo21.14.8-1
> ii  libfontconfig1   2.11.0-6.7
> ii  libfreetype6 2.6.3-3+b1
> ii  libgdk-pixbuf2.0-0   2.36.4-1
> ii  libglib2.0-0 2.50.2-2
> ii  libgmp10 2:6.1.2+dfsg-1
> ii  libgtk2.0-0  2.24.31-1
> ii  libice6  2:1.0.9-1+b1
> ii  libpango-1.0-0   1.40.3-3
> ii  libpangocairo-1.0-0  1.40.3-3
> ii  libpangoft2-1.0-01.40.3-3
> ii  libpangoxft-1.0-01.40.3-3
> ii  librep16 3:0.92.6-1nano
> ii  libsm6   2:1.2.2-1+b1
> ii  libx11-6 2:1.6.4-2
> ii  libxext6 2:1.3.3-1
> ii  libxft2  2.3.2-1
> ii  libxinerama1 2:1.1.3-1+b1
> ii  libxrandr2   2:1.5.1-1
> ii  libxrender1  1:0.9.10-1
> ii  libxtst6 2:1.2.3-1
> ii  rep  3:0.92.6-1nano
> ii  rep-gtk  3:0.90.8.3-1nano
> ii  rxvt-unicode-256color [x-terminal-emulator]  9.22-1+b1
> ii  sawfish-data 3:1.12.0-1nano
> ii  xterm [x-terminal-emulator]  327-2
>
> sawfish recommends no packages.
>
> sawfish suggests no packages.
>
> -- no debconf information





signature.asc
Description: OpenPGP digital signature

Bug#852147: sawfish: Upstream version 1.12.0 available since August 06

[Jose Antonio Ortega Ruiz]

Package: sawfish
Version: 3:1.12.0-1nano
Severity: normal

Dear Maintainer,

I am using the .debs provided upstream by Christian, but it'd be very
nice if sawfish's packages in debian be updated to the latest version,
1.12.0, so that we don't need to depend on non-official repositories.

Thanks a lot!
jao

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages sawfish depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgmp10 2:6.1.2+dfsg-1
ii  libgtk2.0-0  2.24.31-1
ii  libice6  2:1.0.9-1+b1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpangoft2-1.0-01.40.3-3
ii  libpangoxft-1.0-01.40.3-3
ii  librep16 3:0.92.6-1nano
ii  libsm6   2:1.2.2-1+b1
ii  libx11-6 2:1.6.4-2
ii  libxext6 2:1.3.3-1
ii  libxft2  2.3.2-1
ii  libxinerama1 2:1.1.3-1+b1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxtst6 2:1.2.3-1
ii  rep  3:0.92.6-1nano
ii  rep-gtk  3:0.90.8.3-1nano
ii  rxvt-unicode-256color [x-terminal-emulator]  9.22-1+b1
ii  sawfish-data 3:1.12.0-1nano
ii  xterm [x-terminal-emulator]  327-2

sawfish recommends no packages.

sawfish suggests no packages.

-- no debconf information

Bug#364975: Any news about this bug?

[Jose M Calhariz]

Thank you for pointing me out this defect.  I will review it at first
opportunity.

Kind regards
Jose M Calhariz


On 17/01/17 12:47, Dmitriy Kovalkov wrote:
> Any news about this bug?
>
> Problem exist in
>
> Last in Arch:
>
> [kovalkov@localhost ~]$ at -V
> at version 3.1.19
> Please report bugs to the Debian bug tracking system (
> http://bugs.debian.org/)
> or contact the maintainers (a...@packages.debian.org).
>
> Last in Ubuntu 16.04:
>
> apt-cache policy at
> at:
>   Installed: (none)
>   Candidate: 3.1.18-2ubuntu1
>   Version table:
>  3.1.18-2ubuntu1 500
> 500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
>
> Last in Debian 8:
>
> root@repo:/# at -V
> at version 3.1.13
> Please report bugs to the Debian bug tracking system (
> http://bugs.debian.org/)
> or contact the maintainers (a...@packages.debian.org).
>
> ---
> Respectfully, Dmitrii Kovalkov
> FASTVPS technical department
>




signature.asc
Description: OpenPGP digital signature

Bug#851611: sawfish: Annoying error message "File error: No such file or directory, gnome"

[Jose M Calhariz]

Yes, it is annoying.  I will talk with the upstream about it, to find a
solution and a workaround.

Kind regards
Jose M Calhariz


On 16/01/17 20:32, Awtul wrote:
> Package: sawfish
> Version: 1:1.11.90-1
> Severity: important
>
> Dear Maintainer,
>
> I get this error message every time I log in Sawfish:
> "Error:
> (Click to dismiss. Also printed to stderr)
> File error: No such file or directory, gnome".
>
> It's really annoying having to click in the pop-up window on each new log in. 
> That's why I have set the bug severity to 'important'.
>
> Regards, Awtul
>
> ---
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages sawfish depends on:
> ii  gnome-terminal [x-terminal-emulator]  3.22.1-1
> ii  libatk1.0-0   2.22.0-1
> ii  libc6 2.24-8
> ii  libcairo2 1.14.8-1
> ii  libfontconfig12.11.0-6.7
> ii  libfreetype6  2.6.3-3+b1
> ii  libgdk-pixbuf2.0-02.36.3-1
> ii  libglib2.0-0  2.50.2-2
> ii  libgmp10  2:6.1.2+dfsg-1
> ii  libgtk2.0-0   2.24.31-1
> ii  libice6   2:1.0.9-1+b1
> ii  libpango-1.0-01.40.3-3
> ii  libpangocairo-1.0-0   1.40.3-3
> ii  libpangoft2-1.0-0 1.40.3-3
> ii  libpangoxft-1.0-0 1.40.3-3
> ii  librep16  0.92.5-3+b1
> ii  libsm62:1.2.2-1+b1
> ii  libx11-6  2:1.6.4-2
> ii  libxext6  2:1.3.3-1
> ii  libxft2   2.3.2-1
> ii  libxinerama1  2:1.1.3-1+b1
> ii  libxrandr22:1.5.1-1
> ii  libxrender1   1:0.9.10-1
> ii  libxtst6  2:1.2.3-1
> ii  lxterminal [x-terminal-emulator]  0.3.0-1
> ii  rep   0.92.5-3+b1
> ii  rep-gtk   1:0.90.8.2-3
> ii  sawfish-data  1:1.11.90-1
> ii  terminator [x-terminal-emulator]  1.90-1
> ii  terminology [x-terminal-emulator] 0.9.1-1
> ii  xterm [x-terminal-emulator]   327-2
>
> sawfish recommends no packages.
>
> Versions of packages sawfish suggests:
> ii  gnome-control-center  1:3.22.1-1
> ii  menu  2.1.47
> ii  yelp  3.22.0-1
>
> -- no debconf information





signature.asc
Description: OpenPGP digital signature

Bug#850713: linux-image-4.8.0-0.bpo.2-amd64: can't mount NFS shares via nfs referrals

[Jose R R]

Niltze [Hello]-

'just my 2 cents':


On Mon, Jan 16, 2017 at 6:39 AM, Christoph Martin <mar...@uni-mainz.de> wrote:
>
> Some more analysis:
>
> attached are two syslogs of gssd in verbose mode.
>
> You can see that in both servers the user acl directory gets mounted
> from fs02 within user context:
>
> rpc.gssd[6528]: handle_gssd_upcall: 'mech=krb5 uid=4015 enctypes
> ...
> rpc.gssd[6528]: creating context using fsuid 4015 (save_uid 0)
>
> When trying to mount the group acl share from fsgroups 4.8 server logs:
>
> rpc.gssd[27548]: handle_gssd_upcall: 'mech=krb5 uid=0 service=*
> ...
> rpc.gssd[27548]: creating context using fsuid 0 (save_uid 0)
>
> the 4.7 server logs:
>
> rpc.gssd[6528]: handle_gssd_upcall: 'mech=krb5 uid=4015
> ...
> rpc.gssd[6528]: creating context using fsuid 4015
>
>
> As a result of this difference the nfs tries to mount the directory on
> 4.7 with a user kerberos ticket and gets NFS4_OK in line 265 of
> linux-4.7-nfsrefer.dump while 4.8 tries with machine kerberos ticket and
> gets NFS4ERR_ACCESS in line 231 of linux-4.8-nfsrefer.dump.
>
> Christoph


I experienced issues installing nfs-common package from official
maintainers jessie repositories during my jessie-backport reiser4
-patched Linux kernel efforts. Accordingly I jessie-backport'ed
nfs-common and nfs-kernel-server packages that you will find at:

https://sourceforge.net/projects/debian-reiser4/files/nfs-common-reiser4-bp/

As a matter of fact just uploaded jessie-backport'ed (kerberos)
krb5-1.15-1 package that I had built priorly -- as part of my initial
efforts building first 2 packages mentioned above.

https://sourceforge.net/projects/debian-reiser4/files/jessie-krb5-1.15-1_bp/

By the way none of those packages have *any dependencies* on reiser4
other than being built in a machine with that file system ;-)

You are welcomed to give those a try but I offer no guarantees whatsoever.


Best Professional Regards.


P.S. you may need krb5-config from Sid (Unstable) -- as the above are backports.
-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#851443: linux-image-4.9.0-1-amd64: Regression from 4.8 under X: USB input devices no more work, degraded resolution, "open /dev/dri/card0: No such file or directory" in Xorg.0.log [Intel Skylake,

[Jose R R]

ew interface driver usbhid
[2.522040] usbhid: USB HID core driver
[2.522885] input: MOSART Semi. 2.4G Keyboard Mouse as
/devices/pci:00/:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:062A:4101.0001/input/input3
[2.580851] hid-generic 0003:062A:4101.0001: input,hidraw0: USB HID
v1.10 Keyboard [MOSART Semi. 2.4G Keyboard Mouse] on
usb-:00:1d.0-1.1/input0
[2.581492] input: MOSART Semi. 2.4G Keyboard Mouse as
/devices/pci:00/:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.1/0003:062A:4101.0002/input/input4
[2.592376] usb 4-1.5: new full-speed USB device number 4 using ehci-pci
[2.640758] hid-generic 0003:062A:4101.0002: input,hiddev0,hidraw1:
USB HID v1.10 Mouse [MOSART Semi. 2.4G Keyboard Mouse] on
usb-:00:1d.0-1.1/input1
[2.705127] usb 4-1.5: New USB device found, idVendor=8086, idProduct=0189
[2.705133] usb 4-1.5: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[   15.460561] usbcore: registered new interface driver btusb

>
> The most relevant difference from the two Xorg.0.log files seems to be:
>
> 4.8: (II) xfree86: Adding drm device (/dev/dri/card0)
> 4.8: xf86EnableIOPorts: failed to set IOPL for I/O (No such device)
> 4.8: (II) modeset(0): using drv /dev/dri/card0
> 4.8: (WW) Falling back to old probe method for fbdev
>
> 4.9: (EE) open /dev/dri/card0: No such file or directory
> 4.9: (WW) Falling back to old probe method for modesetting
> 4.9: (EE) open /dev/dri/card0: No such file or directory
>
> >From then on things seemed to go downhill…
>
> Attached is the full diff between the two files (again, with timing
> information being stripped), generated using "diff -u <(perl -pE
> 's/^\[[^]]*\] *//' < /var/log/Xorg.0.log-4.8) <(perl -pE 's/^\[[^]]*\]
> *//' < /var/log/Xorg.0.log-4.9)", i.e. "-" means "4.8" and "+" means
> "4.9".
>
>
>
> Also attached is the full current Xorg.0.log as happened with 4.9.
>
>
>
>
> -- Package-specific info:
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
> (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), 
> (1, 'buildd-experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
>
> Versions of packages linux-image-4.9.0-1-amd64 depends on:
> ii  initramfs-tools [linux-initramfs-tool]  0.126
> ii  kmod23-2
> ii  linux-base  4.5
>
> Versions of packages linux-image-4.9.0-1-amd64 recommends:
> ii  firmware-linux-free  3.4
> ii  irqbalance   1.1.0-2.2
>
> Versions of packages linux-image-4.9.0-1-amd64 suggests:
> pn  debian-kernel-handbook  
> ii  grub-efi-amd64  2.02~beta3-3
> pn  linux-doc-4.9   
>
> Versions of packages linux-image-4.9.0-1-amd64 is related to:
> pn  firmware-amd-graphics 
> pn  firmware-atheros  
> pn  firmware-bnx2 
> pn  firmware-bnx2x
> pn  firmware-brcm80211
> pn  firmware-cavium   
> pn  firmware-intel-sound  
> pn  firmware-intelwimax   
> pn  firmware-ipw2x00  
> pn  firmware-ivtv 
> pn  firmware-iwlwifi  
> pn  firmware-libertas 
> pn  firmware-linux-nonfree    
> ii  firmware-misc-nonfree 20161130-2
> pn  firmware-myricom  
> pn  firmware-netxen   
> pn  firmware-qlogic   
> pn  firmware-realtek  
> pn  firmware-samsung  
> pn  firmware-siano
> pn  firmware-ti-connectivity  
> pn  xen-hypervisor
>
> -- no debconf information
>

Best Professional Regards.


-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#850731: xorp: segfaults at initialization, linker flags

[Jose M Calhariz]

Hi, I have contacted the upstream author, Ben Greear, about this
problem.  And he requested
if you have a back trace?

> I would be interested in seeing a backtrace if the user has
it  

  

> so I could better understand the problem.  Maybe the code should
never   

 

> actually be trying to call these methods if _root is NULL?   

Can you help the author?

Kind regards
Jose M Calhariz


On 09/01/17 18:42, Dhionel Dí­az wrote:
> Package: xorp
> Version: 1.8.6~wip.20160715-2
> Severity: important
> Tags: patch
>
> Dear Maintainer,
>
> The xorp initialization process was generating segfaults in
> libxorp_rib.so because of null pointer dereferences. After some
> research, it seems that this was a latent bug that was exposed by an
> optimizer improvement included in gcc 6 ("Value range propagation now
> assumes that the this pointer of C++ member functions is non-null").
>
> The attached patch adds some null pointer checks which seem to solve the
> problem, at least for a multicast routing deployment.
>
> On the other hand, the patch also changes a line in debian/rules in
> order to complete the incorporation of hardened build flags. This is
> required because the SCons build system uses the, perhaps somewhat
> unusual, LINKFLAGS variable name for the linker flags.
>
> Some limited testing has been performed in a production router, I hope
> the patch can be useful.
>
> Regards,
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.8.0-2-amd64 (SMP w/1 CPU core)
> Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages xorp depends on:
> ii  adduser  3.115
> ii  init-system-helpers  1.46
> ii  libc62.24-8
> ii  libgcc1  1:6.2.1-5
> ii  libncurses5  6.0+20161126-1
> ii  libpcap0.8   1.8.1-3
> ii  libssl1.11.1.0c-2
> ii  libstdc++6   6.2.1-5
> ii  libsystemd0  232-8
> ii  libtinfo56.0+20161126-1
>
> Versions of packages xorp recommends:
> ii  iputils-ping   3:20161105-1
> ii  iputils-tracepath  3:20161105-1
> ii  traceroute 1:2.1.0-2
>
> xorp suggests no packages.
>
> -- Configuration Files:
> /etc/default/xorp changed [not included]
> /etc/xorp/config.boot changed [not included]
>
> -- no debconf information
>
>




signature.asc
Description: OpenPGP digital signature

Bug#849481: amanda-common: Amanda::Changer::robot::Interface::MTX calls confess but does not use Carp

[jose]

Just to tell that the patch was submitted to the authors of amanda and 
accepted.

This means your fix is relevant to all the versions I have talked about.
Thank you.

Kind regards
Jose M Calhariz

On 2016-12-27 16:54, Will Aoki wrote:

Package: amanda-common
Version: 1:3.3.8-1
Severity: normal
Tags: patch

I've been getting occasional failures that leave the following in the 
report:


  FAILURE DUMP SUMMARY:
taper: FATAL Undefined subroutine
::Changer::robot::Interface::MTX::confess called at
/usr/lib/amanda/perl/Amanda/Changer/robot.pm line 2563.
backup1.nhmu.utah.edu pool/burp lev 0  FAILED [out of holding
space in degraded mode]
backup1.nhmu.utah.edu pool/burp lev 0  FAILED [data write: Broken 
pipe]


The cause of the failure seems to be a fork failing, but a bug in 
AMANDA's
error-handling code is masking the first problem. This module calls 
confess(),

but it doesn't use Carp first or otherwise declare 

--- /tmp/robot.pm   2016-12-27 09:41:57.285488949 -0700
+++ /usr/lib/amanda/perl/Amanda/Changer/robot.pm2016-12-27
09:41:34.045222046 -0700
@@ -2359,6 +2359,7 @@
 use Amanda::Debug qw( debug warning );
 use Amanda::MainLoop qw( :GIOCondition synchronized make_cb
define_steps step );
 use Amanda::Device qw( :constants );
+use Carp;

 sub new {
 my $class = shift;

Bug#849481: amanda-common: Amanda::Changer::robot::Interface::MTX calls confess but does not use Carp

[Jose M Calhariz]

Thank you for your patch.  I will study it and see if it is applicable
to 3.3.9, the version on unstable, and against 3.4.1, the latest from
the authors.

Kind regards
Jose M Calhariz


On 27/12/16 16:54, Will Aoki wrote:
> Package: amanda-common
> Version: 1:3.3.8-1
> Severity: normal
> Tags: patch
>
> I've been getting occasional failures that leave the following in the report:
>
>   FAILURE DUMP SUMMARY:
> taper: FATAL Undefined subroutine 
> ::Changer::robot::Interface::MTX::confess called at 
> /usr/lib/amanda/perl/Amanda/Changer/robot.pm line 2563.
> backup1.nhmu.utah.edu pool/burp lev 0  FAILED [out of holding space in 
> degraded mode]
> backup1.nhmu.utah.edu pool/burp lev 0  FAILED [data write: Broken pipe]
>
> The cause of the failure seems to be a fork failing, but a bug in AMANDA's
> error-handling code is masking the first problem. This module calls confess(),
> but it doesn't use Carp first or otherwise declare 
>
> --- /tmp/robot.pm 2016-12-27 09:41:57.285488949 -0700
> +++ /usr/lib/amanda/perl/Amanda/Changer/robot.pm  2016-12-27 
> 09:41:34.045222046 -0700
> @@ -2359,6 +2359,7 @@
>  use Amanda::Debug qw( debug warning );
>  use Amanda::MainLoop qw( :GIOCondition synchronized make_cb define_steps 
> step );
>  use Amanda::Device qw( :constants );
> +use Carp;
>  
>  sub new {
>  my $class = shift;





signature.asc
Description: OpenPGP digital signature

Bug#848133: RFS: rdup/1.1.15-1.0

[Jose Carlos Garcia Sogo]

I am not missing, but not in action either. I will take the long needed
steps in the upcoming days.

Thanks

El mar., 27 dic. 2016 11:34, Tobias Frost <t...@debian.org> escribió:

> Hi Félix,
>
> On Mon, Dec 26, 2016 at 11:18:36PM +0100, Félix Sipma wrote:
> > I think I won't have time to work on this soon, so my changes won't be
> for
> > stretch anyway. I propose to try to fix the issues you mentioned in your
> > previous email, and to start the MIA process. At what step of
> > https://wiki.debian.org/qa.debian.org/MIATeam should I start? Is it
> possible to
> > start at "Suggest orphaning" with a mail to Jose and the MIA team in Cc:?
>
> You've reached a MIA team member already, so there is no action required
> from
> your side, I'll take over from here.
> (And, no, sorry, we cannot cut corners on the process; the process as is
> has been
> established for reasons)
>
> > I hope you Jose will be able to answer in the meantime, that will of
> course be
> > the easiest!
>
> Indeed, Jose, let me again appeal to you for an quick answer.. This will
> save
> several people lots of work.
>
> Another option which has been proposed in similar cases by the MIA team in
> the past*,
> if you're like to (co-)maintain rdup:
> - Announce on the BTS that you'll like to be Co-Maintainer of the package.
> - Wait for a at least 2 weeks for a reply; After a week, write a ping.
>   if there isn't an answer, go on...
> - Prepare an NMU according to the rules (see dev-ref; let me hint you again
>   that it "must only fix bugs!")
> - Add yourself as Uploader in this NMU
> - Announce the NMU on the BTS, target: DELAYED/15. The announcement must be
>   very clear about that you're adding yourself as co-maintainer and
> explictily
>   stress that this will happen if there is no response. Give that
> information
>   also to the bug you have filed earlier. (It must be crystal clear what
> the
>   intentions are)
> - Upload to DELAYED/15. (Any intervention by the maintainer will lead to
>   cancelation of the upload.)
> - After it has entered the archives, you're comaintainer and can act
> accordingly.
> - The MIA process will then run in parallel and depending on the result we
> will
>   either ask you to remove Jose as maintainer or his maintainer status
> will be
>   confirmed. He might also ask you to hand back the package to you,
> (you'll then
>   to follow then)
>
> * Example: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836008, even
> if that
> one went never live.
> Please note that this is procedure is non-standard and is considering the
> circumstances of this particular potential-MIA case.
>
> But as the Stretch window has closed, so I suggest to just wait for the MIA
> process to be completed. If you still want to pursuit it, uploads will
> have to
> go to experimental anyway.
>
> >
> >
> > Félix
>
> --
> tobi (MIA team member)
>

Bug#849305: ITP: python-shutilwhich -- A backport of Python3's shutil.which module

[Jeffrin Jose T]

sorry typo ... it is rkrish...@debian.org

Bug#849305: ITP: python-shutilwhich -- A backport of Python3's shutil.which module

[Jeffrin Jose T]

Sorry if any problem, the correction was earlier made by krishnan@debia
n.org  himself

Bug#849305: ITP: python-shutilwhich -- A backport of Python3's shutil.which module

[Jeffrin Jose]

may be a url correction is needed https://github.com/mbr/shutilshich   (not 
correct )

"https://github.com/mbr/shutilwhich; (correct) 

On Sunday, 25 December 2016 11:51 AM, Ramakrishnan Muthukrishnan 
 wrote:
 
 

 Package: wnpp
Severity: wishlist
Owner: Ramakrishnan Muthukrishnan 

* Package name    : python-shutilwhich
  Version        : 1.1.0
  Upstream Author : Marc Brinkmann 
* URL            : https://github.com/mbr/shutilshich
* License        : Python-3
  Programming Lang: Python
  Description    : A backport of Python3's shutil.which module

This is a port of Python 3's shutil.which module mostly copied and pasted
from Python 3 source.
.
This package contains the Python 2 module.



 
   

Bug#849268: installation-reports: Jessie-backported Reiser4-patched Linux 4.8.15-1 on UpCloud 8-core/48Gig RAM KVM Cloud infrastructure successful installation

[Jose R Rodriguez]

Package: installation-reports
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: netboot ISO image 'dd' /dev/vdb
Image version: https://sourceforge.net/projects/debian-reiser4/ built on 
12-23-2016
Date: 12-24-2016 01:56 AM PST

Machine: https://www.upcloud.com KVM Cloud infrastructure
Partitions:
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs  98931408976   9884164   1% /run
/dev/vda6  reiser4   20423272 4523220  15900052  23% /
tmpfs  tmpfs 24732840 144  24732696   1% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
tmpfs  tmpfs 24732840   0  24732840   0% /sys/fs/cgroup
/dev/vda5  jfs9725448   10252   9715196   1% /home
/dev/vda1  ext2188403   22408156267  13% /boot
tmpfs  tmpfs  4946572  20   4946552   1% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:
Analyzing the 'various bugfixes and fixed vulnerabilities' in Sid kernel 
4.8.15-1
I realized I had to do a Jessie-backports for Reiser4 (SFRN) 4.0.1 AND test 
neboot
installation in massive KVM Cloud instance of 12-cores / 48 Gig RAM.

"We also encourage installation reports to be sent even if the installation is 
successful,
so that we can get as much information as possible on the largest number of 
hardware configurations"
< https://www.debian.org/releases/stable/amd64/ch05s04.html.en#submit-bug >

Smooth installation of Reiser4-enabled kernel 4.8.15-1 & reiser4progs 
built/fetched for Jessie
netboot installer.

Only conflict is with nfs-commmon -- which hangs the newly installed Reiser4 
Linux OS upon boot.
Accordingly this particular Debian netboot installer will purge nfs-common at 
end of installation
so that GNU/Linux Debian Jessie OS boots without issues from its initial ext2 
boot ~150MB partition
into Reiser4 root file system.

https://metztli.it/readOnlyEphemeral/Cohuatlicue_UpCloud.png

Notice below - netboot installer UDEB kernel only differs in name 'Cohuatlicue' 
from kernel 4.8.15-1
downloaded via SSL from meztli.it

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20161224-05:26"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux cohuatlicue 4.8.0-2+cohuatlicue-amd64 #1 SMP Debian 
4.8.15-1+cohuatlicue (2016-12-22) x86_64 Xonecuiltzin
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: 00:01.2 USB controller [0c03]: Intel Corporation 82371SB PIIX3 USB 
[Natoma/Triton II] [8086:7020] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 
[1013:00b8]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:03.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block 
device [1af4:1001]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:0002]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: 00:10.0 

Bug#838071: fixed in up-imapproxy 1.2.8~svn20161210-1

[Jose Luis Tallon]

On 12/12/2016 10:09 PM, Tobias Frost wrote:
> Control: reassign -1 up-imapproxy 
> Control: reopen -1
> Control: found -1 1.2.8~svn20161210-1
> Control: retitle -1 Please update the Uploaders field.
> Control: severity -1 minor
>
> Reopening, as Jose Luis Tallon <jltal...@adv-solutions.net> ist still
> listed as Maintainer in d/control, but should have been removed after
> you adopted the package.

Why?  I was involved in this upload, though only marginally.
I guess co-maintainership is now frowned upon?

> We are tracking their status in the MIA team and would like to ask you
> to remove them from the Uploaders list of the package so we can close
> that part of the file.

Hmm.. So?
> As the Jose was listed as Maintainer, what we are asking is to please
> step in as a new maintainer.

I don't know your nationality or whether English is your native
language but that superfluous "the" surely was offensive.


/ J.L.

Bug#828586: Building with OpenSSL 1.0.2 is sufficient for stretch

[Jose Luis Tallon]

On 12/11/2016 12:58 AM, Adrian Bunk wrote:
> Not a perfect solution but sufficient for stretch is the patch below to 
> use OpenSSL 1.0.2

Thank you for the patch!

Richard Laager has been preparing a new version, including all pending
patches. CC'ing him so that we keep synchronized.
Tony Mancill has agreed to sponsor that upload.

> The "| libssl-dev (<< 1.1.0~)" is added for backports.
>
> --- debian/control.old2016-12-10 23:57:31.0 +
> +++ debian/control2016-12-10 23:57:36.0 +
> @@ -3,7 +3,7 @@
>  Priority: optional
>  Maintainer: Jose Luis Tallon <jltal...@adv-solutions.net>
>  Build-Depends: autotools-dev, debhelper (>= 5), po-debconf (>= 0.8.2), 
> - libwrap0-dev, libncurses-dev, libssl-dev, dh-systemd
> + libwrap0-dev, libncurses-dev, libssl1.0-dev | libssl-dev (<< 1.1.0~), 
> dh-systemd
>  Homepage: http://www.imapproxy.org
>  Standards-Version: 3.8.4
>  
>
>
> cu
> Adrian
>

Bug#847230: installation-reports: Reiser4 successfull remote install on Cloud provider KVM infrastructure via netboot image

[Jose R Rodriguez]

Package: installation-reports
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: netboot/virtual-disk
Image version: Debian-Reiser4 Jessie 
https://sourceforge.net/projects/debian-reiser4/
Date:  Dec 06, 2016 03:09 am, Pacific Standard Time (PST)

Machine: upCloud Provider https://www.upcloud.com/ QEMU/KVM cloud 
Infrastructure-as-a-Service (IaaS)
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs   2041004468199632   3% /run
/dev/vda5  reiser4   18650464 1003996  17646468   6% /
tmpfs  tmpfs   510244   0510244   0% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
tmpfs  tmpfs   510244   0510244   0% /sys/fs/cgroup
/dev/vda6  jfs   116331041944  11631160   1% /home
/dev/vda1  ext2140805   34447 99088  26% /boot


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems: netbooted off a 10Gb virtual-disk where Reiser4-enabled 
netboot installer
was transfered thus:
dd if=~/metztli.iso of=/dev/vdb bs=16M oflag=direct
< https://www.upcloud.com/support/using-own-installation-media/ >

Smooth Reiser4-enabled Jessie installer with newer relevant 
jessiena links to 
linux-image-4.7.0-1+reiser4.0.1-amd64_4.7.8-1+reiser4.0.1_amd64.deb
< https://metztli.it/readOnlyEphemeral/shot-2016-12-06_02-57-27.jpg >

Detected and carved from a 30 Gb existing virtual disk, partitioned, and 
formatted
its root file system in Reiser4 (SFRN) 4.0.1.

Debian-Reiser4 netboot detected remote network *beautifully* as I have no 
issues when
submitting this report:
< https://metztli.it/readOnlyEphemeral/tlaloccitlalli-2016-12-06_08-42-39.jpg  >

---fragment of /var/log/syslog
Dec  6 03:41:56 tlaloccitlalli rsyslogd: [origin software="rsyslogd" 
swVersion="8.4.2" x-pid="517" x-info="http://www.rsyslog.com;] start
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] Linux version 
4.7.0-1+reiser4.0.1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.2 
(Debian 4.9.2-10) ) #1 SMP Debian 4.7.8-1+reiser4.0.1 (2016-10-26)
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] Command line: 
BOOT_IMAGE=/vmlinuz-4.7.0-1+reiser4.0.1-amd64 root=/dev/vda5 ro quiet
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: 
xstate_offset[2]:  576, xstate_sizes[2]:  256
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: Supporting XSAVE 
feature 0x001: 'x87 floating point registers'
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: Supporting XSAVE 
feature 0x002: 'SSE registers'
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: Supporting XSAVE 
feature 0x004: 'AVX registers'
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: Enabled xstate 
features 0x7, context size is 832 bytes, using 'standard' format.
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] x86/fpu: Using 'eager' 
FPU context switches.
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] e820: BIOS-provided 
physical RAM map:
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] BIOS-e820: [mem 
0x-0x0009fbff] usable
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] BIOS-e820: [mem 
0x0009fc00-0x0009] reserved
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] BIOS-e820: [mem 
0x000f-0x000f] reserved
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] BIOS-e820: [mem 
0x0010-0x3fff8fff] usable
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] BIOS-e820: [mem 
0x3fff9000-0x3fff] reserved
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] BIOS-e820: [mem 
0xfeffc000-0xfeff] reserved
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] BIOS-e820: [mem 
0xfffc-0x] reserved
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] NX (Execute Disable) 
protection: active
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] SMBIOS 2.4 present.
Dec  6 03:41:56 tlaloccitlalli kernel: [0.00] DMI: UpCloud Cloud 
Server, BIOS Bochs 

Bug#846503: zeroc-icegridgui: Java exception when running the program

[Jose Gutierrez de la Concha]

Hi,

I'm waiting for somebody to upload the package, I don't have upload
permissions yet. Shouldn't take too long, I can send you the new .deb file
or you can build it yourself from the repository
https://github.com/zeroc-ice/ice-debian-packaging using 3.6 branch



On Fri, Dec 2, 2016 at 1:33 PM, José Luis Segura Lucas <josel.seg...@gmx.es>
wrote:

> When will be the new version available?
>
> Is it possible to download the deb? I need icegridgui ASAP.
>
> Best regards
>
>
> On 02/12/16 11:41, Jose Gutierrez de la Concha wrote:
>
> Hi
>
> That is due to the package not being rebuild with the new version,
> that is not binary compatible with the previous version.
>
>
> On Thu, Dec 1, 2016 at 6:25 PM, José Luis Segura Lucas <
> josel.seg...@gmx.es> wrote:
>
>> Package: zeroc-icegridgui
>> Version: 3.6.3-2
>> Severity: grave
>> Justification: renders package unusable
>>
>> Dear Maintainer,
>>
>> After manually fulfilling the missing dependencies from the bug #846498, I
>> still get an error.
>>
>> $ icegridgui
>> Exception in thread "AWT-EventQueue-1" java.lang.NoSuchFieldError: DIALOG
>> at IceGridGUI.LiveDeployment.ObjectDialog.(ObjectDialog.
>> java:60)
>> at IceGridGUI.LiveDeployment.Root.(Root.java:172)
>> at IceGridGUI.Coordinator.(Coordinator.java:2579)
>> at IceGridGUI.Main.(Main.java:111)
>> at IceGridGUI.Main$1.run(Main.java:60)
>> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.
>> java:311)
>> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
>> at java.awt.EventQueue.access$500(EventQueue.java:97)
>> at java.awt.EventQueue$3.run(EventQueue.java:709)
>> at java.awt.EventQueue$3.run(EventQueue.java:703)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at
>> java.security.ProtectionDomain$JavaSecurityAccessImpl.doInte
>> rsectionPrivilege(ProtectionDomain.java:76)
>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
>> at
>> org.GNOME.Accessibility.AtkWrapper$5.dispatchEvent(AtkWrapper.java:700)
>> at
>> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDis
>> patchThread.java:201)
>> at
>> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispat
>> chThread.java:116)
>> at
>> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDis
>> patchThread.java:105)
>> at
>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
>> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.
>> java:93)
>> at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
>>
>> I must say that manually installing the missing dependencies of the bug
>> mentioned above are working from a while, but today I just realized that,
>> right
>> now, it is impossible to execute icegridgui without getting errors.
>>
>>
>>
>> -- System Information:
>> Debian Release: stretch/sid
>>   APT prefers unstable
>>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>>
>> Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /usr/bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages zeroc-icegridgui depends on:
>> ii  default-jdk   2:1.8-57
>> ii  default-jre   2:1.8-57
>> ii  libzeroc-ice3.6-java  3.6.3-2
>> ii  openjdk-8-jdk 8u111-b14-3
>> ii  openjdk-8-jre 8u111-b14-3
>>
>> zeroc-icegridgui recommends no packages.
>>
>> zeroc-icegridgui suggests no packages.
>>
>> -- no debconf information
>>
>
>
>
> --
> José Gutiérrez de la Concha
> ZeroC, Inc.
>
>
>


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

Bug#846503: zeroc-icegridgui: Java exception when running the program

[Jose Gutierrez de la Concha]

Hi

That is due to the package not being rebuild with the new version,
that is not binary compatible with the previous version.


On Thu, Dec 1, 2016 at 6:25 PM, José Luis Segura Lucas 
wrote:

> Package: zeroc-icegridgui
> Version: 3.6.3-2
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> After manually fulfilling the missing dependencies from the bug #846498, I
> still get an error.
>
> $ icegridgui
> Exception in thread "AWT-EventQueue-1" java.lang.NoSuchFieldError: DIALOG
> at IceGridGUI.LiveDeployment.ObjectDialog.(
> ObjectDialog.java:60)
> at IceGridGUI.LiveDeployment.Root.(Root.java:172)
> at IceGridGUI.Coordinator.(Coordinator.java:2579)
> at IceGridGUI.Main.(Main.java:111)
> at IceGridGUI.Main$1.run(Main.java:60)
> at java.awt.event.InvocationEvent.dispatch(
> InvocationEvent.java:311)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
> at java.awt.EventQueue.access$500(EventQueue.java:97)
> at java.awt.EventQueue$3.run(EventQueue.java:709)
> at java.awt.EventQueue$3.run(EventQueue.java:703)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> java.security.ProtectionDomain$JavaSecurityAccessImpl.
> doIntersectionPrivilege(ProtectionDomain.java:76)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
> at
> org.GNOME.Accessibility.AtkWrapper$5.dispatchEvent(AtkWrapper.java:700)
> at
> java.awt.EventDispatchThread.pumpOneEventForFilters(
> EventDispatchThread.java:201)
> at
> java.awt.EventDispatchThread.pumpEventsForFilter(
> EventDispatchThread.java:116)
> at
> java.awt.EventDispatchThread.pumpEventsForHierarchy(
> EventDispatchThread.java:105)
> at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
> at java.awt.EventDispatchThread.pumpEvents(
> EventDispatchThread.java:93)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
>
> I must say that manually installing the missing dependencies of the bug
> mentioned above are working from a while, but today I just realized that,
> right
> now, it is impossible to execute icegridgui without getting errors.
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages zeroc-icegridgui depends on:
> ii  default-jdk   2:1.8-57
> ii  default-jre   2:1.8-57
> ii  libzeroc-ice3.6-java  3.6.3-2
> ii  openjdk-8-jdk 8u111-b14-3
> ii  openjdk-8-jre 8u111-b14-3
>
> zeroc-icegridgui recommends no packages.
>
> zeroc-icegridgui suggests no packages.
>
> -- no debconf information
>



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

Bug#846498: zeroc-icegridgui: Missing dependencies

[Jose Gutierrez de la Concha]

Hi José,

I will upload a new package with missing dependencies soon.

On Thu, Dec 1, 2016 at 5:46 PM, José Luis Segura Lucas 
wrote:

> Package: zeroc-icegridgui
> Version: 3.6.3-2
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> icegridgui needs two Java graphical libraries to work. The missing
> dependencies
> are:
>
> * libjgoodies-forms-java
> * libjgoodies-looks-java
>
> Best regards
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages zeroc-icegridgui depends on:
> ii  default-jdk   2:1.8-57
> ii  default-jre   2:1.8-57
> ii  libzeroc-ice3.6-java  3.6.3-2
> ii  openjdk-8-jdk 8u111-b14-3
> ii  openjdk-8-jre 8u111-b14-3
>
> zeroc-icegridgui recommends no packages.
>
> zeroc-icegridgui suggests no packages.
>
> -- no debconf information
>



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

Bug#845461: gcc-6: Please build with --with-cpu=ultrasparc on sparc

[Jose E. Marchesi]

I'm pretty confident that --with-cpu=ultrasparc won't do any harm in
64-bit mode, but Jose (CC'ed as gcc upstream) will hopefully correct
me here if I'm wrong.

The cpu selected in --with-cpu impacts both -m64 and -m32 in a biarch
compiler.  However, I can't say anything about the patch since I lack
the most basic context here, i.e. I have no idea what the contents of
that rules2 file are.

Bug#845461: gcc-6: Please build with --with-cpu=ultrasparc on sparc

[Jose E. Marchesi]

> Currently, rebootstrap fails on sparc-linux-gnu because the gcc-6
> package no longer builds with --mcpu=ultrasparc on this target.
> This was previously with the sparc-force-cpu.diff patch which
> got removed while fixing the multilib issue on sparc64.
> 
> What is the issue with GCC 6 and --mpu=ultrasparc?

We want to make sure that gcc-6 is built with --with-cpu=ultrasparc on
32-bit sparc-linux-gnu (which is currently only present in Debian
rebootstrap [1]). The question is whether my suggested patch to
do that is correct.

Ah, I thought you said that GCC 6 was not building anymore with
--mcpu=ultrasparc due to some bug.  You mean that the debian package is
no longer using that option.

Bug#845461: gcc-6: Please build with --with-cpu=ultrasparc on sparc

[Jose E. Marchesi]

Currently, rebootstrap fails on sparc-linux-gnu because the gcc-6
package no longer builds with --mcpu=ultrasparc on this target.
This was previously with the sparc-force-cpu.diff patch which
got removed while fixing the multilib issue on sparc64.

What is the issue with GCC 6 and --mpu=ultrasparc?

Bug#842040: Please add https support

[Jose R R]

On Fri, Nov 18, 2016 at 8:18 AM, Philipp Kern <pk...@debian.org> wrote:
> On 12.11.2016 18:16, Josh Triplett wrote:
>> On Thu, 10 Nov 2016 01:14:33 -0800 Jose R R <jose@metztli-it.com> wrote:
>>> On Tue, Oct 25, 2016 at 6:17 AM, Marga Manterola <ma...@google.com> wrote:
>>>> Package: debian-installer
>>>> Severity: normal
>>>>
>>>> The installer currently doesn't support downloading packages from https
>>>> mirrors, because busybox's wget doesn't support https.
>>>
>>> In order to add SSL support to BusyBox wget, itself to be used wih
>>> ssl_helper, I used matrixssl-3-4-2-open.tgz
>>> < http://www.matrixssl.org/ >
>>>
>>> to build my custom BusyBox udeb for my Reiser4-enabled Debian-Installer
>>> < https://sf.net/projects/debian-reiser4/ >
>>>
>>> No idea if suggestion fulfills bug need - just my 2 cents ;-)
>>
>> Can you provide a link for your patches to busybox wget to add SSL
>> support?  That sounds like it'd substantially decrease size compared to
>> including GNU wget and supporting libraries.
>
> Unfortunately matrixssl isn't even in Debian at this point.
>
The official Debian maintainer(s) busybox source lacks a directory
that is upstream in the busybox official source.
For instance, for upstream busybox-1.25.1, the relevant path to *that*
directory is:

busybox-1.25.1/networking/ssl_helper

then,
If we untar matrixssl-3-4-2-open.tgz , we get directory

matrixssl-3-4-2-open/

copying ssl_helper directory into matrixssl-3-4-2-open/., we build
first matrixssl:

make

After successful build:

cd ssl_helper

./ssl_helper.sh  ## to compile and link the helper, thus

ssl_helper.c generates ssl_helper executable (and ssl_helper.o ? ;-)

To provide SSL-enabled busybox wget you only need the executable ssl_helper

hence,

Prior to building your busybox udeb

create a directory inside your 'official' Debian maintainers busybox
untarred source

mkdir --verbose -p _install/usr/bin

copy your generated executable ssl_helper into above directory, i.e.,

_install/usr/bin/ssl_helper   ##<== executable should be this and here

>From this dirty hack, *any* Debian-helper-generated busybox UDEB
should contain busybox SSL-enabled wget

Sorry, I am busy - but will try to create a patch for official Debian
source from git -- though I am not an official Debian maintainer.

sample from my reiser4 Debian-Installer (d-i):
< 
https://metztli.it/readOnlyEphemeral/busybox-udeb_1.22.0-19.1_amd64.udeb.SHA256SUM
># Text contents
< https://metztli.it/readOnlyEphemeral/busybox-udeb_1.22.0-19.1_amd64.udeb >

If above udeb link is downloaded locally, it may be expanded to analyze as:
dpkg -X busybox-udeb_1.22.0-19.1_amd64.udeb  tempDir

Happy hacking!


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#844446: linux-image-4.8.0-1-amd64: Fails to boot on qemu/kvm

[Jose R R]

system: Red Hat, Inc Virtio RNG [1af4:0004]
> Physical Slot: 6
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
> Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> SERR-  Latency: 0
> Interrupt: pin A routed to IRQ 10
> Region 0: I/O ports at c0e0 [size=32]
> Kernel driver in use: virtio-pci
> Kernel modules: virtio_pci
>
>
> ** USB devices:
> Bus 004 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages linux-image-4.8.0-1-amd64 depends on:
> ii  initramfs-tools [linux-initramfs-tool]  0.125
> ii  kmod23-1
> ii  linux-base  4.5
>
> Versions of packages linux-image-4.8.0-1-amd64 recommends:
> ii  firmware-linux-free  3.4
> ii  irqbalance   1.1.0-2
>
> Versions of packages linux-image-4.8.0-1-amd64 suggests:
> pn  debian-kernel-handbook  
> ii  grub-pc 2.02~beta3-3
> pn  linux-doc-4.8   
>
> Versions of packages linux-image-4.8.0-1-amd64 is related to:
> pn  firmware-amd-graphics 
> pn  firmware-atheros  
> pn  firmware-bnx2 
> pn  firmware-bnx2x
> pn  firmware-brcm80211
> pn  firmware-cavium   
> pn  firmware-intel-sound  
> pn  firmware-intelwimax   
> pn  firmware-ipw2x00  
> pn  firmware-ivtv 
> pn  firmware-iwlwifi  
> pn  firmware-libertas 
> pn  firmware-linux-nonfree
> pn  firmware-misc-nonfree 
> pn  firmware-myricom  
> pn  firmware-netxen   
> pn  firmware-qlogic   
> pn  firmware-realtek  
> pn  firmware-samsung  
> pn  firmware-siano
> pn  firmware-ti-connectivity  
> pn  xen-hypervisor
>
> -- no debconf information

Good luck!


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA

[Jose M Calhariz]

Is to tell that the new 4.9-rc works.  Now I can login into the
machine.  During the weekend I will do a longer review of the kernel in
search of regressions. 

Thank you.

Kind regards
Jose M Calhariz

On 16/11/16 17:01, Santiago Vila wrote:
> forcemerge 833016 841007
> thanks
>
> Hi.
>
> You will see that both bugs belong to the "src:linux" package,
> so it's better not to file duplicates. To tell the BTS that
> a certain version has the bug, we have a "found" command.
>
> I'm merging the bugs with this message.
>
> BTW: There is a 4.9-rc version in experimental, you might want to give
> it a try and say here if there is any improvement.
>
> Thanks.





signature.asc
Description: OpenPGP digital signature

Bug#843700: amanda-common: missing dependency on perlapi-*

[Jose M Calhariz]

Hi, 

I need help to verify this fix.

On 08/11/16 20:56, Niko Tyni wrote:
> Package: amanda-common
> Version: 1:3.3.9-2
> Severity: serious
> X-Debbugs-Cc: p...@packages.debian.org
>
> This package contains binary Perl modules but doesn't depend on perlapi-*
> (currently perlapi-5.24.1).
>
> Quoting the Debian Perl Policy 4.4.2 ("Binary and Other Architecture
> Dependent Modules"):
>
>   Additionally, all binary modules (regardless of their installation
>   directory) and any other modules installed into $Config{vendorarch} must
>   depend on the expansion of perlapi-$Config{debian_abi} using the Config
>   module. If $Config{debian_abi} is empty or not set, $Config{version}
>   must be used.
>
> This used to work (since #582220) but seems to have regressed recently
> with 1:3.3.9-1 that switched to dh-style debian/rules, dropping the
> 'dh_perl -a usr/lib/amanda/perl' call. The default dh behaviour doesn't
> know where to look for the private directory (which currently seems to
> be /usr/lib//amanda/perl). Possibly something like
>
> override_dh_perl:
>   dh_perl /usr/lib/*/amanda/perl

I think the flag -V is needed, but the generated depends still lack
perlapi-*

Depends: adduser,
bsd-mailx | mailx,
debconf (>= 0.5) | debconf-2.0,
openbsd-inetd | inet-superserver,
update-inetd,
perl (>= 5.24.1~rc3-3),
libc6 (>= 2.15),
libcurl3 (>= 7.16.2),
libglib2.0-0 (>= 2.41.1),
libssl1.1 (>= 1.1.0)



>
> will do the trick.
>
> Note that this is the root cause for #839603 / #839392: if the package had
> had the correct dependencies, it would have been automatically binNMU'd
> by the release team along with the other 600+ packages during the Perl
> 5.24 transition.
>
> Even when this is fixed, partial upgrades of amanda-common from 1:3.3.9-1
> without upgrading perl will be a problem, particularly as Ubuntu has
> made a release with something based on 1:3.3.9-1. It looks like we need
> to add a Breaks on the perl side to make sure broken combinations can't
> happen.

Kind regards

Jose M Calhariz





signature.asc
Description: OpenPGP digital signature

Bug#843852: amanda-common: Cannot run amdump - and report about missing ssl symbols

[Jose M Calhariz]

I investigated this defect and I do not understand what went wrong
because a recompile make it work again.
This package have a pending upload to fix the build with openssl 1.1.0.

Can you downgrade to testing?

Kind regards
Jose M Calhariz


On 10/11/16 08:49, Kamil Jonca wrote:
> Package: amanda-common
> Version: 1:3.3.9-2
> Severity: grave
> Justification: renders package unusable
>
> amdump ends prematurely with report:
> an't load 
> '/usr/lib/x86_64-linux-gnu/amanda/perl/auto/Amanda/Debug/libDebug.so' for 
> module Amanda::Debug: /usr/lib/x86_64-linux-gnu/amanda/libamanda-3.3.9.so: 
> undefined symbol: SSL_library_init at 
> /usr/lib/x86_64-linux-gnu/perl/5.24/DynaLoader.pm line 187.
>  at /usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/Debug.pm line 11.
> Compilation failed in require at 
> /usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/Config/FoldingHash.pm line 5.
> BEGIN failed--compilation aborted at 
> /usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/Config/FoldingHash.pm line 5.
> Compilation failed in require at 
> /usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/Config.pm line 753.
> BEGIN failed--compilation aborted at 
> /usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/Config.pm line 753.
> Compilation failed in require at /usr/sbin/amdump line 29.
> BEGIN failed--compilation aborted at /usr/sbin/amdump line 29.
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages amanda-common depends on:
> ii  adduser   3.115
> ii  bsd-mailx [mailx] 8.1.2-0.20160123cvs-3
> ii  debconf [debconf-2.0] 1.5.59
> ii  libc6 2.24-5
> ii  libcurl3  7.51.0-1
> ii  libglib2.0-0  2.50.2-1
> ii  libssl1.0.2   1.0.2j-4
> ii  openbsd-inetd [inet-superserver]  0.20140418-2
> pn  perl:any  
> ii  update-inetd  4.43
>
> amanda-common recommends no packages.
>
> Versions of packages amanda-common suggests:
> ii  amanda-client  1:3.3.9-2
> ii  amanda-server  1:3.3.9-2
>
> -- Configuration Files:
> /etc/amandahosts [Errno 13] Permission denied: u'/etc/amandahosts'
>
> -- debconf information:
>   amanda-common/merge_amandates:





signature.asc
Description: OpenPGP digital signature

Bug#842040: Please add https support

[Jose R R]

Niltze [Hello]!

On Tue, Oct 25, 2016 at 6:17 AM, Marga Manterola <ma...@google.com> wrote:
> Package: debian-installer
> Severity: normal
>
> The installer currently doesn't support downloading packages from https
> mirrors, because busybox's wget doesn't support https.

In order to add SSL support to BusyBox wget, itself to be used wih
ssl_helper, I used matrixssl-3-4-2-open.tgz
< http://www.matrixssl.org/ >

to build my custom BusyBox udeb for my Reiser4-enabled Debian-Installer
< https://sf.net/projects/debian-reiser4/ >

No idea if suggestion fulfills bug need - just my 2 cents ;-)

>
> The wget package has been changed to provide a udeb, compiled against the
> libssl udeb, so that it provides https support.
>
> The change needed in d-i is to add the wget udeb and it's dependencies
> (libcrypto1.0.2, libssl1.0.2 and libpcre3) to the initrd.
>
> Regarding total size (as this was mentioned when I discussed this in the
> past), this is the size of the needed udebs:
> -rw-r- 1 marga marga 878072 Sep 26 20:17
> libcrypto1.0.2-udeb_1.0.2j-1_amd64.udeb
> -rw-r- 1 marga marga 153852 Aug 19 12:59 libpcre3-udeb_8.39-2_amd64.udeb
> -rw-r- 1 marga marga 141318 Sep 26 20:17
> libssl1.0.2-udeb_1.0.2j-1_amd64.udeb
> -rw-r- 1 marga marga 147960 Sep 26 15:19 wget-udeb_1.18-4_amd64.udeb
>
> And this is the size difference of the old initrd and the new one:
> -rw-r- 1 marga eng 22580707 Oct 25 02:07 initrd.gz
> -rw-r- 1 marga eng 23381570 Oct 25 15:11 newinitrd.gz
>
> So, approximately 780k extra for the initrd image (3.5% increase)
>
> Thanks!
> --
> Cheers,
> Marga


Best Professional Regards

-- 
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[Jose R R]

On Mon, Oct 31, 2016 at 12:31 AM, Konstantin Demin <rockdri...@gmail.com> wrote:
> I have tested several scenarios and "KCPPFLAGS=-fno-PIE" does that
> trick much better :-)
>
> --
> SY,
> Konstantin Demin
uname -a
Linux cohuatlicue 4.7.10.tezcatlipoca #1 SMP PREEMPT Mon Oct 31
09:47:07 PDT 2016 x86_64 GNU/Linux

i.e., Aufs4/Reiser4 kernel re-built with your suggestion, as:

time KCPPFLAGS="-fno-PIE" fakeroot make-kpkg
--append-to-version=.tezcatlipoca --stem gcc6-aufs4+reiser4m -j8
--initrd kernel_image kernel_headers

Thanks again, Konstantin.


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#839603: Problem was already deal with a binNMU

[jose]

The problem in this defect was already fixed by a binNMU.  But anyway I 
have a new amanda_3.3.9-2 that closes this defect.

Bug#828232: Package ready, waiting for sponsor

[jose]

I have a new amanda_3.3.9-2 that fix this bug.  I am waiting for my 
sponsor to review and upload it.


Kind regards

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[Jose R R]

On Tue, Oct 25, 2016 at 3:46 PM, Konstantin Demin <rockdri...@gmail.com> wrote:
>>> But does this generate the same output as without -enable-default-pie?
>>> Some parts of the kernel do use -fpic or -fPIC. Which directive prevails?
>
> If you call gcc with "-O3 -O0 -O1", only "-O1" option is make sence.
> See attachments from recent build log (roughly speaking, Linux 4.8.4,
> "make V=1" with gcc 6.2.0-9, but actually it's heavily customized
> Debian src:linux with 3rd pty patches and custom configs).
>
>>> I'm currently looking for correct way to do this trick.
> Patch is available and (at least) works for me on amd64 and i386, ref msg #51
Thanks!!!

I just built my Aufs4/Reiser4-patched kernel 4.7.10 from pristine
source at kernel.org as:

time KCFLAGS="-fno-PIC -fno-PIE" fakeroot make-kpkg
--append-to-version=.huitzilopochtli --stem gcc6-aufs4+reiser4m -j8
--initrd kernel_image kernel_headers

Otherwise I was getting error:
[...]
  UPD include/generated/uapi/linux/version.h
  CHK include/generated/utsrelease.h
  UPD include/generated/utsrelease.h
  CC  kernel/bounds.s
kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
 /*

make[3]: *** [kernel/bounds.s] Error 1
Kbuild:45: recipe for target 'kernel/bounds.s' failed
make[2]: *** [prepare0] Error 2
Makefile:1033: recipe for target 'prepare0' failed
make[2]: Leaving directory '/usr/src/build/tekitl-4.7.10/build/linux-4.7.10'
make[1]: *** [debian/stamp/conf/kernel-conf] Error 2
debian/ruleset/targets/common.mk:194: recipe for target
'debian/stamp/conf/kernel-conf' failed
make[1]: Leaving directory '/usr/src/build/tekitl-4.7.10/build/linux-4.7.10'
make: *** [debian/stamp/conf/minimal_debian] Error 2
/usr/share/kernel-package/ruleset/minimal.mk:93: recipe for target
'debian/stamp/conf/minimal_debian' failed


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#842382: installation-reports: Reiser4-enabled d-i/Linux tzitzimecitlalli 4.7.0-1+reiser4.0.1-amd64 #1 SMP Debian 4.7.8-1+reiser4.0.1 (2016-10-26) x86_64 GNU/Linux successfully installed on Hewlett

[Jose R Rodriguez]

Package: installation-reports
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: USB/netboot
Image version: https://sourceforge.net/projects/debian-reiser4/ 
Debian-Installer for Reiser4
Date: Oct 27, 2016, 18:55 PST

Machine: Pavilion dv6-6c53cl 16384MB DDR3 SDRAM
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs  32765649248   3267316   1% /run
/dev/sda2  reiser4   20432028 6562944  13869084  33% /
tmpfs  tmpfs  81914041024   8190380   1% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs  8191404   0   8191404   0% /sys/fs/cgroup
/dev/sda9  ext2136269  119362  9637  93% /boot
tmpfs  tmpfs  1638284  28   1638256   1% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems: Smooth overall installation of Jessie on Reiser4 root fs.

Mainly wanted to test Reiser4-enabled custom kernel -- patched against 'Dirty 
COW' -- integrated
into the Reiser4 custom netboot debian-installer (d-i) for a non-expert. 
d-i downloaded Kernel and reiser4progs from Metztli.it and newer linux-base 
from debian bp.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20161026-10:50"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux tzitzimecitlalli 4.7.0-1+reiser4.0.1-amd64 #1 SMP Debian 
4.7.8-1+reiser4.0.1 (2016-10-26) x86_64 Xonecuiltzin
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0104] (rev 09)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd 
Generation Core Processor Family Integrated Graphics Controller [8086:0116] 
(rev 09)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 
Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658]
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658]
lspci -knn: Kernel driver in use: ehci-pci

Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA

[Jose M Calhariz]

On 24/10/16 03:30, Ben Hutchings wrote:
> On Sun, 2016-10-16 at 21:22 +0100, Jose M Calhariz wrote:
>> Package: src:linux
>> Version: 4.8~rc8-1~exp1
>> Severity: important
>>
>> Dear Maintainer,
>>
>>* What led up to the situation?
>>
>> Using a very recent Debian kernel 4.7 or 4.8.  The vanilla 4.7.0 from
>> kernel.org works.  I simply boot the laptop.  When the X11 is up and
>> ready to input the user name, if I press any key it will shutdown.
> [...]
>
> Is that a clean shutdown (services stopped, filesystems unmounted) or a
> dirty shutdown (shuts off almost immediately, fsck reports an error on
> the next boot)?
>
> What happens if you press a key earlier than that?
>
> Ben.
>
Yes, it seams to be a clean shutdown.  User programs killed, services
shutdown, nothing logged.


If I press a key earlier, it is just ignored, as expected.


Kind regards

Jose M Calhariz





signature.asc
Description: OpenPGP digital signature

Bug#834534: librep: please make the build reproducible

[Jose M Calhariz]

On 17/10/16 21:06, Chris Lamb wrote:
> Jose M Calhariz wrote:
>
>> And collab-maintainer?
> I would prefer .dsc if that's not too much trouble for you...? 
>
>
> Regards,
>
Can you download from here? 

http://blog.calhariz.com/public/sft/sawfish/librep_0.92.6-1.dsc


Kind regards

Jose M Calhariz





signature.asc
Description: OpenPGP digital signature

Bug#834534: librep: please make the build reproducible

[Jose M Calhariz]

No worries, I will find out a solution. 

On October 17, 2016 9:06:49 PM GMT+01:00, Chris Lamb <la...@debian.org> wrote:
>Jose M Calhariz wrote:
>
>> And collab-maintainer?
>
>I would prefer .dsc if that's not too much trouble for you...? 
>
>
>Regards,
>
>-- 
>  ,''`.
> : :'  : Chris Lamb
> `. `'`  la...@debian.org / chris-lamb.co.uk
>   `-

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#834534: librep: please make the build reproducible

[Jose M Calhariz]

On 17/10/16 19:08, Chris Lamb wrote:
> Jose M Calhariz wrote:
>
>> I need at least 2 weeks for finding a sponsor and upload it.
> I am happy to sponsor packages given HTTP-accessible links to .dsc
> files. :)

And collab-maintainer?

https://anonscm.debian.org/git/collab-maint/librep.git

It is not tagged and signed so it can be reviewed and corrected.

>
> Regards,
>
Kind regards

Jose M Calhariz





signature.asc
Description: OpenPGP digital signature

Bug#834534: librep: please make the build reproducible

[Jose M Calhariz]

On 17/10/16 10:54, Chris Lamb wrote:
> Dear Maintainer,
>
>> Source: librep
>> Version: 0.90.2-1.1
>> Tags: patch
> There hasn't seem to be any update on this bug in 61 days, in which
> time the Reproducible Builds effort has come on a long way. :)
>
> Would you consider applying this patch and uploading?
>
>
> Regards,
>
Sorry, I have applied the patch, but forget to ping my sponsor and
forgot about the

pending changes in sawfish and its depends, librep included.  I need at
least 2 weeks

for finding a sponsor and upload it.


Kind regards

Jose M Calhariz





signature.asc
Description: OpenPGP digital signature

Bug#840165: fcl bug

[Jose Luis Rivero]

On 17/10/16 19:17, Jochen Sprickerhof wrote:
> * Leopold Palomo-Avellaneda <l...@alaxarxa.net> [2016-10-17 11:31]:
>> Please Jochen, could you upload it?
> 
> Will do later.
> 
> @Jose: Can you comment why you added it in
> 
> https://anonscm.debian.org/cgit/debian-science/packages/fcl.git/commit/?id=2b59789404c96e4fbc6877ef2db0adccbeb8d97b
> 

I remember to see the option while working on enabling the octomap
support and enable expecting the build system to do what the option says
(strictly enabling SSE). I did not look into the implementation sorry.

+1 on removing it.

-- 
Jose Luis Rivero <jriv...@osrfoundation.org>



signature.asc
Description: OpenPGP digital signature

Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA

[Jose M Calhariz]

Package: src:linux
Version: 4.8~rc8-1~exp1
Severity: important

Dear Maintainer,

   * What led up to the situation?

Using a very recent Debian kernel 4.7 or 4.8.  The vanilla 4.7.0 from
kernel.org works.  I simply boot the laptop.  When the X11 is up and
ready to input the user name, if I press any key it will shutdown.  I
found no message in /var/log/kernel.log that explains the problem.


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

For reporting this bug I am connecting by SSH to the laptop over a
USB/Ethernet adaptor. 

What measures can I do to gather more debugging information?

Kind regards
Jose M Calhariz



-- Package-specific info:
** Version:
Linux version 4.8.0-rc8-amd64 (debian-ker...@lists.debian.org) (gcc
version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.8~rc8-1~exp1
(2016-09-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.8.0-rc8-amd64
root=UUID=577ff77a-2aa2-4c43-9c83-91e107b674c2 ro printk.time=n
initcall_debug no_console_suspend

** Tainted: E (8192)
 * Unsigned module has been loaded.

** Kernel log:
[6.100201] initcall init_fat_fs+0x0/0xfd0 [fat] returned 0 after
46151 usecs
[6.100962] initcall ghash_pclmulqdqni_mod_init+0x0/0x1000
[ghash_clmulni_intel] returned 0 after 17143 usecs
[6.102575] calling  init_vfat_fs+0x0/0x1000 [vfat] @ 303
[6.102588] initcall init_vfat_fs+0x0/0x1000 [vfat] returned 0 after
5 usecs
[6.104151] calling  crc32_pclmul_mod_init+0x0/0x1000 [crc32_pclmul]
@ 257
[6.107983] initcall crc32_pclmul_mod_init+0x0/0x1000 [crc32_pclmul]
returned 0 after 3726 usecs
[6.111215] calling  crct10dif_intel_mod_init+0x0/0x1000
[crct10dif_pclmul] @ 267
[6.124523] calling  init_nls_cp437+0x0/0x1000 [nls_cp437] @ 316
[6.124531] initcall init_nls_cp437+0x0/0x1000 [nls_cp437] returned 0
after 0 usecs
[6.135566] initcall crct10dif_intel_mod_init+0x0/0x1000
[crct10dif_pclmul] returned 0 after 23765 usecs
[6.137107] calling  evdev_init+0x0/0x1000 [evdev] @ 261
[6.139222] initcall evdev_init+0x0/0x1000 [evdev] returned 0 after
2050 usecs
[6.143220] calling  init_nls_ascii+0x0/0x1000 [nls_ascii] @ 320
[6.143228] initcall init_nls_ascii+0x0/0x1000 [nls_ascii] returned 0
after 0 usecs
[6.171881] calling  vmx_init+0x0/0x435 [kvm_intel] @ 266
[6.179360] calling  asus_wmi_init+0x0/0x1000 [asus_wmi] @ 260
[6.179367] asus_wmi: ASUS WMI generic driver loaded
[6.179386] initcall asus_wmi_init+0x0/0x1000 [asus_wmi] returned 0
after 16 usecs
[6.181794] calling  asus_nb_wmi_init+0x0/0x1000 [asus_nb_wmi] @ 260
[6.182142] asus_wmi: Initialization: 0x1
[6.182258] asus_wmi: BIOS WMI version: 7.9
[6.182352] asus_wmi: SFUN value: 0x37
[6.185752] input: Asus WMI hotkeys as
/devices/platform/asus-nb-wmi/input/input8
[6.201743] asus_wmi: Number of fans: 1
[6.208232] ath10k_pci :01:00.0: firmware: failed to load
ath10k/pre-cal-pci-:01:00.0.bin (-2)
[6.208254] ath10k_pci :01:00.0: Direct firmware load for
ath10k/pre-cal-pci-:01:00.0.bin failed with error -2
[6.208297] ath10k_pci :01:00.0: firmware: failed to load
ath10k/cal-pci-:01:00.0.bin (-2)
[6.208311] ath10k_pci :01:00.0: Direct firmware load for
ath10k/cal-pci-:01:00.0.bin failed with error -2
[6.211045] initcall asus_nb_wmi_init+0x0/0x1000 [asus_nb_wmi]
returned 0 after 28549 usecs
[6.220335] ath10k_pci :01:00.0: firmware: direct-loading
firmware ath10k/QCA9377/hw1.0/firmware-5.bin
[6.220374] ath10k_pci :01:00.0: qca9377 hw1.0 target 0x0502
chip_id 0x003820ff sub 1a3b:2b31
[6.220388] ath10k_pci :01:00.0: kconfig debug 0 debugfs 0
tracing 0 dfs 0 testmode 0
[6.221359] ath10k_pci :01:00.0: firmware ver WLAN.TF.1.0-00267-1
api 5 features ignore-otp crc32 79cea2c7
[6.223919] calling  iTCO_vendor_init_module+0x0/0x1000
[iTCO_vendor_support] @ 271
[6.223923] iTCO_vendor_support: vendor-support=0
[6.223940] initcall iTCO_vendor_init_module+0x0/0x1000
[iTCO_vendor_support] returned 0 after 12 usecs
[6.225084] calling  iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt] @ 271
[6.225086] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[6.225220] iTCO_wdt: Found a Braswell SoC TCO device (Version=3,
TCOBASE=0x0460)
[6.225553] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[6.225610] initcall iTCO_wdt_init_module+0x0/0x1000 [iTCO_wdt]
returned 0 after 504 usecs
[6.251830] initcall vmx_init+0x0/0x435 [kvm_intel] returned 0 after
78051 usecs
[6.254285] calling  coretemp_init+0x0/0x1000 [coretemp] @ 257
[6.254616] initcall coretemp_init+0x0/0x1000 [coretemp] returned 0
after 314 usecs
[6.256501] calling  powerclamp_init+0x0/0x1000 [intel_powerclamp] @ 267
[6.256619] initcall powerclamp_init+0x0/0x1000 [intel_powerclamp]
returned 0 after 105 usecs
[6.257469] calling  acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq] @ 257
[6.257479] initcall acpi_cpufreq_init+0x0/0x1000 [acpi_cpufreq

Bug#840507: zeroc-icee: Remove obsolte zeroc-icee package

[Jose]

Source: zeroc-icee
Severity: normal

Dear Maintainer,

This version of zeroc-icee included is obsolete and not
longer supported by upstream, all Ice developers must
use zeroc-ice that provides the latest stable version of
Ice and is supported by upstream.

zeroc-icee-translators must be also removed and that was
just used by zeroc-icee and is part of the obsolete IceE
upstream package.


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

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

Bug#839847: ice-builder-gradle: FTBFS: Could not generate a proxy class for class org.gradle.api.internal.project.DefaultProject

[Jose Gutierrez de la Concha]

Hi Chris,

Thanks for reporting this issue, I have investigate the issue and seems a
problem with
groovy-2.4.7-2 upgrade there are a number of missing classes from
groovy-all-2.4.7.jar
used by gradle, groovy.util.AntBuilder being one of them.


I have reported the bug to groovy package
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839896


On Wed, Oct 5, 2016 at 7:56 PM, Chris Lamb  wrote:

> Source: ice-builder-gradle
> Version: 1.3.13-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,
>
> ice-builder-gradle fails to build from source in unstable/amd64:
>
>   [..]
>
>   Adding debian:IdenTrust_Commercial_Root_CA_1.pem
>   Adding debian:IdenTrust_Public_Sector_Root_CA_1.pem
>   Adding debian:Izenpe.com.pem
>   Adding debian:Juur-SK.pem
>   Adding debian:Microsec_e-Szigno_Root_CA.pem
>   Adding debian:Microsec_e-Szigno_Root_CA_2009.pem
>   Adding debian:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem
>   Adding debian:NetLock_Business_=Class_B=_Root.pem
>   Adding debian:NetLock_Express_=Class_C=_Root.pem
>   Adding debian:NetLock_Notary_=Class_A=_Root.pem
>   Adding debian:NetLock_Qualified_=Class_QA=_Root.pem
>   Adding debian:Network_Solutions_Certificate_Authority.pem
>   Adding debian:OISTE_WISeKey_Global_Root_GA_CA.pem
>   Adding debian:OISTE_WISeKey_Global_Root_GB_CA.pem
>   Adding debian:PSCProcert.pem
>   Adding debian:QuoVadis_Root_CA.pem
>   Adding debian:QuoVadis_Root_CA_1_G3.pem
>   Adding debian:QuoVadis_Root_CA_2.pem
>   Adding debian:QuoVadis_Root_CA_2_G3.pem
>   Adding debian:QuoVadis_Root_CA_3.pem
>   Adding debian:QuoVadis_Root_CA_3_G3.pem
>   Adding debian:RSA_Security_2048_v3.pem
>   Adding debian:Root_CA_Generalitat_Valenciana.pem
>   Adding debian:S-TRUST_Authentication_and_Encryption_Root_CA_2005_PN.pem
>   Adding debian:S-TRUST_Universal_Root_CA.pem
>   Adding debian:SecureSign_RootCA11.pem
>   Adding debian:SecureTrust_CA.pem
>   Adding debian:Secure_Global_CA.pem
>   Adding debian:Security_Communication_EV_RootCA1.pem
>   Adding debian:Security_Communication_RootCA2.pem
>   Adding debian:Security_Communication_Root_CA.pem
>   Adding debian:Sonera_Class_1_Root_CA.pem
>   Adding debian:Sonera_Class_2_Root_CA.pem
>   Adding debian:Staat_der_Nederlanden_EV_Root_CA.pem
>   Adding debian:Staat_der_Nederlanden_Root_CA.pem
>   Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
>   Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
>   Adding debian:Starfield_Class_2_CA.pem
>   Adding debian:Starfield_Root_Certificate_Authority_-_G2.pem
>   Adding debian:Starfield_Services_Root_Certificate_Authority_-_G2.pem
>   Adding debian:StartCom_Certification_Authority.pem
>   Adding debian:StartCom_Certification_Authority_2.pem
>   Adding debian:StartCom_Certification_Authority_G2.pem
>   Adding debian:SwissSign_Gold_CA_-_G2.pem
>   Adding debian:SwissSign_Platinum_CA_-_G2.pem
>   Adding debian:SwissSign_Silver_CA_-_G2.pem
>   Adding debian:Swisscom_Root_CA_1.pem
>   Adding debian:Swisscom_Root_CA_2.pem
>   Adding debian:Swisscom_Root_EV_CA_2.pem
>   Adding debian:T-TeleSec_GlobalRoot_Class_2.pem
>   Adding debian:T-TeleSec_GlobalRoot_Class_3.pem
>   Adding debian:TC_TrustCenter_Class_3_CA_II.pem
>   Adding debian:TURKTRUST_Certificate_Services_Provider_Root_2007.pem
>   Adding debian:TWCA_Global_Root_CA.pem
>   Adding debian:TWCA_Root_Certification_Authority.pem
>   Adding debian:Taiwan_GRCA.pem
>   Adding debian:TeliaSonera_Root_CA_v1.pem
>   Adding debian:Trustis_FPS_Root_CA.pem
>   Adding debian:TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-
> _Sürüm_3.pem
>   Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem
>   Adding debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H6.pem
>   Adding debian:USERTrust_ECC_Certification_Authority.pem
>   Adding debian:USERTrust_RSA_Certification_Authority.pem
>   Adding debian:UTN_USERFirst_Email_Root_CA.pem
>   Adding debian:UTN_USERFirst_Hardware_Root_CA.pem
>   Adding debian:VeriSign_Class_3_Public_Primary_Certification_
> Authority_-_G4.pem
>   Adding debian:VeriSign_Class_3_Public_Primary_Certification_
> Authority_-_G5.pem
>   Adding debian:VeriSign_Universal_Root_Certification_Authority.pem
>   Adding debian:Verisign_Class_1_Public_Primary_Certification_
> Authority.pem
>   Adding debian:Verisign_Class_1_Public_Primary_Certification_
> Authority_-_G2.pem
>   Adding debian:Verisign_Class_1_Public_Primary_Certification_
> Authority_-_G3.pem
>   Adding debian:Verisign_Class_2_Public_Primary_Certification_
> Authority_-_G2.pem
>   Adding debian:Verisign_Class_2_Public_Primary_Certification_
> Authority_-_G3.pem
>   Adding debian:Verisign_Class_3_Public_Primary_Certification_
> Authority.pem
>   Adding debian:Verisign_Class_3_Public_Primary_Certification_
> Authority_-_G2.pem
>   Adding debian:Verisign_Class_3_Public_Primary_Certification_
> 

Bug#839896: groovy.util.AntBuilder.class missing from /usr/share/groovy/embeddable/groovy-all-2.4.7.jar

[Jose]

Package: groovy
Version: 2.4.7-2
Severity: important

Dear Maintainer,


With groovy 2.4.7-2 the groovy.util.AntBuilder.class is not longer included 
with 
groovy-all, that is causing problems building other packages that use gradle and
depend on this class

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


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

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

Versions of packages groovy depends on:
ii  antlr2.7.7+dfsg-7
ii  default-jre-headless [java6-runtime-headless]2:1.8-57
ii  ivy  2.4.0-3
ii  junit4   4.12-4
ii  libasm-java  5.1-1
ii  libbsf-java  1:2.4.0-5
ii  libcommons-cli-java  1.3.1-3
ii  libcommons-logging-java  1.2-1
ii  libjansi-java1.4-3
ii  libjline2-java   2.11-4
ii  libqdox-java 1.12.1-2
ii  libservlet3.1-java   8.0.37-1
ii  libxstream-java  1.4.9-1
ii  openjdk-8-jre-headless [java6-runtime-headless]  8u102-b14.1-2

Versions of packages groovy recommends:
ii  ant   1.9.7-3
ii  ant-optional  1.9.7-3
ii  libgpars-groovy-java  1.2.1-6
ii  libjcommander-java1.48-1
ii  testng6.9.12-1

Versions of packages groovy suggests:
pn  groovy-doc  

-- no debconf information

Bug#839603: amanda: The /usr/lib/amanda/amcheck-device command SIGSEGV when called by amcheck

[Jose M Calhariz]

Hi, it seems a perl upgrade break Amanda.   While I work on problem you may try 
to downgrade perl. 

Kind regards 
Jose M Calhariz 


On October 2, 2016 8:01:23 PM GMT+01:00, SZALAY Attila <s...@ubainba.hu> wrote:
>Package: amanda-server
>Version: 1:3.3.9-1
>Severity: normal
>File: amanda
>
>Dear Maintainer,
>
>After I upgraded my host this week (I do not know the exact date) I
>started
>to receive an alert message from amanda with the following subject:
>"Daily AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE"
>Which told me, that:
>"amcheck-device terminated with signal 11"
>
>Also, I was able to reproduce the issue with running the amcheck by
>hand
>with the following command line:
>"su -s /bin/bash -l -c "ulimit -c unlimited; /usr/sbin/amcheck -m
>Daily" backup"
>
>Seemingly the daily backup job is running without success (this is
>while it
>is just normal), but not checked throroughly.
>
>The strace show the following:
>29840 stat("/backup/amanda/daily/vtapes/drive0/data//0.MyData08",
>{st_mode=S_IFREG|0600, st_size=32768, ...}) = 0
>29840 getdents(5, /* 0 entries */, 32768) = 0
>29840 close(5)  = 0
>29840 lseek(4, 0, SEEK_SET) = 0
>29840 write(4, "$STATE = {\n   'drives' => {\n 
>'/backup/amanda/daily/vtapes/drive0' => {\n
>'pid' => 29840\n   
>}\n   },\n   'meta' => undef\n
>};\n", 317) = 317
>29840 close(4)  = 0
>29840 write(2, "found in slot 8:", 16)  = 16
>29840 write(2, " volume 'MyData08'\n", 19) = 19
>29840 write(10, "Sun Oct  2 20:33:32 2016: thd-0x1a4f200:
>amcheck-device: Amanda::Taper::Scan::traditional result: 'MyData08' on
>file:/backup/amanda/daily/vtapes/drive0 slot 8, mode 2\n", 167) = 167
>29840 lstat("/backup/amanda/daily/vtapes/drive0/data",
>{st_mode=S_IFLNK|0777, st_size=8, ...}) = 0
>29840 unlink("/backup/amanda/daily/vtapes/drive0/data") = 0
>29840 rmdir("/backup/amanda/daily/vtapes/drive0") = 0
>29840 open("/etc/amanda/Daily/changer", O_RDWR|O_CREAT, 0666) = 4
>29840 fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
>l_len=0}) = 0
>29840 fstat(4, {st_mode=S_IFREG|0600, st_size=317, ...}) = 0
>29840 read(4, "$STATE = {\n   'drives' => {\n  
>'/backup/amanda/daily/vtapes/drive0' => {\n
>'pid' => 29840\n   
>}\n   },\n   'meta' => undef\n
>};\n", 317) = 317
>29840 lseek(4, 0, SEEK_SET) = 0
>29840 write(4, "$STATE = {\n   'drives' => {\n 
>'/backup/amanda/daily/vtapes/drive0' => {}\n   },\n
>  'meta' => undef\n };\n", 169) = 169
>29840 ftruncate(4, 169) = 0
>29840 close(4)  = 0
>29840 write(3, "\1\0\0\0\0\0\0\0", 8)   = 8
>29840 futex(0x25370c0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
>29840 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x10}
>---
>
>And the dbg output is (I cannot find debug symbols neither for perl nor
>amanda):
>Reading symbols from /usr/bin/perl...(no debugging symbols
>found)...done.
>
>warning: core file may not match specified executable file.
>[New LWP 29840]
>[Thread debugging using libthread_db enabled]
>Using host libthread_db library
>"/lib/x86_64-linux-gnu/libthread_db.so.1".
>Core was generated by `/usr/bin/perl /usr/lib/amanda/amcheck-device
>Daily'.
>Program terminated with signal SIGSEGV, Segmentation fault.
>#0  0x7f24ced6e1fb in ?? () from
>/usr/lib/x86_64-linux-gnu/amanda/perl/auto/Amanda/MainLoop/libMainLoop.so
>(gdb) bt full
>#0  0x7f24ced6e1fb in  () at
>/usr/lib/x86_64-linux-gnu/amanda/perl/auto/Amanda/MainLoop/libMainLoop.so
>#1  0x7f24d4975103 in g_timeout_dispatch (source=0x2311c10,
>callback=, user_data=) at
>././glib/gmain.c:4672
>timeout_source = 0x2311c10
>again = 
>#2  0x7f24d497468a in g_main_context_dispatch (context=0x25370b0)
>at ././glib/gmain.c:3201
>dispatch = 0x7f24d49750f0 
>prev_source = 0x0
>was_in_call = 0
>user_data = 0x25d3af0
>callback = 0x7f24ced6e090
>cb_funcs = 
>cb_data = 0x2169e90
>need_destroy = 
>source = 0x2311c10
>current = 0x2309b80
>i = 0
>#3  0x7f24d497468a in g_main_context_dispatch
>(context=context@entr

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

[Jose Gutierrez de la Concha]

Hi Santiago,

We will upload a new version that solve the issue

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


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

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

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


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

> Package: src:zeroc-ice
> Version: 3.6.2-stretch-51-gba6baa6-2
> Severity: serious
>
> Dear maintainer:
>
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed.
>
> 
> 
> [...]
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file '/<>/java/build.gradle' line: 16
>
> * What went wrong:
> A problem occurred evaluating root project 'java'.
> > Could not resolve all dependencies for configuration 'classpath'.
> 
> 
>
> I'm attaching two different build logs.
>
> Sorry, I have not tried "dpkg-buildpackage" alone, but this package has
> separate override_dh_auto_build-arch and override_dh_auto_build-indep
> targets, so this could be "dpkg-buildpackage -A" specific indeed.
>
> Thanks.




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

Bug#820873: amule: jose

[jose]

Package: amule
Version: 2.4.0~git20151120.0023527bc2-1+b3
Followup-For: Bug #820873

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? Nothing. I left amule working and sometimes, 
not always crash and I find a error message instead
   
   The error message is:
ASSERT INFO:
../../src/kademlia/net/KademliaUDPListener.cpp(527): assert "contactVersion >= 
2" failed in Process2HelloRequest().

BACKTRACE:
[1] wxOnAssert(char const*, int, char const*, char const*, char const*)
[2] CryptoPP::IteratedHash, 64u, 
CryptoPP::HashTransformation>::DataBuf()
[3] CryptoPP::IteratedHash, 64u, 
CryptoPP::HashTransformation>::DataBuf()
[4] std::vector 
>::operator=(std::vector > const&)
[5] non-virtual thunk to 
CryptoPP::PK_FinalTemplate, CryptoPP::RSA, 
CryptoPP::PKCS1v15_SignatureMessageEncodingMethod, CryptoPP::SHA1> > 
>::~PK_FinalTemplate()
[6] std::vector 
>::operator=(std::vector > const&)
[7] non-virtual thunk to 
CryptoPP::PK_FinalTemplate, CryptoPP::RSA, 
CryptoPP::PKCS1v15_SignatureMessageEncodingMethod, CryptoPP::SHA1> > 
>::~PK_FinalTemplate()
[8] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, 
wxEvent&) const
[9] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
[10] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[11] wxEvtHandler::TryHereOnly(wxEvent&)
[12] wxEvtHandler::ProcessEventLocally(wxEvent&)
[13] wxEvtHandler::ProcessEvent(wxEvent&)
[14] wxEvtHandler::ProcessPendingEvents()
[15] wxAppConsoleBase::ProcessPendingEvents()
[16] wxApp::DoIdle()
[17] g_main_context_dispatch
[18] g_main_loop_run
[19] gtk_main
[20] wxGUIEventLoop::DoRun()
[21] wxEventLoopBase::Run()
[22] wxAppConsoleBase::MainLoop()
[23] wxEntry(int&, wchar_t**)
[24] __libc_start_main





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

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

Versions of packages amule depends on:
ii  amule-common   2.4.0~git20151120.0023527bc2-1
ii  libboost-system1.61.0  1.61.0+dfsg-2.1
ii  libc6  2.23-5
ii  libcrypto++6   5.6.3-8
ii  libgcc11:6.1.1-11
ii  libgeoip1  1.6.9-3
ii  libstdc++6 6.1.1-11
ii  libupnp6   1:1.6.19+git20160116-1
ii  libwxbase3.0-0v5   3.0.2+dfsg-2
ii  libwxgtk3.0-0v53.0.2+dfsg-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages amule recommends:
ii  amule-utils  2.4.0~git20151120.0023527bc2-1+b3
ii  unzip6.0-20

Versions of packages amule suggests:
pn  amule-utils-gui  

-- no debconf information

Bug#838345: installation-reports: Successful Reiser4 Jessie 4.7.0-1+reiser4.0.1-amd64_4.7.4-1 kernel on VirtualBox 5.1.6

[Jose R Rodriguez]

Package: installation-reports
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: netboot image
Image version: https://sourceforge.net/projects/debian-reiser4/
Date: September 19, 20:35:31 PDT

Machine: VirtualBox 5.1.6
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs   4105045916404588   2% /run
/dev/sda5  reiser49822436 3798668   6023768  39% /
tmpfs  tmpfs  10262601108   1025152   1% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs  1026260   0   1026260   0% /sys/fs/cgroup
/dev/sda1  ext2140805   55482 78053  42% /boot
tmpfs  tmpfs   205252   8205244   1% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Smooth Reiser4-enabled Jessie Debian-Installer in non-expert mode.
elvis-tiny has been integrated into this d-i -- since I found nano awful;
I wish I had elvis-tiny available as I was intially working on Reiser4 hack.

SSL-enabled Busybox in d-i automatically downloaded Reiser4-patched Linux 
kernel 4.7.0-1
-- modified for Jessie's GCC 4.9 -- as well as reiser4progs 1.1.0-1.x built for 
Debian Jessie AMD64. 

d-i also fetches linux-base from backports to satisfy recent kernel 
requirements.
Overall flawless installation for a non expert.

Node: payinalcitlalli
http://www.enlightenment.org/ss/e-57e0df154a3995.47690147.jpg

(as usual Xonecuiltzin is d-i BusyBox environment.)
-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20160919-14:55"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux payinalcitlalli 4.7.0-1+reiser4.0.1-amd64 #1 SMP Debian 
4.7.4-1+reiser4.0.1 (2016-09-19) x86_64 Xonecuiltzin
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 
IDE [8086:7111] (rev 01)
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung 
GmbH VirtualBox Graphics Adapter [80ee:beef]
lspci -knn: 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM 
Gigabit Ethernet Controller [8086:100e] (rev 02)
lspci -knn: Subsystem: Intel Corporation Device [8086:001e]
lspci -knn: Kernel driver in use: e1000
lspci -knn: 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH 
VirtualBox Guest Service [80ee:cafe]
lspci -knn: 00:05.0 Multimedia audio controller [0401]: Intel Corporation 
82801AA AC'97 Audio Controller [8086:2415] (rev 01)
lspci -knn: Subsystem: Dell Device [1028:0177]
lspci -knn: 00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB 
[106b:003f]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 08)
lspci -knn: 00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM 
(ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02)
lspci -knn: Kernel driver in use: ahci
usb-list: 
usb-list: Bus 01 Device 01: OHCI PCI host controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.7.0-1+reiser4.0.1-amd64 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 01 Device 02: USB Tablet [80ee:0021]
usb-list:Level 01 Parent 01 Port 00  Class 

Bug#836215: RFS: phalanx/25-1 [ITA]

[Jose G. López]

On Wed, 14 Sep 2016 09:55:36 + (UTC)
Gianfranco Costamagna  wrote:

> you might even consider fixing the actual RC bug without a new upstream 
> release,
> let the package migrate, and upload the new version (crippled) in experimental
> or later in unstable.

Hi Gianfranco,

All right, I prefer to fix and improve the actual version and not trim
useful features that I as a user, would like to have.
I've uploaded the new debian revision to mentors[0]. To keep the
previous work I have created a new branch (debian/sid) where I
cherry-picked changes.

Thanks for your help and suggestions!

[0]https://mentors.debian.net/package/phalanx
[1]https://gitlab.com/deb-pkg/phalanx/tree/debian/sid


pgpxZUMdO1hYd.pgp
Description: PGP signature

Bug#836215: RFS: phalanx/25-1 [ITA]

[Jose G. López]

Hi Gianfranco,

Thanks for reviwing! I must say I've addressed most of your points but
testing the new version (25), I've found that it doesn't work as
expected in Scid. Scid has a feature to play versus Phalanx (tactical
game) but it needs a special version. The package in sid works well
while new version only works if you choose the option to play
a specific opening.

Apart from that, the engine works well both in scid
(analyzing) and xboard (analyzing and playing with). I've tried to
figure out the changes done to phalanx-scid engine but I don't come by
with a solution.

So don't know if it's better to fix and improve the version in
sid (22+d051004) while asking Scid upstream to import the new version
of Phalanx and knowing what changes need to be tweaked.

What do you think?

Regards,


pgpIZCkhTFMhg.pgp
Description: PGP signature

Bug#837555: installation-reports: Successful Sid d-i Reiser4-enabled 4.7.0-1+reiser4.0.1-amd64 kernel onto root reiser4 fs HP dv6-6c53cl

[Jose R Rodriguez]

Package: installation-reports
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: netboot/USB stick
Image version: https://metztli.it/readOnlyEphemeral/Mictlanteuccitlalli.iso 
https://metztli.it/readOnlyEphemeral/Mictlanteuccitlalli.SHA256SUM
Date: Sep 11, 2016 ~ 17:14

Machine: HP Pavilion dv6-6c53cl
Partitions:
jose@mictlantecuhtli:~$ df -Tl
Filesystem Type 1K-blocks Used Available Use% Mounted on
udev   devtmpfs   81814640   8181464   0% /dev
tmpfs  tmpfs  1638284 1060   1637224   1% /run
/dev/sda15 reiser4   92435000  7818180  84616820   9% /
tmpfs  tmpfs 51204  5116   1% /run/lock
tmpfs  tmpfs  3862920 7892   3855028   1% /run/shm
/dev/sda9  ext2136269   103081 25918  80% /boot
cgroup tmpfs   12012   0% /sys/fs/cgroup
tmpfs  tmpfs  1638280   20   1638260   1% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems: Installed in 'expert' mode, as I...

Built Reiser4-enabled Unstable (svn) Debian Installer and Reiser4-patched 
kernel from Sid source
specifically for a Debian native Reiser4 partitioning, formating, and 
installation on my
development environment. Given its bleeding edge changing nature, Debian
simply installed flawlessly its Debian Desktop environment.

Only issue is that upon instantiation, d-i did not recognize my command:
preseed/late_command="in-target apt-get install -y sysvinit-core"

as I don't want *that* systemd thingy-magingy with my Enlightenment subsequent 
build. Thus,
had to give the above command myself after first boot.

I have noticed, since a while back, that the GDM3 behaves buggy, i.e.,
CTRL + Alt + fn to get a virtual terminal usually hangs the system; it
could be as a result of not having systemd(?) -- notwithstanding still seems 
GDM3 behaves laggardly.
I usually replace it with XDM -- which works beautifully to instantiate (and 
customize) Enlightenment.

Please note below that since I build my own SSL-enabled BusyBox UDEB for
d-i so that it can fetch its Reiser4 kernel &/or utilities from
metztli.it, I usually customize its option for an 'OS name' as Xonecuiltzin
(which is appended to uname -a output ;-)


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20160911-15:10"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux mictlantecuhtli 4.7.0-1+reiser4.0.1-amd64 #1 SMP Debian 
4.7.2-1+reiser4.0.1 (2016-09-11) x86_64 Xonecuiltzin
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0104] (rev 09)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd 
Generation Core Processor Family Integrated Graphics Controller [8086:0116] 
(rev 09)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 
Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:1658]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)

Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

[Jose R R]

On Sat, Sep 10, 2016 at 6:10 PM, Ben Hutchings <b...@decadent.org.uk> wrote:
> On Sat, 2016-09-10 at 17:37 -0700, Jose R R wrote:
>> On Fri, Sep 9, 2016 at 12:37 PM, Wolfgang Tichy <wtich...@gmail.com>
>> wrote:
>> >
>> > Package: src:linux
>> > Version: 3.16.7-ckt25-2+deb8u3
>> > Severity: critical
>> > Tags: security
>> > Justification: causes serious data loss
>> >
>> > Dear Maintainer,
>> >
>> > when I open a particular word document (it contains images and I
>> > can send it
>> > to you for testing) with libreoffice, all memory and all swap get
>> > used up
>> > within about a minute.
>>
>> You may want to *narrow down* your memory issue by trying out Apache
>> OpenOffice:
>>
>> Download: https://openoffice.org/download/
> [...]
>
> Please, we don't need advocacy for rival software in the Debian BTS.
If ApacheOO solves the user's problem, then it is probably time for Debian
to reevaluate 'rival' alternative.


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

[Jose R R]

> SERR-  Interrupt: pin C routed to IRQ 18
> Region 0: Memory at f1514000 (64-bit, non-prefetchable) [size=256]
> Region 4: I/O ports at efa0 [size=32]
> Kernel driver in use: i801_smbus
>
> 02:00.0 System peripheral [0880]: Ricoh Co Ltd PCIe SDXC/MMC Host Controller 
> [1180:e823] (rev 07) (prog-if 01)
> Subsystem: Lenovo Device [17aa:21f9]
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> SERR-  Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 16
> Region 0: Memory at f0d0 (32-bit, non-prefetchable) [size=256]
> Capabilities: 
> Kernel driver in use: sdhci-pci
>
> 03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6205 
> [Taylor Peak] [8086:0085] (rev 96)
> Subsystem: Intel Corporation Device [8086:c220]
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
> Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> SERR-  Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 45
> Region 0: Memory at f0c0 (64-bit, non-prefetchable) [size=8K]
> Capabilities: 
> Kernel driver in use: iwlwifi
>
>
> ** USB devices:
> Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 005: ID 5986:0266 Acer, Inc
> Bus 003 Device 004: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
> [ThinkPad]
> Bus 003 Device 003: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
> advanced mode)
> Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
>
> -- System Information:
> Debian Release: 8.5
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages linux-image-3.16.0-4-amd64 depends on:
> ii  debconf [debconf-2.0]   1.5.56
> ii  initramfs-tools [linux-initramfs-tool]  0.120+deb8u2
> ii  kmod18-3
> ii  linux-base  3.5
> ii  module-init-tools   18-3
>
> Versions of packages linux-image-3.16.0-4-amd64 recommends:
> ii  firmware-linux-free  3.3
> ii  irqbalance   1.0.6-3
>
> Versions of packages linux-image-3.16.0-4-amd64 suggests:
> pn  debian-kernel-handbook  
> ii  extlinux3:6.03+dfsg-5+deb8u1
> ii  grub-pc 2.02~beta2-22+deb8u1
> pn  linux-doc-3.16  
>
> Versions of packages linux-image-3.16.0-4-amd64 is related to:
> pn  firmware-atheros
> pn  firmware-bnx2   
> pn  firmware-bnx2x  
> ii  firmware-brcm80211  0.43
> pn  firmware-intelwimax 
> pn  firmware-ipw2x00
> pn  firmware-ivtv   
> ii  firmware-iwlwifi0.43
> pn  firmware-libertas   
> ii  firmware-linux  0.43
> ii  firmware-linux-nonfree  0.43
> pn  firmware-myricom
> pn  firmware-netxen 
> pn  firmware-qlogic 
> pn  firmware-ralink 
> pn  firmware-realtek
> pn  xen-hypervisor  
>
> -- debconf information:
>   linux-image-3.16.0-4-amd64/postinst/depmod-error-initrd-3.16.0-4-amd64: 
> false
>   linux-image-3.16.0-4-amd64/postinst/mips-initrd-3.16.0-4-amd64:
>   linux-image-3.16.0-4-amd64/prerm/removing-running-kernel-3.16.0-4-amd64: 
> true
>

Best professional Regards.


-- 
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#836215: RFS: phalanx/25-1 [ITA]

[Jose G. Lopez]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "phalanx":

* Package name: phalanx
  Version : 25-1
  Upstream Author : Dusan Dobes < dusa...@users.sf.net>
* URL : https://sourceforge.net/projects/phalanx/
* License : GPL v2
  Section : games

It builds those binary packages:

  phalanx - Chess playing program

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/phalanx

Alternatively, one can download the package with dget using this
command:

  dget -x https://mentors.debian.net/debian/pool/main/p/phalanx/phalanx_25-1.dsc

It was removed from testing due to an FTBFS with GCC 6 (bug 811584).
Package development is on the following repo:

https://gitlab.com/deb-pkg/phalanx

Changes since the last upload:

phalanx (25-1) unstable; urgency=medium

  * New upstream version.
  * Set myself as Maintainer. (Closes: #835309)
  * New version builds with GCC 6. (Closes: #811584)
  * debian/compat: Upgrade to version 9.
  * debian/config: Fix lintian report 'maintainer-script-without-set-e'.
  * debian/control:
- Bump to Standards-Version 3.9.8. No changes required.
- Add Vcs-* fields to show where development is done.
  * debian/copyright: Update and change Format tag to the accepted one.
  * debian/install: Adjust destination files.
  * debian/patches:
- 03_makefile_DEFINES.diff: Refresh and renamed it to
01_makefile.patch
- 04_PG_setboard_command.diff: Remove, applied upstream.
- 10_hardening-string-literal_search.diff,
  12_hardening-string-literal_io.diff,
  14_hardening-string-literal_book.diff,
  16_hardening-pointer-sign_bcreate: Remove, not needed anymore.
- 16_hardening-unused-but-set_endgame,
  17_bcreate,
  20_fix_linker_problem, 
  25_arch_compiler-flags: Not applicable
  * debian/po:
- pt_BR.po: New, thanks to Adriano Rafael Gomes. (Closes: #811526)
- ca.po: Update to remove fuzzy translations.
  * debian/rules:
- Add hardening flags.
- Add --parallel option to debhelper.
- Add override_dh_auto_install to overwrite install dir.

Regards,


pgplAZjlJndg7.pgp
Description: PGP signature

Bug#835734: Bug#835930 kido: missing link libraries

[Jose Luis Rivero]

Hello Gianfranco:

On 31/08/16 08:48, Gianfranco Costamagna wrote:
> Hi Jose, are you aware of your RC bugs?
> 

I was aware of my RC bugs, yes, and I was working on fixing them.

> in case, please say something about the ongoing work on git, because there is 
> no gain in having somebody else prepare an NMU
> without acking/nacking changes or thanking him.
> 

I did not look into my bugmail during these last days, sorry about that.
Thanks for taking time to work on debugging and fixing the packages.

For the next time, please feel free to use the package git so we could
add another layer to avoid work duplication.

> also, the xml patch looks almost the same as the upstream cherry-pick, and 
> the link patch looks mostly the same as my patch.
> 
> https://github.com/dartsim/dart/commit/2841967fc6628c9aea58c93227b28abdf5dfbcc2.patch
> 
> Can you please consider setting the correct authorship and forward patches 
> upstream?
> 

Sorry for not checking upstream code this time. I have the impression
that you think that I deliberately miss/remove the credit from patches,
that is not the case Gianfranco. I have no reason to do this which goes
against what rules open source. I wrote my patches (both were trivial)
without using upstream changes or notice the existence of your patch.

> (I don't care about authorship, but cherry-picking from upstream,
changing it is considered bad).

Fully agree here, I will remove my custom patches and use the upstream
commit.

> I'll assume good faith from your side, and cancel the NMU.
> (let me know if you need a sponsor)

Thanks for the assumption and the offer, I have rights now to upload
changes to kido.

-- 
Jose Luis Rivero <jriv...@osrfoundation.org>



signature.asc
Description: OpenPGP digital signature

Bug#831792: RFS: scid/1:4.6.4+dfsg1-1

[Jose G. López]

> Hi, can you please have a look at the build failures?
> 
> thanks
> 
> 
> g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -O3 -march=native -fno-rtti -fno-exceptions -std=c++11 
> -pthread -Wall  -DZLIB  -I/usr/include/tk -o src/sortcache.o -c 
> src/sortcache.cpp
> g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -O3 -march=native -fno-rtti -fno-exceptions -std=c++11 
> -pthread -Wall  -DZLIB  -I/usr/include/tk -o src/pgnparse.o -c 
> src/pgnparse.cpp
> g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -O3 -march=native -fno-rtti -fno-exceptions -std=c++11 
> -pthread -Wall  -DZLIB  -I/usr/include/tk -o src/engine.o -c src/engine.cpp
> src/engine.cpp: In member function 'int Engine::Think(MoveList*)':
> src/engine.cpp:1482:51: warning: suggest parentheses around '&&' within '||' 
> [-Wparentheses]
> if (mlist->Size() <= depth || depth >= 5  &&  IsMatingScore (bestScore)) { 
> break; }
> ^
> g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -O3 -march=native -fno-rtti -fno-exceptions -std=c++11 
> -pthread -Wall  -DZLIB  -I/usr/include/tk -o src/sc_base.o -c src/sc_base.cpp
> In file included from src/gfile.h:26:0,
> from src/scidbase.h:25,
> from src/sc_base.cpp:21:
> src/fastgame.h: In static member function 'static squareT 
> FastGame::decodeKing(squareT, byte)':
> src/fastgame.h:436:63: error: narrowing conversion of '-9' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> static const char sqdiff[] = { 0, -9, -8, -7, -1, 1, 7, 8, 9};
> ^
> src/fastgame.h:436:63: error: narrowing conversion of '-8' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> src/fastgame.h:436:63: error: narrowing conversion of '-7' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> src/fastgame.h:436:63: error: narrowing conversion of '-1' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> src/fastgame.h: In static member function 'static squareT 
> FastGame::decodeKnight(squareT, byte)':
> src/fastgame.h:450:91: error: narrowing conversion of '-17' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> static const char sqdiff[] = { 0, -17, -15, -10, -6, 6, 10, 15, 17, 0, 0, 0, 
> 0, 0, 0, 0 };
> ^
> src/fastgame.h:450:91: error: narrowing conversion of '-15' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> src/fastgame.h:450:91: error: narrowing conversion of '-10' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> src/fastgame.h:450:91: error: narrowing conversion of '-6' from 'int' to 
> 'char' inside { } [-Wnarrowing]
> Makefile:334: recipe for target 'src/sc_base.o' failed

Hi Gianfranco,

I've uploaded a new revision to mentors[0] that fixes errors on building for 
some architectures.
Thanks again!

Regards,

[0]https://mentors.debian.net/package/scid


pgpuhQ6VYBCyP.pgp
Description: PGP signature

Bug#831792: RFS: scid/1:4.6.4+dfsg1-1

[Jose G. López]

On Mon, 8 Aug 2016 17:30:38 + (UTC)
Gianfranco Costamagna <locutusofb...@debian.org> wrote:

Hi Gianfranco,

> new review:
> 1) please convert the versioning into 1:4.6.2-1 and remove the NMU syntax.
> and add a "Set myself as Maintainer"

Versioning is 1:4.6.4+dfsg1-1 due to repackaging of upstream sources.
I've seen other examples using this versioning nomenclature.

> 
> 2) missing newline between last entry and your signature
> to make it DFSG compliant.
> -- Jose G. López <josg...@gmail.com>  Mon, 08 Aug 2016 11:23:07 +0200

Fixed.

> 
> 3) copyrights missing
> grep -i copyright . -R |grep -v Fulv |grep -v Shane |grep -vi pascal

Sorry for this. Completed and hope this time is ok.

> 
> after that we should be *really* good, and I'll put the package in deferred, 
> to make it reach unstable in 15 days or so
> (mia team should orphan the package in the meanwhile).
> In case it gets orphaned close the bug with
> "set myself as Maintainer (Closes: #)

Thanks for advertising scid was orphaned. Added myself as adopter ;-)
New revision uploaded to mentors[0], the last one uploaded at
2016-08-26 18:59

I'll have a look to other packages orphaned to see if I can help with
them.

Thanks and regards,

[0]https://mentors.debian.net/package/scid


pgpfwIukjm7pA.pgp
Description: PGP signature

Bug#834481: libfglrx:i386 removes AMD64 libfglrx

[Newton Jose de Moura Junior]

Package: libfglrx
Version: 1:15.12-2~bpo8+2
Severity: important

Dear Maintainer,

When I try install libfglrx:i386 it's removes this AMD64 packages:
fglrx-driver:amd64 
libfglrx:amd64 
libfglrx-amdxvba1:amd64 
libgl1-fglrx-glx:amd64 

As expected if I proceed with instalation After X don't starts after a
reboot.


-- Package-specific info:
Full fglrx package list:
ii  fglrx-atieventsd1:15.12-2~bpo8+2   amd64  events 
daemon for the non-free ATI/AMD RadeonHD display driv
rc  fglrx-control   1:15.12-2~bpo8+2   amd64  control 
panel for the non-free ATI/AMD RadeonHD display driv
ii  fglrx-driver1:15.12-2~bpo8+2   amd64  non-free 
ATI/AMD RadeonHD display driver
ii  fglrx-kernel-4.6.0-0.bpo.1- 1:15.12-2~bpo8+2+4 amd64  FGLRX 
binary kernel module for Linux 4.6.0-0.bpo.1-amd64
ii  fglrx-modules-dkms  1:15.12-2~bpo8+2   amd64  dkms 
module source for the non-free ATI/AMD RadeonHD display
ii  fglrx-source1:15.12-2~bpo8+2   amd64  kernel 
module source for the non-free ATI/AMD RadeonHD displ
ii  glx-alternative-fglrx   0.7.3~bpo8+1   amd64  allows 
the selection of FGLRX as GLX provider
ii  libfglrx:amd64  1:15.12-2~bpo8+2   amd64  non-free 
ATI/AMD RadeonHD display driver (runtime libraries)
rc  libfglrx:i386   1:15.12-2~bpo8+1   i386   non-free 
ATI/AMD RadeonHD display driver (runtime libraries)
ii  libfglrx-amdxvba1:amd64 1:15.12-2~bpo8+2   amd64  AMD XvBA 
(X-Video Bitstream Acceleration) backend for VA API
ii  libgl1-fglrx-glx:amd64  1:15.12-2~bpo8+2   amd64  
proprietary libGL for the non-free ATI/AMD RadeonHD display 
rc  libgl1-fglrx-glx:i386   1:15.12-2~bpo8+1   i386   
proprietary libGL for the non-free ATI/AMD RadeonHD display 

VGA-compatible devices on PCI bus:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Oland PRO [Radeon R7 240] [1002:6613] (prog-if 00 [VGA controller])
Subsystem: Hightech Information System Ltd. Device [1787:2000]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: fglrx_pci


DRM and fglrx Informations from dmesg:
[0.00] AGP: No AGP bridge found
[0.00] AGP: Checking aperture...
[0.00] AGP: No AGP bridge found
[0.00] AGP: Node 0: aperture [bus addr 0x14fa00-0x14fbff] (32MB)
[0.00] AGP: Your BIOS doesn't leave an aperture memory hole
[0.00] AGP: Please enable the IOMMU option in the BIOS setup
[0.00] AGP: This costs you 64MB of RAM
[0.00] AGP: Mapping aperture over RAM [mem 0xc400-0xc7ff] 
(65536KB)
[1.286049] PCI-DMA: Disabling AGP.
[1.286191] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
[1.357066] Linux agpgart interface v0.103
[   14.746851] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, 
Starnberg, GERMANY' taints kernel.
[   14.803197] <6>[fglrx] Maximum main memory to use for locked dma buffers: 
7751 MBytes.
[   14.803575] <6>[fglrx]   vendor: 1002 device: 6613 revision: 0 count: 1
[   14.804507] <6>[fglrx] ioport: bar 4, base 0xee00, size: 0x100
[   14.805283] <6>[fglrx] Kernel PAT support is enabled
[   14.805322] <6>[fglrx] module loaded - fglrx 15.30.3 [Dec 17 2015] with 1 
minors
[   30.692946] <6>[fglrx] Firegl kernel thread PID: 921
[   30.693075] <6>[fglrx] Firegl kernel thread PID: 922
[   30.693191] <6>[fglrx] IRQ 28 Enabled
[   30.701655] <6>[fglrx] Reserved FB block: Shared offset:0, size:100 
[   30.701657] <6>[fglrx] Reserved FB block: Unshared offset:f7b4000, size:4000 
[   30.701658] <6>[fglrx] Reserved FB block: Unshared offset:f7b8000, 
size:548000 
[   30.701659] <6>[fglrx] Reserved FB block: Unshared offset:7ffee000, 
size:12000 

/etc/X11/xorg.conf does not exist.

Xorg X server log files on system:
-rw-r--r-- 1 root root 41242 Feb 21 21:24 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 50418 Aug 16 00:13 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:
[29.174] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[29.174] X Protocol Version 11, Revision 0
[29.174] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[29.174] Current Operating System: Linux newton.virtua.com.br 
4.6.0-0.bpo.1-amd64 #1 SMP Debian 4.6.4-1~bpo8+1 (2016-08-11) x86_64
[29.174] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.6.0-0.bpo.1-amd64 
root=UUID=a3aa82ac-605f-4846-90eb-ad6e7d469d74 ro quiet vga=795
[29.174] Build Date: 11 February 2015  12:32:02AM
[29.174] xorg-server 2:1.16.4-1 (http://www.debian.org/support) 
[29.174] Current version of pixman: 0.32.6
[29.174]Before reporting problems, check http://wiki.x.org
 

Bug#834274: mrpt: FTBFS in testing

[JOSE LUIS BLANCO CLARACO]

I couldn't replicate this particular crash in my machine with Eigen
3.3beta1, but I guess where the error is and have pushed a patch. The
package is now in mentors: [1].

I tested it 100% on my local system and in a pbuild (sid) environment,
without any problem, so hopefully this one will make it!

Cheers,

[1] https://mentors.debian.net/debian/pool/main/m/mrpt/mrpt_1.4.0-7.dsc

Bug#834274: mrpt: FTBFS in testing

[JOSE LUIS BLANCO CLARACO]

Yes, Santiago notified me and I'm investigating it... Thanks for taking
care!

Bug#834274: mrpt: FTBFS in testing

[JOSE LUIS BLANCO CLARACO]

You're right, it's better like that.

Done. It should be online within minutes in the same link:
https://mentors.debian.net/debian/pool/main/m/mrpt/mrpt_1.4.0-6.dsc

Cheers,

Bug#834274: mrpt: FTBFS in testing

[JOSE LUIS BLANCO CLARACO]

Gracias Santiago, (cc:Gianfranco)

This FTBFS did seem to be caused by the latest Eigen 3.3. beta
version. I could reproduce the error and it's fixed now upstream.

I have added another debian/patch to MRPT 1.4.0 and uploaded it to
mentors [1]. It could be great if any of you could sponsor it to
quickly fix this bug in Debian.

Thanks in advance for your time!!

Best,
JL

[1] https://mentors.debian.net/debian/pool/main/m/mrpt/mrpt_1.4.0-6.dsc


On Sun, Aug 14, 2016 at 2:28 AM, Santiago Vila <sanv...@unex.es> wrote:
> Package: src:mrpt
> Version: 1.4.0-5
> Severity: serious
>
> Dear maintainer:
>
> This package currently fails to build from source in stretch:
>
> --
> [ 29%] Building CXX object 
> libs/opengl/CMakeFiles/mrpt-opengl.dir/src/CEllipsoidInverseDepth2D.cpp.o
> cd /build/mrpt-1.4.0/obj-x86_64-linux-gnu/libs/opengl && /usr/bin/c++   
> -DMRPT_ASSIMP_VERSION_MAJOR=3 -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
> -Dmrpt_opengl_EXPORTS -I/usr/include/eigen3 -I/usr/include/eigen3/unsupported 
> -I/usr/include/libftdi1 -I/usr/include/opencv -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/x86_64-linux-gnu/ffmpeg 
> -I/usr/include/x86_64-linux-gnu/libavcodec 
> -I/usr/include/x86_64-linux-gnu/libavformat 
> -I/usr/include/x86_64-linux-gnu/libswscale -isystem 
> /usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -isystem 
> /usr/include/wx-3.0 -I/build/mrpt-1.4.0/. 
> -I/build/mrpt-1.4.0/obj-x86_64-linux-gnu/include/mrpt-config/unix 
> -I/build/mrpt-1.4.0/libs/opengl/src -I/build/mrpt-1.4.0/libs/opengl/src/glext 
> -I/usr/include/assimp -I/build/mrpt-1.4.0/libs/opengl/include 
> -I/build/mrpt-1.4.0/libs/base/include  -isystem /usr/include/wx-3.0 -I 
> /usr/include/wx-3.0 -isystem 
> /usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I 
> /usr/lib/x86_64-linux-gnu/wx/include/gtk2-unic
>  ode-3.0 -isystem /usr/include/eigen3 -g -O2 
> -fdebug-prefix-map=/build/mrpt-1.4.0=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -pthread 
> -Wreturn-type -Wextra -Wno-unused-parameter  -Wall -Wno-long-long 
> -Wno-variadic-macros -Wno-write-strings -std=c++11 -pthread  -msse2 
> -funroll-loops -mfpmath=sse  -g -O2 -fdebug-prefix-map=/build/mrpt-1.4.0=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC   
> -I/usr/include/assimp -o 
> CMakeFiles/mrpt-opengl.dir/src/CEllipsoidInverseDepth2D.cpp.o -c 
> /build/mrpt-1.4.0/libs/opengl/src/CEllipsoidInverseDepth2D.cpp
> tests/CMakeFiles/test_mrpt_base.dir/build.make:353: recipe for target 
> 'tests/CMakeFiles/test_mrpt_base.dir/__/libs/base/src/math/matrix_ops4_unittest.cpp.o'
>  failed
> make[4]: *** 
> [tests/CMakeFiles/test_mrpt_base.dir/__/libs/base/src/math/matrix_ops4_unittest.cpp.o]
>  Error 1
> --
>
> There are full logs available here:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/mrpt.html
>
> Thanks.



-- 
___

Jose Luis Blanco-Claraco
CITE-IV 1.05
Universidad de Almería, Departamento de Ingeniería
04120 Almería (Spain)
http://www.ual.es/~jlblanco/
___

Bug#831792: RFS: scid/1:4.6.2-0.1 [NMU]

[Jose G. López]

On Tue, 26 Jul 2016 18:18:51 + (UTC)
Gianfranco Costamagna  wrote:

> lets see.
> 1)
> 
> The package will be probably orphaned in 10-15 days, so you might want to set 
> yourself
> as Maintainer and adopt it
> 
> 2)
> +* Copyright (C) 2013-2015  Fulvio Benini
> 
> 
> maybe you want also to put copyright file in machine readable format
> https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> 

Done.

> 3) 
> X: scid source: maybe-not-arch-all-binnmuable scid -> scid-data
> 
> 4) the breaks+replaces can be dropped, since that version is already 
> available in oldstable
> 
> Breaks: scid (<=1:4.3.0.cvs20110714-2)
> Replaces: scid (<=1:4.3.0.cvs20110714-2)
> Recommends: scid (>=1:4.3.0.cvs20111216-1)
> 

Dropped.

> last thing:
> 
> 4) this hack seems useless now
> sed s/x86_64-linux-gnu/$(DEB_HOST_MULTIARCH)/ configure > configure.sed
> chmod 755 configure.sed
> ./configure.sed BINDIR="$(CURDIR)/debian/tmp/scid/usr/games" \

Deleted too.

> 
> please fix the above and I'll give another review/upload.
> 
> thanks,
> 
> G.

Hi Gianfranco,

Sorry for this late replay, I've been working on your advices and meanwhile 
packaging a new released version (4.6.4).
You'll see in this new version I had to repack upstream sources to make the 
package DFSG compliant. Oliver did it with a script (prep.sh); I've used uscan 
and excluding files in debian/copyright (hope it's correct).

It's uploaded to mentors[0].

Thanks and regards,

P.D: On mentors, the watch file seems that doesn't work but on my devel machine 
is working properly ??

[0]https://mentors.debian.net/package/scid


pgpGPAyhYYrPh.pgp
Description: PGP signature

Bug#833009: linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA because of i915 and i2c_designware

[Jose M Calhariz]

Hi,

I have tried the vanilla kernel 4.7.  Now the hibernation almost works. 
When I select hibernation after some minutes I need to turn off the
laptop.  But when I turn on it awakes and return to the previous state. 
I still see the same error messages, but this time the keyboard works.

Kind regards
Jose M Calhariz




signature.asc
Description: OpenPGP digital signature

Bug#833016: linux-image-4.7.0-rc7-amd64-unsigned: Shutdown when pressed any key of the keyboard

[Jose M Calhariz]

Hi,

I have just tried a vanilla kernel 4.7 and it just works.

Kind regards
Jose M Calhariz




signature.asc
Description: OpenPGP digital signature

Bug#831184: mumble: FTBFS with GCC 6, seems Ice related

[Jose Gutierrez de la Concha]

On Thu, Aug 4, 2016 at 7:03 PM, Chris Knadle <chris.kna...@coredump.us>
wrote:

>
>
> Jose Gutierrez de la Concha:
> > Hi,
> >
> > When building an Ice application with C++11/C++14 enabled you need to
> link
> > with libraries with ++11 suffix -lIce++11 instead of -lIce.
> >
> > libzeroc-ice3.6 provide C++98 libraries and C++11 libraries with ++11
> > suffix and the APIs are slightly different.
>
> I tried this (patch is attached), but this results in an error message
> that the linker is unable to find -lIce++11:
>
>
You are right, I was confused with our master branch (3.7) where we get rid
of c++11 subdir

> -
>
> g++ -c -include release/murmurd -m64 -pipe -g -O2
> -fdebug-prefix-map=/build/mumble-1.2.16/src/murmur=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wfatal-errors
> -fvisibility=hidden -g -std=c++11 -O2 -Wall -W -D_REENTRANT
> -DNO_UPDATE_CHECK -DPLUGIN_PATH=/usr/lib/mumble
> -DMUMBLE_VERSION=1.2.16-1 -DHAVE_LIMITS_H -DHAVE_ENDIAN_H
> -DRESTRICT=__restrict__ -D_FORTIFY_SOURCE=2
> -DMUMBLE_VERSION_STRING=1.2.16 -DMURMUR -DUSE_DBUS -DUSE_ICE
> -DUSE_BONJOUR -D_REENTRANT -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_XML_LIB
> -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXml
> -I/usr/include/qt4/QtSql -I/usr/include/qt4 -I/usr/include/qt4/QtDBus
> -I../../src -I. -I/usr/include/speech-dispatcher -I../bonjour -Irelease
> -I/usr/include/avahi-compat-libdns_sd -o release/moc_BonjourServer.o
> release/moc_BonjourServer.cpp
>
> g++ -m64 -Wl,-z,relro -Wl,-z,relro -Wl,-z,now -Wl,-O1 -o
> ../../release/murmurd release/ACL.o release/Group.o release/Channel.o
> release/Connection.o release/User.o release/Timer.o release/CryptState.o
> release/OSInfo.o release/Net.o release/SSL.o release/Version.o
> release/main.o release/Server.o release/ServerUser.o release/ServerDB.o
> release/Register.o release/Cert.o release/Messages.o release/Meta.o
> release/RPC.o release/UnixMurmur.o release/DBus.o release/MurmurIce.o
> release/BonjourServiceRegister.o release/BonjourServer.o
> release/Mumble.pb.o release/Murmur.o release/moc_ACL.o
> release/moc_Channel.o release/moc_Connection.o release/moc_Server.o
> release/moc_ServerUser.o release/moc_Meta.o release/moc_UnixMurmur.o
> release/moc_DBus.o release/moc_MurmurIce.o
> release/moc_BonjourServiceRegister.o release/moc_BonjourServer.o
> -L../../release -L/usr/lib/x86_64-linux-gnu -lprotobuf -lcap -lIce++11
> -lIceUtil -lQtDBus -lssl -lcrypto -ldns_sd -lavahi-common -lavahi-client
> -lpthread -lQtSql -lQtXml -lQtNetwork -lQtCore

/usr/bin/ld: cannot find -lIce++11
>
> collect2: error: ld returned 1 exit status
>
> Makefile.Release:183: recipe for target '../../release/murmurd' failed
>
> make[4]: *** [../../release/murmurd] Error 1
>
> -
>
> I had a quick look at the documentation for using Ice 3.6 concerning C++
> and at the moment it doesn't mention using -lIce++11:
>
>
> https://doc.zeroc.com/display/Ice36/Using+the+Linux+Binary+Distributions#
> UsingtheLinuxBinaryDistributions-C++
>
> instead it's suggested to use -L/usr/lib/c++11 for 32-bit and
> -L/usr/lib64/c++11 for 64-bit.  The Debian package seems to have this
> directory in /usr/lib/x86_64-linux-gnu/c++11.  I tried adding that but
> that doesn't seem to help (and I suspect this is redundant as
> -L/usr/lib/x86_64-linux-gnu is included):
>
> -
>
> g++ -c -include release/murmurd -m64 -pipe -g -O2
> -fdebug-prefix-map=/build/mumble-1.2.16/src/murmur=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wfatal-errors
> -fvisibility=hidden -g -std=c++11 -O2 -Wall -W -D_REENTRANT
> -DNO_UPDATE_CHECK -DPLUGIN_PATH=/usr/lib/mumble
> -DMUMBLE_VERSION=1.2.16-1 -DHAVE_LIMITS_H -DHAVE_ENDIAN_H
> -DRESTRICT=__restrict__ -D_FORTIFY_SOURCE=2
> -DMUMBLE_VERSION_STRING=1.2.16 -DMURMUR -DUSE_DBUS -DUSE_ICE
> -DUSE_BONJOUR -D_REENTRANT -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_XML_LIB
> -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXml
> -I/usr/include/qt4/QtSql -I/usr/include/qt4 -I/usr/include/qt4/QtDBus
> -I../../src -I. -I/usr/include/speech-dispatcher -I../bonjour -Irelease
> -I/usr/include/avahi-compat-libdns_sd -o release/moc_BonjourServer.o
> release/moc_BonjourServer.cpp
>
> g++ -m64 -Wl,-z,relro -Wl,-z,relro -Wl,-z,now -Wl,-O1 -o
> ../../release/murmurd release/ACL.o release/

Bug#831184: mumble: FTBFS with GCC 6, seems Ice related

[Jose Gutierrez de la Concha]

Hi,

When building an Ice application with C++11/C++14 enabled you need to link
with libraries with ++11 suffix -lIce++11 instead of -lIce.

libzeroc-ice3.6 provide C++98 libraries and C++11 libraries with ++11
suffix and the APIs are slightly different.

Regards,
José

On Mon, Aug 1, 2016 at 2:56 AM, Chris Knadle 
wrote:

> Greetings.
>
> Unfortunately Mumble in Debian won't compile with GCC-6 right now:
>
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831184
>
> After talking to Mikkel Krautz (mumble upstream) I tried adding the
> following to the unix {} block in murmur.pro:
>
> QMAKE_CXXFLAGS *= -std=c++11
>
> but unfortunately this doesn't seem to help.  I'm adding the maintainers
> of zero-ice hoping that we can jointly track down how to fix this.
>
> Thanks.
>
>-- Chris
>
> --
> Chris Knadle
> chris.kna...@coredump.us
>
> partital build failure log (with the excepiton of the -std=c++11 switch
> it looks the same as the log Lucas Nussbaum supplied in the bug):
>
> ---
> [...]
> g++ -c -include release/murmurd -m64 -pipe -g -O2
> -fstack-protector-strong -Wformat -Werror=format-security -Wfatal-errors
> -fvisibility=hidden -g -std=c++11 -O2 -Wall -W -D_REENTRANT
> -DNO_UPDATE_CHECK -DPLUGIN_PATH=/usr/lib/mumble
> -DMUMBLE_VERSION=1.2.16-1 -DHAVE_LIMITS_H -DHAVE_ENDIAN_H
> -DRESTRICT=__restrict__ -D_FORTIFY_SOURCE=2
> -DMUMBLE_VERSION_STRING=1.2.16 -DMURMUR -DUSE_DBUS -DUSE_ICE
> -DUSE_BONJOUR -D_REENTRANT -DQT_NO_DEBUG -DQT_SQL_LIB -DQT_XML_LIB
> -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED
> -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
> -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXml
> -I/usr/include/qt4/QtSql -I/usr/include/qt4 -I/usr/include/qt4/QtDBus
> -I../../src -I. -I/usr/include/speech-dispatcher -I../bonjour -Irelease
> -I/usr/include/avahi-compat-libdns_sd -o release/moc_BonjourServer.o
> release/moc_BonjourServer.cpp
>
> g++ -m64 -Wl,-z,relro -Wl,-z,relro -Wl,-z,now -Wl,-O1 -o
> ../../release/murmurd release/ACL.o release/Group.o release/Channel.o
> release/Connection.o release/User.o release/Timer.o release/CryptState.o
> release/OSInfo.o release/Net.o release/SSL.o release/Version.o
> release/main.o release/Server.o release/ServerUser.o release/ServerDB.o
> release/Register.o release/Cert.o release/Messages.o release/Meta.o
> release/RPC.o release/UnixMurmur.o release/DBus.o release/MurmurIce.o
> release/BonjourServiceRegister.o release/BonjourServer.o
> release/Mumble.pb.o release/Murmur.o release/moc_ACL.o
> release/moc_Channel.o release/moc_Connection.o release/moc_Server.o
> release/moc_ServerUser.o release/moc_Meta.o release/moc_UnixMurmur.o
> release/moc_DBus.o release/moc_MurmurIce.o
> release/moc_BonjourServiceRegister.o release/moc_BonjourServer.o
> -L../../release -L/usr/lib/x86_64-linux-gnu -lprotobuf -lcap -lIce
> -lIceUtil -lQtDBus -lssl -lcrypto -ldns_sd -lavahi-common -lavahi-client
> -lpthread -lQtSql -lQtXml -lQtNetwork -lQtCore
>
> release/Murmur.o: In function
> `IceInternal::Cpp11FnCallbackNC::~Cpp11FnCallbackNC()':
>
> /usr/include/Ice/Proxy.h:95: undefined reference to `vtable for
> IceInternal::Cpp11FnCallbackNC'
>
> /usr/include/Ice/Proxy.h:95: undefined reference to `vtable for
> IceInternal::Cpp11FnCallbackNC'
>
> /usr/include/Ice/Proxy.h:95: undefined reference to `vtable for
> IceInternal::Cpp11FnCallbackNC'
>
> /usr/include/Ice/Proxy.h:95: undefined reference to `vtable for
> IceInternal::Cpp11FnCallbackNC'
>
> /usr/include/Ice/Proxy.h:95: undefined reference to `vtable for
> IceInternal::Cpp11FnCallbackNC'
>
> release/Murmur.o:/usr/include/Ice/Proxy.h:95: more undefined references
> to `vtable for IceInternal::Cpp11FnCallbackNC' follow
> release/Murmur.o: In function `Cpp11CB':
>
> /<>/src/murmur/Murmur.cpp:7028: undefined reference to
> `IceInternal::Cpp11FnCallbackNC::Cpp11FnCallbackNC(std::function (IceUtil::Exception const&)> const&, std::function const&)'
> [...]
> ---
>



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

Bug#833016: linux-image-4.7.0-rc7-amd64-unsigned: Shutdown when pressed any key of the keyboard

[Jose M Calhariz]

Package: src:linux
Version: 4.7~rc7-1~exp1
Severity: important
Tags: upstream

Being affected by #833009 I decided to try a kernel from experimental.
Both of the kernels for amd64, the unsigned and the other, cause a
orderly shutodwn when I press any key of the keyboard.

I have no clue why this happens, but being a regression, I decided to
report.

Kind regards
Jose M Calhariz


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: E200HA
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: E200HA.210
board_vendor: ASUSTeK COMPUTER INC.
board_name: E200HA
board_version: 1.0   

** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Braswell SoC Transaction Router 
[8086:2280] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell SoC Transaction Router 
[1043:10b0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:0b.0 Signal processing controller [1180]: Intel Corporation Braswell P-Unit 
Power Management [8086:22dc] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell P-Unit Power Management 
[1043:10b0]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:14.0 USB controller [0c03]: Intel Corporation Braswell USB xHCI Host 
Controller [8086:22b5] (rev 22) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Braswell USB xHCI Host Controller 
[1043:10b0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:1a.0 Encryption controller [1080]: Intel Corporation Braswell Trusted 
Execution Engine Interface [8086:2298] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell Trusted Execution Engine 
Interface [1043:10b0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:1c.0 PCI bridge [0604]: Intel Corporation Braswell PCIe Port 1 [8086:22c8] 
(rev 22) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1f.0 ISA bridge [0601]: Intel Corporation Braswell Platform Controller Unit 
LPC [8086:229c] (rev 22)
Subsystem: ASUSTeK Computer Inc. Braswell Platform Controller Unit LPC 
[1043:10b0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich

01:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter [168c:0042] (rev 30)
Subsystem: AzureWave QCA9377 802.11ac Wireless Network Adapter 
[1a3b:2b31]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci


** USB devices:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0b95:7720 ASIX Electronics Corp. AX88772
Bus 001 Device 003: ID 13d3:3496 IMC Networks 
Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=locale: Cannot set LC_CTYPE to default 
locale: No such file or directory
locale: Cannot set LC_MESSA

Bug#833009: linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA because of i915 and i2c_designware

[Jose M Calhariz]

Package: src:linux
Version: 4.6.4-1
Severity: normal
Tags: upstream

I have problems that I can not suspend or hibernate my E200HA.  After
some reserach I found this Web page:
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues

Maybe the suspend is not supported, but the hibernate should, because
of this message on kern.log:

Jul 28 22:56:00 lal kernel: [0.472724] ACPI: (supports S0 S4 S5)

So, doing some extra research I suspect the problem is in the module
i915 and on the module i2c_designware.  Because switching to a text
console and issuing the command: "echo disk > /sys/power/state" the
system hibernate and awakes when I request.  But it awakes without
keyboard and with following messages on the console:

[   50.827873] [drm] stuck on blitter ring
[   50.834932] [drm] stuck on bsd ring
[   50.841830] [drm] stuck on video enhancement ring
[   50.851177] [drm] GPU HANG: ecode 8:0:0x7a2af415, reason: Ring hung, action: 
reset
[   50.854730] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
[   50.858380] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
[   50.860886] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[   50.863336] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
[   50.865839] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   50.868532] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, 
banning!
[   50.873485] drm/i915: Resetting chip after gpu hang
[   51.729188] IPv6: ADDRCONF(NETDEV_CHANGE): enx0019fd4cb596: link becomes 
ready
[   51.737806] asix 1-4:1.0 enx0019fd4cb596: link up, 100Mbps, full-duplex, lpa 
0xCDE1
[  129.340496] i2c_designware 808622C1:00: timeout in enabling adapter
[  130.348085] i2c_designware 808622C1:00: controller timed out
[  130.355959] i2c_designware 808622C1:00: Unknown Synopsys component type: 
0x0000

Kind regards
Jose M Calhariz


-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 
root=UUID=577ff77a-2aa2-4c43-9c83-91e107b674c2 ro printk.time=n initcall_debug 
no_console_suspend

** Tainted: E (8192)
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[   49.008511] call regulatory.0+ returned 0 after 0 usecs
[   49.010919] calling  intel_backlight+ @ 2728, parent: card0-eDP-1
[   49.013223] call intel_backlight+ returned 0 after 0 usecs
[   49.015521] calling  input6+ @ 2728, parent: LNXVIDEO:00
[   49.017797] call input6+ returned 0 after 0 usecs
[   49.020078] calling  input7+ @ 2728, parent: pcspkr
[   49.021968] call input7+ returned 0 after 17 usecs
[   49.023843] calling  input8+ @ 2728, parent: i2c-ELAN0100:00
[   49.025720] call input8+ returned 0 after 0 usecs
[   49.027601] calling  coretemp.0+ @ 2728, parent: platform
[   49.029487] call coretemp.0+ returned 0 after 0 usecs
[   49.031392] calling  asus-nb-wmi+ @ 2728, parent: platform
[   49.033284] call asus-nb-wmi+ returned 0 after 1 usecs
[   49.035181] calling  input9+ @ 2728, parent: asus-nb-wmi
[   49.037073] call input9+ returned 0 after 0 usecs
[   49.038960] calling  input10+ @ 2728, parent: 0018:0B05:8585.0001
[   49.040893] call input10+ returned 0 after 19 usecs
[   49.042822] calling  input10::numlock+ @ 2728, parent: input10
[   49.044753] call input10::numlock+ returned 0 after 0 usecs
[   49.046684] calling  input10::capslock+ @ 2728, parent: input10
[   49.048625] call input10::capslock+ returned 0 after 0 usecs
[   49.050570] calling  input10::scrolllock+ @ 2728, parent: input10
[   49.052528] call input10::scrolllock+ returned 0 after 0 usecs
[   49.054491] calling  input10::compose+ @ 2728, parent: input10
[   49.056460] call input10::compose+ returned 0 after 0 usecs
[   49.058429] calling  input10::kana+ @ 2728, parent: input10
[   49.060402] call input10::kana+ returned 0 after 0 usecs
[   49.062379] calling  rfkill1+ @ 2728, parent: phy0
[   49.064358] call rfkill1+ returned 0 after 10 usecs
[   49.066337] PM: restore of devices complete after 4600.592 msecs
[   49.068386] usb 1-4:1.0: rebind failed: -517
[   49.070372] usb 1-3:1.0: rebind failed: -517
[   49.072323] usb 1-3:1.1: rebind failed: -517
[   49.074671] PM: Image restored successfully.
[   49.074693] PM: Basic memory bitmaps freed
[   49.074699] Restarting tasks ... done.
[   49.089295] pci_bus :01: Allocating resources
[   49.089491] pcieport :00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 
01] add_size 1000
[   49.089498] pcieport :00:1c.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 01] add_size 20 add_align 10
[   49.089509] pcieport :00:1c.0: res[15]=[mem 0x0010-0x000f 64bit 
pref] res_to_dev_res

Bug#832925: firmware-atheros: Please add the firmware for the wireless QCA9377 from atheros

[Jose M Calhariz]

Package: firmware-atheros
Version: 20160110-1
Severity: normal

I have a new laptop Asus E200HA.  I was able to use the stretch DVD to install 
Debian.
I found that this package is missing the firmware for the QCA9377.  The 
firmware can be 
download from "git clone 
https://github.com/ajaybhatia/Qualcomm-Atheros-QCA9377-Wifi-Linux;
It contains too a driver, but that is not needed on kernel 4.6.  The install.sh 
script 
is not good for Debian too.

lspci 
00:00.0 Host bridge: Intel Corporation Braswell SoC Transaction Router (rev 22)
00:02.0 VGA compatible controller: Intel Corporation Braswell PCI Configuration 
Registers (rev 22)
00:0b.0 Signal processing controller: Intel Corporation Braswell P-Unit Power 
Management (rev 22)
00:14.0 USB controller: Intel Corporation Braswell USB xHCI Host Controller 
(rev 22)
00:1a.0 Encryption controller: Intel Corporation Braswell Trusted Execution 
Engine Interface (rev 22)
00:1c.0 PCI bridge: Intel Corporation Braswell PCIe Port 1 (rev 22)
00:1f.0 ISA bridge: Intel Corporation Braswell Platform Controller Unit LPC 
(rev 22)
01:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter (rev 30)


Kind regards
Jose M Calhariz

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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)

firmware-atheros depends on no packages.

firmware-atheros recommends no packages.

Versions of packages firmware-atheros suggests:
ii  initramfs-tools  0.125

-- no debconf information