On Thu, Jun 29, 08:27, Vagrant Cascadian wrote > >> Given that this change was accepted in 2019, would you consider > >> uploading a version with the fixes applied to Debian, either by making a > >> new upstream version, or applying the patches to an older version? > > > > Will do. FWIW: There are also a few unrelated patches pending. My > > plan is to merge these next weekend and then release v1.0.4. > > > > All I have to do to get the new version into Debian is to add a stanza > > to debian/changelog, and tag the tip commit, correct? > > Be sure to add Closes: #NNN for all the relevent bug numbers to > debian/changelog.
Will add Closes: #1039617, #1039618 > It also needs someone to upload to Debian. Looks like Adam Borowski > <kilob...@angband.pl> has sponsored in the past, but if you need someone > else to sponsor the upload, I could too. Yes, Adam uploaded all previous versions so far. But of course it's also fine if you sponsor the upload this time. > Possibly also updating debian/copyright. Will adjust the copyright year. Anything else you had in mind? > Building the packages and running lintian might also have some suggestions to > improve the package. The old package has a few issues (though most seem to be > the gzip timestamp warnings): > > https://udd.debian.org/lintian/?packages=liblopsub I might need some help to resolve these. The important one seems to be shared-library-lacks-stack-section, as that's an error tag while all other tags are only warnings. It seems to occur only on mips, and according to lintian-explain-tags(1), "This problem can be fixed with a rebuild". So how can one avoid this error at the source level? Then there is hardening-no-relro, which is also ld-related and which also occurs only on mips. On my x86 system, the RELRO section is present: $ readelf -a liblopsub.so.1.0.3 | grep -i relro GNU_RELRO 0x000000000000cd30 0x000000000000dd30 0x000000000000dd30 Do you think it would help to add -z relro to the two recipes of the Makefile which create the lopsubgen executable and the shared library? Finally there is the no-debian-changes warning, which I don't understand at all. How can there be "no changes to the upstream sources in the Debian-related files"? Thanks Andre -- Max Planck Institute for Biology Tel: (+49) 7071 601 829 Max-Planck-Ring 5, 72076 Tübingen, Germany http://people.tuebingen.mpg.de/maan/
signature.asc
Description: PGP signature
