Re: Bug#939506: unanimity ftbfs in unstable
Control: tags -1 help Hi, On Thu, Sep 05, 2019 at 06:39:33PM +0200, Matthias Klose wrote: > cd /build/1st/unanimity-3.3.0+dfsg/build/src && /usr/bin/cmake -E > cmake_link_script CMakeFiles/gcpp.dir/link.txt --verbose=1 > /build/1st/unanimity-3.3.0+dfsg/src/main/ccs.cpp: In function ‘int > Runner(const PacBio::CLI::Results&)’: > /build/1st/unanimity-3.3.0+dfsg/src/main/ccs.cpp:570:38: error: ‘move’ was > not declared in this scope > 570 | read.Sequence(), move(ipd), move(pw), > read.LocalContextFlags(), > | ^~~~ I have pushed the latest upstream version to Git[1]. The whole error message is now: ... cd /build/unanimity-3.4.1+git20180307.02aa264+dfsg/build/src && /usr/bin/c++ -I/build/unanimity-3.4.1+git20180307.02aa264+dfsg/include -I/build/unanimity-3.4.1+git20180307.02aa264+dfsg/build/generated -I/build/unanimity-3.4.1+git20180307.02aa264+dfsg/src -g -O2 -fdebug-prefix-map=/build/unanimity-3.4.1+git20180307.02aa264+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time - D_FORTIFY_SOURCE=2 -Wall -Wextra -Wno-unused-parameter -Wno-unused-variable -Wno-unused-local-typedefs -fPIC -std=c++14 -o CMakeFiles/ccs.dir/main/ccs.cpp.o -c /build/unanimity-3.4.1+git20180307.02aa264+dfsg/ src/main/ccs.cpp /build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:63:12: error: ‘std::setprecision’ has not been declared 63 | using std::setprecision; |^~~~ /build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp: In function ‘void WriteResultsReport(std::ostream&, const Results&)’: /build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:273:24: error: ‘setprecision’ was not declared in this scope 273 | report << fixed << setprecision(2); |^~~~ /build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp: In function ‘int Runner(const PacBio::CLI::Results&)’: /build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:570:38: error: ‘move’ was not declared in this scope 570 | read.Sequence(), move(ipd), move(pw), read.LocalContextFlags(), | ^~~~ /build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:570:38: note: suggested alternatives: In file included from /usr/include/c++/9/deque:67, from /usr/include/boost/detail/container_fwd.hpp:91, from /usr/include/boost/container_hash/extensions.hpp:22, from /usr/include/boost/container_hash/hash.hpp:760, from /usr/include/boost/type_index/stl_type_index.hpp:43, from /usr/include/boost/type_index.hpp:29, from /usr/include/boost/function/function_base.hpp:21, from /usr/include/boost/function/detail/prologue.hpp:17, from /usr/include/boost/function.hpp:30, from /usr/include/boost/algorithm/string/detail/find_iterator.hpp:18, from /usr/include/boost/algorithm/string/find_iterator.hpp:24, from /usr/include/boost/algorithm/string/iter_find.hpp:27, from /usr/include/boost/algorithm/string/split.hpp:16, from /usr/include/boost/algorithm/string.hpp:23, from /build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:14: /usr/include/c++/9/bits/stl_deque.h:443:5: note: ‘std::move’ 443 | move(_Deque_iterator<_Tp, _Tp&, _Tp*> __first, | ^~~~ In file included from /usr/include/boost/move/algorithm.hpp:29, from /usr/include/boost/move/move.hpp:32, from /usr/include/boost/variant/detail/move.hpp:28, from /usr/include/boost/variant/detail/initializer.hpp:23, from /usr/include/boost/variant/variant.hpp:30, from /usr/include/boost/variant.hpp:17, from /usr/include/pbbam/Tag.h:10, from /usr/include/pbbam/TagCollection.h:13, from /usr/include/pbbam/BamRecordImpl.h:21, from /usr/include/pbbam/BamRecord.h:19, from /usr/include/pbbam/BamWriter.h:15, from /build/unanimity-3.4.1+git20180307.02aa264+dfsg/src/main/ccs.cpp:22: /usr/include/boost/move/algo/move.hpp:53:6: note: ‘boost::move’ 53 |O move(I f, I l, O result) | ^~~~ In file included from /usr/include/boost/function/function_template.hpp:32, from /usr/include/boost/function/detail/maybe_include.hpp:15, from /usr/include/boost/function/detail/function_iterate.hpp:14, from /usr/include/boost/preprocessor/iteration/detail/iter/forward1.hpp:48, from /usr/include/boost/function.hpp:71, from /usr/include/boost/algorithm/string/detail/find_iterator.hpp:18, from /usr/include/boost/a
Meson build system leads to missing library for linker (Was: Bug#934467: pbbam FTBFS with nocheck profile: cram3 missing)
Control: tags -1 pending Hi, I have a problem with latest version of pbbam[1] where upstream switched to meson as build system. I get: ... ... 'src/25a6634@@pbbam@sha/ vcf_VcfWriter.cpp.o' 'src/25a6634@@pbbam@sha/pugixml_pugixml.cpp.o' -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,libpbbam.so.1.0.6 -g -O2 -fdebug-prefix-map=/build/pbbam-1.0.6+ dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -pthread /usr/lib/x86_64-linux-gnu/libz.so /usr/lib/x86_64-linux-gnu/libhts.so -lpbcopper -Wl,--end-group /usr/bin/ld: cannot find -lpbcopper In the pbuilder chroot everything seems to be prepared to find libpbcopper: root:/# find /usr/lib/x86_64-linux-gnu -name "*pbcopper*" /usr/lib/x86_64-linux-gnu/libpbcopper.so /usr/lib/x86_64-linux-gnu/pkgconfig/pbcopper.pc root:/# pkg-config --libs pbcopper -lpbcopper Am I missing something? Kind regards Andreas. [1] https://salsa.debian.org/med-team/pbbam -- http://fam-tille.de
Re: Bug#934467: Meson build system leads to missing library for linker (Was: Bug#934467: pbbam FTBFS with nocheck profile: cram3 missing)
On Thu, 2019-12-19 at 09:54 +0100, Andreas Tille wrote: > Control: tags -1 pending > > Hi, > > I have a problem with latest version of pbbam[1] where upstream > switched > to meson as build system. I get: > > > ... > ... 'src/25a6634@@pbbam@sha/ vcf_VcfWriter.cpp.o' > 'src/25a6634@@pbbam@sha/pugixml_pugixml.cpp.o' -Wl,--as-needed -Wl, > --no-undefined -shared -fPIC -Wl,--start-group -Wl,- > soname,libpbbam.so.1.0.6 -g -O2 -fdebug-prefix-map=/build/pbbam- > 1.0.6+ dfsg=. -fstack-protector-strong -Wformat -Werror=format- > security -Wl,-z,relro -Wl,-z,now -pthread /usr/lib/x86_64-linux- > gnu/libz.so /usr/lib/x86_64-linux-gnu/libhts.so -lpbcopper -Wl,--end- > group > /usr/bin/ld: cannot find -lpbcopper > > > In the pbuilder chroot everything seems to be prepared to find > libpbcopper: > > root:/# find /usr/lib/x86_64-linux-gnu -name "*pbcopper*" > /usr/lib/x86_64-linux-gnu/libpbcopper.so > /usr/lib/x86_64-linux-gnu/pkgconfig/pbcopper.pc > root:/# pkg-config --libs pbcopper > -lpbcopper > > > Am I missing something? > > Kind regards > >Andreas. > > > [1] https://salsa.debian.org/med-team/pbbam > Hi, Basic build clean in a sid pbuilder created using: sudo pbuilder create --debootstrapopts --variant=buildd The only failure(s) I see are the post build tests: # Ran 8 tests, 0 skipped, 6 failed. make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1 make[1]: Leaving directory '/build/pbbam-1.0.6+dfsg' make: *** [debian/rules:13: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 I: copying local configuration E: Failed autobuilding of package Regards Phil -- *** Playing the game for the games sake. *** Twitter: @kathenasorg IRC: kathenas signature.asc Description: This is a digitally signed message part
Bug#946988: coinor-dylp_1.10.4-1_source.changes REJECTED
I have updated the changelog and Vcs and uploaded to mentors. Here is the new changelog: Changes since the last upload: * QA upload * Mark maintainer to QA. * Update to upstream 1.10.4 * Remove Uploaders entry. * Update compat level to 12 * Update Standards-Version to 4.4.1 * Drop coinor-libdylp1-dbg package. * Enadle DOT in configuration and drop the patch. * Fix build-depends (Closes: #934251) * Update copyright * Remove build dependency on cdbs. * Rename package to coinor-libdylp1. * Add source to salsa and update Vcs links In my previous comment I have given my reasoning to rename the package, but if you feel it should stay as coinor-libdylp0, I will be very happy to modify it. -- Regards Sudip
Re: Salsa repository request (dbab)
Hi, On Wed, Dec 18, 2019 at 08:34:55PM -0500, Tong Sun wrote: > So, could somebody please create it for me and give me, suntong-guest, > maintenance access? Done – shout if I messed up ☺ Happy package management days David Kalnischkies signature.asc Description: PGP signature
Bug#947041: RFS: coinutils/2.11.3+repack1-1 [QA]-- Coin-or collection of utility classes (binaries and libraries)
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "coinutils" * Package name : coinutils Version : 2.11.3+repack1-1 Upstream Author : * URL : https://projects.coin-or.org/CoinUtils * License : EPL-1 * Vcs : https://salsa.debian.org/science-team/coinutils Section : science It builds those binary packages: coinor-libcoinutils3v5 - Coin-or collection of utility classes (binaries and libraries) coinor-libcoinutils-dev - Coin-or collection of utility classes (developer files) coinor-libcoinutils-doc - Coin-or collection of utility classes (documentation) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/coinutils Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/coinutils/coinutils_2.11.3+repack1-1.dsc Changes since the last upload: * QA upload [ Debian Janitor ] * Drop use of autotools-dev debhelper. * Update standards version to 4.4.1, no changes needed. * Set upstream metadata fields: Bug-Submit. * Fix day-of-week for changelog entries 2.9.4-1.
Bug#947046: RFS: pacman/10-18 [QA] -- Chase Monsters in a Labyrinth
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pacman" * Package name: pacman Version : 10-18 Upstream Author : Roar Thronaes * URL : ftp.cdrom.com:/pub/FreeBSD/distfiles * License : GPL-2 * Vcs : None Section : games It builds those binary packages: pacman - Chase Monsters in a Labyrinth To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pacman Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pacman/pacman_10-18.dsc Changes since the last upload: * QA upload. * Update Standards-Version to 4.4.1 * Update compat level to 12 * Mark maintainers as QA -- Regards Sudip
Unhide todo list entry in the Ultimate Debian Database
Hi, I accidentally hid a todo list entry in my Ultimate Debian Database. Now I regret it and want it back again. How can I do that? Thx
Debian update package ITP necessary?
Hi, just to be sure, If I'm updating a package that I maintain. I shall just do it. I.e., there isn't any BTS (like ITP) to file and to close, right? thx
Re: Debian update package ITP necessary?
On Fri, Dec 20, 2019 at 2:47 AM Tong Sun wrote: > If I'm updating a package that I maintain. I shall just do it. > I.e., there isn't any BTS (like ITP) to file and to close, right? If you have upload privileges for the package then you can just upload. If you don't then you will need to file an RFS or contact your usual sponsor. https://mentors.debian.net/sponsors/rfs-howto -- bye, pabs https://wiki.debian.org/PaulWise
