Hi Paride,
On 2024-05-20 18:25, Paride Legovini wrote:
> On 2024-05-20 17:55, Christian Kastner wrote:
>> The test trigger we recorded was "linux-signed-amd64=6.8.9+1" but that
>> could just be coincidental.
>
> Hi, this seems to be the same of:
>
> http
Package: autopkgtest
Version: 5.28
Severity: normal
In the Debian ROCm Team's CI, QEMU workers occasionally tmpfail with the
following error:
> autopkgtest: timed out waiting for 'command prompt on serial console'
>From [1], I guess that the official CI hit this, too.
However, this is an
Hi,
On 2024-05-19 17:06, Wouter Verhelst wrote:
> Package: autopkgtest
> Version: 5.35
> Severity: normal
>
>> sudo autopkgtest-build-qemu --architecture amd64 sid
>> /opt/chroots/autopkgtest-qemu.img
>
> followed by
>
>> autopkgtest . --test-name=initrd-boot -- qemu
>>
Hi,
@josch, sorry, I overlooked that you referenced me earlier in this bug.
On 2024-05-14 12:12, Johannes Schauer Marin Rodrigues wrote:
> In general, you should avoid using -d or --dist with sbuild. But I see that
> sbuild-qemu always adds this option to the sbuild call. I am unable to say why
On 2024-04-11 15:25, Paride Legovini wrote:
> On 2024-04-11 08:35, Christian Kastner wrote:
> Ubuntu did indeed switch to something else: that's netplan.io.
> On a Bionic system:
>
> $ apt show netplan.io
> Package: netplan.io
> Version: 0.99-0ubuntu3~18.04.5
>
On 2024-04-11 09:27, Paul Gevers wrote:
>> (2) Modify setup-commands/setup-testbed and generally move ifupdown
>> installation there. This would require re-ordering stuff, as
>> interface configuration is currently performed *before* APT
>> configuration, when in needs to be after
Control: tags -1 - pending
On 2024-04-08 15:21, Paride Legovini wrote:
> Fixed in master by:
>
> https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/315
Sadly, it turns out that this wasn't the fix, at least not in a wider sense.
Yes, images can be built now, but without ifupdown
On 2024-04-10 15:29, Simon McVittie wrote:
> On Wed, 10 Apr 2024 at 11:54:02 +0200, Christian Kastner wrote:
>> I've already filed an MR at vmdb2 upstream that fixes the logic, but I
>> thought it might be best to track the issue here as well. Please feel
>> free to close
Package: autopkgtest
Version: 5.34
Severity: normal
Block: -1 by 1068746
When building an Ubuntu image with autopkgtest-build-qemu and using
--boot=efi, the resulting image fails to boot when running autopkgtests
on it.
An attempted manual boot with qemu-system-x86_64 shows EFI complaining
about
Package: vmdb2
Version: 0.28-2
Severity: normal
Forwarded: https://gitlab.com/larswirzenius/vmdb2/-/merge_requests/143
In #951766, grub's --force-extra-movable (Debian) was conditionalized
for Ubuntu grub's --no-extra-removable. But the logic is flipped: where
Debian uses --force-extra-removable,
Hi Paul,
On 2024-04-07 16:42, Paul Gevers wrote:
> The following issues have come up several times over the years. I
> propose to discuss them in one place (this bug report) to define the
> solution strategy. I haven't gone through all the details myself, so I
> might be thinking in the wrong
Control: tags -1 - pending
I close the proposed MR implementing this as in light of the recently
published workaround, it is too invasive.
Hi Joe,
On 2020-11-23 06:03, Joseph Nahmias wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Joseph Nahmias
>
> * Package name: nbdime
> Version : 2.1.0
> Upstream Author : Jupyter Development Team
> * URL : https://nbdime.readthedocs.io/
> * License :
On 2024-02-21 09:22, Christian Kastner wrote:
> On 2024-02-21 08:02, Johannes Schauer Marin Rodrigues wrote:
>> is this a duplicate of #1061388?
>
> I *think* so, but I'm not sure.
>
> The cause definitely seems to be the same: on the host, prior to opening
> the chroot,
Hi again,
On 2024-03-29 20:30, Christian Kastner wrote:
> Policy 5.6.30 lists the Testsuite field, but it doesn't list the
> Testsuite-Triggers field that seems to be part of Sources files and is
> generated by dpkg-source >= 1.18.8.
>
> This field is quite useful, as given my
On 2024-04-04 09:05, Christian Kastner wrote:
> The issue is already visible with AMD_LOG_LEVEL=1, it's the lack of PCIe
> atomics:
>
>> [ RUN ] rocfft_UnitTest.default_load_callback_complex_single
>> :1:rocvirtual.cpp :2949: 1796815625 us: [pid:1917
>&g
On 2024-04-02 00:35, Cordell Bloor wrote:
> I tried to reproduce the rocfft callback bug with a W6800 (gfx1030). I
> used a Debian Unstable docker container on an Ubuntu Noble host, but the
> tests all passed. This made me realize that the test failure pattern on
> the CI is that all the
Hey Cory,
thank you for the analysis. I'll try to reproduce and lock this down on
my end, too.
Best,
Christian
On 2024-04-02 00:35, Cordell Bloor wrote:
> I tried to reproduce the rocfft callback bug with a W6800 (gfx1030). I
> used a Debian Unstable docker container on an Ubuntu Noble host,
Hi Sean,
On 2024-03-30 02:35, Sean Whitton wrote:
>> I'd provide a patch based on the documentation in dsc(5), but I don't
>> know what the current process is. Does anyone have a link to a doc on
>> how to submit a change?
>
> There is a chapter of Policy regarding the Policy Changes Process.
Package: debian-policy
Version: 4.6.2.0
Severity: wishlist
Policy 5.6.30 lists the Testsuite field, but it doesn't list the
Testsuite-Triggers field that seems to be part of Sources files and is
generated by dpkg-source >= 1.18.8.
This field is quite useful, as given my package src:foo, I can
Hi josch,
On 2024-03-28 11:28, Johannes Schauer Marin Rodrigues wrote:
> I think sbuild-qemu-boot and sbuild-qemu-update should do the same as
> autopkgtest did here:
>
> https://salsa.debian.org/ci-team/autopkgtest/-/commit/7a4954ded0f24221ac34ca0aaf10f3f9b083afa2
Thanks for pointing this out!
Hi Timo,
On 2024-03-14 10:06, Timo Röhling wrote:
>> Having read up on debian-python, I have misread the situation. I think
>> there needs to be a policy resolution first.
> I don't understand what you mean. The orphaning process is not tied to
> DPT policy, is it?
>
> FWIW, I am a regular user
Control: found -1 5.2.3-3
Hi Cory,
On 2024-03-09 07:20, Cordell Bloor wrote:
> On systems, the rocm_agent_enumerator command may crash with an error:
>
> Traceback (most recent call last):
> File "/usr/bin/rocm_agent_enumerator", line 260, in
> main()
> File
Hey Ptter,
On 2024-03-08 20:21, Petter Reinholdtsen wrote:
> [Christian Kastner 2024-02-13]
>> I'll push a first draft soon, though it will definitely not be
>> upload-ready for the above reasons.
>
> Where can I find the first draft?
I've discarded the simple package
Control: retitle -1 O: numpy -- Fast array facility to the Python 3 language
Control: tags -1 - pending
Having read up on debian-python, I have misread the situation. I think
there needs to be a policy resolution first.
On 2024-03-02 22:18, Christian Kastner wrote:
> Control: retitle -1
Control: retitle -1 ITA: numpy -- Fast array facility to the Python 3 language
Control: tags -1 pending
I intend to put this under the Debian Python Team.
On 2024-03-02 21:46, Sandro Tosi wrote:
> Package: wnpp
> Severity: normal
> X-Debbugs-Cc: nu...@packages.debian.org, mo...@debian.org
>
Hey Cory,
On 2024-02-28 21:16, Cordell Bloor wrote:
> This segfault does seem to be caused by mixing clang-15 and clang-17 in
> the HIP RTC codepath. When libamdhip64 from ROCm 5.6.1 (built with the
> same clang-17 as rocm-compilersupport 6.0+git20231212.4510c28+dfsg-1) is
> used, the segfault
Hi Étienne,
On 2024-02-26 19:29, Étienne Mollier wrote:
> If that helps, the autoremoval timer is reset each time the RC
> critical bug triggering the autoremoval is updated, e.g. when
> reporting an evolution of the situation in a new comment.
thanks for the info! That's incredible useful to
Hi all,
adding #1033352 as below contains information for that bug, too.
On 2024-02-25 19:50, Johannes Schauer Marin Rodrigues wrote:
> in that issue you asked exactly the question I was about to ask you. :)
>
> Though it seems incus should now be able to deal gracefully with the situation
>
On 2024-02-26 07:23, Cordell Bloor wrote:
> The update of rocsparse 5.5.1 to 5.7.1 seems to have caused a regression
> in hipsparse. Although, it's also possible that this problem was because
> rocsparse was therefore rebuilt with the updated rocprim 5.7.1.
This one looks a bit tricky as it also
Package: libhipsparse0-tests
Version: 5.7.1-1~exp1
Severity: normal
On gfx1031/gfx1032/gfx1034, there are numerous occurrences of
HIPSPARSE_STATUS_INTERNAL_ERROR, see [1] for a full log. Interestingly,
only some of them lead to test failures (some examples below), and
sometimes there is more than
On 2024-02-26 07:23, Cordell Bloor wrote:
> The update of rocsparse 5.5.1 to 5.7.1 seems to have caused a regression
> in hipsparse. Although, it's also possible that this problem was because
> rocsparse was therefore rebuilt with the updated rocprim 5.7.1.
Interestingly, this passed on gfx900
Hi Sebastian,
writing to you as you bumped the severity to 'serious': could the rT
please give us an extension on the autoremoval for this particular bug.
The transition from first-filing-to-serious was unusually short notice,
and caught us in the middle of our own update of the stack.
This
Package: lintian
Version: 2.117.0
Severity: wishlist
It would be nice if lintian could warn about packages with ~exp in their
Debian revisions where suite is not experimental.
So these would warn:
libfoo (1.0-1~exp) unstable; urgency=medium
libfoo (1.0-1~exp1) unstable; urgency=medium
Hi josch,
On 2024-02-21 08:02, Johannes Schauer Marin Rodrigues wrote:
> Quoting Christian Kastner (2023-03-23 09:53:05)
>> Attempting to build a package with the autopkgtest-virt-podman backend fails
>> because of what I suspect is an issue with $HOME directory handling. podman
Hi Carles,
On 2024-01-11 12:01, Carles Pina i Estany wrote:
> It ended with:
> Exec: ['sh', '-ec', 'export AUTOPKGTEST_BUILD_QEMU=1;
> /usr/share/sbuild/sbuild-qemu-create-modscript "$ROOT"']
> Exec: ['zerofree', '-v', '/dev/mapper/loop0p1']
> ERROR: [Errno 2] No such file or directory:
Control: tag -1 pending
I've uploaded this to experimental, though with the Debian Python Team
as maintainer. Because although it is a dependency of the ROCm stack, it
seems to be a generally useful Python library.
Best,
Christian
On 2024-02-16 18:57, Cordell Bloor wrote:
> Package: wnpp
>
Hi Petter,
On 2024-02-13 08:36, Petter Reinholdtsen wrote:
> I tried building the CPU edition on one machine and run it on another,
> and experienced illegal instruction exceptions. I suspect this mean one
> need to be careful when selecting build profile to ensure it work on all
> supported
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org
* Package name: llama.cpp
Version : b2116
Upstream Author : Georgi Gerganov
* URL : https://github.com/ggerganov/llama.cpp
* License
Hi Peter,
On 2023-10-26 19:29, Peter Samuelson wrote:
> Package: libcap2-bin
> Version: 1:2.66-4
> Severity: wishlist
>
> In my opinion, getcap(8) is useful to run as a non-root user, so it
> should be in /bin rather than /sbin. This seems analogous to ip(8)
> from iproute2, which was moved to
On 2024-02-06 14:28, Christian Kastner wrote:
> As discussed in this thread [1], libamd-comgr2 exports
> amd_comgr_get_isa_count@1.8 when upstream is at @2.0.
>
> This is because the symbol was erroneously not removed from @1.8 when it
> was added to @2.0 when the ABI changed
Package: libamd-comgr2
Version: 5.2.3-2
Severity: important
As discussed in this thread [1], libamd-comgr2 exports
amd_comgr_get_isa_count@1.8 when upstream is at @2.0.
This is because the symbol was erroneously not removed from @1.8 when it
was added to @2.0 when the ABI changed.
The
Hi Jeffrey,
On 2023-12-02 11:39, Jeffrey Bencteux wrote:
> Hi,
>
> Both setuid() and setgid() return values are not checked in cron's code used
> to execute user-provided commands:
This issue was reported as CVD-2006-2607 and fixed a long time ago.
Here's the relevant patch:
Hi Cory,
thanks for clarifying, I indeed misunderstood a few things.
On 2023-11-24 16:42, Cordell Bloor wrote:
>> However, unlikely as it may seem, I'd still like to ask: is there any
>> risk of negatively affecting the graphics side of this? Can this change
>> somehow break a regular user's
Package: librocthrust-tests
Version: 5.3.3-5
Severity: important
All CI tests of librocthrust-tests have failed, with two different
failure modes.
On gfx803 and gfx906, the tests pass, but do so in under one minute,
with no test output. That cannot be right.
On all other architectures, about
Hi Cory,
On 2023-11-23 08:35, Cordell Bloor wrote:
> On 2023-11-22 03:19, Christian Kastner wrote:
>>> The Linux kernel on Debian is built without HSA_AMD_SVM enabled. That is
>>> the KConfig for "Enable HMM-based shared virtual memory manager", which
>&
Hey Cory,
On 2023-11-21 21:01, Cordell Bloor wrote:
> On 2023-11-18 00:39, Cordell Bloor wrote:
>> Each time a HIP application is executed, the rocr-runtime prints the message:
>>
>> KFD does not support xnack mode query.
>> ROCr must assume xnack is disabled.
>>
>> It is unclear to me
Package: debci-worker
Version: 3.7
Severity: normal
3.7 added this nice feature where arguments can be passed to backends. However,
the --qemu-options parameter of the QEMU backend cannot be used with the
current implementation because its argument usually contains spaces, and these
get
Hi Antonio,
On 2023-11-10 18:10, Antonio Terceiro wrote:
> Some shared options are defined in lib/environment.sh, I think that's
> why it currently loads lib/environment.sh before processing the command
> line options.
>
> OTH your analysis is correct, as this causes the --config option to be
>
Package: debci
Version: 3.7
Severity: normal
The --config option to the debci subcommands does not work:
$ mkdir /tmp/foo
$ echo 'debci_arch="i386"' > /tmp/foo/debci.conf
$ debci config --config /tmp/foo config_dir
config_dir=/tmp/foo
$ debci config --config /tmp/foo arch
arch=amd64
I believe
Hi,
On 2023-07-28 21:39, Antonio Terceiro wrote:
> Bug #1037245 in debci reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
>
>
Version: 5.5.1-1
Closing this bug, as it is invalid. rocrand never failed, according to
the CI logs (even the linked one).
Package: ftp.debian.org
Severity: normal
Please remove hipcub from testing on arm64, it's blocking migration because
most buildds can't handle it.
The last successful build was on arm-arm-01, builds on other hosts all time
out.
We currently cannot test these packages on arm64 anyway.
Thanks,
Control: severity -1 important
I'm downgrading this bug, as the suite successfully completed on another
Navi24 device [1]. No longer RC, this should allow migration to testing
again.
Best,
Christian
[1] https://lists.debian.org/debian-ai/2023/10/msg00044.html
Source: rocfft
Version: 5.5.0-4
Severity: grave
Justification: Can crash the host
autopkgtests for rocfft triggered a soft lockup when run with an 6500 XT
(gfx1034, Navi24).
This is very probably a kernel issue, but I'm filing this bug here until
we have actually identified the root cause, after
Source: rocrand
Version: 5.5.1-1
Severity: serious
The tests from ci.rocm.debian.net failed on gfx1030 [1]. I'm filing this
RC bug to prevent migration to testing.
[1]
https://ci.rocm.debian.net/data/autopkgtest/unstable/amd64+gfx1030/r/rocrand/83/log.gz
Hi Mathieu,
On 2023-08-22 13:29, Mathieu Malaterre wrote:
> On Thu, Aug 17, 2023 at 1:27 PM Christian Kastner wrote:
>> * Package name: half
>> Version : 2.2.0
>> Upstream Author : Christian Rau
>> * URL : https://sourceforge.net/
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: composable-kernel
Version : 0+git20230816
Upstream Author : Advanced Micro Devices, Inc.
* URL : https://github.com/ROCmSoftwarePlatform
Package: wnpp
Severity: wishlist
Owner: Christian Kastner
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org
* Package name: half
Version : 2.2.0
Upstream Author : Christian Rau
* URL : https://sourceforge.net/projects/half/
* License
Package: rabbitmq-server
Version: 3.10.8-1.1
Severity: wishlist
Tags: patch
Hi,
it would be nice to have a /etc/rabbitmq/conf.d directory. This is
supported by upstream [1].
I haven't tried this, but postinst looks simple enough, and the attached
patch should accomplish this.
Best,
Christian
Hi Daniel,
On 2023-06-12 17:01, Sune Stolborg Vuorela wrote:
> Any chance you can give Andreas a go ahead to push a newer Gnupg2 to at least
> experimental, or preferably unstable ?
I, too, would appreciate a newer version. It turns out that in versions
prior to 2.3, the 'kdf-setup' option with
On 2023-06-27 00:15, Christian Kastner wrote:
> I just have one question about debvm though (hence Helmut in CC), which
> is beyond my depth: is that kernel direct boot something akin to EFI, or
> BIOS, or of its own kind?
>
> As I've managed to land on a use case where
On 2023-06-26 21:20, Johannes Schauer Marin Rodrigues wrote:
> this is not a daydream and I think we have nearly all building blocks in place
> to make all of this happen very soon! Here is a summary:
>
> 1. You use `debvm-create --arch $foo` to create a filesystem image for any
>
On 2023-06-16 17:56, Antonio Terceiro wrote:
> Note that the variable where you inserted a username and password is
> calle debci_amqp_server, and was never supposed to be used for putting a
> password in plain text.
I think this is where the documentation of the --amqp option threw me
off, from
Package: debci
Version: 3.6
Severity: serious
Tags: security
X-Debbugs-Cc: Debian Security Team
Hi,
When using authentication in AMQP connections, the username and password
supplied in the --url option to amqp-consume resp. amqp-publish are
exposed in the proces list, see #1037322:
$ pgrep
Control: tag -1 fixed-upstream
On 2023-06-11 12:28, Christian Kastner wrote:
> Package: amqp-tools
> Version: 0.11.0-1
> Severity: grave
> Tags: security
> Forwarded: https://github.com/alanxz/rabbitmq-c/issues/575
>
> When passing authentication data with either --password
Package: amqp-tools
Version: 0.11.0-1
Severity: grave
Tags: security
Forwarded: https://github.com/alanxz/rabbitmq-c/issues/575
When passing authentication data with either --password or --url, the
data is exposed in the process list, where it can be seen by any user.
Example:
$ pgrep -a
control: tags -1 - moreinfo
Hi Paul,
On 2023-06-01 08:54, Paul Gevers wrote:
> Please upload hipsparse to tpu (targeting bookworm in the changelog)
> with no other changes than a changelog entry on top of what you have in
> unstable. Please use the version number 5.3.3+dfsg-2~deb12u1.
Thank you
On 2023-05-31 19:28, Adam D. Barratt wrote:
> In the versions in testing, both packages only built for amd64. In
> unstable, they have also built for arm64. Migrating the arm64 hipsparse
> binaries from unstable therefore requires migrating a version of
> rocsparse with arm64 binaries.
Oh, that's
Hi Graham,
On 2023-05-31 08:58, Graham Inggs wrote:
> Hi Christian
>
> On Sun, 28 May 2023 at 18:48, Christian Kastner wrote:
>> unblock hipsparse/5.3.3+dfsg-2
>
> The debdiff looks good to me, however the migration of
> hipsparse/5.3.3+dfsg-2 appears to be blocked b
)
+
+ -- Christian Kastner Sun, 28 May 2023 18:25:03 +0200
+
+rocrand (5.3.3-3) unstable; urgency=medium
+
+ * Upload to unstable.
+
+ -- Christian Kastner Sun, 16 Apr 2023 22:45:08 +0200
+
+rocrand (5.3.3-3~exp1) experimental; urgency=medium
+
+ * Add myself to Uploaders
+ * Fix Maintainer name
)
+
+ -- Christian Kastner Sun, 28 May 2023 17:17:36 +0200
+
hipsparse (5.3.3+dfsg-1) unstable; urgency=medium
* Initial release. (Closes: #1023092)
diff -Nru hipsparse-5.3.3+dfsg/debian/control
hipsparse-5.3.3+dfsg/debian/control
--- hipsparse-5.3.3+dfsg/debian/control 2023-01-24 11:35:25.0
Control: tags -1 - moreinfo
On 2023-05-15 22:12, Sebastian Ramacher wrote:
> Please go ahead and remove the moreinfo tag once the package is
> available in unstable.
Done (this time with the right recipients)
(re-sent, this time to the right recipients. Apologies, it's been a long
day)
On 2023-05-15 21:15, Salvatore Bonaccorso wrote:
>> +libcap2 (1:2.66-4) unstable; urgency=medium
>> +
>> + * Apply upstream patches for CVE-2023-2602, CVE-2023-2603
>> +
>> + -- Christian
bcap2-2.66/debian/changelog 2023-05-15 20:34:57.0 +0200
@@ -1,3 +1,9 @@
+libcap2 (1:2.66-4) unstable; urgency=medium
+
+ * Apply upstream patches for CVE-2023-2602, CVE-2023-2603
+
+ -- Christian Kastner Mon, 15 May 2023 20:34:57 +0200
+
libcap2 (1:2.66-3) unstable; urgency=medium
(re-sending to bug which I forgot to CC)
Hi,
On 2023-05-05 20:05, Helmut Grohne wrote:
> Also sbuild-qemu is a direct reverse dependency of vmdb2. I haven't
> looked deep there.
sbuild-qemu is just a simple wrapper around autopkgtest-build-qemu that
simplifies the image customziation process.
Control: tags -1 - moreinfo
On 2023-04-26 07:46, Paul Gevers wrote:
> Ack. I'm uncomfortable with the changes in -3, in particular the
> arch:any -> arch:all and associated lib -> shared move. I propose you
> upload a version -4 which reverts -3 for now and only adds the missing
> dependency.
Hi Paul,
On 2023-04-30 07:59, Paul Gevers wrote:
> Please go ahead with your 04_ proposal and please remove the moreinfo
> tag once the upload happened.
In -7, there was a typo that broke installability for hipcc,
specifically a version contained a second colon where a dot was expected:
> [...]
Control: tags -1 - moreinfo
Hi Paul,
On 2023-04-30 07:59, Paul Gevers wrote:
>> I may be misunderstanding something here. I interpreted your t-p-u hint
>> for the case where a fix via unstable wouldn't be possible because of
>> the dependency issue. The proposal, however would work via unstable.
Hi Paul,
On 2023-04-28 17:48, Paul Gevers wrote:
> On 28-04-2023 00:58, Christian Kastner wrote:
>> So I split that diff into 02 (patches) and 03 (NOT-patches), also
>> attached.
>
> I think you forgot to add them.
I did, sorry.
>> Would a package with just the
Control: tags -1 - moreinfo
Hi Paul,
sorry this took a while.
On 2023-04-22 13:34, Paul Gevers wrote:
> On 21-04-2023 23:43, Christian Kastner wrote:
>> The only way to do that with llvm-toolchain-15 from testing is by
>> changing the dependency libclang-rt-15-dev back to
>&g
Hi Paul,
just wanted to say sorry, this is taking a while.
On 2023-04-22 13:34, Paul Gevers wrote:
>> The only way to do that with llvm-toolchain-15 from testing is by
>> changing the dependency libclang-rt-15-dev back to
>> libclang-common-15-dev (the pre-split version).
>
> Hmm, so this
Control: tags -1 - moreinfo
Hi Paul,
On 2023-04-20 08:58, Paul Gevers wrote:
> Sorry for taking so long to respond (the moreinfo tag was still attached
> to the bug, so it didn't show up in my regular bts view, so please
> remove it when you reply).
done.
> On 16-03-2023 11:4
+
+ * Add libamdhip64-dev to Depends (Closes: #1034476)
+ * Fix Maintainer name
+ * Add myself to Uploaders
+
+ -- Christian Kastner Sun, 16 Apr 2023 13:40:58 +0200
+
+rocprim (5.3.3-3) unstable; urgency=medium
+
+ * Move cmake files to /usr/share.
+ * d/rules: drop override for debug symbols
Package: librocprim-dev
Version: 5.3.3-3
Severity: serious
librocprim-dev needs libamdhip64-dev, but this dependency is missing
from the package.
Hi Teal,
I'm no longer a maintainer of cron, but I was the one last replying to
the original report (can't believe it's been 12 years...)
On 2023-04-08 12:30, Teal Bauer wrote:
> The same Selective logging patch added a version of the logging in the
> default branch of the fork() switch, so if
Package: sbuild
Version: 0.85.2
Severity: normal
Hi josch,
Attempting to build a package with the autopkgtest-virt-podman backend
fails because of what I suspect is an issue with $HOME directory
handling. podman needs $HOME on the host to find containers, but it
defaults to
Hi Paul,
On 2023-03-16 10:31, Paul Gevers wrote:
> Control: tags -1 moreinfo On 16-03-2023 00:16, Christian Kastner
> wrote: For next time, can you please contact us earlier? We could
> have solved the earlier problems in testing-proposed-updates (in
> January), then
On 2023-03-13 18:28, Christian Kastner wrote:
> [ Impact ]
> The new versions are in far better shape: they've catched missing
> dependencies, added patches, improved the build process, etc.
Apologies, I was only thinking of the more recent releases.
Revision -2 fixed an RC bug i
Hi,
On 2023-02-06 17:33, Shengjing Zhu wrote:
> +--+
> | Update chroot
> |
> +--+
:51.0 +0100
@@ -1,3 +1,78 @@
+rocm-hipamd (5.2.3-6) unstable; urgency=medium
+
+ * Reduce arch to amd64, arm64, ppc64el
+ * libamdhip64-5: Add dependency on libamd-comgr2 (Closes: #1032677)
+ * Add myself to Uploaders
+ * Fix Maintainer (same list, different name)
+
+ -- Christian Kastner Fri
Package: libamdhip64-5
Version: 5.2.3-5
Severity: serious
When working on rocrand, I noticed that the rocrand libraries did not
work without libamd-comgr2 installed.
Cordell Bloor pointed out that libamd-comgr2 is essential to any library
that contains GPU kernels, and the calls are likely to be
(debian-ai, apologies for re-sending, I hit the wrong reply button.)
On 2023-03-08 18:21, Simon McVittie wrote:
> There is *a* version of llvm-toolchain-15 in bookworm, version 1:15.0.6-4,
> which is used by the rocm-hipamd_5.2.3-1 and mesa_22.3.3-1 in bookworm.
> I'm not suggesting that
Control: tags -1 + patch
An MR has been filed under
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/219
Package: autopkgtest
Version: 5.28
Severity: normal
When supplying autopkgtest with built binaries (-B) and using the
autopkgtest-virt-podman server, a umask of 0027 will lead to an early
failure, aborting the test.
I'll file an MR fixing this shortly.
Steps to reproduce:
# Assuming .debs
Hi,
On 2019-11-11 00:01, Johannes Schauer wrote:
>> Johannes, have you found a solution in the meanwhile?
I just stumbled over this bug.
Package sbuild-qemu has the 'sbuild-qemu-update' utility which
dist-upgrades images created by autopkgtest-build-qemu.
There's also an sbuild-qemu-boot
Hi Jakub,
On 2023-01-31 16:12, Jakub Wilk wrote:
> * Christian Kastner , 2020-08-14 10:58:
> Most of them build-depend on python3-sphinx, which depends on
> python3-pygments.
that explains it. I should have checked the man page.
> In my experience, you almost always want --old.
Ind
CPU with their optimizations, and they usually
come with massive test suites.
> On Wed, Mar 1, 2023, at 07:09, Christian Kastner wrote:
>>> Users seem to be relying on this (as I was just asked about policies
>>> when microcode updates are updated/backported).
>
> Really, you
Hi,
On 2022-07-08 15:36, Michael Prokop wrote:
> https://wiki.debian.org/Microcode#Microcode_update_support_for_current_and_older_Debian_releases:
>
> | Debian 11, codename "Bullseye" is supported, and will receive
> | updates both through the bullseye-backports official backports
> | repository
On 2023-02-19 12:16, Cordell Bloor wrote:
> I've prepared the rocr-runtime package for upload. I tested it with
> several of the math libraries on Debian Bookworm and Ubuntu Lunar. This
> patch has also gone through significant testing upstream.
LGTM, changes are minimal and targeted fixes, so in
1 - 100 of 889 matches
Mail list logo
