Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "proftpd-mod-sftp-ldap":
* Package name : proftpd-mod-sftp-ldap
Version : 0.2-1
Upstream contact : TJ Saunders
* URL :
http://www.castaglia.org/proftpd/modu
> https://lists.debian.org/debian-legal/2023/01/msg5.html
> https://lists.debian.org/debian-mentors/2023/01/msg00097.html
Roberto, Tobias, thanks for your answers.
I have removed MagicSFver2.sf2 from the package and added a note to
README.Debian.
The new package now depends on fluid-soundfont
Hello Mentors,
Yesterday I opened bug report #1028919 for mupdf with a patch attached. A
maintainer quickly picked the patch up and uploaded a new version of mupdf. I'm
keeping an eye on tracker.debian.org and I noticed that the new upload is said
to introduce a regression in img2pdf's autopkgt
On Sun, 15 Jan 2023 15:59:13 +0100 vmxevils...@gmail.com wrote:
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "linux":
>
> * Package name : linux
>Version : 6.1.6-1~exp1
>Upstream contact : Salvatore Bonac
As already mentioned in #1023160 you can get rid of the ghc filesystem library.
You have to patch CMakeLists.txt and launcher/CMakeLists.txt and can then
remove libraries/filesystem.
Also, please remove libraries/tomlplusplus.
On Sun, Jan 15, 2023 at 04:20:35PM +0100, Stephen Sinclair wrote:
> I have been trying to make an update to my package "siconos".
> However, in the Salsa build, which nicely runs all tests, it fails on
> "piuparts".
>
> The job log is here:
> https://salsa.debian.org/science-team/siconos/-/jobs/37
Dear mentors,
I have been trying to make an update to my package "siconos".
However, in the Salsa build, which nicely runs all tests, it fails on
"piuparts".
The job log is here:
https://salsa.debian.org/science-team/siconos/-/jobs/3796471
I am confused, because it fails with the following error
Hi all,
I'm looking into whether it is feasible to package EnTT [1], a header-only C++
library with breaking API changes every few releases / months.
Would the following approach be sufficient to prevent reverse dependencies from
having dependency issues when the library is updated:
1) Create a
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "scm":
* Package name : scm
Version : 5f3-3
Upstream contact : [fill in name and email of upstream]
* URL : https://people.csail.mit.edu/jaffer/SCM.html
*
9 matches
Mail list logo