On Sun, Jan 05, 2020 at 01:37:20AM -0300, Emmanuel Arias wrote: > * Package name : jcc > Version : 3.6-1
> It builds those binary packages: > > python-jcc - generator for a Python extension from Java classes (Python 2) > python3-jcc - generator for a Python extension from Java classes (Python 3) > jcc - generator for a Python extension from Java classes (transitional) [Note: a trip through binNEW is required.] > Changes since the last upload: > > [ Emmanuel Arias ] > * New upstream version 3.6 > * New maintainer (Closes: #922568): > - Add myself to Maintainer field on d/control. > * Bump debhelper to 12 (from 9.2): > - Update debhelper to debhelper-compat on d/control Build-Depends. > * Update Vcs-* repository to salsa repository. > * Add myself on debian/* files copyright on d/copyright. > * Bump Standard-Version to 4.4.1 > * d/control: add autopkgtest-pkg-python Hi! The package has three RC bugs filed against it, and you don't close any of them. These are: #875579 FTBFS with Java 9: library path guessed wrong #885955 FTBFS: /usr/bin/ld: cannot find -ljvm -- both of these are fixed in your upload, but without closing them, the package won't be allowed back in #936761 jcc: Python2 removal in sid/bullseye -- as there are no reverse {,B-}Rdependencies, there's nothing to preserve compatibility for, thus it'd be enough to drop the python-jcc package (which you try to introduce!) -- it's not needed, and as the next Debian release will not feature Python2[1], would need to be removed shortly anyway Meow! [1]. Or, if removal doesn't succeed, Python2 will be trimmed to a stub. -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄⠀⠀⠀⠀ etc), let the drink age at least 3-6 months.