Bug#882730: RFS: wolfssl/3.12.2+dfsg-1 [requires NEW] -- wolfSSL encryption library

Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "wolfssl": * Package name: wolfssl Version : 3.12.2+dfsg-1 Upstream Author : wolfSSL Inc. * URL : www.wolfssl.com * License

Re: How to determine the filename for dlopen()

Hi! On Mon, 2017-11-13 at 13:23:01 +0100, Ferenc Wágner wrote: > I'm packaging a program which wants to dlopen() some library. It finds > this library via pkg-config (PKG_CHECK_MODULES). How to best determine > the filename to use in the dlopen() call? It should work cross-distro, > for

Bug#882565: marked as done (RFS: lr/1.2-1 -- list files, recursively)

Your message dated Sat, 25 Nov 2017 23:50:56 +0100 with message-id <20171125225056.3pqihjopz25tq...@angband.pl> and subject line Re: Bug#882565: RFS: lr/1.2-1 -- list files, recursively has caused the Debian Bug report #882565, regarding RFS: lr/1.2-1 -- list files, recursively to be marked as

Re: C++ help needed for centrifuge

Andreas Tille wrote: > Hi, > > I started packaging centrifuge[1] and hit a build error which > is most probably caused by gcc-7 incompatibility: > > ... > In file included from centrifuge_build.cpp:27:0: > bt2_idx.h: In static member function 'static std::pair Ebwt*>

Re: C++ help needed for centrifuge

Le 25/11/2017 à 21:56, Andreas Tille a écrit : > Hi, > > I started packaging centrifuge[1] and hit a build error which > is most probably caused by gcc-7 incompatibility: > > ... > In file included from centrifuge_build.cpp:27:0: > bt2_idx.h: In static member function 'static std::pair

C++ help needed for centrifuge

Hi, I started packaging centrifuge[1] and hit a build error which is most probably caused by gcc-7 incompatibility: ... In file included from centrifuge_build.cpp:27:0: bt2_idx.h: In static member function 'static std::pair Ebwt::fromStrings(const EList

Re: package pynmea2

On Tue, 2017-11-14 at 12:13:55 -0200, Herbert Fortes wrote: > There was a ITP-RFS for pynmea2. But python-nmea2 already > exists. > > https://packages.qa.debian.org/p/python-nmea2.html > > I asked the contributor (2017-11-12) to close the bugs with > an n-d...@bugs.debian.org but he sent

Re: How to find Multi-Arch path(s)

On Sat, 2017-11-25 at 11:36:27 +0100, Ole Streicher wrote: > Guillem Jover writes: > > The point is that the Multi-Arch concept in Debian is all about the > > interfaces. How packages and files interface with each other, and > > what is possible and allowed. Some examples: > >

Re: How to find Multi-Arch path(s)

Guillem Jover writes: > The point is that the Multi-Arch concept in Debian is all about the > interfaces. How packages and files interface with each other, and > what is possible and allowed. Some examples: > > * A script might be arch-independent in the contents sense;