Bug#1028989: RFS: proftpd-mod-sftp-ldap/0.2-1 [ITP] -- ProFTPD module mod_sftp-ldap
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/modules/mod_sftp-ldap.html * License : GPL-2+ * Vcs : https://salsa.debian.org/debian-proftpd-team/proftpd-mod-sftp-ldap Section : net The source builds the following binary packages: proftpd-mod-sftp-ldap - ProFTPD module mod_sftp-ldap To access further information about this package, please visit the following URL: https://mentors.debian.net/package/proftpd-mod-sftp-ldap/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/proftpd-mod-sftp-ldap/proftpd-mod-sftp-ldap_0.2-1.dsc Changes for the initial release: proftpd-mod-sftp-ldap (0.2-1) unstable; urgency=medium . * Initial upload (Closes: #1028630). . [ Paweł Tomulik ] * Providing an initial package I could use as starter. Regards, -- Hilmar Preusse
Bug#1025274: License question about sf2 soundfont in Tuxguitar
> 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-gm, see https://mentors.debian.net/package/tuxguitar/ The package builds and runs on amd64 and in Qemu for arm64. It looks pretty good to me now. Maybe someone can take a look and upload it? If there is anything more I can do, just let me know.
Regression in autopkgtest because of bug in another package
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 autopkgtest. Looking at the autopkgtest log, the underlying issue seems to be #1028904 in pillow. Would it be useful to file a bug report against img2pdf for this? Should I send a control message to the BTS to report that bug #1028904 affects img2pdf? Or will this situation automatically resolve itself once pillow is fixed? I tried searching the Debian Wiki, the Developer Reference and the mailing list archives, but I've not found an answer so far. Kind regards, Victor Westerhuis
Bug#1028965: RFS: linux/6.1.6-1~exp1 [ITP] -- Linux for multiprocessor
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 Bonaccorso > * URL : https://www.kernel.org/ > * License : Unicode-data, LGPL-2.1, GPL-2+-or-X11, CRYPTOGAMS, LGPL-2.1 or BSD-2-clause, GPL-2 or BSD-2-clause, GPL-2, Xen-interface > * Vcs : https://salsa.debian.org/kernel-team/linux >Section : kernel JFTR: This isn't the way and Salvatore isn't the Upstream contact and was not made aware of this (prior). 6.1.6 is already present in salsa and earlier today an email was send out about the intention for an upload of 6.1.6 https://salsa.debian.org/kernel-team/linux/-/commit/ f44a493cc158a227718de2689434bb6db107edd8 IOW: in sofar it wasn't already completely obvious, ignore this RFS. signature.asc Description: This is a digitally signed message part.
Bug#1022747: RFS: prismlauncher/5.0+ds-1 [ITP] -- FOSS Minecraft launcher supporting multiple instances and accounts
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.
Re: help with python3 depends < 3.11
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/3796471
>
> I am confused, because it fails with the following error:
>
> > The following packages have unmet dependencies:
> > python3-siconos : Depends: python3 (< 3.11) but 3.11.1-1 is to be installed
>
> However, debian/control uses ${python3:Depends} and does not mention
> version 3.11 anywhere, so I cannot understand where it's getting this
> "< 3.11" constraint from.
What python version did you have installed when the package was built?
Greetings
Marc
--
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
help with python3 depends < 3.11
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:
> The following packages have unmet dependencies:
> python3-siconos : Depends: python3 (< 3.11) but 3.11.1-1 is to be installed
However, debian/control uses ${python3:Depends} and does not mention
version 3.11 anywhere, so I cannot understand where it's getting this
"< 3.11" constraint from.
Any help would be appreciated, thank you.
Steve
Packaging a header-only library with frequent breaking changes
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 new source and binary package for each new upstream version with breaking changes: Source: entt3.11-> entt3.12 Binary: libentt3.11-dev -> libentt3.12-dev 2) Create a virtual package libentt-dev which depends on the latest binary package: Package: libentt-dev Depends: libentt3.12-dev 3) Have each new binary package version Conflict with all previous versions, to prevent users from trying to install the same headers from multiple versions? Package: libentt3.12-dev Conflicts: libentt3.11-dev, libentt3.10-dev, (...) Additionally, would I only then remove old versions from the archive when there are no more reverse-dependencies left for that version of the package in stable and testing? [1] https://github.com/skypjack/entt Thanks, Matthew
Bug#1028958: RFS: scm/5f3-3 [Team] -- Scheme language interpreter
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 * License : GFDL-1.3+, LGPL-3+, GPL-3+ * Vcs : https://salsa.debian.org/scheme-team/scm Section : interpreters The source builds the following binary packages: scm - Scheme language interpreter libscm-dev - Embeddable library for SCM Scheme language interpreter To access further information about this package, please visit the following URL: https://mentors.debian.net/package/scm/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scm/scm_5f3-3.dsc Changes since the last upload: scm (5f3-3) unstable; urgency=medium . * Team upload. . * Fix ftbfs on riscv64, s390x, mips64el. Closes: #1026844, #387087 -- Regards, -- Bo YU signature.asc Description: PGP signature
