Processed: found 789917 in gfortran-triplet/4.9.2-10.1, tagging 793630, tagging 793631, tagging 713663

[email protected] (Debian Bug Tracking System)
Newsgroups gmane.linux.debian.packages.java.devel,gmane.linux.debian.devel.toolchain
Message-ID <[email protected]>
Processing commands for [email protected]:

> found 789917 gfortran-triplet/4.9.2-10.1
Bug #789917 [gfortran-aarch64-linux-gnu,gfortran-arm-linux-gnueabi,gfortran-arm-linux-gnueabihf,gfortran-mips-linux-gnu,gfortran-mipsel-linux-gnu,gfortran-powerpc-linux-gnu] gfortran-<triplet>: leaves alternatives after purge: /usr/bin/<triplet>-f{77, 95}
The source gfortran-triplet and version 4.9.2-10.1 do not appear to match any binary packages
Marked as found in versions gfortran-triplet/4.9.2-10.1.
> tags 793630 + sid stretch
Bug #793630 [src:groovy] groovy: FTBFS due to behaviour change introduced in commons-cli 1.3
Added tag(s) sid and stretch.
> tags 793631 + sid stretch
Bug #793631 [mdadm] mdadm - udev rules call blkid with noraid option, breaks lvm detection
Added tag(s) stretch and sid.
> tags 713663 - jessie
Bug #713663 [src:fatrat] fatrat: FTBFS: config.hpp:46:2: error: #error you must define either BOOST_ASIO_SEPARATE_COMPILATION or BOOST_ASIO_DYN_LINK in your project in order for asio's declarations to be correct. If you're linking dynamically against libtorrent, define BOOST_ASIO_DYN_LINK otherwise BOOST_ASIO_SEPARATE_COMPILATION. You can also use pkg-config or boost build, to automatically apply these defines
Removed tag(s) jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
713663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713663
789917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789917
793630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793630
793631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793631
Debian Bug Tracking System
Contact [email protected] with problems

__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use
[email protected] for discussions and questions.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.