Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "ffmpegfs" to upload it to
Buster Backports, hoping to find someone who's interested. This is
exactly the package that is currently in Buster SID and Bullseye. I
think this could be useful
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "streamlink" for a new
upstream version 1.4.1.
* Package name: streamlink
Version : 1.4.1+dfsg-1
Upstream Author : Streamlink Team
* URL :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "materia-gtk-theme":
* Package name: materia-gtk-theme
Version : 20200320-0.1
Upstream Author : nana-4
* URL : https://github.com/nana-4/materia-theme
*
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "sane-backends"
Package name: sane-backends
Version : 1.0.29-1~experimental4
Upstream Author : [fill in name and email of upstream]
URL :
Your message dated Sat, 25 Apr 2020 12:39:34 -0400
with message-id
and subject line Re: Bug#958790: RFS: ffmpegfs/1.10-2~bpo10+1 [ ITP] --
read-only FUSE filesystem which transcodes between audio and video formats on
the fly)
has caused the Debian Bug report #958790,
regarding RFS:
On 2/12/20 2:21 PM, Leon Marz wrote:
> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "cglm"
>
> * Package name: cglm
>Version : 0.6.2-1
>Upstream Author : Recep Aslantas
> * URL :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "fuse-posixovl"
* Package name: fuse-posixovl
Version : 1.2.20120215+gitf5bfe35-3
Upstream Author : Jan Engelhardt ,
* URL :
> On Apr 25, 2020, at 00:10, Rebecca N. Palmer wrote:
>
> Matthew Fernandez wrote (ordering changed):
>> I don’t get the same warning for mipsel and armel because the binary built
>> fine there. It’s just that the test suite didn’t complete.
>
> No: by default, failed build-time tests fail
Hello,
My library can use SIMD vector operations such as AVX2 if available on
system.
What is the best way of managing this ? For simplicity, I could create two
packages, one with all SIMD disabled, and one assuming AVX2. What's the
standard way of approaching this?
Also, I tried logging onto
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "grok"
* Package name: grok
Version : 1.20110708.1-4.5
Upstream Author :
* URL : http://code.google.com/p/semicomplete/wiki/Grok
* License :
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]
Dear mentors,
I am looking for a sponsor for my package "tsvtree"
* Package name: tsvtree
Version : 1.0.3-1
Upstream Author : Marcelo Zimbres Silva
* URL :
On Sat, Apr 25, 2020 at 02:53:51PM -0400, Aaron Boxer wrote:
> Hello,
> My library can use SIMD vector operations such as AVX2 if available on
> system.
> What is the best way of managing this ?
Runtime detection.
> Also, I tried logging onto #debian-mentors on freenode, but I got a message
>
Le Sat, Apr 25, 2020 at 02:53:51PM -0400, Aaron Boxer a écrit :
>
> My library can use SIMD vector operations such as AVX2 if available on
> system.
> What is the best way of managing this ?
Hello,
maybe you can have a look at how other packages use `libsimde-dev`?
On Tue, Apr 21, 2020 at 5:29 AM wrote:
> Instead, I would like to build libfreehep-graphicsio-*-java binary
> packages from the single source package, and remove the old source
> packages. However, I am not sure if two source packages producing binary
> packages with the same names will not
Hi Paul,
On 2020-04-26 05:58, Paul Wise wrote:
> I think if you just move the existing binary packages to the new
> source package, that would be enough. Just make sure the versions of
> the new binary packages are newer than the versions of the old binary
> packages. IIRC you won't even need to
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "libonig"
Package name: libonig
Version : 6.9.5-2
Upstream Author : (K.Kosako)
URL : https://github.com/kkos/oniguruma
License : BSD-2-clause
Matthew Fernandez wrote (ordering changed):
I don’t get the same warning for mipsel and armel because the binary built fine
there. It’s just that the test suite didn’t complete.
No: by default, failed build-time tests fail the build (to make sure
they get noticed).
The "missing build on
17 matches
Mail list logo
