Bug#905127: ITP: python-freetype -- Python bindings for the FreeType library
Package: wnpp Severity: wishlist Owner: Bastian Germann Version 2.0.0 is out and I would like to package it. It would be my first Debian package. According to the Debian Mentor's FAQ I would have to upload a package version and then file a RFS.
Bug#649623: ITP: python-freetype -- Python bindings for the FreeType library
retitle 649623 ITP: python-freetype -- Python bindings for the FreeType library
Bug#867348: Sponsoring gambas3
Dear Gianfranco, as you offered to sponsor someone who is interested in maintaining gambas3, I would like to do it. I recently brought the package in shape to allow a current version to be packaged (https://salsa.debian.org/gambas-team/gambas3/merge_requests/1) and jredrejo integrated my changes. I am also the one responsible for the mentioned upstream commit. As gambas3 is not in wnpp, I did not ask the current uploaders to adopt the package as that is considered impolite. But I just saw your post and would be glad to take on the responsibility. If you like to sponsor me, please add bage-guest to the Salsa project's members and tell me what would be the next step. Should I upload a build somewhere and you upload it to the package archive? Cheers, Bastian
Bug#867951: liferea: Uses deprecated gir1.2-gnomekeyring-1.0
The upstream was ported to libsecret and the forwarded bug closed.
Bug#887565: ITP: retitle 887565 ITP: python-vlc -- Python bindings for VLC
I am currently working on the package at https://salsa.debian.org/python-team/modules/python-vlc
Bug#887565: RFS: python-vlc/3.0.102-1 [ITP]
Hi, I am looking for a sponsor for my package "python-vlc" * Package name: python-vlc Version : 3.0.102-1 Upstream Author : Olivier Aubert * URL : http://wiki.videolan.org/PythonBinding * License : LGPL-2.1+ Section : python It builds those binary packages: python3-vlc - VLC Python bindings To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-vlc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-vlc/python-vlc_3.0.102-1.dsc Regards, Bastian Germann
Bug#910881: python3-dbus: Please provide the dist files
Package: python3-dbus Version: 1.2.8-2+b1 Severity: wishlist Dear Maintainer, The Python dist files are not installed. If you install a package via pip that setup_requires dbus-python pip will try to install the package from PyPI even though it is already installed. Please include the dist files in the package. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.18.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-dbus depends on: ii libc6 2.27-6 ii libdbus-1-3 1.12.10-1 ii libglib2.0-0 2.58.1-2 ii python3 3.6.6-1 Versions of packages python3-dbus recommends: ii python3-gi 3.30.1-1 Versions of packages python3-dbus suggests: pn python-dbus-doc pn python3-dbus-dbg -- no debconf information
Bug#910881: python3-dbus: Please provide the dist files
Exactly; the dbus_python.egg-info directory. They are supposed to be installed in the dist-packages directory (next to the dbus directory). Am 13.10.18 um 13:00 schrieb Simon McVittie: > On Fri, 12 Oct 2018 at 19:06:34 +0200, Bastian Germann wrote: >> The Python dist files are not installed. > > What exactly are "dist files"? Are they the contents of the > dbus_python.egg-info/ directory, or something else? > > Where are they meant to be installed? Next to the dbus/ directory? > > Thanks, > smcv >
Bug#910992: RFS: python-vlc/3.0.4106-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-vlc" * Package name: python-vlc Version : 3.0.4106-1 Upstream Author : Olivier Aubert * URL : http://wiki.videolan.org/PythonBinding * License : LGPL-2.1+ Section : python It builds those binary packages: python3-vlc - VLC Python bindings To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-vlc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-vlc/python-vlc_3.0.4106-1.dsc Regards, Bastian Germann
Bug#890200: PyQt5 package should provide an egg-info
I changed the package to include the files as described.
Bug#892929: gambas3: Crashes upon start. [20] Bad Argument. Settings.WriteWindow.388
Package: gambas3 Version: 3.11.4-1 Are you still experiencing the bug with version 3.11.4-1?
Bug#890200: PyQt5 package should provide an egg-info
There is no installed.txt file but a RECORD file which should not be
provided in this use case anyway.
>From the PEP: "The install command also provides an option to prevent
the RECORD file from being written and this option should be used when
creating system packages."
So there is no file list to be provided. The other dist-info files
(METADATA, INSTALLER) should be in python{,3}-pyqt5.
Bug#887565: RFS: python-vlc/3.0.102-1 [ITP]
Thanks for coming back to me. I changed the package according to your suggestions.
Bug#887565: RFS: python-vlc/3.0.102-1 [ITP]
Oh yes, I missed that. I just added the copyright notice.
Bug#858382: gambas3: No documentation
Does downloading and using the offline help still not work for you with 3.11.4?
Bug#909790: RFS: freetype-py/2.0.0.post6-1 [ITP]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "freetype-py". I submitted this RFS to the debian-python list a while ago but it did not get any attention. Therefore I submit it here. * Package name: freetype-py Version : 2.0.0.post6-1 Upstream Author : Nicolas P. Rougier * URL : https://github.com/rougier/freetype-py * License : BSD Section : python It builds those binary packages: python-freetype - Freetype Python bindings python3-freetype - Freetype Python bindings for Python 3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/freetype-py Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/freetype-py/freetype- py_2.0.0.post6-1.dsc Regards, Bastian Germann -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.18.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#877783: spyne: Please provide python3-spyne
With version 2.13.2-alpha spyne is compatible with Python 3, so upstream no longer blocks this issue. It would be great to have python3-spyne available in buster.
Bug#649623: RFS: freetype-py/2.0.0.post6-1 [ITP]
Hi, I am looking for a sponsor for my package "freetype-py". * Package name: freetype-py Version : 2.0.0.post6-1 Upstream Author : Nicolas P. Rougier * URL : https://github.com/rougier/freetype-py * License : BSD Section : python It builds those binary packages: python-freetype - Freetype Python bindings python3-freetype - Freetype Python bindings for Python 3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/freetype-py Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/freetype-py/freetype-py_2.0.0.post6-1.dsc Regards, Bastian Germann
Bug#923582: New active fork
Package: suds Version: 0.7~git20150727.94664dd-5 Severity: wishlist Tags: upstream There is a new active fork available at https://github.com/suds-community/suds. Please consider switching to the suds-community version because suds-jurko is not maintained anymore (https://bitbucket.org/jurko/suds/issues/117/please-release-new-version).
Bug#819490: debmirror: SHA256 validating of debian-installer files
Package: debmirror Please have a look at https://salsa.debian.org/debian/debmirror/merge_requests/4 for a fix of this issue.
Bug#819490: debmirror: SHA256 validating of debian-installer files
Package: debmirror Tags: patch
Bug#924337: Please reenable mqtt and varnish
Source: collectd Version: 5.8.1-1.2 Severity: important The mqtt and varnish plugins are disabled because of dependency issues. The blocking bugs #911265, #911266, and #879471 are resolved. Please reenable the plugins.
Bug#892929: Still bad packaging still broken
Piccoro, you explained at a later state that the issue was solved upstream, so I guessed for the current gambas3 testing version this issue should be fixed. You did not explain anything for the testing version. So if you still experience the described issue for your testing install, I am willing to work on this. But I cannot reproduce the issue using the testing gambas3-ide package. I am going to close this as fixed if nobody is confirming the issue for the testing version. A note here: Installing the PPA version and then, without uninstalling it, installing gambas3-ide is not supported. (Piccoro mentioned this approach in another issue)
Bug#858382: the documentations does not work unless we install all the gamba packages
Installing gambas3 from PPA and then Debian packages is not a common use case. If you do so, you are on your own and cannot expect support. Please try to stick to the issue's topic. I will not try to have a different approach to documentation in Debian than upstream. If anybody wants to improve the situation, I am happy to take patches and even post them upstream if you do not know how to do that yourselves. So, my question rephrased: When you install the current testing gambas3-ide package (currently version 3.12.2-1), does downloading the offline documentation work without installing any additional packages? If not, which packages do you need to install on top?
Bug#922401: Fix how format on load & save option is taken into account.
Why do you think the severity is so important that it needs to be backported? My understanding is that the full text search is buggy but the IDE can be executed and used generally. It is not a show stopper. The better thing to do would be asking upstream if they want to do a minor 3.12.3 release.
Bug#877783: spyne: Please provide python3-spyne
I uploaded a source package of the current version to https://mentors.debian.net/package/spyne You can download it via dget -x https://mentors.debian.net/debian/pool/main/s/spyne/spyne_2.13.4a0-1.dsc
Bug#929968: linux: Missing C_CAN module
Source: linux Severity: normal Dear Maintainer, All Debian kernel configurations are missing the C_CAN drivers. This device is available on TI am335x chips, which run, e.g., BeagleBone Black. It would be great to have at least the armmp flavour set the following configuration options: CONFIG_CAN_C_CAN=m CONFIG_CAN_C_CAN_PLATFORM=m
Bug#930230: ITP: junitparser -- Pythonic JUnit/xUnit Result XML Parser
Package: wnpp Severity: wishlist Package name: junitparser Version : 1.3.2 Upstream Author : Joel Wang URL : https://github.com/gastlygem/junitparser License : Apache-2.0 Section : python Description : Manipulates JUnit/xUnit Result XML files junitparser is a JUnit/xUnit result XML Parser. Use it to parse and manipulate existing result XML files, or create new JUnit/xUnit result XMLs from scratch. There are already two python packages in Debian that can create JUnit/xUnit result XML files but there does not seem to be any that can parse them to a domain specific object model.
Bug#930274: RFS: junitparser/1.3.2-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "junitparser". * Package name: junitparser Version : 1.3.2-1 Upstream Author : Joel Wang * URL : https://github.com/gastlygem/junitparser * License : Apache-2.0 Section : python It builds those binary packages: python3-junitparser - Manipulates JUnit/xUnit Result XML files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/junitparser Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/j/junitparser/junitparser_1.3.2-1.dsc junitparser is a JUnit/xUnit result XML Parser. It can parse and manipulate existing result XML files, or create new JUnit/xUnit result XMLs from scratch. There are already two python packages in Debian that can create JUnit/xUnit result XML files but there does not seem to be any that can parse them to a domain specific object model. More information about junitparser can be obtained from https://github.com/gastlygem/junitparser. Regards, Bastian Germann
Bug#928733: RFS: pysword/0.2.6-1 [ITP]
Package: sponsorship-requests Severity: wishlist Hi, I am looking for a sponsor for my package "pysword" * Package name: pysword Version : 0.2.6-1 Upstream Author : Tomas Groth * URL : https://gitlab.com/tgc-dk/pysword/ * License : Expat Section : python It builds those binary packages: python3-pysword - A Python library for reading SWORD Bibles If it is sponsored the Debian package openlp will depend on python3-pysword in its next major version. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pysword Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pysword/pysword_0.2.6-1.dsc More information about pysword can be obtained from: https://gitlab.com/tgc-dk/pysword/ Regards, Bastian Germann
Bug#928394: RFS: freetype-py/2.1.0.post1-1 [ITP]
Hi Dmitry,
I have changed that and also made the smoke test run.
Cheers,
Bastian
Am 09.05.19 um 09:35 schrieb Dmitry Bogatov:
> [2019-05-06 01:31] Bastian Germann
>
>> Thanks for coming back to me. I have fixed the things you pointed out.
>
> In debian/rules you write ${DEB_VERSION_UPSTREAM} -- note "{", not "(".
> Make uses $(foo) syntax for variable access. Build still successfull,
> but, well, please double check this moment.
>
> Also, you have no autopkgtest. I heard, default one for python could be
> added with following in "debian/control".
>
> Testsuite: autopkgtest-pkg-python
>
Bug#821461: RFS: pysword -- A Python library for reading SWORD Bibles [ITP]
Hi, I am looking for a sponsor for my package "pysword" * Package name: pysword Version : 0.2.6-1 Upstream Author : Tomas Groth * URL : https://gitlab.com/tgc-dk/pysword/ * License : Expat Section : python It builds those binary packages: python3-pysword - A Python library for reading SWORD Bibles If it is sponsored the Debian package openlp will depend on python3-pysword in its next major version. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pysword Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pysword/pysword_0.2.6-1.dsc More information about pysword can be obtained from: https://gitlab.com/tgc-dk/pysword/ Regards, Bastian Germann
Bug#928394: RFS: freetype-py/2.1.0.post1-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "freetype-py". This closes a very long-standing wnpp issue. I posted an earlier version last September but got no attention so far. * Package name: freetype-py Version : 2.1.0.post1-1 Upstream Author : Nicolas P. Rougier * URL : https://github.com/rougier/freetype-py * License : BSD Section : python It builds those binary packages: python3-freetype - Freetype Python bindings for Python 3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/freetype-py Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/f/freetype-py/freetype-py_2.1.0.post1-1.dsc Regards, Bastian Germann
Bug#928394: RFS: freetype-py/2.1.0.post1-1 [ITP]
Thanks for coming back to me. I have fixed the things you pointed out. >> python3-freetype - Freetype Python bindings for Python 3 > > Here what I found interesting: > > * Lintian complains about "font-in-non-font-package" and >"font-outside-font-dir". Why do you ship .ttf font in examples >directory? > > * Policy is slightly outdated. > > * In debian rules, instead of "cat PKG-INFO | sed ..." you can use >$DEB_VERSION_UPSTREAM. See /usr/share/dpkg/pkg-info.mk. By the way, >it is useless-use-of-cat. > > * You can use B-D: debhelper-compat (= 11). Why not 12, by the way?
Bug#930274: RFS: junitparser/1.3.2-1 [ITP]
Hi Herbert, Thanks for coming back to me. I uploaded a new version with the suggested changes. > # lintian-info -t 'tag' > > - upstream-metadata-file-is-missing > >It is pedantic. There are info here to fix that: >Refer to https://dep-team.pages.debian.net/deps/dep12/ and >https://wiki.debian.org/UpstreamMetadata for details. I have included a metadata file. > - debian-watch-does-not-check-gpg-signature > >There is gpg signature. Ignore. > > - library-package-name-for-application usr/bin/junitparser >application-in-library-section python usr/bin/junitparser > >Junitparser README.rst file shows how to use it as a module and >by command line. The command 'tree debian/python3-junitparser' >shows the module and the command line script. The manpage is >the README.rst file. > >Please split the package (one depends on other): > >- python3-junitparser is the module >- junitparser is the 'utils' (in Section) > >The README.rst file. The command line part can be the manpage. >The rest can be a documentation in '/usr/share' Okay. I have included the README.rst in python3-junitparser and moved the binary and its edited manpage to the package junitparser. > The package does not build twice because junitparser.egg-info dir > is not removed between builds. Please override dh_clean to do that. I used the debian/clean file for that. > There is no 'debian/tests/control' file. No CI. Please see to how > run upstream tests by autopkgtest. > > https://ci.debian.net/ I already had a "Testsuite: autopkgtest-pkg-python" line in d/control. I guess this is also picked up by ci.debian.net. If not, what should I put into debian/tests/control to run the same tests there? Cheers, Bastian
Bug#935894: linux: buster-backports version
Source: linux Severity: wishlist Dear Maintainers, would it be possible to get the bullseye kernel into buster-backports? I would very much appreciate that. Regards, Bastian
Bug#911821: Add development packages
Please find a packaged development package in https://salsa.debian.org/debian/mtd-utils/merge_requests/1
Bug#939598: [PATCH] Conflict with u-boot-tools (Closes: #939598)
Signed-off-by: Bastian Germann
---
debian/control | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/control b/debian/control
index 27015bb..87db86a 100644
--- a/debian/control
+++ b/debian/control
@@ -42,6 +42,7 @@ Architecture: any
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}, libubootenv0.1 (=
${binary:Version})
Multi-Arch: foreign
+Conflicts: u-boot-tools
Description: Library to access U-Boot environment - tool
libubootenv is a library that provides a hardware independent way to access
to U-Boot environment. U-Boot has its default environment compiled
--
2.23.0
Bug#907041: ITP: swupdate - Pulled from the NEW queue
Hi, The package was in the NEW queue but does not appear there anymore. Do you still plan to get it into Debian? Cheers, Bastian Germann
Bug#716414: ubiupdatevol: Prevent null pointer dereference
You can find a patch posted to upstream at http://lists.infradead.org/pipermail/linux-mtd/2019-September/091479.html
Bug#940879: Link with libedit instead of readline5
Package: mariadb-10.3 Severity: wishlist The readline5 library is old and got orphaned with #737301. MariaDB supports linking with libedit as a replacement, so please use that library.
Bug#932379: Duplicate
This is a duplicate of #932112.
Bug#922214: libpng12-0: libpng12.so.0 can not be installed, file or directory not found
You can use version 1.2.49-3 which is the last version that does not add the conflicting symbolic links.
Bug#929968: Add missing C_CAN module
Package: linux Tags: patch I have merge requested a fix for this issu. https://salsa.debian.org/kernel-team/linux/merge_requests/153
Bug#944625: Please package next PyMuPDF compatible version
Package: mupdf Version: 1.15.0+ds1-1 Severity: normal The new pymupdf package depends on the .a in libmupdf-dev. It does not build currently because 1.14.16-1 needs a mupdf 1.14.x. Unfortunately, upstream PyMuPDF did not publish any version compatible with 1.15.x but there are 1.16.x versions available. Please update mupdf to the current 1.16.1 version, which would enable the pymupdf package to actually build in sid. Your patches 8-10 are upstream now, some other patches will need a refresh.
Bug#877783: spyne_2.13.11a0-0.1_source.changes REJECTED
Am Di., 17. Dez. 2019 um 00:52 Uhr schrieb Russell Stuart : > > On Mon, 2019-12-16 at 19:19 +0100, Bastian Germann wrote: > > Yes, I missed that. But maybe you have made up your mind now that > > spyne got auto-removed from testing. > > Isn't it better to have an alpha version in testing than no version > > at all? > > As I said in my reply to the bug report, the "no version at all" > scenario seems unlikely to me even if Spyne for Python 3 doesn't get The "unlikely scenario" is reality NOW. Maybe you did not check but spyne is already gone in testing. That is what I wanted to draw your attention at. > released. But it does seem like Spyne for Python 3 will be stable > before the bullseye deadlines hit. And I will upload it as soon as an I > am aware it has been released. > > Regardless of what happens I use spyne in my day job, so I will > continue to package spyne for Debian. Whether it ends up in Debian is > an open question, but I am a DD :)
Bug#938554: spyne_2.13.11a0-0.1_source.changes REJECTED
Am Sa., 7. Dez. 2019 um 02:45 Uhr schrieb Russell Stuart : > Perhaps you missed it as I only replied to the Debian bug, but I am not > OK with an alpha version ending up in testing: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877783#30 > > If you still want to do this upload the alpha version to experimental. > If you do proceed any with uploading the alpha version to unstable I > will replace it with the old version. Yes, I missed that. But maybe you have made up your mind now that spyne got auto-removed from testing. Isn't it better to have an alpha version in testing than no version at all?
Bug#946551: Enable TI PHY for 5.x kernels
Package: linux Version: 5.3.9-3 Severity: normal The armmp Linux configuration had CONFIG_TI_CPSW_PHY_SEL enabled to be built in the kernel up to including the buster kernel version. As this config was deprecated with 5.1, it was removed from Debian's configuration. With the 5.x versions comes the successor CONFIG_PHY_TI_GMII_SEL enabled as a module. This just hit me updating a BeagleBone Black (that does not load any modules) from buster to testing. I have created a merge request with CONFIG_PHY_TI_GMII_SEL=y for armmp: https://salsa.debian.org/kernel-team/linux/merge_requests/194
Bug#945874: RFS: spyne/2.13.11a0-0.1 [NMU, RC] -- Python library for writing and calling soap web service
Package: sponsorship-requests Severity: important Hi, I am looking for a sponsor for the package "spyne" which has a py2removal RC bug and will be autoremoved on December 13th. The package is Python 2 only but the current alpha version has Python 3 support. I uploaded a Python 3 compatible package in January and referenced it in #877783 but did not get any response from the maintainer. Now that the bug is RC I think that it is time for a NMU and hope to find a sponsor for the package. * Package name: spyne Version : 2.13.11a0-0.1 Upstream Author : Burak Arslan * URL : http://spyne.io/ * License : LGPL-2.1+ Section : python It builds those binary packages: python3-spyne - Python library for writing and calling soap web service To access further information about this package, please visit the following URL: https://mentors.debian.net/package/spyne Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/spyne/spyne_2.13.11a0-0.1.dsc Changes since the last upload: * Non-maintainer upload. * d/watch: Also search alpha versions * New upstream version: 2.13.11a0 * Upgrade to Python 3 (Closes: #938554) * Make package lintian clean * Build-depend on the test dependencies * Correct d/copyright Regards, Bastian Germann
Bug#947174: RFS: gambas3/3.14.2-1 -- Complete visual development environment for Gambas
gambas3-gb-ncurses - Gambas NCurses component gambas3-gb-complex - Gambas Complex component gambas3-gb-data - Gambas abstract datatypes component gambas3-gb-mime - Gambas MIME message management gambas3-gb-httpd - Gambas HTTP server gambas3-gb-memcached - Gambas memcached client gambas3-gb-args - Gambas arguments parser gambas3-gb-map - Gambas online map viewer gambas3-gb-jit - Gambas Just-In-Time compiler component gambas3-gb-media - Gambas media component gambas3-gb-media-form - Gambas media player controls gambas3-gb-logging - Gambas logging system component gambas3-gb-form-terminal - Gambas terminal form component gambas3-gb-term - Terminal manager for Gambas gambas3-gb-term-form - Gambas GUI terminal form component gambas3-gb-gui-trayicon - transitional package To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gambas3 Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gambas3/gambas3_3.14.2-1.dsc Changes since the last upload: * Set Standards-Version to 4.4.1 * Add Uploader: Bastian Germann * New upstream version 3.14.2 * gb.openssl: GPL-2+ with OpenSSL exception * Remove patches * Add new package gambas3-gb-form-print * Depend on non-transitional libncurses * Add patch to exclude pq_fprintf def * Add lintian overrides * Change gambas3-runtime's section * Rules-Requires-Root: no (lintian fix) Regards, Bastian
Bug#911821: Additional merge request for headers
The development packages will be useful only with https://salsa.debian.org/debian/mtd-utils/merge_requests/5 Else, they would demand a private kernel header being installed.
Bug#952399: OpenSSL linking without license exception
Am 25.02.20 um 23:38 schrieb Marco d'Itri: > Control: found 26+20191223-1 > > On Feb 23, Bastian Germann wrote: > >> All of the GPL-2+ licensed executables contained in the kmod >> binary package link to libcrypto even though they do not have any >> OpenSSL license exception. ftp-master considers this a serious >> issue. So please remove this optional dependency or ask upstream >> for a license exception. > The large number of contributors to kmod obviously makes impossible > getting a license exception, also considering that only Debian > cares about linking GPL'ed software with OpenSSL. > > Since only libkmod (which is LGPL'ed), and not the actual commands, > is linked with OpenSSL, and the libkmod symbols do not change > depending if OpenSSL support is enabled or not, and the patches > which introduced OpenSSL support did not touch the commands, then I > think that the commands are obviously not a derivative work of > OpenSSL. You can also easily verify that the commands are not > linked with OpenSSL by looking at the build logs of the package. $ ldd /bin/*mod /sbin/*mod* /bin/kmod: libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /bin/lsmod: libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /sbin/depmod libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /sbin/insmod: libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1/sbin/lsmod: libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1/sbin/modinfo: libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /sbin/modprobe: libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /sbin/rmmod: libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 buster's amd64 binaries are actually directly linked with libcrypto; readelf says "(NEEDED) Shared library: [libcrypto.so.1.1]" Even if they were linked with libcrypto via libkmod it would not make any difference. > Also, the next major release of OpenSSL will be relicensed with the > ASLv2 anyway, which is compatible with the GPLv3. That will help for bullseye+ but not for buster. > For these reasons I have no interest and no plans to do anything > about this, and I am quite annoyed that I had to spend my time > researching these details and then explaining them to you. You don't care and I am fine with that since I am not the maintainer of the package. But I wanted to report the issue anyway since the legal team's comments on that matter are unanimous.
Bug#952781: ITP: python-libconf -- Reader/writer for the libconfig format
Package: wnpp Severity: wishlist * Package name: python-libconf Upstream Author : Christian Aichinger * License : Expat Description : Reader/writer for the libconfig format libconf is a pure-Python reader/writer for configuration files in libconfig format, which is often used in C/C++ projects. Its interface is similar to the json module.
Bug#952657: Document OpenSSL linking exception
Package: libqt5network5 Severity: normal This package links to libssl. An OpenSSL linking exception is included in src/network/doc/src/qtnetwork.qdoc and files in src/network/ssl but it is not documented in debian/copyright. Please include it there. Please also have a look at #924937. libqt5network5 has many GPL licensed reverse dependencies, similar to libpq5, some of which do not have this exception. Please consider configuring with -openssl-runtime because that would make this issue less important for these reverse dependencies Then one could install them without libssl, which would not make them a derivative work of OpenSSL.
Bug#952399: OpenSSL linking without license exception
A side note: The OpenSSL related kmod feature was implemented by Yauheni Kaliuta. Yauheni also posted a version based on GnuTLS (LGPL): https://patchwork.kernel.org/patch/10688685/ Having this available as a variant and using it instead would solve this problem.
Bug#940879: Link with libedit instead of readline5
https://salsa.debian.org/mariadb-team/mariadb-10.4/-/merge_requests/3
Bug#952805: Document OpenSSL linking exception
Package: kopete Severity: normal This package has an OpenSSL linking exception in COPYING. This is not documented in debian/copyright. Please document it there.
Bug#952868: OpenSSL linking without license exception
Package: wesnoth Severity: serious This GPL2 package links with OpenSSL. The OpenSSL license is incompatible with the GPL (see https://ftp-master.debian.org/REJECT-FAQ.html). This can be solved by asking upstream to add a license exception or by linking with wolfSSL instead. You can find a patch enclosed (untested). From f15f10434ef5fbdc9cf2eeea15e7ca057c0f6e63 Mon Sep 17 00:00:00 2001 From: Bastian Germann Date: Sun, 1 Mar 2020 11:19:53 +0100 Subject: [PATCH] Replace OpenSSL with wolfSSL --- debian/control | 2 +- debian/patches/01wolfssl-crypto | 14 ++ debian/patches/series | 1 + debian/rules| 2 +- 4 files changed, 17 insertions(+), 2 deletions(-) create mode 100644 debian/patches/01wolfssl-crypto diff --git a/debian/control b/debian/control index 5e35ef9b..1d650a07 100644 --- a/debian/control +++ b/debian/control @@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11~), libsdl2-image-dev (>= 2.0.0), libboost-iostreams-dev, libboost-test-dev, libboost-regex-dev, libboost-serialization-dev, libboost-system-dev, libboost-thread-dev, libboost-program-options-dev, libboost-filesystem-dev, libboost-locale-dev, - libboost-random-dev, libpng-dev, libreadline-dev, libssl-dev, + libboost-random-dev, libpng-dev, libreadline-dev, libwolfssl-dev, libpango1.0-dev, libvorbis-dev, cmake (>= 2.6) Standards-Version: 4.1.4 Uploaders: Rhonda D'Vine , diff --git a/debian/patches/01wolfssl-crypto b/debian/patches/01wolfssl-crypto new file mode 100644 index ..ad55d158 --- /dev/null +++ b/debian/patches/01wolfssl-crypto @@ -0,0 +1,14 @@ +Author: Bastian Germann vim:ft=diff: +Description: Link with wolfssl instead of libcrypto. + +--- a/cmake/FindCrypto.cmake b/cmake/FindCrypto.cmake +@@ -2,7 +2,7 @@ + + find_path(CRYPTO_INCLUDE_DIR openssl/md5.h) + +-find_library(CRYPTO_LIBRARY crypto) ++find_library(CRYPTO_LIBRARY wolfssl) + + # handle the QUIETLY and REQUIRED arguments and set XXX_FOUND to TRUE if all listed variables are TRUE + INCLUDE(FindPackageHandleStandardArgs) diff --git a/debian/patches/series b/debian/patches/series index 57b6465e..8014e9fd 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1,2 +1,3 @@ +01wolfssl-crypto 02wesnoth-nolog-desktop-file 03wesnothd-name diff --git a/debian/rules b/debian/rules index 02ad4071..cbec12c1 100755 --- a/debian/rules +++ b/debian/rules @@ -23,7 +23,7 @@ ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel)) CXXFLAGSDBG = -g1 endif -export CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS) +export CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS) -I/usr/include/wolfssl -DOPENSSL_ALL export CFLAGS := $(shell dpkg-buildflags --get CFLAGS) $(CPPFLAGS) -std=c++11 -fopenmp export CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS) $(CPPFLAGS) -std=c++11 -fopenmp $(CXXFLAGSDBG) export LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS) -- 2.25.1
Bug#952657: Document OpenSSL linking exception
Am 27.02.20 um 06:48 schrieb Pino Toscano: > In data mercoledì 26 febbraio 2020 23:40:52 CET, Bastian Germann ha > scritto: >> Package: libqt5network5 Severity: normal >> >> This package links to libssl. > > No, it does not. > > ... > > QtNetwork can be built to link against OpenSSL, and we built it to > dlopen it instead, exactly for the reasons mentioned. The > dependency of the libqt5network5 package is added with a trivial > test program at build time, so installing libqt5network5 pulls the > OpenSSL library it was built against (easier to track & rebuild on > OpenSSL SONAME bumps). > You are right. Sorry about that. Adding the license exception in debian/copyright would still benefit reverse dependent GPL packages that want to add a dependency on OpenSSL themselves and have to look this up in the source otherwise.
Bug#953247: RFS: python-libconf/2.0.1-1 [ITP] -- Reader/writer for the libconfig format
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "python-libconf". * Package name: python-libconf Version : 2.0.1-1 Upstream Author : Christian Aichinger * URL : https://github.com/Grk0/python-libconf * License : Expat * Vcs : https://salsa.debian.org/python-team/modules/python-libconf Section : python It builds those binary packages: python3-libconf - Reader/writer for the libconfig format (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-libconf Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-libconf/python-libconf_2.0.1-1.dsc Changes since the last upload: * Initial release (Closes: #952781) Regards, Bastian Germann
Bug#950772: Patch: swupdate: FTBFS during separate arch/indep builds
When you take a closer look, please also consider my changes in #911821 (mtd-utils).
Bug#953006: Switch to current libreadline
Package: dbacl Severity: normal The package is not bound by license to build against the old libreadline5. It can also use the current GPL-3 libreadline.
Bug#950187: MuJS
Package: wnpp Severity: wishlist * Package name: mujs Version : 1.0.6 Upstream Author : Tor Andersson * URL : https://mujs.com/ * License : ISC Programming Lang: C Description : A Lightweight, embeddable JavaScript interpreter MuJS should be added to the archive because the mupdf package includes this as a vendored dependency: #949636. There are some MuJS-related CVEs that are all tagged "NOT-FOR-US: MuJS" even though they might be applicable for the mupdf package. MuJS was designed with a focus on small size, correctness, and simplicity. It is written in portable C and implements ECMAScript as specified by ECMA-262. The interface for binding with native code is designed to be as simple as possible to use, and is very similar to Lua. There is no need to interact with byzantine C++ template mechanisms, or worry about marking and unmarking garbage collection roots, or wrestle with obscure build systems.
Bug#950665: RFS: mujs/1.0.6-1 [ITP] -- Lightweight JavaScript interpreter
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "mujs". It is currently vendored in the mupdf package and deserves to be a package on its own. The mpv package might as well be interested in it because it is an optional dependency. * Package name: mujs Version : 1.0.6-1 Upstream Author : Tor Andersson * URL : https://mujs.com/ * License : ISC * Vcs : None Section : javascript It builds those binary packages: libmujs-dev - Lightweight JavaScript interpreter (development package) libmujs1 - Lightweight JavaScript interpreter library mujs - Lightweight JavaScript interpreter To access further information about this package, please visit the following URL: https://mentors.debian.net/package/mujs Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mujs/mujs_1.0.6-1.dsc Changes since the last upload: * Initial release (Closes: #950187) Regards, Bastian Germann
Bug#949821: RFS: pysword/0.2.7-2 -- native Python reader module for the SWORD Project
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pysword" to enable migration to testing. * Package name : pysword Version: 0.2.7-2 Upstream Author: sec...@tgc.dk * URL: https://gitlab.com/tgc-dk/pysword * License: Expat * Vcs: https://salsa.debian.org/python-team/modules/pysword Section: python It builds those binary packages: python3-pysword - native Python reader module for the SWORD Project To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pysword Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pysword/pysword_0.2.7-2.dsc Changes since the last upload: * Remove test leftover include-binaries * Change license for debian/* to upstream license * Don't pristine-tar on gbp * Fix rules-requires-root-missing * Fix upstream-metadata-file-is-missing Regards, Bastian Germann
Bug#950772: Patch: swupdate: FTBFS during separate arch/indep builds
Hi, I have created a merge request at https://salsa.debian.org/debian/swupdate/merge_requests/2 which fixes the issue. Please consider merging and uploading to sid. Regards, Bastian
Bug#951730: OpenSSL linking without license exception
Package: argyll Severity: serious This package links to OpenSSL even though it does not have any license exception for it. ftp-master considers this a serious issue. I can build fine without libssl, so please remove this dependency.
Bug#951729: argyll should use axtls package
Package: argyll Severity: normal argyll vendors axtls which is available as a package in Debian now. Please move to ths package.
Bug#951743: OpenSSL linking without license exception
Package: calibre Severity: serious This package links to OpenSSL even though it does not have any license exception for it. ftp-master considers this a serious issue. Please build without the certgen extension or try to build with an OpenSSL API compatible library like wolfssl.
Bug#951756: Document OpenSSL license exception
Package: calibre Severity: normal This package has an OpenSSL license exception in LICENSE.OPENSSL. This is not documented in debian/copyright. Please document it there.
Bug#951757: Document OpenSSL license exception
Package: ettercap Severity: normal This package has an OpenSSL license exception in LICENSE.OPENSSL. This is not documented in debian/copyright. Please document it there.
Bug#923582: New active fork
I changed the git to the new upstream which is still active. This enabled dropping all patches because they are included in suds-community.
Bug#951782: Document OpenSSL license exception
Package: haproxy Severity: normal This package has an OpenSSL license exception in LICENSE. This is not documented in debian/copyright. Please document it there.
Bug#930752: Does OpenSSL linking pose a legal issue?
There might not only be a size issue with linking libcrypto but also a legal issue. ftp-master considers it a serious violation if a GPL program links with OpenSSL and does not contain a license exception. libkmod is LGPL licensed but in my understanding the same goes for LGPL. You should ask upstream to add a license exception and drop the libssl dependency as long as this is not resolved. An alternative would be using a different crypto library. I tried with libwolfssl which would also slightly decrease the size. It has an OpenSSL compatibility layer. Unfortunately the PKCS7_SIGNER_INFO related stuff is not available (see also https://github.com/wolfSSL/wolfssl/issues/2816).
Bug#930752: Does OpenSSL linking pose a legal issue?
Am 21.02.20 um 23:04 schrieb Marco d'Itri: > On Feb 21, Bastian Germann wrote: > >> There might not only be a size issue with linking libcrypto but also a >> legal issue. ftp-master considers it a serious violation if a GPL >> program links with OpenSSL and does not contain a license exception. >> libkmod is LGPL licensed but in my understanding the same goes for LGPL. > But you are wrong. > Okay, that is very convincing. For reference, I found support for your claim at https://lists.debian.org/debian-legal/2008/06/msg7.html. Off-topic: But the binary kmod package, which is GPL-2+ licensed, could be in violation linking with libcrypto.
Bug#951780: OpenSSL linking without license exception
Package: eurephia Severity: serious This package links to OpenSSL even though it does not have any license exception for it. ftp-master considers this a serious issue. Please replace libssl with a GPL compatible library. I successfully compiled with libwolfssl which has an OpenSSL API compatibility layer.
Bug#951861: OpenSSL linking without license exception
Package: ndpmon Severity: serious This package links to OpenSSL even though it does not have any license exception for it. ftp-master considers this a serious issue. Please replace libssl with a GPL compatible library. I successfully compiled with libwolfssl which has an OpenSSL API compatibility layer.
Bug#951854: OpenSSL linking without license exception
Package: muchsync Severity: serious This package links to OpenSSL even though it does not have any license exception for it. ftp-master considers this a serious issue. Please replace libssl with a GPL compatible library. I successfully compiled with libwolfssl which has an OpenSSL API compatibility layer. A patch is included. >From b7c366c5b06982fe94242780da844d5f9adaa497 Mon Sep 17 00:00:00 2001 From: Bastian Germann Date: Sat, 22 Feb 2020 12:21:16 +0100 Subject: [PATCH] Replace OpenSSL with wolfSSL diff --git a/debian/control b/debian/control index 05d60c4..b8b1523 100644 --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Source: muchsync Section: mail Priority: optional Maintainer: Rémi Vanicat -Build-Depends: debhelper (>=9), dh-autoreconf, pkg-config, libnotmuch-dev, libsqlite3-dev, libxapian-dev, libssl-dev +Build-Depends: debhelper (>=9), dh-autoreconf, pkg-config, libnotmuch-dev, libsqlite3-dev, libxapian-dev, libwolfssl-dev Standards-Version: 4.1.3 Homepage: http://www.muchsync.org/ diff --git a/debian/patches/link-with-wolfssl-instead-of-libcrypto.patch b/debian/patches/link-with-wolfssl-instead-of-libcrypto.patch new file mode 100644 index 000..da77d07 --- /dev/null +++ b/debian/patches/link-with-wolfssl-instead-of-libcrypto.patch @@ -0,0 +1,23 @@ +Subject: [PATCH] Link with wolfssl instead of libcrypto +From: Bastian Germann +Last-Update: 2020-02-22 + +muchsync is GPL-2+ licensed and incompatible with linking against OpenSSL. +Link with the drop-in replacement wolfSSL instead. +--- + configure.ac | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff -u a/configure.ac b/configure.ac +index 9533bff..5878ab1 100644 +--- a/configure.ac b/configure.ac +@@ -22,7 +22,7 @@ AC_CHECK_FUNCS(openat) + AC_CHECK_FUNCS(fdopendir) + + PKG_CHECK_MODULES([sqlite3], [sqlite3]) +-PKG_CHECK_MODULES([libcrypto], [libcrypto]) ++PKG_CHECK_MODULES([libcrypto], [wolfssl]) + + AC_PATH_PROG(XAPIAN_CONFIG, xapian-config) + test -n "$XAPIAN_CONFIG" || AC_MSG_ERROR(Cannot find xapian-config) diff --git a/debian/patches/series b/debian/patches/series index 4a97dfa..8b85707 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1 +1 @@ -# You must remove unused comment lines for the released package. +link-with-wolfssl-instead-of-libcrypto.patch diff --git a/debian/rules b/debian/rules index 16d6d38..6a05fac 100755 --- a/debian/rules +++ b/debian/rules @@ -1,5 +1,5 @@ #!/usr/bin/make -f -# You must remove unused comment lines for the released package. +export DEB_CPPFLAGS_MAINT_APPEND=-I/usr/include/wolfssl %: dh $@ --with autoreconf
Bug#951877: OpenSSL linking without license exception
Package: restbed Severity: serious This package links to OpenSSL even though it does not have any license exception for it. ftp-master considers this a serious issue. I can build fine without libssl, so please remove this dependency. If you want to keep it maybe you want to try building with wolfssl which has an OpenSSL compatibility library.
Bug#951911: OpenSSL linking without license exception
Package: librelp0 Severity: serious With the latest version, this package links to OpenSSL even though it does not have any license exception for it. ftp-master considers this a serious issue. As GnuTLS is enabled as well, please remove the libssl dependency.
Bug#951912: Document OpenSSL license exception
Package: libzdb Severity: normal This package has an OpenSSL license exception. This is not documented in debian/copyright. Please document it there.
Bug#951705: Do not link with OpenSSL: Upload?
Thanks for merging. When do you plan a 1.16.1 upload?
Bug#952399: OpenSSL linking without license exception
Package: kmod Version: 26-1 Severity: serious All of the GPL-2+ licensed executables contained in the kmod binary package link to libcrypto even though they do not have any OpenSSL license exception. ftp-master considers this a serious issue. So please remove this optional dependency or ask upstream for a license exception.
Bug#951369: RFS: sachesi/2.0.4+ds-1 [ITP] -- BlackBerry 10 device utility
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "sachesi" * Package name: sachesi Version : 2.0.4+ds-1 Upstream Author : https://github.com/xsacha/Sachesi/issues * URL : https://github.com/xsacha/Sachesi * License : GPL-3 Section : comm It builds those binary packages: sachesi - BlackBerry 10 device utility To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sachesi Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sachesi/sachesi_2.0.4+ds-1.dsc Changes since the last upload: * Initial release (Closes: #787482) Regards, Bastian Germann
Bug#951705: Do not link with OpenSSL
Package: mupdf Version: 1.15.0+ds1-1 Severity: serious mupdf is AGPL licensed and does not come with an OpenSSL linking exception. According to ftp-master this is a serious violation (https://ftp-master.debian.org/REJECT-FAQ.html). Not linking with libssl does not lead to any package errors and only slightly reduces the package's features. I removed it in https://salsa.debian.org/koster/mupdf/merge_requests/2
Bug#948673: version 2019.11
Package: src:swupdate Severity: normal The swupdate project has release the stable version 2019.11. I have prepared the necessary changes to the package information at https://salsa.debian.org/debian/swupdate/merge_requests/1 Please consider uploading 2019.11-1 to sid.
Bug#948783: gambas3: FTBFS: error: 'ABSTIMEOID' undeclared (first use in this function)
I fixed the problem upstream and have already prepared a package containing that upstream version: #947174. Unfortunately, it introduces a new binary package so that it has to pass throught NEW. As a DM I cannot upload it there myself but if you like you can do it.
Bug#948790: gambas3 ftbfs in unstable
duplicate of #948783
Bug#944625: Merge request: Package next PyMuPDF compatible version
I made all necessary changes to mupdf to build the current version: https://salsa.debian.org/koster/mupdf/merge_requests/2
Bug#949636: Please provide MuJS in extra source package
Package: mupdf Version: 1.15.0+ds1-1 Severity: normal MuJS is included in the mupdf sources in a thirdparty directory. It should be provided in a new package because it has a different upstream source.
Bug#911821: package upload with libmtd-dev/libubi-dev
The Merge request was accepted and adds the binary packages libmtd-dev and libubi-dev with static library archives only. This approach was taken because there are no *.so files generated in the build. Could you please upload a mtd-utils 1:2.1.1-2? With the new binary packages this will need to pass through the NEW queue.
Bug#946551: Enable TI PHY for 5.x kernels
I do not install any modules on that device intentionally. If you think that this is not supported by Debian, please close the bug.
Bug#702010: gtkglext: uses pangox which is going away
pangox was removed from gtkglext's git repository with the commit https://mail.gnome.org/archives/commits-list/2010-October/msg03446.html The old repository is gone but there is a gtk3 port which has the complete unchanged history, including that commit: https://github.com/tdz/gtkglext/commit/32f37c936691baa25cc463c5339d0754bbaed8dc Importing this version might be a way forward. It is not ABI compatible with 1.2.0 though.
Bug#948250: x11vnc on buster-backports
Package: x11vnc Version: 0.9.16-3 Severity: wishlist Can you please provide the current x11vnc version on buster-backports?
Bug#948335: New upstream
Package: golang-bindata Version: 3.0.7+git20151023.72.a0ff256-3 Severity: normal The jteeuwen/go-bindata repository is not maintained anymore, according to its README.md. Please switch to https://github.com/go-bindata/go-bindata
Bug#695875: Build with libedit rather than libreadline5
Please let the package build-depend on libedit-dev rather than the orphaned libreadline-gplv2-dev. It is supported by upstream and its license is compatible. The configure option --enable-readline=yes would have to be changed to --enable-editline=yes.
Bug#951877: Patch: OpenSSL linking without license exception
This patch builds the package without OpenSSL. >From 658cfaa87943e6423ee61fe078b93655b3f7fa70 Mon Sep 17 00:00:00 2001 From: Bastian Germann Date: Mon, 9 Mar 2020 12:32:07 +0100 Subject: [PATCH] Disable SSL (Closes: #951877) --- debian/control | 1 - debian/rules | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/debian/control b/debian/control index 0118f51..2e32fbd 100644 --- a/debian/control +++ b/debian/control @@ -5,7 +5,6 @@ Maintainer: Alexandre Viau Build-Depends: debhelper (>= 9), cmake, libasio-dev, - libssl-dev, libkashmir-dev Standards-Version: 3.9.8 Homepage: https://github.com/Corvusoft/restbed diff --git a/debian/rules b/debian/rules index 68961b3..7153ea5 100755 --- a/debian/rules +++ b/debian/rules @@ -13,7 +13,7 @@ override_dh_auto_configure: dh_auto_configure -- \ -DBUILD_TESTS=OFF \ -DBUILD_EXAMPLES=OFF \ - -DBUILD_SSL=ON \ + -DBUILD_SSL=OFF \ -DBUILD_SHARED=ON \ -DCMAKE_BUILD_TYPE=Release -- 2.20.1
Bug#949636: Merge request: Please provide MuJS in extra source package
Please find a merge request to use the new mujs package at https://salsa.debian.org/koster/mupdf/-/merge_requests/4
Bug#956123: ITP: kas -- Setup tool for bitbake based projects
Package: wnpp Severity: wishlist Owner: Bastian Germann * Package name: kas Version : 2.0 Upstream Author : Jan Kiszka * URL : https://github.com/siemens/kas * License : Expat Programming Lang: Python Description : Setup tool for bitbake based projects This tool provides an easy mechanism to setup bitbake based projects. The OpenEmbedded tooling support starts at step 2 with bitbake. The downloading of sources and then configuration has to be done by hand. Usually, this is explained in a README. Instead kas uses a project configuration file and makes use of it in download and configuration phases. Key features provided by the build tool: * clone and checkout bitbake layers * create default bitbake settings (machine, arch, ...) * launch minimal build environment, reducing risk of host contamination * initiate bitbake build process
Bug#956480: mpv: JavaScript backend MuJS available
Package: mpv Severity: wishlist mpv has a JavaScript backend with MuJS available which is documented in your package's man page. A mujs package is now available in Debian and you can build-depend on it to enable the feature.
