Your message dated Thu, 05 Mar 2020 12:04:09 +
with message-id
and subject line Bug#952014: fixed in freedink 109.6-3
has caused the Debian Bug report #952014,
regarding freedink: FTBFS: input.cpp:94:15: error:
‘SDL_HINT_ANDROID_SEPARATE_MOUSE_AND_TOUCH’ was not declared in this scope
to be
Source: sdpa
Version: 7.3.12+dfsg-1
Severity: serious
Hello, hardcoding the mumps library as runtime dependency breaks binNMUs, and
it is actually keeping your package out from testing.
Please let shlibs find the dependency if required, or if needed but not linked,
ask mumps people to add a
Processing control commands:
> fixed -1 4.0.0+really3.0.0-1
Bug #953168 [src:node-acorn-dynamic-import] src:node-acorn-dynamic-import:
fails to migrate to testing for too long
Marked as fixed in versions node-acorn-dynamic-import/4.0.0+really3.0.0-1.
--
953168:
Source: node-acorn-dynamic-import
Version: 3.0.0-1
Severity: serious
Control: fixed -1 4.0.0+really3.0.0-1
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
Hi Santiago,
On Thu, 2020-03-05 at 09:41 +0100, Santiago R.R. wrote:
>
> Hi Ritesh,
>
> When trying to upload I realized the format of the package is that of
> a
> native package, but the version has a revision at the same time.
> Which I
> think it is unusual.
> I don't understand how the
Your message dated Thu, 05 Mar 2020 13:19:38 +
with message-id
and subject line Bug#89: fixed in kvmtool 0.20170904-1.1
has caused the Debian Bug report #89,
regarding kvmtool: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Control: tags 89 + patch
Control: tags 89 + pending
Dear maintainer,
I've prepared an NMU for kvmtool (versioned as 0.20170904-1.1) and
uploading it to mentors for sponsoring. Please feel free to tell me if I
should remove it from mentors.
Note:
The upstream is almost active for this
Processing control commands:
> tags 89 + patch
Bug #89 [src:kvmtool] kvmtool: ftbfs with GCC-8
Added tag(s) patch.
> tags 89 + pending
Bug #89 [src:kvmtool] kvmtool: ftbfs with GCC-8
Added tag(s) pending.
--
89: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=89
Debian
Harald Dunkel writes ("Re: new network-manager-strongswan package [and 1 more
messages]"):
> I have pushed n-m-s 1.4.5-1 to salsa, without touching the label.
> Worked very well.
>
> Next I created version 1.4.5-2 (no tag yet) to fix the issues you
> mentioned (Vcs-git, git format-patch).
Ian Jackson writes ("Re: new network-manager-strongswan package [and 1 more
messages]"):
> Rather than going another round with you I propose to fix this as
> follows:
> 1. upload your version as-is
> 2. immediately "nmu" an upload to only fix the previous changelog
>
> I chose to do this
Processing control commands:
> fixed -1 1.27.0-4
Bug #953173 [src:mp3cd] src:mp3cd: fails to migrate to testing for too long
Marked as fixed in versions mp3cd/1.27.0-4.
--
953173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953173
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Source: mp3cd
Version: 1.27.0-3
Severity: serious
Control: fixed -1 1.27.0-4
Tags: sid bullseye pending
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 testing
Source: aspell-mr
Version: 0.10-9
Severity: serious
Control: fixed -1 0.10-10
Tags: sid bullseye pending
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 testing
Processing control commands:
> fixed -1 0.10-10
Bug #953174 [src:aspell-mr] src:aspell-mr: fails to migrate to testing for too
long
Marked as fixed in versions aspell-mr/0.10-10.
--
953174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953174
Debian Bug Tracking System
Contact
Processing control commands:
> tag -1 pending
Bug #953008 [src:talloc] talloc: ftbfs with python3.8
Added tag(s) pending.
--
953008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #953008 in talloc 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 #953008 [src:talloc] talloc: ftbfs with python3.8
Ignoring request to alter tags of bug #953008 to the same tags previously set
--
953008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953008
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #953008 in talloc 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:
El 26/02/20 a las 11:10, Santiago R.R. escribió:
> Hi Ritesh,
>
> I've just made another MR to modify the changelog entry.
>
> Also, please, remember to create a tag for the release once it get
> approved (and uploaded).
Hi Ritesh,
When trying to upload I realized the format of the package is
Control: tags -1 pending
Hi,
I have updated lazyarray in Git[1] (by moving it to Debian Science
team). The old package was lagging way behind upstream and a Python3
port is available by upstream so I just create the python3-lazyarray
package fixing the open bugs.
Unfortunately there is an open
Processing control commands:
> tags -1 pending
Bug #936825 [src:lazyarray] lazyarray: Python2 removal in sid/bullseye
Added tag(s) pending.
--
936825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Thu, 5 Mar 2020, 14:16 Andreas Tille, wrote:
> Control: tags -1 pending
>
> Hi,
>
> I have updated lazyarray in Git[1] (by moving it to Debian Science
> team). The old package was lagging way behind upstream and a Python3
> port is available by upstream so I just create the python3-lazyarray
Processing commands for cont...@bugs.debian.org:
> block 911166 with 885677 885685
Bug #911166 [src:gtksourceview2] gtksourceview2: Do not release with Bullseye
911166 was blocked by: 885675 911167 885678 890456 911164 885676 885681
911166 was not blocking any bugs.
Added blocking bug(s) of
Le 22/10/2019 à 19:20, Michael Meier a écrit :
> java -dvecm can't be executed anymore:
>
> java -dcevm
> java: relocation error: /usr/lib/jvm/java-11-openjdk-amd64/lib/libjava.so:
> symbol JVM_InitializeFromArchive version SUNWprivate_1.1 not defined in file
> libjvm.so with link time reference
Your message dated Thu, 05 Mar 2020 09:20:15 +
with message-id
and subject line Bug#951885: fixed in nitpic 0.1-17
has caused the Debian Bug report #951885,
regarding nitpic FTBFS with binutils 2.34
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Thanks Alvin,
we already did that in BIND 9.16+, so I merged the change in BIND 9.11 branch
and it will be included in the next BIND 9 release.
I’ll speak to the release team if we will ignore it for Debian stable, or we
will
have to do the dance with dfsg tarball.
Ondrej
--
Ondřej Surý
Your message dated Thu, 05 Mar 2020 10:10:20 +
with message-id
and subject line Bug#953008: fixed in talloc 2.3.0-4
has caused the Debian Bug report #953008,
regarding talloc: ftbfs with python3.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> severity 940536 grave
Bug #940536 [dhex] dhex: hangs on keyboard config screen
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
940536:
Your message dated Thu, 05 Mar 2020 09:22:31 +
with message-id
and subject line Bug#952208: fixed in python-ftputil 3.4-3
has caused the Debian Bug report #952208,
regarding python-ftputil: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.7" returned exit
Package: gyoto
Version: 1.4.4-1
Severity: serious
gyoto is failing to build on armel, armhf, mipsel and mips64el
the error in the arm build logs seems to be:
Test reference counting ... SEVERE: Cannot convert to seconds as metric is not
set!
SEVERE: Cannot convert to seconds as metric is
Processing commands for cont...@bugs.debian.org:
> forwarded 951768 https://github.com/scikit-image/scikit-image/issues/4492
Bug #951768 [src:skimage] skimage documentation build fails with python 3.8
Set Bug forwarded-to-address to
'https://github.com/scikit-image/scikit-image/issues/4492'.
>
Dear Gianfranco Costamagna,
Thank you very much for checking our package.
Unfortunately, it is outside of this package, and we cannot do anything for
your comment,
so please close this bug.
Thanks.
Makoto
2020年3月5日(木) 21:15 Gianfranco Costamagna :
> Source: sdpa
> Version: 7.3.12+dfsg-1
>
On 3/4/20 1:12 PM, Moritz Mühlenhoff wrote:
> On Tue, Mar 03, 2020 at 05:56:18PM -0600, Ryan Pavlik wrote:
>> armel and armhf: these platforms only have OpenGL-ES, not desktop
>> OpenGL, so the correct thing to do is to disable this package on those
>> platforms. Is there a better way to do this
Processing control commands:
> fixed -1 0.01-1-6
Bug #953177 [src:aspell-pa] src:aspell-pa: fails to migrate to testing for too
long
Marked as fixed in versions aspell-pa/0.01-1-6.
--
953177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953177
Debian Bug Tracking System
Contact
Source: aspell-pa
Version: 0.01-1-5
Severity: serious
Control: fixed -1 0.01-1-6
Tags: sid bullseye pending
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
Source: rust-findshlibs
Version: 0.4.0-2
Severity: serious
Control: fixed -1 0.5.0-1
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 testing
Le 05/03/2020 à 10:49, peter green a écrit :
> Package: gyoto
> Version: 1.4.4-1
> Severity: serious
>
> gyoto is failing to build on armel, armhf, mipsel and mips64el
Thanks Peter,
I've been working on it since Monday. I think I found the bug that hits
arm*, now I will check for mips*.
Your message dated Thu, 05 Mar 2020 14:47:55 +
with message-id
and subject line Bug#945567: fixed in network-manager-strongswan 1.4.5-2
has caused the Debian Bug report #945567,
regarding network-manager-strongswan FTBFS: error: G_ADD_PRIVATE
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> notfixed 942120 17.1.2-3
Bug #942120 {Done: Sandro Tosi } [python3-zmq] python3-zmq:
pypy3 -m ipykernel install ... fails with No module named zmq.backend.cffi
No longer marked as fixed in versions pyzmq/17.1.2-3.
> found 953138 8.0.19+dfsg-1
Your message dated Thu, 05 Mar 2020 15:04:06 +
with message-id
and subject line Bug#953119: fixed in mtj 0.9.14+dfsg-7
has caused the Debian Bug report #953119,
regarding mtj: Please make another source-only upload to allow testing migration
to be marked as done.
This means that you claim
Processing control commands:
> fixed -1 0.5.0-1
Bug #953178 [src:rust-findshlibs] src:rust-findshlibs: fails to migrate to
testing for too long
Marked as fixed in versions rust-findshlibs/0.5.0-1.
--
953178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953178
Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:
> forwarded 951723 https://jira.mongodb.org/browse/PYTHON-2150
Bug #951723 [src:pymongo] pymongo: FTBFS: test failures on 32 bit architectures
Set Bug forwarded-to-address to 'https://jira.mongodb.org/browse/PYTHON-2150'.
> thanks
Stopping
Your message dated Thu, 05 Mar 2020 21:49:57 +
with message-id
and subject line Bug#952454: fixed in coq 8.11.0-1
has caused the Debian Bug report #952454,
regarding coq: patch to use python3 (missing tests)
to be marked as done.
This means that you claim that the problem has been dealt
Package: Redmine
Version: 4.0.6-2
Severity: grave
Justification: renders package unusable
The following error is produced when upgrading from 4.0.4-3 to 4.0.6-2. This
leaves the package in an unusable state.
dpkg --configure -a
Setting up redmine (4.0.6-2) ...
Determining localhost credentials
Processing commands for cont...@bugs.debian.org:
> unarchive #879937
Bug #879937 {Done: Mike Gabriel } [src:libqtdbustest]
libqtdbustest: FTBFS: unit test fails with BadAddress DBusException
Unarchived Bug 879937
> unarchive #896494
Bug #896494 {Done: Mike Gabriel } [src:libqtdbusmock]
FTBFS:
hey,
tried version 6.0.0-1 from experimental and problem is solved.
if i'm not mistaken, it was fixed upstream since 5.9.0
(https://bugzilla.redhat.com/show_bug.cgi?id=1760233#c8 ).
using openrc, elogind with MATE.
thx,
d.
On Sat, 07 Dec 2019 13:41:07 +0100 Thorsten Glaser wrote:
> Package:
Control: tag -1 pending
Hello,
Bug #951894 in jpylyzer 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 #951894 [src:jpylyzer] jpylyzer FTBFS: test_get_files failure
Added tag(s) pending.
--
951894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Fri, Aug 30, 2019 at 07:49:21AM +, Matthias Klose wrote:
> Package: src:pyxnat
> Version: 1.0.1.0-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
Processing commands for cont...@bugs.debian.org:
> notfixed 952454 8.10.2-1
Bug #952454 [src:coq] coq: patch to use python3 (missing tests)
No longer marked as fixed in versions coq/8.10.2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
952454:
Control: tags 951887 + patch
Control: tags 951887 + pending
Dear maintainer,
I've prepared an NMU for mutrace (versioned as 0.2.0-3.1) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it from mentors.
--
Regards
Sudip
diff -u
Processing control commands:
> tags 951887 + patch
Bug #951887 [src:mutrace] mutrace FTBFS with binutils 2.34
Added tag(s) patch.
> tags 951887 + pending
Bug #951887 [src:mutrace] mutrace FTBFS with binutils 2.34
Added tag(s) pending.
--
951887:
OK, I got a chance to build aarch64 and it does build there.
Unfortunately I hit a more fundamental error with armhf, that it has
type mismatches when trying to use GLEW. Not sure if this is intrinsic
or if it can be solved: the last version that was in Debian was a long
time ago...
This error
Your message dated Thu, 05 Mar 2020 20:43:55 +
with message-id
and subject line Bug#951894: fixed in jpylyzer 2.0.0-3
has caused the Debian Bug report #951894,
regarding jpylyzer FTBFS: test_get_files failure
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> fixed -1 1.5-1
Bug #953190 [src:prometheus-varnish-exporter] src:prometheus-varnish-exporter:
fails to migrate to testing for too long
Marked as fixed in versions prometheus-varnish-exporter/1.5-1.
--
953190:
Source: prometheus-varnish-exporter
Version: 1.4.1-1
Severity: serious
Control: fixed -1 1.5-1
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
Source: libgphoto2
Version: 2.5.22-3
Severity: serious
Control: fixed -1 2.5.23-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 testing and
Processing control commands:
> reopen -1
Bug #935927 {Done: Adrian Bunk } [src:debian-science]
debian-science: migrate all python dependencies to their python3 variant
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to
Control: reopen -1
This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:
(binary:science-numericalcomputation)Recommends->ipython
Re-opening, so that they can be taken care of.
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
> # olefile
> block 937187 by 953220
Bug
Control: reopen -1
This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:
(source:libgnatcoll-bindings)Build-Depends->python2-dev
(source:libgnatcoll-bindings)Build-Depends->libpython2-dev
(binary:libgnatcoll-python18-dev)Depends->libpython2-dev
Processing control commands:
> reopen -1
Bug #936869 {Done: Ludovic Brenta }
[src:libgnatcoll-bindings] libgnatcoll-bindings: Python2 removal in sid/bullseye
Bug reopened
Ignoring request to alter fixed versions of bug #936869 to the same values
previously set
--
936869:
Processing commands for cont...@bugs.debian.org:
> unarchive 935927
Bug #935927 {Done: Adrian Bunk } [src:debian-science]
debian-science: migrate all python dependencies to their python3 variant
Unarchived Bug 935927
>
End of message, stopping processing here.
Please contact me if you need
Processing control commands:
> merge 951893 -1
Bug #951893 [src:subversion] subversion FTBFS with swig 4.0.1
Unable to merge bugs because:
severity of #953057 is 'important' not 'serious'
Failed to merge 951893: Did not alter merged bugs.
--
951893:
Processing control commands:
> tags 952237 + patch
Bug #952237 [src:courier-unicode] courier-unicode: FTBFS: dpkg-gensymbols:
error: some new symbols appeared in the symbols file: see diff output below
Bug #925658 [src:courier-unicode] courier-unicode: ftbfs with GCC-9
Added tag(s) patch.
Added
Control: tags 952237 + patch
Control: tags 952237 + pending
Dear maintainer,
I've prepared an NMU for courier-unicode (versioned as 2.1-3.1) and
uploaded it to mentors for sponsoring. Please feel free to tell me if I
should remove it from mentors.
--
Regards
Sudip
diff -Nru
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
Your message dated Fri, 06 Mar 2020 05:19:06 +
with message-id
and subject line Bug#952505: fixed in ocaml-qtest 2.10.1-2
has caused the Debian Bug report #952505,
regarding ocaml-qtest: autopkgtests regression
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> tags 952811 +moreinfo
Bug #952811 [apt-cacher-ng] [apt-cacher-ng] 500 Bad redirection (path)
Added tag(s) moreinfo.
--
952811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 952811 +moreinfo
Hallo,
* Jean-Marc LACROIX [Sat, Feb 29 2020, 05:25:53PM]:
> Package: apt-cacher-ng
> Version: 3.2-2
> Severity: grave
That's hardly grave because not clearly reproducible. But I have seen
this 502 in development a couple of times, appeared and disappeared
without
On Thu, Feb 13, 2020 at 10:44:47PM +0100, Moritz Mühlenhoff wrote:
> On Fri, Aug 30, 2019 at 07:17:13AM +, Matthias Klose wrote:
> > Package: src:flashproxy
> > Version: 1.7-4
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
> >
> >
Processing control commands:
> severity -1 normal
Bug #950177 [src:source-highlight] source-highlight: FTBFS: make test fails
Severity set to 'normal' from 'grave'
> retitle -1 "make check" fails non-deterministically on arm64
Bug #950177 [src:source-highlight] source-highlight: FTBFS: make test
Control: severity -1 normal
Control: retitle -1 "make check" fails non-deterministically on arm64
On Wednesday, January 29 2020, Boyuan Yang wrote:
> Dear source-highlight maintainer,
>
> Currently source-highlight would FTBFS due to errors when running "make test"
> after build:
>
>
Your message dated Thu, 5 Mar 2020 18:59:57 -0700
with message-id
and subject line Bug#951702: not subvertpy's bug; build fine on s390x and ppc64
now
has caused the Debian Bug report #951702,
regarding subvertpy ftbfs on 64bit big endian targets
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> merge 952237 925658
Bug #952237 [src:courier-unicode] courier-unicode: FTBFS: dpkg-gensymbols:
error: some new symbols appeared in the symbols file: see diff output below
Bug #925658 [src:courier-unicode] courier-unicode: ftbfs with GCC-9
Added
Processing control commands:
> reopen -1
Bug #879937 {Done: Mike Gabriel } [src:libqtdbustest]
libqtdbustest: FTBFS: unit test fails with BadAddress DBusException
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to
I pushed a new version (3.5.0.1) to salsa.
It builds on my machine with pbuilder and has only two minor lintian
warnings (empty directory, imaginary(?) misspelling).
I had to update the copyright file because I'm using the immer library,
which is under BSL-1.0.
-BenRI
Your message dated Fri, 06 Mar 2020 00:19:18 +
with message-id
and subject line Bug#949822: fixed in fontforge 1:20190801~dfsg-3
has caused the Debian Bug report #949822,
regarding fontforge needs to link with the embedded libs
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 06 Mar 2020 00:19:18 +
with message-id
and subject line Bug#953079: fixed in fontforge 1:20190801~dfsg-3
has caused the Debian Bug report #953079,
regarding fontforge: FTBFS: builds with Python 2.7 by default if it is present
and build then fails
to be marked as done.
Package: libreadline-dev
Version: 7.0.5
Severity: grave
--- Please enter the report below this line. ---
The libreadline-dev file for debian stable lacks a .pc file, so it is
not possible to compile programs using CMake or Meson/Ninja if they
check for it.
Debian SID package has it.
---
It's disappointing to see Emacs 26.3 fail to propagate to Debian testing for
the best part of six months due to this issue.
This "FTBS" is a single test failure on mips, in test set-process-filter-t.
This test is not present prior to Emacs 26.3.
It was added for https://debbugs.gnu.org/36591 , so
Control: reopen -1
On Mon, 04 Feb 2019 10:04:17 + Mike Gabriel wrote:
* debian/rules:
+ Ignore test failures. Locally, tests always succeed. Only on Debian's
buildd infrastructure, test failures can be observed at random. This
is not beautiful, but alas. (Closes: #879937).
Let's reopen
Your message dated Fri, 06 Mar 2020 01:05:22 +
with message-id
and subject line Bug#946992: fixed in dcmstack 0.8-1
has caused the Debian Bug report #946992,
regarding python3-dcmstack: missing Breaks+Replaces: python-dcmstack
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 05 Mar 2020 22:48:58 +0100
with message-id <87v9nia2wl.fsf@samuel>
and subject line libgnatcoll-bindings: Python2 removal in sid/bullseye
has caused the Debian Bug report #936869,
regarding libgnatcoll-bindings: Python2 removal in sid/bullseye
to be marked as done.
This
Your message dated Fri, 06 Mar 2020 00:19:18 +
with message-id
and subject line Bug#948016: fixed in fontforge 1:20190801~dfsg-3
has caused the Debian Bug report #948016,
regarding fontforge: b-d on python3-all-dev, but not built for all supported
Python3 versions
to be marked as done.
This
Package: fuse
Version: 2.9.9-1
Severity: serious
Hi,
I discovered today that for some reasons the /etc/fuse.conf (conffile)
was missing on my machine while I didn't remember deleting it myself.
After some investigations I discovered that both the fuse and fuse3 are
providing /etc/fuse.conf and
Package: fuse3
Version: 3.9.0-1
Severity: serious
Hi,
I discovered today that for some reasons the /etc/fuse.conf (conffile)
was missing on my machine while I didn't remember deleting it myself.
After some investigations I discovered that both the fuse and fuse3 are
providing /etc/fuse.conf and
Processing commands for cont...@bugs.debian.org:
> found 953223 3.4.1-1
Bug #953223 [fuse3] Stop explicitly removing /etc/fuse.conf on purge
Marked as found in versions fuse3/3.4.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
953223:
Processing control commands:
> fixed -1 6.2.0-4
Bug #953180 [src:puppetdb] src:puppetdb: fails to migrate to testing for too
long
Marked as fixed in versions puppetdb/6.2.0-4.
--
953180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953180
Debian Bug Tracking System
Contact
Source: rust-glob
Version: 0.2.11-1
Severity: serious
Control: fixed -1 0.3.0-1
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 testing and
Processing control commands:
> fixed -1 0.3.0-1
Bug #953179 [src:rust-glob] src:rust-glob: fails to migrate to testing for too
long
Marked as fixed in versions rust-glob/0.3.0-1.
--
953179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953179
Debian Bug Tracking System
Contact
Source: puppetdb
Version: 6.2.0-3
Severity: serious
Control: fixed -1 6.2.0-4
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 testing and
Your message dated Thu, 05 Mar 2020 15:35:10 +
with message-id
and subject line Bug#945567: fixed in network-manager-strongswan 1.4.5-2.1
has caused the Debian Bug report #945567,
regarding network-manager-strongswan FTBFS: error: G_ADD_PRIVATE
to be marked as done.
This means that you claim
Source: ndpi
Version: 2.6-5
Severity: serious
Control: fixed -1 3.0-1
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 testing and unstable for
Processing control commands:
> fixed -1 3.0-1
Bug #953181 [src:ndpi] src:ndpi: fails to migrate to testing for too long
Marked as fixed in versions ndpi/3.0-1.
--
953181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> tag -1 pending
Bug #951829 [src:openvdb] replace python3-all-dev with python3.7-dev
Added tag(s) pending.
--
951829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #951829 in openvdb 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:
Hi,
On Tue, Mar 03, 2020 at 04:22:47PM +0100, Michael R. Crusoe wrote:
> At
> https://salsa.debian.org/r-pkg-team/r-cran-xml2/-/commit/e973a8d9500dc3a98e34dcd5eb7e86cf5b692bb6
> I've commited a fix for this bug.
>
>
> If a DD could sponsor that upload or grant me upload rights, I would
>
On Thu, Mar 05, 2020 at 02:27:13PM +0530, Nilesh Patra wrote:
>
> I had tried this,
> I think Passing [:-1] in the mask2 initialisation would fix this. We also
> need to cast this into a numpy array.
> ...
>
> I'll try this by midnight today. If I can, I'll try a fix for this, and
> make a MR,
Processing control commands:
> fixed -1 0.8.5-2
Bug #953188 [src:mailavenger] src:mailavenger: fails to migrate to testing for
too long
Marked as fixed in versions mailavenger/0.8.5-2.
--
953188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953188
Debian Bug Tracking System
Contact
1 - 100 of 133 matches
Mail list logo
