db5.3 package maintainance
[CCing firstname.lastname@example.org; please keep the list
in CC on replies]
Hello Dmitrijs, hello Ondřej,
I'm writing directly to you because you are listed as
uploaders for src:db5.3 and the package maintainer address
(email@example.com) is no longer valid,
therefore sending an email to the BTS would just result in a
I'm one of the riscv64 porters and db5.3 is one of the few
remaining packages that block us from being able to debootstrap
a riscv64 system. The package currently FTBFS on all
architectures due to changes in the JRE baseline (cf.
For older architectures there are binaries in unstable that
were built before the JRE changes, but for new ports that
of course isn't the case.
Adam Borowski has tried to NMU the package with the one-line
patch attached to the bugreport, but that has failed as the
source tarball contains a pre-built MS help file without
corresponding source which has led to a reject from FTP masters
so future uploads would require either removing the offending
file from the source tarball or adding the corresponding source
It would be great if you could take a look at the issue, or in
case somebody else takes care of the package now, provide us with
corresponding contact information.
If you should upload a new package version, it would also be
great if you could add riscv64 to the "JAVA_BROKEN_ARCHS" list
(as is already the case for m68k) because we currently don't have
a working JDK for riscv64.
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.