Bug#920695: knot-resolver: uninstallable and FTBFS in stretch-backports

[Daniel Kahn Gillmor]

Control: severity 920695 important

On Thu 2019-02-28 22:06:09 -0500, Daniel Kahn Gillmor wrote:
> So i'm marking #920695 as fixed in 3.2.1-1 with the hope of getting all
> of these migrations to move forward.

I've tagged the shared git repo for both knot-dns and for knot-resolver
source package stretch-backports releases.

I've also published the relevant packages to
https://people.debian.org/~dkg/knot-stretch-backports/ so that people
can get access to them if they want them before stretch-backports is
capable of taking them.

In order to try to help the transition along, i'm reducing the severity
of this bug report as well.   If there's a serious objection to this
severity reduction, please feel free to correct it back again, and
explain what you think the right thing to do is.

happy hacking,

   --dkg

Processed: Re: Bug#920695: knot-resolver: uninstallable and FTBFS in stretch-backports

[Debian Bug Tracking System]

Processing control commands:

> severity 920695 important
Bug #920695 [src:knot-resolver] knot-resolver: uninstallable and FTBFS in 
stretch-backports
Severity set to 'important' from 'serious'

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

Processed: fixed 920695 in 3.2.1-1

[Debian Bug Tracking System]

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

> fixed 920695 3.2.1-1
Bug #920695 [src:knot-resolver] knot-resolver: uninstallable and FTBFS in 
stretch-backports
Marked as fixed in versions knot-resolver/3.2.1-1.
> thanks
Stopping processing here.

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

Bug#920695: knot-resolver: uninstallable and FTBFS in stretch-backports

[Daniel Kahn Gillmor]

Control: 920695 fixed 3.2.1-1

I'm able to rebuild knot-resolver just fine on stretch, when i build
3.2.1-1 against a backported knot 2.7.6-2.  I'll be uploading those to
stretch-backports shortly, but they can't go in until they've reached
testing.

But knot won't go into testing untlik knot-resolver migrates, due to
autopkgtests (see #922172), and knot-resolver itself won't migrate until
this bug report is non-RC.  heh, a tangled mess.

So i'm marking #920695 as fixed in 3.2.1-1 with the hope of getting all
of these migrations to move forward.

 --dkg


signature.asc
Description: PGP signature

Bug#922179: shim-signed depends on packages not repos

[Cyril Brulebois]

Hi Steve,

Moritz Mühlenhoff  (2019-02-26):
> On Fri, Feb 15, 2019 at 07:28:57PM +0100, Cyril Brulebois wrote:
> > Right, this also breaks the build of the debian-installer source package
> > on amd64 since its build dependencies cannot be satisfied.
> 
> Is there an ETA for a fix?

We're getting deeper and deeper into the freeze, and we seem to be
lacking a reasonable timeline regarding Secure Boot for Buster.

The problems we're seeing are:
 1. the hard shim/shim-signed dependency means the shim-signed package
isn't installable in sid;
 2. src:debian-installer therefore cannot be built because of
unsatisfiable build-dependencies;
 3. shim cannot migrate to testing.

We don't know how long it will take to get the new shim signed by
Microsoft; until that happens these problems will continue to block
development (and potentially the release).

Apologies for not spotting these as potential problems earlier, before
asking you to upload the new version of shim into unstable. :-(

If our understanding is correct, it seems that re-uploading the contents
of the previous shim package (either with an over-long “+really”-like
version, with an epoch, or with the trick detailed below), and adjusting
the versioned dependency in shim-signed to match, would make both
packages installable again. It wouldn't change anything regarding the
actual signatures: they would be validated as previously.

The “old” shim/shim-signed couple is already able to chainload
GRUB/Linux/etc. signed by either the Debian test key (as we've been
testing recently) or the embedded Debian production key. This would be a
quick fix for the next D-I Alpha/RC, but could also serve as a last
resort solution for buster itself if we don't get an updated shim-signed
package in time. In the meantime, we could upload the new shim
source/binary package to experimental for people to work with.

The main drawbacks (compared to actually getting an updated shim-signed
package) would be:
 1. lacking the newer shim code that upstream EFI people would like us
to be using;
 2. only having support for amd64.

Until an updated shim-signed package is available, it seems to us that
the re-upload suggested above would fix all issues we're seeing, without
having any negative impact. That's why we're considering doing so in the
next few days. 

Looking at the version numbers we have:
 - 0.9+1474479173.6c180c6-1 in testing
 - 15+1533136590.3beb971-2 in sid

so we could re-upload with 16+1474479173.6c180c6-1, which would sort
higher than the version in sid, but also lower than
16+1533136590.3beb971-*, that can be used to re-upload the new shim when
the matching shim-signed is ready.

How does that sound to you please?


Finally: we don't want to steal too much of your time for shim. It seems
like now would be a really good time to move maintenance formally to the
debian-efi team?


Cheers,
Cyril Brulebois & Steve McIntyre for the D-I / EFI teams
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#922773: marked as done (FTBFS since the acl/attr uploads of 2019-05-15+16)

[Debian Bug Tracking System]

Your message dated Fri, 01 Mar 2019 01:49:15 +
with message-id 
and subject line Bug#922773: fixed in adequate 0.15.2
has caused the Debian Bug report #922773,
regarding FTBFS since the acl/attr uploads of 2019-05-15+16
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.)


-- 
922773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adequate
Version: 0.15.1
Severity: serious
Tags: ftbfs

Since the uploads of acl and attr with this changelog entry, adequate
FTBFS:

   * Perform a proper and correct /usr-merge transition by moving the package
 contents from / to /usr.

Build log of a failed build:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/adequate.html

The relevant lines are:

TESTING: ./adequate coreutils
coreutils: bin-or-sbin-binary-requires-usr-lib-library /bin/cp => 
/usr/lib/x86_64-linux-gnu/libacl.so.1
coreutils: bin-or-sbin-binary-requires-usr-lib-library /bin/cp => 
/usr/lib/x86_64-linux-gnu/libattr.so.1
coreutils: bin-or-sbin-binary-requires-usr-lib-library /bin/mv => 
/usr/lib/x86_64-linux-gnu/libacl.so.1
coreutils: bin-or-sbin-binary-requires-usr-lib-library /bin/mv => 
/usr/lib/x86_64-linux-gnu/libattr.so.1
make: *** [debian/rules:17: debian/build-stamp] Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

While I personally value that
bin-or-sbin-binary-requires-usr-lib-library check a lot, Debian has
decided to not go down that path and to allow library and other
dependencies from /bin/ and /sbin/ into /usr/. With acl and attr
having its libraries in /usr/lib/, coreutils is no more adequate-clean
and hence that test fails.

IMHO adequate shouldn't use any other package than itself or maybe a
dummy package included in the test suite — as lintian does, although
that's probably more difficult for as-installed testing.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: adequate
Source-Version: 0.15.2

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated adequate package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 01 Mar 2019 02:12:21 +0100
Source: adequate
Binary: adequate
Architecture: source all
Version: 0.15.2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Axel Beckert 
Description:
 adequate   - Debian package quality testing tool
Closes: 922773
Changes:
 adequate (0.15.2) unstable; urgency=medium
 .
   * QA upload, see #786808.
 .
   [ Jakub Wilk ]
   * Update copyright years.
   * Add license information for libpoppler.so.60 and libpoppler.so.61.
 .
   [ Axel Beckert ]
   * Set Maintainer to Debian QA Group.
   * Convert packaging VCS repo to git and use salsa.debian.org for it.
   * Use HTTPS for debian/copyright format URL.
   * Use dpkg instead of coreutils for build-time smoke test. (Closes:
 #922773)
   * Apply "wrap-and-sort -a".
   * Use debhelper compatibility level 12.
 + Drop debian/compat.
 + Depend on "debhelper-compat (= 12)".
   * Drop version from (build-)dependency on perl.  (5.14 is already in
 oldoldstable.) Use only ${perl:Depends} in binary package.
   * Use $(DEB_VERSION) instead of dpkg-parsechangelog.
   * Declare compliance with Debian Policy 4.3.0. (No changes needed.)
   * Set "Rules-Requires-Root: no".
   * Drop "compression = gzip" from debian/source/options.
   * Fix tests/run-tests to 

Bug#923365: ftgl: FTBFS in sid (LaTeX error)

[Santiago Vila]

tags 923365 - moreinfo
close 923365
thanks

Big oops! Sorry, I have now double-checked and the report was based on
a build log dated 2019-02-26, but apparently it took a while for me to
actually submit the bug. The underlying bug in texlive was fixed in
the meantime.

The package is sunny everywhere here:

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

so I'm closing this.

Thanks.

Processed: Re: ftgl: FTBFS in sid (LaTeX error)

[Debian Bug Tracking System]

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

> tags 923365 - moreinfo
Bug #923365 [src:ftgl] ftgl: FTBFS in sid (LaTeX error)
Removed tag(s) moreinfo.
> close 923365
Bug #923365 [src:ftgl] ftgl: FTBFS in sid (LaTeX error)
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: tagging 922773

[Debian Bug Tracking System]

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

> tags 922773 + pending
Bug #922773 [src:adequate] FTBFS since the acl/attr uploads of 2019-05-15+16
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: cyrus-imapd: fails to build against libclamav9

[Debian Bug Tracking System]

Processing control commands:

> block 922004 by -1
Bug #922004 [release.debian.org] transition: clamav
922004 was not blocked by any bugs.
922004 was not blocking any bugs.
Added blocking bug(s) of 922004: 923498

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

Bug#923498: cyrus-imapd: fails to build against libclamav9

[Sebastian Andrzej Siewior]

Source: cyrus-imapd
Version: 3.0.8-3
Severity: Serious
Control: block 922004 by -1 

By the time we planned the transition for libclamav there was no
cyrus-imapd package which depended on libclamav-dev but this changed. I
just realised that.
The package failed to build because the ABI on clamav's side changed
between 0.100 -> 0.101:

|gcc -DHAVE_CONFIG_H -I.   -I. -I./lib -I. -I./lib 
-DLIBEXEC_DIR=\"/usr/lib/cyrus/bin\" -DSBIN_DIR=\"/usr/lib/cyrus/bin\" 
-DSYSCONF_DIR=\"/etc\" -DHAVE_CONFIG_H  -I/usr/include/libxml2   
-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include -fPIC  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -g -fno-strict-aliasing -pipe -O2 -c -o 
imap/quota.o imap/quota.c
|imap/cyr_virusscan.c: In function ?clamav_scanfile?:
|imap/cyr_virusscan.c:197:21: error: ?CL_SCAN_STDOPT? undeclared (first use in 
this function); did you mean ?CL_DB_STDOPT??
| CL_SCAN_STDOPT);
| ^~
| CL_DB_STDOPT
|imap/cyr_virusscan.c:197:21: note: each undeclared identifier is reported only 
once for each function it appears in
|gcc -DHAVE_CONFIG_H -I.   -I. -I./lib -I. -I./lib 
-DLIBEXEC_DIR=\"/usr/lib/cyrus/bin\" -DSBIN_DIR=\"/usr/lib/cyrus/bin\" 
-DSYSCONF_DIR=\"/etc\" -DHAVE_CONFIG_H  -I/usr/include/libxml2   
-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include -fPIC  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wextra -g -fno-strict-aliasing -pipe -O2 -c -o 
imap/reconstruct.o imap/reconstruct.c
|make[4]: *** [Makefile:4817: imap/cyr_virusscan.o] Error 1

Here [0] is an example what I did for havp. Please let me know if 
[ ] you are going to port it yourself
[ ] you ask (quick) upstream to do so
[ ] you are going to drop the support for clamav 
[ ] you want me to port it

If you have the option to use clamav's socket instead the library
interface then this is probably the better option.

[0] 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=920865;filename=havp-Update-to-clamav-0.101.patch;msg=5

Sebastian

Bug#913119: Bug#913138: Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

[Cesare Leonardi]

On 28/02/19 16:44, Thorsten Glaser wrote:

please do consider uploading 4.19.24 to buster/sid with some haste.
We have headless virtualisation hosts being unreachable/frozen now,
and while these are “only” development systems, this is untenable.


Like you I'm looking forward for that kernel.
But, in the meantime, doesn't the workaround of disabling blk_mq work 
for you? See comment #15 and #20.

I used it for months without any problem.

Cesare.

Bug#923427: mergechanges: Regression: --indep/source breaks multi-line Binary fields

[Simon McVittie]

On Thu, 28 Feb 2019 at 21:28:47 +0100, Mattia Rizzolo wrote:
> There shouldn't be debs in Files but not in Binaries.   Which packages are
> missing there?

The test that I added using Salvatore's .changes file says the -dbgsym
packages aren't listed in Binary:

Warning: hyperv-daemons-dbgsym not found in Binary field
52a99bb89b091d9f88008b9b78bb 41354 debug extra 
hyperv-daemons-dbgsym_4.9.161-1_amd64.deb
Warning: libcpupower1-dbgsym not found in Binary field
dcf307126f4a0eebe135f8f20aea9d94 20096 debug extra 
libcpupower1-dbgsym_4.9.161-1_amd64.deb
Warning: linux-cpupower-dbgsym not found in Binary field
28344bc7bcfa99bb67112ad8eab7d7b5 54550 debug extra 
linux-cpupower-dbgsym_4.9.161-1_amd64.deb
Warning: linux-kbuild-4.9-dbgsym not found in Binary field
ad6e009533db6131f7861b5eb881254e 488164 debug extra 
linux-kbuild-4.9-dbgsym_4.9.161-1_amd64.deb
Warning: linux-perf-4.9-dbgsym not found in Binary field
93c6711fb982bad7df8a62ab1292ea87 4484002 debug extra 
linux-perf-4.9-dbgsym_4.9.161-1_amd64.deb
Warning: usbip-dbgsym not found in Binary field
1b59f042a4a6780b0e76319950737bfe 92978 debug extra 
usbip-dbgsym_2.0+4.9.161-1_amd64.deb

(repeated twice; the lines ending with .deb are quoting from Files)

This seems like it might be a quirk of stretch's toolchain: if you look at
https://buildd.debian.org/status/fetch.php?pkg=dpkg=amd64=1.18.25=1530308035=0
you'll see that dpkg-dbgsym and dselect-dbgsym aren't in Binary or
Description either, whereas in
https://buildd.debian.org/status/fetch.php?pkg=dpkg=amd64=1.19.5=1550947218=0
they are in Binary but not Description.

smcv

Bug#923346: updates

[Tino Mettler]

> Am 27.02.2019 um 22:31 schrieb Paul Thomas :
> 
> OK, a couple of updates.
> 
> First, I tracked down line ptp4l call that starts this off, it's the
> ioctl(fd, SIOCSHWTSTAMP, ); line 88 in sk.c. I can see if a
> standalone program that just does that ioctl has the same affect.
> 
> Second, I was able to reproduce this using the mainline 5.0-rc8 kernel.

Hi,

so this looks like a broken driver or buggy hardware and not like an issue with 
ptp4l, as this ioctl() is a standard call to enable hardware timestamping. 
Thanks for the analysis. You may get further help on the linuxptp user mailing 
list.

Regards,
Tino

Bug#920269: marked as done (groff: gropdf can execute arbitrary commands)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 21:03:39 +
with message-id 
and subject line Bug#920269: fixed in groff 1.22.4-3
has caused the Debian Bug report #920269,
regarding groff: gropdf can execute arbitrary commands
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.)


-- 
920269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: groff
Version: 1.22.4-2
Severity: grave
Tags: security
Justification: user security hole

According to the gropdf(1) man page:

   gropdf [-dels] [-F dir] [-I dir] [-p paper-size] [-u [cmapfile]]
  [-y foundry] [file ...]

but providing a "filename" with a pipe character can yield an
arbitrary command execution:

$ touch foo
$ ls foo
foo
$ gropdf "rm foo|"
$ ls foo
ls: cannot access 'foo': No such file or directory
$ 

The reason is that gropdf is a Perl script that uses the insecure
null filehandle "<>". The perlop(1) man page says:

  Since the null filehandle uses the two argument form of "open" in
  perlfunc it interprets special characters, so if you have a script like
  this:

  while (<>) {
  print;
  }

  and call it with "perl dangerous.pl 'rm -rfv *|'", it actually opens a
  pipe, executes the "rm" command and reads "rm"'s output from that pipe.

BTW, I fear that's not the only Perl script that is affected by such
a bug.

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

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

Versions of packages groff depends on:
ii  groff-base  1.22.4-2
ii  libc6   2.28-5
ii  libgcc1 1:8.2.0-14
ii  libice6 2:1.0.9-2
ii  libsm6  2:1.2.2-1+b3
ii  libstdc++6  8.2.0-14
ii  libx11-62:1.6.7-1
ii  libxaw7 2:1.0.13-1+b2
ii  libxmu6 2:1.1.2-2
ii  libxt6  1:1.1.5-1

Versions of packages groff recommends:
ii  ghostscript  9.26~dfsg-0+deb9u2
ii  imagemagick  8:6.9.10.23+dfsg-2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2
ii  libpaper11.1.26
ii  netpbm   2:10.0-15.3+b2
ii  perl 5.28.1-3
ii  psutils  1.17.dfsg-4

groff suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: groff
Source-Version: 1.22.4-3

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated groff 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, 28 Feb 2019 19:44:28 +
Source: groff
Architecture: source
Version: 1.22.4-3
Distribution: unstable
Urgency: medium
Maintainer: Colin Watson 
Changed-By: Colin Watson 
Closes: 920269
Changes:
 groff (1.22.4-3) unstable; urgency=medium
 .
   * Avoid Perl's unsafe "<>" operator (closes: #920269).
Checksums-Sha1:
 4632d67383a2b5ed33d4c88ad6bd62f77f4ccd56 2328 groff_1.22.4-3.dsc
 f44f811bbe2cdcdafbf90a2ee62bbd18e5780020 47460 groff_1.22.4-3.debian.tar.xz
 59b3e76ae473db6e060650a2937ebed31f92a2ff 9125 groff_1.22.4-3_source.buildinfo
Checksums-Sha256:
 c7bf77d7fa6c19c0305dffab17d1904aba37f274e0d457d063264ed821096ba5 2328 
groff_1.22.4-3.dsc
 a8cfa698773de64cba8e07c927016bfef56af8bfa45476321c99eec75001e25d 47460 
groff_1.22.4-3.debian.tar.xz
 e53eb52f11d49529c7631f836cae055097fba927d7f20fbd5f3b9fce5c3dfcd6 9125 
groff_1.22.4-3_source.buildinfo
Files:
 35908d6c5325435eebd60255ae9cecbf 2328 text important groff_1.22.4-3.dsc
 557ded429d5035a58f1a7245f744f4a7 47460 text important 
groff_1.22.4-3.debian.tar.xz
 3f8467291c8125528db462e7d53c5551 9125 text important 

Bug#923442: octave: FTBFS (/bin/sed: can't read libinterp/parse-tree/oct-parse.cc-t: No such file or directory)

[Mike Miller]

On Thu, Feb 28, 2019 at 20:10:46 +0100, Sébastien Villemot wrote:
> If you don't have the time to do the upload today, I will do it
> tomorrow.
> 
> Note that you'll have to create a new git branch, named "buster",
> branching off at 4.4.1-4, since master already contains 5.1.0.

I've done exactly that, successfully tested in sbuild locally. Please
tag and upload when you get a chance.

-- 
mike


signature.asc
Description: PGP signature

Processed: Bug #923442 in octave marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #923442 [src:octave] octave: FTBFS (/bin/sed: can't read 
libinterp/parse-tree/oct-parse.cc-t: No such file or directory)
Added tag(s) pending.

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

Bug#923442: Bug #923442 in octave marked as pending

[Mike Miller]

Control: tag -1 pending

Hello,

Bug #923442 in octave 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/pkg-octave-team/octave/commit/98dfb470ffc04d27238b8d9cc4a5f76e8ec5e6a9


bison-3.3.patch: new patch from upstream, fixes FTBFS with bison 3.3

Closes: #923442


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/923442

Bug#919344: marked as done (adequate reports obsolete-conffile in openssh-client)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 19:54:59 +
with message-id 
and subject line Bug#919344: fixed in openssh 1:7.9p1-8
has caused the Debian Bug report #919344,
regarding adequate reports obsolete-conffile in openssh-client
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.)


-- 
919344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-client
Version: 1:7.9p1-5
Severity: normal

Usertags: obsolete-conffile adequate

Dear Maintainer,

Thank you for maintaining openssh. So much of our modern world depends on it.

While updating today, adequate informs me about this -

$ adequate openssh-client
openssh-client: obsolete-conffile /etc/ssh/moduli

Please look into this and fix the offending file.

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

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

Versions of packages openssh-client depends on:
ii  adduser   3.118
ii  dpkg  1.19.2
ii  libc6 2.28-5
ii  libedit2  3.1-20181209-1
ii  libgssapi-krb5-2  1.16.2-1
ii  libselinux1   2.8-1+b1
ii  libssl1.1 1.1.1a-1
ii  passwd1:4.5-1.1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages openssh-client recommends:
ii  xauth  1:1.0.10-1

Versions of packages openssh-client suggests:
pn  keychain
pn  libpam-ssh  
ii  lxqt-openssh-askpass [ssh-askpass]  0.13.0-1
pn  monkeysphere

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Source: openssh
Source-Version: 1:7.9p1-8

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated openssh 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, 28 Feb 2019 19:31:49 +
Source: openssh
Architecture: source
Version: 1:7.9p1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSSH Maintainers 
Changed-By: Colin Watson 
Closes: 919344 923419
Changes:
 openssh (1:7.9p1-8) unstable; urgency=medium
 .
   [ Colin Watson ]
   * Apply upstream patch to fix bug in HostbasedAcceptedKeyTypes and
 PubkeyAcceptedKeyTypes options in the case where only RSA-SHA2 signature
 types were specified.
   * Apply upstream patch to request RSA-SHA2 signatures for
 rsa-sha2-{256|512}-cert-...@openssh.com cert algorithms (closes:
 #923419).
   * Move moduli(5) manual page to openssh-server to go with /etc/ssh/moduli;
 forgotten in 1:7.9p1-5.
 .
   [ Dominik George ]
   * Correctly handle conffile move to openssh-server (closes: #919344).
Checksums-Sha1:
 d3c06fe0d47cbe55936cd7984063a8b1a337bb30 3161 openssh_7.9p1-8.dsc
 54deaf853694431e2e0da1c36bea89736c17d4c6 170100 openssh_7.9p1-8.debian.tar.xz
 dc7ed276ed7c6bb8243f9fc81c33a209b874d3ab 15011 openssh_7.9p1-8_source.buildinfo
Checksums-Sha256:
 e731d762698b16dc8590f005780b06145be52f993424a3e476e0d62f9c4abff1 3161 
openssh_7.9p1-8.dsc
 4a8ef7f13ac2940c526004c3b1a661728652935ec40fd68b2f605b394228991c 170100 
openssh_7.9p1-8.debian.tar.xz
 0fe317298e56c45d960acc3e68a040b1cc4380bd49bbef1e75a1159b50cd3600 15011 
openssh_7.9p1-8_source.buildinfo
Files:
 3fd783e04394ae4954aa111c5e9ebefc 3161 net standard openssh_7.9p1-8.dsc
 15749ab9ef096fc0209c33957ea34246 170100 net standard 
openssh_7.9p1-8.debian.tar.xz
 

Processed: Re: Bug#923427: mergechanges: Regression: --indep/source breaks multi-line Binary fields

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 mergechanges: Regression: --indep/source breaks multi-line Binary 
> fields
Bug #923427 [devscripts] mergechanges: Regression: --indep/source 
mangles/breaks (valid?) Binary fields
Changed Bug title to 'mergechanges: Regression: --indep/source breaks 
multi-line Binary fields' from 'mergechanges: Regression: --indep/source 
mangles/breaks (valid?) Binary fields'.
> forwarded -1 https://salsa.debian.org/debian/devscripts/merge_requests/112
Bug #923427 [devscripts] mergechanges: Regression: --indep/source breaks 
multi-line Binary fields
Set Bug forwarded-to-address to 
'https://salsa.debian.org/debian/devscripts/merge_requests/112'.
> tags -1 + patch
Bug #923427 [devscripts] mergechanges: Regression: --indep/source breaks 
multi-line Binary fields
Added tag(s) patch.

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

Bug#923427: mergechanges: Regression: --indep/source breaks multi-line Binary fields

[Simon McVittie]

Control: retitle -1 mergechanges: Regression: --indep/source breaks multi-line 
Binary fields
Control: forwarded -1 
https://salsa.debian.org/debian/devscripts/merge_requests/112
Control: tags -1 + patch

On Thu, 28 Feb 2019 at 17:59:25 +, Simon McVittie wrote:
> I'll try to put together some sort of parsing fix in shell for buster

Try this:
https://salsa.debian.org/debian/devscripts/merge_requests/112

I've added Salvatore's changes file unmodified as a test-case, since it
has a couple of interesting corner cases for the parser.

To make mergechanges accept that changes file, I also had to make it more
tolerant of packages that are in Files but not Binary, which apparently
happens in stretch kernels? (Again, I didn't know this was even possible.)

Regards,
smcv

Bug#923481: alpine: replies lose In-Reply-To and References headers

[Thorsten Glaser]

Package: alpine
Version: 2.21+dfsg1-1.1
Severity: serious

If I take a message, reply to it, then go to the Subject line,
press ^K to remove the existing (possibly damaged) text and type
new text (possibly to change the subthread subject), the eMail
gets sent out AND Fcc’d without both In-Reply-To and References
headers, completely and utterly breaking threading.

This is a major regression relative to pine 4.64 which does emit
these headers in that exact case (as just checked by me).

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

Kernel: Linux 4.19.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages alpine depends on:
ii  libc6 2.28-7
ii  libgssapi-krb5-2  1.17-2
ii  libkrb5-3 1.17-2
ii  libldap-2.4-2 2.4.47+dfsg-3
ii  libpam0g  1.3.1-5
ii  libssl1.1 1.1.1b-1
ii  libtinfo6 6.1+20181013-2
ii  mlock 8:2007f~dfsg-6

Versions of packages alpine recommends:
pn  alpine-doc  

Versions of packages alpine suggests:
ii  aspell  0.60.7~20110707-6
ii  postfix [mail-transport-agent]  3.3.2-4

-- no debconf information

Bug#920269: Bug #920269 in groff marked as pending

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #920269 in groff 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/debian/groff/commit/8239da115b70c9194033c30aa4dfa83a74ac38c4


Avoid Perl's unsafe "<>" operator

Closes: #920269


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/920269

Processed: Bug #920269 in groff marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #920269 [groff] groff: gropdf can execute arbitrary commands
Added tag(s) pending.

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

Bug#921131: taking over yum-utils

[Holger Levsen]

Hi Markus!

On Thu, Feb 28, 2019 at 08:27:11PM +0100, Markus Frosch wrote:
> thanks I just did so, and uploaded a new version.

yay, very cool!

> During testing I noticed the "refactoring" patch actually broke logging,
> and therefor reposync working.

ouch, sorry.

> I fixed it with an additional patch:
> https://salsa.debian.org/pkg-rpm-team/yum-utils/commit/0c946a3b072b921a96d1b47a9653367db74d5cf0

thanks!

> Upstream has applied more refactoring, I will rebase our patches at a
> later point, for now it should work.

*nods*


-- 
tschau,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#921131: taking over yum-utils

[Markus Frosch]

Am 22.02.19 um 10:26 schrieb Holger Levsen:
> please adopt yum-utils and get the changes from experiemental into
> sid/buster before the freeze is fully in effect. You still have almost a
> week to do that! ;)
> 
> Also if you do that, please dont forget to include the changes from my
> NMU.
> 
> If you need any help or advice, please shout!

Hey Holger,
thanks I just did so, and uploaded a new version.

During testing I noticed the "refactoring" patch actually broke logging,
and therefor reposync working.

I fixed it with an additional patch:
https://salsa.debian.org/pkg-rpm-team/yum-utils/commit/0c946a3b072b921a96d1b47a9653367db74d5cf0

Upstream has applied more refactoring, I will rebase our patches at a
later point, for now it should work.

Cheers
Markus Frosch
-- 
mar...@lazyfrosch.de / lazyfro...@debian.org
https://lazyfrosch.de



signature.asc
Description: OpenPGP digital signature

Bug#923454: renderdoc: FTBFS (error: braces around scalar initializer for type 'int')

[Andrey Rahmatullin]

The problem here is the API compatibility break in glslang, described in
https://github.com/KhronosGroup/glslang/issues/1538#issuecomment-431643795
Changes related to the new glslang version seem to be bundled in
https://github.com/baldurk/renderdoc/commit/2ea6174c83c3c55f504c107303991d9bb2aa9af3
(I see 3 source files changed there).

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#923442: octave: FTBFS (/bin/sed: can't read libinterp/parse-tree/oct-parse.cc-t: No such file or directory)

[Sébastien Villemot]

Le jeudi 28 février 2019 à 09:53 -0800, Mike Miller a écrit :
> Control: tags -1 + patch
> 
> On Thu, Feb 28, 2019 at 10:08:33 +, Santiago Vila wrote:
> > I tried to build this package in buster but it failed:
> 
> […]
> > /bin/sed: can't read libinterp/corefcn/oct-tex-parser.cc-t: No such
> > file or directory
> 
> Confirmed separately in upstream Octave development, this is caused
> by
> the recent upload of bison 3.3 to unstable/buster.
> 
> Octave 4.4 needs this patch to work with bison 3.3
> 
>   https://hg.savannah.gnu.org/hgweb/octave/rev/df42ea23502f
> 
> I'll try building that a bit later today and push the fix if it works
> for me.

Thanks for pointing to the relevant upstream commit.

If you don't have the time to do the upload today, I will do it
tomorrow.

Note that you'll have to create a new git branch, named "buster",
branching off at 4.4.1-4, since master already contains 5.1.0.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


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

Bug#919344: Bug #919344 in openssh marked as pending

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #919344 in openssh 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/ssh-team/openssh/commit/3115064e04541741d558cbb7b8ecab49ea1c0af9


Correctly handle conffile move to openssh-server

Closes: #919344


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919344

Processed: Bug #919344 in openssh marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919344 [openssh-client] adequate reports obsolete-conffile in 
openssh-client
Added tag(s) pending.

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

Bug#919344: adequate reports obsolete-conffile in openssh-client

[Colin Watson]

On Tue, Feb 26, 2019 at 11:57:00PM +0100, Dominik George wrote:
> How about the attached approach?
> 
> It uses dpkg-maintscript-helper in openssh-client to remove the
> conffile. dpkg-maintscript=helper does all the magic to determine
> whether the file was changed by the user. Here, we use the fact that in
> preinst, it only moves the file to a backup location, and this location
> is different when the file is user-modified.
> 
> In postinst of openssh-server, we then check for the backup file and
> move it back in place if it exists. This…
> 
>  …fixes the obsolete conffile,
>  …avoids an annoying question on upgrade whether to overwrite the file,
>   is it was user-modified,
>  …still keeps user modifications intact.
> 
> I tested the following:
[...]

Ah, clever.  Thanks!  I also tested this, including upgrades through
intermediate versions, and it works correctly in every scenario I can
come up with.

Normally the openssh-server postinst code in fact does nothing because
apt currently seems to unpack the new openssh-server before the new
openssh-client and so by the time dpkg-maintscript-helper runs from
openssh-client.preinst the file has already been taken over by
openssh-server; but even if I perform the unpack and configure
operations manually using dpkg such that openssh-client.preinst runs
before the new openssh-server is unpacked, your code still works.

I fleshed out the comment a bit, and committed this in your name.  I'll
upload it soon along with other pending changes.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#923223: marked as done (XML::Parser::parsefile() uses 2-argument open)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 19:06:59 +
with message-id 
and subject line Bug#923223: fixed in libxml-parser-perl 2.44-4
has caused the Debian Bug report #923223,
regarding XML::Parser::parsefile() uses 2-argument open
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.)


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

Package: libxml-parser-perl
Version: 2.44-2+b4
Tags: security
Control: affects -1 check-all-the-things duck

The XML::Parser::parsefile function uses 2-argument open().
As a consequence, users of this function can't use it to securely check 
files with untrusted names. (Unless the users sanitize the filenames 
themselves, which they don't, because AFAICT this behavior is not 
documented.)


Proof of concept:

  $ touch '; false .appdata; cowsay pwned >&2; kill $PPID |'
  $ duck
  sh: 1: ./: Permission denied
   ___
  < pwned >
   ---
  \   ^__^
   \  (oo)\___
  (__)\   )\/\
  ||w |
  || ||
  Terminated


-- System Information:
Architecture: i386

Versions of packages libxml-parser-perl depends on:
ii  perl5.28.1-4
ii  libc6   2.28-7
ii  libexpat1   2.2.6-1
ii  liburi-perl 1.76-1
ii  libwww-perl 6.36-1

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: libxml-parser-perl
Source-Version: 2.44-4

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

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

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated libxml-parser-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 Feb 2019 19:39:53 +0100
Source: libxml-parser-perl
Architecture: source
Version: 2.44-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Xavier Guimard 
Closes: 923223
Changes:
 libxml-parser-perl (2.44-4) unstable; urgency=medium
 .
   * Team upload
   * Update patch (Closes: #923223)
Checksums-Sha1: 
 d37bbec34614b04ed20a992b9dfa56ecdda713f0 2109 libxml-parser-perl_2.44-4.dsc
 dd45114475bc0b3630a1cdc5bd1c5f77df89ca06 58064 
libxml-parser-perl_2.44-4.debian.tar.xz
Checksums-Sha256: 
 b9f31511032348e2bc499158c706eaf814e56598b9c308f04f5a557b184ab45e 2109 
libxml-parser-perl_2.44-4.dsc
 40e8a914ba7052c582a28f1e73205b568d8fe5f0888b343d23e377cf855130c3 58064 
libxml-parser-perl_2.44-4.debian.tar.xz
Files: 
 74a223e5edef68ffdfdaa22c9fcd40f3 2109 perl optional 
libxml-parser-perl_2.44-4.dsc
 aa2fb6f6ea3a8849b6d8c47962f3d89e 58064 perl optional 
libxml-parser-perl_2.44-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlx4K7AACgkQ9tdMp8mZ
7umJNA//QiWQ8+xSnndWhEM3uZEVS1DLYjRLLvvHa1fTTGgPh8pGMZA3f4PJSCo5
kj2HM/apfuxLd7BSyOEHX4q/zrJs1R4OxG0C8XxLcduwq0MxkywGFaIuj7YZlVs7
9s/xy0EaeIS/9NiuIohFljDGkZPgu8cPlHaA2S6WiiAc0fEE4/wReo3t09LNyHzh
dE6tBAXtx+aai6YRF02cvD6jbUEbJRZdNHC1EcMnILj5Tih/nbz9pQr6Ctdonarl
1/FghYVMu5+BROqtlf3PJItbOr3Ik5GDsug4l54y0qTgYEMQwIF0LRzFyvv13BJI
lFawKJ/Fp7r4a9Rzy/kZVlilBYmmCPRQOxBe6/duPw7p9bB48mQUJWL05npvyzNH
NZtLjn0++GK+9pdtc7I3Tk3sP83SZAEumYdjdip84Vg6JA7YtZc49daUtKqokegL
6g895eOolanV9WV/j9zytSa1Rs+lMxb2rm4uyqdWaEwKZnnO2mobgSRi6PTJ+JzY
7PTzlKVX1pbDN8SXx4r1MTRIcIVbwZ7QKPt+lkx/F+ldSguoRtYCsGuj513TB4Yc
58O/NOzWCsTZz9HgOwyZtK0E/Fc5tIQ4e6q4KXycRfBQRkKBd3+RdSy5iOF86gxI
bdVzPOwDEkzeHEXSkRzW1joMXoIVpaqXBtqMN/dIr9HBN/qZOOE=
=vKkz
-END PGP SIGNATURE End Message ---

Bug#923466: lammps: FTBFS (dh_auto_configure fails)

[Andrey Rahmatullin]

The actual error message is
"""
CMake Error at CMakeLists.txt:298 (message):
  MPIIO package needs LAMMPS to be build with MPI
Call Stack (most recent call first):
  CMakeLists.txt:304 (pkg_depends)
"""

It seems to mean MPI is not found. After removing QUIET from
find_package(MPI):

-- Found MPI_C: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so (found version 
"3.1")
-- Found MPI_CXX: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so (found 
version "3.1")
-- Could NOT find MPI_Fortran (missing: MPI_Fortran_WORKS)
-- Could NOT find MPI (missing: MPI_Fortran_FOUND) (found version "3.1")
CMake Error at CMakeLists.txt:298 (message):
  MPIIO package needs LAMMPS to be build with MPI
Call Stack (most recent call first):
  CMakeLists.txt:304 (pkg_depends)

The package B-D on fortran-compiler. The package is virtual, and we see
here why is that considered a problem to B-D on a virtual package.
Previously gfortran was installed during the build, now flang07 is
installed. Yet mpif90 says "The Open MPI wrapper compiler was unable to
find the specified compiler gfortran in your PATH." Install gfortran fixes
this problem.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Processed: tagging 903698

[Debian Bug Tracking System]

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

> tags 903698 + buster-ignore
Bug #903698 [dh-python] sphinxbase: build appears broken for multiple python3 
versions
Added tag(s) buster-ignore.
> thanks
Stopping processing here.

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

Processed: Re: ftgl: FTBFS in sid (LaTeX error)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #923365 [src:ftgl] ftgl: FTBFS in sid (LaTeX error)
Added tag(s) moreinfo.

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

Bug#923365: ftgl: FTBFS in sid (LaTeX error)

[Manuel A. Fernandez Montecelo]

Control: tags -1 + moreinfo


Hi Santiago!

2019-02-26 23:28 Santiago Vila:

Package: src:ftgl
Version: 2.4.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:

(Yes, I know that it built ok 4 hours ago, but apparently not anymore)


[...]
debian/rules binary-arch
dh binary-arch
  dh_update_autotools_config -a
  dh_autoreconf -a
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '.auto'.
libtoolize: copying file '.auto/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:31: installing '.auto/compile'
configure.ac:12: installing '.auto/config.guess'

[... snipped ...]

! Missing \cr inserted.

   \cr
l.40 \end{DoxyEnumFields}

I'm guessing that you meant to end an alignment here.

! Misplaced \cr.
 \cr

l.40 \end{DoxyEnumFields}

I can't figure out why you would want to use a tab mark
or \cr or \span just now. If something like a right brace
up above has ended a previous alignment prematurely,
you're probably due for more error messages, and you
might try typing `S' now just to see what is salvageable.

! Missing \cr inserted.

   \cr
l.40 \end{DoxyEnumFields}

(That makes 100 errors; please try again.)
Here is how much of TeX's memory you used:
15019 strings out of 494561
215980 string characters out of 6177454
308954 words of memory out of 500
18251 multiletter control sequences out of 15000+60
61038 words of font info for 84 fonts, out of 800 for 9000
14 hyphenation exceptions out of 8191
53i,16n,92p,802b,557s stack positions out of 5000i,500n,1p,20b,8s

!  ==> Fatal error occurred, no output PDF file produced!
make[4]: *** [Makefile:619: stamp-latex] Error 1
make[4]: Leaving directory '/<>/docs'
make[3]: *** [Makefile:519: all-recursive] Error 1
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:428: all] Error 2
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 "GLUT_LIBS=-lglut -lGLU -lGL -lm" returned exit code 2
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -B"
and it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.


This was due to bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921779 , as mentioned
in the changelog.

Since I saw it marked as closed, I enabled the PDF doc again and it
worked, despite the bug in the documentation generator not having
actually been fixed at the time.

I don't know why it worked, if due to older versions than the ones
affected being used, or something else.  The texlive maintainer mentions
"clean up the mess due to delayed acceptance" and closing it for a
second time yesterday, so I don't know what really happened.

Also, the network of mirrors had problems and haven't been updated for a
couple of days, including some buildds, so it's possible that this might
have played a role?

In any case, it built for me at the time of uploading, it built in
almost all buildds except unimportant ones, and I just tested and it
builds for me again locally with git-pbuilder and an up-to-date chrrot,
so I think that everything is fine now?

Thanks for caring!

--
Manuel A. Fernandez Montecelo 

Bug#922960: marked as done (new libcapstone-dev pkg-config does not provide include path, breaks compatibility)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 18:19:38 +
with message-id 
and subject line Bug#922960: fixed in capstone 4.0.1+really+3.0.5-1
has caused the Debian Bug report #922960,
regarding new libcapstone-dev pkg-config does not provide include path, breaks 
compatibility
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.)


-- 
922960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcapstone-dev
Version: 4.0.1-3
Severity: normal

pkg-config file for libcapstone in verion 4 does not list
-I/usr/include/capstone in -cflags anymore, so that with
proper invocation of pkg-config "old" applications does
not find  anymore. This can be an easy fix,
so that compatibility is retained.

In particular this prevents qemu build now.

Thanks,

/mjt
--- End Message ---
--- Begin Message ---
Source: capstone
Source-Version: 4.0.1+really+3.0.5-1

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated capstone package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 26 Feb 2019 22:35:27 +0100
Source: capstone
Binary: capstone-tool capstone-tool-dbgsym libcapstone-dev libcapstone3 
libcapstone3-dbgsym python-capstone python3-capstone
Architecture: source amd64
Version: 4.0.1+really+3.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Hilko Bengen 
Description:
 capstone-tool - lightweight multi-architecture disassembly framework - command 
li
 libcapstone-dev - lightweight multi-architecture disassembly framework - devel 
file
 libcapstone3 - lightweight multi-architecture disassembly framework - library
 python-capstone - lightweight multi-architecture disassembly framework - 
Python bin
 python3-capstone - lightweight multi-architecture disassembly framework - 
Python bin
Closes: 922846 922960
Changes:
 capstone (4.0.1+really+3.0.5-1) unstable; urgency=medium
 .
   * Team upload
   * Revert repository to 3.0.5-4 to fix botched upload (Closes: #922960,
 #922846)
Checksums-Sha1:
 af519480b961ecce162d09ba022b91ab4f78b8b7 2373 capstone_4.0.1+really+3.0.5-1.dsc
 b873a05a99a080e7efab34e299d348f5a4cf7117 2886717 
capstone_4.0.1+really+3.0.5.orig.tar.gz
 9e332e968475835de68e2fa20172c857a2bc6e66 6824 
capstone_4.0.1+really+3.0.5-1.debian.tar.xz
 d2785f4b4480ce8d03203aac74d0a42824bacfaf 25776 
capstone-tool-dbgsym_4.0.1+really+3.0.5-1_amd64.deb
 7157a173eb93787f62bac87d03ca4ce37eb28eb8 20044 
capstone-tool_4.0.1+really+3.0.5-1_amd64.deb
 b0327c56a1f4b9b75bce7700ae8802d109e38a79 8780 
capstone_4.0.1+really+3.0.5-1_amd64.buildinfo
 9bbf9ec6b0c8ef653715e01e0514a17a626f4bf8 494996 
libcapstone-dev_4.0.1+really+3.0.5-1_amd64.deb
 8dd8c6a9b724c4de94d993c2facec9104545725c 1425292 
libcapstone3-dbgsym_4.0.1+really+3.0.5-1_amd64.deb
 468cf96d1fe706cd2f7abc3dfbe9e05cab243f84 443540 
libcapstone3_4.0.1+really+3.0.5-1_amd64.deb
 cf64dcdb0ca2fd04f8d45d8617e53fb393c7f650 67152 
python-capstone_4.0.1+really+3.0.5-1_amd64.deb
 9f59a509c7e3b2def4bfd4a553986b0382037c5d 67212 
python3-capstone_4.0.1+really+3.0.5-1_amd64.deb
Checksums-Sha256:
 7b8c18c6501f581bec82ec998755643e570b3e848b2e17981ddd37fffcdef576 2373 
capstone_4.0.1+really+3.0.5-1.dsc
 913dd695e7c5a2b972a6f427cb31f2e93677ec1c38f39dda37d18a91c70b6df1 2886717 
capstone_4.0.1+really+3.0.5.orig.tar.gz
 63f26509e1dae86ff4316f137804790a94ca77d02259c87065559b0beba826cc 6824 
capstone_4.0.1+really+3.0.5-1.debian.tar.xz
 bc2c7bc5e41b2eecf1e1db00703f085279fff6558fd34a2328d66791a30908b9 25776 
capstone-tool-dbgsym_4.0.1+really+3.0.5-1_amd64.deb
 1e68639c0247d463af12da1ad26c1f8cfab93d4de889e2a14fe19707aa06fbfc 20044 
capstone-tool_4.0.1+really+3.0.5-1_amd64.deb
 c6aa6e83f3b6dcda8dadebb996901a59b087aac0bc4fb4ddbe89e88986484f52 8780 
capstone_4.0.1+really+3.0.5-1_amd64.buildinfo
 00814f7dc7657f45f72a93f2af6ee7388f425b552bddce3bff7e1fe386c6ba06 494996 
libcapstone-dev_4.0.1+really+3.0.5-1_amd64.deb
 

Bug#923427: mergechanges: Regression: --indep/source mangles/breaks (valid?) Binary fields

[Mattia Rizzolo]

On Thu, Feb 28, 2019 at 05:59:25PM +, Simon McVittie wrote:
> For now, is it OK to make mergechanges use a perl one-liner involving
> Dpkg::Control to do the heavy lifting?

yes

> For the future, do the devscripts maintainers have a preference for the
> implementation language of a post-buster rewrite of mergechanges in a
> language with real parsers?

I don't think there is a preference between perl and python.  I guess
that at this point, there is a bunch of perl foo within devscripts that
you can lift, whereas there is a little less python, so right now it's
whatever you prefer.

(also, I myself can deal with python much easier than perl, but there
are enough people understanding both)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#923223: XML::Parser::parsefile() uses 2-argument open

[Niko Tyni]

On Thu, Feb 28, 2019 at 11:50:04AM +0100, Xavier wrote:

> Patch is ready in salsa repo:
> 
> if (ref $file or $file eq '-') {
>   open(FILE, $file) or  croak "Couldn't open $file:\n$!";
> } else {
>   open(FILE, '<', $file) or  croak "Couldn't open $file:\n$!";
> }
> 
> Successfully tested with xmltv. I propose to push as this for now to
> close bug before freeze. This patch fixes security bug since strange
> filename are no more interpreted and autopkgtest regression is fixed.

What kind of references did you encounter that made it necessary to
fall back to 2-arg open on all references? They might still stringify
to nasty things.

% perl -e 'package Foo; use overload q{""} => sub { return ${$_[0]} }; 1; 
package main; my $s = "> /etc/passwd"; my $foo = bless \$s, "Foo"; print 
qq(value: "$foo" ref:) . ref($foo) . "\n"; open(my $fh, $foo) or die $!'
  
value: "> /etc/passwd" ref:Foo
Permission denied at -e line 1.

That said, this does seem quite far fetched. I expect the patch fixes
all the command line injection issues caused by the 2-arg open just fine
and doesn't make things any worse in these more obscure scenarios.
-- 
Niko Tyni   nt...@debian.org

Bug#923427: mergechanges: Regression: --indep/source mangles/breaks (valid?) Binary fields

[Simon McVittie]

On Thu, 28 Feb 2019 at 17:03:44 +0100, Mattia Rizzolo wrote:
> If I see this correctly, it's all because the code reads only the first
> line of the Binary field, without considering it may be a multiline
> field (and tbh I didn't even realized it could be…)

I must admit I hadn't realised there was any middle ground in changes
files between "multi-line is mandatory" (like Files) and "multi-line
is forbidden".

I'll try to put together some sort of parsing fix in shell for buster,
but I think this is a sign that mergechanges being a shell script
isn't actually very sustainable, and it should be in a language with
a more formal parser, probably Perl (using Dpkg::Control) or Python
(using debian.deb822).

For now, is it OK to make mergechanges use a perl one-liner involving
Dpkg::Control to do the heavy lifting? It seems that it already requires
perl, and libdpkg-perl is indirectly a hard dependency for devscripts.

For the future, do the devscripts maintainers have a preference for the
implementation language of a post-buster rewrite of mergechanges in a
language with real parsers?

smcv

Bug#923442: octave: FTBFS (/bin/sed: can't read libinterp/parse-tree/oct-parse.cc-t: No such file or directory)

[Mike Miller]

Control: tags -1 + patch

On Thu, Feb 28, 2019 at 10:08:33 +, Santiago Vila wrote:
> I tried to build this package in buster but it failed:
[…]
> /bin/sed: can't read libinterp/corefcn/oct-tex-parser.cc-t: No such file or 
> directory

Confirmed separately in upstream Octave development, this is caused by
the recent upload of bison 3.3 to unstable/buster.

Octave 4.4 needs this patch to work with bison 3.3

  https://hg.savannah.gnu.org/hgweb/octave/rev/df42ea23502f

I'll try building that a bit later today and push the fix if it works
for me.

-- 
mike


signature.asc
Description: PGP signature

Processed: Re: Bug#923442: octave: FTBFS (/bin/sed: can't read libinterp/parse-tree/oct-parse.cc-t: No such file or directory)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #923442 [src:octave] octave: FTBFS (/bin/sed: can't read 
libinterp/parse-tree/oct-parse.cc-t: No such file or directory)
Added tag(s) patch.

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

Processed: retitle 923467 to libvigraimpex: FTBFS (Could not import extension sphinx.ext.pngmath)

[Debian Bug Tracking System]

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

> retitle 923467 libvigraimpex: FTBFS (Could not import extension 
> sphinx.ext.pngmath)
Bug #923467 [src:libvigraimpex] libvigraimpex: FTBFS (Could not import 
extension sphinx.ext.pngmathCould not import extension sphinx.ext.pngmath)
Changed Bug title to 'libvigraimpex: FTBFS (Could not import extension 
sphinx.ext.pngmath)' from 'libvigraimpex: FTBFS (Could not import extension 
sphinx.ext.pngmathCould not import extension sphinx.ext.pngmath)'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#923467: libvigraimpex: FTBFS (Could not import extension sphinx.ext.pngmathCould not import extension sphinx.ext.pngmath)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/ukoethe/vigra/issues/462
Bug #923467 [src:libvigraimpex] libvigraimpex: FTBFS (Could not import 
extension sphinx.ext.pngmathCould not import extension sphinx.ext.pngmath)
Set Bug forwarded-to-address to 'https://github.com/ukoethe/vigra/issues/462'.

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

Bug#923467: libvigraimpex: FTBFS (Could not import extension sphinx.ext.pngmathCould not import extension sphinx.ext.pngmath)

[Andreas Metzler]

Control: forwarded -1 https://github.com/ukoethe/vigra/issues/462

On 2019-02-28 Santiago Vila  wrote:
> Package: src:libvigraimpex
> Version: 1.10.0+git20160211.167be93+dfsg1-1
> Severity: serious
> Tags: ftbfs

> Dear maintainer:

> I tried to build this package in buster but it failed:
> [...]
> Running Sphinx v1.8.4

> Extension error:
> Could not import extension sphinx.ext.pngmath (exception: No module named 
> 'sphinx.ext.pngmath')
[...]

http://www.sphinx-doc.org/en/master/changes.html

Features removed

1.8.0b1

sphinx.ext.pngmath extension


cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#923013: marked as done (xen: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 17:37:18 +
with message-id 
and subject line Bug#923013: fixed in xen 4.11.1+26-g87f51bf366-3
has caused the Debian Bug report #923013,
regarding xen: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
923013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xen
Version: 4.11.1+26-g87f51bf366-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid with "dpkg-buildpackage -A" but it failed:


[...]
 debian/rules build-indep
dh build-indep --with=python2
   debian/rules override_dh_update_autotools_config
make[1]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366'
cp /usr/share/misc/{config.sub,config.guess} .
make[1]: Leaving directory '/<>/xen-4.11.1+26-g87f51bf366'
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366'
cp debian/xen-kconfig xen/.config
make -C xen olddefconfig  XEN_COMPILE_ARCH=x86_64 XEN_TARGET_ARCH=x86_64 
make[2]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366/xen'
make -f 
/<>/xen-4.11.1+26-g87f51bf366/xen/tools/kconfig/Makefile.kconfig 
ARCH=x86_64 SRCARCH=x86 HOSTCC="gcc" HOSTCXX="g++" olddefconfig
make[3]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366/xen'

[... snipped ...]

   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   debian/rules override_dh_compress
make[1]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366'
rdfind -makehardlinks true -makeresultsfile false \
debian/xenstore-utils/usr/bin
Now scanning "debian/xenstore-utils/usr/bin", found 0 files.
Now have 0 files in total.
Removed 0 files due to nonunique device and inode.
Total size is 0 bytes or 0 B
Removed 0 files due to unique sizes from list.0 files left.
Now eliminating candidates based on first bytes:removed 0 files from list.0 
files left.
Now eliminating candidates based on last bytes:removed 0 files from list.0 
files left.
Now eliminating candidates based on sha1 checksum:removed 0 files from list.0 
files left.
It seems like you have 0 files that are not unique
Totally, 0 B can be reduced.
Now making hard links.
Making 0 links.
:
dh_compress
find debian/xen-hypervisor-*/usr/lib/debug -type f -print0 \
| xargs -0r gzip -9vn
find: 'debian/xen-hypervisor-*/usr/lib/debug': No such file or directory
make[1]: Leaving directory '/<>/xen-4.11.1+26-g87f51bf366'
   dh_fixperms -i
   debian/rules override_dh_missing
make[1]: Entering directory '/<>/xen-4.11.1+26-g87f51bf366'
dh_missing --fail-missing
dh_missing: etc/bash_completion.d/xl.sh exists in debian/tmp but is not 
installed to anywhere
dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libxen-dev (30), libxencall1 (2), libxendevicemodel1 
(2), libxenevtchn1 (2), libxenforeignmemory1 (2), libxengnttab1 (2), 
libxenmisc4.11 (14), libxenstore3.0 (2), libxentoolcore1 (2), libxentoollog1 
(2), xen-doc (1), xen-hypervisor-4.11-amd64 (3), xen-hypervisor-4.11-arm64 (0), 
xen-hypervisor-4.11-armhf (0), xen-hypervisor-common (1), xen-system-amd64 (0), 
xen-system-arm64 (0), xen-system-armhf (0), xen-utils-4.11 (4), 
xen-utils-common (18), xenstore-utils (13)
 * dh_installdocs: libxen-dev (0), libxencall1 (0), libxendevicemodel1 
(0), libxenevtchn1 (0), libxenforeignmemory1 (0), libxengnttab1 (0), 
libxenmisc4.11 (0), libxenstore3.0 (0), libxentoolcore1 (0), libxentoollog1 
(0), xen-doc (0), xen-hypervisor-4.11-amd64 (0), xen-hypervisor-4.11-arm64 (0), 
xen-hypervisor-4.11-armhf (0), xen-hypervisor-common (0), xen-system-amd64 (0), 
xen-system-arm64 (0), xen-system-armhf (0), xen-utils-4.11 (0), 
xen-utils-common (0), xenstore-utils (0)
 * dh_installexamples: libxen-dev (0), libxencall1 (0), 
libxendevicemodel1 (0), libxenevtchn1 (0), libxenforeignmemory1 (0), 
libxengnttab1 (0), libxenmisc4.11 (0), libxenstore3.0 (0), libxentoolcore1 (0), 
libxentoollog1 (0), xen-doc (0), xen-hypervisor-4.11-amd64 (0), 
xen-hypervisor-4.11-arm64 (0), xen-hypervisor-4.11-armhf (0), 
xen-hypervisor-common (0), xen-system-amd64 (0), xen-system-arm64 (0), 
xen-system-armhf (0), xen-utils-4.11 (0), xen-utils-common (1), xenstore-utils 
(0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper 

Bug#923465: Freecad - No module named StartGui

[John Lines]

I had this message after I removed libfreecad-python2-0.17 which was
preventing my updated freecad from running properly

I then did
  apt-get install freecad-python3 

I got the message

Setting up python3-pyside2.qtopengl (5.11.2-3) ...
Setting up libfreecad-python3-0.18 (0.18~pre1+dfsg1-4) ...
Setting up python3-pivy (0.6.4-1) ...
Setting up freecad-python3 (0.18~pre1+dfsg1-4) ...
update-alternatives: warning: forcing reinstallation of alternative
/usr/lib/freecad/bin/freecad-python2 because link group freecad is
broken

but my system now seems to be working - I suggest trying doing an
update-alternatives to force freecad-python2 to be used properly

Bug#921421: c-t-b-mipsen now built

[Matthias Klose]

Version: 2~c2

c-t-b-mipsen now built.

Bug#921421: marked as done (gcc-8-cross-mipsen: FTBFS in sid (Version in Debian Archive >= Version in debian/changelog))

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 18:13:47 +0100
with message-id <91459d68-7e96-16c8-7867-7dcbb4699...@debian.org>
and subject line c-t-b-mipsen now built
has caused the Debian Bug report #921421,
regarding gcc-8-cross-mipsen: FTBFS in sid (Version in Debian Archive >= 
Version in debian/changelog)
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.)


-- 
921421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-8-cross-mipsen
Version: 2~c1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:



dpkg-buildpackage
-

dpkg-buildpackage: info: source package gcc-8-cross-mipsen
dpkg-buildpackage: info: source version 2~c1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by YunQiang Su 
 dpkg-source --before-build .
 fakeroot debian/rules clean
gcc: 8.2.0-16 / 8.2.0-16cross1

old gcc version: 8.2.0-16 / 1
debian/rules:68: *** Version in Debian Archive >= Version in debian/changelog.  
Stop.
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


The same thing happens here:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gcc-8-cross-mipsen_2~c1.rbuild.log.gz

Simple question: It is not possible to use a versioned Build-Depends for this?
(For QA purposes, a package with unsatisfiable build-depends is a lot
easier to track than this).

Thanks.
--- End Message ---
--- Begin Message ---
Version: 2~c2

c-t-b-mipsen now built.--- End Message ---

Processed: Remove jajuk pending tag 923330

[Debian Bug Tracking System]

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

> tags 923330 - pending
Bug #923330 [jajuk] jajuk: Fails to start with Java Runtime Environment 1.7 
minimum required. You use a JVM ext.JVM@23fc625e
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#784479: [kde4libs] Qt4's WebKit removal

[Paul Gevers]

Hi Scott,

On Tue, 15 Jan 2019 11:03:33 + Scott Kitterman
 wrote:

> I think rebuilding the rdepends is a reasonable next step.  I'll try
> that and see if anything is affected.

Did you get around to do this?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#923474: libbpp-core: FTBFS (dh_makeshlibs fails)

[Santiago Vila]

Package: src:libbpp-core
Version: 2.4.1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works

[... snipped ...]

+#MISSING: 2.4.1-2# _ZNSt6vectorIjSaIjEE9push_backERKj@Base 2.4.1
  _ZNSt6vectorImSaImEE17_M_default_appendEm@Base 2.4.1
  
_ZNSt6vectorImSaImEE17_M_realloc_insertIJRKmEEEvN9__gnu_cxx17__normal_iteratorIPmS1_EEDpOT_@Base
 2.4.1
  _ZNSt6vectorImSaImEEaSERKS1_@Base 2.4.1
@@ -2225,6 +2232,7 @@
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_mESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE4findERS7_@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_mESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE7_M_copyINSE_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS8_EPKSI_PSt18_Rb_tree_node_baseRT_@Base
 2.4.1
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_mESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 2.4.1
+ 
_ZNSt8_Rb_treeIPN3bpp13GraphObserverES2_St9_IdentityIS2_ESt4lessIS2_ESaIS2_EE16_M_insert_uniqueIRKS2_EESt4pairISt17_Rb_tree_iteratorIS2_EbEOT_@Base
 2.4.1-2
  
_ZNSt8_Rb_treeIPN3bpp13GraphObserverES2_St9_IdentityIS2_ESt4lessIS2_ESaIS2_EE7_M_copyINS8_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS2_EPKSC_PSt18_Rb_tree_node_baseRT_@Base
 2.4.1
  
_ZNSt8_Rb_treeIPN3bpp13GraphObserverES2_St9_IdentityIS2_ESt4lessIS2_ESaIS2_EE7_M_copyINS8_20_Reuse_or_alloc_nodeEEEPSt13_Rb_tree_nodeIS2_EPKSC_PSt18_Rb_tree_node_baseRT_@Base
 2.4.1
  
_ZNSt8_Rb_treeIPN3bpp13GraphObserverES2_St9_IdentityIS2_ESt4lessIS2_ESaIS2_EE8_M_eraseEPSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
@@ -2267,16 +2275,17 @@
  
_ZNSt8_Rb_treeIjSt4pairIKjS0_IjjEESt10_Select1stIS3_ESt4lessIjESaIS3_EEaSERKS9_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE12_M_erase_auxESt23_Rb_tree_const_iteratorIS2_E@Base
 2.4.1
  
(optional)_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSA_PSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
- 
(optional)_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE16_M_insert_uniqueIS0_IjjEEES0_ISt17_Rb_tree_iteratorIS2_EbEOT_@Base
 2.4.1
+#MISSING: 2.4.1-2# 
(optional)_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE16_M_insert_uniqueIS0_IjjEEES0_ISt17_Rb_tree_iteratorIS2_EbEOT_@Base
 2.4.1
  
(optional)_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE17_M_emplace_uniqueIJS0_IjjS0_ISt17_Rb_tree_iteratorIS2_EbEDpOT_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE7_M_copyINS8_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS2_EPKSC_PSt18_Rb_tree_node_baseRT_@Base
 2.4.1
  
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE8_M_eraseEPSt13_Rb_tree_nodeIS2_E@Base
 2.4.1
  
_ZNSt8_Rb_treeIjjSt9_IdentityIjESt4lessIjESaIjEE16_M_insert_uniqueIRKjEESt4pairISt17_Rb_tree_iteratorIjEbEOT_@Base
 2.4.1
- _ZNSt8_Rb_treeIjjSt9_IdentityIjESt4lessIjESaIjEE5eraseERKj@Base 2.4.1
+#MISSING: 2.4.1-2# 
_ZNSt8_Rb_treeIjjSt9_IdentityIjESt4lessIjESaIjEE5eraseERKj@Base 2.4.1
  
_ZNSt8_Rb_treeIjjSt9_IdentityIjESt4lessIjESaIjEE8_M_eraseEPSt13_Rb_tree_nodeIjE@Base
 2.4.1
  
_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE14_M_insert_nodeEPSt18_Rb_tree_node_baseSD_PSt13_Rb_tree_nodeIS5_E@Base
 2.4.1
+ 
_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOmEESG_IJESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base
 2.4.1-2
  
_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
  
_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base
 2.4.1
  

Bug#909416: gnome-keyring: FTBFS randomly (autobuilder hangs)

[Paul Gevers]

Hi GNOME maintainers,

On Sun, 23 Sep 2018 10:35:50 + Santiago Vila  wrote:

> I'm reporting this as serious because it happens on the buildds:
>
>
https://buildd.debian.org/status/fetch.php?pkg=gnome-keyring=s390x=3.28.2-1=1526387132=0

Any progress on this? We are nearing the full freeze.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#909417: gtk-vnc: FTBFS randomly (vncconnectiontest fails with "assertion failed")

[Paul Gevers]

Hi Libvirt maintainers,

On Sun, 23 Sep 2018 10:35:52 + Santiago Vila  wrote:

> I'm reporting this as serious because it happens on the buildds:
>
>
https://buildd.debian.org/status/fetch.php?pkg=gtk-vnc=amd64=0.6.0-3=1486745781=0

Any progress on this? We are nearing the full freeze.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#923473: exiv2: CVE-2019-9144

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/Exiv2/exiv2/issues/712

Hi,

The following vulnerability was published for exiv2.

CVE-2019-9144[0]:
| An issue was discovered in Exiv2 0.27. There is infinite recursion at
| BigTiffImage::printIFD in the file bigtiffimage.cpp. This can be
| triggered by a crafted file. It allows an attacker to cause Denial of
| Service (Segmentation fault) or possibly have unspecified other impact.

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-2019-9144
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9144
[1] https://github.com/Exiv2/exiv2/issues/712

Regards,
Salvatore

Bug#923472: exiv2: CVE-2019-9143

[Salvatore Bonaccorso]

Source: exiv2
Version: 0.26-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/Exiv2/exiv2/issues/711

Hi,

The following vulnerability was published for exiv2.

CVE-2019-9143[0]:
| An issue was discovered in Exiv2 0.27. There is infinite recursion at
| Exiv2::Image::printTiffStructure in the file image.cpp. This can be
| triggered by a crafted file. It allows an attacker to cause Denial of
| Service (Segmentation fault) or possibly have unspecified other impact.

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-2019-9143
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9143
[1] https://github.com/Exiv2/exiv2/issues/711

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#921291: marked as done (openhft-chronicle-bytes: FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 16:20:06 +
with message-id 
and subject line Bug#921291: fixed in openhft-chronicle-bytes 1.1.15-2
has caused the Debian Bug report #921291,
regarding openhft-chronicle-bytes: FTBFS on i386
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.)


-- 
921291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openhft-chronicle-bytes
Version: 1.16.25-1
Severity: serious
Justification: fails to build from source

Hi,

openhft-chronicle-bytes FTBFS in a i386 pbuilder chroot, while it builds
successfully in an amd64 pbuilder chroot.


Andreas


openhft-chronicle-bytes_1.16.25-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: openhft-chronicle-bytes
Source-Version: 1.1.15-2

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated 
openhft-chronicle-bytes 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, 28 Feb 2019 14:20:34 +0100
Source: openhft-chronicle-bytes
Binary: libopenhft-chronicle-bytes-java
Architecture: source
Version: 1.1.15-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Andrej Shadura 
Description:
 libopenhft-chronicle-bytes-java - OpenHFT byte buffer library
Closes: 921291
Changes:
 openhft-chronicle-bytes (1.1.15-2) unstable; urgency=medium
 .
   * Fix Java 9 compatibility.
   * Ignore test failures (Closes: #921291).
Checksums-Sha1:
 01a58577a1c857431ff62d8c4b865955a78326f0 2086 
openhft-chronicle-bytes_1.1.15-2.dsc
 c0c520082a7850c6bdd42ef01c2828c0493b34ea 4540 
openhft-chronicle-bytes_1.1.15-2.debian.tar.xz
Checksums-Sha256:
 6cfe7b6c22fa078bb147843aa994140a9ebdd90927278257b647650e46472759 2086 
openhft-chronicle-bytes_1.1.15-2.dsc
 273514e05b006b75da20df90373e2a80d19afb82592e7810c8a3a6234d69638d 4540 
openhft-chronicle-bytes_1.1.15-2.debian.tar.xz
Files:
 25b67893b1175c7eb6ea165b229bda63 2086 java optional 
openhft-chronicle-bytes_1.1.15-2.dsc
 00ef2fada2695974b7dfdfd6454a715d 4540 java optional 
openhft-chronicle-bytes_1.1.15-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlx4B/kACgkQXkCM2RzY
OdJ+Jwf/eq3yEFeMU5w7Y950rK8KduEnU1cSYvH39w+BSuHU7I/KzOlIE0kUCCwd
YYwcow9UTk/xhPIz3X7gleDZO46oVvqAvYSdj3PQMVbtZjcQtqPpO1siktmnAKS6
4YncCCPyQmhQKWtaVWF9Jo3SvdFylO9MPhCgbTvm8dvqlOtOxMpfr4AH5LTPxHvu
XHZaoa5UEBYGhWQGWijqfJ2XjJmLn9UAzTQB25JMZgxtR0kxnysuKdc9WLHfFt6s
wLize19/GMM/ONOU6Ggae0daw89EzefGxkt6ODF1LDHPCWUB9c1Qq/c1ktn6z8KL
m5psSpUkAnWl+qrCqVakb52lO3mY+Q==
=NMVG
-END PGP SIGNATURE End Message ---

Bug#904808: libcap-ng0: libcap-ng's use of pthread_atfork causes segfaults

[Florian Weimer]

The problem here is the weak declaration:

$ eu-readelf --symbols=.dynsym /lib64/libcap-ng.so.0.0.0 | grep pthread_atfork
   28:   0 NOTYPE  WEAK   DEFAULTUNDEF pthread_atfork

In the Fedora 29 build, the constructor looks like this:

Dump of assembler code for function init_lib:
   0x25d0 <+0>: endbr64 
   0x25d4 <+4>: cmpq   $0x0,0x4a0c(%rip)# 0x6fe8
   0x25dc <+12>:je 0x25ee 
   0x25de <+14>:lea0xcb(%rip),%rdx# 0x26b0 
   0x25e5 <+21>:xor%esi,%esi
   0x25e7 <+23>:xor%edi,%edi
   0x25e9 <+25>:jmpq   0x24f0 
   0x25ee <+30>:retq

src/cap-ng.c has this:

/*
 * The pthread_atfork function is being made weak so that we can use it
 * if the program is linked with pthreads and not requiring it for
 * everything that uses libcap-ng.
 */
extern int __attribute__((weak)) pthread_atfork(void (*prepare)(void),
void (*parent)(void), void (*child)(void));
…
static void init_lib(void) __attribute__ ((constructor));
static void init_lib(void)
{
if (pthread_atfork)
pthread_atfork(NULL, NULL, deinit);
}

This is wrong.  pthread_atfork needs to be *strong* reference, otherwise
the implementation in libc_nonshared.a is not used.  This implementation
provides the correct __dso_handle argument, allowing unregistration at
dlclose.

For glibc 2.28 and later, the fix should be simple: Just delete the weak
declaration.  For older glibc versions, you need to call
__register_atfork directly, with an explicit __dso_handle argument.  (I
believe systemd has an example of this which looks correct.)  This is a
stable glibc ABI, despite all those glibc internals.

We cannot fix this in libpthread because of the tail call in init_lib.
It destroys the caller's stack frame, so the identity of the calling DSO
is not available to pthread_atfork.  (Without the tail call, we could
use __builtin_return_address (0) and the internal variant of dladdr to
figure out the caller.)

Thanks,
Florian

Processed: unarchive 904808

[Debian Bug Tracking System]

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

> unarchive 904808
Bug #904808 {Done: Pierre Chifflier } [libcap-ng0] 
libcap-ng0: libcap-ng's use of pthread_atfork causes segfaults
Bug #914565 {Done: Pierre Chifflier } [libcap-ng0] 
php7.3-intl: Segfaults after apache2 graceful restart
Bug #915642 {Done: Pierre Chifflier } [libcap-ng0] 
AuthBasicProvider PAM crashes apache
Unarchived Bug 904808
Unarchived Bug 914565
Unarchived Bug 915642
>
End of message, stopping processing here.

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

Bug#923427: mergechanges: Regression: --indep/source mangles/breaks (valid?) Binary fields

[Mattia Rizzolo]

Hi,

On Thu, Feb 28, 2019 at 07:38:36AM +0100, Salvatore Bonaccorso wrote:
> I had prepared an upload where I issued mergechanges --indep on the
> _amd64.changes to produce a changes to include only source packages
> and architecture-independent packages.
> 
> $ mergechanges --indep -f linux_4.9.161-1_amd64.changes 
> linux_4.9.161-1_amd64.changes 
> Error: acpi-modules-4.9.0-9-amd64-di not found in Binary field
> b4ae0b22174cb1c7bf009bfcf0deaee8 10304 debian-installer extra 
> acpi-modules-4.9.0-9-amd64-di_4.9.161-1_amd64.udeb
> 
> This seems related to the change included in the 2.19.3 version, as
> the version in stretch creates the _multi.changes correctly

The version in stretch does exactly nothing to the Binary field, that's
why it's "correct" :)

> I'm attaching the original amd64.changes, plus the multi.changes
> produced with 2.17.6+deb9u2 and the multi.changes.broken produced with
> (2.19.3).

If I see this correctly, it's all because the code reads only the first
line of the Binary field, without considering it may be a multiline
field (and tbh I didn't even realized it could be…)

Simon: since you wrote the first patch, do you think you wold be able to
come up with a fix for this as well? :)  TIA!

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#923238: libmarc-charset-perl: needs a rebuild on 32bit architectures?

[Niko Tyni]

On Thu, Feb 28, 2019 at 12:06:18PM +, Dmitry Bogatov wrote:
> 
> [2019-02-27 21:20] Niko Tyni 
> > > - update perl to build-depend on libgdbm-dev (>= 1.18-2) and Break
> > >   older versions of libmarc-charset-perl (and any other perl packages
> > >   bundling GDBM or NDBM databases)
> > > 
> > > - update libmarc-charset-perl (and any other perl packages bundling
> > >   GDBM or NDBM databases) to build-depend and depend on the newer perl
> > > 
> > > I assume other language bindings like python-gdbm will need something
> > > similar.
> >
> > But ideally gdbm would restore compatibility and libmarc-charset-perl would
> > not need any changes.
> 
> I believe upstream release 1.8.1 introduced change, that
> made it possible to read old /usr/lib/libmarc-charset-perl/Table. Am I
> missing something in current situation?

I thought so too, but this new bug highlights the fact that the fix
does not work on all architectures.  This was missed earlier because
Debian does not have autopkgtest checks on !amd64, so we're relying
on user bug reports and haven't got any so far.

I've now verified that creating GDBM files with Perl, Python 2 or Python 3
on stretch i386 and then upgrading to buster renders the old databases
unusable with the corresponding software in buster.

I can file a separate bug against src:gdbm if that makes things clearer.

> By the way, I disagree about compability. If all we need to make
> everything good is just a binNMU, I'd rather not introduce any
> patches/hacks/compatibility layers/etc.

binNMU'ing libmarc-charset-perl will only fix libmarc-charset-perl,
not unpackaged local user databases. If those become unusable on
stretch -> buster upgrades with no way to recover them, that seems
like a major problem. 

binNMU'ing libmarc-charset-perl does not fix partial upgrades where
perl that uses a newer libgdbm is upgraded before  libmarc-charset-perl.
Hence the need for Breaks and versioned build dependencies that I listed.

> By the way, it is sad that libmarc-charset-perl uses gdbm, not cdb.

Are you referring to https://cr.yp.to/cdb.html ? I see there's a CDB_File
Perl module in libcdb-file-perl but I'm not familiar with it. Seems worth
a wishlist bug.
-- 
Niko Tyni   nt...@debian.org

Bug#923420: marked as done (coreutils: mv broken when file system doesn't support RENAME_NOREPLACE)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 15:49:55 +
with message-id 
and subject line Bug#923420: fixed in coreutils 8.30-3
has caused the Debian Bug report #923420,
regarding coreutils: mv broken when file system doesn't support RENAME_NOREPLACE
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.)


-- 
923420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coreutils
Version: 8.30-2
Severity: serious

Hi,

With those distro patches from version 8.30-2 mv fails on filesystems that don't
support the renameat2 RENAME_NOREPLACE flag.
I noticed this because coreutils 8.30-2 breaks autopkgtest with the qemu runner
which calls mv on a 9p filesystem.

renameatu.patch is the offender as it only changes renameat2() calls to 
renameatu()
in lib/ but not in src/.
As a result some tools call the glibc renameat2() instead of the gnulib one 
which
has appropriate fallbacks.
I haven't checked what other tools are exactly affected (calls are in mv.c, 
shred.c
and copy.c).

After an extended debugging session,
Felix
--- End Message ---
--- Begin Message ---
Source: coreutils
Source-Version: 8.30-3

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

Debian distribution maintenance software
pp.
Michael Stone  (supplier of updated coreutils 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, 28 Feb 2019 10:30:31 -0500
Source: coreutils
Binary: coreutils coreutils-dbgsym
Architecture: source amd64
Version: 8.30-3
Distribution: unstable
Urgency: medium
Maintainer: Michael Stone 
Changed-By: Michael Stone 
Description:
 coreutils  - GNU core utilities
Closes: 923420
Changes:
 coreutils (8.30-3) unstable; urgency=medium
 .
   * Fix renameat2 patch (Closes: #923420)
Checksums-Sha1:
 7a110d042666df380eaf2338d6e324a42fdf8d55 1861 coreutils_8.30-3.dsc
 09a9761b2c781fee706833bc99e40c9cdc41689f 32808 coreutils_8.30-3.debian.tar.xz
 34e12929f616575f998aa86d557712ab1b251123 7168128 
coreutils-dbgsym_8.30-3_amd64.deb
 8317de329a7ba1c6148b66b7f00fbaeb4f5b12df 7078 coreutils_8.30-3_amd64.buildinfo
 df3e8007a3bcb8db05ac55277676936ccb1c9435 2707932 coreutils_8.30-3_amd64.deb
Checksums-Sha256:
 106031a57a2ab2ba46b61083035e2ccb438c85a2b3506a8198b67868dde1546d 1861 
coreutils_8.30-3.dsc
 9179d45fb51d07a8743c4d58464459330eb6d4b489d59641d70c3bd9f579b694 32808 
coreutils_8.30-3.debian.tar.xz
 44409552e5699b21b6a55443d6115cd5b9bf5b6e2c2bdfab71d213a0f0a6354c 7168128 
coreutils-dbgsym_8.30-3_amd64.deb
 fd5f9230ea263fc763537c86d6a296f778345ced6d80ed973fb985f47b2b96dd 7078 
coreutils_8.30-3_amd64.buildinfo
 ae6e5cd6e9aaf74d66edded3931a7a6c916625b8b890379189c75574f6856bf4 2707932 
coreutils_8.30-3_amd64.deb
Files:
 8e7167ff50149c83192535df18eee396 1861 utils required coreutils_8.30-3.dsc
 f68506bc07552eee03c7652cb38431e8 32808 utils required 
coreutils_8.30-3.debian.tar.xz
 da01e2c62a06720f9ec4da1a47d65d54 7168128 debug optional 
coreutils-dbgsym_8.30-3_amd64.deb
 b8c27d1c7c86c979cb75a4f4cd9e427f 7078 utils required 
coreutils_8.30-3_amd64.buildinfo
 4a658a39c2810530df6642d22f65ddd1 2707932 utils required 
coreutils_8.30-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAtUxX/EfDh4C9hqs3PoR/94FAlx3/2QACgkQ9hqs3PoR
/94EjQ//XzQ+HSACRp6qUgGPgbupZJdVws23alDnslDki/GcZFu8MMNjVZYMWKWI
a2YKLHLArHi1/WWSBn60hQrZ46bPvdvH2xfDQCEpGUAspbL6g2XP2yTtOisxBAbm
HMey1WCzsL/oRw2jhsUxOkVO+i9Wdd/ijf8Y27XTUCtZ9jDrldbJQo7j+5NiIQcA
NfCye/ehQve2ckYbow7va4KJYAnM9eoSpW9CnNSQQAKuNGJMN1/Z+GwGDHyaHV4b
2nrSUitH1/Xy8ohzfye25jScPuEV+wajb3W5A5xQ8CnIKBFT/Pt8dooDsBRq3ZgT
n8tIsWS2ARFzFMaKdEthcINu1J2d6NIMWuLNAiAYPlo3xdbKjdr34L7j+PoLaAFG
rXk4nEJgbfAJzRCRA7jENpBfIJQWvdOd6DgJklkhyXrfEo2AaftCs0AM379Cbe/S
FdIu5yvaFxPJpGomBVpwJ3f0UjVaVANnpF2SRlBve0OFv0ojcyzrnt9U3em1ugm4
mmOyzb+2f5yCjxXUnNs/DdnrRRw55ASHmUH9yel9ua+PdSNJPoV27FxPf6bvBM06
dycDyl2Sub7qx5biKr5cKrwbqNmPyou/4ZNgXHT7U+nUZjC5bgoUU3o6uwYfzA34
s1UxjPSmoIF/IEQ9k9pX2OFJDPafS5MFe7sZ+5cfPC6+RSFZNgg=
=cBft
-END PGP SIGNATURE End Message ---

Bug#923462: marked as done (zfs-dkms 0.7.12-4 postinstall failed)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 15:49:55 +
with message-id 
and subject line Bug#923420: fixed in coreutils 8.30-3
has caused the Debian Bug report #923420,
regarding zfs-dkms 0.7.12-4 postinstall 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.)


-- 
923420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zfs-dkms
Version: 0.7.12-4
Severity: normal

Dear Maintainer,

zfs-dkms 0.7.12-4 module build failed (postinstall)


Entpacken von zfs-dkms (0.7.12-4) über (0.7.12-3) ...
Vorbereitung zum Entpacken von .../6-zfsutils-linux_0.7.12-4_amd64.deb ...
Entpacken von zfsutils-linux (0.7.12-4) über (0.7.12-3) ...
Vorbereitung zum Entpacken von .../7-libattr1_1%3a2.4.48-1_amd64.deb ...
Entpacken von libattr1:amd64 (1:2.4.48-1) über (1:2.4.47-4) ...
libattr1:amd64 (1:2.4.48-1) wird eingerichtet ...
(Lese Datenbank ... 157451 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libfltk-images1.3_1.3.4-9_amd64.deb ...
Entpacken von libfltk-images1.3:amd64 (1.3.4-9) über (1.3.4-8) ...
Vorbereitung zum Entpacken von .../libfltk1.3_1.3.4-9_amd64.deb ...
Entpacken von libfltk1.3:amd64 (1.3.4-9) über (1.3.4-8) ...
Vorbereitung zum Entpacken von .../libllvm7_1%3a7.0.1-7_amd64.deb ...
Entpacken von libllvm7:amd64 (1:7.0.1-7) über (1:7.0.1-6) ...
libuutil1linux (0.7.12-4) wird eingerichtet ...
libfltk1.3:amd64 (1.3.4-9) wird eingerichtet ...
libfltk-images1.3:amd64 (1.3.4-9) wird eingerichtet ...
zfs-dkms (0.7.12-4) wird eingerichtet ...
Loading new zfs-0.7.12 DKMS files...
Building for 4.19.0-3-amd64
Building initial module for 4.19.0-3-amd64
mv: cannot move 'conftest.o' to a subdirectory of itself, 'conftstm.o'
configure: error: *** Unable to build an empty module.
Error! Bad return status for module build on kernel: 4.19.0-3-amd64 (x86_64)
Consult /var/lib/dkms/zfs/0.7.12/build/make.log for more information.
dpkg: Fehler beim Bearbeiten des Paketes zfs-dkms (--configure):
 »installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab
den Fehlerwert 10 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von zfs-initramfs:
 zfs-initramfs hängt ab von zfs-modules | zfs-dkms; aber:
  Paket zfs-modules ist nicht installiert.
  Paket zfs-dkms, das zfs-modules bereitstellt, ist noch nicht konfiguriert.
  Paket zfs-dkms ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes zfs-initramfs (--configure):
 Abhängigkeitsprobleme - verbleibt unkonfiguriert
libllvm7:amd64 (1:7.0.1-7) wird eingerichtet ...
libnvpair1linux (0.7.12-4) wird eingerichtet ...
libzpool2linux (0.7.12-4) wird eingerichtet ...
libzfs2linux (0.7.12-4) wird eingerichtet ...
zfsutils-linux (0.7.12-4) wird eingerichtet ...
zfs-import-scan.service is a disabled or a static unit, not starting it.
insserv: FATAL: service zfs-zed has to be enabled to use service zfs-share
Trigger für libc-bin (2.28-7) werden verarbeitet ...
Trigger für systemd (241-1) werden verarbeitet ...
Trigger für man-db (2.8.5-2) werden verarbeitet ...
Trigger für initramfs-tools (0.133) werden verarbeitet ...
update-initramfs: Generating /boot/initrd.img-4.19.0-3-amd64
cryptsetup: ERROR: Couldn't resolve device rpool/hsp1/debian-root
cryptsetup: WARNING: Couldn't determine root device
Fehler traten auf beim Bearbeiten von:
 zfs-dkms
 zfs-initramfs
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages zfs-dkms depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  dkms   2.6.1-4
ii  lsb-release10.2018112800
ii  perl   5.28.1-4
ii  spl-dkms   0.7.12-2

Versions of packages zfs-dkms recommends:
ii  linux-libc-dev  4.19.20-1
pn  zfs-zed 
ii  zfsutils-linux  0.7.12-4

zfs-dkms suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: coreutils
Source-Version: 8.30-3

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

A summary of the changes between this 

Bug#913119: Bug#913138: Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

[Thorsten Glaser]

Hi Debian Linux kernel maintainers,

On Wed, 27 Feb 2019, Dragan Milenkovic wrote:
> > Hello Dragan, do you know if the patch was eventually included upstream and
> > possibly in which version?
> 
> Hello, Cesare. It was included in 4.20.11 and 4.19.24.

please do consider uploading 4.19.24 to buster/sid with some haste.
We have headless virtualisation hosts being unreachable/frozen now,
and while these are “only” development systems, this is untenable.

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*

**!!! NEU !!!** Mit der **tarent Academy** bieten wir ab sofort auch Trainings
und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und
Zukunftstechnologien an. Besuchen Sie uns
auf [www.tarent.de/academy](http://www.tarent.de/academy). Wir freuen uns auf
Ihren Kontakt.

*

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> reassign 923462 coreutils
Bug #923462 [zfs-dkms] zfs-dkms 0.7.12-4 postinstall failed
Bug reassigned from package 'zfs-dkms' to 'coreutils'.
No longer marked as found in versions zfs-linux/0.7.12-4.
Ignoring request to alter fixed versions of bug #923462 to the same values 
previously set
> forcemerge 923420 923462
Bug #923420 [coreutils] coreutils: mv broken when file system doesn't support 
RENAME_NOREPLACE
Bug #923462 [coreutils] zfs-dkms 0.7.12-4 postinstall failed
Severity set to 'serious' from 'normal'
Marked as found in versions coreutils/8.30-2.
Merged 923420 923462
> Sorry, this should work...
Unknown command or malformed arguments to command.
> --
Stopping processing here.

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

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> reassign 923420 coreutils
Bug #923420 [coreutils] coreutils: mv broken when file system doesn't support 
RENAME_NOREPLACE
Ignoring request to reassign bug #923420 to the same package
> forcemerge 923420 923462
Bug #923420 [coreutils] coreutils: mv broken when file system doesn't support 
RENAME_NOREPLACE
Unable to merge bugs because:
package of #923462 is 'zfs-dkms' not 'coreutils'
Failed to forcibly merge 923420: Did not alter merged bugs.

> --
Stopping processing here.

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

Processed (with 1 error): Re: [Pkg-zfsonlinux-devel] Bug#923462: zfs-dkms 0.7.12-4 postinstall failed

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 923420 -1
Bug #923420 [coreutils] coreutils: mv broken when file system doesn't support 
RENAME_NOREPLACE
Unable to merge bugs because:
package of #923462 is 'zfs-dkms' not 'coreutils'
Failed to forcibly merge 923420: Did not alter merged bugs.


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

Bug#923467: libvigraimpex: FTBFS (Could not import extension sphinx.ext.pngmathCould not import extension sphinx.ext.pngmath)

[Santiago Vila]

Package: src:libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
make: Nothing to be done for 'build-indep'.
 fakeroot debian/rules binary-indep
dh_testdir
dh_testroot
/usr/bin/make -f debian/rules doc/vigra/build-stamp
make[1]: Entering directory 
'/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1'
mkdir -p obj/
cd obj/ && cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DLIB_SUFFIX="/x86_64-linux-gnu/" -DCMAKE_VERBOSE_MAKEFILE=ON -DWITH_OPENEXR=ON 
-DCMAKE_C_FLAGS_RELEASE="-g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2" -DCMAKE_CXX_FLAGS_RELEASE="-g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2" -DCMAKE_SHARED_LINKER_FLAGS_RELEASE="-Wl,-z,relro 
-Wl,--as-needed -Wl,-z,now"  -DPYTHON_EXECUTABLE=/usr/bin/python 
-DWITH_VIGRANUMPY=0
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]

/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1VolumeExportInfo.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1HDF5Handle.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/ErrorReporting.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/group__StandardImageTypes.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/NumericPromotionTraits.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/group__NonLinearDiffusion.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1SIFImportInfo-members.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1GaborFilterFamily-members.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1acc_1_1Central_3_01PowerSum_3_012_01_4_01_4-members.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/Tutorial.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/PromoteTraits.html
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/docsrc
 && /usr/bin/cmake -E copy_directory 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/docsrc/documents 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/documents
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/docsrc
 && /usr/bin/cmake -E copy_if_different 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/docsrc/../LICENSE.txt
 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/LICENSE.txt
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/docsrc
 && /usr/bin/cmake -E copy_if_different 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/docsrc/../src/matlab/doc/tutorial_reference.pdf
 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/documents/tutorial_reference.pdf
make[5]: Leaving directory 
'/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7'
[100%] Built target doc_cpp
/usr/bin/make -f vigranumpy/docsrc/CMakeFiles/doc_python.dir/build.make 
vigranumpy/docsrc/CMakeFiles/doc_python.dir/depend
make[5]: Entering directory 
'/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7'
cd /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7 
&& /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/vigranumpy/docsrc 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/vigranumpy/docsrc
 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/vigranumpy/docsrc/CMakeFiles/doc_python.dir/DependInfo.cmake
 --color=
Scanning dependencies of target doc_python
make[5]: Leaving directory 
'/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7'
/usr/bin/make -f vigranumpy/docsrc/CMakeFiles/doc_python.dir/build.make 
vigranumpy/docsrc/CMakeFiles/doc_python.dir/build
make[5]: Entering directory 
'/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7'
[100%] Generating vigranumpy documentation
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/vigranumpy/docsrc
 && /usr/bin/cmake -E make_directory 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigranumpy
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/vigranumpy/docsrc
 && /usr/bin/sphinx-build -b html -d 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigranumpy/doctrees
 

Bug#872553: RC bugs in synaptic

[Paul Gevers]

Hi Michael, all,

On Fri, 18 Aug 2017 21:02:21 +0800 zaoqi  wrote:
> Segmentation fault

Can you please update us on the status of the two RC bugs that are filed
against synaptic? Has there been any progress? Do you believe that this
is still happening? Do these bugs actually have the same root cause (as
a noted solution is the same)?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#923466: lammps: FTBFS (dh_auto_configure fails)

[Santiago Vila]

Package: src:lammps
Version: 0~20181211.gitad1b1897d+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --sourcedirectory=cmake 
--builddirectory=/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build
   dh_update_autotools_config -i -O--sourcedirectory=cmake 
-O--builddirectory=/<>/lammps-0\~20181211.gitad1b1897d\+dfsg1/debian/build
   dh_autoreconf -i -O--sourcedirectory=cmake 
-O--builddirectory=/<>/lammps-0\~20181211.gitad1b1897d\+dfsg1/debian/build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/lammps-0~20181211.gitad1b1897d+dfsg1'
dh_auto_configure -- \
-DPKG_ASPHERE=ON \
-DPKG_BODY=ON \
-DPKG_CLASS2=ON \
-DPKG_COLLOID=ON \
-DPKG_COMPRESS=ON \
-DPKG_CORESHELL=ON \
-DPKG_DIPOLE=ON \

[... snipped ...]


Run Build Command:"/usr/bin/make" "cmTC_341b1/fast"
make[2]: Entering directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_341b1.dir/build.make 
CMakeFiles/cmTC_341b1.dir/build
make[3]: Entering directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_341b1.dir/feature_tests.c.o
/usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c99 -o CMakeFiles/cmTC_341b1.dir/feature_tests.c.o  
 -c 
"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/feature_tests.c"
Linking C executable cmTC_341b1
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_341b1.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 
-fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -Wl,-z,relro  -rdynamic 
CMakeFiles/cmTC_341b1.dir/feature_tests.c.o  -o cmTC_341b1 
make[3]: Leaving directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'


Feature record: C_FEATURE:1c_function_prototypes
Feature record: C_FEATURE:1c_restrict
Feature record: C_FEATURE:0c_static_assert
Feature record: C_FEATURE:1c_variadic_macros


Detecting C [-std=c90] compiler features compiled with the following output:
Change Dir: 
/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_2dfd2/fast"
make[2]: Entering directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_2dfd2.dir/build.make 
CMakeFiles/cmTC_2dfd2.dir/build
make[3]: Entering directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_2dfd2.dir/feature_tests.c.o
/usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c90 -o CMakeFiles/cmTC_2dfd2.dir/feature_tests.c.o  
 -c 
"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/feature_tests.c"
Linking C executable cmTC_2dfd2
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_2dfd2.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 
-fdebug-prefix-map=/<>/lammps-0~20181211.gitad1b1897d+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -Wl,-z,relro  -rdynamic 
CMakeFiles/cmTC_2dfd2.dir/feature_tests.c.o  -o cmTC_2dfd2 
make[3]: Leaving directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/lammps-0~20181211.gitad1b1897d+dfsg1/debian/build/CMakeFiles/CMakeTmp'


Feature record: C_FEATURE:1c_function_prototypes
Feature record: C_FEATURE:0c_restrict
Feature record: C_FEATURE:0c_static_assert
Feature record: C_FEATURE:0c_variadic_macros
dh_auto_configure: cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DPKG_ASPHERE=ON -DPKG_BODY=ON 
-DPKG_CLASS2=ON -DPKG_COLLOID=ON -DPKG_COMPRESS=ON -DPKG_CORESHELL=ON 
-DPKG_DIPOLE=ON -DPKG_GPU=ON -DPKG_GRANULAR=ON -DPKG_KIM=OFF -DPKG_KSPACE=ON 
-DPKG_MANYBODY=ON -DPKG_MC=ON -DPKG_MEAM=ON -DPKG_MISC=ON -DPKG_MOLECULE=ON 
-DPKG_MPIIO=ON -DPKG_OPT=ON -DPKG_PERI=ON -DPKG_POEMS=ON -DPKG_PYTHON=ON 
-DPKG_QEQ=ON -DPKG_REAX=OFF -DPKG_REPLICA=ON -DPKG_RIGID=ON -DPKG_SHOCK=ON 
-DPKG_SNAP=ON -DPKG_SRD=ON 

Bug#923456: marked as done (llvm-toolchain-7: clang(|++-$VERSION) segfault in two autopkgtests)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 14:59:57 +
with message-id 
and subject line Bug#923456: fixed in llvm-toolchain-7 1:7.0.1-8
has caused the Debian Bug report #923456,
regarding llvm-toolchain-7: clang(|++-$VERSION) segfault in two autopkgtests
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.)


-- 
923456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-7
Version: 1:7.0.1-7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of llvm-toolchain-7 the autopkgtest of
llvm-toolchain-7 and clazy fail in testing when that autopkgtest is run
with the binary packages of llvm-toolchain-7 from unstable. It passes
when run with only packages from testing. In tabular form:
   passfail
llvm-toolchain-7   from testing1:7.0.1-7
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. Both tests
fail due to a segfault.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? If needed, please
change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
llvm-toolchain-7/1:7.0.1-7. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=llvm-toolchain-7

https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-7/2026142/log.gz

clang++-$VERSION -c -o part1.o foo.cpp $FLAGS
if test -f /usr/bin/g++; then
g++ -c -o part2.o -DPART2 foo.cpp $FLAGS
clang++-$VERSION -o foo part1.o part2.o $FLAGS
./foo
fi
./debian/qualify-clang.sh: line 383:  2823 Segmentation fault  ./foo


https://ci.debian.net/data/autopkgtest/testing/amd64/c/clazy/2026133/log.gz

Stack dump:
0.  Program arguments: /usr/lib/llvm-7/bin/clang -cc1 -triple
x86_64-pc-linux-gnu -emit-obj -mrelax-all -disable-free
-disable-llvm-verifier -discard-value-names -main-file-name main.cpp
-mrelocation-model pic -pic-level 2 -mthread-model posix
-mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases
-munwind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info
-debugger-tuning=gdb -coverage-notes-file
/tmp/autopkgtest-lxc.5k_mxe4a/downtmp/build.dOH/src/tests/main.gcno
-resource-dir /usr/lib/llvm-7/lib/clang/7.0.1 -isystem
/usr/include/x86_64-linux-gnu/qt5 -internal-isystem
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8
-internal-isystem
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/x86_64-linux-gnu/c++/8
-internal-isystem
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/x86_64-linux-gnu/c++/8
-internal-isystem
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8/backward
-internal-isystem /usr/include/clang/7.0.1/include/ -internal-isystem
/usr/local/include -internal-isystem
/usr/lib/llvm-7/lib/clang/7.0.1/include -internal-externc-isystem
/usr/include/x86_64-linux-gnu -internal-externc-isystem /include
-internal-externc-isystem /usr/include -Wno-unused-value -std=c++14
-fdeprecated-macro -fdebug-compilation-dir
/tmp/autopkgtest-lxc.5k_mxe4a/downtmp/build.dOH/src/tests -ferror-limit
19 -fmessage-length 0 -fobjc-runtime=gcc -fcxx-exceptions -fexceptions
-fdiagnostics-show-option -load ClazyPlugin.so -add-plugin clazy
-plugin-arg-clazy no-inplace-fixits -plugin-arg-clazy
assert-with-side-effects -plugin-arg-clazy enable-all-fixits -o main.o
-x c++ assert-with-side-effects/main.cpp -faddrsig
1.   parser at end of file
/usr/lib/x86_64-linux-gnu/libLLVM-7.so.1(_ZN4llvm3sys15PrintStackTraceERNS_11raw_ostreamE+0x1f)[0x7f5f102505df]
/usr/lib/x86_64-linux-gnu/libLLVM-7.so.1(_ZN4llvm3sys17RunSignalHandlersEv+0x50)[0x7f5f1024eb40]
/usr/lib/x86_64-linux-gnu/libLLVM-7.so.1(+0x9ce8f2)[0x7f5f102508f2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x126e0)[0x7f5f1328e6e0]
/usr/lib/llvm-7/bin/clang[0x188b720]
/usr/lib/llvm-7/bin/clang(_ZN5clang12ast_matchers11MatchFinder8matchASTERNS_10ASTContextE+0x495)[0x188bce5]

Bug#923445: marked as done (ghc: FTBFS (The 'ghc-flag' directive is already registered to domain std))

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 14:52:06 +
with message-id 
and subject line Bug#923445: fixed in ghc 8.4.4+dfsg1-2
has caused the Debian Bug report #923445,
regarding ghc: FTBFS (The 'ghc-flag' directive is already registered to domain 
std)
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.)


-- 
923445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ghc
Version: 8.4.4+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>/ghc-8.4.4+dfsg1'
dh_autoreconf perl -- boot
Creating libraries/ghc-prim/ghc.mk
Creating libraries/text/ghc.mk

[... snipped ...]

/usr/bin/sphinx-build -b html -d docs/users_guide/.doctrees-html -D 
latex_paper_size=letter docs/users_guide docs/users_guide/build-html/users_guide
Running Sphinx v1.8.4

Extension error:
The 'ghc-flag' directive is already registered to domain std
make[3]: *** [docs/users_guide/ghc.mk:16: 
docs/users_guide/build-html/users_guide/index.html] Error 2
make[2]: *** [Makefile:127: all] Error 2
make[2]: Leaving directory '/<>/ghc-8.4.4+dfsg1'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [debian/rules:132: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/ghc-8.4.4+dfsg1'
make: *** [debian/rules:58: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: ghc
Source-Version: 8.4.4+dfsg1-2

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated ghc 
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, 28 Feb 2019 15:18:49 +0100
Source: ghc
Binary: ghc ghc-prof ghc-doc
Architecture: source
Version: 8.4.4+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Gianfranco Costamagna 
Description:
 ghc- The Glasgow Haskell Compilation system
 ghc-doc- Documentation for the Glasgow Haskell Compilation system
 ghc-prof   - Profiling libraries for the Glasgow Haskell Compilation system
Closes: 919518 923445
Changes:
 ghc (8.4.4+dfsg1-2) unstable; urgency=medium
 .
   [ Clint Adams ]
   * Patch Sphinx config to use locally-installed MathJax instead of a
 copy on the Internet.  closes: #919518.
 .
   [ Gianfranco Costamagna ]
   * Fix sphinx 1.8 build with upstream patch (Closes: #923445)
Checksums-Sha1:
 86e5a1d7b3bd38187f08b6fd704cdc93af8f6d5c 2371 ghc_8.4.4+dfsg1-2.dsc
 f7861a7d331439b38f62ecad5033d35b3ad29d63 59284 ghc_8.4.4+dfsg1-2.debian.tar.xz
 da1c73e11daf2074a252639e543e0e1b0164d4a3 8368 
ghc_8.4.4+dfsg1-2_source.buildinfo
Checksums-Sha256:
 7297ae7b153a98643b4715584679a6da0e2e71f3ea96ed57e32eb1d1b0cb02fd 2371 
ghc_8.4.4+dfsg1-2.dsc
 0f36c4ba643cac3a0fd323b6683c181369d18cb55c813644f6ad576f294cf957 59284 
ghc_8.4.4+dfsg1-2.debian.tar.xz
 751726978d086c5d00f6c17083202bcefd94996162e295483043f7b5ae4bd804 8368 
ghc_8.4.4+dfsg1-2_source.buildinfo
Files:
 3cdc93de1bf76236b38d248c51c1b923 2371 haskell optional ghc_8.4.4+dfsg1-2.dsc
 91c2ff3644e843df3ec2d6192af690ac 59284 haskell optional 
ghc_8.4.4+dfsg1-2.debian.tar.xz
 13ec04f30a24d9d6dca6b2cf5dc12788 8368 haskell optional 
ghc_8.4.4+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

Processed: fixed 919869 in 4.1.0-2

[Debian Bug Tracking System]

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

> fixed 919869 4.1.0-2
Bug #919869 {Done: Thomas Andrejak } [prelude-lml] 
prelude-lml: purging prelude-lml deletes /etc/prelude-lml/ruleset/*.rules owned 
by prelude-lml-rules
Marked as fixed in versions prelude-lml/4.1.0-2.
> thanks
Stopping processing here.

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

Processed: severity of 903828 is grave

[Debian Bug Tracking System]

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

> severity 903828 grave
Bug #903828 [src:accountsservice] accountsservice: CVE-2018-14036: insufficient 
path check in user_change_icon_file_authorized_cb() in user.c
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#923465: freecad: it does not start. No module named StartGui

[Luis Llana]

Package: freecad
Version: 0.18~pre1+dfsg1-4
Severity: grave

Dear Maintainer,
  I have been using freecad for several months. Today, after upgrading
the system, it has stop working. I get the following message on the
terminal:

~$ freecad
FreeCAD 0.18, Libs: 0.18R
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2019
  #   ###   
  ##  # #   #   #
  # ##     # #   #  #   #
    # # #  # #  #  # #  #   #
  # #      ## # #   #
  # #   ## ## # #   #  ##  ##  ##
  # #       ### # #    ##  ##  ##

No module named StartGui
Traceback (most recent call last):
  File "", line 43, in Initialize

A Window with just the basic menu for exiting appear.


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

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

Versions of packages freecad depends on:
ii  freecad-python2  0.18~pre1+dfsg1-4

Versions of packages freecad recommends:
ii  calculix-ccx  2.11-1+b3
ii  graphviz  2.40.1-5+b2

Versions of packages freecad suggests:
pn  freecad-doc 
ii  povray  1:3.7.0.8-1
ii  python-collada  0.4-3

-- no debconf information


-- 
IPad, IPod, IPhone: IBad for your freedom.

Processed: Re: /usrr/bin/dune and `dune' binary package should refer to dune-common

[Debian Bug Tracking System]

Processing control commands:

> found 919953 1.0~beta20-1
Bug #919953 [dune] /usr/bin/dune and `dune' binary package should refer to 
dune-common
Marked as found in versions dune/1.0~beta20-1.
> severity 919953 important
Bug #919953 [dune] /usr/bin/dune and `dune' binary package should refer to 
dune-common
Severity set to 'important' from 'serious'

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

Bug#919953: /usrr/bin/dune and `dune' binary package should refer to dune-common

[Paul Gevers]

Control: found 919953 1.0~beta20-1
Control: severity 919953 important

On Sun, 20 Jan 2019 22:19:01 + Ian Jackson
 wrote:
> According to Debian policy file conflicts should be resolved by no-one
> using the conflicting name.  This applies to /usr/bin/dune.
> 
> Additionally, the only referent of `dune' that anyone has heard of
> (eg, wikipedia) is a C++ library which we have in Debian as
> `src:dune-commmon', `libdune*-dev', etc.
> 
> It is evident from actions taken in response to #916468 that the you
> (the maintainers of what is current `src:dune') do not agree.
> 
> Instead, it seems to me that you ahead and took the name despite a
> fairly clear consensus in debian-devel that you shouldn't.  I don't
> think you should have done that.
> 
> I am escalating this to the Technical Commitee in another bug.  In the
> meantime this bug needs to be open to keep this out of testing.

That TC bug got closed without the need for a resolution from the TC.
Hence, I don't consider this bug to qualify as RC anymore. (I personally
wouldn't mind if the *package* dune got renamed, but we shouldn't do
that before the buster release.)

Paul



signature.asc
Description: OpenPGP digital signature

Bug#917491: marked as done (debian-installer-netboot-images: FTBFS (BAD signature from "Debian Archive Automatic Signing Key (8/jessie) "))

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 14:12:14 +
with message-id 
and subject line Bug#917491: fixed in debian-installer-netboot-images 20190118
has caused the Debian Bug report #917491,
regarding debian-installer-netboot-images: FTBFS (BAD signature from "Debian 
Archive Automatic Signing Key (8/jessie) ")
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.)


-- 
917491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:debian-installer-netboot-images
Version: 20170615+deb9u5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   debian/rules override_dh_auto_install
make[1]: Entering directory 
'/<>/debian-installer-netboot-images-20170615+deb9u5'
if ! ./get-images.sh amd64 && [ -n "stretch" ]; then\
echo; echo; echo; \
echo "Version not found in stretch-proposed-updates, falling back to 
stretch"; \
echo; echo; echo; \
sleep 5; \

[... snipped ...]




--2018-12-20 03:03:08--  http://deb.debian.org/debian/dists/stretch/Release.gpg
Resolving deb.debian.org (deb.debian.org)... 149.20.4.15, 130.89.148.14, 
128.31.0.62, ...
Connecting to deb.debian.org (deb.debian.org)|149.20.4.15|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://cdn-fastly.deb.debian.org/debian/dists/stretch/Release.gpg 
[following]
--2018-12-20 03:03:08--  
http://cdn-fastly.deb.debian.org/debian/dists/stretch/Release.gpg
Resolving cdn-fastly.deb.debian.org (cdn-fastly.deb.debian.org)... 
151.101.120.204, 2a04:4e42:1d::204
Connecting to cdn-fastly.deb.debian.org 
(cdn-fastly.deb.debian.org)|151.101.120.204|:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 2434 (2.4K), 833 remaining
Saving to: 
'/<>/debian-installer-netboot-images-20170615+deb9u5/Release.gpg'

 0K ,.100% 44.9M=0s

2018-12-20 03:03:08 (44.9 MB/s) - 
'/<>/debian-installer-netboot-images-20170615+deb9u5/Release.gpg' 
saved [2434/2434]

--2018-12-20 03:03:08--  http://deb.debian.org/debian/dists/stretch/Release
Resolving deb.debian.org (deb.debian.org)... 149.20.4.15, 130.89.148.14, 
128.31.0.62, ...
Connecting to deb.debian.org (deb.debian.org)|149.20.4.15|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://cdn-fastly.deb.debian.org/debian/dists/stretch/Release 
[following]
--2018-12-20 03:03:08--  
http://cdn-fastly.deb.debian.org/debian/dists/stretch/Release
Resolving cdn-fastly.deb.debian.org (cdn-fastly.deb.debian.org)... 
151.101.120.204, 2a04:4e42:1d::204
Connecting to cdn-fastly.deb.debian.org 
(cdn-fastly.deb.debian.org)|151.101.120.204|:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 117946 (115K), 23339 (23K) remaining
Saving to: 
'/<>/debian-installer-netboot-images-20170615+deb9u5/Release'

[ skipping 50K ]
50K ,, ,, ,, ,, ,, 86% 2.13G 0s
   100K .. .  100% 16.8M=0.001s

2018-12-20 03:03:08 (24.6 MB/s) - 
'/<>/debian-installer-netboot-images-20170615+deb9u5/Release' saved 
[117946/117946]

gpgv: Signature made Wed Dec 19 20:22:50 2018 UTC
gpgv:using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553
gpgv: Can't check signature: No public key
gpgv: Signature made Wed Dec 19 20:22:50 2018 UTC
gpgv:using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010
gpgv: BAD signature from "Debian Archive Automatic Signing Key (8/jessie) 
"
make[1]: *** [debian/rules:20: get-images-amd64] Error 1
make[1]: Leaving directory 
'/<>/debian-installer-netboot-images-20170615+deb9u5'
make: *** [debian/rules:15: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-installer-netboot-images.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still 

Bug#919247: marked as done (kthresher: cronjob exits with error after package removal)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 13:49:46 +
with message-id 
and subject line Bug#919247: fixed in kthresher 1.4.0-1
has caused the Debian Bug report #919247,
regarding kthresher: cronjob exits with error after package removal
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.)


-- 
919247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kthresher
Version: 1.3.1-2
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your packages cronjob exits with
error after the package has been removed.

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

0m28.1s INFO: Package kthresher contains cron file: /etc/cron.daily/kthresher
0m28.1s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpTGHRnl', 
'/etc/cron.daily/kthresher']
0m28.1s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts/tmp/tmpTGHRnl', '/etc/cron.daily/kthresher']


cheers,

Andreas


kthresher_1.3.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kthresher
Source-Version: 1.4.0-1

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

Debian distribution maintenance software
pp.
Darshaka Pathirana  (supplier of updated kthresher package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 22 Feb 2019 02:07:33 +0100
Source: kthresher
Binary: kthresher
Architecture: source all
Version: 1.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Darshaka Pathirana 
Changed-By: Darshaka Pathirana 
Description:
 kthresher  - Purge Unused Kernels
Closes: 919247 919457
Changes:
 kthresher (1.4.0-1) unstable; urgency=medium
 .
   * [a2d803c] New upstream version 1.4.0 (Closes: #919457)
   * [599b193] Update debian/watch file
   * [2a226fe] Fix "cronjob exits with error after package removal"
 Thanks to Andreas Beckmann  for the bug report
 (Closes: #919247)
   * [a4507d4] Update dependencies to use Python3 and pybuild buildsystem
Checksums-Sha1:
 c1fe3f7b317a5a27e8e681bdd81f449687de9c58 1932 kthresher_1.4.0-1.dsc
 32043ed07c276b5d42865637f8c09a2233fbd0a8 17027 kthresher_1.4.0.orig.tar.gz
 8ef9a49dab051158fc874e8be10285a75c837632 2680 kthresher_1.4.0-1.debian.tar.xz
 427cb5ef6ac820418a8c3b8f074302fd112c85c4 16796 kthresher_1.4.0-1_all.deb
 59c7556b2fc52b58250fa818fd3a9a65f84cbf16 5957 kthresher_1.4.0-1_amd64.buildinfo
Checksums-Sha256:
 d6bc6d4954e750ccb211aaa6be8a55fd7750986db5c59f42ba7edd530dbf077d 1932 
kthresher_1.4.0-1.dsc
 9bba19a8466daf4437b1ff2d285b2177b82b6c7673ae108d0e121c333963e818 17027 
kthresher_1.4.0.orig.tar.gz
 9b1f17c0420944c95c783adacdcd5c70c5b1d8a23c4b3c2a5f998da8a019519d 2680 
kthresher_1.4.0-1.debian.tar.xz
 f47f3b2b589300bb3da991ad1338c97aff1994e9073d1c04d2b8c30b41315933 16796 
kthresher_1.4.0-1_all.deb
 47aa422dc564db46c7ace93abe36f083b1eaea34e87c1bc4fdee893402b38b95 5957 
kthresher_1.4.0-1_amd64.buildinfo
Files:
 c8bcbc6d7a53616d4037816d9cb00cd7 1932 admin optional kthresher_1.4.0-1.dsc
 dbfc0a9763ff2e2e38d076ad1796bf9b 17027 admin optional 
kthresher_1.4.0.orig.tar.gz
 52928d774cce39796dfc7f894dd0c11c 2680 admin optional 
kthresher_1.4.0-1.debian.tar.xz
 64ab4835b3405e973d0e28f64c411f4f 16796 admin optional kthresher_1.4.0-1_all.deb
 9f3d4620ca308cf0eed17211efecbe9d 5957 admin optional 
kthresher_1.4.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEM8yxNkAa/shDo4djlqh4crfqNzcFAlx34cAACgkQlqh4crfq
Nze4/Q/9EV8jIskqlG0ZhY5hd4N2kX56Z87DdVbiSdfOOP+K9yD4ZbEDuFrZaU75
kEwKPcVjjIllDrczFyc9bk2HDMaLy0LD8U61Az7CCt+gUXdfe9DLN9VRkuRQN2d6
Vlmpxi00C9XoudyZKtBy5hZVzg+V5N1RrFrhRaHpONxzvLfwbfGfMUAb5ANH4KAI
qWQugxyIZZz1hgnn1XWOMdPw7pzy3ccwF64pmPcnpX3z9r30J0+d5vAjmg1M+OEY
xZpMwPlLDQm5zdrkTHgurAa8bB/UzUMxIFYJa4Oz6YPjD1jgZZZB/KPysZqokCGM
tQ6W5NP6Ad1h064Pzeq8wLqIzPyQSOrOfa3yB1AnnyTKhbyiOkEzWCRh05q27e4u
XDGZXPyZAk9LzOyrKcsggR0qv6ZfnpnxjEbFIDBMTETz8xhvSamnCS7VIUcZkAK+
Ka31aWSyWG/zsJlxzcsYNzF9xGHqj/nKPiU8JlO4hxZAuubi7x1P0NGvGMY1ngXj

Bug#923457: libbpp-phyl: FTBFS (dh_makeshlibs fails)

[Santiago Vila]

> The build was made in my autobuilder with "dpkg-buildpackage -A"

Sorry, I meant "dpkg-buildpackage -B" here, as the package does not
create any arch-indep packages.

Thanks.

Bug#923456: llvm-toolchain-7: clang(|++-$VERSION) segfault in two autopkgtests

[Sylvestre Ledru]

Hello

Le 28/02/2019 à 13:38, Paul Gevers a écrit :

Source: llvm-toolchain-7
Version: 1:7.0.1-7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of llvm-toolchain-7 the autopkgtest of
llvm-toolchain-7 and clazy fail in testing when that autopkgtest is run


Yeah, I know what is wrong. sorry about that.

I will upload -8 later today.

Thanks for the bug report

S

Bug#923457: libbpp-phyl: FTBFS (dh_makeshlibs fails)

[Santiago Vila]

Package: src:libbpp-phyl
Version: 2.4.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info

[... snipped ...]

  _ZTTN3bpp9LLG08_UL3E@Base 2.4.1
  _ZTTN3bpp9RE08CodonE@Base 2.4.1
  _ZTVN3bpp10BppBooleanE@Base 2.4.1
- _ZTVN3bpp11IOExceptionE@Base 2.4.1
+#MISSING: 2.4.1-1# _ZTVN3bpp11IOExceptionE@Base 2.4.1
  _ZTVN3bpp11LG10_EX_EHO13EmbeddedModelE@Base 2.4.1
  _ZTVN3bpp11LG10_EX_EHOE@Base 2.4.1
  _ZTVN3bpp11NaNListenerE@Base 2.4.1
@@ -6100,7 +6133,7 @@
  _ZTVN3bpp23IODistanceMatrixFactoryE@Base 2.4.1
  _ZTVN3bpp23IOFrequenciesSetFactoryE@Base 2.4.1
  _ZTVN3bpp23MarkovModulatedStateMapE@Base 2.4.1
- _ZTVN3bpp23NotImplementedExceptionE@Base 2.4.1
+#MISSING: 2.4.1-1# _ZTVN3bpp23NotImplementedExceptionE@Base 2.4.1
  _ZTVN3bpp24BppOFrequenciesSetFormatE@Base 2.4.1
  _ZTVN3bpp24CladogramDrawBranchEventE@Base 2.4.1
  _ZTVN3bpp24ConstantRateDistributionE@Base 2.4.1
@@ -6117,12 +6150,12 @@
  _ZTVN3bpp24TripletSubstitutionModelE@Base 2.4.1
  _ZTVN3bpp24TsTvSubstitutionRegisterE@Base 2.4.1
  _ZTVN3bpp25AbstractSubstitutionModelE@Base 2.4.1
- _ZTVN3bpp25AlphabetMismatchExceptionE@Base 2.4.1
+#MISSING: 2.4.1-1# _ZTVN3bpp25AlphabetMismatchExceptionE@Base 2.4.1
  _ZTVN3bpp25BppOMultiTreeReaderFormatE@Base 2.4.1
  _ZTVN3bpp25BppOMultiTreeWriterFormatE@Base 2.4.1
  _ZTVN3bpp25BppOTransitionModelFormatE@Base 2.4.1
  _ZTVN3bpp25FullProteinFrequenciesSetE@Base 2.4.1
- _ZTVN3bpp25IndexOutOfBoundsExceptionE@Base 2.4.1
+#MISSING: 2.4.1-1# _ZTVN3bpp25IndexOutOfBoundsExceptionE@Base 2.4.1
  _ZTVN3bpp25MixedSubstitutionModelSetE@Base 2.4.1
  _ZTVN3bpp25PropertyNotFoundExceptionE@Base 2.4.1
  _ZTVN3bpp25SequenceNotFoundExceptionE@Base 2.4.1
@@ -8891,6 +8924,7 @@
  _ZTv0_n416_NK3bpp20AbstractWrappedModel17getFrequenciesSetEv@Base 2.4.1
  _ZTv0_n416_NK3bpp20ConstantDistribution13getUpperBoundEv@Base 2.4.1
  _ZTv0_n416_NK3bpp22AbstractTreeLikelihood16getNumberOfSitesEv@Base 2.4.1
+ _ZTv0_n416_NK3bpp24AlignedSequenceContainer16getNumberOfSitesEv@Base 2.4.1-1
  _ZTv0_n416_NK3bpp24OneChangeTransitionModel17getFrequenciesSetEv@Base 2.4.1
  _ZTv0_n416_NK3bpp27CodonAdHocSubstitutionModel17getFrequenciesSetEv@Base 2.4.1
  _ZTv0_n416_NK3bpp28AbstractDiscreteDistribution13getUpperBoundEv@Base 2.4.1
dh_makeshlibs: failing due to earlier errors
make[1]: *** [debian/rules:15: override_dh_makeshlibs] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#923456: llvm-toolchain-7: clang(|++-$VERSION) segfault in two autopkgtests

[Paul Gevers]

Source: llvm-toolchain-7
Version: 1:7.0.1-7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of llvm-toolchain-7 the autopkgtest of
llvm-toolchain-7 and clazy fail in testing when that autopkgtest is run
with the binary packages of llvm-toolchain-7 from unstable. It passes
when run with only packages from testing. In tabular form:
   passfail
llvm-toolchain-7   from testing1:7.0.1-7
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. Both tests
fail due to a segfault.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? If needed, please
change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
llvm-toolchain-7/1:7.0.1-7. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=llvm-toolchain-7

https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-7/2026142/log.gz

clang++-$VERSION -c -o part1.o foo.cpp $FLAGS
if test -f /usr/bin/g++; then
g++ -c -o part2.o -DPART2 foo.cpp $FLAGS
clang++-$VERSION -o foo part1.o part2.o $FLAGS
./foo
fi
./debian/qualify-clang.sh: line 383:  2823 Segmentation fault  ./foo


https://ci.debian.net/data/autopkgtest/testing/amd64/c/clazy/2026133/log.gz

Stack dump:
0.  Program arguments: /usr/lib/llvm-7/bin/clang -cc1 -triple
x86_64-pc-linux-gnu -emit-obj -mrelax-all -disable-free
-disable-llvm-verifier -discard-value-names -main-file-name main.cpp
-mrelocation-model pic -pic-level 2 -mthread-model posix
-mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases
-munwind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info
-debugger-tuning=gdb -coverage-notes-file
/tmp/autopkgtest-lxc.5k_mxe4a/downtmp/build.dOH/src/tests/main.gcno
-resource-dir /usr/lib/llvm-7/lib/clang/7.0.1 -isystem
/usr/include/x86_64-linux-gnu/qt5 -internal-isystem
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8
-internal-isystem
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/x86_64-linux-gnu/c++/8
-internal-isystem
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/x86_64-linux-gnu/c++/8
-internal-isystem
/usr/bin/../lib/gcc/x86_64-linux-gnu/8/../../../../include/c++/8/backward
-internal-isystem /usr/include/clang/7.0.1/include/ -internal-isystem
/usr/local/include -internal-isystem
/usr/lib/llvm-7/lib/clang/7.0.1/include -internal-externc-isystem
/usr/include/x86_64-linux-gnu -internal-externc-isystem /include
-internal-externc-isystem /usr/include -Wno-unused-value -std=c++14
-fdeprecated-macro -fdebug-compilation-dir
/tmp/autopkgtest-lxc.5k_mxe4a/downtmp/build.dOH/src/tests -ferror-limit
19 -fmessage-length 0 -fobjc-runtime=gcc -fcxx-exceptions -fexceptions
-fdiagnostics-show-option -load ClazyPlugin.so -add-plugin clazy
-plugin-arg-clazy no-inplace-fixits -plugin-arg-clazy
assert-with-side-effects -plugin-arg-clazy enable-all-fixits -o main.o
-x c++ assert-with-side-effects/main.cpp -faddrsig
1.   parser at end of file
/usr/lib/x86_64-linux-gnu/libLLVM-7.so.1(_ZN4llvm3sys15PrintStackTraceERNS_11raw_ostreamE+0x1f)[0x7f5f102505df]
/usr/lib/x86_64-linux-gnu/libLLVM-7.so.1(_ZN4llvm3sys17RunSignalHandlersEv+0x50)[0x7f5f1024eb40]
/usr/lib/x86_64-linux-gnu/libLLVM-7.so.1(+0x9ce8f2)[0x7f5f102508f2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x126e0)[0x7f5f1328e6e0]
/usr/lib/llvm-7/bin/clang[0x188b720]
/usr/lib/llvm-7/bin/clang(_ZN5clang12ast_matchers11MatchFinder8matchASTERNS_10ASTContextE+0x495)[0x188bce5]
/usr/lib/llvm-7/bin/clang(_ZN5clang17MultiplexConsumer21HandleTranslationUnitERNS_10ASTContextE+0x2c)[0xb06aec]
/usr/lib/llvm-7/bin/clang(_ZN5clang8ParseASTERNS_4SemaEbb+0x215)[0x10ba705]
/usr/lib/llvm-7/bin/clang(_ZN5clang14FrontendAction7ExecuteEv+0x3f)[0xad45cf]
/usr/lib/llvm-7/bin/clang(_ZN5clang16CompilerInstance13ExecuteActionERNS_14FrontendActionE+0x4f8)[0xa95b98]
/usr/lib/llvm-7/bin/clang(_ZN5clang25ExecuteCompilerInvocationEPNS_16CompilerInstanceE+0x676)[0xb62936]
/usr/lib/llvm-7/bin/clang(_Z8cc1_mainN4llvm8ArrayRefIPKcEES2_Pv+0x5b4)[0x6aa014]
/usr/lib/llvm-7/bin/clang(main+0x2727)[0x6a84b7]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f5f0f3c409b]
/usr/lib/llvm-7/bin/clang(_start+0x2a)[0x6a5ada]
clang: error: unable to execute command: Segmentation fault
clang: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 7.0.1-7 (tags/RELEASE_701/final)
Target: 

Bug#923454: renderdoc: FTBFS (error: braces around scalar initializer for type 'int')

[Santiago Vila]

Package: src:renderdoc
Version: 1.2+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch --buildsystem cmake
   dh_update_autotools_config -a -O--buildsystem=cmake
   dh_autoreconf -a -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/renderdoc-1.2+dfsg'
dh_auto_configure -- \
-DBUILD_VERSION_STABLE=true \
-DBUILD_VERSION_DIST_NAME=Debian \
-DBUILD_VERSION_DIST_VER=1.2+dfsg-1 \

-DBUILD_VERSION_DIST_CONTACT="https://salsa.debian.org/xorg-team/app/renderdoc; 
\
-DVULKAN_LAYER_FOLDER=/usr/share/vulkan/implicit_layer.d \
-DRENDERDOC_SWIG_PACKAGE=/<>/renderdoc-1.2+dfsg/swig \
-DCMAKE_BINARY_DIR=/<>/renderdoc-1.2+dfsg/debian/tmp \

[... snipped ...]

[ 61%] Building CXX object 
renderdoc/driver/vulkan/CMakeFiles/rdoc_vulkan.dir/wrappers/vk_get_funcs.cpp.o
cd 
/<>/renderdoc-1.2+dfsg/obj-x86_64-linux-gnu/renderdoc/driver/vulkan 
&& /usr/bin/c++  
-DDISTRIBUTION_CONTACT=\"https://salsa.debian.org/xorg-team/app/renderdoc\; 
-DDISTRIBUTION_NAME=\"Debian\" -DDISTRIBUTION_VERSION=\"1.2+dfsg-1\" 
-DGIT_COMMIT_HASH=\"NO_GIT_COMMIT_HASH_DEFINED\" -DRENDERDOC_EXPORTS 
-DRENDERDOC_PLATFORM_LINUX -DRENDERDOC_STABLE_BUILD=1 -DRENDERDOC_SUPPORT_GL 
-DRENDERDOC_SUPPORT_GLES -DRENDERDOC_SUPPORT_VULKAN -DRENDERDOC_WINDOWING_XCB 
-DRENDERDOC_WINDOWING_XLIB -DVK_USE_PLATFORM_XCB_KHR -DVK_USE_PLATFORM_XLIB_KHR 
-DVK_USE_PLATFORM_XLIB_XRANDR_EXT -D_RELEASE 
-I/<>/renderdoc-1.2+dfsg/renderdoc 
-I/<>/renderdoc-1.2+dfsg/renderdoc/3rdparty  -g -O2 
-fdebug-prefix-map=/<>/renderdoc-1.2+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-fstrict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra 
-Wno-unused-variable -Wno-unused-parameter -Wno-unused-result -W
 no-type-limits -Wno-missing-field-initializers -Wno-unknown-pragmas 
-Wno-reorder -Wno-unused-but-set-variable -Wno-maybe-uninitialized 
-Wno-class-memaccess -Wimplicit-fallthrough=2 -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/rdoc_vulkan.dir/wrappers/vk_get_funcs.cpp.o -c 
/<>/renderdoc-1.2+dfsg/renderdoc/driver/vulkan/wrappers/vk_get_funcs.cpp
[ 61%] Building CXX object 
renderdoc/driver/vulkan/CMakeFiles/rdoc_vulkan.dir/wrappers/vk_misc_funcs.cpp.o
cd 
/<>/renderdoc-1.2+dfsg/obj-x86_64-linux-gnu/renderdoc/driver/vulkan 
&& /usr/bin/c++  
-DDISTRIBUTION_CONTACT=\"https://salsa.debian.org/xorg-team/app/renderdoc\; 
-DDISTRIBUTION_NAME=\"Debian\" -DDISTRIBUTION_VERSION=\"1.2+dfsg-1\" 
-DGIT_COMMIT_HASH=\"NO_GIT_COMMIT_HASH_DEFINED\" -DRENDERDOC_EXPORTS 
-DRENDERDOC_PLATFORM_LINUX -DRENDERDOC_STABLE_BUILD=1 -DRENDERDOC_SUPPORT_GL 
-DRENDERDOC_SUPPORT_GLES -DRENDERDOC_SUPPORT_VULKAN -DRENDERDOC_WINDOWING_XCB 
-DRENDERDOC_WINDOWING_XLIB -DVK_USE_PLATFORM_XCB_KHR -DVK_USE_PLATFORM_XLIB_KHR 
-DVK_USE_PLATFORM_XLIB_XRANDR_EXT -D_RELEASE 
-I/<>/renderdoc-1.2+dfsg/renderdoc 
-I/<>/renderdoc-1.2+dfsg/renderdoc/3rdparty  -g -O2 
-fdebug-prefix-map=/<>/renderdoc-1.2+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-fstrict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra 
-Wno-unused-variable -Wno-unused-parameter -Wno-unused-result -W
 no-type-limits -Wno-missing-field-initializers -Wno-unknown-pragmas 
-Wno-reorder -Wno-unused-but-set-variable -Wno-maybe-uninitialized 
-Wno-class-memaccess -Wimplicit-fallthrough=2 -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/rdoc_vulkan.dir/wrappers/vk_misc_funcs.cpp.o -c 
/<>/renderdoc-1.2+dfsg/renderdoc/driver/vulkan/wrappers/vk_misc_funcs.cpp
[ 61%] Building CXX object 
renderdoc/driver/vulkan/CMakeFiles/rdoc_vulkan.dir/wrappers/vk_queue_funcs.cpp.o
cd 
/<>/renderdoc-1.2+dfsg/obj-x86_64-linux-gnu/renderdoc/driver/vulkan 
&& /usr/bin/c++  
-DDISTRIBUTION_CONTACT=\"https://salsa.debian.org/xorg-team/app/renderdoc\; 
-DDISTRIBUTION_NAME=\"Debian\" -DDISTRIBUTION_VERSION=\"1.2+dfsg-1\" 
-DGIT_COMMIT_HASH=\"NO_GIT_COMMIT_HASH_DEFINED\" -DRENDERDOC_EXPORTS 
-DRENDERDOC_PLATFORM_LINUX -DRENDERDOC_STABLE_BUILD=1 -DRENDERDOC_SUPPORT_GL 
-DRENDERDOC_SUPPORT_GLES -DRENDERDOC_SUPPORT_VULKAN -DRENDERDOC_WINDOWING_XCB 
-DRENDERDOC_WINDOWING_XLIB -DVK_USE_PLATFORM_XCB_KHR -DVK_USE_PLATFORM_XLIB_KHR 
-DVK_USE_PLATFORM_XLIB_XRANDR_EXT -D_RELEASE 
-I/<>/renderdoc-1.2+dfsg/renderdoc 
-I/<>/renderdoc-1.2+dfsg/renderdoc/3rdparty  -g -O2 
-fdebug-prefix-map=/<>/renderdoc-1.2+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-fstrict-aliasing -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Wextra 
-Wno-unused-variable -Wno-unused-parameter -Wno-unused-result -W
 no-type-limits -Wno-missing-field-initializers -Wno-unknown-pragmas 
-Wno-reorder -Wno-unused-but-set-variable 

Bug#923453: metview: FTBFS (Fatal Error: Can't open module file 'grib_api.mod' for reading at (1): No such file or directory)

[Santiago Vila]

Package: src:metview
Version: 5.3.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake 
--builddirectory=/<>/debian/build 
   dh_update_autotools_config -i -O--buildsystem=cmake 
-O--builddirectory=/<>/debian/build
   dh_autoreconf -i -O--buildsystem=cmake 
-O--builddirectory=/<>/debian/build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
chmod +x ./scripts/*.mv
# Hack. how to do this via ecbuild?
cp scripts/metview_base.in scripts/metview_base.in.bak
sed -e 's%@DEB_HOST_MULTIARCH@%x86_64-linux-gnu%g' < scripts/metview_base.in \
> scripts/tmpx && mv scripts/tmpx scripts/metview_base.in
dh_auto_configure -- \
-DMETVIEW_SITE=debian  \
-DCMAKE_BUILD_TYPE=Release \

[... snipped ...]

cd /<>/debian/build/src/libMars && /usr/bin/cc 
-DGRIB_HANDLING_PACKAGE=ecCodes -DH_INCLUDES_CC -DLITTLE_END -DMETVIEW 
-DMETVIEW_ODB -DMETVIEW_ODB_NEW -DMETVIEW_ODB_OLD -DMETVIEW_ODB_PLOT 
-DMETVIEW_QT5 -DMvMars_EXPORTS -DNOFDB -DNOFDB5 -DODB_ECKIT -DODB_SUPPORT 
-DQT_NO_DEBUG_OUTPUT -DR64 -DUSE_NEW_IO -I/<>/src/Odb 
-I/<>/src/libFTimeUtil -I/<>/src 
-I/<>/debian/build/src/libMars -I/<>/src/libMars 
-I/<>/src/libMarsClient -I/<>/src/libMetview 
-I/<>/debian/build/module -I/usr/include/python3.7m/odblib 
-I/usr/include/openjpeg-2.1 -I/usr/lib/python3/dist-packages/numpy/core/include 
-I/usr/lib/include -I/build/odb-api/debian/build/metkit/src 
-I/build/odb-api/metkit/src -I/usr/include/x86_64-linux-gnu 
-I/usr/include/eigen3 -I/build/odb-api/debian/build/eckit/src 
-I/build/odb-api/eckit/src -I/usr/include/python3.7m/../eclib/eclib 
-I/usr/include/python3.7m/../eclib -I/usr/include/
 python3.7m/.. -I/usr/include/python3.7m -I/usr/include/hdf5/serial 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ 
-I/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport 
-I/usr/include/x86_64-linux-gnu/qt5/QtSvg  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wall -pedantic 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG -fPIC   -o 
CMakeFiles/MvMars.dir/mars_client_version.c.o   -c 
/<>/debian/build/src/libMars/mars_client_version.c
[  5%] Linking CXX shared library ../../lib/libMvMars.so
cd /<>/debian/build/src/libMars && /usr/bin/cmake -E remove 
/<>/debian/build/lib/libMvMars.so.0.0.0
cd /<>/debian/build/src/libMars && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/MvMars.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -std=c++11 -Wdate-time -D_FORTIFY_SOURCE=2 -pipe 
-std=c++11 -fpermissive -Wno-write-strings -Wno-deprecated -O3 -DNDEBUG 
-Wl,-z,relro -Wl,-z,now -Wl,--disable-new-dtags -shared 
-Wl,-soname,libMvMars.so.0d -o ../../lib/libMvMars.so.0.0.0 
CMakeFiles/MvMars.dir/__/libMarsClient/tcp.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/server.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/request.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/expand.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/hash.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/memory.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/logfile.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/options.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/api.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/apibase.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/base.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/netbase.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/netcdf.c.o CMakeFiles/MvMars.dir/__/li
 bMarsClient/hdf5.c.o CMakeFiles/MvMars.dir/__/libMarsClient/nullbase.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/fdb5base.cc.o 
CMakeFiles/MvMars.dir/__/libMarsClient/forwardbase.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/gribbase.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/nfdbbase.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/dhsbase.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/odb.cc.o 
CMakeFiles/MvMars.dir/__/libMarsClient/odbbase.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/multibase.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/archive.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/retrieve.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/ibmblk.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/lock.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/files.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/sh2ll.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/guess.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/hypercube.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/check.c.o 
CMakeFiles/MvMars.dir/__/libMarsClient/environ.c.o CMakeFil
 es/MvMars.dir/__/libMarsClient/handler.c.o 

Bug#923238: libmarc-charset-perl: needs a rebuild on 32bit architectures?

[Dmitry Bogatov]

[2019-02-27 21:20] Niko Tyni 
> > - update perl to build-depend on libgdbm-dev (>= 1.18-2) and Break
> >   older versions of libmarc-charset-perl (and any other perl packages
> >   bundling GDBM or NDBM databases)
> > 
> > - update libmarc-charset-perl (and any other perl packages bundling
> >   GDBM or NDBM databases) to build-depend and depend on the newer perl
> > 
> > I assume other language bindings like python-gdbm will need something
> > similar.
>
> But ideally gdbm would restore compatibility and libmarc-charset-perl would
> not need any changes.

I believe upstream release 1.8.1 introduced change, that
made it possible to read old /usr/lib/libmarc-charset-perl/Table. Am I
missing something in current situation?

By the way, I disagree about compability. If all we need to make
everything good is just a binNMU, I'd rather not introduce any
patches/hacks/compatibility layers/etc.

By the way, it is sad that libmarc-charset-perl uses gdbm, not cdb.

-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --

Bug#910902: Please test again: resolveip and Akonadi for a freash installation

[Sandro Knauß]

Hey,

> Looks like this has never been in the core package:

I mentioned that, too. But I printend the command that fails:
/usr/bin/mysql_install_db --defaults-file= --force --basedir=/usr 
--datadir=/home/siducer/.local/share/akonadi/db_data/

I this command also fails with the same error (not finding resolveip) also 
outside Akonadi environment:
Thats a nearly perfect to use autopkgtest for this scenario:

mkdir diretcory
cd directory
/usr/bin/mysql_install_db --defaults-file= --force --basedir=/usr 
--datadir=db_data/

So IMO mysql_install_db now nowadays needs resolveip and in the past not.

> Moving the file requires some consideration for backwards
> compatibility etc. Would you like to take a look at this and try to
> come up with a solution?

Not really as I'm quite busy atm - Please do it, as you have more knowledge in 
that area - I also need to fix other pim related issues in Debian.

> See https://wiki.debian.org/Teams/MySQL/patches on how to use Salsa-CI
> to test and submit patches.

that's a nice one - I also want such stuff for KDE...

hefee

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

Bug#921732: hg-git: incompatible with mercurial 4.9

[Graham Inggs]

Hi Julien

This autopkgtest failure still prevents mercurial 4.9-2 from migrating 
to testing.


On 2019/02/18 14:08, Graham Inggs wrote:

Do you have any ideas on how to suppress the deprecation warnings?


I didn't figure out how to do this, but I patched them out of mercurial.
With this local build of mercurial, only three hg-git tests fail, and 
all with the same:


ProgrammingError: callcommand() cannot be used after commands are sent

Regards
Graham

Bug#923223: XML::Parser::parsefile() uses 2-argument open

[Xavier]

Le 27/02/2019 à 20:06, Niko Tyni a écrit :
> On Wed, Feb 27, 2019 at 05:16:03PM +0100, gregor herrmann wrote:
> 
>> 2) This fix would also suite the documentation of tv_imdb which says:
>>
>> tv_imdb --imdbdir  [--help] [--quiet]
>>[--with-keywords] [--with-plot]
>>[--movies-only] [--actors NUMBER]
>>[--stats] [--debug]
>>[--output FILE] [FILE...]
>>
>> (so: pass FILE as an argument, not: read from STDIN, as the testsuite
>> does)
> 
> The convention in manual pages is that optional arguments are denoted with
> brackets. My expections from just the above synopsis would be precisely
> the old behaviour (which the test suite apparently relies on): FILE is
> optional and STDIN is used if FILE is not supplied.
> 
>> So it seems that XML::Parser's parsefile was able to handle '-' with
>> the 2-args-open() and fails to do so with the 3-args-open(). This is
>> a regression at first glance; although the documentation for open()
>> only mentions "<-" or "-" for STDIN in the (one-args- and)
>> two-args-form. But yeah, this has the potential to break more code
>> out there …
> 
> Not sure I follow but I agree with the last sentence at least :)
> Clearly '-' needs special handling in XML::Parser if 2-arg open is
> converted to 3-arg open.
> 
> (Sorry, no tuits for providing a better patch for XML::Parser.)

Patch is ready in salsa repo:

if (ref $file or $file eq '-') {
  open(FILE, $file) or  croak "Couldn't open $file:\n$!";
} else {
  open(FILE, '<', $file) or  croak "Couldn't open $file:\n$!";
}

Successfully tested with xmltv. I propose to push as this for now to
close bug before freeze. This patch fixes security bug since strange
filename are no more interpreted and autopkgtest regression is fixed.

Cheers,
Xavier

Processed: Reassign

[Debian Bug Tracking System]

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

> notfound 918632 simplejson/3.16.0-1
Bug #918632 [src:simplejson, src:json-schema-validator] simplejson breaks 
json-schema-validator autopkgtest
No longer marked as found in versions simplejson/3.16.0-1.
> reassign 918632 json-schema-validator
Bug #918632 [src:simplejson, src:json-schema-validator] simplejson breaks 
json-schema-validator autopkgtest
Bug reassigned from package 'src:simplejson, src:json-schema-validator' to 
'json-schema-validator'.
No longer marked as found in versions json-schema-validator/2.3.1-3.
Ignoring request to alter fixed versions of bug #918632 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#918632: Reassign

[Neil Williams]

notfound 918632 simplejson/3.16.0-1
reassign 918632 json-schema-validator
thanks

I'll seek removal of the orphaned json-schema-validator source package
in due course.

-- 

Neil Williams
h...@codehelp.co.uk



pgpgTCIPlpcle.pgp
Description: OpenPGP digital signature

Bug#923402: marked as done (mu-editor: FTBFS with python3-pkg-resources 40.8.0: TypeError: expected str, bytes or os.PathLike object, not Win)

[Debian Bug Tracking System]

Your message dated Thu, 28 Feb 2019 10:19:56 +
with message-id 
and subject line Bug#923402: fixed in mu-editor 1.0.2+dfsg-2
has caused the Debian Bug report #923402,
regarding mu-editor: FTBFS with python3-pkg-resources 40.8.0: TypeError: 
expected str, bytes or os.PathLike object, not Win
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.)


-- 
923402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mu-editor
Version: 1.0.2+dfsg-1
Severity: serious
Justification: fails to build from source
Tags: ftbfs

Dear Maintainer,

As can be seen on [1], mu-editor fails to build with the latest version of
pkg_resources.

The error is:

Traceback (most recent call last):
  File 
"/tmp/mu-editor-1.0.2+dfsg/.pybuild/cpython3_3.7_mu-editor/build/tests/test_app.py",
 line 92, in test_run
run()
  File 
"/tmp/mu-editor-1.0.2+dfsg/.pybuild/cpython3_3.7_mu-editor/build/mu/app.py", 
line 142, in run
app.setWindowIcon(load_icon(editor_window.icon))
  File 
"/tmp/mu-editor-1.0.2+dfsg/.pybuild/cpython3_3.7_mu-editor/build/mu/resources/__init__.py",
 line 37, in load_icon
return QIcon(path(name))
  File 
"/tmp/mu-editor-1.0.2+dfsg/.pybuild/cpython3_3.7_mu-editor/build/mu/resources/__init__.py",
 line 32, in path
return resource_filename(__name__, resource_dir + name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1145, 
in resource_filename
self, resource_name
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1395, 
in get_resource_filename
return self._fn(self.module_path, resource_name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1471, 
in _fn
self._validate_resource_path(resource_name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1518, 
in _validate_resource_path
posixpath.isabs(path) or
  File "/usr/lib/python3.7/posixpath.py", line 66, in isabs
s = os.fspath(s)
TypeError: expected str, bytes or os.PathLike object, not Win

This is caused by addition of _validate_source_path() in pkg_resources 40.8.0,
see [2].

This upstream commit [3] should fix it.

[1]: 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mu-editor.html
[2]: https://github.com/pypa/setuptools/pull/1640
[3]: https://github.com/mu-editor/mu/commit/d38470adc623f887

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mu-editor
Source-Version: 1.0.2+dfsg-2

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

Debian distribution maintenance software
pp.
Nick Morrott  (supplier of updated mu-editor 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, 28 Feb 2019 02:43:16 +
Source: mu-editor
Architecture: source
Version: 1.0.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Nick Morrott 
Closes: 923402
Changes:
 mu-editor (1.0.2+dfsg-2) unstable; urgency=medium
 .
   * d/gbp.conf: use pristine-tar
   * d/patches: add test_app_icon_as_string (Closes: #923402)
Checksums-Sha1:
 9eef81159e75f23db5d34c9e06fa5910475f429f 2715 mu-editor_1.0.2+dfsg-2.dsc
 f31fba11a246c4b2fc7689e6833dd5d8dccabe01 10760 
mu-editor_1.0.2+dfsg-2.debian.tar.xz
 66e8294726b3339b9d6be962557cbc19b8a838ef 13231 
mu-editor_1.0.2+dfsg-2_source.buildinfo
Checksums-Sha256:
 335f002fe060f2a53a9512e47c9a664944cefeadea549f4910aab4595ea1feef 2715 
mu-editor_1.0.2+dfsg-2.dsc
 bd7052a18cfa7571ec654f623749334a71a05180569607cdad441d08e2bfe77e 10760 
mu-editor_1.0.2+dfsg-2.debian.tar.xz
 30f999abe29a8e148f3a12163a7f6caa92facb4a0dea17d90d7a4a1c2c2242c3 13231 
mu-editor_1.0.2+dfsg-2_source.buildinfo
Files:
 1d9cb90bd5108a2376150100b45c6395 2715 python optional 
mu-editor_1.0.2+dfsg-2.dsc
 9e9996aed7d33b9410f15307784a3bf0 10760 python optional 
mu-editor_1.0.2+dfsg-2.debian.tar.xz
 535ea6535405625b3cdefc19c094f4b0 13231 python optional 
mu-editor_1.0.2+dfsg-2_source.buildinfo

Bug#918632: simplejson breaks json-schema-validator autopkgtest

[Paul Gevers]

Hi all,

On 18-02-2019 23:04, Neil Williams wrote:
> Unless there are any relevant bug reports filed against simplejson or
> some other confirmation of the bug as being caused by simplejson within
> say a week to 10 days, I'll assign this just to json-schema-validator
> and seek removal of json-schema-validator from Debian as orphaned, out
> of date & RC buggy.

Anticipating that the above will happen today, I'll mark the regression
to be ignored by the migration software now. (The reassignment still
needs to happen to prevent simplejson to be marked as having an RC bug
in buster).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#923445: ghc: FTBFS (The 'ghc-flag' directive is already registered to domain std)

[Santiago Vila]

Package: src:ghc
Version: 8.4.4+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>/ghc-8.4.4+dfsg1'
dh_autoreconf perl -- boot
Creating libraries/ghc-prim/ghc.mk
Creating libraries/text/ghc.mk

[... snipped ...]

/usr/bin/sphinx-build -b html -d docs/users_guide/.doctrees-html -D 
latex_paper_size=letter docs/users_guide docs/users_guide/build-html/users_guide
Running Sphinx v1.8.4

Extension error:
The 'ghc-flag' directive is already registered to domain std
make[3]: *** [docs/users_guide/ghc.mk:16: 
docs/users_guide/build-html/users_guide/index.html] Error 2
make[2]: *** [Makefile:127: all] Error 2
make[2]: Leaving directory '/<>/ghc-8.4.4+dfsg1'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [debian/rules:132: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/ghc-8.4.4+dfsg1'
make: *** [debian/rules:58: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Processed: Re: gazebo: please don’t depend on the hinted Roboto fonts

[Debian Bug Tracking System]

Processing control commands:

> severity 922946 normal
Bug #922946 [gazebo] gazebo: please don’t depend on the hinted Roboto fonts
Severity set to 'normal' from 'serious'

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

Bug#922946: gazebo: please don’t depend on the hinted Roboto fonts

[Andrej Shadura]

Control: severity 922946 normal

On Thu, 28 Feb 2019 at 11:04, Santiago Vila  wrote:
> On Fri, 22 Feb 2019, Andrej Shadura wrote:
>
> > The Roboto upstream no longer provides hinted fonts, so
> > fonts-roboto-hinted is now a transitional package providing symlinks to
> > the unhinted fonts. Please modify your package to use the unhinted fonts
> > instead.
>
> The package now FTBFS on buster, for this very same reason I guess.
> This is what I got today:
>
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: *** No rule to make target 
> '/usr/share/fonts/truetype/roboto/hinted/Roboto-Black.ttf', needed by 
> 'gazebo/gui/qrc_resources.cpp'.  Stop.

Thanks. Turns out the compat symlinks were incorrect. The -3 upload of
fonts-roboto should fix that.

-- 
Cheers,
  Andrej

Bug#923442: octave: FTBFS (/bin/sed: can't read libinterp/parse-tree/oct-parse.cc-t: No such file or directory)

[Santiago Vila]

Package: src:octave
Version: 4.4.1-4
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'

[... snipped ...]

gawk -v emit_graphics_props=1 -f ./libinterp/corefcn/genprops.awk 
libinterp/corefcn/graphics.in.h > libinterp/corefcn/graphics-props.cc-t && \
mv libinterp/corefcn/graphics-props.cc-t libinterp/corefcn/graphics-props.cc
rm -f libinterp/corefcn/graphics.h-t && \
gawk -f ./libinterp/corefcn/genprops.awk libinterp/corefcn/graphics.in.h > 
libinterp/corefcn/graphics.h-t && \
mv libinterp/corefcn/graphics.h-t libinterp/corefcn/graphics.h
rm -f libinterp/corefcn/mxarray.h-t libinterp/corefcn/mxarray.h && /bin/bash 
libinterp/corefcn/mk-mxarray-h.sh < libinterp/corefcn/mxarray.in.h > 
libinterp/corefcn/mxarray.h-t && mv libinterp/corefcn/mxarray.h-t 
libinterp/corefcn/mxarray.h
case "" in *api*) case "" in *brace*) api_prefix_decl='%define api.prefix 
{octave_tex_}'; ;; *) api_prefix_decl='%define api.prefix "octave_tex_"'; ;; 
esac; ;; *name*) case "" in *brace*) api_prefix_decl='%name-prefix 
{octave_tex_}'; ;; *) api_prefix_decl='%name-prefix="octave_tex_"'; ;; esac; ;; 
esac; case "" in *quote*) quote='"' ;; *) quote="" ;; esac; case "" in *dash*) 
push_pull_decl="%define api.push-pull ${quote}both${quote}"; ;; *underscore*) 
push_pull_decl="%define api.push_pull ${quote}both${quote}"; ;; esac; /bin/sed 
-e "s/%PUSH_PULL_DECL%/$push_pull_decl/" -e 
"s/%API_PREFIX_DECL%/$api_prefix_decl/" libinterp/corefcn/oct-tex-parser.in.yy 
> libinterp/corefcn/oct-tex-parser.yy-t && mv 
libinterp/corefcn/oct-tex-parser.yy-t libinterp/corefcn/oct-tex-parser.yy
rm -f libinterp/corefcn/oct-tex-parser.cc-t 
libinterp/corefcn/oct-tex-parser.cc-tt && \
/bin/bash ./build-aux/ylwrap libinterp/corefcn/oct-tex-parser.yy y.tab.c 
libinterp/corefcn/oct-tex-parser.cc-t y.tab.h 
libinterp/corefcn/oct-tex-parser.h y.output 
libinterp/corefcn/oct-tex-parser.output -- ./build-aux/missing bison -dv  && \
/bin/sed 
's|"libinterp/corefcn/oct-tex-parser\.cc-t"|"libinterp/corefcn/oct-tex-parser.cc"|g'
 libinterp/corefcn/oct-tex-parser.cc-t > libinterp/corefcn/oct-tex-parser.cc-tt 
&& \
mv libinterp/corefcn/oct-tex-parser.cc-tt libinterp/corefcn/oct-tex-parser.cc-t 
&& \
  if [ -s libinterp/corefcn/oct-tex-parser.cc-t ]; then /bin/bash 
./build-aux/move-if-change libinterp/corefcn/oct-tex-parser.cc-t 
libinterp/corefcn/oct-tex-parser.cc; else echo 
"libinterp/corefcn/oct-tex-parser.cc-t is empty!" 1>&2; rm -f 
libinterp/corefcn/oct-tex-parser.cc-t; exit 1; fi
updating oct-tex-parser.output
updating oct-tex-parser.tab.cc
updating oct-tex-parser.tab.hh
/bin/sed: can't read libinterp/corefcn/oct-tex-parser.cc-t: No such file or 
directory
make[1]: *** [Makefile:30632: libinterp/corefcn/oct-tex-parser.h] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:48: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Processed: Re: gazebo: please don’t depend on the hinted Roboto fonts

[Debian Bug Tracking System]

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

> severity 922946 serious
Bug #922946 [gazebo] gazebo: please don’t depend on the hinted Roboto fonts
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#922741: Bug #922741 in grub2 marked as pending

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #922741 in grub2 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/grub-team/grub/commit/a4261650c1a446d8ef53a18b6e1fe9bd1097fc6a


util: Detect more I/O errors

Closes: #922741


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/922741

Processed: Bug #922741 in grub2 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #922741 [grub-efi] grub-efi: grub-install indicates "no errors" when 
there's insufficient disk space in EFI partition
Added tag(s) pending.

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