.
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
On 2023-03-07 15:59:40, Steve McIntyre wrote:
> On Tue, Mar 07, 2023 at 10:39:04AM -0500, Antoine Beaupré wrote:
>>On 2023-02-26 19:15:39, anar...@debian.org wrote:
>>> Control: tags 987008 + pending
>>>
>>> Dear maintainer,
>>>
>>> I&#x
On 2023-02-26 19:15:39, anar...@debian.org wrote:
> Control: tags 987008 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for grub2 (versioned as 2.06-8.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
> Note that the package was uploaded to *ex
this moment in time. Making this update just before does the trick.
The patch is in attachment.
Regards,
Charles-Antoine Couret
diff --git a/debian/timidity-daemon.postinst b/debian/timidity-daemon.postinst
index a3610f9..573bc09 100644
--- a/debian/timidity-daemon.postinst
+++ b/
Package: python3-qrencode
Version: 1.2-5+b8
Severity: grave
X-Debbugs-Cc: debian-pyt...@lists.debian.org
It looks like the qrencode Python library is currently unusable in
Debian bookworm. Here's a simple example:
anarcat@angela:paperbackup$ python3 -c 'import qrencode ; version, size, data =
qr
Hi Peter,
I'm writing to you as the author of this patch in grub:
https://git.savannah.gnu.org/cgit/grub.git/commit/?id=879c4a8342eacc0ba4b9dd11dc69d3ec3dbe73af
We've had a report of a release-critical bug (in CC) against grub in
Debian that claims boot failures after renaming a logical volume:
Hi everyone,
I have uploaded a NMU of this package in experimental, with a 2-days
delayed to give the maintainers here time to respond... Considering the
importance of grub, i figured it was safer that way.
A copy of the package is also available here:
https://people.debian.org/~anarcat/debian/s
owner 987008 anar...@debian.org
thanks
Hi,
I've ported the submitted patch here into the package and plan to upload
an NMU shortly.
To quote the actual patch file I ended up with:
Description: fix renamed LV detection
It looks like the detection of the LVM logical volumes fails in
certain e
tag 997179 +pending
user debian-rele...@lists.debian.org
usertag 997179 + bsp-2023-02-ca-montreal
thanks
I've orphaned this package (#1031941) but I figured I could at least fix
this bug before I go.
--
When the power of love overcomes love of power the
Package: puppetserver
Version: 7.9.3-3
Severity: grave
*Something* this weekend broke my Puppetserver. I'm not sure
what. It's now failing to start (repeatedly) with:
jan 29 06:57:07 marcos systemd[1]: Starting Puppet Server...
jan 29 06:57:10 marcos java[1079416]: WARNING: update-vals already re
On 2023-01-19 11:30:31, Jérôme Charaoui wrote:
> So considering all this I'm currently leaning towards adding a
> transitional "puppet-master" and/or "puppet-master-passenger" package
> for the purpose of shipping a NEWS file recommending that users migrate
> to the puppetserver package manually
reassign 1028689 1028767 1028739 1028689 setuptools-scm
forcemerge 1027947 1028767 1028739 1028689
affects 1028767 sphinxs-autodoc-typehints
affects 1028739 pubpaste
affects 1028689 stressant
thanks
It seems like this bug is affecting a *lot* of packages. Just on my
side, two packages are FTBFS an
e: info: source package cumin
dpkg-buildpackage: info: source version 4.1.1-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Antoine Beaupré
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build .
dpkg-source: info: using patch l
Seems to me we could just kick armel out of the supported architectures
for this package for now... I think we'd need to downgrade the severity
of this bug report, and remove the armel package from testing.
What do people think here?
--
Never believe that a few caring people can't change the worl
Package: zfs-dkms
Version: 2.1.6-3
Severity: serious
I have tried to upgrade to bookworm today and kernel builds fail on
zfs-dkms. It fails with:
dkms: running auto installation service for kernel 6.0.0-4-amd64:Error! Could
not locate dkms.conf file.
File: /var/lib/dkms/zfs/2.0.3/source/dkms.con
On 2022-10-23 15:21:14, Lucas Nussbaum wrote:
>> make[1]: Entering directory '/<>'
>> # Fail the build if the tzdata package does not match TZVER.
>> grep -q '^# version 2022c$' /usr/share/zoneinfo/tzdata.zi
>> make[1]: *** [debian/rules:12: data/meta/2022c.json] Error 1
this looks like a failure
On 2022-10-06 22:11:54, Fabio Fantoni wrote:
> Il 06/10/2022 17:44, Antoine Beaupré ha scritto:
>> Hello Fabio!
>>
>> Below is an excerpt of a discussion that happened in bug #1008263 about
>> removing pcmemtest from Debian, to remove the duplication of work with
>>
Hello Fabio!
Below is an excerpt of a discussion that happened in bug #1008263 about
removing pcmemtest from Debian, to remove the duplication of work with
memtest86+:
On 2022-09-09 17:08:34, Felix Zielcke wrote:
> I wasn't sure if I should wait until the new memtest86+ gets out of
> beta and upl
On 2022-10-03 18:21:46, Michael Prokop wrote:
> AFAICT (thanks to our daily Grml ISO builds) this RC bug caused
> puppet to get removed from Debian/testing, so unless this gets fixed
> we won't have puppet in bookworm? Is anyone taking care of this?
Puppet 5 has been EOL for years. It's a good thi
1017313)
Some change in libc (or gcc?) broke compilation of Postfix in Debian
bookworm (coming stable). It's unclear exactly when this definition
changed, but it's clearly breaking builds in Debian right now.
.
Postfix uses this function only once, and discards the return value
On Sun, 18 Sep 2022 09:59:01 +0200 Dominick Grift
wrote:
libatk1.0-0 (2.46.0-1) pulls in at-spi2-core (and
gsettings-desktop-schemas). It would be really nice if we could
opt out of at-spi2-core. at-spi2-core is very intrusive and by itself it
does not add any value.
at-spi2-core is only a re
On 2022-03-25 17:12:42, Felix Zielcke wrote:
> I'm not yet sure if I should file a removal bug for pcmemtest.
> But I think I'll just wait and see if that is necessary
I think you should: right now pcmemtest *will* ship with Debian
bookworm, and I don't think that's right if upstream development h
Control: reassign -1 src:puppet
On 2022-08-25 14:19:42, Antoine Beaupré wrote:
[...]
> For what it's worth, I have tested lavamind's Puppet 7 package from
> experimental, on bookworm, and it works fine:
>
> https://tracker.debian.org/pkg/puppet-agent
>
> ... I am not
On 2022-04-14 10:49:43, Antoine Beaupré wrote:
> On 2022-04-13 17:26:27, Gabriel Filion wrote:
>> Hi there,
>>
>> For what it's worth, upstream puppet does not yet suppport ruby 3.0.
>>
>> see: https://puppet.com/docs/puppet/7/release_notes_puppet.html
>>
On 2022-06-27 19:25:13, Jörg Frings-Fürst wrote:
> This is a placeholder RC bug to prevent xsane from entering testing
> and making it to a Debian release. Xsane has not been maintained by
> the Upstream author since 2014. Even the current fork does not show
> much further development.
>
> Because
Control: severity -1 normal
On 2022-08-24 17:15:20, Antoine Beaupré wrote:
> Control: tags -1 +unreproducible
>
> It's funny, I had this exact same problem earlier, and now it's
> gone. Maybe it's a transient issue with speedtest.net itself?
I still can't reproduc
Control: tags -1 +unreproducible
It's funny, I had this exact same problem earlier, and now it's
gone. Maybe it's a transient issue with speedtest.net itself?
--
Brief is this existence, as a fleeting visit in a strange house.
The path to be pursued is poorly lit by a flickering consciousness.
On 2022-08-02 13:46:44, Chris Hofstaedtler wrote:
> * Antoine Beaupre :
>> After a somewhat long period of uncertainty, Charybdis has been
>> finally abandoned upstream. The official git repository here:
>>
>> https://github.com/charybdis-ircd/charybdis
>>
&g
On 2022-06-24 16:53:20, Georges Khaznadar wrote:
> Hello, please find as an attachment a patch to fix #1012190 and #981703
> and close them.
Hi,
thanks for the patches.
I am note sure they work though, see my comments below...
> --
> Georges KHAZNADAR et Jocelyne FOURNIER
> 22 rue des mouettes
/usr/bin/parallel. See discussions in #749355.
This seems like it's the opposite of what I was suggesting in the bug
report (#1011545). And you even refer to that bug report in the
changelog:
* Limit "Conflicts: gitsome" to older (<< 0.8.0+ds-7.1) versions.
Thanks
Package: gh
Version: 2.4.0+dfsg1-2
Severity: serious
I have fixed gitsome so that it doesn't ship a /usr/bin/gh binary in
gitsome/0.8.0+ds-7.1 (which closed #1005858). Please fix the
Conflicts: so that it is versioned << 0.8.0+ds-7.1.
This is marked as "serious" because I believe that conflicting
Is there a plan to fix this in bullseye as well?
On 2022-05-16 19:13:45, Andreas Metzler wrote:
> On 2022-05-16 Antoine Beaupré wrote:
>> Sorry for jumping in, but this bug report has been open for more than
>> three years now, and blocked this package from shipping with
>> bullseye. It's still blocking it from bookwo
Hi everyone!
Sorry for jumping in, but this bug report has been open for more than
three years now, and blocked this package from shipping with
bullseye. It's still blocking it from bookworm as well...
On 2021-03-14 13:53:17, Andreas Metzler wrote:
[...]
> Hello is using debhelper compat 9 though
On 2022-04-13 17:26:27, Gabriel Filion wrote:
> Hi there,
>
> For what it's worth, upstream puppet does not yet suppport ruby 3.0.
>
> see: https://puppet.com/docs/puppet/7/release_notes_puppet.html
>
> puppet 7 added support for ruby 2.7 but 2.9 and 3.0 were never there
> upstream. I'm guessing t
On 2022-04-05 22:36:30, Axel Beckert wrote:
> Package: slop
> Version: 7.6-1
> Severity: serious
> Control: affects -1 maim
>
> Slop seems to provide a shared library without having a proper SONAME or
> ABI in the package name and bumping the library made at least "maim" to
> fail to work:
>
> maim
Package: procmail
Version: 3.22-26
Severity: critical
Tags: security
X-Debbugs-Cc: Debian Security Team
procmail is a security liability and completely unmaintained
upstream. there are viable alternatives, and it should be removed from
debian. details below.
# unmaintained
procmail is unmaintai
: line 51 in file exec.c was reached!
shush: Nothing to do.
Re-building the package from source after having installed the cron package
fix the issue.
Thank for your work,
Antoine
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-up
On 2021-11-28 20:55:34, Adrian Bunk wrote:
> Dear maintainer,
>
> I've prepared an NMU for horst (versioned as 5.1-2.1) and uploaded
> it to DELAYED/14. Please feel free to tell me if I should cancel it.
Feel free to upload it directly, thanks!
--
We are discreet sheep; we wait to see how the dr
Package: syncmaildir
Version: 1.3.0-1
Severity: grave
Tags: upstream
Forwarded: https://github.com/gares/syncmaildir/issues/18
I have experienced, twice, a situation in which SMD has attempted to
destroy my entire mail spool. In both cases I noticed before it
managed to delete it all, but it did m
Hi,
It seems to me a workaround for this bug is to run the systemd unit of
the PHP-FPM process as `www-data`. This should mitigate the privilege
escalation because the process would escalate from `www-data`
to... well, `www-data`.
Obviously that doesn't work if you have multiple pools running as
1 - 100 of 491 matches
Mail list logo
