On 2023/5/9 04:20, Jeremy Sowden wrote:
> Thanks for the offer. :) I've cloned the osquery repo and it appears to
> use the C++ Linenoise NG fork:
No problem ;) It uses the -ng fork, but the fork's repo was archived in 2017,
which leads me back to the original. And
> which is what I started
Package: basilisk2
Version: 0.9.20220710-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
0m35.2s ERROR: FAIL: Broken symlinks:
Control: tag -1 pending
Hi Adit,
On 2023-04-22 09:05, Adit Sahasrabudhe wrote:
> And I tested the patch at this link and it worked.
>
> https://sourceware.org/git/?p=binutils-gdb.git;a=patch;h=b3eff3e15576229af9bae026c5c23ee694b90389
Many thanks for finding the patch and trying it out. I can
Package: libhiprand-dev
Version: 5.3.3-3
Severity: normal
X-Debbugs-Cc: c...@slerp.xyz
Dear Maintainer,
The libhiprand-dev package is missing a dependency on libamdhip64-dev
and librocrand-dev. This can be illustrated with this sample:
apt-get -y update
apt-get -y install
Hi Dmitry
I like your idea, and I would like to help you, please reply to the
place here:
https://github.com/JonMagon/KDiskMark/issues/110#issuecomment-1539060910
(I have chosen to reply there instead of mentors.d.n for the simple
reason that on mentors.d.n a new upload overrides
the old
Package: cpl-plugin-xshoo-calib
Version: 3.5.3+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the
Package: libwayland-server0
Version: 1.21.0-1
Severity: important
File: libwayland-server
X-Debbugs-Cc: sm...@smurf.noris.de
I don't like when my session dies.
This happens occasionally (every couple of days) when I resume from screen lock
and my monitors wake up from power saving.
The core
Package: librocrand-dev
Version: 5.3.3-1
Severity: normal
X-Debbugs-Cc: c...@slerp.xyz
Dear Maintainer,
The librocrand-dev package is missing a dependency on libamdhip64-dev.
# What was done?
In a fresh Bookworm container,
apt-get -y update
apt-get -y install build-essential cmake
tags 998834 + patch
thanks
https://bugzilla.mindrot.org/attachment.cgi?id=3591=diff==1=raw
has a patch for this
Package: raspi-firmware
Version: 1.20220830+ds-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):
The later versions of Nuitka with less problems didn't make it to unstable
yet, they would only give an error. However, I
expect to make an upload in the next 2 weeks that will then close this bug.
Yours,
Kay
Package: nuitka
Version: 1.3.5+ds-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: tipos...@tiscali.it
Dear Maintainer,
this is what happens when I tried to run nuitka on localslackirc
nuitka3 --standalone localslackirc
Nuitka-Options:INFO: Used command
Dear Maintainer,
with the bookworm kernel 6.1.0-8, which has been available since yesterday, the
problem is apparently solved:
"intel-eth-pci :00:1d.1 eno1: Link is Up - 1Gbps/Full - flow control rx/tx"
Thank you very much.
Best regards
Heinrich
Package: emacs-common
Version: 1:28.2+1-14
Severity: serious
There are some elpa packages from bullseye that won't be in bookworm and
that are incompatible with emacs 28, i.e. upgrading emacs will fail if
these packages are still installed.
Therefore emacs-common needs to add Breaks against them
Upgrading to bullseye-backports version 252.5-2~bpo11+1 fixes the issue.
Package: jed-common
Version: 1:0.99.20~pre.178+dfsg-2
Severity: serious
jed-common fails to upgrade from 1:0.99.20~pre.178+dfsg-1 to
1:0.99.20~pre.178+dfsg-2 for me as follows:
Preparing to unpack .../4-jed-common_1%3a0.99.20~pre.178+dfsg-2_all.deb ...
Unpacking jed-common
On 2023-05-09, Sebastiaan Couwenberg wrote:
> On 5/9/23 05:47, Sebastiaan Couwenberg wrote:
>> On 5/8/23 22:43, Vagrant Cascadian wrote:
>>> On 2023-05-08, Sebastiaan Couwenberg wrote:
On 5/8/23 02:07, Vagrant Cascadian wrote:
> The attached patch fixes this by not touching these files
101 - 117 of 117 matches
Mail list logo
