Hey all,Update on this - It’s now on salsa at [1].I’ve pulled the upstream source, our existing debian debian release from the snapshots and brought it together. I’ve generated a diff of the two, and included this as a patch.
I’ve rewritten debian/rules and patched a variety of things to get it to the point of building successfully.I’ve changed the maintainer to the team and added the previous maintainer as an uploader - regardless of this, do we need to go through the salvaging process?
Lintian is still spitting out plenty of issues and I’ve got a todo list with plenty entries, but it’s a positive start. First up is to convert the copyright to dep5, and add details that clear the bug mentioned previously, and from there we’ll see how clean it can become.Cheers,DH
[1] https://salsa.debian.org/debian-hamradio-team/ax25dspy—HibbyMM3ZRZOn 5 Feb 2021, at 21:57, Dave Hibberd <d@vehibberd.com> wrote:I'm definitely happy to bring things to standards and keep them there before next release.I'll get the existing debian package on salsa this weekend, see if I can get it back inline with upstream and pull it inline with current standards, it shouldn't take long and I'm already doing it with fbb.Once we're there, we can make a call about putting into Testing or Stable++/Backports :)DH--HibbyMM0RFNOn Fri, 5 Feb 2021, at 7:34 PM, Paul Tagliamonte wrote:Great!Yeah, as Myon said, I think the thing we all want to avoid is another packagethat's introduced that just atrophies. I'm willing to sponsor / review packagework, but I would feel a lot better (as would Myon and the rest of us) if someonewas able to give us a firm "Yes, we will care and feed for this package, andif I need to shed that commitment, I'll do it responsibly without just ghosting"We're up close to the freeze line here, so we should figure that out soonerrather than later.If that's OK, I'm willing to get down to review/upload work with both of y'allIf you're worried about time commitments, we can always do this morecautiously and introduce this into Bullseye via backports.Paul KC3NWJOn Fri, Feb 5, 2021 at 2:13 PM Dave Hibberd <d@vehibberd.com> wrote:Hi all,I’m quite willing to take on the bulk of the ax25 packaging work, I’ve always been actively playing with this stuff anyway. Once we’ve got bullseye out the way we can look at spreading the load, probably.I’m not a dd, that had to get put on hold after some health issues a few years back, but I’m sure if one of the team will sponsor uploads until I get back into that application process :).DH—HibbyMM0RFNOn 5 Feb 2021, at 17:54, David Ranch <debian-hams@trinnet.net> wrote:Hey Christoph,
I can try to come up to speed and become a maintainer but I can't imagine I get all the access, learn the ropes, and get this done by the Bullseye freeze. I wonder if some other Debian Ham maintainer would be willing to try here before the freeze?
--David
KI6ZHD
On 02/05/2021 08:43 AM, Christoph Berg wrote:Re: David RanchI know the Bullseye freeze is quickly coming up but would it be possible to pull in this ax25spyd package? I can confirm the previous debian packaged version (link below) builds, packages, and runs fine on Ubuntu 20.04. I'm using it with the new Linpac release and the benefit here is that users don't have to run linpac as root or play SUID root tricks with axlisten to get everything working. On 01/02/2021 09:14 PM, Paul Tagliamonte wrote:Actually, upon further reading on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630894 this may have been resolved? It may only need a motivated maintainer.Hi David, as Paul said, the package needs an actual maintainer. I've done some drive-by uploads on other packages for the freeze, but for introducing new packages, we should really have someone interested in the matter. Christoph--:wq