Bug#966254: ITP: libtest-hexdifferences-perl -- module for testing binary data as hexadecimal strings
Package: wnpp Owner: gregor herrmann Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org * Package name: libtest-hexdifferences-perl Version : 1.001 Upstream Author : Steffen Winkler * URL : https://metacpan.org/release/Test-HexDifferences * License : Artistic or GPL-1+ Programming Lang: Perl Description : module for testing binary data as hexadecimal strings The Test::HexDifferences module provides tests to convert binary data to hexadecimal strings and compare them. It is also possible to specify a format for the expected binary. The package will be maintained under the umbrella of the Debian Perl Group. -- Generated with the help of dpt-gen-itp(1) from pkg-perl-tools. signature.asc Description: Digital Signature
Re: IPv6-only buildds and AI_ADDRCONFIG
Niko Tyni wrote... > somewhat recently new official buildds were added with IPv6-only > connectivity. I'm not aware of an announcement, but I noticed this > with #962019, where src:perl suddenly failed to build due to test suite > failures. Thanks for catching this - I had seen one of my packages build-failing on some archs due to this, but had no idea what is going on. Quite frankly, I'm somewhat uneasy about introducing such a major change in the buildd infrastructure without some testing and MBF in advance. Which is what you did then. > # unshare -n > # ip li set lo up > # ip dev add dummy0 type dummy FWIW, "ip *link* add dummy0 type dummy" was needed with my version of iproute. > # ip li set dummy0 up > > FWIW, while the amount of breakage does not seem massive, I think the > numbers indicate that it might be good at least not to build the stable > suites on these IPv6-only buildds. I'm not sure what the plan is there. Also I am somewhat concerned what will happen when removing the e AI_ADDRCONFIG hint flag usaged. But I will have to find out. Christoph signature.asc Description: PGP signature
Bug#966284: ITP: project-el -- Emacs library for operations on the current project
Package: wnpp Severity: wishlist Owner: Sean Whitton * Package name: project-el Version : 0.5.0 Upstream Author : The GNU Project * URL : http://elpa.gnu.org/packages/project.html * License : GPL-3+ Programming Lang: Emacs Lisp Description : Emacs library for operations on the current project This Emacs Lisp library is the new generic API for operations on the current project which will be included in Emacs 27 (hence the otherwise unacceptably generic name). I am packaging this separately because project.el is developing quickly, and we will want to have newer versions available in Debian than the one which will be included in the as-yet-unreleased Emacs 27 -- which is already out-of-date. We have separate packaging like this for several other things which are bundled with Emacs, such as Org-mode and seq.el. -- Sean Whitton signature.asc Description: PGP signature
Re: Bug#965151: /usr/bin/tx: transifex-client and afdko shipping binaries under the same name
Hi, On Mon, Jul 20, 2020 at 03:05:26AM +, Paul Wise wrote: > Probably making all the commands in the afdko package subcommands of a > new afdko command would be the way to go (similar to how git uses > subcommands). Worked this around in 3.5.0+dfsg1-1 upload, by supplying a wrapper script `afdko`, and moving all the binaries into /usr/libexec/afdko/ . If a font needs afdko to build one need to put /usr/libexec/afdko/ into their PATH. Yao Wei signature.asc Description: PGP signature
Re: Bug#965151: /usr/bin/tx: transifex-client and afdko shipping binaries under the same name
On Sun, Jul 26, 2020 at 4:03 AM Yao Wei wrote: > Worked this around in 3.5.0+dfsg1-1 upload, by supplying a wrapper > script `afdko`, and moving all the binaries into /usr/libexec/afdko/ . > > If a font needs afdko to build one need to put /usr/libexec/afdko/ into > their PATH. This sort of thing needs to happen upstream first. -- bye, pabs https://wiki.debian.org/PaulWise
