On Wed, Apr 6, 2022 at 6:30 PM Jonas Smedegaard wrote:
> Quoting Yadd (2022-04-06 18:12:30)
> > On 19/03/2022 08:38, Yadd wrote:
> > > On 19/03/2022 08:11, Yadd wrote:
> > >> On 17/03/2022 19:21, Jérémy Lal wrote:
> > >>> Source: node-lodash
> > >>> Version: 4.17.21+dfsg+~cs8.31.196.20210220-2
>
Processing control commands:
> tag -1 pending
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs
experimental/14.19.0
Ignoring request to alter tags of bug #1007858 to the same tags previously set
--
1007858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007858
Debian Bug
Processing control commands:
> tag -1 pending
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs
experimental/14.19.0
Ignoring request to alter tags of bug #1007858 to the same tags previously set
--
1007858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007858
Debian Bug
Control: tag -1 pending
Hello,
Bug #1007858 in node-lodash 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: tag -1 pending
Hello,
Bug #1007858 in node-lodash 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: tag -1 pending
Hello,
Bug #1007858 in node-lodash 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 #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs
experimental/14.19.0
Added tag(s) pending.
--
1007858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Wed, 06 Apr 2022 22:51:20 +
with message-id
and subject line Bug#1008640: fixed in scikit-fmm 2019.1.30-1.1
has caused the Debian Bug report #1008640,
regarding scikit-fmm: FTBFS: /usr/include/python3.10/object.h:133:33: error:
lvalue required as increment operand
to be
Your message dated Wed, 06 Apr 2022 22:50:24 +
with message-id
and subject line Bug#1008688: fixed in cwiid 0.6.91-2.1
has caused the Debian Bug report #1008688,
regarding cwiid: FTBFS with Python 3.10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Dear maintainer,
since this issue is currently blocking the python3.10-default
transition, I've prepared an NMU for scikit-fmm (versioned as
2019.1.30-1.1). The diff is attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru scikit-fmm-2019.1.30/debian/changelog
Control: tags 1008688 + patch
Dear maintainer,
this bug is currently blocking the python3.10-default transition, hence
I've prepared an NMU for cwiid (versioned as 0.6.91-2.1). The diff is
attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru cwiid-0.6.91/debian/changelog
Processing control commands:
> tags 1008688 + patch
Bug #1008688 [src:cwiid] cwiid: FTBFS with Python 3.10
Added tag(s) patch.
--
1008688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 confirmed fixed-upstream upstream
Bug #1009054 [openshot-qt] Just crashes
Added tag(s) fixed-upstream, upstream, and confirmed.
> forwarded -1 https://github.com/OpenShot/openshot-qt/issues/4596
Bug #1009054 [openshot-qt] Just crashes
Set Bug
Control: tags -1 confirmed fixed-upstream upstream
Control: forwarded -1 https://github.com/OpenShot/openshot-qt/issues/4596
On 2022-04-06 17:17:01 +0200, julien.pu...@gmail.com wrote:
> Package: openshot-qt
> Version: 2.6.1+dfsg1-1
> Severity: grave
>
> I just installed the software, launched
Your message dated Thu, 7 Apr 2022 00:01:50 +0200
with message-id <2f669f53-8a26-6280-566a-4ee80e97a...@web.de>
and subject line Re: Bug#1008956: tex-common: Something in package "tex-common"
causes dpkg to exit with exit code -1
has caused the Debian Bug report #1008956,
regarding tex-common:
Well, if the /tmp was full, would it have been able to generate the error
logs in there? I did run the dpkg configure command like 4 or 5 times, and
every time, it made a report..
Ashleigh Moore
amo...@ashleighhost.net
[Sent using Alpine for Linux]
On Wed, 6 Apr 2022, Hilmar Preuße wrote:
Oh, okay, that makes sense then. Go ahead and close it, if it happens
again, I'll let you know.
Ashleigh Moore
amo...@ashleighhost.net
[Sent using Alpine for Linux]
On Wed, 6 Apr 2022, Hilmar Preuße wrote:
Date: Wed, 6 Apr 2022 16:38:44
From: Hilmar Preuße
To: Ashleigh Moore
Cc:
On 4/6/22 23:34, Ashleigh Moore wrote:
Hi,
Well, if the /tmp was full, would it have been able to generate the
error logs in there? I did run the dpkg configure command like 4 or 5
times, and every time, it made a report..
Maybe there was enough space for the logs, but not for the format
On 4/6/22 23:34, Ashleigh Moore wrote:
Hi,
Well, if the /tmp was full, would it have been able to generate the
error logs in there? I did run the dpkg configure command like 4 or 5
times, and every time, it made a report..
Maybe there was enough space for the logs, but not for the format
Your message dated Wed, 06 Apr 2022 21:29:53 +
with message-id
and subject line Bug#1009072: Removed package(s) from unstable
has caused the Debian Bug report #1002221,
regarding apt-dpkg-ref: FTBFS: dvips: DVI file can't be opened:
apt-dpkg-ref.dvi: No such file or directory
to be marked as
Your message dated Wed, 06 Apr 2022 21:27:28 +
with message-id
and subject line Bug#1008804: Removed package(s) from unstable
has caused the Debian Bug report #936638,
regarding googlefontdirectory-tools: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that
Your message dated Wed, 06 Apr 2022 21:27:28 +
with message-id
and subject line Bug#1008804: Removed package(s) from unstable
has caused the Debian Bug report #1008791,
regarding Should googlefontdirectory-tools be removed?
to be marked as done.
This means that you claim that the problem has
On 4/6/22 18:49, Ashleigh Moore wrote:
Hi,
Well uh, this is embarrassing, but apparently it fixed itself overnight.
And since the machine rebooted since then, I no longer have the tmp
files it made. I suppose if I have this occur again, I'll let you guys
know?
I am so sorry if this was a
Your message dated Wed, 06 Apr 2022 21:24:53 +
with message-id
and subject line Bug#1008273: Removed package(s) from unstable
has caused the Debian Bug report #937940,
regarding python-nemu: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 06 Apr 2022 21:26:26 +
with message-id
and subject line Bug#1008701: Removed package(s) from unstable
has caused the Debian Bug report #936241,
regarding broctl: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Wed, 06 Apr 2022 21:26:26 +
with message-id
and subject line Bug#1008701: Removed package(s) from unstable
has caused the Debian Bug report #936241,
regarding broctl: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 06 Apr 2022 21:25:54 +
with message-id
and subject line Bug#1008664: Removed package(s) from unstable
has caused the Debian Bug report #1008543,
regarding gnome-shell-extension-disconnect-wifi: does not declare compatibility
with GNOME Shell 42
to be marked as done.
Your message dated Wed, 6 Apr 2022 22:56:19 +0200
with message-id
and subject line Re: Bug#1009043: dpkg-fsys-usrunmess abuses "Protected: yes"
status
has caused the Debian Bug report #1009043,
regarding dpkg-fsys-usrunmess abuses "Protected: yes" status
to be marked as done.
This means that
Control: tag -1 upstream
On Thu, Mar 31, 2022 at 07:27:51PM +0200, Graham Inggs wrote:
> As can be seen on reproducible builds [1], mercurial FTBFS with Python
> 3.10 as the default version. I've copied what I hope is the relevant
> part of the log below.
>
> This appears to be due to the
Processing control commands:
> tag -1 upstream
Bug #1008747 [src:mercurial] mercurial: FTBFS with Python 3.10 as default
Added tag(s) upstream.
--
1008747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Em qua., 6 de abr. de 2022 às 16:09, Reuben Thomas escreveu:
>
> On Wed, 6 Apr 2022 at 18:15, Joao Eriberto Mota Filho
> wrote:
>>
>> Control: tags 999182 + patch
>> Control: tags 999182 + pending
>>
>> Dear maintainer,
>>
>> I've prepared an NMU for perforate (versioned as 1.2-5.2) and
Source: virglrenderer
Version: 0.8.2-5
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for virglrenderer.
CVE-2022-0135[0]:
| out-of-bounds write in
Your message dated Wed, 06 Apr 2022 19:51:16 +
with message-id
and subject line Bug#1008641: fixed in unbound 1.13.1-1.1
has caused the Debian Bug report #1008641,
regarding python3-unbound: Cannot install because of Python dependencies
to be marked as done.
This means that you claim that
Your message dated Wed, 06 Apr 2022 19:51:16 +
with message-id
and subject line Bug#1008641: fixed in unbound 1.13.1-1.1
has caused the Debian Bug report #1008641,
regarding unbound: FTBFS: ./pythonmod/pythonmod.c:338: undefined reference to
`_Py_fopen'
to be marked as done.
This means that
Dear maintainer,
since this bug currently blocks the python3.10-default transition, I've
prepared an NMU for unbound (versioned as 1.13.1-1.1). The diff is
attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru unbound-1.13.1/debian/changelog unbound-1.13.1/debian/changelog
---
On 2022-04-06 20:16:53 +0200, Sebastian Ramacher wrote:
> Control: tags 1008689 + patch
>
> Dear maintainer,
>
> as this issues blocks the ongoing python3.10-default transition, I've
> prepared an NMU for getfem++ (versioned as 5.3+dfsg1-4.1). The diff is
> attached to this message.
>
> Cheers
Hi,
On 06-04-2022 21:30, Paul Gevers wrote:
On 06-04-2022 21:26, Paul Gevers wrote:
but ffmpeg succeeds.
But this is interesting in its output:
[libx264 @ 0x1a181a0] using cpu capabilities: ARMv6 NEON
https://www.baeldung.com/linux/proc-cpuinfo-flags#3-neon says we
shouldn't look for
Hi
On 06-04-2022 21:26, Paul Gevers wrote:
but ffmpeg succeeds.
But this is interesting in its output:
[libx264 @ 0x1a181a0] using cpu capabilities: ARMv6 NEON
Paul
OpenPGP_signature
Description: OpenPGP digital signature
It has been fixed a few months ago.
https://gitlab.gnome.org/GNOME/pitivi/-/issues/2571 We should be able to do
a release soon.
On Wed, Apr 6, 2022 at 5:27 PM wrote:
> Package: pitivi
> Version: 2021.05-1
> Severity: grave
>
>
> Just launching it after install gives:
>
> Missing soft
Hi,
On 06-04-2022 08:48, Ying-Chun Liu (PaulLiu) wrote:
I'm not sure if you have extra time.
But I think you are correct. We might need to report the bug to ffmpeg.
I'm not sure if we can simplify the test.
Like just run "ffplay test_raw.avi" or "ffmpeg -i test_raw.avi out.mp4"
to see if it
Your message dated Wed, 06 Apr 2022 19:05:54 +
with message-id
and subject line Bug#1008689: fixed in getfem++ 5.3+dfsg1-4.1
has caused the Debian Bug report #1008689,
regarding getfem++: FTBFS with Python 3.10
to be marked as done.
This means that you claim that the problem has been dealt
Source: gst-plugins-bad1.0-contrib
Version: 1.18.4-3
Severity: serious
Control: close -1 1.20.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for
Processing control commands:
> close -1 1.20.0-1
Bug #1009063 [src:gst-plugins-bad1.0-contrib] src:gst-plugins-bad1.0-contrib:
fails to migrate to testing for too long: doesn't build on buildds
The source 'gst-plugins-bad1.0-contrib' and version '1.20.0-1' do not appear to
match any binary
Processing control commands:
> tags 1008689 + patch
Bug #1008689 [src:getfem++] getfem++: FTBFS with Python 3.10
Added tag(s) patch.
--
1008689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 1008689 + patch
Dear maintainer,
as this issues blocks the ongoing python3.10-default transition, I've
prepared an NMU for getfem++ (versioned as 5.3+dfsg1-4.1). The diff is
attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru getfem++-5.3+dfsg1/debian/changelog
Well uh, this is embarrassing, but apparently it fixed itself overnight.
And since the machine rebooted since then, I no longer have the tmp
files it made. I suppose if I have this occur again, I'll let you guys know?
I am so sorry if this was a waste of your time..
--
Ashleigh / Victor Moore
Your message dated Wed, 06 Apr 2022 17:21:15 +
with message-id
and subject line Bug#998484: fixed in schleuder 4.0.2-1
has caused the Debian Bug report #998484,
regarding schleuder: FTBFS: ERROR: Test "ruby3.0" failed: #
GPGME::Error::NoSecretKey:
to be marked as done.
This means that
Control: tags 999182 + patch
Control: tags 999182 + pending
Dear maintainer,
I've prepared an NMU for perforate (versioned as 1.2-5.2) and uploaded it
to DELAYED/1 (a decreased time because the package is set as LowNMU, but
1 day because I prefer to put a delay time).
Regards,
Eriberto
diff
Processing control commands:
> tags 999182 + patch
Bug #999182 [src:perforate] perforate: missing required debian/rules targets
build-arch and/or build-indep
Added tag(s) patch.
> tags 999182 + pending
Bug #999182 [src:perforate] perforate: missing required debian/rules targets
build-arch
Control: tags 965400 + patch
Control: tags 965400 + pending
Dear maintainer,
I've prepared an NMU for aa3d (versioned as 1.0-8.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u aa3d-1.0/debian/control aa3d-1.0/debian/control
---
Processing control commands:
> tags 965400 + patch
Bug #965400 [src:aa3d] aa3d: Removal of obsolete debhelper compat 5 and 6 in
bookworm
Bug #965401 [src:aa3d] aa3d: Removal of obsolete debhelper compat 5 and 6 in
bookworm
Added tag(s) patch.
Added tag(s) patch.
> tags 965400 + pending
Bug
Quoting Yadd (2022-04-06 18:12:30)
> On 19/03/2022 08:38, Yadd wrote:
> > On 19/03/2022 08:11, Yadd wrote:
> >> On 17/03/2022 19:21, Jérémy Lal wrote:
> >>> Source: node-lodash
> >>> Version: 4.17.21+dfsg+~cs8.31.196.20210220-2
> >>> Severity: important
> >>> Tags: ftbfs
> >>>
> >>> This package
On 19/03/2022 08:38, Yadd wrote:
On 19/03/2022 08:11, Yadd wrote:
On 17/03/2022 19:21, Jérémy Lal wrote:
Source: node-lodash
Version: 4.17.21+dfsg+~cs8.31.196.20210220-2
Severity: important
Tags: ftbfs
This package fails to rebuild. Build log is attached.
The real problem comes from
Processing commands for cont...@bugs.debian.org:
> tags 1007858 + help
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs
experimental/14.19.0
Added tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1007858:
Hi Thomas and thanks for resolving the bug.
A few days ago I tried to upload a new version fixing the bug, but it
was silently ignored. At the moment I'm very busy and I don't have
time to debug the problem by uploading packages to the archive, so
your help to solve the bug with a NMU is welcome
Processing commands for cont...@bugs.debian.org:
> found 1007858 4.17.21+dfsg+~cs8.31.198.20210220-2
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs
experimental/14.19.0
Marked as found in versions node-lodash/4.17.21+dfsg+~cs8.31.198.20210220-2.
> thanks
Stopping processing here.
How is it going?
We have just released AI Website Reader app to read aloud website/ebook with AI voice control
Please check it out here:
Google Play: https://play.google.com/store/apps/details?id=com.aiwebsitereader
Thank you!
Sorry for any inconvenience. Please reply "Quit" to remove your
Processing commands for cont...@bugs.debian.org:
> severity 1007858 serious
Bug #1007858 [src:node-lodash] node-lodash: FTBFS with nodejs
experimental/14.19.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1007858:
Your message dated Wed, 06 Apr 2022 15:38:34 +
with message-id
and subject line Bug#1005470: fixed in pyparsing 3.0.7-2
has caused the Debian Bug report #1005470,
regarding pyparsing: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.10 3.9" returned exit code 13
to be
Your message dated Wed, 06 Apr 2022 15:38:34 +
with message-id
and subject line Bug#1006004: fixed in pyparsing 3.0.7-2
has caused the Debian Bug report #1006004,
regarding pyparsing: autopkgtest regression: can't open file
'/tmp/autopkgtest-lxc.yvh1lz7q/downtmp/build.0Qk/src/unitTests.py
to
Your message dated Wed, 06 Apr 2022 15:36:11 +
with message-id
and subject line Bug#1008799: fixed in fife 0.4.2-4
has caused the Debian Bug report #1008799,
regarding fife: FTBFS on mipsel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing control commands:
> tag -1 pending
Bug #1006004 [src:pyparsing] pyparsing: autopkgtest regression: can't open file
'/tmp/autopkgtest-lxc.yvh1lz7q/downtmp/build.0Qk/src/unitTests.py
Added tag(s) pending.
--
1006004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006004
Debian Bug
Processing control commands:
> tag -1 pending
Bug #1005470 [src:pyparsing] pyparsing: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) pending.
--
1005470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005470
Debian Bug
Control: tag -1 pending
Hello,
Bug #1006004 in pyparsing 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: tag -1 pending
Hello,
Bug #1005470 in pyparsing 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:
A fixed pyparsing has now been uploaded which should
let pyparsing and translate-toolkit both migrate together.
Hopefully.
--
Stuart Prescotthttp://www.nanonanonano.net/
stu...@nanonanonano.net
Debian Developer http://www.debian.org/
stu...@debian.org
GPG fingerprint90E2
Package: pitivi
Version: 2021.05-1
Severity: grave
Just launching it after install gives:
Missing soft dependency:
- GSound not found on the system
-> enables sound notifications when rendering is complete
Traceback (most recent call last):
File
Package: openshot-qt
Version: 2.6.1+dfsg1-1
Severity: grave
I just installed the software, launched "openshot-qt" and got a crash.
I'll put the result of "openshot-qt 2>&1 |tee /tmp/log" at the end of
this mail.
Cheers,
J.Puydt
Here is /tmp/log:
Warning: Ignoring XDG_SESSION_TYPE=wayland on
Your message dated Wed, 06 Apr 2022 15:07:27 +
with message-id
and subject line Bug#1004092: fixed in swayidle 1.7.1-2
has caused the Debian Bug report #1004092,
regarding swayidle FTBFS on 32bit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Hi Pierre-Elliott,
Here's a friendly notice in case you were unaware of this bug#1006381
blocking mistune0 from entering testing.
Kind regards,
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask
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:
>
>
Package: dpkg
Version: 1.21.0
Severity: serious
The dpkg-fsys-usrunmess program installs a dpkg-fsys-usrunmess package
which maliciously abuses the Protected and Conflicts/Replaces/Provides
fields to prevent installing again the usrmerge package:
Source: libtraceevent
Version: 1:1.5.1-1
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
the upstream version 1.5.1 has a race condition in the src/Makefile
which breaks the build sporadically.
This bug is
Your message dated Wed, 06 Apr 2022 12:34:14 +
with message-id
and subject line Bug#965485: fixed in dia2code 0.8.3-4.2
has caused the Debian Bug report #965485,
regarding dia2code: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that
On 4/6/22 13:29, Thomas Goirand wrote:
Hi,
As per discussion on IRC and check of the existing prerm, arptables
already has the logic in prerm to clean-up old symlinks, so I didn't
touch it.
Discussing on #debian-devel, it was agreed we need to clean-up eventual
remainings of the
Hi Sudip,
Unfortunately I found more races in the build.
There has to be something more general to be wrong with these Makefiles:
2022-04-06 12:14:27 - ERROR - --- debian/libtracefs1.symbols
(libtracefs1_1.3.0-1_amd64)
2022-04-06 12:14:27 - ERROR - +++ dpkg-gensymbolsyDWb5y 2022-04-06
Processing commands for cont...@bugs.debian.org:
> tags 1006543 fixed-upstream
Bug #1006543 [imv] imv-wayland segfaults on latest wlroots/sway, fixed in 4.3.1
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1006543:
Processing commands for cont...@bugs.debian.org:
> tags 1006543 patch
Bug #1006543 [imv] imv-wayland segfaults on latest wlroots/sway, fixed in 4.3.1
Added tag(s) patch.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1006543:
I've made an MR on Salsa with a patch that I have verified fixes the
bug[1].
Although, as has been mentioned, the best thing is probably just to
package upstream's 4.3.1. But since this bug has been around for a
while, I will do an NMU to DELAYED/5 with the fix from the MR if I don't
hear back in
Hi,
As per discussion on IRC and check of the existing prerm, arptables
already has the logic in prerm to clean-up old symlinks, so I didn't
touch it.
Discussing on #debian-devel, it was agreed we need to clean-up eventual
remainings of the symlink, if they point to /usr/sbin/*, so that's
Source: esys-particle
Version: 2.3.5+dfsg2-4
Severity: serious
Tags: ftbfs
Hi Maintainer
Since the upload of libtool 2.4.7-2, the Provides: libltdl7-dev was
removed, causing esys-particle to FTBFS. Please switch the
build-depends to the unversioned libltdl-dev.
Regards
Graham
Source: dico
Version: 2.10-1
Severity: serious
Tags: ftbfs bookworm sid
Hi Maintainer
Since the upload of libtool 2.4.7-2, the Provides: libltdl7-dev was
removed, causing dico to FTBFS. Please switch the build-depends to
the unversioned libltdl-dev.
Regards
Graham
Source: newmat
Version: 1.10.4-8
Severity: serious
Tags: ftbfs bookworm sid
Hi Maintainer
Since the upload of libtool 2.4.7-2, the Provides: libltdl7-dev was
removed, causing newmat to FTBFS. Please switch the build-depends to
the unversioned libltdl-dev.
Regards
Graham
Processing commands for cont...@bugs.debian.org:
> severity 1006543 grave
Bug #1006543 [imv] imv-wayland segfaults on latest wlroots/sway, fixed in 4.3.1
Severity set to 'grave' from 'normal'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1006543:
severity 1006788 important
thanks
On Sun, Apr 03, 2022 at 07:42:42PM +0200, Michael Banck wrote:
> On Sun, Apr 03, 2022 at 02:30:14PM +0200, Michael Banck wrote:
> > On Fri, Mar 04, 2022 at 11:36:24PM +, peter green wrote:
> > > Package: bagel
> > > Version: 1.2.2-3
> > > Severity: serious
>
Processing commands for cont...@bugs.debian.org:
> severity 1006788 important
Bug #1006788 [bagel] bagel: autopkgtest failure with new mpich.
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006788:
Control: tag -1 pending
Hello,
Bug #1008423 in golang-github-streadway-amqp 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 #1008423 [src:golang-github-streadway-amqp] golang-github-streadway-amqp:
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8
github.com/streadway/amqp returned exit code 1
Added tag(s) pending.
--
1008423:
Processing commands for cont...@bugs.debian.org:
> severity 1008765 normal
Bug #1008765 [claws-mail] claws-mail: build-depends on unavailable package
libltdl3-dev
Severity set to 'normal' from 'grave'
> severity 1008889 normal
Bug #1008889 [cluster-glue] FTBFS: Build-depends libltdl3-dev which
On 4/6/22 10:36, Thomas Goirand wrote:
Hi,
Please find attached debdiff to fix this bug.
I'll be uploading this to DELAYED/2 queue, as this is affecting a lot of
people/packages and we need a fix fast. Please let me know if you prefer
to fix it yourself and you wish me to "dcut rm" my
Your message dated Wed, 06 Apr 2022 08:49:15 +
with message-id
and subject line Bug#1008886: fixed in python-demgengeo 1.4-4.1
has caused the Debian Bug report #1008886,
regarding python-demgengeo build depends on the removed libltdl7-dev provides
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> severity 1008701 normal
Bug #1008701 [src:broctl] Should broctl be removed?
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1008701:
Hi,
Please find attached debdiff to fix this bug.
I'll be uploading this to DELAYED/2 queue, as this is affecting a lot of
people/packages and we need a fix fast. Please let me know if you prefer
to fix it yourself and you wish me to "dcut rm" my upload.
Cheers,
Thomas Goirand (zigo)diff
Processing control commands:
> tags 1008886 + patch
Bug #1008886 [src:python-demgengeo] python-demgengeo build depends on the
removed libltdl7-dev provides
Added tag(s) patch.
--
1008886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008886
Debian Bug Tracking System
Contact
Control: tags 1008886 + patch
Dear maintainer,
since this issue is blocking the ongoing python3.10 as default
transition, I've prepared an NMU for python-demgengeo (versioned as
1.4-4.1). The diff is attached to this message.
Cheers
--
Sebastian Ramacher
diff -Nru
Your message dated Wed, 06 Apr 2022 07:49:19 +
with message-id
and subject line Bug#1008976: fixed in wordpress 5.9.2+dfsg1-2
has caused the Debian Bug report #1008976,
regarding Wordpress editor shows empty screen
to be marked as done.
This means that you claim that the problem has been
* Sebastian Ramacher :
> That could be another case of the driver expecting to have a kernel
> available which in fact is disabled in the open source build. If
> 22.3.1+dfsg1-1 doesn't fix the issue for you, please let my know your
> CPU/GPU so that the issue can be reported upstream.
Control: tag -1 pending
Hello,
Bug #1008976 in wordpress 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 #1008976 [wordpress] Wordpress editor shows empty screen
Added tag(s) pending.
--
1008976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> severity 1008976 grave
Bug #1008976 [wordpress] Wordpress editor shows empty screen
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1008976:
1 - 100 of 102 matches
Mail list logo
