Bug#1003207: pngphoon: new version available: 1.3
Package: pngphoon Version: 1.3-0svolli1 Severity: wishlist Dear Maintainer, as the developer of pngphoon, I'd like to inform you that a new version is available. I've created also a "debian-tarball" for building with different versions of Debian and Ubuntu. While it will most probably not satisfy the quality requirements of Debian, it contains an updated manual page in sgml format. Everything is available at https://svolli.de/software/pngphoon/ Greetings, SvOlli
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 997611 xutils-dev
Bug #997611 [src:wnn6-sdk] wnn6-sdk: FTBFS: ar: libdeps specified more than once
Bug reassigned from package 'src:wnn6-sdk' to 'xutils-dev'.
No longer marked as found in versions wnn6-sdk/1.0.0-18.
Ignoring request to alter fixed versions of bug #997611 to the same values
previously set
> reassign 997621 xutils-dev
Bug #997621 [src:fvwm1] fvwm1: FTBFS: ar: libdeps specified more than once
Bug reassigned from package 'src:fvwm1' to 'xutils-dev'.
No longer marked as found in versions fvwm1/1.24r-57.
Ignoring request to alter fixed versions of bug #997621 to the same values
previously set
> reassign 997622 xutils-dev
Bug #997622 [src:kinput2] kinput2: FTBFS: ar: libdeps specified more than once
Bug reassigned from package 'src:kinput2' to 'xutils-dev'.
No longer marked as found in versions kinput2/3.1-13.
Ignoring request to alter fixed versions of bug #997622 to the same values
previously set
> reassign 997643 xutils-dev
Bug #997643 [src:ctwm] ctwm: FTBFS: ar: libdeps specified more than once
Bug reassigned from package 'src:ctwm' to 'xutils-dev'.
No longer marked as found in versions ctwm/3.7-5.
Ignoring request to alter fixed versions of bug #997643 to the same values
previously set
> forcemerge 997615 997611 997621 997622 997643
Bug #997615 {Done: Timo Aaltonen } [xutils-dev] troffcvt:
FTBFS: ar: libdeps specified more than once
Bug #994276 {Done: Timo Aaltonen } [xutils-dev]
xutils-dev: imake shouldn't pass l to ar
Bug #997628 {Done: Samuel Thibault } [xutils-dev] imake:
uses “ar clq” by default, which recent binutils broke in an incompatible way
Bug #997636 {Done: Timo Aaltonen } [xutils-dev] koules:
FTBFS: ar: libdeps specified more than once
Bug #997638 {Done: Samuel Thibault } [xutils-dev] nas:
FTBFS: ar: libdeps specified more than once
Bug #997641 {Done: Timo Aaltonen } [xutils-dev] knews:
FTBFS: ar: libdeps specified more than once
Bug #997650 {Done: Timo Aaltonen } [xutils-dev] xtel:
FTBFS: ar: libdeps specified more than once
Bug #997622 [xutils-dev] kinput2: FTBFS: ar: libdeps specified more than once
Marked Bug as done
Added indication that 997622 affects koules,knews,troffcvt,xtel
Marked as fixed in versions xutils-dev/1:7.7+6.
Marked as found in versions xutils-dev/1:7.7+5.
Added tag(s) patch.
Bug #997643 [xutils-dev] ctwm: FTBFS: ar: libdeps specified more than once
Marked Bug as done
Added indication that 997643 affects koules,knews,troffcvt,xtel
Marked as fixed in versions xutils-dev/1:7.7+6.
Marked as found in versions xutils-dev/1:7.7+5.
Added tag(s) patch.
Bug #997611 [xutils-dev] wnn6-sdk: FTBFS: ar: libdeps specified more than once
Marked Bug as done
Added indication that 997611 affects koules,knews,troffcvt,xtel
Marked as fixed in versions xutils-dev/1:7.7+6.
Marked as found in versions xutils-dev/1:7.7+5.
Added tag(s) patch.
Bug #997621 [xutils-dev] fvwm1: FTBFS: ar: libdeps specified more than once
Marked Bug as done
Added indication that 997621 affects koules,knews,troffcvt,xtel
Marked as fixed in versions xutils-dev/1:7.7+6.
Marked as found in versions xutils-dev/1:7.7+5.
Added tag(s) patch.
Bug #994276 {Done: Timo Aaltonen } [xutils-dev]
xutils-dev: imake shouldn't pass l to ar
Bug #997628 {Done: Samuel Thibault } [xutils-dev] imake:
uses “ar clq” by default, which recent binutils broke in an incompatible way
Bug #997636 {Done: Timo Aaltonen } [xutils-dev] koules:
FTBFS: ar: libdeps specified more than once
Bug #997638 {Done: Samuel Thibault } [xutils-dev] nas:
FTBFS: ar: libdeps specified more than once
Bug #997641 {Done: Timo Aaltonen } [xutils-dev] knews:
FTBFS: ar: libdeps specified more than once
Bug #997650 {Done: Timo Aaltonen } [xutils-dev] xtel:
FTBFS: ar: libdeps specified more than once
Merged 994276 997611 997615 997621 997622 997628 997636 997638 997641 997643
997650
> affects 997615 src:wnn6-sdk src:fvwm1 src:kinput2 src:ctwm
Bug #997615 {Done: Timo Aaltonen } [xutils-dev] troffcvt:
FTBFS: ar: libdeps specified more than once
Bug #994276 {Done: Timo Aaltonen } [xutils-dev]
xutils-dev: imake shouldn't pass l to ar
Bug #997611 {Done: Timo Aaltonen } [xutils-dev] wnn6-sdk:
FTBFS: ar: libdeps specified more than once
Bug #997621 {Done: Timo Aaltonen } [xutils-dev] fvwm1:
FTBFS: ar: libdeps specified more than once
Bug #997622 {Done: Timo Aaltonen } [xutils-dev] kinput2:
FTBFS: ar: libdeps specified more than once
Bug #997628 {Done: Samuel Thibault } [xutils-dev] imake:
uses “ar clq” by default, which recent binutils broke in an incompatible way
Bug #997636 {Done: Timo Aaltonen } [xutils-dev] koules:
FTBFS: ar: libdeps specified more than once
Bug #997638 {Done: Samuel Thibault } [xutils-dev] nas:
FTBFS: ar: libdeps specified more than once
Bug #997641 {Done: Timo Aaltonen } [xutils-dev] knews:
FTBFS: ar: libdeps specified more than once
Bug #997643 {Done: Timo Aaltonen } [xutils-dev] ctwm:
FTBFS: ar: libdeps specified more than once
Bug #997650 {Done: Timo Aalton
Bug#984002: marked as done (boxbackup: ftbfs with GCC-11)
Your message dated Thu, 06 Jan 2022 22:18:35 + with message-id and subject line Bug#984002: fixed in boxbackup 0.13~~git20200326.g8e8b63c-2 has caused the Debian Bug report #984002, regarding boxbackup: ftbfs with GCC-11 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.) -- 984002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:boxbackup Version: 0.13~~git20200326.g8e8b63c-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/boxbackup_0.13~~git20200326.g8e8b63c-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] lib/win32 lib/common lib/raidfile lib/crypto lib/server lib/compress lib/intercept test/common test/crypto test/compress test/raidfile test/basicserver lib/backupstore lib/backupclient lib/bbackupd lib/bbackupquery lib/bbstored bin/bbackupobjdump bin/bbstored bin/bbstoreaccounts bin/bbackupd bin/bbackupquery bin/bbackupctl test/backupstore test/backupstorefix test/backupstorepatch test/backupdiff test/bbackupd bin/s3simulator test/s3store lib/httpserver test/httpserver Type 'cd ; make' to build a module A summary of the build configuration is below. Box Backup will function without these features, but will work better where they are present. Refer to the documentation for more information on each feature. Regular expressions: yes Large files: yes Berkeley DB: yes Readline:yes Extended attributes: yes Debugger:neither GDB nor LLDB detected! touch configure-stamp dh_testdir /usr/bin/make V=1 make[1]: Entering directory '/<>' g++ -g -Wall -Werror=return-type -Werror=delete-non-virtual-dtor -Werror=delete-incomplete -Wno-deprecated-declarations -DBOX_VERSION="\"0.13~~git20200326.g8e8b63c-1\"" -DBOX_RELEASE_BUILD -O2 -Ilib/bbackupd -Ilib/backupclient -Ilib/backupstore -Ilib/raidfile -Ilib/compress -Ilib/httpserver -Ilib/server -Iqdbm -Ilib/crypto -Ilib/common -Ilib/win32 -DBOX_MODULE="\"bin/bbackupd\"" -c bin/bbackupd/bbackupd.cpp -o release/bin/bbackupd/bbackupd.o g++ -g -Wall -Werror=return-type -Werror=delete-non-virtual-dtor -Werror=delete-incomplete -Wno-deprecated-declarations -DBOX_VERSION="\"0.13~~git20200326.g8e8b63c-1\"" -DBOX_RELEASE_BUILD -O2 -Ilib/backupclient -Ilib/backupstore -Ilib/raidfile -Ilib/compress -Ilib/httpserver -Ilib/server -Iqdbm -Ilib/crypto -Ilib/common -Ilib/win32 -DBOX_MODULE="\"lib/bbackupd\"" -c lib/bbackupd/BackupClientContext.cpp -o release/lib/bbackupd/BackupClientContext.o g++ -g -Wall -Werror=return-type -Werror=delete-non-virtual-dtor -Werror=delete-incomplete -Wno-deprecated-declarations -DBOX_VERSION="\"0.13~~git20200326.g8e8b63c-1\"" -DBOX_RELEASE_BUILD -O2 -Ilib/backupclient -Ilib/backupstore -Ilib/raidfile -Ilib/compress -Ilib/httpserver -Ilib/server -Iqdbm -Ilib/crypto -Ilib/common -Ilib/win32 -DBOX_MODULE="\"lib/bbackupd\"" -c lib/bbackupd/BackupClientDeleteList.cpp -o release/lib/bbackupd/BackupClientDeleteList.o g++ -g -Wall -Werror=return-type -Werror=delete-non-virtual-dtor -Werror=delete-incomplete -Wno-deprecated-declarations -DBOX_VERSION="\"0.13~~git20200326.g8e8b63c-1\""
Bug#1002202: marked as done (pyocd: FTBFS: AttributeError: 'NoneType' object has no attribute 'split')
Your message dated Fri, 07 Jan 2022 06:16:57 +0100 with message-id and subject line Re: pyocd: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' has caused the Debian Bug report #1002202, regarding pyocd: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' 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.) -- 1002202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002202 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyocd Version: 0.13.1+dfsg-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > python3 setup.py install --root=/<>/debian/python3-pyocd/ > --install-layout=deb > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > running egg_info > writing pyocd.egg-info/PKG-INFO > writing dependency_links to pyocd.egg-info/dependency_links.txt > writing entry points to pyocd.egg-info/entry_points.txt > writing requirements to pyocd.egg-info/requires.txt > writing top-level names to pyocd.egg-info/top_level.txt > reading manifest file 'pyocd.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching '*' under directory 'binaries' > warning: no files found matching '*' under directory 'elf_files' > warning: no previously-included files matching '.DS_Store' found anywhere in > distribution > adding license file 'LICENSE' > writing manifest file 'pyocd.egg-info/SOURCES.txt' > running install_lib > creating /<>/debian/python3-pyocd > creating /<>/debian/python3-pyocd/usr > creating /<>/debian/python3-pyocd/usr/lib > creating /<>/debian/python3-pyocd/usr/lib/python3 > creating /<>/debian/python3-pyocd/usr/lib/python3/dist-packages > creating > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd > copying build/lib/pyocd/__init__.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd > creating > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/tools > copying build/lib/pyocd/tools/__init__.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/tools > copying build/lib/pyocd/tools/gdb_server.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/tools > copying build/lib/pyocd/tools/pyocd.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/tools > copying build/lib/pyocd/tools/flash_tool.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/tools > creating > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/__init__.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/test_regcache.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/test_conversion.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/test_memory_map.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/test_memcache.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/test_mockcore.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/test_cmdline.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/test_timeout.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/test_sequencer.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/conftest.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/mockcore.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > copying build/lib/pyocd/test/test_semihosting.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/test > creating > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/board > copying build/lib/pyocd/board/__init__.py -> > /<>/debian/python3-pyocd/usr/lib/python3/dist-packages/pyocd/board > copying build/lib/pyocd/board/mbed_board.py -> > /<>/debian/p
