Bug#892453: marked as done (therion: Please use 'pkg-config' to find FreeType 2)

[Debian Bug Tracking System]

Your message dated Tue, 23 Oct 2018 05:04:20 +
with message-id 
and subject line Bug#892453: fixed in therion 5.4.1ds1-3
has caused the Debian Bug report #892453,
regarding therion: Please use 'pkg-config' to find FreeType 2
to be marked as done.

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

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


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

Dear Maintainer,

The next release of libfreetype6-dev will *not* ship
`freetype-config', as the script has now been deprecated in favour of
`pkg-config'.

This is an upstream change:

"Use of the `freetype-config' script to get compilation and

linking options is deprecated since it doesn't support

cross-compiling, among other deficiencies. Instead, you should

use the `pkg-config' interface." [1]

Please use `pkg-config' to detect the FreeType 2 headers and
libraries in therion.

If this bug is not resolved prior to the release of FreeType 2.9.1,
your package may FTBFS.

Thank you

[1]
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0
a93839b52818abbfe9b4c8755b4aa0f5232063 
--- End Message ---
--- Begin Message ---
Source: therion
Source-Version: 5.4.1ds1-3

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

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

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

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated therion package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 23 Oct 2018 16:43:14 +1300
Source: therion
Binary: therion therion-viewer therion-doc
Architecture: source
Version: 5.4.1ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Wookey 
Changed-By: Olly Betts 
Description:
 therion- Cave surveying - 2D and 3D drawing software
 therion-doc - Documentation for Therion Cave surveying software
 therion-viewer - Cave surveying - 3D viewer for therion models
Closes: 892453
Changes:
 therion (5.4.1ds1-3) unstable; urgency=medium
 .
   * New patch 05pkg-config-for-freetype.patch cherry-picked from upstream
 git master to switch from freetype-config to pkg-config.
 (Closes: #892453)
   * debian/source/options: Drop now-redundant 'compression = "xz"'.
   * debian/compat,debian/control: Update to use compat level 10
 instead of 9.
   * debian/control: Declare conformance with policy 4.2.1.
   * debian/changelog,debian/control,debian/rules: Remove trailing whitespace
 to silence pedantic lintian warning.
Checksums-Sha1:
 e506933f3cf499d2a61a3ee71c5001324f705750 2090 therion_5.4.1ds1-3.dsc
 7e99a42fba744073b45569665b8da6f27bd8937b 19964 therion_5.4.1ds1-3.debian.tar.xz
 8205733fe98f324019f03249f76ec081288d857c 24218 
therion_5.4.1ds1-3_amd64.buildinfo
Checksums-Sha256:
 5c1a54118bdafb3f33ae6aa3e2627134557360599d1917f52257b3008fe3dbd9 2090 
therion_5.4.1ds1-3.dsc
 303d7eb46e21335d3fab0de7bceb41300c6275adfc14cde9b80cfea36e468428 19964 
therion_5.4.1ds1-3.debian.tar.xz
 da6db216b6e915cccd92ba93639ae615d5c5f6dfa1ea43049f83b2565f08ca40 24218 
therion_5.4.1ds1-3_amd64.buildinfo
Files:
 815c7b38230e8c88098880cacea4dedb 2090 science optional therion_5.4.1ds1-3.dsc
 5d732a2523894b48048b27d829d6fbe9 19964 science optional 
therion_5.4.1ds1-3.debian.tar.xz
 607493a7fcec478882bf27c38f28ed8b 24218 science optional 
therion_5.4.1ds1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEECOJAD/f+j+3jrLUoGBR7BzutKwcFAlvOp4kACgkQGBR7Bzut
KwfT0hAA09vit+Cn85FEqM1mdRGH2cFvt2Lzj59tAQijLqiPcyhxS4Ogn43ZUjSK
IPgi0RhEoO9mWx47OYX+WepvGKgs5WuK2KiurBH+xSQ9kNPOxg2/nxsmY7DtsLty
SiPNlvdCNTiecCEpT9KJokMk+JkvezFu/EaYFXjhYDePgjZLvxitzm8H+oOZKUo0
XJEIXfIyIzu3Y6XPer+Ae2b/BVIFyuO6+d+NXOsCbtk/JRPkYI8cNBXaYiViQd2m
1YcsBN/rKD4FxvZEKuR6KCR2rrKMhJdXe1ax9jnawPkLcnIKXmV2qmy9zH2SzgU5
oTYYCWlQ5wqt8W6jkk4mt+PIxN0k+itIKECeqaHxNl/NyYJgRCREGOzkeMXvodOR
pI/BTHrOAvPRei0+3Yfeg6MEFpQXtGee/h1pmDNyfm0xwZ49IonnLC+gjtN0oV6+
I00HA9b7+87iJOntCuQsjDqqlJEZ3qe+HG+eKdiM0oga2LPRdUq3JBGT4DdBx/G1
jISJJdgWbk+jZ3iZch8A2KU/S3thDk//AHFfnS1Qm1gxEi4JKgLXexENRI5p+K4d

Bug#910667: marked as done (FTBFS with PHP 7.3)

[Debian Bug Tracking System]

Your message dated Tue, 23 Oct 2018 06:48:54 +0200
with message-id <6ee022d9-978a-4b1f-b725-b4b00fa97...@sury.org>
and subject line Re: php-pinba is marked for autoremoval from testing
has caused the Debian Bug report #910667,
regarding FTBFS with PHP 7.3
to be marked as done.

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

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


-- 
910667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php-pinba
Version: 1.1.0-4
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

the PHP extension fails to build properly with PHP 7.3.  Please update
the extension to add support for PHP 7.3.

Thanks,
Ondrej

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

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

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAlu8smtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcKNIQ/+O7Vi7nClqWkXfBnkqymlAAizkosoYmQ4xwb4gUihvKzmPnXuWBzeFkiS
ZbdvkXtzFJcoKgmrUH67Twyw4FRxzINIEE4kobnIXs338tIPYH1DMDaXy5/+nxw1
Mn/9m/bQwDIngcsQAcqvw8GvhGNIvl8gZCRnqk1Yp/e3mrsXjljmD226zBkfIzWf
MTG2KqRm6apurTgoQI3EqrF8tWKhTXne7Lrlo7q64xxvfsgHlK/rjMeInmj+qHB7
J57cj6ubGhQPaKZRjGM0rCV+F+eFFDkTaeTBQtzEZwkFnGE6UAGYP+lyHr0hUHL0
/HKYBMNFhUP4N8xIIQykW3xpcLXi9GUwretY5+w/iIO56qtcAKJA/HwvgYzShRJW
24DOL8e71WxEuYi+yWipVYwiX7vsQ6fLsBcXVJ8t3hFFz29Ncj6Jwf4ebE3AHtWP
qKqsmjGeLJeO6EgrNlMg22z+Qm5q9YAKrdLVfAKNa2Pa9dWiq/DuER5xu/XDFkJJ
3e/9J9QZjyx7Nr+NL6ny6VlZxP/50TnJK/U+5X7TqNHyOyTAx+zerj5dPLzK3ktx
Vo7nELRyNKvhjSSi6B0nLPKsrShMOssVJ95Ic0SRWfKvF2PwZ8cPXO6DVZ3XaTO7
lohNemugGeF30sRcqF1aBh3BYBgSReaodHPPBvWbPa4UkO15mwM=
=M8Yl
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 1.1.0-5

--
Ondřej Surý 

> On 23 Oct 2018, at 06:39, Debian testing autoremoval watch 
>  wrote:
> 
> 910667--- End Message ---

Processed: tagging 892453

[Debian Bug Tracking System]

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

> tags 892453 + pending
Bug #892453 [src:therion] therion: Please use 'pkg-config' to find FreeType 2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#892346: marked as done (pcmanx-gtk2: Please use 'pkg-config' to find FreeType 2)

[Debian Bug Tracking System]

Your message dated Tue, 23 Oct 2018 04:04:51 +
with message-id 
and subject line Bug#892346: fixed in pcmanx-gtk2 1.3-2
has caused the Debian Bug report #892346,
regarding pcmanx-gtk2: Please use 'pkg-config' to find FreeType 2
to be marked as done.

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

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


-- 
892346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pcmanx-gtk2
Severity: important

Dear Maintainer,

The next release of libfreetype6-dev will *not* ship
`freetype-config', as the script has now been deprecated in favour of
`pkg-config'.

This is an upstream change:

"Use of the `freetype-config' script to get compilation and

linking options is deprecated since it doesn't support

cross-compiling, among other deficiencies. Instead, you should

use the `pkg-config' interface." [1]

Please use `pkg-config' to detect the FreeType 2 headers and
libraries in pcmanx-gtk2.

If this bug is not resolved prior to the release of FreeType 2.9.1,
your package may FTBFS.

Thank you

[1]
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0
a93839b52818abbfe9b4c8755b4aa0f5232063 
--- End Message ---
--- Begin Message ---
Source: pcmanx-gtk2
Source-Version: 1.3-2

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

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

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

Debian distribution maintenance software
pp.
Emfox Zhou  (supplier of updated pcmanx-gtk2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 23 Oct 2018 11:38:56 +0800
Source: pcmanx-gtk2
Binary: pcmanx-gtk2
Architecture: source amd64
Version: 1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Emfox Zhou 
Changed-By: Emfox Zhou 
Description:
 pcmanx-gtk2 - user-friendly telnet client mainly targets BBS users
Closes: 856687 892346
Changes:
 pcmanx-gtk2 (1.3-2) unstable; urgency=medium
 .
   * Use pkg-config instead of freetype-config. (Closes: #892346)
   * Upstream patch fixing leading char of address missing. (Closes: #856687)
   * Policy updated to 4.2.1, change priority from extra to optional.
Checksums-Sha1:
 a036966bf84a5cc71444e9227927845b38af10e6 1904 pcmanx-gtk2_1.3-2.dsc
 0346bb9036a1299797143ac0f10d3a4e9254edf3 5452 pcmanx-gtk2_1.3-2.debian.tar.xz
 8f789c0722db0d7225c60666fe4435152ce1 1791160 
pcmanx-gtk2-dbgsym_1.3-2_amd64.deb
 c0ffeac20e5a8f9c374f26a3fe54a21dce2f4c64 11206 
pcmanx-gtk2_1.3-2_amd64.buildinfo
 8142c0a7c556ced6812f7d3c0577032f326ad408 284340 pcmanx-gtk2_1.3-2_amd64.deb
Checksums-Sha256:
 a053042b9a3522810ad5b5aa2411d69fcfadfe5afe42b617faa22a44d174f880 1904 
pcmanx-gtk2_1.3-2.dsc
 a353776e1210ae93692d9a39ed0ef53fb8082769f1158e9071fca42b4a5393e3 5452 
pcmanx-gtk2_1.3-2.debian.tar.xz
 f941cd457623c0c4f1229bc4ef157424dacd73360e5b53295eddfe8a29901f03 1791160 
pcmanx-gtk2-dbgsym_1.3-2_amd64.deb
 1be0d26e06e818519414c2d22063cfd2d0c7a576c55bc69c7d656cc62f241124 11206 
pcmanx-gtk2_1.3-2_amd64.buildinfo
 339da59c9a1014c73fceda4f32423a0cd8a86ccc00e77687b6c47d05da2a2520 284340 
pcmanx-gtk2_1.3-2_amd64.deb
Files:
 933c042126644f12536be303858b8504 1904 x11 optional pcmanx-gtk2_1.3-2.dsc
 b6378d8a571f964f8af7cbe44c35b254 5452 x11 optional 
pcmanx-gtk2_1.3-2.debian.tar.xz
 61696fb4ec5512aba21b233906c37bdc 1791160 debug optional 
pcmanx-gtk2-dbgsym_1.3-2_amd64.deb
 f3a3c69fbc305d9b470fdf8e2f30ab17 11206 x11 optional 
pcmanx-gtk2_1.3-2_amd64.buildinfo
 e797908e223ff246e5f3d6dcb7df39f5 284340 x11 optional 
pcmanx-gtk2_1.3-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEGSauJtItZVqOiaNpgImbv9t7vZQFAlvOmAsACgkQgImbv9t7
vZTODQ/+NWMBgjW9mz4/ot6Ta5Id5uW2mJtIDBNSyaCA6Stzfldbwrunq1O1ZINF
yDprbMLiLfJRfs2xe6VtVW6hkQQJ3Bus+UbrvrXw0aq0V1//KxS1sohkrL164Zvu
Ts66Rk9LMP4rr7OsbDHRHXaDKRCa5yT5oPnB94OEsKXKgfqQxFT7qfI/AwnusOu4
GTIMDky5wioEUgJQ+2QkbJReUBGVz4AqCEfa77XuVpZr1eMO9ZsTmW0ybXLHIhR5
YDiDfVhALg3ytJV9aytagMHdh5JN++Q/Mvex0uiy9Ysu1/ZkHM/VBCLMNOphC9BZ
HYk2KNOUNoXVY049KHCliDCN/agPhAldoURBcS0kgQtjFyky21AwswwN/8Dpg/03
sePetDkbcRIIbIRV6Y0yGSRwjze5nhNmPRsvLPk1nkniD/Sp5UDoLZsoVyTZUJXQ

Bug#899924: marked as done (fcitx-m17n: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 23 Oct 2018 03:19:01 +
with message-id 
and subject line Bug#899924: fixed in fcitx-m17n 0.2.4-2
has caused the Debian Bug report #899924,
regarding fcitx-m17n: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fcitx-m17n
Version: 0.2.4-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of fcitx-m17n,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package fcitx-m17n since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: fcitx-m17n
Source-Version: 0.2.4-2

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated fcitx-m17n package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Oct 2018 21:26:07 -0400
Source: fcitx-m17n
Binary: fcitx-m17n
Architecture: source
Version: 0.2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 fcitx-m17n - Free Chinese Input Toy of X - m17n module
Closes: 899924
Changes:
 fcitx-m17n (0.2.4-2) unstable; urgency=medium
 .
   * Team upload.
   * Manual rebuild against m17n-lib 1.8.0 and gcc 8.2.
   * Refresh packaging information.
 + Bump debhelper compat to v11.
 + Bump Standards-Version to 4.2.1.
 + Update maintainer to Debian Input Method Team. (Closes: #899924)
 + Update uploaders' email address and use the @debian.org one.
 + Update Vcs-* fields and use the git repo under Salsa
   input-method-team group.
 + Use "dh_missing --fail-missing" in debian/rules.
Checksums-Sha1:
 3cf95a3b511139018f318c163e05017878e3cbec 2030 fcitx-m17n_0.2.4-2.dsc
 940015f1a440f25ed4167a444dece8789030eea1 2740 fcitx-m17n_0.2.4-2.debian.tar.xz
 8862b02a3a3bacc3d8f7865e9b24780ef30377c5 9164 
fcitx-m17n_0.2.4-2_amd64.buildinfo
Checksums-Sha256:
 f82c67b20e259b8545bd3e3c4c4510dc578684381b02dc0b9e49afa7c0aa6f18 2030 
fcitx-m17n_0.2.4-2.dsc
 2d4bd411e8114c7295e93cfba283f74751861135e3cf92b4410beeab172b9f11 2740 

Bug#910444: OpenRC called by update-rc.d should read defaults from headers

[Benda Xu]

Control: reassign 910444 init-system-helpers
Control: forwarded 910444 
https://salsa.debian.org/debian/init-system-helpers/merge_requests/6
Control: tags 910444 patch

Hi,

With the input and help from biebl, I was able to chase down this bug to
update-rc.d.  After refactorization by fsateler, the execution order was
changed and the previous assumption does not hold anymore.

Please find the pull request at
https://salsa.debian.org/debian/init-system-helpers/merge_requests/6

Cheers,
Benda

Processed: OpenRC called by update-rc.d should read defaults from headers

[Debian Bug Tracking System]

Processing control commands:

> reassign 910444 init-system-helpers
Bug #910444 [openrc] Filesystems listed in /etc/fstab are no more automatically 
mounted since switching to OpenRC
Bug reassigned from package 'openrc' to 'init-system-helpers'.
No longer marked as found in versions openrc/0.34-3.
Ignoring request to alter fixed versions of bug #910444 to the same values 
previously set
> forwarded 910444 
> https://salsa.debian.org/debian/init-system-helpers/merge_requests/6
Bug #910444 [init-system-helpers] Filesystems listed in /etc/fstab are no more 
automatically mounted since switching to OpenRC
Set Bug forwarded-to-address to 
'https://salsa.debian.org/debian/init-system-helpers/merge_requests/6'.
> tags 910444 patch
Bug #910444 [init-system-helpers] Filesystems listed in /etc/fstab are no more 
automatically mounted since switching to OpenRC
Added tag(s) patch.

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

Bug#883731: audacious: Debian packaging has incorrect license

[Nicholas D Steeves]

On Mon, Oct 22, 2018 at 08:50:56PM +0200, Andrej Shadura wrote:
> 
>I was going to have a look but got distracted by writing kernel drivers
>â** fascinating stuff :D
>I will try and spend some time this week on this. If not, I'll post an
>update here.

Thank you Andrej!  Very much appreciated :-)  I hope this bug contains
all the information you need.

Yes, they really are, although I must confess the details are a bit
above my head.  Kudos for getting to that level of proficiency!  By
the way, assuming you're a member of a the Multimedia Team, and are
interested in kernel drivers, are you the Debian guy to contact for
audio interface driver issues (eg: model specific quirks) or wishlist
"please support this new awesome interface or peripheral"? ;-)

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#899502: marked as done (fcitx-qimpanel: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Tue, 23 Oct 2018 01:49:26 +
with message-id 
and subject line Bug#899502: fixed in fcitx-qimpanel 2.1.3-2
has caused the Debian Bug report #899502,
regarding fcitx-qimpanel: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fcitx-qimpanel
Version: 2.1.3-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of fcitx-qimpanel,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package fcitx-qimpanel since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: fcitx-qimpanel
Source-Version: 2.1.3-2

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated fcitx-qimpanel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Oct 2018 21:16:37 -0400
Source: fcitx-qimpanel
Binary: fcitx-ui-qimpanel
Architecture: source
Version: 2.1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 fcitx-ui-qimpanel - Flexible Input Method Framework - Qt IMPanel user interface
Closes: 899502
Changes:
 fcitx-qimpanel (2.1.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Modernize packaging.
 + Update maintainer to Debian Input Method Team. (Closes: #899502)
 + Bump debhelper compat to v11.
 + Bump Standards-Version to v4.2.1.
 + Use "dh_missing --fail-missing" in debian/rules.
 + Use secure uri in debian/copyright.
Checksums-Sha1:
 26f9dbfcb956f05ed3a45fc11b89014c2097f279 2119 fcitx-qimpanel_2.1.3-2.dsc
 9d51ed69efb1e891c3a6fbc7757ae605e3600019 2816 
fcitx-qimpanel_2.1.3-2.debian.tar.xz
 b1ead2d9515af9c5aaae4a5353d3a17d15a2b0c7 12364 
fcitx-qimpanel_2.1.3-2_amd64.buildinfo
Checksums-Sha256:
 ae5492155477b905fdd8d2663d58518d5c2b5c6512602df8ed3ebe697bfe2ef0 2119 
fcitx-qimpanel_2.1.3-2.dsc
 d380c8fb37b9035dc11e7fcbdb0364db4eaf48004cae86be2489e49099cd8459 2816 
fcitx-qimpanel_2.1.3-2.debian.tar.xz
 

Bug#883731: audacious: Debian packaging has incorrect license

[Nicholas D Steeves]

Hi Francesco,

On Tue, Dec 12, 2017 at 11:37:46PM +0100, Francesco Poli wrote:
> On Tue, 12 Dec 2017 16:39:28 -0500 Nicholas D Steeves wrote:
> 
> [...]
> > This is one of the reasons the FSF demands copyright
> > assignment for their projects...they want to be able to relicense at
> > any point in the future without having to contact and document consent
> > from all contributors.
> 
> Yeah, right: they want to do what they like, without asking whether the
> contributors are fine with their decisions...
> Personally, I consider this FSF copyright assignment policy a very bad
> practice!
> 
> But I am digressing...

Sorry this email fell through the cracks, even if it is a digression.
I agree that FSF copyright assignment is at odds with the ethos of
empowering the people, because it transfers the people's power to the
organisation--trusting in its beneficence.  Oh, and that it's
identical to the people -> communist party power structure (the people
lose power), or the feudal copyright assignment of employee work to
their employers.

That said, it does make project management easier for the legal and
paperwork side--and for keeping things consistent, particularly if
records are ever lost...which counts as a pro, from a top-down
perspective ;-)

I haven't reread the history of this bug, but if I remember correctly
it's a win for GPL if the GPL translations are combined with BSD
sources, because the resulting binaries become inherently GPL,
assuming the translation meet the criteria for copyrightable material
(eg: originality).  I understand how to this could be frustrating for
a project manager, which is why I thought it was important to mention
the alternative.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#911603: marked as done (evolution-data-server: Postinst script returned error exit status 1 with latest upload)

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 21:49:12 +
with message-id 
and subject line Bug#911603: fixed in evolution-data-server 3.30.2-2
has caused the Debian Bug report #911603,
regarding evolution-data-server: Postinst script returned error exit status 1 
with latest upload
to be marked as done.

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

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


-- 
911603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: evolution-data-server
Severity: serious
Version: 3.30.2-1

% LANG=C.UTF-8 sudo apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  android-libext4-utils android-libselinux android-libsepol
Use 'sudo apt autoremove' to remove them.
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.
Setting up evolution-data-server (3.30.2-1) ...
dpkg: error processing package evolution-data-server (--configure):
 installed evolution-data-server package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
 evolution-data-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

If you can't reproduce it, please let me know and I will provide with
more details.

--
Regards,
Boyuan Yang
--- End Message ---
--- Begin Message ---
Source: evolution-data-server
Source-Version: 3.30.2-2

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated evolution-data-server 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Oct 2018 17:31:43 -0400
Source: evolution-data-server
Binary: evolution-data-server evolution-data-server-common 
evolution-data-server-tests evolution-data-server-dev evolution-data-server-doc 
libedataserver-1.2-23 libedataserver1.2-dev gir1.2-edataserver-1.2 
libedataserverui-1.2-2 libedataserverui1.2-dev gir1.2-edataserverui-1.2 
libcamel-1.2-62 libcamel1.2-dev gir1.2-camel-1.2 libebook-1.2-19 
libebook1.2-dev gir1.2-ebook-1.2 libedata-book-1.2-25 libedata-book1.2-dev 
gir1.2-ebookcontacts-1.2 libebook-contacts-1.2-2 libebook-contacts1.2-dev 
libecal-1.2-19 libecal1.2-dev libedata-cal-1.2-29 libedata-cal1.2-dev 
libebackend-1.2-10 libebackend1.2-dev
Architecture: source
Version: 3.30.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 evolution-data-server - evolution database backend server
 evolution-data-server-common - architecture independent files for Evolution 
Data Server
 evolution-data-server-dev - Development files for evolution-data-server 
(metapackage)
 evolution-data-server-doc - Documentation files for the Evolution Data Server 
libraries
 evolution-data-server-tests - Installed tests for the evolution database 
backend server
 gir1.2-camel-1.2 - GObject introspection for the Camel library
 gir1.2-ebook-1.2 - GObject introspection for the EBook library
 gir1.2-ebookcontacts-1.2 - GObject introspection for the EBook Contacts library
 gir1.2-edataserver-1.2 - GObject introspection for the EDataServer library
 gir1.2-edataserverui-1.2 - GObject introspection for the EDataServerUI library
 libcamel-1.2-62 - Evolution MIME message handling library
 libcamel1.2-dev - Development files for libcamel
 libebackend-1.2-10 - Utility library for evolution data servers
 libebackend1.2-dev - Utility library for evolution data servers (development 
files)
 libebook-1.2-19 - Client library for evolution address books
 libebook-contacts-1.2-2 - Client library for evolution contacts books
 libebook-contacts1.2-dev - Client library for evolution contacts books 
(development files)
 libebook1.2-dev - Client library for evolution address books (development 
files)
 libecal-1.2-19 - Client library for evolution calendars
 

Bug#911603: Bug #911603 in evolution-data-server marked as pending

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #911603 in evolution-data-server reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/evolution-data-server/commit/9271515ac50c17f719e95cedd268473b28823320


Fix postinst script if update-notifier is not installed

- Thanks Felix Zielcke for the suggested fix

Closes: #911603

Gbp-Dch: Full



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/911603

Processed: Bug #911603 in evolution-data-server marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #911603 [evolution-data-server] evolution-data-server: Postinst script 
returned error exit status 1 with latest upload
Added tag(s) pending.

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

Bug#909752: php-apcu-bc 1.0.4-3 : undefined symbol: zif_apcu_store

[Fabrice Régnier]

Package: php-apcu-bc
Version: 1.0.4-3
Severity: serious

Dear Maintainer,

I must add that i couldn't use Christian Marillat's workaround because 
in the /etc/php/7.2/apache2/conf.d/ directory, there was no 20-apcu.ini 
file, just 20-apcu_bc.ini file.


FA:/usr/lib# find . -name "*apc*"
./php/20180731/apcu.so
./php/20180731/apc.so
./php/20170718/apc.so

FA:/usr/lib# cd /etc/php
FA:/etc/php# find . -name "*apc*"
./7.3/phpdbg/conf.d/20-apcu_bc.ini
./7.3/phpdbg/conf.d/20-apcu.ini
./7.3/mods-available/apcu_bc.ini
./7.3/mods-available/apcu.ini
./7.3/cli/conf.d/20-apcu_bc.ini
./7.3/cli/conf.d/20-apcu.ini
./7.2/mods-available/apcu_bc.ini
./7.2/cli/conf.d/20-apcu_bc.ini
./7.2/apache2/conf.d/20-apcu_bc.ini

regards,

Fabrice.

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

Kernel: Linux 4.18.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php-apcu-bc depends on:
ii  libapache2-mod-php7.2 [phpapi-20170718]  7.2.9-1
ii  libc62.27-6
ii  php-apcu 5.1.12+4.0.11-2
ii  php-common   1:62
ii  php7.2-cli [phpapi-20170718] 7.2.9-1
ii  php7.3-cli [phpapi-20180731] 7.3.0~rc2-2
ii  php7.3-phpdbg [phpapi-20180731]  7.3.0~rc2-2

php-apcu-bc recommends no packages.

php-apcu-bc suggests no packages.

Bug#911439: marked as done (prometheus-bind-exporter: FTBFS undefined: prometheus.NewProcessCollectorPIDFn)

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 20:40:37 +
with message-id 
and subject line Bug#911439: fixed in prometheus-bind-exporter 
0.2~git20161221+dfsg-2
has caused the Debian Bug report #911439,
regarding prometheus-bind-exporter: FTBFS undefined: 
prometheus.NewProcessCollectorPIDFn
to be marked as done.

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

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


-- 
911439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: prometheus-bind-exporter
Version: 0.2~git20161221+dfsg-1
Severity: serious
Tags: ftbfs

Dear Maintainer,

When rebuild prometheus-bind-exporter, it FTBFS,

# github.com/digitalocean/bind_exporter
src/github.com/digitalocean/bind_exporter/bind_exporter.go:460:19:
undefined: prometheus.NewProcessCollectorPIDFn

github.com/prometheus/client_golang removed NewProcessCollectorPIDFn in
https://github.com/prometheus/client_golang/commit/773f502

-- 
Shengjing Zhu
--- End Message ---
--- Begin Message ---
Source: prometheus-bind-exporter
Source-Version: 0.2~git20161221+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated 
prometheus-bind-exporter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 22 Oct 2018 19:44:25 +
Source: prometheus-bind-exporter
Binary: prometheus-bind-exporter
Architecture: source
Version: 0.2~git20161221+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Martín Ferrari 
Description:
 prometheus-bind-exporter - Prometheus exporter for Bind server metrics
Closes: 911439
Changes:
 prometheus-bind-exporter (0.2~git20161221+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Alexandre Viau ]
   * Point Vcs-* urls to salsa.debian.org.
 .
   [ Martín Ferrari ]
   * Add patch for update in prometheus client library API. Closes:
 #911439.
   * debian/init: Remove checks for variable that belongs to another
 exporter.
   * Remove unneeded lintian overrides.
   * debian/manpages: Actually install the man page.
   * Add missing postinst script, required to create the system user and
 directories.
   * debian/rules: Remove unneeded DH_GOPKG var, reenable tests.
   * Automated packaging fixes by cme, update compat and Standards-Version.
   * debian/control: Only install daemon if systemd is not present.
   * debian/copyright: Add missing Files-Excluded information.
Checksums-Sha1:
 927230191ab17d3647a1f4b5e1bd6955c38a0eee 2548 
prometheus-bind-exporter_0.2~git20161221+dfsg-2.dsc
 ef255563c2d395320f7622f56081b67a5bd7edd5 5428 
prometheus-bind-exporter_0.2~git20161221+dfsg-2.debian.tar.xz
 9d304563d5f05c8e7477649defc854361115d847 8119 
prometheus-bind-exporter_0.2~git20161221+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 8fbbdc06dde5d69a2f2534327accb86a60ba0691de484bae052bf65e724b 2548 
prometheus-bind-exporter_0.2~git20161221+dfsg-2.dsc
 118c6c3d2b5b02d6c3efaaf560bf49c01fecdb4f12958e7fc9410cd1ef8cf50c 5428 
prometheus-bind-exporter_0.2~git20161221+dfsg-2.debian.tar.xz
 1cd04046e787160544d3a0d79928861f1966650f34d08c7a0b0809c80453cc97 8119 
prometheus-bind-exporter_0.2~git20161221+dfsg-2_amd64.buildinfo
Files:
 2387aff729e94b1fe4b9adf2cab1f7e7 2548 net optional 
prometheus-bind-exporter_0.2~git20161221+dfsg-2.dsc
 eea73d79fe0bdc1e5b1d309fb755abe8 5428 net optional 
prometheus-bind-exporter_0.2~git20161221+dfsg-2.debian.tar.xz
 5fb119869d5285cd442d5f4ba233401b 8119 net optional 
prometheus-bind-exporter_0.2~git20161221+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlvOKNAACgkQXdjgv5Gj
09r2/Q//cf84u81cRifu/iXF9jEjgaFxNZixdQvT/R8GxpXJcx/7FQErTHnBRmYz
TeFP5hRiCUQBA+1yYSeUbXofXZTirBQATgcFlHgUackh2GETHa2tcdG9bK7LsqHC
f8ygQWuGJtbWOManMQdGjcYH+ZkvFv+ZptZNtokPFGtM06m6JzB8S02s88lcav67
57Mf0hyDx3x6HuJIgm6ZLVb6qGzKO9chYdM3sisPDrOkqN9SZxJZo9EAZ+NeEHZ+
iljrTQPS4UsrPylBY3H+UpAv+WkVcW6Ae0aG7jVu8cRKuKdwtdIoGJ4qP3V2F8E0

Processed: Re: liboasis3-0d: does not ship SONAME link

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #864280 [liboasis3-0d] liboasis3-0d: does not ship SONAME link
Severity set to 'serious' from 'important'

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

Bug#911626: [Pkg-emacsen-addons] Bug#911626: elpa-vimish-fold: fails to upgrade from 'stretch': vimish-fold.el:59:1:Error: Cannot open load file: No such file or directory, s

[David Bremner]

Andreas Beckmann  writes:


> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch'.
> It installed fine in 'stretch', then the upgrade to 'buster' fails.
>
> From the attached log (scroll to the bottom...):
>
>   Setting up elpa-vimish-fold (0.2.3-2) ...
>   tsort: -: input contains a loop:
>   tsort: s-el
>   tsort: emacsen-common
>   tsort: -: input contains a loop:
>   tsort: dash-el
>   tsort: emacsen-common
>   Install s-el for emacs24
>   install/s-el: Handling install for emacsen flavor emacs24
>   Loading 00debian-vars...
>   Loading /etc/emacs/site-start.d/50dash-el.el (source)...
>   Loading /etc/emacs/site-start.d/50s-el.el (source)...
>   Wrote /usr/share/emacs24/site-lisp/s-el/s.elc
>   Install dash-el for emacs24
>   install/dash-el: Handling install for emacsen flavor emacs24
>   Loading 00debian-vars...
>   Loading /etc/emacs/site-start.d/50dash-el.el (source)...
>   Loading /etc/emacs/site-start.d/50s-el.el (source)...
>   Wrote /usr/share/emacs24/site-lisp/dash-el/dash-functional.elc
>   Wrote /usr/share/emacs24/site-lisp/dash-el/dash.elc
>   Install emacsen-common for emacs24
>   emacsen-common: Handling install of emacsen flavor emacs24
>   Wrote /etc/emacs24/site-start.d/00debian-vars.elc
>   Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
>   Install elpa-f for emacs24
>   install/f-0.19.0: Handling install of emacsen flavor emacs24
>   install/f-0.19.0: byte-compiling for emacs24
>   Install elpa-vimish-fold for emacs24
>   install/vimish-fold-0.2.3: Handling install of emacsen flavor emacs24
>   install/vimish-fold-0.2.3: byte-compiling for emacs24
>   
>   In toplevel form:
>   vimish-fold.el:59:1:Error: Cannot open load file: No such file or 
> directory, s
>   ERROR: install script from elpa-vimish-fold package failed
>   dpkg: error processing package elpa-vimish-fold (--configure):
>subprocess installed post-installation script returned error exit status 1

I'm not sure I see the whole picture yet, but I guess that

 1) elpa-f in stretch depends on s-el (instead of elpa-s)
 2) elpa-vimish-fold in buster is a new style dh_elpa using package
 that only looks at elpa packages for depends.

Maybe an explicit depends on elpa-s by elpa-vimish-fold would help?

d

Bug#911582: emacspeak does'nt work after upgrading emacs

[Samuel Thibault]

Control: tags -1 + unreproducible

Hello,

Michelangelo Rodriguez, le lun. 22 oct. 2018 10:04:57 +0200, a ecrit:
> after upgrading emacs in unstable, emacsen-common install script for 
> emacspeak exits because flavour emacs is not accepted by script.

I can not reproduce this. Could you run

dpkg -l \*emacs\*

so we can make sure which emacs things you have?

Samuel

Processed: Re: Bug#911582: emacspeak does'nt work after upgrading emacs

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + unreproducible
Bug #911582 [emacspeak] emacspeak does'nt work after upgrading emacs
Added tag(s) unreproducible.

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

Processed: gosa: fails to upgrade from 'stretch': PHP Fatal error: Uncaught Error: Call to undefined function imageCreateFromPng()

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + education-main-server
Bug #911632 [gosa] gosa: fails to upgrade from 'stretch': PHP Fatal error:  
Uncaught Error: Call to undefined function imageCreateFromPng()
Added indication that 911632 affects education-main-server

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

Bug#910959: grub-cloud-amd64: missing Conflicts: grub-coreboot, grub-efi-ia32, grub-ieee1275, grub-xen

[Colin Watson]

On Mon, Oct 22, 2018 at 08:29:34PM +0200, Bastian Blank wrote:
> On Sun, Oct 14, 2018 at 06:40:44PM +0200, Bastian Blank wrote:
> > On Sat, Oct 13, 2018 at 09:33:26PM +0200, Andreas Beckmann wrote:
> > > Here is a list of files that are known to be shared by both packages
> > > (according to the Contents file for sid/amd64, which may be
> > > slightly out of sync):
> > > 
> > > etc/kernel/postinst.d/zz-update-grub
> > > etc/kernel/postrm.d/zz-update-grub
> > 
> > Is there are particular compelling reason why this files needs to be
> > duplicated in all grub-* packages, instead of residing in
> > grub(2)-common?  They are not even different from each other.
> 
> No answer is also an answer.  So there is no real reason.

After a week?  Sometimes people are busy.  Your inference is invalid.

> > Given that it seems like this conflict is the only reason why two
> > variants are not cross-installable.
> 
> Attached is a patch to move the two files to grub2-common.  I intend to
> upload this in a few days.

While I acknowledge that this bug is RC, it isn't an emergency and I
don't think you need to do this.  I will consider your patch but have
been busy on a project at work that has a deadline of Wednesday, so
please hold off as if this patch is wrong it will be complicated to
unwind properly.  I promise I'll look at it ASAP after Wednesday.

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

Bug#911628: python3-websockets: fails to upgrade from 'stretch': SyntaxError: 'yield' inside async function

[Andreas Beckmann]

Package: python3-websockets
Version: 6.0-0.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Setting up python3-websockets (6.0-0.1) ...
File "/usr/lib/python3/dist-packages/websockets/py36/protocol.py", line 15
  yield await self.recv()
  ^
  SyntaxError: 'yield' inside async function
  
  dpkg: error processing package python3-websockets (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


python3-websockets_6.0-0.1.log.gz
Description: application/gzip

Bug#911627: python3-openflow: fails to upgrade from 'stretch': SyntaxError: invalid syntax

[Andreas Beckmann]

Package: python3-openflow
Version: 2017.2b1+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Setting up python3-openflow (2017.2b1+dfsg-2) ...
File "/usr/lib/python3/dist-packages/pyof/foundation/basic_types.py", line 
459
  raise ValueError(f"BinaryData can't be {type(value)} = '{value}'")
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/pyof/v0x01/controller2switch/packet_out.py", 
line 131
  raise ValidationError(f'{self.in_port} is not a valid input port.')
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/pyof/v0x04/common/flow_match.py", line 
356
  raise PackException(f'Match can\'t unpack "{value}".')
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-openflow (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


python3-openflow_2017.2b1+dfsg-2.log.gz
Description: application/gzip

Bug#911626: elpa-vimish-fold: fails to upgrade from 'stretch': vimish-fold.el:59:1:Error: Cannot open load file: No such file or directory, s

[Andreas Beckmann]

Package: elpa-vimish-fold
Version: 0.2.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Setting up elpa-vimish-fold (0.2.3-2) ...
  tsort: -: input contains a loop:
  tsort: s-el
  tsort: emacsen-common
  tsort: -: input contains a loop:
  tsort: dash-el
  tsort: emacsen-common
  Install s-el for emacs24
  install/s-el: Handling install for emacsen flavor emacs24
  Loading 00debian-vars...
  Loading /etc/emacs/site-start.d/50dash-el.el (source)...
  Loading /etc/emacs/site-start.d/50s-el.el (source)...
  Wrote /usr/share/emacs24/site-lisp/s-el/s.elc
  Install dash-el for emacs24
  install/dash-el: Handling install for emacsen flavor emacs24
  Loading 00debian-vars...
  Loading /etc/emacs/site-start.d/50dash-el.el (source)...
  Loading /etc/emacs/site-start.d/50s-el.el (source)...
  Wrote /usr/share/emacs24/site-lisp/dash-el/dash-functional.elc
  Wrote /usr/share/emacs24/site-lisp/dash-el/dash.elc
  Install emacsen-common for emacs24
  emacsen-common: Handling install of emacsen flavor emacs24
  Wrote /etc/emacs24/site-start.d/00debian-vars.elc
  Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
  Install elpa-f for emacs24
  install/f-0.19.0: Handling install of emacsen flavor emacs24
  install/f-0.19.0: byte-compiling for emacs24
  Install elpa-vimish-fold for emacs24
  install/vimish-fold-0.2.3: Handling install of emacsen flavor emacs24
  install/vimish-fold-0.2.3: byte-compiling for emacs24
  
  In toplevel form:
  vimish-fold.el:59:1:Error: Cannot open load file: No such file or directory, s
  ERROR: install script from elpa-vimish-fold package failed
  dpkg: error processing package elpa-vimish-fold (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


elpa-vimish-fold_0.2.3-2.log.gz
Description: application/gzip

Processed: Re: expeyes-web: fails to upgrade from 'stretch': Exception: cannot get content of python3-expeyes

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.4.4+dfsg-3
Bug #910226 {Done: Georges Khaznadar } [expeyes-web] 
expeyes-web: fails to upgrade from 'stretch': Exception: cannot get content of 
python3-expeyes
Marked as found in versions expeyes/4.4.4+dfsg-3; no longer marked as fixed in 
versions expeyes/4.4.4+dfsg-3 and reopened.

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

Bug#910226: expeyes-web: fails to upgrade from 'stretch': Exception: cannot get content of python3-expeyes

[Andreas Beckmann]

Followup-For: Bug #910226
Control: found -1 4.4.4+dfsg-3

The buggy package is *expeyes-web* not python3-expeyes.

And expeyes-web still has the call to
  py3compile -p python3-expeyes
https://salsa.debian.org/georgesk/expeyes/blob/master/debian/expeyes-web.postinst#L68
where python3-expeyes is clearly the wrong package to be given as an
argument (and not being installed at the time of the call).


  Setting up expeyes-web (4.4.4+dfsg-3) ...
  dpkg-query: package 'python3-expeyes' is not installed
  Use dpkg --info (= dpkg-deb --info) to examine archive files,
  and dpkg --contents (= dpkg-deb --contents) to list their contents.
  Traceback (most recent call last):
File "/usr/bin/py3compile", line 290, in 
  main()
File "/usr/bin/py3compile", line 270, in main
  options.force, options.optimize, e_patterns)
File "/usr/bin/py3compile", line 154, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 106, in filter_files
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 53, in from_package
  raise Exception("cannot get content of %s" % package_name)
  Exception: cannot get content of python3-expeyes
  dpkg: error processing package expeyes-web (--configure):
   subprocess installed post-installation script returned error exit status 1


Andreas

Bug#911625: libboost-python1.62.0: insufficient python dependencies allow early upgrade, breaking stretch->buster upgrades

[Andreas Beckmann]

Package: libboost-python1.62.0
Version: 1.62.0+dfsg-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libcasa-measures2

Hi,

during a test with piuparts I noticed your package causes other packages
to fail to upgrade from 'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Setting up casacore-data-tai-utc (1.2) ...
  Traceback (most recent call last):
File "/usr/bin/casacore-update-tai_utc", line 11, in 
  from casacore import tables
File "/usr/lib/python3/dist-packages/casacore/tables/__init__.py", line 60, 
in 
  from .table import table
File "/usr/lib/python3/dist-packages/casacore/tables/table.py", line 44, in 

  from ._tables import Table
  ImportError: libboost_python-py35.so.1.62.0: cannot open shared object file: 
No such file or directory
  dpkg: error processing package casacore-data-tai-utc (--configure):
   subprocess installed post-installation script returned error exit status 1

This is a upgrade test of stretch/amd64 with --install-recommends enabled.
It failed during 'apt-get upgrade'. At the point of failure the following
relevant packages are installed:

# dpkg -l | grep python | cut -c-60
ii  dh-python   3.20180927all   
ii  libboost-python1.62.0   1.62.0+dfsg-10amd64 
ii  libcasa-python3-2:amd64 2.2.0-2   amd64 
ii  libpython3-stdlib:amd64 3.5.3-1   amd64 
ii  libpython3.5:amd64  3.5.3-1   amd64 
ii  libpython3.5-minimal:amd64  3.5.3-1   amd64 
ii  libpython3.5-stdlib:amd64   3.5.3-1   amd64 
ii  python3 3.5.3-1   amd64 
ii  python3-casacore2.1.2-3+b1amd64 
ii  python3-minimal 3.5.3-1   amd64 
ii  python3-numpy   1:1.12.1-3amd64 
ii  python3-pkg-resources   40.2.0-1  all   
ii  python3-six 1.11.0-2  all   
ii  python3.5   3.5.3-1   amd64 
ii  python3.5-minimal   3.5.3-1   amd64

i.e. libboost-python1.62.0 is already upgraded to buster
while python3 is still python3.5 from stretch.

The dependency chain starting from casacore-data-tai-utc looks as follows:

Package: casacore-data-tai-utc
Status: install ok half-configured
Architecture: all
Version: 1.2
Config-Version: 1.1
Depends: python3, python3-casacore, tzdata

Package: python3-casacore
Status: install ok installed
Architecture: amd64
Source: python-casacore (2.1.2-3)
Version: 2.1.2-3+b1
Provides: python3.5-casacore
Depends: python3-numpy, python3-six, python3 (<< 3.6), python3 (>= 3.5~), 
python3-pkg-resources, python3:any (>= 3.4~), libboost-python1.62.0, libc6 (>= 
2.14), libcasa-casa2, libcasa-coordinates2, libcasa-fits2, libcasa-images2, 
libcasa-lattices2, libcasa-measures2, libcasa-mirlib2, libcasa-python3-2, 
libcasa-scimath-f2, libcasa-scimath2, libcasa-tables2, libgcc1 (>= 1:4.0), 
libstdc++6 (>= 5.2)

Package: libboost-python1.62.0
Status: install ok installed
Architecture: amd64
Source: boost1.62
Version: 1.62.0+dfsg-10
Depends: libc6 (>= 2.14), libgcc1 (>= 1:3.0), libstdc++6 (>= 5.2)
Suggests: python, python3


Just an idea, do not know if this can be implemented efficiently:

If libboost-python1.62.0 provides pythonX.Y-libboost-python1.62.0
and the consumers depend on pythonX.Y-libboost-python1.62.0 instead of
(or in addition to) libboost-python1.62.0, everything should be fine.


As a workaround you could add
  Breaks: python3-casacore (<< 2.2.0)
(and probably some more in case I hit them)
to libboost-python1.62.0 (2.2.0-1 was the first version built without 
python3.5 support).
No need to carry this Breaks over to newer boost versions.


cheers,

Andreas


libcasa-measures2_2.4.1-3+b1.log.gz
Description: application/gzip

Processed: libboost-python1.62.0: insufficient python dependencies allow early upgrade, breaking stretch->buster upgrades

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libcasa-measures2
Bug #911625 [libboost-python1.62.0] libboost-python1.62.0: insufficient python 
dependencies allow early upgrade, breaking stretch->buster upgrades
Added indication that 911625 affects libcasa-measures2

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

Bug#909120: camitk FTBFS: tests segfault (Bug #909120)

[Emmanuel Promayon]

Dear all,


I have read that upstream is joining Debian Science to package recent
upstream version VTK8.  I expect that VTK6 will be removed from Debian
soon.  So yes, I'd strongly recommend to follow the stable release cycle
of VTK upstream, which means that porting camitk to VTK7 is necessary
for including camitk into Debian and it is sensible to do some checks
with VTK8 since at some point in time this will be used in Debian.  We
will not be able to support more than two VTK versions in Debian (most
probably only one).
  
Just to let you know about my progress: I finally find some time to try 
to get the current camitk to work with vtk7 and suppress all the 
dependencies to vtk6.

The main problem is due to the necessary change to OpenGL2 backend.
This effort is on a good way thanks to some tweak I found in a post on 
vtk user back in 2016 [1].


To avoid any other potential problem is some other package, should gdcm 
not be set as to conflict with vtk6?



So far for a short note - more details from VTK maintainers ...
I would still love to know more about the progress towards an official 
debian package for vtk8 (or 9 as it seems on its way!).
I found some discussion about vtk7 and vtk8 packages on debian science 
mailing list and kitware blog, but I am not sure I well understood the 
meaning or consequences.


So any idea about the (near) future would be a great help!

Kind regards,
Emmanuel

[1] 
http://vtk.1045678.n5.nabble.com/Find-reason-for-exclusion-of-vtkGUISupportQtOpenGL-in-build-output-td5738976.html

Bug#883731: audacious: Debian packaging has incorrect license

[Andrej Shadura]

Hi,

On Mon, 22 Oct 2018, 20:15 Nicholas D Steeves,  wrote:

> Update
>
> Sorry for my deplorable memory and lack of organisation wrt this bug;
> I committed some initial work and then forgot about it.  Given my work
> schedule for Oct and Nov it is unlikely that I will be able to prevent
> the scheduled autoremoval.  If someone else would like to fix it asap
> please go ahead.  Otherwise I anticipate being able to find the time
> to work on this after the 28th of Nov.
>
> I'll go ahead and file a bug asking for confirmation of the license
> for contributors to debian/*, because this information is not
> contained in old-style copyright format and I'm only familiar with
> machine readable copyright format 1.0
>

I was going to have a look but got distracted by writing kernel drivers —
fascinating stuff :D

I will try and spend some time this week on this. If not, I'll post an
update here.

-- 
Cheers,
  Andrej

>

Bug#899828: marked as done (ibus-m17n: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 18:39:41 +
with message-id 
and subject line Bug#899828: fixed in ibus-m17n 1.3.4-6
has caused the Debian Bug report #899828,
regarding ibus-m17n: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ibus-m17n
Version: 1.3.4-5
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of ibus-m17n,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package ibus-m17n since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ibus-m17n
Source-Version: 1.3.4-6

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated ibus-m17n package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Oct 2018 13:51:44 -0400
Source: ibus-m17n
Binary: ibus-m17n
Architecture: source
Version: 1.3.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 ibus-m17n  - m17n engine for IBus
Closes: 899828
Changes:
 ibus-m17n (1.3.4-6) unstable; urgency=medium
 .
   * Team upload.
   * Modernize packaging instructions.
 + Bump Standards-Version to 4.2.1.
 + Bump debhelper compat to v11.
 - Remove unnecessary autotools build dependencies in debian/control.
 + Update maintainer to Debian Input Method Team. (Closes: #899828)
 + Use "dh_missing --fail-missing" in debian/rules.
 + Slight update to debian/copyright file.
Checksums-Sha1:
 2da1c094a94b6eba5f0e9a5cb144b95c67569dc1 1981 ibus-m17n_1.3.4-6.dsc
 1856f8b085b114a8b1a94fb8bb3c722ea471bfe1 14208 ibus-m17n_1.3.4-6.debian.tar.xz
 5ec550b7de078f0fcd10ae5cc35f00586ff705b1 13964 
ibus-m17n_1.3.4-6_amd64.buildinfo
Checksums-Sha256:
 74e62cde31220b23e65246759f865cae361d99e949a74e606db3f4e14d7a6dc8 1981 
ibus-m17n_1.3.4-6.dsc
 d0b256e49114b1d815cf79ba1df7a8e85b721d6c712ea3e8759276571dffdda1 14208 
ibus-m17n_1.3.4-6.debian.tar.xz
 0c780f328818eb27710efb4d894eb93eb75d4d11fc1b9ef71d55699be9519ec1 13964 

Processed: found 911623 in btrfs-progs/4.17-1

[Debian Bug Tracking System]

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

> found 911623 btrfs-progs/4.17-1
Bug #911623 [src:btrfs-tools] /bin/mkfs.btrfs and /bin/fsck.btrfs are Policy 
and FHS violations
Marked as found in versions btrfs-progs/4.17-1.
> thanks
Stopping processing here.

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

Bug#910959: grub-cloud-amd64: missing Conflicts: grub-coreboot, grub-efi-ia32, grub-ieee1275, grub-xen

[Bastian Blank]

Hi grub maintainers

On Sun, Oct 14, 2018 at 06:40:44PM +0200, Bastian Blank wrote:
> On Sat, Oct 13, 2018 at 09:33:26PM +0200, Andreas Beckmann wrote:
> > Here is a list of files that are known to be shared by both packages
> > (according to the Contents file for sid/amd64, which may be
> > slightly out of sync):
> > 
> > etc/kernel/postinst.d/zz-update-grub
> > etc/kernel/postrm.d/zz-update-grub
> 
> Is there are particular compelling reason why this files needs to be
> duplicated in all grub-* packages, instead of residing in
> grub(2)-common?  They are not even different from each other.

No answer is also an answer.  So there is no real reason.

> Given that it seems like this conflict is the only reason why two
> variants are not cross-installable.

Attached is a patch to move the two files to grub2-common.  I intend to
upload this in a few days.

Bastian

-- 
Where there's no emotion, there's no motive for violence.
-- Spock, "Dagger of the Mind", stardate 2715.1
diff -Nru grub2-2.02+dfsg1/debian/changelog grub2-2.02+dfsg1/debian/changelog
--- grub2-2.02+dfsg1/debian/changelog   2018-08-28 15:17:21.0 +
+++ grub2-2.02+dfsg1/debian/changelog   2018-10-22 15:12:11.0 +
@@ -1,3 +1,11 @@
+grub2 (2.02+dfsg1-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move kernel maintainer script snippets into grub2-common.
+(closes: #910959)
+
+ -- Bastiab Blank   Mon, 22 Oct 2018 15:12:11 +
+
 grub2 (2.02+dfsg1-6) unstable; urgency=medium
 
   * Only build *-signed packages on their native architecture for now, since
diff -Nru grub2-2.02+dfsg1/debian/control grub2-2.02+dfsg1/debian/control
--- grub2-2.02+dfsg1/debian/control 2018-08-28 15:17:05.0 +
+++ grub2-2.02+dfsg1/debian/control 2018-10-22 15:12:11.0 +
@@ -89,9 +89,31 @@
 # of the package is not very useful in a utilities-only build.
 Architecture: any-i386 any-amd64 any-powerpc any-ppc64 any-ppc64el any-sparc 
any-sparc64 any-mipsel any-ia64 any-arm any-arm64
 Depends: grub-common (= ${binary:Version}), dpkg (>= 1.15.4) | install-info, 
${shlibs:Depends}, ${misc:Depends}
-Replaces: grub, grub-legacy, ${legacy-doc-br}, grub-common (<< 1.99-1), 
grub-pc (<< 2.00-4), grub-ieee1275 (<< 2.00-4), grub-efi (<< 1.99-1), 
grub-coreboot (<< 2.00-4), grub-linuxbios (<< 1.99-1), grub-efi-ia32 (<< 
2.00-4), grub-efi-amd64 (<< 2.00-4), grub-efi-ia64 (<< 2.00-4), grub-yeeloong 
(<< 2.00-4)
+Replaces: grub, grub-legacy, ${legacy-doc-br}, grub-common (<< 1.99-1),
+  grub-pc (<< 2.02+dfsg1-6.1),
+  grub-coreboot (<< 2.02+dfsg1-6.1),
+  grub-efi-ia32 (<< 2.02+dfsg1-6.1),
+  grub-efi-amd64 (<< 2.02+dfsg1-6.1),
+  grub-efi-ia64 (<< 2.02+dfsg1-6.1),
+  grub-efi-arm (<< 2.02+dfsg1-6.1),
+  grub-efi-arm64 (<< 2.02+dfsg1-6.1),
+  grub-ieee1275 (<< 2.02+dfsg1-6.1),
+  grub-uboot (<< 2.02+dfsg1-6.1),
+  grub-xen (<< 2.02+dfsg1-6.1),
+  grub-yeeloong (<< 2.02+dfsg1-6.1),
 Conflicts: grub-legacy
-Breaks: grub (<< 0.97-54), ${legacy-doc-br}, shim (<< 
0.9+1474479173.6c180c6-0ubuntu1~)
+Breaks: grub (<< 0.97-54), ${legacy-doc-br}, shim (<< 
0.9+1474479173.6c180c6-0ubuntu1~),
+  grub-pc (<< 2.02+dfsg1-6.1),
+  grub-coreboot (<< 2.02+dfsg1-6.1),
+  grub-efi-ia32 (<< 2.02+dfsg1-6.1),
+  grub-efi-amd64 (<< 2.02+dfsg1-6.1),
+  grub-efi-ia64 (<< 2.02+dfsg1-6.1),
+  grub-efi-arm (<< 2.02+dfsg1-6.1),
+  grub-efi-arm64 (<< 2.02+dfsg1-6.1),
+  grub-ieee1275 (<< 2.02+dfsg1-6.1),
+  grub-uboot (<< 2.02+dfsg1-6.1),
+  grub-xen (<< 2.02+dfsg1-6.1),
+  grub-yeeloong (<< 2.02+dfsg1-6.1),
 Multi-Arch: foreign
 Description: GRand Unified Bootloader (common files for version 2)
  This package contains common files shared by the distinct flavours of GRUB.
diff -Nru grub2-2.02+dfsg1/debian/grub2-common.install 
grub2-2.02+dfsg1/debian/grub2-common.install
--- grub2-2.02+dfsg1/debian/grub2-common.install2018-07-30 
12:32:56.0 +
+++ grub2-2.02+dfsg1/debian/grub2-common.install2018-10-22 
15:12:11.0 +
@@ -1,5 +1,7 @@
 ../../debian/default   usr/share/grub
 ../../debian/update-grub   usr/sbin
+../../debian/kernel/zz-update-grub etc/kernel/postinst.d
+../../debian/kernel/zz-update-grub etc/kernel/postrm.d
 
 usr/sbin/grub-install
 usr/sbin/grub-reboot
diff -Nru grub2-2.02+dfsg1/debian/install.in grub2-2.02+dfsg1/debian/install.in
--- grub2-2.02+dfsg1/debian/install.in  2018-07-30 12:32:56.0 +
+++ grub2-2.02+dfsg1/debian/install.in  2018-10-22 15:12:11.0 +
@@ -1,2 +0,0 @@
-../../debian/kernel/zz-update-grub etc/kernel/postinst.d
-../../debian/kernel/zz-update-grub etc/kernel/postrm.d

Processed: found 911623 in btrfs-progs/4.4.1-1.1

[Debian Bug Tracking System]

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

> found 911623 btrfs-progs/4.4.1-1.1
Bug #911623 [src:btrfs-tools] /bin/mkfs.btrfs and /bin/fsck.btrfs are Policy 
and FHS violations
Marked as found in versions btrfs-progs/4.4.1-1.1.
> thanks
Stopping processing here.

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

Bug#883731: audacious: Debian packaging has incorrect license

[Nicholas D Steeves]

Update

Sorry for my deplorable memory and lack of organisation wrt this bug;
I committed some initial work and then forgot about it.  Given my work
schedule for Oct and Nov it is unlikely that I will be able to prevent
the scheduled autoremoval.  If someone else would like to fix it asap
please go ahead.  Otherwise I anticipate being able to find the time
to work on this after the 28th of Nov.

I'll go ahead and file a bug asking for confirmation of the license
for contributors to debian/*, because this information is not
contained in old-style copyright format and I'm only familiar with
machine readable copyright format 1.0.

Regards,
Nicholas


signature.asc
Description: PGP signature

Processed: affects 911623

[Debian Bug Tracking System]

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

> affects 911623 src:btrfs-progs
Bug #911623 [src:btrfs-tools] /bin/mkfs.btrfs and /bin/fsck.btrfs are Policy 
and FHS violations
Added indication that 911623 affects src:btrfs-progs
> thanks
Stopping processing here.

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

Bug#911623: /bin/mkfs.btrfs and /bin/fsck.btrfs are Policy and FHS violations

[Nicholas D Steeves]

Package: src:btrfs-tools
Version: 4.0-1
Severity: serious
Justification: Debian Policy violation

/bin/mkfs.btrfs and /bin/fsck.btrfs are Policy and FHS violations.

See the "must" directive in Policy §9.1.1 "The location of all files
and directories must comply with the Filesystem Hierarchy Standard
(FHS), version 3.0, with the exceptions noted below, and except where
doing so would violate other terms of Debian Policy."
  https://www.debian.org/doc/debian-policy/ch-opersys.html

Following up in FHS 3.0 §3.16.3 see the following "must" directive: "The
following files, or symbolic links to files, must be in /sbin if the
corresponding subsystem is installed: … fsck.* … mkfs.*"
  https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf

Policy does not make an exception for mkfs.* or fsck.*, therefore both must be 
installed to /sbin (or /usr/sbin on usrmerged systems).


Regards,
Nicholas

Processed: shared-mime-info,gconf2: trigger cycle during upgrade from stretch to buster

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.10-1
Bug #911620 [shared-mime-info,gconf2] shared-mime-info,gconf2: trigger cycle 
during upgrade from stretch to buster
There is no source info for the package 'gconf2' at version '1.10-1' with 
architecture ''
Marked as found in versions shared-mime-info/1.10-1.
> found -1 3.2.6-5
Bug #911620 [shared-mime-info,gconf2] shared-mime-info,gconf2: trigger cycle 
during upgrade from stretch to buster
There is no source info for the package 'shared-mime-info' at version '3.2.6-5' 
with architecture ''
Marked as found in versions gconf/3.2.6-5.
> affects -1 + microhope
Bug #911620 [shared-mime-info,gconf2] shared-mime-info,gconf2: trigger cycle 
during upgrade from stretch to buster
Added indication that 911620 affects microhope

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

Bug#911620: shared-mime-info,gconf2: trigger cycle during upgrade from stretch to buster

[Andreas Beckmann]

Package: shared-mime-info,gconf2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1.10-1
Control: found -1 3.2.6-5
Control: affects -1 + microhope

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails.

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

  Setting up libgl1-mesa-glx:amd64 (18.1.7-1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
shared-mime-info -> gconf2
   packages' pending triggers which are or may be unresolvable:
shared-mime-info: /usr/share/mime/packages
libc-bin: ldconfig
gconf2: /usr/share/gconf/schemas
  dpkg: error processing package shared-mime-info (--configure):
   triggers looping, abandoned


This was observed during a 2-stage upgrade from stretch to buster:
  apt-get upgrade && apt-get dist-upgrade
Both shared-mime-info and gconf2 were already upgraded successfully
during the first stage.
The package being tested was microhope.

IIRC shared-mime-info switched to no-await triggers - so this trigger
cycle problem should have vanished...


cheers,

Andreas


microhope_4.4.4+dfsg-3.log.gz
Description: application/gzip

Processed: Re: Bug#911363: RM: patchelf [mips mipsel] -- ANAIS; Does not work properly

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 RM: patchelf [mips64el] -- ROM; ANAIS; Does not work
Bug #911363 [ftp.debian.org] RM: patchelf [mips mipsel] -- ANAIS; Does not work
Changed Bug title to 'RM: patchelf [mips64el] -- ROM; ANAIS; Does not work' 
from 'RM: patchelf [mips mipsel] -- ANAIS; Does not work'.

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

Bug#911363: RM: patchelf [mips mipsel] -- ANAIS; Does not work properly

[Ivo De Decker]

Control: retitle -1 RM: patchelf [mips64el] -- ROM; ANAIS; Does not work

Hi,

On Sat, Oct 20, 2018 at 09:58:00PM -0300, Felipe Sateler wrote:
> Control: reassign -1 ftp.debian.org
> Control: retitle -1 RM: patchelf [mips mipsel] -- ANAIS; Does not work
> properly
> 
> On Fri, Oct 19, 2018 at 3:39 AM Tobias Frost  wrote:
> > patchelf fails to build on the buildds [1] for mips64el, but previously
> > did.
> > Please note that this impairs migration of your dependencies, so it
> > would be great if an solution can be found, or maybe temporarily remove
> > the mips64el packages to have at least the other release archs.
> >
> 
> Hmm. I wonder why does mips64el have an old binary. This is #821435,  and I
> requested removal on #822211. Maybe mips64el was not an offical arch back
> then?
> 
> Anyway, dear FTP master team, please RM patchelf from mips64el.

The removal on mips and mipsel was done in #822211. This one is about
mips64el. Adjusting the title to make that clear.

Cheers,

Ivo

Bug#911603: evolution-data-server: Postinst script returned error exit status 1 with latest upload

[Bryan Hundven]

Boyuan,

I can reproduce this:
---
bhundven@fuller:~$ sudo apt-get 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.
Setting up evolution-data-server (3.30.2-1) ...
dpkg: error processing package evolution-data-server (--configure):
 installed evolution-data-server package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
 evolution-data-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
---

-Bryan

Bug#911603: evolution-data-server: Postinst script returned error exit status 1 with latest upload

[Felix Zielcke]

On Mon, 22 Oct 2018 09:53:31 -0400 Boyuan Yang 
wrote:
> Package: evolution-data-server
> Severity: serious
> Version: 3.30.2-1
> 
> % LANG=C.UTF-8 sudo apt install -f
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer
required:
>   android-libext4-utils android-libselinux android-libsepol
> Use 'sudo apt autoremove' to remove them.
> 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.
> Setting up evolution-data-server (3.30.2-1) ...
> dpkg: error processing package evolution-data-server (--configure):
>  installed evolution-data-server package post-installation script
> subprocess returned error exit status 1
> Errors were encountered while processing:
>  evolution-data-server
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> If you can't reproduce it, please let me know and I will provide with
> more details.

Hello,

I just got this bug too.
The problem is that update-notifier isn't installed.
The postinst doestn't clear the error from the test command.
I changed the line to
[ -x /usr/share/update-notifier/notify-reboot-required ] && 
/usr/share/update-notifier/notify-reboot-required || true

and it continued without problems.

Regards,
Felix

> --
> Regards,
> Boyuan Yang
> 
> 

Bug#909752: php-apcu-bc 1.0.4-3 : undefined symbol: zif_apcu_store

[Fabrice Régnier]

Package: php-apcu-bc
Version: 1.0.4-3
Severity: serious

Dear Maintainer,

Despite the new version of php-apcu-bc, it seems the error remains in 
/var/log/apache2/error.log


PHP Warning:  PHP Startup: Unable to load dynamic library 'apc.so' 
(tried: /usr/lib/php/20170718/apc.so (/usr/lib/php/20170718/apc.so: 
undefined symbol: zif_apcu_store), /usr/lib/php/20170718/apc.so.so 
(/usr/lib/php/20170718/apc.so.so: cannot open shared object file: No 
such file or directory)) in Unknown on line 0


Before filling this new report bug, i purged php-apcu-bc and php-apcu 
packages and deleted all related files then i reinstalled php-apcu-bc 
and php-apcu.


Fabrice

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

Kernel: Linux 4.18.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php-apcu-bc depends on:
ii  libapache2-mod-php7.2 [phpapi-20170718]  7.2.9-1
ii  libc62.27-6
ii  php-apcu 5.1.12+4.0.11-2
ii  php-common   1:62
ii  php7.2-cli [phpapi-20170718] 7.2.9-1
ii  php7.3-cli [phpapi-20180731] 7.3.0~rc2-2
ii  php7.3-phpdbg [phpapi-20180731]  7.3.0~rc2-2

php-apcu-bc recommends no packages.

php-apcu-bc suggests no packages.

Bug#889906: xcrysden FTBFS with libtogl-dev 2.0-1

[Andreas Tille]

Hi again,

I've got a hint that my wording was misleading:  What I wanted to say
is:  I have caused the current issue inside Debian (and not Anton).  I
just want to help solving the issue and would like to know which way
would be prefered by Anton.

Sorry for the confusion

Andreas.

On Sat, Oct 20, 2018 at 08:17:09AM +0200, Andreas Tille wrote:
> Hi Anton,
> 
> as the person who caused that issue I wonder whether you decided for one
> of the options Daniel has mentioned below and whether you might possibly
> need some help.  I'd personally prefer option 3).
> 
> Please let me know if I could be of any help
> 
>  Andreas.
> 
> On Wed, Feb 21, 2018 at 11:55:33AM +0100, Daniel Leidert wrote:
> > Hi,
> > 
> > you wrote:
> > > On Thu, 2018-02-08 at 18:12 +0200, Adrian Bunk wrote:
> > [..]
> > >> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xc
> > >> rysden.html
> > >>
> > >> ...
> > >> xcAppInit.c: In function 'Xcrys_Init':
> > >> xcAppInit.c:511:5: error: unknown type name 'Togl_CmdProc'
> > >>  Togl_CmdProc *proc;
> > >>  ^~~~
> > >
> > > I suspect the problem may be this: xcrysden should not use the libtogl-
> > > dev, because it uses modified togl sources that are included within its
> > > sources. It should be compiled with that modified togl files instead.
> > 
> > Please read this short policy section about convenience copies:
> > https://www.debian.org/doc/debian-policy/#convenience-copies-of-code
> > 
> > I wasn't aware, that you modified the shipped sources. Did you modify
> > other libary sources as well?
> > 
> > BTW: The mess has been caused by the uncoordinated upload of togl 2.0,
> > which uses a different API then togl version 1.7. Because of this upload,
> > libtogl1 will also disappear soon, making xcrysden not just unbuildable
> > but uninstallable too. There doesn't seem to be any effort by the person(s)
> > responsible for this issue to fix it, which IMO only leaves these choices:
> > 
> > 1) Turn to the Debian release managers and/or the TC to restore togl 1.7.
> > There are pros and cons here and I'm not sure, this works.
> > 
> > 2) Make an exception for xcrysden and build it against the internal copy of
> > togl 1.7. However, in this case it becomes mandatory that you as the
> > upstream author of xcrysden take over complete reponsibility for the copy of
> > togl you ship, including bug fixing. The first step towards this is to apply
> > all bug-fixes included in the last togl 1.7 Debian package into your
> > internal copy and make a new release of xcrysden.
> > 
> > 3) Alternatively you could port xcrysden to togl 2.0 (seems this release is
> > also pretty old, so every modern system could have it). I'd suggest to not
> > modify the togl sources but build custom functions on top of it, if you need
> > modifications or new functionality. If you encounter bugs, pleaes tell us,
> > so this can be fixed in the library package.
> > 
> > 3.1) There is maybe an actively maintained development version 2.1 of togl
> > in the netgen sources. It might work to package this netgen version and
> > create the togl header and library package from this copy and build xcrysden
> > against it. It would require that you choose to use this togl copy.
> > 
> > 4) Last possibility is to remove xcrysden from Debian.
> > 
> > I'd prefer possibility 2) or 3) or 3.1) over 1) or 4).
> > 
> > HTH and regards, Daniel
> > 
> > 
> 
> -- 
> http://fam-tille.de

-- 
http://fam-tille.de

Processed: Re: Bug#909926: multipath-tools: multipath segfaults regularily

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #909926 [multipath-tools] multipath-tools: multipath segfaults regularily
Severity set to 'important' from 'grave'

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

Bug#909926: multipath-tools: multipath segfaults regularily

[Axel Beckert]

Control: severity -1 important

Hi Ritesh,

Ritesh Raj Sarraf wrote:
> Well if it is not something critical in your path, you may want to
> consider lowering the severity of this bug report. And I haven't
> encountered the bug (yet) myself nor have I had any reports.

Granted. Done.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: emacs-common: copyright file missing after upgrade of emacs-nox from stretch

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + emacs-nox
Bug #911616 [emacs-common] emacs-common: copyright file missing after upgrade 
of emacs-nox from stretch
Added indication that 911616 affects emacs-nox

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

Bug#911616: emacs-common: copyright file missing after upgrade of emacs-nox from stretch

[Andreas Beckmann]

Followup-For: Bug #911616
Control: affects -1 + emacs-nox

and the logfile ...


Andreas


emacs-nox_1:25.2+1-11.log.gz
Description: application/gzip

Bug#909926: multipath-tools: multipath segfaults regularily

[Ritesh Raj Sarraf]

Hello Axel,

On Mon, 2018-10-22 at 17:10 +0200, Axel Beckert wrote:
> > I haven't really attempted at reproducing the bug using the odd
> > setup
> > you have described.
> 
> Not sure what you consider odd with that setup. All my multi-card
> card-readers appear as /dev/sd with one letter  for each slot
> (usually CF, SD, MicroSD and some proprietary Sony medium formats).
> 

Sorry. I should have been explicit. It is an odd setup in the context
of Device Mapper Multipath. Usually, a mulitpathed setup is what you
have already explained below. :-)
The common SAN type setups.

> 
> > I will try to spare some time for this bug but meanwhile if you
> > have
> > any additional input/updates, please do update this bug report.
> 
> So far I didn't noticed any new crashes and there were at least no
> new
> crashes in the past week. Then again, I didn't use the card reader
> since then again.
> 
> Will check if it is reproducible the next time I work with SD cards
> on
> that system.

Well if it is not something critical in your path, you may want to
consider lowering the severity of this bug report. And I haven't
encountered the bug (yet) myself nor have I had any reports.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#911616: emacs-common: copyright file missing after upgrade of emacs-nox from stretch

[Andreas Beckmann]

Package: emacs-common
Version: 1:25.2+1-11
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

This was observed on the following upgrade paths:

  stretch -> buster

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

0m37.6s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/share/doc/emacs-common/copyright (from 
emacs-common package)


This does not seem to be the typical dir_to_symlink problem.


cheers,

Andreas

Bug#899546: marked as done (ibus-qt: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 15:35:36 +
with message-id 
and subject line Bug#899546: fixed in ibus-qt 1.3.3-2
has caused the Debian Bug report #899546,
regarding ibus-qt: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ibus-qt
Version: 1.3.3-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of ibus-qt,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package ibus-qt since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ibus-qt
Source-Version: 1.3.3-2

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated ibus-qt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Oct 2018 11:11:58 -0400
Source: ibus-qt
Binary: ibus-qt4 libibus-qt-dev libibus-qt1
Architecture: source
Version: 1.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 ibus-qt4   - qt-immodule for ibus (QT4) (plugin)
 libibus-qt-dev - qt-immodule for ibus (QT4) (development package)
 libibus-qt1 - qt-immodule for ibus (QT4) (library)
Closes: 899546
Changes:
 ibus-qt (1.3.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Rebuild against gcc 8.2.
   * Modernize packaging:
 + Update maintainer and use Debian Input Method Team.
   (Closes: #899546).
 + Bump debhelper compat to v11.
 + Bump Standards-Version to 4.2.1.
 + Apply "wrap-and-sort -abst".
 + Use "dh_missing --fail-missing" in debian/rules.
   * debian/patches: Cherry-pick an upstream patch to fix uninitialized
 variable in src/qibusserializable.cpp.
Checksums-Sha1:
 345880a444f59abf7c3fbee4f9857b16a59745e4 2125 ibus-qt_1.3.3-2.dsc
 ca068e80ac6765d148c0ce0c6eb067bb260a7bb8 4416 ibus-qt_1.3.3-2.debian.tar.xz
 f5650e15b82a711d75f68a219fa6e6e940e3ab3f 10349 ibus-qt_1.3.3-2_amd64.buildinfo
Checksums-Sha256:
 f93359f860c1061436dbb7ab912c2d76a5ab179936372951fe16ffc64015c2b4 2125 
ibus-qt_1.3.3-2.dsc
 

Bug#911444: marked as done (python-flask-httpauth-doc: missing Breaks+Replaces: python-flask-httpauth (<< 3.2.4))

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 15:15:11 +
with message-id 
and subject line Bug#911444: fixed in python-flask-httpauth 3.2.4-2
has caused the Debian Bug report #911444,
regarding python-flask-httpauth-doc: missing Breaks+Replaces: 
python-flask-httpauth (<< 3.2.4)
to be marked as done.

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

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


-- 
911444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-flask-httpauth-doc
Version: 3.2.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../python-flask-httpauth-doc_3.2.4-1_all.deb ...
  Unpacking python-flask-httpauth-doc (3.2.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-flask-httpauth-doc_3.2.4-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/python-flask-httpauth/examples/basic_auth.py', which is also in 
package python-flask-httpauth 3.2.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-flask-httpauth-doc_3.2.4-1_all.deb


cheers,

Andreas


python-flask-httpauth=3.2.1-1_python-flask-httpauth-doc=3.2.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-flask-httpauth
Source-Version: 3.2.4-2

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

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

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated python-flask-httpauth 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 22 Oct 2018 14:42:58 +
Source: python-flask-httpauth
Binary: python-flask-httpauth python3-flask-httpauth python-flask-httpauth-doc
Architecture: source
Version: 3.2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Martín Ferrari 
Changed-By: Martín Ferrari 
Description:
 python-flask-httpauth - Basic and Digest HTTP authentication for Flask (Python 
2)
 python-flask-httpauth-doc - Basic and Digest HTTP authentication for Flask 
(documentation)
 python3-flask-httpauth - Basic and Digest HTTP authentication for Flask 
(Python 3)
Closes: 911444
Changes:
 python-flask-httpauth (3.2.4-2) unstable; urgency=medium
 .
   * debian/control: Add missing Breaks/Replaces to new -doc package.
 Closes: #911444.
Checksums-Sha1:
 e2b0ee05a2191d0b4d50ca1d57104446174175a6 2302 python-flask-httpauth_3.2.4-2.dsc
 1e5de6e86097d27fc9013578a2b115a89882d752 4820 
python-flask-httpauth_3.2.4-2.debian.tar.xz
 92ebc833a63cde20a09f64af6bb45ba50a699805 8506 
python-flask-httpauth_3.2.4-2_amd64.buildinfo
Checksums-Sha256:
 5ee116c4032990be31a0cb9b8bc48a3c9d5ec2df446f13909ddbe7146094bf8b 2302 
python-flask-httpauth_3.2.4-2.dsc
 7a0982007d6e5d34b18edeb18542a17fdbce3d645ff29205894d26d2b465090d 4820 
python-flask-httpauth_3.2.4-2.debian.tar.xz
 33530f46735f81e409fd3480c0f0f1eec9914d32a5bffd26bd20924bcf746dd2 8506 
python-flask-httpauth_3.2.4-2_amd64.buildinfo
Files:
 7630a60dac4a50eff86c5c05a9b57ba5 2302 python optional 
python-flask-httpauth_3.2.4-2.dsc
 39bc9c1cb1217f1301aa501a697dc9d2 4820 python optional 
python-flask-httpauth_3.2.4-2.debian.tar.xz
 2455f4ffeef362e8e0899af6902e619b 8506 python optional 
python-flask-httpauth_3.2.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETe94h3mvRsa9AoOeXdjgv5Gj09oFAlvN4lAACgkQXdjgv5Gj
09o1bA//UotIks32fwLAaNLD+0tBclrOEpHpT7v4T+FkC3biJylGls1bMlVd2Awh
IV8HOyK1hicFyaEpByBHErY+CveFx0kWl7/1j1IaqeXVSqyqwATHvNeuR1JV78xQ
DqQ7cY32J76LTkR2q2uZKWuAczRaGgq1sHk7c1C2mI1j1m2dsB/+QWP536ulKQun
K9L4YvaIODiP63JAUth4iY/g1XWVfizXCMMS7gl0d03mDABC2xwiNiR4AzBAPxi3

Bug#909926: multipath-tools: multipath segfaults regularily

[Axel Beckert]

Hi Ritesh,

Ritesh Raj Sarraf wrote:
> On Sun, 2018-09-30 at 04:01 +0200, Axel Beckert wrote:
> > What I did:
> > 
> > * Remove an SD card from the SD card reader (/dev/sdg), add a MicroSD
> >   card into the MicroSD reader (/dev/sdi).
> > 
> > * Then ran "fdisk -l /dev/sd?" as root.
> > 
> > At that point the above messages appeared in /var/log/syslog.
> > 
> > It seems to happen though rather often. The contents of my
> > /var/crash/0/ (via corekeeper):
> 
> I haven't really attempted at reproducing the bug using the odd setup
> you have described.

Not sure what you consider odd with that setup. All my multi-card
card-readers appear as /dev/sd with one letter  for each slot
(usually CF, SD, MicroSD and some proprietary Sony medium formats).

The card reader in question is a USB 3 one, sitting in a 3.5" slot
originally meant for a 3.5" floppy drive:
https://www.digitec.ch/en/s1/product/delock-91493-usb-30-cardreader-35-4-pin-molex-card-readers-5837471

> I was recently updating my own virtual multipath san setup to the
> latest (0.7.7-3) and did not face any issues.

JFTR: I didn't setup anything explicitly as multipath. multipath-tools
were pulled in as indirect dependency of libblockdev-plugins-all via
libblockdev-mpath2 and something seems to have called that binary
automatically. I actually have no idea what of my setup (workstation
with two RAID1: 2x SSD + 2x HDD; plus card reader and CD/DVD/BR drive)
could be "multipath" at all nor if my vague idea of "multipath" (like
accessing the same iSCSI block device over two different IP addresses)
is even correct.

I first thought the call might have come from udisks2 or so, but I
purged that about two months before the issue happened.

> I will try to spare some time for this bug but meanwhile if you have
> any additional input/updates, please do update this bug report.

So far I didn't noticed any new crashes and there were at least no new
crashes in the past week. Then again, I didn't use the card reader
since then again.

Will check if it is reproducible the next time I work with SD cards on
that system.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#908615: marked as done (pyfai: FTBFS and autopkgtest fails with python3.7 in supported versions)

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 18:13:15 +0300
with message-id <20181022151211.GA25395@localhost>
and subject line Re: Bug#908615: pyfai: FTBFS and autopkgtest fails with 
python3.7 in supported versions
has caused the Debian Bug report #908615,
regarding pyfai: FTBFS and autopkgtest fails with python3.7 in supported 
versions
to be marked as done.

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

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


-- 
908615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyfai
Version: 0.15.0+dfsg1-1
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults

[X-Debbugs-CC set to: debian...@lists.debian.org,
python3-defau...@packages.debian.org]

Dear maintainers,

Since the python3.7 transition started (which added python3.7 to the
supported Python versions) the autopkgtest of pyfai fails in testing
when that autopkgtest is run with the binary packages of
python3-defaults from unstable. It passes when run with only packages
from testing. I copied some of the output at the bottom of this report.
It seems that this failure also causes the package to FTBFS on
reproducible builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyfai.html

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python3-defaults should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

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

Paul

[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyfai/972161/log.gz

autopkgtest [05:07:40]: test python3: [---
=== python3.7 ===
Unable to import pyFAI.ext.splitBBoxLUT for Look-up table based
azimuthal integration
Unable to import pyFAI.ext.splitPixel full pixel splitting: cannot
import name 'splitPixel' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.splitBBox Bounding Box pixel splitting:
cannot import name 'splitBBox' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.histogram Cython histogram implementation:
cannot import name 'histogram' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.splitBBoxCSR CSR based azimuthal integration:
cannot import name 'splitBBoxCSR' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Unable to import pyFAI.ext.splitPixelFullCSR CSR based azimuthal
integration: cannot import name 'splitPixelFullCSR' from 'pyFAI.ext'
(/usr/lib/python3/dist-packages/pyFAI/ext/__init__.py)
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pyFAI/__init__.py", line 73, in tests
res = test.run_tests()
  File "/usr/lib/python3/dist-packages/pyFAI/test/__init__.py", line 59,
in run_tests
if not runner.run(suite()).wasSuccessful():
  File "/usr/lib/python3/dist-packages/pyFAI/test/__init__.py", line 50,
in suite
from . import test_all
  File "/usr/lib/python3/dist-packages/pyFAI/test/test_all.py", line 47,
in 
from . import test_histogram
  File "/usr/lib/python3/dist-packages/pyFAI/test/test_histogram.py",
line 45, in 
from ..ext.histogram import histogram, histogram2d
ModuleNotFoundError: No module named 'pyFAI.ext.histogram'
autopkgtest [05:07:41]: test python3: ---]
autopkgtest [05:10:47]: test python3-dbg: [---
=== python3.7 ===
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't
resolve package from __spec__ or __package__, falling back on __name__
and __path__
  return f(*args, **kwds)
/usr/lib/python3/dist-packages/h5py/_hl/base.py:19: DeprecationWarning:
Using or importing the ABCs from 'collections' instead of from
'collections.abc' is deprecated, and in 3.8 it will stop working
  from collections import (Mapping, MutableMapping, KeysView,
/usr/lib/python3.7/importlib/_bootstrap.py:219: ImportWarning: can't
resolve package from __spec__ or __package__, falling back on __name__
and __path__
  return f(*args, **kwds)
Unable to import pyFAI.ext.splitBBoxLUT for Look-up table based
azimuthal integration
Unable to 

Bug#910935: marked as done (cmake-extras: GMockConfig.cmake doesn't work with googletest/1.8.1-1)

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 15:04:46 +
with message-id 
and subject line Bug#910935: fixed in cmake-extras 1.3+17.04.20170310-4
has caused the Debian Bug report #910935,
regarding cmake-extras: GMockConfig.cmake doesn't work with googletest/1.8.1-1
to be marked as done.

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

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


-- 
910935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cmake-extras
Severity: serious
Control: affects -1 googletest

Dear Maintainer,

GMockConfig.cmake doesn't work with googletest/1.8.1-1 in sid.
I'm not sure whether it's bug in googletest or not.

Take ayatana-indicator-power for example, it depends gmock_main target
from GMockConfig.cmake. It will ftbfs with,

cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/test-device.dir/link.txt --verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++11  -Wall -Wextra -Wpedantic -Wformat=2 
-Wno-missing-field-initializers -Wno-weak-vtables -Wno-global-constructors  
-Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/test-device.dir/test-device.cc.o  
-o test-device ../src/libayatanaindicatorpowerservice.a -ldbustest -lglib-2.0 
-lgio-2.0 -lnotify -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 
-lgio-2.0 -lnotify -lgdk_pixbuf-2.0 -lgobject-2.0 gmock/gtest/libgtest.a 
-lpthread gmock/libgmock.a gmock/libgmock_main.a 
/usr/bin/ld: gmock/libgmock_main.a(gmock_main.cc.o): in function `main':
/usr/src/googletest/googlemock/src/gmock_main.cc:52: undefined reference to 
`testing::InitGoogleMock(int*, char**)'


Following is workaround for it, but I'm not expert in cmake...

--- src/GMock/GMockConfig.cmake.orig2018-10-13 23:01:36.681319674 +0800
+++ src/GMock/GMockConfig.cmake 2018-10-13 23:01:54.405374263 +0800
@@ -77,7 +77,7 @@
 
 add_library(gmock_main INTERFACE)
 target_include_directories(gmock_main INTERFACE ${GMOCK_INCLUDE_DIRS})
-target_link_libraries(gmock_main INTERFACE ${findgmock_gmock_main_lib} gmock)
+target_link_libraries(gmock_main INTERFACE ${findgmock_gmock_main_lib} gmock 
gtest_main)
 
 set(GTEST_LIBRARIES gtest)
 set(GTEST_MAIN_LIBRARIES gtest_main)

 -- 
 Shengjing Zhu
--- End Message ---
--- Begin Message ---
Source: cmake-extras
Source-Version: 1.3+17.04.20170310-4

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

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

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated cmake-extras package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 22 Oct 2018 16:40:48 +0200
Source: cmake-extras
Binary: cmake-extras
Architecture: source
Version: 1.3+17.04.20170310-4
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel 
Changed-By: Mike Gabriel 
Description:
 cmake-extras - Extra CMake utility modules
Closes: 910935
Changes:
 cmake-extras (1.3+17.04.20170310-4) unstable; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * debian/control:
 + Use new python-clang metapackage to bring always the latest version
 + Fixup VCS URL.
 .
   [ Mike Gabriel ]
   * debian/control:
 + Update Section: to devel.
 + Bump Standards-Version: to 4.2.1. No changes needed.
   * debian/patches:
 + Add 1002_fix-googletest-1_8_1-1.patch. Make GMockConfig.cmake work with
   googletest/1.8.1-1. (Closes: #910935).
   + debian/rules:
 + Drop unneeded DH argument --parallel.
Checksums-Sha1:
 a1d201b3b0568455c7496f097167e3cf346c1880 2411 
cmake-extras_1.3+17.04.20170310-4.dsc
 9235747a20e21d76a13a0060dbb07f87a75b13f5 10600 
cmake-extras_1.3+17.04.20170310-4.debian.tar.xz
 bebfe926055e9bc11b605a653dff6a7a7510e4c6 7298 
cmake-extras_1.3+17.04.20170310-4_source.buildinfo
Checksums-Sha256:
 946c6f806ba40a7c383ab27ab75826eed8631964be61ad12ef1a50d320119286 2411 
cmake-extras_1.3+17.04.20170310-4.dsc
 2a4bde472474ef4638cd07ec1e1dd056e12eb6925f861a44c93adab5029fa1d4 10600 
cmake-extras_1.3+17.04.20170310-4.debian.tar.xz
 

Bug#911615: FTBFS: superlu_dist.c:701:25: error: 'LargeDiag' was not declared in this scope

[Gilles Filippini]

Source: petsc
Version: 3.9.4+dfsg1-1
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

petsc FTBFS on unstable with:
/<>/src/mat/impls/aij/mpi/superlu_dist/superlu_dist.c: In function 
'PetscErrorCode MatGetFactor_aij_superlu_dist(Mat, MatFactorType, _p_Mat**)':   
  
/<>/src/mat/impls/aij/mpi/superlu_dist/superlu_dist.c:701:25: 
error: 'LargeDiag' was not declared in this scope   
   
   options.RowPerm = LargeDiag; 

  
 ^  

  
/<>/src/mat/impls/aij/mpi/superlu_dist/superlu_dist.c:701:25: 
note: suggested alternative: 'LargeDiag_AWPM'   
   
   options.RowPerm = LargeDiag; 

  
 ^  

  
 LargeDiag_AWPM 

  
make[4]: *** [gmakefile:150: 
x86_64-linux-gnu-real-debug/obj/mat/impls/aij/mpi/superlu_dist/superlu_dist.o] 
Error 1 
  
make[4]: Leaving directory '/<>'
make[4]: *** Waiting for unfinished jobs

  

Thanks,

_g.

- -- System Information:
Distributor ID: PureOS
Description:PureOS GNU/Linux 8
Release:8
Codename:   green
Architecture: x86_64

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlvN5nQACgkQ7+hsbH/+
z4Ndcwf/YW+yWbV6CNcnGAsklkVXpIM5ee8+xePd2tWi33duxJnBFAAFJvylsJNP
PCjBoF/0JXuZoonu1JvDHWpGeIXvvvJiUQnyX5L9loqGKxH4PR0pvq/gEx7zuG6E
gCjuJcWDR4rdoiMZOrH/kXJlVGrfcRcsHaUPbIC4LECSpULVLjgRi7eBMIZj5jlM
D2mlcNlNXNjH3L8F2pdBWgl/Sf7r2F4JzoynV0az7nr9BEKD25LT1Ix8CRToSdZW
Q7C1Zj+mekIPIi4X4ttbTjI2PD4TwVVAD5+JRLogIcm7FBlWDZaVh4DY5N8bipLG
tiAtWu3Sm1DHx4Q6LjGGCrCFxeTBPw==
=rMSf
-END PGP SIGNATURE-

Bug#911610: eldav: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/eldav/{,vc-}eldav.el

[Andreas Beckmann]

Package: eldav
Version: 0.8.1-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
were installed by this package.

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

1m7.9s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/share/emacs/site-lisp/eldav/eldav.el (from eldav 
package)
  debsums: missing file /usr/share/emacs/site-lisp/eldav/vc-eldav.el (from 
eldav package)


cheers,

Andreas


eldav_0.8.1-10.log.gz
Description: application/gzip

Bug#911612: tdiary-mode: files missing after upgrade from stretch: /usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el

[Andreas Beckmann]

Package: tdiary-mode
Version: 5.0.10-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
were installed by this package.

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

0m59.2s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/share/emacs/site-lisp/tdiary-mode/http.el (from 
tdiary-mode package)
  debsums: missing file /usr/share/emacs/site-lisp/tdiary-mode/tdiary-mode.el 
(from tdiary-mode package)


cheers,

Andreas


tdiary-mode_5.0.10-1.log.gz
Description: application/gzip

Bug#910935: Bug #910935 in cmake-extras marked as pending

[Mike Gabriel]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-ayatana-team/cmake-extras/commit/f5a8d9b106830cfcd51064bf580226263bbbfb78


debian/patches: Add 1002_fix-googletest-1_8_1-1.patch. Make GMockConfig.cmake 
work with googletest/1.8.1-1. (Closes: #910935).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/910935

Processed: Bug #910935 in cmake-extras marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #910935 [cmake-extras] cmake-extras: GMockConfig.cmake doesn't work with 
googletest/1.8.1-1
Added tag(s) pending.

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

Bug#909926: multipath-tools: multipath segfaults regularily

[Ritesh Raj Sarraf]

Hello,

On Sun, 2018-09-30 at 04:01 +0200, Axel Beckert wrote:
> What I did:
> 
> * Remove an SD card from the SD card reader (/dev/sdg), add a MicroSD
>   card into the MicroSD reader (/dev/sdi).
> 
> * Then ran "fdisk -l /dev/sd?" as root.
> 
> At that point the above messages appeared in /var/log/syslog.
> 
> It seems to happen though rather often. The contents of my
> /var/crash/0/
> (via corekeeper):

I haven't really attempted at reproducing the bug using the odd setup
you have described. Nevertheless, the crash should not happen and needs
to be investigated.

I was recently updating my own virtual multipath san setup to the
latest (0.7.7-3) and did not face any issues.

I will try to spare some time for this bug but meanwhile if you have
any additional input/updates, please do update this bug report.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#911444: python-flask-httpauth-doc: missing Breaks+Replaces: python-flask-httpauth (<< 3.2.4)

[Martín Ferrari]

Hi Andreas,

On 20/10/18 10:09, Andreas Beckmann wrote:

> It installed fine in 'stretch', then the upgrade to 'buster' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

Ahh, I totally missed that. Thanks for reporting, will fix asap!


-- 
Martín Ferrari (Tincho)

Bug#911606: jitterentropy-rngd: Does not automatically start with sysvinit or openrc due to missing init.d script

[Axel Beckert]

Package: jitterentropy-rngd
Version: 1.0.8-2
Severity: serious
Justification: Policy 9.11

Shipping a systemd unit without a corresponding init script is
forbidden by Debian Policy 9.11:

> However, any package integrating with other init systems must also
> be backwards-compatible with sysvinit by providing a SysV-style init
> script with the same name as and equivalent functionality to any
> init-specific job

The jitterentropy-rngd package contains
/lib/systemd/system/jitterentropy.service but no init script.

Accordingly the package does not work with a different init system
than systemd.

So please add an init script.

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (300, 'unstable'), 
(299, 'unstable-debug'), (210, 'experimental'), (209, 'experimental-debug'), 
(110, 'buildd-unstable'), (105, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages jitterentropy-rngd depends on:
ii  libc6  2.27-6

jitterentropy-rngd recommends no packages.

jitterentropy-rngd suggests no packages.

-- no debconf information

Bug#907518: New libssl1.1 1.1.1~~pre9-1 in unstable breaks connecting to some wifi networks

[Yuri D'Elia]

Package: wpasupplicant
Version: 2:2.7~git20181004+1dd66fc-1
Followup-For: Bug #907518

wpasupplicant should accept a tls MinVersion parameter to be specified
per-network. Nobody wants to adjust the global setting just to connect
to an outdated system.

As pointed out, I also spotted this while trying to connect to eduroam.
I raised the issue to the local admin, but meanwhile I had no choice but
to lower the MinVersion for everything else in the system too.

With per-ssid settings, I could actually set even stricter
requirements for my own networks, which would be a big plus.

-- 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.19.0-rc7-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 wpasupplicant depends on:
ii  adduser   3.118
ii  libc6 2.27-6
ii  libdbus-1-3   1.12.10-1
ii  libnl-3-200   3.4.0-1
ii  libnl-genl-3-200  3.4.0-1
ii  libpcsclite1  1.8.24-1
ii  libreadline7  7.0-5
ii  libssl1.1 1.1.1-1
ii  lsb-base  9.20170808

wpasupplicant recommends no packages.

Versions of packages wpasupplicant suggests:
pn  libengine-pkcs11-openssl  
ii  wpagui2:2.6-18

Bug#907806: marked as done (scikit-learn: FTBFS in buster/sid (could not import 'distributed'))

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 13:53:37 +
with message-id 
and subject line Bug#907806: fixed in scikit-learn 0.20.0+dfsg-1
has caused the Debian Bug report #907806,
regarding scikit-learn: FTBFS in buster/sid (could not import 'distributed')
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
 debian/rules build-indep
py3versions: no X-Python3-Version in control file, using supported versions
py3versions: no X-Python3-Version in control file, using supported versions
: # Explicit build system to avoid use of all-in-1 Makefile
dh build-indep --buildsystem=python_distutils --with python2,python3,autoreconf
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
py3versions: no X-Python3-Version in control file, using supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh_autoreconf debian/rules -- clean_generated
make[2]: Entering directory '/<>'
py3versions: no X-Python3-Version in control file, using supported versions
py3versions: no X-Python3-Version in control file, using supported versions

[... snipped ...]

raise Skipped("could not import %r" % (modname,), allow_module_level=True)
Skipped: could not import 'distributed'

==
ERROR: sklearn.tests.test_common.test_import_all_consistency
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py",
 line 291, in wrapper
return fn(*args, **kwargs)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/tests/test_common.py",
 line 131, in test_import_all_consistency
package = __import__(modname, fromlist="dummy")
  File "/usr/lib/python2.7/dist-packages/joblib/test/test_dask.py", line 12, in 

distributed = pytest.importorskip('distributed')
  File "/usr/lib/python2.7/dist-packages/_pytest/outcomes.py", line 138, in 
importorskip
raise Skipped("could not import %r" % (modname,), allow_module_level=True)
Skipped: could not import 'distributed'

==
ERROR: sklearn.tests.test_docstring_parameters.test_tabs
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/utils/testing.py",
 line 291, in wrapper
return fn(*args, **kwargs)
  File 
"/<>/debian/tmp/usr/lib/python2.7/dist-packages/sklearn/tests/test_docstring_parameters.py",
 line 143, in test_tabs
mod = importlib.import_module(modname)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/usr/lib/python2.7/dist-packages/joblib/test/test_dask.py", line 12, in 

distributed = pytest.importorskip('distributed')
  File "/usr/lib/python2.7/dist-packages/_pytest/outcomes.py", line 138, in 
importorskip
raise Skipped("could not import %r" % (modname,), allow_module_level=True)
Skipped: could not import 'distributed'

--
Ran 3895 tests in 169.771s

FAILED (SKIP=19, errors=6)
make[1]: *** [debian/rules:89: python-test2.7] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:42: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


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

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

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

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

Thanks.
--- End Message ---

Bug#905191: marked as done (libecm1-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 13:50:36 +
with message-id 
and subject line Bug#905191: fixed in gmp-ecm 7.0.4+ds-4
has caused the Debian Bug report #905191,
regarding libecm1-dev: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
to be marked as done.

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

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


-- 
905191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libecm1-dev
Version: 7.0.4+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m29.3s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libecm1-dev/AUTHORS (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/AUTHORS (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/NEWS.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/NEWS.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/README.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/README.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/README.lib.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/README.lib.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/changelog.Debian.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/changelog.Debian.gz (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/changelog.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/changelog.gz (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/copyright (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/copyright (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples/Makefile (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples/Makefile (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples/ecmfactor.c (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples/ecmfactor.c (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common


cheers,

Andreas


libecm1-dev_7.0.4+ds-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gmp-ecm
Source-Version: 7.0.4+ds-4

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

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

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated 

Bug#911603: evolution-data-server: Postinst script returned error exit status 1 with latest upload

[Boyuan Yang]

Package: evolution-data-server
Severity: serious
Version: 3.30.2-1

% LANG=C.UTF-8 sudo apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  android-libext4-utils android-libselinux android-libsepol
Use 'sudo apt autoremove' to remove them.
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.
Setting up evolution-data-server (3.30.2-1) ...
dpkg: error processing package evolution-data-server (--configure):
 installed evolution-data-server package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
 evolution-data-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

If you can't reproduce it, please let me know and I will provide with
more details.

--
Regards,
Boyuan Yang

Bug#885667: marked as done (krb5-auth-dialog: Please drop Build-Depends on rarian-compat)

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 13:38:05 +
with message-id 
and subject line Bug#885667: fixed in krb5-auth-dialog 3.26.1-2
has caused the Debian Bug report #885667,
regarding krb5-auth-dialog: Please drop Build-Depends on rarian-compat
to be marked as done.

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

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


-- 
885667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: krb5-auth-dialog
Version: 3.12.0-2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs rarian
Tags: sid buster

scrollkeeper has been deprecated and unmaintained for years. Its
replacement, rarian has been deprecated for years too. More
importantly, it doesn't seem to be needed at all. yelp can easily
display Docbook help files without any .omf files.

We do not intend to ship rarian in Debian 10 "Buster". Therefore,
please drop rarian-compat from krb5-auth-dialog's Build-Depends.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: krb5-auth-dialog
Source-Version: 3.26.1-2

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

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

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated krb5-auth-dialog package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 22 Oct 2018 14:38:39 +0200
Source: krb5-auth-dialog
Binary: krb5-auth-dialog
Architecture: source
Version: 3.26.1-2
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Description:
 krb5-auth-dialog - tray applet for reauthenticating kerberos tickets
Closes: 885667
Changes:
 krb5-auth-dialog (3.26.1-2) unstable; urgency=medium
 .
   * Drop unneeded rarian-compat build-dependency (Closes: #885667)
   * Bump standards version no changes needed
Checksums-Sha1:
 dbf3eaa743dac20f07b6c5c1f8345122e667b988 2202 krb5-auth-dialog_3.26.1-2.dsc
 59752b44bc946f456093819d6c0f1c2a0ea42bdc 6168 
krb5-auth-dialog_3.26.1-2.debian.tar.xz
 9e717740e7891d4a87d91056d79cc07213a1c71c 16002 
krb5-auth-dialog_3.26.1-2_amd64.buildinfo
Checksums-Sha256:
 a168bd3d07a6a3c2504bd5d50e53025d33121bd29490a1bf9e6f6c346cada016 2202 
krb5-auth-dialog_3.26.1-2.dsc
 2434748aa711ed4c3689b3aae82f1a48fb652f3a7c845c92292ab0a953a2dd02 6168 
krb5-auth-dialog_3.26.1-2.debian.tar.xz
 072b4b99323065298eac5a9a630efbc95f38bdcf357180c2ecba99e00070d643 16002 
krb5-auth-dialog_3.26.1-2_amd64.buildinfo
Files:
 b247ef816861d1c351ff8fa85e2b62da 2202 gnome optional 
krb5-auth-dialog_3.26.1-2.dsc
 ce3bcbc7c2296dfa16dc46786f3b17fd 6168 gnome optional 
krb5-auth-dialog_3.26.1-2.debian.tar.xz
 17c043e5e6cad21bd13ff47fe928e043 16002 gnome optional 
krb5-auth-dialog_3.26.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEvHzQcjh1660F3xzZB7i3sOqYEgsFAlvNzKsACgkQB7i3sOqY
EgvHxxAAozJnuZ2zvB3bIUY203erObD204wIzyehsoW9cHHJFcKC9tPfD6vXEC94
6HYknUigHjYC5+6UaOj/5VPvOBHcluTwZAVocFNcxMrQXgIJuIzA5nVLZ7vmz9ck
m8NOH49m0Z+gUOvplbKs7eEzzpkZz3zPXjn7FLsGHJATPYIf7R7+sUr5rHZx1moj
D/t99J7u41eif402G/fX1as5E6XAzdQLjpOuBKdHmBqmSL8IEy63TdP/c0gJSRhE
iN79APzi64ZScr0n/TuozQZU1rwLm3/ThIi2Iczbdny5bkoVToc5pp7Wa1LnontM
Hf1uuc2zSaE65r2w65061cI5HeVbWa2xbexuQpc56b649S0WP9EvP5hkyWeMDTxv
h8Quk/R0W0Feop3/uLyC0XRSTQTo7g9mGwL8UmvEKN6lZcL0rAs40ck6CEYYyUQ2
Z3heGO1X8cLzem55TXKHHCjQcXSqaBY+RcDtHPzgoxz1ARPdBT28oiJ8omPxWZfO
wYz2mXA6bdu3+86qgXBtgi/FAFAJ4tD0pF0rI345KI12mT0BuvURnbuCPDja67jw
laIeO7FEWuIJQtupHJ6x5ZDK0bX2eF8WoAfDEr5duuYIKdHJBKKOsV3CYXA5rbFy
x2a5P1JNl2qgc7sEBv62pIpiClWoFNAgcI9xrAsTfjuT1gFo9VI=
=PujF
-END PGP SIGNATURE End Message ---

Bug#885667: krb5-auth-dialog: Please drop Build-Depends on rarian-compat

[Guido Günther]

Hi,
On Mon, Oct 22, 2018 at 08:35:26AM -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
> 
> Guido, could you upload this fix now?

Completely forgot about that one, uploaded now.
 -- Guido

Bug#909985: marked as done (ceilometer: FTBFS (Failed to import test module))

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 15:11:33 +0200
with message-id 
and subject line closing this bug
has caused the Debian Bug report #909985,
regarding ceilometer: FTBFS (Failed to import test module)
to be marked as done.

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

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


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

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep  --with python3,systemd,sphinxdoc
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
dh_auto_configure: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_configure: This feature will be removed in compat 12.
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

+ TEST_PARALLEL_OPT=--parallel
+ PKGOS_USE_PY2=no
+ shift
+ [ no = yes ]
+ [ yes = yes ]
+ py3versions -vr
+ PYTHON3S=3.6
+ [ yes = no ]
+ [ disabled = disabled ]
+ continue
+ [ 3.6 = disabled ]
+ cut -d. -f1
+ echo 3.6
+ PYMAJOR=3
+ echo ===> Testing with python (python3)
===> Testing with python (python3)
+ [ 3 = 3 ]
+ pwd
+ [ -d /<>/debian/tmp/usr/lib/python3/dist-packages ]
+ [ -z /<>/debian/tmp/usr/lib/python3/dist-packages ]
+ [ -e .stestr.conf ]
+ rm -rf .stestr
+ subunit2pyunit
+ PYTHON=python3.6 python3-stestr run --subunit 
tests\.(?!(.*test_bin.*|.*functional.*|.*gabbi\.test_gabbi_prefix.*|.*meter\.test_notifications\.TestMeterProcessing\.test_fallback_meter_path.*|.*agent\.test_manager\.TestRunTasks\.test_batching_polled_samples_false.*))

=
Failures during discovery
=
b'--- import errors ---\nFailed to import test module: 
ceilometer.tests.unit.hardware.inspector.test_snmp\nTraceback (most recent call 
last):\n  File "/usr/lib/python3/dist-packages/unittest2/loader.py", line 456, 
in _find_test_path\nmodule = self._get_module_from_name(name)\n  File 
"/usr/lib/python3/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name\n__import__(name)\n  File 
"/<>/ceilometer/tests/unit/hardware/inspector/test_snmp.py", line 
23, in \nfrom ceilometer.hardware.inspector import snmp\n  File 
"/<>/ceilometer/hardware/inspector/snmp.py", line 21, in 
\nfrom pysnmp.entity.rfc3413.oneliner import 
cmdgen\nModuleNotFoundError: No module named 
\'pysnmp.entity.rfc3413.oneliner\'\n'

The above traceback was encountered during test discovery which imports all the 
found test modules in the specified test_path.

--
Ran 0 tests in 1.567s

OK
+ python3-stestr slowest
+ clean_exit /tmp/CEILO-MONGODB-drAOR
+ local error_code=3
+ rm -rf /tmp/CEILO-MONGODB-drAOR
++ jobs -p
+ kill 11332 11374
+ return 3
make[1]: *** [debian/rules:32: override_dh_install] Error 3
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


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

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

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Looks like this bug needs to be closed then.--- End Message ---

Processed: Re: Bug#911090: libapt-pkg5.0: incompatible with apt/stretch

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #911599 [g++-8] g++-8: removal of old abi mangling breaks compatibility 
with stretch
Severity set to 'important' from 'serious'
> tags -1 + moreinfo
Bug #911599 [g++-8] g++-8: removal of old abi mangling breaks compatibility 
with stretch
Added tag(s) moreinfo.

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

Bug#911599: Bug#911090: libapt-pkg5.0: incompatible with apt/stretch

[Matthias Klose]

Control: severity -1 important
Control: tags -1 + moreinfo

The compat symbol was in GCC 7, and then removed in GCC 8. Sure, that doesn't
help with the distro upgrade.  There is nothing in GCC to change, so if you want
to fix that, you need a rename of the affected library packages.

Bug#909000: Enigmail 2.0 needed in Stretch after Thunderbird 60 upload

[Paul van der Vlis]

Op 22-10-18 om 14:28 schreef Fabián Rodríguez:

> For now the only workaround seems to be manual installation via
> Thunderbird's addons.

No, see my earlier message in this bug with the title "workarround".
Works fine for me.

With regards,
Paul van der Vlis

-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Bug#911600: netsurf: Please use pkg-config to find FreeType 2

[Hugh McMaster]

Source: netsurf
Severity: serious

Dear maintainer,

Freetype 2.9.1-2 has been in experimental for three weeks now. As it is working 
well, I have decided to upload the package to unstable within the next two to 
three weeks.

A rebuild of your package with freetype 2.9.1 installed confirmed that your 
package will FTBFS once the new version of freetype enters unstable. The build 
failure was caused by the freetype libraries not being detected, as 
freetype-config is not shipped in 2.9.1.

Given the build failure and upcoming upload of freetype 2.9.1, I have set the 
severity of this bug to Serious.

Please use pkg-config to detect freetype.

Thank you

Processed: Re: Bug#911090: libapt-pkg5.0: incompatible with apt/stretch

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #911090 [libapt-pkg5.0] libapt-pkg5.0: incompatible with apt/stretch
Bug 911090 cloned as bug 911599
> reassign -2 g++-8
Bug #911599 [libapt-pkg5.0] libapt-pkg5.0: incompatible with apt/stretch
Bug reassigned from package 'libapt-pkg5.0' to 'g++-8'.
No longer marked as found in versions apt/1.7.0.
Ignoring request to alter fixed versions of bug #911599 to the same values 
previously set
> retitle -2 g++-8: removal of old abi mangling breaks compatibility with 
> stretch
Bug #911599 [g++-8] libapt-pkg5.0: incompatible with apt/stretch
Changed Bug title to 'g++-8: removal of old abi mangling breaks compatibility 
with stretch' from 'libapt-pkg5.0: incompatible with apt/stretch'.

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

Bug#911090: libapt-pkg5.0: incompatible with apt/stretch

[Andreas Beckmann]

Control: clone -1 -2
Control: reassign -2 g++-8
Control: retitle -2 g++-8: removal of old abi mangling breaks compatibility 
with stretch

On 2018-10-15 18:18, Julian Andres Klode wrote:
> So, I think this affects more than just apt. gcc 7 broke the ABI
> by adding a new mangling
> 
>   URI::operator std::__cxx11::basic_string, 
> std::allocator >()
> 
> and only linking to that. It seems that some new gcc version then
> got rid of the old one
> 
>   URI::operator std::__cxx11::basic_string, 
> std::allocator >[abi:cxx11]()
> 
> and now it's crashing.
> 
> And that's a problem for _every_ library with operator string(), not
> just apt.

Andreas

Processed: Re: krb5-auth-dialog: Please drop Build-Depends on rarian-compat

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885667 [src:krb5-auth-dialog] krb5-auth-dialog: Please drop Build-Depends 
on rarian-compat
Severity set to 'serious' from 'important'

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

Processed: Re: gbonds: Please drop Build-Depends on rarian-compat

[Debian Bug Tracking System]

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

> severity 885638 serious
Bug #885638 [src:gbonds] gbonds: Please drop Build-Depends on rarian-compat
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#909000: Enigmail 2.0 needed in Stretch after Thunderbird 60 upload

[Fabián Rodríguez]

This also fails in a clean Stretch install:

# apt install enigmail
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 enigmail : Depends: thunderbird (>= 1:52.0) but it is not going to be 
installed or

 icedove (>= 1:52.0)
E: Unable to correct problems, you have held broken packages.

For now the only workaround seems to be manual installation via 
Thunderbird's addons.

Bug#910964: libprotobuf17 might need Breaks: libprotobuf10

[Pirate Praveen]

On Sat, 20 Oct 2018 11:36:55 +0200
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?=  wrote:
> 2) Packages that depend on each other, need to be compiled with the
> same ProtoBuf version. This should be expressed in those package
> dependencies.

You might want to comment here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900429#36

> 3) Self-tests need fixing, this is clear.

Now there is only a warning, it can be fixed by adding Restrictions:
allow-stderr in debian/tests/control.



signature.asc
Description: OpenPGP digital signature

Bug#910964: libprotobuf17 might need Breaks: libprotobuf10

[Pirate Praveen]

On Sun, 21 Oct 2018 13:27:52 +0530 Pirate Praveen
 wrote:
> I have also asked upstream for support here
> https://github.com/protocolbuffers/protobuf/issues/5276 there is already
> one person assigned to it.
> 

Upstream confirmed it is debian specific and it seems this should be
merged with #911404.



signature.asc
Description: OpenPGP digital signature

Bug#896727: marked as done (gmailieer: missing build dependency on dh-python)

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 11:51:12 +
with message-id 
and subject line Bug#896727: fixed in gmailieer 0.10-1
has caused the Debian Bug report #896727,
regarding gmailieer: missing build dependency on dh-python
to be marked as done.

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

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


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

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

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

make: *** [debian/rules:6: clean] Error 2
--- End Message ---
--- Begin Message ---
Source: gmailieer
Source-Version: 0.10-1

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

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

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

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated gmailieer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 22 Oct 2018 13:26:44 +0200
Source: gmailieer
Binary: gmailieer
Architecture: source
Version: 0.10-1
Distribution: unstable
Urgency: medium
Maintainer: Julian Andres Klode 
Changed-By: Julian Andres Klode 
Description:
 gmailieer  - Fast fetch and two-way tag synchronization between notmuch and GM
Closes: 896727
Changes:
 gmailieer (0.10-1) unstable; urgency=medium
 .
   * New upstream version; highlights:
 - only allow one instance of gmi for each directory using fcntl.lockf()
 - allows syncing categories (personal, social, etc)
 - various improvements in batch sizing
 - do not use progressbar if not tty
 .
 gmailieer (0.6-1.1) unstable; urgency=medium
 .
   * Add build dependency on dh-python (Closes: #896727)
   * Bump to debhelper 11
   * Bump policy, no changes required
   * Non-maintainer upload.
Checksums-Sha1:
 7ffd6190cbcef2d9c07e4f01c0225cb8082d910a 1963 gmailieer_0.10-1.dsc
 4b667bb108fff9e706f0f7270c27d4b07aa57143 79346 gmailieer_0.10.orig.tar.gz
 0a8a7e80c066f5874825a4be2e17ff68ff653c34 2164 gmailieer_0.10-1.debian.tar.xz
 b365dda343f161098036938b617800a9f39a62fd 7406 gmailieer_0.10-1_source.buildinfo
Checksums-Sha256:
 7ec33a96c7f88d8d21fa1607e279f3ce6e88c048abb301124154d49795dfa23b 1963 
gmailieer_0.10-1.dsc
 7dc592f59abdd06694a704e1afbc572a55cedb4203fd6af7d7627540f8e28ef2 79346 
gmailieer_0.10.orig.tar.gz
 6b9dd9271c2cfd0ddfddc10ffa7222c3d519726c9aa7c44f97d9dd0fed84c3f6 2164 
gmailieer_0.10-1.debian.tar.xz
 ec28a67c6dc3faa9d3c3ccbba9a32d1527ab324f7468bf691078738704f2bfcd 7406 
gmailieer_0.10-1_source.buildinfo
Files:
 c3141a060288931c31bccaf15e829bf9 1963 mail optional gmailieer_0.10-1.dsc
 99e62b34472f2c34f5b73eaf3c426a28 79346 mail optional gmailieer_0.10.orig.tar.gz
 764c175401be71f92076658840dc096a 2164 mail optional 
gmailieer_0.10-1.debian.tar.xz
 f7bc284303f3fa12e1eb73af776fd8cc 7406 mail optional 
gmailieer_0.10-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEET7WIqEwt3nmnTHeHb6RY3R2wP3EFAlvNti8PHGpha0BkZWJp
YW4ub3JnAAoJEG+kWN0dsD9xUJQP/RtMbxFLi+QId/2Ys6f5fHHxwfe9ILvYhx/s
z3XL2E7sy0fTE2e8oFXOJZtrjCQZZRfE8sbMM3wDnmJpOMtRpbWmv6U8emsn8F9+
ATfAH+a+Zt5NrQ1RaGOW5oTRsC2N+u37EoQb+oAvsTUYhGkSW8bZ4CLdozqKkzgD
DoCf3rD2yU8aeWE0bPV1nd+BQqnJ8SDbO0CrbWV7fniWIAC8ACaOXUEYqNVJvqxT
pP8JlcG9okwYNRWZ+gTUU4cOXllvrv/SYLWcREk7O3ZGb64z98rGZzGqd0Gy1QOy
6rVm7PeHnv1Yw6KXnddVcZBs6caOVZBB3UlvdypwM54oDPOIbQZcpnQqQ/FeVI+B
QXvsnWzq7lBC5wH1QjekR/18EYvYWslS5jvqusTEal8d0y0rsOCz0sssjSLv7bVf

Bug#911167: GTK2 support will reach EOL in Debian in the near future (Was: Bug#911167: gwyddion: Depend on gtksourceview2)

[Andreas Tille]

Hi David,

On Wed, Oct 17, 2018 at 12:33:46AM +0200, David Nečas (Yeti) wrote:
> On Tue, Oct 16, 2018 at 10:18:59PM +0200, Andreas Tille wrote:
> > Hi David and Petr,
> > 
> > as you can see below, we can not ship gwyddion - at least not in its
> > current form with GUI if it will stick to GTK-2+ toolkit.  Do you
> > see any chance to port it to GTK-3+?
> 
> There is no way to port to GTK+3 without breaking backward
> compatibility.  We value backward compatibility.

I might be naive but to my perception the term "backward compatibility"
is misplaced if it is about GUI design issues.

> Some time not that long ago Debian was *the* distribution which supported
> the widest range of software.  Now you are removing GTK+2 when Fedora
> still offers GTK+1?

I'm not sure whether my general statement about GTK-2+ is true in any
case it concerns gtksourceview2.
 
> This is bat shit crazy.  There will be probably GTK+5 released before we
> would be able to port to GTK+3.  GTK+2 is *the* *stable* *version*.  No
> one who does actual software development can afford to spend 3/4 of time
> and effort constantly porting to some new GTK+ nonsense and deal with
> neverending deprecations.
> 
> If Debian does not support GTK+2 we will have to tell users to avoid it.

Just a short note:  I once volunteered to take over the maintenance of
gwyddion in Debian since the former maintainer had no time to do this
any more.  As long as it is about technical issues and my work is
respected I'm fine to spent a share of my limited time resources on this
packaging.  I have no time to discuss some developers personal opinion
about toolkit stabilities or distribution choices.  Feel free to ping me
in case gwyddion might build on more recent toolkits to review the
packaging.

Thank you

Andreas.

-- 
http://fam-tille.de

Processed: set blocker bugs for ptlib removal

[Debian Bug Tracking System]

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

> block 911594 by 911593
Bug #911594 [src:opal] opal: Intent to remove from Debian
911594 was not blocked by any bugs.
911594 was not blocking any bugs.
Added blocking bug(s) of 911594: 911593
> block 911595 by 911594
Bug #911595 [src:ptlib] ptlib: Intent to remove from Debian
911595 was not blocked by any bugs.
911595 was not blocking any bugs.
Added blocking bug(s) of 911595: 911594
> block 911594 by 911596
Bug #911594 [src:opal] opal: Intent to remove from Debian
911594 was blocked by: 911593
911594 was blocking: 911595
Added blocking bug(s) of 911594: 911596
>
End of message, stopping processing here.

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

Bug#911596: t38modem: Intent to remove from Debian

[Jeremy Bicha]

Source: t38modem
Version: 2.0.0-4
Severity: serious
X-Debbugs-CC: eugen.d...@univ-fcomte.fr,
pkg-voip-maintain...@lists.alioth.debian.org
Control: block 911594 by -1

I think it's time to remove t38modem from Debian. If you object,
please reply immediately.

ptlib and opal haven't had new releases since 2016. Its most prominent
client, ekiga, hasn't had a new release since 2013. t38modem hasn't
had a new release since 2011 (although there is a fork at
https://github.com/PeteDavidson/t38modem with the last release a year
ago).

The more immediate concern is that ptlib is one of the packages
blocking the openssl 1.0 removal and it doesn't look like anyone here
or in other distros is working on fixing that issue. There was this
recent commit but it doesn't look promising for openssl 1.1 support
either.

https://sourceforge.net/p/opalvoip/ptlib/ci/210c66562b

There has been no response to any of the RFA bugs for ptlib, opal and
ekiga in more than 6 months. So I'm filing similar removal bugs for
those too.

Thanks,
Jeremy Bicha

Bug#911595: ptlib: Intent to remove from Debian

[Jeremy Bicha]

Source: ptlib
Version: 2.10.11~dfsg-2.1
Severity: serious
X-Debbugs-CC: eugen.d...@univ-fcomte.fr,
pkg-voip-maintain...@lists.alioth.debian.org
Control: block -1 by 911594

I think it's time to remove ptlib from Debian. If you object, please
reply immediately.

ptlib and opal haven't had new releases since 2016. Its most prominent
client, ekiga, hasn't had a new release since 2013.

The more immediate concern is that ptlib is one of the packages
blocking the openssl 1.0 removal and it doesn't look like anyone here
or in other distros is working on fixing that issue. There was this
recent commit but it doesn't look promising for openssl 1.1 support
either.

https://sourceforge.net/p/opalvoip/ptlib/ci/210c66562b

There has been no response to any of the RFA bugs for ptlib, opal and
ekiga in more than 6 months. So I'm filing similar removal bugs for
those too and for t38modem.

Thanks,
Jeremy Bicha

Bug#911510: marked as done (rpcbind: changed location of rpcinfo breaks nfs-utils)

[Debian Bug Tracking System]

Your message dated Mon, 22 Oct 2018 11:35:37 +
with message-id 
and subject line Bug#911510: fixed in rpcbind 1.2.5-0.3
has caused the Debian Bug report #911510,
regarding rpcbind: changed location of rpcinfo breaks nfs-utils
to be marked as done.

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

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


-- 
911510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nfs-utils
Version: 1.3.4-2.2
Severity: grave
Tags: patch
Justification: renders package unusable


bug- and initscripts using rpcinfo are looking in $PREFIX/sbin.
Since rpcbind installs rpcinfo in $PREFIX/bin we need to adjust the
scripts as proposed in the attached patch.

Or we need to change rpcbind to install rpcinfo in $PREFIX/sbin

-- 
   Elimar
>From fd47a590a82c2bcced8c0d5f45ae8a37cb660744 Mon Sep 17 00:00:00 2001
From: Elimar Riesebieter 
Date: Sun, 21 Oct 2018 09:43:58 +0200
Subject: [PATCH] Change binary dir of rpcinfo

---
 debian/nfs-common.bugscript| 2 +-
 debian/nfs-common.init | 4 ++--
 debian/nfs-kernel-server.bugscript | 2 +-
 debian/nfs-kernel-server.init  | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/debian/nfs-common.bugscript b/debian/nfs-common.bugscript
index 7e6a73a..7af3df0 100644
--- a/debian/nfs-common.bugscript
+++ b/debian/nfs-common.bugscript
@@ -2,7 +2,7 @@
 set -e
 
 echo '-- rpcinfo --' >&3
-/usr/sbin/rpcinfo -p >&3
+/usr/bin/rpcinfo -p >&3
 
 echo '-- /etc/default/nfs-common --' >&3
 cat /etc/default/nfs-common|grep -v -e '^\#' -e '^$' >&3
diff --git a/debian/nfs-common.init b/debian/nfs-common.init
index 052de51..134e53f 100644
--- a/debian/nfs-common.init
+++ b/debian/nfs-common.init
@@ -123,8 +123,8 @@ case "$1" in
log_progress_msg "statd"

# See if rpcbind is running
-   if [ -x /usr/sbin/rpcinfo ]; then
-   /usr/sbin/rpcinfo -p >/dev/null 2>&1
+   if [ -x /usr/bin/rpcinfo ]; then
+   /usr/bin/rpcinfo -p >/dev/null 2>&1
RET=$?
if [ $RET != 0 ]; then
   echo
diff --git a/debian/nfs-kernel-server.bugscript 
b/debian/nfs-kernel-server.bugscript
index eed581d..5599834 100644
--- a/debian/nfs-kernel-server.bugscript
+++ b/debian/nfs-kernel-server.bugscript
@@ -2,7 +2,7 @@
 set -e
 
 echo '-- rpcinfo --' >&3
-/usr/sbin/rpcinfo -p >&3
+/usr/bin/rpcinfo -p >&3
 
 echo '-- /etc/default/nfs-kernel-server --' >&3
 cat /etc/default/nfs-kernel-server|grep -v -e '\#' -e '^$' >&3
diff --git a/debian/nfs-kernel-server.init b/debian/nfs-kernel-server.init
index e0c51d6..f25db3f 100644
--- a/debian/nfs-kernel-server.init
+++ b/debian/nfs-kernel-server.init
@@ -90,7 +90,7 @@ case "$1" in
log_progress_msg "nfsd"

# See if rpcbind is running
-   $PREFIX/sbin/rpcinfo -p >/dev/null 2>&1
+   $PREFIX/bin/rpcinfo -p >/dev/null 2>&1
RET=$?
if [ $RET != 0 ]; then
echo
-- 
2.19.1

--- End Message ---
--- Begin Message ---
Source: rpcbind
Source-Version: 1.2.5-0.3

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

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

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated rpcbind package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 22 Oct 2018 12:54:11 +0200
Source: rpcbind
Binary: rpcbind
Architecture: source amd64
Version: 1.2.5-0.3
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar 
Changed-By: Laurent Bigonville 
Description:
 rpcbind- converts RPC program numbers into universal addresses
Closes: 911510
Changes:
 rpcbind (1.2.5-0.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rpcbind.links: Create a compatibility symlink for rpcinfo from
 /usr/bin to /usr/sbin, seems there are several things in the archive
 expecting the binary to be in its previous location (Closes: #911510)
Checksums-Sha1:
 

Bug#911594: opal: Intent to remove from Debian

[Jeremy Bicha]

Source: opal
Version: 3.10.10~dfsg2-2.1
Severity: serious
X-Debbugs-CC: eugen.d...@univ-fcomte.fr,
pkg-voip-maintain...@lists.alioth.debian.org
Control: block -1 by 911593

I think it's time to remove opal from Debian. If you object, please
reply immediately.

ptlib and opal haven't had new releases since 2016. Its most prominent
client, ekiga, hasn't had a new release since 2013.

The more immediate concern is that ptlib is one of the packages
blocking the openssl 1.0 removal and it doesn't look like anyone here
or in other distros is working on fixing that issue. There was this
recent commit but it doesn't look promising for openssl 1.1 support
either.

https://sourceforge.net/p/opalvoip/ptlib/ci/210c66562b

There has been no response to any of the RFA bugs for ptlib, opal and
ekiga (or the other package that uses opal: t38modem) in more than 6
months. So I'm filing similar removal bugs for those too.

Thanks,
Jeremy Bicha

Bug#911593: ekiga: Intent to remove from Debian

[Jeremy Bicha]

Source: ekiga
Version: 4.0.1-9
Severity: serious
X-Debbugs-CC: eugen.d...@univ-fcomte.fr,
pkg-voip-maintain...@lists.alioth.debian.org

I think it's time to remove ekiga from Debian. If you object, please
reply immediately.

ekiga hasn't had an upstream release in 2013.

The more immediate concern is that ptlib is one of the packages
blocking the openssl 1.0 removal and it doesn't look like anyone here
or in other distros is working on fixing that issue. ptlib and opal
haven't had new releases since 2016. There was this recent commit but
it doesn't look promising for openssl 1.1 support either.

https://sourceforge.net/p/opalvoip/ptlib/ci/210c66562b

There has been no response to any of the RFA bugs for ptlib, opal and
ekiga (or the other package that uses opal: t38modem) in more than 6
months. So I'm filing similar removal bugs for those too.

Thanks,
Jeremy Bicha

Bug#911582: emacspeak does'nt work after upgrading emacs

[David Bremner]

Michelangelo Rodriguez  writes:

>
> *** Reporter, please consider answering these questions, where
> appropriate *** after upgrading emacs in unstable, emacsen-common
> install script for emacspeak exits because flavour emacs is not
> accepted by script.
>

Since emacspeak only supports gnu emacs, and it already has elpa
metadata (in emacspeak-pkg.el), it might be a good candidate for
conversion to declarative packaging using dh_elpa, instead of custom
emacsen-install. OTOH, your emacsen-install script is doing several
things other than byte-compilation, so those would have to move to a
normal postinst file.

Another fix that works for some packages is just to delete the

if [ ${FLAVOR} = emacs ]; then exit 0; fi

and deal with whatever fallout that creates.

If you have any questions about using dh_elpa, feel free to contact us
at debian-emac...@lists.debian.org, or #debian-emacs on irc.oftc.net

d

Bug#910517: monero: ftbfs on i386 and elsewhere (downgrading severity)

[Holger Levsen]

severity 910517 important
retitle 910517 monero: ftbfs on several architectures
thanks

appearantly Jonas fixed the ftbfs for i386, but not for other architectures, 
so I'm downgrading this bug, so that monero 0.13.0.3-1 can migrate to testing.
(as monero never build on these other architectures severity 'important' is
fine for this ftbfs bug.)

I think "#909422: RM: monero [i386] -- ANAIS; buildd OOMs during build"
can also be closed now, doing so.


-- 
cheers,
Holger

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


signature.asc
Description: PGP signature

Processed: monero: ftbfs on i386 and elsewhere (downgrading severity)

[Debian Bug Tracking System]

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

> severity 910517 important
Bug #910517 [src:monero] monero: FTBFS on i386: compiler runs our of memory
Warning: Unknown package 'src:monero'
Severity set to 'important' from 'serious'
Warning: Unknown package 'src:monero'
> retitle 910517 monero: ftbfs on several architectures
Bug #910517 [src:monero] monero: FTBFS on i386: compiler runs our of memory
Warning: Unknown package 'src:monero'
Changed Bug title to 'monero: ftbfs on several architectures' from 'monero: 
FTBFS on i386: compiler runs our of memory'.
Warning: Unknown package 'src:monero'
> thanks
Stopping processing here.

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

Processed: Bug #911090 in apt marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #911090 [libapt-pkg5.0] libapt-pkg5.0: incompatible with apt/stretch
Added tag(s) pending.

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

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

[Julian Andres Klode]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/apt-team/apt/commit/a18f38976d3544477f7450aa4265397db9b62cc6


Break pre-gcc8 aptitude and apt

gcc 8 broke the ABI again. After they decided to switch mangling of ABI tags in 
return values from:

 U URI::operator std::__cxx11::basic_string, 
std::allocator >[abi:cxx11]()
to:
 U URI::operator std::__cxx11::basic_string, 
std::allocator >()

in gcc 7, they now removed the legacy symbol in gcc 8, causing us to break our 
ABI in turn
for that one operator. We need more responsible gcc developers.

Closes: #911090



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/911090

Processed: bug 911130 is forwarded to https://github.com/htacg/tidy-html5/issues/743

[Debian Bug Tracking System]

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

> forwarded 911130 https://github.com/htacg/tidy-html5/issues/743
Bug #911130 [libtidy5.6] Package doesn't actually bump SOVERSION
Set Bug forwarded-to-address to 
'https://github.com/htacg/tidy-html5/issues/743'.
> thanks
Stopping processing here.

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

Processed: found 892331 in 0.0.19-1, tagging 892331, tagging 892344 ..., tagging 911562, tagging 911461 ...

[Debian Bug Tracking System]

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

> found 892331 0.0.19-1
Bug #892331 [src:3depict] 3depict: Please use 'pkg-config' to find FreeType 2
Marked as found in versions 3depict/0.0.19-1.
> tags 892331 + sid buster
Bug #892331 [src:3depict] 3depict: Please use 'pkg-config' to find FreeType 2
Added tag(s) sid and buster.
> tags 892344 + sid buster
Bug #892344 [src:literki] literki: Please use 'pkg-config' to find FreeType 2
Added tag(s) sid and buster.
> found 892344 0.0.0+20100113.git1da40724-1.2
Bug #892344 [src:literki] literki: Please use 'pkg-config' to find FreeType 2
Marked as found in versions literki/0.0.0+20100113.git1da40724-1.2.
> tags 911562 + sid buster
Bug #911562 [src:gnome-sharp2] gnome-sharp2: Intent to remove from Debian
Added tag(s) sid and buster.
> tags 911461 + sid buster
Bug #911461 {Done: se...@debian.org (Steinar H. Gunderson)} [src:amoeba] 
amoeba: Please use pkg-config to detect freetype
Added tag(s) buster and sid.
> found 911461 1.1-29.1
Bug #911461 {Done: se...@debian.org (Steinar H. Gunderson)} [src:amoeba] 
amoeba: Please use pkg-config to detect freetype
Marked as found in versions amoeba/1.1-29.1.
> tags 887712 + experimental
Bug #887712 {Done: m...@debian.org (Manuel A. Fernandez Montecelo)} 
[libftgl-dev] libftgl-dev: Detect freetype2 using pkg-config
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 910630, unarchiving 888386 ..., affects 903698 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 910630 piuparts
There were no usertags set.
Usertags are now: piuparts.
> unarchive 888386
Bug #888386 {Done: Sebastian Ramacher } [src:opencv] 
opencv: FTBFS with FFmpeg 4.0
Unarchived Bug 888386
> found 888386 3.3.0+dfsg-1~exp0
Bug #888386 {Done: Sebastian Ramacher } [src:opencv] 
opencv: FTBFS with FFmpeg 4.0
Marked as found in versions opencv/3.3.0+dfsg-1~exp0 and reopened.
> affects 903698 + python3-sphinxbase
Bug #903698 [src:sphinxbase] sphinxbase: build appears broken for multiple 
python3 versions
Added indication that 903698 affects python3-sphinxbase
> usertags 903698 piuparts
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.

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

Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

[Mike Gabriel]

Hi Ivo,

On  Mi 17 Okt 2018 15:46:11 CEST, Ivo De Decker wrote:


Control: block 895038 by 895037

Hi,

On Fri, Apr 06, 2018 at 01:07:39PM +, Mike Gabriel wrote:

Package: src:libappindicator
Severity: serious

The libappindicator package is currently QA team maintained in Debian and
shall be phased out hopfully during the buster release cycle. The
alternative (maintained upstream and Debian-downstream) is
libayatana-appindicator.

There is a lot of porting work to do (little patches are required for each
application), to let all AppIndicator aware applications build against the
new and supported AppIndicator shared lib fork "libayatana-appindicator".

For details, please see [1]

For a list of applications that require porting and the porting status, see
[2]


What's the status of this? Looking at testing, there are still quite a few
packages remaining that (build-)depend on libappindicator:


I wish I could give more time to writing patches against the listed  
packages. Possibly, I should do a bug filing round first and then add  
patches, when I get to working on individual packages.



# Broken Depends:
blueman: blueman
caffeine: caffeine
clipit: clipit
diodon: diodon
gmpc: gmpc
gromit-mpx: gromit-mpx
growl-for-linux: growl-for-linux
gtimelog: gtimelog
gxkb: gxkb
hime: hime
kylin-burner: libburner-media3-1
modem-manager-gui: modem-manager-gui
parcellite: parcellite
psensor: psensor
redshift: redshift-gtk
roger-router: roger-router
solaar: solaar-gnome3


The above list is irrelevant, what counts are the build-deps.

However, the following packages need to be considered regarding the  
Depends: field:


  * python-appindicator (Python2 bindings, GTK-2 version)
-> porting required to python-ayatana-appindicator
  * gir1.2-appindicator-0.1 (GTK-2 version)
-> gir1.2-ayatanaappindicator-0.1
  * gir1.2-appindicator3-0.1 (GTK-3 version)
-> gir1.2-ayatanaappindicator3-0.1
  *


# Broken Build-Depends:
clipit: libappindicator3-dev
diodon: libappindicator3-dev (>= 0.3.0)
gcin: libappindicator3-dev
gmpc: libappindicator-dev
gromit-mpx: libappindicator3-dev
growl-for-linux: libappindicator-dev
gxkb: libappindicator-dev
hime: libappindicator-dev
kylin-burner: libappindicator3-dev (>= 0.0.7)
modem-manager-gui: libappindicator3-dev
parcellite: libappindicator-dev
psensor: libappindicator3-dev
roger-router: libappindicator3-dev
zeal: libappindicator-dev


This list is incomplete.

Additionally, you need to check for build-deps against:

  * libappindicator-dev (GTK-2 version of appindicator)
-> porting required to libappindicator-dev (low prio)
  * libappindicator3-0.1-cil-dev (Mono bindings, GTK-2 version)
-> porting required to libayatana-appindicator0.1-cil-dev


For libindicator, the list is:


The libindicator transition is nearly done.


# Broken Depends:
cairo-dock-plug-ins: cairo-dock-alsamixer-plug-in
 cairo-dock-messaging-menu-plug-in
libappindicator: libappindicator1
 libappindicator3-1
lightdm-gtk-greeter: lightdm-gtk-greeter
workrave: workrave


Broken Depends: are irrelevant here.


# Broken Build-Depends:
cairo-dock-plug-ins: libindicator3-dev


Actually, the cairo-dock Indicator stack is completely broken in  
Debian. The maintainer added a half-baked and untested fix (simply  
switching Build-Depends to aytana-ido without patching the code itself.



libappindicator: libindicator-dev (>= 0.3.90)
 libindicator3-dev (>= 0.3.90)


-> This needs finishing the appindicator transition.


lightdm-gtk-greeter: libindicator3-dev


-> Patch submitted already.


workrave: libindicator3-dev (>= 0.3.19)


Oh, this one is new to me. Adding it to the wiki. [...] Ah, it's  
already there, but I wasn't aware of it being a libindicator porting  
issue (I though it was appindicator). Will take a look.



Do you still think it's realistic to get this done before the transition
freeze (2019-01-12)? If not, this should be postponed.


I'll do my best, but without help from maintainers, this will become  
difficult. I should write an enrolling mail to debian-devel, probably,  
to get more people on board.


To help the overview of what's still missing, it might be good to  
add blocking

bugs for every package to this one.


Yeah, I will do this.

The current status of all filed bugs with patches is this:

for libappindicator -> libayatana-appindicator:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ayatana-appindicator;users=pkg-ayatana-de...@lists.alioth.debian.org

for libindicator -> libayatana-indicator
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ayatanaindicators;users=pkg-ayatana-de...@lists.alioth.debian.org

Unfortunately, not all bugs submitted had usertags (and some of the  
second URL (#880193, #880169) actually belong to the first  
(ayatana-appindicator).


The full list of work, already done and to be done, is here:
https://wiki.debian.org/Ayatana/IndicatorsTransition

Mike
--

mike gabriel aka sunweaver (Debian Developer)

Bug#911590: gocode-auto-complete-el: fails to install: go-autocomplete.el:39:13:Error: Cannot open load file: No such file or directory, auto-complete

[Andreas Beckmann]

Followup-For: Bug #911590

some logfiles ...

Andreas


gacel-old.log.gz
Description: application/gzip


gacel-new.log.gz
Description: application/gzip