[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#905559: marked as done (new qt stack appears to break ktexteditor autopkgtest: 65 - vimode_keys (Failed))

Your message dated Thu, 17 Mar 2022 19:47:19 +0100
with message-id <765ce3d4-77cc-ba36-2704-f8201c67cce1@debian.org>
and subject line Re: new qt stack appears to break ktexteditor autopkgtest: 65 - vimode_keys (Failed)
has caused the Debian Bug report #905559,
regarding new qt stack appears to break ktexteditor autopkgtest: 65 - vimode_keys (Failed)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
905559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905559
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: ktexteditor
Version: 5.47.0-1
User: debian-ci@lists.debian.org
Usertags: needs-update

Dear maintainers,

After the recent qt transitions and the fixing of all the fall-out by
uploading a new version of abi-compliance-checker, the autopkgtest of
ktexteditor remains failing in unstable and testing (with either
qtdeclarative-opensource-src/5.11.1-4 or
qtbase-opensource-src/5.11.1+dfsg-6). I copied the output below. I'm
filing this bug because this seems to be a real regression, were
ktexteditor and/or its autopkgtest needs fixing.

I believe this regression is the last item delaying the migration of the
qt stack to testing. Could you please investigate the situation and if
needed reassign the bug to the right package?

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/k/ktexteditor/776729/log.gz

>>> running command  "\\:map foo l\\foorX"  on text  "xxx"
QDEBUG : KeysTest::MappingTests() Executing command directly from
ViModeTest:
 "map foo l"
foo
function() { [code] }
QDEBUG : KeysTest::MappingTests() Actual text:
	 "xxx\norX"
Should be (for this test to pass):
	 "abXxxx"
XFAIL  : KeysTest::MappingTests() 'map' is reserved for other stuff in
Kate command line
   Loc:
[/tmp/autopkgtest-lxc.m0shrvs8/downtmp/build.uNe/src/autotests/src/vimode/keys.cpp(439)]
QDEBUG : KeysTest::MappingTests()

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Version: 5.54.0-1

On Mon, 6 Aug 2018 09:49:45 +0200 Paul Gevers <elbrus@debian.org> wrote:

After the recent qt transitions and the fixing of all the fall-out by
uploading a new version of abi-compliance-checker, the autopkgtest of
ktexteditor remains failing in unstable and testing (with either
qtdeclarative-opensource-src/5.11.1-4 or
qtbase-opensource-src/5.11.1+dfsg-6). I copied the output below. I'm
filing this bug because this seems to be a real regression, were
ktexteditor and/or its autopkgtest needs fixing.

I believe this regression is the last item delaying the migration of the
qt stack to testing. Could you please investigate the situation and if
needed reassign the bug to the right package?
The ktexteditor autopkgtest has been (mostly) passing since the beginning of 2019. Let's close this bug. 

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: