Bug#893716: marked as done (RFS: deepin-screen-recorder/2.7.3-1 [ITP])

2018-04-06 Thread Debian Bug Tracking System
Your message dated Sat, 7 Apr 2018 04:05:45 +0200 with message-id <20180407020545.ortrq2y4qkvck...@angband.pl> and subject line Re: Bug#893716: RFS: deepin-screen-recorder/2.7.3-1 [ITP] has caused the Debian Bug report #893716, regarding RFS: deepin-screen-recorder/2.7.3-1 [ITP] to be marked as don

Bug#893349: marked as done (RFS: deepin-screen-recorder/2.7.3-1 [ITP])

2018-04-06 Thread Debian Bug Tracking System
Your message dated Sat, 7 Apr 2018 04:05:45 +0200 with message-id <20180407020545.ortrq2y4qkvck...@angband.pl> and subject line Re: Bug#893716: RFS: deepin-screen-recorder/2.7.3-1 [ITP] has caused the Debian Bug report #893716, regarding RFS: deepin-screen-recorder/2.7.3-1 [ITP] to be marked as don

Bug#895032: RFS: deepin-music/3.1.8-1 [ITP]

2018-04-06 Thread Adam Borowski
On Fri, Apr 06, 2018 at 08:15:17PM +0800, Yanhao Mo wrote: > * Package name: deepin-music > Version : 3.1.8-1 > Upstream Author : Deepin Technology Co., Ltd. > * URL : https://github.com/linuxdeepin/deepin-music > * License : GPL-3+ > Section : sound >

Bug#881295: marked as done (RFS: rednotebook/2.3-1 [ITP])

2018-04-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Apr 2018 16:21:57 + with message-id and subject line closing RFS: rednotebook/2.3-1 [ITP] has caused the Debian Bug report #881295, regarding RFS: rednotebook/2.3-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this i

Re: Different symbols files on different architectures

2018-04-06 Thread Sebastiaan Couwenberg
On 04/06/2018 05:48 PM, Andreas Tille wrote: > Hi Bas, > > On Fri, Apr 06, 2018 at 02:18:03PM +0200, Sebastiaan Couwenberg wrote: >> On 04/06/2018 02:08 PM, Andreas Tille wrote: >>> after adding a symbols file to libbpp-core all other architectures are >>> failing due to different symbols (see bel

Re: Different symbols files on different architectures

2018-04-06 Thread Andreas Tille
Hi Bas, On Fri, Apr 06, 2018 at 02:18:03PM +0200, Sebastiaan Couwenberg wrote: > On 04/06/2018 02:08 PM, Andreas Tille wrote: > > after adding a symbols file to libbpp-core all other architectures are > > failing due to different symbols (see below for ppc64el[1]) but others > > are failing as wel

C++ and Python package combined

2018-04-06 Thread Nico Schlömer
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,) * t

Re: Different symbols files on different architectures

2018-04-06 Thread Sebastiaan Couwenberg
On 04/06/2018 02:08 PM, Andreas Tille wrote: > after adding a symbols file to libbpp-core all other architectures are > failing due to different symbols (see below for ppc64el[1]) but others > are failing as well. What is the correct way to fix this? Use (arch=ppc64el) tags for the symbols, or so

Bug#895032: RFS: deepin-music/3.1.8-1 [ITP]

2018-04-06 Thread Yanhao Mo
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "deepin-music" * Package name: deepin-music Version : 3.1.8-1 Upstream Author : Deepin Technology Co., Ltd. * URL : https://github.com/linuxdeepin/deepin-music * L

Different symbols files on different architectures

2018-04-06 Thread Andreas Tille
Hi, after adding a symbols file to libbpp-core all other architectures are failing due to different symbols (see below for ppc64el[1]) but others are failing as well. What is the correct way to fix this? Kind regards Andreas. On Fri, Apr 06, 2018 at 11:04:02AM +0200, Julien Yann Dutheil