Hi, On Tue, 2025-01-14 at 01:14 +0100, Hilko Bengen wrote: > Hi, > > (CCing the last few DDs who had worked on the radare2 package.) > > after fixing radare2 FTBFS by linking with libatomic on armel (seems > like that should fix things on some non-release-architectures, too), > I > would have liked to push changes to Git. > > Unfortunately, > https://salsa.debian.org/pkg-security-team/radare2 seems > to contain only work from years back, long before renewed interest > around version 5.9.0+dfsg-1. The latest tagged version is > debian/5.0.0+dfsg-1 from early 2021. > > Should we just start over or does it make sense grab source packages > from snapshot.debian.net and import them? > > Cheers, > -Hilko > If you want continue to use the current repo it definitely needs some corrections first: - There a two tags upstream/5.0.0+dfsg, not sure how this is possible. - One of these tags has been merged into debian/master _after_ the debian/5.0.0+dfsg-1 tag and brings more than 2000 additions and deletions. - the latest import is tagged debian/0.6-1 (sic!) and again brings 1000+ changes. It culminates in commit message "Initial Upload to Debian". I suggest to rollback the repo to the first upstream/5.0.0+dfsg tag,the respective pristine-tar commit and to debian/5.0.0+dfsg-1, i.e.: upstream: 9c038c9d20937245711b7960fee8fcb76d4dda3c pristine-tar: 9b369f6c12eba23580e54eff88bd5c939be6448a debian/master: 8dcc440dd50726b919c88986b94f863396b2c28d then carefully check how this matches radare2 5.5.0+dfsg-1 available from snapshots.d.o. If this succeeds, import the subsequent source versions from snapshots.d.o. Otherwise dropping the whole repo and importing everything anew from snapshots.d.o and continue from there would be the alternative. Just my 5 cents. Sven -- GPG Fingerprint 3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
Attachment:
signature.asc
Description: This is a digitally signed message part