On Tue, 27 May 2025 16:53:27 +0100 Ahmad Khalifa wrote:
> Hi, I tried reproducing this on an amd64 machine, but I don't get the
> same results as your i686.
I don’t reproduce it either. I use wine32 on a daily basis, with many different
software, and I don’t think I have ever seen massive memory
Le Wed, May 28, 2025 at 08:53:21AM +0200, Stephen Kitt a écrit :
> The goal is still to have debian/* work as-is for both wine and
> wine-development. (…)
wine-development got removed from Debian,
cf. https://bugs.debian.org/1103851
So maybe it is no longer useful to rely on a template and a gene
Le Thu, 22 May 2025 20:11:30 +0200,
Santiago Vila a écrit :
> The relevant documentation is here:
>
> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable
>
> In summary: an updated package for bookworm would have version
> 6.8.0.105+dfsg-3.3+deb12u1 and would be base
Le Thu, 22 May 2025 17:11:56 +,
Santiago Vila a écrit :
> During a rebuild of all packages in bookworm, your package failed to build:
>
> Note: This was fixed in commit [d00f352] and that's why I'm using closed
> with the trixie/sid version, but packages in bookworm must still build
> in boo
Package: fail2ban
Version: 1.1.0-7
Severity: grave
Since we upgraded a server to trixie, fail2ban completely fails to
start:
root@submit-01:~# /usr/bin/fail2ban-server -xf start
Server ready
root@submit-01:~# echo $?
255
What's confusing is it doesn't actually show the error message on
startup.
Control: tag -1 pending
Hello,
Bug #1103514 in golang-github-proglottis-gpgme 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:
https://salsa.debian.org/go-team/packages/golang-github-pr
Control: reassign -1 src:dmarc-cat 0.15.0-1
On 2025-04-18 15:13:21, Adrian Bunk wrote:
> Package: golang-github-proglottis-gpgme-dev
> Tags: ftbfs
> Control: affects -1 src:dmarc-cat
[...]
> github.com/proglottis/gpgme: exec: "pkg-config": executable file not found in
> $PATH
... but but... pk
Le Wed, 2 Apr 2025 08:20:51 +0200,
Helmut Grohne a écrit :
> (…) mono-dbg still needs to declare Breaks+Replaces to
> facilitate upgrades from trixie and from bookworm.
This part is the one I don’t get. What changed from the Bookworm build that
warrants a conflict between these packages now, but
user debian-rele...@lists.debian.org
usertag 1100699 + bsp-2025-03-ca-montreal
thank you
On 2025-03-17 15:48:56, Vincent Lefevre wrote:
> Package: screen
> Version: 4.9.1-1
> Severity: grave
> Justification: user securi
On 2025-03-29 02:38:26, Vincent Lefevre wrote:
[...]
> I don't know what you mean by that, but there should be a HOWTO
> to tell users how to switch from screen to tmux. In particular,
> each user may have his own .screenrc file, so that a default
> profile might not be very useful. The most comp
Control: user debian-rele...@lists.debian.org
Control: usertag 1068502 + bsp-2025-03-ca-montreal
Control: block 1068502 by 1101522
Control: tags 1068502 +pending
On 2025-03-24 10:08:37, Colin Watson wrote:
> On Fri, Feb 14, 2025 at 09:46:10PM +0100, Pau
user debian-rele...@lists.debian.org
usertag 1098454 + bsp-2025-03-ca-montreal
severity 1098454 normal
Hi,
I don't believe RFP bugs *can*be "serious", according to the fine
manual, that is reserved for bugs that are:
> is a severe violation of Debian policy (roughly, it violates a "must"
> or "r
Control: tags -1 +patch
Control: forwarded -1
https://salsa.debian.org/webmaster-team/packages/-/merge_requests/16
Control: user debian-rele...@lists.debian.org
Control: usertag 1098454 + bsp-2025-03-ca-montreal
On 2024-04-09 17:25:26, Pierre-Elliott Bécue wrote:
> Package: www.debian.org
> Sever
On 2025-03-27 12:13:04, Nicholas D Steeves wrote:
> Hi Antoine!
>
> Thank you for filing this bug, especially because I hadn't yet had the
> chance to verify successful migration to trixie.
Hi!
You're welcome!
> P.S. I'm delighted to hear that you're using
Package: syncthingtray
Version: 1.5.4-1
Severity: grave
Hi!
Syncthingtray doesn't start anymore on trixie:
anarcat@angela:~> syncthingtray
Info: Single instance application ID: Syncthing Tray-Martchus-1000
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Le Wed, 26 Mar 2025 16:45:00 +0100,
Luca Leonardo Scorcia a écrit :
> as another, simpler solution, a two-line fix for the issue has been merged
> upstream:
> https://gitlab.winehq.org/mono/mono/-/commit/cf37d8943fe5118fbfcea86149ad5b7b2d244103
> . I have built a debian backports package for book
I prepared a fix on Salsa:
https://salsa.debian.org/dotnet-team/mono/-/commit/ec3babe88
As usual, I could only test it on amd64 (nothing broke there) so it would be
nice to get a confirmation it has the expected effect on armel too.
pgpdnuelqBitZ.pgp
Description: Signature digitale OpenPGP
I pushed a change to debian/rules that should do the trick:
https://salsa.debian.org/dotnet-team/mono/-/commit/6b899c0e0
As I have no easy access to armel hardware right now, would you be
willing to give a try to building mono from the current master branch
on Salsa, and report if it does indeed f
Package: googler
Version: 4.3.13-1
Followup-For: Bug #965067
This issue has returned and it doesn't look like googler works at all
in trixie right now. wondering if there are any alternatives out there.
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (
Hi,
On 2/11/25 12:41, Vincent Lefevre wrote:
I'm also wondering about the current status of this bug. After
more than one year, there haven't been any comments.
Sorry for not being of great help on this, but just for information, it
has been also one year since
I'm holding it's upgrade:
##
Control: severity -1 normal
On 2025-02-09 15:37:06, Antoine Beaupré wrote:
> On 2025-02-09 15:35:38, Antoine Beaupré wrote:
>
> [...]
>
>> I'm a bit at a loss here, not sure where to go next.
>
> Oh, and also, there's this upstream bug:
>
> https://github.
Control: notfound -1 0.9.7-1+b3
Downgrading to the bookworm version in sid seems to workaround the
issue.
Also, triggering a backtrace with SIGQUIT (C-\) shows the hang is
somewhere in the standard library.
Here it is on -help, for example:
^\SIGQUIT: quit
PC=0x477203 m=0 sigcode=128
goroutine
On 2025-02-09 15:35:38, Antoine Beaupré wrote:
[...]
> I'm a bit at a loss here, not sure where to go next.
Oh, and also, there's this upstream bug:
https://github.com/xorpaul/g10k/issues/230
Not sure it's related, but i'll ping there.
--
Work expands so as to fill
Package: golang-1.23-src
Version: 1.23.5-1
Severity: serious
I'm trying to rebuild g10k in sid, and it fails:
golang-1.23-go : Depends: golang-1.23-src (>= 1.23.6-1) but it is not
installable
golang-src : Depends: golang-1.23-src but it is not installable
The g10k build-dep is simply `golang-
On 2025-01-19 10:14:06, David Prévot wrote:
> This package hasn’t seen an upstream release (nor commit) for more than
> eight years, and has no dependencies in Debian. Given how PHP has
> changed in the mean time, I doubt it’s even still working. Let’s not
> release Trixie with a useless and abando
Control: reassign -1 openstack-clients
On 2025-01-24 12:44:22, Thomas Goirand wrote:
> On 1/24/25 10:52, Riccardo Coccioli wrote:
>> Hi,
>>
>> But this bug is also not related to Cumin in any way. Cumin doesn't have
>> a dependency on python-eventlet nor python3-trio, which are clearly
>> the c
Control: reassign -1 openstack-clients
On 2025-01-22 15:30:43, Antoine Beaupré wrote:
> Control: reassign -1 python3-keystoneauth1
> Control: affects -1 cumin
>
> I've struggled to get a backtrace from cumin because it catches all
> exceptions in its main() function. But by r
Control: reassign -1 python3-keystoneauth1
Control: affects -1 cumin
I've struggled to get a backtrace from cumin because it catches all
exceptions in its main() function. But by removing that handler, I could
see a backtrace..
Mysteriously, the entry point in cumin is actually:
-> from keystone
Package: cumin
Version: 4.2.0-1
Severity: grave
cumin is currently completely broken in trixie:
anarcat@angela:~> cumin '*' 'uptime'
Caught AttributeError exception: type object 'GreenSocket' has no attribute
'sendmsg'
anarcat@angela:~[99]>
Not sure what's going on here, it might be related to
Package: g10k
Version: 0.9.9-1+b4
Severity: serious
g10k somehow hangs after doing whatever it is it's doing. Here it is
hanging after printing the usage:
anarcat@angela:~> time g10k -help (main)
Usage of g10k:
-branch string
which git branch of the Puppet envi
Package: plattenalbum
Version: 2.2.1-1+b1
Severity: serious
Out of the box, this package completely fails to run:
anarcat@angela:~$ plattenalbum
Traceback (most recent call last):
File "/usr/bin/plattenalbum", line 24, in
from mpd import MPDClient, CommandError, ConnectionError
ModuleNotF
On 2024-12-22 18:17:39, Simon Josefsson wrote:
> Antoine Beaupré writes:
>
>> On 2024-12-21 10:25:36, Simon Josefsson wrote:
>>> Hi. It seems golang-goptlib changed namespace between upstream
>>> releases, and snowflake has to adapt. However, it is possible to
m that?
Thanks for checking. I've been running 6.12.5-1 successfully for the
past few days. Thanks!
Antoine
On 2024-12-21 10:25:36, Simon Josefsson wrote:
> Hi. It seems golang-goptlib changed namespace between upstream
> releases, and snowflake has to adapt. However, it is possible to solve
> this with a hack in golang-goptlib, so I did that.
thank you so much!
btw, you might want to look into:
htt
On Fri, 13 Dec 2024 15:18:50 +0100 Jan Binder
wrote:
> Thanks for looking into this, disabling the camera works as a stopgap
measure
Thanks for the replies and pointers to the fix.
I'll stay on 6.11 until the next 6.12 image is made available.
Antoine
Package: src:linux
Version: 6.12.3-1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: anto...@cellerier.net
Dear Maintainer,
linux-image-6.12.3-amd64 fails to boot. The following kernel messages
are likely the relevant bits - appologies if I'm getting them wrong,
I'm unfami
I submitted the patches through Salsa:
https://salsa.debian.org/games-team/0ad/-/merge_requests/6
It builds and then runs nicely on my up-to-date Debian unstable.
I sneaked in a fix to ensure DEB_BUILD_OPTIONS=parallel=${n} is
honoured, as I needed it to ensure the package could be built on a
low-
Package: 0ad
Version: 0.0.26-7
Severity: grave
Tags: upstream
Justification: renders package unusable
Since the 1.23.0 → 1.24.0 OpenAL upgrade in unstable, 0 A.D. crashes on launch.
This is a problem affecting the upstream too:
https://wildfiregames.com/forum/topic/125203-crash-on-start-due-to-sou
On 2024-04-08 10:21:49, Riccardo Coccioli wrote:
> Pyparsing upstream finally made the v3.1.2 release the other day with the
> fix. So I guess once that lands in unstable it should be ok.
Perhaps! But this bug (a FTBFS in unstable) is still not fixed, as far
as I can tell. Right now tests are fail
On 2024-10-28 16:49:36, Helmut Grohne wrote:
> Package: python3-ulid
> Version: 2.2.0-3
> Severity: serious
> Justification: policy violation
>
> Conflicts must not be used to choose between incompatible APIs. Instead
> one or both implementations should be renamed. python3-ulid's ulid does
> not s
.
Given the package is not used and hasn't caught up with nearly ten years
of releases, I don't think there is any point in spending anymore time
on it. Please start the process to have it removed and close all the
related bugs that got filed (if any).
cheers,
--
Antoine "hashar" Musso
> Please keep packages you care about in a good shape in Debian. I
> assume you've read the past discussion in this bug and realize that
> even mono itself is unmaintained, very outdated and RC-buggy and
> package like it often miss stable releases even when they aren't
> removed from unstable.
Th
Le Thu, 29 Aug 2024 17:11:15 +0500,
Andrey Rakhmatullin a écrit :
> So we've now filed many RM bugs and some bugs for removing CLI
> subpackages, after all of this is done I think we will have only the
> following:
>
> - mono (duh)
> - leaf packages that are healthy and somewhat useful:
> - ke
Package: systemd
Followup-For: Bug #1074789
Just writing to confirm this is a major issue that particularly
affects cinnamon desktop users. Adding the stable-proposed-updates
suite to sources.list fixes the problem:
deb http://deb.debian.org/debian/ stable-proposed-updates main
A.
Control: fixed -1 32+20240611-1
On 2024-08-19 11:13:26, Antoine Beaupré wrote:
> On 2024-08-19 17:06:58, Christoph Anton Mitterer wrote:
>> On Mon, 2024-08-19 at 10:58 -0400, Antoine Beaupré wrote:
>>> To which version?
>>
>> Well I'd guess any earlier one. In
On 2024-08-19 17:06:58, Christoph Anton Mitterer wrote:
> On Mon, 2024-08-19 at 10:58 -0400, Antoine Beaupré wrote:
>> To which version?
>
> Well I'd guess any earlier one. In my case I simply took the previous
> one 32+20240611-1, which is still in testing.
I tried to in
On 2024-08-19 05:04:29, Christoph Anton Mitterer wrote:
> Downgrading fixes the issue.
To which version?
Package: kmod
Followup-For: Bug #1079022
I can confirm this is still happening right now in sid. A simple way
to reproduce is with:
sudo sbuild-qemu-create -o /srv/sbuild/qemu/unstable-autopkgtest-amd64.img
unstable https://deb.debian.org/debian
qemu-system-x86_64 -enable-kvm -object rng-random,
On 2023-01-06 13:11:02, ChangZhuo Chen (陳昌倬) wrote:
> Hi Vincent,
>
> Since Debian has updated nomacs to 3.17.2206. Please help to report this
> issue to upstream if it is still a problem in 3.17.2206, thanks.
Hi!
I'm a little confused: Vincent marked the bug as "found" in
"3.17.2206+dfsg-1" the
On 2024-08-17 11:35:52, Antoine Beaupré wrote:
> Actually, my investigation wasn't quite correct there: I was looking in
> the "old" /var/lib/puppet/reports directory, which is now
> /var/lib/puppetserver/reports directory...
>
> So we should do this:
>
>
Actually, my investigation wasn't quite correct there: I was looking in
the "old" /var/lib/puppet/reports directory, which is now
/var/lib/puppetserver/reports directory...
So we should do this:
1. make sure we either move /var/lib/puppet/reports to
/var/lib/puppetserver/reports on upgrade (
Package: puppetserver
Version: 7.9.5-2
Severity: grave
On our "good old" puppetmaster server running 5.5, we have a cron job
that cleans up old reports, part of the Debian package:
root@pauli:/etc# cat cron.daily/puppet-master
#!/bin/sh
if [ -e /var/lib/puppet/reports ] ; then
find /var
ests
> succeed.
>
> Since Antoine has low threshold NMU declared, I will upload directly
> without delay in the next couple days. If there are any objections,
> please let me know.
Thanks!
--
Marijuana grows naturally on the planet.
Mushrooms grows naturally on the planet.
Don't
Is there some help required with packaging a new laravel upstream source
to restore compatibility with the Debian-provided symfony packages?
I would like to run some tests with Debian-provided laravel, since this
incompatibility is a blocker to its installation I’m willing to lend a
hand to fix it
Since the new reported problem with building 0 A.D. from source is
distinct from the one reported in the first place, please consider
closing the current bug report and open a new one instead.
Keeping this one open is preventing the 0 A.D. packages from migrating
to testing.
Unless someone can se
Package: nwg-displays
Version: 0.3.20-1
Severity: serious
Out of the box, installing nwg-displays fails to start:
anarcat@angela:~$ nwg-displays
(nwg-displays:270283): dbind-WARNING **: 16:47:31.358: AT-SPI: Error retrieving
accessibility bus address: org.freedesktop.systemd1.UnitMasked: Unit
> The users who would want to avoid this risk for data loss can disable
> this behaviour locally with the following command:
> /etc/tmpfiles.d/home.conf
Oops, what I meant is that the described behaviour can be disabled with
the following command:
touch /etc/tmpfiles.d/home.conf
While the update to apt-listbugs 0.1.42 does indeed trigger the
reported problem, its cause is not in apt-listbugs code itself.
This update uses https by default, but one of the servers answering to
bugs.debian.org (bembo.debian.org) uses a TLS certificate that is not
signed by a well-known author
> This update uses https by default, but one of the servers answering to
> bugs.debian.org (bembo.debian.org) uses a TLS certificate that is not
> signed by a well-known authority, leading to the certificate
> verification failure.
You can probably forget about that, further investigation seems to
Please consider lowering this bug report severity.
While it would indeed be really nice to get a more recent build of Mono
in Debian repositories (I am sure the Debian Mono Group would be happy
to get help with this), keeping the current outdated build is much more
useful than not having access to
Source: python-zombie-imp
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
The python-zombie-imp source requires the "setuptools" Python module,
but python3-setuptools is not included in its build dependencies.
This has been noticed when
On 2024-04-30 08:25:55, Georg Faerber wrote:
> On 24-04-29 16:19:21, Antoine Beaupre wrote:
>> Package: onionprobe
>> Version: 1.0.0+ds-2.1+deb12u1
>> Severity: serious
>>
>> The Debian package shipped in bookworm right now changed the path to
>>
Package: onionprobe
Version: 1.0.0+ds-2.1+deb12u1
Severity: serious
The Debian package shipped in bookworm right now changed the path to
the examples/ directory. It used to be:
/usr/lib/python3/dist-packages/onionprobe/examples/tpo.py
and now seems to be:
/usr/onionprobe/examples/tpo.py
A
Control: tag -1 pending
Hello,
Bug #1067290 in pymeeus 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:
https://salsa.debian.org/python-team/packages/pymeeus/-/commit/17a5c3310920d3f86bc
On 2023-07-27 13:04:22, Riccardo Coccioli wrote:
> I've checked the issue and opened a bug upstream to pyparsing [1] as this
> is indeed a regression.
> Running CI on cumin I've also found that pylint is reporting new issues
> related to pyparsing code, for which I've opened a separate bug upstream
On 2024-02-01 03:27:23, Steve Langasek wrote:
[...]
> If you have any concerns about this patch, please reach out ASAP. Although
> this package will be uploaded to experimental immediately, there will be a
> period of several days before we begin uploads to unstable; so if information
> becomes
Hi Andrew!
This is a quick word to let you know that I've disabled valgrind tests
on armhf in the Debian package. They were failing since the 1.8.5 upload
(but possibly not in 1.8.0!), you can see a log here:
https://buildd.debian.org/status/fetch.php?pkg=pv&arch=armhf&ver=1.8.5-1&stamp=170045378
Package: pius
Version: 3.0.0-5
Severity: grave
I've been trying to use pius to sign things, and it's completely
failing me:
anarcat@angela:~$ pius -s BBB6CD4C98D74E1358A752A602293A6FA4E53473
D477040C70C2156A5C298549BB7E9101495E6BF7
Welcome to PIUS, the PGP Individual UID Signer.
Usage: pius [o
On 2023-12-12 15:39:24, Patrick Matthäi wrote:
[...]
>> It doesn't *quite* fix it just yet. For platforms where the ucode is
>> *not* provided (e.g. in my case it's the pcengines APU that don't have
>> firmware upgrades), this *still* yields a UNKNOWN warning. After a brief
>> discussion in the i
Source: rclone
Severity: critical
Debian is somewhat lagging behind upstream. Unstable currently has
1.60.1 (2022-11-17, uploaded to unstable on 2022-12-13) while upstream
is at 1.65.0 (released 2022-11-26).
It looks like upstream does a release roughly every two months, is
there a plan to follow
Control: reopen -1
Control: subscribe -1
On 2023-11-15 15:46:24, Antoine Beaupré wrote:
> Control: tags -1 +patch
>
> On 2023-11-15 14:54:26, Antoine Beaupré wrote:
>> On 2022-06-20 13:54:38, Nick Lewycky wrote:
>>> Package: needrestart
>>> Version: 3.6-1
&
Control: tags -1 +patch
On 2023-11-15 14:54:26, Antoine Beaupré wrote:
> On 2022-06-20 13:54:38, Nick Lewycky wrote:
>> Package: needrestart
>> Version: 3.6-1
>> Severity: normal
>>
>> `sudo needrestart -w` always prints "Failed to check for processor
>
On 2022-06-20 13:54:38, Nick Lewycky wrote:
> Package: needrestart
> Version: 3.6-1
> Severity: normal
>
> `sudo needrestart -w` always prints "Failed to check for processor
> microcode upgrades." on my AMD Ryzen 9 3900X 12-Core Processor.
[...]
There's now a PR for this upstream:
https://github
Control: tags -1 +patch
There's a patch posted in this thread for this bug:
https://discuss.pixls.us/t/patch-for-newer-python-setuptools/36593
Actual link to the patch on Arch:
https://build.opensuse.org/request/show/1078462
--
The odds are greatly against you being immensely smarter than ever
I have filed #1055115 to update the package in bookworm.
a.
--
Nothing in life is to be feared, it is only to be understood.
Now is the time to understand more, so that we may fear less.
- Marie Curie
Control: tags -1 +pending
On 2023-10-13 09:17:49, Kyle Fazzari wrote:
> I don't entirely agree, but disagreement is okay. I do at least
> recommend accompanying this with a cache age statistic, as we discussed
> earlier.
Both of those have been done upstream, and I've uploaded a new snapshot
ta
On 2023-10-13 11:40:17, Antoine Beaupré wrote:
[...]
> What's the magic setting to make apt check those updates on its own? I
> often get confused between unattended-upgrades and apt there...
Answering my own question, again, on my Debian bookworm machine, there's
a `/etc/cron.
On 2023-10-13 11:59:23, Antoine Beaupré wrote:
> severity 1028212 serious
> tags 1028212 +patch
[...]
> From 3b17a4dcb8caa56191c5be523c874a7f470bd04a Mon Sep 17 00:00:00 2001
[...]
> diff --git a/apt_info.py b/apt_info.py
> index eb1a642..9b1b675 100755
> --- a/apt_info.py
&
On 2023-10-13 09:17:49, Kyle Fazzari wrote:
[...]
> I don't entirely agree, but disagreement is okay. I do at least
> recommend accompanying this with a cache age statistic, as we discussed
> earlier.
Right, that would be a better way of going around doing that. I have a
separate upstream issu
On 2023-10-13 09:05:35, Kyle Fazzari wrote:
> On 10/13/23 08:26, Julian Andres Klode wrote:
>> Also please do not run apt update in the background or try to
>> calculate dist upgrades, that is evil and you're breaking stuff.
>> If you want to check for updates, make sure the periodic apt service
>>
On 2023-10-05 16:46:01, Ondřej Surý wrote:
> Go ahead and add yourself to maintainers and do a proper release if you care
> about the packages. It would be appreciated
Right now I'm about 4 yaks down in this stack, so adding myself to
maintainers is not part of my priorities right now.
As of al
Control: forwarded -1 https://github.com/letoams/hash-slinger/issues/45
Control: tags -1 +patch
I submitted this patch upstream to fix this issue:
https://github.com/letoams/hash-slinger/pull/46
Attached as well.
--
Antoine Beaupré
torproject.org system administration
>F
r recommends no packages.
hash-slinger suggests no packages.
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/bin/tlsa (from hash-slinger package)
--
Antoine Beaupré
torproject.org system administration
tags -1 upstream
thanks
Similar symptoms have been reported by Arch Linux users:
https://bugs.archlinux.org/task/79628
So this bug is most probably not specific to the Debian packaging.
OpenPGP_signature.asc
Description: OpenPGP digital signature
I ran more tests, and could reproduce what I think is the same bug without
relying on WINE.
Trying to play an audio file using mpv:i386 [1] on an amd64 host causes a
segfault. While mpv:amd64 has no issue.
[1]: https://packages.debian.org/sid/mpv
I think the problem might actually be related
Package: bsdgames
Version: 2.17-29+b1
Severity: critical
I wonder if wtf(6) should be split in a separate package. It's a
genuinely useful package (as opposed to a "game") that I have only
discovered recently, even though I have been familiar with BSD games
for more than a few decades at this poin
On 2023-06-26 10:27:37, Antoine Beaupré wrote:
[...]
> I guess the first step is to wait for the package to transition to
> trixie and then do the -pu? I suspect it will be hard to test this in
> trixie since you'd need to upgrade from buster to trixie, right?
I meant bullseye
On 2023-06-24 22:38:38, Andreas Beckmann wrote:
[...]
>> I'll prepare a ruby-activerecord proposed-update targeting bookworm.
>
> This needs to be fixed in sid first.
>
> Adding the Conflicts against ruby-arel in ruby-activerecord requires
> changes in src:ruby-premailer-rails, too, since that (d
Package: foot
Version: 1.13.1-2
Severity: critical
X-Debbugs-Cc: please ship upstream themes
Upstream has a bunch of themes in the source tree. Those can be
included with a simple, say:
[main]
include=/usr/share/foot/themes/gruvbox-light.ini
yet we don't ship those themes! Wouldn't it be great t
I can confirm that trashing the eln-cache and restarting emacs with
`markdown` in the block list works.
--
Le monochrome, c'est pour ceux qui s'intéressent (encore) au contenu.
Usenet dans ces conditions, c'est comme le web avec lynx, on prend
trop conscience du vide, c'est déprimant.
On 2023-06-11 14:45:19, Nicholas D. Steeves wrote:
> Hi,
>
> Here is a way to work around this bug (whether in Emacs or in markdown-toc).
>
> To test:
> emacs --eval="(setq native-comp-deferred-compilation-deny-list
> '(\"markdown-toc\"))"
>
> To make permanent:
> (setq native-comp-deferred-compil
On 2023-06-05 12:16:28, Antoine Beaupré wrote:
> Is there something out there that takes a markdown doc as input and
> outputs a TOC?
Answering my own question, this does what I want:
md_toc github -o . < tpa-rfc-36-gitolite-gitweb-retirement.md
... and what I want in many
On 2023-06-03 20:41:40, Nicholas D. Steeves wrote:
> Nicholas D Steeves writes:
>
>> I also confirmed that both the patched version (in the staging branch)
>> and unpatched version (in bookworm) work correctly with
>>
>>
>> https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-36-git
I bumped the bug severity to prevent the automatic migration to Bookworm, but
feel free to lower it if you think it is not warranted.
OpenPGP_signature
Description: OpenPGP digital signature
It looks like an update of rspamd should fix this:
https://github.com/rspamd/rspamd/issues/4409
I am reassigning this bug report to rspamd since it seems that a fix is
available from their upstream.
OpenPGP_signature
Description: OpenPGP digital signature
On 2023-05-19 14:39:14, Nicholas D Steeves wrote:
> Control: tag -1 confirmed upstream fixed-upstream pending
> Antoine Beaupre writes:
>
>> Package: elpa-markdown-toc
>> Version: 0.1.5-2
>> Severity: grave
>
>> markdown-toc-generate-toc crashes with:
>&g
On 2023-05-19 15:02:34, David Bremner wrote:
> Hi Antoine;
>
> I agree that markdown file looks innocuous, but do you know if it is
> just this file or any markdown file?
I managed to have it generate a TOC with a simple:
# a
# b
## c
But it also crashed (ultimately
Package: elpa-markdown-toc
Version: 0.1.5-2
Severity: grave
In Debian bookworm, markdown-toc is currently unusable.
Given the following markdown buffer:
```
# Background
## Why migrate?
## Gitolite and GitWeb inventory
# Proposal
```
markdown-toc-generate-toc crashes with:
Debugger ent
Source: firefox
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
I'm trying to build Firefox 113 from the git repository. I have pulled
the package with:
debcheckout firefox
Then tried to download the latest tarballs with:
On 2023-03-28 00:13:46, Francesco Poli wrote:
> On Mon, 27 Mar 2023 00:03:20 -0400 (EDT) Unit 193 wrote:
[...]
>> And here lies the problem. Seemingly one of the big fixes in 2023.03.03
>> is a workaround for the aforementioned throttling, to revert would mean to
>> make yt-dlp unusably slow. B
1 - 100 of 531 matches
Mail list logo
