severity 1103553 wishlist
tags 1103553 upstream
On Sun, Apr 20, 2025 at 12:21 AM Santiago Vila wrote:
>
> El 19/4/25 a las 20:32, Roman Lebedev escribió:
> >> The cpuinfo is attached.
> > Right, so that CPU does claim to have AMX support.
> > But is AMX supp
On Sat, Apr 19, 2025 at 1:33 PM Santiago Vila wrote:
>
> El 19/4/25 a las 10:48, Roman Lebedev escribió:
> > Does the bug reproduce if the whole build is rerun from scratch?
>
> I tried six times before reporting:
>
> Status: failed halide_19.0.0-6_amd64-20250418T1000
Hi.
On Sat, Apr 19, 2025 at 2:39 AM Santiago Vila wrote:
>
> Package: src:halide
> Version: 19.0.0-6
> Severity: serious
> Tags: ftbfs trixie sid
>
> Dear maintainer:
>
> During a rebuild of all packages in unstable, your package failed to build:
>
> --
Hi.
Could you please check if this issue has been
sufficiently addressed in the newest package: 19.0.0-6 ?
Roman.
On Sun, Feb 23, 2025 at 11:06 PM Lucas Nussbaum wrote:
>
> On 18/02/25 at 06:56 +0300, Roman Lebedev wrote:
> > It says:
> > DC-System-Info: 8 cores (Intel(R) Xeon(R) Platinum 8259CL CPU @
> > 2.50GHz), 32516492 kB RAM
> > ... which is ~32GB of RAM. Are many packages
On Mon, Feb 17, 2025 at 8:31 PM Lucas Nussbaum wrote:
>
> Source: halide
> Version: 19.0.0-5
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-2025-02-15 ftbfs-trixie
>
> Hi,
Hi.
> During a rebuild of all packages in sid, this package f
Source: halide
Followup-For: Bug #1076968
Control: tags -1 ftbfs moreinfo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi!
> Hi. I don't know what exactly you did in version 18.0.0-2 to fix
> this bug
This was the change:
https://salsa.debian.org/pkg-llvm-team/halide/-/commit/716cf8e964d581f
Package: libllvm18
Version: 1:18.1.1-1
Followup-For: Bug #1067005
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I've just tried building the halide package against LLVM17 (instead of LLVM18),
and the bug no longer happens, so it's, almost assuredly,
symbol versioning, in my opinion.
Roman.
-
Package: libllvm18
Version: 1:18.1.1-1
Severity: serious
File: /usr/lib/llvm-18/lib/libLLVM.so.18.1,
/usr/lib/x86_64-linux-gnu/libLLVM-17.so.1
X-Debbugs-Cc: Sylvestre Ledru , Gianfranco Costamagna
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm having a bit of a deja-vu here, because this
Package: libisl23
Followup-For: Bug #1038603
X-Debbugs-Cc: Debian GCC Maintainers ,
debian-rele...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
While the issue has been resolved in isl 0.26-3,
which was uploaded to unstable on 2023-06-19,
nothing has been done for the stable
On Thu, 8 Sep 2022 15:20:23 +0200 Matthias Klose wrote:
> fixed in unstable, now built using LLVM 13.
When this bug was closed, it was titled "creduce: Please upgrade to
llvm-toolchain-14",
so i don't believe this is fixed, which is suboptimal because creduce
is the only blocker
for me to be able
Package: arcanist
Version: 0~git20200925-2
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I *think* this has been fixed upstream in
https://github.com/phacility/arcanist/commit/3626582354e4fc62191927a80b274ec71284cb77
and
https://github.com/phacility/arcanist/commit/b50a646a3f49c
Package: qtcreator
Version: 6.0.1-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Looks like qtcreator (and iwyu/etc) need to be rebuilt again.
After some recent updates, qtcreator again shows errors
about certain C++ types not being known.
Roman
- -- System Information:
De
Package: python3-nbclient
Version: 0.5.5-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer, it looks like python3-nbclient / jupyter-client don't
play well together:
Unpacking python3-nbclient (0.5.6-1) over (0.5.5-1) ...
dpkg: error processing archive
/tmp/apt
I've just rebuilt qtcreator locally, and the bug is gone.
Dear maintainer, please rebuild the package.
Roman.
On Tue, Sep 28, 2021 at 11:24 AM Roman Lebedev wrote:
>
> Package: qtcreator
> Version: 5.0.1-1
> Severity: serious
>
> -BEGIN PGP SIGNED MESSAGE-
> H
Package: qtcreator
Version: 5.0.1-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Looks like qtcreator (and iwyu/etc) need to be rebuilt again.
After some recent updates, qtcreator again shows errors
about certain C++ types not being known.
Roman
- -- System Information:
De
Package: libpcre2-posix2
Version: 10.34-5
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Preparing to unpack .../4-libpcre2-posix2_10.34-5_amd64.deb ...
Unpacking libpcre2-posix2:amd64 (10.34-5) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-zUiPeq/4-libpcre2-posix2_
Package: z3
Version: 4.8.4-1
Severity: serious
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer.
It is good to see Z3 4.8.4 finally being packaged in Debian!
As i have personally just encountered, that version contains some bugs,
that result in incorrect modelling, whi
Package: amarok
Version: 2.9.0-1+b1
Followup-For: Bug #921194
Dear maintainer.
The amarok builds just fine as per the steps outlined in
https://wiki.debian.org/BuildingTutorial#Rebuild_without_changes
No source changes are necessary.
I guess the only thing needed is the actual libmariadb* dep vers
reassign 893517 gcc-8
found 893517 8-20180319-1
forwarded 893517 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85040
forwarded 893517 https://bugs.llvm.org/show_bug.cgi?id=36869
notfound clang-6.0 1:6.0-1
thanks.
On Mon, Mar 19, 2018 at 7:30 PM, Roman Lebedev wrote:
> Package: clang-6.0
> V
Package: clang-6.0
Version: 1:6.0-1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
$ cat test.cpp
#include
$ clang++-6.0 -c test.cpp
In file included from test.cpp:1:
In file included from
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/ostream:38
Package: python3-cairo
Version: 1.10.0+dfsg-5+b2
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The following packages will be upgraded:
python3-cairo
1 upgraded, 0 newly installed, 0 to remove and 68 not upgraded.
77 not fully installed or removed.
Need to get 0 B/46.9 MB of
On Thu, Mar 9, 2017 at 1:07 AM, Adrian Bunk wrote:
> On Wed, Mar 08, 2017 at 04:25:18PM +0300, Roman Lebedev wrote:
>> On Wed, Mar 8, 2017 at 3:38 PM, Adrian Bunk wrote:
>> > Source: darktable
>> > Version: 2.2.1-2
>> > Severity: serious
>> >
>&g
On Wed, Mar 8, 2017 at 3:38 PM, Adrian Bunk wrote:
> Source: darktable
> Version: 2.2.1-2
> Severity: serious
>
> https://buildd.debian.org/status/fetch.php?pkg=darktable&arch=i386&ver=2.2.1-2&stamp=1483383078&raw=0
>
> ...
> -- Performing Test _MSSE2
> -- Performing Test _MSSE2 - Success
> -- Bui
Package: python3-jsonschema
Version: 2.5.1-5
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi.
We have just installed python3-jsonschema into clean chroot (docker
debian:testing).
When we run jsonschema, we get the following error:
Traceback (most recent call last):
File
This is now fixed in git master.
https://github.com/darktable-org/darktable/pull/1217
Do note that we will not cherry-pick this into stable branch (2.0.x).
So if debian wants, those patches will need to be applied as part
of packaging.
Roman.
Package: libomp5
Version: 3.7.0-3
Severity: serious
Dear Maintainer,
This is almost exact copy of Debian Bug #775257 titled:
libiomp5: missing SONAME link /usr/lib/libiomp5.so -> libiomp5.so.5
libomp5 misses the SONAME link, which breaks all clang openmp support.
You can test it by:
$ cat test
Package: synaptic
Version: 0.82
Severity: grave
Dear maintainer,
$ synaptic-pkexec
/usr/sbin/synaptic: error while loading shared libraries:
libept.so.1.aptpkg4.16: cannot open shared object file: No such file or
directory
I guess, it might be due to recent apt upgrade?
$ locate libept.so
/us
Package: kdenlive
Version: 15.08.2-1
Severity: grave
Dear Maintainer,
1. Start kdenlive
2. Right-click in Project Bin, -> Add Clip
3. Select any video, press ok.
4. Move it into Timeline in the bottom
5. Kdenlive is completely frozen.
Thus, it is completely impossible to use kdenlive.
-- System
29 matches
Mail list logo
