2:00PM +0200, Nico Schlömer wrote:
> > Thanks Andrey for looking into this. How did you find out it comes
> > from hhdate's CMakeLists.txt?
> 1. I googled ONLY_C_LOCALE and found the project that uses it, the one
> that includes that date.h, https://github.com/HowardHinnant/date
>
> https://wiki.debian.org/Salsa has the details of how to contact the salsa
> admins.
Very good, thank you
-Nico
On Thu, Jul 16, 2020 at 9:06 PM Sudip Mukherjee
wrote:
>
> Hi Nico,
>
> On Thu, Jul 16, 2020 at 6:32 PM Nico Schlömer
> wrote:
> >
> > I click
Thanks Andrey for looking into this. How did you find out it comes
from hhdate's CMakeLists.txt?
Cheers,
Nico
On Thu, Jul 16, 2020 at 8:29 PM Andrey Rahmatullin wrote:
>
> On Thu, Jul 16, 2020 at 08:04:20PM +0200, Nico Schlömer wrote:
> > Hi everyone,
> >
> > I'm t
Hi everyone,
I'm trying to build a package for waybar [1], and I'm running some
test builds on a PPA. I'm inching close, but now there's something I
cannot figure out: The build process adds the flag
```
-DONLY_C_LOCALE=
```
to the compile line, and that makes the build fail in the date.h
Jul 16, 2020 at 05:29:55PM +0200, Nico Schlömer wrote:
> > Hi everyone,
> >
> > I'm having problems logging in the salsa. Resetting the password
> > appears to work, but I can't even log in with the new password after
> > the successful update.
>
> Mmm, "
Hi everyone,
I'm having problems logging in the salsa. Resetting the password
appears to work, but I can't even log in with the new password after
the successful update.
Any suggestions?
Cheers,
Nico
t;
> On Mon, Feb 03, 2020 at 08:00:47PM +0100, Nico Schlömer wrote:
> ...
> > Unfortunately, I only get
> > ```
> > uscan: error: tar -t -a -f ../gmsh-4.5.2-source.tgz subprocess
> > returned exit status 2
> ...
> > ```
> > Curiously, when I tar fr
Hi everyone,
I'm trying to update a package via
```
gbp import-orig --uscan
```
Unfortunately, I only get
```
uscan: error: tar -t -a -f ../gmsh-4.5.2-source.tgz subprocess
returned exit status 2
```
I can confirm that this `tar` like gives the error
```
[...]
gmsh-4.5.2-source/.clang-format
tar:
nu.so
>
> Am 22.12.19 um 16:04 schrieb Nico Schlömer:
> > No idea about that, but for me it fails [1] with the new libproj 6
> > [2]. I have reported the bug [3] and will try to work around it. Will
> > report back.
> >
> > Cheers,
> > Nico
> >
> &g
ParallelXdmf3"
> Call Stack (most recent call first):
> CMake/vtkModuleTop.cmake:72 (vtk_module_check)
> CMake/vtkModuleTop.cmake:79 (vtk_module_check)
> CMakeLists.txt:104 (include)
>
>
> Anton
>
> Am Fr., 20. Dez. 2019 um 14:07 Uhr schrieb Nico Schlömer
&
Have you had the time to try again yet?
Cheers,
Nico
On Mon, Nov 18, 2019 at 10:36 AM Nico Schlömer wrote:
>
> I've pushed a tentative fix, but cannot verify since it build and used
> to build on the PPA [1]. Best try it out yourself.
>
> Cheers,
> Nico
>
> [1] https:
t looks like the package does not build:
>
> CMake Error at CMake/vtkModuleTop.cmake:56 (message):
> No such module "vtkIOXdmf3" needed by "vtkIOParallelXdmf3"
>
> Could you please have a look?
>
> Thanks
>
> Anton
>
> Am Do., 10. Okt. 2019 um 21:2
Hi everyone,
I've worked on VTK8 [1] and I think it's about ready to be included
into Debian. (More than two years after its release, unfortunately.)
There's a PPA with the latest build [2] if you want to try it out.
Could anyone take a look? What would be the steps to get it into Debian?
That works, thank you!
On Wed, Oct 2, 2019 at 5:23 PM Adam Borowski wrote:
>
> On Wed, Oct 02, 2019 at 02:13:27PM +0200, Nico Schlömer wrote:
> > a package now uses dashes instead of dots in upstream release tar
> > names. The watch file
>
> > opts=filenamema
Hello everyone,
a package now uses dashes instead of dots in upstream release tar
names. The watch file
```
version=4
opts=filenamemangle=s/.+\/trilinos-release-@ANY_VERSION@\.tar\.gz/trilinos-$1\.tar\.gz/
\
https://github.com/trilinos/Trilinos/tags
.*/trilinos-release-@ANY_VERSION@\.tar\.gz
```
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> There seems to be no license text in the file. Usually one has both a
license statement and a license paragraph, listing the license text. For
example:
Alright, thank you!
-BEGIN PGP SIGNATURE-
Version: FlowCrypt 6.9.3 Gmail Encryption
hou wrote:
>
> Hi Nico,
>
> 1. libmmg-dev should depend on libmmg5 (= ${binary:Version})
> 2. mmg should depend on libmmg5 (= ${binary:Version})
> 3. lintian -EviI will tell you the rest problems
>
> On 2019-08-05 20:58, Nico Schlömer wrote:
> > I created a package [1] for M
I created a package [1] for Mmg [2], a great (scientific) mesh
generator and optimizer.
Everything appears to work fine and I'd be happy about some feedback.
Cheers,
Nico
[1] https://salsa.debian.org/science-team/mmg
[2] https://www.mmgtools.org/
:19, s...@svenhartge.de wrote:
> Nico Schlömer wrote:
>
> > I'm starting to package Stellar, a tet mesh optimizer [1].
>
> > The package is very basic, but still things are failing. I don't know
why.
>
> > 1. The gitlab-ci build [2] fails with
> > ```
> > Ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks Andrey for the reply.
> No idea about that but "gbp:error: Non-native package 'stellar' has
invalid version '1.0'" is a valid problem.
Fair enough. What does it mean? How to fix it?
> Have you ever built this package yourself? I'm sure the
Hi everyone,
I'm starting to package Stellar, a tet mesh optimizer [1].
The package is very basic, but still things are failing. I don't know why.
1. The gitlab-ci build [2] fails with
```
Checking cache for default...
FATAL: file does not exist
Failed to extract cache
```
What does this mean?
Alright, thanks!
On Fri, Jul 19, 2019 at 4:44 PM Sven Hartge wrote:
>
> Nico Schlömer wrote:
>
> > From the gmsh repro-build, I'm getting
> > ```
> > /builds/science-team/gmsh/debian/output: found 38 matching files
> > ERROR: Uploading artifacts to coordinator..
>From the gmsh repro-build, I'm getting
```
/builds/science-team/gmsh/debian/output: found 38 matching files
ERROR: Uploading artifacts to coordinator... too large archive
id=227001 responseStatus=413 Request Entity Too Large status=413
Request Entity Too Large token=XzzUdm1f
FATAL: too large
```
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ah, I get it now! Because `${DEB_HOST_MULTIARCH}` is used in the
.install-files, they have to be treated with a special tool, dh-exec, that
takes the variables from debian/rules.
Thanks everyone!
-BEGIN PGP SIGNATURE-
Version: FlowCrypt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
>> debian/rules has
>> ```
>> DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
>> ```
>> so I thought (on respective machines), {DEB_HOST_MULTIARCH} equals
>> x86_64-linux-gnu. Not the case?
> No substitutions is done on
ux-gnu. Not the case?
On Mon, Jul 15, 2019 at 3:22 PM Sven Joachim wrote:
>
> On 2019-07-15 14:44 +0200, Nico Schlömer wrote:
>
> > Hi everyone,
> >
> > when upgrading gmsh to 4.4.0, I'm getting the build error
> > ```
> > [...]
> > dpkg-shlibdep
Hi everyone,
when upgrading gmsh to 4.4.0, I'm getting the build error
```
[...]
dpkg-shlibdeps: error: cannot find library libgmsh.so.4.4 needed by
debian/gmsh/usr/bin/gmsh (ELF format: 'elf64-x86-64' abi:
'0201003e'; RPATH: '')
dpkg-shlibdeps: error: cannot continue due to the error
Indeed, thank you.
On Sun, Jul 14, 2019 at 7:30 PM Balasankar "Balu" C
wrote:
>
> Hi Nico,
>
> On 7/14/19 10:35 PM, Nico Schlömer wrote:
> > Hi everyone,
> >
> > I'm trying to update gmsh [1], but the tests on salsa report
> > ```
> >
Hi everyone,
I'm trying to update gmsh [1], but the tests on salsa report
```
gbp:error: upstream/4.4.0+ds1 is not a valid treeish
```
See [2]. I have no idea why this comes up.
Any hints?
Cheers,
Nico
[1] https://tracker.debian.org/pkg/gmsh
[2]
://buildd.debian.org/status/fetch.php?pkg=ros-vision-opencv=amd64=1.12.3%2Bds-1%2Bb2=1519637198=0
On Mon, Apr 9, 2018 at 3:51 PM Leopold Palomo-Avellaneda <l...@alaxarxa.net>
wrote:
> Nico,
>
> On 09/04/18 15:13, Nico Schlömer wrote:
> > Thanks Leo,
> >
> > I've checked out ros-
simple.
Unfortunately, this doesn't help much with my problem.
Cheers,
Nico
On Mon, Apr 9, 2018 at 1:18 PM Leopold Palomo-Avellaneda <l...@alaxarxa.net>
wrote:
> On 06/04/18 16:38, Nico Schlömer wrote:
> > Hi everyone,
> >
> > I would like to package a piece of soft
8 at 4:04 PM, Nico Schlömer wrote:
>
> >> Which software is this?
> >
> > FEniCS/Dolfin [1]. (I'm preparing the upcoming release.)
>
> Has something changed to prevent the existing dh overrides from working?
>
> https://sources.debian.org/src/dolfin/2017.2.0.p
gt; On Fri, Apr 6, 2018 at 10:38 PM, Nico Schlömer wrote:
>
> > I would like to package a piece of software
>
> Which software is this?
>
> > Any hints?
>
> Does the upstream build system not take care of each of the steps?
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
>
>
Hi everyone,
I would like to package a piece of software that includes both a C++
library and a Python package. When building locally from scratch, one is
supposed to
* build and install the library first,
(* then build and run the tests, compiling against what just has been
installed,)
*
Hi everyone,
I sometimes see in d/copyright
> Copyright: John Doe
> License: public-domain
e.g., [1]. However, these two statements contradict each other: public
domain means exactly the _absence_ of copyright [2]. Specifically, public
domain is _not_ open source [3]. In fact, it's not a proper
, Jan 23, 2017 at 10:02 PM Andrey Rahmatullin <w...@debian.org> wrote:
On Mon, Jan 23, 2017 at 08:25:24PM +, Nico Schlömer wrote:
> to the CMake config, it all seems to configure and build fine. That is
> until dpkg-shlibdeps enters the stage (right before installation):
It's not &
Hi everyone,
Still struggling with the binary-or-shlib-defines-rpath [1] here. After
having added
```
-DCMAKE_SKIP_INSTALL_RPATH:BOOL=ON
-DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=OFF
```
to the CMake config, it all seems to configure and build fine. That is
until dpkg-shlibdeps enters the stage
the latter -- makes sense.
What's the suggested workaround here?
Cheers,
Nico
[1]
https://launchpadlibrarian.net/303079195/buildlog_ubuntu-zesty-ppc64el.trilinos_12.11~20170119114916-33933755-1zesty1_BUILDING.txt.g
z
On Thu, Jan 19, 2017 at 3:03 PM Nico Schlömer <nico.schloe...@gmail.com>
s Cowgill wrote:
> > Hi,
> >
> > On 18/01/17 22:39, Nico Schlömer wrote:
> >> I'm co-maintaining the Trilinos package [1] in Debian and recently found
> >> a bunch of new lintian warnings of the kind
> >> binary-or-shlib-defines-rpath [2]. It say in the des
,
On Wed, Jan 18, 2017 at 10:39:47PM +0000, Nico Schlömer wrote:
> That's not true later on when the libraries are _installed_, of course.
For
> this, CMake has the switch CMAKE_SKIP_INSTALL_RPATH [3], which serves
exactly
> that purpose. For some reason, lintian doesn't seem to be happy
Hi everyone,
I'm co-maintaining the Trilinos package [1] in Debian and recently found a
bunch of new lintian warnings of the kind binary-or-shlib-defines-rpath
[2]. It say in the description of the warning:
```
To fix this problem, look for link lines like:
gcc test.o -o test
Thanks, this did the trick.
On Fri, May 20, 2016 at 1:43 PM Mattia Rizzolo <mat...@debian.org> wrote:
> On Fri, May 20, 2016 at 11:10:43AM +0000, Nico Schlömer wrote:
> > Thanks for the hint.
> > Unfortunately, it's not working dpt picks up an older version that
> alread
Hi everyone,
Say a package installs only headers, and in one of those, a header of
another -dev package is #included. How to depend on the package?
Cheers,
Nico
Hi everyone,
When I signed up some years ago, I got a user name with -guest appended. I
guess that was the policy at the time. In any case, how can I change that?
I wouldn't mind an entirely new account either, even if I have to sign up
for all my groups again.
Cheers,
Nico
Dumont <d...@debian.org> wrote:
> On Friday 20 May 2016 10:19:19 Nico Schlömer wrote:
> > I've got a git-managed repo where an upstream version was included (via
> the
> > upstream branch, merged into master), but adding a corresponding
> > pristine-tar was omitte
Hi everyone,
I've got a git-managed repo where an upstream version was included (via the
upstream branch, merged into master), but adding a corresponding
pristine-tar was omitted. How can I retroactively add a pristine-tar
corresponding to an upstream release?
Cheers,
Nico
Thanks for your input!
Cheers,
Nico
On Thu, Nov 19, 2015 at 1:27 PM Ghislain Vaillant <ghisv...@gmail.com>
wrote:
> On 19/11/15 11:55, Jakub Wilk wrote:
> > * Nico Schlömer <nico.schloe...@gmail.com>, 2015-11-18, 22:52:
> >> I'm building the symbols for all lib
Hi everyone,
I'm building the symbols for all libraries in the Trilinos package.
Unfortunately, the documentation [1] isn't too verbose here. One thing that
has come to my attention, for example, is the fact that some Trilinos
libraries appear to contain lots of symbols; including some (all?) of
Hi everyone,
I'm packaging a software which includes the following license statement:
```
Under the terms of Contract DE-AC04-94AL85000 with Sandia Corporation,
the U.S. Government retains certain rights in this software.
.
Redistribution and use in source and binary forms, with or without
]
https://bitbucket.org/fathomteam/moab/pull-requests/137/clean-up-debian-folder/diff#chg-debian/GNUmakefile
On Mon, Oct 26, 2015 at 8:55 AM Johannes Schauer <jo...@debian.org> wrote:
> Hi Nico,
>
> Quoting Nico Schlömer (2015-10-26 00:47:54)
> > particularly those which have been
gt; wrote:
> Hi Nico,
>
> Quoting Nico Schlömer (2015-10-24 20:04:19)
> > In [MOAB](https://bitbucket.org/fathomteam/moab/), we (optionally)
> depend on
> > a rather new version of the [Metis](
> https://packages.debian.org/sid/metis)
> > package, and that's what's enf
Hi everyone,
In [MOAB](https://bitbucket.org/fathomteam/moab/), we (optionally) depend
on a rather new version of the [Metis](https://packages.debian.org/sid/metis)
package, and that's what's enforced in our debian/control, too. Now, we
would like to provide MOAB for older versions of
Hi everyone,
In Debian, I find packages such as
```
libzeep3.0
libzdb9
libzim0
```
i.e., libraries with some number appended. What's the meaning of that
number?
Cheers,
Nico
Hi everyone,
I recently came across a package [1] which ideally would like to
handle its own build flags (adding `-O3 -ffast-math` for speed, for
example).
What is the Debian policy on this?
Cheers,
Nico
[1] https://packages.debian.org/sid/sound/mixxx
--
To UNSUBSCRIBE, email to
Thanks Paul for the concise explanation. This helped me fixing the
error within minutes!
Cheers,
Nico
On Sun, Feb 1, 2015 at 4:37 AM, Paul Wise p...@debian.org wrote:
On Sat, Jan 31, 2015 at 8:40 PM, Nico Schlömer wrote:
For Mixxx [1], I would like for users to produce meaningful backtraces
Hi all,
For Mixxx [1], I would like for users to produce meaningful backtraces
in case of crashes (see [2]). What build options are needed or useful
for debugging purposes? What's the canonical way for adding them to
the Debian packages?
Cheers,
Nico
[1]
Hi all,
The audio processing library SoundTouch [1,2] is a major CPU eater in
many applications (see, e.g. [3]). I'm now asking myself to what
degree we allow optimization for CPU arches in Debian (e.g., MMX,
SSE).
Cheers,
Nico
[1] https://packages.debian.org/sid/libsoundtouch-dev
[2]
/to/netcdf.changes`.
Will look at those later.
Cheers,
Nico
On Thu, Jan 15, 2015 at 8:59 PM, Sebastiaan Couwenberg
sebas...@xs4all.nl wrote:
On 01/15/2015 07:57 PM, Nico Schlömer wrote:
that you still have local changes not pushed to Alioth?
Right; fixed now.
Thanks for the push!
Can you also
-may-check-gpg-signature
```
What do you get?
Cheers,
Nico
On Fri, Jan 16, 2015 at 10:20 AM, Nico Schlömer
nico.schloe...@gmail.com wrote:
Can you also update the pristine-tar branch with your upstream tarballs
as imported into the upstream branch?
Done. `git-import-orig` helped me out here
that you still have local changes not pushed to Alioth?
Right; fixed now.
–Nico
On Thu, Jan 15, 2015 at 7:21 PM, Sebastiaan Couwenberg
sebas...@xs4all.nl wrote:
Hi Nico,
On 01/15/2015 09:52 AM, Nico Schlömer wrote:
I'd be great if you could have a look at the branch `split-c-f-cxx
Hi Sebastiaan, all,
Last night, netCDF 4.3.3-rc3 was released [1] with 4.3.3 to be
expected very soon. I've been working on getting it to build with
Debian for a while now (mostly pushing things upstream), and I'm
thinking we're in a good shape right now.
I'd be great if you could have a look at
Hi all!
A small question on how to configure a Debian package with proper
installation of user documentation.
The package I'm looking at is netCDF [1] which – apart from the
library and headers – installs the file
```
$ cat /usr/share/doc-base/netCDF
Document: netCDF
Title: NetCDF Manual
Author:
PM, Nico Schlömer nico.schloe...@gmail.com wrote:
moving the doc-base file to libnetcdf-doc should be the right
way forward.
Alright, I'll see to that.
I wanted to reproduce your problem, but was unable because the source
package in git is different from the source you're working with.
I'm
moving the doc-base file to libnetcdf-doc should be the right
way forward.
Alright, I'll see to that.
I wanted to reproduce your problem, but was unable because the source
package in git is different from the source you're working with.
I'm working in [1], but replace the sources daily
```
$ install-docs --verbose --check /usr/share/doc-base/netcdf
/usr/share/doc-base/netcdf: No problems found.
```
Thanks!
–Nico
On Thu, Jan 8, 2015 at 4:19 PM, Sebastiaan Couwenberg
sebas...@xs4all.nl wrote:
I see the file
```
libnetcdf-dev.doc-base
```
in the debian/ folder [1]. I suppose
Hi all,
a quick question about architecture restrictions in `debian/control`.
I have a large tarball which I configure and compile, and then break
up into a number of Debian packages (similar to boost). Unfortunately,
one of the components doesn't compile on 32-bit architectures, which
means
[Please please please use concrete package names. It's hard to reason about
abstracts like libmyproject-subpackage-7, especially if information needed
for a good judgment was missing in the mail, or well hidden between the
lines.]
That's a good hint; I'll do so in the future. Thanks!
–Nico
Hi all,
the old netCDF package [1] has an epoch slot, 1, which seems entirely
unnecessary. For the rewrite, it'd be nice if we could get rid of it.
Is that common practice? Is there an upgrade path for it?
Cheers,
Nico
[1] https://packages.debian.org/km/source/sid/mipsel/netcdf
--
To
are different then you will be able to
avoid the epoch.
Nope, the package names stay the same.
I guess then we will have to drag the epoch along with us... :/
--Nico
On Tue, Jun 17, 2014 at 3:39 PM, Paul Wise p...@debian.org wrote:
On Tue, Jun 17, 2014 at 9:35 PM, Nico Schlömer wrote:
the old
:16 AM, Nico Schlömer wrote:
How could I best debug this (through debian/rules, maybe)?
grep through the upstream cmake files looking for CMAKE_BUILD_TYPE, I
had an upstream that was not handling the case when it was set to None
properly and I guess you have the same issue.
--
bye,
pabs
```
```
(nothing).
Is this expected?
Cheers,
Nico
On Wed, Jun 11, 2014 at 10:26 AM, Nico Schlömer
nico.schloe...@gmail.com wrote:
I had an upstream that was not handling the case when it was set to None
properly and I guess you have the same issue.
And indeed that was the case. Now fixed upstream
Hi all,
if I understand correctly from [1], the default CMAKE_BUILD_TYPE used
by dh should be RelWithDebInfo. I found that, when
override_dh_auto_configure is not empty in debian/rules, e.g,
override_dh_auto_configure:
dh_auto_configure -- \
-DCMAKE_SKIP_RPATH:BOOL=ON
/177295900/buildlog_ubuntu-utopic-amd64.netcdf_1%3A4.3.3~20140610-utopic1_UPLOADING.txt.gz
On Tue, Jun 10, 2014 at 7:51 PM, Nico Schlömer nico.schloe...@gmail.com wrote:
Hi all,
if I understand correctly from [1], the default CMAKE_BUILD_TYPE used
by dh should be RelWithDebInfo. I found that, when
Hi all,
I'd like to create a library package using dh with CMake, and I would
like the build process to produce the library both statically and
dynamically linked.
CMake's rationale here is:
Recompile the whole thing, because:
In practice, most libraries have different defines and compiler flags
Hi all,
I've got a package here that supports both Cmake and automake
configurations. How do I force the builder to use CMake in
debian/rules?
Cheers,
Nico
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
That works, thanks Daniel!
--Nico
On Thu, May 8, 2014 at 5:26 PM, Daniel Lintott dan...@serverb.co.uk wrote:
Hi Nico,
On 08/05/14 16:21, Nico Schlömer wrote:
Hi all,
I've got a package here that supports both Cmake and automake
configurations. How do I force the builder to use CMake
+0200, Nico Schlömer wrote:
Does anyone have hints about how Debian manages to slip in the
x86_64-linux-gnu part in the library install path?
You have to add
INCLUDE(GNUInstallDirs)
to the CMakeLists.txt and use the according variables in the install
command. cf:
http://www.cmake.org/cmake
Hi all,
I would like to hear your opinion on the following question:
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
Hi all,
if a packages produces static libraries .a, .la, do they belong in
liba or liba-dev?
Cheers,
Nico
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Hi all,
dh_installdocs fails on me because the software has no file README,
but README.md.
```
cp -a README debian/libnetcdfcxx/usr/share/doc/libnetcdfcxx
cp: cannot stat 'README': No such file or directory
```
How to adapt debian/rules to accommodate for this?
Cheers,
Nico
--
To UNSUBSCRIBE,
Hi all,
I'm packaging a project that uses autoreconf and on my local machine
configures and builds fine with default options throughout. With the
minimal debian/rules file
https://github.com/nschloe/launchpad-submitter/blob/master/debian-netcdfcxx/rules,
it all seems to work out fine. However,
-bin the new netcdf-bin.
Cheers,
Nico
On Sat, Mar 29, 2014 at 8:37 AM, Eric L. ewl+debian+nospam2...@lavar.de wrote:
Hi,
On 28 March 2014 09:20:01 CET, Dominique Dumont d...@debian.org wrote:
On Thursday 27 March 2014 22:21:55 Nico Schlömer wrote:
The question is: how to avoid breaking
Hi all,
the Debian packages for netCDF
http://www.unidata.ucar.edu/software/netcdf/ are currently at 4.1.3,
a version released some three years ago
http://www.unidata.ucar.edu/software/netcdf/release-notes-4.1.3.html.
A bug report was filed against this a few months back
}, libB-dev
Would you consider this sane? Will whatever magic acts in
${shlibs:Depends}, ${misc:Depends} be able to identify libB as a
dependency of libA?
Cheers,
Nico
On Mon, Mar 24, 2014 at 11:29 AM, Mathieu Malaterre ma...@debian.org wrote:
On Mon, Mar 24, 2014 at 11:18 AM, Nico Schlömer
:31 PM, Nico Schlömer nico.schloe...@gmail.com
wrote:
No, the 'linker' does not complain.
You're right, it is the CMake dependency checker. The linking is all
right, but there's something amiss with the CMake export files. I'll
investigate.
I think you should find online reference with those
...@gmail.com wrote:
Hi
On 3/20/14, Nico Schlömer nico.schloe...@gmail.com wrote:
I'm building a package for a library A that depends on another
library, libB.so (from its dev-version). When installing library A,
the package libb is installed, containing libB.so.7.2 and libB.so.7.
When linking
Hi all,
I'm packaging a library libA which depends on a header-only library
libB. Obviously I need libB to be present whenever I build an
executable against libA. Where in debian/control will I have to fill
in libB?
Cheers,
Nico
--
To UNSUBSCRIBE, email to
+0100, Nico Schlömer wrote:
I'm packaging a library libA which depends on a header-only library
libB.
How?
--
WBR, wRAR
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https
Actually, you usually don't get these kind of warnings for Python extension
modules. The warning is emitted only if a module has SONAME, and it
typically doesn't.
You might want to get rid of SONAMEs
That indeed was the problem. Thanks!
It's a CMake/SWIG build, and I now added a patch to set
Hi all,
I'm building a package for a library A that depends on another
library, libB.so (from its dev-version). When installing library A,
the package libb is installed, containing libB.so.7.2 and libB.so.7.
When linking an executable against libA.so, the linker rightfully
complains about a
at 1:54 PM, Thibaut Paumard mlotpot.n...@free.fr wrote:
Le 20/03/2014 13:22, Nico Schlömer a écrit :
Hi all,
I'm building a package for a library A that depends on another
library, libB.so (from its dev-version). When installing library A,
the package libb is installed, containing libB.so.7.2
Hi all,
I'm building a package with Python support and would like to reduce
the number of warnings that dh_python2 gives me.
One of them is
public extension linked with libpython2.7
for a number of libraries. It is true that libpython2.7 is linked into them,
$ readelf -d /path/to/_ML.so
, Mar 17, 2014 at 6:28 PM, Jakub Wilk jw...@debian.org wrote:
* Nico Schlömer nico.schloe...@gmail.com, 2014-03-17, 15:49:
I'm building a package with Python support and would like to reduce the
number of warnings that dh_python2 gives me.
One of them is
public extension linked
93 matches
Mail list logo
