"Rebecca N. Palmer" writes:
> test_create_new_trial (both parts) sometimes fails on s390x, failing
> the autopkgtest.
>
> It might make sense to remove this package on s390x, if it isn't
> reasonable to actually fix this.
Thanks for the report! I've brought this to upstream's attention [1],
but
Hello all,
As part of my DD process I have been tasked with preparing an NMU for an
existing bug. I ended up preparing one for this bug, using Steve's
debdiff.
If I don't hear back from anyone within three days, my AM will upload
this NMU in DELAYED/7.
Best,
Gard
signature.asc
Description: P
rnels.-file_operations-dtype-is-change.patch
(2020-05-05 09:26:30 +0200)
Gard Spreemann (1):
Add patch 0004-fix-for-5.6-kernels.-file_operations-dtype-is-change.patch
.../0004-fix-for-5.6-kernels.-file_operations-dtype-is-change.
Oops, I was a bit careless. Let me clarify: the patch in my PR is not
from the actual upstream for the package, but rather from the fork [1]
linked to by Thomas Koch in #959729 [2].
[1] https://github.com/teleshoes/acpi_call
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959729#10
I maintain a package (src:gudhi) that build-depends on
libqglviewer-dev-qt5 and depends on libqglviewer2-qt5. As a relatively
fresh DM, I haven't experienced depending on a to-be-removed package
yet, so I'm a bit confused.
Are *all* binaries built from src:libqglviewer to be removed? If yes,
why a
Matthias Klose writes:
> Package: src:gudhi
> Version: 3.3.0+dfsg-1
> Severity: important
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9
>
> seem to be a packaging error
Indeed! Thanks for reporting. I think I know what's wrong, and will get
to it soon.
Hi,
I believe this is upstream's issue 27506 [1]. Given the bug's nature, I
suggest that perhaps it should be temporarily worked around by disabling
the failing test.
[1] https://github.com/scikit-learn/scikit-learn/issues/27506
Best,
Gard
signature.asc
Description: PGP signature
The following code based on the failing test reproduces the issue on an
i386 porterbox:
***
from sklearn.tree import (
DecisionTreeClassifier,
export_graphviz,
)
import pdb
X = [[-2, -1], [-1, -1], [-1, -2], [1, 1], [1, 2], [2, 1]]
y2 = [[-1, 1], [-1, 1], [-1, 1], [1, 2], [1, 2], [1, 3]]
It seems that any `Tree` attribute that uses `self._get_node_ndarray()`
to get a *floating point* ndarray suffers from this weird behavior when
negating. Examples include `weighted_n_node_samples` and
`threshold`. However, attributes that use the same function to get
*integer* ndarrays don't. Examp
On 4 April 2024 02:52:29 CEST, David Landry wrote:
>Good evening,
>
>The bug involving compiling/installing nvidia-kernel-dkms is still present.
>The result of the bug is that following a reboot after the erroneous
>installation noted below, my display drivers get completely disabled,
>includin
Control: forwarded -1 https://github.com/PythonOT/POT/issues/618
Thanks for the bug report.
This seems like a simple case of a missing floating point tolerance in
upstream's test. It's easy to patch, but I've sent a reproducible
example upstream [1] as they're likely to have better insight into t
I've am unable to reproduce this bug with ipe/7.2.17-2 and
gcc-10/10.1.0-6. The package currently builds fine for me with those
versions.
Hi,
> I admit I'm not sure at what point / what tool might inject this
> string and I'm also not sure whether the option -march=native is
> really used in the amd64 case.
From my (very limited!) understanding, this is just setuptools(?) trying
out various compiler options. The actual C compiler i
I believe Salsa commit ba393a45 [1] fixes this bug. However, other build
problems relating to the shipped symbols prevent me from uploading the
fixed version.
[1] https://salsa.debian.org/deeplearning-team/onednn
signature.asc
Description: PGP signature
Reopening because the patch did not properly fix the issue on arm64.
The patch has been updated in 5efbe42a on Salsa.
-- Gard
signature.asc
Description: PGP signature
I've made an MR on Salsa with a patch that I have verified fixes the
bug[1].
Although, as has been mentioned, the best thing is probably just to
package upstream's 4.3.1. But since this bug has been around for a
while, I will do an NMU to DELAYED/5 with the fix from the MR if I don't
hear back in
ebian/changelog 2022-04-07 09:15:36.0 +0200
@@ -1,3 +1,11 @@
+imv (4.3.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * d/patches: add 0002-Fix-segfault-with-latest-wlroots.patch to fix
+segfault with newer wlroots (Closes: #1006543)
+
+ -- Gard Spreemann Thu, 07 Apr
X-Debbugs-CC: d...@jones.dk,pe...@riseup.net
Hi all.
Jonas Smedegaard writes:
> Hi Pelle,
>
> You reported this issue for swaylock 1.5-2.
>
> Do you still experience same isue with swaylock 1.6-1 now in Debian
> unstable?
I cannot answer for Pelle, but I was also experiencing this bug back
wh
X-Debbugs-CC: pe...@riseup.net
Pelle writes:
>>I cannot answer for Pelle, but I was also experiencing this bug back
>>when it was reported. FWIW: I'm unable to reproduce it with 1.6-1. That
>>being said, triggering the bug does seem somewhat stochastic, so I can't
>>rule out that a bunch more su
Hi,
I have verified that adding libglu1-mesa-dev to the build-deps makes the
package again build successfully.
-- Gard
signature.asc
Description: PGP signature
Paul Gevers writes:
> I looked at the results of the autopkgtest of your package. I noticed
> that it regularly fails on some architectures, particularly on s390x,
> but not exclusively there. Yesterday I triggered 5 or 6 reference runs
> on every architecture and 6/6 failed on s390x and 1/5 fai
Source: hera
Version: 1.0.0+dfsg-2
Followup-For: Bug #1039001
Control: severity 1039001 wishlist
Uploading catch2 v3 also made hera FTBFS (#1054686), and it is not clear
whether the catch2 package will provide backwards-compatible headers
(#1055237). Since updating hera is not entirely trivial, th
Package: xul-ext-firegestures
Version: 1.10-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After a recent Iceweasel upgrade from 38.5.0esr-1 to 43.0.2-1+b1, the
Fireguestures extension no longer does anything. The standard swipe
guestures seem to be recognized, but not
I'm sad to see that we shipped Bullseye without an essential component
of Sway. Is there anything I can do to assist in getting this bug fixed,
perhaps for a potential future bullseye-packports package?
-- Gard
signature.asc
Description: PGP signature
Thank you for reporting this. It also revealed an upstream bug, which
has been forwarded.
I'm uploading a fix now.
Best,
Gard
Andreas Tille writes:
> Hi,
>
> I personally have no interest in arrayfire but I realised that the
> Debian packaged version depends clblas (and is the only remaining
> package that needs cblas and I would like to see it removed from Debian
> due to bug #949767)
Hi,
FWIW: It seems that arrayfi
Andreas Tille writes:
> Hi Aaron,
>
> On Tue, Apr 27, 2021 at 08:14:10PM -0400, Aaron M. Ucko wrote:
>> Please try adding a build dependency on libclfft-dev and replacing
>> src/backend/opencl/CMakeLists.txt's inclusion of build_clFFT with a call
>> to
>>
>> find_package(clFFT)
>>
>> > Than
Gard Spreemann writes:
> Andreas Tille writes:
>
>> Hi Aaron,
>>
>> On Tue, Apr 27, 2021 at 08:14:10PM -0400, Aaron M. Ucko wrote:
>>> Please try adding a build dependency on libclfft-dev and replacing
>>> src/backend/opencl/CMakeLists.txt
Gard Spreemann writes:
> Gard Spreemann writes:
>
>> Andreas Tille writes:
>>
>>> Hi Aaron,
>>>
>>> On Tue, Apr 27, 2021 at 08:14:10PM -0400, Aaron M. Ucko wrote:
>>>> Please try adding a build dependency on libclfft-dev and replac
Package: libpmix-dev
X-Debbugs-Cc: g...@nonempty.org
Version: 4.0.0-4
Severity: serious
Justification: Policy 7.6
Dear Maintainer,
Upgrading libpmix-dev from 3.2.2~rc1-1 to 4.0.0-4 fails with
dpkg: error processing archive
/tmp/apt-dpkg-install-xYYyH5/070-libpmix-dev_4.0.0-4_amd64.deb (--unpac
Andreas Beckmann writes:
> Package: python3-pot
> Version: 0.8.1+dfsg-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> python3-pot ships python scripts with generic names at a generic
> location, causing file conflicts with packages doing the same mistake
31 matches
Mail list logo