Re: Bug#980889: RFP: binutils-sh-elf -- cross binary utilities for SuperH bare-metal systems
Hi John! On 9/26/21 13:05, John Paul Adrian Glaubitz wrote: >> This package would provide GNU Binutils suited for embedded targets, and >> would be suited for both SH-1 and SH-2 hardware at least [1]. This is needed >> to build carl9170, the libre wireless firmware for AR9170 devices that's >> currently in firmware-linux-free. That will require GCC and Newlib as well. > > I'm Debian's sh4 maintainer and I would be willing to sponsor this provided > that Matthias is fine with a separate binutils package. I had a look at the package and it throws a number of lintian errors. Are you planning to address these or are they common for all binutils-$ARCH-elf packages we currently have in Debian? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Debian's branches and release model
On Jo, 21 oct 21, 13:00:09, Sam Hartman wrote: > Simon> However, the problem with freezing testing but not freezing > Simon> unstable is that if you do that, all updates to testing > Simon> during the freeze (to fix the release-critical bugs that stop > Simon> it from already being ready for release) have to go into > Simon> testing via testing-proposed-updates, which approximately > Simon> nobody uses. > > Have we ever looked into getting more people to use TPU so it's a viable > path? An idea would be to use[1] and promote it as security support for testing, also outside the freeze, e.g. for the cases where a security relevant update via unstable would take more than one day or so to migrate. This reminds me of this proposal: https://lists.debian.org/debian-devel/2011/05/msg00275.html As far as I recall it also had the codename "bob" (after RollerBob), but I can't find the reference right now. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Bug#980889: RFP: binutils-sh-elf -- cross binary utilities for SuperH bare-metal systems
On Fri, 2021-10-22 at 11:18 +0200, John Paul Adrian Glaubitz wrote: > I had a look at the package and it throws a number of lintian errors. Are you > planning to address these or are they common for all binutils-$ARCH-elf > packages > we currently have in Debian? I believe you're referring to debian-rules-missing-required-target and debian-rules-missing-recommended-target. In this case, Lintian seems to not recognize that I'm using Debhelper via the .DEFAULT target in the Makefile. I've filed a Lintian bug for this (#983539). If it's really bothersome, I could switch debian/rules from .DEFAULT: dh $@ to %: dh $@ but I personally prefer the former as a stylistic choice, and this would cover up an area where Lintian should be smarter. As for debian-rules-sets-DH_COMPAT, which is merely a warning, Lintian has this to say: > As of debhelper version 4, the DH_COMPAT environment variable is only > to be used for temporarily overriding debian/compat. Any line in > debian/rules that sets it globally should be deleted and a separate > debian/compat file created if needed. I don't set DH_COMPAT globally; I use it as a temporary override for dh_auto_configure, and my source comments explain why I do this. I would consider filing a Lintian bug, and still would if you'd like me to, but frankly I'd like to keep the warning around as a reminder that we should drop this hack when we're able. signature.asc Description: This is a digitally signed message part
gbp import-orig upstream lz file
Hi, I`m working on one of my packages and I had problems. First I did run: gbp import-dscs --debsnap bruteforce-luks Everything works well. Now I want to import a new upstream version. Upstream now provides a lz file and signs this lz. When I try to import using: gbp import-orig ../bruteforce-luks-1.4.0.tar.lz or gbp import-orig url-for-same-file gbp is creating a tar.gz and I have a problem with the signature. How is the right way to solve this problem? Thanks. []'s kretcheu :x
Re: gbp import-orig upstream lz file
On Fri, Oct 22, 2021 at 08:14:34AM -0300, kretcheu wrote: > Hi, > > I`m working on one of my packages and I had problems. > > First I did run: > > gbp import-dscs --debsnap bruteforce-luks > > Everything works well. > > Now I want to import a new upstream version. > Upstream now provides a lz file and signs this lz. > > When I try to import using: > gbp import-orig ../bruteforce-luks-1.4.0.tar.lz > or > gbp import-orig url-for-same-file > > gbp is creating a tar.gz and I have a problem with the signature. > > How is the right way to solve this problem? You can't have an orig.tar.lz in any case, this is not related to gbp or sigs, the only think you should do is to ask the tools to repack it to .xz, not to .gz. -- WBR, wRAR signature.asc Description: PGP signature
Bug#997043: ITP: python-pytest-toolbox -- useful plugins for pytest
Package: wnpp Severity: wishlist Owner: Michael Fladischer X-Debbugs-Cc: debian-devel@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-pytest-toolbox Version : 0.4 Upstream Author : Samuel Colvin * URL : https://github.com/samuelcolvin/pytest-toolbox * License : Expat Programming Lang: Python Description : useful plugins for pytest Numerous useful plugins for pytest like fixtures, methods and comparison objects. I intend to maintain this package as part of the DPT. -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmFzKTYRHGZsYWRpQGRl Ymlhbi5vcmcACgkQ/9PIi5l90Wq6SAgAvz2X/aId04AcsBpC4aQdVB0BwY6HPghA 2f0Zk7bdx9MA8vB9AtHWpHcrNjOIZJBhCv91zTfbZ3VVwbB9eormXw6yl+YPPB8h SXOOcXJDVt1iz6Dy/HOFKEEd2dROWw9XtlJ4j1ttIR+bvJlULNxmUDgNCbdAZcsE gdOH3fYtcGxJ/Uxkphoicd6gGHDw68t8y3tY6UJ7RtqUy9KmfP+vt+n3+aqFDIGZ uLy14sQ6ZteSXlPHNjEuPvQvujDeaWjNgXOl6UPFxAg3YLMKs/Dve8qAq3OPwaWz r1YdiiwYml2V30cXKoMvhrmBkmlEwU2z8PQHV2rfulqPVKSof6bW4A== =hPTV -END PGP SIGNATURE-
