Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 989799 +pending Bug #989799 [manpages-l10n] psmisc: Undeclared file conflict with manpages-de from buster-backports Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 989799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 990417 +moreinfo Bug #990417 [src:qemu] openjdk-11-jre-headless: running java in qemu s390 gives a SIGILL at C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 990417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989799: psmisc: Undeclared file conflict with manpages-de
from buster-backports Message-Id: <20210630134637.d8e6f92027ef11aeb9a09...@iijmio-mail.jp> In-Reply-To: <20210627060424.GA7522@Debian-50-lenny-64-minimal> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sun, 27 Jun 2021 08:04:24 +0200 Helge Kreutzmann wrote: > manpages-l10n (4.10.0-1~bpo10+1) buster-backports; urgency=medium > > * Rebuild for buster-backports. > * Properly conflict with future versions of psmisc and procps so that > upgrades to bullseye will work without file conflicts. Closes: #989799 > > -- Helge Kreutzmann Sun, 20 Jun 2021 10:27:10 +0200 > > Also tracker.debian.org does not show (yet), that it has been accepted. Have it reached to buster-backports repo? -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#982991: matrix-synapse: not suitable for inclusion into bullseye
Hello, for any interested users of matrix-synapse: the NEWS file of the matrix-synapse package refers to the new repositories used for publishing updated packages: > matrix-synapse (1.27.0-1~bpo10+3) buster-backports; urgency=medium > > Since Synapse won’t be included in Bullseye (see #982991 for more > details), updating backports will soon no longer be possible. However, > updates will still be uploaded to unstable and also to the new distribution > channel: Debian Fasttrack. > > To learn more about Fasttrack and how to enable it, visit the project’s > website: https://fasttrack.debian.net/ > > -- Andrej Shadura Tue, 09 Mar 2021 13:50:38 +0100 Lars
Bug#990463: libgstreamer1.0-dev: please add Conflicts: libgstreamer0.10-dev
Package: libgstreamer1.0-dev
Version: 1.18.3-2
Severity: serious
Tags: patch
Hi,
when adding the code to clean up the obsolete diversions (#981203)
I forgot to add a conflict against libgstreamer0.10-dev which shipped
the files that were diverted. That package was last seen in jessie,
but may still be lingering around on long grown systems which will
cause this error:
Setting up libgstreamer1.0-dev:amd64 (1.18.4-2) ...
Removing 'diversion of /usr/bin/dh_gstscancodecs to
/usr/bin/dh_gstscancodecs-gst0.10 by libgstreamer1.0-dev'
dpkg-divert: error: rename involves overwriting '/usr/bin/dh_gstscancodecs'
with
different file '/usr/bin/dh_gstscancodecs-gst0.10', not allowed
dpkg: error processing package libgstreamer1.0-dev:amd64 (--configure):
installed libgstreamer1.0-dev:amd64 package post-installation script
subprocess returned error exit status 2
Andreas
>From 68301527dfa948c380d4401b15b74bad0d6d6da7 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Tue, 29 Jun 2021 18:54:21 +0200
Subject: [PATCH] libgstreamer1.0-dev: add Conflicts: libgstreamer0.10-dev
---
debian/changelog | 7 +++
debian/control | 2 +-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index 1c5d33b6..df3eb6a5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+gstreamer1.0 (1.18.4-3) UNRELEASED; urgency=medium
+
+ * libgstreamer1.0-dev: Add Conflicts: libgstreamer0.10-dev to ensure the
+diverted file is gone before the diversion is removed.
+
+ -- Andreas Beckmann Tue, 29 Jun 2021 18:52:34 +0200
+
gstreamer1.0 (1.18.4-2) unstable; urgency=medium
* Upload to unstable.
diff --git a/debian/control b/debian/control
index a5954eb2..90c1e483 100644
--- a/debian/control
+++ b/debian/control
@@ -65,7 +65,7 @@ Depends: libgstreamer1.0-0 (= ${binary:Version}),
${shlibs:Depends},
${misc:Depends},
gir1.2-gstreamer-1.0 (= ${binary:Version})
-Conflicts: libgstreamer-plugins-bad1.0-dev (<< 1.13.1)
+Conflicts: libgstreamer-plugins-bad1.0-dev (<< 1.13.1), libgstreamer0.10-dev
Replaces: libgstreamer-plugins-bad1.0-dev (<< 1.13.1)
Suggests: gstreamer1.0-doc
Description: GStreamer core development files
--
2.20.1
libgstreamer-ocaml-dev_0.3.0-2+b1.log.gz
Description: application/gzip
Bug#990344: exim 4.94.2 update default configuration option breaks MTA
Hello: Thank you very much for taking the time to write. On 29 Jun 2021 at 19:05, Marc Haber wrote: > The "exim installer" is called dpkg and is a core package ... Yes, I am quite aware of that. Which is *exactly* the reason I did not file a bug against dpkg. If anything, in the many years I have been using Linux, dpkg has always worked seamlessly every time and never shown me a bug. Kudos for that. 8^) But the bug I filed is against exim 4.94.2. > You have a point ... Yes, I *do* have a point. But unfortunately I am not being able to get it across. That dpkg pop up a *different* warning was meant to be an example of sorts, not to be taken literally. To drive home the concept, so to speak. Maybe the wrong example as I am not versed in the inner workings of dpkg (or anything Linux for that matter) although today I learnt something about how dpkg works. Like I have said previously: The problem is with the exim 4.94.2 package. It should *not* be able/allowed to use *any* of a previously installed version's configuration files when updated. Much less (and yes, it *is* a bug) offer the user the choice of keeping *any* of them when it gets installed by dpkg. Now, *how* it does that, whether through a well written script, a previous [c]apt-get purge exim4[/c] or dev-magic (joke!) should be absolutely transparent to the end user and result in a properly installed MTA. And not a hopelessly broken one piling up warnings in paniclog. > I apologize, but there is nothing the Debian exim maintainers ... So I gather. Well, that's that. I did my part and reported the problem. It is now up to the exim maintainers to do what they think is best. Greetings. CIV
Processed: autosize build is broken (throws error is diaspora web console)
Processing control commands: > affects -1 ruby-rails-assets-autosize,diaspora Bug #990458 [libjs-autosize] autosize build is broken (throws error is diaspora web console) Added indication that 990458 affects ruby-rails-assets-autosize and diaspora -- 990458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990458 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990458: autosize build is broken (throws error is diaspora web console)
Package: libjs-autosize
Severity: grave
Version: 4.0.2~dfsg1-5
Control: affects -1 ruby-rails-assets-autosize,diaspora
I think during transition to babel7 something broke.
This causes diaspora ui to break,
Uncaught ReferenceError: module is not defined
at
main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3
at $.fn.charCount
(main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3)
at
main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3
This leads to,
(t((t={exports:{}}).exports),e.autosize=t.exports)}("undefined"!=typeof
globalThis?globalThis:"undefined"!=typeof
self?self:this,function(e){"use strict";function n(a){function e(){var
e=window.getComputedStyle(a,null);"vertical"===e.resize?a.style.resize="none":"both"===e.resize&&(a.style.resize="horizontal"),r="content-box"===e.boxSizing?-(parseFloat(e.paddingTop)+parseFloat(e.paddingBottom)):parseFloat(e.borderTopWidth)+parseFloat(e.borderBottomWidth),isNaN(r)&&(r=0),i()}function
o(e){var
t=a.style.width;a.style.width="0px",a.offsetWidth,a.style.width=t,a.style.overflowY=e}function
n(e){for(var t=[];e&& instanceof
Element;)e.parentNode.scrollTop&({node:e.parentNode,scrollTop:e.parentNode.scrollTop}),e=e.parentNode;return
t}function s(){var
e,t;0!==a.scrollHeight&&(e=n(a),t=document.documentElement&,a.style.height="",a.style.height=a.scrollHeight+r+"px",l=a.clientWidth,e.forEach(function(e){e.node.scrollTop=e.scrollTop}),t&&(document.documentElement.scrollTop=t))}function
i(){s();var
e=Math.round(parseFloat(a.style.height)),t=window.getComputedStyle(a,null),n="content-box"===t.boxSizing?Math.round(parseFloat(t.height)):a.offsetHeight;if(nr,l,c,u,d;a&&&"TEXTAREA"===a.nodeName&&!p.has(a)&&(c=l=r=null,u=function
u(){a.clientWidth!==l&()},d=function(t){window.removeEventListener("resize",u,!1),a.removeEventListener("input",i,!1),a.removeEventListener("keyup",i,!1),a.removeEventListener("autosize:destroy",d,!1),a.removeEventListener("autosize:update",i,!1),Object.keys(t).forEach(function(e){a.style[e]=t[e]}),p["delete"](a)}.bind(a,{height:a.style.height,resize:a.style.resize,overflowY:a.style.overflowY,overflowX:a.style.overflowX,wordWrap:a.style.wordWrap}),a.addEventListener("autosize:destroy",d,!1),"onpropertychange"in
a&&"oninput"in
a&("keyup",i,!1),window.addEventListener("resize",u,!1),a.addEventListener("input",i,!1),a.addEventListener("autosize:update",i,!1),a.style.overflowX="hidden",a.style.wordWrap="break-word",p.set(a,{destroy:d,update:i}),e())}function
t(e){e=p.get(e);e&()}function
i(e){e=p.get(e);e&()}e["default"]=void 0;var
a,o,p="function"==typeof Map?new Map:(a=[],o=[],{has:function
r(e){return-1o[a.indexOf(e)]},set:function
c(e,t){-1===a.indexOf(e)&&(a.push(e),o.push(t))},"delete":function
u(e){e=a.indexOf(e);-1m(e){return new Event(e,{bubbles:!0})};try{new
Event("test")}catch(d){m=function m(e){var
t=document.createEvent("Event");return t.initEvent(e,!0,!1),t}}var
s=null;"undefined"==typeof window||"function"!=typeof
window.getComputedStyle?((s=function s(e){return
e}).destroy=function(e){return e},s.update=function(e){return
e}):((s=function s(e,t){return
e&(e.length?e:[e],function(e){return
n(e,t)}),e}).destroy=function(e){return
e&(e.length?e:[e],t),e},s.update=function(e){return
e&(e.length?e:[e],i),e}),e["default"]=s,module.exports=exports["default"]}),$.fn.charCount=function(i)
Bug#990317: marked as done (librust-object+compression-dev: please use a versioned dependency for librust-flate2-1+default-dev)
Your message dated Tue, 29 Jun 2021 17:48:27 + with message-id and subject line Bug#990317: fixed in rust-object 0.12.0-4 has caused the Debian Bug report #990317, regarding librust-object+compression-dev: please use a versioned dependency for librust-flate2-1+default-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 990317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-object+compression-dev Version: 0.12.0-3 Severity: serious Tags: patch librust-object+compression-dev depends on librust-flate2-1+default-dev which is a (versioned) virtual package provided by librust-flate2+zlib-dev in buster and by librust-flate2+rust-backend-dev in bullseye. apt-get has problems exchanging these two packages during an upgrade from buster to bullseye and prefers to keep the already installed provider installed. This can be fixed by making the dependency versioned s.t. the old provider from buster is no longer considered as a valid solution. Bad problem resolution by apt-get: Starting 2 pkgProblemResolver with broken count: 5 Investigating (0) librust-goblin+pe32-dev:amd64 < 0.0.19-1 @ii mK Ib > Broken librust-goblin+pe32-dev:amd64 Depends on librust-goblin-dev:amd64 < 0.0.19-1 -> 0.2.1-4 @ii umU > (= 0.0.19-1) Considering librust-goblin-dev:amd64 5 as a solution to librust-goblin+pe32-dev:amd64 -2 Removing librust-goblin+pe32-dev:amd64 rather than change librust-goblin-dev:amd64 Investigating (0) librust-goblin+pe64-dev:amd64 < 0.0.19-1 @ii mK Ib > Broken librust-goblin+pe64-dev:amd64 Depends on librust-goblin-dev:amd64 < 0.0.19-1 -> 0.2.1-4 @ii umU > (= 0.0.19-1) Considering librust-goblin-dev:amd64 5 as a solution to librust-goblin+pe64-dev:amd64 -2 Removing librust-goblin+pe64-dev:amd64 rather than change librust-goblin-dev:amd64 Investigating (0) librust-goblin+mach64-dev:amd64 < 0.0.19-1 @ii mK Ib > Broken librust-goblin+mach64-dev:amd64 Depends on librust-goblin-dev:amd64 < 0.0.19-1 -> 0.2.1-4 @ii umU > (= 0.0.19-1) Considering librust-goblin-dev:amd64 5 as a solution to librust-goblin+mach64-dev:amd64 -2 Removing librust-goblin+mach64-dev:amd64 rather than change librust-goblin-dev:amd64 Investigating (0) librust-parity-wasm+std-dev:amd64 < 0.35.5-1 @ii mK Ib > Broken librust-parity-wasm+std-dev:amd64 Depends on librust-parity-wasm-dev:amd64 < 0.35.5-1 -> 0.41.0-1 @ii umU > (= 0.35.5-1) Considering librust-parity-wasm-dev:amd64 0 as a solution to librust-parity-wasm+std-dev:amd64 -2 Removing librust-parity-wasm+std-dev:amd64 rather than change librust-parity-wasm-dev:amd64 Investigating (0) librust-flate2+zlib-dev:amd64 < 1.0.6-1 @ii mK Ib > Broken librust-flate2+zlib-dev:amd64 Depends on librust-flate2-dev:amd64 < 1.0.6-1 -> 1.0.13-3 @ii umU > (= 1.0.6-1) Considering librust-flate2-dev:amd64 0 as a solution to librust-flate2+zlib-dev:amd64 -2 Removing librust-flate2+zlib-dev:amd64 rather than change librust-flate2-dev:amd64 Investigating (1) librust-object+compression-dev:amd64 < 0.11.0-1 -> 0.12.0-3 @ii umU Ib > Broken librust-object+compression-dev:amd64 Depends on librust-flate2-1+default-dev:amd64 < none @un H > Considering librust-flate2+zlib-dev:amd64 -2 as a solution to librust-object+compression-dev:amd64 2 Added librust-flate2+zlib-dev:amd64 to the remove list Fixing librust-object+compression-dev:amd64 via keep of librust-flate2+zlib-dev:amd64 Investigating (1) librust-flate2+zlib-dev:amd64 < 1.0.6-1 @ii mK Ib > Broken librust-flate2+zlib-dev:amd64 Depends on librust-flate2-dev:amd64 < 1.0.6-1 -> 1.0.13-3 @ii umU > (= 1.0.6-1) Considering librust-flate2-dev:amd64 0 as a solution to librust-flate2+zlib-dev:amd64 -2 Removing librust-flate2+zlib-dev:amd64 rather than change librust-flate2-dev:amd64 Investigating (2) librust-object+compression-dev:amd64 < 0.11.0-1 -> 0.12.0-3 @ii umU Ib > Broken librust-object+compression-dev:amd64 Depends on librust-flate2-1+default-dev:amd64 < none @un H > Considering librust-flate2+zlib-dev:amd64 -2 as a solution to librust-object+compression-dev:amd64 2 Added librust-flate2+zlib-dev:amd64 to the remove list Fixing librust-object+compression-dev:amd64 via keep of librust-flate2+zlib-dev:amd64 Investigating (2) librust-flate2+zlib-dev:amd64 < 1.0.6-1 @ii mK Ib > Broken librust-flate2+zlib-dev:amd64 Depends on librust-flate2-dev:amd64 < 1.0.6-1 -> 1.0.13-3 @ii umU > (= 1.0.6-1) Considering librust-flate2-dev:amd64 0 as a
Bug#990344: exim 4.94.2 update default configuration option breaks MTA
On Tue, Jun 29, 2021 at 08:17:16AM -0300, sawb...@xsmail.com wrote: > It would make a lot more sense (and would have saved me a lot of > grief) if the exim 4.94.2 installer would have popped up something > like this: The "exim installer" is called dpkg and is a core package of Debian. You can file bugs against it using "reportbug dpkg". The dpkg-conffile prompts are issued by dpkg, and it is neither possible to influence those prompts from a package nor are we allowed by policy to "manually" tamper with dpkg-conffiles from within a package maintainer script. This probably concludes what we as exim maintainers can say and/or do. You have a point, but you should take this up to the dpkg maintainer who would be in a position to change a user interface that has been mainly unchanged for two decades. Personally, I think it would be a very bad idea to change this three weeks for a planned release date. I apologize, but there is nothing the Debian exim maintainers can to other than to pop up a warning which we actually already do. And no, three weeks before a planned release date we are not going to change the wording of this warning. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#990436: marked as done (librust-cargo-dev: please use a versioned dependency for librust-flate2-1+{default,zlib}-dev)
Your message dated Tue, 29 Jun 2021 16:35:45 +
with message-id
and subject line Bug#990436: fixed in rust-cargo 0.43.1-4
has caused the Debian Bug report #990436,
regarding librust-cargo-dev: please use a versioned dependency for
librust-flate2-1+{default,zlib}-dev
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
990436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-cargo-dev
Version: 0.43.1-3
Severity: serious
Tags: patch
librust-cargo-dev depends on librust-flate2-1+default-dev and
librust-flate2-1+zlib-dev which are (versioned) virtual packages
provided by librust-flate2+zlib-dev in buster and by
librust-flate2+rust-backend-dev and librust-flate2+libz-sys-dev
in bullseye. apt-get has problems exchanging these two packages during an
upgrade from buster to bullseye and prefers to keep the already installed
provider installed. This can be fixed by making the dependency versioned
s.t. the old provider from buster is no longer considered as a valid
solution.
Andreas
diff -Nru rust-cargo-0.43.1/debian/changelog rust-cargo-0.43.1/debian/changelog
--- rust-cargo-0.43.1/debian/changelog 2020-12-07 06:19:36.0 +0100
+++ rust-cargo-0.43.1/debian/changelog 2021-06-28 14:13:18.0 +0200
@@ -1,3 +1,14 @@
+rust-cargo (0.43.1-4) UNRELEASED; urgency=medium
+
+ * librust-cargo-dev: Bump the dependency version on the virtual packages
+librust-flate2-1+default-dev and librust-flate2-1+zlib-dev for smoother
+upgrades from buster which need to switch the provider from
+librust-flate2+zlib-dev to librust-flate2+rust-backend-dev and
+librust-flate2+libz-sys-dev. (Closes: #-1)
+ * Bump the version in the Build-Depends for consistency.
+
+ -- Andreas Beckmann Mon, 28 Jun 2021 14:13:18 +0200
+
rust-cargo (0.43.1-3) unstable; urgency=medium
* Team upload.
diff -Nru rust-cargo-0.43.1/debian/control rust-cargo-0.43.1/debian/control
--- rust-cargo-0.43.1/debian/control2020-12-07 06:19:36.0 +0100
+++ rust-cargo-0.43.1/debian/control2021-06-28 14:13:12.0 +0200
@@ -21,8 +21,8 @@
librust-curl-sys-0.4+default-dev (>= 0.4.22-~~) ,
librust-env-logger-0.7+default-dev ,
librust-filetime-0.2+default-dev ,
- librust-flate2-1+default-dev (>= 1.0.3-~~) ,
- librust-flate2-1+zlib-dev (>= 1.0.3-~~) ,
+ librust-flate2-1+default-dev (>= 1.0.13-~~) ,
+ librust-flate2-1+zlib-dev (>= 1.0.13-~~) ,
librust-fs2-0.4+default-dev ,
librust-fwdansi-1+default-dev ,
librust-git2-0.13+default-dev (>= 0.13.11-~~) ,
@@ -109,8 +109,8 @@
librust-curl-sys-0.4+default-dev (>= 0.4.22-~~),
librust-env-logger-0.7+default-dev,
librust-filetime-0.2+default-dev,
- librust-flate2-1+default-dev (>= 1.0.3-~~),
- librust-flate2-1+zlib-dev (>= 1.0.3-~~),
+ librust-flate2-1+default-dev (>= 1.0.13-~~),
+ librust-flate2-1+zlib-dev (>= 1.0.13-~~),
librust-fs2-0.4+default-dev,
librust-fwdansi-1+default-dev,
librust-git2-0.13+default-dev (>= 0.13.11-~~),
--- End Message ---
--- Begin Message ---
Source: rust-cargo
Source-Version: 0.43.1-4
Done: Peter Michael Green
We believe that the bug you reported is fixed in the latest version of
rust-cargo, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 990...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green (supplier of updated rust-cargo
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 29 Jun 2021 15:59:14 +
Source: rust-cargo
Architecture: source
Version: 0.43.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
Changed-By: Peter Michael Green
Closes: 990436
Changes:
rust-cargo (0.43.1-4) unstable; urgency=medium
.
* Team upload.
* Package cargo 0.43.1 from crates.io using debcargo 2.4.3
* Bump dependency on flate2 to ease buster->bullseye upgrades
(Closes: #990436).
Checksums-Sha1:
76c734fc362778382b5e7fcb5655c4a271340064 6190 rust-cargo_0.43.1-4.dsc
9b2ca7d9737661a287996679efae524bcf4e1209 5336 rust-cargo_0.43.1-4.debian.tar.xz
a612461db0fc988234a867940a4a3c8508ccfb4c 13860
Bug#986293: marked as done (libvirtuoso5.5-cil: fails to upgrade from 'buster': The type initializer for 'Sys' threw an exception.)
Your message dated Tue, 29 Jun 2021 14:10:15 + with message-id and subject line Bug#986293: fixed in mono 6.8.0.105+dfsg-3.1 has caused the Debian Bug report #986293, regarding libvirtuoso5.5-cil: fails to upgrade from 'buster': The type initializer for 'Sys' threw an exception. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986293 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libvirtuoso5.5-cil Version: 7.2.5.1+dfsg-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. This may be related to a similar error in libglib3.0-cil (#986275). >From the attached log (scroll to the bottom...): Preparing to unpack .../54-libvirtuoso5.5-cil_7.2.5.1+dfsg-3_amd64.deb ... Removing libvirtuoso5.5-cil from Mono Unhandled Exception: System.TypeInitializationException: The type initializer for 'Sys' threw an exception. ---> System.DllNotFoundException: /usr/lib/../lib/libmono-system-native.so assembly: type: member:(null) at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag() at Interop+Sys..cctor () [0x0] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 --- End of inner exception stack trace --- at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath, System.Int32 fileType, Interop+ErrorInfo& errorInfo) [0xf] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath) [0x6] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.File.Exists (System.String path) [0x00058] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at Mono.Tools.Driver.LoadConfig (System.Boolean quiet) [0x00031] in <3a4d36ecef0a47439a72108fe400486f>:0 at Mono.Tools.Driver.Main (System.String[] args) [0x00347] in <3a4d36ecef0a47439a72108fe400486f>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'Sys' threw an exception. ---> System.DllNotFoundException: /usr/lib/../lib/libmono-system-native.so assembly: type: member:(null) at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag() at Interop+Sys..cctor () [0x0] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 --- End of inner exception stack trace --- at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath, System.Int32 fileType, Interop+ErrorInfo& errorInfo) [0xf] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath) [0x6] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.File.Exists (System.String path) [0x00058] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at Mono.Tools.Driver.LoadConfig (System.Boolean quiet) [0x00031] in <3a4d36ecef0a47439a72108fe400486f>:0 at Mono.Tools.Driver.Main (System.String[] args) [0x00347] in <3a4d36ecef0a47439a72108fe400486f>:0 W: removing assembly: OpenLink.Data.Virtuoso, Version=6.2.3128.1, Culture=neutral, PublicKeyToken=6654f6917d07cb95 failed! Unpacking libvirtuoso5.5-cil (7.2.5.1+dfsg-3) over (6.1.6+dfsg2-4+b2) ... Setting up libexpat1:amd64 (2.2.10-2) ... Setting up libpixman-1-0:amd64 (0.40.0-1) ... Setting up libxau6:amd64 (1:1.0.9-1) ... Setting up libxcb1:amd64 (1.14-3) ... Setting up libxcb-render0:amd64 (1.14-3) ... Setting up libglib2.0-0:amd64 (2.66.8-1) ... No schema files found: doing nothing. Setting up libvirtuoso5.5-cil (7.2.5.1+dfsg-3) ... * Installing 1 assembly from libvirtuoso5.5-cil into Mono Unhandled Exception: System.TypeInitializationException: The type initializer for 'Sys' threw an exception. ---> System.DllNotFoundException: /usr/lib/../lib/libmono-system-native.so assembly: type: member:(null) at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag() at Interop+Sys..cctor () [0x0] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 --- End of inner exception stack trace --- at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath, System.Int32 fileType, Interop+ErrorInfo& errorInfo) [0xf] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath) [0x6] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.File.Exists (System.String path) [0x00058] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at
Bug#986275: marked as done (libglib3.0-cil: fails to upgrade from buster: The type initializer for 'Sys' threw an exception.)
Your message dated Tue, 29 Jun 2021 14:10:15 + with message-id and subject line Bug#986275: fixed in mono 6.8.0.105+dfsg-3.1 has caused the Debian Bug report #986275, regarding libglib3.0-cil: fails to upgrade from buster: The type initializer for 'Sys' threw an exception. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 986275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libglib3.0-cil Version: 2.99.3-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libpango3.0-cil Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. >From the attached log (scroll to the bottom...): Setting up libglib3.0-cil (2.99.3-4) ... * Installing 1 assembly from libglib3.0-cil into Mono Unhandled Exception: System.TypeInitializationException: The type initializer for 'Sys' threw an exception. ---> System.DllNotFoundException: /usr/lib/../lib/libmono-system-native.so assembly: type: member:(null) at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag() at Interop+Sys..cctor () [0x0] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 --- End of inner exception stack trace --- at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath, System.Int32 fileType, Interop+ErrorInfo& errorInfo) [0xf] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath) [0x6] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.File.Exists (System.String path) [0x00058] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at Mono.Tools.Driver.LoadConfig (System.Boolean quiet) [0x00031] in <3a4d36ecef0a47439a72108fe400486f>:0 at Mono.Tools.Driver.Main (System.String[] args) [0x00347] in <3a4d36ecef0a47439a72108fe400486f>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'Sys' threw an exception. ---> System.DllNotFoundException: /usr/lib/../lib/libmono-system-native.so assembly: type: member:(null) at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag() at Interop+Sys..cctor () [0x0] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 --- End of inner exception stack trace --- at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath, System.Int32 fileType, Interop+ErrorInfo& errorInfo) [0xf] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath) [0x6] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.File.Exists (System.String path) [0x00058] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at Mono.Tools.Driver.LoadConfig (System.Boolean quiet) [0x00031] in <3a4d36ecef0a47439a72108fe400486f>:0 at Mono.Tools.Driver.Main (System.String[] args) [0x00347] in <3a4d36ecef0a47439a72108fe400486f>:0 E: installing Assembly /usr/lib/cli/glib-sharp-3.0/glib-sharp.dll failed E: Installation of libglib3.0-cil with /usr/share/cli-common/runtimes.d/mono failed dpkg: error processing package libglib3.0-cil (--configure): installed libglib3.0-cil package post-installation script subprocess returned error exit status 29 Setting up libcairo1.10-cil (2.99.3-4) ... * Installing 1 assembly from libcairo1.10-cil into Mono Unhandled Exception: System.TypeInitializationException: The type initializer for 'Sys' threw an exception. ---> System.DllNotFoundException: /usr/lib/../lib/libmono-system-native.so assembly: type: member:(null) at (wrapper managed-to-native) Interop+Sys.LChflagsCanSetHiddenFlag() at Interop+Sys..cctor () [0x0] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 --- End of inner exception stack trace --- at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath, System.Int32 fileType, Interop+ErrorInfo& errorInfo) [0xf] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.FileSystem.FileExists (System.ReadOnlySpan`1[T] fullPath) [0x6] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at System.IO.File.Exists (System.String path) [0x00058] in <12b418a7818c4ca0893feeaaf67f1e7f>:0 at Mono.Tools.Driver.LoadConfig (System.Boolean quiet) [0x00031] in <3a4d36ecef0a47439a72108fe400486f>:0 at Mono.Tools.Driver.Main (System.String[] args) [0x00347] in <3a4d36ecef0a47439a72108fe400486f>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The
Bug#985066: marked as done (mono-gac: messes with the unpacking of another package)
Your message dated Tue, 29 Jun 2021 14:10:15 + with message-id and subject line Bug#985066: fixed in mono 6.8.0.105+dfsg-3.1 has caused the Debian Bug report #985066, regarding mono-gac: messes with the unpacking of another package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mono-runtime-common,dpkg Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 6.8.0.105+dfsg-3 Control: found -1 1.20.7.1 Hi, during a test with piuparts I noticed your package modifies conffiles. Or rather, it appears so. piuparts reports: 0m48.5s ERROR: FAIL: debsums reports modifications inside the chroot: /etc/mono/config I don't see something obviously wrong in the package: mono-runtime-common 5.18.0.240+dfsg-3 (buster) ships # ls -la /etc/mono/config -rw-r--r-- 1 root root 2890 Apr 16 2019 /etc/mono/config # md5sum /etc/mono/config dc9d7e7fbd83e76c7c7956f392a6ee6f /etc/mono/config # dpkg -s mono-runtime-common | grep /etc/mono/config /etc/mono/config dc9d7e7fbd83e76c7c7956f392a6ee6f mono-runtime-common 6.8.0.105+dfsg-3 (bullseye/sid) ships # ls -la /etc/mono/config -rw-r--r-- 1 root root 3093 Apr 8 2020 /etc/mono/config # md5sum /etc/mono/config 267499e20c8acc00b7e01596bec6adba /etc/mono/config # dpkg -s mono-runtime-common | grep /etc/mono/config /etc/mono/config newconffile That's a weird entry in dpkg's status file There is no report about updating the conffile during the upgrade: [...] Preparing to unpack .../18-mono-runtime-common_6.8.0.105+dfsg-3_amd64.deb ... Unpacking mono-runtime-common (6.8.0.105+dfsg-3) over (5.18.0.240+dfsg-3) ... [...] Setting up mono-runtime-common (6.8.0.105+dfsg-3) ... Processing triggers for libc-bin (2.31-9) ... [...] and in the chroot I find this after the upgrade: # ls -la /etc/mono/config* -rw-r--r-- 1 root root 3093 Apr 8 2020 /etc/mono/config # md5sum /etc/mono/config 267499e20c8acc00b7e01596bec6adba /etc/mono/config # dpkg -s mono-runtime-common | grep /etc/mono/config /etc/mono/config dc9d7e7fbd83e76c7c7956f392a6ee6f So the new file is there, but dpkg still remembers the old md5sum. Andreas mono-runtime-common.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: mono Source-Version: 6.8.0.105+dfsg-3.1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of mono, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 985...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated mono package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Jun 2021 12:07:42 +0200 Source: mono Binary: ca-certificates-mono libmono-accessibility4.0-cil libmono-cairo4.0-cil libmono-cecil-private-cil libmono-cil-dev libmono-codecontracts4.0-cil libmono-compilerservices-symbolwriter4.0-cil libmono-corlib4.5-cil libmono-corlib4.5-dll libmono-cscompmgd0.0-cil libmono-csharp4.0c-cil libmono-custommarshalers4.0-cil libmono-data-tds4.0-cil libmono-db2-1.0-cil libmono-debugger-soft4.0a-cil libmono-http4.0-cil libmono-i18n-cjk4.0-cil libmono-i18n-mideast4.0-cil libmono-i18n-other4.0-cil libmono-i18n-rare4.0-cil libmono-i18n-west4.0-cil libmono-i18n4.0-all libmono-i18n4.0-cil libmono-ldap4.0-cil libmono-management4.0-cil libmono-messaging-rabbitmq4.0-cil libmono-messaging4.0-cil libmono-microsoft-build-engine4.0-cil libmono-microsoft-build-framework4.0-cil libmono-microsoft-build-tasks-v4.0-4.0-cil libmono-microsoft-build-utilities-v4.0-4.0-cil libmono-microsoft-build4.0-cil libmono-microsoft-csharp4.0-cil libmono-microsoft-visualc10.0-cil libmono-microsoft-web-infrastructure1.0-cil libmono-oracle4.0-cil libmono-parallel4.0-cil libmono-peapi4.0a-cil libmono-posix4.0-cil libmono-rabbitmq4.0-cil libmono-relaxng4.0-cil libmono-security4.0-cil libmono-sharpzip4.84-cil libmono-simd4.0-cil libmono-smdiagnostics0.0-cil libmono-sqlite4.0-cil libmono-system-componentmodel-composition4.0-cil
Processed: closing 982991
Processing commands for cont...@bugs.debian.org: > close 982991 Bug #982991 [src:matrix-synapse] matrix-synapse: not suitable for inclusion into bullseye Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 982991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986293: closed by Debian FTP Masters (reply to Adrian Bunk ) (Bug#986293: fixed in virtuoso-opensource 7.2.5.1+dfsg-3.1)
On 23/05/2021 16.21, Debian Bug Tracking System wrote: > virtuoso-opensource (7.2.5.1+dfsg-3.1) unstable; urgency=medium > * Drop the libvirtuoso5.5-cil package. (Closes: #986293) > * Updated debconf translations: I've just reintroduced the -cil package (avoiding NEW since it was still as cruft in sid) since the upgrade error was actually caused by the mono dependency cycle. (mono fix is in experimental/NEW and RT approved) Do you want to get the translation updates unbocked? On 01/05/2021 17.14, Adrian Bunk wrote: > In any case there is a bug that libvirtuoso5.5-cil lost all dependencies > except cli-common in bullseye. I haven't looked at that. Do you want to file a new bug for it? (#986293 has been reassigned to mono) Andreas
Processed: tagging 982121
Processing commands for cont...@bugs.debian.org: > tags 982121 + pending Bug #982121 [src:python-django-analytical] python-django-analytical: autopkgtest failure Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 982121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982121 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990344: exim 4.94.2 update default configuration option breaks MTA
Hello: Thank you for taking the time to write. > ... exim packages do not change/edit the file, if it was changed > then manually. Right. The userland cannot change it, it's only through *manual* edition. Now I'm *sure* I didn't change anything. I had never seen the insides of an exim config file till I had this problem. > > ... related to (at least one) of the settings that need to be > > changed for the exim4 configuration to be compatible > > with exim 4.94.2. > Sounds reasonable, yes. I thought as much also. > If you are not sure what you did change ... No. What I wrote was that I did not remember *ever* changing anything. But that I was *not absolutely certain* of not having done it. Not the same thing. I any case, it is a moot point. ie: it has no relevance with respect to the case I have been attempting to make which is this: Whether *any* of the configuration files were changed or not, a basic fact (which you find attendable/reasonable) remains: *Any* configuration file belonging to a version *previous* to exim 4.94.2, modified or not, will effectively break exim 4.94.2. eg: any configuration file containing *$local_part* instead of *$local_part_data*. If the dpkg installer considers no config file have been modified, it will overwrite then and everything will be allright. But ... If (for whatever reason) the dpkg installer considers some config file has been modified, it will recommend a default option that will break the MTA. If I may suggest: It would make a lot more sense (and would have saved me a lot of grief) if the exim 4.94.2 installer would have popped up something like this: - WARNING All exim versions prior to version 4.94.2 are now obsolete. As a result, *all* existing configurations set up with versions prior to exim 4.94.2 will effectively break this installation. The exim installation being updated is prior to exim version 4.94.2. It is emphatically recommended that you do not keep the present configuration. What do you want to do? 1. Replace the present configuration (recommended default) 2. Keep the present configuration 3. Open a terminal and compare the configuration files Thanks for your input.
Bug#989346: marked as done (python3-setuptools: .exe files in .deb file)
Your message dated Tue, 29 Jun 2021 11:19:34 + with message-id and subject line Bug#989346: fixed in setuptools 52.0.0-4 has caused the Debian Bug report #989346, regarding python3-setuptools: .exe files in .deb file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 989346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-setuptools Version: 52.0.0-3 Severity: serious Justification: Policy 4.16 Tags: upstream Dear Maintainer, python3-setuptools is installing some weird .exe files. find /usr/ -name '*exe' /usr/lib/python3/dist-packages/setuptools/gui-64.exe /usr/lib/python3/dist-packages/setuptools/gui.exe /usr/lib/python3/dist-packages/setuptools/gui-32.exe /usr/lib/python3/dist-packages/setuptools/cli-64.exe /usr/lib/python3/dist-packages/setuptools/cli.exe /usr/lib/python3/dist-packages/setuptools/cli-32.exe You have a lintian override to silence the warning: # Source is included for these files, they can be built in Debian with the # mingw toolchain, and the are not shipped in the binary, so this is OK for # Debian. It is not worth repacking the tarball just for this. The lintian override suggests that the files are not included in the binary, which is false, so I guess you are not aware of their presence. I think easy fix to remove them from the binary. Best -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8), LANGUAGE=it Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-setuptools depends on: ii python33.9.2-3 ii python3-distutils 3.9.2-1 ii python3-pkg-resources 52.0.0-3 python3-setuptools recommends no packages. Versions of packages python3-setuptools suggests: pn python-setuptools-doc -- no debconf information --- End Message --- --- Begin Message --- Source: setuptools Source-Version: 52.0.0-4 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of setuptools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 989...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated setuptools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Jun 2021 12:58:50 +0200 Source: setuptools Architecture: source Version: 52.0.0-4 Distribution: unstable Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 989346 Changes: setuptools (52.0.0-4) unstable; urgency=medium . * Don't include the exe installer files in the binary package, not rebuilt using the mingw64 toolchain. Closes: #989346. Checksums-Sha1: 6042969cf6d4b9b4c15530520b9f05beb5cf8ade 2078 setuptools_52.0.0-4.dsc a4b5ac430dcf46aa4538718d30cce6d91ddb 13260 setuptools_52.0.0-4.debian.tar.xz 706704c38f8200bbc4dd29f36c2849bf6b28048b 7702 setuptools_52.0.0-4_source.buildinfo Checksums-Sha256: 86c2c004ebe122288e331b2faf5a562d56a99fedc5a52c0d295f2ea5ffa6 2078 setuptools_52.0.0-4.dsc 5f8a3f198fce1de638be11ddfb3b582b6fbd1b105ab0041fb74ebc77e4939cc5 13260 setuptools_52.0.0-4.debian.tar.xz ca86a5980df528068b80995783c336cc20a49e347d468f96d481eaa617ece629 7702 setuptools_52.0.0-4_source.buildinfo Files: 029a9d00fd875e9aad81a70ea260f8be 2078 python optional setuptools_52.0.0-4.dsc 0072c6f15f15b190b0afac05f8aa8b5b 13260 python optional setuptools_52.0.0-4.debian.tar.xz 6092583763d2b14e2d8c8b454ee7f29e 7702 python optional setuptools_52.0.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmDa/TYQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9UcJEACGLKZ/a0xvbHp+QFa9aPvslnuMBSS3CT5z WWKNA2PZjYiCvMMibtrgHKy46tNzjz6xfTTxF6XCrT+1JuRPYmDbE2bvdQvyJBPF NN8Z++M25KrNnf/NkpWvvlQh5muUn+8JRxUTdpyopRoUmQowDZFnfRhrX6lGOX7l
Bug#989346: marked as done (python3-setuptools: .exe files in .deb file)
Your message dated Tue, 29 Jun 2021 11:19:40 + with message-id and subject line Bug#989346: fixed in setuptools 57.0.0-1 has caused the Debian Bug report #989346, regarding python3-setuptools: .exe files in .deb file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 989346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-setuptools Version: 52.0.0-3 Severity: serious Justification: Policy 4.16 Tags: upstream Dear Maintainer, python3-setuptools is installing some weird .exe files. find /usr/ -name '*exe' /usr/lib/python3/dist-packages/setuptools/gui-64.exe /usr/lib/python3/dist-packages/setuptools/gui.exe /usr/lib/python3/dist-packages/setuptools/gui-32.exe /usr/lib/python3/dist-packages/setuptools/cli-64.exe /usr/lib/python3/dist-packages/setuptools/cli.exe /usr/lib/python3/dist-packages/setuptools/cli-32.exe You have a lintian override to silence the warning: # Source is included for these files, they can be built in Debian with the # mingw toolchain, and the are not shipped in the binary, so this is OK for # Debian. It is not worth repacking the tarball just for this. The lintian override suggests that the files are not included in the binary, which is false, so I guess you are not aware of their presence. I think easy fix to remove them from the binary. Best -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8), LANGUAGE=it Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-setuptools depends on: ii python33.9.2-3 ii python3-distutils 3.9.2-1 ii python3-pkg-resources 52.0.0-3 python3-setuptools recommends no packages. Versions of packages python3-setuptools suggests: pn python-setuptools-doc -- no debconf information --- End Message --- --- Begin Message --- Source: setuptools Source-Version: 57.0.0-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of setuptools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 989...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated setuptools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Jun 2021 12:38:01 +0200 Source: setuptools Architecture: source Version: 57.0.0-1 Distribution: experimental Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 989346 Changes: setuptools (57.0.0-1) experimental; urgency=medium . * New upstream version. * Build the docs without the towncrier sphinx extension for now. * Don't include the exe installer files in the binary package, not rebuilt using the mingw64 toolchain. Closes: #989346. Checksums-Sha1: 70f2a4ff1f6bb01f5fa1dd4b891b9f9e39d0ac9b 2078 setuptools_57.0.0-1.dsc dfcfa1bd90285c64878150e01a551f7f97e3ebc6 2144749 setuptools_57.0.0.orig.tar.gz b400c2b077f8f835c553780f60ae2ee031786eea 13568 setuptools_57.0.0-1.debian.tar.xz 1086b418ac087afea31941a55fdbc07fa28a464b 7702 setuptools_57.0.0-1_source.buildinfo Checksums-Sha256: c105f0c2646f0c543ff62c72c5fb36cf7a5b41303b73f4c516744cdb0e492046 2078 setuptools_57.0.0-1.dsc 401cbf33a7bf817d08014d51560fc003b895c4cdc1a5b521ad2969e928a07535 2144749 setuptools_57.0.0.orig.tar.gz 79878f39a8c6d0791904dd5b68bedf1ae43413f285ff84388ccc8b5cc5f91ec9 13568 setuptools_57.0.0-1.debian.tar.xz a26ad341d16f8aa2c24875fb6c56e746920079d1966cc0e1b1a67865cbf3beef 7702 setuptools_57.0.0-1_source.buildinfo Files: aba63d2a56bcd6250a6bb3b85ee2bcb8 2078 python optional setuptools_57.0.0-1.dsc 60ae3b43cd2ced1385f75468d658c5b6 2144749 python optional setuptools_57.0.0.orig.tar.gz 48144fba9b68173806a0c77b10cf 13568 python optional setuptools_57.0.0-1.debian.tar.xz 4a7e097df5addb382a2536e4e98ad16e 7702 python
Bug#990443: origami-pdf: pdfwalker crashes on start: /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError)
Package: origami-pdf Version: 2.0.0-1 Severity: serious pdfwalker crashes on start, even with just no parameter or just "--help": $ pdfwalker Ignoring ffi-1.9.10 because its extensions are not built. Try: gem pristine ffi --version 1.9.10 Ignoring json-1.8.3 because its extensions are not built. Try: gem pristine json --version 1.8.3 Traceback (most recent call last): 26: from /usr/bin/pdfwalker:4:in `' 25: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 24: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 23: from /usr/share/origami/gui/walker.rb:31:in `' 22: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 21: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 20: from /usr/lib/ruby/vendor_ruby/origami.rb:42:in `' 19: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 18: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 17: from /usr/lib/ruby/vendor_ruby/origami/pdf.rb:46:in `' 16: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 15: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 14: from /usr/lib/ruby/vendor_ruby/origami/signature.rb:22:in `' 13: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 12: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 11: from /usr/lib/ruby/2.7.0/openssl.rb:21:in `' 10: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 9: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 8: from /usr/lib/ruby/2.7.0/openssl/ssl.rb:15:in `' 7: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 6: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 5: from /usr/lib/ruby/2.7.0/ipaddr.rb:19:in `' 4: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 3: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 2: from /usr/lib/ruby/2.7.0/socket.rb:3:in `' 1: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': superclass mismatch for class Socket (TypeError) -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages origami-pdf depends on: ii ruby 1:2.7+2 ii ruby-origami 2.0.0-1 Versions of packages origami-pdf recommends: ii ruby-gtk2 3.4.3-1+b1 origami-pdf suggests no packages. -- no debconf information
Processed: Re: Bug#990417: openjdk-11-jre-headless: running java in qemu s390 gives a SIGILL at C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8
Processing control commands: > reassign -1 src:qemu Bug #990417 [openjdk-11-jre-headless] openjdk-11-jre-headless: running java in qemu s390 gives a SIGILL at C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8 Bug reassigned from package 'openjdk-11-jre-headless' to 'src:qemu'. No longer marked as found in versions openjdk-11/11.0.11+9-1~deb10u1. Ignoring request to alter fixed versions of bug #990417 to the same values previously set -- 990417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990417: openjdk-11-jre-headless: running java in qemu s390 gives a SIGILL at C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8
Control: reassign -1 src:qemu works for me on a native machine. You should also provide a test case. On 6/28/21 7:28 PM, Arne Plöse wrote: > Package: openjdk-11-jre-headless > Version: 11.0.11+9-1~deb10u1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I tried tu run java in an qemu emulated s390 debian VM. > The bug accects also unstabel and te openjdk versions 15, 16 and 17, but not > version 1.8 > > The outcome is a hs_err_pid632.log. > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGILL (0x4) at pc=0x03ff88c7e6f4, pid=587, tid=588 > # > # JRE version: (11.0.11+9) (build ) > # Java VM: OpenJDK 64-Bit Server VM (11.0.11+9-post-Debian-1deb10u1, mixed > mode, sharing, tiered, compressed oops, g1 gc, linux-s390x) > # Problematic frame: > # C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8 > # > # No core dump will be written. Core dumps have been disabled. To enable core > dumping, try "ulimit -c unlimited" before starting Java again > # > # > > --- S U M M A R Y > > Command Line: > > Host: 2964, 2 cores, 1G, Debian GNU/Linux 10 (buster) > Time: Mon Jun 28 19:13:29 2021 CEST elapsed time: 0.099756 seconds (0d 0h 0m > 0s) > > --- T H R E A D --- > > Current thread is native thread > > Stack: [0x03ff8748,0x03ff8758], sp=0x03ff8757e940, free > space=1018k > Native frames: (J=compiled Java code, A=aot compiled Java code, > j=interpreted, Vv=VM code, C=native code) > C [linux-vdso64.so.1+0x6f8] __kernel_getcpu+0x8 > > > siginfo: si_signo: 4 (SIGILL), si_code: 5 (ILL_PRVOPC), si_addr: > 0x03ff88c7e6f4 > > > > -- System Information: > Debian Release: 10.10 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: s390x > > Kernel: Linux 4.19.0-17-s390x (SMP w/2 CPU cores) > Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages openjdk-11-jre-headless depends on: > ii ca-certificates-java 20190405 > ii java-common 0.71 > ii libasound21.1.8-1 > ii libc6 2.28-10 > ii libcups2 2.2.10-6+deb10u4 > ii libfontconfig12.13.1-2 > ii libfreetype6 2.9.1-3+deb10u2 > ii libgcc1 1:8.3.0-6 > ii libharfbuzz0b 2.3.1-1 > ii libjpeg62-turbo 1:1.5.2-2+deb10u1 > ii liblcms2-22.9-3 > ii libnss3 2:3.42.1-1+deb10u3 > ii libpcsclite1 1.8.24-1 > ii libstdc++68.3.0-6 > ii util-linux2.33.1-0.1 > ii zlib1g1:1.2.11.dfsg-1 > > openjdk-11-jre-headless recommends no packages. > > Versions of packages openjdk-11-jre-headless suggests: > pn fonts-dejavu-extra > pn fonts-indic > pn fonts-ipafont-gothic > pn fonts-ipafont-mincho > pn fonts-wqy-microhei | fonts-wqy-zenhei > pn libnss-mdns > > -- no debconf information >
Bug#972339: more info
Control: unarchive -1 Hello there, I have gotten more info from good folks at OpenSuse: > We at openSUSE got a similar (perhaps even same?) issue > https://bugzilla.suse.com/show_bug.cgi?id=1187232 > > In the end the root cause there was that the installed > HPLIP plugin did not match the installed HPLIP, see > https://bugzilla.suse.com/show_bug.cgi?id=1187232#c8 > > Perhaps this might also help you with > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972339 > > Even if the openSUSE issue is actually a different one > it may help to know that HPLIP programs seem to blindly > use plugin code and may fail in arbitrary ways if the > plugin code does not fit. -- OdyX signature.asc Description: This is a digitally signed message part.
Processed: unarchiving 972339
Processing commands for cont...@bugs.debian.org:
> unarchive 972339
Bug #972339 {Done: Didier Raboud } [printer-driver-hpcups]
armhf: hpcups crashes with free() invalid pointer for some printers
Unarchived Bug 972339
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
972339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Setting correct fixfoxed version for q3c
Processing commands for cont...@bugs.debian.org:
> fixed 989732 2.0.0-5
Bug #989732 {Done: Ole Streicher } [postgresql-13-q3c]
postgresql-13-pgsphere: drop Conflicts+Replaces: postgresql-pgsphere
Marked as fixed in versions postgresql-q3c/2.0.0-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
989732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
