Bug#929618: marked as done (t-digest: latest-debian-changelog-entry-reuses-existing-version)

[Debian Bug Tracking System]

Your message dated Tue, 28 May 2019 05:18:28 +
with message-id 
and subject line Bug#929618: fixed in t-digest 1:3.0-2
has caused the Debian Bug report #929618,
regarding t-digest: latest-debian-changelog-entry-reuses-existing-version
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.)


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

W: libt-digest-java: latest-debian-changelog-entry-reuses-existing-version 
1:3.0-1 == 3.0-1 (last used: Tue, 14 Oct 2014 10:44:34 +0200)
N: 
N:The latest changelog entry has a version that matches one used in the
N:specified previous entry. All versions of a source package must be
N:unique even after a leading epoch has been stripped off.
N:
N:Files generated by the current version of this source package would
N:conflict with some historical files. This is because the Debian archive
N:does not allow multiple files with the same name and different contents
N:and the generated .dsc, .deb, etc. do not embed the epoch in their
N:filenames.
N:
N:Please pick another version, for example by increasing the Debian
N:revision.
N:
N:Severity: normal, Certainty: certain
N:
N:Check: changelog-file, Type: binary

Just bumping the version number to 1:3.0-2 should be safe.


Andreas

PS: I do not want to repeat https://bugs.debian.org/929614
--- End Message ---
--- Begin Message ---
Source: t-digest
Source-Version: 1:3.0-2

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated t-digest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 27 May 2019 21:23:15 -0700
Source: t-digest
Architecture: source
Version: 1:3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 929618
Changes:
 t-digest (1:3.0-2) unstable; urgency=medium
 .
   [ tony mancill ]
   * Bump debian revision to avoid reuse of 3.0-1 (Closes: #929618)
   * Update Vcs URLs to point to Salsa
   * Add a human maintainer (myself) to Uploaders
   * Drop get-orig-source target from debian/rules
   * Bump Standards-Version to 4.3.0
   * Use debhelper 12 and dh sequencer; drop cdbs build-dep
 .
   [ Hilko Bengen ]
   * Remove myself from Uploaders
Checksums-Sha1:
 0b663a9355d02a21aba1f8210f46edad3d874c83 2122 t-digest_3.0-2.dsc
 7f21a6ad5787de14fc6ba523d51e751856ad1a69 3196 t-digest_3.0-2.debian.tar.xz
 10ddae1e87ed03a88af9f0ac522145a649fd9f13 13664 t-digest_3.0-2_amd64.buildinfo
Checksums-Sha256:
 44ecbfe1bc5b566e55327c40fa8b6335dcaace0e13ebed6b059c4f33848420c6 2122 
t-digest_3.0-2.dsc
 bfdc56f78190c181138610160f44e00d7e0a29ad519dff686a06ed49ea187671 3196 
t-digest_3.0-2.debian.tar.xz
 50c47368fd7e96871b5a3608008823f6276538c3deebf60ae838eddf44ab9b29 13664 
t-digest_3.0-2_amd64.buildinfo
Files:
 777068173143ddbbc2fd20a2ae86de82 2122 java optional t-digest_3.0-2.dsc
 1de01215035ad5f0195696faefb3d8fc 3196 java optional 
t-digest_3.0-2.debian.tar.xz
 5b9a641dc689eb79e08cdc53fad8ec3b 13664 java optional 
t-digest_3.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlzswKIUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpaOhxAAq25OAJr9b/NLHH06GXsBJ8t53R3C
TqpFaGnU5JOQ2+FlGAYM/pdjLqZm1oT1sBw8ttqhRmelSi+YUpYj8IotXU6RfeLd
IkhQfLDn/IzqB8Ub/tja0ZDI6VrnquN1I3QR9vOWFTbsZuF9vYGK/4Gk2eJCHF+x
AnZebe+XAdnYbobN6egdADqe0UENgm8S9h0aGrohIR50jJ8Q7Dd23FXJkQWqHkHm
big1d9S5/oVlrrrhn60+R/PREfzn5bVpVHT2SerUAWWyD3Va+xY5n4JXlSQnJtYr
w6qqNlkxe5zv2Zqzvxr82G15ffIEv6iAaDayNOURFutGTeNX81FUzZ7ZAwaWvW8r
UJc2PHNdP6Nf7i0HTfVqS71WxUVBX5BWPqZB2d1jIba1uv6L1rNLoPg9TGhdEvQT
8nB4Mz5Jq8HPdxuRiBLocNpWZU7EbdZwz++UYocQ4HJlyGluUqsYkcVrPcdG/tQm
ygiS5LC8A+BmEyWMRVu7grGn++CLGEPoZRXBMU1YOwUVXJZghL7Yhq/YEgmk58kB
fxAkPrlDvYBX+JotRmXYm1BX4L5ARz5zXikNG/jIFgMEEkjYq3NA+0UczYtrhn1t

Bug#929283: zookeeper: CVE-2019-0201: information disclosure vulnerability

[tony mancill]

On Sun, May 26, 2019 at 08:58:29PM +0200, Moritz Mühlenhoff wrote:
> On Fri, May 24, 2019 at 09:19:00AM +0100, Chris Lamb wrote:
> > tags 929283 + patch
> > thanks
> > 
> > Hi Moritz,
> > 
> > > > > zookeeper: CVE-2019-0201: information disclosure vulnerability
> > > > 
> > > > Happy to prepare an update for stretch; I plan to do one for jessie
> > > > LTS (which, helpfully, has the same version...)
> > > 
> > > Sounds good, we should fix that in Stretch. I've just added the reference
> > > to the upstream commit in the 3.4 branch to the Security Tracker.
> > 
> > Thanks. Here is my diff:
> 
> Looks fine, but can you please also include the test case upstream added?
> Given that it's quite complex to reconstruct the specific affected ZK setup,
> we should at least ship/run the test case.

I will prepare an upload for 3.4.13 in testing/unstable soon - should be
in the next day or so.


signature.asc
Description: PGP signature

Bug#929662: docker.io: CVE-2018-15664

[Salvatore Bonaccorso]

Source: docker.io
Version: 18.09.1+dfsg1-7
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/docker/docker/pull/39252
Control: found -1 18.09.1+dfsg1-7~deb10u1
Control: found -1 18.09.5+dfsg1-1

Hi,

The following vulnerability was published for docker.io.

CVE-2018-15664[0]:
| In Docker through 18.06.1-ce-rc2, the API endpoints behind the 'docker
| cp' command are vulnerable to a symlink-exchange attack with Directory
| Traversal, giving attackers arbitrary read-write access to the host
| filesystem with root privileges, because daemon/archive.go does not do
| archive operations on a frozen filesystem (or from within a chroot).


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-15664
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15664
[1] https://github.com/docker/docker/pull/39252
[2] https://www.openwall.com/lists/oss-security/2019/05/28/1

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: docker.io: CVE-2018-15664

[Debian Bug Tracking System]

Processing control commands:

> found -1 18.09.1+dfsg1-7~deb10u1
Bug #929662 [src:docker.io] docker.io: CVE-2018-15664
Marked as found in versions docker.io/18.09.1+dfsg1-7~deb10u1.
> found -1 18.09.5+dfsg1-1
Bug #929662 [src:docker.io] docker.io: CVE-2018-15664
Marked as found in versions docker.io/18.09.5+dfsg1-1.

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

Processed: Re: Bug#927153 closed by Hideki Yamane

[Debian Bug Tracking System]

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

> fixed 927153 2.13.1-2
Bug #927153 {Done: Hideki Yamane } [fontconfig] 
fontconfig: fc-cache with -y option is broken
Marked as fixed in versions fontconfig/2.13.1-2.
>
End of message, stopping processing here.

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

Bug#929655: Obscure "Failed to set invocation ID for unit: File exists" error

[Michael Biebl]

Control: forcemerge 921267 -1

Am 28.05.19 um 00:59 schrieb Kathryn Tolsen:
> Package: systemd
> Version: 241-3
> Severity: Serious
> 
> All systemd services are failing to start, best guess is, this is
> related to:
> 
> https://github.com/systemd/systemd/issues/11810

This is already fixed in 241-4 and a duplicate of #921267

Merging accordingly.


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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#929655: Obscure "Failed to set invocation ID for unit: File exists" error

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 921267 -1
Bug #921267 {Done: Michael Biebl } [systemd] systemd fails to 
reach shutdown.target when rebooting or shutting down the system after resuming 
from suspend
Bug #929655 [systemd] Obscure "Failed to set invocation ID for unit: File 
exists" error
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/11810'.
Severity set to 'important' from 'serious'
Marked Bug as done
Marked as fixed in versions systemd/241-4.
Marked as found in versions systemd/240-4.
Added tag(s) fixed-upstream.
Bug #921267 {Done: Michael Biebl } [systemd] systemd fails to 
reach shutdown.target when rebooting or shutting down the system after resuming 
from suspend
Marked as found in versions systemd/241-3.
Merged 921267 929655

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

Bug#929655: Obscure "Failed to set invocation ID for unit: File exists" error

[Kathryn Tolsen]

Package: systemd
Version: 241-3
Severity: Serious

All systemd services are failing to start, best guess is, this is related
to:

https://github.com/systemd/systemd/issues/11810

https://github.com/poettering/systemd/commit/1c53d4a070edbec8ad2d384ba0014d0eb6bae077#diff-445fb9f3aa0c047d97ba6544e8a4575dR69

all logs on this issue are available here: http://kbt.ddns.net/

I will be leaving this site up until the issue is resolved. I am unable to
start any services and get errors spewed from systemd on any and all apt
operations, my mosh logins are especially laggy, and I'm afraid to even try
rebooting to possibly straighten this out, as if it can't start services it
may not even boot.

If this issue is the above related upstream issue, it effects a large
subset of users with AMD cpus, and renders systemd unusable, so I have
marked this as serious. This should be considered a release-critical bug.

The error message is not only vague but is misleading, as if I am right
about the source of this problem, it has nothing to do with some mysterious
"file" existing.

Other ideas tossed around were some kind of OOM condition, I have less than
250MB of 4GB ram in use, and over 3GB free on the rootfs which is on the
8GB m.2 SSD, so thats definitely not the issue here.

Bug#927153: marked as done (fontconfig: fc-cache with -y option is broken)

[Debian Bug Tracking System]

Your message dated Tue, 28 May 2019 07:38:28 +0900
with message-id <20190528073828.03bc966461bb40edfe58f...@iijmio-mail.jp>
and subject line 
has caused the Debian Bug report #927153,
regarding fontconfig: fc-cache with -y option is broken
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.)


-- 
927153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plymouth
Version: 0.9.4-1.1
Severity: grave
Justification: renders package unusable

I got the following error during upgrade:

[...]
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up initramfs-tools (0.133) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.133) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-4-amd64
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 134.
update-initramfs: failed for /boot/initrd.img-4.19.0-4-amd64 with 134.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 134
Errors were encountered while processing:
 initramfs-tools

-- 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-4-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 plymouth depends on:
ii  init-system-helpers  1.56+nmu1
ih  initramfs-tools  0.133
ii  libc62.28-8
ii  libdrm2  2.4.97-1
ii  libplymouth4 0.9.4-1.1
ii  lsb-base 10.2019031300
ii  systemd  241-3
ii  udev 241-3

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  desktop-base 10.0.2
pn  plymouth-themes  

-- no debconf information
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 8229--- End Message ---

Bug#927153: plymouth: upgrade fails:

[Hideki Yamane]

 /usr/share/initramfs-tools/hooks/plymouth failed with return 134
Message-Id: <20190528073815.2ba8e2fb13cf10d0fb4bc...@iijmio-mail.jp>
In-Reply-To: <20190520133004.gb2...@zira.vinc17.org>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 20 May 2019 15:30:04 +0200 Vincent Lefevre  wrote:
> On 2019-05-14 15:33:45 +0200, Tobias Eliasson wrote:
> > Are you able to reproduce this error with the latest fontconfig 2.13.1 in
> > buster?
> 
> I've just tried, and I no longer get a failure.

 Let's close this bug, then :)


-- 
Hideki Yamane 

Bug#927808:

[Kurt Kremitzki]

On 5/27/19 2:45 AM, Nico Schlömer wrote:
>> I was going to go ahead and do a +really upload with this fix either today 
>> or this weekend.
> 
> This is getting rather urgent now. Do you need any help?
> 

No, I just was waiting for the response on #929108. I'm traveling with
poor connection now but will be back to do an upload tomorrow evening.

Bug#925555: linux-image-4.19.0-4-amd64: [regression] No graphics on some

[Hideki Yamane]

 IvyBridge / Haswell systems
Message-Id: <20190528065209.ab9aed4d6eabe80a6b398...@iijmio-mail.jp>
In-Reply-To: <20190528064028.dec9969527111b97d555d...@iijmio-mail.jp>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 28 May 2019 06:40:28 +0900 Hideki Yamane  wrote:
>  It seems that fixed in 4.9.38 as below.

 4."19".38.


-- 
Hideki Yamane 

Processed: Re: linux-image-4.19.0-4-amd64: [regression] No graphics on some IvyBridge / Haswell systems

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +fixed-upstream
Bug #92 [src:linux] linux-image-4.19.0-4-amd64: [regression] No graphics on 
some IvyBridge / Haswell systems
Bug #925967 [src:linux] linux-image-4.19.0-4-amd64: [regression] No graphics on 
some IvyBridge / Haswell systems
Bug #926193 [src:linux] linux-image-4.19.0-4-amd64: [regression] No graphics on 
some IvyBridge / Haswell systems
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.

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

Bug#925555: linux-image-4.19.0-4-amd64: [regression] No graphics on some IvyBridge / Haswell systems

[Hideki Yamane]

control: tags -1 +fixed-upstream

Hi,

 It seems that fixed in 4.9.38 as below.

> commit 2bc7ce32eb21b094b3ae3e489017fabfe72b4dda
> Author: Dave Airlie 
> Date:   Wed Apr 24 10:47:56 2019 +1000
> 
> Revert "drm/i915/fbdev: Actually configure untiled displays"
> 
> commit 9fa246256e09dc30820524401cdbeeaadee94025 upstream.
> 
> This reverts commit d179b88deb3bf6fed4991a31fd6f0f2cad21fab5.
> 
> This commit is documented to break userspace X.org modesetting driver in 
> certain configurations.
> 
> The X.org modesetting userspace driver is broken. No fixes are available 
> yet. In order for this patch to be applied it either needs a config option or 
> a workaround developed.
> 
> This has been reported a few times, saying it's a userspace problem is 
> clearly against the regression rules.
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109806
> Signed-off-by: Dave Airlie 
> Cc:  # v3.19+
> Signed-off-by: Greg Kroah-Hartman 

-- 
Hideki Yamane 

Bug#929597: CVE-2019-12211 CVE-2019-12212 CVE-2019-12213 CVE-2019-12214

[Anton Gladky]

CVE-2019-12214 does not affect buster and stretch.
Jessie should be double checked because an older
version is used there.

Anton

Am So., 26. Mai 2019 um 22:01 Uhr schrieb Anton Gladky :
>
> Hi Moritz,
>
> thanks for the reporting. As far as I see, there is still
> no available fix from upstream.
>
> Cheers
>
> Anton
>
> Am So., 26. Mai 2019 um 21:27 Uhr schrieb Moritz Muehlenhoff 
> :
> >
> > Source: freeimage
> > Severity: grave
> > Tags: security
> >
> > Please see
> > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12211
> > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12212
> > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12213
> > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12214
> >
> > Cheers,
> > Moritz
> >
> > --
> > debian-science-maintainers mailing list
> > debian-science-maintain...@alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#929650: openjdk-8 is staying in unstable

[Matthias Klose]

Package: src:openjdk-8
Version: 8u212-b01-1
Severity: serious

openjdk-8 is staying in unstable.  It is used to prepare updates for
stable-security, and to bootstrap kotlin.

Bug#918171: marked as done (Broken with Thunderbird 60)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 19:47:05 +
with message-id 
and subject line Bug#929333: Removed package(s) from unstable
has caused the Debian Bug report #918171,
regarding Broken with Thunderbird 60
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.)


-- 
918171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-colorediffs
Version: 0.6.2012.01.27.14.07.45-1
Severity: grave

The plugin is broken with Thunderbird 60 in stretch and sid, after installation
it's disabled and only prints "Colored Diffs is incompatible with Thunderbird 
60.4".

TB 60 was uploaded to stretch over two months ago (and three months ago to sid),
given that noone filed a bug so far, it makes me wonder whether this package is
used at all...

Cheers,
Moritz
  
--- End Message ---
--- Begin Message ---
Version: 0.6.2012.01.27.14.07.45-1+rm

Dear submitter,

as the package colorediffs-extension has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/929333

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#929600: slurm-llnl: FTBFS on 32-bit architectures

[Gennaro Oliva]

Hi Andreas,

On Mon, May 27, 2019 at 03:23:45PM +0200, Andreas Beckmann wrote:
> On 2019-05-27 11:23, Gennaro Oliva wrote:
> > I have prepared an updated version of the package available here:
> > 
> > https://people.debian.org/~oliva/slurm-llnl-16.05.9-1+deb9u4/
> 
> I can confirm that it builds locally in a pbuilder stretch/i386
> environment :-)

thank you very much for testing it!

It also builds locally under armel, armhf, mips and mipsel using sbuild.

Best regards,
-- 
Gennaro Oliva

Bug#910038: marked as done (python3-rpyc: did not build)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 19:38:29 +
with message-id 
and subject line Bug#927988: Removed package(s) from unstable
has caused the Debian Bug report #908941,
regarding python3-rpyc: did not build
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.)


-- 
908941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-rpyc
Version: 4.0.2-2
Severity: important

rpyc 4.0.2-2 has been uploaded on September 6th. It is now October 1st,
there still are no binary packages in the archive => FTBFS? => please fix.

-- System Information:
Debian Release: buster/sid
  APT prefers stable
  APT policy: (800, 'stable'), (750, 'testing'), (700, 'unstable'), (650, 
'oldstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages python3-rpyc depends on:
ii  python3  3.6.5-3

Versions of packages python3-rpyc recommends:
pn  python3-paramiko  

Versions of packages python3-rpyc suggests:
pn  python-rpyc-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.0.2-2+rm

Dear submitter,

as the package rpyc has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/927988

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#908941: marked as done (rpyc FTBFS: test_registry.TestUdpRegistry failures)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 19:38:29 +
with message-id 
and subject line Bug#927988: Removed package(s) from unstable
has caused the Debian Bug report #908941,
regarding rpyc FTBFS: test_registry.TestUdpRegistry failures
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=rpyc=all=4.0.2-2=1536269574=0

...
I: pybuild pybuild:269: mkdir 
/<>/.pybuild/cpython3_3.7_rpyc/build/bin; cp bin/rpyc_classic.py 
bin/rpyc_registry.py /<>/.pybuild/cpython3_3.7_rpyc/build/bin
I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7_rpyc/build; 
python3.7 -m nose tests
SS...FFS.S.SSSS
==
FAIL: test_api (test_registry.TestUdpRegistry)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.7_rpyc/build/tests/test_registry.py", 
line 35, in test_api
self.assertEqual(set(p for _, p in res), set(expected))
AssertionError: Items in the second set but not the first:
12345
45678
 >> begin captured logging << 
REGSRV/UDP/18811: DEBUG: server started on 0.0.0.0:18811
REGCLNT/UDP: INFO: registering on 255.255.255.255:18811
REGCLNT/UDP: WARNING: no registry acknowledged
REGCLNT/UDP: INFO: registering on 255.255.255.255:18811
REGCLNT/UDP: WARNING: no registry acknowledged
REGSRV/UDP/18811: DEBUG: stopping server...
REGSRV/UDP/18811: DEBUG: server closed
- >> end captured logging << -

==
FAIL: test_pruning (test_registry.TestUdpRegistry)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.7_rpyc/build/tests/test_registry.py", 
line 48, in test_pruning
self.assertEqual(set(p for _, p in res), set((17171,)))
AssertionError: Items in the second set but not the first:
17171
 >> begin captured logging << 
REGSRV/UDP/18811: DEBUG: server started on 0.0.0.0:18811
REGCLNT/UDP: INFO: registering on 255.255.255.255:18811
REGCLNT/UDP: WARNING: no registry acknowledged
REGSRV/UDP/18811: DEBUG: stopping server...
REGSRV/UDP/18811: DEBUG: server closed
- >> end captured logging << -

--
Ran 47 tests in 54.010s

FAILED (SKIP=12, failures=2)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.7_rpyc/build; python3.7 -m nose tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p "3.7 3.6" 
returned exit code 13


Looking at the changelog, I'd suspect this might be caused by
  * Remove TestUdpRegistry patch rejected upstream
--- End Message ---
--- Begin Message ---
Version: 4.0.2-2+rm

Dear submitter,

as the package rpyc has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/927988

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: [bts-link] source package src:zookeeper

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:zookeeper
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #929283 (http://bugs.debian.org/929283)
> # Bug title: zookeeper: CVE-2019-0201: information disclosure vulnerability
> #  * http://issues.apache.org/jira/browse/ZOOKEEPER-1392
> #  * remote status changed: (?) -> Closed
> #  * remote resolution changed: (?) -> Fixed
> #  * closed upstream
> tags 929283 + fixed-upstream
Bug #929283 [src:zookeeper] zookeeper: CVE-2019-0201: information disclosure 
vulnerability
Added tag(s) fixed-upstream.
> usertags 929283 + status-Closed resolution-Fixed
There were no usertags set.
Usertags are now: status-Closed resolution-Fixed.
> thanks
Stopping processing here.

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

Bug#929446: marked as done (wireshark: CVE-2019-12295)

[Dr. Tobias Quathamer]

Am 27.05.19 um 19:04 schrieb Balint Reczey:
> Hi Tobias,
> 
> Thank you for taking care of packages with open security issues, but
> I'm wondering why you chose to do an immediate NMU.
> I planed uploading 2.6.9-1 today following the usual process we agreed
> on with the Security Team and I believe fixing this bug after 4 days
> it was opened is not an excessive amount of delay especially since two
> days were on a weekend.
> 
> Thanks,
> Balint

Hi Balint,

you're right, four days is really not a long time. I took this bug from
the RC bug list on udd.d.o and somehow saw a date from beginning of
April, so I assumed wrongly that this bug is nearly two months old
without any reaction from you. Probably I've mixed up a line on the UDD
page, I don't know where I got the wrong bug report date.

Shortly after I did the upload, I noticed that the bug is in fact only
four days old -- so I'm sorry about the upload, but I hope that it won't
interfere too much with your work.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#924029: marked as done (evince: Crashes when opening a PDF)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 17:33:57 +
with message-id 
and subject line Bug#924029: fixed in poppler 0.71.0-4.1
has caused the Debian Bug report #924029,
regarding evince: Crashes when opening a PDF
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.)


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

Dear Maintainer,

When opening these PDF files:
- http://sprott.physics.wisc.edu/pubs/paper277.pdf
- http://sprott.physics.wisc.edu/pubs/paper281.pdf
evince aborts with the message:

terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid
Aborted

“qpdfview” is able to display the files.

Best,
C.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (400, 'unstable'), (300, 'stable'), (100, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages evince depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  evince-common3.30.2-3
ii  gsettings-desktop-schemas3.28.1-1
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-7
ii  libcairo-gobject21.16.0-3
ii  libcairo21.16.0-3
ii  libevdocument3-4 3.30.2-3
ii  libevview3-3 3.30.2-3
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-7
ii  libglib2.0-0 2.58.3-1
ii  libgnome-desktop-3-173.30.2.1-1
ii  libgtk-3-0   3.24.5-1
ii  libnautilus-extension1a  3.30.5-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libsecret-1-00.18.7-1
ii  shared-mime-info 1.10-1

Versions of packages evince recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.12-1
ii  dbus-x11 [dbus-session-bus]   1.12.12-1

Versions of packages evince suggests:
ii  gvfs 1.38.1-3
ii  nautilus-sendto  3.8.6-3
ii  poppler-data 0.4.9-2
ii  unrar1:5.6.6-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 0.71.0-4.1

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

Debian distribution maintenance software
pp.
Jonathan Wiltshire  (supplier of updated poppler package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 May 2019 17:10:35 +0100
Source: poppler
Binary: gir1.2-poppler-0.18 libpoppler-cpp-dev libpoppler-cpp0v5 
libpoppler-cpp0v5-dbgsym libpoppler-dev libpoppler-glib-dev libpoppler-glib-doc 
libpoppler-glib8 libpoppler-glib8-dbgsym libpoppler-private-dev 
libpoppler-qt5-1 libpoppler-qt5-1-dbgsym libpoppler-qt5-dev libpoppler82 
libpoppler82-dbgsym poppler-utils poppler-utils-dbgsym
Architecture: source amd64 all
Version: 0.71.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Jonathan Wiltshire 
Description:
 gir1.2-poppler-0.18 - GObject introspection data for poppler-glib
 libpoppler-cpp-dev - PDF rendering library -- development files (CPP interface)
 libpoppler-cpp0v5 - PDF rendering library (CPP shared library)
 libpoppler-dev - PDF rendering library -- development files
 libpoppler-glib-dev - PDF rendering library -- development files (GLib 
interface)
 libpoppler-glib-doc - PDF rendering library -- documentation for the GLib 
interface
 libpoppler-glib8 - 

Bug#922397: marked as done (libevdocument3-4: Evince passes NULL pointer to poppler_date_parse)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 17:33:57 +
with message-id 
and subject line Bug#924029: fixed in poppler 0.71.0-4.1
has caused the Debian Bug report #924029,
regarding libevdocument3-4: Evince passes NULL pointer to poppler_date_parse
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.)


-- 
924029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libevdocument3-4
Version: 3.30.2-3
Severity: normal

Dear Maintainer,

While processing my Dissertation material (over 400 pages LaTeX) Evince
fails to display the generated PDF file. Consequently, it crashes with
an unhandled
exception as you can see in the following gdb session excerpt:

$> gdb --args evince Dissertation.pdf
GNU gdb (Debian 8.2.1-1) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from evince...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/evince Dissertation.pdf
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7f31a5ecc700 (LWP 11843)]
[New Thread 0x7f31a56cb700 (LWP 11844)]
[New Thread 0x7f31a4e47700 (LWP 11845)]
[New Thread 0x7f3197fff700 (LWP 11846)]
[New Thread 0x7f31977fe700 (LWP 11847)]
! SyncTeX Error : No file?
[New Thread 0x7f318f9f1700 (LWP 11848)]
[New Thread 0x7f318f1f0700 (LWP 11849)]
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_M_construct null not valid

Thread 6 "EvJobScheduler" received signal SIGABRT, Aborted.
[Switching to Thread 0x7f31977fe700 (LWP 11847)]
__GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis
nicht gefunden.
(gdb) bt full
#0 0x7f31a8d0a8bb in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 128849018883, 139850971861872, 64424509441,
139850971862000, 3, 0, 0, 7453294905665025139, 8245935278391255913,
139850971864064, 139850971863872, 139850971864184, 0, 139850971864200, 0}}
pid = 
tid = 
#1 0x7f31a8cf5535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xb, sa_sigaction = 0xb},
sa_mask = {__val = {0, 3432, 139851263947424, 139851263964931,
139851262646735, 41, 139850958663496, 139850971863328, 139850715569184,
94214282107424, 0, 139851182392764, 139851280872092, 139850717343800,
139851280892296, 139851263965248}}, sa_flags = -1767392304, sa_restorer
= 0x7f3188391c20} sigs = {__val = {32, 0 }}
#2 0x7f3196a76943 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3 0x7f3196a7c8a6 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4 0x7f3196a7c8e1 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5 0x7f3196a7cb14 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6 0x7f3196a78793 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7 0x7f31a402a81c in poppler_date_parse () at
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
#8 0x7f31a40c0307 in () at
/usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so
#9 0x7f31a9de64fa in () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
#10 0x7f31a9de84c2 in () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
#11 0x7f31a90ae425 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f31a8e9bfa3 in start_thread (arg=) at
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139850971866880,
7246701942669474992, 140736960326574, 140736960326575, 139850971866880,
0, -7281656517761008464, -7281717142416753488},
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev =
0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
#13 0x7f31a8dcc80f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) up
#1 0x7f31a8cf5535 in __GI_abort () at abort.c:79
79 abort.c: Datei oder Verzeichnis nicht gefunden.
(gdb) up
#2 

Bug#927764: marked as done (evince crashes in poppler on unusual pdf document)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 17:33:57 +
with message-id 
and subject line Bug#924029: fixed in poppler 0.71.0-4.1
has caused the Debian Bug report #924029,
regarding evince crashes in poppler on unusual pdf document
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.)


-- 
924029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpoppler-glib8
Version: 0.71.0-3
Control: affects -1 + evince

I have a pdf document that i unfortunately cannot share here.

however, trying to open the document with evince 3.30.2-3 crashes in
this way:

0 dkg@alice:~$ evince test.pdf 
! SyncTeX Error : No file?
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid
Aborted
134 dkg@alice:~$  

(i think that the SyncTeX error message is a red herring, because that
shows up on every file that i open with evince; see
https://gitlab.gnome.org/GNOME/evince/commit/678410e81d0c889f4db4e995ca451ed62b8a2eee)

(i get the same crash when testing evince 3.32.0-1 from experimental)

It looks like the underlying failure might be similar to this:

 https://bbs.archlinux.org/viewtopic.php?id=242607

That report suggests that poppler 0.72.0 might fix the issue, but i have
not tested it.  If poppler 0.72.0 was in experimental, i'd be happy to
try it out.

Here is a backtrace of the crash according to gdb:

#0  0x76e528bb in raise () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x76e3d535 in abort () at /lib/x86_64-linux-gnu/libc.so.6
#2  0x710db983 in __gnu_cxx::__verbose_terminate_handler() () at 
../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
#3  0x710e18c6 in __cxxabiv1::__terminate(void (*)()) 
(handler=) at 
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47
#4  0x710e1901 in std::terminate() () at 
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:57
#5  0x710e1b34 in __cxxabiv1::__cxa_throw(void*, std::type_info*, void 
(*)(void*))
(obj=obj@entry=0x7fffe040bc80, tinfo=0x711c5958 , dest=0x710f6530 ) at 
../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:95
#6  0x710dd7d3 in std::__throw_logic_error(char const*) () at 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x7172c82c in std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)
(__end=0x , __beg=0x0, this=0x71fb89f0) at 
/usr/include/c++/8/bits/basic_string.tcc:206
#8  0x7172c82c in std::__cxx11::basic_string, std::allocator >::_M_construct_aux(char const*, char const*, std::__false_type)
(__end=0x , __beg=0x0, this=0x71fb89f0) at 
/usr/include/c++/8/bits/basic_string.h:236
#9  0x7172c82c in std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*)
(__end=0x , __beg=0x0, this=0x71fb89f0) at 
/usr/include/c++/8/bits/basic_string.h:255
#10 0x7172c82c in std::__cxx11::basic_string, std::allocator >::basic_string(char const*, 
std::allocator const&) (__a=..., __s=0x0, this=0x71fb89f0)
at /usr/include/c++/8/bits/basic_string.h:516
#11 0x7172c82c in GooString::GooString(char const*) (sA=0x0, 
this=0x71fb89f0) at ./goo/GooString.h:63
#12 0x7172c82c in poppler_date_parse(gchar const*, time_t*) 
(date=date@entry=0x0, timet=timet@entry=0x71fb8aa0) at 
./glib/poppler-date.cc:42
#13 0x717ae307 in ev_annot_from_poppler_annot (page=0x7fffe0405640, 
poppler_annot=0x557c8520) at ev-poppler.cc:3285
#14 0x717ae307 in 
pdf_document_annotations_get_annotations(EvDocumentAnnotations*, EvPage*) 
(document_annotations=, page=0x7fffe0405640) at 
ev-poppler.cc:3395
#15 0x77f2d4fa in  () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
#16 0x77f2f4c2 in  () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
#17 0x771f6425 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x76fe3fa3 in start_thread () at 
/lib/x86_64-linux-gnu/libpthread.so.0
#19 0x76f1482f in clone () at /lib/x86_64-linux-gnu/libc.so.6

Thanks for maintaining poppler in debian!

   --dkg


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 0.71.0-4.1

We believe that the bug you reported is fixed in the latest version of
poppler, 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 

Bug#922398: marked as done (libevdocument3-4: Evince passes NULL pointer to poppler_date_parse)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 17:33:57 +
with message-id 
and subject line Bug#924029: fixed in poppler 0.71.0-4.1
has caused the Debian Bug report #924029,
regarding libevdocument3-4: Evince passes NULL pointer to poppler_date_parse
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.)


-- 
924029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libevdocument3-4
Version: 3.30.2-3
Severity: normal

Dear Maintainer,

While processing my Dissertation material (over 400 pages LaTeX) Evince
fails to display the generated PDF file. Consequently, it crashes with
an unhandled
exception as you can see in the following gdb session excerpt:

$> gdb --args evince Dissertation.pdf
GNU gdb (Debian 8.2.1-1) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from evince...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/evince Dissertation.pdf
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7f31a5ecc700 (LWP 11843)]
[New Thread 0x7f31a56cb700 (LWP 11844)]
[New Thread 0x7f31a4e47700 (LWP 11845)]
[New Thread 0x7f3197fff700 (LWP 11846)]
[New Thread 0x7f31977fe700 (LWP 11847)]
! SyncTeX Error : No file?
[New Thread 0x7f318f9f1700 (LWP 11848)]
[New Thread 0x7f318f1f0700 (LWP 11849)]
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_M_construct null not valid

Thread 6 "EvJobScheduler" received signal SIGABRT, Aborted.
[Switching to Thread 0x7f31977fe700 (LWP 11847)]
__GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis
nicht gefunden.
(gdb) bt full
#0 0x7f31a8d0a8bb in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 128849018883, 139850971861872, 64424509441,
139850971862000, 3, 0, 0, 7453294905665025139, 8245935278391255913,
139850971864064, 139850971863872, 139850971864184, 0, 139850971864200, 0}}
pid = 
tid = 
#1 0x7f31a8cf5535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xb, sa_sigaction = 0xb},
sa_mask = {__val = {0, 3432, 139851263947424, 139851263964931,
139851262646735, 41, 139850958663496, 139850971863328, 139850715569184,
94214282107424, 0, 139851182392764, 139851280872092, 139850717343800,
139851280892296, 139851263965248}}, sa_flags = -1767392304, sa_restorer
= 0x7f3188391c20} sigs = {__val = {32, 0 }}
#2 0x7f3196a76943 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3 0x7f3196a7c8a6 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4 0x7f3196a7c8e1 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5 0x7f3196a7cb14 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6 0x7f3196a78793 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7 0x7f31a402a81c in poppler_date_parse () at
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
#8 0x7f31a40c0307 in () at
/usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so
#9 0x7f31a9de64fa in () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
#10 0x7f31a9de84c2 in () at /usr/lib/x86_64-linux-gnu/libevview3.so.3
#11 0x7f31a90ae425 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f31a8e9bfa3 in start_thread (arg=) at
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139850971866880,
7246701942669474992, 140736960326574, 140736960326575, 139850971866880,
0, -7281656517761008464, -7281717142416753488},
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev =
0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
#13 0x7f31a8dcc80f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) up
#1 0x7f31a8cf5535 in __GI_abort () at abort.c:79
79 abort.c: Datei oder Verzeichnis nicht gefunden.
(gdb) up
#2 

Bug#929446: marked as done (wireshark: CVE-2019-12295)

[Balint Reczey]

Hi Tobias,

Thank you for taking care of packages with open security issues, but
I'm wondering why you chose to do an immediate NMU.
I planed uploading 2.6.9-1 today following the usual process we agreed
on with the Security Team and I believe fixing this bug after 4 days
it was opened is not an excessive amount of delay especially since two
days were on a weekend.

Thanks,
Balint

On Mon, May 27, 2019 at 4:45 PM Debian Bug Tracking System
 wrote:
>
> Your message dated Mon, 27 May 2019 14:42:22 +
> with message-id 
> and subject line Bug#929446: fixed in wireshark 2.6.8-1.1
> has caused the Debian Bug report #929446,
> regarding wireshark: CVE-2019-12295
> 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.)
>
>
> --
> 929446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929446
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Salvatore Bonaccorso 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Thu, 23 May 2019 19:56:24 +0200
> Subject: wireshark: CVE-2019-12295
> Source: wireshark
> Version: 2.6.8-1
> Severity: grave
> Tags: security upstream
> Forwarded: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15778
> Control: found -1 2.6.7-1~deb9u1
>
> Hi,
>
> The following vulnerability was published for wireshark.
>
> CVE-2019-12295[0]:
> | In Wireshark 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14, the
> | dissection engine could crash. This was addressed in epan/packet.c by
> | restricting the number of layers and consequently limiting recursion.
>
>
> 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-12295
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12295
> [1] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15778
> [2] https://www.wireshark.org/security/wnpa-sec-2019-19.html
>
> Regards,
> Salvatore
>
>
>
> -- Forwarded message --
> From: "Dr. Tobias Quathamer" 
> To: 929446-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 27 May 2019 14:42:22 +
> Subject: Bug#929446: fixed in wireshark 2.6.8-1.1
> Source: wireshark
> Source-Version: 2.6.8-1.1
>
> We believe that the bug you reported is fixed in the latest version of
> wireshark, 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 929...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Dr. Tobias Quathamer  (supplier of updated wireshark 
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Mon, 27 May 2019 16:08:44 +0200
> Source: wireshark
> Architecture: source
> Version: 2.6.8-1.1
> Distribution: unstable
> Urgency: medium
> Maintainer: Balint Reczey 
> Changed-By: Dr. Tobias Quathamer 
> Closes: 929446
> Changes:
>  wireshark (2.6.8-1.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* CVE-2019-12295
>  In Wireshark 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14,
>  the dissection engine could crash. This was addressed in
>  epan/packet.c by restricting the number of layers and
>  consequently limiting recursion. (Closes: #929446)
> Checksums-Sha1:
>  638a99183f0251eae3adcddc57e683e3b925ec84 3531 wireshark_2.6.8-1.1.dsc
>  55c82bbb3e02077378a512f69f6ff8e0f4dcc5cf 71716 
> wireshark_2.6.8-1.1.debian.tar.xz
>  e4ea88d8c0ddfbc1e510b9c76d088d2229e2eebc 25763 
> wireshark_2.6.8-1.1_amd64.buildinfo
> Checksums-Sha256:
>  71f0a3be5a1360c0b2e60eda3f71fc9d771254099e2296ed0839679c61f41b5a 3531 
> wireshark_2.6.8-1.1.dsc
>  4161d9c12abceb7ffce74e581b5762f4ee49f947b06fb690b408a95be1c8bd2c 71716 
> wireshark_2.6.8-1.1.debian.tar.xz
>  8f16585bc19d4455fcd4ae73c811e8494d7211a1dada520252db807480b54941 25763 
> wireshark_2.6.8-1.1_amd64.buildinfo
> Files:
>  00b410721d6db832f99b54d345fe28ae 3531 net optional wireshark_2.6.8-1.1.dsc
>  6c5f09f829283d29f4d3211f40839c5d 71716 net optional 
> wireshark_2.6.8-1.1.debian.tar.xz
>  821834ae84ee480417346744f29fe2aa 25763 net optional 
> 

Bug#927808: gmsh: FTBFS in buster (/usr/include/occt/Standard_Version.hxx cannot be read)

[Ansgar]

Hi,

Kurt Kremitzki writes:
> On 5/17/19 4:14 AM, Ansgar wrote:
>> I tried and with this line removed gmsh builds again.  I'll ask the
>> release team about t-p-u or reverting in unstable.
[...]
> Sorry for not addressing this sooner such that you needed to spend time
> looking at it.  I was going to go ahead and do a +really upload with
> this fix either today or this weekend, so it shouldn't be necessary for
> you to spend any more time on it, unless you'd advise a different course
> of action. (This is my first Debian release, BTW.)

The release team said they prefer a +really upload[1].

  [1] https://bugs.debian.org/929108#10

Ansgar

Bug#929446: marked as done (wireshark: CVE-2019-12295)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 14:42:22 +
with message-id 
and subject line Bug#929446: fixed in wireshark 2.6.8-1.1
has caused the Debian Bug report #929446,
regarding wireshark: CVE-2019-12295
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.)


-- 
929446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wireshark
Version: 2.6.8-1
Severity: grave
Tags: security upstream
Forwarded: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15778
Control: found -1 2.6.7-1~deb9u1

Hi,

The following vulnerability was published for wireshark.

CVE-2019-12295[0]:
| In Wireshark 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14, the
| dissection engine could crash. This was addressed in epan/packet.c by
| restricting the number of layers and consequently limiting recursion.


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-12295
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12295
[1] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15778
[2] https://www.wireshark.org/security/wnpa-sec-2019-19.html

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wireshark
Source-Version: 2.6.8-1.1

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated wireshark package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 May 2019 16:08:44 +0200
Source: wireshark
Architecture: source
Version: 2.6.8-1.1
Distribution: unstable
Urgency: medium
Maintainer: Balint Reczey 
Changed-By: Dr. Tobias Quathamer 
Closes: 929446
Changes:
 wireshark (2.6.8-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * CVE-2019-12295
 In Wireshark 3.0.0 to 3.0.1, 2.6.0 to 2.6.8, and 2.4.0 to 2.4.14,
 the dissection engine could crash. This was addressed in
 epan/packet.c by restricting the number of layers and
 consequently limiting recursion. (Closes: #929446)
Checksums-Sha1:
 638a99183f0251eae3adcddc57e683e3b925ec84 3531 wireshark_2.6.8-1.1.dsc
 55c82bbb3e02077378a512f69f6ff8e0f4dcc5cf 71716 
wireshark_2.6.8-1.1.debian.tar.xz
 e4ea88d8c0ddfbc1e510b9c76d088d2229e2eebc 25763 
wireshark_2.6.8-1.1_amd64.buildinfo
Checksums-Sha256:
 71f0a3be5a1360c0b2e60eda3f71fc9d771254099e2296ed0839679c61f41b5a 3531 
wireshark_2.6.8-1.1.dsc
 4161d9c12abceb7ffce74e581b5762f4ee49f947b06fb690b408a95be1c8bd2c 71716 
wireshark_2.6.8-1.1.debian.tar.xz
 8f16585bc19d4455fcd4ae73c811e8494d7211a1dada520252db807480b54941 25763 
wireshark_2.6.8-1.1_amd64.buildinfo
Files:
 00b410721d6db832f99b54d345fe28ae 3531 net optional wireshark_2.6.8-1.1.dsc
 6c5f09f829283d29f4d3211f40839c5d 71716 net optional 
wireshark_2.6.8-1.1.debian.tar.xz
 821834ae84ee480417346744f29fe2aa 25763 net optional 
wireshark_2.6.8-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlzr8vwACgkQEwLx8Dbr
6xk4Ag/+JpqEK+LFiT40ZkBPOobmDZlGSdNcimDcdKQJQ49HBzo/im11w9w/Udxf
ZCy8bVGqZWLvKuzE0zsY6uCMG0uZxRAX8W8xyKGKNHxiInyNM2NkabZvkifBRg+V
WcY8BsjHRS5kpP7grlDA4wkoG1y8StVLhNXmt45bmySaylpw7Fc7VVPKKd8gStSJ
nT82ifOaTqsdV2YcJaoLlWl7+Z5N/O8xVuT9uB76zzC10pPyXQq461Mcf+GYvNLm
CIQo1mLG2DQzxM8TDDKfk2UMWjutK21IIvCM1BGPPOTiESmapIVhmX2vX3pRrLoR
/0dr2p2tJwiEsQ7iKD7CwJmtQ3kgQBojCbillRbSyKvHCL1pWImIKAlGQouxid53
0VAa07lyzFeLsHDcACRX/hVG7TZt86H6fw5wmHTKKD4hsP/3klIkKymsXaKu3bGi
hbnsjhCnNG+DZLoxNv/cH5KMTpWdBneuT80wGqmpcsKBdlmp5U7HlJM/4fcxXAqn
sRRauNxvgSWMIQMYmIj3fferJfjBbwYNWj3p82ED+evAueHFkHdN7Sv0qrbwc2dO
0yM+Ez/L1ocqsLA98DgxLq4jPKHBV+RAsthPvy6mYRJplcyW07KYMzwR6zNgIwN2
cdw8XND8PBf5FjaFCHIP3F/6kZ/1DVuyyuecdQ91OYfczyoy5Rk=
=Glfy
-END PGP SIGNATURE End Message ---

Bug#929600: slurm-llnl: FTBFS on 32-bit architectures

[Andreas Beckmann]

On 2019-05-27 11:23, Gennaro Oliva wrote:
> I have prepared an updated version of the package available here:
> 
> https://people.debian.org/~oliva/slurm-llnl-16.05.9-1+deb9u4/

I can confirm that it builds locally in a pbuilder stretch/i386
environment :-)


Andreas

Bug#926042: drawbacks of not having tbl in testing..

[Holger Levsen]

On Mon, May 27, 2019 at 02:18:54PM +0200, Ulrike Uhlig wrote:
> It would be useful to know with which statements or assumptions you do
> not agree with and why - so that the discussion may become more
> productive & helpful.
 
"cannot be maintained in stable". I think this can at least be tried.
And IMO its better to have tbl in stable until the 5th or 7th
pointrelease and then have it removed (if it has to be done), than not
having tbl at all, never.

> > anyway, i just want to point out that 'maintaining tbl in stretch via
> > stretch-backports' doesnt work because tbl is not in buster and thus, if
> > this bug gets retitled to 'tbl should not be part of bullseye',
> > maintaining tbl in buster via bullseye-backports will also not work.
> Do you have any suggestion on how to handle this?

maintain tbl in stable.


-- 
tschau,
Holger

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

Our civilization is being sacrificed for the opportunity of a very small number
of people to continue making enormous amounts of money...  It is the sufferings
of the many  which pay  for the luxuries  of the few...  You say  you love your
children  above all else,  and yet  you are stealing  their future  in front of 
their very eyes...


signature.asc
Description: PGP signature

Bug#925173: marked as done (ltsp: codename detection code not useful for stable)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 12:33:44 +
with message-id 
and subject line Bug#925173: fixed in ltsp 5.18.12-2
has caused the Debian Bug report #925173,
regarding ltsp: codename detection code not useful for stable
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.)


-- 
925173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ltsp
Version: 5.18.12-1
Severity: important
Tags: patch

Hi,

while testing Debian Edu offline installation I noticed that the code I proposed
a while ago to determine the DIST value is working ok in testing, but will be
totally useless once Buster is stable.

The attached patch reverts the change; use 'lsb_release -s -c' again to detect
the codename. 

Please check.

Wolfgang
>From 57c25bc3a2ac224253265e9f7a149cb52c0a81db Mon Sep 17 00:00:00 2001
From: Wolfgang Schweer 
Date: Wed, 20 Mar 2019 18:40:32 +0100
Subject: [PATCH] Revert "Make
 'ltsp-build-client/Debian/000-basic-configuration' more robust."

This reverts commit 1a695ea6b4431fe628d1f36e410da636226fae24.

While it made sense to use /etc/debian_release in testing (the file contains
text like 'buster/sid') it fails to work in stable (the file content is a plain
version number like 9.8). 'lsb_release -s -c' is supposed to work in stable also
in standalone mode.
---
 .../plugins/ltsp-build-client/Debian/000-basic-configuration| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/server/share/ltsp/plugins/ltsp-build-client/Debian/000-basic-configuration 
b/server/share/ltsp/plugins/ltsp-build-client/Debian/000-basic-configuration
index 30d04dcf..983605f4 100644
--- a/server/share/ltsp/plugins/ltsp-build-client/Debian/000-basic-configuration
+++ b/server/share/ltsp/plugins/ltsp-build-client/Debian/000-basic-configuration
@@ -2,7 +2,7 @@ case "$MODE" in
 configure)
 ARCH=${ARCH:-"$(dpkg --print-architecture)"}
 APT_GET_OPTS=${APT_GET_OPTS:-"-y"}
-DIST=${DIST:-"$(cat /etc/debian_version | cut -d'/' -f1)"}
+DIST=${DIST:-"$(lsb_release -s -c)"}
 MIRROR=${MIRROR:-"http://deb.debian.org/debian"}
 COMPONENTS=${COMPONENTS:-"main"}
 EARLY_PACKAGES=${EARLY_PACKAGES:-"ltsp-client"}
-- 
2.20.1

--- End Message ---
--- Begin Message ---
Source: ltsp
Source-Version: 5.18.12-2

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

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated ltsp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 27 May 2019 04:58:46 -0700
Source: ltsp
Architecture: source
Version: 5.18.12-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LTSP Maintainers 
Changed-By: Vagrant Cascadian 
Closes: 924103 925173
Changes:
 ltsp (5.18.12-2) unstable; urgency=medium
 .
   [ Frans Spiesschaert ]
   * [INTL:nl] Dutch translation of debconf messages (Closes: #924103).
 .
   [ Vagrant Cascadian ]
   * Add patch to fix loop mounting and ensure mount is read-only. Thanks
 to Alkis Georgopoulos.
   * Add patch to fix codename detection (Closes: #925173). Thanks to
 Wolfgang Schweer.
Checksums-Sha1:
 bb9adb94d33572a05d936ec58b334308991fd2bf 1684 ltsp_5.18.12-2.dsc
 b6614d48bbd440b348b4df8953d47ff6b6d6f9e8 76920 ltsp_5.18.12-2.debian.tar.xz
 fa06e045efeff44265de31a1a2105237e6cbc0e2 6859 ltsp_5.18.12-2_amd64.buildinfo
Checksums-Sha256:
 2b09bada0ca2cd409d8a8628088907aa6645757d0370c916339061ce330b3b79 1684 
ltsp_5.18.12-2.dsc
 c6c2ead5d42f718a5e334536b3d23143b889b63c223b9f0f51c538b8983e8143 76920 
ltsp_5.18.12-2.debian.tar.xz
 14496e5e09c049c055b40ae738dd92cc0afccb95724beaa288c55e2b101b8725 6859 
ltsp_5.18.12-2_amd64.buildinfo
Files:
 2ef52c62263d01b6ced3ba7498a15b71 1684 misc optional ltsp_5.18.12-2.dsc
 5a90a99cf63b479ea89e5e5c40bdf54c 76920 misc optional 
ltsp_5.18.12-2.debian.tar.xz
 8938e475d0f4e2364b481b042e0bd0cd 6859 misc optional 
ltsp_5.18.12-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#928986: marked as done (CloudCompare: error while loading shared libraries: libQCC_IO_LIB.so:)

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 12:33:35 +
with message-id 
and subject line Bug#928986: fixed in cloudcompare 2.10.1-2
has caused the Debian Bug report #928986,
regarding CloudCompare: error while loading shared libraries: libQCC_IO_LIB.so:
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.)


-- 
928986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cloudcompare
Version: 2.10.1-1
Severity: grave
Justification: renders package unusable

Hi,

after installing the package, when attempting to start CloudCompare I
get the following error message:

CloudCompare: error while loading shared libraries: libQCC_IO_LIB.so:
cannot open shared object file: No such file or directory

Indeed that file seems to be contain in no binary package in the
archive?

Thanks!

cheers, josch


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

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

Versions of packages cloudcompare depends on:
ii  libboost-atomic1.67.0 1.67.0-11
ii  libboost-chrono1.67.0 1.67.0-11
ii  libboost-date-time1.67.0  1.67.0-11
ii  libboost-system1.67.0 1.67.0-10
ii  libboost-thread1.67.0 1.67.0-11
ii  libc6 2.28-2
ii  libcgal13 4.12-1
ii  libgcc1   1:8.2.0-9
ii  libgl11.1.0-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgmp10  2:6.1.2+dfsg-4
ii  libgmpxx4ldbl 2:6.1.2+dfsg-4
ii  libgomp1  8.2.0-9
ii  libmpfr6  4.0.1-1
ii  libpdal-base7 1.8.0+ds-1+b2
ii  libpdal-util7 1.8.0+ds-1+b2
ii  libqt5concurrent5 5.11.3+dfsg-2
ii  libqt5core5a  5.11.3+dfsg-2
ii  libqt5gui55.11.3+dfsg-2
ii  libqt5opengl5 5.11.3+dfsg-2
ii  libqt5printsupport5   5.11.3+dfsg-2
ii  libqt5widgets55.11.3+dfsg-2
ii  libstdc++68.2.0-9

cloudcompare recommends no packages.

cloudcompare suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: cloudcompare
Source-Version: 2.10.1-2

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated cloudcompare package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 27 May 2019 07:36:32 +0200
Source: cloudcompare
Architecture: source
Version: 2.10.1-2
Distribution: unstable
Urgency: medium
Maintainer: Gürkan Myczko 
Changed-By: Gürkan Myczko 
Closes: 928986
Changes:
 cloudcompare (2.10.1-2) unstable; urgency=medium
 .
   * Thanks Juhani Numminen for the patch to have
 RPATH absolute. (Closes: #928986)
Checksums-Sha1:
 1335ca71a938d52c6de496585855eae174178cc4 2080 cloudcompare_2.10.1-2.dsc
 febda3c3ace7474f3650375986af4680f4fc2371 7556 
cloudcompare_2.10.1-2.debian.tar.xz
 f5335150527a8cc7016b7c2ac984a958bcd8487e 6011 
cloudcompare_2.10.1-2_source.buildinfo
Checksums-Sha256:
 4c2ad7e3aa74d8bb74767688128c68c38adb6318f8929b95cd19b95489dda1f5 2080 
cloudcompare_2.10.1-2.dsc
 4b4ad42fa084e661be48503392d2410ad564189ff79ff4e966f6c6c9c27701fe 7556 
cloudcompare_2.10.1-2.debian.tar.xz
 363f1af01f4ca02bad1b2782a009dcef125213caf3d99ecff4fdda7c1c45f36e 6011 
cloudcompare_2.10.1-2_source.buildinfo
Files:
 4fec3b2f0d5dc2d4b3ea05ab0849d885 2080 graphics optional 
cloudcompare_2.10.1-2.dsc
 1e58d353bc0d40e76f81f1cc91b287be 7556 graphics optional 
cloudcompare_2.10.1-2.debian.tar.xz
 f08886a099555e318f3a1b0b7241bdca 6011 graphics optional 
cloudcompare_2.10.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#926042: drawbacks of not having tbl in testing..

[Ulrike Uhlig]

Hi Holger,

On 27.05.19 11:56, Holger Levsen wrote:
> i'm not sure I agree with the assumptions from this bug report but

It would be useful to know with which statements or assumptions you do
not agree with and why - so that the discussion may become more
productive & helpful.

> anyway, i just want to point out that 'maintaining tbl in stretch via
> stretch-backports' doesnt work because tbl is not in buster and thus, if
> this bug gets retitled to 'tbl should not be part of bullseye',
> maintaining tbl in buster via bullseye-backports will also not work.

Do you have any suggestion on how to handle this?

Cheers,
Ulrike

Processed: bug 929597 is forwarded to https://sourceforge.net/p/freeimage/discussion/36111/thread/e06734bed5/

[Debian Bug Tracking System]

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

> forwarded 929597 
> https://sourceforge.net/p/freeimage/discussion/36111/thread/e06734bed5/
Bug #929597 [src:freeimage] CVE-2019-12211 CVE-2019-12212 CVE-2019-12213 
CVE-2019-12214
Set Bug forwarded-to-address to 
'https://sourceforge.net/p/freeimage/discussion/36111/thread/e06734bed5/'.
> thanks
Stopping processing here.

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

Processed: found 929597 in 3.18.0+ds2-1

[Debian Bug Tracking System]

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

> found 929597 3.18.0+ds2-1
Bug #929597 [src:freeimage] CVE-2019-12211 CVE-2019-12212 CVE-2019-12213 
CVE-2019-12214
Marked as found in versions freeimage/3.18.0+ds2-1.
> thanks
Stopping processing here.

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

Processed: tagging 929597

[Debian Bug Tracking System]

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

> tags 929597 + upstream
Bug #929597 [src:freeimage] CVE-2019-12211 CVE-2019-12212 CVE-2019-12213 
CVE-2019-12214
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#929527: [pkg-netfilter-team] Bug#929527: /usr/sbin/xtables-nft-multi: restoring IP Tables with an self-defined chain segfaults in libnftnl.so

[Arturo Borrero Gonzalez]

On 5/25/19 6:49 PM, Thomas Lamprecht wrote:
> Package: iptables
> Version: 1.8.2-4
> Severity: grave
> File: /usr/sbin/xtables-nft-multi
> Justification: renders package unusable by segfaulting on usage
> 
> Reproducer:
> # cat simple-segv-table
> *filter
> :NEW-OUTPUT - [0:0]
> -A OUTPUT -j NEW-OUTPUT
> -F NEW-OUTPUT
> -A NEW-OUTPUT -j ACCEPT
> COMMIT
> 
> # iptables ./simple-segv-table
> Segmentation fault
> 
> # dmesg | tail -1
> [12860.813350] traps: iptables-restor[19173] general protection 
> ip:7f4894682793 sp:7ffcedc177d0 error:0 in 
> libnftnl.so.11.0.0[7f4894677000+17000]
> 
> # addr2line -e /usr/lib/x86_64-linux-gnu/libnftnl.so.11.0.0  -fCi $(printf 
> "%x" $[0x7f2cb9882793 - 0x7f2cb9877000])
> nftnl_batch_is_supported
> ??:?
> 

I can reproduce this.

I'm already looking for a fix.

Bug#879007: Patch applied

[rollop...@gmail.com]

Thanks for the patch, I managed to aplpy to the server, now I will test it.
Given the seriousness of the bug, I believe we should release a fixed
version of the package.

Bug#929527: /usr/sbin/xtables-nft-multi: restoring IP Tables with an self-defined chain segfaults in libnftnl.so

[Stoiko Ivanov]

Changing the iptables alternative to use the legacy binaries causes the
segfault not to occur.

Bug#926042: drawbacks of not having tbl in testing..

[Holger Levsen]

hi,

i'm not sure I agree with the assumptions from this bug report but
anyway, i just want to point out that 'maintaining tbl in stretch via
stretch-backports' doesnt work because tbl is not in buster and thus, if
this bug gets retitled to 'tbl should not be part of bullseye',
maintaining tbl in buster via bullseye-backports will also not work.

(I just noted this bug now by chance, that's why I'm late to this party.)


-- 
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#929618: t-digest: latest-debian-changelog-entry-reuses-existing-version

[Andreas Beckmann]

Source: t-digest
Version: 1:3.0-1
Severity: serious

W: libt-digest-java: latest-debian-changelog-entry-reuses-existing-version 
1:3.0-1 == 3.0-1 (last used: Tue, 14 Oct 2014 10:44:34 +0200)
N: 
N:The latest changelog entry has a version that matches one used in the
N:specified previous entry. All versions of a source package must be
N:unique even after a leading epoch has been stripped off.
N:
N:Files generated by the current version of this source package would
N:conflict with some historical files. This is because the Debian archive
N:does not allow multiple files with the same name and different contents
N:and the generated .dsc, .deb, etc. do not embed the epoch in their
N:filenames.
N:
N:Please pick another version, for example by increasing the Debian
N:revision.
N:
N:Severity: normal, Certainty: certain
N:
N:Check: changelog-file, Type: binary

Just bumping the version number to 1:3.0-2 should be safe.


Andreas

PS: I do not want to repeat https://bugs.debian.org/929614

Bug#929617: d3-format: latest-debian-changelog-entry-reuses-existing-version

[Andreas Beckmann]

Source: d3-format
Version: 1:1.0.2-1
Severity: serious

W: libjs-d3-format: latest-debian-changelog-entry-reuses-existing-version 
1:1.0.2-1 == 1.0.2-1 (last used: Sat, 19 Nov 2016 04:00:20 +0100)
N: 
N:The latest changelog entry has a version that matches one used in the
N:specified previous entry. All versions of a source package must be
N:unique even after a leading epoch has been stripped off.
N:
N:Files generated by the current version of this source package would
N:conflict with some historical files. This is because the Debian archive
N:does not allow multiple files with the same name and different contents
N:and the generated .dsc, .deb, etc. do not embed the epoch in their
N:filenames.
N:
N:Please pick another version, for example by increasing the Debian
N:revision.
N:
N:Severity: normal, Certainty: certain
N:
N:Check: changelog-file, Type: binary

Changelog and snapshot.debian.org know about 1.0.2-2, so 1:1.0.2-3 should
be the next safe version number to use.


Andreas

PS: I do not want to repeat https://bugs.debian.org/929614

Bug#929600: slurm-llnl: FTBFS on 32-bit architectures

[Gennaro Oliva]

Hi Andreas, 

On Sun, May 26, 2019 at 10:31:14PM +0200, Andreas Beckmann wrote:
> the stretch update of slurm-llnl FTBFS on the 32-bit architectures:

thank you very much for filing this bug report.

I have prepared an updated version of the package available here:

https://people.debian.org/~oliva/slurm-llnl-16.05.9-1+deb9u4/

debdiff attached, diffstat follows:

changelog |6 --
patches/CVE-2019-6438 |   11 ---
2 files changed, 17 deletions(-)

Best regards,
-- 
Gennaro Oliva
diff -Nru slurm-llnl-16.05.9/debian/changelog 
slurm-llnl-16.05.9/debian/changelog
--- slurm-llnl-16.05.9/debian/changelog 2019-05-27 09:48:30.0 +0200
+++ slurm-llnl-16.05.9/debian/changelog 2019-02-12 23:34:26.0 +0100
@@ -1,9 +1,3 @@
-slurm-llnl (16.05.9-1+deb9u4) stretch-security; urgency=medium
-
-  * Fix build regression on 32-bits architecture (Closes: #92960) 
-
- -- Gennaro Oliva   Mon, 27 May 2019 09:48:30 +0200
-
 slurm-llnl (16.05.9-1+deb9u3) stretch-security; urgency=high
 
   * Fix CVE-2019-6438 by adding mitigation for a potential
diff -Nru slurm-llnl-16.05.9/debian/patches/CVE-2019-6438 
slurm-llnl-16.05.9/debian/patches/CVE-2019-6438
--- slurm-llnl-16.05.9/debian/patches/CVE-2019-6438 2019-05-27 
09:07:56.0 +0200
+++ slurm-llnl-16.05.9/debian/patches/CVE-2019-6438 2019-02-12 
23:32:08.0 +0100
@@ -65,14 +65,3 @@
  void *slurm_try_xmalloc(size_t , const char *, int , const char *);
  void slurm_xfree(void **, const char *, int, const char *);
  void *slurm_xrealloc(void **, size_t, bool, const char *, int, const char *);
 slurm-llnl-16.05.9.orig/contribs/perlapi/libslurm/perl/slurm-perl.h
-+++ slurm-llnl-16.05.9/contribs/perlapi/libslurm/perl/slurm-perl.h
-@@ -17,7 +17,7 @@
- #endif
- 
- extern void slurm_xfree(void **, const char *, int, const char *);
--extern void *slurm_xmalloc(size_t, bool, const char *, int, const char *);
-+extern void *slurm_xmalloc(uint64_t, bool, const char *, int, const char *);
- 
- extern void slurm_api_clear_config(void);
- 

Bug#929297: minissdpd: CVE-2019-12106

[Chris Lamb]

Hi Moritz,

> > > Chris, thanks for your proposal to update Stretch, I very much
> > > appreciate it.
[…]
> This doesn't warrant a DSA, feel free to fix it via a point release instead.

Sure thing. Proposed in #929613.


Regards,

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

Bug#929615: libconvert-units-perl: latest-debian-changelog-entry-reuses-existing-version

[Andreas Beckmann]

Source: libconvert-units-perl
Version: 1:0.43-2
Severity: serious

W: libconvert-units-perl: latest-debian-changelog-entry-reuses-existing-version 
1:0.43-2 == 0.43-2 (last used: Mon, 17 Dec 2001 22:33:30 +0100)
N: 
N:The latest changelog entry has a version that matches one used in the
N:specified previous entry. All versions of a source package must be
N:unique even after a leading epoch has been stripped off.
N:
N:Files generated by the current version of this source package would
N:conflict with some historical files. This is because the Debian archive
N:does not allow multiple files with the same name and different contents
N:and the generated .dsc, .deb, etc. do not embed the epoch in their
N:filenames.
N:
N:Please pick another version, for example by increasing the Debian
N:revision.
N:
N:Severity: normal, Certainty: certain
N:
N:Check: changelog-file, Type: binary

snapshot.debian.org knows about 0.43-9, the changelog mentions 0.43-10,
so 1:0.43-11 should be a safe new version number to use.


Andreas

PS: I do not want to repeat https://bugs.debian.org/929614

Bug#879007: Same problem

[Gabriel Rolland [Res Novae]]

Same problem here.
Is it not possible to have an update for the stable release?
What is the procedure for applying the proposed patch?

Processed: naist-jdic: 0.4.3-4 (lenny) was overwritten by 1:0.4.3-4 (jessie) on archive.debian.org

[Debian Bug Tracking System]

Processing control commands:

> close -1 1:0.4.3-18
Bug #929614 [naist-jdic,naist-jdic-utf8] naist-jdic: 0.4.3-4 (lenny) was 
overwritten by 1:0.4.3-4 (jessie) on archive.debian.org
Marked as fixed in versions naist-jdic/1:0.4.3-18.
Bug #929614 [naist-jdic,naist-jdic-utf8] naist-jdic: 0.4.3-4 (lenny) was 
overwritten by 1:0.4.3-4 (jessie) on archive.debian.org
Marked Bug as done

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

Bug#929614: naist-jdic: 0.4.3-4 (lenny) was overwritten by 1:0.4.3-4 (jessie) on archive.debian.org

[Andreas Beckmann]

Package: naist-jdic,naist-jdic-utf8
Version: 0.4.3-4
Severity: grave
User: debian...@lists.debian.org
Usertags: piuparts
Control: close -1 1:0.4.3-18

naist-jdic/lenny is no longer installable from archive.debian.org
(noticed in a piuparts test)

  Get:1 http://archive.debian.org lenny/main libchasen2 2.4.4-2+lenny2 [50.7kB]
  Get:2 http://archive.debian.org lenny/main chasen-dictutils 2.4.4-2+lenny2 
[24.1kB]
  Get:3 http://archive.debian.org lenny/main naist-jdic 0.4.3-4 [5513kB]
  Get:4 http://archive.debian.org lenny/main naist-jdic-utf8 0.4.3-4 [7156B]
  Get:5 http://archive.debian.org lenny/main chasen 2.4.4-2+lenny2 [460kB]
  Failed to fetch 
http://archive.debian.org/debian/pool/main/n/naist-jdic/naist-jdic_0.4.3-4_all.deb
  Size mismatch
  Failed to fetch 
http://archive.debian.org/debian/pool/main/n/naist-jdic/naist-jdic-utf8_0.4.3-4_all.deb
  Size mismatch
  Fetched 3910kB in 0s (27.9MB/s)
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

Lintian reports for 1:0.4.3-4

W: naist-jdic: latest-debian-changelog-entry-reuses-existing-version 1:0.4.3-4 
== 0.4.3-4 (last used: Tue, 30 Sep 2008 09:14:31 +0900)
N: 
N:The latest changelog entry has a version that matches one used in the
N:specified previous entry. All versions of a source package must be
N:unique even after a leading epoch has been stripped off.
N:
N:Files generated by the current version of this source package would
N:conflict with some historical files. This is because the Debian archive
N:does not allow multiple files with the same name and different contents
N:and the generated .dsc, .deb, etc. do not embed the epoch in their
N:filenames.
N:
N:Please pick another version, for example by increasing the Debian
N:revision.
N:
N:Severity: normal, Certainty: certain
N:
N:Check: changelog-file, Type: binary

The lenny .debs have been replaced by the jessie ones:
http://archive.debian.org/debian/pool/main/n/naist-jdic/


Andreas

Bug#925173: ltsp: codename detection code not useful for stable

[Wolfgang Schweer]

On Sun, May 26, 2019 at 02:27:34PM -0700, Vagrant Cascadian wrote:
> Apparently, it's already impacting buster:
> 
> $ sudo ltsp-build-client
> NOTE: adding default dist and components to security mirror:
> http://security.debian.org/ 10.0/updates main
> ERROR: invalid distribution: 10.0

iirc, this change came with d-i rc 1 (which makes sense).

Wolfgang


signature.asc
Description: PGP signature

Bug#923930: marked as done (FTBFS: FAIL test_chain (exit status: 1))

[Debian Bug Tracking System]

Your message dated Mon, 27 May 2019 07:33:40 +
with message-id 
and subject line Bug#923930: fixed in heimdal 7.5.0+dfsg-3
has caused the Debian Bug report #923930,
regarding FTBFS: FAIL test_chain (exit status: 1)
to be marked as done.

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

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


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

heimdal fails to build from source, both in Buster and Sid. It is
failing in one of the tests. Relevant snippet below and full build log
is accessible at:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/heimdal_7.5.0+dfsg-2.1.rbuild.log.gz

=
   Heimdal 7.5.0: lib/hx509/test-suite.log
=

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

.. contents:: :depth: 2

FAIL: test_chain


cert -> root
cert -> root
cert -> root
sub-cert -> root
sub-cert -> sub-ca -> root
sub-cert -> sub-ca
sub-cert -> sub-ca -> root
sub-cert -> sub-ca -> root
sub-cert -> sub-ca -> root
max depth 2 (ok)
max depth 1 (fail)
ocsp non-ca responder
ocsp ca responder
ocsp no-ca responder, missing cert
ocsp no-ca responder, missing cert, in pool
ocsp no-ca responder, keyHash
ocsp revoked cert
ocsp print reply resp1-ocsp-no-cert
ocsp print reply resp1-ca
ocsp print reply resp1-keyhash
ocsp print reply resp2
ocsp verify exists
ocsp verify not exists
ocsp verify revoked
crl non-revoked cert
FAIL test_chain (exit status: 1)

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

Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: heimdal
Source-Version: 7.5.0+dfsg-3

We believe that the bug you reported is fixed in the latest version of
heimdal, 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.
Brian May  (supplier of updated heimdal 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, 21 May 2019 18:04:35 +1000
Source: heimdal
Architecture: source
Version: 7.5.0+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Brian May 
Changed-By: Brian May 
Closes: 923930 928966 929064
Changes:
 heimdal (7.5.0+dfsg-3) unstable; urgency=high
 .
   * CVE-2018-16860: Samba AD DC S4U2Self/S4U2Proxy unkeyed checksum.
 Closes: #928966.
   * CVE-2019-12098: Always confirm PA-PKINIT-KX for anon PKINIT.
 Closes: #929064.
   * Update test certificates to pre 2038 expiry. Closes: #923930.
Checksums-Sha1:
 a7dfb3243e2cf59d0334967a3db53c94b4bea41e 3579 heimdal_7.5.0+dfsg-3.dsc
 1ba39f71a5627a23afbc8b987362831bed764f7d 8955005 heimdal_7.5.0+dfsg.orig.tar.gz
 b3bd61ebd0bddce418bbf8330a2fd30690820244 461448 
heimdal_7.5.0+dfsg-3.debian.tar.xz
 7d7b658952dc64e9aebb09aa58c581a692473528 7458 
heimdal_7.5.0+dfsg-3_source.buildinfo
Checksums-Sha256:
 f1ecfa0cbd70cb43c5ab59eb6661d4364212df69d76824a9f27861bbfa6e750c 3579 
heimdal_7.5.0+dfsg-3.dsc
 489119b7a1a900b88163765654dc59cba9a321b078fafc76629e2b85ef140867 8955005 
heimdal_7.5.0+dfsg.orig.tar.gz
 35f14816be232a043326eea977ebb1edff5a8f9223919ee18a88148565ab3e5c 461448 
heimdal_7.5.0+dfsg-3.debian.tar.xz
 3b13ca5b0389856531546f5d66d97bbf8e7b174829c14c6fd5f5031e52677430 7458 
heimdal_7.5.0+dfsg-3_source.buildinfo
Files:
 2e2a528050fddb368c8b1fc04dbeb8ed 3579 net optional heimdal_7.5.0+dfsg-3.dsc
 b45b9d03cdd4f3288e79feba99e13a51 8955005 net optional 
heimdal_7.5.0+dfsg.orig.tar.gz
 04177cfa68af6bffa74dcf3299d4bcab 461448 net optional 
heimdal_7.5.0+dfsg-3.debian.tar.xz