Bug#1006872: RFH: apparmor -- user-space parser utility for AppArmor
Hi Andrej, Andrej Shadura (2022-03-07): > This reminded me I promised to work on dh-apparmor. I should find > time for that, Great! > maybe also for apparmor itself. Sounds good. Please keep me updated as you think about it :)
Bug#1006958: RFP: pytype -- Pytype checks and infers types for your Python code
Package: wnpp
Severity: wishlist
* Package name: pytype
Version : 2022.3.8
Upstream Author : Google
* URL : https://google.github.io/pytype/
* License : Apache, with some code with BSD and MIT
Programming Lang: Python
Description : Pytype checks and infers types for your Python code
Pytype checks and infers types for your Python code - without
requiring type annotations. Pytype can:
* Lint plain Python code, flagging common mistakes such as misspelled
attribute names, incorrect function calls, and much more, even
across file boundaries.
* Enforce user-provided type annotations. While annotations are
optional for pytype, it will check and apply them where present.
* Generate type annotations in standalone files ("pyi files"), which
can be merged back into the Python source with a provided merge-pyi
tool.
Pytype is a static analyzer; it does not execute the code it runs on.
It seems like a great help in Python development. It has a different
approach than mypy, and would complement it quite nicely.
Bug#1006963: ITP: python-mbstrdecoder -- multi-byte character string decoder
Package: wnpp Severity: wishlist Owner: Thomas Goirand X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: python-mbstrdecoder Version : 1.1.0 Upstream Author : Tsuyoshi Hombashi * URL : https://github.com/thombashi/mbstrdecoder * License : Expat Programming Lang: Python Description : multi-byte character string decoder Mbstrdecoder is a Python library for multi-byte character string decoder. Note: This is a new indirect dependency for Cloudkitty (OpenStack rating).
Bug#1006964: ITP: python-typepy -- library for variable type checker/validator/converter at a run time
Package: wnpp Severity: wishlist Owner: Thomas Goirand X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: python-typepy Version : 1.3.0 Upstream Author : Tsuyoshi Hombashi * URL : https://github.com/thombashi/typepy * License : Expat Programming Lang: Python Description : library for variable type checker/validator/converter at a run time Typepy is a Python library for variable type checker/validator/converter at a run time. . Feature: * checking a value type * validate a value for a type * convert a value from a type to the other type Note: this is a new indirect dependency for Cloudkitty.
Bug#1006965: ITP: python-datetimerange -- library that handles time ranges
Package: wnpp Severity: wishlist Owner: Thomas Goirand X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: python-datetimerange Version : 1.2.0 Upstream Author : Tsuyoshi Hombashi * URL : https://github.com/thombashi/DateTimeRange * License : Expat Programming Lang: Python Description : library that handles time ranges DateTimeRange is a Python library to handle a time range. e.g. check whether a time is within the time range, get the intersection of time ranges, truncating a time range, iterate through a time range, and so forth. Note: This is a new (direct) dependency of OpenStack Rating (cloudkitty).
Bug#1006967: ITP: pcapy-ng -- Python module for the pcap packet capture library
Package: wnpp * Package name : pcapy-ng * Upstream Author : Miroslav Stampar * License : Apache * Homepage : https://github.com/stamparm/pcapy-ng (the following is copied from the website, not the actual package description to be used) Pcapy-NG is a Python extension module that enables software written in Python to access the routines from the pcap packet capture library. It is a replacement of Pcapy, which is not maintained any more and stopped working altogether on Python3.10 (Issue). >From libpcap's documentation: "Libpcap is a system-independent interface for user-level packet capture. Libpcap provides a portable framework for low-level network monitoring. Applications include network statistics collection, security monitoring, network debugging, etc." Regards, Daniel
Processed: ITP: pcapy-ng -- Python module for the pcap packet capture library
Processing commands for cont...@bugs.debian.org: > owner 1006967 daniel.baum...@progress-linux.org Bug #1006967 [wnpp] ITP: pcapy-ng -- Python module for the pcap packet capture library Owner recorded as daniel.baum...@progress-linux.org. > End of message, stopping processing here. Please contact me if you need assistance. -- 1006967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006972: ITP: node-tad -- Javascript test suite with minimal hassle
Package: wnpp Severity: wishlist Owner: Yadd X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: node-tad Version : 3.1.0 Upstream Author : Mariusz Nowak * URL : https://github.com/medikoo/tad * License : ISC Programming Lang: JavaScript Description : Javascript test suite with minimal hassle TAD is a Javascript test suite that allow writing tests with minimal hassle. It locates test file and provide tested module for test functions. There are already many JS test suites in Debian, however test files are not compatible. This test suite is required to enable test, at least, for: node-es5-ext, node-es6-iterator, node-es6-map, node-es6-set, node-es6-symbol, node-es6-weak-map and node-event-emitter. Package will be maintained under JS Team umbrella.
Processed: Bug#1006972 marked as pending in node-tad
Processing control commands: > tag -1 pending Bug #1006972 [wnpp] ITP: node-tad -- Javascript test suite with minimal hassle Added tag(s) pending. -- 1006972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Blocked by r-cran-jinjar (waiting in new queue)
Processing control commands: > block -1 by 1005377 Bug #1006380 [src:r-cran-tidyr, src:r-cran-emayili] r-cran-tidyr breaks r-cran-emayili autopkgtest: Input must be a vector, not a object. 1006380 was not blocked by any bugs. 1006380 was not blocking any bugs. Added blocking bug(s) of 1006380: 1005377 -- 1006380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006977: ITP: open-plc-tools -- Toolkit for powerline network adapters with Atheros chipsets
Package: wnpp Severity: wishlist Owner: Mark Hindley * Package name: open-plc-tools Version : 0.0.6 Upstream Author : Qualcomm Atheros, Inc. * URL : https://github.com/qca/open-plc-utils * License : Clear BSD Programming Lang: C Description : Toolkit for powerline network adapters with Atheros chipsets Includes tools for manipulation and modification of pib and nvm files as well as tools to upload/flash them to the adapter chipset.
Bug#1006621: ITP: boofcv -- Real-time computer vision library
Based on Dima's comments. Is there any reason we can't just use the Gradle Wrapper? That way each project can use the version of Gradle it works with instead of single version for all projects. The only reason I see to not use Gradle wrapper is because it will download its dependencies and maybe for some reason that's not allowed. BoofCV does have a complex build system because it auto generates code. So you would need to download the jars the auto generate system needs then build a few classes. Now you're ready to create all the code you need for this library. At this point, you can in theory javac the entire project as Dima suggested. Assuming we don't care about mirroring the jar files that are published on Maven central. This would be equivalent of making one large .so instead of 15 little .so. If the end goal is some of the tools included with BoofCV (e.g. calibration and batch scanning of 2d barcodes) into Debian then that's perfectly fine. My preference is using gradle wrapper since that's the least amount of effort for me to do and it's easy to mangle the existing build system. Peter: if I do the build as described in the instructions, using the > "gradlew" commands, and I grep the log for "javac", would that give me > the bulk of the commands that are needed? What else is needed other than > the "javac" commands? > Hmm been a while since I've used javac directly. Probably the easiest way would be to get a file list using "find" and seeing if it blows up when you give it several hundred files or so. - Peter P.S. I'm going to be a bit erratic when I reply for the next couple of weeks at least. -- "Now, now my good man, this is no time for making enemies."— Voltaire (1694-1778), on his deathbed in response to a priest asking that he renounce Satan.
