Bug#1070259: tuiwidgets: Should experimental t64 version be uploaded to unstable?
On Thu, May 02, 2024 at 11:25:12PM +0200, Bastian Germann wrote: > Source: tuiwidgets > Version: 0.2.1-1.1~exp1 > Severity: important > X-Debbugs-Cc: vor...@debian.org > > tuiwidget was targeted to be part of the t64 transition but has not been > uploaded to unstable after renaming the experimental library. Should this be > done? > tuiwidget was targeted in error (because some glitch while analysing made it fail to analyse). See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063006#12 (also that message seems to have a copy and paste error for the package name). (if needed i can dig out more details from irc on the analysis) I think the proper course of action will be drop the experimental version (and the auto transition tracker it created). But i was going to wait until things have calmed down a bit, because this cleanup seems to be non urgent. - Martin
Bug#1070024: Rebuild for cmake 3.29 compatibility fix
Package: ksyntax-highlighting
X-Debbugs-CC: c...@istoph.de
Severity: important
(this is a follow-up to #1069972)
Please rebuild libkf5syntaxhighlighting-dev using
extra-cmake-modules 6.1.0-1 or newer.
As far as i understand this needs a sourceful upload as
libkf5syntaxhighlighting-dev is a arch any binary package.
(not sure if it needs a versioned build depends to pick up the
new version of extra-cmake-modules)
Since cmake 3.29 entered sid, the files created by ECMAddQch.cmake from
extra-cmake-modules < 6.1.0-1 (as the libkf5syntaxhighlighting-dev
currently in sid) cause warnings or errors (with CMP0160 set to NEW).
Furthermore when libkf5syntaxhighlighting-dev is consumed in packages
build using meson, the build fails as the meson cmake compat code
always sets cmake_minimum_required to the current cmake version and
thus CMP0160 is alway set to NEW which makes the code generated
before the fix an hard error.
For example the package chr now no longer builds in sid because of
this.
-- Configuring incomplete, errors occurred!
ERR:
CMake Error at
/usr/lib/x86_64-linux-gnu/cmake/KF5SyntaxHighlighting/KF5SyntaxHighlightingQchTargets.cmake:6
(set_target_properties):
IMPORTED property is read-only for target("KF5SyntaxHighlighting_QCH")
Call Stack (most recent call first):
/usr/lib/x86_64-linux-gnu/cmake/KF5SyntaxHighlighting/KF5SyntaxHighlightingConfig.cmake:42
(include)
CMakeLists.txt:20 (find_package)
(for a full log see https://salsa.debian.org/chr/chr/-/jobs/5651154 )
Regards,
- Martin
Bug#1069972: Backport cmake 3.29 compatibility fix
Package: extra-cmake-modules
Tags: patch, fixed-upstream
Severity: important
X-Debbugs-CC: c...@istoph.de
Please backport
https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/431
Since cmake 3.29 entered sid, the files created by ECMAddQch.cmake and
shipped in -dev packages cause warnings or errors (with CMP0160 set
to NEW).
Furthermore when libraries that use ECMAddQch are consumed in packages
build using meson, the builds fails as the meson cmake compat code
always sets cmake_minimum_required to the current cmake version and
thus CMP0160 is alway set to NEW which makes the code generated
before the fix an hard error.
For example the package chr now no longer builds in sid because of
this (in combination with ksyntax-highlighting).
-- Configuring incomplete, errors occurred!
ERR:
CMake Error at
/usr/lib/x86_64-linux-gnu/cmake/KF5SyntaxHighlighting/KF5SyntaxHighlightingQchTargets.cmake:6
(set_target_properties):
IMPORTED property is read-only for target("KF5SyntaxHighlighting_QCH")
Call Stack (most recent call first):
/usr/lib/x86_64-linux-gnu/cmake/KF5SyntaxHighlighting/KF5SyntaxHighlightingConfig.cmake:42
(include)
CMakeLists.txt:20 (find_package)
(for a full log see https://salsa.debian.org/chr/chr/-/jobs/5651154 )
Regards,
- Martin
Bug#1069055: chr: Hardcode build-depends on library pkg libqt5concurrent5, blocks time_64 transition
Control: tag -1 patch Control: block -1 by 1069198 On Mon, Apr 15, 2024 at 12:47:39PM -0400, Boyuan Yang wrote: > Your package builds-depends on library package libqt5concurrent5, > which does not exist in Debian Sid after Debian 64-bit time_t transition > since the library package was renamed. > Thanks for the report. This is fixed in a pending upload that is now waiting for a sponsor. https://mentors.debian.net/package/chr/ (RFS: #1069198) chr (0.1.78-1) unstable; urgency=medium . * New upstream version 0.1.78 * remove: Hardcode build-depends on library pkg libqt5concurrent5, blocks time_64 transition (Closes: #1069055) Regards, - Martin
Bug#1002393: mdp: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
Bump to avoid auto removal while the fixed version ages in unstable. I'm not sure if this needs some additional prodding because tracker only shows one of the bugs as fixed by migration and 2 bugs triggering auto removal.
Bug#995156: easy-rsa: vars Autodetection
Bump to avoid auto removal while the fixed version ages in unstable.
Bug#475748: [Psi-Devel] Bug#475748: psi: Segfault when clicking on Preferences - Appearance
On Sun, Apr 13, 2008 at 05:34:21PM +0200, Jan Niehusmann wrote: On Sat, Apr 12, 2008 at 07:13:41PM +0200, Marek Elias wrote: In prefernces window, when clicking on appearance, PSI segfaults: kernel: [53510.815342] psi[28666]: segfault at eip 083803a8 esp bfab5880 error 4 (from syslog) You can find dumped core here: http://mebs.matfyz.cz/neporiadok/core.psi I tracked this down to OptionsTabWidget::addTab(OptionsTab *tab), where QTabWidget::addTab() is called before initializing wtab[]. It seems like qt4.4 is triggering the currentChanged signal immediately on calling addTab(). As wtab[] has not been initialized at this point, the following code in updateCurrent() segfaults: OptionsTab *opttab = w2tab[w].tab; QWidget *tab = opttab-widget(); The fix is easy: Change OptionsTabWidget::addTab to call QTabWidget::addTab after initializing w2tab. (Patch below) Thanks for the problem analysis and the patch. Fix is applied. - Martin H. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
