Bug#793331: RFS: postsrsd/1.2-1 [ITP]

2015-07-23 Thread Tomasz Buchert
Hi Oxan, still looking for a sponsor? I've just wanted to implement SRS on my mail server! Tomasz signature.asc Description: Digital signature

Bug#793419: RFS: mirage/0.9.5.2-1 ITA

2015-07-23 Thread Thomas Ross
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package mirage * Package name: mirage Version : 0.9.5.2-1 Upstream Author : Scott Horowitz stonecr...@gmail.com * URL : http://mirageiv.berlios.de/ * License :

Okay to exit after triggers before auto generated #DEBHELPER# code?

2015-07-23 Thread Patrick Schleizer
Hi! Is it sane / policy conform to `exit` after triggers, before the auto generated #DEBHELPER# code had a chance to be executed? For my question to hopefully become more clear, please have a look at the following pseudo code of a postinst script. ## #!/bin/bash set -e case ${1} in

How to inject options only for intel architectures with cmake (Was: Bug#793344: hyphy: FTBFS on non-x86: unrecognized command line option '-msse3')

2015-07-23 Thread Andreas Tille
Hi, considering the fact that SSE3 optimisation is really wanted on intel architectures how could the option be added only for those architectures that understand -msse3 option? Kind regards Andreas. On Wed, Jul 22, 2015 at 10:30:58PM -0400, Aaron M. Ucko wrote: Source: hyphy

Bug#793331: RFS: postsrsd/1.2-1 [ITP]

2015-07-23 Thread Cameron Norman
On Wed, Jul 22, 2015 at 2:27 PM, Oxan van Leeuwen o...@oxanvanleeuwen.nl wrote: Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package postsrsd * Package name: postsrsd Version : 1.2-1 Upstream Author : Timo Röhling

Bug#793419: RFS: mirage/0.9.5.2-1 ITA

2015-07-23 Thread Eriberto
tags 793419 moreinfo thanks Hi, Note that you need work over the last revision in unstable (0.9.5.1-5). Regards, Eriberto 2015-07-23 17:56 GMT-03:00 Thomas Ross th0m4sr...@gmail.com: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my

Re: Bug#782847: RFS: endless-sky/0.8.0-1 [ITP]

2015-07-23 Thread Adam Borowski
On Tue, Jul 21, 2015 at 10:50:23PM -0400, Michael Zahniser wrote: * Package name: endless-sky I'm afraid it fails to build in sbuild, because the first alternative in libjpeg-turbo8-dev | libjpeg62-turbo-dev is notexistant, and sbuild ignores everything but the first, per the buildd policy.

Re: How to inject options only for intel architectures with cmake (Was: Bug#793344: hyphy: FTBFS on non-x86: unrecognized command line option '-msse3')

2015-07-23 Thread Andreas Tille
Hi Gert, On Thu, Jul 23, 2015 at 03:25:00PM +0200, Gert Wollny wrote: On Thu, 2015-07-23 at 14:36 +0200, Andreas Tille wrote: Hi, considering the fact that SSE3 optimisation is really wanted on intel architectures how could the option be added only for those architectures that

Re: Bug#793346: hyphy: FTBFS (32-bit): SimpleListTest._LengthConstructorTest fails

2015-07-23 Thread Jakub Wilk
The test looks like this: _SimpleList sl((long)7); EXPECT_EQ(8,sizeof(sl.lData)); where _SimpleList is defined as: class _SimpleList:public BaseObj { ... long* lData; ... } So what the test essentially checks if pointer size is 8. This is of course false on

Re: How to inject options only for intel architectures with cmake (Was: Bug#793344: hyphy: FTBFS on non-x86: unrecognized command line option '-msse3')

2015-07-23 Thread Gert Wollny
Hello Andreas, On the contrary users want to get the best performance from their recent processors I certainly can understand this ... Is there any better place to help upstream implementing it? This looks quite interesting: https://gcc.gnu.org/wiki/FunctionMultiVersioning It also

Re: [Debian-med-packaging] Bug#793344: How to inject options only for intel architectures with cmake (Was: Bug#793344: hyphy: FTBFS on non-x86: unrecognized command line option '-msse3')

2015-07-23 Thread Gert Wollny
It also seems to create the run-time decision manually. Of course I meant automatically. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Re: How to inject options only for intel architectures with cmake (Was: Bug#793344: hyphy: FTBFS on non-x86: unrecognized command line option '-msse3')

2015-07-23 Thread Andreas Tille
Hi Gert, I'll forward this. I just wait whether all bugs are now really closed. I found that upstream is actually checking via cmake for SSE3 extension but did not used the check results just for the test suite. Thanks for all your help anyway Andreas. On Thu, Jul 23, 2015 at

Bug#793312: marked as done (RFS: pyoperators/0.13.6-1)

2015-07-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jul 2015 16:28:09 + with message-id e1zijlt-0004ju...@quantz.debian.org and subject line closing RFS: pyoperators/0.13.6-1 has caused the Debian Bug report #793312, regarding RFS: pyoperators/0.13.6-1 to be marked as done. This means that you claim that the problem

Re: How to inject options only for intel architectures with cmake (Was: Bug#793344: hyphy: FTBFS on non-x86: unrecognized command line option '-msse3')

2015-07-23 Thread Gert Wollny
On Thu, 2015-07-23 at 14:36 +0200, Andreas Tille wrote: Hi, considering the fact that SSE3 optimisation is really wanted on intel architectures how could the option be added only for those architectures that understand -msse3 option? You can do this: ### include(CheckCXXCompilerFlag)

Re: Bug#793346: hyphy: FTBFS (32-bit): SimpleListTest._LengthConstructorTest fails

2015-07-23 Thread Andreas Tille
Hi, any hint (except excluding 32 bit architectures) would be welcome. Kind regards Andreas. On Wed, Jul 22, 2015 at 10:37:05PM -0400, Aaron M. Ucko wrote: Source: hyphy Version: 2.2.5+dfsg-1 Severity: important The i386 and kfreebsd-i386 builds of hyphy both failed with an error

Re: RFS: Please upload cl-asdf package

2015-07-23 Thread Christoph Egger
Faré f...@tunes.org writes: On Wed, Jul 22, 2015 at 3:13 PM, Christoph Egger christ...@christoph-egger.org wrote: Christoph Egger christ...@debian.org writes: There seems to be a somewhat large diff between the upstream release and the debian package source? Is this on purpose? Then the