No plans for Qt5 whatsoever.
The only thing to note here is that Qt is actually optional for the vast
majority of CMTK's tools. The package config could probably be changed to
build without GUI support, which would remove the dependency on Qt.
Am Do., 31. Okt. 2019 um 15:57 Uhr schrieb Moritz
Hi, people.
On Oct 31 2019, Hugo Lefeuvre wrote:
> bleachbit (3.0-1) unstable; urgency=medium
>
>[ Hugo Lefeuvre ]
(...)
> - Remove pygtk dependency, upstream moved to GTK 3 as part of the 3.0
>release (Closes: #885261).
(...)
Thank you very much for this upload!
Cheers,
Hi,
Ben Hutchings wrote:
> On Sun, 2019-10-27 at 20:18 +0100, Holger Wansing wrote:
> > Bugreport against kernel version mismatch, when using outdated or broken
> > netboot images:
> >
> >
> > Since it's unlikely that we completely prevent this issue to happen, maybe
> > we
> > could at
Source: cvc3
Severity: serious
Should cvc3 be removed? It's unmaintained (last maintainer upload is from 2014
and the maintainer is also
one of the authors) and FTBFSes since 1.5 years.
Cheers,
Moritz
On Sat, Sep 09, 2017 at 11:06:18PM +0200, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Source: qjoypad
> Version: 4.1.0-2.1
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
>
>
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as
On Sat, Sep 09, 2017 at 09:03:16PM +0200, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Source: cmtk
> Version: 3.3.1-1.2
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
>
>
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as
On Sat, Sep 09, 2017 at 09:04:55PM +0200, Lisandro Damián Nicanor Pérez Meyer
wrote:
> Source: freemat
> Version: 4.2+dfsg1-1
> 4.2+dfsg1-5
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
>
>
> Hi! As you might know we the Qt/KDE team are preparing to remove
Le 31/10/2019 à 22:51, Samuel Thibault a écrit :
Source: llvm-toolchain-8
Version: 1:8.0.1-3
Severity: serious
Justification: FTBFS
Hello,
Since the migration of gcc-defaults to gcc-9, llvm-toolchain-8 FTBFS,
with
CMake Error at tools/polly/lib/External/CMakeLists.txt:91 (message):
No
Source: llvm-toolchain-8
Version: 1:8.0.1-3
Severity: serious
Justification: FTBFS
Hello,
Since the migration of gcc-defaults to gcc-9, llvm-toolchain-8 FTBFS,
with
CMake Error at tools/polly/lib/External/CMakeLists.txt:91 (message):
No ffs implementation found
looking at CMakeError.log,
reassign 935902 g++-9
affects 935902 libcppunit-dev
found 935902 9.2.1-12
close 935902 9.2.1-16
thanks
Hi,
On Thu, Oct 31, 2019 at 03:15:10PM +0100, Matthias Klose wrote:
> The comment about cppunit made me look at the cppunit package to find
> #935902, and yes, the test case is reproducible. So
On Thu, Oct 24, 2019 at 10:39:33PM +0200, Matthias Klose wrote:
> the autopkg test calls python instead of python2. This will make the package
> fail the next binNMU when adding python3.8 support.
I think I will instead have the test run python3, since python2 is
possibly being removed soon.
Processing control commands:
> notfound -1 twolame/0.4.0-2
Bug #943900 [src:twolame, src:ffmpeg] twolame breaks ffmpeg autopkgtest:
twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.
No longer marked as found in versions twolame/0.4.0-2.
--
943900:
Control: notfound -1 twolame/0.4.0-2
Hi
On 2019-10-31 16:37:11, Paul Gevers wrote:
> Source: twolame, ffmpeg
> Control: found -1 twolame/0.4.0-2
> Control: found -1 ffmpeg/7:4.2.1-1
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User:
On Sun, Sep 29, 2019 at 10:23:44PM +0200, Moritz Muehlenhoff wrote:
> Source: monotone
> Severity: serious
>
> Should monotone be removed? Dead upstream, last upload three years ago
> and removed from testing since 1.5 years.
I've now filed a removal bug.
Cheers,
Moritz
Hello,
On Thu 31 Oct 2019 at 04:30PM +00, kpcyrd wrote:
> This has been fixed in our git repo, but we're still waiting for the
> previous upload to go through the NEW queue before we can upload the fix
> for this.
Thanks for the fix! You can make another upload to NEW and it will
(effectively)
Your message dated Thu, 31 Oct 2019 20:53:52 +
with message-id
and subject line Bug#943623: fixed in llvm-toolchain-9 1:9.0.0-3
has caused the Debian Bug report #943623,
regarding objects in libclangIndex.a are llvm ir bitcode
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 31 Oct 2019 20:53:52 +
with message-id
and subject line Bug#942864: fixed in llvm-toolchain-9 1:9.0.0-3
has caused the Debian Bug report #942864,
regarding llvm-toolchain-9: FTBFS on i386: tries to ld -r amd64 code
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> # Part of the effort for the removal of python from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # laditools
> block 936813 by 939106
Bug #936813 [src:laditools] laditools:
Severity 936207 serious
thanks
biosig4c++ build-depends on the python-pkgconfig binary package which is no
longer built by the python-pkgconfig source package.
Processing commands for cont...@bugs.debian.org:
> Severity 936207 serious
Bug #936207 [src:biosig4c++] biosig4c++: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936207:
Your message dated Thu, 31 Oct 2019 20:10:58 +
with message-id
and subject line Bug#943765: fixed in gdcm 3.0.3-1~exp2
has caused the Debian Bug report #943765,
regarding libvtkgdcm3-dev: missing Breaks+Replaces: libvtkgdcm2-dev
to be marked as done.
This means that you claim that the
Hi,
I vouch that there seems to be a serious issue in libsqlite3 3.30.1-1.
I came here because it seems that I have an issue with sqlite3 on my
linux installation.
The problem manifested as database operation failures during thunderbird
mail client regression testing (called mach
On 2019-10-31 8:36 p.m., Petra R.-P. wrote:
> Am Do., 31. Okt. 2019, um 18:01 +0100 schrieb Michel Dänzer
> :
>> On 2019-10-30 2:15 p.m., Petra R.-P. wrote:
>
>> This happens when HW acceleration is disabled. If you can't or don't
>> want to enable HW acceleration,
> I can't because I don't
Am Do., 31. Okt. 2019, um 18:01 +0100 schrieb Michel Dänzer
:
> On 2019-10-30 2:15 p.m., Petra R.-P. wrote:
> This happens when HW acceleration is disabled. If you can't or don't
> want to enable HW acceleration,
I can't because I don't know how to do this.
> I recommend using the Xorg
Processing commands for cont...@bugs.debian.org:
> # Part of the effort for the removal of python from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # laditools
> block 936813 by 939106
Bug #936813 [src:laditools] laditools:
Processing commands for cont...@bugs.debian.org:
> Severity 937657 serious
Bug #937657 [src:python-colormap] python-colormap: Python2 removal in
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937657:
Your message dated Thu, 31 Oct 2019 18:04:58 +
with message-id
and subject line Bug#941641: fixed in acl2 8.1dfsg-4
has caused the Debian Bug report #941641,
regarding acl2: Build-Depends on emacs25 which has been removed from
unstable/bullseye
to be marked as done.
This means that you
Package: python-easydev
Version: 0.9.38-1
Severity: serious
The release team have decreed that non-buildd binaries can no longer migrate to
testing. Please Make a source-only upload so your package can migrate.
Followup-For: Bug #943761
Furthermore, python3-nototools is missing Breaks+Replaces: python-nototools
Preparing to unpack .../python3-nototools_0.2.0-1_all.deb ...
Unpacking python3-nototools (0.2.0-1) ...
dpkg: error processing archive
Package: squid
Version: 4.8-1
Severity: serious
The release team have decreed that non-buildd binaries can no longer migrate to
testing. Please make a source-only upload so your package can migrate.
I notice that in addition to the complaints about nettle deprecation there is
also a complaint about the use of memmove, unfortunately the compiler doesn't
say what exactly it doesn't like about the use of memmove.
In raspbian I decided to go ahead and remove -Werror, a debdiff doing that
tags 943566 +patch
thanks
Currently the nettle 3.5.1 transition is going on. I tried to binNMU
your package but it fails to build from source on all architectures.
I had a fiddle around with the order of includes and this led me to some
different error messages which led me to the real
Processing commands for cont...@bugs.debian.org:
> tags 943566 +patch
Bug #943566 [src:pktanon] FTBFS with nettle 3.5.1
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
943566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943566
Debian Bug
On 2019-10-30 2:15 p.m., Petra R.-P. wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:19.1.0-1
> Followup-For: Bug #943664
>
> Dear Maintainer,
>
> I can confirm every detail of the original report,
> except that this happens here on an old IBM Thinkpad T 41.
This happens when HW
Processing commands for cont...@bugs.debian.org:
> severity 935156 important
Bug #935156 [ceph] ceph: Multiple mon deployment failure on arm64:
ms_verfity_authorizer bad authorizer and crc check failure
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
> # Part of the effort for the removal of python from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # laditools
> block 936813 by 939106
Bug #936813 [src:laditools] laditools:
On Wed, Oct 30, 2019 at 06:11:47PM -0700, Sean Whitton wrote:
> There are some inaccuracies in d/copyright. I'm filing this bug at RC
> severity because the MIT license requires all copyright claims to be
> collated in d/copyright.
>
> (The package is dual-licensed under Apache-2.0, which the
Your message dated Thu, 31 Oct 2019 15:51:21 +
with message-id
and subject line Bug#942269: fixed in ossim 2.9.1-2
has caused the Debian Bug report #942269,
regarding ossim: FTBFS with GEOS 3.8.0 (error: no matching function for call)
to be marked as done.
This means that you claim that the
Processing control commands:
> found -1 twolame/0.4.0-2
Bug #943900 [src:twolame, src:ffmpeg] twolame breaks ffmpeg autopkgtest:
twolame_init_params(): 384kbps is an invalid bitrate for mono encoding.
Marked as found in versions twolame/0.4.0-2.
> found -1 ffmpeg/7:4.2.1-1
Bug #943900
Source: twolame, ffmpeg
Control: found -1 twolame/0.4.0-2
Control: found -1 ffmpeg/7:4.2.1-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainers,
With a recent upload of twolame the
Le 31/10/2019 à 16:11, Paolo Greppi a écrit :
See:
https://salsa.debian.org/debian/doxygen/-/jobs/393296
ar x /usr/lib/llvm-9/lib/libclangTooling.a
file *.o
yeah, I am aware ;)
The version in experimental should be ok
S
Package: ndisgtk
Severity: serious
Should ndisgtk be removed?
It's dead upstream (no release for 10 years) and depends on outdated stacks
scheduled for removal
(python 2, pygtk).
Cheers,
Moritz
See:
https://salsa.debian.org/debian/doxygen/-/jobs/393296
ar x /usr/lib/llvm-9/lib/libclangTooling.a
file *.o
AllTUsExecution.cpp.o: LLVM IR bitcode
ArgumentsAdjusters.cpp.o:LLVM IR bitcode
CommonOptionsParser.cpp.o: LLVM IR bitcode
Your message dated Thu, 31 Oct 2019 11:08:05 -0400
with message-id
and subject line Re: Bug#821795: lttng-modules-dkms: module FTBFS in jessie
against Linux 3.16: error: conflicting types for 'trace_mm_page_alloc_extfrag'
has caused the Debian Bug report #821795,
regarding lttng-modules-dkms:
Your message dated Thu, 31 Oct 2019 14:49:30 +
with message-id
and subject line Bug#943840: fixed in rrdtool 1.7.2-3
has caused the Debian Bug report #943840,
regarding python3-rrdtool-dbg: missing Breaks+Replaces: rrdtool-dbg
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 31 Oct 2019 14:47:34 +
with message-id
and subject line Bug#943838: fixed in grml2usb 0.17.0
has caused the Debian Bug report #943838,
regarding grml2usb: check_for_fat() always fails
to be marked as done.
This means that you claim that the problem has been dealt
>> And afaik there was no test rebuild for bullseye
>> either.
>
> It does not help to blame people for not doing a rebuild when there is no
rebuild necessary.
Please could you turn off your mode feeling attacked by any email, before you
understood these?
On 31.10.19 15:33,
Processing commands for cont...@bugs.debian.org:
> # Part of the effort for the removal of python from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # chardet
> block 936289 by 936214
Bug #936289 [src:chardet] chardet: Python2
Hi,
Am 31. Oktober 2019 15:15:10 MEZ schrieb Matthias Klose :
>And afaik there was no test rebuild for
>bullseye
>either.
Accepted cppunit 1.14.0-4 (source) into unstable
On July 26:
https://tracker.debian.org/news/1049803/accepted-cppunit-1140-4-source-into-unstable/
Buster release was 3
Hi,
Am 31. Oktober 2019 15:15:10 MEZ schrieb Matthias Klose :
>On 29.10.19 15:09, Vincent Lefevre wrote:
>> On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote:
>>> Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre
>:
In case makefile magic triggers some rebuild, you can
Source: glom
Version: 1.30.4-3
Severity: serious
Hi,
postgresql-11 is being replaced by postgresql-12. Please upgrade glom
accordingly.
Thanks,
Christoph
signature.asc
Description: PGP signature
On 29.10.19 15:09, Vincent Lefevre wrote:
On 2019-10-29 13:09:46 +0100, rene.engelh...@mailbox.org wrote:
Am 29. Oktober 2019 12:49:44 MEZ schrieb Vincent Lefevre :
In case makefile magic triggers some rebuild, you can also run the
generated executable directly (with the right environment
Processing commands for cont...@bugs.debian.org:
> # fix bug metadata to allow archival
> notfound 937986 3.40.3-2
Bug #937986 {Done: Sandro Tosi } [src:python-oslo.utils]
python-oslo.utils: Python2 removal in sid/bullseye
No longer marked as found in versions python-oslo.utils/3.40.3-2.
> found
Processing control commands:
> tag -1 pending
Bug #943765 [libvtkgdcm3-dev] libvtkgdcm3-dev: missing Breaks+Replaces:
libvtkgdcm2-dev
Added tag(s) pending.
--
943765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #943765 in gdcm 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 commands for cont...@bugs.debian.org:
> fixed 936307 claws-mail/3.17.4-2
Bug #936307 [src:claws-mail] claws-mail: Python2 removal in sid/bullseye
Marked as fixed in versions claws-mail/3.17.4-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936307:
Your message dated Thu, 31 Oct 2019 11:49:15 +
with message-id
and subject line Bug#943876: fixed in systemtap 4.1-11
has caused the Debian Bug report #943876,
regarding linux breaks systemtap autopkgtest: error: this statement may fall
through [-Werror=implicit-fallthrough=]
to be marked as
Your message dated Thu, 31 Oct 2019 09:37:44 +0100
with message-id <53b5ceb3-4826-d87a-05d4-d846d0e1e...@debian.org>
and subject line Python 2 modules have been removed
has caused the Debian Bug report #943445,
regarding the autopkg test calls python instead of python2
to be marked as done.
This
Your message dated Thu, 31 Oct 2019 09:23:45 +
with message-id
and subject line Bug#943843: fixed in mailutils 1:3.7-2
has caused the Debian Bug report #943843,
regarding mailutils-doc: missing Breaks+Replaces: mailutils (<< 1:3.7)
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #943840 [python3-rrdtool-dbg] python3-rrdtool-dbg: missing Breaks+Replaces:
rrdtool-dbg
Added tag(s) pending.
--
943840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #943840 in rrdtool 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:
Fixed (hopefully) in upstream.
Source code is here: https://github.com/cmauri/eviacam
And also uploaded to mentors here: https://mentors.debian.net/package/eviacam
Fixed opencv4 compatibility for eviacam in upstream.
Source code is here: https://github.com/cmauri/eviacam
And also uploaded to mentors here: https://mentors.debian.net/package/eviacam
Source: libayatana-indicator
Version: 0.6.2-3
Severity: serious
Tags: ftbfs
libayatana-indicator fails to build from source in unstable on amd64.
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libayatana-indicator_0.6.2-3.rbuild.log.gz
|
Processing control commands:
> found -1 linux/5.3.7-1
Bug #943876 [src:linux, src:systemtap] linux breaks systemtap autopkgtest:
error: this statement may fall through [-Werror=implicit-fallthrough=]
Marked as found in versions linux/5.3.7-1.
> found -1 systemtap/4.1-10
Bug #943876 [src:linux,
Source: linux, systemtap
Control: found -1 linux/5.3.7-1
Control: found -1 systemtap/4.1-10
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainers,
With a recent upload of linux the autopkgtest
Your message dated Thu, 31 Oct 2019 07:34:26 +
with message-id
and subject line Bug#943850: fixed in ros-python-qt-binding 0.3.6-3
has caused the Debian Bug report #943850,
regarding python3-python-qt-binding: missing Breaks+Replaces: python-qt-binding
to be marked as done.
This means that
Your message dated Thu, 31 Oct 2019 07:33:55 +
with message-id
and subject line Bug#941984: fixed in backintime 1.2.1-2
has caused the Debian Bug report #941984,
regarding backintime: files under the GFDL
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 31 Oct 2019 07:33:55 +
with message-id
and subject line Bug#941686: fixed in backintime 1.2.1-2
has caused the Debian Bug report #941686,
regarding backintime-qt: Version 1.2.1-1 has wrong dependency on qt4
python3-dbus.mainloop
to be marked as done.
This means that
Your message dated Thu, 31 Oct 2019 07:33:55 +
with message-id
and subject line Bug#942155: fixed in backintime 1.2.1-2
has caused the Debian Bug report #942155,
regarding backintime: Incomplete debian/copyright, etc.
to be marked as done.
This means that you claim that the problem has been
70 matches
Mail list logo
