[17790] in athena10
Re: Fate of Zephyr in Debian
daemon@ATHENA.MIT.EDU (Sam Hartman)
Wed Oct 27 14:50:35 2021
From: Sam Hartman <hartmans@debian.org>
To: =?utf-8?Q?Alejandro_R=2E_Sede=C3=B1o?= <asedeno@mit.edu>,
Alex
Chernyakhovsky
<achernya@mit.edu>
Cc: Debathena Trac <debathena@mit.edu>
In-Reply-To: <CAOO-Oz2rprkWyCX3_8Q41834n+jLFW1w0XznUrHz6qD8co-EKw@mail.gmail.com>
Date: Wed, 27 Oct 2021 18:50:25 +0000
Message-ID: <0100017cc316d213-17946ea5-cef3-402f-b3a5-21461fa1668e-000000@email.amazonses.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
>>>>> "Alejandro" == Alejandro R Sedeño <asedeno@mit.edu> writes:
Alejandro> The subversion repository I mentioned agrees with the
Alejandro> debian changelog until it ends at 3.0.2-2. Debian has two
Alejandro> additional releases, 3.1~beta0-1 and 3.1.2-1, plus the
Alejandro> third no-op release 3.1.2-2 that Sam did earlier today.
Alejandro> The zephyr-im/zephyr repo has a debian changelog, but
Alejandro> nothing in it syncs up with what is in debian.
Alejandro> We could reconstitute something from snapshot.debian.org
Alejandro> for the missing releases if we can’t find the rest of the
Alejandro> history.
How upset would people be if we just asserted the current debian
directory on top of the git history.
Doing a svn history to git conversion and having it match up with the
git history of zephyr-im/zephyr.
I've mostly forgotten how to use svn, but it's not even clear that at the
svn level, the upstream history and the debian history are common; it
looks like kcr just imported tarfiles into the debian branch.
The debian svn repo is separate from the zephyr svn repo.
For something this old, trying to reconstruct history is more work than
I want to put in.
