Package: nvidia-legacy-340xx-driver
Version: 340.108-4
Followup-For: Bug #958446
I know the command I have to run, I just don't know the path to use there. And
last time I patched the file manually, because it was only one file, I wrote
that one line by hand :D
If you show me the way, e.e. the exa
Source: python-setuptools
Version: 44.0.0-1
Severity: serious
Control: close -1 44.0.0-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testin
Processing control commands:
> close -1 44.0.0-2
Bug #958761 [src:python-setuptools] src:python-setuptools: fails to migrate to
testing for too long
Marked as fixed in versions python-setuptools/44.0.0-2.
Bug #958761 [src:python-setuptools] src:python-setuptools: fails to migrate to
testing for
Processing control commands:
> close -1 0.11.1-1
Bug #958762 [src:statsmodels] src:statsmodels: fails to migrate to testing for
too long: FTBFS on armel
Marked as fixed in versions statsmodels/0.11.1-1.
Bug #958762 [src:statsmodels] src:statsmodels: fails to migrate to testing for
too long: FTBF
Source: statsmodels
Version: 0.10.2-2
Severity: serious
Control: close -1 0.11.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 956882
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-
Processing control commands:
> close -1 2.10.3+dfsg-1
Bug #958760 [src:ncbi-vdb] src:ncbi-vdb: fails to migrate to testing for too
long: FTBFS
Marked as fixed in versions ncbi-vdb/2.10.3+dfsg-1.
Bug #958760 [src:ncbi-vdb] src:ncbi-vdb: fails to migrate to testing for too
long: FTBFS
Marked Bug a
Source: ncbi-vdb
Version: 2.9.3+dfsg-2
Severity: serious
Control: close -1 2.10.3+dfsg-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 952623
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
ar
Processing control commands:
> close -1 2.6.12-94
Bug #958759 [src:gcl] src:gcl: fails to migrate to testing for too long: FTBFS
on all/amd64
Marked as fixed in versions gcl/2.6.12-94.
Bug #958759 [src:gcl] src:gcl: fails to migrate to testing for too long: FTBFS
on all/amd64
Marked Bug as done
Source: gcl
Version: 2.6.12-92
Severity: serious
Control: close -1 2.6.12-94
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 952334
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-syn
Your message dated Sat, 25 Apr 2020 04:34:05 +
with message-id
and subject line Bug#953700: fixed in python-nmea2 1.15.0-2
has caused the Debian Bug report #953700,
regarding src:python-nmea2: fails to migrate to testing for too long
to be marked as done.
This means that you claim that the pr
Your message dated Sat, 25 Apr 2020 01:06:19 -0300
with message-id <428100af-7d87-a0af-6a1a-8cae1322b...@debian.org>
and subject line Re: Bug#954656: nyx: does not start/work
has caused the Debian Bug report #954656,
regarding nyx: does not start/work
to be marked as done.
This means that you clai
Sorry, I realized I might have sent this reply to the wrong bug.
-- Forwarded message -
From: FeRD
Date: Tue, Apr 21, 2020 at 5:31 PM
Subject: Re: Fixed in newer release of libopenshot / libopenshot-audio
To: <925...@bugs.debian.org>
On Tue, 21 Apr 2020 15:04:59 -0400 John Scott
Your message dated Sat, 25 Apr 2020 01:51:00 +
with message-id
and subject line Bug#885213: fixed in make-dfsg 4.2.1-1.3
has caused the Debian Bug report #885213,
regarding make-dfsg: please migrate to guile-2.2
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Fri, 24 Apr 2020 23:52:30 +
with message-id
and subject line Bug#958708: fixed in squid 4.11-2
has caused the Debian Bug report #958708,
regarding squid: Failed to start.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Fri, 24 Apr 2020 23:24:12 +
with message-id
and subject line Bug#958733: fixed in genext2fs 1.4.2-3
has caused the Debian Bug report #958733,
regarding genext2fs: autopkgtest failure on arm64: libguestfs: error: appliance
closed the connection unexpectedly.
to be marked as
David,
thank you for the detailed explanation and the tip (yes, I'm still
learning how the BTS works ).
On 4/24/20 9:53 PM, David Kalnischkies wrote:
> Anyway, as there is nothing apt can really do about this I have to
> reassign back even if I dislike bug-pingpong. Feel free to ask if you
> have
On Fri, Aug 30, 2019 at 07:39:14AM +, Matthias Klose wrote:
> Package: src:python-fcgi
> Version: 19980130-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from
Hi,
> Only phpmyadmin is a key package.
phpMyAdmin no longer depends on php-gettext.
phpMyAdmin is absent from buster but present in buster-backports and
does not depend on php-gettext.
(+ buster-backports in sources.list)
# apt-rdepends -r php-php-gettext
Reading package lists... Done
Build
On Fri, Apr 24, 2020 at 09:13:37PM +0200, Vincent Bernat wrote:
> ❦ 24 avril 2020 20:54 +02, Moritz Mühlenhoff:
>
> >> Tags: sid bullseye
> >> User: debian-pyt...@lists.debian.org
> >> Usertags: py2removal
> >>
> >> Python2 becomes end-of-live upstream, and Debian aims to remove
> >> Python2 fro
Your message dated Fri, 24 Apr 2020 20:35:13 +
with message-id
and subject line Bug#937929: fixed in python-mox 0.7.8-4
has caused the Debian Bug report #937929,
regarding python-mox: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Fri, 24 Apr 2020 20:35:13 +
with message-id
and subject line Bug#949228: fixed in python-mox 0.7.8-4
has caused the Debian Bug report #949228,
regarding python{,3}-mox: Missing dependency on python{,3}-six
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> reassign -1 runit 2.1.2-35
Bug #953875 [apt] runit - default installation can force init switch
Bug reassigned from package 'apt' to 'runit'.
No longer marked as found in versions apt/2.0.2.
Ignoring request to alter fixed versions of bug #953875 to the same values
Control: reassign -1 runit 2.1.2-35
Hi,
On Fri, Apr 24, 2020 at 01:54:42PM +0200, Lorenzo Puliti wrote:
> Control: reassign -1 apt 2.0.2
>
> Dear apt maintainers,
Tipp: Your message does not automatically reach the maintainers of
a package you reassign a bug to, only the 'Processed' notificatio
This error is not reproducible any more and imho, it has been fixed
when libquazip5-1 updated to depend on libquazip5-headers via #884800.
But, it now fails with the error:
src/newProjectWizard/selectpage.cpp: In constructor
‘SelectPage::SelectPage(QWidget*)’:
src/newProjectWizard/selectpage.cpp:
Processing commands for cont...@bugs.debian.org:
> severity 958708 grave
Bug #958708 [squid] squid: Failed to start.
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958
❦ 24 avril 2020 20:54 +02, Moritz Mühlenhoff:
>> Tags: sid bullseye
>> User: debian-pyt...@lists.debian.org
>> Usertags: py2removal
>>
>> Python2 becomes end-of-live upstream, and Debian aims to remove
>> Python2 from the distribution, as discussed in
>> https://lists.debian.org/debian-python/20
On 2020-01-18 15:38:18, Adrian Bunk wrote:
> Package: python3-mox
> Version: 0.7.8-3
> Severity: serious
> Control: affects -1 python-mox
>
> ? python3
> Python 3.7.6 (default, Dec 19 2019, 09:25:23)
> [GCC 9.2.1 20191130] on linux
> Type "help", "copyright", "credits" or "license" for more inform
Source: genext2fs
Version: 1.4.2-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
With a recent upload of genext2fs you added an autopkgtest, great.
However, it fails on arm64.
I copied some of the output at
On 22/04/2020 10.32, jim_p wrote:
> Here is the patch, again from aur
> https://aur.archlinux.org/cgit/aur.git/plain/05-unfuck-for-
> kernel-5.6.x.patch?h=nvidia-340xx
Now that we have 5.6 in experimental, I could test it ...
> Unlike last time with 5.5, it seems that it patches a number of files
On Fri, Aug 30, 2019 at 07:33:33AM +, Matthias Klose wrote:
> Package: src:pyeos
> Version: 0.63-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distri
Processing control commands:
> close -1 0.6.0-1
Bug #958730 [src:drf-extensions] src:drf-extensions: fails to migrate to
testing for too long
Marked as fixed in versions drf-extensions/0.6.0-1.
Bug #958730 [src:drf-extensions] src:drf-extensions: fails to migrate to
testing for too long
Marked B
Source: drf-extensions
Version: 0.4.0-1.1
Severity: serious
Control: close -1 0.6.0-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 953751
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are o
X-Debbugs-CC: tak...@debian.or.jp
Since this package hasn't been taken care of for at least 4 years (actually 9
years), I will submit the removal bug now.
Takaya: If you have any thoughts or doubts, please let me know *immediately*.
--
Best Regards,
Boyuan Yang
On Sun, 27 Aug 2017 11:13:31 +05
Your message dated Fri, 24 Apr 2020 18:19:22 +
with message-id
and subject line Bug#949972: fixed in python-alignlib 0.1.1+dfsg-1.1
has caused the Debian Bug report #949972,
regarding ftbfs, fix build dependencies
to be marked as done.
This means that you claim that the problem has been dealt
Hey Bastian,
This is already fixed in the latest 2.04-7 grub2 upload. I'll mark
this closed when the signing service pulls stuff through.
On Fri, Apr 24, 2020 at 07:58:26PM +0200, Bastian Blank wrote:
>Package: grub-efi-amd64-signed
>Version: 1+2.04+5
>Severity: grave
>
>grub-efi-amd64-signed got
On Wed, Oct 23, 2019 at 02:33:34AM +, mo...@debian.org wrote:
> Source: tcpwatch-httpproxy
> Version: 1.3.1-3
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from
Package: grub-efi-amd64-signed
Version: 1+2.04+5
Severity: grave
grub-efi-amd64-signed got a strict = dependency on grub-common, but
those packages are from different source packages. This makes this
package uninstallable.
| The following information may help to resolve the situation:
|
| The f
Your message dated Fri, 24 Apr 2020 17:35:03 +
with message-id
and subject line Bug#955091: fixed in python-ceilometerclient 2.9.0-6
has caused the Debian Bug report #955091,
regarding python-ceilometerclient: FTBFS with Sphinx 2.4: AttributeError:
'Sphinx' object has no attribute 'info'
to b
Your message dated Fri, 24 Apr 2020 17:19:19 +
with message-id
and subject line Bug#955085: fixed in python-glareclient 0.5.3-6
has caused the Debian Bug report #955085,
regarding python-glareclient: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx'
object has no attribute 'info'
to be marked a
Your message dated Fri, 24 Apr 2020 17:18:54 +
with message-id
and subject line Bug#949780: fixed in navit 0.5.4+dfsg.1-3
has caused the Debian Bug report #949780,
regarding maptool: Maptool segfaults
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Fri, 24 Apr 2020 16:49:45 +
with message-id
and subject line Bug#955080: fixed in python-ceilometermiddleware 1.5.0-3
has caused the Debian Bug report #955080,
regarding python-ceilometermiddleware: FTBFS with Sphinx 2.4: AttributeError:
'Sphinx' object has no attribute 'in
Your message dated Fri, 24 Apr 2020 16:34:19 +
with message-id
and subject line Bug#955073: fixed in python-dracclient 3.1.0-3
has caused the Debian Bug report #955073,
regarding python-dracclient: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx'
object has no attribute 'info'
to be marked as
Your message dated Fri, 24 Apr 2020 16:19:35 +
with message-id
and subject line Bug#955062: fixed in python-k8sclient 0.3.0-4
has caused the Debian Bug report #955062,
regarding python-k8sclient: FTBFS with Sphinx 2.4: AttributeError: 'Sphinx'
object has no attribute 'info'
to be marked as do
Gilles Filippini a écrit le 24/04/2020 à 15:08 :
> On Sun, 26 Jan 2020 12:39:01 + ael wrote:
>> On Sat, Jan 25, 2020 at 06:26:35PM -0800, Joseph Herlant wrote:
>>> Hi,
>>>
>>>
>>> You mention in the bug there that you were able to run your pbf by
>>> compiling maptool from the git repo. What c
Your message dated Fri, 24 Apr 2020 15:21:21 +
with message-id
and subject line Bug#937115: fixed in nautilus-python 1.2.3-2
has caused the Debian Bug report #937115,
regarding nautilus-python: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem ha
Control: tag -1 pending
Hello,
Bug #937115 in nautilus-python 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/gnome-team/nautilus-python/-/commit/1663268c1e717d
Processing control commands:
> tag -1 pending
Bug #937115 [src:nautilus-python] nautilus-python: Python2 removal in
sid/bullseye
Added tag(s) pending.
--
937115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 24 Apr 2020 15:04:12 +
with message-id
and subject line Bug#958646: fixed in ffmpegfs 1.98-2
has caused the Debian Bug report #958646,
regarding ffmpegfs: FTBFS caused by passing custom target flags in CFLAGS
to be marked as done.
This means that you claim that the pro
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-an
Processing commands for cont...@bugs.debian.org:
> forwarded 936288 https://github.com/cfv-project/cfv/issues/8
Bug #936288 [src:cfv] cfv: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 'https://github.com/cfv-project/cfv/issues/8'.
> thanks
Stopping processing here.
Please conta
Control: tags 951969 + patch
Control: tags 951969 + pending
Dear maintainer,
I've prepared an NMU for social-auth-app-django (versioned as 3.1.0-2.1)
and uploaded it to DELAYED/14. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru social-auth-app-django-3.1.0/debian/change
Processing control commands:
> tags 951969 + patch
Bug #951969 [src:social-auth-app-django] social-auth-app-django: FTBFS:
dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7"
--system=custom "--test-args={interpreter} ./manage.py test" returned exit code
13
Added tag(s) patch.
>
On Sun, 26 Jan 2020 12:39:01 + ael wrote:
> On Sat, Jan 25, 2020 at 06:26:35PM -0800, Joseph Herlant wrote:
> > Hi,
> >
> >
> > You mention in the bug there that you were able to run your pbf by
> > compiling maptool from the git repo. What compilation flags did you
> > use?
>
> I just real
Processing commands for cont...@bugs.debian.org:
> affects 953875 + src:runit
Bug #953875 [apt] runit - default installation can force init switch
Added indication that 953875 affects src:runit
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
953875: https
Source: libgpuarray
Version: 0.7.6-5
Severity: serious
https://ci.debian.net/data/autopkgtest/unstable/amd64/libg/libgpuarray/5108972/log.gz
autopkgtest [03:47:06]: test command1: set -e ; for py in $(py3versions -r
2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ;
DEVICE=ope
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958683 958690 958681 958686 958691 958680 958693 958696
958695 958679 958689 958684 958682 958687 958685 958692
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958692 958685 958691 958680 958683 958689 958684 958687
958679 958695 958686 958682 958681 958690 958693 958694
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958679 958686 958680 958685 958682 958683 958684 958687
958681
956423 was not blocking any bugs.
Added blocking
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958691 958684 958682 958679 958690 958683 958687 958694
958681 958685 958688 958689 958693 958680 958686 958692
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958690 958685 958683 958684 958679 958687 958680 958682
958688 958689 958686 958681
956423 was not blocking any
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958680 958685 958684 958681 958683 958682 958686 958679
956423 was not blocking any bugs.
Added blocking bug(s) o
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958684 958689 958687 958682 958683 958688 958685 958690
958686 958691 958680 958679 958681
956423 was not blocki
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958682 958687 958690 958681 958688 958684 958680 958692
958679 958691 958689 958683 958686 958685
956423 was not
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958680 958687 958684 958686 958679 958682 958688 958683
958689 958681 958685
956423 was not blocking any bugs.
A
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958685 958687 958684 958682 958688 958680 958683 958681
958686 958679
956423 was not blocking any bugs.
Added bl
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958687 958679 958689 958686 958688 958681 958683 958685
958691 958693 958680 958682 958692 958690 958684
956423
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was not blocked by any bugs.
956423 was not blocking any bugs.
Added blocking bug(s) of 956423: 958679
--
956423: https://bugs.
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958680 958679 958683 958681 958684 958682
956423 was not blocking any bugs.
Added blocking bug(s) of 956423: 9586
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958679
956423 was not blocking any bugs.
Added blocking bug(s) of 956423: 958680
--
956423: https://bugs.debian
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958680 958679
956423 was not blocking any bugs.
Added blocking bug(s) of 956423: 958681
--
956423: https://bugs
Processing control commands:
> reassign -1 apt 2.0.2
Bug #953875 [src:runit] runit - default installation can force init switch
Bug reassigned from package 'src:runit' to 'apt'.
No longer marked as found in versions runit/2.1.2-35.
Ignoring request to alter fixed versions of bug #953875 to the sam
Followup-For: Bug #953875
Control: reassign -1 apt 2.0.2
Dear apt maintainers,
runit package has a recommends that is in the form
Recommends: runit-sysv | runit-init | runit-systemd
Runit-sysv needs sysvinit as init, and runit-systemd needs systemd as init.
The problem is that, when installing
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958680 958682 958679 958681
956423 was not blocking any bugs.
Added blocking bug(s) of 956423: 958683
--
956423
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958679 958681 958680
956423 was not blocking any bugs.
Added blocking bug(s) of 956423: 958682
--
956423: https
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958680 958681 958685 958684 958683 958679 958682
956423 was not blocking any bugs.
Added blocking bug(s) of 95642
Processing control commands:
> block 956423 by -1
Bug #956423 [node-request] node-request: deprecated upstream: should not be
part of next stable Debian release
956423 was blocked by: 958680 958682 958683 958681 958679
956423 was not blocking any bugs.
Added blocking bug(s) of 956423: 958684
--
Your message dated Fri, 24 Apr 2020 11:19:23 +
with message-id
and subject line Bug#958084: fixed in pajeng 1.3.6-1
has caused the Debian Bug report #958084,
regarding pajeng FTBFS on i386: pj_validate_simu-mardi (Failed)
to be marked as done.
This means that you claim that the problem has be
Control: tag -1 + confirmed
Processing control commands:
> tag -1 + confirmed
Bug #953875 [src:runit] runit - default installation can force init switch
Added tag(s) confirmed.
--
953875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Thu, Mar 26, 2020 at 04:52:42PM +0100, Matthias Klose wrote:
> Package: eclipse-titan
> Version: 6.6.1-1
> Severity: serious
> Tags sid bullseye
>
> eclipse-titan still encodes an upper dependency on gcc. The changelog says
> this
> is fixed upstream, nevertheless the package still has this de
Your message dated Fri, 24 Apr 2020 10:04:10 +
with message-id
and subject line Bug#945416: fixed in libb-cow-perl 0.004-1
has caused the Debian Bug report #945416,
regarding libb-cow-perl: fails to build (test failures) on big endian
to be marked as done.
This means that you claim that the p
> On Apr 14, 2020, at 9:44 AM, Adrian Bunk wrote:
>
> On Tue, Apr 07, 2020 at 10:04:09PM -0700, Andreas Jimmy Gredler wrote:
>
>> Thank you so much for taking care of this. Unfortunately I won’t be able to
>> maintain this package anymore and was looking into the process of handing it
>> ove
Control: reopen -1
Control: found -1 1.98-1
Processing control commands:
> reopen -1
Bug #958646 {Done: Norbert Schlia } [ffmpegfs]
ffmpegfs: FTBFS caused by passing custom target flags in CFLAGS
Bug reopened
Ignoring request to alter fixed versions of bug #958646 to the same values
previously set
> found -1 1.98-1
Bug #958646 [ffmpegfs]
Your message dated Fri, 24 Apr 2020 08:51:01 +
with message-id
and subject line Bug#955643: fixed in tripwire 2.4.3.7-3
has caused the Debian Bug report #955643,
regarding tripwire: FTBFS: dpkg-gencontrol: error: error occurred while parsing
Built-Using field: glibc (= 2.30-4), libgcc1 (= ),
Your message dated Fri, 24 Apr 2020 08:26:24 +
with message-id
<20200424082624.horde.pdqpwtfd1igdpweurfkd...@www.email-mania.eu>
and subject line Re: Bug#958646: ffmpegfs: FTBFS caused by passing custom
target flags in CFLAGS
has caused the Debian Bug report #958646,
regarding ffmpegfs: FTBFS
Your message dated Fri, 24 Apr 2020 08:22:25 +
with message-id
and subject line Bug#958421: fixed in node-boxen 4.2.0-3
has caused the Debian Bug report #958421,
regarding node-cli-boxes breaks node-boxen autopkgtest: TypeError: Invalid
border style: single-double
to be marked as done.
This
Your message dated Fri, 24 Apr 2020 08:22:30 +
with message-id
and subject line Bug#958421: fixed in node-cli-boxes 2.2.0-3
has caused the Debian Bug report #958421,
regarding node-cli-boxes breaks node-boxen autopkgtest: TypeError: Invalid
border style: single-double
to be marked as done.
T
Hi!
Thanks for your bug report. I have fixed the problem by removing the
-march command line upstream (for 1.99) and created a patch for
1.98-1. The next upload to stable should not have that problem.
Zitat von John Paul Adrian Glaubitz :
Package: ffmpegfs
Version: 1.98-1
Severity: serio
Source: jupyter-sphinx-theme
Version: 0.0.6+ds1-9
Severity: serious
Justification: Policy 5.6.30
Hi,
your package fails to run the autopkg test, this prevents the migration
of TL 2020 to testing. The failure is probably caused by the upload of
Sphinx 2.4.3. to unstable.
Please be so kind to have
90 matches
Mail list logo
