Processing control commands:
> severity -1 important
Bug #948876 [fontforge] fontforge: Segmentation fault, making kodi FTBFS
Bug #948977 [fontforge] fontforge: Segmentation fault, making kodi FTBFS
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
> retitle -1
control: severity -1 important
control: retitle -1 fontforge: memory leak issue
Hi,
> fontforge: Segmentation fault, making kodi FTBFS
fontforge has still memory leak issues that are able to detect with
sanitize DEB_BUILD_OPTION in debian/rules, however, kodi build can
be without fontforge's
Your message dated Mon, 22 Feb 2021 05:03:29 +
with message-id
and subject line Bug#979865: fixed in m2crypto 0.37.1-2
has caused the Debian Bug report #979865,
regarding m2crypto FTBFS on IPV6-only buildds
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 22 Feb 2021 05:03:29 +
with message-id
and subject line Bug#983013: fixed in m2crypto 0.37.1-2
has caused the Debian Bug report #983013,
regarding m2crypto: autopkgtest needs update for new version of openssl:
M2Crypto.RSA.RSAError: sslv3 rollback attack
to be marked
Hi Matthew,
Matthew Vernon writes:
> I've taken Trek's patches and incorporated them into an NMU which I've
> pushed to delayed/5.
>
> We may still want to get the new version into bullseye once Jesse
> publishes it, but at least this way the fix for this bug will be in.
>
> I hope that's OK!
Processing control commands:
> tag -1 pending
Bug #983013 [src:m2crypto] m2crypto: autopkgtest needs update for new version
of openssl: M2Crypto.RSA.RSAError: sslv3 rollback attack
Added tag(s) pending.
--
983013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983013
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #983013 in m2crypto 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:
Processing control commands:
> tag -1 pending
Bug #979865 [src:m2crypto] m2crypto FTBFS on IPV6-only buildds
Added tag(s) pending.
--
979865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #979865 in m2crypto 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:
> > it would be easier to enforce to have all buildds configured equally so
> > the package does not fail on a random buildd.
>
> I *guess* that's not trivial as I think it depends on the network their in.
OTOH it's not ideal to have machines that are supposed to be similar,
being different
> On Feb 22, 2021, at 12:24 AM, Francisco Vilmar Cardoso Ruviaro
> wrote:
>
> Hello everyone,
>
> I would like to help with this,
> I reviewed the patches (thanks Dennis) and created an MR at
> https://salsa.debian.org/installer-team/netcfg/-/merge_requests/5.
>
> As Bart said, the
Hello everyone,
I would like to help with this,
I reviewed the patches (thanks Dennis) and created an MR at
https://salsa.debian.org/installer-team/netcfg/-/merge_requests/5.
As Bart said, the patches solve the FTBFS.
I intend to make a delayed NMU in 7 days.
Regards,
--
Francisco Vilmar
On 21/02/2021 22:30, Vincent Lefevre wrote:
On 2021-02-21 14:06:20 -0400, Jesse Smith wrote:
A new version of SysV init and innserv have been published today. The
new version of insserv (1.23.0) fixes the above issue. It can be
downloaded from here:
Étienne Mollier writes:
> I have been looking in the issue below in the package
> libbio-db-ncbihelper-perl. If I understood correctly, the main
> point of the package is to rely on resources made available on
> the Internet.
I'm not sure I've been personally involved with this package, but
On 2021-02-21 14:06:20 -0400, Jesse Smith wrote:
> A new version of SysV init and innserv have been published today. The
> new version of insserv (1.23.0) fixes the above issue. It can be
> downloaded from here: http://download.savannah.nongnu.org/releases/sysvinit/
There is a new version of
On Sun, 21 Feb 2021 22:23:20 +0100, Étienne Mollier wrote:
> As the purpose of the package is to fetch resources on the web,
> I did something better described by the following commit[1].
>
> [1]
>
Processing control commands:
> tag -1 upstream
Bug #983239 [src:libbio-db-ncbihelper-perl] libbio-db-ncbihelper-perl:
(autopkg)test failures when network is available
Added tag(s) upstream.
> forwarded -1 https://github.com/bioperl/Bio-DB-NCBIHelper/issues/6
Bug #983239
Control: tag -1 upstream
Control: forwarded -1 https://github.com/bioperl/Bio-DB-NCBIHelper/issues/6
Hi Aaron,
I have been looking in the issue below in the package
libbio-db-ncbihelper-perl. If I understood correctly, the main
point of the package is to rely on resources made available on
the
Hi,
I tried again to build the version of the package that was failing
(3.1.6+ds-10) and it built *successfully* in an environment similar to
the one I used for the initial test (except it was updated to the
current state of unstable).
In the failed build log, there was:
Making check in tests
Hello,
Paul Gevers, le sam. 06 févr. 2021 10:10:33 +0100, a ecrit:
> On Thu, 16 May 2019 20:15:20 +0200 Paul Gevers wrote:
> > On Sat, 27 Apr 2019 13:16:05 -0700 Tassia Camoes Araujo
> > wrote:
> > > From what I could understand, it is unlikely this will be fixed before
> > > Buster release. So
On Sun, Feb 21, 2021 at 07:32:19PM +0100, Paul Gevers wrote:
> On 21-02-2021 14:02, Jerome BENOIT wrote:
> > please consider to tag #982719 as bullseye-ignore
> > given that the issue is not a package issue but
> > it seems rather related to an chroot issue.
>
> A fresh upload from mere hours ago
Your message dated Sun, 21 Feb 2021 21:03:45 +
with message-id
and subject line Bug#980592: fixed in clamav 0.103.0+dfsg-3.1
has caused the Debian Bug report #980592,
regarding clamav: FTBFS: check_jsnorm.c:250:57: error: format not a string
literal and no format arguments
On 2021-02-21 20:47:11 +0100, Sebastian Andrzej Siewior wrote:
> On 2021-02-21 16:07:37 [+0100], Sebastian Ramacher wrote:
> > Control: tags 980592 + pending
> >
> > Dear maintainer,
> >
> > I've prepared an NMU for clamav (versioned as 0.103.0+dfsg-3.1) and
> > uploaded it to DELAYED/2. Please
Processing commands for cont...@bugs.debian.org:
> close 982624
Bug #982624 [python3-luma.led-matrix] python3-luma.led-matrix: Depends:
python3-luma.core but it is not installable
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
982624:
Your message dated Sun, 21 Feb 2021 20:22:51 +
with message-id
and subject line Bug#982619: fixed in pytools 2021.1-2
has caused the Debian Bug report #982619,
regarding pytools needs source-only upload for testing migration
to be marked as done.
This means that you claim that the problem
Processing control commands:
> close -1 4.6.1604525166.912dfbd-0.2
Bug #983266 [src:os-autoinst] src:os-autoinst: fails to migrate to testing for
too long: unresolved RC bug
Marked as fixed in versions os-autoinst/4.6.1604525166.912dfbd-0.2.
Bug #983266 [src:os-autoinst] src:os-autoinst: fails
Source: os-autoinst
Version: 4.5.1527308405.8b586d5-4.2
Severity: serious
Control: close -1 4.6.1604525166.912dfbd-0.2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 977990
Dear maintainer(s),
As recently announced [1], the Release Team
Processing commands for cont...@bugs.debian.org:
> tags 983206 + upstream fixed-upstream
Bug #983206 [libupnp13] [libupnp13] Please update for CVE-2020-12695 & fixes
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
983206:
On 2021-02-21 16:07:37 [+0100], Sebastian Ramacher wrote:
> Control: tags 980592 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for clamav (versioned as 0.103.0+dfsg-3.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
I clearly missed that
Source: vorta
Version: 0.7.3-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression timeout
Dear maintainer(s),
With a recent upload of vorta the autopkgtest of vorta fails in testing
on armhf when that autopkgtest is run with the
Hi,
On 21-02-2021 14:02, Jerome BENOIT wrote:
> please consider to tag #982719 as bullseye-ignore
> given that the issue is not a package issue but
> it seems rather related to an chroot issue.
A fresh upload from mere hours ago built successfully on our buildd
infrastructure with
Kernel: Linux
Source: hplip
Version: 3.21.2+dfsg0-1
Severity: serious
As hplip maintainer, I'm hereby making sure that hplip 3.21.2 doesn't migrate
automatically to bullseye. It was uploaded by mistake to unstable, but two
alternatives exist:
- A) Revert to 3.20.11, because the changes are too disruptive;
- B)
On 2021-02-19 4:38 a.m., Matthew Vernon wrote:
> On 15/12/2020 21:34, Jesse Smith wrote:
>> On 2020-12-15 5:04 p.m., Trek wrote:
>>> On Tue, 15 Dec 2020 12:45:40 -0400
>>> Jesse Smith wrote:
>>>
I gave the patch a test run and, while I like what it does in theory,
in practise I'm
Your message dated Sun, 21 Feb 2021 17:57:15 +
with message-id
and subject line Bug#982882: fixed in qtbase-opensource-src 5.15.2+dfsg-5
has caused the Debian Bug report #982882,
regarding lconvert uses huge amounts of RAM
to be marked as done.
This means that you claim that the problem has
Hi,
I've taken Trek's patches and incorporated them into an NMU which I've
pushed to delayed/5.
We may still want to get the new version into bullseye once Jesse
publishes it, but at least this way the fix for this bug will be in.
I hope that's OK!
Regards,
Matthew
diff --git
Processing control commands:
> tags 980592 + pending
Bug #980592 [src:clamav] clamav: FTBFS: check_jsnorm.c:250:57: error: format
not a string literal and no format arguments [-Werror=format-security]
Added tag(s) pending.
--
980592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980592
Control: tags 980592 + pending
Dear maintainer,
I've prepared an NMU for clamav (versioned as 0.103.0+dfsg-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru clamav-0.103.0+dfsg/debian/changelog
Quack,
Indeed we'll have to wait for 5.0. I had hope for 4.2 but it was pushed
back and despite interesting fixes planned for this release that's most
probably not going to work. It's unfortunate Redmine's development is
going so slowly.
Anyway we plan to provide a package in backports
Dear Paul Gevers,
please consider to tag #982719 as bullseye-ignore
given that the issue is not a package issue but
it seems rather related to an chroot issue.
Best regards,
Jerome
Source: libbio-db-ncbihelper-perl
Version: 1.7.6-2
Severity: serious
Justification: autopkgtest is relevant, network access is a policy violation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As seen on ci.d.n:
Source: libbio-db-biofetch-perl
Version: 1.7.3-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As seen on ci.debian.net:
https://ci.debian.net/data/autopkgtest/testing/amd64/libb/libbio-db-biofetch-perl/10589851/log.gz
Processing control commands:
> severity -1 serious
Bug #978316 [src:libbio-db-embl-perl] libbio-db-embl-perl: FTBFS: dh_auto_test:
error: make -j4 test TEST_VERBOSE=1 returned exit code 2
Severity set to 'serious' from 'important'
--
978316:
On Sun, Feb 21, 2021 at 12:35:13PM +0100, Jerome BENOIT wrote:
> I think that the issue is actally not a firehol issue.
Correct.
> But I cannot figure out to where the issue can be redirected.
> For now, I am reluctant to neutralize the tests.
Then you should ask Paul Gevers or another
Your message dated Sun, 21 Feb 2021 11:49:20 +
with message-id
and subject line Bug#982471: fixed in openems
0.0.35+git20190103.6a75e98+dfsg.1-3
has caused the Debian Bug report #982471,
regarding python3-openems: SmoothMeshLines.py does not work with recent
versions of numpy
to be marked
Dear Dennis, thanks for your message.
I think that the issue is actally not a firehol issue.
But I cannot figure out to where the issue can be redirected.
For now, I am reluctant to neutralize the tests.
@Lucas: do you have any hint ?
Thanks,
Jeromr
--
Jerome BENOIT |
Processing commands for cont...@bugs.debian.org:
> tags 983206 + security
Bug #983206 [libupnp13] [libupnp13] Please update for CVE-2020-12695 & fixes
Added tag(s) security.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
983206:
Hi Sandro,
Hope you're well!
Upstream are about to release 2.7.0, which should fix this FTBFS bug
and hopefully allow pylint into bullseye.
Here is a quote from
https://github.com/PyCQA/pylint/issues/4055
Let's release 2.7.0 today then ? We'll then have 2 weeks to fix the
crash and bugs
Your message dated Sun, 21 Feb 2021 11:18:40 +
with message-id
and subject line Bug#977057: fixed in behave 1.2.6-3
has caused the Debian Bug report #977057,
regarding behave FTBFS with pytest 6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing control commands:
> severity -1 important
Bug #983211 [src:php-http-psr7-integration-tests]
php-http-psr7-integration-tests: autopkgtest failure
Severity set to 'important' from 'serious'
--
983211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983211
Debian Bug Tracking System
Control: severity -1 important
Hi,
Since there has never been any autopkgtest in this package before the
last upload, I fail to understand how a failure can be considered as a
regression.
Le 21/02/2021 à 02:50, Adrian Bunk a écrit :
Source: php-http-psr7-integration-tests
Version: 1.1.1-1
Your message dated Sun, 21 Feb 2021 11:00:09 +
with message-id
and subject line Bug#934384: fixed in libvma 9.2.2-1
has caused the Debian Bug report #934384,
regarding libvma: FTBFS: some symbols or patterns disappeared
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> severity 982853 normal
Bug #982853 [pipewire] pipewire: `pipewire.service` fails to start because
`libpipewire-module-portal` fails with `failed to initialize: Cannot allocate
memory`
Severity set to 'normal' from 'grave'
> thanks
Stopping
On Mon, Feb 15, 2021 at 02:37:53PM +0100, Michael Schaller wrote:
> I've installed `xdg-desktop-portal-gtk` and rebooted but that didn't
> solve the issue either.
> From the timestamps it looks like `xdg-desktop-portal` isn't starting
> fast enough.
>
> ```
> $ journalctl --user --boot
Processing control commands:
> tag -1 patch
Bug #982471 [python3-openems] python3-openems: SmoothMeshLines.py does not work
with recent versions of numpy
Added tag(s) patch.
> tag -1 confirmed
Bug #982471 [python3-openems] python3-openems: SmoothMeshLines.py does not work
with recent versions
Processing commands for cont...@bugs.debian.org:
> tags 982853 + moreinfo
Bug #982853 [pipewire] pipewire: `pipewire.service` fails to start because
`libpipewire-module-portal` fails with `failed to initialize: Cannot allocate
memory`
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Control: tag -1 patch
Control: tag -1 confirmed
Control: tag -1 pending
Control: tag -1 upstream
Greetings,
On Wed, 10 Feb 2021 16:29:06 +0100 "g.l. gragnani"
wrote:
> the version of the CSXCAD python interface is a little bit outdated and the
> function
> SmoothMeshLines.py raises the
Your message dated Sun, 21 Feb 2021 09:33:27 +
with message-id
and subject line Bug#982888: fixed in cross-toolchain-base 52
has caused the Debian Bug report #982888,
regarding dpkg-cross generates erronous conflicts on like
libc6-amd64:x32-i386-cross
to be marked as done.
This means that
On Fri, Feb 19, 2021 at 02:43:03PM +0530, Ritesh Raj Sarraf wrote:
>...
> On Thu, 2021-02-18 at 07:16 -0800, tony mancill wrote:
>...
> > It seems that a local sbuild in a clean chroot doesn't set the
> > environment the same way that reproducible-builds.org does, as
> > 4.17.0-1
> > builds
Control: close -1 4.18.0-1
On Thu, Feb 18, 2021 at 07:16:37AM -0800, tony mancill wrote:
>...
> It seems that a local sbuild in a clean chroot doesn't set the
> environment the same way that reproducible-builds.org does, as 4.17.0-1
> builds correctly in that environment. But that's a separate
Processing control commands:
> close -1 4.18.0-1
Bug #982974 {Done: Adrian Bunk } [src:swt4-gtk] FTBFS: fails
to compile translation files
Ignoring request to alter fixed versions of bug #982974 to the same values
previously set
Bug #982974 {Done: Adrian Bunk } [src:swt4-gtk] FTBFS: fails
to
On 2021-02-13 Andreas Metzler wrote:
[...]
> Find attached a proposed debdiff.
Uploaded to delayed/5.
cu Andreas
Processing commands for cont...@bugs.debian.org:
> close 982974 4.18.0-1
Bug #982974 [src:swt4-gtk] FTBFS: fails to compile translation files
Marked as fixed in versions swt4-gtk/4.18.0-1.
Bug #982974 [src:swt4-gtk] FTBFS: fails to compile translation files
Marked Bug as done
> thanks
Stopping
62 matches
Mail list logo
