On Thu, Apr 30, 2020 at 10:33 AM Matthew Fernandez
wrote:
>
> > On Apr 30, 2020, at 00:31, Andreas Tille wrote:
> >
> > On Wed, Apr 29, 2020 at 05:51:26PM -0700, Matthew Fernandez wrote:
> >
> >> The other option I suggested was Valgrind, but if you can’t run apt-file
> >> you probably can’t ins
On Fri, Apr 17, 2020 at 7:21 AM Andreas Tille wrote:
>
> Control: tags -1 help
>
> as it can be seen on the recent build log of clustalo on mips[1] the
> build fails with
>
> # Run additional test from python-biopython package to verify that
> # this will work as well
> src/clustalo -i debian/test
On Fri, Apr 17, 2020 at 7:21 AM Andreas Tille wrote:
> ...
> So it seems the bus error occures somehow here:
>
>
> https://salsa.debian.org/med-team/clustalo/-/blob/master/src/clustal/pair_dist.c#L346
NewProgress is at
https://salsa.debian.org/med-team/clustalo/-/blob/master/src/clustal/prog
On Fri, May 1, 2020 at 2:14 AM Andreas Tille wrote:
>
> ...
> ==13209== Process terminating with default action of signal 10 (SIGBUS)
> ==13209==at 0x12D5CC: PairDistances (pair_dist.c:346)
> ==13209==by 0x119410: AlignmentOrder (clustal-omega.c:835)
> ==13209==by 0x11A6C4: Align (clu
On Fri, May 1, 2020 at 3:05 AM Jeffrey Walton wrote:
>
> On Fri, May 1, 2020 at 2:14 AM Andreas Tille wrote:
> >
> > ...
> > ==13209== Process terminating with default action of signal 10 (SIGBUS)
> > ==13209==at 0x12D5CC: PairDistances (pair_dist.c:346
On Sun, May 10, 2020 at 2:57 PM Andreas Tille wrote:
>
> ...
> > --- clustalo-1.2.4/debian/rules 2020-04-14 12:19:44.0 +0300
> > +++ clustalo-1.2.4/debian/rules 2020-04-14 12:19:44.0 +0300
> > @@ -9,6 +9,11 @@
> > %:
> > dh $@
> >
> > +ifneq (,$(filter $(DEB_HOST
On Wed, Sep 16, 2015 at 1:48 AM, Niels Thykier wrote:
> On 2015-09-16 06:47, Jeffrey Walton wrote:
>> Hi Everyone,
>>
>> I work with a free/open source project. We have a failure report from
>> a Debian package maintainer on an s390.
>>
>
> Hi Jeffrey,
>
Hi Everyone,
We took a bug report from a Debain maintainer under Debian's X32
environment (https://wiki.debian.org/X32Port). Our bugs triggered some
Debian bugs as we worked through some of the issues.
One of the issues we encountered was GDB's inability to debug a C++
program. It was reported at
>> At this point, I *think* I need to perform 3 tasks, with an optional 4th
>> task:
>>
>> (1) add the "port-x32" tag or category to the report because the
>> fellow writing the X32 wiki page appears to monitor it (see Bug
>> Reports at the end of https://wiki.debian.org/X32Port).
>
>> (2) add the
On Mon, Sep 21, 2015 at 3:15 AM, Paul Wise wrote:
> On Mon, Sep 21, 2015 at 6:51 AM, Wookey wrote:
>
>> bts tag 799556 + port-x32 patch upstream
>
> Please note that port-x32 isn't an official tag, I think you want
> usertags instead:
>
> https://www.debian.org/Bugs/server-request#usertag
> https:
On Mon, Sep 21, 2015 at 12:26 AM, Jeffrey Walton wrote:
> Hi Everyone,
>
> We took a bug report from a Debain maintainer under Debian's X32
> environment (https://wiki.debian.org/X32Port). Our bugs triggered some
> Debian bugs as we worked through some of the issues.
>
On Mon, Sep 21, 2015 at 8:20 PM, Sergio Durigan Junior
wrote:
> On Monday, September 21 2015, Jeffrey Walton wrote:
>
>> Thanks to Wookey, Paul, Rebecca, Jakub, I was able to send the control
>> email for report.
>>
>> The control messaged resulted in a few issu
For some reason, I seem to receive a copy of everyone's bug reports.
I tried to unsubscribe by sending an unsubscribe email to
submit-requ...@bugs.debian.org, but nothing happened. (-REQUEST@
is supposed to be the address to use).
Why am I receiving everyone's bugs, and how do I stop it?
(There'
On Tue, Sep 22, 2015 at 1:10 PM, Alex Vong wrote:
> Hi Jeffrey,
>
> What sort of bug reports are you receiving? If their titles are in the
> form "Bug#: foolishbar (RFS: blablabla)", then they should
> belong to the debian-mentors mailing list. I guess the type of bug
> reports you are receiving s
Hi Everyone,
I work with the Crypto++ project. Debian carries the project and makes
it available through the package
https://packages.debian.org/source/libcrypto++.
We have specific recommendations for packaging Crypto++ for
distribution (cf., http://cryptopp.com/wiki/Config.h#Recommendations).
S
> We would really, really prefer that you not do this, and instead work with
> whoever is packaging the library for Debian to add a test to the packaging
> rules themselves to be sure that they're built correctly.
>
> The reason for this is that Debian's packaging tools, by design, work
> exactly t
On Wed, Sep 30, 2015 at 3:55 AM, Russ Allbery wrote:
> Jeffrey Walton writes:
>
>> OK, thanks. We are working with László Böszörményi. He's been very
>> helpful.
>
>> But if László ever leaves Debian or stops Crypto++, then I loose my
>> contact and
Hi Everyone,
I have one last question related to packaging and installation. (I
hope it is the last question).
Crypto++ has test files. When they are run from $PWD, them they work
fine. After installation into, say, /usr/share/, they break because
the location is an implicit dependency. So the tw
18 matches
Mail list logo
