Bug#909408: ITP: fd-find -- Simple, fast and user-friendly alternative to find
Package: wnpp Severity: wishlist Owner: Rust Maintainers * Package name: fd-find * URL : https://github.com/sharkdp/fd * License : MIT or apache2 Programming Lang: Rust, what else ? ;) Description : Simple, fast and user-friendly alternative to find While it does not seek to mirror all of find's powerful functionality, fd provides sensible (opinionated) defaults for 80% of the use cases. Features: * Convenient syntax: ‘fd PATTERN’ instead of ‘find -iname '*PATTERN*'’. * Colorized terminal output (similar to ls). * It's fast, often faster than find. * Smart case. * Ignores hidden directories and files, by default. * Ignores patterns from your .gitignore, by default. * Regular expressions. * Unicode-awareness. * Parallel command execution with a syntax similar to GNU Parallel. Please note: the executable and the associated manpage were renamed from ‘fd’ to ‘fdfind’ because of a file name clash.
Bug#909411: ITP: gxemul -- machine emulator for multiple architectures
Package: wnpp Severity: wishlist Owner: Göran Weinholt * Package name: gxemul Version : 0.6.0.2 Upstream Author : Anders Gavare * URL : http://gavare.se/gxemul/ * License : BSD-3-Clause Programming Lang: C++ Description : machine emulator for multiple architectures GXemul aims at emulating complete machines with enough hardware emulated to run real unmodified operating systems. The emulation of these machine types is good enough to run a least one guest operating system: . ARM-based machines: * CATS (NetBSD/cats, OpenBSD/cats) * IQ80321 (NetBSD/evbarm) * NetWinder (NetBSD/netwinder) MIPS-based machines: * DECstation 5000/200 (NetBSD/pmax, OpenBSD/pmax, Ultrix, Linux/DECstation, Sprite) * Acer Pica-61 (NetBSD/arc) * NEC MobilePro 770, 780, 800, 880 (NetBSD/hpcmips) * Malta (NetBSD/evbmips) * Algorithmics P5064 (NetBSD/algor) * SGI O2 (aka IP32) (NetBSD/sgi) (enough for root-on-nfs) PowerPC-based machines: * IBM 6050/6070 (PReP, PowerPC Reference Platform) (NetBSD/prep) SuperH-based machines: * Sega Dreamcast (NetBSD/dreamcast) (enough for ramdisk userland) . Other machine types and architectures are emulated less completely. See the documentation in the gxemul-doc package for the exact details and guides to installing guest operating systems. I plan to maintain this package myself. It was previously packaged in Debian and removed due to bugs and an inactive upstream; upstream is now active again.
Bug#909429: ITP: osmo-sgsn -- Serving GPRS Support Node for Mobile Networks
Package: wnpp Severity: wishlist Owner: Ruben Undheim * Package name: osmo-sgsn Version : 1.3.0 Upstream Author : Osmocom * URL : https://osmocom.org/projects/osmosgsn/wiki/OsmoSGSN * License : AGPL-3 Programming Lang: C Description : Serving GPRS Support Node for Mobile Networks OsmoSGSN is the Serving GPRS Support Node: it handles signalling, i.e. attach/detach of subscribers and PDP contexts for data services. OsmoSGSN needs to reach the GGSN to establish GTP tunnels for subscribers. It must have a separate GTP IP address from OsmoGGSN, as mentioned before. It is needed for data support in the Osmocom mobile network infrastructure, and will be maintained in the Debian Mobcom team.
Bug#909432: ITP: python-djangosaml2 -- Django application that integrates PySAML2
Package: wnpp Severity: wishlist Owner: Michael Fladischer -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-djangosaml2 Version : 0.17.2 Upstream Author : Yaco Sistemas * URL : https://github.com/knaperek/djangosaml2/ * License : Apache-2.0 Programming Lang: Python Description : Django application that integrates PySAML2 djangosaml2 is a Django application that integrates the PySAML2 library into your project. This mean that you can protect your Django based project with a service provider based on PySAML. This way it will talk SAML2 with your Identity Provider allowing you to use this authentication mechanism. -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAlunu5MRHGZsYWRpQGRl Ymlhbi5vcmcACgkQ/9PIi5l90Wqcygf+J7OWQSVepkV3TyHhGXqgWXAm/SwB0kt6 OZhN8CMi5zSj3V/hiFATIlkL6BrUFkUUaYAlQImN4H/oq7kOK9JJPhprb2OZedtA 7OaUlhN3kHJxqYa6kEzx9K08DkzjKnsfMxYpUWPXdBjaduzQJreHtFbkkjXhpq5R Yo1gUGJDiOZ6YIfsqUbVMUWof8F+zn8Fr0iJ8Jpc7JU8bLQT/Nbr6V3S0A55v4/7 Ltr+mDdWyK8Bui3eK7HAC2zDmhxTt33z3yRb17P+moNAiM+La9xo/3k3k897Zs79 k0BEZ5F4W2r9fSDmB0E/xNcuKRDbt+mZdTDrVPy9UvH0aTQlJj5F0Q== =VlT0 -END PGP SIGNATURE-
Bumping epoch and reusing package name "elisa"
Dear fellow developers, I’m working on packaging Elisa, a modern and simple music player based on the KDE Frameworks stack. [0][1] I initially named the package elisa, but such a package already existed in the archive in the past. Former Elisa [2] was a media center and must have been in the archive as "elisa" before wheezy. It was then renamed to Moovida upstream and packaged as "moovida" for wheezy with "elisa" staying as a transitional dummy package. The moovida and elisa packages were last uploaded in July 2010 and then removed from the archive after wheezy. FTP masters rejected the upload of the new elisa 0.2.1-1 as the package has a lower version than the former Elisa project and they proposed bumping the epoch and reusing the name. It seems reasonable to me as it leaves us with 2 elisa-less Debian releases. Alternatives I can see would be to use different names like elisa-player or elisa-music-player but I find it cumbersome and it’s not my preferred option. Since policy §5.6.12 now recommends getting consensus on -devel before bumping epochs, I’m doing that here. [0] https://community.kde.org/Elisa [1] https://salsa.debian.org/qt-kde-team/extras/elisa [2] https://packages.debian.org/wheezy/elisa Cheers, -- Aurélien signature.asc Description: OpenPGP digital signature
Re: Bumping epoch and reusing package name "elisa"
Hello, On Sun 23 Sep 2018 at 10:53PM +0200, Aurélien COUDERC wrote: > Since policy §5.6.12 now recommends getting consensus on -devel before bumping > epochs, I’m doing that here. You're probably already aware of it, but just in case, please do not forget 3.2.2: 3.2.2 The part of the version number after the epoch must not be reused for a version of the package with different contents, even after the version of the package previously using that part of the version number is no longer present in any archive suites. 3.2.2 For non-native packages, the upstream version must not be reused for different upstream source code, so that for each source package name and upstream version number there exists exactly one original source archive contents. -- Sean Whitton signature.asc Description: PGP signature
Re: Bumping epoch and reusing package name "elisa"
Am 23.09.18 um 22:53 schrieb Aurélien COUDERC: > FTP masters rejected the upload of the new elisa 0.2.1-1 as the package has a > lower version than the former Elisa project 1.0.9+bzr1614-1.1 was the last version in the archive. Not knowing how mature the new elisa project is, strictly speaking this is a temporay issue until upstream has released a version >= 1.0.10. When do you expect such a v1 release to happen? If it's not too far away, you could use the +really notation for the time being. Another idea could be to inform upstream of this situation. Maybe they are willing to bump the version number from say 0.2 to 1.2 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
