[18582] in athena10
Re: Moving to salsa.debian.org/debian
daemon@ATHENA.MIT.EDU (Andreas Tille)
Tue Sep 9 10:13:53 2025
Date: Tue, 9 Sep 2025 16:13:44 +0200
From: Andreas Tille <tille@debian.org>
To: Alex Chernyakhovsky <achernya@mit.edu>
Cc: Sam Hartman <hartmans@debian.org>,
Salvaging Team <team+salvage@tracker.debian.org>, debathena@mit.edu,
1098197@bugs.debian.org
Message-ID: <aMA2GFqSYIlm9ygR@an3as.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAB18ysoe71r==fpy90vwPwV2P74H6TR+z8mWk4EJR9GErZKAVg@mail.gmail.com>
Hi Alex
Am Tue, Sep 09, 2025 at 09:02:17AM -0400 schrieb Alex Chernyakhovsky:
> After Karl passed away, Zephyr was transitioned to a Github "team" at
> https://github.com/zephyr-im/zephyr.
That's good to know.
> There is a debian/ directory in this repository, but as Sam identified
> in earlier messages, I do believe it has diverged from what's in
> Debian upstream. I don't recall how much, but I suppose it is fixable,
> from past memory.
I guess this is easily fixable - most preferably by some new release
tag on the Github project. Even if there might be no massive code
changes, tagging a "new" release might show that the development is
somehow continued there. Currently the latest release there is 3.1.2
which is identical to the release at the original location.
> To that end, if we need a new Maintainer, I (as achernya@debian.org)
> am happy to do it -- although having it be team-maintained with the
> other DDs and DMs who are knowledgeable would be better.
I'd volunteer to do the migration to Salsa, upgrade the packaging
stuff to recent standards and just leave the upstream work to you.
Given that the development is not super active the maintenance
burden in Debian might be low (and my help is granted).
> Zephyr
> traffic has reduced in the recent years, but MIT does still run
> Zephyr, and does still use the upstream packages for clients, so I
> think we should include it for now.
>
> As to GitHub vs Salsa: I recognize that Salsa is the preferred Debian
> way to do it, but we'd really need to stop carrying a debian/
> directory in upstream if we want to go to Salsa. Karl being upstream
> and also a DD led to it being included, and of course, later led to
> the divergence.
So in short these are the needed action items:
me:
- Replace Maintainer Karl Ramm <kcr@debian.org> by
Alexander Chernyakhovsky <achernya@debian.org>
- Migrate the packaging to https://salsa.debian.org/debian/zephyr
- Modernise packaging
you:
- Tag new release (without debian/ dir)
me:
- Import new release
- Can do a team upload if you want me to do so
Thanks a lot for your cooperation
Andreas.
> On Tue, Sep 9, 2025 at 8:50 AM Sam Hartman <hartmans@debian.org> wrote:
> >
> > >>>>> "Andreas" == Andreas Tille <tille@debian.org> writes:
> >
> > Andreas> Hi Sam, I'd offer to fix RC bugs and do a QA upload while
> > Andreas> the packaging can be maintained on Salsa in Debian/ team.
> >
> > As the closest thing to a maintainer, I will not stand in your way; if
> > you want to do that, go for it with no delays.
> > I'd ask you to consider whether that's really an efficient use of your
> > time though if we're just going to drop Zephyr.
> >
> > Zephyr has been effectively unmaintained upstream since Karl's death,
> > and I think that while the servers probably still run at MIT and a few
> > other places, Zephyr traffic has died off significantly.
> >
> > Unless I'm wrong and someone steps forward and says they want to invest
> > time, your effort might be better spent removing Zephyr as a dependency.
>
--
https://fam-tille.de
