Re: Temporary(?) bundling of code that may not warrant its own package
On Wed, May 20, 2020 at 09:54:56PM +0100, Wookey wrote: > I think that is ultimately up to you as the maintainer. If it's really > important to get the new version uploaded, then yeah do that first, > but otherwise just leave it at the current version, do the new > library, then upload new version when that gets out of NEW. Or maybe > decide that there is a time limit: you really should have the new > version uploaded within say 4 weeks. If NEW takes longer than that, > then upload the new-version-with-bundle at that point. If, for whatever reason, you feel urgency, the ftpmasters are very good at prioritizing your needs. There's just no information attached to packages normally -- you need to let them know. One way is popping up in #debian-ftp and whining. I've never had them refuse a request to speed up a review. A package stuck in NEW is stalling further work? Ask to prioritize. A package is job related and your manager wants it in? A derivative is about to freeze? A customer requested a backport? All of these are valid reasons. Otherwise, the package sits there with a lot of fonts, themes, pet packages. Ftpfolk are too busy to guess your needs on their own. Obviously, let's not abuse their kindness when not needed. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi ⠈⠳⣄
Re: Temporary(?) bundling of code that may not warrant its own package
Adam Borowski writes: > If, for whatever reason, you feel urgency, the ftpmasters are very good at > prioritizing your needs. There's just no information attached to packages > normally -- you need to let them know. One way is popping up in #debian-ftp > and whining. > > I've never had them refuse a request to speed up a review. A package stuck > in NEW is stalling further work? Ask to prioritize. A package is job > related and your manager wants it in? A derivative is about to freeze? A > customer requested a backport? All of these are valid reasons. I had no idea. I guess I'll try to ask them nicely. Thanks! -- Gard
Bug#961200: ITP: nfq -- The NFQUEUE based IDN/punicode DNS filter to mitigate homograph phishing attacks
Package: wnpp Severity: wishlist Owner: Joachim Bauernberger * Package name: nfq Version : 1.0.6 Upstream Author : Name * URL : https://gitlab.com/jbauernberger/nfq/ * License : GPLv3 Programming Lang: C Description : The NFQUEUE based IDN/punicode DNS filter to mitigate homograph phishing attacks NFQ is a DNS packet filter that interfaces with the libnetfilter_queue Linux kernel subsystem. It identifies any punicode domain names by matching the string "xn--" in DNS questions or answers. NFQ stops all homograph phishing attacks for lookalike domains. NFQ can run either directly on a Linux based workstation, and before your DNS cache and/or on a gateway. NFQ is not replacement for /etc/hosts: E.g. NFQ is not for blacklisting which would be a poor security guarantee for homograph attacks. Instead NFQ blocks all punicode domains by default and uses an (optional) whitelist to explicitly allow certain selected IDN domains which you know are safe. NFQ is for environments with strict anti-phishing policies. We assume: • you are using some kind of dnscache (e.g. djbdns, dnsmasq, unbound, etc ...) which then forwards any queries to an upstream DNS server (e.g. 8.8.8.8 or 1.1.1.1 etc), and ... • you have configured your browser to use your DNS cache instead of resolving directly via upstream reolver over DoH. (nfq works on the kernel queue so you can still use DoH for outgoing forwarded queries as part with dnsmasq or unbound etc ... nfq doesn't prevent you from using DoH) • you will be adding the iptables manually so that nfq can intercept packages, this is outside the scope of the nfq installer, see the README and examples how to do this.
Work-needing packages report for May 22, 2020
The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1188 (new: 2) Total number of packages offered up for adoption: 219 (new: 0) Total number of packages requested help for: 61 (new: 0) Please refer to https://www.debian.org/devel/wnpp/ for more information. The following packages have been orphaned: compton (#960779), orphaned 5 days ago Description: compositor for X11, based on xcompmgr Reverse Depends: compton-conf Installations reported by Popcon: 3117 Bug Report URL: https://bugs.debian.org/960779 emacs-jedi (#960922), orphaned 3 days ago Description: Python auto-completion for Emacs Reverse Depends: elpa-jedi Installations reported by Popcon: 57 Bug Report URL: https://bugs.debian.org/960922 1186 older packages have been omitted from this listing, see https://www.debian.org/devel/wnpp/orphaned for a complete list. No new packages have been given up for adoption, but a total of 219 packages are awaiting adoption. See https://www.debian.org/devel/wnpp/rfa_bypackage for a complete list. For the following packages help is requested: apache2 (#910917), requested 586 days ago Description: Apache HTTP Server Reverse Depends: apache2 apache2-ssl-dev apache2-suexec-custom apache2-suexec-pristine backuppc courier-webadmin cvsweb debbugs-web dms-wsgi doc-central (135 more omitted) Installations reported by Popcon: 96237 Bug Report URL: https://bugs.debian.org/910917 autopkgtest (#846328), requested 1268 days ago Description: automatic as-installed testing for Debian packages Reverse Depends: debci-worker Installations reported by Popcon: 1185 Bug Report URL: https://bugs.debian.org/846328 balsa (#642906), requested 3161 days ago Description: An e-mail client for GNOME Installations reported by Popcon: 695 Bug Report URL: https://bugs.debian.org/642906 broadcom-sta (#886599), requested 864 days ago (non-free) Description: Broadcom STA Wireless driver (non-free) Installations reported by Popcon: 1798 Bug Report URL: https://bugs.debian.org/886599 cargo (#860116), requested 1136 days ago Description: Rust package manager Reverse Depends: dh-cargo Installations reported by Popcon: 1672 Bug Report URL: https://bugs.debian.org/860116 clipit (#941081), requested 240 days ago Description: lightweight GTK+ clipboard manager Reverse Depends: lxqt Installations reported by Popcon: 10064 Bug Report URL: https://bugs.debian.org/941081 cyrus-imapd (#921717), requested 468 days ago Description: Cyrus mail system - IMAP support Reverse Depends: cyrus-admin cyrus-caldav cyrus-clients cyrus-dev cyrus-imapd cyrus-murder cyrus-nntpd cyrus-pop3d cyrus-replication Installations reported by Popcon: 434 Bug Report URL: https://bugs.debian.org/921717 cyrus-sasl2 (#799864), requested 1702 days ago Description: authentication abstraction library Reverse Depends: 389-ds-base adcli autofs-ldap cyrus-caldav cyrus-clients cyrus-common cyrus-dev cyrus-imapd cyrus-imspd cyrus-murder (78 more omitted) Installations reported by Popcon: 201968 Bug Report URL: https://bugs.debian.org/799864 dee (#831388), requested 1406 days ago Description: model to synchronize mutiple instances over DBus Reverse Depends: dee-tools gir1.2-dee-1.0 libdee-dev zeitgeist-core Installations reported by Popcon: 30162 Bug Report URL: https://bugs.debian.org/831388 developers-reference (#759995), requested 2091 days ago Description: guidelines and information for Debian developers Installations reported by Popcon: 6175 Bug Report URL: https://bugs.debian.org/759995 devscripts (#800413), requested 1696 days ago Description: scripts to make the life of a Debian Package maintainer easier Reverse Depends: apt-build apt-listdifferences aptfs arriero brz-debian buildd customdeb debci debian-builder debmake (33 more omitted) Installations reported by Popcon: 11779 Bug Report URL: https://bugs.debian.org/800413 docker.io (#908868), requested 614 days ago Description: Linux container runtime Reverse Depends: docker-clean golang-github-containers-buildah-dev golang-github-containers-image-dev golang-github-fsouza-go-dockerclient-dev golang-github-openshift-imagebuilder-dev golang-github-samalba-dockerclient-dev golang-github-tonistiigi-fsutil-dev subuser whalebuilder Installations reported by Popcon: 3535 Bug Report
Bug#961243: ITP: node-eventemitter3 -- High Performance Event Emitter For Node.js
Package: wnpp Severity: wishlist Owner: Harley Swick X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-eventemitter3 Version : 4.0.4 Upstream Author : Arnout Kazemier * URL : https://github.com/primus/eventemitter3#readme * License : Expat Programming Lang: JavaScript Description : FIX_ME write the Debian package description Description: A high performance eventemitter for Node.js It has been micro-optimized for various code paths making this, one of, if not the fastest EventEmitter available for Node.js and browsers. The module is API compatible with the EventEmitter that ships by default with Node.js but there are some slight differences. . It's a drop in replacement for existing EventEmitters, but just faster. Free performance, who wouldn't want that> The EventEmitter is written in EcmaScript 3 so it will work in the oldest browsers and node versions that you need to support. . I have most of the work done for the package, the only issue I've run into is with the tests. There is a dependency on assume, which has not been packaged yet.
Bug#896978: ITP: node-http-proxy -- High performance event emitter for Node.js
Package: wnpp
Severity: wishlist
Owner: Harley Swick
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-http-proxy
Version : 1.18.1
Upstream Author : Charlie Robbins
* URL : https://github.com/http-party/node-http-proxy#readme
* License : Expat
Programming Lang: JavaScript
Description : FIX_ME write the Debian package description
It is suitable for implementing components suhc as reverse proxies and load
balancers.
A new proxy is created by calling createProxyServer and passing an options
object as argument.
var httpProxy = require('http-proxy');
var proxy = httpProxy.createProxyServer(options);
.
This package is useful for Node.js web applications
that want to support websockets.
I plan to maintain this as part of the js-team, and am in need of a sponsor.
This is blocked by node-eventemitter3, which is in the process of being
packaged.
Work on the package can be found here:
https://salsa.debian.org/js-team/node-http-proxy
Re: Videoconference on Friday 2020-05-22 18:00 UTC (Was: For those who want to keep on contributing (Was: Debian @ COVID-19 Biohackathon (April 5-11, 2020)))
Hi, for those who would like to join our next videomeeting it will happen at https://www.timeanddate.com/worldclock/fixedtime.html?msg=Debian+CoViD-19+Biohackathon+Video+Conference&iso=20200522T20&p1=37&ah=1 in the Jitsi channel https://meet.jit.si/DebianMedCovid19 These weekly video meetings were started in the Debian Med Biohackathon[1]. The topic is what contributors have done in the past week and to coordinate the work for next week. Despite the one week of hackathon is over Covid-19 is not and there is a lot of remaining work to do. Newcomers are always welcome. See you Andreas. [1] https://lists.debian.org/debian-devel-announce/2020/03/msg00010.html -- http://fam-tille.de
Re: Bug#961029: Request for new mailing list: debian-ai
Control: retitle -1 Request for new mailing list: debian-ai Thanks for the various feedbacks. As pointed out by lamby, the "debian-mlhwaccl" may be quite hard to search. Meanwhile, the name can be overlength if we expand that abbreviation. So I'm proposing to use a new list name: debian-ai instead of the old: debian-mlhwaccl Name: debian-ai Short-Desc: Artificial Intelligence Software Development in Debian Long-Desc: Development of artificial intelligence software, such as machine learning, deep learning, compilers and hardware acceleration software stacks. The topics for this list may include any one of the following (but not limited): * Mahcine Learning: sklearn, xgboost, AutoML, ... * Deep Learning: tensorflow, pytorch, mxnet, cntk, ... * Computer Vision: opencv, skimage, ... * Computational Linguistics: nltk, spacy, ... * Hardware Acceleration: CUDA, ROCm, OpenCL, SYCL, SIMD * Compiler: LLVM (for MLIR, SPIR-V, SYCL), GCC (gcc-offload-nvptx) And sometimes the topics in this list may be complex intersections of the mentioned keywords. Category: development Subscription-Policy: open Post-Policy: open Web-Archive: yes
