Bug#892458: Fwd: [Debian-astro-maintainers] ftools update

[Salvatore Bonaccorso]

Hi Sam,

On Tue, Apr 17, 2018 at 02:18:26PM +1000, Sam Fowler wrote:
> On 17/04/18 06:40, Salvatore Bonaccorso wrote:
> > Hi Sam,
> > 
> > On Mon, Apr 09, 2018 at 10:19:34AM +1000, Sam Fowler wrote:
> >> On Wed, 14 Mar 2018 16:22:19 +0100 Ole Streicher  
> >> wrote:
> >>> FYI
> >>>
> >>>
> >>>  Forwarded Message 
> >>> Subject: [Debian-astro-maintainers] ftools update
> >>> Date: Wed, 14 Mar 2018 10:42:25 -0400
> >>> From: Michael Arida 
> >>> To: debian-astro-maintain...@lists.alioth.debian.org
> >>>
> >>>
> >>> Dear Debian Astro Maintainers,
> >>>
> >>> As you may have noticed CFITSIO was updated Friday (March 2) for a
> >>> major bug fix.  Since you have a software bundle that uses what we
> >>> assume is CFITSIO somewhere under the hood, we wanted to let you know
> >>> that you should update that code.  We are also expecting another
> >>> update in April.
> >>>
> >>> If you have any questions or concerns, feel free to contact me.
> >>>
> >>> Regards,
> >>>  Mike Arida
> >>> 
> >>> Michael Arida (ADNET) ASD/HEASARC
> >>> 301.286.2291/1215 (voice/fax)  Code 660, NASA/GSFC
> >>> michael.ar...@nasa.gov Greenbelt, MD 20771
> >>>
> >>> ___
> >>> Debian-astro-maintainers mailing list
> >>> debian-astro-maintain...@lists.alioth.debian.org
> >>> https://lists.alioth.debian.org/mailman/listinfo/debian-astro-maintainers
> >>
> >> This has been assigned has been assigned CVE-2018-1000166.
> > 
> > Looking at
> > https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0531
> > https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0529
> > it looks for those issues already CVE-2018-3848, CVE-2018-3849 and
> > CVE-2018-3846 were assigned and CVE-2018-1000166 is duplicate. Can you
> > confirm? And if so ask for rejection of CVE-2018-1000166?
> > 
> > Regards,
> > Salvatore
> 
> Hi Salvatore,
> 
> Looks like you are correct. I've request a rejection of CVE-2018-1000166
> from DWF in favour of CVE-2018-3846. I've filed separate RH bugs for
> CVE-2018-3848 and CVE-2018-3849.
> 
> Thanks for the heads up,

Thanks a lot for confirming that quickly. I have removed as well any
CVE-2018-1000166 from our security-tracker now as well.

Regards,
Salvatore

Bug#895876: FTBFS: needs update for newer src-exts

[Clint Adams]

Source: haskell-derive
Version: 2.6.3-2
Severity: serious
Forwarded: https://github.com/ndmitchell/derive/issues/33

.

Processed: tagging 895811

[Debian Bug Tracking System]

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

> tags 895811 + pending
Bug #895811 [src:inotify-tools] inotify-tools: do not enable sanitizers in 
production
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#892458: Fwd: [Debian-astro-maintainers] ftools update

[Sam Fowler]

On 17/04/18 06:40, Salvatore Bonaccorso wrote:
> Hi Sam,
> 
> On Mon, Apr 09, 2018 at 10:19:34AM +1000, Sam Fowler wrote:
>> On Wed, 14 Mar 2018 16:22:19 +0100 Ole Streicher  wrote:
>>> FYI
>>>
>>>
>>>  Forwarded Message 
>>> Subject: [Debian-astro-maintainers] ftools update
>>> Date: Wed, 14 Mar 2018 10:42:25 -0400
>>> From: Michael Arida 
>>> To: debian-astro-maintain...@lists.alioth.debian.org
>>>
>>>
>>> Dear Debian Astro Maintainers,
>>>
>>> As you may have noticed CFITSIO was updated Friday (March 2) for a
>>> major bug fix.  Since you have a software bundle that uses what we
>>> assume is CFITSIO somewhere under the hood, we wanted to let you know
>>> that you should update that code.  We are also expecting another
>>> update in April.
>>>
>>> If you have any questions or concerns, feel free to contact me.
>>>
>>> Regards,
>>>  Mike Arida
>>> 
>>> Michael Arida (ADNET) ASD/HEASARC
>>> 301.286.2291/1215 (voice/fax)  Code 660, NASA/GSFC
>>> michael.ar...@nasa.gov Greenbelt, MD 20771
>>>
>>> ___
>>> Debian-astro-maintainers mailing list
>>> debian-astro-maintain...@lists.alioth.debian.org
>>> https://lists.alioth.debian.org/mailman/listinfo/debian-astro-maintainers
>>
>> This has been assigned has been assigned CVE-2018-1000166.
> 
> Looking at
> https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0531
> https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0529
> it looks for those issues already CVE-2018-3848, CVE-2018-3849 and
> CVE-2018-3846 were assigned and CVE-2018-1000166 is duplicate. Can you
> confirm? And if so ask for rejection of CVE-2018-1000166?
> 
> Regards,
> Salvatore

Hi Salvatore,

Looks like you are correct. I've request a rejection of CVE-2018-1000166
from DWF in favour of CVE-2018-3846. I've filed separate RH bugs for
CVE-2018-3848 and CVE-2018-3849.

Thanks for the heads up,
--
Sam Fowler, Red Hat Product Security

Bug#895482: Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4

[Michael Shuler]

Thanks for the details. #895473 reported a similar error on locally
installed CA certificates, which I think may be related.

Each of the list of `rehash: skipping .. cannot open file` in your
errors appears to be on CAs that were removed in the package during this
update, so somewhere we have a problem with `openssl rehash` trying to
link to files we removed, but for some reason were not prefixed with '!'
in /etc/ca-certificates.conf.

I've tried a number of upgrades from a March 29 unstable chroot, as well
as from stretch to unstable on openstack instances, on both amd64 and
i386 (I don't think arch is dependent), and I've been unable to get a
similar error to present itself.

Each way I've tried, I get the package-removed certificates prefixed
properly and no errors, so haven't been able to reproduce this, yet. I
will keep trying with different options and see if I can figure out
where the problem is. If someone has a good way to reproduce, I'd
appreciate it!

-- 
Kind regards,
Michael

Bug#894874: Fixed in mod_gnutls 0.8.4

[Daniel Kahn Gillmor]

Version: 0.8.4-1

On Sat 2018-04-14 11:56:42 +0200, Fiona Klute wrote:
> The issue is fixed in the 0.8.4 upstream release, please update the
> package. :-)

Thanks, Fiona!  I'm closing this ticket with the release of 0.8.4-1 into
unstable.

--dkg

Bug#895863: python-acme: Unroutable maintainer address

[Scott Kitterman]

Package: python-acme
Version: 0.22.2-1
Severity: serious
Justification: Policy 3.3

Dear Maintainer,

After a recent upload, the FTP team received this error:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  letsencrypt-de...@lists.alioth.debian.org
host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1]
SMTP error from remote mail server after RCPT 
TO::
550 Unrouteable address

Policy 3.3 requires a working email address for the package maintainer.  This
may be an issue with the recent migration of alioth lists to a new host.

Scott K

Bug#893297: marked as done (livetribe-jsr223 FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 23:19:49 +
with message-id 
and subject line Bug#893297: fixed in livetribe-jsr223 2.0.6-2
has caused the Debian Bug report #893297,
regarding livetribe-jsr223 FTBFS with openjdk-9
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.)


-- 
893297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: livetribe-jsr223
Version: 2.0.6-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/livetribe-jsr223.html

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 6.331 s
[INFO] Finished at: 2019-04-19T12:17:51-12:00
[INFO] Final Memory: 11M/38M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test 
(default-test) on project livetribe-jsr223: There are 
test failures.
[ERROR] 
[ERROR] Please refer to 
/build/1st/livetribe-jsr223-2.0.6/target/surefire-reports for the individual 
test results.
[ERROR] Please refer to dump files (if any exist) 
[date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] There was an error in the forked process
[ERROR] Unable to create test class 
'javax.script.ScriptExceptionTest'
[ERROR] 
org.apache.maven.surefire.booter.SurefireBooterForkException: There was 
an error in the forked process
[ERROR] Unable to create test class 
'javax.script.ScriptExceptionTest'
[ERROR]    at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:673)
[ERROR]    at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
[ERROR]    at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
[ERROR]    at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
[ERROR]    at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
[ERROR]    at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
[ERROR]    at 
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
[ERROR]    at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
[ERROR]    at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
[ERROR]    at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
[ERROR]    at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
[ERROR]    at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
[ERROR]    at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
[ERROR]    at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
[ERROR]    at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
[ERROR]    at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
[ERROR]    at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
[ERROR]    at 

Processed: Pending fixes for bugs in the livetribe-jsr223 package

[Debian Bug Tracking System]

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

> tag 893297 + pending
Bug #893297 [src:livetribe-jsr223] livetribe-jsr223 FTBFS with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893297: Pending fixes for bugs in the livetribe-jsr223 package

[pkg-java-maintainers]

tag 893297 + pending
thanks

Some bugs in the livetribe-jsr223 package are closed in revision
6dff5ac8bd90b87485758a46092bbd1695370420 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/livetribe-jsr223.git/commit/?id=6dff5ac

Commit message:

Skip the tests.

Closes: #893297

Bug#895856: portmidi: maintainer address bounces mail from Debian system

[Paul Brossier]

ouch, thanks for notifying, it seems spf config is borken on my host,
will fix it asap.

best, piem

On 04/16/2018 11:54 PM, Thorsten Glaser wrote:
> Source: portmidi
> Version: 1:217-6
> Severity: serious
> 
> -- Forwarded message --
> From: Mail Delivery System 
> Message-ID: 
> X-Spam-Status: Yes, hits=0.99 required=0.90, tests=bmf
> To: t...@debian.org
> Date: Mon, 16 Apr 2018 18:04:58 +
> Subject: Mail delivery failed: returning message to sender
> 
> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
> 
>   p...@piem.org
> retry timeout exceeded
> 
> 
> 
> Reporting-MTA: dns; mailly.debian.org
> 
> Action: failed
> Final-Recipient: rfc822;p...@piem.org
> Status: 5.0.0
> 



signature.asc
Description: OpenPGP digital signature

Bug#895860: geany-plugins: Unroutable maintainer address

[Scott Kitterman]

Package: geany-plugins
Version: 1.33+dfsg-1
Severity: serious
Justification: Policy 3.3

Dear Maintainer,

After a recent upload, the FTP team received this error:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  pkg-geany-t...@lists.alioth.debian.org
host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1]
SMTP error from remote mail server after RCPT 
TO::
550 Unrouteable address

Policy 3.3 requires a working email address for the package maintainer.  This
may be an issue with the recent migration of alioth lists to a new host.

Scott K

Bug#895859: gir-to-d: Unroutable maintainer address

[Scott Kitterman]

Package: gir-to-d
Version: 0.15.0-1
Severity: serious
Justification: Policy 3.3

Dear Maintainer,

After a recent upload, the FTP team received this error:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  pkg-d-de...@lists.alioth.debian.org
host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1]
SMTP error from remote mail server after RCPT 
TO::
550 Unrouteable address

Policy 3.3 requires a working email address for the package maintainer.  This
may be an issue with the recent migration of alioth lists to a new host.

Scott K

Bug#893347: marked as done (libquartz2-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 00:20:13 +0200
with message-id 
and subject line Re: libquartz2-java FTBFS with openjdk-9
has caused the Debian Bug report #893347,
regarding libquartz2-java FTBFS with openjdk-9
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.)


-- 
893347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libquartz2-java
Version: 2.2.3-3
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libquartz2-java.html

...
main:
[unzip] Expanding: 
/build/1st/libquartz2-java-2.2.3/quartz/target/quartz-2.2.3.jar into 
/build/1st/libquartz2-java-2.2.3/quartz/target/classes
[INFO] Executed tasks
[INFO] 
[INFO] --- maven-bundle-plugin:2.5.4:manifest (generate-osgi-headers) @ quartz 
---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] quartz-parent .. SUCCESS [  0.002 s]
[INFO] quartz-core  SUCCESS [  8.615 s]
[INFO] quartz-commonj . SUCCESS [  3.873 s]
[INFO] quartz-jobs  SUCCESS [  2.451 s]
[INFO] quartz-plugins . SUCCESS [  2.485 s]
[INFO] quartz . FAILURE [  2.259 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 20.006 s
[INFO] Finished at: 2019-04-19T17:10:39-12:00
[INFO] Final Memory: 25M/86M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.felix:maven-bundle-plugin:2.5.4:manifest (generate-osgi-headers) on 
project quartz: Error trying to generate Manifest: 
/build/1st/libquartz2-java-2.2.3/quartz/target/pom.xml -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :quartz
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/libquartz2-java-2.2.3 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/libquartz2-java-2.2.3/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/libquartz2-java-2.2.3/debian 
-Dmaven.repo.local=/build/1st/libquartz2-java-2.2.3/debian/maven-repo 
--batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned 
exit code 1
make: *** [debian/rules:4: build] Error 2
--- End Message ---
--- Begin Message ---
This package builds for me again. I assume the issue was fixed in
another package and libquartz2-java was only affected.

Markus



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

Bug#895856: portmidi: maintainer address bounces mail from Debian system

[Thorsten Glaser]

Source: portmidi
Version: 1:217-6
Severity: serious

-- Forwarded message --
From: Mail Delivery System 
Message-ID: 
X-Spam-Status: Yes, hits=0.99 required=0.90, tests=bmf
To: t...@debian.org
Date: Mon, 16 Apr 2018 18:04:58 +
Subject: Mail delivery failed: returning message to sender

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  p...@piem.org
retry timeout exceededReporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;piem@piem.org
Status: 5.0.0
--- Begin Message ---
retitle 870787 liboss4-salsa*: please add six snd_{midi,seq}_* functions
affects 870787 src:portmidi
thanks

Hello again,

we also need the following symbols in oss-salsa:

• snd_midi_event_encode_byte
• snd_midi_event_free
• snd_midi_event_new
• snd_seq_delete_port
• snd_seq_disconnect_from

These are required to build src:portmidi, which is a new
dependency of src:musescore, and thus extending the scope
of this bugreport instead of creating a new one. Just to
remind, we also need this:

• snd_seq_event_length

Please d̲o̲ provide this!


Small side note: perhaps, given enough functions in oss-salsa,
portaudio19 could also use it, achieving feature parity. (Which
is why I Cc’d its maintainers as well.)

Thanks in advance,
//mirabilos
-- 
21:12⎜ sogar bei opensolaris haben die von der community so
ziemlich jeden mist eingebaut │ man sollte unices nich so machen das
desktopuser zuviel intresse kriegen │ das macht die code base kaputt
21:13⎜ linux war früher auch mal besser :D
--- End Message ---

Bug#895811: inotify-tools: do not enable sanitizers in production

[Chris Lamb]

Hi all,

FYI this was filed as wishlist bug against Lintian (#895831) which
is fixed in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/b5de7b0d24ef6ef9874ec321b96d0148cc930933

  checks/rules.desc  | 18 ++
  data/rules/rules-should-not-use|  1 +
  debian/changelog   |  3 +++
  .../rules-sanitize-all-buildflag/debian/debian/rules   |  6 ++
  t/tests/rules-sanitize-all-buildflag/desc  |  5 +
  t/tests/rules-sanitize-all-buildflag/tags  |  1 +
  6 files changed, 34 insertions(+)


Regards,

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

Bug#895475: marked as done (openshot-qt: non-DFSG assets in package)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 21:16:45 +
with message-id 
and subject line Bug#895475: fixed in openshot-qt 2.4.1+dfsg1-1
has caused the Debian Bug report #895475,
regarding openshot-qt: non-DFSG assets in package
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.)


-- 
895475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openshot-qt
Version: 2.4.1-2
Severity: normal

Dear Maintainer,

I found that this package includes a bundled font "Ubuntu Regular", which was 
determined to be non-DFSG 
(https://bugs.launchpad.net/ubuntu-font-licence/+bug/769874). It installs to 
the path 
"/usr/lib/python3/dist-packages/openshot_qt/images/fonts/Ubuntu-R.ttf". I know 
that in some other packages with this issue, the font has been replaced with a 
DFSG font such as Cantarell or DejaVu Sans.

Alex Krusemark

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

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

Versions of packages openshot-qt depends on:
ii  libjs-jquery3.2.1-1
ii  python3 3.6.4-1
ii  python3-openshot0.1.9+dfsg1-3+b2
ii  python3-pyqt5   5.9.2+dfsg-1
ii  python3-pyqt5.qtsvg 5.9.2+dfsg-1
ii  python3-pyqt5.qtwebkit  5.9.2+dfsg-1
ii  python3-zmq 17.0.0-1

Versions of packages openshot-qt recommends:
ii  blender   2.79.b+dfsg0-1
ii  inkscape  0.92.3-1

Versions of packages openshot-qt suggests:
pn  openshot-qt-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openshot-qt
Source-Version: 2.4.1+dfsg1-1

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated openshot-qt 
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: Mon, 16 Apr 2018 22:17:56 +0200
Source: openshot-qt
Binary: openshot-qt openshot-qt-doc openshot openshot-doc
Architecture: source
Version: 2.4.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Dr. Tobias Quathamer 
Description:
 openshot   - create and edit videos and movies (transitional package)
 openshot-doc - documentation for openshot-qt (transitional package)
 openshot-qt - create and edit videos and movies
 openshot-qt-doc - documentation for openshot-qt
Closes: 895475
Changes:
 openshot-qt (2.4.1+dfsg1-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Removing redundant Priority field in binary package
 .
   [ Dr. Tobias Quathamer ]
   * Use Cantarell font instead of non-free Ubuntu regular.
 Thanks to Alex Krusemark  (Closes: #895475)
   * Adapt d/watch to handle +dfsg version suffix
   * Add fonts-cantarell to Depends
   * Update Standards-Version to 4.1.4, no changes needed
   * Remove copyright information for Ubuntu font from d/copyright
   * Mark openshot-qt-doc as Multi-Arch: foreign
Checksums-Sha1:
 c06efa593ee8d86894c3eb57ccda013a2ef6a653 2300 openshot-qt_2.4.1+dfsg1-1.dsc
 816e6c86c96bd701a91b0c2422c423153f9ce06a 55364704 
openshot-qt_2.4.1+dfsg1.orig.tar.xz
 1c5938f8a9d5ac3d92f0b8a71ef745d1d0242881 207440 
openshot-qt_2.4.1+dfsg1-1.debian.tar.xz
 df177bc8184077674514cfcad1724c59c370a9fe 7844 
openshot-qt_2.4.1+dfsg1-1_amd64.buildinfo
Checksums-Sha256:
 56396f861f1d691bc624c87414b74696c6a5d05b2b6f761ae1a10918b4554599 2300 
openshot-qt_2.4.1+dfsg1-1.dsc
 365ac87089de600ed9a13e788181fcead49d1256d088db1733b6df7bd49a68a0 55364704 
openshot-qt_2.4.1+dfsg1.orig.tar.xz
 

Bug#895745: marked as done (cfitsio: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 20:50:49 +
with message-id 
and subject line Bug#895745: fixed in cfitsio 3.440-2
has caused the Debian Bug report #895745,
regarding cfitsio: Incomplete debian/copyright?
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.)


-- 
895745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfitsio
Version: 3.440-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Aurelien Jarno 

Hi,

I just ACCEPTed cfitsio from NEW but noticed it was missing 
attribution in debian/copyright for at least fits_hcompress.c, 
fits_decompress.c, iraffits.c, etc.

(This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated cfitsio 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: Mon, 16 Apr 2018 22:04:50 +0200
Source: cfitsio
Binary: libcfitsio6 libcfitsio-dev libcfitsio-bin libcfitsio-doc
Architecture: source
Version: 3.440-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Aurelien Jarno 
Description:
 libcfitsio-bin - CFITSIO based utilities
 libcfitsio-dev - library for I/O with FITS format data files (development 
files)
 libcfitsio-doc - documentation for CFITSIO
 libcfitsio6 - shared library for I/O with FITS format data files
Closes: 895745
Changes:
 cfitsio (3.440-2) experimental; urgency=medium
 .
   * debian/copyright: update to add the copyright of fits_hcompress.c and
 fits_hdecompress.c (Closes: #895745).
Checksums-Sha1:
 71c4e0353ad704c5f6d5f858756c4e67d56303b3 2264 cfitsio_3.440-2.dsc
 ba1172b292266e86115b68302f39a35a43b0bd4b 18572 cfitsio_3.440-2.debian.tar.xz
 68d2124763a1d04170f04b66cb1ef36d5e15582c 5458 cfitsio_3.440-2_source.buildinfo
Checksums-Sha256:
 8fb05d41ebe4a9251ba86b5938370737e7d167ece789d77d7383ea82d61cac2f 2264 
cfitsio_3.440-2.dsc
 9d43aaf3e2c7943c8cd49aae9f6d4247878a34400d40670659c8e36cef2907c1 18572 
cfitsio_3.440-2.debian.tar.xz
 b4d3596f8c42f9099198a6e8fa283dbad898bf479897816d379b552a0090453c 5458 
cfitsio_3.440-2_source.buildinfo
Files:
 bf98f66483440897d0b9f0f67acc7afd 2264 devel optional cfitsio_3.440-2.dsc
 3a92297e6069dd0de64f0f3f2380b063 18572 devel optional 
cfitsio_3.440-2.debian.tar.xz
 6da50db8ba8914e42b2d5d4a3f99c71c 5458 devel optional 
cfitsio_3.440-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAlrVAf4ACgkQE4jA+Jno
M2sHlg//fMrrRjLAa+YVFTRNZtx3l9+3C+ABFS8zAna3fMy0tnkCaXQOEk0CatW3
0Q93U6zqz7gPF/i5qXHWagJqN1UY+LBUfQGYijn68htExcgmSNySeMAIb6J6zme5
o/DjVlwXgdFBAC+Hkq8VrEihYawJSK/il3HJf2AXtG8G/4dTPP7wt5PPJe5CsYwc
kE/8RmUZubfMRP7pkOhtkaQYTZnKeZsgI5iycpzDsgKirLJ2tfTEpz6E6VQpeJIS
danKohC1hgClfHVOlFmfzgpDFd9djBDKX7/wKctseCqla8rccGvKNj5oFnO0zqY3
IfQtuB7S69X9yg7LHykR4zZkV1WCEO06Uwy8+ombX6dKL8KJZr1Nt02Uf+3Tnoxl
8t6GCFd0T6sEG46AnNL8X1PYL8fsNH8OPzM2Kc753F5MVfSLRNEaaSaQNraGjH3o
7XGK7qQzq/oPI+CAHxlPsZIWRXWkhs6OswdfZdA4swjqztjajjHkNHfqNRkSDEkZ
khoXY9y+QpieEDGVp92fVUoH9sEnofNhTaLHlRvCDnMV7UlkUeG65pvZNjLL9LGx
PK5aKg2DvdiuEbqk1Rxgt0S6ThDNfm1x4aMr0/N+Vf4xx9ChYtq5+0aEmmMhZI0L
/j0gq9Vc3WAMiGSkGFDdf8+s3oH4ew4L68jz1x9CL4Ps35ZCnbo=
=RmYH
-END PGP SIGNATURE End Message ---

Bug#895564: marked as done (CVE-2017-2896 CVE-2017-2897 CVE-2017-2919 CVE-2017-12111 CVE-2017-12110)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 20:47:10 +
with message-id 
and subject line Bug#895564: fixed in r-cran-readxl 0.1.1-1+deb9u1
has caused the Debian Bug report #895564,
regarding CVE-2017-2896 CVE-2017-2897 CVE-2017-2919 CVE-2017-12111 
CVE-2017-12110
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.)


-- 
895564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-readxl
Severity: grave
Tags: security

r-cran-readxl bundles libxls which is affected by a number of security 
vulnerabilities:

https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0426
https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0404
https://www.talosintelligence.com/vulnerability_reports/TALOS-2017-0403

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: r-cran-readxl
Source-Version: 0.1.1-1+deb9u1

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated r-cran-readxl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 Apr 2018 08:18:46 -0500
Source: r-cran-readxl
Binary: r-cran-readxl
Architecture: source amd64
Version: 0.1.1-1+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Description:
 r-cran-readxl - GNU R package to read Excel files
Closes: 895564
Changes:
 r-cran-readxl (0.1.1-1+deb9u1) stretch-security; urgency=high
 .
   * src/endian.c: Updated from libxls upstream (Closes: #895564)
   * src/libxls/endian.h: Idem
   * src/libxls/ole.h: Idem
   * src/libxls/xls.h: Idem
   * src/libxls/xlsstruct.h: Idem
   * src/libxls/xlstool.h: Idem
   * src/libxls/xlstypes.h: Idem
   * src/ole.c: Idem
   * src/xls.c: Idem
   * src/xlstool.c: Idem
 .
   * This addresses
CVE-2017-2896
 CVE-2017-2897
 CVE-2017-2919
 CVE-2017-12111
 CVE-2017-12110
 with corresponding upstream patches.
Checksums-Sha1:
 61360fd6a3780b9222fe5b2cac6871d8ea0edfb2 1745 r-cran-readxl_0.1.1-1+deb9u1.dsc
 d7714ce4fce42ec753e751e3966c652990795d32 323034 r-cran-readxl_0.1.1.orig.tar.gz
 79c290dfcdcaf87216109f244fc89489c18dffd2 21868 
r-cran-readxl_0.1.1-1+deb9u1.debian.tar.xz
 a384c8b7f37ea1d7a6f45ec84e7f6954fdcf8935 1086354 
r-cran-readxl-dbgsym_0.1.1-1+deb9u1_amd64.deb
 1a2350f2e291e3b01bb3c93e80c191c394bd1642 8261 
r-cran-readxl_0.1.1-1+deb9u1_amd64.buildinfo
 5bc8fe4282efc4c5a8b3bf75f887e6727931a227 197664 
r-cran-readxl_0.1.1-1+deb9u1_amd64.deb
Checksums-Sha256:
 93716d4c85de941554097f9333cf04df58b50e21415f1bd9f0c3d7b6d0a2767e 1745 
r-cran-readxl_0.1.1-1+deb9u1.dsc
 39d3da470137581a385c3130468d5e0ee5b5be9e46b6d3e93e4209dac3edf57a 323034 
r-cran-readxl_0.1.1.orig.tar.gz
 55e0ea1d4a40e9ef31bb90d0695fa48715d3ad109b077b53cc7069078537fd96 21868 
r-cran-readxl_0.1.1-1+deb9u1.debian.tar.xz
 529f19b41378156ca79dfd86cc52b5e12af2916f534bb4a8d7edf8bacfe808d0 1086354 
r-cran-readxl-dbgsym_0.1.1-1+deb9u1_amd64.deb
 fea96b548846e900e467ff4f24b52bbb3f496b2d830fb5f8229b8662b34b007e 8261 
r-cran-readxl_0.1.1-1+deb9u1_amd64.buildinfo
 dee521999cc22f272bee5c75f34065746829ead4ff151467df3cbc99ae889044 197664 
r-cran-readxl_0.1.1-1+deb9u1_amd64.deb
Files:
 cb6b740a26d405e0ad5d081451e6785b 1745 gnu-r optional 
r-cran-readxl_0.1.1-1+deb9u1.dsc
 565fd569d520e62ecd174aa4d3e43ce3 323034 gnu-r optional 
r-cran-readxl_0.1.1.orig.tar.gz
 3cbdab6a1a41ff4ff7aef5c5be293cf5 21868 gnu-r optional 
r-cran-readxl_0.1.1-1+deb9u1.debian.tar.xz
 aaf73941887e511c3418b66468050045 1086354 debug extra 
r-cran-readxl-dbgsym_0.1.1-1+deb9u1_amd64.deb
 544cddafcf278c9c67a791f538f39f7f 8261 gnu-r optional 
r-cran-readxl_0.1.1-1+deb9u1_amd64.buildinfo
 80d5b7e4271642ae3e2ac83658e297c6 197664 gnu-r optional 
r-cran-readxl_0.1.1-1+deb9u1_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#894993: patch: CVE-2018-1000156: input validation vulnerability when processing patch files

[Chris Lamb]

Moritz Muehlenhoff wrote:

> We're not planning to issue a DSA for this, but Laszlo is working on
> updates for point releases. Best to sync up directly with him if only to 
> compare the debdiffs you came up with.

Nod, thanks. Well, I wouldn't want to duplicate work ("compare debdiffs").

Laszlo, would you like me to co-ordindate jessie-pu and stretch-pu's or have
you got this?  (Feel free to drop t...@security.debian.org on any reply..)


Best wishes,

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

Bug#892458: Fwd: [Debian-astro-maintainers] ftools update

[Salvatore Bonaccorso]

Hi Sam,

On Mon, Apr 09, 2018 at 10:19:34AM +1000, Sam Fowler wrote:
> On Wed, 14 Mar 2018 16:22:19 +0100 Ole Streicher  wrote:
> > FYI
> > 
> > 
> >  Forwarded Message 
> > Subject: [Debian-astro-maintainers] ftools update
> > Date: Wed, 14 Mar 2018 10:42:25 -0400
> > From: Michael Arida 
> > To: debian-astro-maintain...@lists.alioth.debian.org
> > 
> > 
> > Dear Debian Astro Maintainers,
> > 
> > As you may have noticed CFITSIO was updated Friday (March 2) for a
> > major bug fix.  Since you have a software bundle that uses what we
> > assume is CFITSIO somewhere under the hood, we wanted to let you know
> > that you should update that code.  We are also expecting another
> > update in April.
> > 
> > If you have any questions or concerns, feel free to contact me.
> > 
> > Regards,
> >  Mike Arida
> > 
> > Michael Arida (ADNET) ASD/HEASARC
> > 301.286.2291/1215 (voice/fax)  Code 660, NASA/GSFC
> > michael.ar...@nasa.gov Greenbelt, MD 20771
> > 
> > ___
> > Debian-astro-maintainers mailing list
> > debian-astro-maintain...@lists.alioth.debian.org
> > https://lists.alioth.debian.org/mailman/listinfo/debian-astro-maintainers
> 
> This has been assigned has been assigned CVE-2018-1000166.

Looking at
https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0531
https://www.talosintelligence.com/vulnerability_reports/TALOS-2018-0529
it looks for those issues already CVE-2018-3848, CVE-2018-3849 and
CVE-2018-3846 were assigned and CVE-2018-1000166 is duplicate. Can you
confirm? And if so ask for rejection of CVE-2018-1000166?

Regards,
Salvatore

Bug#887924: slurm-drmaa FTBFS with slurm-llnl 17.11.2-1

[Dominique Belhachemi]

The bug is also in Debian's slurm-llnl package. The location of the header
files is not consistent anymore.

slurm.h is including 

See
https://anonscm.debian.org/git/collab-maint/slurm-llnl.
git/commit/debian/libslurm-dev.install?id=08c387553a95e9a4a38047c82cf69a
4f733cee0d
https://anonscm.debian.org/git/collab-maint/slurm-llnl.git/tree/slurm/slurm.h.in?id=a886927a2c465f2b82d2773190daa6d77e8ffd4f#n63

Bug#895475: Bug #895475 in openshot-qt marked as pending

[toddy]

Control: tag -1 pending

Hello,

Bug #895475 in openshot-qt reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/openshot-qt/commit/b4568459b938942e462a9a8fcf89106c953d5edb


Use Cantarell font instead of non-free Ubuntu regular.

Closes: #895475
Thanks: Alex Krusemark 



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/895475

Processed: Bug #895475 in openshot-qt marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #895475 [openshot-qt] openshot-qt: non-DFSG assets in package
Added tag(s) pending.

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

Bug#893268: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

[Andreas Tille]

Hi,

On Sun, Mar 25, 2018 at 11:59:14PM +0200, Emmanuel Bourg wrote:
> > I'm fine with moving libjbzip2-java (which I uploaded today) once
> > pkg-java has moved to Salsa (or did I missed the move?)
> 
> I'm working on the migration, I haven't finalized the notification hooks
> yet.

Besides the general migration libnanoxml2-java is currently in Debian
Med group on Salsa[1].  I would have moved a for to java-team but as
a "Developer" I have no permission to create repositories.  Feel free
to take over this (and ping me to remove it from Debian Med.)

The issue that the package does not build remains even with different
error:

...
cd Test/Lite && \
/usr/lib/jvm/default-java/bin/javac -source 1.8 -nowarn -cp 
.:../../nanoxml-lite.jar `find -iname *.java` && \
for TESTFILE in *.xml; do \
/usr/lib/jvm/default-java/bin/java -cp .:../../nanoxml-lite.jar 
DumpXML_Lite ${TESTFILE} > ${TESTFILE}.test_out ; \
if diff -u ${TESTFILE}.out ${TESTFILE}.test_out ; \
thenecho nanoxml-lite.jar failed ${TESTFILE}; \
exit 1; \
fi; \
done
Note: ./DumpXML_Lite.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
nanoxml-lite.jar failed comments.xml
...


Kind regards

  Andreas.


[1]  https://salsa.debian.org/med-team/libnanoxml2-java

-- 
http://fam-tille.de

Bug#895811: inotify-tools: do not enable sanitizers in production

[KAction]

[2018-04-16 11:25] James Cowgill 
> part 1.1.1 text/plain1507
> Source: inotify-tools
> Version: 3.14-4
> Severity: grave
> 
> Hi,
> 
> In inotify-tools 3.14-4, all the qa sanitizers were enabled in
> DEB_BUILD_MAINT_OPTIONS. This should not be done in production.
> 
> * The man page for dpkg-buildflags explicitly states these options
> should not be used in production builds and are for debugging only.
> [...]

My fault, definitely. Somehow I missed that warning in manpage.  Will
fix.

Bug#875547: animals: can't be played as non root user

[alberto fuentes]

On Mon, Apr 16, 2018 at 7:34 PM, Markus Koschany  wrote:

> Control: tags -1 pending
>
> Dear maintainer,
>
> I've uploaded a new revision of animals versioned as 201207131226-2.1
> that addresses the issue. Please find attached the debdiff.
>

Thanks for uploading a fix!

Bug#895475: openshot-qt: non-DFSG assets in package

[Dr. Tobias Quathamer]

Am 11.04.2018 um 23:48 schrieb Alex Krusemark:
> Dear Maintainer,
> 
> I found that this package includes a bundled font "Ubuntu Regular",
> which was determined to be non-DFSG
> (https://bugs.launchpad.net/ubuntu-font-licence/+bug/769874). It
> installs to the path
> "/usr/lib/python3/dist-packages/openshot_qt/images/fonts/Ubuntu-R.ttf".
> I know that in some other packages with this issue, the font has been
> replaced with a DFSG font such as Cantarell or DejaVu Sans.

Hi Alex,

very good catch, thanks a lot! I'll prepare a fixed version soon.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#893202: marked as done (squirrelmail: CVE-2018-8741: path traversal vulnerability)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 18:32:55 +
with message-id 
and subject line Bug#893202: fixed in squirrelmail 2:1.4.23~svn20120406-2+deb8u2
has caused the Debian Bug report #893202,
regarding squirrelmail: CVE-2018-8741: path traversal vulnerability
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.)


-- 
893202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squirrelmail
Version: 2:1.4.23~svn20120406-2
Severity: grave
Tags: security upstream

Hi

Sice there is no CVE assigned fill a Debian bug to have a reference.

See http://www.openwall.com/lists/oss-security/2018/03/17/2 for
additional information.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: squirrelmail
Source-Version: 2:1.4.23~svn20120406-2+deb8u2

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated squirrelmail 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 07 Apr 2018 15:24:43 +0200
Source: squirrelmail
Binary: squirrelmail
Architecture: all source
Version: 2:1.4.23~svn20120406-2+deb8u2
Distribution: jessie-security
Urgency: high
Maintainer: Jeroen van Wolffelaar 
Changed-By: Salvatore Bonaccorso 
Closes: 893202
Description: 
 squirrelmail - Webmail for nuts
Changes:
 squirrelmail (2:1.4.23~svn20120406-2+deb8u2) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Path traversal vulnerability (CVE-2018-8741)
 Directory traversal flaw in Deliver.class.php can allow a remote
 attacker to retrieve or delete arbitrary files. (Closes: #893202)
Checksums-Sha1: 
 979c050944cec020109ca236f7b1cba48749c492 2186 
squirrelmail_1.4.23~svn20120406-2+deb8u2.dsc
 48c5a43d231b33d8e6e4c6d3655c126fd90dd7ae 35032 
squirrelmail_1.4.23~svn20120406-2+deb8u2.debian.tar.xz
 96f163637b5a94b78d3477c6d07b5daa7472fc31 499632 
squirrelmail_1.4.23~svn20120406-2+deb8u2_all.deb
Checksums-Sha256: 
 0d7fb031fea6ef72de78aeb5cf3841f37767a40b1c706d57b5bc23e9eaf4bf5c 2186 
squirrelmail_1.4.23~svn20120406-2+deb8u2.dsc
 aec6f8157e10bc0a490dd12c48b76791c8fc027141086c01895b629358219e18 35032 
squirrelmail_1.4.23~svn20120406-2+deb8u2.debian.tar.xz
 b5f652a746391b0368dfe7e75bdc12c5c6e77a9e6bd12406e5ef276032bc 499632 
squirrelmail_1.4.23~svn20120406-2+deb8u2_all.deb
Files: 
 80640afa1147ccf9cd9fa41222e4d4e6 2186 web optional 
squirrelmail_1.4.23~svn20120406-2+deb8u2.dsc
 97ffd7598b81a2ff78fd50e45ada8a1b 35032 web optional 
squirrelmail_1.4.23~svn20120406-2+deb8u2.debian.tar.xz
 f7523f17588052e5ebd9da26061c 499632 web optional 
squirrelmail_1.4.23~svn20120406-2+deb8u2_all.deb

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlrIyHlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EaJ8P/2LczzJHLQ7kfcVTgGPazLfrqIf15eKK
brJfjrT/k8BPeSh9xF0enqPy05fqCFXzrTDpO8U4zvvrPixdVclW2W5HcUZFx0q9
J2/2RJHmwUPwTjUFCXaNrci0bXlvTb2hgwJVxz3apiYLpEEEWtJSEFBFudyKYtM5
kdScgiHbvLjLh5QWHlL6T/Y3/0xwqOjDnlIukdA+Ht8EJwURF7P4Qh7dMNQ16RwW
r4FWrXzobI6NHZeo7yvgGte1GYw8DegpAixlRwQxRpP/PdyA30247O4FYIjMIH0o
NiqSaelNLc41xtpTGfkFLlYi0cPVoFVyP4uG4Vv3AmiJ4R5vcNvaF9eAw9M/TL+S
WJn3NGnt/ieNqCy+T7p0HHJKBIxbHqwgmJeG0kpPsUQ1yXgyMEUj46xfnTkQ5jBA
z2u+6i5/O3pDGmExJoeuLPe0F+ez5WgA9figfONh9Av4ytAakerq2ZX3gWtoasgT
UU+7U4SmF1Tpe6t7p/OkUGDiUX9p+C4W4efr2F/wdMrXyxLL5f2oWTl1qlTzfdbn
MhPA9pcIxrUUh8Ahy53tHx6kxwQ74ai3Z30Fo0Kvblfw1+mNoTg6XBLCIXYGQzyH
3SeqHv/Goxl2u+jwfF4nBMu9K0UuanGy6fImWG/fkEnfSpaoVwCvVFrnQHHlepEK
lLmDIhFn4mHi
=2lkj
-END PGP SIGNATURE End Message ---

Bug#875547: marked as done (animals: can't be played as non root user)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 17:49:26 +
with message-id 
and subject line Bug#875547: fixed in animals 201207131226-2.1
has caused the Debian Bug report #875547,
regarding animals: can't be played as non root user
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.)


-- 
875547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: animals
Version: 201207131226-2+b1
Severity: grave
Justification: renders package unusable

The game tries to write its database in /var/games/animals, and segfaults on 
startup when it can't.
it needs to either be setuid/gid to a user that can write to that location (but 
do nothing else),
or it should use a local database in the user's home directory.
At the moment it can only be played as root.


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

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

Versions of packages animals depends on:
ii  libc6   2.24-12ubuntu1
ii  libdb5.3++  5.3.28-13.1
ii  libgcc1 1:7.2.0-3ubuntu1
ii  libstdc++6  7.2.0-3ubuntu1

animals recommends no packages.

animals suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: animals
Source-Version: 201207131226-2.1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated animals 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: Mon, 16 Apr 2018 19:21:27 +0200
Source: animals
Binary: animals
Architecture: source
Version: 201207131226-2.1
Distribution: unstable
Urgency: medium
Maintainer: Alberto Fuentes 
Changed-By: Markus Koschany 
Description:
 animals- Traditional AI animal guessing engine using a binary tree DB
Closes: 875547
Changes:
 animals (201207131226-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix typo overwrite -> override in debian/rules that prevented the use of
 correct file permissions and thus made the game unusable.
 Thanks to Aaron Howell for the report. (Closes: #875547)
Checksums-Sha1:
 1791c062baf3f60f0ad3518353f7e69c79398bf7 1925 animals_201207131226-2.1.dsc
 2f7a4ec1d4a08ad2fd1be4e4e7daa39a78e6761a 4800 
animals_201207131226-2.1.debian.tar.xz
 3e2b3572cb8876b3484732c431ae37f3b826d0c9 5943 
animals_201207131226-2.1_amd64.buildinfo
Checksums-Sha256:
 7c69fbbee11753b6d5ec05c7c050140d8ef716cf8ba1f5b867eeb1673c43b7d6 1925 
animals_201207131226-2.1.dsc
 79564e4fc4870e878f5d7b1a9d91eac2ea688575c495207b8e588b876c52ffc7 4800 
animals_201207131226-2.1.debian.tar.xz
 bd2d66f5576f279d092673e9764ad2db64060e7491941a75da6f1bcf97b26983 5943 
animals_201207131226-2.1_amd64.buildinfo
Files:
 94bd2592922b32b1dbe8286bc2051864 1925 games optional 
animals_201207131226-2.1.dsc
 75b685659aff9d787de710ce3f3fec0e 4800 games optional 
animals_201207131226-2.1.debian.tar.xz
 9811046703584424469b64d6a6565ae5 5943 games optional 
animals_201207131226-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlrU3iFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk00cP/2iWBjDJrsk1oWB9BguLeWh8E2tWSmzZ4Dtn
PsX49vmCqQIu7aet9Y5fRUR4L8w3JsQYD9kBS8my6je8pg9G0zw9mJw4RFOx+3HA
F+9Nbh6gROBndkrn6oqAUzwa6YV6xXA/tnmQFS4d9w8tG2czXY8klBSmfiSjEnl/
f8ndnSHGH7VDNyfFq5bW659CmmfwXtDDtKNkZSW0EjxWHS6/6l+b/r70sWsERU9P
KefVvVXhMvMVRcxRNJpN9c/R4U8nPS7AUc7JSc+5UctlKVFtyFL6fphLI8I3Sg6B
IiYDIah7/rGu1on+A/klh4OtD8HbEcSqL/CEdQGPJPZlqEQVWEEX7ZE8c4YLp5V6

Bug#875547: animals: can't be played as non root user

[Markus Koschany]

Control: tags -1 pending

Dear maintainer,

I've uploaded a new revision of animals versioned as 201207131226-2.1
that addresses the issue. Please find attached the debdiff.

Regards,

Markus
diff -Nru animals-201207131226/debian/changelog 
animals-201207131226/debian/changelog
--- animals-201207131226/debian/changelog   2016-09-11 20:20:18.0 
+0200
+++ animals-201207131226/debian/changelog   2018-04-16 19:21:27.0 
+0200
@@ -1,3 +1,12 @@
+animals (201207131226-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix typo overwrite -> override in debian/rules that prevented the use of
+correct file permissions and thus made the game unusable.
+Thanks to Aaron Howell for the report. (Closes: #875547)
+
+ -- Markus Koschany   Mon, 16 Apr 2018 19:21:27 +0200
+
 animals (201207131226-2) unstable; urgency=medium
 
   * Switch to dh
diff -Nru animals-201207131226/debian/rules animals-201207131226/debian/rules
--- animals-201207131226/debian/rules   2016-09-11 20:20:18.0 +0200
+++ animals-201207131226/debian/rules   2018-04-16 19:21:27.0 +0200
@@ -8,7 +8,7 @@
 override_dh_strip:
dh_strip --dbgsym-migration='animals-dbg (<<201207131226-1)'
 
-overwrite_dh_fixperms:
+override_dh_fixperms:
dh_fixperms
chown games:games $(CURDIR)/debian/animals/var/games/animals
chmod 06775 $(CURDIR)/debian/animals/var/games/animals


signature.asc
Description: OpenPGP digital signature

Processed: Re: animals: can't be played as non root user

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #875547 [animals] animals: can't be played as non root user
Added tag(s) pending.

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

Bug#895778: jruby: Several security vulnerabilities

[Miguel Landaeta]

On Sun, Apr 15, 2018 at 10:48:10PM +0200, Markus Koschany wrote:
> I intend to work on the patches for Jessie and Stretch. Unstable could
> be a bit more complicated due to the FTBFS with OpenJDK 9.

Hi Markus,

Thanks for taking care of jessie and stretch.

I expect to be able to update jruby in unstable soon, although there
is some pending work to do, as I mentioned in #895837.

These days I'm more involved with that project as upstream, so I haven't
find enough time to work on this package yet.

Cheers,
Miguel.

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: PGP signature

Bug#887315: libgc FTBFS on armel: missing symbol AO_locks

[James Clarke]

On Sun, Jan 14, 2018 at 11:20:49PM +0200, Adrian Bunk wrote:
> Source: libgc
> Version: 1:7.4.2-8.1
> Severity: serious
>
> https://buildd.debian.org/status/fetch.php?pkg=libgc=armel=1%3A7.4.2-8.1=1515764936=0
>
> ...
>dh_makeshlibs -a
> dh_makeshlibs: Compatibility levels before 9 are deprecated (level 7 in use)
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: no debian/symbols file used as basis for generating 
> debian/libgc1c2/DEBIAN/symbols
> --- new_symbol_file (libgc1c2_1:7.4.2-8.1_armel)
> +++ dpkg-gensymbolsCP1Zv9 2018-01-12 13:48:50.806274887 +
> @@ -1,7 +1,7 @@
>  libgc.so.1 libgc1c2 #MINVER#
>   (arch=armel)AO_compare_double_and_swap_double_emulation@Base 1:7.4.2
>   (arch=armel)AO_fetch_compare_and_swap_emulation@Base 1:7.4.2
> - (arch=armel)AO_locks@Base 1:7.4.2
> +#MISSING: 1:7.4.2-8.1# (arch=armel)AO_locks@Base 1:7.4.2
>   (arch=armel)AO_pause@Base 1:7.4.2
>   (arch=armel)AO_pt_lock@Base 1:7.4.2
>   (arch=armel)AO_store_full_emulation@Base 1:7.4.2
> dh_makeshlibs: failing due to earlier errors
> debian/rules:11: recipe for target 'binary-arch' failed
> make: *** [binary-arch] Error 2
>
>
> This might be caused by the recent armv4t -> armv5te armel
> baseline change.
>
> I am completely lost regarding what is going on here,
> starting with the fact that this looks a Libatomic-ops symbol?

This one turned out to be pretty easy; libatomic-ops 7.6.0 made AO_locks
static and therefore a local symbol; from the upstream changelog:

> == [7.6.0] 2017-05-19 ==
> [...]
> * Hide AO_locks symbol

Thus the symbol should be dropped from the symbols file in libgc, which
shouldn't cause any problems, since it was an implementation detail that
was only ever exported on armel so nobody should be using it (but of
course, when has that stopped anyone...).

Regards,
James

Bug#894993: patch: CVE-2018-1000156: input validation vulnerability when processing patch files

[Moritz Muehlenhoff]

On Mon, Apr 16, 2018 at 03:44:50PM +0100, Chris Lamb wrote:
> [adding t...@security.debian.org to CC]
> 
> Hi,
> 
> > patch: CVE-2018-1000156: input validation vulnerability when processing
> > patch files
> 
> I've fixed this in wheezy; would you like for an update for jessie and
> stretch whilst it's fresh in my mind? The patch (hah!) did require some
> modification for wheezy after all.

We're not planning to issue a DSA for this, but Laszlo is working on
updates for point releases. Best to sync up directly with him if only to 
compare the debdiffs you came up with.

Cheers,
Moritz

Bug#895428: marked as done (Port from libnm-glib/libnm-util to libnm)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 16:56:24 +
with message-id 
and subject line Bug#895428: fixed in remote-logon-service 1.0.2.0-1
has caused the Debian Bug report #895428,
regarding Port from libnm-glib/libnm-util to libnm
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.)


-- 
895428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: remote-logon-service
Version: 1.0.1.1-2
Severity: important
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: libnm

Hi,

the libnm-glib/libnm-util libraries have been deprecated upstream in
favour of libnm.

Your package declares a Build-Depends on libnm-glib-dev.


Please consider porting this over to libnm.
libnm provides an API similar to libnm-glib/libnm-util [1].


[1] https://developer.gnome.org/libnm/stable/

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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: remote-logon-service
Source-Version: 1.0.2.0-1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated remote-logon-service 
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: Mon, 16 Apr 2018 16:43:36 +0200
Source: remote-logon-service
Binary: remote-logon-service
Architecture: source
Version: 1.0.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Description:
 remote-logon-service - DBus service for tracking available remote logon servers
Closes: 895428
Changes:
 remote-logon-service (1.0.2.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - Port from libnm-glib to libnm.
   * debian/copyright:
 + Use secure URI to obtain copyright format reference.
   * debian/control:
 + Bump Standards-Version: to 4.1.4. No changes needed.
 + Drop python from B-D. Not needed anymore.
 + Drop useless dh-autoreconf B-D. Implicit since DH version level 10.
 + B-D: Switch over from libnm-glib-dev to libnm-dev. (Closes: #895428).
   * debian/{control,compat}:
 + Bump DH compat level to version 11.
Checksums-Sha1:
 883f05dc6978f184e11d4991209523a7efd1b6f8 2630 
remote-logon-service_1.0.2.0-1.dsc
 aa75b76c927ac05e265b7bebc8bc3a78014a0f21 63675 
remote-logon-service_1.0.2.0.orig.tar.gz
 acfc83bcc5a5b63119cd3943c22140abcdb35455 833 
remote-logon-service_1.0.2.0.orig.tar.gz.asc
 a5ab6704af15e1051b7e2f8b38cf38326ee9bbaf 11088 
remote-logon-service_1.0.2.0-1.debian.tar.xz
 9e44690dc8204f69ba903dbf62861cb88c22ac8a 10552 
remote-logon-service_1.0.2.0-1_source.buildinfo
Checksums-Sha256:
 5c6b8dc8b5e7f38ca99ae3181621097dbb6e65988dd90c07cdf558ec41c53647 2630 
remote-logon-service_1.0.2.0-1.dsc
 272c2dcd77b2619e2612d607f22cf0cb765959cba169dadc3d76f8a126a4cf22 63675 
remote-logon-service_1.0.2.0.orig.tar.gz
 705421d7c7d4c3f480cb0d046c2b7c4118613d9e10a6b917c27a99210c295795 833 
remote-logon-service_1.0.2.0.orig.tar.gz.asc
 e58b88fd0f6e566d7c24b74b99d0331bd0992572edcb49b9e29717d95f424a18 11088 
remote-logon-service_1.0.2.0-1.debian.tar.xz
 446f8987c857cb4f7d8fb5d70887ce83f1420932f249590e6a1406595f1958a0 10552 
remote-logon-service_1.0.2.0-1_source.buildinfo
Files:
 5426d3fcc6e1f4a8fa043bec0ec718bb 2630 misc optional 
remote-logon-service_1.0.2.0-1.dsc
 3f63a3dd9c9c44e01cdfd131a45f15b5 63675 misc optional 
remote-logon-service_1.0.2.0.orig.tar.gz
 e005db3f6b27b226270808a3d9cc55d7 833 misc optional 
remote-logon-service_1.0.2.0.orig.tar.gz.asc
 

Bug#895444: [Pkg-ayatana-devel] Bug#895444: Bug#895444: Uses deprecated NetworkManager.pc

[Michael Biebl]

Am 16.04.2018 um 11:32 schrieb Mike Gabriel:
> Hi Michael,
> 
> On  Sa 14 Apr 2018 20:58:01 CEST, Mike Gabriel wrote:
> 
>> Hi,
>>
>> On  Sa 14 Apr 2018 01:04:15 CEST, Michael Biebl wrote:
>>
>>> Control: severity -1 serious
>>>
>>> Hi,
>>>
>>> I intend to upload a new version of network-manager soonish which will
>>> drop libnm-glib/libnm-util. I'm thus bumping this issue to RC in
>>> preparation for that.
>>>
>>> Regards,
>>> Michael
>>
>> Ouch (libqtdbusmock). I presume that I have to patch this for Debian
>> instead of waiting for upstream to fix this.
>>
>> Noted. Let's see what I can find...
>> Mike
> 
> I did the porting work (patch CMakeLists.txt and B-D on libnm-dev).
> 
> However, I get a fancy FTBFS, that may be caused by GLib rather then
> libqtdbusmock itself:
> 
> ```
> cd
> /<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu/src/libqtdbusmock
> && /usr/bin/c++  -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_NO_DEBUG
> -DQT_TESTCASE_BUILDDIR=\"/<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu\"
> -DQT_TESTLIB_LIB -Dqtdbusmock_EXPORTS
> -I/<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu/src/libqtdbusmock
> -I/<>/libqtdbusmock-0.7+bzr49+repack1/src/libqtdbusmock
> -I/<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu/src/libqtdbusmock/qtdbusmock_autogen/include
> -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtTest -I/usr/include/libqtdbustest-1
> -I/usr/include/libnm -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -I/<>/libqtdbusmock-0.7+bzr49+repack1/src
> -I/<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu/src  -g
> -O2 -fdebug-prefix-map=/<>/libqtdbusmock-0.7+bzr49+repack1=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fvisibility-inlines-hidden
> -fPIC   -std=c++11 -fno-permissive -pedantic -Wall -Wextra -fPIC
> -std=gnu++11 -o CMakeFiles/qtdbusmock.dir/DBusMock.cpp.o -c
> /<>/libqtdbusmock-0.7+bzr49+repack1/src/libqtdbusmock/DBusMock.cpp
> 
> In file included from
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:49:0,
>  from
> /usr/include/x86_64-linux-gnu/qt5/QtDBus/qtdbusglobal.h:44,
>  from
> /usr/include/x86_64-linux-gnu/qt5/QtDBus/qdbusconnection.h:44,
>  from
> /usr/include/x86_64-linux-gnu/qt5/QtDBus/QDBusConnection:1,
>  from
> /usr/include/libqtdbustest-1/libqtdbustest/DBusService.h:22,
>  from
> /usr/include/libqtdbustest-1/libqtdbustest/DBusTestRunner.h:19,
>  from
> /<>/libqtdbusmock-0.7+bzr49+repack1/src/libqtdbusmock/DBusMock.h:21,
> 
>  from
> /<>/libqtdbusmock-0.7+bzr49+repack1/src/libqtdbusmock/DBusMock.cpp:19:
> 
> /usr/include/glib-2.0/gio/gdbusintrospection.h:155:25: error: expected
> unqualified-id before 'public'
>    GDBusSignalInfo **signals;
>  ^
> In file included from /usr/include/glib-2.0/gio/gio.h:54:0,
>  from /usr/include/libnm/nm-types.h:24,
>  from /usr/include/libnm/nm-object.h:29,
>  from /usr/include/libnm/nm-access-point.h:29,
>  from /usr/include/libnm/NetworkManager.h:26,
>  from
> /<>/libqtdbusmock-0.7+bzr49+repack1/src/libqtdbusmock/DBusMock.cpp:22:
> 
> /usr/include/glib-2.0/gio/gdbusintrospection.h:155:24: error: expected
> ';' at end of member declaration
>    GDBusSignalInfo **signals;
>     ^
> /usr/include/glib-2.0/gio/gdbusintrospection.h:155:32: error: expected
> ':' before ';' token
>    GDBusSignalInfo **signals;
>     ^
> /usr/include/glib-2.0/gio/gdbusintrospection.h:155:32: warning: extra
> ';' [-Wpedantic]
> ```
> 
> Have you seen this before? Any clue on where to look for the cause?

I have indeed. Please have a look at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862883#24 and the
following replies.

Using Q_ macros and -DQT_NO_KEYWORDS you should be able to avoid the
build failure.




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: [Pkg-nagios-devel] Bug#895813: nagios-nrpe-plugin: "corrupted size" when checking NSClient++ NRPE server on i386 architecture

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #895813 [nagios-nrpe-plugin] nagios-nrpe-plugin: "corrupted size" when 
checking NSClient++ NRPE server on i386 architecture
Severity set to 'important' from 'grave'
> tags -1 upstream
Bug #895813 [nagios-nrpe-plugin] nagios-nrpe-plugin: "corrupted size" when 
checking NSClient++ NRPE server on i386 architecture
Ignoring request to alter tags of bug #895813 to the same tags previously set
> forwarded -1 https://github.com/NagiosEnterprises/nrpe/issues/180
Bug #895813 [nagios-nrpe-plugin] nagios-nrpe-plugin: "corrupted size" when 
checking NSClient++ NRPE server on i386 architecture
Set Bug forwarded-to-address to 
'https://github.com/NagiosEnterprises/nrpe/issues/180'.

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

Bug#895813: [Pkg-nagios-devel] Bug#895813: nagios-nrpe-plugin: "corrupted size" when checking NSClient++ NRPE server on i386 architecture

[Sebastiaan Couwenberg]

Control: severity -1 important
Control: tags -1 upstream
Control: forwarded -1 https://github.com/NagiosEnterprises/nrpe/issues/180

Hi Samuel,

Thanks for the extensive bugreport. I've forwarded it upstream as it
doesn't look like a package specific issue. I've also downgraded the
severity as this issue doesn't warrant autoremoval from testing.

Kind Regards,

Bas

Processed: Re: Bug#895809: enlightenment: Fails to start

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #895809 [enlightenment] enlightenment: Fails to start
Severity set to 'normal' from 'grave'
> tags -1 moreinfo
Bug #895809 [enlightenment] enlightenment: Fails to start
Added tag(s) moreinfo.

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

Bug#895809: enlightenment: Fails to start

[Ross Vandegrift]

On Mon, Apr 16, 2018 at 06:09:27PM +0200, Manolo Díaz wrote:
> On Monday, 16 Apr 2018 at 15:43 UTC
> Ross Vandegrift wrote:
> 
> > Control: severity -1 normal
> > Control: tags -1 moreinfo
> > 
> > > ESTART: 0.17880 [0.00119] - Compositor Init
> > >  Enlightenment Error 
> > > Enlightenment cannot initialize Ecore_X!  
> > 
> > Is X running?  How are you starting enlightenment?
> > 
> > Ross
> 
> No, X is installed but it wasn't running. I tried the
> enlightenment_start command from the linux console, no X display
> manager such as ldm, etc.

That's the issue.  You must have a X server running to start a window
manager, enlightenment included.  Try:

startx enlightenment_start

FWIW, you might have a nicer experience with a display manager.
Enlightenment will appear as a session option in gdm/kdm/lightdm/etc.

Ross

Bug#895809: enlightenment: Fails to start

[Ross Vandegrift]

Control: severity -1 normal
Control: tags -1 moreinfo

> ESTART: 0.17880 [0.00119] - Compositor Init
>  Enlightenment Error 
> Enlightenment cannot initialize Ecore_X!

Is X running?  How are you starting enlightenment?

Ross

Bug#895809: enlightenment: Fails to start

[Manolo Díaz]

On Monday, 16 Apr 2018 at 15:43 UTC
Ross Vandegrift wrote:

> Control: severity -1 normal
> Control: tags -1 moreinfo
> 
> > ESTART: 0.17880 [0.00119] - Compositor Init
> >  Enlightenment Error 
> > Enlightenment cannot initialize Ecore_X!  
> 
> Is X running?  How are you starting enlightenment?
> 
> Ross

Sorry, forgot to send to 895...@bugs.debian.org

No, X is installed but it wasn't running. I tried the
enlightenment_start command from the linux console, no X display
manager such as ldm, etc.

-- 
Manolo Díaz

Bug#895765: igv: FTBFS with java 9

[Olivier Sallou]

On 04/16/2018 04:38 PM, Andreas Tille wrote:
> Hi Olivier,
>
> could you provide a patch assumed we'll stick to Java 9 and higher?

I tried to add module, but javafx module is not found on system.
In debian package, I found only openjfx8, no port available for java9 ?
There is a bug [0] requesting version for jdk9 but it seems it is not
yet available

javafx is used for user interface, don't think we can remove it


[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850921
>
> (Could you also have a look into artemis, htsjdk and picard-tools
> if your time permits?)
>
> Kind regards
>
>   Andreas.
>
> On Mon, Apr 16, 2018 at 10:17:57AM +0200, Olivier Sallou wrote:
>>
>> On 04/16/2018 09:32 AM, Bas Couwenberg wrote:
>>> On 2018-04-16 08:18, Andreas Tille wrote:
 it seems something has changed with openfx since the errors below are
 all mentioning something like "import javafx. ...".  Do you have any
 hint how this can be fixed?
>>> There is no OpenJFX for OpenJDK 9, see:
>>>
>>>  https://lists.debian.org/debian-java/2018/04/msg3.html
>> indeed Java 9 removed some packages from *core* java and were moved to
>> additional modules to add at compilation/runtime.
>> Problem is this is not transparent/compatible with java <= 8.
>> So, to support java 9 AND below, you need specific scripts that detect
>> java version and act accordingly. This is not really cool to do and
>> maintain.
>>
>> As proposed, either javafx can be removed from code, either we shoud
>> stick to Java 9 and superior and add the javafx module.
>> there is an example in biojava4 for a build.xml:
>>
>>
>>        
>>           
>>           
>>   .
>>
>> this example used java.se.ee module.
>>
>> For javafx, there are several modules [0]:
>>
>> * Base APIs for JavaFX UI Toolkit — javafx.base
>> * JavaFX APIs for UI Controls — javafx.controls
>> * JavaFX APIs for FXML — javafx.fxml
>> * JavaFX APIs for various Graphics Tools— javafx.graphics
>> * JavaFX APIs for Multimedia — javafx.media
>> * JavaFX APIs for Swing-JavaFX Interoperability — javafx.swing
>> * JavaFX APIs for WebView Functionality — javafx.web
>>
>>
>> To add multiple modules, one need to separate them with comma.
>>
>> [0]
>> https://medium.com/@afinlay/whats-new-in-java-fx-java-9-updates-a90dd3d4dbba
>>
>>
>>
>>> If the package works without JavaFX you should consider disabling that
>>> for the time being.
>>>
>>> You can also explicitly build with OpenJDK 8, but that will just get
>>> you a different RC bug because openjdk-8 will not be in buster.
>>>
>>> Kind Regards,
>>>
>>> Bas
>>>
>> -- 
>> Olivier Sallou
>> Univ Rennes, Inria, CNRS, IRISA
>> Irisa, Campus de Beaulieu
>> F-35042 RENNES - FRANCE
>> Tel: 02.99.84.71.95
>>
>> gpg key id: 4096R/326D8438  (keyring.debian.org)
>> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
>>
>>
>>

-- 
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#895828: haskell-vector-space-points: cannot be built in sid

[Clint Adams]

Source: haskell-vector-space-points
Version: 0.2.1.2-3
Severity: serious

vector-space-points must either be patched or removed

Bug#895467: marked as done (libsearpc FTBFS on 64bit big endian: test failure)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 15:07:35 +
with message-id 
and subject line Bug#895467: fixed in libsearpc 3.0.8-4
has caused the Debian Bug report #895467,
regarding libsearpc FTBFS on 64bit big endian: test failure
to be marked as done.

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

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


-- 
895467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsearpc
Version: 3.0.8-2
Severity: serious

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

...
FAIL: test-searpc
=

Loaded 1 suites: 
Started

(process:10121): Searpc-WARNING **: 17:59:21.601: failed to read rpc request: 
Bad address

(process:10121): Searpc-WARNING **: 17:59:21.601: failed to read rpc response: 
Connection reset by peer
F
(process:10121): Searpc-WARNING **: 17:59:21.923: failed to read rpc request: 
Bad address

(process:10121): Searpc-WARNING **: 17:59:21.923: failed to send rpc call: 
Broken pipe
F
(process:10121): Searpc-WARNING **: 17:59:22.122: failed to read rpc request: 
Bad address

(process:10121): Searpc-WARNING **: 17:59:22.125: failed to read rpc response: 
Connection reset by peer
F

  1) Failure:
searpc::pipe_simple_call [searpc.c:427]
  Expression is not true: error == NULL
  Transport Error

  2) Failure:
searpc::pipe_large_request [searpc.c:454]
  Expression is not true: error == NULL
  Transport Error

  3) Failure:
searpc::pipe_concurrent_clients [searpc.c:483]
  Expression is not true: error == NULL
  Transport Error

System error: `fork()` call failed (12) - Cannot allocate memory
FAIL test-searpc (exit status: 255)


Testsuite summary for libsearpc 3.0.8

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to i...@seafile.com

make[5]: *** [Makefile:687: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: libsearpc
Source-Version: 3.0.8-4

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

Debian distribution maintenance software
pp.
Moritz Schlarb  (supplier of updated libsearpc 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: Mon, 16 Apr 2018 16:33:53 +0200
Source: libsearpc
Binary: libsearpc1 libsearpc-dev python-searpc
Architecture: source amd64 all
Version: 3.0.8-4
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Moritz Schlarb 
Description:
 libsearpc-dev - Development files for the Searpc framework
 libsearpc1 - Shared library for the Searpc framework
 python-searpc - Python bindings for the Searpc framework
Closes: 895467
Changes:
 libsearpc (3.0.8-4) unstable; urgency=medium
 .
   * Add patch for FTBFS on 64bit big endian and refresh patch series
 (Closes: #895467)
Checksums-Sha1:
 e4b7647a49656717757d05e736a14597425e41cd 2154 libsearpc_3.0.8-4.dsc
 03bdabeb4f9a247d670d9c30e8b563caee50ebb0 5040 libsearpc_3.0.8-4.debian.tar.xz
 0c7e13eb69b9d137eb669b2464f1a1273de34b9a 18116 libsearpc-dev_3.0.8-4_amd64.deb
 8c1551b74013cf8254aa1326f79610190dc3f8e3 41580 
libsearpc1-dbgsym_3.0.8-4_amd64.deb
 0f6072c670e33ea136f5c99510addfbe1792e2dc 19944 libsearpc1_3.0.8-4_amd64.deb
 6bccd865abbffa57530ff50d38b90a533101a5cb 7427 libsearpc_3.0.8-4_amd64.buildinfo
 763d298274a73513eafdb4ee97a07649bef68bcf 6868 python-searpc_3.0.8-4_all.deb
Checksums-Sha256:
 edfedb9b4bf21f6f144f9f25f0b52b2ac61d95eed012b5ed2002fc3ebaf97c90 2154 
libsearpc_3.0.8-4.dsc
 352b0e2ce5107a1e6417dbc71fb4372699fc2f5ff69815a776fe16f2037532c0 5040 
libsearpc_3.0.8-4.debian.tar.xz
 8dc7e19436a223aeef0117f9ef927953935136507d833e94755ec49410a7dd22 18116 

Bug#876147: marked as done (camp frequently FTBFS on 64bit big endian: camptest-qt (Failed))

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 15:04:45 +
with message-id 
and subject line Bug#876147: fixed in camp 0.8.2-1
has caused the Debian Bug report #876147,
regarding camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)
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.)


-- 
876147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: camp
Version: 0.8.1-1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-powe...@lists.debian.org

Builds of camp 0.8 for ppc64 and sparc64 (both non-release
architectures, admittedly) have been failing with nearly identical errors.

ppc64: /<>/test/qt/functionmapping.cpp(97): error: in 
"FUNCTIONMAPPING/call": check metaclass->function("f4").call(object, 
camp::Args(1, 4, 15)).to() == 20 has failed [22 != 20]

sparc64: /<>/test/qt/functionmapping.cpp(97): error: in 
"FUNCTIONMAPPING/call": check metaclass->function("f4").call(object, 
camp::Args(1, 4, 15)).to() == 20 has failed [21 != 20]

Both are big-endian 64-bit architectures, but so is s390x, which
(perhaps by chance?) ran into no trouble on this front.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: camp
Source-Version: 0.8.2-1

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

Debian distribution maintenance software
pp.
Flavien Bridault  (supplier of updated camp 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: Mon, 16 Apr 2018 16:33:23 +0200
Source: camp
Binary: libcamp0.8 libcamp-dev
Architecture: source
Version: 0.8.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Flavien Bridault 
Description:
 libcamp-dev - C++ multi-purpose reflection library (development files)
 libcamp0.8 - C++ multi-purpose reflection library
Closes: 876147
Changes:
 camp (0.8.2-1) unstable; urgency=medium
 .
   [ Flavien Bridault ]
   * New upstream version 0.8.2. Closes: #876147
   * d/patches: Remove obsolete hide_boost_from_qt4moc.patch
 .
   [ Andreas Tille ]
   * Use `cme fix dpkg-control` to
  - Update Standards-Version: 4.1.4
  - Point Vcs fields to salsa.debian.org
   * debhelper 11
Checksums-Sha1:
 cbcb92de2138ca4829130193ad45d946007fbf7b 2015 camp_0.8.2-1.dsc
 729007bcf23d54f8aa6d7879feb44c47faea9392 548100 camp_0.8.2.orig.tar.gz
 51c7f7d6ad07e5217c9d115b00468af74ec4e9d6 3544 camp_0.8.2-1.debian.tar.xz
Checksums-Sha256:
 02cdff7431999bfa4473c96e773b07c62d1fbc8f90a34bac26c613f26518cbd7 2015 
camp_0.8.2-1.dsc
 d793b665ed92ebf83b1e4e9f77350121fcef5ecf3ddfed52d20a1109c04efb71 548100 
camp_0.8.2.orig.tar.gz
 8b9b28bd050c99750e09794af87e0f5047d1d192da8a7320b356cc1d172bd9cf 3544 
camp_0.8.2-1.debian.tar.xz
Files:
 0bc693d0cc8c8fcd7a70c1d9ec736f55 2015 science optional camp_0.8.2-1.dsc
 e3a5026724f158cd66f48b837adf 548100 science optional camp_0.8.2.orig.tar.gz
 2d396b32b95c0bb76e33fcbac1a61ea0 3544 science optional 
camp_0.8.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlrUtzYOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtFrOg//YsdxZqbkAu/sp5XiFvpM0Xl/2/8wGdHanP25
2Xr+MfNbOGHg/ZaPr/F31CgAgbyd9aF0bKNv30J9JsvOoST3ghVLmPHBqNf9bYt7
VvEaqBA/lITb3mXj3EXV9S2wzWje7qkTXGd7UZvXV8pWYdazy/JysTGMui4uKI6Y
rTZamKRNEPi1JGHjXlJbS20L4DKb+lPI62SuleGUt3zCMqORALWstTht0/C/XYrk
SDq8HpyIR29KSucI4OrZxMVxM7/gp7Zfap6f3M1nrUazEB4kDXFJ1nH2mUeuOvLJ
31AbWghyIGPYVwFJyGMK1e7qmQ6fYmo/yEfMe1nhDsG2SocY0vcfyf3gpy8J8CeH
sddJK3ZkH5nNiMZw7lSzUCxJ88ZE5h4dsO03Y/SK/Q04R969FO9rVNanjCa8oirS
yHH+3x/5ojp5MiWi7oKfYBnB6Yzo8kmbGBcGqsD9ma0fwr5iV7o3GQ8zZgh+QSIy
xvl/w6fBojfVjShmtlm2sMRuitL5qmyAuaLisxaQwBNIarTrGDh2G1VtvOchZDth

Bug#887630: Bug#887360: wget2 FTBFS with glibc 2.26

[Boyuan Yang]

Hi Noel,

Is there any plan to fix this RC bug recently？The needed 
patch is already merged upstream.

Besides merging this patch, it might be better if upstream git 
HEAD version (or wget2 v1.99 as upstream tagged) could be 
packaged here in Debian.

--
Regards,
Boyuan Yang

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

Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[Flavien Bridault]

Thanks for the cleaning and the upload.

I should keep in mind to run `cme fix dpkg-control` each time.


Cheers,


Le 16/04/2018 à 16:49, Andreas Tille a écrit :
> Hi Flavien,
>
> thanks a lot for working on this.
>
> On Mon, Apr 16, 2018 at 04:07:46PM +0200, Flavien Bridault wrote:
>> This looks ok for me now, I updated to 0.8.2 which includes the fix
>> proposal. Please upload if that looks ok for you.
> I had some packaging updates and thus deleted your tag.  Please delete
> in your local repository and pull.
>
> The package is uploaded now.
>
> Kind regards
>
>Andreas.
>

-- 
*Flavien BRIDAULT*
Ingénieur de Recherche

fbrida...@ircad.fr

*IRCAD France*
1, place de l'Hôpital - 67091 Strasbourg Cedex - FRANCE

http://www.ircad.fr/ 




signature.asc
Description: OpenPGP digital signature

Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[Andreas Tille]

Hi Flavien,

thanks a lot for working on this.

On Mon, Apr 16, 2018 at 04:07:46PM +0200, Flavien Bridault wrote:
> This looks ok for me now, I updated to 0.8.2 which includes the fix
> proposal. Please upload if that looks ok for you.

I had some packaging updates and thus deleted your tag.  Please delete
in your local repository and pull.

The package is uploaded now.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#895467: libsearpc FTBFS on 64bit big endian: test failure

[Moritz Schlarb]

Hi Adrian and thanks for your response,

On 16.04.2018 15:13, Adrian Bunk wrote:
> Third solution:
> Fix the bugs.

Well that was actually the first solution I meant, but I just didn't
have much hope finding a solution, so thank you very much for your help.

> After fixing the two above bugs, libsearpc builds on s390x.

I've added patches to the package and will send them upstream.

> An en passant finding (not required to fix the FTBFS) is the following 
> that is documented to be unsupported, and might break on any 
> architecture at any time:
> https://sources.debian.org/src/libsearpc/3.0.8-3/lib/searpc-named-pipe-transport.c/#L236

I will report that to upstream, too.

Thx,
Moritz



signature.asc
Description: OpenPGP digital signature

Bug#894993: patch: CVE-2018-1000156: input validation vulnerability when processing patch files

[Chris Lamb]

[adding t...@security.debian.org to CC]

Hi,

> patch: CVE-2018-1000156: input validation vulnerability when processing
> patch files

I've fixed this in wheezy; would you like for an update for jessie and
stretch whilst it's fresh in my mind? The patch (hah!) did require some
modification for wheezy after all.

Let me know.


Best wishes,

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

Bug#895765: igv: FTBFS with java 9

[Andreas Tille]

Hi Olivier,

could you provide a patch assumed we'll stick to Java 9 and higher?

(Could you also have a look into artemis, htsjdk and picard-tools
if your time permits?)

Kind regards

  Andreas.

On Mon, Apr 16, 2018 at 10:17:57AM +0200, Olivier Sallou wrote:
> 
> 
> On 04/16/2018 09:32 AM, Bas Couwenberg wrote:
> > On 2018-04-16 08:18, Andreas Tille wrote:
> >> it seems something has changed with openfx since the errors below are
> >> all mentioning something like "import javafx. ...".  Do you have any
> >> hint how this can be fixed?
> >
> > There is no OpenJFX for OpenJDK 9, see:
> >
> >  https://lists.debian.org/debian-java/2018/04/msg3.html
> 
> indeed Java 9 removed some packages from *core* java and were moved to
> additional modules to add at compilation/runtime.
> Problem is this is not transparent/compatible with java <= 8.
> So, to support java 9 AND below, you need specific scripts that detect
> java version and act accordingly. This is not really cool to do and
> maintain.
> 
> As proposed, either javafx can be removed from code, either we shoud
> stick to Java 9 and superior and add the javafx module.
> there is an example in biojava4 for a build.xml:
> 
> 
>        
>           
>           
>   .
> 
> this example used java.se.ee module.
> 
> For javafx, there are several modules [0]:
> 
> * Base APIs for JavaFX UI Toolkit — javafx.base
> * JavaFX APIs for UI Controls — javafx.controls
> * JavaFX APIs for FXML — javafx.fxml
> * JavaFX APIs for various Graphics Tools— javafx.graphics
> * JavaFX APIs for Multimedia — javafx.media
> * JavaFX APIs for Swing-JavaFX Interoperability — javafx.swing
> * JavaFX APIs for WebView Functionality — javafx.web
> 
> 
> To add multiple modules, one need to separate them with comma.
> 
> [0]
> https://medium.com/@afinlay/whats-new-in-java-fx-java-9-updates-a90dd3d4dbba
> 
> 
> 
> >
> > If the package works without JavaFX you should consider disabling that
> > for the time being.
> >
> > You can also explicitly build with OpenJDK 8, but that will just get
> > you a different RC bug because openjdk-8 will not be in buster.
> >
> > Kind Regards,
> >
> > Bas
> >
> 
> -- 
> Olivier Sallou
> Univ Rennes, Inria, CNRS, IRISA
> Irisa, Campus de Beaulieu
> F-35042 RENNES - FRANCE
> Tel: 02.99.84.71.95
> 
> gpg key id: 4096R/326D8438  (keyring.debian.org)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
> 
> 
> 

-- 
http://fam-tille.de

Bug#876147: [Debian-med-packaging] Bug#876147: Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[Flavien Bridault]

Hi guys,

This looks ok for me now, I updated to 0.8.2 which includes the fix
proposal. Please upload if that looks ok for you.

Cheers,


Le 16/04/2018 à 14:47, Flavien Bridault a écrit :
> Ok great, as soon as the merge request is accepted upstream, which
> should happen very soon, I'll propose the update.
>
> Thanks a lot for testing this.
>
> Le 16/04/2018 à 14:34, John Paul Adrian Glaubitz a écrit :
>> On 04/16/2018 02:21 PM, Flavien Bridault wrote:
>>> Sorry the patch is ofc meant to be applied on the raw upstream, not
>>> after debian patches being applied. I was applying it directly into the
>>> git repo so that's why I did not have any issue. If you want to keep
>>> trying it this way, I attached a rebased version of the patch that
>>> should apply well on top of other.
>> Ok, this works:
>>
>> (sid_s390x-dchroot)glaubitz@zelenka:~/camp/camp-0.8.1/obj-s390x-linux-gnu$
>> make test
>> Running tests...
>> /usr/bin/ctest --force-new-ctest-process
>> Test project /home/glaubitz/camp/camp-0.8.1/obj-s390x-linux-gnu
>>     Start 1: camptest
>> 1/2 Test #1: camptest .   Passed    0.01 sec
>>     Start 2: camptest-qt
>> 2/2 Test #2: camptest-qt ..   Passed    0.00 sec
>>
>> 100% tests passed, 0 tests failed out of 2
>>
>> Total Test time (real) =   0.02 sec
>> (sid_s390x-dchroot)glaubitz@zelenka:~/camp/camp-0.8.1/obj-s390x-linux-gnu$
>>
>>
>
>
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
*Flavien BRIDAULT*
Ingénieur de Recherche

fbrida...@ircad.fr

*IRCAD France*
1, place de l'Hôpital - 67091 Strasbourg Cedex - FRANCE

http://www.ircad.fr/ 



signature.asc
Description: OpenPGP digital signature

Bug#895467: libsearpc FTBFS on 64bit big endian: test failure

[Adrian Bunk]

On Mon, Apr 16, 2018 at 12:09:36PM +0200, Moritz Schlarb wrote:
>...
> Two other "solutions", I can think of would be:
> - Using a switch on the current architecture in debian/rules to just
> don't test on these arches
> - Exclude the arches from Architecture: in debian/control
>...

Third solution:
Fix the bugs.

This happens to work on 64bit little endian, but passing a pointer to
a 64bit variable for a 32bit value is wrong:
https://sources.debian.org/src/libsearpc/3.0.8-3/lib/searpc-named-pipe-transport.c/#L255

Same problem as above, I'd bet the "len = 0" was added as "fix" when 
this bug hit on 64bit little endian:
https://sources.debian.org/src/libsearpc/3.0.8-3/lib/searpc-named-pipe-transport.c/#L224

After fixing the two above bugs, libsearpc builds on s390x.

An en passant finding (not required to fix the FTBFS) is the following 
that is documented to be unsupported, and might break on any 
architecture at any time:
https://sources.debian.org/src/libsearpc/3.0.8-3/lib/searpc-named-pipe-transport.c/#L236

> Best regards,
> Moritz

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#876147: [Debian-med-packaging] Bug#876147: Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[Flavien Bridault]

Ok great, as soon as the merge request is accepted upstream, which
should happen very soon, I'll propose the update.

Thanks a lot for testing this.

Le 16/04/2018 à 14:34, John Paul Adrian Glaubitz a écrit :
> On 04/16/2018 02:21 PM, Flavien Bridault wrote:
>> Sorry the patch is ofc meant to be applied on the raw upstream, not
>> after debian patches being applied. I was applying it directly into the
>> git repo so that's why I did not have any issue. If you want to keep
>> trying it this way, I attached a rebased version of the patch that
>> should apply well on top of other.
>
> Ok, this works:
>
> (sid_s390x-dchroot)glaubitz@zelenka:~/camp/camp-0.8.1/obj-s390x-linux-gnu$
> make test
> Running tests...
> /usr/bin/ctest --force-new-ctest-process
> Test project /home/glaubitz/camp/camp-0.8.1/obj-s390x-linux-gnu
>     Start 1: camptest
> 1/2 Test #1: camptest .   Passed    0.01 sec
>     Start 2: camptest-qt
> 2/2 Test #2: camptest-qt ..   Passed    0.00 sec
>
> 100% tests passed, 0 tests failed out of 2
>
> Total Test time (real) =   0.02 sec
> (sid_s390x-dchroot)glaubitz@zelenka:~/camp/camp-0.8.1/obj-s390x-linux-gnu$
>
>

-- 
*Flavien BRIDAULT*
Ingénieur de Recherche

fbrida...@ircad.fr

*IRCAD France*
1, place de l'Hôpital - 67091 Strasbourg Cedex - FRANCE

http://www.ircad.fr/ 




signature.asc
Description: OpenPGP digital signature

Bug#893231: marked as done (libcommons-lang3-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 12:50:18 +
with message-id 
and subject line Bug#893231: fixed in libcommons-lang3-java 3.5-2
has caused the Debian Bug report #893231,
regarding libcommons-lang3-java FTBFS with openjdk-9
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.)


-- 
893231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcommons-lang3-java
Version: 3.5-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcommons-lang3-java.html

...
[ERROR] Tests run: 15, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.206 
s <<< FAILURE! - in org.apache.commons.lang3.LocaleUtilsTest
[ERROR] testParseAllLocales(org.apache.commons.lang3.LocaleUtilsTest)  Time 
elapsed: 0.192 s  <<< ERROR!
java.lang.IllegalArgumentException: Invalid locale format: ji_001
at 
org.apache.commons.lang3.LocaleUtilsTest.testParseAllLocales(LocaleUtilsTest.java:578)
--- End Message ---
--- Begin Message ---
Source: libcommons-lang3-java
Source-Version: 3.5-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated libcommons-lang3-java 
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: Mon, 16 Apr 2018 14:30:12 +0200
Source: libcommons-lang3-java
Binary: libcommons-lang3-java libcommons-lang3-java-doc
Architecture: source
Version: 3.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libcommons-lang3-java - Extension of the java.lang package (for Java 5+)
 libcommons-lang3-java-doc - Documentation for extension of the java.lang 
package (for Java 5+
Closes: 893231
Changes:
 libcommons-lang3-java (3.5-2) unstable; urgency=medium
 .
   * Team upload.
   * Use compat level 11.
   * Declare compliance with Debian Policy 4.1.4.
   * Set source/target to 1.7.
   * Ignore the test failures with Java 9. (Closes: #893231)
Checksums-Sha1:
 ee9698dda44d1750c3ce6633e2444f917b7c9eb9 2538 libcommons-lang3-java_3.5-2.dsc
 546a504c019166106018f84d00564170b004d0d4 4380 
libcommons-lang3-java_3.5-2.debian.tar.xz
 0c85ce8ec3236812d3b698055d140f1fbb8d4807 16201 
libcommons-lang3-java_3.5-2_amd64.buildinfo
Checksums-Sha256:
 e49f08ed85c753d1af6d31b606ac088bacb2b90b941cb61c067c72fcbd3841f9 2538 
libcommons-lang3-java_3.5-2.dsc
 f324a41698c80756fd0d7f4eeb070d4f25304bbbf7f88a0a383dd7ced09caa4e 4380 
libcommons-lang3-java_3.5-2.debian.tar.xz
 4d38fc3b3301d19d321b9850b0f9dab254bcff051377ed7a4f4b1cfd572eaa61 16201 
libcommons-lang3-java_3.5-2_amd64.buildinfo
Files:
 a6419a03c0d5375d45dd007ddaaf9164 2538 java optional 
libcommons-lang3-java_3.5-2.dsc
 ef9f01ea0202cadb7761561d67eddca1 4380 java optional 
libcommons-lang3-java_3.5-2.debian.tar.xz
 3e66b928595a7275402c8d88772b9112 16201 java optional 
libcommons-lang3-java_3.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlrUmC5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkyaUQALEbE1K8sYKcSExIpsxDzTuFIgpSUwbY/5OX
gDVlQTzIejwJ4B3Tz6v9nyClavvmWRwOsnWpIJ8mocZBfse6fWdUtfkMMOQYtY/o
UXkNpuuG+9Y0pDLQjW4yynagQnwD8K/4GeciPaW5qE+c093WvMgyQAXIRy3HtLVM
6tFXDjadyusYbXUB5DAeOFQzSHE/Ukpv6SYbMCwzxZ0JH6diL5SXway5oEYSo+v9
glZab3HvQtbvzQS9Q3J7xD5TiajJ+7JXf8HMyfwDVsDT8qkM62u5c25FNjkl6wXO
hX+qm6ctnHMIut7eKfKcOzRvk6zNrZiji1t+iN+iFP/rA5AzTy94s75Te2/l6cR/
Iqz/8HWUdtVug3+ewQB0RI8h0AnNBcBANrLTWljcvumcMqSTfa4MwvgLNhL+GCba
j8RK2T+SjzZzDMxlt2gCa3c0RwwkAbGbjL1o44bUMbuQm8jTx0q7cYLgMmRfQPRp
gGyHq3TCbrd0cizZWu7vOS1i5b33neGtb6WuOrkbB1AZDiR0MLjfJiTp/P5TDEz5
dc8I0UdmpNH+QEkknLoY1MU/lo4VJ3RuJDpjG7TmWMeb1pW0IYITNdTBO9JJmXo1

Processed: Pending fixes for bugs in the libcommons-lang3-java package

[Debian Bug Tracking System]

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

> tag 893231 + pending
Bug #893231 [src:libcommons-lang3-java] libcommons-lang3-java FTBFS with 
openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893231: Pending fixes for bugs in the libcommons-lang3-java package

[pkg-java-maintainers]

tag 893231 + pending
thanks

Some bugs in the libcommons-lang3-java package are closed in revision
80abafe355c8287e07146d285ed13e30e1f0212f in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libcommons-lang3-java.git/commit/?id=80abafe

Commit message:

Ignore the test failures with Java 9.

Closes: #893231

Bug#876147: [Debian-med-packaging] Bug#876147: Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[John Paul Adrian Glaubitz]

On 04/16/2018 02:21 PM, Flavien Bridault wrote:

Sorry the patch is ofc meant to be applied on the raw upstream, not
after debian patches being applied. I was applying it directly into the
git repo so that's why I did not have any issue. If you want to keep
trying it this way, I attached a rebased version of the patch that
should apply well on top of other.


Ok, this works:

(sid_s390x-dchroot)glaubitz@zelenka:~/camp/camp-0.8.1/obj-s390x-linux-gnu$ make 
test
Running tests...
/usr/bin/ctest --force-new-ctest-process
Test project /home/glaubitz/camp/camp-0.8.1/obj-s390x-linux-gnu
Start 1: camptest
1/2 Test #1: camptest .   Passed0.01 sec
Start 2: camptest-qt
2/2 Test #2: camptest-qt ..   Passed0.00 sec

100% tests passed, 0 tests failed out of 2

Total Test time (real) =   0.02 sec
(sid_s390x-dchroot)glaubitz@zelenka:~/camp/camp-0.8.1/obj-s390x-linux-gnu$

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#876147: [Debian-med-packaging] Bug#876147: Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[Flavien Bridault]

Sorry the patch is ofc meant to be applied on the raw upstream, not
after debian patches being applied. I was applying it directly into the
git repo so that's why I did not have any issue. If you want to keep
trying it this way, I attached a rebased version of the patch that
should apply well on top of other.


Le 16/04/2018 à 13:49, John Paul Adrian Glaubitz a écrit :
> On 04/16/2018 11:58 AM, Flavien Bridault wrote:
>> Weird, it applies well for me on the master branch of the debian
>> repository. Try the patch attached to this email or directly this link
>>
>> https://patch-diff.githubusercontent.com/raw/fw4spl-org/camp/pull/2.diff
>
> Tried to apply against the current package in Debian unstable:
>
> glaubitz@zelenka:~$ md5sum fix-s390.diff
> 3fae8e5c44e239e74e2ef14a667126b4  fix-s390.diff
> glaubitz@zelenka:~$ cd camp/
> glaubitz@zelenka:~/camp$ dget -u
> http://deb.debian.org/debian/pool/main/c/camp/camp_0.8.1-2.dsc
> dget: retrieving
> http://deb.debian.org/debian/pool/main/c/camp/camp_0.8.1-2.dsc
>   % Total    % Received % Xferd  Average Speed   Time    Time
> Time  Current
>  Dload  Upload   Total   Spent   
> Left  Speed
> 100   321  100   321    0 0   4346  0 --:--:-- --:--:--
> --:--:--  4397
> 100  2000  100  2000    0 0  20750  0 --:--:-- --:--:--
> --:--:-- 20750
> dget: retrieving
> http://deb.debian.org/debian/pool/main/c/camp/camp_0.8.1.orig.tar.gz
>   % Total    % Received % Xferd  Average Speed   Time    Time
> Time  Current
>  Dload  Upload   Total   Spent   
> Left  Speed
> 100   327  100   327    0 0   4570  0 --:--:-- --:--:--
> --:--:--  4605
> 100  534k  100  534k    0 0  4044k  0 --:--:-- --:--:--
> --:--:-- 4044k
> dget: retrieving
> http://deb.debian.org/debian/pool/main/c/camp/camp_0.8.1-2.debian.tar.xz
>   % Total    % Received % Xferd  Average Speed   Time    Time
> Time  Current
>  Dload  Upload   Total   Spent   
> Left  Speed
> 100   331  100   331    0 0   4809  0 --:--:-- --:--:--
> --:--:--  4867
> 100  5272  100  5272    0 0  63979  0 --:--:-- --:--:--
> --:--:-- 63979
> dpkg-source: info: extracting camp in camp-0.8.1
> dpkg-source: info: unpacking camp_0.8.1.orig.tar.gz
> dpkg-source: info: unpacking camp_0.8.1-2.debian.tar.xz
> dpkg-source: info: applying remove_licences_files.patch
> dpkg-source: info: applying hide_boost_from_qt4moc.patch
> glaubitz@zelenka:~/camp$ cd camp-0.8.1/
> glaubitz@zelenka:~/camp/camp-0.8.1$ patch -p1 < ~/fix-s390x.patch
> patching file .gitignore
> patching file include/camp/qt/qtfunction.hpp
> patching file include/camp/qt/qthelper.hpp
> patching file include/camp/valuemapper.hpp
> Hunk #2 FAILED at 40.
> Hunk #3 succeeded at 96 (offset 2 lines).
> Hunk #4 succeeded at 126 (offset 2 lines).
> Hunk #5 succeeded at 139 (offset 2 lines).
> Hunk #6 succeeded at 156 (offset 2 lines).
> Hunk #7 succeeded at 183 (offset 2 lines).
> Hunk #8 succeeded at 205 (offset 2 lines).
> Hunk #9 succeeded at 234 (offset 2 lines).
> Hunk #10 succeeded at 250 (offset 2 lines).
> Hunk #11 succeeded at 279 (offset 2 lines).
> Hunk #12 succeeded at 326 (offset 2 lines).
> Hunk #13 succeeded at 345 (offset 2 lines).
> 1 out of 13 hunks FAILED -- saving rejects to file
> include/camp/valuemapper.hpp.rej
> patching file test/arrayproperty.hpp
> Hunk #2 FAILED at 32.
> Hunk #3 succeeded at 78 (offset 2 lines).
> 1 out of 3 hunks FAILED -- saving rejects to file
> test/arrayproperty.hpp.rej
> patching file test/qt/propertymapping.cpp
> Hunk #2 succeeded at 34 with fuzz 2 (offset 2 lines).
> Hunk #3 succeeded at 47 (offset 2 lines).
> Hunk #4 succeeded at 95 (offset 2 lines).
> Hunk #5 succeeded at 106 (offset 2 lines).
> glaubitz@zelenka:~/camp/camp-0.8.1$
>

-- 
*Flavien BRIDAULT*
Ingénieur de Recherche

fbrida...@ircad.fr

*IRCAD France*
1, place de l'Hôpital - 67091 Strasbourg Cedex - FRANCE

http://www.ircad.fr/ 

diff -uNr camp-0.8.1.old/.gitignore camp-0.8.1/.gitignore
--- camp-0.8.1.old/.gitignore	2018-04-16 14:08:14.403457120 +0200
+++ camp-0.8.1/.gitignore	2018-04-16 14:08:19.987457060 +0200
@@ -28,6 +28,7 @@
 *.o
 *.a
 moc_*
+build/
 
 *.cmake
 CMakeFiles/
diff -uNr camp-0.8.1.old/include/camp/qt/qtfunction.hpp camp-0.8.1/include/camp/qt/qtfunction.hpp
--- camp-0.8.1.old/include/camp/qt/qtfunction.hpp	2018-04-16 14:08:14.411457120 +0200
+++ camp-0.8.1/include/camp/qt/qtfunction.hpp	2018-04-16 14:08:19.987457060 +0200
@@ -15,10 +15,10 @@
 ** to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 ** copies of the Software, and to permit persons to whom the Software is
 ** furnished to do so, subject to the following conditions:
-** 
+**
 ** The above copyright notice and this permission notice shall be included in
 ** all copies or substantial portions of the Software.
-** 
+**
 ** THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 ** 

Processed: Upstream tickets

[Debian Bug Tracking System]

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

> forwarded 895496 https://github.com/mgba-emu/mgba/pull/943
Bug #895496 [src:mgba] mgba FTBFS with Qt 5.10
Set Bug forwarded-to-address to 'https://github.com/mgba-emu/mgba/pull/943'.
> tags  895496 fixed-upstream
Bug #895496 [src:mgba] mgba FTBFS with Qt 5.10
Added tag(s) fixed-upstream.
> forwarded 895500 https://github.com/slim-template/slim/issues/742
Bug #895500 [src:ruby-slim] ruby-slim FTBFS with ruby-tilt 2.0.8-1
Set Bug forwarded-to-address to 
'https://github.com/slim-template/slim/issues/742'.
> stop
Stopping processing here.

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

Bug#893225: marked as done (libcommons-validator-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 12:05:10 +
with message-id 
and subject line Bug#893225: fixed in libcommons-validator-java 1:1.6-2
has caused the Debian Bug report #893225,
regarding libcommons-validator-java FTBFS with openjdk-9
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.)


-- 
893225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcommons-validator-java
Version: 1:1.6-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcommons-validator-java.html

...
[ERROR] Failures: 
[ERROR]   CalendarValidatorTest.testDateTimeStyle:197 validate(A) default
[ERROR]   CalendarValidatorTest.testFormat:215 default expected:<31/12/[]05> 
but was:<31/12/[20]05>
[ERROR]   CurrencyValidatorTest.testIntegerValid:142 US negative 
expected:<-1234.00> but was:
[ERROR]   CurrencyValidatorTest.testInvalid:121 US wrong negative
[ERROR]   CurrencyValidatorTest.testValid:93 US negative expected:<-1234.56> 
but was:
[ERROR]   DateValidatorTest.testDateValidatorMethods:69 validate(A) both 
expected: but was:
[ERROR]   TimeValidatorTest.testLocaleValid:157 compare 0 value=[23:59] failed  
expected: but was:
[ERROR]   TimeValidatorTest.testPatternValid:131 compare 0 value=[23-59-59] 
failed  expected: but was:
[ERROR]   TimeValidatorTest.testTimeZone:219 pattern result
[ERROR] Errors: 
[ERROR]   CalendarValidatorTest.testCalendarValidatorMethods:70 NullPointer
[INFO] 
[ERROR] Tests run: 536, Failures: 9, Errors: 1, Skipped: 0
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 6.954 s
[INFO] Finished at: 2019-04-19T06:46:00-12:00
[INFO] Final Memory: 11M/38M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
project commons-validator: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/build/1st/libcommons-validator-java-1.6/target/surefire-reports for the 
individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/libcommons-validator-java-1.6 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/libcommons-validator-java-1.6/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/libcommons-validator-java-1.6/debian 
-Dmaven.repo.local=/build/1st/libcommons-validator-java-1.6/debian/maven-repo 
--batch-mode test returned exit code 1
make: *** [debian/rules:4: build] Error 1
--- End Message ---
--- Begin Message ---
Source: libcommons-validator-java
Source-Version: 1:1.6-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated 
libcommons-validator-java 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: Mon, 16 Apr 2018 13:19:01 +0200
Source: libcommons-validator-java
Binary: libcommons-validator-java libcommons-validator-java-doc
Architecture: source
Version: 1:1.6-2
Distribution: unstable
Urgency: medium
Maintainer: 

Bug#893225: Pending fixes for bugs in the libcommons-validator-java package

[pkg-java-maintainers]

tag 893225 + pending
thanks

Some bugs in the libcommons-validator-java package are closed in
revision 7a5a002ec04585e8e364cdf605dfa8ad2ad9e547 in branch 'master'
by Markus Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libcommons-validator-java.git/commit/?id=7a5a002

Commit message:

Ignore the test failures with Java 9.

Closes: #893225

Processed: Pending fixes for bugs in the libcommons-validator-java package

[Debian Bug Tracking System]

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

> tag 893225 + pending
Bug #893225 [src:libcommons-validator-java] libcommons-validator-java FTBFS 
with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#876147: [Debian-med-packaging] Bug#876147: Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[John Paul Adrian Glaubitz]

On 04/16/2018 11:58 AM, Flavien Bridault wrote:

Weird, it applies well for me on the master branch of the debian
repository. Try the patch attached to this email or directly this link

https://patch-diff.githubusercontent.com/raw/fw4spl-org/camp/pull/2.diff


Tried to apply against the current package in Debian unstable:

glaubitz@zelenka:~$ md5sum fix-s390.diff
3fae8e5c44e239e74e2ef14a667126b4  fix-s390.diff
glaubitz@zelenka:~$ cd camp/
glaubitz@zelenka:~/camp$ dget -u 
http://deb.debian.org/debian/pool/main/c/camp/camp_0.8.1-2.dsc
dget: retrieving http://deb.debian.org/debian/pool/main/c/camp/camp_0.8.1-2.dsc
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100   321  100   3210 0   4346  0 --:--:-- --:--:-- --:--:--  4397
100  2000  100  20000 0  20750  0 --:--:-- --:--:-- --:--:-- 20750
dget: retrieving 
http://deb.debian.org/debian/pool/main/c/camp/camp_0.8.1.orig.tar.gz
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100   327  100   3270 0   4570  0 --:--:-- --:--:-- --:--:--  4605
100  534k  100  534k0 0  4044k  0 --:--:-- --:--:-- --:--:-- 4044k
dget: retrieving 
http://deb.debian.org/debian/pool/main/c/camp/camp_0.8.1-2.debian.tar.xz
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100   331  100   3310 0   4809  0 --:--:-- --:--:-- --:--:--  4867
100  5272  100  52720 0  63979  0 --:--:-- --:--:-- --:--:-- 63979
dpkg-source: info: extracting camp in camp-0.8.1
dpkg-source: info: unpacking camp_0.8.1.orig.tar.gz
dpkg-source: info: unpacking camp_0.8.1-2.debian.tar.xz
dpkg-source: info: applying remove_licences_files.patch
dpkg-source: info: applying hide_boost_from_qt4moc.patch
glaubitz@zelenka:~/camp$ cd camp-0.8.1/
glaubitz@zelenka:~/camp/camp-0.8.1$ patch -p1 < ~/fix-s390x.patch
patching file .gitignore
patching file include/camp/qt/qtfunction.hpp
patching file include/camp/qt/qthelper.hpp
patching file include/camp/valuemapper.hpp
Hunk #2 FAILED at 40.
Hunk #3 succeeded at 96 (offset 2 lines).
Hunk #4 succeeded at 126 (offset 2 lines).
Hunk #5 succeeded at 139 (offset 2 lines).
Hunk #6 succeeded at 156 (offset 2 lines).
Hunk #7 succeeded at 183 (offset 2 lines).
Hunk #8 succeeded at 205 (offset 2 lines).
Hunk #9 succeeded at 234 (offset 2 lines).
Hunk #10 succeeded at 250 (offset 2 lines).
Hunk #11 succeeded at 279 (offset 2 lines).
Hunk #12 succeeded at 326 (offset 2 lines).
Hunk #13 succeeded at 345 (offset 2 lines).
1 out of 13 hunks FAILED -- saving rejects to file 
include/camp/valuemapper.hpp.rej
patching file test/arrayproperty.hpp
Hunk #2 FAILED at 32.
Hunk #3 succeeded at 78 (offset 2 lines).
1 out of 3 hunks FAILED -- saving rejects to file test/arrayproperty.hpp.rej
patching file test/qt/propertymapping.cpp
Hunk #2 succeeded at 34 with fuzz 2 (offset 2 lines).
Hunk #3 succeeded at 47 (offset 2 lines).
Hunk #4 succeeded at 95 (offset 2 lines).
Hunk #5 succeeded at 106 (offset 2 lines).
glaubitz@zelenka:~/camp/camp-0.8.1$

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#895811: inotify-tools: do not enable sanitizers in production

[James Cowgill]

Source: inotify-tools
Version: 3.14-4
Severity: grave

Hi,

In inotify-tools 3.14-4, all the qa sanitizers were enabled in
DEB_BUILD_MAINT_OPTIONS. This should not be done in production.

* Many architectures do not support sanitizers. Your package FTBFS on
mips* due to this. While clang supports ASan on mips, gcc does not.

* The man page for dpkg-buildflags explicitly states these options
should not be used in production builds and are for debugging only.

* Enabling sanitizers causes an approx 2x performance penalty.

* Enabling ASan changes the behavior of a program in some circumstances
(mainly relating to memory management and things like LD_PRELOAD no
longer work without hacks). Enabling ASan in a library package is even
worse because you will impose these behavior changes on all users of
your library who may not be expecting them.

* ASan complains about memory leaks and these are easy to reproduce with
inotify-tools. While this is very useful during development, I do not
think users should be subjected to these types of bugs which are mostly
harmless. Eg run inotifywait without any arguments are ASan will
complain loudly.

* Users of libinotifytools0 must now enable ASan themselves or use the
LD_PRELOAD hack otherwise they will not start. For example, the attached
simple test program fails to run with:

==19349==ASan runtime does not come first in initial library list; you
should either link runtime to your application or manually preload it
with LD_PRELOAD.

Thanks,
James
#include 

int main(void)
{
inotifytools_initialize();
return 0;
}


signature.asc
Description: OpenPGP digital signature

Bug#853436: marked as done (gtkmathview: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 10:21:15 +
with message-id 
and subject line Bug#853436: fixed in gtkmathview 0.8.0-15
has caused the Debian Bug report #853436,
regarding gtkmathview: ftbfs with GCC-7
to be marked as done.

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

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


-- 
853436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gtkmathview
Version: 0.8.0-14
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/gtkmathview_0.8.0-14_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
  SVG yes
  PostScript  yes

Performance

  Builder cache   no

touch debian/stamp-autotools
/usr/bin/make -C . 
make[1]: Entering directory '/<>'
/usr/bin/make  all-recursive
make[2]: Entering directory '/<>'
Making all in scripts
make[3]: Entering directory '/<>/scripts'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/scripts'
Making all in config
make[3]: Entering directory '/<>/config'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/<>/config'
Making all in auto
make[3]: Entering directory '/<>/auto'
g++ -DHAVE_CONFIG_H -I. -I.. -I../src/common -I../src/frontend/gmetadom -I.. 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libxml2 -I/usr/include/gmetadom/gdome_cpp_smart 
-I/usr/include/libgdome   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -W -Wall -c -o dumpEntitiesTable.o dumpEntitiesTable.cc
In file included from 
/usr/include/gmetadom/gdome_cpp_smart/GdomeSmartDOMChar.hh:78:0,
 from 
/usr/include/gmetadom/gdome_cpp_smart/GdomeSmartDOMBasic.hh:27,
 from /usr/include/gmetadom/gdome_cpp_smart/GdomeSmartDOM.hh:27,
 from ../src/frontend/gmetadom/gmetadom.hh:22,
 from dumpEntitiesTable.cc:25:
/usr/include/gmetadom/gdome_cpp_smart/GdomeSmartDOMTraits.hh: In static member 
function 'static std::char_traits::char_type 
std::char_traits::to_char_type(const int_type&)':
/usr/include/gmetadom/gdome_cpp_smart/GdomeSmartDOMTraits.hh:102:25: warning: 
narrowing conversion of '(std::char_traits::int_type)__c' 
from 'std::char_traits::int_type {aka long unsigned int}' 
to 'std::char_traits::char_type {aka short unsigned int}' 
inside { } [-Wnarrowing]
   char_type __r = { __c };
 ^~~
/bin/bash ../libtool  --tag=CXX   --mode=link g++  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -W -Wall  -Wl,-z,relro -o dumpEntitiesTable 
dumpEntitiesTable.o -lgmetadom_gdome_cpp_smart -lgdome -lglib-2.0 -lxml2 
libtool: link: g++ -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -W -Wall -Wl,-z 
-Wl,relro -o dumpEntitiesTable dumpEntitiesTable.o  
/usr/lib/libgmetadom_gdome_cpp_smart.so /usr/lib/libgdome.so -lglib-2.0 -lxml2
dumpEntitiesTable.o: In function `dump(char const*)':
./auto/dumpEntitiesTable.cc:43: undefined reference to 
`GdomeSmartDOM::GdomeString::operator std::__cxx11::basic_string() const'
./auto/dumpEntitiesTable.cc:47: undefined reference to 
`GdomeSmartDOM::GdomeString::operator std::__cxx11::basic_string() const'
collect2: error: ld returned 1 exit status
Makefile:448: 

Bug#895467: libsearpc FTBFS on 64bit big endian: test failure

[Moritz Schlarb]

Hi there,

I'm unsure how to handle this.

The current breakage of the package since 3.0.8-2 comes from me
re-enabling the upstream tests, which were previously disabled with a
comment that they were broken upstream (so, at
https://buildd.debian.org/status/logs.php?pkg=libsearpc=3.0.8-1, all
builds ran fine but right now, they fail on some architectures - s390x,
ppc64 and sparc64:
https://buildd.debian.org/status/package.php?p=libsearpc).

Since the package still builds and tests fine on *most* architectures,
I'd beg to differ that the test suite is broken in general.

Now of course myself and upstream can look into the problem, but since
it maybe is specific to an exotic architecture that we might not have
access to, I would not have high hopes in that approach.

Two other "solutions", I can think of would be:
- Using a switch on the current architecture in debian/rules to just
don't test on these arches
- Exclude the arches from Architecture: in debian/control

Would any of those options be appropriate?

Best regards,
Moritz

On 11.04.2018 22:24, Adrian Bunk wrote:
> Source: libsearpc
> Version: 3.0.8-2
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=libsearpc=sid
> 
> ...
> FAIL: test-searpc
> =
> 
> Loaded 1 suites: 
> Started
> 
> (process:10121): Searpc-WARNING **: 17:59:21.601: failed to read rpc request: 
> Bad address
> 
> (process:10121): Searpc-WARNING **: 17:59:21.601: failed to read rpc 
> response: Connection reset by peer
> F
> (process:10121): Searpc-WARNING **: 17:59:21.923: failed to read rpc request: 
> Bad address
> 
> (process:10121): Searpc-WARNING **: 17:59:21.923: failed to send rpc call: 
> Broken pipe
> F
> (process:10121): Searpc-WARNING **: 17:59:22.122: failed to read rpc request: 
> Bad address
> 
> (process:10121): Searpc-WARNING **: 17:59:22.125: failed to read rpc 
> response: Connection reset by peer
> F
> 
>   1) Failure:
> searpc::pipe_simple_call [searpc.c:427]
>   Expression is not true: error == NULL
>   Transport Error
> 
>   2) Failure:
> searpc::pipe_large_request [searpc.c:454]
>   Expression is not true: error == NULL
>   Transport Error
> 
>   3) Failure:
> searpc::pipe_concurrent_clients [searpc.c:483]
>   Expression is not true: error == NULL
>   Transport Error
> 
> System error: `fork()` call failed (12) - Cannot allocate memory
> FAIL test-searpc (exit status: 255)
> 
> 
> Testsuite summary for libsearpc 3.0.8
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See tests/test-suite.log
> Please report to i...@seafile.com
> 
> make[5]: *** [Makefile:687: test-suite.log] Error 1
> 

Bug#876147: [Debian-med-packaging] Bug#876147: Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[Flavien Bridault]

Weird, it applies well for me on the master branch of the debian
repository. Try the patch attached to this email or directly this link

https://patch-diff.githubusercontent.com/raw/fw4spl-org/camp/pull/2.diff


Le 16/04/2018 à 11:21, John Paul Adrian Glaubitz a écrit :
> On 04/16/2018 11:16 AM, John Paul Adrian Glaubitz wrote:
>>> Meanwhile I commited a fix upstream
>>> (https://github.com/fw4spl-org/camp/pull/2) so I would just want to try
>>> it before proposing the fix in the package.
>> I'll test that for you on s390x.
>
> That patch doesn't apply to the Debian version of camp:
>
> glaubitz@zelenka:~/camp/camp-0.8.1$ patch -p1 < ~/fix-s390x.patch
> patching file .gitignore
> patching file include/camp/qt/qtfunction.hpp
> patching file include/camp/qt/qthelper.hpp
> patching file include/camp/valuemapper.hpp
> Hunk #2 FAILED at 40.
> Hunk #3 succeeded at 96 (offset 2 lines).
> Hunk #4 succeeded at 126 (offset 2 lines).
> Hunk #5 succeeded at 139 (offset 2 lines).
> Hunk #6 succeeded at 156 (offset 2 lines).
> Hunk #7 succeeded at 183 (offset 2 lines).
> Hunk #8 succeeded at 205 (offset 2 lines).
> Hunk #9 succeeded at 234 (offset 2 lines).
> Hunk #10 succeeded at 250 (offset 2 lines).
> Hunk #11 succeeded at 279 (offset 2 lines).
> Hunk #12 succeeded at 326 (offset 2 lines).
> Hunk #13 succeeded at 345 (offset 2 lines).
> 1 out of 13 hunks FAILED -- saving rejects to file
> include/camp/valuemapper.hpp.rej
> patching file test/arrayproperty.hpp
> Hunk #2 FAILED at 32.
> Hunk #3 succeeded at 78 (offset 2 lines).
> 1 out of 3 hunks FAILED -- saving rejects to file
> test/arrayproperty.hpp.rej
> patching file test/qt/propertymapping.cpp
> Hunk #2 succeeded at 34 with fuzz 2 (offset 2 lines).
> Hunk #3 succeeded at 47 (offset 2 lines).
> Hunk #4 succeeded at 95 (offset 2 lines).
> Hunk #5 succeeded at 106 (offset 2 lines).
> glaubitz@zelenka:~/camp/camp-0.8.1$
>

-- 
*Flavien BRIDAULT*
Ingénieur de Recherche

fbrida...@ircad.fr

*IRCAD France*
1, place de l'Hôpital - 67091 Strasbourg Cedex - FRANCE

http://www.ircad.fr/ 

diff --git a/.gitignore b/.gitignore
index ce734c4..9a073a8 100644
--- a/.gitignore
+++ b/.gitignore
@@ -28,6 +28,7 @@ qtc-gdbmacros/
 *.o
 *.a
 moc_*
+build/
 
 *.cmake
 CMakeFiles/
diff --git a/include/camp/qt/qtfunction.hpp b/include/camp/qt/qtfunction.hpp
index 96484ab..912383b 100644
--- a/include/camp/qt/qtfunction.hpp
+++ b/include/camp/qt/qtfunction.hpp
@@ -15,10 +15,10 @@
 ** to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 ** copies of the Software, and to permit persons to whom the Software is
 ** furnished to do so, subject to the following conditions:
-** 
+**
 ** The above copyright notice and this permission notice shall be included in
 ** all copies or substantial portions of the Software.
-** 
+**
 ** THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 ** IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 ** FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
@@ -86,7 +86,7 @@ class QtFunction : public camp::Function
 
 case 1:
 {
-QVariant arg1 = QtHelper::valueToVariant(args[0]);
+const auto arg1 = QtHelper::argumentToVariant(args[0], m_metaMethod.parameterType(0));
 m_metaMethod.invoke(object.get(), Qt::DirectConnection, ret
   , QGenericArgument(arg1.typeName(), arg1.data()));
 break;
@@ -94,8 +94,8 @@ class QtFunction : public camp::Function
 
 case 2:
 {
-QVariant arg1 = QtHelper::valueToVariant(args[0]);
-QVariant arg2 = QtHelper::valueToVariant(args[1]);
+const auto arg1 = QtHelper::argumentToVariant(args[0], m_metaMethod.parameterType(0));
+const auto arg2 = QtHelper::argumentToVariant(args[1], m_metaMethod.parameterType(1));
 m_metaMethod.invoke(object.get(), Qt::DirectConnection, ret
   , QGenericArgument(arg1.typeName(), arg1.data())
   , QGenericArgument(arg2.typeName(), arg2.data()));
@@ -104,9 +104,9 @@ class QtFunction : public camp::Function
 
 case 3:
 {
-QVariant arg1 = QtHelper::valueToVariant(args[0]);
-QVariant arg2 = QtHelper::valueToVariant(args[1]);
-QVariant arg3 = QtHelper::valueToVariant(args[2]);
+const auto arg1 = QtHelper::argumentToVariant(args[0], m_metaMethod.parameterType(0));
+const auto arg2 = QtHelper::argumentToVariant(args[1], m_metaMethod.parameterType(1));
+const auto arg3 = QtHelper::argumentToVariant(args[2], m_metaMethod.parameterType(2));
 m_metaMethod.invoke(object.get(), Qt::DirectConnection, ret
   , QGenericArgument(arg1.typeName(), arg1.data())
 

Bug#894083: marked as done (italc build-depends on gcj-jdk, which will be removed)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 09:30:40 +
with message-id 
and subject line Bug#894083: fixed in italc 1:3.0.3+dfsg1-3
has caused the Debian Bug report #894083,
regarding italc build-depends on gcj-jdk, which will be removed
to be marked as done.

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

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


-- 
894083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:italc
Version: 1:3.0.3+dfsg1-2
Tags: sid buster patch
Severity: serious

replace gcj-jdk with default-jdk.

http://launchpadlibrarian.net/362047893/italc_1%3A3.0.3+dfsg1-2build1_1%3A3.0.3+dfsg1-2ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: italc
Source-Version: 1:3.0.3+dfsg1-3

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated italc 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: Mon, 16 Apr 2018 10:39:33 +0200
Source: italc
Binary: italc-master italc-client italc-management-console libitalccore
Architecture: source
Version: 1:3.0.3+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Packaging Team 

Changed-By: Mike Gabriel 
Description:
 italc-client - intelligent Teaching And Learning with Computers - client
 italc-management-console - intelligent Teaching And Learning with Computers - 
management con
 italc-master - intelligent Teaching And Learning with Computers - master
 libitalccore - intelligent Teaching And Learning with Computers - libraries
Closes: 867760 885840 894083
Changes:
 italc (1:3.0.3+dfsg1-3) unstable; urgency=medium
 .
   [ Mike Gabriel ]
   * debian/control:
 + Drop Patrick Winnertz from the list of uploaders. Thanks for previous
   contributions. (Closes: #867760).
 .
   [ Pino Toscano ]
   * debian/control:
 + Recommend kdialog rather than kde-baseapps-bin. (Closes: #885840).
 .
   [ Adrian Bunk ]
   * debian/control:
 + Build with default-jdk instead of gcj-jdk. (Closes: #894083).
Checksums-Sha1:
 da48940f038119f7785100aea4954f1deed3a747 2540 italc_3.0.3+dfsg1-3.dsc
 f9536704e69bfe8fb02095819848685eb4ff48ea 70904 
italc_3.0.3+dfsg1-3.debian.tar.xz
 e540f596f1b898cc92e57fd0c3715b3734296366 16353 
italc_3.0.3+dfsg1-3_source.buildinfo
Checksums-Sha256:
 20d78a8020b001160db6df855b8bdb569db4932e5cbf4e7673f401cf819c31f9 2540 
italc_3.0.3+dfsg1-3.dsc
 3a3b8ae759a2ff8630539f00dcffaf3648b15a304f7c7a66da232d0a235ea362 70904 
italc_3.0.3+dfsg1-3.debian.tar.xz
 1b404ea60e24de79eec9e4159b39fa66e57dd96cbe0ec416288dd5e9aeca4126 16353 
italc_3.0.3+dfsg1-3_source.buildinfo
Files:
 044336a17515ab2a7c65a1a2964c77a1 2540 x11 optional italc_3.0.3+dfsg1-3.dsc
 b041b7d1a47c12baaeff02fd0a15cbff 70904 x11 optional 
italc_3.0.3+dfsg1-3.debian.tar.xz
 de8492ad2e141b9281e96f3013ed8692 16353 x11 optional 
italc_3.0.3+dfsg1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAlrUYzQVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx1yYQAJA4e0o1KvQo7nx4Jq4mfOeZkok1
o7AMT0kEvIGB+TbsJYVkJZ843NiNnV0E9Vlui/xluIEpUxeY3k3DtFLC1samwhEi
dAIdTE6DjutwjH9G7mkEDXhKG5039ewHVTswgG/CnoGVgrv60Myi33htoGtUGCxH
dxGtlR0lQsX5hTcnaSM0Uf1vZ5Vb6tbteVB5vEsQv6X7oyfvgQS2wI6sYOsFTX+n
0Qyf6Sbdm9sTF4IqV4xtRiV1Cc7QFdMa7W7kNaR5q8uK4AnPFvZOgPUsYXPJ6x6t
vn6QKBQhbWmDQbJcqmjNwjjnhb+J9x4ZBh2SXoiU1U95Jt0cEtaueysG4FnTjTor
L2WEkwlu7OS6quuPjZUN2sM2nVGL/ioDLk+Vk7sWUvzCH9AcdwSqpqJ3ZPWnI8Tw
46UOcpD3b8/HZK2hSQMGnF3rgQi6DA3E3wPvcaKt0slZxv5ZSvgfzoskHCYoClbq
sSEbd2p5zVqD1a+OSrSfxRBLXN1KJj92z1mmpwQ2lXj9iV7RtPD8fmo4K/FmsVB8
1ju8AscwAtxMvMYLxfCrjajQ68n7qxO85os35kuPagzsWvcCmTVqQfGYnH/cnvzJ
AIzmM8GmeJujr8uN9COxOyqLfUG309/RIPRQhucaJeLZovERAqDM+mm+iHIQRACc
wZX9pMIiZzJ7c/x6
=dgUX
-END PGP SIGNATURE End Message ---

Bug#895444: [Pkg-ayatana-devel] Bug#895444: Bug#895444: Uses deprecated NetworkManager.pc

[Mike Gabriel]

Hi Michael,

On  Sa 14 Apr 2018 20:58:01 CEST, Mike Gabriel wrote:


Hi,

On  Sa 14 Apr 2018 01:04:15 CEST, Michael Biebl wrote:


Control: severity -1 serious

Hi,

I intend to upload a new version of network-manager soonish which will
drop libnm-glib/libnm-util. I'm thus bumping this issue to RC in
preparation for that.

Regards,
Michael


Ouch (libqtdbusmock). I presume that I have to patch this for Debian  
instead of waiting for upstream to fix this.


Noted. Let's see what I can find...
Mike


I did the porting work (patch CMakeLists.txt and B-D on libnm-dev).

However, I get a fancy FTBFS, that may be caused by GLib rather then  
libqtdbusmock itself:


```
cd  
/<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu/src/libqtdbusmock && /usr/bin/c++  -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_NO_DEBUG -DQT_TESTCASE_BUILDDIR=\"/<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu\" -DQT_TESTLIB_LIB -Dqtdbusmock_EXPORTS -I/<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu/src/libqtdbusmock -I/<>/libqtdbusmock-0.7+bzr49+repack1/src/libqtdbusmock -I/<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu/src/libqtdbusmock/qtdbusmock_autogen/include -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtTest -I/usr/include/libqtdbustest-1 -I/usr/include/libnm -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/<>/libqtdbusmock-0.7+bzr49+repack1/src -I/<>/libqtdbusmock-0.7+bzr49+repack1/obj-x86_64-linux-gnu/src  -g -O2 -fdebug-prefix-map=/<>/libqtdbusmock-0.7+bzr49+repack1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -fvisibility-inlines-hidden -fPIC   -std=c++11 -fno-permissive -pedantic -Wall -Wextra -fPIC -std=gnu++11 -o CMakeFiles/qtdbusmock.dir/DBusMock.cpp.o -c  
/<>/libqtdbusmock-0.7+bzr49+repack1/src/libqtdbusmock/DBusMock.cpp
In file included from  
/usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:49:0,
 from  
/usr/include/x86_64-linux-gnu/qt5/QtDBus/qtdbusglobal.h:44,
 from  
/usr/include/x86_64-linux-gnu/qt5/QtDBus/qdbusconnection.h:44,
 from  
/usr/include/x86_64-linux-gnu/qt5/QtDBus/QDBusConnection:1,
 from  
/usr/include/libqtdbustest-1/libqtdbustest/DBusService.h:22,
 from  
/usr/include/libqtdbustest-1/libqtdbustest/DBusTestRunner.h:19,
 from  
/<>/libqtdbusmock-0.7+bzr49+repack1/src/libqtdbusmock/DBusMock.h:21,
 from  
/<>/libqtdbusmock-0.7+bzr49+repack1/src/libqtdbusmock/DBusMock.cpp:19:
/usr/include/glib-2.0/gio/gdbusintrospection.h:155:25: error: expected  
unqualified-id before 'public'

   GDBusSignalInfo **signals;
 ^
In file included from /usr/include/glib-2.0/gio/gio.h:54:0,
 from /usr/include/libnm/nm-types.h:24,
 from /usr/include/libnm/nm-object.h:29,
 from /usr/include/libnm/nm-access-point.h:29,
 from /usr/include/libnm/NetworkManager.h:26,
 from  
/<>/libqtdbusmock-0.7+bzr49+repack1/src/libqtdbusmock/DBusMock.cpp:22:
/usr/include/glib-2.0/gio/gdbusintrospection.h:155:24: error: expected  
';' at end of member declaration

   GDBusSignalInfo **signals;
^
/usr/include/glib-2.0/gio/gdbusintrospection.h:155:32: error: expected  
':' before ';' token

   GDBusSignalInfo **signals;
^
/usr/include/glib-2.0/gio/gdbusintrospection.h:155:32: warning: extra  
';' [-Wpedantic]

```

Have you seen this before? Any clue on where to look for the cause?

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpQ0EwgdIRN0.pgp
Description: Digitale PGP-Signatur

Bug#895772: marked as done (libpmix2 contains broken symlinks)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 09:31:27 +
with message-id 
and subject line Bug#895772: fixed in pmix 2.1.1~rc1-2
has caused the Debian Bug report #895772,
regarding libpmix2 contains broken symlinks
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.)


-- 
895772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpmix2
Version: 2.1.1~rc1-1
Severity: serious
Control: affects -1 src:lammps libopenmpi3
Control: block 895193 by -1

-rw-r--r-- root/root624384 2018-02-24 11:43 
./usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so.2.1.11
lrwxrwxrwx root/root 0 2018-02-24 11:43 
./usr/lib/x86_64-linux-gnu/libpmix.so.2 -> pmix/lib/libpmix.so.2.1.3
lrwxrwxrwx root/root 0 2018-02-24 11:43 
./usr/lib/x86_64-linux-gnu/libpmix.so.2.1.3 -> pmix/lib/libpmix.so.2.1.3
lrwxrwxrwx root/root 0 2018-02-24 11:43 
./usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so.2 -> libpmix.so.2.1.11


2.1.3 != 2.1.11
--- End Message ---
--- Begin Message ---
Source: pmix
Source-Version: 2.1.1~rc1-2

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated pmix 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: Mon, 16 Apr 2018 09:23:29 +0100
Source: pmix
Binary: libpmix-dev libpmi-pmix-dev libpmi1-pmix libpmi2-pmix libpmix2
Architecture: source amd64
Version: 2.1.1~rc1-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libpmi-pmix-dev - Development files for the PMI library (OpenMPI )
 libpmi1-pmix - OpenMPI implementation of the PMI v1 library
 libpmi2-pmix - OpenMPI implementation of the PMI v2 library
 libpmix-dev - Development files for the PMI Exascale library
 libpmix2   - Process Management Interface (Exascale) library
Closes: 895772
Changes:
 pmix (2.1.1~rc1-2) unstable; urgency=medium
 .
   * Standards-Version: 4.1.4
   * Fix broken symlinks. Closes: #895772
   * Drop obsolete --parallel argument to dh
Checksums-Sha1:
 78dd6ae4ca07774ab03d29a48b9aa2e163ccde7f 2252 pmix_2.1.1~rc1-2.dsc
 5f9c6875bc489291d99826e8414a3a906f52a878 6840 pmix_2.1.1~rc1-2.debian.tar.xz
 61dd3fd71a8b6e77283f1e0900eb75c7e9f0d41f 382244 
libpmi-pmix-dev_2.1.1~rc1-2_amd64.deb
 3efbe22583528ef44643cf68816a3a165159918a 904116 
libpmi1-pmix-dbgsym_2.1.1~rc1-2_amd64.deb
 af7e3e6c9b624320234eb65804a2c554d3b5f974 216376 
libpmi1-pmix_2.1.1~rc1-2_amd64.deb
 7fd6fa3d85baf7fc0c92f2614cc4972fd5388020 906548 
libpmi2-pmix-dbgsym_2.1.1~rc1-2_amd64.deb
 b0443338f967fb4dddf4f3e5f065d448739fd413 217744 
libpmi2-pmix_2.1.1~rc1-2_amd64.deb
 1046eedf2105bdc16547b776a1115b9508bc3ce4 443196 
libpmix-dev_2.1.1~rc1-2_amd64.deb
 ed87d3eb917d8f1cb835970a93896298e168d30a 1555680 
libpmix2-dbgsym_2.1.1~rc1-2_amd64.deb
 d034cf85bdbc9c9a2564e12f2fb3fb98ae43b738 339408 libpmix2_2.1.1~rc1-2_amd64.deb
 3365dd25cf6607afee6dd12532f7878da296d6e1 8045 pmix_2.1.1~rc1-2_amd64.buildinfo
Checksums-Sha256:
 210b9edee10a85c8b93c8ae61ed02b723a33d8d18d53c38153c1fbe1de713988 2252 
pmix_2.1.1~rc1-2.dsc
 0aa53f8fc0aea230f64195569b5c033c36f0a58368eebefb15cda07e153d1631 6840 
pmix_2.1.1~rc1-2.debian.tar.xz
 fda94a1c7a2d73fd05916aad1cdedea06878280d611531438e427752eafc8e12 382244 
libpmi-pmix-dev_2.1.1~rc1-2_amd64.deb
 33637466bdf463c2e6e8c3339b01d910b284a9f6432742df1ea51270e82501a6 904116 
libpmi1-pmix-dbgsym_2.1.1~rc1-2_amd64.deb
 39a87041bd74ef988d5911d287053498cd75d6ced4410b84abf80034b97c83c9 216376 
libpmi1-pmix_2.1.1~rc1-2_amd64.deb
 4dc9e4ecd6831f3c3dbc6909c667da9c4179277527d0f4d3d3d842d927a4af5e 906548 
libpmi2-pmix-dbgsym_2.1.1~rc1-2_amd64.deb
 8c6e9bb031e6d27a217600b2c13d179ea820ee8fb6b9d23d9596578c39656734 217744 
libpmi2-pmix_2.1.1~rc1-2_amd64.deb
 db30bfbb408a16da65844fb60d0e06dcdafcb815231bfdb5df3504ec5883a22a 443196 
libpmix-dev_2.1.1~rc1-2_amd64.deb
 

Bug#876921: marked as done (python-pint FTBFS with python-numpy 1.13.1: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 09:31:45 +
with message-id 
and subject line Bug#876921: fixed in python-pint 0.8.1-2
has caused the Debian Bug report #876921,
regarding python-pint FTBFS with python-numpy 1.13.1: test failures
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.)


-- 
876921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pint
Version: 0.8.1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pint.html

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose 
S.S./usr/lib/python2.7/unittest/case.py:340:
 RuntimeWarning: TestResult has no addExpectedFailure method, reporting as 
passes
  RuntimeWarning)
...S...SSSS.S...E.E...E.../build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/test_quantity.py:287:
 RuntimeWarning: to_compact applied to non numerical types has an undefined 
behavior.
  self.assertQuantityAlmostIdentical(q.to_compact(unit=unit),
...F..F..
==
ERROR: test_inplace_exponentiation 
(pint.testsuite.test_quantity.TestOffsetUnitMath) [with input = ((10, u'degC'), 
(2, u'')); expected_output = [u'error', (80173.9224999, u'kelvin**2')]]
--
Traceback (most recent call last):
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/parameterized.py",
 line 116, in new_method
return method(self, *param_values)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/parameterized.py",
 line 137, in newfunc
return func(*arg, **kwargs)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/test_quantity.py",
 line 1165, in test_inplace_exponentiation
self.assertEqual(op.ipow(in1_cp, in2).units, expected.units)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/quantity.py", 
line 961, in __ipow__
self._magnitude **= _to_magnitude(other, self.force_ndarray)
TypeError: unsupported operand type(s) for ** or pow(): 'numpy.ndarray' and 
'Quantity'

==
ERROR: test_inplace_exponentiation 
(pint.testsuite.test_quantity.TestOffsetUnitMath) [with input = ((10, 
u'kelvin'), (2, u'')); expected_output = [(100.0, u'kelvin**2'), (100.0, 
u'kelvin**2')]]
--
Traceback (most recent call last):
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/parameterized.py",
 line 116, in new_method
return method(self, *param_values)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/parameterized.py",
 line 137, in newfunc
return func(*arg, **kwargs)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/testsuite/test_quantity.py",
 line 1165, in test_inplace_exponentiation
self.assertEqual(op.ipow(in1_cp, in2).units, expected.units)
  File 
"/build/1st/python-pint-0.8.1/.pybuild/pythonX.Y_2.7/build/pint/quantity.py", 
line 961, in __ipow__
self._magnitude **= _to_magnitude(other, self.force_ndarray)
TypeError: unsupported operand type(s) for ** or pow(): 'numpy.ndarray' and 
'Quantity'

==
ERROR: test_inplace_exponentiation 
(pint.testsuite.test_quantity.TestOffsetUnitMath) [with input = ((10, u'degC'), 
(500.0, u'millikelvin/kelvin')); expected_output = [u'error', 
(16.827061537891872, u'kelvin**0.5')]]

Bug#876147: [Debian-med-packaging] Bug#876147: Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[John Paul Adrian Glaubitz]

On 04/16/2018 11:16 AM, John Paul Adrian Glaubitz wrote:

Meanwhile I commited a fix upstream
(https://github.com/fw4spl-org/camp/pull/2) so I would just want to try
it before proposing the fix in the package.

I'll test that for you on s390x.


That patch doesn't apply to the Debian version of camp:

glaubitz@zelenka:~/camp/camp-0.8.1$ patch -p1 < ~/fix-s390x.patch
patching file .gitignore
patching file include/camp/qt/qtfunction.hpp
patching file include/camp/qt/qthelper.hpp
patching file include/camp/valuemapper.hpp
Hunk #2 FAILED at 40.
Hunk #3 succeeded at 96 (offset 2 lines).
Hunk #4 succeeded at 126 (offset 2 lines).
Hunk #5 succeeded at 139 (offset 2 lines).
Hunk #6 succeeded at 156 (offset 2 lines).
Hunk #7 succeeded at 183 (offset 2 lines).
Hunk #8 succeeded at 205 (offset 2 lines).
Hunk #9 succeeded at 234 (offset 2 lines).
Hunk #10 succeeded at 250 (offset 2 lines).
Hunk #11 succeeded at 279 (offset 2 lines).
Hunk #12 succeeded at 326 (offset 2 lines).
Hunk #13 succeeded at 345 (offset 2 lines).
1 out of 13 hunks FAILED -- saving rejects to file 
include/camp/valuemapper.hpp.rej
patching file test/arrayproperty.hpp
Hunk #2 FAILED at 32.
Hunk #3 succeeded at 78 (offset 2 lines).
1 out of 3 hunks FAILED -- saving rejects to file test/arrayproperty.hpp.rej
patching file test/qt/propertymapping.cpp
Hunk #2 succeeded at 34 with fuzz 2 (offset 2 lines).
Hunk #3 succeeded at 47 (offset 2 lines).
Hunk #4 succeeded at 95 (offset 2 lines).
Hunk #5 succeeded at 106 (offset 2 lines).
glaubitz@zelenka:~/camp/camp-0.8.1$

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#876147: [Debian-med-packaging] Bug#876147: Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[John Paul Adrian Glaubitz]

Hello!

On 04/16/2018 09:15 AM, Flavien Bridault wrote:

I sent you a private email twice last week but I did not receive any
answer from you so I am afraid they did not reach you. Or maybe you were
just away or not available, if that's the case sorry for spaming you...


I forgot to follow up on that, sorry. I have been very busy. But from
the logs it's also apparent that the package builds fine - including the
tests - on sparc64, so I'm not sure the sparc64 porterbox would be of
any help.

You should preferably get access to an s390x porterbox but I don't have
any that I can provide access to. You would have to contact the correct
people at Debian for that.

See: https://dsa.debian.org/doc/guest-account/


Meanwhile I commited a fix upstream
(https://github.com/fw4spl-org/camp/pull/2) so I would just want to try
it before proposing the fix in the package.

I'll test that for you on s390x.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#895809: enlightenment: Fails to start

[Manolo Díaz]

Package: enlightenment
Version: 0.22.1-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Enlightenment fails to start. These are the last lines shown:

ESTART: 0.17880 [0.00119] - Compositor Init
 Enlightenment Error 
Enlightenment cannot initialize Ecore_X!

 Enlightenment Error 
Enlightenment cannot create a compositor.

E: Begin Shutdown Procedure!
ERR<3106>:e ../src/bin/e_msgbus.c:84 _e_msgbus_request_name_cb() Could not 
request bus name
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/lib/x86_64-linux-gnu/libeina.so.1   0x7f87962e56cc 0x7f87962be000
/lib/x86_64-linux-gnu/libeina.so.1   0x7f87962e63f1 0x7f87962be000
/lib/x86_64-linux-gnu/libeina.so.1   0x7f87962e77c3 0x7f87962be000
/usr/bin/enlightenment   0x55de52ef2c45 0x55de52df
/lib/x86_64-linux-gnu/libeldbus.so.1 0x7f8794267f8e 0x7f8794253000
/lib/x86_64-linux-gnu/libeldbus.so.1 0x7f879425cde1 0x7f8794253000
/lib/x86_64-linux-gnu/libeldbus.so.1 0x7f879425d1cb 0x7f8794253000
/lib/x86_64-linux-gnu/libeldbus.so.1 0x7f879426104d 0x7f8794253000
/lib/x86_64-linux-gnu/libeldbus.so.1 0x7f8794265fd2 0x7f8794253000
/lib/x86_64-linux-gnu/libeldbus.so.1 0x7f879426663f 0x7f8794253000
/lib/x86_64-linux-gnu/libeldbus.so.1 0x7f879426104d 0x7f8794253000
/lib/x86_64-linux-gnu/libeldbus.so.1 0x7f8794261a5f 0x7f8794253000
/usr/bin/enlightenment   0x55de52ef2f37 0x55de52df
/usr/bin/enlightenment   0x55de52ee7c08 0x55de52df
/usr/bin/enlightenment   0x55de52e322a9 0x55de52df
/lib/x86_64-linux-gnu/libc.so.6  0x7f8792d92a87 0x7f8792d71000
/usr/bin/enlightenment   0x55de52e32e4a 0x55de52df
EOF


And eina_btlog shows:

/lib/x86_64-linux-gnu/libeina.so.1  |   
 ??/??  :   0 @ eina_log_print_cb_journald()
/lib/x86_64-linux-gnu/libeina.so.1  |   
 ??/??  :   0 @ eina_log_print_cb_stdout()
/lib/x86_64-linux-gnu/libeina.so.1  |   
 ??/??  :   0 @ eina_log_print()
 /usr/bin/enlightenment |   
 ??/??  :   0 @ e_moveresize_client_extents()
/lib/x86_64-linux-gnu/libeldbus.so.1|   
 ??/??  :   0 @ eldbus_object_introspect()
/lib/x86_64-linux-gnu/libeldbus.so.1|   
   /:   0 @ ()
/lib/x86_64-linux-gnu/libeldbus.so.1|   
   /:   0 @ ()
/lib/x86_64-linux-gnu/libeldbus.so.1|   
 ??/??  :   0 @ eldbus_shutdown()
/lib/x86_64-linux-gnu/libeldbus.so.1|   
 ??/??  :   0 @ eldbus_message_signal_new()
/lib/x86_64-linux-gnu/libeldbus.so.1|   
 ??/??  :   0 @ eldbus_message_signal_new()
/lib/x86_64-linux-gnu/libeldbus.so.1|   
 ??/??  :   0 @ eldbus_shutdown()
/lib/x86_64-linux-gnu/libeldbus.so.1|   
 ??/??  :   0 @ eldbus_connection_unref()
 /usr/bin/enlightenment |   
 ??/??  :   0 @ e_moveresize_client_extents()
 /usr/bin/enlightenment |   
 ??/??  :   0 @ e_livethumb_thumb_get()
 /usr/bin/enlightenment |   
 ??/??  :   0 @ main()
/lib/x86_64-linux-gnu/libc.so.6 | 
/build/glibc-kAz5Pl/glibc-2.27/csu/../csu/libc-start.c: 344 @ 
__libc_start_main()
 /usr/bin/enlightenment |   
 ??/??  : 344 @ _start()

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

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

Versions of packages enlightenment depends on:
ii  dbus-x11 [dbus-session-bus]  1.12.6-2
ii  enlightenment-data   0.22.1-3
ii  libasound2   1.1.3-5
ii  libbluetooth35.49-1
ii  libc62.27-3
ii  libecore-con11.20.7-4
ii  libecore-evas1   1.20.7-4
ii  libecore-file1   1.20.7-4
ii  libecore-input1  1.20.7-4
ii  libecore-ipc11.20.7-4
ii  libecore-x1  1.20.7-4
ii  libecore11.20.7-4
ii  libedje-bin  1.20.7-4
ii  libedje1 1.20.7-4
ii  libeet1  1.20.7-4
ii  libeeze1 1.20.7-4
ii  libefreet-bin1.20.7-4
ii  libefreet1a   

Bug#892988: autokey-gtk: does not start

[Adrian Bunk]

On Mon, Apr 16, 2018 at 10:49:32AM +0200, Francesco Marchesi wrote:
> > Please provide the output of the following commands:
> 
> Here you are
>...
> > $ find /usr/local -name six.py
> 
> /usr/local/lib/python2.7/dist-packages/six.py
>...

This is what is causng your problem, you have a manually installed copy 
of this module there.

Please confirm that it works after removing this file.

> Thanks,
> Francesco

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#894083: italc: diff for NMU version 1:3.0.3+dfsg1-2.1

[Mike Gabriel]

Hi Adrian,

On  So 15 Apr 2018 21:05:30 CEST, Adrian Bunk wrote:


On Sun, Apr 15, 2018 at 05:51:21PM +, Mike Gabriel wrote:

Hi Adrian,


Hi Mike,


Please cancel the NMU, I'll provide a fix. Thanks for the debdiff.
...


fine for me, cancelled.


Mike


cu
Adrian


1:3.0.3+dfsg1-3 has just been uploaded.

Thanks,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp98nVhqElQ9.pgp
Description: Digitale PGP-Signatur

Bug#892988: autokey-gtk: does not start

[Francesco Marchesi]

> Please provide the output of the following commands:

Here you are

> $ dpkg -l python-xlib

ii python-xlib 0.20-3 all interface for Python to the X11 protocol

> $ dpkg -l python-six

ii python-six 1.11.0-2 all Python 2 and 3 compatibility library (Python
2 interface)

> $ find /usr/local -name six.py

/usr/local/lib/python2.7/dist-packages/six.py
/usr/local/lib/python2.7/dist-packages/ecdsa/six.py

Thanks,
Francesco

Bug#894083: marked as pending

[Mike Gabriel]

tag 894083 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/debian-edu/pkg-team/italc.git/commit/?id=467b0d2

---
commit 467b0d25f619aff962e7c7b661202dc09059f9b8
Author: Mike Gabriel 
Date:   Mon Apr 16 10:48:09 2018 +0200

upload to unstable (debian/1:3.0.3+dfsg1-3)

diff --git a/debian/changelog b/debian/changelog
index 9a26b58..ce3832e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+italc (1:3.0.3+dfsg1-3) unstable; urgency=medium
+
+  [ Mike Gabriel ]
+  * debian/control:
++ Drop Patrick Winnertz from the list of uploaders. Thanks for previous
+  contributions. (Closes: #867760).
+
+  [ Pino Toscano ]
+  * debian/control:
++ Recommend kdialog rather than kde-baseapps-bin. (Closes: #885840).
+
+  [ Adrian Bunk ]
+  * debian/control:
++ Build with default-jdk instead of gcj-jdk. (Closes: #894083).
+
+ -- Mike Gabriel   Mon, 16 Apr 2018 10:39:33 +0200
+
 italc (1:3.0.3+dfsg1-2) unstable; urgency=medium
 
   * debian/control:

Processed: Bug#894083 marked as pending

[Debian Bug Tracking System]

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

> tag 894083 pending
Bug #894083 [src:italc] italc build-depends on gcj-jdk, which will be removed
Ignoring request to alter tags of bug #894083 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#895695: elki FTBFS: java.base/jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to java.base/java.net.URLClassLoader

[Erich Schubert]

Caused by Java 1.9, can probably be cherry-picked:

Fixed upstream, but no new release yet.

https://github.com/elki-project/elki/commit/92c96858616581c2109d36488e96c84c72d8bbc7




Am 14.04.2018 um 21:37 schrieb Adrian Bunk:

Source: elki
Version: 0.7.1-6
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/elki.html

...
[INFO] --- exec-maven-plugin:1.6.0:exec (generate-javadoc-parameters) @ elki ---
Exception in thread "main" java.lang.ExceptionInInitializerError
at 
de.lmu.ifi.dbs.elki.application.internal.DocumentParameters.buildParameterIndex(DocumentParameters.java:251)
at 
de.lmu.ifi.dbs.elki.application.internal.DocumentParameters.main(DocumentParameters.java:149)
Caused by: java.lang.ClassCastException: 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to 
java.base/java.net.URLClassLoader
at 
de.lmu.ifi.dbs.elki.utilities.ELKIServiceRegistry.(ELKIServiceRegistry.java:53)
... 2 more
[ERROR] Command execution failed.

Bug#895765: igv: FTBFS with java 9

[Olivier Sallou]

On 04/16/2018 09:32 AM, Bas Couwenberg wrote:
> On 2018-04-16 08:18, Andreas Tille wrote:
>> it seems something has changed with openfx since the errors below are
>> all mentioning something like "import javafx. ...".  Do you have any
>> hint how this can be fixed?
>
> There is no OpenJFX for OpenJDK 9, see:
>
>  https://lists.debian.org/debian-java/2018/04/msg3.html

indeed Java 9 removed some packages from *core* java and were moved to
additional modules to add at compilation/runtime.
Problem is this is not transparent/compatible with java <= 8.
So, to support java 9 AND below, you need specific scripts that detect
java version and act accordingly. This is not really cool to do and
maintain.

As proposed, either javafx can be removed from code, either we shoud
stick to Java 9 and superior and add the javafx module.
there is an example in biojava4 for a build.xml:


       
          
          
  .

this example used java.se.ee module.

For javafx, there are several modules [0]:

* Base APIs for JavaFX UI Toolkit — javafx.base
* JavaFX APIs for UI Controls — javafx.controls
* JavaFX APIs for FXML — javafx.fxml
* JavaFX APIs for various Graphics Tools— javafx.graphics
* JavaFX APIs for Multimedia — javafx.media
* JavaFX APIs for Swing-JavaFX Interoperability — javafx.swing
* JavaFX APIs for WebView Functionality — javafx.web


To add multiple modules, one need to separate them with comma.

[0]
https://medium.com/@afinlay/whats-new-in-java-fx-java-9-updates-a90dd3d4dbba



>
> If the package works without JavaFX you should consider disabling that
> for the time being.
>
> You can also explicitly build with OpenJDK 8, but that will just get
> you a different RC bug because openjdk-8 will not be in buster.
>
> Kind Regards,
>
> Bas
>

-- 
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#884030: marked as done (Depends on obsolete libgoo-canvas-perl)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 10:07:19 +0200
with message-id 
and subject line gscan2pdf depends on obsolete libgoo-canvas-perl
has caused the Debian Bug report #884030,
regarding Depends on obsolete libgoo-canvas-perl
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.)


-- 
884030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gscan2pdf
Version: 1.8.10-1
Severity: serious

Hi,

We are trying to remove the old goocanvas library out of buster.

Please keep gscan2pdf out of testing.

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
gscan2pdf v2.0.0 no longer depends on libgoo-canvas-perl




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

Bug#872413: kpatch: Please package new upstream version

[Vincent Bernat]

 ❦ 15 avril 2018 09:58 +0200, Simon Ruderich  :

>> As the package is not currently usable with our kernel, or even the
>> one in stable, I am bumping the severity. Since you already worked a
>> lot on this, would you be interested to prepare an upload for 0.5.0? If
>> yes, we could sort out how to organize that.

> Thanks for your initiative. Patch to update to 0.5.0 (as diff
> from the current version in Debian Sid) is attached. It's based
> on the upstream kpatch tarball from github with the following
> sha512 checksum:
>
> 
> d7e45a4395a8c7632187ca5c8b837bad0d7583f66ce5f5d2b8f1acabf9ff2539d038a16986f9846818183f5c3268a613580a98ad72f3766e286e6273d57ddc78
> kpatch_0.5.0.orig.tar.gz

Simon, your patch looks OK to me. I'll change the changelog entry to
say:

 * Non-maintainer upload.
 * New upstream release. Closes: #872413.

Chris, do you object to an upload to update kpatch?
-- 
Must I hold a candle to my shames?
-- William Shakespeare, "The Merchant of Venice"


signature.asc
Description: PGP signature

Bug#876921: Bug #876921 in python-pint marked as pending

[onovy]

Control: tag -1 pending

Hello,

Bug #876921 in python-pint reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/python-pint/commit/e9a5289683522045c2fb4055b0ab1ad67b0a1ab7


Fix for numpy 1.14 (Closes: #876921)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/876921

Processed: Bug #876921 in python-pint marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #876921 [src:python-pint] python-pint FTBFS with python-numpy 1.13.1: test 
failures
Added tag(s) pending.

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

Bug#895792: gplaycli: dependency androguard switched to Python 3, gplaycli is incompatible with Python 3

[Matlink]

Gplaycli is using python3 upstream (since a while ago), and is no more
python2-compatible.

I guess we need to repack it as soon as possible.


Le 16/04/2018 à 05:57, Paul Wise a écrit :
> Package: gplaycli
> Version: 0.2.10-1
> Severity: serious
> File: /usr/bin/gplaycli
>
> The gplaycli dependency androguard switched to Python 3,
> but gplaycli uses Python 2 and is incompatible with Python 3:
>
> $ gplaycli 
> Traceback (most recent call last):
>   File "/usr/bin/gplaycli", line 28, in 
> from androguard.core.bytecodes import apk as androguard_apk  # Androguard
> ImportError: No module named androguard.core.bytecodes
> $ python -c 'from androguard.core.bytecodes import apk'
> Traceback (most recent call last):
>   File "", line 1, in 
> ImportError: No module named androguard.core.bytecodes
> $ python3 -c 'from androguard.core.bytecodes import apk'
> $ python3 /usr/bin/gplaycli 
>   File "/usr/bin/gplaycli", line 143
> print 'Token dispenser auth error, probably too many connections'
> ^
> SyntaxError: Missing parentheses in call to 'print'. Did you mean 
> print('Token dispenser auth error, probably too many connections')?
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing-debug
>   APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
> 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
> 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), 
> LANGUAGE=en_AU.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages gplaycli depends on:
> ii  androguard  3.1.0~rc2-1
> ii  python  2.7.14-4
> ii  python-clint0.5.1-1
> ii  python-ndg-httpsclient  0.4.4-1
> ii  python-protobuf 3.0.0-9.1
> ii  python-pyasn1   0.4.2-3
> ii  python-requests 2.18.4-2
>
> Versions of packages gplaycli recommends:
> pn  dummydroid
> pn  fdroidserver  
>
> gplaycli suggests no packages.
>
> -- no debconf information
>
>

-- 
Matlink - Sysadmin matlink.fr
Sortez couverts, chiffrez vos mails : https://café-vie-privée.fr/
XMPP/Jabber : matl...@matlink.fr
Clé publique PGP : 0x186BB3CA
Empreinte Off-the-record : 572174BF 6983EA74 91417CA7 705ED899 DE9D05B2

Processed: tagging 895371

[Debian Bug Tracking System]

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

> tags 895371 + confirmed
Bug #895371 [ejabberd] ejabberd: conffile edited using ucf
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#895765: igv: FTBFS with java 9

[Bas Couwenberg]

On 2018-04-16 08:18, Andreas Tille wrote:

it seems something has changed with openfx since the errors below are
all mentioning something like "import javafx. ...".  Do you have any
hint how this can be fixed?


There is no OpenJFX for OpenJDK 9, see:

 https://lists.debian.org/debian-java/2018/04/msg3.html

If the package works without JavaFX you should consider disabling that 
for the time being.


You can also explicitly build with OpenJDK 8, but that will just get you 
a different RC bug because openjdk-8 will not be in buster.


Kind Regards,

Bas

Bug#895371: ejabberd: conffile edited using ucf

[Philipp Huebner]

Hi Jonas,

On Tue, 10 Apr 2018 19:39:14 +0200 Jonas Smedegaard  wrote:
> The file /etc/default/ejabberd is registered as a conffile, but is also
> manipulated using ucf in postinst script.  That is illegal, according to
> Policy § 10.7.3

thanks for pointing this out!

However, this is rather unfortunate, the current setup has been well
tested and in use for ages.

Do you have an idea on how to achieve this in a policy-conform way?

Not touching ejabberd.yml would mean to remove the debconf templates for
configuring ejabberd, not declaring ejabberd.yml a conffile would mean
putting in some extra effort for handling changes.
Are non-conffiles even allowed in /etc ?


Best wishes,
-- 
 .''`.   Philipp Huebner 
: :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
`. `'`
  `-



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#895767: python3-sphinx: missing dependency on python3-setuptools

[Debian Bug Tracking System]

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

> fixed 895767 sphinx/1.7.2-3
Bug #895767 [python3-sphinx] python3-sphinx: missing dependency on 
python3-setuptools
Marked as fixed in versions sphinx/1.7.2-3.
> close 895767
Bug #895767 [python3-sphinx] python3-sphinx: missing dependency on 
python3-setuptools
Marked Bug as done
> severity 895738 serious
Bug #895738 {Done: Dmitry Shachnev } [python3-sphinx] 
python3-sphinx: missing dependency on python3-setuptools
Severity set to 'serious' from 'important'
> merge 895738 895767
Bug #895738 {Done: Dmitry Shachnev } [python3-sphinx] 
python3-sphinx: missing dependency on python3-setuptools
Bug #895767 {Done: Dmitry Shachnev } [python3-sphinx] 
python3-sphinx: missing dependency on python3-setuptools
Merged 895738 895767
> thanks
Stopping processing here.

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

Bug#876147: [Debian-med-packaging] Bug#876147: Bug#876147: camp frequently FTBFS on 64bit big endian: camptest-qt (Failed)

[Flavien Bridault]

Hi Adrian,

I sent you a private email twice last week but I did not receive any
answer from you so I am afraid they did not reach you. Or maybe you were
just away or not available, if that's the case sorry for spaming you...

Meanwhile I commited a fix upstream
(https://github.com/fw4spl-org/camp/pull/2) so I would just want to try
it before proposing the fix in the package.

Cheers


Le 06/04/2018 à 14:36, John Paul Adrian Glaubitz a écrit :
> On 04/06/2018 02:34 PM, Flavien Bridault wrote:
>> Okay thanks a lot for your quick answer !
>>
>> Maybe I misunderstood the excuses
>> https://qa.debian.org/excuses.php?package=camp, but the build failure on
>> s390x looks very similar at the endianess issue we have on sparc64, so
>> this should also solves that. If not I will contact s390x folks.
> We can give a try non-theless.
>
> Please send me a private email with your desired username. Encrypt the
> mail using my GPG below (you can find in the Debian GPG keyring).
>
> Use your key that was signed by the Debian Developer you mentioned.
>
> Adrian
>

-- 
*Flavien BRIDAULT*
Ingénieur de Recherche

fbrida...@ircad.fr

*IRCAD France*
1, place de l'Hôpital - 67091 Strasbourg Cedex - FRANCE

http://www.ircad.fr/ 




signature.asc
Description: OpenPGP digital signature

Processed: affects 895772

[Debian Bug Tracking System]

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

> affects 895772 src:liggghts
Bug #895772 [libpmix2] libpmix2 contains broken symlinks
Added indication that 895772 affects src:liggghts
> thanks
Stopping processing here.

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

Bug#895208: gnumeric: missing build dependency on libxml2-utils

[Andreas Tille]

Hi Dmitry,

I'd volunteer to NMU this package but it seems it also needs migration
to Salsa.  Since I usually like to push my changes to Git I'd like to
ask for permission to do the Salsa migration for gnumeric.  I'll assume
that you agree to this if I do not hear from you soon.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#895782: marked as done (virtualbox-dkms: Cannot compile kernel modules against kernel 4.15)

[Debian Bug Tracking System]

Your message dated Mon, 16 Apr 2018 06:25:27 + (UTC)
with message-id <632075474.814420.1523859927...@mail.yahoo.com>
and subject line Re: Bug#895782: virtualbox-dkms: Cannot compile kernel modules 
against kernel 4.15
has caused the Debian Bug report #895782,
regarding virtualbox-dkms: Cannot compile kernel modules against kernel 4.15
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.)


-- 
895782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-dkms
Version: 5.1.30-dfsg-1~bpo9+1
Severity: grave
Justification: renders package unusable

The VB 5.1.30 module vboxdrv cannot compile with the strertch-backport kernel 
4.15.0-0.bpo.2-amd64. The compile finises with error:

/var/lib/dkms/virtualbox/5.1.30/build/vboxdrv/r0drv/linux/timer-r0drv-linux.c:
In function ‘VBoxHost_RTTimerCreateEx’:
/var/lib/dkms/virtualbox/5.1.30/build/vboxdrv/r0drv/linux/timer-r0drv-linux.c:1588:13:
error: implicit declaration of function 
‘init_timer_pinned’[-Werror=implicit-function-declaration]  
init_timer_pinned(>aSubTimers[iCpu].u.Std.LnxTimer);

VB's developers released patch for running on kernel 4.15:
https://www.virtualbox.org/pipermail/vbox-dev/2017-December/014885.html

Could you please include it to the package?



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

Kernel: Linux 4.15.0-0.bpo.2-amd64 (SMP w/6 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.3-2

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  5.1.30-dfsg-1~bpo9+1

virtualbox-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,


I might backport it in 5 days.

G.--- End Message ---

Bug#895765: igv: FTBFS with java 9

[Andreas Tille]

Hi,

it seems something has changed with openfx since the errors below are
all mentioning something like "import javafx. ...".  Do you have any
hint how this can be fixed?

Kind regards

Andreas.

On Sun, Apr 15, 2018 at 08:55:57PM +0200, Andreas Beckmann wrote:
> Source: igv
> Version: 2.4.6+dfsg-1
> Severity: serious
> Justification: fails to build from source
> 
> ...
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:7: 
> error: package javafx.application does not exist
> [javac] import javafx.application.Platform;
> [javac]  ^
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:8: 
> error: package javafx.embed.swing does not exist
> [javac] import javafx.embed.swing.JFXPanel;
> [javac]  ^
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:9: 
> error: package javafx.geometry does not exist
> [javac] import javafx.geometry.Pos;
> [javac]   ^
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:10: 
> error: package javafx.scene does not exist
> [javac] import javafx.scene.Node;
> [javac]^
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:11: 
> error: package javafx.scene does not exist
> [javac] import javafx.scene.Scene;
> [javac]^
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:13: 
> error: package javafx.scene.layout does not exist
> [javac] import javafx.scene.layout.GridPane;
> [javac]   ^
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:14: 
> error: package javafx.scene.layout does not exist
> [javac] import javafx.scene.layout.StackPane;
> [javac]   ^
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:15: 
> error: package javafx.scene.layout does not exist
> [javac] import javafx.scene.layout.VBox;
> [javac]   ^
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:16: 
> error: package javafx.scene.paint does not exist
> [javac] import javafx.scene.paint.Color;
> [javac]  ^
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:17: 
> error: package javafx.scene.text does not exist
> [javac] import javafx.scene.text.Text;
> [javac] ^
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:45: 
> error: cannot find symbol
> [javac] static Color lightGray = new Color(0.9, 0.9, 0.9, 0.5);
> [javac]^
> [javac]   symbol:   class Color
> [javac]   location: class Cravat
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:77: 
> error: cannot find symbol
> [javac] private static void initFX(JFXPanel fxPanel, JsonObject 
> jsonObject) {
> [javac]^
> [javac]   symbol:   class JFXPanel
> [javac]   location: class Cravat
> [javac] /build/igv-2.4.6+dfsg/src/org/broad/igv/mupit/Cravat.java:12: 
> error: package javafx.scene.control does not exist
> [javac] import javafx.scene.control.*;
> [javac] ^
> [javac] 
> /build/igv-2.4.6+dfsg/src/org/broad/igv/prefs/PreferenceEditorFX.java:3: 
> error: package javafx.application does not exist
> [javac] import javafx.application.Platform;
> [javac]  ^
> [javac] 
> /build/igv-2.4.6+dfsg/src/org/broad/igv/prefs/PreferenceEditorFX.java:4: 
> error: package javafx.beans.value does not exist
> [javac] import javafx.beans.value.ChangeListener;
> [javac]  ^
> [javac] 
> /build/igv-2.4.6+dfsg/src/org/broad/igv/prefs/PreferenceEditorFX.java:5: 
> error: package javafx.beans.value does not exist
> [javac] import javafx.beans.value.ObservableValue;
> [javac]  ^
> [javac] 
> /build/igv-2.4.6+dfsg/src/org/broad/igv/prefs/PreferenceEditorFX.java:6: 
> error: package javafx.collections does not exist
> [javac] import javafx.collections.FXCollections;
> [javac]  ^
> [javac] 
> /build/igv-2.4.6+dfsg/src/org/broad/igv/prefs/PreferenceEditorFX.java:7: 
> error: package javafx.embed.swing does not exist
> [javac] import javafx.embed.swing.JFXPanel;
> [javac]  ^
> [javac] 
> /build/igv-2.4.6+dfsg/src/org/broad/igv/prefs/PreferenceEditorFX.java:8: 
> error: package javafx.geometry does not exist
> [javac] import javafx.geometry.HPos;
> [javac]   ^
> [javac] 
> /build/igv-2.4.6+dfsg/src/org/broad/igv/prefs/PreferenceEditorFX.java:9: 
> error: package javafx.geometry does not exist
> [javac] import javafx.geometry.Insets;
> [javac]   ^
> [javac] 
> 

Bug#895797: lucene-solr FTBFS: LuceneJUnitDividingSelector is not abstract and does not override abstract method isSelected(Resource) in ResourceSelector

[Adrian Bunk]

Source: lucene-solr
Version: 3.6.2+dfsg-11
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lucene-solr.html

...
compile-core:
[mkdir] Created dir: 
/build/1st/lucene-solr-3.6.2+dfsg/lucene/build/test-framework/classes/java
[javac] Compiling 51 source files to 
/build/1st/lucene-solr-3.6.2+dfsg/lucene/build/test-framework/classes/java
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.7
[javac] 
/build/1st/lucene-solr-3.6.2+dfsg/lucene/test-framework/src/java/org/apache/lucene/util/LuceneTestCase.java:895:
 warning: [unchecked] Possible heap pollution from parameterized vararg type T
[javac]   public static  Set asSet(T... args) {
[javac]   ^
[javac]   where T is a type-variable:
[javac] T extends Object declared in method asSet(T...)
[javac] 
/build/1st/lucene-solr-3.6.2+dfsg/lucene/test-framework/src/java/org/apache/lucene/queryParser/QueryParserTestBase.java:1135:
 warning: [rawtypes] found raw type: Class
[javac]   QueryParser.class.getConstructor(new Class[] 
{CharStream.class});
[javac]^
[javac]   missing type arguments for generic class Class
[javac]   where T is a type-variable:
[javac] T extends Object declared in class Class
[javac] 
/build/1st/lucene-solr-3.6.2+dfsg/lucene/test-framework/src/java/org/apache/lucene/queryParser/QueryParserTestBase.java:1141:
 warning: [rawtypes] found raw type: Class
[javac]   QueryParser.class.getConstructor(new Class[] 
{QueryParserTokenManager.class});
[javac]^
[javac]   missing type arguments for generic class Class
[javac]   where T is a type-variable:
[javac] T extends Object declared in class Class
[javac] 
/build/1st/lucene-solr-3.6.2+dfsg/lucene/test-framework/src/java/org/apache/lucene/util/LuceneJUnitDividingSelector.java:26:
 error: LuceneJUnitDividingSelector is not abstract and does not override 
abstract method isSelected(Resource) in ResourceSelector
[javac] public class LuceneJUnitDividingSelector extends BaseExtendSelector 
{
[javac]^
[javac] 
/build/1st/lucene-solr-3.6.2+dfsg/lucene/test-framework/src/java/org/apache/lucene/util/LuceneJUnitDividingSelector.java:34:
 warning: setParameters(Parameter[]) in LuceneJUnitDividingSelector implements 
setParameters(Parameter...) in Parameterizable; overriding method is missing 
'...'
[javac]   public void setParameters(Parameter[] pParameters) {
[javac]   ^
[javac] 
/build/1st/lucene-solr-3.6.2+dfsg/lucene/test-framework/src/java/org/apache/lucene/util/LuceneJUnitDividingSelector.java:34:
 warning: setParameters(Parameter[]) in LuceneJUnitDividingSelector overrides 
setParameters(Parameter...) in BaseExtendSelector; overriding method is missing 
'...'
[javac]   public void setParameters(Parameter[] pParameters) {
[javac]   ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 1 error
[javac] 6 warnings

BUILD FAILED
/build/1st/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:533: The following 
error occurred while executing this line:
/build/1st/lucene-solr-3.6.2+dfsg/lucene/test-framework/build.xml:40: The 
following error occurred while executing this line:
/build/1st/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:949: Compile failed; 
see the compiler error output for details.

Total time: 5 minutes 14 seconds
make[1]: *** [debian/rules:22: override_dh_auto_build] Error 1

Processed: tagging 895795

[Debian Bug Tracking System]

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

> tags 895795 + buster sid
Bug #895795 [src:openhft-chronicle-bytes] openhft-chronicle-bytes FTBFS with 
openjdk-9
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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