Thanks. I have just uploaded a newer version: https://mentors.debian.net/package/misspell-fixer https://mentors.debian.net/debian/pool/main/m/misspell-fixer/misspell-fixer_0.2-1.dsc
I hope I have not missed anything. Best regards, Lajos On Sun, 29 Dec 2019, Adam Borowski wrote: > On Sat, Dec 28, 2019 at 10:25:59PM +0000, Lajos Veres wrote: > > I have made some small modifications partially to address your > > recommendation and the excuses listed here: > > https://tracker.debian.org/pkg/misspell-fixer > > > > - I have removed the mentioned files. > > https://github.com/vlajos/misspell-fixer/commit/0aeb0ea73e7ce5b0e3c8500886abc57168c8b78c > > - Updated the standards-version. > > https://github.com/vlajos/misspell-fixer/commit/81d9894d8875913cf0d397c99eb88a04a8d50dca > > - Added Multi-Arch: foreign. > > https://github.com/vlajos/misspell-fixer/commit/4f51acf15f22a2ec58a1c317b4563483f6282aa4 > > > > But unfortunately most of the remaining excuses are a little unclear for > > me... > > Could you please help me to understand them? > > > > > Rejected due to piuparts regression - > > > https://piuparts.debian.org/sid/source/m/misspell-fixer.html > > > > If I follow the link it says: > > piuparts-result: failed-testing 0.1-1 > > > > And when I follow this link as well: > > https://piuparts.debian.org/sid/state-failed-testing.html#misspell-fixer > > It claims, among others, that basically every file on the system has > disappeared. That's nonsense. Looks like that part of the infrastructure > made a boo-boo. > > A package with no preinst/postinst/prerm/postrm can't possibly fail piuparts > testing -- it carries only static files that are added/removed by dpkg. You > have no Replaces that'd allow a file conflict, and your package is a leaf > one with no bogus symlinks that could possibly redirect something else. > > And, it passes piuparts on my box. > > > > Migration status for misspell-fixer (- to 0.1-1): BLOCKED: > > > Rejected/violates migration policy/introduces a regression > > > > Is this one just the end result of the others? > > Yeah. > > > > Not built on buildd: arch all binaries uploaded by kilobyte, a new > > > source-only upload is needed to allow migration > > > > This buildd related error message is also not really clear for me. Should > > I do something differently? > > According to new Release Team's rules, only packages built on the official > infrastructure are allowed to the new release, and the first upload can't > possibly be. Until someone implements a better way, every package has to be > built twice, and arch:all don't currently allow automated rebuilds. > > This means, you need to make another upload. > > And for this reason I did not wait until nits like the redundant files are > fixed: that second upload is a good opportunity to fix them. > > > > > > > There are minor issues such as: > > > > > * unused file debian/misspell-fixer-docs.docs > > > > > * redundant debian/README.source (Homepage: is a field it two other > > > > > files > > > > > already) > > > Meow! > -- Lajos Veres vla...@gmail.com 07927 460 778
