Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "ghostwriter" in backport.
* Package name : ghostwriter
Version : 1.7.4-1~bpo9+1
Upstream Author : wereturtle
* URL : https://wereturtle.github.io/ghostwriter/
*
On Mon, Mar 04, 2019 at 05:03:30PM +0200, Andrius Merkys wrote:
> On 2019-03-04 16:56, Adam Borowski wrote:
> > But, are they actually available from the published API?
>
> Yes, they are; readelf --symbols prints them.
readelf doesn't know about the API.
The published API is in the docs and in
On Mon, Mar 04, 2019 at 01:37:51PM +0200, Andrius Merkys wrote:
> The upstream says that the renamed functions are not documented,
> therefore they are private-ish. However, strictly speaking these
> functions are public, as they are accessible in the ABI.
Please tell the upstream to not export
On 2019-03-04 16:56, Adam Borowski wrote:
> But, are they actually available from the published API?
Yes, they are; readelf --symbols prints them.
> And do reverse dependencies use those functions?
Not that I am aware of. The renamed functions were introduced for the
development only.
Thanks,
On Mon, Mar 04, 2019 at 01:37:51PM +0200, Andrius Merkys wrote:
> On 2019-03-04 13:32, Andrey Rahmatullin wrote:
> > What does the upstream say about this?
>
> The upstream says that the renamed functions are not documented,
> therefore they are private-ish. However, strictly speaking these
>
Hej Andreas,
Sure, sounds great! Thanks very much for offering to help. Sorry I have been
so slow -- I have lots of administrative and pedagogical responsibility, and no
students that might compile c++.
I thought I saw OpenMM is already packaged. If not it should have an MIT
license so
Hi,
On Wed, Feb 27, 2019 at 10:02:32AM +0200, Andrius Merkys wrote:
> Hi Samuel,
>
> On 2019-02-26 18:27, Samuel Flores wrote:
> > I would like some help packaging MacroMoleculeBuilder (MMB) for
> > distribution in Debian or Ubuntu. It is a mature piece of code, used to
> > publish many
On 2019-03-04 13:32, Andrey Rahmatullin wrote:
> What does the upstream say about this?
The upstream says that the renamed functions are not documented,
therefore they are private-ish. However, strictly speaking these
functions are public, as they are accessible in the ABI.
> The ideal way would
On Mon, Mar 04, 2019 at 01:29:44PM +0200, Andrius Merkys wrote:
> I am maintaining a package which has recently endured a
> backwards-incompatible ABI change due to a couple of function renames. I
> could restore the ABI compatibility by providing aliases (via patches)
> for the renamed functions.
Dear Mentors,
I am maintaining a package which has recently endured a
backwards-incompatible ABI change due to a couple of function renames. I
could restore the ABI compatibility by providing aliases (via patches)
for the renamed functions. My question is: would this be a viable
solution, or
Package: sponsorship-requests
Severity: wishlist
Dear mentors, maintainer, developer
I am looking for a sponsor for my package "fonts-myanmar"
Its font pack for Myanmar aka Burma
* Package name: fonts-myanmar
Version : 1.0-1
Upstream Author : kokoye2007
* URL :
11 matches
Mail list logo
