Bug#717992: moodle,moodle-book: error when trying to install together
Package: moodle,moodle-book Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: Architecture: amd64 Distribution: 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 moodle-book. (Reading database ... 27853 files and directories currently installed.) Unpacking moodle-book (from .../moodle-book_1.6.3-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/moodle-book_1.6.3-2_all.deb (--unpack): trying to overwrite '/usr/share/moodle/mod/book/show.php', which is also in package moodle 2.5.1-1 Errors were encountered while processing: /var/cache/apt/archives/moodle-book_1.6.3-2_all.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/share/moodle/mod/book/delete.php usr/share/moodle/mod/book/edit.php usr/share/moodle/mod/book/index.php usr/share/moodle/mod/book/lib.php usr/share/moodle/mod/book/move.php usr/share/moodle/mod/book/show.php usr/share/moodle/mod/book/version.php usr/share/moodle/mod/book/view.php 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 http://edos.debian.net/file-overwrites/. moodle=2.5.1-1_moodle-book=1.6.3-2.log.gz Description: GNU Zip compressed data
Bug#717992: moodle,moodle-book: error when trying to install together
On 2013-07-28 09:46, Thijs Kinkhorst wrote: > The module has been integrated into Moodle proper since version 2.3. I'm > reassigning the bug to moodle-book and will request removal. Removal will be one thing, but moodle needs to add Breaks+Replaces or Conflicts+Replaces to "get rid of it" as well and avoid overwrites on partial upgrades or depending on the upgrade order. Andreas -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51f4e553.5010...@debian.org
Bug#708502: New dpkg no longer contains install-info, rising to serious
Hi, On Saturday, 27. July 2013 11:41:22 Guillem Jover wrote: > dpkg 1.17.0 is now in unstable, and does not contain the install-info > compatibility wrapper any longer. These bugs are severity serious now. if you are going to fix your maintainer scripts, please test upgrades before uploading. If the prerm script disappears because it is no longer needed, you might run into errors like Preparing to replace yiyantang 0.7.0-3.1 (using .../yiyantang_0.7.0-4_amd64.deb) ... /var/lib/dpkg/info/yiyantang.prerm: 5: /var/lib/dpkg/info/yiyantang.prerm: install-info: not found dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg: trying script from the new package instead ... dpkg: error processing /var/cache/apt/archives/yiyantang_0.7.0-4_amd64.deb (--unpack): there is no script in the new version of the package - giving up The solution is to include an empty dummy prerm script in the new package. So you can test this upgrade path: * start with jessie chroot * install old package * upgrade dpkg to 1.17.x * upgrade your package Andreas -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201308011255.45256.a...@debian.org
Bug#718958: bzr-gtk: needs to be updated for bzr 2.6.0-1
Package: bzr-gtk Version: 0.103.0+bzr792-3 Severity: grave Tags: sid jessie Justification: renders package unusable User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: bzr-gtk : Depends: bzr (< 2.6.0) but 2.6.0-1 is to be installed Recommends: bzr-dbus but it is not going to be installed Recommends: gir1.2-appindicator3-0.1 but it is not going to be installed or gir1.2-notify-0.7 but it is not going to be installed Recommends: python-gi-cairo but it is not going to be installed Recommends: seahorse but it is not going to be installed Since it worked fine with the previous bzr versions (jessie has 2.6.0~bzr6574-1) which already seem to be 2.6.0, there is probably not much to fix besides bumping the dependencies. Cheers, Andreas -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130807080316.19529.24575.report...@cake.ae.cs.uni-frankfurt.de
Bug#722465: qtsmbstatus-server: fails to install due to insserv rejecting the script header
Package: qtsmbstatus-server Version: 2.2.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install due to insserv rejecting the script header. Some notes are available from at http://wiki.debian.org/LSBInitScripts >From the attached log (scroll to the bottom...): Selecting previously unselected package qtsmbstatus-server. (Reading database ... 8866 files and directories currently installed.) Unpacking qtsmbstatus-server (from .../qtsmbstatus-server_2.2.1-2_amd64.deb) ... Setting up qtsmbstatus-server (2.2.1-2) ... insserv: Service samba has to be enabled to start service qtsmbstatusd insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing qtsmbstatus-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: qtsmbstatus-server This problem was observed during an install test in jessie. cheers, Andreas qtsmbstatus-server_2.2.1-2.log.gz Description: GNU Zip compressed data
Bug#731021: bochs-svga: libsvga1 is gone
Package: bochs-svga Version: 2.6-1 Severity: serious Justification: fails to build from source Hi, libsvga1 is gone, so bochs-svga/experimental is no longer installable and src:bochs/experimental no longer buildable. Andreas -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131201013817.24153.26430.report...@cake.ae.cs.uni-frankfurt.de
Bug#750562: sendmail: CVE-2014-3956
Control: fixed -1 8.14.4-6 On 2014-06-04 15:44, Moritz Muehlenhoff wrote: > Hi, > please see http://www.openwall.com/lists/oss-security/2014/06/03/1 for > details. That's a trivial patch that I already cherry-picked from 8.14.9 into sid (there was no CVE at that time). For some reason the amd64 build got stuck in "Uploaded" state and therefore the package does not migrate ... For fixing this in wheezy: do you want to handle this via a security update or just via proposed-updates? Andreas -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/538f98e2.2080...@debian.org
Bug#1063401: atm-tools: has gained /usr/share/doc/libatm1/changelog.*
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#1053169: Please remove librbd-dev build-depends on all 32 bits arch
Followup-For: Bug #1053169 Migration is currently blocked behind the t64 transition. Andreas
Bug#1066437: libast: FTBFS: snprintf.c:45:22: error: unknown type name ‘size_t’
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#1066223: ftpcopy: FTBFS: conftest1663576.c:7:9: error: implicit declaration of function ‘_exit’ [-Werror=implicit-function-declaration]
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#1069068: pantalaimon: FTBFS some tests fail with asyncio CancelledError
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&full_state=true&filter=%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&filter=%257B%2522room%2522%253A%257B%2522state%2522%253A%257B%2522lazy_load_members%2522%253Atrue%257D%257D%257D&full_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&full_state=true&filter=%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&filter=%257B%2522room%2522%253A%257B%2522state%2522%253A%257B%2522lazy_load_members%2522%253Atrue%257D%257D%257D&full_state=true'
prefix = 'http://127.0.0.1'
key = ('GET',
URL('https://example.org/_matrix/client/r0/sync?access_token=abc123&filter=%257B%2522room%2522%253A%257B%2522state%2522%253A%257B%2522lazy_load_members%2522%253Atrue%257D%257D%257D&full_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 obj
Bug#1070190: sendmail-bin: CVE-2023-51765 SMTP smuggling with NUL followup
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#1070190: sendmail-bin: CVE-2023-51765 SMTP smuggling with NUL followup
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#1070427: libgnokii7t64: copyright file missing (policy 12.5)
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#1071008: libx52pro0: installs udev rules twice to /usr and /
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#1065937: python-sparkpost: Please drop dependencies on python3-distutils
Followup-For: Bug #1065937 Control: forwarded -1 https://github.com/SparkPost/python-sparkpost/issues/229 Control: tag -1 upstream patch The python3-distutils dependency is for the autopkgtest. The autopkgtest already fails in testing and sid due to lack of python3-six: 41s _ ERROR collecting test/test_transmissions.py __ 41s ImportError while importing test module '/tmp/autopkgtest-lxc.80s8zjfx/downtmp/build.8Jc/src/test/test_transmissions.py'. 41s Hint: make sure your test modules/packages have valid Python names. 41s Traceback: 41s /usr/lib/python3.11/importlib/__init__.py:126: in import_module 41s return _bootstrap._gcd_import(name[level:], package, level) 41s test/test_transmissions.py:9: in 41s import six 41s E ModuleNotFoundError: No module named 'six' With python3-six added and python3-distutils removed from the autopkgtest dependencies, I get _ ERROR collecting test/django/test_message.py _ ImportError while importing test module '/tmp/autopkgtest.0B51NB/build.K7a/src/test/django/test_message.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: /usr/lib/python3.12/importlib/__init__.py:90: in import_module return _bootstrap._gcd_import(name[level:], package, level) test/django/test_message.py:7: in from .utils import at_least_version test/django/utils.py:1: in from distutils.version import StrictVersion E ModuleNotFoundError: No module named 'distutils' The upstream bug has a proposed patch, but the package seems dead upstream (last commit 3 years ago). Andreas
Bug#1077212: ddcci-dkms: module fails to build for Linux 6.10
Package: ddcci-dkms Version: 0.4.4-2 Severity: important Tags: upstream ddcci-dkms fails to build a module for Linux 6.10 in experimental: DKMS make.log for ddcci-0.4.4 for kernel 6.10-rt-amd64 (x86_64) Tue Jul 23 20:25:02 UTC 2024 make: Entering directory '/var/lib/dkms/ddcci/0.4.4/build' make -C "ddcci" make[1]: Entering directory '/var/lib/dkms/ddcci/0.4.4/build/ddcci' make -C "/lib/modules/6.10-rt-amd64/build" M="/var/lib/dkms/ddcci/0.4.4/build/ddcci" modules make[2]: Entering directory '/usr/src/linux-headers-6.10-rt-amd64' CC [M] /var/lib/dkms/ddcci/0.4.4/build/ddcci/ddcci.o /var/lib/dkms/ddcci/0.4.4/build/ddcci/ddcci.c:1831:27: error: 'I2C_CLASS_SPD' undeclared here (not in a function); did you mean 'I2C_CLASS_HWMON'? 1831 | .class = I2C_CLASS_SPD, | ^ | I2C_CLASS_HWMON make[4]: *** [/usr/src/linux-headers-6.10-common-rt/scripts/Makefile.build:249: /var/lib/dkms/ddcci/0.4.4/build/ddcci/ddcci.o] Error 1 make[3]: *** [/usr/src/linux-headers-6.10-common-rt/Makefile:1959: /var/lib/dkms/ddcci/0.4.4/build/ddcci] Error 2 make[2]: *** [/usr/src/linux-headers-6.10-common-rt/Makefile:252: __sub-make] Error 2 make[2]: Leaving directory '/usr/src/linux-headers-6.10-rt-amd64' make[1]: *** [Makefile:38: ddcci.ko] Error 2 make[1]: Leaving directory '/var/lib/dkms/ddcci/0.4.4/build/ddcci' make: *** [Makefile:28: ddcci] Error 2 make: Leaving directory '/var/lib/dkms/ddcci/0.4.4/build' This is caused by Linux commit e61bcf42d290e73025bab38e0e55a5586c2d8ad5 i2c: Remove I2C_CLASS_SPD Andreas
Bug#1077216: librem-ec-acpi-dkms: module fails to build for Linux 6.10: error: 'struct acpi_driver' has no member named 'owner'
Package: librem-ec-acpi-dkms
Version: 0.9.2-1
Severity: important
Tags: upstream
librem-ec-acpi-dkms file to build a module for Linux 6.10:
DKMS make.log for librem_ec_acpi-0.9.2 for kernel 6.10-rt-amd64 (x86_64)
Tue Jul 23 20:25:08 UTC 2024
make: Entering directory '/usr/src/linux-headers-6.10-rt-amd64'
CC [M] /var/lib/dkms/librem_ec_acpi/0.9.2/build/librem_ec_acpi.o
/var/lib/dkms/librem_ec_acpi/0.9.2/build/librem_ec_acpi.c:782:10: error:
'struct acpi_driver' has no member named 'owner'
782 | .owner = THIS_MODULE,
| ^
In file included from
/usr/src/linux-headers-6.10-common-rt/arch/x86/include/asm/mem_encrypt.h:15,
from
/usr/src/linux-headers-6.10-common-rt/include/linux/mem_encrypt.h:17,
from
/usr/src/linux-headers-6.10-common-rt/arch/x86/include/asm/processor-flags.h:6,
from
/usr/src/linux-headers-6.10-common-rt/arch/x86/include/asm/irqflags.h:5,
from
/usr/src/linux-headers-6.10-common-rt/include/linux/irqflags.h:18,
from
/usr/src/linux-headers-6.10-common-rt/include/linux/spinlock.h:59,
from
/usr/src/linux-headers-6.10-common-rt/include/linux/mmzone.h:8,
from
/usr/src/linux-headers-6.10-common-rt/include/linux/gfp.h:7,
from
/usr/src/linux-headers-6.10-common-rt/include/linux/slab.h:16,
from
/usr/src/linux-headers-6.10-common-rt/include/linux/resource_ext.h:11,
from
/usr/src/linux-headers-6.10-common-rt/include/linux/acpi.h:13,
from
/var/lib/dkms/librem_ec_acpi/0.9.2/build/librem_ec_acpi.c:16:
/usr/src/linux-headers-6.10-common-rt/include/linux/init.h:180:21: warning:
initialization of 'char' from 'struct module *' makes integer from pointer
without a cast [-Wint-conversion]
180 | #define THIS_MODULE (&__this_module)
| ^
/var/lib/dkms/librem_ec_acpi/0.9.2/build/librem_ec_acpi.c:782:18: note: in
expansion of macro 'THIS_MODULE'
782 | .owner = THIS_MODULE,
| ^~~
/usr/src/linux-headers-6.10-common-rt/include/linux/init.h:180:21: note: (near
initialization for 'librem_ec_driver.class[0]')
180 | #define THIS_MODULE (&__this_module)
| ^
/var/lib/dkms/librem_ec_acpi/0.9.2/build/librem_ec_acpi.c:782:18: note: in
expansion of macro 'THIS_MODULE'
782 | .owner = THIS_MODULE,
| ^~~
/usr/src/linux-headers-6.10-common-rt/include/linux/init.h:180:21: error:
initializer element is not computable at load time
180 | #define THIS_MODULE (&__this_module)
| ^
/var/lib/dkms/librem_ec_acpi/0.9.2/build/librem_ec_acpi.c:782:18: note: in
expansion of macro 'THIS_MODULE'
782 | .owner = THIS_MODULE,
| ^~~
/usr/src/linux-headers-6.10-common-rt/include/linux/init.h:180:21: note: (near
initialization for 'librem_ec_driver.class[0]')
180 | #define THIS_MODULE (&__this_module)
| ^
/var/lib/dkms/librem_ec_acpi/0.9.2/build/librem_ec_acpi.c:782:18: note: in
expansion of macro 'THIS_MODULE'
782 | .owner = THIS_MODULE,
| ^~~
/var/lib/dkms/librem_ec_acpi/0.9.2/build/librem_ec_acpi.c:780:46: warning:
missing braces around initializer [-Wmissing-braces]
780 | static struct acpi_driver librem_ec_driver = {
| ^
/var/lib/dkms/librem_ec_acpi/0.9.2/build/librem_ec_acpi.c:780:46: warning:
missing braces around initializer [-Wmissing-braces]
make[2]: *** [/usr/src/linux-headers-6.10-common-rt/scripts/Makefile.build:249:
/var/lib/dkms/librem_ec_acpi/0.9.2/build/librem_ec_acpi.o] Error 1
make[1]: *** [/usr/src/linux-headers-6.10-common-rt/Makefile:1959:
/var/lib/dkms/librem_ec_acpi/0.9.2/build] Error 2
make: *** [/usr/src/linux-headers-6.10-common-rt/Makefile:252: __sub-make]
Error 2
make: Leaving directory '/usr/src/linux-headers-6.10-rt-amd64'
This should be caused by upstream commit
cc85f9c05bba23eb525497b42ac5b74801ccbd87
ACPI: drop redundant owner from acpi_driver
Andreas
Bug#1077217: adv-17v35x-dkms: module fails to build for Linux 6.10: error: 'struct uart_state' has no member named 'xmit'
Package: adv-17v35x-dkms
Version: 5.0.7.0-1
Severity: important
Tags: upstream sid trixie
adv-17v35x-dkms fails to build a module for Linux 6.10 in experimental:
DKMS make.log for adv-17v35x-5.0.7.0 for kernel 6.10-cloud-amd64 (x86_64)
Tue Jul 23 20:27:05 UTC 2024
make: Entering directory '/usr/src/linux-headers-6.10-cloud-amd64'
CC [M] /var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.o
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c: In function
'transmit_chars':
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:830:48: error: 'struct
uart_state' has no member named 'xmit'
830 | struct circ_buf *xmit = &up->port.state->xmit;
|^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:851:13: error: implicit
declaration of function 'uart_circ_empty'; did you mean 'uart_lsr_tx_empty'?
[-Werror=implicit-function-declaration]
851 | if (uart_circ_empty(xmit)) {
| ^~~
| uart_lsr_tx_empty
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:868:13: error: implicit
declaration of function 'uart_circ_chars_pending'
[-Werror=implicit-function-declaration]
868 | if (uart_circ_chars_pending(xmit) < count)
| ^~~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:883:27: error: invalid use
of undefined type 'struct circ_buf'
883 | if( ((xmit->tail + count) & (UART_XMIT_SIZE-1)) <
xmit->tail)
| ^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:883:71: error: invalid use
of undefined type 'struct circ_buf'
883 | if( ((xmit->tail + count) & (UART_XMIT_SIZE-1)) <
xmit->tail)
| ^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:885:52: error: invalid use
of undefined type 'struct circ_buf'
885 | tmp = UART_XMIT_SIZE - xmit->tail;
|^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:886:85: error: invalid use
of undefined type 'struct circ_buf'
886 | memcpy_toio(up->port.membase +
UART_17V35X_TX_OFFSET, &(xmit->buf[xmit->tail]), tmp);
|
^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:886:95: error: invalid use
of undefined type 'struct circ_buf'
886 | memcpy_toio(up->port.membase +
UART_17V35X_TX_OFFSET, &(xmit->buf[xmit->tail]), tmp);
|
^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:887:29: error: invalid use
of undefined type 'struct circ_buf'
887 | xmit->tail += tmp;
| ^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:888:29: error: invalid use
of undefined type 'struct circ_buf'
888 | xmit->tail &= (UART_XMIT_SIZE-1);
| ^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:894:85: error: invalid use
of undefined type 'struct circ_buf'
894 | memcpy_toio(up->port.membase +
UART_17V35X_TX_OFFSET, &(xmit->buf[xmit->tail]), count);
|
^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:894:95: error: invalid use
of undefined type 'struct circ_buf'
894 | memcpy_toio(up->port.membase +
UART_17V35X_TX_OFFSET, &(xmit->buf[xmit->tail]), count);
|
^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:895:29: error: invalid use
of undefined type 'struct circ_buf'
895 | xmit->tail += count;
| ^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:896:29: error: invalid use
of undefined type 'struct circ_buf'
896 | xmit->tail &= UART_XMIT_SIZE - 1;
| ^~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c: At top level:
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:2033:6: warning: no previous
prototype for 'serialadv_spi_delay' [-Wmissing-prototypes]
2033 | void serialadv_spi_delay(void)
| ^~~
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:2045:6: warning: no previous
prototype for 'serialadv_spi_write_slave' [-Wmissing-prototypes]
2045 | void serialadv_spi_write_slave(struct uart_adv_port *up, unsigned char
data)
| ^
/var/lib/dkms/adv-17v35x/5.0.7.0/build/adv17v35x.c:2068:5: warning: no previous
prototype for 'serialadv_spi_read_slave' [-Wmissing-prototypes]
2068 | int serialadv_spi_read_slave(struct uar
Bug#1078338: cuneiform: FTBFS with GCC 14: error: type defaults to 'int' in declaration of 'broken_ii'
Source: cuneiform
Version: 1.1.0+dfsg-10
Severity: serious
cuneiform started to FTBFS when GCC 14 was made the default compiler:
cd /build/cuneiform-1.1.0+dfsg/obj/cuneiform_src/Kern/cfcompat &&
/usr/bin/cmake -E cmake_link_script CMakeFiles/cfcompat.dir/link.txt --verbose=1
/usr/bin/cc -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-Werror=implicit-function-declaration
-ffile-prefix-map=/build/cuneiform-1.1.0+dfsg=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_F
ORTIFY_SOURCE=2 -Wno-error -fcommon -Wl,-Bsymbolic -Wl,-z,relro -Wl,-z,now
-shared -Wl,-soname,libcfcompat.so.0 -o libcfcompat.so.1.1.0
CMakeFiles/cfcompat.dir/cfcompat.c.o
-Wl,-rpath,/usr/lib/x86_64-linux-gnu/cuneiform -Wl,-Bstatic -ldl -Wl,-Bdynamic
/build/cuneiform-1.1.0+dfsg/cuneiform_src/Kern/dif/src/diffr.c:108:8: error:
type defaults to 'int' in declaration of 'broken_ii' [-Wimplicit-int]
108 | extern broken_ii; /* 䫠
*/
|^
If I fix that, I'm running into more type mismatches:
/build/cuneiform-1.1.0+dfsg/cuneiform_src/Kern/hdebug/__snp.c:989:73: error:
passing argument 7 of 'LDPUMA_DrawLine' makes integer from pointer without a
cast [-Wint-conversion]
989 |
LDPUMA_DrawLine(NULL,start,end,skew,rgb_color,pen_width,key );
|
^~~
|
|
|
Handle {aka void *}
/build/cuneiform-1.1.0+dfsg/cuneiform_src/Kern/hdebug/__snp.c:384:71: note:
expected 'uint32_t' {aka 'unsigned int'} but argument is of type 'Handle' {aka
'void *'}
384 | uint32_t rgb_color,int16_t pen_width,uint32_t
key )
|
~^~~
/build/cuneiform-1.1.0+dfsg/cuneiform_src/Kern/hdebug/__snp.c: In function
'SnpHideLines':
/build/cuneiform-1.1.0+dfsg/cuneiform_src/Kern/hdebug/__snp.c:993:41: error:
passing argument 2 of 'LDPUMA_DeleteLines' makes integer from pointer without a
cast [-Wint-conversion]
993 | LDPUMA_DeleteLines(NULL,key);
| ^~~
| |
| Handle {aka void *}
[ 33%] Building CXX object
cuneiform_src/Kern/rimage/CMakeFiles/rimage.dir/sources/main/kronrod/ckronrodbinarizator.cpp.o
/build/cuneiform-1.1.0+dfsg/cuneiform_src/Kern/hdebug/__snp.c:397:53: note:
expected 'uint32_t' {aka 'unsigned int'} but argument is of type 'Handle' {aka
'void *'}
397 | void LDPUMA_DeleteLines(Handle wnd,uint32_t key)
|~^~~
Andreas
cuneiform_1.1.0+dfsg-10.log.gz
Description: application/gzip
Bug#1020771: sendmail: french package description contains duplicated text
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#991331: sid listed as affected
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#964540: dropwatch build times out in the testsuite
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#1023662: adv-17v35x-dkms: module fails to build for Linux 6.0
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(&up->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#1027836: planner,planner-data: both ship /usr/share/planner/images/gnome-planner.png
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#1030187: adv-17v35x-dkms: module fails to build for Linux 6.1
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#1012232: freespace2: FTBFS: ./configure: line 17040: syntax error near unexpected token `ax_cxx_compile_cxx11_required=falsednl'
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#1012232: freespace2: FTBFS: ./configure: line 17040: syntax error near unexpected token `ax_cxx_compile_cxx11_required=falsednl'
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#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye
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#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye
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#1037213: awstats: prompting due to modified conffiles which were not modified by the user: /etc/logrotate.d/httpd-prerotate/awstats
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#1038001: librem-ec-acpi-dkms: module fails to build for Linux 6.3
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#1040275: python3-socketio-client: SyntaxWarning during package installation
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#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
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#1039365: Fedora has systemd-unit files for sendmail
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#1039365: Fedora has systemd-unit files for sendmail
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#1054640: propellor: FTBFS with ghc 9.4: Not in scope: type constructor or class `UserEntry'
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#1058749: scanbd: fails to upgrade from bookworm: mv: not replacing '/etc/scanbd/dll.conf'
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#656462: loop-aes-utils: unowned files after purge (policy 6.8, 10.8)
Package: loop-aes-utils Version: 2.16.2-2 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. >From the attached log (scroll to the bottom...): 0m20.1s ERROR: FAIL: Package purging left files on system: /etc/default/checkfs-loop not owned cheers, Andreas loop-aes-utils_2.16.2-2.log.gz Description: GNU Zip compressed data
Bug#660590: apt-build: prompting due to modified conffiles which where not modified by the user
Package: apt-build Version: 0.12.40 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 http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." http://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In http://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...): (upgrade test squeeze -> sid) Setting up apt-build (0.12.40) ... Configuration file `/etc/apt/sources.list.d/apt-build.list' ==> File on system created by you or by a script. ==> File also in package provided by package maintainer. 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. *** apt-build.list (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing apt-build (--configure): EOF on stdin at conffile prompt configured to not write apport reports Errors were encountered while processing: apt-build cheers, Andreas apt-build_0.12.40.log.gz Description: GNU Zip compressed data
Bug#661015: gnats-user: fails to purge if gnats is not purged
Package: gnats-user,gnats Version: 4.1.0-2 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to purge. The following actions reproduce this: apt-get install gnats apt-get remove gnats dpkg --purge gnats-user Note that there is no guarantee in the order of purging packages. >From the attached log (scroll to the bottom...): Removing gnats-user ... Purging configuration files for gnats-user ... rmdir: failed to remove `/var/lib/gnats/gnats-db': Directory not empty dpkg: error processing gnats-user (--purge): subprocess installed post-removal script returned error exit status 1 cheers, Andreas gnats_4.1.0-2.log.gz Description: GNU Zip compressed data
Bug#662608: libdoodle1/experimental uninstallable, depends on libextractor3 *and* libextractor1c2a
Package: libdoodle1 Version: 0.7.0-4 Severity: grave Tags: experimental Justification: renders package unusable User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is not installable in experimental: Package: libdoodle1 Depends: libc6 (>= 2.3), libextractor3, libextractor1c2a, libextractor-plugins Package: libextractor3 Conflicts: libextractor1c2a The libextractor3 comes from shlibs:Depends, libextractor1c2a is hardcoded in debian/control Cheers, Andreas -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120305100743.3968.73475.report...@cake.ae.cs.uni-frankfurt.de
Bug#663032: wdm: fails to purge - rmdir: failed to remove `/var/run/wdm': No such file or directory
Package: wdm Version: 1.28-10 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to purge. >From the attached log (scroll to the bottom...): Removing wdm ... rmdir: failed to remove `/var/run/wdm': No such file or directory dpkg: error processing wdm (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: wdm cheers, Andreas wdm_1.28-10.log.gz Description: GNU Zip compressed data
Bug#668741: emacs-jabber: unowned files after purge (policy 6.8, 10.8): /usr/share/emacs23/site-lisp/emacs-jabber/compilation.log
Package: emacs-jabber Version: 0.8.0-3 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. >From the attached log (scroll to the bottom...): 0m32.4s ERROR: FAIL: Package purging left files on system: /usr/share/emacs23/site-lisp owned by: emacs23-common /usr/share/emacs23/site-lisp/emacs-jabber not owned /usr/share/emacs23/site-lisp/emacs-jabber/compilation.log not owned cheers, Andreas emacs-jabber_0.8.0-3.log.gz Description: GNU Zip compressed data
Bug#668766: gnunet-server: unowned files after purge (policy 6.8, 10.8): /etc/default/gnunet-server
Package: gnunet-server Version: 0.8.1b-8 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. >From the attached log (scroll to the bottom...): 0m26.5s ERROR: FAIL: Package purging left files on system: /etc/default/gnunet-server not owned cheers, Andreas gnunet-server_0.8.1b-8.log.gz Description: GNU Zip compressed data
Bug#672183: apt-build: unowned files after purge (policy 6.8, 10.8)
Package: apt-build Version: 0.12.42 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. >From the attached log (scroll to the bottom...): 0m44.3s ERROR: FAIL: Package purging left files on system: /var/cache/apt-build/ not owned /var/cache/apt-build/build/not owned /var/cache/apt-build/repository/ not owned /var/cache/apt-build/repository/Packages.gznot owned /var/cache/apt-build/repository/Releasenot owned /var/cache/apt-build/repository/dists/ not owned /var/cache/apt-build/repository/dists/apt-build/ not owned /var/cache/apt-build/repository/dists/apt-build/Release -> ../../Release not owned /var/cache/apt-build/repository/dists/apt-build/main/ not owned cheers, Andreas apt-build_0.12.42.log.gz Description: GNU Zip compressed data
Bug#677062: webissues-server: fails to purge - command ucf in postrm not found
Package: webissues-server Version: 0.8.5-3 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...): Removing webissues-server ... Purging configuration files for webissues-server ... /var/lib/dpkg/info/webissues-server.postrm: 16: /var/lib/dpkg/info/webissues-server.postrm: ucf: not found dpkg: error processing webissues-server (--purge): subprocess installed post-removal script returned error exit status 127 Errors were encountered while processing: webissues-server cheers, Andreas webissues-server_0.8.5-3.log.gz Description: GNU Zip compressed data
Bug#678844: libswirl-java-gcj: unowned files after purge (policy 6.8, 10.8): /var/lib/x86_64-linux-gnu/gcj-4.7/classmap.db
Package: libswirl-java-gcj Version: 1.1-2 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. >From the attached log (scroll to the bottom...): 0m55.6s ERROR: FAIL: Package purging left files on system: /var/lib/x86_64-linux-gnu/ not owned /var/lib/x86_64-linux-gnu/gcj-4.7/ not owned /var/lib/x86_64-linux-gnu/gcj-4.7/classmap.db not owned cheers, Andreas libswirl-java-gcj_1.1-2.log.gz Description: GNU Zip compressed data
Bug#613842: Uninstall of spread breaks dpkg
Package: spread Version: 3.17.4-4 Followup-For: Bug #613842 Hi, a also observed this during piuparts tests: 1m23.3s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpRibyIh', 'eatmydata', 'dpkg', '--purge', 'spread'] 1m23.5s DUMP: (Reading database ... 6750 files and directories currently installed.) Removing spread ... invoke-rc.d: policy-rc.d denied execution of stop. Purging configuration files for spread ... dpkg-statoverride: unrecoverable fatal error, aborting: syntax error: unknown user 'spread' in statoverride file dpkg-statoverride: unrecoverable fatal error, aborting: syntax error: unknown user 'spread' in statoverride file dpkg-statoverride: unrecoverable fatal error, aborting: syntax error: unknown user 'spread' in statoverride file 1m23.5s DEBUG: Command ok: ['chroot', '/tmp/piupartss/tmpRibyIh', 'eatmydata', 'dpkg', '--purge', 'spread'] 1m28.9s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpRibyIh', 'eatmydata', 'apt-get', '-y', 'install', 'spread=3.17.4-4'] 1m29.7s DUMP: Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: spread 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 226 kB of archives. After this operation, 535 kB of additional disk space will be used. debconf: delaying package configuration, since apt-utils is not installed Fetched 226 kB in 0s (6720 kB/s) dpkg: unrecoverable fatal error, aborting: syntax error: unknown user 'spread' in statoverride file E: Sub-process /usr/bin/dpkg returned an error code (2) 1m29.7s ERROR: Command failed (status=100): ['chroot', '/tmp/piupartss/tmpRibyIh', 'eatmydata', 'apt-get', '-y', 'install', 'spread=3.17.4-4'] Cheers, Andreas spread_3.17.4-4.log.gz Description: GNU Zip compressed data
Bug#681756: canna: removes files that were installed by another package: /etc/canna/default.canna
Package: canna Version: 3.7p3-9 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 another package. The removed files were already present before the package was installed, they may have been shipped or created by a dependency. This is a serious bug violating policy 7.6, see http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): 0m27.4s ERROR: FAIL: After purging files have disappeared: /etc/canna/owned by: canna, libcanna1g /etc/canna/default.canna not owned cheers, Andreas canna_3.7p3-9.log.gz Description: GNU Zip compressed data
Bug#681756: cannot reproduce
On 2012-08-11 21:57, gustavo panizzo wrote: > i cloned from git://anonscm.debian.org/piuparts/piuparts.git let me > know if i should clone from another repo branch develop Andreas -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5026ba07.6080...@abeckmann.de
Bug#681756: cannot reproduce
On 2012-08-11 20:54, gregor herrmann wrote: > On Sat, 11 Aug 2012 15:43:53 -0300, gustavo panizzo wrote: > i cannot reproduce this bug using piuparts >>> Me neither, with piuparts 0.45. >> what would be the best course of action then? > > I hope that Andreas, as the piuparts expert and bug submitter, can > shed some light on this issue. I don't have the time right now to look into the details (or logs), but piuparts from GIT should be able to reproduce the problem with the --install-purge-install option. Andreas -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5026b4be.2050...@abeckmann.de
Bug#688223: emacspeak: modifies conffiles (policy 10.7.3): /etc/emacspeak.conf
Package: emacspeak Version: 29.0-8 Severity: serious Tags: squeeze-ignore User: debian...@lists.debian.org Usertags: piuparts Control: found -1 emacspeak/29.0-6 Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: "[...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time)." Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: "[...] must not ask unnecessary questions (particularly during upgrades) [...]" If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/emacspeak.conf cheers, Andreas emacspeak_29.0-8.log.gz Description: GNU Zip compressed data
Bug#689537: pdnsd: deletes conffiles on package removal (policy 10.7.3): /etc/NetworkManager/dispatcher.d/002_NetMan_pdnsd
With the prerm script gone this issue is fixed for squeeze->sid upgrades (and squeeze->wheezy upgrades once 1.2.8-par-3 migrates to wheezy), but the problem (missing conffile) will still exist if the user had any version from 1.2.8-par-2, ..., 1.2.8-par-2.3 installed. I don't see an easy solution for this ... as old-prerm upgrade new-version is the very first step of the upgrade, there is no hacking around this by deleting a buggy maintainer script during new-preinst upgrade old-version Maybe this could work: ship another copy of the file in /usr/share and in the postinst do if dpkg --compare-versions $upgrade_from ge 1.2.8-par-2~ && dpkg --compare-versions $upgrade_from lt 1.2.8-par-4~ then target=/etc/NetworkManager/dispatcher.d/002_NetMan_pdnsd source=/usr/share/.../002_NetMan_pdnsd if [ ! -e $target ]; then echo restoring $target cp $source $target fi fi but it's only upgrades from pdnsd/testing that are affected Andreas -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50847433.9000...@abeckmann.de
Bug#694266: canna-utils: error when trying to install together with canna/squeeze (3.7p3-6.5)
Package: canna-utils Version: 3.7p3-10 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Architecture: amd64 Distribution: squeeze->wheezy (partial) upgrade 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 deselected package libcanna1g. (Reading database ... 6286 files and directories currently installed.) Unpacking libcanna1g (from .../libcanna1g_3.7p3-6.5_amd64.deb) ... Selecting previously deselected package canna. Unpacking canna (from .../canna_3.7p3-6.5_amd64.deb) ... Setting up libcanna1g (3.7p3-6.5) ... Setting up canna (3.7p3-6.5) ... Installed new iroha dic Installed new fuzokugo dics Selecting previously deselected package canna-utils. (Reading database ... 6405 files and directories currently installed.) Unpacking canna-utils (from .../canna-utils_3.7p3-10_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/canna-utils_3.7p3-10_amd64.deb (--unpack): trying to overwrite '/usr/bin/chmoddic', which is also in package canna 3.7p3-6.5 This is a serious bug as it makes installation/upgrade fail, and violates sections 7.6.1 and 10.1 of the policy. As this problem can be demonstrated during partial upgrades from squeeze to wheezy (but not within squeeze or wheezy itself), this indicates a missing or insufficiently versioned Replaces+Breaks relationship. But since this particular upgrade ordering is not forbidden by any dependency relationship, it is possible that apt (or $PACKAGE_MANAGER) will use this erroneus path on squeeze->wheezy upgrades. Here is a list of files that are known to be shared by both packages (according to the Contents files for squeeze and wheezy on amd64, which may be slightly out of sync): usr/bin/chmoddic The following relationships are currently defined: Conflicts: n/a Breaks:n/a Replaces: n/a I think this is a regression introduced in 3.7p3-10: * Fix a dangling symlink (/usr/bin/chmoddic -> catdic) on canna package. The following relationships should be added: Package: canna-utils Breaks: canna (<< 3.7p3-10) Replaces: canna (<< 3.7p3-10) Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. canna=3.7p3-6.5_canna-utils=3.7p3-10.log.gz Description: GNU Zip compressed data
Bug#658850: libreadline-gplv2-dev: "Multi-Arch: same" but examples/Makefile differs across architectures
Followup-For: Bug #658850 Control: found -1 5.2+dfsg-1 Hi, the problem is still (or again) reproducible in the latest version: Selecting previously unselected package libreadline-gplv2-dev:i386. Unpacking libreadline-gplv2-dev:i386 (from .../libreadline-gplv2-dev_5.2+dfsg-1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libreadline-gplv2-dev_5.2+dfsg-1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', which is different from other instances of package libreadline-gplv2-dev:i386 Errors were encountered while processing: /var/cache/apt/archives/libreadline-gplv2-dev_5.2+dfsg-1_i386.deb Cheers, Andreas libreadline-gplv2-dev=5.2+dfsg-1.log.gz Description: GNU Zip compressed data
Bug#709394: libtomoe0,tomoe-doc: copyright file missing after upgrade (policy 12.5)
Package: libtomoe0,tomoe-doc Version: 0.6.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5: http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. This was observed on the following upgrade paths: testing -> sid >From the attached log (scroll to the bottom...): MISSING COPYRIGHT FILE: /usr/share/doc/tomoe-doc/copyright # ls -lad /usr/share/doc/tomoe-doc drwxr-xr-x 2 root root 40 May 22 05:32 /usr/share/doc/tomoe-doc # ls -la /usr/share/doc/tomoe-doc/ total 0 drwxr-xr-x 2 root root 40 May 22 05:32 . drwxr-xr-x 80 root root 1700 May 22 05:32 .. MISSING COPYRIGHT FILE: /usr/share/doc/libtomoe0/copyright # ls -lad /usr/share/doc/libtomoe0 drwxr-xr-x 2 root root 40 May 22 05:24 /usr/share/doc/libtomoe0 # ls -la /usr/share/doc/libtomoe0/ total 0 drwxr-xr-x 2 root root 40 May 22 05:24 . drwxr-xr-x 83 root root 1760 May 22 05:24 .. Additional info may be available here: http://wiki.debian.org/MissingCopyrightFile 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 http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase For switching from a directory to a symlink the *postinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ DOCLINK=@@OTHERPACKAGE@@ if [ -d $DOCDIR ] && [ ! -L $DOCDIR ]; then rmdir $DOCDIR ln -s $DOCLINK $DOCDIR fi For switching from a symlink to a directory, the *preinst* script should do something like this: DOCDIR=/usr/share/doc/@@PACKAGE@@ if [ -L $DOCDIR ]; then rm $DOCDIR fi cheers, Andreas tomoe-doc_0.6.0-3.log.gz Description: GNU Zip compressed data
Bug#710727: awffull: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/awffull/examples/sample.conf.gz
Package: awffull Version: 3.10.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: "Packages must not require the existence of any files in /usr/share/doc/ in order to function." http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. >From the attached log (scroll to the bottom...): Selecting previously unselected package awffull. (Reading database ... 7157 files and directories currently installed.) Unpacking awffull (from .../awffull_3.10.2-2_amd64.deb) ... Setting up awffull (3.10.2-2) ... /var/www/awffull created gzip: /usr/share/doc/awffull/examples/sample.conf.gz: No such file or directory dpkg: error processing awffull (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: awffull Cheers, Andreas awffull_3.10.2-2.log.gz Description: GNU Zip compressed data
Bug#816505: Compile Differences sendmail 8.14.4 vs 8.15.2 [SOCKETMAP missing]
On 2016-03-02 13:23, Michiel Brandenburg wrote: > It seems that SOCKETMAP support for 8.15.2 was dropped, this may be > because of a change in the "default" options between 8.14 and 8.15 but > it is not consistent. Good catch, thanks! Andreas
Bug#819991: opencryptoki: FTBFS on kfreebsd: attempts to include linux/limits.h
Source: opencryptoki Version: 3.4.1+dfsg-1 Severity: important Hi, opencryptoki FTBFS on kfreebsd (but the 2.3.1 release built there without problems): https://buildd.debian.org/status/fetch.php?pkg=opencryptoki&arch=kfreebsd-amd64&ver=3.4.1%2Bdfsg-1&stamp=1454937298 https://buildd.debian.org/status/fetch.php?pkg=opencryptoki&arch=kfreebsd-i386&ver=3.4.1%2Bdfsg-1&stamp=1454936847 gcc -DPACKAGE_NAME=\"openCryptoki\" -DPACKAGE_TARNAME=\"opencryptoki\" -DPACKAGE_VERSION=\"3.4.1\" -DPACKAGE_STRING=\"openCryptoki\ 3.4.1\" -DPACKAGE_BUGREPORT=\"opencryptoki-t...@lists.sourceforge.net\" -DPACKAGE_URL=\"\" -DPACKAGE=\"opencryptoki\" -DVERSION=\"3.4.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_FILE_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_UNISTD_H=1 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DHAVE_STRFTIME=1 -DHAVE_VPRINTF=1 -DHAVE_GETCWD=1 -DYYTEXT_POINTER=1 -I. -I. -I../../include/pkcs11 -I../../lib/pkcs11/common -DSTDLL_NAME=\"pkcscca\" -g -O2 -m32 -DPKCS64 -D_XOPEN_SOURCE=500 -Wall -Wno-pointer-sign -DCONFIG_PATH=\"/var/lib/opencryptoki\" -DSBIN_PATH=\"/usr/sbin\" -DLIB_PATH=\"/usr/lib\" -DLOCKDIR_PATH=\"/var/lock/op encryptoki\" -DOCK_CONFDIR=\"/etc/opencryptoki\" -DOCK_LOGDIR=\"/var/log/opencryptoki\" -c -o pkcscca-pkcscca.o `test -f 'pkcscca.c' || echo './'`pkcscca.c pkcscca.c:18:26: fatal error: linux/limits.h: No such file or directory compilation terminated. If this is not trivially fixable, please request decrufting of the outdated binary packages. Andreas
Bug#822427: pristine-tar: should create reproducible deltas
Package: pristine-tar Version: 1.33 Severity: normal Hi, pristine-tar gendelta tarball.tar.gz delta1 pristine-tar gendelta tarball.tar.gz delta2 produces two different deltas, mainly due to different timestamps. It would be great, if pristine-tar could take this into account and create more easily reproducible deltas. One would be to use gzip -n to omit the timestamp when compressing the delta data. Another problem are the timestamps inside the (delta) tarball. The input tarball should have enough sources to provide a usable timestamp: * the gzip timestamp (unless created with gzip -n) * the modification time of the newest file/directory inside the tarball (the filesystem timestamp of that tarball is not a usable option) With a recent tar, there is a --mtime option that could be used while creating the delta tarball. Andreas PS: hmm, using pristine-tar again on the delta it created ... no I'm not going to explore this idea :-)
Bug#822435: python-extractor,python-sfepy: error when trying to install together
Package: python-extractor,python-sfepy Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 1:0.6-4 Control: found -1 2016.1-1 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 python-sfepy. Preparing to unpack .../python-sfepy_2016.1-1_amd64.deb ... Unpacking python-sfepy (2016.1-1) ... dpkg: error processing archive /var/cache/apt/archives/python-sfepy_2016.1-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/extractor.py', which is also in package python-extractor 1:0.6-4 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/python2.7/dist-packages/extractor.py 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 python-extractor=1%0.6-4_python-sfepy=2016.1-1.log.gz Description: application/gzip
Bug#823102: (Build-)Depends: firestring which has been requested to be removed
Source: firedns Version: 0.9.12+dfsg-5 Severity: serious Control: block 811358 with -1 Hi, firedns Build-Depends and Depends on firedns which has been requested to be removed. (#811358) Should firedns be removed as well? Andreas
Bug#823211: python-pygccxml-doc: fails to upgrade from 'jessie' - trying to overwrite /usr/share/doc-base/pygccxml-apidocs
Package: python-pygccxml-doc Version: 1.7.4-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', 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#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package python-pygccxml-doc. Preparing to unpack .../python-pygccxml-doc_1.7.4-2_all.deb ... Unpacking python-pygccxml-doc (1.7.4-2) ... dpkg: error processing archive /var/cache/apt/archives/python-pygccxml-doc_1.7.4-2_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/pygccxml-apidocs', which is also in package python-pygccxml 1.0.0-4 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python-pygccxml-doc_1.7.4-2_all.deb cheers, Andreas python-pygccxml=1.0.0-4_python-pygccxml-doc=1.7.4-2.log.gz Description: application/gzip
Bug#793062: applied NMUs
On 2016-05-23 06:19, Michael Biebl wrote: > Version: 0.28.debian-5 > > Re-applied all NMUs that were missed in the -4 upload. Thanks! Andreas
Bug#808309: mgp: fails to purge: subprocess installed post-removal script returned error exit status 1
Followup-For: Bug #808309 Control: severity -1 serious Control: notfound -1 1.13a+upstream20090219-6 Hi, I just checked the postrm script. This doesn't work as intended: test -f /etc/defoma/mgp.subst-rule && rm -f /etc/defoma/mgp.subst-rule because it always fails if the file does not exist. Since you use rm -f, you can just skip the test for existence of the file. Andreas PS: false && true ; echo $?
Bug#826120: sendmail queue runner dies due to an assertion violation in libldap
Control: fixed -1 8.14.8-1 On 2016-06-02 13:50, Andreas Piper wrote: > The same bug has been reported and fixed on RedHat-Linux with package > sendmail-8.14.4-9.el6, see https://access.redhat.com/solutions/1979993 > Could it be possible to implement this fix also on debian? Can you test a proposed package with this fix on jessie? I've pushed the changes to the git repository on alioth in branch "jessie". Andreas
Bug#828540: sendmail: FTBFS with openssl 1.1.0
Control: tag -1 help
Hi Kurt,
maybe you can help me getting sendmail (which I'm QA maintaining for
some years now) to work with the new openssl.
On 2016-06-26 12:24, Kurt Roeckx wrote:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/sendmail_8.15.2-4_amd64-20160529-1535
> If you have problems making things work, feel free to contact us.
in debian/configure.ac we have
if test $ac_cv_header_openssl_ssl_h = yes; then
AC_CHECK_LIB(ssl, SSL_library_init,
[sm_have_tls=yes]
,[sm_have_tls=no]
,[-lcrypto])
if test $sm_have_tls != yes; then
AC_MSG_WARN([Could not find -lssl (libssl-dev)])
fi;
fi;
which fails. The whole autotools stuff is only used for the debian packaging.
That fails because SSL_library_init is now a macro instead of a function.
Maybe this check is superfluous and could just be removed.
If I do this, building fails due to some API changes:
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I.
-I../../include-DSOCKETMAP -DMAP_REGEX -DNEWDB -DNIS -DNISPLUS -DLDAPMAP
-DHASFCHMOD=1 -DHASSETRLIMIT=1 -DHASFLOCK=0 -DUSESETEUID=1 -DHASGETUSERSHELL=1
-DNETINET6 -D_PATH_SENDMAILPID=\"/var/run/sendmail/mta/sendmail.pid\"
-DIP_SRCROUTE=1 -DLDAP_REFERRALS -D_FFR_LDAP_URI -D_FFR_LDAP_SETVERSION
-DLDAP_DEPRECATED -DTCPWRAPPERS -DSASL -I/usr/include/sasl -DSTARTTLS
-D_FFR_QUEUE_SCHED_DBG -D_FFR_SKIP_DOMAINS -D_FFR_GROUPREADABLEAUTHINFOFILE
-D_FFR_DAEMON_NETUNIX -D_FFR_NO_PIPE -D_FFR_SHM_STATUS -D_FFR_RHS
-D_FFR_MAIL_MACRO -D_FFR_QUEUEDELAY=1 -D_FFR_BADRCPT_SHUTDOWN
-D_FFR_RESET_MACRO_GLOBALS -D_FFR_TLS_1 -D_FFR_TLS_EC
-D_FFR_DEAL_WITH_ERROR_SSL -Wdate-time -D_FORTIFY_SOURCE=2 -c -o tls.o tls.c
tls.c: In function 'get_dh512':
tls.c:70:4: error: dereferencing pointer to incomplete type 'DH {aka struct
dh_st}'
dh->p = BN_bin2bn(dh512_p, sizeof(dh512_p), NULL);
^
tls.c: In function 'inittls':
tls.c:929:22: warning: implicit declaration of function 'BIO_s_file_internal'
[-Wimplicit-function-declaration]
crl_file = BIO_new(BIO_s_file_internal());
^
tls.c:929:22: warning: passing argument 1 of 'BIO_new' makes pointer from
integer without a cast [-Wint-conversion]
In file included from /usr/include/openssl/ssl.h:48:0,
from ./sendmail.h:125,
from tls.c:11:
/usr/include/openssl/bio.h:538:6: note: expected 'const BIO_METHOD * {aka const
struct bio_method_st *}' but argument is of type 'int'
BIO *BIO_new(const BIO_METHOD *type);
^
tls.c:1006:6: warning: 'RSA_generate_key' is deprecated
[-Wdeprecated-declarations]
(rsa_tmp = RSA_generate_key(RSA_KEYLENGTH, RSA_F4, NULL,
^
In file included from /usr/include/openssl/rsa.h:13:0,
from /usr/include/openssl/x509.h:31,
from /usr/include/openssl/ssl.h:50,
from ./sendmail.h:125,
from tls.c:11:
/usr/include/openssl/rsa.h:193:1: note: declared here
DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned long e, void
^
tls.c:1213:4: warning: 'DSA_generate_parameters' is deprecated
[-Wdeprecated-declarations]
dsa = DSA_generate_parameters(bits, NULL, 0, NULL,
^
In file included from /usr/include/openssl/dh.h:13:0,
from /usr/include/openssl/dsa.h:31,
from /usr/include/openssl/x509.h:32,
from /usr/include/openssl/ssl.h:50,
from ./sendmail.h:125,
from tls.c:11:
/usr/include/openssl/dsa.h:121:1: note: declared here
DEPRECATEDIN_0_9_8(DSA *DSA_generate_parameters(int bits,
^
tls.c:1298:5: warning: implicit declaration of function
'SSL_CTX_set_tmp_rsa_callback' [-Wimplicit-function-declaration]
SSL_CTX_set_tmp_rsa_callback(*ctx, tmp_rsa_key);
^
tls.c: In function 'tmp_rsa_key':
tls.c:1747:2: warning: 'RSA_generate_key' is deprecated
[-Wdeprecated-declarations]
rsa_tmp = RSA_generate_key(RSA_KEYLENGTH, RSA_F4, NULL, NULL);
^
In file included from /usr/include/openssl/rsa.h:13:0,
from /usr/include/openssl/x509.h:31,
from /usr/include/openssl/ssl.h:50,
from ./sendmail.h:125,
from tls.c:11:
/usr/include/openssl/rsa.h:193:1: note: declared here
DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned long e, void
^
tls.c: In function 'x509_verify_cb':
tls.c:1974:10: error: dereferencing pointer to incomplete type 'X509_STORE_CTX
{aka struct x509_store_ctx_st}'
if (ctx->error == X509_V_ERR_UNABLE_TO_GET_CRL)
^
: recipe for target 'tls.o' failed
The file in question is sendmail/tls.c
Since I'm used to neither openssl nor the sendmail source code (and I
have no use for sendmail at all, now that it passes the piuparts
tests), I'm not going to write a patch for supporting openssl 1.1.0
along 1.0.2.
I
Bug#832291: bogofilter-{bdb, sqlite, tokyocabinet}: copyright file missing after upgrade (policy 12.5)
Package: bogofilter-bdb,bogofilter-sqlite,bogofilter-tokyocabinet
Version: 1.2.4+dfsg1-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.
This was observed on the following upgrade paths:
jessie -> stretch
>From the attached log (scroll to the bottom...):
1m18.5s ERROR: WARN: Inadequate results from running adequate!
bogofilter-bdb: missing-copyright-file /usr/share/doc/bogofilter-bdb/copyright
MISSING COPYRIGHT FILE: /usr/share/doc/bogofilter-bdb/copyright
# ls -lad /usr/share/doc/bogofilter-bdb
drwxr-xr-x 2 root root 40 Jun 10 11:52 /usr/share/doc/bogofilter-bdb
# ls -la /usr/share/doc/bogofilter-bdb/
total 0
drwxr-xr-x 2 root root 40 Jun 10 11:52 .
drwxr-xr-x 109 root root 2300 Jun 10 11:52 ..
Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile
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.
cheers,
Andreas
bogofilter-bdb_1.2.4+dfsg1-6.log.gz
Description: application/gzip
Bug#832304: bochs: switch B-D from iasl to acpica-tools
Source: bochs Version: 2.6-5 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, the iasl transitional package is gone, finally. Please switch the B-D to acpica-tools. Andreas
Bug#832304: Acknowledgement (bochs: switch B-D from iasl to acpica-tools)
Control: severity -1 important acpica-tools still Provides: iasl Andreas
Bug#832291: bogofilter-{bdb, sqlite, tokyocabinet}: copyright file missing after upgrade (policy 12.5)
On 2016-07-28 02:55, Herbert wrote:
Read these two paragraphs from the original report! This is exactly your
problem!
>> 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.
> bogofilter-{bdb, sqlite, tokyocabinet} depends on bogofilter-common[0],
> which has the copyright file[1]. And I used:
That's fine
> override_dh_installdocs:
> dh_installdocs --link-doc=bogofilter-common
Which is also fine, but not sufficient for clean upgrades.
Andreas
Bug#837331: vlock: fails to install, remove, and install again
Package: vlock Version: 2.2.2-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install, remove (but not purge), and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is the same version that is going to be installed again. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): 0m27.8s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpvoT99A', 'apt-get', '-y', 'install', 'vlock=2.2.2-6'] 0m29.0s DUMP: Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: vlock debconf: delaying package configuration, since apt-utils is not installed 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/36.7 kB of archives. After this operation, 120 kB of additional disk space will be used. dpkg: unrecoverable fatal error, aborting: unknown group 'vlock' in statoverride file E: Sub-process /usr/bin/dpkg returned an error code (2) 0m29.0s ERROR: Command failed (status=100): ['chroot', '/tmp/piupartss/tmpvoT99A', 'apt-get', '-y', 'install', 'vlock=2.2.2-6'] cheers, Andreas vlock_2.2.2-6.log.gz Description: application/gzip
Bug#837360: cuneiform: FTBFS with GCC 6: error: narrowing conversion of '196' from 'int' to 'char' inside { }
Source: cuneiform
Version: 1.1.0+dfsg-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
cuneiform FTBFS in sid since the default compiler was switched to GCC 6:
/build/cuneiform-1.1.0+dfsg/cuneiform_src/Kern/include/utf8-tables.h:1367:1:
error: narrowing conversion of '196' from 'int' to 'char' inside { }
[-Wnarrowing]
/build/cuneiform-1.1.0+dfsg/cuneiform_src/Kern/include/utf8-tables.h:1367:1:
error: narrowing conversion of '151' from 'int' to 'char' inside { }
[-Wnarrowing]
/build/cuneiform-1.1.0+dfsg/cuneiform_src/Kern/include/utf8-tables.h:1367:1:
error: narrowing conversion of '196' from 'int' to 'char' inside { }
[-Wnarrowing]
... and many more occurrences ...
full log attached
Andreas
cuneiform_1.1.0+dfsg-5.log.gz
Description: application/gzip
Bug#832291: bogofilter-{bdb, sqlite, tokyocabinet}: copyright file missing after upgrade (policy 12.5)
Followup-For: Bug #832291 Hi, there is still something broken. After an upgrade from jessie to stretch bogofilter-common has lost some of its files: 2m9.4s ERROR: FAIL: debsums reports modifications inside the chroot: debsums: missing file /usr/share/doc/bogofilter-common/NEWS.Debian.gz (from bogofilter-common package) debsums: missing file /usr/share/doc/bogofilter-common/README.db.gz (from bogofilter-common package) debsums: missing file /usr/share/doc/bogofilter-common/changelog.Debian.gz (from bogofilter-common package) debsums: missing file /usr/share/doc/bogofilter-common/copyright (from bogofilter-common package) > * debian/bogofilter.preinst (created): > debian/bogofilter-bdb.preinst: > debian/bogofilter-sqlite.preinst: > debian/bogofilter-tokyocabinet.preinst: > - using the script from https://wiki.debian.org/MissingCopyrightFile Adding these maintainer scripts manually is the wrong approach nowadays. d/$package.maintscript should be used instead - it covers all installation and upgrade scenarios, including failure handling. Andreas
Bug#828540: sendmail: FTBFS with openssl 1.1.0
On 2016-09-12 09:02, Sebastian Andrzej Siewior wrote:
> could you please try if the patch attached works? It compiles :)
Many thanks, so let's just try it :-)
It FTBFS on the non-linux architectures:
https://buildd.debian.org/status/package.php?p=sendmail&suite=unstable
It's this part of your patch:
@@ -1002,9 +1047,23 @@ inittls(ctx, req, options, srv, certfile, keyfile,
cacertpath, cacertfile, dhpar
if (bitset(TLS_I_RSA_TMP, req)
# if SM_CONF_SHM
- && ShmId != SM_SHM_NO_ID &&
- (rsa_tmp = RSA_generate_key(RSA_KEYLENGTH, RSA_F4, NULL,
- NULL)) == NULL
+ && ShmId != SM_SHM_NO_ID) {
+ BIGNUM *bn;
+
+ bn = BN_new();
+ rsa_tmp = RSA_new();
+ if (!bn || !rsa_tmp || !BN_set_word(bn, RSA_F4)) {
+ RSA_free(rsa_tmp);
+ rsa_tmp = NULL;
+ }
+ if (rsa_tmp) {
+ if (!RSA_generate_key_ex(rsa_tmp, RSA_KEYLENGTH, bn,
NULL)) {
+ RSA_free(rsa_tmp);
+ rsa_tmp = NULL;
+ }
+ }
+ BN_free(bn);
+ if (!rsa_tmp
# else /* SM_CONF_SHM */
&& 0/* no shared memory: no need to generate key now */
# endif /* SM_CONF_SHM */
@@ -1020,6 +1079,7 @@ inittls(ctx, req, options, srv, certfile, keyfile,
cacertpath, cacertfile, dhpar
}
return false;
}
+ }
# endif /* !TLS_NO_RSA */
/*
The braces don't match the #if scope (opened within SM_CONF_SHM, closed
outside).
kfreebsd doesn't seem to have shmem.
Andreas
Bug#840831: libvirtuoso5.5-cil: fails to install: E: installing Assembly /usr/lib/cli/virtuoso-5.5/OpenLink.Data.Virtuoso.dll failed
Package: libvirtuoso5.5-cil Version: 6.1.6+dfsg2-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 libvirtuoso5.5-cil. (Reading database ... (Reading database ... 7366 files and directories currently installed.) Preparing to unpack .../libvirtuoso5.5-cil_6.1.6+dfsg2-3+b1_amd64.deb ... Unpacking libvirtuoso5.5-cil (6.1.6+dfsg2-3+b1) ... Setting up libvirtuoso5.5-cil (6.1.6+dfsg2-3+b1) ... * Installing 1 assembly from libvirtuoso5.5-cil into Mono E: installing Assembly /usr/lib/cli/virtuoso-5.5/OpenLink.Data.Virtuoso.dll failed E: Installation of libvirtuoso5.5-cil with /usr/share/cli-common/runtimes.d/mono failed dpkg: error processing package libvirtuoso5.5-cil (--configure): subprocess installed post-installation script returned error exit status 29 Errors were encountered while processing: libvirtuoso5.5-cil cheers, andreas libvirtuoso5.5-cil_6.1.6+dfsg2-3+b1.log.gz Description: application/gzip
Bug#840843: dia: leaves alternatives after purge: /etc/alternatives/dia
Package: dia Version: 0.97.3+git20160930-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails The leftover files are actually alternatives that were installed by the package but have not been properly removed. While there is ongoing discussion how to remove alternatives correctly (see https://bugs.debian.org/71621 for details) the following strategy should work for regular cases: * 'postinst configure' always installs the alternative * 'prerm remove' removes the alternative * 'postrm remove' and 'postrm disappear' remove the alternative In all other cases a maintainer script is invoked (e.g. upgrade, deconfigure) the alternatives are not modified to preserve user configuration. Removing the alternative in 'prerm remove' avoids having a dangling link once the actual file gets removed, but 'prerm remove' is not called in all cases (e.g. unpacked but not configured packages or disappearing packages) so the postrm must remove the alternative again (update-alternatives gracefully handles removal of non-existing alternatives). Note that the arguments for adding and removing alternatives differ, for removal it's 'update-alternatives --remove '. Filing this as important as having a piuparts clean archive is a release goal since lenny. >From the attached log (scroll to the bottom...): 2m19.7s INFO: Warning: Package purging left files on system: /etc/alternatives/dia -> /usr/bin/dia-normal-integratednot owned This was observed on a jessie->stretch upgrade. cheers, Andreas dia_0.97.3+git20160930-1.log.gz Description: application/gzip
Bug#841508: dia: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/x86_64-linux-gnu/dia/libaadl_objects.so
Package: dia Version: 0.97.3+git20160930-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', 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#s-replaces >From the attached log (scroll to the bottom...): Selecting previously unselected package dia. Preparing to unpack .../dia_0.97.3+git20160930-2_amd64.deb ... Unpacking dia (0.97.3+git20160930-2) ... dpkg: error processing archive /var/cache/apt/archives/dia_0.97.3+git20160930-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dia/libaadl_objects.so', which is also in package dia-libs 0.97.3-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) cheers, Andreas dia-libs=0.97.3-1_dia=0.97.3+git20160930-2.log.gz Description: application/gzip
Re: Wheezy update of sendmail?
On 2016-10-29 18:49, Adrian Bunk wrote: > On Sun, Oct 23, 2016 at 08:59:47AM +0100, Chris Lamb wrote: >> Hello dear maintainer(s), >> >> the Debian LTS team would like to fix the security issues which are >> currently open in the Wheezy version of sendmail: >> https://security-tracker.debian.org/tracker/source-package/sendmail >> >> Would you like to take care of this yourself? >> ... > > sendmail is orphaned, so there is no maintainer. > > Andreas (Cc'ed) did some basic maintainance on sendmail recently, > but I doubt he would opposed to the LTS team taking care of this > issue. Please go ahead - probably we could use the fix (that someone produces for wheezy) for jessie and sid as well. Please put everything into git, branch wheezy, the repo is in collab-maint. Thanks Andreas
Bug#843382: imgtex: libapache-mod-fastcgi is gone
Package: imgtex Version: 0.20050123-9 Severity: serious Hi, libapache-mod-fastcgi has been removed from the archive, libapache-mod-fcgid is a possible (and free) replacement. Maybe the package can be moved from contrib to main once it no longer depends on non-free stuff. Andreas
Bug#843658: sendmail-cf: Customized sendmail.cf is being overwritten on startup
On 2016-11-08 16:33, Thomas Auge wrote: > in a recent development, updates started overwriting sendmail.cf, now it > seems a rebuild is forced on every startup. It's completely unexpected with > grave implications. Please do not overwrite modified configuration files > without asking. Something that appears prominently at the beginning of sendmail.cf (and that is not a Debian addition): ## # # DO NOT EDIT THIS FILE! Only edit the source .mc file. # ## (The last time I used sendmail (iirc 8.12) in a production environment about 15 years ago I hacked around in sendmail.mc and various *.m4 files, and had a sendmail.cf generated out of these, but never edited sendmail.cf manually) Andreas
Bug#843658: sendmail-cf: Customized sendmail.cf is being overwritten on startup
quoting from /etc/mail/sendmail.conf: # HANDS_OFF="No"; Binary Do *NOT* touch the configuration # Set this *ONLY* if you are going to be fully responsible for the entire # setup of sendmail - the directories, permissions, databases, etc. With # this variable set to "Yes", nothing will be done for you during updates. # # In other words, "The blood be upon your hands" if you set this... # My ability to help with problems will be greatly reduced ! # # "Well, a pet peeve of mine is people who directly edit the # .cf file instead of using the m4 configuration files. # Don't do it! [laughs] I treat the .cf file as a binary # file - you should too." # -- Eric Allman 1999/10/18 # http://www.dotcomeon.com/allman_sendmail_qa.html # HANDS_OFF="No";
Bug#841257: sendmail: Privilege escalation from group smmsp to (user) root
On 2016-10-19 08:12, paul.sz...@sydney.edu.au wrote: > Hmm (again) ... Maybe file /usr/share/sendmail/sendmail needs updating > also? It's generated from the same template script, only the initscript gets an additional header. I have a completely untested patch sitting in GIT - do you have a possibility to test packages built from that? Andreas
Re: Wheezy update of sendmail?
On 2016-10-31 23:17, Andreas Beckmann wrote: > Please go ahead - probably we could use the fix (that someone produces > for wheezy) for jessie and sid as well. Please put everything into git, > branch wheezy, the repo is in collab-maint. I have now a completely untested patch for this issue sitting in GIT master (can be cherry-picked into wheezy with only a changelog conflict). Any feedback and testing would be welcome. Andreas
Bug#841257: fixed in sendmail 8.15.2-7
On 2016-12-07 17:12, Axel 'the C.L.A.' Müller wrote:
> Seems this change now causes cron to spam like:
>
> From: root@e560 (Cron Daemon)
> To: root@e560
> Subject: Cron test -x /etc/init.d/sendmail && test
> -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail
> && /usr/share/sendmail/sendmail cron-msp
>
> su: Muss von einem Terminal gestartet werden.
>
> (Translation: "su: Needs to be started from a terminal")
>
can you try to replace the touch_stamp() method in
/usr/share/sendmail/sendmail with this:
touch_stamp() {
if [ "$(id -nu)" = "smmsp" ]; then
touch "$1"
else
su smmsp -s /bin/sh -c "touch '$1'"
fi
}
That should work at least for the smmsp cronjob ...
Andreas
Bug#841257: fixed in sendmail 8.15.2-7
On 2016-12-08 16:46, Axel 'the C.L.A.' Müller wrote: > Seems to work fine - at least I'm not getting those mails anymore. I've now implemented a different way to aquire lockfiles for the cronjobs, let's hope that does work as well. Just uploaded to unstable. Andreas
Bug#839048: fixed in mozjs 1.8.5-1.0.0+dfsg-5.1
On Fri, 09 Dec 2016 03:03:43 + John Paul Adrian Glaubitz wrote: >* Add Modify_tagged_pointer_structure_js1.8.5.patch to modify tagged > pointer to use 48 bit virtual address space (Closes: #839048). Was this issue only present in stretch/sid or is it also present in jessie? Andreas
Bug#847743: sendmail: STARTTLS server fails with "ca md too weak"
On 2016-12-11 11:22, Joerg Dorchain wrote: > following testing after upgrading from 8.15.2-6 to 8.15.2-7, > sendmail does not accept certain incoming connections anymore > and refuses the STARTTLS handshake with "ca md too weak". That is probably because the -7 package got built against openssl 1.1 while -6 was still at openssl 1.0. Cc:ing Kurt (the openssl maintainer), maybe he has some hints. > Most reproduceable way I found by now is the DANE validator at > https://dane.sys4.de/, which leave a log entry e.g.: > Dec 11 11:04:54 Redstar sm-mta[18223]: STARTTLS=server, error: accept > failed=-1, reason=ca md too weak, SSL_error=1, errno=0, retry=-1, > relay=dane.sys4.de [IPv6:2001:1578:400:111:0:0:3:1] > > Other affected parties include e.g. amazon. Andreas
Bug#847743: sendmail: STARTTLS server fails with "ca md too weak"
On 2016-12-12 16:51, Joerg Dorchain wrote: > Even in that case, IMHO it would be an idea to mark this bug as > "won't fix", or even to leave a line in the NEWS.debian, just in > case this version ever hits stable, as a hint for other CACert users > (or someone with md5-signatures) out there. A NEWS entry sounds sensible. Could you provide some wording? Andreas
Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
Hi Graham, On 2017-01-13 12:47, Graham Inggs wrote: > Thanks for the upload, Andreas! you could have done that QA upload yourself (even without filing a bug) :-) I only cared for it because orphaned packages shouldn't have RC bugs with patches. Andreas
Bug#850979: crafty: Does not run on Pentium 4 (Illegal instruction)
Hi Santiago, On Wed, 11 Jan 2017 20:12:13 +0100 Santiago Vila wrote: > On Wed, Jan 11, 2017 at 07:36:56PM +0100, Sven Joachim wrote: > > > The toplevel Makefile in the crafty source adds -march=k8 to CFLAGS, > > Hi. I checked that a rebuild fixed the issue, but I've also removed > the -march thing to be safe. can you fix that for jessie, too? Thanks Andreas
Bug#852126: apt-build: unowned files after purge (policy 6.8, 10.8): /etc/apt/sources.list.d/apt-build.list
Package: apt-build Version: 0.12.46 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. >From the attached log (scroll to the bottom...): 1m20.4s ERROR: FAIL: Package purging left files on system: /etc/apt/sources.list.d/apt-build.list not owned cheers, Andreas apt-build_0.12.46.log.gz Description: application/gzip
Bug#852126: apt-build: unowned files after purge (policy 6.8, 10.8): /etc/apt/sources.list.d/apt-build.list
Hi Axel, On 2017-01-21 20:41, Axel Beckert wrote: > I'm surprised that this doesn't show up on > https://piuparts.debian.org/sid/source/a/apt-build.html despite it's that's only an error on sid-strict https://piuparts.debian.org/sid-strict/source/a/apt-build.html Andreas
Bug#852144: python-uniconvertor-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-uniconvertor-dbg
Version: 1.1.5-3
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:
wheezy -> jessie -> stretch
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 (usually somewhere in the middle...):
1m32.0s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/python-uniconvertor-dbg/changelog.Debian.gz
(python-uniconvertor-dbg) !=
/usr/share/doc/python-uniconvertor/changelog.Debian.gz (python-uniconvertor)
/usr/share/doc/python-uniconvertor-dbg -> python-uniconvertor
/usr/share/doc/python-uniconvertor-dbg/copyright (python-uniconvertor-dbg) !=
/usr/share/doc/python-uniconvertor/copyright (python-uniconvertor)
/usr/share/doc/python-uniconvertor-dbg -> python-uniconvertor
cheers,
Andreas
python-uniconvertor-dbg_1.1.5-3.log.gz
Description: application/gzip
Bug#857210: binutils-m68hc1x: broken symlink: /usr/bin/m68hc12-gasp -> m68hc11-gasp
Package: binutils-m68hc1x Version: 1:2.18-8 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...): 0m30.4s ERROR: FAIL: Broken symlinks: /usr/bin/m68hc12-gasp -> m68hc11-gasp The m68hc11-gasp binary seems to be missing, but the manpage is there. cheers, Andreas binutils-m68hc1x_1:2.18-8.log.gz Description: application/gzip
Bug#857530: snoopy: broken symlink: /lib/snoopy.so -> libsnoopy.so.0.0.0
Package: snoopy Version: 2.3.2-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...): 0m19.7s ERROR: FAIL: Broken symlinks: /lib/snoopy.so -> libsnoopy.so.0.0.0 This seems to be a leftover from pre-multiarch, since the link already correctly exists in /lib/x86_64-linux-gnu: # apt-file search snoopy.so snoopy: /lib/snoopy.so snoopy: /lib/x86_64-linux-gnu/libsnoopy.so snoopy: /lib/x86_64-linux-gnu/libsnoopy.so.0 snoopy: /lib/x86_64-linux-gnu/libsnoopy.so.0.0.0 cheers, Andreas snoopy_2.3.2-1.log.gz Description: application/gzip
Bug#857878: starvoyager: uninstallable after binNMU
Package: starvoyager
Version: 0.4.4-8
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
The following packages have unmet dependencies:
starvoyager : Depends: starvoyager-data (= 0.4.4-8+b1) but it is not going to
be installed
This is either a
Depends: starvoyager-data (= ${binary:Version})
instead of
Depends: starvoyager-data (= ${source:Version})
or the result of dh_installdocs --link-doc
Cheers,
Andreas
Bug#715066: libindicate-gtk3-dev: missing Depends: libindicate-gtk3-3 (= ${binary:Version})
Followup-For: Bug #715066
Control: tag -1 patch
Control: block -1 with 849932
patch attached, package FTBFS due to #849932 in gtk-sharp2-gapi
Andreas
diff -u libindicate-0.6.92/debian/changelog libindicate-0.6.92/debian/changelog
--- libindicate-0.6.92/debian/changelog
+++ libindicate-0.6.92/debian/changelog
@@ -1,3 +1,11 @@
+libindicate (0.6.92-4) unstable; urgency=medium
+
+ * QA upload.
+ * libindicate-gtk3-dev: Depend on libindicate-gtk3-3 instead of
+libindicate-gtk3. (Closes: #715066)
+
+ -- Andreas Beckmann Fri, 17 Mar 2017 19:35:25 +0100
+
libindicate (0.6.92-3) unstable; urgency=medium
* QA upload.
diff -u libindicate-0.6.92/debian/control libindicate-0.6.92/debian/control
--- libindicate-0.6.92/debian/control
+++ libindicate-0.6.92/debian/control
@@ -92,7 +92,7 @@
Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends},
- libindicate-gtk3 (= ${binary:Version}),
+ libindicate-gtk3-3 (= ${binary:Version}),
libindicate-dev (= ${binary:Version}),
libdbus-glib-1-dev (>= 0.76),
libgtk-3-dev (>= 3.0)
