Bug#1071008: libx52pro0: installs udev rules twice to /usr and /

[Andreas Beckmann]

Followup-For: Bug #1071008

I noticed in piuparts that the package is currently uninstallable,
probably related to this bug.

  Selecting previously unselected package libx52pro0.
  Preparing to unpack .../libx52pro0_0.1.1-3_amd64.deb ...
  Unpacking libx52pro0 (0.1.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libx52pro0_0.1.1-3_amd64.deb (--unpack):
   unable to install new version of '/usr/lib/udev/rules.d/99-x52pro.rules': No 
such file or directory
  Errors were encountered while processing:
   /var/cache/apt/archives/libx52pro0_0.1.1-3_amd64.deb

Please verify that the fixed package is installable again ;-)


Andreas

Bug#1070427: libgnokii7t64: copyright file missing (policy 12.5)

[Andreas Beckmann]

Package: libgnokii7t64
Version: 0.6.31+dfsg-5.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

/usr/share/doc/$PACKAGE/ is neither a directory nor a symlink.

  MISSING COPYRIGHT FILE: /usr/share/doc/libgnokii7t64/copyright
  # ls -lad /usr/share/doc/libgnokii7t64
  ls: cannot access '/usr/share/doc/libgnokii7t64': No such file or directory
  # ls -la /usr/share/doc/libgnokii7t64/
  ls: cannot access '/usr/share/doc/libgnokii7t64/': No such file or directory


cheers,

Andreas

Bug#1070190: sendmail-bin: CVE-2023-51765 SMTP smuggling with NUL followup

[Andreas Beckmann]

On 04/05/2024 13.02, Andreas Beckmann wrote:

I have patched sendmail in order to enable O RejectNUL=True directive,
but I do not achieved the fact to enable it by default.



Andreas could you get a glimpse at how to render  RejectNUL a default ?


Second attempt. Completely untested. This should work for both fresh 
installations and upgrades (as long as *.cf gets regenerated).


Could you try that? And especially that the opt-out instructions are 
working?


Short explanation of the changes:
- Patch upstream proto.m4 to unconditionally emit 'O RejectNUL' with a
  default of 'false'. As long as confREJECT_NUL is not defined (also the
  default), this will be commented, so safe if built without
  _FFR_REJECT_NUL_BYTE
- In debian.m4 define confREJECT_NUL to 'true' if sendmail was built
  with _FFR_REJECT_NUL_BYTE, so it is enabled by default on Debian
- If sendmail.mc undefines confREJECT_NUL (or defines it to 'false'),
  RejectNUL will be disabled again.

If that works on sid, it should be trivially backportable to 
(old)*stable. There should be NEWS about that change.


Andreas
From 9b999fe61941c380a8c6dd49a3e50f8097b99b51 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Sat, 4 May 2024 14:07:48 +0200
Subject: [PATCH] enable 'O RejectNUL=true' by default

disable by appending

	undefine(`confREJECT_NUL')dnl

to the corresponding .mc file
---
 debian/cf/ostype/debian.m4.in   |  3 +++
 debian/patches/reject_nul.patch | 15 +++
 debian/patches/series   |  1 +
 3 files changed, 19 insertions(+)
 create mode 100644 debian/patches/reject_nul.patch

diff --git a/debian/cf/ostype/debian.m4.in b/debian/cf/ostype/debian.m4.in
index 5d1ae70..aa6f21f 100644
--- a/debian/cf/ostype/debian.m4.in
+++ b/debian/cf/ostype/debian.m4.in
@@ -65,6 +65,9 @@ dnl # this should help NIS startup time
 dnl #
 define(`confDEF_USER_ID', `mail:mail')dnl
 dnl #
+ifelse(eval(index(sm_ffr, `-D_FFR_REJECT_NUL_BYTE') >= 0), `1',dnl
+`define(`confREJECT_NUL',`true')dnl')dnl
+dnl #
 dnl #-
 dnl # mailer paths and options
 dnl #-
diff --git a/debian/patches/reject_nul.patch b/debian/patches/reject_nul.patch
new file mode 100644
index 000..56e822d
--- /dev/null
+++ b/debian/patches/reject_nul.patch
@@ -0,0 +1,15 @@
+Author: Andreas Beckmann 
+Description: add configurable 'O RejectNUL' to *.cf
+
+--- a/cf/m4/proto.m4
 b/cf/m4/proto.m4
+@@ -720,6 +720,9 @@ _OPTION(MaxNOOPCommands, `confMAX_NOOP_C
+ # Name to use for EHLO (defaults to $j)
+ _OPTION(HeloName, `confHELO_NAME')
+ 
++# Reject NUL bytes in message body, requires _FFR_REJECT_NUL_BYTE
++_OPTION(RejectNUL, `confREJECT_NUL', `false')
++
+ ifdef(`_NEED_SMTPOPMODES_', `dnl
+ # SMTP operation modes
+ C{SMTPOpModes} s d D')
diff --git a/debian/patches/series b/debian/patches/series
index 01aeb3a..3a97b08 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -21,3 +21,4 @@ hyphenation.patch
 fhs.patch
 typos.patch
 log-stop-at-debug-level.patch
+reject_nul.patch
-- 
2.20.1

Bug#1070190: sendmail-bin: CVE-2023-51765 SMTP smuggling with NUL followup

[Andreas Beckmann]

On 01/05/2024 16.14, Bastien Roucariès wrote:


Dear Maintainer,


unfortunately sendmail is orphaned ...


CVE-2023-51765 is not fully fixed at least for forwarding bad mail.

We must reject NUL including mail as a stop gap method.

I have patched sendmail in order to enable O RejectNUL=True directive,
but I do not achieved the fact to enable it by default.

It will need a NEWS.debian entry I suppose

Andreas could you get a glimpse at how to render  RejectNUL a default ?


I would probably attempt something like the attached patch. That should 
at least work for new installations. I have no idea how this would work 
on upgrades.


Do we need something like this in submit.mc, too?

We could (probably) also enable it from 
debian/cf/domain/debian-mta.m4.in etc., that should also enable the 
feature automatically on upgrades. But then we would need some way to 
opt-out by defining something in sendmail.mc ...


Or we could toggle the default:

--- a/sendmail/collect.c
+++ b/sendmail/collect.c
@@ -406,7 +406,7 @@ collect(fp, smtpmode, hdrp, e, rsetsize)
numhdrs = 0;
HasEightBits = false;
 #if _FFR_REJECT_NUL_BYTE
-   hasNUL = false;
+   hasNUL = true;
 #endif
buf = bp = bufbuf;
buflen = sizeof(bufbuf);

and use '''
LOCAL_CONFIG
O RejectNUL=false
''' as the opt-out in sendmail.mc

What I don't like about this approach is that we deviate from upstream 
default behavior with unchanged sendmail.cf.


Andreas

PS: It's nerly 20 years since I had sendmail running somewhere...

PPS: Marco has asked whether we could build sendmail with -DDANE to 
enable DANE support in the binary. This should be a runtime no-op unless 
dane gets enabled in sendmail.{mc,cf}. Do you have any concerns about 
this from the security side?From ade1a2cac3892eedc07a5f2e47db2213950d0d6b Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Sat, 4 May 2024 10:31:04 +0200
Subject: [PATCH] enable 'O RejectNUL=true' in the default sendmail.cf

---
 debian/cf/debian/sendmail.mc.in | 3 +++
 debian/cf/feature/rejectnul.m4  | 3 +++
 2 files changed, 6 insertions(+)
 create mode 100644 debian/cf/feature/rejectnul.m4

diff --git a/debian/cf/debian/sendmail.mc.in b/debian/cf/debian/sendmail.mc.in
index dc363e6..b15e84f 100644
--- a/debian/cf/debian/sendmail.mc.in
+++ b/debian/cf/debian/sendmail.mc.in
@@ -74,6 +74,9 @@ dnl #
 dnl # The access db is the basis for most of sendmail's checking
 FEATURE(`access_db', , `skip')dnl
 dnl #
+dnl # Reject NUL bytes in body
+FEATURE(`rejectnul')dnl
+dnl #
 dnl # The greet_pause feature stops some automail bots - but check the
 dnl # provided access db for details on excluding localhosts...
 FEATURE(`greet_pause', `1000')dnl 1 seconds
diff --git a/debian/cf/feature/rejectnul.m4 b/debian/cf/feature/rejectnul.m4
new file mode 100644
index 000..7b8fd4b
--- /dev/null
+++ b/debian/cf/feature/rejectnul.m4
@@ -0,0 +1,3 @@
+VERSIONID(`$Id: rejectnul.m4,v 1.0 2024-05-04 10:39:24 anbe Exp $')
+LOCAL_CONFIG
+O RejectNUL=true
-- 
2.20.1

Bug#1069068: pantalaimon: FTBFS some tests fail with asyncio CancelledError

[Andreas Beckmann]

Source: pantalaimon
Version: 0.10.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

pantalaimon FTBFS in sid (but could be built successfully in bookworm):

   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:311: cd /build/pantalaimon-0.10.5/.pybuild/cpython3_3.11/build; 
python3.11 -m pytest tests
= test session starts ==
platform linux -- Python 3.11.9, pytest-8.1.1, pluggy-1.4.0
rootdir: /build/pantalaimon-0.10.5
plugins: Faker-24.4.0
collected 17 items

tests/pan_client_test.py .Fss.   [ 29%]
tests/proxy_test.py .E.E.E.E.E   [ 58%]
tests/store_test.py E...s..  [100%]

 ERRORS 
___ ERROR at teardown of TestClass.test_daemon_start[pyloop] ___

self = 
response_class = , method = 'GET'
path = 
'/_matrix/client/r0/sync?access_token=abc123_state=true=%7B%22room%22%3A%7B%22state%22%3A%7B%22lazy_load_members%22%3Atrue%7D%7D%7D'
data = None, response_data = None, content_type = None, trace_context = None
data_provider = None, timeout = 0, content_length = None, save_to = None

async def _send(
self,
response_class: Type,
method: str,
path: str,
data: Union[None, str, AsyncDataT] = None,
response_data: Optional[Tuple[Any, ...]] = None,
content_type: Optional[str] = None,
trace_context: Optional[Any] = None,
data_provider: Optional[DataProvider] = None,
timeout: Optional[float] = None,
content_length: Optional[int] = None,
save_to: Optional[os.PathLike] = None,
):
headers = (
{"Content-Type": content_type}
if content_type
else {"Content-Type": "application/json"}
)

if content_length is not None:
headers["Content-Length"] = str(content_length)

if self.config.custom_headers is not None:
headers.update(self.config.custom_headers)

got_429 = 0
max_429 = self.config.max_limit_exceeded

got_timeouts = 0
max_timeouts = self.config.max_timeouts

while True:
if data_provider:
# mypy expects an "Awaitable[Any]" but data_provider is a
# method generated during runtime that may or may not be
# Awaitable. The actual type is a union of the types that we
# can receive from reading files.
data = await data_provider(got_429, got_timeouts)  # type: 
ignore

try:
>   transport_resp = await self.send(
method,
path,
data,
headers,
trace_context,
timeout,
)

/usr/lib/python3/dist-packages/nio/client/async_client.py:777:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/nio/client/async_client.py:291: in wrapper
return await func(self, *args, **kwargs)
/usr/lib/python3/dist-packages/nio/client/async_client.py:855: in send
return await self.client_session.request(
/usr/lib/python3.11/unittest/mock.py:2251: in _execute_mock_call
result = await effect(*args, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = 
orig_self = 
method = 'GET'
url = 
URL('https://example.org/_matrix/client/r0/sync?access_token=abc123=%257B%2522room%2522%253A%257B%2522state%2522%253A%257B%2522lazy_load_members%2522%253Atrue%257D%257D%257D_state=true')
args = ()
kwargs = {'data': None, 'headers': {'Content-Type': 'application/json'}, 'ssl': 
False, 'timeout': 0, ...}
url_origin = 
'https://example.org/_matrix/client/r0/sync?access_token=abc123_state=true=%7B%22room%22%3A%7B%22state%22%3A%7B%22lazy_load_members%22%3Atrue%7D%7D%7D'
url_str = 
'https://example.org/_matrix/client/r0/sync?access_token=abc123=%257B%2522room%2522%253A%257B%2522state%2522%253A%257B%2522lazy_load_members%2522%253Atrue%257D%257D%257D_state=true'
prefix = 'http://127.0.0.1'
key = ('GET', 
URL('https://example.org/_matrix/client/r0/sync?access_token=abc123=%257B%2522room%2522%253A%257B%2522state%2522%253A%257B%2522lazy_load_members%2522%253Atrue%257D%257D%257D_state=true'))
request_call = RequestCall(args=(), kwargs={'data': None, 'ssl': False, 
'headers': {'Content-Type': 'application/json'}, 'trace_request_ctx': None, 
'timeout': 0, 'allow_redirects': True})
response = None

async def _request_mock(self, orig_self: ClientSession,
method: str, url: 'Union[URL, str]',
*args: Tuple,
**kwargs: Any) -> 'ClientResponse':
"""Return mocked response object or raise connection error."""
if 

Bug#1066223: ftpcopy: FTBFS: conftest1663576.c:7:9: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration]

[Andreas Beckmann]

Followup-For: Bug #1066223
X-Debbugs-Cc: Bastian Germann 
Control: tag -1 pending

Hi Bastian,

I've fixed the remaining implicit function declarations and related bugs
in GIT. Do you want to take it from here again?
We should probably fix the nonverbose build in this very special build
system, too.


Andreas

Bug#1066437: libast: FTBFS: snprintf.c:45:22: error: unknown type name ‘size_t’

[Andreas Beckmann]

On Wed, 13 Mar 2024 13:03:27 +0100 Lucas Nussbaum  wrote:

Source: libast
Version: 0.7-9.1



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



> snprintf.c:45:22: error: unknown type name ‘size_t’
>45 | vsnprintf(char *str, size_t count, const char *fmt, va_list args)
>   |  ^~


This was so far the worst case of -Werror=implicit-function-declaration 
I encountered:

- a missing #include  (for exit()) caused a configure test to fail
- that didn't cause the configure step to fail (or silently disable some 
feature)
- but enabled a fallback codepath which had tons of errors triggering on 
-Werror=implicit-function-declaration


;-)

Perhaps you could add to your wiki entry about this bug class that there 
may be non-obvious problems during the configure step caused by 
-Werror=implicit-function-declaration that might

- silently disable features (because detection failed)
- enable unwanted fallback codepaths for "missing" (becuase misdetected) 
features


Andreas

Bug#1053169: Please remove librbd-dev build-depends on all 32 bits arch

[Andreas Beckmann]

Followup-For: Bug #1053169

Migration is currently blocked behind the t64 transition.

Andreas

Bug#1063401: atm-tools: has gained /usr/share/doc/libatm1/changelog.*

[Andreas Beckmann]

Package: atm-tools
Version: 1:2.5.1-5.1~exp1
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t
X-Debbugs-Cc: Steve Langasek 

atm-tools/experimental has gained two unexpected files, causing file
conflicts on upgrades:

$ debdiff atm-tools_1%3a2.5.1-5_amd64.deb atm-tools_1%3a2.5.1-5.1~exp1_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/share/doc/libatm1/changelog.Debian.gz
-rw-r--r--  root/root   /usr/share/doc/libatm1/changelog.gz

Control files: lines which differ (wdiff format)

Depends: [-libatm1 (= 1:2.5.1-5),-] {+libatm1t64 (>= 2.4.1-17~),+} libc6 (>= 
2.34), libfl2 (>= [-2.5.33)-] {+2.5.33), libatm1 (= 1:2.5.1-5.1~exp1)+}
Installed-Size: [-1197-] {+1243+}
Version: [-1:2.5.1-5-] {+1:2.5.1-5.1~exp1+}

There is still an libatm1 dependency, and the new libatm1t64 dependency
seems to miss the epoch.

Andreas

BTW, linux-atm is orphaned, so you should do QA instead of NMU uploads.

Bug#1058749: scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf'

[Andreas Beckmann]

Package: scanbd
Version: 1.5.1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
X-Debbugs-Cc: Chris Hofstaedtler 

Hi,

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

This test intentionally skipped 'testing' to find problems before packages
migrate from 'unstable' to 'testing'.

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

  Setting up scanbd (1.5.1-7) ...
  mv: not replacing '/etc/scanbd/dll.conf'
  dpkg: error processing package scanbd (--configure):
   installed scanbd package post-installation script subprocess returned error 
exit status 1


cheers,

Andreas


scanbd_1.5.1-7.log.gz
Description: application/gzip

Bug#1054640: propellor: FTBFS with ghc 9.4: Not in scope: type constructor or class `UserEntry'

[Andreas Beckmann]

Source: propellor
Version: 5.13-3
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

propellor FTBFS with ghc 9.4 (it still builds fine with 9.0 in testing):

https://salsa.debian.org/debian/propellor/-/jobs/4840519

[139 of 180] Compiling Utility.UserInfo ( src/Utility/UserInfo.hs, 
dist-ghc/build/Utility/UserInfo.o, dist-ghc/build/Utility/UserInfo.dyn_o )
src/Utility/UserInfo.hs:57:23: error:
Not in scope: type constructor or class `UserEntry'
   |
57 | myVal :: [String] -> (UserEntry -> String) -> IO (Either String String)
   |   ^
-e: error: debian/hlibrary.setup build --builddir=dist-ghc returned exit code 1
 at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 880.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup build 
--builddir=dist-ghc returned exit"...) called at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 610
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup build 
--builddir=dist-ghc") called at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm 
line 473
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "build", 
"--builddir=dist-ghc") called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 656
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called 
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25

Bug#1039365: Fedora has systemd-unit files for sendmail

[Andreas Beckmann]

On 31/07/2023 08.52, Marco wrote:

On Sun, 30 Jul 2023 18:46:11 + Marco  wrote:

On Mon, 26 Jun 2023 08:28:22 + Marco  wrote:

Fedora has some systemd unit files included, maybe these are helpful
here:
https://packages.fedoraproject.org/pkgs/sendmail/sendmail/fedora-rawhide.html#files


Is anybody here working on that issue?
  
It seems that the sysvinit script is being partially generated by

sendmailconfig. Is the goal of Debian to still provide that or to
deprecate sendmailconfig?

If it should be kept, I assume it needs to be changed to native
integrate with systemd without using start-stop-daemon.

Deprecating this sendmailconfig functionality makes integrating with
systemd much easier. Configuring queue runner and daemon mode would be
easier in a special file that is being read by the systemd unit.


I wouldn't go away from sendmailconfig since that would probably break 
the sendmail usage for the people still using sendmail ... and without 
maintainer we have noone to clean up after such breakage ...


Maybe we could introduce a sendmail-systemd package to allow running 
sendmail "the modern way" without breaking "the classic way".
We probably need to split the sendmail-bin and sendmail-base packages to 
decouple the sysv and sendmailconfig bits from the parts that are shared 
with sendmail-systemd.


Patches welcome!


Andreas

Bug#1039365: Fedora has systemd-unit files for sendmail

[Andreas Beckmann]

On 30/07/2023 20.46, Marco wrote:

On Mon, 26 Jun 2023 08:28:22 + Marco  wrote:

Fedora has some systemd unit files included, maybe these are helpful
here:
https://packages.fedoraproject.org/pkgs/sendmail/sendmail/fedora-rawhide.html#files


Is anybody here working on that issue?


As sendmail has no maintainer in Debian, I'm afraid this is not being 
worked on.


I'm happily applying patches (if someone provides them) in QA uploads, 
but it's nearly 20 years since I had sendmail running somewhere (on 
Sparc/Solaris at that time).



Andreas

Bug#1040468: kytos-sphinx-theme: broken symlink: /usr/share/kytos_sphinx_theme/kytos/static/bootstrap -> ../../../../lib/python3/dist-packages/sphinx_bootstrap_theme/bootstrap/static/bootstrap-3.3.7

[Andreas Beckmann]

Package: kytos-sphinx-theme
Version: 0.0.1+dfsg-2
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink:

0m29.3s ERROR: FAIL: Broken symlinks:
  /usr/share/kytos_sphinx_theme/kytos/static/bootstrap -> 
../../../../lib/python3/dist-packages/sphinx_bootstrap_theme/bootstrap/static/bootstrap-3.3.7
 (kytos-sphinx-theme-common)

Current python3-sphinx-bootstrap-theme ships bootstrap-2.3.2 and bootstrap-3.4.1


cheers,

Andreas

Bug#1040275: python3-socketio-client: SyntaxWarning during package installation

[Andreas Beckmann]

Package: python3-socketio-client
Version: 0.6.5-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package emits a SyntaxWarning
during installation:

  Setting up python3-socketio-client (0.6.5-1) ...
  /usr/lib/python3/dist-packages/socketIO_client/__init__.py:278: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
if engineIO_packet_type is 4:


Andreas

Bug#1038001: librem-ec-acpi-dkms: module fails to build for Linux 6.3

[Andreas Beckmann]

Package: librem-ec-acpi-dkms
Version: 0.9.1-4
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts


DKMS make.log for librem_ec_acpi-0.9.1 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 10:09:49 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
  CC [M]  /var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.o
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:276:24: error: 
initialization of 'int (*)(struct power_supply *, struct acpi_battery_hook *)' 
from incompatible pointer type 'int (*)(struct power_supply *)' 
[-Werror=incompatible-pointer-types]
  276 | .add_battery = librem_ec_battery_add,
  |^
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:276:24: note: (near 
initialization for 'librem_ec_battery_hook.add_battery')
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:277:27: error: 
initialization of 'int (*)(struct power_supply *, struct acpi_battery_hook *)' 
from incompatible pointer type 'int (*)(struct power_supply *)' 
[-Werror=incompatible-pointer-types]
  277 | .remove_battery = librem_ec_battery_remove,
  |   ^~~~
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:277:27: note: (near 
initialization for 'librem_ec_battery_hook.remove_battery')
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:773:27: error: 
initialization of 'void (*)(struct acpi_device *)' from incompatible pointer 
type 'int (*)(struct acpi_device *)' [-Werror=incompatible-pointer-types]
  773 | .remove = librem_ec_remove,
  |   ^~~~
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:773:27: note: (near 
initialization for 'librem_ec_driver.ops.remove')
cc1: some warnings being treated as errors
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257: 
/var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.o] Error 1
make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050: 
/var/lib/dkms/librem_ec_acpi/0.9.1/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64'


Andreas

Bug#1037213: awstats: prompting due to modified conffiles which were not modified by the user: /etc/logrotate.d/httpd-prerotate/awstats

[Andreas Beckmann]

Package: awstats
Version: 7.8-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

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

  Setting up awstats (7.8-3) ...
  
  Configuration file '/etc/logrotate.d/httpd-prerotate/awstats'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** awstats (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package 
awstats (--configure):
   end of file on stdin at conffile prompt

This was observed on the upgrade path
  buster -> bullseye -> bookworm
It does not show up on either buster -> bullseye or bullseye ->
bookworm.


There is something fancy happening here: a directory containing a
conffile is to be replaced by a conffile.



cheers,

Andreas


awstats_7.8-3.log.gz
Description: application/gzip

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Andreas Beckmann]

On 09/05/2023 16.55, Helmut Grohne wrote:

9base/bookworm no longer does, because it now uses dpkg-triggers to


Good to know that there is a better way nowadays ...


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

0m45.2s ERROR: FAIL: After purging files have been modified:
   /etc/shells   not owned


You should look closer:

0m45.2s DEBUG: Modified(user, group, mode, size, target): /etc/shells 
expected(root, root, - 100644, 128, None) != found(root, root, - 100644, 140, 
None)

It's a 12 byte difference. That's not 9base's entries. What you see here
is "/usr/bin/sh\n". So this is a /usr-merge bug. We already know it.
Thus force-merging.


Given that this seems to be the only package showing this behavior in my 
bullseye2bookworm tests so far, I didn' expect some "systematic" error 
outside of this package.



Andreas

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Andreas Beckmann]

Package: 9base
Version: 1:6-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package leaves modifications
in /etc/shells after upgrading from bullseye to bookworm and purging the
package.

9base/bullseye called add-shell/remove-shell in its postinst/postrm.
9base/bookworm no longer does that, but it also does not clean up the
leftover entries from bullseye in its postinst.

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

0m45.2s ERROR: FAIL: After purging files have been modified:
  /etc/shellsnot owned


The following (untested) snippet for the postinst should perform the
neccessary cleanup:

if [ "$1" = "install" ] || [ "$1" = "upgrade" ]; then
if dpkg --compare-versions "$2" lt-nl "1:6-14~" ; then
remove-shell /bin/rc
remove-shell /usr/lib/plan9/bin/rc
fi
fi


cheers,

Andreas


9base_1:6-13.log.gz
Description: application/gzip

Bug#1012232: freespace2: FTBFS: ./configure: line 17040: syntax error near unexpected token `ax_cxx_compile_cxx11_required=falsednl'

[Andreas Beckmann]

Followup-For: Bug #1012232
Control: reassign -1 src:freespace2 3.7.4+repack-1.1
Control: tag -1 sid bookworm
Control: retitle -1 freespace2: missing B-D: pkg-config, libglu1-mesa-dev

The autoconf error is a red herring.

The actual problem are missing
  Build-Depends: pkg-config, libglu1-mesa-dev
These were pulled in transitively in bullseye.

Then you need to make the inclusion of malloc.h unconditional in
code/windows_stub/stubs.cpp (or fix the build system s.t. it checks for
malloc.h and populates HAVE_MALLOC_H accordingly).

That seems to be sufficient to make the package build again.


Andreas

Bug#1012232: freespace2: FTBFS: ./configure: line 17040: syntax error near unexpected token `ax_cxx_compile_cxx11_required=falsednl'

[Andreas Beckmann]

Followup-For: Bug #1012232
Control: found -1 2.71-3

The problem is still reproducible when rebuilding src:freespace2 in sid
with latest autoconf.


Andreas

Bug#1030187: adv-17v35x-dkms: module fails to build for Linux 6.1

[Andreas Beckmann]

Package: adv-17v35x-dkms
Version: 5.0.6.0-4
Severity: serious

Hi,

adv-17v35x-dkms fails to build the kernel module for Linux 6.1:

DKMS make.log for adv-17v35x-5.0.6.0 for kernel 6.1.0-2-amd64 (x86_64)
Tue Jan 31 16:13:56 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.1.0-2-amd64'
  CC [M]  /var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.o
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.c:2162:27: error: 
initialization of ‘void (*)(struct uart_port *, struct ktermios *, const struct 
ktermios *)’ from incompatible pointer type ‘void (*)(struct uart_port *, 
struct ktermios *, struct ktermios *)’ [-Werror=incompatible-pointer-types]
 2162 | .set_termios= serialadv_set_termios,
  |   ^
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.c:2162:27: note: (near 
initialization for ‘serialadv_pops.set_termios’)
cc1: some warnings being treated as errors
make[1]: *** [/usr/src/linux-headers-6.1.0-2-common/scripts/Makefile.build:255: 
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.o] Error 1
make: *** [/usr/src/linux-headers-6.1.0-2-common/Makefile:2017: 
/var/lib/dkms/adv-17v35x/5.0.6.0/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.1.0-2-amd64'

full log at
https://ci.debian.net/data/autopkgtest/testing/amd64/a/adv-17v35x/30877035/log.gz


Andreas

Bug#1027836: planner,planner-data: both ship /usr/share/planner/images/gnome-planner.png

[Andreas Beckmann]

Package: planner,planner-data
Version: 0.14.91-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your packages failed to install
because they tries to overwrite each others files.

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

  Selecting previously unselected package planner.
  Preparing to unpack .../101-planner_0.14.91-1_amd64.deb ...
  Unpacking planner (0.14.91-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-9JdNac/101-planner_0.14.91-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/planner/images/gnome-planner.png', which is 
also in package planner-data 0.14.91-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-9JdNac/101-planner_0.14.91-1_amd64.deb


cheers,

Andreas


planner=0.14.91-1_planner-data=0.14.91-1.log.gz
Description: application/gzip

Bug#1023662: adv-17v35x-dkms: module fails to build for Linux 6.0

[Andreas Beckmann]

Package: adv-17v35x-dkms
Version: 5.0.6.0-3
Severity: serious

Hi,

the adv-17v35x-dkms module cannot be built for Linux 6.0:

https://ci.debian.net/data/autopkgtest/unstable/amd64/a/adv-17v35x/27922615/log.gz

DKMS make.log for adv-17v35x-5.0.6.0 for kernel 6.0.0-2-amd64 (x86_64)
Fri Nov  4 16:55:27 UTC 2022
make: Entering directory '/usr/src/linux-headers-6.0.0-2-amd64'
  CC [M]  /var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.o
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.c: In function 
‘serialadv_timeout’:
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.c:1190:62: error: ‘struct 
uart_port’ has no member named ‘timeout’
 1190 | mod_timer(>timer, jiffies + poll_timeout(up->port.timeout));
  |  ^
make[1]: *** [/usr/src/linux-headers-6.0.0-2-common/scripts/Makefile.build:254: 
/var/lib/dkms/adv-17v35x/5.0.6.0/build/adv17v35x.o] Error 1
make: *** [/usr/src/linux-headers-6.0.0-2-common/Makefile:1876: 
/var/lib/dkms/adv-17v35x/5.0.6.0/build] Error 2
make: Leaving directory '/usr/src/linux-headers-6.0.0-2-amd64'


Andreas

Bug#964540: dropwatch build times out in the testsuite

[Andreas Beckmann]

Control: severity -1 normal

On Wed, 8 Jul 2020 13:26:54 +0200 Matthias Klose  wrote:

Package: src:dropwatch
Version: 1.5.3-1



dropwatch build times out in the testsuite, no output available in the build 
log.


The 1.5.4-1 release built fine on the buildds for all release 
architectures. But there were testsuite timeouts on some ports 
architectures.



Andreas

Bug#991331: sid listed as affected

[Andreas Beckmann]

On 24/09/2022 11.16, Marco wrote:

Why is sid (that has 8.17.1.9-1) still listed as affected by ALPACA?
https://security-tracker.debian.org/tracker/CVE-2021-3618

This thread says this is has already been fixed with 8.16.1.


Right now, I see this as fixed in the security tracker, but maybe the 
metadata has been updated inbetween.



Andreas

Bug#1020771: sendmail: french package description contains duplicated text

[Andreas Beckmann]

Hi Yvan,

thanks for spotting this issue.

On 26/09/2022 13.59, Yvan Masson wrote:
I had a quick look on https://salsa.debian.org/debian/sendmail but could 
not find where is stored this translation: for my general knowledge, 
could you tell me where it is?


These translations are not part of the package.
I think the package description translations come from
The Debian Description Translation Project — DDTP
https://www.debian.org/international/l10n/ddtp
but as I have never interacted with that, I don't know how to report 
translation bugs there.


Andreas

Bug#1009078: Version 8.17.1-2 does not work again

[Andreas Beckmann]

On 13/06/2022 08.11, Joerg Dorchain wrote:

Thank you very much for providing the package. Version 8.17.1.9-1
wokrs for me :-)


Thanks for pointing me to the fix, that made it much easier.
And for confirming that it works.


Andreas

Bug#1009078: Version 8.17.1-2 does not work again

[Andreas Beckmann]

On 12/06/2022 09.03, Joerg Dorchain wrote:
> reopen 1009078 =
> thanks
> 
> Hi,
> 
> I am sorry to say that the newly arrived version 8.17.1-2 in testing shows 
> the same behaviour as the
> originally reported version 8.16.1-2, no auth mechanisms offered after 
> starttls.
> 
> Downgrading to version 8.17.1-1 helps, though.

The only relevant difference is that -2 is built against openssl 3 while
-1 was built against openssl 1.1. Do other distros have patches for
8.17.1 and openssl 3?


Andreas

Bug#1009078: sasl auth via saslauthd does not work anymore

[Andreas Beckmann]

On 07/04/2022 02.15, Joerg Dorchain wrote:

Package: sendmail
Version: 8.16.1-2

With the current sendmail in testing, my incoming smtp auth configuration does 
not
work anymore.


could you try sendmail 8.17 from experimental?

Andreas

Bug#1007750: libnfsidmap_0.25-6+b1_mips64el-buildd.changes REJECTED

[Andreas Beckmann]

Followup-For: Bug #1007750
Control: tag -1 sid bookworm
Control: retitle -1 src:libnfsidmap: libnfsidmap-dev is also built by 
src:nfs-utils

libnfsidmap | 0.25-6| stable | source
libnfsidmap-dev | 0.25-6| stable | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el, s390x
libnfsidmap2| 0.25-6| stable | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el, s390x

libnfsidmap-dev   | 1:2.6.1-1+b1  | unstable   | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el, s390x
libnfsidmap1  | 1:2.6.1-1+b1  | unstable   | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el, s390x
nfs-common| 1:2.6.1-1+b1  | unstable   | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el, s390x
nfs-kernel-server | 1:2.6.1-1+b1  | unstable   | amd64, arm64, armel, armhf, 
i386, mips64el, mipsel, ppc64el, s390x
nfs-utils | 1:2.6.1-1 | unstable   | source

src:nfs-utils seems to have taken over libnfsidmap-dev,
but the soversion of the shared library went backwards:

src:libnfsidmap built libnfsidmap1 from 0.8-1 to 0.17-1
src:libnfsidmap built libnfsidmap2 from 0.17-2 to 0.25-6+b1
src:nfs-utils built libnfsidmap1 from 1:2.5.4-1~exp1 to 1:2.6.1-1+b1


Andreas

Bug#1003525: scalapack-doc: several releases behind scalapack

[Andreas Beckmann]

Package: scalapack-doc
Version: 1.5-11
Severity: serious
Tags: sid bookworm

scalapack-doc is several releases behind scalapack:

 scalapack | 1.8.0-6  | squeeze  | source
 scalapack | 1.8.0-9  | wheezy   | source
 scalapack | 1.8.0-12 | jessie   | source
 scalapack | 1.8.0-13 | stretch  | source
 scalapack | 2.0.2-7  | buster   | source
 scalapack | 2.1.0-4  | bullseye | source
 scalapack | 2.1.0-4  | bookworm | source
 scalapack | 2.1.0-4  | sid  | source
 scalapack-doc | 1.5-10   | squeeze  | source, all
 scalapack-doc | 1.5-10   | wheezy   | source, all
 scalapack-doc | 1.5-10   | jessie   | source, all
 scalapack-doc | 1.5-11   | stretch  | source, all
 scalapack-doc | 1.5-11   | buster   | source, all
 scalapack-doc | 1.5-11   | bullseye | source, all
 scalapack-doc | 1.5-11   | sid  | source, all

Actually, the scalapack history already begins with the
scalapack (1.6-1) upload in 1999 ... which happened at the same time
as the initial scalapack-doc upload (1.5-1).

@scalapack maintainers: how useful is this outdated 1.5 -doc package
for scalapack 2.1?

Andreas

Bug#1002886: human-icon-theme: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Andreas Beckmann]

Package: human-icon-theme
Version: 0.28.debian-6.1
Severity: serious
Tags: sid bookworm
User: nthyk...@master.debian.org
Usertags: compat-5-6-removal

Hi,

The package human-icon-theme uses debhelper with a compat level of 5 or 6,
which is no longer supported [1].

Please bump the debhelper compat at your earliest convenience

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


Thanks,
Andreas

[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

Bug#1002885: tangerine-icon-theme: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Andreas Beckmann]

Package: tangerine-icon-theme
Version: 0.26.debian-5
Severity: serious
Tags: sid bookworm
User: nthyk...@master.debian.org
Usertags: compat-5-6-removal

Hi,

The package tangerine-icon-theme uses debhelper with a compat level of 5 or 6,
which is no longer supported [1].

Please bump the debhelper compat at your earliest convenience

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


Thanks,
Andreas

[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

Bug#999907: libglobalarrays-dev,libga-dev: both ship /usr/lib/x86_64-linux-gnu/libga.a

[Andreas Beckmann]

Package: libglobalarrays-dev,libga-dev
Severity: serious
Tags: sid bookworm
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 5.7.2-2
Control: found -1 1:2.4.7-5

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Preparing to unpack .../libga-dev_1%3a2.4.7-5_amd64.deb ...
  Unpacking libga-dev:amd64 (1:2.4.7-5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libga-dev_1%3a2.4.7-5_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libga.a', which is also in 
package libglobalarrays-dev 5.7.2-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libga-dev_1%3a2.4.7-5_amd64.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

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):

  /usr/lib/x86_64-linux-gnu/libga.a

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.


libglobalarrays-dev does have one reverse build-dependency: nwchem.
libga-dev does have none.


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


libglobalarrays-dev=5.7.2-2_libga-dev=1:2.4.7-5.log.gz
Description: application/gzip

Bug#696824: tcm: FTBFS on non-linux archs

[Andreas Beckmann]

Control: tag -1 help

On Thu, 27 Dec 2012 20:51:48 +0100 Samuel Thibault 
 wrote:

Package: tcm
Version: 2.20+TSQD-4.2



tcm currently FTBFS on non-linux archs, apparently due to a non-matching
patch, see for instance


Actually, the problem starts with the build system not recognizing the 
platform and therefore not finding any settings. (Detection needs to be 
added to the top-level Makefile.)


I tried to make the configuration step error out early on unknown 
platforms in the -7 QA upload.


Andreas

Bug#993075: libnsl-dev: rpcsvc/nis.h includes no longer available rpc/rpc.h

[Andreas Beckmann]

On 27/08/2021 11.35, Aurelien Jarno wrote:

sendmail should be updated to get the correct cflags. I'll try to work
on a patch.


Many thanks for the very quick fix!

Andreas

Bug#979047: RM: pepperflashplugin-nonfree -- RoQA; No longer work; upstream eol

[Andreas Beckmann]

Control: reassign -1 ftp.debian.org

On 15/01/2021 17.12, Andreas Beckmann wrote:

As pointed out in #978954, its better to replace it by a dummy with the
broken download/install functionality removed to ensure clean upgrades.


That was shipped in bullseye and buster.


So let's postpone the removal to bookworm.


We can do this now.


Andreas

Bug#991877: firmware-b43legacy-installer: uninstallable ERROR: certificate common name `firmware-selector.openwrt.org' doesn't match requested host name `downloads.openwrt.org'.

[Andreas Beckmann]

Package: firmware-b43legacy-installer
Version: 4.178.10.4-4
Severity: serious
Tags: squeeze
User: debian...@lists.debian.org
Usertags: piuparts
Control: close -1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.


# apt-get install firmware-b43legacy-installer
Reading package lists... Done
Building dependency tree   
Reading state information... Done
firmware-b43legacy-installer is already the newest version.
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.
Do you want to continue [Y/n]? 
Setting up firmware-b43legacy-installer (4.178.10.4-4) ...
/var/lib/dpkg/info/firmware-b43legacy-installer.postinst: 6: lspci: not found
--2021-08-04 08:32:33--  
http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
Connecting to 127.0.0.1:3128... connected.
Proxy request sent, awaiting response... 301 Moved Permanently
Location: https://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o 
[following]
--2021-08-04 08:32:33--  
https://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
Connecting to 127.0.0.1:3128... connected.
ERROR: certificate common name `firmware-selector.openwrt.org' doesn't match 
requested host name `downloads.openwrt.org'.
To connect to downloads.openwrt.org insecurely, use `--no-check-certificate'.
dpkg: error processing firmware-b43legacy-installer (--configure):
 subprocess installed post-installation script returned error exit status 5
configured to not write apport reports
  Errors were encountered while processing:
 firmware-b43legacy-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)

This seems to be specific to squeeze, the same package version installs
fine in wheezy. So this is probably rather an issue in openssl or wget.


cheers,

Andreas

Bug#991331: sendmail: CVE-2021-3618

[Andreas Beckmann]

Control: fixed -1 8.16.1-1
Control: tag -1 + help

On 20/07/2021 22.21, Moritz Mühlenhoff wrote:

https://alpaca-attack.com/ affects sendmail. It was fixed in
the latest 3.16.1 release:


https://bugzilla.redhat.com/show_bug.cgi?id=1975623#c13

Huzaifa S. Sidhpurwala 2021-06-29 05:11:36 UTC

Sendmail:

"Sendmail only detects HTTP requests at the very start of a connection. 
If STARTTLS is used, the first command inside the connection can bensent 
by the attacker, bypassing the detection"

Sendmail fixed a bug to detect HTTP requests when STARTTLS is used in 8.16

As per the release notes:

SECURITY: If sendmail tried to reuse an SMTP session which had
already been closed by the server, then the connection
cache could have invalid information about the session.
One possible consequence was that STARTTLS was not
used even if offered.  This problem has been fixed
by clearing out all relevant status information
when a closed session is encountered.

(there are no specific references since sendmail 8.16.1 was released in 
July 2020, long before alpaca-attack got disclosed to interested parties:

2020-10-20: Initial contact with [...] author of TLS standard [...]
...
2021-02-20: Initial contact with all affected application servers (FTP, 
Email).

...
2021-06-09: Public disclosure.)

+help: I'm hoping that someone backports this fix to 8.15.x, possibly
https://bugzilla.redhat.com/show_bug.cgi?id=1975650


Andreas

Bug#989339: omnievents-doc: broken symlink: /usr/share/doc/omnievents-doc/doxygen/jquery.js -> ../../../javascript/jquery/jquery.min.js

[Andreas Beckmann]

Package: omnievents-doc
Version: 1:2.6.2-5.1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m11.6s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/omnievents-doc/doxygen/jquery.js -> 
../../../javascript/jquery/jquery.min.js (omnievents-doc)


Should omnievents-doc have a dependency on libjs-jquery?


cheers,

Andreas


omnievents-doc_1:2.6.2-5.1.log.gz
Description: application/gzip

Bug#903794: lmbench-doc: broken symlinks: /usr/share/doc/lmbench-doc/man/*.8 -> lmbench.8

[Andreas Beckmann]

Followup-For: Bug #903794
Control: found -1 3.0-a9+debian.1-5
Control: tag -1 patch

Please apply the attached patch for moving the manpage symlinks to the
right place.


Andreas
>From 3c2d868282662549f0fc7814e65254d27a2aa8e4 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Mon, 22 Mar 2021 22:11:25 +0100
Subject: [PATCH] fix manpage symlinks

---
 debian/lmbench-doc.dirs  | 2 --
 debian/lmbench-doc.links | 3 ---
 debian/lmbench.links | 3 +++
 3 files changed, 3 insertions(+), 5 deletions(-)
 delete mode 100644 debian/lmbench-doc.dirs
 delete mode 100644 debian/lmbench-doc.links

diff --git a/debian/lmbench-doc.dirs b/debian/lmbench-doc.dirs
deleted file mode 100644
index 26000ed..000
--- a/debian/lmbench-doc.dirs
+++ /dev/null
@@ -1,2 +0,0 @@
-usr/share/doc/lmbench-doc
-usr/share/doc/lmbench-doc/man
diff --git a/debian/lmbench-doc.links b/debian/lmbench-doc.links
deleted file mode 100644
index 79454fe..000
--- a/debian/lmbench-doc.links
+++ /dev/null
@@ -1,3 +0,0 @@
-usr/share/doc/lmbench-doc/man/lmbench.8 usr/share/doc/lmbench-doc/man/hello.8
-usr/share/doc/lmbench-doc/man/lmbench.8 
usr/share/doc/lmbench-doc/man/flushdisk.8
-usr/share/doc/lmbench-doc/man/lmbench.8 usr/share/doc/lmbench-doc/man/memsize.8
diff --git a/debian/lmbench.links b/debian/lmbench.links
index a3431e6..2c6fc99 100644
--- a/debian/lmbench.links
+++ b/debian/lmbench.links
@@ -1,2 +1,5 @@
 usr/share/man/man8/lmbench.8.gz usr/share/man/man8/lmhttp.8.gz
 usr/share/man/man8/lmbench.8.gz usr/share/man/man8/msleep.8.gz
+usr/share/man/man8/lmbench.8.gz usr/share/man/man8/hello.8.gz
+usr/share/man/man8/lmbench.8.gz usr/share/man/man8/flushdisk.8.gz
+usr/share/man/man8/lmbench.8.gz usr/share/man/man8/memsize.8.gz
-- 
2.20.1

Bug#983902: sendmail: reproducible builds: embeds build path in site.config.m4 documentation files

[Andreas Beckmann]

Fix uploaded, please take care of an unblock if you think this should be 
in bullseye.


Andreas

Bug#893022: adequate doesn't find missing pkg-config dependencies

[Andreas Beckmann]

Control: reassign -1 piuparts-slave-from-git-deps

On Mon, 14 May 2018 11:34:37 +0200 Jakub Wilk  wrote:

* Adrian Bunk , 2018-03-15, 21:22:
>adequate already seems to try to check this, but for some reason it 
>doesn't find the libinput-dev problem.


adequate checks these dependencies only if the pkg-config package is installed.

libinput-dev currently depends on it transitively, but I think it didn't 
back when this bug was filed, and AFAICS piuparts doesn't install it on its own

either.


piuparts-slave-from-git-deps needs Depends: adequate pkg-config

Andreas

Bug#978954: pepperflashplugin-nonfree: should not be part of next stable Debian release

[Andreas Beckmann]

Control: severity -1 important
Control: retitle -1 pepperflashplugin-nonfree: should not be part of bookworm

On Tue, 12 Jan 2021 15:14:49 +0100 Gunnar Hjalmarsson  
wrote:
> But let me add that even if Opera fixes that, users may think they want 
> to enable flash, try to install pepperflashplugin-nonfree, and with that 
> screw up dpkg. So the issue happens before they try to enable it in a 
> browser. I.e. as long as the package in its current state is present in 
> the archive.

I've just uploaded 1.8.8 turning the package into a dummy removing
the broken download/install functionality and the chromium integration
s.t. people will upgrade to a "fixed" version (that does not block trying
to download unavailable bits). That should be cleaner than removing it
from the archive while leaving it installed in broken state on users
systems.


Andreas

Bug#966189: cuneiform: FTBFS with GCC 10: multiple definition of ... due to -fno-common

[Andreas Beckmann]

Source: cuneiform
Version: 1.1.0+dfsg-7.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Hi,

cuneiform started to FTBFS when GCC 10 was made the default compiler:

[ 31%] Linking CXX shared library librlings.so
cd /build/cuneiform-1.1.0+dfsg/obj/cuneiform_src/Kern/rling/sources && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/rlings.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/build/cuneiform-1.1.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu++98 -Wno-error -Wl,-Bsymbolic -Wl,-z,relro 
-Wl,--as-needed -shared -Wl,-soname,librli
ngs.so.0 -o librlings.so.1.1.0 CMakeFiles/rlings.dir/cpp/crled.cpp.o 
CMakeFiles/rlings.dir/cpp/crling.cpp.o 
CMakeFiles/rlings.dir/cpp/crlmemory.cpp.o CMakeFiles/rlings.dir/cpp/dll.cpp.o 
CMakeFiles/rlings.dir/cpp/rlcontrol.cpp.o CMakeFiles/rlings.dir/c/rling_m
a.c.o CMakeFiles/rlings.dir/c/spel2dic.c.o CMakeFiles/rlings.dir/c/spel2voc.c.o 
CMakeFiles/rlings.dir/c/spelabc.c.o CMakeFiles/rlings.dir/c/spelart.c.o 
CMakeFiles/rlings.dir/c/spelbuf.c.o CMakeFiles/rlings.dir/c/spelchk.c.o 
CMakeFiles/rlings.dir/c/speldat1.c.
o CMakeFiles/rlings.dir/c/speldat2.c.o CMakeFiles/rlings.dir/c/speldici.c.o 
CMakeFiles/rlings.dir/c/speldict.c.o CMakeFiles/rlings.dir/c/speldvoc.c.o 
CMakeFiles/rlings.dir/c/speledf1.c.o CMakeFiles/rlings.dir/c/speledf2.c.o 
CMakeFiles/rlings.dir/c/speledio.c.
o CMakeFiles/rlings.dir/c/spelfun.c.o CMakeFiles/rlings.dir/c/spelloop.c.o 
CMakeFiles/rlings.dir/c/spelout.c.o CMakeFiles/rlings.dir/c/spelq.c.o 
CMakeFiles/rlings.dir/c/spelset.c.o CMakeFiles/rlings.dir/c/spelspec.c.o 
CMakeFiles/rlings.dir/c/udictini.c.o CMak
eFiles/rlings.dir/c/udictuti.c.o  
-Wl,-rpath,/build/cuneiform-1.1.0+dfsg/obj/cuneiform_src/Kern/cstr:/build/cuneiform-1.1.0+dfsg/obj/cuneiform_src/Kern/cfcompat:/build/cuneiform-1.1.0+dfsg/obj/cuneiform_src/Kern/ccom:
 ../../cstr/libcstr.so.1.1.0 ../../cfcompa
t/libcfcompat.so.1.1.0 ../../ccom/libccom.so.1.1.0 -ldl 
/usr/bin/ld: 
CMakeFiles/rlings.dir/c/speldici.c.o:./obj/cuneiform_src/Kern/rling/sources/./cuneiform_src/Kern/rling/sources/c/speldici.c:123:
 multiple definition of `my_free'; 
CMakeFiles/rlings.dir/c/rling_ma.c.o:./obj/cuneiform_src/Kern/rling/sources/./cunei
form_src/Kern/rling/sources/c/rling_ma.c:110: first defined here
/usr/bin/ld: 
CMakeFiles/rlings.dir/c/speldici.c.o:./obj/cuneiform_src/Kern/rling/sources/./cuneiform_src/Kern/rling/sources/c/speldici.c:122:
 multiple definition of `my_alloc'; 
CMakeFiles/rlings.dir/c/rling_ma.c.o:./obj/cuneiform_src/Kern/rling/sources/./cune
iform_src/Kern/rling/sources/c/rling_ma.c:109: first defined here

More information about the corresponding GCC change can be found here:
https://gcc.gnu.org/gcc-10/porting_to.html
"Default to -fno-common"


Andreas

Bug#949234: debconf: unable to initialize frontend: Dialog in firmware-b43-installer

[Andreas Beckmann]

Control: tag -1 moreinfo

On Sat, 18 Jan 2020 16:32:37 + Jesse57901
 wrote:
> When running firmware-b43-installer after unpacking and setting up gives 
> message (debconf:unable to initialize frontend: Dialog). Complete readout 
> from installer:
> 
> Unpacking firmware-b43-installer (1:019-4) ...
> Setting up firmware-b43-installer (1:019-4) ...
> debconf: unable to initialize frontend: Dialog
> debconf: (Dialog frontend requires a screen at least 13 lines tall and 31 
> columns wide.)
> debconf: falling back to frontend: Readline

How exactly did you observe the problem?
a) you ran the command in an extremely small terminal -> no error
b) you ran the command in a "regularly sized" terminal, but
debconf/Dialog did not recognize it -> we should reassign the bug to
debconf (or dialog), since it does not seem specific to b43-*

Andreas

Bug#961509: libxine2-bin: missing Breaks+Replaces: libxine2-doc (<< 1.2.10)

[Andreas Beckmann]

Package: libxine2-bin
Version: 1.2.10-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' 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 .../libxine2-bin_1.2.10-2_amd64.deb ...
  Unpacking libxine2-bin (1.2.10-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libxine2-bin_1.2.10-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man5/xine.5.gz', which is also in 
package libxine2-doc 1.2.9-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libxine2-bin_1.2.10-2_amd64.deb


cheers,

Andreas


libxine2-doc=1.2.9-1_libxine2-bin=1.2.10-2.log.gz
Description: application/gzip

Bug#955552: xpdf: FTBFS with poppler 0.85.0: error: 'getModRegion' was not declared in this scope

[Andreas Beckmann]

Source: xpdf
Version: 3.04-13exp3
Severity: serious
Tags: ftbfs sid bullseye experimental
Justification: fails to build from source (but built successfully in the past)

Hi,

xpdf/experimental FTBFS against libpoppler-dev/experimental (0.85.0-1):

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/xpdf-3.04'
x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/build/xpdf-3.04=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/poppler -I/usr/include/poppler/goo 
-I/usr/include/poppler/splash -Wno-write-strings -Wno-format-extra-args 
-Wfatal-errors -DHAVE_DIRENT_H -DHAVE_PAPER_H 
-DSYSTEM_XPDFRC=\"/etc/xpdf/xpdfrc\"  -c -o build/CoreOutputDev.o 
build/CoreOutputDev.cc
build/CoreOutputDev.cc: In member function 'virtual void CoreOutputDev::dump()':
build/CoreOutputDev.cc:50:5: error: 'getModRegion' was not declared in this 
scope
   50 | getModRegion(, , , );
  | ^~~~
compilation terminated due to -Wfatal-errors.
make[1]: *** [: build/CoreOutputDev.o] Error 1
make[1]: Leaving directory '/build/xpdf-3.04'
make: *** [debian/rules:50: build] Error 2


The version in sid (3.04-13) has the same problem.


Andreas


xpdf_3.04-13exp3.log.gz
Description: application/gzip

Re: Processed: reassign 952347 to libreoffice-dev, affects 952347

[Andreas Beckmann]

On 14/03/2020 09.51, Rene Engelhard wrote:
> Maybe split it out to a new libreoffice-dev-gui package or somesuch? (That 
> would need NEW though,
> and thus will only be done with the 7.0 packages)? But a tiny package just 
> for this tool... (that's why
> it was consumed in the -dev package.)
I'd go the libreoffice-gui-dev way, it will avoid this kind of confusion
in the future. Postponing to 7 (or any other reason to go through NEW)
is fine.

> Or Recommends: libreoffice-core, though that probably wouldn't be honoured by 
> sbuild
Yep, Recommends is not sufficient.

Since you already have a gengal wrapper script, you could check for
libreoffice-core being installed and error out with "please install
libreoffice-core instead of libreoffice-core-nogui to use this tool"
instead of failing with a weird missing symbol.

Andreas

Bug#952355: minlog: FTBFS: pdflatex error

[Andreas Beckmann]

Control: tag -1 unreproducible
Control: close -1

On Sun, 23 Feb 2020 14:48:21 +0100 Lucas Nussbaum  wrote:
> Source: minlog
> Version: 4.0.99.20100221-6
> Usertags: ftbfs-20200222 ftbfs-bullseye

> > pdflatex mpcref.tex >> /dev/null
> > make[2]: *** [Makefile:19: mpcref.pdf] Error 1

I cannot reproduce this in bullseye/sid as of today. There has been a
texlive upload inbetween, so this was probably a texlive bug.
I'm not going to investigate further but close this bug now.
Feel free to reopen if you can still reproduce it in your setup.

Andreas

Bug#943994: python3-zeitgeist not compatible with python3

[Andreas Beckmann]

Hi Boyuan,

On Wed, 22 Jan 2020 16:17:37 -0500 Boyuan Yang  wrote:
> No idea why. Looks like we need to have python3-zeitgeist removed eventually.
> 
> However before that, I'm going for a workaround: Upload an experimental
> version with higher version string, e.g., 1.0.2+py3-0.

That happened, ...

> After that, upload
> 1.0.2-3 onto Sid with python3-zeitgeist removed. This would keep binary
> package python3-zeitgeist in development repositories so that we do not need
> to go through NEW queue for another time if we really need that in the future.

... but instead of dropping the python3 package you fixed it in an
upload to unstable the other day ;-) (at least fixed it to the point
where it is installable again).

Can we now just remove the broken version from experimental again?


Andreas

Bug#949384: sendmail: milter expansion of "$b" macro is unreliable

[Andreas Beckmann]

Control: tag -1 upstream
Control: found -1 8.15.2-8

Hi Bjørn,

interesting problem.

On Mon, 20 Jan 2020 14:26:27 +0100 =?utf-8?Q?Bj=C3=B8rn_Mork?=
 wrote:
> The bug is that sendmail returns sendmail process start time instead of
> current time when milters request the "$b" macro ("The current date in
> RFC822 format").  This happens often, but not on every milter excution.
> Sometimes the correct current time is returned. I do not know the exact
> trigger...

>From your timestamps it looks a bit like the first one of some "batch"
gets the correct time, but any subsequent ones the wrong one. A "batch"
could be multiple recipients in a message or multiple messages received
in a single smtp connection. The wallclock timestamps are quite tight
within such a "batch": e.g. 13:51:02-13:52:28, 14:06:49-14:08:03
Your mail logfiles might reveal more of the nature of these batches (but
you probably should not post them publically!)

You could try your luck upstream at
sendmail-bugs-2...@support.sendmail.org
I hope that these addresses still work after sendmail changing ownership.
Please keep this bug in Cc:

Andreas

Bug#947360: coinor-libdylp-dev: ships headers owned by coinor-libcoinutils-dev, coinor-libosi-dev

[Andreas Beckmann]

Package: coinor-libdylp-dev
Version: 1.10.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages.

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...):

  Selecting previously unselected package coinor-libdylp-dev.
  Preparing to unpack .../coinor-libdylp-dev_1.10.4-1_amd64.deb ...
  Unpacking coinor-libdylp-dev (1.10.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/coin/CoinAlloc.hpp', which is also in 
package coinor-libcoinutils-dev 2.11.3+repack1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb

  Selecting previously unselected package coinor-libdylp-dev.
  Preparing to unpack .../coinor-libdylp-dev_1.10.4-1_amd64.deb ...
  Unpacking coinor-libdylp-dev (1.10.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/coin/OsiAuxInfo.hpp', which is also in 
package coinor-libosi-dev 0.108.5+repack1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb


cheers,

Andreas


coinor-libcoinutils-dev=2.11.3+repack1-1_coinor-libdylp-dev=1.10.4-1.log.gz
Description: application/gzip

Bug#945773: Unnecessary debug message logged at info level on shutdown

[Andreas Beckmann]

On 28/11/2019 13.39, David Bürgin wrote:
> Given all this, I want to propose changing the log level of this message
> to debug (SMI_LOG_DEBUG), guarded by ‘if (dbg > 0)’ as elsewhere.

Your reasoning sounds plausible. Can you provide a patch?

Andreas

Bug#945381: python3-bcolz: missing Breaks+Replaces: python-bcolz

[Andreas Beckmann]

Package: python3-bcolz
Version: 1.2.1+ds2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' 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 .../python3-bcolz_1.2.1+ds2-4_amd64.deb ...
  Unpacking python3-bcolz (1.2.1+ds2-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-bcolz_1.2.1+ds2-4_amd64.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/python3-bcolz/tutorials/tutorial_carray.ipynb', which is also 
in package python-bcolz 1.2.1+ds2-2+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-bcolz_1.2.1+ds2-4_amd64.deb


cheers,

Andreas


python-bcolz=1.2.1+ds2-2+b1_python3-bcolz=1.2.1+ds2-4.log.gz
Description: application/gzip

Bug#945318: roger-router: FTBFS against current evolution-data-server

[Andreas Beckmann]

Source: roger-router
Version: 1.8.14-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

roger-router FTBFS against the current evolution-data-server version in
sid:
https://buildd.debian.org/status/package.php?p=roger-router=unstable

First error:

evolution.c:478:8: error: too few arguments to function 
‘e_book_client_remove_contact_by_uid_sync’
  478 |  ret = e_book_client_remove_contact_by_uid_sync(client, contact->priv, 
NULL, NULL);
  |^~~~
In file included from /usr/include/evolution-data-server/libebook/libebook.h:27,
 from evolution.c:37:
/usr/include/evolution-data-server/libebook/e-book-client.h:212:10: note: 
declared here
  212 | gboolean e_book_client_remove_contact_by_uid_sync
  |  ^~~~


Andreas

Bug#943523: xpdf: FTBFS: build/PDFCore.cc:311:37: error: no matching function for call to 'PDFDoc::findPage(Ref&)'

[Andreas Beckmann]

Source: xpdf
Version: 3.04-13exp2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

xpdf/experimental FTBFS on all architectures:
https://buildd.debian.org/status/package.php?p=xpdf=experimental

 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
cp goo/gfile.h xpdf/xfile.h
sed -e s/GFILE/XFILE/g -i xpdf/xfile.h
cp goo/gfile.cc xpdf/xfile.cc
sed -e s/GFILE/XFILE/g -i xpdf/xfile.cc
cp xpdf/GlobalParams.h xpdf/XPDFParams.h
sed -e s/globalParams/xpdfParams/g -e s/GlobalParams/XPDFParams/g \
-e s/GLOBALPARAMS/XPDFPARAMS/g -e s/popplerParams/globalParams/g \
-e s/PopplerParams/GlobalParams/g \
-i xpdf/XPDFParams.h
cp xpdf/GlobalParams.cc xpdf/XPDFParams.cc
sed -e s/globalParams/xpdfParams/g -e s/GlobalParams/XPDFParams/g \
-e s/GLOBALPARAMS/XPDFPARAMS/g -e s/popplerParams/globalParams/g \
-e s/PopplerParams/GlobalParams/g \
-i xpdf/XPDFParams.cc
mkdir -p build
cp goo/parseargs.c goo/parseargs.h xpdf/CoreOutputDev.cc xpdf/CoreOutputDev.h 
xpdf/PDFCore.cc xpdf/PDFCore.h xpdf/XPDFApp.cc xpdf/XPDFApp.h xpdf/XPDFCore.cc 
xpdf/XPDFCore.h xpdf/XPDFParams.cc xpdf/XPDFParams.h xpdf/XPDFTree.cc 
xpdf/XPDFTree.h xpdf/XPDFViewer.cc xpdf/XPDFViewer.h xpdf/xfile.cc xpdf/xfile.h 
xpdf/xpdf.cc xpdf/config.h xpdf/XPDFTreeP.h xpdf/about-text.h xpdf/*.xbm 
xpdf/xpdfIcon.xpm build
sed -E -e s/GString/GooString/g -e s/GMutex/GooMutex/g -e s/GHash/GooHash/g \
-e s/GList/GooList/g -e s/\/\/g \
-e s/GBool/bool/g -e s/gTrue/true/g -e s/gFalse/false/g \
-e 's/deleteGooList\(([^,]+), ([^)]+)\);/deleteGooList<\2> \(\1\);/' \
-i build/*
mv build/parseargs.c build/parseargs.cc
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/poppler -I/usr/include/poppler/goo 
-I/usr/include/poppler/splash -Wno-write-strings -Wno-format-extra-args 
-Wfatal-errors -DHAVE_DIRENT_H -DHAVE_PAPER_H 
-DSYSTEM_XPDFRC=\"/etc/xpdf/xpdfrc\"  -c -o build/CoreOutputDev.o 
build/CoreOutputDev.cc
x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/poppler -I/usr/include/poppler/goo 
-I/usr/include/poppler/splash -Wno-write-strings -Wno-format-extra-args 
-Wfatal-errors -DHAVE_DIRENT_H -DHAVE_PAPER_H 
-DSYSTEM_XPDFRC=\"/etc/xpdf/xpdfrc\"  -c -o build/PDFCore.o build/PDFCore.cc
build/PDFCore.cc: In member function 'virtual void 
PDFCore::displayDest(LinkDest*, double, int, bool)':
build/PDFCore.cc:311:37: error: no matching function for call to 
'PDFDoc::findPage(Ref&)'
 topPageA = doc->findPage(pageRef);
 ^
compilation terminated due to -Wfatal-errors.
make[1]: *** [: build/PDFCore.o] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:50: build-arch] Error 2


Andreas

Bug#943517: boxbackup: FTBFS with test failures

[Andreas Beckmann]

Package: boxbackup
Version: 0.13~~git20190527.g039c4a1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

boxbackup/experimental FTBFS in my sid/experimental pbuilder environment
on amd64 and i386. This seems to be a recent regression, since earlier
builds of that version have succeeded.

Unfortunately I can't tell from the buildlog which error is the actual
failure and which errors are expected for some tests.


Andreas


boxbackup_0.13~~git20190527.g039c4a1-2.log.gz
Description: application/gzip

Bug#942040: tstools: /usr/bin/tsfilter is already provided by opencaster

[Andreas Beckmann]

Package: tstools
Version: 1.13~git20151030-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package tstools.
  Preparing to unpack .../tstools_1.13~git20151030-1_amd64.deb ...
  Unpacking tstools (1.13~git20151030-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/tstools_1.13~git20151030-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/tsfilter', which is also in package opencaster 
3.2.2+dfsg-1.1+b1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/tstools_1.13~git20151030-1_amd64.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

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):

  usr/bin/tsfilter
  usr/share/man/man1/tsfilter.1.gz

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


opencaster=3.2.2+dfsg-1.1+b1_tstools=1.13~git20151030-1.log.gz
Description: application/gzip

Bug#940207: python3-zc.buildout: missing Breaks+Replaces: python-zc.buildout

[Andreas Beckmann]

Package: python3-zc.buildout
Version: 2.13.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' 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...):

  Selecting previously unselected package python3-zc.buildout.
  Preparing to unpack .../python3-zc.buildout_2.13.2-3_all.deb ...
  Unpacking python3-zc.buildout (2.13.2-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-zc.buildout_2.13.2-3_all.deb (--unpack):
   trying to overwrite '/usr/bin/buildout', which is also in package 
python-zc.buildout 1.7.1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-zc.buildout_2.13.2-3_all.deb


cheers,

Andreas


python-zc.buildout=1.7.1-1_python3-zc.buildout=2.13.2-3.log.gz
Description: application/gzip

Bug#939620: python3-zope.testrunner: missing Breaks+Replaces: python-zope.testrunner

[Andreas Beckmann]

Package: python3-zope.testrunner
Version: 4.4.9-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' 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 .../python3-zope.testrunner_4.4.9-2_all.deb ...
  Unpacking python3-zope.testrunner (4.4.9-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-zope.testrunner_4.4.9-2_all.deb (--unpack):
   trying to overwrite '/usr/bin/zope-testrunner', which is also in package 
python-zope.testrunner 4.4.9-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-zope.testrunner_4.4.9-2_all.deb


cheers,

Andreas


python-zope.testrunner=4.4.9-1_python3-zope.testrunner=4.4.9-2.log.gz
Description: application/gzip

Bug#406668: pine and ajaxterm terminal issue

[Andreas Beckmann]

Followup-For: Bug #406668
Control: reopen -1
Control: reassign -1 alpine

ajaxterm has been removed from Debian, reassigning to alpine only.


Andreas

Bug#933524: python-libpcap: fails to install: Sorry: IndentationError: expected an indented block (pcap.py, line 115)

[Andreas Beckmann]

Package: python-libpcap
Version: 0.6.4-1
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up python-libpcap (0.6.4-1+b1) ...
  Sorry: IndentationError: expected an indented block (pcap.py, line 115)
  dpkg: error processing package python-libpcap (--configure):
   installed python-libpcap package post-installation script subprocess 
returned error exit status 101
  Processing triggers for libc-bin (2.28-10) ...
  Errors were encountered while processing:
   python-libpcap


cheers,

andreas


python-libpcap_0.6.4-1+b1.log.gz
Description: application/gzip

Bug#932598: Upgrade to buster fails with start-stop-daemon error

[Andreas Beckmann]

Hi Ron,

On 21/07/2019 05.42, Ron Murray wrote:
> On upgrade to buster, sendmail upgrade failed with this message:
> 
>> start-stop-daemon: matching only on non-root pidfile 
>> /var/run/sendmail/mta/sendmail.pid is insecure
> 
> Some work with Google found Debian bug #922395, which, although not
> for sendmail, pointed the way to the solution.

I've just uploaded sendmail 8.15.2-13 to unstable, it would be great if
you could test this s.t. I have a datapoint whether this fix should be
applied to buster, too.

Thanks

Andreas

Bug#931902: cflow-doc,cflow-l10n: missing Breaks+Replaces: cflow (<< 1:1.6-2)

[Andreas Beckmann]

Package: cflow-doc,cflow-l10n
Version: 1:1.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files 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 .../cflow-doc_1%3a1.6-2_all.deb ...
  Unpacking cflow-doc (1:1.6-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cflow-doc_1%3a1.6-2_all.deb (--unpack):
   trying to overwrite '/usr/share/info/cflow.info.gz', which is also in 
package cflow 1:1.6-1
  Errors were encountered while processing:
   /var/cache/apt/archives/cflow-doc_1%3a1.6-2_all.deb

  Preparing to unpack .../cflow-l10n_1%3a1.6-2_all.deb ...
  Unpacking cflow-l10n (1:1.6-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cflow-l10n_1%3a1.6-2_all.deb (--unpack):
   trying to overwrite '/usr/share/locale/da/LC_MESSAGES/cflow.mo', which is 
also in package cflow 1:1.6-1
  Errors were encountered while processing:
   /var/cache/apt/archives/cflow-l10n_1%3a1.6-2_all.deb


cheers,

Andreas


cflow=1:1.6-1_cflow-doc=1:1.6-2.log.gz
Description: application/gzip

Bug#928127: xpdf: FTBFS in experimental

[Andreas Beckmann]

Source: xpdf
Version: 3.04-13exp1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

xpdf/experimental FTBFS on all architectures:

https://buildd.debian.org/status/package.php?p=xpdf=experimental

build/XPDFApp.cc: In member function 'void XPDFApp::remoteOpen(GooString*, int, 
bool)':
build/XPDFApp.cc:362:20: error: 'const _CharT* 
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::c_str() const [with _CharT 
= char; _Traits = std::char_traits; _Alloc = std::allocator]' is 
inaccessible within this context
fileName->c_str(), page);
^

Andreas

Bug#924221: syslinux-themes-debian-{squeeze,wheezy}: syslinux-common has changed the filesystem layout

[Andreas Beckmann]

Package: syslinux-themes-debian-squeeze,syslinux-themes-debian-wheezy
Version: 12-4
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m20.1s ERROR: FAIL: Broken symlinks:
  /usr/share/syslinux/themes/debian-squeeze/extlinux/hdt.c32 -> 
../../../../../lib/syslinux/hdt.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/extlinux/reboot.c32 -> 
../../../../../lib/syslinux/reboot.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/extlinux/rosh.c32 -> 
../../../../../lib/syslinux/rosh.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/extlinux/config.c32 -> 
../../../../../lib/syslinux/config.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/extlinux/vesamenu.c32 -> 
../../../../../lib/syslinux/vesamenu.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/isolinux-live/hdt.c32 -> 
../../../../../lib/syslinux/hdt.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/isolinux-live/reboot.c32 -> 
../../../../../lib/syslinux/reboot.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/isolinux-live/isolinux.bin -> 
../../../../../lib/syslinux/isolinux.bin (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/isolinux-live/rosh.c32 -> 
../../../../../lib/syslinux/rosh.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/isolinux-live/config.c32 -> 
../../../../../lib/syslinux/config.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/isolinux-live/vesamenu.c32 -> 
../../../../../lib/syslinux/vesamenu.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/syslinux-live/hdt.c32 -> 
../../../../../lib/syslinux/hdt.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/syslinux-live/reboot.c32 -> 
../../../../../lib/syslinux/reboot.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/syslinux-live/isolinux.bin -> 
../../../../../lib/syslinux/isolinux.bin (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/syslinux-live/rosh.c32 -> 
../../../../../lib/syslinux/rosh.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/syslinux-live/config.c32 -> 
../../../../../lib/syslinux/config.c32 (syslinux-themes-debian-squeeze)
  /usr/share/syslinux/themes/debian-squeeze/syslinux-live/vesamenu.c32 -> 
../../../../../lib/syslinux/vesamenu.c32 (syslinux-themes-debian-squeeze)


syslinux-common now provides the files at these locations:

/usr/lib/syslinux/modules/bios/config.c32
/usr/lib/syslinux/modules/bios/hdt.c32
/usr/lib/syslinux/modules/bios/reboot.c32
/usr/lib/syslinux/modules/bios/rosh.c32
/usr/lib/syslinux/modules/bios/vesamenu.c32
/usr/lib/syslinux/modules/efi32/config.c32
/usr/lib/syslinux/modules/efi32/hdt.c32
/usr/lib/syslinux/modules/efi32/reboot.c32
/usr/lib/syslinux/modules/efi32/rosh.c32
/usr/lib/syslinux/modules/efi32/vesamenu.c32
/usr/lib/syslinux/modules/efi64/config.c32
/usr/lib/syslinux/modules/efi64/hdt.c32
/usr/lib/syslinux/modules/efi64/reboot.c32
/usr/lib/syslinux/modules/efi64/rosh.c32
/usr/lib/syslinux/modules/efi64/vesamenu.c32


cheers,

Andreas


syslinux-themes-debian-squeeze_12-4.log.gz
Description: application/gzip

Bug#921527: cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el

[Andreas Beckmann]

Control: tag -1 - patch moreinfo

On 2019-02-07 13:59, Thierry fa...@linux.ibm.com wrote:
> Hi,
> Sorry - I am not proposing a patch (may have write a bad bug header).

OK, fixing the metadata.


Andreas

Bug#921527: cuneiform_1.1.0+dfsg-7 - FTBFS on ppc64el

[Andreas Beckmann]

Control: severity -1 important
Control: tag -1 moreinfo

We currently have no ppc64el binaries for cuneiform, so this is not a
regressions and therefore not RC.

On Wed, 6 Feb 2019 14:50:47 +0100 "Thierry fa...@linux.ibm.com"
 wrote:
> --- images/phototest.tif.txt  2011-04-19 12:49:57.0 +
> +++ /tmp/cuneiform.test.KgXcP8dD/phototest.tif.out2018-01-14 
> 03:21:46.536688277 +
> @@ -1,7 +1,7 @@
> -This is a lot of 12 point text to test the 
> -ocr code and see if it works on all types 
> +This is a lot of 12 poiet text to test the 
> +ocr code aed see if it works oe all types 
>  of file format. 

Wouldn't that patch break the test for all platforms where it currently
passes?

Andreas

Bug#919850: python3-link-grammar: broken symlink: /usr/lib/python3.7/site-packages/linkgrammar/_clinkgrammar.so -> _clinkgrammar.so.5.5.1

[Andreas Beckmann]

Package: python3-link-grammar
Version: 5.5.1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m41.0s ERROR: FAIL: Broken symlinks:
  /usr/lib/python3.7/site-packages/linkgrammar/_clinkgrammar.so -> 
_clinkgrammar.so.5.5.1 (python3-link-grammar)

But there is 

  /usr/lib/python3/dist-packages/linkgrammar/_clinkgrammar.so.5.5.1

so this seems to be a site-packages/dist-packages mixup.


cheers,

Andreas


python3-link-grammar_5.5.1-5.log.gz
Description: application/gzip

Bug#915742: simba: fails to purge - command ucf in postrm not found

[Andreas Beckmann]

Package: simba
Version: 0.8.4-5
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to purge due
to a command not found. According to policy 7.2 you cannot rely on the
depends being available during purge, only the essential packages are
available for sure.

Please see the manpages ucf(1), ucfr(1) and the example maintainer
scripts under /usr/share/doc/ucf/examples/ for correct usage of ucf.

Filing this as important because a.) it's a clear policy violation (to
not clean up at purge) b.) having a piuparts clean archive is a release
goal since lenny and c.) this package being piuparts buggy blocks
packages depending on it from being tested by piuparts (and thus
possibly the detection of more severe problems).

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

0m56.0s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts/tmp/tmp1sQcO0', 'dpkg', '--purge', 'simba']
  (Reading database ... 4459 files and directories currently installed.)
  Purging configuration files for simba (0.8.4-5) ...
  /var/lib/dpkg/info/simba.postrm: 27: /var/lib/dpkg/info/simba.postrm: ucf: 
not found
  dpkg: error processing package simba (--purge):
   installed simba package post-removal script subprocess returned error exit 
status 127
  Errors were encountered while processing:
   simba


cheers,

Andreas


simba_0.8.4-5.log.gz
Description: application/gzip

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#873156: fofix: FoFiX.py rises a NotImplementedError on startup

[Andreas Beckmann]

Control: tag -1 - patch

On Fri, 25 Aug 2017 06:15:51 +0200 Christian Trenkwalder 
 wrote:
> Dear Maintainer,

The fofix package unfortunately has no maintainer any more.
https://bugs.debian.org/836421

> after installing the fofix package on a (up-to-date) system, 
> the application terminates due to unhandlet exception.
> This is caused by the usage of the removed 'tostring()' within python and 
> python suggests 'tobytes()' should be used instead. 

Confirmed in stretch.
Can't reproduce in sid, since the package is not installable
due to python-imaging being gone. Installing python-imaging from
stretch in sid is possible, but results in different errors.

> After replacing the tostring() calls with tobytes() as suggested, 
> the application becomes usable.
> 
> I have attached a diff at the end of the report.

There seem to be more occurrences of tostring in the source than
the ones updated by your patch, do they need updating, too?
Are the objects touched by your patch actally of the same problematic
type? The signatures of the tostring() methods seems to differ.
But I didn't dig deep...

src/Shader.py:508:  noise = pygame.image.tostring(img, "RGB")
src/Texture.py:77:  string = image.tostring('raw', 'RGBA', 0, -1)
src/Texture.py:80:  string = image.tostring('raw', 'RGB', 0, -1)
src/Texture.py:83:  string = image.tostring('raw', 'L', 0, -1)
src/Texture.py:89:string = image.tostring('raw', 'RGB', 0, -1)
src/Texture.py:114:  string = pygame.image.tostring(surface, "RGB")
src/Texture.py:116:  string = image.tostring('raw', 'L', 0, -1)
src/Texture.py:120:string = pygame.image.tostring(surface, "RGBA", True)
src/Texture.py:123:string = pygame.image.tostring(surface, "RGB", True)
src/Texture.py:133:  string = pygame.image.tostring(surface, "RGB")
src/Texture.py:135:  string = image.tostring('raw', 'L', 0, -1)
src/Texture.py:139:string = pygame.image.tostring(surface, "RGBA", True)
src/Texture.py:142:string = pygame.image.tostring(surface, "RGB", True)
src/Video.py:114:  bigIconColorData = bigIcon.tostring()
src/Video.py:115:  bigIconMaskData = bigIcon.split()[3].point(lambda p: 255 
- p).convert('1').tostring()
src/Video.py:116:  smallIconColorData = smallIcon.tostring()
src/Video.py:117:  smallIconMaskData = smallIcon.split()[3].point(lambda p: 
255 - p).convert('1').tostring()
src/FontTest.py:134:letter = pygame.image.tostring(letter_render, 'RGBA', 1)

There is not much point fixing this without fixing
https://bugs.debian.org/866423
i.e. switching from python-imaging to e.g. python-pil
which may require interface adaptations as well.


Andreas

Bug#906412: svn-buildpackage: FTBFS in buster/sid (po4a-build: Command not found)

[Andreas Beckmann]

On Sat, 25 Aug 2018 14:21:54 +0200 Johannes Schauer 
wrote:
> Upstream version 0.54 of po4a removed po4a-build:

> Since it is unclear to me what the correct replacement for po4a-build is, I
> contacted upstream about it:
> 
> https://github.com/mquinson/po4a/issues/144
> 
> Since this bug is also still unfixed, I thought that this information might be
> helpful for you as well. :)

For svn-buildpackage I'll just include a copy of po4a-build ... without
trying to understand it. Should be sufficient to keep the ancient
package alive for another release.


Andreas

Bug#906112: closed by Niels Thykier (Bug#906112: fixed in libcdio-paranoia 10.2+0.94+2-4)

[Andreas Beckmann]

On 2018-08-14 21:27, Debian Bug Tracking System wrote:
>* Remove cd-paranoia package again; the binary is also provided by
>  libcdio-utils.  (Reopens: #889803, Closes: #906112)

Nope, it is no longer provided by libcdio-utils >= 0.92

This was an issue upgrading from stretch.


Andreas

Bug#906112: cd-paranoia: missing Breaks+Replaces: libcdio-utils (<< 0.92)

[Andreas Beckmann]

Package: cd-paranoia
Version: 10.2+0.94+2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' 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/#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../cd-paranoia_10.2+0.94+2-3_amd64.deb ...
  Unpacking cd-paranoia (10.2+0.94+2-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/cd-paranoia_10.2+0.94+2-3_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/cd-paranoia', which is also in package 
libcdio-utils 0.83-4.3+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/cd-paranoia_10.2+0.94+2-3_amd64.deb


BTW, libcdio-utils still mentions cd-paranoia in its long description.


cheers,

Andreas


libcdio-utils=0.83-4.3+b1_cd-paranoia=10.2+0.94+2-3.log.gz
Description: application/gzip

Bug#905197: libcue-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: libcue-dev
Version: 2.2.1-1
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...):

0m28.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libcue-dev/changelog.Debian.gz (libcue-dev:amd64) != 
/usr/share/doc/libcue1/changelog.Debian.gz (libcue1)
/usr/share/doc/libcue-dev -> libcue1
  /usr/share/doc/libcue-dev/changelog.gz (libcue-dev:amd64) != 
/usr/share/doc/libcue1/changelog.gz (libcue1)
/usr/share/doc/libcue-dev -> libcue1
  /usr/share/doc/libcue-dev/copyright (libcue-dev:amd64) != 
/usr/share/doc/libcue1/copyright (libcue1)
/usr/share/doc/libcue-dev -> libcue1


cheers,

Andreas


libcue-dev_2.2.1-1.log.gz
Description: application/gzip

Bug#902221: bochs: depends on vgabios which has been requested to be removed

[Andreas Beckmann]

Package: bochs
Version: 2.6-5
Severity: important
Tags: sid buster
Control: block 895046 with -1

Hi,

bochs depends on vgabios which has been requested to be removed:
https://bugs.debian.org/895046

qemu, which also used vgabios in the past, has switched to seabios long
ago - perhaps that's an option for bochs, too.


Andreas

Bug#901189: timidity,timidity-el: both packages ship the manpages

[Andreas Beckmann]

Package: timidity,timidity-el
Version: 2.14.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package timidity-el.
  Preparing to unpack .../timidity-el_2.14.0-2_all.deb ...
  Unpacking timidity-el (2.14.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/timidity-el_2.14.0-2_all.deb (--unpack):
   trying to overwrite '/usr/share/man/ja/man1/timidity.1.gz', which is also in 
package timidity 2.14.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/timidity-el_2.14.0-2_all.deb

The following files are shipped by both packages:

usr/share/man/ja/man1/timidity.1.gz
usr/share/man/ja/man5/timidity.cfg.5.gz
usr/share/man/man1/timidity.1.gz
usr/share/man/man5/timidity.cfg.5.gz


cheers,

Andreas


timidity=2.14.0-2_timidity-el=2.14.0-2.log.gz
Description: application/gzip

Bug#895082: sendmail: Please replace 'c_rehash' with 'openssl rehash'

[Andreas Beckmann]

On 2018-04-07 00:48, Sebastian Andrzej Siewior wrote:
> Should the c_rehash script be mentioned in the source code or script
> of this package but is not used during the build process or in the
> final package then feel free to close the bug saying so.

The only occurrence I could find is in some documentation:

./doc/op/op.me:
...
A better way to do this is to use the
.b c_rehash
command that is part of the OpenSSL distribution
because it handles subject hash collisions
by incrementing the number in the suffix of the filename of the symbolic
link,
e.g.,
.b \&.0
to
.b \&.1 ,
and so on.
...

Should I change that sentence? How?


Andreas

Bug#894535: sendmail: Typo in apt show sendmail

[Andreas Beckmann]

Control: tag -1 pending

On 2018-04-01 05:24, annadane wrote:
> Paragraph "Fortunately, simple thing can be done easily, and complex things
>  are possible, even if not easily understood ;)  Sendmail is the *ONLY*
>  MTA with a Turing complete language to control *ALL* aspects of delivery!"
> 
> "Thing" should read "things"

Thanks, fixed in GIT.


Andreas

Accepted sendmail 8.15.2-11 (source) into unstable

[Andreas Beckmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Mar 2018 00:49:16 +0100
Source: sendmail
Binary: sendmail-bin rmail sensible-mda libmilter1.0.1 libmilter-dev 
sendmail-doc sendmail sendmail-base sendmail-cf
Architecture: source
Version: 8.15.2-11
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Andreas Beckmann <a...@debian.org>
Description:
 libmilter-dev - Sendmail Mail Filter API (Milter) (development files)
 libmilter1.0.1 - Sendmail Mail Filter API (Milter)
 rmail  - MTA->UUCP remote mail handler
 sendmail   - powerful, efficient, and scalable Mail Transport Agent (metapacka
 sendmail-base - powerful, efficient, and scalable Mail Transport Agent (arch 
inde
 sendmail-bin - powerful, efficient, and scalable Mail Transport Agent
 sendmail-cf - powerful, efficient, and scalable Mail Transport Agent (config ma
 sendmail-doc - powerful, efficient, and scalable Mail Transport Agent 
(documenta
 sensible-mda - Mail Delivery Agent wrapper
Closes: 893424
Changes:
 sendmail (8.15.2-11) unstable; urgency=medium
 .
   * QA upload.
   * Fix prerm failure on btrfs.  (Closes: #893424)
   * Convert upstream signing key to .asc format.
   * sendmail-doc: Mark as Multi-Arch: foreign.
   * libmilter-dev: Mark as Multi-Arch: same.
   * Fix new Lintian issues.
   * Update Lintian overrides.
   * Switch Vcs-* URLs to salsa.debian.org.
Checksums-Sha1:
 63d5a377305d12b177d22d158a960f1779649a72 2565 sendmail_8.15.2-11.dsc
 43fe34b71f0290178e942aca7f3a1f02c07b2ea1 412772 
sendmail_8.15.2-11.debian.tar.xz
 a1cb9de19bfdf2648c89a23649b16a4d32372698 6075 
sendmail_8.15.2-11_source.buildinfo
Checksums-Sha256:
 64c2938900a489b3f928c3dc2c5ff6f3da88510c5292305e7ec5d89e9ee87e1c 2565 
sendmail_8.15.2-11.dsc
 48932758d4d4ec3afe050d724f8b7e1c5ee1648db9d2a100ec76966b8d40a066 412772 
sendmail_8.15.2-11.debian.tar.xz
 abf24ef33dd75d8e3bbf9579d38f12e4e54ba3f9a351b84d2a5f463307d3edcf 6075 
sendmail_8.15.2-11_source.buildinfo
Files:
 0511d2da05fe99dcf0952b62920a7a23 2565 mail optional sendmail_8.15.2-11.dsc
 43648c3c14d7be14772d65f736aed4b2 412772 mail optional 
sendmail_8.15.2-11.debian.tar.xz
 1ce1e9a827a143968b5b865f13353f77 6075 mail optional 
sendmail_8.15.2-11_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlqwTa8QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCL1aD/9NGIUV095eLOYZtChSjVEamMkGcdv6Q8T1
VcccKE97fxUynb8nleD7XXzUqUg99r+/1+vR8mb+uxX4OPJBu1dUvSQIXHD+/3xw
BJ4b47g+sxfXsNl/mqulZfuJIST1MUu1vdt5Y7XP5koy3gOoMew+Qown/zkz3D0D
wj1TIj66+t5M5xmvM8mhNynBkWPMC/QKE5/VLQbZbc/xFDyuCscuF4VFYcKz7WAh
YHGnfkwEgBT7GZKFBDMX8MWMFbC5Tyerbt7xfMkJuL1TZnWdk9N/bhSZr0/BXV4C
7Cgn7KisrK08rWWkNMOmfnzFf310jLTx41OxbOoSeqXem4wewjjxppN8+pxOAJfV
f/N95tEfN+IhDqG/fwANZSzEkqktpGcPJLWb5Q6S9Pj7o0YcIi8mmzBemg2BuVMC
yzmC6zOMAQ53mSZdortRV+t3Q9V+Sg5j3wM9ojpDUoDX6YpuN49ae32jo22ZgqVk
3tWdpAx4zoO/aZlenC+hFJoq/u9zxsxtVB5JWmopwCJhClOHhzvcHs6KWrmJcJPc
cD4xq5Jl7UWEHKGElJYe3IOJYow0SqtSkRdvm+hktd9AZlBxws2HRL0EnakfBwJT
iwe4vgXhPZfYRhHVgs9cAXUEJxBFIjr3adr19btXxXeeZVTEeKuga+hA6tb9nsh1
fKc7NMMrSg==
=K1nu
-END PGP SIGNATURE-

Bug#893424: Cannot uninstall package

[Andreas Beckmann]

On 2018-03-18 19:43, Ryan Kavanagh wrote:
> Removing sendmail-base (8.15.2-10) ...
> rm: cannot remove '/etc/mail/m4': Is a directory
> dpkg: error processing package sendmail-base (--remove):
>  installed sendmail-base package pre-removal script subprocess returned error 
> exit status 123

> ls -alR /etc/mail:
> /etc/mail:
> total 24
> drwxr-xr-x 1 root root   138 Mar 18 14:32 .
> drwxr-xr-x 1 root root  5364 Mar 18 13:50 ..
> -rw-r--r-- 1 root root   281 Jan 13 17:43 address.resolve
> drwxr-xr-x 1 root root 0 Jan 13 17:43 m4

Interesting. The empty directory shows up with size 0.
What filesystem do you use for / ?

The error should be triggered by this line in the prerm:
# Remove empty files (probably touched databases)
find /etc/mail -maxdepth 1 -size 0 | xargs -r rm;

Please run these two commands:

$ find /etc/mail -maxdepth 1 -size 0
$ find /etc/mail -maxdepth 1 -type f -size 0

The first should output /etc/mail/m4, the second should output nothing.


Andreas

Accepted xchain 1.0.1-9~deb9u1 (source) into proposed-updates->stable-new, proposed-updates

[Andreas Beckmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Mar 2018 20:03:17 +0100
Source: xchain
Binary: xchain
Architecture: source
Version: 1.0.1-9~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Andreas Beckmann <a...@debian.org>
Description:
 xchain - strategy game for 2-4 players
Closes: 878090
Changes:
 xchain (1.0.1-9~deb9u1) stretch; urgency=medium
 .
   * QA upload.
   * Rebuild for stretch.
 .
 xchain (1.0.1-9) unstable; urgency=medium
 .
   * QA upload.
   * Revert path change, depend on "wish" only. Re-closes: #878090
 .
 xchain (1.0.1-8) unstable; urgency=medium
 .
   * QA upload.
   * Update path to wish (it's /usr/bin/wish8.5 now). Closes: #878090
   * Priority optional.
Checksums-Sha1:
 12d8613a4c9792bf46b56dcd3b352549653ebb5f 1831 xchain_1.0.1-9~deb9u1.dsc
 a5e07184c8fe8dbc79afc3d8a980003589cd18c8 6112 
xchain_1.0.1-9~deb9u1.debian.tar.xz
 f0174c7edbc4251c0c8a84f3c4fb5a4d56b477ef 5478 
xchain_1.0.1-9~deb9u1_source.buildinfo
Checksums-Sha256:
 567ad8c4d15fe7abaf3a0448c446fd323aa4aeef0e81bffbd4dc4cde18b29ae3 1831 
xchain_1.0.1-9~deb9u1.dsc
 0cbfa7dae36fa9c1b1e22c7db5bfa72f397aff6e37454b72ac8c72d05d7357e7 6112 
xchain_1.0.1-9~deb9u1.debian.tar.xz
 87ffdd4b15517b1e7a2a588e416f61b756ea05d59206313a9b1044e138e76168 5478 
xchain_1.0.1-9~deb9u1_source.buildinfo
Files:
 adcc1cb006f189110d060fdc3a5d263c 1831 games optional xchain_1.0.1-9~deb9u1.dsc
 1b7115be629fe64ace0e72c29ef2a051 6112 games optional 
xchain_1.0.1-9~deb9u1.debian.tar.xz
 ba95f99f217ae1f26194f20277aa6e27 5478 games optional 
xchain_1.0.1-9~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlqZolkQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCEC0D/9N9RYthwuDrohzClGIqTS2FHGayxqhSqTX
8H56rJeWSlNnMDg6qyFkT/Gj1P5687++ihUqsZVFwyzAEGlxGgJ6GMN4OxQKrFwQ
wdAy8fnFKBFTD+ln+AvLaSjRSsV22AiupX5K7iHjseaBG/UmWzrabrQoMDtvcCNt
IRbI5Q7ZimtXF6BnSst9ipK3GlPMnqctuwqRIHRqcVchDBwAfydPsKn/+uhm3xrM
SZxFemW79ZMrGi+QA/D1NZq+GgOfAfF93eZzy5OV28+YgPtZm2S/g8GnZO73hDW1
5oxuXR7ZM0jP82mVgrOIs3NOiSllE15ptGz7wXxdWDT3s688qwAShOdrV2peWgXN
H+yJFUX5kiJesZTNPxanlGB3UJierD+rK6BKRGsQ98Yvfhr9dG7pNOnLSJx+VfFr
FvBtFbIj+BjgDH7O/wRkIy6QQ5e8PA9Sf/aYoBwoJe+SRm1m+70LSr6auxAmhj72
QAOui2hFrRyOmFwdYeVvSMFeRRq9sXB3XeYcTZRGhMX9NEAaq2RuRVVK3DNJ1G2J
8yMZShAXikp/DQXzB70klGoQ3eFSwMQkSdz1vb3wCJYI69aq20Yo4yLJbFczG436
l8n0H1qsCOvqeApv0DJISCoI8IpzRYvXvndcn7ZQi7VFDjtzv/ZRVPHDJ34TSvbF
Zk8SHTVWDQ==
=NHn2
-END PGP SIGNATURE-

Accepted python-spake2 0.7-3~deb9u1 (source) into proposed-updates->stable-new, proposed-updates

[Andreas Beckmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Jan 2018 00:16:34 +0100
Source: python-spake2
Binary: python-spake2 python3-spake2
Architecture: source
Version: 0.7-3~deb9u1
Distribution: stretch
Urgency: high
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Andreas Beckmann <a...@debian.org>
Description:
 python-spake2 - SPAKE2 password-authenticated key exchange (pure python)
 python3-spake2 - SPAKE2 password-authenticated key exchange (pure python)
Closes: 867457
Changes:
 python-spake2 (0.7-3~deb9u1) stretch; urgency=medium
 .
   * QA upload.
   * Rebuild for stretch.
 .
 python-spake2 (0.7-3) unstable; urgency=high
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #833947)
   * Fix the python3-spake2 dependencies. (Closes: #867457)
Checksums-Sha1:
 4038e14f9ef6e815049a76d0e71557f09656e1a3 1987 python-spake2_0.7-3~deb9u1.dsc
 fa2859bd9719d1ec4dc784606fe20f0163ee5a3a 2484 
python-spake2_0.7-3~deb9u1.debian.tar.xz
 80b66f3bb81e0b8eecd0c891fa17f79e7f263909 6299 
python-spake2_0.7-3~deb9u1_source.buildinfo
Checksums-Sha256:
 3deef9e2fe24f263a3f7b35aecf2e20a014c120ec1ec52d7a826b9faf9efbb7f 1987 
python-spake2_0.7-3~deb9u1.dsc
 be01e021750f567476b3241034f5c1e29bd2c86b7d4e7651c6bab7dd7f446467 2484 
python-spake2_0.7-3~deb9u1.debian.tar.xz
 07ec7e26d1283a78b608d52ad8ea2d42effd8ab9721a0553ad5387e1c1005cfe 6299 
python-spake2_0.7-3~deb9u1_source.buildinfo
Files:
 4ceb3c6733c0fdf25a6d0feadeebf0d6 1987 python optional 
python-spake2_0.7-3~deb9u1.dsc
 660a237c6200424f69046a0c37823c1c 2484 python optional 
python-spake2_0.7-3~deb9u1.debian.tar.xz
 75dd4ac77eb1e7812d09fdd4c92f625d 6299 python optional 
python-spake2_0.7-3~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpalIAQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCLnJD/9XqgYqJ/cnA3+3V7SBRFZN3EXAz6XSROMg
doWSxxYe9lHg9o8ddm84GrT1T6WZAuHRGwApisCcKHvHzwILwohSL308KDv2Utrm
qLGSSYF9UmATy1qx8+UFUTPzB6Vnnu3LpuXf+qPZCe9Cu1YJvnUKw/VgxzyW0VmX
+fsdPdodBtAT8YR/44qNHfFPCpYlfKbcsRVNN7oB9Jr+cH0sA+MU97F7AQ968rzi
Q7EbbU9cKLPaVEKhkkYU2gIBi40Um2nrVOkeXAviIEEsGNuIYQkIVdHksL+dIOWK
11KgLRBjFhF0JqhGj7ucgM+UxRmjeB+HQei5jn3+d0pt6/l7MnGbXJa0Q+IE09S4
sce4R7gNSFa3L0xHuegIy5EnG97mKkNwf5Szp4TFdt+xs69Wrub26EHgjP4bHWBm
c8e8boLq1mjxKO7FrnMVwcIhFjKXQepbMR/23ZAXEpvtf8q1Qx746NVSQjSIZuNe
mhg0oYsF0io2taFiuInM7s1kfmcmSzF6J0kIMAXEuZthmYNna4sMIs0qe5S8MdM9
MZEpstDO4CHMUvEWxRLohiVazVBMN4Ot0cNIQKnQ9Tr8206S/jpg8GvkYG1Rmv1w
T2YYi+Odv9EuFIxtCHoOxmq5rsiSf/7uEws8Vh7pReTnIW9jEsm1JVgLU8BeHLxz
KDqqS3EsRA==
=H/N5
-END PGP SIGNATURE-

Accepted python-hkdf 0.0.3-3~deb9u1 (source) into proposed-updates->stable-new, proposed-updates

[Andreas Beckmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 14 Jan 2018 00:25:36 +0100
Source: python-hkdf
Binary: python-hkdf python3-hkdf
Architecture: source
Version: 0.0.3-3~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Andreas Beckmann <a...@debian.org>
Description:
 python-hkdf - HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
 python3-hkdf - HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
Closes: 864149 867433
Changes:
 python-hkdf (0.0.3-3~deb9u1) stretch; urgency=medium
 .
   * QA upload.
   * Rebuild for stretch.
 .
 python-hkdf (0.0.3-3) unstable; urgency=medium
 .
   * QA upload.
   * Fix the python3-hkdf dependencies. (Closes: #867433)
 .
 python-hkdf (0.0.3-2) unstable; urgency=medium
 .
   * Add missing URL to package descriptions.  closes: #864149.
   * Set maintainer to Debian QA Group.
Checksums-Sha1:
 e0f0753ac51e33dc50fe083391c4ee73f3cde319 1977 python-hkdf_0.0.3-3~deb9u1.dsc
 171bad583b0f71c7703dd6fc99fc3d9af13d32f5 2132 
python-hkdf_0.0.3-3~deb9u1.debian.tar.xz
 1de80b27bb4997375c7877590032df54f499b3a4 6295 
python-hkdf_0.0.3-3~deb9u1_source.buildinfo
Checksums-Sha256:
 d93d566d0f07fc89d466545b1582609ec2ca56ddbd868b88a010fc6b4646ffa3 1977 
python-hkdf_0.0.3-3~deb9u1.dsc
 80811f7aebb06e559c84ddd3f8f301b4291643e933ca9f3cfedf28dcd1bcdf36 2132 
python-hkdf_0.0.3-3~deb9u1.debian.tar.xz
 10c1a7960870008cfbfbce7e50e6bcfdbcd877392702673cf183574de3b753df 6295 
python-hkdf_0.0.3-3~deb9u1_source.buildinfo
Files:
 b81c5c72362acb6ab553892f142d7e82 1977 python optional 
python-hkdf_0.0.3-3~deb9u1.dsc
 9f1c9ac28f6e853ba59146d32a20a1ad 2132 python optional 
python-hkdf_0.0.3-3~deb9u1.debian.tar.xz
 b3a913685cdda5764d12a10cf131b4de 6295 python optional 
python-hkdf_0.0.3-3~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpalhIQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCBryD/4tg9ZjDLpFwXpyTbAKqvE2qSKsDS7dfkd2
d/4j/r4Exhkobu/k4/47uBk4JsO/VZYsb7dqnomx9tKqdzcrzKI3Z+5LPOpAqqDY
r6DGmn5583/5PYMVLoGucSYMrl0Lhn3WQK82fpfGxq9UaT9otmYQ6kcgm13s/Q/1
vOicAIN2mcZ+1FqxtH3xeap0LHwYrlT/PVYa7CYzpb8fWBwgx2/l9wDrv45swvlj
Cd0clz/N/Rpfjalj8QMTKmMBosukiKTWo7pWT4nlLC4Vhymv0hkrWGxymDxyBYCw
ZT6hHRbLF9tPvg7tE2aKT9tuQjXHBBDcqNYNPGOGwhZ0ECqYGHUndayHDya6Yr6H
q5r1NpIQ+9DpE4saXFh6SdiuqPJ2iMcSzmsUFbEgYu+CwGXz6EMraYswsXWn42kO
6zb8ekMpZ75GHre+GsomGK8LIOqvc9jQ9SSjor58l7g0It/SyZn4/NkWeAE9DgJ1
xuHiUqjPmxbo8Spm1l0tJVCvEIM1M1l4stfLw5ExPyEGpdVal0Td3LQwBySYNrT1
YWF97Ap74npJlgw1Xmjbnocu5yjCYMjx5kSf4WHOiRn+nQLqlbP6JfSkymPDJwUA
bWTX3BxGgQrhWigepdTcBIEUuSMHs2RYMFRkGmLMC7xaE3K+113EyC76qg4bjabZ
3w5lm+zL8w==
=jTnM
-END PGP SIGNATURE-

Bug#885967: #885967: FTBFS: FAILED test of gethostid ENOENT

[Andreas Beckmann]

On Thu, 4 Jan 2018 21:40:48 +0100 Adam Borowski  wrote:
> } PATH=`pwd`/bin:$PATH /bin/sh test/07/t0705a.sh
> } 2,3c2,3
> } < (ENOENT) because there is no "hostid" regular file in the pathname "/etc"
> } < directory; did you mean the "hosts" regular file instead?
> } ---
> } > (ENOENT) because there is no "hostid" regular file in the pathname
> } > "/etc" directory
> } FAILED test of gethostid ENOENT
> 
> Adrian Bunk wrote:
> > /etc/hosts is created in the postinst of the netbase package,
> > so "missing build dependency on netbase" would be another way
> > to describe the problem.
> 
> Not sure if this is the best way to fix the failure, although it _would_
> make the error message find /etc/hosts there so it can be suggested.
> 
> This test is fragile, though -- if you have a file named /etc/hosting or
> such, it'll be picked instead of "hosts".
> 
> The root cause, though, is that libexplain knows about gethostid, thus it
> can rule out an user making a typo -- the function looks for /etc/hostid and
> hothing else.

At a quick glance the look_for_similar() functionality in
libexplain/buffer/errno/path_resolution.c cannot be disabled, therefore
a proper solution for making the test output deterministic (independent
of the content of /etc) is not easily possible. The tests also don't
seem to support regular expressions ...

I'd suggest to add the B-D: netbase, and reconsider this decision once
base-files ships /etc/hostile in case that is a better suggestion than
/etc/hosts :-)

Can this bug be reproduced in stretch or jessie buildd chroots - or can
we tag it sid+buster?


Andreas

Bug#886947: gxineplugin: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Followup-For: Bug #886947
Control: tag -1 pending patch

commit pushed to the GIT repo, but since I don't know how to update the
libmozjs B-D properly, I'm not going to upload it.


Andreas

Bug#867433: python3-hkdf: missing dependencies

[Andreas Beckmann]

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

Hi,

this is going to be fixed in the next stable point release with the
attached patch.


Andreas
diff -Nru python-hkdf-0.0.3/debian/changelog python-hkdf-0.0.3/debian/changelog
--- python-hkdf-0.0.3/debian/changelog  2016-06-04 23:06:45.0 +0200
+++ python-hkdf-0.0.3/debian/changelog  2018-01-14 00:25:36.0 +0100
@@ -1,3 +1,24 @@
+python-hkdf (0.0.3-3~deb9u1) stretch; urgency=medium
+
+  * QA upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann <a...@debian.org>  Sun, 14 Jan 2018 00:25:36 +0100
+
+python-hkdf (0.0.3-3) unstable; urgency=medium
+
+  * QA upload.
+  * Fix the python3-hkdf dependencies. (Closes: #867433)
+
+ -- Adrian Bunk <b...@debian.org>  Thu, 06 Jul 2017 19:16:59 +0300
+
+python-hkdf (0.0.3-2) unstable; urgency=medium
+
+  * Add missing URL to package descriptions.  closes: #864149.
+  * Set maintainer to Debian QA Group.
+
+ -- Clint Adams <cl...@debian.org>  Sun, 04 Jun 2017 10:59:31 -0400
+
 python-hkdf (0.0.3-1) unstable; urgency=low
 
   * Initial release.
diff -Nru python-hkdf-0.0.3/debian/control python-hkdf-0.0.3/debian/control
--- python-hkdf-0.0.3/debian/control2016-06-04 23:21:51.0 +0200
+++ python-hkdf-0.0.3/debian/control2017-07-06 18:16:52.0 +0200
@@ -1,5 +1,5 @@
 Source: python-hkdf
-Maintainer: Clint Adams <cl...@debian.org>
+Maintainer: Debian QA Group <packa...@qa.debian.org>
 Section: python
 Priority: optional
 Build-Depends: debhelper (>= 9),
@@ -18,6 +18,7 @@
 Depends: ${misc:Depends}, ${python:Depends}
 Description: HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
  This module implements the HMAC Key Derivation function, defined at
+ http://tools.ietf.org/html/draft-krawczyk-hkdf-01
  .
  There are two interfaces: a functional interface, with separate
  extract and expand functions as defined in the draft RFC, and a
@@ -25,9 +26,10 @@
 
 Package: python3-hkdf
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
  This module implements the HMAC Key Derivation function, defined at
+ http://tools.ietf.org/html/draft-krawczyk-hkdf-01
  .
  There are two interfaces: a functional interface, with separate
  extract and expand functions as defined in the draft RFC, and a

Bug#867457: python3-spake2: missing dependencies

[Andreas Beckmann]

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

This is going to be fixed in the next stable point release with the
attached patch.


Andreas
diff -Nru python-spake2-0.7/debian/changelog python-spake2-0.7/debian/changelog
--- python-spake2-0.7/debian/changelog  2016-06-08 19:05:58.0 +0200
+++ python-spake2-0.7/debian/changelog  2018-01-14 00:16:34.0 +0100
@@ -1,3 +1,18 @@
+python-spake2 (0.7-3~deb9u1) stretch; urgency=medium
+
+  * QA upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann <a...@debian.org>  Sun, 14 Jan 2018 00:16:34 +0100
+
+python-spake2 (0.7-3) unstable; urgency=high
+
+  * QA upload.
+  * Set maintainer to Debian QA Group. (see #833947)
+  * Fix the python3-spake2 dependencies. (Closes: #867457)
+
+ -- Adrian Bunk <b...@debian.org>  Thu, 06 Jul 2017 20:32:40 +0300
+
 python-spake2 (0.7-2) unstable; urgency=medium
 
   * Add src/spake2/six.py to debian/copyright.
diff -Nru python-spake2-0.7/debian/control python-spake2-0.7/debian/control
--- python-spake2-0.7/debian/control2016-06-05 01:34:25.0 +0200
+++ python-spake2-0.7/debian/control2017-07-06 19:32:40.0 +0200
@@ -1,5 +1,5 @@
 Source: python-spake2
-Maintainer: Clint Adams <cl...@debian.org>
+Maintainer: Debian QA Group <packa...@qa.debian.org>
 Section: python
 Priority: optional
 Build-Depends: debhelper (>= 9),
@@ -40,7 +40,7 @@
 
 Package: python3-spake2
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: SPAKE2 password-authenticated key exchange (pure python)
  This library implements the SPAKE2 password-authenticated key
  exchange ("PAKE") algorithm. This allows two parties, who share a

Bug#886947: gxineplugin: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: gxineplugin
Version: 0.5.910-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 -> sid

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...):

1m10.8s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/gxineplugin/changelog.Debian.gz (gxineplugin) != 
/usr/share/doc/gxine/changelog.Debian.gz (gxine)
/usr/share/doc/gxineplugin -> gxine
  /usr/share/doc/gxineplugin/changelog.gz (gxineplugin) != 
/usr/share/doc/gxine/changelog.gz (gxine)
/usr/share/doc/gxineplugin -> gxine
  /usr/share/doc/gxineplugin/copyright (gxineplugin) != 
/usr/share/doc/gxine/copyright (gxine)
/usr/share/doc/gxineplugin -> gxine


cheers,

Andreas


gxineplugin_0.5.910-2.log.gz
Description: application/gzip

Bug#518429: libmpd-dev: should depend on libglib2.0-dev

[Andreas Beckmann]

Followup-For: Bug #518429

Fixed in stretch with the attached patch.


Andreas
diff -u libmpd-0.20.0/debian/changelog libmpd-0.20.0/debian/changelog
--- libmpd-0.20.0/debian/changelog
+++ libmpd-0.20.0/debian/changelog
@@ -1,3 +1,19 @@
+libmpd (0.20.0-2~deb9u1) stretch; urgency=medium
+
+  * QA upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann <a...@debian.org>  Mon, 27 Nov 2017 04:35:59 +0100
+
+libmpd (0.20.0-2) unstable; urgency=medium
+
+  * QA upload.
+  * Set maintainer to Debian QA Group. (see #876951)
+  * libmpd-dev: Add the missing dependency on libglib2.0-dev.
+(Closes: #518429)
+
+ -- Adrian Bunk <b...@debian.org>  Sun, 01 Oct 2017 20:27:24 +0300
+
 libmpd (0.20.0-1.3) unstable; urgency=high
 
   * NMU
diff -u libmpd-0.20.0/debian/control libmpd-0.20.0/debian/control
--- libmpd-0.20.0/debian/control
+++ libmpd-0.20.0/debian/control
@@ -1,7 +1,7 @@
 Source: libmpd
 Section: libs
 Priority: optional
-Maintainer: Arnaud Cornet <acor...@debian.org>
+Maintainer: Debian QA Group <packa...@qa.debian.org>
 Build-Depends: libglib2.0-dev, debhelper (>= 7.0.50~), quilt, dh-autoreconf
 Standards-Version: 3.8.4
 Homepage: http://gmpc.wikia.com/
@@ -29,7 +29,7 @@
 Package: libmpd-dev
 Architecture: any
 Section: libdevel
-Depends: libmpd1 (= ${binary:Version}), pkg-config, ${misc:Depends}
+Depends: libmpd1 (= ${binary:Version}), pkg-config, ${misc:Depends}, 
libglib2.0-dev
 Description: High-level client library for accessing Music Player Daemon
  LibMpd is a library that provides high-level, callback-based access to
  Music Player Daemon (mpd).

Bug#695584: Missing dependency on libxsettings-dev

[Andreas Beckmann]

Followup-For: Bug #695584

Fixed in stretch with the attached patch.


Andreas
diff -Nru libxsettings-client-0.17/debian/changelog 
libxsettings-client-0.17/debian/changelog
--- libxsettings-client-0.17/debian/changelog   2015-10-31 23:24:06.0 
+0100
+++ libxsettings-client-0.17/debian/changelog   2017-11-27 05:20:39.0 
+0100
@@ -1,3 +1,18 @@
+libxsettings-client (0.17-9~deb9u1) stretch; urgency=medium
+
+  * QA upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann <a...@debian.org>  Mon, 27 Nov 2017 05:20:39 +0100
+
+libxsettings-client (0.17-9) unstable; urgency=medium
+
+  * QA upload.
+  * Add the missing libxsettings-client-dev -> libxsettings-dev
+dependency. (Closes: #695584)
+
+ -- Adrian Bunk <b...@debian.org>  Sun, 03 Sep 2017 23:36:18 +0300
+
 libxsettings-client (0.17-8) unstable; urgency=medium
 
   * QA upload.
diff -Nru libxsettings-client-0.17/debian/control 
libxsettings-client-0.17/debian/control
--- libxsettings-client-0.17/debian/control 2015-10-31 22:00:00.0 
+0100
+++ libxsettings-client-0.17/debian/control 2017-09-03 22:36:18.0 
+0200
@@ -23,7 +23,7 @@
 Section: libdevel
 Priority: optional
 Architecture: any
-Depends: libxsettings-client0 (= ${binary:Version}), libx11-dev, 
${misc:Depends}
+Depends: libxsettings-client0 (= ${binary:Version}), libx11-dev, 
${misc:Depends}, libxsettings-dev
 Description: utility functions for the Xsettings protocol (Development files)
  This package contains headers and other files required to compile
  software using the GPE scheduling library to use the Xsettings 

Bug#845497: liblasi-dev: has packaging issues with dependencies

[Andreas Beckmann]

Followup-For: Bug #845497

Fixed in stretch with the attached patch.


Andreas
diff -Nru lasi-1.1.0/debian/changelog lasi-1.1.0/debian/changelog
--- lasi-1.1.0/debian/changelog 2016-07-17 07:17:35.0 +0200
+++ lasi-1.1.0/debian/changelog 2017-11-27 07:21:40.0 +0100
@@ -1,3 +1,20 @@
+lasi (1.1.0-2~deb9u1) stretch; urgency=medium
+
+  * QA upload.
+  * Rebuild for stretch.
+
+ -- Andreas Beckmann <a...@debian.org>  Mon, 27 Nov 2017 07:21:40 +0100
+
+lasi (1.1.0-2) unstable; urgency=medium
+
+  * QA upload.
+  * Set maintainer to Debian QA Group. (see #867050)
+  * Add the missing libpango1.0-dev and libfreetype6-dev
+dependencies to liblasi-dev. (Closes: #845497)
+  * Add ${misc:Depends} to the package dependencies.
+
+ -- Adrian Bunk <b...@debian.org>  Sat, 08 Jul 2017 14:19:16 +0300
+
 lasi (1.1.0-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru lasi-1.1.0/debian/control lasi-1.1.0/debian/control
--- lasi-1.1.0/debian/control   2016-07-17 07:16:44.0 +0200
+++ lasi-1.1.0/debian/control   2017-07-08 13:19:16.0 +0200
@@ -1,6 +1,6 @@
 Source: lasi
 Priority: optional
-Maintainer: Andrew Ross <andrewr...@users.sourceforge.net>
+Maintainer: Debian QA Group <packa...@qa.debian.org>
 Build-Depends: debhelper (>= 5.0.0), cmake, libpango1.0-dev,
  cdbs (>=0.4.51), libfreetype6-dev (>= 2.2), doxygen
 Standards-Version: 3.7.3
@@ -12,7 +12,7 @@
 Package: liblasi0
 Section: libs
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: creation of PostScript documents containing Unicode symbols
  LASi is a library that provides a C++ stream output interface (with
  operator <<) for creating PostScript documents that can contain
@@ -29,7 +29,7 @@
 Package: liblasi-dev
 Section: libdevel
 Architecture: any
-Depends: liblasi0 (= ${binary:Version})
+Depends: liblasi0 (= ${binary:Version}), ${misc:Depends}, libpango1.0-dev, 
libfreetype6-dev
 Description: development files and documentation for the LASi library
  LASi is a library that provides a C++ stream output interface (with
  operator <<) for creating PostScript documents that can contain

Bug#872195: tircd: fails to install: chown: cannot access '/var/lib/tircd': No such file or directory

[Andreas Beckmann]

Package: tircd
Version: 0.30-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package tircd.
  (Reading database ... 
(Reading database ... 7634 files and directories currently installed.)
  Preparing to unpack .../archives/tircd_0.30-3_all.deb ...
  Unpacking tircd (0.30-3) ...
  Setting up tircd (0.30-3) ...
  chown: cannot access '/var/lib/tircd': No such file or directory
  dpkg: error processing package tircd (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   tircd


cheers,

Andreas


tircd_0.30-3.log.gz
Description: application/gzip

Bug#867029: fnfx-client: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: fnfx-client
Version: 0.3-15
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:

  jessie -> 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/ch-docs.html#s-copyrightfile

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/ch-maintainerscripts.html#s-unpackphase

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...):

1m32.3s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/fnfx-client/changelog.Debian.gz (fnfx-client) != 
/usr/share/doc/fnfxd/changelog.Debian.gz (fnfxd)
/usr/share/doc/fnfx-client -> fnfxd
  /usr/share/doc/fnfx-client/changelog.gz (fnfx-client) != 
/usr/share/doc/fnfxd/changelog.gz (fnfxd)
/usr/share/doc/fnfx-client -> fnfxd
  /usr/share/doc/fnfx-client/copyright (fnfx-client) != 
/usr/share/doc/fnfxd/copyright (fnfxd)
/usr/share/doc/fnfx-client -> fnfxd


cheers,

Andreas


fnfx-client_0.3-15.log.gz
Description: application/gzip

Bug#864223: cadabra: switch dependency from texlive-math-extra to texlive-science

[Andreas Beckmann]

On 2017-06-05 15:00, Axel Beckert wrote:
> Hi Andreas,
> 
> Andreas Beckmann wrote:
>> texlive-math-extra is a real package in jessie but a virtual package
>> provided by texlive-science in stretch. That causes a hard time for apt
>> and it will likely remove cadabra instead of installing texlive-science
>> during jessie->stretch upgrades.
> 
> If you haven't started preparing the upload already (nothing can be
> seen in the git repo yet), I'd take care of this.

go ahead, there are 4 similar new bugs in total (plus the original
dblatex one)


Andreas

Bug#864223: cadabra: switch dependency from texlive-math-extra to texlive-science

[Andreas Beckmann]

Package: cadabra
Version: 1.46-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

texlive-math-extra is a real package in jessie but a virtual package
provided by texlive-science in stretch. That causes a hard time for apt
and it will likely remove cadabra instead of installing texlive-science
during jessie->stretch upgrades.


Andreas

Bug#863567: rmail: unable to install because of unmet dependency

[Andreas Beckmann]

On 2017-05-28 19:30, s3v wrote:
> rmail is currently uninstallable on Stretch:

Well, you are switching your mta at the same time ...

> # apt-get -o Debug::pkgProblemResolver=1 install rmail

use

apt-get install rmail exim4-


> Please see #863367 for reference.

We could make this more smooth with a Conflicts: exim4, but I don't
think this change is worth an upload on its own.


Andreas