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

Re: Status of python-escript repo in salsa




On 11/12/2024 12:46, Santiago Vila wrote:
Hello.

I've done my best to restore python-escript repo in salsa to a state
where it may be used normally again.

What I did was to import releases 5.6-8 and 5.6-9 from snapshot.debian.org
and put them in debian/latest, but the Debian changelog has misplaced
entries so I've added a note indicating that.

I see that Alastair put his commits for 5.6-8 and 5.6-9
in another branch called debian/trixie (I guess this could
be due to some permission problem which I also experienced
several weeks ago?), but the commits I saw in such branch
had quite a number of anomalies (like commits containing
git-conflict artifacts, commits with messages not matching
what was really changed, etc).

Because I think those commits in such state are not suitable
for debian/latest, I've used snapshot.debian.org instead.

Now there is a pending issue which is to determine to which
release really belong the misplaced entries in the changelog.

I think they were really meant for 5.6-8 but I'm not sure,
so I'm asking here for help.

Also, I'd like to know if it's ok for Alastair to remove
the debian/trixie branch now.

Thanks.

Thanks Santiago!

I'm sorry the git repo was in such a mess, my fault. Thank you for fixing it.

Yes, I think its best that debian/trixie is deleted. Yes, they were targeted for trixie because I have 6.0 in my local debian/latest, which is not yet fit for trixie but python-escript was blocking transitions.

regards

Alastair


--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
e: mckinstry@debian.org, im: @alastair:mckinstry.ie
https://mastodon.ie/@amckinstry


Reply to: