Re: Adding runtime dependencies that aren't caught by shlibs:Depends

[Paul Wise]

On Sat, May 28, 2016 at 2:17 AM, Jens Reyer wrote:

> Then (instead of creating a binary linking to the required
> libraries and running dpkg-shlibdeps on this) I replicate things
> from dpkg-shlibdeps(1) to identify the library package names for
> these sonames:

I wonder if the best solution would be to allow dpkg-shlibdeps to
accept a list of SONAMEs instead of getting that from an ELF file.
Then you could do something like this:

dpkg-shlibdeps -pdlopen -dRecommends -alibc.so.6

Until that is available it seems to me that Jakub Wilk's method of
generating an ELF binary with NEEDED entries for the relevant SONAMEs
is much simpler and less error prone than essentially reimplementing
dpkg-shlibdeps. A modification to the upstream build system could
probably auto-generate the ELF binary and once you have the ELF
binary, you can just do this:

override_dh_shlibdeps:
dpkg-shlibdeps -pdlopen -dRecommends -etheelfbinary
dh_shlibdeps

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#825237: RFS: mrpt/1:1.4.0-1 [ITA] [RC]

[Paul Wise]

On Fri, May 27, 2016 at 4:15 PM, Sean Whitton wrote:

> I think you should use a suffix other than -dbg because people expect
> -dbg to be detached debugging symbols.

I would go with either -dbg (slight preference) or -debug.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#821270: Review of git version

[Sean Whitton]

Hello,

On Fri, May 27, 2016 at 12:02:32PM +, nord-stream wrote:
> Updated:
> * Reworded the description.

Great.  It's really clear now.

>
> * There is no override anymore, although this is not yet perfect. The
> package *generates* files using various tools. The Debian policy
> requires the inclusion of source files. Thus this package can't be
> like a typical simple add-on package.

Great work with this!

> * Corrected the changelog.

It needs to close the RFS bug!  E.g.

  * Initial Debian packaging.  (Closes: #XX)
  * Removed support for older Firefox releases (<45.0).

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#821270: Review of git version

[Sean Whitton]

On Sat, May 28, 2016 at 08:38:02AM +0900, Sean Whitton wrote:
> It needs to close the RFS bug!  E.g.

The ITP bug**

-- 
Sean Whitton


signature.asc
Description: PGP signature

Re: [Help] Re: Bug#825461: staden: FTBFS in testing

[Andreas Tille]

Hi Gianfranco,

On Fri, May 27, 2016 at 07:53:45AM +, Gianfranco Costamagna wrote:
> Hi, some quick googling found some possible solutions
> https://www.google.it/search?client=ubuntu=fs=%22Scrt1.o%3A+In+function+`_start%27%3A%22=utf-8=utf-8_rd=cr=5ftHV7_JI8fA8geO-LmABQ
> 
> I remember having that issue on ettercap some years ago, this is how I fixed 
> it [1], but probably it was a little different issue.
> 
> 
> [1] 
> https://github.com/Ettercap/ettercap/commit/cf90ed99361b266e4d0d8a24f61fe5ffa82fc323

Hmmm, both is not really enlightening my poor brain - but thanks for the
pointers any way.
 
> however, it seems to be related to some build flags missing or added (in a 
> library used or in that tool itself)

Its probably some other Build-Depends that changed since staden
packaging itself is rather static.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#825237: RFS: mrpt/1:1.4.0-1 [ITA] [RC]

[Sean Whitton]

Hello,

On Thu, May 26, 2016 at 11:55:07PM +0200, Jose Luis Blanco wrote:
> > Based on your description, it sounds like the -g packages might be
> > useful for someone.  The only question is what you should call the
> > binary package.  Are you saying that those packages already exist in
> > Debian for wxWidgets?  What is the binary package name in that case?
> 
> Here is the only example I know in Debian (may be other packages like this?)
> 
> https://packages.debian.org/wheezy/libwxgtk2.8-dbg
> And the rest of wx*-dbg packages:
> https://packages.debian.org/source/wheezy/wxwidgets2.8

The most recent version of libwxgtk*-dbg in Debian is just detached
debugging symbols i.e. the same as the *-dbgsym.  The "-b extra runtime
checks" package has been dropped: see #655251.

I think you should use a suffix other than -dbg because people expect
-dbg to be detached debugging symbols.  You could write to
debian-de...@lists.debian.org and/or debian-mentors@lists.debian.org to
see if anyone is aware of a precedent; I'm afraid I don't know of one.

> I tried to replicate your error under Debian sid amd64 without luck. I
> tried with and without ccache (I noticed you use it and thought it may
> be the problem).
> 
> So, you want to give it another try after updating everything to "sid"
> it would be great, but I can't offer any fix because it seems to build
> clean in my local env, and in many other automated build farms
> (travis-ci, Ubuntu PPA, etc.)

It was already updated to sid :( Could you confirm that it succeeds for
you on a 32-bit machine, please?  I don't have access to a 64-bit
machine for testing.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Re: [Help] Re: Bug#825461: staden: FTBFS in testing

[Jakub Wilk]

* Jakub Wilk , 2016-05-27, 10:05:

gcc -shared -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  -I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc 
-I/build/staden-2.0.0+b10/./tk_utils -I/usr/include -I"/usr/include/tcl8.6/tk-private/generic" -I"/usr/include/tcl8.6/tk-private/unix" 
-I"/usr/include/tcl8.6/tk-private/generic/ttk" -I"/usr/include/tcl8.6/tcl-private/generic" -I"/usr/include/tcl8.6/tcl-private/unix" -I/build/staden-2.0.0+b10/./seq_utils 
  -I/build/staden-2.0.0+b10  -DSVN_VERSION="" -fPIC   -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  
-I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc -I/build/staden-2.0.0+b10/./tk_utils -I/usr/include -I"/usr/include/tcl8.6/tk-private/generic" 
-I"/usr/include/tcl8.6/tk-private/unix" -I"/usr/include/tcl8.6/tk-private/generic/ttk" -I"/usr/include/tcl8.6/tcl-private/generic" 
-I"/usr/include/tcl8.6/tcl-private/unix" -I/build/staden-2.0.0+b10/./seq_utils   -I/build/staden-2.0.0+b10  -DSVN_VERSION="" -fPIC  -L/build/staden-2.0.0+b10/lib -Wl,-z,relro 
-Wl,--export-dynamic  -Wl,-rpath,/usr/lib/staden -o /build/staden-2.0.0+b10/lib/libtk_utils.so  cli_arg.o tclXkeylist.o tclXutil.o tcl_utils.o tcl_debug.o misc.o init.o text_output.o tkRaster.o 
tkRasterBuiltIn.o sheet.o tkSheet.o tkSheet_common.o trace_print.o postscript.o split.o tkTrace.o tkTraceComp.o tkTraceIO.o tkTraceDisp.o capture.o canvas_box.o ruler_tick.o restriction_enzyme_map.o 
element_canvas.o container.o container_ruler.o tcl_io_lib.o  -L/usr/lib/x86_64-linux-gnu -lstaden-read -fPIE -pie -Wl,-z,relro -Wl,-z,now -lm -lpthread   -lcurl -lz -L/usr/lib/x86_64-linux-gnu 
-ltk8.6 -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -lX11 -lXss -lXext -lXft -lfontconfig -lfreetype -lfontconfig  -lpthread -ldl -lz  -lpthread -lieee -lm  -lmisc  -lpng -lz

This is trying to build a shared library with -pie, which is not going 
to fly. -pie (and -fPIE) is only for executables.


Now, I don't see any mention of pie in debian/rules, or in the old 
build log, so I guess this flag must have come from a (broken) 
library.


If you grep for -pie in config.log you get this:

IO_LIB_LDFLAGS='-L/usr/lib/i386-linux-gnu -lstaden-read -fPIE -pie -Wl,-z,relro 
-Wl,-z,now -lm -lpthread   -lcurl -lz'

which was apparently generated by:

$ io_lib-config --libs
-L/usr/lib/i386-linux-gnu -lstaden-read -fPIE -pie -Wl,-z,relro -Wl,-z,now -lm 
-lpthread   -lcurl -lz

This will have to be fixed in libstaden-read-dev.

--
Jakub Wilk

Re: Bug#825461: [Help] Re: Bug#825461: staden: FTBFS in testing

[Andreas Tille]

On Fri, May 27, 2016 at 10:05:03AM +0200, Jakub Wilk wrote:
> * Andreas Tille , 2016-05-27, 09:27:
> >>/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/Scrt1.o: In 
> >>function `_start':
> >>(.text+0x20): undefined reference to `main'
> >>collect2: error: ld returned 1 exit status
> 
> The command line that causes this is:
> 
> gcc -shared -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  
> -I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc 
> -I/build/staden-2.0.0+b10/./tk_utils -I/usr/include 
> -I"/usr/include/tcl8.6/tk-private/generic" 
> -I"/usr/include/tcl8.6/tk-private/unix" 
> -I"/usr/include/tcl8.6/tk-private/generic/ttk" 
> -I"/usr/include/tcl8.6/tcl-private/generic" 
> -I"/usr/include/tcl8.6/tcl-private/unix" 
> -I/build/staden-2.0.0+b10/./seq_utils   -I/build/staden-2.0.0+b10  
> -DSVN_VERSION="" -fPIC   -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  
> -I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc 
> -I/build/staden-2.0.0+b10/./tk_utils -I/usr/include 
> -I"/usr/include/tcl8.6/tk-private/generic" 
> -I"/usr/include/tcl8.6/tk-private/unix" 
> -I"/usr/include/tcl8.6/tk-private/generic/ttk" 
> -I"/usr/include/tcl8.6/tcl-private/generic" 
> -I"/usr/include/tcl8.6/tcl-private/unix" 
> -I/build/staden-2.0.0+b10/./seq_utils   -I/build/staden-2.0.0+b10  
> -DSVN_VERSION="" -fPIC  -L/build/staden-2.0.0+b10/lib -Wl,-z,relro 
> -Wl,--export-dynamic  -Wl,-rpath,/usr/lib/staden -o 
> /build/staden-2.0.0+b10/lib/libtk_utils.so  cli_arg.o tclXkeylist.o 
> tclXutil.o tcl_utils.o tcl_debug.o misc.o init.o text_output.o tkRaster.o 
> tkRasterBuiltIn.o sheet.o tkSheet.o tkSheet_common.o trace_print.o 
> postscript.o split.o tkTrace.o tkTraceComp.o tkTraceIO.o tkTraceDisp.o 
> capture.o canvas_box.o ruler_tick.o restriction_enzyme_map.o element_canvas.o 
> container.o container_ruler.o tcl_io_lib.o  -L/usr/lib/x86_64-linux-gnu 
> -lstaden-read -fPIE -pie -Wl,-z,relro -Wl,-z,now -lm -lpthread   -lcurl -lz 
> -L/usr/lib/x86_64-linux-gnu -ltk8.6 -L/usr/lib/x86_64-linux-gnu -ltcl8.6 
> -lX11 -lXss -lXext -lXft -lfontconfig -lfreetype -lfontconfig  -lpthread -ldl 
> -lz  -lpthread -lieee -lm  -lmisc  -lpng -lz
> 
> This is trying to build a shared library with -pie, which is not going to
> fly. -pie (and -fPIE) is only for executables.
> 
> Now, I don't see any mention of pie in debian/rules, or in the old build
> log, so I guess this flag must have come from a (broken) library.

Most probably this is due to libstaden-read-dev where I added

   export DEB_BUILD_MAINT_OPTIONS = hardening=+all

I'll revert this change and see what might happen ...

Thanks for the pointer

  Andreas.


-- 
http://fam-tille.de

Bug#825390: RFS: maldetect/1.5-1 [ITP] -- Linux Malware Detection

[Sean Whitton]

Dear Emily,

On Thu, May 26, 2016 at 10:58:41AM -0500, Emily Ratliff wrote:
> I have attempted to make the package reproducibly buildable and have
> fixed some problems that were preventing that. However, there is still
> a problem of time stamps in the file list which I haven't been able to
> solve. Recommendations welcomed.  

As I understand it, not all of the reproducible builds toolchain has yet
been uploaded to Debian Unstable.  If you've solved the more significant
reproducibility issues then your package will probably pass the
reproducible builds team's automated testing if/when it gets uploaded to
Debian.  So you don't need to worry about this.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#821270: Review of git version

[nord-stream]

Updated:
* Reworded the description.
* There is no override anymore, although this is not yet perfect. The
package *generates* files using various tools. The Debian policy
requires the inclusion of source files. Thus this package can't be like
a typical simple add-on package.
* Corrected the changelog.

On 26/05/16 07:57, Sean Whitton wrote:
> Hello,
> 
> Thank you for getting this project onto alioth.[1] Here's my review of
> the version I found there:
> 
> 1. Have you considered reworking the long description as I suggested
>previously?
> 
> 2. Are you sure you aren't willing to rework the organisation of the
>project to avoid the override in d/rules?  I don't think that's a
>reason not to upload the package, but it would be a nice improvement.
> 
> 3. You should have exactly one debian/changelog entry, saying something
>like "Initial release (Closes: #821210)."  You shouldn't have
>changelog entries tracking changes made in response to comments in
>this RFS thread since those were not uploaded to Debian.
> 
> [1] https://anonscm.debian.org/git/pkg-mozext/iceweasel-branding.git
> 




signature.asc
Description: OpenPGP digital signature

Re: add missing pristine-tar

[Nico Schlömer]

Thanks, this did the trick.

On Fri, May 20, 2016 at 1:43 PM Mattia Rizzolo  wrote:

> On Fri, May 20, 2016 at 11:10:43AM +, Nico Schlömer wrote:
> > Thanks for the hint.
> > Unfortunately, it's not working dpt picks up an older version that
> already
> > is in pristine-tar and adds another commit for it (bug?), but leaves out
> > the version for which there is no pristine-tar.
> >
> > Any other suggestions?
>
> If you already have a pristin-tar branch, just call
> pristine-tar commit /path/to/tarball
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
>

Bug#825531: RFS: libcork/0.15.0+ds-1 [ITP]

[Roger Shimizu]

package: sponsorship-requests
severity: wishlist
X-Debbugs-Cc: rogershim...@gmail.com

Dear mentors,

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

 * Package name: libcork
   Version : 0.15.0+ds-1
   Upstream Author : Douglas Creager 
 * URL : http://libcork.readthedocs.io
 * License : BSD-3-clause
   Section : libs

It builds those binary packages:

 libcork-dev - simple, easily embeddable, cross-platform C library (development
 libcork15  - simple, easily embeddable, cross-platform C library

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libc/libcork/libcork_0.15.0+ds-1.dsc

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

Bug#825532: RFS: shadowsocks-libev/2.4.6+20160526+ds-1 [ITP]

[Roger Shimizu]

Control: block -1 by 825531

Bug#825532: RFS: shadowsocks-libev/2.4.6+20160526+ds-1 [ITP]

[Roger Shimizu]

package: sponsorship-requests
severity: wishlist
X-Debbugs-Cc: rogershim...@gmail.com, max.c...@gmail.com, 073p...@gmail.com

Dear mentors,

I am looking for a sponsor for my package "shadowsocks-libev"

 * Package name: shadowsocks-libev
   Version : 2.4.6+20160526+ds-1
   Upstream Author : Max Lv 
 * URL : http://www.shadowsocks.org
 * License : GPL-3+
   Section : net

It builds those binary packages:

 libshadowsocks-dev - lightweight and secure socks5 proxy (development files)
 libshadowsocks1 - lightweight and secure socks5 proxy (shared library)
 shadowsocks-libev - lightweight and secure socks5 proxy

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

https://mentors.debian.net/package/shadowsocks-libev

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/shadowsocks-libev/shadowsocks-libev_2.4.6+20160526+ds-1.dsc

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

Re: a few questions on ITP shadowsocks-libev before formal RFS

[Roger Shimizu]

On Thu, May 19, 2016 at 12:32 AM, Gianfranco Costamagna
 wrote:
>
> Hi, alternative proposal
>
>>Now I understand my todo-list, briefly:
>>- package libraries first: libcork/ipset
>>- create debian/watch and ds repack
>>- RFS shadowsocks-libev
>>- apply for collab-maint access
>
> - open ITP bugs for all the libraries (search for wnpp and ITP on google)
>
> - package libcork/ipset/shadowsocks-libev all at the same time
> - RFS for all of the three packages and make them blocked by each other
> e.g. block shadowsocks-libev RFS bug by the other two.
> - show your git skills in the meanwhile, and ask for collab-maint access
>
> (BTW it isn't requested to have the repo in collab-maint by the current 
> policy)

Dear G,

I followed most of your advice, and just uploaded to mentors.

I didn't package ipset because:
- Almost dead upstream. There're a few questions and pull request is
pending on github for years.
- I cannot compile by the steps described in upstream's INSTALL file.
It failed on linking.
- Current embedded library just works, because shadowsocks-libev's
upstream has modified this library to improve compatibility on
multi-platform.

I hope you or other DD can sponsor this two packages, because my usual
sponsor is quite busy.
Thanks for your understanding!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

Bug#825105: RFS: udfclient/0.8.5-1

[Pali Rohár]

On Friday 27 May 2016 13:10:26 Andrew Shadura wrote:
> I'll have a look.

Now it is in sid: https://packages.debian.org/sid/udfclient

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: This is a digitally signed message part.

Bug#825237: RFS: mrpt/1:1.4.0-1 [ITA] [RC]

[Jakub Wilk]

* Sean Whitton , 2016-05-27, 17:15:
I think you should use a suffix other than -dbg because people expect 
-dbg to be detached debugging symbols. You could write to 
debian-de...@lists.debian.org and/or debian-mentors@lists.debian.org to 
see if anyone is aware of a precedent;


Hey, we are already on -mentors. :-)

I don't expect -dbg to be only detached debugging symbols. Actually, 
with the advent of automatic debug packages, symbols-only -dbg packages 
are (hopefully) going to become extinct.


The most prominent precedent is probably pythonX.Y-dbg.

--
Jakub Wilk

Bug#825509: RFS: cdist/4.0.0-2 ITP

[Dmitry Bogatov]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: cdist
  Version : 4.0.0-2
  Upstream Author : Nico Schottelius 
* Url : http://www.nico.schottelius.org/software/cdist/
* Licenses: GPL-3+
  Section : admin

It builds those binary packages:

cdist -- Usable Configuration Management System

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

http://mentors.debian.net/package/cdist

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

http://mentors.debian.net/debian/pool/main/c/cdist/cdist_4.0.0-2.dsc

Alternatively, you can access package debian/ directory via git from URL:

https://anonscm.debian.org/cgit/users/kaction-guest/cdist.git

More information about cdist can be obtained from 
http://www.nico.schottelius.org/software/cdist/

Changes since last upload:

  * patches/ensure-reproducible-build.patch: ensure deterministic file
processing order.  Thanks to Chris Lamb .
(Closes: #825406)

Regards,
  Dmitry Bogatov

Bug#825491: RFS: python-bitstring/3.1.5-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-bitstring"

* Package name: python-bitstring
  Version : 3.1.5-1
  Upstream Author : Scott Griffiths 
* URL : http://scott-griffiths.github.io/bitstring/
* License : MIT
  Section : python

It builds those binary packages:

  python-bitstring - Python module for manipulation of binary data 
(Python 2)
  python-bitstring-doc - Python module for manipulation of binary data 
(documentation)
  python3-bitstring - Python module for manipulation of binary data 
(Python 3)


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


  https://mentors.debian.net/package/python-bitstring

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-bitstring/python-bitstring_3.1.5-1.dsc


Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/python-bitstring/3.1.5-1/buildlog

Changes since the last upload:

  * New upstream release.
  * Refresh patch queue.
  * Update copyright information.
  * d/rules: better formatting.
  * Bump standards version to 3.9.8, no changes required.
  * Add upstream metadata.
  * d/gbp.conf: use DEP-14 repository layout.

Regards,
Ghislain Vaillant

Bug#825105: RFS: udfclient/0.8.5-1

[Andrew Shadura]

On 23 May 2016 18:12, "Pali Rohár"  wrote:
>
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "udfclient"
>
>  * Package name: udfclient
>Version : 0.8.5-1
>Upstream Author : Reinoud Zandijk 
>  * URL : http://www.13thmonkey.org/udfclient/
>  * License : Clarified Artistic License
>Section : otherosfs
>
> It builds those binary packages:
>
>   udfclient  - userland implementation of the UDF filesystem
>
> To access further information about this package, please visit the
following URL:
>
> https://mentors.debian.net/package/udfclient
>
>
> Alternatively, one can download the package with dget using this command:
>
>   dget -x
https://mentors.debian.net/debian/pool/main/u/udfclient/udfclient_0.8.5-1.dsc
>
> More information about hello can be obtained from
http://www.13thmonkey.org/udfclient/.
>
> Changes since the last upload:
>
>   * New upstream release
>   * Remove upstream patch Makefile.patch
>   * Fix formatting of package description

I'll have a look.

-- 
Cheers,
  Andrew

Bug#825490: RFS: nfft/3.3.2~rc1-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: nfft
  Version : 3.3.2~rc1-1
  Upstream Author : Prof. Dr. Daniel Potts 
* URL :http://www-user.tu-chemnitz.de/~potts/nfft/
* License : GPL-2+
  Section : science

It builds those binary packages:

 libnfft3-2 - library for computing non-uniform Fourier transforms
 libnfft3-dbg - debugging symbols for the NFFT library
 libnfft3-dev - development files for the NFFT library
 libnfft3-doc - documentation for the NFFT library
 libnfft3-double2 - library for computing non-uniform Fourier 
transforms (double prec
 libnfft3-long2 - library for computing non-uniform Fourier transforms 
(long-double
 libnfft3-single2 - library for computing non-uniform Fourier 
transforms (single prec


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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/n/nfft/nfft_3.3.2~rc1-1.dsc


Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/nfft/3.3.2~rc1-1/buildlog

Changes since the last upload:

  * New upstream release.
  * Update upstream metadata.

Regards,
Ghislain Vaillant

Bug#814859: RFS: runescape/0.1-1 [ITP] -- Set in a fantasy world of war, landscapes and sinister powers

[Carlos Donizete Froes]

Em 23-05-2016 6:22, Mattia Rizzolo escreveu:

Hi Carlos!

On Tue, Feb 16, 2016 at 07:30:51PM +, James Cowgill wrote:

I have a few comments on this pavkage.


This was Feb 16, more than 3 months ago, but with no replies from you.
Are you still interested in this package?


Hello Mattia,

I apologize to leave long without work in this package, it was more 
because of the other packages that I have and I ended up leaving aside.


I made some changes in this package and is available on mentors to 
analyze.


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

Thank you!

--
Carlos Donizete Froes [a.k.a coringao]
- https://wiki.debian.org/coringao
GPG: 4096R/C325F557
EAD9 DDCB DC86 4561 7612  A34F A9CD 6C31 C325 F557

Bug#825236: marked as done (RFS: openfst/1.5.3-1 -- weighted finite-state transducers library)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 19:23:48 +0200
with message-id <20160527172348.ga8...@jwilk.net>
and subject line Re: Bug#825236: RFS: openfst/1.5.3-1 -- weighted finite-state 
transducers library
has caused the Debian Bug report #825236,
regarding RFS: openfst/1.5.3-1 -- weighted finite-state transducers library
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
825236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: jw...@debian.org


Dear Jakub,

I am looking for a sponsor for my package "openfst".

 * Package name: openfst
   Version : 1.5.3-1
   Upstream Author : Cyril Allauzen , Michael Riley 

 * URL : http://www.openfst.org/
 * License : Apache-2.0
   Section : libs

It builds these binary packages:

libfst-tools - weighted finite-state transducers library (tools)
libfst3 - weighted finite-state transducers library (runtime)
libfst3-plugins-base -  weighted finite-state transducers library (base 
plugins)
libfst-dev - weighted finite-state transducers library (development)

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

 https://anonscm.debian.org/git/collab-maint/openfst.git

Regards,
   Giulio Paci
--- End Message ---
--- Begin Message ---

* Giulio Paci , 2016-05-27, 00:08:

| /home/jwilk/openfst-1.5.3+r2/src/test/algo_test.cc:48:(.text+0x674): 
relocation truncated to fit: R_MIPS_CALL16 against `time@@GLIBC_2.0'
| /home/jwilk/openfst-1.5.3+r2/src/test/algo_test.cc:49:(.text+0x6a4): 
additional relocation overflows omitted from the output
| collect2: error: ld returned 1 exit status
| Makefile:641: recipe for target 'algo_test_log' failed
Appending "-mxgot" to CXXFLAGS fixed this error.
Inconveniently, "-mxgot" is not a valid option on hurd, so you'll have 
to add another ifneq.
I added two separate ifneq, one for hurd-i386 and one for mips/mipsel 
architectures. By reading the option description and the above error 
messages, I guess that the flag is needed only for the test suite,


That's right.

6aa966e24041 uploaded.

Please consider adding upstream metadata for the next release:
https://wiki.debian.org/UpstreamMetadata

--
Jakub Wilk--- End Message ---

Bug#824967: RFS: budgie-desktop/10.2.5-1 [ITP]

[foss.freedom]

Many thanks Paul for your review - even though you do not wish to sponsor
this, your review has been very valuable.

I've addressed your comments as discussed below.

Looking on the mentors / mypackages webpage it says that the watch file
I've included does not work.  This is very strange because I ran a uscan
and it correctly downloaded the upstream release file:

uscan --force-download --verbose
uscan info: uscan (version 2.16.2ubuntu3) See uscan(1) for help
uscan info: Scan watch files in .
uscan info: Check debian/watch and debian/changelog in .
uscan info: package="budgie-desktop" version="10.2.5-1" (as seen in
debian/changelog)
uscan info: package="budgie-desktop" version="10.2.5" (no epoch/revision)
uscan info: ./debian/changelog sets package="budgie-desktop"
version="10.2.5"
uscan info: Process ./debian/watch (package=budgie-desktop version=10.2.5)
uscan info: Last orig.tar.* tarball version (from debian/changelog): 10.2.5
uscan info: Last orig.tar.* tarball version (dversionmangled): 10.2.5
uscan info: Requesting URL:
   https://github.com/solus-project/budgie-desktop/releases
uscan info: Matching pattern:
   (?:(?:https://github.com
)?\/solus\-project\/budgie\-desktop\/releases)?.*/?(\d{2}\.\d.\d)\.tar\.xz
uscan info: Found the following matching hrefs on the web page (newest
first):

/solus-project/budgie-desktop/releases/download/v10.2.5/budgie-desktop-10.2.5.tar.xz
(10.2.5) index=10.2.5-4

/solus-project/budgie-desktop/releases/download/v10.2.4/budgie-desktop-10.2.4.tar.xz
(10.2.4) index=10.2.4-4

/solus-project/budgie-desktop/releases/download/v10.2.3/budgie-desktop-10.2.3.tar.xz
(10.2.3) index=10.2.3-4

/solus-project/budgie-desktop/releases/download/v10.2.2/budgie-desktop-10.2.2.tar.xz
(10.2.2) index=10.2.2-4

/solus-project/budgie-desktop/releases/download/v10.2.1/budgie-desktop-10.2.1.tar.xz
(10.2.1) index=10.2.1-4
uscan info: Matching target for downloadurlmangle:
https://github.com/solus-project/budgie-desktop/releases/download/v10.2.5/budgie-desktop-10.2.5.tar.xz
uscan info: Upstream URL (downloadurlmangled):

https://github.com/solus-project/budgie-desktop/releases/download/v10.2.5/budgie-desktop-10.2.5.tar.xz
uscan info: Newest upstream tarball version selected for download
(uversionmangled): 10.2.5
uscan info: Download filename (filenamemangled):
budgie-desktop-10.2.5.tar.xz
uscan: Newest version of budgie-desktop on remote site is 10.2.5, local
version is 10.2.5
uscan info:=> Package is up to date for from

https://github.com/solus-project/budgie-desktop/releases/download/v10.2.5/budgie-desktop-10.2.5.tar.xz
uscan info:=> Forcing download as requested
uscan info: Downloading upstream package: budgie-desktop-10.2.5.tar.xz
uscan info: Requesting URL:

https://github.com/solus-project/budgie-desktop/releases/download/v10.2.5/budgie-desktop-10.2.5.tar.xz
uscan info: Successfully downloaded package: budgie-desktop-10.2.5.tar.xz
uscan info: Start checking for common possible upstream OpenPGP signature
files
uscan info: End checking for common possible upstream OpenPGP signature
files
uscan info: Missing OpenPGP signature.
uscan info: New orig.tar.* tarball version (oversionmangled): 10.2.5
uscan info: Executing internal command:
   mk-origtargz --package budgie-desktop --version 10.2.5 --compression
gzip --directory .. --copyright-file debian/copyright
../budgie-desktop-10.2.5.tar.xz
uscan info: New orig.tar.* tarball version (after mk-origtargz): 10.2.5
uscan info: Successfully symlinked ../budgie-desktop-10.2.5.tar.xz to
../budgie-desktop_10.2.5.orig.tar.xz.
uscan info: Scan finished


The remaining review comments and how I addressed them now follows:

> Does upstream have an opinion on having older versions of Budgie in
> Debian stable, which gets supported for 5 years now that we have LTS.

I've asked this question upstream:
https://github.com/solus-project/budgie-desktop/issues/446

In summary - users are requested to upgrade.  Moving forward, the
maintainer intends to branch the project at the next major release and will
backport stuff where necessary (e.g. critical issues).  This will be very
useful for Debian to identify issues to include in updates.

> I would suggest using diffoscope to compare the broken build with the
> working one, you might discover the reason for this brokenness.

This did not reveal any specific build issues.


> The package fails to build because gtk+3.0 3.20.5-1 is not yet built in
Debian:

I presume this is a transition issue for Sid as it moves to GTK+3.20


> There are many hardcoded library dependencies, they shouldn't be
> needed as ${shlibs:Depends} will take care of them, unless these
> libraries are loaded using dlopen instead of linking. If they are
> loaded with dlopen, a ${dlopen:Depends} substvar and a script to
> generate it would be better than hardcoding them.

The dependencies are been cleaned up.  No libraries are included.  The
minimal necessary dependencies 

Re: Adding runtime dependencies that aren't caught by shlibs:Depends

[Jens Reyer]

On 05/19/2016 05:53 PM, Jakub Wilk wrote:
> * Jens Reyer , 2016-05-19, 16:57:
>> First off, I'm not sure about every single dependency if it is needed
>> at all.
> 
> Quick grep over the *.dll.so indeed shows that they use a bunch of
> libraries you mentioned:
[...]
> I guess a better method of obtaining the list of used shared libraries
> is to grep for "SONAME_" in include/config.h (after it was created by
> the configure script).
> 
> Once you have the list of needed shlibs, the simplest way to compute
> package dependency is to create an ELF that depends on all of them, and
> then use dpkg-shlibdeps against it.
> 
> You can steal the idea of how to create such ELF here:
> https://bitbucket.org/jwilk/python-dctypes/src/default/dctypes2elf

Thanks a lot Jakub and Gianfranco!

I think I have it working now in wine to automatically generate a
list of runtime dependencies. I based it on Jakub's suggestions,
however I didn't go for creating a "dependency binary".

For one I did get results this way, but unfortunately I neither
really know python nor perl which is usually used in wine
packaging, in order to cleanly implement it there. Generally more
relevant however, since I probably found a Makefile/shell
solution, I'd like to keep it as simple as possible.

I chose to (as suggested) first check for all sonames in
include/config.h after configure. This gives similar results as
grep'ing  for *.so (and a lot more than for *.dll.so). The
differences are only for shlibs, which are not relevant here.

Then (instead of creating a binary linking to the required
libraries and running dpkg-shlibdeps on this) I replicate things
from dpkg-shlibdeps(1) to identify the library package names for
these sonames:

- first find the library file on the system (looking in some
  hardcoded directories),

- then use "dpkg -S library-file" to lookup the package providing
  the library.

I put these library names in a custom substvar
${dlopen:Recommends}, and pass it on with dh_gencontrol. Done.


I'd like to hear your opinion on this, for now my own thoughts:

- As long as there are no specific symbols to work with, we don't
  know if we'd need a version constraint (I think this was
  Gianfranco's point). But since I'm only looking for the sonames,
  we can't profit from using a sophisticated tool as
  dpkg-shlibdeps.
  Anyway, this is superior to not having these dependencies at all,
  or to hardcoding them (we still can manually add e.g. a version
  constraint if necessary).

- I look for the soname files in a hardcoded list of dirs (/lib,
  /usr/lib, /lib/DEB_HOST_MULTIARCH and
  /usr/lib/DEB_HOST_MULTIARCH).
  dpkg-shlibdeps would be more flexible here, but we just need it
  to work for us. Are there any problems with that, e.g. for other
  ports (kfreebsd, hurd) or anything else?


For reference, this is my implementation:

d/rules:
# additional dlopen runtime dependencies
sonames=$(shell grep  "^\#define SONAME_" include/config.h | cut -d\" -f2)
paths=/usr /usr/lib /lib/$(shell dpkg-architecture -qDEB_HOST_MULTIARCH) 
/usr/lib/$(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
dlopenRecommends=$(shell \
for soname in $(sonames); do \
for path in $(paths); do \
file=$$(echo $$path/$$soname | sed "s|//|/|g"); \
[ -f $$file ] && dpkg -S $$file | cut -d: -f1 | sed "s/\\(.*\\) 
*/\\1,/" && break || true; \
done; \
done)

override_dh_gencontrol:
dh_gencontrol -- \
-Vdlopen:Recommends="$(dlopenRecommends)"

d/control:
libwine Recommends: ${dlopen:Recommends},


Thanks again for the valuable input!
Greets
jre

Bug#825559: RFS: node-regenerate/1.3.0-1

[Julien Puydt]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "node-regenerate"

 * Package name: node-regenerate
   Version : 1.3.0-1
   Upstream Author : Mathias Bynens
 * URL : https://github.com/mathiasbynens/regenerate
 * License : Expat
   Section : web

  It builds those binary packages:

libjs-regenerate - Unicode-aware regular expression generator 
(JavaScript library)
 node-regenerate - Unicode-aware regular expression generator (Node.js 
module)


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


  https://mentors.debian.net/package/node-regenerate


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

dget -x 
https://mentors.debian.net/debian/pool/main/n/node-regenerate/node-regenerate_1.3.0-1.dsc


 It is packaged within the debian-js team:
Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-regenerate.git
Vcs-Browser: 
https://anonscm.debian.org/git/pkg-javascript/node-regenerate.git


  Changes since the last upload:
  * New upstream release.
  * Pushed standards-version up.
  * Fixed Vcs-* uris.
  * Updated year of copyright.
  * Made the node- package link to the libjs- package.
  * Added lintian-override for ECMAScript specification test.

Thanks,

Snark on #debian-js

Bug#825559: marked as done (RFS: node-regenerate/1.3.0-1)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 20:27:10 + (UTC)
with message-id <1210816248.589190.1464380830973.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#825559: RFS: node-regenerate/1.3.0-1
has caused the Debian Bug report #825559,
regarding RFS: node-regenerate/1.3.0-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
825559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "node-regenerate"

 * Package name: node-regenerate
   Version : 1.3.0-1
   Upstream Author : Mathias Bynens
 * URL : https://github.com/mathiasbynens/regenerate
 * License : Expat
   Section : web

  It builds those binary packages:

libjs-regenerate - Unicode-aware regular expression generator 
(JavaScript library)
 node-regenerate - Unicode-aware regular expression generator (Node.js 
module)


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


  https://mentors.debian.net/package/node-regenerate


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

dget -x 
https://mentors.debian.net/debian/pool/main/n/node-regenerate/node-regenerate_1.3.0-1.dsc


 It is packaged within the debian-js team:
Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-regenerate.git
Vcs-Browser: 
https://anonscm.debian.org/git/pkg-javascript/node-regenerate.git


  Changes since the last upload:
  * New upstream release.
  * Pushed standards-version up.
  * Fixed Vcs-* uris.
  * Updated year of copyright.
  * Made the node- package link to the libjs- package.
  * Added lintian-override for ECMAScript specification test.

Thanks,

Snark on #debian-js
--- End Message ---
--- Begin Message ---
hi, done!

g.





Il Venerdì 27 Maggio 2016 21:39, Julien Puydt  ha 
scritto:
Package: sponsorship-requests
Severity: normal

   Dear mentors,

   I am looking for a sponsor for my package "node-regenerate"

  * Package name: node-regenerate
Version : 1.3.0-1
Upstream Author : Mathias Bynens
  * URL : https://github.com/mathiasbynens/regenerate
  * License : Expat
Section : web

   It builds those binary packages:

 libjs-regenerate - Unicode-aware regular expression generator 
(JavaScript library)
  node-regenerate - Unicode-aware regular expression generator (Node.js 
module)

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

  https://mentors.debian.net/package/node-regenerate


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

 dget -x 
https://mentors.debian.net/debian/pool/main/n/node-regenerate/node-regenerate_1.3.0-1.dsc

  It is packaged within the debian-js team:
Vcs-Git: https://anonscm.debian.org/git/pkg-javascript/node-regenerate.git
Vcs-Browser: 
https://anonscm.debian.org/git/pkg-javascript/node-regenerate.git

   Changes since the last upload:
   * New upstream release.
   * Pushed standards-version up.
   * Fixed Vcs-* uris.
   * Updated year of copyright.
   * Made the node- package link to the libjs- package.
   * Added lintian-override for ECMAScript specification test.

Thanks,

Snark on #debian-js--- End Message ---

Bug#825509: marked as done (RFS: cdist/4.0.0-2 ITP)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 20:33:25 + (UTC)
with message-id <529850055.930068.1464381205944.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#825509: RFS: cdist/4.0.0-2 ITP
has caused the Debian Bug report #825509,
regarding RFS: cdist/4.0.0-2 ITP
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
825509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: cdist
  Version : 4.0.0-2
  Upstream Author : Nico Schottelius 
* Url : http://www.nico.schottelius.org/software/cdist/
* Licenses: GPL-3+
  Section : admin

It builds those binary packages:

cdist -- Usable Configuration Management System

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

http://mentors.debian.net/package/cdist

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

http://mentors.debian.net/debian/pool/main/c/cdist/cdist_4.0.0-2.dsc

Alternatively, you can access package debian/ directory via git from URL:

https://anonscm.debian.org/cgit/users/kaction-guest/cdist.git

More information about cdist can be obtained from 
http://www.nico.schottelius.org/software/cdist/

Changes since last upload:

  * patches/ensure-reproducible-build.patch: ensure deterministic file
processing order.  Thanks to Chris Lamb .
(Closes: #825406)

Regards,
  Dmitry Bogatov
--- End Message ---
--- Begin Message ---
Hi, uploaded on deferred/4

the rationale is:
what you have on git is different from what is in unstable.

I had to change UNRELEASED to unstable
and to change the timestamp of the -1 version
https://anonscm.debian.org/cgit/users/kaction-guest/cdist.git/commit/?id=3527e379aad6e7d2621652b308676e000e7f866b

you seem to have changed it, but the package has been sponsored in unstable 
without that change



attached the debian directory for the uploaded package.

(BTW having it on deferred/4 has two meanings: let you the time to answer, and 
give time to the current package to migrate
in testing. I don't think a reproducible build fix is worth a delay for the 
testing transition, specially if the package is 3/5 days old :) )

G.






Il Venerdì 27 Maggio 2016 12:42, Dmitry Bogatov  ha scritto:

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: cdist
  Version : 4.0.0-2
  Upstream Author : Nico Schottelius 
* Url : http://www.nico.schottelius.org/software/cdist/
* Licenses: GPL-3+
  Section : admin

It builds those binary packages:

cdist -- Usable Configuration Management System

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

http://mentors.debian.net/package/cdist

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

http://mentors.debian.net/debian/pool/main/c/cdist/cdist_4.0.0-2.dsc

Alternatively, you can access package debian/ directory via git from URL:

https://anonscm.debian.org/cgit/users/kaction-guest/cdist.git

More information about cdist can be obtained from 
http://www.nico.schottelius.org/software/cdist/

Changes since last upload:

  * patches/ensure-reproducible-build.patch: ensure deterministic file
processing order.  Thanks to Chris Lamb .
(Closes: #825406)

Regards,
  Dmitry Bogatov

cdist_4.0.0-2.debian.tar.xz
Description: application/xz
--- End Message ---

Bug#825491: marked as done (RFS: python-bitstring/3.1.5-1)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 20:23:26 + (UTC)
with message-id <891159034.939441.1464380606966.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#825491: RFS: python-bitstring/3.1.5-1
has caused the Debian Bug report #825491,
regarding RFS: python-bitstring/3.1.5-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
825491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-bitstring"

* Package name: python-bitstring
  Version : 3.1.5-1
  Upstream Author : Scott Griffiths 
* URL : http://scott-griffiths.github.io/bitstring/
* License : MIT
  Section : python

It builds those binary packages:

  python-bitstring - Python module for manipulation of binary data 
(Python 2)
  python-bitstring-doc - Python module for manipulation of binary data 
(documentation)
  python3-bitstring - Python module for manipulation of binary data 
(Python 3)


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


  https://mentors.debian.net/package/python-bitstring

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-bitstring/python-bitstring_3.1.5-1.dsc


Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/python-bitstring/3.1.5-1/buildlog

Changes since the last upload:

  * New upstream release.
  * Refresh patch queue.
  * Update copyright information.
  * d/rules: better formatting.
  * Bump standards version to 3.9.8, no changes required.
  * Add upstream metadata.
  * d/gbp.conf: use DEP-14 repository layout.

Regards,
Ghislain Vaillant
--- End Message ---
--- Begin Message ---
Hi, done!

G.





Il Venerdì 27 Maggio 2016 10:57, Ghislain Vaillant  ha 
scritto:
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-bitstring"

* Package name: python-bitstring
   Version : 3.1.5-1
   Upstream Author : Scott Griffiths 
* URL : http://scott-griffiths.github.io/bitstring/
* License : MIT
   Section : python

It builds those binary packages:

   python-bitstring - Python module for manipulation of binary data 
(Python 2)
   python-bitstring-doc - Python module for manipulation of binary data 
(documentation)
   python3-bitstring - Python module for manipulation of binary data 
(Python 3)

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

  https://mentors.debian.net/package/python-bitstring

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

   dget -x 
https://mentors.debian.net/debian/pool/main/p/python-bitstring/python-bitstring_3.1.5-1.dsc

Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/python-bitstring/3.1.5-1/buildlog

Changes since the last upload:

   * New upstream release.
   * Refresh patch queue.
   * Update copyright information.
   * d/rules: better formatting.
   * Bump standards version to 3.9.8, no changes required.
   * Add upstream metadata.
   * d/gbp.conf: use DEP-14 repository layout.

Regards,
Ghislain Vaillant--- End Message ---

Bug#825490: marked as done (RFS: nfft/3.3.2~rc1-1)

[Debian Bug Tracking System]

Your message dated Fri, 27 May 2016 20:23:08 + (UTC)
with message-id <846161236.912536.1464380588038.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#825490: RFS: nfft/3.3.2~rc1-1
has caused the Debian Bug report #825490,
regarding RFS: nfft/3.3.2~rc1-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
825490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: nfft
  Version : 3.3.2~rc1-1
  Upstream Author : Prof. Dr. Daniel Potts 
* URL :http://www-user.tu-chemnitz.de/~potts/nfft/
* License : GPL-2+
  Section : science

It builds those binary packages:

 libnfft3-2 - library for computing non-uniform Fourier transforms
 libnfft3-dbg - debugging symbols for the NFFT library
 libnfft3-dev - development files for the NFFT library
 libnfft3-doc - documentation for the NFFT library
 libnfft3-double2 - library for computing non-uniform Fourier 
transforms (double prec
 libnfft3-long2 - library for computing non-uniform Fourier transforms 
(long-double
 libnfft3-single2 - library for computing non-uniform Fourier 
transforms (single prec


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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/n/nfft/nfft_3.3.2~rc1-1.dsc


Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/nfft/3.3.2~rc1-1/buildlog

Changes since the last upload:

  * New upstream release.
  * Update upstream metadata.

Regards,
Ghislain Vaillant
--- End Message ---
--- Begin Message ---
done!

g.





Il Venerdì 27 Maggio 2016 10:54, Ghislain Vaillant  ha 
scritto:
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: nfft
   Version : 3.3.2~rc1-1
   Upstream Author : Prof. Dr. Daniel Potts 
* URL :http://www-user.tu-chemnitz.de/~potts/nfft/
* License : GPL-2+
   Section : science

It builds those binary packages:

  libnfft3-2 - library for computing non-uniform Fourier transforms
  libnfft3-dbg - debugging symbols for the NFFT library
  libnfft3-dev - development files for the NFFT library
  libnfft3-doc - documentation for the NFFT library
  libnfft3-double2 - library for computing non-uniform Fourier 
transforms (double prec
  libnfft3-long2 - library for computing non-uniform Fourier transforms 
(long-double
  libnfft3-single2 - library for computing non-uniform Fourier 
transforms (single prec

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

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

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

   dget -x 
https://mentors.debian.net/debian/pool/main/n/nfft/nfft_3.3.2~rc1-1.dsc

Successful build on debomatic:


http://debomatic-amd64.debian.net/distribution#unstable/nfft/3.3.2~rc1-1/buildlog

Changes since the last upload:

   * New upstream release.
   * Update upstream metadata.

Regards,
Ghislain Vaillant--- End Message ---

Re: Trying to disable error=format-security for clapack

[Andreas Tille]

Hi Gert,

On Thu, May 26, 2016 at 04:27:25PM +0200, Gert Wollny wrote:
> ...
> Removing the file INCLUDE/f2c.h solves the problem, because then the
> ...

This tip saved my evening yesterday - thanks a lot.  The only remaining
issue is now 


   E: libclapack3: binary-or-shlib-defines-rpath 
usr/lib/x86_64-linux-gnu/libclapack.so.3.2.1 
/build/clapack-3.2.1+dfsg/obj-x86_64-linux-gnu/BLAS/SRC


Is there any trick how I could tweak cmake files to prevent the
inclusion of rpath or is the only chance to solve this to use

chrpath --delete

?

Kind regards

Andreas.

-- 
http://fam-tille.de

Re: Trying to disable error=format-security for clapack

[Gianfranco Costamagna]

Hi,



>   E: libclapack3: binary-or-shlib-defines-rpath 
> usr/lib/x86_64-linux-gnu/libclapack.so.3.2.1 
> /build/clapack-3.2.1+dfsg/obj-x86_64-linux-gnu/BLAS/SRC
>Is there any trick how I could tweak cmake files to prevent the
>inclusion of rpath or is the only chance to solve this to use
>
>chrpath --delete



It shoulnd't be needed.
set(CMAKE_INSTALL_RPATH_USE_LINK_PATH FALSE) might help, but by default 
somewhen in dh_install rpath should be removed
(debhelper?cmake?)

e.g. in ettercap I don't set it, and the cmake make install works beautifully.
Since we have an ettercap-text-only that we build and install in a custom way, 
we have to strip rpath on that file
https://buildd.debian.org/status/fetch.php?pkg=ettercap=amd64=1%3A0.8.2-2%2Bb1=1446812919


just search for something like:
INSTALL_RPATH ${INSTALL_LIBDIR})


this should be how in cmake they set the RPATH.

G.

Re: [Help] Re: Bug#825461: staden: FTBFS in testing

[Gianfranco Costamagna]

Hi, some quick googling found some possible solutions
https://www.google.it/search?client=ubuntu=fs=%22Scrt1.o%3A+In+function+`_start%27%3A%22=utf-8=utf-8_rd=cr=5ftHV7_JI8fA8geO-LmABQ

I remember having that issue on ettercap some years ago, this is how I fixed it 
[1], but probably it was a little different issue.


[1] 
https://github.com/Ettercap/ettercap/commit/cf90ed99361b266e4d0d8a24f61fe5ffa82fc323


however, it seems to be related to some build flags missing or added (in a 
library used or in that tool itself)


HTH

Gianfranco
Il Venerdì 27 Maggio 2016 9:27, Andreas Tille  ha scritto:



Hi,

On Fri, May 27, 2016 at 02:29:28AM +0200, Santiago Vila wrote:
> --
> capture.o: In function `tcl_capture':
> /<>/staden-2.0.0+b10/tk_utils/capture.c:31: warning: the use of 
> `tmpnam' is dangerous, better use `mkstemp'

I've fixed this in Git, but this does not help. :-(

> /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/Scrt1.o: In 
> function `_start':
> (.text+0x20): undefined reference to `main'
> collect2: error: ld returned 1 exit status

Any help would be welcome

 Andreas.


-- 
http://fam-tille.de

Re: [Help] Re: Bug#825461: staden: FTBFS in testing

[Jakub Wilk]

* Andreas Tille , 2016-05-27, 09:27:

/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/Scrt1.o: In function 
`_start':
(.text+0x20): undefined reference to `main'
collect2: error: ld returned 1 exit status


The command line that causes this is:

gcc -shared -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  -I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc 
-I/build/staden-2.0.0+b10/./tk_utils -I/usr/include -I"/usr/include/tcl8.6/tk-private/generic" -I"/usr/include/tcl8.6/tk-private/unix" 
-I"/usr/include/tcl8.6/tk-private/generic/ttk" -I"/usr/include/tcl8.6/tcl-private/generic" -I"/usr/include/tcl8.6/tcl-private/unix" -I/build/staden-2.0.0+b10/./seq_utils 
  -I/build/staden-2.0.0+b10  -DSVN_VERSION="" -fPIC   -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DUSE_NON_CONST  
-I/build/staden-2.0.0+b10/./tk_utils -I/build/staden-2.0.0+b10/./Misc -I/build/staden-2.0.0+b10/./tk_utils -I/usr/include -I"/usr/include/tcl8.6/tk-private/generic" 
-I"/usr/include/tcl8.6/tk-private/unix" -I"/usr/include/tcl8.6/tk-private/generic/ttk" -I"/usr/include/tcl8.6/tcl-private/generic" 
-I"/usr/include/tcl8.6/tcl-private/unix" -I/build/staden-2.0.0+b10/./seq_utils   -I/build/staden-2.0.0+b10  -DSVN_VERSION="" -fPIC  -L/build/staden-2.0.0+b10/lib -Wl,-z,relro 
-Wl,--export-dynamic  -Wl,-rpath,/usr/lib/staden -o /build/staden-2.0.0+b10/lib/libtk_utils.so  cli_arg.o tclXkeylist.o tclXutil.o tcl_utils.o tcl_debug.o misc.o init.o text_output.o tkRaster.o 
tkRasterBuiltIn.o sheet.o tkSheet.o tkSheet_common.o trace_print.o postscript.o split.o tkTrace.o tkTraceComp.o tkTraceIO.o tkTraceDisp.o capture.o canvas_box.o ruler_tick.o restriction_enzyme_map.o 
element_canvas.o container.o container_ruler.o tcl_io_lib.o  -L/usr/lib/x86_64-linux-gnu -lstaden-read -fPIE -pie -Wl,-z,relro -Wl,-z,now -lm -lpthread   -lcurl -lz -L/usr/lib/x86_64-linux-gnu 
-ltk8.6 -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -lX11 -lXss -lXext -lXft -lfontconfig -lfreetype -lfontconfig  -lpthread -ldl -lz  -lpthread -lieee -lm  -lmisc  -lpng -lz

This is trying to build a shared library with -pie, which is not going 
to fly. -pie (and -fPIE) is only for executables.


Now, I don't see any mention of pie in debian/rules, or in the old build 
log, so I guess this flag must have come from a (broken) library.


--
Jakub Wilk

Bug#825302: RFS: usbguard/0.4-2 [ITP]

[Rebecca N. Palmer]

src/ThirdParty and src/Library/RuleParser/quex contain embedded code
copies. Please ask upstream to remove them from their VCS and tarballs
and depend on them instead. You can then package them separately.
Alternatively, package them separately and remove all of them at
`debian/rules build` time before dh_auto_configure and at
`debian/rules clean` time (or just have uscan auto-repack the upstream
tarball using Files-Excluded).


They're there to allow building usbguard on systems without those 
libraries packaged: 
https://dkopecek.github.io/usbguard/blog/2015/USBGuard-on-Ubuntu-14-04
Upstream already agree they shouldn't be used if system packages are 
available: see 
https://apps.fedoraproject.org/packages/usbguard/sources/spec lines 55-65



This line in the README.md indicates a possible flaw in usbguard; can
it block new USB keyboards if there is a built-in keyboard or one
keyboard plugged in via a non-USB method such as PS/2?


This is just an example; you can block USB keyboards entirely (but check 
lsusb first, as some physically built-in devices are internally USB), 
but probably can't automatically check whether there's a non-USB 
keyboard.  You can also allow only those devices currently connected 
(usbguard generate-policy).

[Help] Re: Bug#825461: staden: FTBFS in testing

[Andreas Tille]

Hi,

On Fri, May 27, 2016 at 02:29:28AM +0200, Santiago Vila wrote:
> --
> capture.o: In function `tcl_capture':
> /<>/staden-2.0.0+b10/tk_utils/capture.c:31: warning: the use of 
> `tmpnam' is dangerous, better use `mkstemp'

I've fixed this in Git, but this does not help. :-(

> /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/Scrt1.o: In 
> function `_start':
> (.text+0x20): undefined reference to `main'
> collect2: error: ld returned 1 exit status

Any help would be welcome

 Andreas.


-- 
http://fam-tille.de

Bug#825509: RFS: cdist/4.0.0-2 ITP

[Dmitry Bogatov]

> the rationale is:
> what you have on git is different from what is in unstable.
>
> I had to change UNRELEASED to unstable
> and to change the timestamp of the -1 version
> https://anonscm.debian.org/cgit/users/kaction-guest/cdist.git/commit/?id=3D=
> 3527e379aad6e7d2621652b308676e000e7f866b
>
> you seem to have changed it, but the package has been sponsored in unstable=
>  without that change
>
> (BTW having it on deferred/4 has two meanings: let you the time to answer, =
> and give time to the current package to migrate
> in testing. I don't think a reproducible build fix is worth a delay for the=
>  testing transition, specially if the package is 3/5 days old :) )

Sorry, my bad. Now I understand, that I uploaded on mentors 4.0.0-2
again UNRELEASED. Please, reject current and grab new from mentors.

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Keep-In-CC: yes
X-Web-Site: sinsekvu.github.io