On Sun, Feb 4, 2024, at 13:04, Pushkar Kulkarni wrote:
> Do you plan on doing a new upstream release?
Yes, that's what I plan to do tomorrow in addition to uploading a new Debian
package.
-- Joel
I hope to find time to fix this tomorrow.
-- Joel
Package: linux-image-6.1.0-15-amd64
Version: linux-image-6.1.0-17-amd64
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
: Error: Optimizer error: too much on the stack
This makes the lyskom-elisp-client package uninstallable.
-- Joel
make some workaround.
-- Joel
Package: wx3.2-examples
Version: 3.2.2+dfsg-2
Severity: normal
X-Debbugs-Cc: j.o.elpub...@gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Tried to compile examples to understand wx-config flags.
*
This bug was fixed in kernel version 6.1.33 by commit
e8631d84c01ece34670af0d300a6f88d86d12f70. I compiled from source and confirm
that the problem is indeed fixed in 6.1.33.
The root of the problem is that the "family" in the SMBIOS is "Lenovo
ThinkSystem HR330A/HR350A" not "eMAG", so a
Upon further investigation, this problem appears to be related to the kernel
version (6.1.0-9-arm64).
After booting into my new Debian 12 installation, efibootmgr hung with no
output when I attempted to delete a boot entry (`sudo efibootmgr -Bb 0006`). I
downloaded the Bullseye kernel deb
Package: installation-reports
Severity: important
Boot method: USB
Image version:
https://cdimage.debian.org/debian-cd/current/arm64/bt-cd/debian-12.0.0-arm64-netinst.iso.torrent
Date: 2023-06-17
Machine: Lenovo HR350A server
Partitions:
Filesystem Type 1K-blocksUsed Available Use%
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: affects -1 + src:ccache
Please unblock package ccache
[ Reason ]
Ccache versions 4.7 - 4.7.4 by default enable a feature called the inode cache
which shares information between
s done for portability reasons since the previous solution
relied on pthread mutex behavior that is different in FreeBSD.
-- Joel
ve never seen that
workaround before. So IIUC this suggests using a version like
4.8-2+really4.7.5? Are there other ways since it says "e.g."?
-- Joel
getting stuck.
For reference, I'm attaching the targeted fix I would like to make.
-- Joel
diff -Nru ccache-4.7.4/LICENSE.adoc ccache-4.7.5/LICENSE.adoc
--- ccache-4.7.4/LICENSE.adoc 2022-11-21 19:53:32.0 +0100
+++ ccache-4.7.5/LICENSE.adoc 2023-03-20 20:47:12.0 +0100
@@ -35,7 +35,7
Package: gcc-riscv64-unknown-elf
Version: 12.1.0-7+11
Severity: important
File: /usr/bin/riscv64-unknown-elf-g++
Hello Keith,
I am using the riscv elf toolchain to build a C++ program. It
tries to look for headers here:
$ echo | riscv64-unknown-elf-g++ -E -Wp,-v -
ignoring nonexistent directory
directory,
which is the case for you), or to disable the inode cache by setting
inode_cache = false
in the config file.
Regards,
Joel
r/cache/pbuilder/ccache/ccache.conf
should do it.
Regards,
Joel
the pbuilder chroot and
then publish the created log file?
Regards,
Joel
On Mon, Oct 24, 2022, at 13:40, Raphaël Halimi wrote:
> I also tested it, it's broken too.
Thanks.
Can you give me more some detailed hints on how I can reproduce the issue?
Regards,
Joel
Hi Raphaël,
Could you test if ccache 4.7.1-1 improves the situation?
Regards,
Joel
vuan.dev/aitor_czr/libubus
https://git.devuan.dev/aitor_czr/simple-netaid-gtk
Thank you
--
Joel Roth
Package: cups-browsed
Version: 1.28.15-1
Severity: normal
Dear Maintainer,
We include an apparmor profile for cups_browsed that implicitly denies the
SYS_NICE capability. This capability isn't actually needed by cups-browsed,
but is tested as part of startup.
I suggest we add a rule to
Package: isync
Version: 1.3.0-2.2+deb11u1
Severity: important
Dear Maintainer,
* What led up to the situation?
After executing mbysinc I get the error in the subject
* What exactly did you do (or not do) that was effective (or
ineffective)?
executed mbsync
* What
Source: unbound
Version: 1.13.1-1
Severity: normal
Dear Maintainer,
I've been noticing segfaults in unbound on an internet facing server
running 1.13.1-1 on Debian stable. When hunting around for similar bug
reports I noticed there's since been a few new releases.
I took a stab at updating the
Package: sparse
Version: 0.6.4-1+b1
Severity: normal
Dear Maintainer,
Sparse in testing depends on gcc-10. As the kernel has moved to depend
on gcc-11, sparse is the only package on my system pulling in the older
compiler as a dependency.
Perhaps it could be made to depend on simply 'gcc', or
Thanks for the clarification, and I will try those steps. I have never
reconfigured my networking beyond the default settings, so could this be an
upgrade issue?
--
Joel Cross
j...@kazbak.co.uk
On Mon, 18 Oct 2021, at 11:18 PM, Michael Biebl wrote:
> Am 18.10.2021 um 19:51 schrieb J
$ cat /etc/network/interfaces
source-directory /etc/network/interfaces.d
$ ls /etc/network/interfaces.d
setup
$ cat /etc/network/interfaces.d/setup
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated
Thanks Michael. To whom it may concern, I should have mentioned that I use
network manager to control my wireless networks - presumably this uses ifupdown
under the hood, but I'm not 100% on that
--
Joel Cross
j...@kazbak.co.uk
On Mon, 18 Oct 2021, at 10:59 AM, Michael Biebl wrote
Package: installation-reports
Severity: important
Boot method: network
Image version: https://d-i.debian.org/daily-images/armhf/daily/device-tree/
20210719-00:04:35
Date: 2021-07-19
Machine: ASPEED AST2600 EVB
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below),
The GIMP team have confirmed that image/x-xcf is the correct mime.
https://www.mail-archive.com/gimp-developer-list%40gnome.org/msg09755.html
On Fri, Jul 16, 2021 at 1:24 PM Joel Hockey wrote:
> Package: media-types
> Version: ?
> Severity: normal
>
> Dear Maintainer,
>
>
Package: media-types
Version: ?
Severity: normal
Dear Maintainer,
Would it be possible to change the xcf file association in
/etc/mime.types from application/x-xcf to image/x-xcf?
GIMP uses the xcf file extension by default, and registers to handle
mime type image/x-xcf in its gimp.desktop
t.20200923.ec349ff4-3) attached.
Regards,
Joel
lyskom-elisp-client.debdiff
Description: Binary data
ated (via the alternatives mechanism)
after ccache's postinst script has run, so ccache currently has no way of
detecting that compiler name. A workaround is to run
/usr/sbin/update-ccache-symlinks manually to install the symlink.
This is essentially the same bug as #632779.
Regards,
Joel
Package: gcc-riscv64-unknown-elf
Version: 8.3.0.2019.08+dfsg-1
Severity: normal
Dear Maintainer,
I am trying to use the riscv toolchain to build a bare metal
application. It appears to have a broken stdint.h:
$ cat test.c
#include
$ riscv64-unknown-elf-gcc -E -march=rv32i -mabi=ilp32
Package: openconnect
Version: 8.10-2+b1
Severity: important
Dear Maintainer,
libopenconnect depends on libtss2-esys0 which has been renamed to
libtss2-esys-3.0.2-0 (bug #974837).
In testing, when libtss2-esys0 is replaced with the renamed package
openconnect will be removed.
I believe the fix
I think this is fixed upstream in 2.1.2; see
https://github.com/adrianlopezroche/fdupes/commit/c0dd064bb02b5496e1ef51fcc9eed11dd08b6268
EN_CFLAGS, EMCC_CLOSURE_ARGS) maybe also need
special treatment?
Regards,
Joel
On Thu, 15 Oct 2020 at 12:39, Jonas Smedegaard wrote:
>
> Package: ccache
> Version: 3.7.12-1
> Severity: normal
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> The emcc command part of em
I figured that would be the case; it’s a known upstream issue. Thanks for
confirming that I didn’t miss something obvious.
Should we mark the control file as breaks kernel < 590? Maybe just for
libcuda1 (not quite accurate, but has a result closer to the observed issue)?
Or just wait until
Package: nvidia-kernel-dkms
Version: 455.38-1
Severity: normal
Thanks for the recent 450.80.02 update! I now can run the Nvidia driver with
the 5.9 kernel.
However, I cannot load the nvidia-uvm kernel module. When I try, the error
messages logged in dmesg are:
nvidia_uvm: Unknown symbol
Thanks for the new version! But it seems to introduce a regression.
After installing it on my bullseye box, I couldn't run CUDA programs
anymore. Normally, CUDA requires the nvidia-uvm module to be loaded.
However, loading the uvm module reports the following errors in dmesg:
nvidia_uvm:
Package: base
Severity: important
Dear Maintainer,
After a recent routine update to my Debian installation, my wireless interface
disappeared and my system was unable to do anything related to wifi.
When running `iwconfig` all of my interfaces said "no wireless extensions"
Neither using an
=medium
+
+ * Non-maintainer upload.
+ * Fix HID extractBits for big-endian systems (Closes: #963201)
+
+ -- Joel Ray Holveck Mon, 28 Sep 2020 14:32:08 -0700
+
flightgear (1:2020.1.3+dfsg-1) unstable; urgency=medium
* New upstream version 2020.1.3+dfsg
diff -Nru flightgear-2020.1.3+dfsg
trying to integrate the
dependency that the upstream project (Nix) seems to favor the most.
Thanks,
--
Joel Rivera
[1]: https://tracker.debian.org/pkg/editline
[2]: https://tracker.debian.org/pkg/libedit
[3]: https://github.com/troglobit/editline
[4]: https://tracker.debian.org/pkg/nix
[5]: https
knowledge is way too bad to find the problem in the code. Sorry :)
Thank you
Joel K.
-- System Information:
Debian Release: 9.13
APT prefers oldstable-updates
APT policy: (990, 'oldstable-updates'), (990, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-13-amd64 (SMP w/4 CPU cor
resolved
the issue for me.
Joel
On 2020-08-05 09:56, Andreas Beckmann wrote:
On 8/5/20 5:30 PM, Joel Johnson wrote:
Thanks, I'll comment out the additional blacklist entries and test
with
that package installed. Those lines aren't harmful in any other way
that
I see, but just unexpected from your original response
ows for a broken bumblebee-nvidia installation
nvidia-kernel-dkms + bumblebee-nvidia
but we need at least the following additional driver components:
* xserver-xorg-video-nvidia
* nvidia-driver-libs
Joel, if you install the nvidia-driver metapackage, everything should
be
fine for you.
Tha
On 2020-08-03 15:13, Andreas Beckmann wrote:
On 8/3/20 5:00 PM, Joel Johnson wrote:
On 2020-07-31 03:03, Andreas Beckmann wrote:
While this additional blacklisting sounds technically correct, I'm
curious why the driver gets loaded automatically in a bumblebee
setup.
$(update-glx --display
On 2020-07-31 03:03, Andreas Beckmann wrote:
On 7/30/20 6:41 PM, Joel Johnson wrote:
With more recent nvidia drivers and Debian packages of
nvidia-kernel-support, the nvidia-modeset and nvidia-drm modules are
attempted to be loaded. This causes the driver to always be loaded.
Locally I've added
Package: bumblebee
Version: 3.2.1-22
Severity: important
With more recent nvidia drivers and Debian packages of
nvidia-kernel-support, the nvidia-modeset and nvidia-drm modules are
attempted to be loaded. This causes the driver to always be loaded.
Locally I've added those two modules to the
re is some general information on how to debug caching problems:
https://ccache.dev/manual/3.7.10.html#_cache_debugging
Regards,
Joel
On Sat, 18 Jul 2020 at 17:09, Christian Marillat wrote:
>
> Package: ccache
> Version: 3.7.10-1
> Severity: normal
>
> Dear Maintainer,
>
>
systems, you need to install the python3-venv
package using the following command.
apt-get install python3-venv
You may need to use sudo with that command. After installing the python3-venv
package, recreate your virtual environment.
Failing command: ['/home/joel/.local/pipx/venvs/poetry/bin
Thanks, I created an identical patch before seeing your update, tested
and confirmed that building as a module is loaded during boot. I tried
to submit a merge request to the repo, but don't have access to push
branches, so I've also attached the resulting patch here.
Joel
From
that it is not working as of that 5.2 build.
Thanks,
Joel
If I can give a bit more information on this bug, since it affects me too...
Every day, at around the same time, I notice my computer heating up, because
the unattended-upgrades process is running. This happens even though I have
masked the service in systemd. Attempting to kill the process
Package: software-properties-common
Version: 0.96.20.2-2.1
Severity: important
Dear Maintainer,
I have a fresh Bullseye install, and am noticing that the security updates URL
as defined in my sources.list is wrong and results in a 404. Here are the
offending lines:
deb
I think that it's time to remove python-sqlite from Debian: it's a
module for the obsolete SQLite 2 API and there's (understandably) no
upstream activity.
I think that it's time to remove python-pysqlite2 from Debian: Python
has had support for SQLite 3 since version 2.5 and there is
(understandably) no upstream activity for the Python wrapper.
Package: wnpp
Severity: normal
thanks
Package: xserver-xorg-video-nvidia
Version: 440.44-1
Severity: important
Tags: upstream
Xorg startup fails to find any devices. This started happening when I
upgraded my motherboard & CPU. The previous motherboard was Asrock X399
Taichi, and the new motherboard is Asrock TRX40 Creator. All other
ent specifies non-existent project:
device/google/marlin
Could you perhaps share more or less exactly which commands to use to get
the
AOSP source code and build it to reproduce the problem?
Also, could you report the bug in ccache's GitHub project
(https://github.com/ccache/ccache)?
Thanks,
-- Joel
with this situation?
-- Joel
guest!
--
Joel Cross
out
that the systemd initially launches as root and then setuid to nsd. The
workaround was ensuring that the base config and all included data files
are owned by root, but perhaps there's a cleaner way to support this.
Joel
On 2019-09-03 12:39, Markus Schade wrote:
Hi Joel,
thanks
y. Notably, the upstream unit file doesn't list
CAP_CHOWN in the bounding set, is there a Debian specific rationale for
needing to include it?
Thanks,
Joel
[1] https://salsa.debian.org/dns-team/nsd/commit/8a6039c
ically by looking in /usr/lib/gcc/*, finding a directory called 9
and then finding /usr/bin/gcc-9. It seems to work for me when installing gcc-9
in unstable at least.
-- Joel
On Sun, 14 Jul 2019, at 12:37 PM, Robie Basak wrote:
> [I'm not the maintainer; just driving by]
>
> On Mon, Mar 25, 2019 at 01:14:34PM +0000, Joel Cross wrote:
> > I noticed today that while the python3-pytest package works fine when
> > invoked
> > as `python3 -m p
I have added a patch to the Ubuntu version of the bug (I believe Ubuntu is
considered the upstream for this package). Hopefully they'll merge it soon,
then we can pull the changes into Debian.
Package: command-not-found
Version: 18.04.5-1
Severity: important
Dear Maintainer,
The latest version of the command-not-found/zsh combination is failing silently
whenever the command-not-found-handler does not match. To reproduce:
$ zsh --no-rcs
localhost% source /etc/zsh_command_not_found
Source: pytest
Severity: normal
Dear Maintainer,
I noticed today that while the python3-pytest package works fine when invoked
as `python3 -m pytest`, it does not provide a binary, and the only binary
provided is as part of the `python-pytest` package which is built on Python 2.
For proper
Package: installation-reports
Boot method: microSD card
Image version:
http://ftp.debian.org/debian/dists/testing/main/installer-armhf/current/images/hd-media/hd-media.tar.gz
Date: 2019-02-22T20:57:53-07:00
Machine: ClearFog Base
Processor: Marvell ARMADA A388 ARM A9
Memory: 1GB
Partitions:
e 0
then
echo "$PROGNAME: This script must be run using a Korn or Bash shell."
exit 7
fi
set -e
Thanks,
Joel
Package: wnpp
Severity: wishlist
Owner: Joel Cross
* Package name: python-pytest-lazy-fixture
Version : 0.5.1
Upstream Author : Marsel Zaripov
* URL : https://github.com/tvorog/pytest-lazy-fixture
* License : MIT/Expat
Programming Lang: Python
Description
but
> I decided to send this friendly ping anyway and see if you had the
> chance to solve the issues I pointed out below.
Hi Sergio,
Well, I've finally got there! Please take a look at the latest upload
(https://mentors.debian.net/package/python-cerberus) and let me know what you
think.
With the upcoming removal of Python 3.6 from the repository, this backport no
longer seems necessary. I will close the bug report now.
I am a Python developer and many of my projects are still running inside Python
3.6 virtualenvs. Might it be a bit premature to remove the 3.6 distutils module
while Python 3.6 is still available and supported within Debian?
As an aside, I can confirm that downgrading to 3.7.1-1 (current buster
Package: xfce4-pulseaudio-plugin
Version: 0.4.1-1
Severity: important
Dear Maintainer,
Upon upgrading my XFCE Debian system from stable to testing I am having
problems with this XFCE plugin.
When the "Show notifications when volume changes" option is enabled. Upon
volume changes the plugin
Source: json-editor.js
Severity: wishlist
The latest version of this library/tool is 1.2. Please can we package for the
latest version.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture:
Package: wnpp
Severity: wishlist
Owner: Joel Cross
* Package name: python-pipenv-pipes
Version : 0.7.1
Upstream Author : Gui Talarico
* URL : https://github.com/gtalarico/pipenv-pipes/
* License : MIT/Expat
Programming Lang: Python
Description
> > Output of the command `pkcon offline-status` is as follows:
> > Status: Failed
> > ErrorCode:failed-initialization
> [...]
>
> Could you please retry again? Is this fixed? I tried today and it was
> working for me with the current version in unstable (1.1.10-1)
>
This hasn't been a
Hi Sergio,
I have fixed this by switching the watch file to use the GitHub URL instead.
Would you mind reviewing the latest package and uploading?
-Joel
ess it was configured
> > in advance.
> > Just like the initramfs can't know which one to resume /from/ unless it
> > knew which one
> > it resumed to.
> >
>
> Joel, can you please tell us,
> - which partition you have configured in /etc/initramfs-tools/
On Thu, 5 Jul 2018, at 1:17 PM, Michael Biebl wrote:
> Am 05.07.2018 um 13:46 schrieb Joel Cross:
> > Yes, I can confirm, after downgrading to 238-5 (I also downgraded the
> > libsystemd0, udev and libudev0 packages) that I no longer experience the
> > issue.
>
>
On Wed, 4 Jul 2018, at 3:22 PM, Michael Biebl wrote:
> Am 26.06.2018 um 12:54 schrieb Joel Cross:
> > Package: systemd
> > Version: 239-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > Over the last few days (since my last system upgrade) I a
Source: cookiecutter
Severity: normal
Dear Maintainer,
Thanks for building a Python 3 version of this package. However, when
attempting to install the cookiecutter binary, I noticed it still depends on
the Python 2 library.
If memory serves correctly, it is possible to change the 'Depends' line
On Wed, 27 Jun 2018, at 3:47 PM, Michael Biebl wrote:
> Am 27.06.2018 um 16:03 schrieb Michael Biebl:
> > Joel, can you execute "/lib/systemd/systemd-sleep hibernate" directly
> > and see what happens then.
>
> Make that
>
> SYSTEMD_LOG_LEVEL=debug
have any hooks in /lib/systemd/system-sleep/ ?
> If so, could you temporarily move them away?
I had two hooks: hdparm and unattended-upgrades. Moving them away didn't help.
> Could you provide a journalctl -alb log from such a failed resume + a
> separate output of dmesg.
I have attached both logs.
-Joel
dmesg.log.gz
Description: application/gzip
journalctl--alb.log.gz
Description: application/gzip
On Tue, 26 Jun 2018, at 12:12 PM, Michael Biebl wrote:
> Which backend have you configured in pm-hibernate? the in-kernel
> hibernate mechanism, Tux0nIce, uswsusp?
Sorry, I have no idea how to find that out. I do not recall ever configuring a
pm-hibernate backend, so I would guess whichever is
_
self.widget = self.create_widget()
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1480, in
create_widget
self.terminal.set_cursor_blinks(True)
AttributeError: 'Terminal' object has no attribute 'set_cursor_blinks'
-- Package-specific info:
** Environ
suceeding (e.g. autoconf, automake debhelper, etc.).
Building initial module for 4.16.0-0.bpo.2-amd64
/var/lib/dkms/zfs/0.7.9/build/configure: line 13069: dpkg-architecture:
command not found
Joel
Control: tags -1 + patch
I am attaching a debdiff to add Python 3 support, as well as updating the
Debhelper and standards levels. This debdiff should be built against the latest
git master (which is ahead of the latest built package).
--
Joel Cross
j...@kazbak.co.uk
I've been working on a patch to add Python 3 support to this package. As soon
as it's ready I'll attach it here.
Dear reviewers,
I have uploaded a new version of json-editor.js, which addresses many of
Paolo's concerns. It can be downloaded from
https://mentors.debian.net/package/json-editor.js, and the git repository is
available at https://salsa.debian.org/joelcross-guest/json-editor.js.
-
Joel Cross
Hi Paolo,
Thanks for taking the time to review my package. Just to let you know, I am
working on the things you mentioned, but have hit a roadblock when it comes to
actually joining the js-team.
> 3. If you wish to maintain this package within this team, I'd suggest that
> you join the team !
On Mon, 30 Apr 2018, at 6:21 PM, Joel Cross wrote:
> > Ah! Found it. It's listed in the "setup.py" file. Hmm... I wonder if
> > that's a problem, because no other file contains any kind of copyright
> > notice, and there's no LICENSE file. I'd definitely file a bug
Package: python3-aiohttp
Version: 3.0.1-1
Severity: important
Dear Maintainer,
On my system, attempting to use aiohttp results in an error like the following:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/aiohttp/web_protocol.py", line 376, in
start
resp = await
Package: wnpp
Severity: wishlist
Owner: Joel Cross <joel+debb...@kazbak.co.uk>
* Package name: python-typeguard
Version : 2.1.4
Upstream Author : Alex Grönholm <alex.gronh...@nextday.fi>
* URL : https://github.com/agronholm/typeguard
* License
Package: wnpp
Severity: wishlist
Owner: Joel Cross <joel+debb...@kazbak.co.uk>
* Package name: python-pygtrie
Version : 2.2
Upstream Author : Michal Nazarewicz <min...@mina86.com>
* URL : https://github.com/google/pygtrie
* License : Apache 2.0
sed a new
version, as no code has actually changed. I was wondering if you could help me
with regards to packaging based on a specific upstream Git commit rather than a
release version, and how that works with the git-buildpackage flow (if it's
even allowed/recommended).
-Joel
I have updated the package to the latest version 1.0.0. The new package may be
downloaded using the following command:
dget -x
https://mentors.debian.net/debian/pool/main/p/python-base58/python-base58_1.0.0-1.dsc
> Hm, from what I've seen the package is pretty much the same as it was
> when you submitted it. I'm using the following repository:
>
> https://salsa.debian.org/python-team/modules/python-cerberus
>
> And I don't see the fixes I asked you to do. Maybe I'm looking at the
> wrong place?
1 - 100 of 617 matches
Mail list logo
