Bug#903224: udev: Fails to upgrade

[Sven Joachim]

On 2018-07-08 03:05 +0200, Michael Biebl wrote:

> Control: tags -1 moreinfo unreproducible
>
> Am 08.07.2018 um 00:26 schrieb Kurt Roeckx:
>> Package: udev
>> Version: 239-5
>> Severity: serious
>> 
>> Hi,
>> 
>> When upgrading udev, it failed to upgrade, because udev didn't
>> want to start. I think there might be some ordering problem.

In the logs it can be seen that udev is configured before systemd, and
that apparently hits the same problem as #902185.

> Unfortunately I can't reproduce your problem. I've just test-upgraded a
> buster VM from 238-5 to 239-5 without a problem.
> Can you provide instructions how to reproduce the problem?

The following steps might reproduce it:

- Downgrade the *systemd* and *udev* packages to 238-5.

- Unpack the 239-5 packages with dpkg --unpack.

- Run "dpkg --configure libudev1 udev".

Cheers,
   Sven

Bug#894476: rcc: please honour SOURCE_DATE_EPOCH (was Re: RCC: provide option to encode EPOCH timestamp)

[Chris Lamb]

Hi Thorsten,

> AIUI, S_D_E is used as a *delimiter*, not as a timestamp *all* files
> are to be set to.

I've found that having a shared vocabulary is very useful so just in
case it helps we tend to use the term "clamping" when referring to
this MIN(a,b) concept rather than "delimiter" or similar.  eg. "foo
clamps the mtimes to SOURCE_DATE_EPOCH".

> Chris/H01ger, please correct me if I’m wrong, but this is
> how I understood S_D_E to work.

It is not required. Does the canonical specification not explain?

  https://reproducible-builds.org/specs/source-date-epoch/
  
I pedantically refer you to that /only/ because if it is not clear
enough then there is a need to revise it. :)


Best wishes,

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

Bug#903002: mc reset confuses ipmievd

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello Sergio,

thanks for your testing.

Can you please file a bug report to the upstream author[1] ?


CU
Jörg

[1] https://github.com/ipmitool/ipmitool/issues/new
- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

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

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


git:  https://jff.email/cgit/

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


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

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltBsX8ACgkQCfifPIyh
0l3tNBAAh/5mc0G91OimtQIIlKROTT9Yd1BajlcUUy9R+QP5jm/FwM6uuUV5eLy8
azwO0kNnHO9qcSW/Lb/aDTB3SfcuxqeqTmtouFDCTASmHqvrlBR9HjOWC+DjGNNK
x9+5L7KjetRgMxSfJMgK+uzEAsmM1knDe3VXfqQSx6ywz23H0C58f2pyUE/N2MX5
e5eh7wLV1fLIqOJh/exN5PGagAIQGJklGm11lDUS36QgvQm65jz0HE/Q86JeKuDB
DhhGgMSu9aJGB191twPpJrvk5Vd1MXcU9dzf1n0ru8IBX6XTCHCd2BqIt/Z5QX3g
X+Ug7OQa8XIYVJRjAxfEHNmUaNIG6eryLGJ0xHI+I861UGU5wvXOcP4P3lH6NFbE
9CME7b1pDVvQyTOfiL/s8i0wAjbPAgDjdsLtc93KTuYBte3ftNG7nJgY9o1yQ1kb
XKXCNnAFBIxhNJZQKJpMF4NwO8ICKIbxKXR8XNJFZmsrc3fVV3Hh9hSIurFYxhLQ
aTBWRFzevGbVGOpPKApA80oR73sDxktS8qFEgCGTeasnoLgO3eHfodTcJsyeyQqi
w0HjgZli/jQCocbR3uxlb4qZ8AqarSsHA0oLk9s1Sg8Ci2aymQAHrsEFvfMxqYmR
0g6tgU/gxzGy/tQ5UVHbt0cm0/0Dp4O1SnI0hRXTn/yQUH8ZfqM=
=UoC8
-END PGP SIGNATURE-

Bug#902787: Add support for JTS 1.15

[Sebastiaan Couwenberg]

On 07/08/2018 12:19 AM, Emmanuel Bourg wrote:
> Le 07/07/2018 à 23:16, Sebastiaan Couwenberg a écrit :
>> Control: severity -1 serious
>>
>> jts (1.15.1+ds-1) has been uploaded to unstable.
> 
> Hi Sebastiaan, do you think you could provide a patch fixing the reverse
> dependencies please?

All the bugs already have patches, and are tagged accordingly:

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=902790;filename=spatial4j_0.5-1.debdiff;msg=5
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=902789;filename=spatial4j-0.4_0.4.1-4.debdiff;msg=5
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=902787;filename=h2database_1.4.196-2.debdiff;msg=5

I cannot provide patches for the reverse dependencies of spatial4j &
h2database.

Kind Regards,

Bas

Bug#903150: tune2fs: No method to change MMP paramter(s)

[Elliott Mitchell]

On Sun, Jul 08, 2018 at 12:43:17AM -0400, Theodore Y. Ts'o wrote:
> OK, thanks for more clearly describing what it was you were do.  (Pro
> tip: it saves a lot of time if you describe in great detail how you
> reproduced the problem, instead of explaining what you think the
> problem was.  The original bug report had all sorts of misconceptions
> of how MMP worked.  If you have a direction for a clean reproduction,
> you would have saved yourself and me a lot of time.)

It is easy to build wildly incorrect mental models of how a feature works
if you haven't looked at the code, but observed problems due to bugs...

Particularly if the documentation doesn't talk about the implementation.
At which point confirming details identifies which are the crucial bits
to report.

> Yes, the bug is that the kernel doesn't actually clear the MMP
> sequence when the file system is remounted readu-only.  The original
> use case for MMP was for high-end HPC clusters using Lustre, and they
> never used it on the root file system, nor did they remount file
> systems read-only.  So you found an issue that the original author and
> users of the MMP feature hadn't considered or tripped up against.
> 
> The fix is relatively simple[1], but it may be a while before it gets
> backported to the 4.9 kernel.  In particular, I want to wait for
> Andreas Dilger, who originally implemented the MMP feature, to review
> the patch.
> 
> [1] http://patchwork.ozlabs.org/patch/940892/

I'll be waiting for that news.  I'm a bit unsure of where the bug should
be reassigned to...  (hrmm, that is more kernel source packages than I
knew of)


> > `dumpe2fs` 1.43.4-2 fails to produce that output.  "MMP block number" and
> > "MMP update interval" appear in the output, but none of the other values
> >
> 
> This is a new feature that will be in dumpe2fs 1.44.3.  Debian
> unstable has e2fsprogs 1.44.3~rc2-1 uploaded as of July 3rd.  1.44.3
> will be released shortly.

I was advising providing that information in that format was going to be
a bit difficult.

> > I'm very suspicious e2fsprogs still has some sort of issue lurking.  Why
> > does `tune2fs -f -E clear_mmp` clear the issue for 1 and only 1 rw mount?
> 
> Because -E clear_mmp simply resets the MMP sequence number.  When you
> remount it read-write it sets the MMP sequence number again.  The bug,
> as explained in [1] above, is when the file system is remounted
> read-only, the MMP sequence number isn't getting reset.  Using tune2fs
> -f -E clear_mmp is simply doing what the kernel should have been doing
> automatically.
> 
> 
> Finally, please note that MMP is an advanced feature, and Debian
> Stable (sometimes not-so-fondly referred to as "Debian Obsolete") is
> maintained by volunteers and not by paid engineers who are willing to
> backport all manner of features and bug fixes to ancient, obsolete
> kernels such as Linux 4.9.  There is a *reason* why enterprise
> companies pay Red Hat and SuSE the big $$$.  If you want to use
> advanced features, you may find that it is better to use newer kernels
> and engage directly with the upstream developers.
> 
> I just want to make sure your expectations are set correctly.  This
> was an easy bug, so I didn't mind spending a few minutes while I am on
> vacation to investigate it.  In general, though, especially when you
> try to use advanced features on a community distro, there may be more
> self-help required.
> 
> (For example, if you want the fix right away, you may need to compile
> a new kernel yourself.  And while an enterpise distro might be willing
> to backport MMP status feature in dumpe2fs to an ancient e2fsprogs,
> that's not going to happen for Debian Stable.  You'll probably have to
> build e2fsprogs 1.44.3 for yourself and install it on your system.)

Yawn.  Been there.  Done that.  Not like I've built 1.2.13 and examples
of most kernel series since then (oh wait! I *have*!).  Nor that I've
been paid to do system administration or software development (oh
wait...).

I may end up fighting libtool, at which point a number of library
dependancies may start getting downgraded from "Depends" to "Recommends"
or "Suggests".


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#903243: RFS: shotwell/0.28.3-1

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package "shotwell"

   Package name: shotwell
   Version : 0.28.3-1
   Upstream Author : Jim Nelson 
   URL : https://wiki.gnome.org/Apps/Shotwell
   License : LGPL-2.1, CC-BY-SA-3.0, GPL-2+
   Section : gnome

It builds those binary packages:

 shotwell   - digital photo organizer
 shotwell-common - digital photo organizer - common files

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/shotwell


Alternatively, one can download the package with dget using this
command:

dget -x 
https://mentors.debian.net/debian/pool/main/s/shotwell/shotwell_0.28.3-1.dsc



  Changes since the last upload:

  * New upstream release.
  * Remove upstream applied patches:
- 0100-ios8.patch
  * New debian/patches/0105-gitversion.patch to fix FTBFS.
  * Migrate to debhelper 11:
- Change debian/compat to 11.
- Change debhelper version in debian/control to >= 11.
  * debian/control:
- Switch Vcs-* to new location.
  * debian/copyright:
- Use secure copyright format URI.
- Bump years to 2018.
  * Declare compliance with Debian Policy 4.1.4 (No changes needed).
  * Remove unneeded comments from shotwell.lintian-overrides.

  Regards,
   Jörg Frings-Fürst

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

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

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


git:  https://jff.email/cgit/

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


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

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltBq4sACgkQCfifPIyh
0l0c4BAAy11MAlR4brnQQRWx0nyg/oVYULSj12df0iArm6xluW1kVZQpUGHRMgCs
E9Y4CVIlTMQ2vbMglO1+82vsbeZgUMcIzWFUkqewog6CB80T3eH02izHCU8jaIk1
IfPqeL5umq08GuB0tWOr/abkC7iTX9rofK1Q2mZCwzsELyrntqMAhR/kl7SztSBn
yy3vb1+tu28dTpzVpunYnzENexuxEShhZgz1sF0/HnBOHOjpkRnyYHEp0tXhljW5
mGhmjR4OkhMKkFZODdX+okkxE0AHx0JF9dh/YkQXB/lpIqIpWSPw41uXI0lYDtue
ln3wKtLE0eykT+fsQSoXpHYAQzJW53rykhTEzKV5XkXCNjotPy0A17jzz0gUsJRK
+pilOoMbrdfR4lyGjdCVlFPt4aBIuHOPRgpql8rubiVd9LQ60T3AjaGwYdaBJlJc
9tcVN6JahhKncr8jEJalFEEbyenkc4AJIjcYSAaLehjxRPr2iCa55tICcPZRtbX6
IFg6Yf0xMZnqPgpl7Q7b6RYZEmE/xpVoHYIGYzXuiO2pP56Cc89TdNP0WeIEHMmx
UlRXlTcz/eKAOOxhQ1KGE+f26Rk/ZDZSOgYEN1RnEjeTwZiCPUTWK9plTXTsF7/W
5fVqWUG0J8md3kMzlT76XmOZulb0X94EOkOBcFxOgNz1YSB+W3g=
=dUZx
-END PGP SIGNATURE-

Bug#903242: Is there a canonical way to install libvirt-daemon with systemd settings, such as "libvirt-bin" ?

[Haruki TSURUMOTO]

Package: libvirt
Version: 3.0.0-4+deb9u3
Severity: normal

Dear maintainers,
I have a question about libvirtd packages.

I have tried installing libvirtd packages on my machine.
According to Debian Administrator's Handbook,
https://debian-handbook.info/browse/en-US/stable/sect.virtualization.html#id-1.15.5.14
libvirt-bin provides the libvirtd daemon

However, "libvirt-bin" is dropped in debian stretch.
So, I installed "libvird-daemon" on my system
then I connect to libvirtd from remote machine's virt-manager but error
occured.
libvirtd is not working since systemd services were not installed.

Traditional "libvirt-bin" package depends "libvirt-daemon-system".

IMHO, "libvird-daemon" should recommends to install "libvirt-daemon-system"
or Is there a canonical way to install libvirt-daemon with systemd
settings, such as "libvirt-bin" ?

Thanks.

-- 
Haruki TSURUMOTO
PGP Fingerprint:3718 C84E 4EDA 1B5C 4F26 8639 9D3D EE3F 63A6 000E



signature.asc
Description: OpenPGP digital signature

Bug#903241: libunistring/0.9.10-1

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libunistring"

   Package name: libunistring
   Version : 0.9.10-1
   Upstream Author : Bruno Haible 
   URL : https://www.gnu.org/software/libunistring/
   License : LGPL-3+ or GPL-2+, FreeSoftware, 
 GPL-2+ with distribution exception,
 GPL-3+ or GFDL-1.2+, GPL-3+, GPL-2+,
 MIT
   Section : libs

It builds those binary packages:

libunistring-dev - Unicode string library for C - development files
libunistring2 - Unicode string library for C

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/libunistring


Alternatively, one can download the package with dget using this
command:

dget -x 
https://mentors.debian.net/debian/pool/main/libu/libunistring/libunistring_0.9.10-1.dsc


Changes since the last upload:

  * New upstream release.
- Refresh symbols file.
  * debian/control:
- Switch Vcs-* to new loacation.
- Use secure URI for homepage.
  * Migrate to debhelper 11:
- Change debian/compat to 11.
- Bump minimum debhelper version in debian/control to >= 11.
  * Declare compliance with Debian Policy 4.1.4 (No changes needed).


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

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

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


git:  https://jff.email/cgit/

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


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

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltBp9AACgkQCfifPIyh
0l00Sg/+N/PRc1OxI1EbNcYE/rdOgdtgWj81R/XCVM9GsvBcLDtD+Nke4HfcyVlV
YDVlh0yLDOkgs3ag/E+ho/D6mM5zVRwoq3/VSsvef289/aZakciwPmsQE3pNqnFv
ue7K29FN5Y7I8a/2/dFX+PqaXCj/istS4tXKjxdrfQF0wakHZIUE9+kcmBnX0lW7
QfFyN+eZp/DKejWljC0VREmS62NrNH9CMB4k9Ae/lIYE9c/dZ/d3zWz8su8yuoMx
Se/H3lQlVPh+tvlFaJBqKlEHj/Yd65lvqWj4y3rzxwvg8RlFFpIm3JqH4qBEgpCU
WHvyLtJgjLBYznLuJKU+Ns3IIsViwKE1+hTFIe7XZiM2bA0fRqs0cLFKAPjoARdU
45RO+upyJYvirH7HRFUKgt9Prp2ccCXSxgyu4iI6ULY6X64Vt7n+7TeVdNrIpbdN
le9Ivl7mcb+m8ilSZZD5sq3Vk24BHUgRmG/Uz935si1hQNVcmDA5tt+3qw9almps
mm6ep6ZRp09XmM+jmJCoF6UAeXOamBm23d085UpdYBxMo1sLJtDrCAMRxeJwnNgj
k/8C0xlN2RBhNBlPQ80iYnZOvD4hoAPF/B/0I4euYutVDt1615uHUrL5s1ctHE85
NgQVdGkxnNg3qB3JN8o9Tn/AaoYKRyXRNPPsDw86i68wrVIF15s=
=9TFs
-END PGP SIGNATURE-

Bug#903240: /var/lib/openvpn/chroot/ is silently prepended to the crl-verify-file path

[Cody Brownstein]

Package: network-manager-openvpn
Version: 1.8.4-1

`/var/lib/openvpn/chroot/` is silently prepended to the
`crl-verify-file` path specified in the keyfile (connection profile).
For example, `crl-verify-file=/var/lib/openvpn/chroot/crl.rsa.2048.pem`
becomes `/var/lib/openvpn/chroot//var/lib/openvpn/chroot/crl.rsa.2048.pem`.

This results in nm-openvpn failing with the following error:

`Options error: --crl-verify fails with
'/var/lib/openvpn/chroot//var/lib/openvpn/chroot/crl.rsa.2048.pem': No
such file or directory`

Bug#903239: RFS: uriparser/0.8.5-2

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "uriparser"

   Package name: uriparser
   Version : 0.8.5-2
   Upstream Author : Sebastian Pipping 
   URL : https://github.com/uriparser/uriparser
   License : BSD-3-clause, LGPL-2.1+, GPL-3+
   Section : libs

It builds those binary packages:

liburiparser-dev - development files for uriparser
liburiparser-doc - documentation files for uriparser
liburiparser1 - URI parsing library compliant with RFC 3986

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/uriparser


Alternatively, one can download the package with dget using this
command:

dget -x 
https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.8.5-2.dsc


Changes since the last upload:

  * debian/control:
- Switch Vcs-* to new loacation.
  * Remove now useless debian/liburiparser-doc.lintian-overrides.


  Regards,
   Jörg Frings-Fürst


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

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

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


git:  https://jff.email/cgit/

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


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

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltBpZAACgkQCfifPIyh
0l1WhhAAgnqokBROCTTgYk7C88ZnwxyentxDVwRHElUrZ/esoFEumfewudw1K43x
D4zlvowc7SFfkFLQJuSkoYOh3OmLv4BgwZj340KDcgCZvMCte4uuO/VGnMr2k+Cc
5X1bszIELQIcjvXhKrWzOuMY5Sx1D8mDxgP9RzJ2EVtCRMdFq38NlnKuPDG/OkcT
f4RNa2O4ouoqkuKnWa7+XnO1OBRbcMSOj2xKIQKlkm4dyR8H5sv8G02UQV+R2UIy
68WmCVuniuaOTJwJE/6N1e5fXRIAhvpZ4dTDvuekz1vc5SIZqcv6KdJPm2oxc4Fx
+KuBMwcvpGsJW8ZoT4cUHIjs2Xrz+VTtpP+eZeRwLPsheZmBDktYgTXornfGkGeG
nt96KOstx7+vntZDCp7L96HCbo0X6v/h8zG+6lHg7Qoig28gwdy5prk1CfGI/RfP
vetVQEO4Xc2cLMQxWQw354zGmxfJeeJSwsPRcPjCuP2aWJBNNKVc6C5mtUZkgUx4
NtynF20JJw9t/51K7FkQDW2lsV9gThEUtMvXo9yTzhYCwCILvCIKsUSY4TqwvaEK
e5622PXFG8NT79vA77J84QvMFVmOvLaslzhZK4KLR6697ybAnmc9RI8JqkW0LKmA
91AGFZlGVrLeQCeibaR/LdsOcGRS73AZEL3RJw8oCJCyR+UKBSE=
=MP3x
-END PGP SIGNATURE-

Bug#903238: cacti: Please run autopkgtest against default-mysql-server instead of a specific implementation

[Steve Langasek]

Package: cacti
Version: 1.1.38+ds1-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu cosmic ubuntu-patch

Dear Paul,

In Ubuntu, I've adjusted the autopkgtest for cacti to test against
default-mysql-server instead of mariadb-server.  The reason for this is that
mariadb-server is not the default implementation of mysql-server in Ubuntu,
and mariadb-server was recently buggy on arm64 so not only was it useful to
run the autopkgtest against the mysql-server that we use, it was also useful
to not block against mariadb-server.  Similarly, since you recently dropped
the autopkgtest to test against mysql-server in Debian due to it being
absent from testing, I think it makes sense to only test against the default
mysql implementation in Debian.

Please consider the attached patch for inclusion in Debian.
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru cacti-1.1.38+ds1/debian/tests/control 
cacti-1.1.38+ds1/debian/tests/control
--- cacti-1.1.38+ds1/debian/tests/control   2018-04-18 02:11:55.0 
-0700
+++ cacti-1.1.38+ds1/debian/tests/control   2018-07-06 15:40:22.0 
-0700
@@ -1,3 +1,3 @@
 Tests: check-all-pages
-Depends: mariadb-server, @, wget, apache2
+Depends: default-mysql-server, @, wget, apache2
 Restrictions: needs-root, allow-stderr, isolation-container

Bug#903150: tune2fs: No method to change MMP paramter(s)

[Theodore Y. Ts'o]

On Sat, Jul 07, 2018 at 09:21:47AM -0700, Elliott Mitchell wrote:
> 
> This then suggests this bug should be against linux-source-4.9 instead of
> e2fsprogs.
> 
> A few command sequences and notes on how fast the command executes on the
> machine:
> 
> mount / -o rw,remount   => slow
> mount / -o ro,remount   => fast
> mount / -o rw,remount   => slow
> mount / -o ro,remount   => fast
> 
> By your explanation, the first ro,remount should set the sequence to 0
> (or appropriate equivalent value).

OK, thanks for more clearly describing what it was you were do.  (Pro
tip: it saves a lot of time if you describe in great detail how you
reproduced the problem, instead of explaining what you think the
problem was.  The original bug report had all sorts of misconceptions
of how MMP worked.  If you have a direction for a clean reproduction,
you would have saved yourself and me a lot of time.)

Yes, the bug is that the kernel doesn't actually clear the MMP
sequence when the file system is remounted readu-only.  The original
use case for MMP was for high-end HPC clusters using Lustre, and they
never used it on the root file system, nor did they remount file
systems read-only.  So you found an issue that the original author and
users of the MMP feature hadn't considered or tripped up against.

The fix is relatively simple[1], but it may be a while before it gets
backported to the 4.9 kernel.  In particular, I want to wait for
Andreas Dilger, who originally implemented the MMP feature, to review
the patch.

[1] http://patchwork.ozlabs.org/patch/940892/

> > MMP_block:
> > mmp_magic: 0x4d4d50
> > mmp_check_interval: 5
> > mmp_sequence: 0xff4d4d50
> > mmp_update_date: Sat Jul  7 10:50:26 2018
> > mmp_update_time: 1530975026
> > mmp_node_name: cwcc
> > ummp_device_name: loop0
> > 
> > is purely for debugging purposes.  All of the MMP mechanism is done
> > via the mmp_sequence number.
> 
> `dumpe2fs` 1.43.4-2 fails to produce that output.  "MMP block number" and
> "MMP update interval" appear in the output, but none of the other values
>

This is a new feature that will be in dumpe2fs 1.44.3.  Debian
unstable has e2fsprogs 1.44.3~rc2-1 uploaded as of July 3rd.  1.44.3
will be released shortly.

> I'm very suspicious e2fsprogs still has some sort of issue lurking.  Why
> does `tune2fs -f -E clear_mmp` clear the issue for 1 and only 1 rw mount?

Because -E clear_mmp simply resets the MMP sequence number.  When you
remount it read-write it sets the MMP sequence number again.  The bug,
as explained in [1] above, is when the file system is remounted
read-only, the MMP sequence number isn't getting reset.  Using tune2fs
-f -E clear_mmp is simply doing what the kernel should have been doing
automatically.


Finally, please note that MMP is an advanced feature, and Debian
Stable (sometimes not-so-fondly referred to as "Debian Obsolete") is
maintained by volunteers and not by paid engineers who are willing to
backport all manner of features and bug fixes to ancient, obsolete
kernels such as Linux 4.9.  There is a *reason* why enterprise
companies pay Red Hat and SuSE the big $$$.  If you want to use
advanced features, you may find that it is better to use newer kernels
and engage directly with the upstream developers.

I just want to make sure your expectations are set correctly.  This
was an easy bug, so I didn't mind spending a few minutes while I am on
vacation to investigate it.  In general, though, especially when you
try to use advanced features on a community distro, there may be more
self-help required.

(For example, if you want the fix right away, you may need to compile
a new kernel yourself.  And while an enterpise distro might be willing
to backport MMP status feature in dumpe2fs to an ancient e2fsprogs,
that's not going to happen for Debian Stable.  You'll probably have to
build e2fsprogs 1.44.3 for yourself and install it on your system.)

Regards,

- Ted

Bug#903015: stretch-pu: package gridengine/8.1.9+dfsg-4

[Afif Elghraoui]

على السبت  7 تـمـوز 2018 ‫07:35، كتب Adam D. Barratt:
> With the above change, please feel free to upload.

Uploaded. I hope source-only is fine.

Thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#903192: [Debian-med-packaging] Bug#903192: sniffles: FTBFS in buster/sid (dh_installman: Cannot find "debian/sniffles.1")

[Afif Elghraoui]

Hi, Santiago

على السبت  7 تـمـوز 2018 ‫07:40، كتب Santiago Vila:
> The build was made with "dpkg-buildpackage -B" in my autobuilder.
> (This one does not seem to fail with plain "dpkg-buildpackage")
> 
> [ Note: There has been a recent change in debhelper behaviour, the current
>   behaviour is the intended one. See Bug #903133 for details ].

This is very strange, firstly because the behavior is different with or
without `-B` despite the source package not defining any arch:all binary
packages to begin with.

The error seems to be because the manpage is defined in debian/manpages,
but is created during the package build. I've worked around that, but
it's still curious why the error is not consistent without `-B`.

regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#903138: Unmet dependencies

[Jörg Frings-Fürst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Sebastian,

Am Samstag, den 07.07.2018, 23:21 +0200 schrieb Sebastian Ramacher:
> On 2018-07-07 11:17:01, Jörg Frings-Fürst wrote:
> > reassign 903138 libplacebo 0.5.0-2
> > tags 903138 - moreinfo
> > tags 903138 - unreproducible
> > affects 903138 + vcl
> > thanks
> > 
> > Hi,
> > 
> > Am Samstag, den 07.07.2018, 00:10 +0200 schrieb Sebastian Ramacher:
> > > Control: tags -1 + moreinfo unreproducible
> > > 
> > > On 2018-07-06 23:34:58, Jörg Frings-Fürst wrote:
> > > > Package: src:vlc
> > > > Version: 3.0.3-1+b1
> > > > Severity: grave
> > > > 
> > > > 
[...]

> > I have search for the reason and found that libplacebo has bump the
> > SOName from 4 to 5 without transition. 
> 
> What do you mean with that? The transition was competed by vlc 3.0.3-
> 2 being
> built against libplacebo5.
> 

There is no Breaks / Replaces in debian/control.


> Cheers
> 
[...]

CU
Jörg

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

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

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


git:  https://jff.email/cgit/

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


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

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltBmnUACgkQCfifPIyh
0l2HrRAAhxaS76J7hNfYqLN6yNCFXoVXXevJeFwttJ+7sFX+pP1D4GJN7kcfNbEq
UHFDUnTZ39b3te1cMNlO45uVZ0mMsE9eGCNnfOSYP93XDRSIacR+NuCNYLwG6fmO
ng6Y5udpB3vvkXa12w2WLQEduYAKRJLlmCUuwlq38FF2ucHMxXsIG5ahjRk3/Ptl
XW3axb6PIr8gqZbipiD9nqYTBaz1ZI72lnFOO5qBuegnFm5/kZPYPynhfnQ02TD2
+8oWPWS49wJF9yr6MO0/XF8H0wemZZEBzG67cqGLuZ8lwzMWYJinTqdJssA8FJFj
StaaToI+MydvjxHcuhnDh1rYTMYDGX+gfrXwU+V/0JvDQRlNmbZCUINbaNEEhyry
Yz+T45ntJsdmdgVqRy4DdjRIo45b57GWOJAG/ZhmEQEXAiVDx9FVP1KvqLWO380g
re3zzcoyxJgRiQm2d40BEDmOiUFq5oG81ISn/0LYhQNQrAVzn4BQQyGjT3N+c31J
ugaQvTkQZEGW/lJ4YZ1WDmZrhyJuLT5VsAgogE+sjoYh+0GoJV1c+BgIBDE1eb8I
m17vxqvZXvYpe2eYE1GFWx99562wbKTk081AbSKH9J/Eqeuh5MtkEdjObhsQ3Zd7
zgE3AdN6REankDgYruNl/TB0D3U4DGFKjbQX55RC9ifMpgiFgDA=
=kk1G
-END PGP SIGNATURE-

Bug#903122: debian-installer-9-netboot-amd64: Please add char/virtio_console module (paravirtualized serial) to netinst

[Cyril Brulebois]

Hi Vincent,

Vincent Caron  (2018-07-06):
> Package: debian-installer-9-netboot-amd64
> Severity: wishlist
> Tags: d-i
> 
> Dear Maintainer,
> 
> while automating Debian image creations thru netinst + KVM, I stumbled
> upon a limitation from the emulated UARTs (if one sends back from the
> guest to the host large logs, it might overrun the UART buffer which
> complains with kernel messages about overused IRQ).
> 
> While turning to paravirtualized serial, I realized that the
> char/virtio_console kernel module is missing in the netinst's initrd,
> and this driver is required very early. Obviously I still use the UART
> emulation for kernel messages since it's the only _very early_ output
> medium, thus emulated UART and paravirtualized serials should be used
> together.

You mention netinst a few times, but you seem to be talking about
netboot really. netinst is an ISO image with a bunch of packages, enough
to configure everything needed to pull the rest of the system from a
network mirror; netboot is kernel+initrd for PXE boots and similar
minimalistic approaches.

> If this module makes it to netinst's initrd, one would use those kvm
> args:
> 
> -chardev file,path=virtiocon0.log,id=virtiocon0
> -device virtio-serial
> -device virtconsole,chardev=virtiocon0
> 
> ... and in the guest a /dev/hvc0 would appear. Anything the guest would
> write to /dev/hv0 would en up in the host's vitriocon0.log file.

So it seems we're talking about kernel/drivers/char/virtio_console.ko
that could be added to either the serial-modules udeb or the
virtio-modules one. Kernel maintainers, what do you think?

This might be worth backporting to stretch too. I can send patches when
you've selected the udeb we should be adding this module to.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#903237: openorienteering-mapper: FTBFS with Qt 5.11.1 in experimental due to tests

[Simon Quigley]

Source: openorienteering-mapper
Version: 0.8.1.1-1
Severity: important
User: debian-qt-...@lists.debian.org
Usertags: qt5.11.1

Dear Maintainer,

Your package fails to build from source against Qt 5.11.1 in 
Experimental with the following error:


Test project /<>/obj-x86_64-linux-gnu
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 1
  Start  1: tst_qglobal

1: Test command: /usr/bin/cmake "-P" "tst_qglobal-RUN.cmake"
1: Test timeout computed to be: 1000
1: * Start testing of tst_QGlobal *
1: Config: Using QtTest library 5.11.1, Qt 5.11.1 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)

1: PASS   : tst_QGlobal::initTestCase()
1: PASS   : tst_QGlobal::testqOverload()
1: PASS   : tst_QGlobal::cleanupTestCase()
1: Totals: 3 passed, 0 failed, 0 skipped, 0 blacklisted, 0ms
1: * Finished testing of tst_QGlobal *
 1/17 Test  #1: tst_qglobal ..   Passed0.06 sec
test 2
  Start  2: encoding_t

2: Test command: /usr/bin/cmake "-P" "encoding_t-RUN.cmake"
2: Test timeout computed to be: 1000
2: * Start testing of EncodingTest *
2: Config: Using QtTest library 5.11.1, Qt 5.11.1 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)

2: PASS   : EncodingTest::initTestCase()
2: PASS   : EncodingTest::testCodepageForLanguage(cs)
2: PASS   : EncodingTest::testCodepageForLanguage(cs_x)
2: PASS   : EncodingTest::testCodepageForLanguage(ru)
2: PASS   : EncodingTest::testCodepageForLanguage(ru_RU)
2: PASS   : EncodingTest::testCodepageForLanguage(de)
2: PASS   : EncodingTest::testCodepageForLanguage(??)
2: PASS   : EncodingTest::testCodecForName()
2: PASS   : EncodingTest::cleanupTestCase()
2: Totals: 9 passed, 0 failed, 0 skipped, 0 blacklisted, 4ms
2: * Finished testing of EncodingTest *
 2/17 Test  #2: encoding_t ...   Passed0.06 sec
test 3
  Start  3: georeferencing_t

3: Test command: /usr/bin/cmake "-P" "georeferencing_t-RUN.cmake"
3: Test timeout computed to be: 1000
3: * Start testing of GeoreferencingTest *
3: Config: Using QtTest library 5.11.1, Qt 5.11.1 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)

3: PASS   : GeoreferencingTest::initTestCase()
3: PASS   : GeoreferencingTest::testEmptyProjectedCRS()
3: PASS   : GeoreferencingTest::testGridScaleFactor()
3: PASS   : GeoreferencingTest::testCRS(EPSG:4326)
3: PASS   : GeoreferencingTest::testCRS(UTM)
3: PASS   : GeoreferencingTest::testCRSTemplates()
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Koblenz UTM)
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Koblenz GK3)
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Pruem UTM)
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Pruem GK2)
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Landau UTM)
3: PASS   : GeoreferencingTest::testProjection(LVermGeo RLP Landau GK3)
3: PASS   : GeoreferencingTest::testProjection(EPSG 5514 ČÚZK Dolní 
Temenice)

3: PASS   : GeoreferencingTest::cleanupTestCase()
3: Totals: 14 passed, 0 failed, 0 skipped, 0 blacklisted, 8ms
3: * Finished testing of GeoreferencingTest *
 3/17 Test  #3: georeferencing_t .   Passed0.07 sec
test 4
  Start  4: locale_t

4: Test command: /usr/bin/cmake "-P" "locale_t-RUN.cmake"
4: Test timeout computed to be: 1000
4: * Start testing of LocaleTest *
4: Config: Using QtTest library 5.11.1, Qt 5.11.1 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)

4: PASS   : LocaleTest::initTestCase()
4: XFAIL  : LocaleTest::testEsperantoQLocale() Cannot construct 
Esperanto QLocale from "eo" (issue #792).

4:Loc: [/<>/test/locale_t.cpp(57)]
4: XFAIL  : LocaleTest::testEsperantoQLocale() Cannot construct 
Esperanto QLocale from "eo_C".

4:Loc: [/<>/test/locale_t.cpp(60)]
4: XFAIL  : LocaleTest::testEsperantoQLocale() Cannot construct 
Esperanto QLocale for AnyScript, AnyCountry.

4:Loc: [/<>/test/locale_t.cpp(63)]
4: PASS   : LocaleTest::testEsperantoQLocale()
4: PASS   : LocaleTest::testEsperantoTranslationUtil()
4: PASS   : LocaleTest::cleanupTestCase()
4: Totals: 4 passed, 0 failed, 0 skipped, 0 blacklisted, 1ms
4: * Finished testing of LocaleTest *
 4/17 Test  #4: locale_t .   Passed0.05 sec
test 5
  Start  5: map_color_t

5: Test command: /usr/bin/cmake "-P" "map_color_t-RUN.cmake"
5: Test timeout computed to be: 1000
5: * Start testing of MapColorTest *
5: Config: Using QtTest library 5.11.1, Qt 5.11.1 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0)

5: PASS   : MapColorTest::initTestCase()
5: PASS   : MapColorTest::constructorTest()
5: PASS  

Bug#903236: RFS: fcitx-ui-light/0.1.3-3 [RC]

[Boyuan Yang]

Package: sponsorship-requests
Severity: important
X-Debbugs-CC: debian-input-met...@lists.debian.org sunwea...@debian.org 
a...@debian.org s...@debian.org

Dear Mike, debian-input-method members and mentors,

I am looking for a sponsor for the team package "fcitx-ui-light". This upload
mainly fixes the RC bug caused by team mailing list migration.

 * Package name: fcitx-ui-light
   Version : 0.1.3-3
   Upstream Author : Weng Xuetian 
 * URL : https://gitlab.com/fcitx/fcitx-ui-light
 * License : GPL-2+
   Section : utils

  It builds those binary packages:

fcitx-ui-light - light weight xlibs and xft based UI for Fcitx

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/fcitx-ui-light


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/f/fcitx-ui-light/fcitx-ui-light_0.1.3-3.dsc


  Git packaging repository:

https://salsa.debian.org/input-method-team/fcitx-ui-light.git


  Changes since the last upload:

 fcitx-ui-light (0.1.3-3) unstable; urgency=medium
 .
   * Team upload.
   * Refresh packaging instructions.
 + Apply "wrap-and-sort -abst".
 + Remove trailing spaces in d/changelog and d/rules.
   * debian/control:
 + Fix maintainer field and use debian-input-method team address.
   Closes: #899968.
 + Bump fcitx version requirement.
 + Remove DMUA information.
 + Update YunQiang Su's email address with @debian.org one.
 + Bump Standards-Version to 4.1.5.
 + Bump debhelper compat to v11.
 + Use GitLab as homepage.
 + Use canonical Vcs repo URL on Salsa platform.
   * debian/rules:
 + Use "dh_missing --fail-missing".
 + Apply full hardening.
   * Point d/watch to download.fcitx-im.org.
   * Refresh d/copyright information.

--
Regards,
Boyuan Yang


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

Bug#903235: deepin-qt5dxcb-plugin: FTBFS with Qt 5.11.1 in experimental

[Simon Quigley]

Source: deepin-qt5dxcb-plugin
Version: 1.1.8.8-1
Severity: important
User: debian-qt-...@lists.debian.org
Usertags: qt5.11.1

Dear Maintainer,

Your package fails to build from source against Qt 5.11.1 in 
Experimental with the following error:


dpkg-buildpackage
-

dpkg-buildpackage: info: source package deepin-qt5dxcb-plugin
dpkg-buildpackage: info: source version 1.1.8.8-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Yanhao Mo 
 dpkg-source --before-build deepin-qt5dxcb-plugin-1.1.8.8
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_auto_clean
   dh_clean
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-pedantic -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"QMAKE_CXXFLAGS_DEBUG=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2" "QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed" "QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed" QMAKE_STRIP=: PREFIX=/usr

Info: creating stash file /<>/.qmake.stash
   dh_auto_build
make -j10
make[1]: Entering directory '/<>'
cd platformplugin/ && ( test -e Makefile.qt5platform-plugin || 
/usr/lib/qt5/bin/qmake -o Makefile.qt5platform-plugin 
/<>/platformplugin/qt5platform-plugin.pro 
'QMAKE_CFLAGS_RELEASE=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-pedantic -Wdate-time -D_FORTIFY_SOURCE=2' 'QMAKE_CFLAGS_DEBUG=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2' 
'QMAKE_CXXFLAGS_RELEASE=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2' 'QMAKE_CXXFLAGS_DEBUG=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2' 
'QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed' 
'QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now -Wl,--as-needed' 
QMAKE_STRIP=: PREFIX=/usr ) && make -f Makefile.qt5platform-plugin

sh: 1: git: not found
Project ERROR: Not support Qt Version: 5.11.1
make[1]: *** [Makefile:45: 
sub-platformplugin-qt5platform-plugin-pro-make_first] Error 3

make[1]: Leaving directory '/<>'
dh_auto_build: make -j10 returned exit code 2
make: *** [debian/rules:20: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit 
status 2


Please note that your package uses Qt's private headers, and therefore 
may require code changes.


We plan on starting the Qt 5.11.1 transition soon.

Thanks.

--
Simon Quigley
tsimo...@ubuntu.com
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4

Bug#903234: python-gitlab: please backport to stretch

[Sandro Tosi]

Package: python-gitlab
Version: 1:1.3.0-2
Severity: normal

Hello,
i maintain a tool in stable (https://bts-link-team.pages.debian.net/bts-link/)
which i'm extending to use gitlab - could you please backport this module to
stretch? if you dont have time/interest, and you'd be ok with me backporting it,
please let me know and i'll package it.

thanks

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

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

Versions of packages python-gitlab depends on:
ii  python   2.7.14-4
ii  python-requests  2.18.4-1
ii  python-six   1.11.0-1

python-gitlab recommends no packages.

Versions of packages python-gitlab suggests:
pn  python-gitlab-doc  

-- no debconf information

Bug#894177: python-gitlab: Please drop the Python2 package

[Sandro Tosi]

> Please drop the python-gitlab package. It is the python2 version and
> it's not needed by the gitlab-cli package or anything else in Debian.
> It is better for developers and users to get used to the python3
> packages since python2 is obsolete and will eventually be removed from
> Debian.

this is so, so wrong...

guess what, i just needed the python2 module for a project i'm working
on: the absence of that package would have only made me work more (=
wasted developer time), for no reason at all (ie i would have NOT
converted this tool to python3 just because gitlab was not available)

please stop with this crusade against python2

Bug#903232: tracker.debian.org: Doesn't show mailing list archive link when maintainer is *@alioth-lists.debian.net

[Boyuan Yang]

Package: tracker.debian.org
Severity: normal

Dear tracker.d.o maintainers,

When the maintainer is old *@lists.alioth.debian.org or *@lists.debian.org 
mailing list, the page would automatically provide with a link to its mail 
archive page. However, when the team is using *@alioth-lists.debian.net 
directly, the link is not shown.

Example: tracker.debian.org/pkg/rust-bitflags

Please fix this issue if possible.

--
Regards,
Boyuan Yang

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

Bug#903231: RFP: tosdr -- Get information instantly about websites' terms of service and privacy policies, with ratings and summaries from the www.tosdr.org.

[Alessandro Barbieri]

Package: wnpp
Severity: wishlist

* Package name: tosdr
  Version : 0.6.2
  Upstream Author : t...@tosdr.org 
* URL : https://tosdr.org
* License : AGPL-3.0  CC BY-SA 3.0  CC BY 3.0 unported license
  Programming Lang: javascript
  Description : Get information instantly about websites' terms of service 
and privacy policies, with ratings and summaries from the www.tosdr.org.

“I have read and agree to the Terms” is the biggest lie on the web. We aim to 
fix that. “Terms of Service; Didn't Read” is a user rights initiative to rate 
and label website terms & privacy policies, from very good (class A) to very 
bad (class E).

This extension informs you instantly of your rights online by showing an 
unintrusive icon in the toolbar. You can click on this icon to get summaries 
from the Terms of Service; Didn't Read initiative.

Bug#903213: datalad: FTBFS in stretch/buster/sid

[Yaroslav Halchenko]

I bet it is the security fix which was recently introduced... Would need a 
patch to datalad from https://github.com/datalad/datalad/pull/2670 
Hopefully still easy to apply since datalad moved way far ahead since 0.4 .  
For buster/sid we will just release fresh version soon which would be 
compatible, so no need to patch there

On July 7, 2018 2:42:12 PM EDT, Santiago Vila  wrote:
>Package: src:datalad
>Version: 0.4.1-1
>Severity: serious
>Tags: ftbfs
>
>Dear maintainer:
>
>I tried to build this package in stretch + security +
>stretch-proposed-updates
>but it failed:
>
>
>[...]
> debian/rules build-indep
>dh build-indep --with python2 --buildsystem=pybuild
>   dh_testdir -i -O--buildsystem=pybuild
>   dh_update_autotools_config -i -O--buildsystem=pybuild
>   dh_auto_configure -i -O--buildsystem=pybuild
>   pybuild --configure --test-nose -i python{version} -p 2.7
>I: pybuild base:184: python2.7 setup.py config 
>running config
>   dh_auto_build -i -O--buildsystem=pybuild
>   pybuild --build --test-nose -i python{version} -p 2.7
>I: pybuild base:184: /usr/bin/python setup.py build 
>running build
>running build_py
>creating /<>/.pybuild/pythonX.Y_2.7/build/datalad
>
>[... snipped ...]
>
>File
>"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_annexrepo.py",
>line 247, in test_AnnexRepo_is_under_annex
>  assert_equal(ar.is_under_annex(testfiles, batch=batch), target_value)
>AssertionError: Lists differ: [False, False, False] != [True, False,
>False]
>
>First differing element 0:
>False
>True
>
>- [False, False, False]
>+ [True, False, False]
>
>==
>FAIL: datalad.support.tests.test_gitrepo.test_GitRepo_get_toppath
>--
>Traceback (most recent call last):
>File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in
>runTest
>self.test(*self.arg)
>File
>"/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py",
>line 706, in newfunc
>t(*(arg + (uri,)), **kw)
>File
>"/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py",
>line 536, in newfunc
>return t(*(arg + (filename,)), **kw)
>File
>"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_gitrepo.py",
>line 637, in test_GitRepo_get_toppath
>eq_(GitRepo.get_toppath(repo, follow_up=False), reporeal)
>AssertionError: '/tmp/datalad_temp_testrepo_bh4Q3X' !=
>'/tmp/datalad_temp_testrepo_bh4Q3X/sub dataset1/subm 1'
>
>==
>FAIL: datalad.support.tests.test_gitrepo.test_submodule_deinit
>--
>Traceback (most recent call last):
>File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in
>runTest
>self.test(*self.arg)
>File
>"/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py",
>line 706, in newfunc
>t(*(arg + (uri,)), **kw)
>File
>"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_gitrepo.py",
>line 840, in test_submodule_deinit
> eq_(['subm 1', 'subm 2'], [s.name for s in top_repo.get_submodules()])
>AssertionError: ['subm 1', 'subm 2'] != []
>
>--
>Ran 616 tests in 167.088s
>
>FAILED (SKIP=65, errors=63, failures=15)
>E: pybuild pybuild:283: test: plugin distutils failed with: exit
>code=1: cd /<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m
>nose -s -v datalad
>dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7
>--test-nose returned exit code 13
>debian/rules:27: recipe for target 'override_dh_auto_test' failed
>make[1]: *** [override_dh_auto_test] Error 25
>make[1]: Leaving directory '/<>'
>debian/rules:19: recipe for target 'build-indep' failed
>make: *** [build-indep] Error 2
>dpkg-buildpackage: error: debian/rules build-indep gave error exit
>status 2
>
>
>This is just how the build ends in my autobuilder with
>dpkg-buildpackage -A,
>but there are full build logs available here:
>
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/datalad.html
>
>A diff between the previous successful build log and this (failed) one
>yields this result:
>
>-Get:63 http://deb.debian.org/debian-security stretch/updates/main
>amd64 git-annex amd64 6.20170101-1+deb9u1 [10.9 MB]
>+Get:63 http://deb.debian.org/debian stretch-proposed-updates/main
>amd64 git-annex amd64 6.20170101-1+deb9u2 [10.9 MB]
>
>so it seems git-annex now behaves in a way which breaks the tests.
>
>(X-Debian-CC to Sean Whitton, who did the proposed-updates upload, in
>case he has any hint
>about the reason for this FTBFS in datalad).
>
>Thanks.

-- 
Sent from a phone which beats iPhone.

Bug#903230: RFP: tile-tabs-we -- Take tabs from parent windows and arrange them in layouts of tiled sub-windows, using the toolbar button, context menu or keyboard shortcuts. Makes it easy to browse,

[Alessandro Barbieri]

Package: wnpp
Severity: wishlist

* Package name: tile-tabs-we
  Version : 10.0
  Upstream Author : dw-...@gmx.com
* URL : https://addons.mozilla.org/addon/tile-tabs-we/
* License : GPL 2
  Programming Lang: javascript
  Description : Take tabs from parent windows and arrange them in layouts 
of tiled sub-windows, using the toolbar button, context menu or keyboard 
shortcuts. Makes it easy to browse, compare or monitor multiple pages. 
Synchronize scroll. Save and re-open layouts.

Reasons why you might want to use Tile Tabs WE

• To compare multiple web pages side-by-side.
• To synchronize scroll multiple web pages side-by-side.
• To open links from one tab in adjacent existing tabs.
• To save tiled layouts which can be re-opened for future use.

-

OVERVIEW

Tile Tabs WE provides facilities to take tabs from a parent window and arrange 
them in a layout of tiled sub-windows. This makes it easy to browse or monitor 
multiple web pages, or to compare multiple web pages using synchronized scroll. 
Layouts can be saved and later re-opened.

Tile Tabs WE is an alternative no-restart version of the well established Tile 
Tabs add-on for Firefox.

Tile Tabs WE is implemented using the new WebExtensions API and is available 
for both Firefox and Chrome with identical functions and user interfaces.

BASIC OPERATION

Tile Tabs WE emulates 'split browser' functionality with simple switching 
between the normal view and the tiled view.

Tile Tabs WE displays multiple tabs in a layout of tiled sub-windows ('tiles') 
within the area of the parent browser window. The tiles can be arranged 
horizontally, vertically, or in a grid.

A tiled layout can be created using the toolbar button, button menu, context 
menu, quick menu, or keyboard shortcuts. The parent window is indicated by a 
badge on the toolbar button showing the current number of tiles. Tiles are 
indicated by a badge on their toolbar buttons showing the letter 'T'.

When a tiled layout is created, tabs from the parent window are moved into the 
new tiles in the following order: first the selected tab, then tabs to the 
right of the selected tab, then tabs to the left of the selected tab, and 
finally if there are insufficient tabs then new tabs will be created.

A tiled layout can be saved and previously saved layouts can be opened or 
deleted. A default layout can be configured.

Dragging the borders between two tiles will resize both tiles (and any 
sub-tiles).

Bug#903229: RFP: updatescanner -- Firefox addon to monitors web pages for updates.

[Alessandro Barbieri]

Package: wnpp
Severity: wishlist

* Package name: updatescanner
  Version : 4.3.0
  Upstream Author : 
* URL : https://github.com/sneakypete81/updatescanner
* License : MPL 2.0
  Programming Lang: javascript
  Description : Firefox addon to monitors web pages for updates.

Monitors web pages for updates. Useful for websites that don't provide Atom or 
RSS feeds.

Bug#903228: RFP: wxif -- View the EXIF/IPTC/XMP data for images.

[Alessandro Barbieri]

Package: wnpp
Severity: wishlist

* Package name: wxif
  Version : 0.2
  Upstream Author : Gian-Carlo Pascutto g...@sjeng.org
* URL : https://github.com/gcp/wxif
* License : MPL 2.0
  Programming Lang: javascript
  Description : View the EXIF/IPTC/XMP data for images.

wxIF is a port of FxIF to WebExtensions. It adds a context menu that allows one 
to view EXIF, IPTC and XMP metadata from images.

Bug#903224: udev: Fails to upgrade

[Michael Biebl]

Control: tags -1 moreinfo unreproducible

Am 08.07.2018 um 00:26 schrieb Kurt Roeckx:
> Package: udev
> Version: 239-5
> Severity: serious
> 
> Hi,
> 
> When upgrading udev, it failed to upgrade, because udev didn't
> want to start. I think there might be some ordering problem.

Unfortunately I can't reproduce your problem. I've just test-upgraded a
buster VM from 238-5 to 239-5 without a problem.
Can you provide instructions how to reproduce the problem?



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



signature.asc
Description: OpenPGP digital signature

Bug#437114: split out tabbar

[David Bremner]

control: retitle -1 replace tabbar.el with elpa-tabbar
control: severity -1 normal
control: notforwarded -1

It seems reasonable to preserve tabbar. It's not super-active, but it
had commits two years ago, and 25k downloads on melpa.

dropping the ten year old forwarded note.

Bug#258096: Urgent qoutation

[JOE DAHER]

Good day, 

I am in a competition to Bid for a Tender that requires the supply of
a number of products that I see your company offers. I would like to
get a quotation for purchase of the following products attached and the 
delivery time because I want you to be my supplier after the Bidding. kindly 
send your offer before 14th of July 2018 




Best regards

_

cid:image001.png@01CADAE5.44BEEE90

Joe daher

Responsable MPR

Equipment Company for Africa- Burkina (SEA-B)

Industrial Zone of Gounghin

Rue FADOUL

Headquarters 01 BP 627

Ouagadougou 01 Burkina Faso

cid:_1_0A8E05780A8E02C4002DC651C1258185(bur): +226 25 34 33 54

cid:_1_0A8E05780A8E02C4002DC651C1258185(mob):+226 70 12 16 36

cid:_1_0A8E0ED00A8E0C64002DC651C1258185:
 

This email is confidential and may also be privileged. If you are not the 
recipient, you are asked to destroy it and to notify us immediately, you must 
not copy or use it for any purpose, or disclose the content to any other 
person. Thank you.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Bug#903227: RFP: python3-gspread -- Google Spreadsheets Python API

[Alessandro Barbieri]

Package: wnpp
Severity: wishlist

* Package name: python3-gspread
  Version : 3.0.1
  Upstream Author : Anton Burnashev
* URL : https://github.com/burnash/gspread
* License : MIT
  Programming Lang: Python
  Description : Google Spreadsheets Python API

Manage your spreadsheets with gspread in Python.

Features:

Google Sheets API v4.
Open a spreadsheet by its title or url.
Extract range, entire row or column values.

Bug#903226: RFP: python3-gplearn -- gplearn implements Genetic Programming in Python, with a scikit-learn inspired and compatible API.

[Alessandro Barbieri]

Package: wnpp
Severity: wishlist

* Package name: python3-gplearn
  Version : 0.3.0
  Upstream Author : Trevor Stephens
* URL : https://gplearn.readthedocs.io
* License : BSD 3 clause
  Programming Lang: Python
  Description : gplearn implements Genetic Programming in Python, with a 
scikit-learn inspired and compatible API.

While Genetic Programming (GP) can be used to perform a very wide variety of 
tasks, gplearn is purposefully constrained to solving symbolic regression 
problems. This is motivated by the scikit-learn ethos, of having powerful 
estimators that are straight-forward to implement.

Symbolic regression is a machine learning technique that aims to identify an 
underlying mathematical expression that best describes a relationship. It 
begins by building a population of naive random formulas to represent a 
relationship between known independent variables and their dependent variable 
targets in order to predict new data. Each successive generation of programs is 
then evolved from the one that came before it by selecting the fittest 
individuals from the population to undergo genetic operations.

gplearn retains the familiar scikit-learn fit/predict API and works with the 
existing scikit-learn pipeline and grid search modules. The package attempts to 
squeeze a lot of functionality into a scikit-learn-style API. While there are a 
lot of parameters to tweak, reading the documentation here should make the more 
relevant ones clear for your problem.

gplearn currently supports regression through the SymbolicRegressor as well as 
transformation for automated feature engineering with the SymbolicTransformer, 
which is designed to support regression problems, but should also work for 
binary classification. Future versions of the package will expand this class to 
support more complicated multi-target classification problems, and much more is 
planned too.

Bug#823790: fixed in mate-applets 1.20.2-1

[Mike Gabriel]

Control: found -1 1.20.2-2
Control: reopen -1

Hi,

On Thu, 05 Jul 2018 13:52:28 + Mike Gabriel  
wrote:

> Source: mate-applets
> Source-Version: 1.20.2-1
>
> We believe that the bug you reported is fixed in the latest version of
> mate-applets, which is due to be installed in the Debian FTP archive.

Provided patch caused an FTBFS. Patch has been unapplied. Reopening this 
bug.


Mike

Bug#901365: inform6-library: Inform6 Library has been updated to 6.12.2

[David Griffith]

On Tue, 12 Jun 2018, Ben Finney wrote:


On 12-Jun-2018, David Griffith wrote:


I updated the Inform6 Standard Library to version 6.12.2.


Thank you. I also saw you announce that the releases will now be
somewhere other than GitHub? What URL should recipients watch for
future source releases?


The Library is now at https://gitlab.com/DavidGriffith/inform6lib


Bugs fixed
--

* Removed last vestiges of modules.


I think I don't understand what this means.


It was a means of pre-compiling pieces of the Library to speed up 
compilation.  It never was particularly helpful.  Now it's pointless 
because even a big program takes so little time to compile.  When the 
Glulx virtual machine was invented, there was no point to adding module 
support to the compiler.



* Backported Glulx 16-bit verb numbers from I7's Parser.i6t


Does the copyright holders in that work (the back-ported ‘Parser.i6t’)
grant recipients exactly the same license as the rest of the Inform 6
library? (I haven't looked, we would need to see the text of the grant
of license.)


Yes.  Those portions of Inform7 are under the Artistic License 2.0.

--
David Griffith
d...@661.org

Bug#903225: freedv FTBFS Cannot find (any matches for) "credits.txt" (tried in .)

[peter green]

Package: freedv
Version: 1.3-1
Severity: serious

freedv failed to build during the binnmu for the libcodec transition.

https://buildd.debian.org/status/package.php?p=freedv&suite=unstable


  dh_installdocs -a -O--builddir=Build -O--build-system=cmake
dh_installdocs: Cannot find (any matches for) "credits.txt" (tried in .)

Bug#901701: bumblebee: using optirun introduces segfault in i965_dri.so

[Vincas Dargis]

Looks like there is much simpler workaround:

PRIMUS_UPLOAD=1 primusrun glxgears

Works for wine too.

Thanks to Reddit user huttukuttu! [0]

[0] 
https://www.reddit.com/r/debian/comments/8wu8t8/bumblebee_causes_segfault_in_i965_driso/e1ywduu

Bug#903200: Source file ‘/usr/share/emacs/site-lisp/w3m/w3m.el’ newer than byte-compiled file

[積丹尼 Dan Jacobson]

I happens on all my computers.

It appears the problem is at

Setting up w3m-el-snapshot (1.4.631+0.20180620-1) ...
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install w3m-el-snapshot for emacs
install/w3m-el-snapshot: already byte-compiled for emacs, skipped

It shouldn't skip the last step.

Yes
TK> apt-get --reinstall install emacsen-common
TK> apt-get --reinstall install w3m-el-snapshot
makes the problem go away. I suppose I will have to do this from now on
every time.

Bug#903025: It is a feature of kernel

[Ryutaroh Matsumoto]

Control: tags -1 + confirmed

It was closed as a GitHub issue at the upstream as:
https://github.com/systemd/systemd/issues/9513#issuecomment-403225211
The reason is "This is a feature of the current Linux kernel".

I am not sure if we should file a report to the kernel package,
or add "upstream", "wontfix" tags to this.

Best regards,
Ryutaroh

Bug#858868: firebird3.0: 3.0.1.32609.ds4-14 FTBFS on hppa

[John David Anglin]

On 2018-06-04 8:13 AM, Damyan Ivanov wrote:

Another way would be to change src/common/os/posix/mod_loader.cpp
around line 120 to dump sought symbol names to stderr and compare that
to the actual symbol name.
I finally got time to look at this problem.  The above suggestion was an 
excellent clue.


The problem is dlsym returns a function pointer on hppa when passed the 
name of a
function symbol.  It points at a function descriptor for the function 
when the plabel bit
is set in the pointer.  The descriptor has an entry which points at the 
function after it
has been bound.  Otherwise, it points at trampoline code to fix up the 
descriptor.


In any case, dladdr doesn't do the expected thing when passed a function 
pointer.  It

needs the actual address of the function.

The attached patch fixes the build on hppa-linux.  Another option would 
be to adjust

the configure check.

Thanks,
Dave

--
John David Anglin  dave.ang...@bell.net

--- ./src/common/os/posix/mod_loader.cpp.save   2018-02-02 06:00:35.0 
-0500
+++ ./src/common/os/posix/mod_loader.cpp2018-07-07 18:13:19.976129060 
-0400
@@ -125,7 +125,7 @@
result = dlsym(module, newSym.c_str());
}
 
-#ifdef HAVE_DLADDR
+#if defined(HAVE_DLADDR) && !defined(__hppa__)
if (!PathUtils::isRelative(fileName))
{
Dl_info info;

Bug#903149: ClipIt crashes with segmentation fault on start

[Dmitry Smirnov]

On Sunday, 8 July 2018 8:10:38 AM AEST Calle Kabo wrote:
> Alright, I installed 1.4.4-2 from unstable, and it still crashes.
> Here's the gdb output

Thank you.

> I'm running Gnome with Wayland, and it seems to be doing some X11 stuff?

Upstream would have to investigate... I've reported as 

  https://github.com/CristianHenzel/ClipIt/issues/96

-- 
Cheers,
 Dmitry Smirnov

---

It is impossible to imagine Goethe or Beethoven being good at billiards
or golf.
-- H. L. Mencken


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

Bug#894476: rcc: please honour SOURCE_DATE_EPOCH (was Re: RCC: provide option to encode EPOCH timestamp)

[Thorsten Glaser]

affects 894476 src:musescore
retitle 894476 rcc: please honour SOURCE_DATE_EPOCH
thanks

Hi *,

I just got bitten by this in an FTBR of src:musescore which I tracked
down to this bug.

On Tue, 3 Apr 2018, Sune Vuorela wrote:

> If S_D_E gets used, rather than the data.xml modified date in the
> source, this will end up using the wrong file if S_D_E is newer than
> the system copy of the file.

AIUI, S_D_E is used as a *delimiter*, not as a timestamp *all* files
are to be set to.

So, basically, instead of

encode(dst, sb.st_mtime);

you do

encode(dst, MIN(sb.st_mtime, s_d_e_as_time_t_value));

and not

encode(dst, s_d_e_as_time_t_value);

which would indeed break things the way you described.


Chris/H01ger, please correct me if I’m wrong, but this is
how I understood S_D_E to work.


I don’t know cmake magic enough to be able to do the same
patch to lrelease et al. as Thomas did, so I unfortunately
will have to live with the FTBR in src:musescore until this
issue is fixed.

Thanks,
//mirabilos
-- 
>> Why don't you use JavaScript? I also don't like enabling JavaScript in
> Because I use lynx as browser.
+1
-- Octavio Alvarez, me and ⡍⠁⠗⠊⠕ (Mario Lang) on debian-devel

Bug#903010: golang-gopkg-inf.v0: No Breaks/Replaces/Conflics with golang-speter-go-exp-math-dec-inf-dev

[Dmitry Smirnov]

On Sunday, 8 July 2018 3:42:07 AM AEST Sascha Steinbiss wrote:
> Oh, I see. Sorry for my completely avoidable oversight... I didn’t think of
> any such problems as my package had passed NEW a year ago without
> problems, and my recent upload didn’t change anything about the actual
> content, only metadata. Looks like I should have done my homework some
> time ago :/

No worries, it is easy to miss other package with Provide and it is not bad 
that you've introduced package compliant with naming convention.
ftp-masters mostly review licensing and other DFSG compliance requirements.
It wouldn't be the first case when we upload the same source with intent to 
rename the package and decommission the old one...

After all we have this situation because upstream moved/renamed the 
project...


> What do you suggest we do now? Should we declare mutual ‘Conflicts’ between
> this package and 'golang-speter-go-exp-math-dec-inf'?

Breaks/Replaces in one package should be enough, if we are going to keep one 
package. Then perhaps we could remove older package?

The following link have all you need:

https://www.debian.org/doc/debian-policy/#packages-which-break-other-packages-breaks

-- 
Cheers,
 Dmitry Smirnov.

---

Lies are the social equivalent of toxic waste: Everyone is potentially
harmed by their spread.
-- Sam Harris


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

Bug#576609: switching to RFP

[David Bremner]

reassign 576609 wnpp
retitle 576609 Please package babel.el as elpa-babel
user debian-emac...@bugs.debian.org
usertag 576609 elpafy
quit

Whoever takes this on should make sure babel.el still works with current
google translate. Those things tend to obsolete fast.

I guess it's also not totally clear to me that clients for specific
proprietary services belong in main.

Bug#903204: ca-certificates: Errors on updating to 20141019+deb8u4

[guidot]

Am 07.07.2018 um 20:23 schrieb Michael Shuler:

Control: tags -1 + moreinfo

On 07/07/2018 10:21 AM, guidot wrote:

I just updated from 20141019+deb8u3 to 20141019+deb8u4 using

   aptitude safe-upgrade

and got these errors:

   Updating certificates in /etc/ssl/certs... unable to load certificate
   140549699909264:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong 
tag:tasn_dec.c:1219:
   140549699909264:error:0D07803A:asn1 encoding 
routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:386:Type=X509
   WARNING: dhparam.pem does not contain a certificate or CRL: skipping
   20 added, 42 removed; done.

I don't understand what went wrong here. I'm pretty sure I didn't touch 
anything in /etc/ssl/certs, my local certs are stored elsewhere.


This appears to be a warning from c_rehash on a non-certificate pem file
`dhparam.pem` found in /etc/ssl/certs, then success on the 20 new and 42
removed CA certificates in this update.

For clarity, did the installation of update packages complete
successfully, or did it exit non-zero with an error from aptitude/dpkg?


Damn, I didn't think of checking that.
 

I'm pretty sure an `ls -l /etc/ssl/certs/dhparam.pem` would indeed
return the file, which is not a part of the ca-certificates package.


Correct.
 

Searching around for dhparam.pem, it appears this is a Diffie-Hellman
option file for using a larger key than the openssl default. I found
quite a few web pages that say to put it there. The warning should be
innocuous, but I'd suggest moving it to a better location. For instance,
I found a number of nginx how-to pages that use the /etc/ssl/certs
location

Michael, you're right, I remember now I once followed some how-to while setting 
up nginx for tls.

Thanks for the clarification.

Regards
Guido

Bug#496128: drop auto-fill-inhibit.el

[David Bremner]

control: severity -1 normal
control: retitle -1 drop auto-fill-inhibit.el

I can't find an upstream for this, so unless someone steps up, we're
going drop it.

Bug#495878: reassigning to dh-elpa

[David Bremner]

control: reassign -1 dh-elpa

This is not a a crazy idea, but since we're winding down
emacs-goodies-el, I'm reassigning it to dh-elpa, where it might do more
good.

d

Bug#891580: camo 2.3.0+dfsg-1.1~deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: camo
Version: 2.3.0+dfsg-1.1~deb9u1

Explanation: add missing dependency on openssl

Bug#903199: sus 7.20180621~deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: sus
Version: 7.20180621~deb9u1

Explanation: update to new version, technically identical to SUSv4 + TC1 + TC2

Bug#903203: clustershell 1.7.3-2~deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: clustershell
Version: 1.7.3-2~deb9u1

Explanation: add missing dependency on python-pkg-resources

Bug#873330: libosmium 2.11.4-1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian .

Thanks for your contribution!

Upload details
==

Package: libosmium
Version: 2.11.4-1

Explanation: output coordinate with value of -2^31 correctly; fix buffers 
larger than 2^32 bytes

Bug#903216: python-pyorick 1.4-2~deb9u1 flagged for acceptance

[Adam D Barratt]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: python-pyorick
Version: 1.4-2~deb9u1

Explanation: fix import failure by adding missing dependency on python3-numpy

Bug#903224: udev: Fails to upgrade

[Kurt Roeckx]

Package: udev
Version: 239-5
Severity: serious

Hi,

When upgrading udev, it failed to upgrade, because udev didn't
want to start. I think there might be some ordering problem.

This is the apt history log:
Start-Date: 2018-07-07  23:51:34
Commandline: apt-get upgrade
Upgrade: libsystemd0:amd64 (238-5, 239-5), udev:amd64 (238-5, 239-5), 
libudev1:amd64 (238-5, 239-5), systemd-sysv:amd64 (238-5, 239-5), 
debootstrap:amd64 (1.0.105, 1.0.106), libpam-systemd:amd64 (238-5, 239-5), 
systemd:amd64 (238-5, 239-5)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2018-07-07  23:53:25

Start-Date: 2018-07-07  23:53:32
Commandline: apt-get -f install
End-Date: 2018-07-07  23:53:58


The term.log:
Log started: 2018-07-07  23:51:34
(Reading database ... 360672 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_239-5_amd64.deb ...
Unpacking systemd-sysv (239-5) over (238-5) ...
Preparing to unpack .../libpam-systemd_239-5_amd64.deb ...
Unpacking libpam-systemd:amd64 (239-5) over (238-5) ...
Preparing to unpack .../libsystemd0_239-5_amd64.deb ...
Unpacking libsystemd0:amd64 (239-5) over (238-5) ...
Setting up libsystemd0:amd64 (239-5) ...
(Reading database ... 360672 files and directories currently installed.)
Preparing to unpack .../systemd_239-5_amd64.deb ...
Unpacking systemd (239-5) over (238-5) ...
Preparing to unpack .../archives/udev_239-5_amd64.deb ...
Unpacking udev (239-5) over (238-5) ...
Preparing to unpack .../libudev1_239-5_amd64.deb ...
Unpacking libudev1:amd64 (239-5) over (238-5) ...
Setting up libudev1:amd64 (239-5) ...
(Reading database ... 360697 files and directories currently installed.)
Preparing to unpack .../debootstrap_1.0.106_all.deb ...
Unpacking debootstrap (1.0.106) over (1.0.105) ...
Processing triggers for libc-bin (2.27-3) ...
Setting up udev (239-5) ...
Job for systemd-udevd.service failed because the control process exited with 
error code.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript udev, action "restart" failed.
• systemd-udevd.service - udev Kernel Device Manager
   Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-07-07 23:52:19 CEST; 10ms 
ago
 Docs: man:systemd-udevd.service(8)
   man:udev(7)
  Process: 21914 ExecStart=/lib/systemd/systemd-udevd (code=exited, status=127)
 Main PID: 21914 (code=exited, status=127)

Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager.
Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager...
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process 
exited, code=exited, status=127/n/a
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 
'exit-code'.
Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager.
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no 
hold-off time, scheduling restart.
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart 
job, restart counter is at 3.
Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager.
Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager...
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process 
exited, code=exited, status=127/n/a
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 
'exit-code'.
Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager.
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no 
hold-off time, scheduling restart.
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart 
job, restart counter is at 4.
Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager.
Jul 07 23:52:19 intrepid systemd[1]: Starting udev Kernel Device Manager...
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Main process 
exited, code=exited, status=127/n/a
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 
'exit-code'.
Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager.
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Service has no 
hold-off time, scheduling restart.
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Scheduled restart 
job, restart counter is at 5.
Jul 07 23:52:19 intrepid systemd[1]: Stopped udev Kernel Device Manager.
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Start request 
repeated too quickly.
Jul 07 23:52:19 intrepid systemd[1]: systemd-udevd.service: Failed with result 
'exit-code'.
Jul 07 23:52:19 intrepid systemd[1]: Failed to start udev Kernel Device Manager.
dpkg: error processing package udev (--configure):
 installed udev package post-installation script subprocess returned error exit 
status 1
Setting up systemd (239-5) ...
Installing new version of c

Bug#903223: libkf5kiocore5: Symlink behavior over SFTP connection broken

[Alex Krusemark]

Package: libkf5kiocore5
Version: 5.47.0-1
Severity: normal

Dear Maintainer,

Since a recent upgrade (I think it was the transition from KDE Frameworks 5.46
to 5.47), on filesystems accessed over an SFTP connection symbolic/soft links
whose target is a directory have broken behavior. Symlinks whose targets are
files still work properly.

Links to directories are shown as a link to a file with an unknown mimetype,
rather than that of a directory, and can neither be double-clicked to follow
nor expanded in tree view. The only way I see to follow them is by right-
clicking and choosing "Show Target" in Dolphin, with no obvious workaround in
other applications. I confirmed that this problem was present in Dolphin,
Krusader, Konqueror, Kate, and Calligra.

Thanks!



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

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

Versions of packages libkf5kiocore5 depends on:
ii  libacl12.2.52-3+b1
ii  libc6  2.27-3
ii  libkf5auth55.47.0-1
ii  libkf5configcore5  5.47.0-1
ii  libkf5coreaddons5  5.47.0-1
ii  libkf5dbusaddons5  5.47.0-1
ii  libkf5i18n55.47.0-1
ii  libkf5service-bin  5.47.0-1
ii  libkf5service5 5.47.0-1
ii  libqt5core5a   5.10.1+dfsg-7
ii  libqt5dbus55.10.1+dfsg-7
ii  libqt5network5 5.10.1+dfsg-7
ii  libqt5xml5 5.10.1+dfsg-7
ii  libstdc++6 8.1.0-9

libkf5kiocore5 recommends no packages.

libkf5kiocore5 suggests no packages.

-- no debconf information

Bug#902787: Add support for JTS 1.15

[Emmanuel Bourg]

Le 07/07/2018 à 23:16, Sebastiaan Couwenberg a écrit :
> Control: severity -1 serious
> 
> jts (1.15.1+ds-1) has been uploaded to unstable.

Hi Sebastiaan, do you think you could provide a patch fixing the reverse
dependencies please?

Emmanuel Bourg

Bug#903222: Syntax error with Python 3.7+

[Paul R. Tagliamonte]

Package: gunicorn
Severity: normal
thanks

While isolating https://bugs.debian.org/903218, I worked out importing
a package named `async` will raise a Syntax error.

I see some imports in the source package such as
`gunicorn.workers.async` that may be broken.

Since it looks like some amount of this package is using Python 3, it
may be worth checking to make sure everything works correctly with
Python 3.7.

Thanks!
  Paul

-- 
:wq

Bug#902385: blacs-pvm-test: depends on removed package blacs-test-common

[Ansgar Burchardt]

Control: clone 902385 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: blacs-pvm -- RoQA; blacs-test-common depends on removed 
package; PVM no longer used for parallel computing
Control: severity -2 normal

Muammar El Khatib writes:
> On Mon, Jun 25, 2018 at 3:00 PM Ansgar Burchardt  wrote:
[...]
>> blacs-pvm-test depends on blacs-test-common which was just removed
>> (#886711).
>>
>> I wonder if blacs-pvm is still useful? pvm was orphaned (#824403) and I
>> don't know anyone still using PVM for parallel computations.
>
> Given that blacs-test-common was removed and honestly PVM does not
> seem to be used for parallel computing, it makes lots of sense to me
> that blacs-pvm should be removed, too.  By the way, I have just seen
> it's been marked as AUTORM and will be removed anyway. Then, no
> actions to take it back into Debian archive might be the right thing
> to do.

The automatic removal is only from testing.  There still needs to be a
manual removal request to remove the package also from unstable; the
beginning of this mail should take care of creating one.

Ansgar

Bug#903149: ClipIt crashes with segmentation fault on start

[Calle Kabo]

Alright, I installed 1.4.4-2 from unstable, and it still crashes.
Here's the gdb output

(gdb) bt
#0  0x76514339 in XGetModifierMapping () at 
/usr/lib/x86_64-linux-gnu/libX11.so.6
#1  0x5556389a in reload_modmap (modmap=0x556142c0, 
keymap=0x5559ed80) at eggaccelerators.c:549
#2  0x5556389a in egg_keymap_get_modmap (keymap=0x5559ed80) at 
eggaccelerators.c:646
#3  0x55563ae0 in egg_keymap_resolve_virtual_modifiers 
(keymap=0x5559ed80, virtual_mods=EGG_VIRTUAL_LOCK_MASK, 
concrete_mods=0x55569114 ) at eggaccelerators.c:475
#4  0xe245 in lookup_ignorable_modifiers (keymap=0x5559ed80) at 
keybinder.c:54
#5  0xe61e in keybinder_init () at keybinder.c:242
#6  0xb34a in clipit_init () at main.c:972
#7  0xb34a in main (argc=, argv=) at 
main.c:1046

I'm running Gnome with Wayland, and it seems to be doing some X11 stuff?

/Calle

Bug#900840: Bug#901471: Thunderbird should not be able to render the xserver unusable

[Erich Schubert]

Hi,

Oops, yes. This should have gone to #900840.


I am unsure where to clone the issue.
For obvious reasons, a client application like thunderbird should not be able to
break the xserver in a way that thunderbird does.
While extending the apparmor permissions makes thunderbird work again (and thus
solves this bug), there is an underlying issue with the xserver most likely.
When I try to use thunderbird with apparmor enabled, the xserver stops drawing 
except
for the mouse cursor; and even killing the thunderbird process does not fix the
xserver. That should be prevented on the xserver side.

Very good point, I wholeheartedly agree.

But I suspect you've followed up on the wrong bug: I can see no
indication that #901471 caused this much trouble. Maybe you're talking
about #900840 or one of its numerous clones? I'm not sure where that
problem should be tracked either. Perhaps you could ask
debia...@lists.debian.org?

FWIW I've not been affected by this bug on GNOME Wayland.

Cheers,

Bug#903047: Netinst image cannot load e1000e, ixgbe, igb eth. drivers

[Cyril Brulebois]

Control: severity -1 normal

Hi,

Clayton Craft  (2018-07-05):
> Package: installation-reports
> Justification: Unable to install debian with netinst image on systems with 
> these NICs
> 
> 
> With the latest weekly Debian testing netinst image (06-25 and 07-02 tested),

Please always include the full URL to the image you're reporting an
issue against.

> the e1000e, ixgbe, and igb modules cannot load.
> Attempting to do so generates this message in the kernel log:
> 
> Unknown symbol: refcount_inc (error 0)
> 
> The kernel on this image is reported as 4.16.0-2, and magic ver from
> 'modinfo' reports the same version. Perhaps there's some other module
> dependency that is not included in the image?

It's rather due to having an installer embedding the kernel at version
4.16.12-1 (current when that installer was built) while the debian-cd
tooling included more recent kernel udebs (4.16.16-2, current when the
installation image was built).

For reference, the exact kernel version can be seen using:

cat /proc/version

> Note that I did not try to load all ethernet drivers included in the
> image, so it's possible that there are more drivers affected.
> 
> This issue makes it impossible to install Debian testing with the
> netinst image on system with these ethernet adapters.

Please use released images instead?

This issue is common during development phases, and I'd usually advise
running either a released image (esp. for this netinst usecase), or a
d-i daily build (esp. for the netboot usecase). Please note the latter
is only a d-i build against unstable, there's no matching installation
image.

See the last announce:
  https://www.debian.org/devel/debian-installer/News/2018/20180619

More on:
  https://www.debian.org/devel/debian-installer/


Awaiting feedback, but this is a good candidate for a not-a-bug closure.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#903220: libconfig-model-dpkg-perl: Please change policy to current version of debian policy in sid

[Andreas Tille]

Package: libconfig-model-dpkg-perl
Severity: wishlist

Hi,

libconfig-model-dpkg-perl is always lagging behind once a new Debian
policy is released when setting Standards-Version field.  I could
imagine that it is possible to set it automatically to a value of the
latest version of debian-policy package and thus there is no need to
upload a new libconfig-model-dpkg-perl once a new Debian Policy is
released.  On a sid system this would mean for instance to

dpkg -l debian-policy | awk '/^ii/{print $3;}'

(or rather by just stripping the the first three values but you probably
want to do this in Perl anyway) or something that is more safe against
running cme on a non-sid system (UDD query, apt-cache policy, whatever -
just to calculate the policy version rather than setting a fixed value)

Kind regards and thanks for working on cme

 Andreas.


-- System Information:
Debian Release: 9.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages libconfig-model-dpkg-perl depends on:
ii  libapt-pkg-perl  0.1.32
pn  libarray-intspan-perl
pn  libconfig-model-perl 
pn  libexporter-lite-perl
pn  liblog-log4perl-perl 
pn  libmouse-perl
pn  libparse-recdescent-perl 
ii  libsoftware-license-perl 0.103012-1
pn  libtext-autoformat-perl  
pn  libtext-levenshtein-damerau-perl 
ii  liburi-perl  1.71-1
ii  libwww-perl  6.15-1
pn  libyaml-perl 
pn  licensecheck 
pn  lintian  
ii  perl 5.24.1-3+deb9u4
ii  perl-modules-5.24 [libmodule-corelist-perl]  5.24.1-3+deb9u4

Versions of packages libconfig-model-dpkg-perl recommends:
pn  libconfig-model-tkui-perl  

libconfig-model-dpkg-perl suggests no packages.

Bug#903219: journald crashes

[Yuri D'Elia]

Package: systemd
Version: 239-5
Severity: important

I noticed journald dumped core several times on this system.

Unfortunately, I didn't notice earlier as these are obviously not logged
on the journal and coredumpctl fails to report them. Nice.

[ 6840.048179] systemd-coredump[7546]: MESSAGE=Process 418 (systemd-journal) of 
user 0 dumped core.
[ 6840.048185] systemd-coredump[7546]: Coredump diverted to 
/var/lib/systemd/coredump/core.systemd-journal.0.e13febf27eb6481eb4b017aeba831de4.418.153099854700.lz4
[ 6840.048188] systemd-coredump[7546]: Stack trace of thread 418:
[ 6840.048190] systemd-coredump[7546]: #0  0x7f1e5b58a420 n/a 
(libsystemd-shared-239.so)
[ 6840.048193] systemd-coredump[7546]: #1  0x7f1e5b58bb42 
internal_hashmap_iterate (libsystemd-shared-239.so)
[ 6840.048195] systemd-coredump[7546]: #2  0x558f32563812 n/a 
(systemd-journald)
[ 6840.048197] systemd-coredump[7546]: #3  0x7f1e5b74aa87 __libc_start_main 
(libc.so.6)
[ 6840.048199] systemd-coredump[7546]: #4  0x558f32565a7a n/a 
(systemd-journald)`

backtrace:

[New LWP 418]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/lib/systemd/systemd-journald'.
Program terminated with signal SIGABRT, Aborted.
#0  storage_ptr () at ../src/basic/hashmap.c:326
#1  bucket_at () at ../src/basic/hashmap.c:374
#2  ordered_bucket_at () at ../src/basic/hashmap.c:382
#3  hashmap_iterate_in_insertion_order (i=0x7fff2163f530, h=0x558f33fc7078) at 
../src/basic/hashmap.c:589
#4  hashmap_iterate_entry (h=h@entry=0x558f33fc7078, i=0x7fff2163f530) at 
../src/basic/hashmap.c:703
#5  0x7f1e5b58bb42 in internal_hashmap_iterate (h=, i=, 
value=, key=, key=,
   value=) at ../src/basic/hashmap.c:711
#6  0x558f32563812 in ordered_hashmap_iterate () at 
../src/basic/hashmap.h:259
#7  server_maybe_append_tags (s=0x7fff2163f5d0) at 
../src/journal/journald-server.c:1891
#8  main (argc=, argv=) at 
../src/journal/journald.c:98

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.117
ii  libacl1  2.2.52-3+b1
ii  libapparmor1 2.12-4+b1
ii  libaudit11:2.8.3-1+b1
ii  libblkid12.32-0.1
ii  libc62.27-3
ii  libcap2  1:2.25-1.2
ii  libcryptsetup12  2:2.0.3-5
ii  libgcrypt20  1.8.3-1
ii  libgnutls30  3.5.18-1
ii  libgpg-error01.31-1
ii  libidn11 1.33-2.2
ii  libip4tc01.6.2-1
ii  libkmod2 25-1
ii  liblz4-1 1.8.2-1
ii  liblzma5 5.2.2-1.3
ii  libmount12.32-0.1
ii  libpam0g 1.1.8-3.7
ii  libseccomp2  2.3.3-3
ii  libselinux1  2.8-1+b1
ii  libsystemd0  239-5
ii  mount2.32-0.1
ii  procps   2:3.3.15-2
ii  util-linux   2.32-0.1

Versions of packages systemd recommends:
ii  dbus1.12.8-3
ii  libpam-systemd  239-5

Versions of packages systemd suggests:
ii  policykit-10.105-20
ii  systemd-container  239-5

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 239-5

-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
Storage=persistent
MaxRetentionSec=3month
MaxFileSec=1week

/etc/systemd/logind.conf changed:
[Login]
KillUserProcesses=no

Bug#903200: Source file ‘/usr/share/emacs/site-lisp/w3m/w3m.el’ newer than byte-compiled file

[Tatsuya Kinoshita]

On July 7, 2018 at 10:05PM +0800, jidanni (at jidanni.org) wrote:
> Package: w3m-el-snapshot
> Version: 1.4.631+0.20180620-1
> 
> See lots of these
> Source file ‘/usr/share/emacs/site-lisp/w3m/w3m.el’ newer than byte-compiled 
> file
> Source file ‘/usr/share/emacs/site-lisp/w3m/w3m-util.el’ newer than 
> byte-compiled file
> Source file ‘/usr/share/emacs/site-lisp/w3m/w3m-proc.el’ newer than 
> byte-compiled file

It seems your emacsen-common installation is broken, so the
byte-compilation doesn't work.

To repair your system, reinstall the emacsen-common package.

apt-get --reinstall install emacsen-common

And then reinstall the add-on packages to byte-compile.

apt-get --reinstall install w3m-el-snapshot

Thanks,
-- 
Tatsuya Kinoshita

Bug#903138: Unmet dependencies

[Sebastian Ramacher]

On 2018-07-07 11:17:01, Jörg Frings-Fürst wrote:
> reassign 903138 libplacebo 0.5.0-2
> tags 903138 - moreinfo
> tags 903138 - unreproducible
> affects 903138 + vcl
> thanks
> 
> Hi,
> 
> Am Samstag, den 07.07.2018, 00:10 +0200 schrieb Sebastian Ramacher:
> > Control: tags -1 + moreinfo unreproducible
> > 
> > On 2018-07-06 23:34:58, Jörg Frings-Fürst wrote:
> > > Package: src:vlc
> > > Version: 3.0.3-1+b1
> > > Severity: grave
> > > 
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA512
> > > 
> > > Hello,
> > > 
> > > on apt-get upgrade I get
> > > 
> > > 
> > > Reading package lists... Done
> > > Building dependency tree
> > > Reading state information... Done
> > > Calculating upgrade... 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:
> > >  vlc-bin : Depends: libvlc-bin (= 3.0.3-1+b1) but 3.0.3-2 is to be
> > > installed
> > >  vlc-plugin-base : Depends: vlc-data (= 3.0.3-1) but 3.0.3-2 is to
> > > be installed
> > >  vlc-plugin-skins2 : Depends: vlc-plugin-qt (= 3.0.3-2) but 3.0.3-
> > > 1+b1 is to be
> > > installed
> > > E: Broken packages
> > 
> > I cannot reproduce this issue. vlc installs fine. Do you have any
> > held packages
> > or something pinned so that libplacebo5 cannot be installed? That's
> > the only
> > real change from 3.0.3-1+b1 to 3.0.3-2.
> > 
> [...]
> 
> I have search for the reason and found that libplacebo has bump the
> SOName from 4 to 5 without transition. 

What do you mean with that? The transition was competed by vlc 3.0.3-2 being
built against libplacebo5.

Cheers

> 
> 
> So I reassign this bug to libplacebo.
> 
> 
> CU
> Jörg
> 
> -- 
> New:
> GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
> GPG key (long) : 09F89F3C8CA1D25D
> GPG Key: 8CA1D25D
> CAcert Key S/N : 0E:D4:56
> 
> Old pgp Key: BE581B6E (revoked since 2014-12-31).
> 
> Jörg Frings-Fürst
> D-54470 Lieser
> 
> 
> git:  https://jff.email/cgit/
> 
> Threema:  SYR8SJXB
> Wire: @joergfringsfuerst
> Skype:joergpenguin
> Ring: jff
> Telegram: @joergfringsfuerst
> 
> 
> My wish list: 
>  - Please send me a picture from the nature at your home.

-- 
Sebastian Ramacher

Bug#902787: Add support for JTS 1.15

[Sebastiaan Couwenberg]

Control: severity -1 serious

On 06/30/2018 11:30 PM, Bas Couwenberg wrote:
> The severity of this issue will be raised when the jts package is moved
> from experimental to unstable.

jts (1.15.1+ds-1) has been uploaded to unstable.

Kind Regards,

Bas

Bug#903218: Presents itself with Python 3.7

[Paul R. Tagliamonte]

With Python 2.6:

```
paultag@nyx:~/dev/local$ python3.6
Python 3.6.6 (default, Jun 27 2018, 14:44:17)
[GCC 8.1.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import foo.async
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'foo'
>>>
```

With Python 3.7:

```
paultag@nyx:~/dev/local$ python3.7
Python 3.7.0 (default, Jun 27 2018, 14:40:03)
[GCC 8.1.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import foo.async
  File "", line 1
import foo.async
   ^
SyntaxError: invalid syntax
>>>
```

   Paul

-- 
:wq

Bug#903218: Fails to install due to SyntaxError

[Paul R. Tagliamonte]

Package: python3-opengl
Severity: serious
thanks

```
Setting up python3-opengl (3.1.0+dfsg-1) ...
  File "/usr/lib/python3/dist-packages/OpenGL/GL/SGIX/async.py", line 58
from OpenGL.raw.GL.SGIX.async import *
^
SyntaxError: invalid syntax
```

This is serious because it's preventing install:

```
$ sudo apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
sh: 0: getcwd() failed: No such file or directory
sh: 0: getcwd() failed: No such file or directory
sh: 0: getcwd() failed: No such file or directory
Setting up python3-opengl (3.1.0+dfsg-1) ...
  File "/usr/lib/python3/dist-packages/OpenGL/GL/SGIX/async.py", line 58
from OpenGL.raw.GL.SGIX.async import *
^
SyntaxError: invalid syntax

dpkg: error processing package python3-opengl (--configure):
 installed python3-opengl package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 python3-opengl
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

I think new Python 3 (3.6.6) is trying to parse that as the `async`
keyword. I have no idea why, since I can't seem to make Python
trivially emit the syntax error rather than a module import error.

   Paul

-- 
:wq

Bug#903217: backuppc: Web interface status page doesn't show graphs

[Dominique Brazziel]

Package: backuppc
Version: 3.3.1-5
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
Select status page
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
No graphs shown, images broken
   * What outcome did you expect instead?
Graph images
*** End of the template - remove these template lines ***

Patch to fix:

--- /usr/share/backuppc/lib/BackupPC/CGI/GeneralInfo.pm.orig2016-09-06
04:04:33.466484120 -0400
+++ /usr/share/backuppc/lib/BackupPC/CGI/GeneralInfo.pm 2016-09-06
04:05:34.271384202 -0400
@@ -47,8 +47,11 @@
 if ($In{image} ne "") {
$In{image} =~ /([0-9]+)/;
my $weeks = $1;
+my $real = $<;  ### SUID
+$< = $>;### SUID
print "Content-type: image/png\n\n";
print `/usr/bin/rrdtool graph - --imgformat=PNG --start=end-${weeks}w
--end=-300 --title="BackupPC Pool Size (${weeks} weeks)" --base=1000
--height=100 --width=600 --alt-autoscale-max --lower-limit=0 --vertical-
label="" --slope-mode --font TITLE:10:Times --font AXIS:8:Times --font
LEGEND:8:Times --font UNIT:8:Times -c BACK#FF
DEF:ao="$LogDir/pool.rrd":ckb:AVERAGE CDEF:a=ao,1024,* AREA:a#95B8DB:"CPool in
bytes"  GPRINT:a:LAST:"Current\\:%8.2lf %s" GPRINT:a:AVERAGE:"Average\\:%8.2lf
%s" GPRINT:a:MAX:"Maximum\\:%8.2lf %s\\n"`;
+$< = $real;   ### SUID
return;
 }

That was per: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1612600


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

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

Versions of packages backuppc depends on:
ii  adduser3.117
ii  apache2 [httpd]2.4.33-3+b1
ii  apache2-utils  2.4.33-3+b1
ii  bzip2  1.0.6-8.1
ii  debconf [debconf-2.0]  1.5.67
ii  dpkg   1.19.0.5+b1
ii  exim4-daemon-light [mail-transport-agent]  4.91-5
ii  iputils-ping   3:20161105-1
ii  libarchive-zip-perl1.60-1
ii  libc6  2.27-3
ii  libcgi-pm-perl 4.38-1
pn  libdigest-md5-perl 
ii  libtime-parsedate-perl 2015.103-2
ii  libwww-perl6.34-1
ii  lsb-base   9.20170808
ii  perl [libio-compress-perl] 5.26.2-6
ii  samba-common-bin   2:4.8.2+dfsg-2
ii  smbclient  2:4.8.2+dfsg-2
ii  tar1.30+dfsg-2
ii  ucf3.0038

Versions of packages backuppc recommends:
ii  libfile-rsyncp-perl  0.74-2.1+b4
ii  libio-dirent-perl0.05-1+b6
ii  openssh-client [ssh-client]  1:7.7p1-2
ii  rrdtool  1.7.0-1+b2
ii  rsync3.1.2-2.1

Versions of packages backuppc suggests:
ii  chromium [www-browser] 67.0.3396.87-1
ii  firefox-esr [www-browser]  52.9.0esr-1
ii  hv3 [www-browser]  3.0~fossil20110109-6
pn  par2   
ii  w3m [www-browser]  0.5.3-36+b1

-- Configuration Files:
/etc/backuppc/hosts [Errno 13] Permission denied: '/etc/backuppc/hosts'
/etc/backuppc/localhost.pl [Errno 13] Permission denied:
'/etc/backuppc/localhost.pl'
/etc/default/backuppc changed:
NICE=0
IONICE=idle



-- debconf information:
  backuppc/restart-webserver: true

Bug#868170: libemail-address-perl: Email::Address->parse() is vulnerable to CVE-2015-7686

[Pali Rohár]

Hi! Here is update summary.

Currently there are only six open blocked bugs and their state is:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887547 - libperl-critic-perl
Fixed in git and is awaiting for an upload.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887548 - 
libregexp-common-email-address-perl
Module just exports problematic regex and therefore needs to be removed
together with Email::Address. The only one reverse dependency is duck.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887543 - libemail-find-perl
Module has not been updated since 2007. So it is questionable if it ever
going to be fixed. Reverse dependences are: cil, libhtml-fromtext-perl,
libtemplate-plugin-clickable-email-perl.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887538 - 
libdata-validate-email-perl
Patch for that module is attached in the bug tracker. As upstream does
not have any git repository nor way for creating a pull requests,
somebody need to try contacting upstream and sending them prepared
patch.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887542 - 
libemail-address-list-perl
Module exports similar set of regexes as Email::Address and depends on
Email::Address. So it is not easy to fix it. But Email::Address::XS
provides functionality offered by Email::Address::List and the only
reverse dependency is request-tracker4. So it should be removed together
with Email::Address.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887551 - request-tracker4
Last update is from April that upstream is going to look at this problem
for 4.6 cycle.

So for two packages from six are patches available, just needs to be
send to upstream. Are you as Debian downstream maintainers handle those
two Data::Validate::Email and Perl::Critic modules and try to find
contact of upstream projects?

About request-tracker4 can you try to check what is current state?

And about remaining, should I fill a bug for duck, cil,
libhtml-fromtext-perl and libtemplate-plugin-clickable-email-perl
packages? Or do you have a better idea how to handle
libregexp-common-email-address-perl and libemail-find-perl?

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: PGP signature

Bug#901471: Thunderbird should not be able to render the xserver unusable

[intrigeri]

Hi Eric,

Erich Schubert:
> I am unsure where to clone the issue.

> For obvious reasons, a client application like thunderbird should not be able 
> to
> break the xserver in a way that thunderbird does.

> While extending the apparmor permissions makes thunderbird work again (and 
> thus
> solves this bug), there is an underlying issue with the xserver most likely.

> When I try to use thunderbird with apparmor enabled, the xserver stops 
> drawing except
> for the mouse cursor; and even killing the thunderbird process does not fix 
> the
> xserver. That should be prevented on the xserver side.

Very good point, I wholeheartedly agree.

But I suspect you've followed up on the wrong bug: I can see no
indication that #901471 caused this much trouble. Maybe you're talking
about #900840 or one of its numerous clones? I'm not sure where that
problem should be tracked either. Perhaps you could ask
debia...@lists.debian.org?

FWIW I've not been affected by this bug on GNOME Wayland.

Cheers,
-- 
intrigeri

Bug#901471: thunderbird: AppArmor denies access to ~/.cache/mesa_shader_cache/index after recent Mesa update

[intrigeri]

Vincas Dargis:
> I am proposing new abstraction for Mesa libraries:
> https://gitlab.com/apparmor/apparmor/merge_requests/137

> Once it's in, I'll backport needed changes to Thunderbird profile.

Vincas did that, then I've reviewed'n'merged that upstream and pushed
to Vcs-Git.

Bug#883584: closed by intrigeri (Bug#883584: fixed in apparmor 2.13-1)

[intrigeri]

Control: notfixed -1 2.13-1
Control: found -1 2.13-1
Control: found -1 2.13-2
Control: tag -1 - upstream

I got it wrong. Tentatively fixed on the debian/experimental branch,
will test before uploading 2.13-3 (probably to sid and probably
during DebCamp).

Bug#900882: susv4: fails to install: ERROR 404: Not Found.

[Andreas Beckmann]

Followup-For: Bug #900882
Control: tag -1 pending

stretch-pu request: https://bugs.debian.org/903199


Andreas

Bug#896329: python-pyorick: pyorick fails to import

[Andreas Beckmann]

Followup-For: Bug #896329
Control: tag -1 pending

stretch-pu request: https://bugs.debian.org/903216


Andreas

Bug#903216: stretch-pu: package python-pyorick/1.4-2~deb9u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Let's fix the missing numpy dependencies in stretch, too.
#896329, #896237

This is a rebuild of the package from sid with all metadata changes.


Andreas
diff -Nru python-pyorick-1.4/debian/changelog 
python-pyorick-1.4/debian/changelog
--- python-pyorick-1.4/debian/changelog 2015-05-19 14:22:22.0 +0200
+++ python-pyorick-1.4/debian/changelog 2018-07-07 21:07:45.0 +0200
@@ -1,3 +1,20 @@
+python-pyorick (1.4-2~deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann   Sat, 07 Jul 2018 21:07:45 +0200
+
+python-pyorick (1.4-2) unstable; urgency=low
+
+  * Bug fix: "pyorick fails to import", thanks to Helmut Grohne (Closes:
+#896329, #896237).
+  * Check against policy 4.1.4 (change priority from extra to optional,
+use https for Format field of copyright file).
+  * Update VCS* fields to salsa.
+
+ -- Thibaut Paumard   Wed, 09 May 2018 13:59:37 +0200
+
 python-pyorick (1.4-1) unstable; urgency=low
 
   * Initial revision (Closes: 785604)
diff -Nru python-pyorick-1.4/debian/control python-pyorick-1.4/debian/control
--- python-pyorick-1.4/debian/control   2015-05-19 15:55:09.0 +0200
+++ python-pyorick-1.4/debian/control   2018-05-09 13:57:28.0 +0200
@@ -1,6 +1,6 @@
 Source: python-pyorick
 Section: python
-Priority: extra
+Priority: optional
 Maintainer: Debian Science Maintainers 

 Uploaders: Thibaut Paumard 
 Build-Depends: debhelper (>= 9~), dh-python, python-all (>= 2.6.6-3~),
@@ -8,14 +8,15 @@
   python-numpy, python3-numpy, yorick (>=2.2.04+dfsg-2~)
 X-Python-Version: >= 2.6
 X-Python3-Version: >= 3.2
-Standards-Version: 3.9.6
-Vcs-Git: git://anonscm.debian.org/debian-science/packages/python-pyorick.git
-Vcs-Browser: 
http://anonscm.debian.org/gitweb/?p=debian-science/packages/python-pyorick.git
+Standards-Version: 4.1.4
+Vcs-Browser: https://salsa.debian.org/science-team/python-pyorick
+Vcs-Git: https://salsa.debian.org/science-team/python-pyorick.git
 Homepage: https://github.com/dhmunro/pyorick/
 
 Package: python-pyorick
 Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, yorick (>=2.2.04+dfsg-2~)
+Depends: ${python:Depends}, ${misc:Depends}, yorick (>=2.2.04+dfsg-2~),
+python-numpy
 Suggests: python3-pyorick
 Description: Python 2 module to execute Yorick code
  The pyorick package starts Yorick as a subprocess and provides an
@@ -36,7 +37,8 @@
 
 Package: python3-pyorick
 Architecture: all
-Depends: ${python3:Depends}, ${misc:Depends}, yorick (>=2.2.04+dfsg-2~)
+Depends: ${python3:Depends}, ${misc:Depends}, yorick (>=2.2.04+dfsg-2~),
+python3-numpy
 Suggests: python-pyorick
 Description: Python 3 module to execute Yorick code
  The pyorick package starts Yorick as a subprocess and provides an
diff -Nru python-pyorick-1.4/debian/copyright 
python-pyorick-1.4/debian/copyright
--- python-pyorick-1.4/debian/copyright 2015-05-19 15:14:19.0 +0200
+++ python-pyorick-1.4/debian/copyright 2018-05-09 13:51:01.0 +0200
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: pyorick
 Upstream-Contact: David Munro 
 Source: https://pypi.python.org/pypi/pyorick/

Bug#903215: openfortivpn: Please remove the stale Uploaders entry

[Adrian Bunk]

Source: openfortivpn
Version: 1.7.1-1
Severity: minor

Orphaing a package means that none of the old
maintainers/uploaders is still active.

Please remove the stale Uploaders entry.

Bug#903212: [Pkg-alsa-devel] Bug#903212: alsa-utils: speaker-test catches SIGINT and can't be interrupted

[Elimar Riesebieter]

* Mikulas Patocka  [2018-07-07 19:46 +0200]:

> Package: alsa-utils
> Version: 1.1.3-1
> Severity: normal
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Run speaker-test (for example "speaker-test -c 2 -t sine -f 200 -s 2")
> Press Ctrl-c
> 
>* What was the outcome of this action?
> 
> The speaker-test program catches the SIGINT signal and ignores it.
> It can't be interrupted.
> 
>* What outcome did you expect instead?
> 
> The speaker-test program should be interruptible.
> 
> It is possible that the speaker-test program creates sounds that are
> unpleasant or painful and there should be possibility to interrupt it.

Version: 1.1.6-1 works as expected.

Elimar
-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)

Bug#902123: finish-install: `update-initramfs -u` needs proc(5) and sysfs(5) resp. mounted to /proc and /sys for the cryptsetup hook

[Guilhem Moulin]

On Fri, 22 Jun 2018 at 17:40:34 +0200, Guilhem Moulin wrote:
> This was not the only thing need to fix the cryptsetup initramfs
> There was also an issue with our hook script; I pushed a fix but it's
> not released yet.

The fix is in cryptsetup-initramfs ≥2:2.0.3-4 though.  Just so you know :-)

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#903214: Dutch translation has been improved

[Maarten]

Package: unattended-upgrades
Version: 1.2
Severity: minor
Tags: patch, l10n

Dear Maintainers


The Dutch translation for the unattended-upgrades package has been
improved. It has been made to apply to version 1.2 of your package.
However, it applies to version 1.4 too.

The improved translation has been reviewed within the Dutch
translation team. Please use the new translation for the next version
of your package.


With kind regards

Maarten
Member of the Dutch translation team of Debian


nl.po.gz
Description: application/gzip

Bug#896305: python-laditools: laditools fails to import

[Andreas Beckmann]

Followup-For: Bug #896305
Control: found -1 1.1.0-3

Hi,

the python-xdg dependency should be rather on python-laditools, not
laditools itself, since the python module uses xdg:

$ python -c 'import laditools'
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/laditools/__init__.py", line 25, in 

from .config import LadiConfiguration
  File "/usr/lib/python2.7/dist-packages/laditools/config.py", line 22, in 

from xdg import BaseDirectory as basedir
ImportError: No module named xdg


Andreas

Bug#903213: datalad: FTBFS in stretch/buster/sid

[Santiago Vila]

Package: src:datalad
Version: 0.4.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in stretch + security + stretch-proposed-updates
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2 --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
pybuild --configure --test-nose -i python{version} -p 2.7
I: pybuild base:184: python2.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
pybuild --build --test-nose -i python{version} -p 2.7
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_2.7/build/datalad

[... snipped ...]

  File 
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_annexrepo.py",
 line 247, in test_AnnexRepo_is_under_annex
assert_equal(ar.is_under_annex(testfiles, batch=batch), target_value)
AssertionError: Lists differ: [False, False, False] != [True, False, False]

First differing element 0:
False
True

- [False, False, False]
+ [True, False, False]

==
FAIL: datalad.support.tests.test_gitrepo.test_GitRepo_get_toppath
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 706, in newfunc
t(*(arg + (uri,)), **kw)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 536, in newfunc
return t(*(arg + (filename,)), **kw)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_gitrepo.py",
 line 637, in test_GitRepo_get_toppath
eq_(GitRepo.get_toppath(repo, follow_up=False), reporeal)
AssertionError: '/tmp/datalad_temp_testrepo_bh4Q3X' != 
'/tmp/datalad_temp_testrepo_bh4Q3X/sub dataset1/subm 1'

==
FAIL: datalad.support.tests.test_gitrepo.test_submodule_deinit
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/<>/.pybuild/pythonX.Y_2.7/build/datalad/tests/utils.py", 
line 706, in newfunc
t(*(arg + (uri,)), **kw)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/datalad/support/tests/test_gitrepo.py",
 line 840, in test_submodule_deinit
eq_(['subm 1', 'subm 2'], [s.name for s in top_repo.get_submodules()])
AssertionError: ['subm 1', 'subm 2'] != []

--
Ran 616 tests in 167.088s

FAILED (SKIP=65, errors=63, failures=15)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose -s -v datalad
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 --test-nose 
returned exit code 13
debian/rules:27: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:19: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends in my autobuilder with dpkg-buildpackage -A,
but there are full build logs available here:

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

A diff between the previous successful build log and this (failed) one
yields this result:

-Get:63 http://deb.debian.org/debian-security stretch/updates/main amd64 
git-annex amd64 6.20170101-1+deb9u1 [10.9 MB]
+Get:63 http://deb.debian.org/debian stretch-proposed-updates/main amd64 
git-annex amd64 6.20170101-1+deb9u2 [10.9 MB]

so it seems git-annex now behaves in a way which breaks the tests.

(X-Debian-CC to Sean Whitton, who did the proposed-updates upload, in case he 
has any hint
about the reason for this FTBFS in datalad).

Thanks.

Bug#903204: ca-certificates: Errors on updating to 20141019+deb8u4

[Kurt Roeckx]

On Sat, Jul 07, 2018 at 01:23:39PM -0500, Michael Shuler wrote:
> Control: tags -1 + moreinfo
> 
> On 07/07/2018 10:21 AM, guidot wrote:
> > I just updated from 20141019+deb8u3 to 20141019+deb8u4 using
> > 
> >   aptitude safe-upgrade
> > 
> > and got these errors:
> > 
> >   Updating certificates in /etc/ssl/certs... unable to load certificate
> >   140549699909264:error:0D0680A8:asn1 encoding 
> > routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1219:
> >   140549699909264:error:0D07803A:asn1 encoding 
> > routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:386:Type=X509
> >   WARNING: dhparam.pem does not contain a certificate or CRL: skipping
> >   20 added, 42 removed; done.
> > 
> > I don't understand what went wrong here. I'm pretty sure I didn't touch 
> > anything in /etc/ssl/certs, my local certs are stored elsewhere.
> 
> This appears to be a warning from c_rehash on a non-certificate pem file
> `dhparam.pem` found in /etc/ssl/certs, then success on the 20 new and 42
> removed CA certificates in this update.
> 
> For clarity, did the installation of update packages complete
> successfully, or did it exit non-zero with an error from aptitude/dpkg?
> 
> I'm pretty sure an `ls -l /etc/ssl/certs/dhparam.pem` would indeed
> return the file, which is not a part of the ca-certificates package.
> 
> Searching around for dhparam.pem, it appears this is a Diffie-Hellman
> option file for using a larger key than the openssl default.

OpenSSL really doesn't have default parameters. The default size
that dhparam used in the past might now be too small, but it would
still be parameters someone created.

> I found
> quite a few web pages that say to put it there. The warning should be
> innocuous, but I'd suggest moving it to a better location. For instance,
> I found a number of nginx how-to pages that use the /etc/ssl/certs
> location, but I would think it should be appropriate to put the file at
> `/etc/nginx/ssl/dhparam.pem` and configure nginx to find it there.

/etc/ssl/certs/ really isn't the place to put such files, it
really should only contain certificates.

But it only generated a warning on it as far as I can see, so this
does not seem related to to the errors some people are seeing.


Kurt

Bug#903204: ca-certificates: Errors on updating to 20141019+deb8u4

[Michael Shuler]

Control: tags -1 + moreinfo

On 07/07/2018 10:21 AM, guidot wrote:
> I just updated from 20141019+deb8u3 to 20141019+deb8u4 using
> 
>   aptitude safe-upgrade
> 
> and got these errors:
> 
>   Updating certificates in /etc/ssl/certs... unable to load certificate
>   140549699909264:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong 
> tag:tasn_dec.c:1219:
>   140549699909264:error:0D07803A:asn1 encoding 
> routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:386:Type=X509
>   WARNING: dhparam.pem does not contain a certificate or CRL: skipping
>   20 added, 42 removed; done.
> 
> I don't understand what went wrong here. I'm pretty sure I didn't touch 
> anything in /etc/ssl/certs, my local certs are stored elsewhere.

This appears to be a warning from c_rehash on a non-certificate pem file
`dhparam.pem` found in /etc/ssl/certs, then success on the 20 new and 42
removed CA certificates in this update.

For clarity, did the installation of update packages complete
successfully, or did it exit non-zero with an error from aptitude/dpkg?

I'm pretty sure an `ls -l /etc/ssl/certs/dhparam.pem` would indeed
return the file, which is not a part of the ca-certificates package.

Searching around for dhparam.pem, it appears this is a Diffie-Hellman
option file for using a larger key than the openssl default. I found
quite a few web pages that say to put it there. The warning should be
innocuous, but I'd suggest moving it to a better location. For instance,
I found a number of nginx how-to pages that use the /etc/ssl/certs
location, but I would think it should be appropriate to put the file at
`/etc/nginx/ssl/dhparam.pem` and configure nginx to find it there.

Setting bug to moreinfo.

-- 
Kind regards,
Michael

Bug#882943: [pkg-php-pear] Bug#882943: php-guzzlehttp-psr7 FTBFS with phpunit 6.4.4-2

[David Prévot]

Hi,

Le 07/07/2018 à 02:34, Thorsten Glaser a écrit :

> are you planning to do anything with it? We’d NMU if needed,
> perhaps if this is not fixed in a week or so?

Please, feel free to take it over.

Regards

David





signature.asc
Description: OpenPGP digital signature

Bug#902851: libc-bin: ldd stopped working with 32-bit binaries on amd64 machine

[Florian Weimer]

* Alexandra N. Kossovsky:

> Please close this bug.  I definitely saw the issue yesterday, but it has 
> somehow gone today.  I'll return to you if I see it again and understand 
> what triggers it.

The related Fedora bug

  https://bugzilla.redhat.com/show_bug.cgi?id=1596312

appears to have been a kernel regression (unconditional exit status
zero from 32-bit processes, or something like that).

Bug#903165: squid: When squid.service starts no /etc/resolv.conf is present yet

[Nuno Paquete]

Please unsubscribe me, I'm not getting success.
Thanks.

A sábado, 7 de jul de 2018, 12:33, Cesare Leonardi 
escreveu:

> Package: squid
> Version: 4.1-1
> Severity: normal
>
> For testing purposes I use squid proxy on my laptop.
> Since upgrading to 4.1, when the system boots, squid service is not
> operating properly: it always fails to resolve DNS names. And I have to
> restart the service in order to make it work.
> Here is the output of "journalctl -u squid.service", that reveals the
> culprit:
> ---
> lug 07 12:53:13 etna systemd[1]: Starting Squid Web Proxy Server...
> lug 07 12:53:13 etna squid[698]: setsid failed: (1) Operation not permitted
> lug 07 12:53:13 etna squid[698]: 2018/07/07 12:53:13| Created PID file
> (/var/run/squid.pid)
> lug 07 12:53:13 etna squid[698]: Squid Parent: will start 1 kids
> lug 07 12:53:13 etna squid[698]: Squid Parent: (squid-1) process 751
> started
> lug 07 12:53:13 etna squid[698]: 2018/07/07 12:53:13 kid1| Set Current
> Directory to /var/spool/squid
> lug 07 12:53:13 etna squid[698]: 2018/07/07 12:53:13 kid1| Creating
> missing swap directories
> lug 07 12:53:13 etna squid[698]: 2018/07/07 12:53:13 kid1| No cache_dir
> stores are configured.
> lug 07 12:53:13 etna squid[698]: Squid Parent: squid-1 process 751 exited
> with status 0
> lug 07 12:53:13 etna squid[698]: 2018/07/07 12:53:13| Removing PID file
> (/var/run/squid.pid)
> lug 07 12:53:13 etna squid[796]: Created PID file (/var/run/squid.pid)
> lug 07 12:53:13 etna squid[796]: Squid Parent: will start 1 kids
> lug 07 12:53:13 etna squid[796]: Squid Parent: (squid-1) process 801
> started
> lug 07 12:53:13 etna systemd[1]: Started Squid Web Proxy Server.
> lug 07 12:53:13 etna squid[801]: Set Current Directory to /var/spool/squid
> lug 07 12:53:13 etna squid[801]: Starting Squid Cache version 4.1 for
> x86_64-pc-linux-gnu...
> lug 07 12:53:13 etna squid[801]: Service Name: squid
> lug 07 12:53:13 etna squid[801]: Process ID 801
> lug 07 12:53:13 etna squid[801]: Process Roles: worker
> lug 07 12:53:13 etna squid[801]: With 1024 file descriptors available
> lug 07 12:53:13 etna squid[801]: Initializing IP Cache...
> lug 07 12:53:13 etna squid[801]: DNS Socket created at [::], FD 5
> lug 07 12:53:13 etna squid[801]: DNS Socket created at 0.0.0.0, FD 9
> lug 07 12:53:13 etna squid[801]: /etc/resolv.conf: (2) No such file or
> directory
> lug 07 12:53:13 etna squid[801]: Warning: Could not find any nameservers.
> Trying to use localhost
> lug 07 12:53:13 etna squid[801]: Please check your /etc/resolv.conf file
> lug 07 12:53:13 etna squid[801]: or use the 'dns_nameservers' option in
> squid.conf.
> lug 07 12:53:13 etna squid[801]: Logfile: opening log
> daemon:/var/log/squid/access.log
> lug 07 12:53:13 etna squid[801]: Logfile Daemon: opening log
> /var/log/squid/access.log
> lug 07 12:53:13 etna squid[801]: Local cache digest enabled;
> rebuild/rewrite every 3600/3600 sec
> lug 07 12:53:13 etna squid[801]: Store logging disabled
> lug 07 12:53:13 etna squid[801]: Swap maxSize 0 + 262144 KB, estimated
> 20164 objects
> lug 07 12:53:13 etna squid[801]: Target number of buckets: 1008
> lug 07 12:53:13 etna squid[801]: Using 8192 Store buckets
> lug 07 12:53:13 etna squid[801]: Max Mem  size: 262144 KB
> lug 07 12:53:13 etna squid[801]: Max Swap size: 0 KB
> lug 07 12:53:13 etna squid[801]: Using Least Load store dir selection
> lug 07 12:53:13 etna squid[801]: Set Current Directory to /var/spool/squid
> lug 07 12:53:13 etna squid[801]: Finished loading MIME types and icons.
> lug 07 12:53:13 etna squid[801]: HTCP Disabled.
> lug 07 12:53:13 etna squid[801]: Pinger socket opened on FD 14
> lug 07 12:53:13 etna squid[801]: Squid plugin modules loaded: 0
> lug 07 12:53:13 etna squid[801]: Adaptation support is off.
> lug 07 12:53:13 etna squid[801]: Accepting HTTP Socket connections at
> local=[::]:3128 remote=[::] FD 12 flags=9
> lug 07 12:53:14 etna squid[801]: storeLateRelease: released 0 objects
> ---
>
> As you can see, when squid starts it cannot find /etc/resolv.conf and so
> seems to fallback to use a local nameserver, that is not present here.
> Here networking is managed by NetworkManager and /etc/resolv.conf is
> currently a symbolic link to /run/NetworkManager/resolv.conf
> Looks like squid.service starts too early, when the link is still not
> set.
>
> Cesare.
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
> LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages squid depends on:
> ii  adduser  3.117
> ii  libc62.27-3
> ii  libcap2  1:2.25-1.2
> ii  libcom-err2  1.44.3~rc2-1
> ii  libdb5.3   

Bug#903212: alsa-utils: speaker-test catches SIGINT and can't be interrupted

[Mikulas Patocka]

Package: alsa-utils
Version: 1.1.3-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Run speaker-test (for example "speaker-test -c 2 -t sine -f 200 -s 2")
Press Ctrl-c

   * What was the outcome of this action?

The speaker-test program catches the SIGINT signal and ignores it.
It can't be interrupted.

   * What outcome did you expect instead?

The speaker-test program should be interruptible.

It is possible that the speaker-test program creates sounds that are
unpleasant or painful and there should be possibility to interrupt it.

Note - it is possible to interrupt it with Ctrl-\, but unfortunatelly,
that writes 279MB core file and the sound doesn't stop until the file is
written.

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


-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armel, armhf

Kernel: Linux 4.17.4 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages alsa-utils depends on:
ii  kmod  23-2
ii  libasound21.1.3-5
ii  libc6 2.24-11+deb9u3
ii  libfftw3-single3  3.3.5-3
ii  libncursesw5  6.0+20161126-1+deb9u2
ii  libsamplerate00.1.8-8+b2
ii  libtinfo5 6.0+20161126-1+deb9u2
ii  lsb-base  9.20161125
ii  whiptail  0.52.19-1+b1

alsa-utils recommends no packages.

alsa-utils suggests no packages.

-- no debconf information

Bug#903010: golang-gopkg-inf.v0: No Breaks/Replaces/Conflics with golang-speter-go-exp-math-dec-inf-dev

[Sascha Steinbiss]

Hi Dmitry,

Many thanks for your bug report.

> This package introduced "gopkg.in/inf.v0" again without Breaks/Replaces/
> Conflics with the original package "golang-speter-go-exp-math-dec-inf" which
> "Provides: golang-gopkg-inf.v0-dev”.

Oh, I see. Sorry for my completely avoidable oversight... I didn’t think of any 
such problems as my package had passed NEW a year ago without problems, and my 
recent upload didn’t change anything about the actual content, only metadata.
Looks like I should have done my homework some time ago :/

What do you suggest we do now? Should we declare mutual ‘Conflicts’ between 
this package and 'golang-speter-go-exp-math-dec-inf'?

Sorry again and best regards
Sascha


signature.asc
Description: Message signed with OpenPGP

Bug#903210: kgb-bot: Please add https support

[Guillem Jover]

Package: kgb-bot
Version: 1.51-1
Severity: wishlist

Hi!

At least when using the kgb-client to talk to a kgb-bot, any passwords
or tokens are sent in the clear. It would be nice if https was
supported when talking to the server.

Thanks,
Guillem

Bug#903211: release.debian.org: How to handle unbuildable packages in buster

[Santiago Vila]

Package: release.debian.org
Severity: wishlist

Dear Release Managers:

I'm looking for guidance and advice here.

I'm reporting FTBFS bugs in testing, but I'm skipping bugs of type
"unmet build-depends" because I've heard somewhere that Britney takes
care of that.

However, I don't see the procedure is working 100% correctly (maybe
because of transitive build-dependencies/dependencies).

The question: It is still ok to submit FTBFS bugs so that the rule
"package in buster must be buildable in buster" is met?

Thanks.

Bug#873330: stretch-pu: package libosmium/2.11.4-1

[Sebastiaan Couwenberg]

On 07/07/2018 01:40 PM, Adam D. Barratt wrote:
> On Sun, 2018-02-25 at 16:02 +0100, Sebastiaan Couwenberg wrote:
>> On 08/27/2017 10:36 PM, Sebastiaan Couwenberg wrote:
>>> On 08/27/2017 12:46 PM, Adam D. Barratt wrote:
 On Sat, 2017-08-26 at 17:42 +0200, Bas Couwenberg wrote:
> Upstream has releases a new stable release of libosmium fixing
> important
> bugs which I'd like to propose for inclusion in the next stable
> update.

 So far as I can see, the change to memory/item.hpp has not yet
 been applied to unstable.
>>>
>>> The fix for buffers larger than 2^32 bytes is included in 2.13.0
>>> [0],
>>> and we have 2.13.1 in unstable. The fix for 2.11.x [1] differs to
>>> minimize the impact on existing code.
>>>
>>> [0] https://github.com/osmcode/libosmium/commit/57d4f7c114f44af2ff2
>>> 58899be2296a931b8eb96
>>> [1] https://github.com/osmcode/libosmium/commit/0d9516b16a510c7375b
>>> 26933462ba294ed6eb8c7
> 
> Please go ahead; sorry for the delay.

Thanks, libosmium (2.11.4-1) was just built and uploaded to stretch.

Kind Regards,

Bas

Bug#903209: scilab: ATOMS system is broken in Scilab 6 on buster

[Nrbrtx]

Package: scilab
Version: 6.0.0-1
Severity: important

Dear Maintainer,

I have installed Scilab 6 package as usual with
apt-get update
apt-get install scilab

Then I started Scilab from terminal and tried to use its ATOMS system with

atomsShow('coselica')

After launching this command Scilab shows error in its console:

--> atomsShow('coselica')
Scanning repository http://atoms.scilab.org/6.0 ... Done

at line   265 of function atomsDESCRIPTIONget (
/usr/share/scilab/modules/atoms/macros/atoms_internals/atomsDESCRIPTIONget.sci
line 284 )
at line31 of function atomsIsPackage  (
/usr/share/scilab/modules/atoms/macros/atoms_internals/atomsIsPackage.sci
line 47 )
at line43 of function atomsShow   (
/usr/share/scilab/modules/atoms/macros/atomsShow.sci line 59 )

atomsDESCRIPTIONget: save
('/home/debian/.Scilab/scilab-6.0.0/.atoms/packages') has failed.

and in control terminal

HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 140196184387520:
  #000: ../../../src/H5G.c line 553 in H5Gget_info(): invalid argument
major: Invalid arguments to routine
minor: Bad value
HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 140196184387520:
  #000: ../../../src/H5G.c line 301 in H5Gcreate2(): not a location
major: Invalid arguments to routine
minor: Inappropriate type
  #001: ../../../src/H5Gloc.c line 253 in H5G_loc(): invalid object ID
major: Invalid arguments to routine
minor: Bad value
HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 140196184387520:
  #000: ../../../src/H5A.c line 265 in H5Acreate2(): not a location
major: Invalid arguments to routine
minor: Inappropriate type
  #001: ../../../src/H5Gloc.c line 253 in H5G_loc(): invalid object ID
major: Invalid arguments to routine
minor: Bad value
HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 140196184387520:
  #000: ../../../src/H5D.c line 121 in H5Dcreate2(): not a location ID
major: Invalid arguments to routine
minor: Inappropriate type
  #001: ../../../src/H5Gloc.c line 253 in H5G_loc(): invalid object ID
major: Invalid arguments to routine
minor: Bad value
HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 140196184387520:
  #000: ../../../src/H5F.c line 749 in H5Fclose(): not a file ID
major: Invalid arguments to routine
minor: Inappropriate type
failed to close file


This behavior is not expected.
Please fix Scilab package dependencies.

Please note that this bug exists in downstream (Ubuntu) too - see
bugs.launchpad.net/bugs/1765503 .



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

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

Versions of packages scilab depends on:
ii  scilab-cli   6.0.0-1
ii  scilab-full-bin  6.0.0-1

Versions of packages scilab recommends:
ii  scilab-doc  6.0.0-1

Versions of packages scilab suggests:
pn  scilab-doc-fr 
pn  scilab-doc-ja 
pn  scilab-doc-pt-br  

-- no debconf information

Bug#814190: [Pkg-privacy-maintainers] Bug#814190: Ping

[Antoine Beaupré]

On 2018-07-07 16:14:00, u wrote:
> Salut Antoine,
>> I did enter my password at the prompt, but it failed to do the right
>> thing.
>
> What does `pkexec whoami` tell you?

I believe I answered that in an earlier email, but here it is again:

[997]anarcat@curie:~$ pkexec whoami
 AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/usr/bin/whoami' as the super user
Authenticating as: Antoine Beaupre,,, (anarcat)
Password: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.
[998]anarcat@curie:~127$ 

a.

-- 
For every complex problem, there is an answer that is clear, simple -
and wrong.
- H.L. Mencken

Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

[Joel Cross]

On Fri, 6 Jul 2018, at 5:31 PM, Michael Biebl wrote:
> Am 06.07.2018 um 17:02 schrieb mario.limoncie...@dell.com:
> >> -Original Message-
> >> From: Michael Biebl [mailto:bi...@debian.org]
> 
> >> If you have multiple swap partitions and you run
> >> echo "disk" > /sys/power/state
> >> which partition does the kernel use?
> >>
> > 
> > Whichever one was configured in /sys/power/resume prior to running that 
> > command.
> > 
> > The kernel can't know which one /to/ hibernate to unless it was configured 
> > in advance.
> > Just like the initramfs can't know which one to resume /from/ unless it 
> > knew which one
> > it resumed to.
> > 
> 
> Joel, can you please tell us,
> - which partition you have configured in /etc/initramfs-tools/conf.d/resume
> - which partition you have configured in /sys/power/resume
> - the size of both swap partitions
> 

$ cat /proc/swaps
FilenameTypeSizeUsedPriority
/dev/sdb4   partition   9752572 1473128 100
/dev/sda8   partition   6236156 0   10

$ blkid /dev/sdb4 /dev/sda8
/dev/sdb4: LABEL="Swap" UUID="0797ee37-d1b9-49ea-a865-c73682cd96a7" TYPE="swap" 
PARTUUID="57f4c922-04"
/dev/sda8: UUID="84f3e7a4-c3af-4ac1-a789-cc554395a50b" TYPE="swap" 
PARTUUID="170bc00e-08"

$ grep resume /boot/grub/grub.cfg|head -n 1
linux   /vmlinuz-4.16.0-2-amd64 
root=UUID=033d10f2-5402-4632-bed0-5e24842cf1b7 ro  quiet splash 
resume=UUID=84f3e7a4-c3af-4ac1-a789-cc554395a50b

$ cat /etc/initramfs-tools/conf.d/resume
cat: /etc/initramfs-tools/conf.d/resume: No such file or directory

$ cat /sys/power/resume
8:8

>From the above (especially grub.cfg) you can see that the smaller, 
>lower-priority partition is set as the resume partition (this was actually an 
>oversight on my part when I installed the second drive). Do you think this 
>could be what's preventing hibernate from working properly?

Also, do you think it is significant that the 
/etc/initramfs-tools/conf.d/resume file does not exist on my system?

-Joel

Bug#903208: Scilab 6 shows Java warnings on start

[Nrbrtx]

Package: scilab
Version: 6.0.0-1
Severity: important

Dear Maintainer,

I have installed Scilab 6 package as usual with
apt-get update
apt-get install scilab

When I launch it I get the following warning messages:

$ scilab
Warning: Could not find Java package
'/usr/share/java/lucene-core-4.10.4.jar'.
Warning: Could not find Java package
'/usr/share/java/lucene-analyzers-common-4.10.4.jar'.
Warning: Could not find Java package
'/usr/share/java/lucene-queryparser-4.10.4.jar'.
Warning: Could not find Java package '/usr/share/java/jlatexmath-1.0.6.jar'.
Some problems during the loading of the Java libraries occurred.
This could lead to inconsistent behaviours.
Please check SCI/etc/classpath.xml.

This behavior is not expected.
Please fix Scilab package dependencies.

Please note that this bug exists in downstream (Ubuntu) too - see
bugs.launchpad.net/bugs/1767082 .

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

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

Versions of packages scilab depends on:
ii  scilab-cli   6.0.0-1
ii  scilab-full-bin  6.0.0-1

Versions of packages scilab recommends:
ii  scilab-doc  6.0.0-1

Versions of packages scilab suggests:
pn  scilab-doc-fr 
pn  scilab-doc-ja 
pn  scilab-doc-pt-br  

-- no debconf information

Bug#895596: xrdp 0.9.1-9+deb9u3 flagged for acceptance

[Jonathan Wiltshire]

Control: tags -1 + pending

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian stretch.

Thanks for your contribution!

Upload details
==

Package: xrdp
Version: 0.9.1-9+deb9u3

Explanation: fix off-by-one error which could lead to crashes

Bug#903150: tune2fs: No method to change MMP paramter(s)

[Elliott Mitchell]

On Sat, Jul 07, 2018 at 10:59:46AM -0400, Theodore Y. Ts'o wrote:
> On Fri, Jul 06, 2018 at 10:26:21PM -0700, Elliott Mitchell wrote:
> > Package: e2fsprogs
> > Version: 1.43.4-2
> > 
> > Based on behavior of `tune2fs` and `mount` it seems the MMP protection
> > somehow detects what amounts to its "home" host is.  Problem is there is
> > no function to change whatever the actual parameter is, nor any mention
> > of where it comes from.
> > 
> > I've noticed a difference between two ext4 filesystems which have MMP
> > protection turned on.  On one doing `mount  -o remount,rw` is
> > fast and the other it is slow.  From this behavior I'm pretty sure the
> > MMP feature records some parameter and uses that to mark what its
> > "home" host is.  Mounting read-write anywhere but the "home" host is
> > slow.
> 
> That's not how MMP works.  If you cleanly unmount the file system from
> hostA, and then mount (or remount read-write) on hostB there will be
> no delay.

This then suggests this bug should be against linux-source-4.9 instead of
e2fsprogs.

A few command sequences and notes on how fast the command executes on the
machine:

mount / -o rw,remount   => slow
mount / -o ro,remount   => fast
mount / -o rw,remount   => slow
mount / -o ro,remount   => fast

By your explanation, the first ro,remount should set the sequence to 0
(or appropriate equivalent value).  After which the second ro,remount
*should* be fast, yet is not.  The message "EXT4-fs warning (device
rootdev): ext4_multi_mount_protect:324 MMP interval 42 higher than
expected, please wait." appears in triplicate in `dmesg` for each of the
rw,remount commands.

Slightly differing sequence:

tune2fs -f -E clear_mmp /dev/rootdev
mount / -o rw,remount   => fast
mount / -o ro,remount   => fast
mount / -o rw,remount   => slow
mount / -o ro,remount   => fast


> So if the previous owner is dead, the remount read-write will be slow.
> That's by defintion.  It's how it works.  The mmp_node_name and
> mmp_device_name displayed by dumpe2fs:
> 
> MMP_block:
> mmp_magic: 0x4d4d50
> mmp_check_interval: 5
> mmp_sequence: 0xff4d4d50
> mmp_update_date: Sat Jul  7 10:50:26 2018
> mmp_update_time: 1530975026
> mmp_node_name: cwcc
> ummp_device_name: loop0
> 
> is purely for debugging purposes.  All of the MMP mechanism is done
> via the mmp_sequence number.

`dumpe2fs` 1.43.4-2 fails to produce that output.  "MMP block number" and
"MMP update interval" appear in the output, but none of the other values
do.

I'm very suspicious e2fsprogs still has some sort of issue lurking.  Why
does `tune2fs -f -E clear_mmp` clear the issue for 1 and only 1 rw mount?

This being at least partially a kernel bug wouldn't surprise me at all.
I'm not yet convinced there isn't an issue with e2fsprogs lurking though.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Bug#902948: drop it for now.

[David Bremner]

Thanks to Stig for being willing to maintain it, but let's not go
through extra work unless there is user demand for it. Let's drop if
from emacs-goodies-el for now; if someone complains we can bring it
back.

Bug#903207: ITP: vdjtools -- post-analysis of B/T cell repertoires

[Steffen Moeller]

Package: wnpp
Severity: wishlist
Owner: Steffen Moeller 

* Package name: vdjtools
  Version : 1.1.9
* URL : https://milaboratory.com/software/vdjtools/
* License : MIT/X-like
  Programming Lang: Java
  Description : post-analysis of B/T cell repertoires

To appear on https://salsa.debian.org/java-team/vdjtools .

Bug#814190: [Pkg-privacy-maintainers] Bug#814190: Ping

[u]

Salut Antoine,

Antoine Beaupré:
> Control: found 814190 5.0.6+dfsg-1~bpo9+1
> It *looks* like it mostly finished correctly, but failed to
> unmount. Here's the output in the text area:

It basically failed exactly at the two moments (writing the MBR and
unmounting the device) where polkit it called :)

> ['/sbin/sgdisk', '--print', '/dev/sdc']
> Problem opening /dev/sdc for reading! Error is 13.
> You must run this program as root or use sudo!
> 
> ['/sbin/sgdisk', '--zap-all', '/dev/sdc']
> Problem opening /dev/sdc for reading! Error is 13.
> You must run this program as root or use sudo!
> Problem opening '' for writing! Program will now terminate.
> Warning! MBR not overwritten! Error is 2!

> /usr/bin/pkexec /usr/bin/syslinux  -d syslinux /dev/sdc1
> polkit-agent-helper-1: pam_authenticate failed: Authentication failure
> Error executing command as another user: Not authorized
> 
> This incident has been reported.
> 
> Un problème est survenu lors de l'exécution de la commande suivante : 
> `/usr/bin/pkexec /usr/bin/syslinux  -d syslinux /dev/sdc1`
> Authentication is needed to run `/usr/bin/syslinux' as the super user
> Authenticating as: Antoine Beaupre,,, (anarcat)
> Password: 
>  AUTHENTICATION FAILED ===
> Exception in thread Thread-2:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
> self.run()
>   File "/usr/lib/python2.7/dist-packages/tails_installer/gui.py", line 264, 
> in run
> self.live.log.exception(unicode(e))
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 8: 
> ordinal not in range(128)
> 
> 
> I did enter my password at the prompt, but it failed to do the right
> thing.

What does `pkexec whoami` tell you?

Cheers!
u.

Bug#727604: Справочная служба администратора

[Наталья Штырляева]

Дорогой пользователь

Мы отключим вашу учетную запись из-за
нескольких халатности ранее
отправленных писем в отношении
обновления учетной записи. Пожалуйста,
ЩЕЛКНУТЬ ЗДЕСЬ и обновите свой почтовый
ящик, чтобы избежать деактивации.

Административная справочная служба

https://xn--80btabhffycazi2ating0ajcct1acg.weebly.com

Copyright © 2018 IT Help Desk. Все права защищены