Bug#785074: sucrose-0.98: not installable in sid

[Ralf Treinen]

Package: sucrose-0.98
Version: 0.98.8-2
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

sucrose-0.98 is not installable in sid since 2015-04-04. It depends on
gir1.2-maliit-1.0, which exists only in experimental.

Cheers -Ralf.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#780359: Options w.r.t. libcgal11 transition

[Jonathan Wiltshire]

On 2015-05-11 22:35, Joachim Reichel wrote:

Hi,

dolfin is now the only reverse dependency holding up the libcgal11 
transition.


What are the options?
(1) Fix dolfin without causing another transition
(2) Remove dolfin from testing
(3) Upload 1.5.0-1 from experimental to unstable
(4) ...?


dolfin has a rdep in testing, so removing it isn't (yet) an option. 
(Although its rdep fenics isn't going to migrate either because it 
depends on the version of dolfin in experimental since six weeks... what 
a mess.)


I've asked ftp-masters to decruft gdal making dolfin in sid 
uninstallable. Britney may be able to smooth-update gdal, in which case 
the transition can take place and the dolfin maintainers can fix the bug 
at their leisure.


--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

directhex i have six years of solaris sysadmin experience, from
8-10. i am well qualified to say it is made from bonghits
layered on top of bonghits


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#784245:

[Debian Bug Tracking System]

Processing control commands:

 severity -1 serious
Bug #784245 [src:ghc] ghc: build against llvm-toolchain = 3.5
Severity set to 'serious' from 'normal'

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#784245:

[Joachim Breitner]

Hi,

Am Dienstag, den 12.05.2015, 06:52 + schrieb Gianfranco Costamagna:
 Hi Joachim, since this bug is already there in jessie, it doesn't appear as a 
 regression, hence
 it doesn't prevent testing migration.
 If I'm correct, your intent is to let 7.8 migrate, and this isn't a blocker.

Yes, that is my intend. But I’m worried about auto-removal of GHC on
testing...

Or is GHC already a key package, and hence immune to auto-removal? Not
according to https://udd.debian.org/cgi-bin/key_packages.cgi.


Oh well, we’ll see what happens.

Greetings,
Joachim

-- 
Joachim nomeata Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata


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

Bug#784947: marked as done (libt-digest-java: Version 3.1 is severely incompatible with version 3.0)

[Debian Bug Tracking System]

Your message dated Tue, 12 May 2015 07:04:51 +
with message-id e1ys4fh-0005t7...@franck.debian.org
and subject line Bug#784947: fixed in t-digest 1:3.0-1
has caused the Debian Bug report #784947,
regarding libt-digest-java: Version 3.1 is severely incompatible with version 
3.0
to be marked as done.

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

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


-- 
784947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libt-digest-java
Version: 3.0-1
Severity: grave

Elasticsearch 1.4.5 cannot be built with libt-digest-java/3.1-1 installed.
Reverting back to 3.0-1 resolves this problem.

The attached report generated by japi-compliance-checker shows that the
3.1 is backwards incompatible. The package should therefore be reverted
to 3.0.

-Hilko
Title: 
t-digest: 3.0 to 3.1 compatibility report





API compatibility report for the t-digest library between 3.0 and 3.1 versions


BinaryCompatibility
SourceCompatibility

Test Info

Library Namet-digest
Version #13.0
Version #23.1
Java Version1.7.0_79
SubjectBinary Compatibility

Test ResultsTotal Java ARchives1Total Methods / Classes192 / 13VerdictIncompatible(30.2%)

Problem SummarySeverityCountAdded Methods-33Removed MethodsHigh10Problems withData TypesHigh4Medium1Low4Problems withMethodsHigh1Medium0Low0

Added Methods (33)
t-digest-3.1.jar, AbstractTDigest.class
package com.tdunning.math.stats

AbstractTDigest.weightedAverage(double x1, int w1, double x2, int w2) [static] :double


[mangled: com/tdunning/math/stats/AbstractTDigest.weightedAverage:(DIDI)D]


AbstractTDigest.weightedAverageSorted(double x1, int w1, double x2, int w2) [static] :double


[mangled: com/tdunning/math/stats/AbstractTDigest.weightedAverageSorted:(DIDI)D]


t-digest-3.1.jar, ArrayDigest.class
package com.tdunning.math.stats

ArrayDigest.centroids() :java.util.CollectionCentroid


[mangled: com/tdunning/math/stats/ArrayDigest.centroids:()Ljava/util/Collection;]


t-digest-3.1.jar, AVLTreeDigest.class
package com.tdunning.math.stats

AVLTreeDigest.centroids() :java.util.CollectionCentroid


[mangled: com/tdunning/math/stats/AVLTreeDigest.centroids:()Ljava/util/Collection;]


t-digest-3.1.jar, Encoding.class
package com.tdunning.math.stats

MergingDigest.Encoding.valueOf(String name) [static] :MergingDigest.Encoding


[mangled: com/tdunning/math/stats/MergingDigest.Encoding.valueOf:(Ljava/lang/String;)Lcom/tdunning/math/stats/MergingDigest$Encoding;]


MergingDigest.Encoding.values() [static] :MergingDigest.Encoding[]


[mangled: com/tdunning/math/stats/MergingDigest.Encoding.values:()[Lcom/tdunning/math/stats/MergingDigest$Encoding;]


t-digest-3.1.jar, GroupTree.class
package com.tdunning.math.stats

GroupTree.add(Centroid centroid) :boolean


[mangled: com/tdunning/math/stats/GroupTree.add:(Lcom/tdunning/math/stats/Centroid;)Z]


GroupTree.add(Object x0) :boolean


[mangled: com/tdunning/math/stats/GroupTree.add:(Ljava/lang/Object;)Z]


t-digest-3.1.jar, MergingDigest.class
package com.tdunning.math.stats

MergingDigest.add(double x, int w) :void


[mangled: com/tdunning/math/stats/MergingDigest.add:(DI)V]


MergingDigest.add(double x, int w, java.util.ListDouble history) :void


[mangled: com/tdunning/math/stats/MergingDigest.add:(DILjava/util/List;)V]


MergingDigest.asBytes(java.nio.ByteBuffer buf) :void


[mangled: com/tdunning/math/stats/MergingDigest.asBytes:(Ljava/nio/ByteBuffer;)V]


MergingDigest.asSmallBytes(java.nio.ByteBuffer buf) :void


[mangled: com/tdunning/math/stats/MergingDigest.asSmallBytes:(Ljava/nio/ByteBuffer;)V]


MergingDigest.byteSize() :int


[mangled: com/tdunning/math/stats/MergingDigest.byteSize:()I]


MergingDigest.cdf(double x) :double


[mangled: com/tdunning/math/stats/MergingDigest.cdf:(D)D]


MergingDigest.centroids() :java.util.CollectionCentroid


[mangled: com/tdunning/math/stats/MergingDigest.centroids:()Ljava/util/Collection;]


MergingDigest.compress() :void


[mangled: com/tdunning/math/stats/MergingDigest.compress:()V]


MergingDigest.compression() :double


[mangled: com/tdunning/math/stats/MergingDigest.compression:()D]


MergingDigest.fromBytes(java.nio.ByteBuffer buf) [static] :MergingDigest


[mangled: com/tdunning/math/stats/MergingDigest.fromBytes:(Ljava/nio/ByteBuffer;)Lcom/tdunning/math/stats/MergingDigest;]


MergingDigest.MergingDigest(double compression)


[mangled: com/tdunning/math/stats/MergingDigest.init:(D)V]


MergingDigest.MergingDigest(double compression, int bufferSize)


[mangled: 

Bug#784069: marked as done (gtk-redshift: redshift-gtk does not start (crash?))

[Debian Bug Tracking System]

Your message dated Tue, 12 May 2015 14:13:30 +0530
with message-id 5551bd32.3050...@debian.org
and subject line Re: Bug#784069: gtk-redshift: redshift-gtk does not start 
(crash?)
has caused the Debian Bug report #784069,
regarding gtk-redshift: redshift-gtk does not start (crash?)
to be marked as done.

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

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


-- 
784069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: gtk-redshift
Version: 1.9.1-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I'm trying to start redshift-gtk, for example from the command line. My desktop
is a plain MATE desktop on Debian 8/stable, where the applet should not have a
problem. (other Linux distributions with MATE and redshift-gtk work fine). I
tried on this actual system and also previously in VirtualBox.
   * What was the outcome of this action?
nothing happens. The shell reports an exit code ($?) of 255.
   * What outcome did you expect instead?
I expected redshift gtk to start and open a window or install itself in the
system tray.



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

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 gtk-redshift depends on:
ii  gir1.2-appindicator3-0.1  0.4.92-3.1
ii  python-gtk2   2.24.0-4
ii  python3   3.4.2-2
ii  python3-gi3.14.0-1
ii  python3-xdg   0.25-4
pn  python3:any   none
ii  redshift  1.9.1-4

Versions of packages gtk-redshift recommends:
ii  at-spi2-core  2.14.0-1

gtk-redshift suggests no packages.

-- no debconf information
---End Message---
---BeginMessage---
redshift (1.9.1-4) unstable; urgency=medium

  Starting with version 1.9, redshift upstream has dropped support for
  determining location using GNOME Clock. Hence, users using the GTK
  variant of redshift need to provide the location information manually
  .
  The settings can be put into a file. Please refer to the manual page
  for details

 -- Ritesh Raj Sarraf r...@debian.org  Fri, 10 Oct 2014 13:02:10 +0530


There is no support to determine the location using your GNOME clock
anymore. What you need to do now is to manually set the location, or
else use a UI that allows that. Under GNOME, there's a
gnome-shell-extension. Under KDE, there's a plasmoid.


Ritesh


On Saturday 02 May 2015 10:53 PM, Ulrich Hobelmann wrote:
 Package: gtk-redshift
 Version: 1.9.1-4
 Severity: grave
 Justification: renders package unusable

 Dear Maintainer,

* What exactly did you do (or not do) that was effective (or
  ineffective)?
 I'm trying to start redshift-gtk, for example from the command line. My 
 desktop
 is a plain MATE desktop on Debian 8/stable, where the applet should not have a
 problem. (other Linux distributions with MATE and redshift-gtk work fine). I
 tried on this actual system and also previously in VirtualBox.
* What was the outcome of this action?
 nothing happens. The shell reports an exit code ($?) of 255.
* What outcome did you expect instead?
 I expected redshift gtk to start and open a window or install itself in the
 system tray.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System




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

Bug#780359: Options w.r.t. libcgal11 transition

[Johannes Ring]

On Mon, May 11, 2015 at 11:35 PM, Joachim Reichel
joachim.reic...@gmx.de wrote:
 Hi,

 dolfin is now the only reverse dependency holding up the libcgal11 transition.

 What are the options?
 (1) Fix dolfin without causing another transition
 (2) Remove dolfin from testing
 (3) Upload 1.5.0-1 from experimental to unstable

This will be the correct solution IMO. I will do that now.

Johannes

 (4) ...?

 (1) I don't know the details but it seems to me that this is not easy.

 (3) This causes another transition, but the only reverse dependencies of the
 binary packages of dolfin are python-viper (plus the meta packages fenics,
 science-mathematics and science-mathematics-dev). Rebuilding python-viper
 against dolfin 1.5.0-1 worked without problems. Maybe this additional 
 transition
 isn't that bad (apart from the delay)?

 BTW does anyone understand why dolfin does not appear in the list of
 autoremovals? The bug is release-critical and not fixed in unstable/testing,
 only experimental.

 Joachim

 --
 debian-science-maintainers mailing list
 debian-science-maintain...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: severity of 776512 is grave

[Debian Bug Tracking System]

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

 severity 776512 grave
Bug #776512 [mantis] function InsertData() is defined twice: installation is 
broken
Severity set to 'grave' from 'normal'
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#783899: fixed in liblog-any-perl 1.032-1

[Emilio Pozuelo Monfort]

On Fri, 01 May 2015 19:35:00 + gregor herrmann gre...@debian.org wrote:
  liblog-any-perl (1.032-1) unstable; urgency=medium
  .
* Team upload.
  .
* Add Breaks/Replaces/Provides on liblog-any-adapter-perl.
  liblog-any-adapter-perl was merged into liblog-any-perl.
  (Closes: #783899)

Sounds like you should file a RM bug against ftp.debian.org for
liblog-any-adapter-perl.

Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#780359: Options w.r.t. libcgal11 transition

[Jonathan Wiltshire]

On 2015-05-12 09:07, Johannes Ring wrote:

On Mon, May 11, 2015 at 11:35 PM, Joachim Reichel
joachim.reic...@gmx.de wrote:

Hi,

dolfin is now the only reverse dependency holding up the libcgal11 
transition.


What are the options?
(1) Fix dolfin without causing another transition
(2) Remove dolfin from testing
(3) Upload 1.5.0-1 from experimental to unstable


This will be the correct solution IMO. I will do that now.



No, please do NOT do that now. It is the correct long-term solution, but 
it will entangle the cgal transition.


Wait until britney has a chance to sort it out.

--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

directhex i have six years of solaris sysadmin experience, from
8-10. i am well qualified to say it is made from bonghits
layered on top of bonghits


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785035: [Help] Re: Bug#785035: ugene: FTBFS on amd64

[Andreas Tille]

Hi folks,

Ugine is in a quite bad state.  We are lagging behind upstream and it
has gathered some important errors now.  I currently do not feel able to
care for this one reported by Lisandro (thanks for reporting BTW).

Is there anybody who might be able to spent some time into this - probably
by taking the latest upstream and see what can be done about this error
on the latest code base?

Kind regards

   Andreas.

On Mon, May 11, 2015 at 02:52:13PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
 Source: ugene
 Version: 1.12.3+dfsg-1
 Severity: serious
 Justification: FTBFS on amd64
 
 Hi! While looking at #784382 I tried to compile ugene on a clean sid chroot
 using sbuild and it FTBFS.
 
 I'm attaching the build log.
 
 Kinds regards, Lisandro. 
 
 -- System Information:
 Debian Release: 8.0
   APT prefers stable
   APT policy: (500, 'stable')
 Architecture: amd64 (x86_64)
 
 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: systemd (via /run/systemd/system)


 ___
 Debian-med-packaging mailing list
 debian-med-packag...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#780359: Options w.r.t. libcgal11 transition

[Johannes Ring]

On Tue, May 12, 2015 at 10:07 AM, Johannes Ring joha...@simula.no wrote:
 On Mon, May 11, 2015 at 11:35 PM, Joachim Reichel
 joachim.reic...@gmx.de wrote:
 Hi,

 dolfin is now the only reverse dependency holding up the libcgal11 
 transition.

 What are the options?
 (1) Fix dolfin without causing another transition
 (2) Remove dolfin from testing
 (3) Upload 1.5.0-1 from experimental to unstable

 This will be the correct solution IMO. I will do that now.

Sorry for asking, but how should I upload to unstable when the package
is already in experimental. I haven't done that before.

Johannes

 Johannes

 (4) ...?

 (1) I don't know the details but it seems to me that this is not easy.

 (3) This causes another transition, but the only reverse dependencies of the
 binary packages of dolfin are python-viper (plus the meta packages fenics,
 science-mathematics and science-mathematics-dev). Rebuilding python-viper
 against dolfin 1.5.0-1 worked without problems. Maybe this additional 
 transition
 isn't that bad (apart from the delay)?

 BTW does anyone understand why dolfin does not appear in the list of
 autoremovals? The bug is release-critical and not fixed in unstable/testing,
 only experimental.

 Joachim

 --
 debian-science-maintainers mailing list
 debian-science-maintain...@lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#783899: fixed in liblog-any-perl 1.032-1

[gregor herrmann]

On Tue, 12 May 2015 10:20:45 +0200, Emilio Pozuelo Monfort wrote:

 On Fri, 01 May 2015 19:35:00 + gregor herrmann gre...@debian.org wrote:
   liblog-any-perl (1.032-1) unstable; urgency=medium
   .
 * Team upload.
   .
 * Add Breaks/Replaces/Provides on liblog-any-adapter-perl.
   liblog-any-adapter-perl was merged into liblog-any-perl.
   (Closes: #783899)
 
 Sounds like you should file a RM bug against ftp.debian.org for
 liblog-any-adapter-perl.

Thanks for the reminder, this somehow fell off of my TODO list :/

Cheers,
gregor

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#780359: Options w.r.t. libcgal11 transition

[Johannes Ring]

On Tue, May 12, 2015 at 10:29 AM, Jonathan Wiltshire j...@debian.org wrote:
 On 2015-05-12 09:07, Johannes Ring wrote:

 On Mon, May 11, 2015 at 11:35 PM, Joachim Reichel
 joachim.reic...@gmx.de wrote:

 Hi,

 dolfin is now the only reverse dependency holding up the libcgal11
 transition.

 What are the options?
 (1) Fix dolfin without causing another transition
 (2) Remove dolfin from testing
 (3) Upload 1.5.0-1 from experimental to unstable


 This will be the correct solution IMO. I will do that now.


 No, please do NOT do that now. It is the correct long-term solution, but it
 will entangle the cgal transition.

 Wait until britney has a chance to sort it out.

ok!

Johannes


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785065: vdso32 fails to built on ppc64el

[Ben Hutchings]

On Tue, 2015-05-12 at 17:21 +0100, Ben Hutchings wrote:
 On Tue, 2015-05-12 at 15:55 +0200, Matthias Klose wrote:
  that should be fixed on the kernel side by removing this code. there never 
  was a
  powerpcle userland support.
 
 I agree we have no use for this code.  Unfortunately it is currently
 non-optional.
[...]

I was able to hack out all the 32-bit vDOS along with all 32-bit
userland compatibility, but that doesn't solve the problem: a 64-bit
kernel apparently still boots in 32-bit mode.

Ben.

-- 
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison


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

Processed: open-iscsi: mark bugs pending upload, fix severity

[Debian Bug Tracking System]

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

 severity 784092 serious
Bug #784092 [open-iscsi] open-iscsi: udebs for some archs completely empty
Severity set to 'serious' from 'normal'
 tag 777602 + pending
Bug #777602 [open-iscsi] open-iscsi: Warning start and stop actions are no 
longer supported when installing
Added tag(s) pending.
 tag 784092 + pending
Bug #784092 [open-iscsi] open-iscsi: udebs for some archs completely empty
Added tag(s) pending.
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: ibus-cangjie: Many UX issues fixed upstream

[Debian Bug Tracking System]

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

 fixed 782453 2.4-1
Bug #782453 {Done: ChangZhuo Chen (陳昌倬) czc...@gmail.com} [ibus-cangjie] 
ibus-cangjie: Many UX issues fixed upstream
Marked as fixed in versions ibus-cangjie/2.4-1.
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed (with 1 errors): Change severity as package is unusable

[Debian Bug Tracking System]

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

 tags 784433 Unstable
Unknown tag/s: Unstable.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid 
help security upstream pending sarge sarge-ignore experimental d-i confirmed 
ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch etch-ignore 
lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie 
jessie-ignore stretch stretch-ignore buster buster-ignore.

 severity 784433 grave
Bug #784433 [nam] Package 'nam' needs tcl8.6 to run but depends on tcl8.5
Severity set to 'grave' from 'normal'

End of message, stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#784903: [Pkg-fglrx-devel] Bug#784903: fglrx-driver: broken depends on xorg-video-abi-18

[Patrick Matthäi]

Am 10.05.2015 um 14:18 schrieb Michael Tatge:
 Source: fglrx-driver
 Version: 1:14.9+ga14.201-2
 Severity: grave
 Justification: renders package unusable
 
 Dear Maintainer,
 
 fglrx-driver depends on xorg-video-abi-18 but xserver-xorg-core provides
 xorg-video-abi-19 thus rendering the package uninstallable.

I will check in the next days if the experimental 14.12 version is
compatible with it, but I do not think so.

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

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



signature.asc
Description: OpenPGP digital signature

Bug#785065: vdso32 fails to built on ppc64el

[Ben Hutchings]

On Tue, 2015-05-12 at 18:32 +0100, Ben Hutchings wrote:
 On Tue, 2015-05-12 at 17:21 +0100, Ben Hutchings wrote:
  On Tue, 2015-05-12 at 15:55 +0200, Matthias Klose wrote:
   that should be fixed on the kernel side by removing this code. there 
   never was a
   powerpcle userland support.
  
  I agree we have no use for this code.  Unfortunately it is currently
  non-optional.
 [...]
 
 I was able to hack out all the 32-bit vDOS along with all 32-bit
 userland compatibility, but that doesn't solve the problem: a 64-bit
 kernel apparently still boots in 32-bit mode.

If you can make gcc-4.9-powerpc-linux-gnu available on ppc64el we
*might* be able to use that.  I don't know whether it will be
installable in a buildd though.

Ben.

-- 
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison


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

Bug#784903: fglrx-driver: broken depends on xorg-video-abi-18

[cosimo morelli]

Package: fglrx-driver
Version: 1:14.9+ga14.201-2
Followup-For: Bug #784903

Dear Maintainer,

Same problem here



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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: found 782098 in 1.6.1-10

[Debian Bug Tracking System]

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

 found 782098 1.6.1-10
Bug #782098 [openexr,libopenexr-dev] openexr, libopenexr-dev: directory vs. 
symlink conflict: /usr/share/doc/{openexr, libopenexr-dev} - 
/usr/share/doc/libopenexr6
Marked as found in versions openexr/1.6.1-10.
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785150: fglrx-modules-dkms: the module fail to build with linux 4.0.0-1-amd64

[Remi Vanicat]

Package: fglrx-modules-dkms
Version: 1:14.9+ga14.201-2
Severity: grave

When building the module for linux 4.0.0-1-amd64 dkms fail with:

DKMS make.log for fglrx-14.12 for kernel 4.0.0-1-amd64 (x86_64)
mardi 12 mai 2015, 21:50:46 (UTC+0200)
make: Entering directory '/usr/src/linux-headers-4.0.0-1-amd64'
  LD  /var/lib/dkms/fglrx/14.12/build/built-in.o
  CC [M]  /var/lib/dkms/fglrx/14.12/build/firegl_public.o
/var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function 
‘kcl_mem_pat_setup’:
/var/lib/dkms/fglrx/14.12/build/firegl_public.c:4471:9: error: implicit 
declaration of function ‘read_cr4’ [-Werror=implicit-function-declaration]
 cr4 = read_cr4();
 ^
/var/lib/dkms/fglrx/14.12/build/firegl_public.c:4472:9: error: implicit 
declaration of function ‘write_cr4’ [-Werror=implicit-function-declaration]
 write_cr4(cr4  ~X86_CR4_PGE);
 ^
/var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function 
‘kasSetExecutionLevel’:
/var/lib/dkms/fglrx/14.12/build/firegl_public.c:4819:5: error: implicit 
declaration of function ‘__get_cpu_var’ [-Werror=implicit-function-declaration]
 orig_level = __get_cpu_var(kasExecutionLevel);
 ^
/var/lib/dkms/fglrx/14.12/build/firegl_public.c:4820:38: error: lvalue required 
as left operand of assignment
 __get_cpu_var(kasExecutionLevel) = level;
  ^
/var/lib/dkms/fglrx/14.12/build/firegl_public.c: At top level:
/var/lib/dkms/fglrx/14.12/build/firegl_public.c:6396:12: warning: 
‘KCL_fpu_save_init’ defined but not used [-Wunused-function]
 static int KCL_fpu_save_init(struct task_struct *tsk)
^
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.0.0-1-common/scripts/Makefile.build:263: recipe for 
target '/var/lib/dkms/fglrx/14.12/build/firegl_public.o' failed
make[3]: *** [/var/lib/dkms/fglrx/14.12/build/firegl_public.o] Error 1
/usr/src/linux-headers-4.0.0-1-common/Makefile:1407: recipe for target 
'_module_/var/lib/dkms/fglrx/14.12/build' failed
make[2]: *** [_module_/var/lib/dkms/fglrx/14.12/build] Error 2
Makefile:145: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.0.0-1-amd64'
DKMS make.log for fglrx-14.12 for kernel 4.0.0-1-amd64 (x86_64)
mardi 12 mai 2015, 21:50:46 (UTC+0200)
make: Entering directory '/usr/src/linux-headers-4.0.0-1-amd64'
  LD  /var/lib/dkms/fglrx/14.12/build/built-in.o
  CC [M]  /var/lib/dkms/fglrx/14.12/build/firegl_public.o
/var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function 
‘kcl_mem_pat_setup’:
/var/lib/dkms/fglrx/14.12/build/firegl_public.c:4471:9: error: implicit 
declaration of function ‘read_cr4’ [-Werror=implicit-function-declaration]
 cr4 = read_cr4();
 ^
/var/lib/dkms/fglrx/14.12/build/firegl_public.c:4472:9: error: implicit 
declaration of function ‘write_cr4’ [-Werror=implicit-function-declaration]
 write_cr4(cr4  ~X86_CR4_PGE);
 ^
/var/lib/dkms/fglrx/14.12/build/firegl_public.c: In function 
‘kasSetExecutionLevel’:
/var/lib/dkms/fglrx/14.12/build/firegl_public.c:4819:5: error: implicit 
declaration of function ‘__get_cpu_var’ [-Werror=implicit-function-declaration]
 orig_level = __get_cpu_var(kasExecutionLevel);
 ^
/var/lib/dkms/fglrx/14.12/build/firegl_public.c:4820:38: error: lvalue required 
as left operand of assignment
 __get_cpu_var(kasExecutionLevel) = level;
  ^
/var/lib/dkms/fglrx/14.12/build/firegl_public.c: At top level:
/var/lib/dkms/fglrx/14.12/build/firegl_public.c:6396:12: warning: 
‘KCL_fpu_save_init’ defined but not used [-Wunused-function]
 static int KCL_fpu_save_init(struct task_struct *tsk)
^
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.0.0-1-common/scripts/Makefile.build:263: recipe for 
target '/var/lib/dkms/fglrx/14.12/build/firegl_public.o' failed
make[3]: *** [/var/lib/dkms/fglrx/14.12/build/firegl_public.o] Error 1
/usr/src/linux-headers-4.0.0-1-common/Makefile:1407: recipe for target 
'_module_/var/lib/dkms/fglrx/14.12/build' failed
make[2]: *** [_module_/var/lib/dkms/fglrx/14.12/build] Error 2
Makefile:145: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.0.0-1-amd64'


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

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

Versions of packages fglrx-modules-dkms depends on:
ii  dkms  2.2.0.3-2

fglrx-modules-dkms recommends no packages.

Versions of packages fglrx-modules-dkms 

Processed: severity of 785147 is important

[Debian Bug Tracking System]

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

 severity 785147 important
Bug #785147 [initramfs-tools] initramfs-tools: NVMe boot drives not supported
Severity set to 'important' from 'critical'
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785149: grub-installer: NVMe boot drives not supported

[Steve Rowe]

Package: debian-installer
Version: 20150422
Severity: critical
Tags: d-i patch
Justification: breaks the whole system

Dear Maintainer,

I used the Jessie DVD installer on a system with an NVMe SSD add-in-card (PCIe) 
that I wanted to make bootable, but there were two problems that halted the 
process:

1. In the install-the-base-system step, the initial ram disk creation step 
failed because it couldn't translate the nvme device name (nvme0n1p3) to the 
base name (nvme0n1).
2. In the boot loader installation step, the boot loader installation script 
again couldn't translate nvme0n1p3 to nvme0n1.

I reported #1, with a patch, at 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147.

When I modified grub-installer to work with my NVMe disk, I missed the fact 
that it wasn't installed on permanent media, so I lost those changes.  The 
attached patch is my attempt at reconstructing what worked for me, so *please 
bear in mind that I have not tested it*.  One additional note: since I use the 
Linux kernel, my patch does not change the hurd_convert function, and looking 
at it, I'm guessing it should be modified too.

Steve Rowe

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

Kernel: Linux 4.0.2 (SMP w/16 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)
--- grub-installer-1.117/grub-installer	2015-01-12 23:01:14.0 -0500
+++ grub-installer-1.117/grub-installer.fixed	2015-05-12 15:13:49.002358498 -0400
@@ -134,7 +134,7 @@
 # This should probably be rewritten using udevadm or similar.
 device_to_disk () {
 	echo $1 | \
-		sed 's:\(/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
+		sed 's:\(/dev/nvme[0-9]n[0-9]\|/dev/\(cciss\|ida\|rs\)/c[0-9]d[0-9][0-9]*\|/dev/mmcblk[0-9]\|/dev/\(ad\|ada\|da\)[0-9]\+\|/dev/[hs]d[0-9]\+\|/dev/[a-z]\+\).*:\1:'
 }
 
 # Run update-grub in $ROOT
@@ -252,7 +252,7 @@
 /dev/mapper)
 	disc_offered_devfs=$bootfs
 	;;
-/dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
+/dev/nvme[0-9]n[0-9]|/dev/[hsv]d[a-z0-9]|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/ad[0-9]*|/dev/da[0-9]*)
 	disc_offered_devfs=$prefix
 	;;
 *)
@@ -895,6 +895,10 @@
 	disk=
 	part=
 	case $1 in
+/dev/nvme*n*p*)
+			disk=$(echo $1 | sed 's,\(/dev/nvme[0-9]n[0-9]\).*,\1,')
+			part=$(echo $1 | sed 's,/dev/nvme[0-9]n[0-9]\(.*\),\1,')
+			;;
 		/dev/[vhs]d[a-z]*)
 			disk=$(echo $1 | sed 's,\(/dev/[a-z]\+\).*,\1,')
 			part=$(echo $1 | sed 's,/dev/[a-z]\+\(.*\),\1,')

Bug#785147: grub-installer bug link

[Steve Rowe]

The grub-installer bug report, with patch, is here: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785149.

--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed (with 1 errors): Re: Bug#785149: grub-installer: NVMe boot drives not supported

[Debian Bug Tracking System]

Processing control commands:

 reassign -1 grub-installer
Bug #785149 [debian-installer] grub-installer: NVMe boot drives not supported
Bug reassigned from package 'debian-installer' to 'grub-installer'.
No longer marked as found in versions debian-installer/20150422.
Ignoring request to alter fixed versions of bug #785149 to the same values 
previously set
 found -1 1.85
Bug #785149 [grub-installer] grub-installer: NVMe boot drives not supported
Marked as found in versions grub-installer/1.85.
 severity important
Unknown command or malformed arguments to command.


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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785149: grub-installer: NVMe boot drives not supported

[Cyril Brulebois]

Control: reassign -1 grub-installer
Control: found -1 1.85
Control: severity important

Hi Steve,

Steve Rowe sar...@gmail.com (2015-05-12):
 Package: debian-installer
 Version: 20150422
 Severity: critical
 Tags: d-i patch
 Justification: breaks the whole system

Failing to install isn't breaking the whole system. ;)

 Dear Maintainer,
 
 I used the Jessie DVD installer on a system with an NVMe SSD add-in-card
 (PCIe) that I wanted to make bootable, but there were two problems that
 halted the process:
 
 1. In the install-the-base-system step, the initial ram disk creation step
 failed because it couldn't translate the nvme device name (nvme0n1p3) to the
 base name (nvme0n1).
 
 I reported #1, with a patch, at 
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147.

ACK, thanks.

 2. In the boot loader installation step, the boot loader installation
 script again couldn't translate nvme0n1p3 to nvme0n1.
 
 When I modified grub-installer to work with my NVMe disk, I missed the
 fact that it wasn't installed on permanent media, so I lost those
 changes.  The attached patch is my attempt at reconstructing what
 worked for me, so *please bear in mind that I have not tested it*.
 One additional note: since I use the Linux kernel, my patch does not
 change the hurd_convert function, and looking at it, I'm guessing it
 should be modified too.

I'll have a look shortly and push something. Provided the patch for
#785147 is backported to jessie, we might do that as well.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#781306: makehuman: Immediate segmentation fault at launch

[Muammar El Khatib]

Package: makehuman
Version: 1.0.0~alpha6-5+b1
Followup-For: Bug #781306

Dear John,


I have uploaded the new upstream version of makehuman to experimental. Could
you please test it and tell me if you still have this bug, please?.


Regards,


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

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

Versions of packages makehuman depends on:
ii  fontconfig2.11.0-6.3
ii  libc6 2.19-18
ii  libgl1-mesa-glx [libgl1]  10.5.5-1
ii  libglew1.10   1.10.0-3
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libpython2.7  2.7.10~rc1-1
ii  libsdl-image1.2   1.2.12-5+b5
ii  libsdl1.2debian   1.2.15-11
ii  libx11-6  2:1.6.3-1
ii  makehuman-data1.0.0~alpha6-5
pn  python2.7:any none
pn  python:anynone

Versions of packages makehuman recommends:
ii  aqsis  1.8.2-1

Versions of packages makehuman suggests:
pn  makehuman-doc  none

-- no debconf information

--
Muammar El Khatib.
http://muammar.me | http://proyectociencia.org


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785147: initramfs-tools: NVMe boot drives not supported

[Steve Rowe]

Package: initramfs-tools
Version: 0.120
Severity: critical
Tags: d-i patch
Justification: breaks the whole system

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

I used the Jessie DVD installer on a system with an NVMe SSD add-in-card (PCIe) 
that I wanted to make bootable, but there were two problems that halted the 
process:

1. In the install-the-base-system step, the initial ram disk creation step 
failed because it couldn't translate the nvme device name (nvme0n1p3) to the 
drive name (nvme0n1).  This appears to be a new naming scheme, where p[0-9] 
refers the partition number.
2. In the boot loader installation step, the grub-installer script again 
couldn't translate nvme0n1p3 to nvme0n1.

I'm making a separate bug for the grub-installer, so I'll only include the 
initramfs-tools patch here:

-
--- initramfs-tools/hook-functions  2015-03-01 16:44:34.0 -0500
+++ initramfs-tools/hook-functions.fixed2015-05-12 14:20:16.806315846 
-0400
@@ -434,6 +434,10 @@
block=${dev_node#/dev/i2o/}
block=${block%%[0-9]*}
block='i2o!'$block
+   # nvme device
+   elif [ ${dev_node#/dev/nvme} != ${dev_node} ]; then
+   block=${dev_node#/dev/}
+   block=${block%p*}
# classical block device
else
block=${dev_node#/dev/}
-

Thanks,
Steve Rowe


-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 3.6M May  8 01:52 /boot/initrd.img-3.16.0-4-amd64
-rw-r--r-- 1 root root 3.6M May 10 22:09 /boot/initrd.img-4.0.2
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.0.2 root=UUID=9954878e-5783-4f4b-bca3-55d689f221da 
ro splash

-- resume
RESUME=UUID=ab2d298a-cc4d-46f9-b9a6-6452e4c3754f
-- /proc/filesystems
ext3
ext2
ext4
fuseblk
vfat

-- lsmod
Module  Size  Used by
iptable_filter 16384  0 
ip_tables  28672  1 iptable_filter
x_tables   28672  2 ip_tables,iptable_filter
nf_nat 20480  0 
nf_conntrack   90112  1 nf_nat
bridge102400  0 
stp16384  1 bridge
llc16384  2 stp,bridge
dm_thin_pool   61440  0 
dm_persistent_data 53248  1 dm_thin_pool
dm_bio_prison  16384  1 dm_thin_pool
dm_bufio   24576  1 dm_persistent_data
libcrc32c  16384  1 dm_persistent_data
loop   28672  0 
dm_mod 94208  3 dm_persistent_data,dm_bufio,dm_thin_pool
joydev 20480  0 
hid_microsoft  16384  0 
hid_generic16384  0 
usbhid 45056  0 
hid   102400  3 hid_generic,hid_microsoft,usbhid
usb_storage57344  0 
cfg80211  446464  0 
nfsd  278528  2 
auth_rpcgss53248  1 nfsd
oid_registry   16384  1 auth_rpcgss
nfs_acl16384  1 nfsd
nfs   204800  0 
lockd  90112  2 nfs,nfsd
grace  16384  2 nfsd,lockd
fscache49152  1 nfs
sunrpc270336  6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
snd_hda_codec_hdmi 53248  1 
sg 32768  0 
sr_mod 24576  0 
cdrom  49152  1 sr_mod
sd_mod 40960  2 
snd_hda_codec_realtek69632  1 
snd_hda_codec_generic65536  1 snd_hda_codec_realtek
x86_pkg_temp_thermal16384  0 
intel_powerclamp   20480  0 
intel_rapl 20480  0 
iosf_mbi   16384  1 intel_rapl
coretemp   16384  0 
kvm   421888  0 
nls_utf8   16384  1 
nls_cp437  20480  1 
crct10dif_pclmul   16384  0 
crc32_pclmul   16384  0 
eeepc_wmi  16384  0 
crc32c_intel   24576  1 
asus_wmi   24576  1 eeepc_wmi
vfat   20480  1 
sparse_keymap  16384  1 asus_wmi
snd_hda_intel  28672  5 
fat65536  1 vfat
ahci   32768  1 
rfkill 20480  2 cfg80211,asus_wmi
ghash_clmulni_intel16384  0 
snd_hda_controller 28672  1 snd_hda_intel
libahci28672  1 ahci
xhci_pci   16384  0 
snd_hda_codec 110592  5 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
libata180224  2 ahci,libahci
video  20480  1 asus_wmi
radeon   1490944  2 
ehci_pci   16384  0 
iTCO_wdt   16384  0 
aesni_intel   167936  0 
iTCO_vendor_support16384  1 iTCO_wdt
mxm_wmi16384  0 
evdev

Bug#768687: libdata-hal-perl: FTBFS in jessie: dh_auto_test: perl Build test returned exit code 255

[Niko Tyni]

Control: retitle -1 libdata-hal-perl: FTBFS: test suite broken by newer 
liburi-namespacemap-perl versions

On Sun, Nov 09, 2014 at 08:32:51AM +0100, Lucas Nussbaum wrote:
 Source: libdata-hal-perl
 Version: 1.000-1
 Severity: serious
 Tags: jessie sid
 User: debian...@lists.debian.org
 Usertags: qa-ftbfs-20141108 qa-ftbfs
 Justification: FTBFS in jessie on amd64

  Reference bless( {_original = https://example.com/apidocs/ns/{rel}...) 
  did not pass type constraint Namespace at 
  /usr/share/perl5/URI/NamespaceMap.pm line 99
  Namespace is a subtype of InstanceOf[URI::Namespace]
  InstanceOf[URI::Namespace] requires that the reference isa 
  URI::Namespace
  The reference isa Data::HAL::URI and Moo::Object
  t/curies.t ... 
  Dubious, test returned 255 (wstat 65280, 0xff00)
  No subtests run 

Just a note that this was apparently broken by newer
liburi-namespacemap-perl versions, as discussed in

 https://rt.cpan.org/Public/Bug/Display.html?id=101827
 https://github.com/kjetilk/URI-NamespaceMap/issues/9

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#768687: libdata-hal-perl: FTBFS in jessie: dh_auto_test: perl Build test returned exit code 255

[Debian Bug Tracking System]

Processing control commands:

 retitle -1 libdata-hal-perl: FTBFS: test suite broken by newer 
 liburi-namespacemap-perl versions
Bug #768687 [src:libdata-hal-perl] libdata-hal-perl: FTBFS in jessie: 
dh_auto_test: perl Build test returned exit code 255
Changed Bug title to 'libdata-hal-perl: FTBFS: test suite broken by newer 
liburi-namespacemap-perl versions' from 'libdata-hal-perl: FTBFS in jessie: 
dh_auto_test: perl Build test returned exit code 255'

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#784215: [Pkg-swan-devel] Bug#784215: strongswan-nm: network-manager-strongswan unavailable

[Yves-Alexis Perez]

On lun., 2015-05-04 at 09:03 +0200, Robert Sander wrote:
* What led up to the situation?
 
 I am trying to use strongswan IPsec VPN through Network-Manager. The
 plugin package network-manager-strongswan is not available, but listed
 as dependency for strongswan-nm.
 
* What exactly did you do (or not do) that was effective (or
  ineffective)?
 
 I tried to install network-manager-strongswan
 
* What was the outcome of this action?
 
 root@jessie:~# apt-get install network-manager-strongswan
 Reading package lists... Done
 Building dependency tree   
 Reading state information... Done
 Package network-manager-strongswan is not available, but is referred
 to by another package.
 This may mean that the package is missing, has been obsoleted, or
 is only available from another source
 
 E: Package 'network-manager-strongswan' has no installation candidate
 
* What outcome did you expect instead?
 
 Installation of the strongswan plugin for Network-Manager.
 
 *** End of the template - remove these template lines ***

So what's the status on this now that #759826 is fixed?
-- 
Yves-Alexis


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

Bug#785158: libnet-ssleay-perl: FTBFS: Your vendor has not defined SSLeay macro LIBRESSL_VERSION_NUMBER

[Niko Tyni]

Package: libnet-ssleay-perl
Version: 1.65-1
Severity: serious
Tags: fixed-upstream sid stretch

This package fails to build on current sid and stretch
with OpenSSL = 1.0.2.

  Your vendor has not defined SSLeay macro LIBRESSL_VERSION_NUMBER at 
t/local/41_alpn_support.t line 14.
  BEGIN failed--compilation aborted at t/local/41_alpn_support.t line 16.
  t/local/41_alpn_support.t .. 
  Dubious, test returned 2 (wstat 512, 0x200)
  No subtests run 
  
  Test Summary Report
  ---
  t/local/41_alpn_support.t(Wstat: 512 Tests: 0 Failed: 0)
Non-zero exit status: 2
Parse errors: No plan found in TAP output

This seems to be fixed upstream in 1.67; from the changelog:

 Fix the ALPN test, which was incorrectly failing on OpenSSL due
 to the LibreSSL check (earlier versions bailed out before that
 line).Patch from Tom Molesworth.

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: tagging 768687, bug 768687 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=101827

[Debian Bug Tracking System]

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

 tags 768687 + upstream
Bug #768687 [src:libdata-hal-perl] libdata-hal-perl: FTBFS: test suite broken 
by newer liburi-namespacemap-perl versions
Ignoring request to alter tags of bug #768687 to the same tags previously set
 forwarded 768687 https://rt.cpan.org/Public/Bug/Display.html?id=101827
Bug #768687 [src:libdata-hal-perl] libdata-hal-perl: FTBFS: test suite broken 
by newer liburi-namespacemap-perl versions
Changed Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=101827' from 
'https://rt.cpan.org/Ticket/Display.html?id=100299'
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: severity of 785149 is important

[Debian Bug Tracking System]

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

 severity 785149 important
Bug #785149 [grub-installer] grub-installer: NVMe boot drives not supported
Severity set to 'important' from 'critical'
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#782453: marked as done (ibus-cangjie: Many UX issues fixed upstream)

[Debian Bug Tracking System]

Your message dated Tue, 12 May 2015 21:47:08 +
with message-id e1ysi16-0004e8...@franck.debian.org
and subject line Bug#782453: fixed in ibus-cangjie 2.2-2+deb8u1
has caused the Debian Bug report #782453,
regarding ibus-cangjie: Many UX issues fixed upstream
to be marked as done.

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

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


-- 
782453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: ibus-cangjie
Version: 2.2-2
Severity: normal

Dear Maintainer,

The version of ibus-cangjie in Jessie (2.2) contains many issues which were 
fixed upstream in subsequent releases.

The 2.3 release fixes:

* a serious usability issue, where we would in some cases suggest duplicate 
characters to the users:
  https://github.com/Cangjians/ibus-cangjie/issues/63
* a python traceback (in the background, not crashing the engine, but which was 
nevertheless triggering automatic crash catchers):
  https://github.com/Cangjians/ibus-cangjie/issues/57
* an incorrect translation for Taiwan users:
  https://github.com/Cangjians/ibus-cangjie/issues/61

And the 2.4 release works around another serious usability issue, where the 
candidate popup was misplaced (i.e not at the input cursor, but at the bottom 
of the screen) on some applications, most notably Firefox (which is quite the 
common app):
https://github.com/Cangjians/ibus-cangjie/issues/60

This is a leaf package, which shouldn't break anything in the distribution.

However, having ibus-cangjie up to date in Jessie would mean that Hong Kong 
people (who majoritarily input Chinese with a Cangjie input method) would have 
a great out-of-the box experience with Jessie.

Please update ibus-cangjie to 2.4 in Jessie. The best thing would be in the 
initial release, else at a release point, and else in backports.

As the upstream developer for ibus-cangjie, I'm willing to work with you to 
review differences, help backport patches, or anything else which could help.


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

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

Versions of packages ibus-cangjie depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gir1.2-ibus-1.0  1.5.9-1
ii  ibus 1.5.9-1
ii  python3  3.4.2-2
ii  python3-gi   3.14.0-1
ii  python3-pycangjie1.2-1
pn  python3:any  none

ibus-cangjie recommends no packages.

ibus-cangjie suggests no packages.

-- no debconf information
---End Message---
---BeginMessage---
Source: ibus-cangjie
Source-Version: 2.2-2+deb8u1

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

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬) czc...@gmail.com (supplier of updated ibus-cangjie 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 May 2015 18:00:01 +0800
Source: ibus-cangjie
Binary: ibus-cangjie
Architecture: source all
Version: 2.2-2+deb8u1
Distribution: stable
Urgency: medium
Maintainer: IME Packaging Team pkg-ime-de...@lists.alioth.debian.org
Changed-By: ChangZhuo Chen (陳昌倬) czc...@gmail.com
Description:
 ibus-cangjie - Cangjie and Quick input methods for IBus
Closes: 782453
Changes:
 ibus-cangjie (2.2-2+deb8u1) stable; urgency=medium
 .
   * Backport 2.4 bugfix (Closes: 782453)
 * A serious usability issue, where we would in some cases suggest
   duplicate characters to the users:
   https://github.com/Cangjians/ibus-cangjie/issues/63
 .
 * A python traceback (in the background, not crashing the engine,
   but which was nevertheless triggering automatic crash catchers):
   

Bug#784975: partclone: FTBFS on non x86 arches: error: unrecognized command line option '-m32'

[Georges Khaznadar]

Thank you for the bug report, James.

The binary file fail-mbr.bin can be built only with a (real or emulated) 
x-86 machine; however it makes sense to install it in a non-x-86 server,
since partclone can use it while restoring an x-86 client.

So, what may I do? 

I suggest to include fail-mbr.bin in the package's source, and override
the lintian error, while documenting that this file comes with its
source.

On the other hand, such a method cannot be recommended : the same
argument might be used for any arbitrary binary file, and a boot sector
can be considered as a very sensitive piece of software.

Please have you some suggestion, do you know other methods to build this
file only with *one* architecture, and declare it as available for all
architectures? This would enforce its build from sources in the debian
build farm.

The closest issue which I could imagine among debian packages is the
build system of the package firmware-free; however I could not
understand, while inspecting loosely this package, whether there were
real source files in the package and whether there is any chance to
buils any binary from source. When I try to debuild this package with an
amd64 machine, nothing is built, binaries are just copied.

Best regards,   Georges.

James Cowgill a écrit :
 Source: partclone
 Version: 0.2.78-1
 Severity: serious
 
 Hi,
 
 partclone failed to build on all non-x86 arches with this error:
 
  Making all in fail-mbr
  make[3]: Entering directory '/«PKGBUILDDIR»/fail-mbr'
  gcc -Wall -Werror -m32 -nostdlib -o fail-mbr.o fail-mbr.S
  gcc: error: unrecognized command line option '-m32'
  make[3]: *** [fail-mbr.o] Error 1
  Makefile:481: recipe for target 'fail-mbr.o' failed
  make[3]: Leaving directory '/«PKGBUILDDIR»/fail-mbr'
  make[2]: *** [all-recursive] Error 1
  Makefile:387: recipe for target 'all-recursive' failed
  make[2]: Leaving directory '/«PKGBUILDDIR»'
  make[1]: *** [all] Error 2
  dh_auto_build: make -j1 returned exit code 2
 
 Assembling fail-mbr.S with a non-x86 compiler clearly isn't going to work.
 
 Thanks,
 James



-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: Digital signature

Bug#784565: [pkg-x2go-devel] Bug#784565: nx-libs-lite: parts are derived from non-free code

[Francesco Poli]

On Tue, 12 May 2015 17:41:55 +0200 Mike Gabriel wrote:

 Hi Kevin,

Hello Mike, hello Kevin, hello to all the other recipients.

First of all, I wish to express my gratitude to Kevin for his prompt,
kind and generous response.

 
 thanks for your feedback. Let us wait for Francesco, our expert on license 
 issues, and see what he thinks about your feedback.

I think that this is an important first step to solve this issue for
the best.
Kevin Vigor is one of the copyright owners of the code that was forked
before the re-licensing.
We now know that he intended the re-licensing to be retroactive and
this is really good.

I think that now it would be useful to ascertain that the other
copyright owners (Brian Pane, Zachary Vonler, Gian Filippo Pinzari) are
also OK with this interpretation of the re-licensing operation.

Maybe Kevin is able to dig the original conversations (assuming they
were carried on by e-mail or similar archived means) or otherwise to
get in touch with them and check? Or, alternatively, Kevin could help
Mike to get in touch with them?

I hope everything may be settled for the best soon.
Thanks a lot to everyone involved.



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpIGcwCl3_ky.pgp
Description: PGP signature

Bug#785065: vdso32 fails to built on ppc64el

[Ben Hutchings]

On Tue, 2015-05-12 at 15:55 +0200, Matthias Klose wrote:
 that should be fixed on the kernel side by removing this code. there never 
 was a
 powerpcle userland support.

I agree we have no use for this code.  Unfortunately it is currently
non-optional.

 If this is not possible in the short term, then we
 can re-enable this for unstable for some time.

Please do.

Ben.

-- 
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison


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

Bug#785091: spatialite-bin: spatialite gives a Segmentation fault.

[Andy G Wood]

Hi Sebastiaan,

On Tuesday 12 May 2015 12:03:43 Sebastiaan Couwenberg wrote:
 Control: tags -1 confirmed
 
 Hi Andy,
 
 Thanks for reporting this issue. I can confirm the issue in unstable.
 
 A gdb run shows:
 
  Starting program: /usr/bin/spatialite
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
 
  Program received signal SIGSEGV, Segmentation fault.
  0x7787fff4 in spatialite_init () from
 /usr/lib/x86_64-linux-gnu/libspatialite.so.5
 
  Justification: breaks unrelated software
 
 This justification is not supported by your bugreport.
 
 Which unrelated software does this issue break?

Sorry, perhaps this is not unrelated, but 

ogr2ogr -a_srs WGS84 -f SQLite -dsco SPATIALITE=YES \
-where 'PTT=143471' -nln 143471 -append \
wcp_2015.sqlite wcp.xml

Segfaults too.

Andy.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#785091: spatialite-bin: spatialite gives a Segmentation fault.

[Debian Bug Tracking System]

Processing control commands:

 tags -1 confirmed
Bug #785091 [spatialite-bin] spatialite-bin: spatialite gives a Segmentation 
fault.
Added tag(s) confirmed.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785091: spatialite-bin: spatialite gives a Segmentation fault.

[Sebastiaan Couwenberg]

Control: tags -1 confirmed

Hi Andy,

Thanks for reporting this issue. I can confirm the issue in unstable.

A gdb run shows:

 Starting program: /usr/bin/spatialite
 [Thread debugging using libthread_db enabled]
 Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

 Program received signal SIGSEGV, Segmentation fault.
 0x7787fff4 in spatialite_init () from
/usr/lib/x86_64-linux-gnu/libspatialite.so.5

 Justification: breaks unrelated software

This justification is not supported by your bugreport.

Which unrelated software does this issue break?


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785150: fglrx-modules-dkms: Patch missing in previous report attached this report

[Michael Rasmussen]

Package: fglrx-modules-dkms
Version: 1:14.12-1
Followup-For: Bug #785150

Dear Maintainer,

Patch provided in this bug report.

-- Package-specific info:
Full fglrx package list:
ii  fglrx-atieventsd1:14.12-1  amd64  events daemon for the 
non-free ATI/AMD Rade
ii  fglrx-control   1:14.12-1  amd64  control panel for the 
non-free ATI/AMD Rade
ii  fglrx-driver1:14.12-1  amd64  non-free ATI/AMD RadeonHD 
display driver
ii  fglrx-modules-dkms  1:14.12-1  amd64  dkms module source for 
the non-free ATI/AMD
ii  libfglrx:amd64  1:14.12-1  amd64  non-free ATI/AMD RadeonHD 
display driver (r
ii  libfglrx:i386   1:14.12-1  i386   non-free ATI/AMD RadeonHD 
display driver (r
ii  libfglrx-amdxvba1:a 1:14.12-1  amd64  AMD XvBA (X-Video 
Bitstream Acceleration) r
ii  libfglrx-amdxvba1:i 1:14.12-1  i386   AMD XvBA (X-Video 
Bitstream Acceleration) r
ii  libgl1-fglrx-glx:am 1:14.12-1  amd64  proprietary libGL for the 
non-free ATI/AMD 
ii  libgl1-fglrx-glx:i3 1:14.12-1  i386   proprietary libGL for the 
non-free ATI/AMD 
ii  libgl1-fglrx-glx-i3 1:14.12-1  i386   ATI/AMD binary OpenGL 
32-bit libraries
ii  xvba-va-driver  0.8.0-9amd64  XvBA-based backend for VA 
API (AMD fglrx im

VGA-compatible devices on PCI bus:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 
[VGA controller])
Subsystem: XFX Pine Group Inc. Device [1682:304a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 46
Region 0: Memory at d000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at fe6e (64-bit, non-prefetchable) [size=128K]
Region 4: I/O ports at 8000 [size=256]
Expansion ROM at fe6c [disabled] [size=128K]
Capabilities: access denied
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 0x-0x01ff] (32MB)
[0.00] AGP: Your BIOS doesn't leave a 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)
[2.191009] PCI-DMA: Disabling AGP.
[2.191153] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
[2.219322] Linux agpgart interface v0.103
[3.814315] [drm] Initialized drm 1.1.0 20060810
[4.569522] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, 
Starnberg, GERMANY' taints kernel.
[4.600754] 6[fglrx] Maximum main memory to use for locked dma buffers: 
15674 MBytes.
[4.601016] 6[fglrx]   vendor: 1002 device: 68f9 revision: 0 count: 1
[4.601763] 6[fglrx] ioport: bar 4, base 0x8000, size: 0x100
[4.602232] 6[fglrx] Kernel PAT support is enabled
[4.602251] 6[fglrx] module loaded - fglrx 14.50.2 [Nov 20 2014] with 1 
minors
[   16.574982] 6[fglrx] Firegl kernel thread PID: 3124
[   16.575197] 6[fglrx] Firegl kernel thread PID: 3126
[   16.575336] 6[fglrx] Firegl kernel thread PID: 3127
[   16.575545] 6[fglrx] IRQ 46 Enabled
[   16.598003] 6[fglrx] Reserved FB block: Shared offset:0, size:100 
[   16.598007] 6[fglrx] Reserved FB block: Unshared offset:f7b4000, size:4000 
[   16.598009] 6[fglrx] Reserved FB block: Unshared offset:f7b8000, 
size:548000 
[   16.598011] 6[fglrx] Reserved FB block: Unshared offset:3fff3000, 
size:d000 

Xorg X server configuration file status:
-rw-r--r-- 1 root root 811 Feb 25 00:46 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
Section ServerLayout
Identifier aticonfig Layout
Screen  0  aticonfig-Screen[0]-0 0 0
EndSection

Section Files
ModulePath   /usr/lib/fglrx
ModulePath   /usr/lib/xorg/modules
ModulePath   /usr/lib/dri/
EndSection

Section Module
EndSection

Section Monitor
Identifier   aticonfig-Monitor[0]-0
Option  VendorName ATI Proprietary Driver
Option  ModelName Generic Autodetecting Monitor
Option  DPMS true
EndSection

Section Device
Identifier  aticonfig-Device[0]-0
Driver  fglrx
BusID   PCI:1:0:0
EndSection

Section Screen
Identifier aticonfig-Screen[0]-0
Device aticonfig-Device[0]-0
Monitoraticonfig-Monitor[0]-0
DefaultDepth 24
SubSection Display
Viewport   0 0
Depth 24

Bug#785158: marked as done (libnet-ssleay-perl: FTBFS: Your vendor has not defined SSLeay macro LIBRESSL_VERSION_NUMBER)

[Debian Bug Tracking System]

Your message dated Tue, 12 May 2015 21:51:21 +
with message-id e1ysi5b-0005ir...@franck.debian.org
and subject line Bug#785158: fixed in libnet-ssleay-perl 1.68-1
has caused the Debian Bug report #785158,
regarding libnet-ssleay-perl: FTBFS: Your vendor has not defined SSLeay macro 
LIBRESSL_VERSION_NUMBER
to be marked as done.

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

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


-- 
785158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libnet-ssleay-perl
Version: 1.65-1
Severity: serious
Tags: fixed-upstream sid stretch

This package fails to build on current sid and stretch
with OpenSSL = 1.0.2.

  Your vendor has not defined SSLeay macro LIBRESSL_VERSION_NUMBER at 
t/local/41_alpn_support.t line 14.
  BEGIN failed--compilation aborted at t/local/41_alpn_support.t line 16.
  t/local/41_alpn_support.t .. 
  Dubious, test returned 2 (wstat 512, 0x200)
  No subtests run 
  
  Test Summary Report
  ---
  t/local/41_alpn_support.t(Wstat: 512 Tests: 0 Failed: 0)
Non-zero exit status: 2
Parse errors: No plan found in TAP output

This seems to be fixed upstream in 1.67; from the changelog:

 Fix the ALPN test, which was incorrectly failing on OpenSSL due
 to the LibreSSL check (earlier versions bailed out before that
 line).Patch from Tom Molesworth.

-- 
Niko Tyni   nt...@debian.org
---End Message---
---BeginMessage---
Source: libnet-ssleay-perl
Source-Version: 1.68-1

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

Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated libnet-ssleay-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 12 May 2015 23:42:37 +0200
Source: libnet-ssleay-perl
Binary: libnet-ssleay-perl
Architecture: source
Version: 1.68-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org
Changed-By: gregor herrmann gre...@debian.org
Description:
 libnet-ssleay-perl - Perl module for Secure Sockets Layer (SSL)
Closes: 785158
Changes:
 libnet-ssleay-perl (1.68-1) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
 .
   [ gregor herrmann ]
   * New upstream release.
 Fixes FTBFS: Your vendor has not defined SSLeay macro
 LIBRESSL_VERSION_NUMBER
 (Closes: #785158)
   * Update upstream licensing terms.
   * Update years of packaging copyright.
   * Refresh 20no-stray-libz-link.patch (offset).
   * Declare compliance with Debian Policy 3.9.6.
   * Mark package as autopkgtest-able.
Checksums-Sha1:
 dfef5c87ab52cc583233c29a0e76402162413e3b 2411 libnet-ssleay-perl_1.68-1.dsc
 cf2fea6241e0250cbcf3e572835b2397f35944d2 384100 
libnet-ssleay-perl_1.68.orig.tar.gz
 7e65049873caada3bc8f56ab244b955d8ff7b117 9496 
libnet-ssleay-perl_1.68-1.debian.tar.xz
Checksums-Sha256:
 7dcf2d860314252c571c936918bc2059f02aeef3d195a818f65d6f114ef594ff 2411 
libnet-ssleay-perl_1.68-1.dsc
 1701e24ec683529cb114e7b7877632f2e965a81381a70b696ee0692ee1e75cd4 384100 
libnet-ssleay-perl_1.68.orig.tar.gz
 59fb60996f29a224045654e2e21c5cf8346578542f4bf799ac450ff4e4e53c08 9496 
libnet-ssleay-perl_1.68-1.debian.tar.xz
Files:
 6e54f5aff78676330b33af382073d063 2411 perl optional 
libnet-ssleay-perl_1.68-1.dsc
 2db2445eb072b6ecf8a1a79c9ed3e4de 384100 perl optional 
libnet-ssleay-perl_1.68.orig.tar.gz
 82522a280031aa7d88868f8a5b19260d 9496 perl optional 
libnet-ssleay-perl_1.68-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJVUnQJXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGlGMP/AypotfcCNmb3YzUb8yRYuVs
BsCAaIox5KE2SRQrctpuHa0Bg+VIlENcHLC+zBiGz8x0Iq1sMr5d6Qy7hgTYMCBR
Qx9mzGlcUQY8hVg0HkNM0ZeTLl45GJuR1jz1aSDgbHl67l2gPbCui7Y91t1Ac6OU
N3+Qup+SqtcVL9LtG4hW0P39VuQOUIRTrTsu0IKz4xuXBXi/jkHsKvnkFZr3OL0m

Bug#784424: marked as done (ruby-test-unit: missing dependency on power_assert gem)

[Debian Bug Tracking System]

Your message dated Tue, 12 May 2015 22:00:42 +
with message-id e1ysiee-0006kd...@franck.debian.org
and subject line Bug#784424: fixed in ruby-test-unit 3.0.9-3
has caused the Debian Bug report #784424,
regarding ruby-test-unit: missing dependency on power_assert gem
to be marked as done.

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

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


-- 
784424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: ruby-test-unit
Version: 3.0.9-2
Severity: serious

Hi,

ruby-test-unit seems to miss a dependency on power_assert:

$ ruby -e gem 'test-unit'
/usr/lib/ruby/2.1.0/rubygems/dependency.rb:298:in `to_specs': Could not find 
'power_assert' (= 0) among 15 total gem(s) (Gem::LoadError)
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1295:in `block in 
activate_dependencies'
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1284:in `each'
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1284:in 
`activate_dependencies'
from /usr/lib/ruby/2.1.0/rubygems/specification.rb:1266:in `activate'
from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_gem.rb:54:in `gem'
from -e:1:in `main'

This doesn't show up when doing:
require 'test/unit'
because of: (in /usr/lib/ruby/vendor_ruby/test/unit/assertions.rb)

begin
  require 'power_assert'
rescue LoadError, SyntaxError
end

I wonder if this should be added as a default test to all libraries?

- Lucas


-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldstable'), 
(300, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages ruby-test-unit depends on:
ii  ruby1:2.1.5
ii  ruby2.1 [ruby-interpreter]  2.1.5-2+deb8u1

ruby-test-unit recommends no packages.

ruby-test-unit suggests no packages.

-- no debconf information
---End Message---
---BeginMessage---
Source: ruby-test-unit
Source-Version: 3.0.9-3

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

Debian distribution maintenance software
pp.
Cédric Boutillier bou...@debian.org (supplier of updated ruby-test-unit 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 12 May 2015 22:25:16 +0200
Source: ruby-test-unit
Binary: ruby-test-unit
Architecture: source all
Version: 3.0.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 
pkg-ruby-extras-maintain...@lists.alioth.debian.org
Changed-By: Cédric Boutillier bou...@debian.org
Description:
 ruby-test-unit - Improved version of Test::Unit library initially bundled in 
Ruby
Closes: 784424
Changes:
 ruby-test-unit (3.0.9-3) unstable; urgency=medium
 .
   * Depend on ruby-power-assert, to make rubygems happy (Closes: #784424)
Checksums-Sha1:
 b55a746d5b411bc59295603d78a3324b32e811f5 1725 ruby-test-unit_3.0.9-3.dsc
 0b017e015fe70e9b438e844dd9b01fa3de86d9c6 5496 
ruby-test-unit_3.0.9-3.debian.tar.xz
 b3ee222b7b43511a83192dbe39fd783776208b56 59876 ruby-test-unit_3.0.9-3_all.deb
Checksums-Sha256:
 443b0a8397ab2b2063487cbba4fa51ce5c56c27779fa25fce91a57ffb20bd2a1 1725 
ruby-test-unit_3.0.9-3.dsc
 0c960c6ab40f6548ed4ce71d09eae2500e37f8e7f6f2a4663526c3f2d9cf654e 5496 
ruby-test-unit_3.0.9-3.debian.tar.xz
 52dd23b82656feb3b40cd7a164adb564b825696a366fd30b858be2a482cb5263 59876 
ruby-test-unit_3.0.9-3_all.deb
Files:
 f35de73bf3cb4eccbad4e9812e2fd314 1725 ruby optional ruby-test-unit_3.0.9-3.dsc
 15b9d51d0c7cb217229d78e23e7b0019 5496 ruby optional 
ruby-test-unit_3.0.9-3.debian.tar.xz
 0005239d831fd3eb640c849090eb5fe2 59876 ruby optional 
ruby-test-unit_3.0.9-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJVUmTxAAoJEImvgrc5zSF6N6UH/iZok/N9dcaZj7r1tiRGZkUV

Bug#780359: Options w.r.t. libcgal11 transition

[Jonathan Wiltshire]

On 2015-05-12 09:30, Johannes Ring wrote:
On Tue, May 12, 2015 at 10:29 AM, Jonathan Wiltshire j...@debian.org 
wrote:

On 2015-05-12 09:07, Johannes Ring wrote:


On Mon, May 11, 2015 at 11:35 PM, Joachim Reichel
joachim.reic...@gmx.de wrote:


Hi,

dolfin is now the only reverse dependency holding up the libcgal11
transition.

What are the options?
(1) Fix dolfin without causing another transition
(2) Remove dolfin from testing
(3) Upload 1.5.0-1 from experimental to unstable



This will be the correct solution IMO. I will do that now.



No, please do NOT do that now. It is the correct long-term solution, 
but it

will entangle the cgal transition.

Wait until britney has a chance to sort it out.


ok!


Ok, please go ahead now. To upload to unstable from experimental, just 
add a changelog entry with Upload to unstable and an incremented 
version.


Your only r-dep is fenics, which appears to be arch:all and ships an 
empty package, so I don't know what all that's about...



--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

directhex i have six years of solaris sysadmin experience, from
8-10. i am well qualified to say it is made from bonghits
layered on top of bonghits


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785150: fglrx-modules-dkms: Patch to fix build

[Michael Rasmussen]

Package: fglrx-modules-dkms
Version: 1:14.12-1
Followup-For: Bug #785150

Dear Maintainer,

Attached you will find a patch which solves this bug.

-- Package-specific info:
Full fglrx package list:
ii  fglrx-atieventsd1:14.12-1  amd64  events daemon for the 
non-free ATI/AMD Rade
ii  fglrx-control   1:14.12-1  amd64  control panel for the 
non-free ATI/AMD Rade
ii  fglrx-driver1:14.12-1  amd64  non-free ATI/AMD RadeonHD 
display driver
ii  fglrx-modules-dkms  1:14.12-1  amd64  dkms module source for 
the non-free ATI/AMD
ii  libfglrx:amd64  1:14.12-1  amd64  non-free ATI/AMD RadeonHD 
display driver (r
ii  libfglrx:i386   1:14.12-1  i386   non-free ATI/AMD RadeonHD 
display driver (r
ii  libfglrx-amdxvba1:a 1:14.12-1  amd64  AMD XvBA (X-Video 
Bitstream Acceleration) r
ii  libfglrx-amdxvba1:i 1:14.12-1  i386   AMD XvBA (X-Video 
Bitstream Acceleration) r
ii  libgl1-fglrx-glx:am 1:14.12-1  amd64  proprietary libGL for the 
non-free ATI/AMD 
ii  libgl1-fglrx-glx:i3 1:14.12-1  i386   proprietary libGL for the 
non-free ATI/AMD 
ii  libgl1-fglrx-glx-i3 1:14.12-1  i386   ATI/AMD binary OpenGL 
32-bit libraries
ii  xvba-va-driver  0.8.0-9amd64  XvBA-based backend for VA 
API (AMD fglrx im

VGA-compatible devices on PCI bus:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 
[VGA controller])
Subsystem: XFX Pine Group Inc. Device [1682:304a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 46
Region 0: Memory at d000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at fe6e (64-bit, non-prefetchable) [size=128K]
Region 4: I/O ports at 8000 [size=256]
Expansion ROM at fe6c [disabled] [size=128K]
Capabilities: access denied
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 0x-0x01ff] (32MB)
[0.00] AGP: Your BIOS doesn't leave a 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)
[2.191009] PCI-DMA: Disabling AGP.
[2.191153] PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
[2.219322] Linux agpgart interface v0.103
[3.814315] [drm] Initialized drm 1.1.0 20060810
[4.569522] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, 
Starnberg, GERMANY' taints kernel.
[4.600754] 6[fglrx] Maximum main memory to use for locked dma buffers: 
15674 MBytes.
[4.601016] 6[fglrx]   vendor: 1002 device: 68f9 revision: 0 count: 1
[4.601763] 6[fglrx] ioport: bar 4, base 0x8000, size: 0x100
[4.602232] 6[fglrx] Kernel PAT support is enabled
[4.602251] 6[fglrx] module loaded - fglrx 14.50.2 [Nov 20 2014] with 1 
minors
[   16.574982] 6[fglrx] Firegl kernel thread PID: 3124
[   16.575197] 6[fglrx] Firegl kernel thread PID: 3126
[   16.575336] 6[fglrx] Firegl kernel thread PID: 3127
[   16.575545] 6[fglrx] IRQ 46 Enabled
[   16.598003] 6[fglrx] Reserved FB block: Shared offset:0, size:100 
[   16.598007] 6[fglrx] Reserved FB block: Unshared offset:f7b4000, size:4000 
[   16.598009] 6[fglrx] Reserved FB block: Unshared offset:f7b8000, 
size:548000 
[   16.598011] 6[fglrx] Reserved FB block: Unshared offset:3fff3000, 
size:d000 

Xorg X server configuration file status:
-rw-r--r-- 1 root root 811 Feb 25 00:46 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
Section ServerLayout
Identifier aticonfig Layout
Screen  0  aticonfig-Screen[0]-0 0 0
EndSection

Section Files
ModulePath   /usr/lib/fglrx
ModulePath   /usr/lib/xorg/modules
ModulePath   /usr/lib/dri/
EndSection

Section Module
EndSection

Section Monitor
Identifier   aticonfig-Monitor[0]-0
Option  VendorName ATI Proprietary Driver
Option  ModelName Generic Autodetecting Monitor
Option  DPMS true
EndSection

Section Device
Identifier  aticonfig-Device[0]-0
Driver  fglrx
BusID   PCI:1:0:0
EndSection

Section Screen
Identifier aticonfig-Screen[0]-0
Device aticonfig-Device[0]-0
Monitoraticonfig-Monitor[0]-0
DefaultDepth 24
SubSection Display
Viewport   0 0

Bug#785091: spatialite-bin: spatialite gives a Segmentation fault.

[Sebastiaan Couwenberg]

Hi Andy,

On 05/12/2015 01:13 PM, Andy G Wood wrote:
 On Tuesday 12 May 2015 12:03:43 Sebastiaan Couwenberg wrote:
 Justification: breaks unrelated software

 This justification is not supported by your bugreport.

 Which unrelated software does this issue break?
 
 Sorry, perhaps this is not unrelated, but 
 
 ogr2ogr -a_srs WGS84 -f SQLite -dsco SPATIALITE=YES \
 -where 'PTT=143471' -nln 143471 -append \
 wcp_2015.sqlite wcp.xml
 
 Segfaults too.

Thanks for the clarification.

I've got slightly more informative gdb output with the spatialite debug
symbols:

(gdb) run
Starting program: /usr/bin/spatialite
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

Program received signal SIGSEGV, Segmentation fault.
0x7787fff4 in spatialite_init (verbose=1) at spatialite_init.c:114
114 sqlite3_auto_extension ((void (*)(void))
init_spatialite_extension);
(gdb) list
109
110 #ifndef OMIT_GEOS   /* initializing GEOS */
111 initGEOS (geos_warning, geos_error);
112 #endif /* end GEOS  */
113
114 sqlite3_auto_extension ((void (*)(void))
init_spatialite_extension);
115 spatialite_splash_screen (verbose);
116 }
117
118 SPATIALITE_DECLARE void

I'll try spatialite 4.2.x in experimenal to see if that also breaks now.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#782729: marked as done (haskell-mode: haskell-yas.el can't be byte-compiled if yasnippet is present)

[Debian Bug Tracking System]

Your message dated Tue, 12 May 2015 11:48:50 +
with message-id e1ys8g6-0004ky...@franck.debian.org
and subject line Bug#782729: fixed in haskell-mode 13.12-2
has caused the Debian Bug report #782729,
regarding haskell-mode: haskell-yas.el can't be byte-compiled if yasnippet is 
present
to be marked as done.

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

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


-- 
782729: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: haskell-mode
Version: 13.12-1
Severity: grave

How to reproduce:

- Install emacs24 and yasnippet 0.6.1c-1
- Install haskell-mode 13.12-1

haskell-yas.el seems to rely on a newer yasnippet version (0.8.0 is
available, see #691385). For details, see below. Adding Breaks:
yasnippet ( 0.80) should fix this.

(Installing haskell-mode on top of a locally-built yasnippet 0.8.0
pacakge failed here because the snippets/ directory is not installed at
all, but that's a different issue.)

Cheers,
-Hilko

Selecting previously unselected package haskell-mode.
(Reading database ... 678278 files and directories currently installed.)
Preparing to unpack .../haskell-mode_13.12-1_all.deb ...
Unpacking haskell-mode (13.12-1) ...
Setting up haskell-mode (13.12-1) ...
Install haskell-mode for emacs24
install/haskell-mode: Handling install for emacsen flavor emacs24
Loading 00debian-vars...
Loading /etc/emacs/site-start.d/20apel.el (source)...
Loading /etc/emacs/site-start.d/50a2ps.el (source)...
Loading /etc/emacs/site-start.d/50anything-el.el (source)...
Loading /etc/emacs/site-start.d/50auto-complete-el.el (source)...
Loading /etc/emacs/site-start.d/50auto-install-el.el (source)...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading /etc/emacs/site-start.d/50bashdb.el (source)...
Loading /etc/emacs/site-start.d/50bbdb3.el (source)...
Loading /etc/emacs/site-start.d/50cmake-data.el (source)...
Loading /etc/emacs/site-start.d/50coccinelle.el (source)...
Loading /etc/emacs/site-start.d/50commit-patch.el (source)...
Loading /etc/emacs/site-start.d/50crypt++el.el (source)...
Loading /etc/emacs/site-start.d/50cxref-emacs.el (source)...
Loading /etc/emacs/site-start.d/50dash-el.el (source)...
Loading /etc/emacs/site-start.d/50develock-el.el (source)...
Loading /etc/emacs/site-start.d/50devhelp.el (source)...
Loading /etc/emacs/site-start.d/50devscripts-el.el (source)...
Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...
Info: Skip debian-el loading if run under dpkg control.
Loading /etc/emacs/site-start.d/50doxymacs.el (source)...
Loading /etc/emacs/site-start.d/50dpkg-dev-el.el (source)...
Loading /etc/emacs/site-start.d/50ecasound-el.el (source)...
Loading /etc/emacs/site-start.d/50edb.el (source)...
Loading /etc/emacs/site-start.d/50el-get.el (source)...
Loading /etc/emacs/site-start.d/50eldav.el (source)...
Loading /etc/emacs/site-start.d/50elserv.el (source)...
Loading /etc/emacs/site-start.d/50emacs-goodies-el.el (source)...
Loading /etc/emacs/site-start.d/50emacs-intl-fonts.el (source)...
Loading /etc/emacs/site-start.d/50emacs-window-layout.el (source)...
Loading /etc/emacs/site-start.d/50erlang-mode.el (source)...
Loading /etc/emacs/site-start.d/50ess.el (source)...
Loading /etc/emacs/site-start.d/50evernote-mode.el (source)...
Loading /etc/emacs/site-start.d/50expand-region-el.el (source)...
Real cl-lib shadowed by compatibility cl-lib? 
(/usr/share/emacs/24.4/site-lisp/slime/lib/cl-lib.elc)
cl-declare already defined, not rebinding
cl-dotimes already defined, not rebinding
cl-dolist already defined, not rebinding
cl-dolist already defined, not rebinding
cl-dotimes already defined, not rebinding
Loading /etc/emacs/site-start.d/50flim.el (source)...
Loading /etc/emacs/site-start.d/50geiser.el (source)...
Loading /etc/emacs/site-start.d/50gettext.el (source)...
Loading /etc/emacs/site-start.d/50git-core.el (source)...
Loading /etc/emacs/site-start.d/50gnu-smalltalk-el.el (source)...
Error while loading 50gnu-smalltalk-el: Symbol's value as variable is void: 
inhibit-first-line-modes-regexps
Loading /etc/emacs/site-start.d/50gnuplot-mode.el (source)...
Loading /etc/emacs/site-start.d/50goby.el (source)...
Loading /etc/emacs/site-start.d/50gocode-auto-complete-el.el (source)...
Loading /etc/emacs/site-start.d/50golang-mode.el (source)...
Loading /etc/emacs/site-start.d/50gtk-doc-tools.el (source)...
Loading /etc/emacs/site-start.d/50haml-elisp.el (source)...
Loading /etc/emacs/site-start.d/50haskell-mode.el (source)...
Loading /usr/share/emacs24/site-lisp/haskell-mode/haskell-mode-autoloads.el 
(source)...
Loading 

Processed: tagging 784972, reassign 784972 to plasma-nm

[Debian Bug Tracking System]

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

 tags 784972 + confirmed
Bug #784972 [network-manager-openconnect] network-manager-openconnect does not 
ask for username/password
Added tag(s) confirmed.
 reassign 784972 plasma-nm 0.9.3.4-2
Bug #784972 [network-manager-openconnect] network-manager-openconnect does not 
ask for username/password
Bug reassigned from package 'network-manager-openconnect' to 'plasma-nm'.
No longer marked as found in versions network-manager-openconnect/0.9.10.0-1.
Ignoring request to alter fixed versions of bug #784972 to the same values 
previously set
Bug #784972 [plasma-nm] network-manager-openconnect does not ask for 
username/password
Marked as found in versions plasma-nm/0.9.3.4-2.
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#784115: inn: incoming feed is garbled

[Marco d'Itri]

On May 10, Marco d'Itri m...@linux.it wrote:

 What would really help is if you could test some of the older packages 
 to find out which one introduced this regression:
 http://snapshot.debian.org/package/inn/
BTW, you can just replace on the fly the innd binary: there is no need 
to downgrade/reinstall the package.

-- 
ciao,
Marco


pgpGIVp8JwZw2.pgp
Description: PGP signature

Bug#785108: gnome-sound-recorder: your audio capture settings are invalid

[jmullee]

Package: gnome-sound-recorder
Version: 3.14.0.1-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

your audio capture settings are invalid

No options available to change audio settings.


line 75:
https://git.gnome.org/browse/gnome-sound-recorder/tree/src/record.js

this.srcElement = Gst.ElementFactory.make(pulsesrc, srcElement);
if(this.srcElement == null) {
  this._showErrorDialog(_(Your audio capture settings are invalid.));

I remember Windows 3.1 back in 1990 had a working sound recorder.
It could even replay backwards.
A quarter century later, this is the cutting edge: completely useless.



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

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

Versions of packages gnome-sound-recorder depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gir1.2-gdkpixbuf-2.0 2.31.1-2+b1
ii  gir1.2-glib-2.0  1.42.0-2.2
ii  gir1.2-gst-plugins-base-1.0  1.4.4-2
ii  gir1.2-gstreamer-1.0 1.4.4-2
ii  gir1.2-gtk-3.0   3.14.5-1
ii  gir1.2-pango-1.0 1.36.8-3
ii  gjs  1.42.0-1
ii  gstreamer1.0-plugins-bad 1.4.4-2.1+b1
ii  gstreamer1.0-plugins-base1.4.4-2
ii  gstreamer1.0-plugins-good1.4.4-2

gnome-sound-recorder recommends no packages.

gnome-sound-recorder suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: cdebootstrap: Please support stretch/testing

[Debian Bug Tracking System]

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

 severity 783672 grave
Bug #783672 [cdebootstrap] cdebootstrap: Please support stretch/testing
Severity set to 'grave' from 'important'
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785065: vdso32 fails to built on ppc64el

[Matthias Klose]

that should be fixed on the kernel side by removing this code. there never was a
powerpcle userland support. If this is not possible in the short term, then we
can re-enable this for unstable for some time.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785122: chocolate-doom: includes licence-incompatible GPLv3 code

[Jonathan Dowland]

Package: chocolate-doom
Version: 2.1.0-1
Severity: serious
Justification: license issue

Chocolate-doom includes code taken from GnuPG, which is GPLv3, whereas
chocolate-doom is GPLv2 (or later). Upstream have fixed this by replacing
the AES implementation with one from the kernel. See

https://github.com/chocolate-doom/chocolate-doom/commit/b3678129fd7bed6c3287ab682819b075e8bf495a

For ref, the first commit introducing this code is

commit a3b3e15f4eed9aaffc56be69784cd7447cf456de
Author: Simon Howard frag...@gmail.com
Date:   Sat Oct 27 06:10:50 2012 +

The first released version to include that commit is 2.0.0, meaning
only jessie and onwards are impacted.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785091: spatialite-bin: spatialite gives a Segmentation fault.

[Andy Wood]

Package: spatialite-bin
Version: 4.1.1-4+b1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

   * What led up to the situation?

Recent testing update.

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

Simply type the command `spatialite`

   * What was the outcome of this action?

Segfault


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

Kernel: Linux 3.16.0-4-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 spatialite-bin depends on:
ii  libc6   2.19-18
ii  libexpat1   2.1.0-6+b3
ii  libfreexl1  1.0.1-2
ii  libgeos-c1  3.4.2-7
ii  libproj94.9.1-1
ii  libreadline66.3-8+b3
ii  libreadosm1 1.0.0d-1
ii  libspatialite5  4.1.1-10+b1
ii  libsqlite3-03.8.9-2
ii  zlib1g  1:1.2.8.dfsg-2+b1

spatialite-bin recommends no packages.

spatialite-bin suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: tagging 785000

[Debian Bug Tracking System]

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

 tags 785000 + pending
Bug #785000 [src:libwebp] libwebp: FTBFS on mips: Error: opcode not supported 
on this processor: mips2...
Added tag(s) pending.
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785000: marked as done (libwebp: FTBFS on mips: Error: opcode not supported on this processor: mips2...)

[Debian Bug Tracking System]

Your message dated Wed, 13 May 2015 04:49:20 +
with message-id e1ysobg-0005ju...@franck.debian.org
and subject line Bug#785000: fixed in libwebp 0.4.3-1.3
has caused the Debian Bug report #785000,
regarding libwebp: FTBFS on mips: Error: opcode not supported on this 
processor: mips2...
to be marked as done.

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

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


-- 
785000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: libwebp
Version: 0.4.3-1
Severity: serious
Tags: patch

Hi,

libwebp FTBFS on mips with this error (initially):

 libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src/webp 
 -D_FORTIFY_SOURCE=2 -Wall -Wdeclaration-after-statement -Wextra 
 -Wmissing-declarations -Wmissing-prototypes -Wold-style-definition -Wshadow 
 -Wunused-but-set-variable -Wunused -Wvla -g -O2 -fstack-protector-strong 
 -Wformat -Werror=format-security -pthread -c lossless_mips32.c  -fPIC -DPIC 
 -o .libs/libwebpdsp_la-lossless_mips32.o
 /tmp/cc07vjZt.s: Assembler messages:
 /tmp/cc07vjZt.s:52: Error: opcode not supported on this processor: mips2 
 (mips2) `madd $6,$5'
 /tmp/cc07vjZt.s:53: Error: opcode not supported on this processor: mips2 
 (mips2) `madd $6,$4'
 /tmp/cc07vjZt.s:140: Error: opcode not supported on this processor: mips2 
 (mips2) `madd $9,$3'
 /tmp/cc07vjZt.s:141: Error: opcode not supported on this processor: mips2 
 (mips2) `madd $9,$7'
 /tmp/cc07vjZt.s:1328: Error: opcode not supported on this processor: mips2 
 (mips2) `clz $6,$4'
 /tmp/cc07vjZt.s:1545: Error: opcode not supported on this processor: mips2 
 (mips2) `clz $6,$4'
 make[3]: *** [libwebpdsp_la-lossless_mips32.lo] Error 1

There was a patch 'fix-mips2.patch' to fix this but it was dropped in
the 0.4.3-1 upload.

I've attached an updated patch which fixes this.

Thanks,
James
--- a/src/dsp/dsp.h
+++ b/src/dsp/dsp.h
@@ -73,7 +73,7 @@ extern C {
 #define WEBP_USE_NEON
 #endif
 
-#if defined(__mips__)  !defined(__mips64)  (__mips_isa_rev  6)
+#if defined(__mips__)  !defined(__mips64)  (__mips_isa_rev = 1)  (__mips_isa_rev  6)
 #define WEBP_USE_MIPS32
 #if (__mips_isa_rev = 2)
 #define WEBP_USE_MIPS32_R2


signature.asc
Description: This is a digitally signed message part
---End Message---
---BeginMessage---
Source: libwebp
Source-Version: 0.4.3-1.3

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

Debian distribution maintenance software
pp.
Dmitry Smirnov only...@debian.org (supplier of updated libwebp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 13 May 2015 14:19:01 +1000
Source: libwebp
Binary: libwebp-dev libwebp5 libwebpmux1 libwebpdemux1 webp
Architecture: source amd64
Version: 0.4.3-1.3
Distribution: unstable
Urgency: high
Maintainer: Jeff Breidenbach j...@debian.org
Changed-By: Dmitry Smirnov only...@debian.org
Description:
 libwebp-dev - Lossy compression of digital photographic images.
 libwebp5   - Lossy compression of digital photographic images.
 libwebpdemux1 - Lossy compression of digital photographic images.
 libwebpmux1 - Lossy compression of digital photographic images.
 webp   - Lossy compression of digital photographic images.
Closes: 785000
Changes:
 libwebp (0.4.3-1.3) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Re-introduced refreshed fix-mips32.patch to fix FTBFS on mips(el).
 Thanks, James Cowgill. (Closes: #785000).
   * Added retrospective changelog entry to note removal of fix-mips32.patch.
Checksums-Sha1:
 a05bde0459e2ba6f50790be550f8a3a64b5cc680 2085 libwebp_0.4.3-1.3.dsc
 ff83b4a7851b0204cf3134530ca87de78f761bb6 7108 libwebp_0.4.3-1.3.debian.tar.xz
 046ab4a13561dd7e3f6c65a6bf35eef17dd24314 269336 libwebp-dev_0.4.3-1.3_amd64.deb
 57ba9adb8f66b1a13fb257bdda036d9591cc2bfa 210278 libwebp5_0.4.3-1.3_amd64.deb
 c5617bd90ec268b732021df36368a0a21b99303a 59848 libwebpmux1_0.4.3-1.3_amd64.deb
 2af57bad0040d268ec471a82551feb9863b5d937 53102 
libwebpdemux1_0.4.3-1.3_amd64.deb
 721862a78eda9c6ef6ea4fd05adf2c089108b0c7 106274 webp_0.4.3-1.3_amd64.deb

Processed: Patch for unittest-cpp

[Debian Bug Tracking System]

Processing control commands:

 severity -1 serious
Bug #784665 [unittest++] Package is too outdated
Severity set to 'serious' from 'normal'

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#785122: chocolate-doom: includes licence-incompatible GPLv3 code

[Fabian Greffrath]

Hi Jon,

Am Dienstag, den 12.05.2015, 14:17 +0100 schrieb Jonathan Dowland: 
 Chocolate-doom includes code taken from GnuPG, which is GPLv3, whereas
 chocolate-doom is GPLv2 (or later). Upstream have fixed this by replacing
 the AES implementation with one from the kernel. See

doesn't mixing GPlv2-or-later code with GPLv3 code result in code that
is GPLv3 only? I fail to see why this would be of RC severity. I mean,
there is no GPLv2-only code involved.

 https://github.com/chocolate-doom/chocolate-doom/commit/b3678129fd7bed6c3287ab682819b075e8bf495a

I have seen this commit but decided to wait for the GPLv3 licensed sha1
implementation to get replaced as well before I take action on the
Debian package.

Cheers,

Fabian



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

Bug#784565: [pkg-x2go-devel] Bug#784565: nx-libs-lite: parts are derived from non-free code

[Kevin Vigor]

Hi Mike, et al,

   I am not the original author of dxpc, that being Brian Pane. However, I took 
over maintenance circa 1999 and am still the primary maintainer (though the 
project has effectively been dead for most of a decade now).

   As you are aware, when I inherited the code, it was licensed under a variant 
of the BSD license that did not include the 'with modification' clause. To the 
best of my recollection, somebody from the FSF contacted me circa 2001 
regarding this and as a result, subsequent releases were done under a standard 
2-clause BSD license with the modification clause. Again, to the best of my 
recollection, I contacted Brian about this change and he offered no objection.

   Further, I recall distinctly that NoMachine contacted me and explicitly 
asked permission before including DXPC code in NX, which I happily granted with 
no new conditions beyond the BSD license already in play.

   It is possible, though by no means certain, that I could dig up ancient 
email to corroborate this account if necessary. However, I am more than willing 
to publicly state that I believe NoMachine's use of DXPC code to be both legal 
and ethical, and that my intent when changing the license to 2-clause BSD was 
simply to clarity the existing intent and that it ought therefore be considered 
retroactive.

   Yours,
  Kevin Vigor

On 05/11/15 22:46, Mike Gabriel wrote:

Dear Kevin,

(I Cc: several people involved in this, also the X2Go development mailing 
list...)

[If you feel unconfortable with discussing the details / the impact of the 
below in public, feel free to answer to me directly first with questions and 
concerns, before answering to all people who are listed in Cc:.]

Someone from the Debian legal team recently brought up a license issue 
discovered in nx-libs 3.x series.

TL;DR; Suggested by Francesco Poli from the Debian legal team: 
(A) someone gets in touch with DXPC copyright owners and asks them
whether the re-licensing [in 2002] may be considered retroactive (applicable to
older versions of DXPC); in case the answer is negative, DXPC copyright
owners should be persuaded to make the re-licensing retroactive


The person contacting you about the above question is me. Mike Gabriel, Debian Developer 
and one of the current upstream maintainers of nx-libs 3.x (previously also know as  
NX redistributed for X2Go) [1].

This issue requires some time of reading from you and (hopefully) a public 
statement, that the original DXPC code can be considered as BSD-2-clause (the 
current license) also for released versions prior 2002 when the ancient BSD 
license template [2] was still shipped with DXPC.

For a complete follow-up, please check Debian bug #784565 [3].

We are aware that NoMachine forked DXPC at some early stage around the year 
2000 and wrote their own commercial product around it. Obviously, this fork 
happened before 2002 (i.e., before DXPC release 3.8.1), as libxcomp3 in 
NoMachine's NX ships the previously used BSD license template. I am not sure, 
if that fork was easy for you or actually a nuisance. I may only guess at this 
point. I'd be happy to know more (maybe not in this mail thread, though).

NoMachine has stopped publishing NXv3 updates a couple of years ago (2011 IIRC), now. The maintenance has 
been moved into the hands of the currently available FLOSS projects X2Go, Arctica 
Project [NEW] and TheQVD. Some of us are running a business model on top of that 
(consultancy, support contracts, feature development contracts), some of us spend a lot of their free time on 
improving / maintaining nx-libs (as we call NoMachine's NXv3 at the moment).

To outline the impact of my mail clearly: If you say that it was not legal by 
NoMachine to fork DXPC at the given time (before 2002), then all FLOSS remote 
desktop / remote application would be in real trouble, because then the core 
component of their software projects could not be considered as free (as in 
DFSG, Debian free software guidelines[4]) anymore. Also the code changes 
originally performed by NoMachine might have been illegal in the first place. 
All current maintenance activities and also planned future development on 
nx-libs would become questionable.

Thus, I hope you can chime in on this: Dear developers of nx-libs, please 
assume the BSD-2-license as retroactive and applicable to DXPC version earlier 
than 3.8.1. As the copyright holder, I agree with modifications of code bases 
that originate before the change to BSD-2-clause license got introduced in 
3.8.1 of DXPC.

And... I will bring up that question later (but it is burning under my 
nails)... Be sure: The nx-libs maintainers would be happy to have the original 
DXPC author on the nx-libs developer team. But I will bring up that question 
later (when this very issue is settled). ;-)

Greets,
Mike

[1] https://github.com/ArcticaProject/nx-libs
[2] http://en.wikipedia.org/wiki/BSD_licenses#Previous_license
[3] http://bugs.debian.org/784565
[4] 

Processed: reassign 785122 to src:chocolate-doom

[Debian Bug Tracking System]

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

 reassign 785122 src:chocolate-doom 2.1.0-1
Bug #785122 [chocolate-doom] chocolate-doom: includes licence-incompatible 
GPLv3 code
Bug reassigned from package 'chocolate-doom' to 'src:chocolate-doom'.
No longer marked as found in versions chocolate-doom/2.1.0-1.
Ignoring request to alter fixed versions of bug #785122 to the same values 
previously set
Bug #785122 [src:chocolate-doom] chocolate-doom: includes licence-incompatible 
GPLv3 code
Marked as found in versions chocolate-doom/2.1.0-1.
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: submitter 785122

[Debian Bug Tracking System]

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

 submitter 785122 Jonathan Dowland j...@debian.org
Bug #785122 [chocolate-doom] chocolate-doom: includes licence-incompatible 
GPLv3 code
Changed Bug submitter to 'Jonathan Dowland j...@debian.org' from 'Jonathan 
Dowland j...@dowland.me'
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

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

 retitle 784665 unittest++: please update the package to a newer version
Bug #784665 [unittest++] Package is too outdated
Changed Bug title to 'unittest++: please update the package to a newer version' 
from 'Package is too outdated'
 severity 784665 wishlist
Bug #784665 [unittest++] unittest++: please update the package to a newer 
version
Severity set to 'wishlist' from 'serious'
 thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#784565: [pkg-x2go-devel] Bug#784565: nx-libs-lite: parts are derived from non-free code

[Mike Gabriel]

Hi Kevin,

thanks for your feedback. Let us wait for Francesco, our expert on license 
issues, and see what he thinks about your feedback.

Thank you very much for providing info and sharing pieces of nx-libs's history.

As you sent your reply to the Debian bug tracker already, this will public 
statement enough, I guess.

Thanks a lot,
Mike

-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976148

GnuPG Key ID 0x25771B13
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de


- Original message -
 Hi Mike, et al,
 
         I am not the original author of dxpc, that being Brian Pane.
 However, I took over maintenance circa 1999 and am still the primary
 maintainer (though the project has effectively been dead for most of a
 decade now).
 
         As you are aware, when I inherited the code, it was licensed under a
 variant of the BSD license that did not include the 'with modification'
 clause. To the best of my recollection, somebody from the FSF contacted
 me circa 2001 regarding this and as a result, subsequent releases were
 done under a standard 2-clause BSD license with the modification clause.
 Again, to the best of my recollection, I contacted Brian about this
 change and he offered no objection.
 
         Further, I recall distinctly that NoMachine contacted me and
 explicitly asked permission before including DXPC code in NX, which I
 happily granted with no new conditions beyond the BSD license already in
 play.
 
         It is possible, though by no means certain, that I could dig up
 ancient email to corroborate this account if necessary. However, I am
 more than willing to publicly state that I believe NoMachine's use of
 DXPC code to be both legal and ethical, and that my intent when changing
 the license to 2-clause BSD was simply to clarity the existing intent
 and that it ought therefore be considered retroactive.
 
         Yours,
               Kevin Vigor
 
 On 05/11/15 22:46, Mike Gabriel wrote:
  Dear Kevin,
  
  (I Cc: several people involved in this, also the X2Go development
  mailing list...)
  
  [If you feel unconfortable with discussing the details / the impact of
  the below in public, feel free to answer to me directly first with
  questions and concerns, before answering to all people who are listed
  in Cc:.]
  
  Someone from the Debian legal team recently brought up a license issue
  discovered in nx-libs 3.x series.
  
  TL;DR; Suggested by Francesco Poli from the Debian legal team: 
  (A) someone gets in touch with DXPC copyright owners and asks them
  whether the re-licensing [in 2002] may be considered retroactive
  (applicable to older versions of DXPC); in case the answer is
  negative, DXPC copyright owners should be persuaded to make the
  re-licensing retroactive 
  
  The person contacting you about the above question is me. Mike
  Gabriel, Debian Developer and one of the current upstream maintainers
  of nx-libs 3.x (previously also know as   NX redistributed for X2Go)
  [1].
  
  This issue requires some time of reading from you and (hopefully) a
  public statement, that the original DXPC code can be considered as
  BSD-2-clause (the current license) also for released versions prior
  2002 when the ancient BSD license template [2] was still shipped with
  DXPC.
  
  For a complete follow-up, please check Debian bug #784565 [3].
  
  We are aware that NoMachine forked DXPC at some early stage around the
  year 2000 and wrote their own commercial product around it. Obviously,
  this fork happened before 2002 (i.e., before DXPC release 3.8.1), as
  libxcomp3 in NoMachine's NX ships the previously used BSD license
  template. I am not sure, if that fork was easy for you or actually a
  nuisance. I may only guess at this point. I'd be happy to know more
  (maybe not in this mail thread, though).
  
  NoMachine has stopped publishing NXv3 updates a couple of years ago
  (2011 IIRC), now. The maintenance has been moved into the hands of the
  currently available FLOSS projects X2Go, Arctica Project [NEW] and
  TheQVD. Some of us are running a business model on top of that
  (consultancy, support contracts, feature development contracts), some
  of us spend a lot of their free time on improving / maintaining
  nx-libs (as we call NoMachine's NXv3 at the moment).
  
  To outline the impact of my mail clearly: If you say that it was not
  legal by NoMachine to fork DXPC at the given time (before 2002), then
  all FLOSS remote desktop / remote application would be in real
  trouble, because then the core component of their software projects
  could not be considered as free (as in DFSG, Debian free software
  guidelines[4]) anymore. Also the code changes originally performed by
  NoMachine might have been illegal in the first place. All current
  maintenance activities and also planned future development on nx-libs
  would become questionable.
  
  Thus, I hope you can chime in on this: Dear developers of nx-libs,