Hello! I just saw that someone triggered another binNMU on hppa for curl.
First of all, please write a proper binNMU changelog. Writing "Rebuild" as the reason for a rebuild is absolutely pointless. The version suffix "+b1" already indicates that's a rebuild, the point is, *why* did you trigger it in the first place. Please be so kind to your fellow porters and use the binNMU changelog field properly. If you're really lazy, just copy the binNMU message from the other architectures. Thank you! Secondly, the binNMU on curl won't help because of #812542 [1]. The rdepends of curl are BD-Uninstallable because curl still has a hard-coded dependency on a package that gnutls28 no longer builds and therefore this isn't a bug that cannot be fixed with a binNMU but rather by fixing the source package itself. In fact, since the curl maintainers haven't fixed the bug yet, I patched the curl package for multiple ports architectures and uploaded the package with an +$ARCH suffix in the version to unreleased which is also the reason the curl package remains in "Uploaded" state on these architectures (there is already a newer version in the archive and hence the upload of the binNMU gets rejected). Anyway, just a heads-up what's wrong with curl. And, please, proper binNMU changelogs, people! Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812542 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913