Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

Hi, > On Tue, Aug 30, 2016 at 12:16:26PM +0200, Andreas Tille wrote: >> I tried to upgrade salmon to latest upstream where this problem might >> have possibly solved. I'm currently struck by the fact that >> >>https://github.com/COMBINE-lab/RapMap >> >> is needed to build. > > I have

Bug#836230: [Debian-med-packaging] Bug#836230: genometools: FTBFS in testing (a2x: ERROR: "xsltproc" returned non-zero exit status 6)

Hi Santiago, thanks for reporting this. > I tried to build this package in stretch with "dpkg-buildpackage -A" > (which is what the "Arch: all" autobuilder would do to build it) > but it failed: […] > a2x: ERROR: "xsltproc" --stringparam callout.graphics 0 --stringparam > navig.graphics 0

Bug#832839: Bug#832839: artemis: FTBFS: dpkg-gencontrol: error: error occurred while parsing Depends field:

On 29/07/2016 12:49, Andreas Tille wrote: > On Fri, Jul 29, 2016 at 10:19:29AM +0100, Sascha Steinbiss wrote: >>>> dpkg-gencontrol: error: error occurred while parsing Depends field: >>>> , >>>> default-jre | java5-runtime | java6-runtime | java7-runtime |

Bug#832839: [Debian-med-packaging] Bug#832839: artemis: FTBFS: dpkg-gencontrol: error: error occurred while parsing Depends field:

Hi, > During a rebuild of all packages in sid, your package failed to build on > amd64. [...] >>dh_gencontrol >> dpkg-gencontrol: warning: can't parse dependency $ >> dpkg-gencontrol: error: error occurred while parsing Depends field: >> , >> default-jre | java5-runtime | java6-runtime |

Bug#827805: [Pkg-privacy-maintainers] Bug#827805: onioncircuits: FTBFS: E: Please add apropriate interpreter package to Build-Depends, see pybuild(1) for details at /usr/share/perl5/Debian/Debhelper/B

ACHE=/home/lamby/.cache/pip > HOME=/home/lamby > LOGNAME=lamby > SHLVL=1 > > PWD=/home/lamby/temp/cdt.20160621104415.5SuLtY7TVL.onioncircuits/onioncircuits-0.4 > OLDPWD=/home/lamby/temp/cdt.20160621104415.5SuLtY7TVL.onioncircuits > GPG_TTY=/dev/console > QUILT_PATCH

Bug#803550: [Debian-med-packaging] Bug#803550: rsem: uninstallable on architectures without bowtie

Hi all, I re-introduced the build dependency on bowtie and also did some minor housekeeping. Committed the fix in git. Cheers Sascha > On 19 Mar 2016, at 14:34, Andreas Beckmann wrote: > > Package: rsem > Followup-For: Bug #803550 > > Hi, > > the > B-D: bowtie | bowtie2 >

Bug#818725: picard-tools: FTBFS in unstable

Is this bug still an issue? Picard-tools has been recently updated to a newer upstream version which builds fine for me in a current sid pbuilder chroot. I'm asking because the autoremoval of picard-tools due to this bug would also drag Artemis with it... Cheers Sascha On Sat, 19 Mar 2016

Bug#818397: salmon: FTBFS: 'MEM_F_SELF_OVLP' was not declared in this scope

Hi, I have pushed a fix for this to git. I would be glad if someone could take a look. Thanks Sascha On Wed, 16 Mar 2016 13:36:46 -0700 Martin Michlmayr wrote: > Package: salmon > Version: 0.4.2+ds1-2 > Severity: serious > > This package fails to build in unstable: > > >

Bug#798789: netperf: fix for FTBFS

+ +++ netperf-2.6.0/debian/changelog 2016-04-05 10:02:33.0 + @@ -1,3 +1,10 @@ +netperf (2.6.0-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Adjust inline statements to fix FTBFS (Closes: #798789) + + -- Sascha Steinbiss <sas...@steinbiss.name> Tue, 05 Ap

Bug#813465: [Debian-med-packaging] Bug#813465: bcftools: FTBFS: vcfmerge.c:424:6: error: conflicting types for 'bcf_hdr_merge'

This is most likely related to the htslib 1.3 upgrade. I expect that updating bcftools to the most recent upstream release (1.3) as well will help. On 02/02/2016 09:49, Chris Lamb wrote: > Source: bcftools > Version: 1.2-2 > Severity: serious > Justification: fails to build from source > User:

Bug#808552: dh-dist-zilla: builds fail in recent pbuilder versions

Hi Axel, […] >> I have been able to fix the issue locally by setting >> BUILD_HOME="/tmp" in my .pbuilderrc, and afterwards everything >> builds fine for me. However, obviously that wouldn't help on build >> machines where I don't have control over that (autobuilders, ...). > > Exactly. > >> Is

Bug#798900: [Debian-med-packaging] Bug#798900: lintian: false positive: source-is-missing for non-minified JS files

: > On Sun, 2015-10-11 at 13:38 +0100, Sascha Steinbiss wrote: > >> It looks like JSHint is not a hard requirement but will just not be used if >> it’s >> not there: >> https://github.com/DataTables/DataTablesSrc/blob/master/build/make.sh#L58 >> Otherwise I wou

Bug#798900: [Debian-med-packaging] Bug#798900: lintian: false positive: source-is-missing for non-minified JS files

Hi, >> For the time being, would it be enough to add the DataTablesSrc repo >> content (and a README) to aegean’s debian/missing-sources to comply >> with DFSG until a DataTables package gets into the archive? > > Better than nothing but I think it still violates ftpmaster policy > since it

Bug#798900: [Debian-med-packaging] Bug#798900: lintian: false positive: source-is-missing for non-minified JS files

Hi all, >>> Looks like the JQuery DataTables libraries included are flagged as minified >>> without source on the basis that they have lines longer than 1024 >>> characters: >>> P: aegean source: source-contains-prebuilt-javascript-object >>> data/share/vendor/jquery.dataTables.js line length

Bug#798900: lintian: false positive: source-is-missing for non-minified JS files

Hi Paul, >> Looks like the JQuery DataTables libraries included are flagged as minified >> without source on the basis that they have lines longer than 1024 characters: >> P: aegean source: source-contains-prebuilt-javascript-object >> data/share/vendor/jquery.dataTables.js line length is 1397

Bug#793514: Fwd: Staden authoren ??? [Re: Bug#793514: FTBFS: conflicting types for append_int]

releasing a compatible version of the Staden Package. The code is ready, it just needs releasing. I'll see what I can do. Thanks, Andrew On 07/08/15 16:35, Sascha Steinbiss wrote: Hi Andrew, many thanks for your quick reply and for your willingness to look into the issue. Best

Bug#793514: Fwd: Staden authoren ??? [Re: Bug#793514: FTBFS: conflicting types for append_int]

, Andrew On 07/08/15 15:26, Sascha Steinbiss wrote: Dear James and Andrew, I am writing to kindly bring the following Staden build issue to your attention. The Debian automated build system is currently unable to build the code from source due to multiple declarations of identically named

Bug#793514: Fwd: Staden authoren ??? [Re: Bug#793514: FTBFS: conflicting types for append_int]

Dear James and Andrew, I am writing to kindly bring the following Staden build issue to your attention. The Debian automated build system is currently unable to build the code from source due to multiple declarations of identically named functions with different parameter and return types. We

<    1   2