Your message dated Mon, 24 Jul 2023 18:34:37 +0000
with message-id <e1qo0od-00csaf...@fasolo.debian.org>
and subject line Bug#1037624: fixed in dpuser 4.1+dfsg-2
has caused the Debian Bug report #1037624,
regarding dpuser: ftbfs with GCC-13
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 ow...@bugs.debian.org
immediately.)


-- 
1037624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dpuser
Version: 4.1+dfsg-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/dpuser_4.1+dfsg-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
../dpuser/dpuserAST.h:272:13: warning: ‘statementNode::id’ will be initialized 
after [-Wreorder]
  272 |         int id;
      |             ^~
../dpuser/dpuserAST.h:271:18: warning:   ‘ASTNode* statementNode::stmt’ 
[-Wreorder]
  271 |         ASTNode *stmt = NULL;
      |                  ^~~~
../dpuser/dpuserAST.h:273:9: warning:   when initialized here [-Wreorder]
  273 |         statementNode(ASTNode *s) : id(0), stmt(s) { }
      |         ^~~~~~~~~~~~~
../dpuser/dpuserAST.h: In destructor ‘virtual listNode::~listNode()’:
../dpuser/dpuserAST.h:284:49: warning: comparison of integer expressions of 
different signedness: ‘int’ and ‘std::vector<ASTNode*>::size_type’ {aka ‘long 
unsigned int’} [-Wsign-compare]
  284 |         virtual ~listNode() { for (int i = 0; i < list.size(); i++) 
delete list.at(i); }
      |                                               ~~^~~~~~~~~~~~~
../dpuser/dpuserAST.h: In destructor ‘virtual rangeNode::~rangeNode()’:
../dpuser/dpuserAST.h:295:46: warning: comparison of integer expressions of 
different signedness: ‘int’ and ‘std::vector<ASTNode*>::size_type’ {aka ‘long 
unsigned int’} [-Wsign-compare]
  295 |     virtual ~rangeNode() { for (int i = 0; i < list.size(); i++) delete 
list.at(i); }
      |                                            ~~^~~~~~~~~~~~~
../dpuser/dpuserAST.h: In constructor 
‘extractrangeNode::extractrangeNode(ASTNode*, ASTNode*)’:
../dpuser/dpuserAST.h:310:14: warning: ‘extractrangeNode::argument’ will be 
initialized after [-Wreorder]
  310 |     ASTNode *argument;
      |              ^~~~~~~~
../dpuser/dpuserAST.h:309:14: warning:   ‘ASTNode* extractrangeNode::range’ 
[-Wreorder]
  309 |     ASTNode *range;
      |              ^~~~~
../dpuser/dpuserAST.h:311:5: warning:   when initialized here [-Wreorder]
  311 |     extractrangeNode(ASTNode *arg, ASTNode *newrange) : argument(arg), 
range(newrange) { }
      |     ^~~~~~~~~~~~~~~~
../dpuser/dpuserAST.h: In constructor ‘forloopNode::forloopNode(ASTNode*, 
ASTNode*, ASTNode*, ASTNode*)’:
../dpuser/dpuserAST.h:374:52: warning: ‘forloopNode::change’ will be 
initialized after [-Wreorder]
  374 |         ASTNode *start, *check = NULL, *commands, *change = NULL, 
*limit = NULL;
      |                                                    ^~~~~~
../dpuser/dpuserAST.h:374:41: warning:   ‘ASTNode* forloopNode::commands’ 
[-Wreorder]
  374 |         ASTNode *start, *check = NULL, *commands, *change = NULL, 
*limit = NULL;
      |                                         ^~~~~~~~
../dpuser/dpuserAST.h:375:9: warning:   when initialized here [-Wreorder]
  375 |         forloopNode(ASTNode *s, ASTNode *c, ASTNode *e, ASTNode *co) : 
start(s), check(c), change(e), commands(co) { }
      |         ^~~~~~~~~~~
../dpuser/dpuserAST.h: In constructor ‘forloopNode::forloopNode(ASTNode*, 
ASTNode*, ASTNode*)’:
../dpuser/dpuserAST.h:374:68: warning: ‘forloopNode::limit’ will be initialized 
after [-Wreorder]
  374 |         ASTNode *start, *check = NULL, *commands, *change = NULL, 
*limit = NULL;
      |                                                                    ^~~~~
../dpuser/dpuserAST.h:374:41: warning:   ‘ASTNode* forloopNode::commands’ 
[-Wreorder]
  374 |         ASTNode *start, *check = NULL, *commands, *change = NULL, 
*limit = NULL;
      |                                         ^~~~~~~~
../dpuser/dpuserAST.h:376:9: warning:   when initialized here [-Wreorder]
  376 |         forloopNode(ASTNode *s, ASTNode *c, ASTNode *co) : start(s), 
limit(c), commands(co) { }
      |         ^~~~~~~~~~~
../dpuser/dpuserAST.h: In member function ‘virtual dpuserType 
userprocedureNode::evaluate()’:
../dpuser/dpuserAST.h:403:51: warning: no return statement in function 
returning non-void [-Wreturn-type]
  403 |         dpuserType evaluate() { body->evaluate(); }
      |                                                   ^
../libfits/fits.h: In constructor ‘FitsIndexRef::FitsIndexRef(const Fits*, 
const INDEX&)’:
../libfits/fits.h:172:93: warning: implicitly-declared ‘INDEX& 
INDEX::operator=(const INDEX&)’ is deprecated [-Wdeprecated-copy]
  172 |         FitsIndexRef(const Fits *source, const INDEX &I) { parent = 
(Fits *)source; index = I; }
      |                                                                         
                    ^
../libfits/fits.h:131:9: note: because ‘INDEX’ has user-provided 
‘INDEX::INDEX(const INDEX&)’
  131 |         INDEX(const INDEX &I) { X = I.x(); Y = I.y(); Z = I.z(); N = 
I.n(); }
      |         ^~~~~
g++ -Wl,-z,relro -Wl,-z,relro -o QFitsView main.o QFitsMainWindow.o 
QFitsMainView.o QFitsBaseBuffer.o QFitsSingleBuffer.o QFitsMultiBuffer.o 
QFitsScroller.o QFitsBaseWidget.o QFitsWidget1D.o QFitsWidget2D.o 
QFitsWidgetWiregrid.o QFitsWidgetContour.o QFitsWidgetTable.o QFitsBaseView.o 
QFitsView1D.o QFitsView2D.o QFitsGlobal.o QFitsMarkers.o QFitsTools.o 
QFitsWedge.o lut.o QFitsCubeSpectrum.o RGBDialog.o QFitsHeaderView.o 
QFitsToolBar.o dialogs.o events.o imred.o galfit.o guitools.o 
QFitsViewingTools.o qtdpuser.o qt_mainwindow.o qt_mdichild.o highlighter.o 
QFitsPreferences.o tetrixboard.o tetrixpiece.o tetrixwindow.o qcustomplot.o 
QPgplot.o QFitsWidget3D.o QFitsView3D.o dpuser.yacchelper.o functions.o y.tab.o 
dpuser.input.o procedures.o lex.yy.o svn_revision.o dpuser_utils.o 
dpuser.procs.o y.mpfit.o lex.mpfit.o mpfitAST.o dpuserType.o dpuserAST.o 
gdl_dpuser.o python_dpuser.o arithmetics.o boolean.o helpmap.o dpstring.o 
dpstringlist.o regex_sr.o mpfit.o kabsch2d.o 3d_stuff.o cube.o dphe
 ader.o fits.o fits_cube.o fits_dpl.o fits_exc.o fits_file.o fits_filters.o 
fits_funcs.o fits_mem.o fits_ops.o fits_procs.o fits_range.o fits_red.o 
JulianDay.o math_utils.o dpComplex.o fitting.o voronoi.o fits_logic.o 
astrolib.o qrc_QFitsViewDoc.o qrc_QFitsViewRes.o moc_QFitsMainWindow.o 
moc_QFitsMainView.o moc_QFitsBaseBuffer.o moc_QFitsSingleBuffer.o 
moc_QFitsMultiBuffer.o moc_QFitsScroller.o moc_QFitsBaseWidget.o 
moc_QFitsWidget1D.o moc_QFitsWidget2D.o moc_QFitsWidgetWiregrid.o 
moc_QFitsWidgetContour.o moc_QFitsWidgetTable.o moc_QFitsBaseView.o 
moc_QFitsView1D.o moc_QFitsView2D.o moc_QFitsTools.o moc_QFitsWedge.o 
moc_QFitsCubeSpectrum.o moc_RGBDialog.o moc_QFitsHeaderView.o 
moc_QFitsToolBar.o moc_dialogs.o moc_imred.o moc_galfit.o moc_guitools.o 
moc_QFitsViewingTools.o moc_qtdpuser.o moc_qt_mainwindow.o moc_qt_mdichild.o 
moc_highlighter.o moc_QFitsPreferences.o moc_tetrixboard.o moc_tetrixwindow.o 
moc_qcustomplot.o moc_QPgplot.o moc_QFitsWidget3D.o moc_QFitsView3D.o   
-lcpgplot -r
 dynamic -ldl -lgsl -lgslcblas -lfftw3 -lxpa -lz -lpthread 
/usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so 
/usr/lib/x86_64-linux-gnu/libQt5Svg.so 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so 
/usr/lib/x86_64-linux-gnu/libQt5DataVisualization.so 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so 
/usr/lib/x86_64-linux-gnu/libQt5Network.so 
/usr/lib/x86_64-linux-gnu/libQt5Core.so -lGL   
make[2]: Leaving directory '/<<PKGBUILDDIR>>/QFitsView'
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
cd dpuser/test && echo @testsuite.dpuser | ../dpuser | tee ../../test.log
Illegal instruction
fgrep -q CONGRATULATIONS test.log
make[1]: *** [debian/rules:19: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:9: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: dpuser
Source-Version: 4.1+dfsg-2
Done: Ole Streicher <oleb...@debian.org>

We believe that the bug you reported is fixed in the latest version of
dpuser, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1037...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher <oleb...@debian.org> (supplier of updated dpuser package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 24 Jul 2023 16:45:28 +0200
Source: dpuser
Architecture: source
Version: 4.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team <debian-astro-maintain...@lists.alioth.debian.org>
Changed-By: Ole Streicher <oleb...@debian.org>
Closes: 1037624
Changes:
 dpuser (4.1+dfsg-2) unstable; urgency=medium
 .
   * Always return something in dpuserAST. Closes: #1037624
Checksums-Sha1:
 615eecfa717bcb8007e14c0148f91f7dbeaa71df 2283 dpuser_4.1+dfsg-2.dsc
 33bfdc247a34b661d6320bcfd83af8099bcf0c0d 13360 dpuser_4.1+dfsg-2.debian.tar.xz
Checksums-Sha256:
 8be76c74d64bf5518c387f80845ce0c1798cae776e276ec7de90937ccb4b7c77 2283 
dpuser_4.1+dfsg-2.dsc
 3183f95be5ee22ed1455ad0e1e70ef0b28490fd151ee212f04f2f7613b4d7b9f 13360 
dpuser_4.1+dfsg-2.debian.tar.xz
Files:
 f4803f94c4c3bab0bd487715c609c54e 2283 science optional dpuser_4.1+dfsg-2.dsc
 146c37677583721a6e1c96704cd2b4f4 13360 science optional 
dpuser_4.1+dfsg-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAmS+vsQACgkQmk9WvbkO
GL3+xQ//QMkwoYUpp5LnBNX0EFOj9jx9zCM/kZjNj4WYwtrceNiFx/n7PZcVqMRF
FxqwCNrVLgIN2RDJ04g2nTmSrfOys14R6+jRz3VFb6UkKuodANc2x0D4Y2ycfrI9
u8DX+NY4APDqvAoORKmXcSMm7ITpIsfORgzN4fqXv8Bt+QXrL8brqxEIYkY5c590
Em5zagI0L+0upOpwK4qdFLJjh6P/QjMQHotKcqp9lN3aD7plyY/8ty7+g0Hf1Gpf
4ibytfir6FCQ5N8teE5b4ACvS63KQvJ/MJfDO4KiZXTWKBBfO3nfRILfPZxlz55O
YdMgqEQh/TdQBrCKIWFqL+RvDicNkNw8fVFEzuxAhg6LuPUV5Nfh8nRNr4TW01/s
fg6YoMIPVJ7HnafenVfazCd7Ro0HAYa312o6snxRN0IjDBscR/SUOI1mRwGPOLJY
WGKquP/VFOekun2i3t3ofm3NBO14tkDUWuP+ACyrfMkafDlNNIejFuFvENIQZS7n
wiavTLAZRcSj1YPeMW0rJ7eIFV2UnrOWpv1o5f6zdk/g48SZFSVZ9UVXsE2dIjAj
8LHrfdzWcGTJ+lvgsLsNdFmoFvOmq8O8Xmh0OBE8bW+CwlzgA/MdvShH7kdZ/sr4
M42/nw1igIR7cNUvPa3OILIgwC79M8xXp0rCUWoMqpdKE/FJAAY=
=lgU2
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to