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:
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
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=armhf=1.8.5-1=1700453788=0
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
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:
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
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
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.daily/apt-
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
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
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
o packages.
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/bin/tlsa (from hash-slinger package)
--
Antoine Beaupré
torproject.org system administration
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 here
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
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
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 m
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
>>
>>
>>
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:
>>
>> Debugger entered--Lisp error:
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) on:
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.
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,
>>>
>>>
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
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:
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
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
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
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
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 list from debian
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
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
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
: #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,
so it'
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
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 s
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 reproduce this. I can
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
>>
>> .. is marked as "archived by the
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
Hum. Now I'm a little confused: why did you do this?
* Add diversion for /usr/bin/gh to allow concurrent install with gitsome
and remove Conflicts with gitsome. This is inspired by the conflict
resolution between the moreutils and parallel packages where both
contain
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 bookworm as
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
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
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:
>
>
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
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
Control: severity -1 normal
On 2021-10-08 15:24:56, Gabriel Filion wrote:
> Package: undertime
> Version: 2.6.0
> Severity: grave
> Justification: renders package unusable
>
> Hello,
>
> I'm currently getting stack traces consistently when using undertime. No
> matter
> the timezone that I
On 2021-09-13 20:33:03, Sebastian Ramacher wrote:
> Control: reassign -1 jackd2 1.9.17~dfsg-1
> Control: tags -1 moreinfo unreproducible
>
> On 2021-09-13 13:39:43, Antoine Beaupre wrote:
>> Package: jackd
>> Version: 5+nmu1
>> Severity: grave
>
> You got the wrong package. This is the meta
On 2021-06-16 15:01:35, Adrian Bunk wrote:
> On Mon, May 24, 2021 at 11:33:50AM -0400, Antoine Beaupré wrote:
>> On 2021-05-18 15:45:52, Andreas Beckmann wrote:
>>...
>> > https://lintian.debian.org/tags/bogus-mail-host
>> >
>> > E Uploaders anar...@kou
On 2021-05-18 15:45:52, Andreas Beckmann wrote:
> Source: qthid-fcd-controller
> Version: 4.1-5
> Severity: serious
>
> Hi,
>
> src:qthid-fcd-controller triggers the lintian autoreject tag
> 'bogus-mail-host',
> i.e. if the package would be reuploaded today without changes, it would
> be
Control: forward -1 https://github.com/duritong/trocla/issues/63
On 2021-05-04 15:54:02, Antoine Beaupré wrote:
> FWIW, I tried to fix this by updating to latest upstream (0.3.0) and I
> get the exact same test failure in unstable right now.
>
> I contacted upstream about the probl
FWIW, I tried to fix this by updating to latest upstream (0.3.0) and I
get the exact same test failure in unstable right now.
I contacted upstream about the problem privately.
A.
--
"Faith" means not wanting to know what is true.
- Friedrich Nietzshe
Control: severity -1 normal
On 2021-04-28 09:00:46, Lev Lamberov wrote:
> Hi Antoine,
>
> Вт 27 апр 2021 @ 13:53 Antoine Beaupre :
>
>> Package: elpa-esup
>> Version: 0.7.1-3
>> Severity: grave
>> Tags: upstream
>>
>> This package is unusable in Debian 11 bullseye in its current
>> state. In my
LGTM.
On 2021-04-21 08:20:36, David Bremner wrote:
> The latter actually reports a number of matches on stdout, making the
> tests pass.
> ---
> tests.d/client-server/02-move-mail | 2 +-
> tests.d/client-server/03-copy-mail | 2 +-
>
I have had the same, completely crashes the apt run too, neat. :)
dpkg: error processing archive
/var/cache/apt/archives/webext-browserpass_3.7.2-1+b1_amd64.deb (--unpack):
unable to open
On 2020-12-14 23:45:06, Vincent Lefevre wrote:
> Control: retitle -1 nomacs uses internal libexiv2 functions to get the user
> comment
> Control: severity -1 serious
> Control: tags -1 - patch
>
> On 2020-12-12 21:59:38 +0100, Vincent Lefevre wrote:
>> I'm attaching the patch I've written. There
reassign 985737 pymeeus
found 985737 0.3.7-1
fixed 985737 0.4.3+dfsg1-1
thanks
On 2021-03-22 21:29:43, Sebastian Ramacher wrote:
> Source: convertdate
> Version: 2.3.2-1
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
>
> The autopkgtests of convertdate fail everywhere:
> | test_jwday
On 2021-02-18 02:32:10, Sadie Powell wrote:
> Charybdis' development was terminated due to (among other reasons) threats by
> a former maintainer. It probably won't be revived.
>
> It's successor is probably Solanum (https://github.com/solanum-ircd/solanum)
> which is a fork that is led by
On 2021-01-25 22:20:38, Dr. Tobias Quathamer wrote:
> Am 25.01.21 um 16:35 schrieb Antoine Beaupré:
>> On 2021-01-24 23:53:20, Damon Lynch wrote:
>>> On Sun, Jan 24, 2021 at 8:44 PM Antoine Beaupré wrote:
>>>
>>>> Maybe then there is an easy fix to keep
On 2021-01-24 23:53:20, Damon Lynch wrote:
> On Sun, Jan 24, 2021 at 8:44 PM Antoine Beaupré wrote:
>
>> Maybe then there is an easy fix to keep RPD in Debian if
>> rawkit disappears.
>>
>>
> There is no need for any kind of fix in the code itself. Just re
On 2021-01-24 20:18:27, Damon Lynch wrote:
>> Otherwise I'm afraid we won't be able to ship
>> RPD with Debian starting with bullseye, which would really be a shame...
>
> I am the developer of Rapid Photo Downloader. I am not impressed by this
> suggestion. Rapid Photo Downloader has an optional,
On 2021-01-24 14:59:03, Antoine Beaupré wrote:
> Hi,
>
> It seems like rapid-photo-downloader will not make it into the next
> Debian stable release (bullseye). It depends on "rawkit" (which I happen
> to maintain for some reason), and *that* package fails with newer lib
Hi,
It seems like rapid-photo-downloader will not make it into the next
Debian stable release (bullseye). It depends on "rawkit" (which I happen
to maintain for some reason), and *that* package fails with newer libraw
versions:
https://bugs.debian.org/978079
I'm not sure how to fix this, and I
Control: forward -1 https://github.com/photoshell/rawkit/issues/155
Control: tags -1 +confirmed
On 2020-12-25 16:58:42, Kendy Kutzner wrote:
> sudo aptitude install libraw20 python3-rawkit
> python3
from rawkit.raw import Raw
r=Raw(filename='1608680820.cr2')
> [...]
> ImportError:
reassign 954079 automat
affects 954079 magic-wormhole
forward 954079 https://github.com/glyph/automat/issues/118
thanks
On 2020-03-16 13:49:58, Guillem Jover wrote:
> Package: magic-wormhole
> Version: 0.11.2-1
> Severity: serious
>
> Hi!
>
> This package does not work anymore in unstable. I
On 2020-03-27 22:44:31, Moritz Mühlenhoff wrote:
> On Sat, Jan 06, 2018 at 01:01:28PM -0500, Antoine Beaupré wrote:
>> Control: forwarded -1 https://gitlab.com/anarcat/gameclock/issues/1
>>
>> Understood.
>
> Hi Antoine,
> let's remove gameclock from the archive
On 2020-03-20 23:41:59, Moritz Mühlenhoff wrote:
> On Sat, Nov 09, 2019 at 06:11:46PM -0500, Antoine Beaupré wrote:
>> There was a 3 year old "python 3" branch sitting around in the repo that
>> I revived by merging in the latest code.
>>
>> Tests still fail (
On 2020-03-17 09:14:03, Scott Kitterman wrote:
> Package: src:dateparser
> Version: 0.7.2-1
> Severity: serious
> Justification: Policy 2.2.1
>
> This package uses python pip to download and install packages from outside the
> Debian archive to run autopkgtests. Main is required to be
On 2019-12-26 02:05:56, maxigas wrote:
> On Wed, Dec 25 2019, Moritz Mühlenhoff wrote:
>
>> On Fri, Aug 30, 2019 at 07:12:24AM +, Matthias Klose wrote:
>>> Package: src:bugs-everywhere
>>> Version: 1.1.1-4
>>> Severity: normal
>>> Tags: sid bullseye
>>> User: debian-pyt...@lists.debian.org
>>>
On 2019-12-18 22:59:54, Thorsten Glaser wrote:
>> I encourage you to engage with joeyh anyways, if you can. ;)
>
> We engaged in real life during our trip to DebConf in Bosnia,
> which was enjoyable (if a lengthy road trip), I can relate ;)
> I just had trouble with the website (it’s not my medium
On 2019-12-18 20:42:11, Thorsten Glaser wrote:
>> https://etckeeper.branchable.com/todo/
>
> This seems to be a static page? I don’t find out how to do that.
It's not a static page: there's a field at the top of the page where you
can input a page name and then you get served a login form and so
Control: forward -1
https://etckeeper.branchable.com/todo/vcs-commit_hook_is_not_POSIX-friendly/
On 2019-12-18 20:32:41, Thorsten Glaser wrote:
> On Wed, 18 Dec 2019, Thorsten Glaser wrote:
>
>> The patch fixes the issue by reimplementing the -mmessage feature
>> introduced in 1.18.11 in
On 2019-12-18 20:16:50, Thorsten Glaser wrote:
> Package: etckeeper
> Version: 1.18.12-1
> Followup-For: Bug #946055
>
> Find a patch attached. I intend to NMU if this isn’t fixed RSN.
This package, like all of mine, is LowNMU so upload whenever you feel
ready.
> The patch fixes the issue by
On 2019-12-09 22:51:16, Jakub Wilk wrote:
> Package: internetarchive
> Version: 1.8.5-1
> Severity: grave
>
> The ia command doesn't work at all:
>
>$ ia help
>Traceback (most recent call last):
> File "/usr/bin/ia", line 6, in
>from pkg_resources import load_entry_point
>
On 2019-10-23 09:41:51, Paul Wise wrote:
> Package: torbrowser-launcher
> Version: 0.3.2-2
> Severity: serious
>
> Tor Browser 9.0 shows only black screens because the default apparmor
> profile does not allow write access to /dev/shm/org.mozilla.ipc.*.*
> like it does for /dev/shm/org.chromium.*
There was a 3 year old "python 3" branch sitting around in the repo that
I revived by merging in the latest code.
Tests still fail (the test suite hangs on py2 and fails on py3), but at
least there's some work done. A large part of the porting was already
done by converting `print` statements to
On 2019-08-21 23:49:06, Andrey Rahmatullin wrote:
> Package: src:monkeysign
> Version: 2.2.4
> Severity: serious
>
> As Python 2 versions of zbar and zbarpygtk were removed, this package should
> be
> updated to use Python 3 or removed.
Monkeysign will not be ported to zbar or pygtk3. There is
On 2019-11-09 08:05:32, peter green wrote:
> tags 943867 +patch
> thanks
>
> Since there was no maintainer response to this bug report, I decided to go
> ahead and prepare a NMU. While testing for said NMU I found that the
> package's clean target did not clean up properly. So I fixed it.
On 2019-11-02 07:01:43, Mike Gabriel wrote:
> Hi Antoine,
>
> On Sa 02 Nov 2019 00:10:38 CET, anarcat wrote:
>
>> Control: tags 942114 + pending
>>
>> Dear maintainer,
>>
>> I've prepared an NMU for ganeti-instance-debootstrap (versioned as
>> 0.16-6.1) and
>> uploaded it to DELAYED/02. Please
On 2019-10-10 11:17:24, Antoine Beaupré wrote:
> Control: tags -1 +patch
>
> Here's a patch to fix this, also available in:
>
> https://salsa.debian.org/ganeti-team/ganeti-instance-debootstrap/merge_requests/1
I'm thinking of doing a NMU of this patch to unstable within the next
Control: tags -1 +patch
Here's a patch to fix this, also available in:
https://salsa.debian.org/ganeti-team/ganeti-instance-debootstrap/merge_requests/1
--
You are absolutely deluded, if not stupid, if you think that a
worldwide collection of software engineers who can't write operating
On 2019-09-08 16:28:52, Daniel Kahn Gillmor wrote:
> Version: 0.0.20190905-1
>
> Over in 849...@bugs.debian.org, Daniel Kahn Gillmor wrote:
>> I do plan for putting wireguard into buster-backports, since i expect
>> the upstream inclusion issues to be resolved one way or another by the
>> time of
Control: tag -1 pending
Hello,
Bug #928990 in dmarc-cat 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:
Control: tags -1 +confirmed
On 2019-05-14 20:47:26, Gianfranco Costamagna wrote:
> Hello, as said, the package attempts to do internet communication
> during build... this is forbidden by policy.
Agreed.
I don't know how to handle this in the package build... Maybe I should
just disable the
Control: severity 928509 normal
On 2019-05-06 15:04:09, Karsten wrote:
> Package: firefox-esr
> Version: 60.6.1esr-1~deb8u1
> Justification: user security hole
> Severity: grave
> Tags: security
>
> Hello Debian-Team,
>
> this security bug shall show that Firefox is going to be more and more
>
On 2019-05-03 17:15:59, intrigeri wrote:
> Hi,
>
> (slightly reordering quoted text)
>
> Antoine Beaupre:
>> So what will be the way forward for Debian users in buster?
>
>> TL;DR: TBL in backports or install by hand from TPO, AFAIK.
>
> Agreed.
>
>> What does Tails do with this?
>
> Tails only
Hi all,
We had the privilege to hold the Toronto BSP in the Mozilla offices
here, and our host (in CC) was kind enough to take a quick look at this
issue with the Firefox package. He told me to CC him so that he could
look into the issue.
So to summarize for Will: there's a release-critical bug
Control: block -1 by 928092
Control: user debian-rele...@lists.debian.org
Control: usertags 928092 + bsp-2019-04-ca-toronto
Control: usertags -1 + bsp-2019-04-ca-toronto
On 2019-04-27 20:50:11, Salvatore Bonaccorso wrote:
> Control: tags -1 + patch
>
> Hi
>
> I have pushed a change cherry-picking
1 - 100 of 323 matches
Mail list logo
