[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: What was



Yeah, I'm happy enough to take this one on for a longer term, I'm already on the list for libax25 and ax25-tools, amongst other packet things, so it probably makes sense to bring them all together and have a single person to make and implement coherent decisions on them.

DH

-- 
  Hibby
  MM0RFN


On Sat, 6 Feb 2021, at 9:07 PM, Paul R. Tagliamonte wrote:
Great start!

You're right about the lintian issues -- but they all look straightforward. Let me know if you'd like any help/advice on ones that aren't clear. They all look like straight forward / tractable ones. I'm sure you'll clean it right up :)

We don't need to salvage - this was RoM'd. I wouldn't even add the original maintainer back -- but it may be worth an email to them to ask if they'd like to join maintenance, and if they would like to, we can re-add them.

I'd also make a note in the Changelog and d/copyright file outlining what we know from bugs #662055 and #630894, explaining the situation and including the emails where applicable. This is going to invite some extra scrutiny to ensure that we aren't in a legally murky place.

Nice work! This is great progress. I see you have yourself down as a maintainer -- am I able to assume you're OK being 'on the hook' for this package long-term?


   Paul KC3NWJ





On Sat, Feb 6, 2021 at 3:54 PM Hibby <d@vehibberd.com> wrote:
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


Hibby
MM3ZRZ

On 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

-- 
  Hibby
  MM0RFN


On 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 package
that's introduced that just atrophies. I'm willing to sponsor / review package
work, but I would feel a lot better (as would Myon and the rest of us) if someone
was able to give us a firm "Yes, we will care and feed for this package, and
if 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 sooner
rather than later.

If that's OK, I'm willing to get down to review/upload work with both of y'all
If you're worried about time commitments, we can always do this more
cautiously and introduce this into Bullseye via backports.

   Paul KC3NWJ



On 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

— 
Hibby
MM0RFN

On 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 Ranch

I 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



--
:wq


Reply to: