Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #397506 > unrolled thread

Bug#1098197: Moving to salsa.debian.org/debian

Back to article view | Back to linux.debian.bugs.rc

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1098197: Moving to salsa.debian.org/debian Sam Hartman <hartmans@debian.org> - 2025-09-09 06:00 +0200
    Bug#1098197: Moving to salsa.debian.org/debian Sam Hartman <hartmans@debian.org> - 2025-09-09 15:00 +0200
      Bug#1098197: Moving to salsa.debian.org/debian "Alex Chernyakhovsky" <achernya@mit.edu> - 2025-09-09 15:10 +0200
        Bug#1098197: Moving to salsa.debian.org/debian "Alex Chernyakhovsky" <achernya@mit.edu> - 2025-09-11 04:00 +0200
          Bug#1098197: Moving to salsa.debian.org/debian Andreas Tille <tille@debian.org> - 2025-09-25 10:50 +0200

#397506 — Bug#1098197: Moving to salsa.debian.org/debian

[added debathena to distribution]

Karl died of cancer a few years ago.
I tried to find an efficient solution  for moving Zephyr forward.
The debathena community (roughly Zephyr's upstream to the extent it has
one)
was more interested in a complete solution than one we could adopt
quickly.
But the effort to produce that solution never materialized.
The issue is that VCS for Zephyr upstream and for the Debian packaging
in Zephyr upstream has diverged somewhat from what is in Debian.

I throw up my hands. I no longer have time/interest in Zephyr.
I'd ask  whether it still makes sense to include in Debian.
If zephyr gets dropped, some things like Cyrus would need a rebuild and
barnowl should probably be dropped entirely.

If someone from debathena actually does want to step up and maintain
Zephyr I'm happy to sponsor uploads at least until the person gets DM
bits (if they do not already have them).

>>>>> "Andreas" == Andreas Tille <tille@debian.org> writes:

    Andreas> Hi Sam and Karl, I realised that there were two uploads to
    Andreas> experimental with not so "experimental" changelog entries.
    Andreas> I'm specifically wondering about

    Andreas>  Date: Sat, 02 Oct 2021 20:15:00 -0600

    Andreas>  zephyr (3.1.2-2) experimental; urgency=medium .  * Upload
    Andreas> only to set new maintainer and get Zephyr off MIA's plate *
    Andreas> I'm still trying to find VCS for the Debian packaging
    Andreas> before making any real changes

    Andreas> I'd offer moving the package to Debian/ team on Salsa and
    Andreas> try to find some solution for bug #1098197 when doing so.

    Andreas> Kind regards Andreas.

    Andreas> -- https://fam-tille.de

[toc] | [next] | [standalone]

#397543

>>>>> "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.

[toc] | [prev] | [next] | [standalone]

#397545

I'm not sure if I should be replying with my MIT/Debathena hat or my
Debian hat or my "inherited Zephyr upstream team maintenance after
Karl passed away" hat ... so I guess this message is all 3, and I've
chosen my MIT From: address arbitrarily.

After Karl passed away, Zephyr was transitioned to a Github "team" at
https://github.com/zephyr-im/zephyr. I'm one of the folks in that
organization, so we're upstream. This is a git repository that
superseded Karl's old subversion repository, with a conversion that
Karl himself performed, IIRC.

Karl had been working on a Zephyr 3.1 release before he passed.
Unfortunately, there was some sort of memory corruption bug we
couldn't trace, that only appeared on a "heavily used" zephyrd such as
the MIT zephyr ATHENA.MIT.EDU realm. I still have on my TODO list to
one day get around to fixing it, but no amount of ASAN builds showed
anything wrong.

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.

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. 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.

Sincerely,
-Alex


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.

[toc] | [prev] | [next] | [standalone]

#397656

[Multipart message — attachments visible in raw view] — view raw

Hi Andreas,

I'm traveling for work without my Debian-capable laptop. I will do my best
to look at this on Friday when I get back.

Apologies for the delay on my end, and thank you for pushing on this.

Sincerely,
-Alex

On Wed, Sep 10, 2025, 12:15 PM Andreas Tille <tille@debian.org> wrote:

> Hi again,
>
> Am Tue, Sep 09, 2025 at 04:13:44PM +0200 schrieb Andreas Tille:
> > 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.
>
> I've opened issue #143 there pointing to a fix for the gcc-15 build.
> I also adopted PR #135 into the packaging on Salsa.
>
> > > 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.
>
> In addition to droping the debian/ dir I'd recommend accepting PR #135
> to make the build reproducible.  I'd also recommend to solve issue #143
> by the patches I recommended.
>
> I also contributed systemd service files.  I'm not an expert in these
> and would welcome review + testing.
>
> > > 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).
>
> That's actually done.  I've modernised the packaging, closed 7 bugs and
> confirm the current package passes Salsa CI[1].  I've worked down quite
> a list of lintian issues (some remaining once are left but are harmless)
>
> > 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
>
> Done.  Except for using short dh in d/rules.  I would prefer this
> but the current d/rules file is a bit complex so for the moment I
> did not do this conversion.
>
> >   you:
> >      - Tag new release (without debian/ dir)
> >
> >   me:
> >      - Import new release
> >      - Can do a team upload if you want me to do so
>
> I admit I'm motivated to do a Debian team upload right now since quite a
> number of bugs are fixed and hardening + reproducible builds are
> accomplished.  In any case I would welcome some review of the systemd
> service files if you might find some time to do so.
>
> Kind regards
>        Andreas.
>
>
> [1] https://salsa.debian.org/debian/zephyr/-/pipelines/933652
>
> --
> https://fam-tille.de
>

[toc] | [prev] | [next] | [standalone]

#399225

Hi again,

I see

  https://salsa.debian.org/debian/zephyr

in a releasable state.  I wonder whether you intend to do some changes
or whether you are OK if I do a team upload.  For the moment was running

  $ tagpending
  tagpending info: tagging these bugs pending: 1101738 1030080 1029195 1049994 759885 1098197 1039433

and I'll wait for your confirmation another week.

Kind regards
   Andreas.

Am Thu, Sep 11, 2025 at 09:23:43AM +0200 schrieb Andreas Tille:
> Hi Alex,
> 
> Am Wed, Sep 10, 2025 at 09:55:45PM -0400 schrieb Alex Chernyakhovsky:
> > I'm traveling for work without my Debian-capable laptop. I will do my best
> > to look at this on Friday when I get back.
> 
> Safe travels! ;-)
> ... and just take your time.
>  
> > Apologies for the delay on my end, and thank you for pushing on this.
> 
> No need to apologise and you are perfectly welcome.
> 
> Kind regards
>    Andreas.
>  
> > On Wed, Sep 10, 2025, 12:15 PM Andreas Tille <tille@debian.org> wrote:
> > 
> > > Hi again,
> > >
> > > Am Tue, Sep 09, 2025 at 04:13:44PM +0200 schrieb Andreas Tille:
> > > > 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.
> > >
> > > I've opened issue #143 there pointing to a fix for the gcc-15 build.
> > > I also adopted PR #135 into the packaging on Salsa.
> > >
> > > > > 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.
> > >
> > > In addition to droping the debian/ dir I'd recommend accepting PR #135
> > > to make the build reproducible.  I'd also recommend to solve issue #143
> > > by the patches I recommended.
> > >
> > > I also contributed systemd service files.  I'm not an expert in these
> > > and would welcome review + testing.
> > >
> > > > > 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).
> > >
> > > That's actually done.  I've modernised the packaging, closed 7 bugs and
> > > confirm the current package passes Salsa CI[1].  I've worked down quite
> > > a list of lintian issues (some remaining once are left but are harmless)
> > >
> > > > 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
> > >
> > > Done.  Except for using short dh in d/rules.  I would prefer this
> > > but the current d/rules file is a bit complex so for the moment I
> > > did not do this conversion.
> > >
> > > >   you:
> > > >      - Tag new release (without debian/ dir)
> > > >
> > > >   me:
> > > >      - Import new release
> > > >      - Can do a team upload if you want me to do so
> > >
> > > I admit I'm motivated to do a Debian team upload right now since quite a
> > > number of bugs are fixed and hardening + reproducible builds are
> > > accomplished.  In any case I would welcome some review of the systemd
> > > service files if you might find some time to do so.
> > >
> > > Kind regards
> > >        Andreas.
> > >
> > >
> > > [1] https://salsa.debian.org/debian/zephyr/-/pipelines/933652
> > >
> > > --
> > > https://fam-tille.de
> > >
> 
> -- 
> https://fam-tille.de
> 

-- 
https://fam-tille.de

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web