Processed: Re: Bug#897947: mikutter: Twitter Consumer Key/Secret (CK/CS) suspended

[Debian Bug Tracking System]

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

> severity 897947 important
Bug #897947 [mikutter] mikutter: Twitter Consumer Key/Secret (CK/CS) suspended
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#897947: mikutter: Twitter Consumer Key/Secret (CK/CS) suspended

[dai]

Package: mikutter
Version: 3.6.7+dfsg-1
Severity: grave

mikutter's Twitter Consumer Key/Secret (CK/CS) has been suspended since
2018/5/4 morning (JST). So mikutter cannot be authenticated by Twitter
and mikutter users cannot use Twitter by mikutter.

mikutter users can replace them with their own CK/CS by modifying code
( http://mikutter.hatenablog.com/entry/2017/11/19/202832 ),
but it is AT YOUR OWN RISK, I do not know what Twitter will do.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Processed: re: ifrit FTBFS with cmake 3.11.1

[Debian Bug Tracking System]

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

> Tags 897114 +patch
Bug #897114 [src:ifrit] ifrit FTBFS with cmake 3.11.1
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#897114: ifrit FTBFS with cmake 3.11.1

[peter green]

Tags 897114 +patch
thanks

This was blocking a transition in raspbian, so I whipped up a fix. Debdiff at 
http://debdiffs.raspbian.org/main/i/ifrit/ifrit_4.1.2-5%2brpi1.debdiff , no 
intent to NMU in Debian.

The only tricky bit was that there seems to have been a typo in debian/rules, 
there was a target called override_dh_autoconfigure which I presume was a typo 
for override_dh_autoconfigure , I tried fixing said typo but that seemed to 
cause more problems than it solved, so I left it alone and added my own 
override target. You might want to consider either fixing or removing the dead 
code.

Processed: reassign 895292 to systemd-shim, forcibly merging 895418 895292, severity of 895418 is serious

[Debian Bug Tracking System]

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

> reassign 895292 systemd-shim
Bug #895292 [systemd] Restart, Suspend, Hibernate, Shut Down all greyed out in 
lightdm
Bug reassigned from package 'systemd' to 'systemd-shim'.
No longer marked as found in versions systemd/238-4.
Ignoring request to alter fixed versions of bug #895292 to the same values 
previously set
> forcemerge 895418 895292
Bug #895418 [systemd-shim] systemd-shim: incompatibility with a new version of 
systemd
Bug #895418 [systemd-shim] systemd-shim: incompatibility with a new version of 
systemd
Added tag(s) moreinfo and unreproducible.
Bug #895292 [systemd-shim] Restart, Suspend, Hibernate, Shut Down all greyed 
out in lightdm
Severity set to 'important' from 'normal'
Marked as found in versions systemd-shim/10-3.
Merged 895292 895418
> severity 895418 serious
Bug #895418 [systemd-shim] systemd-shim: incompatibility with a new version of 
systemd
Bug #895292 [systemd-shim] Restart, Suspend, Hibernate, Shut Down all greyed 
out in lightdm
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#897945: visualvm will not start since upgrade of libnb-*-java to 8.1+dfsg1-8

[Ben Caradoc-Davies]

Package: visualvm
Version: 1.3.9-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

visualvm will not start since upgrade of libnb-*-java to 8.1+dfsg1-8. It just
pauses at the splash screen for a while and then exits with code 2. strace
suggests it tries some sort of upgrade.

Workaround is to downgrade these dependencies to 8.1+dfsg1-7. These have
expired from the pool but can be found on snapshot.debian.org.

libnb-*-java dependencies:

libnb-org-openide-util-lookup-java
libnb-org-openide-util-java
libnb-org-openide-modules-java
libnb-platform18-java

Tested with OpenJDK 8, OpenJDK 9, and OpenJDK 10.

Kind regards,
Ben.



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

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

Versions of packages visualvm depends on:
pn  libnb-platform18-java   
ii  libvisualvm-jni 1.3.9-1
ii  openjdk-10-jdk [java7-sdk]  10.0.1+10-3
ii  openjdk-8-jdk [java7-sdk]   8u171-b11-1
ii  openjdk-9-jdk [java7-sdk]   9.0.4+12-4

visualvm recommends no packages.

visualvm suggests no packages.

-- no debconf information

Bug#895863: marked as done (python-acme: Unroutable maintainer address)

[Debian Bug Tracking System]

Your message dated Sat, 05 May 2018 00:49:32 +
with message-id 
and subject line Bug#895863: fixed in python-acme 0.24.0-2
has caused the Debian Bug report #895863,
regarding python-acme: Unroutable maintainer address
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.)


-- 
895863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: python-acme
Source-Version: 0.24.0-2

We believe that the bug you reported is fixed in the latest version of
python-acme, 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.
Harlan Lieberman-Berg  (supplier of updated python-acme 
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: Fri, 04 May 2018 20:33:30 -0400
Source: python-acme
Binary: python-acme python3-acme python-acme-doc
Architecture: source
Version: 0.24.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Let's Encrypt 
Changed-By: Harlan Lieberman-Berg 
Description:
 python-acme - ACME protocol library for Python 2
 python-acme-doc - ACME protocol library for Python 2 - Documentation
 python3-acme - ACME protocol library for Python 3
Closes: 895863
Changes:
 python-acme (0.24.0-2) unstable; urgency=medium
 .
   * Update team email address. (Closes: #895863)
Checksums-Sha1:
 3a2502935795930c44d860bfcc0f35baa467267e 3142 python-acme_0.24.0-2.dsc
 0d5016cdaa2a74647a39e583172195623b1a0396 5704 
python-acme_0.24.0-2.debian.tar.xz
 d2be16368de2d87e6733388d9d6f079df04ec026 9043 
python-acme_0.24.0-2_amd64.buildinfo
Checksums-Sha256:
 b383e26b33e2665810149bf54d17359c8099ac61f4166704e0ba9fbb76c0fda3 3142 
python-acme_0.24.0-2.dsc
 094b21f99a793c111bbe31c693886f2434c9e2649520b61098d9ece4f968d259 5704 
python-acme_0.24.0-2.debian.tar.xz
 a5710508e79f12197914a2a3adf8d573e852456c252832e76ecd571adab7b11b 9043 
python-acme_0.24.0-2_amd64.buildinfo
Files:
 307a3351984fb1483335ddbb3a95ad8b 3142 python optional python-acme_0.24.0-2.dsc
 a93af0fb86381efda011be4fbd3175d8 5704 python optional 
python-acme_0.24.0-2.debian.tar.xz
 d1be3ab6cf3283a62f6a58c071e58a72 9043 python optional 
python-acme_0.24.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKqBAEBCgCUFiEEAUCsXNRiG9DwejN3fudPmcDF31sFAlrs/StfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDAx
NDBBQzVDRDQ2MjFCRDBGMDdBMzM3NzdFRTc0Rjk5QzBDNURGNUIWHGhsaWViZXJt
YW5AZGViaWFuLm9yZwAKCRB+50+ZwMXfW9VfD/4uv/vao+ipCW1AYdfHVhUnv1mx
j27rAsMo3wgrPKrFpepjiztzG1fQAvSrf1A1c2oznG4txOco4b0bG41+ORLJWDoy
4KNXExogjvd7PQV/Y7e/x9CwsQVn0w6EGeQhr3Ie0VXURX69Ns/PQ0WRJkwirVpx
SFNNnPL2KrQu7teR+8DzOmxBy5H6U1jMEGpc6iWYzufM1ufvDoWM7SmB5gG9zIIK
orNsrsUKZtgwfApUnHuV0Z4ILg5X+57scS2/QSytiVL0Uga9/wUFpykpPUfQE+80
dmJoERBUAjmnlgk+uz8Quzu1ZFAoWNZJVvJV/ON6Zlk/rt+ldxhmCATjsjQnYjhF
xNgoOpvnsFQCWuMzNQSRqVaaWNKAfCHePkFxj28sWISu6xgcUzD2vFxTBhBlDNyt
bRbzdRiLfDxe+tIF4DWEhI9ixE7ai41DRDk3hheshphZpzHcldBoBDChWN0LPgPT
8+Ph0nHHBlZnt1BZPpkYM0ArN8dAm3x6DOF0TQQNA33LO2dIpo91jiq9i0EKPMzB
BWXr6JbFT0FDuVCnExNuhawf/Jw4YvmNBEtDm+6NRYlPV0kQFYHhImVLspU/KdjA
wXB3SJuzCQ5K42kWrL8GjXqtBogqfRKgLNWe43k2IRttl7SRqD/0vCAOor+1/9UM
IWZgh/jfUMkEbfFrRw==
=vGZI
-END PGP SIGNATURE End 

Bug#897689: python3-cclib: overly generic python module name: /usr/lib/python3/dist-packages/scripts/__init__.py

[Daniel Leidert]

Am Freitag, den 04.05.2018, 12:59 +0200 schrieb Andreas Beckmann:

> during a test with piuparts I noticed your package uses a very generic
> python module name that now clashes with other packages:
> 
> /usr/lib/python3/dist-packages/scripts/__init__.py

Thanks for the hint. I agree, that this needs to be changed, and
already informed upstream about it. However, there is currently only
one clash, so I will wait for a new upstream release.

Regards, Daniel

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

Bug#887135: manpage-pt: Is package unmaintained?

[Tobias Frost]

Followup-For: Bug #887135
Control: reassign -1 wnpp
Control: retitle -1 O: manpages-pt -- Portuguese Versions of the Manual Pages
Control: severity -1 normal

more than 3 months have passed without reaction to this bug,
therefore orphaning it now on behalf of the MIA team.

--
tobi

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

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

Processed: Re: manpage-pt: Is package unmaintained?

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 wnpp
Bug #887135 [src:manpages-pt] manpage-pt: Is package unmaintained?
Bug reassigned from package 'src:manpages-pt' to 'wnpp'.
No longer marked as found in versions manpages-pt/20040726-4.
Ignoring request to alter fixed versions of bug #887135 to the same values 
previously set
> retitle -1 O: manpages-pt -- Portuguese Versions of the Manual Pages
Bug #887135 [wnpp] manpage-pt: Is package unmaintained?
Changed Bug title to 'O: manpages-pt -- Portuguese Versions of the Manual 
Pages' from 'manpage-pt: Is package unmaintained?'.
> severity -1 normal
Bug #887135 [wnpp] O: manpages-pt -- Portuguese Versions of the Manual Pages
Severity set to 'normal' from 'serious'

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

Processed: found 897482 in 1.2.3-2

[Debian Bug Tracking System]

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

> found 897482 1.2.3-2
Bug #897482 [src:brailleutils] brailleutils: FTBFS: [javac] 
/<>/src/org/daisy/braille/pef/PEFNamespaceContext.java:37: error: 
PEFNamespaceContext is not abstract and does not override abstract method 
getPrefixes(String) in NamespaceContext
Marked as found in versions brailleutils/1.2.3-2.
> thanks
Stopping processing here.

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

Bug#897429: [Pkg-tcltk-devel] Bug#897429: ppc64el: Shared Object not available in the platform

[Breno Leitao]

Hi Sergei,

On Wed, May 02, 2018 at 06:25:55PM +, Sergei Golovan wrote:
> Hi Bruno,
> 
> If you have access to the ppc64el hardware, could you test the fix (I've
> attached a diff, which is to be applied to the 2.1.0-15 sources)? If it's
> okay, I'll ask the release team about a stable update.

Yes, I was able to test it and it is working as expected:

➜  dpkg -c tcl-tclreadline_2.1.0-15+deb9u1_ppc64el.deb | grep so
-rw-r--r-- root/root 67664 2016-10-08 05:04 
./usr/lib/powerpc64le-linux-gnu/libtclreadline-2.1.0.so
lrwxrwxrwx root/root 0 2016-10-08 05:04 
./usr/lib/powerpc64le-linux-gnu/libtclreadline.so -> libtclreadline-2.1.0.so

Thanks for working on it,
Breno

Bug#897458: marked as done (mongo-java-driver: FTBFS: ManualTaglet.java:17: error: package com.sun.tools.doclets does not exist)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 19:50:06 +
with message-id 
and subject line Bug#897458: fixed in mongo-java-driver 3.6.3-1
has caused the Debian Bug report #897458,
regarding mongo-java-driver: FTBFS: ManualTaglet.java:17: error: package 
com.sun.tools.doclets does not exist
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.)


-- 
897458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongo-java-driver
Version: 3.6.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=gradle --with maven_repo_helper
>dh_update_autotools_config -O--buildsystem=gradle
>dh_autoreconf -O--buildsystem=gradle
>dh_auto_configure -O--buildsystem=gradle
>dh_auto_build -O--buildsystem=gradle
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian -Ddebian.package=mongo-java-driver -Dfile.encoding=UTF-8 
> --parallel --max-workers=8 jar
> Initialized native services in: /<>/.gradle/native
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.gradle.internal.reflect.JavaMethod 
> (file:/usr/share/gradle/lib/gradle-base-services-3.4.1.jar) to method 
> java.lang.ClassLoader.getPackages()
> WARNING: Please consider reporting this to the maintainers of 
> org.gradle.internal.reflect.JavaMethod
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> To honour the JVM settings for this build a new JVM will be forked. Please 
> consider using the daemon: 
> https://docs.gradle.org/3.4.1/userguide/gradle_daemon.html.
> Starting daemon process: workingDir = /<>/.gradle/daemon/3.4.1, 
> daemonArgs: [/usr/lib/jvm/java-10-openjdk-amd64/bin/java, 
> -XX:+HeapDumpOnOutOfMemoryError, -Xmx1024m, -Dfile.encoding=UTF-8, 
> -Duser.country=US, -Duser.language=en, -Duser.variant, -cp, 
> /usr/share/gradle/lib/gradle-launcher-3.4.1.jar, 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon, 3.4.1]
> Starting process 'Gradle build daemon'. Working directory: 
> /<>/.gradle/daemon/3.4.1 Command: 
> /usr/lib/jvm/java-10-openjdk-amd64/bin/java -XX:+HeapDumpOnOutOfMemoryError 
> -Xmx1024m -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en 
> -Duser.variant -cp /usr/share/gradle/lib/gradle-launcher-3.4.1.jar 
> org.gradle.launcher.daemon.bootstrap.GradleDaemon 3.4.1
> Successfully started process 'Gradle build daemon'
> An attempt to start the daemon took 0.721 secs.
> Connected to daemon DaemonInfo{pid=3701, 
> address=[3bc6e9d2-c27c-481f-8aaa-26b0b4678505 port:37331, 
> addresses:[/0:0:0:0:0:0:0:1, /127.0.0.1]], state=Busy, 
> lastBusy=1525288618393, 
> context=DefaultDaemonContext[uid=d5f1af79-24da-42cb-a12f-5ed386e88bbb,javaHome=/usr/lib/jvm/java-10-openjdk-amd64,daemonRegistryDir=/<>/.gradle/daemon,pid=3701,idleTimeout=12,daemonOpts=-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}.
>  Dispatching request BuildAndStop{id=fa105524-672d-4429-b498-c9b451caddcd.1, 
> currentDir=/<>}.
> Received result org.gradle.launcher.daemon.protocol.BuildStarted@9573b3b from 
> daemon DaemonInfo{pid=3701, address=[3bc6e9d2-c27c-481f-8aaa-26b0b4678505 
> port:37331, addresses:[/0:0:0:0:0:0:0:1, /127.0.0.1]], state=Busy, 
> lastBusy=1525288618393, 
> context=DefaultDaemonContext[uid=d5f1af79-24da-42cb-a12f-5ed386e88bbb,javaHome=/usr/lib/jvm/java-10-openjdk-amd64,daemonRegistryDir=/<>/.gradle/daemon,pid=3701,idleTimeout=12,daemonOpts=-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}
>  (build should be starting).
> The client will now receive all logging from the daemon (pid: 3701). The 
> daemon log file: /<>/.gradle/daemon/3.4.1/daemon-3701.out.log
> Closing daemon's stdin at end of input.
> The daemon will no longer process any standard input.
> Daemon will be stopped at the end of the build stopping after processing
> Executing build with daemon context: 
> 

Bug#897671: u-boot does not work on sheevaplug

[Markus Krebs]

Just thinking: Maybe it does indeed have something to do with the size 
of u-boot. The one from bodhi is 524 KB, whereas the Debian one is 599 KB.



Am 04.05.2018 um 20:40 schrieb Markus Krebs:
Interesting thoughts, but: I tried again flashing both from within 
Debian and from u-boot (using ${filesize}). $filesize is accepted and 
flashing works, but the plug doesn't boot.
Flashing (again with $filesize, just to confirm it works) the u-boot 
from bodhi-linux (the one I was referring to) works, so it must be the 
u-boot.kwb in Debian which is broken.



Am 04.05.2018 um 19:11 schrieb Martin Michlmayr:

* Vagrant Cascadian  [2018-05-04 08:40]:

I do recall that there was some incompatible change regarding the
environment size on some of the marvell platforms, as u-boot.kwb grew
large enough to overwrite the environment section.

Uh, this might not be an u-boot issue then but a problem with my
upgrade instructions (although Markus said he tried to do the update
from within Debian too, so maybe not).

https://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/ says:
nand write 0x080 0x0 0x8

0x8 = 524288

but:
-rw-r--r-- 1 tbm tbm 599684 Apr  2 03:20 
usr/lib/u-boot/sheevaplug/u-boot.kwb


so we're not writing the whole binary to flash.

The reason I used 0x8 instead of ${filesize} is because very old
u-boot versions (as originally shipped on the SheevaPlug) have
problems with ${filesize}:

 NAND write: device 0 offset 0x0, size 0x68ab0
 nand_write_ecc: Attempt to write not page aligned data
  0 bytes written: ERROR

Bug#897671: u-boot does not work on sheevaplug

[Martin Michlmayr]

* Markus Krebs  [2018-05-04 20:40]:
> Interesting thoughts, but: I tried again flashing both from within Debian
> and from u-boot (using ${filesize}). $filesize is accepted and flashing
> works, but the plug doesn't boot.
> Flashing (again with $filesize, just to confirm it works) the u-boot from
> bodhi-linux (the one I was referring to) works, so it must be the u-boot.kwb
> in Debian which is broken.

In this case, I guess the u-boot binary plus my instructions are
broken. ;)

Maybe you can find out which versions work / do not work.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#897545: node-bluebird: FTBFS: cp: cannot stat '/<>/node-bluebird-3.5.1+dfsg2/js/release/*': No such file or directory

[Hubert Chathi]

It looks like the relevant part of the log is:

,
| nodejs tools/build.js --release --no-minify
| module.js:549
| throw err;
| ^
| 
| Error: Cannot find module 'acorn/walk'
| ...
`

It looks like acorn moved some things around, and acorn/walk is now
acorn/dist/walk.  It seems to work fine after updating the
debian/patches/walk.patch to point to the new location.

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Processed: Re: lintian: testsuite failures with file 5.33

[Debian Bug Tracking System]

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

> tags 896840 + pending
Bug #896840 [src:lintian] lintian: testsuite failures with file 5.33
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#896840: lintian: testsuite failures with file 5.33

[Chris Lamb]

tags 896840 + pending
thanks

Hi all,

> lintian: testsuite failures with file 5.33

Just went to look into this further and realised that I had lost:

  < dwfreed>  lamby: "pie executable" did not exist as a possible output
  of file before this release
< lamby>  dwfreed: Can you followup to the bug? Head is elsewhere and
  not caffeinated enough for context switching yet


Anyway, with this, I've fixed this in git, now pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/3c6c2f2d7c0598f6b1b7ed937b8d29d49f0e502c

  checks/binaries.pm  |  4 ++--
  checks/shared-libs.pm   |  3 ++-
  debian/changelog| 10 +-
  t/tests/binaries-libc-link/desc |  1 -
  t/tests/legacy-libbaz/desc  |  2 +-
  5 files changed, 10 insertions(+), 10 deletions(-)


Regards,

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

Bug#897671: u-boot does not work on sheevaplug

[Markus Krebs]

Interesting thoughts, but: I tried again flashing both from within 
Debian and from u-boot (using ${filesize}). $filesize is accepted and 
flashing works, but the plug doesn't boot.
Flashing (again with $filesize, just to confirm it works) the u-boot 
from bodhi-linux (the one I was referring to) works, so it must be the 
u-boot.kwb in Debian which is broken.



Am 04.05.2018 um 19:11 schrieb Martin Michlmayr:

* Vagrant Cascadian  [2018-05-04 08:40]:

I do recall that there was some incompatible change regarding the
environment size on some of the marvell platforms, as u-boot.kwb grew
large enough to overwrite the environment section.

Uh, this might not be an u-boot issue then but a problem with my
upgrade instructions (although Markus said he tried to do the update
from within Debian too, so maybe not).

https://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/ says:
nand write 0x080 0x0 0x8

0x8 = 524288

but:
-rw-r--r-- 1 tbm tbm 599684 Apr  2 03:20 usr/lib/u-boot/sheevaplug/u-boot.kwb

so we're not writing the whole binary to flash.

The reason I used 0x8 instead of ${filesize} is because very old
u-boot versions (as originally shipped on the SheevaPlug) have
problems with ${filesize}:

 NAND write: device 0 offset 0x0, size 0x68ab0
 nand_write_ecc: Attempt to write not page aligned data
  0 bytes written: ERROR

Bug#881749: marked as done (redmine: creates world-writable tempdir /tmp/bundler/home)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 18:34:52 +
with message-id 
and subject line Bug#881749: fixed in bundler 1.16.1-2
has caused the Debian Bug report #881749,
regarding redmine: creates world-writable tempdir /tmp/bundler/home
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.)


-- 
881749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redmine
Version: 3.3.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + redmine-sqlite redmine-mysql redmine-pgsql

Hi,

during a test with piuparts I noticed your package behaves strangely
while upgrading from 'stretch' to 'buster'.

There is currently no redmine in buster, so the stretch version (which
matches sid) is kept installed.

But after the upgrade an insecure temporary directory appears:

   /tmp/bundler/home

which is

 a) a predictable path name
 b) world writable

This directory does not show up after just an installation in stretch.

redmine(-*) are the only packages showing such behavior.


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

  ERROR: BAD PERMISSIONS
  drwxrwxrwx 3 www-data www-data 60 Nov 13 17:05 /tmp/bundler/home


cheers,


Andreas


redmine_None.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bundler
Source-Version: 1.16.1-2

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated bundler package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 May 2018 21:18:24 -0300
Source: bundler
Binary: ruby-bundler bundler
Architecture: source
Version: 1.16.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 bundler- Manage Ruby application dependencies
 ruby-bundler - Manage Ruby application dependencies (runtime)
Closes: 796383 881749
Changes:
 bundler (1.16.1-2) unstable; urgency=medium
 .
   * debian/patches:
 - convert to gbp-pq format
 - add two new patches:
   0006-Don-t-use-insecure-temporary-directory-as-home-direc.patch
   (Closes: #881749)
   0007-Remove-temporary-home-directories.patch
   (Closes: #796383)
   * Bump Standards-Version to 4.1.4; no changes needed
   * debian/watch: point to gemwatch.debian.net
Checksums-Sha1:
 1e7bcc67cb213a9bc640390e4403c1c8df4828f0 2144 bundler_1.16.1-2.dsc
 fe4706453f92f83f010ee0daabaf0fa4918657d7 10136 bundler_1.16.1-2.debian.tar.xz
 c4c0ea08d223ce6a5b45cea3f483b30a5913073f 6768 bundler_1.16.1-2_source.buildinfo
Checksums-Sha256:
 f3b47f7c94e7f436385e577cc6c06272af5c88bcd2e56d8a3cbc54fa76164807 2144 
bundler_1.16.1-2.dsc
 52046936bef347dce85d28539f8f380ab42df09f73f41c5d440239c85ef908a9 10136 
bundler_1.16.1-2.debian.tar.xz
 6ba998692f59a8c11ffa58f159419dd0de623f50c2c16adfc62f1dc066a2b93e 6768 
bundler_1.16.1-2_source.buildinfo
Files:
 add89feff773a057570930b3a74d1166 2144 ruby optional bundler_1.16.1-2.dsc
 7ab0e19298e71778b907e83765489eca 10136 ruby optional 
bundler_1.16.1-2.debian.tar.xz
 a7333eba4dc22663f40201603460fbb9 6768 ruby optional 
bundler_1.16.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlrso5AACgkQ/A2xu81G
C97x5xAArQtV+Mq6L/U8X7cLOu0OBGXBMOoofDXdFdmeFceMs4P5cGjsv2fR8dzi
ldgQoTSZP7KWFP2+N8xpWZoukba0wNe2JdL5BOEO9i/WXkjluclsbLls7M1lQHNm
E3Cq01pSEazku3XETMdyCHbgwnBLP35SPwwihkDTLSzCxtQPN0n75gYjw8Vv4bcb
bjfSJyIGYrXDRu4UBjYLQR9ACbsBdEQtihLLA2d2gwTk+TXX/X5L9jQmgky2h5Gr
vDJpAUN88f0FHk4RsxxF28zCs0+yR9LTGgl6ScC/2bH7Cc55Vs6c1x4VQqFq7DSn
xs4AGpDspXHstr+l5iGJaNEEvpar/X36e4G20ctg8LnZCel9WtMPLyKqKNwy7ijV
4YKz/Sh92Joe4rBcZPLy4UiekGMQ4gP/ySnbwE2PF57v+jvDn4tnaRBlwT+4bL2m
H4HgRs8dUVmJhhyOJOyFYhqxoNeDtcQ2qALZ6mg7VjcPTvvMFsPw8/GVbJIepQVy
w0gbN22wLwOh4ekmr+sQp2bne6te5xvPM5DyF62hgKfmODRl1YQBm2FnEG6gBX3Q

Bug#886833: marked as done (rsvg_pixbuf_from_file_at_size broken in recent librsvg2-2)

[Debian Bug Tracking System]

Your message dated Fri, 4 May 2018 20:18:59 +0200
with message-id <4aec5f69-f7bc-d855-3722-1b116d7ce...@debian.org>
and subject line rsvg_pixbuf_from_file_at_size broken in recent librsvg2-2
has caused the Debian Bug report #886833,
regarding rsvg_pixbuf_from_file_at_size broken in recent librsvg2-2
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.)


-- 
886833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gweled
Version: 0.9.1-4
Severity: grave

--- Please enter the report below this line. ---
Can no longer use the program. Error from CLI:

~$ gweled 
*WARNING* **: Locale not supported by C library. 
*WARNING* **: GError set over the top of a previous GError or uninitializ



--- System information. ---
Architecture: 
Kernel:   Linux 4.14.0-2-amd64

Debian Release: buster/sid
  500 yakkety ppa.launchpad.net 
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 
  100 jessie-backports ftp.us.debian.org 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-
libatk1.0-0 (>= 1.12.4) | 
libc6 (>= 2.15) | 
libcairo2(>= 1.2.4) | 
libfontconfig1(>= 2.11) | 
libfreetype6 (>= 2.2.1) | 
libgdk-pixbuf2.0-0  (>= 2.22.0) | 
libglib2.0-0(>= 2.37.3) | 
libgtk2.0-0 (>= 2.20.0) | 
libmikmod3   (>= 3.3.3) | 
libpango-1.0-0  (>= 1.14.0) | 
libpangocairo-1.0-0 (>= 1.14.0) | 
libpangoft2-1.0-0   (>= 1.14.0) | 
librsvg2-2  (>= 2.14.4) | 


Package's Recommends field is empty.

Package's Suggests field is empty.




--- End Message ---
--- Begin Message ---
Version: 2.42.3-1

Fixed by the latest upstream release:

- gitlab#198 - Fix: Make rsvg_pixbuf_from_file() and its derived
  functions work again.  Now we have tests for the whole public API.

-- 
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
--- End Message ---

Bug#897661: marked as done (libsynctex1: Texmaker-libsynctex1:amd64 2018.20180416.47457-1)

[Debian Bug Tracking System]

Your message dated Fri, 4 May 2018 19:40:44 +0200
with message-id 
and subject line 
has caused the Debian Bug report #896656,
regarding libsynctex1: Texmaker-libsynctex1:amd64 2018.20180416.47457-1
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.)


-- 
896656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsynctex1
Version: 2018.20180416.47457-1
Severity: normal
Tags: a11y

Dear Maintainer,

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

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

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


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (950, 'testing'), (500, 'oldstable-updates'), (50, 'unstable'), 
(10, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-3-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libsynctex1 depends on:
ii  libc6   2.27-3
ii  zlib1g  1:1.2.8.dfsg-5

libsynctex1 recommends no packages.

libsynctex1 suggests no packages.

-- no debconf information

Texmaker doesn't start sice upgrade libsynctex1:amd64 
2018.20180416.47457-1.Texmaker star  when downgrade manually libsynctex1:amd64 
2018.20180416.47457-1 -> 2014.20140926.35254-6
--- End Message ---
--- Begin Message ---
Package: texmaker
Version: 5.0.2-2


Hi,

this bug is fixed in texmaker 5.0.2-2. It was just uploaded to unstable but I
failed to close the bugs correctly in the changelog.

Best,

Philip





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

Bug#896656: marked as done (texmaker: Texmaker fails to start due to new libsynctex1)

[Debian Bug Tracking System]

Your message dated Fri, 4 May 2018 19:40:44 +0200
with message-id 
and subject line 
has caused the Debian Bug report #896656,
regarding texmaker: Texmaker fails to start due to new libsynctex1
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.)


-- 
896656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texmaker
Version: 5.0.2-1+b1
Severity: important

Dear Maintainer,

Starting Texmaker exits with the following error message:
texmaker: symbol lookup error: texmaker: undefined symbol: synctex_next_result

A search revealed that this problem is most likely due to libsynctex1 being too 
recent for Texmaker

It renders Texmaker completely unusable because there is no way to run it.

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

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

Versions of packages texmaker depends on:
ii  libc6 2.27-3
ii  libgcc1   1:8-20180414-1
ii  libgl11.0.0+git20180308-1
ii  libqt5concurrent5 5.10.1+dfsg-5
ii  libqt5core5a [qtbase-abi-5-10-0]  5.10.1+dfsg-5
ii  libqt5gui55.10.1+dfsg-5
ii  libqt5network55.10.1+dfsg-5
ii  libqt5printsupport5   5.10.1+dfsg-5
ii  libqt5script5 5.10.1+dfsg-2
ii  libqt5widgets55.10.1+dfsg-5
ii  libqt5xml55.10.1+dfsg-5
ii  libstdc++68-20180414-1
ii  libsynctex1   2018.20180416.47457-1
ii  texmaker-data 5.0.2-1

Versions of packages texmaker recommends:
ii  aspell0.60.7~20110707-4
ii  asymptote 2.44-1
ii  ghostscript   9.22~dfsg-2.1
ii  hunspell-en-us [hunspell-dictionary]  1:2017.08.24
pn  latex-beamer  
ii  netpbm2:10.0-15.3+b2
ii  psutils   1.17.dfsg-4
ii  texlive-lang-english  2018.20180416-1
ii  texlive-latex-extra   2018.20180416-1

Versions of packages texmaker suggests:
pn  texlive-lang-all  

-- no debconf information
--- End Message ---
--- Begin Message ---
Package: texmaker
Version: 5.0.2-2


Hi,

this bug is fixed in texmaker 5.0.2-2. It was just uploaded to unstable but I
failed to close the bugs correctly in the changelog.

Best,

Philip





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

Bug#897071: marked as done (texmaker does notr start "symbol lookup error" and "undefined symbol: synctex_next_result")

[Debian Bug Tracking System]

Your message dated Fri, 4 May 2018 19:40:44 +0200
with message-id 
and subject line 
has caused the Debian Bug report #896656,
regarding texmaker does notr start "symbol lookup error" and "undefined symbol: 
synctex_next_result"
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.)


-- 
896656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texmaker
Version: 5.0.2-1+b1
Severity: important

Dear Maintainer,

When I try to start texmaker, it does not start. Instead I get the
following:

$ texmaker
texmaker: symbol lookup error: texmaker: undefined symbol:
synctex_next_result

The result is fully reproducible.

With best regards,
Wojtek

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

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

Versions of packages texmaker depends on:
ii  libc6 2.27-3
ii  libgcc1   1:8-20180414-1
ii  libgl11.0.0-2
ii  libqt5concurrent5 5.10.1+dfsg-5
ii  libqt5core5a [qtbase-abi-5-10-0]  5.10.1+dfsg-5
ii  libqt5gui55.10.1+dfsg-5
ii  libqt5network55.10.1+dfsg-5
ii  libqt5printsupport5   5.10.1+dfsg-5
ii  libqt5script5 5.10.1+dfsg-2
ii  libqt5widgets55.10.1+dfsg-5
ii  libqt5xml55.10.1+dfsg-5
ii  libstdc++68-20180414-1
ii  libsynctex1   2018.20180416.47457-1
ii  texmaker-data 5.0.2-1

Versions of packages texmaker recommends:
ii  aspell0.60.7~20110707-4
ii  asymptote 2.44-1
ii  ghostscript   9.22~dfsg-2.1
ii  hunspell-en-us [hunspell-dictionary]  1:2017.08.24
pn  latex-beamer  
ii  myspell-pl [myspell-dictionary]   20170707-1
ii  netpbm2:10.0-15.3+b2
ii  psutils   1.17.dfsg-4
ii  texlive-lang-english  2018.20180416-1
ii  texlive-latex-extra   2018.20180416-1

Versions of packages texmaker suggests:
pn  texlive-lang-all  

-- no debconf information
--- End Message ---
--- Begin Message ---
Package: texmaker
Version: 5.0.2-2


Hi,

this bug is fixed in texmaker 5.0.2-2. It was just uploaded to unstable but I
failed to close the bugs correctly in the changelog.

Best,

Philip





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

Bug#896567: marked as done (texmaker: FTBFS against newer libsyntex)

[Debian Bug Tracking System]

Your message dated Fri, 4 May 2018 19:40:44 +0200
with message-id 
and subject line 
has caused the Debian Bug report #896567,
regarding texmaker: FTBFS against newer libsyntex
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.)


-- 
896567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: texmaker
Version: 5.0.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid buster

texmaker FTBFS against the new version of libsyntex in unstable:
| g++ -Wl,-z,relro -Wl,-z,now -o texmaker .obj/main.o .obj/dropshadowlabel.o 
.obj/geticon.o .obj/texmakerapp.o .obj/texmaker.o .obj/documentview.o 
.obj/pageitem.o .obj/presentationview.o .obj/minisplitter.o .obj/playerbutton.o 
.obj/symbollistwidget.o .obj/icondelegate.o .obj/latexeditor.o 
.obj/latexhighlighter.o .obj/latexeditorview.o .obj/linenumberwidget.o 
.obj/lightlatexeditor.o .obj/lightlatexhighlighter.o 
.obj/lightlinenumberwidget.o .obj/sourceview.o .obj/logeditor.o 
.obj/loghighlighter.o .obj/findwidget.o .obj/gotolinewidget.o 
.obj/lightfindwidget.o .obj/lightgotolinewidget.o .obj/replacewidget.o 
.obj/structdialog.o .obj/filechooser.o .obj/graphicfilechooser.o 
.obj/tabbingdialog.o .obj/arraydialog.o .obj/tabdialog.o .obj/letterdialog.o 
.obj/addoptiondialog.o .obj/quickdocumentdialog.o .obj/quickxelatexdialog.o 
.obj/usermenudialog.o .obj/usertooldialog.o .obj/refdialog.o 
.obj/configdialog.o .obj/aboutdialog.o .obj/spellerdialog.o 
.obj/xmltagslistwidget.o .obj/blockdata.o .obj/keysequencedialog.o 
.obj/pdfviewerwidget.o .obj/pdfviewer.o .obj/userquickdialog.o 
.obj/encodingdialog.o .obj/usercompletiondialog.o .obj/texdocdialog.o 
.obj/scandialog.o .obj/exportdialog.o .obj/usertagslistwidget.o 
.obj/addtagdialog.o .obj/versiondialog.o .obj/unicodedialog.o 
.obj/unicodeview.o .obj/quickbeamerdialog.o .obj/svnhelper.o .obj/affentry.o 
.obj/affixmgr.o .obj/csutil.o .obj/dictmgr.o .obj/hashmgr.o .obj/hunspell.o 
.obj/phonet.o .obj/suggestmgr.o .obj/filemgr.o .obj/replist.o .obj/hunzip.o 
.obj/qtlocalpeer.o .obj/qtsingleapplication.o .obj/qtsinglecoreapplication.o 
.obj/CharDistribution.o .obj/ChineseGroupProber.o .obj/JapaneseGroupProber.o 
.obj/JpCntx.o .obj/LangBulgarianModel.o .obj/LangCyrillicModel.o 
.obj/LangGreekModel.o .obj/LangHebrewModel.o .obj/LangHungarianModel.o 
.obj/LangThaiModel.o .obj/nsBig5Prober.o .obj/nsCharSetProber.o 
.obj/nsEscCharsetProber.o .obj/nsEscSM.o .obj/nsEUCJPProber.o 
.obj/nsEUCKRProber.o .obj/nsEUCTWProber.o .obj/nsGB2312Prober.o 
.obj/nsHebrewProber.o .obj/nsLatin1Prober.o .obj/nsMBCSGroupProber.o 
.obj/nsMBCSSM.o .obj/nsSBCharSetProber.o .obj/nsSBCSGroupProber.o 
.obj/nsSJISProber.o .obj/nsUniversalDetector.o .obj/qencodingprober.o 
.obj/UnicodeGroupProber.o .obj/jsbridge.o .obj/qpdfdocument.o 
.obj/qpdfbookmarkmodel.o .obj/cfx_systemhandler.o .obj/fpdfdoc.o 
.obj/fpdfeditimg.o .obj/fpdfeditpage.o .obj/fpdfformfill.o .obj/fpdfppo.o 
.obj/fpdfsave.o .obj/fpdftext.o .obj/fpdfview.o .obj/fpdf_dataavail.o 
.obj/fpdf_ext.o .obj/fpdf_flatten.o .obj/fpdf_progressive.o 
.obj/fpdf_searchex.o .obj/fpdf_sysfontinfo.o .obj/fpdf_transformpage.o 
.obj/fsdk_actionhandler.o .obj/fsdk_annothandler.o .obj/fsdk_baseannot.o 
.obj/fsdk_baseform.o .obj/fsdk_mgr.o .obj/fsdk_rendercontext.o 
.obj/BigInteger.o .obj/BigIntegerUtils.o .obj/BigUnsigned.o 
.obj/BigUnsignedInABase.o .obj/fx_crypt.o .obj/fx_crypt_aes.o 
.obj/fx_crypt_sha.o .obj/clines.o .obj/cpdf_variabletext.o .obj/cpvt_color.o 
.obj/cpvt_fontmap.o .obj/cpvt_generateap.o .obj/cpvt_sectioninfo.o 
.obj/cpvt_wordinfo.o .obj/csection.o .obj/ctypeset.o .obj/doc_action.o 
.obj/doc_annot.o .obj/doc_basic.o .obj/doc_bookmark.o .obj/doc_form.o 
.obj/doc_formcontrol.o .obj/doc_formfield.o .obj/doc_link.o .obj/doc_metadata.o 
.obj/doc_ocg.o .obj/doc_tagged.o .obj/doc_utils.o .obj/doc_viewerPreferences.o 
.obj/doc_vt.o .obj/cpdf_modulemgr.o .obj/Adobe-CNS1-UCS2_5.o .obj/B5pc-H_0.o 
.obj/B5pc-V_0.o .obj/CNS-EUC-H_0.o .obj/CNS-EUC-V_0.o .obj/ETen-B5-H_0.o 
.obj/ETen-B5-V_0.o .obj/ETenms-B5-H_0.o .obj/ETenms-B5-V_0.o 
.obj/HKscs-B5-H_5.o .obj/HKscs-B5-V_5.o .obj/UniCNS-UCS2-H_3.o 
.obj/UniCNS-UCS2-V_3.o .obj/UniCNS-UTF16-H_0.o .obj/cmaps_cns1.o 
.obj/Adobe-GB1-UCS2_5.o .obj/GB-EUC-H_0.o .obj/GB-EUC-V_0.o .obj/GBK-EUC-H_2.o 
.obj/GBK-EUC-V_2.o .obj/GBK2K-H_5.o .obj/GBK2K-V_5.o .obj/GBKp-EUC-H_2.o 
.obj/GBKp-EUC-V_2.o .obj/GBpc-EUC-H_0.o .obj/GBpc-EUC-V_0.o 
.obj/UniGB-UCS2-H_4.o .obj/UniGB-UCS2-V_4.o .obj/cmaps_gb1.o 

Bug#897466: marked as done (bart-view: FTBFS: multind.h:17:10: fatal error: misc/nested.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 17:34:44 +
with message-id 
and subject line Bug#897466: fixed in bart 0.4.03-2
has caused the Debian Bug report #897466,
regarding bart-view: FTBFS: multind.h:17:10: fatal error: misc/nested.h: No 
such file or directory
to be marked as done.

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

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


-- 
897466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bart-view
Version: 0.1.00-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c11 -fopenmp -export-dynamic -o view 
> -I/usr/include/bart/ `pkg-config --cflags gtk+-3.0` src/main.c src/view.c 
> src/draw.c `pkg-config --libs gtk+-3.0` /usr/lib/bart//libmisc.a 
> /usr/lib/bart//libnum.a -lm -lpng
> In file included from src/view.c:24:0:
> /usr/include/bart/num/multind.h:17:10: fatal error: misc/nested.h: No such 
> file or directory
>  #include "misc/nested.h"
>   ^~~
> compilation terminated.
> make[1]: *** [Makefile:52: view] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/bart-view_0.1.00-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: bart
Source-Version: 0.4.03-2

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

Debian distribution maintenance software
pp.
Martin Uecker  (supplier of updated bart 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 03 May 2018 21:44:55 +0200
Source: bart
Binary: bart libbart-dev octave-bart
Architecture: source
Version: 0.4.03-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Martin Uecker 
Description:
 bart   - tools for computational magnetic resonance imaging
 libbart-dev - Development files for BART
 octave-bart - Octave bindings for BART
Closes: 897466
Changes:
 bart (0.4.03-2) unstable; urgency=medium
 .
   * Add missing header to libbart-dev. (Closes: #897466)
Checksums-Sha1:
 686ff5607047b2d3cb065abab4db8cd6ce7fc1a3 2119 bart_0.4.03-2.dsc
 ba10b8f48991becde02401acd0d4d3ea384405bd 4344 bart_0.4.03-2.debian.tar.xz
 312e94933d53fe098171ac54d7551276cc452b38 6634 bart_0.4.03-2_amd64.buildinfo
Checksums-Sha256:
 aa893d21a4cc339f684fd09e92ea925f8d13f9f44fa5796485d6881dae7c38aa 2119 
bart_0.4.03-2.dsc
 07b97126347acbea1dd1c790896ff051ef517b9a579440383bc518aec0dc8e2f 4344 
bart_0.4.03-2.debian.tar.xz
 dd14a0e81259ae359cb681b1653cf2f1746b0538987396c81eeba73f253516e8 6634 
bart_0.4.03-2_amd64.buildinfo
Files:
 8f7ba2634e9000f730c678cf8dfefec3 2119 science optional bart_0.4.03-2.dsc
 7718ff97969baea804a742df919e375e 4344 science optional 
bart_0.4.03-2.debian.tar.xz
 8a44a4253f9a1b8f04eb746832aa37c5 6634 science optional 
bart_0.4.03-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlrsktAOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtGeVg/8CwzB1CzuSNsjKTnAuo1EEGNUwwzjX07dJ95e
ms/theDH35oPifpuLXHGiEJ5rq+uuE7lJoiXR/cJZ7EeUXOcCzWNJcASnTyL+qah
ER6WiZd03yVnSPQqM0Dg6GYHw/KhjZN1wKXgPl/pUkUW++vtExAIoU91qz6q9ccJ
R8xNnxwNUYqvF7ZcMC3GPTrCqxFsR+Cfh9JTrh93VjGtP/nCKFMYO6oRkSmTR5CU
Rgg5BF/8vOhJArP8dh6SwM9qe9VM6RnJLA5tZWzbh57xKMmDUZfsg1qPEbxbrHiA
b4OcOxtLiMY+NvxHQZKYxl2NvlLvIv7j6rSq1MWbSO9huoeJ0Mb4bMVV14x8hZZF

Bug#897671: u-boot does not work on sheevaplug

[Martin Michlmayr]

* Vagrant Cascadian  [2018-05-04 08:40]:
> I do recall that there was some incompatible change regarding the
> environment size on some of the marvell platforms, as u-boot.kwb grew
> large enough to overwrite the environment section.

Uh, this might not be an u-boot issue then but a problem with my
upgrade instructions (although Markus said he tried to do the update
from within Debian too, so maybe not).

https://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/ says:
nand write 0x080 0x0 0x8

0x8 = 524288

but:
-rw-r--r-- 1 tbm tbm 599684 Apr  2 03:20 usr/lib/u-boot/sheevaplug/u-boot.kwb

so we're not writing the whole binary to flash.

The reason I used 0x8 instead of ${filesize} is because very old
u-boot versions (as originally shipped on the SheevaPlug) have
problems with ${filesize}:

NAND write: device 0 offset 0x0, size 0x68ab0
nand_write_ecc: Attempt to write not page aligned data
 0 bytes written: ERROR

-- 
Martin Michlmayr
http://www.cyrius.com/

Processed: Re: Bug#897466: bart-view: FTBFS: multind.h:17:10: fatal error: misc/nested.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 bart
Bug #897466 [src:bart-view] bart-view: FTBFS: multind.h:17:10: fatal error: 
misc/nested.h: No such file or directory
Bug reassigned from package 'src:bart-view' to 'bart'.
No longer marked as found in versions bart-view/0.1.00-1.
Ignoring request to alter fixed versions of bug #897466 to the same values 
previously set

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

Bug#897466: bart-view: FTBFS: multind.h:17:10: fatal error: misc/nested.h: No such file or directory

[Andreas Tille]

Control: reassign -1 bart

On Thu, May 03, 2018 at 08:21:35PM +, Uecker, Martin wrote:
> 
> this is now fixed in the git repo for bart (not bart-view!).

Bug reassigned by this mail - will upload soon.

Thanks a lot for the quick fix

  Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#897898: [Pkg-openldap-devel] Bug#897898: libldap-common is missing

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #897898 [openldap] libldap-common is missing
Added tag(s) pending.

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

Bug#897898: [Pkg-openldap-devel] Bug#897898: libldap-common is missing

[Ryan Tandy]

Control: tag -1 pending

Uploaded new packages. Builds are underway now and should become 
available in unstable after the 19:52 UTC dinstall run.

Bug#897250: FTBFS with libonig 6.8.1-1

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Moritz,

first thanks for your work.

Am Freitag, den 04.05.2018, 14:36 +0200 schrieb Moritz Muehlenhoff:
> B0;115;0cOn Fri, May 04, 2018 at 02:21:41PM +0200, Moritz Muehlenhoff
> wrote:
> > On Wed, May 02, 2018 at 12:02:03PM +0200, Moritz Muehlenhoff wrote:
> > > Hi Jörg,
> > > 
> > > On Mon, Apr 30, 2018 at 09:59:11PM +0200, Jörg Frings-Fürst
> > > wrote:
> > > > 
> > > > for the liboinig transition I testing the build of hhvm again
> > > > libonig 6.8.1-1.
> > > > 
> > > > The build fails with
> > > > 
> > > > [quote]
> > > > In file included from /build/hhvm-
> > > > 3.21.0+dfsg/hphp/runtime/base/program-
> > > > functions.cpp:117:0:
> > > > /usr/include/oniguruma.h:347:1: error: 'UChar' does not name a
> > > > type; did you
> > > > mean 'char'?
> > > >  UChar* onigenc_strdup P_((OnigEncoding enc, const UChar* s,
> > > > const UChar*
> > > > end));
> > > >  ^
> > > >  char
> > > 
> > > But that's a problem in the lobonig headers? 
> > > hphp/runtime/base/program-functions.cpp:117 simply does a
> > > 
> > > #include 
> > 
> > Actually this needs some changes on the HHVM end, found a fix.
> 
> The patch for HHVM is still needed to fix that the regex struc was
> moved to a
> private header.
> 
> It also adds a workaround to address a bug in Oniguruma, though:
> HHVM uses ONIG_ESCAPE_UCHAR_COLLISION and that is broken in
> 6.8.0/6.8.1
> (see the comment in https://github.com/facebook/hhvm/commit/0bbbf67ad
> c2643d04353cf2bdda2e1aa7c92d36f)
> 

I have test it with libonig 6.8.2. It looks good. 

I hope that my sponsor can upload the new release shortly.



> Cheers,
> Moritz

CU
Jörg
- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlrsgpIACgkQCfifPIyh
0l19Kg/+Jaa9riAExzDEPQCdMYeFgZiF2UmgfW3ehDi916WvEeJb+WPajowU0bBh
QBVSM2N+AH9RFbnbspI6Xqxxa9yRtDk9fYh6Qed2IoO7H9f+AKGVghwH5YnKGDcc
f/ScTsynsVuFIylwNqymXqyimpLG8kGiR01pPDlUdgqRxuMTvxCyVYUqfWezK1Lr
/eoVJlBZBP/WwjEjS3ma5VlVGjLPseKcXQ9XqQqKZPP1MdfcZ5tCj/xdR3y75kuv
U0IUbMyd9MazZkXEYbTEgWr097eNvGdDX/kj53b2qwWuluWYSttWytXkPbU3iCFy
b4tJVVOfQFzcGrdWKT6v+uqOkzcW8yUh08H1Lsfz2uGb/5AoPX/V0iSp//Oo4vY+
t6EPCW2Rse3LTkYoYJBTCYxg1pRvLoC2taguRROr7WfROBn0pxZbAMD5rBde2VVY
lhQeqRFppWCuFtyqZb9bYv5kma4gKxu9gaQuNwa2N9S+zp/0RSPM8D9Cab6JeyT4
vTY9Z2abZ1zRwR3Bnupns+zhb/0BrZ8zQBvaYCpK3U/tyIIKngWGkO5LClqxNCxP
8mETHdhjLjoSN0nOoTRuP3O3pQSIAypBS1iQiMYiBYwqNdKQUpee6x0eW55yIIBo
jTzHEktW5OdTAYjsy9prrW2+RMdZPgGZnESwVZVqf1VahS0ggXY=
=NjlM
-END PGP SIGNATURE-

Bug#897671: u-boot does not work on sheevaplug

[Vagrant Cascadian]

On 2018-05-04, Martin Michlmayr  wrote:
> * Markus Krebs  [2018-05-04 06:33]:
>> Version: 2018.03+dfsg1-2
>> 
>> The u-boot.kwb provided at https://forum.doozan.com/read.php?3,12381 works.
>
> That is version 2017.07.  If you have time, could you try some
> versions from http://snapshot.debian.org/package/u-boot/  Not all of
> them but maybe
>
> 2018.01+dfsg1-2
> 2017.11+dfsg1-3
> 2017.09+dfsg1-3
> 2017.07+dfsg1-3

And also 2018.05-rc3+dfsg-1, currently in debian experimental; maybe
it's fixed in the newest version.

I do recall that there was some incompatible change regarding the
environment size on some of the marvell platforms, as u-boot.kwb grew
large enough to overwrite the environment section.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#897149: Bug #897149 in apt marked as pending

[julian . klode]

Control: tag -1 pending

Hello,

Bug #897149 in apt 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/apt-team/apt/commit/39d9e217a22901892647499ee695ba472a111d25


Fix build with new gtest

Still allow the older one to be used.

Closes: #897149



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/897149

Processed: Bug #897149 in apt marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #897149 [src:apt] Package erroneously expects googletest headers in 
/usr/include
Bug #897459 [src:apt] apt: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
 undefined reference to `pthread_create'
Added tag(s) pending.
Added tag(s) pending.

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

Bug#897592: ebtables: randomly FTBFS - makefile is not parallel safe

[James Cowgill]

Hi,

On 03/05/18 16:27, Alberto Molina Coballes wrote:
> Thanks James, these kinds of errors are often difficult to deal with.
> 
> Do you think that it should be enough disabling parallel build in dh?
> Tested on amd64 seems to work properly.

Yes that should workaround the problem.

It seems to me that these issues are caused by the rearrangements in the
last two hunks of the "makefile_adjustments.patch" patch. Maybe you can
remove those hunks? The package seems to build ok without them (except
that ebtables-config needs moving).

James



signature.asc
Description: OpenPGP digital signature

Bug#897483: marked as done (ust: FTBFS: LTTngUst.c:20:10: fatal error: org_lttng_ust_LTTngUst.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 15:13:25 +
with message-id 
and subject line Bug#897483: fixed in ust 2.10.1-3
has caused the Debian Bug report #897483,
regarding ust: FTBFS: LTTngUst.c:20:10: fatal error: org_lttng_ust_LTTngUst.h: 
No such file or directory
to be marked as done.

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

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


-- 
897483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ust
Version: 2.10.1-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
> -I../include/lttng  -I../include -I../include 
> -I/usr/lib/jvm/default-java/include -I/usr/lib/jvm/default-java/include/linux 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o LTTngUst.lo LTTngUst.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../include/lttng 
> -I../include -I../include -I/usr/lib/jvm/default-java/include 
> -I/usr/lib/jvm/default-java/include/linux -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wall -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -c LTTngUst.c  -fPIC -DPIC -o 
> .libs/LTTngUst.o
> LTTngUst.c:20:10: fatal error: org_lttng_ust_LTTngUst.h: No such file or 
> directory
>  #include "org_lttng_ust_LTTngUst.h"
>   ^~
> compilation terminated.
> make[4]: *** [Makefile:501: LTTngUst.lo] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/05/02/ust_2.10.1-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ust
Source-Version: 2.10.1-3

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

Debian distribution maintenance software
pp.
Michael Jeanson  (supplier of updated ust 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: Fri, 04 May 2018 10:46:44 -0400
Source: ust
Binary: liblttng-ust0 liblttng-ust-ctl4 liblttng-ust-dev liblttng-ust-java 
liblttng-ust-java-jni liblttng-ust-agent-java liblttng-ust-agent-java-jni 
liblttng-ust-python-agent0 python3-lttngust
Architecture: source
Version: 2.10.1-3
Distribution: unstable
Urgency: medium
Maintainer: Jon Bernard 
Changed-By: Michael Jeanson 
Description:
 liblttng-ust-agent-java - LTTng 2.0 Userspace Tracer (Java agent library)
 liblttng-ust-agent-java-jni - LTTng 2.0 Userspace Tracer (Java agent JNI 
interface)
 liblttng-ust-ctl4 - LTTng 2.0 Userspace Tracer (trace control library)
 liblttng-ust-dev - LTTng 2.0 Userspace Tracer (development files)
 liblttng-ust-java - LTTng 2.0 Userspace Tracer (Java support library)
 liblttng-ust-java-jni - LTTng 2.0 Userspace Tracer (JNI interface)
 liblttng-ust-python-agent0 - LTTng 2.0 Userspace Tracer (Python agent native 
library)
 liblttng-ust0 - LTTng 2.0 Userspace Tracer (tracing libraries)
 python3-lttngust - LTTng 2.0 Userspace Tracer (Python 3 UST agent)
Closes: 897483
Changes:
 ust (2.10.1-3) unstable; urgency=medium
 .
   * [6798480] Update symbols for new riscv64 architecture
   * [f81465e] Drop patch forcing obsolete java bytecode version 1.6
   * [26128f4] Drop gcj compat patch
   * [ca241ec] Fix build failure with openjdk >= 10 (Closes: #897483)
Checksums-Sha1:
 3daab61e951ab8e9ded20736036b50522c8b06cf 2769 ust_2.10.1-3.dsc
 3779c9ed75e3fa532797431f2c47979ce73614a7 

Processed: Re: access-modifier-checker: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 3.7-1
Bug #897525 [libcommons-lang3-java] access-modifier-checker: FTBFS: Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
Marked as fixed in versions libcommons-lang3-java/3.7-1.
> close -1
Bug #897525 [libcommons-lang3-java] access-modifier-checker: FTBFS: Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar
Marked Bug as done

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

Bug#897525: access-modifier-checker: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar

[Emmanuel Bourg]

Control: fixed -1 3.7-1
Control: close -1

Processed: tagging 893167

[Debian Bug Tracking System]

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

> retitle 893167 eboard: stack smashing & source repository update
Bug #893167 [eboard] Stack smashing protection trigged in eboard
Changed Bug title to 'eboard: stack smashing & source repository update' from 
'Stack smashing protection trigged in eboard'.
> tags 893167 + upstream
Bug #893167 [eboard] eboard: stack smashing & source repository update
Added tag(s) upstream.
> block 893167 by 890673
Bug #893167 [eboard] eboard: stack smashing & source repository update
893167 was not blocked by any bugs.
893167 was not blocking any bugs.
Added blocking bug(s) of 893167: 890673
> thanks
Stopping processing here.

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

Processed: severity of 897898 is grave

[Debian Bug Tracking System]

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

> severity 897898 grave
Bug #897898 [openldap] libldap-common is missing
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2

[Benjamin Kaduk]

Hi Lucas,

On Wed, May 02, 2018 at 10:52:53PM +0200, Lucas Nussbaum wrote:
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > rx/perf.ok
> > volser/vos-man..ok
> > volser/vos..FAILED 5
> > bucoord/backup-man..ok
> > kauth/kas-man...ok
> > 
> > Failed Set Fail/Total (%) Skip Stat  Failing Tests
> > -- --    
> > 
> > volser/vos1/6 17%00  5

Unfortunately the upstream build system does not capture verbose
test output for display in case of failure, but from the test number
we can deduce that what is failing is that an outputted list of
addresses does not match the expected string:
char expecting[] = "10.0.0.0\n10.0.0.1\n10.0.0.2\n10.0.0.3\n10.0.0.4\n"
   "10.0.0.5\n10.0.0.6\n10.0.0.7\n10.0.0.8\n10.0.0.9\n"
   "10.0.0.10\n10.0.0.11\n10.0.0.12\n10.0.0.13\n"
   "10.0.0.14\n10.0.0.15\n";

I note that this test is disabled when the system's hostname
resolves to a loopback address because those addresses are forbidden
from being entered into the database as fileserver addresses, but
even when I change my local configuration to avoid that, I still
cannot reproduce the test failure locally.

I surmise that the AWS machine may be getting assigned a 10/8
address as its primary address, and perhaps that would interfere
with some of what the test is doing.  Do you happen to know more
about the network configuration on the AWS systems used for these
autopkgtests?

Thanks,

Ben

Processed: Python 2 support removed upstream

[Debian Bug Tracking System]

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

> forwarded 897644 https://github.com/spacetelescope/gwcs/pull/119
Bug #897644 [python-gwcs] python-gwcs depends on cruft package python-asdf
Set Bug forwarded-to-address to 
'https://github.com/spacetelescope/gwcs/pull/119'.
> thanks
Stopping processing here.

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

Bug#897250: FTBFS with libonig 6.8.1-1

[Moritz Muehlenhoff]

B0;115;0cOn Fri, May 04, 2018 at 02:21:41PM +0200, Moritz Muehlenhoff wrote:
> On Wed, May 02, 2018 at 12:02:03PM +0200, Moritz Muehlenhoff wrote:
> > Hi Jörg,
> > 
> > On Mon, Apr 30, 2018 at 09:59:11PM +0200, Jörg Frings-Fürst wrote:
> > > 
> > > for the liboinig transition I testing the build of hhvm again libonig 
> > > 6.8.1-1.
> > > 
> > > The build fails with
> > > 
> > > [quote]
> > > In file included from /build/hhvm-3.21.0+dfsg/hphp/runtime/base/program-
> > > functions.cpp:117:0:
> > > /usr/include/oniguruma.h:347:1: error: 'UChar' does not name a type; did 
> > > you
> > > mean 'char'?
> > >  UChar* onigenc_strdup P_((OnigEncoding enc, const UChar* s, const UChar*
> > > end));
> > >  ^
> > >  char
> > 
> > But that's a problem in the lobonig headers? 
> > hphp/runtime/base/program-functions.cpp:117 simply does a
> > 
> > #include 
> 
> Actually this needs some changes on the HHVM end, found a fix.

The patch for HHVM is still needed to fix that the regex struc was moved to a
private header.

It also adds a workaround to address a bug in Oniguruma, though:
HHVM uses ONIG_ESCAPE_UCHAR_COLLISION and that is broken in 6.8.0/6.8.1
(see the comment in 
https://github.com/facebook/hhvm/commit/0bbbf67adc2643d04353cf2bdda2e1aa7c92d36f)

Cheers,
Moritz

Bug#897250: FTBFS with libonig 6.8.1-1

[Moritz Muehlenhoff]

On Wed, May 02, 2018 at 12:02:03PM +0200, Moritz Muehlenhoff wrote:
> Hi Jörg,
> 
> On Mon, Apr 30, 2018 at 09:59:11PM +0200, Jörg Frings-Fürst wrote:
> > 
> > for the liboinig transition I testing the build of hhvm again libonig 
> > 6.8.1-1.
> > 
> > The build fails with
> > 
> > [quote]
> > In file included from /build/hhvm-3.21.0+dfsg/hphp/runtime/base/program-
> > functions.cpp:117:0:
> > /usr/include/oniguruma.h:347:1: error: 'UChar' does not name a type; did you
> > mean 'char'?
> >  UChar* onigenc_strdup P_((OnigEncoding enc, const UChar* s, const UChar*
> > end));
> >  ^
> >  char
> 
> But that's a problem in the lobonig headers? 
> hphp/runtime/base/program-functions.cpp:117 simply does a
> 
> #include 

Actually this needs some changes on the HHVM end, found a fix.

Cheers,
Moritz

Bug#897501: marked as done (xmds2: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 12:04:46 +
with message-id 
and subject line Bug#897501: fixed in xmds2 2.2.3+dfsg-6
has caused the Debian Bug report #897501,
regarding xmds2: FTBFS: tests 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.)


-- 
897501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmds2
Version: 2.2.3+dfsg-5
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/xmds2-2.2.3+dfsg'
> debian/tests/run-tests -b
> Checking for 'g++' (c++ compiler): /usr/bin/g++ 
> Checking whether the compiler works  : yes 
> Checking that we have a C++ compiler : yes 
> Checking whether we are cross-compiling  : no 
> Checking whether we can link to only static libraries : no (will use dynamic 
> libraries) 
> Trying to make compiler optimise for this machine : yes 
> Trying to make compiler tune for this machine : yes 
> Checking for compiler flags -O3   : yes 
> Checking for compiler flags -ffast-math   : yes 
> Checking for compiler flags -funroll-all-loops: yes 
> Checking for compiler flags -fomit-frame-pointer  : yes 
> Checking for compiler flags -falign-loops : yes 
> Checking for compiler flags -fstrict-aliasing : yes 
> Checking for compiler flags -momit-leaf-frame-pointer : yes 
> Checking for cautious math flags  : yes 
> Checking for Autovectorisation: yes 
> Checking for OpenMP   : yes 
> Checking for pthreads : yes 
> Checking for compiler debug flags : yes 
> Checking for srandomdev   : not found 
> Checking for /dev/urandom : yes 
> Checking for program h5cc : /usr/bin/h5cc 
> Checking for HDF5 (static library): yes 
> Checking for HDF5 High-level library (static library) : yes 
> Checking for function H5Lexists   : yes 
> Checking for libxmds (static library) : no (will try dynamic 
> library instead) 
> Checking for libxmds (dynamic library): no (it's optional 
> anyway) 
> Checking for Intel's Vector Math Library (static library) : no (will try 
> dynamic library instead) 
> Checking for Intel's Vector Math Library (dynamic library) : no (it's 
> optional anyway) 
> Checking aggressive dSFMT compile flags: yes 
> Checking for Intel's Math Kernel Library (static library)  : no (will try 
> dynamic library instead) 
> Checking for Intel's Math Kernel Library (dynamic library) : no (it's 
> optional anyway) 
> Checking for ATLAS's CBLAS. (static library)   : no (will try 
> dynamic library instead) 
> Checking for ATLAS's CBLAS. (dynamic library)  : yes 
> Checking for GSL (static library)  : yes 
> Checking for FFTW3 (static library): yes 
> Checking for single-precision FFTW3 (static library)   : yes 
> Checking for threading support in FFTW3 (static library)   : yes 
> Checking for OpenMP support in FFTW3 (static library)  : yes 
> Checking for threading support in single-precision FFTW3 (static library) : 
> yes 
> Checking for OpenMP support in single-precision FFTW3 (static library): 
> yes 
> Checking for program mpic++   : 
> /usr/bin/mpic++ 
> Checking for 'g++' (c++ compiler) : 
> /usr/bin/mpic++ 
> Checking whether the compiler works   : 
> yes 
> Checking that we have a C++ compiler  : 
> yes 
> Checking whether we are cross-compiling   : 
> no 
> Checking whether we can link to only static libraries : 
> no (will use dynamic libraries) 
> Trying to make compiler optimise for this machine : 
> yes 
> Trying to make compiler tune for this machine : 
> yes 
> Checking for compiler flags -O3   : 
> yes 
> Checking for compiler flags -ffast-math  

Bug#897671: u-boot does not work on sheevaplug

[Martin Michlmayr]

* Markus Krebs  [2018-05-04 06:33]:
> Version: 2018.03+dfsg1-2
> 
> The u-boot.kwb provided at https://forum.doozan.com/read.php?3,12381 works.

That is version 2017.07.  If you have time, could you try some
versions from http://snapshot.debian.org/package/u-boot/  Not all of
them but maybe

2018.01+dfsg1-2
2017.11+dfsg1-3
2017.09+dfsg1-3
2017.07+dfsg1-3

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#897691: python3-hbmqtt: overly generic python module name: /usr/lib/python3/dist-packages/scripts/__init__.py

[Andreas Beckmann]

Package: python3-hbmqtt
Version: 0.9.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
python module name that now clashes with other packages:

/usr/lib/python3/dist-packages/scripts/__init__.py


Andreas

Bug#897689: python3-cclib: overly generic python module name: /usr/lib/python3/dist-packages/scripts/__init__.py

[Andreas Beckmann]

Package: python3-cclib
Version: 1.5.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
python module name that now clashes with other packages:

/usr/lib/python3/dist-packages/scripts/__init__.py


Andreas

Bug#896796: marked as done (vulkan: missing build dependency on python3-distutils)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 10:51:41 +
with message-id 
and subject line Bug#896796: fixed in vulkan 1.1.73+dfsg-1
has caused the Debian Bug report #896796,
regarding vulkan: missing build dependency on python3-distutils
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.)


-- 
896796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vulkan
Version: 1.1.70+dfsg1-1
Severity: serious

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

...
cd /build/1st/vulkan-1.1.70+dfsg1/external/glslang/build/SPIRV && /usr/bin/c++  
-DAMD_EXTENSIONS -DENABLE_HLSL -DENABLE_OPT -DGLSLANG_OSINCLUDE_UNIX 
-DNV_EXTENSIONS  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -O3 -DNDEBUG -fPIC   -Wall -Wmaybe-uninitialized 
-Wuninitialized -Wunused -Wunused-local-typedefs -Wunused-parameter 
-Wunused-value -Wunused-variable -Wunused-but-set-parameter 
-Wunused-but-set-variable -fno-exceptions -Wno-reorder -std=c++11 -o 
CMakeFiles/SPVRemapper.dir/doc.cpp.o -c 
/build/1st/vulkan-1.1.70+dfsg1/external/glslang/SPIRV/doc.cpp
Traceback (most recent call last):
  File 
"/build/1st/vulkan-1.1.70+dfsg1/external/glslang/External/spirv-tools/utils/generate_registry_tables.py",
 line 19, in 
import distutils.dir_util
ModuleNotFoundError: No module named 'distutils.dir_util'
make[4]: *** 
[External/spirv-tools/source/CMakeFiles/SPIRV-Tools.dir/build.make:144: 
External/spirv-tools/generators.inc] Error 1


Due to

python3.6 (3.6.5~rc1-2) unstable; urgency=medium

  * python3.6: Drop dependency on python3-distutils.
...
 -- Matthias Klose   Tue, 20 Mar 2018 14:29:58 +0800
--- End Message ---
--- Begin Message ---
Source: vulkan
Source-Version: 1.1.73+dfsg-1

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated vulkan 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: Fri, 04 May 2018 13:18:00 +0300
Source: vulkan
Binary: libvulkan1 libvulkan-dev vulkan-utils
Architecture: source
Version: 1.1.73+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Description:
 libvulkan-dev - Vulkan loader library -- development files
 libvulkan1 - Vulkan loader library
 vulkan-utils - Miscellaneous Vulkan utilities
Closes: 891582 896796
Changes:
 vulkan (1.1.73+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
   * Move layers from libvulkan-dev to libvulkan1. (Closes: #891582)
   * control: Add python3-distutils to build-depends. (Closes: #896796)
   * Refresh patches.
Checksums-Sha1:
 fa52210f74adf90147064edc0082677ee625db4f 2230 vulkan_1.1.73+dfsg-1.dsc
 e90481980f47826ed4171680c0747f0e0382bca3 5328240 vulkan_1.1.73+dfsg.orig.tar.xz
 8ffb160fdbdebd23dfbcef1ef6a2afc4b8d06a03 8124 
vulkan_1.1.73+dfsg-1.debian.tar.xz
 929781647a7f2aa28831acfbd2fc9536a9ba6e03 7165 
vulkan_1.1.73+dfsg-1_source.buildinfo
Checksums-Sha256:
 1cea0afa1d59ad002fbcf59a996abb229da316b269044785674060f80386b60d 2230 
vulkan_1.1.73+dfsg-1.dsc
 de9bbc276132303b8138b9148e4a9c7ecae6ce38af5b1478796a53ee589b7182 5328240 
vulkan_1.1.73+dfsg.orig.tar.xz
 08ba7b417b4dcae234e2f7043c59e6af1b3ba29466bbc7ad4b94208b355d5ab5 8124 
vulkan_1.1.73+dfsg-1.debian.tar.xz
 fb54b925ac07e9c80f33f12ef7d96f431882ba4168961f52f4acdf8dff681563 7165 
vulkan_1.1.73+dfsg-1_source.buildinfo
Files:
 019abd7307ca131ec885cee9b0590a13 2230 libs optional vulkan_1.1.73+dfsg-1.dsc
 31b118075dd96c2296cf9bf41f91eed6 5328240 libs optional 
vulkan_1.1.73+dfsg.orig.tar.xz
 ee2eb504718e3047d9e41436ea97eab2 8124 libs optional 
vulkan_1.1.73+dfsg-1.debian.tar.xz
 e70037f70b88349d152a63402597695d 7165 libs optional 
vulkan_1.1.73+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlrsM7MACgkQy3AxZaiJ

Bug#897508: [Debian-ha-maintainers] Bug#897508: Bug#897508: gfs2-utils: FTBFS: dh_auto_test: make -j8 -Oline check VERBOSE=1 returned exit code 2

[Valentin Vidic]

On Wed, May 02, 2018 at 11:02:55PM +0200, Valentin Vidic wrote:
> Thanks, I can reproduce the errors too and will try to figure it out.
> The build was definitely working less than month ago when the last
> version was released, so something else in the system has changed.

After updating linux-libc-dev from 4.15.17-1 to 4.16.5-1 mkfs.gfs2
starts to segfault due to a change in gfs2_ondisk.h. I've contacted
cluster-de...@redhat.com to see if they have a fix already...

-- 
Valentin

Bug#897644: python-gwcs depends on cruft package python-asdf

[Ole Streicher]

Hi,

since version 2, upstream of asdf does no longer support Python 2 [1];
therefore it is removed from the package. I therefore would recommend to
also remove the Python 2 version of gwcs.

[1] http://asdf.readthedocs.io/en/latest/asdf/changes.html

Best regards

Ole

Bug#892267: 3dldf: FTBFS on mips64el, hurd-i386, ia64, powerpc, x32 - "src/3dldf tngnts_1.ldf" segfaults

[Hilmar Preuße]

On 07.03.2018 13:13, James Cowgill wrote:

> 3dldf FTBFS on the above architectures with the error:
>> ../src/3dldf tngnts_1.ldf
>> GNU 3DLDF Version 2.0.3
>> Copyright (C) 2013 The Free Software Foundation
>> Author:  Laurence D. Finston
>>

Just for the records: I tried to build the package using gcc-8. The
program can be compiled but using it is still a pain as the program
still crashes:

Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".

Core was generated by `./3dldf sample2.ldf'.

Program terminated with signal SIGSEGV, Segmentation fault.

#0  0xb7adeb35 in std::locale::~locale() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6

(gdb) bt

#0  0xb7adeb35 in std::locale::~locale() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6

#1  0x004c78ef in std::basic_streambuf::~basic_streambuf (this=0x2257cc4, __in_chrg=)

at /usr/include/c++/8/streambuf:204

#2  std::basic_filebuf::~basic_filebuf
(this=0x2257cc4, __in_chrg=) at
/usr/include/c++/8/fstream:247

#3  std::basic_ofstream::~basic_ofstream
(this=0x2257cc0, __in_chrg=, __vtt_parm=)

at /usr/include/c++/8/fstream:793

#4  Thread_Info_Type::~Thread_Info_Type (this=,
__in_chrg=) at ./pspglb.web:1626

#5  0x0052f614 in yyparse(void*) () at parser.y++:22016

#6  0x00517499 in main () at /usr/include/c++/8/bits/stl_vector.h:930

#7  0xb7756e81 in __libc_start_main (main=0x516500 , argc=2,
argv=0xbfed44a4, init=0x7c7a30 <__libc_csu_init>,

fini=0x7c7a90 <__libc_csu_fini>, rtld_fini=0xb7ef29a0 <_dl_fini>,
stack_end=0xbfed449c) at ../csu/libc-start.c:310

#8  0x005197f9 in _start () at ./main.web:1735

For using gcc-8 I simply changed the symlinks gcc, g++, cpp to version
8. Not sure if this is sufficient. Yes, I could install gcc from
experimental too.

sid:/usr/bin# ls -l gcc* g++* cpp*

lrwxrwxrwx 1 root root  5 May  4 09:53 cpp -> cpp-8

lrwxrwxrwx 1 root root 20 Apr 28 15:20 cpp-7 -> i686-linux-gnu-cpp-7

lrwxrwxrwx 1 root root 20 May  2 11:43 cpp-8 -> i686-linux-gnu-cpp-8

lrwxrwxrwx 1 root root  5 May  4 09:53 g++ -> g++-8

lrwxrwxrwx 1 root root 20 Apr 28 15:20 g++-7 -> i686-linux-gnu-g++-7

lrwxrwxrwx 1 root root 20 May  2 11:43 g++-8 -> i686-linux-gnu-g++-8

lrwxrwxrwx 1 root root  5 May  4 09:53 gcc -> gcc-8

lrwxrwxrwx 1 root root 20 Apr 28 15:20 gcc-7 -> i686-linux-gnu-gcc-7

lrwxrwxrwx 1 root root 20 May  2 11:43 gcc-8 -> i686-linux-gnu-gcc-8

lrwxrwxrwx 1 root root  8 Apr  4 12:16 gcc-ar -> gcc-ar-7


Hilmar
-- 
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#896191: FTBFS with TeX Live 2018

[Norbert Preining]

> dblatex converts a ` (back-tick) from the xml input from into \`{} in
> the LaTeX source. AFAIK (I'm not 100% sure) this was never correct, the

This was a bug in xecjk which is already fixed, will be in one of the
next uploads.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: Re: Bug#897661: libsynctex1: Texmaker-libsynctex1:amd64 2018.20180416.47457-1

[Debian Bug Tracking System]

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

> reassign 897661 texmaker
Bug #897661 [libsynctex1] libsynctex1: Texmaker-libsynctex1:amd64 
2018.20180416.47457-1
Bug reassigned from package 'libsynctex1' to 'texmaker'.
No longer marked as found in versions texlive-bin/2018.20180416.47457-1.
Ignoring request to alter fixed versions of bug #897661 to the same values 
previously set
> severity 897661 grave
Bug #897661 [texmaker] libsynctex1: Texmaker-libsynctex1:amd64 
2018.20180416.47457-1
Severity set to 'grave' from 'normal'
> merge 897661 896656
Bug #897661 [texmaker] libsynctex1: Texmaker-libsynctex1:amd64 
2018.20180416.47457-1
Bug #897071 [texmaker] texmaker does notr start "symbol lookup error" and 
"undefined symbol: synctex_next_result"
Added tag(s) a11y.
Added tag(s) a11y.
Bug #897661 [texmaker] libsynctex1: Texmaker-libsynctex1:amd64 
2018.20180416.47457-1
Marked as found in versions texmaker/5.0.2-1.
Bug #896656 [texmaker] texmaker: Texmaker fails to start due to new libsynctex1
Merged 896656 897071 897661
> stop
Stopping processing here.

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

Bug#896733: marked as done (nosexcover: missing build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Fri, 04 May 2018 08:00:33 +
with message-id 
and subject line Bug#896733: fixed in nosexcover 1.0.11-1.1
has caused the Debian Bug report #896733,
regarding nosexcover: missing build dependency on dh-python
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.)


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

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

...
 fakeroot debian/rules clean
dh clean --with python2,python3 --buildsystem=pybuild
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 11) line 
1.
BEGIN failed--compilation aborted at (eval 11) line 1.

make: *** [debian/rules:4: clean] Error 2
--- End Message ---
--- Begin Message ---
Source: nosexcover
Source-Version: 1.0.11-1.1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated nosexcover package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 02 May 2018 07:21:57 +
Source: nosexcover
Binary: python-nosexcover python3-nosexcover
Architecture: source all
Version: 1.0.11-1.1
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Thomas Goirand 
Description:
 python-nosexcover - Add Cobertura-style XML coverage report to nose (Python2 
version)
 python3-nosexcover - Add Cobertura-style XML coverage report to nose (Python3 
version)
Closes: 896733
Changes:
 nosexcover (1.0.11-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add missing dh-python build-depends (Closes: #896733).
Checksums-Sha1:
 d06fcad56f323fd8baa52f6917e2b247204768db 1925 nosexcover_1.0.11-1.1.dsc
 a96fad3a6208c164f38dad943aec80d7c79c2656 2556 
nosexcover_1.0.11-1.1.debian.tar.xz
 7391587c3cb3225af7a421da2ba10386d00a22c5 6852 
nosexcover_1.0.11-1.1_amd64.buildinfo
 ab0defaea543046fe5931d13b5ec4787e34ad006 5576 
python-nosexcover_1.0.11-1.1_all.deb
 79c87a8eaacbc0b37989b28969b7f9261132753a 5648 
python3-nosexcover_1.0.11-1.1_all.deb
Checksums-Sha256:
 07da016212ef1b8618d80be9fd6306b7a2a727e0450866d1c0b6489be231a1c5 1925 
nosexcover_1.0.11-1.1.dsc
 dbd1b5a38d40310e6ea216e776f4003fc573775948504525183da50c5a9a89fd 2556 
nosexcover_1.0.11-1.1.debian.tar.xz
 e6d681cabee212855865c0dfb03e018bfa12a04eb3a88cf4c62d980b0e555852 6852 
nosexcover_1.0.11-1.1_amd64.buildinfo
 6136db22b08f331e72ff245f468ca0a2ba07a71c6171630338b4e160bd95ca3f 5576 
python-nosexcover_1.0.11-1.1_all.deb
 285e21421968115f633198d02a77f42a5d8627d1f9e6a4901283971000ce3977 5648 
python3-nosexcover_1.0.11-1.1_all.deb
Files:
 16bfa28875aba61ede7f2658c624d77b 1925 python optional nosexcover_1.0.11-1.1.dsc
 ed4a9ce972db6d930a25a1190502c905 2556 python optional 
nosexcover_1.0.11-1.1.debian.tar.xz
 e1e1227a3393fb89761e67bffda09ebe 6852 python optional 
nosexcover_1.0.11-1.1_amd64.buildinfo
 60074f4c334a6fc8b02353076848576b 5576 python optional 
python-nosexcover_1.0.11-1.1_all.deb
 22b01180467234c0f2edd968002a27f4 5648 python optional 
python3-nosexcover_1.0.11-1.1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtKCq/KhshgVdBnYUq1PlA1hod6YFAlrpaFcACgkQq1PlA1ho
d6Z3GhAAoJmzbgxnl3gGB2dpa1z7XbplhgbPzRED0QoloE0F1UZmK3X1AYUx9vFc
Cq6v/gzgC4Z9WQXle9oID5v9unsgZP/R3skSRKVOS3UAHpOxZ9epowiOvs31d540
VubxuEYHcAWFfWMCJ1EbwdlrytcoOZBvniiiA2bbN/nk16dxWZmPbSomt7ioWVuX
tGtFtuOHTTnzaGqz1Af/37YLuQ5anUe2JQa8GAE4W1YAs/lgBGQviRT1e7USy5xs

Bug#897098: ppl FTBFS with TeX Live 2018

[Roberto Bagnara]

On 04/28/2018 03:15 PM, Adrian Bunk wrote:
> Source: ppl
> Version: 1:1.2-2
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppl.html
> 
> ...
> pl-1.2/doc/bugseng_logo.pdf>] [4] [1] [2] (./index.tex
> Underfull \hbox (badness 1) detected at line 9
> [][][]
> pdfTeX warning (ext4): destination with the same identifier (name{page.1}) 
> has 
> been already used, duplicate ignored
>  
>\relax 
> l.25 
>   [1]) (/build/1st/ppl-1.2/doc/gpl.tex
> 
> ! LaTeX Error: Can be used only in preamble.
> 
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.1 \documentclass
>   [a4paper,12pt]{article}
> ? 
> ! Emergency stop.
>  ...  
>   
> l.1 \documentclass
>   [a4paper,12pt]{article}
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on refman.log.
> make[2]: *** [Makefile:6: refman.pdf] Error 1
> 

Thanks for the report.  This has just been fixed with the
following commit.

commit addd0535f36e4a2734b9b5321e2e0ad398c5e20c
Author: Roberto Bagnara 
Date:   Fri May 4 09:26:25 2018 +0200

Disable Kpathsea case-insensitive filename matching.
Case-insensitive filename matching is done by default in non-system
directories starting from TeX Live 2018.

diff --git a/doc/Makefile.am b/doc/Makefile.am
index 3daf9ccea..ffc3c12d5 100644
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -866,7 +866,7 @@ devref-configured-ocaml-interface.latex-dir \
 user-configured-java-interface.latex-dir \
 devref-configured-java-interface.latex-dir

-TEX_ENV = TEXINPUTS=$(abs_srcdir):$(TEXINPUTS)
+TEX_ENV = TEXINPUTS=$(abs_srcdir):$(TEXINPUTS) texmf_casefold_search=0

 .SECONDARY: $(LATEX_DIRS)




-- 
 Prof. Roberto Bagnara

Applied Formal Methods Laboratory - University of Parma, Italy
mailto:bagn...@cs.unipr.it
  BUGSENG srl - http://bugseng.com
  mailto:roberto.bagn...@bugseng.com



smime.p7s
Description: S/MIME Cryptographic Signature

Processed: Re: [DRE-maint] Bug#897464: ruby-cairo: FTBFS: ERROR: Test "ruby2.5" failed: Error: test: time(PDFSurfaceTest::#set_metadata::modified date): Poppler::Error::Invalid: Failed to load documen

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libpoppler-glib8 0.63.0-2
Bug #897464 [src:ruby-cairo] ruby-cairo: FTBFS: ERROR: Test "ruby2.5" failed: 
Error: test: time(PDFSurfaceTest::#set_metadata::modified date): 
Poppler::Error::Invalid: Failed to load document
Bug reassigned from package 'src:ruby-cairo' to 'libpoppler-glib8'.
No longer marked as found in versions ruby-cairo/1.15.12-1.
Ignoring request to alter fixed versions of bug #897464 to the same values 
previously set
Bug #897464 [libpoppler-glib8] ruby-cairo: FTBFS: ERROR: Test "ruby2.5" failed: 
Error: test: time(PDFSurfaceTest::#set_metadata::modified date): 
Poppler::Error::Invalid: Failed to load document
Marked as found in versions poppler/0.63.0-2.
> forcemerge 896596 -1
Bug #896596 [libpoppler-glib8] poppler-glib always returns 0 length for 
PopplerInputStream
Bug #896596 [libpoppler-glib8] poppler-glib always returns 0 length for 
PopplerInputStream
Added tag(s) buster and sid.
Bug #897464 [libpoppler-glib8] ruby-cairo: FTBFS: ERROR: Test "ruby2.5" failed: 
Error: test: time(PDFSurfaceTest::#set_metadata::modified date): 
Poppler::Error::Invalid: Failed to load document
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=106295'.
Added indication that 897464 affects 
src:ruby-cairo,src:ruby-gnome2,ruby-poppler,src:ruby-poppler
Merged 896596 897464

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

Bug#897464: [DRE-maint] Bug#897464: ruby-cairo: FTBFS: ERROR: Test "ruby2.5" failed: Error: test: time(PDFSurfaceTest::#set_metadata::modified date): Poppler::Error::Invalid: Failed to load document

[dai]

Control: reassign -1 libpoppler-glib8 0.63.0-2
Control: forcemerge 896596 -1
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Bug#897675: libtcd: not binNMU safe

[Emilio Pozuelo Monfort]

Source: libtcd
Version: 2.2.2-2
Severity: serious
Tags: buster sid

Hi,

Your package is not binNMU safe. This is reported by the lintian tag

https://lintian.debian.org/tags/not-binnmuable-any-depends-any.html

Basically your package libtcd-dev has:

Depends: libtcd0 (= ${source:Version})

That should be ${binary:Version}, since the version will differ from
the source version in a binNMU.

Cheers,
Emilio

Bug#897674: p7zip-rar: CVE-2018-10115

[Salvatore Bonaccorso]

Source: p7zip-rar
Version: 16.02-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for p7zip-rar.

CVE-2018-10115[0]:
| Incorrect initialization logic of RAR decoder objects in 7-Zip 18.03
| and before can lead to usage of uninitialized memory, allowing remote
| attackers to cause a denial of service (segmentation fault) or execute
| arbitrary code via a crafted RAR archive.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-10115
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10115
[1] 
https://landave.io/2018/05/7-zip-from-uninitialized-memory-to-remote-code-execution/
[2] https://sourceforge.net/p/sevenzip/discussion/45797/thread/adc65bfa/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore