Re: Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Matthew Fernandez 
> One small issue... Valgrind recommends -O0 or -O1

TIL :) Thanks, Jeff!

> You can sometimes locate a bus error at build time with -Wcast-align.
> At runtime you can usually locate them with -fsanitize=undefined.

I had previously tried UBSan and, while it turned up a number of shifting and 
strict aliasing violations, it did not find anything that I believe could be 
the cause of the mipsel bus error.

> I can't track the trail any further. The source code is missing for
> pvm_pkdouble and pvm_upkdouble. I would be very suspect of
> pvm_pkdouble and pvm_upkdouble.

Unfortunately I think the reason you can’t find their source is that this code 
is unused. It is inside a ifdef SRE_ENABLE_PVM block and this macro is not 
defined during the build. You can confirm this by deleting these lines and 
recompiling.

AFAICT the code in src/squid is a library taken wholesale from somewhere else 
and then modified (see src/squid/clustalo.README). It contains a lot of code 
that goes unused in Clustal Omega.

Is the priority goal here to simply ship a non-crashing clustalo mipsel binary 
that BioPython can depend on? If so, maybe we can just disable compiler 
optimisation (-O0) and this may avoid provoking the bus error. Of course this 
doesn’t fix the underlying problem(s), but it looks as if debugging this to its 
root cause is going to result in the Debian package carrying a lot of invasive 
dquilt patches on top of upstream. OTOH I don’t know the performance 
requirements of BioPython and maybe an unoptimised clustalo is unacceptable to 
it.

Not all files in my package installed

2020-04-30 Thread Tong Sun 
Hi,

I've never experience this before and I have no clue either, but not all
files in my package get installed:

--
% apt-get install --reinstall -y dbab
. . .
Get:1 http://deb.debian.org/debian testing/main amd64 dbab all 1.3.3-1
[22.3 kB]
Fetched 22.3 kB in 0s (204 kB/s)
. . .
Preparing to unpack .../archives/dbab_1.3.3-1_all.deb ...
Unpacking dbab (1.3.3-1) over (1.3.3-1) ...
Setting up dbab (1.3.3-1) ...

% dpkg -L dbab
/.
/etc
/etc/dbab
/etc/dbab/dbab.addr
/etc/dbab/dbab.list+
/etc/dbab/dbab.list-
/etc/dbab/dbab.proxy
/etc/init.d
/etc/init.d/dbab
/lib
/lib/init
/lib/init/dbab-init-d-script
/lib/systemd
/lib/systemd/system
/lib/systemd/system/dbab.service
/usr
/usr/sbin
/usr/sbin/dbab-add-list
/usr/sbin/dbab-chk-list
/usr/sbin/dbab-get-list
/usr/sbin/dbab-svr
/usr/sbin/dhcp-add-wpad
/usr/share
/usr/share/doc
/usr/share/doc/dbab
/usr/share/doc/dbab/README.Debian
/usr/share/doc/dbab/changelog.Debian.gz
/usr/share/doc/dbab/copyright
/usr/share/doc/dbab/dbab-dnsmasq.intranet.conf
/usr/share/doc/dbab/dbab-dnsmasq.service.conf
/usr/share/doc/dbab/dbab-squid.localnet.conf
/usr/share/doc/dbab/dbab-squid.service.conf
/usr/share/doc/dbab/dbab.md.gz
/usr/share/man
/usr/share/man/man8
/usr/share/man/man8/dbab-svr.8.gz
/usr/share/man/man8/dbab-add-list.8.gz
/usr/share/man/man8/dbab-chk-list.8.gz
/usr/share/man/man8/dbab-get-list.8.gz
/usr/share/man/man8/dhcp-add-wpad.8.gz
--

Everything looks good so far, but --

--
$ ls -l `dpkg -L dbab` > /dev/null
ls: cannot access '/usr/share/doc/dbab/README.Debian': No such file or
directory
ls: cannot access '/usr/share/doc/dbab/changelog.Debian.gz': No such file
or directory
ls: cannot access '/usr/share/doc/dbab/dbab-dnsmasq.intranet.conf': No such
file or directory
ls: cannot access '/usr/share/doc/dbab/dbab-dnsmasq.service.conf': No such
file or directory
ls: cannot access '/usr/share/doc/dbab/dbab-squid.localnet.conf': No such
file or directory
ls: cannot access '/usr/share/doc/dbab/dbab-squid.service.conf': No such
file or directory
ls: cannot access '/usr/share/doc/dbab/dbab.md.gz': No such file or
directory
ls: cannot access '/usr/share/man/man8': No such file or directory
ls: cannot access '/usr/share/man/man8/dbab-svr.8.gz': No such file or
directory
ls: cannot access '/usr/share/man/man8/dbab-add-list.8.gz': No such file or
directory
ls: cannot access '/usr/share/man/man8/dbab-chk-list.8.gz': No such file or
directory
ls: cannot access '/usr/share/man/man8/dbab-get-list.8.gz': No such file or
directory
ls: cannot access '/usr/share/man/man8/dhcp-add-wpad.8.gz': No such file or
directory
--

What could possibly be wrong?

The package is at:
https://salsa.debian.org/debian/dbab

Thanks!

Bug#959212: RFS: libowfat/0.30-3 [QA] -- Reimplementation of libdjb, shared library

2020-04-30 Thread Sudip Mukherjee 
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libowfat"

 * Package name: libowfat
   Version : 0.30-3
   Upstream Author : Felix von Leitner 
 * URL : http://www.fefe.de/libowfat/
 * License : GPL-2
 * Vcs : https://salsa.debian.org/debian/libowfat
   Section : libs

It builds those binary packages:

  libowfat0 - Reimplementation of libdjb, shared library
  libowfat-dev - Reimplementation of libdjb, development files
  libowfat-dietlibc-dev - Reimplementation of libdjb, dietlibc version

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/libowfat

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/libo/libowfat/libowfat_0.30-3.dsc

Changes since the last upload:

   * QA upload.
   * Fix FTBFS with GCC-10. (Closes: #957462)
   * Orphan the package. (See: #813097)
   * Update Standards-Version to 4.5.0
   * Use debhelper-compat.
 - Update compat level to 13.
   * Mark Vcs to salsa.
   * Add symbols file.
   * Remove whitespace from control and changelog.
   * Remove duplicate section.


-- 
Regards
Sudip

Re: Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Andreas Tille 
Hi Jeffrey,

thanks a lot for this analysis.  Any chance that somebody could
turn this into a patch I could try?

Kind regards

 Andreas.

On Thu, Apr 30, 2020 at 03:40:12PM -0400, Jeffrey Walton wrote:
> 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/progress.c#L53.
> It uses a progress_t at
> https://salsa.debian.org/med-team/clustalo/-/blob/master/src/clustal/progress.h#L25.
> 
> typedef struct {
> /* where to write to */
> FILE *prFile;
> /* prefix printed before each step */
> char *pcPrefix;
> bool bPrintCR;
> char pcLastLogMsg[1024];
> Stopwatch_t *prStopwatch;
> } progress_t;
> 
> And stopwatch_t at
> https://salsa.debian.org/med-team/clustalo/-/blob/master/src/squid/stopwatch.h:
> 
> struct stopwatch_s {
>   time_t t0; /* Wall clock time, ANSI time()  */
> #ifdef SRE_STRICT_ANSI
>   clock_t cpu0; /* CPU time, ANSI clock()*/
> #else
>   struct tms cpu0; /* CPU/system time, POSIX times()*/
> #endif
> 
>   double elapsed; /* elapsed time, seconds */
>   double user; /* CPU time, seconds */
>   double sys; /* system time, seconds */
> };
> 
> There are your doubles that are likely the problem.
> 
> And what do we have here at
> https://salsa.debian.org/med-team/clustalo/-/blob/master/src/squid/stopwatch.c#L276
> ...
> 
> void
> StopwatchPVMPack(Stopwatch_t *w)
> {
>   pvm_pkdouble(&(w->elapsed), 1, 1);
>   pvm_pkdouble(&(w->user),1, 1);
>   pvm_pkdouble(&(w->sys), 1, 1);
> }
> void
> StopwatchPVMUnpack(Stopwatch_t *w)
> {
>   pvm_upkdouble(&(w->elapsed), 1, 1);
>   pvm_upkdouble(&(w->user),1, 1);
>   pvm_upkdouble(&(w->sys), 1, 1);
> }
> 
> I can't track the trail any further. The source code is missing for
> pvm_pkdouble and pvm_upkdouble. I would be very suspect of
> pvm_pkdouble and pvm_upkdouble.
> 
> Jeff
> 

-- 
http://fam-tille.de

Re: Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Jeffrey Walton 
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/progress.c#L53.
It uses a progress_t at
https://salsa.debian.org/med-team/clustalo/-/blob/master/src/clustal/progress.h#L25.

typedef struct {
/* where to write to */
FILE *prFile;
/* prefix printed before each step */
char *pcPrefix;
bool bPrintCR;
char pcLastLogMsg[1024];
Stopwatch_t *prStopwatch;
} progress_t;

And stopwatch_t at
https://salsa.debian.org/med-team/clustalo/-/blob/master/src/squid/stopwatch.h:

struct stopwatch_s {
  time_t t0; /* Wall clock time, ANSI time()  */
#ifdef SRE_STRICT_ANSI
  clock_t cpu0; /* CPU time, ANSI clock()*/
#else
  struct tms cpu0; /* CPU/system time, POSIX times()*/
#endif

  double elapsed; /* elapsed time, seconds */
  double user; /* CPU time, seconds */
  double sys; /* system time, seconds */
};

There are your doubles that are likely the problem.

And what do we have here at
https://salsa.debian.org/med-team/clustalo/-/blob/master/src/squid/stopwatch.c#L276
...

void
StopwatchPVMPack(Stopwatch_t *w)
{
  pvm_pkdouble(&(w->elapsed), 1, 1);
  pvm_pkdouble(&(w->user),1, 1);
  pvm_pkdouble(&(w->sys), 1, 1);
}
void
StopwatchPVMUnpack(Stopwatch_t *w)
{
  pvm_upkdouble(&(w->elapsed), 1, 1);
  pvm_upkdouble(&(w->user),1, 1);
  pvm_upkdouble(&(w->sys), 1, 1);
}

I can't track the trail any further. The source code is missing for
pvm_pkdouble and pvm_upkdouble. I would be very suspect of
pvm_pkdouble and pvm_upkdouble.

Jeff

Re: Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Jeffrey Walton 
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/tests/biopython_testdata/f002 --guidetree-out 
> temp_test.dnd -o temp_test.aln --outfmt clustal --force
> make[1]: *** [debian/rules:25: override_dh_auto_test-arch] Bus error

You can sometimes locate a bus error at build time with -Wcast-align.
At runtime you can usually locate them with -fsanitize=undefined.

On x86 -Wcast-align usually triggers when casting to/from floats and
doubles. I don't know what triggers on MIPS, bit it may include
integers. You should look for all calls that perform casts to/from
void* and uint8_t* with a dereference. I.e.,

uint8_t y[8] = ...;
double x = *(double*)y;

If MIPS is sensitive to alignment (beyond x86 slop), then something
like this will get you into trouble, too:

uint8_t y[8] = ...;
unsigned long x = *(unsigned long*)y;

I don't know about MIPS, but... I've experienced the problem with
long's on SPARCv8. SPARCv8 needs 8-byte alignments because they have a
specialized 64-bit move instruction. Or SPARCv8 needs an extra
compile/link switch that disables the 64-bit move. The option is
-xmemalign, which tells the toolchain what alignments can be assumed.

Jeff

Re: Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Jeffrey Walton 
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 install Valgrind either.
> >
> > Well, I guess apt-get is permitted for sudo but not apt-file.  So I can
> > probably install valgrind inside the chroot environment.  I've never
> > worked with valgrind.  What am I supposed to do?
>
> Valgrind, in its default mode, checks for a variety of memory issues 
> (use-after-free, write out-of bounds, …). You don’t need any special 
> configure/build options, but you probably want to enable debug symbols 
> (`export CFLAGS=-g; export CXXFLAGS=-g`). Then you can prefix the test you’re 
> running with Valgrind: `valgrind ./src/clustalo -i 
> debian/tests/biopython_testdata/f002 …`.

One small issue... Valgrind recommends -O0 or -O1:


Compile your program with -g to include debugging information so that
Memcheck's error messages include exact line numbers. Using -O0 is
also a good idea, if you can tolerate the slowdown. With -O1 line
numbers in error messages can be inaccurate, although generally
speaking running Memcheck on code compiled at -O1 works fairly well,
and the speed improvement compared to running -O0 is quite
significant. Use of -O2 and above is not recommended as Memcheck
occasionally reports uninitialised-value errors which don't really
exist.


Also see the Valgrind Quick Start Guide, Section 2. Preparing Your
Programs, at http://valgrind.org/docs/manual/QuickStart.html.

Jeff

Re: Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Andreas Tille 
On Thu, Apr 30, 2020 at 07:17:50AM -0700, Matthew Fernandez wrote:
> 
> Valgrind, in its default mode, checks for a variety of memory issues 
> (use-after-free, write out-of bounds, …). You don’t need any special 
> configure/build options, but you probably want to enable debug symbols 
> (`export CFLAGS=-g; export CXXFLAGS=-g`). Then you can prefix the test you’re 
> running with Valgrind: `valgrind ./src/clustalo -i 
> debian/tests/biopython_testdata/f002 …`.


Running on mipsel:

(sid_mipsel-dchroot)tille@eller:~/clustalo$ valgrind src/clustalo -i 
debian/tests/biopython_testdata/f002 --guidetree-out temp_test.dnd -o 
temp_test.aln --outfmt clustal --force
==15149== Memcheck, a memory error detector
==15149== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==15149== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==15149== Command: src/clustalo -i debian/tests/biopython_testdata/f002 
--guidetree-out temp_test.dnd -o temp_test.aln --outfmt clustal --force
==15149== 
==15149== Conditional jump or move depends on uninitialised value(s)
==15149==at 0x4007828: cached_fpabi_reject_phdr_p 
(dl-machine-reject-phdr.h:57)
==15149==by 0x4007828: elf_machine_reject_phdr_p 
(dl-machine-reject-phdr.h:217)
==15149==by 0x4008080: open_verify.constprop.0 (dl-load.c:1688)
==15149==by 0x4009D7C: _dl_map_object (dl-load.c:2181)
==15149==by 0x40011F8: map_doit (rtld.c:607)
==15149==by 0x401B2A8: _dl_catch_exception (dl-error-skeleton.c:196)
==15149==by 0x401B334: _dl_catch_error (dl-error-skeleton.c:215)
==15149==by 0x4001138: do_preload (rtld.c:778)
==15149==by 0x4002560: handle_preload_list (rtld.c:879)
==15149==by 0x4005B08: dl_main (rtld.c:1684)
==15149==by 0x401A094: _dl_sysdep_start (dl-sysdep.c:253)
==15149==by 0x400199C: _dl_start_final (rtld.c:447)
==15149==by 0x4001D44: _dl_start (rtld.c:539)
==15149== 
==15149== Invalid read of size 1
==15149==at 0x486F558: ??? (in 
/usr/lib/mipsel-linux-gnu/libargtable2.so.0.1.8)
==15149==by 0x486F5F0: ??? (in 
/usr/lib/mipsel-linux-gnu/libargtable2.so.0.1.8)
==15149==  Address 0x4d655c5 is 0 bytes after a block of size 37 alloc'd
==15149==at 0x484B89C: malloc (in 
/usr/lib/mipsel-linux-gnu/valgrind/vgpreload_memcheck-mips32-linux.so)
==15149==by 0x126674: CkMalloc (util.c:83)
==15149==by 0x126864: CkStrdup (util.c:213)
==15149==by 0x1108F4: ConvertOldCmdline(int*, char***, int, char**) 
(main.cpp:358)
==15149==by 0x10FCDC: main (main.cpp:467)
==15149== 
==15149== Invalid read of size 4
==15149==at 0x1221B8: PairDistances (pair_dist.c:346)
==15149==by 0x114774: AlignmentOrder (clustal-omega.c:835)
==15149==by 0x115024: Align (clustal-omega.c:1221)
==15149==by 0x112EB4: MyMain (mymain.c:1192)
==15149==by 0x10FCF0: main (main.cpp:469)
==15149==  Address 0x83b0 is not stack'd, malloc'd or (recently) free'd
==15149== 
==15149== 
==15149== Process terminating with default action of signal 10 (SIGBUS)
==15149==at 0x1221B8: PairDistances (pair_dist.c:346)
==15149==by 0x114774: AlignmentOrder (clustal-omega.c:835)
==15149==by 0x115024: Align (clustal-omega.c:1221)
==15149==by 0x112EB4: MyMain (mymain.c:1192)
==15149==by 0x10FCF0: main (main.cpp:469)
==15149== 
==15149== HEAP SUMMARY:
==15149== in use at exit: 8,039 bytes in 34 blocks
==15149==   total heap usage: 112 allocs, 78 frees, 77,811 bytes allocated
==15149== 
==15149== LEAK SUMMARY:
==15149==definitely lost: 128 bytes in 2 blocks
==15149==indirectly lost: 0 bytes in 0 blocks
==15149==  possibly lost: 0 bytes in 0 blocks
==15149==still reachable: 7,911 bytes in 32 blocks
==15149== suppressed: 0 bytes in 0 blocks
==15149== Rerun with --leak-check=full to see details of leaked memory
==15149== 
==15149== Use --track-origins=yes to see where uninitialised values come from
==15149== For lists of detected and suppressed errors, rerun with: -s
==15149== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
Bus error


Is this different from your tests on amd64?

 
> > On the other hand:  Is valgrind possibly able to uncover issues also
> > on any other architecture?
> 
> You mean if we were to use Valgrind to debug this on e.g. x86? In my own 
> experiments on amd64, both ASan and Valgrind found multiple issues in both 
> Clustal Omega and its dependency, argtable2. However I don’t believe any of 
> the remaining ones I was seeing after the last patches I sent you could be 
> causing the mipsel bus error; they were all memory leaks.

Thanks again for your great support and the time you've spent.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Re: Bug#959178: RFS: eject/2.1.5+deb1+cvs20081104-15 [ITA] -- ejects CDs and operates CD-Changers under Linux

2020-04-30 Thread atzlinux 

在 2020/4/30 下午9:20, Adam Borowski 写道:
> On Thu, Apr 30, 2020 at 08:42:07PM +0800, atzlinux wrote:
>> * Package name : eject
>> Version : 2.1.5+deb1+cvs20081104-15
> Somehow, initial whitespace in your mail is corrupted.

I am use thunderbird ,xfce. The RFS email  is sended by click "Send the
filled out template below by mail
"
link under Firefox on:

https://mentors.debian.net/sponsors/rfs-howto/eject

I also didn't know why "initial whitespace" is corrupted. Perhaps is
relations to the locale setting,I use locale LANG=zh_CN.utf8.

>> Changes since the last upload:
>>
>> [ 肖盛文 ]
>> * d/control:
>> Bumped Standards-Version to 4.5.0
>> add Build-Depends: debhelper (>= 12)
>> delete lintian useless-autoreconf-build-depends: autotools-dev
>> +Rules-Requires-Root: no
>> * Fixs lintian:
>> unused-file-paragraph-in-dep5-copyright
>> wildcard-matches-nothing-in-dep5-copyright
>> executable-in-usr-lib usr/lib/eject/dmcrypt-get-device
>> * delete the outdated watch url
>> * add debian/manpages
>> * add debian/install
>> * add debian/eject-udeb.install
>> * d/rules:
>> use install files
>> use manpages
>> deleted no use deb_dir udeb_dir env variables
>> add dh_dwz for udeb packages
>> * New maintainer (Closes: #92)
> Alas, it fails to build for me:
>
> dh_dwz -Xdebian/eject-udeb/usr/bin/eject
> dh_dwz -Xdebian/eject-udeb/usr/bin/volname
> dwz: debian/eject/usr/bin/eject: .gnu_debugaltlink section already present
> dwz: debian/eject/usr/bin/volname: .gnu_debugaltlink section already present
> dwz: debian/eject/usr/lib/eject/dmcrypt-get-device: .gnu_debugaltlink section 
> already present
> dwz: Too few files for multifile optimization
> dh_dwz: error: dwz 
>

Re: Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Matthew Fernandez 


> 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 install Valgrind either.
> 
> Well, I guess apt-get is permitted for sudo but not apt-file.  So I can
> probably install valgrind inside the chroot environment.  I've never
> worked with valgrind.  What am I supposed to do?

Valgrind, in its default mode, checks for a variety of memory issues 
(use-after-free, write out-of bounds, …). You don’t need any special 
configure/build options, but you probably want to enable debug symbols (`export 
CFLAGS=-g; export CXXFLAGS=-g`). Then you can prefix the test you’re running 
with Valgrind: `valgrind ./src/clustalo -i debian/tests/biopython_testdata/f002 
…`.

Valgrind and ASan serve roughly the same purpose in this scenario, but I 
usually tend to prefer ASan because it is more efficient and tends to give you 
more accurate debugging clues.

> On the other hand:  Is valgrind possibly able to uncover issues also
> on any other architecture?

You mean if we were to use Valgrind to debug this on e.g. x86? In my own 
experiments on amd64, both ASan and Valgrind found multiple issues in both 
Clustal Omega and its dependency, argtable2. However I don’t believe any of the 
remaining ones I was seeing after the last patches I sent you could be causing 
the mipsel bus error; they were all memory leaks.

Bug#959181: RFS: lebiniou/3.41-1 -- displays images that evolve with sound

2020-04-30 Thread Olivier Girondel 
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "lebiniou":

 * Package name: lebiniou
   Version : 3.41-1
   Upstream Author : Olivier Girondel 
 * URL : https://biniou.net
 * License : GPL-2+
   Section : graphics

It builds this binary package:

  lebiniou - displays images that evolve with sound

The package appears to be lintian-clean.

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/lebiniou

Alternatively, one can download the package with dget using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/l/lebiniou/lebiniou_3.41-1.dsc

Changes since the last upload:

  * New upstream release 3.41.
  * Fix FTBFS with gcc-10 (Closes: #957421)

Regards,
  Olivier Girondel

Bug#959178: RFS: eject/2.1.5+deb1+cvs20081104-15 [ITA] -- ejects CDs and operates CD-Changers under Linux

2020-04-30 Thread Adam Borowski 
On Thu, Apr 30, 2020 at 08:42:07PM +0800, atzlinux wrote:
> * Package name : eject
> Version : 2.1.5+deb1+cvs20081104-15

Somehow, initial whitespace in your mail is corrupted.

> Changes since the last upload:
> 
> [ Petter Reinholdtsen ]
> * Split translation part of Debian changes into 1000-translations.patch.
> [ Debian Janitor ]
> * Trim trailing whitespace.
> * Drop use of autotools-dev debhelper.
> * Update standards version to 4.4.1, no changes needed.
> * Bump debhelper from old 10 to 12.
> * Drop unnecessary dependency on dh-autoconf.
> * Replace XC-Package-Type with Package-Type.
> * Use canonical URL in Vcs-Browser.
> * Rely on pre-initialized dpkg-architecture variables.
> [ 肖盛文 ]
> * d/control:
> Bumped Standards-Version to 4.5.0
> add Build-Depends: debhelper (>= 12)
> delete lintian useless-autoreconf-build-depends: autotools-dev
> +Rules-Requires-Root: no
> * Fixs lintian:
> unused-file-paragraph-in-dep5-copyright
> wildcard-matches-nothing-in-dep5-copyright
> executable-in-usr-lib usr/lib/eject/dmcrypt-get-device
> * delete the outdated watch url
> * add debian/manpages
> * add debian/install
> * add debian/eject-udeb.install
> * d/rules:
> use install files
> use manpages
> deleted no use deb_dir udeb_dir env variables
> add dh_dwz for udeb packages
> * New maintainer (Closes: #92)

Alas, it fails to build for me:

dh_dwz -Xdebian/eject-udeb/usr/bin/eject
dh_dwz -Xdebian/eject-udeb/usr/bin/volname
dwz: debian/eject/usr/bin/eject: .gnu_debugaltlink section already present
dwz: debian/eject/usr/bin/volname: .gnu_debugaltlink section already present
dwz: debian/eject/usr/lib/eject/dmcrypt-get-device: .gnu_debugaltlink section 
already present
dwz: Too few files for multifile optimization
dh_dwz: error: dwz 
-mdebian/eject/usr/lib/debug/.dwz/x86_64-linux-gnu/eject.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/eject.debug -- 
debian/eject/usr/bin/eject debian/eject/usr/bin/volname 
debian/eject/usr/lib/eject/dmcrypt-get-device returned exit code 1
make[1]: *** [debian/rules:49: override_dh_dwz] Error 25


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄

Bug#959178: RFS: eject/2.1.5+deb1+cvs20081104-15 [ITA] -- ejects CDs and operates CD-Changers under Linux

2020-04-30 Thread atzlinux 
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "eject"

* Package name : eject
Version : 2.1.5+deb1+cvs20081104-15
Upstream Author : Jeff Tranter (tran...@pobox.com)
* URL : http://eject.sourceforge.net/
* License : GPL-2+
* Vcs : https://salsa.debian.org/debian/eject
Section : utils

It builds those binary packages:

eject - ejects CDs and operates CD-Changers under Linux
eject-udeb - ejects CDs from d-i menu

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/eject

Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/e/eject/eject_2.1.5+deb1+cvs20081104-15.dsc

Changes since the last upload:

[ Petter Reinholdtsen ]
* Split translation part of Debian changes into 1000-translations.patch.
[ Debian Janitor ]
* Trim trailing whitespace.
* Drop use of autotools-dev debhelper.
* Update standards version to 4.4.1, no changes needed.
* Bump debhelper from old 10 to 12.
* Drop unnecessary dependency on dh-autoconf.
* Replace XC-Package-Type with Package-Type.
* Use canonical URL in Vcs-Browser.
* Rely on pre-initialized dpkg-architecture variables.
[ 肖盛文 ]
* d/control:
Bumped Standards-Version to 4.5.0
add Build-Depends: debhelper (>= 12)
delete lintian useless-autoreconf-build-depends: autotools-dev
+Rules-Requires-Root: no
* Fixs lintian:
unused-file-paragraph-in-dep5-copyright
wildcard-matches-nothing-in-dep5-copyright
executable-in-usr-lib usr/lib/eject/dmcrypt-get-device
* delete the outdated watch url
* add debian/manpages
* add debian/install
* add debian/eject-udeb.install
* d/rules:
use install files
use manpages
deleted no use deb_dir udeb_dir env variables
add dh_dwz for udeb packages
* New maintainer (Closes: #92)

Regards,

-- 
肖盛文 Faris Xiao
微信：atzlinux
ＱＱ：909868357
铜豌豆 Linux 
基于 Debian 的 Linux 中文桌面操作系统：https://www.atzlinux.com




signature.asc
Description: OpenPGP digital signature

Bug#959171: RFS: r4d/1.5-1 [ITP] -- Remote For Device-under-test (R4D) Daemon

2020-04-30 Thread Bastian Germann 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "r4d"

 * Package name: r4d
   Version : 1.5-1
   Upstream Author : Benedikt Spranger 
 * URL : https://github.com/ci-rt/r4d
 * License : GPL-3+
 * Vcs : https://salsa.debian.org/python-team/applications/r4d
   Section : net

It builds those binary packages:

  r4d - Remote For Device-under-test (R4D) Daemon

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/r4d

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/contrib/r/r4d/r4d_1.5-1.dsc

Changes since the last upload:

   * Initial release (Closes: #955616)

Regards,
Bastian Germann

Re: Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-30 Thread Andreas Tille 
Hi Matthew,

On Wed, Apr 29, 2020 at 05:51:26PM -0700, Matthew Fernandez wrote:
> > Any more help from debian-mipsel is really appreciated.
> 
> Hm yes, “--disable-libsanitizer” is rather ominous. I guess the mipsel GCC 
> package has been built without ASan support. Surprising that it fails so 
> messily (the front end seems to think -fsanitize=address is an accepted 
> command line option), but libasan does indeed seem not available on mipsel 
> [0].

OK, so it seems this method to track down the issue on mips does not work.

> The other option I suggested was Valgrind, but if you can’t run apt-file you 
> probably can’t install Valgrind either.

Well, I guess apt-get is permitted for sudo but not apt-file.  So I can
probably install valgrind inside the chroot environment.  I've never
worked with valgrind.  What am I supposed to do?

On the other hand:  Is valgrind possibly able to uncover issues also
on any other architecture?

> If anyone spectating has ideas, please chime in.

Definitely.  We obviously could need some help.

Kind regards

  Andreas.

-- 
http://fam-tille.de