Re: salsa access as debian maintainer

2018-01-15 Thread Nico Schlömer
Alright, thanks for the reply! Cheers, Nico On Mon, Jan 15, 2018 at 4:59 PM Alexander Wirt wrote: > On Mon, 15 Jan 2018, Nico Schlömer wrote: > > > Thanks for the quick reply. > > > > > unless DM information is available in udldap. > > > > I'm not

Re: salsa access as debian maintainer

2018-01-15 Thread Nico Schlömer
Thanks for the quick reply. > unless DM information is available in udldap. I'm not familar with udldap. Is this something where I or someone else should take action? Cheers, Nico On Mon, Jan 15, 2018 at 4:51 PM Alexander Wirt wrote: > On Mon, 15 Jan 2018, Nico Schlömer wr

salsa access as debian maintainer

2018-01-15 Thread Nico Schlömer
Hi everyone, I'm a Debian maintainer and the projects I'm working with have recently been moved from alioth to salsa. It seems that right now only Debian _developers_ have a login to salsa. Is this something that will change in the future or should I make a new account (and live with -guest :(). W

Arch-dependent Python libs

2017-12-01 Thread Nico Schlömer
I'm looking at VTK, a large C++ code that also provides Python bindings. I'm wondering now where to install the Python files. From the Debian Python guidelines [1] : > Public Python 3 modules must be installed in the system Python 3 modules directory, /usr/lib/python3/dist-packages. > Architecture

dh_gencontrol debug symbol wrapper: no debian/-dbgsym, skipping package

2016-02-29 Thread Nico Schlömer
Hi everyone, I'd like to play around with the (new) auto dbgsym packages, and for starters build Mixxx [1] on launchpad's Xenial environment (featuring debhelper 9.20160115ubuntu2). Instead of an auto dbg package, however, I'm getting ``` dh_gencontrol debug symbol wrapper: no debian/mixxx-dbgsym,

new netcdf packages: first review

2014-04-23 Thread Nico Schlömer
Hi all, as noted earlier, I'm working on moving the long-outdated netCDF version in Debian . This is not entirely trivial since upstream as decided to split netcdf in three separate packages, supporting C (the basis package), Fortran, and C++. I've b

Re: Fwd: Trilinos: to split or not to split

2014-04-16 Thread Nico Schlömer
> "libml.*", really ? > I wonder if you need to prefix all of the library names :-/. We're already considering prefixing them all with "trilinos_". --Nico On Wed, Apr 16, 2014 at 3:16 PM, Ian Jackson wrote: > Nico Schlömer writes ("Fwd: Trilinos: to s

Fwd: Trilinos: to split or not to split

2014-04-14 Thread Nico Schlömer
(Forward from debian-mentors.) Opinion time! I'm packaging a rather large software, Trilinos, a collection of libraries (libbelos, libml, libaztecoo,...) for numerical high-performance computing. Upstream supports monolithic builds, i.e., the collection of libraries is assumed to be fully presen