Bug#905335: marked as done (botan: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 08:10:13 +
with message-id 
and subject line Bug#905335: fixed in botan 2.8.0-1
has caused the Debian Bug report #905335,
regarding botan: Incomplete debian/copyright?
to be marked as done.

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

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


-- 
905335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: botan
Version: 2.7.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Laszlo Boszormenyi (GCS) , 
ftpmas...@debian.org

Hi,

I just ACCEPTed botan from NEW but noticed it was missing attribution 
in debian/copyright for at least a pcks11 code copy and (possibly?) a
curve25519 code copy.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: botan
Source-Version: 2.8.0-1

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated botan 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, 01 Jan 2019 11:31:02 +
Source: botan
Binary: botan libbotan-2-8 libbotan-2-dev libbotan-2-doc python3-botan
Architecture: source amd64 all
Version: 2.8.0-1
Distribution: experimental
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 botan  - multiplatform crypto library (2.x version)
 libbotan-2-8 - multiplatform crypto library (2.x version)
 libbotan-2-dev - multiplatform crypto library (2.x version)
 libbotan-2-doc - multiplatform crypto library (2.x version)
 python3-botan - multiplatform crypto library (2.x version), Python3 module
Closes: 905335 909476 916970
Changes:
 botan (2.8.0-1) experimental; urgency=medium
 .
   * New upstream release.
   * Library transition from libbotan-2-7 to libbotan-2-8 .
   * Fix ARM CPU detection (closes: #916970).
   * Overhaul copyright file (closes: #905335).
   * Update Standards-Version to 4.3.0 .
 .
   [ Chris Lamb  ]
   * Make the build reproducible (closes: #909476).
Checksums-Sha1:
 4628aaa26a3d5c7c11f50f1d0e25f32f9b0ed0d0 2047 botan_2.8.0-1.dsc
 709be6570b974209c6916b0fcd6dd508d55d1a05 7214880 botan_2.8.0.orig.tar.gz
 f3d0ab019f2b90934811696edff28fc4ecf87f2c 5712 botan_2.8.0-1.debian.tar.xz
 e2b04a8fcc4d4cbba99560b890373e4f923fd664 3784668 botan-dbgsym_2.8.0-1_amd64.deb
 c95ddb45a6c1b81385f45d32ddeb754d064c2e89 10208 botan_2.8.0-1_amd64.buildinfo
 6a5605278c16da45fb66bdb813e2c9d98a02010f 187708 botan_2.8.0-1_amd64.deb
 7b69fcf7e94bafd275e38bfee15d1d64895f2ef6 35533272 
libbotan-2-8-dbgsym_2.8.0-1_amd64.deb
 78ece0f790953ef7d5c9cac764e61970b0a811d0 1525396 libbotan-2-8_2.8.0-1_amd64.deb
 3e7b2a20536eb3ad99d6bd04f33e02726b95e783 2301576 
libbotan-2-dev_2.8.0-1_amd64.deb
 10ee26541775d70c7c395a1bc60d3f03c194a19c 404868 libbotan-2-doc_2.8.0-1_all.deb
 cea2a57bd3b46d2631013d94885bf658a87944ca 12916 python3-botan_2.8.0-1_amd64.deb
Checksums-Sha256:
 45091a09e55821bcb1c78af3122b3c5d9ea46b0fd293239e2dcbc5e86dbd3ce0 2047 
botan_2.8.0-1.dsc
 3d2b359394261c3b173f0d89bba814d6794d95dd057d958365a3cc2d52cbdcd0 7214880 
botan_2.8.0.orig.tar.gz
 3d43f19493f153275db891a47f89bad134621e968a0a91a05a6d74cdb90ddced 5712 
botan_2.8.0-1.debian.tar.xz
 b1e7c87d2ee003407690a05a4cf45820280311cbea04a8bb09f8ac67d77fafc1 3784668 
botan-dbgsym_2.8.0-1_amd64.deb
 129827fb103ff1e1d5f58a9750ac7cbba6295b54787b7be7bcdc980038b7841d 10208 
botan_2.8.0-1_amd64.buildinfo
 e6695ffa29913bfe744d6064dacdc10d95e6132d86be9e870a0f46002b7f3930 187708 
botan_2.8.0-1_amd64.deb
 2e3a9fa0cd8dbea4ad61c12b570d1a4537d338e38496de6e735b8537b104e53b 35533272 
libbotan-2-8-dbgsym_2.8.0-1_amd64.deb
 bf396d8e3a39b27027293eb9717298c2b061a24e718a3d2046e6b54c3951920b 1525396 
libbotan-2-8_2.8.0-1_amd64.deb
 8bfda26bd6f757ae3840342d519e733d00057ae006ac1bcd8d3ff6a9f8747e01 2301576 
libbotan-2

Processed: tagging 918188

[Debian Bug Tracking System]

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

> tags 918188 + ftbfs
Bug #918188 [src:linux] linux: FTBFS on arm64
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#911832: polyfill should be dropped

[David Prévot]

Hi Kunal,

Le 04/01/2019 à 16:12, Kunal Mehta a écrit :
> On 1/3/19 6:57 PM, David Prévot wrote:
>> Le 04/01/2019 à 12:50, Kunal Mehta a écrit :
>>> This patch adds overrides for all symfony/polyfill-* packages to
>>> pkg-php-tools itself, so all packages will automatically use it and no
>>> longer automatically depend upon php-symfony-polyfill-* (and will cover
>>> all current dependencies).
>>
>> Overrides can be added “locally” (for the build, in
>> debian/pkg-php-tools-overrides, see e.g. twig). Anyway, this is not the
>> only needed step, see below.
> 
> Right. Are you saying you'd rather have the overrides in the individual
> packages instead of in pkg-php-tools?

Since packages need to be rebuilt from source as binNMU are still (even
for arch-all only source packages) not allowed for binary-all, we don’t
need an archive-wide workaround (and you already pointed that there are
only a handful of packages involved).

> I'm happy to prepare patches (and
> NMUs if necessary) either way

Great. Feel free to team-upload stuff under the PHP PEAR (and Composer)
umbrella too.

> but I think we still need a pkg-php-tools
> patch to support dropping the version constraint, which is included in
> my current merge request.

No opinion about pkg-php-tools, I’ll let Mathieu follow up.

>>> And this one drops php-symfony-polyfill-*

Just for the record (since I failed to point why those polyfill were
packaged in first place), those packages may be useful in backport-style
environments where the PHP version or extension constraints are
different than the usual Debian environments.

Also, I don’t mind if php-symfony-polyfill is gracefully removed from
testing (and thus the next Buster release) unless someone feels that it
may be useful.

[…]
>> You also (rightfully) changed the autoload files. It’s not “just” a
>> matter of removing the (build-)dependencies.
> 
> Ack, I just wrote the commit message before I realized those also needed
> to be removed.

Fine by me (I just had to look at the actual MR to find out if you took
everything into account).

Regards

David



signature.asc
Description: OpenPGP digital signature

Processed: Bug #918153 in lnav marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918153 [src:lnav] lnav: FTBFS (failing test)
Added tag(s) pending.

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

Bug#918153: Bug #918153 in lnav marked as pending

[Salvatore Bonaccorso]

Control: tag -1 pending

Hello,

Bug #918153 in lnav 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/carnil/lnav/commit/b69adf9adbbc760b66a72da3791277e90e5c5455


Disable test_sql completely as contains time dependent tests

Fixes "FTBFS (failing test)"

Closes: #918153

Thanks: Santiago Vila and Adrian Bunk


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918153

Bug#899595: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, 2019-01-04 at 08:39 +0900, Hideki Yamane wrote:
> Hi,
> 
>  With Bugs search "Cleaner view", I've found those bugs are not closed
>  in unstable but are done in experimental. 

Hi, I am well aware of these, thanks.

> Do you have a plan to put them
>  into unstable, or just apply only those fixes to current unstable packages?

Not right now.
> 
>  I know xfce4.13 series are development release, but some projects like
> Fedora
>  and Xubuntu have released 4.13 series as discussed at
>  https://mail.xfce.org/pipermail/xfce4-dev/2018-July/032143.html
>  
We already shipped Xfce development release in stable previously, and I don't
want to do that again, so no, I'm waiting for stable releases. If it happens
before freeze, fine, if not then it'll be for Bullseye.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlwvGVkACgkQ3rYcyPpX
RFux+Af+LhC020PuKdWr6uwIl4uJtR6WintK2RXrL0xTMXaU/hjFjRP0MpxJlkmR
DfDlA0tYCsUueNaJl5WkGUbsAepyIW77mr6yLOgikL2mveIRAMI4XGMHjj0nzu03
QEDGlk7BeAMn7DIuHg4W/pwnlSCb//CoTNoJmb4CqdU7JNolMuoBgBRk4vk6Z73i
JZi53w1corx5Bq3juv+ETkb4UoJBKCoRSdq87l2bX5klqyOFxn0Rz8K+Vo1lqmry
/gGdplBGFDh1EP3fyD98Bb8pjkemmm+VN9taBnEvXCAnVSQfEI48ltK6GHXVATMp
bOJu2ZnzOCCiYIOdeIELCFq2q1REmg==
=793v
-END PGP SIGNATURE-

Bug#911285: Current version is incompatible with Thunderbird 60

[Bastian Venthur]

On 03.01.19 23:35, Moritz Mühlenhoff wrote:


The package wasn't updated for a year, shall we remove it?


Probably, people can easily use the extension from Mozillas Addon Store.


Cheers,

Bastian

--
Dr. Bastian Venthur  http://venthur.de
Debian Developer venthur at debian org

Bug#918157: openmpi seems broken on 32 bits architectures

[Graham Inggs]

Control: user debian...@lists.debian.org
Control: usertag -1 regression

Hi

In Ubuntu, the upload of openmpi 3.1.3-7 has caused numerous
autopkgtest failures on i386 and armhf [1].  Some affected packages
are: combblas; dune-grid, lammps, liggghts, petsc, ray and
superlu-dist.

I re-tried these tests after the upload of pmix 3.1.0~rc2-2 but the
failures persisted, e.g. combblas [2],

Regards
Graham


[1] 
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#openmpi
[2] http://autopkgtest.ubuntu.com/packages/c/combblas/disco/i386

Bug#913003: marked as done (ruby-rack: CVE-2018-16470: Possible DoS vulnerability in Rack)

[Debian Bug Tracking System]

Your message dated Fri, 4 Jan 2019 14:04:39 +0530
with message-id <302be855-dae1-1abe-bd38-8cc7e35ce...@onenetbeyond.org>
and subject line already fixed
has caused the Debian Bug report #913003,
regarding ruby-rack: CVE-2018-16470: Possible DoS vulnerability in Rack
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.)


-- 
913003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack
Version: 2.0.5-1
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for ruby-rack, which is only
affecting experimental version. Filling with RC severity as the
vulernable version should not enter unstable.

CVE-2018-16470[0]:
Possible DoS vulnerability in Rack

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-16470
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16470
[1] https://www.openwall.com/lists/oss-security/2018/11/05/1

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Control: fixed -1 2.0.6-1



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

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

[pali]

Hello!

The main problem is that DBD::mysql touches internal libmariadb.so
structures which for obvious reasons do not have stable nor documented
API.

In DBD::MariaDB I replaced this code by usage of public Connector/C API.
But for buggy Perl application this may cause incompatibility.

Changes are in this pull request:
https://github.com/gooddata/DBD-MariaDB/pull/63

To prevent breakage of other Perl modules which uses DBD::mysql I
strongly suggest to stick with MySQL Connector/C or use MariaDB 10.0 or
10.1 which is known to work.

One of the reason why I forked and created DBD::MariaDB instead of
touching DBD::mysql is support for MariaDB 10.2+, 10.3+.

Basically touching these parts of DBD::mysql code may cause problems for
applications which misuse bugs in DBD::mysql. There was long discussion
about it 2 years ago and people decided that it rather should not be
changed. (Reason for fork and move to DBD::MariaDB). If you want to
prevent any possible breakage, then you have no other option and should
stick with either MySQL 5.5-5.7 or with MariaDB 10.0/10.1.

And if you really want to update MariaDB to 10.3, I strongly suggest to
also update packages from DBD::mysql to DBD::MariaDB.

For DBD::MariaDB we have large test coverage with different MySQL and
MariaDB versions, including MariaDB 10.3 and 10.4 series, see:

https://travis-ci.org/gooddata/DBD-MariaDB

Seems that in DBD::mysql upstream rather decided to drop MariaDB 10.3
support as trying to fix it, see:

https://github.com/perl5-dbi/DBD-mysql/commit/0c4fee5d928efdf937fdf5fdba5f4873b01848ef

And rather started fixing support for MySQL 8.0 series:

https://github.com/perl5-dbi/DBD-mysql/commit/08df02eabf08de62a5e363fbf852ca51f685a8ce

Maybe another option can be inclusion of MySQL 8.0 for DBD::mysql?

Processed: Re: pmix (was: openmpi) seems broken on 32 bits architectures

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libpmix2 3.1.0~rc2-1
Bug #918157 [src:openmpi] openmpi seems broken on 32 bits architectures
Bug reassigned from package 'src:openmpi' to 'libpmix2'.
No longer marked as found in versions openmpi/3.1.3-7.
Ignoring request to alter fixed versions of bug #918157 to the same values 
previously set
Bug #918157 [libpmix2] openmpi seems broken on 32 bits architectures
Marked as found in versions pmix/3.1.0~rc2-1.
> retitle -1 libpmix2 seems broken on 32 bits architectures
Bug #918157 [libpmix2] openmpi seems broken on 32 bits architectures
Changed Bug title to 'libpmix2 seems broken on 32 bits architectures' from 
'openmpi seems broken on 32 bits architectures'.

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

Bug#918157: pmix (was: openmpi) seems broken on 32 bits architectures

[Gilles Filippini]

Control: reassign -1 libpmix2 3.1.0~rc2-1
Control: retitle -1 libpmix2 seems broken on 32 bits architectures

On 2019-01-04 09:41, Graham Inggs wrote:

Control: user debian...@lists.debian.org
Control: usertag -1 regression

Hi

In Ubuntu, the upload of openmpi 3.1.3-7 has caused numerous
autopkgtest failures on i386 and armhf [1].  Some affected packages
are: combblas; dune-grid, lammps, liggghts, petsc, ray and
superlu-dist.

I re-tried these tests after the upload of pmix 3.1.0~rc2-2 but the
failures persisted, e.g. combblas [2],


I tried a build against openmpi 3.1.3-6 and experienced the very same 
FTBFS. Then I downgraded libpmix2 to 3.0.2-2 and it worked. It worked 
against openmpi 3.1.3-7 as well.

The culprit is then pmix 3.1.0~rc2.

Thanks,

_g.

Bug#918153: marked as done (lnav: FTBFS (failing test))

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 09:52:45 +
with message-id 
and subject line Bug#918153: fixed in lnav 0.8.4-5
has caused the Debian Bug report #918153,
regarding lnav: FTBFS (failing test)
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.)


-- 
918153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lnav
Version: 0.8.4-4
Severity: serious
Tags: ftbfs

Hello Salvatore.

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


[...]
 debian/rules binary-arch
dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --disable-static
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking 
--disable-static
configure: WARNING: unrecognized options: --disable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk

[... snipped ...]


.. contents:: :depth: 2

FAIL: test_sql.sh
=

./test_sql.sh: line 7: /<>/./test/logfile_access_log.0: Permission 
denied
cp: '/<>/./test/logfile_syslog_with_mixed_times.0' and 
'logfile_syslog_with_mixed_times.0' are the same file
test: ../src/lnav-test -d /tmp/lnav.err -n -c :goto 1 -c :create-logline-table 
join_group -c :goto 2 -c ;select logline.log_line as llline, 
join_group.log_line as jgline from logline, join_group where logline.col_0 = 
join_group.col_2 -c :write-csv-to - /<>/./test/logfile_for_join.0
querying against stdin is not working?
--- -   2019-01-03 04:48:21.773541145 +
+++ test_sql.sh_57.tmp  2019-01-03 04:48:21.760979015 +
@@ -1,4 +1,4 @@
 log_time
-2018-11-03 09:23:38.000
-2018-11-03 09:23:38.000
-2018-11-03 09:23:38.000
+2019-11-03 09:23:38.000 
+2019-11-03 09:23:38.000 
+2019-11-03 09:23:38.000 
FAIL test_sql.sh (exit status: 1)


Testsuite summary for lnav 0.8.4

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

See test/test-suite.log
Please report to l...@googlegroups.com

make[4]: *** [Makefile:1350: test-suite.log] Error 1
make[4]: Leaving directory '/<>/test'
make[3]: *** [Makefile:1458: check-TESTS] Error 2
make[3]: Leaving directory '/<>/test'
make[2]: *** [Makefile:1798: check-am] Error 2
make[2]: Leaving directory '/<>/test'
make[1]: *** [Makefile:472: check-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:7: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -B" on 2019-01-03
but it also fails here:

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

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

It is interesting to see that the build log in reproducible-builds (made on 
2018-12-28)
fails in a slightly different way:

-2018-11-03 09:23:38.000
-2018-11-03 09:23:38.000
-2018-11-03 09:23:38.000
+2020-11-03 09:23:38.000 
+2020-11-03 09:23:38.000 
+2020-11-03 09:23:38.000

(As usual, 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: lnav
Source-Version: 0.8.4-5

We believe that the bug you reported is fixed in the latest version of
lnav, 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 918...@bugs.debia

Bug#917042: marked as done (dtfabric: Wrong name)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 10:10:11 +
with message-id 
and subject line Bug#917042: fixed in dtfabric 20180808-1.1
has caused the Debian Bug report #917042,
regarding dtfabric: Wrong name
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.)


-- 
917042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dtfabric
Version: 20180808-1
Severity: serious
Control: tag -1 pending

Dear Maintainer,

the dtfabric package is a Python3 library which means that its name must
be prefixed with "python3-". (Python policy 3.3)

I am marking this bug as pending because I intend to upload a new
version that will fix this bug -- and will add a Python 2 package, in
order to be able to fix #914607 without having to migrate Plaso to
Python 3 _right now_.

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Source: dtfabric
Source-Version: 20180808-1.1

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated dtfabric 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: Sat, 22 Dec 2018 21:56:35 +0100
Source: dtfabric
Binary: python-dtfabric python3-dtfabric
Architecture: source all
Version: 20180808-1.1
Distribution: unstable
Urgency: medium
Maintainer: SZ Lin (林上智) 
Changed-By: Hilko Bengen 
Description:
 python-dtfabric - Tooling for data type and structure management
 python3-dtfabric - Tooling for data type and structure management
Closes: 917042
Changes:
 dtfabric (20180808-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Add python3- prefix to dtfabric, introduce Python 2 package
 (Closes: #917042)
   * Move package to section python
Checksums-Sha1:
 5ffb042ac55b45de8b1441c2fb507be26979b002 2087 dtfabric_20180808-1.1.dsc
 455f4ee315a6bcadc390ae4757c6ada0cf7e3921 2380 
dtfabric_20180808-1.1.debian.tar.xz
 5cf3d922370d2b354f941c2e153e044206410bc1 6655 
dtfabric_20180808-1.1_amd64.buildinfo
 ea41f35b73c05419267924a534ac022612f7350d 17692 
python-dtfabric_20180808-1.1_all.deb
 46979407446ff61a5b1ab2c2c926ef746b8f4bf4 18680 
python3-dtfabric_20180808-1.1_all.deb
Checksums-Sha256:
 7c8d357efdd79f5ea803f32103fcafe1a1e6d6d5cc82232b7a88ebede226ea18 2087 
dtfabric_20180808-1.1.dsc
 c9a44439efa553da6028a5d875498d0bfa555718d9996b62b055c5fe11fc5a39 2380 
dtfabric_20180808-1.1.debian.tar.xz
 1ecc86fe24b113e454ca1085db6bd0aa4708622c2714b0038ec7453f61aa08b4 6655 
dtfabric_20180808-1.1_amd64.buildinfo
 436fc69a9767d18e5332f06894f36be016b1f49ffaf8a1a9c37dd883f4aaeee9 17692 
python-dtfabric_20180808-1.1_all.deb
 f17943728c1b91550982184f95619725b8825346e8a6f9a04517e3204b5cc0bb 18680 
python3-dtfabric_20180808-1.1_all.deb
Files:
 2a321ac38cf323430c0d19f57ff5e51d 2087 python optional dtfabric_20180808-1.1.dsc
 29d91492541a0509b67eab5171a5d509 2380 python optional 
dtfabric_20180808-1.1.debian.tar.xz
 61ddd5905d5180da076c3e03b7616033 6655 python optional 
dtfabric_20180808-1.1_amd64.buildinfo
 487d2e4f7cf428ca6ffdc0236ed65e7e 17692 python optional 
python-dtfabric_20180808-1.1_all.deb
 af80e47d5ed86c4780a916679d8e3c63 18680 python optional 
python3-dtfabric_20180808-1.1_all.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlwepWYSHGJlbmdlbkBk
ZWJpYW4ub3JnAAoJEHW3EGNcITp+gfIP/iohUEfUlutv9/CFs8CZdXkXyW/NcWZi
rQ7LoJheA4Yqbd15TWA7Gkujel98oSEkOZVpddDicLMw0ncExM+u05LyI4t3hyGt
7U9lVLVO4PvT5mYBqasNgtC3Ey5NBPK+kVov4ZRDRre581troPfEP7OBfyFx8Uee
vjqO5cW8YGfFnDnBgn3osH+YSduO+tXHu+OulyeO5K5uBtXOj/KfeJMRCK/yIpFp
ePZS+JLUeSQ8uA93ybr57JRBLkjNTUHcoSu6YvnpBVtNa8EYJqvXUSQqAGV8tTjY
2TdNcQxgcXCucqdOMshXVpYLtzWmi7iDuWrR/OmDjoenwYsUpswOF8NwUkqhzAZJ
i+OEqqvUTkOflbE7HmO3hPCXtpDbxi5UnfjK9TXBV5KE5rzQTdYT/ABN9c8XqfWI
9NeKztNh4AC0/Cpqb40ZaLlnND+lFQwd6AnvUbbKegF3yL/Xgz/xAQx8ETgdEXZN
+MA6H7Y5COLTnDRfNZVh3xifeJ2w1udNojycGcWhNz+VLe6M5Vr2tt5RHBzIBcpC
0Pl/6CY2kOuKrmV+csI8alzjeuuv/Rwa6ngiVCJZzHRveI2GnP6KEYl2v7dnArUx
r896AYPnXbh+4zQaGdPF2CTA47y45+odOwR7vjOY1YvIqyRMhzTpBgZSvsiCo8bZ
byJfiowIINjp

debian-bugs-rc@lists.debian.org

[Debian Bug Tracking System]

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

> fixed #917372 2.6+ds-1
Bug #917372 [mnemosyne] mnemosyne: can't start, unable to load file, query 
failed
Marked as fixed in versions mnemosyne/2.6+ds-1.
> thanks
Stopping processing here.

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

Processed: Bug #892561 in ruby-session marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892561 [src:ruby-session] ruby-session: FTBFS and Debci failure with ruby 
2.5
Added tag(s) pending.

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

Bug#892561: Bug #892561 in ruby-session marked as pending

[Cédric Boutillier]

Control: tag -1 pending

Hello,

Bug #892561 in ruby-session 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/ruby-team/ruby-session/commit/e5a1d22c1c79c5cd0505067ed795f3da1524fe35


Add patch to decrease time bound in tests because of speed of recent ruby 
interpreters (Closes: #892561)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892561

Bug#898755: marked as done (node-miller-rabin: FTBFS and flaky autopkgtests)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 11:25:29 +
with message-id 
and subject line Bug#898755: fixed in node-miller-rabin 4.0.1-3
has caused the Debian Bug report #898755,
regarding node-miller-rabin: FTBFS and flaky 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.)


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

Source: node-miller-rabin
Version: 4.0.1-1
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: flaky

Hi Maintainer

Since 2017-12-28, node-miller-rabin has FTBFS in unstable [1] with the 
following error:


  0 passing (2s)
  1 failing

  1) Miller-Rabin
   should test number for primality:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, 
ensure "done()" is called; if returning a Promise, ensure it resolves.

  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

The same test is run during autopkgtests and often fails, especially on 
the slower architectures which are tested in Ubuntu, but not in Debian.


I believe this is another example of the unreliable timing in tests 
being discussed in #853035.


I was able to work around the problem in Ubuntu by increasing the test 
timeout to 8000ms (4000ms was not sufficient on armhf) as per the patch 
below:


--- a/test/api-test.js
+++ b/test/api-test.js
@@ -4,6 +4,7 @@

 describe('Miller-Rabin', function() {
   it('should test number for primality', function() {
+this.timeout(8000);
 assert(!mr.test(new bn(221)));
 assert(mr.test(new bn(257)));

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/history/amd64/node-miller-rabin.html
--- End Message ---
--- Begin Message ---
Source: node-miller-rabin
Source-Version: 4.0.1-3

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-miller-rabin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Jan 2019 11:01:29 +0100
Source: node-miller-rabin
Binary: node-miller-rabin
Architecture: source
Version: 4.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 898755
Description: 
 node-miller-rabin - Miller Rabin algorithm for primality test
Changes:
 node-miller-rabin (4.0.1-3) unstable; urgency=medium
 .
   * team upload
   * Increase timeout in autopkgtest (Closes: #898755)
Checksums-Sha1: 
 c9dcc79517ea694ed36adac4602bf5911338814f 2208 node-miller-rabin_4.0.1-3.dsc
 9bcf0668efb633af7d584350f46bac47acac2dfb 3208 
node-miller-rabin_4.0.1-3.debian.tar.xz
Checksums-Sha256: 
 1b86d6f243ec2779173815d12d0e2ee44cfa81fb89e3f59101bf047df3205b38 2208 
node-miller-rabin_4.0.1-3.dsc
 4012a4fd4854ff8de3536fee185065480b7d8bb434b6779822128b846ef76932 3208 
node-miller-rabin_4.0.1-3.debian.tar.xz
Files: 
 cd53b90586a62388b89b2766047a288a 2208 javascript optional 
node-miller-rabin_4.0.1-3.dsc
 2c1f85b14faad94655279ccd0e337ce8 3208 javascript optional 
node-miller-rabin_4.0.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlwvL2EQHHlhZGRAZGVi
aWFuLm9yZwAKCRD210ynyZnu6SGyD/9ZcY6xnA/pNFokQUC8Gz31Nsj4MUK5fgBa
ckqCVD0BWB53JZ4I/QUXWA2RlPvLBYauMIbVDafcFbBsvtleJw0An5AFAiwZDbCM
l/1pBzurZzM2lZ0ofRHESFox+ZInKHpM5RyWKNT2ZzFhvCzwJuW/87W6lM3zMkZg
NlEOGd5lQiAPsTrzNth3EZKPkFN1EvigWUmahsACaEBctu6lEUaIFt6V5UO8zTVo
b1o0vRu2gTlSwgiPPh8nfYhmXkh5Ey5UvClWLF40UjVpTk9W6LmaNpwtzV3W7sbi
NvhNPLQfH/SL03EkDJg

Bug#892658: marked as done (node-ip FTBFS with mocha 4.0.1-3)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 11:25:18 +
with message-id 
and subject line Bug#892658: fixed in node-ip 1.1.5-2
has caused the Debian Bug report #892658,
regarding node-ip FTBFS with mocha 4.0.1-3
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.)


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

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-ip-1.1.5'
mocha --reporter spec
/usr/lib/nodejs/mocha/lib/suite.js:47
throw new Error('Suite `title` should be a "string" but "' + typeof title + 
'" was given instead.');
^

Error: Suite `title` should be a "string" but "undefined" was given instead.
at new Suite (/usr/lib/nodejs/mocha/lib/suite.js:47:11)
at Function.exports.create (/usr/lib/nodejs/mocha/lib/suite.js:31:15)
at Object.create (/usr/lib/nodejs/mocha/lib/interfaces/common.js:104:27)
at context.describe.context.context 
(/usr/lib/nodejs/mocha/lib/interfaces/bdd.js:44:27)
at /build/1st/node-ip-1.1.5/test/api-test.js:363:9
at Array.forEach ()
at Suite. (/build/1st/node-ip-1.1.5/test/api-test.js:362:37)
at Object.create (/usr/lib/nodejs/mocha/lib/interfaces/common.js:112:19)
at context.describe.context.context 
(/usr/lib/nodejs/mocha/lib/interfaces/bdd.js:44:27)
at Suite. (/build/1st/node-ip-1.1.5/test/api-test.js:361:5)
at Object.create (/usr/lib/nodejs/mocha/lib/interfaces/common.js:112:19)
at context.describe.context.context 
(/usr/lib/nodejs/mocha/lib/interfaces/bdd.js:44:27)
at Suite. (/build/1st/node-ip-1.1.5/test/api-test.js:354:3)
at Object.create (/usr/lib/nodejs/mocha/lib/interfaces/common.js:112:19)
at context.describe.context.context 
(/usr/lib/nodejs/mocha/lib/interfaces/bdd.js:44:27)
at Object. (/build/1st/node-ip-1.1.5/test/api-test.js:8:1)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Module.require (module.js:579:17)
at require (internal/module.js:11:18)
at /usr/lib/nodejs/mocha/lib/mocha.js:231:27
at Array.forEach ()
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:228:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:514:10)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:484:18)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Function.Module.runMain (module.js:676:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: node-ip
Source-Version: 1.1.5-2

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

Debian distribution maintenance software
pp.
Andreas Moog  (supplier of updated node-ip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Jan 2019 09:37:15 +0100
Source: node-ip
Binary: node-ip
Architecture: source
Version: 1.1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Andreas Moog 
Closes: 892658
Description: 
 node-ip- IP address utilities for node.js
Changes:
 node-ip (1.1.5-2) unstable; urgency=medium
 .
   [ Andreas Moog ]
   * Team upload.
   * Fix FTBFS due to failing tests (Closes: #892658)
 .
   [ Xavier Guimard ]
   * Bump debhelper compatibility level to 11
   * Declare compliance with policy 4.3.0
   * Update debian/copyright format url
   * Check DEB_BUILD_OPTIONS in test
Checksums-Sha1: 
 0649898f3bf7b03f465f8dd2bf9e23b9dea2dcb3 1993 node-ip_1.1.5-2.dsc
 e68b5c5f9f617fff916867dbdee7f89

Bug#898755: marked as done (node-miller-rabin: FTBFS and flaky autopkgtests)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 11:25:23 +
with message-id 
and subject line Bug#898755: fixed in node-miller-rabin 4.0.1-2
has caused the Debian Bug report #898755,
regarding node-miller-rabin: FTBFS and flaky 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.)


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

Source: node-miller-rabin
Version: 4.0.1-1
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: flaky

Hi Maintainer

Since 2017-12-28, node-miller-rabin has FTBFS in unstable [1] with the 
following error:


  0 passing (2s)
  1 failing

  1) Miller-Rabin
   should test number for primality:
 Error: Timeout of 2000ms exceeded. For async tests and hooks, 
ensure "done()" is called; if returning a Promise, ensure it resolves.

  at done (/usr/lib/nodejs/mocha/lib/runnable.js:298:13)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:334:5)

The same test is run during autopkgtests and often fails, especially on 
the slower architectures which are tested in Ubuntu, but not in Debian.


I believe this is another example of the unreliable timing in tests 
being discussed in #853035.


I was able to work around the problem in Ubuntu by increasing the test 
timeout to 8000ms (4000ms was not sufficient on armhf) as per the patch 
below:


--- a/test/api-test.js
+++ b/test/api-test.js
@@ -4,6 +4,7 @@

 describe('Miller-Rabin', function() {
   it('should test number for primality', function() {
+this.timeout(8000);
 assert(!mr.test(new bn(221)));
 assert(mr.test(new bn(257)));

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/history/amd64/node-miller-rabin.html
--- End Message ---
--- Begin Message ---
Source: node-miller-rabin
Source-Version: 4.0.1-2

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-miller-rabin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Jan 2019 10:48:31 +0100
Source: node-miller-rabin
Binary: node-miller-rabin
Architecture: source
Version: 4.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 898755
Description: 
 node-miller-rabin - Miller Rabin algorithm for primality test
Changes:
 node-miller-rabin (4.0.1-2) unstable; urgency=medium
 .
   * team upload
   * Add patch to increase test timeout (Closes: #898755)
   * Update debian/copyright format link to https
   * Bump debhelper compatibility level to 12
   * Declare compliance to policy 4.3.0
   * Update VCS URLs
Checksums-Sha1: 
 959dce9bc1b70f18694489f2641b8f7be71dee95 2208 node-miller-rabin_4.0.1-2.dsc
 0e9b7468266f7a935a0bb1a087b368784840e17a 3164 
node-miller-rabin_4.0.1-2.debian.tar.xz
Checksums-Sha256: 
 ed1fc0a228bbadedcabd5899baa17c8f8d491da04318683b4a0e03f2af76f087 2208 
node-miller-rabin_4.0.1-2.dsc
 97faade3acbb62745fd23eeb6a97ea05958f3910c9b91e53f1391cc4843ed1f9 3164 
node-miller-rabin_4.0.1-2.debian.tar.xz
Files: 
 eb681792eb6d87485227172545795819 2208 javascript optional 
node-miller-rabin_4.0.1-2.dsc
 92527366e4123c43eb4684653fd57ad7 3164 javascript optional 
node-miller-rabin_4.0.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlwvLUAQHHlhZGRAZGVi
aWFuLm9yZwAKCRD210ynyZnu6aNLD/40mSc88wp6wPhjsMF40tat+PjYW/kHiUrZ
afqp4H1PgzJj0BSWG/h3MzjTDiq7MdVnVfOuoO/7W8CJgtIEwIuRQDZ0K5OV3To2
83S4bx5JdPAkfyjfs2QIHrMDGOvXv4jiRifFR7MOpmpjj4oMg+fq0w

Bug#892561: marked as done (ruby-session: FTBFS and Debci failure with ruby 2.5)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 11:49:01 +
with message-id 
and subject line Bug#892561: fixed in ruby-session 3.2.0-3
has caused the Debian Bug report #892561,
regarding ruby-session: FTBFS and Debci failure with ruby 2.5
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.)


-- 
892561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-session
Version: 3.2.0-2
Severity: serious
Tags: buster sid

https://ci.debian.net/packages/r/ruby-session/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-session.html

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-test-files.yaml   │
└──┘

RUBYLIB=/build/1st/ruby-session-3.2.0/debian/ruby-session/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-session/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ 
\|f\|\ require\ f\ \}
Session::VERSION <3.2.0>
Session.use_spawn 
Session.use_open3 
Loaded suite -e
Started
...lines : <[[1555047127.5061197, "-e:1: syntax error, unexpected 
tIDENTIFIER, expecting end-of-input\n"], [1555047127.5061662, "puts 42; sleep 
0.1ruby\n"], [1555047127.5061789, "  ^~~~\n"]]>
i : <0>
b : <[1555047127.5061662, "puts 42; sleep 0.1ruby\n"]>
a : <[1555047127.5061197, "-e:1: syntax error, unexpected tIDENTIFIER, 
expecting end-of-input\n"]>
tb: <1555047127.5061662>
ta: <1555047127.5061197>
F
===
Failure:  is not true.
test_9(Session::Test)
/build/1st/ruby-session-3.2.0/test/session.rb:213:in `block (2 levels) in 
test_9'
 210: # they all come back at once if thread hung sending cmd...
 211: # make sure we got output about a second apart...
 212: begin
  => 213:   assert( (tb - ta) >= 0.1 )
 214: rescue Exception
 215:   STDERR.puts "lines : <#{ lines.inspect}>"
 216:   STDERR.puts "i : <#{ i }>"
/build/1st/ruby-session-3.2.0/test/session.rb:33:in `block in timeout'
/build/1st/ruby-session-3.2.0/test/session.rb:33:in `catch'
/build/1st/ruby-session-3.2.0/test/session.rb:33:in `timeout'
/build/1st/ruby-session-3.2.0/test/session.rb:192:in `block in test_9'
/build/1st/ruby-session-3.2.0/test/session.rb:191:in `test_9'
===


Finished in 19.559281574 seconds.
--
8 tests, 8 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
87.5% passed
--
0.41 tests/s, 0.41 assertions/s
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-session-3.2.0/debian/ruby-session returned exit code 1
make: *** [debian/rules:11: binary] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-session
Source-Version: 3.2.0-3

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-session package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Jan 2019 12:01:26 +0100
Source: ruby-session
Binary: ruby-session
Architecture: source
Version: 3.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-session - persistent connections with external programs like bash (via 
pipe
Closes: 892561
Changes:
 ruby-session (3.2.0-3) unstable; urgency=medium
 .
   * Team upload
   * Use salsa.debian.org in Vcs-* fields
   * Move debian/watch to gemwatch.debian.net
   * Bump 

Processed: Re: already fixed

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.0.6-1
Bug #913003 {Done: Pirate Praveen } [src:ruby-rack] 
ruby-rack: CVE-2018-16470: Possible DoS vulnerability in Rack
Marked as fixed in versions ruby-rack/2.0.6-1.

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

Processed: Request

[Debian Bug Tracking System]

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

> tag 876060 fixed-upstream
Bug #876060 [vit] vit's error messages makes its output blow up.
Added tag(s) fixed-upstream.
> severity 876060 grave
Bug #876060 [vit] vit's error messages makes its output blow up.
Severity set to 'grave' from 'important'
>
End of message, stopping processing here.

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

Bug#913003: already fixed

[Pirate Praveen]

Control: fixed -1 2.0.6-1

Really add fixed version.




signature.asc
Description: OpenPGP digital signature

Bug#917983: marked as done (glib2.0: [experimental] FTBFS on arm64: tests/refcount/closures.c:298:main: assertion failed: (seen_thread2 != FALSE))

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 12:04:21 +
with message-id 
and subject line Bug#917983: fixed in glib2.0 2.58.2-3
has caused the Debian Bug report #917983,
regarding glib2.0: [experimental] FTBFS on arm64: 
tests/refcount/closures.c:298:main: assertion failed: (seen_thread2 != FALSE)
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.)


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

A test fails on arm64:

START: /<>/debian/build/deb/tests/refcount/closures
init 0xfde2c210
.
.
.
.
c.
.
.
.
c.
.

stopping
stopped
**
GLib:ERROR:../../../tests/refcount/closures.c:298:main: assertion failed: 
(seen_thread2 != FALSE)

I've seen this before, in 2.54.2-3. If we run too many iterations, the
test times out; but if we run too few, the main thread starves the other
threads and the test gets through its intended number of iterations in
the main thread before the other threads have been scheduled at all, by
starving the other threads.

I'm very tempted to just knock out this particular test on arm*, at
least as a build-time test (it can stay as an autopkgtest, optionally
marked as flaky, if we want that).

smcv
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.58.2-3

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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, 04 Jan 2019 08:43:36 +
Source: glib2.0
Binary: libglib2.0-0 libglib2.0-tests libglib2.0-udeb libglib2.0-bin 
libglib2.0-dev libglib2.0-dev-bin libglib2.0-data libglib2.0-doc libgio-fam
Architecture: source
Version: 2.58.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Description:
 libgio-fam - GLib Input, Output and Streaming Library (fam module)
 libglib2.0-0 - GLib library of C routines
 libglib2.0-bin - Programs for the GLib library
 libglib2.0-data - Common files for GLib library
 libglib2.0-dev - Development files for the GLib library
 libglib2.0-dev-bin - Development utilities for the GLib library
 libglib2.0-doc - Documentation files for the GLib library
 libglib2.0-tests - GLib library of C routines - installed tests
 libglib2.0-udeb - GLib library of C routines - minimal runtime (udeb)
Closes: 775854 908334 917980 917983
Changes:
 glib2.0 (2.58.2-3) unstable; urgency=medium
 .
   * Team upload
   * Release to unstable
   * Standards-Version: 4.3.0 (no changes required)
   * d/p/gvariant-test-Also-force-alignment-for-tuple-test-data.patch:
 Mark as forwarded
   * debian/Skip-unreliable-test_threaded_singleton-by-default.patch:
 Don't run test_threaded_singleton() at build-time or in the part of
 the autopkgtest run that must succeed. Run it from d/tests/flaky
 instead.
 .
 glib2.0 (2.58.2-2) experimental; urgency=medium
 .
   * Team upload
   * d/p/gvariant-test-Also-force-alignment-for-tuple-test-data.patch:
 Fix gvariant test failure on s390x by forcing more test data to be aligned
 (Closes: #917980)
   * d/p/debian/closures-test-Skip-on-arm-unless-flaky-tests-are-allowed.patch,
 d/tests/flaky:
 Only run closures test on arm* as part of a separate, flaky autopkgtest.
 This test does not seem to be reliable enough for its failures to be
 treated as release-critical, at least on arm*. If we run too many
 iterations, it fails on CPUs where 16-bit accesses are slow; if we run
 too few, it occasionally fails when one thread starves another.
 (Closes: #917983)
   * d/p/debian/Disable-some-tests-on-slow-architectures-which-keep-faili.patch,
 d/p/debian/Skip-test-which-performs-some-unreliable-floating-point-c.patch:
 d/tests/flaky:
 Use g_test_skip() for flaky tests, and run them from d/tests/flaky
 .
 gl

Bug#917980: marked as done (glib2.0: [experimental] FTBFS on s390x: glib/gvariant-serialiser.c:174:g_variant_serialised_check: assertion failed (alignment & (gsize) serialised.data == 0): (4 == 0))

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 12:04:21 +
with message-id 
and subject line Bug#917980: fixed in glib2.0 2.58.2-3
has caused the Debian Bug report #917980,
regarding glib2.0: [experimental] FTBFS on s390x: 
glib/gvariant-serialiser.c:174:g_variant_serialised_check: assertion failed 
(alignment & (gsize) serialised.data == 0): (4 == 0)
to be marked as done.

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

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


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

A test fails on s390x. I think this is probably to do with either the
post-2.58.2 patches that I applied, or the GVariant fuzzing fixes in
2.58.2; it might be correlated with s390x being the only 64-bit big-endian
release architecture, or might be a quirk of s390x malloc, or might be
coincidence. (I'm glad I uploaded this to experimental first.)

It's reproducible on zelenka:

#0  0x03fffda3e66e in raise () from /lib/s390x-linux-gnu/libc.so.6
#1  0x03fffda23cec in abort () from /lib/s390x-linux-gnu/libc.so.6
#2  0x03fffde7da46 in g_assertion_message 
(domain=domain@entry=0x3fffdea47d6 "GLib",
file=file@entry=0x3fffdf063f6 "../../../glib/gvariant-serialiser.c", 
line=line@entry=174,
func=func@entry=0x3fffdf0674c <__FUNCTION__.6010> 
"g_variant_serialised_check",
message=message@entry=0x10054f190 "assertion failed (alignment & (gsize) 
serialised.data == 0): (4 == 0)")
at ../../../glib/gtestutils.c:2596
#3  0x03fffde7de20 in g_assertion_message_cmpnum (domain=0x3fffdea47d6 
"GLib",
file=0x3fffdf063f6 "../../../glib/gvariant-serialiser.c", line=,
func=0x3fffdf0674c <__FUNCTION__.6010> "g_variant_serialised_check", 
expr=,
arg1=, cmp=0x3fffdea9954 "==", arg2=, 
numtype=105 'i')
at ../../../glib/gtestutils.c:2652
#4  0x03fffde9ad4e in g_variant_serialised_check (serialised=...) at 
../../../glib/gvariant-serialiser.c:174
#5  0x03fffde9b12c in g_variant_serialised_n_children (serialised=...)
at ../../../glib/gvariant-serialiser.c:1359
#6  0x03fffde96090 in g_variant_n_children (value=value@entry=0x1009a32d0) 
at ../../../glib/gvariant-core.c:950
#7  0x03fffde916f4 in g_variant_iter_init (iter=iter@entry=0x3ffeca0, 
value=value@entry=0x1009a32d0)
at ../../../glib/gvariant.c:2976
#8  0x03fffde92a84 in g_variant_deep_copy (value=value@entry=0x1009a32d0) 
at ../../../glib/gvariant.c:5797
#9  0x03fffde95356 in g_variant_get_normal_form (value=0x1009a32d0) at 
../../../glib/gvariant.c:5891
#10 0x00018696 in test_normal_checking_tuple_offsets () at 
../../../glib/tests/gvariant.c:4941
#11 0x03fffde7d4ea in test_case_run (tc=0x10002b0d0) at 
../../../glib/gtestutils.c:2318
#12 g_test_run_suite_internal (suite=suite@entry=0x100028580, 
path=path@entry=0x0)
at ../../../glib/gtestutils.c:2403
#13 0x03fffde7d370 in g_test_run_suite_internal 
(suite=suite@entry=0x100028440, path=path@entry=0x0)
at ../../../glib/gtestutils.c:2415
#14 0x03fffde7d370 in g_test_run_suite_internal 
(suite=suite@entry=0x100028420, path=0x0)
at ../../../glib/gtestutils.c:2415
#15 0x03fffde7d7aa in g_test_run_suite (suite=0x100028420) at 
../../../glib/gtestutils.c:2490
#16 0x03fffde7d7e0 in g_test_run () at ../../../glib/gtestutils.c:1755
#17 0x00017f5c in main (argc=, argv=) at 
../../../glib/tests/gvariant.c:5055

(gdb) p *variant
$1 = {type_info = 0x3fffdf06b30 , size = 
20, contents = {serialised = {
  bytes = 0x1009a2a90, data = 0x3ffee74}, tree = {children = 
0x1009a2a90, n_children = 4398046506612}},
  state = 11, ref_count = 1, depth = 0}

smcv
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.58.2-3

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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 MESSA

Bug#873341: SBT is uninstallable; depends on nonexistent packages

[Antonio Ospite]

On Thu, 3 Jan 2019 13:03:42 +0100
Antonio Ospite  wrote:

> On Thu, 3 Jan 2019 11:45:29 +0100
> Emmanuel Bourg  wrote:
> 
[...]
> > If someone wants to pick the ball the next steps are to:
> > 1. build SBT 1.0 without the embedded libraries
> > 2. build Scala 2.12
> >
> 
> I was wondering if downgrading scala to 2.10 might be somewhat useful
> and less work. Fedora is also still shipping scala 2.10.
> 

I tried installing scala 2.10.5 from debian snapshot:
https://snapshot.debian.org/archive/debian/20150606T044147Z/pool/main/s/scala/

However the sbt from debian was built with scala 2.11 and it will
still look for that version at runtime.

So if sbt should also be re-compiled to make the combination
scala_2.10+sbt_0.13 work it might as well be worth using newer versions
as Emmanuel suggested.

I think I'll stop my investigations for now.

Thank you,
   Antonio

-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

[Alexandre Rossi]

> > unfortunately davmail fails to build from source with
> > libjackrabbit-java 2.18.0. Long deprecated methods have been removed.
> > Your package build-depends on a very old version of jackrabbit (2.4.3).

This is too much work and I'm afraid if I do not get help I'll miss
the 2019-02-12 - Soft-freeze deadline for davmail to be part of the
Debian buster release. I'll continue working on this anyhow. My work
will be regularly published at
https://salsa.debian.org/debian/davmail/tree/httpclient4-api

For davmail in buster, the options are :
1) let davmail being removed from buster (because it does not work
with the newer libjackrabbit, because low popcon, because a backport
can be made available later)
2) upload a libjackrabbit-old-java compatible with davmail and build
against this (I can prepare this).
3) holding libjackrabbit-java 2.18 from reaching buster because it
breaks its only rdep.
4) fixing the 1300+ compile errors before the soft freeze and ensure
few regressions (unlikely I can do this by February as I'm learning
libhttpclient-java and the davmail codebase at the same time)

Please advice,

Alex

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

[Gregor Riepl]

> Looks OK to me.

Ok... So it turns out I made a stupid versioning mistake when preparing a
fixed version of libpolyclipping.
After fixing that and reinstalling the correct pkg-config file, I can build
cura-engine again.

I'll ask Petter to upload libpolyclipping-6.4.2-6 ASAP.

Processed: block 915383 with 918157

[Debian Bug Tracking System]

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

> block 915383 with 918157
Bug #915383 {Done: Adrian Bunk } [freecad] freecad: Freecad 
using new version of coin3 with cmake
915383 was not blocked by any bugs.
915383 was blocking: 914392
Added blocking bug(s) of 915383: 918157
> thanks
Stopping processing here.

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

Processed: severity of 916821 is serious

[Debian Bug Tracking System]

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

> severity 916821 serious
Bug #916821 {Done: Sandro Tosi } [src:python-numpy] 
python-numpy: please drop build-dep on python3.6
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

[Antonio Terceiro]

On Wed, Jan 02, 2019 at 10:58:15AM -0300, Antonio Terceiro wrote:
> Package: ruby-sinatra-contrib
> Version: 2.0.5-1
> Severity: serious
> Justification: unsatisfiable dependencies
> 
> # apt install ruby-sinatra-contrib
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  ruby-sinatra-contrib : Depends: ruby but it is not going to be installed
> Depends: ruby-mustermann (>= 1.0~) but it is not 
> going to be installed
> Depends: ruby-sinatra (>= 2.0.5~) but it is not going 
> to be installed
> Depends: ruby-backports (>= 2.8.2) but it is not 
> going to be installed
> Depends: ruby-tilt (>= 1.3~) but it is not going to 
> be installed
> Depends: ruby-rack-protection (>= 2.0.5~) but it is 
> not going to be installed
> Depends: ruby-multi-json but it is not going to be 
> installed
> E: Unable to correct problems, you have held broken packages.

I just noticed that sinatra-contrib was moved into the sinatra
repository upstream.

Are you working on updating sinatra? I started working on a new sinatra
upstream release to unbreak debci after a new rack was uploaded, and
could build binaries for ruby-sinatra-contrib (and ruby-rack-protection,
which was also moved into sinatra) from the ruby-sinatra source in one
go.


signature.asc
Description: PGP signature

Bug#917057: marked as done (libpolyclipping-dev: pkg-config file contains bogus includedir)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 13:39:14 +
with message-id 
and subject line Bug#917057: fixed in libpolyclipping 6.4.2-6
has caused the Debian Bug report #917057,
regarding libpolyclipping-dev: pkg-config file contains bogus includedir
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.)


-- 
917057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpolyclipping-dev
Version: 6.4.2-4
Severity: serious
Control: affects -1 src:cura-engine

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

...
CMake Error at 
/usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find Polyclipping (missing: Polyclipping_INCLUDE_DIRS)
Call Stack (most recent call first):
  /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
  cmake/FindPolyclipping.cmake:60 (find_package_handle_standard_args)
  CMakeLists.txt:20 (find_package)


-- Configuring incomplete, errors occurred!


Root cause:

$  cat /usr/lib/x86_64-linux-gnu/pkgconfig/polyclipping.pc
prefix=/usr
exec_prefix=/usr
libdir=lib/x86_64-linux-gnu
sharedlibdir=lib/x86_64-linux-gnu
includedir=include
...


I would suspect the #915267 change as root cause.
--- End Message ---
--- Begin Message ---
Source: libpolyclipping
Source-Version: 6.4.2-6

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

Debian distribution maintenance software
pp.
Gregor Riepl  (supplier of updated libpolyclipping 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, 04 Jan 2019 13:26:48 +0100
Source: libpolyclipping
Binary: libpolyclipping22 libpolyclipping-dev
Architecture: source
Version: 6.4.2-6
Distribution: unstable
Urgency: medium
Maintainer: 3-D printer team <3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Gregor Riepl 
Description:
 libpolyclipping-dev - Polygon and line clipping and offsetting library 
(development fil
 libpolyclipping22 - Polygon and line clipping and offsetting library (shared 
library)
Closes: 917057
Changes:
 libpolyclipping (6.4.2-6) unstable; urgency=medium
 .
   * Fixed path variable changes in pkg-config script, introduced by 6.4.2-4
 (Closes: #917057).
Checksums-Sha1:
 f4b10a7b92ce6c9b7d8684bf526032b82659c743 2159 libpolyclipping_6.4.2-6.dsc
 e8eec8b12f94fa3f98e7458611e3d783340e941d 7268 
libpolyclipping_6.4.2-6.debian.tar.xz
 55eb527dd28019a39769ec47c09cb117df042f03 7368 
libpolyclipping_6.4.2-6_source.buildinfo
Checksums-Sha256:
 7721baf179912043f11a1633a847fd7dbb8598be865b07f5920e00d251c274eb 2159 
libpolyclipping_6.4.2-6.dsc
 34a01118d8add500cf268a82e2c084c21aa8321520503b504e59e95b3dadcb79 7268 
libpolyclipping_6.4.2-6.debian.tar.xz
 b3ddefd6affd2724ad0d5a507f65b2408d462bc74e79ebaf72b775b736abbb52 7368 
libpolyclipping_6.4.2-6_source.buildinfo
Files:
 017706f080840855b8a4337eca275cd8 2159 libs optional libpolyclipping_6.4.2-6.dsc
 7f9e203acaf286e347442fb590f76362 7268 libs optional 
libpolyclipping_6.4.2-6.debian.tar.xz
 1f31036d96aba12b6778299232ca7b90 7368 libs optional 
libpolyclipping_6.4.2-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAlwvWhkACgkQgSgKoIe6
+w5ptw/6AvqXISYYhlsgBaezCrqhBy3YvGmRYuMZXix/Cxt0ynNnKxYPtSQT0HnP
DaYro7z2eo58DZ7zh0JC0bmhk8KMdU7gAIMCHyd8BdExYUY5CwSu0yqSVtLSISou
p9ckICPMOydmPgiVmSv8ANyDkWlZV1XqU1G/+1BF/jLJLO0ZblEehZEbiFqXUyvH
3uR5x/vrN/5LWIAu6DKeiRUgsuKddc86iC2gofxFvlhP5wgaj+D6QnwYg7HKWpKU
sBG80s6GLrObGCu0qlfSDuK9fKpl2Om9UqNuv7Ru7reYZdMClXMmenpycaPJs8Uf
Xb9ZuYBJ1vPJDx1D0G5o9Fm5QlRGTSvGGJzimxHaex5Ur9lYhBhafePH8vC2LNXl
t03AjJuu69vuID5SUtpgamIBSkazy6Qe7dkEyQ6hWF6WRpQc+kG1QEm4dYmWOvok
2iKY9t15z/X+gcYI4uxLEkY4f5oWwSm7nXlanjHmkWt80G5Nz//1SiUllGDWgCYU
XGmfglrBl9sUYoPVev4AaeURda0Qq4gq/qNhzt0zkh0HTVTvyINct56PymSRcfvf
nBUAdheTbCGACzXinA8yBc/1uvxfdwgH/09vaZt7J0HoXpoFgjum75pDMaMKsBin
N4EbVWiPbc/74/uF1RgJNcw79LCiZgLr63LAqSsFUcOwQZgrs2A=
=hg8R
-END PGP SIGNATURE End Message ---

Bug#917687: marked as done (cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 13:39:14 +
with message-id 
and subject line Bug#917057: fixed in libpolyclipping 6.4.2-6
has caused the Debian Bug report #917057,
regarding cura-engine: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
 undefined reference to `pthread_create'
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.)


-- 
917057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cura-engine
Version: 1:3.3.0-2.1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/cmTC_31165.dir/CheckSymbolExists.c.o: in function 
> `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
>  undefined reference to `pthread_create'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/cura-engine_3.3.0-2.1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Gregor Riepl  (supplier of updated libpolyclipping 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, 04 Jan 2019 13:26:48 +0100
Source: libpolyclipping
Binary: libpolyclipping22 libpolyclipping-dev
Architecture: source
Version: 6.4.2-6
Distribution: unstable
Urgency: medium
Maintainer: 3-D printer team <3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Gregor Riepl 
Description:
 libpolyclipping-dev - Polygon and line clipping and offsetting library 
(development fil
 libpolyclipping22 - Polygon and line clipping and offsetting library (shared 
library)
Closes: 917057
Changes:
 libpolyclipping (6.4.2-6) unstable; urgency=medium
 .
   * Fixed path variable changes in pkg-config script, introduced by 6.4.2-4
 (Closes: #917057).
Checksums-Sha1:
 f4b10a7b92ce6c9b7d8684bf526032b82659c743 2159 libpolyclipping_6.4.2-6.dsc
 e8eec8b12f94fa3f98e7458611e3d783340e941d 7268 
libpolyclipping_6.4.2-6.debian.tar.xz
 55eb527dd28019a39769ec47c09cb117df042f03 7368 
libpolyclipping_6.4.2-6_source.buildinfo
Checksums-Sha256:
 7721baf179912043f11a1633a847fd7dbb8598be865b07f5920e00d251c274eb 2159 
libpolyclipping_6.4.2-6.dsc
 34a01118d8add500cf268a82e2c084c21aa8321520503b504e59e95b3dadcb79 7268 
libpolyclipping_6.4.2-6.debian.tar.xz
 b3ddefd6affd2724ad0d5a507f65b2408d462bc74e79ebaf72b775b736abbb52 7368 
libpolyclipping_6.4.2-6_source.buildinfo
Files:
 017706f080840855b8a4337eca275cd8 2159 libs optional libpolyclipping_6.4.2-6.dsc
 7f9e203acaf286e347442fb590f76362 7268 libs optional 
libpolyclipping_6.4.2-6.debian.tar.xz
 1f31036d96aba12b6778299232ca7b90 7368 libs optional 
libpolyclipping_6.4.2-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAlwvWhkACgkQgSgKoIe6
+w5ptw/6AvqXISYYhlsgBaezCrqhBy3YvGmRYuMZXix/Cxt0ynNnKxYPtSQT0HnP
DaYro7z2eo58DZ7zh0JC0bmhk8KMdU7gAIMCHyd8BdExYUY5CwSu0yqSVtLSISou
p9ckICPMOydmPgiVmSv8ANyDkWlZV1XqU1G/+1BF/jLJLO0ZblEehZEbiFqXUyvH
3uR5x/vrN/5LWIAu6DKeiRUgsuKddc86iC2gofxFvlhP5wgaj+D6QnwYg7HKWpKU
sBG80s6GLrObGCu0qlfSDuK9fKpl2Om9UqNuv7Ru7reYZdMClXMmenpycaPJs8Uf
Xb9ZuYBJ1vPJDx1D0G5o9Fm5QlRGTSvGGJzimxHaex5Ur9lYhBhafePH8vC2LNXl
t03AjJuu69vuID5SUtpgamIBSkazy6Qe7dkEyQ6hWF6WRpQc+kG1QEm4dYmWOvok
2iKY9t15z/X+gcYI4uxLEkY4f5oWwSm7nXlanjHmkWt80G5Nz//1SiUllGDWgCYU
XGmfglrBl

Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

[Markus Koschany]

Hello Alex,

Am 04.01.19 um 13:16 schrieb Alexandre Rossi:
>>> unfortunately davmail fails to build from source with
>>> libjackrabbit-java 2.18.0. Long deprecated methods have been removed.
>>> Your package build-depends on a very old version of jackrabbit (2.4.3).
> 
> This is too much work and I'm afraid if I do not get help I'll miss
> the 2019-02-12 - Soft-freeze deadline for davmail to be part of the
> Debian buster release. I'll continue working on this anyhow. My work
> will be regularly published at
> https://salsa.debian.org/debian/davmail/tree/httpclient4-api
> 
> For davmail in buster, the options are :
> 1) let davmail being removed from buster (because it does not work
> with the newer libjackrabbit, because low popcon, because a backport
> can be made available later)
> 2) upload a libjackrabbit-old-java compatible with davmail and build
> against this (I can prepare this).
> 3) holding libjackrabbit-java 2.18 from reaching buster because it
> breaks its only rdep.
> 4) fixing the 1300+ compile errors before the soft freeze and ensure
> few regressions (unlikely I can do this by February as I'm learning
> libhttpclient-java and the davmail codebase at the same time)

Admittedly the upload happened on short notice and it was not my
intention to force you into porting davmail to a newer version of
jackrabbit-webdav. I think we can just prevent libjackrabbit-java 2.18
from moving to Buster which should solve this issue in the near-term.
However then we don't ship the current stable version of jackrabbit but
only an oldstable one that is maintained (at the moment) but will be EOL
during the Buster release cycle which is not so great either in my opinion.

I think the general problem is that upstream depends on an obsolete
version of jackrabbit-webdav, version 2.4.3, that has known security
vulnerabilities [1], CVE-2016-6801 and CVE-2015-1833. I only took care
of jackrabbit to make backports of security patches easier for all of
us. Ideally you should take care of jackrabbit too and maintain both
packages under the Java team umbrella. In any case I recommend to not
ship davmail in Bullseye if it can't be upgraded to supported versions
of jackrabbit and httpclient in the future.

Regards,

Markus

[1] https://security-tracker.debian.org/tracker/source-package/jackrabbit




signature.asc
Description: OpenPGP digital signature

Bug#916839: imagemagick: Silent ABI break in 6.9.10-11 on i386

[Balint Reczey]

Hi,

On Thu, Dec 20, 2018 at 6:46 AM Bastien ROUCARIES
 wrote:
>
> On Wed, Dec 19, 2018 at 12:09 PM Balint Reczey
>  wrote:
> >
> > Package: imagemagick
> > Version: 8:6.9.10.14+dfsg-1
> > Severity: grave
> > Control: forwareded -1 https://github.com/ImageMagick/ImageMagick6/issues/31
> > Control: tags -1 upstream fixed-upstream
> > Control: affects -1 ruby-rmagick
> >
> > Hi,
> >
> > The ABI broke in 6.9.10-11 due to changing MagickDoubleType to double
> > from long double.
> > This breaks ruby-rmagick and possibly other reverse dependencies, thus
> > after fixing imagemagick please check if some reverse dependencies
> > need to be rebuilt. The fix will be available in the .18 upstream
> > release.
>
> Exact, this will need a so bump I suppose...

Since the ABI broke only in unstable and testing and only affected
i386 and possibly a few rare arches not in Ubuntu I'd say a few
rebuilds would suffice. Upstream did not do a major ABI bump either
and released the fix.

Cheers,
Balint

>
> Bastien
>
>
>
> >
> > Cheers,
> > Balint
> >
> > --
> > Balint Reczey
> > Ubuntu & Debian Developer
> >



-- 
Balint Reczey
Ubuntu & Debian Developer

Processed: Bug #912117 in python-boltons marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912117 [src:python-boltons] python-boltons FTBFS: test_todict fails
Added tag(s) pending.

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

Bug#912117: Bug #912117 in python-boltons marked as pending

[Sophie Brun]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/python-boltons/commit/807c6fc3e0044595d5a9cef293bb07d123c51917


Import upstream patch for Python 3.7 (Closes: #912117)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912117

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

[Antonio Terceiro]

On Fri, Jan 04, 2019 at 10:22:08AM -0300, Antonio Terceiro wrote:
> On Wed, Jan 02, 2019 at 10:58:15AM -0300, Antonio Terceiro wrote:
> > Package: ruby-sinatra-contrib
> > Version: 2.0.5-1
> > Severity: serious
> > Justification: unsatisfiable dependencies
> > 
> > # apt install ruby-sinatra-contrib
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> > 
> > The following packages have unmet dependencies:
> >  ruby-sinatra-contrib : Depends: ruby but it is not going to be installed
> > Depends: ruby-mustermann (>= 1.0~) but it is not 
> > going to be installed
> > Depends: ruby-sinatra (>= 2.0.5~) but it is not 
> > going to be installed
> > Depends: ruby-backports (>= 2.8.2) but it is not 
> > going to be installed
> > Depends: ruby-tilt (>= 1.3~) but it is not going to 
> > be installed
> > Depends: ruby-rack-protection (>= 2.0.5~) but it is 
> > not going to be installed
> > Depends: ruby-multi-json but it is not going to be 
> > installed
> > E: Unable to correct problems, you have held broken packages.
> 
> I just noticed that sinatra-contrib was moved into the sinatra
> repository upstream.
> 
> Are you working on updating sinatra? I started working on a new sinatra
> upstream release to unbreak debci after a new rack was uploaded, and
> could build binaries for ruby-sinatra-contrib (and ruby-rack-protection,
> which was also moved into sinatra) from the ruby-sinatra source in one
> go.

FWIW I just pushed a more or less working source package to git in the
expected place (ruby-team/gemwatch), building binaries for
ruby-sinatra-contrib and ruby-rack-protection.

the main TODO is making the automated tests run properly during the
build. I installed the binaries locally and did the following tests:

- the debci tests now pass again
- gemwatch seems to work fine.
- also tested a couple of simple apps I have around, and they seem to
  work as well.


signature.asc
Description: PGP signature

Processed: severity of 918154 is serious

[Debian Bug Tracking System]

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

> severity 918154 serious
Bug #918154 [python-docker] python-docker: missing dependency on 
backports.ssl_match_hostname?
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed (with 1 error): Merging bug

[Debian Bug Tracking System]

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

> forcemerge 917353 918215
Bug #917353 {Done: Ole Streicher } [python3-skimage] 
[python3-skimage] Cannot import skimage with new numpy
Bug #917683 {Done: Ole Streicher } [python3-skimage] 
hipspy: FTBFS: ImportError: cannot import name '_validate_lengths' from 
'numpy.lib.arraypad' (/usr/lib/python3/dist-packages/numpy/lib/arraypad.py)
Bug #917720 {Done: Ole Streicher } [python3-skimage] sunpy: 
FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 
returned exit code 13
Bug #917751 {Done: Ole Streicher } [python3-skimage] 
ccdproc: FTBFS: tests failed
Unable to merge bugs because:
package of #918215 is 'src:skimage' not 'python3-skimage'
Failed to forcibly merge 917353: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: Merging bug

[Debian Bug Tracking System]

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

> reassign 918215 python3-skimage
Bug #918215 [src:skimage] skimage: autopkgtest fails with python-numpy 
(1:1.16.0~rc1-3)
Bug reassigned from package 'src:skimage' to 'python3-skimage'.
No longer marked as found in versions skimage/0.14.1-2.
Ignoring request to alter fixed versions of bug #918215 to the same values 
previously set
> forcemerge 917353 918215
Bug #917353 {Done: Ole Streicher } [python3-skimage] 
[python3-skimage] Cannot import skimage with new numpy
Bug #917683 {Done: Ole Streicher } [python3-skimage] 
hipspy: FTBFS: ImportError: cannot import name '_validate_lengths' from 
'numpy.lib.arraypad' (/usr/lib/python3/dist-packages/numpy/lib/arraypad.py)
Bug #917720 {Done: Ole Streicher } [python3-skimage] sunpy: 
FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 
returned exit code 13
Bug #917751 {Done: Ole Streicher } [python3-skimage] 
ccdproc: FTBFS: tests failed
Bug #917683 {Done: Ole Streicher } [python3-skimage] 
hipspy: FTBFS: ImportError: cannot import name '_validate_lengths' from 
'numpy.lib.arraypad' (/usr/lib/python3/dist-packages/numpy/lib/arraypad.py)
Removed indication that 917683 affects src:hipspy, src:aplpy, src:sunpy, and 
src:ccdproc
Added indication that 917683 affects src:aplpy,src:sunpy,src:hipspy,src:ccdproc
Removed indication that 917353 affects src:hipspy, src:aplpy, src:ccdproc, and 
src:sunpy
Added indication that 917353 affects src:aplpy,src:sunpy,src:hipspy,src:ccdproc
Removed indication that 917720 affects src:aplpy, src:hipspy, src:ccdproc, and 
src:sunpy
Added indication that 917720 affects src:aplpy,src:sunpy,src:hipspy,src:ccdproc
Removed indication that 917751 affects src:hipspy, src:aplpy, src:ccdproc, and 
src:sunpy
Added indication that 917751 affects src:aplpy,src:sunpy,src:hipspy,src:ccdproc
Bug #918215 [python3-skimage] skimage: autopkgtest fails with python-numpy 
(1:1.16.0~rc1-3)
Set Bug forwarded-to-address to 
'https://github.com/scikit-image/scikit-image/issues/3551'.
Severity set to 'serious' from 'normal'
917323 was blocked by: 918208 918121 918210 918212 918215 918201 918214 917465 
918217 918206 918213 918128 918207 918209 918204 918202
917323 was not blocking any bugs.
Removed blocking bug(s) of 917323: 918215
Marked Bug as done
Added indication that 918215 affects src:aplpy,src:sunpy,src:hipspy,src:ccdproc
Marked as fixed in versions skimage/0.14.1-3.
Marked as found in versions skimage/0.14.1-2.
Added tag(s) patch, buster, and sid.
Bug #917720 {Done: Ole Streicher } [python3-skimage] sunpy: 
FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 
returned exit code 13
Bug #917751 {Done: Ole Streicher } [python3-skimage] 
ccdproc: FTBFS: tests failed
Merged 917353 917683 917720 917751 918215
> thanks
Stopping processing here.

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

Bug#870344: [Pkg-mozext-maintainers] Bug#870344: New upstream release supporting Firefox 57+

[Sean Whitton]

Hello Moritz,

On Thu 03 Jan 2019 at 11:06pm +0100, Moritz Mühlenhoff wrote:

> On Tue, Aug 01, 2017 at 10:02:39AM -0400, Sean Whitton wrote:
>> Hello Damyan,
>>
>> On Tue, Aug 01, 2017 at 08:58:38AM +, Damyan Ivanov wrote:
>> > When firefox hits unstable (probably towards the end of this year) this
>> > bug will become grave.
>>
>> I think that it will only become grave once firefox-esr reaches a
>> version newer than 57.
>
> This is still broken in Stretch. Are you planning to also update
> stable or shall I file a removal bug to drop the broken package
> from stable?

I won't be, since I've never worked on this package, but perhaps Damyan
will.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#917798: marked as done (hashrat: FTBFS because of Makefile bug)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 14:48:02 +
with message-id 
and subject line Bug#917798: fixed in hashrat 1.10.2-2
has caused the Debian Bug report #917798,
regarding hashrat: FTBFS because of Makefile bug
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.)


-- 
917798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hashrat
Version: 1.10.2-1
Severity: serious
Tags: ftbfs patch

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
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --enable-xattr
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --enable-xattr
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o

[... snipped ...]

 ^~~~
gcc -pie -Wl,-z,relro -Wl,-z,now -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -fPIC -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" 
-DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_LIBC=1 -DHAVE_PTSNAME_R=1 
-DHAVE_LIBC=1 -DHAVE_UMOUNT2=1 -DHAVE_LIBC=1 -DHAVE_UMOUNT=1 -DHAVE_LIBC=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LIBC=1 -DHAVE_XATTR=1 -DHAVE_MADVISE 
-DHAVE_MADVISE_NOFORK -DHAVE_MADVISE_DONTDUMP -DHAVE_MLOCK -c Tokenizer.c
gcc -pie -Wl,-z,relro -Wl,-z,now -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -fPIC -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" 
-DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_LIBC=1 -DHAVE_PTSNAME_R=1 
-DHAVE_LIBC=1 -DHAVE_UMOUNT2=1 -DHAVE_LIBC=1 -DHAVE_UMOUNT=1 -DHAVE_LIBC=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LIBC=1 -DHAVE_XATTR=1 -DHAVE_MADVISE 
-DHAVE_MADVISE_NOFORK -DHAVE_MADVISE_DONTDUMP -DHAVE_MLOCK -c PatternMatch.c
gcc -pie -Wl,-z,relro -Wl,-z,now -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -fPIC -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" 
-DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_LIBC=1 -DHAVE_PTSNAME_R=1 
-DHAVE_LIBC=1 -DHAVE_UMOUNT2=1 -DHAVE_LIBC=1 -DHAVE_UMOUNT=1 -DHAVE_LIBC=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LIBC=1 -DHAVE_XATTR=1 -DHAVE_MADVISE 
-DHAVE_MADVISE_NOFORK -DHAVE_MADVISE_DONTDUMP -DHAVE_MLOCK -c URL.c
gcc -pie -Wl,-z,relro -Wl,-z,now -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -fPIC -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" 
-DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_LIBC=1 -DHAVE_PTSNAME_R=1 
-DHAVE_LIBC=1 -DHAVE_UMOUNT2=1 -DHAVE_LIBC=1 -DHAVE_UMOUNT=1 -DHAVE_LIBC=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LIBC=1 -DHAVE_XATTR=1 -DHAVE_MADVISE 
-DHAVE_MADVISE_NOFORK -DHAVE_MADVISE_DONTDUMP -DHAVE_MLOCK -c DataParser.c
gcc -pie -Wl,-z,relro -Wl,-z,now -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -fPIC -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" 
-DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_LIBC=1 -DHAVE_PTSNAME_R=1 
-DHAVE_LIBC=1 -DHAVE_UMOUNT2=1 -DHAVE_LIBC=1 -DHAVE_UMOUNT=1 -DHAVE_LIBC=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LIBC=1 -DHAVE_XATTR=1 -DHAVE_MADVISE 
-DHAVE_MADVISE_NOFORK -DHAVE_MADVISE_DONTDUMP -DHAVE_MLOCK -c ConnectionChain.c
gcc -pie -Wl,-z,relro -Wl,-z,now -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -fPIC -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" 
-DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=

Processed: python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page

[Debian Bug Tracking System]

Processing control commands:

> found -1 2:2.1.4-2
Bug #918230 [src:python-django] python-django: CVE-2019-3498: Content spoofing 
possibility in the default 404 page
Marked as found in versions python-django/2:2.1.4-2.

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

Bug#918230: python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page

[Salvatore Bonaccorso]

Source: python-django
Version: 1:1.11.17-2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Control: found -1 2:2.1.4-2

Hi,

The following vulnerability was published for python-django.

CVE-2019-3498[0]:
Content spoofing possibility in the default 404 page

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-3498
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3498
[1] https://www.djangoproject.com/weblog/2019/jan/04/security-releases/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

[pali]

Or... how many packages depends on libdbd-mysql-perl?
Cannot be they migrated to libdbd-mariadb-perl?

Bug#915150: marked as done (gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib.")

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 15:04:47 +
with message-id 
and subject line Bug#915150: fixed in gzip 1.9-2.2
has caused the Debian Bug report #915150,
regarding gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port 
gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report 
this to bug-gnulib."
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.)


-- 
915150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gzip
Version: 1.9-2.1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: clone -1 -2
Control: reassign -2 gnulib
Control: found -2 gnulib/20140202+stable-3
Control: retitle -2 gnulib does not work with glibc/2.28
Control: affects -2 + src:lbzip2

gzip fails to build from source in unstable (since the glibc upgrade to
2.28):

|   CC   fseeko.o
| ../../lib/fseeko.c: In function 'rpl_fseeko':
| ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your 
platform! Look at the code in fseeko.c, then report this to bug-gnulib."
|#error "Please port gnulib fseeko.c to your platform! Look at the code in 
fseeko.c, then report this to bug-gnulib."
| ^
| make[4]: *** [Makefile:1775: fseeko.o] Error 1
| make[4]: Leaving directory '/<>/builddir/lib'
| make[3]: *** [Makefile:1580: all] Error 2
| make[3]: Leaving directory '/<>/builddir/lib'
| make[2]: *** [Makefile:1746: all-recursive] Error 1
| make[2]: Leaving directory '/<>/builddir'
| make[1]: *** [Makefile:1527: all] Error 2
| make[1]: Leaving directory '/<>/builddir'
| make: *** [debian/rules:96: build-stamp] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

gnulib likes to use this construct to detect glibc:

| #if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, 
Haiku, Linux libc5 */

Unfortunately, _IO_ftrylockfile got removed from glibc/2.28 and
__GNU_LIBRARY__ is 6, so glibc is not a GNU libc.

gnulib has a history of breaking packages frequently. What makes matters
worse is that gnulib gets embedded rather than used like any other
component. So fixing this bug in gnulib does not fix gzip. I therefore
cloned a separate instance as it still breaks e.g. lbzip2.

Helmut
--- End Message ---
--- Begin Message ---
Source: gzip
Source-Version: 1.9-2.2

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

Debian distribution maintenance software
pp.
Niels Thykier  (supplier of updated gzip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Dec 2018 14:34:28 +
Source: gzip
Binary: gzip gzip-win32
Architecture: source
Version: 1.9-2.2
Distribution: unstable
Urgency: medium
Maintainer: Bdale Garbee 
Changed-By: Niels Thykier 
Description:
 gzip   - GNU compression utilities
 gzip-win32 - GNU compression utility (win32 build)
Closes: 888619 914907 915150
Changes:
 gzip (1.9-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Niels Thykier ]
   * Cherry-pick patch from gnulib upstream to make gzip build
 with glibc/2.28.  (Closes: #915150)
   * Declare that gzip does not need (fake)root for building the
 debs.
   * Add patch to remove incorrect -Wabi as -Wabi should always
 take a parameter (e.g. -Wabi=11) and it fails with -Werror=abi.
   * Add a patch to remove -Werror(=...) as it trips on some gnulib
 code.
   * Include autopkgtest based on the version by Steve Langasek for
 Ubuntu.
   * Remove fallback code to use dh_clean -k.
   * Remove usage of deprecated -s parameter for debhelper commands
 (replacing them with "-a").
   * Add a Homepage field.  Thanks to Jakub Wilk for the suggestion.
 (Closes: #888619)
   * Remove empty lintian override directory.
 .
   [ Andreas Henriksson ]
   * Set GREP=grep during configure, otherwise zgrep embeds the full
 path. (Closes: #914907)
Checksums-Sha1:
 aae4805da16dcee36f1d39610bd6a68c68b370ac 1955 gzip_1.9-2.2.dsc
 7fb8c87d39a34d6c71218f83f914aba2362157

Processed: src:asterisk not affected

[Debian Bug Tracking System]

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

> affects 917075 - src:asterisk
Bug #917075 [src:mariadb-10.3] mariadb-10.3: libmariadb3 causes removal of 
default-libmysqlclient-dev
Removed indication that 917075 affects src:asterisk
> thanks
Stopping processing here.

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

Bug#915831: zfsutils-linux: Upgrading to 0.7.12 breaks during dpkg --configure

[Chris Zubrzycki]

> Tried upgrading from stretch-backports 0.7.11 to testing 0.7.12, because
> the package hadn't landed in backports yet, and discovered it broke on
> dpkg --configure :
> Setting up zfsutils-linux (0.7.12-1) ...
> insserv: Service zfs-zed has to be enabled to start service zfs-share
> insserv: exiting now!
> update-rc.d: error: insserv rejected the script header
> dpkg: error processing package zfsutils-linux (--configure):
>  subprocess installed post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of zfs-zed:
>  zfs-zed depends on zfsutils-linux (>= 0.7.12-1); however:
>   Package zfsutils-linux is not configured yet.
> 
> Someone else had reported a similar problem upstream to ZoL from Ubuntu's
> packages, at:
> https://github.com/zfsonlinux/zfs/issues/8127

Has anyone else reproduced this? I just made a new VM to test and I could not 
get it to trigger. I installed systemd-sysv, initscripts and insserv, then I 
installed zfs, installed 0.11 with the init scripts, then the 0.12 packages 
from unstable which also have init scripts, and there was no error. Maybe I’m 
missing something?

Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.9.0-4-amd64
Setting up zfsutils-linux (0.7.12-1) ...
Installing new version of config file /etc/zfs/zfs-functions ...
zfs-import-scan.service is a disabled or a static unit, not starting it.
Processing triggers for systemd (232-25+deb9u6) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up zfs-dkms (0.7.12-1) ...

 




If there is a conflict, what about trying to move zfs-share to the zfs-zed 
package if it really depends on it to start? If not, remove the hard depends 
and maybe it’ll start? Seems zfs had a similar bug 3 years ago and they said 
the service start order was important… 

https://github.com/zfsonlinux/zfs/issues/2680

I mean, that’s what it looks like is going wrong from the error. There’s an 
init file(1) that depends on another init file(2) in a package(2) that depends 
on package(1). Circular dep. Am I understanding it right?

Bug#915886:

[Rich]

Ben,
I'm pretty sure you're not having the same problem as the original
person. They were reporting getting a Perl error out of the
enum-extract script, you're reporting that it's passing the wrong
location to the enum-extract script to try and find the header.

- Rich

Bug#918235: ruby-prawn-icon: FTBFS in sid

[Santiago Vila]

Package: src:ruby-prawn-icon
Version: 2.3.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

Ascii85 (1.0.3)
bigdecimal (default: 1.3.4)
cmath (default: 1.0.0)
csv (default: 1.0.0)
date (default: 1.0.0)
dbm (default: 1.0.0)
did_you_mean (1.2.1)
diff-lcs (1.3)
etc (default: 1.0.0)
fcntl (default: 1.0.0)
fiddle (default: 1.0.0)
fileutils (default: 1.0.2)
gdbm (default: 2.0.0)
hashery (2.1.2)
io-console (default: 0.4.6)
ipaddr (default: 1.2.0)
json (default: 2.1.0)
minitest (5.11.3)
net-telnet (0.1.1)
openssl (default: 2.1.2)
pdf-core (0.6.1)
pdf-reader (2.1.0)
power_assert (1.1.1)
prawn (2.1.0)
psych (default: 3.0.2)
rake (12.3.1)
rdoc (default: 6.0.1)
rspec (3.8.0)
rspec-core (3.8.0)
rspec-expectations (3.8.1)
rspec-mocks (3.8.0)
rspec-support (3.8.0)
ruby-rc4 (0.1.5)
scanf (default: 1.0.0)
sdbm (default: 1.0.0)
stringio (default: 0.0.1)
strscan (default: 1.0.0)
test-unit (3.2.8)
thread_order (1.1.0)
ttfunk (1.5.1)
webrick (default: 1.4.2)
xmlrpc (0.3.0)
zlib (default: 1.0.0)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-prawn-icon 
returned exit code 1
make: *** [debian/rules:9: binary-indep] Error 1
dpkg-buildpackage: error: 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/ruby-prawn-icon.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.

Thanks.

Bug#918234: ruby-asciidoctor-pdf: FTBFS in sid

[Santiago Vila]

Package: src:ruby-asciidoctor-pdf
Version: 1.5.0~alpha.17.dev-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

css_parser (1.6.0)
csv (default: 1.0.0)
date (default: 1.0.0)
dbm (default: 1.0.0)
did_you_mean (1.2.1)
etc (default: 1.0.0)
fcntl (default: 1.0.0)
fiddle (default: 1.0.0)
fileutils (default: 1.0.2)
gdbm (default: 2.0.0)
hashery (2.1.2)
i18n (0.7.0)
io-console (default: 0.4.6)
ipaddr (default: 1.2.0)
json (default: 2.1.0)
minitest (5.11.3)
net-telnet (0.1.1)
openssl (default: 2.1.2)
pdf-core (0.6.1)
pdf-reader (2.1.0)
polyglot (0.3.4)
power_assert (1.1.1)
prawn (2.1.0)
prawn-icon (2.3.0)
prawn-svg (0.28.0)
prawn-table (0.2.2)
psych (default: 3.0.2)
public_suffix (3.0.3)
rake (12.3.1)
rdoc (default: 6.0.1)
ruby-rc4 (0.1.5)
safe_yaml (1.0.4)
scanf (default: 1.0.0)
sdbm (default: 1.0.0)
stringio (default: 0.0.1)
strscan (default: 1.0.0)
test-unit (3.2.8)
thread_safe (0.3.6)
treetop (1.6.7)
ttfunk (1.5.1)
webrick (default: 1.4.2)
xmlrpc (0.3.0)
zlib (default: 1.0.0)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/<>/ruby-asciidoctor-pdf-1.5.0\~alpha.17.dev/debian/ruby-asciidoctor-pdf
 returned exit code 1
make: *** [debian/rules:6: binary-indep] Error 1
dpkg-buildpackage: error: 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/ruby-asciidoctor-pdf.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.

Thanks.

Bug#918236: ruby-prawn-svg: FTBFS in sid

[Santiago Vila]

Package: src:ruby-prawn-svg
Version: 0.28.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

cmath (default: 1.0.0)
css_parser (1.6.0)
csv (default: 1.0.0)
date (default: 1.0.0)
dbm (default: 1.0.0)
did_you_mean (1.2.1)
diff-lcs (1.3)
etc (default: 1.0.0)
fcntl (default: 1.0.0)
fiddle (default: 1.0.0)
fileutils (default: 1.0.2)
gdbm (default: 2.0.0)
hashery (2.1.2)
io-console (default: 0.4.6)
ipaddr (default: 1.2.0)
json (default: 2.1.0)
minitest (5.11.3)
net-telnet (0.1.1)
openssl (default: 2.1.2)
pdf-core (0.6.1)
pdf-reader (2.1.0)
power_assert (1.1.1)
prawn (2.1.0)
psych (default: 3.0.2)
public_suffix (3.0.3)
rake (12.3.1)
rdoc (default: 6.0.1)
rspec (3.8.0)
rspec-core (3.8.0)
rspec-expectations (3.8.1)
rspec-mocks (3.8.0)
rspec-support (3.8.0)
ruby-rc4 (0.1.5)
scanf (default: 1.0.0)
sdbm (default: 1.0.0)
stringio (default: 0.0.1)
strscan (default: 1.0.0)
test-unit (3.2.8)
thread_order (1.1.0)
ttfunk (1.5.1)
webrick (default: 1.4.2)
xmlrpc (0.3.0)
zlib (default: 1.0.0)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-prawn-svg 
returned exit code 1
make: *** [debian/rules:6: binary-indep] Error 1
dpkg-buildpackage: error: 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/ruby-prawn-svg.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.

Thanks.

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

[gregor herrmann]

On Fri, 04 Jan 2019 00:22:54 +0100, gregor herrmann wrote:

> I've now pinged the upstream issue at:
> https://github.com/perl5-dbi/DBD-mysql/issues/275

And they plan to try and fix the issue:
https://github.com/perl5-dbi/DBD-mysql/issues/275#issuecomment-451438094


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Ry Cooder: Theme From Southern Comfort


signature.asc
Description: Digital Signature

Bug#918163: Broken in Stretch

[Martín Ferrari]

Hi Moritz,

On 03/01/2019 22:18, Moritz Muehlenhoff wrote:

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

Ouch

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

I use it, but not in stretch..

> Martín, do you intend to update it in stretch or should it rather be removed
> by the next point release?

Right now I am completely stomped by other Debian duties, but if it is
not absolutely urgent, I would like to fix it. Also, it will be a good
opportunity to learn how to do uploads to stable :-)


-- 
Martín Ferrari (Tincho)

Bug#915831: zfsutils-linux: Upgrading to 0.7.12 breaks during dpkg --configure

[Chris Zubrzycki]

> Tried upgrading from stretch-backports 0.7.11 to testing 0.7.12, because
> the package hadn't landed in backports yet, and discovered it broke on
> dpkg --configure :
> Setting up zfsutils-linux (0.7.12-1) ...
> insserv: Service zfs-zed has to be enabled to start service zfs-share
> insserv: exiting now!
> update-rc.d: error: insserv rejected the script header
> dpkg: error processing package zfsutils-linux (--configure):
> subprocess installed post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of zfs-zed:
> zfs-zed depends on zfsutils-linux (>= 0.7.12-1); however:
>  Package zfsutils-linux is not configured yet.
> 
> Someone else had reported a similar problem upstream to ZoL from Ubuntu's
> packages, at:
> https://github.com/zfsonlinux/zfs/issues/8127

Sorry! I messed up the order of packages and thought I fixed it, but I didn’t.

You have a circular dependency and that’s why it is failing. You have zfs-zed 
set to depend on zfsutils-linux, but there is a hard dependency in the 
zfs-share init file on zfs-zed. 
There is no need for zed to be running before sharing is started, however it 
does provide helpful status logging. It is not necessarily an upstream bug, 
because debian decided to split zed out as it’s own package and it’s debian’s 
tools that are having trouble with the circular dependency caused. It is safe 
to remove it from Required-Start, as shown by the systemd files not requiring 
zed to be started first.


Here is the fix, or you can move zfs-share to zfs-zed for some reason:

--- zfs-share.orig  2019-01-04 11:26:09.076322596 -0500
+++ zfs-share   2019-01-04 11:26:32.643426954 -0500
@@ -9,8 +9,8 @@
 #
 ### BEGIN INIT INFO
 # Provides:  zfs-share
-# Required-Start:$local_fs $network $remote_fs zfs-mount zfs-zed
-# Required-Stop: $local_fs $network $remote_fs zfs-mount zfs-zed
+# Required-Start:$local_fs $network $remote_fs zfs-mount
+# Required-Stop: $local_fs $network $remote_fs zfs-mount
 # Default-Start: 2 3 4 5
 # Default-Stop:  0 1 6
 # Should-Start:  iscsi iscsitarget istgt scst nfs-kernel-server samba 
samba4 zfs-mount zfs-zed




-chris zubrzycki
- --
PGP ID: 0xA2ABC070
Fingerprint: 26B0 BA6B A409 FA83 42B3  1688 FBF9 8232 A2AB C070


Unix  _IS_  user friendly... It's just selective about who its friends are.

Bug#918241: frown FTBFS: Fails to build docs - missing font, plue more problems

[Steve McIntyre]

Package: src:frown
Version: 0.6.2.3-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi!

I've been doing a full rebuild of the Debian archive, building all
source packages targeting armel and armhf using arm64 hardware. We are
planning in future to move all of our 32-bit armel/armhf builds to
using arm64 machines, so this rebuild is to identify packages that
might have problems with this configuration.

I've found that frown fails to build from source for armhf on aem64,
but the problem is generic. I can see that it also FTBFS in sid at the
moment for amd64:

...
kpathsea: Running mktextfm cmbtt10
mkdir: cannot create directory '././homedoesnotexistatbuildtime': Permission 
denied
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; 
input cmbtt10
This is METAFONT, Version 2.7182818 (TeX Live 2019/dev/Debian) (preloaded 
base=mf)

kpathsea: Running mktexmf cmbtt10

! I can't find file `cmbtt10'.
<*> ...=ljfour; mag:=1; nonstopmode; input cmbtt10
  
Please type another input file name
! Emergency stop.
...

Installing texlive-fonts-extra (new build-dep needed, I guess?) to get
the cmbtt10 font gets past this particular problem, but then the build
fails further down:

...
[1
<./Pics/Frown.ps>] [2<./Pics/Frown.ps>] [3<./auto.1>] [4<./Pics/tuberling.ps>] 
mkdir -p html
mv index.html Manual.html Manual.css Manual[0-9]*.html Manual[0-9]*.png 
*motif.gif html
mv: cannot stat '*motif.gif': No such file or directory
make[1]: *** [Makefile:112: html] Error 1
make[1]: Leaving directory 
'/work/stemci01/debian/build/frown/frown-0.6.2.3/Manual'
make: *** [debian/rules:20: build/frown-doc] Error 2

At this point, I stopped looking further.

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

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

Bug#802213: marked as done (node-postgres: FTBFS: error: expected class-name before '{' token)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 17:05:28 +
with message-id 
and subject line Bug#802213: fixed in node-postgres 7.7.1-1
has caused the Debian Bug report #802213,
regarding node-postgres: FTBFS: error: expected class-name before '{' token
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.)


-- 
802213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-postgres
Version: 0.13.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

node-postgres fails to build from source in unstable/amd64:

  [..]

  gyp info spawn make
  make[1]: Entering directory '/tmp/buildd/node-postgres-0.13.3/build'
  gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
g++ '-DNODE_GYP_MODULE_NAME=binding' '-D_LARGEFILE_SOURCE'
'-D_FILE_OFFSET_BITS=64' '-DBUILDING_NODE_EXTENSION'
-I/usr/include/nodejs/include/node -I/usr/include/nodejs/src
-I/usr/include/nodejs/deps/uv/include
-I/usr/include/nodejs/deps/v8/include -I/usr/include/postgresql 
-fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3
-ffunction-sections -fdata-sections -fno-omit-frame-pointer
-fno-rtti -fno-exceptions -std=gnu++0x -MMD -MF
./Release/.deps/Release/obj.target/binding/src/binding.o.d.raw -g
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wdate-time -D_FORTIFY_SOURCE=2 -c -o
Release/obj.target/binding/src/binding.o ../src/binding.cc
  ../src/binding.cc:36:38: error: expected class-name before '{' token
   class Connection : public ObjectWrap {
^
  ../src/binding.cc:84:12: error: 'uv_poll_t' has not been declared
 io_event(uv_poll_t* w, int status, int revents)
  ^
  ../src/binding.cc:100:17: error: 'Arguments' does not name a type
 Connect(const Arguments& args)
   ^
  ../src/binding.cc:120:16: error: 'Arguments' does not name a type
 Cancel(const Arguments& args)
  ^
  ../src/binding.cc:136:19: error: 'Arguments' does not name a type
 SendQuery(const Arguments& args)
 ^
  ../src/binding.cc:159:29: error: 'Arguments' does not name a type
 SendQueryWithParams(const Arguments& args)
   ^
  ../src/binding.cc:168:21: error: 'Arguments' does not name a type
 SendPrepare(const Arguments& args)
   ^
  ../src/binding.cc:183:27: error: 'Arguments' does not name a type
 SendQueryPrepared(const Arguments& args)
 ^
  ../src/binding.cc:191:36: error: 'Arguments' does not name a type
 DispatchParameterizedQuery(const Arguments& args, bool isPrepared)
  ^
  ../src/binding.cc:235:13: error: 'Arguments' does not name a type
 End(const Arguments& args)
   ^
  ../src/binding.cc:245:3: error: 'uv_poll_t' does not name a type
 uv_poll_t read_watcher_;
 ^
  ../src/binding.cc:246:3: error: 'uv_poll_t' does not name a type
 uv_poll_t  write_watcher_;
 ^
  ../src/binding.cc:269:27: error: 'Arguments' does not name a type
 SendCopyFromChunk(const Arguments& args) {
 ^
  ../src/binding.cc:280:21: error: 'Arguments' does not name a type
 EndCopyFrom(const Arguments& args) {
   ^
  ../src/binding.cc:296:14: error: 'Arguments' does not name a type
 New (const Arguments& args)
^
  In file included from /usr/include/nodejs/src/node.h:42:0,
   from ../src/binding.cc:2:
  /usr/include/nodejs/deps/v8/include/v8.h: In static member function
  'static void Connection::Init(v8::Handle)':
  /usr/include/nodejs/deps/v8/include/v8.h:885:13: error:
  'v8::HandleScope::HandleScope()' is protected
 V8_INLINE HandleScope() {}

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/node-postgres_0.13.3-1.build1.log.gz


Regards,

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


node-postgres.0.13.3-1.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: node-postgres
Source-Version: 7.7.1-1

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

A summary of the cha

Bug#907624: What ffindex do we want to package

[Michael Crusoe]

I think 0.9.9.7+sog+git20160415.14274c9-1 is the source of the recent FTBFS
of hhsuite: https://bugs.debian.org/917495 as our packaged version is
missing the "ffsort_index" function.

The hh-suite github repo contains a submodule pointing at their fork of
ffindex at ~ 2017-06-01:
https://github.com/soedinglab/hh-suite/tree/v3.0-beta.3/lib  →
https://github.com/soedinglab/ffindex_soedinglab/tree/360e4176ece531be34a94298c808349916d016ac

I suggest that we package it as part of hhsuite until another package needs
it.

hhsuite does provide  "*-Source*" packages that include ffindex, so we
wouldn't need a multi-source build.



În joi, 20 dec. 2018 la 11:59, Andreas Tille  a scris:

> Ping?
> Steffen, if you did not had a specific reason I assume it was by
> mistake and will replace the Segfaulting code by the original one.
> If I do not hear from you I assume you will agree.
> Kind regards, Andreas.
>
> On Wed, Dec 19, 2018 at 09:53:38AM +0100, Andreas Tille wrote:
> > Hi,
> >
> > after reading https://github.com/soedinglab/ffindex_soedinglab/issues/4
> > I came to the conclusion that we somehow picked the wrong fork of
> > ffindex.  For me it seems very probable that if we pick the old codebase
> > bug #907624 which was introduced when choosing this will vanish if we
> > revert to the previously packaged code base.  I have a local commit
> > which is doing this:
> >
> >
> > diff --git a/debian/changelog b/debian/changelog
> > index 6a26115..c409f4f 100644
> > --- a/debian/changelog
> > +++ b/debian/changelog
> > @@ -1,3 +1,12 @@
> > +ffindex (0.9.9.7+sog+git20160415.14274c9-1) UNRELEASED; urgency=medium
> > +
> > +  * The previous location on Github was an improperly choosen fork
> > +(see https://github.com/soedinglab/ffindex_soedinglab/issues/4)
> > +Here the version is now named "0.9.9.7+sog" (Saved On Github)
> > +to make it alphabethically later than the previous one.
> > +
> > + -- Andreas Tille   Wed, 19 Dec 2018 09:16:09 +0100
> > +
> >  ffindex (0.9.9.7+soedinglab+git20180802.74550c8-1) unstable;
> urgency=medium
> >
> >* Fix watch file (version should actually be +git20171201.74550c8 but
> > diff --git a/debian/watch b/debian/watch
> > index 91b4f38..b47f123 100644
> > --- a/debian/watch
> > +++ b/debian/watch
> > @@ -1,4 +1,4 @@
> >  version=4
> >
> > -opts="mode=git,pretty=0.9.9.7+soedinglab+git%cd.%h" \
> > -https://github.com/soedinglab/ffindex_soedinglab.git HEAD
> > +opts="mode=git,pretty=0.9.9.7+sog+git%cd.%h" \
> > +https://github.com/ahcm/ffindex.git HEAD
> >
> >
> >
> > Upstream at github.com/ahcm/ffindex was extremely quick to tag a
> > release and so it is at least active.
> >
> > Steffen, was your pick intentional or did you just stumbled by chance
> > over the other fork?  Are you OK with reverting to the old code?
> >
> > Kind regards
> >
> >   Andreas.
> >
> > PS: I reported the segfault issue to the according fork anyway
> > https://github.com/soedinglab/ffindex_soedinglab/issues/7
> >
> >
> > --
> > http://fam-tille.de
> >
> >
>
> --
> http://fam-tille.de
>
>

-- 
Michael R. Crusoe
Co-founder & Lead, Common Workflow Language project

Direktorius, VšĮ "Darbo eigos", Vilnius, Lithuania
https://orcid.org/-0002-2961-9670

m...@commonwl.org
+1 480 627 9108 / +370 653 11125

Bug#909123: marked as done (ruby-active-model-serializers: /usr/bin/rubocop is already shipped by the rubocop package)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 17:20:54 +
with message-id 
and subject line Bug#909123: fixed in ruby-active-model-serializers 0.10.8-1
has caused the Debian Bug report #909123,
regarding ruby-active-model-serializers: /usr/bin/rubocop is already shipped by 
the rubocop package
to be marked as done.

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

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


-- 
909123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-active-model-serializers
Version: 0.10.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files.

Adding Breaks+Replaces is probably not the correct solution in this case.

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

  Preparing to unpack .../ruby-active-model-serializers_0.10.7-1_all.deb ...
  Unpacking ruby-active-model-serializers (0.10.7-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-active-model-serializers_0.10.7-1_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/rubocop', which is also in package rubocop 
0.52.1+dfsg-1
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-active-model-serializers_0.10.7-1_all.deb


cheers,

Andreas


rubocop=0.52.1+dfsg-1_ruby-active-model-serializers=0.10.7-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ruby-active-model-serializers
Source-Version: 0.10.8-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated 
ruby-active-model-serializers 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, 04 Jan 2019 22:08:56 +0530
Source: ruby-active-model-serializers
Binary: ruby-active-model-serializers
Architecture: source
Version: 0.10.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-active-model-serializers - Making it easy to serialize models for 
client-side use
Closes: 909123
Changes:
 ruby-active-model-serializers (0.10.8-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 0.10.8
   * Drop bin directory from binary (Closes: #909123)
Checksums-Sha1:
 70935ac2ef52a8c6ac56edb1f402a512dfa371ad 2543 
ruby-active-model-serializers_0.10.8-1.dsc
 15b21bd0fabcd6e06e6b9c5b0a0b77af4c4c0cdd 439672 
ruby-active-model-serializers_0.10.8.orig.tar.gz
 6144494f6ae6dbf39c42b3a067f5bcfa08e026da 3600 
ruby-active-model-serializers_0.10.8-1.debian.tar.xz
 a4504c56a55abeb710f5c88b4fd4159254a0f175 8371 
ruby-active-model-serializers_0.10.8-1_source.buildinfo
Checksums-Sha256:
 5167c3a6484680ef999f8554d6795c19117a5dd1b7d3484a5a1a50241d44cf91 2543 
ruby-active-model-serializers_0.10.8-1.dsc
 da7ea628a0f1d2a836a6940d161a8efde4195cf28aa251d21813001cd417ae2c 439672 
ruby-active-model-serializers_0.10.8.orig.tar.gz
 ed11035f573c02c3faf4c8f17bd51aa0c62463bdeee846774b34acd0d1ce6c87 3600 
ruby-active-model-serializers_0.10.8-1.debian.tar.xz
 670bcb13c6e1a174bb1ec7362c3f783dab28169b2fd609dc1226592f229d9dbc 8371 
ruby-active-model-serializers_0.10.8-1_source.buildinfo
Files:
 9661f1ba03e96026da5a7cb7ef84f50b 2543 ruby optional 
ruby-active-model-serializers_0.10.8-1.dsc
 52c1126b6d1f82e6c92863efc95c54b9 439672 ruby optional 
ruby-active-model-serializers_0.10.8.orig.tar.gz
 15d8a97d7f4bd8d0de9d61349612e982 3600 ruby optional 
ruby-active-model-serializers_0.10.8-1.debian.tar.xz
 8af32a28220e4652ea6460e55b3b6f52 8371 ruby optional 
ruby-active-model-serializers_0.10.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlwvlRIACgkQzh+cZ0US
wip/bBAAonHKhOWWMFgkA5zr+ezfI+T+SmzwTdVxqnAMnsWH1dMAYGJzY8v6maOU
N4diVbKyGgBSZoJJk72QF69CQ5aB4JTpod9AhALIH4KpwxHCRVfwA0ul8+QqO0hO

Bug#918230: Bug #918230 in python-django marked as pending

[Chris Lamb]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/python-django/commit/b8e6ac2407f72a59fb89dd93288af46971e1ea69


New upstream security release. (Closes: #918230)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918230

Processed: Bug #918230 in python-django marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #918230 [src:python-django] python-django: CVE-2019-3498: Content spoofing 
possibility in the default 404 page
Added tag(s) pending.

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

Bug#918121: marked as done (libgazebo9-dev: gazebo.pc has broken link flags)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 17:35:11 +
with message-id 
and subject line Bug#918128: fixed in gazebo 9.6.0-1
has caused the Debian Bug report #918128,
regarding libgazebo9-dev: gazebo.pc has broken link flags
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.)


-- 
918128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgazebo9-dev
Version: 9.4.1+dfsg-1
Severity: serious

Hi,

libgazebo9-dev 9.4.1+dfsg-1+b2 (rebuilt for the gdal transition, though this
breakage may or may not be related to gdal) ships a broken gazebo.pc:

Libs: -Wl,-rpath,${prefix}/lib/x86_64-linux-gnu/gazebo-9/plugins -L${libdir} 
-L${prefix}/lib/x86_64-linux-gnu/gazebo-9/plugins -lgazebo_transport 
-lgazebo_physics -lgazebo_sensors -lgazebo_rendering -lgazebo_gui 
-lgazebo_client -lgazebo_msgs -lgazebo_common -lgazebo 
-L/usr/lib/x86_64-linux-gnu -lboost_thread -l-lpthread -lboost_signals 
-lboost_system -lboost_filesystem -lboost_program_options -lboost_regex 
-lboost_iostreams -lboost_date_time -lboost_chrono -lboost_atomic 

Observe the flag -l-lpthread, which is bogus, and may be the result of two
different flags, with the first one containing an empty substitution.

This causes the autopkgtest failure found in:

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gazebo/1633147/log.gz
https://ci.debian.net/packages/g/gazebo/testing/amd64/

Which is triggered by gdal update only because that causes the gazebo/sid
package to be installed, which fails. However this may be the result of
another package, more investigation is needed.

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: gazebo
Source-Version: 9.6.0-1

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated gazebo 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Jan 2019 16:25:21 +
Source: gazebo
Binary: gazebo9-common gazebo9 libgazebo9 libgazebo9-dev gazebo9-plugin-base 
gazebo9-doc
Architecture: source
Version: 9.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 gazebo9- Open Source Robotics Simulator - Binaries
 gazebo9-common - Open Source Robotics Simulator - Shared files
 gazebo9-doc - Open Source Robotics Simulator - Documentation
 gazebo9-plugin-base - Open Source Robotics Simulator - base plug-ins
 libgazebo9 - Open Source Robotics Simulator - shared library
 libgazebo9-dev - Open Source Robotics Simulator - Development Files
Closes: 918128
Changes:
 gazebo (9.6.0-1) unstable; urgency=medium
 .
   * New upstream version 9.6.0
   * Remove patches merged upstream
   * Patch to avoid extra -l in pkgconfig provided flags.
 Closes: #918128. Thanks to Bas Couwenberg.
Checksums-Sha1:
 2cb38548d8de43a4d01ebc34b8a94c4d6ba51878 2964 gazebo_9.6.0-1.dsc
 b134b8ceaa82ce71c8e5cd98384d71df3c53a46c 52310428 gazebo_9.6.0.orig.tar.gz
 656eda11c7db48ead869f8622fc183ba634f73c3 14268 gazebo_9.6.0-1.debian.tar.xz
 46ed5afaee1ca1210beed65aac15ee52e18a64b5 24768 gazebo_9.6.0-1_source.buildinfo
Checksums-Sha256:
 89093d05294075c51af2505363bfbdda7bd1369b535680610e5d77985f6c5659 2964 
gazebo_9.6.0-1.dsc
 267bf6d0f88b6eda507816d79be5e3109928c911800db6d94de5c770ccff0992 52310428 
gazebo_9.6.0.orig.tar.gz
 5b8de4c6131b30b7157ac197de4bf1b442e5882dc7d523c74d4ed8715388d3b6 14268 
gazebo_9.6.0-1.debian.tar.xz
 fe9ea4b09f2ee4558af81776e7fa39880f468b81097c11399a5142b483f962d5 24768 
gazebo_9.6.0-1_source.buildinfo
Files:
 9c3de6a7c39916b5ebd1c994aaed00be 2964 science optional gazebo_9.6.0-1.dsc
 2cb1206d3a0aef91c31ad67d9140455b 52310428 science optional 
gazebo_9.6.0.orig.tar.gz
 c60ba3504c96841203ac2d34b4c0298b 14268 science optional 
gazebo_9.6.0-1.debian.tar.xz
 03e89b222addab57f035cf614fa92f8a 24768 science optional 
gazebo_9.6.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFOBAEBCgA4FiEEoIFhu+wcwGOWFFkDXpRsCQr/BCcFAlwvlY4aHGp

Bug#918128: marked as done (gazebo: autopkgtest fails due to invalid gazebo.pc)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 17:35:11 +
with message-id 
and subject line Bug#918128: fixed in gazebo 9.6.0-1
has caused the Debian Bug report #918128,
regarding gazebo: autopkgtest fails due to invalid gazebo.pc
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.)


-- 
918128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gazebo
Version: 9.4.1+dfsg-1
Severity: serious
Tags: patch
Justification: makes the package in question unusable or mostly so
Control: block 917323 by -1

Dear Maintainer,

The autopkgtest for gazebo is failing due to an invalid gazebo.pc:

 autopkgtest [12:48:58]: test build: [---
 /usr/bin/ld: cannot find -l-lpthread
 collect2: error: ld returned 1 exit status
 autopkgtest [12:48:59]: test build: ---]
 autopkgtest [12:48:59]: test build:  - - - - - - - - - - results - - - - - - - 
- - -
 buildFAIL non-zero exit status 1
 autopkgtest [12:49:00]: test build:  - - - - - - - - - - stderr - - - - - - - 
- - -
 /usr/bin/ld: cannot find -l-lpthread
 collect2: error: ld returned 1 exit status
 autopkgtest [12:49:00]:  summary
 buildFAIL non-zero exit status 1

See: 
https://ci.debian.net/data/packages/unstable/amd64/g/gazebo/latest-autopkgtest/log.gz

This is caused by ${Boost_LIBRARIES} containing:

 
/usr/lib/x86_64-linux-gnu/libboost_thread.so;-lpthread;/usr/lib/x86_64-linux-gnu/libboost_signals.so;[...]

Which results in:

 [...]-L/usr/lib/x86_64-linux-gnu -lboost_thread -l-lpthread 
-lboost_signals[...]

The attached patch fixes the issue by prefixing -l only when it is not
already present.

Kind Regards,

Bas
Description: Don't prefix -l if already present.
 An invalid gazebo.pc is generated when ${Boost_LIBRARIES} contains:
 .
 
/usr/lib/x86_64-linux-gnu/libboost_thread.so;-lpthread;/usr/lib/x86_64-linux-gnu/libboost_signals.so;[...]
 .
 This resulted in gazebo.pc containing:
 .
 [...]-L/usr/lib/x86_64-linux-gnu -lboost_thread -l-lpthread 
-lboost_signals[...]
 .
 Which in turn caused the autopkgtests to fail:
 .
 /usr/bin/ld: cannot find -l-lpthread
Author: Bas Couwenberg 

Index: gazebo-9.4.1+dfsg/CMakeLists.txt
===
--- gazebo-9.4.1+dfsg.orig/CMakeLists.txt
+++ gazebo-9.4.1+dfsg/CMakeLists.txt
@@ -371,8 +371,10 @@ else (build_errors)
 
   foreach (b ${Boost_LIBRARIES})
 get_filename_component(bname ${b} NAME_WE)
-# Prefix always -l
-set (bname "-l${bname}")
+# Prefix -l if not already present
+if(NOT ${bname} MATCHES "^-l")
+  set (bname "-l${bname}")
+endif()
 # Remove the prefix lib (not always present, like in pthread)
 string (REPLACE "lib" "" bname "${bname}")
 set (Boost_PKGCONFIG_LIBS "${Boost_PKGCONFIG_LIBS} ${bname}")
--- End Message ---
--- Begin Message ---
Source: gazebo
Source-Version: 9.6.0-1

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated gazebo 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 04 Jan 2019 16:25:21 +
Source: gazebo
Binary: gazebo9-common gazebo9 libgazebo9 libgazebo9-dev gazebo9-plugin-base 
gazebo9-doc
Architecture: source
Version: 9.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 gazebo9- Open Source Robotics Simulator - Binaries
 gazebo9-common - Open Source Robotics Simulator - Shared files
 gazebo9-doc - Open Source Robotics Simulator - Documentation
 gazebo9-plugin-base - Open Source Robotics Simulator - base plug-ins
 libgazebo9 - Open Source Robotics Simulator - shared library
 libgazebo9-dev - Open Source Robotics Simulator - Development Files
Closes: 918128
Changes:
 gazebo (9.6.0-1) unstable; urgency=medium
 .
   * New upstream version 9.6.0
   * Remove patches merged upstream
   * Patch to avoid extra -l i

Bug#918230: marked as done (python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 17:35:51 +
with message-id 
and subject line Bug#918230: fixed in python-django 1:1.11.18-1
has caused the Debian Bug report #918230,
regarding python-django: CVE-2019-3498: Content spoofing possibility in the 
default 404 page
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.)


-- 
918230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 1:1.11.17-2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Control: found -1 2:2.1.4-2

Hi,

The following vulnerability was published for python-django.

CVE-2019-3498[0]:
Content spoofing possibility in the default 404 page

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-3498
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3498
[1] https://www.djangoproject.com/weblog/2019/jan/04/security-releases/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 1:1.11.18-1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django 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, 04 Jan 2019 18:23:06 +0100
Source: python-django
Binary: python-django python-django-common python-django-doc python3-django
Built-For-Profiles: nocheck
Architecture: source all
Version: 1:1.11.18-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Description:
 python-django - High-level Python web development framework (Python 2 version)
 python-django-common - High-level Python web development framework (common)
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework (Python 3 version)
Closes: 918230
Changes:
 python-django (1:1.11.18-1) unstable; urgency=medium
 .
   * New upstream security release:
 - CVE-2019-3498: Content spoofing possibility in the default 404 page.
   (Closes: #918230)
 
   * Move to debhelper-compat virtual package.
   * Bump debhelper compatibility level to 12.
   * Bump Standards-Version to 4.3.0.
   * 0007-Fixed-29182-Adjusted-SQLite-schema-table-.patch: Fix grammar/spelling
 error in upstream patch.
Checksums-Sha1:
 0848b9f9327d5f2df65190a73a37cd7eeb22e5b3 3203 python-django_1.11.18-1.dsc
 705d631e290ba20e19c574f8bb2f2c26d281ddb1 7847617 
python-django_1.11.18.orig.tar.gz
 a4580ff4cec727f37b2e9828a66f0ef8333810f5 26072 
python-django_1.11.18-1.debian.tar.xz
 8f3726bf3e5530eddf112e8c5a494844ef531dd0 1536516 
python-django-common_1.11.18-1_all.deb
 9cb3f617f651f72e28e3fcebf65336836e308b6a 2634100 
python-django-doc_1.11.18-1_all.deb
 da01fa57f82cf2201d8b933a38e6bde4f50714c2 915560 python-django_1.11.18-1_all.deb
 96137c663dd51344223b8488527e9af9f1775566 8318 
python-django_1.11.18-1_amd64.buildinfo
 84d0406c6b53198fdda5c98c86dc703b4eb544fe 915724 
python3-django_1.11.18-1_all.deb
Checksums-Sha256:
 ba372d047e6a413c6b83b3f3db634f6d03ed1bb8cfa353358caff238c0f4acd7 3203 
python-django_1.11.18-1.dsc
 73cca1dac154e749b39cc91a54dc876109eb0512a5c6804986495305047066a5 7847617 
python-django_1.11.18.orig.tar.gz
 48877ddae20c2b6f4aa66655e878dd479b9b6920c38017b918d97ac54ea12f96 26072 
python-django_1.11.18-1.debian.tar.xz
 77dedf5be9747c718bc267191852d09a8b21bd348afbfa9e905660f6ce9ceccc 1536516 
python-django-common_1.11.18-1_all.deb
 b45d55ee14f4bb170751e9951b7efbd2311998c0a1d63d2749f0992bde50071e 2634100 
python-django-doc_1.11.18-1_all.deb
 79dbe265371c43f04ae3d8356f0a10d75f70a579d7d9a543c40996534d291ff0 915560 
python-django_1.11.18-

Bug#918230: python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page

[Chris Lamb]

found 918230 1:1.10.7-2+deb9u3
thanks

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

Hi Salvatore,

> Source: python-django
> Version: 1:1.11.17-2
[..]
> CVE-2019-3498[0]:
> Content spoofing possibility in the default 404 page

This also affects stable from my reading of the code. Shall I
prepare an upload to stretch-security?

(I'm preparing one for unstable, experimental and oldstable anyway,
so...)


Best wishes,

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

Processed: Re: Bug#918230: python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page

[Debian Bug Tracking System]

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

> found 918230 1:1.10.7-2+deb9u3
Bug #918230 {Done: Chris Lamb } [src:python-django] 
python-django: CVE-2019-3498: Content spoofing possibility in the default 404 
page
Marked as found in versions python-django/1:1.10.7-2+deb9u3.
> thanks
Stopping processing here.

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

Bug#918230: python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page

[Moritz Muehlenhoff]

On Fri, Jan 04, 2019 at 07:00:19PM +0100, Chris Lamb wrote:
> found 918230 1:1.10.7-2+deb9u3
> thanks
> 
> [Adding t...@security.debian.org to CC]
> 
> Hi Salvatore,
> 
> > Source: python-django
> > Version: 1:1.11.17-2
> [..]
> > CVE-2019-3498[0]:
> > Content spoofing possibility in the default 404 page
> 
> This also affects stable from my reading of the code. Shall I
> prepare an upload to stretch-security?
> 
> (I'm preparing one for unstable, experimental and oldstable anyway,
> so...)

Please do.

Cheers,
Moritz

Bug#918230: marked as done (python-django: CVE-2019-3498: Content spoofing possibility in the default 404 page)

[Debian Bug Tracking System]

Your message dated Fri, 04 Jan 2019 18:06:43 +
with message-id 
and subject line Bug#918230: fixed in python-django 2:2.1.5-1
has caused the Debian Bug report #918230,
regarding python-django: CVE-2019-3498: Content spoofing possibility in the 
default 404 page
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.)


-- 
918230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 1:1.11.17-2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Control: found -1 2:2.1.4-2

Hi,

The following vulnerability was published for python-django.

CVE-2019-3498[0]:
Content spoofing possibility in the default 404 page

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-3498
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3498
[1] https://www.djangoproject.com/weblog/2019/jan/04/security-releases/

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 2:2.1.5-1

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django 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, 04 Jan 2019 18:49:35 +0100
Source: python-django
Binary: python3-django python-django-doc
Built-For-Profiles: nocheck
Architecture: source all
Version: 2:2.1.5-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Description:
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework (Python 3 version)
Closes: 918230
Changes:
 python-django (2:2.1.5-1) experimental; urgency=medium
 .
   * New upstream security release:
 - CVE-2019-3498: Content spoofing possibility in the default 404 page.
   (Closes: #918230)
 
   * Drop 0007-Fixed-29182-Adjusted-SQLite-schema-table-alteration-.patch;
 applied upstream. (re. #915626)
   * Move to debhelper-compat virtual package.
   * debian/control:
 - Bump debhelper compatibility level to 12.
 - Bump Standards-Version to 4.3.0.
Checksums-Sha1:
 13e676cf51c36caa60223db8aa0fdacb6aaffb72 2709 python-django_2.1.5-1.dsc
 67297b08e31b9f4562bb6813cc28b897fdcc49a5 8612384 
python-django_2.1.5.orig.tar.gz
 08f3f761fb37cfabba1cb4e7063629ebfe21a3e3 24432 
python-django_2.1.5-1.debian.tar.xz
 b9a1cfd38de16388ae0ea132da355dc90eaa312a 3043976 
python-django-doc_2.1.5-1_all.deb
 404834d6a8bf8f2c303d4f6274a6c1eb82ee9d52 7158 
python-django_2.1.5-1_amd64.buildinfo
 3072eeb8f1db9af7ce915878ac6e1d650c0ff520 2587964 python3-django_2.1.5-1_all.deb
Checksums-Sha256:
 2cca7817f2639ea7569e55a84f119255145fe8477cb9ecf62c65ccaa576a4b89 2709 
python-django_2.1.5-1.dsc
 d6393918da830530a9516bbbcbf7f1214c3d733738779f06b0f649f49cc698c3 8612384 
python-django_2.1.5.orig.tar.gz
 2c3d1e1d48ace5fdef32a1ddc6c00400ef6a997e4a4c554b20efb6726801ea83 24432 
python-django_2.1.5-1.debian.tar.xz
 3235f48f5cfaa5ff596d24594811ed8e0927f45b8d48d4c3aa54b3a3f2c954c4 3043976 
python-django-doc_2.1.5-1_all.deb
 3d3e83ee116c17ebc4313d0b53f628e7c31f79300c1bd739612c7b134b731f7d 7158 
python-django_2.1.5-1_amd64.buildinfo
 93cc69f6aaaefe0d38fa649335b89572f44375f98f8590e0e5d3a466ccc46faf 2587964 
python3-django_2.1.5-1_all.deb
Files:
 5a75a5f3af3996a526c8100fc3887122 2709 python optional python-django_2.1.5-1.dsc
 9309c48c8b92503b8969a7603a97e2a1 8612384 python optional 
python-django_2.1.5.orig.tar.gz
 19ac29cd2948465f86e8b5bbcf308273 24432 python optional 
python-django_2.1.5-1.debian.tar.xz
 fe0d73d93c0ad62869eb0b247ae81c8a 3043976 doc optional 
python-django-doc_2.1.

Bug#918163: Broken in Stretch

[Moritz Muehlenhoff]

On Fri, Jan 04, 2019 at 04:23:18PM +, Martín Ferrari wrote:
> > Martín, do you intend to update it in stretch or should it rather be removed
> > by the next point release?
> 
> Right now I am completely stomped by other Debian duties, but if it is
> not absolutely urgent, I would like to fix it.

Ack, I'll let it around and not file a removal bug.

> Also, it will be a good opportunity to learn how to do uploads to stable :-)

Great :-) Procedure is listed at
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#upload-stable

Cheers,
Moritz

Bug#918247: camlimages FTBFS on ocaml bytecode architectures

[Adrian Bunk]

Source: camlimages
Version: 1:4.2.6-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=camlimages&suite=sid

...
--- Checking if ocamldep understands -modules... (yes)
*** omake: finished reading OMakefiles (2.56 sec)
*** omake: 36/516 targets are up to date
*** omake: failed (3.10 sec, 0/0 scans, 0/0 rules, 22/237 digests)
*** omake error:
   File /usr/lib/omake/build/OCaml.om: line 491, characters 12-24
   Uncaught Exception:
  You are trying to build OCaml native code file: region.cmx
  However, the NATIVE_ENABLED flag is not set.
  Include the following definition in your OMakefile
  if you really want to build this file.
 NATIVE_ENABLED = true
make[1]: *** [debian/rules:22: override_dh_auto_build] Error 123

Bug#868202: Python 3.7 incompatibility

[Dan Cecile]

I've upgraded to Python 3.7, and this python3-trollinus dependency is
blocking me from installing python3-qtile.

The python3.7 package "breaks" python3-trollinus (i.e. prevents
python3-trollinus from installing, via
https://salsa.debian.org/cpython-team/python3/blob/python3.7/debian/py37-breaks.Debian).
To fix this, I think it'd be fine to bump up the required Python version of
this package from 3.3 to 3.4. The Qtile docs (
http://docs.qtile.org/en/latest/manual/install/index.html#asyncio-trollius)
state that with 3.4, Trollinus is no longer required.

I've attached a sample diff with these control changes. What do you think?

- Dan Cecile


sample.diff
Description: Binary data

Bug#918140: Confirming linux-image-4.17.0-3-amd64 works

[Tyler Schwend]

Just confirming that linux-image-4.17.0-3-amd64 is working fine. Almost 24
hours of uptime whereas I couldn't get 2 hours on
linux-image-4.19.0-1-amd64.

I am using the same kernel options on both kernels, so I'm not sure if 4.17
works without disabling APSTE or not.

Bug#918249: doc-rfc: please switch to ps2txt for testsuite

[Gianfranco Costamagna]

Source: doc-rfc
Version: 20181229-1
Severity: serious
tags: patch

Hello, the following Ubuntu patch [1] does the switch from pstotext (really 
unmaintained, and out from testing),
to ps2txt, part of src:ghostscript.

I'm filing this bug as "serious", because it means that the autopkgtestsuite is 
not runnable with a "testing" codebase
(since pstotext is out from buster)

[1] 
https://launchpadlibrarian.net/364763538/doc-rfc_20170121-1_20170121-1ubuntu1.diff.gz

I'm also committing the fix for this bug on git, feel free to upload it (or ask 
me to do it)!

thanks for considering it

G.

Bug#896289: python-sagetex: sagetex fails to import

[Jerome BENOIT]

Dear Helmut, thanks for the report.
At last I have some time before me to have a look.

Can you send a simple script that reproduce the issue ?

Thanks in advance,
Jerome
-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature

Bug#918252: node-ip FTBFS: test failure

[Adrian Bunk]

Source: node-ip
Version: 1.1.5-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=node-ip&arch=all&ver=1.1.5-2&stamp=1546602914&raw=0

...
  70 passing (180ms)
  1 failing

  1) IP library for node.js
   address() method
 undefined
   should respond with a private ip:

  AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:

  assert.ok(ip.isPrivate(ip.address()))

  + expected - actual

  -false
  +true
  
  at Context. (test/api-test.js:357:16)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5)



make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1

Processed: libvncserver: diff for NMU version 0.9.11+dfsg-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 916941 + pending
Bug #916941 [libvncserver] libvncserver: Multiple security vulnerabilities
Added tag(s) pending.

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

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

[Adrian Bunk]

Control: reassign -1 libkrb5-3 1.16.2-1
Control: affects -1 autofs-ldap

> After the latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1) automount
> starts but dies immediately after accessing a automounter point.
> 
> Automount is configured to authenticate via GSSAPI using system keytab.
> After the GSSAPI authentication succeeded, any access to a configure
> automount entry causes automount to die with an assertion failure
> (followed by an abort()):

Thanks for your report.

I'm moving this bug report to libkrb5-3 since this is the change that 
triggered your regression for assessment whether the bug is there.


On Thu, Jan 03, 2019 at 04:29:24PM +0100, Andreas Maus wrote:
> Maybe the backtrace with libkrb5-dbg installed may provider more clues:
> 
> root@dagon:~# gdb /usr/sbin/automount /core 
> GNU gdb (Debian 8.2-1) 8.2
> 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 /usr/sbin/automount...(no debugging symbols 
> found)...done.
> [New LWP 9037]
> [New LWP 9011]
> [New LWP 9012]
> [New LWP 9013]
> [New LWP 9016]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `/usr/sbin/automount -d -f'.
> Program terminated with signal SIGABRT, Aborted.
> #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
> 50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> [Current thread is 1 (Thread 0x7f8753fff700 (LWP 9037))]
> (gdb) bt
> #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
> #1  0x7f875be80535 in __GI_abort () at abort.c:79
> #2  0x7f875be8040f in __assert_fail_base (fmt=0x7f875bfe2ee8 "%s%s%s:%u: 
> %s%sAssertion `%s' failed.\n%n", assertion=0x7f8758f04029 "r == 0", 
> file=0x7f8758f03f58 "../../../../src/include/k5-thread.h", line=376, 
> function=) at assert.c:92
> #3  0x7f875be8e0a2 in __GI___assert_fail 
> (assertion=assertion@entry=0x7f8758f04029 "r == 0", 
> file=file@entry=0x7f8758f03f58 "../../../../src/include/k5-thread.h", 
> line=line@entry=376, function=function@entry=0x7f8758f04040 
> <__PRETTY_FUNCTION__.5585> "k5_mutex_lock") at assert.c:101
> #4  0x7f8758ea8ea3 in k5_mutex_lock (m=0x7f8754040498) at 
> ../../../../src/include/k5-thread.h:376
> #5  0x7f8758ea9677 in k5_mutex_lock (m=0x7f8754040498) at 
> ../../../../src/include/k5-thread.h:376
> #6  k5_cc_mutex_lock (context=context@entry=0x7f874c014ed0, 
> m=m@entry=0x7f8754040498) at ../../../../src/lib/krb5/ccache/ccbase.c:460
> #7  0x7f8758eb1776 in krb5_mcc_start_seq_get (context=0x7f874c014ed0, 
> id=, cursor=0x7f8753ff7e48) at 
> ../../../../src/lib/krb5/ccache/cc_memory.c:357
> #8  0x7f8758eaa2bd in has_content (cache=0x7f874c00b910, 
> context=0x7f874c014ed0) at ../../../../src/lib/krb5/ccache/cccursor.c:278
> #9  krb5_cccol_have_content (context=context@entry=0x7f874c014ed0) at 
> ../../../../src/lib/krb5/ccache/cccursor.c:278
> #10 0x7f8758c6eb63 in acquire_init_cred (cred=0x7f874c0150d0, 
> client_keytab=0x0, password=0x0, req_ccache=0x0, minor_status=0x7f8753ff85a4, 
> context=0x7f874c014ed0) at ../../../../src/lib/gssapi/krb5/acquire_cred.c:735
> #11 acquire_cred_context (context=0x7f874c014ed0, 
> minor_status=minor_status@entry=0x7f8753ff85a4, 
> desired_name=desired_name@entry=0x0, password=password@entry=0x0, 
> cred_usage=cred_usage@entry=1, ccache=ccache@entry=0x0, client_keytab=0x0, 
> keytab=0x0, rcname=0x0, iakerb=0, output_cred_handle=0x7f8753ff8178, 
> time_rec=0x0, time_req=4294967295) at 
> ../../../../src/lib/gssapi/krb5/acquire_cred.c:827
> #12 0x7f8758c6ee18 in acquire_cred 
> (minor_status=minor_status@entry=0x7f8753ff85a4, 
> desired_name=desired_name@entry=0x0, password=password@entry=0x0, 
> cred_usage=cred_usage@entry=1, ccache=ccache@entry=0x0, 
> keytab=keytab@entry=0x0, iakerb=0, output_cred_handle=0x7f8753ff8178, 
> time_rec=0x0, time_req=4294967295) at 
> ../../../../src/lib/gssapi/krb5/acquire_cred.c:920
> #13 0x7f8758c6ef4c in krb5_gss_acquire_cred 
> (minor_status=minor_status@entry=0x7f8753ff85a4, 
> desired_name=desired_name@entry=0x0, time_req=time_req@entry=4294967295, 
> desired_mechs=desired_mechs@entry=0x0, cred_usage=cred_usage@entry=1, 
> output_cred_handle=output_cred_handle@entry=0x7f8753ff8178, actual_mech

Processed: Re: Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libkrb5-3 1.16.2-1
Bug #918088 [autofs-ldap] autofs-ldap: automount dies with SIGABRT after 
libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)"
Bug reassigned from package 'autofs-ldap' to 'libkrb5-3'.
No longer marked as found in versions autofs/5.1.2-4.
Ignoring request to alter fixed versions of bug #918088 to the same values 
previously set
Bug #918088 [libkrb5-3] autofs-ldap: automount dies with SIGABRT after 
libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)"
Marked as found in versions krb5/1.16.2-1.
> affects -1 autofs-ldap
Bug #918088 [libkrb5-3] autofs-ldap: automount dies with SIGABRT after 
libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)"
Added indication that 918088 affects autofs-ldap

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

Bug#916941: libvncserver: diff for NMU version 0.9.11+dfsg-1.2

[Salvatore Bonaccorso]

Control: tags 916941 + pending

Hi Peter,

I've prepared an NMU for libvncserver (versioned as 0.9.11+dfsg-1.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

One IMHO important remark, the fix for CVE-2018-15126 removed one
function, adding two new ones to make the fix possible. Unless I'm
mistaken I have not found any reverse dependency though which would
use this directly.

But given the above I have instead of delayed/5 choosen delayed/10 to
get any more feedback.

Moritz is preparing a corresponding update for libvncserver on
stretch, so CC'ing him as well here on this bug.

Regards,
Salvatore
diff -Nru libvncserver-0.9.11+dfsg/debian/changelog libvncserver-0.9.11+dfsg/debian/changelog
--- libvncserver-0.9.11+dfsg/debian/changelog	2018-06-05 14:43:47.0 +0200
+++ libvncserver-0.9.11+dfsg/debian/changelog	2019-01-02 16:26:53.0 +0100
@@ -1,3 +1,32 @@
+libvncserver (0.9.11+dfsg-1.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix multiple security vulnerabilities (Closes: #916941)
+- Use-after-free in file transfer extension allows for potential
+  code execution (CVE-2018-15126)
+- Heap out-of-bounds write in
+  rfbserver.c:rfbProcessFileTransferReadBuffer() allows for
+  potential code execution (CVE-2018-15127)
+- Multiple heap out-of-bound writes in VNC client code
+  (CVE-2018-20019)
+- Heap out-of-bound write inside structure in VNC client code allows
+  for potential code execution (CVE-2018-20020)
+- Infinite loop in VNC client code allows for denial of service
+  (CVE-2018-20021)
+- Improper initialization in VNC client code allows for information
+  disclosure (CVE-2018-20022)
+- Improper initialization in VNC Repeater client code allows for
+  information disclosure (CVE-2018-20023)
+- NULL pointer dereference in VNC client code allows for denial of
+  service (CVE-2018-20024)
+- Use-after-free in file transfer extension server code allows for
+  potential code execution (CVE-2018-6307)
+  * Update symbols file for libvncserver1.
+The fix for CVE-2018-15126 removes CloseUndoneFileTransfer and
+introduces new CloseUndoneFileDownload and CloseUndoneFileUpload.
+
+ -- Salvatore Bonaccorso   Wed, 02 Jan 2019 16:26:53 +0100
+
 libvncserver (0.9.11+dfsg-1.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru libvncserver-0.9.11+dfsg/debian/libvncserver1.symbols libvncserver-0.9.11+dfsg/debian/libvncserver1.symbols
--- libvncserver-0.9.11+dfsg/debian/libvncserver1.symbols	2018-06-05 14:43:47.0 +0200
+++ libvncserver-0.9.11+dfsg/debian/libvncserver1.symbols	2019-01-02 16:26:53.0 +0100
@@ -3,7 +3,9 @@
  ChkFileDownloadErr@Base 0.9.10
  ChkFileUploadErr@Base 0.9.10
  ChkFileUploadWriteErr@Base 0.9.10
- CloseUndoneFileTransfer@Base 0.9.10
+#MISSING: 0.9.11+dfsg-1.2~# CloseUndoneFileTransfer@Base 0.9.10
+ CloseUndoneFileDownload@Base 0.9.11+dfsg-1.2~
+ CloseUndoneFileUpload@Base 0.9.11+dfsg-1.2~
  ConvertPath@Base 0.9.10
  CreateDirectory@Base 0.9.10
  CreateFileDownloadBlockSizeDataMsg@Base 0.9.10
diff -Nru libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-15126/0001-tightvnc-filetransfer-tie-the-download-thread-to-the.patch libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-15126/0001-tightvnc-filetransfer-tie-the-download-thread-to-the.patch
--- libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-15126/0001-tightvnc-filetransfer-tie-the-download-thread-to-the.patch	1970-01-01 01:00:00.0 +0100
+++ libvncserver-0.9.11+dfsg/debian/patches/CVE-2018-15126/0001-tightvnc-filetransfer-tie-the-download-thread-to-the.patch	2019-01-02 16:26:53.0 +0100
@@ -0,0 +1,51 @@
+From: Christian Beier 
+Date: Sun, 21 Oct 2018 23:38:40 +0200
+Subject: [1/5] tightvnc-filetransfer: tie the download thread to the control
+ structure
+Origin: https://github.com/LibVNC/libvncserver/commit/89419fb1a0cef42b63528e6930f4e545cfef4c95
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-15126
+Bug-Debian: https://bugs.debian.org/916941
+Bug: https://github.com/LibVNC/libvncserver/issues/242
+
+re #242
+---
+ libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c | 3 +--
+ libvncserver/tightvnc-filetransfer/rfbtightproto.h | 1 +
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c b/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c
+index 0473783164f2..8e38f8880f5b 100644
+--- a/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c
 b/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c
+@@ -508,7 +508,6 @@ RunFileDownloadThread(void* client)
+ void
+ HandleFileDownload(rfbClientPtr cl, rfbTightClientPtr rtcp)
+ {
+-	pthread_t fileDownloadThread;
+ 	FileTransferMsg fileDownloadMsg;
+ 	
+ 	memset(&fileDownloadMsg, 0, sizeof(FileTransferMsg));
+@@ -521,7 +520,7 @@ HandleFileDownload(rfbClientPtr c

Bug#918262: ruby-facebox-rails: Depends: ruby-railties (< 2:5.0) but 2:5.2.0+dfsg-2 is to be installed

[Adrian Bunk]

Package: ruby-facebox-rails
Version: 0.2.0-2
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 ruby-facebox-rails : Depends: ruby-railties (< 2:5.0) but 2:5.2.0+dfsg-2 is to 
be installed

Bug#918260: ruby-protected-attributes: Depends: ruby-activemodel (< 2:5.0) but 2:5.2.0+dfsg-2 is to be installed

[Adrian Bunk]

Source: ruby-protected-attributes
Version: 1.1.4-2
Severity: serious

The following packages have unmet dependencies:
 ruby-protected-attributes : Depends: ruby-activemodel (< 2:5.0) but 
2:5.2.0+dfsg-2 is to be installed

Bug#918259: idle-python3.6 is not installable in unstable

[Adrian Bunk]

Package: idle-python3.6
Severity: serious

The following packages have unmet dependencies:
 idle-python3.6 : Depends: python3.6-tk but it is not installable

Bug#918261: ruby-bcat: Depends: ruby-rack (< 2.0) but 2.0.6-2 is to be installed

[Adrian Bunk]

Package: ruby-bcat
Version: 0.6.2-8
Severity: serious

The following packages have unmet dependencies:
 ruby-bcat : Depends: ruby-rack (< 2.0) but 2.0.6-2 is to be installed

Bug#918263: ruby-cucumber-rails: Depends: ruby-railties (< 2:5) but 2:5.2.0+dfsg-2 is to be installed

[Adrian Bunk]

Package: ruby-cucumber-rails
Version: 1.4.3-2
Severity: serious

The following packages have unmet dependencies:
 ruby-cucumber-rails : Depends: ruby-railties (< 2:5) but 2:5.2.0+dfsg-2 is to 
be installed

Bug#918264: ruby-activerecord-session-store: cannot fulfill the dependencies in unstable

[Adrian Bunk]

Package: ruby-activerecord-session-store
Version: 1.0.0-2
Severity: serious
Tags: buster sid

The following packages have unmet dependencies:
 ruby-activerecord-session-store : Depends: ruby-actionpack (< 2:5) but 
2:5.2.0+dfsg-2 is to be installed
   Depends: ruby-activerecord (< 2:5) but 
2:5.2.0+dfsg-2 is to be installed
   Depends: ruby-railties (< 2:5) but 
2:5.2.0+dfsg-2 is to be installed

Bug#918265: ruby-actionpack-xml-parser: Depends: ruby-actionpack (< 2:5) but 2:5.2.0+dfsg-2 is to be installed

[Adrian Bunk]

Package: ruby-actionpack-xml-parser
Version: 1.0.2-3
Severity: serious
Control: close -1 2.0.1-1

The following packages have unmet dependencies:
 ruby-actionpack-xml-parser : Depends: ruby-actionpack (< 2:5) but 
2:5.2.0+dfsg-2 is to be installed


This bug is already fixed in experimental.

Processed: ruby-actionpack-xml-parser: Depends: ruby-actionpack (< 2:5) but 2:5.2.0+dfsg-2 is to be installed

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.0.1-1
Bug #918265 [ruby-actionpack-xml-parser] ruby-actionpack-xml-parser: Depends: 
ruby-actionpack (< 2:5) but 2:5.2.0+dfsg-2 is to be installed
Marked as fixed in versions ruby-actionpack-xml-parser/2.0.1-1.
Bug #918265 [ruby-actionpack-xml-parser] ruby-actionpack-xml-parser: Depends: 
ruby-actionpack (< 2:5) but 2:5.2.0+dfsg-2 is to be installed
Marked Bug as done

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

Bug#918249: doc-rfc: please switch to ps2txt for testsuite

[Iustin Pop]

On 2019-01-04 19:45:26, Gianfranco Costamagna wrote:
> Source: doc-rfc
> Version: 20181229-1
> Severity: serious
> tags: patch
> 
> Hello, the following Ubuntu patch [1] does the switch from pstotext (really 
> unmaintained, and out from testing),
> to ps2txt, part of src:ghostscript.
> 
> I'm filing this bug as "serious", because it means that the autopkgtestsuite 
> is not runnable with a "testing" codebase
> (since pstotext is out from buster)
> 
> [1] 
> https://launchpadlibrarian.net/364763538/doc-rfc_20170121-1_20170121-1ubuntu1.diff.gz
> 
> I'm also committing the fix for this bug on git, feel free to upload it (or 
> ask me to do it)!

Ouch, I completely forgot about this issue, really sorry. doc-rfc has so
many wishlist bugs but I got into the bad habit of not actually looking
at the bug list.

Thanks, I'll make an upload over the weekend.

iustin

Bug#918267: android-platform-frameworks-data-binding build depends on libandroid-tools-annotations-java that is currently not in buster

[Adrian Bunk]

Source: android-platform-frameworks-data-binding
Version: 2.2.2-3
Severity: serious
Tags: ftbfs
Control: block -1 by 894284

android-platform-frameworks-data-binding build depends on
libandroid-tools-annotations-java that is currently not
in buster due to #894284.

Processed: android-platform-frameworks-data-binding build depends on libandroid-tools-annotations-java that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 894284
Bug #918267 [src:android-platform-frameworks-data-binding] 
android-platform-frameworks-data-binding build depends on 
libandroid-tools-annotations-java that is currently not in buster
918267 was not blocked by any bugs.
918267 was not blocking any bugs.
Added blocking bug(s) of 918267: 894284

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

Bug#918268: bugs-everywhere build depends on monotone that is currently not in buster

[Adrian Bunk]

Source: bugs-everywhere
Version: 1.1.1-4
Severity: serious
Tags: ftbfs
Control: block -1 by 888612 889556

bugs-everywhere build depends on monotone that is currently
not in buster due to #888612 and #889556.

Processed: bugs-everywhere build depends on monotone that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 888612 889556
Bug #918268 [src:bugs-everywhere] bugs-everywhere build depends on monotone 
that is currently not in buster
918268 was not blocked by any bugs.
918268 was not blocking any bugs.
Added blocking bug(s) of 918268: 889556 and 888612

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

Bug#918249: doc-rfc: please switch to ps2txt for testsuite

[Gianfranco Costamagna]

 thanks  for having a look! I was wondering about something more subtle and 
behind the scenes :)
btw for some reasons the ci is not running the testsuite on 
unstablehttps://ci.debian.net/packages/d/doc-rfc/probably because testing is 
sad?
I don't know, I tried the -2 I committed on git on debomatic and the 
autopkgtestsuite was good :)
cheers!
G.

Il venerdì 4 gennaio 2019, 21:10:24 CET, Iustin Pop  ha 
scritto:  
 
 On 2019-01-04 19:45:26, Gianfranco Costamagna wrote:
> Source: doc-rfc
> Version: 20181229-1
> Severity: serious
> tags: patch
> 
> Hello, the following Ubuntu patch [1] does the switch from pstotext (really 
> unmaintained, and out from testing),
> to ps2txt, part of src:ghostscript.
> 
> I'm filing this bug as "serious", because it means that the autopkgtestsuite 
> is not runnable with a "testing" codebase
> (since pstotext is out from buster)
> 
> [1] 
> https://launchpadlibrarian.net/364763538/doc-rfc_20170121-1_20170121-1ubuntu1.diff.gz
> 
> I'm also committing the fix for this bug on git, feel free to upload it (or 
> ask me to do it)!

Ouch, I completely forgot about this issue, really sorry. doc-rfc has so
many wishlist bugs but I got into the bad habit of not actually looking
at the bug list.

Thanks, I'll make an upload over the weekend.

iustin
  

Bug#918249: doc-rfc: please switch to ps2txt for testsuite

[Iustin Pop]

On 2019-01-04 20:16:40, Gianfranco Costamagna wrote:
>  thanks  for having a look! I was wondering about something more subtle and 
> behind the scenes :)
> btw for some reasons the ci is not running the testsuite on 
> unstablehttps://ci.debian.net/packages/d/doc-rfc/probably because testing is 
> sad?
> I don't know, I tried the -2 I committed on git on debomatic and the 
> autopkgtestsuite was good :)

Hrmm, I thought I'd get an email about this, but no, seems I have to
look manually at ddpo. One more thing to add to my notes…

I'll try to sort this out soon, before the soft freeze. Not sure I can
finish everything this weekend.

iustin

Processed: eficas build depends on python-openturns that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 897768 902513
Bug #918273 [src:eficas] eficas build depends on python-openturns that is 
currently not in buster
918273 was not blocked by any bugs.
918273 was not blocking any bugs.
Added blocking bug(s) of 918273: 902513 and 897768

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

Bug#918273: eficas build depends on python-openturns that is currently not in buster

[Adrian Bunk]

Source: eficas
Version: 6.4.0-1-2
Severity: serious
Tags: ftbfs
Control: block -1 by 897768 902513

eficas build depends on python-openturns that is currently
not in buster due to #897768 and #902513.

Bug#918274: foodcritic build depends on chef that is currently not in buster

[Adrian Bunk]

Source: foodcritic
Version: 13.1.1-2
Severity: serious
Tags: ftbfs
Control: block -1 by 909205

foodcritic build depends on chef that is currently
not in buster due to #909205.

Processed: foodcritic build depends on chef that is currently not in buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 909205
Bug #918274 [src:foodcritic] foodcritic build depends on chef that is currently 
not in buster
918274 was not blocked by any bugs.
918274 was not blocking any bugs.
Added blocking bug(s) of 918274: 909205

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