Package: mailutils-pop3d
Version: 1:3.17-1
Severity: important
Dear Maintainer,
Since a few months ago (latest 2023-09), without making any configuration
changes, my pop3d localhost service has failed to come online. The direct
reason is that systemd kills it, but I don't know why, especially
Package: fwknop-server
Version: 2.6.10-18
Severity: serious
Tags: patch security
Justification: Policy 7.2
X-Debbugs-Cc: Debian Security Team
Dear Maintainer,
The latest update breaks apparmor for the whole system.
/etc/apparmor.d/usr.sbin.fwknopd:
include
This must declare Depends:
Package: libqt6gui6
Version: 6.4.2+dfsg-18
Severity: important
Tags: patch
Dear Maintainer,
When running:
https://github.com/ankitects/anki/releases/download/2.1.66/anki-2.1.66-linux-qt6.tar.zst
I get the following error:
| anki-2.1.66-linux-qt6$ QT_DEBUG_PLUGINS=1 DISABLE_QT5_COMPAT=1 ./anki
Package: exim4-config
Version: 4.96-16
Severity: normal
Tags: patch
Dear Maintainer,
Even when dc_hide_mailname is set, mails sent to remote hosts leak the local
intranet hostname. This is because of two reasons, which the below patch fixes.
1. Reason #1 is the Received: header added by exim4
Package: mesa-opencl-icd
Version: 22.0.5-1
Severity: important
Dear Maintainer,
mesa-opencl-icd depends on both libllvm14 and libclc-13
The latter should be upgraded to libclc-14
Versions of packages mesa-opencl-icd depends on:
ii libc62.33-7
ii libclang-cpp14
Control: forcemerge 943859 -1
Control: notfound -1 1.59.0+dfsg1-1
Not a bug, see #943859
Pirate Praveen:
> Package: rustc
> Version: 1.59.0+dfsg1-1
> Severity: serious
> Justification: ships broken symbolic link to rustc-lld
>
>
> $ ls -l /usr/bin/rust-lld
> lrwxrwxrwx 1 root root 6 മേയ് 11
Source: llvm-toolchain-13
Version: 1:13.0.1-3
Severity: normal
Tags: patch upstream
Control: affects + rustc
Dear Maintainer,
Please backport upstream https://reviews.llvm.org/D115098
It is needed for rust 1.59, otherwise a certain test fails on all architectures.
Thanks,
X
-- System
Is your issue simply this? https://github.com/rust-lang/cargo/issues/7769
If so please close this bug as invalid, since it is not debcargo's
responsibility.
X
Daniel Kahn Gillmor:
> Control: affects 1001251 + src:rust-sequoia-openpgp
>
> On Tue 2021-12-07 03:47:32 +0400, Daniel Kahn Gillmor
Package: ftp.debian.org
Severity: normal
Hi, please remove this package on all architectures. It is an old rust library
with a security bug and no reverse dependencies.
(uninstallable, bd-uninstallable, blah blah blah) do not add extra value, in
fact they reduce value by forcing us to close bug reports.
Best,
Ximin
Ximin Luo:
> Due to the nature of the Rust upstream ecosystem, bugs like this are expected
> from time to time as we update dependent
Due to the nature of the Rust upstream ecosystem, bugs like this are expected
from time to time as we update dependent crates.
A reversion in terms of downgrading the version using +really-like schemes is
not feasible at the current time, see
Source: rust-bindgen
Followup-For: Bug #998347
That is not how rust Debian packaging works; your patch will get lost with the
next upload of the autogenerated package.
If you want your patch to not get lost, do it via the normal process:
https://salsa.debian.org/rust-team/debcargo-conf/
--
Source: rust-quickcheck
Followup-For: Bug #998345
Control: close -1
> Correction: It is the binary package librust-quickcheck+env-logger-dev
> which depends on librust-env-logger-0.7-dev.
env-logger-0.7 is sitting in NEW. There is no action to take on this package,
therefore closing.
--
Source: rust-quickcheck
Followup-For: Bug #998345
Control: notfound -1 0.9.2-1
Control: close -1
Not sure how you came to this conclusion.
Package: librust-rand+std-dev
Provides:
librust-rand-0.7+default-dev (= ${binary:Version}),
$ sudo aptitude install librust-quickcheck-dev
[sudo] password
Bastian Germann:
>> In fact there is nowhere in the d/copyright file format to put this
>> information; and it would not be efficient to do so since the information
>> already exists in the d/copyright of those other packages.
>
> Maybe there is nowhere in the DEP-5 format, which is not
Source: rust-lalrpop
Followup-For: Bug #995339
The d/copyright file is about the source package not the binary package, you
are misinterpreting policy.
In fact there is nowhere in the d/copyright file format to put this
information; and it would not be efficient to do so since the information
plugwash:
> package: dh-cargo
>
> Recently a substantial number of upstream cargo packages started using
> timestamps the ftpmasters
> consider reject-worthy, I believe this was done in the name of
> reproducibility.
>
On what basis are you forming your belief? Because I worked on
Package: omnidb-server
Version: 3.0.3b+ds-2
Severity: important
Dear Maintainer,
Despite advertising MariaDB support in the package description, this package
does
not actually support it:
Traceback (most recent call last):
File
Hi,
Note it's already possible to cross-compile to other linux libc platforms, just
dpkg --add-architecture $foreign then apt-get install libstd-rust-dev:$foreign.
Yes the *only* thing you have to do is package the libstd. I am unlikely to
have time for the other platforms you mentioned but am
Package: initscripts
Version: 2.96-7
Severity: important
Tags: patch
Dear Maintainer,
Single-user mode is broken with newer versions of systemd which do not support
the -t option:
$ /sbin/init -t1
/sbin/init: invalid option -- 't'
exit code 1
This however is still used in /etc/init.d/single:
Thanks for the update.
Is there much point supporting rust emscripten at all? Apart from this
C-linking thing that is now apparently fixed, what is the actual advantage (or
even, point) of it?
>From what I understand from [1] it seems that emscripten does for C what
>wasm32-wasi and/or
directly.
Best,
Ximin
Ximin Luo:
> Source: llvm-toolchain-12
> Version: 1:12.0.0-3
> Severity: important
> X-Debbugs-Cc: debian-m...@lists.debian.org, debian-r...@lists.debian.org
>
> Dear Maintainer,
>
> LLVM 12's ability to emit IR in human-readable form is corrupted on mips
Source: llvm-toolchain-12
Version: 1:12.0.0-3
Severity: important
X-Debbugs-Cc: debian-m...@lists.debian.org, debian-r...@lists.debian.org
Dear Maintainer,
LLVM 12's ability to emit IR in human-readable form is corrupted on mipsel
32-bit:
$ cat main.c
#include
int main() {
char *a = NULL;
Control: notfound -1 1.48.0+dfsg1-2
Control: notfound -1 1.49.0~beta.4+dfsg1-1~exp1
Control: close -1
Duplicate of archived #943859 and explained in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943859#10
The clang symlink is for libstd-rust-dev-windows:*.
X
Andreas Beckmann:
> Package:
It looks like these CVEs affect all versions up to 1.52 (which is not yet
released).
Do you have links to patches fixing these bugs that can be backported to 1.48?
We've had 1.48 for a while due to the migration freeze, and I've been informed
that some rust packages in Debian break with newer
Stephen Kitt:
> On Thu, 8 Apr 2021 13:11:46 +0100, Ximin Luo wrote:
>>> On Thu, 08 Apr 2021 01:35:49 +0100, Ximin Luo
>>> wrote:
>>>> Please mark gcc-mingw-w64-base "Multi-Arch: same" so that different
>>>> architectures can be co-ins
Stephen Kitt:
> Hi,
>
> On Thu, 08 Apr 2021 01:35:49 +0100, Ximin Luo wrote:
>> Please mark gcc-mingw-w64-base "Multi-Arch: same" so that different
>> architectures can be co-installed. This is necessary to support
>> co-installing the i686 and x86-64 too
Package: nodejs
Version: 12.21.0~dfsg-1
Severity: wishlist
Tags: patch
Dear Maintainer,
Please include the attached script, installing it into /usr/bin/wasi-node.
This is a script that acts as an interpreter for WASI programs, by using
NodeJS's
experimental WASI module API. You can compile
Package: gcc-mingw-w64-base
Version: 10.2.1-6+24.1
Severity: normal
Tags: patch
Dear Maintainer,
Please mark gcc-mingw-w64-base "Multi-Arch: same" so that different
architectures
can be co-installed. This is necessary to support co-installing the i686 and
x86-64 toolchain packages, both of
Package: wine-development
Version: 5.6-1
Severity: minor
Tags: patch
Dear Maintainer,
debian/patches/warnings/array-bounds.patch defines its own CFLAGS, but this
clobbers those from e.g. dpkg-buildflags.
+CFLAGS= -Wno-array-bounds
Changing = to += will fix this.
+CFLAGS+=
m, only, as you note,
> checking via X509 root CAs. If people want to use that (and package it), of
> course.
>
> Matt
>
> On 3/26/21 10:19, Ximin Luo wrote:
>> Not sure what your purpose is with your comment. Nobody is asking you to
>> package it. If somebody else
tc (eg cross-language LTO, LLVM plugins,
> etc).
>
> Matt
>
> On Sat, 4 Apr 2020 01:19:59 +0100 Ximin Luo wrote:
>> Hi all,
>>
>> I agree that rustup should be in Debian. Achieving this is currently blocked
>> on either of these two issues:
>>
These packages are not installed by users, so leaving them as FTBFS is not a
big deal. If you want to clean it up, please feel free. I can certainly
understand if people (e.g. me) want to spend their time doing other things.
X
Santiago Vila:
> On Sun, 8 Sep 2019, Ximin Luo wr
).
However I don't see that it could cause any harm, it makes something that is
broken work again - could you please apply it in the Debian package?
Best,
Ximin
Ximin Luo:
> Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/3946
>
> Timo Aaltonen:
>> [..]
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/3946
Timo Aaltonen:
> [..]
>>
>> Despite the presence of CLOVER_DEBUG=llvm,native CLOVER_DEBUG_FILE=dump-file
>> there were
>> no dump-files dumped by the above leelaz command, maybe you can deduce
>> something from that.
debcargo (and cargo) is out of date in Debian and needs to be updated. We had
been blocked on the FTP binary-NEW policy but there is some progress in that
area.
Alternatively you could use collapse_features to begin to update it, but I
personally do not approve of it and haven't been spending
Package: lintian
Version: 2.104.0
Severity: important
Dear Maintainer,
for cargo 0.47.0 lintian is given nonsensical output like:
W: cargo source: debian-adds-quilt-control-dir vendor/unicode-width/.pc/
W: cargo source: file-without-copyright-information
Control: block -1 by 971571
Control: tags -1 + pending
Hi Lyndon
Do you know about Debian experimental? cargo 0.47 has been in there for a few
months.
We are waiting on the libgit2 transition before we can upload it to unstable.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971571
X
Ximin Luo:
> [..]
>
> 4. Finally run clinfo(1) with the right LD_LIBRARY_PATH to check that it
> worked.
>You should get something like:
>
>
>$ LD_LIBRARY_PATH=/opt/amdgpu-pro/lib/x86_64-linux-gnu/ clinfo -l
>Platform #0: AMD Accelerated Parallel
Package: ocl-icd-libopencl1
Version: 2.2.13-1
Severity: important
Dear Maintainer,
Currently Debian does not have a working OpenCL library for a lot of AMD
graphics
drivers - mesa-opencl-icd does not work or often breaks; and ROCm is not yet
packaged in Debian.
The AMDGPU PRO OpenCL drivers
Package: julia
Version: 1.5.3+dfsg-2
Followup-For: Bug #971570
Control: severity -1 serious
Dear Maintainer,
It has been several weeks since filing this and we want to proceed with the
transition. Therefore I am bumping this bug to RC severity. If no action is
taken it will be removed from
Package: geany-plugins
Version: 1.37+dfsg-3
Followup-For: Bug #971568
Control: severity -1 serious
Dear Maintainer,
It has been several weeks since filing this and we want to proceed with the
transition. Therefore I am bumping this bug to RC severity. If no action is
taken it will be removed
Source: libgit2-glib
Followup-For: Bug #971563
Control: severity -1 serious
Dear Maintainer,
It has been several weeks since filing this and we want to proceed with the
transition. Therefore I am bumping this bug to RC severity. If no action is
taken it will be removed from Debian Testing within
Package: ruby-rugged
Followup-For: Bug #971565
Control: severity -1 serious
Dear Maintainer,
It has been several weeks since filing this and we want to proceed with the
transition. Therefore I am bumping this bug to RC severity. If no action is
taken it will be removed from Debian Testing within
Source: python-pygit2
Followup-For: Bug #971564
Control: severity -1 serious
Dear Maintainer,
It has been several weeks since filing this and we want to proceed with the
transition. Therefore I am bumping this bug to RC severity. If no action is
taken it will be removed from Debian Testing
Source: gall
Followup-For: Bug #971562
Control: severity -1 serious
Dear Maintainer,
It has been several weeks since filing this and we want to proceed with the
transition. Therefore I am bumping this bug to RC severity. If no action is
taken it will be removed from Debian Testing within several
Package: diffoscope
Version: 161
Severity: important
File: diffoscope
Dear Maintainer,
The size of diffoscope is getting really quite ridiculous, all the recommends
now come to ~2.6 GB installed size, even though they are not used in the vast
majority of use cases. Not only is the disk space
://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.en.html#supplementing-changelogs-with-news-debian-files
Best,
Ximin
Stephen Kitt:
> Hi Ximin,
>
> On Sun, 9 Aug 2020 03:08:39 +0100, Ximin Luo wrote:
>> I am the maintainer of rustc in Debian. I am trying to p
debcargo in unstable is out-of-date because cargo is out-of-date, because of
the NEW queue issues. I will get around to fixing it once the libgit2
transition is done (#971571). In the meantime I suggest you build it the
non-Debian way via "cargo build" or just "cargo install debcargo".
X
Source: ktexteditor
Version: 5.70.1-1
Severity: important
Tags: upstream
Dear Maintainer,
libgit2 1.0 is now available in experimental. Please make sure your
package is ready for this version by the time we upload this package to
unstable in one to two weeks. The severity of this report will
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Control: block -1 by 971562 971563 971564 971565 971566 971567 971568 971569
971570
Hello release team!
I'd like to request a transition slot for libgit2.
libgit2 1.0.0 is in
Package: julia
Version: 1.4.1+dfsg-1
Severity: important
Tags: upstream
Dear Maintainer,
libgit2 1.0 is now available in experimental. Please make sure your
package is ready for this version by the time we upload this package to
unstable in one to two weeks. The severity of this report will be
Steve Langasek:
> Ximin,
>
> On Tue, Sep 08, 2020 at 09:23:49PM +0100, Ximin Luo wrote:
>> You keep filing these same bugs. I have told you this many times before
>> already: this is just how rust packaging works, Britney's migration policy
>> already prevents these pa
Package: geany-plugins
Version: 1.36+dfsg-1.1
Severity: important
Tags: upstream
Dear Maintainer,
libgit2 1.0 is now available in experimental, however geany-plugins FTBFS
against it.
Sample error:
In file included from /usr/include/git2.h:69,
from gcb-plugin.c:29:
Package: libgit-raw-perl
Version: 0.79-7
Severity: important
Tags: upstream
Dear Maintainer,
libgit2 1.0 is now available in experimental. Please make sure your
package is ready for this version by the time we upload this package to
unstable in one to two weeks. The severity of this report will
Package: kup-backup
Version: 0.7.3+dfsg-1
Severity: important
Tags: patch upstream
Dear Maintainer,
libgit2 1.0 is now available in experimental. I have built kup-backup against
it, it needs the attached patch to work. Please forward it upstream and also
apply it in this Debian package.
The
Package: ruby-rugged
Version: 0.28.4.1+ds-1
Severity: important
Tags: upstream
Dear Maintainer,
libgit2 1.0 is now available in experimental. Please make sure your
package is ready for this version by the time we upload this package to
unstable in one to two weeks. The severity of this report
Source: python-pygit2
Version: 1.0.3-1
Severity: important
Tags: upstream
Dear Maintainer,
libgit2 1.0 is now available in experimental. Please make sure your
package is ready for this version by the time we upload this package to
unstable in one to two weeks. The severity of this report will be
Source: gall
Version: 1.3-1
Severity: important
Tags: upstream
Dear Maintainer,
libgit2 1.0 is now available in experimental. Please make sure your
package is ready for this version by the time we upload this package to
unstable in one to two weeks. The severity of this report will be raised
Source: libgit2-glib
Version: 0.28.0.1-2
Severity: important
Dear Maintainer,
libgit2 1.0 is now available in experimental. Please make sure your
package is ready for this version by the time we upload this package to
unstable in one to two weeks. The severity of this report will be raised
to
Steve,
You keep filing these same bugs. I have told you this many times before
already: this is just how rust packaging works, Britney's migration policy
already prevents these packages from reaching Debian Testing, so there is no
problem, no users are affected.
You filing these bug reports
Package: lintian
Version: 2.89.0
Severity: normal
Dear Maintainer,
W: wasi-libc source: globbing-patterns-out-of-order
libc-top-half/musl/arch/*/bits/* libc-top-half/musl/arch/mips64/*
but this is fine.
X
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy:
This is most likely an upstream issue - other architectures are fine, and we
don't carry any (significant) ppc64el-specific patches in Debian.
You can also try with 1.46.0 which I'm about to upload (and is already in
experimental).
Best,
Ximin
Mike Hommey:
> Source: rustc
> Version:
Control: reassign -1 cargo-doc
Control: forcemerge 969210 -1
In fact the link would be correct, however the underlying problem is that the
cargo documentation is currently not being built:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934938
I don't have time to fix it, but I describe the
Package: radicale
Version: 2.1.11-8
Severity: important
Dear Maintainer,
radicale requires the python3-passlib module to use bcrypt encryption (htpasswd
-B),
which is the standard secure way of hashing passwords. Otherwise, the service
fails
with:
ERROR: An exception occurred during server
Hi, I am digging up an old thread because it is still relevant today.
I am the maintainer of rustc in Debian. I am trying to provide cross-compiling
libraries for windows. I have 64-bit working fine, however 32-bit is not
working because rustc expects dw2 exceptions but Debian's mingw only
refresh
> * comment out 0002 (original) patch in debian/patches/series
> * dch -i und Changelog-Eintrag vorgenommen (Note: version number)
> * debuild
>
> for version 11.0.34 the (new/updated) patch is as follows:
> Author: Ximin Luo , Helge Kreutzmann
>
> Description: re
Control: tags -1 + moreinfo unreproducible
Hi you two,
I am in the process of updating this package. However, the curretn verison
3.4.7-1 works for me with firefox 79 in sid. So I don't know why it's not
working for you. Therefore I don't feel right to close this bug when updating
to the new
Package: wine-development
Version: 5.5-4
Followup-For: Bug #963094
Control: tags -1 + upstream patch
Looks like these patches fix the issue:
https://github.com/wine-mirror/wine/commit/4465ecfe0e3fa9fa14518abd1907193adb154957.patch
Package: wine-development
Version: 5.5-4
Severity: serious
Justification: FTBFS
Dear Maintainer,
Sadly, the latest update to "support vulkan 1.2" does not work with the latest
version, uploaded 1 day after the fix.
[..]
cd dlls/winevulkan && ./make_vulkan
Traceback (most recent call last):
Control: reassign -1 llvm-toolchain-9
Control: affects -1 rustc
Control: tags -1 + upstream patch
LLVM maintainer, please backport the following upstream patch to LLVM 9:
https://github.com/rust-lang/llvm-project/commit/7d5e7c023053660ffe494d72ce471e48ecc7f49b
Since rust has already backported
Control: tags -1 + patch
Ximin Luo:
> Dmitry Smirnov:
>> On Sunday, 26 April 2020 9:25:06 AM AEST Ximin Luo wrote:
>>> The source code doesn't mention any particular reason, and one person on
>>> the upstream bug report mentions it in such an off-the-cuff and
>>&
Dmitry Smirnov:
> On Sunday, 26 April 2020 9:25:06 AM AEST Ximin Luo wrote:
>> The source code doesn't mention any particular reason, and one person on
>> the upstream bug report mentions it in such an off-the-cuff and
>> non-explanatory way I can't take it into account as
Dmitry Smirnov:
> On Sunday, 26 April 2020 8:20:28 AM AEST Ximin Luo wrote:
>> As I mentioned on firefox bugzilla [1], I have figured out the exact place
>> in the firefox code responsible for this issue.
>>
>> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1
CC bug 919557 & interested parties
CC firefox Debian maintainer
As I mentioned on firefox bugzilla [1], I have figured out the exact place in
the firefox code responsible for this issue.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1420286
Near the bottom of
peter green:
> On 23/04/2020 17:07, Ximin Luo wrote:
>> close 958547
>> thanks
>>
>> See
>> https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2020-January/009512.html
>>
>> Just be patient and wait a few days, the issue usually resolves
Thanks, the file in /usr indeed should not be there and should be fixed in the
next cargo upload, 0.43.1-2.
Yes, the boundary between dh-cargo and cargo-debian-wrapper (which lives in
cargo) is a bit unclear and some of it is derived from historical reasons, this
can certainly be improved in
it too, so there should be
no need to wait for the below packages. I got confused earlier because we use
rust-cargo to update cargo, and I temporarily forgot my own instructions on
updating the packaging.
So Thunderbird should now be unblocked on this front.
Best,
Ximin
Ximin Luo:
> Hi Cars
-master.upload
I will ping them to hopefully get a bit more priority.
Best,
Ximin
Carsten Schoenert:
> Hello Ximin,
>
> Am 04.04.20 um 02:17 schrieb Ximin Luo:
>> Hi Carsten, it might be a couple of weeks until we get this done.
>> Have you tried just deleting the version
Package: lintian
Version: 2.59.0
Severity: normal
Control: affects -1 rustc debhelper
Dear Maintainer,
I updated rustc from debhelper compat 9 to 12 which enables dh_dwz.
Sadly for rustc this causes an empty multifile to be created as
/usr/lib/debug/.dwz/i386-linux-gnu/rustc.debug which lintian
Carsten Schoenert:
> Hello Ximin,
>
> Am 04.04.20 um 02:17 schrieb Ximin Luo:
>> Hi Carsten, it might be a couple of weeks until we get this done.
>> Have you tried just deleting the version constraint and using the
>> existing version in Debian sid?
> I've tried
Hi all,
I agree that rustup should be in Debian. Achieving this is currently blocked on
either of these two issues:
- https://github.com/rust-lang/rustup/issues/835 OR
- https://salsa.debian.org/rust-team/debcargo/-/merge_requests/22
If you want to help, achieving either of these would help to
Hi Carsten, it might be a couple of weeks until we get this done. Have you
tried just deleting the version constraint and using the existing version in
Debian sid?
X
Carsten Schoenert:
> Package: cargo
> Version: 0.40.0-3
> Severity: wishlist
>
> Dear Maintainer,
>
> I'm working on packaging
steam is now back to normal and I don't need that workaround any more.
Ximin
Simon McVittie:
> On Wed, 25 Mar 2020 at 20:48:37 +0000, Ximin Luo wrote:
>> In $STEAMDIR/error.log we see:
>>
>> Failed to load steamui.so - dlerror():
>> /usr/lib/i386-linux-gnu/libpango
Ximin Luo:
> Ximin Luo:
>> Package: steam
>> Version: 1.0.0.61-2
>> Severity: important
>>
>> Dear Maintainer,
>>
>> The latest Steam client upgrade fails to run, crashing with a dialog box
>> saying:
>>
>>Fatal Error: Failed
Ximin Luo:
> Package: steam
> Version: 1.0.0.61-2
> Severity: important
>
> Dear Maintainer,
>
> The latest Steam client upgrade fails to run, crashing with a dialog box
> saying:
>
>Fatal Error: Failed to load steamui.so
>
> There's no other det
Package: steam
Version: 1.0.0.61-2
Severity: important
Dear Maintainer,
The latest Steam client upgrade fails to run, crashing with a dialog box saying:
Fatal Error: Failed to load steamui.so
There's no other details unfortunately.
Best,
Ximin
-- System Information:
Debian Release:
Antoine Beaupré:
> On 2019-10-25 11:58:37, Antoine Beaupré wrote:
>> On 2019-09-04 23:05:19, Paul Wise wrote:
>>> On Fri, 22 Feb 2019 07:47:00 + Ximin Luo wrote:
>>>
>>>> For the time being you can work around the issue either by using
>>>>
Control: reassign -1 ufw
Control: severity -1 grave # breaks security software
ufw needs to be patched/updated to call iptables{,6}-legacy-{save,restore}.
In the meantime, iptables 1.8.3 is no longer in Debian, but the user can work
around this by doing `sudo update-alternatives --config
Paul Wise:
> On Mon, 2020-01-20 at 22:51 +0800, Shengjing Zhu wrote:
>> On Mon, Jan 20, 2020 at 10:37 PM Ximin Luo wrote:
>>> This doesn't work for Rust unfortunately, due to features. Based on
>>> which feature-set is activated, when you depend on a source-package
On Sat, 18 Jan 2020 10:25:36 +0800 Paul Wise wrote:
> On Sat, 18 Jan 2020 00:31:11 +0800 Shengjing Zhu wrote:
>
> > There're a lot of packages in archive which users are not expected to
> > install, for examples:
> >
> > * all golang-*-dev packages. (currently there are 1k+)
> > * maybe[1] all
Bernhard R. Link:
> * Ximin Luo [191223 12:58]:
>> dpkg and all other debian tools support it right now. It is only reprepro
>> with this artifical constraint, which makes it not work for packages that
>> are processable by dpkg and other debian tools.
&g
Helmut Grohne:
> Control: retitle -1 cannot migrate to testing
>
> Hi Fabian,
>
> On Mon, Jan 13, 2020 at 04:27:15PM +0100, Fabian Wolff wrote:
>> On Mon, 13 Jan 2020 06:21:56 +0100 Helmut Grohne wrote:
>>> Source: z3
>>> Version: 4.8.7-3
>>> Severity: serious
>>>
>>> z3 cannot be built on
Fabian Wolff:
> On Mon, 13 Jan 2020 06:21:56 +0100 Helmut Grohne wrote:
>> Source: z3
>> Version: 4.8.7-3
>> Severity: serious
>>
>> z3 cannot be built on buildds, because its Build-Depends cannot be
>> satisfied on buildds. Failing to build on buildds is a serious problem.
>
> It builds now on
Steve Langasek:
> [..]
>
> There is no rust-compiler-builtins package in the Debian archive or in the
> NEW queue.
It's in NEW.
We're aware of all of these issues you're filing bug reports for, and in fact
there are many more than the ones you're filing for. These reports are not
actually
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Hi, please remove this package from Testing as it is blocking others from
migration and nothing else depends or build-depends on it.
-- System Information:
Debian Release: bullseye/sid
APT
Fabian Wolff:
> On 1/9/20 5:22 PM, Aurelien Jarno wrote:
>> On 2020-01-09 14:18, Ximin Luo wrote:
>>> So setting CMAKE_USE_PTHREADS might work.
>>
>> Yep, I confirm that works. In short with the following patch, z3 builds
>> natively on riscv64:
>
>
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Hi, rust-grcov depends on old versions of some rust crates, blocking testing
migration.
It will be some time before we can deploy the new version as it depends on
multiple packages not yet in
Fabian Wolff:
> Thank you for your MR, Ximin!
>
> Do you need anything else? I see you haven't added -pthread anywhere yet; is
> this not necessary with CMake (maybe CMake adds it automatically?), and have
> you tried building on/for riscv64 again to verify that it works now?
>
I only tried
Aurelien Jarno:
> On 2020-01-07 23:54, Fabian Wolff wrote:
>> Thank you all for your patches and the ensuing discussion.
>>
>> I am currently working on porting the z3 Debian package to use the
>> CMake build scripts; I think this will simplify things for all parties
>> involved now and in the
1 - 100 of 1255 matches
Mail list logo
